Ya, not a great idea on the client updates being automatic.  We had an issue a 
bit ago where an update to the SCEP client fubared the encryption software on 
our laptops.  Not a great situation.

> -----Original Message-----
> From: [email protected]
> [mailto:[email protected]] On Behalf Of Marcum, John
> Sent: Tuesday, June 10, 2014 12:00 PM
> To: [email protected]
> Subject: RE: [mssms] Client Version 5.00.7958.1104 (R2 CU1)
> 
> IMO.... Using more unique names for updates would help. I see CU1 for R2
> and CU1 for SP1 then I have to think "what came first SP1 or R2"? and so
> forth. Next make all client updates use the automatic updates feature rather
> than just some of them.
> 
> 
> 
> 
> -----Original Message-----
> From: [email protected]
> [mailto:[email protected]] On Behalf Of Brian Huneycutt
> Sent: Tuesday, June 10, 2014 1:01 PM
> To: [email protected]
> Subject: RE: [mssms] Client Version 5.00.7958.1104 (R2 CU1)
> 
> Having multiple product versions in market at once can definitely make things
> confusing :)
> 5.00.7958.1104 is an R2 hotfix (pre-CU1)
> http://support.microsoft.com/kb/2910552
> 
> John in your list below you have these (I've sorted earliest to latest)
> 5.00.7711.0000 - 2012 RTM
> 5.00.7804.1000 - 2012 SP1
> 5.00.7958.1000 - 2012 R2
> 5.00.7958.1101 - R2 hotfix 2905002 (superseded by 2910552. Both articles are
> cross-referenced, and both in R2 CU1)
> 5.00.7958.1203 - R2 CU1
> 
> Our KB articles for Cumulative Updates now contain all the version specific
> details you should need to make identification easier, though we have not
> retroactively added that info to older articles.
> It looks like some of our individual hotfix KB articles don't explicitly call 
> out
> the client version when it changes; we can work on correcting those.
> What else should we consider to ease the confusion?
> Thanks,
> Brian Huneycutt
> 
> -----Original Message-----
> From: [email protected]
> [mailto:[email protected]] On Behalf Of Marcum, John
> Sent: Tuesday, June 10, 2014 1:30 PM
> To: [email protected]
> Subject: RE: [mssms] Client Version 5.00.7958.1104 (R2 CU1)
> 
> Here's what I have. I think the way they are doing updates is a confusing
> mess.
> 
> 5.00.7958.1000
> 5.00.7958.1203
> 5.00.7711.0000
> 5.00.7804.1000
> 5.00.7958.1101
> 
> 
> 
> 
> 
> 
> -----Original Message-----
> From: [email protected]
> [mailto:[email protected]] On Behalf Of Todd Hemsell
> Sent: Tuesday, June 10, 2014 12:22 PM
> To: [email protected]
> Subject: Re: [mssms] Client Version 5.00.7958.1104 (R2 CU1)
> 
> yes, and somehow I am at an impossible version number.
> 
> Thanks
> 
> On Tue, Jun 10, 2014 at 12:17 PM, Heaton, Joseph@Wildlife
> <[email protected]> wrote:
> >
> http://blogs.technet.com/b/configmgrdogs/archive/2014/04/11/configmgr-
> > 2012-version-numbers.aspx
> >
> > http://en.wikipedia.org/wiki/System_Center_Configuration_Manager
> >
> >
> > Not from Microsoft direct, but these show the version numbers.
> >
> >
> >
> >> -----Original Message-----
> >> From: [email protected]
> >> [mailto:[email protected]] On Behalf Of Todd Hemsell
> >> Sent: Tuesday, June 10, 2014 10:12 AM
> >> To: [email protected]
> >> Subject: Re: [mssms] Client Version 5.00.7958.1104 (R2 CU1)
> >>
> >> you happen to have a link to the update you installed? I am doing
> >> something wrong over here.
> >>
> >> On Tue, Jun 10, 2014 at 12:05 PM, Kent, Mark
> >> <[email protected]>
> >> wrote:
> >> > I have 5.00.7958.1203, from one post R2 CU1 update.
> >> >
> >> > Mark Kent (MCP)
> >> > Sr. Desktop Systems Engineer
> >> > Computing & Technology Services - SUNY Buffalo State
> >> >
> >> > -----Original Message-----
> >> > From: [email protected]
> >> > [mailto:[email protected]] On Behalf Of Todd Hemsell
> >> > Sent: Tuesday, June 10, 2014 1:03 PM
> >> > To: [email protected]
> >> > Subject: [mssms] Client Version 5.00.7958.1104 (R2 CU1)
> >> >
> >> >  What is the most recent client version? I have 5.00.7958.1104
> >> >
> >> > I get ZERO hits when googling that version.
> >> >
> >> > /Todd
> >> >
> >> >
> >> >
> >> >
> >>
> >>
> >
> >
> 
> 
> 
> 
> 
> ________________________________
> 
> Confidentiality Notice: This e-mail is from a law firm and may be protected by
> the attorney-client or work product privileges. If you have received this
> message in error, please notify the sender by replying to this e-mail and then
> delete it from your computer.
> 
> ________________________________
> 
> Confidentiality Notice: This e-mail is from a law firm and may be protected by
> the attorney-client or work product privileges. If you have received this
> message in error, please notify the sender by replying to this e-mail and then
> delete it from your computer.
> 
> 
> 
> ________________________________
> 
> Confidentiality Notice: This e-mail is from a law firm and may be protected by
> the attorney-client or work product privileges. If you have received this
> message in error, please notify the sender by replying to this e-mail and then
> delete it from your computer.
> 
> ________________________________
> 
> Confidentiality Notice: This e-mail is from a law firm and may be protected by
> the attorney-client or work product privileges. If you have received this
> message in error, please notify the sender by replying to this e-mail and then
> delete it from your computer.


Reply via email to