SCCM Client connects to wrong site code in lab with Production and TP sites

[ace_ventura]

I am trying to setup a test sccm server running the tech preview with a site code of TP1 in the same domain as my main lab sccm server with a site code of RYK.  When I install the client on a windows 10 pc from the TP1 sccm console after a while it will be assigned to the RYK site.  

My boundaries for site RYK are setup as such:
10.0.0.2-10.0.0.99 (clients)
10.10.0.20-10.10.0.24 (servers a)
10.10.0.26-10.10.0.99 (servers b)

so here i am excluding the IP of 10.10.0.25 which is the TP1 site server.  My boundary group for my main RYK site is called production and it contains the three boundaries listed above.

I do have another boundary which is my AD site but there are no site systems in it and its not a member of any boundary groups,

My boundaries for site TP1 are setup as such: 
10.0.0.200-10.0.0.210 (test clients)
10.10.0.25-10.10.0.25 (cm02 TP1 server)

this site server also has a boundary which is my AD site the same as above and it also does not contain any members or is a member of any boundary groups

VM-PC08 has an manual ip of 10.0.0.201 and is joined to the home.local domain, both site servers RYK (10.10.0.24) and TP1 (10.10.0.25) are members of the home.local domain as well.

How can i run a production version of sccm along side a test tech preview version of sccm and have my clients assigned to the correct site.  when I installed the client on vm-pc08 initially it was assigned to TP1 but after a while it moved to RYK.  As you can see my boundaries and groups don't overlap so in theory that shouldn't be an issue but what am i missing?  Client push is disabled on both sites.  My clients get installed via a OSD TS on the RYK site and manually from the console in TP1

[anyweb]

personally I would setup technical preview virtually, in it's own self contained lab, that's how i do it, it's fully pki, with ad01, cm01, issuing_ca and webserver servers, self contained with 3 clients, that allows me to test everything safely

but back to your issue, have you configured client installation properties as these properties are published to Active Directory Domain Services and used during the client installation process.

the ccmsetup.log on the clients will reveal how your clients were installed... start looking there

[ace_ventura]

the clients install just fine with no issues, its when i install the clients on a test vm using the tp1 sccm console after a while they switch their site from tp1 to my main site ryk

[anyweb]

does the ccmsetup.log reveal where they are getting the installation properties from when they change site code?

[ace_ventura]

looking through the ccmsetup log no where in it does it reference my main primary site server cm01 with a site code of ryk, it does reference the correct site cm02

[ace_ventura]

it does not, there doesnt appear to be anything in that log regarding a site change at all.

[anyweb]

ok check locationservices.log and execmgr.log for clues

[ace_ventura]

nothing in execmgr.log related to it but i did find in locationservices the following:  I don't understand why it switched.  I saw the line Client is not assigned to a site. Cannot get portal info. but it didnt make sense to me when it was in fact assigned to TP1 its just after a few hours decided to switch to RYK

Client is not assigned to a site. Cannot get portal info.    LocationServices    4/1/2022 6:31:05 PM    9280 (0x2440)
Current AD forest name is home.local, domain name is home.local    LocationServices    4/1/2022 6:31:06 PM    9280 (0x2440)
Domain joined client is in Intranet    LocationServices    4/1/2022 6:31:06 PM    9280 (0x2440)
The MP name retrieved is 'CM01.home.local' with version '9068' and capabilities '<Capabilities SchemaVersion="1.0"><Property Name="SSL" Version="1"/><Property Name="SSLState" Value="63"/></Capabilities>'    LocationServices    4/1/2022 6:31:06 PM    9280 (0x2440)
MP 'CM01.home.home.local' is compatible    LocationServices    4/1/2022 6:31:06 PM    9280 (0x2440)
No AAD tenants information found.    LocationServices    4/1/2022 6:31:06 PM    9280 (0x2440)
Persisted AAD on-boarding info.    LocationServices    4/1/2022 6:31:06 PM    9280 (0x2440)
Refreshed security settings over AD    LocationServices    4/1/2022 6:31:06 PM    9280 (0x2440)
Attempting to retrieve lookup MP(s) from AD    LocationServices    4/1/2022 6:31:06 PM    9280 (0x2440)
Current AD forest name is home.local, domain name is home.local    LocationServices    4/1/2022 6:31:06 PM    9280 (0x2440)
Domain joined client is in Intranet    LocationServices    4/1/2022 6:31:06 PM    9280 (0x2440)
Lookup Management Points from AD:    LocationServices    4/1/2022 6:31:06 PM    9280 (0x2440)
Name: 'CM01.home.local' HTTPS: 'Y' ForestTrust: 'N'     LocationServices    4/1/2022 6:31:06 PM    9280 (0x2440)
Retrieved lookup MP(s) from AD    LocationServices    4/1/2022 6:31:06 PM    9280 (0x2440)
MapNLMCostDataToCCMCost() returning Cost 0x1    LocationServices    4/1/2022 6:31:06 PM    9280 (0x2440)
Raising event:
instance of CCM_CcmHttp_Status
{
    ClientID = "GUID:CC0EB89D-C05B-43C3-9157-0B07C5C035B1";
    DateTime = "20220401233106.309000+000";
    HostName = "CM02.home.local";
    HRESULT = "0x00000000";
    ProcessID = 9976;
    StatusCode = 0;
    ThreadID = 9280;
};
    LocationServices    4/1/2022 6:31:06 PM    9280 (0x2440)
