Share

Admin using Microsoft Configuration Manager

Topics in this section


Overview

Desktop Connector can be installed using Microsoft Configuration Manager. To learn more, see the help topic Using Microsoft Configuration Manager to deploy and manage Autodesk products


Version 16.9.1.2222 or later

Important: If Desktop Connector is already installed on the machine, it must be shut down prior to upgrading.
  1. OPTIONAL STEP: Create a SuppressNotification.reg to add and set the registry values:

    • [HKEY_LOCAL_MACHINE\SOFTWARE\Autodesk\Desktop Connector Advanced Settings]
    • "SuppressUpdateCommandAndNotifications"=dword:00000001
    Note: When using step 1, all notifications of any current or retired version of Desktop Connector will be suppressed.
  2. Create a Install.cmd file to install Desktop Connector:

    • regedit /s .\SuppressNotification.reg
    • Taskkill /IM desktopconnector.applications.tray.exe /f
    • Taskkill /F /IM explorer.exe
    • .\Setup.exe -i install --silent
  3. Place the Install.cmd and SuppressNotification.reg in the same location as the install executable.

  4. Include the Install.cmd in the SCCM deployment package.


Version 14.9.0.1430 to 16.8.0.2169

Important: If Desktop Connector is already installed on the machine, it must be shut down prior to upgrading.
  1. OPTIONAL STEP: Create a SuppressNotification.reg to add and set the registry values:

    • [HKEY_LOCAL_MACHINE\SOFTWARE\Autodesk\Desktop Connector\AdvancedSettings]
    • "SuppressUpdateCommandAndNotifications"=dword:00000001
    Note: When using step 1 all notifications of any new or retired versions of Desktop Connector will be suppressed.
  2. Create a Install.cmd file to install Desktop Connector:

    • regedit /s .\SuppressNotification.reg
    • Taskkill /IM desktopconnector.applications.tray.exe /f
    • Taskkill /F /IM explorer.exe
    • .\Setup.exe -i install --silent
  3. Place the Install.cmd and SuppressNotification.reg in the same location as the install executable.

  4. Include the Install.cmd in the SCCM deployment package.


Was this information helpful?