This guide provides instructions for the initial provisioning and configuration of Gemini Enterprise.

System Initialization

  1. The appliance configuration is performed using the Gemini Enterprise: Manager (GEM) web console. Using a supported web browser, navigate to:
    https: (IP address from prior step>)
  2. A security warning or message may be displayed. This is expected and does not indicate a problem. Depending on your browser you may have to choose “proceed anyway” or “continue” for the page to load.
  3. Upon the first visit to Manager, the End User Software License Agreement is shown. After reading the terms, choose Accept to advance to the next screen.


Manager supports multiple languages. Setting a preferred language adjusts the entire user experience accordingly.

If the hostname and timezone settings were skipped in previous basic configurations, this step provides an opportunity to configure them.

License Activation

This step allows you to activate the appropriate license for your intended use. You can choose to activate the full Enterprise Edition which requires a pre-purchased license or the Free Edition, which requires no license. You may also opt for the third option of a 30-day trial of the Enterprise Edition which does not require a licence.

If you chose to activate a pre-purchased Enterprise license, the next step will walk through the application process. You may either choose to retrieve the license from an existing license server or apply a new license from a file.

Applying a license from a file involves a three step process, outlined in this screen. It involves generating a request, submitting the file to Gemini Support and finally uploading the received license file to the appliance.

Alternatively, if a license server is used to manage all available licenses, selecting the “Connect to a License Server” will allow specification of license server information - IP Address and token - in order to perform the validation.


If you have multiple appliances to be configured, select “Bulk Provisioning” to launch a wizard that allows configuration of multiple appliances at one time. The configuration includes all aspects of naming, network configuration, LDAP access and software installation.

To operate as a standalone appliance, select “Stand-Alone (single) provisioning”.

Bulk Provisioning

The Bulk Provisioning Wizard is a step-by-step workflow that allows configuration of multiple appliances in one simple process. Before proceeding further, all other appliances that are to be configured, will need to be powered up and network-accessible. No other configuration steps are needed on these other appliances.

Bulk Provisioning - Appliance Discovery

This steps discovers and confirms the entire set of appliances that are to be configured. The discovery process can be done in one of two ways:

If the IP addresses of all appliances are known, and available in a text file, it can be uploaded to launch the discovery process. The file will need to contain one IP address per line.

Alternatively, the appliances can be discovered on the network by performing an IP subnet scan, using a CIDR notation to specify the subnet. E.g. Please note that the scope of the subnet will determine the length of time taken for the scan to complete.

Bulk Provisioning - Network Settings

This step configures the mechanism used for assigning IP addresses of the appliances being configured.

The default option “Network settings - Static assigned” uses dynamic assignment using a DHCP Server.

Alternatively, choosing “Network settings - Static assigned” will utilize DHCP for the initial assignment only, but then use that IP as the static setting from that point onwards. This is useful when building a DHCP server for deployment temporarily, and the DHCP server is not needed after that step.

Bulk Provisioning - Hostname

This step provides multiple options for automatically assigning a hostname to each appliance being provisioned.

If DNS records have been assigned for each appliance, the “Use Reverse DNS Lookup” option uses the hostname discovered through the DNS server.

Alternatively, the “Specify Custom Pattern” option allows the specification of a custom string pattern composed of text and certain allowed tokens, to automatically compose a hostname. The following tokens are allowed:

$service_tag$ - is replaced with the service tag of the appliance, as indicated on the box or available within Gemini support.

$increment$ - is an automatically incrementing number

Bulk Provisioning - Change Admin Password

This step is used to specify the password for the “admin” account on each appliance being configured.

It is recommended that you use a strong password or if applicable, follow appropriate password security policy as required for your enterprise.

Please note all the appliances will be updated with the same admin password.

Bulk Provisioning - Connect to LDAP

If an LDAP account is to be required for access to each appliance, this step allows the specification of LDAP server authentication information. This will be used to authenticate users upon login to the appliance. Read LDAP Authentication in Settings chapter for more details.

Please note that LDAP authentication is optional, and by default the appliance resorts to local account-based authentication.

Bulk Provisioning - SSH Authentication

This step allows configuration of SSH access on each appliance being configured. It allows the specification of a password for SSH access, or the upload of an SSH key to complete the key exchange and bypass the password.

Please note this step is optional and can be skipped.

Bulk Provisioning - Summary

This summary screen lists all the appliances about to be provisioned along with configuration settings. It should be used as a final review and confirmation step before starting the automated configuration step.

it is also strongly recommended that the a CSV file be downloaded for future reference.

Clicking on Start initiates the automated provisioning process, which can take several minutes or longer depending on the number of appliances being provisioned.

The status of each appliance is updated in real-time. After all appliances have been provisioned, clicking on Finished completes the process.

Stand-Alone Provisioning - Join Cluster

To include this node into an existing Manager Cluster, select “Join an existing appliance cluster” and provide the IP Address and the Token String that were assigned to the Master Node.

To operate as a standalone appliance, or to configure a cluster at a later time, select “Operate as a standalone appliance”.

Stand-Alone Provisioning - Change Admin Password

Update the password for the account ‘admin’ in Manager here. It is recommended that you use a strong password or if applicable, follow appropriate password security policy as required for your enterprise.


Congratulations! The Completed screen lets you know that this appliance has been configured. Click “Get Started” to launch Manager. Return visits to this page will proceed directly to login. Configured settings may still be changed within the corresponding areas within Manager.

Initial Login

Upon completion of the setup process and clicking on Get Started in the previous section, you will be presented with the login screen. Log in to Manager with the username ‘admin’ and the newly changed password from the previous step.