Deploy an ArcGIS Desktop Float Use - Esri/arcgis-powershell-dsc GitHub Wiki
This workflow guides you through the first-time installation of ArcGIS Desktop Software across many machines. When the PowerShell DSC for ArcGIS module is finished, your machines will have the following components installed and licensed:
- One or more ArcGIS Desktops
- License Manager
You can spread these components across your machines in any configuration you wish.
Prepare your deployment
Before you run the command to the module in PowerShell DSC, you’ll need to obtain the necessary files and resources and add them to your local machine.
Note: We recommend you use WMF 5.x for the best experience.
Log in to the machine on which you'll be installing ArcGIS Desktop. You should have PowerShell DSC and administrative authority on the machine.
You can prepare the files either through GitHub or using the PowerShell Gallery:
Option 1: Prepare your deployment using GitHub
- Clone this repository to your local machine.
- Add the "ArcGIS" modules folder to your
PsModulePath
, or copy the modules into the default PowerShell Modules folder (e.g.C:\Program Files\WindowsPowerShell\Modules
). - Log in to My Esri. Download your ArcGIS Desktop and License Manager software installation files and licenses to the machine.
- Because you’re planning a multiple-machine deployment of ArcGIS Desktop, you will need to place the software installation files and licenses on each machine. You can do this in one of two ways:
- a) Add the file to a file share. Grant permissions on the file share to the LocalSystem Account of each machine that will be in the deployment. The LCM (Local Configuration Manager) component of PowerShell DSC runs as the Windows LocalSystem Account.
- b) Manually copy software installation files and licenses to each machine.
Option 2: Prepare your deployment using the PowerShell Gallery
- Log in to my.esri.com. Download your ArcGIS Desktop and License Manager software installation files and licenses.
- Because you’re planning a multiple-machine deployment of ArcGIS Desktop, you will need to place the software installation files and licenses on each machine. You can do this in one of two ways:
- a) Add the file to a file share. Grant permissions on the file share to the LocalSystem Account of each machine that will be in the deployment. The LCM (Local Configuration Manager) component of PowerShell DSC runs as the Windows LocalSystem Account.
- b) Manually copy software installation files and licenses to each machine.
- Install the ArcGIS module using the command
Install-Module ArcGIS
. - Download the
SampleConfigs
files from the GitHub repository.
Edit the configuration file
- Open the Desktop-Float.json file from the SampleConfigs folder on your local machine.
- Replace the placeholder variables in brackets with your deployment properties and parameters. Refer to the Variables reference page for a full list.
Because you can install many ArcGIS Desktops and License Manager in any configuration you'd like across your machines, the deployment architecture is determined by how you specify it in the AllNodes
section. For example, AllNodes
section below will install ArcGIS Desktop on Machine 1 and Machine 2, and License Manager on Machine 3:
{
"AllNodes": [
{
"NodeName": "[Machine Name 1]",
"Role": [
"Desktop"
]
},
{
"NodeName": "[Machine Name 2]",
"Role": [
"Desktop"
]
},
{
"NodeName": "[Machine Name 3]",
"Role": [
"LicenseManager"
]
}
],
Install your deployment
In PowerShell DSC, run the Configure-ArcGIS
cmdlet and provide the path to the configuration file as an input parameter. Mode
, DebugSwitch
and Credential
are optional arguments.
Invoke-ArcGISConfiguration -ConfigurationParametersFile [Path to Configuration JSON File](/Esri/arcgis-powershell-dsc/wiki/Path-to-Configuration-JSON-File) -Mode [Install | InstallLicense | Uninstall ] -Credential [Config RunAs - Optional] -DebugSwitch
or
Invoke-ArcGISConfiguration [Path to Configuration json File](/Esri/arcgis-powershell-dsc/wiki/Path-to-Configuration-json-File) [Install | InstallLicense | Uninstall ] -Credential [Config RunAs - Optional] -DebugSwitch