none
vbscripts not running RRS feed

  • Question

  • Hi guys,

    We've been running a hybrid 2012 / 2013 MDT setup due to legacy requirements and have recently installed update 2 to MDT2013.

    It looks as though none of our vbscripts in task sequences are running in MDT2013. MDT2012 is fine.

    Removing the 'continue on error' switch has no effect as it looks as though the builds think everything is running successfully.

    Our syntax etc is identical to what we are using in 2012.

    Has anybody come across this that could shed some light on the issue or is there something simple that's been missed.

    Thanks in advance for any help.

    Cheers

    Monday, June 20, 2016 7:37 AM

All replies

  • Were these vbscripts that ran applications? If so, what does ztiapplications.log show?  If not, I assume they lived in the scripts directory.  Does the ltiCopyScripts.log show those scripts being copied over?  If so, the smsts log file (I think I got the file name right) might have some information.
    Monday, June 20, 2016 2:45 PM
  • A little more information after more digging.

    The lti / zti mdt scripts are copying over successfully, the scripts that aren't running are our vb scripts located on a network share. CMD's run fine but vbs' are not !

    The scripts are mainly used for copying files and placing shortcuts etc.

    The task sequence syntax is identical to what we have in our 2012 environment. Wierd !

    Tuesday, June 21, 2016 11:18 AM
  • Hi guys,

    We've been running a hybrid 2012 / 2013 MDT setup due to legacy requirements and have recently installed update 2 to MDT2013.

    I can't tell you how much this concerns me. Exactly what do you mean by "Hybrid 2012 / 2013" environment?

    A MDT Deployment share should be *either* MDT 2012 (why?) or MDT 2013, with *NO* mixing of scripts.  

    [...]

    Removing the 'continue on error' switch has no effect as it looks as though the builds think everything is running successfully.

     WHAT!?!?! I sure hope you are not commenting out the "on error resume next" and "on error goto 0" commands in the MDT scripts. They are there for a reason, if you are getting random errors, commenting them out will make them even MORE random.

    Has anybody come across this that could shed some light on the issue or is there something simple that's been missed.

    First off, there is no reason why anyone should use MDT 2012 Update 1, MDT 2013 will easily support Windows 7 and above. However, if you wanted to run MDT 2012 Update 1, then I would keep it on a separate share.


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

    Wednesday, June 22, 2016 5:04 AM
    Moderator
  • I think I'm causing you unnecessary concern with the 'hybrid' comment.

    They are 2 separate standalone MDT entities. We've retained 2012 for some legacy OS deployment due to software requirements on some VERY legacy machines which we cant phase out yet for political reasons.

    The continue on error I refer to is the radio button on the task sequence options to continue with building if the step errors. I was hoping this would give us a few more clues as to why the task sequence appears to be ignoring the command lines calling the vb scripts from the network share.


    • Edited by G_Burton Wednesday, June 22, 2016 8:02 AM
    Wednesday, June 22, 2016 8:00 AM
  • If you have custom scripts, then you may need to log the output if they are failing.

    MDT does not do a very good job of capturing all errors from vbscripts within the Task Sequence.

    I wrote this script to assist with capturing errors:

    https://tmintner.wordpress.com/2009/11/05/capturing-debug-information-from-client-scripts/

    http://mdtex.codeplex.com/SourceControl/latest#Templates/Distribution/Scripts/ZTICScript.cmd

    http://mdtex.codeplex.com/SourceControl/latest#Templates/Distribution/Scripts/ZTICScript_log.wsf


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

    Wednesday, June 22, 2016 4:29 PM
    Moderator
  • Getting a little more bizarre now. As a test we added a cmd to the task sequence to copy all of our custom scripts to the C:\Minint\scripts folder to match the location of the default MDT scripts copied.

    Using the same syntax in the command line to call the scripts still gives no result or error and the vbs' just don't run !

    We're banging our heads against the wall now !

    It's a little frustrating as I've sort of inherited the setup without having much experience, and it's just worked up until now !

    Thursday, June 23, 2016 2:57 PM