Re: Post SP1 shutdown slow

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance



> That KB is supposed to say "Needs Exchange 2003 sp1" not SBS sp1...

I'm not understanding the poing you're making. They're touting this hotfix
as a cure for the slow-shutdown process, and it's not.

> I talked to PSS about that and they said unless it's taking 10 minutes or
> more it's perfectly fine.

Perfectly fine with whom? It's pretty cavalier of them to decide what's
perfectly fine for me. The "Windows is shutting down" part of the shutdown
process is taking nearly 4 times as long as it did pre SBS/SP1--2:45 vs :35
seconds--and extending the shutdown from 5 to nearly 8 minutes. That adds up
when you're doing maintenance on multiple servers.

> If you remember what that fix is doing [remember the registry fix we had
> to do pre sp1?] it was killing the running services and potentially
> harming things.

Which fix are we talking about here?

> You want a fast shut down that kills processes and possibly damages your
> server or you want a graceful shutdown that keeps everything in good
> shape?

I want it to shutdown the way it did before SBS/SP1. I certainly don't
expect a Service Pack to make things worse.

> If you want a faster shut down manually shut off Exchange first. It's
> Exchange and AD and the price we pay for all on one box.

But there was no problem with this pre-SBS/SP1, and there's a problem now.
Even if manually shutting down Exchange does solve this (and I'm not
convinced it will since PSS has been pushing non-fixes lately), how does it
speed up the shutdown process? Add the time it takes to manually shutdown
Exchange, and it will take nearly as long to shutdown the server as it now
does without manually shutting down Exchange. Additionally, if this is so
simply a fix, why wasn't it incorporated into SBS/SP1?

They've introduced a problem and are now ducking responsibility. Surprising?
Not really. As with the DSRESTOR error, this seems to be the new tack
they're taking: 1) Provide a spurious response as to cause; 2) If that
doesn't satisfy people, provide a spurious fix; 3) If that doesn't satisfy
people, say that we'll fix it Real Soon Now.

PSS is blowing smoke on this. I don't think I'm being unreasonable in
objecting to a Service Pack making things worse, which is what this one is
doing. Is this new, slower shutdown a serious problem? No. Is it annoying?
Yes. And it's even more annoying to have PSS making that decision for me. At
the very least they should cop to the problem honestly and put it in the
release notes. Nor should they be pushing a hotfix that takes me a half-hour
of phone time to get and than doesn't fix the problem. For PSS to be
claiming a hotfix will fix something it won't is simply unacceptable.

GaryK

> Gary Karasik wrote:
>
>>Hi,
>>
>>Post install of SBS/SP1 (note: this does not happen post Server 2003 SP1;
>>it happens only after install of SBS/SP1), the server takes nearly two
>>minutes longer to shut down.
>>
>>This problem is NOT solved by hotfix 887539.
>>
>>GaryK
>>
>>
>
> --
> An open letter to the Security Community::
> http://msmvps.com/bradley/archive/2004/12/12/23540.aspx


.



Relevant Pages

  • RE: CommandBarControl - keeping them tied to the menu item
    ... the fix for this problem will be provides. ... Why I suggest contact MS PSS is ... request for a hotfix. ... Microsoft Online Partner Support ...
    (microsoft.public.office.developer.com.add_ins)
  • Re: Post SP1 shutdown slow
    ... > damage the server. ... What you're not getting here is that this post-SBS/SP1 slower shutdown has ... nothing to do with the fix in the article you cite. ... > If you think it's too slow go call PSS. ...
    (microsoft.public.windows.server.sbs)
  • Re: Event ID 8331
    ... Scott, Thanks for the note. ... I called PSS and they couldn't find ... anything related to that hotfix or the event ID. ... >There is a hotfix to fix this error..You will also notice ...
    (microsoft.public.exchange.admin)
  • Re: I need a hotfix for windows 2003 dns problem.
    ... > DNS Server Service ... > I need to obtain a hotfix for the problem above. ... Call MS PSS, choose the option to get a hot fix, give them the KB article ...
    (microsoft.public.win2000.dns)
  • Re: Outlook with TLS/SSL
    ... If it's a hotfix, no you can't just "Grab" it from somewhere. ... calls to PSS for hotfixes are free. ... > Is there a place where I can grab the fix (I'm assuming the fix is to be ...
    (microsoft.public.exchange.admin)