다음을 통해 공유

Resources on "How to move from ConfMgr 2007 to ConfMgr 2012"

  • 아티클

I am  attaching below some information and resources, on  the considerations and the way to move from ConfMgr 2007 to ConfMgr 2012...

Because of the design changes that were introduced in Microsoft System Center 2012 Configuration Manager, you cannot upgrade an existing Microsoft System Center Configuration Manager 2007 infrastructure to System Center 2012 Configuration Manager. However, you can migrate some or all of the supported data from a Configuration Manager 2007 site to a System Center 2012 Configuration Manager site. You can also migrate the data from a single Configuration Manager 2007 site to several different System Center 2012 Configuration Manager sites, or you can move data from multiple Configuration Manager 2007 sites to a single System Center 2012 Configuration Manager site.

Migration to System Center 2012 Configuration Manager
From <https://blogs.technet.com/b/server-cloud/archive/2012/03/27/migration-to-system-center-2012-configuration-manager.aspx>

But I thought in-place upgrades were not supported? That is true for the most part, but through the migration framework we have enabled the capability to perform this in-place upgrade for Distribution Points only and convert your migrated content.  The Distribution Point can reside on a Secondary Site and/or be a standalone site server. All types of Configuration Manager 2007 Distribution Points are capable of in-place upgrade, including Branch Distribution Points, Server Share Distribution Points, and traditional Distribution Points.  Distribution Points that resides on Primary sites are not eligible to be upgraded.  

How easy is it to create a Migration Distribution Point upgrade job?   First, you have to configure Migration. Basically, this means establishing a link between your top tier Configuration Manager 2012 site and top tier Configuration Manager 2007 site.  A data gathering process runs, collecting information from the Configuration Manager 2007 site, and copies it into the Configuration Manager 2012 site to be later used to create Migration jobs.  Once Migration has been configured, you enable Shared Distribution Points, a one-time action for source sites in the Configuration Manager 2007 hierarchy.  Migration is now configured and you can now create migration jobs to migrate objects. Choose a few objects and packages and create a migration job. You are now ready to perform a Migration Distribution Point upgrade job. 

What do you mean the Migration Distribution point job is orchestrated end to end?   Once you create the Migration Distribution Point upgrade job, monitor the status of the job in the Upgrade Distribution Point node of the console.  Configuration Manager 2012 performs the uninstall of the site role through Configuration Manager 2007, then installs the Configuration Manager 2012 Distribution Point, and finally converts all the migrated content.  The only action required is to create the Migration Distribution Point job. 

What special considerations or requirements should we be aware of?   Always check documentation first. The supported configurations for Configuration Manager 2012 Distribution Points are outlined in the documentation, and we only allow the upgrade for supported platforms.  Also be sure to remove the Configuration Manager 2007 agent from the Distribution Point, especially Branch Distribution Points, before creating the Migration Distribution Point upgrade job.  It is not supported to have a Configuration Manager 2012 site role being managed by a Configuration Manager 2007 client.

How can you learn more?   You can get a more detailed overview and step-by-step instructions on TechNet online library at Migrating Hierarchies in System Center 2012 Configuration Manager https://technet.microsoft.com/en-us/library/gg682006.aspx.

Is this really your favorite feature?   Yes, but I also love Package Conversion Manager (PCM) which can be used to convert classic software distributions into the new AppModel. At the end of the day, the hope for migration is to save you time while preserving your investment in Configuration Manager 2007.  This is core to the migration framework within Configuration Manager 2012, try it out. See you all at MMS!

Planning for Migration to System Center 2012 Configuration Manager

Additionally, you might have to plan for overlap between the source hierarchy and your destination hierarchy. As an example, consider when the source hierarchy is configured to use the same network locations or boundaries as your destination hierarchy and you then install new clients to your destination hierarchy and use automatic site assignment. In this scenario, because a newly installed Configuration Manager client can select a site to join from either hierarchy, the client could incorrectly assign to your source hierarchy. Therefore, plan to assign each new client in the destination hierarchy to a specific site in that hierarchy instead of using automatic-site assignment.

