ты пошем смотрел?

Get-SCOMPendingManagement | where {$_.AgentPendingActionType -eq "ManualApproval"} | Approve-SCOMPendingManagement

ну это поменяй на имя и убедись что его нет или есть, если есть, то пошем аппрув делай

FYI

Всегда запускайте патчи run as administrator

There is a post-installation procedure in the KBxxxxxxx-AMD64-Server.msp, at the end of the process, that runs in an elevated process and sets applicable agents into pending for an update.  This ONLY runs with success, IF:

 

The user called the KBxxxxxxx-AMD64-Server.msp file from an ELEVATED CMD Prompt.

The user who called it is a SCOM Admin, Local Administrator of the OS, and SQL Sysadmin role level rights in SQL.

The agents expected to show up in pending are flagged as “Remotely Manageable” = Yes

The agents will only be placed into pending, that are assigned to the management server that you just patched.

 

If the customer used Windows Update for the server patch – this won’t work.

•2000 network devices (approximately 25,000 monitored ports) managed by two resource pools


•1000 network devices (approximately 12,500 monitored ports) managed by a resource pool that has three or more management servers


•500 network devices (approximately 6,250 monitored ports) managed by a resource pool that has two or more gateway servers

Откуда это?

с сайта мс выдрал

бляха муха

ща все перепробвал

UPS от APC не детектит по SNMP

icmp и хули он мне даст?!

Initialization of a module of type "SnmpWalkWA" (CLSID "{C3713D4D-B1FF-4835-A644-8EF774830FA2}") failed with error code The file exists. causing the rule "System.NetworkManagement.Monitoring.SnmpWalkTask" running for instance

создал новый пул

проверил доступ

Ты по какому часовому поясу живёшь?

переделал discovery.conf раз 300 все фичи так сказать тестил

по мск

Спать иди  :)