Package and Deploy ArcGIS Pro 3.5.7 in Configuration Manager

Learn how to package ArcGIS Pro 3.5.7, apply MSP patches, configure ODBC dependencies, and deploy to device collections using Microsoft Configuration Manager.

August 13, 2026 By Michael Limberg

This guide walks through packaging ArcGIS Pro 3.5.7 alongside its required ODBC drivers and software patches. Completing this ensures you have a fully automated deployment chain ready to be distributed to targeted device collections.

This workflow applies to SCCM Administrators and Packaging Engineers responsible for deploying enterprise software. It is typically used when preparing end-user workstations for a major version upgrade that requires a rigid prerequisite chain.

Part 1: Package the ODBC Drivers

Before deploying ArcGIS Pro, you must prepare its prerequisite ODBC drivers.

Step #1: Right-click in the Applications node of the Software Library and select Create Application. — Right-click in the Applications node of the Software Library and select **Create Application**.

Step #2: Browse to your network share and select the msodbcsql_17.10.6.1_x64.msi installer file. — Browse to your network share and select the `msodbcsql_17.10.6.1_x64.msi` installer file.

Enter a descriptive name, such as Microsoft ODBC Driver 17.10.6.1 for SQL Server.

Step #4: Specify the installation program command and proceed through the wizard summary. — Specify the installation program command and proceed through the wizard summary.

Step #5: Click Close when the application is successfully created. — Click **Close** when the application is successfully created.

Step #6: Right-click the new application and select Distribute Content to send it to your distribution point groups. — Right-click the new application and select **Distribute Content** to send it to your distribution point groups.

Step #7: Repeat the application creation process to create a second package for Microsoft ODBC Driver 18 using its MSI file. — Repeat the application creation process to create a second package for **Microsoft ODBC Driver 18** using its MSI file.

Step #8: Open the properties for the new ODBC 18 application, go to the Deployment Types tab, and double-click the MSI deployment type. — Open the properties for the new ODBC 18 application, go to the **Deployment Types** tab, and double-click the MSI deployment type.

Step #9: On the Content tab, configure the deployment options to Do not download content. — On the **Content** tab, configure the deployment options to **Do not download content**.

Step #10: Verify or edit your commands on the Programs tab, click OK, and distribute the content. — Verify or edit your commands on the **Programs** tab, click OK, and distribute the content.

Part 2: Package the Base ArcGIS Pro Application

Step #11: Right-click the ArcGIS folder in the Software Library and select Create Application. — Right-click the ArcGIS folder in the Software Library and select **Create Application**.

Step #12: Browse to your installation directory and select the ArcGISPro.msi installer. — Browse to your installation directory and select the `ArcGISPro.msi` installer.

Step #13: During the setup wizard, append custom parameters to the installation program line (e.g., ALLUSERS=1 INSTALLDIR="..."). — During the setup wizard, append custom parameters to the installation program line (e.g., `ALLUSERS=1 INSTALLDIR="..."`).

Step #14: Click Close to finish creating the base application. — Click **Close** to finish creating the base application.

Step #15: Edit the application's deployment type properties to set the content option to Do not download content, then distribute the application. — Edit the application's deployment type properties to set the content option to **Do not download content**, then distribute the application.

Part 3: Package the ArcGIS Pro 3.57 Patch

Step #16: Right-click your application folder and select Create Application. — Right-click your application folder and select **Create Application**.

Step #17: Select Manually specify the application information and click Next. — Select **Manually specify the application information** and click **Next**.

Name the application ArcGIS Pro 3.57 Patch.

Step #19: Navigate to the Deployment Types page and click Add. — Navigate to the **Deployment Types** page and click **Add**.

Step #20: Select Manually specify the deployment type and proceed. — Select **Manually specify the deployment type** and proceed.

Step #21: In the Content tab, specify the network location containing your patch .msp file. — In the **Content** tab, specify the network location containing your patch `.msp` file.

Step #22: Enter the patch installation command, ensuring you use the correct flags: msiexec.exe /p "ArcGIS_Pro_357_198657.msp" REINSTALLMODE=omus REINSTALL=ALL /qb. — Enter the patch installation command, ensuring you use the correct flags: `msiexec.exe /p "ArcGIS_Pro_357_198657.msp" REINSTALLMODE=omus REINSTALL=ALL /qb`.

Step #23: On the Detection Method tab, click Add Clause. — On the **Detection Method** tab, click **Add Clause**.

Step #24: Set the file system rule to check for ArcGISPro.exe located at C:\Program Files\ArcGIS\Pro\bin. — Set the file system rule to check for `ArcGISPro.exe` located at `C:\Program Files\ArcGIS\Pro\bin`.

