Windows Server R2 WSUS-12: an example of a classic troubleshooting operation

This article mainly discusses two kinds of errors, one is in the actual deployment, due to incorrect configuration steps caused by abnormal update error, the other is the completion of WSUS deployment, in the late operation of the process of errors, general errors are mainly concentrated in the post-operation period, there may be a variety of clients can not update the error.

(i) During the deployment process, the error configuration causes the client to be unable to update

The client was unable to contact the WSUS server for patch updates by looking at the client's local Windows Update log file and found the following error in the file.

650) this.width=650; "title=" 104 "style=" border-top:0px;border-right:0px;background-image:none;border-bottom:0px; border-left:0px;padding-top:0px;padding-left:0px;padding-right:0px; "border=" 0 "alt=" 104 "src=" http:// Img1.51cto.com/attachment/201405/8/639838_1399518207bct4.png "height=" 447 "/>

In fact, the above error is a typical deployment of careless errors, in the previous article I have mentioned many times, in the WSUS 3.0 era, the default update uses 80 port, and to the WSUS 4.0 era, the default is 8530 port, if you deploy WSUS 4.0, It is easy to refer to the deployment documentation for WSUS 3.0, which is the correct way to do this: When setting up Group Policy, specify the address of the update server followed by a 8530 port number. 650) this.width=650; "title=" style= "Border-top:0px;border-right:0px;background-image:none;border-bottom : 0px;border-left:0px;padding-top:0px;padding-left:0px;padding-right:0px; "border=" 0 "alt=" "src="/HTTP// Img1.51cto.com/attachment/201405/8/639838_1399518208keai.png "height=" 484 "/>

(ii) Late operation and maintenance of the error

One common mistake is to report an error code when the Windows Update is updated.

The first method of processing:

First, disable the Automatic Update and Crytographic service services separately in the services, and then change the%systemroot%\softwaredistribution and%systemroot%\windows\ System32\catroot2 the directory name, and finally the two services just restarted.

The second way of processing:

With online repair, you can access the Windows Update Troubleshooter (Bing Search) tool online, detect local Windows Update, fix it automatically, and then try to update it.

The Third Way:

Depending on the error code, search the Web for the relevant KB to determine if the problem is known, and then install the known issue of hotfix to fix it.

This article from "Zeng Hung Xin Technical column" blog, declined to reprint!