A Few Vail Questions Answered

I spoke briefly with Dave Berowitz and Jonas Svensson of the Windows Home Server team today about a couple of questions I had about the recently released Vail public beta (see my overview). This information should be of interest if you're using or considering Windows Home Server.

Upgrading from v1 to Vail

The big one was about upgrading from Windows Home Server v1 to Vail. As you may know, WHS v1 is a 32-bit system and Vail is 64-bit, and Microsoft does not support upgrading from 32-bit Windows versions to 64-bit versions. This is the case with Vail, and Microsoft is not explicitly supporting any sort of data upgrade path between the two systems. So you're welcome to stick with your v1 server--the software will be fully supported through 2012--or move to the new platform and take advantage of those additional features. Customers are migrating data currently with network file copy/Robocopy-type operations, and it looks like that's pretty much you're only option.

File system changes

In WHS v1, the system used standard NTFS-formatted disks, so if the server crashed, you could take the disks out individually, pop them in any Windows PC, and copy the data off. With Vail, Microsoft has changed Drive Extender to use block-based duplication instead of file-based duplication, so this is no longer possible. However--and this is a very important point--you can pop those disks into any Vail-based PC server and access the data that way. I was pointed to a Windows Home Server Forums post that details this and other changes to the Drive Extender technology in Vail.

New/Improved features:

For duplicated folders, data is duplicated in real time to two separate drives - there is no hourly migration pass.

File system level encryption (EFS) and compression are now supported for Drive Extender folders.

File conflicts are gone, duplication works as intended for files in use as it is performed at the block level now.

Deprecated features:

A data drive from a storage pool cannot be read on machine not running the “Vail” server software.

Data isn't rebalanced across drives to ensure even distribution. The data allocation attempts to keep drives evenly used. A periodic rebalance operation is considered for the next version.

There's a lot more, so check out the post.

Media Center integration

I noted in my overview of Vail that Microsoft had told me in September 2008 that it was planning some form of Media Center integration with WHS Vail. Today, I was told the following: "Microsoft has never publicly announced anything regarding Media Center in Windows Home Server, though we've always looked at different scenarios for the product and did consider that. But we have lots of complementary capabilities in Vail, including streaming inside and outside of the home, organizing all of your media in one place, and accessing that content through a variety of clients, including Windows 7 PCs and Xbox 360."

SKU differences/different markets

As I noted previously, the Vail public preview is marked as "Premium Edition," suggesting that there will be multiple versions (or "SKUs") of the product. Microsoft had no comment about that, beyond noting that it was too early to discuss product branding or pricing. That said, the Vail core market is the same as that for v1, home users, and Microsoft knows there is a dedicated and avid tech enthusiast audience as well.

Changes to come

The Vail public preview is representative of the final release but is not quite feature complete. Microsoft told me to expect some post-beta changes coming down the road.

Hope this helps. --Paul

Discuss this Article 4

DarkSages
on Apr 28, 2010

Paul when you installed Vail did all of your devices like sound video network installed correctly? I did this on a number of dell computers and it was not liking some devices. Whats  weird is that those same devices work on server 2008 64x. I don't really care about the video card or sound but I do care about my network card it is a 1Gps card and the one in my board is only 100mbs. Thanks for the info it will help on making future decisions.

Waethorn
on Apr 28, 2010

Could it be that we'll see WHS become the next Media Center PC concept?

Waethorn
on Apr 28, 2010

@DarkSages:

WHS Vail is based on Server 2008 R2, not R1, so driver availability might not be the same.  If you can't get drivers for your PC components on Server 2008 R2, the Windows 7 x64 drivers will work fine.  You can also try Vista x64 drivers if Win7 ones aren't available, but they won't be digitally signed for Win7/Srv2008R2 so you might get a warning about that.  They should still work though.

Also, video drivers aren't necessary.  Standard VGA is all you need since you'll only be remoting in with RDP or using the management console.  It's standard for servers not to use specialized video drivers because remote management won't use any of the servers graphics acceleration anyway (and in most cases, servers usually only have very basic video support).  Ditto for sound.  I'd suggest just disabling sound in your servers BIOS to save you from having to install a driver.  It won't have any affect on media streaming to your PC's either.

The only drivers you should concentrate on with a server are network, storage subsystem, and additional chipset features that don't have Windows drivers included out of the box.  Unless you have a specific reason to, I've found that getting into the constant driver update cycle on a server OS is just going to lead to trouble.  Utilize WHQL drivers on Windows Update, if there are any available instead.

On a real business server, you should use RAID with a decent controller card.  On the other hand, with WHS, since it shouldn't be configured with RAID, if you use a SATA controller, set the mode to AHCI so that you get the use of SATA Gen 2 features like Native Command Queing.  Legacy IDE mode doesn't support that.

Waethorn
on Apr 28, 2010

@DS:

What kind of network card is it?

If you don't know, go into the property sheet of the device in Device Manager, to the Details tab.  Pull down the drop-down menu and choose "Compatible ID's", and post the second one (it should only have the bus, Vendor ID, and Device ID and nothing else - the Revision code isn't important).

eg.:  PCI\VEN_10EC&DEV_8168

That's a Realtek Gbe NIC on a PCIe bus (PnP firmwares don't differentiate between PCI and PCIe).

The 10EC is Realtek's Vendor ID.  Each vendor has their own.  Intel's is 8086, and you should know why.  Some companies use the Device ID as their model number for the part.  In this case, this happens to be a Realtek RTL8168-compatible LAN device (it could be one of the variants of the 8168, but the driver is the same).

Oh, and just FYI:  In Vista and 7-based OS's (like Vail, or Server 2008 [R2]), you can right-click and copy any of the lines out of the PnP info from Device Manager.  You can also copy it from XP/Srv2003, but there is no right-click menu, so you have to use Ctrl-C, or Ctrl-Ins if you're one of us old-time hardcore users.  ;)

Please or Register to post comments.

IT/Dev Connections

Las Vegas
September 30th - October 4th

Paul ThurottYou'll have the opportunity to experience:
• 120 Technical
Sessions
• Networking with Peers
• Expert Speakers


Come See Paul Thurrott & Mary Jo Foley in Person!

Register Now

Office 365 InfoCenter

Get the latest insight and info from Paul

Read Now!

What I Use