Automation

I want to create a single deployment set for computers, where only the software that the user has permission to install is deployed. For example, when a device is set up for a user named Pieter, who has the 'Sales' role, only the sales-related app...

The ability to use a custom install script for advanced installs such as detecting OS type and adjusting install location based on Server OS or Workstation

Application is added to application manager that has the ability to have a "complete or full" install for some administrators, so they get all the functionality and menus (there could even be a licence associated to use the full features). Then th...

The Deployment under automation is always deploying the production version but i want to be able to choose a different fase like development or test. Sometimes we want to test an entire deployment with new version before changing the packages to p...

As a system administrator, I want to be able to limit the systems on which to deploy applications, such as 32-bit or 64-bit systems, or different operating systems, such as Windows 10, 11, servers, or workstations. Also ability to require older ve...

As a sys admin, I want to run my deployment process using schedule (not when the new version is released)

I would like to define how many previous application version I want to keep as retired before removing the application/installation media from ConfigMgr.

For every deployment I prefer to save logging in the C:\Windows\Temp directory. We should be able to call variables so that the log file naming is dynamic such as adding the install string /l*v C:\Windows\Temp\%APPNAME%-%VERSION%.log and having th...

Application manager: Pre and post scripts running should be supported

Each deployment process should have its own individual deployment type