ArcGIS Mission Server can be installed using the installation wizard or the command prompt. For instructions on using the installation wizard, see Install ArcGIS Mission Server with the installation wizard.
Tip:
The installation mode that you choose determines the default uninstallation mode. For example, if you install silently from the command line, the uninstallation defaults to a silent uninstallation from the command line.
Each machine with an installation of ArcGIS Mission Server requires an authorization file. The recommended method of registration is to use the software authorization wizard, which opens after installation, or you can visit My Esri to obtain an authorization file before installing the software.
At this release, ArcGIS Mission does not support a multiple-machine server site.
Prepare to install ArcGIS Mission Server
Before installing ArcGIS Mission Server, complete the following steps:
- Sign in to My Esri and obtain the following files:
- Your ArcGIS Mission Server software download
- Your authorization file
- Verify that your machine meets the system requirements.
- Modify the firewall of the ArcGIS Mission Server machine to allow communication on port 20443, which ArcGIS Mission Server uses to communicate.
Once you've completed these steps, proceed with the command line installation detailed below.
Note:
Command line parameters are case sensitive. If you have trouble getting your installation to work, confirm that the case matches each property as shown in the code examples below.
Configure the Windows account
The ArcGIS Mission Server account must be configured when the software is installed silently. For production systems, it is recommended that you designate a preexisting account that resides in your domain or Active Directory and follows your organization's security policy.
If command line parameters are not used to configure the ArcGIS Mission Server account during silent installation, the account is automatically set to the Local System account.
Use the command line parameters below to configure the Portal for ArcGIS account.
Passing account credentials directly
Caution:
If the ArcGIS Mission Server account is not defined during a silent (/qb) installation, or the credentials are not valid, the setup displays a warning message during installation. The message can be closed by clicking OK. Under these circumstances, the ArcGIS Mission Server account is set to the Local System account.
USER_NAME=<operating system account>
The account can be a domain account or a local account. If you're using a domain account, it must already exist. If you're using a local account, the account will be created if it does not already exist. If the account is not valid, a message appears during installation indicating that the account or password is invalid.
MSA=TRUE
This parameter should only be used with a Managed Service Account. A Managed Service Account must already exist on your domain. Do not use this parameter with a local account or a domain account with password. A Managed Service Account will not use the PASSWORD parameter.
PASSWORD=<account password>
This is the password for the account specified for the USER_NAME parameter. If the password is not valid, a message appears during installation indicating that the account or password is invalid.
Examples are below.
Caution:
Command line parameters are case sensitive. If you're having trouble getting your command line installation working, confirm that the case matches the properties as shown in the examples.
Using a domain account
<path to the ArcGIS Mission Server setup download>\setup.exe /qb USER_NAME=mydomain\mydomainaccount PASSWORD=my.password
Using a new or existing local account
<path to the ArcGIS Mission Server setup download>\setup.exe /qb USER_NAME=myaccount PASSWORD=my.password
Using a Managed Service Account
<path to the ArcGIS Mission Server setup download>\setup.exe /qb MSA=TRUE USER_NAME=mydomain\mymsa
Specify the installation location
By default, ArcGIS Mission Server is installed at C:\Program Files\ArcGIS\Mission\.
Optionally use the INSTALLDIR property to change the installation location for ArcGIS Mission Server from this default location.
Browse to the directory containing setup.exe
The following command demonstrates installation without specifying an account:
<setup directory>setup.exe /qb INSTALLDIR="C:\MissionServer\"
The following command demonstrates installation specifying a domain account:
<setup directory>setup.exe /qb USER_NAME=mydomain\mydomainaccount PASSWORD=my.password1
The following command demonstrates using a new or existing local account:
<setup directory>setup.exe /qb USER_NAME=myaccount PASSWORD=my.password1
Note:
If the ArcGIS Mission Server account is not defined during a silent (/qb) installation, or the credentials are not valid, the setup displays, Warning 208808: Credentials are not valid during installation. Click OK to close the message. The ArcGIS Mission Server account is set to the Local System account.
Make sure the user has full permissions to the ArcGIS Mission Server installation directory. The user account specified during ArcGIS Mission Server installation will be the account used to run the software.
INSTALLDIR—Installation location
USER_NAME—The Windows account can be a domain account or a local account. If you specify a domain account, it must already exist. If you specify a local account that does not yet exist, the setup creates the account. If the account is not valid, a message appears during installation indicating so.
PASSWORD—If this password is not valid, a message appears during installation indicating that either the account or the password is invalid.
Import account credentials from a file
If you don't have a configuration file to import, proceed to the next step.
You can also use a server configuration file to import your Windows account credentials. Server configuration files can be exported during ArcGIS Mission Server installation and used in future installations. To import credentials from an existing server configuration file, set the following two parameters:
- ACCOUNT—If you're importing credentials from a file, set this parameter to UseConfigFile (matching the case exactly). There are no other valid values for this parameter.
- CONFIGPATH—Specify the full path and name of the server configuration file you are using.
Example: <setup directory>\setup.exe /qb ACCOUNT=UseConfigFile CONFIGPATH=\\networkmachine\serverconfigs\standardaccount.xml
Export credentials to a server configuration file
If you don't want to export a configuration file, proceed to the next step.
You can export the account credentials used in the current ArcGIS Mission Server installation to use in a future installation. The server configuration file that is created is an encrypted XML file.
When exporting a server configuration file to a network share, the Local System account on the machine where ArcGIS Mission Server is being installed must have write permissions to the network share. For example, if you're installing ArcGIS Mission Server on a machine named Turing, the Local System account on Turing must have write permission to the network share. If the permissions are not set, the server configuration file may not export successfully.
Note:
If you are unsure how to correctly set permissions for the network share, contact your system administrator or export the server configuration file locally and copy it to the network share.
Use the following two command line parameters to export the ArcGIS Mission Server account credentials to a server configuration file:
- EXPORTCONFIG—Set this parameter to Yes to export the account information set for the USER_NAME and PASSWORD parameters to a server configuration file. The default is No.
- CONFIGPATH—Specify the full path and name of the server configuration file you want to create, including the file extension .xml. The specified folder must already exist.
Authorize your software
Once the installation is complete,use the software authorization wizard to authorize your instance of ArcGIS Mission Server, or you can authorize your software silently.
If you authorize your software silently, run SoftwareAuthorization.exe with the following syntax to authorize ArcGIS Mission Server silently. You must have all user information complete in the authorization or provisioning file before running the file.
If you have a .prvc authorization file, use the following command:
<ArcGIS Mission Server installation>\bin\SoftwareAuthorization.exe /S /Ver 10.8 /LIF <full path and name of .prvc authorization file>
After authorizing your software, create an ArcGIS Mission Server site. This can be done using the installation wizard or the createsite command line utility. The createsite utility can be used along with a silent installation to fully automate the ArcGIS Mission Serverinstallation.
Authorize in a headless environment
You can authorize ArcGIS Mission Server in an environment with no display (headless) using a provisioning (.prvc) file.
- At the prompt, run the following command after installation is complete:
<ArcGIS Mission Server installation>\bin\SoftwareAuthorization.exe /F <full path to the .prvc file> /O <full path to authorization file output>
- When the output information file has been created, do one of the following:
Browse to the Esri customer service website. Follow the instructions to upload your authorization information file and download your .prvc authorization file.
Send your authorization information file by email to [email protected]. Esri will send your .prvc authorization file back to you in an email.
- When you receive your .prvc authorization file, run the authorizeSoftware script again to process it and complete the server authorization process:
<ArcGIS Mission Server installation>\bin\SoftwareAuthorization.exe /F <full path to the .prvc file>
Repeat this workflow for each machine where ArcGIS Mission Server will be installed.After authorizing your software, create an ArcGIS Mission Server site. This can be done using the installation wizard or the createsite command line utility. The createsite utility can be used along with a silent installation to fully automate the ArcGIS Mission Server installation.