install a xp pro terminal server with windows server 2003 server

Hello!
Can someone tell me how to install there a post on xp pro terminal server with windows server 2003 server! I want to install stations TSE agent in these positions are under windows xp pro and this siege is a server in Win2003 server.
So I am asking on how to install there a post in win xp pro mode TSE.
Thank you:)

TSE is the client originally installed with Windows XP. It is called "Remote Desktop Connection".

As I know that, windows server 2003 remote desktop that support two connection for admin use. If you wish for a limited time for users who could remote connect to you windows server 2003.

Then, you should install terminal server. At the beginning, that support 60-90 ( the more precise value should be 60 days from installing it )

This is a period that allowed you to setup all thing and if it works then, you should obtain lisence from microsoft.

A final remind, terminal service was support on windows 2000 workgroup, windows 2000 domain, windows server 2003 workgroup, windows server 2003 domain.

XP Pro would handle multiple connections just fine. As for security, no, I don't think I will buy that one.

If you search around the internet you will find hacks to enable multiple connections, you have to hack a few registry keys and replace a file, it's a .dll, but I don't recall which one right at the moment.

As long as this isn't for a business / production (read you make money from it) setup then go for it. If it's one of the above scenarios then I would very highly suggest that you buy a copy of Windows server 2003 as this feature is supported in that OS.

edit:

here's a link that should help out nicely:

http://episteme.arstechnica.com/eve/...m=294000755631

The standard CALs that you have allow for client computers on the network to connect to your Windows Server 2003 system for file access or authentication.

Terminal Services, on the other hand, provide an entire operating system experience for a user and thus require different ... and more expensive ... access licenses.

From Microsoft's Pricing Page:

http://www.microsoft.com/windowsserv...g/pricing.mspx