Различия

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

--- microsoft-system-center:operations-manager [12.11.2022 14:54] – [Использование механизма оповещений] Алексей Максимов
+++ microsoft-system-center:operations-manager [01.09.2025 12:38] (текущий) – [Решение проблем] Алексей Максимов
@@ Строка 8: / Строка 8: @@
 ==== Версионность ====
-  * [[https://buildnumbers.wordpress.com/scom/|SCOM build numbers]]
+  * [[https://buildnumbers.wordpress.com/scom/|SCOM Builds : MOM 2000 - SCOM 2019]]
+  * [[https://thesystemcenterblog.wordpress.com/scom-build-versions/|SCOM Builds : SCOM 2007 - SCOM 2025]]
@@ Строка 22: / Строка 23: @@
   * [[https://blog.it-kb.ru/2013/01/25/problems-after-system-center-2012-operations-manager-scom-opsmgr-upgrage-update-migrate-move-databases-on-another-sql-server/|SCOM 2012 SP1 - Настройка SQL Server после восстановления БД]]
   * [[https://blog.it-kb.ru/2013/01/23/deployment-system-center-2012-operations-manager-sp1-opsmgr-scom-console-with-configmgr-sccm-2012/|SCOM 2012 SP1 - Развёртывание консоли управления SCOM с помощью SCCM 2012]]
-  * [[https://blog.it-kb.ru/2013/11/08/upgrade-system-center-2012-sp1-operations-manager-to-sc-2012-r2-update-opsmgr-scom-in-single-server-management-group/|SCOM 2012 SP1 - Обновляем SCOM до уровня System Center 2012 R2 (в конфигурации Single-server management group)]]
+  * [[https://blog.it-kb.ru/2013/11/08/upgrade-system-center-2012-sp1-operations-manager-to-sc-2012-r2-update-opsmgr-scom-in-single-server-management-group/|SCOM 2012 SP1 - Обновление до уровня System Center 2012 R2 (Single-server management group)]]
   * [[https://kevinholman.com/2016/10/22/opsmgr-2016-quickstart-deployment-guide/|SCOM 2016 - Руководство по развёртыванию от Kevin Holman]]
   * [[https://kevinholman.com/2022/05/01/scom-2022-quickstart-deployment-guide/|SCOM 2022 - Руководство по развёртыванию от Kevin Holman]]
@@ Строка 97: / Строка 98: @@
 ----
-==== Механизмы оповещений SCOM ====
+==== Механизмы оповещений ====
   * [[https://blog.it-kb.ru/2012/10/03/system-center-2012-operations-manager-scom-sms-notifiaction-subscription/|SCOM 2012 - Настраиваем SMS оповещения]]
@@ Строка 103: / Строка 104: @@
 ----
-==== Оптимизация производительности SCOM ====
+==== Производительность SCOM ====
   * [[http://blogs.technet.com/b/kevinholman/archive/2010/01/05/understanding-and-modifying-data-warehouse-retention-and-grooming.aspx|Understanding and modifying Data Warehouse retention and grooming [Kevin Holman]]]
@@ Строка 129: / Строка 130: @@
   * [[https://blog.it-kb.ru/2014/02/03/system-center-2012-r2-operations-manager-scom-opsmgr-console-operations-manager-cannot-connect-to-the-web-service-the-microsoft-management-pack-catalog-web-service-cannot-be-contacted-at-this-time/|SCOM 2012 R2 - Operations Manager cannot connect to the Web service - The Microsoft Management Pack Catalog Web Service cannot be contacted at this time]]
   * [[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/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]]