Blog

Thursday, May 15, 2014

Starting Interactive FireDaemon Services In Session At Login Using Login Scripts

Windows Vista or later implements Session 0 isolation. What this means is that services with a GUI component that would normally interact with the Desktop are not visible if you RDP into your server or login via the console. You will have to switch to Session 0 via the Interactive Services Detection Service popup. You can run Interactive FireDaemon Services on your RDP session though. There are some caveats:

  1. The FireDaemon service must be configured to run as the LocalSystem account. When the service runs In Session it will run under the logged in users credentials
  2. If you log off the service will be killed. FireDaemon will restart the service for you but back on Session 0.

You can write a Windows logon script to run your services interactively. To do this:

  1. Create all the necessary FireDaemon services using the FireDaemon GUI
  2. Decide whether you want these services to be Manual start (ie. let the login script start them) or Automatic start (ie. they are started when Windows starts)
  3. Write the logon script batch file and place it somewhere logical on your C: drive
  4. Configure the logon script to run at logon via the Local Group Policy Editor.

Here's an example logon script - it uses the "call" directive to avoid UAC and elevate appropriately. Remember the user you login as in this instance must have the necessary privileges (eg. be a member of the Administrators group) in order to run FireDaemon effectively. Use this script if your services are manual start (ie. your services are started In Session and killed and stopped when you logoff).

call "C:\Program Files\FireDaemon\FireDaemon.exe" --start Mercury --in-session > Log.txt
call "C:\Program Files\FireDaemon\FireDaemon.exe" --start Runtime --in-session >> Log.txt
call "C:\Program Files\FireDaemon\FireDaemon.exe" --start Taskmgr --in-session >> Log.txt
call "C:\Program Files\FireDaemon\FireDaemon.exe" --start LST_Server --in-session >> Log.txt

Use this script if your services are set to automatic (ie. your services are restarted In Session and killed and restarted on Session if you logoff):

call "C:\Program Files\FireDaemon\FireDaemon.exe" --restart Mercury --in-session > Log.txt
call "C:\Program Files\FireDaemon\FireDaemon.exe" --restart Runtime --in-session >> Log.txt
call "C:\Program Files\FireDaemon\FireDaemon.exe" --restart Taskmgr --in-session >> Log.txt
call "C:\Program Files\FireDaemon\FireDaemon.exe" --restart LST_Server --in-session >> Log.txt

For more information on the FireDaemon Command Line Interface and various command syntax please see this section in the manual.

Comments
Post has no comments.



Captcha Image

Recent Posts



Tags


Archive

    Sign up for Product Updates and Discounts
    Captcha Image
    ×