You need to ensure that you can transfer objects from Configuration Manager 2007 to Configuration Manager 2012

Your network contains a single Active Directory forest named contoso.com. Contoso.com
contains three System Center 2012 Configuration Manager sites and one System Center
Configuration Manager 2007 site. You need to ensure that you can transfer objects from
Configuration Manager 2007 to Configuration Manager 2012. What should you do?

Your network contains a single Active Directory forest named contoso.com. Contoso.com
contains three System Center 2012 Configuration Manager sites and one System Center
Configuration Manager 2007 site. You need to ensure that you can transfer objects from
Configuration Manager 2007 to Configuration Manager 2012. What should you do?

A.
Assign the computer account of the Central Administration site server permission to the
Configuration Manager 2007 site. Assign the computer account of the Central
Administration site server permissions to the Microsoft SQL Server database instance.

B.
Extend the Active Directory schema and assign the Central Administration site server
permissions to the System\System Management container.

C.
Connect the Configuration Manager 2007 primary site as a child primary site of the
Configuration Manager 2012 primary site.

D.
Connect the Configuration Manager 2012 primary site as a child primary site of the
Configuration Manager 2007 primary site.

Explanation:
Assign the computer account of the Central Administration site server permission to the
Configuration Manger 2007 site.
Assign the computer account of the Central Administration site server permission to the
Microsoft SQL Server database instance.
http://technet.microsoft.com/en-us/library/gg712991.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.
http://technet.microsoft.com/en-us/library/gg681981.aspx Planning for Migration to System
Center 2012 Configuration Manager You must first install a System Center 2012
Configuration Manager hierarchy to be the destination hierarchy before you can migrate data
from a supported source hierarchy. After you install the destination hierarchy, configure the
management features and functions that you want to use in your destination hierarchy
before you start to migrate data. http://technet.microsoft.com/en-us/library/gg712313.aspx
Prerequisites for Migration in System Center 2012 Configuration Manager To migrate from a
supported source hierarchy, you must have access to each applicable Configuration
Manager source site, and permissions within the System Center 2012 Configuration
Manager destination site to configure and run migration operations. Required Configurations
for Migration Data Gathering To enable the destination site to gather data, you must
configure the following two source site access accounts for use with each source site:
* Source Site Account: This account is used to access the SMS Provider of the source site.
* For a Configuration Manager 2007 SP2 source site, this account requires Read
permission to all source site objects.
* For a System Center 2012 Configuration Manager source site, this account requires Read
permission to all source site objects, You grant this permission to the account by using rolebased administration.
* Source Site Database Account: This account is used to access the SQL Server database
of the source site and requires Read and Execute permissions to the source site database.
You can configure these accounts when you configure a new source hierarchy, data
gathering for an additional source site, or when you reconfigure the credentials for a source
site. These accounts can use a domain user account, or you can specify the computer
account of the top-level site of the destination hierarchy.
Security Note: If you use the Configuration Manager computer account for either access
account, ensure that this account is a member of the security group Distributed COM Users
in the domain where the source site resides.
When gathering data, the following network protocols and ports are used:
NetBIOS/SMB – 445 (TCP)
RPC (WMI) – 135 (TCP)
SQL Server – 1433 (TCP)



Leave a Reply 0

Your email address will not be published. Required fields are marked *