From 31e4e9fbd551582225a414203f0d2c1e0d28d34e Mon Sep 17 00:00:00 2001 From: JanKeller1 Date: Wed, 24 Aug 2016 19:44:02 -0700 Subject: [PATCH 1/2] Formatting overhaul where orig fmt was not working --- .../appv-client-configuration-settings.md | 76 +- ...pv-deploy-the-appv-server-with-a-script.md | 1072 ++++++----------- 2 files changed, 425 insertions(+), 723 deletions(-) diff --git a/windows/manage/appv-client-configuration-settings.md b/windows/manage/appv-client-configuration-settings.md index 7fe953302b..59e07c520f 100644 --- a/windows/manage/appv-client-configuration-settings.md +++ b/windows/manage/appv-client-configuration-settings.md @@ -21,45 +21,45 @@ You can use Group Policy to configure App-V client settings by using the Group P The following table provides information about App-V client configuration settings that can be configured through Windows PowerShell cmdlets: -| **Name of option in Windows PowerShell**
Type | Description | Cmdlet or cmdlets for setting | Disabled Policy State Keys and Values | +| Windows PowerShell cmdlet or cmdlets,
**Option**
Type | Description | Disabled Policy State Keys and Values | |------------|------------|------------|------------| -| **PackageInstallationRoot**
String | Specifies directory where all new applications and updates will be installed. | Set-AppvClientConfiguration,
Set-AppvPublishingServer | Policy value not written (same as Not Configured) | -| **PackageSourceRoot**
String | Overrides source location for downloading package content. | Set-AppvClientConfiguration,
Set-AppvPublishingServer | Policy value not written (same as Not Configured) | -| **AllowHighCostLaunch**
True (enabled); False (Disabled state) | This setting controls whether virtualized applications are launched on Windows 10 machines connected via a metered network connection (For example, 4G). | Set-AppvClientConfiguration,
Set-AppvPublishingServer | 0 | -| **ReestablishmentRetries**
Integer (0-99) | Specifies the number of times to retry a dropped session. | Set-AppvClientConfiguration,
Set-AppvPublishingServer | Policy value not written (same as Not Configured) | -| **ReestablishmentInterval**
Integer (0-3600) | Specifies the number of seconds between attempts to reestablish a dropped session. | Set-AppvClientConfiguration,
Set-AppvPublishingServer | Policy value not written (same as Not Configured) | -| **LocationProvider**
String | Specifies the CLSID for a compatible implementation of the IAppvPackageLocationProvider interface. | Set-AppvClientConfiguration,
Set-AppvPublishingServer | Policy value not written (same as Not Configured) | -| **CertFilterForClientSsl**
String | Specifies the path to a valid certificate in the certificate store. | Set-AppvClientConfiguration,
Set-AppvPublishingServer | Policy value not written (same as Not Configured) | -| **VerifyCertificateRevocationList**
True(enabled); False(Disabled state) | Verifies Server certificate revocation status before steaming using HTTPS. | Set-AppvClientConfiguration,
Set-AppvPublishingServer | 0 | -| **SharedContentStoreMode**
True(enabled); False(Disabled state) | Specifies that streamed package contents will be not be saved to the local hard disk. | Set-AppvClientConfiguration,
Set-AppvPublishingServer | 0 | -| **Name**
String | Displays the name of publishing server. | Set-AppvPublishingServer | Policy value not written (same as Not Configured) | -| **URL**
String | Displays the URL of publishing server. | Set-AppvPublishingServer | Policy value not written (same as Not Configured) | -| **GlobalRefreshEnabled**
True(enabled); False(Disabled state) | Enables global publishing refresh (Boolean) | Set-AppvPublishingServer | False | -| **GlobalRefreshOnLogon**
True(enabled); False(Disabled state) | Triggers a global publishing refresh on logon. ( Boolean) | Set-AppvPublishingServer | False | -| **GlobalRefreshInterval**
Integer (0-744) | Specifies the publishing refresh interval using the GlobalRefreshIntervalUnit. To disable package refresh, select 0. | Set-AppvPublishingServer | 0 | -| **GlobalRefreshIntervalUnit**
0 for hour, 1 for day | Specifies the interval unit (Hour 0-23, Day 0-31). | Set-AppvPublishingServer | 1 | -| **UserRefreshEnabled**
True(enabled); False(Disabled state) | Enables user publishing refresh (Boolean) | Set-AppvPublishingServer | False | -| **UserRefreshOnLogon**
True(enabled); False(Disabled state) | Triggers a user publishing refresh onlogon. ( Boolean)Word count (with spaces): 60 | Set-AppvPublishingServer | False | -| **UserRefreshInterval**
Word count (with spaces): 85Integer (0-744 Hours) | Specifies the publishing refresh interval using the UserRefreshIntervalUnit. To disable package refresh, select 0. | Set-AppvPublishingServer | 0 | -| **UserRefreshIntervalUnit**
0 for hour, 1 for day | Specifies the interval unit (Hour 0-23, Day 0-31). | Set-AppvPublishingServer | 1 | -| **MigrationMode**
True(enabled state); False (disabled state) | Migration mode allows the App-V client to modify shortcuts and FTA’s for packages created using a previous version of App-V. | Set-AppvClientConfiguration,
Set-AppvPublishingServer | | -| **EnablePackageScripts**
True(enabled); False(Disabled state) | Enables scripts defined in the package manifest of configuration files that should run. | Set-AppvClientConfiguration,
Set-AppvPublishingServer | | -| **RoamingFileExclusions**
String | Specifies the file paths relative to %userprofile% that do not roam with a user's profile. Example usage: /ROAMINGFILEEXCLUSIONS='desktop;my pictures' | Set-AppvClientConfiguration | | -| **RoamingRegistryExclusions**
String | Specifies the registry paths that do not roam with a user profile. Example usage: /ROAMINGREGISTRYEXCLUSIONS=software\\classes;software\\clients | Set-AppvClientConfiguration,
Set-AppvPublishingServer | Policy value not written (same as Not Configured) | -| **IntegrationRootUser**
String | Specifies the location to create symbolic links associated with the current version of a per-user published package. all virtual application extensions, for example shortcuts and file type associations, will point to this path. If you do not specify a path, symbolic links will not be used when you publish the package. For example: %localappdata%\\Microsoft\\AppV\\Client\\Integration. | Set-AppvClientConfiguration,
Set-AppvPublishingServer | Policy value not written (same as Not Configured) | -| **IntegrationRootGlobal**
String | Specifies the location to create symbolic links associated with the current version of a globally published package. all virtual application extensions, for example shortcuts and file type associations, will point to this path. If you do not specify a path, symbolic links will not be used when you publish the package. For example: %allusersprofile%\\Microsoft\\AppV\\Client\\Integration | Set-AppvClientConfiguration,
Set-AppvPublishingServer | Policy value not written (same as Not Configured) | -| **VirtualizableExtensions**
String | A comma -delineated list of file name extensions that can be used to determine if a locally installed application can be run in the virtual environment. When shortcuts, FTAs, and other extension points are created during publishing, App-V will compare the file name extension to the list if the application that is associated with the extension point is locally installed. If the extension is located, the **RunVirtual** command line parameter will be added, and the application will run virtually. For more information about the **RunVirtual** parameter, see [Running a Locally Installed Application Inside a Virtual Environment with Virtualized Applications](appv-running-locally-installed-applications-inside-a-virtual-environment.md). | Set-AppvClientConfiguration,
Set-AppvPublishingServer | Policy value not written | -| **ReportingEnabled**
True (enabled); False (Disabled state) | Enables the client to return information to a reporting server. | Set-AppvClientConfiguration,
Set-AppvPublishingServer | False | -| **ReportingServerURL**
String | Specifies the location on the reporting server where client information is saved. | Set-AppvClientConfiguration,
Set-AppvPublishingServer | Policy value not written (same as Not Configured) | -| **ReportingDataCacheLimit**
Integer \[0-1024\] | Specifies the maximum size in megabytes (MB) of the XML cache for storing reporting information. The size applies to the cache in memory. When the limit is reached, the log file will roll over. Set between 0 and 1024. | Set-AppvClientConfiguration,
Set-AppvPublishingServer | Policy value not written (same as Not Configured) | -| **ReportingDataBlockSize**
Integer \[1024 - Unlimited\] | Specifies the maximum size in bytes to transmit to the server for reporting upload requests. This can help avoid permanent transmission failures when the log has reached a significant size. Set between 1024 and unlimited. | Set-AppvClientConfiguration,
Set-AppvPublishingServer | Policy value not written (same as Not Configured) | -| **ReportingStartTime**
Integer (0 – 23) | Specifies the time to initiate the client to send data to the reporting server. You must specify a valid integer between 0-23 corresponding to the hour of the day. By default the **ReportingStartTime** will start on the current day at 10 P.M.or 22.
**Note** You should configure this setting to a time when computers running the App-V client are least likely to be offline. | Set-AppvClientConfiguration,
Set-AppvPublishingServer | Policy value not written (same as Not Configured) | -| **ReportingInterval**
Integer | Specifies the retry interval that the client will use to resend data to the reporting server. | Set-AppvClientConfiguration,
Set-AppvPublishingServer | Policy value not written (same as Not Configured) | -| **ReportingRandomDelay**
Integer \[0 - ReportingRandomDelay\] | Specifies the maximum delay (in minutes) for data to be sent to the reporting server. When the scheduled task is started, the client generates a random delay between 0 and **ReportingRandomDelay** and will wait the specified duration before sending data. This can help to prevent collisions on the server. | Set-AppvClientConfiguration,
Set-AppvPublishingServer | Policy value not written (same as Not Configured) | -| **EnableDynamicVirtualization
**1 (Enabled), 0 (Disabled) | Enables supported Shell Extensions, Browser Helper Objects, and Active X controls to be virtualized and run with virtual applications. | Set-AppvClientConfiguration,
Set-AppvPublishingServer | | -| **EnablePublishingRefreshUI**
1 (Enabled), 0 (Disabled) | Enables the publishing refresh progress bar for the computer running the App-V Client. | Set-AppvClientConfiguration,
Set-AppvPublishingServer | | -| **HidePublishingRefreshUI**
1 (Enabled), 0 (Disabled) | Hides the publishing refresh progress bar. | Sync-AppvPublishingServer | | -| **ProcessesUsingVirtualComponents**
String | Specifies a list of process paths (that may contain wildcards), which are candidates for using dynamic virtualization (supported shell extensions, browser helper objects, and ActiveX controls). Only processes whose full path matches one of these items can use dynamic virtualization. | Set-AppvClientConfiguration,
Set-AppvPublishingServer | Empty string. | +| Set-AppvClientConfiguration,
Set-AppvPublishingServer

