I'm trying to install Server 2008 Standard on my ProLiant DL160 running ESXi 3.5.
I've been using ESXi for awhile now and have purchased HP servers with Windows Server media before but this is the first time purchasing Server 2008. When I try installing, once the initial file copy is completed and the server reboots I get an error saying:
HP Support was useless on this issue; I'm pretty sure the installation is trying to see the bios to make sure it's running on a ProLiant server before installing but ESXi doesn't pass that data to it and the installation fails.
Any suggestions? I'd rather not try and deal with an RMA process with Server 2008 and then have to buy the retail version.
It's Windows 64bit ??? Did you enabled Virtualization in BIOS-> Advanced Options?
If you found this information useful, please consider awarding points for "Correct" or "Helpful". Thanks!!!
First time i got, windows setup error. After that I enabled Intel VT en Execute Bit.
I'm trying to install SBS2008 (x64) and i choose Windows server 2008 x64 template.
Setup stops with a HP logo showing "This system is not supported platform".
The problem is HP ROK searches for HP BIOS.
The SMBIOS.reflectHost = "true" did not solve the problem for me.
But I did actually figure out a way around this problem.
I downloaded w2008Server trial iso from microsoft.com, installed it with the serials supplied with the HP OEM media.
I have the same problem. HP DL360 G5 with HP OEM Windows 2008 Standart.
Same message .... platform not supported.
Adding string SMBIOS......=true didn't help.
I have ESXi 3.5 U3. Intel VT in BIOS is enabled.
Option to use MS W2K8 trial with HP OEM software key is not a licensed option i guess :((((
I don't know how it is with the server 2008 std. trial CD. But the SBS 2008 trial DVD is just a normal OEM DVD and if you give a correct product key it just install a normal OEM instead of the trial.
So just try it with that option, i don't see why this would be a license problem.
I ran into this when I converted an HP Workstation. Its weird but looks like someone went through the trouble to create an utility, it worked for VMware Workstation.