 |
 |
Jon Galbreath wrote: >The certificate change had been posted for weeks. Once again, shades of the opening chapter of "Hitchhikers Guide to the Universe". -- dkm >Â The issue with the load balancer or whatever it was this morning, was not. > >Jon Galbreath >MCSE/Security+ >Systems Administrator >International Studies and Programs >Ph: 517-884-2144 ><mailto:[log in to unmask]>[log in to unmask] > >From: Troy Murray [mailto:[log in to unmask]] >Sent: Tuesday, September 14, 2010 10:53 AM >To: [log in to unmask] >Subject: Re: [MSUNAG] mail.msu.edu certificate > >Is there a single source for these type of >announcements of changes to the network that I >can subscribe to? Having to subscribe to >multiple lists just for announcements seems more >complicated then it needs to be. > >I see MSU Service Status has an area for >scheduled maintenance, was this issue posted at that location does anyone know? > > >On Tue, Sep 14, 2010 at 8:35 AM, Gary Schrock ><<mailto:[log in to unmask]>[log in to unmask]> wrote: >On 9/14/2010 9:31 AM, Fishbeck, John wrote: >In ATS' defense, they announced that this was >going to happen several times over the past >month via the ><mailto:[log in to unmask]>[log in to unmask] listserv. > > > >Ah, apparently I overlooked that email >list. Thanks, I'll make sure I subscribe to that. > >Gary >Regards, > >John Fishbeck >Physical Plant Computer Systems& Networking Group > > > >-----Original Message----- >From: Gary Schrock [mailto:[log in to unmask]] >Sent: Tuesday, September 14, 2010 9:26 AM >To: <mailto:[log in to unmask]>[log in to unmask] >Subject: [MSUNAG] <http://mail.msu.edu>mail.msu.edu certificate > >I'm sure people have already started to run into this today, but just to >warn you, your users might be asking about this. Apparently they >updated the <http://mail.msu.edu>mail.msu.edu >ssl certificate this morning. The Service >Status history suggests that "Many clients will not be affected", but so >far that's not my experience. Outlook users doing sends here are >getting prompted to accept a certificate that can't be verified. >(Checking mail doesn't seem to prompt this, but sending mail definitely >does seem to be.) > >(Personally, I'm seeing this on a Windows 7 machine running Office 2007, >all updates installed, and so far everyone that I know using outlook >that I've asked has seen it. So I'd have to wonder about the "Many >clients will not be affected."). > >One other note, I honestly don't remember seeing any sort of >communication that this was happening, did I miss it? > >Gary > > > > > > >-- >Troy Murray