Secunia
|
|

|
|
|
|
|
|
|
|
|
|
|
|
|
| mdivet | host not found |
|---|---|
|
12th Jun, 2012 16:18 |
|
Ranking: 0 Posts: 2 User Since: 12th Jun, 2012 System Score: N/A Location: US |
I have a host that had CSI agent installed as part of a Win7 32-bit image, and the host cannot be found in the CSI console. The CSI agent was removed from our default image as I understand that to cause problems with the unique identifier. The CSI Agent is now deployed via WDS. The goal is to make the host report to the CSI console, and in turn use this method to fix other hosts that have the CSI agent from image and not reporting in. I have tried, in this order: 1. log on to host; remove CSI agent. 2. open regedit; delete hkey_local_machine > software > secunia key, and hkey_local_machine > software > wow6432node > secunia (where applicable.) 3. reboot 4. log on again. re-install CSI agent via windows update. 5. go to CSI console on the server; refresh database. then search for host. host not found. Suggestions are appreciated. |
| O.Marin | RE: host not found |
|
15th Jun, 2012 11:26 |
| Score: 30 Posts: 116 User Since: 4th Aug 2011 System Score: N/A Location: Copenhagen, DK |
Hi, If you had problem with duplicate GUID for CSI Agent then you can do the following steps to remove the GUID: 1. Remove the CSI Agent - open command prompt, go to the location of the csi agent and run csia.exe -r 2. Remove from the registry the entry GUID - go to Regedit -> HKEY_LOCAL_MACHINE\SOFTWARE\Secunia\GUID (for 32-bit) or HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Secunia\GU 3. Reinstall the CSI Agent - from command prompt, go to the location of the csi agent and run csia.exe -i -L The CSI Agent has a 10 minutes delay build in so it might take 15 minutes until you see the agent in the CSI Console. From your post I can see you've done the steps above. Do you still have issues that the CSI Agents are not checking in? -- Kind Regards, Oana Marin Solution Specialist |
| mdivet | RE: host not found | ||||||||
|
15th Jun, 2012 17:15 | ||||||||
| Score: 0 Posts: 2 User Since: 12th Jun 2012 System Score: N/A Location: US |
It does appear that removing the GUID and reinstalling CSI agent does fix the problem; it took the better part of a week but the host did finally appear in the CSI console. Thank you for your input. |
||||||||
|
|||||||||
Not a customer already?Learn more about how our market leading Vulnerability Management solutions can help you manage risk and ensure compliance. |