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

Bulleted list cleanup

Browse Source
This commit is contained in:
Heidi Lohr
2018-04-16 16:46:14 -07:00
parent 73704b2b02
commit 442b022c41
5 changed files with 9 additions and 19 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@ -66,5 +66,4 @@ Add or vote on suggestions on the [Application Virtualization feedback site](htt
## Related topics
* [Release Notes for App-V for Windows 10, version 1607](appv-release-notes-for-appv-for-windows.md)
* [Release Notes for App-V for Windows 10, version 1703](appv-release-notes-for-appv-for-windows-1703.md)

7
windows/application-management/app-v/revision-heidi/appv-auto-batch-sequencing.md
View File

@ -92,15 +92,10 @@ Sequencing multipe apps at the same time requires that you create a **ConfigFIle
2. Add the following required XML info for each app:
- ```<AppName>```. The name of the app you're adding to the package.
- ```<InstallerFolder>```. The file path to the folder with the app installer.
- ```<Installer>```. The file name for the app executable. This will typically be an .exe or .msi file.
- ```<TimeoutInMinutes>```. The maximum amount of time, in minutes, that the cmdlet should wait for sequencing to complete. You can enter a different value for each app, based on the size and complexity of the app itself.
- ```<Cmdlet>```. Determines whether the sequencer uses the cmdlet or the App-V Sequencer interface. **True** tells the sequencer to usea cmdlet-based sequencing, while **False** tells the sequencer to use the App-V Sequencer interface. You can use both the cmdlet and the interface together in the same ConfigFile, for different apps.
- ```<Enabled>```. Indicates whether the app should be sequenced. **True** includes the app, while **False** ignores it. You can include as many apps as you want in the batch file, but optionally enable only a few of them.
**Example:**
@ -128,7 +123,7 @@ Sequencing multipe apps at the same time requires that you create a **ConfigFIle
</xml>
```
#### Start the App-V Sequencer interface and app installation process
#### How to start the App-V Sequencer interface and app installation process
Open PowerShell as an admin on the Host computer and run the following commands to start the batch sequencing:

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

@ -190,8 +190,6 @@ Add or vote on suggestions on the [Application Virtualization feedback site](htt
## Related topics
[App-V supported configurations](appv-supported-configurations.md)
[Planning for high availability with App-V](appv-planning-for-high-availability-with-appv.md)
[Planning to deploy App-V](appv-planning-to-deploy-appv.md)
* [App-V supported configurations](appv-supported-configurations.md)
* [Planning for high availability with App-V](appv-planning-for-high-availability-with-appv.md)
* [Planning to deploy App-V](appv-planning-to-deploy-appv.md)

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

@ -17,9 +17,9 @@ Use the information in this article to use Application Virtualization (App-V) to
This topic contains the following sections:
* [What to know before you start](#what-to-know-before-you-start)
* [Creating an Office 2016 package for App-V with the Office Deployment Tool](#creating-an-office-2016-package-for-app-v-with-the-office-deployment-tool) 
* [Publishing the Office package for App-V](#publishing-the-office-package-for-app-v) 
* [Customizing and managing Office App-V packages](#customizing-and-managing-office-app-v-packages) 
* [Creating an Office 2016 package for App-V with the Office Deployment Tool](#creating-an-office-2016-package-for-app-v-with-the-office-deployment-tool)
* [Publishing the Office package for App-V](#publishing-the-office-package-for-app-v)
* [Customizing and managing Office App-V packages](#customizing-and-managing-office-app-v-packages)
## What to know before you start
@ -364,8 +364,8 @@ To upgrade an Office 2016 package, use the Office Deployment Tool. To upgrade a
>[!NOTE]
>Office App-V packages have two Version IDs:
* An Office 2016 App-V Package Version ID that is unique across all packages created using the Office Deployment Tool.
* A second App-V Package Version ID, formatted as X.X.X.X, in the AppX manifest that will only change if there is a new version of Office itself. For example, if a new Office 2016 release with upgrades is available, and a package is created through the Office Deployment Tool to incorporate these upgrades, the X.X.X.X version ID will change to reflect the new version of Office. The App-V server will use the X.X.X.X version ID to differentiate this package and recognize that it contains new upgrades to the previously published package, and as a result, publish it as an upgrade to the existing Office 2016 package.
>* An Office 2016 App-V Package Version ID that is unique across all packages created using the Office Deployment Tool.
>* A second App-V Package Version ID, formatted as X.X.X.X, in the AppX manifest that will only change if there is a new version of Office itself. For example, if a new Office 2016 release with upgrades is available, and a package is created through the Office Deployment Tool to incorporate these upgrades, the X.X.X.X version ID will change to reflect the new version of Office. The App-V server will use the X.X.X.X version ID to differentiate this package and recognize that it contains new upgrades to the previously published package, and as a result, publish it as an upgrade to the existing Office 2016 package.
2. Globally publish the newly created Office 2016 App-V Packages onto the computers you want to apply the new updates to. Since the new package has the same lineage as the older Office 2016 App-V Package, publishing will be fast, as publishing the new package with the updates only applies the new changes to the old package.
3. Upgrades will be applied in the same manner of any globally published App-V packages. Because applications will probably be in use, upgrades might be delayed until the computer is rebooted.

2
windows/application-management/app-v/revision-heidi/appv-planning-for-high-availability-with-appv.md
View File

@ -89,9 +89,7 @@ Use the following steps to modify the connection string to include ```failover p
Click any of the following links for more information:
* [Prepare a mirror database for mirroring (SQL Server)](https://docs.microsoft.com/en-us/sql/database-engine/database-mirroring/prepare-a-mirror-database-for-mirroring-sql-server).
* [Establish a database mirroring session using Windows Authentication (SQL Server Management Studio)](https://docs.microsoft.com/en-us/sql/database-engine/database-mirroring/establish-database-mirroring-session-windows-authentication).
* [Deprecated database engine features in SQL Server 2012](<https://msdn.microsoft.com/library/ms143729(v=sql.110).aspx>).
## Support for Microsoft SQL Server Always On configuration