Re: good question for a good XP guru!

From: djc (noone_at_nowhere.com)
Date: 10/06/04


Date: Wed, 6 Oct 2004 09:10:21 -0400

Thanks for the reply Darrell. The method was, at least at one time,
recommended by Microsoft. I certianly don't doubt what your saying it true
though. Do you have any links to updated information on this?

thanks again.

""Darrell Gorter[MSFT]"" <Darrellg@online.microsoft.com> wrote in message
news:jxzUIS0qEHA.1520@cpmsftngxa06.phx.gbl...
> Hello djc,
> That process is fraught with errors.
> When you overwrite the default user profile with another profiles such as
> the "sysprep" profile that you generated, the profile contains a number of
> links and pointers back the "sysprep" profile locations. So if the new
> users do not have permissions to that "sysprep" profile they will get
> errors.
> It is possible that the ACLs on some of the registry keys may be specific
> also the "sysprep" profile.
> Power settings for the most part do require administrator rights, not all
> of them but most of them require you to be an administrator.
> Thanks,
> Darrell Gorter[MSFT]
>
> This posting is provided "AS IS" with no warranties, and confers no rights
> --------------------
> >From: "djc" <noone@nowhere.com>
> >Subject: good question for a good XP guru!
> >Date: Mon, 4 Oct 2004 15:57:08 -0400
> >Lines: 46
> >X-Priority: 3
> >X-MSMail-Priority: Normal
> >X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
> >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
> >Message-ID: <#wr$hxkqEHA.2964@TK2MSFTNGP14.phx.gbl>
> >Newsgroups: microsoft.public.windowsxp.setup_deployment
> >NNTP-Posting-Host: mail.hesstech.com 209.178.219.91
> >Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP14.phx.gbl
> >Xref: cpmsftngxa06.phx.gbl
> microsoft.public.windowsxp.setup_deployment:124883
> >X-Tomcat-NG: microsoft.public.windowsxp.setup_deployment
> >
> >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!
> >
> >
> >
> >
>



Relevant Pages

  • Re: How hard would it be to script this process
    ... scripting that little bit might be somewhat simpler for you ... > Log in as Local Administrator Account and do the following: ... > b) Rename the built-in Administrator account, ... > a) Create a domain account user profile. ...
    (microsoft.public.windows.server.scripting)
  • good question for a good XP guru!
    ... Per microsoft guidelines I setup a local user account ... installed all applications while logged in as sysprep. ... local administrator and copy sysprep's user profile to the Default Users's ... Settings folders. ...
    (microsoft.public.windowsxp.setup_deployment)
  • good question for a good XP guru!
    ... Per microsoft guidelines I setup a local user account ... installed all applications while logged in as sysprep. ... local administrator and copy sysprep's user profile to the Default Users's ... Settings folders. ...
    (microsoft.public.windowsxp.setup_deployment)
  • good question for an xp guru
    ... Per microsoft guidelines I setup a local user account ... installed all applications while logged in as sysprep. ... local administrator and copy sysprep's user profile to the Default Users's ... The error does not occur when done as THE local administrator. ...
    (microsoft.public.windowsxp.configuration_manage)
  • RE: good question for a good XP guru!
    ... When you overwrite the default user profile with another profiles such as ... links and pointers back the "sysprep" profile locations. ... >local administrator and copy sysprep's user profile to the Default Users's ... The error does not occur when done as THE local administrator. ...
    (microsoft.public.windowsxp.setup_deployment)