Task Sequence - Run Command Line without Package
You could create one package that holds all your batch/script files and use the Run command line step. Just link the same package to all your Run Command Line step.
July 10th, 2011 8:25am

U can also use "Run this step as the following account" to run the script from a file share. Make sure this account has the permissions on the share. Try to always use UNC paths when possible.
Free Windows Admin Tool Kit Click here and download it now
July 10th, 2011 8:49am

I'm trying to run a .vbs file in a task sequence without placing it in a package. I have set the "Start in" path to "E:\path to vbs file" and I'm getting an error saying invalid directory. My command line is "file.vbs @varraible". I have confirmed that manually running the command from the right directory does indeed work. Do I need to use cmd /c or csript.exe in order for this to work? If it's just a one liner like this than id rather not have to place it in a package. Thanks.
July 10th, 2011 9:57am

E: is on the local machine you are trying to run it from? John Marcum | http://myitforum.com/cs2/blogs/jmarcum/|
Free Windows Admin Tool Kit Click here and download it now
July 10th, 2011 10:14am

E: is the drive on our SCCM server containing all of our packages and other source files, including the .vbs I'm trying to run.
July 10th, 2011 10:20am

Task Sequences run on the client, so the path specified is local to it not the site server.Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys
Free Windows Admin Tool Kit Click here and download it now
July 10th, 2011 10:38am

Ok that makes sense. My angle was that, in my opinion, it seems to take more work to create a package and is overkill for a one line command. I'm working on a task sequence that has a lot of steps involving batch files and scripts that do very basic things and I figured being able to manage it right from the task sequence would be easier. Though in the long run if I ever needed to access these steps in other task sequences via a package is indeed the best way to go. Thanks Jason
July 10th, 2011 10:39am

Hmm I tried the UNC path, but had the same error.
Free Windows Admin Tool Kit Click here and download it now
July 10th, 2011 10:49am

The task sequence runs as the local SYSTEM of the target computer and so will not have access to any given UNC. Is there a reason you don't supply the batch file in a package? It makes things easier and using UNCs defeats the scale-out design and purpose of using DPs.Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys
July 10th, 2011 8:09pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics