Windows Server R2 WSUS-11: Classic Client Error-handling

In the actual WSUS operations, there may be situations where you need to manually adjust the client or server, for example, because of Group Policy, or if the refresh interval is not present, and the client (including the client and server) does not receive the update, we need to perform some operations on the client to locate the problem. Confirm what caused the patch not being received.

(i) Refresh the Group Policy and collect the Group Policy result set to ensure that the client obtains the WSUS-related policies

First I landed a client, opened CMD, entered the Group Policy Refresh command Gpupdate/force,.

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_1399517242y1uh.png "height=" 204 "/>

After the refresh is successful, we use gpresult/h gpreport.html to collect the Group Policy results.

650) this.width=650; "title=" 153 "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=" 153 "src=" http:// Img1.51cto.com/attachment/201405/8/639838_1399517242bcyb.png "height=" 158 "/>

When the collection is complete, the results are saved to the current path, and a gpreport HTML file is generated.

650) this.width=650; "title=" 154 "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=" 154 "src=" http:// Img1.51cto.com/attachment/201405/8/639838_1399517242ygjz.png "height=" 362 "/>

And then we double-click on the report file, you can see the Group Policy information that has been applied to WSUS.

650) this.width=650; "title=" 155 "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=" 155 "src=" http:// Img1.51cto.com/attachment/201405/8/639838_1399517243vyyz.png "height=" 420 "/>

650) this.width=650; "title=" 156 "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=" 156 "src=" http:// Img1.51cto.com/attachment/201405/8/639838_1399517243maqh.png "height=" 217 "/>

(ii) Manually contacting the WSUS server using the Detect command

In cmd, enter Wuauclt/detectnow.

650) this.width=650; "title=" 157 "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=" 157 "src=" http:// Img1.51cto.com/attachment/201405/8/639838_1399517243qfhl.png "height="/>

If WSUS is successfully contacted, we can use the following command to see that the client is connected to the relevant port on WSUS.

If WSUS 3.0 is connected to port 80;

In the case of WSUS 4.0 or higher, the connection is 8530 or 8531 ports;

650) this.width=650; "title=" 158 "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=" 158 "src=" http:// Img1.51cto.com/attachment/201405/8/639838_1399517244isoe.png "height="/>

After doing this, the default machine that has been contacted to WSUS is placed in the Unassigned Computer group of WSUS.

(iii) Look at the client's windowsupdate log file

If you have done the above two steps, or can not contact the WSUS server, then we may need to check the local log file, to see if the log is not recorded in the relevant error message.

Look, my log record is normal, no error.

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_1399517244mfmf.png "height="/>

(iv) If the update is not normal, see if the local Windows Update component is normal

This is mainly to see if the local Windows Update Service is turned on and so on, which will be introduced in the following troubleshooting article.

(v) If the update is not normal, you need to determine whether the product is a bug

This is mainly to see the WSUS Team blog, or TechNet published KB, or with the agent confirmed to judge.

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