XP SP3 Sysprep and Default User Behavior

[AJ]

I have read every thread I can find on this and still no-one has reported the
behavior I am experiencing with my SP3 deployment.

I have a Pre-Sysprep'd SP2 image, I upgrade it to SP3 using the full SP3
download (not Windows Update), then fully patch any other post SP3 hotfixes
using Windows Update.

I download and extract Deploy.cab and overwrite my current c:\sysprep files
with the new versions.

I have already configured my Administrator profile with different folder
views and placed several tools (like process explorer and process monitor) on
the desktop. I also have already created a local user named Default and
customized it with user views, wallpaper and a smaller customized Start Menu.

I reboot and capture my "new Pre-Sysprep" image. I log on to Windows as
Administrator to copy my customized user named Default over the Default User
profile and grant Authenticated Users permissions. I then delete the user
named Default and its directory from the workstation.

I have a .bat file in the sysprep directory named doprep.bat which contains
the following command:
"%SystemDrive%\Sysprep\Sysprep.exe" -mini -quiet -reseal -forceshutdown

I have used this process since Windows 2000 and I don’t want to get in to a
discussion of its merits or downsides.

Everything should work as it did XP SP2 with the KB887816 patch installed,
but it doesn’t.

Here is what I see:

Administrator profile gets deleted and recreated sometime during Mini-Setup,
I can confirm this by files in the profile being present in my “post Sysprep”
version of the image when I use Ghost Explorer to view the .gho file.
Files on the Administrator desktop get moved to the folder C:\Program
Files\Program Shortcuts, this folder did not exist before Mini-Setup ran
using the above .gho as a reference.
The Default User profile works exactly as expected with the exception of its
desktop shortcuts which get moved to the C:\Program Files\Program Shortcuts
folder and Administrative Tools is in the start menu when it was not present
in the .gho file.

I thought I could get my Default User working by moving the desktop
shortcuts over to the All Users profile, but they were also moved to the
C:\Program Files\Program Shortcuts folder as well.

Any help would be appreciated, I have run out of options and my deadline is
near.

Thanks in advance!

AJ

[Daveg]

Take a look at this blog entry to see if it addresses your issue.

http://blogs.technet.com/deploymentguys/archive/2008/05/22/configuring-default-settings-for-windows-image-deployment-update-for-windows-xp-sp3.aspx

Dave Guenthner [MSFT]

[AJ]

Unfortunately, that post gives no helpful information.

I'm aware of the profile copy changes, and the inclusion of the previous SP2
patch to restore SP1 functionality.

If I use the suggested ServerProfile setting in the Sysprep.inf, it
re-restores the SP2 default functionality.

Neither of these are the SP1 or the patched SP2 behavior, which is what I
need. I need to have an Administrator and Default User profile differently
configured.

AJ

Post by Daveg
Take a look at this blog entry to see if it addresses your issue.
http://blogs.technet.com/deploymentguys/archive/2008/05/22/configuring-default-settings-for-windows-image-deployment-update-for-windows-xp-sp3.aspx
Dave Guenthner [MSFT]

[Adam Leinss]

Post by AJ
Any help would be appreciated, I have run out of options and my
deadline is near.

This will probably be of no help to you, but I'm not seeing any of the
behavior in my SP3 patched image you just described. Our administrator and
default user profiles are the same, but I went in and changed the folder
views and placed a folder called "Admin tools" logged in as administrator.
I sysprepped the machine and everything is still there after the sysprep.

I can only suggest making a new image and trying the sysprep again and see
what results you get, then keep adding your apps to the image, sysprep and
see if it keeps behaving.

Adam

[AJ]

Adam,

Thanks for the heads up, I'm not sure I understand your post 100% but I get
the gist, you're not having the same issue I am.

I have taken another SP2 XP box, configured the default user and the admin
user differently, syprep'd the box and received the exact same behaviour with
no applications installed, just fully patched.

