SP2 - Sysprep regenerates default user

[Adin Sabic]

Hi,

I have updated my XP image to include SP2. After
installing sp2 I replaced the default user with my highly
customised one, then run sysprep to prepare for imaging.

After the machine is rebooted the mini setup wizard runs
and completes with no errors. However once rebooted and
logged back on my custom default user profile has been
replaced by the basic original XP one, with all my
changes lost. I have tried it several times and get the
same results.

Is it by design that in SP2, sysprep regenerates the
default user profile. Is there a work around as it is
highly annoying?

Thanks

Adin

 

[Uwe Afemann]

Hi,

I have updated my XP image to include SP2. After
installing sp2 I replaced the default user with my highly
customised one, then run sysprep to prepare for imaging.

After the machine is rebooted the mini setup wizard runs
and completes with no errors. However once rebooted and
logged back on my custom default user profile has been
replaced by the basic original XP one, with all my
changes lost. I have tried it several times and get the
same results.

Is it by design that in SP2, sysprep regenerates the
default user profile. Is there a work around as it is
highly annoying?

Thanks

Adin

Hi,
the new behavior (bug) is by design. Sysprep creates a new Default User
from the Administrator's profile. I got this information from someone in
this newsgroup.
I use the following work around.
Before preparing for sysprep I save my Default User profile to another
location, i. e. use xcopy with /E /O /Y /I /H /K switches to mantain
all user rights and after rebooting I restore Default User from the
location where I saved the Default User profile. But before restoring I
totally remove the Default User Profile in order to get a clean Default
User profile without any stuff from the Administrator's profile, i. e. I
use rmdir with switches /s and /q.
I put all these commands in two scripts and a link on the
administrator's desktop.
Hope this will help you.

Uwe

 

[Steve Roberts]

Before running sysprep we run a .reg file that contains the following. This
tells sysprep not to wipe out profiles. Seems to work fine with SP2 also.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\OemStartMenuDa
ta]
"OemDesktopCleanupDisable"=dword:00000001

Steve

 

[Guest]

This key prevents the desktop icons getting cleared, not
settings associated with default user.

Uwe's solution is a work around but it's an extra step
not needed with SP1, and when you have several hundred
machines to image it becomes a nuisance.

I hope Microsoft release a solution to this as this
problem makes rollouts less automated.

-----Original Message-----
Before running sysprep we run a .reg file that contains the following. This
tells sysprep not to wipe out profiles. Seems to work fine with SP2 also.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVers
ion\OemStartMenuDa
ta]
"OemDesktopCleanupDisable"=dword:00000001

Steve

Hi,

I have updated my XP image to include SP2. After
installing sp2 I replaced the default user with my highly
customised one, then run sysprep to prepare for imaging.

After the machine is rebooted the mini setup wizard runs
and completes with no errors. However once rebooted and
logged back on my custom default user profile has been
replaced by the basic original XP one, with all my
changes lost. I have tried it several times and get the
same results.

Is it by design that in SP2, sysprep regenerates the
default user profile. Is there a work around as it is
highly annoying?

Thanks

Adin

.