SCOM (Anglais)

Work around for installing SC 2016 OM console and SC 2016 SM console on the same server

Microsoft Operations Manager and OMS -

Following is the work around for installing SC 2016 OM console and SC 2016 SM console on the same server:

  1. Install SC 2016 OM console and then install SC 2016 SM console on the same server
  2. Add system environment variable DEVPATH which contains folder path of the Microsoft.EnterpriseManagement.Core.dll with the value “C:\Program Files\Microsoft System Center 2016\Operations Manager\Console\SDK Binaries”
  3. Add following highlighted entry in the config file (C:\Program Files\Microsoft System Center 2016\Operations Manager\Console\Microsoft.EnterpriseManagement.Monitoring.Console.exe.config)

                              <configuration>

                              ….

                             <runtime>

                            <developmentMode developerInstallation=”true” />

                            </runtime>

                            ….

                           </configuration>

  With above modifications both the consoles will co-exist on the same server.

 

Inbox MP hotfix for WMI health monitor

Microsoft Operations Manager and OMS -

In SCOM 2016, when the support for Nano was introduced, a regression caused issue in functioning of the WMI health monitor. This issue was hit only when

  • WinRM was configured to use https only
  • The Service Principal Name was registered to set http/servername to a user account

The issue has been fixed, the protocol used by the script that was causing the failure has been modified to use the DCOM protocol as in SCOM 2012 R2. We have released the inbox MP package here.

Installation Steps- Import the .msi package on to the SCOM 2016 machine and install the files. If the MPs already exists, they will be upgraded with the latest files.
The package has 2 inbox MPs, their names and versions are given below

  • Microsoft.SystemCenter.2007.mp – 7.2.11907.0
  • Microsoft.SystemCenter.Internal.mp 7.0.8437.10

Service Map management pack in public preview

Microsoft Operations Manager and OMS -

Have you ever tried to use Distributed Applications in Operations Manager, but got frustrated with the manual process of creating the diagrams? They can be difficult to create and harder to maintain in modern, dynamic systems.

Wouldn’t it be great if those diagrams could be built and maintained for you automatically? With the public preview of the new Service Map management pack, that reality is here.

Service Map is an Azure service automatically discovers application components on Windows and Linux systems and maps the communication between services. You can create diagrams for individual servers or complex maps of groups of servers representing your business services.

 

With this new integration, you can take the dynamic maps that Service Map creates and have them automatically create and maintain your Distributed Application Diagrams in Operations Manager. As your business services change, your diagrams will change along with them. Now, you can set up dashboards showing the health of your services and trust that the underlying Distributed Applications represent the real-world infrastructures, even as they change.

 

For more information, look at the online documentation or download the management pack and try it out for yourself.

We’d love your feedback on this new feature. Feel free to send me an email at david.irwin@microsoft.com.

– David Irwin

Update on APM fix for agent crashing issue shipped in UR3

Microsoft Operations Manager and OMS -

Overview of the .NET 2.0 fix that was shipped in UR3

We have been investigating this issue actively and this fix has not solved the issue completely. We are actively working to resolve the issue and release a hotfix soon.

Workarounds:

  • SCOM 2016 Agent can be replaced with SCOM 2012 R2 Agent, it’s forward-compatible with SCOM 2016 Server and APM feature will continue to work with the older bits
  • SCOM 2016 Agent can be reinstalled with NOAPM=1 switch in msiexec.exe setup command line, APM feature will be excluded from setup

 

Additional issues along with the workaround

SharePoint Central Administration site stops working when SCOM 2016 Agent is installed onto the server

  • Although SCOM 2016 Agent installs APM component in the disabled state by default, it adds a registry setting to load inactive APM into IIS Application pools
  • If APM is not yet configured for this server, those application pools will only have APM loaded in inactive state without any monitoring
  • The issue has been reported that inactive APM may crash SharePoint Central Administration v4 application pool and prevent this application from starting

Workarounds:

  • If APM feature is required on that server: downgrade SCOM Agent to 2012 R2 and continue monitoring;
  • If APM feature is not required on that server: keep SCOM 2016 Agent and re-install it with “NOAPM=1” in the setup command line

 

Web Site crashes during startup when SCOM 2016 Agent is installed onto the server

  • Although SCOM 2016 Agent installs APM component in the disabled state by default, it adds a registry setting to load inactive APM into IIS Application pools.
  • If APM is not yet configured for this server, those application pools will only have APM loaded in inactive state without any monitoring.
  • If application pool account has no access to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\System Center Operations Manager\12\APMAgent registry key, inactive APM won’t be able to read that key and this application pool process may crash.

Workaround:

  • Add “Read” access permission for the application pool account to: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\System Center Operations Manager\12\APMAgent

APM fix for agent crashing issue shipped in UR3 is not completely resolved

Microsoft Operations Manager and OMS -

The Application Performance Monitoring (APM) feature in System Center 2016 Operations Manager Agent causes a crash for the IIS Application Pool that’s running under the .NET Framework 2.0 runtime. A fix for this issue was made in UR3, however the fix does not seem to solve the issue completely. We are investigating this issue and we would be releasing a hotfix with a resolution soon.

S'abonner à Philippe BARTH agrégateur - SCOM (Anglais)