Explore topic-wise InterviewSolutions in .

No. Windows RT and Windows Phone 8 includes a management client that Configuration Manager uses, and Configuration Manager MANAGES mobile DEVICES that run IOS by directly CALLING APIs.

No. Windows RT and Windows Phone 8 includes a management client that Configuration Manager uses, and Configuration Manager manages mobile devices that run iOS by directly calling APIs.

No. ALTHOUGH the MICROSOFT Intune CONNECTOR uses PKI certificates, Microsoft Intune automatically requests and installs these certificates for you.

No. Although the Microsoft Intune connector uses PKI certificates, Microsoft Intune automatically requests and installs these certificates for you.

Yes. You require specific application certificates before USERS can install applications on Windows RT, Windows PHONE 8, and IOS. You do not require certificates to MAKE applications available to mobile devices that run Android.

Yes. You require specific application certificates before users can install applications on Windows RT, Windows Phone 8, and iOS. You do not require certificates to make applications available to mobile devices that run Android.

YES. You MUST specify a WORK or school account before you can install the Microsoft Intune connector in CONFIGURATION Manager SP1.

Yes. You must specify a work or school account before you can install the Microsoft Intune connector in Configuration Manager SP1.

YES, if you only want to find mobile devices and retrieve inventory DATA from them as a read-only mode of OPERATION, you can do this by granting a subset of the CMDLETS that the account uses to connect to the Exchange Client Access server.

The required cmdlets for a read-only mode of operation are as FOLLOWS:

• Get-ActiveSyncDevice
• Get-ActiveSyncDeviceStatistics
• Get-ActiveSyncOrganizationSettings
• Get-ActiveSyncMailboxPolicy
• Get-ExchangeServer
• Get-Recipient
• Set-ADServerSettings

Yes, if you only want to find mobile devices and retrieve inventory data from them as a read-only mode of operation, you can do this by granting a subset of the cmdlets that the account uses to connect to the Exchange Client Access server.

The required cmdlets for a read-only mode of operation are as follows:

No. In this dual management scenario, Configuration MANAGER SENDS the wipe command in the client policy and by using the Exchange Server connector, and then monitors the wipe status for the mobile DEVICE. As soon as Configuration Manager receives a wipe confirmation from the mobile device, it cancels the second and pending wipe command so that the mobile device is not wiped TWICE.

No. In this dual management scenario, Configuration Manager sends the wipe command in the client policy and by using the Exchange Server connector, and then monitors the wipe status for the mobile device. As soon as Configuration Manager receives a wipe confirmation from the mobile device, it cancels the second and pending wipe command so that the mobile device is not wiped twice.

To better support VIRTUAL desktop infrastructure (VDI) environments and large-scale client deployments, System CENTER 2012 Configuration Manager has a RANDOMIZATION delay for SCHEDULED activities. This means that for scheduled activities, clients are unlikely to run the ACTION at the exact time that you configure. In Configuration Manager SP1 only, you can use client settings to enable or disable the randomization delay for required software updates and required applications. By default, this setting is disabled.

To better support virtual desktop infrastructure (VDI) environments and large-scale client deployments, System Center 2012 Configuration Manager has a randomization delay for scheduled activities. This means that for scheduled activities, clients are unlikely to run the action at the exact time that you configure. In Configuration Manager SP1 only, you can use client settings to enable or disable the randomization delay for required software updates and required applications. By default, this setting is disabled.

A manager computer for the sleeping computer’s subnet responds to the first connection attempt and wakes up the sleeping computer, which then CONTACTS the NETWORK switch. After the computer is awake and the network switch is updated, subsequent connection attempts will successfully connect to the DESTINATION computer. Most TCP connections automatically retry and you will not see that the first connection (and possibly additional connections) time out. For Remote Desktop connections, however, you are more likely to see an initial failed connection and must manually retry. For computers that must come out of hibernation, you will probably experience a longer delay than for computers that are in other sleep STATES.

A manager computer for the sleeping computer’s subnet responds to the first connection attempt and wakes up the sleeping computer, which then contacts the network switch. After the computer is awake and the network switch is updated, subsequent connection attempts will successfully connect to the destination computer. Most TCP connections automatically retry and you will not see that the first connection (and possibly additional connections) time out. For Remote Desktop connections, however, you are more likely to see an initial failed connection and must manually retry. For computers that must come out of hibernation, you will probably experience a longer delay than for computers that are in other sleep states.

If you have enabled the wake-up PROXY client SETTING on CONFIGURATION Manager SP1 clients, and then disable it, the Confirmer Wake-up Proxy service is removed from clients.

If you have enabled the wake-up proxy client setting on Configuration Manager SP1 clients, and then disable it, the Confirmer Wake-up Proxy service is removed from clients.

Yes. Wake-up PROXY in Configuration Manager SP1 has its own client SERVICE NAMED Confirmer Wake-up Proxy that RUNS SEPARATELY from the SMS Agent Host (CCMExec.exe). This service is installed when a client is configured for wake-up proxy and then new client checks make sure that this wake-up proxy service is running and that the startup type is automatic.

Yes. Wake-up proxy in Configuration Manager SP1 has its own client service named Confirmer Wake-up Proxy that runs separately from the SMS Agent Host (CCMExec.exe). This service is installed when a client is configured for wake-up proxy and then new client checks make sure that this wake-up proxy service is running and that the startup type is automatic.

There is no report in System Center 2012 Configuration Manager that displays which collections of COMPUTERS have a power plan applied. However, in the DEVICE Collections list, you can SELECT the Power Configurations column to display whether a collection has a power plan applied.

There is no report in System Center 2012 Configuration Manager that displays which collections of computers have a power plan applied. However, in the Device Collections list, you can select the Power Configurations column to display whether a collection has a power plan applied.

Yes, although you do not need Windows Server 2012 R2 for the certificate registration point, you do need this OPERATING system version (or later) to install the Configuration Manager Policy Module on the server that runs the Network Device Enrollment Service.

Before this version of the operating system, the Network Device Enrollment Service was designed for secured intranet environments only, to accept interactive computer certificate requests for network equipment such as ROUTERS. Changes in Windows Server 2012 R2 now accommodate user certificates as well as computer certificates, and the new support for a policy module makes this SOLUTION scalable for an enterprise environment. In addition, the increased security now supports running this service in a perimeter network (also known as a DMZ), which is IMPORTANT for devices that you manage on the Internet, such as IOS and Android devices.

Yes, although you do not need Windows Server 2012 R2 for the certificate registration point, you do need this operating system version (or later) to install the Configuration Manager Policy Module on the server that runs the Network Device Enrollment Service.

Before this version of the operating system, the Network Device Enrollment Service was designed for secured intranet environments only, to accept interactive computer certificate requests for network equipment such as routers. Changes in Windows Server 2012 R2 now accommodate user certificates as well as computer certificates, and the new support for a policy module makes this solution scalable for an enterprise environment. In addition, the increased security now supports running this service in a perimeter network (also known as a DMZ), which is important for devices that you manage on the Internet, such as iOS and Android devices.

YES, you are limited to three certificate templates per hierarchy and each of these certificate templates are restricted to the three key usages that the Network Device Enrollment SERVICE supports: signing, encryption, and both signing and encryption. So, for example, you couldn’t use two certificate templates that supported both signing and encryption.

Although different servers running the Network Device Enrollment Service can be configured to use different certificate templates, Configuration Manager cannot support this configuration because you cannot assign clients to specific servers. If you have multiple certificate registration point site system servers in the hierarchy that communicate with multiple servers running the Network Device Enrollment Service, Configuration Manager non-deterministically assigns clients to the AVAILABLE servers to automatically load balance the REQUESTS.

Yes, you are limited to three certificate templates per hierarchy and each of these certificate templates are restricted to the three key usages that the Network Device Enrollment Service supports: signing, encryption, and both signing and encryption. So, for example, you couldn’t use two certificate templates that supported both signing and encryption.

Although different servers running the Network Device Enrollment Service can be configured to use different certificate templates, Configuration Manager cannot support this configuration because you cannot assign clients to specific servers. If you have multiple certificate registration point site system servers in the hierarchy that communicate with multiple servers running the Network Device Enrollment Service, Configuration Manager non-deterministically assigns clients to the available servers to automatically load balance the requests.

AMT-based computers that were provisioned with Configuration Manager 2007 must have their provisioning data removed before you migrate them to System Center 2012 Configuration Manager, and then provisioned again by System Center 2012 Configuration Manager. Because of functional CHANGES between the versions, the security group, OU, and web server certificate template have different requirements:

