The App-V Blog

A PowerShell script to list all existing App-V package dependencies

As I'm sure you're all aware by now, back in App-V 4.5 we first introduced Dynamic Suite Composition, a technology that allows you to link, or create dependencies between, multiple virtualized applications.  This is a powerful feature that allows multiple virtual applications to share the same virtual environment without having to re-sequence those apps together manually.

While this is a great feature of App-V that makes managing your virtual apps incredibly quick and easy, there's not an automatic way to see all the dependencies you've created in your environment.  With that in mind, I got a tip that one of our friends at Sepago created a cool PowerShell script that does just that.

I don't want to steal all of the authors thunder but I do have an example of sample output from this script here:

PS D:\> .\Get-AppVPackageDependencies.ps1 .\

============================================================
Dependencies found:
============================================================

DaveSoft_CopyRite_Vista.CopyRite -> Nvu
Opera -> Firefox_JRE

============================================================
All packages found:
============================================================

Name                                                   GUID
—-                                                        —-
Nvu                                                      3AAC7EE6-84C4-4021-966B-56C52FF95AAF
WinDirStat                                            3C5E1C59-D56E-4463-B9A0-5190034E6223
DaveSoft_CopyRite_Vista.CopyRite   4A7697E4-ED02-4D87-A8F0-88D7DEB914DE
Firefox_JRE                                         999E8458-D477-4975-B3C8-3BCE1252B991
Opera                                                   24D14B13-1838-45B2-9DAC-78D0A7432F69

You can get all the details and find the script here:

http://blogs.sepago.de/helge/2010/01/06/powershell-script-lists-app-v-package-dependencies-dynamic-suite-composition-dsc/

As always, this script is not made nor tested by Microsoft and we make no warranties or support it in any way, etc etc, but it's something that should make your life as an App-V admin a little bit easier.

Enjoy!

J.C. Hornbeck | System Center Knowledge Engineer

Solution: Error message when you try to publish a Windows Installer package for a virtual application from a network share to an App-V Client: xxxxxx-xxxxxx0A-000001D1

After you sequence an application that uses the Microsoft Application Virtualization (App-V) Sequencer version 4.5 or a later version, you have the option of generating a Windows Installer package to publish the application. If you try to publish a Windows Installer package that is located on a network share, you may receive the following error message:

The Application Virtualization Client could not complete the operation.

Additionally, the corresponding Sftlog.txt file contains several additional errors that have a result code (also known as rc) of xxxxxx2A-00000005. Also, the Windows Installer log file contains logs that resemble the following:

=== Logging stopped: date time ===MSI (c) (3C:68) [11:53:01:145]: Note: 1: 1708 MSI (c) (3C:68) [11:53:01:145]: Note: 1: 2262 2: Error 3: -2147287038 MSI (c) (3C:68) [11:53:01:145]: Note: 1: 2262 2: Error 3: -2147287038 MSI (c) (3C:68) [11:53:01:145]: Product: msitest -- Installation failed.

For details on the cause and how to fix this issue please see the following new Knowledge base article:

KB979598 - Error message when you try to publish a Windows Installer package for a virtual application from a network share to an App-V Client: "xxxxxx-xxxxxx0A-000001D1"

J.C. Hornbeck | System Center Knowledge Engineer

Now available for download: Hotfix Package 1 for Microsoft Application Virtualization 4.5 Service Pack 1: January 2010

Just a quick FYI that we recently released a new Knowledge Base article documenting a hotfix package for January 2010 that contains the latest hotfixes for Microsoft Application Virtualization (App-V) 4.5 Service Pack 1 (SP1).

You can get all the details on the specific issues that are fixed as well as download the hotfix here:

KB978480 - Hotfix Package 1 for Microsoft Application Virtualization 4.5 Service Pack 1: January 2010

J.C. Hornbeck | System Center Knowledge Engineer

Solution: Licensing error when you run an Adobe Creative Suite 4 Application on a x64 App-V client platform

When you virtualize one or more applications from Adobe's Creative Suite 4 (CS), such as Acrobat Reader or Adobe Photoshop, you may receive the following error message:

Licensing for this product has stopped working.
You cannot use this product at this time. You must repair the problem by uninstalling and then reinstalling this product or contacting your IT administrator or Adobe customer support for help.
Error:129:6

Note This error occurs within 15 minutes after you start a virtualized instance on the x64 Application Virtualization (App-V) client.

