You are on page 1of 33

BizTalk 2010 VHD Virtual Machine

Download this fully configured virtual machine of the latest release of BizTalk
Server. Evaluate the new capabilities of BizTalk Server 2010 by completing the
BizTalk Server 2010 Training Kit which is preinstalled on this VHD. The BizTalk
Server 2010 training kit includes labs and training videos to help you learn about
the new features of BizTalk Server 2010.
http://www.microsoft.com/download/en/details.aspx?id=13624
System requirements
Supported Operating Systems: Windows Server 2008 R2
Windows Server 2008 R2 Hyper-V, Microsoft Hyper-V Server 2008 R2 and
Windows Server 2008 SP2 Hyper-V Windows Server 2008 R2 Hyper-V is
required to use this virtual machine
In addition to the system requirements for Windows Server 2008 as
described in the release notes, a 64-bit system with hardware-assisted
virtualization enabled and data execution prevention (DEP) is required.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~In order to use this evaluation package
you will need to have Microsoft Hyper-V installed on a physical machine. Hyper-
V is available on Windows Server 2008 and Windows Server 2008 R2. This virtual
machine requires Hyper-V on Windows Server 2008 R2. Details on how to install
Hyper-V can be found here. Details of how to setup the VHD are included in the
documentation that accompanies the product. In the Setup folder there is an
application that will add all the VMs into Hyper-V. The app does this while
maintaining only a single copy of the base images. To install, open a command
promt with the "Run as Administrator" option and change directory to the setup
folder. The import will fail if you do not run the command prompt with this option.
Then run the command: importVM.exe full path to base image For example, if the
root of the labs is c:\Microsoft BizTalk Server 2010 Training, then the command
would be: importVM.exe "C:\Microsoft BizTalk Server 2010
Training\VM\common\BizTalk2010Demo.vhd"

Enable Hardware settings in BIOS to run Hyper V
IftekharH

IftekharH
Microsoft
MSFT
7,581 Points 3 3 1
Recent Achievements
Blog Commentator II Blog Conversation Starter Blogger III
View Profile
9 Aug 2010 2:46 PM
Comments 0
Likes

I would be lying if I say that i don't get this question anymore from our customers
and partners.
I just bought a new server and it appears to have a multitude of BI OS options for
virtualization. Which BI OS options should be enabled and/or disabled to use
with Hyper-V?
I recently received a well drafted message by our friends in Virtualization product
group here in Microsoft. Here is what suggested by Microsoft Virtualization Team
with respect to HYPER-V, BIOS & PROCESSOR FEATURES and i cant resist
to share it with you all because it makes things so clear and easy.
Hyper-V RTM/R2 Hardware
Requirements
--
When it comes to hardware requirements for Hyper-V, the hardware requirements
are relatively straightforward and have been mainstream for many years and many
generations of systems.
1. 1. Hyper-V is 64-bit only and thus requires a 64-bit (x64) processor
1. Windows Server 2008 was the final 32-bit (x86) Windows Server
release and Windows Server 2008 32-bit version does not include
Hyper-V
2. 2. Hardware Virtualization Assists* in the form of:
1. Intel VT-x (initially codenamed Vanderpool)
2. AMD AMD-V (also called SVM and initially codename Pacifica)
3. 3. Hyper-V requires Hardware Data Execution Prevention:
1. Intel refers to it as Execute Disable (XD). This feature must be
enabled in the system BIOS.
2. AMD refers to it as No Execute (NX). This feature must be enabled in
the system BIOS.
Again, these are Hyper-V requirements and Hyper-V will not run without these
capabilities.
*Note: When you enable hardware assisted virtualization (Intel VT or AMD AMD-
V) in the BIOS, you must TURN THE SYSTEM OFF. NOT REBOOT. OFF. If
you dont power cycle the system completely, you will not enable hardware
assisted virtualization on the majority of systems in the market.
Hyper-V R2* & SLAT Hardware
For traditional server virtualization or virtualization desktops without
RemoteFX, SLAT hardware is not required, but HI GHLY RECOMMENDED.
The use of SLAT capable hardware offers significant performance improvements
across the board.
Intel refers to this a Extended Page Tables (EPT)
AMD refers to this as Nested Page Tables (NPT) or Rapid Virtualization
Indexing (RVI)
If there are BIOS option to enable these features (theyre usually on by default),
these options should be enabled.
For virtualizing desktops using RemoteFX, SLAT hardware is REQUI RED. The
use of SLAT capable hardware offers significant performance improvements
across the board and is especially important when using RemoteFX. These
technologies are an extension to the traditional TLB that allow Hyper-V to use the
hardware to handle multiple TLBs one for each virtual machine. This is
fundamental requirement for RemoteFX.
Intel refers to this a Extended Page Tables (EPT).
AMD refers to this as Nested Page Tables (NPT) or Rapid Virtualization
Indexing (RVI).
If there are BIOS option to enable these features (theyre usually on by default),
these options should be enabled.
Personally, I wouldnt purchase any system for virtualization that is not SLAT
capable.
*Note: To take advantage of SLAT hardware, you must be running Windows
Server 2008 R2 or later or Microsoft Hyper-V Server 2008 R2 or later. Previous
versions (Windows Server 2008/2008 SP2 & Microsoft Hyper-V Server 2008/2008
SP2) do not support SLAT hardware and will simply ignore these hardware
capabilities.
Hyper-V : What to Disable in the BIOS
There are some hardware features that Hyper-V does not utilize and enabling them
will prevent Hyper-V from loading. Specifically, please be sure
that:
Intel VT-d is disabled
Trusted Execution is disabled
If either of these options is enabled, Hyper-V wont launch and errors will be
posted to the Event Log.
===========================================================
================
Q: Im trying to run Hyper-V on my system and Hyper-V wont launch. When I
look in the event log I see events such as:
Event ID 41: Hyper-V Launch failed; Either VMX not present or not enabled
in the BIOS
Event ID 32: Hyper-V Launch failed; At least one of the processors in this
system does not appear to provide a virtualization platform supported by
Hyper-V
Ive ensured that both:
Hardware Assists are enabled (Intel VT or AMD-V)
Data Execution Prevention is enabled (Intel XD or AMD NX)
What am I doing wrong?
A: It sounds like youre doing a lot right, but there are a few additional BIOS
settings you should check. Please be sure that:
1. Intel VT-d is disabled
2. Trusted Execution is disabled
Hyper-V does not utilize these hardware features and enabling them will prevent
Hyper-V from loading.
===========================================================
================
Q: I see that Hyper-V requires hardware Data Execution Prevention. What does
that mean? What does DEP do?
A: For more information on DEP, check out this article Data Execution Prevention
on MSDN and a useful KB here.

