|
From: Josh J. <jj...@gc...> - 2007-03-28 14:57:16
|
I'm by no means an expert but I experienced this problem also. This is why I believe it happened to me.
1. I installed server and verified it was running and I could connect to HQ.
2. I installed my agent on another box and as soon as it said it successfully started I killed it so that I could proceed with installing the agent as a service.
3. I installed the agent as a service and started it.
4. That particular agent in HQ didn't show WIN32 or any of the hard drives.
I fixed it by removing the agent and reinstalling it. After you start the agent for the first time and it communicates with the server let it run for a while before you kill it to install as a service.
1. Stop the agent service on the windows box
2. Open your command line, change to your agents directory, and run hq-agent -u to uninstall as a service
3. Delete the Data folder from your agent directory
4. Use the SERVER installation download to install your agent
a. By running setup.bat -full (option 3 for agent install)
5. Complete the agent install so that your window says "agent successfully started"
6. DO NOT CLOSE THAT WINDOW
7. Log into your HQ and accept your auto discovery inventory, browse to that resource, and you should see that it is only partially populated
8. Refresh every few minutes and you should see that all of the availability icons change to green checks and your additional item like disk drives and CPU get added.
9. When satisfied close your agent, install it as a service, and restart it.
I was killing my initial agent discovery before it could complete, it sounds like you are having the same symptoms.
|