Install MECM Support Center alongside client by default
I have no metrics to back this up, yet I feel Support Center is under utilized as it has to be installed separately and manually from the MECM client.
Could you give us one or more of the following options?
1) Add an checkbox in the client install settings area to have Support Center install after the MECM client is installed.
2) Have Support Center install by default like the MECM client
3) Make installing Support Center an option in the Add dropdown under a Tools folder, in the TS editor.
We don’t package Support Center with the client at this time because it would add 15MB or so to the MSI package, and we’re trying to avoid bloating it as much as possible.
That being said, there’s certainly no reason we can’t have other solutions in place to make it easier to get Support Center onto client machines or to otherwise opt-in to having it distribute with clients.
We will look into ways to improve this in the future.
I might be stepping on some security toes here, but why would you want it installed on the clients?
I have it on my own computer and connect to clients remotely.
William AE Bluhm commented
Absolutely, a default/optional, auto-generated app/package, would be ideal!
AdminAdam Meltzer (ConfigMgr Product Team) (Software Engineer, Microsoft Endpoint Configuration Manager) commented
So make it like a built-in package? We can definitely look into this.
In any event, there's lots of great ideas here for things we can look into adding in the future. Thank you again for your feedback.
William Bluhm commented
Thank you for the quick response Adam.
My first suggestion from above wasn't worded very coherently so I'll try to expand on it. My thought was that when you install/update MECM, the client package gets updated to the latest version and gets distro'd to DPs. Why not have a similar application or package for Support Center? This could be done via opt-in or by default if the community feels it is advantageous.