RE: Sysprep issues with WinXP SP2 (that I did not have with WinXP SP1)

Hello Lyman,
This was a change that was requested and included with SP2
Here is a QFE article link to revert the behavior.
887816 Changes in behavior of the SysPrep and RIPREP tools after you
install Windows XP Service Pack 2
http://support.microsoft.com/default.aspx?scid=kb;EN-US;887816

Thanks,
Darrell Gorter[MSFT]

This posting is provided "AS IS" with no warranties, and confers no rights
--------------------
<From: "Lyman Green" <lymang@xxxxxxxxx>
<Newsgroups: microsoft.public.windowsxp.setup_deployment
<Subject: Sysprep issues with WinXP SP2 (that I did not have with WinXP SP1)
<Date: 12 Jan 2006 07:30:54 -0800
<Organization: http://groups.google.com
<Lines: 45
<Message-ID: <1137079854.496404.9880@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
<NNTP-Posting-Host: 192.58.204.226
<Mime-Version: 1.0
<Content-Type: text/plain; charset="iso-8859-1"
<X-Trace: posting.google.com 1137079859 26671 127.0.0.1 (12 Jan 2006
15:30:59 GMT)
<X-Complaints-To: groups-abuse@xxxxxxxxxx
<NNTP-Posting-Date: Thu, 12 Jan 2006 15:30:59 +0000 (UTC)
<User-Agent: G2/0.2
<X-HTTP-UserAgent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1;
NET CLR 1.0.3705; .NET CLR 1.1.4322),gzip(gfe),gzip(gfe)
<Complaints-To: groups-abuse@xxxxxxxxxx
<Injection-Info: g43g2000cwa.googlegroups.com; posting-host=192.58.204.226;
< posting-account=EDSCdAwAAABnllg95lrEbqIVbKod9Z7P
<Path:
TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!newsfeed00.sul.t-online.de!t-onli
ne.de!border2.nntp.dca.giganews.com!border1.nntp.dca.giganews.com!nntp.gigan
ews.com!postnews.google.com!g43g2000cwa.googlegroups.com!not-for-mail
<Xref: TK2MSFTNGXA02.phx.gbl
microsoft.public.windowsxp.setup_deployment:146127
<X-Tomcat-NG: microsoft.public.windowsxp.setup_deployment
<
<Under SP1 I had an "master image" drive that had everything configured
<exactly how I wanted it. When I needed to change the image, I would
<logon with the administrator account and make the change to the system,
<and then run sysprep and "use mini-setup" and then "reseal."
<Everything worked great!
<
<If I apply WinXPSP2 to the master image drive, the scenario changes,
<and I haven't been able to figure out why for the life of me.
<
<Under SP2 I am seeing the following behavior: I fire up a newly cloned
<SP1 system. I have the system joining the network automatically via
<the sysprep.inf file. All this works fine. I run WinXPSP2 and make a
<few other post SP2 tweaks to the registry. Once I've confirmed XPSP2
<is applied successfully to the system, I run sysprep, and choose the
<same choices as I did under SP1 (use mini-setup and then reseal). All
<still looks well - it appears as though everything is working. I take
<the cloned copy and join it to the network and run through the
<mini-setup wizard. I logon as administrator and add a new user (all as
<I did exactly, no changes). When I then logoff and log on with the new
<user, I see the weirdness.
<
<For some reason, the new user has a number of the settings (both
<registry and otherwise) that the administrator profile had! Like for
<instance, I had a specific bitmap for the desktop background for the
<admin profile only (splashed across the bitmap in capital letters
<"Admin Logon"). Somehow, the sysprep process has copied that default
<background bitmap into the default user settings!!! I completely do not
<understand why or how this is happening, and I have confirmed that this
<ONLY happens after the sysprep.
<
<If I just apply WinXPSP2 and do not sysprep the system, and then add a
<new user and logon with that user, I will not see these issues.
<
<Another example: for the administrative profile I have "Display
<Administrative Tools" selected in the Customize Classic Start Menu
<options. I had that option OFF for the default user profile. Sysprep
<has now copied that option to the default user profile.
<
<Has anyone seen similar behavior and if so, do you have a solution?
<
<I'd appreciate any assistance, I've been beating my head against a wall
<trying to figure out why this is happening.
<
<Lyman Green
<
<

.

Relevant Pages

  • Re: XP SP2 sysprep user profiles
    ... >> and then sysprep it for deployment - when you log into AD as a user and ... an administrator account in AD wants to be the default ... >> user profile instead of it populating the current logged on user. ... > Note that this is somewhat changed in WinXP SP2: ...
    (microsoft.public.windowsxp.setup_deployment)
  • Re: Sysprep and SP2
    ... > my problem if you use Sysprep with SP2. ... > I know that there is a new version of Sysprep for XP ... > default user got the Administrator's profile. ... -- torgeir, Microsoft MVP Scripting and WMI, Porsgrunn Norway Administration scripting examples and an ONLINE version of the 1328 page Scripting Guide: ...
    (microsoft.public.windowsxp.setup_deployment)
  • Sysprep issues with WinXP SP2 (that I did not have with WinXP SP1)
    ... I logon as administrator and add a new user (all as ... admin profile only (splashed across the bitmap in capital letters ... the sysprep process has copied that default ...
    (microsoft.public.windowsxp.setup_deployment)
  • Re: SP2 - Sysprep regenerates default user
    ... Before running sysprep we run a .reg file that contains the following. ... Seems to work fine with SP2 also. ... > logged back on my custom default user profile has been ... > default user profile. ...
    (microsoft.public.windowsxp.setup_deployment)
  • Re: Sysprep and SP2
    ... >> my problem if you use Sysprep with SP2. ... >> I know that there is a new version of Sysprep for XP ... >> slipstreamed installation of XP w SP2. ... >> default user got the Administrator's profile. ...
    (microsoft.public.windowsxp.setup_deployment)