If you're already using App-V 5.x, you don't need to re-deploy the App-V server components as they haven't changed since App-V 5.0 was released. **Before you start:** -- Ensure that you’ve installed prerequisite software. See [App-V Prerequisites](appv-prerequisites.md). +- Ensure that you’ve installed required software. See [App-V Prerequisites](appv-prerequisites.md). - Review the server section of [App-V security considerations](appv-security-considerations.md). @@ -26,13 +26,19 @@ Use the following procedure to install the App-V server.. **To install the App-V server** -1. Copy the App-V server installation files to the computer on which you want to install it. +1. Download the App-V server components. All five App-V server components are included in the Microsoft Desktop Optimization Pack (MDOP) 2015 ISO package, which can be downloaded from: -2. Start the App-V server installation by right-clicking and running **appv\_server\_setup.exe** as an administrator, and then click **Install**. + - The [MSDN (Microsoft Developer Network) subscriptions site](https://msdn.microsoft.com/en-us/subscriptions/downloads/default.aspx#FileId=65215) You must have a MSDN subscription to download the MDOP ISO package from the MSDN subscriptions site. -3. Review and accept the license terms, and choose whether to enable Microsoft updates. + - The [Volume Licensing Service Center](https://www.microsoft.com/en-us/licensing/default.aspx) if you're using [Windows 10 for Enterprise or Education](https://www.microsoft.com/en-us/WindowsForBusiness/windows-product-home). -4. On the **Feature Selection** page, select all of the following components. +2. Copy the App-V server installation files to the computer on which you want to install it. + +3. Start the App-V server installation by right-clicking and running **appv\_server\_setup.exe** as an administrator, and then click **Install**. + +4. Review and accept the license terms, and choose whether to enable Microsoft updates. + +5. On the **Feature Selection** page, select all of the following components. | Component | Description | | - | - | @@ -42,21 +48,20 @@ Use the following procedure to install the App-V server.. | Reporting server | Provides App-V reporting services. | | Reporting database | Facilitates database predeployments for App-V reporting. | -5. On the **Installation Location** page, accept the default location where the selected components will be installed, or change the location by typing a new path on the **Installation Location** line. +6. On the **Installation Location** page, accept the default location where the selected components will be installed, or change the location by typing a new path on the **Installation Location** line. -6. On the initial **Create New Management Database** page, configure the **Microsoft SQL Server instance** and **Management Server database** by selecting the appropriate option below. +7. On the initial **Create New Management Database** page, configure the **Microsoft SQL Server instance** and **Management Server database** by selecting the appropriate option below. | Method | What you need to do | | - | - | | You are using a custom Microsoft SQL Server instance. | Select **Use the custom instance**, and type the name of the instance.
Use the format **INSTANCENAME**. The assumed installation location is the local computer.
Not supported: A server name using the format **ServerName**\\**INSTANCE**.| | You are using a custom database name. | Select **Custom configuration** and type the database name.
The database name must be unique, or the installation will fail.| -7. On the **Configure** page, accept the default value **Use this local computer**. +8. On the **Configure** page, accept the default value **Use this local computer**. - > [!NOTE] - > If you are installing the Management server and Management database side by side, some options on this page are not available. In this case, the appropriate options are selected by default and cannot be changed. + >**Note** If you are installing the Management server and Management database side by side, some options on this page are not available. In this case, the appropriate options are selected by default and cannot be changed. -8. On the initial **Create New Reporting Database** page, configure the **Microsoft SQL Server instance** and **Reporting Server database** by selecting the appropriate option below. +9. On the initial **Create New Reporting Database** page, configure the **Microsoft SQL Server instance** and **Reporting Server database** by selecting the appropriate option below. | Method | What you need to do | | - | - | @@ -64,21 +69,21 @@ Use the following procedure to install the App-V server.. | You are using a custom database name. | Select **Custom configuration** and type the database name.
The database name must be unique, or the installation will fail.| -9. On the **Configure** page, accept the default value: **Use this local computer**. +10. On the **Configure** page, accept the default value: **Use this local computer**. - > [!NOTE] + >**Note** > If you are installing the Management server and Management database side by side, some options on this page are not available. In this case, the appropriate options are selected by default and cannot be changed. -10. On the **Configure** (Management Server Configuration) page, specify the following: +11. On the **Configure** (Management Server Configuration) page, specify the following: | Item to configure | Description and examples | | - | - | - Type the AD group with sufficient permissions to manage the App-V environment. | Example: MyDomain\MyUser
After installation, you can add additional users or groups by using the Management console. However, global security groups and Active Directory Domain Services (AD DS) distribution groups are not supported. You must use Domain local or Universal groups are required to perform this action.| - | **Website name**: Specify the custom name that will be used to run the publishing service.
If you do not have a custom name, do not make any changes.| + | Type the AD group with sufficient permissions to manage the App-V environment. | Example: MyDomain\MyUser
After installation, you can add users or groups on the management console. However, global security groups and Active Directory Domain Services (AD DS) distribution groups are not supported. You must use Domain local or Universal groups to perform this action.| + | **Website name**: Specify the custom name that will be used to run the publishing service.
| If you do not have a custom name, do not make any changes.| |**Port binding**: Specify a unique port number that will be used by App-V. | Example: **12345**
Ensure that the port specified is not being used by another website. | -11. On the **Configure Publishing Server Configuration** page, specify the following: +12. On the **Configure Publishing Server Configuration** page, specify the following: | Item to configure | Description and examples | | - | - | @@ -86,16 +91,16 @@ Use the following procedure to install the App-V server.. | **Website name**: Specify the custom name that will be used to run the publishing service.| If you do not have a custom name, do not make any changes. | | **Port binding**: Specify a unique port number that will be used by App-V. | Example: 54321
Ensure that the port specified is not being used by another website. | -12. On the **Reporting Server** page, specify the following: +13. On the **Reporting Server** page, specify the following: | Item to configure | Description and examples | | - | - | | **Website name**: Specify the custom name that will be used to run the Reporting Service. | If you do not have a custom name, do not make any changes. | | **Port binding**: Specify a unique port number that will be used by App-V. | Example: 55555
Ensure that the port specified is not being used by another website. | -13. To start the installation, click **Install** on the **Ready** page, and then click **Close** on the **Finished** page. +14. To start the installation, click **Install** on the **Ready** page, and then click **Close** on the **Finished** page. -14. To verify that the setup completed successfully, open a web browser, and type the following URL: +15. To verify that the setup completed successfully, open a web browser, and type the following URL: **http://\<_Management server machine name_\>:\<_Management service port number_\>/console.html**. diff --git a/windows/manage/appv-deploying-appv.md b/windows/manage/appv-deploying-appv.md index 4afd68b171..14a78375a1 100644 --- a/windows/manage/appv-deploying-appv.md +++ b/windows/manage/appv-deploying-appv.md @@ -8,16 +8,16 @@ ms.sitesec: library ms.prod: w10 --- -# Deploying App-V +# Deploying App-V for Windows 10 -App-V supports a number of different deployment options. This section of the App-V Administrator’s Guide includes information you should consider about the deployment of App-V and step-by-step procedures to help you successfully perform the tasks that you must complete at different stages of your deployment. +App-V supports a number of different deployment options. Review this topic for information about the tasks that you must complete at different stages in your deployment. ## App-V Deployment Information - [Deploying the App-V Sequencer and Client](appv-deploying-the-appv-sequencer-and-client.md) - This section describes how to install the App-V sequencer which is used to virtualize applications, and the App-V client which runs on target computers to facilitate virtualized packages. + This section describes how to install the App-V sequencer, which is used to virtualize applications, and how to enable the App-V client, which runs on target computers to facilitate virtualized packages. - [Deploying the App-V Server](appv-deploying-the-appv-server.md) diff --git a/windows/manage/appv-deploying-the-appv-server.md b/windows/manage/appv-deploying-the-appv-server.md index 309a23843c..60f2618aad 100644 --- a/windows/manage/appv-deploying-the-appv-server.md +++ b/windows/manage/appv-deploying-the-appv-server.md @@ -1,6 +1,6 @@ --- title: Deploying the App-V Server (Windows 10) -description: Deploying the App-V Server +description: Deploying the App-V Server in App-V for Windows 10 author: MaggiePucciEvans ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy @@ -8,29 +8,36 @@ ms.sitesec: library ms.prod: w10 --- -# Deploying the App-V Server +# Deploying the App-V server -You can install the App-V server features by using different deployment configurations, which are described in this topic. Before you install the server features, review the server section of [App-V Security Considerations](appv-security-considerations.md). +Applies to: Windows 10, version 1607 -For information about deploying the App-V Server, see [About App-V](appv-about-appv.md). +>**Note** If you plan to use the App-V server components in your deployment, note that they reference App-V 5.x. This is because the App-V server components have not changed in App-V for Windows 10. + +You can install the Application Virtualization (App-V) server components using different deployment configurations, which are described in this topic. Before you install the server features, review the server section of [App-V Security Considerations](appv-security-considerations.md). + +For information about deploying App-V for Windows 10, see [About App-V](appv-about-appv.md). >**Important**
Before you install and configure the App-V servers, you must specify a port where each component will be hosted. You must also add the associated firewall rules to allow incoming requests to access the specified ports. The installer does not modify firewall settings. ## Download and install App-V server components +>**Note**
+If you're already using App-V 5.x, you don't need to re-deploy the App-V server components as they haven't changed since App-V 5.0 was released. + App-V offers the following five server components, each of which serves a specific purpose in an App-V environment. - **Management server.** Use the App-V management server and console to manage your App-V infrastructure. See [Administering App-V with the management console](appv-administering-virtual-applications-with-the-management-console.md) for more information about the management server. - >**Note**
If you are using App-V with your electronic software distribution solution, you don’t need to use the management server and console. However, you can still take advantage of the reporting and streaming capabilities in App-V. + >**Note**
If you are using App-V with your electronic software distribution solution, you don’t need to use the management server and console. However, you may want to take advantage of the reporting and streaming capabilities in App-V. -- **Management database.** Use the App-V management database to facilitate database pre-deployments for App-V management. See [How to deploy the App-V server components](appv-deploy-the-appv-server.md) for more information about the management database. +- **Management database.** Use the App-V management database to facilitate database pre-deployments for App-V management. See [How to Deploy the App-V Server](appv-deploy-the-appv-server.md) for more information about the management database. - **Publishing server.** Use the App-V publishing server to host and stream virtual applications. The publishing server supports the HTTP and HTTPS protocols and does not require a database connection. See [How to install the App-V publishing server](appv-install-the-publishing-server-on-a-remote-computer.md) for more information about configuring the publishing server. - **Reporting server.** Use the App-V reporting server to generate reports that help you manage your App-V infrastructure. The reporting server requires a connection to the reporting database. See [About App-V reporting](appv-reporting.md) for more information about the reporting capabilities in App-V. -- **Reporting database.** Use the App-V reporting database to facilitate database pre-deployments for App-V reporting. See [How to deploy the App-V server](appv-deploy-the-appv-server.md) for more information about the reporting database. +- **Reporting database.** Use the App-V reporting database to facilitate database pre-deployments for App-V reporting. See [How to Deploy the App-V Server](appv-deploy-the-appv-server.md) for more information about the reporting database. All five App-V server components are included in the Microsoft Desktop Optimization Pack (MDOP) 2015 ISO package, which can be downloaded from: @@ -38,8 +45,6 @@ All five App-V server components are included in the Microsoft Desktop Optimizat - The [Volume Licensing Service Center](https://www.microsoft.com/en-us/licensing/default.aspx) if you're using [Windows 10 for Enterprise or Education](https://www.microsoft.com/en-us/WindowsForBusiness/windows-product-home). - >**Note**
If you're already using App-V 5.x, you don't need to re-deploy the App-V server components as they haven't changed since App-V 5.0 was released. - In large organizations, you might want to install more than one instance of the server components to get: - Fault tolerance for situations when one of the servers is unavailable. @@ -49,14 +54,14 @@ In large organizations, you might want to install more than one instance of the - Scalability to support a high load. For example, you can install additional servers behind a network load balancer. ## App-V standalone deployment -The App-V standalone deployment provides a good topology for a small deployment or a test environment. When you use this type of implementation, all server components are deployed to a single computer. The services and associated databases will compete for the resources on the computer that runs the App-V components. Therefore, you should not use this topology for larger deployments. +The App-V standalone deployment provides a good topology for a small deployment or a test environment. When you use this type of implementation, all server components are installed on a single computer. The services and associated databases will compete for the resources on the computer that runs the App-V components. Therefore, you should not use this strategy for larger deployments. - [How to Deploy the App-V Server](appv-deploy-the-appv-server.md) - [How to Deploy the App-V Server Using a Script](appv-deploy-the-appv-server-with-a-script.md) ## App-V Server distributed deployment -The distributed deployment topology can support a large App-V client base and it allows you to more easily manage and scale your environment. When you use this type of deployment, the App-V Server components are deployed across multiple computers, based on the structure and requirements of the organization. +The distributed deployment topology can support a large App-V client base and it allows you to more easily manage and scale your environment. When you use this type of deployment, the App-V server components are deployed across multiple computers, based on the structure and requirements of the organization. - [How to Install the Management and Reporting Databases on Separate Computers from the Management and Reporting Services](appv-install-the-management-and-reporting-databases-on-separate-computers.md) @@ -97,7 +102,7 @@ The reporting information will be maintained until it is successfully sent to th If you want to retrieve report information, you must use Microsoft SQL Server Reporting Services (SSRS) which is available with Microsoft SQL. SSRS is not installed when you install the App-V reporting server and it must be deployed separately to generate the associated reports. -For more information, see [About App-V Reporting](appv-reporting.md) and [How to Enable Reporting on the App-V Client by Using PowerShell](appv-enable-reporting-on-the-appv-client-with-powershell.md). +For more information, see [About App-V Reporting](appv-reporting.md) and [How to Enable Reporting on the App-V Client by Using PowerShell](appv-enable-reporting-on-the-appv-client-with-powershell.md). ## Other resources for the App-V server - [Deploying App-V](appv-deploying-appv.md) diff --git a/windows/manage/appv-enable-the-app-v-desktop-client.md b/windows/manage/appv-enable-the-app-v-desktop-client.md index fe8bc4ffdc..2a92c9d953 100644 --- a/windows/manage/appv-enable-the-app-v-desktop-client.md +++ b/windows/manage/appv-enable-the-app-v-desktop-client.md @@ -8,15 +8,15 @@ ms.sitesec: library ms.prod: w10 --- -# Enable the App-V desktop client +# Enable the App-V in-box client The App-V client is the component that runs virtualized applications on user devices. The client enables users to interact with icons and file names to start virtualized applications. The client can also get virtual application content from the management server. -With Windows 10, the App-V client is installed automatically. You need to enable the client to allow user devices to access and run virtual applications. You can enable the client with the Group Policy editor or with Windows PowerShell. +With Windows 10, version 1607, the App-V client is installed automatically. You need to enable the client to allow user devices to access and run virtual applications. You can enable the client with the Group Policy editor or with Windows PowerShell. **To enable the App-V client with Group Policy:** -1. Open the device’s **Local Group Policy Editor**. +1. Open the device’s **Group Policy Editor**. 2. Navigate to **Computer Configuration** > **Administrative Templates** > **System** > **App-V**. @@ -28,11 +28,11 @@ With Windows 10, the App-V client is installed automatically. You need to enable 1. Open Windows PowerShell. -2. Type `Enable-Appv` and press Enter. +2. Type `Enable-Appv` and press ENTER. 3. Restart the device. -4. To verify that the App-V client is enabled on the device, enter **AppvClientEnabled** or **Get-AppvStatus** in Windows PowerShell. +4. To verify that the App-V client is enabled on the device, enter **Get-AppvStatus** in Windows PowerShell. See [Using the client management console](appv-using-the-client-management-console.md) for information about configuring the App-V client. diff --git a/windows/manage/appv-evaluating-appv.md b/windows/manage/appv-evaluating-appv.md index 20d2eba290..cdb5351de3 100644 --- a/windows/manage/appv-evaluating-appv.md +++ b/windows/manage/appv-evaluating-appv.md @@ -30,7 +30,7 @@ Use the following links for information about setting up the App-V sequencer and Use the following links for information about setting up the App-V server in your lab environment. -- [How to Deploy the App-V Server](appv-deploy-the-appv-server.md) +- [How to Deploy the App-V server](appv-deploy-the-appv-server.md) - [Administering App-V Virtual Applications by Using the Management Console](appv-administering-virtual-applications-with-the-management-console.md) diff --git a/windows/manage/appv-getting-started.md b/windows/manage/appv-getting-started.md index 2e33f78295..1923a4353a 100644 --- a/windows/manage/appv-getting-started.md +++ b/windows/manage/appv-getting-started.md @@ -9,9 +9,9 @@ ms.prod: w10 --- -# Getting Started with App-V +# Getting Started with App-V for Windows 10 -Microsoft Application Virtualization (App-V) enables organizations to deliver Win32 applications to users as virtual applications. Virtual applications are installed on centrally managed servers and delivered to users as a service – in real time and on as as-needed basis. Users launch virtual applications from familiar access points and interact with them as if they were installed locally. +Microsoft Application Virtualization (App-V) for Windows 10 enables organizations to deliver Win32 applications to users as virtual applications. Virtual applications are installed on centrally managed servers and delivered to users as a service – in real time and on as as-needed basis. Users launch virtual applications from familiar access points and interact with them as if they were installed locally. With the release of Windows 10, version 1607, App-V is included with the [Windows 10 for Enterprise edition](https://www.microsoft.com/en-us/WindowsForBusiness/windows-for-enterprise). If you are new to Windows 10 and App-V, you’ll need to download, activate, and install server- and client-side components to start delivering virtual applications to users. For information about what you need to know before getting started with App-V, see the [Application Virtualization (App-V) overview](appv-for-windows.md). @@ -30,11 +30,11 @@ To start using App-V to deliver virtual applications to users, you’ll need to | Component | What it does | Where to find it | |------------|--|------| -| App-V server components | App-V offers five server components that work together to allow you to host and publish virtual applications, generate usage reports, and manage your App-V environment. For information about the server components, see [Deploying the App-V Server](#_Deploying_the_App-V). | The App-V server components are included in the Microsoft Desktop Optimization Pack (MDOP) 2015 ISO package, which can be downloaded from the [MSDN (Microsoft Developer Network) subscriptions site](https://msdn.microsoft.com/en-us/subscriptions/downloads/default.aspx#FileId=65215).
You must have a MSDN subscription to download the MDOP ISO package.
See [Deploying the App-V Server](appv-deploying-the-appv-server.md) for more information about installing and using the server components. | +| App-V server components | App-V offers five server components that work together to allow you to host and publish virtual applications, generate usage reports, and manage your App-V environment. For information about the server components, see [Deploying the App-V Server](appv-deploying-the-appv-server.md).
**Note** If you're already using App-V 5.x, you don't need to re-deploy the App-V server components as they haven't changed since App-V 5.0 was released. | The App-V server components are included in the Microsoft Desktop Optimization Pack (MDOP) 2015 ISO package, which can be downloaded from:
- The [MSDN (Microsoft Developer Network) subscriptions site](https://msdn.microsoft.com/en-us/subscriptions/downloads/default.aspx#FileId=65215). You must have a MSDN subscription to download the MDOP ISO package from the MSDN subscriptions site.
- The [Volume Licensing Service Center](https://www.microsoft.com/en-us/licensing/default.aspx) if you're using [Windows 10 for Enterprise or Education](https://www.microsoft.com/en-us/WindowsForBusiness/windows-product-home).
See [Deploying the App-V Server](appv-deploying-the-appv-server.md) for more information about installing and using the server components. | App-V client and App-V Remote Desktop Services (RDS) client | The App-V client is the component that runs virtualized applications on user devices. The client enables users to interact with icons and file names to start virtualized applications. | The App-V client is automatically installed with Windows 10.
For information about enabling the client, see [Enable the App-V desktop client](appv-enable-the-app-v-desktop-client.md). | | App-V sequencer | Use the App-V sequencer to convert Win32 applications into virtual packages for deployment to user devices. Devices must be running the App-V client to allow users to interact with virtual applications. | Installed with the [Windows Assessment and Deployment kit (ADK) for Windows 10, version 1607](https://developer.microsoft.com/en-us/windows/hardware/windows-assessment-deployment-kit). | -For more information about these elements, see [High Level Architecture for App-V](appv-high-level-architecture.md). +For more information about these components, see [High Level Architecture for App-V](appv-high-level-architecture.md). If you are new to this product, we recommend that you read the documentation thoroughly. Before you deploy it to a production environment, we also recommend that you validate your deployment plan in a test network environment. You might also consider taking a class about relevant technologies. For information about Microsoft training opportunities, see the [Microsoft Training Overview](https://www.microsoft.com/en-us/learning/default.aspx). diff --git a/windows/manage/appv-install-the-appv-client-for-shared-content-store-mode.md b/windows/manage/appv-install-the-appv-client-for-shared-content-store-mode.md index fb6da496d4..f02ef3fd54 100644 --- a/windows/manage/appv-install-the-appv-client-for-shared-content-store-mode.md +++ b/windows/manage/appv-install-the-appv-client-for-shared-content-store-mode.md @@ -12,7 +12,7 @@ ms.prod: w10 # How to Install the App-V Client for Shared Content Store Mode -Use the following procedure to install the Microsoft Application Virtualization (App-V) client so that it uses the App-V Shared Content Store (SCS) mode. You should ensure that all required prerequisites are installed on the computer you plan to install to. Use the following link to see [App-V Prerequisites](appv-prerequisites.md). +Use the following procedure to install the Microsoft Application Virtualization (App-V) client so that it uses the App-V Shared Content Store (SCS) mode. **Enable the App-V client for SCS mode** diff --git a/windows/manage/appv-maintaining-appv.md b/windows/manage/appv-maintaining-appv.md index 6cf35b1731..487547914c 100644 --- a/windows/manage/appv-maintaining-appv.md +++ b/windows/manage/appv-maintaining-appv.md @@ -12,19 +12,18 @@ ms.prod: w10 # Maintaining App-V -After you have completed all the necessary planning, and then deployment of App-V, you can use the following information to maintain the App-V infrastructure. +After you have deployed App-V for Windows 10, you can use the following information to maintain the App-V infrastructure. -## Move the App-V Server +## Moving the App-V server - -The App-V server connects to the App-V database. Therefore you can install the management component to any computer on the network and then connect it to the App-V database. +The App-V server connects to the App-V database. Therefore you can install the management component on any computer on the network and then connect it to the App-V database. [How to Move the App-V Server to Another Computer](appv-move-the-appv-server-to-another-computer.md) -## Determine if an App-V Application is Running Virtualized +## Determine if an App-V Application is Running Virtualized -Independent software vendors (ISV) who want to determine if an application is running virtualized with App-V or above, 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. +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. diff --git a/windows/manage/appv-migrating-to-appv-from-a-previous-version.md b/windows/manage/appv-migrating-to-appv-from-a-previous-version.md index 87958fb0dd..c6ff02b2cb 100644 --- a/windows/manage/appv-migrating-to-appv-from-a-previous-version.md +++ b/windows/manage/appv-migrating-to-appv-from-a-previous-version.md @@ -13,14 +13,13 @@ ms.prod: w10 With Microsoft Application Virtualization (App-V), you can migrate your existing App-V 4.6 or App-V 5.0 infrastructure to the more flexible, integrated, and easier to manage App-V infrastructure. -However, you cannot migrate directly from App-V 4.x to App-V, you must migrate to App-V 5.0 first. For more information on migrating from App-V 4.x to App-V 5.0, see [Migrating from a Previous Version](appv-migrating-to-appv-from-a-previous-version.md) +However, you cannot migrate directly from App-V 4.x to App-V for Windows 10—you must migrate to App-V 5.0 first. For more information on migrating from App-V 4.x to App-V 5.0, see [Migrating to App-V server from a Previous Version](https://technet.microsoft.com/en-us/itpro/mdop/appv-v5/migrating-to-app-v-51-from-a-previous-version) **Note** -App-V packages are exactly the same as App-V 5.0 packages. There has been no change in the package format between the versions and therefore, there is no need to convert App-V 5.0 packages to App-V packages. +Packages for App-V for Windows 10 are exactly the same as packages for App-V 5.0. There has been no change in the package format between the versions and therefore, there is no need to convert App-V 5.0 packages to App-V for Window 10 packages. -For more information about the differences between App-V 4.6 and App-V, see the **Differences between App-4.6 and App-V 5.0 section** of [About App-V 5.0](https://technet.microsoft.com/en-us/itpro/mdop/appv-v5/about-app-v-50). +For information about the differences between earlier versions of App-V, see the **Differences between App-4.6 and App-V 5.0 section** of [About App-V 5.0](https://technet.microsoft.com/en-us/itpro/mdop/appv-v5/about-app-v-50). - ## Improvements to the App-V Package Converter @@ -252,7 +251,7 @@ You must be running the latest version of App-V 4.6 to use coexistence mode. Ad -## Migrating the App-V Server Full Infrastructure +## Migrating the App-V server Server Full Infrastructure There is no direct method to upgrade to a full App-V infrastructure. Use the information in the following section for information about upgrading the App-V server. @@ -278,8 +277,8 @@ There is no direct method to upgrade to a full App-V infrastructure. Use the inf
[Enable the App-V desktop client](appv-enable-the-app-v-desktop-client.md).
Install App-V server.
[How to Deploy the App-V Server](appv-deploy-the-appv-server.md).
Install App-V server server.
[How to Deploy the App-V server Server](appv-deploy-the-appv-server.md).
Migrate existing packages.
If you plan to use the App-V management server, plan for the required roles.
[Planning for the App-V Server Deployment](appv-planning-for-appv-server-deployment.md)
[Planning for the App-V 5.1 Server Deployment](appv-planning-for-appv-server-deployment.md)
| Prerequisite | -Details | -
|---|---|
[Microsoft .NET Framework 4.5.1 (Web Installer)](http://www.microsoft.com//download/details.aspx?id=40773) |
-- |
[Windows PowerShell 3.0](http://www.microsoft.com/download/details.aspx?id=34595) - |
-Installing PowerShell 3.0 requires a restart. |
-
[KB2533623](http://support.microsoft.com/kb/2533623) |
-Applies to Windows 7 only: Download and install the KB. |
-
[Visual C++ Redistributable Packages for Visual Studio 2013](http://www.microsoft.com/download/details.aspx?id=40784) |
-- |
**C:\Program Files (x86)\Windows Kits\10\Microsoft Application Virtualization\Sequencer** -**Workaround**: Do one of the following: +4. Run the following command: -- Assign the package to groups containing only user accounts. This will ensure that the package’s custom configuration is stored in each user’s profile and will be applied correctly. + `Update-AppvPackageMsi -MsiPackage "
**C:\Program Files (x86)\Windows Kits\10** -- Create a new package with the custom configuration using the App-V sequencer. - -## Server files not deleted after new App-V for Windows server installation - - -If you uninstall the App-V 5.0 SP1 Server and then install the App-V Server, the installation fails, the wrong version of the Management server is installed, and an error message is returned. The issue occurs because the Server files are not being deleted when you uninstall App-V 5.0 SP1, so the installation process does an upgrade instead of a new installation. - -**Workaround**: Delete this registry key before you start installing App-V: - -Under HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Wow6432Node\\Microsoft\\Windows\\CurrentVersion\\Uninstall, locate and delete the installation GUID key that contains the DWORD value "DisplayName" with value data "Microsoft Application Virtualization (App-V) Server". This is the only key that should be deleted. - -## File type associations added manually are not saved correctly - - -File type associations added to an application package manually using the Shortcuts and FTAs tab at the end of the application upgrade wizard are not saved correctly. They will not be available to the App-V Client or to the 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. - -## 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. - - -To decrease the amount of data written to a client’s local disk, you can enable SCS mode on the App-V 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 - -## In the Management Console Add Package dialog box, the Browse button is not available when using Chrome or Firefox - - -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 - -## Upgrading App-V Management Server to 5.1 sometimes fails with the message “A database error occurred” - - -If you install the App-V 5.0 SP1 Management Server, and then try to upgrade to App-V 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. - -## Users cannot open a package in a user-published connection group if you add or remove an optional package - - -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 - - -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 not displayed properly in Sequencer - - -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. - -## InsertVersionInfo.sql script no longer required for the Management Database - - -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](https://support.microsoft.com/kb/3031340). - -**Important** -**Step 1** is not required for versions of App-V later than App-V 5.0 SP3. - - - -## Microsoft Visual Studio 2012 not supported - - -App-V does not support Visual Studio 2012. - -**Workaround**: None - -## Application filename restrictions for App-V Sequencer - - -The App-V Sequencer cannot sequence applications with filenames matching "CO_<x>" where x is any numeral. Error 0x8007139F will be generated. - -**Workaround**: Use a different filename ## Have a suggestion for App-V? - Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv). ## Related topics - [About App-V](appv-about-appv.md) - - - - - - - - - diff --git a/windows/manage/appv-reporting.md b/windows/manage/appv-reporting.md index a23ad9f73a..b76c62fad9 100644 --- a/windows/manage/appv-reporting.md +++ b/windows/manage/appv-reporting.md @@ -308,7 +308,7 @@ Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-micros ## Related topics -[Deploying the App-V Server](appv-deploying-the-appv-server.md) +[Deploying the App-V server](appv-deploying-the-appv-server.md) [How to install the Reporting Server on a Standalone Computer and Connect it to the Database](appv-install-the-reporting-server-on-a-standalone-computer.md) diff --git a/windows/manage/appv-security-considerations.md b/windows/manage/appv-security-considerations.md index 79d71d971a..0a114d5036 100644 --- a/windows/manage/appv-security-considerations.md +++ b/windows/manage/appv-security-considerations.md @@ -29,7 +29,7 @@ Effective as of June, 2014, the PackageStoreAccessControl (PSAC) feature that wa **Understand the security risks.** The most serious risk to App-V is that its functionality could be hijacked by an unauthorized user who could then reconfigure key data on App-V clients. The loss of App-V functionality for a short period of time due to a denial-of-service attack would not generally have a catastrophic impact. -**Physically secure your computers**. Security is incomplete without physical security. Anyone with physical access to an App-V server could potentially attack the entire client base. Any potential physical attacks must be considered high risk and mitigated appropriately. App-V servers should be stored in a physically secure server room with controlled access. Secure these computers when administrators are not physically present by having the operating system lock the computer, or by using a secured screen saver. +**Physically secure your computers**. Security is incomplete without physical security. Anyone with physical access to an App-V 5.1 server could potentially attack the entire client base. Any potential physical attacks must be considered high risk and mitigated appropriately. App-V 5.1 servers should be stored in a physically secure server room with controlled access. Secure these computers when administrators are not physically present by having the operating system lock the computer, or by using a secured screen saver. **Apply the most recent security updates to all computers**. To stay informed about the latest updates for operating systems, Microsoft SQL Server, and App-V, subscribe to the Security Notification service (
| Operating system | -Service pack | -System architecture | -
|---|---|---|
Windows 10, version 1511 |
-- | 32-bit or 64-bit |
-
Windows 10, version 1507 |
-- | 32-bit or 64-bit |
-
Windows 8.1 |
-- | 32-bit or 64-bit |
-
Windows 8 |
-- | 32-bit or 64-bit |
-
Windows /p> |
-SP1 |
-32-bit or 64-bit |
-
| Operating system | -Service Pack | -System architecture | -
|---|---|---|
Microsoft Windows Server 2016 |
-- | 64-bit |
-
Microsoft Windows Server 2012 R2 |
-- | 64-bit |
-
Microsoft Windows Server 2012 |
-- | 64-bit |
-
Microsoft Windows Server 2008 R2 |
-SP1 |
-64-bit |
-
| App-V Version | -System Center Configuration Manager 2007 | -System Center 2012 Configuration Manager | -System Center 2012 Configuration Manager SP1 | -System Center 2012 R2 Configuration Manager | -System Center 2012 R2 Configuration Manager SP1 | -System Center 2012 Configuration Manager SP2 | -System Center Configuration Manager Version 1511 | -
|---|---|---|---|---|---|---|---|
App-V 4.5 |
-R2 |
-No |
-No |
-No |
-No |
-No |
-No |
-
App-V 4.5 CU1 |
-R2 |
-No |
-No |
-No |
-No |
-No |
-No |
-
App-V 4.5 SP1 |
-R2 |
-No |
-No |
-No |
-No |
-No |
-No |
-
App-V 4.5 SP2 |
-R2 |
-No |
-No |
-No |
-No |
-No |
-No |
-
App-V 4.6 |
-R2, SP1 |
-No |
-No |
-No |
-No |
-No |
-No |
-
App-V 4.6 SP1 |
-R2, R3, SP2 |
-Yes |
-Yes |
-Yes |
-No |
-No |
-No |
-
App-V 4.6 SP2 |
-R2, R3, SP2 |
-Yes |
-Yes |
-Yes |
-No |
-No |
-No |
-
App-V 4.6 SP3 |
-R2, R3, SP2 |
-No |
-Yes |
-Yes |
-No |
-Yes |
-Yes |
-
App-V 5.0 |
-MSI-Wrapper-Only |
-No |
-Yes |
-Yes |
-Yes |
-Yes |
-Yes |
-
App-V 5.0 SP1 |
-MSI-Wrapper Only |
-No |
-Yes |
-Yes |
-Yes |
-Yes |
-Yes |
-
App-V 5.0 SP2 |
-MSI-Wrapper Only |
-No |
-2012 SP1 CU4 -App-V 5.0 HF5 or later |
-2012 R2 CU1 -App-V 5.0 HF5 or later |
-Yes |
-With App-V 5.0 SP2 HF5 or later |
-With App-V 5.0 SP2 HF5 or later |
-
App-V 5.0 SP2 HF4 |
-MSI-Wrapper Only |
-No |
-2012 SP1 CU4 -App-V 5.0 HF5 or later |
-2012 R2 CU1 -App-V 5.0 HF5 or later |
-Yes |
-Requires HF5 or later |
-Requires HF5 or later |
-
App-V 5.0 SP3 |
-MSI-Wrapper Only |
-No |
-2012 SP1 CU4 |
-2012 R2 CU1 |
-Yes |
-Yes |
-Yes |
-
App-V |
-MSI-Wrapper Only |
-No |
-2012 SP1 CU4 |
-2012 R2 CU1 |
-Yes |
-Yes |
-Yes |
-