Running OmniRush Server as an NT Service

Also see: Running OmniRush Server as Application

NT Services are complex, and require Win2000 expertise to manage. NT Services, especially in a networked environment, are complex to manage. Always configure and run OmniRush in Application Mode before switching to Service mode. In the event of ANY problems with OmniRush, the first step is to switch back to Application Mode. Do not attempt use of OmniRush as an NT Service unless you have appropriate training and/or certification.  Z-Firm does not offer technical support for Windows networking/operating system.  

In some cases, service mode operation is simply not possible. Network configuration issues, CRM configuration issues, and other aspects can simply prevent OmniRush from ever running as a service.

Z-Firm technical support for NT Service operation is level II or III support and is on a best effort basis. Due to the networking and environmental complexity of NT Service operation, support for this mode is higher level, and not included in installation agreements, service/maintenance agreements, or initial purchase support. Support for converting to service mode is on a time basis, and there are no guarantees of success.

OmniRush Server installs to run in application mode.  The reason for this default is that running in NT Service mode is complex.  

• NT Services cannot access drive letters (they must use UNC)

• Accessing network shares, printers, and other network resources requires planning and often some network administration.  

Z-Firm research indicates that %25-40 of OmniRush installations require network and environment tuning in order to run as a service.

To get OmniRush up and running quickly, OmniRush installs itself to run in application mode.  Z-Firm requires that all installations initially run in application mode and test out successfully before switching to NT Service mode.  

Note: Always configure, run, and test OmniRush in Application mode before switching it to run as a service.

Steps to Switch to NT Service Operation:

1. Stop all OmniRush Modules

2. Stop and exit the OmniRush Launcher via the System Tray icon

3. Remove the OmniRush Launcher icon from the Start Up group or any other place that might auto-start the Launcher as an application.

4. Open OmniRush Administrator

5. From the computer leaf on the tree, select Launcher Settings:

6. Then, check the Run as NT service box:

7. Now go to the NT Service Control Manager and take two steps:

1. Set the OmniRush Launcher service to start automatically

2. Manually start the OmniRush Launcher service

You can now start modules.  OmniRush is now running in NT Service mode.

Be sure to delete the OmniRush Launcher from the Startup group.

Test the system for correct operation, particularly examine interaction with the CRM system and network printing.

It is crucial that the Application Mode Launcher is not run if the Launcher Service is running (and visa versa). Only a single launcher may run at a given time. If for any reason two launchers (service and application) are started concurrently, reboot the system.

If there are any problems, the universal first step is to switch back to application mode.  Continuing in NT Service mode may require planning and network research and administration.  Also review this help file carefully.  There are several articles on how to examine and correct your system for NT Service operation.