none
Compliance scan unavailable for 2/5 hosts RRS feed

  • Question

  • Have just taken over management of a Hyper-V cluster for a small organisation and noticed a strange issue on a couple of hosts in VMM. The compliance "scan" option is totally greyed out. Have searched high and low and not found anything remotely similar. Hosts are working fine. Running the following PowerShell command:

    Get-SCComplianceStatus -VMMManagedComputer  $(Get-SCVMHost -ComputerName "HYPERVHOST1").ManagedComputer

    Results in the following error:

    Get-SCComplianceStatus : VMM cannot find ComplianceStatus object aae12e1c-2c1e-41d2-99b1-3b0d0000aec3. (Error ID: 801,Detailed Error: )
    
    Ensure the library object is valid, and then try the operation again.
    At line:1 char:1+ Get-SCComplianceStatus -VMMManagedComputer  $(Get-SCVMHost -ComputerN ...
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~    
    + CategoryInfo          : ReadError: (:) [Get-SCComplianceStatus], CarmineException    
    + FullyQualifiedErrorId : 801,Microsoft.SystemCenter.VirtualMachineManager.Cmdlets.GetComplianceStatusCmdlet

    Checked VirtualManagerDB and noticed the two hosts missing from the BaseLineComplianceStatus table.

    Any ideas what would cause this and how to resolve?

    Cheers.

    Sunday, December 8, 2019 4:29 AM

All replies

  • Nevermind, managed to fix it.

    Trying to force a scan using PowerShell showed this error message - 

    Start-SCComplianceScan : Compliance scan or update remediation action cannot be completed on HYPERVHOST1.
    (Error ID: 24044)

    Ensure the specified machine is managed by the VMM server and has at least one baseline assigned, and then try the operation again.


    So I thought maybe removing and re-adding the host group to the baseline scope might refresh this - and it did!! Had some strange results though. Hosts in another cluster (also suffering same issue) completely disappeared from the compliance list. Need to remove all hosts from all baselines and then re-add to get everything working correctly again.

    Hope post might help someone else running into this ggglitch ;)









    Sunday, December 8, 2019 4:44 AM
  • Hello,

    It's glad to hear the issue has been resolved.

    The solution is helpful to others, who may face with the same problem.

    If you still have any other questions about this case, please feel free to submit here.

    Best regards,

    Andy Liu


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, December 9, 2019 6:56 AM