Were you SP3 patched or did you do the rest of the windows updates that have
released since when you sysprep'd. Did you build the MASS STORAGE SECTION,
did you run Mini-Setup?

Post by Adam Leinss

Post by AJ
Any help would be appreciated, I have run out of options and my
deadline is near.

This will probably be of no help to you, but I'm not seeing any of the
behavior in my SP3 patched image you just described. Our administrator and
default user profiles are the same, but I went in and changed the folder
views and placed a folder called "Admin tools" logged in as administrator.
I sysprepped the machine and everything is still there after the sysprep.
I can only suggest making a new image and trying the sysprep again and see
what results you get, then keep adding your apps to the image, sysprep and
see if it keeps behaving.
Adam

[Adam Leinss]

Post by AJ
Were you SP3 patched or did you do the rest of the windows updates
that have released since when you sysprep'd. Did you build the MASS
STORAGE SECTION, did you run Mini-Setup?

Every time I update our image, I would apply the updates from Windows
update and document them in a text file in the image.

I then applied the full SP3 against the image (which was at the SP2
level).

Since SP3, I've applied all the updates from Windowsupdate.com (except
Internet Explorer 7) and still no issues.

I create static entries in my mass storage section:

[SysprepMassStorage]

;IDE chipset driver for Dell Optiplex 280
PCI\VEN_8086&DEV_266F=C:\i\d\c\ich6ide.inf
;IDE chipset driver for Gateway 600YGR
PCI\VEN_8086&DEV_248A=C:\windows\inf\mshdc.inf
;IDE chipset driver for Dell Latitude D610
PCI\VEN_8086&DEV_2653=C:\windows\inf\mshdc.inf
;IDE chipset driver for Gateway ESX 500L
PCI\VEN_8086&DEV_24CB=C:\i\d\c\ich4ide.inf
;IDE chipset driver for Dell Latitude D600
PCI\VEN_8086&DEV_24CA=C:\i\d\c\ich4ide.inf
;IDE chipset driver for Dell GX620, GX520
PCI\VEN_8086&DEV_27C0=C:\i\d\c\ich7ide.inf
PCI\VEN_8086&DEV_27DF=C:\i\d\c\ich7ide.inf
;IDE chipset driver for Dell Optiplex GX270
PCI\VEN_8086&DEV_24D1=C:\windows\inf\mshdc.inf
PCI\VEN_8086&DEV_24DB=C:\windows\inf\mshdc.inf
;IDE chipset driver for Gateway 700L
PCI\VEN_8086&DEV_244B=C:\windows\inf\mshdc.inf
;IDE chipset driver for Dell GX745
PCI\VEN_8086&DEV_2820=C:\i\d\c\ich8ide.inf
PCI\VEN_8086&DEV_2825=C:\i\d\c\ich8ide.inf
; SATA chipset driver for Dell GX755
PCI\VEN_8086&DEV_2922=C:\i\d\dl\gx755\ide\iaahci.inf

In terms of the sysprep switches, I'm running: sysprep -pnp -mini -reseal

Adam

[rogierd]

Adam

We are working for weeks to create an image that will work on 755 and 745.
Your post suggests that you have an image that works on both computer types
(with 755 in AHCI mode). I've uses your sysprep inf settings but still no
luck. Have you made other changes to let it work ?
I hope you can help me out.

Rogier

Post by Adam Leinss

Post by AJ
Were you SP3 patched or did you do the rest of the windows updates
that have released since when you sysprep'd. Did you build the MASS
STORAGE SECTION, did you run Mini-Setup?

