|
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Private messages
Log in
|
|
| Author |
Message |
Bouncing Otter Guest
|
Posted: Tue May 16, 2006 11:35 am Post subject: Terminal Server Shutdown |
|
|
OK, i was just about to leave my work yesterday and for some unknown reason
the terminal server which had forty remopte desktops running off it, decided
it would be a good idea just to turn itself off for no apparent reason. The
other two servers next to it however still continued to run. I have checked
the system logs and from what i could see there is no reason i can see for it
to do this. Can anyone help me try and find out what went wrong so i can
prevent it from happening in the future? what should i be looking for? |
|
| Back to top |
|
 |
|
|
Bouncing Otter Guest
|
Posted: Tue May 16, 2006 1:38 pm Post subject: RE: Terminal Server Shutdown |
|
|
And i am aware i may have posted this in the wrong place but wasn't sure
where else to put it. If someone wants to tell me i'll happily repost in the
right place.
"Bouncing Otter" wrote:
| Quote: | OK, i was just about to leave my work yesterday and for some unknown reason
the terminal server which had forty remopte desktops running off it, decided
it would be a good idea just to turn itself off for no apparent reason. The
other two servers next to it however still continued to run. I have checked
the system logs and from what i could see there is no reason i can see for it
to do this. Can anyone help me try and find out what went wrong so i can
prevent it from happening in the future? what should i be looking for? |
|
|
| Back to top |
|
 |
Don Wilwol Guest
|
Posted: Tue May 16, 2006 3:15 pm Post subject: Re: Terminal Server Shutdown |
|
|
Check the event log to start with. Monitor cpu. Depending on what you are
running, 40 remote desktops can be max, especially if you are running legacy
applications. Outlook tends to use a large amount of resources as well.
--
--------
Hope It Helps!
dw
_______________________________
Don Wilwol
Distributed Application Technologies.
dwilwol(DELETE)@datbusiness.com
www.AtTheDataCenter.com (personal website)
www.skysphere.com (hosting available)
"Bouncing Otter" <BouncingOtter@discussions.microsoft.com> wrote in message
news:C80F6BAA-291B-48B2-95DF-628522714B07@microsoft.com...
| Quote: | And i am aware i may have posted this in the wrong place but wasn't sure
where else to put it. If someone wants to tell me i'll happily repost in
the
right place.
"Bouncing Otter" wrote:
OK, i was just about to leave my work yesterday and for some unknown
reason
the terminal server which had forty remopte desktops running off it,
decided
it would be a good idea just to turn itself off for no apparent reason.
The
other two servers next to it however still continued to run. I have
checked
the system logs and from what i could see there is no reason i can see
for it
to do this. Can anyone help me try and find out what went wrong so i can
prevent it from happening in the future? what should i be looking for? |
|
|
| Back to top |
|
 |
Bouncing Otter Guest
|
Posted: Tue May 16, 2006 4:01 pm Post subject: Re: Terminal Server Shutdown |
|
|
first of all, thank you for the post,
erm as i mentioned in my original post i already checked the system logs and
i struggled to find anything to take the blame.
Also, i didn't think that just because the CPU was running at 100% it would
make the thing just switch off, it didn't even restart, just switched off.
Usually when our CPU peaks for a while it just slows down all the remote
desktops for a bit till it sorts itself out. What should i be looking for in
the systems logs?
"Don Wilwol" wrote:
| Quote: | Check the event log to start with. Monitor cpu. Depending on what you are
running, 40 remote desktops can be max, especially if you are running legacy
applications. Outlook tends to use a large amount of resources as well.
--
--------
Hope It Helps!
dw
_______________________________
Don Wilwol
Distributed Application Technologies.
dwilwol(DELETE)@datbusiness.com
www.AtTheDataCenter.com (personal website)
www.skysphere.com (hosting available)
"Bouncing Otter" <BouncingOtter@discussions.microsoft.com> wrote in message
news:C80F6BAA-291B-48B2-95DF-628522714B07@microsoft.com...
And i am aware i may have posted this in the wrong place but wasn't sure
where else to put it. If someone wants to tell me i'll happily repost in
the
right place.
"Bouncing Otter" wrote:
OK, i was just about to leave my work yesterday and for some unknown
reason
the terminal server which had forty remopte desktops running off it,
decided
it would be a good idea just to turn itself off for no apparent reason.
The
other two servers next to it however still continued to run. I have
checked
the system logs and from what i could see there is no reason i can see
for it
to do this. Can anyone help me try and find out what went wrong so i can
prevent it from happening in the future? what should i be looking for?
|
|
|
| Back to top |
|
 |
