Upgrade the IDSync Mindshift Connector

Owned by Larry Yunker
Last updated: Jun 01, 2020 by Fernando Sayago (Unlicensed)
3 min read

This guide describes the upgrade process for an AD to Mindshift Syncronizer environment

Step-by-step guide

  • Download the most recent version from the Azure content delivery network.

  • Expand the zip file and locate the Identity Syncronizer x64 xxx.exe file

  • Stop all IDSync services (IdentitySyncronizer, AgentService, and Syncronizer.Attendant services), close Identity Syncronizer Management Studio and any other files that are open from c:\program files\identity syncronizer

  • Rename the C:\Program Files\Identity Syncronizer\ directory  (usually, suffixing it with the date it was changed)

  • Run a backup of the Identity Syncronizer database

  • Run Identity Syncronizer x64 xxx.exe file as administrator and confirm that you want to upgrade the current version

Click Next and then Finish.

  • After the installation completes, restart the Syncronizer.Service.exe and Syncronizer.Autoattendant.exe services.

  • Review log file in C:\Program Files\Identity Syncronizer\ to ensure that API calls are resulting in proper responses from Autotask’s new API calls.

  • Use the Agent push function (Agent tab of the IDSync Management Studio) to push the updated IDSync agent and MMC components to each domain controller.

  • Run the Syncronizer.Agent.Config.exe from 'C:\Program Files\Identity Syncronizer\'  on each domain controller in your environment (where you have the IDSync Agent installed) to ensure that the agent is installed and configured properly

  • Run the ManagementConsole.Installer.exe from 'C:\Program Files\Identity Syncronizer\'   on each domain controller in your environment (where you have the IDSync Agent installed) to ensure that the Autotask TAB is updated on the domain controller

  • Depending on which version of IDSync the customer is currently using, it is possible that the upgrade will also install a new Agent.DLL file. The agent.dll is used for password capture.  That process has been optimized over the past few years and the newer Agent.DLL is desirable.  If the Agent.DLL file was upgraded, the domain controllers should be scheduled to be rebooted whenever is convenient to the customer.  This reboot does not have to happen at the time of the install, but the new Agent.DLL will not be used until after the reboot occurs.