• If you used a security group in Configuration Manager 2007 for 802.1X authentication, you can continue to use this group if it is a universal security group. If it is not a universal group, you must CONVERT it or create a new universal security group for System Center 2012 Configuration Manager. The security permissions of Read Members and Write Members for the site server computer account REMAIN the same.
• The OU can be used without modification. However, System Center 2012 Configuration Manager no longer requires Full Control to this object and all child objects. You can reduce these permissions to Create Computer Objects and Delete Computer Objects on this object only.
• The web server certificate template from Configuration Manager 2007 cannot be used in System Center 2012 Configuration Manager without modification. This certificate template no longer uses Supply in the request and the site server computer account no longer requires Read and Enroll permissions.

AMT-based computers that were provisioned with Configuration Manager 2007 must have their provisioning data removed before you migrate them to System Center 2012 Configuration Manager, and then provisioned again by System Center 2012 Configuration Manager. Because of functional changes between the versions, the security group, OU, and web server certificate template have different requirements:

You can MANAGE Intel vPro computers by using out of BAND MANAGEMENT in System Center 2012 Configuration MANAGER.

You can manage Intel vPro computers by using out of band management in System Center 2012 Configuration Manager.

Probably. You can reduce the disk space REQUIRED to install the CONFIGURATION Manager client by using customized settings, such as excluding INSTALLATION files that the client does not require and specifying the client CACHE to be smaller than the DEFAULT size.

Probably. You can reduce the disk space required to install the Configuration Manager client by using customized settings, such as excluding installation files that the client does not require and specifying the client cache to be smaller than the default size.

Direct Access is a Windows solution for managing domain computers when they move from the intranet to the Internet. This solution requires the minimum operating systems of Windows Server 2008 R2 and Windows 7 on clients. Internet-based client management is specific to Configuration Manager, and it allows you to manage computers and MOBILE devices when they are on the Internet. The Configuration Manager clients can be on workgroup computers and never connect to the intranet, and they can also be mobile devices. The Configuration Manager solution works for all operating system versions that are supported by Configuration Manager.

Unless you are using Windows Server 2012 with only Windows 8 clients for Direct Access, both solutions require PKI certificates on clients and servers. However, Direct Access requires a Microsoft enterprise certification authority, whereas Configuration Manager can use any PKI certificate that meets the requirements documented in PKI Certificate Requirements for Configuration Manager.

Not all Configuration Manager Features are supported for Internet-based client management. For more information, see the Planning for Internet-Based Client Management section in the Planning for Communications in Configuration Manager Topic. In COMPARISON, because a client that CONNECTS over Direct Access behaves as if it is on the intranet, all features, with the EXCEPTION of deploying an operating system, are supported by Configuration Manager.

Direct Access is a Windows solution for managing domain computers when they move from the intranet to the Internet. This solution requires the minimum operating systems of Windows Server 2008 R2 and Windows 7 on clients. Internet-based client management is specific to Configuration Manager, and it allows you to manage computers and mobile devices when they are on the Internet. The Configuration Manager clients can be on workgroup computers and never connect to the intranet, and they can also be mobile devices. The Configuration Manager solution works for all operating system versions that are supported by Configuration Manager.

Unless you are using Windows Server 2012 with only Windows 8 clients for Direct Access, both solutions require PKI certificates on clients and servers. However, Direct Access requires a Microsoft enterprise certification authority, whereas Configuration Manager can use any PKI certificate that meets the requirements documented in PKI Certificate Requirements for Configuration Manager.

Not all Configuration Manager Features are supported for Internet-based client management. For more information, see the Planning for Internet-Based Client Management section in the Planning for Communications in Configuration Manager Topic. In comparison, because a client that connects over Direct Access behaves as if it is on the intranet, all features, with the exception of deploying an operating system, are supported by Configuration Manager.

Configuration Manager contains MANY improvements since Configuration Manager 2007 to help you manage clients when they are on the Internet:

• Configuration Manager supports a gradual transition to using PKI CERTIFICATES, and not all clients and site systems have to use PKI certificates before you can manage clients on the Internet.
• The certificate selection process that Configuration Manager USES is improved by using a certificate issuers list.
• ALTHOUGH deploying an operating system is STILL not supported over the Internet, you can deploy generic task sequences for clients that are on the Internet.
• If the Internet-based management point can authenticate the user, user policies are not supported when clients are on the Internet. This functionality supports user-centric management and user device affinity for when you deploy applications to users.
• Configuration Manager Internet-based clients on the Internet first try to download any required software updates from Microsoft Update, rather than from an Internet-based distribution point in their assigned site. Only if this fails, will they then try to download the required software updates from an Internet-based distribution point.

