It is generally not necessary to include computer objects in synchronization or to migrate them using migration sessions.
The only reason for doing this is to bring Source attributes, such as Description, or the computer's Group Membership over to the Target domain. In this case the account will be created as disabled, unassociated computer account. Later, when RUM is used to migrate computers, the computer account will be enabled and this step (pre-creating the account during synchronization or migration) ensures that the computer will be present in a particular OU. It may also be advisable to migrate computers using this method that have printers attached. That way the child object (the printer) will be created in the target domain for use after the migration.
This function allows Admins to administer the computer migration more granularly, eg. each department might want to have a dedicated OU for computer accounts or Description and / or Group Membership needs to come across.
At no stage is it necessary to select computer accounts when using the Custom Map or the option "Select Objects" when executing tasks.
**Note: do not rename the migrated computer accounts on the target before the computer is migrated. This will cause a new computer account to be created in the default computers OU.**
