I should clarify a few items. 1) The GUI on the client workstation needs to be available only to that workstation.
2) Once I have launched the application that uses the GUI I could disconnect as long as the application keeps running. There is nothing I want or need to see on the desktop. 3) This process needs to be repeatable. If the application ends and closes I need to be able to reset the workstation state to begin the process over with a clean start. 4) The application is a purchased product. I know it can be launched from the command line when you are logged on at a workstation. I need to do this from a remote machine and with multiple instances. Thanks -----Original Message----- From: Tim Wood [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 14, 2004 6:00 PM To: Neild,Bruce Cc: [EMAIL PROTECTED] Subject: Re: Multiple Workstations At 06:53 AM 01/14/04, you wrote: >Hello Everyone: >I have been researching a method to run a GUI application on multiple >workstations in the same network. The application can be launched from >the command line directly or via a batch file on a single workstation. >It needs the desktop to interact with other GUI components. >I would like to use a scheduling program on a master workstation or >server (W2K or XP) to launch this application on other multiple >workstations not in use by any other user. If you write your application in X (probably Unix/Linux hosted, unless there's an X library for Windows), it'll be easy: have your "slave" workstations run the application instances, with their $DISPLAYs pointed at the master server's Xvnc instance. Then connect to that Xvnc instance with vncviewer from anywhere and see all the app. instances. I think there's an obstacle to aggregating all the displays if the application is Win32, even with VNC server or Term. Server on Windows slave boxes, because there's no facility to aggregate all those virtual desktops from the slave machines onto one display (physical or virtual). (A VVNC might do it. :) However if you don't mind having one vncviewer process for each slave desktop, then yes, a VNC desktop running as a service (for automatic startup) on each slave box makes sense. YMMV, FWIW, HTH, etc. TW ============================================================================== This communication, together with any attachments hereto or links contained herein, is intended for the use of the intended recipient(s) only and may contain information that is confidential or legally protected. If you are not the intended recipient, you are hereby notified that any review, disclosure, copying, dissemination, distribution or use of this communication is STRICTLY PROHIBITED. If you have received this communication in error, please notify the sender immediately by return e-mail message and delete all copies of the original communication, along with any attachments hereto or links herein, from your system. ============================================================================== The Travelers E-mail System <tdmmsws1> made this annotation on 01/15/2004 06:49:07 AM. _______________________________________________ VNC-List mailing list [EMAIL PROTECTED] To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
