70-243 · Question #176
You have System Center 2012 R2 Configuration Manager installed on a production network and Configuration Manager Service Pack 1 (SP1) installed on a test network. You use the test network to test…
The correct answer is C. Use the Export Application option and the Import Application option. ConfigMgr's built-in Export and Import Application options are the most direct and low-effort method for transferring application objects between separate ConfigMgr hierarchies.
Question
You have System Center 2012 R2 Configuration Manager installed on a production network and Configuration Manager Service Pack 1 (SP1) installed on a test network. You use the test network to test the SP1 version of Configuration Manager before upgrading Configuration Manager on the production network. On the test network, you create several Configuration Manager applications. You need to make the applications on the test network available on the production network. The solution must minimize administrative effort. What should you do?
Options
- AInstall the production site server as aclient of the test site, and then deploy the applications to the
- BCreate a migration job.
- CUse the Export Application option and the Import Application option.
- DManually recreate the applications in the production environment.
How the community answered
(15 responses)- A7% (1)
- C80% (12)
- D13% (2)
Why each option
ConfigMgr's built-in Export and Import Application options are the most direct and low-effort method for transferring application objects between separate ConfigMgr hierarchies.
Installing the production site server as a client of the test site is not a supported or recognized mechanism for transferring application definitions between two separate ConfigMgr hierarchies.
ConfigMgr migration jobs are designed to migrate inventory, collections, and deployments from a ConfigMgr 2007 source hierarchy to a 2012 destination hierarchy - they involve substantial configuration overhead and are not intended for transferring specific application objects between two 2012 SP1 environments.
The Export Application option in ConfigMgr packages the application definition, deployment types, and dependencies into a .zip file that can be imported into any other ConfigMgr hierarchy using Import Application. This native feature requires no additional infrastructure setup and preserves application settings in a single operation, directly minimizing administrative effort when moving objects from a test to a production environment.
Manually recreating each application in the production environment requires the highest administrative effort of all options, directly contradicting the requirement to minimize effort.
Concept tested: ConfigMgr application export and import between hierarchies
Source: https://learn.microsoft.com/en-us/mem/configmgr/apps/deploy-use/export-import-applications
Topics
Community Discussion
No community discussion yet for this question.