Microsoft won't let you achieve your step; so address your goal instead.
Microsoft erroneously conflates has an EFI partitioned hard disc with has EFI firmware. This is, of course, clearly wrong. It's quite possible — and indeed is becoming ever more desirable these days — to have an EFI partitioned disc on a machine that has old non-EFI firmware. You actually — although it took over a fortnight for people here to wring the goal out of you rather than the step — want the converse. You want to have an old PC/AT-style MBR partitioned disc on a machine that has EFI firmware. (EFI firmware itself has no problem with either partition table format, and is indeed required by the EFI specification to understand both. It's Microsoft that makes this error.) And you want this because someone else's software cannot understand the EFI partition table.
One of the several consequences of Microsoft's error is that the Windows NT 6.1 installer has to be invoked from an install medium that has in turn been bootstrapped from old PC98 firmware, in order for it to accept the idea of installing Windows NT 6.1 to a disc partitioned with the old PC/AT MBR partitioning scheme. Unfortunately, if the Windows NT install disc is bootstrapped in the new EFI way the installer will think that there's EFI firmware, and so declare that it cannot be installed to non-EFI partitioned hard discs.
As Weaver has pointed out, and as the Microsoft documentation explains, the installation CD-ROM is in fact dual-boot. As Rod Smith further explains, one therefore can manually construct a Windows NT 6.1 install disc that bootstraps in the old PC98 way. The Windows NT 6.1 installer will then allow installation to an old PC/AT MBR partitioned hard disc.
However, on systems lacking a compatibility support module, as you say your system does, this will not help one whit. Your system will require the EFI version of Microsoft's Boot Manager, installed on the EFI System Partition, because that's how your firmware will try to bootstrap the operating system. But when the Windows NT 6.1 installer is started on non-EFI firmware, it installs the non-EFI version of Microsoft's Boot Manager and won't create an EFI System Partition. Such an installation will not actually bootstrap on your machine, and you won't even be able to complete the installation procedure. Indeed, because you lack a CSM you won't even be able to begin the installation procedure, because you won't even be able to bootstrap the installation disc in the old PC98 way. Microsoft won't let you achieve your step, two times over.
So focus on your goal, instead. Your goal is to enable your customer to deploy Windows Server 2008 onto machines that have EFI firmware from a system image. Therefore the correct question that you should be asking — of the software vendor — is how to get that old/broken disc imaging software fixed so that it has no trouble with the EFI partition table.
Well, after much searching, experimentation, and general frustration, I have basically come to the conclusion that Hyper-V does not currently support UEFI guests, even if the Hyper-V server is running in UEFI configuration.
This seems to be supported by the fact that that recent builds of Windows Blue have what they call "Generation 2" VM's that include UEFI support, based on this article:
http://www.chris123nt.com/2013/04/23/windows-8-1-blue-build-9369-hyper-v-uefi/
Sad really that there's been so much misinformation about this floating about, with so many people insisting UEFI works for guests, but I can find no way to make that happen.
EDIT:
Since this question was asked, Microsoft released Windows Server 2012 R2, which supports the Generation 2 VM's, which do in fact support UEFI for guests.
Best Answer
This is, in fact, possible:
gdisk
on it. I used a CentOS 7 Core installation and used recovery mode. I did this by editing the grub boot options and tacking onrescue
to the end.gdisk
on the disk with Windows installed. See the gdisk docs for more info.repair your computer
option.At this point, I had to load the VMWare PVSCSI drivers, and already had the floppy with the drivers mounted. To do this, you can run
drvload A:\AMD64\PVSCSI.INI
. Alternatively, you can go through the initial Windows setup, and load the drivers via the GUI. You may then back out and click theRepair your computer
link.Run the following commands to (with luck) restore the boot loader:
Note that your mileage may vary, and I would definitely at least snapshot the VM before doing this, but a full backup is better.