Preparing to Install
Before you install Commander, you must do the following tasks.
By installing this software, you're accepting the License Agreement. If you don't accept the terms of the License Agreement, please return this product.
Download the Commander software
Make sure you have administrative access to the machine
Installing Commander requires administrative access.
Make sure the machine you're installing on has the recommended configuration
See System Requirements.
Install Microsoft System Center VMM Administrator Console on the Commander host. Note that SCVMM requires that the host be joined to the domain.
Install Microsoft .NET Framework version 4.7 release 460805 or higher.
To work with Microsoft SCVMM cloud accounts in Commander, all SCVMM hosts must have Microsoft .NET Framework version 4.7 or higher installed before you install Commander or before you upgrade a previous release of Commander.
Ensure that event-based refresher mode is enabled.
Commander takes advantage of SCVMM's event-based refresher mode so that it can obtain IP address changes from SCVMM VMs. If refresher mode isn't enabled on your SCVMM hosts, you need to run some Windows PowerShell commands on the hosts to manually set the refresher mode. See How to enable the event-based refresher mode for Virtual Machine Manager hosts on the Microsoft Support site.
The Commander Windows service also needs an account under whose context it will run. Commander will also use this account to connect to remote storage.
If you're using the default (PostgreSQL) database, this account must be a local, non-administrator user. If you're using Microsoft SQL, the account may be any local account or a Domain account.
In either case, disable User Must Change Password At Next Login when you configure the account. The account must also have the Log on as a service right added.
If you're using a local account, configure the account with Password Never Expires and User Cannot Change Password.
On Windows, the user must be granted Access this computer from network, otherwise the account isn't accepted and you see a generic username/password error.
Ensure that the Secondary Logon service startup type is set to Manual
When you're installing Commander, if the Secondary Logon service is disabled, the Commander service won't start.
This error message is displayed by the installer after you enter the service account credentials:
Invalid Configuration: The supplied account is not allowed to log on locally, check the security policy.
In addition, the following error is written to the installer.log file:
Error: Couldn't create Process: (1058) The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.
When the Secondary Logon service startup type is set to Manual, the Commander service starts automatically.
Prepare to use Microsoft SQL Server for production use
If you are using Microsoft SQL Server:
A default Postgres database is included with Commander, but isnot recommended for production use. See also Database considerations.
Create an administrative account in each cloud account
For each cloud account, Commander requires an administrative account that has full administrative access on the entire cloud account. Administrator privileges are required for a number of functions that Commander performs. These functions include retrieving VM and infrastructure information, managing VM identity, powering VMs on and off, and other policy actions.
Create a uniquely identifiable administrative account on each cloud account (for example, "Embot"). Creating a unique account name allows you to easily track Commander commands sent to the cloud account by Commander or by Commander users.
If this installation of Commander will be used in a production environment, don't use the default self-signed SSL certificate. Instead, you must generate an SSL certificate and have it certified by a certificate authority. See the Snow Globe article Generating and Installing an SSL Certificate to learn how.