Install on Windows Server

Obtain the latest Maverics MSI package by contacting [email protected] and transfer the file to the target server.

As an Administrator, double-click the MSI file (or right-click and choose “Install”). The maverics.exe binary will be installed in the C:\Program Files\Strata Identity\Maverics directory. The Maverics service will start automatically with a delayed auto start. This means the Maverics service will not start until all the other auto-start services have started. Note that the Startup Type value of the Maverics service will be reset back to Automatic (Delayed Start) on the next reinstall or upgrade if it has been manually changed.

Server Requirements

Before you start, please note that you can run your Orchestrator instance on the server of your choice, whether on-premises or in a public cloud infrastructure provider such as Azure, AWS, or GCP.

  • Operating System:
    • Windows: Windows Server 2016, 2019, or 2022
  • Disk: 10GB (minimum)
  • memory: 8GB (minimum)
  • typical ports required: 22 (SSH/SCP), 3389 (Windows Remote Desktop), 443, 80
  • root or Administrator access (for installation and configuration)
  • Network egress from the Orchestrator host to your chosen cloud identity system

Configuring and Starting

Put your Maverics license file in the install directory.

Local Configuration File

Create a maverics.yaml file in the install directory and add your desired Orchestrator configuration.

Remote Configuration File

See the Remote Configuration & Auto-Reload section on how to configure the Orchestrator for remote shared storage.

Setting Environment Variables on Windows

The environment variables required for remote shared storage contain credentials. Use the following method to limit the visibility of these variables to mavericsSvc only so they will not be visible to other services or applications on the system.

Open the Registry Editor and navigate to HKLM\System\CurrentControlSet\Services\mavericsSvc. Create a multi-string value (REG_MULTI_SZ) called Environment if it does not already exist.

Add the remote configuration to the bottom of the entry if there are existing values there.

Set one of the following environment variables as described in the Remote Configuration section.

  • MAVERICS_AZURE_CONFIG
  • MAVERICS_AWS_CONFIG
  • MAVERICS_GCP_CONFIG
  • MAVERICS_GITHUB_CONFIG
  • MAVERICS_GITLAB_CONFIG
ℹ️
The orchestrator MSI installer adds a MAVERICS_CONFIG System environment variable by default. Delete this environment variable (System Properties > Advanced > Environment Variables… > System variables) to avoid configuration conflicts.

Auto-Reload

See the Auto-Reload section for configuring the Orchestrator to poll for changes to configuration.

Starting the Service

The Maverics service does not start automatically after orchstrator installation or upgrade. To start it, from the Computer Management console or the Windows Search field, launch Services (services.msc). Find the Maverics service in the list, right-click and select “Start.”

The “Startup type” for the Maverics service is set to “Auto”, which means the service will be started each time Windows starts.

Viewing logs

To view Orchestrator logs, go to the Start menu and search for Event Viewer. In Event Viewer, go to Windows Logs > Applications. Orchestrator events are listed in items displaying Maverics as the source. These logs may be helpful in troubleshooting any issues.

Update

Obtain the latest Maverics MSI package and transfer the file to the target server.

As Administrator, double-click the MSI file (or right-click and choose “Install”). The maverics.exe binary will be installed in the C:\Program Files\Strata Identity\Maverics install directory, replacing the previous version.

The Maverics service must be restarted manually or with a reboot.

Uninstall

In Windows Settings or the Search field, find and select “Add or Remove Programs.

Under Apps & features, search for “Maverics.”

Click Maverics and choose “Uninstall.” The installer will not automatically delete the install directory if the maverics.lic and maverics.yaml file are there. This can be done manually by deleting the empty directories.