Configuration Manager contains many improvements since Configuration Manager 2007 to help you manage clients when they are on the Internet:

Review the checks that CLIENT health makes in the section monitoring the STATUS of Client Computers in Configuration Manager in the topic Introduction to Client Deployment in Configuration Manager. You can use compliance settings in Configuration Manager to check for ADDITIONAL items that you consider required for the health of your clients. For example, you might check for SPECIFIC registry key entries, files, and PERMISSIONS.

Review the checks that client health makes in the section monitoring the Status of Client Computers in Configuration Manager in the topic Introduction to Client Deployment in Configuration Manager. You can use compliance settings in Configuration Manager to check for additional items that you consider required for the health of your clients. For example, you might check for specific registry key entries, files, and permissions.

YES, client status is new in System Center 2012 Configuration Manager and ALLOWS you to monitor the activity of CLIENTS and check and remediate various problems that can OCCUR.

Yes, client status is new in System Center 2012 Configuration Manager and allows you to monitor the activity of clients and check and remediate various problems that can occur.

A client’s assigned site is the primary site that creates the client policy to manage the device. Clients are always assigned to primary sites, even if they roam into another primary site or reside within the boundaries of a secondary site. The client’s installed site REFERS to the site that sent the client the client installation FILES to run CCMSetup.exe. For example, if you used the Client Push Installation Wizard, you can specify INSTALL the client software from a specified site and select any site in the hierarchy. The resident site refers to the site that owns the boundaries that the client CURRENTLY resides in. For example, this might be a secondary site of the client’s primary site. Or, it might be another primary site if the client is ROAMING and temporarily connected to a network that belongs to another site in the hierarchy.

A client’s assigned site is the primary site that creates the client policy to manage the device. Clients are always assigned to primary sites, even if they roam into another primary site or reside within the boundaries of a secondary site. The client’s installed site refers to the site that sent the client the client installation files to run CCMSetup.exe. For example, if you used the Client Push Installation Wizard, you can specify Install the client software from a specified site and select any site in the hierarchy. The resident site refers to the site that owns the boundaries that the client currently resides in. For example, this might be a secondary site of the client’s primary site. Or, it might be another primary site if the client is roaming and temporarily connected to a network that belongs to another site in the hierarchy.

For information about supporting clients for a VIRTUAL desktop infrastructure (VDI), SEE the CONSIDERATIONS for Managing the Configuration Manager CLIENT in a Virtual Desktop Infrastructure (VDI) section in the Introduction to Client Deployment in Configuration Manager Topic.

For information about supporting clients for a virtual desktop infrastructure (VDI), see the Considerations for Managing the Configuration Manager Client in a Virtual Desktop Infrastructure (VDI) section in the Introduction to Client Deployment in Configuration Manager Topic.

The TERM “device” in SYSTEM Center 2012 Configuration Manager applies to a computer or a MOBILE device such as a Windows Mobile PHONE.

The term “device” in System Center 2012 Configuration Manager applies to a computer or a mobile device such as a Windows Mobile Phone.

When you create a PACKAGE and program to upgrade Configuration Manager Clients, this installation method is designed to upgrade EXISTING System Center 2012 Configuration Manager clients. You can control which distribution points hosts the package and the client computers that install the package. This installation method supports only System Center 2012 Configuration Manager clients and cannot upgrade Configuration Manager 2007 clients.

In comparison, the automatic client upgrade method AUTOMATICALLY creates the client upgrade package and program and this installation method can be used with Configuration Manager 2007 clients as well as System Center 2012 Configuration Manager Clients. The package is automatically distributed to all distribution points in the hierarchy and the deployment is sent to all clients in the hierarchy for evaluation. This installation method supports System Center 2012 Configuration Manager clients and Configuration Manager 2007 clients that are assigned to a System Center 2012 Configuration Manager site. Because you cannot restrict which distribution points are sent the upgrade package or which clients are sent the deployment, use automatic client upgrade with caution and do not use it as your main method to deploy the client software.

When you create a package and program to upgrade Configuration Manager Clients, this installation method is designed to upgrade existing System Center 2012 Configuration Manager clients. You can control which distribution points hosts the package and the client computers that install the package. This installation method supports only System Center 2012 Configuration Manager clients and cannot upgrade Configuration Manager 2007 clients.

