The Microsoft Application Virtualization Blog : KB Article

KB: Allowing applications running inside an App-V Virtual Environment (VE) to read from or write to the native registry

J.C. Hornbeck — Thu, 06 Sep 2012 17:06:31 GMT

Here’s a new Knowledge Base article we published. This one explains how to allow applications running inside an App-V Virtual Environment to read from or write to the native registry on a client.

=====

Summary

The purpose of this document is to describe the support for registry pass-through functionality that exists in Microsoft Application Virtualization (App-V) version 4.6. Registry pass-through functionality is used when applications running inside a Virtual Environment (VE) need to read/write the contents of the native registry on a client.

More Information

The problem registry pass-through functionality addresses is when an application needs to write values to the native, non-virtual registry such that those values are created on the client system and are then visible to programs that have access to the native registry (e.g. natively installed applications).

While the isolation provided by the VE is normally desired and is a cornerstone of the functionality delivered by App-V, there are cases where an application needs to have read/write access to the native system and update its state. Registry pass-through functionality provides the ability to write-through, or pass-through, registry operations from applications running inside the VE. Values that are written to pass-through locations from inside the VE can subsequently be used by other applications.

Declaring a pass-through

Pass-through keys are defined in the following location on the client system:

HKLM\Software\[Wow6432Node\]Microsoft\Softgrid\4.5\SystemGuard\Overrides\VirtualRegistryPassThroughEx

The VirtualRegistryPassThroughEx key should contain REG_MULTI_SZ type values identifying the registry keys on the client that should be accessed natively by an application in the VE.

Examples:

HKEY_LOCAL_MACHINE\Software\Microsoft\DirectDraw
HKEY_CURRENT_USER\Software\Microsoft\ActiveMovie\devenum

All registry values read or written at these levels, or anywhere in the tree underneath, will go to the native registry on the system on which the VE is running.

Collisions

Package overlaps with pass-through

In all cases, the registry values in the package take precedence over the pass-through locations. This means that locations that are defined in both locations – pass-through location and virtual registry – will create a runtime environment that ignores the pass-through location. For example, if a package has HKEY_LOCAL_MACHINE\Software\Microsoft\DirectDraw\KeyName\VRegValue=5 and a registry pass-through is defined for HKEY_LOCAL_MACHINE\Software\Microsoft\DirectDraw then VRegValue will have value 5 inside the VE regardless of its value on the target machine.

DSC packages overlap with pass-through

DSC packages (i.e. packages using Dynamic Suite Composition), either primary or secondary, will have the same behavior as with the non-DSC case for which there is overlap between pass-through and native.

For more information on DSC see How To Use Dynamic Suite Composition (http://technet.microsoft.com/en-us/library/cc843662.aspx)

64-bit Considerations

Strings defined as pass-through registry keys are not modified via 32-on-64 Operating System functions such as redirection. The strings will be processed verbatim.

Existence of key on local system

In order for this functionality to operate predictably, the key that is specified in the pass-through must also exist on the local system.

=====

For the most current version of this article please see the following:

2750869 - Allowing applications running inside an App-V Virtual Environment (VE) to read from or write to the native registry

J.C. Hornbeck | Knowledge Engineer | Management and Security Division

Get the latest System Center news on Facebook and Twitter:

The Forefront Server Protection blog: http://blogs.technet.com/b/fss/
The Forefront Endpoint Security blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/

KB: Expanding an App-V 4.6 SP1 package fails with error: Failed to expand package to disk

J.C. Hornbeck — Tue, 04 Sep 2012 18:52:08 GMT

Here’s a new Knowledge Base article we published. This one talks about an issue you might run into where expanding an App-V 4.6 SP1 package fails with an error saying “Failed to expand package to disk.”

=====

Symptoms

To successfully sequence a plug-in with the 4.6 SP1 Sequencer, the package for the primary application should be expanded to the local system drive. If the package (SFT, ICO, SPRJ, OSD, etc.) is on a local drive of the Sequencer, but not the C: drive, the expansion will fail.

Using TOOLS>Expand to Local System expands the package back to the original file structure on the Q: drive. When the package to be expanded is not on the C: drive, this error occurs:

"Failed to expand package to disk - check the sequencer log for error details. Revert the machine to clean state and retry."

Cause

This is a known issue in this 4.6 SP1 release.

Resolution

Revert the Sequencer and copy the package to a folder on the C:\ drive before expanding. Expanding from a UNC path share will also work.

=====

For the most current version of this article please see the following:

2513357 - Expanding an App-V 4.6 SP1 package fails with error: Failed to expand package to disk

J.C. Hornbeck | Knowledge Engineer | Management and Security Division

Get the latest System Center news on Facebook and Twitter:

KB: Changes to an App-V application are not included when deployed using System Center 2012 Configuration Manager

J.C. Hornbeck — Tue, 07 Aug 2012 17:50:54 GMT

Here’s a new Knowledge Base article we published. This one talks about an issue where changes to an App-V package may not get delivered when the app is deployed using ConfigMgr 2012.

=====

Symptoms

Consider the following scenario:

You create a Microsoft Application Virtualization (App-V) application.
You deploy the source for the application to a System Center 2012 Configuration Manager distribution point.
You change the application by using the App-V Sequencer.
You deploy the content for the updated application to the distribution point.

In this scenario, when users run the application, your changes are not included in the application.

Cause

This problem occurs because the App-V Sequencer saves the virtual application's SFT file (.sft) using a different name when changes are saved for the application. For example, if your virtual application is named MyApp.sft, the App-V Sequencer will save the changed application as MyApp_2.sft. Without manual adjustment, the Deployment Type for the App-V application will still refer to the original .sft file name.

Workaround

To work around this problem, change the Deployment Type to refer to the current .sft file manually.

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

More Information

Because the file name changes when you update an App-V application, Binary Delta Replication is not used to download the updated content to the clients. Binary Delta Replication is possible only when you work with two versions of a file that have the same name.

=====

For the most current version of this article please see the following:

2683934 - Changes to an App-V application are not included when deployed using System Center 2012 Configuration Manager

J.C. Hornbeck | Knowledge Engineer | Management and Security Division

Get the latest System Center news on Facebook and Twitter:

The Forefront Server Protection blog: http://blogs.technet.com/b/fss/
The Forefront Endpoint Security blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity- support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/

Hotfix Package 6 for Microsoft Application Virtualization 4.6 SP1: April 2012 Now Available

J.C. Hornbeck — Tue, 22 May 2012 20:47:19 GMT

This article describes a hotfix package that contains the latest fixes for Microsoft Application Virtualization (App-V) 4.6 Service Pack 1 (SP1). This hotfix package is dated April 2012.

This hotfix package fixes the following issue:

On a server that is running Windows Server 2008 R2, the Microsoft Application Virtualization service receives an exception and then crashes. After the crash, the service cannot be started because of the lost file system, and the server must be restarted.

For all the details and a download link please see the following:

KB2693779 - Hotfix Package 6 for Microsoft Application Virtualization 4.6 SP1: April 2012

J.C. Hornbeck | System Center & Security Knowledge Engineer

Get the latest System Center news on Facebook and Twitter:

KB: How to sequence the Microsoft System Center Configuration Manager 2007 R3 Admin Console using Microsoft App-V

J.C. Hornbeck — Thu, 19 Apr 2012 20:16:48 GMT

Here’s one more Knowledge Base article we published today. This one shows you how to sequence (virtualize) the ConfigMgr admin console in App-V.

=====

Symptoms

When trying to Sequence (virtualize) the System Center Configuration Manager 2007 (ConfigMgr) administrator’s console, the resulting package will generate the following error and fail to run:

MMC cannot initialize the snap-in

Resolution

Using the steps below, you can virtualize the admin console and have it run successfully.

NOTE In the example below, it is assumed that we are sequencing the Microsoft System Center Configuration Manager 2007 R3 admin console for the 64-bit version of Windows 7 Service Pack 1.

1. Follow Best Practices for the Microsoft Application Virtualization Sequencer : http://technet.microsoft.com/en-us/library/dd351420.aspx

2. Build the clean system with 64-bit version of Windows 7 SP1 and join it to the domain.

3. Install the APPV 4.6 SP1 Sequencer with Hotfix 3 (http://support.microsoft.com/kb/2571168). Launch the Microsoft Application Virtualization Sequencer and select Create New Virtual Application Package.

4. Select Create Package (Default) option and Click Next. Note that Prepare the Computer for Creating a Virtual Package may give the Warning “Windows Defender is active”. If so, launch the Services.msc snap-in and stop the Windows Defender service. After doing so, click refresh and then click Next.

5. Select the Standard Application (default) option and click Next.

6. On the Select Installer Screen, browse to “SPLASH.HTA” on the Configuration Manager (ConfigMgr) installation media and click Next.

7. Name the Package SCCMConsole.001 and leave other options as the defaults and click Next.

8. Once the ConfigMgr installation screen appears, click Install Configuration Manager 2007 SP2 and click Next.

9. Select Install or Upgrade an Administrator Console and click Next.

10. Accept license agreement and Click Next.

11. Select No, I do not want to participate right now and click Next.

12. Leave the Destination Folder to the default (i.e. C:\Program Files(x86)\Microsoft Configuration Manager Console\) and click Next.

13. Provide your site Server Name and Click Next, then Next again.

14. Ensure the Pre-check passes then click on Begin Install.

15. Once the installation finishes click Next and then click Finish.

16. Back on the Installation screen on the Sequencer, click on the “Run” option to install the ConfigMgr R3 prerequisite hotfix http://support.microsoft.com/kb/977384) and R3.

17. Provide the path to the 977384 hotfix and choose Install.

18. When complete and back at the Installation screen on the Sequencer, click on the “Run” option to install R3.

19. Click on Run and provide the path to R3’s “SPLASH.HTA” and click Next and install R3.

20. When complete, click on I am Finished installing

21. Select the ConfigMgr console and run it. After launching the console close it. Click Next to review the installation report and click Next when you’re done.

22. Select the Customize option and click Next

23. Now under Edit Short Cut screen, right Click and edit the ConfigMgr Console.

24 Click on “Change Icon…” and browse to “C:\Program Files\Microsoft Configuration Manager Console\bin\i386\” and select “SETUP.EXE”

25. Select the proper icon and provide the version No: 4.00.6487.2157

26. Click “Save”

27. Right click “ConfigMgr Documentation” and click “Edit”

28. Click on “Change Icon…” and browse to “C:\Windows” and select “hh”

29. Select the proper icon and click “Save”

30. Right click on ConfigMgr setup and select Remove.

31. Right click on ConfigMgr Setup Repair Wizard and select Remove.

32. Click next and then Run ALL.

33. Select the Target OS, click Next and then select Create the Package. The Package will be saved as SCMMConsole.001.

34. Copy the Package to the App-V management content share.

35. Edit the OSD file of ConfigMgr Console.OSD in Notepad. Change the VALUE of <SUBSYSTEM VALUE= "windows"/> to <SUBSYSTEM VALUE= "console"/> and save the OSD file.

36. Now follow the normal procedure to import the Package in to your APPV Management server and verify that the console is published to the APPV users.

When you double click ConfigMgr Console on an App-V client you may see the error “MMC cannot initialize the snap-in.” If so, hold the Shift Key and right-click on ConfigMgr Console and select Run as different user. Provide whichever user credentials that have access to the ConfigMgr site server.

More Information

This is published on the Microsoft App-V blog here:

http://blogs.technet.com/b/appv/archive/2012/03/20/how-to-sequence-the-system-center-configuration-manager-2007-r3-admin-console-with-microsoft-app-v.aspx

Also see the following Knowledge Base article:

2559075 - Elevation and Run-As Considerations in Microsoft App-V Environments (http://support.microsoft.com/kb/2559075)

=====

For the most current version of this article please see the following:

2685079 : How to sequence the Microsoft System Center Configuration Manager 2007 R3 Admin Console using Microsoft App-V

J.C. Hornbeck | System Center & Security Knowledge Engineer

Get the latest System Center news on Facebook and Twitter:

KB: Launching an App-V application fails with "Unable to initialize package information (0x00000000)" error

J.C. Hornbeck — Thu, 19 Apr 2012 18:02:58 GMT

Here’s a new Knowledge Base article we published this morning. This one talks about a couple work arounds for an App-V issue where launching an App-V application fails with "Unable to initialize package information (0x00000000)":

=====

Symptoms

When launching an application virtualized with Microsoft Application Virtualization (App-V), the application fails to start and generates the following error message:

Unable to initialize package information (0x00000000)

Cause

This can occur when App-V is set to work in Full Infrastructure Mode (http://technet.microsoft.com/en-us/magazine/2008.10.appv.aspx#id0110023) and the Configuration Manager (ConfigMgr) client agent is installed on the same machine where the App-V client is already installed. When the Configuration Manager client agent is installed, it assumes that it should handle the virtualized applications. During the Configuration Manager client agent installation, the App-V client cache is flushed and App-V registry keys are modified, causing the error described above.

Resolution

There are 3 potential work arounds for this issue:

1. The ConfigMgr client agent takes managing virtualized applications when “Allow virtual application package advertisement" in the Advertised Programs Client Agent properties in the ConfigMgr console is checked. If this box is unchecked, it is then possible to run both ConfigMgr and App-V client agents at the same time. To modify this setting, open the ConfigMgr Console, expand Site Database, Site Management, <Site Name>, Site Settings, Client Agents; then open the properties for Advertised Programs Client Agent. The next time the client agents refresh (or if you kick off a Machine Policy Retrieval & Evaluation Cycle), the App-V client will become the default handler again.

2. The second option is to manually modify the registry keys on the client back to the original values. Thus, we can make the following modifications:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SoftGrid\4.5\Client\UserInterface

Change to the following:

LaunchCommand "C:\Program Files\Microsoft Application Virtualization Client\sfttray.exe" /launch "<APP>"
DDELaunchCommand"C:\Program Files\Microsoft Application Virtualization Client\sftdde.exe" "<APP>" <DDE>"

However, keep in mind that if “Allow virtual application package advertisement" in the Advertised Programs Client Agent properties in the ConfigMgr console remains checked, it is possible that it will reset the registries to their previous values and the issue will reoccur.

3. The third option is to use ConfigMgr to manage the virtual applications instead of using the App-V management server. More info on this can be found here:

http://download.microsoft.com/download/f/7/8/f784a197-73be-48ff-83da-4102c05a6d44/APP-V/App-V_and_ConfigMgr_Whitepaper_Final.docx

More Information

Below are the App-V registry keys that are changed during the SCCM client agent installation:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SoftGrid\4.5\Client\UserInterface

LaunchCommand "C:\Windows\system32\CCM\VappLauncher.exe" /launch "<APP>"

DDELaunchCommand"C:\Windows\system32\CCM\VappLauncher.exe" /launch "<APP>"
Instead of the original values shown below:
LaunchCommand "C:\Program Files\Microsoft Application Virtualization Client\sfttray.exe" /launch "<APP>"

DDELaunchCommand"C:\Program Files\Microsoft Application Virtualization Client\sftdde.exe" "<APP>" <DDE>"

=====

For the most current version of this article please see the following:

2694295 : Launching an App-V application fails with "Unable to initialize package information (0x00000000)" error

J.C. Hornbeck | System Center & Security Knowledge Engineer

Get the latest System Center news on Facebook and Twitter:

HOTFIX: OSD tasks stop responding in System Center Configuration Manager 2007 SP2

J.C. Hornbeck — Tue, 03 Apr 2012 20:31:42 GMT

Here’s a new Knowledge Base article we published recently. This one is a hotfix for an issue where a ConfigMgr 2007 SP2 task to install a virtual application that is located on an App-V distribution point that has streaming enabled hangs (stops responding):

=====

Symptoms

Consider the following scenario. You create an operating system deployment (OSD) task on a site server that has Microsoft System Center Configuration Manager 2007 Service Pack 2 (SP2) installed. You configure the task to install a virtual application that is located on a Microsoft Application Virtualization (App-V) distribution point that has streaming enabled. In this scenario, the OSD task stops responding….

=====

For the most current version of this article and a download link for the hotfix itself please see the following:

2678547 : OSD tasks stop responding in System Center Configuration Manager 2007 SP2

J.C. Hornbeck | System Center & Security Knowledge Engineer

Get the latest System Center news on Facebook and Twitter:

Troubleshooting 04-0000180C / 6156 Errors in Microsoft Application Virtualization

J.C. Hornbeck — Tue, 27 Mar 2012 18:44:17 GMT

Here’s a new Knowledge Base article we published today. This one talks about troubleshooting an issue where attempting to upgrade a package in Microsoft Application Virtualization (App-V) fails with error 04-0000180C:

=====

Symptoms

Attempting to upgrade a package in Microsoft Application Virtualization (App-V) fails with error 04-0000180C:

C:\Program Files (x86)\Microsoft Application Virtualization Client>sftmime.com add package:" APP_V1.1" /manifest "C:\\Program Files (x86)\\SMS_CCM\\Cache\\ABC00076.2.S-1-5-21-1111111111-1111111111-1111111111-500\\APP_V1.1_manifest.xml" /overrideUrl "FILE://C:\\Program Files (x86)\\SMS_CCM\\Cache\\ABC00076.2.S-1-5-21-1111111111-1111111111-1111111111-500\\ABC00076.sft"

The Application Virtualization Client could not complete

the operation.

The operation failed because the GUID in the package

manifest matches a package name other than the one

specified. Verify the package name, and then try again.

Error code: 4605F3-18305104-0000180C

For System Center Configuration Manager (CfgMgr) clients, the VirtualApp.log will show entries similar to the following, exiting with error code 6156 (SWRC_PKG_NAMEDOESNOTMATCH):

<![LOG[Executing command line: "C:\Program Files\Microsoft SoftGrid\Microsoft SoftGrid Application Virtualization for Desktops\SFTMIME.COM" ADD PACKAGE:"Package1" /MANIFEST "C:\\WINDOWS\\system32\\CCM\\Cache\\ABC00500.3.S-1-5-21-1111111111-1111111111-1111111111-2672\\Package1.xml" /OverrideUrl "FILE://C:\\WINDOWS\\system32\\CCM\\Cache\\ABC00500.3.S-1-5-21-1111111111-1111111111-1111111111-2672\\ABC00500.sft"]LOG]!><time="16:37:46.837+-120" date="08-08-2008" component="VAppRegistration" context="" type="1" thread="3120" file="registrationhandler.cpp:1031">
<![LOG[The command completed with exit code 6156.]LOG]!><time="16:37:47.368+-120" date="08-08-2008" component="VAppRegistration" context="" type="1" thread="3120" file="registrationhandler.cpp:1140">

Cause

This error indicates that there is a mismatch between the package name of the original package and that of the upgraded package. This results in the App-V client incorrectly determining that there is a duplicate GUID, since the package GUID in both manifests will be the same. To successfully upgrade a package, both of the following conditions must be true:

1. The package GUID must be the same (the Version tag and VERSIONGUID tag will change).

2. The package name must be exactly the same. This can be verified by opening the original and upgrade package's manifest XML in a text editor to compare the NAME and GUID tags.

The NAME tag is derived from the Package Name field on the General Properties tab of the package. The App-V Sequencer allows this field to be changed after sequencing a package but before saving the files. To avoid this error, do not edit this field.

In a second variation, the Microsoft System Center Configuration Manager (ConfigMgr) Virtual Application Package Update Wizard allows for the Name: field to be changed on its General page. Editing the Name: or Version: fields of the New Package's values will result in the errors above.

Resolution

To avoid the 04-0000180C and 6156 errors listed above, do not change the package name in either the App-V Sequencer or the ConfigMgr Virtual Application Package Update Wizard. If the package manifest file is correct, simply re-run the Virtual Application Package Update Wizard without changing any values. If the package name has been changed in the Sequencer, re-sequence the application and do not change this value.

=====

For the most current version of this article please see the following:

2688524 : Troubleshooting 04-0000180C / 6156 Errors in Microsoft Application Virtualization

J.C. Hornbeck | System Center & Security Knowledge Engineer

Get the latest System Center news on Facebook and Twitter:

KB: How to Enable Automatic Crash Dump Generation in Microsoft Application Virtualization

J.C. Hornbeck — Mon, 26 Mar 2012 18:00:07 GMT

Here’s a new Knowledge Base article we published today. This one walks you through how to create a crash dump in Microsoft Application Virtualization should you ever need to do so as guided by a Microsoft support engineer:

=====

Symptoms

This article describes how to enable automatic crash dump generation for Microsoft Application Virtualization (App-V) 4.5 and 4.6 clients. This method has the advantage of using functionality already built in to the product, so no additional software is required to be installed. Note that enabling the registry keys below will potentially generate a number of large files in the Dumps folder; carefully monitor servers or desktops where this option has been set for disk usage. This should normally be done under the guidance of a Microsoft Support professional.

Resolution

To enable automatic crash dump generation, create the following registry value:

32-bit systems:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SoftGrid\4.5\Shared\exceptions

64-bit systems:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\SoftGrid\4.5\Shared\exceptions

Value: GenerateDumps

Type: REG_DWORD

Data: 1 to enable mini-dumps, 0 to disable (default value; uses WER or Dr. Watson)

Restart the Application Virtualization Client service (sftlist) to enable the setting.

More Information

Other values under this key:

=====

For the most current version of this article please see the following:

2690495 : How to Enable Automatic Crash Dump Generation in Microsoft Application Virtualization

J.C. Hornbeck | System Center & Security Knowledge Engineer

Get the latest System Center news on Facebook and Twitter:

KB: Error 0000B00F when attempting to delete a server from the Default Server Group in Microsoft Application Virtualization

J.C. Hornbeck — Thu, 01 Mar 2012 16:02:31 GMT

Here’s a new Knowledge Base article we published today. This one talks about how to fix an issue where you get error 0000B00F attempting to delete a server from the Default Server Group in Microsoft App-V:

=====

Symptoms

When attempting to delete a Server from the Default Server Group in the Microsoft Application Virtualization (App-V) Virtualization Management Console, the following error code is received:

0000B00F

Cause

This occurs because there are licenses assigned to the server that have to be removed before it can be deleted from the Default Server Group. If these licenses have not been automatically removed, it is typically due to the SoftGrid Close Orphaned Sessions Job failing to run or erroring out when it attempted to run. If the App-V database was migrated from another server, it's also possible that the four SoftGrid jobs were not be migrated over along with the database, meaning that these Orphaned Session entries never get cleared from the dbo.LICENSE_ASSIGNMENTS table.

Resolution

Manually run the SoftGrid Close Orphaned Sessions SQL Job to clear out the licenses or manually delete them from the dbo.LICENSE_ASSIGNMENTS table.

First, to determine the server_id of the server that cannot be deleted from the Default Server Group, look at the dbo.SERVERS table which will have the name and hostname fields to identify it (e.g. Server1 has a server_id of 1). Run the following SQL query against the App-V database to determine how many licenses are assigned to Server1:

Select * from License_assignments where server_id = 1

To delete these records directly from the App-V database, run the following SQL query against the App-V database:

Delete from License_assignments where server_id = 1

NOTE Please make a backup of the App-V database prior to running any command or making any modification.

More Information

If the App-V (or SoftGrid) Jobs are not present or not running correctly, eventually the App-V database will grow too large and cause related issues. Please see the following blog posts for more information:

Troubleshooting SoftGrid Database Growth Issues : http://blogs.technet.com/b/appv/archive/2008/08/04/troubleshooting-softgrid-database-growth-issues.aspx

Use the following blog to learn how to create the missing App-V SQL Jobs (Step 7), test and troubleshoot the App-V SQL Jobs (Step 9):

A Complete Guide to SQL 2008 App-V Database Migration : http://blogs.technet.com/b/appv/archive/2012/02/08/a-complete-guide-to-sql-2008-app-v-database-migration.aspx

=====

For the most current version of this article please see the following:

2679610 : Error 0000B00F when attempting to delete a server from the Default Server Group in Microsoft Application Virtualization

J.C. Hornbeck | System Center & Security Knowledge Engineer

Get the latest System Center news on Facebook and Twitter:

Now available: Hotfix Package 5 for Microsoft Application Virtualization 4.6 SP1: December 2011

J.C. Hornbeck — Mon, 13 Feb 2012 18:31:32 GMT

Just a quick FYI that we recently released Hotfix Package 5 for Microsoft Application Virtualization 4.6 SP1 dated December 2011. I don’t think I mentioned this one before so if you haven’t seen it you’ll want to check it out:

=====

This article describes a hotfix package that contains the latest fixes for Microsoft Application Virtualization (App-V) 4.6 Service Pack 1 (SP1). This hotfix package is dated December 2011.

This hotfix package addresses the following issues:

- Assume that you have a virtualized application that is managed by System Center Configuration Manager or by Asset Intelligence. If you run this application by using the System account, the SoftGrid Client folder is moved into the system profile. However, this behavior causes the loss of user settings or of nested SoftGrid Client folders. To resolve this issue, you must create the following registry entry after you apply this hotfix package:

Location: HKEY_LOCAL_MACHINE\Software\Microsoft\Softgrid\4.5\Client\Configuration
Entry: ExpandUserDataDirectoryAsUser
Type: REG_DWORD
Value: 1

- The Application Virtualization client does not start a virtualized application even if the application package is fully loaded in the App-V cache. When this issue occurs, you receive the following error message:

The system cannot find the path specified

If you are not assigned administrative permissions, HTTPS streaming fails when mutual certificate authentication is applied between the client and the server.

Note We recommend that you test hotfixes before you deploy them in a production environment. Because these builds are cumulative, each new hotfix release contains all hotfixes that were included with the previous hotfix package. We recommend that you apply the most recent hotfix release that contains the hotfixes that you want.

For all the details and a download link please see the following:

2645225 : Hotfix Package 5 for Microsoft Application Virtualization 4.6 SP1: December 2011 (http://support.microsoft.com/kb/2645225)

J.C. Hornbeck | System Center & Security Knowledge Engineer

Get the latest System Center news on Facebook and Twitter:

The Forefront Server Protection blog: http://blogs.technet.com/b/fss/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/

Fix: Error Code 0000C800 is generated when connecting to the App-V Management Console

J.C. Hornbeck — Mon, 16 Jan 2012 18:54:39 GMT

Here’s a new KB article we published today. This one tells you how to fix an issue where error code 0000C800 is generated when connecting to the App-V Management Console:

=====

Symptoms

When connecting to the Microsoft Application Virtualization (App-V or SoftGrid) Management Web Service from the App-V Management Console, you receive the following error message:

Unexpected error occurred.
Please report the following error code to your system administrator.
Error code: 0000C800

Cause

This can occur if TCP/IP is disabled in SQL Server Configuration Manager under SQL Server Network Configuration on the App-V Database SQL Server.

Resolution

On the SQL Server where the App-V Database resides, launch SQL Server Configuration Manager, navigate and expand the SQL Server Network Configuration node and enable the TCP/IP protocol on the SQL instance that hosts the App-V Database.

Example:

On a default install of SQL there will be a Protocols for MSSQLSERVER listed under SQL Server Network Configuration. Highlight Protocols for MSSQLSERVER, right click on TCP/IP in the right hand pane and choose Enable from the Context Menu.

More Information

Other articles related to this specific App-V SQL Server connectivity error are below:

930565 Error message when you connect to the App-V (SoftGrid) Management Web Service from the App-V (SoftGrid) Management Console: "Error code: 0000C800" - http://support.microsoft.com/default.aspx?scid=kb;EN-US;930565

SoftGrid Management Console Intermittently Crashes With 0000C800 or 0000C81D Errors - http://blogs.technet.com/b/appv/archive/2007/09/13/softgrid-management-console-intermittently-crashes-with-0000c800-or-0000c81d-errors.aspx

App-V 4.5 Remote Console Configuration Guide - http://blogs.technet.com/b/appv/archive/2009/04/21/app-v-4-5-remote-console-configuration-guide.aspx

=====

For the most current version of this article please see the following:

2663873: Error Code 0000C800 is generated when connecting to the App-V Management Console

J.C. Hornbeck | System Center Knowledge Engineer

Get the latest System Center news on Facebook and Twitter:

Launching an App-V virtualized application on a Remote Desktop Web Access server launches the wrong virtualized application

J.C. Hornbeck — Mon, 28 Nov 2011 22:19:28 GMT

Here’s another KB article we published today. This one tells you how to fix an issue where trying to launch a virtualized application on a Remote Desktop Web Access server ends up launching a different one:

=====

Symptoms

When users login to a Remote Desktop Session Host server using a Remote Desktop Connection, all of the Microsoft Application Virtualization (App-V) applications work properly, however when users launch the same App-V applications on a Remote Desktop Web Access server the wrong virtualized app is launched. For example, the users receive App-V application B when App-V application A is selected even though the icon and the application names are displayed correctly.

Cause

When the RemoteApps are configured using the RemoteApp configuration wizard, an Alias parameter is configured automatically. Since sfttray.exe is the application for all App-V virtualized apps, once the 2nd App-V application is added, the Alias parameter cannot be same name as another application therefore the Wizard increments the file name with a (1), (2) etc. An example of this is below:

You will notice that the Alias is different for each one of the applications on each server. For example, the Alias for App1 on Server 1 is Sfttray, on Server 2 it is Sfttray1, and on Server 3 it is Sftray3. This is the source of the problem as the Aliases need to be identical for each application on each server.

Resolution

To resolve this issue, edit the RemoteApp parameters for the App-V application so that the Alias parameters are the same for each application across all Remote Desktop Session Host servers. It is recommended that the application name referenced after the /launch switch of the sfttray command be used for the Alias.

Example where the App-V launch commands are:

App1 -sfttray.exe /launch "App1 1.1.1.1"
App2 -sfttray.exe /launch "App2 1.1.1.1"
App3 -sfttray.exe /launch "App3 1.1.1.1"
App4 -sfttray.exe /launch "App4 1.1.1.1"

Change the App1,2,3,4 RemoteApp configurations as follows:

Make this change on all Remote Desktop Session Host servers.

More Information

The most common scenario in which this can happen is when you have multiple Remote Desktop Session Host servers and Remote Desktop Web Access servers that are load balanced. When the App-V applications are manually installed on each Remote Desktop Session Host server, they may or may not have not been installed in exactly the same order. Also, the Applications configured in the RemoteApp Program wizard may or may not have not been configured in exactly the same order on the 3 Remote Desktop Session Host servers, thus the Alias names may not be in sync and in the same order on each server.

Application Virtualization 4.6 for Windows Server 2008 R2 Remote Desktop Services - whitepaper -
http://blogs.technet.com/b/appv/archive/2010/05/27/the-app-v-4-6-for-rds-whitepaper-is-now-available.aspx

=====

For the most current version of this article please see the following:

2638538: Launching an App-V virtualized application on a Remote Desktop Web Access server launches the wrong virtualized application

J.C. Hornbeck | System Center Knowledge Engineer

App-V database jobs fail with error - “Executed as user dbo. The server principal “sa” is not able to access the database under the current security context. [SQL State 08004] error 916”.

J.C. Hornbeck — Thu, 17 Nov 2011 14:44:46 GMT

Here’s one more KB article we just published today. This one talks about an issue where App-V database jobs fail if you have the wrong DB selected I the SQL Server Jobs configuration:

=====

Symptoms

The App-V Management Server installation creates database jobs in the SQL jobs section. When one of the database jobs is executed, the job fails with the error message:
“Executed as user dbo. The server principal “sa” is not able to access the database under the current security context. [SQL State 08004] error 916”.

Cause

The correct database is not selected in the SQL Server jobs configuration.

Resolution

1. Open SQL Management Studio.
2. Navigate to the SQL Server Agent\Jobs node in Object Explorer.
3. Open “Properties” for the Job.
4. Select the Page for “Steps” in the left pane.
5. Select “Edit” and change the database name to the App-V Database being used. (e.g. APPVIRT).

=====

For the most current version of this article please see the following:

2597203: App-V database jobs fail with error - “Executed as user dbo. The server principal “sa” is not able to access the database under the current security context. [SQL State 08004] error 916”.

J.C. Hornbeck | System Center Knowledge Engineer

Error Codes XXXXXX2A-00000003 or XXXXXX0A-0000000A when attempting to stream an application from a Microsoft Application Virtualization Management Server

J.C. Hornbeck — Wed, 16 Nov 2011 19:00:39 GMT

Here’s another good KB article we just published today. This one talks about an issue where you get a 00000003 or 0000000A error when trying to launch a virtualized application from an App-V client:

=====

Symptoms

You receive the following error when trying to launch or stream an application using the App-V client:

The Application Virtualization Client could not Launch <APPLICATION NAME>
The System Cannot Find the File Specified
Error Code: XXXXXX-XXXXXX2A-00000003

You may also see the following error:

Unexpected Error
Error Code: XXXXXX-XXXXXX0A-0000000A

Cause

This can easily happen if you use the wrong convention for specifying a UNC path as an HREF for the SFT file in the application’s OSD file.

Resolution

If you use the traditional format and not the proper HREF format for specifying a UNC path, the App-V client will error out. You will need to specify the FILE:// HREF prefix in front of the UNC path. For example, if the SFT file located in \\server\share\directory\application.sft path, you will need to specify the format as follows:

FILE://\\server\share\directory\application.sft

More Information

Please note: Specifying a UNC path using the traditional format (\\server\sharename\directory) for the ASR (ApplicationSourceRoot) OSR (OSDSourceRoot) and ISR (IconSourceRoot) is required for those three values per the documentation here:

http://technet.microsoft.com/en-us/library/cc843817.aspx

=====

For the most current version of this article please see the following:

2641546: Error Codes XXXXXX2A-00000003 or XXXXXX0A-0000000A when attempting to stream an application from a Microsoft Application Virtualization Management Server

J.C. Hornbeck | System Center Knowledge Engineer

Error when loading the Application Virtualization Client Management snap-in on a Windows Server computer running the App-V Client for Remote Desktop Services

J.C. Hornbeck — Wed, 09 Nov 2011 16:16:33 GMT

Here’s another good KB article we just published. This one talks about an issue that may occur if you attempt to maintain multiple connections to the App-V client through the client administrative snap-in/console under the same administrative account when accessed from multiple RDP sessions:

=====

Symptoms

When you open the Application Virtualization (App-V) Client Management snap-in on a Windows Server Computer running the App-V Client for Remote Desktop Services, you get the following error:

MMC could not create the snap-in.
MMC could not create the snap-in. The snap-in might not have installed correctly.
Name: Application Virtualization Client

Cause

This may happen if you attempt to maintain multiple connections to the App-V client through the client administrative snap-in/console under the same administrative account when accessed from multiple RDP sessions.

You can have one console connection alongside a single RDP connection – even under the same user account. The issue only arises when you are attempting a second instance of the MMC snap-in from a second RDP session under the same user account.

Resolution

This issue is known and considered by design.

=====

For the most current version of this article please see the following:

2641268: Error when loading the Application Virtualization Client Management snap-in on a Windows Server computer running the App-V Client for Remote Desktop Services

J.C. Hornbeck | System Center Knowledge Engineer

Error 268480357 starting an App-V Management Server with dynamic SQL ports

J.C. Hornbeck — Wed, 26 Oct 2011 15:34:43 GMT

Here’s another good KB article we published today. If you’re seeing error 268480357 on your App-V server then you’ll want to check this one out.

=====

Symptoms

The Application Virtualization Management Server service may fail to start on a Microsoft Application Virtualization 4.5 (App-V 4.5) server with the following error:

---------------------------
Services
---------------------------
Windows could not start the Application Virtualization Management Server on Local Computer. For more information, review the System Event Log. If this is a non-Microsoft service, contact the service vendor, and refer to service-specific error code 268480357.
---------------------------
OK
---------------------------

A corresponding event will be recorded in the System Event Log:

Log Name: System
Source: Service Control Manager
Event ID: 7024
Task Category: None
Level: Error
Keywords: Classic
Description:
The Application Virtualization Management Server service terminated with service-specific error %%268480357.

The Sft-server.log will show entries similar to the following:

[2011-10-18 14:48:33.578] APPVSRV 3020 1512 SW_SQLDataConnection::Open - - - - 2 41494 "Failed to establish a connection to the data source: (Server: sql01\appvirt, Database: APPVIRT).
"
[2011-10-18 14:48:33.578] APPVSRV 3020 1512 SW_SystemDispatcher::init - - - - 1 44901 "System dispatcher initialization error [-1]. System dispatcher startup will stop.
"
[2011-10-18 14:48:33.578] APPVSRV 3020 1512 SW_SystemDispatcher::fini - - - - 0 44952 "Successfully shut down Microsoft System Center Application Virtualization Management Server Version 4.5.2.17140 (3020)
"

Cause

This error may occur if the App-V Management Server was installed to a named SQL instance that is configured to use dynamic ports. If the Application Virtualization Management Server service is unable to connect to this database at startup, the 268480357 error will be generated. This can occur if either A) the port was hard-coded during setup and the port number has changed or B) if the SPN is not correctly registered for the service.

There are 2 registry keys under HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\SoftGrid\4.5\Server that control which SQL instance the server connects to: SQLServerName and SQLServerPort. SQLServerName will be either the server name or server_name\instance_name, depending on what was chosen during installation. If SQLServerPort is set to 0, App-V queries the SPN of the SQL server instance to determine the port number to connect to. If a port was manually entered during setup, SQLServerPort will be hard-coded to use that port number. In the event that the port number of the SQL instances changes, App-V will not be able to connect to the SQL server.

Resolution

To resolve this issue and allow the App-V Management Server service to start, use either of the following methods:

Method 1 - Use static ports

Record the value of HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\SoftGrid\4.5\Server\SQLServerPort (
Log on to the SQL server and open the SQL Server Configuration Manager
Navigate to SQL Server Network Configuration\Protocols for <SQL_instance_name> (where <SQL_instance_name> is your App-V SQL instance). Double-click on TCP/IP and then click on the IP Addresses tab
For each IP address, remove any value listed for TCP Dynamic Ports. Change TCP Port to the number you recorded in step 1. Repeat for all IP addresses.
Restart the SQL server instance's service (for example, SQL Server (APPV)).
Start the Application Virtualization Management Server service

Method 2 - Continue using dynamic port assignment

Verify that the SPNs for the SQL server instance is correctly configured using the steps outlined in this article: http://blogs.technet.com/b/appv/archive/2009/04/21/app-v-4-5-remote-console-configuration-guide.aspx
Open Regedit and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\SoftGrid\4.5\Server. Edit SQLServerPort to change the value to 0. Verify that SQLServerName reflects the instanace name of your SQL server instance in the format <ServerName>\<InstanceName> (for example, SQLServer01\AppV).
Double-click C:\Program Files (x86)\Microsoft System Center App Virt Management Server\App Virt Management Service\SftMgmt.udl and change the instance name to match the value entered in step 2.
Start the Application Virtualization Management Server service

More Information

The 268480357 error can indicate a general failure to connect. This article addresses the specific scenario of a dynamic port changing its value. Always verify basic connectivity, make sure services are started, firewall rules are in place, etc.

=====

For the most current version of this article please see the following:

2633835: Error 268480357 starting an App-V Management Server with dynamic SQL ports

J.C. Hornbeck | System Center Knowledge Engineer

A known good App-V virtual application package may fail with error 19-00001003 after adding a pre-launch script

J.C. Hornbeck — Thu, 20 Oct 2011 20:52:11 GMT

Here’s a great new KB article we published today. If you’re seeing errors after adding a pre-launch script to one of your App-V packages then you’ll want to check this one out:

=====

Symptoms

A known good Microsoft Application Virtualization (App-V) package may fail with the following error after adding a pre-launch script:
Application Virtualization Error

The Application Virtualization Client could not launch <Package Name>.

The Application Virtualization Client encountered a problem while waiting for the application to be ready to interact with the user. Report the following error code to your System Administrator.

Error code: 4505CD-1F702A19-00001003

Cause

This is typically caused by a timing issue between the App-V client and the Windows Message Pump due to the pre-launch script.

Resolution

To resolve this issue, change the <SUBSYSTEM VALUE="windows"/> XML tag in the .OSD file from windows to console. This change will need to be implemented in each OSD file in the package.

Example:

Change:

To:

If you are deploying packages using a Application Virtualization Server you will need to initiate a DC refresh on the App-V client to update the OSD cache. Once complete this issue should be resolved. If using Configuration Manager 2007 or an MSI package to deploy App-V applications, the package will need to be updated using the sequencer and redeployed.

=====

To continue reading this article please see the link below:

2628029: A known good App-V virtual application package may fail with error 19-00001003 after adding a pre-launch script

J.C. Hornbeck | System Center Knowledge Engineer

VAppCollector launches even if System Center Configuration Manager/App-V integration is not enabled

J.C. Hornbeck — Thu, 20 Oct 2011 13:52:40 GMT

Here’s a great new KB article we published today. This one talks about a potential issue you might see one your App-V/ConfigMgr 2007 clients. If you’re running these now or have plans to do so in the future you’ll probably want to give this one a read:

=====

Symptoms

The VAppCollector component of System Center Configuration Manager 2007 (ConfigMgr 2007) will be launched on a client even if ConfigMgr 2007/Microsoft Application Virtualization (App-V) integration is disabled. This can potentially generate multiple errors in the event log such as Event IDs 2012, 3008, 3210 and 5009.

Cause

This can occur if the Asset Intelligence component is enabled in System Center Configuration Manager 2007. Regardless of whether ConfigMgr 2007 is managing App-V clients or not, it will trigger the launch of VAppCollector. This is by design.

Resolution

There is no supported way to prevent VAppCollector from launching other than by disabling Asset Intelligence, although in most cases this is not a viable solution as it stops all licensing information for the System Center Configuration Manager site.

If you are unable to disable Asset Intelligence, the only other known workarounds are below:

1) Include the computer account as part of the App-V user group assigned in the App-V server. This will allow the system account to launch the applications and thus no errors will be reported in the application event log.

2) Use System Center Configuration Manager 2007 to deploy your virtual packages or to deploy your virtual applications using MSI.

3) Ignore the errors in the event logs as they will not affect the App-V operations.

4) Set the HKLM\software\Microsoft\Softgrid\4.5\Client\Configuration\RequireAuthorizationIfCached registry key to 0. Keep in mind that this affects security because any user can create a shortcut and launch the applications even when they are not authorized. Be sure you fully understand all the implications of this before modifying this registry key. See below definition of this key:

