Hyper-V Server R2

I'm currently attending a conference with a lot of people who own the same kind of companies that I do. It's a fun experience to get to talk to other people who do what I do and face the same things as I do every day.

While the conference is marketing centric, you can't stop IT guys from talking about technology. One conversation that has come up a lot is in regards to virtualization. I'm currently working on two separate virtualization projects for clients. We had to choose a horse, so to speak, between Microsoft and VMWare when it came to the different platforms.

Needless to say, I chose to hitch my cart to the Hyper-V horse in this race. We've seen Microsoft enter markets as the underdog in the past and become the dominant player within a few years. I feel that the virtualization market is going to play out the same way.

You can really tell that they're out to win by the features that they are offering for free. In the past, any kind of clustering required Windows Server Enterprise. If you're using the Hyper-V role on top of Windows Server 2008, you still need Enterprise or better in order to take advantage of the clustering capabilities.

However Microsoft also has a free product called Hyper-V Server 2008 R2. Included for free are some features that are not available with Windows Server Standard running the Hyper-V role, including Cluster Shared Volumes.

Using this free technology, we are able to create highly-available clusters for our clients. With so much running on any one physical machine now, the hardware becomes much more valuable. Using Cluster Shared Volumes (CSV) along with shared storage like iSCSI or Fibre Channel, you can protect your critical systems making sure that even with the total failure of a complete server, you can keep on running.

Our "bread and butter" is small businesses, many of whom are too small to really need this level of virtualization. But I really enjoy working with my larger clients and getting to play with this kind of technology. That's not to say that we don't get to use Hyper-V with our smaller clients. We have many SBS 2008 servers running Hyper-V child machines, and even a few SBS 2008 systems running AS the child machine.

Whether you're using VMWare, Hyper-V or any other technology, virtualization is an amazing technology and I can foresee a day where everything we work on is a virtual machine in some form.

Wake on WLAN

We recently deployed 31 brand spakin' new Dell Latitude E5500 laptops to a school here in town. One of the things I noticed in the BIOS settings was the option to Wake on WLAN instead of the usual Wake on LAN. Intel refers to this WoWLAN. But I can't for the life of me get it to work. If anybody searching the web for it and stumbles upon this article (sorry that I'm not offering a solution this time), please come back and post a solution in the comments if you find one.

We would like to be able to do some offline management of these laptops, and wake them up to do so in the cart on the weekend.

We have it set in the BIOS, and under the power management options in Device Manager. What I guess I can't get my head around is how a magic packet reaches a wireless card, especially one with a secured profile, while the system is off. The wireless card is a BCM4310 based Dell Wireless 1395 WLAN Mini-Card.

Any ideas? Is this Intel only?