We have a number of 4D Servers which we run under a dedicated Windows Account. 
We use the same Windows Account to run all Production Servers on all machines. 
If someone needs to monitor the server they can do that via RDC using that 
Windows Account. That avoids any session confusion. However, it doesn't allow 
multiple users to monitor the same session and, since we run 4D Server from the 
desktop, rather than as a Windows Service, it also exposes the risk of the user 
accidentally 'logging off' instead of 'disconnecting' which causes 4D Server to 
quit. For these reasons we use RealVNC to monitor all servers, which is simply 
a screen sharing app.

>The issue as I understand it is this; Windows Server allows you to have 
>multiple sessions for users concurrently logged in.
>This can be confusing when multiple people connect expecting to administer the 
>same desktop, but instead of seeing a
>shared desktop they get their own desktop in their own session, even though 
>the app they are looking to administer (4D)
>is running  in another user session. To correct this they must be aware of the 
>session they are currently connected to
>and aware of the session that is running the app they want to administer.

Tom Benedict
Optum
This e-mail, including attachments, may include confidential and/or
proprietary information, and may be used only by the person or entity
to which it is addressed. If the reader of this e-mail is not the intended
recipient or his or her authorized agent, the reader is hereby notified
that any dissemination, distribution or copying of this e-mail is
prohibited. If you have received this e-mail in error, please notify the
sender by replying to this message and delete this e-mail immediately.
**********************************************************************
4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
**********************************************************************

Reply via email to