When your computer is having a UEFI , it will prefer a GPT (GUID Partition Table) on the harddisk to function. GPT has advantages over MBR (Master Boot Record) such as support for larger disks.
Start the diskpart.exe and run the command:
When there is a star in the Gpt column the disk is Gpt, else it is an MBR disk.
(Example of a disk without GPT)
More information about the difference between GPT and MBR can be found on the Wiki pages:
GPT = GUID Partition Table (http://en.wikipedia.org/wiki/GUID_Partition_Table)
MBR = Master Boot Record (https://en.wikipedia.org/wiki/Master_boot_record)
Virtual UEFI firmware can be enabled on VMware Workstation 8.x or 9.x, but it is not officially supported.
To do so add the following line to your .vmx file of the virtual machine.
firmware = "efi"
Next time you start the Virtual Machine you will see this screen:
Instead of the BIOS screen of VMware. Starting installing Windows 8 in UEFI mode is now possible. Unfortunately it is not possible to enable Secure Boot in VMware yet.
Changing from BIOS to UEFI also changes the hardware of the Virtual Machine. Normally a VM identifies it as VMware Virtual Platform, with UEFI this is changed to ‘VMware 7.1’ (in my case). So be care full with this.
I found an article on the Technet Blog about creating documents for task sequences. I used it to make an overview of what is done within the task sequence and copied it to Excel.
Often times, after creating an MDT or SCCM task sequence, you need to document it for yourself or your customers. Usually, this involves creating a table with the groups and steps, extracting their descriptions, identifying conditions and denoting the step actions and variables and then having format it all nicely and with indents denoting hierarchy. All of this information is usually already in the XML of the task sequence and all you're really doing is formatting. You can automatically format XML documents by using an XSL transform with the right logic.