System Center Virtual Machine Manager 2012

  1. Specify the addresses for the load balancers you want to use. Use commas or line breaks to separate your entries. Valid addresses ...
  2. Specify the computer name for this virtual machine. No wild cards are allowed. This name is not required to match the virtual ...
  3. Specify the distinguished name for the container and verify that you have GenericRead|CreateChild|WriteProperty rights on ...
  4. Specify the domain that the virtual machine host should join. To join a domain, the computer must have at least one network ...
  5. Specify the encryption key, security file location, and the preferred host group destination for each computer, and then ...
  6. Specify the port classification for the virtual port. For each switch extension associated to the logical switch, one port ...
  7. Specify the reserved IPv4 addresses. Use commas to separate multiple addresses. Ranges of the format IP1-IP2 are allowed. ...
  8. Specify the reserved IPv6 addresses. Use commas to separate multiple addresses. Ranges of the format IP1-IP2 are allowed. ...
  9. Specify the root management server (RMS) to use, and enter the administrative credentials for the management group to which ...
  10. Specify the Run As account to use to discover computers and, when needed, to add the Hyper-V role and deploy the Virtual ...
  11. Specify the Run As account with sufficient privileges to configure load balancers. These credentials will be used to configure ...
  12. Specify the video adapter that this virtual machine should use. The Microsoft RemoteFX 3D video adapter allows you to set ...
  13. Specify the VMM server that the Self-Service portal will connect to, and the port it will use to communicate with the VMM ...
  14. Specify unattend.xml format answer file for a Windows 2008 or Vista template, or a GuestOSProfile. Otherwise specify sysprep.inf ...
  15. Specifying a lower memory priority for this virtual machine might prevent it from starting when other virtual machines are ...
  16. SQL Server data-tier application deployments cannot have over the maximum number (%MaxLimit;) of SQL Server script commands ...
  17. SQL Server data-tier application framework of the required version (%SoftwareVersion; or higher) is not installed on the ...
  18. SQL Server script command execution requires tool sqlcmd. Install SQL Server Client Tools and ensure that sqlcmd.exe location ...
  19. SQL Server Service Run As account %RunAsAccountName; cannot be located for SQL Server deployment %Name; on template %TemplateName; ...
  20. SR-IOV allows a device, such as a network adapter, to gain direct access to physical networks adapters that support SR-IOV. ...
  21. Sriov property (%Name;) cannot be changed on this logical switch because there are VirtualNetworkAdapterPortProfileSets that ...
  22. Start point coordinates of the first item in 'primitives' and end point coordinates of the last item in 'primitives' must ...
  23. Start the service locally in the Services MMC snap-in by running services.msc on %ComputerName;, choose the service %ServiceName;, ...
  24. Static IP address pools require the existence of logical networks. Create a logical network before creating a static IP address ...
  25. Static IP address pools require the existence of VM networks. Create a VM network before creating a static IP address pool. ...
  26. Static IP could not be set on the Host Virtual Network Adapter (%Id;) on Host %ServerName; (WMI Method: %WMIMethodName;, ...
  27. Stop the service locally in the Services MMC snap-in by running services.msc on %ComputerName;, choose the service %ServiceName;, ...
  28. Stop, shut down, or save the virtual machine. If the virtual machine is in a failed state, use "Repair virtual machine" to ...
  29. Stopping a virtual machine causes a loss of service to any users of the machine. You have chosen to stop the following virtual ...
  30. Stopping this virtual machine will cause a loss of service to all users of this virtual machine. Do you want to continue? ...
  31. Storage classification "%Name;" cannot be found. Storage classification reference will be removed from disk (%BusType;, %Bus;, ...
  32. Storage discovery of provider %ProviderName; for user %UserName; failed from %ComputerName; with error code %StorageErrorCode;. ...
  33. Storage logical unit %LogicalUnit; cannot be de-allocated from host group %HostGroupName; as logical unit is already in use. ...
  34. Storage logical unit %LogicalUnit; has been allocated to host group %HostGroupName; where none of the hosts in host group ...
  35. Storage pool %StoragePool; has been allocated to host group %HostGroupName; where none of hosts in host group has access ...
  36. Stores the virtual machine in the library for later use. Before you can start the virtual machine, you must deploy it on ...
  37. Storing the virtual machine in the library is disabled because the virtual machine hardware configuration contains passthrough ...
  38. Support from a physical network adapter and the guest operating system is required to offload IPsec tasks. When sufficient ...
  39. System Center Datacenter Recovery Provider Registration is not done or registration information is not valid, so System Center ...
  40. System Center Datacenter Recovery Provider Subscription ID found in the VMM Database is not valid, SubscriptionID found in ...
  41. System Center Datacenter Recovery setting changes to the service tier template (%Name;) during servicing are not supported ...
  42. System Center Virtual Machine Manager Workgroup Edition cannot manage more than five hosts. The specified Virtual Machine ...
  43. Template document clipping has more than one element. Template instance type cannot be assigned to this template. Remove ...
  44. Tenant administrators manage self-service users and VM networks. Tenant administrators create, deploy, and manage their own ...
  45. The %ObjectType; %FileName; was not attached to %ObjectType2; %ObjectName; because %FileName; is already being managed as ...
  46. The %ObjectType; %FileName; was not attached to %ObjectType2; %ObjectName; because of errors encountered while attempting ...
  47. The -HostDrive and -AnyHostDrive parameters are mutually exclusive. You can specify a value for either the -AnyHostDrive ...
  48. The -ISO and -HostDrive parameters are mutually exclusive. You can specify a value for either the -ISO parameter or the -HostDrive ...
  49. The -LibrarySharePath parameter cannot be used for Set-VMMUserRole with an Administrator or Delegated Administrator profile. ...
  50. The -PendingServiceTemplate, -CommitPendingServiceTemplate and -DismissPendingServiceTemplate parameters are mutually exclusive. ...
  51. The -RemoveQuotaPoint parameter cannot be used for Set-VMMUserRole with an Administrator or Delegated Administrator profile. ...
  52. The -VirtualFloppyDisk and -HostDrive parameters are mutually exclusive. You can specify a value for either the -VirtualFloppyDisk ...
  53. The -VirtualHardDisk and -PassThroughDisk parameters are mutually exclusive. You can specify only one of these parameters. ...
  54. The above provided credentials or Run As account should be a local administrator on the host machines. If a Run As account ...
  55. The above provided Run As account should be a local administrator on the host machine. It will be used while adding the host ...
  56. The Adapter requires that the VMM is registered with the Disaster Recovery Service Portal. You can launch this setup at a ...
  57. The addition of SCSI adapters to the service tier template (%Name;) is allowed during servicing. Any other changes to SCSI ...
  58. The address protocol version of the reserved IP addresses does not match the address protocol version of the static IP address ...
  59. The address protocol version of the virtual IP (VIP) addresses does not match the address protocol version of the static ...
  60. The address range of the pool (%Name;) could not be updated because the requested range would not contain the currently allocated ...
  61. The agent cannot be uninstalled remotely from %ComputerName; without specifying administrator privileges for the machine. ...
  62. The agent is not responding on the perimeter network machine %ComputerName; because either the agent is not installed; or ...
  63. The agent version on (%ComputerName;) has a schema version that is incompatible with Virtual machine manager. The Agent cannot ...
  64. The allocated virtual IP address (%Address;) is not contained in the virtual IP address range. The reserved virtual IP address ...
  65. The application (%Name;, %ObjectType;) restore state operation failed on the virtual machine (%ComputerName;). Detailed error ...
  66. The application (%Name;, %ObjectType;) save state operation failed on the virtual machine (%ComputerName;). Detailed error ...
  67. The application package (%PathName;) is not valid and is ignored for importing. Detailed error message: %DetailedErrorMessage;. ...
  68. The application packages are not identical (for example, package name, version, settings, and so on) and cannot be marked ...
  69. The application packages are not identical (for example, package name, version, settings, and so on) to existing equivalent ...
  70. The application profile name change during the servicing will be ignored. Previous name: %Name; Current name: %FriendlyName; ...
  71. The assembly "{0}" referenced by the add-in assembly "{1}" could not be found in the add-in package. Make sure that this ...
  72. The assembly "{0}" referred to by add-in component "{1}" could not be found in the add-in package. This could be due to the ...
  73. The BITS client job failed to succeed for %ResourceName; resource with following error: %DetailedErrorMessage; Error context: ...
  74. The BITS client job failed to succeed for %ResourceName; when attempting %CmdletName; resource with following error: %DetailedErrorMessage; ...
  75. The BMC address %VMHostName; returned a malformed message during an out of band management operation using IPMI. A required ...