Jeff
December 26th 03, 10:11 PM
Hi,
Log on to the network or local laptop as a user with
administrative rights. Change your view to show all files
and not to hide protected operating system files. Copy
the entire contents of the old c:\Documents...\John to the
new c:\Documents...\John. Log back in as the new John and
all should be well.
Good luck,
Jeff
>-----Original Message-----
>Recently I had to remove a laptop (XP Pro) from an NT4.0
>domain and then re-added it. In doing so, the user
profile
>(C:\Documents and Settings....) would no longer be
>recognized as belonging to the previous \Domain\User
(e.g.
>\GreenSupplies\John) once I added the \Domain\User back
on
>the laptop, eventhough that user was not changed in any
>way. Is there anyway to "re-connect" the \Domain\User to
>his previous settings without having to re-install and re-
>configure all of the software & settings. I tried just
>renaming the user folder c:\Documents and Settings\John,
>but it did not work. I'm guessing this is a "SID" related
>thing. It seems like there should be a quick way to fix
>this. Anyone have any ideas???
>thanks,
>Jamie
>
>
>.
>
Log on to the network or local laptop as a user with
administrative rights. Change your view to show all files
and not to hide protected operating system files. Copy
the entire contents of the old c:\Documents...\John to the
new c:\Documents...\John. Log back in as the new John and
all should be well.
Good luck,
Jeff
>-----Original Message-----
>Recently I had to remove a laptop (XP Pro) from an NT4.0
>domain and then re-added it. In doing so, the user
profile
>(C:\Documents and Settings....) would no longer be
>recognized as belonging to the previous \Domain\User
(e.g.
>\GreenSupplies\John) once I added the \Domain\User back
on
>the laptop, eventhough that user was not changed in any
>way. Is there anyway to "re-connect" the \Domain\User to
>his previous settings without having to re-install and re-
>configure all of the software & settings. I tried just
>renaming the user folder c:\Documents and Settings\John,
>but it did not work. I'm guessing this is a "SID" related
>thing. It seems like there should be a quick way to fix
>this. Anyone have any ideas???
>thanks,
>Jamie
>
>
>.
>