Current AD forest name is home.local, domain name is home.local    LocationServices    4/1/2022 6:31:06 PM    9280 (0x2440)
Domain joined client is in Intranet    LocationServices    4/1/2022 6:31:06 PM    9280 (0x2440)
Successfully stored new Site Server Signing Certificate...    LocationServices    4/1/2022 6:31:06 PM    9280 (0x2440)
Name      : Site Server    LocationServices    4/1/2022 6:31:06 PM    9280 (0x2440)
Thumbprint : E4B0A2D7FDB9556356B9F10E2ED961DD60E7794A    LocationServices    4/1/2022 6:31:06 PM    9280 (0x2440)
Valid From: 2018-07-09, 03:29    LocationServices    4/1/2022 6:31:06 PM    9280 (0x2440)
Valid To  : 2118-06-16, 03:29    LocationServices    4/1/2022 6:31:06 PM    9280 (0x2440)
Refreshed Site Signing Certificate over AD    LocationServices    4/1/2022 6:31:06 PM    9280 (0x2440)
Removing outgoing queues, pending jobs because the client is switching cert or re-registering due to server reset request.    LocationServices    4/1/2022 6:31:06 PM    9280 (0x2440)
Security settings update detected, restarting CcmExec.    LocationServices    4/1/2022 6:31:06 PM    9280 (0x2440)
Group Policy Site Assignment key HKLM\Software\Microsoft\SMS\Mobile Client has changed, will attempt to re-assign the client.    LocationServices    4/1/2022 6:31:06 PM    9732 (0x2604)
Security settings update detected, restarting CcmExec.    LocationServices    4/1/2022 6:31:06 PM    3452 (0x0D7C)
The MP name retrieved is 'CM01.home.local' with version '9068' and capabilities '<Capabilities SchemaVersion="1.0"><Property Name="SSL" Version="1"/><Property Name="SSLState" Value="63"/></Capabilities>'    LocationServices    4/1/2022 6:31:15 PM    864 (0x0360)
MP 'CM01.home.local' is compatible    LocationServices    4/1/2022 6:31:15 PM    864 (0x0360)
No AAD tenants information found.    LocationServices    4/1/2022 6:31:15 PM    864 (0x0360)
Persisted AAD on-boarding info.    LocationServices    4/1/2022 6:31:15 PM    864 (0x0360)
Refreshed security settings over AD    LocationServices    4/1/2022 6:31:15 PM    864 (0x0360)
Attempting to retrieve lookup MP(s) from AD    LocationServices    4/1/2022 6:31:15 PM    864 (0x0360)
Lookup Management Points from AD:    LocationServices    4/1/2022 6:31:15 PM    864 (0x0360)
Name: 'CM01.home.local' HTTPS: 'Y' ForestTrust: 'N'     LocationServices    4/1/2022 6:31:15 PM    864 (0x0360)
Retrieved lookup MP(s) from AD    LocationServices    4/1/2022 6:31:15 PM    864 (0x0360)
Raising event:
instance of CCM_CcmHttp_Status
{
    ClientID = "GUID:CC0EB89D-C05B-43C3-9157-0B07C5C035B1";
    DateTime = "20220401233115.468000+000";
    HostName = "CM02.home.local";
    HRESULT = "0x00000000";
    ProcessID = 2444;
    StatusCode = 0;
    ThreadID = 864;
};
    LocationServices    4/1/2022 6:31:15 PM    864 (0x0360)
Status Agent hasn't been initialized yet. Attempting to create pending event.    LocationServices    4/1/2022 6:31:15 PM    864 (0x0360)
Raising pending event:
instance of CCM_CcmHttp_Status
{
    ClientID = "GUID:CC0EB89D-C05B-43C3-9157-0B07C5C035B1";
    DateTime = "20220401233115.468000+000";
    HostName = "CM02.home.local";
    HRESULT = "0x00000000";
    ProcessID = 2444;
    StatusCode = 0;
    ThreadID = 864;
};
    LocationServices    4/1/2022 6:31:15 PM    864 (0x0360)
No security settings update detected.    LocationServices    4/1/2022 6:31:15 PM    864 (0x0360)
Attempting to retrieve lookup MP(s) from AD    LocationServices    4/1/2022 6:31:15 PM    864 (0x0360)
Lookup Management Points from AD:    LocationServices    4/1/2022 6:31:15 PM    864 (0x0360)
Name: 'CM01.home.local' HTTPS: 'Y' ForestTrust: 'N'     LocationServices    4/1/2022 6:31:15 PM    864 (0x0360)
Retrieved lookup MP(s) from AD    LocationServices    4/1/2022 6:31:15 PM    864 (0x0360)
Attempting to retrieve default management points from lookup MP(s) via HTTPS    LocationServices    4/1/2022 6:31:15 PM    864 (0x0360)
Current AD site of machine is Home.local    LocationServices    4/1/2022 6:31:15 PM    864 (0x0360)
CcmGetLocationOverride    LocationServices    4/1/2022 6:31:15 PM    864 (0x0360)
LocationOverride flags detected on Client    LocationServices    4/1/2022 6:31:15 PM    864 (0x0360)
Refreshing the Management Point List for site RYK    LocationServices    4/1/2022 6:31:15 PM    864 (0x0360)
Retrieved management point encryption info from AD.    LocationServices    4/1/2022 6:31:15 PM    864 (0x0360)
Raising event:
instance of CCM_CcmHttp_Status
{
    ClientID = "GUID:CC0EB89D-C05B-43C3-9157-0B07C5C035B1";
    DateTime = "20220401233115.671000+000";
    HostName = "CM01.home.local";
    HRESULT = "0x00000000";
    ProcessID = 2444;
    StatusCode = 0;
    ThreadID = 864;
};
    LocationServices    4/1/2022 6:31:15 PM    864 (0x0360)
Status Agent hasn't been initialized yet. Attempting to create pending event.    LocationServices    4/1/2022 6:31:15 PM    864 (0x0360)
Raising pending event:
instance of CCM_CcmHttp_Status
{
    ClientID = "GUID:CC0EB89D-C05B-43C3-9157-0B07C5C035B1";
    DateTime = "20220401233115.671000+000";
    HostName = "CM01.home.local";
    HRESULT = "0x00000000";
    ProcessID = 2444;
    StatusCode = 0;
    ThreadID = 864;
};
    LocationServices    4/1/2022 6:31:15 PM    864 (0x0360)
Refreshing trusted key information    LocationServices    4/1/2022 6:31:15 PM    864 (0x0360)
Refreshed Root Site Code from AD    LocationServices    4/1/2022 6:31:15 PM    864 (0x0360)
Attempting to refresh TRK from AD    LocationServices    4/1/2022 6:31:15 PM    864 (0x0360)
Refreshed TRK from AD    LocationServices    4/1/2022 6:31:15 PM    864 (0x0360)
Raising event:
instance of CCM_CcmHttp_Status
{
    ClientID = "GUID:CC0EB89D-C05B-43C3-9157-0B07C5C035B1";
    DateTime = "20220401233115.733000+000";
    HostName = "CM01.home.local";
    HRESULT = "0x00000000";
    ProcessID = 2444;
    StatusCode = 0;
    ThreadID = 864;
};
    LocationServices    4/1/2022 6:31:15 PM    864 (0x0360)
Status Agent hasn't been initialized yet. Attempting to create pending event.    LocationServices    4/1/2022 6:31:15 PM    864 (0x0360)
Raising pending event:
instance of CCM_CcmHttp_Status
{
    ClientID = "GUID:CC0EB89D-C05B-43C3-9157-0B07C5C035B1";
    DateTime = "20220401233115.733000+000";
    HostName = "CM01.home.local";
    HRESULT = "0x00000000";
    ProcessID = 2444;
    StatusCode = 0;
    ThreadID = 864;
};
    LocationServices    4/1/2022 6:31:15 PM    864 (0x0360)
Persisting the management point authentication information in WMI    LocationServices    4/1/2022 6:31:15 PM    864 (0x0360)
Persisted Management Point Authentication Information locally    LocationServices    4/1/2022 6:31:15 PM    864 (0x0360)
ConfigMgr is no longer managing WindowsDO GPO.  Set to default values. Mode = LAN. GroupID = empty    LocationServices    4/1/2022 6:31:15 PM    864 (0x0360)
 

[anyweb]

well if you'd like to zip up all the logs on a client that switched in C:\Windows\CCM\logs and make them available for me in onedrive (pm me a link) I can take a look

[ace_ventura]

pm sent

[ace_ventura]

Issue resolved!

So turns out after digging around i had a group policy set for the client health script which is for my primary site only, this was running and changing the site the test clients were assigned to!