Update WSUS to show Windows 8 Computers as Windows 8 not Windows XP

If you have a server running Windows Server Update Services 3.0 SP2 (SBS 2003 / SBS 2008 / SBS 2011 etc) and you also have some Windows 8 clients that you have joined to the domain, they will probably show up in WSUS as Windows XP Clients not Windows 8!

To resolve this, please install the following patch from Microsoft:


Once installed, you should see the Windows 8 clients reported as Windows 8.


2012 in review

The WordPress.com stats helper monkeys prepared a 2012 annual report for this blog.

Here’s an excerpt:

19,000 people fit into the new Barclays Center to see Jay-Z perform. This blog was viewed about 160,000 times in 2012. If it were a concert at the Barclays Center, it would take about 8 sold-out performances for that many people to see it.

Click here to see the complete report.

Windows 8 – After actually using it for 24 hours

My first impressions of Windows 8 were not very favourable as like most people, I am a creature of habit and change for the sake of change doesn’t sit well with me, so seeing the new Metro UI on Windows 8 for the first time when I installed the Release Candidate onto a PC for testing was a little bit of a shock to the system to say the least.

I had ignored Windows 8 for as long as I possibly could but being in IT Support it wasn’t long before some of our customers had bought a new PC / laptop with Windows 8 on it and ultimately I would end up having to support it, so felt that it was time to take my head out of the sand and swallow the pill, however bitter it was going to taste.

I had also read Mark Minasi’s recent newsletter about Windows 8 and the Surface Tablet (not something that is going to be purchased by me – I love my iPad / iPhone) and decided that perhaps it might not be quite as horrendous as I had first thought it might be.

So I took the already burned DVD with Windows 8 Enterprise on it home and popped it into my laptop and let it install (I decided upon a fresh installation for cleanliness, which is usually a much better way to install Windows).

Once installed, it took a little while to figure out where to find everything but after finding the desktop, customising it to add things like Computer / Control Panel / Networks etc, my favourite background photo of a Tornado GR4 flying past me at Biggin Hill Air Show, I already began to feel at home again and it wasn’t long before I had joined the office domain from home (via my LAN to LAN VPN), had installed Office 365, configured my various email accounts (you can never have too many!) and various other bits of software and was merrily using Windows 8 just as I had done with Windows 7.

Not sure I’ll ever get to like the Tiles on the Metro UI, but then I didn’t ever think I would like Windows 8, so watch this space.

Activating Windows didn’t work initially as it apparently couldn’t find the Internet, despite browsing working happily, so I searched for a solution and ended up using slmgr.vbs to get it activated using an Administrative Command Prompt (slmgr.vbs /ipk ABCDE-FGHIJ-KLMNO-PQRST-UVWXY followed by slmgr.vbs /ato).

The next problem I had was installing some software which needed to install .NET Framework 3.5.  Now .Net Framework 4.5 comes pre-installed on Windows 8, but to get 3.5 installed seemed a little tricky as yet again, it couldn’t seem to find the internet!  What the heck was going on?  Trying to add it again from Control Panel> Programs and Featrues> Turn Windows Features on or off failed for the same reason, so I was beginning to get a bit frustrated.

After a bit of searching using a well-known search Engine (that doesn’t rhyme with Ping), I came upon an article that allowed me to manually install it using the command prompt again!  Is there a pattern forming here or am I suffering from a ‘feature’ of the version I happened to download from Technet?

So, with .NET Framework 3.5 installed, I could complete the Office 365 installation / customization and install other software that wouldn’t install without it (Roxio RecordNow Premier).

I am now trying to install Skype, so search for it in Chrome (I stopped using IE a long time ago – despite being forced to use it on a few Microsoft sites otherwise it just doesn’t work) and it suggests I visit the Microsoft Store, which I do, then just type Skype and it finds the App.  I go to install it and it insists that I log in to be able to install it using a Microsoft Account which I find a little annoying.  I just want to install it!  So having signed in using my seldom used hotmail account, I am allowed to install it and off I go.

One feature I have just found is the ability to turn off the Live Tiles – excellent – most are now being turned off 🙂 (Sport / Finance / Travel / People etc) – I don’t like the constant moving tiles as it is annoyingly distracting, especially for things I couldn’t care less about.

