Consider the following scenario:
- You have WSUS installed on either Windows Server 2012 or 2012 R2
- You install KB3159706
In this situation, WSUS fails to start correctly and thus fails to function.
There are additional steps that are required to configure this update once it is installed. The steps can be found in KB3159706.
Note: If using database mirroring or the SUSDB is part of an AlwaysOn Availability Group, this must be undone before performing the actions described in KB3159706 as a schema update is required for the database.
Microsoft recently made a hotfix available that patches WSUS on Windows Server 2012 and 2012 R2 to allow Windows 10 upgrade to version 1511. Installing the update is not, however, the only step that is required…
- Install the hotfix. This can be downloaded from https://support.microsoft.com/en-us/kb/3095113. Ensure that you pick the appropriate hotfix for the version of Windows Server on which you’re running WSUS. Note that if you’re running Windows Server 2012 R2, there’s also a pre-requisite install.
- Once the hotfix is installed and you’ve restarted your WSUS server, look in the ‘Products and Classifications’ option under the Classifications tab and ensure that the checkbox for upgrades is selected. This is not selected automatically for you:
Note that the upgrade files may take quite some time to download to your WSUS server at the next synchronisation.
- Add a MIME-Type for ‘.esd application/octet-stream’ in IIS on the WSUS server. To do this:
Open IIS Manager
Select the server name
From the ‘IIS’ area in the centre of IIS Manager, open ‘MIME Types’
Enter the information above:
Click OK to close the dialog.
Note: Without this step, clients will fail to download the upgrade with the following error:
Installation Failure: Windows failed to install the following update with error 0x8024200D: Upgrade to Windows 10 [SKU], version 1511, 10586.
- Approve the Upgrade for the classes of computer in your organisation that you want to be upgraded.
Once all of the above steps are in place, computers that are targeted for the upgrade should have this happen automatically at the next update cycle.
During a recent WSUS upgrade from an old server to a new virtual machine running Windows Server 2008 R2, I saw an issue with the server not downloading updates correctly. The server appeared to synchronise correctly, but then no updates were downloaded.
We originally saw an issue like this when we started using Microsoft Threat Management Gateway, and the errors reported in the application event log on the new WSUS server were the same, namely:
Error 10032: The server is failing to download some updates
Error 364: Content file download failed. Reason: The server does not support the necessary HTTP protocol. Background Intelligent Transfer Service (BITS) requires that the server support the Range protocol header.
Microsoft KB article 922330 provides a solution for this specific issue, in our case we’re using a pre-existing SQL Server, so went with
"%programfiles%\Update Services\Setup\ExecuteSQL.exe" -S %Computername% -d "SUSDB" -Q "update tbConfigurationC set BitsDownloadPriorityForeground=1"
However this didn’t solve the issue.
In our case, the existing instance of SQL was on another server, so the command should have been:
"%programfiles%\Update Services\Setup\ExecuteSQL.exe" -S SQLServerName\Instance -d "SUSDB" -Q "update tbConfigurationC set BitsDownloadPriorityForeground=1"
Once the revised command had been run and the WSUS server restarted, the update downloads started automatically.
I’ve been a bit delayed writing this final blog post from Tech Ed EMEA 2008, so I’m back in the UK. The final day at Tech Ed 2008 EMEA IT was not quite as session filled as previous days, mainly because Rik and I had to be heading off to the airport shortly before 3pm to catch our flight home.
The first presentation of the day was on getting the most out of WSUS 3.0 SP1. One of the items that was mentioned was the arrival of WSUS 3.0 SP2; this is currently in the planning phase and aims to fix the top customer and partner issues seen. It will also install on Windows Server 2008 R2. A number of scenarios for WSUS were discussed, including larger numbers of clients, branch offices and disconnected clients (submarines being the example used!) and some best practices discussed. If the video of this talk is available (at the time of writing, it isn’t unfortunately) and you use WSUS, I’d recommend watching it.
The second (and last) talk of the day I went to discussed Exchange 2007 SP1 and Hyper-V. The good news is that Exchange 2007 SP1 is fully supported on any of the x64 hypervisors validated by Microsoft on Windows Server 2008. If you want to virtualise your Exchange 2003 installation, you’ll need to use Virtual Server 2005; note that Exchange 2003 is explicitly not supported on Hyper-V.
Following these talks Rik and I spent some time talking to more of the experts in the ask the experts pavilion and got some answers to some long-standing questions.
Our flight home was uneventful, but it seemed rather cold when we stepped out of the plane at Manchester after the week in Barcelona!