RequireAuthorizationIfCached

Indicates that authorization is always required, whether or not an application is already in cache. Possible values:

0=False: Always try to connect to the server. If a connection to the server cannot be established, the client still allows the user to launch an application that has previously been loaded into cache.

1=True (default): Application always must be authorized at startup. For RTSP streamed applications, the user authorization token is sent to the server for authorization. For file-based applications, file ACLs control whether a user may access the application.

Restart the sftlist service for the change to take effect. See http://technet.microsoft.com/en-us/library/dd464849.aspx for more details.

More Information

VAppCollector is a component developed by the System Center Configuration Manager team to collect information about virtual applications using the App-V client. Besides Asset Intelligence it is used to populate the information in the virtual applications reports in System Center Configuration Manager to gather errors, last launched, etc. It is also used to collect information for virtual applications for metering purposes. VAppCollector does not have its own log as do other components in System Center Configuration Manager 2007.

It is normal behavior to collect all this information during an Hardware inventory cycle and launch of each application. You can gather more information about Asset intelligence by looking at the following log:

Assetadvisor.log

You will see entries similar to these:

Executing "C:\Program Files\Microsoft Application Virtualization Client\sfttray.exe" /exe "C:\Windows\system32\CCM\VAppCollector.exe" /quiet /launch "Microsoft Office Document Cache" AssetAdvisor 8/4/2011 9:34:31 AM 236 (0x00EC)
Timed-out running "C:\Program Files\Microsoft Application Virtualization Client\sfttray.exe" /exe "C:\Windows\system32\CCM\VAppCollector.exe" /quiet /launch "Microsoft Office Document Cache" AssetAdvisor 8/4/2011 9:34:30 AM 236 (0x00EC)

