Problem:
Some IP's/hostnames are listed in Administration, Event Log with the message "Host is not registered". This happens when machines are deleted from inventory but still have the Connector ID installed. The HUB will not allow them to report data until they've been forced to re-register.
In the Connector ID folder on an end-point system, open the imgrcomm.txt file. If it has a line like this, it's probably the issue:
DETAIL: Client IP not registered. (1001)
Possible resolution:
To fix machines reporting Host not registered, we need to stop the services, delete cert.txt, certreq.tnt and start them again. They'll then re-register with the HUB.
Batch Script
To start you'll need to create a machineList.txt file with all of the IP's of 'bad' machines, or of ALL machines. Won't hurt existing working machines.
"C:\Program Files\Liquidware\Connector ID\idcontrol.exe" stop
"C:\Program Files (x86)\Liquidware Labs\Connector ID\idcontrol.exe" stop
del /f "C:\Program Files\Liquidware\Connector ID\ca\cert*.*"
del /f "C:\Program Files (x86)\Liquidware Labs\Connector ID\ca\cert*.*"
"C:\Program Files\Liquidware\Connector ID\idcontrol.exe" start
"C:\Program Files (x86)\Liquidware Labs\Connector ID\idcontrol.exe" start
This will stop the services, delete the needed files to cause them to re-register with the HUB properly when the services are then started at the end. It accounts for both 32/64-bit and will not interrupt the user and can be run at anytime. I would suggest putting the commands into a single script/batch file and then you could use psexec to run it remotely again a machine list you build, i.e.,
psexec.exe @machineList.txt -u Domain\AdminAcct -s -d -n 10 -c -f CIDreRegister.bat
Powershell script & SCCM
PowerShell script named Re-RegisterLiquidwareCID.ps1 with output for success message back to SCCM.
# Stop the Liquidware Connector ID Service
Stop-Service -Name "tntgrd"
Stop-Service -Name "tntdatasvc"
Stop-Service -Name "tntupdsvc"
# Delete any files cert*.*
Remove-Item "C:\Program Files\Liquidware\Connector ID\ca\cert*.*" -Force
Remove-Item "C:\Program Files (x86)\Liquidware Labs\Connector ID\ca\cert*.*" -Force
# Start the Liquidware Connector ID Service
Start-Service -Name "tntgrd"
Start-Service -Name "tntdatasvc"
Start-Service -Name "tntupdsvc"
# Write output, verifying the script has completed
Write-Output "Liquidware CID Key Re-Registered"
Send this script via SCCM to the machine collected from the event log that are reporting "Host is not Registered"
Courtesy of Nate @Medical Review Institute of America
Linux re-register:
sudo /etc/init.d/vs-helper stop
rm -f /opt/vdesktools/grd/cert.txt
sudo /etc/init.d/vs-helper start
Mac re-register:
/usr/bin/sudo /bin/launchctl unload "/Library/LaunchDaemons/com.liquidwarelabs.connectorID.plist"
rm -f "/Library/Application Support/Connector\ ID.app/cert.txt"
/usr/bin/sudo /bin/launchctl load "/Library/LaunchDaemons/com.liquidwarelabs.connectorID.plist"
Please see the latest Stratusphere Installation & Configuration Guide Appendix sections for updated information on Connector ID commands and file locations for various operating systems: https://docs.liquidware.com/stratusphere/en-us/stratusphere.htm
Product: Stratusphere FIT/UX
Product Version: All
Expires on: 365 days from publish date
Updated: April 18, 2024