Task Sequence AFTER Sysprep

espo9

I am trying to have a handful of hardware-specific tasks run LOCALLY AFTER the machine has been sysprepped and shut down. This works fine as long as my distribution share is available. The line in Sysprep.inf: "cscript.exe C:\MININT\Scripts\LiteTouch.wsf /start" works great, but tries to connect. If My MDT 2008 server is not in use 6 months from now, my images will never complete. Why is LiteTouch reaching out to my networdk share? There is a copy of TS.xml locally?

I am only using MDT for the sole purpose of CREATING our base image. It will not be used for deployment in any way (as of now).

Thanks
Scott

n3w813

Just remove or comment out the line in sysprep.inf. This line adds the command to the registry to run on first logon.

[GuiRunOnce]
"cscript.exe C:\MININT\Scripts\LiteTouch.wsf /start"

espo9

My tasks will not continue if I do that. There were remaining tasks (based on model) that need to run AFTER the captured image is deployed (to any machine) without contacting my original BDD Server.

n3w813

I don't see how that is possible WITH the use of MDT/BDD since it always contacts the server when the task sequencer is ran for the first time.

I guess you can copy the files locally before the image is captured for the different tasks you want to run. Then add the tasks/scripts/etc to the [GuiRunOnce] section or in the 'Startup' folder in the Start Menu (be sure to remove them after the installs).