If VAppCollector ran successfully you will see consecutive executing lines otherwise you will receive time-out entries among the executing lines.

Another way to determine if VAppCollector ran is to look into the sftlog.txt and find the lines that do not have usr values in them. Below is an example.

Launched by a user:

[08/04/2011 17:35:57:594 SWAP INF] {hap=C8:app=Microsoft Office Document Cache 14.0.4763.1000:tid=11C8:usr=administrator}
Elapsed time for launch: 6.219 seconds
[08/04/2011 17:36:18:958 SWAP INF] {hap=C8:app=Microsoft Office Document Cache 14.0.4763.1000:tid=11C8:usr=administrator}
App shut down

Launched by VAppCollector (note the lack of a "usr=" entry in the log lines):

[08/04/2011 17:30:21:501 SWAP INF] {hap=C3:app=Microsoft Office Document Cache 14.0.4763.1000:tid=1300}
Elapsed time for launch: 3.422 seconds

[08/04/2011 17:30:29:986 SWAP INF] {hap=C3:app=Microsoft Office Document Cache 14.0.4763.1000:tid=1300}
App shut down

Although VAppCollector will run on clients that have received applications through App-V server, the virtual applications reports in System Center Configuration Manager will not populate as there are no virtual packages to correlate the data. Asset Intelligence reports will have information about virtual packages but due to the lack of permissions to launch the virtual applications it cannot collect information such as software company, version, etc. These columns will show as unidentified or unknown on these reports.

