So, my latest secondment job contains working for a major enterprise company for some months now were I’m involved in a major deployment project for 22k computers and we are going to use MDT 2012, I tought it would be better for me to turn MDT 2012 inside out! Next to the working thingy, I also help people who may have computer problems or are willing to buy a new computer. Most of the people I help are elderly and they just want a computer that works, is value for money and comes without the hassle of a slick sales person at the local electronics store.
Because I already installed several of the same computer types manually I wanted to use MDT 2012 since it is released this april’2012. Because ‘if you do things more then once, you can automate it’ some wise person once said.
When using MDT 2012 and creating a reference image the right way (like, building the ultimate ‘image’ in a virtual machine) to deploy it later on to targetted computers I encountered a problem I could not foresee earlier. UEFI Bios, the new computers that I deliver have UEFI Bios, and the great thing about UEFI Bios is that it needs GPT partition’s to be present or to be created at the hard drive. The great thing about Windows 7 is that it knows how to deal with the situation and it will be able to install itself problem free on a computer with an UEFI interface (stop calling the darn thing UEFI BIOS).
So now to create a reference image that is also capable of dealing with the UEFI requirements we need to create a virtual machine with UEFI instruction.
To do this, you can create a new virtual machine template from lets say a Windows 7 machine. (I use VMware workstation)
When the virtual machine is created, do not power it on but wait for a while and browse to the directory of the virtual machine itself. There you wil find the virtual machine configuration file and for the people who know, I’m talking about the *.vmx file. Edit this file with an extra line that states: firmware = “efi” and save the vmx file. When we now power on the virtual machine the machine thinks it is a EFI driven machine, and we can begin to create our new reference image. The sad thing of this is, that we now have to maintain two images, one with the traditional BIOS instructions, the other with the new EFI instructions and given the period BIOS is still present, this is going to be a long ride.
Just to be sure, here are some images to illustrate:
Select VMX file
Edit VMX file by adding the line firmware = “efi”
For more information, please see the following reference links:
- Install vSphere in VMware Workstation using EFI instead of a BIOS
- Installing Windows to an EFI-Based Computer
- Microsoft Deployment Toolkit (MDT) 2012 > Optional – MDT 2012 Print-Ready Documentation.zip > Using the Microsoft Deployment Toolkit.docx
- Create UEFI-based Hard-Disk Partitions by Using Windows SIM
- Recommended UEFI-Based Disk-Partition Configurations
- What is Windows System Image Manager?
The last thing I want to add, is that the problem can also be resolved by capturing your reference build made on a UEFI Virtual Machine and capture the entire disk > VHD to file and deploying this afterwards to your targetted machines.