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. Fabric Updates - adjust/improve rescan job

    Hello,

    is my assumption correct, that the Fabric Update Remediation steps

    1.2 reboot computer
    1.3 Start compliance scan

    are based on a timeout value?

    with a current update baseline (which includes multiple server reboots] this regrettably breaks an automated update remediation on a cluster level, as it runs into an Error (2927) with the compliance scan as the Node undergoes a second reboot, while VMM is doing so.

    Can you either create the tasks a little more sophisticated in terms of checking for the installation status in between if possible (so its aware that another reboot is being performed..)
    or…

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Patch  ·  Flag idea as inappropriate…  ·  Admin →
  2. "Update remediation of AgentServer"

    24027 Update remediation of AgentServer <Server Name> timed out.

    The Remediation task with a time-out value of 40 minutes.

    When you have updates from more then a month, it will take more then 40 minutes to complete the task.

    I never seen remediation task been successful, because of this and other issues with the remediation feature.

    Please help to update this value or change the behavior so this error does not occur.

    29 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Patch  ·  Flag idea as inappropriate…  ·  Admin →
    declined  ·  Ashish Mehndi responded

    Request you to please connect with support team and raise the same as production ticket. Support Team can work and perform detailed investigation and identify the root cause.

  3. 2016 UR3 deletes vhdx-file when restoring a checkpoint without that disk

    to reproduce:
    - create a new vm
    - create a checkpoint of the new vm
    - attach a second disk to the vm
    - restore the checkpoint

    all versions below UR3:
    - the file of the 2nd disk remains on the csv and can be attached later

    UR3:
    - the agent removes the file of the second disk

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Patch  ·  Flag idea as inappropriate…  ·  Admin →
  4. Shared nothing live migration with each disk to a different location fails

    When LM a VM to a different cluster using VSM, and if the VM has more than one VHDX attached and I want to place each disk on a different CSV. migration fails with an access denied error. Migrating the same VM to one CSV succeeds.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Patch  ·  Flag idea as inappropriate…  ·  Admin →
  5. Add custom pre/post update remediation script for each host to make firmware updates possible during remediation cycle.

    I suggest that you add possibility for pre and post powershell scripts for what to do before and after update remediation.
    That way it would be possible to do hardware firmware upgrades during the remediation phase. Perhaps with configurable timeout before the host is supposed to be back online again?
    Possible parameters to the pre and post scripts could be hostname, BMC address/BMC credentials.

    0 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Patch  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base