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

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: Sysprep issues with WinXP SP2 (that I did not have with WinXP SP1)
    ... This was a change that was requested and included with SP2 ... 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: 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: Corrupt Local File
    ... Logon as administrator, create a new profile, then copy your old one into ... you cannot recover a corrupt profile. ... How to Copy User Data to a New User Profile ... hit ctrl+alt+delete twice at the logon screen and type it in. ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: Desktop blank..
    ... She has a corrupt profile. ... What she needs to do is logon as administrator and create a new profile for ... hit ctrl+alt+delete twice at the logon screen and type it in. ... How to Copy User Data to a New User Profile ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: Corrupt Local File
    ... > Hi Lenny, ... > Logon as administrator, create a new profile, then copy your old one into ... you cannot recover a corrupt profile. ...
    (microsoft.public.windowsxp.help_and_support)