Re: After reboot, can't use admin Terminal Server on SBS 2003
- From: "Dave Nickason [SBS MVP]" <gwdibble@xxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 17 Jan 2008 12:23:48 -0500
People who have been running into this are coming up with workarounds. One
I like is to schedule a reboot an hour out, using the "shutdown" command.
If the server restarts as expected, go in and kill the scheduled task. If
it doesn't restart, the scheduled task will kick off in an hour, and that
restart will restore your access.
I have not yet heard of any instances where the shutdown command fails to
work, either scheduled or run remotely from a desktop PC.
"Jim Graue" <JimGraue@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:F23AFD9D-E06F-4620-8772-F6EC5E1B1212@xxxxxxxxxxxxxxxx
Hi, Dave:
You were, of course, right. Thanks again for your help. Rebooting
brought
back admin TS on the SBS.
--
Best regards,
Jim Graue
"Dave Nickason [SBS MVP]" wrote:
There's a bug where restarts sometimes fail if initiated remotely. You
seem
to be able to access computer management remotely to read the logs,
right?
So in the System log, you should see something that indicates the restart
request. Do you see any follow-up indicating that the server restarted?
Normally, I just look at the eventlog ones - there should be one
indicating
the logging stopped, then one indicating it's starting, then one saying
started. If you don't have those, then the system failed to restart.
The
only thing that will solve this is to reboot it from the console. Or,
often
(but probably not always), you can use the shutdown command from a
workstation. I just do Start -> Run -> shutdown -i and use the resulting
GUI to tell the server to restart.
This most often shows up when applying updates over RDP, probably because
that's mostly when people attempt to initiate restarts over RDP.
However,
it's been documented to happen at other times, and regardless of how you
attempt to initiate the shutdown. It seems like that shutdown command
from
the remote PC is most reliable. I've stopped patching remotely, except
in
instances where I can get to the server fairly rapidly if it does this -
for
example, I do it from my desktop PC, but not from home.
"Jim Graue" <JimGraue@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:288F10F1-C46D-4D00-BF3D-EB05586D962A@xxxxxxxxxxxxxxxx
Modem issues begged for a reboot, which I performed remotely (office is
too
busy during the day to do it). Afterward, I was unable to logon
remotely.
I
get to the office this AM and cannot logon to a console session using
MMC's
RD snap-in (though I can logon at the console), nor can I logon using
RDP.
I'd like to reboot, again, just to see if things clear up, but I'm not
getting errors in eventvwr. Any thoughts are appreciated.
--
Best regards,
Jim Graue
.
- Follow-Ups:
- References:
- Re: After reboot, can't use admin Terminal Server on SBS 2003
- From: Dave Nickason [SBS MVP]
- Re: After reboot, can't use admin Terminal Server on SBS 2003
- From: Jim Graue
- Re: After reboot, can't use admin Terminal Server on SBS 2003
- Prev by Date: Re: One user having messages stuck in Local Delivery
- Next by Date: Re: Access to files for guests
- Previous by thread: Re: After reboot, can't use admin Terminal Server on SBS 2003
- Next by thread: Re: After reboot, can't use admin Terminal Server on SBS 2003
- Index(es):
Relevant Pages
|
