none
CSCRIPT.EXE is not recognised as a valid command while creating ISO RRS feed

  • Question

  • Hi ,

    I have a problem when creating ISO Images for my Deployment share.

    When I try to regenerate the image, it throws an error at the end of ISO Creation saying that Cscript.exe is not recognized as Internal or External command.

    Even after this Error ISO image creation is completed successfully and when i try using this image for deployment the Build dosent continue after the first reboot.

    could someone please advise me on this issue

    Friday, February 13, 2015 12:37 AM

Answers

  • During buildout of the LitetouchPE_x??.wim images, there are places where the MDT console can run custom scripts allowing users to inject custom processing into the WINPE images, that's why it's trying to run cscript.exe.

    If you don't have any custom scripts, It shouldn't affect anything, so you *could* continue.

    WDSUtil.exe is used to enable Multicasting, again, if you don't use Multicasting, you can continue.

    Really, your environment shouldn't do this. Can you run cscript.exe programs locally? Are you joined to a domain? If so, specifically, what are the GPO settings around vbscript?

    Create a text file: Hello.vbs:

    wscript.echo "Hello WOrld"
    

    Save the file and run the command:

    cscript.exe <path>\hello.vbs

    IF it works, I don't know what's going on.

    If it does not work, try re-installing MDT on a new OS.


    Keith Garner - Principal Consultant [owner] - http://DeploymentLive.com

    Monday, February 16, 2015 6:56 AM
    Moderator

All replies

  • Nirmal,

    You might have more luck getting help by attaching the full log file.

    Here is where my log file was saved, but yours would be slightly different:

    "C:\Users\<Username>\AppData\Local\Temp\Update-MDTMedia.1968\Update-MDTMedia-97250.log"


    -BrianG (http://supportishere.com)

    Friday, February 13, 2015 4:22 PM
  • Do you have antivrus? Virus software will block cscript.. Disable the AV, build the ISO again and it should work!
    Friday, February 13, 2015 6:23 PM
  • Hi ,

    It dint work even after uninstalling the anti virus software.

    Could you please advice , where can i find logs for these errors.

    The below is the output shown when rebuilding the Deployment share

    Copy: C:\Program Files\Microsoft Deployment Toolkit\Samples\Background.bmp to C:\Users\nirmal\AppData\Local\Temp\2\MDTUpdate.6796\Mount\Windows\system32\winpe.bmp
    'reg.exe' is not recognized as an internal or external command,
    operable program or batch file.

    Exit code = 1

    REG LOAD failed, rc = 1.
    'cscript.exe' is not recognized as an internal or external command,
    operable program or batch file.

    Exit code = 1

    Copying WIM to the deployment share.
    'cscript.exe' is not recognized as an internal or external command,
    operable program or batch file.

    Exit code = 1


    === Completed processing platform x64 ===


    === Enabling multicast ===

    'wdsutil.exe' is not recognized as an internal or external command,
    operable program or batch file.

    Exit code = 1

    Unable to create multicast namespace "LogisticsShare$", rc = 1.

    === Processing complete ===

    Sunday, February 15, 2015 3:15 AM
  • During buildout of the LitetouchPE_x??.wim images, there are places where the MDT console can run custom scripts allowing users to inject custom processing into the WINPE images, that's why it's trying to run cscript.exe.

    If you don't have any custom scripts, It shouldn't affect anything, so you *could* continue.

    WDSUtil.exe is used to enable Multicasting, again, if you don't use Multicasting, you can continue.

    Really, your environment shouldn't do this. Can you run cscript.exe programs locally? Are you joined to a domain? If so, specifically, what are the GPO settings around vbscript?

    Create a text file: Hello.vbs:

    wscript.echo "Hello WOrld"
    

    Save the file and run the command:

    cscript.exe <path>\hello.vbs

    IF it works, I don't know what's going on.

    If it does not work, try re-installing MDT on a new OS.


    Keith Garner - Principal Consultant [owner] - http://DeploymentLive.com

    Monday, February 16, 2015 6:56 AM
    Moderator