Re: Post SP1 shutdown slow

http://support.microsoft.com/default.aspx?scid=kb;en-us;322672

Until the dsrestore is fixed up ...manually sync up the passwords [which I will be doing myself]

Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP] wrote:

The dsrestor is a issue that got broken with Windows 2003 sp1 and will be fixed. Make no mistake about that it's a key function that has been broken by the security changes in SP1.

This KB is meant for pre sp1 boxes only.

You said you had a box taking 8 minutes... PSS said 10 minutes would be unreasonable.

Call them.

Gary Karasik wrote:

The slower shutdown we have now fixes the issue where we could potentially damage the server.


Nonsense. The problem with services shutting down too quickly was fixed by changing the WaitToKillTimout from RegDWord to RegSZ. If you made that change, which I did, the problem was fixed. That hasn't been changed by SBS/SP1.

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. Mty pre-SBS/SP1 systems that shutdown more quickly have the exact same registry value as systems that shut down more slowly post SBS/SP1. That's the part they're blowing smoke about. They don't know what the problem is, and they're too lazy to find out. They just want to give a response they hope people will accept and go away. They've taken the exact same approach with the DSRESTOR issue.



If you think it's too slow go call PSS.


And the point of this would be? You've already relayed their position.

GaryK

"Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]" <sbradcpa@xxxxxxxxxxx> wrote in message news:%23iJUsivmFHA.2080@xxxxxxxxxxxxxxxxxxxxxxx


Iit was killing services before it was fixed in the SP, Gary...
Services may stop abruptly when you shut down or restart a Windows Small Business Server 2003-based computer:
http://support.microsoft.com/?id=839262


This hotfix is already included in our Service pack and thus this new hotfix doesn't do anything..it's only for the non SP'd machines

The slower shutdown we have now fixes the issue where we could potentially damage the server.

The problem that was there before was 'copped" to it Gary..

If you want to shut down the way it did...go muck up the registry and possibly mess up the server...if that's what you want..follow that KB to undo the fix to the waittokilltimeout

The problem with the KB is that it hints like we need it and we don't..it's already in the SP1. Remember how I said it didn't make any sense that the file in the KB was the same date as the one on my SBS sp1 server?

The KB says "you need SP1 before you apply this" and what it's meaning is that you need Exchange 2003 sp1 before applying this.

If you think it's too slow go call PSS.

Gary Karasik wrote:



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



--
An open letter to the Security Community:: http://msmvps.com/bradley/archive/2004/12/12/23540.aspx







--
An open letter to the Security Community:: http://msmvps.com/bradley/archive/2004/12/12/23540.aspx
.

Relevant Pages

  • 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: Post SP1 shutdown slow
    ... The slower shutdown we have now fixes the issue where we could potentially damage the server. ... Remember how I said it didn't make any sense that the file in the KB was the same date as the one on my SBS sp1 server? ... The KB says "you need SP1 before you apply this" and what it's meaning is that you need Exchange 2003 sp1 before applying this. ... 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. ...
    (microsoft.public.windows.server.sbs)
  • RE: The Infamous "General Network Error"
    ... Since SP1 puts out a newer System.Data.DLL, if you go this route I would ... the only thing that's left to try is> the fix described in MS KB 823679. ... > OS: W2k server, running IIS with MS ASP.NET> 2nd Client: ... W2k server, my app is deployed as Windows Service> ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: Post SP1 shutdown slow
    ... Make no mistake about that it's a key function that has been broken by the security changes in SP1. ... 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. ... Services may stop abruptly when you shut down or restart a Windows Small Business Server 2003-based computer: ...
    (microsoft.public.windows.server.sbs)
  • Re: Cannot find member name System.Data.SqlClient.SqlError
    ... on a Windows 2003 server WITHOUT SP1, ... Microsoft will fix this. ...
    (microsoft.public.dotnet.framework.remoting)