Ideas
What features would you like to see?
All of the feedback that you share in these forums will be monitored and reviewed by the Microsoft engineering teams responsible for building Microsoft Endpoint Configuration Manager, though we can’t promise to reply to all posts.
If you require assisted support, please see https://aka.ms/cmcbsupport for more details.
-
it would really help if symbolic links were supported in sccm apps or packages. that will cut the size of big bundles.
Recently I have been working with Microsoft engineer to help us packaging big application bundles and turned out that SCCM does not support symbolic link. when we package apps with symbolic links all is good until we deploy it and check client cache on the client machine where the symbolic link does not show up / disappears. we use symbolic link to minimize package size specially for Autodesk suits where multiple apps packaged together each requiring same library files and tools.
1 vote -
Have the client wait for Windows Installer to finish if another installation is in progress. To avoid the 1618 error.
When the deployment type is of type Windows Installer, the client should check if Windows Installer is free and not running another installation.
Just to avoid error 1618.1 vote -
Application Deployment with option free disk space
SCCM 1906: application deployment with global option disk space
i added a requirement of free disk space of 47GB for a deployment type and i wonder why its not working this way: show application in software center even with less than 47Gb but mention that its not installable because of too less free space...
Now i dont see it in software center at all if less than 47GB free space and even if its already installed i cant uninstall it if less than 47GB are free after installation because i cant see it.
Wouldnt make it much more sense if…
3 votes -
Application quantity property
It would be helpful to have the ability to assign a QTY to an Application property and to be able to report against it. Purchased vs deployed=Availability. I have been posting the purchase info in the admin comments for myself but management can't report from it.
1 vote -
Application deployment and "Maintenance Windows" setting kills the application when downloading
-Problem overview
If you deploy the application under the following conditions, the running application will be killed immediately after the download phase.
The customer has set "Maintenance Windows", and the problem is that the application is killed at a timing outside the "Maintenance Windows" range.This behavior is reproducible. (Confirmed with MECM 2002)
I want to confirm whether this behavior is a by design or a known issue.-Repro step
1. Set "Maintenance Windows" to the device collection. The next step is to set the installation deadline before entering "Maintenance Windows".In the application's Deployment Type properties, on the Install…
3 votes -
Intranet client with domain user will not be able to get the user based application through the CMG
Currently, when client machine connect to VPN which is in the intranet, only when the user is a cloud user, it will use cmuserservice endpoint. If the logged in account is on-premise domain account, it will access cmuserservice_winauth all the time then the software center cannot see user-based applications.
Please add this feature to allow domain account to get user-based application through CMG when connect VPN as this is quite useful scenario.
3 votes -
Prioritize application deployments
This an idea to add a functionality so we can set a priority from 1-10000 for multiple software deployments.
Currently if one of the packages require a reboot and they get installed ahead of the others that will hold up the deployments until the machine is rebooted.
21 votes -
Add Delivery Optimization to Cloud Management Gateways
Egress costs from a CMG can mount very quickly, but if you had Delivery Optimization, this would make CMG a very lucrative solution. At the moment, egress costs are too high.
1 vote -
Edge Deployment: Add Execution Policy Bypass by default
When creating an Edge deployment via the integrated Edge Management the parameter "-ExcecutionPolicy Bypass" has to be added manually to the installation command if the client's execution policy does not allow the PowerShell script to be run by default.
The bypass parameter should be added to the command line by default.
2 votes -
Phased Deployments
We need more phases in Phased Deployments I would think a max of 6 should suffice for most.
3 votes -
Allow Device and Collection Variables to be Queries via Global Conditions/Requirements
If we allowed device variables and collection variables to be evaluated at the time of app install, it would greatly reduce the effort in Application Packaging when determining exception processes and/or complicated scenarios around Applications that need specific versions of dependent applications.
3 votes -
Add a check box to not install required deployments after a deadline if offline
In a situation in which laptops have already cached an application, but login offline after a required deployment has been canceled for business reasons, they will still install the application which is not ideal. If it is possible to add a check box to the deployment to force the clients to only install the application once they are online or receive policy after a deployment deadline has been reached, that would be great.
1 vote -
Copy Administrative Categories from one application to another
Would love to be able to copy Administrative Categories from one application to another. My org uses these A LOT and it is cumbersome to go through a long list of checkboxes to apply them all to a new application. A way to copy them would save quite a bit of time and would reduce errors.
The list can be copied from the General Information tab, could that be field changed to an input field for copy/paste? Maybe a button for "Copy From Another Application" could be there that would let you choose a source application?
3 votes -
Application Name in Status of App Group Install
When deploying an Application group, it would be nice in Software Center if the name of the individual app that was installing would show in the status.
4 votes -
Application Group reboot behaviour
Given a scenario of an application group which contains more than one application: if any application in that group requires a reboot the whole application group is terminated with an error (AppGroupHandler - InternalProcessAppRules failed with error 0x87d0032e) even though the application which demanded the reboot was installed correctly.
The expected behaviour is to perform the reboot and then continue with the next application in line in the application group after the reboot.
It would be beneficial if any reboot request in the application group process were internally remembered and only one reboot request would be sent to the user…
37 votes -
Install Behavior not met not shown as Error in Monitoring
The ability to use Install Behavior for Applications that an Executable must be closed is great.
But in Monitoring the Application Deployment shows as an Error if the Executable was running when the Application tried to install itself. In the Error Description it states “One or more processes are running and prevent enforcement action”
Why can’t it be shown under Requirements Not Met or a new Category but not as an Error? I don’t see it as an error and so a lot of Deployments show tons of Errors, that are not Errors, only because the Application is waiting for…1 vote -
1 vote
-
Install Behavior prompt not showing in front of Software Center
When using the "Install Behavior" options on a deployment type for an application, the prompt to close the applications does not come to the front of the software center and to the center of the end users attention, please can you fix this?
3 votes -
Orchestration groups - extend with more deployment types
Right now the OG feature only supports software Update deployments.
Extend this feature to include application deployments, TS deployments and application group deployments.
This will increase the value of OG.13 votes -
Available Applications that a user initiates in Software Center should ignore maintenance window for all dependencies and superseded apps
When a user clicks on an application in Software Center while it is available (or pre-deadline) then all dependent and superseded applications should ignore the user's maintenance window. The current behavior is that if a reboot is needed in the chain then the user has to click install again in Software Center. This could be handled by a deployment option so that the current default behavior isn't impacted.
Example:
User Clicks on App1
App1 has a dependency on App2
App2 requires reboot
When user clicks App1, App2 should install, then reboot, then App1 should complete installation and reboot if needed…38 votes
- Don't see your idea?