|
exchange
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Fallout Post-Installation Latest Highly Critical Security UpdateInstalled the latest, super critical MS security update for Exchange-03 SP2.
As usual I installed late in the day but not technically after hours. This is typically not service affecting. Then I schedule a reboot late at night. However, this latest update was service-affecting--users could not open Outlook online. What's up with that? Is there any way to tell in advance if any particular update will cause such behavior before a reboot can be performed? On Thu, 12 Feb 2009 14:18:04 -0800, Scott
<Sc***@discussions.microsoft.com> wrote: >Installed the latest, super critical MS security update for Exchange-03 SP2. Exchange updates typicallly stop the Info store service.>As usual I installed late in the day but not technically after hours. This is >typically not service affecting. Then I schedule a reboot late at night. >However, this latest update was service-affecting--users could not open >Outlook online. What's up with that? Is there any way to tell in advance if >any particular update will cause such behavior before a reboot can be >performed?
Show quote
Hide quote
"Andy David {MVP}" <ada***@pleasekeepinngcheesebucket.com> wrote in message Especially when they replace the store.exe!news:bjg9p49ehdd7amspko6od83l35ovch272a@4ax.com... > On Thu, 12 Feb 2009 14:18:04 -0800, Scott > <Sc***@discussions.microsoft.com> wrote: > >>Installed the latest, super critical MS security update for Exchange-03 >>SP2. >>As usual I installed late in the day but not technically after hours. This >>is >>typically not service affecting. Then I schedule a reboot late at night. >>However, this latest update was service-affecting--users could not open >>Outlook online. What's up with that? Is there any way to tell in advance >>if >>any particular update will cause such behavior before a reboot can be >>performed? > > Exchange updates typicallly stop the Info store service. > The update has a new version of store.exe in it. Thus the need to stop the
store to replace it. Show quoteHide quote "Scott" <Sc***@discussions.microsoft.com> wrote in message news:4F5DF34D-A5C0-4B60-A54E-27CDC792C91C@microsoft.com... > Installed the latest, super critical MS security update for Exchange-03 > SP2. > As usual I installed late in the day but not technically after hours. This > is > typically not service affecting. Then I schedule a reboot late at night. > However, this latest update was service-affecting--users could not open > Outlook online. What's up with that? Is there any way to tell in advance > if > any particular update will cause such behavior before a reboot can be > performed? Martin Blackstone [MVP] <mart***@myrealbox.com> wrote:
> The update has a new version of store.exe in it. Thus the need to Yep. Don't install updates during business hours.> stop the store to replace it. Show quoteHide quote > > > "Scott" <Sc***@discussions.microsoft.com> wrote in message > news:4F5DF34D-A5C0-4B60-A54E-27CDC792C91C@microsoft.com... >> Installed the latest, super critical MS security update for >> Exchange-03 SP2. >> As usual I installed late in the day but not technically after >> hours. This is >> typically not service affecting. Then I schedule a reboot late at >> night. However, this latest update was service-affecting--users >> could not open Outlook online. What's up with that? Is there any way >> to tell in advance if >> any particular update will cause such behavior before a reboot can be >> performed? On Fri, 13 Feb 2009 09:12:32 -0500, "Lanwench [MVP - Exchange]"
<lanwe***@heybuddy.donotsendme.unsolicitedmailatyahoo.com> wrote: >Martin Blackstone [MVP] <mart***@myrealbox.com> wrote: or when the moon is full.>> The update has a new version of store.exe in it. Thus the need to >> stop the store to replace it. > >Yep. Don't install updates during business hours. Show quoteHide quote >> >> >> "Scott" <Sc***@discussions.microsoft.com> wrote in message >> news:4F5DF34D-A5C0-4B60-A54E-27CDC792C91C@microsoft.com... >>> Installed the latest, super critical MS security update for >>> Exchange-03 SP2. >>> As usual I installed late in the day but not technically after >>> hours. This is >>> typically not service affecting. Then I schedule a reboot late at >>> night. However, this latest update was service-affecting--users >>> could not open Outlook online. What's up with that? Is there any way >>> to tell in advance if >>> any particular update will cause such behavior before a reboot can be >>> performed? > > Andy David {MVP} <ada***@pleasekeepinngcheesebucket.com> wrote:
> On Fri, 13 Feb 2009 09:12:32 -0500, "Lanwench [MVP - Exchange]" Unless you first make the sign of the evil eye.> <lanwe***@heybuddy.donotsendme.unsolicitedmailatyahoo.com> wrote: > >> Martin Blackstone [MVP] <mart***@myrealbox.com> wrote: >>> The update has a new version of store.exe in it. Thus the need to >>> stop the store to replace it. >> >> Yep. Don't install updates during business hours. > > or when the moon is full. Show quoteHide quote > > >>> >>> >>> "Scott" <Sc***@discussions.microsoft.com> wrote in message >>> news:4F5DF34D-A5C0-4B60-A54E-27CDC792C91C@microsoft.com... >>>> Installed the latest, super critical MS security update for >>>> Exchange-03 SP2. >>>> As usual I installed late in the day but not technically after >>>> hours. This is >>>> typically not service affecting. Then I schedule a reboot late at >>>> night. However, this latest update was service-affecting--users >>>> could not open Outlook online. What's up with that? Is there any >>>> way to tell in advance if >>>> any particular update will cause such behavior before a reboot can >>>> be performed?  
Thread options
Other interesting topics
exchange redirect - how secure?
Need help with QUEUE question Filtering Junk Mail from your own domain Sender Photos in email.. Store.exe Eating up Memory Random Added contact to email Alerts for "MSExchangeSA service is Stopped" HTTP status code: [501] Urgent help required Upgrading to a 2008 domain Out of Office cannot work |
|||||||||||||||||||||||