Other things to consider:

Any prelaunch scripts that are set in the OSD files of these virtual applications will be launched during the hardware inventory cycle. If for example you are using a prelaunch script to map a drive, there will be an attempt to map the drive using the system account and if the computer doesn't have rights to map the drive it will show as disconnected. To work around this issue and similar issues consider the use of Post shutdown scripts to gracefully disconnect drives and terminate any instance that is triggered during the prelaunch phase.

=====

To continue reading this article please see the link below:

2590590: VAppCollector launches even if System Center Configuration Manager/App-V integration is not enabled

J.C. Hornbeck | System Center Knowledge Engineer

Prescriptive Guidance for Sequencing Office 2010 in App-V 4.6 SP1

J.C. Hornbeck — Mon, 17 Oct 2011 14:08:00 GMT

Here’s a great new guide we published on how to sequence Office 2010 using Microsoft Application Virtualization 4.6 SP1. I didn’t want to post the article in it’s entirety here but there’s a brief intro below as well as a link to the KB itself at the bottom. And don't forget - we also have the App-V Package Accelerator for Microsoft Office Professional Plus 2010 available here:

http://gallery.technet.microsoft.com/App-V-Package-Accelerator-62415d39

=====

Summary

Virtualizing Microsoft Office 2010 using Microsoft Application Virtualization (App-V) is a common task in many App-V environments. This document describes a well-defined series of steps designed to aid customers in successfully sequencing Microsoft Office 2010.

