However, if you haven't seen your GPO in the output, make sure the computer is properly scoped in the GPO Security Filter and the policy is linked to an OU in a way that it could reach the computer object, so you must review your GPO configuration. In this step you want to make sure there is no other GPO in your environment wrongly applying the same settings and so, preceding the correct ones.
To do that, open the prompt as administrator and type:. Make sure the output shows the correct information for your environment. So if you confirm that the output is correctly showing the settings you have configured in your GPO, you can move ahead.
If settings showed are not those you have configured, come back to your GPO management and make sure there is no another old Policy applying the same settings. A really nice way to find out which GPO is applying the settings to your client is executing the command: rsop.
Find out more about Resultant Set of Policy here. Time to test DNS resolution, to do that execute in a prompt:. The default WSUS port used for that , so if you have any different port used in your environment, make sure to use it at this test. To do that, download the tool called Port Query and open it from your client computer:. You can filter the list of computers under a given computer group by status.
The default shows only computers for which updates are needed or which have had installation failures; however, you can filter the display by any status.
Click Refresh after changing the status filter. You can also manage computer groups on the computers page, which includes creating the groups and assigning computers to them.
For more information about managing computer groups, see Managing computer Groups in the next section of this guide, and section 1. You must first configure client computers to contact the WSUS server before you can manage them from that server.
Until you perform this task, your WSUS server will not recognize your client computers and they will not be displayed in the list on the computers page. For more information about setting up client computers, see 1. WSUS allows you to target updates to groups of client computers, so you can ensure that specific computers always get the right updates at the most convenient times. For example, if all the computers in one department such as the Accounting team have a specific configuration, you can set up a group for that team, decide which updates their computers need and what time they should be installed, and then use WSUS reports to evaluate the updates for the team.
Computers are always assigned to the All computers group, and remain assigned to the Unassigned computers group until you assign them to another group. Computers can belong to more than one group. Computer groups can be set up in hierarchies for example, the Payroll group and the Accounts Payable group below the Accounting group. Updates that are approved for a higher group will automatically be deployed to lower groups, as well as to the higher group itself.
In WSUS itself there is are 4 groups under all computers: unassigned computers, excluded computers, client computers, server computers. Judging from the GPO looks like you are not using Group Policy to assign computers but rather registry settings. Let me know what this windows says.
Note: new computers will automatically be placed in the unassigned computers group. Thanks hsc This machine came from our ERP supplier and my guess is they didn't sysprep it In case you have more computers with the same WSUS client ID usually caused by cloning machines or copying VMs you can reset it with the following script:. This batch file will do the following: Echo 1. Stop the wuauserv service Echo 2. Delete the AccountDomainSid registry key if it exists Echo 3.
Delete the PingID registry key if it exists Echo 4. Delete the SusClientId registry key if it exists Echo 5. Restart the wuauserv service Echo 6.
0コメント