Manage Deployment of Console Updates
I would be good if applying an update to Configuration Manager also either:
- initiated the creation of an application/collection/deployment to upgrade administrator consoles, or
- provided the ability for the console to update itself by kicking off a background service to install the update for non-administrator users.
It's great that the console now notifies the user when it's out of date, but the process of applying these updates really needs to be streamlined. Something similar to automatic client upgrade would be amazing.
Scott – How would you like it streamlined? What would you do if you could have anything?
Cherif BENAMMAR commented
I suggest to create an update/package/app to be downloaded to the client via DP and not via UNC like is the case now, Or even, the local SCCM client will detect the existence of the console and checks every 24H if there is any update then download it to the software center and asks user to install it from the console.
Cherif BENAMMAR commented
I suggest to create an update/package/app to be downloaded to the client via DP and not via UNC like is the case now,
Who logs on their PC as a local admin since XP? What good is it to prompt to upgrade if no one can actually perform the upgrade. This is just a nuisance message and without an immediate deployment of the console it often leaves SCCM admins helpless.
User chooses no instead of yes on the console upgrade, then cannot connect to server. Reinstalling the Admin console does not help. Solution, remove the admin gui section in HKCU for that user. Run console, enter server name, Connection works. Just a tip
We solved our problem . We did not install the console in Default Installation path "C:\Program Files (x86)\Microsoft Configuration Manager". After reinstalling the console in Default path updating is working. Seems the updatet can not handle other install paths then the Default one.
yes, the console now prompts to be updated when necessary but it does not work in our environment when a user is not an admin user.
Even for admins it often does not work to update the console.
The automatic creation of an Application would be nice. We use the app model to deploy/upgrade the Admin Console after upgrades. However something similar to the automatic client upgrade would be extremely helpful too. We frequently string the Admin Console application together with a package for a hotfix inside a task sequence because the hotfix packages are auto-generated when the KB is installed on the site server.
Scott Breen commented
For computers that have the Configuration Manager client for that hierarchy installed:
Option 1 - Similar to Automatic client upgrade
Perform the same way an automatic client upgrade is done - using a scheduled task / site settings to control the upgrade over a few days / test collection.
Option 2 - Auto create Application (my preference)
Automatically create a collection / application / optional deployment, then supersede this application each time a new version is installed. Also give the option to automatically upgrade. The configuration of this Application would remain locked (similar to the client package), but it would allow the configuration of deployments.
For computers that don't have a Configuration Manager client for the hierarchy installed, the current solution of notifying them would have to suffice.
This is only what I can think of off the top of my head. Happy to discuss futher.
Scott, in the Current Branch builds of ConfigMgr, the console now prompts to be updated when necessary.