This document guides you through the process of sequencing Office 2010 using the App-V 4.6 SP1 sequencer. If you are using the App-V 4.6 sequencer (i.e App-V 4.6 with no service pack), please follow this document instead: Prescriptive guidance for sequencing Office 2010 in Microsoft App-V.

IMPORTANT: Before starting to sequence, we strongly suggest to read this guide completely in order to understand the configuration options available.

Prerequisites

You will need the following software to use this guide:

Microsoft Application Virtualization version 4.6 SP1: The App-V 4.6 SP1 Sequencer is installed on the Sequencing workstation. It is recommended to apply the latest App-V updates as well.
Microsoft Office 2010 volume SKU (32-bit). Only the 32-bit version of Office 2010 is supported. This may be deployed to either 32 or 64-bit operating systems. We recommend sequencing on the same operating system as that of the operating system to which you will deploy the package.
Microsoft Office 2010 Deployment Kit for App-V: The Deployment Kit installs the Office 2010 licensing service and optionally installs proxies to enable integration features.

Introduction

The Microsoft Office 2010 Deployment Kit for App-V is a required component to sequence and deploy Microsoft Office 2010. The deployment kit provides two main functions:

Installation and configuration of the Office Software Protection Platform service.
Optional configuration of virtualized components to allow for seamless interaction with the operating system.

