mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-14 06:17:22 +00:00
Merge remote-tracking branch 'refs/remotes/origin/vs-9914655' into rs2
This commit is contained in:
LizRoss
commit
28e72f23d5
@ -39,8 +39,9 @@
|
||||
## [Reset a Windows 10 Mobile device](reset-a-windows-10-mobile-device.md)
|
||||
## [Application Virtualization (App-V) for Windows](appv-for-windows.md)
|
||||
### [Getting Started with App-V](appv-getting-started.md)
|
||||
#### [What's new in App-V](appv-about-appv.md)
|
||||
##### [Release Notes for App-V](appv-release-notes-for-appv-for-windows.md)
|
||||
#### [What's new in App-V for Windows 10, version 1703 and earlier](appv-about-appv.md)
|
||||
##### [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)
|
||||
#### [Evaluating App-V](appv-evaluating-appv.md)
|
||||
#### [High Level Architecture for App-V](appv-high-level-architecture.md)
|
||||
### [Planning for App-V](appv-planning-for-appv.md)
|
||||
@ -77,7 +78,10 @@
|
||||
#### [Deploying Microsoft Office 2010 by Using App-V](appv-deploying-microsoft-office-2010-wth-appv.md)
|
||||
### [Operations for App-V](appv-operations.md)
|
||||
#### [Creating and Managing App-V Virtualized Applications](appv-creating-and-managing-virtualized-applications.md)
|
||||
##### [How to Sequence a New Application with App-V](appv-sequence-a-new-application.md)
|
||||
##### [Automatically provision your sequencing environment using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-provision-a-vm.md)
|
||||
##### [Automatically sequence multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-sequencing.md)
|
||||
##### [Automatically update multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-updating.md)
|
||||
##### [Manually sequence a new app using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-sequence-a-new-application.md)
|
||||
##### [How to Modify an Existing Virtual Application Package](appv-modify-an-existing-virtual-application-package.md)
|
||||
##### [How to Create and Use a Project Template](appv-create-and-use-a-project-template.md)
|
||||
##### [How to Create a Package Accelerator](appv-create-a-package-accelerator.md)
|
||||
@ -108,6 +112,7 @@
|
||||
##### [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)
|
||||
#### [Using the App-V Client Management Console](appv-using-the-client-management-console.md)
|
||||
##### [Automatically clean-up unpublished packages on the App-V client](appv-auto-clean-unpublished-packages.md)
|
||||
#### [Migrating to App-V from a Previous Version](appv-migrating-to-appv-from-a-previous-version.md)
|
||||
##### [How to Convert a Package Created in a Previous Version of App-V](appv-convert-a-package-created-in-a-previous-version-of-appv.md)
|
||||
#### [Maintaining App-V](appv-maintaining-appv.md)
|
||||
@ -126,6 +131,7 @@
|
||||
##### [How to Install the App-V Databases and Convert the Associated Security Identifiers by Using Windows PowerShell](appv-install-the-appv-databases-and-convert-the-associated-security-identifiers-with-powershell.md)
|
||||
### [Troubleshooting App-V](appv-troubleshooting.md)
|
||||
### [Technical Reference for App-V](appv-technical-reference.md)
|
||||
#### [Available Mobile Data Management (MDM) settings for App-V](appv-available-mdm-settings.md)
|
||||
#### [Performance Guidance for Application Virtualization](appv-performance-guidance.md)
|
||||
#### [Application Publishing and Client Interaction](appv-application-publishing-and-client-interaction.md)
|
||||
#### [Viewing App-V Server Publishing Metadata](appv-viewing-appv-server-publishing-metadata.md)
|
||||
|
||||
@ -1,26 +1,43 @@
|
||||
---
|
||||
title: What's new in App-V for Windows 10 (Windows 10)
|
||||
description: Information about what's new in App-V for Windows 10.
|
||||
author: MaggiePucciEvans
|
||||
title: What's new in App-V for Windows 10, version 1703 and earlier (Windows 10)
|
||||
description: Information about what's new in App-V for Windows 10, version 1703 and earlier.
|
||||
author: eross-msft
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# What's new in App-V
|
||||
# What's new in App-V for Windows 10, version 1703 and earlier
|
||||
|
||||
**Applies to**
|
||||
- Windows 10, version 1607
|
||||
- Windows 10, version 1703 and earlier
|
||||
|
||||
Microsoft Application Virtualization (App-V) enables organizations to deliver Win32 applications to users as virtual applications. Virtual applications are installed on centrally managed servers and delivered to users as a service – in real time and on as as-needed basis. Users launch virtual applications from familiar access points and interact with them as if they were installed locally.
|
||||
Microsoft Application Virtualization (App-V) helps organizations to deliver Win32 applications to employees as virtual apps. Virtual apps are installed on centrally managed servers and delivered to employees as a service – in real time and on an as-needed basis. Employees start virtual apps from familiar access points and interact with them as if they were installed locally.
|
||||
|
||||
Application Virtualization (App-V) for Windows 10, version 1607, includes these new features and capabilities compared to App-V 5.1. See [App-V release notes](appv-release-notes-for-appv-for-windows.md) for more information about the App-V for Windows 10, version 1607 release.
|
||||
## 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 have required you to manually sequence and update your 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 the provisioning of the prerequisite environment, automating app installation, and expediting the package updating setup.
|
||||
|
||||
Using the automatic sequencer to package your apps provides:
|
||||
- Automatic virtual machine (VM) provisioning of the sequencing environment. For info about this, see [Automatically provision your sequencing environment using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-provision-a-vm.md).
|
||||
|
||||
- Batch-sequencing of packages. This means that multiple apps can be sequenced at the same time, in a single group. For info about this, see [Automatically sequence multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-sequencing.md).
|
||||
|
||||
- Batch-updating of packages. This means that multiple apps can be updated at the same time, in a single group. For info about this, 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
|
||||
Starting with Windows 10, version 1703, you can save an App-V project template (.appvt) file as part of a sequenced App-V package, so it's automatically loaded every time the package opens for editing or updates. Your template can include general option settings, file exclusion list settings, and target operating system settings. For more info about this, see [Create and apply an App-V project template to a sequenced App-V package](appv-create-and-use-a-project-template.md)
|
||||
|
||||
### Automatically cleanup unpublished App-V packages from the App-V client
|
||||
Previous versions of App-V have required you to manually remove your unpublished packages from your client devices, to free up additional storage space. Windows 10, version 1703 introduces the ability to use PowerShell or Group Policy settings to automatically cleanup your unpublished packages after a device restart. For more info about this, see [Automatically cleanup unpublished packages on the App-V client](appv-auto-clean-unpublished-packages.md)
|
||||
|
||||
## 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
|
||||
|
||||
With Windows 10, version 1607 and later releases, Application Virtualization (App-V) is 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.
|
||||
|
||||
For information about earlier versions of App-V, see [MDOP Information Experience](https://technet.microsoft.com/itpro/mdop/index).
|
||||
@ -31,24 +48,23 @@ The changes in App-V for Windows 10, version 1607 impact already existing implem
|
||||
|
||||
- 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.
|
||||
|
||||
>**Note**<br>If you're already using App-V 5.x, you don't need to re-deploy the App-V server components as they haven't changed since App-V 5.0 was released.
|
||||
>[!NOTE]
|
||||
>If you're already using App-V 5.x, you don't need to re-deploy the App-V server components as they haven't changed since App-V 5.0 was released.
|
||||
|
||||
For more information about how to configure an existing App-V installation after upgrading user devices to Windows 10, see [Upgrading to App-V for Windows 10 from an existing installation](appv-upgrading-to-app-v-for-windows-10-from-an-existing-installation.md) and [Migrating to App-V for Windows 10 from a previous version](appv-migrating-to-appv-from-a-previous-version.md).
|
||||
|
||||
>**Important**
|
||||
You can upgrade your existing App-V installation to Windows 10, version 1607 from App-V versions 5.0 SP2 and higher only. If you are using a previous version of App-V, you’ll need to upgrade from that version to App-V 5.0 SP2 before you upgrade to Windows 10, version 1607.
|
||||
|
||||
>[!IMPORTANT]
|
||||
>You can upgrade your existing App-V installation to Windows 10, version 1607 from App-V versions 5.0 SP2 and higher only. If you are using a previous version of App-V, you’ll need to upgrade from that version to App-V 5.0 SP2 before you upgrade to Windows 10, version 1607.
|
||||
|
||||
## Support for System Center
|
||||
|
||||
App-V supports System Center 2016 and System Center 2012 R2 Configuration Manager SP1. See [Planning for App-V Integration with Configuration Manager](https://technet.microsoft.com/library/jj822982.aspx) for information about integrating your App-V environment with Configuration Manager.
|
||||
|
||||
## 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)
|
||||
|
||||
## 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).<br>For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[Release Notes for App-V](appv-release-notes-for-appv-for-windows.md)
|
||||
|
||||
173
windows/manage/appv-auto-batch-sequencing.md
Normal file
173
windows/manage/appv-auto-batch-sequencing.md
Normal file
@ -0,0 +1,173 @@
|
||||
---
|
||||
title: Automatically sequence multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer) (Windows 10)
|
||||
description: How to automatically sequence multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer).
|
||||
author: eross-msft
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
# Automatically sequence multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)
|
||||
|
||||
**Applies to**
|
||||
- Windows 10, version 1703
|
||||
|
||||
Sequencing multiple apps at the same time requires you to install and start Microsoft Application Virtualization Sequencer (App-V Sequencer), and to install the necessary apps to collect any changes made to the operating system during the installation and building of the App-V package.
|
||||
|
||||
In Windows 10, version 1703, running the App-V Sequencer automatically captures and stores your customizations as an App-V project template (.appvt) file. If you want to make changes to this package later, your customizations will be automatically loaded from this template file. This is applicable to all of the sequencing scenarios:
|
||||
|
||||
- Using the New-BatchAppVSequencerPackages cmdlet
|
||||
|
||||
- Using the App-V Sequencer interface
|
||||
|
||||
- Using the new-AppVSequencerPackage cmdlet
|
||||
|
||||
>[!NOTE]
|
||||
>If you're trying to update multiple apps at the same time, see the [Automatically update multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-updating.md) topic.
|
||||
|
||||
### Sequence multiple apps by using a PowerShell cmdlet
|
||||
Sequencing multiple apps at the same time requires that you create a **ConfigFile** with info related to each round of sequencing. This file is then used by the cmdlet to start the VM at a "clean" checkpoint, to copy the installer from the Host device to the VM, and then to start the App-V Sequencer to monitor your specified app installations.
|
||||
|
||||
**To create your ConfigFile for use by the PowerShell cmdlet**
|
||||
|
||||
1. Determine the apps that need to be included in your App-V sequencing package, and then open a text editor, such as Notepad.
|
||||
|
||||
2. Add the following required XML info for each app:
|
||||
|
||||
- **<Name>.** 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.
|
||||
|
||||
- **<InstallerOptions>.** The command-line options required for the app installation.
|
||||
|
||||
- **<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 use 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:**
|
||||
|
||||
```XML
|
||||
<?xml version="1.0"?>
|
||||
<Applications>
|
||||
<Application>
|
||||
<Name>Skype for Windows</Name>
|
||||
<InstallerFolder>D:\Install\New\SkypeforWindows</InstallerFolder>
|
||||
<Installer>SkypeSetup.exe</Installer>
|
||||
<InstallerOptions>/S</InstallerOptions>
|
||||
<TimeoutInMinutes>20</TimeoutInMinutes>
|
||||
<Cmdlet>True</Cmdlet>
|
||||
<Enabled>True</Enabled>
|
||||
</Application>
|
||||
<Application>
|
||||
<Name>Power BI</Name>
|
||||
<InstallerFolder>D:\Install\New\MicrosoftPowerBI</InstallerFolder>
|
||||
<Installer>PBIDesktop.msi</Installer>
|
||||
<InstallerOptions>/S</InstallerOptions>
|
||||
<TimeoutInMinutes>20</TimeoutInMinutes>
|
||||
<Cmdlet>True</Cmdlet>
|
||||
<Enabled>True</Enabled>
|
||||
</Application>
|
||||
</Applications>
|
||||
</xml>
|
||||
```
|
||||
3. Save your completed file, using the name **ConfigFile**.
|
||||
|
||||
|
||||
**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:
|
||||
|
||||
```ps1
|
||||
New-BatchAppVSequencerPackages –ConfigFile <path_to_configfile> –VMName <name_of_vm> -OutputPath <path_to_your_output>
|
||||
```
|
||||
Where _VMName_ is the name of the virtual machine (VM) with the App-V Sequencer installed, where you'll run the batch sequencing, and _OutputPath_ is the full path to where the sequenced packages should be copied.
|
||||
|
||||
The cmdlet creates a "clean" checkpoint on the VM. Next, the cmdlet copies the first app installer listed in the ConfigFile from the Host computer to the VM, and finally a new session of the VM opens (through VMConnect) and sequencing of the app begins from the command-line. After completing sequencing and package creation for the first app on the VM, the package is copied from the VM to the Host computer, specified in the OutputPath parameter. The cmdlet then goes to the second app on your list, reverting the VM back to a "clean" checkpoint and running through all of the steps again, until the second app package is copied to your output folder. This process continues until all apps included in your list are done. After the last app, the VM is reverted back to a "clean" checkpoint and turned off.
|
||||
|
||||
### Sequence multiple apps by using the App-V Sequencer interface
|
||||
Sequencing multipe apps at the same time requires that you create a **ConfigFIle** to collect all of the info related to each round of sequencing. This file is then used by the App-V Sequencer interface after creating a "clean" checkpoint on your VM.
|
||||
|
||||
**To create your ConfigFile for use by the App-V Sequencer interface**
|
||||
|
||||
1. Determine the apps that need to be included in your App-V sequencing package, and then open a text editor, such as Notepad.
|
||||
|
||||
2. Add the following required XML info for each app:
|
||||
|
||||
- **<Name>.** 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:**
|
||||
|
||||
```XML
|
||||
<?xml version="1.0"?>
|
||||
<Applications>
|
||||
<Application>
|
||||
<Name>Skype for Windows</Name>
|
||||
<InstallerFolder>D:\Install\New\SkypeforWindows</InstallerFolder>
|
||||
<Installer>SkypeSetup.exe</Installer>
|
||||
<TimeoutInMinutes>20</TimeoutInMinutes>
|
||||
<Cmdlet>False</Cmdlet>
|
||||
<Enabled>True</Enabled>
|
||||
</Application>
|
||||
<Application>
|
||||
<Name>Power BI</Name>
|
||||
<InstallerFolder>D:\Install\New\MicrosoftPowerBI</InstallerFolder>
|
||||
<Installer>PBIDesktop.msi</Installer>
|
||||
<TimeoutInMinutes>20</TimeoutInMinutes>
|
||||
<Cmdlet>False</Cmdlet>
|
||||
<Enabled>True</Enabled>
|
||||
</Application>
|
||||
</Applications>
|
||||
</xml>
|
||||
```
|
||||
|
||||
|
||||
**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:
|
||||
|
||||
```ps1
|
||||
New-BatchAppVSequencerPackages –ConfigFile <path_to_configfile> –VMName <name_of_vm> -OutputPath <path_to_your_output>
|
||||
```
|
||||
Where _VMName_ is the name of the virtual machine (VM) with the App-V Sequencer installed, where you'll run the batch sequencing, and _OutputPath_ is the full path to where the sequenced packages should be copied.
|
||||
|
||||
The cmdlet creates a "clean" checkpoint on the VM. Next, the cmdlet copies the first app installer listed in the ConfigFile from the Host computer to the VM, and finally a new session of the VM opens (through VMConnect) and sequencing of the app begins from the command-line. After completing sequencing and package creation for the first app on the VM, the package is copied from the VM to the Host computer, specified in the OutputPath parameter. The cmdlet then goes to the second app on your list, reverting the VM back to a "clean" checkpoint and running through all of the steps again, until the second app package is copied to your output folder. This process continues until all apps included in your list are done. After the last app, the VM is reverted back to a "clean" checkpoint and turned off.
|
||||
|
||||
### Review the log files
|
||||
There are 3 types of log files that occur when you sequence multiple apps at the same time:
|
||||
|
||||
- **New-BatchAppVSequencerPackages-<*time_stamp*>.txt**. Located in the %temp%\AutoSequencer\Logs directory. This log contains info about the sequencing activities, such as "Copying installer to VM", "Scheduling sequencing task", and so on for each app. Additionally, if an app times out, this log contains the failure along with the checkpoint for troubleshooting the problem.
|
||||
|
||||
- **New-BatchAppVSequencerPackages-report-<*time_stamp*>.txt**. Located in the **OutputPath** folder you specified earlier. This log contains info about the connections made to the VM, showing if there were any failures. Additionally, it briefly includes success or failure info for all of the apps.
|
||||
|
||||
- **Log.txt file**. Located in the **Output Package** folder. This file contains all code included in the NewAppVSequencerPackage cmdlet, including the allowed parameters.
|
||||
|
||||
### Related topics
|
||||
- [Download the Windows ADK](https://developer.microsoft.com/windows/hardware/windows-assessment-deployment-kit)
|
||||
|
||||
- [How to install the App-V Sequencer](appv-install-the-sequencer.md)
|
||||
|
||||
- [Learn about Hyper-V on Windows Server 2016](https://technet.microsoft.com/en-us/windows-server-docs/compute/hyper-v/hyper-v-on-windows-server)
|
||||
|
||||
- [Automatically provision your sequencing environment using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-provision-a-vm.md)
|
||||
|
||||
- [Manually sequence a single app using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-sequence-a-new-application.md)
|
||||
|
||||
- [Automatically update multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-updating.md)
|
||||
|
||||
- [Automatically cleanup unpublished packages on the App-V client](appv-auto-clean-unpublished-packages.md)
|
||||
|
||||
**Have a suggestion for App-V?**<p>
|
||||
Add or vote on suggestions on the [Application Virtualization feedback site](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization).<br>For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
177
windows/manage/appv-auto-batch-updating.md
Normal file
177
windows/manage/appv-auto-batch-updating.md
Normal file
@ -0,0 +1,177 @@
|
||||
---
|
||||
title: Automatically update multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer) (Windows 10)
|
||||
description: How to automatically update multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer).
|
||||
author: eross-msft
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
# Automatically update multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)
|
||||
|
||||
**Applies to**
|
||||
- Windows 10, version 1703
|
||||
|
||||
Updating multiple apps at the same time follows the same process as [automatically sequencing multiple apps at the same time](appv-auto-batch-sequencing.md). However for updating, you'll pass your previously created app package files to the App-V Sequencer cmdlet for updating.
|
||||
|
||||
Starting with Windows 10, version 1703, running the New-BatchAppVSequencerPackages cmdlet or the App-V Sequencer interface captures and stores all of your customizations as an App-V project template. If you want to make changes to this package later, your customizations are automatically loaded from this template file.
|
||||
|
||||
>[!NOTE]
|
||||
>If you're trying to sequence multiple apps at the same time, see the [Automatically sequence multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-sequencing.md) topic.
|
||||
|
||||
### Update multiple apps by using a PowerShell cmdlet
|
||||
Updating multiple apps at the same time requires that you create a **ConfigFile** with info related to each round of updating. This file is then used by the cmdlet to start the VM at a "clean" checkpoint, to copy the installer from the Host device to the VM, and then to start the App-V Sequencer to monitor your specified app installations.
|
||||
|
||||
**To create your ConfigFile for use by the PowerShell cmdlet**
|
||||
|
||||
1. Determine the apps that need to be included in your app package, and then open a text editor, such as Notepad.
|
||||
|
||||
2. Add the following XML info for each app:
|
||||
|
||||
- **<Name>.** 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.
|
||||
|
||||
- **<InstallerOptions>.** The command-line options required for the app installation.
|
||||
|
||||
- **<Package>.** The file path to the location of your App-V packages. These packages were created when you sequenced your apps.
|
||||
|
||||
- **<TimeoutInMinutes>.** The maximum amount of time, in minutes, that the cmdlet should wait for updating 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 use cmdlet-based updating, 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:**
|
||||
```XML
|
||||
<?xml version="1.0"?>
|
||||
<Applications>
|
||||
<Application>
|
||||
<Name>Skype for Windows Update</Name>
|
||||
<InstallerFolder>D:\Install\Update\SkypeforWindows</InstallerFolder>
|
||||
<Installer>SkypeSetup.exe</Installer>
|
||||
<InstallerOptions>/S</InstallerOptions>
|
||||
<Package>C:\App-V_Package\Microsoft_Apps\skypeupdate.appv</Package>
|
||||
<TimeoutInMinutes>20</TimeoutInMinutes>
|
||||
<Cmdlet>True</Cmdlet>
|
||||
<Enabled>True</Enabled>
|
||||
</Application>
|
||||
<Application>
|
||||
<Name>Microsoft Power BI Update</Name>
|
||||
<InstallerFolder>D:\Install\Update\PowerBI</InstallerFolder>
|
||||
<Installer>PBIDesktop.msi</Installer>
|
||||
<InstallerOptions>/S</InstallerOptions>
|
||||
<Package>C:\App-V_Package\MS_Apps\powerbiupdate.appv</Package>
|
||||
<TimeoutInMinutes>20</TimeoutInMinutes>
|
||||
<Cmdlet>True</Cmdlet>
|
||||
<Enabled>True</Enabled>
|
||||
</Application>
|
||||
</Applications>
|
||||
</xml>
|
||||
```
|
||||
|
||||
3. Save your completed file, using the name **ConfigFile**.
|
||||
|
||||
|
||||
**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 updating:
|
||||
|
||||
```ps1
|
||||
New-BatchAppVSequencerPackages –ConfigFile <path_to_configfile> –VMName <name_of_vm> -OutputPath <path_to_your_output>
|
||||
```
|
||||
Where _VMName_ is the name of the virtual machine (VM) with the App-V Sequencer installed, where you'll run the batch updating, and _OutputPath_ is the full path to where the updated packages should be copied.
|
||||
|
||||
The cmdlet creates a "clean" checkpoint on the VM. Next, the cmdlet copies the first app installer listed in the ConfigFile from the Host computer to the VM, and finally a new session of the VM opens (through VMConnect) and updating of the app begins from the command-line. After completing updating and package creation for the first app on the VM, the package is copied from the VM to the Host computer, specified in the OutputPath parameter. The cmdlet then goes to the second app on your list, reverting the VM back to a "clean" checkpoint and running through all of the steps again, until the second app package is copied to your output folder. This process continues until all apps included in your list are done. After the last app, the VM is reverted back to a "clean" checkpoint and turned off.
|
||||
|
||||
### Update multiple apps by using the App-V Sequencer interface
|
||||
Updating multipe apps at the same time requires that you create a **ConfigFile** to collect all of the info related to each round of updating. This file is then used by the App-V Sequencer interface after creating a "clean" checkpoint on your VM.
|
||||
|
||||
**To create your ConfigFile for use by the App-V Sequencer interface**
|
||||
|
||||
1. Determine the apps that need to be updated and then open a text editor, such as Notepad.
|
||||
|
||||
2. Add the following XML info for each app:
|
||||
|
||||
- **<Name>.** 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.
|
||||
|
||||
- **<Package>.** The file path to the location of your App-V packages. These packages were created when you sequenced your apps.
|
||||
|
||||
- **<TimeoutInMinutes>.** The maximum amount of time, in minutes, the cmdlet should wait for updating 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 updating, 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:**
|
||||
|
||||
```XML
|
||||
<?xml version="1.0"?>
|
||||
<Applications>
|
||||
<Application>
|
||||
<Name>Skype for Windows Update</Name>
|
||||
<InstallerFolder>D:\Install\Update\SkypeforWindows</InstallerFolder>
|
||||
<Installer>SkypeSetup.exe</Installer>
|
||||
<InstallerOptions>/S</InstallerOptions>
|
||||
<Package>C:\App-V_Package\Microsoft_Apps\skypeupdate.appv</Package>
|
||||
<TimeoutInMinutes>20</TimeoutInMinutes>
|
||||
<Cmdlet>False</Cmdlet>
|
||||
<Enabled>True</Enabled>
|
||||
</Application>
|
||||
<Application>
|
||||
<Name>Microsoft Power BI Update</Name>
|
||||
<InstallerFolder>D:\Install\Update\PowerBI</InstallerFolder>
|
||||
<Installer>PBIDesktop.msi</Installer>
|
||||
<InstallerOptions>/S</InstallerOptions>
|
||||
<Package>C:\App-V_Package\MS_Apps\powerbiupdate.appv</Package>
|
||||
<TimeoutInMinutes>20</TimeoutInMinutes>
|
||||
<Cmdlet>False</Cmdlet>
|
||||
<Enabled>True</Enabled>
|
||||
</Application>
|
||||
</Applications>
|
||||
</xml>
|
||||
```
|
||||
|
||||
**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 updating:
|
||||
|
||||
```ps1
|
||||
New-BatchAppVSequencerPackages –ConfigFile <path_to_configfile> –VMName <name_of_vm> -OutputPath <path_to_your_output>
|
||||
```
|
||||
Where _VMName_ is the name of the virtual machine (VM) with the App-V Sequencer installed, where you'll run the batch updating, and _OutputPath_ is the full path to where the updated packages should be copied.
|
||||
|
||||
The cmdlet creates a "clean" checkpoint on the VM. Next, the cmdlet copies the first app installer listed in the ConfigFile from the Host computer to the VM, and finally a new session of the VM opens (through VMConnect) and updating of the app begins from the command-line. After completing updating and package creation for the first app on the VM, the package is copied from the VM to the Host computer, specified in the OutputPath parameter. The cmdlet then goes to the second app on your list, reverting the VM back to a "clean" checkpoint and running through all of the steps again, until the second app package is copied to your output folder. This process continues until all apps included in your list are done. After the last app, the VM is reverted back to a "clean" checkpoint and turned off.
|
||||
|
||||
### Review the log files
|
||||
There are 3 types of log files that occur when you sequence multiple apps at the same time:
|
||||
|
||||
- **New-BatchAppVSequencerPackages-<*time_stamp*>.txt**. Located in the %temp%\AutoSequencer\Logs directory. This log contains info about the updating activities, such as "Copying installer to VM", "Scheduling updating task", and so on for each app. Additionally, if an app times out, this log contains the failure along with the checkpoint for troubleshooting the problem.
|
||||
|
||||
- **New-BatchAppVSequencerPackages-report-<*time_stamp*>.txt**. Located in the **OutputPath** folder you specified earlier. This log contains info about the connections made to the VM, showing if there were any failures. Additionally, it briefly includes success or failure info for all of the apps.
|
||||
|
||||
- **Log.txt file**. Located in the **Output Package** folder. This file contains all code included in the NewAppVSequencerPackage cmdlet, including the allowed parameters.
|
||||
|
||||
### Related topics
|
||||
- [Download the Windows ADK](https://developer.microsoft.com/windows/hardware/windows-assessment-deployment-kit)
|
||||
|
||||
- [How to install the App-V Sequencer](appv-install-the-sequencer.md)
|
||||
|
||||
- [Learn about Hyper-V on Windows Server 2016](https://technet.microsoft.com/en-us/windows-server-docs/compute/hyper-v/hyper-v-on-windows-server)
|
||||
|
||||
- [Automatically provision your sequencing environment using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-provision-a-vm.md)
|
||||
|
||||
- [Manually sequence a single app using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-sequence-a-new-application.md)
|
||||
|
||||
- [Automatically sequence multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-sequencing.md)
|
||||
|
||||
- [Automatically cleanup unpublished packages on the App-V client](appv-auto-clean-unpublished-packages.md)
|
||||
|
||||
|
||||
**Have a suggestion for App-V?**<p>
|
||||
Add or vote on suggestions on the [Application Virtualization feedback site](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization).<br>For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
76
windows/manage/appv-auto-clean-unpublished-packages.md
Normal file
76
windows/manage/appv-auto-clean-unpublished-packages.md
Normal file
@ -0,0 +1,76 @@
|
||||
---
|
||||
title: Automatically cleanup unpublished packages on the App-V client (Windows 10)
|
||||
description: How to automatically clean-up any unpublished packages on your App-V client devices.
|
||||
author: eross-msft
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# Automatically cleanup unpublished packages on the App-V client
|
||||
|
||||
**Applies to**
|
||||
- Windows 10, version 1703
|
||||
|
||||
Previous versions of App-V have required you to manually remove your unpublished packages from your client devices, to free up additional storage space. Windows 10, version 1703 introduces the ability to use PowerShell or Group Policy settings to automatically cleanup your unpublished packages after a device restart.
|
||||
|
||||
## Cleanup by using PowerShell commands
|
||||
Using PowerShell, you can turn on the **AutoCleanupEnabled** setting to automatically cleanup your unpublished App-V packages from your App-V client devices.
|
||||
|
||||
**To turn on the AutoCleanupEnabled option**
|
||||
|
||||
1. Open PowerShell as an admin and run the following command to turn on the automatic package cleanup functionality:
|
||||
|
||||
```ps1
|
||||
Set-AppvClientConfiguration -AutoCleanupEnabled 1
|
||||
```
|
||||
|
||||
The command runs and you should see the following info on the PowerShell screen:
|
||||
|
||||
<table border="1">
|
||||
<tr>
|
||||
<thead>
|
||||
<th>Name</th>
|
||||
<th>Value</th>
|
||||
<th>SetbyGroupPolicy</th>
|
||||
</thead>
|
||||
</tr>
|
||||
<tbody>
|
||||
<tr>
|
||||
<td>AutoCleanupEnabled</td>
|
||||
<td>1</td>
|
||||
<td>False</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
2. Run the following command to make sure the configuration is ready to automatically cleanup your packages.
|
||||
|
||||
```ps1
|
||||
Get-AppvClientConfiguration
|
||||
```
|
||||
You should see the **AutoCleanupEnabled** option turned on (shows a value of "1") in the configuration list.
|
||||
|
||||
## Cleanup by using Group Policy settings
|
||||
Using Group Policy, you can turn on the **Enable automatic cleanup of unused appv packages** setting to automatically cleanup your unpublished App-V packages from your App-V client devices.
|
||||
|
||||
**To turn on the Enable automatic cleanup of unused appv packages setting**
|
||||
|
||||
1. Open your Group Policy editor and double-click the Administrative Templates\System\App-V\PackageManagement\Enable automatic cleanup of unused appv packages setting.
|
||||
|
||||
2. Click **Enabled**, and then click **OK**.
|
||||
|
||||
After your Group Policy updates, the setting is turned on and will cleanup any unpublished App-V packages on the App-V Client after restarting.
|
||||
|
||||
### Related topics
|
||||
- [Download the Windows ADK](https://developer.microsoft.com/windows/hardware/windows-assessment-deployment-kit)
|
||||
|
||||
- [Download the Microsoft Application Virtualization 5.0 Client UI Application](https://www.microsoft.com/en-us/download/details.aspx?id=41186)
|
||||
|
||||
- [Using the App-V Client Management Console](appv-using-the-client-management-console.md)
|
||||
|
||||
|
||||
**Have a suggestion for App-V?**<p>
|
||||
Add or vote on suggestions on the [Application Virtualization feedback site](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization).<br>For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
127
windows/manage/appv-auto-provision-a-vm.md
Normal file
127
windows/manage/appv-auto-provision-a-vm.md
Normal file
@ -0,0 +1,127 @@
|
||||
---
|
||||
title: Automatically provision your sequencing environment using Microsoft Application Virtualization Sequencer (App-V Sequencer) (Windows 10)
|
||||
description: How to automatically provision your sequencing environment using Microsoft Application Virtualization Sequencer (App-V Sequencer) PowerShell cmdlet or the user interface.
|
||||
author: eross-msft
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# Automatically provision your sequencing environment using Microsoft Application Virtualization Sequencer (App-V Sequencer)
|
||||
|
||||
**Applies to**
|
||||
- Windows 10, version 1703
|
||||
|
||||
Previous versions of the App-V Sequencer have required you to manually create your sequencing environment. Windows 10, version 1703 introduces two new PowerShell cmdlets, New-AppVSequencerVM and Connect-AppvSequencerVM, which automatically create your sequencing environment for you, including provisioning your virtual machine.
|
||||
|
||||
## Automatic VM provisioning of the sequencing environment
|
||||
You have 2 options for provisioning an VM for auto-sequencing:
|
||||
- Using a Virtual Hard Disk (VHD)
|
||||
|
||||
-OR-
|
||||
|
||||
- Updating an existing VM
|
||||
|
||||
>[!NOTE]
|
||||
>We have reduced the number of environmental checks performed by the App-V Sequencer, narrowing down the list of apps that need to be disabled or turned off for a clean sequencing experience. We've also suppressed antivirus and other similar app warnings.
|
||||
|
||||
### Provision a new VM by using a VHD file
|
||||
Provisioning your new VM includes creating a VHD file, setting up a user account, turning on remote PowerShell scripting, and installing the App-V Sequencer.
|
||||
|
||||
#### Create a VHD file
|
||||
For this process to work, you must have a base operating system available as a VHD image file, we recommend using the [Convert-WindowsImage.ps1](https://gallery.technet.microsoft.com/scriptcenter/Convert-WindowsImageps1-0fe23a8f) command-line tool.
|
||||
|
||||
**To create a VHD file by using the Convert-WindowsImage command-line tool**
|
||||
1. Open PowerShell as an admin and run the Convert-WindowsImage tool, using the following commands:
|
||||
|
||||
```ps1
|
||||
Convert-WindowsImage -SourcePath "<path_to_iso_image>" -VHDFormat "VHD" -VHDPartitionStyle "MBR"
|
||||
```
|
||||
Where *<path_to_iso_image>* is the full path to your ISO image.
|
||||
|
||||
>[!IMPORTANT]
|
||||
>You must specify the _VHDPartitionStyle_ as **MBR**. Using the default value, **GPT**, will cause a boot failure in your VHD image.
|
||||
|
||||
#### Provision your VM using your VHD file
|
||||
After you have a VHD file, you must provision your VM for auto-sequencing.
|
||||
|
||||
**To provision your VM using your VHD file**
|
||||
1. On the Host device, install Windows 10, version 1703 and the **Microsoft Application Virtualization (App-V) Auto Sequencer** component from the matching version of the Windows Assessment and Deployment Kit (ADK). For more info on how to install the App-V Sequencer, see [Install the App-V Sequencer](appv-install-the-sequencer.md).
|
||||
|
||||
2. Make sure that Hyper-V is turned on. For more info about turning on and using Hyper-V, see [Hyper-V on Windows Server 2016](https://technet.microsoft.com/en-us/windows-server-docs/compute/hyper-v/hyper-v-on-windows-server).
|
||||
|
||||
3. Open PowerShell as an admin and run the **New-AppVSequencerVM** cmdlet, using the following parameters:
|
||||
|
||||
```ps1
|
||||
New-AppVSequencerVM -VMName "<name_of_new_vm>" -ADKPath "<path_to_adk_install_folder>" -VHDPath "<path_to_vhd_file>" -VMMemory <vm_memory_size> -VMSwitch "<name_of_network_switch>"
|
||||
```
|
||||
|
||||
This command creates a new Hyper-V VM file using the provided VHD file and also creates a "clean" checkpoint, from where all sequencing and updating will start.
|
||||
|
||||
|
||||
### Provision an existing VM for auto-sequencing
|
||||
If your apps require custom prerequisites, such as Microsoft SQL Server, we recommend that you preinstall the prerequisites on your VM and then use that VM for auto-sequencing. Using these steps will establish a connection to your existing VM.
|
||||
|
||||
**To connect to your existing VM**
|
||||
- Open PowerShell as an admin and run the following commands on your existing VM:
|
||||
|
||||
- **Set the network category of your connection profile on the VM to _Private_:**
|
||||
|
||||
```ps1
|
||||
Get-netconnectionprofile | set-netconnectionprofile -NetworkCategory Private
|
||||
```
|
||||
|
||||
- **Enable firewall rules for _Remote Desktop_ and _Windows Remote Management_:**
|
||||
|
||||
```ps1
|
||||
Enable-NetFirewallRule -DisplayGroup “Remote Desktop”
|
||||
Enable-NetFirewallRule -DisplayGroup “Windows Remote Management”
|
||||
```
|
||||
|
||||
- **Set the VM to receive remote commands without a confirmation prompt:**
|
||||
|
||||
```ps1
|
||||
Enable-PSRemoting –Force
|
||||
```
|
||||
|
||||
**To provision an existing VM**
|
||||
1. On the Host device, install Windows 10, version 1703 and the **Microsoft Application Virtualization (App-V) Auto Sequencer** component from the matching version of the Windows Assessment and Deployment Kit (ADK). For more info on how to install the App-V Sequencer, see [Install the App-V Sequencer](appv-install-the-sequencer.md).
|
||||
|
||||
2. Open PowerShell as an admin and run the **Connect-AppvSequencerVM** cmdlet, using the following parameters:
|
||||
|
||||
```ps1
|
||||
Connect-AppvSequencerVM -VMName "<name_of_vm>" -ADKPath "<path_to_adk_install_folder>"
|
||||
```
|
||||
|
||||
Where *<name_of_vm>* is the name of the VM granted during its creation and shown in the Hyper-V Manager tool.
|
||||
|
||||
This command creates a new Hyper-V VM file using the provided VHD file and also creates a "clean" checkpoint, from where all sequencing and updating will start.
|
||||
|
||||
|
||||
### Review the provisioning log files
|
||||
The 2 types of provisioning log files, located at %temp%\AutoSequencer\Logs, are:
|
||||
|
||||
- **New-AppVSequencerVM-<*time_stamp*>.txt**. Includes info about the provisioning activities, such as "Waiting for VM session", "Copying installer for Sequencer", and so on.
|
||||
|
||||
- **Connect-AppvSequencerVM-report-<*time_stamp*>.txt**. Includes info about the connections made to the VM, showing whether there were any failures.
|
||||
|
||||
|
||||
### Next steps
|
||||
After provisioning your sequencing environment, you must sequence your apps, either as a group or individually. For more info about sequencing your apps, see [Manually sequence a single new app using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-sequence-a-new-application.md), [Automatically sequence multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-sequencing.md), and [Automatically update multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-updating.md).
|
||||
|
||||
After you sequence your packages, you can automatically cleanup any unpublished packages on the App-V client. For more info, see [Automatically cleanup unpublished packages on the App-V client](appv-auto-clean-unpublished-packages.md).
|
||||
|
||||
### Related topics
|
||||
- [Download the Convert-WindowsImage tool](https://gallery.technet.microsoft.com/scriptcenter/Convert-WindowsImageps1-0fe23a8f)
|
||||
|
||||
- [Download the Windows ADK](https://developer.microsoft.com/windows/hardware/windows-assessment-deployment-kit)
|
||||
|
||||
- [How to install the App-V Sequencer](appv-install-the-sequencer.md)
|
||||
|
||||
- [Learn about Hyper-V on Windows Server 2016](https://technet.microsoft.com/en-us/windows-server-docs/compute/hyper-v/hyper-v-on-windows-server)
|
||||
|
||||
|
||||
**Have a suggestion for App-V?**<p>
|
||||
Add or vote on suggestions on the [Application Virtualization feedback site](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization).<br>For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
211
windows/manage/appv-available-mdm-settings.md
Normal file
211
windows/manage/appv-available-mdm-settings.md
Normal file
@ -0,0 +1,211 @@
|
||||
---
|
||||
title: Available Mobile Data Management (MDM) settings for App-V (Windows 10)
|
||||
description: A list of the available MDM settings for App-V on Windows 10.
|
||||
author: eross-msft
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
# Available Mobile Data Management (MDM) settings for App-V
|
||||
With Windows 10, version 1703, you can configure, deploy, and manage your App-V apps by using these Mobile Data Management (MDM) settings. For the full list of available settings, see the [EnterpriseAppVManagement CSP](https://msdn.microsoft.com/en-us/windows/hardware/commercialize/customize/mdm/enterpriseappvmanagement-csp) page.
|
||||
|
||||
<table>
|
||||
<tr>
|
||||
<th>Policy name</th>
|
||||
<th>Supported versions</th>
|
||||
<th>Details</th>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Name</td>
|
||||
<td>Windows 10, version 1703</td>
|
||||
<td>
|
||||
<ul>
|
||||
<li><strong>URI full path.</strong> ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/<em><enterprise_id></em>/<em><package_family_name></em>/<em><package_full_name></em>/Name</li>
|
||||
<li><strong>Data type.</strong> String</li>
|
||||
<li><strong>Value.</strong> Read-only data, provided by your App-V packages.</li>
|
||||
</ul>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Version</td>
|
||||
<td>Windows 10, version 1703</td>
|
||||
<td>
|
||||
<ul>
|
||||
<li><strong>URI full path.</strong> ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/<em><enterprise_id></em>/<em><package_family_name></em>/<em><package_full_name></em>/Version</li>
|
||||
<li><strong>Data type.</strong> String</li>
|
||||
<li><strong>Value.</strong> Read-only data, provided by your App-V packages.</li>
|
||||
</ul>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Publisher</td>
|
||||
<td>Windows 10, version 1703</td>
|
||||
<td>
|
||||
<ul>
|
||||
<li><strong>URI full path.</strong> ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/<em><enterprise_id></em>/<em><package_family_name></em>/<em><package_full_name></em>/Publisher</li>
|
||||
<li><strong>Data type.</strong> String</li>
|
||||
<li><strong>Value.</strong> Read-only data, provided by your App-V packages.</li>
|
||||
</ul>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>InstallLocation</td>
|
||||
<td>Windows 10, version 1703</td>
|
||||
<td>
|
||||
<ul>
|
||||
<li><strong>URI full path.</strong> ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/<em><enterprise_id></em>/<em><package_family_name></em>/<em><package_full_name></em>/InstallLocation</li>
|
||||
<li><strong>Data type.</strong> String</li>
|
||||
<li><strong>Value.</strong> Read-only data, provided by your App-V packages.</li>
|
||||
</ul>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>InstallDate</td>
|
||||
<td>Windows 10, version 1703</td>
|
||||
<td>
|
||||
<ul>
|
||||
<li><strong>URI full path.</strong> ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/<em><enterprise_id></em>/<em><package_family_name></em>/<em><package_full_name></em>/InstallDate</li>
|
||||
<li><strong>Data type.</strong> String</li>
|
||||
<li><strong>Value.</strong> Read-only data, provided by your App-V packages.</li>
|
||||
</ul>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Users</td>
|
||||
<td>Windows 10, version 1703</td>
|
||||
<td>
|
||||
<ul>
|
||||
<li><strong>URI full path.</strong> ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/<em><enterprise_id></em>/<em><package_family_name></em>/<em><package_full_name></em>/Users</li>
|
||||
<li><strong>Data type.</strong> String</li>
|
||||
<li><strong>Value.</strong> Read-only data, provided by your App-V packages.</li>
|
||||
</ul>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>AppVPackageID</td>
|
||||
<td>Windows 10, version 1703</td>
|
||||
<td>
|
||||
<ul>
|
||||
<li><strong>URI full path.</strong> ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/<em><enterprise_id></em>/<em><package_family_name></em>/<em><package_full_name></em>/AppVPackageID</li>
|
||||
<li><strong>Data type.</strong> String</li>
|
||||
<li><strong>Value.</strong> Read-only data, provided by your App-V packages.</li>
|
||||
</ul>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>AppVVersionID</td>
|
||||
<td>Windows 10, version 1703</td>
|
||||
<td>
|
||||
<ul>
|
||||
<li><strong>URI full path.</strong> ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/<em><enterprise_id></em>/<em><package_family_name></em>/<em><package_full_name></em>/AppVVersionID</li>
|
||||
<li><strong>Data type.</strong> String</li>
|
||||
<li><strong>Value.</strong> Read-only data, provided by your App-V packages.</li>
|
||||
</ul>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>AppVPackageUri</td>
|
||||
<td>Windows 10, version 1703</td>
|
||||
<td>
|
||||
<ul>
|
||||
<li><strong>URI full path.</strong> ./Vendor/MSFT/EnterpriseAppVManagement/AppVPackageManagement/<em><enterprise_id></em>/<em><package_family_name></em>/<em><package_full_name></em>/AppVPackageUri</li>
|
||||
<li><strong>Data type.</strong> String</li>
|
||||
<li><strong>Value.</strong> Read-only data, provided by your App-V packages.</li>
|
||||
</ul>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>LastError</td>
|
||||
<td>Windows 10, version 1703</td>
|
||||
<td>
|
||||
<ul>
|
||||
<li><strong>URI full path.</strong> ./Vendor/MSFT/EnterpriseAppVManagement/AppVPublishing/LastSync/LastError</li>
|
||||
<li><strong>Data type.</strong> String</li>
|
||||
<li><strong>Value.</strong> Read-only data, provided by your App-V client.</li>
|
||||
</ul>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>LastErrorDescription</td>
|
||||
<td>Windows 10, version 1703</td>
|
||||
<td>
|
||||
<ul>
|
||||
<li><strong>URI full path.</strong> ./Vendor/MSFT/EnterpriseAppVManagement/AppVPublishing/LastSync/LastErrorDescription</li>
|
||||
<li><strong>Data type.</strong> String</li>
|
||||
<li><strong>Values.</strong>
|
||||
<ul>
|
||||
<li><strong>0.</strong> No errors returned during publish.</li>
|
||||
<li><strong>1.</strong> Unpublish groups failed during publish.</li>
|
||||
<li><strong>2.</strong> Publish no-group packages failed during publish.</li>
|
||||
<li><strong>3.</strong> Publish group packages failed during publish.</li>
|
||||
<li><strong>4.</strong> Unpublish packages failed during publish.</li>
|
||||
<li><strong>5.</strong> New policy write failed during publish.</li>
|
||||
<li><strong>6.</strong> Multiple non-fatal errors occurred during publish.</li>
|
||||
</ul>
|
||||
</li>
|
||||
</ul>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>SyncStatusDescription</td>
|
||||
<td>Windows 10, version 1703</td>
|
||||
<td>
|
||||
<ul>
|
||||
<li><strong>URI full path.</strong> ./Vendor/MSFT/EnterpriseAppVManagement/AppVPublishing/LastSync/SyncStatusDescription</li>
|
||||
<li><strong>Data type.</strong> String</li>
|
||||
<li><strong>Values.</strong>
|
||||
<ul>
|
||||
<li><strong>0.</strong> App-V publishing is idle.</li>
|
||||
<li><strong>1.</strong> App-V connection groups publish in progress.</li>
|
||||
<li><strong>2.</strong> App-V packages (non-connection group) publish in progress.</li>
|
||||
<li><strong>3.</strong> App-V packages (connection group) publish in progress.</li>
|
||||
<li><strong>4.</strong> App-V packages unpublish in progress.</li>
|
||||
</ul>
|
||||
</li>
|
||||
</ul>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>SyncProgress</td>
|
||||
<td>Windows 10, version 1703</td>
|
||||
<td>
|
||||
<ul>
|
||||
<li><strong>URI full path.</strong> ./Vendor/MSFT/EnterpriseAppVManagement/AppVPublishing/LastSync/SyncProgress</li>
|
||||
<li><strong>Data type.</strong> String</li>
|
||||
<li><strong>Values.</strong>
|
||||
<ul>
|
||||
<li><strong>0.</strong> App-V Sync is idle.</li>
|
||||
<li><strong>1.</strong> App-V Sync is initializing.</li>
|
||||
<li><strong>2.</strong> App-V Sync is in progress.</li>
|
||||
<li><strong>3.</strong> App-V Sync is complete.</li>
|
||||
<li><strong>4.</strong> App-V Sync requires device reboot.</li>
|
||||
</ul>
|
||||
</li>
|
||||
</ul>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>PublishXML</td>
|
||||
<td>Windows 10, version 1703</td>
|
||||
<td>
|
||||
<ul>
|
||||
<li><strong>URI full path.</strong> ./Vendor/MSFT/EnterpriseAppVManagement/AppVPublishing/Sync/PublishXML</li>
|
||||
<li><strong>Data type.</strong> String</li>
|
||||
<li><strong>Value.</strong> Custom value, entered by admin.</li>
|
||||
</ul>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Policy</td>
|
||||
<td>Windows 10, version 1703</td>
|
||||
<td>
|
||||
<ul>
|
||||
<li><strong>URI full path.</strong> ./Vendor/MSFT/EnterpriseAppVManagement/AppVDynamicPolicy/configurationid/Policy</li>
|
||||
<li><strong>Data type.</strong> String</li>
|
||||
<li><strong>Value.</strong> Custom value, entered by admin.</li>
|
||||
</ul>
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
@ -1,55 +1,64 @@
|
||||
---
|
||||
title: How to Create and Use a Project Template (Windows 10)
|
||||
description: How to Create and Use a Project Template
|
||||
author: MaggiePucciEvans
|
||||
title: Create and apply an App-V project template to a sequenced App-V package (Windows 10)
|
||||
description: Steps for how to create and apply an App-V project template (.appvt) to a sequenced App-V package.
|
||||
author: eross-msft
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# How to Create and Use a Project Template
|
||||
# Create and apply an App-V project template to a sequenced App-V package
|
||||
|
||||
**Applies to**
|
||||
- Windows 10, version 1607
|
||||
|
||||
You can use an App-V project template to save commonly applied settings associated with an existing virtual application package. These settings can then be applied when you create new virtual application packages in your environment. Using a project template can streamline the process of creating virtual application packages.
|
||||
You can use an App-V project template (.appvt) file to save commonly applied settings associated with an existing virtual application package. These settings can then be applied when you create new virtual application packages in your environment. Using a project template can streamline the process of creating virtual application packages. App-V project templates differ from App-V Package Accelerators because App-V Package Accelerators are application-specific, while App-V project templates can be applied to multiple applications. For more info about Package Accelerators, see the [How to create a Package Accelerator](appv-create-a-package-accelerator.md) topic.
|
||||
|
||||
> **Note** You can, and often should apply an App-V project template during a package upgrade. For example, if you sequenced an application with a custom exclusion list, it is recommended that an associated template is created and saved for later use while upgrading the sequenced application.
|
||||
>[!IMPORTANT]
|
||||
>In Windows 10, version 1703, running the new-appvsequencerpackage or the update-appvsequencepackage cmdlets automatically captures and stores all of your customizations as an App-V project template. If you want to make changes to this package later, your customizations are automatically loaded from this template file. If you have an auto-saved template and you attempt to load another template through the _TemplateFilePath_ parameter, the customization value from the parameter will override the auto-saved template.
|
||||
|
||||
App-V project templates differ from App-V Application Accelerators because App-V Application Accelerators are application-specific, and App-V project templates can be applied to multiple applications.
|
||||
|
||||
Use the following procedures to create and apply a new template.
|
||||
## Create a project template
|
||||
You must first create and save a project template, including a virtual app package with settings to be used by the template.
|
||||
|
||||
**To create a project template**
|
||||
|
||||
1. To start the App-V sequencer, on the computer that is running the sequencer, click **Start** / **All Programs** / **Microsoft Application Virtualization** / **Microsoft Application Virtualization Sequencer**.
|
||||
1. On the device running the App-V Sequencer, click **Start**, click **All Programs**, click **Microsoft Application Virtualization**, and then click **Microsoft Application Virtualization Sequencer**.
|
||||
|
||||
> **Note** If the virtual application package is currently open in the App-V Sequencer console, skip to step 3 of this procedure.
|
||||
>[!NOTE]
|
||||
>If the virtual app package is currently open in the App-V Sequencer console, skip to Step 3 of this procedure.
|
||||
|
||||
2. To open the existing virtual application package that contains the settings you want to save with the App-V project template, click **File** / **Open**, and then click **Edit Package**. On the **Select Package** page, click **Browse** and locate the virtual application package that you want to open. Click **Edit**.
|
||||
2. On the **File** menu, click **Open**, click **Edit Package**, browse for the virtual app package that includes the settings you want to save with the App-V project template, and then click **Edit** to change any of the settings or info included in the file.
|
||||
|
||||
3. In the App-V Sequencer console, to save the template file, click **File** / **Save As Template**. After you have reviewed the settings that will be saved with the new template, click **OK**. Specify a name that will be associated with the new App-V project template. Click Save.
|
||||
3. On the **File** menu, click **Save As Template**, review the settings associated with the new template, click **OK**, name your new template, and then click **Save**.
|
||||
|
||||
The new App-V project template is saved in the folder you specified.
|
||||
|
||||
**To apply a project template**
|
||||
## Apply a project template
|
||||
After creating the template, you can apply it to all of your new virtual app packages, automatically including all of the settings.
|
||||
|
||||
> **Important** Creating a virtual application package using a project template in conjunction with a Package Accelerator is not supported.
|
||||
>[!IMPORTANT]
|
||||
>Virtual app packages don't support using both a project template and a Package Accelerator together.
|
||||
|
||||
1. To start the App-V sequencer, on the computer that is running the sequencer, click **Start** / **All Programs** / **Microsoft Application Virtualization** / **Microsoft Application Virtualization Sequencer**.
|
||||
1. On the device running the App-V Sequencer, click **Start**, click **All Programs**, click **Microsoft Application Virtualization**, and then click **Microsoft Application Virtualization Sequencer**.
|
||||
|
||||
2. To create or upgrade a new virtual application package by using an App-V project template, click **File** / **New From Template**.
|
||||
2. On the **File** menu, click **New From Template**, browse to your newly created project template, and then click **Open**.
|
||||
|
||||
3. To select the project template that you want to use, browse to the directory where the project template is saved, select the project template, and then click **Open**.
|
||||
3. Create your new virtual app package. The settings saved with your template are automatically applied.
|
||||
|
||||
Create the new virtual application package. The settings saved with the specified template will be applied to the new virtual application package that you are creating.
|
||||
### Related topics
|
||||
- [Download the Windows ADK](https://developer.microsoft.com/windows/hardware/windows-assessment-deployment-kit)
|
||||
|
||||
## Have a suggestion for App-V?
|
||||
- [How to install the App-V Sequencer](appv-install-the-sequencer.md)
|
||||
|
||||
- [Learn about Hyper-V on Windows Server 2016](https://technet.microsoft.com/en-us/windows-server-docs/compute/hyper-v/hyper-v-on-windows-server)
|
||||
|
||||
- [Automatically sequence multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-sequencing.md)
|
||||
|
||||
- [Automatically update multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-updating.md)
|
||||
|
||||
- [Manually sequence a new app using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-sequence-a-new-application.md)
|
||||
|
||||
**Have a suggestion for App-V?**<p>
|
||||
Add or vote on suggestions on the [Application Virtualization feedback site](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization).<br>For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
|
||||
## Related topics
|
||||
|
||||
[Operations for App-V](appv-operations.md)
|
||||
|
||||
@ -68,7 +68,9 @@ The **Options** dialog box in the sequencer console contains the following tabs:
|
||||
|
||||
App-V supports applications that include Microsoft Windows Services. If an application includes a Windows service, the Service will be included in the sequenced virtual package as long as it is installed while being monitored by the sequencer. If a virtual application creates a Windows service when it initially runs, then later, after installation, the application must be run while the sequencer is monitoring so that the Windows Service will be added to the package. Only Services that run under the Local System account are supported. Services that are configured for AutoStart or Delayed AutoStart are started before the first virtual application in a package runs inside the package’s Virtual Environment. Windows Services that are configured to be started on demand by an application are started when the virtual application inside the package starts the Service via API call.
|
||||
|
||||
[How to Sequence a New Application with App-V](appv-sequence-a-new-application.md)
|
||||
- [Automatically provision your sequencing environment using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-provision-a-vm.md)
|
||||
- [How to Sequence a New Application with App-V](appv-sequence-a-new-application.md)
|
||||
- [Automatically sequence multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-sequencing.md)
|
||||
|
||||
## <a href="" id="---------app-v-5-1-shell-extension-support"></a> App-V shell extension support
|
||||
|
||||
@ -166,11 +168,7 @@ You can use the sequencer to modify an existing package. The computer on which y
|
||||
[How to Modify an Existing Virtual Application Package](appv-modify-an-existing-virtual-application-package.md)
|
||||
|
||||
## Creating a project template
|
||||
|
||||
|
||||
A .appvt file is a project template that can be used to save commonly applied, customized settings. You can then more easily use these settings for future sequencings.
|
||||
|
||||
App-V project templates differ from App-V Application Accelerators because App-V Application Accelerators are application-specific, and App-V project templates can be applied to multiple applications. Additionally, you cannot use a project template when you use a Package Accelerator to create a virtual application package. The following general settings are saved with an App-V project template:
|
||||
An App-V project template (.appvt) file is a project template that can be used to save commonly applied, customized settings. You can then more easily use these settings for future sequencings. App-V project templates differ from App-V Application Accelerators because App-V Application Accelerators are application-specific, and App-V project templates can be applied to multiple applications. Additionally, you cannot use a project template when you use a Package Accelerator to create a virtual application package. The following general settings are saved with an App-V project template:
|
||||
|
||||
A template can specify and store multiple settings as follows:
|
||||
|
||||
@ -180,10 +178,15 @@ A template can specify and store multiple settings as follows:
|
||||
|
||||
- **Exclusion Items.** Contains the Exclusion pattern list.
|
||||
|
||||
In Windows 10, version 1703, running the new-appvsequencerpackage or the update-appvsequencepackage cmdlets automatically captures and stores all of your customizations as an App-V project template. If you want to make changes to this package later, your customizations are automatically loaded from this template file.
|
||||
|
||||
>[!IMPORTANT]
|
||||
>If you have an auto-saved template and you attempt to load another template through the _TemplateFilePath_ parameter, the customization value from the parameter will override the auto-saved template.
|
||||
|
||||
[How to Create and Use a Project Template](appv-create-and-use-a-project-template.md)
|
||||
|
||||
## Creating a package accelerator
|
||||
|
||||
## Creating a package accelerator
|
||||
|
||||
**Note**
|
||||
Package accelerators created using a previous version of App-V must be recreated using App-V.
|
||||
|
||||
@ -42,10 +42,14 @@ The topics in this section provide information and step-by-step procedures to he
|
||||
[Operations for App-V](appv-operations.md)
|
||||
|
||||
- [Creating and Managing App-V Virtualized Applications](appv-creating-and-managing-virtualized-applications.md)
|
||||
- [Automatically provision your sequencing environment using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-provision-a-vm.md)
|
||||
- [Automatically sequence multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-sequencing.md)
|
||||
- [Automatically update multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-updating.md)
|
||||
- [Administering App-V Virtual Applications by Using the Management Console](appv-administering-virtual-applications-with-the-management-console.md)
|
||||
- [Managing Connection Groups](appv-managing-connection-groups.md)
|
||||
- [Deploying App-V Packages by Using Electronic Software Distribution (ESD)](appv-deploying-packages-with-electronic-software-distribution-solutions.md)
|
||||
- [Using the App-V Client Management Console](appv-using-the-client-management-console.md)
|
||||
- [Automatically cleanup unpublished packages on the App-V client](appv-auto-clean-unpublished-packages.md)
|
||||
- [Migrating to App-V from a Previous Version](appv-migrating-to-appv-from-a-previous-version.md)
|
||||
- [Maintaining App-V](appv-maintaining-appv.md)
|
||||
- [Administering App-V by Using Windows PowerShell](appv-administering-appv-with-powershell.md)
|
||||
|
||||
@ -16,15 +16,15 @@ ms.prod: w10
|
||||
|
||||
Use the following procedure to configure the App-V client configuration.
|
||||
|
||||
1. To configure the client settings using Windows PowerShell, use the **Set-AppvClientConfiguration** cmdlet. For more information about installing Windows PowerShell, and a list of cmdlets see, [How to Load the Windows PowerShell Cmdlets for App-V and Get Cmdlet Help](appv-load-the-powershell-cmdlets-and-get-cmdlet-help.md).
|
||||
1. To configure the client settings using Windows PowerShell, use the **Set-AppVClientConfiguration** cmdlet. For more information about installing Windows PowerShell, and a list of cmdlets see, [How to Load the Windows PowerShell Cmdlets for App-V and Get Cmdlet Help](appv-load-the-powershell-cmdlets-and-get-cmdlet-help.md).
|
||||
|
||||
2. To modify the client configuration, open a Windows PowerShell Command prompt and run **Set-AppvClientConfiguration** with any required parameters. For example:
|
||||
2. To modify the client configuration, open a Windows PowerShell Command prompt and run **Set-AppVClientConfiguration** with any required parameters. For example:
|
||||
|
||||
`$config = Get-AppvClientConfiguration`
|
||||
`$config = Get-AppVClientConfiguration`
|
||||
|
||||
`Set-AppcClientConfiguration $config`
|
||||
`Set-AppVClientConfiguration $config`
|
||||
|
||||
`Set-AppcClientConfiguration –Name1 MyConfig –Name2 “xyz”`
|
||||
`Set-AppVClientConfiguration –Name1 MyConfig –Name2 “xyz”`
|
||||
|
||||
|
||||
## Have a suggestion for App-V?
|
||||
|
||||
@ -28,20 +28,16 @@ Use the following information to plan how to deploy Office by using Microsoft Ap
|
||||
|
||||
You can use the App-V Sequencer to create plug-in packages for Language Packs, Language Interface Packs, Proofing Tools and ScreenTip Languages. You can then include the plug-in packages in a Connection Group, along with the Office package that you create by using the Office Deployment Toolkit. The Office applications and the plug-in Language Packs interact seamlessly in the same connection group, just like any other packages that are grouped together in a connection group.
|
||||
|
||||
>**Note**
|
||||
Microsoft Visio and Microsoft Project do not provide support for the Thai Language Pack.
|
||||
>[!NOTE]
|
||||
>Microsoft Visio and Microsoft Project do not provide support for the Thai Language Pack.
|
||||
|
||||
## <a href="" id="bkmk-office-vers-supp-appv"></a>Supported versions of Microsoft Office
|
||||
|
||||
<!-- As of February 28, 2017, the first row of the table should be updated, because at that point, support for the Office 2013 version of Office 365 will end. It might also be good to have a link to this KB article: https://support.microsoft.com/kb/3199744 -->
|
||||
|
||||
See [Microsoft Office Product IDs that App-V supports](https://support.microsoft.com/en-us/help/2842297/product-ids-that-are-supported-by-the-office-deployment-tool-for-click) for a list of supported Office products.
|
||||
>**Note** You must use the Office Deployment Tool to create App-V packages for Office 365 ProPlus. Creating packages for the volume-licensed versions of Office Professional Plus or Office Standard is not supported. You cannot use the App-V Sequencer.
|
||||
|
||||
>**Note**
|
||||
Support for the [Office 2013 version of Office 365 ended in Februrary 2017](https://support.microsoft.com/kb/3199744)
|
||||
|
||||
>[!NOTE]
|
||||
>You must use the Office Deployment Tool to create App-V packages for Office 365 ProPlus. Creating packages for the volume-licensed versions of Office Professional Plus or Office Standard is not supported. You cannot use the App-V Sequencer.
|
||||
|
||||
>Support for the [Office 2013 version of Office 365 ended in Februrary 2017](https://support.microsoft.com/kb/3199744)
|
||||
|
||||
## <a href="" id="bkmk-plan-coexisting"></a>Planning for using App-V with coexisting versions of Office
|
||||
|
||||
@ -87,8 +83,8 @@ The Office documentation provides extensive guidance on coexistence for Windows
|
||||
|
||||
The following tables summarize the supported coexistence scenarios. They are organized according to the version and deployment method you’re starting with and the version and deployment method you are migrating to. Be sure to fully test all coexistence solutions before deploying them to a production audience.
|
||||
|
||||
>**Note**
|
||||
Microsoft does not support the use of multiple versions of Office in Windows Server environments that have the Remote Desktop Session Host role service enabled. To run Office coexistence scenarios, you must disable this role service.
|
||||
>[!NOTE]
|
||||
>Microsoft does not support the use of multiple versions of Office in Windows Server environments that have the Remote Desktop Session Host role service enabled. To run Office coexistence scenarios, you must disable this role service.
|
||||
|
||||
|
||||
|
||||
|
||||
121
windows/manage/appv-release-notes-for-appv-for-windows-1703.md
Normal file
121
windows/manage/appv-release-notes-for-appv-for-windows-1703.md
Normal file
@ -0,0 +1,121 @@
|
||||
---
|
||||
title: Release Notes for App-V for Windows 10, version 1703 (Windows 10)
|
||||
description: A list of known issues and workarounds for App-V running on Windows 10, version 1703.
|
||||
author: eross-msft
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# Release Notes for App-V for Windows 10, version 1703
|
||||
|
||||
**Applies to**
|
||||
- Windows 10, version 1703
|
||||
|
||||
The following are known issues and workarounds for Application Virtualization (App-V) running on Windows 10, version 1703.
|
||||
|
||||
<table border="1">
|
||||
<thead>
|
||||
<th>Problem</th>
|
||||
<th>Workaround</th>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr>
|
||||
<td>Unable to manually create a system-owned folder needed for the <code>set-AppVClientConfiguration</code> PowerShell cmdlet when using the <i>PackageInstallationRoot</i>, <i>IntegrationRootUser</i>, or <i>IntegrationRootGlobal</i> parameters.</td>
|
||||
<td>Don't create this file manually, instead let the <code>Add-AppVClientPackage</code> cmdlet auto-generate it.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Failure to update an App-V package from App-V 5.x to the latest in-box version, by using the PowerShell sequencing commands.</td>
|
||||
<td>Make sure you have the complete App-V package or the MSI file from the original app.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Unable to modify the locale for auto-sequencing.</td>
|
||||
<td>Open the <code>C:\Program Files (x86)\Windows Kits\10\Microsoft Application Virtualization\AutoSequencer\Unattend_Sequencer_User_Setup_Template.xml</code> file and include the language code for your locale. For example, if you wanted Spanish (Spain), you'd use: <strong>es-ES</strong>.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Filetype and protocol handlers aren't registering properly with the Google Chrome browser, causing you to not see App-V packages as an option for default apps from the <strong>Settings > Apps> Default Apps</strong> area.</td>
|
||||
<td>The recommended workaround is to add the following code to the AppXManifest.xml file, underneath the <strong><appv:Extensions></strong> tag:
|
||||
<pre><code>
|
||||
<appv:Extension Category="AppV.URLProtocol">
|
||||
<appv:URLProtocol>
|
||||
<appv:Name>ftp</appv:Name>
|
||||
<appv:ApplicationURLProtocol>
|
||||
<appv:DefaultIcon>[{ProgramFilesX86}]\Google\Chrome\Application\chrome.exe,0</appv:DefaultIcon>
|
||||
<appv:ShellCommands>
|
||||
<appv:DefaultCommand>open</appv:DefaultCommand>
|
||||
<appv:ShellCommand>
|
||||
<appv:ApplicationId>[{ProgramFilesX86}]\Google\Chrome\Application\chrome.exe</appv:ApplicationId>
|
||||
<appv:Name>open</appv:Name>
|
||||
<appv:CommandLine>"[{ProgramFilesX86}]\Google\Chrome\Application\chrome.exe" -- "%1"</appv:CommandLine>
|
||||
<appv:DdeExec>
|
||||
<appv:DdeCommand />
|
||||
</appv:DdeExec>
|
||||
</appv:ShellCommand>
|
||||
</appv:ShellCommands>
|
||||
</appv:ApplicationURLProtocol>
|
||||
</appv:URLProtocol>
|
||||
</appv:Extension>
|
||||
<appv:Extension Category="AppV.URLProtocol">
|
||||
<appv:URLProtocol>
|
||||
<appv:Name>http</appv:Name>
|
||||
<appv:ApplicationURLProtocol>
|
||||
<appv:DefaultIcon>[{ProgramFilesX86}]\Google\Chrome\Application\chrome.exe,0</appv:DefaultIcon>
|
||||
<appv:ShellCommands>
|
||||
<appv:DefaultCommand>open</appv:DefaultCommand>
|
||||
<appv:ShellCommand>
|
||||
<appv:ApplicationId>[{ProgramFilesX86}]\Google\Chrome\Application\chrome.exe</appv:ApplicationId>
|
||||
<appv:Name>open</appv:Name>
|
||||
<appv:CommandLine>"[{ProgramFilesX86}]\Google\Chrome\Application\chrome.exe" -- "%1"</appv:CommandLine>
|
||||
<appv:DdeExec>
|
||||
<appv:DdeCommand />
|
||||
</appv:DdeExec>
|
||||
</appv:ShellCommand>
|
||||
</appv:ShellCommands>
|
||||
</appv:ApplicationURLProtocol>
|
||||
</appv:URLProtocol>
|
||||
</appv:Extension>
|
||||
<appv:Extension Category="AppV.URLProtocol">
|
||||
<appv:URLProtocol>
|
||||
<appv:Name>https</appv:Name>
|
||||
<appv:ApplicationURLProtocol>
|
||||
<appv:DefaultIcon>[{ProgramFilesX86}]\Google\Chrome\Application\chrome.exe,0</appv:DefaultIcon>
|
||||
<appv:ShellCommands>
|
||||
<appv:DefaultCommand>open</appv:DefaultCommand>
|
||||
<appv:ShellCommand>
|
||||
<appv:ApplicationId>[{ProgramFilesX86}]\Google\Chrome\Application\chrome.exe</appv:ApplicationId>
|
||||
<appv:Name>open</appv:Name>
|
||||
<appv:CommandLine>"[{ProgramFilesX86}]\Google\Chrome\Application\chrome.exe" -- "%1"</appv:CommandLine>
|
||||
<appv:DdeExec>
|
||||
<appv:DdeCommand />
|
||||
</appv:DdeExec>
|
||||
</appv:ShellCommand>
|
||||
</appv:ShellCommands>
|
||||
</appv:ApplicationURLProtocol>
|
||||
</appv:URLProtocol>
|
||||
</appv:Extension>
|
||||
</code></pre>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
## Related resources list
|
||||
For information that can help with troubleshooting App-V for Windows 10, see:
|
||||
- [Application Virtualization (App-V): List of Microsoft Support Knowledge Base Articles](http://social.technet.microsoft.com/wiki/contents/articles/14272.app-v-v5-x-list-of-microsoft-support-knowledge-base-articles.aspx)
|
||||
|
||||
- [The Official Microsoft App-V Team Blog](https://blogs.technet.microsoft.com/appv/)
|
||||
|
||||
- [Technical Reference for App-V](https://technet.microsoft.com/itpro/windows/manage/appv-technical-reference)
|
||||
|
||||
- [App-V TechNet Forum](https://social.technet.microsoft.com/forums/en-us/home?forum=mdopappv)
|
||||
|
||||
## 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).<br>For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
|
||||
## Related topics
|
||||
- [What's new in App-V for Windows 10](appv-about-appv.md)
|
||||
|
||||
- [Release Notes for App-V for Windows 10, version 1607](appv-release-notes-for-appv-for-windows-1703.md)
|
||||
@ -1,23 +1,21 @@
|
||||
---
|
||||
title: Release Notes for App-V (Windows 10)
|
||||
description: Release Notes for App-V
|
||||
author: MaggiePucciEvans
|
||||
title: Release Notes for App-V for Windows 10, version 1607 (Windows 10)
|
||||
description: A list of known issues and workarounds for App-V running on Windows 10, version 1607.
|
||||
author: eross-msft
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# Release Notes for App-V for Windows 10, version 1607
|
||||
|
||||
**Applies to**
|
||||
- Windows 10, version 1607
|
||||
|
||||
The following are known issues in Application Virtualization (App-V) for Windows 10, version 1607.
|
||||
The following are known issues and workarounds for Application Virtualization (App-V) running on Windows 10, version 1607.
|
||||
|
||||
## Windows Installer packages (.msi files) generated by the App-V sequencer (version 5.1 and earlier) fail to install on computers with the in-box App-V client
|
||||
|
||||
MSI packages that were generated using an App-V sequencer from previous versions of App-V (App-V versions 5.1 and earlier) include a check to validate that the App-V client is installed on client devices before allowing the MSI package to install. Now that the App-V client is installed automatically when you upgrade user devices to Windows 10, version 1607, the pre-requisite check fails and causes the MSI to fail.
|
||||
|
||||
**Workaround**:
|
||||
@ -45,13 +43,11 @@ MSI packages that were generated using an App-V sequencer from previous versions
|
||||
where the path is to the new directory (**C:\MyMsiTools\ for this example**).
|
||||
|
||||
## Error occurs during publishing refresh between App-V 5.0 SP3 Management Server and App-V Client on Windows 10
|
||||
|
||||
An error is generated during publishing refresh when synchronizing packages from the App-V 5.0 SP3 management server to an App-V client on Windows 10. This error occurs because the App-V 5.0 SP3 server does not understand the Windows 10 operating system that is specified in the publishing URL. The issue is fixed for App-V publishing server, but is not backported to versions of App-V 5.0 SP3 or earlier.
|
||||
|
||||
**Workaround**: Upgrade the App-V 5.0 Management server to the App-V Management server for Windows 10 Clients.
|
||||
|
||||
## Custom configurations do not get applied for packages that will be published globally if they are set using the App-V Server
|
||||
|
||||
If you assign a package to an AD group that contains machine accounts and apply a custom configuration to that group using the App-V Server, the custom configuration will not be applied to those machines. The App-V Client will publish packages assigned to a machine account globally. However, it stores custom configuration files per user in each user’s profile. Globally published packages will not have access to this custom configuration.
|
||||
|
||||
**Workaround**: Do one of the following:
|
||||
@ -95,7 +91,6 @@ On the Packages page of the Management Console, if you click **Add or Upgrade**
|
||||
3. Paste the path into the **Add Package** dialog box input field
|
||||
|
||||
## <a href="" id="upgrading-app-v-management-server-to-5-1-sometimes-fails-with-the-message--a-database-error-occurred-"></a>Upgrading App-V Management Server to 5.1 sometimes fails with the message “A database error occurred”
|
||||
|
||||
If you install the App-V 5.0 SP1 Management Server, and then try to upgrade to App-V Server when multiple connection groups are configured and enabled, the following error is displayed: “A database error occurred. Reason: 'Invalid column name 'PackageOptional'. Invalid column name 'VersionOptional'.”
|
||||
|
||||
**Workaround**: Run this command on your SQL database:
|
||||
@ -105,14 +100,11 @@ If you install the App-V 5.0 SP1 Management Server, and then try to upgrade to A
|
||||
where “AppVManagement” is the name of the database.
|
||||
|
||||
## Users cannot open a package in a user-published connection group if you add or remove an optional package
|
||||
|
||||
In environments that are running the RDS Client or that have multiple concurrent users per computer, logged-in users cannot open applications in packages that are in a user-published connection group if an optional package is added to or removed from the connection group.
|
||||
|
||||
**Workaround**: Have users log out and then log back in.
|
||||
|
||||
## Error message is erroneously displayed when the connection group is published only to the user
|
||||
|
||||
|
||||
When you run Repair-AppvClientConnectionGroup, the following error is displayed, even when the connection group is published only to the user: “Internal App-V Integration error: Package not integrated for the user. Please ensure that the package is added to the machine and published to the user.”
|
||||
|
||||
**Workaround**: Do one of the following:
|
||||
@ -132,40 +124,37 @@ When you run Repair-AppvClientConnectionGroup, the following error is displayed,
|
||||
3. If the package is currently published, run **Repair-AppvClientPackage** on that package.
|
||||
|
||||
## Icons not displayed properly in Sequencer
|
||||
|
||||
Icons in the Shortcuts and File Type Associations tab are not displayed correctly when modifying a package in the App-V Sequencer. This problem occurs when the size of the icons are not 16x16 or 32x32.
|
||||
|
||||
**Workaround**: Only use icons that are 16x16 or 32x32.
|
||||
|
||||
## InsertVersionInfo.sql script no longer required for the Management Database
|
||||
|
||||
|
||||
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).
|
||||
|
||||
**Important**
|
||||
**Step 1** is not required for versions of App-V later than App-V 5.0 SP3.
|
||||
|
||||
>[!IMPORTANT]
|
||||
>**Step 1** of the KB article listed above isn't required for versions of App-V later than App-V 5.0 SP3.
|
||||
|
||||
## Microsoft Visual Studio 2012 not supported
|
||||
App-V doesn't support Visual Studio 2012.
|
||||
|
||||
|
||||
App-V does not support Visual Studio 2012.
|
||||
|
||||
**Workaround**: None
|
||||
**Workaround**: Use a newer version of Microsoft Visual Studio.
|
||||
|
||||
## Application filename restrictions for App-V Sequencer
|
||||
|
||||
|
||||
The App-V Sequencer cannot sequence applications with filenames matching "CO_<x>" where x is any numeral. Error 0x8007139F will be generated.
|
||||
|
||||
**Workaround**: Use a different filename
|
||||
|
||||
## Have a suggestion for App-V?
|
||||
## Related resources list
|
||||
For information that can help with troubleshooting App-V for Windows 10, see:
|
||||
- [Application Virtualization (App-V): List of Microsoft Support Knowledge Base Articles](http://social.technet.microsoft.com/wiki/contents/articles/14272.app-v-v5-x-list-of-microsoft-support-knowledge-base-articles.aspx)
|
||||
- [The Official Microsoft App-V Team Blog](https://blogs.technet.microsoft.com/appv/)
|
||||
- [Technical Reference for App-V](https://technet.microsoft.com/itpro/windows/manage/appv-technical-reference)
|
||||
- [App-V TechNet Forum](https://social.technet.microsoft.com/forums/en-us/home?forum=mdopappv)
|
||||
|
||||
## 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).<br>For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
|
||||
## Related topics
|
||||
<a href="https://github.com/Microsoft/windows-itpro-docs/blob/master/CONTRIBUTING.md" class="button big">Help us to improve</a>
|
||||
|
||||
[What's new in App-V for Windows 10](appv-about-appv.md)
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: How to Sequence a New Application with App-V (Windows 10)
|
||||
description: How to Sequence a New Application with App-V
|
||||
author: MaggiePucciEvans
|
||||
title: Manually sequence a new app using the Microsoft Application Virtualization Sequencer (App-V Sequencer) (Windows 10)
|
||||
description: How to manually sequence a new app using the App-V Sequencer
|
||||
author: eross-msft
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
@ -9,10 +9,10 @@ ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# How to Sequence a New Application with App-V
|
||||
# Manually sequence a new app using the Microsoft Application Virtualization Sequencer (App-V Sequencer)
|
||||
|
||||
**Applies to**
|
||||
- Windows 10, version 1607
|
||||
- Windows 10, version 1607 and later
|
||||
|
||||
In Windows 10, version 1607, the App-V Sequencer is included with the Windows ADK. For more info on how to install the App-V Sequencer, see [Install the App-V Sequencer](appv-install-the-sequencer.md).
|
||||
|
||||
@ -36,8 +36,8 @@ In Windows 10, version 1607, the App-V Sequencer is included with the Windows AD
|
||||
|
||||
- If short paths have been disabled for the virtualized package’s target volume, you must also sequence the package to a volume that was created and still has short-paths disabled. It cannot be the system volume.
|
||||
|
||||
> [!NOTE]
|
||||
> The App-V Sequencer cannot sequence applications with filenames matching "CO_<_x_>" where x is any numeral. Error 0x8007139F will be generated.
|
||||
>[!NOTE]
|
||||
>The App-V Sequencer cannot sequence applications with filenames matching "CO_<_x_>" where x is any numeral. Error 0x8007139F will be generated.
|
||||
|
||||
**To sequence a new standard application**
|
||||
|
||||
@ -47,15 +47,15 @@ In Windows 10, version 1607, the App-V Sequencer is included with the Windows AD
|
||||
|
||||
3. On the **Prepare Computer** page, review the issues that could cause the package creation to fail or could cause the package to contain unnecessary data. You should resolve all potential issues before you continue. After making any corrections, click **Refresh** to display the updated information. After you have resolved all potential issues, click **Next**.
|
||||
|
||||
> [!IMPORTANT]
|
||||
> If you are required to disable virus scanning software, you should first scan the computer that runs the sequencer in order to ensure that no unwanted or malicious files could be added to the package.
|
||||
>[!IMPORTANT]
|
||||
>If you are required to disable virus scanning software, you should first scan the computer that runs the sequencer in order to ensure that no unwanted or malicious files could be added to the package.
|
||||
|
||||
4. On the **Type of Application** page, click the **Standard Application (default)** check box, and then click **Next**.
|
||||
|
||||
5. On the **Select Installer** page, click **Browse** and specify the installation file for the application.
|
||||
|
||||
> [!NOTE]
|
||||
> If the specified application installer modifies security access to a file or directory, existing or new, the associated changes will not be captured into the package.
|
||||
>[!NOTE]
|
||||
>If the specified application installer modifies security access to a file or directory, existing or new, the associated changes will not be captured into the package.
|
||||
|
||||
If the application does not have an associated installer file and you plan to run all installation steps manually, select the **Perform a Custom Installation** check box, and then click **Next**.
|
||||
|
||||
@ -65,8 +65,8 @@ In Windows 10, version 1607, the App-V Sequencer is included with the Windows AD
|
||||
|
||||
7. On the **Installation** page, when the sequencer and application installer are ready you can proceed to install the application so that the sequencer can monitor the installation process.
|
||||
|
||||
> [!IMPORTANT]
|
||||
> You should always install applications to a secure location and make sure no other users are logged on to the computer running the sequencer during monitoring.
|
||||
>[!IMPORTANT]
|
||||
>You should always install applications to a secure location and make sure no other users are logged on to the computer running the sequencer during monitoring.
|
||||
|
||||
Use the application's installation process to perform the installation. If additional installation files must be run as part of the installation, click **Run** to locate and run the additional installation files. When you are finished with the installation, select **I am finished installing**. Click **Next**.
|
||||
|
||||
@ -74,8 +74,8 @@ In Windows 10, version 1607, the App-V Sequencer is included with the Windows AD
|
||||
|
||||
9. On the **Configure Software** page, optionally run the programs contained in the package. This step allows you to complete any necessary license or configuration tasks before you deploy and run the package on target computers. To run all the programs at one time, select at least one program, and then click **Run All**. To run specific programs, select the program or programs, and then click **Run Selected**. Complete the required configuration tasks and then close the applications. You may need to wait several minutes for all programs to run.
|
||||
|
||||
> [!NOTE]
|
||||
> To run first-use tasks for any application that is not available in the list, open the application. The associated information will be captured during this step.
|
||||
>[!NOTE]
|
||||
>To run first-use tasks for any application that is not available in the list, open the application. The associated information will be captured during this step.
|
||||
|
||||
Click **Next**.
|
||||
|
||||
@ -91,23 +91,21 @@ In Windows 10, version 1607, the App-V Sequencer is included with the Windows AD
|
||||
|
||||
12. On the **Streaming** page, run each program so that it can be optimized and run more efficiently on target computers. It can take several minutes for all the applications to run. After all applications have run, close each of the applications, and then click **Next**.
|
||||
|
||||
> [!NOTE]
|
||||
> If you do not open any applications during this step, the default streaming method is on-demand streaming delivery. This means applications will be downloaded bit by bit until it can be opened, and then depending on how the background loading is configured, will load the rest of the application.
|
||||
|
||||
|
||||
>[!NOTE]
|
||||
>If you do not open any applications during this step, the default streaming method is on-demand streaming delivery. This means applications will be downloaded bit by bit until it can be opened, and then depending on how the background loading is configured, will load the rest of the application.
|
||||
|
||||
13. On the **Target OS** page, specify the operating systems that can run this package. To allow all supported operating systems in your environment to run this package, select **Allow this package to run on any operating system**. To configure this package to run only on specific operating systems, select **Allow this package to run only on the following operating systems** and select the operating systems that can run this package. Click **Next**.
|
||||
|
||||
> [!IMPORTANT]
|
||||
> Make sure that the operating systems you specify here are supported by the application you are sequencing.
|
||||
>[!IMPORTANT]
|
||||
>Make sure that the operating systems you specify here are supported by the application you are sequencing.
|
||||
|
||||
|
||||
14. The **Create Package** page is displayed. To modify the package without saving it, select **Continue to modify package without saving using the package editor**. This option opens the package in the sequencer console so that you can modify the package before it is saved. Click **Next**.
|
||||
|
||||
To save the package immediately, select **Save the package now** (default). Add optional **Comments** to be associated with the package. Comments are useful for identifying the program version and other information about the package.
|
||||
|
||||
> [!IMPORTANT]
|
||||
> The system does not support non-printable characters in **Comments** and **Descriptions**.
|
||||
>[!IMPORTANT]
|
||||
>The system does not support non-printable characters in **Comments** and **Descriptions**.
|
||||
|
||||
The default **Save Location** is also displayed on this page. To change the default location, click **Browse** and specify the new location. Click **Create**.
|
||||
|
||||
@ -115,14 +113,13 @@ In Windows 10, version 1607, the App-V Sequencer is included with the Windows AD
|
||||
|
||||
The package is now available in the sequencer.
|
||||
|
||||
> [!IMPORTANT]
|
||||
> After you have successfully created a virtual application package, you cannot run the virtual application package on the computer that is running the sequencer.
|
||||
|
||||
>[!IMPORTANT]
|
||||
>After you have successfully created a virtual application package, you cannot run the virtual application package on the computer that is running the sequencer.
|
||||
|
||||
|
||||
**To sequence an add-on or plug-in application**
|
||||
|
||||
> [!NOTE]
|
||||
>[!NOTE]
|
||||
>Before performing the following procedure, install the parent application locally on the computer that is running the sequencer. Or if you have the parent application virtualized, you can follow the steps in the add-on or plug-in workflow to unpack the parent application on the computer.
|
||||
|
||||
>For example, if you are sequencing a plug-in for Microsoft Excel, install Microsoft Excel locally on the computer that is running the sequencer. Also install the parent application in the same directory where the application is installed on target computers. If the plug-in or add-on is going to be used with an existing virtual application package, install the application on the same virtual application drive that was used when you created the parent virtual application package.
|
||||
@ -133,9 +130,8 @@ In Windows 10, version 1607, the App-V Sequencer is included with the Windows AD
|
||||
|
||||
3. On the **Prepare Computer** page, review the issues that might cause the package creation to fail or could cause the package to contain unnecessary data. You should resolve all potential issues before you continue. After making any corrections, click **Refresh** to display the updated information. After you have resolved all potential issues, click **Next**.
|
||||
|
||||
> [!IMPORTANT]
|
||||
> If you are required to disable virus scanning software, you should first scan the computer that runs the sequencer in order to ensure that no unwanted or malicious files could be added to the package.
|
||||
|
||||
>[!IMPORTANT]
|
||||
>If you are required to disable virus scanning software, you should first scan the computer that runs the sequencer in order to ensure that no unwanted or malicious files could be added to the package.
|
||||
|
||||
4. On the **Type of Application** page, select **Add-on or Plug-in**, and then click **Next**.
|
||||
|
||||
@ -143,17 +139,17 @@ In Windows 10, version 1607, the App-V Sequencer is included with the Windows AD
|
||||
|
||||
6. On the **Install Primary** page, ensure that the primary application is installed on the computer that runs the sequencer. Alternatively, you can expand an existing package that has been saved locally on the computer that runs the sequencer. To do this, click **Expand Package**, and then select the package. After you have expanded or installed the parent program, select **I have installed the primary parent program**.
|
||||
|
||||
Click **Next**.
|
||||
7. Click **Next**.
|
||||
|
||||
7. On the **Package Name** page, type a name that will be associated with the package. Use a name that helps identify the purpose and version of the application that will be added to the package. The package name will be displayed in the App-V Management Console.
|
||||
8. On the **Package Name** page, type a name that will be associated with the package. Use a name that helps identify the purpose and version of the application that will be added to the package. The package name will be displayed in the App-V Management Console.
|
||||
|
||||
Click **Next**.
|
||||
9. Click **Next**.
|
||||
|
||||
8. On the **Installation** page, when the sequencer and application installer are ready you can proceed to install the plug-in or add-in application so the sequencer can monitor the installation process. Use the application's installation process to perform the installation. If additional installation files must be run as part of the installation, click **Run** and locate and run the additional installation files. When you are finished with the installation, select **I am finished installing**, and then click **Next**.
|
||||
10. On the **Installation** page, when the sequencer and application installer are ready you can proceed to install the plug-in or add-in application so the sequencer can monitor the installation process. Use the application's installation process to perform the installation. If additional installation files must be run as part of the installation, click **Run** and locate and run the additional installation files. When you are finished with the installation, select **I am finished installing**, and then click **Next**.
|
||||
|
||||
9. On the **Installation Report** page, you can review information about the virtual application package that you just sequenced. For a more detailed explanation about the information displayed in **Additional Information**, double-click the event. After you have reviewed the information, click **Next**.
|
||||
11. On the **Installation Report** page, you can review information about the virtual application package that you just sequenced. For a more detailed explanation about the information displayed in **Additional Information**, double-click the event. After you have reviewed the information, click **Next**.
|
||||
|
||||
10. The **Customize** page is displayed. If you are finished installing and configuring the virtual application, select **Stop now** and skip to step 12 of this procedure. To perform either of the following customizations, select **Customize**.
|
||||
12. The **Customize** page is displayed. If you are finished installing and configuring the virtual application, select **Stop now** and skip to step 12 of this procedure. To perform either of the following customizations, select **Customize**.
|
||||
|
||||
- Optimize how the package will run across a slow or unreliable network.
|
||||
|
||||
@ -161,12 +157,10 @@ In Windows 10, version 1607, the App-V Sequencer is included with the Windows AD
|
||||
|
||||
Click **Next**.
|
||||
|
||||
11. On the **Streaming** page, run each program so that it can be optimized and run more efficiently on target computers. Streaming improves the experience when the virtual application package is run on target computers on high-latency networks. It can take several minutes for all the applications to run. After all applications have run, close each of the applications. You can also configure the package to be required to be fully downloaded before opening by selecting the **Force applications to be downloaded** check-box. Click **Next**.
|
||||
13. On the **Streaming** page, run each program so that it can be optimized and run more efficiently on target computers. Streaming improves the experience when the virtual application package is run on target computers on high-latency networks. It can take several minutes for all the applications to run. After all applications have run, close each of the applications. You can also configure the package to be required to be fully downloaded before opening by selecting the **Force applications to be downloaded** check-box. Click **Next**.
|
||||
|
||||
> [!NOTE]
|
||||
> If necessary, you can stop an application from loading during this step. In the **Application Launch** dialog box, click **Stop** and select one of the check boxes: **Stop all applications** or **Stop this application only**.
|
||||
|
||||
|
||||
>[!NOTE]
|
||||
>If necessary, you can stop an application from loading during this step. In the **Application Launch** dialog box, click **Stop** and select one of the check boxes: **Stop all applications** or **Stop this application only**.
|
||||
|
||||
12. On the **Target OS** page, specify the operating systems that can run this package. To allow all supported operating systems in your environment to run this package, select the **Allow this package to run on any operating system** check box. To configure this package to run only on specific operating systems, select the **Allow this package to run only on the following operating systems** check box, and then select the operating systems that can run this package. Click **Next**.
|
||||
|
||||
@ -174,8 +168,8 @@ In Windows 10, version 1607, the App-V Sequencer is included with the Windows AD
|
||||
|
||||
To save the package immediately, select **Save the package now**. Optionally, add a **Description** that will be associated with the package. Descriptions are useful for identifying the version and other information about the package.
|
||||
|
||||
> [!IMPORTANT]
|
||||
> The system does not support non-printable characters in Comments and Descriptions.
|
||||
>[!IMPORTANT]
|
||||
>The system does not support non-printable characters in Comments and Descriptions.
|
||||
|
||||
The default **Save Location** is also displayed on this page. To change the default location, click **Browse** and specify the new location. Click **Create**.
|
||||
|
||||
@ -187,9 +181,8 @@ In Windows 10, version 1607, the App-V Sequencer is included with the Windows AD
|
||||
|
||||
3. On the **Prepare Computer** page, review the issues that could cause the package creation to fail or could cause the package to contain unnecessary data. You should resolve all potential issues before you continue. After making any corrections, click **Refresh** to display the updated information. After you have resolved all potential issues, click **Next**.
|
||||
|
||||
> [!IMPORTANT]
|
||||
> If you are required to disable virus scanning software, you should first scan the computer that runs the App-V Sequencer in order to ensure that no unwanted or malicious files can be added to the package.
|
||||
|
||||
>[!IMPORTANT]
|
||||
>If you are required to disable virus scanning software, you should first scan the computer that runs the App-V Sequencer in order to ensure that no unwanted or malicious files can be added to the package.
|
||||
|
||||
4. On the **Type of Application** page, select **Middleware**, and then click **Next**.
|
||||
|
||||
@ -197,37 +190,35 @@ In Windows 10, version 1607, the App-V Sequencer is included with the Windows AD
|
||||
|
||||
6. On the **Package Name** page, type a name that will be associated with the package. Use a name that helps identify the purpose and version of the application that will be added to the package. The package name is displayed in the App-V Management Console.
|
||||
|
||||
Click **Next**.
|
||||
7. Click **Next**.
|
||||
|
||||
7. On the **Installation** page, when the sequencer and middleware application installer are ready you can proceed to install the application so that the sequencer can monitor the installation process. Use the application's installation process to perform the installation. If additional installation files must be run as part of the installation, click **Run**, to locate and run the additional installation files. When you are finished with the installation, select the **I am finished installing** check box, and then click **Next**.
|
||||
8. On the **Installation** page, when the sequencer and middleware application installer are ready you can proceed to install the application so that the sequencer can monitor the installation process. Use the application's installation process to perform the installation. If additional installation files must be run as part of the installation, click **Run**, to locate and run the additional installation files. When you are finished with the installation, select the **I am finished installing** check box, and then click **Next**.
|
||||
|
||||
8. On the **Installation** page, wait while the sequencer configures the virtual application package.
|
||||
9. On the **Installation** page, wait while the sequencer configures the virtual application package.
|
||||
|
||||
9. On the **Installation Report** page, you can review information about the virtual application package that you have just sequenced. In **Additional Information**, double-click an event to obtain more detailed information. To proceed, click **Next**.
|
||||
10. On the **Installation Report** page, you can review information about the virtual application package that you have just sequenced. In **Additional Information**, double-click an event to obtain more detailed information. To proceed, click **Next**.
|
||||
|
||||
10. On the **Target OS** page, specify the operating systems that can run this package. To enable all supported operating systems in your environment to run this package, select the **Allow this package to run on any operating system** check box. To configure this package to run only on specific operating systems, select the **Allow this package to run only on the following operating systems** check box and select the operating systems that can run this package. Click **Next**.
|
||||
11. On the **Target OS** page, specify the operating systems that can run this package. To enable all supported operating systems in your environment to run this package, select the **Allow this package to run on any operating system** check box. To configure this package to run only on specific operating systems, select the **Allow this package to run only on the following operating systems** check box and select the operating systems that can run this package. Click **Next**.
|
||||
|
||||
11. On the **Create Package** page is displayed. To modify the package without saving it, select **Continue to modify package without saving using the package editor**. This option opens the package in the sequencer console so that you can modify the package before it is saved. Click **Next**.
|
||||
12. On the **Create Package** page is displayed. To modify the package without saving it, select **Continue to modify package without saving using the package editor**. This option opens the package in the sequencer console so that you can modify the package before it is saved. Click **Next**.
|
||||
|
||||
To save the package immediately, select **Save the package now**. Optionally, add a **Description** to be associated with the package. Descriptions are useful for identifying the program version and other information about the package.
|
||||
|
||||
> [!IMPORTANT]
|
||||
> The system does not support non-printable characters in Comments and Descriptions.
|
||||
>[!IMPORTANT]
|
||||
>The system does not support non-printable characters in Comments and Descriptions.
|
||||
|
||||
The default **Save Location** is also displayed on this page. To change the default location, click **Browse** and specify the new location. Click **Create**.
|
||||
|
||||
12. The **Completion** page is displayed. Review the information in the **Virtual Application Package Report** pane as needed, then click **Close**. This information is also available in the **Report.xml** file that is located in the directory specified in step 11 of this procedure.
|
||||
13. The **Completion** page is displayed. Review the information in the **Virtual Application Package Report** pane as needed, then click **Close**. This information is also available in the **Report.xml** file that is located in the directory specified in step 11 of this procedure.
|
||||
|
||||
The package is now available in the sequencer. To edit the package properties, click **Edit \[Package Name\]**.
|
||||
|
||||
> [!IMPORTANT]
|
||||
> After you have successfully created a virtual application package, you cannot run the virtual application package on the computer that is running the sequencer.
|
||||
>[!IMPORTANT]
|
||||
>After you have successfully created a virtual application package, you cannot run the virtual application package on the computer that is running the sequencer.
|
||||
|
||||
## 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).<br>For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
|
||||
## Related topics
|
||||
|
||||
- [Install the App-V Sequencer](appv-install-the-sequencer.md)
|
||||
- [Operations for App-V](appv-operations.md)
|
||||
|
||||
@ -59,10 +59,15 @@ The following list displays additional optional parameters that can be used with
|
||||
|
||||
- FullLoad - specifies that the package must be fully downloaded to the computer running the App-V before it can be opened.
|
||||
|
||||
## Have a suggestion for App-V?
|
||||
In Windows 10, version 1703, running the new-appvsequencerpackage or the update-appvsequencepackage cmdlets automatically captures and stores all of your customizations as an App-V project template. If you want to make changes to this package later, your customizations are automatically loaded from this template file.
|
||||
|
||||
Add or vote on suggestions on the [Application Virtualization feedback site](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization).<br>For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
>[!IMPORTANT]
|
||||
>If you have an auto-saved template and you attempt to load another template through the _TemplateFilePath_ parameter, the customization value from the parameter will override the auto-saved template.
|
||||
|
||||
## Related topics
|
||||
|
||||
- [Administering App-V by using Windows PowerShell](appv-administering-appv-with-powershell.md)
|
||||
|
||||
## 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).<br>For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
@ -14,23 +14,31 @@ This topic lists new and updated topics in the [Manage Windows 10](index.md) doc
|
||||
|
||||
>If you're looking for **update history** for Windows 10, see [Windows 10 and Windows Server 2016 update history](https://support.microsoft.com/help/12387/windows-10-update-history).
|
||||
|
||||
|
||||
## RELEASE: Windows 10, version 1703
|
||||
|
||||
The topics in this library have been updated for Windows 10, version 1703 (also known as the Creators Update). Some topics have been moved to [Update Windows 10](../update/index.md) or to [Configure Windows 10](../configure/index.md).
|
||||
|
||||
|
||||
## March 2017
|
||||
| New or changed topic | Description |
|
||||
| --- | --- |
|
||||
|[Test scenario 6 - Review a reminder suggested by Cortana based on what you’ve promised in email](cortana-at-work-scenario-6.md) |New |
|
||||
|[What's new in App-V for Windows 10, version 1703 and earlier](appv-about-appv.md)|Updated to include new features in App-V for Windows 10, version 1703. |
|
||||
|[Release Notes for App-V for Windows 10, version 1703](appv-release-notes-for-appv-for-windows-1703.md)|New |
|
||||
|[Automatically provision your sequencing environment using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-provision-a-vm.md) |New |
|
||||
|[Automatically sequence multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-sequencing.md) |New |
|
||||
|[Automatically update multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-auto-batch-updating.md) |New |
|
||||
|[Automatically cleanup unpublished packages on the App-V client](appv-auto-clean-unpublished-packages.md) |New |
|
||||
|[Available Mobile Data Management (MDM) settings for App-V](appv-available-mdm-settings.md) |New |
|
||||
|
||||
## February 2017
|
||||
|
||||
| New or changed topic | Description |
|
||||
| --- | --- |
|
||||
| [Windows Libraries](windows-libraries.md) | New |
|
||||
| [Monitor Windows Updates with Update Compliance](update-compliance-monitor.md) | New |
|
||||
| [Get started with Update Compliance](update-compliance-get-started.md) | New |
|
||||
| [Use Update Compliance to monitor Windows Updates](update-compliance-using.md) | New |
|
||||
| [Assign devices to servicing branches for Windows 10 updates](waas-servicing-branches-windows-10-updates.md) | Added Group Policy setting that blocks user access to Windows Update. |
|
||||
| [Optimize update delivery for Windows 10 updates](waas-optimize-windows-10-updates.md) | Added Express updates. |
|
||||
|[Assign devices to servicing branches for Windows 10 updates](waas-servicing-branches-windows-10-updates.md) | Added Group Policy setting that blocks user access to Windows Update. |
|
||||
|[Optimize update delivery for Windows 10 updates](waas-optimize-windows-10-updates.md) |Added Express updates. |
|
||||
| [Distribute offline apps](distribute-offline-apps.md) | General updates to topic. Added links to supporting content for System Center Configuration Manager and Microsoft Intune. |
|
||||
|
||||
|
||||
|
||||
BIN
windows/manage/images/button.png
Normal file
BIN
windows/manage/images/button.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 9.0 KiB |
Loading…
x
Reference in New Issue
Block a user