In comparison, the automatic client upgrade method automatically creates the client upgrade package and program and this installation method can be used with Configuration Manager 2007 clients as well as System Center 2012 Configuration Manager Clients. The package is automatically distributed to all distribution points in the hierarchy and the deployment is sent to all clients in the hierarchy for evaluation. This installation method supports System Center 2012 Configuration Manager clients and Configuration Manager 2007 clients that are assigned to a System Center 2012 Configuration Manager site. Because you cannot restrict which distribution points are sent the upgrade package or which clients are sent the deployment, use automatic client upgrade with caution and do not use it as your main method to deploy the client software.

To install a CONFIGURATION Manager client by using the Client Push Installation WIZARD, the ADMINISTRATIVE user MUST have at least the Modify resource permission.

To install a Configuration Manager client by using the Client Push Installation Wizard, the administrative user must have at least the Modify resource permission.

YES. System Center 2012 Configuration Manager SUPPORTS the same client installation methods that Configuration Manager 2007 supports: client push, software update-based, group POLICY, manual, logon SCRIPT, and image-based.

Yes. System Center 2012 Configuration Manager supports the same client installation methods that Configuration Manager 2007 supports: client push, software update-based, group policy, manual, logon script, and image-based.

No, ALTHOUGH you can configure role-based administration and security scopes so that ADMINISTRATIVE users can distribute content to selected DISTRIBUTION points only, Configuration Manager always displays all distribution points in the MONITORING workspace.

No, although you can configure role-based administration and security scopes so that administrative users can distribute content to selected distribution points only, Configuration Manager always displays all distribution points in the Monitoring workspace.

Run the REPORT Security for a specific or multiple Configuration MANAGER Objects to FIND the object types that can be assigned to security roles. Additionally you can view the list of objects for a security role by viewing the security roles Properties and selecting the PERMISSIONS tab.

Run the report Security for a specific or multiple Configuration Manager Objects to find the object types that can be assigned to security roles. Additionally you can view the list of objects for a security role by viewing the security roles Properties and selecting the Permissions tab.

Role-based administration does not support an explicit deny action on security roles, security scopes, or collections assigned to an ADMINISTRATIVE user. INSTEAD, configure security roles, security scopes, and collections to grant permissions to administrative users. If users do not have permissions to objects by use of these role-based administration elements, they MIGHT have only partial access to some objects, for example they might be able to view, but not MODIFY specific objects. However, you can use collection membership to EXCLUDE collections from a collection that is assigned to an administrative user.

Role-based administration does not support an explicit deny action on security roles, security scopes, or collections assigned to an administrative user. Instead, configure security roles, security scopes, and collections to grant permissions to administrative users. If users do not have permissions to objects by use of these role-based administration elements, they might have only partial access to some objects, for example they might be able to view, but not modify specific objects. However, you can use collection membership to exclude collections from a collection that is assigned to an administrative user.

As a best practice, SPECIFY a security GROUP RATHER than user accounts when you CONFIGURE administrative users for role-based administration.

As a best practice, specify a security group rather than user accounts when you configure administrative users for role-based administration.

Unlike Configuration Manager 2007, sites no LONGER provide a security boundary. Instead, use role-based administration security roles to configure the permissions different administrative users have, and security scopes and collections to define the set of objects they can view and manage. These settings can be configured at a CENTRAL administration SITE or any primary site and are enforced at all sites THROUGHOUT the hierarchy.

Unlike Configuration Manager 2007, sites no longer provide a security boundary. Instead, use role-based administration security roles to configure the permissions different administrative users have, and security scopes and collections to define the set of objects they can view and manage. These settings can be configured at a central administration site or any primary site and are enforced at all sites throughout the hierarchy.

If you install System Center 2012 Configuration Manager, there is no additional configuration because the Active DIRECTORY user account used to install Configuration Manager is automatically assigned to the Full Administrator security role, assigned to All Scopes, and has access to the All Systems and All USERS and User Groups collections. HOWEVER, if you want to provide full administrative permissions for other Active Directory users to access System Center 2012 Configuration Manager, CREATE new administrative users in Configuration Manager using their Windows accounts and then ASSIGN them to the Full Administrator security role.

If you install System Center 2012 Configuration Manager, there is no additional configuration because the Active Directory user account used to install Configuration Manager is automatically assigned to the Full Administrator security role, assigned to All Scopes, and has access to the All Systems and All Users and User Groups collections. However, if you want to provide full administrative permissions for other Active Directory users to access System Center 2012 Configuration Manager, create new administrative users in Configuration Manager using their Windows accounts and then assign them to the Full Administrator security role.

Because role-based administration is INTEGRATED into the CONFIGURATION of the hierarchy and management functions, there is no separate documentation section for role-based administration. Instead, information is integrated throughout the documentation library. For EXAMPLE, information about planning and configuring role-based administration is in the Planning for Security in Configuration Manager Topic and the Configuring Security for Configuration Manager Topic in the Site Administration for SYSTEM Center 2012 Configuration Manager Guide and the Security and Privacy for System Center 2012 Configuration Manager guide.

The Configuration Manager console lists the description of each role-based security role that is installed with Configuration Manager and the minimum permissions and a SUITABLE security role for each management function is included as a prerequisite in the relevant topic.

Because role-based administration is integrated into the configuration of the hierarchy and management functions, there is no separate documentation section for role-based administration. Instead, information is integrated throughout the documentation library. For example, information about planning and configuring role-based administration is in the Planning for Security in Configuration Manager Topic and the Configuring Security for Configuration Manager Topic in the Site Administration for System Center 2012 Configuration Manager Guide and the Security and Privacy for System Center 2012 Configuration Manager guide.

The Configuration Manager console lists the description of each role-based security role that is installed with Configuration Manager and the minimum permissions and a suitable security role for each management function is included as a prerequisite in the relevant topic.

Yes. When a COLLECTION migrates, Configuration Manager also migrates collection settings, which includes MAINTENANCE windows and collection VARIABLES. However, collection settings for AMT provisioning do not MIGRATE.

Yes. When a collection migrates, Configuration Manager also migrates collection settings, which includes maintenance windows and collection variables. However, collection settings for AMT provisioning do not migrate.

The list of objects you can MIGRATE depends on the version of your source hierarchy. You can migrate most objects from Configuration Manager 2007 to System Center 2012 Configuration Manager, including the FOLLOWING:

• Advertisements
• BOUNDARIES
• Collections
• Configuration baselines and configuration items
• Operating system deployment boot IMAGES, driver packages, drivers, images, and packages
• Software distribution packages
• Software metering rules
• Software updates deployment packages and templates
• Software update deployments
• Software update lists
• Task sequences
• Virtual application packages

When you migrate between System Center 2012 Configuration Manager Hierarchies, the list is similar, and includes objects that are only available in System Center 2012 Configuration Manager, such as Applications.

The list of objects you can migrate depends on the version of your source hierarchy. You can migrate most objects from Configuration Manager 2007 to System Center 2012 Configuration Manager, including the following:

When you migrate between System Center 2012 Configuration Manager Hierarchies, the list is similar, and includes objects that are only available in System Center 2012 Configuration Manager, such as Applications.

System Center 2012 CONFIGURATION MANAGER supports migrating a Configuration Manager 2007 ENVIRONMENT that is at a minimum of Service PACK 2.

System Center 2012 Configuration Manager supports migrating a Configuration Manager 2007 environment that is at a minimum of Service Pack 2.

You can migrate data from more than one source hierarchy, and the source hierarchies do not need to be the same version as each other. This means you can migrate from one or more Configuration Manager 2007 hierarchies, one or more System Center 2012 Configuration Manager hierarchies, and from one or more hierarchies that each run a different version of Configuration Manager. However, you can only migrate from one hierarchy at a time.

You can migrate the hierarchies in any order. However, you cannot migrate data from multiple hierarchies that use the same SITE code. If you try to migrate data from a site that USES the same site code as a migrated site, or that uses the same site code as a site in your destination hierarchy, this CORRUPTS the data in the System Center 2012 Configuration Manager database.

You can migrate data from more than one source hierarchy, and the source hierarchies do not need to be the same version as each other. This means you can migrate from one or more Configuration Manager 2007 hierarchies, one or more System Center 2012 Configuration Manager hierarchies, and from one or more hierarchies that each run a different version of Configuration Manager. However, you can only migrate from one hierarchy at a time.

You can migrate the hierarchies in any order. However, you cannot migrate data from multiple hierarchies that use the same site code. If you try to migrate data from a site that uses the same site code as a migrated site, or that uses the same site code as a site in your destination hierarchy, this corrupts the data in the System Center 2012 Configuration Manager database.

During the upgrade to a System Center 2012 Configuration MANAGER Distribution point, all migrated content is copied and then converted to the single INSTANCE store. When you MIGRATE to a hierarchy that RUNS System Center 2012 Configuration Manager with no service pack, the original Configuration Manager 2007 content remains on the server until it is MANUALLY removed. However, when you migrate to a hierarchy that runs System Center 2012 Configuration Manager SP1, the original Configuration Manager 2007 content is removed after the copy of the content is converted.

During the upgrade to a System Center 2012 Configuration Manager Distribution point, all migrated content is copied and then converted to the single instance store. When you migrate to a hierarchy that runs System Center 2012 Configuration Manager with no service pack, the original Configuration Manager 2007 content remains on the server until it is manually removed. However, when you migrate to a hierarchy that runs System Center 2012 Configuration Manager SP1, the original Configuration Manager 2007 content is removed after the copy of the content is converted.

You can PERFORM an in-place upgrade of a Configuration MANAGER 2007 secondary site to a SYSTEM Center 2012 Configuration Manager Distribution point. During the upgrade, all MIGRATED content is preserved.

You can perform an in-place upgrade of a Configuration Manager 2007 secondary site to a System Center 2012 Configuration Manager Distribution point. During the upgrade, all migrated content is preserved.

You can perform an in-place upgrade of a Configuration Manager 2007 DISTRIBUTION point that preserves all CONTENT during the upgrade. This includes an upgrade of a distribution point on a SERVER SHARE, a branch distribution point, or standard distribution point.

You can perform an in-place upgrade of a Configuration Manager 2007 distribution point that preserves all content during the upgrade. This includes an upgrade of a distribution point on a server share, a branch distribution point, or standard distribution point.

System Center 2012 Configuration Manager can upgrade supported distribution points from Configuration Manager 2007 source HIERARCHIES, and REASSIGN supported distribution points from System Center 2012 Configuration Manager Source hierarchies. When you upgrade or reassign a shared distribution point, the distribution point site system role and the distribution point computer are removed from the source hierarchy, and installed as a distribution point at a site you select in the destination hierarchy. This process ALLOWS you to MAINTAIN your existing distribution points with minimal effort or disruption to your network.

System Center 2012 Configuration Manager can upgrade supported distribution points from Configuration Manager 2007 source hierarchies, and reassign supported distribution points from System Center 2012 Configuration Manager Source hierarchies. When you upgrade or reassign a shared distribution point, the distribution point site system role and the distribution point computer are removed from the source hierarchy, and installed as a distribution point at a site you select in the destination hierarchy. This process allows you to maintain your existing distribution points with minimal effort or disruption to your network.

Shared distribution points are distribution points at sites in the source hierarchy that can be used by clients in the DESTINATION hierarchy during the migration period. A distribution point can be shared only when the source hierarchy that contains the distribution point REMAINS the ACTIVE source hierarchy and distribution point SHARING is enabled for the source site that contains the distribution point. Sharing distribution points ends when you complete migration from the source hierarchy.

Shared distribution points are distribution points at sites in the source hierarchy that can be used by clients in the destination hierarchy during the migration period. A distribution point can be shared only when the source hierarchy that contains the distribution point remains the active source hierarchy and distribution point sharing is enabled for the source site that contains the distribution point. Sharing distribution points ends when you complete migration from the source hierarchy.

When you assign a SITE in the destination hierarchy to own the content, you are selecting the site that maintains that content in the destination hierarchy. Because the site that owns the content is responsible for monitoring the source files for changes, PLAN to specify a site that is NEAR to the source file location on the network.

When you migrate content between a source and destination hierarchy, you are really migrating the METADATA about that content. The content itself might remain hosted on a SHARED distribution point during migration, or on a distribution point that you will upgrade or reassign to the destination hierarchy.

When you assign a site in the destination hierarchy to own the content, you are selecting the site that maintains that content in the destination hierarchy. Because the site that owns the content is responsible for monitoring the source files for changes, plan to specify a site that is near to the source file location on the network.

When you migrate content between a source and destination hierarchy, you are really migrating the metadata about that content. The content itself might remain hosted on a shared distribution point during migration, or on a distribution point that you will upgrade or reassign to the destination hierarchy.

This TYPE of information is easily recreated by an ACTIVE client when it sends data to its new site in the destination hierarchy. Typically, it is only the current information from each client that provides useful information. To retain access to historical inventory information you can keep a Configuration Manager 2007 or System CENTER 2012 Configuration Manager Source site active until the historical data is no LONGER REQUIRED.

