Re: RDC win2003 server

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Yes, uninstalling Terminal Services does have some risks.
And since you are 4 technicians using rdp, you could choose to keep
the server as it is, but then you must install a TS Licensing
Server and buy 4 TS CALs. Note: most likely, Per User TS CALs would
be most convenient in this situation, since technicians tend to
connect from many different workstations.

The biggest disadvantage of this setup is that the server is
internally tuned to be a multi-user Terminal Server. This can have
a negative impact on the performance of other applications (like
Exchange, SQL, and so on).
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
___ please respond in newsgroup, NOT by private email ___

"=?Utf-8?B?TGFycnk=?=" <Larry@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote on
11 jun 2005 in microsoft.public.win2000.termserv.clients:

> Server is running 2003, and i just want to use it for remote
> admin. We have to connect to the console remotely at the mo and
> as there are 4 technicians we sometimes end up disconnecting
> each other. I guessed we need to unistall terminal services,
> but as there is so much running on that server i am reluctant to
> touch it. I am worried that uninstalling it will affect other
> apps on the server.
>
> Thanks for the help
>
> "Vera Noest [MVP]" wrote:
>
>> This server is running Windows 2003, right?
>> Which level of functionality do you want?
>> If you only want Remote Desktop for Administration, then the
>> people who installed the system made the MFM (Most Frequent
>> Mistake :-) to install Terminal Services (which implies
>> Application Server mode). That was how it was done on Windows
>> 2000, but not on 2003. In stead, they should just have enabled
>> Remote Desktop for Administration, in Control Panel - System -
>> Remote, just like on XP. This allows for a maximum of 2 + 1
>> concurrent connections, by default only for Administrators, no
>> extra licensing requirements. The only thing you can do now to
>> go back to Remote Desktop fA is to completely uninstall
>> Terminal Services.
>>
>> If you need Terminal Services (i.e. multiple users accessing
>> the server to run their applications on it), then you need to
>> install a Terminal Services Licensing Server (either on the
>> same server or on another 2003 server), activate it, buy
>> licenses, and install them on the LS.
>>
>> _________________________________________________________
>> Vera Noest
>> MCSE, CCEA, Microsoft MVP - Terminal Server
>> http://hem.fyristorg.com/vera/IT
>> ___ please respond in newsgroup, NOT by private email ___
>>
>> "=?Utf-8?B?TGFycnk=?=" <Larry@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote
>> on 10 jun 2005 in microsoft.public.win2000.termserv.clients:
>>
>> > I am using RDC to manage the servers on our network. The
>> > guys that installed the system seem to have installed
>> > terminal services but no licensing server. Now after 120
>> > days i can only use RDC using the console, as its asking for
>> > the terminal services licensing server. Is there anyway we
>> > can carry on using RDC normally? I dont want to uninstall
>> > terminal services.
.

Relevant Pages

  • Re: Time zone redirection
    ... Administration and full-blown Terminal Services. ... MCSE, CCEA, Microsoft MVP - Terminal Server ... client connections:-O. ... Well - obviously that does not work in Remote Desktop Admin mode ...
    (microsoft.public.windows.terminal_services)
  • RE: Terminal Services
    ... I understand that you want to have staff log ... we cannot make SBS to work as terminal server. ... why you cannot find Terminal Services in Add/Remove Windows Components. ...
    (microsoft.public.windows.server.sbs)
  • Re: can someone help clear this up?
    ... Terminal Services Client Access Licenses are assigned to the client, ... The Terminal Services License Server ...
    (microsoft.public.win2000.termserv.clients)
  • Re: Storing Username/Password problem
    ... double click the RDP-Tcp connection and look at the Logon ... MCSE, CCEA, Microsoft MVP - Terminal Server ... logged on with the credentials specified in Terminal Services ... Do you want each user to have their own account on the server, ...
    (microsoft.public.windows.terminal_services)
  • Re: Storing Username/Password problem
    ... terminal server and then several client machines. ... have their own account on the server, or do you want all of your users to ... Terminal Services Developer ... someone from using your RDP file and being able to log into a Terminal ...
    (microsoft.public.windows.terminal_services)