WSUS 3.1 and the SelfUpdate Virtual Directory

Sunday, January 18th, 2009 | Tech Help

I came back from my extended leave to find that my workstations and servers had not checked into the WSUS server for months. After a bit of detective work the issue came down to the SelfUpdate virtual directory in IIS was missing. The Microsoft help page details how to fix the issue but wasn’t completely helpful. More on that later.

Here is what I did to get my clients checking in again.

Check the folder permissions on the SelfUpdate directory, located at C:\Program Files\Update Service\SelfUpdate. Make sure the permissions like this;

Group Permissions
Administrators Full Control
System Full Control
Domain/Users or Local/Users Read&Execute, Read, List Folders
IUSR_ComputerName Read&Execute, Read, List Folders

In my case the IUSR_ComputerName permission was missing.

After adding the correct permissions I looked for the re-installation msi, Selfupdate.msi. The only problem is that the SelfUpdate re-installation msi was not found on my WSUS server. Turns out in the recent WSUS update to 3.1 this installer can become corrupted and not installed on the server.

To get the Virtual Directory back I would have to install it by hand. Here are the settings you need to create it;

Open Internet Information Services (IIS) Manager. Right click on the “Default Web Site” and choose;

  • New
  • Virtual Directory…
  • It started the VD Creation Wizard
  • Alias = SelfUpdate
  • Path = C:\Program Files\Update Services\SelfUpdate
  • Finish the wizard.
  • Right click on the newly SelfUpdate and choose Permissions.
  • I added “Authenticated Users” and gave them the default rights:
    • Read & Execute
    • List Folder Contents
    • Read

After completing these steps I ran “wuauclt /detectnow” on each of my servers. I left the workstations to check in on their own.

Within 12 hours the number of missing clients had gone from nearly 200 to less than 50. Once everyone logs in on Monday morning this number should dwindle to nothing.

Tags: , ,


5 Comments to WSUS 3.1 and the SelfUpdate Virtual Directory

Alan Pugh
March 7, 2009

Thanks for the info.

I had (almost) the same problem –

1) no Selfupdate.msi file
2) permissions corrupt on the selfupdate VD

I used your instructions to recreate the VD

Thanks again!

Alan Pugh
March 7, 2009

Then I was happy to see that in the event viewer the logged events had changed from
1) ‘Self-update is not working’, to
2) ‘Self-update is working !

That was the kind of instant IT gratification that one seldom comes by!

Nice photos too, by the way!

dal
March 20, 2009

Thanks!!! for this fix. Been trying to resolve issue for 2 days.

Dave
April 26, 2009

That was the kind of instant IT gratification that one seldom comes by!

Nice photos too, by the way!

I noticed the change in the event viewer also. M$ rarely gives those nice messages to us IT Pros.

Thanks for the compliment on the photos. Now she is moving too fast to get nice photos.

George Konikkara
August 10, 2009

Thanks a lot for your solution. That worked for me . Please provide good inputs like these in future. Thanks again and enjoy your kid while you can . Have fun.

Search

Catagories

Photos

IMG_1590.JPG
IMG_1604.JPG
PA040204.JPG
PA040199.JPG
IMG_1579.JPG
PA050216.JPG

Get Spiceworks!

Free Networking Monitoring Software For Network Management