Share

Admin Deployment Guide

Topics in this section

Best Practices for installing Desktop Connector

These instructions are intended for IT specialists with an understanding of Configuration Manager (formerly called SCCM). For more information on deploying Autodesk software using Configuration Manager, refer to this Using Microsoft Configuration Manager to deploy and manage Autodesk products.

  • Always use the .EXE (ODIS installer) for installations and upgrades. This ensures that all necessary dependencies (like Identity Manager and ADSSO, .Net runtime, C++ runtimes, etc.) are installed along with the software.

  • If you choose to use the .MSI file for installation, be aware that it does not bundle any dependencies - you are responsible for installing these separately.

  • Avoid mixing the installation methods (MSI/EXE). Use the same method for both the initial installation and any subsequent upgrades. This can help prevent dual entries in the Programs list or other potential issues.

  • Refer to Installing Desktop Connector using MSI vs. EXE within this document for more detailed information.

  • Autodesk has changed the way the installers are extracted and files are downloaded prior to installation.

    • Refer to the next section Preparing for an Installation or Upgrade for additional information.

Best Practices for Upgrading Desktop Connector

Major vs. minor release upgrades

The recommended upgrade method depends on whether users are upgrading to a minor release or a major release:

  • Minor release (e.g., 16.14 → 16.16 or 17.0 → 17.2): Deploy the new version as an in-place upgrade. Do not uninstall first. User project selections and settings are preserved.
  • Major release (e.g., 16.x → 17.x): The deployment script handles the full reset, uninstall, and reinstall cycle automatically. For manual upgrade workflows, run the Reset Utility, uninstall, and then reinstall to ensure all components and configuration are properly cleared.

For detailed user-facing upgrade steps, see Update Desktop Connector.

Deployment planning guidance

When planning Desktop Connector upgrades across your organization, consider the following:

  • Validate before broad rollout. Test the new version in a controlled environment or with a pilot group before deploying organization-wide.
  • Upgrade when fixes or improvements are relevant. Review the Latest Release Notes to understand what each release includes. Consider upgrading when the release addresses reliability, performance, or workflow issues relevant to your environment.
  • Align versions across teams. Maintaining a consistent Desktop Connector version across teams and offices is recommended to reduce complexity for both users and support.
  • Plan for major release transitions. Upgrading to a new major release (e.g., 16.x to 17.x) involves a reset, uninstall, and reinstall cycle. Factor this into your change management and deployment schedules, including communication to end users.
  • Coordinate with your internal deployment cycles. Schedule upgrades during planned maintenance windows when possible, and ensure your team has time to validate the upgrade before rolling it out broadly.

Download Options for Deployment

Standard Download

Download the latest version of Desktop Connector from the Latest Release Notes Page.

Custom Install Packages

For organizational deployments, you can create Custom Install packages through manage.autodesk.com:

  1. Go to manage.autodesk.com
  2. Navigate to Custom Install
  3. Create your custom deployment package for Desktop Connector
  4. Download the custom package for deployment across your organization
Note:

Custom Install packages are available starting with v17.0 and are supported for both annual releases (2027.0, 2028.0, etc.) and regular upgrades (17.1, 17.2, 2027.1, etc.).

Preparing for an Installation or Upgrade

  1. Download Desktop Connector using one of the methods described in the Download Options for Deployment section.

  2. Open the downloaded package and allow it to extract.

  3. The installer for version v16.8 and below will be downloaded to the default folder in Windows similar to the one shown. C:\Autodesk\Autodesk_Desktop_Connector_16_8_0_2169_Win_64bit

  4. The installer for version v16.9 and above will be downloaded to the default folder in Windows similar to the one shown. C:\Autodesk\Desktop Connector 16.9 Install Files

Example Deployment Script

Important: Autodesk is providing this information for Reference Purposes Only. We recommend that IT admins use this script as a guide to create their own script tailored to their business needs. The script has been designed to help with deployments addressing the following information:
  • This PowerShell script demonstrates how Desktop Connector can be deployed as an IT administrator.
  • It is intended as a reference for IT administrators using Configuration Manager (formerly SCCM) deployments.
  • Do not run this script directly without first reading through the contents and making necessary changes.
  • This script supports install, upgrade, and uninstall operations.
  • For install workflows, this script should be run in the same directory as the Setup.exe executable.
Important: Download the current version of the script here: Example Deployment Script.
Note:

The deployment script includes the cleanup steps that the Reset Utility performs. If you are deploying Desktop Connector using the script, you do not need to run the Reset Utility separately. The Reset Utility is intended for manual uninstall and upgrade workflows only, and it only removes data for the currently logged-in user.

Changelog Revision History for Deployment Script

Version Date Changes
4 5/11/2026 Added support for local workspace cleanup and major release upgrades
3 3/24/2023 Improved documentation in the scripts comments and console outputs
2 3/21/2023 Correctly stop DC before attempting install operations
1 3/07/2023 Initial version of sample script

First Time Installation

  1. When installing for the first time, the installer prepared in the preceding section can be run directly.

  2. When running the installer in a deployment, verify that you are providing the appropriate flags to run silently.

Uninstalling with Standalone Uninstall (Option 1)

For full steps, refer to the Uninstalling Desktop Connector page.

Note:

If you are using the deployment script, the cleanup steps that the Reset Utility performs are built into the script. You do not need to run the Reset Utility separately.

Uninstalling with Setup.exe (Option 2)

This option requires the original Setup.exe to still be available.

  1. Shut down all running Desktop Connector processes.

  2. Run the Reset Utility

  3. Execute the original Setup.exe

    • Example usage: Setup.exe --silent -i uninstall

For more information, refer to Modify a deployment from Autodesk Account.

Unusable "Ghost" Drive Left Behind after Administrative Uninstall

After uninstalling Desktop Connector with Configuration Manager or other administrative means, users may be left with an unusable "ghost" drive like in the following picture:

DC Ghost Drive

If you are planning on reinstalling Desktop Connector, no further action is required. Desktop Connector will automatically clean up any disconnected drives when it starts up.

If you need to remove this "ghost" drive, have the affected user:

  • Download the ZIP file from this link: DC Reset Utility.

    • Extract the contents of the ZIP file to a local folder or your desktop.
    • Run the ResetDesktopConnector.exe file included.
    • Verify that the "ghost" drive is removed

For further information on the Reset Utility, refer to this video Reset Desktop Connector Automated Utility.

Note:

The Reset Utility only removes data for the currently logged-in user. On shared machines, each affected user will need to run it individually.

Manually upgrading Desktop Connector

If you are upgrading using the deployment script, the reset and cleanup steps are handled automatically—no manual steps are required.

For manual upgrade workflows (major or minor release), including detailed step-by-step instructions, see Update Desktop Connector.

Display version vs. MSI ProductVersion

Starting with v2027.0, Desktop Connector uses a year-based version format (for example, 2027.0.0.XXXX). Because Windows Installer requires the first field of the MSI ProductVersion to be 255 or less, the year is shortened in the MSI ProductVersion: 2027 becomes 27, 2028 becomes 28, and so on.

The display version (the full year format) is what users see in the Desktop Connector tray, Programs and Features, and Add or Remove Programs. The MSI ProductVersion (the shortened year format) is the version recorded in the Windows Installer registry and returned by MSI queries.

Version type Format Example Where it appears
Display version YYYY.Major.Minor.Build 2027.0.0.XXXX Desktop Connector tray, Programs and Features, Add or Remove Programs
MSI ProductVersion YY.Major.Minor.Build 27.0.0.XXXX Windows Installer registry (HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\), deployment scripts, MSI property queries

If your deployment scripts or Configuration Manager detection rules query the MSI ProductVersion, use the shortened year format (for example, 27.0.0.XXXX). For user-facing communication and documentation, use the display version (for example, 2027.0.0.XXXX).

Installing Desktop Connector using MSI vs. EXE

What are MSI and EXE files?

A MSI (Microsoft Installer) file and an EXE (executable) file are both types of installation files.

  • The main difference between them lies in their customization and deployment capabilities. MSI files are database files, used by Windows Installer, that store installation settings for software applications. They allow for more customization and are used for network-wide software deployment.
  • On the other hand, EXE files are standalone executable files that initiate an installer for a software program. They are simpler and less customizable.

Desktop Connector Installation Files

  • The recommended method for installing the Desktop Connector is by running the downloaded .exe file located in the Downloads folder for the current user. When you download the desktop connector .exe it will be found at the following location:

    C:\Users\<username>\Downloads

    DC Executable File

  • You will have to run the DesktopConnector-x64.exe and allow it to self-extract to the default location: C:\Autodesk. By allowing it to self-extract you may find the CDX.msi at the following location on your hard drive:

    DC MSI File

FAQs for using MSI vs. EXE installs

Can I use the .msi file for installation?

Yes, you can use the .msi file for installation, but it does not bundle any dependencies. You will need to install these separately.

What happens if I use the .exe for installation and the .msi for upgrade (or vice versa)?

Using different methods for installation and upgrade might result in dual entries in the Programs list. It's best to use the same method for both.

What are the dependencies that I need to install if I choose the .msi file?

The dependencies include but are not limited to Identity Manager/ADSSO, .Net runtime, and C++ runtimes.

Where can I find information about changes in dependencies if I decide to handle them myself?

Remember, these practices and FAQs are based on feedback and customer testing and might not cover all possible scenarios or questions. For the most accurate and comprehensive information, always refer to the official Autodesk support and documentation.

Pre-configured project subscriptions for new installations

Starting with Desktop Connector v2027.2.0, administrators can define a list of projects for Desktop Connector to subscribe to automatically the first time it starts after a fresh installation. When enabled, Desktop Connector reads a subscription file you provide and creates subscription jobs for each listed project, so users are ready to work without selecting projects manually.

Note:

This feature applies only to the first startup after a full installation. It does not run on upgrades or subsequent startups.

Registry key

Add the following value to the Desktop Connector Advanced Settings registry key — the same key used for workspace configuration and delete notification settings.

To apply to all users on the machine (HKLM):

HKEY_LOCAL_MACHINE\SOFTWARE\Autodesk\Desktop Connector Advanced Settings

To apply only to the current user (HKCU):

HKEY_CURRENT_USER\SOFTWARE\Autodesk\Desktop Connector Advanced Settings

Value Name Type Description Default
EnableProjectSubscriptionImport REG_DWORD Enables automatic project subscription on first startup. Set to 1 to enable. 0 or absent disables the feature. Disabled

If this registry key is not set, the subscription list file is ignored and no projects are subscribed automatically.

Important:

Modifying the Windows Registry can have serious effects on a system. Always back up the registry before making changes.

For the full setup workflow — including how to export a subscription file, where to place it, and what happens during first startup — see the Admin Project Subscription Deployment Guide for step-by-step instructions.

Preparing for a network domain change

Certain network changes can impact the stability of Desktop Connector and should be approached with caution and planning. Events like changing the network domain name will impact Desktop Connector and will require steps to restore normal Desktop Connector behavior. Properly planning the activities following a domain name change will ensure Desktop Connector continues to function as expected.

Related Concepts:

Next page: Admin Change Workspace Guide

Was this information helpful?