"jokes54321" <> wrote in message
news:%...
> You certainly missed my point Lawrence.
No, actually I did not miss it, I was merely pointing out that the situation
would have never occurred had it not been for your choice of operational
procedures which are not in the best interest of operating a production
Terminal Server system.
> The point is, when a message box appears and says Reboot Now or Close, it
> should do exactly that.
I can't comment on what exactly happened to you the other day, but I (just
now) went to Windows Update with a test Windows 2000 Server system I have,
installed an update, and received the Reboot Now/Close dialog that you
describe -- the same Reboot Now/Close dialog box that's been in use at
Windows Update for eons -- clicked on Close, and my system did not reboot.
In fact, the Close button worked perfectly for me. It closed the dialog, and
then took me to a web page called "Your Results", which very politely
reminded me that my system needs to be restarted for the updates to take
effect.
> If it doesn't, then I think I have every right to take a shot at Microsoft
> for coding it incorrectly.. I'm certainly not a Linux junkie looking for
> an excuse to blame MS, I put blame where it is due.
Obviously from your dozens of successful uses, and my successful use just
moments ago, the dialog box is not "coded incorrectly".
As to what exactly happened in these two instances would only be speculation
on my part; but as to the suggestion that Microsoft "caused" your problem, I
do think that is reaching a bit, and a misdirected attempt at shuffling off
responsibility to a non-responsible party.
> Your response ****ed me off so much I spent the last hour trying to find
> an article to support your opinions. I didn't find any. Not that I'm
> saying you're wrong, but I didn't find anything supporting your opinions
> either.
My /opinions/ about the recommended practice for updating Terminal
Servers??? No, you probably won't find any "supporting articles". I pretty
much am the original author of those, albeit with significant collaboration
from numerous WSUS testers and administrators, having responded to a few
similar situations in the WSUS newsgroup from WSUS administrators who tried
to do the same thing to their Terminal Servers (update them in the middle of
the day with users logged on) and had them blow up in their faces too.
> I would think that if it was so critical that all users were booted that
> the Windows Update software would enforce that..
Yeah.. well..... ya know, Microsoft has to delegate some sort of
responsibility to the server administrators. Shucks, if they automated
everything, we'd be out of a job! (And, I note, the /second/ attempt to push
the responsibility off somewhere else rather than where it appropriately
resides.)
> Regardless of patching policies, this post boils down to a Reboot Now
> button or a Close button. The close button should not reboot the server,
> so step off your soapbox and drop your condescending attitude.
The Close button does not reboot the server.
As for my 'condescending' attitude, perhaps it is.... but I do expect a
higher level of performance from somebody who claims responsibility for the
operation of seven Terminal Servers! Installing updates in the middle of the
day while the servers are live just doesn't fit that mold. Much less
suffering through the ensuing restart.
Shucks, in some environments, you would have been terminated for that faux
paus.... especially if subsequent 'investigation' determined that the cause
was totally avoidable by more responsible procedures -- which it is.
Or let me put this a different way... I can totally understand the mistake
that caused the restart. I'll even concede your belief that you clicked on
Close, though current empirical evidence suggests that did not happen. I can
even understand the lack of awareness of the risks involved in updating
Terminal Server systems with active sessions. But I'm a bit pressed to
overlook the attempt to blame the problem on somebody else -- and /that/ is
what triggers my 'attitude' about this matter.
> "Lawrence Garvin" <> wrote in message
> news:...
>>
>> Actually..... it's bad enough that you're patching Terminal Servers
>> during the workday at all!!
>>
>> And blaming MS for what is, most likely, your own operational issue, is a
>> cheap shot. There's lots of things out there to legitimately criticize
>> Microsoft for, but don't blame them because you're using unreliable
>> procedures on mission critical servers.
>>
>> Recommended practice for patching Terminal Servers:
>>
>> 1. Remove ALL Terminal Server login sessions from the server.
>> 2. BLOCK Terminal Server logins.
>> 3. Apply updates and restart immediately.
>> 4. ALLOW Terminal Server logins.
>>
>> "jokes54321" <> wrote in message
>> news:%...
>>> We have 7 Terminal Servers and each one reboots itself once a week.
>>>
>>> Usually I apply the Windows Updates during the day and click no to the
>>> reboot so the servers can reboot themselves in the middle of the night.
>>>
>>> Today when I installed the updates on two servers I had two options
>>> appear at the end of the install, Reboot Now and Close.
>>>
>>> I hit close and low and behold, both servers shut down in the middle of
>>> the day.
>>>
>>>
>>> It's bad enough that I am patching servers to keep them safe and up and
>>> running just to have MS bring them down for me..
>>>
>>> I sure hope Microsoft has someone reading these.
>>>
>>>
>>>
>>
>>
>
|
Similar Threads
Linear Mode
