Wednesday, March 4, 2015

Deploy multiple packages using Dynamic Variables in a Task Sequence

When deploying packages within a task sequence you can add multiple steps with a single package in every step. When deploying lots of packages, the task sequence will be very large. There is however an alternative, using "Install software packages according to dynamic variable list". That way you can use a single step for as many packages you want. Just configure the following steps:

-Create a collection and add Collection Variables on it. Name must be APP001, APP002, APP003 (for example) and so on. Value must be the package ID value and Program installation name (which is Install in my case). Add as many packages needed.
-In the task sequence add a "Install package" step and choose for "Install software packages according to dynamic variable list": APP (for example). Mark "If installation of a software package fails, continue installing other packages in the list" when needed.
-Just make sure that on every package used, "Allow this program to be installed from the install package task without being deployed" is checked. Otherwise a 80004005 error will follow during deployment.

(instead of APP you can use any name you want, as long as numbers are used. The name used in task sequence must be same.)
 
Deploy the task sequence on the created collection. All packages will get deployed in a sequence based on the numbering of the collection variables choosed. Just another way for installing packages ;)
In my case I'm installing multiple packages in a single step. Not a problem at all, and very easy to configure.

More blogposts on this topic:
Deploy multiple applications using Dynamic Variables in a Task Sequence

8 comments:

  1. Hi Hunk,

    What will happen if i remove the APP003 application alone, so it will automatically proceed to next step APP004 (like APP01,2,4,5) or any failure will occur. Please advise me on this..

    ReplyDelete
    Replies
    1. There will be no failure. There may be a gap between packages given. No worries about that :)

      Delete
  2. For the life of me I cant figure out why this part of my task sequence keeps failing. I set variables in the unknown computer group and I ensured "Allow this program to be installed..." was checked. Everything else in the task sequence works perfect. Anything I may have possible missed?

    ReplyDelete
    Replies
    1. Just remember configuration for packages and applications are different. Maybe try using a new collection instead of using the unknown computer group. Hope it helps!

      Delete
  3. For the life of me I cant figure out why this isn't working for me... I followed all steps and tried multiple times including to ensure "Allow Program to be installed step..." All packages work fine if deployed individually. Any pointers would be greatly appreciated..

    ReplyDelete
    Replies
    1. Just remember configuration for packages and applications are different. Did you create the variables as mentioned above?

      Delete
  4. Henk,

    Posing the question anywhere I can. I have a PFE and Premier working on this. When I install applications individually with Install Application steps it works on my MDT TS for 7 and 8.1, but not 10. I get a 16389 0x8004005 error. My next thought it to check Allow this program... on those applications or try passing the whole list of default apps for the image as variable. Thoughts, comments, suggestions?

    ReplyDelete
    Replies
    1. Sometimes it helps to put the application installation step lower or higher in the task sequence, as long it's after the ConfigMgr step. It may be TS variables too? Hope it helps!

      Delete