Trevor Sullivan Guest
|
Posted: Tue May 16, 2006 4:58 pm Post subject: Re: Terminal Server Shutdown |
|
|
Bouncing Otter wrote:
| Quote: | OK, i was just about to leave my work yesterday and for some unknown reason
the terminal server which had forty remopte desktops running off it, decided
it would be a good idea just to turn itself off for no apparent reason. The
other two servers next to it however still continued to run. I have checked
the system logs and from what i could see there is no reason i can see for it
to do this. Can anyone help me try and find out what went wrong so i can
prevent it from happening in the future? what should i be looking for?
|
I wonder if it could be a hardware issue .. is the server comprised of
newer hardware? If not, I wouldn't be surprised if an old power supply
(or maybe even a crappy new one) could be the cause of something like
this. In my past experience with PC hardware, a PSU can be the cause of
many problems even much weirder than what you're describing. If the
server is newer and under warranty, you may wish to notify your hardware
vendor of the problem and possibly get one or more PSUs replaced by
them. Have any changes been made to the server recently (eg. RAM upgrade?).
Trevor Sullivan
Microsoft Certified Professional |
|
| Back to top |
|
 |
Bouncing Otter Guest
|
Posted: Tue May 16, 2006 5:12 pm Post subject: Re: Terminal Server Shutdown |
|
|
Hi Trevor, as far as i'm aware there has been no new hardware added to the
servers an i would be the only one that would really do it aswell, i will get
my companies third party support team to consider the possibility of a faulty
PSU and pass it off as my own suggestion. haha, thanks man, Do you have any
idea what i should be looking for in the system logs in cases like this? Like
what kind of messages?
"Trevor Sullivan" wrote:
| Quote: | Bouncing Otter wrote:
OK, i was just about to leave my work yesterday and for some unknown reason
the terminal server which had forty remopte desktops running off it, decided
it would be a good idea just to turn itself off for no apparent reason. The
other two servers next to it however still continued to run. I have checked
the system logs and from what i could see there is no reason i can see for it
to do this. Can anyone help me try and find out what went wrong so i can
prevent it from happening in the future? what should i be looking for?
I wonder if it could be a hardware issue .. is the server comprised of
newer hardware? If not, I wouldn't be surprised if an old power supply
(or maybe even a crappy new one) could be the cause of something like
this. In my past experience with PC hardware, a PSU can be the cause of
many problems even much weirder than what you're describing. If the
server is newer and under warranty, you may wish to notify your hardware
vendor of the problem and possibly get one or more PSUs replaced by
them. Have any changes been made to the server recently (eg. RAM upgrade?).
Trevor Sullivan
Microsoft Certified Professional
|
|
|
| Back to top |
|
 |
Don Wilwol Guest
|
Posted: Tue May 16, 2006 6:13 pm Post subject: Re: Terminal Server Shutdown |
|
|
Just running at 100% shouldn't shut it down. Extended 100% with misbehaving
apps will however. It is also configurable as to whether it shuts down or
restarts. Right click my computer, properties, advanced tab, startup and
recovery is where its configured.
Does anything show in the DRWaston log?
--
----------
Hope It Helps!
dw
_______________________________
Don Wilwol
Distributed Application Technologies.
dwilwol(DELETE)@datbusiness.com
www.AtTheDataCenter.com
www.skysphere.com
"Bouncing Otter" <BouncingOtter@discussions.microsoft.com> wrote in message
news:9AAB9908-F847-487D-98F8-3657FEFF3747@microsoft.com...
| Quote: | first of all, thank you for the post,
erm as i mentioned in my original post i already checked the system logs
and
i struggled to find anything to take the blame.
Also, i didn't think that just because the CPU was running at 100% it
would
make the thing just switch off, it didn't even restart, just switched off.
Usually when our CPU peaks for a while it just slows down all the remote
desktops for a bit till it sorts itself out. What should i be looking for
in
the systems logs?
"Don Wilwol" wrote:
Check the event log to start with. Monitor cpu. Depending on what you are
running, 40 remote desktops can be max, especially if you are running
legacy
applications. Outlook tends to use a large amount of resources as well.
--
--------
Hope It Helps!
dw
_______________________________
Don Wilwol
Distributed Application Technologies.
dwilwol(DELETE)@datbusiness.com
www.AtTheDataCenter.com (personal website)
www.skysphere.com (hosting available)
"Bouncing Otter" <BouncingOtter@discussions.microsoft.com> wrote in
message
news:C80F6BAA-291B-48B2-95DF-628522714B07@microsoft.com...
And i am aware i may have posted this in the wrong place but wasn't
sure
where else to put it. If someone wants to tell me i'll happily repost
in
the
right place.
"Bouncing Otter" wrote:
OK, i was just about to leave my work yesterday and for some unknown
reason
the terminal server which had forty remopte desktops running off it,
decided
it would be a good idea just to turn itself off for no apparent
reason.
The
other two servers next to it however still continued to run. I have
checked
the system logs and from what i could see there is no reason i can see
for it
to do this. Can anyone help me try and find out what went wrong so i
can
prevent it from happening in the future? what should i be looking for?
|
|
|
| Back to top |
|
 |
|
|
|
|