SCOM Agent 2019 "Installation in Progress Error"

Siddhartha Suri Haripuram 1 Reputation point
2022-10-31T16:52:28.193+00:00

Hello Techies,

Trying to Install SCOM Agent in 2019 UR4 where ending up with an error as "Installation in progress" Tried to reject the Agent Installation (Also tried approving agent from OM Shell) which doesn't work. By This Agent is getting installed on the Client with all the Management Server and Group details whereas it doesn't get into Monitoring.

Rejected the Agent in pending management and uninstalled the Agent on client and deleted all the Microsoft Monitoring Agent Folders. Then tried to install the agent Manually on the Client whereas not getting popped in the Pending Management Tab. (Reviewing of Manual Agent for New installations in Pending Management is Enabled)

Checked Logs and found event 21023 with error "OpsMgr has no configuration for management group XXXXX and is requesting new configuration from the Configuration Service." on Client whereas i have tried to add my Dev Management Group within the Same Domain which is getting Monitored Successfully By getting it approved from the Pending Management in Dev SCOM. Whereas Same is not happening with the PROD SCOM.

Could anyone suggest with the options to tackle this errors.

Regards,
Sid

Operations Manager
Operations Manager
A family of System Center products that provide infrastructure monitoring, help ensure the predictable performance and availability of vital applications, and offer comprehensive monitoring for datacenters and cloud, both private and public.
1,438 questions
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. XinGuo-MSFT 15,476 Reputation points
    2022-11-01T09:08:35.387+00:00

    Hi,

    Is there any other error message on the event log, besides event id 21023.


  2. SChalakov 10,371 Reputation points MVP
    2022-11-02T07:17:27.31+00:00

    Hi,

    please make sure that:

    • The Management Group name and Management Server name, used for installing the agent do not have typos.
    • There is connectivity on port 5723 from the agent to the management server.
    • The agent is able to resolve the name of the manegemnt server properly.

    If all those are met, you can enable the verbose agent logging and check what is being logged there. Here is an guide, it is pretty simple to configure:

    How to Debug SCOM agent
    https://jurelab.wordpress.com/2014/09/25/how-to-debug-scom-agent/

    Please review the logs and paste here the relevant content, we will try to help you in finding the cause.

    ----------

    (If the reply was helpful please don't forget to upvote and/or accept as answer, thank you)
    Regards
    Stoyan Chalakov

    0 comments No comments