• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 343
  • Last Modified:

Windows 2008 R2 Terminal Server Crashing out users

Had this problem since we installed a fresh Windows 2008 R2 running remote desktop services for up to 15 users.
Just wondered if anyone has encountered this before and has a fix?

We've tried various Windows Hotfixes downgraded Office 2013 to Office 2010 and changed the network switches around etc but yet it still continues to happen at random!
It can run for the best part of  a week before a user calls in and reports their session is frozen and when we log in as an admin to see what's going it's just stuck on applying settings when logging and nothing ever happens! Only way to get it back up and running is to force a reboot using remote UPS login. They have a seperate SBS 2011 and a serperate database Server running on windows 2008 R2 and these don't have a problem it's just the 2008 R2 terminal server which seems affected and the event logs don't give any clue as to what might be causing it.

Would appreciate if anyone has any feedback on this problem?

Many Thanks in Advance
0
CRL ltd
Asked:
CRL ltd
1 Solution
 
s3e3Commented:
Without any decent event log errors to review it sounds more like a hardware issue.
What type of hardware is it sitting on ? Under warranty ?
Was this hardware ever used before ?

Is it only happening when a specific user logs in or can you replicate the crash ?
0
 
donciakasCommented:
1. are You using licensed software?
2. does Your windows 2008 R2 terminal server has all the updates installed?
3. do you have any antivirus software installed on Your TS? what it is?
4. What software do users use on TS? is it compatible with 2k8 r2 server?
5. what are start-up applications/servises for user/server which launch on user login?
0
 
CRL ltdAuthor Commented:
completely licensed software and their databases run on 64bit PC's with any issue and claim to be supported. Trend is our anti-virus software but we've run this version on other Remote Desktop Servers on this spec without any issue.
All Windows updates are on and there are no out of the ordinary application or services starting at user login. Their LOB applications are actually hosted on another member Server so it's not like the terminal server is the main host for their x2 business database products either!
Seems to be random all users log in without an issue it just suddenly drops them off i.e. crashing their session at random almost like 1 by 1 they hang while other users remain working on it ok until it eventually filters through to them.
0
 [eBook] Windows Nano Server

Download this FREE eBook and learn all you need to get started with Windows Nano Server, including deployment options, remote management
and troubleshooting tips and tricks

 
Michael MachieFull-time technical multi-taskerCommented:
Do you have a limit set for the number of connections allowed? Could it possibly be that when the threshhold is reached the next logon crashes someone else?
0
 
CRL ltdAuthor Commented:
I haven't configured any limits where would they be set?
0
 
Michael MachieFull-time technical multi-taskerCommented:
On RDS Server running Server2008:

(This is copied from the microsoft rds help file)

To configure the number of simultaneous remote connections allowed for a connection

On the RD Session Host server, open Remote Desktop Session Host Configuration. To open Remote Desktop Session Host Configuration, click Start, point to Administrative Tools, point to Remote Desktop Services, and then click Remote Desktop Session Host Configuration.

Under Connections, right-click the name of the connection, and then click Properties.

In the Properties dialog box for the connection, on the Network Adapter tab, click Maximum connections, enter the number of simultaneous remote connections that you want to allow for the connection, and then click OK.

If the Maximum connections option is selected and dimmed, the Limit number of connections Group Policy setting has been enabled and has been applied to the RD Session Host server.

Additionally, you can also set the maximum number of simultaneous connections allowed for an RD Session Host server by applying the Limit number of connections Group Policy setting. This Group Policy setting is located in Computer Configuration\Policies\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Connections and can be configured by using either the Local Group Policy Editor or the Group Policy Management Console (GPMC). Note that the Group Policy setting will take precedence over the setting configured in Remote Desktop Session Host Configuration.

For more information about Group Policy settings for Remote Desktop Services, see the Remote Desktop Services Technical Reference (http://go.microsoft.com/fwlink/?LinkId=138134).


 
0
 
CRL ltdAuthor Commented:
This was finally resolved with a  re-install of the OS. It appears some legacy GPO's may have had incompatible registry settings.
0
 
CRL ltdAuthor Commented:
Self solved
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now