Client computer not updating wsus

The server will only allow those clients within its boundary to download the polices, so if you have not specified the boundaries the client will not be authorized and the policies will not get downloaded.

For boundary issues you can use this as a reference:

If that container has the stale records for the resources, then client records may be created for systems that don’t actually exist, thus they will never report.

A few of these reasons are discussed below: The first thing to check is whether the client is on the network, and if it’s not on the network, does the system even exist?

Resolution: For the stale records you need to make sure that the AD container is cleared of these stale records and scavenging is done for the computers container in AD regularly.

Once this is done you can either make use of the maintenance task or you can create a collection for the NON SMS CLIENTS and then do a delete special to the collection so that the entries will be removed permanently from the SMS\SCCM database.

If you are not publishing the information in AD then you need to make sure that the SLP is configured and working.

For more information you can check Post-installation phase in the link: The client itself is not installed in the Agent You can take a look at this article which will give you a detailed explanation of how you can make sure that the client is installed and reporting successfully. Make sure that the client is able to communicate to the SMS\SCCM server using the FQDN as well as the Net BIOS name. If you can’t ping the server using the FQDN then you will have problems.

Search for client computer not updating wsus:

client computer not updating wsus-6client computer not updating wsus-11

Leave a Reply

Your email address will not be published. Required fields are marked *

One thought on “client computer not updating wsus”