Terminal Server Resource Errors - Help

[ITJunkie]

Hi,

A little background, I have taken over a TS environment for a company with many locations that RDP into HQ. There are roughly 55 users using this particular Terminal server that I keep getting resource errors when users try and connect. However, most of the client terminals are just POS systems and there is only about 15 or 20 users that have full access in terms of internet, email and Office suite.

Original setup has all users just using Local Profiles on that server. It has been my understanding that in TS environments it is a good idea to use Roaming Profiles for users that bounce around between multiple systems. Looking for confirmation of that.

My problem is that some users can login fine and eventually some users will get "Not enough resources available..." error when they try to connect. This server is getting low on disk space and everything I've found seems to point in that direction as the problem. I'm hoping someone can confirm this or point me in the right direction.

I have tried moving some users to roaming profiles and have freed some disk space that way. I'm rather new to this kind of setup so any help in proper setup would be appreciated.

Thanks,

~Bill

 

[dphantom]

The not enough resources generally happens when there are too many users logged in at any one time. A registry change should take care of that.

1) Create/edit these values in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory
Management
"PoolUsageMaximum"=dword:00000030
"PagedPoolSize"=dword:ffffffff
2) Restart.


WARNING: Use at own risk, test thoroughly, no warranty implied or expressed, yada, yada, yada.

As for profiles, yes, if disk space is a problem by all means move your users to roaming profiles. You will want to manage profile size though if users are connecting over slow links or their profiles are very large. Even at T-1 speeds, loading a 500MB profile can take some time and users will not be happy.

 

[ITJunkie]

Thanks DP...I will give that a shot.

 

[netsysadmin]

I just cant imagine that roaming profiles would be good in this situation. they can get quite big and hog up bandwidth while transferring over.

John

 

[dphantom]

Below is the MS KB article I referred to.

Link

As for roaming profiles, it depends, but you really have to be aware of size and available bandwidth. One can manage size pretty well with some scriptis or third party tools. Generally though, I would design a solution where profiles are stored on a local server if one is available.

In this case, profile size is a side issue. The real problem almost certainly is the pagedpool.