Submit a ticketCall us

WebinarUpcoming Webinar: Know What’s Changed – with NEW Server Configuration Monitor

Change management in IT is critical. But, even with a good change management process, changes are too often not correctly tracked, if at all. The configuration of your servers and applications is a key factor in their performance, availability, and security. Many incidents can be tracked back to an authorized (and sometimes unauthorized) configuration change, whether to a system file, configuration file, or Windows® Registry entry. Join SolarWinds VP of product management Brandon Shopp to discover how the new SolarWinds® Server Configuration Monitor is designed to help you.

Register now.

Home > Success Center > Virtualization Manager (VMAN) > VMAN - Knowledgebase Articles > Setting up vSphere DRS to avoid conflicts with VMAN Recommendations

Setting up vSphere DRS to avoid conflicts with VMAN Recommendations

Table of contents

Updated October 20, 2017


Setting vSphere's Distributed Resource Scheduling (DRS) option to "Fully automated" results in very frequent changes to the virtualization environment, and the VMAN Recommendations engine cannot rely on historical data. This can cause a conflict between DRS and Recommendations, which may result in VMs being migrated back and forth unnecessarily.


When using VMAN's Recommendations, you can change vSphere's DRS settings to avoid Recommendations conflicts.


  • VMAN 7.0 and later


You do not need to disable DRS completely. Instead of enabling the "Fully automated" option, you can choose between "Partially automated" DRS or "Manual" DRS. When using VMAN Recommendations, SolarWinds recommends setting DRS to "Partially automated" for best results:





Last modified