Solved

Cannot start litetouch.vbs from within WinPE - MDT 2010

Posted on 2010-08-17
2
1,819 Views
Last Modified: 2013-12-12
Here is my problem:

I just recently install and configured WDT 2010 via the TrueSec DeploymentCD tutorials.  Everything has gone ok up until this point.

I was able to create a capture only task and use it to make my .wim file.  I used that wim file on my usb key and was successful in imaging a laptop with the changes that I made.

I have configured and test the PXE server and it works to the best of my knowledge.  I can PXE boot various Dell machines and VM's.  It boots correctly into my boot image created in WDT.

At this point the process just craps out.  While watching the Videos in the Deployment CD I get to the point right before it asks me for credentials.  And it suddenly reboots.  At the point before the reboot I press F8 and check the bdd.log and litetouch.log.  There is nothing of importance in them.  They are the only two log files created before the reboot.  I went through and made sure that all the steps in the task sequence are set to continue on error.

Here is the strange thing.  Once booted into WinPE before the reboot I can press F8 and map a drive to my deployment share and kick this off: "cscript.exe litetouch.vbs" Granted I have to provide the net use statement with credentials.  But when I run that command IT WORKS!!!

Any ideas where I can track down the cause of litetouch not running in the WinPE session?  Thanks in advance
0
Comment
Question by:PDiBartolo
2 Comments
 
LVL 17

Accepted Solution

by:
James Haywood earned 500 total points
Comment Utility
Have you tried rebuilding your boot image fully and overwriting the one in WDS?
0
 

Author Closing Comment

by:PDiBartolo
Comment Utility
Funny thing is that in all my troubleshooting I was eventually getting to that answer at the same time you commented :)  

Right before this I had enabled a x64 boot image and added it to the pxe server.  I booted a vm up and used the x64 bit image instead of the x86.  it seemed to work just fine.  I had changed some values in the bootstrap.ini file.  I figured those changes are what fixed it.  

I then booted an old junk x86 machine up and got the same issue as before.  That was about the time I read this comment and deleted the x86 boot image from the pxe server and re-added it.  Voila it worked.  I guess in all my configuring I was updating the deployment share but not removing and re-adding the pxe boot image.  

Thanks
Phil
0

Featured Post

How to run any project with ease

Manage projects of all sizes how you want. Great for personal to-do lists, project milestones, team priorities and launch plans.
- Combine task lists, docs, spreadsheets, and chat in one
- View and edit from mobile/offline
- Cut down on emails

Join & Write a Comment

Suggested Solutions

Today, still in the boom of Apple, PC's and products, nearly 50% of the computer users use Windows as graphical operating systems. If you are among those users who love windows, but are grappling to keep the system's hard drive optimized, then you s…
Healthcare organizations in the United States must adhere to the guidance of both the HIPAA (Health Insurance Portability and Accountability Act) and HITECH (Health Information Technology for Economic and Clinical Health Act) for securing and protec…
This video demonstrates how to use each tool, their shortcuts, where and when to use them, and how to use the keyboard to improve workflow.
Video by: Tony
This video teaches viewers how to export a project from Adobe Premiere Pro and the various file types involved.

744 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

17 Experts available now in Live!

Get 1:1 Help Now