Show version incompatability and allow ability to upgrade console to match the Primary site version of Configuration Manager
Today, you can be running a console with one version, that is not in synch with what is running on the primary. The only way you'll know is if you are missing features added to a newer release or if troubleshooting leads you down that route. You have to check the about page in the console to verify version number and compare that against what is installed on the Primary site server to see if they match, what I'm proposing is an easy visual way in the console to inform you when your versions don't match, and to offer the ability to upgrade via a simple click,.
to repro:
Install Configuration Manager 2012 R2 CU3 on the primary, and on a computer that has the Configuration Manager 2012 R2 console installed, connect, you will not be informed of the version difference and will never know it was different unless you went and actively looked for the difference.
Niall C. Brady
shared this idea
AdminMark Silvey - ConfigMgr Product Team
(Engineering Manager, ConfigMgr, Microsoft Endpoint Configuration Manager)
responded
This work item is now complete and available in our 1511 release! Thanks for the feedback!
2 comments
-
Niall C. Brady
commented
to Mark and team, well done, you guys are awesome !
-
Niall C. Brady
commented
hi Mark, there are lots of reasons, if you are using a different version you may not be seeing all the features available to the product (for example fixed powershell cmdlets was a valid reason), or features that have been added/resolved/fixed via an update. Or simply an inability to do things due to the wrong version of the console being installed not matching what's on the primary. My attached pic should give an indication (visible) to the end-user that an update is available, and i think that is key also. (to be informed !), today, you'd have to go hunting to find out,....