Home / server / Questions / 246321
In Process
Mitch
Asked: 2011-03-12 10:03:49 +0800 CST

MDT 2010 Litetouch.vbs Fails to Launch

  • 772

I have the custom image captured. Import the image and files. Prepare the customsettings.ini and the boot.ini to minimize the questions the deployment team will need to answer. Everything works like a charm on virtual machines but when I map to the scripts folder on the deployment share and double-click litetouch.vbs it creates the c:\minint folder, subfolders, and a couple of log files then nothing. Here's what the log files look like:

<![LOG[Property LogPath is now = C:\MININT\SMSOSD\OSDLOGS]LOG]!><time="15:54:28.000+000" date="03-08-2011" component="LiteTouch" context="" type="1" thread="" file="LiteTouch"> <![LOG[Property CleanStart is now = ]LOG]!><time="15:54:28.000+000" date="03-08-2011" component="LiteTouch" context="" type="1" thread="" file="LiteTouch"> <![LOG[Microsoft Deployment Toolkit version: 5.1.1642.01]LOG]!><time="15:54:28.000+000" date="03-08-2011" component="LiteTouch" context="" type="1" thread="" file="LiteTouch"> <![LOG[Property Debug is now = FALSE]LOG]!><time="15:54:28.000+000" date="03-08-2011" component="LiteTouch" context="" type="1" thread="" file="LiteTouch"> <![LOG[GetAllFixedDrives(False)]LOG]!><time="15:54:28.000+000" date="03-08-2011" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">

Anyone encounter this before or know what might be happening/not happening and can direct me in the right way? I've only found a couple of other references to this anywhere and they had no solution/cause listed either. I'm stumped.

mdt-2010

2 Answers

  1. so you've created the reference machine and successfully captured it by correctly connecting to the deployment share\scripts folder and running litetouch.vbs. You've now created a "deploy WIM" task sequence and are launching it by connecting to the share again in Windows? As far as I know you can't build a machine that way. You need to mount your boot WIM in Windows Deployment Services and launch it by booting from the network (usually by pressing F12 at the BIO screen). Does that make sense or have I misunderstood you?

    • 0

  2. I've seen LiteTouch.wsf fail to launch, or fail to get anywhere if it hasn't been run with elevated privileges. Running it as an admin worked for me in that scenario.

    • 0