Complementando o post anterior sobre os novos Management Packs atualizados após o lançamento do Windows e System 2016 (http://www.marcelosincic.com.br/post/new-system-center-operations-manager-2016-management-packs.aspx), segue atualização.

Foi liberado hoje o Preview do novo Management Pack para SQL desde a versão 2008 até 2016.

Importante que este preview já resolve alguns problemas que ocorreram com bases de dados e indicadores na console do SCOM 2016:

New SQL Server 2008/2008 R2/2012 MP Features and Fixes

• No extra permissions on remote WMI are now required for Local System account when Always On hosts have names that are no longer than 15 symbols
• Fixed: Always On discovery and monitoring scripts cannot read cashed values in Windows registry
• Fixed: Wrong MP version number in some Always On scripts
• Fixed: CPUUsage and DBDiskLatency scripts fail with the reason: “Index operation failed”
• Added retry policy in some Always On workflows to make PS-scripts work more stable
• Updated the visualization library
• Changed behavior of Always On scripts for cases when WSFC service is stopped

New SQL Server 2014/2016 MP Features and Fixes

• No extra permissions on remote WMI are now required for Local System account when Always On hosts have names that are no longer than 15 symbols
• Fixed: Always On discovery and monitoring scripts cannot read cashed values in Windows registry
• Fixed: Wrong MP version number in some Always On scripts
• Fixed: CPUUsage and DBDiskLatency scripts fail with the reason: “Index operation failed”
• Added retry policy in some Always On workflows to make PS-scripts work more stable
• Updated the visualization library
• Fixed: Always On objects get undiscovered when any Always On discovery crashes

New SQL Server Replication 2008/2012/2014/2016 MP Features and Fixes

• Added support for configurations where computer host names are longer than 15 symbols
• Fixed: MonitorDistributorSnapshotFreeSpace fails when being launched against SQL Server 2014 SP2
• Fixed: Wrong source detection in logging
• Updated the visualization library

New SQL Server Analysis Services 2008/2012/2014/2016 MP Features and Fixes

• Added support for configurations where computer host names are longer than 15 symbols
• Fixed: AS workflows sometimes crash
• Updated the visualization library

New SQL Server Reporting Services 2008/2012/2014/2016 MP Features and Fixes

• Added support for configurations where computer host names are longer than 15 symbols
• Fixed: Web Service monitors do not support URL reservation https://+:<port>/<ReportServerPage> (protocol is HTTPS)
• Updated the visualization library

New SQL Server Dashboards Features and Fixes

• Fixed: Tiles content is replaced with question signs after a long period of inactivity

Download e detalhes disponiveis em https://blogs.msdn.microsoft.com/sqlreleaseservices/released-public-preview-for-system-center-management-packs-for-sql-server/

Após o lançamento e disponibilização do System Center 2016 (SCOM) utilize os novos Management Packs:

New Management Packs:

System Center Operations Manager Management Packs for Windows Server 2016 Essentials

Microsoft System Center Management Pack for SQL Server 2014

Microsoft System Center Management Pack for SQL Server 2016

Microsoft System Center Management Pack for SQL Server

System Center 2016 Management Packs for Open Source Software

Microsoft System Center Management Pack for System Center Service Manager

System Center Management Packs for Data Protection Manager 2016 Reporting, Discovery and Monitoring

Microsoft System Center 2016 Management Pack for Service Provider Foundation (SPF)

Microsoft System Center 2016 Management Pack for Orchestrator

Seguindo o lançamento do Windows 2016 com o Rollup 1 (http://www.marcelosincic.com.br/post/Upgrade-e-Update-do-Windows-Server-2016.aspx), o mesmo acontece com o System Center 2016.

Após as atualizações do System Center 2016, baixe os novos Management Packs do SCOM: http://www.marcelosincic.com.br/post/new-system-center-operations-manager-2016-management-packs.aspx

Porque isso acontece?

Antes de um fabricante liberar uma midia final ao público, ela é distribuida aos fabricantes.

Por exemplo, o fabricante de HW precisa ter certeza que alguma atualização não afetou drivers ou funcionalidades nativas do servidor. Desenvolvedores (ISVs) precisam ter certeza que seus plugins e softwares continuam “conversando” com a nova versão.

Como os dois produtos foram disponibilizados as midias aos fabricantes e desenvolvedores algumas semanas antes que o lançamento, a Microsoft precisa catalogar e gerar um pacote das atualizações que ocorreram entre esse lançamento para os fabricantes e o GA (General Avaliability) público, que normalmente é de 45 a 60 dias.

Update Rollups de System Center 2016

Update Rollup 1 para VMM: https://support.microsoft.com/en-us/kb/3190597

Update Rollup 1 para SCOM: https://support.microsoft.com/en-us/kb/3190029

Update Rollup 1 para Orchestrator: https://support.microsoft.com/en-us/kb/3190603

Update Rollup 1 para DPM: https://support.microsoft.com/en-us/kb/3190600

Update Rollup para SCCM 1609 TP: https://blogs.technet.microsoft.com/enterprisemobility/2016/09/27/update-1609-for-configuration-manager-technical-preview-available-now/

Lembrando que no caso do SCCM os upgrades e updates é realizado na própria console conforme já abordei em http://www.marcelosincic.com.br/post/Novo-Modelo-de-Updates-do-SCCM-2016.aspx