Applies To: System Center Configuration Manager 2007, System Center Configuration Manager 2007 R2, System Center Configuration Manager 2007 R3, System Center Configuration Manager 2007 SP1, System Center Configuration Manager 2007 SP2 This topic provides general troubleshooting information for Configuration Manager 2007 software updates synchronization and specific synchronization issues and provides detailed information about issues and possible solutions. If configuring the proxy settings does not resolve the issue, troubleshoot this issue like any other name-resolution issue on your network. The status message described in the following table is created. When synchronization fails, status message ID 6703 is created by WSUS Synchronization Manager (the SMS_WSUS_SYNC_MANAGER component in Component Status) and log file entries are recorded on the site server. When WSUS Synchronization Manager initiates WSUS synchronization, access to the Api Remoting30 virtual directory in IIS is required.
It addressed three vulnerabilities in the Windows Kernel-Mode Driver, which if exploited could allow an attacker to elevate their privileges on a compromised machine.
WSUS Configuration Manager connects to WSUS running on the active software update point once every hour, by default, and if there is a problem with ports or connectivity, errors are logged in this log file that might provide more detail than
WSUS Synchronization Manager fails to connect to the WSUS server to initiate synchronization with the message WSUS server not configured.
Look for the error message in one of the detailed troubleshooting topics for possible solutions to the issue.
Log file entries are not written to as part of the synchronization process, but the entries can provide some clues to help troubleshoot issues with synchronization.