The M$ KB article i meant was:
KB834651 - Terminal Services licensing mode changes from Per User or from
Per Device to an invalid value after you add or remove a Windows component
http://support.microsoft.com/kb/834651
Regards,
_____________________________
Piet van Dongen
MCSA, MCSE, MCTS, MCDBA, MCP
CCA, CCEA, CCSP
RPFCP, RWCP, RCP
_____________________________
"Piet van Dongen" <piet_van_dongen.RemoveThis@hotmail.com> schreef in bericht
news:0C3A9693-D117-42E6-BB5C-1064B5B9480C@microsoft.com...
> Hi Somchai,
>
> The remote deskop application that's part of windows xp and higher.
> If you only want to open a published desktop (terminal services 2k/2k3)
> you don't need an 3th party tool to connect.
>
> With the standard RDP client in Windows you can:
>
> - access local client drives on the remote desktop (e.g. terminal
> server session)
> - connect your local client printer(s) => remember to install the
> vendor device drivers or configure the fallback printer driver in GPO.
> - copy and paste between the local client and the terminal server
> session.
> - save the connection as *.RDP file for further distribution to
> users...
>
> Remember to open or redirect TCP port 3389 (default) to your terminal
> server(s) in ISA or on your router.
>
> Regards,
>
> Piet van Dongen
> Thinclient Consultancy. B.V.
>
> "Somchai" <Somchai.RemoveThis@discussions.microsoft.com> schreef in bericht
> news:3801D3CC-EF59-4CF9-980E-E4666B33DEFA@microsoft.com...
>> I am setting up Terminal Server for one of my client, however, I haven't
>> done
>> that before. Connectivity is already there and we are coming in by ISA
>> to
>> our servers. The question is what is the best application for the client
>> to
>> access Terminal server? Do I simply use remote Desktop or should I use
>> another Windows Application or even a thirth party application?
>>
>> Thank you for your input.
>