Различия

Показаны различия между двумя версиями страницы.

--- microsoft-system-center:operations-manager [15.06.2023 12:59] – [Установка и обновление] Алексей Максимов
+++ microsoft-system-center:operations-manager [01.09.2025 12:38] (текущий) – [Решение проблем] Алексей Максимов
@@ Строка 9: / Строка 9: @@
   * [[https://buildnumbers.wordpress.com/scom/|SCOM Builds : MOM 2000 - SCOM 2019]]
-  * [[https://thesystemcenterblog.wordpress.com/scom-build-versions/|SCOM Builds : SCOM 2007 - SCOM 2022]]
+  * [[https://thesystemcenterblog.wordpress.com/scom-build-versions/|SCOM Builds : SCOM 2007 - SCOM 2025]]
@@ Строка 131: / Строка 131: @@
   * [[https://blog.it-kb.ru/2016/01/14/error-in-discovery-progress-of-linux-computer-management-wizard-opsmgr-scom-with-install-operations-manager-agent-to-hp-vsp-4-4-rhel-6-1-failed-during-ssh-discovery-exit-code-1073479115-ssh-connection/|SCOM 2012 R2 - Ошибка при работе мастера обнаружения SCOM при подключении к HP VSP 4.4 (RHEL 6.1) - Failed during SSH discovery. Exit code: -1073479115]]
   * [[https://blog.it-kb.ru/2023/01/19/domain-controller-discovery-error-in-scom-2016-discovery-wizard-discovery-failed-there-were-no-computers-discovered-that-met-your-criteria-computer-verification-failure-0x80070005-access-is-denied/|SCOM 2016 - Ошибка обнаружения контроллеров домена "Discovery failed. There were no computers discovered that met your criteria … Computer verification failure 0x80070005. Access is denied"]]
-  * [[https://blog.it-kb.ru/2023/06/12/multiple-events-with-event-id-32-failed-to-look-up-debug-info-for-provider-unknown-ntstatus-error-code-in-kernel-eventtracing-event-log-after-installing-scom-agent-on-windows-server-2022/|Предупреждения Event ID 32 "Failed to look up debug info for provider…Unknown NTSTATUS Error code" в event-логе Kernel-EventTracing после установки агента SCOM на Windows Server 2022]]
+  * [[https://blog.it-kb.ru/2025/09/01/system-center-2016-operations-manager-active-directory-dc-agent-the-health-service-blocked-access-to-the-windows-credential-nt-authority-system-because-it-is-not-authorized-on-management-group/|SCOM 2016 - Ошибка агента SCOM на контроллере домена "The health service blocked access to the windows credential NT AUTHORITY\SYSTEM because it is not authorized on management group"]]
+  * [[https://blog.it-kb.ru/2023/06/12/multiple-events-with-event-id-32-failed-to-look-up-debug-info-for-provider-unknown-ntstatus-error-code-in-kernel-eventtracing-event-log-after-installing-scom-agent-on-windows-server-2022/|SCOM 2022 - Event ID 32 "Failed to look up debug info for provider…Unknown NTSTATUS Error code" в event-логе Kernel-EventTracing после установки агента SCOM на Windows Server 2022]]
+  * [[https://blog.it-kb.ru/2025/08/27/system-center-2022-operations-manager-health-service-heartbeat-failure-and-failed-to-connect-to-computer-errors-for-already-removed-scom-agent/|SCOM 2022 - Ошибки "Health Service Heartbeat Failure" и "Failed to Connect to Computer" для уже удалённого агента SCOM]]