Logon Server Unavailable Error
I came back from vacation the other day to find that some computers on our primary domain (example.local) were unable to access shares on a secondary domain (test.local) located in another building, accessed via a wireless link). When attempting to open the share (or just browse to the Domain Controller), the following error would appear:
Google'ing did no good, as there were only vague references to DNS issues and WINS servers (the later of which we don't use). As nothing had changed in the environment recently, I was at a bit of a loss. I could ping the DC (Homer) in question, and even RDP to it, but I couldn't for the life of me access the share. NSLOOKUP behaved normally, but then I had a thought -- the DC that I couldn't access was also acting as a DNS server (the primary one for test.local) with example.local as a Secondary Zone (which, of course, contained the DNS entries for the computers that were having trouble accessing the secondary domain). When I loaded the DNS manager and clicked on that zone, I was immediately greeted with an error stating the following:
The problem was that I had removed a DNS server over a year ago and it was still referenced as the primary DNS server for this zone. For some reason, the Windows DNS service had just now decided this was a problem and stopped grabbing copies of the zone from the functional secondary DNS server.
To fix this, I simply right-clicked on the zone, chose Properties, and then removed the offending server IP from the General tab and updated with the correct servers and order. As soon as I finished, the computers had no trouble accessing that DC again. Magic!
Exchange 2007 OWA/ActiveSync with Two SSL Certificates
Yes, it is possible. It's not pretty by any means (a proper Class 2 SSL Certificate is the best way to go), but it can be done. Click Continue Reading for the process.
Short: Microsoft Security Essentials Upgrade Error 0×80070050
I downloaded the Microsoft Security Essentials Ongoing Beta from Microsoft Connect this evening, and as before it installed normally. However, when I tried to update it to the latest version (the setup file on Connect is very out-of-date) the definitions came in fine but the core product refused to upgrade and only provided the error code 0x80070050.
Event viewer wasn't helpful, a reboot didn't fix it, and neither did uninstalling/reinstalling. On a whim, though, I decided to try to the upgrade through Windows Update (after enabling Microsoft Update) and what do you know, it worked!
TL;DR Version: If you get the 0x80070050 error code while trying to upgrade MSE through the MSE program itself, enable Microsoft Update via the Windows Update Control Panel and do the upgrade from there.
Windows Cannot Connect to the Printer: 0x0000007e/0×00000006
Windows 7 has been very good to me so far, but this morning I was literally pounding my desk in frustration over a printer issue. I just received two brand-new Dell Optiplex 780's and was in the process of configuring the printers on them when I happened across this little message:
Windows Cannot Connect to the Printer: 0x0000007e
Now here's the situation. The computers are running Windows 7 Professional x64. The printer (an HP P4015dn) is connected to a Windows XP x86 machine and shared normally. Of all of our printers, this is the only one directly shared with a computer due to a wiring issue I have yet to correct (although now I'm going to make an effort to fix it). I have several other computers running XP and Vista (x86 and x64) that already print this computer without issue, so I was rather stumped. Then I realized I had attempted to install the Vista x64 Postscript drivers instead of the Windows 7 ones.
Unfortunately, Windows 7 no longer provides a dedicated 'Printers' control panel, and the 'Devices and Printers' one doesn't have a Server Properties option to let you manage installed drivers. So, I stopped the print spooler service and manually deleted the drivers from C:\Windows\System32\spool\Drivers. When I tried to re-add the printer, though, I got this message:
Windows Cannot Connect to the Printer: 0x00000006
Hmm. Google wasn't much help, so I went to an old standby - I mannually added the network printer by choosing to create a local port (silly, I know). Here's how to get this working:
- In the Devices and Printers control panel, choose Add a Printer.
- In the new window, click Add a local printer.
- On the following screen, select Create a new port, and then choose Local Port from the drop-down list and click Next.
- When asked to enter a Port Name, use the full path to the printer. For example, if your printer share is called Dave and is a computer with the name PrintSrv1, you would enter \\PrintSrv1\Dave as the Port Name. If you receive an error saying The network path was not found, check the computer name and share name, then try again.
- You should be asked to install a driver. Manually download the correct driver (in this case, the HP Universal PostScript driver worked for my HP P4015dn) from the manufacturer's website and extract it to a folder on your computer. Then click the Have Disk... button in the Add Printer wizard and point it to that folder, then click OK and Next.
- Wait for it to install the driver.
At this point, the printer should be installed and functional. Print a test page to make sure everything worked alright, and then do a little dance (as long as no one is looking)!
Office Apps Stuck on Downloading Files from Network Shares
For a while now I was having problems opening Word and Excel (2007 and 2010) documents on my work computer. Most of the time everything would work, but every now-and-again I'd go to open something and Word or Excel would report that it was "Downloading <filename>", and simply get stuck. Although I could click the little 'X' to cancel and close the window, the process for either Word or Excel would stay active, and any attempts to kill it would fail. In the end, I'd have to hard power off the computer to get it to shutdown, and then do a cold boot.
I wasn't really bothered by it until a few of my users started reporting the same problem. I had a look in to it, and after a lot of fiddling, came across two Microsoft Knowledge Base articles that eventually led me to a solution.
By adding the registry value from the first KB article linked above (EnableShellDataCaching), and by removing the Group Policy object that was creating a persistent drive mapping and replacing it with a login script (below) to map the drive, I haven't had any further reports of the problem.
REM Login Script - Paste these lines in to a batch file, and add that .bat file to a GPO
net use z: /deletenet use z: \\server\share
Android: The cASE of the Missing Ringtones
A little while ago, I sold my old Rogers HTC Magic(+) to my sister, as I had managed to procure a Google Nexus One. Upon receiving it, however, she had troubles getting ringtones to detect in Settings >> Sound and Display >> Ringtones. A little troubleshooting led to the first problem, which was a ringtone downloaded from Rogers that was in the form of a .DM file. Unfortunately, Android devices aren't able to read these DRM-encrusted files. Even with that explained, though, there was another issue - the phone wasn't detecting any MP3's, either.
After remoting in to the computer and taking a look around, everything seemed normal. I had her mount the SD card, and after browsing around, everything looked alright. As instructed, she had created the correct folder structure on the SD card and placed the MP3 appropriately:
/Media/Audio/Ringtones
(relative to the root of the SD card)
I was a bit stumped, but then I had a brain wave, and renamed the folders as such:
/media/audio/ringtones
Sure enough, the phone then happily detected the MP3 as a ringtone.
The TL;DR version: Like most Linux-based operating systems, Android uses case-sensitive paths. Avoid the urge to properly capitalize your folder names!
Low on Server Disk Space? Have Symantec Endpoint? There’s Your Problem
This morning, I received an email from a charity I do some consulting for saying that they were getting a Low Disk Space warning on their primary terminal server. After remoting in, I confirmed that on the 120GB primary partition, there was less than 100MB free. Odd, considering that the server only has about 40GB worth of user files on it.
A quick check (done by selecting likely folders in the root of the drive and opening the properties window) confirmed that C:\ProgramData was using an extra 40GB space that it shouldn't. Further digging revealed that C:\ProgramData\Symantec\Symantec Endpoint Protection\Xfer contained somewhere in the neighbourhood of 48,000 file, each ~20KB in size.
Solution? Delete and recreate the Xfer folder, then run Live Update again. Low disk space problem solved, but would someone at Symantec care to explain just what the hell happened?
Update: Found a temporary fix here: http://www.symantec.com/connect/forums/symatec-ep-making-alot-files-under-xfer-folder
Apparently, the issues results from EndPoint rescanning files in quarantine every time new definitions arrive. If you have a lot of files in quarantine, your disk space will disappear that much faster. Go figure. Apparently they've fixed some instances of this, but not others, as it was supposed to have been solved in MR4, but is still present in MR4 and MR5.
Excluding Multiple Paths with ROBOCOPY
ROBOCOPY is an excellent command line utility that Microsoft began bundling with Windows Vista, and has since been included in Windows 7 and Server 2008 (R2 as well). It makes it incredibly simple to mirror a directory tree, and is great for batch file backups. There are a few quirks with it, however.
When using the /MIR switch, ROBOCOPY overwrites the destination path with everything in the source path. To exclude folders, you're instructed to use the /XD switch. Below is a sample with the correct syntax:
robocopy d:\ n:\Data /MIR /Z /A-:R /R:1 /W:1 /LOG:n:\logs\data.log /XD d:\vms d:\wsus "d:\System Volume Information" d:\tmpbak d:\installs d:\RECYCLER
To break this down, we start with the ROBOCOPY command itself. Following that is the Source Path (D:\) and then the Destination Path (N:\Data). Next is the /MIR switch that tells ROBOCOPY to mirror the existing directory structure and copy everything. The /Z switch sets the job in Restartable Mode, and /A-:R removes any read-only attributes. /R:1 and /W:1 tell ROBOCOPY to Retry copying the file once if it encounters an error, and Wait one second between retries (I've set it this low as the backup runs late at night, as if someone has left a file open it doesn't matter how many retries are attempted).
Following this, the /LOG switch dumps the full output of the copy job to n:\logs\data.log. This includes information on the number of files copied, directories excluded, etc....
Finally, we get to the /XD switch. Note that this is the last included switch - although you can technically have it where ever you want in the command, it's cleaner, and less error-prone if you make it the last switch.
To exclude multiple directories, simply list them with spaces in between. If the path contains spaces (in the example above, I've excluded System Volume Information), wrap it in double-quotes ("). The most important thing, though, is DO NOT EVER, *EVER* include a trailing "\" in excluded paths!
For some reason, ROBOCOPY parses the trailing \ in an odd way. If included in the command, the log will list all of the excluded paths, however it will still copy the data. It won't provide any error messages or other output. For example, if you used the following command:
robocopy d:\ n:\Data /MIR /Z /A-:R /R:1 /W:1 /LOG:n:\logs\data.log /XD d:\vms d:\wsus "d:\System Volume Information\" d:\tmpbak d:\installs d:\RECYCLER
Because there is a trailing \ on "d:\System Volume Information\", the log will report that the excluded directories are d:\vms d:\wsus d:\System Volume Information d:\tmpbak d:\installs d:\RECYCLER, however it will still attempt to copy all of them.
However, if you simply omit the trailing \, ROBOCOPY will correctly parse the list of paths and will ignore them.
Exchange Sync With Android: Possible, But Not Pretty
One of the things I loved about my old iPhone was the built-in Exchange sync. I could sync my email, my calendar, and even my contacts (although I only did the first two). Life was good.
After moving to the Android platform, however, I was disappointed to discover that although an Exchange email app was included, it wouldn't allow you to directly sync an Exchanged-based calendar. A little searching provided a way, though.
- Make sure you're running Office 2003 or 2007 - if you have the Office 2010 Beta installed, it won't work. If you still want to sync, uninstall 2010 and install 2003 or 2007, then follow the Special Note at the end of the post.
- Download the Google Calendar Sync tool.
- Install, follow on-screen instructions.
- ???
- Profit!
Now it should be noted that I did this, and at first it didn't work as I was using Office 2010 Beta 2. Even after uninstalling it and installing Office 2007, I still couldn't sync and received this error:
Could not connect to Microsoft Outlook: error -2147319779
A little searching turned up this link, which contained a hint at the solution. When you install Office 2010, it creates the following registry key:
HKEY_CLASSES_ROOT\TypeLib\'{00062FFF-0000-0000-C000-000000000046}\9.4
In the same key, there should also be a '9.3' entry. With Office 2010 uninstalled, you can safely remove the '9.4' key. Now, restart Google Calendar Sync, and everything should work just fine.
One major caveat with this solution is that your computer has to be up-and-running for the calendar to actually synchronize - fortunately, this isn't much of a problem if you're the only one updating your calendar. With any luck, though, Google will eventually support full Exchange syncing with Android.
Edit: I probably should point out that this is for ROMs without official Exchange support (such as Cyanogenmod, which syncs Exchange mail, but not the calendar). Some official ROMs, like HTC's, actually include Exchange calendar syncing out-of-box.
Update: There's an APK floating around that gives you the Exchange (Corporate) Calendar. I won't link it here, but a Google search for "CorpCal.apk" should give you what you need.
Further Update: Froyo will feature native Exchange Calendar sync, so CorpCal will be rendered moot when the update finally hits.
Even Further Update: Froyo, which has been released OTA for the Nexus One, does in fact feature native Calendar syncing with Exchange. This article is handy if you're stuck on an older ROM, but if not, just use the official method.