You may also receive the following error message:

This product has encountered a problem which requires that you restart your computer before it can be launched.
If you continue to see this message after restarting your computer, please contact either your IT administrator or Adobe technical support for help, and mention the error code shown at the bottom of this screen.
Error:148:3

This issue as well as the cause and resolution are discussed in the new App-V Knowledge Base article below:

KB979595 - Licensing error when you run an Adobe Creative Suite 4 Application on a x64 App-V client platform

J.C. Hornbeck | System Center Knowledge Engineer

App-V 4.6 and applications sequenced using earlier versions

With the release of Microsoft Application Virtualization 4.6 looming on the horizon, a question that seems to pop up over and over again is "Can I run all my apps that I sequenced using App-V 4.5 or 4.2 with the new App-V 4.6 client?"  Another one is "Can I run my old 32-bit packages using the new App-V 64-bit client?"  The short answer to both is Yes but I have a couple bullet points below that should help clear up some of the confusion:

• All of your existing 4.x packages are valid and can continue to be used on the 4.6 client.  All that is required is to modify the OSD file to include the OS values for the 32 and/or 64-bit platform as appropriate.  Below is a snippet from an OSD that shows the new 64-bit related tags and what they would look like:

• All of your existing 4.x packages can be used with either the 32-bit or the 64-bit App-V 4.6 client.
• If you want to sequence and run 64-bit applications, sequence the 64-bit app on a 64-bit OS using the 4.6. sequencer and specify x64 as the target platform. An example of where you would do this is shown below:

• You can continue to sequence 16-bit apps using App-V 4.6, however those sequencings (created with 4.6 or prior releases) will not run on the 64 bit-platforms.

Note: 4.x includes all version from 4.1 SP1 to current.

Note: New 32-bit applications sequenced with the 4.6 sequencer are NOT supported on 4.5 client as indicated in the support matrix below.

Hope this helps,

J.C. Hornbeck | System Center Knowledge Engineer

Solution: You receive an access denied error message when you try to start the APP-V client console

You may receive an access denied error message when you start the Microsoft Application Virtualization 4.5 (APP-V) client console by using the local administrator account.  Additionally, you may receive an error message that resembles the following:

Error code: xxxxxx-xxxxxx33-00000005

If you're running into this issue then we just published a new Knowledge Base article you'll probably be interested in:

KB978554 - You receive an access denied error message when you try to start the APP-V client console

J.C. Hornbeck | System Center Knowledge Engineer

How to remove servers from the App-V management console

We occasionally get questions about how to remove management servers from the management console and although there is no simple way to delete a single server from the management console what you can do as a workaround is essentially delete them all and then re-add the ones you want to keep.  It's a real easy process and goes like this:

1) Run mmc.exe

2) Open File->Add\Remove Snap-in.

3) Click the Add button

4) Select App Virt Management Console

5) Provide the Host Name of one of the servers and click OK.

6) Click Close and then Click OK

7) Add any additional servers, excluding the servers that you want to delete.

8) Click File -> Save and overwrite the sftMMC.msc file.  The default location is “C:\Program Files\Microsoft System Center App Virt Management Server\App Virt Management Console”.

Now every time you run the console you'll only see the servers you added.

J.C. Hornbeck | System Center Knowledge Engineer

How to publish an App-V-enabled application in Citrix XenApp

Just a quick heads up on an App-V KB article we updated last week.  This one describes how to publish an App-V-enabled application in Citrix XenApp:

To publish an App-V-enabled application in Citrix XenApp, follow these steps:

1. Publish Sfttray.exe or publish Sftrun.exe.
2. Publish the .OSD file.
3. Publish the application name followed by a percent sign and then an asterisk (%*) or publish the application name and version followed by a percent sign and then an asterisk.

To continue reading and see all the details check out the Knowledge Base article below:

KB931576 - How to publish an App-V-enabled application in Citrix XenApp

J.C. Hornbeck | System Center Knowledge Engineer

Upgrade to ConfigMgr 2007 SP2 may break App-V File Type Associations

