if they have rigorous change control systems in place then those same change control systems should ensure that the consoles installed on peoples desktops match the version on the site server they are connecting to after a site upgrade has been performed,
in a lot of cases, they don't, nothing is done, and the admin continues his/her work not realizing that they are using a version that may lack features of the primary... hence the DCR, part of the reason they don't is because while the console update is indeed created by the KB, it does not automagically send it out to all desktops/whatever with the console installed, and the steps needed to get it out require some work by someone... I've seen emails on the MVP mailing list just this last week where issues seen in the field were the direct result of the configuration manager console version not matching the version on the primary, and for those reasons, I'd like to see this process made easier, much like it is for other software out there... chee3rs niall On Mon, Dec 8, 2014 at 9:29 PM, Jason Wallace <[email protected]> wrote: > Now Niall why would anyone want this? Surely people's rigorous change > control systems would prevent this from happening? > > > > On 8 Dec 2014, at 20:22, Niall Brady <[email protected]> wrote: > > wow this is now the #4 most popular request on Connect for ConfigMgr, :-) > :-) :-) > > let's get some more votes to get it even more exposure !! > > as regards the wmi issues Michael, I think they occur for other reasons > such as too many applications or windows updates in the task sequence > filling up the small amount of memory assigned to the task sequence > > there was this post about it > > > http://blogs.technet.com/b/configmgrteam/archive/2011/01/18/task-sequence-editor-too-many-steps-issue-and-solution.aspx > > but i believe r@ increased that limit to 10mb or more, can't recall the > exact figure, i haven't seen the issue much lately and it used to happen > regularly, > > however I use the console installed locally on my desktop (windows 8.1) > > On Mon, Dec 8, 2014 at 9:06 PM, Michael Mott <[email protected]> wrote: > >> I know of some folks have wmi issues on the central\primary where TS’s >> are edited. Would this actually help alleviate this issue if all consoles >> are equal perhaps? >> >> >> >> *From:* [email protected] [mailto: >> [email protected]] *On Behalf Of *Murray, Mike >> *Sent:* Monday, December 08, 2014 2:30 PM >> *To:* [email protected] >> *Subject:* RE: [mssms] pls vote it up - Console should show newer >> version available and allow upgrade >> >> >> >> Done, great idea. :) >> >> >> >> *From:* [email protected] [ >> mailto:[email protected] <[email protected]>] *On >> Behalf Of *Niall Brady >> *Sent:* Monday, December 8, 2014 5:53 AM >> *To:* [email protected] >> *Subject:* [mssms] pls vote it up - Console should show newer version >> available and allow upgrade >> >> >> >> please vote it up ! (see the title bar in the attached screenshot for >> the concept....) >> >> "Today, you can be running a console with one version, that is not in >> sync 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,." >> >> >> public link >> >> >> https://connect.microsoft.com/ConfigurationManagervnext/feedback/details/1049659/dcr-show-version-incompatability-and-allow-ability-to-upgrade-console-to-match-the-primary-site-version-of-configuration-manager >> >> mvp link >> >> >> https://connect.microsoft.com/ConfigurationManagervnext/feedback/details/1049655/mvp-dcr-configuration-manager-console-should-alert-you-to-newer-version-availability >> >> cheers >> niall. >> >> >> >> >> >> ------------------------------ >> >> >> Legal Notice: This email is intended only for the person(s) to whom it is >> addressed. If you are not an intended recipient and have received this >> message in error, please notify the sender immediately by replying to this >> email or calling +44(0) 2083269015 (UK) or +1 866 592 4214 (USA). This >> email and any attachments may be privileged and/or confidential. The >> unauthorized use, disclosure, copying or printing of any information it >> contains is strictly prohibited. The opinions expressed in this email are >> those of the author and do not necessarily represent the views of 1E Ltd. >> Nothing in this email will operate to bind 1E to any order or other >> contract. >> >> > > >