Thanks Virtualization Team for such a great written article, I am sure our
customers and partners will find them really useful.
Do send your feedbacks, comments and suggestions, they are always appreciated.
Cheers!
Hyper-V launch failed; No-execute (NX) or DEP not enabled on processor 00
(check BIOS settings)
December 14, 2010 Leave a comment







Rate This


Most of the machines have "Virtualization" Disabled by default in their BIOS. So
the first thing you have to do is to make sure Virtualization is Enabled or turned on
in BIOS setting.
System BIOS
The system BIOS must support the following:
The virtualization technology included in the main processor, and it must be
enabled.
Hardware-enforced Data Execution Prevention (DEP), and it must be
enabled.
You must enter the BIOS setup of the server and make sure that Virtualization
Technology and Execute Disable are both set to Enabled. In most cases, the
required BIOS settings can be found in these BIOS sections (actual names may
differ, based upon your servers BIOS settings):
Security > Execute Disable (set to On)
Performance > Virtualization (set to On)
Performance > VT for Direct I/O Access (set to On)
Performance > Trusted Execution (set to Off)
Please see the video: http://go.microsoft.com/fwlink/?LinkId=163578
If your still having problem, check the following
1. Start | Computer | Properties

2. Click on Advanced System Settings

3. Click on Settings under Performance


4. On Data execution Prevention , if your a seeing the message Your computers
processor does not support hardware-based DEP you may not able to run virtual
machine. Go back to your BIOS and check it again.

Share this:


How to turn on Hardware Assisted Virtualization
John Howard -MSFT

