D
djc
Note: I posted this in the setup/deployment group but my newsreader crapped
out on me so I am posting here. If it shows up in both places.... sorry for
the double post.
xp pro sp2:
Setting up a reference machine for creating a ghost image to deploy to
several machines. Per microsoft guidelines I setup a local user account
(called sysprep) and made it a member of the local administrators group. I
installed all applications while logged in as sysprep. Then I log in as THE
local administrator and copy sysprep's user profile to the Default Users's
Profile. Then I run the sysprep.exe utility to seal the machine and image.
Thats the general order of events. Now, I don't recall the exact wording but
there is an option to 'make private' or something to that effect for local
user accounts in xp. After doing that the directory structure for that user
under the 'documents and settings' directory only includes that user's
account in it's ACL(s). That part I know, because I looked at the permission
changes for the folders... but what I don't know, and did not think about
until afterwards, is this: DOES CHOOSING TO 'MAKE PRIVATE' ALSO CHANGE
PERMISSIONS IN THE REGISTRY? (wish I remembered the actual wording here..
but I'm sure any xp guru will know what I'm talking about)
before copying the sysprep user profile to the Default User Profile I had
chosen this 'make private' option. So when I went to try to copy the sysprep
user profile over the Default User Profile it of course failed because the
Administrator account did not have permissions on sysprep's Documents and
Settings folders. I realized this and added the Administrator's account back
into the ACL for sysprep's Documents and Settings folder.. and then copied
the profile over with no problem. I then went on to finish up by sysprepping
and imaging.
Now, on a newly imaged machine I have a strange error when logged on as a
new user and trying to change Power Scheme to 'Always On': "Not all
privileges referenced are assigned to the caller". The user is a member of
the Power Users' group, which I thought would have sufficient privileges to
do this. The error does not occur when done as THE local administrator.
so, I'm thinking the answer to my question above is YES, and if so I didn't
really copy the whole user profile over did I? All the registry keys that
should be copied as well did not get copied? and things are going to be
screwy? Could someone please let me know if I'm right here and maybe let me
know what other issues I can expect? Will they be serious enough to start
all over and create a new image? Or am I completely wrong? that would be
nice.
any info is appreciated. Thanks!
out on me so I am posting here. If it shows up in both places.... sorry for
the double post.
xp pro sp2:
Setting up a reference machine for creating a ghost image to deploy to
several machines. Per microsoft guidelines I setup a local user account
(called sysprep) and made it a member of the local administrators group. I
installed all applications while logged in as sysprep. Then I log in as THE
local administrator and copy sysprep's user profile to the Default Users's
Profile. Then I run the sysprep.exe utility to seal the machine and image.
Thats the general order of events. Now, I don't recall the exact wording but
there is an option to 'make private' or something to that effect for local
user accounts in xp. After doing that the directory structure for that user
under the 'documents and settings' directory only includes that user's
account in it's ACL(s). That part I know, because I looked at the permission
changes for the folders... but what I don't know, and did not think about
until afterwards, is this: DOES CHOOSING TO 'MAKE PRIVATE' ALSO CHANGE
PERMISSIONS IN THE REGISTRY? (wish I remembered the actual wording here..
but I'm sure any xp guru will know what I'm talking about)
before copying the sysprep user profile to the Default User Profile I had
chosen this 'make private' option. So when I went to try to copy the sysprep
user profile over the Default User Profile it of course failed because the
Administrator account did not have permissions on sysprep's Documents and
Settings folders. I realized this and added the Administrator's account back
into the ACL for sysprep's Documents and Settings folder.. and then copied
the profile over with no problem. I then went on to finish up by sysprepping
and imaging.
Now, on a newly imaged machine I have a strange error when logged on as a
new user and trying to change Power Scheme to 'Always On': "Not all
privileges referenced are assigned to the caller". The user is a member of
the Power Users' group, which I thought would have sufficient privileges to
do this. The error does not occur when done as THE local administrator.
so, I'm thinking the answer to my question above is YES, and if so I didn't
really copy the whole user profile over did I? All the registry keys that
should be copied as well did not get copied? and things are going to be
screwy? Could someone please let me know if I'm right here and maybe let me
know what other issues I can expect? Will they be serious enough to start
all over and create a new image? Or am I completely wrong? that would be
nice.
any info is appreciated. Thanks!