Forums on Intune, SCCM, and Windows 11

Welcome to the forums. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your topics and posts, as well as connect with other members through your own private inbox!

PENDING New Agent configuration on the machines

Messages
10
Reaction score
0
Points
1
Hi Prajwal,

As you know we have setup a new SCCM 2012 R2 1806 with Windows server 2016 STD on different domain,As we have trust relationship between the old(ABC) and new domain(XYZ) and the boundaries are also same, i am able to see all the machines in the Devices option in the configuration manager.
Now can i directly change the site code on the existing Client installed on the machine OR do i need to uninstall all the agents from the machines and install the new client on the machines.
Please help how should i approach as we have around 350 machines.
 
First, there is no product called SCCM 2012 R2 1806, since you called out 1806, you must have CMCB 1086.

Changing the site code is all that you need to do. A quick google search will reveal that there are many scripts that will help you with this task
 
Hi Garth,
Thanks for your response,sure i will search for the script to change the site code.One thing i need to know my old domain will be decommissioned will that impacted the new agents..which i will update by changing site code.
 
CM doesn't care about domains at all. So what exactly is your concern abut shutting down the domain?
 
Hi Garth,
Let me brief you our company has been acquired by new company so domain name has been changed,now we will be removing the old domain so i have asked you after changing the site code for the machines, they will now talk to the new SCCM server so is there any impact to the agents after decommissioning the domain.
 
Just to be clear, is SCCM within the Domain that the name is changing?

SCCM doesn't care about the domain BUT you might have some work to do about setting up Admin accounts if that changes and network access accounts if their domain changed too.

Honestly not many people do this, at best they generally move all PC from one domain to another, they don't rename the domain. So your back out plan is to create a new SCCM server after the domain change has happened.
 
Hi Garth,
As i have already told you i have created a new SCCM server in my new domain,i am not using the old SCCM server.As my Boundaries are same with same IP range i am able to see all my machines in the new SCCM server.
 
So there is no know issues. But renaming a domain is not something people test for.
 
Hi Garth,
As i have already told you i have created a new SCCM server in my new domain,i am not using the old SCCM server.As my Boundaries are same with same IP range i am able to see all my machines in the new SCCM server.
hi Suresh, if you have a new domain and have setup SCCM server over there, you can simply change site code of client agents and point the clients to talk to management point that is in new domain. The client agents will be upgraded because they are of old version. Setting up boundary and boundary group and associating the DP to the boundary group is critical.
 

Forum statistics

Threads
7,156
Messages
27,932
Members
18,237
Latest member
Causal
Back
Top