Hello,
I guess my post back on 2/27 did not make it to everyone.... the switch
that Bill is
speaking of is:


mstsc /v:172.##.#.## /console 


Thank you,
Scott White
I.S. - Application Services Manager
Saratoga Hospital

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bill Palmer
Sent: Friday, March 02, 2007 6:06 PM
To: [email protected]
Cc: Jason Bettio
Subject: RE: [Talk] Remote Desktop with Windows connection

When you connect via Remote Desktop you are initiating a new instance of
a workstation.  When you close it that instance goes away.  If you use
mmc to set up remote desktop connections you can specify a console
connection via a checkbox.  There is also a switch for the remote
desktop client to specify a console connection but I don't remember it
at the moment.  You could try google to find it.

Happy computing!

-- 

Bill Palmer
Financial Coordinator, Information Sys
Mid-Columbia Medical Center
The Dalles, OR 97058
541-296-7417

>>> On 3/2/2007 at 2:09 pm, in message
<[EMAIL PROTECTED]>,
[EMAIL PROTECTED] wrote:
> Hi, I have contacted Boston support about this issue, but I was 
> interested in seeing if anyone else has had this issue and found a 
> work-around.
> 
> We connect to a PC, used solely for Boston work, via Remote Desktop.
We
> just completed programming our first windows connection script.
> 
> Everything runs fine, until we either minimize the Remote Desktop
window
> or disconnect.
> 
> When we do this, the windows connection loses its focus and won't 
> continue with the script until we reconnect or restore it from being 
> minimized.
> 
> Has anyone had a similar issue? If so, were you able to find a way 
> around it?
> 
>  
> 
> Jason T. Bettio - Hospital Apps
> 
> Implementation Specialist
> 
> 717.972.8123
> 
> [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>

> 
>  
> 
> 
> Note:  The information contained in this message may be privileged and

> confidential and protected from disclosure.  If the reader of this 
> message is not the intended recipient, or an employee or agent 
> responsible for delivering this message to the intended recipient, you

> are hereby notified that any dissemination, distribution or copying of

> this communication is strictly prohibited.
> If you have received this communication in error, please notify us 
> immediately by replying to the message and deleting it from your 
> computer.  Thank you.

Reply via email to