Susan,
I too have seen the situation where a shutdown command issued through an RDP session fails to actually reboot the computer.
One recent example has these two event log entries:
The process Explorer.EXE has initiated the restart of computer SERVER on behalf of user Domain\Local Admin UserID for the following reason: Application: Maintenance (Planned)
Reason Code: 0x84040001
Shutdown Type: restart
Comment:
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
The process svchost.exe has initiated the restart of computer SERVER on behalf of user NT AUTHORITY\SYSTEM for the following reason: No title for this reason could be found
Reason Code: 0x80070020
Shutdown Type: restart
Comment:
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
The two entries are 9 seconds apart in the order shown here. The next couple entries are 6013 uptime logs until the server is rebooted from the console a couple days later. Not sure what's causing the double shutdown or why it stops the shutdown process from actually happening but it's awfully annoying.
Andrew Fidel
| "Susan Bradley, CPA
aka Ebitz - SBS Rocks [MVP]" <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED] 10/17/2006 01:20 PM
|
|
Agreed, this isn't just this month. This is been happening with
consistency about the last three to four months that we've been tracking
it. Perhaps longer, but that's about the time those of us in the SBS
MVP listserve started realizing that all of us were having to figure out
alternative means to get to RDP sessions that were not coming back after
patching/rebooting.
In the SBS world it can be Exchange grabbing the TS port of 3389 as it
reboots which can be fixed with a reg edit...but mostly we're seeing
boxes, Windows server (and even workstations) flavors of all variety
that are either getting stuck on the way down, or we see that they get
the reboot command and then they don't reboot.
Currently everyone is just 'working around it' by using Ilo, or getting
remotely into another server or workstation and doing a remote shutdown
command... but I'd/we'd like to get to the bottom of it if we can.
It is consistently happening way too often and I'm seeing it reported
much too often.
Thommes, Michael M. wrote:
> Hi Susan,
> I didn't mean to imply that this was just with the last set of
> patches. I think your note says that you have been seeing this for a
> while. We have too. One of the guys in my group uses Update Expert to
> patch and he sees it more often than I do. Of course, he patches a lot
> more servers than I do. Another part of the group uses WSUS and they
> have not mentioned any issues; but then again, they don't TS into
> computers much. And yes, I will bring it up with my TAM (again?). I
> think I had mentioned it to him previously but never started anything
> formal on it.
>
> Mike Thommes
>
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Susan Bradley,
> CPA aka Ebitz - SBS Rocks [MVP]
> Sent: Tuesday, October 17, 2006 10:54 AM
> To: ActiveDir@mail.activedir.org
> Subject: Re: [ActiveDir] The remote computer has ended the connection.
>
> Can you PLEASE call into Microsoft PSS or your tam or pam or whatever
> and report this? Along with anyone else seeing this issue?
>
> I know that calling into PSS can be a pain, but please report this
> issue.
>
> We are seeing this more and more and I need to have bodies called in.
> We seriously need to get to the bottom of this because in the SBS space
> we do a lot of remote management and if the RDP dies we have to fall
> back to ILOs and this isn't acceptable in my book for patching to do
> this.
>
> Do you rely on WSUS?
>
>
> Vinnie Cardona wrote:
>
>> I have noticed that after updating to the latest security patches and
>> rebooting that some (not all) of my servers had an issues with RDP.
>> It cleared after rebooting a second time. Root cause? /Unknown /at
>> this time.
>>
>>
>>
>> -vC
>>
>>
>>
> ------------------------------------------------------------------------
>
>> *From:* [EMAIL PROTECTED]
>> [mailto:[EMAIL PROTECTED] *On Behalf Of *Technical
>> Support
>> *Sent:* Tuesday, October 17, 2006 8:28 AM
>> *To:* activedir@mail.activedir.org
>> *Subject:* [ActiveDir] The remote computer has ended the connection.
>> *Importance:* High
>>
>>
>>
>> Hi,
>>
>>
>>
>> I am trying to access one of my servers using Remote Connection. I am
>> using mstsc but its not connecting me to the server. error "/*/The
>> remote computer has ended the connection/*/". However if i am using
>> /*/_mstsc /v:IP Address /console_/*/ it lets me connect to it.
>>
>>
>>
>> Problem is in this mode i can use only admin id when connected like
>> this. I want my engineers (who dont have administrator priviledges) to
>>
>
>
>> access this. its not possible in this mode.
>>
>>
>>
>> This all happened when i rebooted my server.
>>
>>
>>
>> Please suggest what can be done to normalize the things.
>>
>>
>>
>> Thanks!!!
>>
>> /*/Ravi/*/
>>
>>
>
>
--
Letting your vendors set your risk analysis these days?
http://www.threatcode.com
If you are a SBSer and you don't subscribe to the SBS Blog... man ... I will hunt you down...
http://blogs.technet.com/sbs
List info : http://www.activedir.org/List.aspx
List FAQ : http://www.activedir.org/ListFAQ.aspx
List archive: http://www.activedir.org/ml/threads.aspx
