The first walk-through will perform an in-place repair on an existing agent to save you from having to uninstall the agent first. In the following steps, I'll walk you through a process to remove the APM feature on the SCOM 2016 agent using the command line. If you use the command line to install your SCOM agents, you can specify a parameter that removes the APM feature from the agent installation (check out this link for command line options) and I figured this was the best place to start as the IIS server in question didn't require the APM feature. We needed to dig deeper to see how we could continue monitoring this server using SCOM without having the IIS Application Pools crashing and as the faulting module path in the Event Log error referenced the APM component, I decided to focus here first. The weird thing about this particular IIS crashing issue though was that the APM feature was never enabled. A number of our customers also use this feature and it's always been very successful. I've previously blogged about SCOM APM, presented on it at conferences and even wrote a chapter in the Mastering SCOM 2012 R2 book about it. APM is typically enabled through the SCOM console on a server-by-server basis and delivers some really nice DevOps scenarios for monitoring.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |