SCOM Global Service Monitor

Hello All!

Pretty short post about System Center Operations Manager Global Service Monitor feature.

Microsoft have pretty useful service called Global Service Monitor(GSM) which could help you to monitor yours external Web Sites from different Locations for Availability.

But some times you can have External Resource but with Limited access from specific White-list and if you want to setup GSM to monitor that resource you can use list of IP from following MS link: IP addresses used by Application Insights  to make ACL Rules on Firewall.

Hope that info will help you set more secure monitoring.

SCOM Skype for Business 2015 Management Pack QoE Monitoring Issue

Hi All!

First all, please make sure that you install/update to latest Skype for Business 2015 Management Pack (SfBMP) version from Microsoft Site. (9319.247 at moment then I am writing Post)

Check SfBMP documentation from MS and make sure that you Enabled Proxy for Agents in SCOM Console or through Powershell.

On SfB level: you need to define Network Site, Network Region, Network Subnet – for  this SfBMP this information have to be configured.

OK let’s assume that you set all prerequisites and SfB Servers from you Topology were discovered with appropriate Roles.

But what about QoE Monitoring? If there is no info in Detail View for Instances:

screeen-8

 

You have to define thresholds for OoE Discovery according to your SLA’s for Example like that:

qoe_overides

Here is some insights:

If we checked that QoE Discovery code in Exported Management Pack we will notice following comment:

#############################################################################

# 1. Discover problematic QoE instances. ( Healthy instances are not discovered at all )

# 2. For each QoE instance, set values of Attributes with alerting context.

#    ( These will be used at Analysis step )

So you will see nothing in views if threshold values are too high (by default for Warn State =14 for Critical State=20) So if you NEED to have info in views you have to setup pretty low threshold values.

And at the End:

screeen-1

Happy Monitoring!

THE USE OF THE WEBPAGES OF artempro.ru IS ON YOUR OWN RISK. THE INFORMATION IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND INCLUDING ALL IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE, COURSE OF DEALING OR USAGE OF TRADE. artempro.ru  IS NOT LIABLE FOR ANY WARRANTY CLAIMS OR DAMAGES, IRRESPECTIVE OF THE LEGAL CAUSE, WHETHER IN CONTRACT, WARRANTY, FAILURE OF A REMEDY TO ACHIEVE ITS INTENDED OR ESSENTIAL PURPOSES, TORT (INCLUDING NEGLIGENCE), STRICT LIABILITY, INDEMNITY OR ANY OTHER LEGAL THEORY AND IN PARTICULAR SHALL NOT BE LIABLE FOR DAMAGES INCURRED AS A RESULT OF CONSULTATION, ASSISTANCE IN SETTING-UP PROCEDURES, BUSINESS INTERRUPTION OR SOFTWARE DEFECTS, EXCEPT WHERE LIABILITY IS MANDATORY FOR DAMAGES TO PRIVATELY USED PROPERTY OR BECAUSE OF VIOLATION OF CARDINAL CONTRACTUAL OBLIGATIONS OR DUE TO INTENT, GROSS NEGLIGENCE OR FAILURE TO CONFORM TO EXPRESS WARRANTIES. HOWEVER, LIABILITY FOR DAMAGES ARISING FROM THE VIOLATION OF CARDINAL CONTRACTUAL OBLIGATIONS SHALL BE LIMITED TO THE FORESEEABLE DAMAGE NORMALLY COVERED BY A CONTRACT EXCEPT IN CASES OF WILFUL MISCONDUCT OR GROSS NEGLIGENCE.

SCOM Monitoring of Linux/Unix of Windows workgroup Agent with same name

Hello All!

Lets assume that for some reason you have in yours infrastructure servers which have exact same FQDNs but different IPs (sometimes it can happen with best of us). And you have question if it is possible to monitor such Objects with your SCOM. Every Entity in SCOM has its own unique HealthService GUID – according to this blog How are GUIDs in SCOM and SCSM calculated? such GUIDs calculated based on many parameter which are same inside Management Group and FQDNs for Windows  Computer and Unix/Linux Computer (which are same for our servers). So it is looks like we cannot monitor Servers with same FQDN.

Workaround available:

Imagine we have two servers deployed

– Server1

FQDN:ubuntu1.contoso.com

IP: XXX.XXX.XXX.001

– Server2

FQDN:ubuntu1.contoso.com

IP: XXX.XXX.XXX.002

On SCOM Management server we can create records in c:\Windows\System32\drivers\etc\hosts file

# Server1

#FQDN:ubuntu1.contoso.com

XXX.XXX.XXX.001 ubuntu1.contoso.com

# Server2

# FQDN:ubuntu1.contoso.com

XXX.XXX.XXX.002 ubuntu1-sec.contoso.com

Next on our “second” server we have to manually generate Certificate

/opt/microsoft/scx/bin/tools/scxsslconfig -h ubuntu1-sec.contoso.com -f -v

Now we can discover this server through SCOM Console with appropriate IP address.

Same can be done with Windows Server Computer but Certificate generated different way.

Happy Monitoring!

THE USE OF THE WEBPAGES OF artempro.ru IS ON YOUR OWN RISK. THE INFORMATION IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND INCLUDING ALL IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE, COURSE OF DEALING OR USAGE OF TRADE. artempro.ru AG IS NOT LIABLE FOR ANY WARRANTY CLAIMS OR DAMAGES, IRRESPECTIVE OF THE LEGAL CAUSE, WHETHER IN CONTRACT, WARRANTY, FAILURE OF A REMEDY TO ACHIEVE ITS INTENDED OR ESSENTIAL PURPOSES, TORT (INCLUDING NEGLIGENCE), STRICT LIABILITY, INDEMNITY OR ANY OTHER LEGAL THEORY AND IN PARTICULAR SHALL NOT BE LIABLE FOR DAMAGES INCURRED AS A RESULT OF CONSULTATION, ASSISTANCE IN SETTING-UP PROCEDURES, BUSINESS INTERRUPTION OR SOFTWARE DEFECTS, EXCEPT WHERE LIABILITY IS MANDATORY FOR DAMAGES TO PRIVATELY USED PROPERTY OR BECAUSE OF VIOLATION OF CARDINAL CONTRACTUAL OBLIGATIONS OR DUE TO INTENT, GROSS NEGLIGENCE OR FAILURE TO CONFORM TO EXPRESS WARRANTIES. HOWEVER, LIABILITY FOR DAMAGES ARISING FROM THE VIOLATION OF CARDINAL CONTRACTUAL OBLIGATIONS SHALL BE LIMITED TO THE FORESEEABLE DAMAGE NORMALLY COVERED BY A CONTRACT EXCEPT IN CASES OF WILFUL MISCONDUCT OR GROSS NEGLIGENCE.