Export (0) Print
Expand All

Issues with Client Self-Update

Applies To: Windows Server 2003 with SP2, Windows Server Update Services

WSUS uses IIS to update most computers to the WSUS-compatible Automatic Update. This process is called client self-update. To accomplish client self-update, WSUS Setup creates a virtual directory under the WSUS Web site named Selfupdate. This virtual directory holds the WSUS-compatible Automatic Updates. This is called the self-update tree.

Using Group Policy to point client computers to your WSUS server should eventually cause an Automatic Updates detection and client self-update. For more information about this process, see Deploying Microsoft Windows Server Update Services (http://go.microsoft.com/fwlink/?linkid=79983).

If the client self-update does not work automatically, use the following suggestions to troubleshoot the problem.

Use the Automatic Updates user interface to differentiate between the SUS and WSUS clients. The following illustrations show the user interface of the SUS and WSUS clients.

SUS client interface WSUS client interface de118e9d-7163-4550-a2c9-e181e6cc93e5

Some computers might already have the WSUS client installed. Other computers might have a version of Automatic Updates that is incapable of performing self-update. For more information see Deploying Microsoft Windows Server Update Services (http://go.microsoft.com/fwlink/?linkid=79983). If the clients in your organization are capable of and require self-update but are still not self-updating, see the next section.

If you have the WSUS client installed but the client computer is pointed to a SUS server, Automatic Updates falls into legacy mode and the client computer uses the SUS client user interface. In this case you need to redirect the computer away from the SUS server to get the WSUS client to function. When you point Automatic Updates to a WSUS server, the WSUS client user interface appears.

If your client computers are pointed to the WSUS server and you do not see the WSUS client user interface shown above, see the next section.

WSUS Setup creates a virtual directory named Selfupdate under the Web site running on port 80 of the computer where you install WSUS. This virtual directory, called the self-update tree, holds the latest WSUS client. For this reason, you must have a Web site running on port 80, even if you put the WSUS Web site on a custom port. The Web site on port 80 does not have to be dedicated to WSUS. WSUS uses the site on port 80 only to host the self-update tree.

To ensure that the self-update tree is working properly, first make sure there is a Web site set up on port 80 of the WSUS server. After that you should run the WSUS script that ensures a proper configuration of self-update on port 80. Open a command window on the WSUS server and type the following:

cscript WSUSInstallDirectory\setup\installselfupdateonport80.vbs

where WSUSInstallDirectory is the directory in which WSUS is installed. If the script is successful, you should see the following output:

Microsoft (R) Windows Script Host Version 5.6
Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.

SetupSelfupdateTree: Finding the index of the Web site on which WUS is installed...
SetupSelfupdateTree: Leaving GetWUSWebSiteIndex.
SetupSelfupdateTree: Finding the index of the web site bound to port 80...
SetupSelfupdateTree: iWebSiteIndex: 1 ServerBindings: :80:index: 0
SetupSelfupdateTree: Found the index of site on Port 80: 1
SetupSelfupdateTree: rootMetabasePath: IIS://LocalHost/W3SVC/1/ROOT
SetupSelfupdateTree: szPort80RootPath=c:\inetpub\wwwroot
SetupSelfupdateTree: iWusWebSiteIndex=1 iPort80WebSiteIndex=1
SetupSelfupdateTree: Warning: This is standalone WUS install. No need to do configuration for SxS install.
Success: InstallSelfupdateOnPort80 succeeded.

If you have WSUS client self-update running on port 80 of the WSUS server, see the next section.

Check the IIS logs on the WSUS server. IIS logs are typically located in %windir%\system32\LogFiles\W3SVC1 for the default Web site. Typical errors might be 404 (file not found) 401/403 (authentication/access), and 500 (Internal server error). Use IIS Help to troubleshoot any problems found in the IIS logs.

If you install Windows SharePoint Services on the same server that is running WSUS, you might see the following issues:

  • An "Access denied" message appears when Automatic Updates tries to update itself, and the latest Automatic Updates will not be running.

  • A message appears warning you that the SelfUpdate service is not available.

If client computers are not running the WSUS-compatible version of Automatic Updates, they will not be able to receive updates through WSUS.

  1. Grant Anonymous access (Anonymous Auth) to the Default Web site, ClientWebService and Selfupdate v-roots in IIS.

  2. Exclude specific requests from being intercepted by the Windows SharePoint Services ISAPI DLL by doing the following:

    1. Open the Windows SharePoint Services Central Administration Site (click Start, point to Administrative Tools, and then click Sharepoint Central Administration).

    2. Click Virtual Server Configuration, and then click Configure Virtual Server Settings.

    3. Click Default Web Site.

    4. Click Virtual Server Management, and then click Define managed paths.

    5. In the Add a new path box, set the type to Excluded Path. Under Path, type the following:

    • /iuident.cab

    • /clientwebservice

    • /Selfupdate

For more information, see KB 828810, "How to enable an ASP Net application to run on a SharePoint virtual server" (http://go.microsoft.com/fwlink/?LinkId=81417).

If the Content site is configured for Enable anonymous access and Selfupdate site is configured for Authenticated access - Integrated Windows Authentication, then client will fail to Selfupdate

  1. On the Start menu, point to Programs, point to Administrative Tools, and then click Internet Information Services (IIS) Manager.

  2. Expand the local computer node.

  3. Expand the WSUS Web site node.

  4. Right-click Selfupdate, and then click Properties.

  5. On the Directory Security tab, under Authentication and access control, click Edit.

  6. In the Authentication Methods dialog box, check the Enable anonymous access check box, and then clear all the buttons below if checked. The user name and password box should be pre populated.

  7. Click OK twice.

Check network connectivity on the WSUS client computer. Use Internet Explorer to determine whether self-update files on the WSUS server are accessible to the client computer. If you perform the following procedure and are prompted to download or open the files, you have verified network connectivity. If you do not have access to these files, there are problems with network connectivity between the WSUS server and the client computer.

  1. Open Internet Explorer.

  2. In the Address bar, type:

    http:// WSUSServerName /selfupdate/wuident.cab

    where WSUSServerName is the name of the WSUS server. You should be prompted to download or open wuident.cab. This verifies network connectivity from the WSUS client and the availability of the wuident.cab file on the WSUS server. If you do not have connectivity or the Web site is not configured correctly, you will get an HTTP error. Check the network settings of the WSUS server and any proxy servers.

  3. If there are any boxes prompting you to download or save, click Cancel.

If you are prompted to save or download both of these files, see the next section.

Check the %windir%\WindowsUpdate.log on the client computer to see if there has been any activity or any attempts to contact the server, such as cached server pingbacks. If you can find no problem with the logs on the WSUS client, see the next section.

If all else has failed, you can attempt to manually manipulate registry settings to get the client computer to self-update to the WSUS client.

  1. Click Start, then Run, and type regedit, and then click OK.

  2. In Registry Editor, navigate to the WindowsUpdate key by expanding the following:

    HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\

    If the WindowsUpdate key does not exist, you need to add it.

  3. On the menu, click Edit, point to New, and then click Key.

  4. Type WindowsUpdate as the name for the new key.

  5. Double-click the WUServer setting, type the URL to your WSUS server, and then press ENTER.

    If the WUServer setting does not exist, you need to add it.

    On the menu, click Edit, point to New, and then click String Value.

  6. Type WUServer as the setting name.

  7. Double-click the WUStatusServer setting, type the URL to your WSUS server, and then press ENTER.

    If the WUStatusServer setting does not exist, do the following:

    On the menu, click Edit, point to New, and then click String Value.

  8. Type WUStatusServer as the setting name.

  9. Navigate to the following:

    HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\WindowsUpdate\AU

    If the AU key does not exist, do the following:

    On the menu, click Edit, point to New, and then click Key.

  10. Type AU as the name for the new key.

  11. Verify that the UseWUServer setting has a value of 1 (0x1). If it does not, modify it by double-clicking the setting and then changing the value.

    If the UseWUServer setting does not exist, do the following:

    On the menu, click Edit, point to New, and then click DWORD Value.

  12. Type UseWUServer for the setting name.

  13. Navigate to the following:

    HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update

  14. Enable and configure Automatic Updates through Control Panel:

    Click Start, click Control Panel, and then double-click Automatic Updates.

  15. In the Automatic Updates dialog box, specify download and installation options, and then click OK. Make sure that Turn off Automatic Updates is not selected.

  16. Ensure that the AUState setting has a value of 2 (0x2). If it does not, modify it by double-clicking and changing the value.

  17. If the LastWaitTimeout setting exists, delete it.

  18. If the DetectionStartTime setting exists, delete it.

  19. Close the Registry Editor.

  1. At the command prompt, stop the Automatic Updates service by typing the following, and then pressing ENTER:

    net stop wuauserv

  2. At the command prompt, restart the Automatic Updates service by typing the following, and then pressing ENTER:

    net start wuauserv

  3. The self-update should occur in six to ten minutes.

  4. Wait approximately one minute, and then refresh the registry. You should now see the following settings and values:

    • DetectionStartTime (REG_SZ) YYYY.MM.DD HH.MM.SS. The DetectionStartTime value is written in local time, but the detection actually occurs 5 minutes after the time noted.

    • LastWaitTimeout (REG_SZ) YYYY.MM.DD HH.MM.SS. The LastWaitTimeout value is written in GMT or Universal Time, and represents the actual time that detection occurs.

Although these values refer to the time that detection is going to start, the first phase of detection is the process of checking whether a self-update is necessary. Therefore, these values actually refer to the time that the self-update from SUS client to the WSUS client should occur.

If the client software has not self-updated after ten minutes, refresh the \Auto Update registry key. If the LastWaitTimeout value has changed and is now 24 hours later than its previous value, that indicates that Automatic Updates was not able to contact the server URL that you specified in the WUServer value.

You should also check the functioning of the Client Web Service. See Issues with WSUS 3.0 Services for more information.

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft