Terminal Services in Windows Xp

  • Thread starter Thread starter Navodit
  • Start date Start date
N

Navodit

Hi

I am trying to get a client-server distributed application working which was originally developed in 2000. As part of the setup, I am required to :

1. Install Terminal Server and Terminal Client on the host computer
2. In the Terminal Services configuration, under the properties of RDP-Tcp, on the Logon settings tab, un-select "Always Prompt for Password".
3. Create Connection "foo" in the Terminal Services Client manager, and make it point to some *.bat on the computer.
4. setup login info "Administrator/passwd/workgroup".

The problem is that I am required to set up this application on a Windows XP machine !

After some hours of googling on the subject, I found that in windows xp, the terminal server is inbuilt and for the terminal client we have remote desktop connection. Is this correct ?

I am not sure how the above steps can be replicated on a Windows XP machine ....

Can someone provide a general mapping between windows 2000 and windows xp as far as terminal services are concerned ? Especially how I can create a connection "foo" pointing to some batch file... Somewhere later in a .asp file in the application, it is required to run: mstc foo. I found that the mstc.exe application is in the windows\system32 directory on a windows xp machine. However how to create the connection is a mystery... Do I need to install some software for this ? Any help or suggestions would be appreciated. Thanks.

p.s.: If you think that this query is better directed to a different newsgroup then please let me know the name of that newsgroup...
 
Your instructions, as you point out, are for windows 2000 - Windows 2000
server, that is. Server 2003 can be configured as Windows 2000 Server. But
XP is a single user OS. Even if you coud set those options, there wouldn't
be any point because only one user (either the local user OR one remote
user) can be logged on at the same time. In Server (2000 or 2003), you can
have 2 simultaneous unlicensed connections in addition to the local user. On
either of those OS's you need terminal services licensing installed if you
want more than 2 simultaneous remote connections. If you have 2000 server,
use that for your terminal server OS. It has no CAL requirements as long as
users connect from a professional desktop OS (2000 pro or XP Pro). In Server
2003, you must have a CAL or terminal services CAL for each connection.

...kurt
Hi

I am trying to get a client-server distributed application working which was
originally developed in 2000. As part of the setup, I am required to :

1. Install Terminal Server and Terminal Client on the host computer
2. In the Terminal Services configuration, under the properties of RDP-Tcp,
on the Logon settings tab, un-select "Always Prompt for Password".
3. Create Connection "foo" in the Terminal Services Client manager, and make
it point to some *.bat on the computer.
4. setup login info "Administrator/passwd/workgroup".

The problem is that I am required to set up this application on a Windows XP
machine !

After some hours of googling on the subject, I found that in windows xp, the
terminal server is inbuilt and for the terminal client we have remote
desktop connection. Is this correct ?

I am not sure how the above steps can be replicated on a Windows XP machine
.....

Can someone provide a general mapping between windows 2000 and windows xp as
far as terminal services are concerned ? Especially how I can create a
connection "foo" pointing to some batch file... Somewhere later in a .asp
file in the application, it is required to run: mstc foo. I found that the
mstc.exe application is in the windows\system32 directory on a windows xp
machine. However how to create the connection is a mystery... Do I need to
install some software for this ? Any help or suggestions would be
appreciated. Thanks.

p.s.: If you think that this query is better directed to a different
newsgroup then please let me know the name of that newsgroup...
 
Also, careful about posting in html or rtf - you'll get flamed!


Hi

I am trying to get a client-server distributed application working which was
originally developed in 2000. As part of the setup, I am required to :

1. Install Terminal Server and Terminal Client on the host computer
2. In the Terminal Services configuration, under the properties of RDP-Tcp,
on the Logon settings tab, un-select "Always Prompt for Password".
3. Create Connection "foo" in the Terminal Services Client manager, and make
it point to some *.bat on the computer.
4. setup login info "Administrator/passwd/workgroup".

The problem is that I am required to set up this application on a Windows XP
machine !

After some hours of googling on the subject, I found that in windows xp, the
terminal server is inbuilt and for the terminal client we have remote
desktop connection. Is this correct ?

I am not sure how the above steps can be replicated on a Windows XP machine
.....

Can someone provide a general mapping between windows 2000 and windows xp as
far as terminal services are concerned ? Especially how I can create a
connection "foo" pointing to some batch file... Somewhere later in a .asp
file in the application, it is required to run: mstc foo. I found that the
mstc.exe application is in the windows\system32 directory on a windows xp
machine. However how to create the connection is a mystery... Do I need to
install some software for this ? Any help or suggestions would be
appreciated. Thanks.

p.s.: If you think that this query is better directed to a different
newsgroup then please let me know the name of that newsgroup...
 
What I need to do is to have an application server so that other clients can
log in and work on different workstatons and use softwares like autocad etc
installed only on the server machine. Earlier this system was developed on a
windows 2000 system. Now I have installed everything from scratch on a
windows xp machine. I did not fully understand your statement.... Do you
mean to imply that it is NOT possible to have such an application on a
windows xp machine ? Or do you mean something else ? Could you please
clarify ? Thanks...
 
You cannot have multiple simultaneous desktops on Windows XP. I don't know
of any clearer way to put it. XP supports one and only one user at a time.
It is worthless as a terminal server. You need either Citrix or a Windows
SERVER Operating System to accomplish this (Window 2000 Pro does not support
remote desktop at all). For the sake of budget, it's cheaper to do it on a
Windows 2000 server than Server 2003 because of the licensing diferences.
Either way is cheaper than Citrix in a small environment. You can often get
Windows 2000 server with up to 25 licenses on eBay for $300 - $500, a
bargain price. Be Certain that it is a legal, unregistered copy. Even with
Windows 2000 Server, your clients will have to be running Windows 2000 Pro
or Windows XP PRO (NOT XP HOME) to connect (after the 120 day license grace
period expires). If they are running XP Home or anything pre-2000, you'll
need to buy a TS-CAL (Terminal Server Client Access License) for each
connection. Also be aware of multi-user licensing requirements for AutoCAD
when installed on a terminal server. AutoCAD is a HUGE resource hog, and if
you plan on having it running in several instances on the same computer,
you're gonna need a whopper of a computer.

....kurt
 
Back
Top