Equipa de suporte de System Center

Heartbeat Metric Alerts for Log Analytics

Bruno M. Afonso — Wed, 21 Mar 2018 17:06:57 GMT

At some point, if you have configured alerts within OMS, you probably have struggled with missing, delayed or false heartbeat alerts. We are aware of these issues and on most of the cases, it was related with latency - for further details on ingestion delays and how it affects the alert configuration refer to this link. Having heard the feedback and in our process of constant improvement, we are introducing a preview of a new alerting feature within Azure Monitor (present in the Azure Portal). With this new solution, we will able to retrieve near real-time notifications of a machine's heartbeat (as well as other metric related alerts), connected to Log Analytics. Let me share with you some clarity on the configuration of this feature: Azure Monitor - Heartbeat Alerts (OMS) Now for the new feauture - the near real-time alerting (currently in limited public preview): This brings down the time it takes to generate a log alert to under 5 minutes. The Metric Alerts on Logs, currently supports the following log types on OMS Log Analytics - heartbeat, perf counters (including those from SCOM), and update. With this solution, logs are converted to metrics as they stream into Log Analytics, these metrics are then pumped into the metrics platform where they can be alerted on. This metric conversion, avoids the ingestion of logs and a bypass is possible, avoiding the described ingestion delays. Alerting configuration with the goal of validating machine hearbeat can now be configured, and a more reliable and consistent monitorization can be achieved by this The official article with the launch is here: https://azure.microsoft.com/en-us/blog/faster-metric-alerts-for-logs-now-in-limited-public-preview/ Configure Alerts Before starting the configuration, you will need to sign up for the this feature: https://aka.ms/MetricLogPreview Afterwards you should be receiving a PDF with the additional details that you need to proceed on doing to gain access to it. After performing the above, here's the configuration needed: 1 - Head to the Azure Portal and find "Monitor" 2 - Then to "Alerts" and select "New Alert Rule" 3 - Now, start adding the configurations for the alert, let's begin with the target selection - Select your target - Subscription, Resource Group and OMS workspace: 4 4 - Add a criteria - as soon as you select this option, you shall be present with all the available options including the metrics:

5 - For the purpose of this test, we will configure Heartbeat metric, after selecting it, you should be seeing something similar to this: 6 - You can configure the alert for your needs, by selecting the specific virtual machine, its OS, version, etc. Also, configure the condition you wish to apply (in the example above, we have an alert for when the heartbeat is less than 3, to be checked over the period of the last 5 minutes, and with a frequency of 1 minute) 7 - Insert a name, description and severity for the alert, and check if you wish for it to become instantly enabled after creation: 8 - As final configuration, you need to define the action group, in order to notify specific individuals or teams, within a variety of channels (email, sms, runbooks, integration with third party ticketing software, etc): You can create a new action group and select the method of your preference: You are all set! From the moment you configure your alert you can manage it under Alerts in Manage Rules. You can delete, desable or enable your rules from there: All of this process will provide a more closer experience to real-time monitorization, since the SLA's are incredibly low. Feel free to reach out to me or my team, for further assistance on this. Bruno Afonso - Microsoft Support Engineer in Azure Monitoring and Automation

Sharepoint 2010 management pack in SCOM 2016

José Miguel Constantino — Thu, 02 Nov 2017 23:48:00 GMT

If you got to this page, then it’s probably because you’re trying to configure the Sharepoint 2010 management pack in SCOM 2016 and you’re getting an error like this one, while running the configuration task:

The Event Policy for the process started at xx:xx:xx has detected errors in the output. The 'StdErr' policy expression: .+ matched the following output: Exception calling "Load" with "1" argument(s): "Could not load file or assembly 'Microsoft.EnterpriseManagement.Core, Version=7.0.5000.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified." Failed to load Microsoft.EnterpriseManagement.Core.dll

Command executed: "C:\Windows\system32\cmd.exe" /c powershell.exe -Version "2.0" -NoLogo -NoProfile -Noninteractive "$ep = get-executionpolicy; if ($ep -gt 'RemoteSigned') {set-executionpolicy remotesigned} & '"C:\Program Files\Microsoft System Center 2016\Operations Manager\Server\Health Service State\Monitoring Host Temporary Files xx\xxxxx\AdminTask.ps1"' 'SharePointMP.Config'" Working Directory: C:\Program Files\System Center Management Packs One or more workflows were affected by this. Workflow name: Microsoft.SharePoint.2010.SCOM2012.ConfigSharePoint Instance name: Microsoft SharePoint 2010 Farm Group Instance ID: {xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx} Management group: Error Code: -2130771918 (Unknown error (0x80ff0032)).

Since Sharepoint 2010 mainstream support ended in 2015, the Sharepoint 2010 management pack was not tested in SCOM 2016, which means that this management pack is not supported in SCOM 2016. We do have feedback from the field that, despite the fact of not being supported, this MP does work in SCOM 2016. Now that you’re aware that the Sharepoint 2010 MP is not officially supported in SCOM 2016, but you still need to use it while you migrate your Sharepoint environment(s) to a more recent (and supported) version, then you can download and use the bellow sample management pack to be able to run the configuration task in SCOM 2016: If you already had the Sharepoint 2010 MP configured in SCOM 2012, then you already know what to do. If this is the first time you’re using the Sharepoint 2010 MP, then you’ll need to: 1 – Download, install and import Sharepoint 2010 MPs Please do carefully review the MP guide: https://www.microsoft.com/en-us/download/details.aspx?id=4419 2 – Download, install and just review in the detail the MP guide (you do not need to import the MP, as it’s for SCOM 2012): https://www.microsoft.com/en-us/download/details.aspx?id=34697 Please note that this sample management pack is provided “AS IS”, without warranty of any kind, express or implied, including but not limited to the warranties of merchantability, fitness for a particular purpose and noninfringement. In no event shall the author or copyright holders be liable for any claim, damages or other liability, whether in an action of contract, tort or otherwise, arising from, out of or in connection with the sample management pack or the use or other dealing in the sample management pack. Download: Community.SharePoint.2010.SCOM2016 José Miguel Constantino - Microsoft CSS Escalation Engineer

Operations Manager 2007/2012: High I/O peaks when writing on disk

Bruno M. Afonso — Fri, 19 May 2017 16:46:26 GMT