Step #25: Change the property to Version, select Greater than or equal to, and enter 3.5.7.57366 as the value. — Change the property to **Version**, select **Greater than or equal to**, and enter `3.5.7.57366` as the value.

Step #26: On the User Experience tab, set the logon requirement to Install for system and the visibility to Hidden. — On the **User Experience** tab, set the logon requirement to **Install for system** and the visibility to **Hidden**.

Step #27: Click Next through the summary and click Close to finish. — Click **Next** through the summary and click **Close** to finish.

Step #28: Open the deployment type properties for the patch, navigate to the Content tab, and select Do not download content. — Open the deployment type properties for the patch, navigate to the **Content** tab, and select **Do not download content**.

Step #29: Distribute the content for the patch application to your distribution points. — Distribute the content for the patch application to your distribution points.

Part 4: Configure the Dependency Chain

To ensure all components install in the correct sequence, you must nest the application dependencies.

Configuration Manager processes dependencies recursively. When the patch is deployed, the client will automatically trigger the installation of ODBC 17, then ODBC 18, then the ArcGIS Pro base, and finally the patch itself.

Application	Deployment Format	Required Dependency
ArcGIS Pro 3.5.7 Patch	MSP Patch	ArcGIS Pro Base
ArcGIS Pro Base	Windows Installer (MSI)	Microsoft ODBC Driver 18
Microsoft ODBC Driver 18	Windows Installer (MSI)	Microsoft ODBC Driver 17
Microsoft ODBC Driver 17	Windows Installer (MSI)	None

Step #30: Open the properties for the ArcGIS Pro 3.57 Patch deployment type and navigate to the Dependencies tab. — Open the properties for the **ArcGIS Pro 3.57 Patch** deployment type and navigate to the **Dependencies** tab.

Step #31: Click Add to create a new dependency group. — Click **Add** to create a new dependency group.

Name the group, click Add, and select Specify Required Application.

Step #33: Select the ArcGIS Pro base deployment type and click OK. — Select the **ArcGIS Pro** base deployment type and click OK.

Step #34: Repeat this process on the base ArcGIS Pro deployment type properties to add Microsoft ODBC Driver 18 as a dependency. — Repeat this process on the base **ArcGIS Pro** deployment type properties to add **Microsoft ODBC Driver 18** as a dependency.

Step #35: Repeat the process on the Microsoft ODBC Driver 18 deployment type properties to add Microsoft ODBC Driver 17 as a dependency. — Repeat the process on the **Microsoft ODBC Driver 18** deployment type properties to add **Microsoft ODBC Driver 17** as a dependency.

Part 5: Target a Device Collection

Step #36: Navigate to Assets and Compliance, right-click Device Collections, and select Create Device Collection. — Navigate to Assets and Compliance, right-click **Device Collections**, and select **Create Device Collection**.

Enter a name for the collection, such as ArcGIS 3.5.7 (with Patch).

Step #38: Click Browse and select a limiting collection, such as All Systems. — Click **Browse** and select a limiting collection, such as **All Systems**.

Step #39: Add your desired membership rules, such as a schedule to evaluate collection members. — Add your desired membership rules, such as a schedule to evaluate collection members.

Step #40: Complete the wizard and click Close. — Complete the wizard and click **Close**.

Q: How is the ArcGIS Pro patch detected after installation?

A: A file system rule checks the version of ArcGISPro.exe at C:\Program Files\ArcGIS\Pro\bin. If the version is greater than or equal to 3.5.7.57366, the patch is considered successfully installed.

Q: In what order will the applications install?

A: Because dependencies are chained, Configuration Manager installs them recursively: ODBC Driver 17, then ODBC Driver 18, then the base ArcGIS Pro package, and finally the ArcGIS Pro patch.

Q: How do I apply custom settings to the base ArcGIS Pro installation?

A: You can append custom arguments like ALLUSERS=1 and INSTALLDIR to the installation command line on the Programs tab of the application's deployment type.

Term	Definition
Deployment Type	A set of installation files and command-line parameters in Configuration Manager used to deploy a specific application.
Distribution Point	A server role in Configuration Manager that hosts the source files for clients to download software.
Device Collection	A logical grouping of devices in Configuration Manager used as a target for application deployments or policy settings.
Detection Method	A set of rules in Configuration Manager used to determine whether an application or patch is already installed on a client.
Dependency	A Configuration Manager feature that forces one or more applications to install before the primary application deployment begins.
MSI	A Windows Installer package format that contains the instructions and data required to install an application.
MSP	A Windows Installer patch file used to deliver updates to an application already installed via an MSI package.
PXE DP	A Distribution Point configured to support Preboot Execution Environment (PXE), typically used for deploying operating systems over a network.