I'have this strange phenomana on a Windows2003 terminal server.
When a user with roaming profile logs on for the first time
(theromaing profile has to be created), it seems to forget that the
usrlogon.cmd has to be executed. There are users experiencing this

One of our employees is currently under investigation and we need to be
about to log their keystrokes for security reasons. Is there a way to log
key stokes in Terminal Server? We are using 2000 and 2003 Terminal Services.

   We have a 2003 domain and a win2K TS that is not part of the domain and
have no plans to add it to the domain. I have an application on the TS that
authenticates with SQL Server via NT security, and therefore does not work.
I have tried domain\user with no luck. What can I do ...

Is there something out there (hopefully free to use) that lists all files and
their sizes that is on my NT server.  I'm wanting to do some cleanup and
would like to be able to see a complete listing instead of having to go
through each folder.

I'm just wondering what the best, most reliable way or the cleanest way to
connect to terminal server is.  I've used a couple of different client
programs, but is there a hands down "best" client program or is it just
users preference?

We would like to track all the attempted logins on out Terminal server.
Whether they are successful or not. Basically we need to know if someone is
trying to hack in.
we are using Windows 2003 and Windows 2000 Terminal Services

Actually My Problem is that in my office everything is secure like in my
firewall outgoing and incoming traffic from all the ports are blocked by
defauly including terminal services port.Now i would like to know how to
connect to my home pc without disturbing the firewall ...

One of the admins I know passed this problem to me, and I'm having trouble
trying to track down just what's causing the issue, thought I'd ask in here
for some thoughts.
Windows 2003 SP0 terminal server (member server) in a 2003 domain.

I just ordered Windows 2003 Server Standard and plan to use it for a
terminal server box in our domain. I also need to order 15 Device CAL's
for Terminal Server in order to allow the 15 workstations to connect to it.
If I understand everything correctly, I install TS in application ...

I m a new in this group,and i hope that this is a corect group for my
question,- I have a problem with win server 2003 and terminal services
users.
Here is the problem:

I managed to get TS setup so that it auto-launches a application when
anyone TS into the server, but that also means that admins get the same
restrictions. What I need is to setup all users except admin level users
so that they get two icons (the two applications) on their desktop ...

We have two Terminal Servers, one running W2K Server SP4, the other W2K3
Server SP1.
Both using Office 2000 (current patches)
Outlook 2000 SR-1 on both systems exhibits the same problem-

I have a client that is looking at some network upgrades.  I'd like to know
if anyone knows if Terminal Server can be set up on XP pro?
THanks!
Rick

I have users using remote desktop to access applications on the server.  How
do I change the start menu to take off the "Shut Down" button?
Dan

I have al laptop with xp home on it and it connected fine to the terminal
server. But the temporary license (90 days) expired and I couldn't connect
to the terminal server anymore.
I then upgrade the machine to XP pro because pro has a CAL build in to it.