About App-V 5.0 SP3
Dotyczy: Application Virtualization 5.0 SP1, Application Virtualization 5.0 SP2, Application Virtualization 5.0 SP3
Use the following sections to review information about significant changes that apply to Microsoft Application Virtualization (App-V) 5.0 SP3:
App-V 5.0 SP3 software prerequisites and supported configurations
Migrating to App-V 5.0 SP3
Manually created connection group xml file requires update to schema
Improvements to connection groups
Administrators can publish and unpublish packages for a specific user
Enable only administrators to publish and unpublish packages
RunVirtual registry key supports packages that are published to the user
New PowerShell cmdlets and updateable cmdlet help
Primary virtual application directory (PVAD) is hidden but can be turned on
ClientVersion is required to view App-V publishing metadata
App-V event logs have been consolidated
App-V 5.0 SP3 software prerequisites and supported configurations
See the following links for the App-V 5.0 SP3 software prerequisites and supported configurations.
| Links to prerequisites and supported configurations | Description |
|---|---|
Prerequisite software that you must install before starting the App-V 5.0 SP3 installation |
|
Supported operating systems and hardware requirements for the App-V Server, Sequencer, and Client components |
Migrating to App-V 5.0 SP3
Use the following information to upgrade to App-V 5.0 SP3 from earlier versions.
Before you start the upgrade
Review the following information before you start the upgrade:
| Items to review before upgrading | Description |
|---|---|
Components to upgrade |
Uwaga To use the App-V client user interface, download the existing version from Microsoft Application Virtualization 5.0 Client UI Application. |
Upgrading from App-V 4.x |
You must first upgrade to App-V 5.0. You cannot upgrade directly from App-V 4.x to App-V 5.0 SP3. For more information, see: |
Upgrading from App-V 5.0 or later |
You can upgrade to App-V 5.0 SP3 directly from any of the following versions:
To upgrade to App-V 5.0 SP3, follow the steps in the remaining sections of this article. |
Required changes to packages and connection groups after upgrade |
None. Packages and connection groups will continue to work as they currently do. |
Steps to upgrade the App-V infrastructure
Complete the following steps to upgrade each component of the App-V infrastructure to App-V 5.0 SP3.
| Step | For more information | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
Step 1: Upgrade the App-V Server. If you are not using the App-V Server, skip this step and go to the next step. Uwaga The App-V 5.0 SP3 client is compatible with the App-V 5.0 SP1 Server. |
Follow these steps:
|
||||||||||
Step 2: Upgrade the App-V Sequencer. |
|||||||||||
Step 3: Upgrade the App-V client or App-V RDS client. |
Check registry keys before installing the App-V 5.0 SP3 Server
This is step 3 from the previous table.
When this step is required |
You are upgrading from App-V SP1 with any subsequent Hotfix Packages that you installed by using an .msp file. |
Which components require that you do this step |
Only the App-V Server components that you are upgrading. |
When you need to do this step |
Before you upgrade the App-V Server to App-V 5.0 SP3 |
What you need to do |
Using the information in the following tables, update each registry key value under |
ManagementDatabase key
If you are installing the Management database, set these registry keys under HKLM\Software\Microsoft\AppV\Server\ManagementDatabase.
| Key name | Description |
|---|---|
IS_MANAGEMENT_DB_PUBLIC_ACCESS_ACCOUNT_REQUIRED |
Describes whether a public access account is required to access non-local management databases. Value is set to “1” if it is required. |
MANAGEMENT_DB_NAME |
Name of the Management database. |
MANAGEMENT_DB_PUBLIC_ACCESS_ACCOUNT |
Account used for read (public) access to the Management database. Used when |
MANAGEMENT_DB_PUBLIC_ACCESS_ACCOUNT_SID |
Secure identifier (SID) of the account used for read (public) access to the Management database. Used when |
MANAGEMENT_DB_SQL_INSTANCE |
SQL Server instance for the Management database. If the value is blank, the default database instance is used. |
MANAGEMENT_DB_WRITE_ACCESS_ACCOUNT |
Account used for write (administrator) access to the Management database. |
MANAGEMENT_DB_WRITE_ACCESS_ACCOUNT_SID |
Secure identifier (SID) of the account used for write (administrator) access to the Management database. |
MANAGEMENT_REMOTE_SERVER_MACHINE_ACCOUNT |
Management server remote computer account (domain\account). |
MANAGEMENT_SERVER_INSTALL_ADMIN_ACCOUNT |
Installation administrator login for the Management server (domain\account). |
MANAGEMENT_SERVER_MACHINE_USE_LOCAL |
Valid values are:
|
ManagementService key
If you are installing the Management server, set these registry keys under HKLM\Software\Microsoft\AppV\Server\ManagementService.
| Key name | Description |
|---|---|
MANAGEMENT_ADMINACCOUNT |
Active Directory Domain Services (AD DS) group or account that is authorized to manage App-V (domain\account). |
MANAGEMENT_DB_SQL_INSTANCE |
SQL server instance that contains the Management database. If the value is blank, the default database instance is used. |
MANAGEMENT_DB_SQL_SERVER_NAME |
Name of the remote SQL server with the Management database. If the value is blank, the local computer is used. |
ReportingDatabase key
If you are installing the Reporting database, set these registry keys under HKLM\Software\Microsoft\AppV\Server\ReportingDatabase.
| Key name | Description |
|---|---|
IS_REPORTING_DB_PUBLIC_ACCESS_ACCOUNT_REQUIRED |
Describes whether a public access account is required to access non-local reporting databases. Value is set to “1” if it is required. |
REPORTING_DB_NAME |
Name of the Reporting database. |
REPORTING_DB_PUBLIC_ACCESS_ACCOUNT |
Account used for read (public) access to the Reporting database. Used when |
REPORTING_DB_PUBLIC_ACCESS_ACCOUNT_SID |
Secure identifier (SID) of the account used for read (public) access to the Reporting database. Used when |
REPORTING_DB_SQL_INSTANCE |
SQL Server instance for the Reporting database. If the value is blank, the default database instance is used. |
REPORTING_DB_WRITE_ACCESS_ACCOUNT |
|
REPORTING_DB_WRITE_ACCESS_ACCOUNT_SID |
|
REPORTING_REMOTE_SERVER_MACHINE_ACCOUNT |
Reporting server remote computer account (domain\account). |
REPORTING_SERVER_INSTALL_ADMIN_ACCOUNT |
Installation administrator login for the Reporting server (domain\account). |
REPORTING_SERVER_MACHINE_USE_LOCAL |
Valid values are:
|
ReportingService key
If you are installing the Reporting server, set these registry keys under HKLM\Software\Microsoft\AppV\Server\ReportingService.
| Key name | Description |
|---|---|
REPORTING_DB_SQL_INSTANCE |
SQL Server instance for the Reporting database. If the value is blank, the default database instance is used. |
REPORTING_DB_SQL_SERVER_NAME |
Name of the remote SQL server with the Reporting database. If the value is blank, the local computer is used. |
Manually created connection group xml file requires update to schema
If you are manually creating the connection group XML file, and want to use the new “optional packages” and “use any version” features that are described in Improvements to connection groups, you must specify the following schema in the XML file:
xmlns="https://schemas.microsoft.com/appv/2014/virtualapplicationconnectiongroup"
For examples and more information, see About the Connection Group File.
Improvements to connection groups
You can manage connection groups more easily by using optional packages and other improvements that have been added in App-V 5.0 SP3. The following table summarizes the tasks that you can perform by using the new connection group features, and links to more detailed information about each task.
| Task/feature | Description | Links to more information | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
Enable a connection group to include optional packages |
Including optional packages in a connection group enables you to dynamically determine which applications will be included in the connection group’s virtual environment, based on the applications that users are entitled to. You don’t need to manage as many connection groups because you can mix optional and non-optional packages in the same connection group. Mixing packages allows different groups of users to use the same connection group, even though users might have only one package in common. Example: You can enable a package with Microsoft Office for all users, but enable different optional packages, which contain different Office plug-ins, to different subsets of users. |
|||||||||
Unpublish or delete an optional package without changing the connection group |
Unpublish or delete, or unpublish and republish an optional package, which is in a connection group, without having to disable or re-enable the connection group on the App-V client. |
|||||||||
Publish connection groups that contain user-published and globally published packages |
Create a user-published connection group that contains user-published and globally published packages. |
How to Create a Connection Group with User-Published and Globally Published Packages |
||||||||
Make a connection group ignore the package version |
Configure a connection group to accept any version of a package, which enables you to upgrade a package without having to disable the connection group. In addition, if there is an optional package with an incorrect version in the connection group, the package is ignored and won’t block the connection group’s virtual environment from being created. |
|||||||||
Limit end users’ publishing capabilities |
Enable only administrators (not end users) to publish packages and to enable connection groups. |
For information about connection groups, see How to Allow Only Administrators to Enable Connection Groups For information about packages, see the following articles:
|
||||||||
Enable or disable a connection group for a specific user |
Administrators can enable or disable a connection group for a specific user by using the optional –UserSID parameter with the following cmdlets:
|
|||||||||
Merging identical package paths into one virtual directory in connection groups |
If two or more packages in a connection group contain identical directory paths, the paths are merged into a single virtual directory inside the connection group virtual environment. This merging of paths allows an application in one package to access files that are in a different package. |
Merging identical package paths into one virtual directory in connection groups |
Administrators can publish and unpublish packages for a specific user
Administrators can use the following cmdlets to publish or unpublish packages for a specific user. To use the cmdlets, enter the –UserSID parameter, followed by the user’s security identifier (SID). For more information, see:
| Cmdlet | Examples |
|---|---|
Publish-AppvClientPackage |
Publish-AppvClientPackage “ContosoApplication” -UserSID S-1-2-34-56789012-3456789012-345678901-2345 |
Unpublish-AppvClientPackage |
Unpublish-AppvClientPackage “ContosoApplication” -UserSID S-1-2-34-56789012-3456789012-345678901-2345 |
Enable only administrators to publish and unpublish packages
You can enable only administrators (not end users) to publish and unpublish packages by using one of the following methods:
| Method | More information |
|---|---|
Group Policy setting |
Navigate to the following Group Policy Object node: Computer Configuration > Policies > Administrative Templates > System > App-V > Publishing. Enable the Require publish as administrator Group Policy setting. |
PowerShell |
To enable only administrators to publish or unpublish packages |
RunVirtual registry key supports packages that are published to the user
App-V 5.0 SP3 adds support for using the RunVirtual registry key with virtualized applications that are in user-published packages. The RunVirtual registry key lets you run a locally installed application in a virtual environment, along with applications that have been virtualized by using App-V.
Previously, the virtualized applications in App-V packages had to be published globally. For more about RunVirtual and about other methods of running locally installed applications in a virtual environment with virtualized applications, see Running a Locally Installed Application Inside a Virtual Environment with Virtualized Applications.
New PowerShell cmdlets and updateable cmdlet help
New PowerShell cmdlets and updateable cmdlet help are included in App-V 5.0 SP3. To download the cmdlet modules, see Loading the PowerShell cmdlets.
New App-V 5.0 SP3 Server PowerShell cmdlets
New Windows PowerShell cmdlets for the App-V Server have been added to help you manage connection groups.
| Cmdlet | Description |
|---|---|
Add-AppvServerConnectionGroupPackage |
Appends a package to the end of a connection group's package list and enables you to configure the package as optional and/or with no version within the connection group. |
Set-AppvServerConnectionGroupPackage |
Enables you to edit details about the connection group package, such as whether it is optional. |
Remove-AppvServerConnectionGroupPackage |
Removes a package from a connection group. |
Getting help for the PowerShell cmdlets
Cmdlet help is available in the following formats:
| Format | Description | ||||||||
|---|---|---|---|---|---|---|---|---|---|
As a downloadable module |
To get the latest help after downloading the cmdlet module:
|
||||||||
On TechNet as web pages |
See the App-V node under Microsoft Desktop Optimization Pack Automation with Windows PowerShell. |
For more information, see How to Load the PowerShell Cmdlets and Get Cmdlet Help.
Primary virtual application directory (PVAD) is hidden but can be turned on
The primary virtual application directory (PVAD) is hidden in App-V 5.0 SP3, but you can turn it back on and make it visible by using one of the following methods:
| Method | Steps |
|---|---|
Use a command line parameter |
Pass the –EnablePVADControl parameter to the Sequencer.exe. |
Create a registry subkey |
|
More about PVAD: When you use the Sequencer to create a package, you can enter any installation path for the package. In past versions of App-V, you were required to specify the primary virtual application directory (PVAD) of the application as the path. PVAD is the directory to which you would typically install an application on your local computer if you weren’t using App-V. For example, if you were installing Office on a computer, the PVAD typically would be C:\Program Files\Microsoft Office\.
ClientVersion is required to view App-V publishing metadata
In App-V 5.0 z dodatkiem SP3, you must provide the following values in the address when you query the App-V Publishing server for metadata:
| Value | Additional details |
|---|---|
ClientVersion |
If you omit the ClientVersion parameter from the query, the metadata excludes the new App-V 5.0 SP3 features. |
ClientOS |
You have to provide this value only if you select specific client operating systems when you sequence the package. If you select the default (all operating systems), do not specify this value in the query. If you omit the ClientOS parameter from the query, only the packages that were sequenced to support any operating system appear in the metadata. |
For syntax and examples of this query, see Viewing App-V Server Publishing Metadata.
App-V event logs have been consolidated
The following event logs, previously located at Applications and Services Logs/Microsoft/AppV/<App-V component>, have been moved to Applications and Services Logs/Microsoft/AppV/ServiceLog.
To view the logs, select View > Show Analytic and Debug Logs in the Event Viewer application.
Client-Catalog
Client-Integration
Client-Orchestration
Client-PackageConfig
Client-Scripting
Client-Service
Client-Vemgr
Client-VFSC
FilesystemMetadataLibrary
ManifestLibrary
PolicyLibrary
Subsystems-ActiveX
Subsystems-AppPath
Subsystems-Com
Subsystems-fta
How to Get MDOP Technologies
App-V is a part of the Microsoft Desktop Optimization Pack (MDOP). MDOP is part of Microsoft Software Assurance. For more information about Microsoft Software Assurance and acquiring MDOP, see How Do I Get MDOP.
Got a suggestion for App-V?
Add or vote on suggestions here. For App-V issues, use the App-V TechNet Forum.
Zobacz też
Pojęcia
Release Notes for App-V 5.0 SP3
-----
You can learn more about MDOP in the TechNet Library, search for troubleshooting on the TechNet Wiki, or follow us on Facebook or Twitter.
-----