This type of information is easily recreated by an active client when it sends data to its new site in the destination hierarchy. Typically, it is only the current information from each client that provides useful information. To retain access to historical inventory information you can keep a Configuration Manager 2007 or System Center 2012 Configuration Manager Source site active until the historical data is no longer required.

When you MIGRATE a CONFIGURATION Manager 2007 package to SYSTEM Center 2012 Configuration Manager, it remains a package after migration. If you want to deploy the software and packages that migrate from your Configuration Manager 2007 hierarchy by using the new APPLICATION model, you can use Microsoft System Center Configuration Manager Package Conversion Manager to convert them into System Center 2012 Configuration Manager Applications.

When you migrate a Configuration Manager 2007 package to System Center 2012 Configuration Manager, it remains a package after migration. If you want to deploy the software and packages that migrate from your Configuration Manager 2007 hierarchy by using the new application model, you can use Microsoft System Center Configuration Manager Package Conversion Manager to convert them into System Center 2012 Configuration Manager Applications.

Typically, you will migrate data from a Configuration Manager 2007 or System Center 2012 Configuration Manager Hierarchy (the source hierarchy) over a period of time that you DEFINE. During the period of migration, you can continue to use your source hierarchy to manage CLIENTS that have not migrated to your new System Center 2012 Configuration Manager hierarchy (the DESTINATION hierarchy). ADDITIONALLY if you UPDATE an object in the source hierarchy after you have migrated that object to your destination hierarchy, you can re-migrate that object again up until you decide to complete your migration.

Typically, you will migrate data from a Configuration Manager 2007 or System Center 2012 Configuration Manager Hierarchy (the source hierarchy) over a period of time that you define. During the period of migration, you can continue to use your source hierarchy to manage clients that have not migrated to your new System Center 2012 Configuration Manager hierarchy (the destination hierarchy). Additionally if you update an object in the source hierarchy after you have migrated that object to your destination hierarchy, you can re-migrate that object again up until you decide to complete your migration.

Several important changes introduced with System Center 2012 CONFIGURATION Manager prevent an in-place upgrade; however, System Center 2012 Configuration Manager does support migration from Configuration Manager 2007 with a side-by-side deployment. For example, System Center 2012 Configuration Manager is native 64 bit application with a database that is optimized for Unicode and that is shared between all sites. Additionally, site types and site relationships have changed. These changes, and others, mean that many existing HIERARCHY STRUCTURES cannot be upgraded.

Several important changes introduced with System Center 2012 Configuration Manager prevent an in-place upgrade; however, System Center 2012 Configuration Manager does support migration from Configuration Manager 2007 with a side-by-side deployment. For example, System Center 2012 Configuration Manager is native 64 bit application with a database that is optimized for Unicode and that is shared between all sites. Additionally, site types and site relationships have changed. These changes, and others, mean that many existing hierarchy structures cannot be upgraded.

No. The new functionality in Configuration MANAGER SP1 supports migration from an existing Configuration Manager SP1 HIERARCHY to another Configuration Manager SP1 hierarchy, in ADDITION to SUPPORTING migration from Configuration Manager 2007 SP2 to Configuration Manager SP1.

No. The new functionality in Configuration Manager SP1 supports migration from an existing Configuration Manager SP1 hierarchy to another Configuration Manager SP1 hierarchy, in addition to supporting migration from Configuration Manager 2007 SP2 to Configuration Manager SP1.

The VERSION of System Center 2012 CONFIGURATION Manager that you use to RUN migration determines the VERSIONS of Configuration Manager 2007 or System Center 2012 Configuration Manager that are supported for migration:

• When you use System Center 2012 Configuration Manager with no service pack, Configuration Manager 2007 sites with SP2 are supported for migration.
• When you use System Center 2012 Configuration Manager with SP1, Configuration Manager 2007 sites with SP2 and System Center 2012 Configuration Manager Sites with SP1 are supported for migration.

Configuration Manager Hierarchies that have data you want to migrate are called source hierarchies. The Configuration Manager HIERARCHY you are migrating data into, is called the destination hierarchy.

The version of System Center 2012 Configuration Manager that you use to run migration determines the versions of Configuration Manager 2007 or System Center 2012 Configuration Manager that are supported for migration:

Configuration Manager Hierarchies that have data you want to migrate are called source hierarchies. The Configuration Manager hierarchy you are migrating data into, is called the destination hierarchy.

CONFIGURATION Manager OFFERS a number of HIGH availability SOLUTIONS.

Configuration Manager offers a number of high availability solutions.