Ran into this video today on Running TeamSpeak 3 Server under FireDaemon Pro.
If you need a service to run once per day at a specific time and then exit, you can do so with the following
- Create your service as normal
- Set Settings -> Upon Program Exit -> Disabled (or Report the Termination)
- Set Scheduling -> Schedule a Restart -> At Specific Time
This will cause FireDaemon to run your app initially to completion. When the app quits FireDaemon doesn't restart it. At the "Specific Time" the app is run again and the cycle continues.
Windows 8 and Windows Server 2012 are here with the new Metro interface. FireDaemon Pro and FireDaemon Fusion both install and run successfully on both versions of Windows. FireDaemon services can be successfully installed and run. Start In Session and Restart In Session also works. There is one issue that we have encountered with both Windows 8 and Server 2012 and that is the Interactive Services Detection service fails to run and bombs out with the error "The Interactive Services Detection service terminated with the following error: Incorrect Function". To fix this get into the Registry Editor and look for HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Windows and change NoInteractiveServices from 1 to 0. Once you make that change you will see the Interactive Services Detection dialog and you can switch desktop over to Session 0.
This was a question that was recently asked in a support ticket and it is a very good one. For those of us who are concerned about security, this is very important. Rest assured though, the service password is not stored in the filesystem. When the service is created is it passed to the Service Control Manager where it is hashed and stored in the SAM.
You can run an executable as a service under FireDaemon even if that executable resides on a network drive. In order to run an executable off of a network drive the following must occur or be true:
1. The executable must be placed in a directory that is shared out
- 2. The executable can be normally referenced via mapped drive (eg. L:\pathfile.exe) or via UNC path (eg. \\serversharepathfile.exe).
- 3. Mapped drives or UNC paths can only be used if the service is run as a nominated local or domain user (see next point).
- 4. If you intend to run the service as a nominated local or domain user then that user has must have permission to access the network resource (ie. share) in question. Further, if you want your application to Interact With The Desktop then you need to ensure that the local or domain user is in the Administrator's group.
- 5. If you want to use a mapped drive then you are going to have to setup a Pre-Service Program to complete the mapping.
- 6. The application working directory can be either a mapped drive or UNC path - however, if a UNC path is used, a trailing slash () must be supplied (eg. \\serversharepath).
If you've ever encountered an error like "Installaware Wizard: Setup database not found" while trying to install FireDaemon or other applications, the reason is because your MSI database might be corrupt. The MSI database stores information about all installed MSI applications. To fix it, download the MSI Cleanup Utility from Microsoft from http://support.microsoft.com/kb/290301 Ensure that you remove any remnants of the FireDaemon installer - then attempt to install again. Also look at deleting the MSI uninstaller. You will find it at a location similar to the following:
If your Pre-Service or Post-Service executable is dying before it has a chance to run, the problem is that the execution time is too low. By default, it is set to 3000ms (3 Seconds). Try setting it to something higher (you might have to keep increasing until you find the proper time).
If you need to access the Services Control Panel, Event Viewer or Task Manager there's a way to do it a lot faster. Rather than going through the run box, start menu, or right clicking my computer you can do it entirely through the FireDaemon window! Simply click the "File" menu and select your desired tool there.
If your server or application fails to restart when a error popup displays then the following fix will solve the problem.
Go to http://msdn.microsoft.com/en-us/windowsembedded/standard/aa731206.aspx and follow the instructions there for the registry modification of
After you change the registry key, you will need to restart the computer for the changes to take effect.
Note: Be extremely careful with the registry as incorrect changes can break Windows.
For low-level filtering out visible notification of various errors use registry entry HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Windows\ErrorMode. ErrorMode value descriptions: 0 - All messages are visible (default value). 1 - Only system messages are invisible. An example of this type of message is: "Virtual Memory Minimum Too Low." 2 - All messages are invisible. An example of this type of message is: "Unable to Locate Component" shown when application can't load DLL statically linked to it.
You should use the last setting (2) for the registry tweak. The first registry key will fix the error (HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Windows\ErrorMode). The registry file contains the following:
Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Windows] "ErrorMode"=dword:00000002
Services in FireDaemon Pro can be restarted in session. This means that you can see your service on your desktop without switching to session 0. This can be useful if you have an application that you want to see running for test purposes.
- Manually Patching VMware ESXi 5.X with vCLI esxcli
- When Your Content Delivery Network Is Bad For Your Website's Health
- One-shot Windows System Event Notification at its finest!
- Fixing InstallShield's Visual C++ 2015 Runtime Preqrequisite
- Avoiding Session 0 Auto Logout with FireDaemon Pro and AutoIT
- WordPress Hardening Guide
- Starting Interactive FireDaemon Services In Session via Automatic Logon and Scheduled Tasks
- Starting Interactive FireDaemon Services In Session At Login Using Login Scripts
- Installing Perl and the VMXNET3 driver retrospectively on a minimalist vSphere CentOS 6 virtual machine
- Importing and Exporting FireDaemon Service Definitions
- Active Directory (2)
- Any Password (1)
- Arista (1)
- Bitvise Tunnelier (1)
- Bitvise WinSSH (1)
- BlueArc (3)
- BlueScreenView (1)
- C++ (2)
- CDN (1)
- centos (4)
- Crash (1)
- Desktop Restore (1)
- esxcli (1)
- esxi (2)
- Filer (1)
- Firedaemon (30)
- Fortigate (1)
- Fortinet (1)
- freeFTPd (1)
- HDS (4)
- HLSW (1)
- HNAS (4)
- InstallShield (1)
- Interactive Services (4)
- iSCSI (1)
- linux (3)
- MooO SystemMonitor (1)
- netapp (1)
- NetLimiter (1)
- nfs (1)
- PeerBlock (1)
- Process Explorer (1)
- QTTabBar (1)
- Service Export (1)
- Service Import (1)
- Session 0 (5)
- Session 0 Viewer (1)
- show chickens (1)
- Software (17)
- software development (1)
- SRCDS (2)
- Startup Delayer (1)
- system administration (52)
- Teamspeak (1)
- TeraCopy (1)
- TreeSize (1)
- Visual Studio (1)
- vmware (3)
- vsphere (3)
- Windows (1)
- Windows Login (2)
- WordPress (1)
- XML (1)