/* * These styles apply ONLY to the header and footer assets. */ * { padding: 0; margin: 0; box-sizing: border-box; } .super-nav { display: flex; justify-content: flex-end; align-items: center; margin: 0 auto; max-width: 1264px; padding-left: 40px; padding-right: 40px; height: 40px; text-align: right; } .super-nav a { color: #34427c; margin-right: 20px; padding: 10px; text-decoration: none; } .super-nav a:hover, .super-nav a:focus { background-color: #f7f9fa; } .footer { background: #f5f5f6; color: #555a62; font-size: 14px; line-height: 1.5; padding: 0; } .footer-image { background-image: url("/themes/kaseya/assets/images/footerImage.png"); height: 500px; background-repeat: no-repeat; background-size: cover; margin-top: -100px; } .footer-wrap { padding-left: 18px; padding-right: 18px; max-width: 1236px; margin: 0 auto; } .footer-main-content { background-color: #000; padding: 100px 0; } .footer .footer-col-title { color: #ffffff; font-weight: 700; font-size: 13px; padding-bottom: 10px; text-transform: uppercase; } .footer .footer-link { color: #9b9ca0; text-decoration: none; } .footer .footer-link:hover, .footer .footer-link:focus, .footer .footer-link:active { text-decoration: underline; } .footer-main-content .footer-link { padding-top: 10px; } .footer-row { display: flex; flex-wrap: wrap; justify-content: space-between; align-items: center; margin: -3px; } .footer-main-content-row { align-items: flex-start; } .footer-bottom-content { padding: 10px; align-items: center; } .footer-col { padding: 0 3px; display: flex; flex-direction: column; } .footer-col-copyRight { justify-content: flex-start; color: #9b9ca0; flex: 1; display: flex; } .footer-last-col { flex-direction: row; } .footer-last-col .footer-link { padding-right: 10px; text-transform: uppercase; } @media screen and (max-width: 768px) { .super-nav { padding-right: 0; } .footer-image { height: 250px; } .footer-main-content { padding: 40px 0; } .footer .footer-col-title { padding-top: 10px; } .footer-row:not(.footer-main-content-row) { display: block; } .footer-col:not(.footer-main-content-col) { width: 100%; text-align: center; padding: 10px 0; } .footer-main-content-col { width: 50%; } .footer-last-col { flex-direction: column; } .footer-last-col .footer-link { padding-bottom: 10px; } } /*# sourceMappingURL=styles.css.map */ Ask the Community Groups

VSAX Server Modules

How to enable and configure the System Center Operations Manager monitoring

System Center Operations Manager (SCOM) is a cross-platform management system for operating systems and hypervisors. It uses a single interface that shows state, health and performance information of computer systems. SCOM provides alerts generated according to some availability, performance, configuration or identifying security situations. It works with Microsoft Windows Server and Unix-based hosts.

SDK Installation:

Before you can start monitoring your SCOM deployment you need to copy the SDK (Software Development Kit) from the Management Group Server to your VSAX installation directory.

You can find the SDK assemblies at %ProgramFiles%\System Center 2012\Operations Manager\Server\SDK Binaries.

Required assemblies:

Microsoft.EnterpriseManagement.Core.dll
Microsoft.EnterpriseManagement.Runtime.dll
Microsoft.EnterpriseManagement.OperationsManager.dll

Note: VSAX Service and Manager must be restarted for the SCOM SDK installation to be detected.

Connection Settings:

In order to connect you must fill in the configuration details in VSAX Manager.
Server Name: FQDN or IP address of the management group server
Use Windows Authentication: If checked VSAX will connect to SCOM using the LocalSystem account.

Domain: NETBIOS name of the domain
Username: User with access to the SCOM Console
Password: The password for the user

How to enable Notifications for the System Center Operations Manager monitoring

SCOM module can notify whenever an alert triggers or reaches warning state.