USMT dilemma

Z

Zeno

I'm in the process of testing USMT, as our co. will be migrating
hundreds of users from a Novell environment to AD.

Because Novell uses local accounts, once we join AD we have to migrate
the accts to the new user domain acct users will be using.

However what I've found is that I export the acct using USMT. Then when
I sign with the new AD account and run the loadstate, all it does is
loads the accts which I backed up using scanstate back to where it was.
Instead of the new acct which I wanted to migrate the profile to.

Can I doing something wrong here..... can anyone please help....
These are the commands I'm using:

scanstate /i "%runpath%\sysfiles.inf" /i "%runpath%\Migapp.inf" /i
"%runpath%\Migsys.inf" /i "%runpath%\miguser.inf" /i
"%runpath%\UserData.inf" /l "%TEMP%\scanlog.txt" /v 7 /x /s /f /o

then just loadstate without any parameters.

Am I doing something wrong??

Thanks in advance....
 
Z

Zeno

Sorry made a mistake double posting....

Just read through the USMT notes again.....

Found that I should be using the /md:NewDomain switch.

So therefore am I right in saying, if I migrate a local account using
scanstate. Then if I want to use the migrated in a domain acct I need
to specify the /md:NewDomain
loadstate c:\profile

then this should load the backedup local\username acct to the
domain\username acct?

Cheers...
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top