Microsoft Application Virtualization 4.5 Service Pack 1 (App-V 4.5 SP1) is now available. This service pack provides the latest updates to Microsoft Application Virtualization 4.5. Additionally, it contains the following improvements:
Support for Windows 7 and Windows Server 2008 R2
App-V 4.5 SP1 provides support for Windows 7 and Windows Server 2008 R2. This includes support for Windows 7 taskbar, for AppLocker, for BranchCache, and for BitLockerToGo. Windows Server 2008 R2 is supported for only the Application Virtualization Server.
Support for third-party Kerberos realms
App-V 4.5 SP1 provides support for environments that have a trust relationship and mapped user accounts between a Windows Domain and an MIT Kerberos realm. For more information about how to enable this support, visit the following Microsoft TechNet Web site:
http://go.microsoft.com/fwlink/?LinkId=166004
Improved support for application publishing and streaming over the HTTP and HTTPS protocols
App-V 4.5 SP1 provides support for application publishing and streaming over the HTTP and HTTPS protocols for the following operating system editions:
- Windows XP Home Edition
- Windows Vista Home Basic
- Windows Vista Home Premium
- Windows 7 Home Basic
- Windows 7 Home Premium
Customer feedback and hotfix rollup
App-V 4.5 SP1 also includes a rollup of fixes to address issues that have been found since the App-V 4.5 Cumulative Update 1 release. This rollup addresses known issues and feedback from partners and customers who are using App-V 4.5.
In addition to some stability improvements, this service pack addresses the following issues:
- When a virtual application tries to delete a file on drive C, a "file not found" error occurs even though the file is deleted successfully.
- When you create an MSI package by using the App-V Sequencer, third-party tools may be unable to validate the resulting MSI package.
This service pack also includes a hotfix that was previously released. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
973873 Hotfix Package 5 for Microsoft Application Virtualization 4.5 Cumulative Update 1: August 2009
-----
For all the details see KB976338 - Description of Microsoft Application Virtualization 4.5 Service Pack 1
Enjoy!
J.C. Hornbeck | Manageability Knowledge Engineer
The following table lists the supported OS VALUE element options and the minimum supported client versions for Microsoft SoftGrid and Microsoft Application Virtualization. This element defines the required operating system. If there are more than one OS element in a particular IMPLEMENTATION tag, it is implied that the software package works with each. If none are present then it is assumed to run on all operating systems:
Steve Thomas | Senior Support Escalation Engineer
We are proud to announce the availability of the white paper “Application Virtualization 4.5 for Terminal Services.” This white paper discusses the benefits, configurations, and considerations when planning a Terminal Services (TS) solution with Microsoft Application Virtualization for TS (App-V for TS). Many customers want to find out the best way to configure and/or deploy App-V for TS on terminal servers. This paper includes topics ranging from choosing an App-V for TS application delivery method to configuring RemoteApp and App-V for TS to work together. We hope you find this document a valuable read if you are implementing App-V for TS.
You can download the white paper here.
If using a virtualized instance of Visual Studio (sequenced according to the instructions at http://technet.microsoft.com/en-us/appvirtualization/dd334515.aspx), when users build a C++ project in Visual Studio 2008 with debugging enabled the compiled program may not run and produce an error in the console window and/or the interface:
ERROR in Visual Studio Interface:
"Unable to start program 'path_to_program\program_name.exe'."
"This application has failed to start because the application configuration is incorrect. Review the manifest file for possible errors. Reinstalling the application may fix this problem. For more details, please see the application event log."
ERROR in console window:
"The system cannot execute the specified program."
This problem does not occur when the project is set to release mode.
This is caused by the debug run-time modules not being captured inside the virtual application package because of how the Application Virtualization side-by-side process works during sequencing. The debug runtimes are not used, so they are left out.
In order to work around this, the user needs to install the debug runtimes on the local machine. They can be built out of Visual Studio 2008 as follows:
1. From Visual Studio, navigate to "File" - "New" - "Project."
2. Select and expand "Other Project Types," then "Setup and Deployment."
3. In the Visual Studio Templates area, select "Setup Project." Click "OK."
4. In the Project window, Right-click "Setup1" and select "Add" - "Merge Module."
5. Select all debug runtimes desired from the list.
6. Click Open
7. Right-click Setup1 and select "Build."
8. Execute the project. It will install the modules you selected.
Hope this helps,
Steve Thomas | Senior Support Escalation Engineer
How can an integrated virtualization strategy that brings server, desktop, and application virtualization together provide significant benefits to your business? Join this webcast to learn about the Microsoft end-to-end virtualization strategy, which uses flexible solutions and common management tools to deliver unique value and savings. We discuss the new features of Windows Server 2008 R2 Hyper-V and Microsoft System Center Virtual Machine Manager 2008 R2. Other topics we cover include simplifying deployment and compatibility testing with Microsoft Application Virtualization (App-V) and delivering scalable desktop virtualization scenarios via Remote Desktop Services, Microsoft Enterprise Desktop Virtualization (MED-V), and Microsoft Virtual Desktop Infrastructure (VDI).
http://msevents.microsoft.com/CUI/WebCastEventDetails.aspx?EventID=1032426071&EventCategory=4&culture=en-US&CountryCode=US
J.C. Hornbeck | Manageability Knowledge Engineer
We just released the hotfix package for August 2009 that contains the latest hotfixes for Microsoft Application Virtualization 4.5 Cumulative Update 1. This hotfix package addresses the following issues:
- 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 attempts 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 fail to 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 refresh 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 refresh 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.
Note You can resolve this problem by creating a UseMITKerberos registry value.
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 (http://support.microsoft.com/kb/322756/ ) How to back up and restore the registry in Windows
- Start Registry Editor.
- Locate and then click the following key in the registry:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SoftGrid\4.5\Client\Network
- On the Edit menu, point to New, and then click DWORD Value.
- Type UseMITKerberos, and then press ENTER.
- On the Edit menu, click Modify.
- Type 1, and then click OK.
- Exit Registry Editor.
Important - Consider the following scenario. You add or remove a user from an Active Directory security group that is used to control access to an application. Then you enable this hotfix. In this scenario, Application Virtualization 4.5 does not correctly publish the application after a publishing refresh procedure. The user must log off and then log back on to see the changes.
- This hotfix does not support Application Virtualization 4.5 in environments that have a trust relationship and a mapped user account between a Windows domain and an MIT Kerberos realm. In some environments, this configuration may work if you install this hotfix. However, this configuration will not be supported in these environments until a future version of Application Virtualization 4.5 is released.
For all the details and to download the package see:
KB973873 - Hotfix Package 5 for Microsoft Application Virtualization 4.5 Cumulative Update 1: August 2009
J.C. Hornbeck | Manageability Knowledge Engineer
This recently came across one of our App-V email DLs here and since I didn’t see this documented anywhere I thought I’d go ahead and post it here. Below are the command line options that the 4.5 Management Server Installer accepts:
The following sample command line installs the Management Server using all the command line options mentioned above:
msiexec /i "setup.msi" /qn /l*vx %temp%\serverinstall.txt OPTIN="true" USERNAME="Krush" COMPANYNAME="MSFT" ADDLOCAL="Release_SoftGrid_Server,Release_AppVirt_Vss_Writer,Release_SoftGrid_Management_Console,Release_SoftGrid_Mgmt_Web_Service" DB_HOST="XRAYHWS" DB_SERVICE="APPVIRT3" DB_PORT="1433" SWICERTHASH="1A7E958464C90D8E8E492372538A83624600E276" SWISERVERRTSPPORT="322" SWIDOMAINNAME="sgl2k3.selfhost.corp.microsoft.com" SWIADMINGROUP="Domain Admins" SWIUSERGROUP="Domain Users" SWICONTENTDIR="c:\program files\Microsoft System Center App Virt Management Server\App Virt Management Server\content\" INSTALLDIR="C:\Program Files\Microsoft System Center App Virt Management Server\"
Hope this helps,
Krush Chavan | App-V Software Development Engineer
In case you missed it over on the MDOP blog, they just announced that Microsoft Desktop Optimization Pack (MDOP) 2009 R2 will be released in late October 2009 and will add Windows 7 support for all components except for MED-V. Server and management components will also support Windows 2008 R2. They go on to say:
“With its virtualization technologies and manageability components, MDOP 2009 R2 is an essential part of your Windows 7 planning and deployment strategy.
This is a great opportunity to highlight the key innovations of MDOP 2009 R2 and talk about how MDOP can help you rapidly migrate to Windows 7, deploy applications with greater ease, resolve application incompatibility, and reduce desktop management costs.
Optimize Windows 7 Application Deployment Using App-V
With Application Virtualization (App-V) you can transform applications into centrally-managed virtual services:
- Reduce the costs of application deployment and increase user productivity - deliver most applications without actually installing them. Updates are made easier, application conflicts are minimized, and IT can spend less time in regression testing. For users, once they are granted access, the application is delivered and available instantly, following the user to enable easy roaming between corporate PCs.
- Reduce your base image footprint and new PC provisioning time - separate your applications from the base image, and minimize the number of applications installed after the image is deployed.
Windows upgrade is the best time to adopt App-V - as part of Windows 7 deployment all applications are tested and re-deployed. This is a great time to take a look at your application delivery strategy and adopt Application Virtualization with minimum overhead and cost.
You can read more in the App-V Cost Reduction Study - savings of $156/PC/Yr in direct costs (11.6% of PC TCO) plus $125/PC/YR in user productivity gains. The sources of direct savings generated by App-V are across automated deployment, patching/updates, non-standard applications, image management, PC provisioning and replacement, and installation risk, as well as user productivity gains.
App-V 4.5 SP1 also offers new capabilities and unique integration with Windows 7:
- Maintain user productivity regardless of application format - integration with the Windows 7 UI maintains the user experience and productivity as virtual applications behave just as regularly installed applications. Users are able to pin applications to the taskbar and leverage jumplists to navigate between applications.
- Increased IT control with AppLocker integration - enforcing compliance of virtual applications with AppLocker policies, and providing consistent policy management for all application types.
- Make users productive anywhere and save on IT infrastructure using BranchCache - virtual applications traverse the WAN only once and are available to users faster through local BranchCache points, eliminating the need for an IIS Server in every branch.
- Secure application delivery with BitLocker ToGo - IT administrators can confidently deliver virtual applications on a secured USB drive, as the associated applications are protected against unauthorized use. Only authorized users have access to the applications, including remote users who may not have connectivity to corporate network.
- Integrate with third-party LDAP directories - reduce administrative overhead for customers who maintain their user accounts in a third-party LDAP directory, and enable Kerberos via Active Directory trust.
Once available, App-V 4.5 SP1 can be deployed immediately to production environments running XP, Vista, Windows7, and Windows Server 32-bit platforms. For customers preparing to run App-V on 64-bit Windows Client and Server platforms they can download App-V 4.6 Beta at Microsoft Connect. App-V 4.6 will be available in H1 2010…”
To read more about all the new features coming with MDOP 2009 R2 see http://blogs.technet.com/mdop/archive/2009/09/14/mdop-2009-r2-what-s-new-in-mdop-for-windows-7.aspx
J.C. Hornbeck | Manageability Knowledge Engineer
Based on the all the feedback we’ve heard from YOU, our customers, we’ve made some major changes to the Sequencer user interface in our 4.6 release which vastly improves the sequencing experience. Here are a few things that you will notice right away:
Welcome page : We now have a convenient page to get you started with your most commonly used tasks like package creation, edit and upgrade. After you create your packages, use the Edit option to make changes to the package like adding new OSs, creating MSIes, compressing package, etc. Upgrade option works well for applying security updates or upgrading the package. In 4.6, the Sequencer will automatically open the wizard to get you started with your upgrade!
Monitoring page redesigned : We have made the page more intuitive to use. The Sequencer will guide you through 3 steps of monitoring – Begin to start up the virtual environment, Install Application and Stop to collect as system changes. The progress bars represents waiting time as well as indicates that the Sequencer is alive while you install your application.
Window minimizing is gone : Based on studies, we found that most users were confused by the abrupt window minimizing during monitoring. Hence we have removed this feature.
Block size is gone : Through extensive testing, we found that 64kb blocks are most optimal for a variety of network bandwidths. Hence to have you make one less decision, we decided to make it simple set the block size to 64kb internally. You will not see the option to set the block size anymore.
You can find the Beta Sequencer at https://connect.microsoft.com/AppV46/Downloads
Happy sequencing!
Nidhi Doshi | App-V 4.6 Sequencer Program Manager
Microsoft Press offers complimentary book “Understanding Microsoft Virtualization Solutions“.
This guide will teach you about the benefits of the latest virtualization technologies and how to plan, implement, and manage virtual infrastructure solutions. The technologies covered include: Windows Server 2008 Hyper-V, System Center Virtual Machine Manager 2009, Microsoft Application Virtualization 4.5, Microsoft Enterprise Desktop Virtualization, and Microsoft Virtual Desktop Infrastructure.
Book content:
1) Microsoft’s Virtualization Solution
2) Server Virtualization – Hyper-V
3) Managing Virtualization – VMM 2008
4) Application Virtualization – App-V
5) Presentation Virtualization – Terminal Services
6) Desktop Virtualization – MED-V and VDI
7) User State Virtualization
8) Building a Virtualization Infrastructure
Copy is available on http://csna01.libredigital.com/?urmvs17u33
Enjoy!
J.C. Hornbeck | Manageability Knowledge Engineer
When sequencing an application, libraries/assemblies that are normally registered and stored in the \windows\winsxs folder are instead copied into the package, and are in the same folder as the executable that uses them . For some applications, when doing a package upgrade, this can cause your setup program to fail because it’s trying to update those assemblies at \windows\winsxs but they do not exist at that location in the package. If you receive an error message while doing a package upgrade related to Side by Side (WinSxS) you can first try removing HKLM\Components from the virtual registry and then performing the package upgrade. This has the effect of telling the TrustedInstaller service that the component does not exist in \windows\winsxs and it should attempt to reinstall it. Most of the time that will allow the package upgrade to now succeed.
Jason Hu | Microsoft App-V Software Development Engineer
The App-V 4.6 beta was just released on Monday and we are excited to have released the product we have been working on for the past few months to our customers. Throughout the week, we have received a number of questions about what is supported between 32-bit and 64-bit sequencing, along with running the sequenced applications on the 32-bit and 64-bit App-V client, so I wanted to address those questions and share more details with everyone here.
Our vision for App-V 4.6 is to allow you to keep all of your existing sequencing investments and be able to leverage 64-bit moving forward, in a simple and straight forward manner.
With that in mind, the following are some general guidelines about what is supported:
Existing packages:
All your pre-4.6 packages are valid and can continue to be used on the 4.6 client – just modify the OSD file to include the OS values for the 32 and/or 64-bit platform as target, as appropriate.
For new 32-bit applications to be run on the 4.6 client:
Sequence the 32-bit app on a 32-bit OS using the 4.6 sequencer. Specify x86 and x64 platforms as targets as appropriate for clients.
Note: App-V will not support running 32-bit applications on a 32-bit OS, if they were sequenced on a 64-bit OS sequencer machine.
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.
For new 64-bit applications to be run on the 4.6 client:
Sequence the 64-bit app on a 64-bit OS using the 4.6. sequencer. Specify x64 as the target platform.
We welcome you to try these out with our Beta Release (available on http://connect.microsoft.com). If you encounter any issues or have any comments, you can report it through the connect site and that will be directed straight to the App-V engineering team.
We are looking forward to your feedback and input on App-V 4.6.
Lidiane Souza | App-V Group Program Manager
As part of our ongoing efforts to continually improve Microsoft App-V, we recently released a hotfix package for July 2009 that contains the latest hotfixes for Microsoft Application Virtualization 4.5 Cumulative Update 1.
This hotfix package addresses the following issues:
- When you apply a disk quota to the profile directories of an user and when the disk quota is near the limit, the App-V client leaks paged pool memory.
- When run as a virtual application, a process that calls RegQueryMultipleValues experience unexpected errors or cannot start. For example, you receive error messages when you start or shutdown the Trapeze application and the application does not work correctly.
- When a App-V client tries to perform a publishing refresh procedure over HTTP or HTTPS, the procedureis not completed successfully. Specifically, the procedure is not completed successfully if a package contains pathnames that have Japanese characters. This problem occurs when the App-V client is running a Japanese version of Windows XP and has Internet Explorer 6 installed.
- When run as a virtual application, Microsoft Access 97 generates an error message 1008 when Access 97 is moving temporary files.
- When a Microsoft Application Virtualization 4.5 client tries to perform a publishing refresh 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.
- In environments that have a trust relationship and mapped user accounts between a Windows Domain and an MIT Kerberos realm, the Microsoft Application Virtualization 4.5 client cannot log on to a publishing server. Additionally, you receive an error message 8009030C.
For more information and details on obtaining the update see the link below:
KB973205 - Hotfix Package 4 for Microsoft Application Virtualization 4.5 Cumulative Update 1: July 2009
J.C. Hornbeck | Manageability Knowledge Engineer
Big news! The MDOP product team just announced the immediate availability of the Microsoft App-V 4.6 beta, the first version to not only support 64-bit clients but also the virtualization of true 64-bit applications:
Today, I am happy to announce immediate availability of Microsoft Application Virtualization (App-V) 4.6 Beta. At TechEd EMEA we announced our commitment to ship the next version of App-V in H1 2010. In March of this year, as part of the MDOP 2009 launch, we indicated that the development of App-V 4.6 was underway. Today, we have reached a major milestone and are a step closer to our goal.
This will be the first version of App-V to support both x64 and x86 Windows platforms. The primary focus of this release is to enable App-V to take advantage of 64-bit Windows platforms including Windows 7 and Windows Server 2008 R2. We’ve also made some improvements in the App-V Sequencer such as simplifying the workflow for creating virtual applications and adding the ability to sequence true 64-bit applications, a first to market! For customers running Windows XP or Windows Vista, you can also use App-V 4.6 Beta and take advantage of the support for Office 2010, 64-bit platform support and additional features in the release.
To get all the details and find out how you can download your very own copy see http://blogs.technet.com/mdop/archive/2009/07/30/app-v-4-6-public-beta-now-available-for-download.aspx.
J.C. Hornbeck | Manageability Knowledge Engineer
Understanding the autoload feature is important for those users either new to App-V in general or are in the process of planning an upgrade to 4.5 from a previous version of Softgrid. Administrators need to understand the various characteristics of the autoload feature and its options for configuration.
First and foremost, autoload governs how the primary and secondary feature block sections of an application are delivered to the client.
It is also important to understand some potential ramifications of using them. Use of autoload triggers will likely increase the initial network traffic of SFT streaming following an installation or upgrade of App-V 4.5. For managed bandwidth environments, this can be a cause of concern especially if the defaults are left in place.
Use of autoload, however, will not cause significant increase to your client overhead since the background streaming will be running using a background thread running at a lower priority. The speed of streaming will be determined by the overall CPU usage of the entire operating system
There are several ways to configure these options when deploying the App-V 4.5 Desktop or Terminal Services Client. You can set these parameters interactively during the installation of the client, through use of the non-interactive command-line installer parameters, manually within the registry, through use of the SFTMIME command, or controlled via group policy.
Setting Autoload Options During an interactive Installation
Autoload options are available when you reach the Runtime Package Policy Configuration dialog box.
The client uses these settings to govern background streaming for applications. Again, bear in mind the defaults especially as it will lead to increased network traffic if set.[PB1]
- When to Load: This basically determines your autoload triggers.
· On Launch: Means the background streaming will start as soon as the application is launched for anything outside of the primary feature block.
· On Login: Means user-authorized applications will start background streaming when the user log on.
· On Publishing Refresh: A new application that has been granted to the user will start background streaming following the periodic publishing refresh (DC Refresh.)
- What Applications to auto load: This actually refers to your autoload targets (applications affected.)
· Do not automatically load applications: Means no applications will be loaded.
· Automatically load previously used applications: Applications previously assigned to the user and launched will be autoloaded into the cache via background streaming
· Automatically Load all applications: Means all applications assigned to the user will be loaded into the cache via background streaming.
Setting Autoload Options with the Client MSI Installer
You can set these options non-interactively when leveraging the command line options of the App-V Client MSI installer (msiexec.exe /i "setup.msi.") For setting the Autoload triggers (when to autoload,) you can use the AUTOLOADTRIGGERS=[0|1|2|4|5] parameter to configure when to autoload during setup.
For autoload targets (which applications are affected) you can use the AUTOLOADONLAUNCH (Default=1), AUTOLOADONLOGIN (Default=1), AUTOLOADONREFRESH (Default=0) and AUTOLOADTARGET.
Each parameter affects loading behavior as follows:
- AUTOLOADONLOGIN—Loading starts when the user logs in.
- AUTOLOADONLAUNCH—Loading starts when the user starts an application.
- AUTOLOADONREFRESH—Loading starts when a publishing refresh occurs.
For AUTOLOAD TARGET, This parameter indicates what will be autoloaded when any given AutoLoadTrigger occurs. The values are as follows:
- None – No autoloading regardless of what triggers were set
- All – If a trigger is enabled all applications that are on the client will be loaded
- Previously Used – If a trigger is enable only applications that have been previously launched will be autoloaded
Setting Autoload options with the SFTMIME Command
You can manually configure autoload settings for individual packages by using the SFTMIME command. The SFTMIME ADD PACKAGE verb allows you to set autoload settings with the following switches:
/AUTOLOADONREFRESH
Background loading is performed after a publishing refresh.
/AUTOLOADONLOGIN
Background loading is performed when a user logs in.
/AUTOLOADONLAUNCH
Background loading is performed after a user starts an application from the package.
/AUTOLOADTARGET target
Indicates which applications from the package will be autoloaded.
NONE
No autoloading will be performed, despite the presence of any /AUTOLOADONxxx flags.
ALL
If an autoload trigger is enabled, all applications in the package will be loaded into cache whether or not they have been previously started.
PREVUSED
If an autoload trigger is enabled, the package will load if any applications in this package have previously been started by a user.
In addition, the CONFIGURE PACKAGE verb has options for adjusting existing autoload settings for a specific package. Those values for the CONFIGURE PACKAGE verb are as follows:
/AUTOLOADNEVER
Background loading is turned off for the package.
/AUTOLOADONREFRESH
Background loading is performed after a publishing refresh.
/AUTOLOADONLOGIN
Background loading is performed when a user logs in.
/AUTOLOADONLAUNCH
Background loading is performed after a user starts an application from the package.
/AUTOLOADTARGET <target>
Indicates which applications from the package will be autoloaded.
NONE
No autoloading will be performed despite the presence of any /AUTOLOADONxxx flags.
ALL
If an autoload trigger is enabled, all applications in the package will be loaded into cache regardless of whether they have ever been launched.
PREVUSED
If an autoload trigger is enabled, the package will load if any applications in this package have previously been started by a user.
Controlling AUTOLOAD settings using a Group Policy
If you have installed the App-V 4.5 ADM template for Group Policy preferences, you can use a GPO to control autoload settings.
Once the template for App-V has been imported, you can find these settings under Computer Configuration - Administrative Templates - Microsoft Application Virtualization Client - Communication.
The following table lists the values
| Policy | Registry Value Affected | Bit mask values |
| Set Background Loading Triggers | AutoLoadTriggers | (0) Never: No bits are set (value is 0), no auto loading will be performed, as there are no triggers set (1) OnLaunch: Perform background loading when a user launches an application (2) OnRefresh: Perform background loading anytime a publishing refresh occurs. (4) OnLogin: Perform background loading for any application when a user logs in. Default: 0x5 (OnLaunch|OnLogin) |
| Specify What to Load in Background | AutoLoadTarget | 1 (WD/TS) This parameter indicates what will be autoloaded when any given AutoLoadTriggers occur. Bit mask values: (0) None - No autoloading, regardless of what triggers may be set. (1) PreviouslyUsed (default) - If any AutoLoad trigger is enabled, load only the packages where at least one app in the package has been previously used by a user (i.e. launched or precached,). This targets ‘important’ apps, meaning apps that have been used before are likely to be more important to a user than apps that have never been launched. (2) All - If any enabled AutoLoad trigger is enabled, all applications in the package (per package) or for all packages (set for client) will be automatically loaded, regardless of whether they have ever been launched. |
Registry Locations of Autoload Settings
The autoload triggers are also stored in the following registry locations: These can also be adjusted directly, however it will require the restart of the App-V client.
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
Steve Thomas | Senior Support Escalation Engineer
