diff --git a/windows/application-management/app-v/appv-client-configuration-settings.md b/windows/application-management/app-v/appv-client-configuration-settings.md index d5a434e8d6..3f87e404cb 100644 --- a/windows/application-management/app-v/appv-client-configuration-settings.md +++ b/windows/application-management/app-v/appv-client-configuration-settings.md @@ -83,7 +83,7 @@ The following table provides information about App-V client configuration settin | **GlobalRefreshIntervalUnit**
0 for hour, 1 for day | Publishing\\Servers{serverId}\\GlobalPeriodicRefreshIntervalUnit | 1 | | **UserRefreshEnabled**
True (Enabled); False (Disabled state) | Publishing\\Servers{serverId}\\UserEnabled | False | | **UserRefreshOnLogon**
True (Enabled); False (Disabled state) | Publishing\\Servers{serverId}\\UserLogonRefresh | False | -| **UserRefreshInterval**
Word count (with spaces): 85Integer (0–744 Hours) | Publishing\\Servers{serverId}\\UserPeriodicRefreshInterval | 0 | +| **UserRefreshInterval**
Word count (with spaces): 85; Integer (0–744 Hours) | Publishing\\Servers{serverId}\\UserPeriodicRefreshInterval | 0 | | **UserRefreshIntervalUnit**
0 for hour, 1 for day | Publishing\\Servers{serverId}\\UserPeriodicRefreshIntervalUnit | 1 | | **MigrationMode**
True(Enabled state); False (Disabled state) | Coexistence\\MigrationMode | | | **EnablePackageScripts**
True (Enabled); False (Disabled state) | \\Scripting\\EnablePackageScripts | | diff --git a/windows/application-management/app-v/appv-deploy-the-appv-server-with-a-script.md b/windows/application-management/app-v/appv-deploy-the-appv-server-with-a-script.md index cb9b7e85d7..a3e5f097a2 100644 --- a/windows/application-management/app-v/appv-deploy-the-appv-server-with-a-script.md +++ b/windows/application-management/app-v/appv-deploy-the-appv-server-with-a-script.md @@ -440,16 +440,16 @@ Using a custom instance of Microsoft SQL Server example:
| */QUIET* | Specifies silent install. | | */UNINSTALL* | Specifies an uninstall. | | */LAYOUT* | Specifies layout action. This extracts the MSIs and script files to a folder without installing the actual product. No value is expected. | -| */LAYOUTDIR* | Specifies the layout directory with a string. For example, ```/LAYOUTDIR="C:\Application Virtualization Server"``` | -| */INSTALLDIR* | Specifies the installation directory with a string. For example, ```/INSTALLDIR="C:\Program Files\Application Virtualization\Server"``` | -| */MUOPTIN* | Enables Microsoft Update. No value is expected | +| */LAYOUTDIR* | Specifies the layout directory with a string. For example, ```/LAYOUTDIR="C:\Application Virtualization Server"```. | +| */INSTALLDIR* | Specifies the installation directory with a string. For example, ```/INSTALLDIR="C:\Program Files\Application Virtualization\Server"```. | +| */MUOPTIN* | Enables Microsoft Update. No value is expected. | | */ACCEPTEULA* | Accepts the license agreement. This is required for an unattended installation. For example, ```/ACCEPTEULA``` or ```/ACCEPTEULA=1```. | ### Parameter definitions for Management Server installation parameters | Parameter | Description | |-----------|-------------| -| */MANAGEMENT_SERVER* | Specifies that the management server will be installed. No value is expected | +| */MANAGEMENT_SERVER* | Specifies that the management server will be installed. No value is expected. | | */MANAGEMENT_ADMINACCOUNT* | Specifies the account that will be allowed administrator access to the management server. This account can be an individual user account or a group. For example, ```/MANAGEMENT_ADMINACCOUNT="mydomain\admin"```. If **/MANAGEMENT_SERVER** isn't specified, this parameter will be ignored.| | */MANAGEMENT_WEBSITE_NAME* | Specifies name of the website that will be created for the management service. For example, ```/MANAGEMENT_WEBSITE_NAME="Microsoft App-V Management Service"``` | | */MANAGEMENT_WEBSITE_PORT* | Specifies the port number that will be used by the management service will use. For example, ```/MANAGEMENT_WEBSITE_PORT=82```. | @@ -458,7 +458,7 @@ Using a custom instance of Microsoft SQL Server example:
| Parameter | Description | |-----------|-------------| -| */DB\_PREDEPLOY\_MANAGEMENT* | Specifies that the management database will be installed. You must have sufficient database permissions to complete this installation. No value is expected | +| */DB\_PREDEPLOY\_MANAGEMENT* | Specifies that the management database will be installed. You must have sufficient database permissions to complete this installation. No value is expected. | | */MANAGEMENT_DB_SQLINSTANCE_USE_DEFAULT* | Indicates that the default SQL instance should be used. No value is expected. | | */MANAGEMENT_DB_CUSTOM_SQLINSTANCE* | Specifies the name of the custom SQL instance that should be used to create a new database. For example, ```/MANAGEMENT_DB_CUSTOM_SQLINSTANCE="MYSQLSERVER"```. If **/DB_PREDEPLOY_MANAGEMENT** isn't specified, this parameter will be ignored. | | */MANAGEMENT_DB_NAME* | Specifies the name of the new management database that should be created. For example, ```/MANAGEMENT_DB_NAME="AppVMgmtDB"```. If **/DB_PREDEPLOY_MANAGEMENT** isn't specified, this will be ignored. | @@ -497,7 +497,7 @@ Using a custom instance of Microsoft SQL Server example:
| Parameter | Description | |-----------|-------------| -| */DB\_PREDEPLOY\_REPORTING* | Specifies that the Reporting Database will be installed. DBA permissions are required for this installation. No value is expected | +| */DB\_PREDEPLOY\_REPORTING* | Specifies that the Reporting Database will be installed. DBA permissions are required for this installation. No value is expected. | | */REPORTING_DB_SQLINSTANCE_USE_DEFAULT* | Specifies the name of the custom SQL instance that should be used. Takes a string. For example, ```/REPORTING_DB_CUSTOM_SQLINSTANCE="MYSQLSERVER"```. | | */REPORTING_DB_NAME* | Specifies the name of the new Reporting database that should be created. Takes a string. For example, ```/REPORTING_DB_NAME="AppVMgmtDB"```. | | */REPORTING_SERVER_MACHINE_USE_LOCAL* | Indicates that the Reporting server that will be accessing the database is installed on the local server. This is a switch parameter, so no value is expected. | diff --git a/windows/application-management/app-v/appv-deploy-the-appv-server.md b/windows/application-management/app-v/appv-deploy-the-appv-server.md index b4c92a9ecd..65af77d8e0 100644 --- a/windows/application-management/app-v/appv-deploy-the-appv-server.md +++ b/windows/application-management/app-v/appv-deploy-the-appv-server.md @@ -73,7 +73,7 @@ ms.date: 04/17/2018 | Item to configure | Description and examples | |---|---| - | Specify the management service URL | Example: https://localhost:12345 | + | Specify the management service URL | Example: http://localhost:12345 | | Website name | Specify the custom website name that will be used to run the publishing service.
If you do not have a custom name, do not make any changes. | | Port binding | Specify a unique port number that will be used by App-V. Example: 54321
Ensure that the port specified is not being used by another website. | 13. On the **Reporting Server** page, specify the following: diff --git a/windows/application-management/app-v/appv-deploying-the-appv-sequencer-and-client.md b/windows/application-management/app-v/appv-deploying-the-appv-sequencer-and-client.md index e3bf835c34..3dbf198437 100644 --- a/windows/application-management/app-v/appv-deploying-the-appv-sequencer-and-client.md +++ b/windows/application-management/app-v/appv-deploying-the-appv-sequencer-and-client.md @@ -33,8 +33,8 @@ You can use Group Policy to configure the client settings for the App-V client a To manage the ADMX template, perform the following steps on the computer that you will use to manage Group Policy. This is typically the Domain Controller. -1. Save the **.admx** file to the following directory: ```Windows \\ PolicyDefinitions``` -2. Save the **.adml** file to the following directory: ```Windows \\ PolicyDefinitions \\ ``` +1. Save the **.admx** file to the following directory: ```Windows\PolicyDefinitions``` +2. Save the **.adml** file to the following directory: ```Windows\PolicyDefinitions\``` After you have completed the preceding steps, you can use Group Policy to configure the client settings by using the Group Policy Management Console under **Computer Configuration** > **Administrative Templates** > **System** > **App-V**. @@ -83,7 +83,7 @@ To deploy the sequencer, see [How to install the Sequencer](appv-install-the-seq You can use the App-V Sequencer log information to troubleshoot Sequencer installation and operational events while using App-V. The Sequencer-related log information can be reviewed with the **Event Viewer**. The following file path is the specific path for Sequencer-related events: -**Event Viewer \\ Applications and Services Logs \\ Microsoft \\ App V**. +**Event Viewer\Applications and Services Logs\Microsoft\App V**. >[!NOTE] >Sequencer-related events are prepended with **AppV\_Sequencer**. Client-related events are prepended with **AppV\_Client**. diff --git a/windows/application-management/app-v/appv-enable-the-app-v-desktop-client.md b/windows/application-management/app-v/appv-enable-the-app-v-desktop-client.md index 6646843201..174bd5559c 100644 --- a/windows/application-management/app-v/appv-enable-the-app-v-desktop-client.md +++ b/windows/application-management/app-v/appv-enable-the-app-v-desktop-client.md @@ -26,9 +26,9 @@ Here's how to enable the App-V client with Group Policy: Here's how to enable the App-V client with Windows PowerShell: 1. Open Windows PowerShell. -2. Type `Enable-Appv`, then select the Enter key. +2. Enter **Enable-Appv**, then select the Enter key. 3. Restart the device. -4. To verify that the App-V client is working, type `Get-AppvStatus`, then select the Enter key. +4. To verify that the App-V client is working, enter **Get-AppvStatus**, then select the Enter key. Check out these articles for more information about how to configure the App-V client: diff --git a/windows/application-management/app-v/appv-install-the-management-and-reporting-databases-on-separate-computers.md b/windows/application-management/app-v/appv-install-the-management-and-reporting-databases-on-separate-computers.md index bbae3de2bb..83991a6803 100644 --- a/windows/application-management/app-v/appv-install-the-management-and-reporting-databases-on-separate-computers.md +++ b/windows/application-management/app-v/appv-install-the-management-and-reporting-databases-on-separate-computers.md @@ -1,6 +1,6 @@ --- -title: How to Install the Management and Reporting Databases on Separate Computers from the Management and Reporting Services (Windows 10) -description: How to install the Management and Reporting Databases on Separate Computers from the Management and Reporting Services +title: How to Install the Management and Reporting Databases on separate computers from the Management and Reporting Services (Windows 10) +description: How to install the Management and Reporting Databases on separate computers from the Management and Reporting Services. author: MaggiePucciEvans ms.pagetype: mdop, appcompat, virtualization ms.mktglfcycl: deploy @@ -8,7 +8,7 @@ ms.sitesec: library ms.prod: w10 ms.date: 04/17/2018 --- -# How to Install the Management and Reporting Databases on Separate Computers from the Management and Reporting Services +# How to Install the Management and Reporting Databases on separate computers from the Management and Reporting Services >Applies to: Windows Server 2016 @@ -27,10 +27,10 @@ Use the following procedure to install the database server and management server 6. On the initial **Create new management server database** page, accept the default selections if appropriate, then select **Next**. * If you are using a custom SQL Server instance, select **Use a custom instance** and enter the name of the instance. * If you are using a custom database name, select **Custom configuration** and enter the database name. -7. On the next **Create new management server database** page, select **Use a remote computer**, then enter the remote machine account using the following format: ```Domain\\MachineAccount```. +7. On the next **Create new management server database** page, select **Use a remote computer**, then enter 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```. After that, select **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```. After that, select **Next**. 8. To start the installation, select **Install**. ## Installing the reporting database and the reporting server on separate computers @@ -43,7 +43,7 @@ Use the following procedure to install the database server and management server 6. On the initial **Create new management server database** page, accept the default selections if appropriate, then select **Next**. * If you're using a custom SQL Server instance, select **Use a custom instance** and enter the instance name. * If you're using a custom database name, select **Custom configuration** and enter the database name. -7. On the next **Create new management server database** page, select **Use a remote computer**, and enter the remote machine account using the following format: ```Domain\\MachineAccount```. +7. On the next **Create new management server database** page, select **Use a remote computer**, and enter 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. After that, select **Next**. @@ -53,9 +53,11 @@ Use the following procedure to install the database server and management server 1. Copy the App-V server installation files to the computer on which you want to install it on. 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: + ```SQL 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: * The App-V Management Database scripts and instructions readme are located in the following folder: **InstallationExtractionLocation** \\ **Database Scripts** \\ **Management Database**. diff --git a/windows/application-management/app-v/appv-install-the-publishing-server-on-a-remote-computer.md b/windows/application-management/app-v/appv-install-the-publishing-server-on-a-remote-computer.md index 5fb7f93a57..bd67be31b0 100644 --- a/windows/application-management/app-v/appv-install-the-publishing-server-on-a-remote-computer.md +++ b/windows/application-management/app-v/appv-install-the-publishing-server-on-a-remote-computer.md @@ -8,7 +8,7 @@ ms.sitesec: library ms.prod: w10 ms.date: 04/17/2018 --- -# How to Install the Publishing Server on a Remote Computer +# How to install the publishing server on a remote computer >Applies to: Windows Server 2016 @@ -23,7 +23,7 @@ Use the following procedure to install the publishing server on a separate compu 5. On the **Installation location** page, accept the default location, then select **Next**. 6. On the **Configure publishing server configuration** page, specify the following items: - * The URL for the management service that the publishing server will connect to. For example, **https://ManagementServerName:12345**. + * The URL for the management service that the publishing server will connect to. For example, **http://ManagementServerName:12345**. * Specify the website name that you want to use for the publishing service. If you don't have a custom name, then use the default name. * For the **Port binding**, specify a unique port number that will be used by App-V. For example, **54321**. 7. On the **Ready to install** page, select **Install**. diff --git a/windows/application-management/app-v/appv-install-the-reporting-server-on-a-standalone-computer.md b/windows/application-management/app-v/appv-install-the-reporting-server-on-a-standalone-computer.md index be11197ac0..fff16610af 100644 --- a/windows/application-management/app-v/appv-install-the-reporting-server-on-a-standalone-computer.md +++ b/windows/application-management/app-v/appv-install-the-reporting-server-on-a-standalone-computer.md @@ -1,5 +1,5 @@ --- -title: How to install the Reporting Server on a Standalone Computer and Connect it to the Database (Windows 10) +title: How to install the Reporting Server on a standalone computer and connect it to the database (Windows 10) description: How to install the App-V Reporting Server on a Standalone Computer and Connect it to the Database author: MaggiePucciEvans ms.pagetype: mdop, appcompat, virtualization diff --git a/windows/application-management/app-v/appv-reporting.md b/windows/application-management/app-v/appv-reporting.md index 7689742322..afe9597029 100644 --- a/windows/application-management/app-v/appv-reporting.md +++ b/windows/application-management/app-v/appv-reporting.md @@ -81,7 +81,7 @@ Yes. Besides manually sending reporting using Windows PowerShell cmdlets (**Send * Using a Windows PowerShell cmdlet: **Set-AppvClientConfiguration**. For example: ```PowerShell - Set-AppvClientConfiguration -ReportingEnabled 1 -ReportingServerURL https://any.com/appv-reporting + Set-AppvClientConfiguration -ReportingEnabled 1 -ReportingServerURL http://any.com/appv-reporting ``` For a complete list of client configuration settings, go to [About client configuration settings](appv-client-configuration-settings.md) and look for the following entries: **ReportingEnabled**, **ReportingServerURL**, **ReportingDataCacheLimit**, **ReportingDataBlockSize**, **ReportingStartTime**, **ReportingRandomDelay**, **ReportingInterval**. @@ -114,10 +114,10 @@ Set-AppVClientConfiguration –ReportingEnabled 1 To configure the client to automatically send data to a specific reporting server, use a command with the following format: ```PowerShell -Set-AppVClientConfiguration -ReportingServerURL https://MyReportingServer:MyPort/ -ReportingStartTime 20 -ReportingInterval 1 -ReportingRandomDelay 30 +Set-AppVClientConfiguration -ReportingServerURL http://MyReportingServer:MyPort/ -ReportingStartTime 20 -ReportingInterval 1 -ReportingRandomDelay 30 ``` -This example command configures the client to automatically send the reporting data to the reporting server URL ```https://MyReportingServer:MyPort/```. The reporting data will be sent to the URL daily between 8:00 PM and 8:30 PM, depending on the session's generated random delay. +This example command configures the client to automatically send the reporting data to the reporting server URL ```http://MyReportingServer:MyPort/```. The reporting data will be sent to the URL daily between 8:00 PM and 8:30 PM, depending on the session's generated random delay. #### Limiting the size of the client's data cache @@ -153,63 +153,11 @@ The following table displays the types of information you can collect by using A |Operating system type||Username| |||Connection group| - ----- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Client informationPackage informationApplication usage

Host name

Package name

Start and end times

App-V client version

Package version

Run status

Processor architecture

Package source

Shutdown state

Operating system version

Percent cached

Application name

Service Pack level

Application version

Operating system type

Username

Connection group

- The client collects and saves this data in an **.xml** format. The data cache is hidden by default and requires administrator rights to open the XML file. ### Sending data to the server -You can configure the computer that is running the App-V client to automatically send data to the specified reporting server. To specify the server use the **Set-AppvClientConfiguration** cmdlet with the following settings: +You can configure the computer that is running the App-V client to automatically send data to the specified reporting server. To specify the server, use the **Set-AppvClientConfiguration** cmdlet with the following settings: * ReportingEnabled * ReportingServerURL @@ -220,7 +168,7 @@ You can configure the computer that is running the App-V client to automatically 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: ```PowerShell -Send-AppVClientReport –URL https://MyReportingServer:MyPort/ -DeleteOnSuccess +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.