**-PackageInstallationRoot**
String | Specifies directory where all new applications and updates will be installed. | Policy value not written (same as Not Configured) | +| Set-AppvClientConfiguration,
Set-AppvPublishingServer

**-PackageSourceRoot**
String | Overrides source location for downloading package content. | Policy value not written (same as Not Configured) | +| Set-AppvClientConfiguration,
Set-AppvPublishingServer

**-AllowHighCostLaunch**
True (enabled); False (Disabled state) | This setting controls whether virtualized applications are launched on Windows 10 machines connected via a metered network connection (For example, 4G). | 0 | +| Set-AppvClientConfiguration,
Set-AppvPublishingServer

**-ReestablishmentRetries**
Integer (0-99) | Specifies the number of times to retry a dropped session. | Policy value not written (same as Not Configured) | +| Set-AppvClientConfiguration,
Set-AppvPublishingServer

**-ReestablishmentInterval**
Integer (0-3600) | Specifies the number of seconds between attempts to reestablish a dropped session. | Policy value not written (same as Not Configured) | +| Set-AppvClientConfiguration,
Set-AppvPublishingServer

**-LocationProvider**
String | Specifies the CLSID for a compatible implementation of the IAppvPackageLocationProvider interface. | Policy value not written (same as Not Configured) | +| Set-AppvClientConfiguration,
Set-AppvPublishingServer

**-CertFilterForClientSsl**
String | Specifies the path to a valid certificate in the certificate store. | Policy value not written (same as Not Configured) | +| Set-AppvClientConfiguration,
Set-AppvPublishingServer

**-VerifyCertificateRevocationList**
True(enabled); False(Disabled state) | Verifies Server certificate revocation status before steaming using HTTPS. | 0 | +| Set-AppvClientConfiguration,
Set-AppvPublishingServer

**-SharedContentStoreMode**
True(enabled); False(Disabled state) | Specifies that streamed package contents will be not be saved to the local hard disk. | 0 | +| Set-AppvPublishingServer

**-Name**
String | Displays the name of publishing server. | Policy value not written (same as Not Configured) | +| Set-AppvPublishingServer

**-URL**
String | Displays the URL of publishing server. | Policy value not written (same as Not Configured) | +| Set-AppvPublishingServer

**-GlobalRefreshEnabled**
True(enabled); False(Disabled state) | Enables global publishing refresh (Boolean) | False | +| Set-AppvPublishingServer

**-GlobalRefreshOnLogon**
True(enabled); False(Disabled state) | Triggers a global publishing refresh on logon. ( Boolean) | False | +| Set-AppvPublishingServer

**-GlobalRefreshInterval**
Integer (0-744) | Specifies the publishing refresh interval using the GlobalRefreshIntervalUnit. To disable package refresh, select 0. | 0 | +| Set-AppvPublishingServer

**-GlobalRefreshIntervalUnit**
0 for hour, 1 for day | Specifies the interval unit (Hour 0-23, Day 0-31). | 1 | +| Set-AppvPublishingServer

**-UserRefreshEnabled**
True(enabled); False(Disabled state) | Enables user publishing refresh (Boolean) | False | +| Set-AppvPublishingServer

**-UserRefreshOnLogon**
True(enabled); False(Disabled state) | Triggers a user publishing refresh onlogon. ( Boolean)Word count (with spaces): 60 | False | +| Set-AppvPublishingServer

**-UserRefreshInterval**
Word count (with spaces): 85Integer (0-744 Hours) | Specifies the publishing refresh interval using the UserRefreshIntervalUnit. To disable package refresh, select 0. | 0 | +| Set-AppvPublishingServer

**-UserRefreshIntervalUnit**
0 for hour, 1 for day | Specifies the interval unit (Hour 0-23, Day 0-31). | 1 | +| Set-AppvClientConfiguration,
Set-AppvPublishingServer

**-MigrationMode**
True(enabled state); False (disabled state) | Migration mode allows the App-V client to modify shortcuts and FTA’s for packages created using a previous version of App-V. | | +| Set-AppvClientConfiguration,
Set-AppvPublishingServer

**-EnablePackageScripts**
True(enabled); False(Disabled state) | Enables scripts defined in the package manifest of configuration files that should run. | | +| Set-AppvClientConfiguration

**-RoamingFileExclusions**
String | Specifies the file paths relative to %userprofile% that do not roam with a user's profile. Example usage: /ROAMINGFILEEXCLUSIONS='desktop;my pictures' | | +| Set-AppvClientConfiguration,
Set-AppvPublishingServer

**-RoamingRegistryExclusions**
String | Specifies the registry paths that do not roam with a user profile. Example usage: /ROAMINGREGISTRYEXCLUSIONS=software\\classes;software\\clients | Policy value not written (same as Not Configured) | +| Set-AppvClientConfiguration,
Set-AppvPublishingServer

**-IntegrationRootUser**
String | Specifies the location to create symbolic links associated with the current version of a per-user published package. all virtual application extensions, for example shortcuts and file type associations, will point to this path. If you do not specify a path, symbolic links will not be used when you publish the package. For example: %localappdata%\\Microsoft\\AppV\\Client\\Integration. | Policy value not written (same as Not Configured) | +| Set-AppvClientConfiguration,
Set-AppvPublishingServer

**-IntegrationRootGlobal**
String | Specifies the location to create symbolic links associated with the current version of a globally published package. all virtual application extensions, for example shortcuts and file type associations, will point to this path. If you do not specify a path, symbolic links will not be used when you publish the package. For example: %allusersprofile%\\Microsoft\\AppV\\Client\\Integration | Policy value not written (same as Not Configured) | +| Set-AppvClientConfiguration,
Set-AppvPublishingServer

**-VirtualizableExtensions**
String | A comma -delineated list of file name extensions that can be used to determine if a locally installed application can be run in the virtual environment. When shortcuts, FTAs, and other extension points are created during publishing, App-V will compare the file name extension to the list if the application that is associated with the extension point is locally installed. If the extension is located, the **RunVirtual** command line parameter will be added, and the application will run virtually. For more information about the **RunVirtual** parameter, see [Running a Locally Installed Application Inside a Virtual Environment with Virtualized Applications](appv-running-locally-installed-applications-inside-a-virtual-environment.md). | Policy value not written | +| Set-AppvClientConfiguration,
Set-AppvPublishingServer

**-ReportingEnabled**
True (enabled); False (Disabled state) | Enables the client to return information to a reporting server. | False | +| Set-AppvClientConfiguration,
Set-AppvPublishingServer

**-ReportingServerURL**
String | Specifies the location on the reporting server where client information is saved. | Policy value not written (same as Not Configured) | +| Set-AppvClientConfiguration,
Set-AppvPublishingServer

**-ReportingDataCacheLimit**
Integer \[0-1024\] | Specifies the maximum size in megabytes (MB) of the XML cache for storing reporting information. The size applies to the cache in memory. When the limit is reached, the log file will roll over. Set between 0 and 1024. | Policy value not written (same as Not Configured) | +| Set-AppvClientConfiguration,
Set-AppvPublishingServer

**-ReportingDataBlockSize**
Integer \[1024 - Unlimited\] | Specifies the maximum size in bytes to transmit to the server for reporting upload requests. This can help avoid permanent transmission failures when the log has reached a significant size. Set between 1024 and unlimited. | Policy value not written (same as Not Configured) | +| Set-AppvClientConfiguration,
Set-AppvPublishingServer

**-ReportingStartTime**
Integer (0 – 23) | Specifies the time to initiate the client to send data to the reporting server. You must specify a valid integer between 0-23 corresponding to the hour of the day. By default the **ReportingStartTime** will start on the current day at 10 P.M.or 22.
**Note** You should configure this setting to a time when computers running the App-V client are least likely to be offline. | Policy value not written (same as Not Configured) | +| Set-AppvClientConfiguration,
Set-AppvPublishingServer

**-ReportingInterval**
Integer | Specifies the retry interval that the client will use to resend data to the reporting server. | Policy value not written (same as Not Configured) | +| Set-AppvClientConfiguration,
Set-AppvPublishingServer

**-ReportingRandomDelay**
Integer \[0 - ReportingRandomDelay\] | Specifies the maximum delay (in minutes) for data to be sent to the reporting server. When the scheduled task is started, the client generates a random delay between 0 and **ReportingRandomDelay** and will wait the specified duration before sending data. This can help to prevent collisions on the server. | Policy value not written (same as Not Configured) | +| Set-AppvClientConfiguration,
Set-AppvPublishingServer

**-EnableDynamicVirtualization
**1 (Enabled), 0 (Disabled) | Enables supported Shell Extensions, Browser Helper Objects, and Active X controls to be virtualized and run with virtual applications. | | +| Set-AppvClientConfiguration,
Set-AppvPublishingServer

**-EnablePublishingRefreshUI**
1 (Enabled), 0 (Disabled) | Enables the publishing refresh progress bar for the computer running the App-V Client. | | +| Sync-AppvPublishingServer

**-HidePublishingRefreshUI**
1 (Enabled), 0 (Disabled) | Hides the publishing refresh progress bar. | | +| Set-AppvClientConfiguration,
Set-AppvPublishingServer

**-ProcessesUsingVirtualComponents**
String | Specifies a list of process paths (that may contain wildcards), which are candidates for using dynamic virtualization (supported shell extensions, browser helper objects, and ActiveX controls). Only processes whose full path matches one of these items can use dynamic virtualization. | Empty string. | ## App-V Client Configuration Settings: Registry Keys diff --git a/windows/manage/appv-deploy-the-appv-server-with-a-script.md b/windows/manage/appv-deploy-the-appv-server-with-a-script.md index a3e8b107ff..ddc30926a2 100644 --- a/windows/manage/appv-deploy-the-appv-server-with-a-script.md +++ b/windows/manage/appv-deploy-the-appv-server-with-a-script.md @@ -1,4 +1,4 @@ ---- +--- title: How to Deploy the App-V Server Using a Script (Windows 10) description: How to Deploy the App-V Server Using a Script author: MaggiePucciEvans @@ -16,723 +16,425 @@ ms.prod: w10 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** +**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 lists and 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 /?**. +> **Note**  The information in the following lists and tables can also be accessed using the command line by typing the following command: **appv\_server\_setup.exe /?**. -**Common parameters and Examples** +## How to use common parameters - ---- - - - - - - -

To Install the Management server and Management database on a local machine.

To use the default instance of Microsoft SQL Server, use the following parameters:

-
    -

  • /MANAGEMENT_SERVER

    • -

  • /MANAGEMENT_ADMINACCOUNT

    • -

  • /MANAGEMENT_WEBSITE_NAME

    • -

  • /MANAGEMENT_WEBSITE_PORT

    • -

  • /DB_PREDEPLOY_MANAGEMENT

    • -

  • /MANAGEMENT_DB_SQLINSTANCE_USE_DEFAULT

    • -

  • /MANAGEMENT_DB_NAME

    • -
-

To use a custom instance of Microsoft SQL Server, use the following parameters:

-
    -

  • /MANAGEMENT_SERVER

    • -

  • /MANAGEMENT_ADMINACCOUNT

    • -

  • /MANAGEMENT_WEBSITE_NAME

    • -

  • /MANAGEMENT_WEBSITE_PORT

    • -

  • /DB_PREDEPLOY_MANAGEMENT

    • -

  • /MANAGEMENT_DB_CUSTOM_SQLINSTANCE

    • -

  • /MANAGEMENT_DB_NAME

    • -
-

Using a custom instance of Microsoft SQL Server example:

-

/appv_server_setup.exe /QUIET

-

/MANAGEMENT_SERVER

-

/MANAGEMENT_ADMINACCOUNT=”Domain\AdminGroup”

-

/MANAGEMENT_WEBSITE_NAME=”Microsoft AppV Management Service”

-

/MANAGEMENT_WEBSITE_PORT=”8080”

-

/DB_PREDEPLOY_MANAGEMENT

-

/MANAGEMENT_DB_CUSTOM_SQLINSTANCE=”SqlInstanceName”

-

/MANAGEMENT_DB_NAME=”AppVManagement”

+## To install the Management server and Management database on a local machine - ---- - - - - - - -

To Install the Management server using an existing Management database on a local machine.

To use the default instance of Microsoft SQL Server, use the following parameters:

-
    -

  • /MANAGEMENT_SERVER

    • -

  • /MANAGEMENT_ADMINACCOUNT

    • -

  • /MANAGEMENT_WEBSITE_NAME

    • -

  • /MANAGEMENT_WEBSITE_PORT

    • -

  • /EXISTING_MANAGEMENT_DB_SQL_SERVER_USE_LOCAL

    • -

  • /EXISTING_MANAGEMENT_DB_SQLINSTANCE_USE_DEFAULT

    • -

  • /EXISTING_MANAGEMENT_DB_NAME

    • -
-

To use a custom instance of Microsoft SQL Server, use these parameters:

-
    -

  • /MANAGEMENT_SERVER

    • -

  • /MANAGEMENT_ADMINACCOUNT

    • -

  • /MANAGEMENT_WEBSITE_NAME

    • -

  • /MANAGEMENT_WEBSITE_PORT

    • -

  • /EXISTING_MANAGEMENT_DB_SQL_SERVER_USE_LOCAL

    • -

  • /EXISTING_MANAGEMENT_DB_CUSTOM_SQLINSTANCE

    • -

  • /EXISTING_MANAGEMENT_DB_NAME

    • -
-

Using a custom instance of Microsoft SQL Server example:

-

/appv_server_setup.exe /QUIET

-

/MANAGEMENT_SERVER

-

/MANAGEMENT_ADMINACCOUNT=”Domain\AdminGroup”

-

/MANAGEMENT_WEBSITE_NAME=”Microsoft AppV Management Service”

-

/MANAGEMENT_WEBSITE_PORT=”8080”

-

/EXISTING_MANAGEMENT_DB_SQL_SERVER_USE_LOCAL

-

/EXISTING_MANAGEMENT_DB_CUSTOM_SQLINSTANCE =”SqlInstanceName”

-

/EXISTING_MANAGEMENT_DB_NAME =”AppVManagement”

+**Default instance of Microsoft SQL Server**: To use the default instance of Microsoft SQL Server, use the following parameters: - ---- - - - - - - -

To install the Management server using an existing Management database on a remote machine.

To use the default instance of Microsoft SQL Server, use the following parameters:

-
    -

  • /MANAGEMENT_SERVER

    • -

  • /MANAGEMENT_ADMINACCOUNT

    • -

  • /MANAGEMENT_WEBSITE_NAME

    • -

  • /MANAGEMENT_WEBSITE_PORT

    • -

  • /EXISTING_MANAGEMENT_DB_REMOTE_SQL_SERVER_NAME

    • -

  • /EXISTING_MANAGEMENT_DB_SQLINSTANCE_USE_DEFAULT

    • -

  • /EXISTING_MANAGEMENT_DB_NAME

    • -
-

To use a custom instance of Microsoft SQL Server, use these parameters:

-
    -

  • /MANAGEMENT_SERVER

    • -

  • /MANAGEMENT_ADMINACCOUNT

    • -

  • /MANAGEMENT_WEBSITE_NAME

    • -

  • /MANAGEMENT_WEBSITE_PORT

    • -

  • /EXISTING_MANAGEMENT_DB_REMOTE_SQL_SERVER_NAME

    • -

  • /EXISTING_MANAGEMENT_DB_CUSTOM_SQLINSTANCE

    • -

  • /EXISTING_MANAGEMENT_DB_NAME

    • -
-

Using a custom instance of Microsoft SQL Server example:

-

/appv_server_setup.exe /QUIET

-

/MANAGEMENT_SERVER

-

/MANAGEMENT_ADMINACCOUNT=”Domain\AdminGroup”

-

/MANAGEMENT_WEBSITE_NAME=”Microsoft AppV Management Service”

-

/MANAGEMENT_WEBSITE_PORT=”8080”

-

/EXISTING_MANAGEMENT_DB_REMOTE_SQL_SERVER_NAME=”SqlServermachine.domainName”

-

/EXISTING_MANAGEMENT_DB_CUSTOM_SQLINSTANCE =”SqlInstanceName”

-

/EXISTING_MANAGEMENT_DB_NAME =”AppVManagement”

+- /MANAGEMENT_SERVER +- /MANAGEMENT_ADMINACCOUNT +- /MANAGEMENT_WEBSITE_NAME +- /MANAGEMENT_WEBSITE_PORT +- /DB_PREDEPLOY_MANAGEMENT +- /MANAGEMENT_DB_SQLINSTANCE_USE_DEFAULT +- /MANAGEMENT_DB_NAME - ---- - - - - - - -

To Install the Management database and the Management Server on the same computer.

To use the default instance of Microsoft SQL Server, use the following parameters:

-
    -

  • /DB_PREDEPLOY_MANAGEMENT

    • -

  • /MANAGEMENT_DB_SQLINSTANCE_USE_DEFAULT

    • -

  • /MANAGEMENT_DB_NAME

    • -

  • /MANAGEMENT_SERVER_MACHINE_USE_LOCAL

    • -

  • /MANAGEMENT_SERVER_INSTALL_ADMIN_ACCOUNT

    • -
-

To use a custom instance of Microsoft SQL Server, use these parameters:

-
    -

  • /DB_PREDEPLOY_MANAGEMENT

    • -

  • /MANAGEMENT_DB_CUSTOM_SQLINSTANCE

    • -

  • /MANAGEMENT_DB_NAME

    • -

  • /MANAGEMENT_SERVER_MACHINE_USE_LOCAL

    • -

  • /MANAGEMENT_SERVER_INSTALL_ADMIN_ACCOUNT

    • -
-

Using a custom instance of Microsoft SQL Server example:

-

/appv_server_setup.exe /QUIET

-

/DB_PREDEPLOY_MANAGEMENT

-

/MANAGEMENT_DB_CUSTOM_SQLINSTANCE=”SqlInstanceName”

-

/MANAGEMENT_DB_NAME=”AppVManagement”

-

/MANAGEMENT_SERVER_MACHINE_USE_LOCAL

-

/MANAGEMENT_SERVER_INSTALL_ADMIN_ACCOUNT=”Domain\InstallAdminAccount”

  +**Custom instance of Microsoft SQL Server**: To use a custom instance of Microsoft SQL Server, use the following parameters: - ---- - - - - - - -

To install the Management database on a different computer than the Management server.

To use the default instance of Microsoft SQL Server, use the following parameters:

-
    -

  • /DB_PREDEPLOY_MANAGEMENT

    • -

  • /MANAGEMENT_DB_SQLINSTANCE_USE_DEFAULT

    • -

  • /MANAGEMENT_DB_NAME

    • -

  • /MANAGEMENT_REMOTE_SERVER_MACHINE_ACCOUNT

    • -

  • /MANAGEMENT_SERVER_INSTALL_ADMIN_ACCOUNT

    • -
-

To use a custom instance of Microsoft SQL Server, use these parameters:

-
    -

  • /DB_PREDEPLOY_MANAGEMENT

    • -

  • /MANAGEMENT_DB_CUSTOM_SQLINSTANCE

    • -

  • /MANAGEMENT_DB_NAME

    • -

  • /MANAGEMENT_REMOTE_SERVER_MACHINE_ACCOUNT

    • -

  • /MANAGEMENT_SERVER_INSTALL_ADMIN_ACCOUNT

    • -
-

Using a custom instance of Microsoft SQL Server example:

-

/appv_server_setup.exe /QUIET

-

/DB_PREDEPLOY_MANAGEMENT

-

/MANAGEMENT_DB_CUSTOM_SQLINSTANCE=”SqlInstanceName”

-

/MANAGEMENT_DB_NAME=”AppVManagement”

-

/MANAGEMENT_REMOTE_SERVER_MACHINE_ACCOUNT=”Domain\MachineAccount”

-

/MANAGEMENT_SERVER_INSTALL_ADMIN_ACCOUNT=”Domain\InstallAdminAccount”

