updates stop after moving ConfMgr

Question

Microsoft updates seem to have stop working after moving the ConfigMgr servers to a new IP network. All servers are being moved out of the old server network.

 See these log entries in UpdateTrustedSites.log the newest are a month old

Starting UpdateTrustedSites with false  S-1-5-21-436374069-484763869-1343024091-27996

AddDefaultPortalToTrustedSites: There is no key for existing URL. Adding key with empty string value for URL.

AddDefaultPortalToTrustedSites: It was determined that catalog Url should not be added to the trusted sites zone.

AddDefaultPortalToTrustedSites: Existing URL is empty.

AddDefaultPortalToTrustedSites: It was determined that catalog Url should not be added to the trusted sites zone.

Answer 1

Did you update your Boundaries with new IP Ranges?

Answer 2

Hi, @Carl94580345

Thank you for posting in Microsoft Q&A forum.

Like Garth mentioned, after you move the ConfigMgr servers to a new IP network, you have to update your boundaries and boundary groups, and make sure the software update point assigned to the new boundary group.

After adding the software update point to the boundary group, run Machine Policy Retrieval & Evaluation Cycle on the Configuration Manager. Check the LocationServices.log on a client machine to confirm the client can connect to the Windows Server Update Services (WSUS) server.

---

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Add comment".