SCOM Agent Auto Approval Not Working

Question

Hi,

In my SCOM setup, I have enabled auto approval of manually installed agents. The newly deployed agents are showing in pending management, but they are not getting approved automatically. New agents are installed during VM deployments. Please let me know, if there is anything to be checked to fix the issue.

Regards

Fadil

Answer 1

Hi there,

It sounds frustrating to have your SCOM agents stuck in pending management.

Here are a few steps you can take to troubleshoot and resolve this issue:

Verify Auto-Approval Settings: Ensure that the auto-approval setting for manually installed agents is correctly configured. You can use the Set-SCOMAgentApprovalSetting cmdlet to check and set this configuration[1].

Check Health Service: Make sure the Health Service is running without errors on both the client agent and the management server. You can do this by checking the Microsoft Monitoring Agent service in the Services console[2].

Review Event Logs: Look at the OperationsManager event log on the agent for any errors or warnings that might indicate why the agent is not being approved. This log is usually very informative.

Manual Approval: If auto-approval is still not working, you might need to manually approve the agents from the Pending Management view in the SCOM console as a temporary workaround.

By following these steps, you should be able to identify and resolve the issue with auto-approval of your SCOM agents. If you need further assistance, feel free to ask!

Is there anything else you'd like to know or any specific error messages you're seeing?

References

[1] Set-SCOMAgentApprovalSetting (OperationsManager) | Microsoft Learn

[2] Troubleshoot agent connectivity issues in Operations Manager

Answer 2

The event log message "device attached not found in management group" suggests that the agent might not be properly recognized by the management group.

• Ensure that the agent is correctly configured to communicate with the appropriate management group. You can verify this by running the Get-SCOMManagementGroupConnection cmdlet on the agent machine to see if it is connected to the correct management group.
• Double-check the agent's configuration settings, including the management server it is pointing to. You can use the Get-SCOMAgent cmdlet to review the agent's settings.
• There might be "ghost" pending actions that are causing the issue. You can use the Get-AgentPendingAction cmdlet to review and clean up any pending actions that might be stuck
• Ensure that the SCOM database is in sync with the management server. Sometimes, database issues can cause agents to not be recognized properly. Running a database sync might help resolve this.