mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-21 05:13:40 +00:00
Merge remote-tracking branch 'refs/remotes/origin/master' into live
This commit is contained in:
LizRoss
@ -1,5 +1,4 @@
|
||||
---
|
||||
localizationpriority: low
|
||||
ms.mktglfcycl: deploy
|
||||
description: Use this guide to learn about the several options and processes you'll need to consider while you're planning for, deploying, and customizing Internet Explorer 11 for your employee's devices.
|
||||
author: eross-msft
|
||||
|
||||
@ -1,5 +1,4 @@
|
||||
---
|
||||
localizationpriority: low
|
||||
ms.mktglfcycl: plan
|
||||
description: IEAK 11 - Internet Explorer Administration Kit 11 Users Guide
|
||||
author: eross-msft
|
||||
|
||||
@ -1,5 +1,4 @@
|
||||
---
|
||||
localizationpriority: low
|
||||
ms.mktglfcycl: deploy
|
||||
description: The landing page for IE11 that lets you access the documentation.
|
||||
author: eross-msft
|
||||
|
||||
@ -27,7 +27,7 @@ If you prefer to use a graphical user interface, you can create a device account
|
||||
|
||||
### <a href="" id="create-device-acct-o365-admin-ctr"></a>Create the account in the Office 365 Admin Center
|
||||
|
||||
1. Sign in to Office 365 by visiting http://portal.office.com/admin/
|
||||
1. Sign in to Office 365 by visiting http://portal.office.com
|
||||
2. Provide the admin credentials for your Office 365 tenant. This will take you to your Office 365 Admin Center.
|
||||
|
||||
|
||||
|
||||
@ -30,12 +30,12 @@ You should fill out one list for each Surface Hub you need to configure, althoug
|
||||
<p>Proxy information</p>
|
||||
</td>
|
||||
<td>
|
||||
<p>If your network uses a proxy to for network and/or Internet access, you must provide a script or server/port information.</p>
|
||||
<p>If your network uses a proxy for network and/or Internet access, you must provide a script or server/port information.</p>
|
||||
</td>
|
||||
<td>
|
||||
<p>http://contoso/proxy.pa (proxy script)
|
||||
OR
|
||||
10.10.10.100, port 8080 (server, port)
|
||||
<p>Proxy script: http://contoso/proxy.pa </br>
|
||||
- OR - </br>
|
||||
Server and port info: 10.10.10.100, port 80
|
||||
</p>
|
||||
</td>
|
||||
<td>
|
||||
@ -64,7 +64,9 @@ OR
|
||||
<p>This is the User Principal Name (UPN) or the domain\username, and the password of the device account. Mail, calendar, and Skype for Business depend on a compatible device account.</p>
|
||||
</td>
|
||||
<td>
|
||||
<p>ConfRoom15@contoso.com, #Passw0rd1 (for UPN) OR CONTOSO\ConfRoom15, #Passw0rd1 (for Domain\username)</p>
|
||||
<p> UPN: ConfRoom15@contoso.com, #Passw0rd1 </br>
|
||||
- OR - <br>
|
||||
Domain and username: CONTOSO\ConfRoom15, #Passw0rd1</p>
|
||||
</td>
|
||||
<td>
|
||||
<p></p>
|
||||
@ -96,7 +98,7 @@ Mail, calendar, and Skype for Business depend on a compatible device account.
|
||||
For Skype for Business to work, the device account must have a valid SIP address. The device will try to find this automatically.</p>
|
||||
</td>
|
||||
<td>
|
||||
<p>sip:ConfRoom15@contoso.com</p>
|
||||
<p>sip: ConfRoom15@contoso.com</p>
|
||||
</td>
|
||||
<td>
|
||||
<p></p>
|
||||
|
||||
@ -8,7 +8,6 @@ ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: activation
|
||||
author: greg-lindsay
|
||||
localizationpriority: medium
|
||||
---
|
||||
|
||||
# Monitor activation
|
||||
|
||||
@ -6,7 +6,6 @@ ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
localizationpriority: high
|
||||
author: brianlic-msft
|
||||
---
|
||||
# Keep Windows 10 secure
|
||||
|
||||
@ -12,41 +12,40 @@ localizationpriority: medium
|
||||
author: iaanw
|
||||
---
|
||||
|
||||
# Enable the Block at First Sight feature in Windows 10
|
||||
# Block at First Sight
|
||||
|
||||
**Applies to**
|
||||
|
||||
- Windows 10, version 1607
|
||||
|
||||
**Audience**
|
||||
|
||||
- Network administrators
|
||||
|
||||
Block at First Sight is a feature of Windows Defender cloud protection that provides a way to detect and block new malware within seconds.
|
||||
|
||||
You can enable Block at First Sight with Group Policy or individually on endpoints.
|
||||
It is enabled by default when certain pre-requisite settings are also enabled. In most cases, these pre-requisite settings are also enabled by default, so the feature is running without any intervention.
|
||||
|
||||
## Backend processing and near-instant determinations
|
||||
## How it works
|
||||
|
||||
When a Windows Defender client encounters a suspicious but previously undetected file, it queries our cloud protection backend. The cloud backend will apply heuristics, machine learning, and automated analysis of the file to determine the files as malicious or clean.
|
||||
When a Windows Defender client encounters a suspicious but undetected file, it queries our cloud protection backend. The cloud backend will apply heuristics, machine learning, and automated analysis of the file to determine the files as malicious or clean.
|
||||
|
||||
If the cloud backend is unable to make a determination, a copy of the file is requested for additional processing and analysis in the cloud.
|
||||
If the cloud backend is unable to make a determination, the file will be locked by Windows Defender while a copy is uploaded to the cloud. Only after the cloud has received the file will Windows Defender release the lock and let the file run. The cloud will perform additional analysis to reach a determination, blocking all future encounters of that file.
|
||||
|
||||
If the Block at First Sight feature is enabled on the client, the file will be locked by Windows Defender while a copy is uploaded to the cloud, processed, and a verdict returned to the client. Only after a determination is returned from the cloud will Windows Defender release the lock and let the file run.
|
||||
|
||||
The file-based determination typically takes 1 to 4 seconds.
|
||||
In many cases this process can reduce the response time to new malware from hours to seconds.
|
||||
|
||||
> [!NOTE]
|
||||
> Suspicious file downloads requiring additional backend processing to reach a determination will be locked by Windows Defender on the first machine where the file is encountered, until it is finished uploading to the backend. Users will see a longer "Running security scan" message in the browser while the file is being uploaded. This might result in what appear to be slower download times for some files.
|
||||
|
||||
|
||||
## Enable Block at First Sight
|
||||
## Confirm Block at First Sight is enabled
|
||||
|
||||
### Use Group Policy to configure Block at First Sight
|
||||
Block at First Sight requires a number of Group Policy settings to be configured correctly or it will not work. Usually, these settings are already enabled in most default Windows Defender deployments in enterprise networks.
|
||||
|
||||
You can use Group Policy to control whether Windows Defender will continue to lock a suspicious file until it is uploaded to the backend.
|
||||
> [!IMPORTANT]
|
||||
> There is no specific individual setting in System Center Configuration Manager to enable Block at First Sight. It is enabled by default when the pre-requisite settings are configured correctly.
|
||||
|
||||
This feature ensures the device checks in real time with the Microsoft Active Protection Service (MAPS) before allowing certain content to be run or accessed. If this feature is disabled, the check will not occur, which will lower the protection state of the device.
|
||||
|
||||
Block at First Sight requires a number of Group Policy settings to be configured correctly or it will not work.
|
||||
|
||||
**Configure pre-requisite cloud protection Group Policy settings:**
|
||||
### Confirm Block at First Sight is enabled with Group Policy
|
||||
|
||||
1. On your Group Policy management machine, open the [Group Policy Management Console](https://technet.microsoft.com/library/cc731212.aspx), right-click the Group Policy Object you want to configure and click **Edit**.
|
||||
|
||||
@ -56,28 +55,56 @@ Block at First Sight requires a number of Group Policy settings to be configured
|
||||
|
||||
5. Expand the tree to **Windows components > Windows Defender > MAPS** and configure the following Group Policies:
|
||||
|
||||
1. Double-click the **Join Microsoft MAPS** setting and set the option to **Enabled**. Click **OK**.
|
||||
1. Double-click the **Join Microsoft MAPS** setting and ensure the option is set to **Enabled**. Click **OK**.
|
||||
|
||||
1. Double-click the **Send file samples when further analysis is required** setting and set the option as **Enabled** and the additional options as either of the following:
|
||||
1. Double-click the **Send file samples when further analysis is required** setting and ensure the option is set to **Enabled** and the additional options are either of the following:
|
||||
|
||||
1. Send safe samples (1)
|
||||
|
||||
1. Send all samples (3)
|
||||
|
||||
> [!NOTE]
|
||||
> [!WARNING]
|
||||
> Setting to 0 (Always Prompt) will lower the protection state of the device. Setting to 2 (Never send) means the "Block at First Sight" feature will not function.
|
||||
|
||||
1. Click OK after both Group Policies have been set.
|
||||
1. Click **OK**.
|
||||
|
||||
1. In the **Group Policy Management Editor**, expand the tree to **Windows components > Windows Defender > Real-time Protection**:
|
||||
|
||||
1. Double-click the **Scan all downloaded files and attachments** setting and set the option to **Enabled**. Click **OK**.
|
||||
1. Double-click the **Scan all downloaded files and attachments** setting and ensure the option is set to **Enabled**. Click **OK**.
|
||||
|
||||
1. Double-click the **Turn off real-time protection** setting and set the option to **Disabled**. Click **OK**.
|
||||
1. Double-click the **Turn off real-time protection** setting and ensure the option is set to **Disabled**. Click **OK**.
|
||||
|
||||
If you had to change any of the settings, you should re-deploy the Group Policy Object across your network to ensure all endpoints are covered.
|
||||
|
||||
|
||||
### Confirm Block at First Sight is enabled with Windows Settings
|
||||
|
||||
**Enable Block at First Sight with Group Policy**
|
||||
> [!NOTE]
|
||||
> If the pre-requisite settings are configured and deployed using Group Policy, the settings described in this section will be greyed-out and unavailable for use on individual endpoints. Changes made through a Group Policy Object must first be deployed to individual endpoints before the setting will be updated in Windows Settings.
|
||||
|
||||
You can confirm that Block at First Sight is enabled in Windows Settings. The feature is automatically enabled, as long as **Cloud-based protection** and **Automatic sample submission** are both turned on.
|
||||
|
||||
**Confirm Block at First Sight is enabled on individual clients**
|
||||
|
||||
1. Open Windows Defender settings:
|
||||
|
||||
a. Open the Windows Defender app and click **Settings**.
|
||||
|
||||
b. On the main Windows Settings page, click **Update & Security** and then **Windows Defender**.
|
||||
|
||||
2. Confirm that **Cloud-based Protection** and **Automatic sample submission** are switched to **On**.
|
||||
|
||||
## Disable Block at First Sight
|
||||
|
||||
> [!WARNING]
|
||||
> Disabling the Block at First Sight feature will lower the protection state of the endpoint and your network.
|
||||
|
||||
> [!NOTE]
|
||||
> You cannot disable Block at First Sight with System Center Configuration Manager
|
||||
|
||||
You may choose to disable the Block at First Sight feature if you want to retain the pre-requisite settings without using Block at First Sight protection. You might wish to do this if you are experiencing latency issues or you want to test the feature's impact on your network.
|
||||
|
||||
**Disable Block at First Sight with Group Policy**
|
||||
|
||||
1. On your Group Policy management machine, open the [Group Policy Management Console](https://technet.microsoft.com/library/cc731212.aspx), right-click the Group Policy Object you want to configure and click **Edit**.
|
||||
|
||||
@ -87,28 +114,14 @@ Block at First Sight requires a number of Group Policy settings to be configured
|
||||
|
||||
5. Expand the tree through **Windows components > Windows Defender > MAPS**.
|
||||
|
||||
1. Double-click the **Configure the ‘Block at First Sight’ feature** setting and set the option to **Enabled**.
|
||||
1. Double-click the **Configure the ‘Block at First Sight’ feature** setting and set the option to **Disabled**.
|
||||
|
||||
> [!NOTE]
|
||||
> The Block at First Sight feature will not function if the pre-requisite group policies have not been correctly set.
|
||||
> Disabling the Block at First Sight feature will not disable or alter the pre-requisite group policies.
|
||||
|
||||
### Manually enable Block at First Sight on individual clients
|
||||
|
||||
To configure un-managed clients that are running Windows 10, Block at First Sight is automatically enabled as long as **Cloud-based protection** and **Automatic sample submission** are both turned on.
|
||||
|
||||
**Enable Block at First Sight on individual clients**
|
||||
|
||||
1. Open Windows Defender settings:
|
||||
|
||||
a. Open the Windows Defender app and click **Settings**.
|
||||
|
||||
b. On the main Windows Settings page, click **Update & Security** and then **Windows Defender**.
|
||||
|
||||
2. Switch **Cloud-based Protection** and **Automatic sample submission** to **On**.
|
||||
|
||||
> [!NOTE]
|
||||
> These settings will be overridden if the network administrator has configured their associated Group Policies. The settings will appear grayed out and you will not be able to modify them if they are being managed by Group Policy.
|
||||
|
||||
## Related topics
|
||||
|
||||
- [Windows Defender in Windows 10](windows-defender-in-windows-10.md)
|
||||
|
||||
|
||||
|
||||
@ -22,9 +22,9 @@ In Windows 10, application notifications about malware detection and remediation
|
||||
|
||||
Notifications will appear on endpoints when manually triggered and scheduled scans are completed and threats are detected. These notifications will also be seen in the **Notification Center**, and a summary of scans and threat detections will also appear at regular time intervals.
|
||||
|
||||
You can enable and disable enhanced notifications with the registry or in Windows Settings.
|
||||
You can enable and disable enhanced notifications in Windows Settings.
|
||||
|
||||
## Configure enhanced notifications
|
||||
## Disable notifications
|
||||
|
||||
You can disable enhanced notifications on individual endpoints in Windows Settings.
|
||||
|
||||
@ -39,6 +39,8 @@ You can disable enhanced notifications on individual endpoints in Windows Settin
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
## Related topics
|
||||
|
||||
- [Windows Defender in Windows 10](windows-defender-in-windows-10.md)
|
||||
@ -42,7 +42,6 @@
|
||||
##### [Release Notes for App-V](appv-release-notes-for-appv-for-windows.md)
|
||||
#### [Evaluating App-V](appv-evaluating-appv.md)
|
||||
#### [High Level Architecture for App-V](appv-high-level-architecture.md)
|
||||
#### [Accessibility for App-V](appv-accessibility.md)
|
||||
### [Planning for App-V](appv-planning-for-appv.md)
|
||||
#### [Preparing Your Environment for App-V](appv-preparing-your-environment.md)
|
||||
##### [App-V Prerequisites](appv-prerequisites.md)
|
||||
@ -62,7 +61,6 @@
|
||||
##### [About Client Configuration Settings](appv-client-configuration-settings.md)
|
||||
##### [Enable the App-V desktop client](appv-enable-the-app-v-desktop-client.md)
|
||||
##### [How to Install the Sequencer](appv-install-the-sequencer.md)
|
||||
##### [How to Modify App-V Client Configuration Using the ADMX Template and Group Policy](appv-modify-client-configuration-with-the-admx-template-and-group-policy.md)
|
||||
#### [Deploying the App-V Server](appv-deploying-the-appv-server.md)
|
||||
##### [How to Deploy the App-V Server](appv-deploy-the-appv-server.md)
|
||||
##### [How to Deploy the App-V Server Using a Script](appv-deploy-the-appv-server-with-a-script.md)
|
||||
@ -108,8 +106,6 @@
|
||||
##### [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)
|
||||
##### [How to Access the Client Management Console](appv-accessing-the-client-management-console.md)
|
||||
##### [How to Configure the Client to Receive Package and Connection Groups Updates From the Publishing Server ](appv-configure-the-client-to-receive-updates-from-the-publishing-server.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)
|
||||
@ -119,6 +115,7 @@
|
||||
##### [How to Manage App-V Packages Running on a Stand-Alone Computer by Using PowerShell](appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md)
|
||||
##### [How to Manage Connection Groups on a Stand-alone Computer by Using PowerShell](appv-manage-connection-groups-on-a-stand-alone-computer-with-powershell.md)
|
||||
##### [How to Modify Client Configuration by Using PowerShell](appv-modify-client-configuration-with-powershell.md)
|
||||
##### [How to Configure the Client to Receive Package and Connection Groups Updates From the Publishing Server](appv-configure-the-client-to-receive-updates-from-the-publishing-server.md)
|
||||
##### [How to Apply the User Configuration File by Using PowerShell](appv-apply-the-user-configuration-file-with-powershell.md)
|
||||
##### [How to Apply the Deployment Configuration File by Using PowerShell](appv-apply-the-deployment-configuration-file-with-powershell.md)
|
||||
##### [How to Sequence a Package by Using PowerShell ](appv-sequence-a-package-with-powershell.md)
|
||||
|
||||
@ -1,169 +1,4 @@
|
||||
---
|
||||
title: Accessibility for App-V (Windows 10)
|
||||
description: Accessibility for App-V
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
redirect_url: https://technet.microsoft.com/itpro/windows/manage/appv-getting-started
|
||||
---
|
||||
|
||||
|
||||
# Accessibility for App-V
|
||||
|
||||
|
||||
Microsoft is committed to making its products and services easier for everyone to use. This section provides information about features and services that make this product and its corresponding documentation more accessible for people with disabilities.
|
||||
|
||||
## Keyboard Shortcuts for the App-V Management Server
|
||||
|
||||
|
||||
Following are the keyboard Shortcuts for the App-V Management Server:
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">To do this</th>
|
||||
<th align="left">Press</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Close a dialog box.</p></td>
|
||||
<td align="left"><p>Esc</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Perform the default action of a dialog box.</p></td>
|
||||
<td align="left"><p>Enter</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Refresh the current page of the App-V client console.</p></td>
|
||||
<td align="left"><p>F5</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
## Keyboard Shortcuts for the App-V Sequencer
|
||||
|
||||
|
||||
Following are the keyboard shortcuts for the Virtual Registry tab in the package editor in the App-V Sequencer:
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">To do this</th>
|
||||
<th align="left">Press</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Open the Find dialog box.</p></td>
|
||||
<td align="left"><p>CTRL + F</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Open the Replace dialog box.</p></td>
|
||||
<td align="left"><p>CTRL + H</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
### Access Any Command with a Few Keystrokes
|
||||
|
||||
**Important**
|
||||
The information in this section only applies to the App-V sequencer. For specific information about the App-V server, see the Keyboard Shortcuts for the App-V Management Server section of this document.
|
||||
|
||||
|
||||
|
||||
Access keys let you quickly use a command by pressing a few keys. You can get to most commands by using two keystrokes. To use an access key:
|
||||
|
||||
1. Press ALT.
|
||||
|
||||
An underline appears beneath the keyboard shortcut for each feature that is available in the current view.
|
||||
|
||||
2. Press the letter underlined in the keyboard shortcut for the feature that you want to use.
|
||||
|
||||
**Note**
|
||||
To cancel the action that you are taking and hide the keyboard shortcuts, press ALT.
|
||||
|
||||
|
||||
|
||||
## Documentation in Alternative Formats
|
||||
|
||||
|
||||
If you have difficulty reading or handling printed materials, you can obtain the documentation for many Microsoft products in more accessible formats. You can view an index of accessible product documentation on the Microsoft Accessibility website. In addition, you can obtain additional Microsoft publications from Learning Ally (formerly Recording for the Blind & Dyslexic, Inc.). Learning Ally distributes these documents to registered, eligible members of their distribution service.
|
||||
|
||||
For information about the availability of Microsoft product documentation and books from Microsoft Press, contact:
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
<col width="50%" />
|
||||
</colgroup>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p><strong>Learning Ally (formerly Recording for the Blind & Dyslexic, Inc.)</strong></p>
|
||||
<p>20 Roszel Road</p>
|
||||
<p>Princeton, NJ 08540</p></td>
|
||||
<td align="left"><p></p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Telephone number from within the United States:</p></td>
|
||||
<td align="left"><p>(800) 221-4792</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Telephone number from outside the United States and Canada:</p></td>
|
||||
<td align="left"><p>(609) 452-0606</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Fax:</p></td>
|
||||
<td align="left"><p>(609) 987-8116</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>[http://www.learningally.org/](http://go.microsoft.com/fwlink/?linkid=239)</p></td>
|
||||
<td align="left"><p>Web addresses can change, so you might be unable to connect to the website or sites mentioned here.</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
## Customer Service for People with Hearing Impairments
|
||||
|
||||
|
||||
If you are deaf or hard-of-hearing, complete access to Microsoft product and customer services is available through a text telephone (TTY/TDD) service:
|
||||
|
||||
- For customer service, contact Microsoft Sales Information Center at (800) 892-5234 between 6:30 AM and 5:30 PM Pacific Time, Monday through Friday, excluding holidays.
|
||||
|
||||
- For technical assistance in the United States, contact Microsoft Product Support Services at (800) 892-5234 between 6:00 AM and 6:00 PM Pacific Time, Monday through Friday, excluding holidays. In Canada, dial (905) 568-9641 between 8:00 AM and 8:00 PM Eastern Time, Monday through Friday, excluding holidays.
|
||||
|
||||
Microsoft Support Services are subject to the prices, terms, and conditions in place at the time the service is used.
|
||||
|
||||
## For More Information
|
||||
|
||||
|
||||
For more information about how accessible technology for computers helps to improve the lives of people with disabilities, see the [Microsoft Accessibility website](http://go.microsoft.com/fwlink/?linkid=8431).
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[Getting Started with App-V](appv-getting-started.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -1,26 +1,4 @@
|
||||
---
|
||||
title: How to access the client management console (Windows 10)
|
||||
description: How to access the client management console
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
redirect_url: https://technet.microsoft.com/itpro/windows/manage/appv-using-the-client-management-console
|
||||
---
|
||||
|
||||
# How to access the client management console
|
||||
|
||||
Use the App-V client management console to manage packages on the computer running the App-V client.
|
||||
|
||||
> [!NOTE]
|
||||
To perform all of the actions available using the client management console, you must have administrative access on the computer running the App-V client.
|
||||
|
||||
The client management console is available from the [Microsoft Download Center](https://www.microsoft.com/en-us/download/details.aspx?id=41186).
|
||||
|
||||
## Have a suggestion for App-V?
|
||||
|
||||
Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). 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)
|
||||
|
||||
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# How to Add or Remove an Administrator by Using the Management Console
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
Use the following procedures to add or remove an administrator on the Microsoft Application Virtualization (App-V) server.
|
||||
|
||||
|
||||
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# How to Add or Upgrade Packages by Using the Management Console
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
You can the following procedure to add or upgrade a package to the App-V Management Console. To upgrade a package that already exists in the Management Console, use the following steps and import the upgraded package using the same package **Name**.
|
||||
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Administering App-V by Using PowerShell (Windows 10)
|
||||
description: Administering App-V by Using PowerShell
|
||||
title: Administering App-V by Using Windows PowerShell (Windows 10)
|
||||
description: Administering App-V by Using Windows PowerShell
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
@ -9,15 +9,16 @@ ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# Administering App-V by Using PowerShell
|
||||
# Administering App-V by Using Windows PowerShell
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
Microsoft Application Virtualization (App-V) provides Windows PowerShell cmdlets, which can help administrators perform various App-V tasks. The following sections provide more information about using Windows PowerShell with App-V.
|
||||
|
||||
## How to administer App-V by using Windows PowerShell
|
||||
|
||||
|
||||
Microsoft Application Virtualization (App-V) provides Windows PowerShell cmdlets, which can help administrators perform various App-V tasks. The following sections provide more information about using PowerShell with App-V.
|
||||
|
||||
## How to administer App-V by using PowerShell
|
||||
|
||||
|
||||
Use the following PowerShell procedures to perform various App-V tasks.
|
||||
Use the following Windows PowerShell procedures to perform various App-V tasks.
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
@ -33,35 +34,35 @@ Use the following PowerShell procedures to perform various App-V tasks.
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>[How to Load the PowerShell Cmdlets and Get Cmdlet Help](appv-load-the-powershell-cmdlets-and-get-cmdlet-help.md)</p></td>
|
||||
<td align="left"><p>Describes how to install the PowerShell cmdlets and find cmdlet help and examples.</p></td>
|
||||
<td align="left"><p>Describes how to install the Windows PowerShell cmdlets and find cmdlet help and examples.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>[How to Manage App-V Packages Running on a Stand-Alone Computer by Using PowerShell](appv-manage-appv-packages-running-on-a-stand-alone-computer-with-powershell.md)</p></td>
|
||||
<td align="left"><p>Describes how to manage the client package lifecycle on a stand-alone computer using PowerShell.</p></td>
|
||||
<td align="left"><p>Describes how to manage the client package lifecycle on a stand-alone computer by using Windows PowerShell.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>[How to Manage Connection Groups on a Stand-alone Computer by Using PowerShell](appv-manage-connection-groups-on-a-stand-alone-computer-with-powershell.md)</p></td>
|
||||
<td align="left"><p>Describes how to manage connection groups using PowerShell.</p></td>
|
||||
<td align="left"><p>Describes how to manage connection groups by using Windows PowerShell.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>[How to Modify Client Configuration by Using PowerShell](appv-modify-client-configuration-with-powershell.md)</p></td>
|
||||
<td align="left"><p>Describes how to modify the client using PowerShell.</p></td>
|
||||
<td align="left"><p>[How to Modify Client Configuration by Using Windows PowerShell](appv-modify-client-configuration-with-powershell.md)</p></td>
|
||||
<td align="left"><p>Describes how to modify the client by using Windows PowerShell.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>[How to Apply the User Configuration File by Using PowerShell](appv-apply-the-user-configuration-file-with-powershell.md)</p></td>
|
||||
<td align="left"><p>Describes how to apply a user configuration file using PowerShell.</p></td>
|
||||
<td align="left"><p>Describes how to apply a user configuration file by using Windows PowerShell.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>[How to Apply the Deployment Configuration File by Using PowerShell](appv-apply-the-deployment-configuration-file-with-powershell.md)</p></td>
|
||||
<td align="left"><p>Describes how to apply a deployment configuration file using PowerShell.</p></td>
|
||||
<td align="left"><p>Describes how to apply a deployment configuration file by using Windows PowerShell.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>[How to Sequence a Package by Using PowerShell](appv-sequence-a-package-with-powershell.md)</p></td>
|
||||
<td align="left"><p>Describes how to create a new package using PowerShell.</p></td>
|
||||
<td align="left"><p>Describes how to create a new package by using Windows PowerShell.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>[How to Create a Package Accelerator by Using PowerShell](appv-create-a-package-accelerator-with-powershell.md)</p></td>
|
||||
<td align="left"><p>Describes how to create a package accelerator using PowerShell. You can use package accelerators automatically sequence large, complex applications.</p></td>
|
||||
<td align="left"><p>Describes how to create a package accelerator by using Windows PowerShell. You can use package accelerators automatically sequence large, complex applications.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>[How to Enable Reporting on the App-V Client by Using PowerShell](appv-enable-reporting-on-the-appv-client-with-powershell.md)</p></td>
|
||||
@ -71,17 +72,22 @@ Use the following PowerShell procedures to perform various App-V tasks.
|
||||
<td align="left"><p>[How to Install the App-V Databases and Convert the Associated Security Identifiers by Using PowerShell](appv-install-the-appv-databases-and-convert-the-associated-security-identifiers-with-powershell.md)</p></td>
|
||||
<td align="left"><p>Describes how to take an array of account names and to convert each of them to the corresponding SID in standard and hexadecimal formats.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>[How to Configure the Client to Receive Package and Connection Groups Updates From the Publishing Server](appv-configure-the-client-to-receive-updates-from-the-publishing-server.md)
|
||||
</p></td>
|
||||
<td align="left"><p>Describes how to use Windows PowerShell to configure a client after you deploy the App-V management and publishing servers, and add the required packages and connection groups.</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
**Important**
|
||||
Make sure that any script you execute with your App-V packages matches the execution policy that you have configured for PowerShell.
|
||||
Make sure that any script you execute with your App-V packages matches the execution policy that you have configured for Windows PowerShell.
|
||||
|
||||
|
||||
|
||||
## PowerShell Error Handling
|
||||
## Windows PowerShell Error Handling
|
||||
|
||||
|
||||
Use the following table for information about App-V PowerShell error handling.
|
||||
@ -127,12 +133,3 @@ Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-micros
|
||||
|
||||
|
||||
[Operations for App-V](appv-operations.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# Administering App-V Virtual Applications by Using the Management Console
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
Use the Microsoft Application Virtualization (App-V) management server to manage packages, connection groups, and package access in your environment. The server publishes application icons, shortcuts, and file type associations to authorized computers that run the App-V client. One or more management servers typically share a common data store for configuration and package information.
|
||||
|
||||
|
||||
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# How to Allow Only Administrators to Enable Connection Groups
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
You can configure the App-V client so that only administrators (not end users) can enable or disable connection groups. In earlier versions of App-V, you could not prevent end users from performing these tasks.
|
||||
|
||||
@ -36,7 +37,7 @@ Use one of the following methods to allow only administrators to enable or disab
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Group Policy setting</p></td>
|
||||
<td align="left"><p>Enable the “Require publish as administrator” Group Policy setting, which is located in the following Group Policy Object node:</p>
|
||||
<p><strong>Computer Configuration > Policies > Administrative Templates > System > App-V > Publishing</strong></p></td>
|
||||
<p><strong>Computer Configuration > Administrative Templates > System > App-V > Publishing</strong></p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>PowerShell cmdlet</p></td>
|
||||
|
||||
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# Application Publishing and Client Interaction
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
This article provides technical information about common App-V client operations and their integration with the local operating system.
|
||||
|
||||
|
||||
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# How to Apply the Deployment Configuration File by Using PowerShell
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
The dynamic deployment configuration file is applied when a package is added or set to a computer running the App-V client before the package has been published. The file configures the default settings for package for all users on the computer running the App-V client. This section describes the steps used to use a deployment configuration file. The procedure is based on the following example and assumes the following package and configuration files exist on a computer:
|
||||
|
||||
|
||||
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# How to Apply the User Configuration File by Using PowerShell
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
The dynamic user configuration file is applied when a package is published to a specific user and determines how the package will run.
|
||||
|
||||
|
||||
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# App-V Capacity Planning
|
||||
|
||||
Applies to: Windows Server 2016, Windows Server 2012 R2, Windows Server 2012, and Windows Server 2008 R2
|
||||
|
||||
The following recommendations can be used as a baseline to help determine capacity planning information that is appropriate to your organization’s App-V infrastructure.
|
||||
|
||||
|
||||
@ -10,9 +10,11 @@ ms.prod: w10
|
||||
|
||||
# About Client Configuration Settings
|
||||
|
||||
The Microsoft Application Virtualization (App-V) client stores its configuration in the registry. You can gather some useful information about the client if you understand the format of data in the registry. You can also configure many client actions by changing registry entries. This topic lists the App-V Client configuration settings and explains their uses. You can use PowerShell to modify the client configuration settings. For more information about using PowerShell and App-V see [Administering App-V by Using PowerShell](appv-administering-appv-with-powershell.md).
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
The Microsoft Application Virtualization (App-V) client stores its configuration in the registry. You can gather some useful information about the client if you understand the format of data in the registry. You can also configure many client actions by changing registry entries. This topic lists the App-V Client configuration settings and explains their uses. You can use Windows PowerShell to modify the client configuration settings. For more information about using Windows PowerShell and App-V see [Administering App-V by Using Windows PowerShell](appv-administering-appv-with-powershell.md).
|
||||
|
||||
You can use Group Policy to configure App-V client settings by using the Group Policy Management Console under **Computer Configuration** > **Administrative Templates** > **System** > **App-V**.
|
||||
|
||||
## App-V Client Configuration Settings: Windows PowerShell
|
||||
|
||||
@ -58,49 +60,49 @@ The following table provides information about App-V client configuration settin
|
||||
| **HidePublishingRefreshUI**<br>1 (Enabled), 0 (Disabled) | Hides the publishing refresh progress bar. | Sync-AppvPublishingServer | |
|
||||
| **ProcessesUsingVirtualComponents**<br>String | Specifies a list of process paths (that may contain wildcards), which are candidates for using dynamic virtualization (supported shell extensions, browser helper objects, and ActiveX controls). Only processes whose full path matches one of these items can use dynamic virtualization. | Set-AppvClientConfiguration,<br>Set-AppvPublishingServer | Empty string. |
|
||||
|
||||
## App-V Client Configuration Settings: Setup Flags and Registry Keys
|
||||
## App-V Client Configuration Settings: Registry Keys
|
||||
|
||||
The following table provides information about App-V client configuration settings that can be configured through setup flags or in the registry:
|
||||
The following table provides information about App-V client configuration settings that can be configured through the registry:
|
||||
|
||||
| **Setting name**<br>Type | Setup Flag | Registry Key Value | Disabled Policy State Keys and Values |
|
||||
|--------------------------------------------------------------------------------|---------------------------|-------------------------------------------------------------------------|---------------------------------------------------|
|
||||
| **PackageInstallationRoot**<br>String | PACKAGEINSTALLATIONROOT | Streaming\\PackageInstallationRoot | Policy value not written (same as Not Configured) |
|
||||
| **PackageSourceRoot**<br>String | PACKAGESOURCEROOT | Streaming\\PackageSourceRoot | Policy value not written (same as Not Configured) |
|
||||
| **AllowHighCostLaunch**<br>True (enabled); False (Disabled state) | Not available. | Streaming\\AllowHighCostLaunch | 0 |
|
||||
| **ReestablishmentRetries**<br>Integer (0-99) | Not available. | Streaming\\ReestablishmentRetries | Policy value not written (same as Not Configured) |
|
||||
| **ReestablishmentInterval**<br>Integer (0-3600) | Not available. | Streaming\\ReestablishmentInterval | Policy value not written (same as Not Configured) |
|
||||
| **LocationProvider**<br>String | Not available. | Streaming\\LocationProvider | Policy value not written (same as Not Configured) |
|
||||
| **CertFilterForClientSsl**<br>String | Not available. | Streaming\\CertFilterForClientSsl | Policy value not written (same as Not Configured) |
|
||||
| **VerifyCertificateRevocationList**<br>True(enabled); False(Disabled state) | Not available. | Streaming\\VerifyCertificateRevocationList | 0 |
|
||||
| **SharedContentStoreMode**<br>True(enabled); False(Disabled state) | SHAREDCONTENTSTOREMODE | Streaming\\SharedContentStoreMode | 0 |
|
||||
| **Name**<br>String | PUBLISHINGSERVERNAME | Publishing\\Servers{serverId}\\FriendlyName | Policy value not written (same as Not Configured) |
|
||||
| **URL**<br>String | PUBLISHINGSERVERURL | Publishing\\Servers{serverId}\\URL | Policy value not written (same as Not Configured) |
|
||||
| **GlobalRefreshEnabled**<br>True(enabled); False(Disabled state) | GLOBALREFRESHENABLED | Publishing\\Servers{serverId}\\GlobalEnabled | False |
|
||||
| **GlobalRefreshOnLogon**<br>True(enabled); False(Disabled state) | GLOBALREFRESHONLOGON | Publishing\\Servers{serverId}\\GlobalLogonRefresh | False |
|
||||
| **GlobalRefreshInterval**<br>Integer (0-744) | GLOBALREFRESHINTERVAL | Publishing\\Servers{serverId}\\GlobalPeriodicRefreshInterval | 0 |
|
||||
| **GlobalRefreshIntervalUnit** <br>0 for hour, 1 for day | GLOBALREFRESHINTERVALUNI | Publishing\\Servers{serverId}\\GlobalPeriodicRefreshIntervalUnit | 1 |
|
||||
| **UserRefreshEnabled**<br>True(enabled); False(Disabled state) | USERREFRESHENABLED | Publishing\\Servers{serverId}\\UserEnabled | False |
|
||||
| **UserRefreshOnLogon**<br>True(enabled); False(Disabled state) | USERREFRESHONLOGON | Publishing\\Servers{serverId}\\UserLogonRefresh | False |
|
||||
| **UserRefreshInterval**<br>Word count (with spaces): 85Integer (0-744 Hours) | USERREFRESHINTERVAL | Publishing\\Servers{serverId}\\UserPeriodicRefreshInterval | 0 |
|
||||
| **UserRefreshIntervalUnit**<br>0 for hour, 1 for day | USERREFRESHINTERVALUNIT | Publishing\\Servers{serverId}\\UserPeriodicRefreshIntervalUnit | 1 |
|
||||
| **MigrationMode**<br>True(enabled state); False (disabled state) | MIGRATIONMODE | Coexistence\\MigrationMode | |
|
||||
| **EnablePackageScripts**<br>True(enabled); False(Disabled state) | ENABLEPACKAGESCRIPTS | \\Scripting\\EnablePackageScripts | |
|
||||
| **RoamingFileExclusions**<br>String | ROAMINGFILEEXCLUSIONS | | |
|
||||
| **RoamingRegistryExclusions**<br>String | ROAMINGREGISTRYEXCLUSIONS | Integration\\RoamingReglstryExclusions | Policy value not written (same as Not Configured) |
|
||||
| **IntegrationRootUser**<br>String | Not available. | Integration\\IntegrationRootUser | Policy value not written (same as Not Configured) |
|
||||
| **IntegrationRootGlobal**<br>String | Not available. | Integration\\IntegrationRootGlobal | Policy value not written (same as Not Configured) |
|
||||
| **VirtualizableExtensions**<br>String | Not available. | Integration\\VirtualizableExtensions | Policy value not written |
|
||||
| **ReportingEnabled**<br>True (enabled); False (Disabled state) | Not available. | Reporting\\EnableReporting | False |
|
||||
| **ReportingServerURL**<br>String | Not available. | Reporting\\ReportingServer | Policy value not written (same as Not Configured) |
|
||||
| **ReportingDataCacheLimit**<br>Integer \[0-1024\] | Not available. | Reporting\\DataCacheLimit | Policy value not written (same as Not Configured) |
|
||||
| **ReportingDataBlockSize**<br>Integer \[1024 - Unlimited\] | Not available. | Reporting\\DataBlockSize | Policy value not written (same as Not Configured) |
|
||||
| **ReportingStartTime**<br>Integer (0 – 23) | Not available. | Reporting\\ StartTime | Policy value not written (same as Not Configured) |
|
||||
| **ReportingInterval**<br>Integer | Not available. | Reporting\\RetryInterval | Policy value not written (same as Not Configured) |
|
||||
| **ReportingRandomDelay**<br>Integer \[0 - ReportingRandomDelay\] | Not available. | Reporting\\RandomDelay | Policy value not written (same as Not Configured) |
|
||||
| **EnableDynamicVirtualization<br>**1 (Enabled), 0 (Disabled) | Not available. | HKEY\_LOCAL\_MACHINE\\Software\\Microsoft\\AppV\\Client\\Virtualization | |
|
||||
| **EnablePublishingRefreshUI**<br>1 (Enabled), 0 (Disabled) | Not available. | HKEY\_LOCAL\_MACHINE\\Software\\Microsoft\\AppV\\Client\\Publishing | |
|
||||
| **HidePublishingRefreshUI**<br>1 (Enabled), 0 (Disabled) | Not available. | | |
|
||||
| **ProcessesUsingVirtualComponents**<br>String | Not available. | Virtualization\\ProcessesUsingVirtualComponents | Empty string. |
|
||||
| **Setting name**<br>Type | Registry Key Value | Disabled Policy State Keys and Values |
|
||||
|---------------------------|---------------------|---------------------------------------|
|
||||
| **PackageInstallationRoot**<br>String | Streaming\\PackageInstallationRoot | Policy value not written (same as Not Configured) |
|
||||
| **PackageSourceRoot**<br>String | Streaming\\PackageSourceRoot | Policy value not written (same as Not Configured) |
|
||||
| **AllowHighCostLaunch**<br>True (enabled); False (Disabled state) | Streaming\\AllowHighCostLaunch | 0 |
|
||||
| **ReestablishmentRetries**<br>Integer (0-99) | Streaming\\ReestablishmentRetries | Policy value not written (same as Not Configured) |
|
||||
| **ReestablishmentInterval**<br>Integer (0-3600) | Streaming\\ReestablishmentInterval | Policy value not written (same as Not Configured) |
|
||||
| **LocationProvider**<br>String | Streaming\\LocationProvider | Policy value not written (same as Not Configured) |
|
||||
| **CertFilterForClientSsl**<br>String | Streaming\\CertFilterForClientSsl | Policy value not written (same as Not Configured) |
|
||||
| **VerifyCertificateRevocationList**<br>True(enabled); False(Disabled state) | Streaming\\VerifyCertificateRevocationList | 0 |
|
||||
| **SharedContentStoreMode**<br>True(enabled); False(Disabled state) | Streaming\\SharedContentStoreMode | 0 |
|
||||
| **Name**<br>String | Publishing\\Servers{serverId}\\FriendlyName | Policy value not written (same as Not Configured) |
|
||||
| **URL**<br>String | Publishing\\Servers{serverId}\\URL | Policy value not written (same as Not Configured) |
|
||||
| **GlobalRefreshEnabled**<br>True(enabled); False(Disabled state) | Publishing\\Servers{serverId}\\GlobalEnabled | False |
|
||||
| **GlobalRefreshOnLogon**<br>True(enabled); False(Disabled state) | Publishing\\Servers{serverId}\\GlobalLogonRefresh | False |
|
||||
| **GlobalRefreshInterval**<br>Integer (0-744) | Publishing\\Servers{serverId}\\GlobalPeriodicRefreshInterval | 0 |
|
||||
| **GlobalRefreshIntervalUnit** <br>0 for hour, 1 for day | Publishing\\Servers{serverId}\\GlobalPeriodicRefreshIntervalUnit | 1 |
|
||||
| **UserRefreshEnabled**<br>True(enabled); False(Disabled state) | Publishing\\Servers{serverId}\\UserEnabled | False |
|
||||
| **UserRefreshOnLogon**<br>True(enabled); False(Disabled state) | Publishing\\Servers{serverId}\\UserLogonRefresh | False |
|
||||
| **UserRefreshInterval**<br>Word count (with spaces): 85Integer (0-744 Hours) | Publishing\\Servers{serverId}\\UserPeriodicRefreshInterval | 0 |
|
||||
| **UserRefreshIntervalUnit**<br>0 for hour, 1 for day | Publishing\\Servers{serverId}\\UserPeriodicRefreshIntervalUnit | 1 |
|
||||
| **MigrationMode**<br>True(enabled state); False (disabled state) | Coexistence\\MigrationMode | |
|
||||
| **EnablePackageScripts**<br>True(enabled); False(Disabled state) | \\Scripting\\EnablePackageScripts | |
|
||||
| **RoamingFileExclusions**<br>String | | |
|
||||
| **RoamingRegistryExclusions**<br>String | Integration\\RoamingReglstryExclusions | Policy value not written (same as Not Configured) |
|
||||
| **IntegrationRootUser**<br>String | Integration\\IntegrationRootUser | Policy value not written (same as Not Configured) |
|
||||
| **IntegrationRootGlobal**<br>String | Integration\\IntegrationRootGlobal | Policy value not written (same as Not Configured) |
|
||||
| **VirtualizableExtensions**<br>String | Integration\\VirtualizableExtensions | Policy value not written |
|
||||
| **ReportingEnabled**<br>True (enabled); False (Disabled state) | Reporting\\EnableReporting | False |
|
||||
| **ReportingServerURL**<br>String | Reporting\\ReportingServer | Policy value not written (same as Not Configured) |
|
||||
| **ReportingDataCacheLimit**<br>Integer \[0-1024\] | Reporting\\DataCacheLimit | Policy value not written (same as Not Configured) |
|
||||
| **ReportingDataBlockSize**<br>Integer \[1024 - Unlimited\] | Reporting\\DataBlockSize | Policy value not written (same as Not Configured) |
|
||||
| **ReportingStartTime**<br>Integer (0 – 23) | Reporting\\ StartTime | Policy value not written (same as Not Configured) |
|
||||
| **ReportingInterval**<br>Integer | Reporting\\RetryInterval | Policy value not written (same as Not Configured) |
|
||||
| **ReportingRandomDelay**<br>Integer \[0 - ReportingRandomDelay\] | Reporting\\RandomDelay | Policy value not written (same as Not Configured) |
|
||||
| **EnableDynamicVirtualization<br>**1 (Enabled), 0 (Disabled) | HKEY\_LOCAL\_MACHINE\\Software\\Microsoft\\AppV\\Client\\Virtualization | |
|
||||
| **EnablePublishingRefreshUI**<br>1 (Enabled), 0 (Disabled) | HKEY\_LOCAL\_MACHINE\\Software\\Microsoft\\AppV\\Client\\Publishing | |
|
||||
| **HidePublishingRefreshUI**<br>1 (Enabled), 0 (Disabled) | | |
|
||||
| **ProcessesUsingVirtualComponents**<br>String | Virtualization\\ProcessesUsingVirtualComponents | Empty string. |
|
||||
|
||||
## Have a suggestion for App-V?
|
||||
|
||||
@ -110,4 +112,3 @@ Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-micros
|
||||
|
||||
[Deploying the App-V Sequencer and Configuring the Client](appv-deploying-the-appv-sequencer-and-client.md)
|
||||
|
||||
[How to Modify App-V Client Configuration Using the ADMX Template and Group Policy](appv-modify-client-configuration-with-the-admx-template-and-group-policy.md)
|
||||
|
||||
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# How to Configure Access to Packages by Using the Management Console
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
Before you deploy an App-V virtualized package, you must configure the Active Directory Domain Services (AD DS) security groups that will be allowed to access and run the applications. The security groups may contain computers or users. Entitling a package to a computer group publishes the package globally to all computers in the group.
|
||||
|
||||
|
||||
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# How to Make a Connection Group Ignore the Package Version
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
Microsoft Application Virtualization (App-V) lets you configure a connection group to use any version of a package, which simplifies package upgrades and reduces the number of connection groups you need to create.
|
||||
|
||||
|
||||
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# How to Configure the Client to Receive Package and Connection Groups Updates From the Publishing Server
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
Deploying packages and connection groups using the App-V publishing server is helpful because it offers single-point management and high scalability.
|
||||
|
||||
|
||||
@ -10,6 +10,8 @@ ms.prod: w10
|
||||
|
||||
# How to Connect to the Management Console
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
Use the following procedure to connect to the App-V Management Console.
|
||||
|
||||
**To connect to the App-V Management Console**
|
||||
|
||||
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# About the Connection Group File
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
**In this topic:**
|
||||
|
||||
|
||||
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# About the Connection Group Virtual Environment
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
**In this topic:**
|
||||
|
||||
|
||||
@ -11,6 +11,8 @@ ms.prod: w10
|
||||
|
||||
# How to Convert a Package Created in a Previous Version of App-V
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
You can use the package converter utility to upgrade virtual application packages that have been created with previous versions of App-V.
|
||||
|
||||
> [!NOTE]
|
||||
|
||||
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# How to Create a Connection Group with User-Published and Globally Published Packages
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
You can create user-entitled connection groups that contain both user-published and globally published packages, using either of the following methods:
|
||||
|
||||
|
||||
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# How to Create a Connection Group
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
Use these steps to create a connection group by using the App-V Management Console. To use PowerShell to create connection groups, see [How to Manage Connection Groups on a Stand-alone Computer by Using PowerShell](appv-manage-connection-groups-on-a-stand-alone-computer-with-powershell.md).
|
||||
|
||||
|
||||
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# How to Create a Custom Configuration File by Using the App-V Management Console
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
You can use a dynamic configuration to customize an App-V package for a specific user. However, you must first create the dynamic user configuration (.xml) file or the dynamic deployment configuration file before you can use the files. Creation of the file is an advanced manual operation. For general information about dynamic user configuration files, see, [About App-V Dynamic Configuration](appv-dynamic-configuration.md).
|
||||
|
||||
|
||||
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# How to Create a Package Accelerator by Using PowerShell
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
App-V package accelerators automatically sequence large, complex applications. Additionally, when you apply an App-V package accelerator, you are not always required to manually install an application to create the virtualized package.
|
||||
|
||||
@ -43,7 +44,7 @@ App-V package accelerators automatically sequence large, complex applications. A
|
||||
## Related topics
|
||||
|
||||
|
||||
[Administering App-V by Using PowerShell](appv-administering-appv-with-powershell.md)
|
||||
[Administering App-V by Using Windows PowerShell](appv-administering-appv-with-powershell.md)
|
||||
|
||||
|
||||
|
||||
|
||||
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# How to Create a Package Accelerator
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
App-V package accelerators automatically generate new virtual application packages.
|
||||
|
||||
|
||||
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# How to Create a Virtual Application Package Using an App-V Package Accelerator
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
**Important**
|
||||
The App-V Sequencer does not grant any license rights to the software application that you use to create the Package Accelerator. You must abide by all end user license terms for the application that you use. It is your responsibility to make sure that the software application’s license terms allow you to create a Package Accelerator with the App-V Sequencer.
|
||||
|
||||
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# How to Create and Use a Project Template
|
||||
|
||||
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.
|
||||
|
||||
|
||||
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# Creating and Managing App-V Virtualized Applications
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
After you have properly deployed the Microsoft Application Virtualization (App-V) sequencer, you can use it to monitor and record the installation and setup process for an application to be run as a virtualized application.
|
||||
|
||||
|
||||
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# How to Customize Virtual Applications Extensions for a Specific AD Group by Using the Management Console
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
Use the following procedure to customize the virtual application extensions for an Active Directory (AD) group.
|
||||
|
||||
|
||||
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# How to Delete a Connection Group
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
Use the following procedure to delete an existing App-V connection group.
|
||||
|
||||
|
||||
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# How to Delete a Package in the Management Console
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
Use the following procedure to delete an App-V package.
|
||||
|
||||
|
||||
@ -11,6 +11,8 @@ ms.prod: w10
|
||||
|
||||
# How to Deploy the App-V Databases by Using SQL Scripts
|
||||
|
||||
Applies to: Windows Server 2016, Windows Server 2012 R2, Windows Server 2012, and Windows Server 2008 R2
|
||||
|
||||
Use the following instructions to use SQL scripts, rather than the Windows Installer, to:
|
||||
|
||||
- Install the App-V databases
|
||||
|
||||
@ -10,6 +10,8 @@ ms.prod: w10
|
||||
|
||||
# How to deploy App-V packages using electronic software distribution
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
You can use an electronic software distribution (ESD) system to deploy App-V virtual applications to App-V clients.
|
||||
|
||||
For component requirements and options for using an ESD to deploy App-V packages, see [Planning to Deploy App-V with an Electronic Software Distribution System](appv-planning-to-deploy-appv-with-electronic-software-distribution-solutions.md).
|
||||
|
||||
@ -11,6 +11,8 @@ ms.prod: w10
|
||||
|
||||
# How to Deploy the App-V Server Using a Script
|
||||
|
||||
Applies to: Windows Server 2016, Windows Server 2012 R2, Windows Server 2012, and Windows Server 2008 R2
|
||||
|
||||
In order to complete the **appv\_server\_setup.exe** Server setup successfully using the command line, you must specify and combine multiple parameters.
|
||||
|
||||
**To Install the App-V server using a script**
|
||||
|
||||
@ -10,6 +10,8 @@ ms.prod: w10
|
||||
|
||||
# How to Deploy the App-V Server (new installation)
|
||||
|
||||
Applies to: Windows Server 2016, Windows Server 2012 R2, Windows Server 2012, and Windows Server 2008 R2
|
||||
|
||||
>**Important**<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.
|
||||
|
||||
**Before you start:**
|
||||
|
||||
@ -10,6 +10,8 @@ ms.prod: w10
|
||||
|
||||
# Deploying App-V for Windows 10
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
App-V supports a number of different deployment options. Review this topic for information about the tasks that you must complete at different stages in your deployment.
|
||||
|
||||
## App-V Deployment Information
|
||||
|
||||
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# Deploying Microsoft Office 2010 by Using App-V
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
You can create Office 2010 packages for Microsoft Application Virtualization (App-V) using one of the following methods:
|
||||
|
||||
|
||||
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# Deploying Microsoft Office 2013 by Using App-V
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
Use the information in this article to use Microsoft Application Virtualization (App-V), or later versions, to deliver Microsoft Office 2013 as a virtualized application to computers in your organization. For information about using App-V to deliver Office 2010, see [Deploying Microsoft Office 2010 by Using App-V](appv-deploying-microsoft-office-2010-wth-appv.md). To successfully deploy Office 2013 with App-V, you need to be familiar with Office 2013 and App-V.
|
||||
|
||||
|
||||
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# Deploying App-V Packages by Using Electronic Software Distribution (ESD)
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
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).
|
||||
|
||||
|
||||
@ -11,6 +11,8 @@ ms.prod: w10
|
||||
|
||||
# Deploying the App-V Sequencer and Configuring the Client
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
The App-V Sequencer and client enable administrators to virtualize and run virtualized applications.
|
||||
|
||||
## Enable the client
|
||||
@ -18,29 +20,25 @@ The App-V Sequencer and client enable administrators to virtualize and run virtu
|
||||
The App-V client is the component that runs a virtualized application on a target computer. The client enables users to interact with icons and to double-click file types, so that they can start a virtualized application. The client can also obtain the virtual application content from the management server.
|
||||
|
||||
> [!NOTE]
|
||||
> In Windows 10, version 1607, App-V is included with the OS. You only need to enable it.
|
||||
> In Windows 10, version 1607, App-V is included with the operating system. You only need to enable it.
|
||||
|
||||
[Enable the App-V desktop client](appv-enable-the-app-v-desktop-client.md)
|
||||
|
||||
## Client Configuration Settings
|
||||
|
||||
The App-V client stores its configuration in the registry. You can gather some useful information about the client if you understand the format of data in the registry. You can also configure many client actions by changing registry entries.
|
||||
|
||||
[About Client Configuration Settings](appv-client-configuration-settings.md)
|
||||
The App-V client stores its configuration in the registry. You can gather some useful information about the client if you understand the format of data in the registry. For information about client settings that you can configure through Windows PowerShell or through the registry, see [About Client Configuration Settings](appv-client-configuration-settings.md).
|
||||
|
||||
## Configure the client by using the ADMX template and Group Policy
|
||||
|
||||
You can use Group Policy to configure the client settings for the App-V client and the Remote Desktop Services client.
|
||||
|
||||
Perform the following steps on the computer that you will use to manage Group Policy. This is typically the Domain Controller.
|
||||
To manage the ADMX template, perform the following steps on the computer that you will use to manage Group Policy. This is typically the Domain Controller.
|
||||
|
||||
1. Save the **.admx** file to the following directory: **Windows \\ PolicyDefinitions**
|
||||
|
||||
2. Save the **.adml** file to the following directory: **Windows \\ PolicyDefinitions \\ <Language Directory>**
|
||||
|
||||
After you have completed the preceding steps, you can manage the App-V client configuration settings with the **Group Policy Management** console.
|
||||
|
||||
[How to Modify App-V Client Configuration Using the ADMX Template and Group Policy](appv-modify-client-configuration-with-the-admx-template-and-group-policy.md)
|
||||
After you have completed the preceding steps, you can use Group Policy to configure the client settings by using the Group Policy Management Console under **Computer Configuration** > **Administrative Templates** > **System** > **App-V**.
|
||||
|
||||
## Understanding Shared Content Store mode for App-V clients
|
||||
|
||||
|
||||
@ -10,7 +10,7 @@ ms.prod: w10
|
||||
|
||||
# Deploying the App-V server
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
Applies to: Windows Server 2016, Windows Server 2012 R2, Windows Server 2012, and Windows Server 2008 R2
|
||||
|
||||
>**Note** If you plan to use the App-V server components in your deployment, note that they reference App-V 5.x. This is because the App-V server components have not changed in App-V for Windows 10.
|
||||
|
||||
|
||||
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# App-V Deployment Checklist
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
This checklist can be used to help you during an App-V deployment.
|
||||
|
||||
|
||||
@ -11,6 +11,8 @@ ms.prod: w10
|
||||
|
||||
# About App-V Dynamic Configuration
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
You can use the dynamic configuration to customize an App-V package for a user. Use the following information to create or edit an existing dynamic configuration file.
|
||||
|
||||
When you edit the dynamic configuration file it customizes how an App-V package will run for a user or group. This helps to provide a more convenient method for package customization by removing the need to re-sequence packages using the desired settings, and provides a way to keep package content and custom settings independent.
|
||||
|
||||
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# How to Enable Only Administrators to Publish Packages by Using an ESD
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
Starting in App-V 5.0 SP3, you can configure the App-V client so that only administrators (not end users) can publish or unpublish packages. In earlier versions of App-V, you could not prevent end users from performing these tasks.
|
||||
|
||||
@ -18,7 +19,7 @@ Starting in App-V 5.0 SP3, you can configure the App-V client so that only admin
|
||||
|
||||
1. Navigate to the following Group Policy Object node:
|
||||
|
||||
**Computer Configuration > Policies > Administrative Templates > System > App-V > Publishing**.
|
||||
**Computer Configuration > Administrative Templates > System > App-V > Publishing**.
|
||||
|
||||
2. Enable the **Require publish as administrator** Group Policy setting.
|
||||
|
||||
|
||||
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# How to Enable Reporting on the App-V Client by Using PowerShell
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
Use the following procedure to configure the App-V for reporting.
|
||||
|
||||
@ -84,4 +85,4 @@ Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-micros
|
||||
## Related topics
|
||||
|
||||
|
||||
[Administering App-V by Using PowerShell](appv-administering-appv-with-powershell.md)
|
||||
[Administering App-V by Using Windows PowerShell](appv-administering-appv-with-powershell.md)
|
||||
|
||||
@ -10,6 +10,8 @@ ms.prod: w10
|
||||
|
||||
# Enable the App-V in-box client
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
The App-V client is the component that runs virtualized applications on user devices. The client enables users to interact with icons and file names to start virtualized applications. The client can also get virtual application content from the management server.
|
||||
|
||||
With Windows 10, version 1607, the App-V client is installed automatically. You need to enable the client to allow user devices to access and run virtual applications. You can enable the client with the Group Policy editor or with Windows PowerShell.
|
||||
@ -32,9 +34,18 @@ With Windows 10, version 1607, the App-V client is installed automatically. You
|
||||
|
||||
3. Restart the device.
|
||||
|
||||
4. To verify that the App-V client is enabled on the device, type `Get-AppvStatus` and press ENTER.
|
||||
4. To verify that the App-V client is enabled on the device, type `Get-AppvStatus` and press ENTER.
|
||||
|
||||
See [Using the client management console](appv-using-the-client-management-console.md) for information about configuring the App-V client.
|
||||
|
||||
For information about configuring the App-V client, see:
|
||||
|
||||
- [Deploying the App-V Sequencer and Configuring the Client](appv-deploying-the-appv-sequencer-and-client.md)
|
||||
|
||||
- [How to Modify Client Configuration by Using Windows PowerShell](appv-modify-client-configuration-with-powershell.md)
|
||||
|
||||
- [Using the client management console](appv-using-the-client-management-console.md)
|
||||
|
||||
- [How to Configure the Client to Receive Package and Connection Groups Updates From the Publishing Server](appv-configure-the-client-to-receive-updates-from-the-publishing-server.md)
|
||||
|
||||
## Have a suggestion for App-V?
|
||||
|
||||
|
||||
@ -11,6 +11,8 @@ ms.prod: w10
|
||||
|
||||
# Evaluating App-V
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
Before you deploy App-V into a production environment, you should evaluate it in a lab environment. You can use the information in this topic to set up App-V in a lab environment for evaluation purposes only.
|
||||
|
||||
## Configure lab computers for App-V Evaluation
|
||||
|
||||
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# Application Virtualization (App-V) for Windows 10 overview
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
The topics in this section provide information and step-by-step procedures to help you administer App-V and its components. This information will be valuable for system administrators who manage large installations with many servers and clients and for support personnel who interact directly with the computers or the end users.
|
||||
|
||||
@ -46,7 +47,7 @@ The topics in this section provide information and step-by-step procedures to he
|
||||
- [Using the App-V Client Management Console](appv-using-the-client-management-console.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 PowerShell](appv-administering-appv-with-powershell.md)
|
||||
- [Administering App-V by Using Windows PowerShell](appv-administering-appv-with-powershell.md)
|
||||
|
||||
[Troubleshooting App-V](appv-troubleshooting.md)
|
||||
|
||||
|
||||
@ -11,6 +11,8 @@ ms.prod: w10
|
||||
|
||||
# Getting Started with App-V for Windows 10
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
Microsoft Application Virtualization (App-V) for Windows 10 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.
|
||||
|
||||
With the release of Windows 10, version 1607, App-V is included with the [Windows 10 for Enterprise edition](https://www.microsoft.com/en-us/WindowsForBusiness/windows-for-enterprise). If you are new to Windows 10 and App-V, you’ll need to download, activate, and install server- and client-side components to start delivering virtual applications to users. For information about what you need to know before getting started with App-V, see the [Application Virtualization (App-V) overview](appv-for-windows.md).
|
||||
|
||||
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# High Level Architecture for App-V
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
Use the following information to help you simplify you Microsoft Application Virtualization (App-V) deployment.
|
||||
|
||||
|
||||
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# How to Install the App-V Databases and Convert the Associated Security Identifiers by Using PowerShell
|
||||
|
||||
Applies to: Windows Server 2016, Windows Server 2012 R2, Windows Server 2012, and Windows Server 2008 R2
|
||||
|
||||
Use the following PowerShell procedure to convert any number of Active Directory Domain Services (AD DS) user or machine accounts into formatted Security Identifiers (SIDs) both in the standard format and in the hexadecimal format used by Microsoft SQL Server when running SQL scripts.
|
||||
|
||||
@ -378,7 +379,7 @@ Before attempting this procedure, you should read and understand the information
|
||||
## Related topics
|
||||
|
||||
|
||||
[Administering App-V by Using PowerShell](appv-administering-appv-with-powershell.md)
|
||||
[Administering App-V by Using Windows PowerShell](appv-administering-appv-with-powershell.md)
|
||||
|
||||
|
||||
|
||||
|
||||
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# How to Install the Management and Reporting Databases on Separate Computers from the Management and Reporting Services
|
||||
|
||||
Applies to: Windows Server 2016, Windows Server 2012 R2, Windows Server 2012, and Windows Server 2008 R2
|
||||
|
||||
Use the following procedure to install the database server and management server on different computers. The computer you plan to install the database server on must be running a supported version of Microsoft SQL or the installation will fail.
|
||||
|
||||
|
||||
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# How to install the Management Server on a Standalone Computer and Connect it to the Database
|
||||
|
||||
Applies to: Windows Server 2016, Windows Server 2012 R2, Windows Server 2012, and Windows Server 2008 R2
|
||||
|
||||
Use the following procedure to install the management server on a standalone computer and connect it to the database.
|
||||
|
||||
|
||||
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# How to Install the Publishing Server on a Remote Computer
|
||||
|
||||
Applies to: Windows Server 2016, Windows Server 2012 R2, Windows Server 2012, and Windows Server 2008 R2
|
||||
|
||||
Use the following procedure to install the publishing server on a separate computer. Before you perform the following procedure, ensure the database and management server are available.
|
||||
|
||||
|
||||
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# How to install the Reporting Server on a Standalone Computer and Connect it to the Database
|
||||
|
||||
Applies to: Windows Server 2016, Windows Server 2012 R2, Windows Server 2012, and Windows Server 2008 R2
|
||||
|
||||
Use the following procedure to install the reporting server on a standalone computer and connect it to the database.
|
||||
|
||||
|
||||
@ -11,6 +11,8 @@ ms.prod: w10
|
||||
|
||||
# Install the App-V Sequencer
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
Use the App-V Sequencer to convert Win32 applications into virtual packages for deployment to user devices. Those devices must be running the App-V client to allow users to interact with virtual applications.
|
||||
|
||||
The App-V Sequencer is included in the Windows 10 Assessment and Deployment Kit (Windows ADK).
|
||||
|
||||
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# How to Load the PowerShell Cmdlets and Get Cmdlet Help
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
What this topic covers:
|
||||
|
||||
|
||||
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# Maintaining App-V
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
After you have deployed App-V for Windows 10, you can use the following information to maintain the App-V infrastructure.
|
||||
|
||||
|
||||
@ -11,6 +11,8 @@ ms.prod: w10
|
||||
|
||||
# How to Manage App-V Packages Running on a Stand-Alone Computer by Using PowerShell
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
|
||||
The following sections explain how to perform various management tasks on a stand-alone client computer by using PowerShell:
|
||||
|
||||
@ -282,7 +284,7 @@ For more information about pending tasks, see [Upgrading an in-use App-V package
|
||||
|
||||
[Operations for App-V](appv-operations.md)
|
||||
|
||||
[Administering App-V by Using PowerShell](appv-administering-appv-with-powershell.md)
|
||||
[Administering App-V by Using Windows PowerShell](appv-administering-appv-with-powershell.md)
|
||||
|
||||
|
||||
|
||||
|
||||
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# How to Manage Connection Groups on a Stand-alone Computer by Using PowerShell
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
An App-V connection group allows you to run all the virtual applications as a defined set of packages in a single virtual environment. For example, you can virtualize an application and its plug-ins by using separate packages, but run them together in a single connection group.
|
||||
|
||||
@ -134,7 +135,7 @@ This topic explains the following procedures:
|
||||
|
||||
[Operations for App-V](appv-operations.md)
|
||||
|
||||
[Administering App-V by Using PowerShell](appv-administering-appv-with-powershell.md)
|
||||
[Administering App-V by Using Windows PowerShell](appv-administering-appv-with-powershell.md)
|
||||
|
||||
|
||||
|
||||
|
||||
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# Managing Connection Groups
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
Connection groups enable the applications within a package to interact with each other in the virtual environment, while remaining isolated from the rest of the system. By using connection groups, administrators can manage packages independently and can avoid having to add the same application multiple times to a client computer.
|
||||
|
||||
|
||||
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# How to Modify an Existing Virtual Application Package
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
This topic explains how to:
|
||||
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: How to Modify Client Configuration by Using PowerShell (Windows 10)
|
||||
description: How to Modify Client Configuration by Using PowerShell
|
||||
title: How to Modify Client Configuration by Using Windows PowerShell (Windows 10)
|
||||
description: How to Modify Client Configuration by Using Windows PowerShell
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
@ -9,16 +9,15 @@ ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# How to Modify Client Configuration by Using PowerShell
|
||||
# How to Modify Client Configuration by Using Windows PowerShell
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
Use the following procedure to configure the App-V client configuration.
|
||||
|
||||
**To modify App-V client configuration using PowerShell**
|
||||
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 PowerShell Cmdlets and Get Cmdlet Help](appv-load-the-powershell-cmdlets-and-get-cmdlet-help.md).
|
||||
|
||||
1. To configure the client settings using PowerShell, use the **Set-AppvClientConfiguration** cmdlet. For more information about installing PowerShell, and a list of cmdlets see, [How to Load the PowerShell Cmdlets and Get Cmdlet Help](appv-load-the-powershell-cmdlets-and-get-cmdlet-help.md).
|
||||
|
||||
2. To modify the client configuration, open a PowerShell Command prompt and run the following cmdlet **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`
|
||||
|
||||
@ -26,18 +25,11 @@ Use the following procedure to configure the App-V client configuration.
|
||||
|
||||
`Set-AppcClientConfiguration –Name1 MyConfig –Name2 “xyz”`
|
||||
|
||||
**Have a suggestion for App-V**? Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). **Got an App-V issue?** Use the [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 [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). 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)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -1,23 +1,4 @@
|
||||
---
|
||||
title: How to Modify App-V Client Configuration Using the ADMX Template and Group Policy (Windows 10)
|
||||
description: How to Modify App-V Client Configuration Using the ADMX Template and Group Policy
|
||||
author: MaggiePucciEvans
|
||||
ms.pagetype: mdop, appcompat, virtualization
|
||||
ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.prod: w10
|
||||
redirect_url: https://technet.microsoft.com/itpro/windows/manage/appv-deploying-the-appv-sequencer-and-client
|
||||
---
|
||||
|
||||
# How to Modify App-V client configuration using the ADMX template and Group Policy
|
||||
|
||||
You can use Group Policy to configure App-V client settings by using the Group Policy Management Console under **Computer Configuration** > **Policies** > **Administrative Templates** > **System** > **App-V**.
|
||||
|
||||
## Have a suggestion for App-V?
|
||||
|
||||
Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). **Got an App-V issue?** Use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/en-US/home?forum=mdopappv).
|
||||
|
||||
## Related topics
|
||||
|
||||
- [Deploying App-V](appv-deploying-appv.md)
|
||||
|
||||
- [About Client Configuration Settings](appv-client-configuration-settings.md)
|
||||
|
||||
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# How to move the App-V server to another computer
|
||||
|
||||
Applies to: Windows Server 2016, Windows Server 2012 R2, Windows Server 2012, and Windows Server 2008 R2
|
||||
|
||||
Use the following information to create a new management server console in your environment.
|
||||
|
||||
|
||||
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# Operations for App-V
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
This section of the Microsoft Application Virtualization (App-V) Administrator’s Guide includes information about the various types of App-V administration and operating tasks that are typically performed by an administrator. This section also includes step-by-step procedures to help you successfully perform those tasks.
|
||||
|
||||
@ -41,7 +42,7 @@ This section of the Microsoft Application Virtualization (App-V) Administrator
|
||||
|
||||
Provides instructions for migrating to App-V from a previous version.
|
||||
|
||||
- [Administering App-V by Using PowerShell](appv-administering-appv-with-powershell.md)
|
||||
- [Administering App-V by Using Windows PowerShell](appv-administering-appv-with-powershell.md)
|
||||
|
||||
Describes the set of Windows PowerShell cmdlets available for administrators performing various App-V server tasks.
|
||||
|
||||
|
||||
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# Performance Guidance for Application Virtualization
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
Learn how to configure App-V for optimal performance, optimize virtual app packages, and provide a better user experience with RDS and VDI.
|
||||
|
||||
|
||||
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# App-V Planning Checklist
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
This checklist can be used to help you plan for preparing your organization for an App-V deployment.
|
||||
|
||||
|
||||
@ -10,6 +10,8 @@ ms.prod: w10
|
||||
|
||||
# Planning to Use Folder Redirection with App-V
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
Microsoft Application Virtualization (App-V) supports the use of folder redirection, a feature that enables users and administrators to redirect the path of a folder to a new location.
|
||||
|
||||
This topic contains the following sections:
|
||||
|
||||
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# Planning for the App-V Server Deployment
|
||||
|
||||
Applies to: Windows Server 2016, Windows Server 2012 R2, Windows Server 2012, and Windows Server 2008 R2
|
||||
|
||||
The Microsoft Application Virtualization (App-V) server infrastructure consists of a set of specialized features that can be installed on one or more server computers, based on the requirements of the enterprise.
|
||||
|
||||
|
||||
@ -11,6 +11,8 @@ ms.prod: w10
|
||||
|
||||
# Planning for App-V
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
Use this information to plan how to deploy App-V so that it does not disrupt your users or the network.
|
||||
|
||||
## Planning information
|
||||
|
||||
@ -11,6 +11,8 @@ ms.prod: w10
|
||||
|
||||
# Planning for High Availability with App-V Server
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
Microsoft Application Virtualization (App-V) system configurations can take advantage of options that maintain a high level of available service.
|
||||
|
||||
Use the information in the following sections to help you understand the options to deploy App-V in a highly available configuration.
|
||||
|
||||
@ -10,6 +10,7 @@ ms.prod: w10
|
||||
|
||||
# Planning for the App-V Sequencer and Client Deployment
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
Before you can use App-V, you must install the App-V Sequencer, enable the App-V client, and optionally the App-V shared content store. The following sections address planning for these installations.
|
||||
|
||||
|
||||
@ -11,6 +11,8 @@ ms.prod: w10
|
||||
|
||||
# Planning for Using App-V with Office
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
Use the following information to plan how to deploy Office by using Microsoft Application Virtualization (App-V). This article includes:
|
||||
|
||||
- [App-V support for Language Packs](#bkmk-lang-pack)
|
||||
|
||||
@ -10,6 +10,8 @@ ms.prod: w10
|
||||
|
||||
# Planning to Deploy App-V with an electronic software distribution system
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
If you are using an electronic software distribution system to deploy App-V packages, review the following planning considerations. For information about using System Center Configuration Manager to deploy App-V, see [Introduction to Application Management in Configuration Manager](https://technet.microsoft.com/en-us/library/gg682125.aspx#BKMK_Appv).
|
||||
|
||||
Review the following component and architecture requirements options that apply when you use an ESD to deploy App-V packages:
|
||||
|
||||
@ -10,6 +10,8 @@ ms.prod: w10
|
||||
|
||||
# Preparing Your Environment for App-V
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
There are a number of different deployment configurations and prerequisites that you must consider before you create your deployment plan for Microsoft Application Virtualization (App-V). This section includes information that can help you gather the information that you must have to formulate a deployment plan that best meets your business requirements.
|
||||
|
||||
## App-V prerequisites
|
||||
|
||||
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# How to Publish a Connection Group
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
After you create a connection group, you must publish it to computers that run the App-V client.
|
||||
|
||||
|
||||
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# How to Publish a Package by Using the Management Console
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
Use the following procedure to publish an App-V package. Once you publish a package, computers that are running the App-V client can access and run the applications in that package.
|
||||
|
||||
@ -31,7 +32,7 @@ The ability to enable only administrators to publish or unpublish packages (desc
|
||||
|
||||
1. Navigate to the following Group Policy Object node:
|
||||
|
||||
**Computer Configuration > Policies > Administrative Templates > System > App-V > Publishing**.
|
||||
**Computer Configuration > Administrative Templates > System > App-V > Publishing**.
|
||||
|
||||
2. Enable the **Require publish as administrator** Group Policy setting.
|
||||
|
||||
|
||||
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# How to Register and Unregister a Publishing Server by Using the Management Console
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
You can register and unregister publishing servers that will synchronize with the App-V management server. You can also see the last attempt that the publishing server made to synchronize the information with the management server.
|
||||
|
||||
|
||||
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# About App-V Reporting
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
Application Virtualization (App-V) includes a built-in reporting feature that helps you collect information about computers running the App-V client as well as information about virtual application package usage. You can use this information to generate reports from a centralized database.
|
||||
|
||||
@ -134,9 +135,7 @@ To use App-V reporting you must enable and configure the App-V client. To config
|
||||
The following examples show how Windows PowerShell parameters can configure the reporting features of the App-V client.
|
||||
|
||||
**Note**
|
||||
The following configuration task can also be configured using Group Policy settings in the App-V ADMX template. The App-V settings are under **Computer Configuration > Administrative Templates > System > App-V**. For more information about using the ADMX template, see [How to Modify App-V Client Configuration Using the ADMX Template and Group Policy](appv-modify-client-configuration-with-the-admx-template-and-group-policy.md).
|
||||
|
||||
|
||||
The following configuration task can also be configured using Group Policy settings in the App-V ADMX template. The App-V settings are under **Computer Configuration > Administrative Templates > System > App-V**.
|
||||
|
||||
**To enable reporting and to initiate data collection on the computer running the App-V client**:
|
||||
|
||||
|
||||
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# Running a Locally Installed Application Inside a Virtual Environment with Virtualized Applications
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
You can run a locally installed application in a virtual environment, alongside applications that have been virtualized by using Microsoft Application Virtualization (App-V). You might want to do this if you:
|
||||
|
||||
|
||||
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# App-V Security Considerations
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
This topic contains a brief overview of the accounts and groups, log files, and other security-related considerations for Microsoft Application Virtualization (App-V).
|
||||
|
||||
|
||||
@ -11,6 +11,8 @@ ms.prod: w10
|
||||
|
||||
# How to Sequence a New Application with App-V
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
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).
|
||||
|
||||
**To review or do before you start sequencing**
|
||||
|
||||
@ -11,6 +11,8 @@ ms.prod: w10
|
||||
|
||||
# How to Sequence a Package by using Windows PowerShell
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
Use the following procedure to create a new App-V package using Windows PowerShell.
|
||||
|
||||
> [!NOTE]
|
||||
|
||||
@ -11,7 +11,7 @@ ms.prod: w10
|
||||
|
||||
# App-V Supported Configurations
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
Applies to: Windows 10, version 1607; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; and Windows Server 2008 R2
|
||||
|
||||
This topic specifies the requirements to install and run App-V in your Windows 10 environment.
|
||||
|
||||
@ -35,7 +35,7 @@ The App-V server does not support the following scenarios:
|
||||
|
||||
### Management server operating system requirements
|
||||
|
||||
The App-V Management server can be installed on a server that runs Windows Server 2008 R2 with SP1 or a later.
|
||||
The App-V Management server can be installed on a server that runs Windows Server 2008 R2 with SP1 or later.
|
||||
|
||||
> [!IMPORTANT]
|
||||
> Deployment of the Management server role to a computer with Remote Desktop Services enabled is not supported.
|
||||
@ -90,7 +90,7 @@ The following table lists the SQL Server versions that are supported for the App
|
||||
|
||||
### Publishing server operating system requirements
|
||||
|
||||
The App-V Publishing server can be installed on a server that runs Windows Server 2008 R2 with SP1 or a later.
|
||||
The App-V Publishing server can be installed on a server that runs Windows Server 2008 R2 with SP1 or later.
|
||||
|
||||
|
||||
### Publishing server hardware requirements
|
||||
@ -105,7 +105,7 @@ App-V adds no additional requirements beyond those of Windows Server.
|
||||
|
||||
### Reporting server operating system requirements
|
||||
|
||||
The App-V Reporting server can be installed on a server that runs Windows Server 2008 R2 with SP1 or a later.
|
||||
The App-V Reporting server can be installed on a server that runs Windows Server 2008 R2 with SP1 or later.
|
||||
|
||||
### Reporting server hardware requirements
|
||||
|
||||
|
||||
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# Technical Reference for App-V
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
This section provides reference information related to managing App-V.
|
||||
|
||||
@ -25,6 +26,14 @@ This section provides reference information related to managing App-V.
|
||||
|
||||
Describes how the following App-V client operations affect the local operating system: App-V files and data storage locations, package registry, package store behavior, roaming registry and data, client application lifecycle management, integration of App-V packages, dynamic configuration, side-by-side assemblies, and client logging.
|
||||
|
||||
- [Viewing App-V Server Publishing Metadata](appv-viewing-appv-server-publishing-metadata.md)
|
||||
|
||||
Tells how to view publishing metadata, which can help you resolve publishing-related issues.
|
||||
|
||||
- [Running a Locally Installed Application Inside a Virtual Environment with Virtualized Applications](appv-running-locally-installed-applications-inside-a-virtual-environment.md)
|
||||
|
||||
Describes reasons and methods for running a locally installed application in a virtual environment, alongside applications that have been virtualized by using Application Virtualization (App-V).
|
||||
|
||||
## Have a suggestion for App-V?
|
||||
|
||||
|
||||
|
||||
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# How to Transfer Access and Configurations to Another Version of a Package by Using the Management Console
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
Use the following procedure to transfer the access and default package configurations to another version of a package by using the management console.
|
||||
|
||||
|
||||
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# Troubleshooting App-V
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
Troubleshooting content is not included in the Administrator’s Guide for this product. Instead, you can find troubleshooting information for this product on the [TechNet Wiki](http://go.microsoft.com/fwlink/p/?LinkId=224905).
|
||||
|
||||
|
||||
@ -11,18 +11,30 @@ ms.prod: w10
|
||||
|
||||
# Using the App-V Client Management Console
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
This topic provides information about how you can configure and manage the Microsoft Application Virtualization (App-V) client.
|
||||
This topic provides information about about using the Application Virtualization (App-V) client management console to manage packages on the computer running the App-V client.
|
||||
|
||||
## Modify App-V client configuration
|
||||
## Obtain the client management console
|
||||
|
||||
The client management console is separate from the App-V client itself. You can download the client management console from the [Microsoft Download Center](https://www.microsoft.com/en-us/download/details.aspx?id=41186).
|
||||
|
||||
The App-V client has associated settings that can be configured to determine how the client will run in your environment. You can manage these settings on the computer that runs the client or by using PowerShell or Group Policy. For more information about how to modify the client using PowerShell or Group Policy configuration see, [How to Modify Client Configuration by Using PowerShell](appv-modify-client-configuration-with-powershell.md).
|
||||
> [!NOTE]
|
||||
To perform all of the actions available using the client management console, you must have administrative access on the computer running the App-V client.
|
||||
|
||||
## Options for managing the App-V client
|
||||
|
||||
The App-V client has associated settings that can be configured to determine how the client will run in your environment. You can manage these settings on the computer that runs the client, or you can use Windows PowerShell or Group Policy. For more information about configuring the client by using Windows PowerShell or Group Policy, see:
|
||||
|
||||
- [Deploying the App-V Sequencer and Configuring the Client](appv-deploying-the-appv-sequencer-and-client.md)
|
||||
|
||||
- [How to Modify Client Configuration by Using Windows PowerShell](appv-modify-client-configuration-with-powershell.md)
|
||||
|
||||
- [How to Configure the Client to Receive Package and Connection Groups Updates From the Publishing Server](appv-configure-the-client-to-receive-updates-from-the-publishing-server.md)
|
||||
|
||||
## <a href="" id="the-app-v-5-1-client-management-console-"></a>The App-V client management console
|
||||
|
||||
|
||||
You can obtain information about the App-V client or perform specific tasks by using the App-V client management console. Many of the tasks that you can perform in the client management console you can also perform by using PowerShell. The associated PowerShell cmdlets for each action are also displayed in the following table. For more information about how to use PowerShell, see [Administering App-V by Using PowerShell](appv-administering-appv-with-powershell.md).
|
||||
You can obtain information about the App-V client or perform specific tasks by using the App-V client management console. Many of the tasks that you can perform in the client management console you can also perform by using Windows PowerShell. The associated Windows PowerShell cmdlets for each action are also displayed in the following table. For more information about how to use Windows PowerShell, see [Administering App-V by Using Windows PowerShell](appv-administering-appv-with-powershell.md).
|
||||
|
||||
The client management console contains the following described main tabs.
|
||||
|
||||
@ -45,10 +57,10 @@ The client management console contains the following described main tabs.
|
||||
<li><p>Update – Use the <strong>Update</strong> tile to refresh a virtualized application or to receive a new virtualized package.</p>
|
||||
<p>The <strong>Last Refresh</strong> displays the current version of the virtualized package.</p></li>
|
||||
<li><p>Download all virtual applications – Use the <strong>Download</strong> tile to download all of the packages provisioned to the current user.</p>
|
||||
<p>(Associated PowerShell cmdlet: <strong>Mount-AppvClientPackage</strong>)</p>
|
||||
<p>(Associated Windows PowerShell cmdlet: <strong>Mount-AppvClientPackage</strong>)</p>
|
||||
<p></p></li>
|
||||
<li><p>Work Offline – Use this tile to disallow all automatic and manual virtual application updates.</p>
|
||||
<p>(Associated PowerShell cmdlet: <strong>Set-AppvPublishServer –UserRefreshEnabled –GlobalRefreshEnabled</strong>)</p></li>
|
||||
<p>(Associated Windows PowerShell cmdlet: <strong>Set-AppvPublishServer –UserRefreshEnabled –GlobalRefreshEnabled</strong>)</p></li>
|
||||
</ul></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
@ -59,18 +71,12 @@ The client management console contains the following described main tabs.
|
||||
<tr class="odd">
|
||||
<td align="left"><p>App Connection Groups</p></td>
|
||||
<td align="left"><p>The <strong>APP CONNECTION GROUPS</strong> tab displays all of the connection groups that are available to the current user. Click a specific connection group to see all of the packages that are part of the selected group. This displays information about connection groups that are already in use and how much of the connection group contents have been downloaded to the computer. Additionally, you can start and stop connection group downloads. You can use this section to initiate a repair. A repair will remove all of the user state that is associated a connection group.</p>
|
||||
<p>(Associated PowerShell cmdlets: Download - <strong>Mount-AppvClientConnectionGroup</strong>. Repair -<strong>AppvClientConnectionGroup</strong>.)</p>
|
||||
<p>(Associated Windows PowerShell cmdlets: Download - <strong>Mount-AppvClientConnectionGroup</strong>. Repair -<strong>AppvClientConnectionGroup</strong>.)</p>
|
||||
<p></p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
[How to Access the Client Management Console](appv-accessing-the-client-management-console.md)
|
||||
|
||||
[How to Configure the Client to Receive Package and Connection Groups Updates From the Publishing Server](appv-configure-the-client-to-receive-updates-from-the-publishing-server.md)
|
||||
|
||||
## Have a suggestion for App-V?
|
||||
|
||||
|
||||
@ -78,14 +84,4 @@ Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-micros
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
[Operations for App-V](appv-operations.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# How to View and Configure Applications and Default Virtual Application Extensions by Using the Management Console
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
Use the following procedure to view and configure default package extensions.
|
||||
|
||||
|
||||
@ -11,6 +11,7 @@ ms.prod: w10
|
||||
|
||||
# Viewing App-V Server Publishing Metadata
|
||||
|
||||
Applies to: Windows Server 2016, Windows Server 2012 R2, Windows Server 2012, and Windows Server 2008 R2
|
||||
|
||||
Use this procedure to view publishing metadata, which can help you resolve publishing-related issues. You must be using the App-V Management server to use this procedure.
|
||||
|
||||
|
||||
Some files were not shown because too many files have changed in this diff Show More
Reference in New Issue
Block a user