Support Tip: Some Microsoft Operations Manager Management Packs Require Proxy Configuration

Published Feb 16 2019 03:46 AM 413 Views
First published on TECHNET on Aug 25, 2016
Hi everyone, my name is Mihai Sarbulescu and today I wanted to share a quick support tip with you. Please be aware that some Management Packs for Microsoft System Center Operations Manager have workflows that need to connect to the Internet in order to perform various actions. The Office 365 Management Pack is a good example of this as it needs to connect to the Internet to complete certain actions related to discovery and monitoring. In such situations, if a proxy server is needed to connect to the Internet from the System Center Operations Manager Management Servers, the proxy configured in Internet Explorer or WinHTTP will not be taken into account by the System Center Operations Manager processes - here MonitoringHost.exe processes which are running the actual workflows.

In order to configure the correct proxy server, the MonitoringHost.exe.config file needs to be modified on all management servers from the All Management Servers Resource Pool . The MonioringHost.exe.config file can be found in the System Center Operations Manager installation folder under %ProgramFiles%\Microsoft System Center 2012\Operations Manager\Server\ . Make a backup of the MonitoringHost.exe.config file and then add these lines in the < configuration > section of the config XML:

<system.net>
<defaultProxy enabled="true" useDefaultCredentials="true">
<proxy proxyaddress="http://<PROXYADDRESS>:<PORT>" bypassonlocal="true" />
<bypasslist>
</bypasslist>
</defaultProxy>
</system.net>

Make sure that you replace < PROXYADDRESS > with the correct proxy server address and < PORT > with the correct proxy server port. When done, simply save the MonitoringHost.exe.config file and close it and you’re all set.

Mihai Sarbulescu | Escalation Engineer | Microsoft
%3CLINGO-SUB%20id%3D%22lingo-sub-351587%22%20slang%3D%22en-US%22%3ESupport%20Tip%3A%20Some%20Microsoft%20Operations%20Manager%20Management%20Packs%20Require%20Proxy%20Configuration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-351587%22%20slang%3D%22en-US%22%3E%0A%20%26lt%3Bmeta%20http-equiv%3D%22Content-Type%22%20content%3D%22text%2Fhtml%3B%20charset%3DUTF-8%22%20%2F%26gt%3B%3CSTRONG%3EFirst%20published%20on%20TECHNET%20on%20Aug%2025%2C%202016%20%3C%2FSTRONG%3E%20%3CBR%20%2F%3E%20Hi%20everyone%2C%20my%20name%20is%20Mihai%20Sarbulescu%20and%20today%20I%20wanted%20to%20share%20a%20quick%20support%20tip%20with%20you.%20Please%20be%20aware%20that%20some%20Management%20Packs%20for%20Microsoft%20System%20Center%20Operations%20Manager%20have%20workflows%20that%20need%20to%20connect%20to%20the%20Internet%20in%20order%20to%20perform%20various%20actions.%20The%20Office%20365%20Management%20Pack%20is%20a%20good%20example%20of%20this%20as%20it%20needs%20to%20connect%20to%20the%20Internet%20to%20complete%20certain%20actions%20related%20to%20discovery%20and%20monitoring.%20In%20such%20situations%2C%20if%20a%20proxy%20server%20is%20needed%20to%20connect%20to%20the%20Internet%20from%20the%20System%20Center%20Operations%20Manager%20Management%20Servers%2C%20the%20proxy%20configured%20in%20Internet%20Explorer%20or%20WinHTTP%20will%20not%20be%20taken%20into%20account%20by%20the%20System%20Center%20Operations%20Manager%20processes%20-%20here%20MonitoringHost.exe%20processes%20which%20are%20running%20the%20actual%20workflows.%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20In%20order%20to%20configure%20the%20correct%20proxy%20server%2C%20the%20%3CB%3E%20MonitoringHost.exe.config%20%3C%2FB%3E%20file%20needs%20to%20be%20modified%20on%20all%20management%20servers%20%3CB%3E%20%3CI%3E%20%3C%2FI%3E%20%3C%2FB%3E%20from%20the%20%3CI%3E%20All%20Management%20Servers%20Resource%20Pool%20%3C%2FI%3E%20.%20The%20MonioringHost.exe.config%20file%20can%20be%20found%20in%20the%20System%20Center%20Operations%20Manager%20installation%20folder%20under%20%3CB%3E%20%25ProgramFiles%25%5CMicrosoft%20System%20Center%202012%5COperations%20Manager%5CServer%5C%20%3C%2FB%3E%20.%20Make%20%3CB%3E%20%3C%2FB%3E%20a%20backup%20of%20the%20MonitoringHost.exe.config%20file%20and%20then%20add%20these%20lines%20in%20the%20%3CEM%3E%20%26lt%3B%20%3C%2FEM%3E%20configuration%20%3CEM%3E%20%26gt%3B%20%3C%2FEM%3E%20section%20of%20the%20config%20XML%3A%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CSYSTEM.NET%3E%20%3CBR%20%2F%3E%20%3CDEFAULTPROXY%20enabled%3D%22%26quot%3Btrue%26quot%3B%22%20usedefaultcredentials%3D%22%26quot%3Btrue%26quot%3B%22%3E%20%3CBR%20%2F%3E%20%3CPROXY%20proxyaddress%3D%22%26quot%3Bhttp%3A%2F%2F%26lt%3BPROXYADDRESS%22%3E%3A%3CPORT%3E%22%20bypassonlocal%3D%22true%22%20%2F%26gt%3B%20%3CBR%20%2F%3E%20%3CBYPASSLIST%3E%20%3CBR%20%2F%3E%20%3C%2FBYPASSLIST%3E%20%3CBR%20%2F%3E%20%3C%2FPORT%3E%20%3CBR%20%2F%3E%20%3C%2FPROXY%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20Make%20sure%20that%20you%20replace%20%3CI%3E%20%26lt%3B%20%3C%2FI%3E%20PROXYADDRESS%20%3CI%3E%20%26gt%3B%20%3C%2FI%3E%20with%20the%20correct%20proxy%20server%20address%20and%20%3CI%3E%20%26lt%3B%20%3C%2FI%3E%20PORT%20%3CI%3E%20%26gt%3B%20%3C%2FI%3E%20with%20the%20correct%20proxy%20server%20port.%20When%20done%2C%20simply%20save%20the%20MonitoringHost.exe.config%20file%20and%20close%20it%20and%20you%E2%80%99re%20all%20set.%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CSTRONG%3EMihai%20Sarbulescu%20%3C%2FSTRONG%3E%20%7C%20Escalation%20Engineer%20%7C%20Microsoft%3C%2FDEFAULTPROXY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-351587%22%20slang%3D%22en-US%22%3EFirst%20published%20on%20TECHNET%20on%20Aug%2025%2C%202016%20Hi%20everyone%2C%20my%20name%20is%20Mihai%20Sarbulescu%20and%20today%20I%20wanted%20to%20share%20a%20quick%20support%20tip%20with%20you.%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-351587%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ESystem%20Center%20Operations%20Manager%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3C%2FSYSTEM.NET%3E%3C%2FLINGO-BODY%3E
Version history
Last update:
‎Mar 11 2019 10:31 AM
Updated by: