1702 clients do not get software updates from Configuration Manager

Applies to: System Center Configuration Manager (current branch - version 1702)


After installing Configuration Manager version 1702, you may see the following symptoms:

- Newly installed clients are unable to get updates from the Software Update Point. This can also occur if the Software Update Point is moved to a different server after installation of version 1702. With verbose client logging enabled, the LocationServices.log file contains an empty value for the WSUSLocationReply entry.

- Some computers show in the console as “Unknown State”


Beginning with version 1702, clients use boundary groups to find a new software update point, and to fallback and find a new software update point if their current one is no longer accessible. If you install a new site that runs version 1702 or later, you must assign software update points to a boundary group before clients can find and use them.


Add the server running the software update point to the default site boundary group for the clients. You can add individual software update points to different boundary groups to control which servers a client can find. For more information, see software update points in the configuring boundary groups topic.


  1. Create a Boundary Group if none exists, and add all the client machines to the Boundary Group with the software update point as the SiteServer
  2. Run Machine policy cycle on the Configuration Manager
  3. Check the LocationServices.log on a client machine to confirm the client can connect to the WSUS server

Note that after doing this you may experience some temporary timeouts if a large number of clients attempts to connect to the WSUS server. This can also cause high CPU usage on the WSUS server. As the clients connect CPU usage should return to normal. If the high CPU usage persists after all clients are connected, see the section Troubleshooting High CPU usage on WSUS server in the article How to troubleshoot WSUS.