Introduction

FireDaemon OEM (FDO) is a specialized version of FireDaemon specifically designed for use by systems integrators or value added resellers that wish to bundle FireDaemon with their own product or platform. FDO is designed to be included in third party-installers or used in conjunction with scripts.

License

The FDO License allows a corporation (including Military and Government) to redistribute FDO royalty free as part of a commercial product or platform. It is prohibited for FDO to be re-distributed or sold as a standalone product.

Pricing and Purchase

For more information on FDO pricing and purchasing methods please refer to the Pricing and Licensing section on the product information page.

Support

OEM customers are entitled to unlimited technical and integration support plus upgrades whilst in maintenance via email and phone.

Functionality

FDO is a superset of FireDaemon Pro. The fundamental differences are as follows:

• No Serial Number Name or Serial Number required for installation
• Additional command line arguments to automate the configuration of the product registry keys

MSXML Compatibility

FireDaemon requires MSXML (Microsoft XML Core Services). MSXML is distributed on every Microsoft Windows platform that has IE4 or later installed. FDO has been designed to be compatible with MSXML v2.0a or later (as is distributed with IE4.01SP1). IE6 distributes MSXML 3.0SP2. For an example of how to determine which version is installed see this Microsoft Support Article. Details of MSXML versions can be found here.

Installing FDO

If you already have a version of FireDaemon installed we recommend that you unzip into the directory "C:\Program Files\FireDaemon OEM". FDO should never be installed into C:\Program Files\FireDaemon in order to avoid conflicts with potential or current FireDaemon Pro installations.

Configuring FDO

In order to successfully setup FDO your installer will either need to create a series of registry keys or you can use the command line functionality to do this for you.

On x86 (32-bit systems) create this top level key:

HKLM

  \SOFTWARE

    \FireDaemon Technologies

        \FireDaemon OEM

On x64 (64-bit systems) create this top level key:

HKLM

  \SOFTWARE

    \Wow6432Node

        \FireDaemon Technologies

            \FireDaemon OEM

Irrespective of platform create the following registry keys under the top level key:

Irrespective of platform, create the following top level key:

HKLM

  \SYSTEM

    \CurrentControlSet

      \Services

        \EventLog

          \Application

            \FireDaemon OEM

Then create the following keys underneath:

Alternately, this setup can be scripted as follows (the value of FIREDAEMON_HOME is the path used to populate the registry values above). You can use the reg.exe command if you want to script the creation of the registry keys yourself.

set FIREDAEMON_HOME=C:\Program Files\FireDaemon OEM

cd %FIREDAEMON_HOME%

.\firedaemon --configure "%FIREDAEMON_HOME%"

Removal of the registry keys is as simple as:

firedaemon --deconfigure

You can then proceed with generating a service XML configuration file or installing a prebuilt one. For example:

firedaemon --install file.xml

Other Notes

When cleaning up your installation ensure that you stop all FireDaemon services in advance, then uninstall them prior to deconfiguring the registry. For example:

net stop myservice1

net stop myservice2

firedaemon --uninstall myservice1

firedaemon --uninstall myservice2

firedaemon --deconfigure

The complete list of options can be found by: firedaemon --help

As previously mentioned, multiple instances of FireDaemon can be installed on the one machine (eg. OEM + Pro). Ensure that your working directory when you install a service is the directory where the FireDaemon redistributables are located. If your working directory differs ensure that you include the path to the redistributables in the global PATH environment variable.

What To Redistribute?

The following files should be minimally included in your installer or deployed on your platform. They must all reside in the same directory:

*Two versions of FireDaemon.exe and FireDaemonUI.exe are supplied. One is specifically for Windows Vista, Server 2008 and Windows 7 the other is for all versions of Windows XP and 2003. The difference between the two is in the application manifest. The Vista, Server 2008 and 7 versions have a specialised manifest that allows the executable to elevate correctly.

FDO is technically classified as a "native or unmanaged Visual C++ .NET application" and requires the Microsoft  Visual C++ 2005 SP1 Runtime. The redistributable package is included in the ZIP file or can be downloaded directly from Microsoft.