SCOM Agent Installation Instructions

Step 1 – Client System Requirements

1. Approximately 500MBs of available free disk space.

2. Windows Server 2012 or higher.

3. .Net Framework 4.7.2 or higher

   1. https://learn.microsoft.com/en-us/dotnet/framework/migration-guide/how-to-determine-which-versions-are-installed

4. Check with PowerShell

   (Get-ItemProperty -Path ‘HKLM:\SOFTWARE\Microsoft\Net Framework Setup\NDP\v4\Full’).Release

Release property needs to be 461308 or higher.

Step 2 – Test Network Communication

Expedient’s monitoring platform utilizes public internet communication. Client Systems must be able to reach the Management Servers on TCP port 5723.

• 810-ShrdMS01.monitorexp.cloud - 206.210.74.160

• 810-ShrdMS02.monitorexp.cloud - 206.210.74.161

To test network connectivity to our monitoring platform with PowerShell:

Test-NetConnection -ComputerName “810-ShrdMS01.monitorexp.cloud” -Port 5723

The Monitoring Agent software must be able to resolve these management servers by name. Systems with limited DNS may need host file entries to resolve.

Step 3 – Download Monitoring Agent Installer

• Monitoring Agent installer is available from Expedient’s public download site:

https://download.expedient.com/scom/
Username: expedient
Pass: publ1c

• Download the ScomAgent.zip file and extract the contents to C:\Staging\ScomAgent.

• The installation commands are dependent upon the extracted content being in the folder C:\Staging\ScomAgent on the Client System. If placed in a different path, the installation commands will need to be altered.

Step 4 – Install the Monitoring Agent and Update Rollup

• Install the Monitoring Agent with PowerShell (Administrative session):

• Set MS Variable:

[string]$mgmtSvr = "810-ShrdMS01.monitorexp.cloud"

• Set Install Parameter Variable:

[Array]$ScomArgs = @("/i", "C:\Staging\ScomAgent\MOMAgent.msi", "/passive", "/norestart", "/l*v", "C:\Staging\ScomAgent\MOMAgentInstall.log", "Use_Settings_From_AD=0", "Management_Group=MonExp", "Management_Server_DNS=$mgmtSvr", "Actions_Use_Computer_Account=1", "Use_Manually_Specified_Settings=1", "Set_Actions_Account=1", "NoAPM=1", "AcceptEndUserLicenseAgreement=1")

• Run the installer:

Start-Process -Wait -NoNewWindow -FilePath msiexec.exe -ArgumentList $ScomArgs

• Install the SCOM Agent Update Rollup (UR1):

C:\Staging\ScomAgent\UR1\KB5020318-amd64-Agent.msp /quiet

Step 5 – Install Certificates

• Certificates are used to secure communication to the Management Servers. There are two certificates. PFX certificate (personal certificate) is unique to each Client System. CER certificate (root certificate) is the same for all Client Systems. These certificates are provided by Expedient. The certificate files (.pfx and .cer) should be placed in the C:\Staging\ScomAgent folder.

• Install the certificates from an administrative PowerShell prompt:

  • The installation commands are dependent upon the certificates being in the C:\Staging\ScomAgent folder on the Client System. If saved to a different path, these commands will need to be altered.

• Install CER (root cert):

Import-Certificate -FilePath "C:\Staging\ScomAgent\MonExp-CA-root.cer" -CertStoreLocation Cert:\LocalMachine\Root

• Install PFX (personal cert):

C:\Staging\ScomAgent\MOMCertImport.exe ("C:\Staging\ScomAgent\" + (Get-WmiObject -Class win32_computersystem).DNSHostName + '.' + (Get-WmiObject -Class win32_computersystem).Domain + '.pfx') /Password "password"

Special Step – Domain Controllers and Exchange Servers

Domain Controllers and Exchange Client Systems require an additional module and permissions to monitor AD and Exchange.

• Install the OOMADs module and set additional permissions from an administrative PowerShell prompt:

  • The install command is dependent upon the OOMADs.msi file in the C:\Staging\ScomAgent folder. Adjust the command accordingly if OOMADs.msi file is in another location.

• Install Module (OOMADs):

Start-Process -Wait -NoNewWindow -FilePath msiexec.exe -ArgumentList ("/i", "C:\Staging\ScomAgent\OOMADs.msi", "/quiet")

• Set Additional Permissions:

CD "C:\Program Files\Microsoft Monitoring Agent\Agent\"
.\HSLockdown.exe /A "NT Authority\System"

• Restart Monitoring Agent service:

Restart-Service HealthService

Last Step – Engage Expedient for Client Approval

Once the Monitoring Agent, both certificates, and the OOMADs module (if required) have been installed, notify Expedient to approve the Client System and begin monitoring.

The Operations Manager log (Event Viewer -> Applications and Services -> Operations Manager) will throw communication errors "OpsMgr Connector could not connect to scom management server name", "connection was actively refused", or "connection was made but was immediately closed” until approved by Expedient.