General VMM Feedback

Do you have an idea or suggestion based on your experience with VMM? We would love to hear it! Please take a few minutes to submit your idea in the one of the forums available on the right or vote up an idea submitted by another VMM customer. All of the feedback you share in these forums will be monitored and reviewed by the Microsoft engineering teams responsible for building VMM.

This forum (General Feedback) is used for any broad feedback related to VMM.
Be specific on your feedback. The more specific, the easier and quicker for us to review. Please be concise!! For more information, please see  User Voice How to FAQ .

VMM Product Team Response is on the bottom right, VMM Product Team Response.

Announcement section is created! This gets updated periodically so stay tuned! We are recruiting VMM customers for TAP. Check new items in VMM Team Announcement.

If you have technical questions or need help with VMM, please try visit our MSDN forums.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Support Server 2012 R2 Hyper-V in VMM 2019

    I know System requirements for System Center Virtual Machine Manager (https://docs.microsoft.com/en-us/system-center/vmm/system-requirements?view=sc-vmm-2019) does not list Server 2012 R2 Hyper-V as being a supported Hyper-V host in a VMM 2019 environment. And there's a difference between "not officially supported" and "officially not supported". VMM 2019 simply does not allow you to install its agent on a Server 2012 R2 Hyper-V server:

    Error (20523)
    The verslon of the Windows operating system on the computer xxxxx is not supported for a host.

    Recommended Action
    Upgrade the operating system to Windows Server 2016 or a later supported version, and then try the operation…

    171 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    12 comments  ·  Host Management  ·  Flag idea as inappropriate…  ·  Admin →
  2. VMM WSUS to update S2D Hyper-converged clusters

    Currently VMM 1807 does not support using a Fabric defined WSUS Update server for updating nodes of a S2D Hyper-converged infrastructure cluster; in fact there within Microsoft VMM documentation there is a "Note" that explicitly states the following:
    “..Note that you cannot update servers part of a Storage Spaces Direct cluster (either hyper-converged or disaggregated) using VMM and trying to patch these using VMM may cause data loss.”

    Yes, MAY CAUSE DATA LOSS!!

    First idea is that this should not be a mere Note, it should be flagged as a WARNING-DATA LOSS IS POSSIBLE.

    Second, how does the VMM group…

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Host Management  ·  Flag idea as inappropriate…  ·  Admin →
  3. Stop using Win32_Product for DHCP Agent version discovery

    Since UR5 VMM polls the Hyper-V hosts every half hour for the DHCP agent version. The Win32_Product WMI class is used for this.

    Because this class is used, every half hour MSIEXEC processes will run consistency and reconfiguration steps for all MSI packages on all Hyper-V hosts. This results in a flood wave of Application Event ID 1035 occurring every 30 minutes.

    The overall impact I cannot oversee as I don't know what is actually reconfigured.
    You can validate VMM is the cause of these calls by enabling WMI tracing.

    Microsoft itself actually advises (https://support.microsoft.com/en-us/kb/974524) not to use…

    47 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Host Management  ·  Flag idea as inappropriate…  ·  Admin →
  4. Enhanced session is not available in VMM

    This was top 4 common items from "End-to-End Hyper-V and Cluster Management in the SCVMM Console" Idea. Please provide specific details on this idea.

    73 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  Host Management  ·  Flag idea as inappropriate…  ·  Admin →
  5. Why reboot after deep discovery?

    It would be nice if there was an option (i.e. a checkbox in GUI) to avoid a reboot after deep discovery is done, as it is very likely that the bare metal deployment process will follow after that. If it could wait for the user provided configurations and continue once those are provided, it would save a reboot, which on modern servers can take a while.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Host Management  ·  Flag idea as inappropriate…  ·  Admin →
    completed  ·  Keiko Harada responded

    This changed in SCVMM 2012 R2, where bare-metal deployment can start after deep discovery without rebooting the machine.

    VMM Product Team

  • Don't see your idea?

Feedback and Knowledge Base