The Deployment Kit is first installed on the sequencing workstation. The Deployment Kit must also be installed on all App-V clients where your Office 2010 package will be deployed…..

=====

To continue reading this article please see the link below:

2627274: Prescriptive Guidance for Sequencing Office 2010 in App-V 4.6 SP1

J.C. Hornbeck | System Center Knowledge Engineer

A VDI solution deployed using the Application Virtualization 4.6 SP1 client appears slow to login

J.C. Hornbeck — Wed, 12 Oct 2011 22:47:00 GMT

Here’s another new KB article we published today. This one talks about some of the causes and solutions to an issue where a VDI solution deployed using the App-V 4.6 SP1 client appears slow to login:

=====

Symptoms

Consider the following scenario:

1. A VDI solution is deployed using the Microsoft Application Virtualization (App-V) 4.6 Service Pack 1 client with the latest updates.
2. The solution is using Read-only Cache and is part of a branch office scenario with a local Streaming server and a home office Virtual Management Server.
In this scenario, logins for users can take between 60 and 120 seconds depending on the branch office location of the VDI servers. If the App-V client is disabled you may notice that the client login time is reduced to as short as 20 seconds although times may vary depending on the unique environment.

Cause

This can occur due to one or both of the following:

1. AutoLoadTriggers and AutoLoadTarget are enabled (default).
2. The App-V package icons and OSD file assets are being copied over the network and depending on how the solution is engineered, these assets could be copied over a slow WAN connection from the home office.

Resolution

To work around this issue, complete the following steps:

1. Set AutoLoadTriggers and AutoLoadTarget registry values on the App-V client computer to a value of 0. AutoLoadTriggers and AutoLoadTarget are stored in the following registry locations:

HKLM\SOFTWARE\Microsoft\SoftGrid\Client\CurrentVersion\Configuration\AutoLoadTriggers (REG_DWORD)
0 = Never
1 = OnLaunch
2 = OnRefresh
4 = OnLogin
5 = On Launch & Login (DEFAULT)

HKLM\SOFTWARE\Microsoft\SoftGrid\Client\CurrentVersion\Configuration\AutoLoadTarget (REG_DWORD)
0 = None
1 = PreviouslyUsed (Default)
2 = All

Note These can also be adjusted directly, however it will require a restart of the App-V client to take effect.

Should this issue continue to take place then proceed to step 2:

2. Create an OS start-up script to copy the icon and OSD files to a local folder on the VDI server and configure the OSDSourceRoot and IconSourceRoot App-V client registry values to point to this local folder. Please see the TechNet reference below for more information regarding these registry values. In the scenario above this reduced the login time to as little as 30 seconds although individual results may vary.

Example

1. Create a directory on the local drive called sr (c:\sr)
2. From an elevated command prompt execute the following commands:

Xcopy /S /Y \\server\content\*.ico c:\sr
Xcopy /S /Y \\server\content\*.osd c:\sr

3. Change the IconSourceRoot and OSDSourceRoot values in the registry to c:\sr

App-V Client Registry Values : http://technet.microsoft.com/en-us/library/dd464849.aspx

More Information

If using DFS to replicate an App-V content share across remote sites, be sure not to disable the IPv6 protocol in the Network Properties of clients and servers involved. This breaks the DFS referral process. If the IPv6 protocol is disabled, remote clients could unintentionally access content on DFS shares across WAN connections.

For information on how the IPv6 protocol is used in the DFS referral process, see the blog article below:

http://blogs.technet.com/b/askds/archive/2009/10/28/dfs-referrals-and-ipv6-outta-site.aspx

=====

For the most current version of this article please see the following:

2626771: A VDI solution deployed using the Application Virtualization 4.6 SP1 client appears slow to login

J.C. Hornbeck | System Center Knowledge Engineer

Applications fail to launch with error 04-00000A04 after App-V 4.6 SP1 upgrade

J.C. Hornbeck — Mon, 03 Oct 2011 18:26:21 GMT

Just a quick heads up on a new KB article we published today:

=====

Symptom

After upgrading a Microsoft Application Virtualization (App-V) 4.6 client to App-V 4.6 Service Pack 1 (SP1), applications may fail to launch with the following error:

The Application Virtualization Client could not launch the application you requested.

An unexpected error occurred. Report the following error code to your

System Administrator.Error code 461758B-0F801904-00000A04

The SFTLog.txt may also have entries similar to the following:

[09/22/2011 13:11:42:814 TRAY ERR] {tid=101:usr=administrator}
The Application Virtualization Client could not launch the application you requested.

An unexpected error occurred. Report the following error code to your System Administrator.

Error code: 461758B-0F801904-00000A04

Cause

This may happen if the DDELaunchMSICommand or LaunchMSICommand registry values under the following keys are incorrect:

For 32-bit systems: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SoftGrid\4.5\Client\UserInterface

For 64-bit systems: HKEY_LOCAL_MACHINE\SOFTWARE\wow64node\Microsoft\SoftGrid\4.5\Client\UserInterface

Resolution

To resolve this issue, edit the registry key to reflect the correct execution string.

For 32-bit clients, edit HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SoftGrid\4.5\Client\UserInterface. For 64-bit clients, use HKEY_LOCAL_MACHINE\SOFTWARE\wow64node\Microsoft\SoftGrid\4.5\Client\UserInterface.

Note that Configuration Manager clients use a different string than App-V clients. If in doubt, check the value of DDELaunchCommand. If it references VappLauncher.exe, Configuration Manager integration is enabled. If it references sfttray.exe, the client is an App-V VAS client.

The correct values are:

Configuration Manager 2007 clients with virtualization support enabled:

Value: DDELaunchMSICommand

Type: REG_SZ

Data: @GcbJDuU`8Dt4ql_+RSRVirtualApp>=T+i$+PP-9,9v}Si8@4X /launch "<APP>"

Value: LaunchMSICommand

Type: REG_SZ

Data: @GcbJDuU`8Dt4ql_+RSRVirtualApp>=T+i$+PP-9,9v}Si8@4X /launch "<APP>"

App-V VAS clients:

Value: DDELaunchMSICommand

Type: REG_SZ

Data: 3OqYobt01?4VH[gf8qiBRelease_Merge_Modules>OO5hSGuIH?xoVn&wQ(Ex "<APP>" <DDE>

Value: LaunchMSICommand

Type: REG_SZ

Data: 3OqYobt01?4VH[gf8qiBRelease_Windows_Desktops>gNkKPt-'NA05f@sdSnKH /launch "<APP>"

More Information

This is a .reg file exported from an ConfigMgr client:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\SoftGrid\4.5\Client\UserInterface]
"AppIcon"="C:\\Program Files (x86)\\Microsoft Application Virtualization Client\\sftcmcres.dll,-484"
"TypeIcon"="C:\\Program Files (x86)\\Microsoft Application Virtualization Client\\sftcmcres.dll,-483"
"DDELaunchMSICommand"="@GcbJDuU`8Dt4ql_+RSRVirtualApp>=T+i$+PP-9,9v}Si8@4X /launch \"<APP>\""
"DDELaunchCommand"="\"C:\\Windows\\CCM\\VappLauncher.exe\" /launch \"<APP>\""
"LaunchCommand"="\"C:\\Windows\\CCM\\VappLauncher.exe\" /launch \"<APP>\""
"LaunchMSICommand"="@GcbJDuU`8Dt4ql_+RSRVirtualApp>=T+i$+PP-9,9v}Si8@4X /launch \"<APP>\""

This is a .reg file exported from a 32-bit 4.6 SP1 VAS client:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SoftGrid\4.5\Client\UserInterface]

"AppIcon"="C:\\Program Files\\Microsoft Application Virtualization Client\\sftcmcres.dll,-484"

"TypeIcon"="C:\\Program Files\\Microsoft Application Virtualization Client\\sftcmcres.dll,-483"

"DDELaunchMSICommand"="3OqYobt01?4VH[gf8qiBRelease_Merge_Modules>OO5hSGuIH?xoVn&wQ(Ex \"<APP>\" <DDE>"

"DDELaunchCommand"="\"C:\\Program Files\\Microsoft Application Virtualization Client\\sftdde.exe\" \"<APP>\" <DDE>"

"LaunchCommand"="\"C:\\Program Files\\Microsoft Application Virtualization Client\\sfttray.exe\" /launch \"<APP>\""

"LaunchMSICommand"="3OqYobt01?4VH[gf8qiBRelease_Windows_Desktops>gNkKPt-'NA05f@sdSnKH /launch \"<APP>\""

Note the difference in syntax due to the escape characters. Note also that the paths to various executables may be different in your environment.

=====

For the most current version of this article please see the following:

2622617: Applications fail to launch with error 04-00000A04 after App-V 4.6 SP1 upgrade

J.C. Hornbeck | System Center Knowledge Engineer

Microsoft Compiled HTML Help files (*.CHM) accessed within App-V packages fail to display correctly after Internet Explorer 8 is upgraded to Internet Explorer 9

J.C. Hornbeck — Tue, 27 Sep 2011 18:27:31 GMT

Here’s one more KB article we published today. Enjoy!

=====

Symptoms

On a Windows Server 2008 R2 RDS server running the App-V Client version 4.6.0.20200, after Internet Explorer 8 is upgraded to Internet Explorer 9, the Microsoft Compiled HTML Help files (*.chm) in some App-V packages may stop working and the help panel will display a blank white screen. If Internet Explorer 9 is uninstalled and reverted back to Internet Explorer 8 the help content will render properly.

Cause

This is a known issue with App-V client 4.6.0.20200.

Resolution

To resolve this issue, install App-V 4.6 SP1 with the latest hotfix rollup. To obtain the latest hotfix rollup please contact Microsoft Support.
Service Pack 1 for Microsoft App-V 4.6 can be downloaded from the following location:

Microsoft Application Virtualization 4.6 Service Pack 1 - http://www.microsoft.com/download/en/details.aspx?id=14552

More Information

The latest Version of the App-V 4.6 client is 4.6 SP1 Hotfix Rollup 4 (as of 9/19/2011). To keep track of the latest App-V updates, please follow the Microsoft Application Virtualization blog at http://blogs.technet.com/b/appv/.

Note Be sure to test these updates against all your App-V packages to insure compatibility in your test environment prior to updating your production environment.

=====

For the most current version of this article please see the following:

2619927: Microsoft Compiled HTML Help files (*.CHM) accessed within App-V packages fail to display correctly after Internet Explorer 8 is upgraded to Internet Explorer 9

J.C. Hornbeck | System Center Knowledge Engineer

Considerations when Updating an App-V Read-only (Shared) Cache

J.C. Hornbeck — Tue, 27 Sep 2011 15:06:03 GMT

Here’s another KB article we published today. It’s a regular fountain of new content!

=====

Summary

The concept of a shared, or read-only cache was introduced in version 4.6 of the Microsoft Application Virtualization client. When using App-V in a Shared Cache environment, it is recommended to use a UNC path to a symbolic link (see http://technet.microsoft.com/en-us/library/ee956915.aspx for more information).

That way, when you change or adjust the shared/read-only cache, you do not have to change the FileName registry value in all of the client’s registries or the master VDI image. There is a possibility that random startup failures may exist for some App-V clients on VDI virtual machines during a App-V FSD (file system device) upgrade or modification (e.g. when applications are being provisioned and added to the read-only cache). This is caused by the App-V client attempting to start during the window where the symbolic link is being updated (a process that involves removal and re-adding the link to initiate the new location). During this window the App-V client engine find that the FSD does not exist and the client will fail to start. You will see the following error in the Windows System Event Log.

Could not start the Application Virtualization Client service on Local Computer.
Error 1068: The dependency service or group failed to start.

In addition, additional dependency errors calling out “sftfs” specifically will also be referenced.

Also note that this is only a problem during the App-V client startup. Restarting the AppV client a few minutes after initial failure will resolve the issue. If the issue persists, there is likely a problem with accessing the shared cache access.

=====

For the most current version of this article please see the following:

2618921: Considerations when Updating an App-V Read-only (Shared) Cache

J.C. Hornbeck | System Center Knowledge Engineer

New KB: Common dialogs fail to open in applications sequenced with Microsoft App-V

J.C. Hornbeck — Mon, 12 Sep 2011 15:42:03 GMT

Here’s a new App-V Knowledge Base article we published this morning. If you’re seeing an issue where dialog boxes fail to open with a virtualized app then you’ll want to check this one out:

=====

Symptoms

Common dialogs such as File \ Open, Save, or Save-As... fail to open in applications sequenced in App-V 4.5 or 4.6. No errors are reported, but clicking on the menu appears to have no effect.

Cause

This is caused if Entrust Group Share (Entrust Entelligence Group Share for Windows Folders 2.30) is installed on a client that is also running App-V 4.6 SP1. Previous versions of App-V do not exhibit this behavior.

Resolution

This behavior is resolved in Microsoft Application Virtualization (App-V) 4.6 SP1 Hotfix 4 (HF04). You can request this update by contacting Microsoft Support.

As a workaround, you can edit the OSD for affected applications to set the SXS_32_ENABLED tag to true. This has the side-effect of bypassing side-by-side assemblies located in the package itself and using only locally installed binaries. This may result in missing files unless the assemblies are installed on the client computer.

To change this setting, open the OSD file for the application and modify the policies section to include the SXS_32_ENABLED tag set to true (the default value is false). This should generally be avoided, as it necessitates that all side-by-side assemblies be installed locally on the machine. For example:

<POLICIES>
<LOCAL_INTERACTION_ALLOWED>FALSE</LOCAL_INTERACTION_ALLOWED>
<SXS_32_ENABLED>TRUE</SXS_32_ENABLED>
</POLICIES>

More Information

A Procmon will reveal entries like this where the volume name is prepended twice to the path:

4:05:26.2364763 PM notepad.exe 3264 CreateFile \Device\eedmk{3378b50c-cda0-11e0-b722-806e6f6e6963}\Device\eedmk{3378b50c-cda0-11e0-b722-806e6f6e6963}\Windows\System32\uxtheme.dll SUCCESS Desired Access: Generic Read, Disposition: Open, Options: Synchronous IO Non-Alert, Non-Directory File, Attributes: n/a, ShareMode: Read, Delete, AllocationSize: n/a, OpenResult: Opened

Other, generic errors may also be seen as a result of trying to locate Side-By-Side assemblies (SxS assemblies) in the wrong path. For example, Notepad will fail on file\open... with:
: Not enough memory available to complete this operation. Quit one or more applications to increase available memory, and then try again.

The presence of the 'double path' is diagnostic.

=====

For the most current version of this article please see the following:

2591554: Common dialogs fail to open in applications sequenced with Microsoft App-V

J.C. Hornbeck | System Center Knowledge Engineer