IT Admin Deployment Guide

This page contains instructions for deploying and managing Desktop Connector using Configuration Manager (formerly called SCCM). To learn more about the Microsoft Configuration Manager, see the help topic Using Microsoft Configuration Manager to deploy and manage Autodesk products.

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


Topics in this section


Best Practices for installing Desktop Connector


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:

Download the current version of the script here: Example Deployment Script.

DC Powershell Script


Changelog Revision History for Deployment Script

Version Date Changes
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/7/2023 Initial version of sample script

Preparing for an Installation or Upgrade

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

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

  3. The installer will now be available for use in deployments in a location similar to the one shown. C:\Autodesk\Autodesk_Desktop_Connector_16_7_1_2164_Win_64bit


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 Setup.exe (Option 1)

This is the first option for uninstalling Desktop Connector. It requires the original Setup.exe to still be available

  1. Shut down all running Desktop Connector processes.

  2. Execute the original Setup.exe

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

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


Uninstalling with Standalone Uninstall (Option 2)

The second option for uninstalling Desktop Connector. It does not require any of the original install files. This is the method used in the example deployment script as shown:

  1. Shut down all running Desktop Connector processes.

  2. Obtain the uninstall string for the installed version of desktop connector.

    • This can be obtained from the registry under the following key: HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\
  3. Execute the uninstall string

    • Include the silent flag, "silent", to verify that no GUI is shown.

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:

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


Upgrading from a v15.x to v16.x of Desktop Connector

Warning:

If you are running any version of the 15.x family of Desktop Connector and would like to upgrade, you must uninstall that version before upgrading to version 16.x. A clean uninstall must be performed to upgrade efficiently.

To uninstall Desktop Connector follow these steps:

  1. Shut down all running Desktop Connector processes.

    • Exit Desktop Connector by right clicking the tray icon Online Icon and selecting Exit.
  2. Uninstall Desktop Connector v15.x (or earlier).

  3. After the uninstall confirms that local workspaces for all users have been deleted. If not, delete the local workspaces.

    • Local workspaces are any folders that are on your local machine. Delete these folders if found (to quickly navigate to your user profile folder type %userprofile% in File Explorer address bar):

      • C:\Users\<USERNAME>\AppData\Local\Autodesk\Desktop Connector
      • C:\Users\<USERNAME>\AppData\Local\Autodesk\Web Services\DesktopConnector
      • C:\Program Files\Autodesk\Desktop Connector
      • C:\ProgramData\Autodesk\Desktop Connector
  4. Install the v16.x version using the same steps described in the First-Time Installation section.

  5. You may have to perform a reboot for Desktop Connector to become available in your system tray. Upon installation you can select your projects to be added to your local drive.


Upgrading a v16.x version of Desktop Connector

  1. Shut down all running Desktop Connector processes.

    • Exit Desktop Connector by right clicking the tray icon Online Icon and selecting Exit.
  2. Install the newer version using the same steps described in the First-Time Installation section.

  3. Any older v16.x versions of Desktop Connector will be removed during the upgrade and no user action is required.


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.


Desktop Connector Installation Files


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 IDSDK/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.


Related Concepts: