We use a lot of contractor resources as surge resources for application packaging. Could you implement an approval process (similar to that of Run Scripts) that would require approval before someone could Deploy a newly created Application? This would greatly improve quality and ensure all new Applications have been reviewed to reduce the risk of an ooops.0 votes
Make it easier to troubleshoot application deployment with:
- Consolidated log file
- Make logging easier to understand and find the reason for failures.
For a new SCCM Admin/Tech troubleshooting appdeployment is hard, have to understand the different log files and know which one to read.0 votes
Add a right click option to see what task sequences an Application is associated to.
This make 'supersede' application easier to identify.0 votes
Provide a task sequence step to install all targeted applications, programs and software updates.
Where imaging a PC is done on a limited time it would be beneficial to install all applications.
Similar to this.
"Install Software on next reboot" switch for required Deployments
We have machines in production which are always online and only the Users can initiate a reboot or an Software Installation. It would be cool to have an option to install all required Deployments if the Users initiate a reboot. This would raise the SW-Compliance extemely, because the Users often do not take a look in the SW-Center an click on install.0 votes
Please add the Comment field to the Package Properties pane.
Added graphics for clarification.0 votes
Bug I think: I deployed the uninstall action for an App-V 4.6 application through SCCM, with a deadline in the year 2099 (to allow leeway for monitoring before and after in my testing), but it ran as soon as it hit.
Deployed to user, install outside maintenance windows (so I would see it in Software Center without having to wait till after work).
Inconvenient, not a show-stopper.0 votes
Office Customization Tool should organize settings into subcategories and needs to update Office 2016 language.
Office Customization Tool should reference subcategories and needs to be updated from Office 2016 language. The same settings that existed in the Office 2016 Customization Tool still exist in the new tool but they are all lumped together in the root categories. Some of the settings names are vague and only make sense once you figure out what subcategory they were formerly associated with. For example, the settings for auto-correct are lumped together with security and encryption settings. Like the Office "Arabic modes" setting. I had to open up the description before it was clear this was a spell check setting and not a UI setting or character-set option. This wouldn't be confusing if it was listed under "Spell-check" or "Autocorrect."
Many of the setting descriptions still refer back to Office 2016. This seams to indicate that the settings were just carbon-copied from the old 2016 OCT. Unfortunely, they are not presented with the same context as originally intended so they make less sense. It shouldn't be difficult to just put the same categories into the new tool.
The new tool has room for improvement.
Office Customization Tool should reference subcategories and needs to be updated from Office 2016 language. The same settings that existed in the Office 2016 Customization Tool still exist in the new tool but they are all lumped together in the root categories. Some of the settings names are vague and only make sense once you figure out what subcategory they were formerly associated with. For example, the settings for auto-correct are lumped together with security and encryption settings. Like the Office "Arabic modes" setting. I had to open up the description before it was clear this was a spell check…0 votes
Similar to how you integrated Edge deployment and maintenance into CM, could you do the same for VSCode?
Pretty much the same as this, but for vscode
Application dependency is causing issues in the following scenario.
"MainApp Addon 1.0" has a dependency on either "MainApp 1.0" or "MainApp 1.1".
MainApp 1.1 superseeds MainApp 1.0 with uninstall checkbox.
Both "MainApp 1.0" and "MainApp Addon 1.0" is installed on computer.
When trying to update "MainApp 1.0" to "MainApp 1.1" the log "AppIntentEval.log" will spit out errors and app upgrade will not occur.
Also new computers will have issues trying to install "MainApp 1.0" and "MainApp Addon 1.0".
This can cause issues in upgrade scenarios of application and workarounds that needs to be created.0 votes
There should be possible to have Uninstall behaviour on applications the same way there is Install behaviour.
Installing Zoom and Zoom outlook plugin via task sequence app model, I put Outlook.exe into the Install behaviour and it tells me to close Outlook before installing. When I try to run uninstall it does not tell the user to close Outlook.
There is a lot of times, it would be very helpful to close an application before uninstall.0 votes
It would be useful to us for an option, similar to allowing application to run via task sequence, that would let us select which applications we would want users to see/install via the CMG. Currently most apps we use are deployed as available to all users but only a select few have the content distributed to our CMG and so causes problems when users try to install and ConfigMgr waits to download content.0 votes
Allow multiple "Product Code" separated by a comma, in the "Windows Source management" under Deployment Type - Program tab.
This would be helpful for such MSI with sub storage streamed in. Those MSI change their Product Code on the fly during installation depending on language detected.0 votes
At the moment application supersedence is only working with machine deployments. Please make this work for user deployments.0 votes
- Don't see your idea?