Hello, I have a single OpsMgr management server and an agent running on W2K8 x86. Both the management server and agent are running OpsMgr 2007 SP1. Both systems are in the same domain. The agent is using an Action account which is a domain user that has Administrators status on the agent system and on the management server.
The Windows Firewall is disabled on both the management server and the agent system.
On the agent system, I can telnet to port 5723 on the management server.
After I installed the agent, it appears in the Operator Console under Monitoring / Computers, with the state "Not Monitored."
Under Active Alerts, the agent system is listed with the critical alert "Health Service Heartbeat Failure." However, the alert has a timestamp of a half-hour ago. On the agent system, in the Services applet you can see that the OpsMgr Health Service is running.
Also under Active Alerts, there is a warning event for "SDK SPN Not Registered"
On the agent system, the Operations Manager event log shows the following errors:
"OpsMgr was unable to set up a communications channel to mvm-jfm-opsmgr.usmv-osd.na.uis.unisys.com and there are no failover hosts. Communication will resume when mvm-jfm-opsmgr.usmv-osd.na.uis.unisys.com is both available and allows communication from this computer."
"The OpsMgr Connector could not connect to mvm-jfm-opsmgr.usmv-osd.na.uis.unisys.com:5723. The error code is 10060L(A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.). Please verify there is network connectivity, the server is running and has registered it's listening port, and there are no firewalls blocking traffic to the destination."
On the agent system, I can ping the management server by hostname. But there was a wrinkle with that. For some reason, the management server hostname was originally resolving to the wrong IP address. I tried to fix this by doing ipcong/release and ipconfig/renew on the management server, and ipconfig/flushdns on the agent system. This didn't help, so instead I added a hosts file entry on the agent system that maps the management server hostname to the correct IP address. As far as I know, that trumps everything, so the (presumed) DNS problem shouldn't be affecting the agent.
I'm also getting a series of Application event messages on the management server for Userenv. I don't know if these could affect OpsMgr. The following two messages appear once every half hour or so:
"Windows cannot query for the list of Group Policy objects. Check the event log for possible messages previously logged by the policy engine that describes the reason for this."
"Windows cannot access the file gpt.ini for GPO CN={31B2F340-016D-11D2-945F-00C04FB984F9},CN=Policies,CN=System,DC=usmv-osd,DC=na,DC=uis,DC=unisys,DC=com. The file must be present at the location <\\usmv-osd.na.uis.unisys.com\sysvol\usmv-osd.na.uis.unisys.com\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\gpt.ini>. (Logon Failure: The target account name is incorrect. ). Group Policy processing aborted."
It's hard for me to tell which of all these symptoms is important, and which to focus on. Thanks in advance for any suggestions.