Microsoft has issued fixes to its last round of Windows Server Management Pack fixes, but is asking you to help it understand if the new fixes fix the messes the last fixes created.
File this one under “doesn't exactly inspire confidence”.
This problem started way back in February 2016 when Microsoft released version 6.0.7303.0 of Windows Server Operating System management pack.
Redmond now says the fixes in that release caused nine new problems, namely:
- Disks in a cluster resource group in a failover cluster were not discovered as either logical disks or cluster disks, as the case may be.
- When trying to discover cluster names on Windows 2008, PowerShell errors appear in the event log indicating failures.
- Disk free space monitoring did not work on Quorum disks in failover clusters.
- Clustered shared volumes were being discovered twice – as a clustered shared volume and as a logical disk.
- Logical disk discovery did not discover logical disk on non-clustered servers with failover cluster feature enabled.
- Mount points were being discovered twice for clustered disks mounted to a folder – as a clustered disk and as a logical disk.
- Clustered shared volume was being discovered incorrectly when it had more than one partition.
- Hyper-V servers in a Windows Server 2012 R2 cluster discovered an additional disk with no properties and with name “Microsoft.Windows.Server.6.2.LogicalDisk”.
- Microsoft.Windows.Server.2008.MaxConcurrentAPI.Monitor was trying to run on Server 2008. This filled the log with errors every two minutes.
The good news is, the fix is in. You can now download version 6.0.7310.0 of the management pack.
But here's the twist: Microsoft's not sure the new fixes fix the failed fixes. So in its notification of the new fixes, it suggests users act as follows:
Please try out these management packs and let us know if the issues are indeed solved. You can drop your feedback on our user voice website.
Yes, we know that Windows Server is a very complex product that can be deployed on practically infinite combinations of hardware, with or without good drivers. But we also thought it's kind of the vendor's job to test its own fixes to make sure they fix things.
Here's that “user voice website” if your fix-fixing efforts aren't happy. ®