John Howard -MSFT
Microsoft Corporation
75,857 Points 11 3 4
Recent Achievements
Proposed Answerer I Forums Answerer II First Marked Answer
View Profile
9 Jan 2008 12:14 AM
Comments 20
Likes
Happy New Year!
I've had quite a few direct emails about this in the last few weeks, so it's probably
worth posting as an FAQ. As you probably know, and as I have stated before,
Hyper-V (codename "Viridian", and formerly known as Windows Server
virtualization) requires assistance from hardware to operate correctly. Specifically,
it requires four capabilities: An x64 CPU; VT (Intel) or AMD-V (AMD) hardware
extensions; No eXecute (NX)/eXecute Disable (XD) and full BIOS support for
hardware virtualization. It's 4 out of 4 required, nothing less. On Intel platforms,
you can normally turn VT on and off in the BIOS, whereas on AMD platforms,
AMD-V is on all the time (at least I have not come across a BIOS which contains
an option to enable/disable AMD-V). NX & XD are usually always configurable,
regardless of platform.
The difficult part is knowing where to turn these settings on and off. While I wish I
could give an unified simple answer, there unfortunately isn't one as the BIOS
configuration layout is down to the motherboard manufacturer. NX/XD will
commonly be located under security settings, and VT will commonly be a
processor option. One thing you should note is that if you do change VT to
enabled, you should hard power cycle the machine - generally a Ctrl/Alt/Del or
"Exit & Save" option is insufficient for the change to take effect.
As for full BIOS support - if you install the Hyper-V role and discover that the
Hypervisor has not launched (you'll get an error message when starting a Virtual
Machine) after enabling the hardware features, it is pretty much up to the
motherboard manufacturer. My advise would always be to ensure you have the
latest BIOS from the manufacturer before installing the role. While many, if not
most, recent motherboards do have support, there really is no easy way short of
directly contacting the manufacturer of determining if their motherboard has full
support.
Cheers,


Re: does the hp p7-1267c support intel vt-x?
[ Edited ]
Options
Mark as New
Bookmark
Subscribe

Subscribe to RSS Feed

Highlight
Print

Report Inappropriate Content
03-30-2012 04:52 PM - 03-30-2012 04:53 PM
Hi,

Did you check under Security in the bios? See the below image. The
default setting is disable.




---------------------------------------------------------------------------------------
HP e9280t, i7-960, 12GB, Vertex 3 120, ATI 4850

enable "Hardware-assisted Virtualization" i n BIOS
Options
Mark as New
Bookmark
Subscribe

Subscribe to RSS Feed

Highlight
Print

Report Inappropriate Content
11-16-2012 09:27 AM
I am running Windows 7 Professional on my HP p7-1225 desktop. I
wish to install Windows XP Mode. But before I do this I would like to
go into the BIOS and enable "Hardware-assisted Virtualization". On
the Microsoft website I ran a test which suggests that this might be
possible on my machine and suggests the following procedure to do
this on an HP system:

Depress Esc key when prompted at startup
Depress the F10 key to Configure BIOS
Scroll to System Configuration using the arrow keys
Select Virtualization Technology and depress the Enter key
Select Enabled and depress the Enter key
Depress the F10 key to save and exit
Select Yes and depress the Enter key
Fully shut down (power off), wait a few seconds, and restart your
computer

I managed to press the Esc key in the tenth of a second when it was
possible to do it at startup and then pressed the F10 key. But there
didn't seem to be anything called "System Configuration" that I could
scroll to. I managed to escape and start the system up. But I need to
find out what the correct procedure is for my machine. Thanks.

Microsoft Hardware-Assisted Virtualization Detection Tool User Guide
Introduction
Windows Virtual PC requires processors with the Intel VT, AMD-V or VIA VT
feature. Furthermore, the processor should have the virtualization setting
enabled.
The Hardware-assisted virtualization detection tool (HAV detection tool) helps
you check if your computer processor supports HAV. The tool also checks if this
setting is enabled for the processor.
This document serves as a user guide for this tool.
Installation
You can download the HAV detection tool from
http://go.microsoft.com/fwlink/?LinkId=163321
Download this tool (havdetectiontool.exe) to your local machine and save it
to say c:\havtool
Double click on the executable and follow the prompts to display the result.
Note: You need administrator privileges to run this tool.
Note: The tool is a self-extracting executable and does not install any folders
or files. Rerun the executable if required. The tool deletes all the installed
files on exit.
Supported Operating Systems
The HAV detection tool ONLY supports the following operating systems and
editions/versions:
Windows Vista Service Pack 1, 2 (Home Basic, Home Premium, Business,
Enterprise, Ultimate)
Windows XP Service Pack 3 (Professional), Windows XP Service Pack 2
(Professional)
Windows 7 (Home Basic, Home Premium, Professional, Enterprise,
Ultimate).
On any operating system/edition/version outside of this list, the tool exits with
the following error message:

Interpreting results of the HAV Detection Tool:
This section describes the results, which the HAV detection tool displays.
a) If you have a computer that does not have a HAV capable processor, the
tool displays the following result:


