USMT weird scenario question

[JP Breton]

sorry for cross posting. Was not sure where to post.

We are currently deploying Windows XP SP2 with BDD 2.0 lite touch.

We have noticed that some user profiles (from windows 2000) were in the
form: username.domain:
example, a user jbreton in a domain call : INET, would have a profile (in
documents and setting) jbreton.inet instead of just jbreton

While the majority of our INET profile user are fine, USMT crash during the
scanstate when it encounters those profile (jbreton.inet)

Is their a way to tell scanstate to don't crash with those profile.

I have tried numerous option : /ALL, /USER:inet\%username% ....etc but none
of them seem to worked.

Anyone have an idea.

Regards

JP

 

[Michael Niehaus [MS]]

I have not seen that issue. Normally, USMT loads the profiles from the path
specified in the registry, so as long as the registry path and the file
system path match everything should be fine. (It doesn't even use the
account name in the registry, instead translating the SID for that account
into the name via an API call.) If the paths don't match, then the machine
has been corrupted. If the paths do match (and as long as the user you are
running Scanstate as has sufficient access to the machine and to the profile
directories), it would be advisable to contact MS Support.

-Michael Niehaus
Systems Design Engineer
(e-mail address removed)
This posting is provided "AS IS" with no warranties, and confers no rights.