mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-16 10:53:43 +00:00
Links: Windows (2021-03)
This commit is contained in:
David Coulter
@ -44,7 +44,7 @@ Previous versions of App-V have required you to manually remove your unpublished
|
||||
|
||||
With Windows 10, version 1607 and later releases, App-V is now included with [Windows 10 for Enterprise and Windows 10 for Education](https://www.microsoft.com/WindowsForBusiness/windows-product-home) and is no longer part of the Microsoft Desktop Optimization Pack.
|
||||
|
||||
To learn more about earlier versions of App-V, see [MDOP Information Experience](https://docs.microsoft.com/microsoft-desktop-optimization-pack/index).
|
||||
To learn more about earlier versions of App-V, see [MDOP Information Experience](/microsoft-desktop-optimization-pack/index).
|
||||
|
||||
The changes in App-V for Windows 10, version 1607 impact existing implementations of App-V in the following ways:
|
||||
|
||||
@ -61,7 +61,7 @@ For more information about how to configure an existing App-V installation after
|
||||
|
||||
## 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) to learn more about how to integrate your App-V environment with Configuration Manager.
|
||||
App-V supports System Center 2016 and System Center 2012 R2 Configuration Manager SP1. See [Planning for App-V Integration with Configuration Manager](/previous-versions/system-center/system-center-2012-R2/jj822982(v=technet.10)) to learn more about how to integrate your App-V environment with Configuration Manager.
|
||||
|
||||
|
||||
|
||||
@ -70,4 +70,4 @@ App-V supports System Center 2016 and System Center 2012 R2 Configuration Manage
|
||||
## Related topics
|
||||
|
||||
* [Release Notes for App-V for Windows 10, version 1607](../app-v/appv-release-notes-for-appv-for-windows.md)
|
||||
* [Release Notes for App-V for Windows 10, version 1703](../app-v/appv-release-notes-for-appv-for-windows-1703.md)
|
||||
* [Release Notes for App-V for Windows 10, version 1703](../app-v/appv-release-notes-for-appv-for-windows-1703.md)
|
||||
@ -85,7 +85,7 @@ To change the default location of the package store during setup, see [Enable th
|
||||
|
||||
### Shared Content Store
|
||||
|
||||
If the App-V Client is configured in Shared Content Store mode, no data is written to disk when a stream fault occurs, which means that the packages require minimal local disk space (publishing data). In VDI environments where local storage can be limited, it's important to use as little disk space as possible. You can minimize disk space usage by streaming applications from a high-performance network location (such as a SAN). For more information, see [Shared Content Store in Microsoft App-V 5.0 - Behind the Scenes](https://blogs.technet.microsoft.com/appv/2013/07/22/shared-content-store-in-microsoft-app-v-5-0-behind-the-scenes/).
|
||||
If the App-V Client is configured in Shared Content Store mode, no data is written to disk when a stream fault occurs, which means that the packages require minimal local disk space (publishing data). In VDI environments where local storage can be limited, it's important to use as little disk space as possible. You can minimize disk space usage by streaming applications from a high-performance network location (such as a SAN). For more information, see [Shared Content Store in Microsoft App-V 5.0 - Behind the Scenes](/archive/blogs/appv/shared-content-store-in-microsoft-app-v-5-0-behind-the-scenes).
|
||||
|
||||
>[!NOTE]
|
||||
>The machine and package store must be located on a local drive, even when you’re using Shared Content Store configurations for the App-V Client.
|
||||
@ -694,7 +694,7 @@ The App-V Client supports publishing applications with support for COM integrati
|
||||
|
||||
App-V supports registering COM objects from the package to the local operating system with two process types: Out-of-process and In-process. Registering COM objects is accomplished with one or a combination of multiple modes of operation for a specific App-V package that includes Off, Isolated, and Integrated. Integrated mode is configured for either the Out-of-process or In-process type. Configuration of COM modes and types is accomplished with dynamic configuration files (deploymentconfig.xml or userconfig.xml).
|
||||
|
||||
For details on App-V integration, see [Microsoft Application Virtualization 5.0 Integration](https://blogs.technet.microsoft.com/appv/2013/01/03/microsoft-application-virtualization-5-0-integration).
|
||||
For details on App-V integration, see [Microsoft Application Virtualization 5.0 Integration](/archive/blogs/appv/microsoft-application-virtualization-5-0-integration).
|
||||
|
||||
### Software clients and application capabilities
|
||||
|
||||
@ -758,7 +758,7 @@ For situations where there is more than one application that could register the
|
||||
|
||||
The AppPath extension point supports calling App-V applications directly from the operating system. Administrators can provide access to App-V applications from operating system commands or scripts without calling the specific path to the executable from either the Run or Start Screen, depending on the operating system. It therefore avoids modifying the system path environment variable on all systems, as it is accomplished during publishing.
|
||||
|
||||
The AppPath extension point is configured either in the manifest or in the dynamic configuration files and is stored in the registry on the local machine during publishing for the user. For additional information on AppPath review: [App Paths - A Virtual Application Extension in App-V 5.0](https://blogs.technet.microsoft.com/virtualworld/2012/12/12/app-paths-a-virtual-application-extension-in-app-v-5-0/).
|
||||
The AppPath extension point is configured either in the manifest or in the dynamic configuration files and is stored in the registry on the local machine during publishing for the user. For additional information on AppPath review: [App Paths - A Virtual Application Extension in App-V 5.0](/archive/blogs/virtualworld/app-paths-a-virtual-application-extension-in-app-v-5-0).
|
||||
|
||||
### Virtual application
|
||||
|
||||
@ -895,7 +895,4 @@ There are three specific categories of events recorded:
|
||||
|
||||
- **Admin** logs events for configurations applied to the App-V Client and also contains the primary warnings and errors.
|
||||
- **Operational** logs the general App-V execution and usage of individual components, creating an audit log of the App-V Client's completed App-V operations.
|
||||
- **Virtual Application** logs virtual application launches and use of virtualization subsystems.
|
||||
|
||||
|
||||
|
||||
- **Virtual Application** logs virtual application launches and use of virtualization subsystems.
|
||||
@ -97,12 +97,8 @@ There are 3 types of log files that occur when you sequence multiple apps at the
|
||||
|
||||
- [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/windows-server-docs/compute/hyper-v/hyper-v-on-windows-server)
|
||||
- [Learn about Hyper-V on Windows Server 2016](/windows-server/virtualization/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 clean up unpublished packages on the App-V client](appv-auto-clean-unpublished-packages.md)
|
||||
|
||||
|
||||
|
||||
|
||||
- [Automatically clean up unpublished packages on the App-V client](appv-auto-clean-unpublished-packages.md)
|
||||
@ -151,12 +151,8 @@ There are three types of log files that occur when you sequence multiple apps at
|
||||
|
||||
- [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/windows-server-docs/compute/hyper-v/hyper-v-on-windows-server)
|
||||
- [Learn about Hyper-V on Windows Server 2016](/windows-server/virtualization/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)
|
||||
|
||||
|
||||
|
||||
|
||||
- [Automatically cleanup unpublished packages on the App-V client](appv-auto-clean-unpublished-packages.md)
|
||||
@ -55,7 +55,7 @@ For this process to work, you must have a base operating system available as a V
|
||||
After you have a VHD file, you must provision your VM for auto-sequencing.
|
||||
|
||||
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/windows-server-docs/compute/hyper-v/hyper-v-on-windows-server).
|
||||
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](/windows-server/virtualization/hyper-v/Hyper-V-on-Windows-Server).
|
||||
3. Open PowerShell as an admin and run the **New-AppVSequencerVM** cmdlet, using the following parameters:
|
||||
|
||||
```PowerShell
|
||||
@ -127,7 +127,4 @@ After you sequence your packages, you can automatically clean up any unpublished
|
||||
- [Download the **Convert-WindowsImage** tool](https://www.powershellgallery.com/packages/Convert-WindowsImage/10.0)
|
||||
- [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/windows-server-docs/compute/hyper-v/hyper-v-on-windows-server)
|
||||
|
||||
|
||||
|
||||
- [Learn about Hyper-V on Windows Server 2016](/windows-server/virtualization/hyper-v/Hyper-V-on-Windows-Server)
|
||||
@ -14,7 +14,7 @@ ms.topic: article
|
||||
---
|
||||
# Available Mobile Device Management (MDM) settings for App-V
|
||||
|
||||
With Windows 10, version 1703, you can configure, deploy, and manage your App-V apps with the following Mobile Device Management (MDM) settings. For the full list of available settings, see the [EnterpriseAppVManagement CSP](https://msdn.microsoft.com/windows/hardware/commercialize/customize/mdm/enterpriseappvmanagement-csp) page.
|
||||
With Windows 10, version 1703, you can configure, deploy, and manage your App-V apps with the following Mobile Device Management (MDM) settings. For the full list of available settings, see the [EnterpriseAppVManagement CSP](/windows/client-management/mdm/enterpriseappvmanagement-csp) page.
|
||||
|
||||
|Policy name|Supported versions|URI full path|Data type|Values|
|
||||
|---|---|---|---|---|
|
||||
@ -32,4 +32,4 @@ With Windows 10, version 1703, you can configure, deploy, and manage your App-V
|
||||
|SyncStatusDescription|Windows 10, version 1703|./Vendor/MSFT/EnterpriseAppVManagement/ AppVPublishing/LastSync/SyncStatusDescription|String|- **0**: App-V publishing is idle.<br>- **1**: App-V connection groups publish in progress.<br>- **2**: App-V packages (non-connection group) publish in progress.<br>- **3**: App-V packages (connection group) publish in progress.<br>- **4**: App-V packages unpublish in progress.|
|
||||
|SyncProgress|Windows 10, version 1703|./Vendor/MSFT/EnterpriseAppVManagement/ AppVPublishing/LastSync/SyncProgress|String|- **0**: App-V Sync is idle.<br>- **1**: App-V Sync is initializing.<br>- **2**: App-V Sync is in progress.<br>- **3**: App-V Sync is complete.<br>- **4**: App-V Sync requires device reboot.|
|
||||
|PublishXML|Windows 10, version 1703|./Vendor/MSFT/EnterpriseAppVManagement/<br>AppVPublishing/Sync/PublishXML|String|Custom value, entered by admin.|
|
||||
|Policy|Windows 10, version 1703|./Vendor/MSFT/EnterpriseAppVManagement/<br>AppVDynamicPolicy/configurationid/Policy|String|Custom value, entered by admin.|
|
||||
|Policy|Windows 10, version 1703|./Vendor/MSFT/EnterpriseAppVManagement/<br>AppVDynamicPolicy/configurationid/Policy|String|Custom value, entered by admin.|
|
||||
@ -50,13 +50,13 @@ For more about adding or upgrading packages, see [How to add or upgrade packages
|
||||
Add-AppvClientConnectionGroup
|
||||
```
|
||||
|
||||
For more information about how to use the **Add-AppvClientConnectionGroup** cmdlet, see [**Add-AppvClientConnectionGroup**](https://docs.microsoft.com/powershell/module/appvclient/add-appvclientconnectiongroup?view=win10-ps).
|
||||
For more information about how to use the **Add-AppvClientConnectionGroup** cmdlet, see [**Add-AppvClientConnectionGroup**](/powershell/module/appvclient/add-appvclientconnectiongroup?view=win10-ps).
|
||||
|
||||
4. When you upgrade a package, use the following cmdlets to remove the old package, add the upgraded package, and publish the upgraded package:
|
||||
|
||||
- [**Remove-AppvClientPackage**](https://docs.microsoft.com/powershell/module/appvclient/remove-appvclientpackage?view=win10-ps)
|
||||
- [**Add-AppvClientPackage**](https://docs.microsoft.com/powershell/module/appvclient/add-appvclientpackage?view=win10-ps)
|
||||
- [**Publish-AppvClientPackage**](https://docs.microsoft.com/powershell/module/appvclient/publish-appvclientpackage?view=win10-ps)
|
||||
- [**Remove-AppvClientPackage**](/powershell/module/appvclient/remove-appvclientpackage?view=win10-ps)
|
||||
- [**Add-AppvClientPackage**](/powershell/module/appvclient/add-appvclientpackage?view=win10-ps)
|
||||
- [**Publish-AppvClientPackage**](/powershell/module/appvclient/publish-appvclientpackage?view=win10-ps)
|
||||
|
||||
For more information, see [How to manage App-V packages running on a stand-alone computer by using Windows PowerShell](appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md).
|
||||
|
||||
@ -66,4 +66,4 @@ For more information, see [How to manage App-V packages running on a stand-alone
|
||||
|
||||
## Related topics
|
||||
|
||||
- [Managing connection groups](appv-managing-connection-groups.md)
|
||||
- [Managing connection groups](appv-managing-connection-groups.md)
|
||||
@ -53,11 +53,7 @@ After creating the template, you can apply it to all of your new virtual app pac
|
||||
|
||||
- [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/windows-server-docs/compute/hyper-v/hyper-v-on-windows-server)
|
||||
- [Learn about Hyper-V on Windows Server 2016](/windows-server/virtualization/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)
|
||||
|
||||
|
||||
|
||||
|
||||
- [Manually sequence a new app using Microsoft Application Virtualization Sequencer (App-V Sequencer)](appv-sequence-a-new-application.md)
|
||||
@ -39,7 +39,7 @@ Before you deploy Office with App-V, review the following requirements.
|
||||
|---|---|
|
||||
|Packaging|All Office applications you wish to deploy to users must be in a single package.<br>In App-V and later, you must use the Office Deployment Tool to create packages. The Sequencer doesn't support package creation.<br>If you're deploying Microsoft Visio 2013 and Microsoft Project 2013 along with Office, you must include them in the same package with Office. For more information, see [Deploying Visio 2013 and Project 2013 with Office](#deploying-visio-2013-and-project-2013-with-office).|
|
||||
|Publishing|You can only publish one Office package per client computer.<br>You must publish the Office package globally, not to the user.|
|
||||
|Deploying Microsoft 365 Apps for enterprise, Visio Pro for Office 365, or Project Pro for Office 365 to a shared computer using Remote Desktop Services.|You must enable [shared computer activation](https://docs.microsoft.com/DeployOffice/overview-of-shared-computer-activation-for-office-365-proplus).<br>You don’t need to use shared computer activation if you’re deploying a volume licensed product, such as Office Professional Plus 2013, Visio Professional 2013, or Project Professional 2013.|
|
||||
|Deploying Microsoft 365 Apps for enterprise, Visio Pro for Office 365, or Project Pro for Office 365 to a shared computer using Remote Desktop Services.|You must enable [shared computer activation](/DeployOffice/overview-of-shared-computer-activation-for-office-365-proplus).<br>You don’t need to use shared computer activation if you’re deploying a volume licensed product, such as Office Professional Plus 2013, Visio Professional 2013, or Project Professional 2013.|
|
||||
|
||||
### Excluding Office applications from a package
|
||||
|
||||
@ -47,7 +47,7 @@ The following table describes the recommended methods for excluding specific Off
|
||||
|
||||
|Task|Details|
|
||||
|---|---|
|
||||
|Use the **ExcludeApp** setting when you create the package by using the Office Deployment Tool.|Enables you to exclude specific Office applications from the package when the Office Deployment Tool creates the package. For example, you can use this setting to create a package that contains only Microsoft Word.<br>For more information, see [ExcludeApp element](https://docs.microsoft.com/DeployOffice/configuration-options-for-the-office-2016-deployment-tool?ui=en-US&rs=en-US&ad=US#excludeapp-element).|
|
||||
|Use the **ExcludeApp** setting when you create the package by using the Office Deployment Tool.|Enables you to exclude specific Office applications from the package when the Office Deployment Tool creates the package. For example, you can use this setting to create a package that contains only Microsoft Word.<br>For more information, see [ExcludeApp element](/DeployOffice/configuration-options-for-the-office-2016-deployment-tool?ad=US&rs=en-US&ui=en-US#excludeapp-element).|
|
||||
|Modify the **DeploymentConfig.xml** file|Modify the **DeploymentConfig.xml** file after creating the package. This file contains the default package settings for all users on a computer running the App-V Client.<br>For more information, see [Disabling Office 2013 applications](#disabling-office-2013-applications).|
|
||||
|
||||
## Creating an Office 2013 package for App-V with the Office Deployment Tool
|
||||
@ -306,7 +306,7 @@ Use the steps in this section to enable Office plug-ins with your Office package
|
||||
You may want to disable specific applications in your Office App-V package. For instance, you can disable Access, but leave all other Office application main available. When you disable an application, the end user will no longer see the shortcut for that application. You do not have to re-sequence the application. When you change the Deployment Configuration File after the Office 2013 App-V package has been published, you will save the changes, add the Office 2013 App-V package, then republish it with the new Deployment Configuration File to apply the new settings to Office 2013 App-V Package applications.
|
||||
|
||||
>[!NOTE]
|
||||
>To exclude specific Office applications (for example, Access and InfoPath) when you create the App-V package with the Office Deployment Tool, use the **ExcludeApp** setting. For more information, see [Reference for Click-to-Run configuration.xml file](https://docs.microsoft.com/DeployOffice/configuration-options-for-the-office-2016-deployment-tool#excludeapp-element).
|
||||
>To exclude specific Office applications (for example, Access and InfoPath) when you create the App-V package with the Office Deployment Tool, use the **ExcludeApp** setting. For more information, see [Reference for Click-to-Run configuration.xml file](/DeployOffice/configuration-options-for-the-office-2016-deployment-tool#excludeapp-element).
|
||||
|
||||
#### To disable an Office 2013 application
|
||||
|
||||
@ -412,7 +412,7 @@ This section describes the requirements and options for deploying Visio 2013 and
|
||||
|Goal|Method|
|
||||
|---|---|
|
||||
|Create two different packages and deploy each one to a different group of users|Create and deploy the following packages:<br>A package that contains only Office—deploy to computers whose users need only Office.<br>A package that contains Office, Visio, and Project—deploy to computers whose users need all three applications.|
|
||||
|Create just one package for the whole organization, or for users who share computers|Follow these steps:<br>1. Create a package that contains Office, Visio, and Project.<br>2. Deploy the package to all users.<br>3. Use [AppLocker](https://docs.microsoft.com/windows/security/threat-protection/applocker/applocker-overview) to prevent specific users from using Visio and Project.|
|
||||
|Create just one package for the whole organization, or for users who share computers|Follow these steps:<br>1. Create a package that contains Office, Visio, and Project.<br>2. Deploy the package to all users.<br>3. Use [AppLocker](/windows/security/threat-protection/applocker/applocker-overview) to prevent specific users from using Visio and Project.|
|
||||
|
||||
## Additional resources
|
||||
|
||||
@ -434,7 +434,4 @@ This section describes the requirements and options for deploying Visio 2013 and
|
||||
|
||||
### Additional resources for Dynamic Configuration
|
||||
|
||||
* [About App-V Dynamic Configuration](appv-dynamic-configuration.md)
|
||||
|
||||
|
||||
|
||||
* [About App-V Dynamic Configuration](appv-dynamic-configuration.md)
|
||||
@ -39,7 +39,7 @@ Before you deploy Office with App-V, review the following requirements.
|
||||
|-----------|-------------------|
|
||||
| Packaging. | All Office applications that you deploy to users must be in a single package.<br>In App-V 5.0 and later, you must use the Office Deployment Tool to create packages. The Sequencer doesn't support package creation.<br>If you're deploying Microsoft Visio 2016 and Microsoft Project 2016 at the same time as Office, you must put them all in the same package. For more information, see [Deploying Visio 2016 and Project 2016 with Office](#deploying-visio-2016-and-project-2016-with-office). |
|
||||
| Publishing. | You can only publish one Office package per client computer.<br>You must publish the Office package globally, not to the user. |
|
||||
| Deploying Microsoft 365 Apps for enterprise, Visio Pro for Office 365, or Project Pro for Office 365 to a shared computer with Remote Desktop Services. | You must enable [shared computer activation](https://docs.microsoft.com/DeployOffice/overview-of-shared-computer-activation-for-office-365-proplus). |
|
||||
| Deploying Microsoft 365 Apps for enterprise, Visio Pro for Office 365, or Project Pro for Office 365 to a shared computer with Remote Desktop Services. | You must enable [shared computer activation](/DeployOffice/overview-of-shared-computer-activation-for-office-365-proplus). |
|
||||
|
||||
### Excluding Office applications from a package
|
||||
|
||||
@ -47,7 +47,7 @@ The following table describes the recommended methods for excluding specific Off
|
||||
|
||||
|Task|Details|
|
||||
|-------------|---------------|
|
||||
| Use the **ExcludeApp** setting when you create the package by using the Office Deployment Tool. | With this setting, you can exclude specific Office applications from the package that the Office Deployment Tool creates. For example, you can use this setting to create a package that contains only Microsoft Word.<br>For more information, see [ExcludeApp element](https://docs.microsoft.com/DeployOffice/configuration-options-for-the-office-2016-deployment-tool?ui=en-US&rs=en-US&ad=US#excludeapp-element). |
|
||||
| Use the **ExcludeApp** setting when you create the package by using the Office Deployment Tool. | With this setting, you can exclude specific Office applications from the package that the Office Deployment Tool creates. For example, you can use this setting to create a package that contains only Microsoft Word.<br>For more information, see [ExcludeApp element](/DeployOffice/configuration-options-for-the-office-2016-deployment-tool?ad=US&rs=en-US&ui=en-US#excludeapp-element). |
|
||||
| Modify the DeploymentConfig.xml file | Modify the DeploymentConfig.xml file after the package has been created. This file contains the default package settings for all users on a computer that is running the App-V Client.<br>For more information, see [Disabling Office 2016 applications](#disabling-office-2016-applications). |
|
||||
|
||||
## Creating an Office 2016 package for App-V with the Office Deployment Tool
|
||||
@ -124,7 +124,7 @@ The XML file included in the Office Deployment Tool specifies the product detail
|
||||
| Language element | Specifies which language the applications support. | `Language ID="en-us"` |
|
||||
| Version (attribute of **Add** element) | Optional. Specifies which build the package will use.<br>Defaults to latest advertised build (as defined in v32.CAB at the Office source). | `16.1.2.3` |
|
||||
| SourcePath (attribute of **Add** element) | Specifies the location the applications will be saved to. | `Sourcepath = "\\Server\Office2016"` |
|
||||
| Channel (part of **Add** element) | Optional. Defines which channel will be used to update Office after installation.<br>The default is **Deferred** for Microsoft 365 Apps for enterprise and **Current** for Visio Pro for Office 365 and Project Desktop Client. <br>For more information about update channels, see [Overview of update channels for Microsoft 365 Apps for enterprise](https://docs.microsoft.com/DeployOffice/overview-of-update-channels-for-office-365-proplus). | `Channel="Current"`<br>`Channel="Deferred"`<br>`Channel="FirstReleaseDeferred"`<br>`Channel="FirstReleaseCurrent"` |
|
||||
| Channel (part of **Add** element) | Optional. Defines which channel will be used to update Office after installation.<br>The default is **Deferred** for Microsoft 365 Apps for enterprise and **Current** for Visio Pro for Office 365 and Project Desktop Client. <br>For more information about update channels, see [Overview of update channels for Microsoft 365 Apps for enterprise](/DeployOffice/overview-of-update-channels-for-office-365-proplus). | `Channel="Current"`<br>`Channel="Deferred"`<br>`Channel="FirstReleaseDeferred"`<br>`Channel="FirstReleaseCurrent"` |
|
||||
|
||||
After editing the **configuration.xml** file to specify the desired product, languages, and the location where the Office 2016 applications will be saved to, you can save the configuration file under a name of your choice, such as "Customconfig.xml."
|
||||
2. **Download the applications into the specified location:** Use an elevated command prompt and a 64-bit operating system to download the Office 2016 applications that will later be converted into an App-V package. The following is an example command:
|
||||
@ -373,14 +373,11 @@ The following table describes the requirements and options for deploying Visio 2
|
||||
| Task | Details |
|
||||
|---------------------|---------------|
|
||||
| How do I package and publish Visio 2016 and Project 2016 with Office? | You must include Visio 2016 and Project 2016 in the same package with Office.<br>If you are not deploying Office, you can create a package that contains Visio and/or Project, as long as you follow the packaging, publishing, and deployment requirements described in this topic. |
|
||||
| How can I deploy Visio 2016 and Project 2016 to specific users? | Use one of the following methods:<br>**To create two different packages and deploy each one to a different group of users**:<br>Create and deploy the following packages:<br>- A package that contains only Office—deploy to computers whose users need only Office.<br>- A package that contains Office, Visio, and Project—deploy to computers whose users need all three applications.<br><br>**To create only one package for the whole organization, or to create a package intended for users who share computers**:<br>1. Create a package that contains Office, Visio, and Project.<br>2. Deploy the package to all users.<br>3. Use [AppLocker](https://docs.microsoft.com/windows/security/threat-protection/applocker/applocker-overview) to prevent specific users from using Visio and Project. |
|
||||
| How can I deploy Visio 2016 and Project 2016 to specific users? | Use one of the following methods:<br>**To create two different packages and deploy each one to a different group of users**:<br>Create and deploy the following packages:<br>- A package that contains only Office—deploy to computers whose users need only Office.<br>- A package that contains Office, Visio, and Project—deploy to computers whose users need all three applications.<br><br>**To create only one package for the whole organization, or to create a package intended for users who share computers**:<br>1. Create a package that contains Office, Visio, and Project.<br>2. Deploy the package to all users.<br>3. Use [AppLocker](/windows/security/threat-protection/applocker/applocker-overview) to prevent specific users from using Visio and Project. |
|
||||
|
||||
## Related topics
|
||||
|
||||
* [Deploying App-V for Windows 10](appv-deploying-appv.md)
|
||||
* [Deploying Microsoft Office 2013 by using App-V](appv-deploying-microsoft-office-2013-with-appv.md)
|
||||
* [Deploying Microsoft Office 2010 by using App-V](appv-deploying-microsoft-office-2010-wth-appv.md)
|
||||
* [Office 2016 Deployment Tool for Click-to-Run](https://www.microsoft.com/download/details.aspx?id=49117)
|
||||
|
||||
|
||||
|
||||
* [Office 2016 Deployment Tool for Click-to-Run](https://www.microsoft.com/download/details.aspx?id=49117)
|
||||
@ -18,7 +18,7 @@ ms.topic: article
|
||||
|
||||
You can deploy App-V packages using an electronic software distribution (ESD) solution. For information about planning to deploy App-V packages with an ESD, see [Planning to deploy App-V with an electronic software distribution system](appv-planning-to-deploy-appv-with-electronic-software-distribution-solutions.md).
|
||||
|
||||
To learn how to deploy App-V packages with Microsoft System Center 2012 Configuration Manager, see [Introduction to application management in Configuration Manager](https://technet.microsoft.com/library/gg682125.aspx#BKMK_Appv)
|
||||
To learn how to deploy App-V packages with Microsoft System Center 2012 Configuration Manager, see [Introduction to application management in Configuration Manager](/previous-versions/system-center/system-center-2012-R2/gg682125(v=technet.10)#BKMK_Appv)
|
||||
|
||||
## How to deploy virtualized packages using an ESD
|
||||
|
||||
@ -31,7 +31,4 @@ To learn how to configure the App-V client to enable only administrators to publ
|
||||
## Related topics
|
||||
|
||||
- [App-V and Citrix integration](https://www.microsoft.com/download/details.aspx?id=40885)
|
||||
- [Operations for App-V](appv-operations.md)
|
||||
|
||||
|
||||
|
||||
- [Operations for App-V](appv-operations.md)
|
||||
@ -25,7 +25,7 @@ If you’re already using App-V, performing an in-place upgrade to Windows 10 on
|
||||
>[!IMPORTANT]
|
||||
>You can upgrade your existing App-V installation to App-V for Windows from App-V versions 5.0 SP2 and higher only. If you are using an earlier version of App-V, you’ll need to upgrade your existing App-V installation to App-V 5.0 SP2 before upgrading to App-V for Windows.
|
||||
|
||||
To learn more about previous versions of App-V, see [MDOP information experience](https://docs.microsoft.com/microsoft-desktop-optimization-pack/index).
|
||||
To learn more about previous versions of App-V, see [MDOP information experience](/microsoft-desktop-optimization-pack/index).
|
||||
|
||||
## Getting started with App-V for Windows 10 (new installations)
|
||||
|
||||
@ -58,4 +58,4 @@ If you're new to App-V, it's a good idea to read the documentation thoroughly. B
|
||||
* [Deploying App-V](appv-deploying-appv.md)
|
||||
* [Operations for App-V](appv-operations.md)
|
||||
* [Troubleshooting App-V](appv-troubleshooting.md)
|
||||
* [Technical reference for App-V](appv-technical-reference.md)
|
||||
* [Technical reference for App-V](appv-technical-reference.md)
|
||||
@ -82,7 +82,7 @@ Starting in App-V 5.0 SP3, cmdlet help is available in two formats:
|
||||
|App-V Sequencer|**Update-Help -Module AppvSequencer**|
|
||||
|App-V Client|**Update-Help -Module AppvClient**|
|
||||
|
||||
* Online in the [Microsoft Desktop Optimization Pack](https://docs.microsoft.com/powershell/mdop/get-started?view=win-mdop2-ps).
|
||||
* Online in the [Microsoft Desktop Optimization Pack](/powershell/mdop/get-started?view=win-mdop2-ps).
|
||||
|
||||
## Displaying the help for a Windows PowerShell cmdlet
|
||||
|
||||
@ -92,7 +92,4 @@ To display help for a specific Windows PowerShell cmdlet:
|
||||
2. Enter **Get-Help** followed by the cmdlet you need help with. For example:
|
||||
```PowerShell
|
||||
Get-Help Publish-AppvClientPackage
|
||||
```
|
||||
|
||||
|
||||
|
||||
```
|
||||
@ -128,7 +128,7 @@ Remove-AppvClientPackage "ContosoApplication"
|
||||
```
|
||||
|
||||
> [!NOTE]
|
||||
> App-V cmdlets have been assigned to variables for the previous examples for clarity only; assignment is not a requirement. Most cmdlets can be combined as displayed in [Add and publish a package](appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md#add-and-publish-a-package). For a detailed tutorial, see [App-V 5.0 Client PowerShell Deep Dive](https://blogs.technet.microsoft.com/appv/2012/12/03/app-v-5-0-client-powershell-deep-dive/).
|
||||
> App-V cmdlets have been assigned to variables for the previous examples for clarity only; assignment is not a requirement. Most cmdlets can be combined as displayed in [Add and publish a package](appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md#add-and-publish-a-package). For a detailed tutorial, see [App-V 5.0 Client PowerShell Deep Dive](/archive/blogs/appv/app-v-5-0-client-powershell-deep-dive).
|
||||
|
||||
## Enable only administrators to publish or unpublish packages
|
||||
|
||||
@ -172,4 +172,4 @@ For more information about pending tasks, see [Upgrading an in-use App-V package
|
||||
## Related topics
|
||||
|
||||
- [Operations for App-V](appv-operations.md)
|
||||
- [Administering App-V by using Windows PowerShell](appv-administering-appv-with-powershell.md)
|
||||
- [Administering App-V by using Windows PowerShell](appv-administering-appv-with-powershell.md)
|
||||
@ -259,4 +259,4 @@ There is no direct method to upgrade to a full App-V infrastructure. Use the inf
|
||||
|
||||
- [Operations for App-V](appv-operations.md)
|
||||
|
||||
- [A simplified Microsoft App-V 5.1 Management Server upgrade procedure](https://blogs.technet.microsoft.com/appv/2015/09/23/a-simplified-microsoft-app-v-5-1-management-server-upgrade-procedure/)
|
||||
- [A simplified Microsoft App-V 5.1 Management Server upgrade procedure](/archive/blogs/appv/a-simplified-microsoft-app-v-5-1-management-server-upgrade-procedure)
|
||||
@ -457,7 +457,7 @@ The following section contains lists with information about Microsoft documentat
|
||||
|
||||
Server Performance Tuning Guidelines for
|
||||
|
||||
- [Microsoft Windows Server 2012 R2](https://msdn.microsoft.com/library/windows/hardware/dn529133.aspx)
|
||||
- [Microsoft Windows Server 2012 R2](/previous-versions//dn529133(v=vs.85))
|
||||
|
||||
- [Microsoft Windows Server 2012](https://download.microsoft.com/download/0/0/B/00BE76AF-D340-4759-8ECD-C80BC53B6231/performance-tuning-guidelines-windows-server-2012.docx)
|
||||
|
||||
@ -465,23 +465,23 @@ Server Performance Tuning Guidelines for
|
||||
|
||||
**Server Roles**
|
||||
|
||||
- [Remote Desktop Virtualization Host](https://msdn.microsoft.com/library/windows/hardware/dn567643.aspx)
|
||||
- [Remote Desktop Virtualization Host](/previous-versions//dn567643(v=vs.85))
|
||||
|
||||
- [Remote Desktop Session Host](https://msdn.microsoft.com/library/windows/hardware/dn567648.aspx)
|
||||
- [Remote Desktop Session Host](/previous-versions//dn567648(v=vs.85))
|
||||
|
||||
- [IIS Relevance: App-V Management, Publishing, Reporting Web Services](https://msdn.microsoft.com/library/windows/hardware/dn567678.aspx)
|
||||
- [IIS Relevance: App-V Management, Publishing, Reporting Web Services](/previous-versions//dn567678(v=vs.85))
|
||||
|
||||
- [File Server (SMB) Relevance: If used for App-V Content Storage and Delivery in SCS Mode](https://technet.microsoft.com/library/jj134210.aspx)
|
||||
- [File Server (SMB) Relevance: If used for App-V Content Storage and Delivery in SCS Mode](/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/jj134210(v=ws.11))
|
||||
|
||||
**Windows Client (Guest OS) Performance Tuning Guidance**
|
||||
|
||||
- [Microsoft Windows 7](https://download.microsoft.com/download/E/5/7/E5783D68-160B-4366-8387-114FC3E45EB4/Performance Tuning Guidelines for Windows 7 Desktop Virtualization v1.9.docx)
|
||||
|
||||
- [Optimization Script: (Provided by Microsoft Support)](https://blogs.technet.com/b/jeff_stokes/archive/2012/10/15/the-microsoft-premier-field-engineer-pfe-view-on-virtual-desktop-vdi-density.aspx)
|
||||
- [Optimization Script: (Provided by Microsoft Support)](/archive/blogs/jeff_stokes/the-microsoft-premier-field-engineer-pfe-view-on-virtual-desktop-vdi-density)
|
||||
|
||||
- [Microsoft Windows 8](https://download.microsoft.com/download/6/0/1/601D7797-A063-4FA7-A2E5-74519B57C2B4/Windows_8_VDI_Image_Client_Tuning_Guide.pdf)
|
||||
|
||||
- [Optimization Script: (Provided by Microsoft Support)](https://blogs.technet.com/b/jeff_stokes/archive/2013/04/09/hot-off-the-presses-get-it-now-the-windows-8-vdi-optimization-script-courtesy-of-pfe.aspx)
|
||||
- [Optimization Script: (Provided by Microsoft Support)](/archive/blogs/jeff_stokes/hot-off-the-presses-get-it-now-the-windows-8-vdi-optimization-script-courtesy-of-pfe)
|
||||
|
||||
## Sequencing Steps to Optimize Packages for Publishing Performance
|
||||
|
||||
@ -742,4 +742,4 @@ The following terms are used when describing concepts and actions related to App
|
||||
|
||||
## Related topics
|
||||
|
||||
[Application Virtualization (App-V) overview](appv-for-windows.md)
|
||||
[Application Virtualization (App-V) overview](appv-for-windows.md)
|
||||
@ -34,12 +34,12 @@ Review the following articles to learn more about configuring IIS and NLB for co
|
||||
|
||||
* [Achieving High Availability and Scalability - ARR and NLB](https://www.iis.net/learn/extensions/configuring-application-request-routing-arr/achieving-high-availability-and-scalability-arr-and-nlb) describes how to configure IIS 7.0.
|
||||
|
||||
* [Network load balancing overview](<https://docs.microsoft.com/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/hh831698(v=ws.11)>) will tell you more about how to configure Microsoft Windows Server.
|
||||
* [Network load balancing overview](/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/hh831698(v=ws.11)) will tell you more about how to configure Microsoft Windows Server.
|
||||
|
||||
This information also applies to IIS NLB clusters in Windows Server 2008, Windows Server 2008 R2, or Windows Server 2012.
|
||||
|
||||
>[!NOTE]
|
||||
>The IIS NLB functionality in Windows Server 2012 is generally the same as in Windows Server 2008 R2. However, some task details have changed in Windows Server 2012. To learn how to work with these changes, see [Common management tasks and navigation in Windows](<https://docs.microsoft.com/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/hh831491(v=ws.11)>).
|
||||
>The IIS NLB functionality in Windows Server 2012 is generally the same as in Windows Server 2008 R2. However, some task details have changed in Windows Server 2012. To learn how to work with these changes, see [Common management tasks and navigation in Windows](/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/hh831491(v=ws.11)).
|
||||
|
||||
## Support for clustered file servers when running SCS mode
|
||||
|
||||
@ -58,8 +58,8 @@ The following steps can be used to validate the configuration:
|
||||
|
||||
Review the following articles to learn more about configuring Windows Server failover clusters:
|
||||
|
||||
* [Create a failover cluster](<https://docs.microsoft.com/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/dn505754(v=ws.11)>)
|
||||
* [Use cluster shared volumes in a failover cluster](<https://docs.microsoft.com/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/jj612868(v=ws.11)>)
|
||||
* [Create a failover cluster](/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/dn505754(v=ws.11))
|
||||
* [Use cluster shared volumes in a failover cluster](/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/jj612868(v=ws.11))
|
||||
|
||||
## Support for Microsoft SQL Server mirroring
|
||||
|
||||
@ -67,8 +67,8 @@ Using Microsoft SQL Server mirroring, where the App-V management server database
|
||||
|
||||
Review the following to learn more about how to configure Microsoft SQL Server mirroring:
|
||||
|
||||
* [Prepare a mirror database for mirroring (SQL Server)](https://docs.microsoft.com/sql/database-engine/database-mirroring/prepare-a-mirror-database-for-mirroring-sql-server)
|
||||
* [Establish a database mirroring session using Windows Authentication (SQL Server Management Studio)](https://msdn.microsoft.com/library/ms188712.aspx) (FIX LINK)
|
||||
* [Prepare a mirror database for mirroring (SQL Server)](/sql/database-engine/database-mirroring/prepare-a-mirror-database-for-mirroring-sql-server)
|
||||
* [Establish a database mirroring session using Windows Authentication (SQL Server Management Studio)](/sql/database-engine/database-mirroring/establish-database-mirroring-session-windows-authentication) (FIX LINK)
|
||||
|
||||
The following steps can be used to validate the configuration:
|
||||
|
||||
@ -92,13 +92,13 @@ Use the following steps to modify the connection string to include ```failover p
|
||||
|
||||
Click any of the following links for more information:
|
||||
|
||||
* [Prepare a mirror database for mirroring (SQL Server)](https://docs.microsoft.com/sql/database-engine/database-mirroring/prepare-a-mirror-database-for-mirroring-sql-server).
|
||||
* [Establish a database mirroring session using Windows Authentication (SQL Server Management Studio)](https://docs.microsoft.com/sql/database-engine/database-mirroring/establish-database-mirroring-session-windows-authentication).
|
||||
* [Prepare a mirror database for mirroring (SQL Server)](/sql/database-engine/database-mirroring/prepare-a-mirror-database-for-mirroring-sql-server).
|
||||
* [Establish a database mirroring session using Windows Authentication (SQL Server Management Studio)](/sql/database-engine/database-mirroring/establish-database-mirroring-session-windows-authentication).
|
||||
* [Deprecated database engine features in SQL Server 2012](<https://msdn.microsoft.com/library/ms143729(v=sql.110).aspx>).
|
||||
|
||||
## Support for Microsoft SQL Server Always On configuration
|
||||
|
||||
The App-V management server database supports deployments to computers running Microsoft SQL Server with the **Always On** configuration. For more information, see [Always On Availability Groups (SQL Server)](https://docs.microsoft.com/sql/database-engine/availability-groups/windows/always-on-availability-groups-sql-server).
|
||||
The App-V management server database supports deployments to computers running Microsoft SQL Server with the **Always On** configuration. For more information, see [Always On Availability Groups (SQL Server)](/sql/database-engine/availability-groups/windows/always-on-availability-groups-sql-server).
|
||||
|
||||
|
||||
|
||||
@ -106,4 +106,4 @@ The App-V management server database supports deployments to computers running M
|
||||
|
||||
## Related topics
|
||||
|
||||
* [Planning to deploy App-V](appv-planning-to-deploy-appv.md)
|
||||
* [Planning to deploy App-V](appv-planning-to-deploy-appv.md)
|
||||
@ -16,7 +16,7 @@ ms.topic: article
|
||||
|
||||
>Applies to: Windows 10, version 1607
|
||||
|
||||
If you are using an electronic software distribution (ESD) system to deploy App-V packages, review the following planning considerations. For information about deploying App-V with Microsoft Endpoint Configuration Manager, see [Introduction to application management in Configuration Manager](https://technet.microsoft.com/library/gg682125.aspx#BKMK_Appv).
|
||||
If you are using an electronic software distribution (ESD) system to deploy App-V packages, review the following planning considerations. For information about deploying App-V with Microsoft Endpoint Configuration Manager, see [Introduction to application management in Configuration Manager](/previous-versions/system-center/system-center-2012-R2/gg682125(v=technet.10)#BKMK_Appv).
|
||||
|
||||
Review the following component and architecture requirements options that apply when you use an ESD to deploy App-V packages:
|
||||
|
||||
@ -33,4 +33,4 @@ Review the following component and architecture requirements options that apply
|
||||
|
||||
* [Planning to deploy App-V](appv-planning-to-deploy-appv.md)
|
||||
* [How to deploy App-V packages Using Electronic Software Distribution](appv-deploy-appv-packages-with-electronic-software-distribution-solutions.md)
|
||||
* [How to enable only administrators to publish packages by using an ESD](appv-enable-administrators-to-publish-packages-with-electronic-software-distribution-solutions.md)
|
||||
* [How to enable only administrators to publish packages by using an ESD](appv-enable-administrators-to-publish-packages-with-electronic-software-distribution-solutions.md)
|
||||
@ -99,7 +99,7 @@ The Management database is only required if you use the App-V Management server.
|
||||
|Custom database name (if applicable)|Unique database name.<br>Default: AppVManagement|
|
||||
|Management server location|Machine account on which the Management server is deployed.<br>Format to use: **Domain\MachineAccount**|
|
||||
|Management server installation administrator|Account used to install the Management server.<br>Format to use: **Domain\AdministratorLoginName**|
|
||||
|Microsoft SQL Server Service Agent|Configure the Management database computer so that the Microsoft SQL Server Agent service is restarted automatically. For instructions, see [Configure SQL Server Agent to restart services automatically](https://technet.microsoft.com/magazine/gg313742.aspx).|
|
||||
|Microsoft SQL Server Service Agent|Configure the Management database computer so that the Microsoft SQL Server Agent service is restarted automatically. For instructions, see [Configure SQL Server Agent to restart services automatically](/previous-versions/technet-magazine/gg313742(v=msdn.10)).|
|
||||
|
||||
### Publishing server prerequisite software
|
||||
|
||||
@ -163,4 +163,4 @@ What to know before installing the prerequisites:
|
||||
## Related topics
|
||||
|
||||
* [Planning for App-V](appv-planning-for-appv.md)
|
||||
* [App-V Supported Configurations](appv-supported-configurations.md)
|
||||
* [App-V Supported Configurations](appv-supported-configurations.md)
|
||||
@ -109,9 +109,9 @@ The following are known issues and workarounds for Application Virtualization (A
|
||||
For information that can help with troubleshooting App-V for Windows 10, see:
|
||||
- [Application Virtualization (App-V): List of Microsoft Support Knowledge Base Articles](https://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/)
|
||||
- [The Official Microsoft App-V Team Blog](/archive/blogs/appv/)
|
||||
|
||||
- [Technical Reference for App-V](https://technet.microsoft.com/itpro/windows/manage/appv-technical-reference)
|
||||
- [Technical Reference for App-V](./appv-technical-reference.md)
|
||||
|
||||
- [App-V TechNet Forum](https://social.technet.microsoft.com/forums/en-us/home?forum=mdopappv)
|
||||
|
||||
@ -121,4 +121,4 @@ For information that can help with troubleshooting App-V for Windows 10, see:
|
||||
## 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)
|
||||
- [Release Notes for App-V for Windows 10, version 1607](appv-release-notes-for-appv-for-windows-1703.md)
|
||||
@ -155,12 +155,11 @@ The App-V Sequencer cannot sequence applications with filenames matching "CO_<
|
||||
## 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](https://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)
|
||||
- [The Official Microsoft App-V Team Blog](/archive/blogs/appv/)
|
||||
- [Technical Reference for App-V](./appv-technical-reference.md)
|
||||
- [App-V TechNet Forum](https://social.technet.microsoft.com/forums/en-us/home?forum=mdopappv)
|
||||
|
||||
|
||||
<br>For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
|
||||
<a href="https://github.com/Microsoft/windows-itpro-docs/blob/master/CONTRIBUTING.md" class="button big">Help us to improve</a>
|
||||
|
||||
<a href="https://github.com/Microsoft/windows-itpro-docs/blob/master/CONTRIBUTING.md" class="button big">Help us to improve</a>
|
||||
@ -194,7 +194,7 @@ You can also use the **Send-AppVClientReport** cmdlet to manually collect data.
|
||||
|
||||
To retrieve report information and create reports using App-V you must use one of the following methods:
|
||||
|
||||
* Microsoft SQL Server Reporting Services (SSRS)—Microsoft SSRS is available with Microsoft SQL Server. SSRS is not installed when you install the App-V reporting server. It must be deployed separately to generate the associated reports. For more information, see the [What is SQL Server Reporting Services (SSRS)?](https://docs.microsoft.com/sql/reporting-services/create-deploy-and-manage-mobile-and-paginated-reports) article.
|
||||
* Microsoft SQL Server Reporting Services (SSRS)—Microsoft SSRS is available with Microsoft SQL Server. SSRS is not installed when you install the App-V reporting server. It must be deployed separately to generate the associated reports. For more information, see the [What is SQL Server Reporting Services (SSRS)?](/sql/reporting-services/create-deploy-and-manage-mobile-and-paginated-reports) article.
|
||||
|
||||
* Scripting—You can generate reports by scripting directly against the App-V reporting database. For example:
|
||||
|
||||
@ -202,7 +202,7 @@ To retrieve report information and create reports using App-V you must use one o
|
||||
|
||||
**spProcessClientReport** is scheduled to run at midnight or 12:00 AM.
|
||||
|
||||
To run the Microsoft SQL Server Scheduled Stored procedure, the Microsoft SQL Server Agent must be running. Make sure the Microsoft SQL Server Agent is set to **AutoStart**. For more information, see [Autostart SQL Server Agent (SQL Server Management Studio)](https://docs.microsoft.com/sql/ssms/agent/autostart-sql-server-agent-sql-server-management-studio).
|
||||
To run the Microsoft SQL Server Scheduled Stored procedure, the Microsoft SQL Server Agent must be running. Make sure the Microsoft SQL Server Agent is set to **AutoStart**. For more information, see [Autostart SQL Server Agent (SQL Server Management Studio)](/sql/ssms/agent/autostart-sql-server-agent-sql-server-management-studio).
|
||||
|
||||
The stored procedure is also created when you use the App-V database scripts.
|
||||
|
||||
@ -215,4 +215,4 @@ You should also ensure that the reporting server web service’s **Maximum Concu
|
||||
## Related topics
|
||||
|
||||
* [Deploying the App-V server](appv-deploying-the-appv-server.md)
|
||||
* [How to install the reporting server on a standalone computer and connect it to the database](appv-install-the-reporting-server-on-a-standalone-computer.md)
|
||||
* [How to install the reporting server on a standalone computer and connect it to the database](appv-install-the-reporting-server-on-a-standalone-computer.md)
|
||||
@ -33,7 +33,7 @@ Effective as of June, 2014, the PackageStoreAccessControl (PSAC) feature introdu
|
||||
|
||||
**Apply the most recent security updates to all computers**. To stay informed about the latest updates for operating systems, Microsoft SQL Server, and App-V, see the [Microsoft Security TechCenter](https://technet.microsoft.com/security/bb291012). (THIS LINK NEEDS TO BE UPDATED)
|
||||
|
||||
**Use strong passwords or pass phrases**. Always use strong passwords with 15 or more characters for all App-V and App-V administrator accounts. Never use blank passwords. For more information about password concepts, see [Password Policy](https://docs.microsoft.com/sql/relational-databases/security/password-policy) and [Strong Passwords](https://docs.microsoft.com/sql/relational-databases/security/strong-passwords). (THIS LINK NEEDS TO BE UPDATED)
|
||||
**Use strong passwords or pass phrases**. Always use strong passwords with 15 or more characters for all App-V and App-V administrator accounts. Never use blank passwords. For more information about password concepts, see [Password Policy](/sql/relational-databases/security/password-policy) and [Strong Passwords](/sql/relational-databases/security/strong-passwords). (THIS LINK NEEDS TO BE UPDATED)
|
||||
|
||||
## Accounts and groups in App-V
|
||||
|
||||
@ -72,4 +72,4 @@ During App-V setup, setup log files are created in the **%temp%** folder of the
|
||||
|
||||
## Related topics
|
||||
|
||||
[Preparing Your Environment for App-V](appv-preparing-your-environment.md)
|
||||
[Preparing Your Environment for App-V](appv-preparing-your-environment.md)
|
||||
@ -104,7 +104,7 @@ Similarly, the App-V Remote Desktop Services (RDS) client is included with Windo
|
||||
|
||||
## Sequencer system requirements
|
||||
|
||||
Sequencer is now part of the Windows Assessment and Deployment Kit (Windows ADK). [Download the latest Windows ADK](https://docs.microsoft.com/windows-hardware/get-started/adk-install) that is recommended for your version of the Windows OS.
|
||||
Sequencer is now part of the Windows Assessment and Deployment Kit (Windows ADK). [Download the latest Windows ADK](/windows-hardware/get-started/adk-install) that is recommended for your version of the Windows OS.
|
||||
|
||||
### Sequencer hardware requirements
|
||||
|
||||
@ -117,4 +117,4 @@ The App-V client works with Configuration Manager versions starting with Technic
|
||||
## Related topics
|
||||
|
||||
* [Planning to deploy App-V](appv-planning-to-deploy-appv.md)
|
||||
* [App-V prerequisites](appv-prerequisites.md)
|
||||
* [App-V prerequisites](appv-prerequisites.md)
|
||||
@ -50,4 +50,4 @@ This section provides reference information related to managing App-V.
|
||||
|
||||
[Administering App-V by Using Windows PowerShell](appv-administering-appv-with-powershell.md)
|
||||
|
||||
[Windows PowerShell reference for App-V](https://technet.microsoft.com/library/dn903534.aspx)
|
||||
[Windows PowerShell reference for App-V](/previous-versions/)
|
||||
@ -22,7 +22,7 @@ For information that can help with troubleshooting App-V for Windows 10, see:
|
||||
|
||||
- [Application Virtualization (App-V): List of Microsoft Support Knowledge Base Articles](https://social.technet.microsoft.com/wiki/contents/articles/14272.app-v-v5-x-list-of-microsoft-support-knowledge-base-articles.aspx)
|
||||
|
||||
- [Microsoft App-V Team Blog](https://blogs.technet.microsoft.com/appv/)
|
||||
- [Microsoft App-V Team Blog](/archive/blogs/appv/)
|
||||
|
||||
- [Release Notes for App-V](appv-release-notes-for-appv-for-windows.md)
|
||||
|
||||
@ -45,4 +45,4 @@ For information that can help with troubleshooting App-V for Windows 10, see:
|
||||
|
||||
|
||||
|
||||
<br>For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
<br>For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
@ -33,7 +33,7 @@ These steps are explained in more detail below.
|
||||
|
||||
## Upgrade user devices to Windows 10
|
||||
|
||||
Performing an in-place upgrade automatically installs the App-V client and migrates users’ App-V applications and settings. See the [Windows 10 and Windows 10 Mobile document set](https://technet.microsoft.com/itpro/windows/index) for information about upgrading user devices to Windows 10.
|
||||
Performing an in-place upgrade automatically installs the App-V client and migrates users’ App-V applications and settings. See the [Windows 10 and Windows 10 Mobile document set](/windows/windows-10/) for information about upgrading user devices to Windows 10.
|
||||
|
||||
## Verify that App-V applications and settings were migrated correctly
|
||||
|
||||
@ -99,4 +99,4 @@ Type the following cmdlet in a Windows PowerShell window:
|
||||
|
||||
|
||||
|
||||
<br>For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
<br>For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
Reference in New Issue
Block a user