This is in 1806 TPDuncan Galbreath supported this idea ·Duncan Galbreath commented
This is especially painful for hierarchies with several remote secondary sites. A lot of manual maintenance that must be done to avoid major issues.
12 votesDuncan Galbreath commented
More information: Each week I have to create about 5 new Applications in SCCM. Currently I have a script that will create the application, populate the information for display in Software Center, create the deployment type, add the installation and uninstallation command lines, and add the detection method.
Our application packages contain a custom exit code that needs to be recognized as a successful deployment. This exit code denotes a certain upgrade scenario that must be differentiated from a standard installation, hence the custom code. Once the script creates the applications, I must manually go into the properties of each Application, edit the deployment type, and manually add the exit code and associated information.
I would like the ability to add that return code information via PowerShell so the process could be fully automated.Duncan Galbreath shared this idea ·