Just a quick heads up that we recently published our prescriptive guidance (aka recipe) for sequencing the Microsoft Office 2010 beta using Microsoft Application Virtualization 4.6.   Please note that:

This article describes one method that you can use to successfully sequence the Beta version of the 2010 Microsoft Office system for use with Microsoft Application Virtualization (App-V) 4.6. The method that is described in this article is not the only method that is available. You may have to change the information in the article as appropriate for your particular environment. 

This process should work on the final version of Office 2010 but of course until it's released we can't make any guarantees.  We'll update the article with any changes (if needed) once it ships.

KB980861 - Prescriptive guidance for sequencing the Beta version of the 2010 Office system in Microsoft App-V

Enjoy!

J.C. Hornbeck | System Center Knowledge Engineer

Read more at: http://blogs.technet.com/b/appv/archive/2010/03/03/new-kb-prescriptive-guidance-for-sequencing-the-beta-version-of-the-2010-office-system-in-microsoft-app-v.aspx

Read more at: http://communities.vmware.com/message/1486339

Read more at: http://communities.vmware.com/message/1486026

Here's an issue we see every once in a while and since I didn't see the details published anywhere I thought I'd go ahead and do that here.

Consider the following scenario:

1.  You install the App-v 4.x server and set the packageroot (content directory) to an alternate location (not the default).
2.  You delete the included Default Application, package and content from the disk.
3.  You upgrade the server to a newer version of App-V.

After completing the steps above, when clients attempt to stream a virtualized application they receive one of the following errors:

A network error occurred error :  XXXXXXXX-XXXXXXXX-20000194

or

A network error occurred error :  XXXXXXXX-XXXXXXXX-10000003

Cause:

This is caused by an invalid value for SOFTGRID_CONTENT_DIR in the registry.

Resolution:

To resolve this issue, complete the following steps:

1.  Start RegEdit

2.  Navigate to the following key:

HKLM\Software\Microsoft\Softgrid\4.5\Server

3. Set the SOFTGRID_CONTENT_DIR value to the proper content directory location.

4.  Restart the server.

More Information:

During the server upgrade, the installer first searches for the defaultapp.sft file location. After getting the defaultapp.sft file path, the installer then gets the content directory path from the SOFTGRID_CONTENT_DIR registry key. If the defaultapp.sft file path is not the same as SOFTGRID_CONTENT_DIR registry entry, the installer overrides the value of SOFTGRID_CONTENT_DIR. If there is no defaultapp.sft file (i.e. it has been deleted), the installer overrides the value of SOFTGRID_CONTENT_DIR anyway with the default installation content directory (PROGRAM_FILES\Microsoft System Center App Virt Management Server\App Virt Management Server\Content).

This is an issue we're aware of and it should be fixed in the next version of the server, but if you run into this in the mean time this is how you can fix it.

J.C. Hornbeck | System Center Knowledge Engineer

Read more at: http://blogs.technet.com/appv/archive/2010/03/02/after-upgrading-a-microsoft-app-v-server-client-machines-may-receive-00000194-errors-when-trying-to-launch-applications.aspx

Here's an issue we see every once in a while and since I didn't see the details published anywhere I thought I'd go ahead and do that here.

Consider the following scenario:

1.  You install the App-v 4.x server and set the packageroot (content directory) to an alternate location (not the default).
2.  You delete the included Default Application, package and content from the disk.
3.  You upgrade the server to a newer version of App-V.

After completing the steps above, when clients attempt to stream a virtualized application they receive one of the following errors:

A network error occurred error :  XXXXXXXX-XXXXXXXX-20000194

or

A network error occurred error :  XXXXXXXX-XXXXXXXX-10000003

Cause:

This is caused by an invalid value for SOFTGRID_CONTENT_DIR in the registry.

Resolution:

To resolve this issue, complete the following steps:

1.  Start RegEdit

2.  Navigate to the following key:

HKLM\Software\Microsoft\Softgrid\4.5\Server

3. Set the SOFTGRID_CONTENT_DIR value to the proper content directory location.

4.  Restart the server.

More Information:

During the server upgrade, the installer first searches for the defaultapp.sft file location. After getting the defaultapp.sft file path, the installer then gets the content directory path from the SOFTGRID_CONTENT_DIR registry key. If the defaultapp.sft file path is not the same as SOFTGRID_CONTENT_DIR registry entry, the installer overrides the value of SOFTGRID_CONTENT_DIR. If there is no defaultapp.sft file (i.e. it has been deleted), the installer overrides the value of SOFTGRID_CONTENT_DIR anyway with the default installation content directory (PROGRAM_FILES\Microsoft System Center App Virt Management Server\App Virt Management Server\Content).

This is an issue we're aware of and it should be fixed in the next version of the server, but if you run into this in the mean time this is how you can fix it.

J.C. Hornbeck | System Center Knowledge Engineer

Read more at: http://blogs.technet.com/b/appv/archive/2010/03/02/after-upgrading-a-microsoft-app-v-server-client-machines-may-receive-00000194-errors-when-trying-to-launch-applications.aspx

Thanks for the help.

Read more at: http://communities.vmware.com/message/1485519

Read more at: http://communities.vmware.com/message/1485236

Read more at: http://www.computerweekly.com/Articles/2010/03/02/240465/ibm-eco-supercomputer-crunches-9tb-of-data-in-20-minutes.htm

Read more at: http://www.bitpipe.com/detail/RES/1267462550_166.html?asrc=RSS_BP_TERM

Read more at: http://communities.vmware.com/message/1484493