System Center Virtual Machine Manager 2012

  1. Modify the bus assignments so that boot and system volume disks are located on IDE bus, and then try the operation again. ...
  2. Modify the Bus assignments so that the boot volume is located on the first hard disk of the virtual machine and then try ...
  3. Modify the bus assignments so that the system volume is located on the IDE bus on the virtual machine and then try the operation ...
  4. Modify the existing Administrator UserRole or create a new UserRole from DelegatedAdmin profile to delegate administration. ...
  5. More than one Virtual Machine exists with the name provided. Get the vm object using the ID parameter to avoid ambiguity. ...
  6. Mount logical unit calls do not have corresponding register logical unit calls. Logical unit IDs with missing register call ...
  7. Move the virtual machine to the private cloud's host group, or add the virtual machine's host group to the private cloud, ...
  8. Move the virtual machine to the private cloud's library share path, or add virtual machine's host group to private cloud, ...
  9. Move virtual machine %VMName; off of the perimeter network or select a virtual machine that is not on a perimeter network, ...
  10. Move VM to a System Center Datacenter Recovery protected cloud before enabling System Center Datacenter Recovery on the VM. ...
  11. Moving the selected host, host group, or host cluster to host group %HostGroupName; will result in a restructuring of folders ...
  12. Moving the virtual machine (%VMName;) to the virtualization host (%VMHostName;) using live migration could not be completed ...
  13. Moving the virtual machine (%VMName;) to the virtualization host using live migration could not be completed because the ...
  14. Multiple library resources were discovered during import of "%SharePath;" folder. This could be an issue if it occurred during ...
  15. must be implemented in the type that exposes element points which position type is defined as ElementPointPositionType.Custom ...
  16. Name; cannot be managed by Virtual Machine Manager, as managing a host cluster in which the HA-VMM is running on is not supported. ...
  17. Name; is already associated with a RunAs account for %TargetName;. A RunAs profile can only be associated with one RunAs ...
  18. Native uplink port profile with logical network definition and used by host network adapter cannot be changed to remove all ...
  19. Native uplink port profile without logical network definition and used by host network adapter cannot be changed to have ...
  20. Need to specify the external name of the vm network by Virtual Switch Extension Manager while explicitly using the External ...
  21. Need to update External VMSubnet on the Virtual Network Adapter port as the actual value (%ActualValue;) is different than ...
  22. Need to update name on this instance of logical switch. Either user updated the LogicalSwitch or updated the name Out of ...
  23. Need to update switch feature setting (%Name;) on this logical switch instance. Either the virtual switch extension manager ...
  24. Need to update the extensions componsed on this instance of logical switch. Either user updated the LogicalSwitch (add/remove/re-order ...
  25. Need to update the order of extensions componsed on this instance of logical switch. Either user updated the LogicalSwitch ...
  26. Need to update uplink mode to (%UplinkMode;) on this instance of logical switch. Either the user updated the uplink mode ...
  27. Need to update windows network virtualization setting on the uplink physical network adapter of this logical switch instance. ...
  28. Need to update/apply uplink port profile set (%Name;) on this logical switch instance. Either the user updated the uplink ...
  29. Network adapter drivers are not available for the operating system of the source computer. The virtual machine will be created ...
  30. Network bandwidth on the virtualization host (%VMHostName;) is not sufficient to satisfy the reserve level for all network ...
  31. Network tags and network locations are obsolete in this version of VMM. Use a logical network to identify the desired network ...
  32. No appropriate IP pool with available virtual IP addresses could be located for load balancer configuration with template ...
  33. No compatible drivers were identified for the device: %DeviceDescription;. The offline physical-to-virtual conversion requires ...
  34. No connected IP address pool with remaining IPv4 addresses could be identified to supply an address for the network adapter. ...
  35. No connected IPv6 address pool with remaining addresses could be identified to supply an address for the network adapter ...
  36. No connected MAC address pool with remaining addresses could be identified to supply an address for the network adapter. ...
  37. No connected virtual IP (VIP) address pool with sufficient remaining addresses could be identified for the virtual machines ...
  38. No IP address has been specified and it is not being assignment automatically from the selected IP subnet. Verify that the ...
  39. No IP pool with available virtual IP addresses could be found that supports the requirements of the virtual machine tier. ...
  40. No load balancer with a back-end connection to logical network %LogicalNetworkName; could be found that supports the requirements ...
  41. No load balancer with a front-end connection to logical network %LogicalNetworkName; could be found that supports the requirements ...
  42. No load balancer with a front-end connection to VM Network %VMNetworkName; could be found that supports the requirements ...
  43. No load balancers with sufficient VIP addresses could be located attached to host group %HostGroupName; and its parent host ...
  44. No load balancers with the manufacturer %ManufacturerName; could be located attached to host group %HostGroupName; and its ...
  45. No load balancers with the model %ModelName; could be located attached to host group %HostGroupName; and its parent host ...
  46. No matching Virtual Switch found on target host for Virtual network adapter VM Network (%VMNetworkName;) and port classification ...
  47. No Run As account is specified for the Application Host '{0}'. Specify a Run As account and then try the operation again. ...
  48. No storage array associated with this host has appropriate resources to provision a clone of VHD resources required by virtual ...
  49. No storage pool associated with the host group containing this host has appropriate resources to provision a copy of VHD ...
  50. No supported virtualization software supports a processor count of %Count;. Please change this to a valid value and try the ...
  51. No virtual hard disk could be located for virtual machine %VMName;. A disk must be present to deploy the virtual machine. ...
  52. Node drag operation cannot be started because another node drag operation is already under way. Complete the current operation ...
  53. None of the virtual machines related to the virtual IP (VIP) address (%Name;) in Microsoft Network Load Balancing are responding. ...
  54. Not enough memory available due to the host reserve at level: %ReserveLevel;. Total memory at this reserve level for use ...
  55. Not enough memory available. Total memory on the host is %MemorySize; MB. Remaining memory for use by existing and new virtual ...
  56. Note: Actual live migrations might differ slightly based on current resource usage on the hosts when Dynamic Optimization ...
  57. Note: The following information was gathered when the operation was attempted. The information may appear cryptic but provides ...
  58. NPIV transfer cannot be used because the physical port %PhysicalWWPN; on server %VMHostName; is connected to a fabric that ...
  59. NPIV transfer cannot be used because the virtual machine %VMName; is not stored on a LUN that is unmasked to a Virtual Port. ...
  60. NUMA spanning is disabled on target host %VMHostName; and memory fragmentation between NUMA nodes may cause this virtual ...
  61. NUMA topology is specified for this virtual machine and the target host does not support NUMA. These NUMA settings will be ...
  62. N_Port ID Virtualization (NPIV) transfer is not supported because the virtual machine (%VMName;) is stored on a LUN that ...
  63. Object cannot be shared because either the user role %UserRoleName; does not have access to the cloud that this object is ...
  64. Object name is invalid. Object name must observe the following rules: - It must begin with an alphabetic character or an ...
  65. Object with the given object ID was serialized using Structured method but it is attempted to be deserialized using {0} method ...
  66. One installed feature requires an immediate reboot of your computer. Click 'Reboot Now' to exit Setup and reboot now. Click ...
  67. One of the encryption algorithms required by the BMC at %VMHostName; is not FIPS compliant as configured on the Windows OS ...
  68. One of the physical network adapter configurations that are being applied does not match any of the physical network adapters ...
  69. One or more applications were not installed when the pending service template for the service (%ServiceName;) was applied, ...
  70. One or more applications were not installed when the pending service template for the service (%ServiceName;) was dismissed, ...
  71. One or more available cluster volumes associated with host %VMHostName; is not associated with a path in the default placement ...
  72. One or more IPv4 addresses could not be configured automatically. For each network to be used, make sure the network is selected, ...
  73. One or more IPv6 addresses were configured automatically. One or more DHCP IPv4 addresses were configured automatically. ...
  74. One or more load balancers are bound to resources and logical networks that are not part of this private cloud, which might ...
  75. One or more logical networks are bound to resources that are not part of this private cloud, which might make the private ...