IT Knowledge Base

I have installed a bunch of updates on the WSUS Server and after that I coudln’t login to the console anymore.

So I did some research on the net and some users had to uninstal KB3148812 and others KB3159706.

Instead of uninstalling following steps helped me:

1. Elevated Command Prompt "C:\Program Files\Update Services\Tools\wsusutil.exe" postinstall /servicing
2. Enable HTTP Activation under .NET Framework 4.5 Features in the Server Manager Add Roles and Features Wizard
3. Restart the WSUS service

Microsoft released a hotfix for that:
https://support.microsoft.com/en-us/kb/3095113

Create a WSUS GPO policy for the workstations and keep in mind that the WSUS port has changed from 80 to 8530. I wrote a tutorial how to setup a WSUS GPO.

Command to search for updates:
wuauclt.exe /detectnow

Following steps solve most of the problems:
1. net stop wuauserv
2. delete everything in: 
    %windir%\SoftwareDistribution\
3. delete logfile:
    %windir%\WindowsUpdate.log
4. net start wuauserv
5. wuauclt.exe /detectnow /resetauthorization
6. Check %windir%\WindowsUpdate.log for errors

1. Install SQL Management Studio on the Server
2. Run it and use following string as your server:
    \\.\pipe\mssql$microsoft##ssee\sql\query

Error Message:
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.

You need to configure your firewall that it supports HTTP 1.1 ranges requests. Unfortunately I couldn’t reach our Firewall Administrator and I had to search for a temporary solution on my own.
You just need to change the settings, so that the BITS is working in foreground mode.

Temporary Solution Steps:
1. Install SQL Management Studio and run it
2. Connect to the DB:
\\.\pipe\mssql$microsoft##ssee\sql\query
3. Run following command on SUSDB:
UPDATE tbConfigurationC SET BitsDownloadPriorityForeground=1
4. Restart Windows Update Service

Notice:
The solution above worked for me on Windows 2008 R2 Server. But actually you could probably also do it with the solution below.  The advantage of it would be that you don’t need to install SQL Management Studio on the Server.

Solution for Windows 2012:
1. Download and install following packages from Microsoft SQL Server 2012 SP1 Feature Pack
DEU\x64\sqlncli.msi
DEU\x64\SqlCmdLnUtils.msi
2.  Create a SQL query file “C:\Temp\WSUS_SetBitsDownloadForeground.sql” with following content:
USE SUSDB;
UPDATE tbConfigurationC SET BitsDownloadPriorityForeground=1;
3. Run the query on the Windows Internal Database (WID):
C:\Program Files\Microsoft SQL Server\110\Tools\Binn>SQLCMD.EXE -S \\.\pipe\Microsoft##WID\tsql\query -i C:\Temp\WSUS_SetBitsDownloadForeground.sql
4. net stop wuauserv
5. net start wuauserv

You know the problem after a fresh windows installation. First you need to do all the windows updates and this takes some time to do it manually. This is the reason why I developed this script. I actually developed it for a packet manager called enteo but it can also be used without it.

Just download it and read the readme file carefully.

It is written in vbscript and can be easily adjusted to your packet manager. Use of course at your own risk!

PSWUInstaller100 4kb

Installation
1. Download it from http://www.microsoft.com/wsus
2. Make sure following roles are installed on the Server:

• MS Internet Information Server 7
• — ASP.NET
• — 6.0 Management Compatibility
• — IIS Metabase Compatibility
• — Windows Authentication

And install Microsoft Report Viewer Redistributable 2005
[http://go.microsoft.com/fwlink/?LinkID=70410]

3. Run the downloaded setup and follow the wizard

Configure WSUS so Computer are assigned via GPO
1. Open WSUS Console
2. Go to Computer/All Computers and create there a new Computer Group
3. Go to Options/Computers and choose “Use Group Policy or registry settings on computers.”
4. Open Group Policy Management Console
5. Create a New Group Policy and Link it to the right OU
6. WSUS Settings you will find in: Computer Configuration\Policies\Administrative Templates\Windows Components\Windows Update
7. Enable “intranet Microsoft update service location”
Intranet Update Service: http://yourwsusserver/
Intranet Statistics Server: http://yourwsusserver/
8. Enable “Client Side Targeting”
Target Group: Computer Group you created in WSUS (See step 3)
9. Check the other useful settings like Configure Automatic Updates and No Auto-Restart with logged on users
10. Restart one of the client computers and check if they are in WSUS Console listed in your new created computer group.

The easiest way to find out if the group policy is applied and really changed the right settings you can check it in registry.

Go to: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate