During Mirage Migration process from Windows XP to Windows 7 the endpoint fails to join Domain specific OU. Failure results in error 2224 and domain join continues without placing computer account into desired OU.
Purpose
Resolves Domain OU joining issue when domain permissions have been verified and are correct however computer account does not end up in the desired OU location.
Cause
DEBUG Wanova.Desktop.Shims.DomainRehab NetJoinDomain result: 2224
NERR_UserExists
Resolution
Mirage Windows XP to Windows 7 migration can join machine accounts to a Microsoft Active Directory environment(AD) as well as an Active Directory Organizational Unit (OU). This process can fail due to various reasons.
It is recommended to ensure that the permissions on the account being used to join the domain are correct as well as the permission on the OU that the computer account(s) will be joined to are correct.
Problems with joining OU typically originate from the fact that the old XP machine still exist within AD and within the old OU.
The client logs will need to be gathered in order to due in depth trouble shooting. To gather logs on the Client side please right click on the mirage icon in the tray then tools and then generate full report. The command will run and then give you the output location of the log bundle.
You can also reference our KB article for assistance as well http://kb.vmware.com/kb/2045794
You can also reference our KB article for assistance as well http://kb.vmware.com/kb/2046069
The log bundle contains the desktop.log file. In the log we can find the DEBUG Wanova.Desktop.Shims.DomainRehab NetJoinDomain result: 2224 error when performing a search.
When using the Microsoft ERR.EXE tool it translates this to "NERR_UserExists". This message is indicating that the AD name used to join the machine to the Domain with already exists in the domain, however within a different OU. To resolve this issue delete the computer account from the domain and either join the domain manually and place the computer account into the correct OU or re-start the Migration process and specify the OU that the XP machine originally belonged to.
Impact/Risks
Machine will not be able to log onto domain, machine and domain relationship trust will not function, log on issues
Additional Information
One possible method to resolve this issue would be to supply a new name for the Windows 7 migrated machine, instead of re-using the existing name of the supplied machine. This is not supported in the Management Console, however it can be done via a CLI.