SCOM Agent Instalation on Windows Servers when all of OS and .Net updates are installed

Question

Hi,
I have a problem regarding installing SCOM agent Remotely/Locally on Windows Servers 2019, I found the main issue regarding my investigation, the main issue is the agent installation got failed when all of OS and .NET updates have been installed before SCOM agent installation, the error is in the following.

Windows Installer installed the product. Product Name: Microsoft Monitoring Agent. Product Version: 10.22.10056.0. Product Language: 0. Manufacturer: Microsoft Corporation. Installation success or error status: 1603.

To make sure about the issue I have installed a fresh OS without any updates and the agent installed successfully, is there any solution or way to install successful the mentioned agent on our windows servers?

The error log which is stored on the SCOM server.
10:46:55 AM : OmAgentFunctions::IsProductInstalled : Leaving
10:46:55 AM : OmAgentFunctions::IsSceServerPresent : IsProductInstalled() failed. HResult: 80070647
10:46:55 AM : OmAgentFunctions::IsSceServerPresent : Leaving
10:46:55 AM : OmAgentFunctions::IsSmServerPresent : Entering
10:46:55 AM : OmAgentFunctions::IsProductInstalled : Entering
10:46:55 AM : OmAgentFunctions::IsProductInstalled : Leaving
10:46:55 AM : OmAgentFunctions::IsSmServerPresent : IsProductInstalled() failed. HResult: 80070647
10:46:55 AM : OmAgentFunctions::IsSmServerPresent : Leaving
10:46:55 AM : OmAgentFunctions::IsHsInstalled : HealthService not installed.
10:46:55 AM : OmAgentFunctions::IsHsInstalled : Leaving
10:46:55 AM : OmAgentFunctions::InstallOmAgent : No HealthService found, performing install.
10:46:55 AM : OmAgentFunctions::InstallOmAgentMsi : Entering
10:46:55 AM : OmAgentFunctions::SetMsiLogging : Entering
10:46:55 AM : OmAgentFunctions::SetMsiLogging : Leaving
10:47:07 AM : OmAgentFunctions::InstallOmAgentMsi : MsiInstallProductW() failed. HResult: 80070643
10:47:07 AM : OmAgentFunctions::GetNTEventLogDescription : select * from Win32_NTLogEvent where LogFile="Application" and EventType = 3 and SourceName = "MsiInstaller" and TimeGenerated >= "20220914061655.000910+000" and TimeGenerated <= "20220914061707.000570+000" HResult: 0
10:47:07 AM : OmAgentFunctions::GetNTEventLogDescription : Next returned HResult: 1
10:47:07 AM : OmAgentFunctions::InstallOmAgentMsi : Leaving
10:47:07 AM : OmAgentFunctions::InstallOmAgent : MsiInstall(OpInstall) failed. HResult: 80070643
10:47:07 AM : OmAgentFunctions::InstallOmAgent : Leaving
10:47:15 AM : CServiceModule::SetServiceStatus : State: 3, Error: 0
10:47:15 AM : CServiceModule::SetServiceStatus : State: 3, Error: 0
10:47:15 AM : IsCurrentMOMServerInstalled : MOM Setup key could not be opened.
10:47:15 AM : CServiceModule::_RegisterFile : Before LoadLibrary
10:47:15 AM : CServiceModule::_RegisterFile : After LoadLibrary
10:47:15 AM : CServiceModule::_RegisterFile : Before GetProcAddress
10:47:15 AM : CServiceModule::_RegisterFile : After GetProcAddress
10:47:15 AM : CServiceModule::_RegisterFile : After FreeLibrary
10:47:15 AM : CServiceModule::RegisterFile : Success return
10:47:15 AM : CServiceModule::RegisterFile : WaitForSingleObject return HResult: 0
10:47:15 AM : CServiceModule::SetServiceStatus : State: 1, Error: 0

Answer 1

Hi HosseinBagheri-2140,

Thank you for posting your query.

Kindly follow the steps provided below to resolve your issue.

In SCOM 2019 there have been security changes, it now requires the account that pushes SCOM agents to be a member of the Log on as a Service.

Open the Local Security Policy on the SCOM management server, go to Local Policies > User Rights Assignment and find Log on as a service and add the account to the Log on as a service group and then try pushing the SCOM agent again.

Go to this link for your reference

https://social.technet.microsoft.com/wiki/contents/articles/53476.scom-troubleshooting-windows-agent-installation.aspx

--------------------------------------------------------------------------------------------------------------------------------------------

If the answer is helpful kindly click "Accept as Answer" and upvote it. Thanks.

Answer 2

HI @Hossein Bagheri ,

imho this issue is not related to ann update, at least not in the classical scenario. I have many different customers, who are all up to date with all update from Microsoft and they do not have this particular issue. In order to try to narrow down the cause for this catastrophic afilure (Windows Installer installed the product. Product Name: Microsoft Monitoring Agent. Product Version: 10.22.10056.0. Product Language: 0. Manufacturer: Microsoft Corporation. Installation success or error status: 1603.) I have to ask some additional questions:

• Are you doing "Push Install" or mauall install (SCCM, GPO, MOMAgent.msi)?
• Can you reproduce the issue on multiple systems?
• Since when does it occur?
• Does the Server has an AV software installed?
• Very important: Are you doing the install with admin privileges?
• What account are you using for the Agent Action Account: a domain account or "Local System"?

Can you please provide some more details here?

Thanks and regards,
Stoyan

Answer 3

Hi,

Could you check if there's any log generated in client Operations Manager event log. It is under Applications and Services Logs->Operations Manager. Maybe it can give us some clues.

For example: