Upgrade the mindShift Connector from 2.07 to 4.1

In order to upgrade your IDSync Software, please follow this simple 

Step-by-step guide

0.- Pre-requisites:

0.1.- Make sure the IDSync server has access to https://licensing.idsync.io.

Use any browser to access the URL:


0.2.- Download and install the Microsoft .NET Framework 4.6:


1.- Stop the IDSync Services and applications:

1.1.- IDSync Management Studio -> Service tab -> ‘Stop service’


1.2.- Windows ‘Services’ management console  (Start -> Services.msc) -> Identity Syncronizer – xxxxxxxx -> Stop Service)

Stop any Started service.

 


2.- Close the IDSync Management Studio (use the 'OK' button to make sure you save any recent change in the system's configuration).

 


3.- Open the Windows Explorer and go to the "C:\Program Files\" folder. Locate and rename the folder the "Identity Syncronizer" folder.


4.- Download the new installer (a URL will be sent via e-mail)

 


5.- Un-zip the installer

           

and Run it as administrator.


6.- Follow the on-screen instructions

Wait for the Identity Syncronizer software to be completely installed, then click Finish to close the installer.


7.- Open the IDSync Management Studio

Then, look for the Exchange tab, confirm the complete configuration is in place, and hit OK.


8.- Once again, open the IDSync Management Studio

Go to the Exchange tab >> License Key section and click on the '...' (Test License Key) button.


A pop-up window will let you know that the license Key has been validated.


As you've probably noticed, the 'License Customer' field is empty (and it can be left this way, since this is not a required field in the software configuration):


Please, do not edit it or write any value in that field (unless communicated by the IDSync support team).



9.- Go the Service tab, and Start the IDSync service


10.- Go to the Transactions tab to confirm that pending transactions are being processed.


Up to this point, the IDSync 'main' software has been upgraded and is running, but we still need to upgrade other components of the IDSync solution:

  • the MMC components (the tab used within the ADUC console)
  • and the IDSync Agent service (to capture and maintain synchronicity of the user's passwords).


Please be aware that you'll need to REBOOT any Domain Controller that you've just upgraded.


Upgrade any Domain Controller or Workstation running an IDSync component.


11.- (Still in the IDSync server) Open the Windows Explorer and navigate to the 'C:\Program Files\Identity Syncronizer\plugins\Installers' folder.

Select the folder that corresponds to the target machine (32 or 64 bit architecture) and copy the idsync.msi file to the Domain Controller or Workstation that you'll be upgrading.


12.- Log in to the Domain Controller or Workstation and Run this command (copy and paste it, then hit 'Enter')

 msiexec /i c:\idsync.msi REINSTALLMODE=VOMUS REINSTALL=ALL /norestart 

 

This will upgrade the IDSync software present in that server.


13.- Using the Windows Explorer, compare and make sure that the Agent.DLL file, present in both ('C:\Windows\system32'  and 'C:\Program Files\Identity Syncronizer') folders are the same (since this file is being used by windows, it is highly possible that the update process can't replace it in the .\system32 folder).

If required, please, rename the 'old' file and then copy the file from the .\Identity Syncronizer folder


14.- In order to complete the IDSync components upgrade, locate the 'Syncronizer.ManagementConsole.Installer.exe' file (in the 'C:\Program Files\Identity Syncronizer' foder) and Run it as Administrator:

Make sure the 'Enable AD users and Computers' option is checked and click OK.


Repeat these steps (11-14) for every Workstation or Domain Controller running any component of the IDSync solution.


Troubleshooting the License Key validation

  • We've seen in certain installations that the license key validation process may fail the first time is attempted (please see the messages present in the IDSync log files).


If you observe this behavior, please, Stop the IDSync service, and repeat steps 8 and 9 so a new validation cycle is performed.