I recently wrote an article about an issue that came to the fore a few months ago relating to how the Application Performance Monitoring (APM) feature in SCOM 2016 agent causes IIS Application pools running under the .NET Framework 2.0 runtime to fail. See the article here: http://www.mrchiyo.com/scom-2016-apm-linked-to-iis-application-pool-failures/. It was expected that a definitive fix for this issue would ship with Update rollup 3 for SCOM 2016. However, update rollup 3 (UR3) for SCOM 2016 was released a few days ago, but it does not appear to have a definitive fix for this issue. See the official update notes here: https://support.microsoft.com/en-us/help/4016126/update-rollup-3-for-system-center-2016-operations-manager MICROSOFT RECOMMENDED WORKAROUNDS: Instead of a definitive fix, the Microsoft product team has highlighted various deployment scenarios, and … Read More
OMS Agent for Linux – v1.3.5-127
Version 1.3.5-127 of the OMS Agent for Linux is now generally available. This update introduces a bug fix but no new features. Bug Fix Python ctypes module detection fix to be able to run omsagent installer on SELinux policy enabled systems. SOURCE: Github Install OMS Agent for Linux – v1.3.3-15 For x86 Architecture (32-bit) systems:
|
1 2 3 |
cd ~ wget https://github.com/Microsoft/OMS-Agent-for-Linux/releases/download/OMSAgent-201705-v1.3.5-127/omsagent-1.3.5-127.universal.x86.sh sudo bash omsagent-1.3.5-127.universal.x86.sh --upgrade -w <WORKSPACE_ID> -s <SECRET_KEY> |
For x64 Architecture (64-bit) Systems
|
1 2 3 |
cd ~ wget https://github.com/Microsoft/OMS-Agent-for-Linux/releases/download/OMSAgent-201705-v1.3.5-127/omsagent-1.3.5-127.universal.x64.sh sudo bash omsagent-1.3.5-127.universal.x64.sh --upgrade -w <WORKSPACE_ID> -s <SECRET_KEY> |
Where WORKSPACE_ID Is the ID for your OMS workspace, and the SECRET_KEY is the relevant key for your OMS workspace. To determine your OMS workspace ID and primary key: Sign into your OMS Workspace From the Overview page, click on Settings In the Settings page, click on Accounts -> Workspace Information. Cheers!
OMS Agent for Linux – v1.3.4-127
The latest release of the OMS Agent for Linux is generally available. This update introduces a new version of Docker provider (version 1.0.0-23), as well as a few bug fixes. New Features Docker provider version 1.0.0-23 Fixes nxOMSGenerateInventory DSC resource memory corruption fix. Installing tar/sed through OS vendor program. syslog-ng unconfigure fix. NPM bug fixes and improvements. nxAutomationWorker DSC resource bug fixes. SOURCE: Github Install OMS Agent for Linux – v1.3.4-127 For x86 Architecture (32-bit) systems:
|
1 2 3 |
cd ~ wget https://github.com/Microsoft/OMS-Agent-for-Linux/releases/download/OMSAgent-201705-v1.3.4-127/omsagent-1.3.4-127.universal.x86.sh sudo bash omsagent-1.3.4-127.universal.x86.sh --upgrade -w <WORKSPACE_ID> -s <SECRET_KEY> |
For x64 Architecture (64-bit) systems:
|
1 2 3 |
cd ~ wget https://github.com/Microsoft/OMS-Agent-for-Linux/releases/download/OMSAgent-201705-v1.3.4-127/omsagent-1.3.4-127.universal.x64.sh sudo bash omsagent-1.3.4-127.universal.x64.sh --upgrade -w <WORKSPACE_ID> -s <SECRET_KEY> |
Where WORKSPACE_ID Is the ID for your OMS workspace, and the SECRET_KEY is the relevant key for your OMS workspace. To determine your OMS workspace ID and primary key: Sign into your OMS Workspace From the Overview … Read More
OMS Agent for Linux – v1.3.4-15
The latest release of the OMS Agent for Linux is now available. This version introduces a few bug fixes but no new features. Fixes Persist conf and certs for OMSAgentForLinux VM extension upgrade scenarios. Persist agentID in upgrade to same workspace scenarios. Improve error codes in omsagent bundle installer. omsagent directory clean up when omsagent bundle is used with –remove option. Source: Github Install OMS Agent for Linux – v1.3.4-15 For x86 Architecture (32-bit) Systems
|
1 2 3 |
cd ~ wget https://github.com/Microsoft/OMS-Agent-for-Linux/releases/download/OMSAgent-201704-v1.3.4-15/omsagent-1.3.4-15.universal.x86.sh sudo bash omsagent-1.3.4-15.universal.x86.sh --upgrade -w <WORKSPACE_ID> -s <SECRET_KEY> |
For x64 Architecture (64-bit) Systems
|
1 2 3 |
cd ~ wget https://github.com/Microsoft/OMS-Agent-for-Linux/releases/download/OMSAgent-201704-v1.3.4-15/omsagent-1.3.4-15.universal.x64.sh sudo bash omsagent-1.3.4-15.universal.x64.sh --upgrade -w <WORKSPACE_ID> -s <SECRET_KEY> |
To determine your OMS workspace ID and primary key: Sign into your OMS Workspace From the Overview page, click on Settings In the Settings page, click on Accounts -> Workspace Information. Cheers!
Application Discovery and Mapping with OMS Service Map
The Service Map solution in Microsoft Operations Management Suite (OMS) is now generally available. Service Map discovers components of applications running on both Windows and Linux systems, and intuitively maps the communication between the services. This capability enables you to view the connections that affect your systems, and better understand the relationships between the various components of your distributed applications. IMAGE SOURCE: TechNet The benefits are many and include discovery of your application and system components, incident management and root cause analysis, migration assurance, patch management, and BCDR strategy and planning. You can read more about its capabilities in the official Service Map articles. It is worth noting that the concept of Application Dependency Mapping (ADM) and attendant capabilities is … Read More
OMS Agent for Linux – v1.3.3-15
The latest release of the OMS Agent for Linux is available on Github. This update builds upon the new features and bug fixes made to v1.3.2-15 of the OMS Agent for Linux. New Features Newest Apache CIM provider 1.0.1-9 (Introduced in v1.3.2-15) Fixes Docker versioning fix. (Introduced in v1.3.2-15) Container buffer and Docker segfault fix. (Introduced in v1.3.2-15) SCX/OMI dependent package compatibility fix for OMSAgentForLinux and LinuxAsm VM extensions. Install OMS Agent for Linux – v1.3.3-15 For x86 Architecture (32-bit) systems:
|
1 2 3 |
cd ~ wget https://github.com/Microsoft/OMS-Agent-for-Linux/releases/download/OMSAgent-201704-v1.3.3-15/omsagent-1.3.3-15.universal.x86.sh sudo bash omsagent-1.3.3-15.universal.x86.sh --upgrade -w <WORKSPACE_ID> -s <SECRET_KEY> |
For x64 Architecture (64-bit) Systems
|
1 2 3 |
cd ~ wget https://github.com/Microsoft/OMS-Agent-for-Linux/releases/download/OMSAgent-201704-v1.3.3-15/omsagent-1.3.3-15.universal.x64.sh sudo bash omsagent-1.3.3-15.universal.x64.sh --upgrade -w <WORKSPACE_ID> -s <SECRET_KEY> |
Where WORKSPACE_ID Is the ID for your OMS workspace, and the SECRET_KEY is the relevant key for your OMS workspace. To determine your OMS workspace ID and primary key: Sign into … Read More
Migrating from Mixed Mode AD FS to a Full Windows Server 2016 AD FS Farm
I recently designed a solution to provide AD FS high availability for a client, using Azure IaaS and PaaS. This necessitated deploying Windows Server 2016 AD FS servers to a Windows Server 2012 R2 farm in order to align with desired DR testing plan, and accommodate downtime schedules. This article will review the specific steps for making the cutover from a mixed mode AD FS environment to a full Windows Server 2016 AD FS farm. It will not go into detail about installing the AD FS roles. At the time of writing this article, adding Windows Server 2016 AD FS servers to a Windows Server 2012 R2 farm in a so-called “mixed-mode” scenario is fully supported, and you can subsequently … Read More
SCOM 2016 APM Linked to IIS Application Pool Failures.
****UPDATES: See update notes at bottom of the page. I recently encountered an issue where a client running a couple of SharePoint (SP) 2013 Farms was starting to see service failures across the board which adversely affected the availability of their sites. Prior to these failures, this client had recently upgraded their SCOM 2012 R2 environments to SCOM 2016, but there’s no definitive indication of causality as it relates to the SCOM upgrade. This article will provide an in-depth review of the issue, and a tested workaround. I’ll also update it with any new information that the Microsoft product group brings to light. The Issue: Firstly we determined that the affected sites were based on legacy IIS application pools … Read More
OMS Agent for Linux – v1.3.1-15
The latest release of the OMS Agent for Linux is available on Github. This update introduces version 1.2.0-1 of the Open Management Infrastructure (OMI), as well as a few bug fixes. New features OMI version 1.2.0-1 Fixes Log rotation for SELinux-enabled machines Fluentd in_exec patch to resolve security_baseline.conf error explosions Log file size limitation fix to allow up to 100MB log file and up to 10 log files. Segfault error due to libcontainer.so Install OMS Agent for Linux – v1.3.1-15 For x86 Architecture (32-bit) system:
|
1 2 3 |
cd ~ wget https://github.com/Microsoft/OMS-Agent-for-Linux/releases/download/OMSAgent-201702-v1.3.1-15/omsagent-1.3.1-15.universal.x86.sh sudo bash omsagent-1.3.1-15.universal.x86.sh --upgrade -w <WORKSPACE_ID> -s <SECRET_KEY> |
For x64 Architecture (64-bit) System:
|
1 2 3 |
cd ~ wget https://github.com/Microsoft/OMS-Agent-for-Linux/releases/download/OMSAgent-201702-v1.3.1-15/omsagent-1.3.1-15.universal.x64.sh sudo bash omsagent-1.3.1-15.universal.x64.sh --upgrade -w <WORKSPACE_ID> -s <SECRET_KEY> |
Where WORKSPACE_ID Is the ID for your OMS workspace, and the SECRET_KEY is the relevant key for your OMS workspace. To determine your OMS workspace ID and primary … Read More
SCOM 2016 Certificate Errors. Event ID 20049
In this article, I’ll review SCOM Certificate Event ID 20049. This error event can be seen during an attempt to initiate mutual authentication across untrusted boundaries such as in a gateway or workgroup boundary scenario. In SCOM, certificates will need to be used for mutual authentication between the management servers and any gateway servers/ agents when Kerberos-based mutual authentication is not possible. If there’s an issue with the certificate, mutual authentication will fail, and one of the errors you could likely encounter is as shown below: The event detail reads: “The specified certificate could not be loaded because the key Usage specified does not meet OpsMgr requirements. The certificate must have the following usage types: Digital Signature, Key Encipherment.” This … Read More