Every time I update our image, I would apply the updates from Windows
update and document them in a text file in the image.
I then applied the full SP3 against the image (which was at the SP2
level).
Since SP3, I've applied all the updates from Windowsupdate.com (except
Internet Explorer 7) and still no issues.
[SysprepMassStorage]
;IDE chipset driver for Dell Optiplex 280
PCI\VEN_8086&DEV_266F=C:\i\d\c\ich6ide.inf
;IDE chipset driver for Gateway 600YGR
PCI\VEN_8086&DEV_248A=C:\windows\inf\mshdc.inf
;IDE chipset driver for Dell Latitude D610
PCI\VEN_8086&DEV_2653=C:\windows\inf\mshdc.inf
;IDE chipset driver for Gateway ESX 500L
PCI\VEN_8086&DEV_24CB=C:\i\d\c\ich4ide.inf
;IDE chipset driver for Dell Latitude D600
PCI\VEN_8086&DEV_24CA=C:\i\d\c\ich4ide.inf
;IDE chipset driver for Dell GX620, GX520
PCI\VEN_8086&DEV_27C0=C:\i\d\c\ich7ide.inf
PCI\VEN_8086&DEV_27DF=C:\i\d\c\ich7ide.inf
;IDE chipset driver for Dell Optiplex GX270
PCI\VEN_8086&DEV_24D1=C:\windows\inf\mshdc.inf
PCI\VEN_8086&DEV_24DB=C:\windows\inf\mshdc.inf
;IDE chipset driver for Gateway 700L
PCI\VEN_8086&DEV_244B=C:\windows\inf\mshdc.inf
;IDE chipset driver for Dell GX745
PCI\VEN_8086&DEV_2820=C:\i\d\c\ich8ide.inf
PCI\VEN_8086&DEV_2825=C:\i\d\c\ich8ide.inf
; SATA chipset driver for Dell GX755
PCI\VEN_8086&DEV_2922=C:\i\d\dl\gx755\ide\iaahci.inf
In terms of the sysprep switches, I'm running: sysprep -pnp -mini -reseal
Adam

[a***@hotmail.com]

Post by rogierd
Adam
We are working for weeks to create an image that will work on 755 and 745.
Your post suggests that you have an image that works on both computer types
(with 755 in AHCI mode). I've uses your sysprep inf settings but still no
luck. Have you made other changes to let it work ?
I hope you can help me out.

The filename is deceiving: we set both the GX745 and GX755 to ATA mode
in the BIOS, otherwise we get the famous 7B stop code.

DEV_2922 just happens to be in that file. The problem that did take
hours on end to solve was getting the NIC driver to work within WinPE
on the GX755. It appears the GX755 uses the same Gigabit drivers as
models past, but with a new device ID....a device ID not present in
the older drivers.

Otherwise, both our Vista and XP images work just fine on the
GX755/745.

Adam

[rogierd]

Adam

Thank you for your response. I think we give up on this.

Rogier

Post by a***@hotmail.com

Adam
We are working for weeks to create an image that will work on 755 and 745..
Your post suggests that you have an image that works on both computer types
(with 755 in AHCI mode). I've uses your sysprep inf settings but still no
luck. Have you made other changes to let it work ?
I hope you can help me out.

The filename is deceiving: we set both the GX745 and GX755 to ATA mode
in the BIOS, otherwise we get the famous 7B stop code.
DEV_2922 just happens to be in that file. The problem that did take
hours on end to solve was getting the NIC driver to work within WinPE
on the GX755. It appears the GX755 uses the same Gigabit drivers as
models past, but with a new device ID....a device ID not present in
the older drivers.
Otherwise, both our Vista and XP images work just fine on the
GX755/745.
Adam

[rogierd]

We finally found a solution for creating an image for all types of Dell
Optiplex including Optiplex 755 ith AHCI enabled .

Create an XP cd with SP3 slipstreamed en the MassStorage driverpack
intergrated http://driverpacks.net/DriverPacks/DriverPack.php?pag=m (howto
also on this site).
Install a 755 with this XP SP3 CD. Capture the PC with SMS.
Content of the Sysprep.inf:
;SetupMgrTag
[Unattended]
KeepPageFile=0
OemSkipEula=Yes
ExtendOemPartition=1
DriverSigningPolicy=Ignore
OemPnPDriversPath=.......
UpdateInstalledDrivers=Yes
UpdateUPHAL=ACPIAPIC_UP,%windir%\Inf\hal.inf


