deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-05-13 13:57:22 +00:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

Editorial changes

Browse Source
This commit is contained in:
Heidi Lohr 2018-03-22 12:16:23 -07:00
parent 952382dd2c
commit 642df9aa11
5 changed files with 31 additions and 36 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
windows/application-management/app-v/revision-heidi/appv-about-appv.md
View File

@ -8,7 +8,6 @@ ms.sitesec: library
ms.prod: w10 ms.prod: w10
ms.date: 04/19/2017 ms.date: 04/19/2017
--- ---
# What's new in App-V for Windows 10, version 1703 and earlier # What's new in App-V for Windows 10, version 1703 and earlier
>Applies to Windows 10, version 1703 and earlier. >Applies to Windows 10, version 1703 and earlier.
@ -23,11 +22,9 @@ Previous versions of the App-V Sequencer required manual sequencing and updating
Using the automatic sequencer to package your apps gives you the following benefits: Using the automatic sequencer to package your apps gives you the following benefits:
* Automatic virtual machine (VM) sequencing environment provisioning. To learn more, see [Automatically provision your sequencing environment using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-provision-a-vm.md). * **Automatic virtual machine (VM) sequencing environment provisioning**. To learn more, see [Automatically provision your sequencing environment using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-provision-a-vm.md).
* **Package batch-sequencing**. This means that multiple apps can be sequenced at the same time, in a single group. To learn more, see [Automatically sequence multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-sequencing.md).
* Package batch-sequencing. This means that multiple apps can be sequenced at the same time, in a single group. To learn more, see [Automatically sequence multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-sequencing.md). * **Package batch-updating**. This means that multiple apps can be updated at the same time, in a single group. To learn more, see [Automatically update multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-updating.md).
* Package batch-updating. This means that multiple apps can be updated at the same time, in a single group. To learn more, see [Automatically update multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-updating.md).
### Updates to the App-V project template ### Updates to the App-V project template
@ -48,7 +45,6 @@ To learn more about earlier versions of App-V, see [MDOP Information Experience]
The changes in App-V for Windows 10, version 1607 impact existing implementations of App-V in the following ways: The changes in App-V for Windows 10, version 1607 impact existing implementations of App-V in the following ways:
* The App-V client is installed on user devices automatically with Windows 10, version 1607, and no longer has to be deployed separately. Performing an in-place upgrade to Windows 10, version 1607, on user devices automatically installs the App-V client. * The App-V client is installed on user devices automatically with Windows 10, version 1607, and no longer has to be deployed separately. Performing an in-place upgrade to Windows 10, version 1607, on user devices automatically installs the App-V client.
* In previous releases of App-V, the application sequencer was included in the Microsoft Desktop Optimization Pack. Although you’ll need to use the new application sequencer to create new virtualized applications, existing virtualized applications will continue to work. The App-V application sequencer is available from the [Windows 10 Assessment and Deployment Kit (ADK)](https://developer.microsoft.com/windows/hardware/windows-assessment-deployment-kit). * In previous releases of App-V, the application sequencer was included in the Microsoft Desktop Optimization Pack. Although you’ll need to use the new application sequencer to create new virtualized applications, existing virtualized applications will continue to work. The App-V application sequencer is available from the [Windows 10 Assessment and Deployment Kit (ADK)](https://developer.microsoft.com/windows/hardware/windows-assessment-deployment-kit).
>[!NOTE] >[!NOTE]

5
windows/application-management/app-v/revision-heidi/appv-capacity-planning.md
View File

@ -35,7 +35,6 @@ You can also manage your App-V environment using an electronic software distribu
* When there are disconnected remote users who can't connect to the App-V infrastructure. * When there are disconnected remote users who can't connect to the App-V infrastructure.
* When you're running a software management system, such as System Center 2012 Configuration Manager. * When you're running a software management system, such as System Center 2012 Configuration Manager.
* When network bandwidth limitations inhibit electronic software distribution. * When network bandwidth limitations inhibit electronic software distribution.
* **Full infrastructure model**—The full infrastructure model provides for software distribution, management, and reporting capabilities; it also includes the streaming of applications across the network. The App-V full infrastructure model consists of one or more App-V management servers that can be used to publish applications to all clients. Publishing places the virtual application icons and shortcuts on the target computer. It can also stream applications to local users. For more information about how to install the management server, see [Planning for App-V Server deployment](appv-planning-for-appv-server-deployment.md). The full infrastructure model is recommended for the following scenarios: * **Full infrastructure model**—The full infrastructure model provides for software distribution, management, and reporting capabilities; it also includes the streaming of applications across the network. The App-V full infrastructure model consists of one or more App-V management servers that can be used to publish applications to all clients. Publishing places the virtual application icons and shortcuts on the target computer. It can also stream applications to local users. For more information about how to install the management server, see [Planning for App-V Server deployment](appv-planning-for-appv-server-deployment.md). The full infrastructure model is recommended for the following scenarios:
* When you want to use the Management Server to publish the application to target computers. * When you want to use the Management Server to publish the application to target computers.
@ -52,8 +51,8 @@ The following section describes end-to-end App-V sizing and planning. For more s
>[!NOTE] >[!NOTE]
>Round trip response time on the client is the time taken by the computer running the App-V client to receive a successful notification from the publishing server. Round trip response time on the publishing server is the time taken by the computer running the publishing server to receive a successful package metadata update from the management server. >Round trip response time on the client is the time taken by the computer running the App-V client to receive a successful notification from the publishing server. Round trip response time on the publishing server is the time taken by the computer running the publishing server to receive a successful package metadata update from the management server.
* 20,000 clients can target a single publishing server to obtain the package refreshes in an acceptable round trip time. (<3 seconds.) * 20,000 clients can target a single publishing server to obtain the package refreshes in an acceptable round trip time (<3 seconds).
* A single management server can support up to 50 publishing servers for package metadata refreshes in an acceptable round trip time. (<5 seconds.) * A single management server can support up to 50 publishing servers for package metadata refreshes in an acceptable round trip time (<5 seconds).
## App-V Management Server capacity planning recommendations ## App-V Management Server capacity planning recommendations

10
windows/application-management/app-v/revision-heidi/appv-client-configuration-settings.md
View File

@ -38,10 +38,10 @@ The following table provides information about App-V client configuration settin
| Set-AppvPublishingServer<br><br>**-GlobalRefreshInterval**<br>Integer (0–744) | Specifies the publishing refresh interval using the GlobalRefreshIntervalUnit. To disable package refresh, specify 0. | 0 | | Set-AppvPublishingServer<br><br>**-GlobalRefreshInterval**<br>Integer (0–744) | Specifies the publishing refresh interval using the GlobalRefreshIntervalUnit. To disable package refresh, specify 0. | 0 |
| Set-AppvPublishingServer<br><br>**-GlobalRefreshIntervalUnit** <br>0 for hour, 1 for day | Specifies the interval unit (Hour 0–23, Day 0–31). | 1 | | Set-AppvPublishingServer<br><br>**-GlobalRefreshIntervalUnit** <br>0 for hour, 1 for day | Specifies the interval unit (Hour 0–23, Day 0–31). | 1 |
| Set-AppvPublishingServer<br><br>**-UserRefreshEnabled**<br>True (enabled); False (Disabled state) | Enables user publishing refresh (Boolean) | False | | Set-AppvPublishingServer<br><br>**-UserRefreshEnabled**<br>True (enabled); False (Disabled state) | Enables user publishing refresh (Boolean) | False |
| Set-AppvPublishingServer<br><br>**-UserRefreshOnLogon**<br>True (enabled); False (Disabled state) | Triggers a user publishing refresh on sign in. ( Boolean)Word count (with spaces): 60 | False | | Set-AppvPublishingServer<br><br>**-UserRefreshOnLogon**<br>True (enabled); False (Disabled state) | Triggers a user publishing refresh on sign in. (Boolean) Word count (with spaces): 60 | False |
| Set-AppvPublishingServer<br><br>**-UserRefreshInterval**<br>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<br><br>**-UserRefreshInterval**<br>Word count (with spaces): 85<br>Integer (0–744 Hours) | Specifies the publishing refresh interval using the UserRefreshIntervalUnit. To disable package refresh, select 0. | 0 |
| Set-AppvPublishingServer<br><br>**-UserRefreshIntervalUnit**<br>0 for hour, 1 for day | Specifies the interval unit (Hour 0–23, Day 0–31). | 1 | | Set-AppvPublishingServer<br><br>**-UserRefreshIntervalUnit**<br>0 for hour, 1 for day | Specifies the interval unit (Hour 0–23, Day 0–31). | 1 |
| Set-AppvClientConfiguration,<br>Set-AppvPublishingServer<br><br>**-MigrationMode**<br>True (enabled state); False (disabled state) | Migration mode allows the App-V client to modify shortcuts and FTA’s for packages created by a previous version of App-V. | | | Set-AppvClientConfiguration,<br>Set-AppvPublishingServer<br><br>**-MigrationMode**<br>True (enabled state); False (Disabled state) | Migration mode allows the App-V client to modify shortcuts and FTA’s for packages created by a previous version of App-V. | |
| Set-AppvClientConfiguration,<br>Set-AppvPublishingServer<br><br>**-EnablePackageScripts**<br>True (enabled); False (Disabled state) | Enables scripts defined in the package manifest of configuration files that should run. | | | Set-AppvClientConfiguration,<br>Set-AppvPublishingServer<br><br>**-EnablePackageScripts**<br>True (enabled); False (Disabled state) | Enables scripts defined in the package manifest of configuration files that should run. | |
| Set-AppvClientConfiguration<br><br>**-RoamingFileExclusions**<br>String | Specifies the file paths relative to %userprofile% that do not roam with a user's profile. For example, ```/ROAMINGFILEEXCLUSIONS='desktop;my pictures'``` | | | Set-AppvClientConfiguration<br><br>**-RoamingFileExclusions**<br>String | Specifies the file paths relative to %userprofile% that do not roam with a user's profile. For example, ```/ROAMINGFILEEXCLUSIONS='desktop;my pictures'``` | |
| Set-AppvClientConfiguration,<br>Set-AppvPublishingServer<br><br>**-RoamingRegistryExclusions**<br>String | Specifies the registry paths that do not roam with a user profile. For example, ```/ROAMINGREGISTRYEXCLUSIONS=software\\classes;software\\clients``` | Policy value not written (same as Not Configured) | | Set-AppvClientConfiguration,<br>Set-AppvPublishingServer<br><br>**-RoamingRegistryExclusions**<br>String | Specifies the registry paths that do not roam with a user profile. For example, ```/ROAMINGREGISTRYEXCLUSIONS=software\\classes;software\\clients``` | Policy value not written (same as Not Configured) |
@ -95,8 +95,8 @@ The following table provides information about App-V client configuration settin
| **ReportingEnabled**<br>True (Enabled); False (Disabled state) | Reporting\\EnableReporting | False | | **ReportingEnabled**<br>True (Enabled); False (Disabled state) | Reporting\\EnableReporting | False |
| **ReportingServerURL**<br>String | Reporting\\ReportingServer | Policy value not written (same as Not Configured) | | **ReportingServerURL**<br>String | Reporting\\ReportingServer | Policy value not written (same as Not Configured) |
| **ReportingDataCacheLimit**<br>Integer \[0–1024\] | Reporting\\DataCacheLimit | Policy value not written (same as Not Configured) | | **ReportingDataCacheLimit**<br>Integer \[0–1024\] | Reporting\\DataCacheLimit | Policy value not written (same as Not Configured) |
| **ReportingDataBlockSize**<br>Integer \[1024 - Unlimited\] | Reporting\\DataBlockSize | Policy value not written (same as Not Configured) | | **ReportingDataBlockSize**<br>Integer \[1024–Unlimited\] | Reporting\\DataBlockSize | Policy value not written (same as Not Configured) |
| **ReportingStartTime**<br>Integer (0 – 23) | Reporting\\ StartTime | Policy value not written (same as Not Configured) | | **ReportingStartTime**<br>Integer (0–23) | Reporting\\ StartTime | Policy value not written (same as Not Configured) |
| **ReportingInterval**<br>Integer | Reporting\\RetryInterval | Policy value not written (same as Not Configured) | | **ReportingInterval**<br>Integer | Reporting\\RetryInterval | Policy value not written (same as Not Configured) |
| **ReportingRandomDelay**<br>Integer \[0 - ReportingRandomDelay\] | Reporting\\RandomDelay | Policy value not written (same as Not Configured) | | **ReportingRandomDelay**<br>Integer \[0 - ReportingRandomDelay\] | Reporting\\RandomDelay | Policy value not written (same as Not Configured) |
| **EnableDynamicVirtualization<br>**1 (Enabled), 0 (Disabled) | HKEY\_LOCAL\_MACHINE\\Software\\Microsoft\\AppV\\Client\\Virtualization | | | **EnableDynamicVirtualization<br>**1 (Enabled), 0 (Disabled) | HKEY\_LOCAL\_MACHINE\\Software\\Microsoft\\AppV\\Client\\Virtualization | |

8
windows/application-management/app-v/revision-heidi/appv-deploy-appv-databases-with-sql-scripts.md
View File

@ -35,7 +35,7 @@ Use the following instructions to use SQL scripts, rather than the Windows Insta
4. Browse to the temporary location that you created, open the extracted **DatabaseScripts** folder, and review the appropriate **readme.txt** file for instructions: 4. Browse to the temporary location that you created, open the extracted **DatabaseScripts** folder, and review the appropriate **readme.txt** file for instructions:
| Database | Location of readme.txt file to use| | Database | Location of readme.txt file to use|
| - | - | |---|---|
| Management database | ManagementDatabase subfolder | | Management database | ManagementDatabase subfolder |
| Reporting database | ReportingDatabase subfolder | | Reporting database | ReportingDatabase subfolder |
@ -44,7 +44,7 @@ Use the following instructions to use SQL scripts, rather than the Windows Insta
>[!IMPORTANT] >[!IMPORTANT]
> The InsertVersionInfo.sql script is not required for versions of the App-V management database later than App-V 5.0 SP3. > The InsertVersionInfo.sql script is not required for versions of the App-V management database later than App-V 5.0 SP3.
> The Permissions.sql script should be updated according to **Step 2** in [KB article 3031340](https://support.microsoft.com/kb/3031340). **Step 1** is not required for versions of App-V later than App-V 5.0 SP3. > The Permissions.sql script should be updated according to Step 2 in [KB article 3031340](https://support.microsoft.com/kb/3031340). Step 1 is not required for versions of App-V later than App-V 5.0 SP3.
### Updated management database README file content ### Updated management database README file content
@ -181,5 +181,5 @@ Add or vote on suggestions on the [Application Virtualization feedback site](htt
## Related topics ## Related topics
- [Deploying the App-V Server](appv-deploying-the-appv-server.md) * [Deploying the App-V Server](appv-deploying-the-appv-server.md)
- [How to Deploy the App-V Server](appv-deploy-the-appv-server.md) * [How to deploy the App-V Server](appv-deploy-the-appv-server.md)

32
windows/application-management/app-v/revision-heidi/appv-deploy-the-appv-server-with-a-script.md
View File

@ -28,25 +28,25 @@ The following examples will show you how to install the Management server and da
To use the default instance of Microsoft SQL Server, use the following parameters: To use the default instance of Microsoft SQL Server, use the following parameters:
* /MANAGEMENT_SERVER * */MANAGEMENT_SERVER*
* /MANAGEMENT_ADMINACCOUNT * */MANAGEMENT_ADMINACCOUNT*
* /MANAGEMENT_WEBSITE_NAME * */MANAGEMENT_WEBSITE_NAME*
* /MANAGEMENT_WEBSITE_PORT * */MANAGEMENT_WEBSITE_PORT*
* /DB_PREDEPLOY_MANAGEMENT * */DB_PREDEPLOY_MANAGEMENT*
* /MANAGEMENT_DB_SQLINSTANCE_USE_DEFAULT * */MANAGEMENT_DB_SQLINSTANCE_USE_DEFAULT*
* /MANAGEMENT_DB_NAME * */MANAGEMENT_DB_NAME*
### Parameters for a custom instance of Microsoft SQL Server for a new installation on a local machine ### Parameters for a custom instance of Microsoft SQL Server for a new installation on a local machine
To use a custom instance of Microsoft SQL Server, use the following parameters: To use a custom instance of Microsoft SQL Server, use the following parameters:
* /MANAGEMENT_SERVER * */MANAGEMENT_SERVER*
* /MANAGEMENT_ADMINACCOUNT * */MANAGEMENT_ADMINACCOUNT*
* /MANAGEMENT_WEBSITE_NAME * */MANAGEMENT_WEBSITE_NAME*
* /MANAGEMENT_WEBSITE_PORT * */MANAGEMENT_WEBSITE_PORT*
* /DB_PREDEPLOY_MANAGEMENT * */DB_PREDEPLOY_MANAGEMENT*
* /MANAGEMENT_DB_CUSTOM_SQLINSTANCE * */MANAGEMENT_DB_CUSTOM_SQLINSTANCE*
* /MANAGEMENT_DB_NAME * */MANAGEMENT_DB_NAME*
### Example parameters for using a custom instance of Microsoft SQL Server for a new installation on a local machine ### Example parameters for using a custom instance of Microsoft SQL Server for a new installation on a local machine
@ -69,8 +69,8 @@ The following examples will show you how to install the Management server on a l
To use the default instance of Microsoft SQL Server, use the following parameters: To use the default instance of Microsoft SQL Server, use the following parameters:
* /MANAGEMENT_SERVER * */MANAGEMENT_SERVER*
* /MANAGEMENT_ADMINACCOUNT * */MANAGEMENT_ADMINACCOUNT*
* /MANAGEMENT_WEBSITE_NAME * /MANAGEMENT_WEBSITE_NAME
* /MANAGEMENT_WEBSITE_PORT * /MANAGEMENT_WEBSITE_PORT
* /EXISTING_MANAGEMENT_DB_SQL_SERVER_USE_LOCAL * /EXISTING_MANAGEMENT_DB_SQL_SERVER_USE_LOCAL