![]() ![]() Pushing the agent out from the 2016 MG would have meant that the 2016 UR2 agent would have been deployed. This work was carried out using Kevin Holman’s Agent Management MP (now SCOM Management) as it has a nice task of adding the existing agent to another Management Group. ![]() We could then upgrade the agent to 2016 when the fix was released. The SCOM Team decided that utilising the existing 2012 R2 agent that was already on the server was a better option and initially have the agent dual homed to both management groups. To do the install with the recommended NOAPM switch would have meant manually installing the agent on hundreds of servers. SCOM 2016 Agent can be reinstalled with NOAPM=1 switch in msiexec.exe setup command line, APM feature will be excluded from setup.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. ![]() On the 6th June they blogged about workarounds that could be used until a fix was released as UR3 still had problems. The System Center Operations Manager team blogged about the issue on 31st May. Net Application Pools crashing with UR2 we decided to wait until UR3 but that did not fix the problem. As we saw posts showing that there were issues with APM and. We had built a new SCOM 2016 Management Group alongside the existing 2012 R2 UR11 one in order to dual home and test before switching over. SCOM 2012 R2 Agent Shows APM/App Pool Crashes in 2016 MG ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |