Server Application Virtualization Service Pack 1 Release Notes
Applies To: System Center 2012 SP1 - Virtual Machine Manager, System Center 2012 R2 Virtual Machine Manager
To search these Release Notes, press CTRL+F.
Read these Release Notes thoroughly before you install Microsoft Server Application Virtualization (Server App-V) Service Pack 1. These Release Notes contain information that you must have to successfully install or use Server App-V Service Pack 1. This document contains information that is not available in the product documentation. If there is a difference between these Release Notes and other Server App-V documentation, the latest change should be considered authoritative. These Release Notes supersede the content that is included with this product.
To help protect against security vulnerabilities and viruses, we recommend that you install the latest available security updates for any new software. For more information, see the Microsoft Security website at http://go.microsoft.com/fwlink/?LinkId=3482.
You can provide feedback, make a suggestion, or report an issue with the Microsoft Application Virtualization (App-V) management system in a community forum on the Microsoft Application Virtualization TechCenter (http://go.microsoft.com/fwlink/?LinkId=275110).
You can also provide your feedback about the documentation directly to the App-V documentation team. Send your documentation feedback to firstname.lastname@example.org.
This section provides the most up-to-date information about issues with Server App-V Service Pack 1. These issues do not appear in the product documentation and in some cases might contradict existing product documentation. When it is possible, these issues will be addressed in later releases.
The Tier feature in Server App-V Server cannot detect connections that are made to databases that are made with DSN-based ODBC connections. If the installer file associated with the application you are trying to sequence requires this type of connection, the sequencer will not detect it during sequencing. An example of an application that exhibits this functionality is Microsoft Dynamics GP running on Microsoft Windows Server 2008 R2.
WORKAROUND During the monitoring phase of sequencing, use the following steps:
Because the sequencer does not automatically retrieve Microsoft SQL Server DACPAC’s and T-SQL scripts from databases during sequencing, you must manually export these artifacts from the Microsoft SQL Server used during installation. After you have these artifacts, you can use them as if they were automatically generated by the sequencer. Use the following link for more information about how to manually extract DACPACs and T-SQL scripts:
To extract a DAC from a Microsoft SQL Server Database (http://go.microsoft.com/fwlink/?LinkId=275108).
To generate T-SQL scripts, use the following procedure:
In Microsoft SQL Server Management Studio, right-click the database you wish to export and select Tasks, and then click Generate Scripts.
In Choose Objects, select all Tables.
In Set Scripting Options, select Advanced.
In the General section, change the value for Type of data to script to Data Only.
Proceed with the remainder of the steps of the wizard.
After you sequence Microsoft Dynamics AX 2009 on a computer that is running Windows Server 2008 R2 x64, you may see an error Side-by-side assembly privatization failed message in the Package Completed section of the Server App-V sequencer.
WORKAROUND Despite the error, the package is actually created without issues. You can ignore this error. No workaround is required.
If an application is sequenced that requires an IWAM_ account for IIS 6 on a computer running Windows Server 2003, the package is not added.
WORKAROUND This is a known issue. There is no workaround.
Applications such as Microsoft SQL Server Reporting Services that create machine name accounts as database logins (for example, domain\machinename$) donot function as expected because they are tied to a specific machine name.
WORKAROUND After you deploy the DACPAC and T-SQL scripts to your database, manually add the appropriate machine name accounts by using the Microsoft SQL Server Management Studio or another database administrative tool.
Certain applications that create Microsoft SQL Server databases also create database logins. The DACPAC that is generated for these databases contains the definition for any new logins, but not the associated passwords. At deployment time, a password must be specified for the new logins.
WORKAROUND The T-SQL scripts that are generated by the Server App-V sequencer will have a line item for setting the password for each new login that is created during sequencing. Open the T-SQL script and look for lines like this, where LOGINNAME is the new Microsoft SQL Server login. Replace $(LOGINNAME_PASSWORD) with the password that you want to use for the new login:
ALTER LOGIN [LOGINNAME] WITH PASSWORD = ‘$(LOGINNAME_PASSWORD)’