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:
Stale Entries: When you use AD discovery, the DDRs are created for the computers that reside in the AD container that we have requested to be queried by the discovery process.
The reason could be that the client has not yet reported to the SCCM\SMS server, or it was reporting previously but has now stopped.
Managing the client in the collection is a continuous task and for a healthy environment the client should be continuously reporting to the SMS\SCCM server.
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.
Sometimes the most challenging part of the Configuration Manager 2007/SMS 2003 deployment phase can be ensuring that the client successfully reports to the site server.