微软应用虚拟化App-V 5.1官方指南

需积分: 19 167 浏览量更新于2024-07-17 收藏 3.59MB PDF 举报

"APP-V-5.1.pdf 是微软官方发布的关于应用虚拟化技术的文档，专注于App-V 5.1版本，包含了从入门到规划、部署、操作、故障排除及技术参考等一系列全面的指导内容。此外，文档还涵盖了App-V 5.0的相关信息，为管理员提供了一个使应用程序无需在终端用户计算机上直接安装即可使用的解决方案，以避免应用冲突并实现集中管理。" 微软应用虚拟化（App-V）5.1是这个技术的一个重要版本，它允许管理员将应用程序转化为中心管理的服务，这些服务不会被安装在用户的电脑上，从而避免了应用程序之间的冲突。这一特性对于多应用环境中的系统管理和维护极为有益，确保了系统的稳定性和兼容性。 App-V 5.1管理员指南详细介绍了如何开始使用该技术，包括设置环境、规划策略、部署虚拟化应用以及后续的运行操作。这部分内容对IT管理员来说至关重要，它提供了从无到有实施App-V 5.1的步骤和最佳实践。例如，"Getting Started with App-V 5.1"章节可能包含创建和发布虚拟应用包的教程，以及配置服务器和客户端的指南。 "Planning for App-V 5.1"部分则帮助管理员评估组织的需求，确定最合适的部署策略，如考虑网络基础设施、服务器容量、用户访问模式等。而"Deploying App-V 5.1"章节则深入到实际的安装和配置过程，可能涵盖服务器和客户端的安装选项、更新策略以及与其他Microsoft产品的集成。在操作和故障排除章节，"Operations for App-V 5.1"和"Troubleshooting App-V 5.1"提供了日常管理和问题解决的指导，帮助管理员应对可能出现的问题，保持系统的高效运行。技术参考部分("Technical Reference for App-V 5.1")则为高级用户和开发者提供了更深入的技术细节，如API接口、数据流工作原理等。文档还包含了App-V 5.0的资料，这为那些仍在使用或计划升级到5.1版本的用户提供了一个过渡的参考。版本之间的差异和改进点通常会在发行说明中详细列出，例如"Release Notes for App-V 5.1"和"Release Notes for App-V 5.0 SP3"。这份PDF是IT管理员部署和管理App-V 5.1的宝贵资源，它提供了全面的信息，支持从规划到维护的整个生命周期管理。无论是初次接触应用虚拟化还是寻求优化现有部署，都能从中获益。

When streaming packages in Shared Content Store

(

SCS

)

mode to a

client that is also managed with AppLocker, additional data is written to

the local disk.

In the Management Console Add Package dialog box, the Browse

button is not available when using Chrome or Firefox

Upgrading App

V Management Server to 5.1 sometimes fails with the

message “A database error occurred”

Users cannot open a package in a user

published connection group if

you add or remove an optional package

Sequencer when updating the saved package again.

Workaround: To add a file type association, open the package for modification and run the update wizard. During

the Installation step, add the new file type association through the operating system. The sequencer will detect the

new association in the system registry and add it to the package’s virtual registry, where it will be available to the

client.

To decrease the amount of data written to a client’s local disk, you can enable SCS mode on the App-V 5.1 Client to

stream the contents of a package on demand. However, if AppLocker manages an application within the package,

some data might be written to the client’s local disk that would not otherwise be written.

Workaround: None

On the Packages page of the Management Console, if you click Add or Upgrade in the lower-right corner, the Add

Package dialog box appears. If you are accessing the Management Console using Chrome or Firefox as your

browser, you will not be able to browse to the location of the package.

Workaround: Type or copy and paste the path to the package into the Add Package input field. If the

Management Console has access to this path, you will be able to add the package. If the package is on a network

share, you can browse to the location using File Explorer by doing these steps:

1. While pressing Shift, right-click on the package file

2. Select Copy as path

3. Paste the path into the Add Package dialog box input field

If you install the App-V 5.0 SP1 Management Server, and then try to upgrade to App-V 5.1 Server when multiple

connection groups are configured and enabled, the following error is displayed: “A database error occurred.

Reason: 'Invalid column name 'PackageOptional'. Invalid column name 'VersionOptional'.”

