unless you are a MSDN subscriber.. then you have much more freedom
http://www.globalknowledge.com/train...=United+States
Vista and MSDN
If all of the above sounds a bit bleak, there is one perfectly legitimate
way you can get around many of these restrictions. You'll notice that this
whole time I've been emphasizing that these restrictions are for retail and
OEM copies of Vista. But what about copies of Vista that you've obtained
through an MSDN subscription?
This is where things get interesting, because MSDN subscribers have a great
deal more freedom with Vista in VMs-more freedom than just about anyone
else. Here's what you can do with Vista if you have an MSDN subscription:
1. All editions of Vista that you can obtain through MSDN-from Home up
through Ultimate-can be installed in a virtual machine.
2. You can move or copy VMs created with the MSDN editions of Vista to
other machines. However, you're only allowed to use the VMs in question for
internal testing and development, as per the MSDN licensing agreement
itself.
3. The last provison falls in line with how MSDN editions of an operating
system can't be used to build a system for retail sale or public use. You
can't host a publicly-accessible Web server with an MSDN copy of Windows
Server 2003, so you should only be able to use VMs made from MSDN licenses
for internal use as well.
"Steve Thackery" <> wrote in message
news:...
>> I was under the impression I could install the 32-bit version on the same
>> computer as the 64-bit as a Microsoft Virtual PC guest OS
>
> Unfortunately, your impression was wrong :-(
>
> You must have a license for each installation of Vista (or XP, for that
> matter), whether that is on a real machine or a VM.
>
> Your license only permits one installation (either 32-bit, or 64-bit), so
> that's why the second installation cannot be activated.
>
> You will have to buy another license (with activation key) for each
> installation.
>
> SteveT