Principale utente con più risposte

A device which is not part of this management group has attempted to access this Health Service.

Domanda

Has anyone found an answer to this yet? I have uninstalled/reinstalled the agents both manually and through the push. Rebooted the client, rebooted the sce server. Forced the group policy to reapply, forced the health agent to /reportnow and I still get the error. The client shows up under the agent managed section but under the health state column it shows not monitored. The clients can ping the SCE server by FQDN and RDP to it as well so name resolution is working fine.

On the the SCE server I get this in the logEvent Type: InformationEvent Source: OpsMgr ConnectorEvent Category: NoneEvent ID: 20000Date: 6/25/2009Time: 10:09:40 AMUser: N/AComputer: *******Description:A device which is not part of this management group has attempted to access this Health Service. Requesting Device Name : *****

And this

Event Type:Information

Event Source:OpsMgr Connector

Event Category:None

Event ID:21042

Date:6/25/2009

Time:10:25:14 AM

User:N/A

Computer:***********

Description:

Operations Manager has discarded 1 items in management group Servername_MG, which came from $$ROOT$$.These items have been discarded because no valid route exists at this time.This can happen when new devices are added to the topology but the complete topology has not been distributed yet.The discarded items will be regenerated.

On the client I getEvent Type: ErrorEvent Source: OpsMgr ConnectorEvent Category: NoneEvent ID: 20070Date: 06/25/2009Time: 10:06:13 AMUser: N/AComputer: ******Description:The OpsMgr Connector connected to ****** 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.

And this as well

Event Type:Error

Event Source:OpsMgr Connector

Event Category:None

Event ID:21016

Date:06/25/2009

Time:10:06:18 AM

User:N/A

Computer:******

Description:

OpsMgr was unable to set up a communications channel to **** and there are no failover hosts.Communication will resume when ******* is both available and allows communication from this computer.

And this

OpsMgr has no configuration for management group Servername_MG and is requesting new configuration from the Configuration Service.

Risposte

Thanks David, We finally opened a case with MS. The problem was we had some orphan machines in our SCE database. Apparently SCE dosent handle this situation very well and did not let any other machines talk to theSCE server or join the SCE group untill they were removed. The orpahn machines did not show up in the console, but they were in an encypted in a table.

If anyone is interested I can email them the script that I was sent to detect and correct this issue.

Yea I have sent the script to eveyone that has aked for it. I dont know if its helped anybody else as none has given me any feedback either way.

I guess I can post it here for everyone to use. Please keep in mind that if you use this script from MS its at your own risk, If your DB blows up, massive catastrophic failure ensues and so forth ITS YOUR OWN FAULT. MAKE SURE YOU HAVE GOOD BACKUPS

Step 1) Run this against your SCE 2007 DB

DECLARE @BaseManagedEntityInternalId int

DECLARE @BaseManagedEntityId uniqueidentifier

DECLARE @ViewName sysname

DECLARE @Statement nvarchar(max)

SET @BaseManagedEntityInternalId = 0

