Steven Griffiths
2009-01-05 16:00:01 UTC
I've created a simple Vista reference machine in Hyper-V using MDT. As I'm
planning on using the SYSPRED-ed version of the reference machine as a base
Hyper-V image, I wanted to strip the image of all performance sapping
features and basically make it look like XP!
My unattend.xml does what I need it to and the reference machine has the
Classic look-and-feel and no wallpaper - just a plain blue background. I have
created a slightly different unattend file to use when running SYSPREP as I
just want to be prompted for the computer name. All this appears to work, but
when the desktop appears, the default wallpaper is present rather than the
plain blue desktop.
Looking in UnattendGC\Setupact.log I can see the following:
2009-01-05 15:29:44, Info [msoobe.exe] Found EULA:
[C:\Windows\system32\en-US\Licenses\_Default\Business\license.rtf]
2009-01-05 15:45:05, Info [msoobe.exe] Commit:
setting computer name [VISTA01]
2009-01-05 15:45:06, Info [msoobe.exe] Successfully
signalled event to start up services
2009-01-05 15:45:08, Info [msoobe.exe] Finalize:
setting wallpaper [C:\Windows\web\Wallpaper\img24.jpg]
2009-01-05 15:45:08, Info [msoobe.exe] Finalize:
setting windows error reporting [0x1]
2009-01-05 15:45:08, Info [msoobe.exe] Running
mandatory tasks
2009-01-05 15:45:13, Info [msoobe.exe] Successfully
installed product key
2009-01-05 15:45:13, Info [msoobe.exe] Configuring
service netprofm for auto start
2009-01-05 15:45:21, Info [msoobe.exe] Successfully
changed configuration for service netprofm
2009-01-05 15:45:21, Info [msoobe.exe] Successfully
verified and committed UI language settings
2009-01-05 15:45:21, Info [msoobe.exe] Starting
service netprofm
2009-01-05 15:45:22, Info [msoobe.exe] Service
netprofm reports as running
2009-01-05 15:45:26, Info [msoobe.exe] Successfully
notified UI language change
2009-01-05 15:45:59, Info [msoobe.exe] Successfully
removed administrator profile
2009-01-05 15:45:59, Info [msoobe.exe] Exiting
mandatory tasks... [0x0]
2009-01-05 15:46:01, Info [msoobe.exe] Mandatory
tasks previously completed
2009-01-05 15:46:01, Info [msoobe.exe] Exiting
mandatory tasks... [0x0]
2009-01-05 15:46:01, Info [msoobe.exe] Exiting...
[0x0]
2009-01-05 15:46:01, Info [oobeldr.exe]
OrchestrateUpdateImageState: Updating image state from
[IMAGE_STATE_UNDEPLOYABLE] --> [IMAGE_STATE_COMPLETE]
2009-01-05 15:46:01, Info [oobeldr.exe] OOBELdr.exe
exiting with code [0x0]...
2009-01-05 15:46:01, Info [windeploy.exe] Process
exited with exit code [0x0]
2009-01-05 15:46:01, Info [windeploy.exe]
WinDeploy.exe exiting with code [0x0]
In particular the entry: [msoobe.exe] Finalize: setting wallpaper
[C:\Windows\web\Wallpaper\img24.jpg]
I'm guessing this is taken from the mini-setup screen that prompts me for
the computer name. Is there any way to stop this behaviour and force there to
be no wallpaper when users logo on? BTW I'm using the CopyProfile setting to
ensure consistency for each user.
Steve G
planning on using the SYSPRED-ed version of the reference machine as a base
Hyper-V image, I wanted to strip the image of all performance sapping
features and basically make it look like XP!
My unattend.xml does what I need it to and the reference machine has the
Classic look-and-feel and no wallpaper - just a plain blue background. I have
created a slightly different unattend file to use when running SYSPREP as I
just want to be prompted for the computer name. All this appears to work, but
when the desktop appears, the default wallpaper is present rather than the
plain blue desktop.
Looking in UnattendGC\Setupact.log I can see the following:
2009-01-05 15:29:44, Info [msoobe.exe] Found EULA:
[C:\Windows\system32\en-US\Licenses\_Default\Business\license.rtf]
2009-01-05 15:45:05, Info [msoobe.exe] Commit:
setting computer name [VISTA01]
2009-01-05 15:45:06, Info [msoobe.exe] Successfully
signalled event to start up services
2009-01-05 15:45:08, Info [msoobe.exe] Finalize:
setting wallpaper [C:\Windows\web\Wallpaper\img24.jpg]
2009-01-05 15:45:08, Info [msoobe.exe] Finalize:
setting windows error reporting [0x1]
2009-01-05 15:45:08, Info [msoobe.exe] Running
mandatory tasks
2009-01-05 15:45:13, Info [msoobe.exe] Successfully
installed product key
2009-01-05 15:45:13, Info [msoobe.exe] Configuring
service netprofm for auto start
2009-01-05 15:45:21, Info [msoobe.exe] Successfully
changed configuration for service netprofm
2009-01-05 15:45:21, Info [msoobe.exe] Successfully
verified and committed UI language settings
2009-01-05 15:45:21, Info [msoobe.exe] Starting
service netprofm
2009-01-05 15:45:22, Info [msoobe.exe] Service
netprofm reports as running
2009-01-05 15:45:26, Info [msoobe.exe] Successfully
notified UI language change
2009-01-05 15:45:59, Info [msoobe.exe] Successfully
removed administrator profile
2009-01-05 15:45:59, Info [msoobe.exe] Exiting
mandatory tasks... [0x0]
2009-01-05 15:46:01, Info [msoobe.exe] Mandatory
tasks previously completed
2009-01-05 15:46:01, Info [msoobe.exe] Exiting
mandatory tasks... [0x0]
2009-01-05 15:46:01, Info [msoobe.exe] Exiting...
[0x0]
2009-01-05 15:46:01, Info [oobeldr.exe]
OrchestrateUpdateImageState: Updating image state from
[IMAGE_STATE_UNDEPLOYABLE] --> [IMAGE_STATE_COMPLETE]
2009-01-05 15:46:01, Info [oobeldr.exe] OOBELdr.exe
exiting with code [0x0]...
2009-01-05 15:46:01, Info [windeploy.exe] Process
exited with exit code [0x0]
2009-01-05 15:46:01, Info [windeploy.exe]
WinDeploy.exe exiting with code [0x0]
In particular the entry: [msoobe.exe] Finalize: setting wallpaper
[C:\Windows\web\Wallpaper\img24.jpg]
I'm guessing this is taken from the mini-setup screen that prompts me for
the computer name. Is there any way to stop this behaviour and force there to
be no wallpaper when users logo on? BTW I'm using the CopyProfile setting to
ensure consistency for each user.
Steve G