+- /MANAGEMENT_SERVER +- /MANAGEMENT_ADMINACCOUNT +- /MANAGEMENT_WEBSITE_NAME +- /MANAGEMENT_WEBSITE_PORT +- /DB_PREDEPLOY_MANAGEMENT +- /MANAGEMENT_DB_CUSTOM_SQLINSTANCE +- /MANAGEMENT_DB_NAME - ---- - - - - - - -

To Install the publishing server.

To use the default instance of Microsoft SQL Server, use the following parameters:

-
    -

  • /PUBLISHING_SERVER

    • -

  • /PUBLISHING_MGT_SERVER

    • -

  • /PUBLISHING_WEBSITE_NAME

    • -

  • /PUBLISHING_WEBSITE_PORT

    • -
-

Using a custom instance of Microsoft SQL Server example:

-

/appv_server_setup.exe /QUIET

-

/PUBLISHING_SERVER

-

/PUBLISHING_MGT_SERVER=”http://ManagementServerName:ManagementPort”

-

/PUBLISHING_WEBSITE_NAME=”Microsoft AppV Publishing Service”

-

/PUBLISHING_WEBSITE_PORT=”8081”

+### Example for using a custom instance of Microsoft SQL Server: - ---- - - - - - - -

To Install the Reporting server and Reporting database on a local machine.

To use the default instance of Microsoft SQL Server, use the following parameters:

-
    -

  • /REPORTING _SERVER

    • -

  • /REPORTING _WEBSITE_NAME

    • -

  • /REPORTING _WEBSITE_PORT

    • -

  • /DB_PREDEPLOY_REPORTING

    • -

  • /REPORTING _DB_SQLINSTANCE_USE_DEFAULT

    • -

  • /REPORTING _DB_NAME

    • -
-

To use a custom instance of Microsoft SQL Server, use these parameters:

-
    -

  • /REPORTING _SERVER

    • -

  • /REPORTING _ADMINACCOUNT

    • -

  • /REPORTING _WEBSITE_NAME

    • -

  • /REPORTING _WEBSITE_PORT

    • -

  • /DB_PREDEPLOY_REPORTING

    • -

  • /REPORTING _DB_CUSTOM_SQLINSTANCE

    • -

  • /REPORTING _DB_NAME

    • -
-

Using a custom instance of Microsoft SQL Server example:

-
    -

  • /appv_server_setup.exe /QUIET

    • -

  • /REPORTING_SERVER

    • -

  • /REPORTING_WEBSITE_NAME=”Microsoft AppV Reporting Service”

    • -

  • /REPORTING_WEBSITE_PORT=”8082”

    • -

  • /DB_PREDEPLOY_REPORTING

    • -

  • /REPORTING_DB_CUSTOM_SQLINSTANCE=”SqlInstanceName”

    • -

  • /REPORTING_DB_NAME=”AppVReporting”

    • -
+/appv_server_setup.exe /QUIET
+/MANAGEMENT_SERVER
+/MANAGEMENT_ADMINACCOUNT="Domain\AdminGroup"
+/MANAGEMENT_WEBSITE_NAME="Microsoft AppV Management Service"
+/MANAGEMENT_WEBSITE_PORT="8080"
+/DB_PREDEPLOY_MANAGEMENT
+/MANAGEMENT_DB_CUSTOM_SQLINSTANCE="SqlInstanceName"
+/MANAGEMENT_DB_NAME="AppVManagement" - ---- - - - - - - -

To Install the Reporting server and using an existing Reporting database on a local machine.

To use the default instance of Microsoft SQL Server, use the following parameters:

-
    -

  • /REPORTING _SERVER

    • -

  • /REPORTING _WEBSITE_NAME

    • -

  • /REPORTING _WEBSITE_PORT

    • -

  • /EXISTING_REPORTING_DB_SQL_SERVER_USE_LOCAL

    • -

  • /EXISTING_REPORTING _DB_SQLINSTANCE_USE_DEFAULT

    • -

  • /EXISTING_REPORTING _DB_NAME

    • -
-

To use a custom instance of Microsoft SQL Server, use these parameters:

-
    -

  • /REPORTING _SERVER

    • -

  • /REPORTING _ADMINACCOUNT

    • -

  • /REPORTING _WEBSITE_NAME

    • -

  • /REPORTING _WEBSITE_PORT

    • -

  • /EXISTING_REPORTING_DB_SQL_SERVER_USE_LOCAL

    • -

  • /EXISTING_REPORTING _DB_CUSTOM_SQLINSTANCE

    • -

  • /EXISTING_REPORTING _DB_NAME

    • -
-

Using a custom instance of Microsoft SQL Server example:

-

/appv_server_setup.exe /QUIET

-

/REPORTING_SERVER

-

/REPORTING_WEBSITE_NAME=”Microsoft AppV Reporting Service”

-

/REPORTING_WEBSITE_PORT=”8082”

-

/EXISTING_REPORTING_DB_SQL_SERVER_USE_LOCAL

-

/EXISTING_REPORTING _DB_CUSTOM_SQLINSTANCE=”SqlInstanceName”

-

/EXITING_REPORTING_DB_NAME=”AppVReporting”

  +## To install the Management server using an existing Management database on a local machine - ---- - - - - - - -

To Install the Reporting server using an existing Reporting database on a remote machine.

To use the default instance of Microsoft SQL Server, use the following parameters:

-
    -

  • /REPORTING _SERVER

    • -

  • /REPORTING _WEBSITE_NAME

    • -

  • /REPORTING _WEBSITE_PORT

    • -

  • /EXISTING_REPORTING_DB_REMOTE_SQL_SERVER_NAME

    • -

  • /EXISTING_REPORTING _DB_SQLINSTANCE_USE_DEFAULT

    • -

  • /EXISTING_REPORTING _DB_NAME

    • -
-

To use a custom instance of Microsoft SQL Server, use these parameters:

-
    -

  • /REPORTING _SERVER

    • -

  • /REPORTING _ADMINACCOUNT

    • -

  • /REPORTING _WEBSITE_NAME

    • -

  • /REPORTING _WEBSITE_PORT

    • -

  • /EXISTING_REPORTING_DB_REMOTE_SQL_SERVER_NAME

    • -

  • /EXISTING_REPORTING _DB_CUSTOM_SQLINSTANCE

    • -

  • /EXISTING_REPORTING _DB_NAME

    • -
-

Using a custom instance of Microsoft SQL Server example:

-

/appv_server_setup.exe /QUIET

-

/REPORTING_SERVER

-

/REPORTING_WEBSITE_NAME=”Microsoft AppV Reporting Service”

-

/REPORTING_WEBSITE_PORT=”8082”

-

/EXISTING_REPORTING_DB_REMOTE_SQL_SERVER_NAME=”SqlServerMachine.DomainName”

-

/EXISTING_REPORTING _DB_CUSTOM_SQLINSTANCE=”SqlInstanceName”

-

/EXITING_REPORTING_DB_NAME=”AppVReporting”

+**Default instance of Microsoft SQL Server**: To use the default instance of Microsoft SQL Server, use the following parameters: - ---- - - - - - - -

To install the Reporting database on the same computer as the Reporting server.

To use the default instance of Microsoft SQL Server, use the following parameters:

-
    -

  • /DB_PREDEPLOY_REPORTING

    • -

  • /REPORTING _DB_SQLINSTANCE_USE_DEFAULT

    • -

  • /REPORTING _DB_NAME

    • -

  • /REPORTING_SERVER_MACHINE_USE_LOCAL

    • -

  • /REPORTING_SERVER_INSTALL_ADMIN_ACCOUNT

    • -
-

To use a custom instance of Microsoft SQL Server, use these parameters:

-
    -

  • /DB_PREDEPLOY_REPORTING

    • -

  • /REPORTING _DB_CUSTOM_SQLINSTANCE

    • -

  • /REPORTING _DB_NAME

    • -

  • /REPORTING_SERVER_MACHINE_USE_LOCAL

    • -

  • /REPORTING_SERVER_INSTALL_ADMIN_ACCOUNT

    • -
-

Using a custom instance of Microsoft SQL Server example:

-

/appv_server_setup.exe /QUIET

-

/DB_PREDEPLOY_REPORTING

-

/REPORTING_DB_CUSTOM_SQLINSTANCE=”SqlInstanceName”

-

/REPORTING_DB_NAME=”AppVReporting”

-

/REPORTING_SERVER_MACHINE_USE_LOCAL

-

/REPORTING_SERVER_INSTALL_ADMIN_ACCOUNT=”Domain\InstallAdminAccount”

+- /MANAGEMENT_SERVER +- /MANAGEMENT_ADMINACCOUNT +- /MANAGEMENT_WEBSITE_NAME +- /MANAGEMENT_WEBSITE_PORT +- /EXISTING_MANAGEMENT_DB_SQL_SERVER_USE_LOCAL +- /EXISTING_MANAGEMENT_DB_SQLINSTANCE_USE_DEFAULT +- /EXISTING_MANAGEMENT_DB_NAME - ---- - - - - - - -

To install the Reporting database on a different computer than the Reporting server.

To use the default instance of Microsoft SQL Server, use the following parameters:

-
    -

  • /DB_PREDEPLOY_REPORTING

    • -

  • /REPORTING _DB_SQLINSTANCE_USE_DEFAULT

    • -

  • /REPORTING _DB_NAME

    • -

  • /REPORTING_REMOTE_SERVER_MACHINE_ACCOUNT

    • -

  • /REPORTING_SERVER_INSTALL_ADMIN_ACCOUNT

    • -
-

To use a custom instance of Microsoft SQL Server, use these parameters:

-
    -

  • /DB_PREDEPLOY_REPORTING

    • -

  • /REPORTING _DB_CUSTOM_SQLINSTANCE

    • -

  • /REPORTING _DB_NAME

    • -

  • /REPORTING_REMOTE_SERVER_MACHINE_ACCOUNT

    • -

  • /REPORTING_SERVER_INSTALL_ADMIN_ACCOUNT

    • -
-

Using a custom instance of Microsoft SQL Server example:

-

/appv_server_setup.exe /QUIET

-

/DB_PREDEPLOY_REPORTING

-

/REPORTING_DB_CUSTOM_SQLINSTANCE=”SqlInstanceName”

-

/REPORTING_DB_NAME=”AppVReporting”

