This topic contains information about how to resolve common problems with Update Services.
Computers are not registering with Update Services.
Update Services keeps track of the computers that are registered with it, and it periodically compares this list with Active Directory. Computers that are listed in Active Directory and that are not registered with Update Services are shown in a warning message in the Update Services home page status area.
Computers may not appear to register with Update Services for a variety of reasons. Some common reasons are:
- The computer accounts in Active Directory may refer to decommissioned or inactive computers. If this is the case, you should delete the computer account by using the Client Computers or Server Computers snap-in in the Server Management console.
- You have just installed the Windows Small Business Server 2003 R2 (Windows SBS 2003 R2) Technologies. In this case, you must allow at least 90 minutes for the client computers to refresh their Group Policy settings. When the client computers refresh their Group Policy settings, they receive new Group Policy settings relating to Update Services, which configure Automatic Updates to use Update Services on the computer that is running Windows SBS 2003 R2. During the first contact with the server, the client computers register with Update Services.
Update Services is running, but updates are not being downloaded from Microsoft Update.
If you have installed Update Services and enabled synchronization through the Update Services home page, but synchronization fails, you may have a problem with the proxy settings.
If you use a proxy server to access the Internet, you need to include that information in the Proxy Server settings for Windows Server Update Services (WSUS) 2.0.
If you installed Internet Security and Acceleration Server (ISA) 2004 with Service Pack 1 from the Windows SBS 2003 R2 Premium Technologies discs, this setting is automatically configured for you.
To configure the proxy-server setting in the WSUS Administrator's console, complete the following steps:
- Click Start, and then point to Administrative Tools. Click Microsoft Windows Server Update Services.
- On the navigation bar, click Options.
- When the Options page appears, click Synchronization Options.
- Under Proxy Server, select Use a proxy server when synchronizing.
- Enter the server name and port number. If your proxy server requires credentials, select the option Use user credentials to connection to the proxy server, and then enter the user name, domain, and password information.
- Under Tasks, click Save settings.
Client computers do not apply the Group Policy objects (GPOs) for Update Services.
If the client computers do not appear to apply the GPOs for Update Services or they appear to apply the GPOs incorrectly, and you have previously installed WSUS 2.0 or a pre-release version of Update Services, you may have a conflict with the GPOs on the domain.
Update Services creates three GPOs that apply to the Windows SBS 2003 R2 domain:
- Small Business Server Update Services Client Computers Policy
- Small Business Server Update Services Common Settings Policy
- Small Business Server Update Services Server Computers Policy
These are the only GPOs related to Update Services that should exist in the Windows SBS 2003 R2 domain.
To verify the GPOs that are related to Update Services and that apply to your Windows SBS 2003 R2 domain, complete the following steps on the computer running Windows SBS 2003 R2:
- Click Start, and then click Server Management.
- In the console pane of the Server Management console, double-click Advanced Management.
- Double-click Group Policy Management, double-click Forest: YourDomain.local, where YourDomain.local is the name of your Windows SBS 2003 R2 domain, and then double-click Domains.
- Double-click YourDomain.local, and then double-click Group Policy Objects.
- Verify that the only GPOs related to Update Services match those listed in this topic.
- If you have any other GPOs related to Update Services or to WSUS 2.0, you should delete them so that they do not conflict with the GPOs that the release version of Update Services creates.
Errors related to update installation and system errors related to Update Services are resolved, but the Update Services home page continues to display the error.
If an error occurs with Update Services, Update Services attempts to display it on the Update Services home page. Update Services renews and deletes error messages every 24 hours. If the error is resolved before 24 hours have elapsed, the error continues to appear until 24 hours have elapsed. After 24 hours, all error messages are removed. If the error is still present, it is re-displayed for another 24 hours. If the error is no longer present, the error is no longer displayed.