|  | ObjectBroker does not currently support starting a  GUI application
that writes to the desktop.  The reason for this is that it is not clear
whether the account under which the application is to be started 
should be allowed direct access to the desktop.
Image your working on your workstation and suddenly someone else
does an invocation causing some application to take control of YOUR
workstation screen.  While this is what you probably do want if your
the one making the invocation, but may not be if you not the one.
We are investigating how to provide this level of control to the system
administrator since we can easily forsee customers wanting to do
this, but wanting to control what does and does not write to the screen.
Your suggestions would be welcomed
Paul Patrick
 | 
|  |     
    In order to interact with the desktop, the server must be in the
    administrator group. From the release notes of the next OBB
    version.
    
     In addition to adding this code to the server program, on Windows NT
     the ObjectBroker agent service must be allowed to interact with the
     desktop.  To enable this interaction:
     1.  In the Control Panel, double-click on Services.
     2.  In the Services window, locate and double-click on ObjectBroker
         for Windows NT.
     3.  In the Service window, click on Allow Service to Interact with
         Desktop; click on OK.
     4.  In the Services window, while ObjectBroker is highlighted, clock
         on Stop and then click on Start, to restart the ObjectBroker agent
         service.
     5.  Verify that the user who is autostarting the server is in the
         Administrators group.
    
    
 |