Sign in
 
HomeLibraryWikiLearnGalleryDownloadsSupportForumsBlogs
Resources for IT Professionals >
> 
> 
> 
LTI Deployment in MDT 2012 - WinPE - 'cscript' is not a recognized internal or external command

Proposed LTI Deployment in MDT 2012 - WinPE - 'cscript' is not a recognized internal or external command

  • Tuesday, October 16, 2012 8:49 PM
     
     
    Sign In to Vote
    0

    As the title states, I'm attempting to deploy a custom (.wim) image through MDT 2012 using the LiteTouch Image (LTI) method. I have captured the .wim off of an existing machine, imported the .wim into Deployment workbench and created a Standard Client Task Sequence. After updating the Deployment Share, I created the bootable LTI media from C:\DeploymentShare$\Boot\LiteTouchPE_x86.iso.

    The issue I'm running into is when I boot to the media, it brings up the WinPE cmd prompt, where I'm supposed to map the DeploymentShare$\Scripts directory  as a network drive according to the directions. When I do that I'm supposed to run 'cscript LiteTouch.vbs'.

    .... When I do this is says " 'cscript' is not a recognized internal or external command."

    So I decided to try to drop the cscript.exe, vbscript.dll, and jscript.dll from my C:\Windows\System32 folder into the DeploymentShare$\Scripts directory.

    From there I ran "regsrv32 vbscript.dll" and "regsrv32 jscript.dll" and I keep receiving the message "There is no script engine for file extension '.vbs' "

    I've tried mapping Z: to %MyDeskPC%:\Windows\System32 to try to get it to pull cscript.exe from there and still got the same error message.

    I don't know how to get this .vbs script to run from the command prompt!

    Tim

     

All Replies

  • Wednesday, October 17, 2012 8:43 PM
     
     
    Sign In to Vote
    0
    Anyone have anything I can try? Any ideas?

    Tim

     
  • Wednesday, October 17, 2012 10:32 PM
     
     
    Sign In to Vote
    0

    The lite touch disk is supposed to run the scripts and connect to the deployment share automatically. Somethings wrong there.

    Have you imported an OS into the deployment workbench and created a task sequence? If not, do so.

    Then, delete the entire contents of the boot folder in your deployment share. Then update the share to recreate the ISO again.

    Blog: http://scriptimus.wordpress.com

     
  • Friday, October 19, 2012 2:53 PM
     
     Proposed
    Sign In to Vote
    0
    As you see in my previous post, I tried all of that already. But I found the issue. I tried reinstalling ADK and MDT like I found in a different post and that still didn't work. After looking at the dism.log and seeing access denied errors when building the iso during the updating of the deployment share, I did some research and tested a few things and it was actually my antivirus software blocking the program from adding certain critical components to the iso. disabled my anti-virus, built my iso, and it worked like a charm. Thanks for the input!
    • Proposed As Answer by Stephan Schwarz Saturday, October 20, 2012 12:36 PM
    •  
     
  • Friday, October 19, 2012 10:44 PM
     
     
    Sign In to Vote
    0

    Cool. I thought there was something goofy with the boot disk hence my suggestion to recreate it. Anti-virus? Who knew?

    :)

    Blog: http://scriptimus.wordpress.com