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

Editorial changes

Browse Source
This commit is contained in:
Heidi Lohr 2018-03-19 16:27:28 -07:00
parent b9095e68b6
commit 54faec60d0
3 changed files with 6 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -17,8 +17,6 @@ Microsoft Application Virtualization (App-V) for Windows 10 delivers Win32 appli
## What's new in App-V Windows 10, version 1703
The following are new features in App-V for Windows 10, version 1703.
### Auto-sequence and update your App-V packages singly or as a batch
Previous versions of the App-V Sequencer required manual sequencing and updating of app packages. This was time-consuming and required extensive interaction, causing many companies to deploy brand-new packages rather than update an existing one. Windows 10, version 1703 introduces the App-V Auto-Sequencer, which automatically sequences your app packages, improving your overall experience by streamlining prerequisite environment provisioning, automating app installation, and expediting package updating setup.
@ -41,9 +39,7 @@ Previous versions of App-V have required you to manually remove your unpublished
## What's new in App-V in Windows 10, version 1607
The following are new features in App-V for Windows 10, version 1607.
## App-V is now a feature in Windows 10
### App-V is now a feature in Windows 10
With Windows 10, version 1607 and later releases, App-V is now included with [Windows 10 for Enterprise and Windows 10 for Education](https://www.microsoft.com/en-us/WindowsForBusiness/windows-product-home) and is no longer part of the Microsoft Desktop Optimization Pack.

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

@ -115,9 +115,9 @@ App-V clients send reporting data to the reporting server. The reporting server
The random delay 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.
Random delay = 4 * number of clients/average requests per second.
*Random delay = 4 × number of clients/average requests per second*.
Example: Random delay for 500 clients with 120 requests per second is 4 * 500/120 = about 17 minutes.
Example: Random delay for 500 clients with 120 requests per second is *4 × 500/120 = about 17 minutes*.
## App-V publishing server capacity planning recommendations

6
windows/application-management/app-v/revision-heidi/appv-deploying-microsoft-office-2013-with-appv.md
View File

@ -251,8 +251,8 @@ The XML file included in the Office Deployment Tool specifies the product detail
|---|---|
|```\\server\Office2013```|This is the network share location that contains the Office Deployment Tool and the custom Configuration.xml file, **Customconfig.xml**.|
|```setup.exe```|This is the Office Deployment Tool.|
|```/download```|This downloads the Office 2013 applications that you specify in the <strong>Customconfig.xml</strong> file. These bits can be later converted in an Office 2013 App-V package with Volume Licensing.|
|```\\server\Office2013\Customconfig.xml```|This passes the XML configuration file required to complete the download process. In this example, the file used is **customconfig.xml**. After using the download command, Office applications should be found in the location specified in the configuration xml file, in this example ```\\Server\Office2013```.|
|```/download```|This downloads the Office 2013 applications that you specify in the **Customconfig.xml** file. These bits can be later converted in an Office 2013 App-V package with Volume Licensing.|
|```\\server\Office2013\Customconfig.xml```|This passes the XML configuration file required to complete the download process. In this example, the file used is **Customconfig.xml**. After using the download command, Office applications should be found in the location specified in the configuration xml file, in this example ```\\Server\Office2013```.|
<table>
<colgroup>
@ -285,7 +285,7 @@ The XML file included in the Office Deployment Tool specifies the product detail
|---|---|
|Add element:<br>Specifies the products and languages to include in the package.|N/A|
|OfficeClientEdition (attribute of Add element):<br>Specifies the edition of Office 2013 product to use: 32-bit or 64-bit. The operation fails if **OfficeClientEdition** is not set to a valid value.|```OfficeClientEdition="32"```<br>```OfficeClientEdition="64"```|
|Product element:<br>Specifies the application. Project 2013 and Visio 2013 must be specified here as an added product to be included in the applications.|```Product ID="O365ProPlusRetail"```<br>```Product ID="VisioProRetail"```<br>```Product ID="ProjectProRetail"```<br>```Product ID="ProPlusVolume"```<br>```Product ID= "ProjectProVolume"```|
|Product element:<br>Specifies the application. Project 2013 and Visio 2013 must be specified here as an added product to be included in the applications.|```Product ID="O365ProPlusRetail"```<br>```Product ID="VisioProRetail"```<br>```Product ID="ProjectProRetail"```<br>```Product ID="ProPlusVolume"```<br>```Product ID="ProjectProVolume"```|
|Language element:<br>Specifies the language supported in the applications.|```Language ID="en-us"```|
|Version (attribute of Add element):<br>Optional. Specifies a build to use for the package. Defaults to latest advertised build (as defined in v32.CAB at the Office source).|```15.1.2.3```|
|SourcePath (attribute of Add element):<br>Specifies the location in which the applications will be saved to.|```Sourcepath="\Server\Office2013”```|