mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-13 13:57:22 +00:00
App-V updates
This commit is contained in:
Maggie Evans
parent
73d494c908
commit
0ffdbcee6a
@ -14,8 +14,8 @@ ms.prod: w10
|
||||
|
||||
This checklist can be used to help you during an App-V deployment.
|
||||
|
||||
> [!NOTE]
|
||||
> This checklist outlines the recommended steps and a high-level list of items to consider when deploying App-V features. It is recommended that you copy this checklist into a spreadsheet program and customize it for your use.
|
||||
>**Note**<br>
|
||||
This checklist outlines the recommended steps and items to consider when deploying App-V features. We recommend that you copy this checklist into a spreadsheet program and customize it for your use.
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Enable the App-V desktop client (Windows 10)
|
||||
description: Enable the App-V desktop client
|
||||
title: Enable the App-V in-box client (Windows 10)
|
||||
description: How to enable the App-V in-box client installed with Windows 10.
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
@ -32,7 +32,7 @@ With Windows 10, version 1607, the App-V client is installed automatically. You
|
||||
|
||||
3. Restart the device.
|
||||
|
||||
4. To verify that the App-V client is enabled on the device, enter **Get-AppvStatus** in Windows PowerShell.
|
||||
4. To verify that the App-V client is enabled on the device, type `Get-AppvStatus` and press ENTER.
|
||||
|
||||
See [Using the client management console](appv-using-the-client-management-console.md) for information about configuring the App-V client.
|
||||
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Evaluating App-V (Windows 10)
|
||||
description: Evaluating App-V
|
||||
description: Evaluating App-V for Windows 10
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
@ -11,8 +11,7 @@ ms.prod: w10
|
||||
|
||||
# Evaluating App-V
|
||||
|
||||
|
||||
Before you deploy pp-V into a production environment, you should evaluate it in a lab environment. You can use the information in this topic to set up App-V in a lab environment for evaluation purposes only.
|
||||
Before you deploy App-V into a production environment, you should evaluate it in a lab environment. You can use the information in this topic to set up App-V in a lab environment for evaluation purposes only.
|
||||
|
||||
## Configure lab computers for App-V Evaluation
|
||||
|
||||
@ -34,7 +33,7 @@ Use the following links for information about setting up the App-V server in you
|
||||
|
||||
- [Administering App-V Virtual Applications by Using the Management Console](appv-administering-virtual-applications-with-the-management-console.md)
|
||||
|
||||
### Installing the App-V Client
|
||||
### Enabling the App-V Client
|
||||
|
||||
Use the following link for more information about creating and managing virtualized packages in your lab environment.
|
||||
|
||||
|
||||
@ -12,7 +12,7 @@ ms.prod: w10
|
||||
# Application Virtualization (App-V) for Windows 10 overview
|
||||
|
||||
|
||||
The topics in this section provides information and step-by-step procedures to help you administer App-V and its components. This information will be valuable for system administrators who manage large installations with many servers and clients and for support personnel who interact directly with the computers or the end users.
|
||||
The topics in this section provide information and step-by-step procedures to help you administer App-V and its components. This information will be valuable for system administrators who manage large installations with many servers and clients and for support personnel who interact directly with the computers or the end users.
|
||||
|
||||
[Getting Started with App-V](appv-getting-started.md)
|
||||
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Getting Started with App-V (Windows 10)
|
||||
description: Getting Started with App-V
|
||||
description: Getting Started with App-V for Windows 10
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: How to Install the Management and Reporting Databases on Separate Computers from the Management and Reporting Services (Windows 10)
|
||||
description: How to Install the Management and Reporting Databases on Separate Computers from the Management and Reporting Services
|
||||
description: How to install the Management and Reporting Databases on Separate Computers from the Management and Reporting Services
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
@ -14,7 +14,7 @@ ms.prod: w10
|
||||
|
||||
Use the following procedure to install the database server and management server on different computers. The computer you plan to install the database server on must be running a supported version of Microsoft SQL or the installation will fail.
|
||||
|
||||
**Note**
|
||||
>**Note**
|
||||
After you complete the deployment, the **Microsoft SQL Server name**, **instance name** and **database name** will be required by the administrator installing the service to be able to connect to these databases.
|
||||
|
||||
|
||||
@ -39,7 +39,7 @@ After you complete the deployment, the **Microsoft SQL Server name**, **instance
|
||||
|
||||
7. On the next **Create New Management Server Database** page, select **Use a remote computer**, and type the remote machine account using the following format: **Domain\\MachineAccount**.
|
||||
|
||||
**Note**
|
||||
>**Note**
|
||||
If you plan to deploy the management server on the same computer you must select **Use this local computer**.
|
||||
|
||||
|
||||
|
||||
@ -28,7 +28,7 @@ Use the following procedure to install the management server on a standalone com
|
||||
|
||||
6. On the **Configure Existing Management Database** page, select **Use a remote SQL Server**, and type the machine name of the computer running Microsoft SQL SQL, for example **SqlServerMachine**.
|
||||
|
||||
**Note**
|
||||
>**Note**
|
||||
If the Microsoft SQL Server is deployed on the same server, select **Use local SQL Server**.
|
||||
|
||||
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: How to Install the Publishing Server on a Remote Computer (Windows 10)
|
||||
description: How to Install the Publishing Server on a Remote Computer
|
||||
description: How to Install the App-V Publishing Server on a Remote Computer
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
@ -44,7 +44,7 @@ Use the following procedure to install the publishing server on a separate compu
|
||||
|
||||
3. Type the name of this server and a description (if required) and click **Add**.
|
||||
|
||||
9. To verify if the publishing server is running correctly, you should import a package to the management server, entitle the package to an AD group, and publish the package. Using an internet browser, open the following URL: **http://publishingserver:pubport**. If the server is running correctly information similar to the following will be displayed:
|
||||
9. To verify that the publishing server is running correctly, you should import a package to the management server, entitle the package to an AD group, and publish the package. Using an internet browser, open the following URL: **http://publishingserver:pubport**. If the server is running correctly information similar to the following will be displayed:
|
||||
|
||||
`<Publishing Protocol="1.0">`
|
||||
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: How to install the Reporting Server on a Standalone Computer and Connect it to the Database (Windows 10)
|
||||
description: How to install the Reporting Server on a Standalone Computer and Connect it to the Database
|
||||
description: How to install the App-V Reporting Server on a Standalone Computer and Connect it to the Database
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: How to Load the PowerShell Cmdlets and Get Cmdlet Help (Windows 10)
|
||||
description: How to Load the PowerShell Cmdlets and Get Cmdlet Help
|
||||
description: How to Load the App-V PowerShell Cmdlets and Get Cmdlet Help
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
|
||||
@ -25,7 +25,7 @@ The App-V server connects to the App-V database. Therefore you can install the m
|
||||
|
||||
Independent software vendors (ISV) who want to determine if an application is running virtualized with App-V should open a named object called **AppVVirtual-<PID>** in the default namespace. For example, Windows API **GetCurrentProcessId()** can be used to obtain the current process's ID, for example 4052, and then if a named Event object called **AppVVirtual-4052** can be successfully opened using **OpenEvent()** in the default namespace for read access, then the application is virtual. If the **OpenEvent()** call fails, the application is not virtual.
|
||||
|
||||
Additionally, ISV’s who want to explicitly virtualize or not virtualize calls on specific API’s with App-V and above, can use the **VirtualizeCurrentThread()** and **CurrentThreadIsVirtualized()** functions implemented in the AppEntSubsystems32.dll module. These provide a way of hinting at a downstream component that the call should or should not be virtualized.
|
||||
Additionally, ISV’s who want to explicitly virtualize or not virtualize calls on specific API’s with App-V 5.1 and later, can use the **VirtualizeCurrentThread()** and **CurrentThreadIsVirtualized()** functions implemented in the AppEntSubsystems32.dll module. These provide a way of hinting at a downstream component that the call should or should not be virtualized.
|
||||
|
||||
## Have a suggestion for App-V?
|
||||
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user