The following example illustrates how to add the Application Migration step to an existing OS Deployment task sequence. Your own task sequence may differ, but the general positioning of these steps is where Install Application steps would normally be placed (after Install Updates and before the Restore User Files).
Choose Add > 1E OSD > AppMigration.
On the Properties tab, enter the following details:
SourceComputerName
.AppMig
.PkgMig
.Choose Add > Software > Install Application.
On the Properties tab:
AppMig
(see step 5 above).On the Options tab:
Choose Add→Software→Install Package.
On the Properties tab:
PkgMig
(see step 6 above).On the Options tab:
Role Based Application Sets can optionally be used in each of the deployment scenarios.
For this to work, the task sequence must contain the variable IncludeRoleBasedAppsForExistingPC set to a value of true, as shown in the picture opposite.
When using IncludeRoleBasedAppsForExistingPC with a value of true for role-based application sets, the DeploymentType variable must be set appropriately in the task sequence before the 1E Application Migration step. |
Application Migration uses the Install Application and Install Package steps in a Task Sequence to install migrated applications and packages. These Task Sequence steps are dependent on the relevant checkbox (auto install flag) being enabled for each application and package:
If a checkbox is not enabled, the software installation will fail for that application or package. An administrator can enable this checkbox for each application and package by using either of the following methods:
|
|
For more details about using the Auto Install feature, please refer to:
The checkbox is located on the General Information tab of the Properties window for a Configuration Manager Application as shown opposite.
The checkbox is also present on the Advanced tab of the Properties window of a Configuration Manager Package program as shown opposite.
If you intend to use Application Migration to migrate applications from an old computer to a new computer (Replace scenario), you may need to include the Get migration settings step in your Task Sequences. The Get Migration Settings Task Sequence step retrieves information from a Computer Association in Configuration Manager so it can determine the source computer when installing applications on the new computer. It is currently distributed with Nomad and is added to the Task Sequence Editor by installing NomadBranchTools.msi. Please refer to Nomad 7.1 - Installing Nomad tools for operating system deployment for more information.