locked
Hyper-V 2019 - Not Discover VM RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi,
    I SCOM 2016 I tried discover Hyper-V 2019 Virtual Machines.
    I have 4 nodes cluster I observerd that when I had less than (about) 30 Virtual Machines, the machines in Discovered succesfully.
    When I have more that 70 Virtual Machines in node - SCOM can not discover any Virtual Machines.
    I did override for Object Discoveries: Hyper-V 2016 Virtual Machine Discovery - Timeout second from 300 to 1200 and still I can not discover VMs.
    In hyper-V node I had error:

    Error 22402:
    Forced to terminate the following PowerShell script because it ran past the configured timeout 3600 seconds.
    Script Name:    DiscoverHyperV2016VirtualMachine.ps1
    One or more workflows were affected by this.  
    Workflow name: Microsoft.Windows.HyperV.2016.VirtualMachineDiscovery
    Instance name: Instanace name
    Instance ID: {92E32F24-0211-4F30-4A89-146FD23C4870}
    Management group: Management Group Name

    and
    Error 22411
    The PowerShell script will be dropped because the it has been waiting in the queue for more than 10 minutes.
    Script Name:    ReadMaintenanceModeRegEntry.ps1
    One or more workflows were affected by this.  
    Workflow name: Microsoft.SystemCenter.Agent.MaintenanceMode
    Instance name: Instanace name
    Instance ID: {22C0A529-E828-A2BC-2277-281F9BE059E1}
    Management group: Management Group Name

    Error 22411
    The PowerShell script will be dropped because the it has been waiting in the queue for more than 10 minutes.
    Script Name:    MemoryUtilization.ps1
    One or more workflows were affected by this.  
    Workflow name: Microsoft.Windows.Server.10.0.OperatingSystem.MemoryAvailableMBytes
    Instance name: Microsoft Windows Server 2019 Datacenter
    Instance ID: {B9D0B210-BF43-1AF3-5E36-7F5BC67D7B15}
    Management group: Management Group Name
    Thursday, November 28, 2019 1:26 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    I don't believe the current version of Microsoft System Center 2016 Management Pack for Hyper-V supports Hyper-V 2019 yet, I have asked about when the support will come but I haven't got an answer yet.

    Best regards,
    Leon

    Blog: https://thesystemcenterblog.com LinkedIn:

    Thursday, November 28, 2019 1:37 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Bartlomiej, 

    which Hyper-V MP version are you using?
    Do you have only Hyper-V or Virtual Machine Manager is also in place?

    It could of course also be that the nodes are so busy and cannot run the discovery scripts, but then I would have expected to see also events related to the scripts, discovering the nodes. Can you please check once again for other similar events? Of course it could just be that you cannot discover the hosts with the Hyper-V 2016 MP like Leon mentioned. 

    Regards,

    (Please take a moment to "Vote as Helpful" and/or "Mark as Answer" where applicable. This helps the community, keeps the forums tidy, and recognizes useful contributions. Thanks!) Blog: https://blog.pohn.ch/ Twitter: @StoyanChalakov


    Thursday, November 28, 2019 1:43 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Stoyan,
    I have:
    Microsoft Windows Hyper-V 2016 Discovery - 10.0.8.0
    Microsoft Windows Hyper-V 2016 Monitoring - 10.0.8.0
    Microsoft Windows Hyper-V Library - 10.0.8.0

    Also I have SCVMM 2019: 10.19.1013.0

    How to check that nodes are busy? I think that I have a lot of memory in nodes.
    I event viewer also I have Warnings:

    Log Name:      Operations Manager
    Source:        Health Service Script
    Date:          28.11.2019 16:38:00
    Event ID:      6024
    Task Category: None
    Level:         Warning
    Keywords:      Classic
    User:          N/A
    Computer:      Server Name
    Description:
    LaunchRestartHealthService.ps1 : Attempted Health Service Restart.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Health Service Script" />
        <EventID Qualifiers="0">6024</EventID>
        <Level>3</Level>
        <Task>0</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2019-11-28T15:38:00.457012800Z" />
        <EventRecordID>614039</EventRecordID>
        <Channel>Operations Manager</Channel>
        <Computer>Server Name</Computer>
        <Security />
      </System>
      <EventData>
        <Data>LaunchRestartHealthService.ps1</Data>
        <Data>Attempted Health Service Restart.</Data>
      </EventData>
    </Event>

    Friday, November 29, 2019 5:45 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Bartlomiej,

    Find an article says that if there are a lot of VMs on the Hyper-V host, some PowerShell script will be failed to run in a limited time 10 minutes. You can refer to it :

    http://www.systemcentercentral.com/research-this-kb-power-shell-script-was-dropped/

    Note: Non-Microsoft link, just for your reference.

    Hope it can help.

    Best regards.
    Crystal

       

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

    Friday, November 29, 2019 6:28 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Bartlomiej,

    How's everything going? If there's anything else we can help, please let us know.

    Best regards.

    Crystal

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

    Wednesday, December 4, 2019 6:38 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Crystal,

    I created items in regedit at Management Server and Hyper-V nodes but stil VMs not discovered.
    HKLM\SOFTWARE\Microosft\Microosft Opertaions Manager\3.0\Modules\Global\PowerShell
    DWORD - QueueMinutes - 120 (decimal)
    DWORD - ScriptLimit - 120 (decimal)

    Friday, December 6, 2019 5:53 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi Bartlomiej,
     
    For the issue, it is a little strange.  I guess it may related to what Stoyan and Leon said. I will try the best to deliver message to the product team to see if they have any comments, but not guaranteed. If there is any update, I'll get back to you immediately.
     
    Thanks for your understanding.
     
    Best regards.
    Crystal

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


    Friday, December 6, 2019 8:23 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Crystal,

    Do you have any news from product team?

    Regards

    Bartłomiej

    Friday, December 13, 2019 10:07 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Bartłomiej,

    Not yet, will strike to see if there's any update.

    best regards.

    Crystal

    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 16, 2019 8:36 AM