Jump to content


  • 0
Paul H

What causes Not Monitored state?

Question

Hi there,

 

I've installed RMS and deployed about 20 clients to my serverpark.

A month or so later i installed a second management server and tried to install clients to about 20 other servers

 

Installation of clients went well but they all show up as Not Monitored.

Even the 2nd Mgt server does that

 

I stopped the health service on target machines and deleted the state folder to no effect

stopped the health service on RMS and deleted the opsmgrconfig.xml to no effect

started the console with /c no effect

 

I now uninstalled all clients and will try again monday

 

Does anybody have any suggestions that i can try or check??

 

Update:

I've removed all opsmgr installations, including the DB and datawarehousing.

Re-installed the DB, the RMS and trying to install DW now but getting errors about the reporting on SQL 2008.

"HTTP://<servername>:80/reports" returns a config error.

tryed several accounts in Reporting services config mgr but no luck

backed up all my databases on the SQL box and will de-install reporting on the SQL server

That worked fine.

wish i could reach my management server in the other datacenter but the line is dead :(

 

to be continued....

 

Well the line is back

installed the management server in the other site

Imported Management packs

installed a couple agents... again not monitored

in the eventviewer i discovered errors stating connection was refused to the management server

On the mgt server i saw a clear statement of the problem: action account used did not have allow log on locally permissions...

 

Why didn't i check eventvwr earlier?? :angry:

 

after adding the action accout to the proper GPO and a gpupdate /force followed by a restart of the systemcenter management service my agents started to get in line

 

problem solved!

Share this post


Link to post
Share on other sites

4 answers to this question

Recommended Posts

  • 0

Hi there,

 

I've installed RMS and deployed about 20 clients to my serverpark.

A month or so later i installed a second management server and tried to install clients to about 20 other servers

 

Installation of clients went well but they all show up as Not Monitored.

Even the 2nd Mgt server does that

 

I stopped the health service on target machines and deleted the state folder to no effect

stopped the health service on RMS and deleted the opsmgrconfig.xml to no effect

started the console with /c no effect

 

I now uninstalled all clients and will try again monday

 

Does anybody have any suggestions that i can try or check??

 

Update:

I've removed all opsmgr installations, including the DB and datawarehousing.

Re-installed the DB, the RMS and trying to install DW now but getting errors about the reporting on SQL 2008.

"HTTP://<servername>:80/reports" returns a config error.

tryed several accounts in Reporting services config mgr but no luck

backed up all my databases on the SQL box and will de-install reporting on the SQL server

That worked fine.

wish i could reach my management server in the other datacenter but the line is dead :(

 

to be continued....

 

Well the line is back

installed the management server in the other site

Imported Management packs

installed a couple agents... again not monitored

in the eventviewer i discovered errors stating connection was refused to the management server

On the mgt server i saw a clear statement of the problem: action account used did not have allow log on locally permissions...

 

Why didn't i check eventvwr earlier?? :angry:

 

after adding the action accout to the proper GPO and a gpupdate /force followed by a restart of the systemcenter management service my agents started to get in line

 

problem solved!

 

 

Hi There,

 

I have the same issue. Could you tell me please how and where do you adding the action account to the GPO?

 

Regards

 

Nick

Share this post


Link to post
Share on other sites

  • 0

Hi Nick,

 

You can either create a new GPO or put this in an existing one.

In the Computer Configuration part of the GPO drill down to Windows settings\security settings\local policies\user rights assignment

One of the entries there is "Allow log on locally"

Here you can state all accounts that need these rights.

 

Be aware that everybody not in that list will be denied that right! So be carefull and first check who should have these rights beside the action accounts

 

good luck

Paul

Share this post


Link to post
Share on other sites

  • 0

Right, it should be in a GPO that can be applied by all computers that will recieve the Agent..

Sorry it wasn't clear the first time.

 

You can us a single GPO high up in the hierarchy or link a new one only to every OU that holds computers.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...


×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.