WHILE EXISTS (SELECT * FROM BaseManagedEntity WHERE (BaseManagedEntityInternalId >

Before executing the above query please ensure that you have the backup of the database. Also note that you need to run the above said query only incase if you do not see the object in the Operations console.

Once it is done:> Stop all the three OpsMgr services: health, Config and SDK on Management Server> Cleared the health service state folder.> Start all the three OpsMgr services: SDK, Config, and health on Management Server.

Tutte le risposte

I noticed the last sentence. Did you run the Feature Configuration Wizard after you installing SCE?

Generally, when the Feature Configuration Wizard was run and Domain Policy mode was selected, a security group named “SCE Managed Computers (<Management Group Name>)” and two Group Policy objects named “SCE Managed Computers Group Policy” and “System Center Essentials All Computers Policy” should be created in Active Directory.

You can recreate it by rerunning the Feature Configuration Wizard.

1. Delete any SCE GPO from AD.

2. Run the command line below on the SCE server:

SCECertPolicyConfigUtil.exe /ManagementGroup <MGName> /uninstall

3. Confirm that the Registry key is removed:

HKLM\Software\Microsoft\System Center Essentials\1.0\PolicySettings

4. Run the Feature Configuration Wizard again and configure a domain-level Group Policy.

Before you install the agents manually, have you checked Global Settings (Administration --> Settings-->Server) to ensure you have configured security to not reject manual agent installations? They are rejected by default, and will result in some of the error messages you see above.Pete Zerger, MVP-OpsMgr and SCE | http://www.systemcentercentral.com

the Feature Configuration Wizard was already run. I have 100 desktops in the group functioning just fine its just one desktop thats getting the above message.the desktop is the exact image/hardware/sp/patch level ____ all the other desktops that are working just fine.

Is there any other error message logged, such as 20067 or 21002? If yes, it could be the problem of Mutual Authentication. Please navigate to the C:\Program Files\System Center Essentials 2007\Certificates directory on the Agent, verify if there are two files: WSUSSSL.cer and WSUSCodeSigning.cer.

Please also check the following conditions if the certificates correct:

1. Verify that the affected computer is in the SCE_Managed_Computers group:

a. Open Active Directory Users and Computers <DSA.MSC>

b. View the OU that contains one of the computers that is experiencing the issue

c. Open the properties of the Computer

d. Select the "Member Of" tab.

e. Verify that SCE_Managed_Computers is listed here. If not, add the computer to the SCE_Managed_Computers group.

f. Log the client off of the network, then log the client back on.

g. Restart the OpsMgr Health Service on the client.

2. Check if duplicate SPNs are there or missing, use following query command:

In the above command, replace DC=domain,DC=com with the DN of the domain

If you find and remove duplicate SPNs, use setspn -D to delete all of the HealthService SPNs. Then, restart OpsMgr Health Service on the management server and let it register its SPNs with the correct logon account. For example:

Ok here is a new twist, after a long weekend the machine finally showed up as being managed and all the of the event log error messages have disappeared.Now, however, the PC is in the "All Computers" Group but not in the all "All clients" default group or the "windows xp" group that I created.

Any ideas as to why It took about a week for it to show up as being managed and whoy not its not showing up in the proper groups?

Any ideas on this, any new computers i add to the domain are showing up as not monitored. The 100 or so original PC's are working fine

in the SCE server i get :

Event Type: InformationEvent Source: OpsMgr ConnectorEvent Category: NoneEvent ID: 20000Date: 8/11/2009Time: 5:23:31 PMUser: N/AComputer: *******Description:A device which is not part of this management group has attempted to access this Health Service. Requesting Device Name : ******

On the clients i getEvent Type: ErrorEvent Source: OpsMgr ConnectorEvent Category: NoneEvent ID: 20070Date: 08/11/2009Time: 5:29:17 PMUser: N/AComputer: ******Description:The OpsMgr Connector connected to ********* 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.

Open the Systems Center Operations Console, go to the administration area right click throw the management server or gateway server that you want, click on properties and on the security tab select this option "Review new manual agents installation in pending management view "

Thanks David, We finally opened a case with MS. The problem was we had some orphan machines in our SCE database. Apparently SCE dosent handle this situation very well and did not let any other machines talk to theSCE server or join the SCE group untill they were removed. The orpahn machines did not show up in the console, but they were in an encypted in a table.

If anyone is interested I can email them the script that I was sent to detect and correct this issue.

We put our RMS and MS into maintenance mode for our patch weekend and then installed 78 new agents. I believe it is due to the RMS being in maintenance mode that the health service doesn't register the new agents properly. I need to remove the entries from the database and I think a reinstall will fix it as at the moment it doesn't help.

Yea I have sent the script to eveyone that has aked for it. I dont know if its helped anybody else as none has given me any feedback either way.

I guess I can post it here for everyone to use. Please keep in mind that if you use this script from MS its at your own risk, If your DB blows up, massive catastrophic failure ensues and so forth ITS YOUR OWN FAULT. MAKE SURE YOU HAVE GOOD BACKUPS

Step 1) Run this against your SCE 2007 DB

DECLARE @BaseManagedEntityInternalId int

DECLARE @BaseManagedEntityId uniqueidentifier

DECLARE @ViewName sysname

DECLARE @Statement nvarchar(max)

SET @BaseManagedEntityInternalId = 0

WHILE EXISTS (SELECT * FROM BaseManagedEntity WHERE (BaseManagedEntityInternalId >

Before executing the above query please ensure that you have the backup of the database. Also note that you need to run the above said query only incase if you do not see the object in the Operations console.

Once it is done:> Stop all the three OpsMgr services: health, Config and SDK on Management Server> Cleared the health service state folder.> Start all the three OpsMgr services: SDK, Config, and health on Management Server.

Thanks David,
We finally opened a case with MS. The problem was we had some orphan machines in our SCE database. Apparently SCE dosent handle this situation very well and did not let any other machines talk to theSCE server or join the SCE group untill they were removed.
The orpahn machines did not show up in the console, but they were in an encypted in a table.

If anyone is interested I can email them the script that I was sent to detect and correct this issue.

Hi, I think I have the same situation. Some machines that were working in one domain and then moved to another trusted domain, started to show this error. They were being monitored ok before the move to a different domain