When you upgrade a computer that is running the App-V 4.5 client to System Center Configuration Manager 2007 SP2, it may break all the File Type Associations (FTA's) for the virtualized applications.  This can occur because the SP2 installer updates the following key in the registry as part of the Configuration Manager 2007 Service Pack 2 upgrade:

HKEY_CLASSES_ROOT\SCCM.VAppLauncher\shell\Open\command

But it does not update the other two keys that App-V uses:

HKLM\SOFTWARE\Microsoft\SoftGrid\4.5\Client\UserInterface - DDELaunchMSICommand and LaunchMSICommand

This causes all the FTAs that were created through a published APP-V application to break, until a time when a new application is published to the machine which triggers the client to update the key itself.  At this point the FTAs for the newly published app would work but the FTAs for all other already existing apps would still be broken.

Resolution

If you publish an application that has FTAs to a client then it will force an update of the previously mentioned key in the registry.  The problem with this is that the application only reads that registry key on startup so the newly published application will be fixed but none of the others.  To fix all of the other applications you would need to restart the App-V client machine after publishing a new app.

Instead of re-publishing an app, I have created the following script that will update those registry keys without requiring you to re-publish an application. Note that you will need to restart the computer after running the script for the fix to take effect.  This can be done manually or automated via a script or management system, etc.

Here is the code of the Visual Basic script:

==========================

On Error Resume Next

'Script Name: App-V_Client_Fix.vbs
'Script Author: BRShaw
'Script Purpose: Fix the FTAs for App-V clients that have been upgraded via a Service Pack
'Script Creation Date: 12/08/2009
'Script Modified Date: 12/08/2009
'Script Version: 1.0
'Revision History

'Ver Date      Person                  Description
'-------------------------------------------------------------------------------------
'1.0    12/08/2009   Brian Shaw                 Created Script.

If UCase(Right(WScript.FullName, 11)) = "WSCRIPT.EXE" Then
  wscript.echo "This script must be run under CScript." _
    & VbCrLf & "You can set this by running: CScript //H:CScript" _
    & VbCrLf & "at the command line."
  WScript.Quit
End If

''******************************************************************************
'* Global Variables
''******************************************************************************
Dim strOutFile, strDir
Dim strAppLauncherValue, strAppLKeyPath, strAppLValueName, strAppLValue
Dim strUIValue, strUIKeyPath, strUIValueName, strUserInterfaceValue
Dim objTextFile, objWMIService, objFile
Dim arrAppLValues
Debug_On = False
Const DeleteReadOnly = TRUE
Const HKEY_CURRENT_USER = &H80000001
Const HKEY_LOCAL_MACHINE = &H80000002
Const ForReading = 1
Const OverwriteExisting = True
Const ForAppending = 8
StrComputer = "."
set oShell = createobject("wscript.shell")
strDir = oShell.currentdirectory
strOutFile = strDir & "\App-V_Fix_Output.txt"
strAppLauncherValue = "None"
strUserInterfaceValue = "None"

''******************************************************************************
'* Create a Text file for output of the script
''******************************************************************************
Set objFSOFileDelete = CreateObject("Scripting.FileSystemObject")
'If the output file exists befor then delete it.
If objFSOFileDelete.FileExists (strOutFile) Then
objFSOFileDelete.DeleteFile(strOutFile)
End If
'Create the Text file to write standard out to.
Set objFSOFileWrite = CreateObject("Scripting.FileSystemObject")
Set objTextFile = objFSOFileWrite.OpenTextFile (strOutFile, ForAppending, TRUE)
objTextFile.WriteLine(Now)

''******************************************************************************
'* Determine What the App launcher setting is
''******************************************************************************
Set oReg=GetObject("winmgmts:{impersonationLevel=impersonate}!\\" & strComputer & "\root\default:StdRegProv")
strAppLKeyPath = "SOFTWARE\Classes\SCCM.VAppLauncher\shell\Open\command"
strAppLValueName = "command"
oReg.GetMultiStringValue HKEY_LOCAL_MACHINE,strAppLKeyPath, strAppLValueName,arrAppLValues

If instr(arrAppLValues(0), "VirtualApp") > 0 Then
  strTemp = Trim(arrAppLValues(0))
  strAppLauncherValue = strTemp
End If

If Debug_On Then
  objTextFile.WriteLine("This is the value of the first Array key: " & arrAppLValues(0))
  objTextFile.WriteLine("This is the value of the App Launcher key pulled from the registry: " & strTemp)
  objTextFile.WriteLine("This is the value of the App Launcher key we are using: " & strAppLauncherValue)
End If

If strAppLauncherValue = "None" Then
    objTextFile.WriteLine("The value did not exist in the regsitry!!")
End If

''******************************************************************************
'* Determine What the UserInterface Setting is
''******************************************************************************
strUIKeyPath = "SOFTWARE\Microsoft\SoftGrid\4.5\Client\UserInterface"
strUIDDEValueName = "DDELaunchMSICommand"
oReg.GetStringValue HKEY_LOCAL_MACHINE,strUIKeyPath,strUIDDEValueName,strUIValue

If instr(strUIValue, "VirtualApp") > 0 Then
  strUserInterfaceValue = strUIValue
End If

If Debug_On Then
  objTextFile.WriteLine("This is the value of the User Interface key pulled from the registry: " & strUIValue)
  objTextFile.WriteLine("This is the value of the User Interface key we are using: " & strUserInterfaceValue)
End If

If strUserIValue = "None" Then
    objTextFile.WriteLine("The value did not exist in the regsitry!!")
End If

''******************************************************************************
'* Set the new value and write it back to the registry
''******************************************************************************

If instr(strUserInterfaceValue, strAppLauncherValue) > 0 Then
  objTextFile.WriteLine("The registry has alreday been updated with the correct App Launcher Command!")
  objTextFile.WriteLine("Here is the value of the App Launcher key: " & strAppLauncherValue)
  objTextFile.WriteLine("Here is the value of the User Interface key: " & strUserInterfaceValue)
Else
  Dim intStringLength, intStartPlace, intNumCharFromRight
  Dim strRightSide, strNewValue
  'Get the length of the user interface key
  intStringLength = Len(strUserInterfaceValue)
  'Find the starting place to cut the string
  intStartPlace = InStr(strUserInterfaceValue, "launch")
  'Find how many characters to pull from the right side, had to subtract the 3 places back from the search string we used
  intNumCharFromRight = intStringLength - (intStartPlace - 3)
  strRightSide = Right(strUserInterfaceValue, intNumCharFromRight)
  If Debug_On Then
    objTextFile.WriteLine("This is the length of the string: " & intStringLength)
    objTextFile.WriteLine("This is the Starting location we are using: " & intStartPlace)
    objTextFile.WriteLine("This is the Number of Characters from the right side we are pulling: " & intNumCharFromRight)
    objTextFile.WriteLine("This is the string we pulled back:  " & strRightSide)
  End If
  'we are now going to add the strings together to get the completed new string
  strNewValue = strAppLauncherValue & strRightSide
  If Debug_On Then
    objTextFile.WriteLine("This is the strings added together: " & strNewValue)
  End If
  'Update the registry key with the new values
  oReg.SetStringValue HKEY_LOCAL_MACHINE,strUIKeyPath,strUIDDEValueName,strNewValue
  strUIValueName = "LaunchMSICommand"
  oReg.SetStringValue HKEY_LOCAL_MACHINE,strUIKeyPath,strUIValueName,strNewValue
  objTextFile.WriteLine("The User Interface option has been updated with this value: " & strNewValue)
End If

==========================

I have tested the script and it does work, just don't forget to restart the client machine.  Just copy all text between the "===" lines and then put in a file called App-V_Client_Fix.vbs and execute it with cscript like this:

cscript App-V_Client_Fix.vbs

The output of the file will be contained in a file called App-V_Fix_Output.txt

Hope this helps,

Brian Shaw | Senior Support Escalation Engineer

New KB - Error message when you upgrade the SQL Server database role from App-V Management Server 4.1 to App-V Management Server 4.5: "Error 25119"

When you try to upgrade the SQL Server database role from Microsoft Application Virtualization (App-V) Management Server 4.1 to Application Virtualization Management Server 4.5, the upgrade may fail with the following error message:

Error 25119. The installation program could not upgrade the configuration data store. Please see the installation log file for more information.

The Knowledge Base article below contains a script that will resolve this issue:

KB976641 - Error message when you upgrade the SQL Server database role from Application Virtualization Management Server 4.1 to Application Virtualization Management Server 4.5: "Error 25119"

Enjoy!

J.C. Hornbeck | System Center Knowledge Engineer

New KB - Hotfix Package 6 for Microsoft Application Virtualization 4.5 Cumulative Update 1: September 2009

This article describes a hotfix package for September 2009 that contains the latest hotfixes for Microsoft Application Virtualization 4.5 Cumulative Update 1.

Note We recommend that you test hotfixes before you deploy them in a production environment. Because the builds are cumulative, each new hotfix release contains all the hotfixes and all the security fixes that were included with the previous update package. We recommend that you consider applying the most recent fix release that contains the most necessary hotfixes.

This hotfix package addresses the following issues:

• In some scenarios, an application may not start, and you receive a DLL error or a "File Not Found" error. This issue is most likely to occur on a multiprocessor computer.
• It takes significantly longer to stream a package over the RTSPS protocol than to stream a package over the RTSP protocol.
• When you use TrueCrypt for drive encryption, any tries to mount an encrypted volume may generate a 0xA stop error.
• The Microsoft Application Virtualization 4.5 client leaks paged pool memory. This problem occurs when you apply a disk quota to the profile directories of a user and when the disk quota is near the limit.
• A virtual application that calls the RegQueryMultipleValues function may experience unexpected errors or cannot start. For example, you receive error messages when you start or shutdown the Trapeze application. Then, the application does not work correctly.
• When an Application Virtualization 4.5 client tries to perform a publishing update procedure over HTTP or over HTTPS, the procedure is not completed successfully. Specifically, the procedure is not completed successfully if a package contains pathnames that have Japanese characters. This problem occurs when the Application Virtualization 4.5 client has Windows Internet Explorer 6 installed and runs a Japanese version of Windows XP.
• When it is run as a virtual application, Microsoft Office Access 97 generates an error message 1008 when Office Access 97 is moving temporary files.
• When an Application Virtualization 4.5 client tries to perform a publishing update procedure over HTTP or over HTTPS on an IPv6 network, the procedure is not completed successfully.
• When you expand a %APPDATA% environment variable to a universal naming conventions (UNC) path, application-specific failures occur when you start virtual applications.
• The Microsoft Application Virtualization 4.5 client cannot log on to a publishing server. This problem occurs in environments that have a trust relationship and a mapped user account between a Windows domain and an MIT Kerberos realm. Additionally, you receive an error message 8009030C.

For all the details and to download the hotfix package see the following Knowledge Base article:

KB974278 - Hotfix Package 6 for Microsoft Application Virtualization 4.5 Cumulative Update 1: September 2009

J.C. Hornbeck | System Center Knowledge Engineer

Do I need to re-sequence my applications when I move to a new OS?

This question has come up numerous times:

Do I need to re-sequence my applications when I move to a new OS?

There have been multiple statements published and circulated about this topic and the real answer is “it depends!"  What’s really important is that you test your existing virtual applications on the new operating system to make sure they work correctly before deploying.  You may find that they work fine, but if you encounter problems you may need to re-sequence on the new operating system.

Here’s the current support statement for App-V from the product group and this statement supersedes all others.

It is often possible to sequence on one OS and run the virtualized app on a different OS, however this scenario is both app and OS dependent and is not guaranteed to work for all app/OS combinations since App-V is not a general purpose OS compatibility solution. If problems are encountered, the customer may be required to sequence on the same OS environment as the App-V client is running in order to resolve those problems.

Note that whatever OS platform is used when sequencing, our “best practices” guidance requires customers to test the sequenced app on all delivery OS platforms prior to putting into production.

Hope this helps,

Peter Ballantyne | Technical Writer

App-V and support for applications with custom shell extensions

Microsoft Application Virtualization does not support applications that use shell extension handlers implemented with a custom dynamic-link library (DLL). The reason that APP-V cannot support applications with custom shell extensions is that this would require providing Windows Explorer access to the virtual environment.  Shell extensions are sometimes referred to as Shell integration.

Some applications allow disabling of their customer shell extensions.  If the application you would like to sequence allows you to disable the shell extension it probably can be sequenced in App-V.

Shell extensions are in-process Component Object Model (COM) objects that extend the abilities of the Windows operating system.

For more information about Shell Extension Handlers check out this MSDN article.
http://msdn.microsoft.com/en-us/library/cc144067(VS.85).aspx

You can use the sysinternals tool Autoruns to view installed Explorer shell extensions.
http://technet.microsoft.com/en-us/sysinternals/bb963902.aspx

You may also enjoy reading the case study about Sequencing Applications for Deployment at Microsoft.
http://technet.microsoft.com/en-us/library/dd871278.aspx.

Jim Truchon | Senior Escalation Engineer

New App-V KB Article: KB976248 - Error message when you upgrade an Application Virtualization client from Windows Vista to Windows 7: "Program Compatibility Report"

When you upgrade a Microsoft Application Virtualization (also known as App-V) client from Windows Vista to Windows 7, you receive the following error message:

Program Compatibility Report
The program is blocked due to compatibility issues.
Report the problem to see if a solution is available. Windows will automatically display a website with more information about compatibility problems.
Microsoft Application Virtualization is incompatible with this version of Windows. For more information, contact Microsoft.

For the details of the issue and the resolution see the following Knowledge Base article:

KB976248 - Error message when you upgrade an Application Virtualization client from Windows Vista to Windows 7: "Program Compatibility Report"

Enjoy!

J.C. Hornbeck | System Center Knowledge Engineer

Announcing App-V 4.6 RC and integration with Office 2010 Beta!

First of all, we are excited to announce the availability of App-V 4.6 RC! In August we announced the App-V 4.6 Beta. Since then we have taken in lots of customer feedback and continue to refine the App-V 4.6 release so that we can deliver a great product!  We invite you to check out the RC release by registering and downloading the App-V 4.6 RC release via Microsoft Connect, where you can also submit feedback directly to the team.

We’re not done though, in addition we’d like to share some great news and also announce our integration with Office 2010 Beta:

Microsoft Office 2010 Beta, Ready to be Sequenced With the Microsoft Office 2010 Beta Deployment Kit for App-V

As you know the Office team just completed a major milestone Microsoft Office 2010 Beta, congrats to the team!  Throughout the process of building Office 2010 the App-V and Office teams have been working very closely to make sequencing Office 2010 Beta possible with App-V 4.6 RC!  We have taken the feedback and requests from post-Office 2007 and App-V 4.5 releases, and have been hard at work implementing a solid integration experience for Office when App-V 4.6 releases in H1 2010. 

So what’s Different when using Microsoft Office 2010 Beta and App-V 4.6 RC together?

Office 2010 has introduced a new piracy protection initiative, the Software Protection Platform (SPP) service.  This service uses a machine’s hardware characteristics and product key to activate the installation, which is performed during the first Office application launch. 

Since the Office 2010 product activation is linked to the hardware on which Office is originally installed, customers who wish to deploy Office 2010 using App-V must physically install the SPP service on the sequencer machine before beginning the sequencing process – and on any client machines that will stream and run Office 2010. 

Our engineering teams have collaborated to address the top customer issues that people were running into when virtualizing past versions of Office.   As a result, Office 2010 has a much more integrated user experience.  The Office 2010 integration delivers key productivity enhancements and a seamless user experience by enabling the following::

· Microsoft SharePoint Integration - You can open, edit, and save Microsoft Office documents using Microsoft SharePoint.

· Microsoft Outlook Fast Search - You can use Microsoft Windows Desktop Search to find specific messages in your inbox.

· MAPI Proxy - You can connect to your inbox using Microsoft Outlook Send To functionality.

· Microsoft Office Document Indexing - You can index your documents so that you can use Microsoft Windows Search to locate files.

· Virtual Mail Control Panel icon - You can use the Email icon in Control Panel to perform advance mail configuration.

· URL protocol handler - You can configure links in the browser and specify the appropriate associated Microsoft Office application.

· Send to Microsoft OneNote Printer driver - You can print documents to Microsoft OneNote.

To help customers facilitate this process, we have created the Microsoft Office 2010 Deployment Kit for App-V (Beta).  The Deployment Kit contains both the required SPP licensing component and Office 2010 integration features.

And what’s even more exciting, you can get your hands on it now.

How Do I Sequence Microsoft Office 2010 Beta for App-V 4.6 RC?

1. Download Office 2010 Beta here

2. Download the Microsoft Office 2010 Deployment Kit for App-V (Beta)

3. Download App-V 4.6 RC on Microsoft Connect

4. Read the App-V recipe for sequencing Office 2010 Beta on Microsoft Connect.

For detailed information on whether your environment meets the requirements of Office 2010 and App-V 4.6 RC, please refer to the App-V recipe.

Please note: We are providing a recipe to support the sequencing and testing of these pre-release products on Microsoft Connect.  Please provide feedback via Microsoft Connect, by choosing FEEDBACK once logged into the App-V 4.6 Program.

We look forward to hearing about your App-V 4.6 RC and Office 2010 experience!