Jump to content


Install Package vs Run Command Line with package in Task Sequence SCCM 2012

Recommended Posts



In SCCM 2012, we have a task sequence that installs package in the very end after setting up operating system. We have tried two approaches:

1. Using Install package step (the package has a program associated with it which executes the vb script eventually)

2. Using Run Command line step (in command line executing script and attach the package.


The second approach executes fine but the first approach halts on executing the script (sometime it hangs there forever). A few times we have seen an error that it doesn't find the file specified (in smsts.log)


Since the script is executed in secondapproach, there should not be any issue in script. Any help, suggestion is welcomed for first approach because that's how we want to install package as it works in SCCM 2007.


FYI, this is on SCCM 2012 RC build.



Share this post

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.