For more information about site assignments, see the Client Site Assignment Considerations section in the Interoperability between Different Versions of Configuration Manager topic. For more information about client site assignment for Configuration Manager 2007, see About Client Site Assignment in Configuration Manager in the Configuration Manager 2007 documentation library.

Planning Topics

Use the following topics to help you plan how to migrate a supported Configuration Manager hierarchy to System Center 2012 Configuration Manager or System Center 2012 R2 Configuration Manager:

From <https://technet.microsoft.com/en-us/library/gg681981.aspx>

Migrating Hierarchies in System Center 2012 Configuration Manager

Use the following topics to help you migrate Configuration Manager hierarchies:

From <https://technet.microsoft.com/en-us/library/gg682006.aspx>

Determine Whether to Migrate Configuration Manager 2007 to System Center 2012 Configuration Manager

 In Microsoft System Center 2012 Configuration Manager, the built-in migration functionality replaces in-place upgrades of existing Configuration Manager infrastructure by providing a process that transfers data from active Configuration Manager 2007 sites. The functionality provided by migration helps you maintain investments that you have made in configurations and deployments while you can take full advantage of core changes in the product introduced in System Center 2012 Configuration Manager. These changes include a simplified Configuration Manager hierarchy that uses fewer sites and resources, and the improved processing by use of native 64-bit code that runs on 64-bit hardware.

Migration can transfer most data from Configuration Manager 2007. If you do not migrate Configuration Manager 2007 to System Center 2012 Configuration Manager, or if you migrate data and want to maintain objects that migration does not migrate, you must re-create non-migrated objects in the new System Center 2012 Configuration Manager hierarchy.

Use the following sections to help you plan for data you can or cannot migrate to System Center 2012 Configuration Manager:

From <https://technet.microsoft.com/en-us/library/gg712991.aspx>

Planning a Content Deployment Migration Strategy in System Center 2012 Configuration Manager

While you are actively migrating data to a System Center 2012 Configuration Manager or System Center 2012 R2 Configuration Manager destination hierarchy, Configuration Manager clients in both hierarchies can maintain access to content that you deployed in the source hierarchy. Additionally, you can use migration to upgrade or reassign distribution points from the source hierarchy to become distribution points in the destination hierarchy. When you share and upgrade or reassign distribution points, this strategy can help you avoid having to redeploy content to new servers in the destination hierarchy for the clients that you migrate.

Although you can recreate and distribute content in the destination hierarchy, you can also use the following options to manage this content:

  • Share distribution points in the source hierarchy with clients in the destination hierarchy.
  • Upgrade stand-alone Configuration Manager 2007 distribution points or Configuration Manager 2007 secondary sites in the source hierarchy to become distribution points in the destination hierarchy.
  • Reassign distribution points from a System Center 2012 Configuration Manager or System Center 2012 R2 Configuration Manager source hierarchy to a site in the destination hierarchy.

From <https://technet.microsoft.com/en-us/library/4f4c9d45-37af-4540-b6c0-3f48ae55ae61>

 Administrator Checklists for Migration Planning in System Center 2012 Configuration Manager

Use the following administrator checklists to help you plan your migration strategy to Microsoft System Center 2012 Configuration Manager:

From <https://technet.microsoft.com/en-us/library/gg712683.aspx>

Configuring Source Hierarchies and Source Sites for Migration to System Center 2012 Configuration Manager

To enable migration of data to your System Center 2012 Configuration Manager environment, you must configure a supported Configuration Manager source hierarchy and one or more source sites in that hierarchy that contain data that you want to migrate.

Note

Operations for migration are run at the top-level site in the destination hierarchy. If you configure migration when you use a Configuration Manager console that is connected to a primary child site, you must allow time for the configuration to replicate to the central administration site, to start, and to then replicate status back to the primary site to which you are connected.

Use the information and procedures in the following sections to specify the source hierarchy and to add additional source sites. After you complete these procedures, you can create migration jobs and start to migrate data from the source hierarchy to the destination hierarchy.

From <https://technet.microsoft.com/en-us/library/gg712307.aspx>

 A nice video also covering the: Migration Best Practices from System Center Configuration Manager 2007 to 2012  https://channel9.msdn.com/Events/MMS/2013/UD-B404