SOLVED SCCM Clients still point to old management point

[Gibbs]

Hi All,

I recently build a new SCCM server (Server 2019, SCCM 1906 TP) and exported/imported some of my application, packages, task sequences etc. Unfortunately also the Configuration Manager Client Package. Now when I run a task sequence to deploy a workstation the configuration manager client is pointing to the old SCCM server. So the "Assigned management point" is SCCM01, were it should be SCCM02. I think all other packages and application fail in the task sequence because the MP is wrong. The newly deployed workstations are shown as Unknown in devices on the new server. Old SCCM server is offline.
I have searched everywhere for a setting that still points to the old SCCM server, but cannot find it. Please help . Thanks.

 

[Garth]

Do you have overlapping boundaries? Did you clean up AD of the boundaries?

 

[Gibbs]

Sometimes it is so simple, just need a little reminder. Thanks!
While installing the new SCCM server I skipped the extending AD schema part, as I was thinking this was already done when I installed the original server. Forgetting the settings it sets in AD.
Got a machine deploying now, I bet it will now work.

 

[Gibbs]

Unfortunately the issue is not solved. I tried extending the AD schema again from the new server, it reported it was successful. I checked AD and DNS. All settings point to the new server. Yet when I deploy a new machine the client will point to the old server.
It is the same network, with the same boundaries. AD site boundary and a single subnet network boundary.

 

[Gibbs]

Using ADSI edit I managed to change the values under system,System Management, SMS-NP-*sitename*-*servername*.*domain*. Changed all the old values to the new server name.
Just tested a new deployment and now it works!

 

[Garth]

You should not need to edit anything, at most you might need to deleted the old AD detail and make sure that you have granted permissions.