M
Matt
Hello,
I am setting up an XP Home workstation and have configured it for two
partitions. I have setup the Documents and Settings folder to reside on
drive D: along with all the profiles so that if I need to reimage the C:
partition I will not lose all the users settings (email, mydocs,
customizations etc).
My problem is that if I do reimage the C: partition, the SAM file will
be redeployed with the original preconfigured accounts and not the new
user accounts created after the original deployment. This means that I
have to add the users to the SAM database again and reassign the
profiles.
Basically what I need is to be able to link up the recreated user
accounts with the old profiles and be able to script this and not use
the GUI Copy To function of user profile copying.
What I have done so far is to use net user to create the new account and
the /profilepath switch to set the account to use the old profile
folder. I have also scripted changing the owner of the old profile with
chown and cacls to give the new account access to the profile folder.
When the user logs in after this is done the profile is used but XP
still generates a second profile but uses the folder of the old profile.
What essentially happens is that the MyDocs and such are available, but
the theme and background is lost (items stored in the users registry).
I have search google for a way to script the Copy To and Permitted to
use functions as they accomplish this task without problem, but again I
want to script this functionality and avoid the GUI.
Anyone have any recommendations or pointers on how I can find a
description of the changes the Permitted to use does to a profile to
allow a new user to access the old profile?
Thanks in advance.
Matt
I am setting up an XP Home workstation and have configured it for two
partitions. I have setup the Documents and Settings folder to reside on
drive D: along with all the profiles so that if I need to reimage the C:
partition I will not lose all the users settings (email, mydocs,
customizations etc).
My problem is that if I do reimage the C: partition, the SAM file will
be redeployed with the original preconfigured accounts and not the new
user accounts created after the original deployment. This means that I
have to add the users to the SAM database again and reassign the
profiles.
Basically what I need is to be able to link up the recreated user
accounts with the old profiles and be able to script this and not use
the GUI Copy To function of user profile copying.
What I have done so far is to use net user to create the new account and
the /profilepath switch to set the account to use the old profile
folder. I have also scripted changing the owner of the old profile with
chown and cacls to give the new account access to the profile folder.
When the user logs in after this is done the profile is used but XP
still generates a second profile but uses the folder of the old profile.
What essentially happens is that the MyDocs and such are available, but
the theme and background is lost (items stored in the users registry).
I have search google for a way to script the Copy To and Permitted to
use functions as they accomplish this task without problem, but again I
want to script this functionality and avoid the GUI.
Anyone have any recommendations or pointers on how I can find a
description of the changes the Permitted to use does to a profile to
allow a new user to access the old profile?
Thanks in advance.
Matt