Microsoft has a new Knowledge Base article that documents the supported command line options for the Microsoft App-V 4.5 Management Server. 

KB2384955 - Supported command line options for the Microsoft App-V 4.5 Management Server installer.

Microsoft has published a new Microsoft Application Virtualization (App-V) Knowledge Base article.  If you're having trouble running virtualized apps on your clients and getting something along the lines of Error Code: xxxxxxx-xxxxxx2A-00002AF9 then you'll want to check this one out:

Symptoms

An application on an App-V client fails to launch with the following error:

The Application Virtualization Client could not launch application name.
No such host is known.
Error Code: xxxxxxx-xxxxxx2A-00002AF9

Cause

This issue can occur if the server name specified in the HREF attribute in the application .osd file is incorrect.

Resolution

To resolve this issue, perform the following steps:

1. On the App-V Management Server, open the application .osd file and scroll down to the following line:

<CODEBASE HREF="rtsp://servername:554/ApplicationDirectory/Application.sft"

2. Verify that the server name specified in the HREF attribute is correct.

Example: If the App-V Management Server name is Appv-Svr, the HREF attribute should look like the example below:

<CODEBASE HREF="rtsp://Appv-Svr:554/ApplicationDirectory/Application.sft"

3. Once the sever name is corrected in the application .osd file, open the Application Virtualization Client MMC snap-in on the App-V client and refresh the Publishing Server.

4. Launch the application on the App-V client.

For the latest version of this information please see the following new Knowledge Base article:

KB2271253 - A virtualized application on a Microsoft App-V client fails to launch with Error Code: 2A-00002AF9

The Hyper-V team released several Hyper-V updates as a single update package via Windows Update. These updates have been publicly available for some time now, but now they are available packaged together as a single roll-up for the convenience of customers.

There are three issues resolved with this update:

• Compatibility with Intel Nehalem Processors
• Compatibility with Intel Westmere Processors
• A network issue when, under extreme network load, the VM network connection is lost.

For specifics on the issues resolved with this update, please see this KB article http://support.microsoft.com/kb/2264080

It’s only one win. But for Microsoft’s Hyper-V virtualization push, it could be a key victory in the global virtualization war vs. VMware. Specifically, CH2M HILL expects to save a projected $3.2 million over the next several years by switching from VMware virtualization solutions to Microsoft’s Hyper-V hypervisor. Here’s the story.