Let's have a look at current situation first. The existing server is build on Windows Server 2008 R2, SQL Server 2008 R2 and ConfigMgr 2012 R2, where the Primary server installation is separated from SQL installation. You may upgrade SQL Server in-place with Microsoft support, but an in-place Windows Server upgrade is not supported. Therefore a new server with a current (2012 R2) server installation is needed. When using Windows Server 2012 an in-place upgrade to 2012 R2 is supported. Otherwise not!
When building a new server, and there's a need to use the existing ConfigMgr database, the computername, IP-address and partitions must be same. Because I want to change the name and partition both, recovery is not possible. Therefore I used a new server build on Windows Server 2012 R2, SQL Server 2014 SP1 and and ConfigMgr 1511. During installation a new Site code and name is requested. The existing name cannot be re-used.
After installation start the migration tools, and migrate all objects needed to the new server.
Update 28-12-2015: Within the Object migration task, collections can be selected as well. As asked by Conor O'Farrell within the comments, both deployments and collections can be migrated successfully. On my software package however the program was disabled after migration, without the possibility to enable it during migration. So yes, you can migrate all stuff needed from ConfigMgr 2012 R2 to 1511. Just great!
Sources used:
Backup and Recovery in Configuration Manager
How to move the ConfigMgr 2012 site database to a new SQL server
Supported configurations for System Center Configuration Manager
Planning a Migration Job Strategy in System Center 2012 Configuration Manager
Hi Henk
ReplyDeleteThanks for the useful information. I'm curios as to how you migrated the deployments etc, if you could not migrate the collections. Did you have to do all of these manually?
Thanks
Con
My pleasure. Will let you know soon.
DeleteA lot of scripting is needed if you want to migrate everything. I would not recommend this in a large environment just for the sake of having a different server name and partitions. The IP issue can be mitigated.
ReplyDeleteYou also have to think about the site name change and the GPO's required to enforce it if you migrate. This is the only controlled way to do it as far as I know.
My advice is to do an in place upgrade if possible.
If you want to change the machine or OS, back-up and do a site restore on the new machine keeping the same FQDN and partitions. I've upgraded from a 2008 site server CM 2012 to a 2012 R2 site server with CM 2012 R2 SP1 with minor issues.
I even moved the database on a separate server before doing the migration. It's a bit slower but if something crashes you have just one role to worry about not the whole damn SQL. Upgrading SQL versions is also easier this way.
In my environment with 32 domains, and about 15000 machines, 800 collections and hundreds of deployments I just can't spare the time to do a migration, for cosmetic reasons. But I would really want to change the site server name to match our naming convention sometime in the future so if you have some insights on how to do a full migration as painless as possible, please share your experience with us.
Thanks for this useful piece of information!
DeleteWhen migrating data, does the data from the source server get removed/deleted?
ReplyDeleteNope, there will be no data removed or get deleted.
DeleteI am also in the same situation. What if I upgrade SCCM 2012 R2 and SQL 2008 R2 in-place to SCCM 1511 and SQL 2014 respectively, then I will install SCCM 1511 and SQL 2014 on new server and migrate everything. If this is possible, could you please share me any good article to migrate data between SQLs?
ReplyDeleteOne of the new features in ConfigMgr 1602 is that in-place upgrade of the Server OS from 2008 R2 -> 2012 R2 is now supported. This will save a lot of time and money for many customers out there, great that it is finally supported!
DeleteHi,
ReplyDeleteI am migrating SCCM 2012 R2 SP1 to new hardware. I have already installed SQL 2014 and SCCM 1602 on new hardware. I am not doing the back/restore because I need minimum downtime. Now, if I use migration feature of SCCM 1602, it will not migrate SQL data. How can I migrate SQL db before running migration jobs?
Just use a backup of the SQL DB on the new server, as long as Site and Server config is same.
DeleteHi - please can you clarify this...
Delete'as long as Site and Server config is same.' if someone is using the 'migration' method then they have probably chosen a new SCCM Site (P01) name
Hi did you find a solution to migrate SQL DB / SUSDB ?
DeleteHi Henk, I tried the same method. But my deployments were not migrated along with collections. Now I have to migrate them manually.Any suggestions? Please
ReplyDeleteWhen using migration tools, is there something mentioned about this in overview before migrating?
DeleteWe have two boxes. Did the migration but deployments were not migrated along with collections. Have to migrate them manually. Any suggestions please..
ReplyDeleteOnly thing I remember you can choose for deployments if they must be active or not active after migration. Hope it helps!
DeleteWhen you did your migration, does the migration of a DP work as if it was SCCM 2007 to SCCM 1606 in respect that you still need to share the DP's and then upgrade?
ReplyDeleteDuring a migration from SCCM 2012 to CB do you still need to share your DP's and then Upgrade in the same way as a migration from 2007 to CB or is the process different?
ReplyDelete