Quote:
|
Originally Posted by Ozzyo99
Right this has been the proverbial plague for our business, it doesn't happen frequently but when it does it's a pain in the backside, especially when factoring in additional non-standard build software, and requesting licence keys for activations etc.
Glad i bumped into this thread because the answer to the problem is:
1. Log onto system (preferably as admin).
2. Goto start/run/regedt32
3. Locate key - HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList
4. This will show all readable profiles on the machine, it may but probably will not show information leading to the users original profile.
5. Navigate to C:\Documents and Settings\UsersName and note the profile name of the original profile, usually the same minus the domain information. Make a note of it.
6. Now go back to regedt and manually edit the duplicate profile location in the ProfileImagePath key to that of the original e.g:
Original - %SystemDrive%\Documents and Settings\jsmith
Duplicate - %SystemDrive%\Documents and Settings\jsmith.domain
Change the duplicate to point to the original profile, save the change.
7. Now have the user log back in, and they should now again be operating on their original profile - bring on huge relief!
|
Hi, everybody.
This is very usefull tip, but, does anybody know if there are things that can not be imported in this way?
I had a client (xp pro) that I had to "rejoin" to the domain, because the domain was recreated (I don