WSUS Server Common Fault

The WSUS server is a server provided by Microsoft to provide patch management for Microsoft operating systems, Microsoft Office, Microsoft server products (ISA Server, etc.) and other products (Visual Studio series, etc.). Many companies have deployed WSUS servers, but the use of WSUS servers is not always easy. This article describes several important issues encountered in using the WSUS server and describes the workaround.

When the CPU usage is 100%

When configuring the WSUS server for the first time, some workstations will become very slow when configuring the workstation and upgrading the system using the WSUS server. The task manager of these workstations may show a CPU usage of 100%, and the svchost.exe process may also consume 100% or nearly 100% of CPU resources.

When this problem occurs, you can temporarily suspend the svchost.exe process, download the patch and install it on the workstation, and then restart the computer to solve the problem. It should be noted that when the patch is installed, the interface shown in Figure 3 appears to indicate that the patch is properly installed. On some workstations, you need to install this patch several times to solve the problem.

For the problem, there are two points to explain: 1. The WSUS server has provided this patch, but for various reasons, some workstations cannot be installed in time, so the CPU usage will be 100%. phenomenon. 2. When WSUS automatically installs patches in the background, the CPU usage may reach 100% temporarily, but it will not always be 100%, but it will be repeated between 40% and 100%. This situation is normal.

Workstation cannot contact WSUS

Use gpedit.msc to configure the workstation for WSUS server update, or import the edited "registry file" to the workstation and upgrade the WSUS server from within the enterprise. The first time you do this, in order for the workstation to download the patch from the WSUS server immediately, you need to type the following at the command prompt:

Wuauclt /detectnow

Wuauclt1 /detectnow

Then use netstat -an, if no connection to the WSUS server is found, or the above command is not used, but after a few days, the workstation does not download any patches from the WSUS server, and the workstation is not found on the WSUS server, then You need to install the WSUS client agent on this workstation and restart your computer to resolve this issue.

Update/redist/standalone/7.0.6000

.381/WindowsUpdateAgent30-x86.exe.

Automatically updated the problem

When the workstation is configured to automatically download and schedule the installation, the workstation will be installed at the specified time. Some people think that the workstation will not be installed at the specified time, but after many tests, the results are as follows:

When the workstation downloads the patch from the WSUS server, a yellow exclamation mark appears in the lower right corner and the message "Already Prepare updates for your computer, click here to install these updates." According to whether the user chooses, there will be three cases:

1. If the user clicks the yellow exclamation mark, the automatic update dialog box will pop up. Click the “Quick Install” button to start the patch installation.

2. If the user has no choice, the WSUS client program will automatically install the patch in the background after the set time is reached. At this time, if you open the task manager, you will find that a svchost.exe process occupies a lot of CPU resources in the "Process" dialog box, and it takes up a lot of memory. This process will complete the automatic installation of the patch. In addition, you can see the installed patches in the Process.

When the installation is complete, if the installed patch needs to restart the computer, if the WSUS client "for a computer with a logged-in user, the scheduled automatic update installation does not perform a reboot" is set to "disable" " or "not configured", a 5-minute countdown window will pop up. If no one cancels the operation within the specified time, the computer will restart. If the configuration is "Enabled", a prompt "Update is complete, need to restart the computer" will pop up. If the installed patch does not require a restart of the computer, there will be no prompts.

3. If it is not installed at the specified time, Windows XP will install the update when it is shut down.

WSUS can't download patches

If the WSUS server can't download the patch, in the "Event Viewer", we can see the following error: "Content file download failed. Reason: This server does not support The necessary HTTP protocol. The Background Intelligent Transfer Service (BITS) requires the server to support the scope protocol header. The solution is as follows:

First, enter the command prompt.

If you use the MSDE or WMSDE database that comes with WSUS 2.0 and install it by default, execute the following code: %programfiles%Update Services

toolsosqlosql.exe -S %Computer

Name%WSUS -E -b -n -Q "USE SUSDB update tbConfigurationC set BitsDownloadPriorityFore

ground=1"

If you are using WSUS 2.0 and an existing Microsoft SQL Server database, execute The following code: %programfiles%Update Services

toolsosqlosql.exe" -S %Computer

name% -E -b -n -Q "USE SUSDB update tbConfigurationC set BitsDownloadPriorityForeground=1"

If you are using WSUS 3.0 and Windows Internal Database (the default installation), execute the following code: %programfiles%Update Services

SetupExecuteSQL.exe -S %Computername%MICROSOFT##SS

EE -d "SUSDB" -Q "update tb

ConfigurationC set BitsDownload

PriorityForeground=1"

If using WSUS 3.0 and an existing SQL Server database installation, Then execute the following code: %programfiles%Update ServicesSetupExecute

SQL.exe"-S %Co Mputername% -d "SUSDB" -Q "update tb

ConfigurationC set BitsDownload

PriorityForeground=1"

Then restart the Update Services service.

There is a 0x80070002 error

Some workstations may appear when updating to XP SP3 "A problem prevents Windows from correctly checking the license of this machine. Error code 0x80070002". If you log out of the computer and still prompt this error after entering again, it means that the update cannot be used.

This is because the computer is installed with a cracked version of the Windows XP operating system. In general, when using the WSUS server to provide upgrade patches for workstations on the network, it does not detect whether the operating system is genuine, but in the following cases: when installing Windows Media Player 11, when installing IE 7.0 (later canceled this) Limit) and when upgrading to XP SP3.

After this problem occurs, although some information says, restore the oembios.bin file under C:windowssystem32. But in fact, to solve this problem in most cases you need to reinstall the operating system. When reinstalling, it is recommended to use the VL version of Windows XP instead of the cracked version or the lite version.

Understanding these typical issues can make it easier for you to manage your WSUS server. Of course, the network is developing, and WSUS is not static, and the actual situation of each unit is different, and the habits of each administrator are different. Therefore, the problems with WSUS servers may also be different. But as long as we are calm and calm, careful analysis and judgment after problems arise can still be resolved quickly.