The latest Exchange patch does need a reboot…

Dear Exchange team:

In your KB http://support.microsoft.com/default.aspx?scid=kb;en-us;924334 you state the following:

Restart requirement

loadTOCNode(3, ‘resolution’);You do not have to restart the computer after you apply this hotfix.

Uhhh…..wanna make a bet?

3: Source:E:\Exchange\bin\SET174.tmp (6.5.7651.43)
110.953: Destination:E:\Exchange\bin\davex.dll (6.5.7638.1)
116.078: UpdateSpUpdSvcInf: Source [ProcessesToRunAfterReboot] section is empty; nothing to do.
116.078: IsRebootRequiredForFileQueue: At least one file operation was delayed; reboot is required.
                              If none are listed below, check above for delayed deletes.
116.078: IsRebootRequiredForFileQueue: e:\exchange\bin\exoledb.dll was delayed; reboot is required.
116.078: IsRebootRequiredForFileQueue: e:\exchange\bin\davex.dll was delayed; reboot is required.
116.078: DoInstallation: A reboot is required to complete the installation of one or more files.
116.078: In Function SetVolatileFlag, line 11576, RegOpenKeyEx failed with error 0x2
116.078: In Function SetVolatileFlag, line 11593, RegOpenKeyEx failed with error 0x2
116.110: UpdateSpUpdSvcInf: Source [ProcessesToRunAfterReboot.RebootNotRequired] section is empty; nothing to do.
116.172: RebootNecessary = 1,WizardInput = 1 , DontReboot = 1, ForceRestart = 0

 

I get really annoyed with the Exchange team regarding their view rebooting…. if we have this on automatic update… we will read on the KB that we don't need a restart when we do… at least both the SBS-WSUS and the real WSUS does properly state that it may require a reboot

 

 

As you can see here…both state "can require restart"

So bottom line…. read the innards of WSUS … as that appears to be a better definitive source of reboot/noreboot information.

3 Thoughts on “The latest Exchange patch does need a reboot…

  1. This one also caused one of my customer’s server to crash when I installed it remotely…beware

  2. The last Exchange SP2 updates I installed stopped the exchange services and failed to restart them on two servers.

  3. I don’t understand why if there are multiple patches that require the service to stop/restart, why can’t they intelligently stop the service(s) for both patches? instead we have patches that stop, restart exchange twice…

Post Navigation