[Display]
BitsPerPel=32
Xresolution=1024
YResolution=768
Vrefresh=70

[Sysprep]
BuildMassStorageSection = Yes

[SysprepMassStorage]

Post by rogierd
Adam
Thank you for your response. I think we give up on this.
Rogier

Post by a***@hotmail.com

Adam
We are working for weeks to create an image that will work on 755 and 745..
Your post suggests that you have an image that works on both computer types
(with 755 in AHCI mode). I've uses your sysprep inf settings but still no
luck. Have you made other changes to let it work ?
I hope you can help me out.

The filename is deceiving: we set both the GX745 and GX755 to ATA mode
in the BIOS, otherwise we get the famous 7B stop code.
DEV_2922 just happens to be in that file. The problem that did take
hours on end to solve was getting the NIC driver to work within WinPE
on the GX755. It appears the GX755 uses the same Gigabit drivers as
models past, but with a new device ID....a device ID not present in
the older drivers.
Otherwise, both our Vista and XP images work just fine on the
GX755/745.
Adam

[jjjustinnn]

I have the same issue.
I'm assuming there is some way to re-copy everything to the DefaultUser
Porfile after sysprep runs, but I've tried several ways, and sometimes it
just seems to do different things.
I have the same folder c:\program files\program shortcuts
I also have a c:\windows\system32\config\systemprofile\ folder
I also have c:\preinstall\Default User set up like a profile.

I can't seem to figure out where the heck sysprep is putting everything, and
then how to get it back after the image is burned.

Have you had any luck in understanding what's happening since you first had
this issue?
Thanks

Post by AJ
I have read every thread I can find on this and still no-one has reported the
behavior I am experiencing with my SP3 deployment.
I have a Pre-Sysprep'd SP2 image, I upgrade it to SP3 using the full SP3
download (not Windows Update), then fully patch any other post SP3 hotfixes
using Windows Update.
I download and extract Deploy.cab and overwrite my current c:\sysprep files
with the new versions.
I have already configured my Administrator profile with different folder
views and placed several tools (like process explorer and process monitor) on
the desktop. I also have already created a local user named Default and
customized it with user views, wallpaper and a smaller customized Start Menu.
I reboot and capture my "new Pre-Sysprep" image. I log on to Windows as
Administrator to copy my customized user named Default over the Default User
profile and grant Authenticated Users permissions. I then delete the user
named Default and its directory from the workstation.
I have a .bat file in the sysprep directory named doprep.bat which contains
"%SystemDrive%\Sysprep\Sysprep.exe" -mini -quiet -reseal -forceshutdown
I have used this process since Windows 2000 and I don’t want to get in to a
discussion of its merits or downsides.
Everything should work as it did XP SP2 with the KB887816 patch installed,
but it doesn’t.
Administrator profile gets deleted and recreated sometime during Mini-Setup,
I can confirm this by files in the profile being present in my “post Sysprep”
version of the image when I use Ghost Explorer to view the .gho file.
Files on the Administrator desktop get moved to the folder C:\Program
Files\Program Shortcuts, this folder did not exist before Mini-Setup ran
using the above .gho as a reference.
The Default User profile works exactly as expected with the exception of its
desktop shortcuts which get moved to the C:\Program Files\Program Shortcuts
folder and Administrative Tools is in the start menu when it was not present
in the .gho file.
I thought I could get my Default User working by moving the desktop
shortcuts over to the All Users profile, but they were also moved to the
C:\Program Files\Program Shortcuts folder as well.
Any help would be appreciated, I have run out of options and my deadline is
near.
Thanks in advance!
AJ

[Randy]

