System Center Virtual Machine Manager 2012 R2

  1. Virtual Machine Manager console is not supported on this operating system. For more information, see 'Supported Operating ...
  2. Virtual Machine Manager could not connect to source computer %ComputerName; after it restarted into Windows PE (temporary ...
  3. Virtual Machine Manager could not connect to the physical-to-virtual source computer %ComputerName; after it restarted to ...
  4. Virtual Machine Manager could not convert %ComputerName; because Virtual Server, on host %VMHostName;, does not support running ...
  5. Virtual Machine Manager could not place this virtual machine on host %VMHostName; because the host does not have any default ...
  6. Virtual Machine Manager could not place this virtual machine on host %VMHostName; because there are no default virtual machine ...
  7. Virtual Machine Manager could not place this virtual machine on host %VMHostName; because there are no volumes available ...
  8. Virtual Machine Manager could not place this virtual machine on the virtualization host (%VMHostName;) because remote connections ...
  9. Virtual Machine Manager could not query Active Directory Domain Services. The fully qualified domain name (%DomainName;) ...
  10. Virtual Machine Manager detected that the library server %ComputerName; is a clustered file server. Virtual Machine Manager ...
  11. Virtual Machine Manager detected that the library server %ComputerName; is a failover cluster node. If you want to add clustered ...
  12. Virtual Machine Manager does not support creation of highly available virtual machines for the virtualization software on ...
  13. Virtual Machine Manager does not support creation of highly available virtual machines for the virtualization software on ...
  14. Virtual Machine Manager does not support updating or re-associating an agent on a host that is in a non-trusted domain or ...
  15. Virtual Machine Manager encountered an error while connecting to the agent after restarting the computer %ComputerName; into ...
  16. Virtual Machine Manager encountered an error while connecting to the agent after restarting the computer (%ComputerName;) ...
  17. Virtual Machine Manager failed to connect to the virtual machine because of a socket connection error. Check the firewall ...
  18. Virtual Machine Manager failed to connect to the virtual machine because the connection timed out while attempting to connect. ...
  19. Virtual Machine Manager failed to connect to the virtual machine because the guest operating system's computer name (%ComputerName;) ...
  20. Virtual Machine Manager failed to connect to the virtual machine because the guest operating system's computer name (%ComputerName;) ...
  21. Virtual Machine Manager failed to connect to the virtual machine because the host name (%VMHostName;) could not be resolved ...
  22. Virtual Machine Manager failed to create the Windows Remote Management (WinRM) listener because there is already an existing ...
  23. Virtual Machine Manager failed to remove the Secure Sockets Layer (SSL) certificate with thumbprint %CertificateHash; obtained ...
  24. Virtual Machine Manager has aborted the request from computer with SMBIOS GUID: %SMBIOSGUID; MAC: %MACAddress; and will not ...
  25. Virtual Machine Manager has accepted the request from computer with SMBIOS GUID: %SMBIOSGUID; MAC: %MACAddress; and will ...
  26. Virtual Machine Manager has added the Secure Sockets Layer (SSL) certificate with thumbprint %CertificateHash; obtained from ...
  27. Virtual Machine Manager has detected more than one network adapter named %FriendlyName; on host %VMHostName;. Information ...
  28. Virtual Machine Manager has detected more than one network adapter on a particular host. Information collected about this ...
  29. Virtual Machine Manager has detected more than one network adapter on the particular host. Information collected about this ...
  30. Virtual Machine Manager has detected more than one network adapter with the same name. Contact your SCVMM Administrator for ...
  31. Virtual Machine Manager has detected more than one network adapter with the same name. For more details, please refresh host ...
  32. Virtual Machine Manager has detected more than one network adapter with the same name. For more details, please refresh host ...
  33. Virtual Machine Manager has detected that %ComputerName; is a node of a failover cluster. You cannot add a cluster node as ...
  34. Virtual Machine Manager has detected that %ComputerName; is either a Windows Server 2008 (or later) failover cluster or a ...
  35. Virtual Machine Manager has detected that the following features are already installed on this machine. These features will ...
  36. Virtual Machine Manager is about to power off the selected hosts. It is advisable to put the hosts in maintenance mode before ...
  37. Virtual Machine Manager is about to power off this host. It is advisable to put the host in maintenance mode before this ...
  38. Virtual Machine Manager is about to restart the operating system on the selected hosts. It is advisable to put the hosts ...
  39. Virtual Machine Manager is about to restart the operating system on this host. It is advisable to put the host in maintenance ...
  40. Virtual Machine Manager is about to shut down the operating system on the selected hosts. Virtual machines on the hosts will ...
  41. Virtual Machine Manager is about to shut down the operating system on this host. Virtual machines on the host will be turned ...
  42. Virtual Machine Manager is not able to use Hyper-V on host %ComputerName;. You must accept the Microsoft Software License ...
  43. Virtual Machine Manager is unable to add the cluster %ComputerName; as a clustered host because the operating system is not ...
  44. Virtual Machine Manager is unable to add the server %ComputerName; as a managed computer because the operating system is ...
  45. Virtual Machine Manager is unable to emulate the exact configuration of the source machine %ServerName;. The number of virtual ...
  46. Virtual Machine Manager is unable to find a value for one or more required Sysprep parameters, such as FullName, ComputerName, ...
  47. Virtual Machine Manager is unable to find host %ComputerName;. The specified computer name contains characters that are not ...
  48. Virtual Machine Manager is unable to update the operating system of the source VMware virtual machine %VMName;. The operating ...
  49. Virtual Machine Manager lost the connection to the virtual machine because this session was disconnected by a remote user. ...
  50. Virtual Machine Manager lost the connection to the virtual machine for one of the following reasons: Another connection was ...
  51. Virtual Machine Manager must shut down the following virtual machines to create the new checkpoint: %ObjectList;. Do you ...
  52. Virtual Machine Manager requires a computer that is a member of a domain. Join this computer to a domain, and then run Setup ...
  53. Virtual Machine Manager server is not supported on this operating system. For more information, see 'Supported Operating ...
  54. Virtual Machine Manager was not able to delete management pack "%Name;" since the management pack is currently not imported. ...
  55. Virtual Machine Manager was not able to retrieve PRO tips from Operations Manager. Operation failed with error: %ActualException; ...
  56. Virtual Machine Manager was unable to create a new file share %ShareName; with local path %SharePath; on %ComputerName;, ...
  57. Virtual Machine Manager was unable to create a new file share with %ShareName; and local path %SharePath; on %ComputerName;. ...
  58. Virtual Machine Manager was unable to create a StoredVMs folder in the writable share path in the private cloud (%CloudName;). ...
  59. Virtual Machine Manager will not convert disk to %PartitionStyle; as the disk contains one or more partitions. This is done ...
  60. Virtual Machine Manager will not deploy an OS to computer with SMBIOS GUID: %SMBIOSGUID; MAC: %MACAddress; because the GUID ...
  61. Virtual Machine network adapter can not be attached to Virtual Switch because the DHCP Server is not enabled on the Virtual ...
  62. Virtual machines being deployed to XenServer hosts from VM Templates require associated XenServer metadata to report the ...
  63. Virtual machines being deployed to XenServer hosts require source XenServer metadata to report the XenServer tools as running. ...
  64. Virtual machines can directly connect to this logical network using the VM network "{0}". You can manage this VM network ...
  65. Virtual machines cannot be transferred from hosts on perimeter networks because of security concerns. For more information ...
  66. Virtual network adapter extension port profile (%Name;) already supplies values for Hyper-v virtual port settings. As a result, ...
  67. Virtual network adapter extension port profile (%Name;) cannot be updated to supply Hyper-v virtual port settings since it ...
  68. Virtual Server cannot be installed because the driver for mounting virtual hard disks (vhdstor) is present on %ComputerName;. ...
  69. Virtual switch (%Name;) is not highly available because the switch in host (%VMHostName;) is not compatible with other hosts. ...
  70. Virtual switch (%Name;) may become not highly available if the host (%VMHostName;) is brought online or moved out of maintenance ...
  71. Virtual switch (%Name;) may become not highly available if the host (%VMHostName;) is brought online or moved out of maintenance ...
  72. Virtual Switch (%Name;) was not associated with logical switch (%LogicalSwitchName;) because the host is not in scope of ...
  73. Virtual switch extension manager (%Address;) specified a network site (logical network definition) that is not isolated. ...
  74. Virtual Switch extension manager does not support specifying subnet and subnet is specified or requires subnet and none specified ...
  75. Virtual switch high availability across cluster has changed. Unable to update host (%Name;) because of error %DetailedErrorMessage; ...