System Center Virtual Machine Manager 2012 R2

  1. Installed switch extension (%Name;) with Driver ID (%Id;) and version ( %CurrentVersion;) is not supported by the virtual ...
  2. Installed switch extension (%Name;) with Driver ID (%Id;) and version ( %CurrentVersion;) needs to be updated. Minimum supported ...
  3. Installing the application %Name;, %ObjectType;, on the application host %ComputerName; failed. Detailed error message: %DetailedErrorMessage; ...
  4. Installing this ActiveX control is not supported on a 64-bit browser. Please navigate to this page using a 32-bit browser. ...
  5. Installs a program that allows you to connect to a VMM management server to centrally view and manage resources, such as ...
  6. Installs the Virtual Machine Manager service, which processes commands and controls communications with the VMM database, ...
  7. Instead, transfer the virtual machine over the LAN, or see Virtual Machine Manager Help for information about using a SAN. ...
  8. Invalid Resource Extension found in the Resource Extension package. The Application Payload section with ID = %Id; had a ...
  9. Invalid string format - expected either a well-known name for page size type or two measurement unit values for page width ...
  10. Invalid string format - expected up to three values separated with space symbol. First value represents cap style, second ...
  11. Invalid string format: Expected four measurement unit or percentage values separated with '{0}' symbol. Here is an example ...
  12. Invalid string format: Expected four measurement unit values separated with '{0}' symbol. Here is an example of valid string: ...
  13. Invalid string format: Expected two measurement unit or percentage values separated with '{0}' symbol. Here is an example ...
  14. Invalid string format: Expected two measurement unit values separated with '{0}' symbol. Here is an example of valid string: ...
  15. Invalid string format: Expected two pairs of measurement unit values separated with '{0}' symbol. These values should represent ...
  16. Invalid use of values for the number of columns and for physical disk redundancy while creating the new storage file share ...
  17. IP Address configuration must define the AllocationMethod to be static in the resource definition (%Name;) in order to define ...
  18. IPv4 address range {0} with start IP address {1}, end IP address {2}, managed by {3}, service instance {4} and IP address ...
  19. IPv4 address {0} managed by {1}, service instance {2} and IP address space {3} could not be synchronized with VMM {4}. Additional ...
  20. IPv6 address range {0} with start IP address {1}, end IP address {2}, managed by {3}, service instance {4} and address space ...
  21. IPv6 address {0} managed by {1}, service instance {2} and IP address space {3} could not be synchronized with VMM {4}. Additional ...
  22. is either part of more than one virtual switch or added twice as part of a single team. Make sure the physical network adapter ...
  23. is not a valid IP subnet. The IP subnet must use classless inter-domain routing (CIDR) notation, for example 192.168.1.0/24, ...
  24. License agreement for update %Name; cannot be accepted at this time as the last attempt to download the license agreement ...
  25. Limit the processor features for the virtual machine on the processor tab of the hardware configuration page, and then try ...
  26. Live clone task on this virtual machine %VMName; creates a diff disk for temporary usage but but it didn't get merged back. ...
  27. Load balancer configuration with template name or ID %LoadBalancerName; is connected to a network adapter that has no static ...
  28. Local Administrator Run As account "%Name;" cannot be found. Run As account reference will be removed from VM template %TemplateName; ...
  29. Local Administrator Run As account "%Name;" cannot be found. Run As account reference will be removed from VM template %TemplateName;" ...
  30. Log in by using an account on the same domain as the VMM management server, or by using an account on a domain that has a ...
  31. Logical network (%LogicalNetworkName;) cannot be associated with the host network adapter. The logical network has externally ...
  32. Logical network (%LogicalNetworkName;) is not available on host (%Name;). Logical networks using private VLANs or externally ...
  33. Logical network {0} could not be synchronized with IPAM because some of the objects conflict with IP address spaces in IPAM. ...
  34. Logical switch (%Name;) has extensions in incorrect order. Switch extensions have to be in ordered as follows :- capture ...
  35. Logical unit %LogicalUnit; couldn't be removed because it's in replication group %Name; which is associated with a storage ...
  36. Logical unit %LogicalUnit; couldn't be removed because it's participating in a remote mirror synchronization relationship. ...
  37. Logical unit information will be imported from the selected storage pools. All physical disk information will be imported. ...
  38. Logical unit information will be imported from the selected storage pools. The assigned classification describes the capabilities ...
  39. MAC address spoofing allows virtual machines to change the source MAC address in outgoing packets to one that is not assigned ...
  40. Make sure each of the logical switches used by the specified set of network adapters is connected to at least one physical ...
  41. Make sure either a MAC address or a Consistent Device Name for each physical network adapter that uses static IP configuration, ...
  42. Make sure that all the clouds of the protected VMs on the source host cluster/host group can be found in the target host ...
  43. Make sure that the account %AccountName; is added to the local Administrator's group on %ComputerName; otherwise VMM server ...
  44. Make sure that the boot disk is specified correctly. The boot disk volume parameter is expected to end with the disk number. ...
  45. Make sure that the computer name is correct, the computer is reachable, and that the required firewall exceptions were added. ...
  46. Make sure that the Hyper-V Replica Broker resource is dependent on a Network Name resource which was acting as its Client ...
  47. Make sure that the Hyper-V Replica Broker resource is dependent on a single Network Name resource which was acting as its ...
  48. Make sure that the specified account can be converted to a GUID if it is a Run As account. If it refers to a service setting, ...
  49. Make sure that the value of VMNetworkServiceSetting contains matching service setting delimiters '@' and refers to exactly ...
  50. Make sure the assignment scope to be assigned to the baseline is not already assigned to the baseline and retry the operation. ...
  51. Make sure the Consistent Device Name and the MAC address are correct, or specify only one of them, then try the operation ...
  52. Make sure the name of service setting has no leading or trailing spaces or periods, and has a length less than 256 characters. ...
  53. Make sure the number of physical network adapters on the computer is greater than or equal to the number of adapters that ...
  54. Make sure the updated reserved virtual IP address range contains all currently allocated virtual IP addresses, or release ...
  55. Make sure the virtual IP (VIP) address range does not contain a default gateway or a reserved IP address and then try again. ...
  56. Make sure there is sufficient disk space on the disk that has the remote installation folder on the PXE server (%ServerName;), ...
  57. Manually grant permissions of the host account to the ISO file, or detach the ISO from the VM and then try the operation ...
  58. Manually register the share to the host through the VMM Admin Console or use the Register-SCStorageFileShare cmdlet, or refresh ...
  59. Manually update the NTFS permissions for the share from the file share properties, or run the Windows PowerShell command ...
  60. Members in this group have permissions to administer virtualization resources on this machine using Virtual Machine Manager ...
  61. Members of the user role will continue having access to the already received resources and the change in permission will ...
  62. Members of VMM user roles may not have remote access to virtual machines that already exist on the selected Hyper-V hosts. ...
  63. Membership in the Administrators, Power Users, Print Operators, or Server Operators group on %ComputerName; is required to ...
  64. Microsoft .NET Framework 4 was not successfully installed. The selected Virtual Machine Manager feature cannot be installed ...
  65. Microsoft Azure Site Recovery couldn't be configured for the cloud. The cloud doesn't contain a Hyper-V host server running ...
  66. Microsoft Azure Site Recovery couldn't be disabled for cloud %CloudName; because the cloud is either protected or acting ...
  67. Microsoft Azure Site Recovery couldn't be enabled for the cloud. A cluster doesn't have the Hyper-V Cluster Broker role enabled, ...
  68. Microsoft Azure Site Recovery protection could not be enabled. In the properties of this virtual machine, the operating system ...
  69. Microsoft Azure Site Recovery protection could not be enabled. In the properties of this virtual machine, there is no disk ...
  70. Microsoft Online Services Sign-in Assistant is not installed. Please install Microsoft Online Services Sign-in Assistant ...
  71. Microsoft Update offers security and important updates for Windows and other Microsoft software, including System Center ...
  72. Microsoft Update offers security and important updates for Windows and other Microsoft software, including System Center ...
  73. Microsoft Visual C++ 2010 Redistributable was not successfully installed. The selected Virtual Machine Manager feature cannot ...
  74. Migrate the recovery VM to a host with version newer than or equal to %TargetHostVSVersion; or select the most suitable host ...
  75. Migrate the virtual machine to a host that supports the conversion of pass-through disks and then try the operation again. ...