You cannot use Windows Virtual PC or Windows XP Mode on this
computer.
b) If you have a computer that has a HAV capable processor but if this feature
(HAV setting) is not enabled on the processor (in the BIOS), the following
screen is shown:


You would need to enable the virtualization setting in the BIOS (click here
to learn more) for this computer before using Windows Virtual PC or
Windows XP Mode on a supported Windows7 edition.
c) If you have a computer that has a HAV capable processor and if this feature
(HAV setting) is enabled on the processor (from the BIOS), the following
screen is shown:


You can use Windows Virtual PC or Windows XP Mode on a supported
Windows 7 edition on this computer.
d) If you have a machine which has Intel Trusted Execution Technology
(Intel TXT) enabled and *if* that setting interfers with the virtualization
setting of your processor, then the following screen is shown:

You would need to disable Intel TXT before using Windows Virtual PC or
Windows XP Mode on a supported Windows 7 edition on this computer.
Collecting Data
With your *explicit approval*, system configuration data collected by the HAV
detection tool will be sent to Microsoft.
If you choose Yes, I would like to send data to Microsoft in any of the screens
above, data will be sent to Microsoft. You can find the Privacy Statement for the
HAV detection tool here: http://go.microsoft.com/fwlink/?LinkId=164031
Command line options
Copy havdetectiontool.exe to a local folder (say c:\HAVTool)
From an elevated command prompt, run the following command to extract
the files:

c:\havtool\havdetectiontool.exe /x

This displays a prompt to choose the directory for the extracting the files.

Choose to extract the files to c:\HAVTool

Help Options:
To display the errorlevels returned by this tool, run one of the following
commands from an elevated command prompt based on your OS architecture
(from the extracted folder as described above):
c:\HAVTool\sources\i386\havtool.exe /?
or
c:\HAVTool\sources\amd64\havtool.exe /?


Quite Mode:
Create a script which executes the tool in quite mode - a snippet is shown
below:

64 bit:
....
set errorlevel=
C:\HAVTool\sources\amd64\havtool.exe /q
echo %ERRORLEVEL%
....



32 bit:
....
set errorlevel=
C:\HAVTool\sources\i386\havtool.exe /q
echo %ERRORLEVEL%
....


Note: Launch the script from an elevated prompt.

Log Option:
To generate richer logs, based on your OS architecture, run one of the following
commands from an elevated command prompt:
c:\HAVTool\sources\i386\havtool.exe /log %temp%\HAV.txt
or
c:\HAVTool\sources\amd64\havtool.exe /log %temp%\HAV.txt

The HAV setting of your processor is displayed and a detailed file containing richer
information is generated (in the above case, in %temp%\HAV.txt)


Enabling Intel VT-x and AMD-V virtualization hardware extensions in BIOS

This section describes how to identify hardware virtualization extensions and
enable them in your BIOS if they are disabled.

The Intel VT-x extensions can be disabled in the BIOS. Certain laptop vendors have
disabled the Intel VT-x extensions by default in their CPUs.

The virtualization extensions cannot be disabled in the BIOS for AMD-V.

Refer to the following section for instructions on enabling disabled virtualization
extensions.

Verify the virtualization extensions are enabled in BIOS. The BIOS settings for Intel
VT or AMD-V are usually in the Chipset or Processor menus. The menu names
may vary from this guide, the virtualization extension settings may be found in
Security Settings or other non standard menu names.


Procedure 21.1. Enabling virtualization extensions in BIOS

1. Reboot the computer and open the system's BIOS menu. This can usually be
done by pressing the delete key, the F1 key or Alt and F4 keys depending on the
system.


2.Enabling the virtualization extensions in BIOS


Note



Many of the steps below may vary depending on your motherboard, processor
type, chipset and OEM. Refer to your system's accompanying documentation for
the correct information on configuring your system.

a. Open the Processor submenu The processor settings menu may be hidden in
the Chipset, Advanced CPU Configuration or Northbridge.


b. Enable Intel Virtualization Technology (also known as Intel VT-x). AMD-V
extensions cannot be disabled in the BIOS and should already be enabled. The
virtualization extensions may be labeled Virtualization Extensions, Vanderpool or
various other names depending on the OEM and system BIOS.


c. Enable Intel VT-d or AMD IOMMU, if the options are available. Intel VT-d and
AMD IOMMU are used for PCI device assignment.


d. Select Save & Exit.



3. Reboot the machine.