Going to jump in. We had a problem with the "Default User" getting changed
on each Sysprep. I developed a way to keep it the way I wanted it. Once I
have the "Default User" set the way I want, before Sysprep, I copy it to the
same "Documents and Settings" folder, but as "DefUser". In Sysprep.inf,
there is an entry like this:
[GuiRunOnce]
"C:\WINDOWS\Options\Finalize.vbs"

Here is Finalize.vbs:
Const Folder1 = "C:\Documents and Settings\Default User"
Const Folder2 = "C:\Documents and Settings\DefUser"
Const Folder3 = "C:\Documents and Settings\Default.Org"

Dim Fso

set Fso = CreateObject("Scripting.FilesystemObject")

fso.MoveFolder Folder1, Folder3
if err.number <> 0 then
wscript.echo "Renaming Default User failed."
Wscript.quit(1)
end if

fso.MoveFolder Folder2, Folder1
if err.number <> 0 then
wscript.echo "Renaming DefUser to Default User failed."
wscript.quit(1)
end if

set fso = nothing
err.clear

When you first log onto the "new" computer (sysprep done and rebooted), log
on as Administrator. The script then renames "Default User" to
"Default.Org", and then renames "DefUser" to "Default User". Then, you can
log out, log on as normal user - and all is the way YOU want it.

Randy Reimers

Post by jjjustinnn
I have the same issue.
I'm assuming there is some way to re-copy everything to the DefaultUser
Porfile after sysprep runs, but I've tried several ways, and sometimes it
just seems to do different things.
I have the same folder c:\program files\program shortcuts
I also have a c:\windows\system32\config\systemprofile\ folder
I also have c:\preinstall\Default User set up like a profile.
I can't seem to figure out where the heck sysprep is putting everything, and
then how to get it back after the image is burned.
Have you had any luck in understanding what's happening since you first had
this issue?
Thanks

Post by AJ
I have read every thread I can find on this and still no-one has reported the
behavior I am experiencing with my SP3 deployment.
I have a Pre-Sysprep'd SP2 image, I upgrade it to SP3 using the full SP3
download (not Windows Update), then fully patch any other post SP3 hotfixes
using Windows Update.
I download and extract Deploy.cab and overwrite my current c:\sysprep files
with the new versions.
I have already configured my Administrator profile with different folder
views and placed several tools (like process explorer and process monitor) on
the desktop. I also have already created a local user named Default and
customized it with user views, wallpaper and a smaller customized Start Menu.
I reboot and capture my "new Pre-Sysprep" image. I log on to Windows as
Administrator to copy my customized user named Default over the Default User
profile and grant Authenticated Users permissions. I then delete the user
named Default and its directory from the workstation.
I have a .bat file in the sysprep directory named doprep.bat which contains
"%SystemDrive%\Sysprep\Sysprep.exe" -mini -quiet -reseal -forceshutdown
I have used this process since Windows 2000 and I don't want to get in to
a
discussion of its merits or downsides.
Everything should work as it did XP SP2 with the KB887816 patch installed,
but it doesn't.
Administrator profile gets deleted and recreated sometime during Mini-Setup,
I can confirm this by files in the profile being present in my "post
Sysprep"
version of the image when I use Ghost Explorer to view the .gho file.
Files on the Administrator desktop get moved to the folder C:\Program
Files\Program Shortcuts, this folder did not exist before Mini-Setup ran
using the above .gho as a reference.
The Default User profile works exactly as expected with the exception of its
desktop shortcuts which get moved to the C:\Program Files\Program Shortcuts
folder and Administrative Tools is in the start menu when it was not present
in the .gho file.
I thought I could get my Default User working by moving the desktop
shortcuts over to the All Users profile, but they were also moved to the
C:\Program Files\Program Shortcuts folder as well.
Any help would be appreciated, I have run out of options and my deadline is
near.
Thanks in advance!
AJ

[jjjustinnn]

Thanks Randy!
I ended up doing the same sort of thing.
I had a lot of frustration with the registry being changed by GP, but I
finally decided to setup the default profile off the domain, and then let the
GP change everything after the profile was copied using this method.
So far so good.