Workaround: Run this command on your SQL database:

ALTER TABLE AppVManagement.dbo.PackageGroupMembers ADD PackageOptional bit NOT NULL DEFAULT 0, VersionOptional

bit NOT NULL DEFAULT 0

where “AppVManagement” is the name of the database.

In environments that are running the RDS Client or that have multiple concurrent users per computer, logged-in

users cannot open applications in packages that are in a user-published connection group if an optional package is

added to or removed from the connection group.

Workaround: Have users log out and then log back in.

Error message is erroneously displayed when the connection group is

published only to the user

Icons not displayed properly in Sequencer

InsertVersionInfo.sql script no longer required for the Management

Database

Microsoft Visual Studio 2012 not supported

Application filename restrictions for App

V 5.x Sequencer

When you run Repair-AppvClientConnectionGroup, the following error is displayed, even when the connection

group is published only to the user: “Internal App-V Integration error: Package not integrated for the user. Please

ensure that the package is added to the machine and published to the user.”

Workaround: Do one of the following:

Publish all packages in a connection group.

The problem arises when the connection group being repaired has packages that are missing or not

available to the user (that is, not published globally or to the user). However, the repair will work if all of the

connection group’s packages are available, so ensure that all packages are published.

Repair packages individually using the Repair-AppvClientPackage command rather than the Repair-

AppvClientConnectionGroup command.

Determine which packages are available to users and then run the Repair-AppvClientPackage command

once for each package. Use PowerShell cmdlets to do the following:

1. Get all the packages in a connection group.

2. Check to see if each package is currently published.

3. If the package is currently published, run Repair-AppvClientPackage on that package.

Icons in the Shortcuts and File Type Associations tab are not displayed correctly when modifying a package in the

App-V Sequencer. This problem occurs when the size of the icons are not 16x16 or 32x32.

Workaround: Only use icons that are 16x16 or 32x32.

The InsertVersionInfo.sql script is not required for versions of the App-V management database later than App-V

5.0 SP3.

The Permissions.sql script should be updated according to Step 2 in KB article 3031340.

Important

Step 1 is not required for versions of App-V later than App-V 5.0 SP3.

App-V 5.1 does not support Visual Studio 2012.

Workaround: None

The App-V 5.x Sequencer cannot sequence applications with filenames matching "CO_<x>" where x is any numeral.

Error 0x8007139F will be generated.

Workaround: Use a different filename

High Level Architecture for App

V 5.1

12/6/2017 • 1 min to read • Edit Online

Architecture Overview

ELEMENT MORE INFORMATION

Use the following information to help you simplify you Microsoft Application Virtualization (App-V) 5.1

deployment.

A typical App-V 5.1 implementation consists of the following elements.

App-V 5.1 Management Server The App-V 5.1 Management server provides overall

management functionality for the App-V 5.1

infrastructure. Additionally, you can install more than one

instance of the management server in your environment

which provides the following benefits:

Fault Tolerance and High Availability – Installing

and configuring the App-V 5.1 Management

server on two separate computers can help in

situations when one of the servers is unavailable

or offline.

You can also help increase App-V 5.1 availability

by installing the Management server on multiple

computers. In this scenario, a network load

balancer should also be considered so that server

requests are balanced.

Scalability – You can add additional management

servers as necessary to support a high load, for

example you can install multiple servers behind a

load balancer.

App-V 5.1 Publishing Server The App-V 5.1 publishing server provides functionality for

virtual application hosting and streaming. The publishing

server does not require a database connection and

supports the following protocols:

HTTP, and HTTPS

You can also help increase App-V 5.1 availability by

installing the Publishing server on multiple computers. A

network load balancer should also be considered so that

server requests are balanced.

App-V 5.1 Reporting Server The App-V 5.1 Reporting server enables authorized users

to run and view existing App-V 5.1 reports and ad hoc

reports that can help them manage the App-V 5.1

infrastructure. The Reporting server requires a connection

to the App-V 5.1 reporting database. You can also help

increase App-V 5.1 availability by installing the Reporting

server on multiple computers. A network load balancer

should also be considered so that server requests are

balanced.

剩余727页未读，继续阅读

张绕忠

粉丝: 0
资源: 1

微软应用虚拟化App-V 5.1官方指南

最新资源