USMT 2.6 and multiple users pointing to the same profile

[Guest]

USMT 2.6 appears to load all of the user hives at once. The problem occurs
when multiple profiles point to the same ntuser.dat file. The first profile
loads the file, the rest error out.

Module Error Can't load registry file C:\Documents and
Settings\USERNAME\ntuser.dat to
S-1-5-21-1315882459-817801392-1359842108-77543 [ERROR=32 (20h)]

Error Failed to process DOMAIN\USERNAME. [ERROR=32 (20h)]
Info Error 32: The process cannot access the file because it is
being
used by another process.

We do this to prepare systems to migrate to Active Directory, so that when
the user migrates to AD, they logon to the same profile.

Any ideas?

Larry

 

[Johan Arwidmark]

Can you post the commandline you are using for scanstate and loadstate


regards

Johan Arwidmark
Microsoft MVP - Setup/Deployment

 

[Guest]

Can you post the commandline you are using for scanstate and loadstate

John... Here they are.


Scanstate:
Q:\scanstate %DEST%\%USER% /c /i Q:\migapp.inf /i Q:\migsys.inf /i
Q:\miguser.inf /i Q:\sysfiles.inf /l c:\%USER%-scan.log /v 7 /localonly /o
/ui:30 /compress-

Loadstate:
c:\userdata\config\usmt\loadstate Q:\%UserName% /l
%windir%\temp\loadstate.log /v 7 /compress- /c

 

[Michael Niehaus [MS]]

I am certain that configuring multiple profiles to point to the same
directory is unsupported (and leads to problems such as the one you
describe).

A better approach for migrating to Active Directory would be to use the
MOVEUSER tool to change the ownership of the existing profile to the domain
account. This can be done as part of the migration process.

-Michael Niehaus
Senior Consultant
MCS US Centers of Excellence - Deployment AOS
(e-mail address removed)
This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Guest]

Thanks Michael... that's what we figured too. We're already established in
this practice, and nearly done with our migration, so we'll have to find a
work around.

Larry

I am certain that configuring multiple profiles to point to the same
directory is unsupported (and leads to problems such as the one you
describe).

A better approach for migrating to Active Directory would be to use the
MOVEUSER tool to change the ownership of the existing profile to the domain
account. This can be done as part of the migration process.

-Michael Niehaus
Senior Consultant
MCS US Centers of Excellence - Deployment AOS
(e-mail address removed)
This posting is provided "AS IS" with no warranties, and confers no rights.

USMT 2.6 appears to load all of the user hives at once. The problem occurs
when multiple profiles point to the same ntuser.dat file. The first
profile
loads the file, the rest error out.

Module Error Can't load registry file C:\Documents and
Settings\USERNAME\ntuser.dat to
S-1-5-21-1315882459-817801392-1359842108-77543 [ERROR=32
(20h)]

Error Failed to process DOMAIN\USERNAME. [ERROR=32 (20h)]
Info Error 32: The process cannot access the file because it is
being
used by another process.

We do this to prepare systems to migrate to Active Directory, so that when
the user migrates to AD, they logon to the same profile.

Any ideas?

Larry