Pour les professionnels de l’informatique >
Forums - Accueil
>
Configuration Manager Setup/Deployment
>
Migration of SCCM and reassignment of clients
Migration of SCCM and reassignment of clients
- Hi,
I have a few questions about the migration process for SCCM.
Lets say we have site X (old SCCM ) and site Y (new SCCM). Site Y will be a fresh install of SCCM. Package/drivers etc will be copied to the new SCCM-server. When we decide to point the clients to the new site, what actions should be done?
I know that I neew to deactive site boundaries on the old SCCM server and activate them on the new one. Then I assume the clients will reassign themselves? Is that really it or is there anything else that I should do that I haven't thought about?
Regards,
Fredrik
Toutes les réponses
- Clients won't reassign automatically. It can be scripted: http://msdn.microsoft.com/en-us/library/cc146558.aspx. You might run into issues with the trusted root key (search the forums for 'resetkeyinformation').
You should also make sure that advertisements don't run twice (given that you created them from scratch), because the client in the new site is not aware what happened at the old site (eg: collection + advertisement for "All XP systems" that installs Software XYZ. If a client installed XYZ in the old site it will install XYZ in the new site again) Clients won't reassign automatically. It can be scripted: http://msdn.microsoft.com/en-us/library/cc146558.aspx. You might run into issues with the trusted root key (search the forums for 'resetkeyinformation').
You should also make sure that advertisements don't run twice (given that you created them from scratch), because the client in the new site is not aware what happened at the old site (eg: collection + advertisement for "All XP systems" that installs Software XYZ. If a client installed XYZ in the old site it will install XYZ in the new site again)
The script you pointed out seems to do the thing for me in this situation. Is it possible to script the resetkeyinformation as well or is it only offered via ccmsetup.exe? I guess I can make an MSI-package of the first script and distribute it via GPO when we are ready make the switch?
My action plan:
1. Copy applications, drivers, OS to our fresh install of SCCM
2. Create new TS. Create advertisements for TS and applications.
3. Make the old SCCM site a child site to our new SCCM site and let status information about clients replicate up in hierarchy (Would this solve the issue with the advertisements eventually running twice on the clients?)
4. Unplugg the child site and remove boundaries.
5. Remove "Publish information to Active Directory" in old site
6. Delete published information in Active Directory in the Systems Management container
5. Add boundaries in the new site
6. Run VB-script on all clients
Suggestions, comments on this plan?
Here is what I found in another thread: http://social.technet.microsoft.com/Forums/en-US/configmgrsetup/thread/d27c2185-4eb9-4d43-a0b4-9ee1363fa605
Here is the outcome of testing from the engineering team:
Moving a client to a new hierarchy will not work from the control panel app on the client or a script on the client regardless of AD extension.
The clients must be installed from the new site server using the 'Always install or upgrade' option in order to force the installation and the move to the new site.
They state that "Always install or upgrade" option should be used. What's you opionion on this? I saw that you participated in that discussion.
Regards,
Fredrik- Client Push is also a valid option to reassign the clients, correct?
- Yes.