Windows 8 Music is now happily playing my iTunes music, so that’s a useful feature and the added information about artists that is available for each artist is quite nice to have.

So – all in all, the rollercoaster ride that I thought I was going to have with Windows 8 hasn’t materialized and despite not being a fan of the Metro UI, I am not rushing to switch back to Windows 7.

If you are debating whether to make the switch to Windows 8 and are used to Windows 7, then there isn’t that much to be upset about as they are virtually one and the same, you just lost the Start Menu Flag and gain lots of pretty colour tiles instead!  Once you have worked out how to switch to the desktop using the Desktop Tile, you are back in home territory and should be feeling warm and cosy again.  My laptop isn’t touch-screen capable, so using a keyboard / mouse is what I am used to and although I now have to press the Windows Key more than I ever have before, I can get used to it.

If you are switching from Windows XP as I am sure one or two are, then it will be quite a radical change and may take some getting used to, but in all fairness, I would take the plunge as you won’t be disappointed (once you are a little bit more familiar with Windows 8).


Exchange 2003 Activesync HTTP 500 Error

Further to my Exchange 2003 / Activesync Troubleshooting Guide which can be found here, I was working remotely on a Windows 2003 Server with Exchange 2003 SP2 installed over the weekend having been asked to try and make Activesync work as they had read through my guide and not managed to get everything working properly.

Initially the server needed to have it’s DNS configuration fixed so that the server could talk to the Internet and allow me access, so once their IT department had resolved that issue I was given credentials and started to look at the problems on the server.

Checking the settings against my article, everything appeared to be set properly, but the test on the test site was throwing HTTP 500 errors (my least favourite!), so I followed Method 2 of KB883380 (remove and re-create the Exchange IIS Virtual Directories) and once they had been recreated and the IIS settings re-checked, I re-ran the test on the test site and still received the HTTP 500 error.  At that point I was debating a call to Microsoft, but started to check the Event logs on the server and saw various DNS related errors which were of some concern.

Outlook 2007 was also installed on the Exchange 2003 server, so I wasn’t convinced that I had a simple fix on my hands.

I ran the Exchange 2003 Best Practises Analyzer tool and that reported that Exchange could not be contacted, which suggested a DNS issue.  In the DNS logs there was an Event ID 800 error:

The zone <zone> is configured to accept updates but the A record for the primary server in the zone’s SOA record is not available on this DNS server. This may indicate a configuration problem. If the address of the primary server for the zone cannot be resolved DNS clients will be unable to locate a server to accept updates for this zone. This will cause DNS clients to be unable to perform DNS updates.

The suggested fix for this was to run dcdiag /fix followed by netdiag /fix and then to restart the Netlogon Service.  I did this but nothing changed.

Running the netdiag /fix threw up the following error:

DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE [FATAL] Failed to fix: DC DNS entry xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx._msdcs.internaldomainname.local. re-registeration on DNS server ‘Server IP Address’ failed.

I checked the DNS zones and saw that both the _msdcs.internaldomain.local zone and internaldomain.local zones were not showing all that they should have been so I deleted both zones and recreated them manually (referring to another Windows 2003 server for the relevant entries.  Once all that could be manually created was created, I re-ran dcdiag /fix and netdiag /fix and still received the error above.

I then tried searching for a way to fix this problem but drew a blank.  Looking through the other event logs, I came across the following error in the System Log:

Event ID: 5788
Source: Netlogon
Description: Attempt to update Service Principal Name (SPN) of the computer object in Active Directory failed. The following error occurred: The attribute syntax specified to the directory service is invalid.

Searching for this error landed me here and upon checking the Computer Name / Domain Name,  I saw that the computer name was simply computername. not computername.internaldomain.local.  Never seen that one before.

Following the resolution in the MS article, I created a VB Script file and ran it on the server and rebooted.

Following the reboot, I re-ran the dcdiag /fix and netdiag /fix and the errors had gone.  In addition, some of the DNS records that I wasn’t able to create manually were magically back, so that seemed to have resolved the DNS issues – hurrah!

I then decided to re-test Activesync and happily received a complete pass on all tests – so now that Exchange could talk to itself, Activesync could actually work!

Running the Exchange Best Practices Analyzer again I was happy to see that Exchange could now talk to itself and the results showed a much happier server with only a few minor issues.

So – if you are seeing the dreaded HTTP 500 error and have gone through my Guide, followed KB883380 method 2 and still get the same error – it just might be a good idea to run the Exchange BPA and check your DNS settings are 100% happy.


Yet more Bad IT Support Companies!

Following on from my earlier Blog Post about bad IT Support Companies (here) I visited a potential new customer today to look over their IT.  The background information I got from the company was that they had used their existing IT Support Company (a one-man band) for the past 5 years or so and whilst mostly happy with their service, there were some outstanding issues that were being neglected and this was causing some concern to the company.

They had recently installed a ‘server’ and their IT wasn’t running as smoothly as they had anticipated, so wanted to get a 2nd opinion about their setup and my company (IT Eye Ltd) was recommended by a mutual company.

Once I arrived, I had a quick look over their IT and came across 4 PCs and a Netbook.  Asking where the server was, I was directed towards an HP xw6600 Workstation with a label on it suggesting it had come out of a company in New York City (NYC-XXXXXXXXX)!  I then used Remote Desktop to connect to the server and discovered that it was running SBS 2008.  This prompted the question about when the server was purchased and I was told May of 2012.  I then asked how much they had paid for the server and they advised me £2,500.

Okay – so they had a recently installed SBS 2008 server of which Exchange 2007 was now no longer supported by Microsoft because the Mainstream Support had now expired!  That begged the question why SBS 2011 wasn’t installed and to that there wasn’t an answer.  I then looked for a license sticker and couldn’t find one, so that also begged the question if they were actually legal.  This conversation continued to the other workstations and no conclusive evidence was available to suggest that they were even remotely compliant.

Looking at one of the XP workstations I saw that it was running XP pro, so checked to see if it was part of the Domain and saw that it was still configured as a Workgroup.

Data was being shared from the server, so at least the server was being used for something other than a drain on their electricity bill, but data was still being held on the Netbook and the data wasn’t being copied to the server or backed up, so was at risk of being lost.  No evidence of server backup was visible either.

I then asked about emails and found out that they were being hosted externally (1and1) and were being collected via Outlook configured as an SMTP/POP3 account and to allow for shared calendars to be accessed, they had turned to Google Mail.

I then pointed out that their server had Exchange built-in and that they need not pay for mail to be hosted externally or use Google Mail for shared Calendars as they could do everything on their own server.

At this point – I think they had decided that they were not being well looked after by their existing IT Support Company and I left them pondering my findings.  We will wait to hear from them and see how they want to proceed.


SBS 2008 / 2011 Disk Space Eaten Up By SharePoint SQL Log Files – How To Reduce The Log File Size

Having been asked to look at an SBS 2008 server with a 74gb C: drive partition that was regularly running out of space (4.5Gb left when I checked this morning) and after freeing up whatever I could using the usual methods of disabling WSUS log files and clearing out old logs etc using the following article:


I decided to see if there was something more that I could do that was slightly more permanent.

I downloaded Windirstat from Sourceforge and installed it onto the server and let it scan the C: drive of the server.

When it had finished scanning, I noticed that by far and above the largest amount of data on the C: drive was being eaten up by the Sharepoint Config SQL Database Log File – amounting to about 24Gb of disk space!  What the heck?

A quick poke around the internet landed me on the following link:


Which allowed me to reduce the overall log files size to about 500Mb and the C: drive of the server now has a more satisfactory 27.9Gb of free space and is no longer sending me errors about the disk space running low, which is always welcome.

One slight issue I had when trying to look at the properties of the Database to change the Recovery Model to Simple was a lack of permissions and an error, but a quick search again landed me on this page:


Now I am by no means an SQL Guru, but I managed to work out how to change the Database Owner from NULL to SA by right-clicking on the Sharepoint_Config…………….. Database and choosing New Query.  Then just type sp_changedbowner ‘sa’ and press F5 to execute the command and bingo, the database owner has been changed and you can now look at the Database properties without seeing an error and thus you can complete the shrinking of the Log Files.

Hope that this frees up tons of space for you too.