How to check the status of BIOS – UEFI – Secure Boot with PowerShell

During the past weeks I spend a bit of time deploying Windows 8 to UEFI enabled clients. With PowerShell 3.0 on Windows 8 you will find some new cmdlets that provide information about the status of your system’s BIOS/UEFI/Secure boot configuration. The below table shows the return values depending on whether the system’s firmware is using BIOS, UEFI and if Secure boot is enabled or not.   BIOS / UEFI Setup BIOS UEFI with CSM Read More …

Windows 8 – How to check if your system can run Hyper-V

Many articles refer to the Sysinternals Coreinfo utility to check whether your system can run Hyper-V on Windows 8 or not. But just this morning I found out that the systeminfo command that is included in Windows provides some additional Hyper-V related information. More Information about Hyper-V on Windows 8 Bringing Hyper-V to “Windows 8” How to Check if Your CPU Supports Second Level Address Translation (SLAT)

ToolTip: CrystalDMI

The CrystalDMI utility allows you to read DMI (Desktop Management Interface) data. CrystalDMI is FREE and does not require installation. Download is available here More information about DMI can be found here

ToolTip: HWiNFO32

Today’s ToolTip is about HWiNFO32 which is a hardware information and diagnostic tool. I have seen many tools that can collect hardware information but this one gives me an impression of being a well organized utility and most important it’s FREE. I recommend that you download the portable ZIP file as that doesn’t require an install. Beside collecting detailed hardware information, HWiNFO32 also includes a Benchmark feature that compares the current system components against other Read More …

ToolTip: Microsoft® Hardware-Assisted Virtualization Detection Tool

Windows Virtual PC requires that your hardware supports hardware-assisted virtualization. There are a number of third party utilities around already, but now Microsoft released one as well. It’s called the Hardware-Assisted Virtualization Detection Tool and can be downloaded from here If you launch the tool manually it will tell you if your system meets the requirements for running Windows Virtual PC or not, quite similar as the Securable utility I wrote about in the Detect Read More …

Accessing the BIOS in Windows Virtual PC

When setting up a Virtual Machine in Windows Virtual PC, You will see the following progress window when the VM is started. This indicates that the VM is running in Enhanced Mode which is the default. To better understand the different modes of Windows Virtual PC I recommend reading the “Three Modes of Windows XP Mode” article. The progress windows is being displayed until the OS running in the VM has started up, so you Read More …

Intel AMT in action

For those of you who do have vPro capable machines in their environment, but never had the chance to take a closer look at the AMT features, this blog post might be of interest. For most people I assume the biggest hurdle to start using the AMT technology is that you need a System Management Infrastructure setup that provides AMT support like Microsoft SCCM, Altiris Client Management Suite, Intel Landesk or the HP System Configuration Read More …

What happens before the OS loads

Ever wondered what actually happens when you turn on your PC before it loads the operating system ? Watch this video with Jamie Schwartz, Development Lead, Windows Kernel Dev team, and Andrew Ritz, Development Manager, Windows Kernel Dev team. Windows Vista PreOS Environment: What happens before the OS loads

vPro colors in BIOS

When remotely accessing the system BIOS of a HP Compaq dc7800 desktop machine using vPro, the BIOS appears in black and white as shown in the picture below: to get the native BIOS colors you must configure the terminal emulator mode to ANSI then, the BIOS will appear with colors as if you were sitting in front of the physical machine. Thanks to Claude Henchoz for the hint.

BIOS Boot delay on VMWARE

Ever had that issue that you wanted to enter the VMWARE BIOS, but you simply don’t made it because the VMWARE session boots too fast ? Add the following line to your *.vmx file. bios.bootDelay = “3000”¨