-

/REPORTING_REMOTE_SERVER_MACHINE_ACCOUNT=”Domain\MachineAccount”

-

/REPORTING_SERVER_INSTALL_ADMIN_ACCOUNT=”Domain\InstallAdminAccount”

+**Custom instance of Microsoft SQL Server**: To use a custom instance of Microsoft SQL Server, use these parameters: -**Parameter Definitions** +- /MANAGEMENT_SERVER +- /MANAGEMENT_ADMINACCOUNT +- /MANAGEMENT_WEBSITE_NAME +- /MANAGEMENT_WEBSITE_PORT +- /EXISTING_MANAGEMENT_DB_SQL_SERVER_USE_LOCAL +- /EXISTING_MANAGEMENT_DB_CUSTOM_SQLINSTANCE +- /EXISTING_MANAGEMENT_DB_NAME -**General Parameters** +### Example for using a custom instance of Microsoft SQL Server: - ---- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterInformation

/QUIET

Specifies silent install.

/UNINSTALL

Specifies an uninstall.

/LAYOUT

Specifies layout action. This extracts the MSIs and script files to a folder without actually installing the product. No value is expected.

/LAYOUTDIR

Specifies the layout directory. Takes a string. For example, /LAYOUTDIR=”C:\Application Virtualization Server”

/INSTALLDIR

Specifies the installation directory. Takes a string. E.g. /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. Example usage: /ACCEPTEULA or /ACCEPTEULA=1.

+/appv_server_setup.exe /QUIET
+/MANAGEMENT_SERVER
+/MANAGEMENT_ADMINACCOUNT="Domain\AdminGroup"
+/MANAGEMENT_WEBSITE_NAME="Microsoft AppV Management Service"
+/MANAGEMENT_WEBSITE_PORT="8080"
+/EXISTING_MANAGEMENT_DB_SQL_SERVER_USE_LOCAL
+/EXISTING_MANAGEMENT_DB_CUSTOM_SQLINSTANCE ="SqlInstanceName"
+/EXISTING_MANAGEMENT_DB_NAME ="AppVManagement" -**Management Server Installation Parameters** +## To install the Management server using an existing Management database on a remote machine - ---- - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterInformation

/MANAGEMENT_SERVER

Specifies that the management server will be installed. No value is expected

/MANAGEMENT_ADMINACCOUNT

Specifies the account that will be allowed to Administrator access to the management server This account can be an individual user account or a group. Example usage: /MANAGEMENT_ADMINACCOUNT=”mydomain\admin”. If /MANAGEMENT_SERVER is not specified, this will be ignored. Specifies the account that will be allowed to Administrator access to the management server. This can be a user account or a group. For example, /MANAGEMENT_ADMINACCOUNT="mydomain\admin".

/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.

+**Default instance of Microsoft SQL Server**: To use the default instance of Microsoft SQL Server, use the following parameters: -**Parameters for the Management Server Database** +- /MANAGEMENT_SERVER +- /MANAGEMENT_ADMINACCOUNT +- /MANAGEMENT_WEBSITE_NAME +- /MANAGEMENT_WEBSITE_PORT +- /EXISTING_MANAGEMENT_DB_REMOTE_SQL_SERVER_NAME +- /EXISTING_MANAGEMENT_DB_SQLINSTANCE_USE_DEFAULT +- /EXISTING_MANAGEMENT_DB_NAME - ---- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterInformation

/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. Example usage: /MANAGEMENT_DB_ CUSTOM_SQLINSTANCE=”MYSQLSERVER”. If /DB_PREDEPLOY_MANAGEMENT is not specified, this will be ignored.

/MANAGEMENT_DB_NAME

Specifies the name of the new management database that should be created. Example usage: /MANAGEMENT_DB_NAME=”AppVMgmtDB”. If /DB_PREDEPLOY_MANAGEMENT is not specified, this will be ignored.

/MANAGEMENT_SERVER_MACHINE_USE_LOCAL

Indicates if the management server that will be accessing the database is installed on the local server. Switch parameter so no value is expected.

/MANAGEMENT_REMOTE_SERVER_MACHINE_ACCOUNT

Specifies the machine account of the remote machine that the management server will be installed on. Example usage: /MANAGEMENT_REMOTE_SERVER_MACHINE_ACCOUNT=”domain\computername”

/MANAGEMENT_SERVER_INSTALL_ADMIN_ACCOUNT

Indicates the Administrator account that will be used to install the management server. Example usage: /MANAGEMENT_SERVER_INSTALL_ADMIN_ACCOUNT =”domain\alias”

+**Custom instance of Microsoft SQL Server**: To use a custom instance of Microsoft SQL Server, use these parameters: -**Parameters for Installing Publishing Server** +- /MANAGEMENT_SERVER +- /MANAGEMENT_ADMINACCOUNT +- /MANAGEMENT_WEBSITE_NAME +- /MANAGEMENT_WEBSITE_PORT +- /EXISTING_MANAGEMENT_DB_REMOTE_SQL_SERVER_NAME +- /EXISTING_MANAGEMENT_DB_CUSTOM_SQLINSTANCE +- /EXISTING_MANAGEMENT_DB_NAME - ---- - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterInformation

/PUBLISHING_SERVER

Specifies that the Publishing Server will be installed. No value is expected

/PUBLISHING_MGT_SERVER

Specifies the URL to Management Service the Publishing server will connect to. Example usage: http://<management server name>:<Management server port number>. If /PUBLISHING_SERVER is not used, this parameter will be ignored

/PUBLISHING_WEBSITE_NAME

Specifies name of the website that will be created for the publishing service. For example, /PUBLISHING_WEBSITE_NAME=”Microsoft App-V Publishing Service”

/PUBLISHING_WEBSITE_PORT

Specifies the port number used by the publishing service. For example, /PUBLISHING_WEBSITE_PORT=83

+### Example for using a custom instance of Microsoft SQL Server: -**Parameters for Reporting Server** +/appv_server_setup.exe /QUIET
+/MANAGEMENT_SERVER
+/MANAGEMENT_ADMINACCOUNT="Domain\AdminGroup"
+/MANAGEMENT_WEBSITE_NAME="Microsoft AppV Management Service"
+/MANAGEMENT_WEBSITE_PORT="8080"
+/EXISTING_MANAGEMENT_DB_REMOTE_SQL_SERVER_NAME="SqlServermachine.domainName"
+/EXISTING_MANAGEMENT_DB_CUSTOM_SQLINSTANCE ="SqlInstanceName"
+/EXISTING_MANAGEMENT_DB_NAME ="AppVManagement" - ---- - - - - - - - - - - - - - - - - - - - +## To install the Management database and the Management Server on the same computer + +**Default instance of Microsoft SQL Server**: To use the default instance of Microsoft SQL Server, use the following parameters: + +- /DB_PREDEPLOY_MANAGEMENT +- /MANAGEMENT_DB_SQLINSTANCE_USE_DEFAULT +- /MANAGEMENT_DB_NAME +- /MANAGEMENT_SERVER_MACHINE_USE_LOCAL +- /MANAGEMENT_SERVER_INSTALL_ADMIN_ACCOUNT + +**Custom instance of Microsoft SQL Server**: To use a custom instance of Microsoft SQL Server, use these parameters: + +- /DB_PREDEPLOY_MANAGEMENT +- /MANAGEMENT_DB_CUSTOM_SQLINSTANCE +- /MANAGEMENT_DB_NAME +- /MANAGEMENT_SERVER_MACHINE_USE_LOCAL +- /MANAGEMENT_SERVER_INSTALL_ADMIN_ACCOUNT + +### Example for using a custom instance of Microsoft SQL Server: + +/appv_server_setup.exe /QUIET
+/DB_PREDEPLOY_MANAGEMENT
+/MANAGEMENT_DB_CUSTOM_SQLINSTANCE="SqlInstanceName"
+/MANAGEMENT_DB_NAME="AppVManagement"
+/MANAGEMENT_SERVER_MACHINE_USE_LOCAL
+/MANAGEMENT_SERVER_INSTALL_ADMIN_ACCOUNT="Domain\InstallAdminAccount" + +## To install the Management database on a different computer than the Management server + +**Default instance of Microsoft SQL Server**: To use the default instance of Microsoft SQL Server, use the following parameters: + +- /DB_PREDEPLOY_MANAGEMENT +- /MANAGEMENT_DB_SQLINSTANCE_USE_DEFAULT +- /MANAGEMENT_DB_NAME +- /MANAGEMENT_REMOTE_SERVER_MACHINE_ACCOUNT +- /MANAGEMENT_SERVER_INSTALL_ADMIN_ACCOUNT + +**Custom instance of Microsoft SQL Server**: To use a custom instance of Microsoft SQL Server, use these parameters: + +- /DB_PREDEPLOY_MANAGEMENT +- /MANAGEMENT_DB_CUSTOM_SQLINSTANCE +- /MANAGEMENT_DB_NAME +- /MANAGEMENT_REMOTE_SERVER_MACHINE_ACCOUNT +- /MANAGEMENT_SERVER_INSTALL_ADMIN_ACCOUNT + +### Example for using a custom instance of Microsoft SQL Server: + +/appv_server_setup.exe /QUIET
+/DB_PREDEPLOY_MANAGEMENT
+/MANAGEMENT_DB_CUSTOM_SQLINSTANCE="SqlInstanceName"
+/MANAGEMENT_DB_NAME="AppVManagement"
+/MANAGEMENT_REMOTE_SERVER_MACHINE_ACCOUNT="Domain\MachineAccount"
+/MANAGEMENT_SERVER_INSTALL_ADMIN_ACCOUNT="Domain\InstallAdminAccount" + +## To install the Publishing server + +**Default instance of Microsoft SQL Server**: To use the default instance of Microsoft SQL Server, use the following parameters: + +- /PUBLISHING_SERVER +- /PUBLISHING_MGT_SERVER +- /PUBLISHING_WEBSITE_NAME +- /PUBLISHING_WEBSITE_PORT + +### Example + +/appv_server_setup.exe /QUIET
+/PUBLISHING_SERVER
+/PUBLISHING_MGT_SERVER="http://ManagementServerName:ManagementPort"
+/PUBLISHING_WEBSITE_NAME="Microsoft AppV Publishing Service"
+/PUBLISHING_WEBSITE_PORT="8081" + +## To install the Reporting server and Reporting database on a local machine + +**Default instance of Microsoft SQL Server**: To use the default instance of Microsoft SQL Server, use the following parameters: + +- /REPORTING _SERVER +- /REPORTING _WEBSITE_NAME +- /REPORTING _WEBSITE_PORT +- /DB_PREDEPLOY_REPORTING +- /REPORTING _DB_SQLINSTANCE_USE_DEFAULT +- /REPORTING _DB_NAME + +**Custom instance of Microsoft SQL Server**: To use a custom instance of Microsoft SQL Server, use these parameters: + +- /REPORTING _SERVER +- /REPORTING _ADMINACCOUNT +- /REPORTING _WEBSITE_NAME +- /REPORTING _WEBSITE_PORT +- /DB_PREDEPLOY_REPORTING +- /REPORTING _DB_CUSTOM_SQLINSTANCE +- /REPORTING _DB_NAME + +### Example for using a custom instance of Microsoft SQL Server: + +/appv_server_setup.exe /QUIET
+/REPORTING_SERVER
+/REPORTING_WEBSITE_NAME="Microsoft AppV Reporting Service"
+/REPORTING_WEBSITE_PORT="8082"
+/DB_PREDEPLOY_REPORTING
+/REPORTING_DB_CUSTOM_SQLINSTANCE="SqlInstanceName"
+/REPORTING_DB_NAME="AppVReporting" + +## To install the Reporting server using an existing Reporting database on a local machine + +**Default instance of Microsoft SQL Server**: To use the default instance of Microsoft SQL Server, use the following parameters: + +- /REPORTING _SERVER +- /REPORTING _WEBSITE_NAME +- /REPORTING _WEBSITE_PORT +- /EXISTING_REPORTING_DB_SQL_SERVER_USE_LOCAL +- /EXISTING_REPORTING_DB_SQLINSTANCE_USE_DEFAULT +- /EXISTING_REPORTING_DB_NAME + +**Custom instance of Microsoft SQL Server**: To use a custom instance of Microsoft SQL Server, use these parameters: + +- /REPORTING _SERVER +- /REPORTING _ADMINACCOUNT +- /REPORTING _WEBSITE_NAME +- /REPORTING _WEBSITE_PORT +- /EXISTING_REPORTING_DB_SQL_SERVER_USE_LOCAL +- /EXISTING_REPORTING _DB_CUSTOM_SQLINSTANCE +- /EXISTING_REPORTING _DB_NAME + +### Example for using a custom instance of Microsoft SQL Server: + +/appv_server_setup.exe /QUIET
+/REPORTING_SERVER
+/REPORTING_WEBSITE_NAME="Microsoft AppV Reporting Service"
+/REPORTING_WEBSITE_PORT="8082"
+/EXISTING_REPORTING_DB_SQL_SERVER_USE_LOCAL
+/EXISTING_REPORTING _DB_CUSTOM_SQLINSTANCE="SqlInstanceName"
+/EXITING_REPORTING_DB_NAME="AppVReporting" + +## To install the Reporting server using an existing Reporting database on a remote machine + +**Default instance of Microsoft SQL Server**: To use the default instance of Microsoft SQL Server, use the following parameters: + +- /REPORTING _SERVER +- /REPORTING _WEBSITE_NAME +- /REPORTING _WEBSITE_PORT +- /EXISTING_REPORTING_DB_REMOTE_SQL_SERVER_NAME +- /EXISTING_REPORTING _DB_SQLINSTANCE_USE_DEFAULT +- /EXISTING_REPORTING _DB_NAME + +**Custom instance of Microsoft SQL Server**: To use a custom instance of Microsoft SQL Server, use these parameters: + +- /REPORTING _SERVER +- /REPORTING _ADMINACCOUNT +- /REPORTING _WEBSITE_NAME +- /REPORTING _WEBSITE_PORT +- /EXISTING_REPORTING_DB_REMOTE_SQL_SERVER_NAME +- /EXISTING_REPORTING _DB_CUSTOM_SQLINSTANCE +- /EXISTING_REPORTING _DB_NAME + +### Example for using a custom instance of Microsoft SQL Server: + +/appv_server_setup.exe /QUIET
+/REPORTING_SERVER
+/REPORTING_WEBSITE_NAME="Microsoft AppV Reporting Service"
+/REPORTING_WEBSITE_PORT="8082"
+/EXISTING_REPORTING_DB_REMOTE_SQL_SERVER_NAME="SqlServerMachine.DomainName"
+/EXISTING_REPORTING _DB_CUSTOM_SQLINSTANCE="SqlInstanceName"
+/EXITING_REPORTING_DB_NAME="AppVReporting" + +## To install the Reporting database on the same computer as the Reporting server + +**Default instance of Microsoft SQL Server**: To use the default instance of Microsoft SQL Server, use the following parameters: + +- /DB_PREDEPLOY_REPORTING +- /REPORTING_DB_SQLINSTANCE_USE_DEFAULT +- /REPORTING_DB_NAME +- /REPORTING_SERVER_MACHINE_USE_LOCAL +- /REPORTING_SERVER_INSTALL_ADMIN_ACCOUNT + +**Custom instance of Microsoft SQL Server**: To use a custom instance of Microsoft SQL Server, use these parameters: + +- /DB_PREDEPLOY_REPORTING +- /REPORTING _DB_CUSTOM_SQLINSTANCE +- /REPORTING _DB_NAME +- /REPORTING_SERVER_MACHINE_USE_LOCAL +- /REPORTING_SERVER_INSTALL_ADMIN_ACCOUNT + +### Example for using a custom instance of Microsoft SQL Server: + +/appv_server_setup.exe /QUIET
+/DB_PREDEPLOY_REPORTING
+/REPORTING_DB_CUSTOM_SQLINSTANCE="SqlInstanceName"
+/REPORTING_DB_NAME="AppVReporting"
+/REPORTING_SERVER_MACHINE_USE_LOCAL
+/REPORTING_SERVER_INSTALL_ADMIN_ACCOUNT="Domain\InstallAdminAccount" + +## To install the Reporting database on a different computer than the Reporting server + +**Default instance of Microsoft SQL Server**: To use the default instance of Microsoft SQL Server, use the following parameters: + +- /DB_PREDEPLOY_REPORTING +- /REPORTING _DB_SQLINSTANCE_USE_DEFAULT +- /REPORTING _DB_NAME +- /REPORTING_REMOTE_SERVER_MACHINE_ACCOUNT +- /REPORTING_SERVER_INSTALL_ADMIN_ACCOUNT + +**Custom instance of Microsoft SQL Server**: To use a custom instance of Microsoft SQL Server, use these parameters: + +- /DB_PREDEPLOY_REPORTING +- /REPORTING _DB_CUSTOM_SQLINSTANCE +- /REPORTING _DB_NAME +- /REPORTING_REMOTE_SERVER_MACHINE_ACCOUNT +- /REPORTING_SERVER_INSTALL_ADMIN_ACCOUNT + +### Example for using a custom instance of Microsoft SQL Server: + +Using a custom instance of Microsoft SQL Server example:
+/appv_server_setup.exe /QUIET
+/DB_PREDEPLOY_REPORTING
+/REPORTING_DB_CUSTOM_SQLINSTANCE="SqlInstanceName"
+/REPORTING_DB_NAME="AppVReporting"
+/REPORTING_REMOTE_SERVER_MACHINE_ACCOUNT="Domain\MachineAccount"
+/REPORTING_SERVER_INSTALL_ADMIN_ACCOUNT="Domain\InstallAdminAccount" + +## Parameter definitions + +- [General parameters](#parameter-definitions-for-general-parameters) +- [Management Server installation parameters](#parameter-definitions-for-management-server-installation-parameters) +- [Management Server Database parameters](#parameter-definitions-for-the-management-server-database) +- [Publishing Server installation parameters](#parameter-definitions-for-publishing-server-installation-parameters) +- [Reporting Server parameters](#parameter-definitions-for-reporting-server) +- [Parameters for using an existing Reporting Server database](#parameters-for-using-an-existing-reporting-server-database) +- [Reporting Server database installation parameters](#parameter-definitions-for-reporting-server-database-installation) +- [Parameters for using an existing Management Server database](#parameters-for-using-an-existing-management-server-database) + +### Parameter definitions for general parameters + +| Parameter | Description | +|-----------|-------------| +| /QUIET | Specifies silent install. | +| /UNINSTALL | Specifies an uninstall. | +| /LAYOUT | Specifies layout action. This extracts the MSIs and script files to a folder without actually installing the product. No value is expected. | +| /LAYOUTDIR | Specifies the layout directory. Takes a string. For example, /LAYOUTDIR="C:\Application Virtualization Server" | +| /INSTALLDIR | Specifies the installation directory. Takes a string. E.g. /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. Example usage: **/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_ADMINACCOUNT | Specifies the account that will be allowed to Administrator access to the management server This account can be an individual user account or a group. Example usage: **/MANAGEMENT_ADMINACCOUNT="mydomain\admin"**. If **/MANAGEMENT_SERVER** is not specified, this will be ignored. Specifies the account that will be allowed to Administrator access to the management server. This can be a user account or a group. For example, **/MANAGEMENT_ADMINACCOUNT="mydomain\admin"**. | +| /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. | + +### Parameter definitions for the Management Server Database + +| 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 | +| /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. Example usage: **/MANAGEMENT_DB_CUSTOM_SQLINSTANCE="MYSQLSERVER"**. If /DB_PREDEPLOY_MANAGEMENT is not specified, this will be ignored. | +| /MANAGEMENT_DB_NAME | Specifies the name of the new management database that should be created. Example usage: **/MANAGEMENT_DB_NAME="AppVMgmtDB"**. If /DB_PREDEPLOY_MANAGEMENT is not specified, this will be ignored. | +| /MANAGEMENT_SERVER_MACHINE_USE_LOCAL | Indicates if the management server that will be accessing the database is installed on the local server. Switch parameter so no value is expected. | +| /MANAGEMENT_REMOTE_SERVER_MACHINE_ACCOUNT | Specifies the machine account of the remote machine that the management server will be installed on. Example usage: **/MANAGEMENT_REMOTE_SERVER_MACHINE_ACCOUNT="domain\computername"** | +| /MANAGEMENT_SERVER_INSTALL_ADMIN_ACCOUNT | Indicates the Administrator account that will be used to install the management server. Example usage: **/MANAGEMENT_SERVER_INSTALL_ADMIN_ACCOUNT ="domain\alias"** | + +### Parameter definitions for Publishing Server installation parameters + +| Parameter | Description | +|-----------|-------------| +| /PUBLISHING_SERVER | Specifies that the Publishing Server will be installed. No value is expected | +| /PUBLISHING_MGT_SERVER | Specifies the URL to Management Service the Publishing server will connect to. Example usage: **http://<management server name>:<Management server port number>**. If /PUBLISHING_SERVER is not used, this parameter will be ignored | +| /PUBLISHING_WEBSITE_NAME | Specifies name of the website that will be created for the publishing service. For example, /PUBLISHING_WEBSITE_NAME="Microsoft App-V Publishing Service" | +| /PUBLISHING_WEBSITE_PORT | Specifies the port number used by the publishing service. For example, /PUBLISHING_WEBSITE_PORT=83 | + +### Parameter definitions for Reporting Server + +| Parameter | Description | +|-----------|-------------| +| /REPORTING_SERVER | Specifies that the Reporting Server will be installed. No value is expected | +| /REPORTING_WEBSITE_NAME | Specifies name of the website that will be created for the Reporting Service. E.g. /REPORTING_WEBSITE_NAME="Microsoft App-V ReportingService" | +| /REPORTING_WEBSITE_PORT | Specifies the port number that the Reporting Service will use. E.g. /REPORTING_WEBSITE_PORT=82 |
ParameterInformation

