SOLVED

Controlling Software Installation Order

Iron Contributor

We have several pieces of software that we need to target to over 1000 Windows 10 machines. 2 pieces of software require reboots so we wish these to be installed after the other 3 (that don't require reboots). How can this be achived in MECM? I see we have application groups but these seem pretty limited and also show up as  single item in Software Centre which we don't like. What are our options?

PS: using MECM 2207

1 Reply
best response confirmed by shocko (Iron Contributor)
Solution

@shocko 

 

To address your scenario in Microsoft Endpoint Configuration Manager (MECM), where you have multiple pieces of software to deploy to over 1000 Windows 10 machines, with a specific installation order and reboot requirements, here's a recommended approach:

 

Create Application Packages: First, create individual application packages for each of the software items you need to deploy. This will give you the flexibility to manage each software's deployment settings independently.

 

Non-OS Deployment Task Sequence: Since you have specific installation order requirements and the need for reboots, consider using a non-OS deployment task sequence. This is a versatile tool in MECM that allows for complex deployment scenarios. You can sequence the installation of the applications in the desired order and specify reboots where necessary. This approach provides greater control over the installation process compared to Application Groups.

 

You can find more information about Non-OS Deployment Task Sequences here: https://learn.microsoft.com/en-us/mem/configmgr/osd/deploy-use/create-a-task-sequence-for-non-operat...

1 best response

Accepted Solutions
best response confirmed by shocko (Iron Contributor)
Solution

@shocko 

 

To address your scenario in Microsoft Endpoint Configuration Manager (MECM), where you have multiple pieces of software to deploy to over 1000 Windows 10 machines, with a specific installation order and reboot requirements, here's a recommended approach:

 

Create Application Packages: First, create individual application packages for each of the software items you need to deploy. This will give you the flexibility to manage each software's deployment settings independently.

 

Non-OS Deployment Task Sequence: Since you have specific installation order requirements and the need for reboots, consider using a non-OS deployment task sequence. This is a versatile tool in MECM that allows for complex deployment scenarios. You can sequence the installation of the applications in the desired order and specify reboots where necessary. This approach provides greater control over the installation process compared to Application Groups.

 

You can find more information about Non-OS Deployment Task Sequences here: https://learn.microsoft.com/en-us/mem/configmgr/osd/deploy-use/create-a-task-sequence-for-non-operat...

View solution in original post