Deployments - Add a separate package as a step

[dtigani]

Not sure if this has been ever asked for before, but sometimes there are packages we want to push out which have several elements. It would be very handy to be able to call different packages as steps within a single package.

This would help when we're pushing out a new application which has some elements requiring Admin access, whilst other parts need to run as the logged in user. Also, we could build out our packages for individual applications, then have a single package which sequentially runs the list of packages required.

Hope this makes sense.

[Esben_D]

I've added your request to our list of deployment module improvements. Both the grouping of multiple packages into one and using different run modes within one package have been added to the list.

[pryan67]

Esben.D wrote:
I've added your request to our list of deployment module improvements. Both the grouping of multiple packages into one and using different run modes within one package have been added to the list.

Is there an update to this? It's been almost two years. We're working currently on upgrading all workstations to Windows 10 and Office 2019, and it would be nice to be able to do them both in one package

[CyberCitizen]

pryan67 wrote:
Is there an update to this? It's been almost two years. We're working currently on upgrading all workstations to Windows 10 and Office 2019, and it would be nice to be able to do them both in one package

Could you not package the Windows 10 upgrade with your Office 2019 in your WDS or are you using the Windows 10 update setup.exe?

The way we did it was with scheduled deployments.

Create a group or report based on the machines to be upgraded.

Have two scheduled deployments for the group / report. One that does the Windows 10 upgrade and one for the Office upgrade. With the Office upgrade you just need to put a check in first to confirm its been upgraded first etc.