Discussion:
Agent installed successfully but not shown as Agent-Managed
(too old to reply)
gcdollar
16 years ago
Permalink
Hi,

I used the Discovery Wizard to install the agent on the target server. It
was successful. However, I could still see the action in pending. It's saying
that installation in progress. I waited for a few hours, and it's the same.
And no server was shown as Agent Managed as a result of this.

I have tried re-run the Discovery Wizard several times, and the results were
all the same. How can move the server which has agent installed to the
Agent-managed section?

Thank you.
Mike Resseler
16 years ago
Permalink
Hey Gcdollar

There are a few things you could check:

1) Check on that server in the eventviewer if it is throwing errors (in
operations manager log)
2) Maybe the installation is failed on that server, see if you can try a
manual installation on that server
3) Check on the management server in the eventviewer for logs (maybe the
scom is refusing this client...)

Can you check these things and also provide us with the following
information:
- OS and SP level of that server
- DMZ / Same domain as RMS / Different Domain / Trusts?

Cheers,

Mike
Post by gcdollar
Hi,
I used the Discovery Wizard to install the agent on the target server. It
was successful. However, I could still see the action in pending. It's saying
that installation in progress. I waited for a few hours, and it's the same.
And no server was shown as Agent Managed as a result of this.
I have tried re-run the Discovery Wizard several times, and the results were
all the same. How can move the server which has agent installed to the
Agent-managed section?
Thank you.
gcdollar
16 years ago
Permalink
Hi Mike,

Thank you for reply.

Yes, there seems an error in the Operation Manager's alert viewer, but I'm
not sure how to fix it because SQL server 2005 with SP1 is installed and SCOM
should have the access to it as I used the Administrator account. The error
is attached below.

I also tried manual install of the agent, and it was successful. I enabled
allowing agent manual installation on SCOM side, but I'm not sure how to
search and list the server which has the agent. The Discovery Wizard always
leads to the agent installation which is not needed. If I force to install
the agent again, it will fail.

Here is the error I saw in the alert viewer:

The process started at 2:47:58 PM failed to create System.PropertyBagData.
Errors found in output: C:\Program Files\System Center Operations Manager
2007\Health Service State\Monitoring Host Temporary Files
3\1049\GetOpsMgrDBPercentFreeSpace.vbs(42, 2) Microsoft OLE DB Provider for
SQL Server: [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist
or access denied.
Command executed: "C:\WINDOWS\system32\cscript.exe" /nologo
"GetOpsMgrDBPercentFreeSpace.vbs" IF-SCOM OperationsManager Working
Directory: C:\Program Files\System Center Operations Manager 2007\Health
Service State\Monitoring Host Temporary Files 3\1049\ One or more workflows
were affected by this. Workflow name:
Microsoft.SystemCenter.OpsMgrDBPercentFreeSpaceMonitor Instance name:
if-scom.ifqa.gc.au.ibm.com Instance ID:
{3E42B2F3-25B6-5B82-A336-43CAAE57AEC0} Management group: IMSSCOM

Info. on the env.
OS: Win Server 2003 Enterprise edition with SP2
SCOM and target server are on the same domain. Domain controller is
installed on the target server side.

Thank you very much.
...
Mike Resseler
16 years ago
Permalink
Hi gdcollar,

It seems that you have two problems here.

1) For the agent.

Can you check the eventviewer of the server with the agent for any problems?
You said that the manual installation was successfull and that you allowed
agent manual installation.
Do you auto-approve them or do you still need to approve a manual
installation. For the search, on the RMS server, in the administration
view, you can click agent-managed view and search for the server based on
its hostname

2) The error

This seems like a nasty one. Reading the error, I see that the SCOM action
account does not have the required permissions to have access to the
database DBNETLIB?

Let us know,

Cheers,

Mike

scomoperator.spaces.live.com
...
gcdollar
16 years ago
Permalink
Hi Mike,

For manually install the agent, I set auto approve on. I assume I don't need
to do anything after manually installing the agent on target server except
find it as a Agent Managed Computer. However, there seems no such option to
search under Administratrion view -> Agent Managent View. Right clicking
"Agent Managed" giving me a list of options and the only one seems doing the
search is Discovery Wizard. As I said before, it would force agent
installation. No option to uncheck the agent installation.

I checked the event viewer in the targe server and saw:
The OpsMgr Connector connected to if-scom.ifqa.gc.au.ibm.com, but the
connection was closed immediately after authentication occured. The most
likely cause of this error is that the agent is not authorized to communicate
with the server, or the server has not received configuration. Check the
event log on the server for the presence of 20000 events, indicating that
agents which are not approved are attempting to connect.

I'm afraid I'm not sure what the above is saying or how to fix it. I did
same thing using MOM2005 and it worked straight away. Is there some network
config missing? But they are on the same domain, and the firewall on both
sides are off. What else could it be?
...
Mike Resseler
16 years ago
Permalink
Hi gcdollar,

If you receive that error, it means that the SCOM server rejected the agent.

This can be caused by: (this list is not complete)

- Missing certificate if SCOM and managed-server is not in the same domain
- The server is not approved in scom (doubtfull since you set auto-approve
on)
- No communication between SCOM and the managed server

Can you telnet to port 5723 on the agent-based server to the SCOM server?

Mike
...
gcdollar
16 years ago
Permalink
Hi Mike,

I can telnet from the agent-based server to port 5723 of SCOM server, ping
by host name or IP address, all without a problem. But the error is still in
the event viewer.

I even tried to install agent on a clean machine, i.e. just Win Server 2003
with SP2, no other softwares. And got the same error. : (
...
GD
16 years ago
Permalink
Hi

A few more questions:
- is the agent in the same domain \ forest as the Operations Manager Root
Management Server?
- have you checked in the administration console under "Pending
Installation" to see if the agent is listed there?
- have you tried restarting the config and sdk services on the RMS to see if
that "enables" the change in administrative settings? I don't think you need
to do this but .... this is OpsMgr ..
- can you push an agent to these machines?

Cheers

Graham
...
gcdollar
16 years ago
Permalink
Hi GD,

1. The agent machine and the Operations Manager Server are on the same domain

2. After manual install of the agent, I don't see the agent is listed under
"Pending Installation" in the administration console. I see the error msg in
the Event Viewer. I think because of the "communication errors", the requst
wasn't pushed to "Pending Installation". that's my guess though.

3. yes, I have tried restarting the config and sdk services, many times.
but that don't seem make any difference.

4. Not sure what you mean by "can you push an agent to these machines?"

Thank you.
...
GD
16 years ago
Permalink
Hi

Ignore the "push" question - I see from earlier in the thread that you have
done this.

It is almost certainly an authentication \ permissons problem which are
difficult to troubleshoot remotely. But:

a) have the servers onto which you have installed agents been 'created' from
images (e.g from ghost)? Is there a duplicate name \ sid issue here? check
the system event log on the servers where the agents are failing.

b) do an nslookup <agentservername> - does the IP address of that server
look "right" or are there potential DNS issues?

c) when you install the agent, is the agent set to run as local system or
are you running it as a windows account?

d) is the server a domain controller?

e) do you have any SDK \ SPN errors -
http://blogs.technet.com/jonathanalmquist/archive/2008/03/12/sdk-spn-not-registered.aspx

Cheers

Graham
...
Continue reading on narkive:
Loading...