Untrusted DP issue - version 2203

Question

Hi All,

We've recently acquired another company and they have two different physical locations, lets call it locations A and B.

All systems in both locations are under same domain.
Each location have its own MP/DP configured and boundaries are assigned based on locations.

Pushing SCCM agent to clients seems to work. Only difference is, location A is able to find its MP/DP correctly and resume with local installation of the agent.
Soon after the agent status turns green like it's supposed to.

Issue is with location B where it just keeps rotating DP's and is never able to find the correct site.

I am also certain the same problem is related to OSD process where PXE boot works and during the process of locating package it reports package XXX000D2 not found.

Problem is almost identical to the issue described in this LINK, except we don't use CAS, only one Primary site.

Anyone know if this is a known bug or was it ever resolved? I am running out of options.

Answer 1

Hi,

Thanks very much for your feedback. We're glad that the goal is achieved now. It's appreciated that you could click "Accept Answer" to the helpful reply, this will help other users to search for useful information more quickly. Here's a short summary for the problem.

Problem/Symptom:
In one office location, it keeps rotating DP's and is never able to find the correct site.

Solution/Workaround:
Remove the incorrect site in the boundary and add the correct site name and it started working.

Thanks again for your time! Have a nice day!

Best regards,
Simon

---

If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 2

What does the log say? Exactly what boundaries have you setup? Why have an mp at the site? Mp should be near Sql server.

Answer 3

Having seen your comment about boundaries made me think. I went to each AD and opened Active Directory Sites and Services to verify the sites and boom!
The site name for location A was very similar to another site which we do not manage.

I think what happened is, someone must have added this incorrectly to the boundary.

Fix was to remove this and add the correct site name and it started working after this.