Hi all, In large Operations Manager environments, I/O peaks when writing in disks can affect the management servers (including the RMS, if it's SCOM 2007) and/or the agents that are managing many workflows. The reasons behind high I/O peaks include: • Number of management packs installed (the number of management packs influence the number of workflows), • Agent or MS acting as proxy for a considerable number of devices, • ESE store version, depending on the Windows Version, • Anti-Virus Exceptions not applied. • Other The case solved in which we based this post, was in a SCOM 2007 environment, but this can also be applied for 2012 versions. The Operations Manager Health service stores records of transactions that are not finished in something called "version store." The version store enables the Extensible Storage Engine (ESE) to track and to manage current transactions. It has a list of operations that are performed by active transactions that are maintained by the HealthService service. This list is an in-memory list of modifications that are made to the HealthService store database. There is a default size optimized for a typical installation of each Operations Manager role. However, the default size may be insufficient for certain Operations Manager environments. In order to get a solution for this, here are the changes on the registry that should be made: 1 - We recommend changing the following registry keys values so that agents\ Management Server can better manage the load: Subkey: HKEY_LOCAL_MACHINE \System\CurrentControlSet\Services\HealthService\Parameters Type: REG_DWORD Name: Persistence Version Store Maximum Base: Decimal The default size of the version store depends on the Operations Manager role and is defined as the number of 16-kilobyte pages to allocate in memory. The default values are as follows: Agent (workstation operating systems): 640 (10 megabytes) Agent (server operating systems): 1920 (30 megabytes) Management Server: 5120 (80 megabytes) It is recommended to set the version store size to double its default size for each machine. For example, if you set the version store size on a computer that hosts a Management Server role, set the registry value to 10240 (decimal). 2 - All management servers, that host a large amount of agentless objects may result in the MS running a large number of workflows: (network/URL/Linux/3rd party/VEEAM). This is an ESE DB setting which controls how often ESE writes to disk. A larger value will decrease disk IO caused by the SCOM healthservice but increase ESE recovery time in the case of a healthservice crash: Subkey: HKLM \System\CurrentControlSet\Services\HealthService\Parameters Type: REG_DWORD Name: Persistence Checkpoint Depth Maximum Base: Decimal SCOM 2007 and 2012 default existing registry value: 20971520 New Value: 104857600 3 – All management servers in a large management group: This sets the maximum size of healthservice internal state queue. It should be equal or larger than the number of monitor based workflows running in a healthservice. Too small of a value, or too many workflows will cause state change loss. The following key should be created: Subkey: HKLM \System\CurrentControlSet\Services\HealthService\Parameters Type: REG_DWORD Name: State Queue Items Base: Decimal Value: 20480 For further information regarding improving the performance of SCOM 2007 and 2012, please check the following blog post from our colleague Matt Goedtel: https://blogs.technet.microsoft.com/mgoedtel/2010/08/24/performance-optimizations-for-operations-manager-2007-r2-and-2012/ Hope this is helpful! Best regards Bruno Afonso Support Engineer EMEA Customer Service & Support

OpsMgr 2012 R2: MonitoringHost.exe causes 100% or high CPU usage on Windows 2008 SP2 or R2 servers after importing SQL MP 6.6.4.0 or 6.6.2.0

José Miguel Constantino — Fri, 08 Apr 2016 12:20:00 GMT

Update (April 8^th) - the SQL team has recently released a community technical preview, where the fix for this issue is included. Have a look at this blog post (download link there): https://blogs.msdn.microsoft.com/sqlreleaseservices/system-center-management-pack-for-sql-product-family-community-technology-preview-ctp2/ Hi all, We're seeing more and more reported issues of the monitoringhost process taking up to 100% of the CPU (or a really high usage on machines with more than 4 cores) on servers running Windows 2008 SP2 or Windows 2008 R2 SP1, after importing SQL MP 6.6.4.0 or 6.6.2.0. After collecting and analyzing several memory dumps of the process while the issue was occurring, we pinpointed the issue on two of the scripts from the SQL Management Pack (CPUUsagePercentDataSource.ps1 and DBDiskLatencyDataSource.ps1) that are causing the bellow .NET issue, due to a recent change on those same scripts: High CPU in .NET app using a static Generic.Dictionary | If broken it is, fix it you should - https://blogs.msdn.microsoft.com/tess/2009/12/21/high-cpu-in-net-app-using-a-static-generic-dictionary/ To mitigate the issue, disable the following rules and monitors on the SQL 2008 MP, if that server is running SQL 2008: Rules: Microsoft.SQLServer.2008.DBEngine.CPUUsagePercent.Collection - MSSQL 2008: Collect DB Engine CPU Utilization (%) Microsoft.SQLServer.2008.DBEngine.ThreadCount.Collection - MSSQL 2008: Collect DB Engine Thread Count Microsoft.SQLServer.2008.Database.DiskReadLatency.Collection - MSSQL 2008: Collect DB Disk Read Latency (ms) Microsoft.SQLServer.2008.Database.DiskWriteLatency.Collection - MSSQL 2008: Collect DB Disk Write Latency (ms) Monitors: Microsoft.SQLServer.2008.DBEngine.CPUUsagePercentMonitor: CPU Utilization (%) Microsoft.SQLServer.2008.DBEngine.ThreadCountMonitor: Thread Count Microsoft.SQLServer.2008.Database.DiskReadLatencyMonitor: Disk Read Latency Microsoft.SQLServer.2008.Database.DiskWriteLatencyMonitor: Disk Write Latency If the server is running SQL 2012, please disable the following rules and monitors: Rules: Microsoft.SQLServer.2012.Database.DiskReadLatency.Collection - MSSQL 2012: Collect DB Disk Read Latency (ms) Microsoft.SQLServer.2012.Database.DiskWriteLatency.Collection - MSSQL 2012: Collect DB Disk Write Latency (ms) Microsoft.SQLServer.2012.DBEngine.CPUUsagePercent.Collection - MSSQL 2012: Collect DB Engine CPU Utilization (%) Microsoft.SQLServer.2012.DBEngine.ThreadCount.Collection - MSSQL 2012: Collect DB Engine Thread Count Monitors: Microsoft.SQLServer.2012.Database.DiskReadLatencyMonitor - Disk Read Latency Microsoft.SQLServer.2012.Database.DiskWriteLatencyMonitor - Disk Write Latency Microsoft.SQLServer.2012.DBEngine.ThreadCountMonitor - Thread Count Microsoft.SQLServer.2012.DBEngine.CPUUsagePercentMonitor - CPU Utilization (%) In the meantime and since the issue is related with PowerShell, I’ve recommended some of my customers to upgrade it to the latest version (4.0) and since then, they didn’t report the issue back (even after enabling the rules and monitors again): Download Windows Management Framework 4.0 from Official Microsoft Download Center - https://www.microsoft.com/en-gb/download/details.aspx?id=40855 The SQL Management Pack engineering team already made a fix for this, which is to force these scripts to run in PowerShell 2.0 context: the fix will be included in the next public release of the SQL MP. Hope this helps! Best regards,

José Miguel Constantino
Escalation Engineer Global Business Support EMEA Customer Service & Support

Últimos lançamentos a ter em conta

José Miguel Constantino — Wed, 06 Aug 2014 10:02:00 GMT

Foram lançados recentemente os seguintes MPs e atualizações para Operations Manager 2012 e Service Manager 2012:

System Center Management Pack for Office 365

https://www.microsoft.com/en-us/download/details.aspx?id=43708

Update Rollup 3 for System Center 2012 R2 Operations Manager

https://support.microsoft.com/kb/2965445

Update Rollup 7 for System Center 2012 Operations Manager Service Pack 1

https://support.microsoft.com/kb/2965420

Update Rollup 3 for System Center 2012 R2 Service Manager

https://support.microsoft.com/kb/2962041

Update Rollup 3 for System Center 2012 R2 Orchestrator

https://support.microsoft.com/kb/2931268

José Miguel Constantino

Support Escalation Engineer

Active Directory Federation Services (ADFS) Management Pack

José Miguel Constantino — Mon, 16 Jun 2014 17:43:00 GMT

Foi lançado hoje uma nova versão do Active Directory Federation Services (ADFS) Management Pack 2012 R2 que corrige um problema detectado na versão original em que as descobertas não funcionavam correctamente e o seguinte erro é mostrado no event viewer do management server:

DiscoveryId: e3646f31-22c9-0d88-8a33-562cee3cc003
HealthServiceId: 15010e66-18b3-2972-6d32-3c5615db06eb
Microsoft.EnterpriseManagement.Common.DiscoveryDataUnresolvedClassPropertyNameException,Unable to resolve the class property name specified in the discovery data item. Try using a fully qualified name.
Class property name: f2851ac1-b1fa-1a1f-7b0f-2c75667a30bf
Rule ID: e3646f31-22c9-0d88-8a33-562cee3cc003

A nova versão do MP que corrige este problema pode ser encontrada aqui: https://www.microsoft.com/en-us/download/details.aspx?id=41184

Cumprimentos,

José Miguel Constantino

Support Escalation Engineer

Site de feedback 'Microsoft Connect' novamente disponível

José Miguel Constantino — Mon, 02 Jun 2014 05:36:00 GMT

Temos novamente disponível o site para feedback direto e/ou reportar problemas dos nossos produtos, Microsoft Connect:

https://connect.microsoft.com/WindowsServer/InvitationUse.aspx?ProgramID=8509&InvitationID=8509-43PB-44TW

Além de ser possível dar sugestões e reportar problemas, também é possível votar em sugestões de outros membros da comunidade System Center.

Ficamos então à espera do vosso feedback!

Cumprimentos,

José Miguel Constantino

Support Escalation Engineer

Update Rollup 4 for System Center 2012 SP1 Service Manager (KB2887775)

José Miguel Constantino — Mon, 18 Nov 2013 03:53:45 GMT

Foi (re)lançada na passada 6ª feira, a atualização UR4 para o Service Manager 2012 SP1 e aqui está então o link direto para o UR4 do Service Manager 2012 SP1:

https://www.microsoft.com/en-us/download/details.aspx?id=40836&WT.mc_id=rss_alldownloads_all

A versão anterior tinha sido retirada conforme mencionado neste blog da nossa equipa de produto:

https://blogs.technet.com/b/servicemanager/archive/2013/10/22/service-manager-2012sp1-ur4-availability.aspx

José Miguel Constantino

Support Escalation Engineer

Suporte em máquinas virtuais Windows Azure para System Center 2012 Configuration Manager e System Center 2012 Endpoint Protection

José Miguel Constantino — Thu, 24 Oct 2013 07:26:00 GMT

A equipa de produto de ConfigMgr (ou SCCM) lançou ontem a seguinte informação de suportabilidade de System Center 2012 Configuration Manager e System Center 2012 Endpoint Protection, a correrem em maquinas virtuais no Windows Azure:

https://blogs.technet.com/b/configmgrteam/archive/2013/10/23/configmgr-and-endpoint-protection-support-for-windows-azure-vms.aspx

A lista de produtos Microsoft suportados em máquinas virtuais no Windows Azure já foi atualizada com esta informação:

Microsoft server software support for Windows Azure Virtual Machines - https://support.microsoft.com/kb/2721672

José Miguel Constantino

Support Escalation Engineer

Update Rollup 4 for System Center 2012 Service Pack 1

José Miguel Constantino — Wed, 23 Oct 2013 03:01:00 GMT

Foi lançada ontem a atualização mais recente para o System Center 2012 SP1:

Description of Update Rollup 4 for System Center 2012 Service Pack 1 - https://support.microsoft.com/kb/2879276

O artigo tem todos os detalhes necessários, mas fica aqui a lista de produtos onde se deve instalar a atualização:

App Controller (KB2887822)
Operations Manager (KB2880799)
Operations Manager - UNIX and Linux Monitoring (part of KB2880799)
Operations Manager - UNIX and Linux Monitoring (Management Pack update)
Service Manager (KB2887775)
Virtual Machine Manager (KB2887779, KB2888944, and KB2888946)

José Miguel Constantino

Support Escalation Engineer