mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-07 18:17:22 +00:00
updating for Windows 10, version 1607
This commit is contained in:
Brian Lich
parent
a4202ede0c
commit
5bfc4eaed0
@ -8,30 +8,20 @@ ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# How to Connect to the Management Console
|
||||
|
||||
|
||||
Use the following procedure to connect to the App-V Management Console.
|
||||
|
||||
**To connect to the App-V Management Console**
|
||||
|
||||
1. Open Internet Explorer browser and type the address for the App-V. For example, **http://<Management server name>:<Management service port number>/Console.html**.
|
||||
1. Open Internet Explorer browser and type the address for the App-V. For example, **http://\<_management server name_\>:\<_management service port number_\>/console.html**.
|
||||
|
||||
2. To view different sections of the console, click the desired section in the navigation pane.
|
||||
|
||||
**Have a suggestion for App-V**? Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). **Got an App-V issue?** Use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
## Have a suggestion for App-V?
|
||||
|
||||
Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). **Got an App-V issue?** Use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[Operations for App-V](appv-operations.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
- [Operations for App-V](appv-operations.md)
|
||||
|
||||
@ -8,42 +8,19 @@ ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
# How to deploy App-V packages using electronic software distribution
|
||||
|
||||
# How to deploy App-V Packages Using Electronic Software Distribution
|
||||
|
||||
|
||||
You can use an electronic software distribution (ESD) system to deploy App-V virtual applications to App-V clients. For details, see the documentation available with the ESD you are using.
|
||||
You can use an electronic software distribution (ESD) system to deploy App-V virtual applications to App-V clients.
|
||||
|
||||
For component requirements and options for using an ESD to deploy App-V packages, see [Planning to Deploy App-V with an Electronic Software Distribution System](appv-planning-to-deploy-appv-with-electronic-software-distribution-solutions.md).
|
||||
|
||||
Use one of the following methods to publish packages to App-V client computers with an ESD:
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Method</th>
|
||||
<th align="left">Description</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Functionality provided by a third-party ESD</p></td>
|
||||
<td align="left"><p>Use the functionality in a third-party ESD.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Stand-alone Windows Installer</p></td>
|
||||
<td align="left"><p>Install the application on the target client computer by using the associated Windows Installer (.msi) file that is created when you initially sequence an application. The Windows Installer file contains the associated App-V package file information used to configure a package and copies the required package files to the client.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>PowerShell</p></td>
|
||||
<td align="left"><p>Use PowerShell cmdlets to deploy virtualized applications. For more information about using PowerShell and App-V, see [Administering App-V by Using PowerShell](appv-administering-appv-with-powershell.md).</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
| Method | Description |
|
||||
| - | - |
|
||||
| Functionality provided by a third-party ESD | Use the functionality in a third-party ESD.|
|
||||
| Stand-alone Windows Installer | Install the application on the target client computer by using the associated Windows Installer (.msi) file that is created when you initially sequence an application. The Windows Installer file contains the associated App-V package file information used to configure a package and copies the required package files to the client. |
|
||||
| Windows PowerShell | Use Windows PowerShell cmdlets to deploy virtualized applications. For more information about using PowerShell and App-V, see [Administering App-V by using Windows PowerShell](appv-administering-appv-with-powershell.md).|
|
||||
|
||||
|
||||
|
||||
@ -55,20 +32,10 @@ Use one of the following methods to publish packages to App-V client computers w
|
||||
|
||||
3. After you create the virtual application, deploy the package by using your ESD solution.
|
||||
|
||||
If you are using System Center Configuration Manager, start by reviewing [Introduction to Application Management in Configuration Manager](http://go.microsoft.com/fwlink/?LinkId=281816) for information about using App-V and System Center 2012 Configuration Manager.
|
||||
## Have a suggestion for App-V?
|
||||
|
||||
**Have a suggestion for App-V**? Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). **Got an App-V issue?** Use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). **Got an App-V issue?** Use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[Operations for App-V](appv-operations.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
- [Operations for App-V](appv-operations.md)
|
||||
|
||||
@ -8,15 +8,15 @@ ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
# How to Deploy the App-V Server
|
||||
# How to Deploy the App-V server
|
||||
|
||||
Use the following procedure to install the Microsoft Application Virtualization (App-V) server. For information about deploying the App-V Server, see [About App-V](appv-about-appv.md#bkmk-migrate-to-51).
|
||||
Use the following procedure to install the App-V server..
|
||||
|
||||
**Before you start:**
|
||||
|
||||
- Ensure that you’ve installed prerequisite software. See [App-V Prerequisites](appv-prerequisites.md).
|
||||
|
||||
- Review the server section of [App-V Security Considerations](appv-security-considerations.md).
|
||||
- Review the server section of [App-V security considerations](appv-security-considerations.md).
|
||||
|
||||
- Specify a port where each component will be hosted.
|
||||
|
||||
@ -34,217 +34,70 @@ Use the following procedure to install the Microsoft Application Virtualization
|
||||
|
||||
4. On the **Feature Selection** page, select all of the following components.
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Component</th>
|
||||
<th align="left">Description</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Management server</p></td>
|
||||
<td align="left"><p>Provides overall management functionality for the App-V infrastructure.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Management database</p></td>
|
||||
<td align="left"><p>Facilitates database predeployments for App-V management.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Publishing server</p></td>
|
||||
<td align="left"><p>Provides hosting and streaming functionality for virtual applications.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Reporting server</p></td>
|
||||
<td align="left"><p>Provides App-V reporting services.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Reporting database</p></td>
|
||||
<td align="left"><p>Facilitates database predeployments for App-V reporting.</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
| Component | Description |
|
||||
| - | - |
|
||||
| Management server | Provides overall management functionality for the App-V infrastructure. |
|
||||
| Management database | Facilitates database predeployments for App-V management. |
|
||||
| Publishing server | Provides hosting and streaming functionality for virtual applications. |
|
||||
| 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 initial **Create New Management Database** page, configure the **Microsoft SQL Server instance** and **Management Server database** by selecting the appropriate option below.
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Method</th>
|
||||
<th align="left">What you need to do</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>You are using a custom Microsoft SQL Server instance.</p></td>
|
||||
<td align="left"><p>Select <strong>Use the custom instance</strong>, and type the name of the instance.</p>
|
||||
<p>Use the format <strong>INSTANCENAME</strong>. The assumed installation location is the local computer.</p>
|
||||
<p>Not supported: A server name using the format <strong>ServerName</strong>\<strong>INSTANCE</strong>.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>You are using a custom database name.</p></td>
|
||||
<td align="left"><p>Select <strong>Custom configuration</strong> and type the database name.</p>
|
||||
<p>The database name must be unique, or the installation will fail.</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
| 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.<br/>Use the format **INSTANCENAME**. The assumed installation location is the local computer.<br/>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.<br/>The database name must be unique, or the installation will fail.|
|
||||
|
||||
7. 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.
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Method</th>
|
||||
<th align="left">What you need to do</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>You are using a custom Microsoft SQL Server instance.</p></td>
|
||||
<td align="left"><p>Select <strong>Use the custom instance</strong>, and type the name of the instance.</p>
|
||||
<p>Use the format <strong>INSTANCENAME</strong>. The assumed installation location is the local computer.</p>
|
||||
<p>Not supported: A server name using the format <strong>ServerName</strong>\<strong>INSTANCE</strong>.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>You are using a custom database name.</p></td>
|
||||
<td align="left"><p>Select <strong>Custom configuration</strong> and type the database name.</p>
|
||||
<p>The database name must be unique, or the installation will fail.</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
| 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.<br/>Use the format **INSTANCENAME**. The assumed installation location is the local computer.<br/>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.<br/>The database name must be unique, or the installation will fail.|
|
||||
|
||||
|
||||
|
||||
9. 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.
|
||||
|
||||
|
||||
|
||||
10. On the **Configure** (Management Server Configuration) page, specify the following:
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Item to configure</th>
|
||||
<th align="left">Description and examples</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Type the AD group with sufficient permissions to manage the App-V environment.</p></td>
|
||||
<td align="left"><p>Example: MyDomain\MyUser</p>
|
||||
<p>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 <strong>Domain local</strong> or <strong>Universal</strong> groups are required to perform this action.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p><strong>Website name</strong>: Specify the custom name that will be used to run the publishing service.</p></td>
|
||||
<td align="left"><p>If you do not have a custom name, do not make any changes.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p><strong>Port binding</strong>: Specify a unique port number that will be used by App-V.</p></td>
|
||||
<td align="left"><p>Example: <strong>12345</strong></p>
|
||||
<p>Ensure that the port specified is not being used by another website.</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
| Item to configure | Description and examples |
|
||||
| - | - |
|
||||
Type the AD group with sufficient permissions to manage the App-V environment. | Example: MyDomain\MyUser<br/>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 <strong>Domain local</strong> or <strong>Universal</strong> groups are required to perform this action.|
|
||||
| **Website name**: Specify the custom name that will be used to run the publishing service.<br/>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**<br/>Ensure that the port specified is not being used by another website. |
|
||||
|
||||
|
||||
11. On the **Configure Publishing Server Configuration** page, specify the following:
|
||||
|
||||
11. On the **Configure** **Publishing Server Configuration** page, specify the following:
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Item to configure</th>
|
||||
<th align="left">Description and examples</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Specify the URL for the management service.</p></td>
|
||||
<td align="left"><p>Example: http://localhost:12345</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p><strong>Website name</strong>: Specify the custom name that will be used to run the publishing service.</p></td>
|
||||
<td align="left"><p>If you do not have a custom name, do not make any changes.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p><strong>Port binding</strong>: Specify a unique port number that will be used by App-V.</p></td>
|
||||
<td align="left"><p>Example: 54321</p>
|
||||
<p>Ensure that the port specified is not being used by another website.</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
| Item to configure | Description and examples |
|
||||
| - | - |
|
||||
| Specify the URL for the management service. | Example: http://localhost:12345 |
|
||||
| **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<br/>Ensure that the port specified is not being used by another website. |
|
||||
|
||||
12. On the **Reporting Server** page, specify the following:
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Item to configure</th>
|
||||
<th align="left">Description and examples</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p><strong>Website name</strong>: Specify the custom name that will be used to run the Reporting Service.</p></td>
|
||||
<td align="left"><p>If you do not have a custom name, do not make any changes.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p><strong>Port binding</strong>: Specify a unique port number that will be used by App-V.</p></td>
|
||||
<td align="left"><p>Example: 55555</p>
|
||||
<p>Ensure that the port specified is not being used by another website.</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
| 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<br/>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 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**.
|
||||
**http://\<_Management server machine name_\>:\<_Management service port number_\>/console.html**.
|
||||
|
||||
Example: **http://localhost:12345/console.html**. If the installation succeeded, the App-V Management console is displayed with no errors.
|
||||
|
||||
@ -254,10 +107,10 @@ Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-micros
|
||||
|
||||
## Related topics
|
||||
|
||||
[Deploying App-V](appv-deploying-appv.md)
|
||||
- [Deploying App-V](appv-deploying-appv.md)
|
||||
|
||||
[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)
|
||||
- [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)
|
||||
|
||||
[How to Install the Publishing Server on a Remote Computer](appv-install-the-publishing-server-on-a-remote-computer.md)
|
||||
- [How to Install the Publishing Server on a Remote Computer](appv-install-the-publishing-server-on-a-remote-computer.md)
|
||||
|
||||
[How to Deploy the App-V Server Using a Script](appv-deploy-the-appv-server-with-a-script.md)
|
||||
- [How to Deploy the App-V Server Using a Script](appv-deploy-the-appv-server-with-a-script.md)
|
||||
|
||||
@ -18,7 +18,7 @@ With Windows 10, the App-V client is installed automatically. You need to enable
|
||||
|
||||
1. Open the device’s **Local Group Policy Editor**.
|
||||
|
||||
2. Navigate to **Computer Configuration** > **Administrative Templates** > **System** > **App-V**.
|
||||
2. Navigate to **Computer Configuration** > **Administrative Templates** > **System** > **App-V**.
|
||||
|
||||
3. Run **Enables App-V Client** and then select **Enabled** on the screen that appears.
|
||||
|
||||
|
||||
@ -14,40 +14,16 @@ ms.prod: w10
|
||||
|
||||
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).
|
||||
|
||||
**Note**
|
||||
Before performing this procedure if necessary uninstall any existing version of the App-V client.
|
||||
**Enable the App-V client for SCS mode**
|
||||
|
||||
|
||||
1. In the Group Policy Management Console, navigate to **Computer Configuration** > **Administrative Templates** > **System** > **App-V** > **Streaming**.
|
||||
|
||||
For more information about SCS mode, see [Shared Content Store in Microsoft App-V 5.0 – Behind the Scenes](http://go.microsoft.com/fwlink/?LinkId=316879) (http://go.microsoft.com/fwlink/?LinkId=316879).
|
||||
2. Enable the **Set the Shared Content Mode (SCS) mode** setting.
|
||||
|
||||
**Install and configure the App-V client for SCS mode**
|
||||
## Have a suggestion for App-V?
|
||||
|
||||
1. Copy the App-V client installation files to the computer on which it will be installed. Open a command line and from the directory where the installation files are saved type one of the following options depending on the version of the client you are installing:
|
||||
|
||||
- To install the RDS version of the App-V client type: **appv\_client\_setup\_rds.exe /SHAREDCONTENTSTOREMODE=1 /q**
|
||||
|
||||
- To install the standard version of the App-V client type: **appv\_client\_setup.exe /SHAREDCONTENTSTOREMODE=1 /q**
|
||||
|
||||
**Important**
|
||||
You must perform a silent installation or the installation will fail.
|
||||
|
||||
|
||||
|
||||
2. After you have completed the installation you can deploy packages to the computer running the client and all package contents will be streamed across the network.
|
||||
|
||||
**Have a suggestion for App-V**? Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). **Got an App-V issue?** Use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). **Got an App-V issue?** Use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[Deploying the App-V Sequencer and Client](appv-deploying-the-appv-sequencer-and-client.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
- [Deploying the App-V Sequencer and Client](appv-deploying-the-appv-sequencer-and-client.md)
|
||||
|
||||
@ -15,18 +15,19 @@ Use the App-V Sequencer to convert Win32 applications into virtual packages for
|
||||
|
||||
The App-V Sequencer is included in the Windows 10 Assessment and Deployment Kit (Windows ADK).
|
||||
|
||||
**Note** The computer that will run the sequencer must not have the App-V client enabled on it. As a best practice, choose a computer with the same hardware and software configurations as the computers that will run the virtual applications. The sequencing process is resource intensive, so make sure that the computer that runs the Sequencer has plenty of memory, a fast processor, and a fast hard drive.
|
||||
> [!NOTE]
|
||||
> The computer that will run the sequencer must not have the App-V client enabled on it. As a best practice, choose a computer with the same hardware and software configurations as the computers that will run the virtual applications. The sequencing process is resource intensive, so make sure that the computer that runs the Sequencer has plenty of memory, a fast processor, and a fast hard drive.
|
||||
|
||||
To install the App-V Sequencer:
|
||||
|
||||
1. Go to [Download the Windows ADK](https://developer.microsoft.com/en-us/windows/hardware/windows-assessment-deployment-kit).
|
||||
1. Go to [Download the Windows ADK](https://developer.microsoft.com/windows/hardware/windows-assessment-deployment-kit).
|
||||
|
||||
2. Click or press the **Get Windows ADK for Windows 10** button on the page to start the ADK installer. On the screen pictured below, select **Microsoft Application Virtualization (App-V) Sequencer** and then click or press **Install**.
|
||||
|
||||
|
||||
|
||||
|
||||
3. To open the Sequencer, from the **Start** menu, select **Microsoft Application Virtualization Sequencer** .
|
||||
3. To open the Sequencer, from the **Start** menu, select **Microsoft Application Virtualization (App-V) Sequencer** .
|
||||
|
||||
See [Creating and managing virtual applications](appv-creating-and-managing-virtualized-applications.md) and the [Application Virtualization Sequencing Guide](http://download.microsoft.com/download/F/7/8/F784A197-73BE-48FF-83DA-4102C05A6D44/App-V%205.0%20Sequencing%20Guide.docx) for information about creating virtual applications with the Sequencer.
|
||||
|
||||
|
||||
@ -8,41 +8,16 @@ ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
# How to Modify App-V client configuration using the ADMX template and Group Policy
|
||||
|
||||
# How to Modify App-V Client Configuration Using the ADMX Template and Group Policy
|
||||
You can use Group Policy to configure App-V client settings by using the Group Policy Management Console under **Computer Configuration** > **Policies** > **Administrative Templates** > **System** > **App-V**.
|
||||
|
||||
## Have a suggestion for App-V?
|
||||
|
||||
Use the Microsoft Application Virtualization (App-V) ADMX template to configure App-V client settings using the ADMX Template and Group Policy.
|
||||
|
||||
**To modify App-V client configuration using Group Policy**
|
||||
|
||||
1. To modify the App-V client configuration, locate the **ADMXTemplate** files that are available with App-V.
|
||||
|
||||
**Note**
|
||||
Use the following link to download the App-V **ADMX Templates**: <http://go.microsoft.com/fwlink/p/?LinkId=393941>.
|
||||
|
||||
|
||||
|
||||
2. On the computer where you manage group Policy, typically the domain controller, copy the template **.admx** file to the following directory: **<Installation Drive> \\ Windows \\ PolicyDefinitions**.
|
||||
|
||||
Next, on the same computer, copy the **.adml** file to the following directory: **<InstallationDrive> \\ Windows \\ PolicyDefinitions \\ en-US**.
|
||||
|
||||
3. After you have copied the files open the Group Policy Management Console, to modify the policies associated with your App-V clients browse to **Computer Configuration** / **Policies** / **Administrative Templates** / **System** / **App-V**.
|
||||
|
||||
**Have a suggestion for App-V**? Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). **Got an App-V issue?** Use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). **Got an App-V issue?** Use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
|
||||
## Related topics
|
||||
|
||||
- [Deploying App-V](appv-deploying-appv.md)
|
||||
|
||||
[Deploying App-V](appv-deploying-appv.md)
|
||||
|
||||
[About Client Configuration Settings](appv-client-configuration-settings.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
- [About Client Configuration Settings](appv-client-configuration-settings.md)
|
||||
|
||||
@ -11,12 +11,10 @@ ms.prod: w10
|
||||
|
||||
# Planning for App-V
|
||||
|
||||
|
||||
Use this information to plan how to deploy Microsoft Application Virtualization (App-V) so that it does not disrupt your users or the network.
|
||||
Use this information to plan how to deploy App-V so that it does not disrupt your users or the network.
|
||||
|
||||
## Planning information
|
||||
|
||||
|
||||
- [Preparing Your Environment for App-V](appv-preparing-your-environment.md)
|
||||
|
||||
This section describes the computing environment requirements and installation prerequisites that should be planned for before beginning App-V setup.
|
||||
@ -31,15 +29,13 @@ Use this information to plan how to deploy Microsoft Application Virtualization
|
||||
|
||||
## 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).
|
||||
|
||||
## <a href="" id="other-resources-for-app-v-5-1-planning-"></a>Other resources for App-V Planning
|
||||
|
||||
## Other resources for App-V planning
|
||||
|
||||
- [Microsoft Application Virtualization Administrator's Guide](appv-microsoft-application-virtualization-administrators-guide.md)
|
||||
|
||||
- [Getting Started with App-V](appv-getting-started.md)
|
||||
- [Getting started with App-V](appv-getting-started.md)
|
||||
|
||||
- [Deploying App-V](appv-deploying-appv.md)
|
||||
|
||||
@ -47,13 +43,4 @@ Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-micros
|
||||
|
||||
- [Troubleshooting App-V](appv-troubleshooting.md)
|
||||
|
||||
- [Technical Reference for App-V](appv-technical-reference.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
- [Technical reference for App-V](appv-technical-reference.md)
|
||||
|
||||
@ -8,21 +8,19 @@ ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# Planning for the App-V Sequencer and Client Deployment
|
||||
|
||||
|
||||
Before you can start to use Microsoft Application Virtualization (App-V), you must install the App-V sequencer, the App-V client, and optionally the App-V shared content store. The following sections address planning for these installations.
|
||||
Before you can use App-V, you must install the App-V Sequencer, enable the App-V client, and optionally the App-V shared content store. The following sections address planning for these installations.
|
||||
|
||||
## Planning for App-V sequencer deployment
|
||||
## Planning for App-V Sequencer deployment
|
||||
|
||||
|
||||
App-V uses a process called sequencing to create virtualized applications and application packages. Sequencing requires the use of a computer that runs the App-V sequencer.
|
||||
App-V uses a process called sequencing to create virtualized applications and application packages. Sequencing requires the use of a computer that runs the App-V Sequencer.
|
||||
|
||||
**Note**
|
||||
For information about the new functionality of App-V sequencer, see the **Sequencer Improvements** section of [About App-V](appv-about-appv.md).
|
||||
> [!NOTE]
|
||||
> For information about the new functionality of App-V sequencer, see the **Sequencer Improvements** section of [About App-V](appv-about-appv.md).
|
||||
|
||||
|
||||
|
||||
The computer that runs the App-V sequencer must meet the minimum system requirements. For a list of these requirements, see [App-V Supported Configurations](appv-supported-configurations.md).
|
||||
|
||||
@ -34,39 +32,22 @@ Ideally, you should install the sequencer on a computer running as a virtual mac
|
||||
|
||||
3. Take a “snapshot” of the environment.
|
||||
|
||||
**Important**
|
||||
You should have your corporate security team review and approve the sequencing process plan. For security reasons, you should keep the sequencer operations in a lab that is separate from the production environment. The separation arrangement can be as simple or as comprehensive as necessary, based on your business requirements. The sequencing computers must be able to connect to the corporate network to copy finished packages to the production servers. However, because the sequencing computers are typically operated without antivirus protection, they must not be on the corporate network unprotected. For example, you might be able to operate behind a firewall or on an isolated network segment. You might also be able to use virtual machines that are configured to share an isolated virtual network. Follow your corporate security policies to safely address these concerns.
|
||||
> [!IMPORTANT]
|
||||
>You should have your corporate security team review and approve the sequencing process plan. For security reasons, you should keep the sequencer operations in a lab that is separate from the production environment. The separation arrangement can be as simple or as comprehensive as necessary, based on your business requirements. The sequencing computers must be able to connect to the corporate network to copy finished packages to the production servers. However, because the sequencing computers are typically operated without antivirus protection, they must not be on the corporate network unprotected. For example, you might be able to operate behind a firewall or on an isolated network segment. You might also be able to use virtual machines that are configured to share an isolated virtual network. Follow your corporate security policies to safely address these concerns.
|
||||
|
||||
|
||||
|
||||
## Planning for App-V client deployment
|
||||
|
||||
|
||||
To run virtualized packages on target computers, you must install the App-V client on the target computers. The App-V client is the component that runs a virtualized application on a target computer. The client enables users to interact with icons and specific file types to start virtualized applications. The client also helps obtain application content from the management server and caches the content before the client starts the application. There are two different client types: the client for Remote Desktop Services, which is used on Remote Desktop Session Host (RD Session Host) server systems and the App-V client, which is used for all other computers.
|
||||
|
||||
The App-V client should be configured by using either the installer command line or by using a PowerShell script after the installation has been completed.
|
||||
|
||||
The settings must be defined carefully in advance in order to expedite the deployment of the App-V client software. This is especially important when you have computers in different offices where the clients must be configured to use different source locations.
|
||||
|
||||
You must also determine how you will deploy the client software. Although it is possible to deploy the client manually on each computer, most organizations prefer to deploy the client through an automated process. A larger organization might have an operational Electronic Software Distribution (ESD) system, which is an ideal client deployment system. If no ESD system exists, you can use your organization’s standard method of installing software. Possible methods include Group Policy or various scripting techniques. Depending on the quantity and disparate locations of your client computers, this deployment process can be complex. You must use a structured approach to ensure that all computers get the client installed with the correct configuration.
|
||||
In Windows 10, version 1607, the App-V client is included with the operating system. For more info, see [Enable the App-V desktop client](appv-enable-the-app-v-desktop-client.md).
|
||||
|
||||
For a list of the client minimum requirements see [App-V Prerequisites](appv-prerequisites.md).
|
||||
|
||||
## <a href="" id="bkmk-client-coexist"></a>Planning for App-V client coexistence
|
||||
|
||||
## Planning for the App-V Shared Content Store (SCS)
|
||||
|
||||
You can deploy the App-V client side by side with the App-V 4.6 client. Client coexistence requires that you add or publish virtualized applications by using either a deployment configuration file or a user configuration file, because there are certain settings in these configuration files that must be configured in order for App-V to function with App-V 4.6 clients. When a package is upgraded by using either the client or the server, the package must resubmit the configuration file. This is true for any package that has a corresponding configuration file, so it is not specific to client coexistence. However, if you do not submit the configuration file during the package upgrade, then the package state will not function as expected in coexistence scenarios.
|
||||
The App-V Shared Content Store mode allows the computer running the App-V client to run virtualized applications and none of the package contents is saved on the computer running the App-V client. Virtual applications are streamed to target computers only when requested by the client.
|
||||
|
||||
App-V dynamic configuration files customize a package for a specific user. You must create the dynamic user configuration (.xml) file or the dynamic deployment configuration file before you can use them. To create the file it requires an advanced manual operation.
|
||||
|
||||
When a dynamic user configuration file is used, none of the App-V information for the extension in the manifest file is used. This means that the dynamic user configuration file must include everything for the extension that is specific to App-V in the manifest file, as well as the changes that you want to make, such as, deletions and updates. For more information about how to create a custom configuration file, see [How to Create a Custom Configuration File by Using the App-V Management Console](appv-create-a-custom-configuration-file-with-the-management-console.md).
|
||||
|
||||
## <a href="" id="bkmk-plan-for-scs"></a>Planning for the App-V Shared Content Store (SCS)
|
||||
|
||||
|
||||
The App-V shared content store mode allows the computer running the App-V client to run virtualized applications and none of the package contents is saved on the computer running the App-V client. Virtual applications are streamed to target computers only when requested by the client.
|
||||
|
||||
The following list displays some of the benefits of using the App-V shared content store:
|
||||
The following list displays some of the benefits of using the App-V Shared Content Store:
|
||||
|
||||
- Reduced app-to-app and multi-user application conflicts and hence a reduced need for regression testing
|
||||
|
||||
@ -76,30 +57,16 @@ The following list displays some of the benefits of using the App-V shared conte
|
||||
|
||||
## 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).
|
||||
|
||||
## <a href="" id="other-resources-for-the-app-v-5-1-deployment-"></a>Other resources for the App-V deployment
|
||||
## Other resources for the App-V deployment
|
||||
|
||||
|
||||
[Planning to Deploy App-V](appv-planning-to-deploy-appv.md)
|
||||
- [Planning to Deploy App-V](appv-planning-to-deploy-appv.md)
|
||||
|
||||
## Related topics
|
||||
|
||||
- [How to Install the Sequencer](appv-install-the-sequencer.md)
|
||||
|
||||
[How to Install the Sequencer](appv-install-the-sequencer.md)
|
||||
|
||||
[How to Deploy the App-V Client](appv-deploy-the-appv-client.md)
|
||||
|
||||
[How to Deploy the App-V 4.6.x and the App-V Client on the Same Computer](appv-deploy-the-appv-46x-and-the-appv--51-client-on-the-same-computer.md)
|
||||
|
||||
[How to Install the App-V Client for Shared Content Store Mode](appv-install-the-appv-client-for-shared-content-store-mode.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
- [Enable the App-V desktop client](appv-enable-the-app-v-desktop-client.md)
|
||||
|
||||
- [How to Install the App-V Client for Shared Content Store Mode](appv-install-the-appv-client-for-shared-content-store-mode.md)
|
||||
|
||||
@ -8,55 +8,21 @@ ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# Planning to Deploy App-V with an Electronic Software Distribution System
|
||||
|
||||
# Planning to Deploy App-V with an electronic software distribution system
|
||||
|
||||
If you are using an electronic software distribution system to deploy App-V packages, review the following planning considerations. For information about using System Center Configuration Manager to deploy App-V, see [Introduction to Application Management in Configuration Manager](http://go.microsoft.com/fwlink/?LinkId=281816).
|
||||
|
||||
Review the following component and architecture requirements options that apply when you use an ESD to deploy App-V packages:
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Deployment requirement or option</th>
|
||||
<th align="left">Description</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>The App-V Management server, Management database, and Publishing server are not required.</p></td>
|
||||
<td align="left"><p>These functions are handled by the implemented ESD solution.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>You can deploy the App-V Reporting server and Reporting database side by side with the ESD.</p></td>
|
||||
<td align="left"><p>The side-by-side deployment lets you to collect data and generate reports.</p>
|
||||
<p>If you enable the App-V client to send report information, and you are not using the App-V Reporting server, the reporting data is stored in associated .xml files.</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
| Deployment requirement or option | Description |
|
||||
| - | - |
|
||||
| The App-V Management server, Management database, and Publishing server are not required. | These functions are handled by the implemented ESD solution. |
|
||||
| You can deploy the App-V Reporting server and Reporting database side by side with the ESD. | The side-by-side deployment lets you to collect data and generate reports.<br/>If you enable the App-V client to send report information, and you are not using the App-V Reporting server, the reporting data is stored in associated .xml files. |
|
||||
|
||||
## 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
|
||||
|
||||
|
||||
[Planning to Deploy App-V](appv-planning-to-deploy-appv.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
- [Planning to deploy App-V](appv-planning-to-deploy-appv.md)
|
||||
|
||||
@ -11,11 +11,9 @@ ms.prod: w10
|
||||
|
||||
# Planning to Deploy App-V
|
||||
|
||||
You should consider a number of different deployment configurations and prerequisites before you create your deployment plan for App-V. This section includes information that can help you gather the information that you must have to formulate a deployment plan that best meets your business requirements.
|
||||
|
||||
You should consider a number of different deployment configurations and prerequisites before you create your deployment plan for Microsoft Application Virtualization (App-V). This section includes information that can help you gather the information that you must have to formulate a deployment plan that best meets your business requirements.
|
||||
|
||||
## <a href="" id="---------app-v-5-1-supported-configurations"></a> App-V supported configurations
|
||||
|
||||
## App-V supported configurations
|
||||
|
||||
Describes the minimum hardware and operating system requirements for each App-V components. For information about software prerequisites that you must install before you install App-V, see [App-V Prerequisites](appv-prerequisites.md).
|
||||
|
||||
@ -23,72 +21,54 @@ Describes the minimum hardware and operating system requirements for each App-V
|
||||
|
||||
## App-V capacity planning
|
||||
|
||||
|
||||
Describes the available options for scaling your App-V deployment.
|
||||
|
||||
[App-V Capacity Planning](appv-capacity-planning.md)
|
||||
|
||||
## Planning for high availability with App-V
|
||||
|
||||
|
||||
Describes the available options for ensuring high availability of App-V databases and services.
|
||||
|
||||
[Planning for High Availability with App-V](appv-planning-for-high-availability-with-appv.md)
|
||||
|
||||
## Planning to Deploy App-V with an Electronic Software Distribution System
|
||||
|
||||
|
||||
Describes the options and requirements for deploying App-V with an electronic software distribution system.
|
||||
|
||||
[Planning to Deploy App-V with an Electronic Software Distribution System](appv-planning-to-deploy-appv-with-electronic-software-distribution-solutions.md)
|
||||
|
||||
## Planning for the App-V Server deployment
|
||||
|
||||
|
||||
Describes the planning considerations for the App-V Server components and their functions.
|
||||
|
||||
[Planning for the App-V Server Deployment](appv-planning-for-appv-server-deployment.md)
|
||||
|
||||
## Planning for the App-V Sequencer and Client deployment
|
||||
|
||||
|
||||
Describes the planning considerations for the App-V Client and for the Sequencer software, which you use to create virtual applications and application packages.
|
||||
|
||||
[Planning for the App-V Sequencer and Client Deployment](appv-planning-for-sequencer-and-client-deployment.md)
|
||||
|
||||
## Planning for migrating from a previous version of App-V
|
||||
|
||||
|
||||
Describes the recommended path for migrating from previous versions of App-V, while ensuring that existing server configurations, packages and clients continue to work in your new App-V environment.
|
||||
|
||||
[Planning for Migrating from a Previous Version of App-V](appv-planning-for-migrating-from-a-previous-version-of-appv.md)
|
||||
|
||||
## Planning for using App-V with Office
|
||||
|
||||
|
||||
Describes the requirements for using App-V with Office and explains the supported scenarios, including information about coexisting versions of Office.
|
||||
|
||||
[Planning for Using App-V with Office](appv-planning-for-using-appv-with-office.md)
|
||||
|
||||
## Planning to use folder redirection with App-V
|
||||
|
||||
|
||||
Explains how folder redirection works with App-V.
|
||||
|
||||
[Planning to Use Folder Redirection with App-V](appv-planning-folder-redirection-with-appv.md)
|
||||
|
||||
## <a href="" id="other-resources-for-app-v-5-1-planning-"></a>Other Resources for App-V Planning
|
||||
|
||||
## Other Resources for App-V Planning
|
||||
|
||||
- [Planning for App-V](appv-planning-for-appv.md)
|
||||
|
||||
- [Performance Guidance for Application Virtualization](appv-performance-guidance.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -8,41 +8,26 @@ ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# Preparing Your Environment for App-V
|
||||
|
||||
|
||||
There are a number of different deployment configurations and prerequisites that you must consider before you create your deployment plan for Microsoft Application Virtualization (App-V). This section includes information that can help you gather the information that you must have to formulate a deployment plan that best meets your business requirements.
|
||||
|
||||
## App-V prerequisites
|
||||
|
||||
|
||||
- [App-V Prerequisites](appv-prerequisites.md)
|
||||
|
||||
Lists the prerequisite software that you must install before installing App-V.
|
||||
|
||||
## App-V security considerations
|
||||
|
||||
|
||||
- [App-V Security Considerations](appv-security-considerations.md)
|
||||
|
||||
Describes accounts, groups, log files, and other considerations for securing your App-V environment.
|
||||
|
||||
## 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).
|
||||
|
||||
## <a href="" id="other-resources-for-app-v-5-1-planning-"></a>Other resources for App-V Planning
|
||||
|
||||
## Other resources for App-V planning
|
||||
|
||||
- [Planning for App-V](appv-planning-for-appv.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -11,39 +11,17 @@ ms.prod: w10
|
||||
|
||||
# How to Sequence a New Application with App-V
|
||||
|
||||
In Windows 10, version 1607, the App-V Sequencer is included with the Windows ADK. For more info on how to install the App-V Sequencer, see [Install the App-V Sequencer](appv-install-the-sequencer.md).
|
||||
|
||||
**To review or do before you start sequencing**
|
||||
|
||||
1. Determine the type of virtualized application package you want to create:
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Application type</th>
|
||||
<th align="left">Description</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Standard</p></td>
|
||||
<td align="left"><p>Creates a package that contains an application or a suite of applications. This is the preferred option for most application types.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Add-on or plug-in</p></td>
|
||||
<td align="left"><p>Creates a package that extends the functionality of a standard application, for example, a plug-in for Microsoft Excel. Additionally, you can use plug-ins for natively installed applications, or for another package that is linked by using connection groups.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Middleware</p></td>
|
||||
<td align="left"><p>Creates a package that is required by a standard application, for example, Java. Middleware packages are used for linking to other packages by using connection groups.</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
| Application type | Description |
|
||||
| - | - |
|
||||
| Standard | Creates a package that contains an application or a suite of applications. This is the preferred option for most application types. |
|
||||
| Add-on or plug-in | Creates a package that extends the functionality of a standard application, for example, a plug-in for Microsoft Excel. Additionally, you can use plug-ins for natively installed applications, or for another package that is linked by using connection groups. |
|
||||
| Middleware | Creates a package that is required by a standard application, for example, Java. Middleware packages are used for linking to other packages by using connection groups. |
|
||||
|
||||
2. Copy all required installation files to the computer that is running the sequencer.
|
||||
|
||||
@ -55,48 +33,40 @@ ms.prod: w10
|
||||
|
||||
- If short paths have been disabled for the virtualized package’s target volume, you must also sequence the package to a volume that was created and still has short-paths disabled. It cannot be the system volume.
|
||||
|
||||
**Note**
|
||||
The App-V Sequencer cannot sequence applications with filenames matching "CO_<x>" where x is any numeral. Error 0x8007139F will be generated.
|
||||
> [!NOTE]
|
||||
> The App-V Sequencer cannot sequence applications with filenames matching "CO_<_x_>" where x is any numeral. Error 0x8007139F will be generated.
|
||||
|
||||
**To sequence a new standard application**
|
||||
|
||||
1. On the computer that runs the sequencer, click **All Programs**, and then Click **Microsoft Application Virtualization**, and then click **Microsoft Application Virtualization Sequencer**.
|
||||
1. On the computer that runs the sequencer, click **All Programs**, and then click **Microsoft Application Virtualization**, and then click **Microsoft Application Virtualization Sequencer**.
|
||||
|
||||
2. In the sequencer, click **Create a New Virtual Application Package**. Select **Create Package (default)**, and then click **Next**.
|
||||
|
||||
3. On the **Prepare Computer** page, review the issues that could cause the package creation to fail or could cause the package to contain unnecessary data. You should resolve all potential issues before you continue. After making any corrections, click **Refresh** to display the updated information. After you have resolved all potential issues, click **Next**.
|
||||
|
||||
**Important**
|
||||
If you are required to disable virus scanning software, you should first scan the computer that runs the sequencer in order to ensure that no unwanted or malicious files could be added to the package.
|
||||
|
||||
|
||||
|
||||
**Note**
|
||||
There is currently no way to disable Windows Defender in Windows 10. If you receive a warning, you can safely ignore it. It is unlikely that Windows Defender will affect sequencing at all.
|
||||
|
||||
|
||||
> [!IMPORTANT]
|
||||
> If you are required to disable virus scanning software, you should first scan the computer that runs the sequencer in order to ensure that no unwanted or malicious files could be added to the package.
|
||||
|
||||
4. On the **Type of Application** page, click the **Standard Application (default)** check box, and then click **Next**.
|
||||
|
||||
5. On the **Select Installer** page, click **Browse** and specify the installation file for the application.
|
||||
|
||||
**Note**
|
||||
If the specified application installer modifies security access to a file or directory, existing or new, the associated changes will not be captured into the package.
|
||||
> [!NOTE]
|
||||
> If the specified application installer modifies security access to a file or directory, existing or new, the associated changes will not be captured into the package.
|
||||
|
||||
|
||||
|
||||
If the application does not have an associated installer file and you plan to run all installation steps manually, select the **Perform a Custom Installation** check box, and then Click **Next**.
|
||||
If the application does not have an associated installer file and you plan to run all installation steps manually, select the **Perform a Custom Installation** check box, and then click **Next**.
|
||||
|
||||
6. On the **Package Name** page, type a name that will be associated with the package. Use a name that helps identify the purpose and version of the application that will be added to the package. The package name is displayed in the App-V 5.0 Management Console.
|
||||
|
||||
6. On the **Package Name** page, type a name that will be associated with the package. Use a name that helps identify the purpose and version of the application that will be added to the package. The package name is displayed in the App-V Management Console.
|
||||
|
||||
Click **Next**.
|
||||
|
||||
7. On the **Installation** page, when the sequencer and application installer are ready you can proceed to install the application so that the sequencer can monitor the installation process.
|
||||
|
||||
**Important**
|
||||
You should always install applications to a secure location and make sure no other users are logged on to the computer running the sequencer during monitoring.
|
||||
> [!IMPORTANT]
|
||||
> You should always install applications to a secure location and make sure no other users are logged on to the computer running the sequencer during monitoring.
|
||||
|
||||
|
||||
|
||||
Use the application's installation process to perform the installation. If additional installation files must be run as part of the installation, click **Run** to locate and run the additional installation files. When you are finished with the installation, select **I am finished installing**. Click **Next**.
|
||||
|
||||
@ -104,10 +74,9 @@ The App-V Sequencer cannot sequence applications with filenames matching "CO_<
|
||||
|
||||
9. On the **Configure Software** page, optionally run the programs contained in the package. This step allows you to complete any necessary license or configuration tasks before you deploy and run the package on target computers. To run all the programs at one time, select at least one program, and then click **Run All**. To run specific programs, select the program or programs, and then click **Run Selected**. Complete the required configuration tasks and then close the applications. You may need to wait several minutes for all programs to run.
|
||||
|
||||
**Note**
|
||||
To run first-use tasks for any application that is not available in the list, open the application. The associated information will be captured during this step.
|
||||
> [!NOTE]
|
||||
> To run first-use tasks for any application that is not available in the list, open the application. The associated information will be captured during this step.
|
||||
|
||||
|
||||
|
||||
Click **Next**.
|
||||
|
||||
@ -123,24 +92,23 @@ The App-V Sequencer cannot sequence applications with filenames matching "CO_<
|
||||
|
||||
12. On the **Streaming** page, run each program so that it can be optimized and run more efficiently on target computers. It can take several minutes for all the applications to run. After all applications have run, close each of the applications, and then click **Next**.
|
||||
|
||||
**Note**
|
||||
If you do not open any applications during this step, the default streaming method is on-demand streaming delivery. This means applications will be downloaded bit by bit until it can be opened, and then depending on how the background loading is configured, will load the rest of the application.
|
||||
> [!NOTE]
|
||||
> If you do not open any applications during this step, the default streaming method is on-demand streaming delivery. This means applications will be downloaded bit by bit until it can be opened, and then depending on how the background loading is configured, will load the rest of the application.
|
||||
|
||||
|
||||
|
||||
13. On the **Target OS** page, specify the operating systems that can run this package. To allow all supported operating systems in your environment to run this package, select **Allow this package to run on any operating system**. To configure this package to run only on specific operating systems, select **Allow this package to run only on the following operating systems** and select the operating systems that can run this package. Click **Next**.
|
||||
|
||||
**Important**
|
||||
Make sure that the operating systems you specify here are supported by the application you are sequencing.
|
||||
> [!IMPORTANT]
|
||||
> Make sure that the operating systems you specify here are supported by the application you are sequencing.
|
||||
|
||||
|
||||
|
||||
14. The **Create Package** page is displayed. To modify the package without saving it, select **Continue to modify package without saving using the package editor**. This option opens the package in the sequencer console so that you can modify the package before it is saved. Click **Next**.
|
||||
|
||||
To save the package immediately, select **Save the package now** (default). Add optional **Comments** to be associated with the package. Comments are useful for identifying the program version and other information about the package.
|
||||
|
||||
**Important**
|
||||
The system does not support non-printable characters in **Comments** and **Descriptions**.
|
||||
> [!IMPORTANT]
|
||||
> The system does not support non-printable characters in **Comments** and **Descriptions**.
|
||||
|
||||
|
||||
|
||||
@ -150,32 +118,27 @@ The App-V Sequencer cannot sequence applications with filenames matching "CO_<
|
||||
|
||||
The package is now available in the sequencer.
|
||||
|
||||
**Important**
|
||||
After you have successfully created a virtual application package, you cannot run the virtual application package on the computer that is running the sequencer.
|
||||
> [!IMPORTANT]
|
||||
> After you have successfully created a virtual application package, you cannot run the virtual application package on the computer that is running the sequencer.
|
||||
|
||||
|
||||
|
||||
**To sequence an add-on or plug-in application**
|
||||
|
||||
1.
|
||||
> [!NOTE]
|
||||
>Before performing the following procedure, install the parent application locally on the computer that is running the sequencer. Or if you have the parent application virtualized, you can follow the steps in the add-on or plug-in workflow to unpack the parent application on the computer.
|
||||
|
||||
**Note**
|
||||
Before performing the following procedure, install the parent application locally on the computer that is running the sequencer. Or if you have the parent application virtualized, you can follow the steps in the add-on or plug-in workflow to unpack the parent application on the computer.
|
||||
>For example, if you are sequencing a plug-in for Microsoft Excel, install Microsoft Excel locally on the computer that is running the sequencer. Also install the parent application in the same directory where the application is installed on target computers. If the plug-in or add-on is going to be used with an existing virtual application package, install the application on the same virtual application drive that was used when you created the parent virtual application package.
|
||||
|
||||
For example, if you are sequencing a plug-in for Microsoft Excel, install Microsoft Excel locally on the computer that is running the sequencer. Also install the parent application in the same directory where the application is installed on target computers. If the plug-in or add-on is going to be used with an existing virtual application package, install the application on the same virtual application drive that was used when you created the parent virtual application package.
|
||||
1. On the computer that runs the sequencer, click **All Programs**, and then Click **Microsoft Application Virtualization**, and then click **Microsoft Application Virtualization Sequencer**.
|
||||
|
||||
|
||||
|
||||
On the computer that runs the sequencer, click **All Programs**, and then Click **Microsoft Application Virtualization**, and then click **Microsoft Application Virtualization Sequencer**.
|
||||
|
||||
2. ****In the sequencer, click **Create a New Virtual Application Package**. Select **Create Package (default)**, and then click **Next**.
|
||||
2. In the sequencer, click **Create a New Virtual Application Package**, select **Create Package (default)**, and then click **Next**.
|
||||
|
||||
3. On the **Prepare Computer** page, review the issues that might cause the package creation to fail or could cause the package to contain unnecessary data. You should resolve all potential issues before you continue. After making any corrections, click **Refresh** to display the updated information. After you have resolved all potential issues, click **Next**.
|
||||
|
||||
**Important**
|
||||
If you are required to disable virus scanning software, you should first scan the computer that runs the sequencer in order to ensure that no unwanted or malicious files could be added to the package.
|
||||
> [!IMPORTANT]
|
||||
> If you are required to disable virus scanning software, you should first scan the computer that runs the sequencer in order to ensure that no unwanted or malicious files could be added to the package.
|
||||
|
||||
|
||||
|
||||
4. On the **Type of Application** page, select **Add-on or Plug-in**, and then click **Next**.
|
||||
|
||||
@ -203,8 +166,8 @@ The App-V Sequencer cannot sequence applications with filenames matching "CO_<
|
||||
|
||||
11. On the **Streaming** page, run each program so that it can be optimized and run more efficiently on target computers. Streaming improves the experience when the virtual application package is run on target computers on high-latency networks. It can take several minutes for all the applications to run. After all applications have run, close each of the applications. You can also configure the package to be required to be fully downloaded before opening by selecting the **Force applications to be downloaded** check-box. Click **Next**.
|
||||
|
||||
**Note**
|
||||
If necessary, you can stop an application from loading during this step. In the **Application Launch** dialog box, click **Stop** and select one of the check boxes: **Stop all applications** or **Stop this application only**.
|
||||
> [!NOTE]
|
||||
> If necessary, you can stop an application from loading during this step. In the **Application Launch** dialog box, click **Stop** and select one of the check boxes: **Stop all applications** or **Stop this application only**.
|
||||
|
||||
|
||||
|
||||
@ -214,8 +177,8 @@ The App-V Sequencer cannot sequence applications with filenames matching "CO_<
|
||||
|
||||
To save the package immediately, select **Save the package now**. Optionally, add a **Description** that will be associated with the package. Descriptions are useful for identifying the version and other information about the package.
|
||||
|
||||
**Important**
|
||||
The system does not support non-printable characters in Comments and Descriptions.
|
||||
> [!IMPORTANT]
|
||||
> The system does not support non-printable characters in Comments and Descriptions.
|
||||
|
||||
|
||||
|
||||
@ -225,14 +188,13 @@ The App-V Sequencer cannot sequence applications with filenames matching "CO_<
|
||||
|
||||
1. On the computer that runs the sequencer, click **All Programs**, and then Click **Microsoft Application Virtualization**, and then click **Microsoft Application Virtualization Sequencer**.
|
||||
|
||||
2. ****In the sequencer, click **Create a New Virtual Application Package**. Select **Create Package (default)**, and then click **Next**.
|
||||
2. In the sequencer, click **Create a New Virtual Application Package**, select **Create Package (default)**, and then click **Next**.
|
||||
|
||||
3. On the **Prepare Computer** page, review the issues that could cause the package creation to fail or could cause the package to contain unnecessary data. You should resolve all potential issues before you continue. After making any corrections, click **Refresh** to display the updated information. After you have resolved all potential issues, click **Next**.
|
||||
|
||||
**Important**
|
||||
If you are required to disable virus scanning software, you should first scan the computer that runs the App-V 5.0 Sequencer in order to ensure that no unwanted or malicious files can be added to the package.
|
||||
> [!IMPORTANT]
|
||||
> If you are required to disable virus scanning software, you should first scan the computer that runs the App-V 5.0 Sequencer in order to ensure that no unwanted or malicious files can be added to the package.
|
||||
|
||||
|
||||
|
||||
4. On the **Type of Application** page, select **Middleware**, and then click **Next**.
|
||||
|
||||
@ -254,10 +216,9 @@ The App-V Sequencer cannot sequence applications with filenames matching "CO_<
|
||||
|
||||
To save the package immediately, select **Save the package now**. Optionally, add a **Description** to be associated with the package. Descriptions are useful for identifying the program version and other information about the package.
|
||||
|
||||
**Important**
|
||||
The system does not support non-printable characters in Comments and Descriptions.
|
||||
|
||||
|
||||
> [!IMPORTANT]
|
||||
> The system does not support non-printable characters in Comments and Descriptions.
|
||||
|
||||
|
||||
The default **Save Location** is also displayed on this page. To change the default location, click **Browse** and specify the new location. Click **Create**.
|
||||
|
||||
@ -265,23 +226,15 @@ The App-V Sequencer cannot sequence applications with filenames matching "CO_<
|
||||
|
||||
The package is now available in the sequencer. To edit the package properties, click **Edit \[Package Name\]**.
|
||||
|
||||
**Important**
|
||||
After you have successfully created a virtual application package, you cannot run the virtual application package on the computer that is running the sequencer.
|
||||
> [!IMPORTANT]
|
||||
> After you have successfully created a virtual application package, you cannot run the virtual application package on the computer that is running the sequencer.
|
||||
|
||||
|
||||
|
||||
**Have a suggestion for App-V**? Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). **Got an App-V issue?** Use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
## Have a suggestion for App-V?
|
||||
Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). **Got an App-V issue?** Use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[Operations for App-V](appv-operations.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
- [Install the App-V Sequencer](appv-install-the-sequencer.md)
|
||||
- [Operations for App-V](appv-operations.md)
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: How to Sequence a Package by Using PowerShell (Windows 10)
|
||||
description: How to Sequence a Package by Using PowerShell
|
||||
title: How to sequence a package by using Windows PowerShell (Windows 10)
|
||||
description: How to sequence a package by using Windows PowerShell
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
@ -9,23 +9,21 @@ ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# How to Sequence a Package by Using PowerShell
|
||||
# How to Sequence a Package by using Windows PowerShell
|
||||
|
||||
Use the following procedure to create a new App-V package using Windows PowerShell.
|
||||
|
||||
Use the following procedure to create a new App-V package using PowerShell.
|
||||
|
||||
**Note**
|
||||
Before you use this procedure you must copy the associated installer files to the computer running the sequencer and you have read and understand the sequencer section of [Planning for the App-V Sequencer and Client Deployment](appv-planning-for-sequencer-and-client-deployment.md).
|
||||
> [!NOTE]
|
||||
> Before you use this procedure you must copy the associated installer files to the computer running the sequencer and you have read and understand the sequencer section of [Planning for the App-V Sequencer and Client Deployment](appv-planning-for-sequencer-and-client-deployment.md).
|
||||
|
||||
|
||||
|
||||
**To create a new virtual application using PowerShell**
|
||||
**To create a new virtual application by using Windows PowerShell**
|
||||
|
||||
1. Install the App-V sequencer. For more information about installing the sequencer see [How to Install the Sequencer](appv-install-the-sequencer.md).
|
||||
|
||||
2. To open a PowerShell console click **Start** and type **PowerShell**. Right-click **Windows PowerShell** and select **Run as Administrator**.
|
||||
2. Click **Start** and type **Windows PowerShell**. Right-click **Windows PowerShell**, and select **Run as Administrator**.
|
||||
|
||||
3. Using the PowerShell console, type the following: **import-module appvsequencer**.
|
||||
3. Using the Windows PowerShell console, type the following: **import-module appvsequencer**.
|
||||
|
||||
4. To create a package, use the **New-AppvSequencerPackage** cmdlet. The following parameters are required to create a package:
|
||||
|
||||
@ -39,34 +37,28 @@ Before you use this procedure you must copy the associated installer files to th
|
||||
|
||||
For example:
|
||||
|
||||
**New-AppvSequencerPackage –Name <name of Package> -PrimaryVirtualApplicationDirectory <path to the package root> -Installer <path to the installer executable> -OutputPath <directory of the output path>**
|
||||
```
|
||||
New-AppvSequencerPackage –Name <name of package> -PrimaryVirtualApplicationDirectory <path to the package root> -Installer <path to the installer executable> -OutputPath <directory of the output path>
|
||||
```
|
||||
|
||||
Wait for the sequencer to create the package. Creating a package using PowerShell can take time. If the package was not created successfully an error will be returned.
|
||||
|
||||
The following list displays additional optional parameters that can be used with **New-AppvSequencerPackage** cmdlet:
|
||||
Wait for the sequencer to create the package. Creating a package by using Windows PowerShell can take time. If the package was not created successfully, an error will be returned.
|
||||
|
||||
- AcceleratorFilePath – specifies the path to the accelerator .cab file to generate a package.
|
||||
The following list displays additional optional parameters that can be used with **New-AppvSequencerPackage** cmdlet:
|
||||
|
||||
- InstalledFilesPath - specifies the path to where the local installed files of the application are saved.
|
||||
- AcceleratorFilePath – specifies the path to the accelerator .cab file to generate a package.
|
||||
|
||||
- InstallMediaPath - specifies the path to where the installation media is
|
||||
- InstalledFilesPath - specifies the path to where the local installed files of the application are saved.
|
||||
|
||||
- TemplateFilePath - specifies the path to a template fileif you want to customize the sequencing process.
|
||||
- InstallMediaPath - specifies the path of the installation media
|
||||
|
||||
- FullLoad - specifies that the package must be fully downloaded to the computer running the App-V before it can be opened.
|
||||
- TemplateFilePath - specifies the path to a template file if you want to customize the sequencing process.
|
||||
|
||||
**Have a suggestion for App-V**? Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). **Got an App-V issue?** Use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
- FullLoad - specifies that the package must be fully downloaded to the computer running the App-V before it can be opened.
|
||||
|
||||
## Have a suggestion for App-V?
|
||||
Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). **Got an App-V issue?** Use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[Administering App-V by Using PowerShell](appv-administering-appv-with-powershell.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
- [Administering App-V by using Windows PowerShell](appv-administering-appv-with-powershell.md)
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user