@Lior_Bela
Thank you for being open to our feedback on orchestrating and sequencing application installations.
We've identified key reasons why this capability is crucial:
- Dependency Management: Some applications must be installed in a specific order due to dependencies, such as add-ons requiring a primary application first. Without sequencing, we face potential operational failures. We use dependencies of Win32 apps now.
- Stability Concerns: Certain applications, like third-party security agents, can disrupt subsequent installations by blocking critical processes, such as PowerShell scripts. Installing these last would prevent interference and ensure smoother deployments. Or, it's very common that some app will strart updating itself in the background, using Windows Installer and blocking other Win32 apps install, so they fail. Moving those to the tail end helps as well. Currently, we use dependencies for this as well.
Implementing sequencing would significantly improve our deployment strategies and reduce setup disruptions, benefiting both our customers and the broader user community.
I have another question about the "Device Preparation Policy": Does this policy allow for the addition of applications (I suppose so), and if so, are these applications only executed during the initial provisioning process? Specifically, will these apps NOT run again for each new user who signs in and has this policy assigned to them?
Thank you.
Microsoft