The Windows installation package has been specifically built to make installation and configuration as automated as possible.

Once installed Zegami will be up and running and ready to create collections. While most common deployments will be satisfied with the default settings, more complicated scenarios may require additional configuration.


Before installing the following prerequisites are recomended:

Service Accounts

The Zegami server and it's related services need to run under a user account. On Windows the default account used on installation the LocalSystem account. This is a highly privileged user and is sutible for simple installations and testing.

For production deployments it is strongly recommended that in production that a dedicated service account be used with minimum permissions.

See the section on Updating the service accounts for more details.


Zegami Server will require write access to a directory which is used to store processed collections and their associated data. For best performance this location should be local to the server running Zegami. On installation a default location at C:\Zegami\collections is created, however this can be changed.


To begin installation run the supplied installer Zegami-[VERSION]-Windows-x86_64.exe (where [VERSION] is the latest version number) Zegami installation step 1

Click Next > and accept the Licence Agreement. Zegami installation step 2

The installation will then begin. Depending on the version of Windows and previously installed software a reboot may be required. Once restarted the installation will continue. Zegami installation step 3

Once installation is complete, click Finish to complete. Zegami installer step 4

Zegami is now installed and ready to use!

On Windows 8.1 and 10 you can access Zegmai at http://localhost.

On Windows Server Zegami uses Internet Information Services (IIS) and is avalaible at http://localhost:5159 (port 5159 has been selected so that it does not conflict with other web applications that may already be running. The port can be changed via IIS Manager).

Please see our Getting Started guide for an overview of the user interface and our Creating a collection guide to get started and create your first collection.

(OPTIONAL) Updating Service Accounts

When changing the service account used by Zegami's services the account will need READ and WRITE permissions on the following directories:

  • C:\Program Files\Zegami\Lib\site-packages\zegami
  • C:\Zegami

Depending on the data sources required for collections the Zegami service account will also require read permission to the data sources. For example if the CSV data source is used for a collection, the Zegami service account will need to have read access to the location of the CSV data file. In the case of an ODBC data source the service account will need read access to the database.

Once the account is ready, update the Log On User for the Zegami Scheduler Service, Zegami Log Service, Zegami Cluster Service and Zegami Web Service (Windows Desktop only)

  1. Open the Services SnapIn
  2. Right click the service and select Properties
  3. Select the Log On tab
  4. Select the This account radio button and set the username and password of the new service account.
  5. Accept the dialog granting the account "Log On as a service" permission if displayed.
  6. Close the properties dialog and restart the service.

For Windows Server deployments the IIS App Pool account will also need to be changed.

  1. Open IIS Manager
  2. In the tree view expand the Server node and select Application Pools.
  3. Right click the Zegami Application Pool and select Advanced Settings...
  4. Select the ... next to the Identity property
  5. Select the Custom account radio button and set the new service account credentials.
  6. Close the properties dialog and recycle the Application Pool


To contact Zegmai support please email with details of the issue.

The default logging location is located at C:\Zegami\Logs and contains log files for the database, services and web server. The services also log to the Windows Application Event Log. If problems occur these logs can be useful when contacting support.