System Center Virtual Machine Manager 2012

  1. The template (%Name;) contains more than one Server App-V package. Running multiple Server-App V packages on a single virtual ...
  2. The template (%Name;) does not contain administrator password or credentials that are required to enable Microsoft network ...
  3. The template (%Name;) does not contain an operating system profile, which is required to enable Microsoft network load balancing. ...
  4. The template (%Name;) does not have a compatible operating system (Windows Server 2008 or Windows 2008 R2), which is required ...
  5. The template (%Name;) is non-customizable. It cannot contain application profiles, SQL Server profiles, or operating system ...
  6. The template (%Name;) must specify the domain administrator credentials if a domain join option is specified in the template. ...
  7. The template (%Name;) network adapter contains inconsistent MAC address types. If the network adapter has a static IP address, ...
  8. The template (%Name;) operating system profile does not have network load balancing and/or network load balancing tools features ...
  9. The template (%Name;) requires deployed virtual machines to have network connectivity with Virtual Machine Manager library ...
  10. The template (%Name;) should contain a SQL Server profile with a SQL Server data-tier application package for successful ...
  11. The template virtual hard disk logical units are not SAN copy capable as logical unit %LogicalUnit; already has maximum number ...
  12. The template virtual hard disk logical units are not SAN copy capable as logical unit %LogicalUnit; is already a snapshot ...
  13. The template virtual hard disk logical units are not SAN copy capable as they belong to different storage pool of same classification. ...
  14. The total number of bytes per second received by the virtual network switch port. This counter is aggregated over a time ...
  15. The total number of bytes per second sent by the virtual network switch port. This counter is aggregated over a time interval. ...
  16. The total number of bytes that have been read per second on this virtual storage device. This counter is aggregated over ...
  17. The total number of bytes that have been written per second on this virtual storage device. This counter is aggregated over ...
  18. The transfer did not succeed. The failure could be due to timeout on the server, client cancelling the job, or client cmdlet ...
  19. The type %ObjectType; is not a scopable type for the user role %Name; because the user role does not have %Permission; permission. ...
  20. The unmanaged Storage Logical Unit %SMLunID;, which is presented to cluster already, is not accessible to host %VMHostName;. ...
  21. The update catalog loads the first 100 updates by latest release date. Use this action to see all updates in the catalog. ...
  22. The use of Consistent Device Naming (CDN) will enable you to easily locate and identify specific network adapters during ...
  23. The user %Name; is not a member of the currently connected user role (%UserRoleName;) or a member of one of the child user ...
  24. The user role member must have an Active Directory Domain Services account. Try the operation again with a valid domain account. ...
  25. The User Role provided is invalid because the Owner ( %UserName; ) of this virtual machine is not a member of the specified ...
  26. The value (%ActualValue;) for property (%PropertyName;) is different from the expected value (%ExpectedValue;) as specified ...
  27. The value for CPUCyclesReservePercent (%PercentageReserve;) cannot be greater than the value for CPUCyclesLimitPercent (%Percentage;). ...
  28. The value for custom property %ParameterName; specified by the host violates a property matching rule for the value %ParameterValue; ...
  29. The value provided for the MAC address is not valid or is an incorrectly formatted address for the VM %VMName; on the %ServerName; ...
  30. The value provided for the MAC address is not valid or is an incorrectly formatted address for the VM %VMName; on the server. ...
  31. The virtual hard disk in the selected host profile may expand beyond its current size, and the selected physical machine ...
  32. The virtual hard disk is not in VHD format or already in VHDX format. Only virtual hard disks of type VHD can be converted ...
  33. The virtual IP (VIP) address (%VIPName;) is not present on the load balancer (%Name;). The VIP address may have been deleted ...
  34. The virtual IP (VIP) address range conflicts with a default gateway or with a reserved IP address for the static IP address ...
  35. The virtual IP (VIP) address that is assigned to a load balancer is the front-end address for a service. The dedicated IP ...
  36. The virtual machine %Name; does not have network connectivity to the library servers to provision the physical resources ...
  37. The virtual machine %VMName; cannot be started because the run under credentials are not valid on the %ServerName; server. ...
  38. The virtual machine %VMName; could not be live migrated to the virtual machine host %VMHostName; using this cluster configuration. ...
  39. The virtual machine %VMName; could not be live migrated to the virtual machine host using this cluster configuration. This ...
  40. The virtual machine %VMName; has Hyper-V replication enabled. Enabling Datacenter Recovery protection on this virtual machine ...
  41. The virtual machine %VMName; is configured as highly available but the selected host does not have high availability services ...
  42. The virtual machine %VMName; is not configured as highly available but the selected host is highly available. The placement ...
  43. The Virtual Machine %VMName; is placed on a SAN which does not support globally unique identifiers for LUNs. SAN transfer ...
  44. The virtual machine %VMName; or one of its checkpoints is configured to use dynamic memory allocation. However, the target ...
  45. The virtual machine %VMName; requires disks from multiple distinct platforms. Virtual machine hosts cannot support multiple ...
  46. The virtual machine %VMName; requires local storage and the most appropriate available destination volume connected to host ...
  47. The virtual machine %VMName; requires recovery protection and isn't configured as highly available but the selected host ...
  48. The virtual machine %VMName; requires shared storage and the most appropriate available destination volume connected to host ...
  49. The virtual machine %VMName; uses a synthetic network adapter or network adapter that is not connected to a logical network. ...
  50. The virtual machine %VMName; uses a synthetic network adapter or network adapter that is not connected to a logical network. ...
  51. The virtual machine (%VMName;) and the virtualization host (%VMHostName;) use processors from different manufacturers. A ...
  52. The virtual machine (%VMName;) and the virtualization host use processors from different manufacturers. A running or saved ...
  53. The virtual machine (%VMName;) cannot be placed on the Hyper-V host (%VMHostName;) because it has checkpoints that are in ...
  54. The virtual machine (%VMName;) cannot be placed on the Hyper-V host because it has checkpoints that are in a format that ...
  55. The virtual machine (%VMName;) could not be live migrated to the virtual machine host (%VMHostName;) using this cluster configuration. ...
  56. The virtual machine (%VMName;) could not be moved using live migration to host because another live migration is in progress. ...
  57. The virtual machine (%VMName;) could not be moved using live migration to the virtualization host (%VMHostName;) because ...
  58. The virtual machine (%VMName;) is not compatible with the virtualization host (%VMHostName;). The virtual machine may not ...
  59. The virtual machine (%VMName;) is not compatible with the virtualization host. The virtual machine may not start or operate ...
  60. The virtual machine (%VMName;) is using processor-specific features not supported on the virtualization host (%VMHostName;). ...
  61. The virtual machine (%VMName;) is using processor-specific features not supported on the virtualization host. To allow for ...
  62. The virtual machine (%VMName;) on the host (%VMHostName;) could not be stored because it has multiple virtual hard disks ...
  63. The virtual machine (%VMName;) violates the maximum memory limit for the virtualization host (%VMHostName;). Maximum memory: ...
  64. The virtual machine (%VMName;) was not moved using live migration to the virtualization host (%VMHostName;) because the operation ...
  65. The virtual machine (%VMName;) was not moved using live migration to the virtualization host because the operation was cancelled. ...
  66. The virtual machine being created from a template must contain at least one virtual hard disk, which must be generalized. ...
  67. The virtual machine configuration %VMName; specifies a host group that does not have access to load balancer %LoadBalancerName; ...
  68. The virtual machine configuration %VMName; specifies a pass-through disk as its source and must use a target disk deployment ...
  69. The virtual machine configuration belongs to a tier that requires a load balancer connected to a single shared host group. ...
  70. The virtual machine configuration could not be added to %ComputerName; because the configuration file %FileName; could not ...
  71. The virtual machine configuration does not have a name. A virtual machine name must be specified in order to determine an ...
  72. The virtual machine configuration targets host group %HostGroupName; and does not have access to required load balancer %LoadBalancerName;. ...
  73. The virtual machine has a network adapter that requires static addresses of both IPv4 and IPv6 address families. When both ...
  74. The virtual machine host %ComputerName; cannot be removed because one or more virtual machines are active on the virtual ...
  75. The virtual machine host group (%Name;) cannot be removed because it is referenced by one or more virtual switch extension ...