Hi Sergi,
When a client receives a different site code than expected, it can lead to issues with configuration and behavior. The site code determines which Configuration Manager site the client belongs to.
First, try check this initial ones;
- Boundary Groups: Ensure that the client’s IP address falls within the correct boundary group associated with the desired site.
- Subnet Boundaries: Review the subnet boundaries defined in your environment.
- In your example, both site XXX and site YYY have the same 192.167.34.0 subnet. This overlap could cause conflicts.
- Make sure each subnet boundary is unique and doesn’t overlap with others.
- Boundary Group Relationships: Check if the boundary groups are correctly associated with the appropriate site systems (Distribution Points, Management Points, etc.).
Additionally. on the client machine, review the Configuration Manager logs (e.g., LocationServices.log
, ClientIDManagerStartup.log
, etc.).