users Docs and Settings

[Guest]

Is there a way to not have every user that i create, for a Win2k3 TS, not
have a folder under "Documents and Settings" folder.
I believe that when i have several people logon and off that it is slowwing
down my server and locking them up, waiting fo the server to catch up.
I just want to be able to creat a user so that he can login and run the
program that i tell them to run and them logoff. NO OTHER FLUFF!!

Thanks

 

[Vera Noest [MVP]]

The data under "Documents and Settings" is the users profile. And
no, you can't have a user without a profile.

If you have not defined any profile for the user, they get a local
profile. This means that the profile is created the first time a
user logs on to the TS as a copy of the Default User profile. When
the user logs off from the TS, the profile is saved and stays on
the TS. Next logon, the profile is already there, so I don't think
that this could cause your server to slow down.
Disadvantages of local profiles are: users will have different
settings on different Terminal Servers + the C: drive of the TS can
easily fill up with the user profile data.

If you have defined a roaming profile for the users (on a network
share), then the centrally stored roaming profile is copied to the
TS when the user logs on (to "Documents and Settings"). When the
user logs off, changes made to the locally cached profile are saved
back to the centrally stored roaming profile. The advantage of this
is obvious when you have more than one Terminal Server: changes in
users settings will follow them from one TS to the next.
Copying of the profile could potentially slow down the logon and
logoff process, but you should always combine a roaming profile
with excluding some data from roaming with the profile (temporary
files, temporary Internet Explorer files, and so on). This is
actually the default. You should also delete the locally cached
copy of the roaming profile from the server when users log off, to
avoid filling up your C: drive.

Tell us a little bit more about the problem that you have with your
server:
* When exactly is it slow or even locking up?
* Does this only happen during logon and logoff, or also in the
middle of a session?
* When this happens, does it happen to all connected users
simultaneously, or only to some?
* When this happens, can you still logon to the console of the
server?
* Does the server recover itself after some time, or do you have to
reboot to get it responsive again?
* Is there anything in the EventLog on the server when this
happens?
* Have you checked in Task Manager if a process is using 100% of
the CPU when this happens?

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
___ please respond in newsgroup, NOT by private email ___

 

[Guest]

The lockups seem to be when they are either working on the TS or when they
are logging off.

It seems that one locks up the server will become slow or 100% utilization,
ts will lockup or freeze for about five minutes and then it will kick
everyone off of the server.

the server will recover about five or so minutes the utilization will go
back down to about 5%

There is nothing in the logs and usually i can't get to the processes screen
to see anything until it recovers.

I have tried most everything that i know. server packs, change router,
security.

Thanks for all the help.

 

[Vera Noest [MVP]]

OK, there are a number of hotfixes regarding freezing 2003 TS.
Read the description of each of them, and check which one matches
your situation. Log on to the console, open Task Manager and
Terminal Server Administration, and then make another user try to
provoke the problem as described in the articles (logging off;
logging off after the session becomes idle, etc). Watch the
processes in that session to see if it really closes.

821467 - Windows Server 2003 Terminal Server Stops Responding
http://support.microsoft.com/?kbid=821467

826139 - Windows Server 2003-Based Computer Becomes Unresponsive to
RDP Sessions
http://support.microsoft.com/?kbid=826139

828662 - Terminal Server stops responding when idle sessions are
being ended
http://support.microsoft.com/?kbid=828662

832971 - Terminal Services stops responding on your Windows Server
2003 server
http://support.microsoft.com/?kbid=832971

886675 - You cannot establish new Terminal Services connections to
a Windows Server 2003-based terminal server
http://support.microsoft.com/?kbid=886675
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
___ please respond in newsgroup, NOT by private email ___

 

[Guest]

If you're just looking for your user to use a single program via TS, the RDP
can be edited so that when dbl clicked, a TS session starts with just the
single intended app running. No other frills or options. This is setup on the
RDP clip itself. The way to set it up can be different depending on the
version of the RDP clip the user is using.

But with the latest version , open the RDP clip, click OPTIONS, select the
Programs tab, click a check in the "Start the following program when
connecting", and finally type in the proper folder path of the exe file you
wish to instigate.