USMT error 1332

[Guest]

Good day ...

I'am testing USMT 2.6 (user state migration tool) to move a user from an
old domain to an new to domain

steps I have taken.
computer in old domain, logon as local administrator,
run usmt as domain administrator of the old domain (runas /user... )

scanstate c:\store /userlddomain\oldusername /i:migsys.inf /i:miguser.inf
/i:sysfiles.inf /l:c:\logs\logscan.txt /v:7 /o /x /s /f
/progress:c:\logs\progscan.txt

no errors

change computer to new domain
reboot
logon as local administrator
run usmt as domain administrator of the new domain (runas /user... )

loadstate c:\store /mdlddomain:newdomain /muldusername:newusername /v:7
/l:c:\logs\logload.txt /progress:c:\logs\progload.txt

I get error 1332 (two times)
error 1332= no mapping between account names and security IDs was done

migration completed succesfully

remarks
newdomain = windows 2003 server with exchange 2003
newusername account already exist on newdomain

migration of office2003 was not succesfull

can somebody tell me how to prevent the errors?

thanks

 

[Johan Arwidmark]

That error is not really an error but a warning which only is
displayed when verbose log levels are enabled for the loadstate
command. The reason being loadstate is enumerating all entries in
HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList which in
this scenario also includes the "old domain" profiles" that cannot be
resolved.

These warnings occurs when you keep the old computer as is (eg. only
changing the domain membership) and can safely be ignored. If you use
the wipe and load scenario with the exact same usmt data store these
warnings does not occur.

To migrate office 2003 you need to include the migapp.inf template
file to your scanstate command.

There seem to be an issue when rerouting user accounts in conjunction
with the default office 2003 migration. Changing to a new domain name
works fine but changing to a new user name does not.

The only workaround I found so far for office 2003 is to migrate the
user account to the new domain but keeping the same username, run
loadstate (example: loadstate /mdlddomain:newdomain /mu:username
c:\store) and then rename the account in the new domain.


regards
Johan Arwidmark

Windows User Group - Nordic
http://www.wug-nordic.net

 

[Guest]

Hi Johan

Thanks for your advice.

I did some testing for migration of office 2003 and used the tool "Microsoft
office 2003 save my settings wizzard" works fine.

before you use scanstate,
logon as the user in the old domain, use the tool "Microsoft office 2003
save my settings wizzard" ,supplied by office 2003

then use USMT - local administrator

logon as the user in the new domain
use the tool `save my settings wizzard´ for restore office 2003 settings

finish

remarks
if you use Exchange account the offline mailbox .ost is not copied to the
new account
you can make your own .inf file with the option to copy .ost file

with regards
Jan en alleman