Skip to content

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

Featured Replies

Hi,

 

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.

 

Thanks,

  • 5 months later...
  • 1 year later...

I am experiencing something similar as well. Did either of you ever resolve this?

Join the conversation

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

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.