Article ID: 976338 - View products that this article applies to.
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=166004Improved 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:
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:
(http://support.microsoft.com/kb/973873/ )Hotfix Package 5 for Microsoft Application Virtualization 4.5 Cumulative Update 1: August 2009
How to obtain App-V 4.5 SP1To obtain this App-V 4.5 SP1, visit your volume licensing or subscription Web site for Microsoft Application Virtualization.
Known issuesFor the latest information about the known issues, visit the following Microsoft TechNet Web site:
Sequencing Microsoft Office 2010
You cannot sequence Microsoft Office 2010 in App-V 4.5 SP1.
Third-party Kerberos realms and publishing refreshConsider the following scenario: