Resolution
Domain Migration Administrator 7.1
symptom
When migrating a computer, a new computer account is created in the target domain, but the workstation domain affiliation is not changed and workstation is not rebooted.
cause
There are two possible reasons this may occur:
DMA is not able to contact the OnePointDMR$ share on the DMA console machine.
This issue also may occur on Windows 2000 machines by running DMA while logged in with a source Domain Admin account and entering a target Domain Admin account into the credential section of the Computer Migration wizard.
fix
To resolve this issue:
- Verify that the credentials that were specified in the 'Migrate Computers' wizard have administrative rights on the DMA console machine. Verify that the workstation can ping the DMA console by NetBIOS machine name and take other steps as necessary to ensure that name resolution is working properly.
- The recommended practice when migrating computers is to log in to the DMA console using an account that is defined in the source domain, and also specifying this account when prompted for credentials in the computer migration wizard. This source account should be a member of the Domain Admins global group in the source domain, and a member of the local Administrators group in the target domain.
note
To identify this issue, review the DCTLog.txt on the workstation that is being migrated. If the last line in the DCTLog.txt is as follows, there may be a permission or name resolution issue:
2002-05-10 11:05:09-Exporting account reference information to '\\servername\OnePointDMR$\WORKSTATION12345678.sectrans'
Where servername is the name of the computer where the DMA console is installed and WORKSTATION is the name of the computer that you are trying to migrate or translate security on.
The next lines should be:
2002-05-10 11:05:10-Changed domain affiliation of local computer to DOMAINNAME.
2002-05-10 11:05:10-The local machine will be rebooted in 0 minutes.
However, if these lines are not present in the log, that means the DMA agent never got to these tasks. Therefore, the domain affiliation was not changed and the computer was not rebooted.