Post by Randy
Going to jump in. We had a problem with the "Default User" getting changed
on each Sysprep. I developed a way to keep it the way I wanted it. Once I
have the "Default User" set the way I want, before Sysprep, I copy it to the
same "Documents and Settings" folder, but as "DefUser". In Sysprep.inf,
[GuiRunOnce]
"C:\WINDOWS\Options\Finalize.vbs"
Const Folder1 = "C:\Documents and Settings\Default User"
Const Folder2 = "C:\Documents and Settings\DefUser"
Const Folder3 = "C:\Documents and Settings\Default.Org"
Dim Fso
set Fso = CreateObject("Scripting.FilesystemObject")
fso.MoveFolder Folder1, Folder3
if err.number <> 0 then
wscript.echo "Renaming Default User failed."
Wscript.quit(1)
end if
fso.MoveFolder Folder2, Folder1
if err.number <> 0 then
wscript.echo "Renaming DefUser to Default User failed."
wscript.quit(1)
end if
set fso = nothing
err.clear
When you first log onto the "new" computer (sysprep done and rebooted), log
on as Administrator. The script then renames "Default User" to
"Default.Org", and then renames "DefUser" to "Default User". Then, you can
log out, log on as normal user - and all is the way YOU want it.
Randy Reimers

Post by jjjustinnn
I have the same issue.
I'm assuming there is some way to re-copy everything to the DefaultUser
Porfile after sysprep runs, but I've tried several ways, and sometimes it
just seems to do different things.
I have the same folder c:\program files\program shortcuts
I also have a c:\windows\system32\config\systemprofile\ folder
I also have c:\preinstall\Default User set up like a profile.
I can't seem to figure out where the heck sysprep is putting everything, and
then how to get it back after the image is burned.
Have you had any luck in understanding what's happening since you first had
this issue?
Thanks

Post by AJ
I have read every thread I can find on this and still no-one has reported the
behavior I am experiencing with my SP3 deployment.
I have a Pre-Sysprep'd SP2 image, I upgrade it to SP3 using the full SP3
download (not Windows Update), then fully patch any other post SP3 hotfixes
using Windows Update.
I download and extract Deploy.cab and overwrite my current c:\sysprep files
with the new versions.
I have already configured my Administrator profile with different folder
views and placed several tools (like process explorer and process monitor) on
the desktop. I also have already created a local user named Default and
customized it with user views, wallpaper and a smaller customized Start Menu.
I reboot and capture my "new Pre-Sysprep" image. I log on to Windows as
Administrator to copy my customized user named Default over the Default User
profile and grant Authenticated Users permissions. I then delete the user
named Default and its directory from the workstation.
I have a .bat file in the sysprep directory named doprep.bat which contains
"%SystemDrive%\Sysprep\Sysprep.exe" -mini -quiet -reseal -forceshutdown
I have used this process since Windows 2000 and I don't want to get in to
a
discussion of its merits or downsides.
Everything should work as it did XP SP2 with the KB887816 patch installed,
but it doesn't.
Administrator profile gets deleted and recreated sometime during Mini-Setup,
I can confirm this by files in the profile being present in my "post
Sysprep"
version of the image when I use Ghost Explorer to view the .gho file.
Files on the Administrator desktop get moved to the folder C:\Program
Files\Program Shortcuts, this folder did not exist before Mini-Setup ran
using the above .gho as a reference.
The Default User profile works exactly as expected with the exception of its
desktop shortcuts which get moved to the C:\Program Files\Program Shortcuts
folder and Administrative Tools is in the start menu when it was not present
in the .gho file.
I thought I could get my Default User working by moving the desktop
shortcuts over to the All Users profile, but they were also moved to the
C:\Program Files\Program Shortcuts folder as well.
Any help would be appreciated, I have run out of options and my deadline is
near.
Thanks in advance!
AJ