Follow

Machines reporting "Host is not registered" in Event Log of HUB

Product: Stratusphere FIT/UX

Product Version: All

Expires on: 365 days from publish date

Updated: July 20, 2018

 

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.

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.

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 Labs\Connector ID\idcontrol.exe" stop
"C:\Program Files (x86)\Liquidware Labs\Connector ID\idcontrol.exe" stop
del /f "C:\Program Files\Liquidware Labs\Connector ID\ca\cert*.*"
del /f "C:\Program Files (x86)\Liquidware Labs\Connector ID\ca\cert*.*"
"C:\Program Files\Liquidware Labs\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

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

0 Comments

Article is closed for comments.