Re: comparison between Remote Desktop Connection and pcAnywhere

From: Patrick Rouse [MVP] (anonymous_at_discussions.microsoft.com)
Date: 03/25/04

  • Next message: Rajneesh Mahajan \(MSFT\): "Re: Troubles with Word and Citrix" 
    Date: Wed, 24 Mar 2004 18:21:10 -0800

    On top of that Terminal Server (or Remote Desktop for Administration) support multiple concurrent sessions on the same machine, whereas PCA only supports one-per-machine.

    In my opinion PCA should only be used to remote control Windows machines not equipped with Terminal Services/Remote Desktop, or you have a specific need to PCA. I dumped products like this as soon as 2000 Server was released.

    Remote Desktop for Administration How tos here:
    http://www.workthin.com/tshta.htm#ConfigureAndManageRemoteDesktopForAdministration

    Patrick Rouse
    Microsoft MVP - Terminal Server
    http://www.workthin.com
         
         ----- Vera Noest [MVP] wrote: -----
         
         Windows 2003 supports a connection to the console session (session
         0), through the use of mstsc /console.
         For most purposes, this is sufficient to remotely manage your server.
         Biggest advantage: it's build-in and doesn't cost you anything.
         pcAnywhere has lots of nice features, but it costs.
         
          --
         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?ZGFtaQ==?=" <anonymous@discussions.microsoft.com> wrote
         in news:AA7F3266-8EC9-4BB9-96D0-B1F06F7BEACC@microsoft.com:
         
    > Does anyone please tell me the pros and the cons for both
    > products?
    >> I always use pcanywhere to control win 2000 servers.
    > Now I will upgrade them to 2003.... should I continue using
    > pcanywhere or should I move to RDC?
    >> Thanks!
    >> Dami
         

  • Next message: Rajneesh Mahajan \(MSFT\): "Re: Troubles with Word and Citrix"

    Relevant Pages

    • Re: Cant see local network printer from Remote Desktop session over VPN
      ... Within the remote session, I can ping the network address of the local printer, and can even connect to its administrative "web" page, but I can't print to it. ... If I understand you correctly, you're using remote desktop to connect to a terminal server at the other end, but you're trying to print directly from the terminal server to the network printer at your end. ...
      (microsoft.public.win2000.networking)
    • Re: How hard is it to config Win2003 to serve a single app and offer users little else?
      ... session is initiated. ... from their RD Connection and then start up with the desktop and all? ... > You can configure your Terminal Server to start a specific ... >> dialed in to ts boxes using remote desktop, ...
      (microsoft.public.windows.terminal_services)
    • Re: Terminal Services RDP-TCP Listener not found
      ... Aadded the users to Remote Desktop Users group still i get the error message ... When add the same user to Administrator group, terminal server session is ...
      (microsoft.public.windows.terminal_services)
    • Re: Terminal Services and Interactive Services
      ... If your Terminal server runs 2003, you can connect to the console ... session with "mstsc /console". ... > see the dialog on remote desktop. ...
      (microsoft.public.win2000.termserv.clients)
    • Re: Remote Access w/PCAnywhere
      ... Use RWW/RDP to connect to a development machine, then run PCA or Netmeeting ... > It only works if I first establish a VPN session. ... > I know everyone is probably thinking why not use remote desktop, ...
      (microsoft.public.windows.server.sbs)