When running OMNIA as a service, the server application will not be available. 

To use the server application when OMNIA is running as a service, you will need to stop the service and then open the server application.

There is a batch file in the OMNIA folder that will configure this feature. This batch file needs to be run from the command prompt as an administrator.

NOTE:  OMNIA developers found a bug in the installation files for OMNIA to run as a service. You will need to replace the installation files.  The installation files are attached to this document.

The OMNIA installation for version 4.x has a problem with the batch files that allow you to setup OMNIA to run as a service.

Please download these attached files and replace the batch files that are in the OMNIA installation folder.

Remember that you must shut down OMNIA, then run the correct batch file for your OS from an elevated command prompt when installing the new service.

Please refer to KB:  OMNIA Run as a Service fix for v4.x

Configuration:

1. Close the OMNIA server application by right-clicking the OMNIA icon in the system tray > Exit
2. Run CMD as admin (C:\windows\system32>Right-click CMD>Run as administrator)
3. Navigate to the OMNIA  directory (See following screen shot for an example on what to type)

4. Execute install.omnia.service.bat and press enter. You will see a list of steps executing.
5. Close CMD
6. Go to services and set the Portal service to auto start

To uninstall the service, follow the same steps, but instead execute the uninstall.portal.service.bat file

WARNING

The only time when portal can run as a service is when the hardware has completely been commissioned, because the server application will be unavailable. If the Server App needs to be accessed, stop the service before

starting the server app. Running the service along with the server app can break your database bat (1022 Bytes) bat (1014 Bytes)