The second most exciting feature (to me) is the support for packages sequenced with 4.5 to be played on 4.6 clients (even the x64 client!).  The problem I had this morning, though, was there are a ton of blogs touting this support, but no one bothered to publish how.  For instance, from The App-V Team Blog:

All your pre-4.6 packages are valid and can continue to be used on the 4.6 client – just modify the OSD file to include the OS values for the 32 and/or 64-bit platform as target, as appropriate.

So, it can be done, but how do I include support for Windows 7 x64 clients in the OSD?  Like this:

Your current OSD files have a section that includes something similar to the following:

<OS VALUE=”WinXP”/>
<OS VALUE=”Win7″/>

This indicates that the package is available for all Windows XP and Windows 7 clients (32-bit of course, because version 4.5 does not support 64-bit).  So, add the following to your OSD file under the last “OS VALUE” entry to enable support for Windows 7 x64:

<OS VALUE=”Win764″/>

And here’s a list of all the available target operating systems:

<OS VALUE=”Win2003TS”/>
<OS VALUE=”Win2003TS64″/>
<OS VALUE=”Win2008R2TS64″/>
<OS VALUE=”Win2008TS”/>
<OS VALUE=”Win2008TS64″/>
<OS VALUE=”Win7″/>
<OS VALUE=”Win764″/>
<OS VALUE=”WinVista”/>
<OS VALUE=”WinVista64″/>
<OS VALUE=”WinXP”/>
<OS VALUE=”WinXP64″/>

Now, if you don’t get it at first, read it again.  Anyway, I was forced to reset my region to 1 (from 1), taking up one of the five changes that I’m allowed.  Not that I’m going to be changing my region to anything else, but still, I find this dialog box humorous.

Remote Server Administration Tools for Windows 7 Release Candidate (RC)

Remote Server Administration Tools for Windows® 7 RC enables IT administrators to manage roles and features that are installed on computers that are running Windows Server® 2008 R2, Windows Server® 2008, or Windows Server® 2003, from a remote computer that is running Windows 7 RC.

Today, I added the third node to the Hyper-V R2 cluster we’re currently testing.  When I did, VMM freaked out and all of the guests on the other two nodes went into a warning state.  The error they displayed:

Warning (13921)

Highly available virtual machine <INSERT NAME> is not supported by VMM because one or more of its network adapters is not configured correctly.

Recommended Action

Ensure that all of the virtual network adapters are either disconnected or connected to highly available virtual networks.

So, how do we fix this issue?  You use Google, of course.  A quick Google-ing gave the following information (edited for grammar):

For a VN [Virtual Network] to be marked as HA, the location and tag of the VN in all nodes must be the same.  For each VN in the cluster[, be sure that]:

• The NICs to which the VN is attached in each node have the same location.
• The Tag in the VN in each node is the same.
• The VN Name is the same.
• After you commit changes, refresh the cluster so ensure that the VN is detected as HA.

Our problem, specifically, was related to the network tagging.  To fix the tag, do the following:

1. Open VMM, and navigate to the “Hosts” view.
2. Right click on one of the hosts and select “Properties.”
3. Navigate to the “Networking” tab.
   
4. Once, there, you’ll need to click each network (in this case, we have two) and add text to the “Network tag:” field.  Keep in mind that these tags will need to be the same across all your hosts in order to make them highly available.
   
5. Rinse and repeat for the rest of your hosts.
6. Once you finish tagging, you’ll need to refresh the cluster node in VMM.
   

That fixed our problem.  Maybe it will help you.

More information here in the “Troubleshoot ‘Unsupported Cluster Configuration’ Status for a Highly Available Virtual Machine” section.

The subsystem needed to support the image type is not present.

A quick Googling led me to this Technet post.  The relevate parts of the post:

WOW64 is not present in Microsoft Hyper-V Server 2008 R2.  This change was made because Microsoft Hyper-V Server is supposed to be a single purpose OS, and users have asked for it to be as small as possible.  So, whenever possible, we will not include general Windows components that are not needed by Hyper-V.

And the resolution:

Issue this command to install WOW64 support:

start /w ocsetup ServerCore-WOW64

And of course: reboot.