Run Omniscope Classic Server (2.9) and Omniscope Evo on the same machine (Windows)

Modified on Tue, 28 Apr 2020 at 03:38 PM

This article describes how to run Omniscope Classic Server (2.9) and Omniscope Evo installation on the same machine.

NOTE: This document is written from the perspective of a user on the Windows operating system.  This document assumes you have administrative privileges to create folders/files, and have knowledge of networking and basic understanding of editing files using notepad. If unsure, it is always best to ask your System administrator in your organisation to help you.

Step 1: Installation

In order to ensure you can run both 2.9 and Omniscope Evo concurrently you need to ensure one installation is installed for "Current user", and one for "All users". This would allow two installation to have independent installation location and not to interfere with each other.

  1. Ensure you have Omniscope 2.9 already installed, and make a note of the location where it is currently installed. You can find this information by starting Omniscope Classic and then going to Help > About. This is important as you would need this information to make sure you install Evo in a different folder to avoid overriding your existing 2.9 installation.

  2. Download Omniscope Evo. Ensure there is no Omniscope running (windows service, or the classic Desktop), and then double-click installer. On the main page of the installer make sure you tick "Customise". This is necessary as it would allow us to change the installation location. Click Next and choose the different location to that of 2.9 (as mentioned above). For example, if you have 2.9 installed for current user, choose "All users" or vice versa.

  3. Click next to finish installing Omniscope.

Step 2: Omniscope Evo configuration

This step involves changing some configuration parameters to the installation to ensure it doesn't use the default location which is C:\Users\<username>\omniscope-server\ 

  1. Go to the Omniscope Evo installation folder (e.g. C:\Users\username\AppData\Local\Visokio Omniscope App or C:\Program Files (x86)\Visokio Omniscope ) and edit the in notepad.

  2. Enable ADVANCED_JVM_ARGS by removing the "#" from start of the "ADVANCED_JVM_ARGS", while making sure there are no leading spaces between start of the line.

  3. Add omniscopeFolder property stating where the Omniscope folder is. For example, if you want have Omniscope running and using "C:\myOmniscopeEvo", then your advanced JVM args should look like:


  4. Save the file.

Step 3: First time setup

  1. Start Omniscope Classic Server 2.9, if not already running. Wait the UI to show up and ensure all your services are running.

  2. Now start Evo - you should see Omniscope asking you to confirm your instance port, choose or accept the port given. Omniscope will automatically choose a new port if Omniscope Classic is already using it.
  3. Once you accept, Omniscope will reboot, and then you should see a blank "File list" page. Click on "Admin" link on the bottom of the page to setup your admin credentials.

  4. Once you credentials are set, to setup the networking ports e.g. HTTP and HTTPS, go to "Networking" section within the Admin web app.

    NOTE: If you wish to use HTTPS make sure you also update the keystore.jks file appropriately and https port.

  5. You can further change the default location of Workflow App Temp, and MonetDB Data Engine location from Disk manager section in Admin Web App.

Once you are happy with all your changes, click "Save changes" and restart Omniscope.

Step 4: Finish

You are now ready to create folders/files, and all logs and server configuration will be stored in the omniscopeFolder location you specified in Step 2.


If you have any problems trying to run Omniscope, check server logs which accessible from the "Admin Web App".

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select atleast one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article