V3. Getting Started
Cameron Kroeker edited this page Feb 11, 2023
·
8 revisions
- 10.6, 10.6.1, 10.7, 10.7.1, 10.8, 10.8.1, 10.9, 10.9.1
- 10.6, 10.6.1, 10.7, 10.7.1, 10.8, 10.8.1, 10.9, 10.9.1
- 10.8, 10.8.1, 10.9, 10.9.1
- 10.7, 10.7.1, 10.8, 10.8.1, 10.9, 10.9.1
- 10.8.1, 10.9, 10.9.1
Note: The Workflow Manager web app is included with the portal setup starting at 10.9.1
- Data Interoperability
- 10.6, 10.6.1, 10.7, 10.7.1, 10.8, 10.8.1, 10.9, 10.9.1
- Data Reviewer
- 10.6, 10.6.1, 10.7, 10.7.1, 10.8, 10.8.1, 10.9, 10.9.1
- Workflow Manager Classic
- 10.6, 10.6.1, 10.7, 10.7.1, 10.8, 10.8.1, 10.9, 10.9.1
- Location Referencing
- 10.6, 10.6.1, 10.7, 10.7.1, 10.8, 10.8.1
- Mapping and Charting Solutions
- 10.6, 10.6.1, 10.7, 10.7.1, 10.8, 10.8.1, 10.9, 10.9.1
- 3.4, 3.4.1, 2020.1, 2020.2, 2020.3, 2021.1, 2021.1.1, 2021.2, 2021.2.1, 2021.3, 2021.3.1
- 10.6, 10.6.1, 10.7, 10.7.1, 10.8, 10.8.1, 10.8.2
- Data Interoperability
- 10.6, 10.6.1, 10.7, 10.7.1, 10.8, 10.8.1, 10.8.2
- Data Reviewer
- 10.6, 10.6.1, 10.7, 10.7.1, 10.8, 10.8.1, 10.8.2
- Workflow Manager Classic
- 10.6, 10.6.1, 10.7, 10.7.1, 10.8, 10.8.1, 10.8.2
- Location Referencing
- 10.6, 10.6.1, 10.7, 10.7.1, 10.8, 10.8.1, 10.8.2
- Mapping and Charting Solutions
- 10.6, 10.6.1, 10.7, 10.7.1, 10.8, 10.8.1, 10.8.2
- Background Geoprocessing (64Bit)
- 10.6, 10.6.1, 10.7, 10.7.1, 10.8, 10.8.1, 10.8.2
- 2.0, 2.1, 2.2, 2.3, 2.4, 2.5, 2.6, 2.7, 2.8, 2.9
- Data Interoperability
- 2.0, 2.1, 2.2, 2.3, 2.4, 2.5, 2.6, 2.7, 2.8, 2.9
- 2018.0, 2018.1, 2019.0, 2019.1, 2019.2, 2020.0, 2020.1, 2021.0, 2021.1
-
Windows 8 (8.1) or Windows Server 2012 (R2)
- Windows Management Framework (WMF) 5.0 or 5.1.
-
Windows 10, Windows Server 2016, Windows Server 2019, or Windows Server 2022
- Windows Management Framework (WMF) 5.0 or 5.1. Typically, this comes pre-installed with the Operating System (OS).
Note - For client SKUs' (Windows 7,8.x,10), run the following commands i.e. Windows 8.1 and 10 to enable Windows PS Remoting.
Set-ExecutionPolicy RemoteSigned
winrm quickconfig
- Set the Location Configuration Manager (LCM)
ConfigurationMode
toApplyOnly
. For detailed steps please visit Microsoft's Configuring the Local Configuration Manager documentation. - Clone the repository to your local machine (e.g:- c:\arcgis-automation)
- 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)
- Download software installers and licenses from myesri.com.
- If your ArcGIS deployment spans more than a single machine, then use one of the following options -
- Add the Files to a FileShare. Grant permissions on the FileShare to the Local System Account of the Machines on which Installations needs to execute. The LCM (Local Configuration Manager) component of PowerShell DSC runs as the Windows Local System Account
- Manually copy software installation files and Licenses to each of the Remote Machines in the deployment.
- Edit the desired JSON configuration file. (Examples can be found in the SampleConfigs folder)
- Run the Invoke-ArcGISConfiguration commandlet and provide the path to the configuration file as an input parameter. Mode and Credential are optional arguments
Invoke-ArcGISConfiguration -ConfigurationParametersFile [[Path to Configuration json File]] -Mode [Install | InstallLicense | InstallLicenseConfigure | Uninstall | Upgrade] -Credential [Config RunAs - Optional]
or simply,
Invoke-ArcGISConfiguration [[Path to Configuration json File]] [Install | InstallLicense | InstallLicenseConfigure | Uninstall | Upgrade] -Credential [Config RunAs - Optional]
- Set the Location Configuration Manager (LCM)
ConfigurationMode
toApplyOnly
. For detailed steps please visit Microsoft's Configuring the Local Configuration Manager documentation. - Download software installers and licenses from myesri.com
- If your ArcGIS deployment spans more than a single machine, then use one of the following options -
- Add the Files to a FileShare. Grant permissions on the FileShare to the Local System Account of the Machines on which Installation needs to execute. The LCM (Local Configuration Manager) component of PowerShell DSC runs as the Windows Local System Account
- Manually copy software installation files and Licenses to each of the Remote Machines in the deployment.
- Install the ArcGIS module using the command Install-Module arcgis.
- Download sample configuration files from the GitHub repository.
- Edit the desired JSON configuration file.
- Run the Invoke-ArcGISConfiguration commandlet and provide the path to the configuration file as an input parameter. Mode and Credential are optional arguments
Invoke-ArcGISConfiguration -ConfigurationParametersFile [[Path to Configuration json File]] -Mode [Install | InstallLicense | InstallLicenseConfigure | Uninstall | Upgrade] -Credential [Config RunAs - Optional]
or simply,
Invoke-ArcGISConfiguration [[Path to Configuration json File]] [Install | InstallLicense | InstallLicenseConfigure | Uninstall | Upgrade] -Credential [Config RunAs - Optional]