The migration job specifies the computers or groups you want to migrate, and the OS and software templates you want to use for OS migration. You must create a migration job to test and activate OS migration.
Follow these steps:
The Migration Jobs page is displayed.
The New Migration Job wizard opens.
The selected migration type is applied to all the computers in the migration job.
Note: If a local domain manager group and a replicated enterprise manager group are with the same name, both the group names appear in the Select Groups page of the wizard. Although the selection includes both the groups, the assessment is only performed on the local group.
Note: For a Machine Replacement migration that includes bare metal computers, you can only select an OS template that is of type global or group-based. Hardware model-based OS templates cannot be used for bare metal computers because the hardware inventory collection is not run on such computers. However, if you have already installed the DSM agent on the new computers and have collected the hardware inventory for such computers, you can use the hardware-model based OS template.
Note: To use a group-based OS template for a machine replacement migration, verify that all new computers (target) are associated with the OS template.
LDAP User
ldap://dirc_name/user_name
ldaps://dirc_name/user_name
WINNT Local User
winnt://computer_name/user_name
WINNT Domain User
winnt://domain_name/user_name
CA IT PAM uses the supplied credentials for accessing Client Automation while executing the job.
Note: Mapping information is mandatory for machine replacement migrations. The mapping file must contain all the computers that are part of the migration job. Otherwise, the migration job creation fails.
The migration job is created and listed in the Migration Jobs page. You can now validate and activate the job.
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|