Specifications
NOTE: Since cross-zone information is not shown, details regarding which zone and which units conflicted is not
sent or show to sub-level zones or users.
Reconciling virtual environment units
A unit cannot reconcile (for example, perform a resync or auto-topology operation) if the unit
or any part of the unit (such as a virtual machine hosted on a hypervisor server) has already
been added to a zone in the DSView 3 software. If the unit fails to reconcile, the following
event occurs:
• A DSView 3 software event is sent to the top level zone. The event lists the conflicting
units (both the unit that already exists and the unit that could not be reconciled), which
zone each unit belongs to, and which user attempted to reconcile the unit.
Virtual machine management and licenses
In some cases, the dynamic relocation of managed virtual machines executed by manual
migration, VMware VMotion, XenMotion or Distributed Resource Scheduler (DRS) may affect
managed device licenses. If a hypervisor manager is not added to the DSView 3 software, but
manages two or more hypervisor servers that are spread throughout multiple zones in the
DSView 3 software, dynamic relocation of managed virtual machines causes the virtual
machine status to be set as “unmanaged” and frees a managed device license in the DSView 3
software. For more information, see Virtual Machines Management on page 4 and the DSView
3 software help.
Launching the VMware Viewer on a Windows Vista
®
client
If a DSView 3 software client is running the Vista operating system and the client browser is
launched with no administrator privileges, attempting to open a VMware message fails. The
error message The executable should not be invoked directly is displayed. To correct this issue,
either launch the client browser to “run as Administrator,” or configure the Vista Access
Control List (ACL) settings to permit the browser to run with administrator privileges.
DSView
®
3 Plug-in Virtualization Technical Bulletin31