Monday, March 12, 2012

Sentillion Vergence installation

Sentillion Vergence
"A solution for bringing SSO, context management, and multi-factor authentication together on a clinical workstation. With its streamlined approach to the clinical workstation, Vergence helps your clinicians quickly access the applications they use to deliver care."
This documentation includes the following products:


  • Sentillion Vergence Desktop Components 4.5.6413 (Windows XP) / 4.5.6629 (Windows 7)
  • Sentillion Vergence Authenticator 3.5.6413 (Windows XP) / 3.5.6629 (Windows 7)
  • Sentillion Vergence BridgeWorks Runtime 2.9.0.6413 (Windows XP)



Sentillion Vergence Desktop Components
The Desktop Components installer will ask for a "Virtual IP" during installation (DNS) that is referenced internally as 'VAULTADDRESS':
  • Command-line installation:
    • "%~DP0DesktopComponents\VergenceDesktopComponentsWithMSIEngine.exe" /S /V"/qn /norestart ADDLOCAL=ALL ALLUSERS=2 VAULTADDRESS=YOUR.VIRTUALIP.HERE"

  • Command-line uninstall:
    • MsiExec.exe /X "{6F70A1F2-445B-4745-E2F2-8906CFBE04A8}" /qn /norestart

In my installer, I edited the MSI,and replaced 2 .DAT files in the [PROGRAMFILESFOLDER]Sentillion\Vergence Desktop Components\DATA folder that needed to be overwritten during installation so that I wouldn't need any other commands afterwards to run.
NOTE: ALWAYS make a backup of the original/vendor provided .MSI just in case something goes wrong (like using Orca instead of something better...)

If you want to run the installer without providing the user a script/long command-line to paste/type in, but still want the 'Virtual IP' populated; you can edit the SETUP.INI and add the following:
  • CMDLINE=/passive /norestart ADDLOCAL=ALL ALLUSERS=2 VAULTADDRESS=YOUR.VIRTUALIP.HERE

This will run the installer with just a basic GUI and automates the process for a user without the ability to cancel the installation.



Sentillion Vergence Authenticator 
The fun one :)


  • Command-line installation:
    • msiexec /i "%~DP0VergenceAuthenticator\Sentillion Vergence Authenticator.msi" /qn /norestart ADDLOCAL=ALL ALLUSERS=2 TRANSFORMS="%~DP0VergenceAuthenticator\LP.MST"

  • Command-line uninstall:
    • MsiExec.exe /X "{7AFFE349-5FCA-52B4-EE61-947501F5DCC9}" /qn /norestart

In my installer, I had to make the following changes:
  1. Copy different files into the [PROGRAMFILESFOLDER]\Sentillion\Vergence Authenticator folder (overwriting/replacing whatever existed in the stock/vendor installer so I again didn't have to copy over the files post-install). This required creating a copy of the MSI and editing the copy.
    • Some of these files were .INI files. Using Installshield (or whatever MSI editing app of your choice), I copied the .INI files that did not exist into the [PROGRAMFILESFOLDER]\Sentillion\Vergence Authenticator folder, and then imported the .INI files into the .INI menu to apply changes if needed.
  2. Create a StartUp shortcut to Launchpad (LP.exe).
    • I created a .MST Transform for the sole purpose of creating a 'StartUp' shortcut during installation.
      • If wondering why a transform, and not including this in the .MSI copy, it's because I can run the installer with or without the transform in case the need to have LP.EXE run at Startup is no longer needed.
NOTE: ALWAYS make a backup of the original/vendor provided .MSI just in case something goes wrong (like using Orca instead of something better...)



Sentillion Vergence BridgeWorks Runtime
The BridgeWorks installer isn't too bad (other than the fact that I don't have a Windows 7 compatible version at the moment).
  • Command-line installation:
    • "%~DP0BridgeWorks\setup.exe" /S /V"/qn /norestart ADDLOCAL=ALL ALLUSERS=2"

  • Command-line uninstall:
    • MsiExec.exe /X "{F8162985-DDE2-D0DC-7C88-129D474002F3}" /qn /norestart

In my installer, I needed to replace the BridgeWorks.ini [PROGRAMFILESFOLDER]Sentillion\BridgeWorks folder that needed to be overwritten during installation so that I wouldn't need any other commands post-installation to run.
NOTE: ALWAYS make a backup of the original/vendor provided .MSI just in case something goes wrong (like using Orca instead of something better...)

If you want to run the installer without providing the user a script/long command-line to paste/type in, you can edit the SETUP.INI and add the following:
  • CMDLINE=/passive /norestart ADDLOCAL=ALL ALLUSERS=2

This will run the installer with just a basic GUI and automates the process for a user without the ability to cancel the installation.

No comments:

Post a Comment