Valuable $.0.02. I was thinking purely from a server standpoint.

 


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Molkentin, Steve
Sent: Tuesday, January 31, 2006 4:22 PM
To: [email protected]
Subject: RE: [ActiveDir] PcAnywhere vs. Terminal servcies

 

Just to clarify though, if you connect to the console using RDP, it locks out the user at the other end, so they can't do anything or even watch... you can then disconnect, but it leaves the machine locked.

 

Just to add to the mix...

 

We use RDP for our servers and DameWare for our clients for support. My $0.02 inc GST.

 

themolk.

 


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Tom Kern
Sent: Wednesday, 1 February 2006 6:54 AM
To: [email protected]
Subject: Re: [ActiveDir] PcAnywhere vs. Terminal servcies

Thats what I thought.

Thanks everyone!

 

On 1/31/06, Condra, Jerry W Mr HP <[EMAIL PROTECTED]> wrote:

We use term serve everyday and disconnect [not logoff] and everything running continues. No switches needed. It's run from this shortcut:

 

%SystemRoot%\System32\mstsc.exe

 

Jerry

 


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Richard Waldrop
Sent: Tuesday, January 31, 2006 1:24 PM
To: [email protected]
Subject: Re: [ActiveDir] PcAnywhere vs. Terminal servcies

 

I may be incorrect but mstsc.exe /console and the session keeps running

In my company I have many people on the Network infrastructure team  that insist on using PcAnywhere over Term services because they feel that when they close out the PcAnywhere window, any application that they start in their user context continues to run.
>
>  
> In Term services this is not the case.
>  
> Is there anyway to make this happen in Term Services Remote Admin mode.
>  
> Most of these servers are Win2k.
>  
> I'd really prefer that they run Term services instead of PcAnywhere and I'd like to figure out a way to give them the same "experience".
>  
>  
> Thank you
>  
>  
>

 

Reply via email to