/REPORTING_SERVER

Specifies that the Reporting Server will be installed. No value is expected

/REPORTING_WEBSITE_NAME

Specifies name of the website that will be created for the Reporting Service. E.g. /REPORTING_WEBSITE_NAME="Microsoft App-V ReportingService"

/REPORTING_WEBSITE_PORT

Specifies the port number that the Reporting Service will use. E.g. /REPORTING_WEBSITE_PORT=82
  -**Parameters for using an Existing Reporting Server Database** +### Parameters for using an existing Reporting Server database - ---- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterInformation

/EXISTING_REPORTING_DB_SQL_SERVER_USE_LOCAL

Indicates that the Microsoft SQL Server is installed on the local server. Switch parameter so no value is expected.

/EXISTING_REPORTING_DB_REMOTE_SQL_SERVER_NAME

Specifies the name of the remote computer that SQL Server is installed on. Takes a string. E.g. /EXISTING_REPORTING_DB_ REMOTE_SQL_SERVER_NAME="mycomputer1"

/EXISTING_ REPORTING _DB_SQLINSTANCE_USE_DEFAULT

Indicates that the default SQL instance is to be used. Switch parameter so no value is expected.

/EXISTING_ REPORTING_DB_CUSTOM_SQLINSTANCE

Specifies the name of the custom SQL instance that should be used. Takes a string. E.g. /EXISTING_REPORTING_DB_ CUSTOM_SQLINSTANCE="MYSQLSERVER"

/EXISTING_ REPORTING _DB_NAME

Specifies the name of the existing Reporting database that should be used. Takes a string. E.g. /EXISITING_REPORTING_DB_NAME="AppVReporting"

  +| Parameter | Description | +|-----------|-------------| +| /EXISTING\_REPORTING\_DB_SQL_SERVER_USE_LOCAL | Indicates that the Microsoft SQL Server is installed on the local server. Switch parameter so no value is expected. | +| /EXISTING_REPORTING_DB_REMOTE_SQL_SERVER_NAME | Specifies the name of the remote computer that SQL Server is installed on. Takes a string. E.g. /EXISTING_REPORTING_DB_REMOTE_SQL_SERVER_NAME="mycomputer1" | +| /EXISTING_REPORTING_DB_SQLINSTANCE_USE_DEFAULT | Indicates that the default SQL instance is to be used. Switch parameter so no value is expected. | +| /EXISTING_REPORTING_DB_CUSTOM_SQLINSTANCE | Specifies the name of the custom SQL instance that should be used. Takes a string. E.g. /EXISTING_REPORTING_DB_CUSTOM_SQLINSTANCE="MYSQLSERVER" | +| /EXISTING_REPORTING_DB_NAME | Specifies the name of the existing Reporting database that should be used. Takes a string. E.g. /EXISTING_REPORTING_DB_NAME="AppVReporting" | -**Parameters for installing Reporting Server Database** +### Parameter definitions for Reporting Server database installation - ---- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterInformation

/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. E.g. /REPORTING_DB_ CUSTOM_SQLINSTANCE="MYSQLSERVER"

/REPORTING_DB_NAME

Specifies the name of the new Reporting database that should be created. Takes a string. E.g. /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. Switch parameter so no value is expected.

/REPORTING_REMOTE_SERVER_MACHINE_ACCOUNT

Specifies the machine account of the remote machine that the Reporting server will be installed on. Takes a string. E.g. /REPORTING_REMOTE_SERVER_MACHINE_ACCOUNT = "domain\computername"

/REPORTING_SERVER_INSTALL_ADMIN_ACCOUNT

Indicates the Administrator account that will be used to install the App-V Reporting Server. Takes a string. E.g. /REPORTING_SERVER_INSTALL_ADMIN_ACCOUNT = "domain\alias"

+| Parameter | Description | +|-----------|-------------| +| /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. E.g. /REPORTING_DB_CUSTOM_SQLINSTANCE="MYSQLSERVER" | +| /REPORTING_DB_NAME | Specifies the name of the new Reporting database that should be created. Takes a string. E.g. /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. Switch parameter so no value is expected. | +| /REPORTING_REMOTE_SERVER_MACHINE_ACCOUNT | Specifies the machine account of the remote machine that the Reporting server will be installed on. Takes a string. E.g. /REPORTING_REMOTE_SERVER_MACHINE_ACCOUNT = "domain\computername" | +| /REPORTING_SERVER_INSTALL_ADMIN_ACCOUNT | Indicates the Administrator account that will be used to install the App-V Reporting Server. Takes a string. E.g. /REPORTING_SERVER_INSTALL_ADMIN_ACCOUNT = "domain\alias" | -**Parameters for using an existing Management Server Database** +### Parameters for using an existing Management Server database - ---- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterInformation

/EXISTING_MANAGEMENT_DB_SQL_SERVER_USE_LOCAL

Indicates that the SQL Server is installed on the local server. Switch parameter so no value is expected.If /DB_PREDEPLOY_MANAGEMENT is specified, this will be ignored.

/EXISTING_MANAGEMENT_DB_REMOTE_SQL_SERVER_NAME

Specifies the name of the remote computer that SQL Server is installed on. Takes a string. E.g. /EXISTING_MANAGEMENT_DB_ REMOTE_SQL_SERVER_NAME="mycomputer1"

/EXISTING_ MANAGEMENT_DB_SQLINSTANCE_USE_DEFAULT

Indicates that the default SQL instance is to be used. Switch parameter so no value is expected. If /DB_PREDEPLOY_MANAGEMENT is specified, this will be ignored.

/EXISTING_MANAGEMENT_DB_ CUSTOM_SQLINSTANCE

Specifies the name of the custom SQL instance that will be used. Example usage /EXISTING_MANAGEMENT_DB_ CUSTOM_SQLINSTANCE=”AppVManagement”. If /DB_PREDEPLOY_MANAGEMENT is specified, this will be ignored.

/EXISTING_MANAGEMENT_DB_NAME

Specifies the name of the existing management database that should be used. Example usage: /EXISITING_MANAGEMENT_DB_NAME=”AppVMgmtDB”. If /DB_PREDEPLOY_MANAGEMENT is specified, this will be ignored.

