Please provide your feedback in this short Flings' survey.

Virtual Machine Desired State Configuration

version 1.0.0 — October 01, 2021

Contributors 11
View All
Comments 9
View All

Release Date: June 14, 2021


Virtual machines often need to have their CPU and/or Memory configurations modified because of performance tuning efforts, resource capacity reclamation (rightsizing), licensing requirements, or other business-related reasons. Virtual infrastructure administrators are challenged with reconfiguring the CPU & Memory configurations of existing (powered on) virtual machines because they typically need to be powered off to make the necessary changes. Powering off virtual machines that are in production and providing business value requires careful planning and scheduling with different departments/application owners to minimize impacts to the business. VMDSC aims to solve this problem.

Other solutions have attempted to solve this problem by scheduling the desired state to take effect at a certain date/time; however, this approach requires coordinating with the business to determine when the virtual machine can be powered off safely. This coordination is extremely time consuming and results in an avoidance to perform the rightsizing of the virtual machine(s).

Virtual Machine Desired State Configuration (VMDSC) allows virtual administrators to specify VM CPU/Memory desired state which will take effect upon the next Guest OS reboot. This removes the burden of having to schedule a downtime window with the business/app owners… VMs realize their desired state the next time they are rebooted which happens naturally because of regular lifecycle operations (OS patching, application updates, etc.). When integrated with vRealize, VMDSC allows VI Admins to automatically rightsize workloads based on vRealize Operations recommendations. Users can rightsize directly from vROps at the VM level or for all VMs within a folder/cluster/resource pool which has a much greater sustainability impact for organizations.

  • vCenter 7.x or above (not tested with earlier versions of vCenter but may work)
  • vSphere Service Account with the following permissions:
    • System.Read
    • System.View
    • VirtualMachine.Interact.PowerOff
    • VirtualMachine.Interact.PowerOn
    • VirtualMachine.Interact.Reset
    • VirtualMachine.Config.CPUCount
    • VirtualMachine.Config.Memory
    • VirtualMachine.Config.AdvancedConfig
    • VirtualMachine.Config.Settings
    • Sessions.ValidateSession
  • See the User Guide for vRealize Suite integration requirements

High-Level Steps

  • Create a VMDSC vCenter Service Account
  • Deploy VMDSC OVA
  • Leverage Postman to configure VM desired state configurations (download & install VMDSC Postman Collection)
  • Integrate with vRealize Orchestrator
  • Integrate with vRealize Operations

Please review the VMDSC User Guide for detailed instructions.


User Guide v1.2 Updates - Added “Change Settings” to VMDSC vCenter role and added the need to import the vROps certificate into vRO.

Launch Version 1.0.0 (Goldblum) - Build Number: 2636821