It is supported to install and operate multiple, independent hierarchies of System Center 2012 Configuration Manager on the same network. However, because different hierarchies of Configuration Manager do not interoperate outside of migration, each hierarchy requires configurations to prevent conflicts between them. Additionally, you can make certain configurations to help resources that you manage to interact with the site systems from the correct hierarchy.

The following sections provide information about using different versions of Configuration Manager on the same network.

Interoperability between System Center 2012 Configuration Manager and Configuration Manager 2007

A System Center 2012 Configuration Manager site or hierarchy cannot interoperate with a Configuration Manager 2007 site or hierarchy. A Configuration Manager 2007 site cannot report to a System Center 2012 Configuration Manager parent site, and you cannot upgrade a Configuration Manager 2007 site to a System Center 2012 Configuration Manager site. Instead of an in-place upgrade, you use System Center 2012 Configuration Manager migration to migrate your Configuration Manager 2007 SP2 objects and data to System Center 2012 Configuration Manager. For information about migrating from Configuration Manager 2007 SP2 to System Center 2012 Configuration Manager, see Migrating Hierarchies in System Center 2012 Configuration Manager.

Because you can deploy a System Center 2012 Configuration Manager site or hierarchy side-by-side with a Configuration Manager 2007 site or hierarchy, take action to prevent clients from either version from trying to join a site from the other Configuration Manager version. For example, if your Configuration Manager hierarchies have overlapping boundaries, including the same network locations, you might assign each new client to a specific site instead of using automatic site assignment. For information about automatic site assignment in System Center 2012 Configuration Manager, see How to Assign Clients to a Site in Configuration Manager. Additionally, it is not supported to install a client from Configuration Manager 2007 on a computer that hosts a site system role from System Center 2012 Configuration Manager, nor to install a System Center 2012 Configuration Manager client on a computer that hosts a site system role from Configuration Manager 2007.

System Center 2012 Configuration Manager supports only System Center 2012 Configuration Manager device and mobile device clients. The following clients and the following Virtual Private Network (VPN) connection are not supported:

  • Any Configuration Manager 2007 or earlier computer client version

  • Any Configuration Manager 2007 or earlier device management client

  • Windows CE Platform Builder device management client (any version)

  • System Center Mobile Device Manager VPN connection

Client Site Assignment Considerations

Interoperability between Sites with Different Service Pack Versions in System Center 2012 Configuration Manager

System Center 2012 Configuration Manager requires that each site in a hierarchy be of the same service pack level. However, while you are actively upgrading a hierarchy to a new service pack, different sites in the hierarchy upgrade at different times. Therefore, to support the upgrade process, Configuration Manager supports limited interactions between different service pack versions in a single hierarchy.

Limitations to Configuration Manager Capabilities in a Mixed-Version Hierarchy

See Also