September 21, 2016
Yesterday I worked with MS tech support to solve a problem at Carden with the new server that it turns out I created months ago. The problem I was having was that the sysvol was not syncing between the old and new servers. Also, AD was looking to the old server for some AD functions when it should have been looking to the new server, which holds all the FSMO roles. The question was why? I could not decommission the old server until this was resolved.
I replaced the hard drive in the old server several months ago because the boot partition was too small and was always full. So I installed a larger HD but had left the original hard drive also connected as a secondary drive. It was not booting from this drive, so I assumed it would not cause any trouble. It turns out that DFS looks to the volume ID to identify a drive when syncing, and when you clone a drive the identical volume ID can end up being cloned too. So DFS was finding two drives where there should have been one, and was therefore confused.
Once I took the older drive offline, DFS syncing operated normally. All is now well. So lesson learned. If you clone a drive with Active Directory data on it, do NOT leave the original drive also attached to that computer. If you want to use that drive for anything it should be wiped first.
July 11, 2016
So for those of you who are running a Mac and use Apple Mail this might be interesting;
If you ever get an attachment called WINMAIL.DAT it’s because Outlook (or another mail client) is encoding the file with extra text information that Apple doesn’t like.
Its like a sulking competition that’s been going on forever it seems, where neither side is willing to change…
Anyway if you do get it, check your webmail (assuming you a have webmail site) instead of asking the person to resend it in a different way. Your webmail interface generally does not use Apple’s Mail product and doesn’t fail at opening those attachments.
Got WINMAIL.DAT? Goto Webmail. Problem solved.
Either that or use a different Email client on your Mac, but I’m presuming that’s going to be more of a hassle than occasionally checking webmail.
May 12, 2016
I had a problem with a Mac that whenever I tried to run Chrome it would fail. I uninstalled and reinstalled but it would still fail.
The fix was to clear out his Chrome profile located here;
- ~/Library/Application Support/Google/Chrome
If you don’t care about the plugins/Bookmarks/etc then go ahead and either delete or rename the Chrome folder. If you do then you’ll need to poke about within that folder to save the info you want.
February 1, 2016
Weird would be a good word here…
Anyway long story short (as always) it was caused by corruption in the OFFICE profile – location found below.
Just rename the office folder – of course making sure you don’t have any office apps open at the time.
- Rename %APPDATA%\Local\Microsoft\Office to something like Office.old.
Open Word (or Excel, etc.) by it’s self (not loading a file) and then close the application.
Then go open that pesky network file and it should fix it.
January 11, 2016
Browser denies access to router because security has been tightened on most browsers!
Quick and easy work around is to use Firefox and change the config as below;
Open Firefox and go to the about:config page
- set security.ssl3.dhe_rsa_aes_128_sha = 0(false)
- set security.ssl3.dhe_rsa_aes_256_sha = 0(false)
Close the browser and reopen (just to be safe) and you should be fine.
December 9, 2015
If you’ve found this page then you know how much of a pain Symantec Endpoint Protection can be when it comes to eating up space. Server today ran out of space – down to 500mb on the main drive. After clean up it’s back to 71GB… yes you read that right.
So how to clean up Symantec Endpoint Protection’s mess? Simple;
Stop the Symantec Services.
Go to C:\Program Files\Symantec\Symantec Protection Center\db and delete (or if you have space then copy this off somewhere or zip it) the sem5.log.
Start the Symantec Services.
That bad boy just continues to eat up space without regard for the environment. Now I’m assuming that there is some sort of limit you can impose on the log file but honestly I haven’t had time (who does) and so I periodically remote in and run the above steps.
December 9, 2015
So you setup a VPN and it works. Well it kinda works. You connect and can ping but you can’t use DNS right? You can’t ping “remoteserver” but you can ping 192.168.1.10.
Simple… just add the VPN’s DNS sever right? Sure that should work… but it doesn’t does it?
Grrr annoyed you add an entry to the hosts file! WTH? Who uses that anymore anyway? But it STILL doesn’t work!
Ahh forget it. They can just remap their drives using an IP address.
Here’s how to fix it! Yay. I finally got tired of this issue and spent some time getting it to work. So before I ramble on any longer here’s the fix;
- Open properties on your VPN connection.
- Go to the Networking Tab
- Bring up TCPIP (v4 – for now)
- If you haven’t already, then add your VPN’s LAN DNS server in the first field under “DNS server addresses”
- In the second field you want to append these DNS suffixes
- Add in here the FQDN or something like mylocaldomain.local (or what ever your local AD domain is)
Worked for me.
December 3, 2015
This is something that might help for future reference. Something I very rarely have to do but would helpful for other people and a good reference.
Specifically changing where your DHCP client points DNS requests to.
- Open DHCP Manager
- Drill down to the scope
- Open Scope Options
- double tap DNS Servers
- Add your new shiny server and move it to the top of the list
- Click OK and you’re done