Skip to main content

Can I reassign the Connector ID Key on a desktop to report to a new HUB or HUB Address?

Steven Hajek
  • Created:
  • Updated:

Problem:  Can I reassign the CID Key on a desktop to report to a new Hub or same HUB but with new IP without reinstalling the Connector ID on all machines manually?

 

Possible Resolution(s)

 

---Windows---

Using a GPO: 

(Easiest method and works in all scenarios: physical, virtual, persistent, non-persistent)

  • Create a new GPO using the attached ADM template.
  • Registry value has now been updated for version 6.7 
  • Edit the 32-bit and 64-bit HUB address values to point to the new HUB.
  • Link it to the appropriate OU's. 
  • Once the policy is pushed out to the machines after some time or a reboot, they will switch over and begin reporting to the new HUB address.

 

Using the registry or a script:


For physical and persistent desktops:

(For persistent desktops based on a master image with occasional refreshes, you would still want to update the master as noted below)

 

 

New 6.7 Install Registry Location going forward:

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Liquidware Labs\ConnectorID

For 6.7 CID Agent versioned machines, execute:

CMD

reg add "HKLM\SOFTWARE\Liquidware Labs\ConnectorID" /v hubAddress /t REG_SZ /f /d <NEWHUBADDRESS>

PSEXEC

psexec.exe @ComputerList.txt -u DOMAIN\Admin -d -s reg add "HKLM\SOFTWARE\Liquidware Labs\ConnectorID" /v hubAddress /t REG_SZ /f /d 10.1.2.3 

 

Related KB: What command line options are available to me during manual connector id install? – Liquidware Customer Support (zendesk.com)

 

For Legacy CID versioned machines (6.6.2-2 and older), please reference below:

 

For 64-bit machines, execute:

reg add "HKLM\SOFTWARE\Wow6432Node\Liquidware Labs\ConnectorID" /v hubAddress /t REG_SZ /f /d <NEWHUBADDRESS>

For 32-bit machines:

reg add "HKLM\SOFTWARE\Liquidware Labs\ConnectorID" /v hubAddress /t REG_SZ /f /d <NEWHUBADDRESS>


This command can be executed across a list of machines using psexec.exe in the PSTools package from SysInternals.  You would need a ComputerList.txt with one resolvable machine name/IP on each line.

You could then mass-deploy this similar to the following using psexec:

 

64-bit example: 

 psexec.exe @ComputerList.txt -u DOMAIN\Admin -d -s reg add "HKLM\SOFTWARE\Wow6432Node\Liquidware Labs\ConnectorID" /v hubAddress /t REG_SZ /f /d 10.1.2.3

(example IP, replace with new HUB IP or DNS)

32-bit example: \

psexec.exe @ComputerList.txt -u DOMAIN\Admin -d -s reg add "HKLM\SOFTWARE\Liquidware Labs\ConnectorID" /v hubAddress /t REG_SZ /f /d 10.1.2.3 

(example IP, replace with new HUB IP or DNS)

 

Once the command was executed on a given machine:

  • It will automatically start sending data to the new HUB address on the next scheduled callback. 
  • It won't hurt to execute both "REG ADD" commands on all machines so you don't need to separate 32-bit from 64-bit and execute twice.
  • Put both commands in a bat file and execute with psexec the same, just add the -c and -f flags to the psexec command.

 

For non-persistent VDI desktops:

(The above method can also be used here but in most cases an uninstall/reinstall is about the same amount of work)

  • On the master image, uninstall the existing CID using Programs and Features. 
  • Download the CID from the new HUB and install to base image.  (You still need to re-download from your HUB if you've only changed the HUB IP or DNS since the hubAddress value is branded into the EXE installer.) 
  • Once confirmed the master is reporting data to the new HUB, execute the appropriate master prep script in:
  • Follow this up with a recompose and the desktops will now report to the new HUB or new IP of existing HUB.

 

---Linux---

You'll need to run the following command locally or remotely to change the HUB address:

sudo /opt/vdesktools/bin/idenq -H <newHUBaddress>

Then if you want to speed it up and not wait until the next callback, you'd run:

sudo /sbin/service vs-helper restart

---MacOS---

You'll need to run the following command locally or remotely to change the HUB address:

/usr/bin/sudo  "/Applications/Connector ID.app/Contents/MacOS/idenq" -H <newHUBaddress>

Then if you want to speed it up and not wait until the next callback, you'd run these 2 commands:

/usr/bin/sudo /bin/launchctl unload "/Library/LaunchDaemons/com.liquidwarelabs.connectorID.plist"

/usr/bin/sudo /bin/launchctl load "/Library/LaunchDaemons/com.liquidwarelabs.connectorID.plist"

 

Product: Stratusphere FIT/UX         

Product Version: ALL

Expires on: NEVER

Updated: April 4th, 2024

Related articles