Mike has been knocking issues out of the park. Here's a tip that might help during SCVMM install. He's seen this a few times... Thanks Mike!
Unable to complete VMM2008 installation
“Microsoft System Center Virtual Machine Manager 2008 has stopped working"
Things to check
1. Is the account used to install VMM2008 a member of local admins group? http://technet.microsoft.com/en-us/library/cc764327.aspx
2. Is the server in a disjointed name space? http://technet.microsoft.com/en-us/library/cc764231.aspx
3. Is the functional level of the domain is either W2K3 or W2K8? This is a hard requirement. http://blogs.technet.com/chengw/archive/2008/06/04/managing-hosts-in-windows-2000-ad-forest-by-using-vmm-2008.aspx
>>> ServerSetup.log <<<
[12/8/2008 10:07:26 AM] * Exception : => ‘my-computer-name’ is not a valid network computer name.Only fully qualified domain names and NETBIOS computer names are valid. An IP address is valid only for hosts on a perimeter network, ESX hosts, and hosts joined to the domain by using an IPv6 address. Check the computer name, and try the operation again. Microsoft.VirtualManager.Utils.CarmineException: ‘my-computer-name’ is not a valid network computer name.
Only fully qualified domain names and NETBIOS computer names are valid. An IP address is valid only for hosts on a perimeter network, ESX hosts, and hosts joined to the domain by using an IPv6 address. Check the computer name, and try the operation again.
*** Carmine error was: ComputerNameInvalid (403)
The computer name of the server intended to become the VMM2008 server was "MY-COMPUTER-NAME”. We renamed to "MYCOMPUTERNAME" and also removed the corresponding entry in the local HOSTS file. This allowed the installation to complete as expected.
Technorati Tags: microsoft,scvmm,hyper-v,virtual,virtualization,windows
PingBack from http://domaintalk.hilium.com/2009/01/01/contributing-engineer-installation-error-computernameinvalid-403/
I am installing on a box with dual interfaces, and the local host file had a non-qualified entry pointing to the secondary interface. Deleting this entry from the host file solved the issue.