4. When the machine has booted, run cat /proc/cpuinfo |grep -E "vmx|svm".
Specifying --color is optional, but useful if you want the search term highlighted. If
the command outputs, the virtualization extensions are now enabled. If there is
no output your system may not have the virtualization extensions or the correct
BIOS setting enabled.

How to enable NX or XD flag bit in BIOS to install Windows 8 RP


Posted Date: 31-
May-2012
Last Updated: 31-May-
2012
Category:
Windows 8
Author: Tony John
Member Level:
Diamond
Points: 50


Did you get stuck with the error Your PCs CPU isnt
compatible with Windows 8 and want to enable NX, XD, XN
flag on your BIOS to resolve this error? Find out how to
enable NX on your BIOS







Many people who tried to install Windows 8 Release Preview have
reported that they are stuck with the error "Your PC's CPU isn't
compatible with Windows 8". It has been confirmed that not all
CPUs are compatible with Windows 8 RP. Even if you were running
Windows 8 Consumer Preview, it is possible that you may not be
able to run Windows 8 Release Preview on the same computer
unless you have the NX bit enabled in your BIOS. Most computers
have it enabled by default, but if not, you have to enable it
manually from the BIOS.

The system requirements for Windows 8 RP does not mention that
your CPU should support NX (or, XD or XN), but it looks like you
need a compatible CPU with this flag enabled in the BIOS.
What is NX, XD and XN in the BIOS

This is a BIOS feature that allows you to enable or disable the
Execute Disable feature of your CPU and can be configured only
through the BIOS of your computer.

NX stands for No eXecute and is a technology used in
processors to prevent execution of certain types of code. This was
originally invented by AMD.

XD is the acronym for eXecute Disable, which is an Intel
specific implementation of NX. It refers to the same feature but
Intel chose to call it by a different name.

XN is the ARM equivalent of the same feature and is the
acronym for eXecute Never.

Essentially, both NX, XD and XN are the same and are different
names for the same feature in AMD, Intel and ARM respectively.
How to enable NX or XD in the BIOS

This flag can be enabled or disabled only through the BIOS of the
computer. In order to enable this flag and make your computer
compatible with Windows 8 RP, follow the steps below:

1. Restart your computer

2. While booting, before the Windows starts, press the key to go to
BIOS. The key to open the BIOS is different for different
computers. Most computers use the keys F2, F12 or DELETE. Try
each of these keys and see if you can get to the BIOS. If none of
those keys work, then one of the tricks I do is, press all the
function keys (F1 to F12) repeatedly on the computer while
starting the computer. Hopefully, that will work.

3. In the BIOS, go to Security tab.

4. Look for the NX or XD flag. In case of Intel processors, you will
see the XD flag and in case of AMD processors, you will see the NX
flag. If that is not enabled, toggle the option and enable it.

5. Save the settings and exit the BIOS settings.

6. Restart your computer.

Now try to install Windows 8 Release Preview. Since you have
enabled NX/XD bit, you will not see the error Your PC's CPU isn't
compatible with Windows 8 anymore.

NX and XD flags missing in the BIOS

The NX or XD flag is not available in all the BIOS programs. Many
manufacturers are not showing this option in the BIOS. I tried a
Lenovo Ideapad laptop and a Sony Vaio laptop. Both laptops have
these options missing in the BIOS. I am still searching for a
solution to this and I will post if I find anything. I found one of the
forums that says we need to contact the computer manufacturer
and get an updated version of the BIOS program to see the NX/XD
bit flags in the BIOS. I am not sure how many consumers are
going to take this pain and upgrade the BIOS program to install
Windows 8 on their computer.

If the eXecute Disable feature is missing in the BIOS, there are
few possible reasons:

1. You have an outdated BIOS program

2. Your CPU does not support NX/XD flag. This is modern feature
introduced in newer versions of the CPU and may not be available
in old versions of the CPUs. If you have an old computer, your CPU
may not have this feature.

3. You may have an incompatible operating system. Only new
operating systems like Windows Server 2003, Windows 2008,
Windows XP, Windows 7, Windows 8 and new versions of Linux
support the XN/XD feature.

Windows 8 Release Preview has a dependency on the NX bit of the
CPU and you cannot install the Windows 8 RP unless the NX is
enabled on your CPU.

If you tried the steps mentioned in this article and it resolved your
error Windows 8 installation error, please let us know by posting a
response below. If the above steps did not work but you had to do
something else to enable NX or XD on your computer, share your
experience and help others.

You might also like