deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-06-15 18:33:43 +00:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity

sweep files for 1607 changes

Browse Source
This commit is contained in:
Justinha
2016-08-12 16:56:25 -07:00
parent 690498decc
commit 92458538d5
10 changed files with 745 additions and 915 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
windows/manage/appv-capacity-planning.md
View File

@ -63,7 +63,7 @@ You can also manage your App-V environment using an Electronic Software Distribu
- With disconnected remote users who cannot connect to the App-V infrastructure.
- When you are running a software management system, such as Configuration Manager 2012.
- When you are running a software management system, such as System Center 2012 Configuration Manager.
- When network bandwidth limitations inhibit electronic software distribution.

51
windows/manage/appv-deploy-the-appv-server-with-a-script.md
View File

@ -11,18 +11,15 @@ ms.prod: w10
# How to Deploy the App-V Server Using a Script
In order to complete the **appv\_server\_setup.exe** Server setup successfully using the command line, you must specify and combine multiple parameters.
**To Install the App-V server using a script**
- Use the following tables for more information about installing the App-V server using the command line.
Use the following tables for more information about installing the App-V server using the command line.
**Note**  
The information in the following tables can also be accessed using the command line by typing the following command: **appv\_server\_setup.exe /?**.
 
**Common parameters and Examples**
<table>
@ -66,8 +63,6 @@ In order to complete the **appv\_server\_setup.exe** Server setup successfully u
</tbody>
</table>
 
<table>
<colgroup>
<col width="50%" />
@ -109,8 +104,6 @@ In order to complete the **appv\_server\_setup.exe** Server setup successfully u
</tbody>
</table>
 
<table>
<colgroup>
<col width="50%" />
@ -152,8 +145,6 @@ In order to complete the **appv\_server\_setup.exe** Server setup successfully u
</tbody>
</table>
 
<table>
<colgroup>
<col width="50%" />
@ -187,9 +178,7 @@ In order to complete the **appv\_server\_setup.exe** Server setup successfully u
<p>/MANAGEMENT_SERVER_INSTALL_ADMIN_ACCOUNT=”Domain\InstallAdminAccount”</p></td>
</tr>
</tbody>
</table>
 
</table>  
<table>
<colgroup>
@ -226,8 +215,6 @@ In order to complete the **appv\_server\_setup.exe** Server setup successfully u
</tbody>
</table>
 
<table>
<colgroup>
<col width="50%" />
@ -253,8 +240,6 @@ In order to complete the **appv\_server\_setup.exe** Server setup successfully u
</tbody>
</table>
 
<table>
<colgroup>
<col width="50%" />
@ -296,8 +281,6 @@ In order to complete the **appv\_server\_setup.exe** Server setup successfully u
</tbody>
</table>
 
<table>
<colgroup>
<col width="50%" />
@ -335,9 +318,7 @@ In order to complete the **appv\_server\_setup.exe** Server setup successfully u
<p>/EXITING_REPORTING_DB_NAME=”AppVReporting”</p></td>
</tr>
</tbody>
</table>
 
</table> 
<table>
<colgroup>
@ -378,8 +359,6 @@ In order to complete the **appv\_server\_setup.exe** Server setup successfully u
</tbody>
</table>
 
<table>
<colgroup>
<col width="50%" />
@ -415,8 +394,6 @@ In order to complete the **appv\_server\_setup.exe** Server setup successfully u
</tbody>
</table>
 
<table>
<colgroup>
<col width="50%" />
@ -452,8 +429,6 @@ In order to complete the **appv\_server\_setup.exe** Server setup successfully u
</tbody>
</table>
 
**Parameter Definitions**
**General Parameters**
@ -501,8 +476,6 @@ In order to complete the **appv\_server\_setup.exe** Server setup successfully u
</tbody>
</table>
 
**Management Server Installation Parameters**
<table>
@ -536,8 +509,6 @@ In order to complete the **appv\_server\_setup.exe** Server setup successfully u
</tbody>
</table>
 
**Parameters for the Management Server Database**
<table>
@ -583,8 +554,6 @@ In order to complete the **appv\_server\_setup.exe** Server setup successfully u
</tbody>
</table>
 
**Parameters for Installing Publishing Server**
<table>
@ -618,8 +587,6 @@ In order to complete the **appv\_server\_setup.exe** Server setup successfully u
</tbody>
</table>
 
**Parameters for Reporting Server**
<table>
@ -647,9 +614,7 @@ In order to complete the **appv\_server\_setup.exe** Server setup successfully u
<td align="left"><p>Specifies the port number that the Reporting Service will use. E.g. /REPORTING_WEBSITE_PORT=82</p></td>
</tr>
</tbody>
</table>
 
</table>  
**Parameters for using an Existing Reporting Server Database**
@ -686,9 +651,7 @@ In order to complete the **appv\_server\_setup.exe** Server setup successfully u
<td align="left"><p>Specifies the name of the existing Reporting database that should be used. Takes a string. E.g. /EXISITING_REPORTING_DB_NAME=&quot;AppVReporting&quot;</p></td>
</tr>
</tbody>
</table>
 
</table>  
**Parameters for installing Reporting Server Database**
@ -731,8 +694,6 @@ In order to complete the **appv\_server\_setup.exe** Server setup successfully u
</tbody>
</table>
 
**Parameters for using an existing Management Server Database**
<table>
@ -772,8 +733,6 @@ In order to complete the **appv\_server\_setup.exe** Server setup successfully u
</tbody>
</table>
 
## Related topics

26
windows/manage/appv-install-the-management-and-reporting-databases-on-separate-computers.md
View File

@ -17,8 +17,6 @@ Use the following procedure to install the database server and management server
>**Note**  
After you complete the deployment, the **Microsoft SQL Server name**, **instance name** and **database name** will be required by the administrator installing the service to be able to connect to these databases.
 
**To install the management database and the management server on separate computers**
1. Copy the App-V server installation files to the computer on which you want to install it on. To start the App-V server installation right-click and run **appv\_server\_setup.exe** as an administrator. Click **Install**.
@ -40,11 +38,7 @@ After you complete the deployment, the **Microsoft SQL Server name**, **instance
7. On the next **Create New Management Server Database** page, select **Use a remote computer**, and type the remote machine account using the following format: **Domain\\MachineAccount**.
>**Note**  
If you plan to deploy the management server on the same computer you must select **Use this local computer**.
 
Specify the user name for the management server **Install Administrator** using the following format: **Domain\\AdministratorLoginName**. Click **Next**.
If you plan to deploy the management server on the same computer you must select **Use this local computer**. Specify the user name for the management server **Install Administrator** using the following format: Domain\\AdministratorLoginName. Click **Next**.
8. To start the installation, click **Install**.
@ -66,14 +60,10 @@ After you complete the deployment, the **Microsoft SQL Server name**, **instance
If you are using a custom database name, then select **Custom configuration** and type the database name.
7. On the next **Create New Reporting Server Database** page, select **Use a remote computer**, and type the remote machine account using the following format: **Domain\\MachineAccount**.
7. On the next **Create New Reporting Server Database** page, select **Use a remote computer**, and type the remote machine account using the following format: Domain\\MachineAccount.
**Note**  
If you plan to deploy the reporting server on the same computer you must select **Use this local computer**.
 
Specify the user name for the reporting server **Install Administrator** using the following format: **Domain\\AdministratorLoginName**. Click **Next**.
If you plan to deploy the reporting server on the same computer you must select **Use this local computer**. Specify the user name for the reporting server **Install Administrator** using the following format: Domain\\AdministratorLoginName. Click **Next**.
8. To start the installation, click **Install**.
@ -83,7 +73,7 @@ After you complete the deployment, the **Microsoft SQL Server name**, **instance
2. To extract the App-V database scripts, open a command prompt and specify the location where the installation files are saved and run the following command:
**appv\_server\_setup.exe** **/LAYOUT** **/LAYOUTDIR=”InstallationExtractionLocation”**.
**appv\_server\_setup.exe** **/LAYOUT** **/LAYOUTDIR=”InstallationExtractionLocation”**
3. After the extraction has been completed, to access the App-V database scripts and instructions readme file:
@ -94,13 +84,13 @@ After you complete the deployment, the **Microsoft SQL Server name**, **instance
4. For each database, copy the scripts to a share and modify them following the instructions in the readme file.
**Note**  
For more information about modifying the required SIDs contained in the scripts see, [How to Install the App-V Databases and Convert the Associated Security Identifiers by Using PowerShell](appv-install-the-appv-databases-and-convert-the-associated-security-identifiers-with-powershell.md).
 
For more information about modifying the required SIDs contained in the scripts see, [How to Install the App-V Databases and Convert the Associated Security Identifiers by Using PowerShell](appv-install-the-appv-databases-and-convert-the-associated-security-identifiers-with-powershell.md).  
5. Run the scripts on the computer running Microsoft SQL Server.
**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). For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
## Related topics

12
windows/manage/appv-install-the-management-server-on-a-standalone-computer.md
View File

@ -29,13 +29,7 @@ Use the following procedure to install the management server on a standalone com
6. On the **Configure Existing Management Database** page, select **Use a remote SQL Server**, and type the machine name of the computer running Microsoft SQL SQL, for example **SqlServerMachine**.
>**Note**  
If the Microsoft SQL Server is deployed on the same server, select **Use local SQL Server**.
 
For the SQL Server Instance, select **Use the default instance**. If you are using a custom Microsoft SQL Server instance, you must select **Use a custom instance** and then type the name of the instance.
Specify the **SQL Server Database name** that this management server will use, for example **AppvManagement**.
If the Microsoft SQL Server is deployed on the same server, select **Use local SQL Server**. For the SQL Server Instance, select **Use the default instance**. If you are using a custom Microsoft SQL Server instance, you must select **Use a custom instance** and then type the name of the instance. Specify the **SQL Server Database name** that this management server will use, for example **AppvManagement**.
7. On the **Configure Management Server Configuration** page, specify the AD group or account that will connect to the management console for administrative purposes for example **MyDomain\\MyUser** or **MyDomain\\AdminGroup**. The account or AD group you specify will be enabled to manage the server through the management console. You can add additional users or groups using the management console after installation
@ -45,7 +39,9 @@ Use the following procedure to install the management server on a standalone com
9. To confirm that the setup has completed successfully, open a web browser, and type the following URL: http://managementserver:portnumber/Console. If the installation was successful, you should see the **Management Console** appear without any error messages or warnings being displayed.
**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). For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
## Related topics

22
windows/manage/appv-install-the-publishing-server-on-a-remote-computer.md
View File

@ -46,23 +46,27 @@ Use the following procedure to install the publishing server on a separate compu
9. To verify that the publishing server is running correctly, you should import a package to the management server, entitle the package to an AD group, and publish the package. Using an internet browser, open the following URL: **http://publishingserver:pubport**. If the server is running correctly information similar to the following will be displayed:
`<Publishing Protocol="1.0">`
```syntax
<Publishing Protocol="1.0">
` <Packages>`
<Packages>
` <Package PackageId="28115343-06e2-44dc-a327-3a0b9b868bda" VersionId="5d03c08f-51dc-4026-8cf9-15ebe3d65a72" PackageUrl="\\server\share\file.appv" />`
<Package PackageId="28115343-06e2-44dc-a327-3a0b9b868bda" VersionId="5d03c08f-51dc-4026-8cf9-15ebe3d65a72" PackageUrl="\\server\share\file.appv" />
` </Packages>`
</Packages>
` <NoGroup>`
<NoGroup>
` <Package PackageId="28115343-06e2-44dc-a327-3a0b9b868bda" />`
<Package PackageId="28115343-06e2-44dc-a327-3a0b9b868bda" />
` </NoGroup>`
</NoGroup>
`</Publishing>`
</Publishing>
```
**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). For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
## Related topics

12
windows/manage/appv-install-the-reporting-server-on-a-standalone-computer.md
View File

@ -34,13 +34,7 @@ Before performing the following procedure you should read and understand [About
6. On the **Configure Existing Reporting Database** page, select **Use a remote SQL Server**, and type the machine name of the computer running Microsoft SQL Server, for example **SqlServerMachine**.
**Note**  
If the Microsoft SQL Server is deployed on the same server, select **Use local SQL Server**.
 
For the SQL Server Instance, select **Use the default instance**. If you are using a custom Microsoft SQL Server instance, you must select **Use a custom instance** and then type the name of the instance.
Specify the **SQL Server Database name** that this reporting server will use, for example **AppvReporting**.
If the Microsoft SQL Server is deployed on the same server, select **Use local SQL Server**. For the SQL Server Instance, select **Use the default instance**. If you are using a custom Microsoft SQL Server instance, you must select **Use a custom instance** and then type the name of the instance. Specify the **SQL Server Database name** that this reporting server will use, for example **AppvReporting**.
7. On the **Configure Reporting Server Configuration** page.
@ -50,7 +44,9 @@ Before performing the following procedure you should read and understand [About
8. Click **Install**.
**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). For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
## Related topics

4
windows/manage/appv-migrating-to-appv-from-a-previous-version.md
View File

@ -200,10 +200,10 @@ After you convert an existing package you should test the package prior to deplo
 
When converting a package check for failing files or shortcuts. Locate the item in App-V 4.6 package. It could possibly be a hard-coded path. Convert the path.
When converting a package check for failing files or shortcuts, locate the item in App-V 4.6 package. It could possibly be a hard-coded path. Convert the path.
**Note**  
It is recommended that you use the App-V sequencer for converting critical applications or applications that need to take advantage of features. See, [How to Sequence a New Application with App-V](appv-sequence-a-new-application.md).
It is recommended that you use the App-V sequencer for converting critical applications or applications that need to take advantage of features. See [How to Sequence a New Application with App-V](appv-sequence-a-new-application.md).
If a converted package does not open after you convert it, it is also recommended that you re-sequence the application using the App-V sequencer.

2
windows/manage/appv-prerequisites.md
View File

@ -50,7 +50,7 @@ The following table indicates the software that is already installed for differe
</div></td>
</tr>
<tr class="odd">
<td align="left"><p>Windows Server 2012</p></td>
<td align="left"><p>Windows Server 2016</p></td>
<td align="left"><p>The following prerequisite software is already installed:</p>
<ul>
<li><p>Microsoft .NET Framework 4.5</p></li>

42
windows/manage/appv-reporting.md
View File

@ -38,7 +38,7 @@ The following list displays the end–to-end high-level workflow for reporting i
 
4. After importing the App-V PowerShell module using `Import-Module AppvClient` as administrator, enable the App-V client. This sample PowerShell cmdlet enables App-V reporting:
4. After importing the App-V Windows PowerShell module using `Import-Module AppvClient` as administrator, enable the App-V client. This sample Windows PowerShell cmdlet enables App-V reporting:
``` syntax
Set-AppvClientConfiguration –reportingserverurl <url>:<port> -reportingenabled 1 – ReportingStartTime <0-23> - ReportingRandomDelay <#min>
@ -53,11 +53,7 @@ The following list displays the end–to-end high-level workflow for reporting i
6. When the App-V client receives the success notification, it empties the data cache to conserve space.
>**Note**  
By default, the cache is cleared after the server confirms receipt of data. You can manually configure the client to save the data cache.
 
If the App-V client device does not receive a success notification from the server, it retains data in the cache and tries to resend data at the next configured interval. Clients continue to collect data and add it to the cache.
By default, the cache is cleared after the server confirms receipt of data. You can manually configure the client to save the data cache. If the App-V client device does not receive a success notification from the server, it retains data in the cache and tries to resend data at the next configured interval. Clients continue to collect data and add it to the cache.
### <a href="" id="-------------app-v-reporting-server-frequently-asked-questions"></a> App-V reporting server frequently asked questions
@ -95,7 +91,7 @@ The following table displays answers to common questions about App-V reporting
<ol>
<li><p>Operating system, and App-V client information. ~150 Bytes, every time this data is sent.</p></li>
<li><p>Published package list. ~7 KB for 30 packages. This is sent only when the package list is updated with a publishing refresh, which is done infrequently; if there is no change, this information is not sent.</p></li>
<li><p>Virtual application usage information – about 0.25KB per event. Opening and closing count as one event if both occur before sending the information. When sending using a scheduled task, only the data since the last successful upload is sent to the server. If sending manually through the PowerShell cmdlet, there is an optional argument that controls if the data needs to be re-sent next time around – that argument is <strong>DeleteOnSuccess</strong>.</p>
<li><p>Virtual application usage information – about 0.25KB per event. Opening and closing count as one event if both occur before sending the information. When sending using a scheduled task, only the data since the last successful upload is sent to the server. If sending manually through the Windows PowerShell cmdlet, there is an optional argument that controls if the data needs to be re-sent next time around – that argument is <strong>DeleteOnSuccess</strong>.</p>
<p></p>
<p>So for example, if twenty applications are opened and closed and reporting information is scheduled to be sent daily, the typical daily traffic should be about 0.15KB + 20 x 0.25KB, or about 5KB/user</p></li>
</ol></td>
@ -104,7 +100,7 @@ The following table displays answers to common questions about App-V reporting
<td align="left"><p>Can reporting be scheduled?</p></td>
<td align="left"><p>Yes. Besides manually sending reporting using PowerShell Cmdlets (<strong>Send-AppvClientReport</strong>), the task can be scheduled so it will happen automatically. There are two ways to schedule the reporting:</p>
<ol>
<li><p>Using PowerShell cmdlets - <strong>Set-AppvClientConfiguration</strong>. For example:</p>
<li><p>Using Windows PowerShell cmdlets - <strong>Set-AppvClientConfiguration</strong>. For example:</p>
<p>Set-AppvClientConfiguration -ReportingEnabled 1 - ReportingServerURL http://any.com/appv-reporting</p>
<p></p>
<p>For a complete list of client configuration settings see [About Client Configuration Settings](appv-client-configuration-settings.md) and look for the following entries: <strong>ReportingEnabled</strong>, <strong>ReportingServerURL</strong>, <strong>ReportingDataCacheLimit</strong>, <strong>ReportingDataBlockSize</strong>, <strong>ReportingStartTime</strong>, <strong>ReportingRandomDelay</strong>, <strong>ReportingInterval</strong>.</p>
@ -112,7 +108,7 @@ The following table displays answers to common questions about App-V reporting
<li><p>By using Group Policy. If distributed using the domain controller, the settings are the same as previously listed.</p>
<div class="alert">
<strong>Note</strong>  
<p>Group Policy settings override local settings configured using PowerShell.</p>
<p>Group Policy settings override local settings configured using Windows PowerShell.</p>
</div>
<div>
 
@ -127,11 +123,11 @@ The following table displays answers to common questions about App-V reporting
## <a href="" id="---------app-v-client-reporting"></a> App-V Client Reporting
To use App-V reporting you must enable and configure the App-V client. After the client has been installed, use the **Set-AppVClientConfiguration** PowerShell cmdlet or the **ADMX Template** to configure reporting. The reporting feature cmdlets are available by using the following link and are prefaced by **Reporting**. For a complete list of client configuration settings see [About Client Configuration Settings](appv-client-configuration-settings.md). The following section provides examples of App-V client reporting configuration using PowerShell.
To use App-V reporting you must enable and configure the App-V client. After the client has been installed, use the **Set-AppVClientConfiguration** Windows PowerShell cmdlet or the **ADMX Template** to configure reporting. The reporting feature cmdlets are available by using the following link and are prefaced by **Reporting**. For a complete list of client configuration settings see [About Client Configuration Settings](appv-client-configuration-settings.md). The following section provides examples of App-V client reporting configuration using Windows PowerShell.
### Configuring App-V Client reporting using PowerShell
### Configuring App-V Client reporting using Windows PowerShell
The following examples show how PowerShell parameters can configure the reporting features of the App-V client.
The following examples show how Windows PowerShell parameters can configure the reporting features of the App-V client.
**Note**  
The following configuration task can also be configured using Group Policy settings in the App-V ADMX template. For more information about using the ADMX template, see [How to Modify App-V Client Configuration Using the ADMX Template and Group Policy](appv-modify-client-configuration-with-the-admx-template-and-group-policy.md).
@ -140,27 +136,31 @@ The following configuration task can also be configured using Group Policy setti
**To enable reporting and to initiate data collection on the computer running the App-V client**:
`Set-AppVClientConfiguration –ReportingEnabled 1`
```syntax
Set-AppVClientConfiguration –ReportingEnabled 1
```
**To configure the client to automatically send data to a specific reporting server**:
``` syntax
Set-AppVClientConfiguration –ReportingServerURL http://MyReportingServer:MyPort/ -ReportingStartTime 20 -ReportingInterval 1 -ReportingRandomDelay 30
Set-AppVClientConfiguration –ReportingServerURL http://MyReportingServer:MyPort/ -ReportingStartTime 20 -ReportingInterval 1 -ReportingRandomDelay 30 -ReportingInterval 1 -ReportingRandomDelay 30
```
`-ReportingInterval 1 -ReportingRandomDelay 30`
This example configures the client to automatically send the reporting data to the reporting server URL **http://MyReportingServer:MyPort/**. Additionally, the reporting data will be sent daily between 8:00 and 8:30 PM, depending on the random delay generated for the session.
**To limit the size of the data cache on the client**:
`Set-AppvClientConfiguration –ReportingDataCacheLimit 100`
```syntax
Set-AppvClientConfiguration –ReportingDataCacheLimit 100
```
Configures the maximum size of the reporting cache on the computer running the App-V client to 100 MB. If the cache limit is reached before the data is sent to the server, then the log rolls over and data will be overwritten as necessary.
**To configure the data block size transmitted across the network between the client and the server**:
`Set-AppvClientConfiguration –ReportingDataBlockSize 10240`
```syntax
Set-AppvClientConfiguration –ReportingDataBlockSize 10240
```
Specifies the maximum data block that the client sends to 10240 MB.
@ -238,9 +238,11 @@ You can configure the computer that is running the App-V client to automatically
- ReportingRandomDelay
After you configure the previous settings, you must create a scheduled task. The scheduled task will contact the server specified by the **ReportingServerURL** setting and will initiate the transfer. If you want to manually send data outside of the scheduled times, use the following PowerShell cmdlet:
After you configure the previous settings, you must create a scheduled task. The scheduled task will contact the server specified by the **ReportingServerURL** setting and will initiate the transfer. If you want to manually send data outside of the scheduled times, use the following Windows PowerShell cmdlet:
`Send-AppVClientReport –URL http://MyReportingServer:MyPort/ -DeleteOnSuccess`
```syntax
Send-AppVClientReport –URL http://MyReportingServer:MyPort/ -DeleteOnSuccess
```
If the reporting server has been previously configured, then the **–URL** parameter can be omitted. Alternatively, if the data should be sent to an alternate location, specify a different URL to override the configured **ReportingServerURL** for this data collection.

123
windows/manage/appv-supported-configurations.md
View File

@ -35,47 +35,7 @@ The App-V server does not support the following scenarios:
### Management server operating system requirements
The following table lists the operating systems that are supported for the App-V Management server installation.
<table>
<colgroup>
<col width="33%" />
<col width="33%" />
<col width="33%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">Operating system</th>
<th align="left">Service Pack</th>
<th align="left">System architecture</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>Microsoft Windows Server 2016</p></td>
<td align="left"><p></p></td>
<td align="left"><p>64-bit</p></td>
</tr>
<tr class="odd">
<td align="left"><p>Microsoft Windows Server 2012 R2</p></td>
<td align="left"><p></p></td>
<td align="left"><p>64-bit</p></td>
</tr>
<tr class="even">
<td align="left"><p>Microsoft Windows Server 2012</p></td>
<td align="left"><p></p></td>
<td align="left"><p>64-bit</p></td>
</tr>
<tr class="odd">
<td align="left"><p>Microsoft Windows Server 2008 R2</p></td>
<td align="left"><p>SP1</p></td>
<td align="left"><p>64-bit</p></td>
</tr>
</tbody>
</table>
 
The App-V Management server can be installed on a server that runs Windows Server 2008 R2 with SP1 or a later.
> [!IMPORTANT]
> Deployment of the Management server role to a computer with Remote Desktop Services enabled is not supported.
@ -130,46 +90,8 @@ The following table lists the SQL Server versions that are supported for the App
### Publishing server operating system requirements
The following table lists the operating systems that are supported for the App-V Publishing server installation.
The App-V Publishing server can be installed on a server that runs Windows Server 2008 R2 with SP1 or a later.
<table>
<colgroup>
<col width="33%" />
<col width="33%" />
<col width="33%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">Operating system</th>
<th align="left">Service Pack</th>
<th align="left">System architecture</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>Microsoft Windows Server 2016</p></td>
<td align="left"><p></p></td>
<td align="left"><p>64-bit</p></td>
</tr>
<tr class="odd">
<td align="left"><p>Microsoft Windows Server 2012 R2</p></td>
<td align="left"><p></p></td>
<td align="left"><p>64-bit</p></td>
</tr>
<tr class="even">
<td align="left"><p>Microsoft Windows Server 2012</p></td>
<td align="left"><p></p></td>
<td align="left"><p>64-bit</p></td>
</tr>
<tr class="odd">
<td align="left"><p>Microsoft Windows Server 2008 R2</p></td>
<td align="left"><p>SP1</p></td>
<td align="left"><p>64-bit</p></td>
</tr>
</tbody>
</table>
 
### Publishing server hardware requirements
@ -183,46 +105,7 @@ App-V adds no additional requirements beyond those of Windows Server.
### Reporting server operating system requirements
The following table lists the operating systems that are supported for the App-V Reporting server installation.
<table>
<colgroup>
<col width="33%" />
<col width="33%" />
<col width="33%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">Operating system</th>
<th align="left">Service Pack</th>
<th align="left">System architecture</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>Microsoft Windows Server 2016</p></td>
<td align="left"><p></p></td>
<td align="left"><p>64-bit</p></td>
</tr>
<tr class="odd">
<td align="left"><p>Microsoft Windows Server 2012 R2</p></td>
<td align="left"><p></p></td>
<td align="left"><p>64-bit</p></td>
</tr>
<tr class="even">
<td align="left"><p>Microsoft Windows Server 2012</p></td>
<td align="left"><p></p></td>
<td align="left"><p>64-bit</p></td>
</tr>
<tr class="odd">
<td align="left"><p>Microsoft Windows Server 2008 R2</p></td>
<td align="left"><p>SP1</p></td>
<td align="left"><p>64-bit</p></td>
</tr>
</tbody>
</table>
 
The App-V Reporting server can be installed on a server that runs Windows Server 2008 R2 with SP1 or a later. 
### Reporting server hardware requirements