I've installed Sesame 1.1.4 (3 user license) on a box which has been upgraded to Windows 2000 Server.

I looked long and hard at whether to run Sesame server as a service or not and because I'd like to be able to check number of users logged in and other administrative Sesame tasks I opted to not have it as a service (at this stage).

This does have a huge disadvantage that should the system restart for any reason I have to log in to start Sesame server again. I use a shortcut in Startup to accomplish this.

It's up and running fine but whenever I RDP in (Remote Desktop) I get another instance of Sesame server trying to start then dying. However the original instance of Sesame server (when I go to the box in question and physically check) is still up and running fine, users can log in normally, all is otherwise well.

Whats the best means of preventing the 2nd attempt at starting Sesame server when using Windows Remote Desktop ? I only need the one userid 'Administrator' on the W2K Server. Everybody else has their own workstation and they are not permitted, or need, to access the W2K server with a Windows login of their own.

TIA.

Thanks for those links Mark, especially the first, which has a huge selection of registry keys to look at. Some look promising.

I have a reasonable familiarity with INSTSRV and SRVANY and contemplated using those to have Sesame server start which may allow Administration access to the server even with Sesame defined and started as a process (under Windows control as opposed to Sesame being told directly with '-daemon' it is to start as a service). I will continue to look for a definite solution that already works, to prevent the Startup folder being processed each time a new RDP session is initiated. Sesame running as a service would alleviate this problem but restricts the ability to fault-diagnose Sesame