Steven said:
Under Windows 2000 Server, Terminal Services gave me the ability
to have multiple user sessions; that is to say, my remote
connection was distinct from the actual local console session.
This does not appear to be the case with Windows XP Professional
Remote Desktop. So, the questions:
1) Am I missing something which will enable multi-session rDP?
2) If there is no multi-session rDP, does anyone know why we've
taken a step backwards?
3) Does anyone know if there are plans to make multi-session rDP
function in the future? If so, any idea when?
Thank you for the pointers! The only thing left is whether or not
MS has plans to add this feature or not (the beta SP2 DLL suggests
to me that it might be coming in SP2; if so, Yippee!!), and I've
take your suggestion and filled out the MS inquiry form form your
second link.
I just added this to the other discussion - and I believe it relevant here
as well..
(Also - please note that Service Pack 2 (SP2) was already released without
the feature over a year ago.. Maybe it will make a comeback in SP3 - but
maybe not.)
Would it be useful to be able to log concurrently into Windows XP?
Yes. Very much so - in reference to corporate admins and fixing things in
the background of their machine(s) or doing unique software installs
(without bothering the user) when a push situations wouldn't work (albeit
seldomly needed - but sometimes just faster in the short run.)
Could it have a use in the way you describe it? Not remotely logging into a
system, but in fact a concurrent logon to your own PC for administrative
purposes?
- As a software developer - I could see this being very useful. But "Switch
User" would work as well and is already part of the system. However, it
could be that the software developer is in a larger environment (domain) and
thus this option is not available - so again a viable option for testing and
tweaking.
- As a stand-alone user - I doubt this 'feature' would get used much - since
switch user is already available in all versions of XP not joined to a
domain.
- As a system administrator (large or small) - I could see the use remotely,
but as for one's own system - I still have trouble seeing the usefulness -
but arguments for and against can go both ways for this group - depending on
style of administration (GUI or command-line oriented.)
So if I was going to vote one way or another - perhaps a feature available
in the Professional editions but not the home (which is easily implemented
at this point, since Home does not have Remote Desktop anyway) and/or one
only available *if* "Fast User Switching" was turned off - such as would
occur in a domain environment.
Although the way I put it may seem restrictive - at least you know in that
way it would not be turned on "by accident" by "Joe Public" and thus a
possible source of future security issues. It also gives System
Administrators and software developers more options once in a domain
environment for managing their own and other systems.