+| Parameter | Description | +|-----------|-------------| +| /EXISTING\_MANAGEMENT\_DB_SQL_SERVER_USE_LOCAL | Indicates that the SQL Server is installed on the local server. Switch parameter so no value is expected.If /DB_PREDEPLOY_MANAGEMENT is specified, this will be ignored. | +| /EXISTING_MANAGEMENT_DB_REMOTE_SQL_SERVER_NAME | Specifies the name of the remote computer that SQL Server is installed on. Takes a string. E.g. /EXISTING_MANAGEMENT_DB_REMOTE_SQL_SERVER_NAME="mycomputer1" | +| /EXISTING_MANAGEMENT_DB_SQLINSTANCE_USE_DEFAULT | Indicates that the default SQL instance is to be used. Switch parameter so no value is expected. If /DB_PREDEPLOY_MANAGEMENT is specified, this will be ignored. | +| /EXISTING_MANAGEMENT_DB_CUSTOM_SQLINSTANCE | Specifies the name of the custom SQL instance that will be used. Example usage **/EXISTING_MANAGEMENT_DB_CUSTOM_SQLINSTANCE="AppVManagement"**. If /DB_PREDEPLOY_MANAGEMENT is specified, this will be ignored. | +| /EXISTING_MANAGEMENT_DB_NAME | Specifies the name of the existing management database that should be used. Example usage: **/EXISTING_MANAGEMENT_DB_NAME="AppVMgmtDB"**. If /DB_PREDEPLOY_MANAGEMENT is specified, this will be ignored. | ## Have a suggestion for App-V? From b5c32f0295b6c445f49a776cd08165e62899ab5c Mon Sep 17 00:00:00 2001 From: JanKeller1 Date: Wed, 24 Aug 2016 19:48:39 -0700 Subject: [PATCH 2/2] Small fixes that came from visual test pass --- ...ation-publishing-and-client-interaction.md | 4 +- windows/manage/appv-capacity-planning.md | 4 +- windows/manage/appv-evaluating-appv.md | 4 +- .../manage/appv-high-level-architecture.md | 4 +- ...porting-server-on-a-standalone-computer.md | 5 +- ...v-planning-folder-redirection-with-appv.md | 4 +- ...ppv-planning-for-using-appv-with-office.md | 6 ++ ...ctronic-software-distribution-solutions.md | 5 + windows/manage/appv-reporting.md | 98 +++++++------------ .../manage/appv-supported-configurations.md | 2 +- 10 files changed, 57 insertions(+), 79 deletions(-) diff --git a/windows/manage/appv-application-publishing-and-client-interaction.md b/windows/manage/appv-application-publishing-and-client-interaction.md index 494ffc80ab..6b0f31cb3f 100644 --- a/windows/manage/appv-application-publishing-and-client-interaction.md +++ b/windows/manage/appv-application-publishing-and-client-interaction.md @@ -67,9 +67,7 @@ The Sequencer creates App-V packages and produces a virtualized application. The -  - -For information about sequencing, see [How to Sequence a New Application with App-V](https://technet.microsoft.com/itpro/windows/manage/appv-sequence-a-new-application). +For information about sequencing, see [How to Sequence a New Application with App-V](appv-sequence-a-new-application.md). ## What’s in the appv file? diff --git a/windows/manage/appv-capacity-planning.md b/windows/manage/appv-capacity-planning.md index d0e054caa1..bf7e512509 100644 --- a/windows/manage/appv-capacity-planning.md +++ b/windows/manage/appv-capacity-planning.md @@ -28,8 +28,8 @@ Before you design the App-V infrastructure, determine the project’s scope. The --++ diff --git a/windows/manage/appv-evaluating-appv.md b/windows/manage/appv-evaluating-appv.md index d1fbce40ed..c125dd8975 100644 --- a/windows/manage/appv-evaluating-appv.md +++ b/windows/manage/appv-evaluating-appv.md @@ -18,7 +18,7 @@ Before you deploy App-V into a production environment, you should evaluate it in ## Configure lab computers for App-V Evaluation -Use the following link for information about setting up the App-V sequencer on a computer in your lab environment. +Use the following links for information about setting up the App-V sequencer on a computer in your lab environment. ### Installing the App-V Sequencer and Creating Packages @@ -38,7 +38,7 @@ Use the following links for information about setting up the App-V server in you ### Enabling the App-V Client -Use the following link for more information about creating and managing virtualized packages in your lab environment. +Use the following links for more information about creating and managing virtualized packages in your lab environment. - [Enable the App-V desktop client](appv-enable-the-app-v-desktop-client.md) diff --git a/windows/manage/appv-high-level-architecture.md b/windows/manage/appv-high-level-architecture.md index ac2a699fcb..b44b2ca181 100644 --- a/windows/manage/appv-high-level-architecture.md +++ b/windows/manage/appv-high-level-architecture.md @@ -23,8 +23,8 @@ A typical App-V implementation consists of the following elements.
--++ diff --git a/windows/manage/appv-install-the-reporting-server-on-a-standalone-computer.md b/windows/manage/appv-install-the-reporting-server-on-a-standalone-computer.md index 584b535d4e..10915488b0 100644 --- a/windows/manage/appv-install-the-reporting-server-on-a-standalone-computer.md +++ b/windows/manage/appv-install-the-reporting-server-on-a-standalone-computer.md @@ -16,10 +16,7 @@ ms.prod: w10 Use the following procedure to install the reporting server on a standalone computer and connect it to the database. -**Important**   -Before performing the following procedure you should read and understand [About App-V Reporting](appv-reporting.md). - -  +> **Important**  Before performing the following procedure you should read and understand [About App-V Reporting](appv-reporting.md). **To install the reporting server on a standalone computer and connect it to the database** diff --git a/windows/manage/appv-planning-folder-redirection-with-appv.md b/windows/manage/appv-planning-folder-redirection-with-appv.md index 17065dcbbd..fbbe90799e 100644 --- a/windows/manage/appv-planning-folder-redirection-with-appv.md +++ b/windows/manage/appv-planning-folder-redirection-with-appv.md @@ -116,8 +116,8 @@ The following table describes how folder redirection works when %AppData% is red
--++ diff --git a/windows/manage/appv-planning-for-using-appv-with-office.md b/windows/manage/appv-planning-for-using-appv-with-office.md index b156a41f4c..46907201bd 100644 --- a/windows/manage/appv-planning-for-using-appv-with-office.md +++ b/windows/manage/appv-planning-for-using-appv-with-office.md @@ -304,3 +304,9 @@ The Office 2013 App-V package supports the following integration points with the ## Have a suggestion for App-V? Add or vote on suggestions on the [Application Virtualization feedback site](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 + +- [Deploying Microsoft Office 2013 by Using App-V](appv-deploying-microsoft-office-2013-with-appv.md) + +- [Deploying Microsoft Office 2010 by Using App-V](appv-deploying-microsoft-office-2010-wth-appv.md) diff --git a/windows/manage/appv-planning-to-deploy-appv-with-electronic-software-distribution-solutions.md b/windows/manage/appv-planning-to-deploy-appv-with-electronic-software-distribution-solutions.md index 81198bde84..fa9a2274ee 100644 --- a/windows/manage/appv-planning-to-deploy-appv-with-electronic-software-distribution-solutions.md +++ b/windows/manage/appv-planning-to-deploy-appv-with-electronic-software-distribution-solutions.md @@ -29,3 +29,8 @@ Add or vote on suggestions on the [Application Virtualization feedback site](htt ## Related topics - [Planning to deploy App-V](appv-planning-to-deploy-appv.md) + +- [How to deploy App-V Packages Using Electronic Software Distribution](appv-deploy-appv-packages-with-electronic-software-distribution-solutions.md) + +- [How to Enable Only Administrators to Publish Packages by Using an ESD](appv-enable-administrators-to-publish-packages-with-electronic-software-distribution-solutions.md) + diff --git a/windows/manage/appv-reporting.md b/windows/manage/appv-reporting.md index 0aced8808d..69722473af 100644 --- a/windows/manage/appv-reporting.md +++ b/windows/manage/appv-reporting.md @@ -56,75 +56,47 @@ The following list displays the end–to-end high-level workflow for reporting i >**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. ### App-V reporting server frequently asked questions -The following table displays answers to common questions about App-V reporting +The following list displays answers to common questions about App-V reporting. -
---- - - - - - - - - - - - - - - - - - - - - - - - - -
QuestionMore Information

What is the frequency that reporting information is sent to the reporting database?

The frequency depends on how the reporting task is configured on the computer running the App-V client. You must configure the frequency / interval for sending the reporting data. App-V Reporting is not enabled by default.

What information is stored in the reporting server database?

The following list displays what is stored in the reporting database:

-
    -

  • The operating system running on the computer running the App-V client: host name, version, service pack, type - client/server, processor architecture.

    • -

  • App-V Client information: version.

    • -

  • Published package list: GUID, version GUID, name.

    • -

  • Application usage information: name, version, streaming server, user (domain\alias), package version GUID, launch status and time, shutdown time.

    • -

What is the average volume of information that is sent to the reporting server?

It depends. The following list displays the three sets of the data sent to the reporting server:

-
    -

  1. Operating system, and App-V client information. ~150 Bytes, every time this data is sent.

    2. -

  2. 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.

    3. -

  3. 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 DeleteOnSuccess.

    -

    -

    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

    4. -

Can reporting be scheduled?

Yes. Besides manually sending reporting using Windows PowerShell cmdlets (Send-AppvClientReport), the task can be scheduled so it will happen automatically. There are two ways to schedule the reporting:

-
    -

  1. Using Windows PowerShell cmdlets - Set-AppvClientConfiguration. For example:

    -

    Set-AppvClientConfiguration -ReportingEnabled 1 -ReportingServerURL http://any.com/appv-reporting

    -

    -

    For a complete list of client configuration settings see [About Client Configuration Settings](appv-client-configuration-settings.md) and look for the following entries: ReportingEnabled, ReportingServerURL, ReportingDataCacheLimit, ReportingDataBlockSize, ReportingStartTime, ReportingRandomDelay, ReportingInterval.

    -

    2. -

  2. By using Group Policy. If distributed using the domain controller, the settings are the same as previously listed.

    -
    -Note   -

    Group Policy settings override local settings configured using Windows PowerShell.

    -
    -
    -  -
    3. -
+- **What is the frequency that reporting information is sent to the reporting database?** + + The frequency depends on how the reporting task is configured on the computer running the App-V client. You must configure the frequency / interval for sending the reporting data. App-V Reporting is not enabled by default. + +- **What information is stored in the reporting server database?** + + The following list displays what is stored in the reporting database: + - The operating system running on the computer running the App-V client: host name, version, service pack, type - client/server, processor architecture. + - App-V Client information: version. + - Published package list: GUID, version GUID, name. + - Application usage information: name, version, streaming server, user (domain\alias), package version GUID, launch status and time, shutdown time. + +- **What is the average volume of information that is sent to the reporting server?** + + It depends. The following list displays the three sets of the data sent to the reporting server: + - Operating system, and App-V client information. ~150 Bytes, every time this data is sent. + - 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. + - 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 **DeleteOnSuccess**. + + 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. + +- **Can reporting be scheduled?** + + Yes. Besides manually sending reporting using Windows PowerShell cmdlets (**Send-AppvClientReport**), the task can be scheduled so it will happen automatically. There are two ways to schedule the reporting: + - Using a Windows PowerShell cmdlet: **Set-AppvClientConfiguration**. For example: + `Set-AppvClientConfiguration -ReportingEnabled 1 -ReportingServerURL http://any.com/appv-reporting` + + For a complete list of client configuration settings see [About Client Configuration Settings](appv-client-configuration-settings.md) and look for the following entries: **ReportingEnabled**, **ReportingServerURL**, **ReportingDataCacheLimit**, **ReportingDataBlockSize**, **ReportingStartTime**, **ReportingRandomDelay**, **ReportingInterval**. + + - By using Group Policy. If distributed using the domain controller, the settings are the same as previously listed. + + **Note**   + Group Policy settings override local settings configured using Windows PowerShell. -  ## App-V Client Reporting diff --git a/windows/manage/appv-supported-configurations.md b/windows/manage/appv-supported-configurations.md index eb3e5fd340..e7a69f7b2a 100644 --- a/windows/manage/appv-supported-configurations.md +++ b/windows/manage/appv-supported-configurations.md @@ -14,7 +14,7 @@ ms.prod: w10 **Applies to** - Windows 10, version 1607; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; and Windows Server 2008 R2 -This topic specifies the requirements to install and run App-V in your Windows 10 environment. +This topic specifies the requirements to install and run App-V in your Windows 10 environment. For information about prerequisite software such as the .NET Framework, see [App-V Prerequisites](appv-prerequisites.md). ## App-V Server system requirements