Controlling single session signon Windows 2003 Server Std. Ed.

[kapshure]

Scenario:

Windows 2003 Server Std. edition in Terminal Service Administration
mode.

In Terminal Services Configuration, under RDP-TCP properties, then
network adapter tab, the maximum amount of connections allowed is (1).
Also, in the policy settings under "Server Settings" the entry for
"Restrict each user to one session" is set to "YES".

Here is the problem. I have a shared account that is used by
contractors who monitor an application for us. This account, say
XYZADMIN, relies on an application being visible upon logging in to
verify certain things; any changes or additions done to said
application must be performed under the XYZADMIN user context so when
the contractor logs in they see the same thing I just finished with. To
clarify if needed, say I make a change to this application, I would
then just disconnect so when they login to this session with XYZADMIN
they see the application just as I left it.

What's happening is say I do some work in this application under
XYZADMIN, and then disconnect---when the contractor logs in, they just
see a fresh desktop with the application not open.

Furthermore, I know the settings that I mention above DO work as we
have a total of 14 Windows 2003 servers (all same hardware, all same
configuration, etc.) and this works on some systems, but I have (3)
where this is not. If you're curious about the systems themselves and
their deployment methods (to insure identical configuration): These are
HP BL30 blades, that were all deployed via drive cloning. These systems
were also all NEWSID after deployment was complete.

I just don't understand why the exact setup works on 3/4 of our
systems, but not on the rest. Any help would be greatly appreciated.

Thanks,

Jonathan

 

[Guest]

Could you have them logon to the console session via mstsc /console so you
can be assured that they always get the correct session.