The updated MP for Hyper-V 2016 has been release get it here.
At this time the documentation has not been updated.
Kevin Holman recently published an article on some recommended registry tweaks for SCOM 2016 environments.
This is an important read to prevent potential future issues.
An updated management pack is available for Office 365 you can get it here.
Updates and Fixes
- Automatically created SPN is never expired.
- Fixed issue: no alerts were generated for identical feature names related to different services.
- Improved discovery logic according to the latest version of Office 365 (support for services with similar display names).
- Updated “Office 365 Incidents and Messages” section.
- Updated “Import the Management Pack” section.
- Updated “Specify permissions your app requires to access Office 365 Management APIs” section.
- Updated “Appendix: Known issues and troubleshooting” section.
With the recent deprivation of SHA1 certificates in favour of the more secure SHA2 it’s important to know that SCOM uses SHA1 to manage workloads for cross platform monitoring (Unix / Linux).
Have no fear the MS SCOM team have released an article on how to replace your existsing SHA-1 certificates with the newer SHA256 certificates.
It is important to note that you will need to update your 2012 R2 environments to UR 12 and your 2016 environments to UR2 respectivly in order to use the new SHA256 certificates by default.
The article is available here
This is a summary of the wave of Management Packs that were released in February 2017. Information and download location in the links provided:
Management Pack for Windows Server Operating System 2016 v10.0.8.0 – here
If you know of any other Management Packs that have been released recently that I may have missed leave me a note in the comments and I’ll add them
Another new management pack is out for Windows Server 2016, the MP for RDS v10.0.5.0 can be found here.
What this MP can do:
- Remote Desktop Session Host: Remote Desktop Session Host (RD Session Host) enables a server to host RemoteApp programs or session-based desktops. Users can connect to RD Session Host servers in a session collection to run programs, save files, and use resources on those servers.
- Remote Desktop Licensing: Remote Desktop Licensing (RD Licensing) manages the licenses required to connect to a Remote Desktop Session Host server or a virtual desktop. You can use RD Licensing to install, issue, and track the availability of licenses.
- Remote Desktop Web Access: Remote Desktop Web Access (RD Web Access) enables users to access RemoteApp and Desktop Connection through the Start menu on a computer that is running Windows 8, Windows 7, or through a web browser. RemoteApp and Desktop Connection provides a customized view of RemoteApp programs and session-based desktops in a session collection, and RemoteApp programs and virtual desktops in a virtual desktop collection.
- Remote Desktop Gateway: Remote Desktop Gateway (RD Gateway) enables authorized users to connect to virtual desktops, RemoteApp programs, and session-based desktops on an internal corporate network from any Internet-connected device.
- Remote Desktop Connection Broker: Remote Desktop Connection Broker (RD Connection Broker):
- Allows users to reconnect to their existing virtual desktops, RemoteApp programs, and session-based desktops.
- Enables you to evenly distribute the load among RD Session Host servers in a session collection or pooled virtual desktops in a pooled virtual desktop collection.
- Provides access to virtual desktops in a virtual desktop collection.
- Remote Desktop Virtualization Host: Remote Desktop Virtualization Host (RD Virtualization Host) integrates with Hyper-V to deploy pooled or personal virtual desktop collections within your organization by using RemoteApp and Desktop Connection.