SOLVED HowTo move clients to new primary site server when old one crashed

[Leen W]

I had e well working SCCM 2016 environment but the host on which this VM ran, crashed.
I 'm now in the process of setting up a new site, removed the entries in AD that were referring to the old site and tried to install the clients again.
Neither push installation (SCCM db populated through AD discovery) nor running ccmsetup locally seems to work.
What does work, is changing on the client the sitecode and than run the machine and user policy cycle.
However, having moren than 300 devices on my network in different building, I would like to have a more automated way of doing this.

Running the script (that I found her) and distribute it as a package is not an option, since my old SCCM doesn 't exist anymore.

Thanks.

 

[Prajwal Desai]

Neither push installation (SCCM db populated through AD discovery) nor running ccmsetup locally seems to work. - Why is this not working with new SCCM setup ?. Did you examine log files for troubleshooting ?.

Changing the site code of the client agent should work fine. If you have a backup of VM, you can restore it.

 

[Leen W]

changing the site code manually on all PCs ? That is an enormous task.
which log file do I have to look in and where is it located ?

 

[Prajwal Desai]

https://prajwaldesai.com/change-site-code-of-configuration-manager-client/

 

[Leen W]

This is not a solution for me.
I had to install an entire new site database, which I populated through AD discovery., but it says in my database "no client". So I cannot send packages.
On the client side however, the client is still referring to the old site code and primary site server, which of course it cannot find anymore.
Pushing the client does not work either.

 

[Edy]

This is not a solution for me.
I had to install an entire new site database, which I populated through AD discovery., but it says in my database "no client". So I cannot send packages.
On the client side however, the client is still referring to the old site code and primary site server, which of course it cannot find anymore.
Pushing the client does not work either.

Use group policy to run a script to change the site code to the new one. Script

 

[Youssef Saad]

You can use Group Policy to change the site code in your clients machine, but you need to import the ConfigMgr ADMX template on your domain policies.