IIS and Sysprep

[David Dixon]

I've just encountered a problem with Windows XP (service pack 2) and
Sysprep. After loading a machine with XP, including IIS and XP SP2, I then
run Sysprep v2.0 (latest available) to prepare for imaging. After dumping
the Ghost image I reboot the machine to XP. At this point the World Wide
Web Publishing service fails to start. Attempts to manually start it result
in an error, "Could not stat the World Wide Web Publishing service on Local
Computer. Error 3: The system cannot find the path specified."
This problem only occurs on XP machines that have SP2 installed. BTW,
we disable the SP2 firewall before running Sysprep. Our only fix is to
remove IIS and reinstall IIS. The service starts OK after that. This is a
pain because our image includes changes to IIS that are a drag to have to
reconfigure after reinstalling IIS.
Has anyone else encountered this problem with WWWP failing after SP2
installation and Sysprep running? Anyone have any ideas? We've never seen
this error message before. Thanks!

David Dixon

 

[Greg F]

I've just encountered a problem with Windows XP (service pack 2) and
Sysprep. After loading a machine with XP, including IIS and XP SP2, I then
run Sysprep v2.0 (latest available) to prepare for imaging. After dumping
the Ghost image I reboot the machine to XP. At this point the World Wide
Web Publishing service fails to start. Attempts to manually start it result
in an error, "Could not stat the World Wide Web Publishing service on Local
Computer. Error 3: The system cannot find the path specified."
This problem only occurs on XP machines that have SP2 installed. BTW,
we disable the SP2 firewall before running Sysprep. Our only fix is to
remove IIS and reinstall IIS. The service starts OK after that. This is a
pain because our image includes changes to IIS that are a drag to have to
reconfigure after reinstalling IIS.
Has anyone else encountered this problem with WWWP failing after SP2
installation and Sysprep running? Anyone have any ideas? We've never seen
this error message before. Thanks!

David Dixon

Hey David,
If you do not specify your firewall options in sysprep then what
happens is by default it will be "turned on" once you ghost your image
onto a computer and sysprep finishes regardless of what firewall
setting you specified in your image.

HTH,
Greg

 

[Guest]

I have the same problem creating a image. I did modify netfw.inf and I did
add this to sysprep "Run Once" command. After...The firewall is not active
but w3scv is still not starting up.