I've been watching the comments - both internally and externally - about yesterday's launch of the Hyper-V Beta (yes, I know I'm on vacation, but this is exciting to watch), and I thought I'd list the answers to a few commonly asked questions.

1. Q:  How do I install Hyper-V on my 32-bit server?
   A:  You don't.  Hyper-V is 64-bit only, and requires that you have an Intel or AMD processor with Virtualization extensions (Intel calls their's VT, AMD calls their's AMD-V).
   
2. Q:  How do I manage Hyper-V remotely?
   A:  It's not terribly easy to do with the beta.  If you're running Windows Server 2008 with Hyper-V Beta on another machine besides your Hyper-V server, you can use the MMC Management Console to connect to your Hyper-V server remotely (which, in fact, you *must* do if your server is running Server Core). 
   
   If you've only got one server, you can use Terminal Services to connect to your Hyper-V server and run the MMC Management Console - though, you'll run into issues controlling the Virtual Machines with VMConnect if you don't have the Integration Components installed. 
   
   You can also use WMI calls to manage a Hyper-V server remotely.  The documentation for that should be online shortly, if it isn't already.
   
   We're going to make remote management easier to do in subsequent releases, so please stay tuned.