Hello,
I have to join 2500 XP standalone users to a W2k domain with 2 W2k3 Domain Controllers working in mixed mode. Each user has his XP workstation profile customized the way he wants it but when each is joined to the domain, a new profile will be created on the local XP workstation and his old will be there but invisible.
These users are not tech savvy and can't address this themselves. I have researched automated ways of doing the obvious: Let the users retain their present profiles.
I have come up with one SID Registry Setting hack but was wondering if anyone had a better solution for a mass scale migration.
Here is what I have so far:
--------------------
Point the new domain SID to look to the location of the old local profile:
Obtain the SID of new new domain account by using the Win2k Resource Kit utility 'getsid'. i.e.:
c:getsid localhost [username] domaincontroller [username]
Using regedit, drill down to HKEY_LOCAL_MACHINE/SOFTWARE/Microsoft/Windows/NTCurrentVersion/ProfileList
and find the SID of the domain account. Change the ProfileImagePath to point to old local profile.
Instead of
%SystemDrive%\Documents and Settings\kjc.JAX
change HKEY_LOCAL_MACHINE/SOFTWARE/Microsoft/Windows NTCurrentVersion/ProfileList/ProfileImagePath
to the location of your old local profile, like this:
%SystemDrive%/Documents and Settings/kjc
Upon next login to the domain account, old local profile will be loaded.
-----------------------
I haven't tried this, but is this the best solution from Microsoft for Large Enterprise migrations in the thousands?
Seems like many people would like to keep their old local profile. Is this hack, which I still have to script and automate the best thing going?
Thanks!
L,
Me
I have to join 2500 XP standalone users to a W2k domain with 2 W2k3 Domain Controllers working in mixed mode. Each user has his XP workstation profile customized the way he wants it but when each is joined to the domain, a new profile will be created on the local XP workstation and his old will be there but invisible.
These users are not tech savvy and can't address this themselves. I have researched automated ways of doing the obvious: Let the users retain their present profiles.
I have come up with one SID Registry Setting hack but was wondering if anyone had a better solution for a mass scale migration.
Here is what I have so far:
--------------------
Point the new domain SID to look to the location of the old local profile:
Obtain the SID of new new domain account by using the Win2k Resource Kit utility 'getsid'. i.e.:
c:getsid localhost [username] domaincontroller [username]
Using regedit, drill down to HKEY_LOCAL_MACHINE/SOFTWARE/Microsoft/Windows/NTCurrentVersion/ProfileList
and find the SID of the domain account. Change the ProfileImagePath to point to old local profile.
Instead of
%SystemDrive%\Documents and Settings\kjc.JAX
change HKEY_LOCAL_MACHINE/SOFTWARE/Microsoft/Windows NTCurrentVersion/ProfileList/ProfileImagePath
to the location of your old local profile, like this:
%SystemDrive%/Documents and Settings/kjc
Upon next login to the domain account, old local profile will be loaded.
-----------------------
I haven't tried this, but is this the best solution from Microsoft for Large Enterprise migrations in the thousands?
Seems like many people would like to keep their old local profile. Is this hack, which I still have to script and automate the best thing going?
Thanks!
L,
Me