Installing new SCCM 2012 infrastructure over an existing SCCM 2012 Infrastructure

Greetings,

I currently have a standalone SCCM 2012 environment running in production.  This implementation isn't in a hierarchy and doesn't support Macs (non-PKI/HTTPS infrastructure), but is managing 1500 PC clients beautifully.

However, we have some sites out-of-state that need to be in their own Primary Site, as well as Macs across both sites need managing as well.  

I have made a new environment entirely on 2012 infrastructure (2012 SCCM, 2012 Server, and 2012 SQL).  This includes a CAS at the top, a PRI for my current site, and SQL for both (all on different hardware, new names, etc.).  I've installed a PKI infrastructure, and it's currently working fine managing the three servers it contains.

I need to start migrating all of the clients and services to the 'new' SCCM implementation, but pushing the SCCM client installs to over the old SCCM doesn't seem to change any settings.  Nor does changing site settings in the control panel of a client.

Anyone know how to configure new site settings without re-installing the SCCM clients on the 'old' infrastructure?

Thanks~

May 5th, 2014 5:47pm

However, we have some sites out-of-state that need to be in their own Primary Site, as well as Macs across both sites need managing as well.  


Why? Why do they need own  primaries?
Free Windows Admin Tool Kit Click here and download it now
May 6th, 2014 1:42am

I agree with Torsten, but you obviously had your reasons. I'd not have gone with a CAS though in this case, unless there are more than 100.000 clients at one Primary Site, some really tricky network routing issues etc.

In your case you'd have to re-assign the clients from the old environment to your new, and by doing so you need to re-install the client.

Grab the files in <ConfigMgr installation location>\Client and create a package of those in the old environment. Deploy this package to your client where you specify the SMSSITECODE=<site_code> and SMSMP property. I'd trial run some clients first and check the ccmsetup.log to see if the clients actual did migrate to your new environment.

Regards,

May 6th, 2014 1:51am

Have you ever used group policy for site assignment? This caught me out when upgrading to a new site code. If it has ever been used, it brands the registry and no amount of tinkering in the configuration manager console or client installation methods could fix it.

To fix our site, I removed the offending GPO settings and set the 'GPRequestedSiteAssignmentCode', 'GPSiteAssignmentRetryDuration(Hours)' and 'GPSiteAssignmentRetryInterval(Min)' items under 'HKLM\Software\Microsoft\SMS\Mobile Client' to delete via GPP.

Details and symptoms I found at http://blog.coretech.dk/heh/new-agents-will-not-re-assign-to-configmgr-2012-site/.


  • Edited by Jilhad 5 hours 29 minutes ago
Free Windows Admin Tool Kit Click here and download it now
May 6th, 2014 2:03am

In your case you'd have to re-assign the clients from the old environment to your new, and by doing so you need to re-install the client.

There's no need to reinstall the client if you just want to assign it to another site. It can easily done by script: http://msdn.microsoft.com/en-us/library/cc146558.aspx
May 6th, 2014 2:23am

It can easily done by script: http://msdn.microsoft.com/en-us/library/cc146558.aspx

Hope, this script supports CM 2012 as well !
Free Windows Admin Tool Kit Click here and download it now
May 6th, 2014 2:42am

Hope, this script supports CM 2012 as well


Yes it does.
May 6th, 2014 3:04am

Interresting, havn't seen that one before. Thanks!
Free Windows Admin Tool Kit Click here and download it now
May 6th, 2014 3:04am

Have you ever used group policy for site assignment? This caught me out when upgrading to a new site code. If it has ever been used, it brands the registry and no amount of tinkering in the configuration manager console or client installation methods could fix it.

To fix our site, I removed the offending GPO settings and set the 'GPRequestedSiteAssignmentCode', 'GPSiteAssignmentRetryDuration(Hours)' and 'GPSiteAssignmentRetryInterval(Min)' items under 'HKLM\Software\Microsoft\SMS\Mobile Client' to delete via GPP.

Details and symptoms I found at http://blog.coretech.dk/heh/new-agents-will-not-re-assign-to-configmgr-2012-site/.


  • Edited by Jilhad Tuesday, May 06, 2014 5:58 AM
  • Marked as answer by Robbles2000 20 hours 55 minutes ago
May 6th, 2014 8:58am

Have you ever used group policy for site assignment? This caught me out when upgrading to a new site code. If it has ever been used, it brands the registry and no amount of tinkering in the configuration manager console or client installation methods could fix it.

To fix our site, I removed the offending GPO settings and set the 'GPRequestedSiteAssignmentCode', 'GPSiteAssignmentRetryDuration(Hours)' and 'GPSiteAssignmentRetryInterval(Min)' items under 'HKLM\Software\Microsoft\SMS\Mobile Client' to delete via GPP.

Details and symptoms I found at http://blog.coretech.dk/heh/new-agents-will-not-re-assign-to-configmgr-2012-site/.


Jilhad,

Looks like most of the machines I was testing were indeed installed via GP before I was able to install via the console.  

Deleting those registry keys allowed me to push the install over the old environment using 'Install Client' from the 'Devices' console, specifying to re-install client.

Now, I just have to figure out a script to remove those keys via SCCM

***Most of you were wondering why I was installing a CAS environment, it's really because this site doesn't conform all that well to our policies, and they will ultimately be administering their own environment.  It seemed to me that it would be easier for me to delegate control/permissions/data using a hierarchy.  It was a tough decision, ***

Thank you all for your help!

Free Windows Admin Tool Kit Click here and download it now
May 7th, 2014 10:17am

***Most of you were wondering why I was installing a CAS environment, it's really because this site doesn't conform all that well to our policies, and they will ultimately be administering their own environment.  It seemed to me that it would be easier for me to delegate control/permissions/data using a hierarchy.  It was a tough decision, ***

Using a CAS does *not* change anything when it comes to permissions. There's *no* difference between a CAS (+ multiple primaries) compared to a standalone primary when it comes to RBA (role based access).
May 7th, 2014 12:21pm

Glad I could help Robbles2000.

To delete the settings in our environment, I used a group policy object and used the group policy preferences registry settings to delete those keys if they existed.

For more information: http://technet.microsoft.com/en-us/library/cc753092.aspx

Free Windows Admin Tool Kit Click here and download it now
May 7th, 2014 7:21pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics