System Center Virtual Machine Manager 2012 R2

  1. A storage logical unit name can only contain alpha-numeric characters. Check the storage logical unit name and then try the ...
  2. A synchronization error has occurred while synchronizing the VMM subnet {0} with IPAM in the logical network definition {1}. ...
  3. A thin provisioning alert threshold cannot be set on storage pool %StoragePool; because it is not a Windows-based file server. ...
  4. A virtual hard disk %FileName; cannot be attached to the same virtual machine or template more than once directly or via ...
  5. A virtual hard disk image size cannot be larger than 2,088,960 MB. A FAT16 virtual hard disk image size cannot be greater ...
  6. A virtual IP (VIP) address with the specified name (%VIPName;) or address (%IPAddress;) already exists on the load balancer ...
  7. A virtual IP (VIP) address with the specified name (%VIPName;) or address (%IPAddress;) already exists on the load balancer ...
  8. A virtual IP (VIP) address with the specified name or address already exists on the load balancer for this VmRole. Ignoring ...
  9. A virtual IP (VIP) address with the specified name or address already exists on the load balancer. Contact your VMM administrator ...
  10. A virtual IP template contains load balancer-related configuration settings for a specific type of network traffic. The virtual ...
  11. A virtual machine connection token cannot be generated because VMM is not configured with a valid virtual machine connection ...
  12. A virtual machine connection token cannot be generated for virtual machine %Name;. Contact your administrator to connect ...
  13. A virtual machine could not be started because its resource allocation exceeds the amount of host resources available on ...
  14. A Virtual Machine Manager feature must be specified in the command line. For help, type setup.exe /? and then press Enter. ...
  15. A virtual machine must be in either the Poweroff, Saved, or Stored state to change the RunGuestCredential virtual machine ...
  16. A virtual machine that uses Hyper-V Recovery Manager can only be deployed to a cloud, but no clouds are available. This virtual ...
  17. A virtual machine with name %VMName; cannot be deployed to host %VMHostName; because the host virtualization platform does ...
  18. A virtual NIC Ethernet address cannot be set if the NIC has a dynamic Ethernet address on the %ServerName; server. To set ...
  19. A Virtual SAN must have at least one adapter in order to be usable by virtual machines. Delete this Virtual SAN if you do ...
  20. A virtual switch cannot be created from the logical switch {0} because all the uplink port profiles in this logical switch ...
  21. A virtual switch with the given ID could not be found on the %ServerName; server. This virtual switch might be required as ...
  22. A VM Network gets the PAIPAddressPoolType value from the logical network. Do not specify the PAIPAddressPoolType parameter. ...
  23. Activating a zoneset may cause some downtime in the fabric until all changes are propagated to the switches. Do you want ...
  24. Add %UserName; as a member of the specified user role or provide a different user role, and then try the operation again. ...
  25. Add a DVD drive to the virtual machine or modify the bus assignments or volume selection to create space on the IDE bus so ...
  26. Add a transient network adapter to the specified set, or use a management network adapter that is not a virtual network adapter. ...
  27. Add a value to the -SourceNetworkConnectionID parameter to specify the network connection name or the MAC address of a TCP/IP ...
  28. Add a value to the -VolumeDeviceID parameter to specify a drive letter or name (in \?\Volume{GUID}\ format) of a volume that ...
  29. Add the library server without adding any library shares. Once that task has completed successfully add the library shares. ...
  30. Add the missing Sysprep binaries for the specified Windows version in the specified folder, and then try the operation again. ...
  31. Add the missing Sysprep parameter either to the answer file or to the operating system configuration, and then try the operation ...
  32. Add-in importing has been disabled due to an error while initializing the add-in pipeline. You must restart the Admin Console ...
  33. Adding a load balancer requires VIP templates to be defined in the system. Go to the Networking node in the Fabric view and ...
  34. Adding a vCenter Server does not automatically add ESX hosts to VMM. To manage ESX hosts through VMM, you must add the vCenter ...
  35. Adding initiator %InitiatorName; to storage group %StorageGroupName; failed with error code %StorageErrorCode;. %StorageErrorMessage; ...
  36. Adding load balancers requires the existence of configuration providers associated with them. You will need to install them ...
  37. Adding storage logical units %LogicalUnits; to storage group %StorageGroupName; failed with error code %StorageErrorCode;. ...
  38. Adding target %TargetName; to storage group %StorageGroupName; failed with error code %StorageErrorCode;. %StorageErrorMessage; ...
  39. Adding the share (%ShareName;) to the library server (%ServerName;) will create a duplicate share path which conflicts with ...
  40. Adding the specified host groups to the load balancer (%Name;) would result in overlapping network-settings-accessible host ...
  41. Adding the specified host groups to the logical switch (%Name;) would result in overlapping network-settings-accessible host ...
  42. Adding the specified host groups to the MAC address pool (%Name;) would result in overlapping network-settings-accessible ...
  43. Adding the specified host groups to the network service (%Name;) would result in overlapping network-settings-accessible ...
  44. Adding the specified host groups to the network site (%Name;) would result in overlapping network-settings-accessible host ...
  45. Adding the specified host groups to the virtual switch extension manager (%Name;) would result in overlapping network-settings-accessible ...
  46. Adding the storage provider %ProviderName; is unsupported because the cluster is running Windows Server 2012 R2, and the ...
  47. Adding virtual switch extension managers requires the existence of configuration providers associated with them. You need ...
  48. Addition of physical disks to storage pool %StoragePool; failed with error code %StorageErrorCode;. %StorageErrorMessage; ...
  49. Additions are not installed in this virtual machine, or the virtual machine has never been started on the %ServerName; server. ...
  50. Additions feature is not available; either Additions are not installed or the feature has been disabled on the %ServerName; ...
  51. After %Name; (%Value;) is created, the Delegated Administrator will not be able to edit it because of host group scoping. ...
  52. After %Name; (%Value;) is updated, the Delegated Administrator will not be able to edit it because of host group scoping. ...
  53. After cluster creation completes, local storage discovery will import physical disk, storage pool, and virtual disk information. ...
  54. After deployment, the servers will be clustered. The selected profile provides the administrator Run As account and the domain ...
  55. After resolving the problem, retry the operation or copy the files required for virtualization manually. Then use the add-patch ...
  56. After the following resources are removed, you will not be able to manage these resources using Virtual Machine Manager. ...
  57. After the following resources are removed, you will not be able to manage these resources using Virtual Machine Manager. ...
  58. After the following resources are removed, you will not be able to manage these resources using Virtual Machine Manager. ...
  59. After VMM for System Center 2012 R2 is installed, you need to perform additional tasks in order to complete the upgrade to ...
  60. After you add an infrastructure server to VMM, you can manage updates to that server by using a WSUS server (update server) ...
  61. After you delete the exemption for this update, the update can be installed on the resource. Are you sure you want to continue? ...
  62. After you select an add-in, you will be informed whether or not the files it contains are valid. If there are no validation ...
  63. Agent communication is blocked. On %ComputerName;, the version of virtualization software or the VMM agent is unsupported. ...
  64. Agent installation failed on %ComputerName; because the supported version of Windows Remote Management (WinRM) is not installed. ...
  65. Agent Service Run As account %RunAsAccountName; cannot be located for SQL Server deployment %Name; on template %TemplateName; ...
  66. All binding parameters (-IDE or -SCSI, -Bus, -LUN) have to be specified as a set and accompany the -VolumeDeviceID parameter. ...
  67. All changes and checkpoints for this virtual machine made after checkpoint %CheckpointName; will be lost after using this ...
  68. All checkpoints created after the selected checkpoint will also be removed. After being removed, checkpoints cannot be used ...
  69. All physical computer profiles used for a scale-out file server cluster must use virtual hard disks with Windows Server 2012 ...
  70. All protected virtual machines must be removed from host groups in the private cloud before the host group can be removed. ...
  71. All template virtual hard disks are not present on SAN copy capable logical units, hence template is not SAN copy capable. ...
  72. All virtual IP (VIP) addresses in the address pool have been used. Contact your VMM administrator for details about this ...
  73. All virtual machines in the same computer tier must specify either a cloud or host group scope. The virtual machine %VMName; ...
  74. All virtual machines in the same computer tier must specify either a cloud or host group scope. The virtual machine %VMName; ...
  75. All virtual machines in the same computer tier must specify either a cloud or host group scope. The virtual machine '%VMName;' ...