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

Merge remote-tracking branch 'refs/remotes/origin/master' into live

Browse Source
This commit is contained in:
LizRoss 2016-08-04 10:01:58 -07:00
commit 0d7d0d62bd
65 changed files with 278 additions and 141 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
browsers/edge/available-policies.md
View File

@ -6,6 +6,7 @@ ms.prod: edge
ms.mktglfcycl: explore
ms.sitesec: library
title: Available policies for Microsoft Edge (Microsoft Edge for IT Pros)
localizationpriority: high
---
# Available policies for Microsoft Edge

1
browsers/edge/emie-to-improve-compatibility.md
View File

@ -7,6 +7,7 @@ ms.mktglfcycl: support
ms.sitesec: library
ms.pagetype: appcompat
title: Use Enterprise Mode to improve compatibility (Microsoft Edge for IT Pros)
localizationpriority: high
---
# Use Enterprise Mode to improve compatibility

1
browsers/edge/enterprise-guidance-using-microsoft-edge-and-ie11.md
View File

@ -7,6 +7,7 @@ ms.prod: edge
ms.mktglfcycl: support
ms.sitesec: library
ms.pagetype: appcompat
localizationpriority: high
---
# Browser: Microsoft Edge and Internet Explorer 11

1
browsers/edge/hardware-and-software-requirements.md
View File

@ -7,6 +7,7 @@ ms.mktglfcycl: support
ms.sitesec: library
ms.pagetype: appcompat
title: Microsoft Edge requirements and language support (Microsoft Edge for IT Pros)
localizationpriority: high
---
# Microsoft Edge requirements and language support

1
browsers/edge/security-enhancements-microsoft-edge.md
View File

@ -5,6 +5,7 @@ ms.mktglfcycl: explore
ms.sitesec: library
ms.pagetype: security
title: Security enhancements for Microsoft Edge (Microsoft Edge for IT Pros)
localizationpriority: high
---
# Security enhancements for Microsoft Edge

200
browsers/internet-explorer/ie11-deploy-guide/collect-data-using-enterprise-site-discovery.md
View File

@ -9,7 +9,6 @@ title: Collect data using Enterprise Site Discovery
ms.sitesec: library
---
# Collect data using Enterprise Site Discovery
**Applies to:**
@ -64,9 +63,49 @@ Data is collected on the configuration characteristics of IE and the sites it br
|Number of visits | X | X | X | X |Number of times a site has been visited. |
|Zone | X | X | X | X |Zone used by IE to browse sites, based on browser settings. |
<p>**Important**<br>By default, IE doesn’t collect this data; you have to turn this feature on if you want to use it. After you turn on this feature, data is collected on all sites visited by IE, except during InPrivate sessions.
The data collection process is silent, so there’s no notification to the employee. Therefore, you must get consent from the employee before you start collecting info. You must also make sure that using this feature complies with all applicable local laws and regulatory requirements.
>**Important**<br>By default, IE doesn’t collect this data; you have to turn this feature on if you want to use it. After you turn on this feature, data is collected on all sites visited by IE, except during InPrivate sessions. Additionally, the data collection process is silent, so there’s no notification to the employee. Therefore, you must get consent from the employee before you start collecting info. You must also make sure that using this feature complies with all applicable local laws and regulatory requirements.
### Understanding the returned reason codes
The following tables provide more info about the Document mode reason, Browser state reason, and the Zone codes that are returned as part of your data collection.
#### DocMode reason
The codes in this table can tell you what document mode was set by IE for a webpage.<br>These codes only apply to Internet Explorer 10 and Internet Explorer 11.
|Code |Description |
|-----|------------|
|3 |Page state is set by the `FEATURE_DOCUMENT_COMPATIBLE_MODE` feature control key.|
|4 |Page is using an X-UA-compatible meta tag. |
|5 |Page is using an X-UA-compatible HTTP header. |
|6 |Page appears on an active **Compatibility View** list. |
|7 |Page is using native XML parsing. |
#### Browser state reason
The codes in this table can tell you why the browser is in its current state. Also called “browser mode”.<br>These codes only apply to Internet Explorer 10 and Internet Explorer 11.
|Code |Description |
|-----|------------|
|1 |Site is on the intranet, with the **Display intranet sites in Compatibility View** box checked. |
|2 |Site appears on an active **Compatibility View** list, created in Group Policy. |
|3 |Site appears on an active **Compatibility View** list, created by the user. |
|4 |Page is using an X-UA-compatible tag. |
|5 |Page state is set by the **Developer** toolbar. |
|6 |Page state is set by the `FEATURE_BROWSER_EMULATION` feature control key. |
|7 |Site appears on the Microsoft **Compatibility View (CV)** list. |
|8 |Site appears on the **Quirks** list, created in Group Policy. |
|11 |Site is using the default browser. |
#### Zone
The codes in this table can tell you what zone is being used by IE to browse sites, based on browser settings.<br>These codes apply to Internet Explorer 8, Internet Explorer 9, Internet Explorer 10, and Internet Explorer 11.
|Code |Description |
|-----|------------|
|-1 |Internet Explorer is using an invalid zone. |
|0 |Internet Explorer is using the Local machine zone. |
|1 |Internet Explorer is using the Local intranet zone. |
|2 |Internet Explorer is using the Trusted sites zone. |
|3 |Internet Explorer is using the Internet zone. |
|4 |Internet Explorer is using the Restricted sites zone. |
## Where is the data stored and how do I collect it?
The data is stored locally, in an industry-standard WMI class, .MOF file or in an XML file, depending on your configuration. This file remains on the client computer until it’s collected. To collect the files, we recommend:
@ -78,8 +117,9 @@ The data is stored locally, in an industry-standard WMI class, .MOF file or in a
## WMI Site Discovery suggestions
We recommend that you collect your data for at most a month at a time, to capture a user’s typical workflow. We don’t recommend collecting data longer than that because the data is stored in a WMI provider and can fill up your computer’s hard drive. You may also want to collect data only for pilot users or a representative sample of people, instead of turning this feature on for everyone in your company.
On average, a website generates about 250bytes of data for each visit, causing only a minor impact to Internet Explorer’s performance. Over the course of a month, collecting data from 20 sites per day from 1,000 users, you’ll get about 150MB of data:<br>\[250bytes (per site visit) \* 20sites/day\* 30days = (approximately) 150KB \*1000users = (approximately) 150MB\].
<p>**Important**<br>The data collection process is silent, so there’s no notification to the employee. Therefore, you must get consent from the employee before you start collecting info. You must also make sure that using this feature complies with all applicable local laws and regulatory requirements.
On average, a website generates about 250bytes of data for each visit, causing only a minor impact to Internet Explorer’s performance. Over the course of a month, collecting data from 20 sites per day from 1,000 users, you’ll get about 150MB of data:<p>250 bytes (per site visit) X 20 sites/day X 30 days = (approximately) 150KB X 1000 users = (approximately) 150MB
>**Important**<br>The data collection process is silent, so there’s no notification to the employee. Therefore, you must get consent from the employee before you start collecting info. You must also make sure that using this feature complies with all applicable local laws and regulatory requirements.
## Getting ready to use Enterprise Site Discovery
Before you can start to collect your data, you must run the provided PowerShell script (IETelemetrySetUp.ps1) on your client devices to start generating the site discovery data and to set up a place to store this data locally. Then, you must start collecting the site discovery data from the client devices, using one of these three options:
@ -92,16 +132,17 @@ Before you can start to collect your data, you must run the provided PowerShell
### WMI only: Running the PowerShell script to compile the .MOF file and to update security privileges
You need to set up your computers for data collection by running the provided PowerShell script (IETelemetrySetUp.ps1) to compile the .mof file and to update security privileges for the new WMI classes.
<p>**Important**<br>You must run this script if you’re using WMI as your data output. It's not necessary if you're using XML as your data output.
![](images/wedge.gif) **To set up Enterprise Site Discovery**
>**Important**<br>You must run this script if you’re using WMI as your data output. It's not necessary if you're using XML as your data output.
**To set up Enterprise Site Discovery**
- Start PowerShell in elevated mode (using admin privileges) and run IETElemetrySetUp.ps1 by by-passing the PowerShell execution policy, using this command: `powershell -ExecutionPolicy Bypass .\IETElemetrySetUp.ps1`. For more info, see [about Execution Policies](http://go.microsoft.com/fwlink/p/?linkid=517460).
### WMI only: Set up your firewall for WMI data
If you choose to use WMI as your data output, you need to make sure that your WMI data can travel through your firewall for the domain. If you’re sure, you can skip this section; otherwise, follow these steps:
![](images/wedge.gif) **To set up your firewall**
**To set up your firewall**
1. In **Control Panel**, click **System and Security**, and then click **Windows Firewall**.
@ -111,65 +152,107 @@ If you choose to use WMI as your data output, you need to make sure that your WM
## Use PowerShell to finish setting up Enterprise Site Discovery
You can determine which zones or domains are used for data collection, using PowerShell. If you don’t want to use PowerShell, you can do this using Group Policy. For more info, see [Use Group Policy to finish setting up Enterprise Site Discovery](#use-group-policy-to-finish-setting-up-enterprise-site-discovery).
<p>**Important**<br>The .ps1 file updates turn on Enterprise Site Discovery and WMI collection for all users on a device.
>**Important**<br>The .ps1 file updates turn on Enterprise Site Discovery and WMI collection for all users on a device.
- **Domain allow list.** If you have a domain allow list, a comma-separated list of domains that should have this feature turned on, you should use this process.
- **Zone allow list.** If you have a zone allow list, a comma-separated list of zones that should have this feature turned on, you should use this process.
![](images/wedge.gif) **To set up data collection using a domain allow list**
**To set up data collection using a domain allow list**
- Start PowerShell in elevated mode (using admin privileges) and run IETElemetrySetUp.ps1, using this command: `.\IETElemetrySetUp.ps1 [other args] -SiteAllowList sharepoint.com,outlook.com,onedrive.com`.
**Important**<br>Wildcards, like \*.microsoft.com, aren’t supported.
>**Important**<br>Wildcards, like \*.microsoft.com, aren’t supported.
![](images/wedge.gif) **To set up data collection using a zone allow list**
**To set up data collection using a zone allow list**
- Start PowerShell in elevated mode (using admin privileges) and run IETElemetrySetUp.ps1, using this command: `.\IETElemetrySetUp.ps1 [other args] -ZoneAllowList Computer,Intranet,TrustedSites,Internet,RestrictedSites`.
**Important**<br>Only Computer, Intranet, TrustedSites, Internet, and RestrictedSites are supported.
>**Important**<br>Only Computer, Intranet, TrustedSites, Internet, and RestrictedSites are supported.
## Use Group Policy to finish setting up Enterprise Site Discovery
You can use Group Policy to finish setting up Enterprise Site Discovery. If you don’t want to use Group Policy, you can do this using PowerShell. For more info, see [Use Powershell to finish setting up Enterprise Site Discovery](#use-powershell-to-finish-setting-up-enterprise-site-discovery).
<p>**Note**<br> All of the Group Policy settings can be used individually or as a group.
![](images/wedge.gif) **To set up Enterprise Site Discovery using Group Policy**
>**Note**<br> All of the Group Policy settings can be used individually or as a group.
**To set up Enterprise Site Discovery using Group Policy**
- Open your Group Policy editor, and go to these new settings:
|Setting name and location |Description |Options |
|---------------------------|-------------|---------|
|Administrative Templates\Windows Components\Internet Explorer\Turn on Site Discovery WMI output |Writes collected data to a WMI class, which can be aggregated using a client-management solution like Configuration Manager. |<ul><li>**On.** Turns on WMI recording.</li><li>**Off.** Turns off WMI recording.</li></ul> |
|Administrative Templates\Windows Components\Internet Explorer\Turn on Site Discovery XML output |Writes collected data to an XML file, which is stored in your specified location. |<ul><li>**XML file path.** Including this turns on XML recording.</li> <li>**Blank.** Turns off XML recording.</li></ul> |
|Administrative Templates\Windows Components\Internet Explorer\Limit Site Discovery output by Zone |Manages which zone can collect data. |To specify which zones can collect data, you must include a binary number that represents your selected zones, based on this order:<p>0 – Restricted Sites zone<br>0 – Internet zone<br>0 – Trusted Sites zone<br>0 – Local Intranet zone<br>0 – Local Machine zone<p>**Example 1:** Include only the Local Intranet zone<p>Binary representation: *00010*, based on:<p>0 – Restricted Sites zone<br>0 – Internet zone<br>0 – Trusted Sites zone<br>1 – Local Intranet zone<br>0 – Local Machine zone<p>**Example 2:** Include only the Restricted Sites, Trusted Sites, and Local Intranet zones<p>Binary representation: *10110*, based on:<p>1 – Restricted Sites zone<br>0 – Internet zone<br>1 – Trusted Sites zone<br>1 – Local Intranet zone<br>1 – Local Machine zone |
|Administrative Templates\Windows Components\Internet Explorer\Limit Site Discovery output by domain |Manages which domains can collect data |To specify which domains can collect data, you must include your selected domains, one domain per line, in the provided box. It should look like:<p>microsoft.sharepoint.com<br>outlook.com<br>onedrive.com<br>timecard.contoso.com<br>LOBApp.contoso.com |
|Setting name and location |Description |Options |
|---------------------------|-------------|---------|
|Administrative Templates\Windows Components\Internet Explorer\Turn on Site Discovery WMI output |Writes collected data to a WMI class, which can be aggregated using a client-management solution like Configuration Manager. |<ul><li>**On.** Turns on WMI recording.</li><li>**Off.** Turns off WMI recording.</li></ul> |
|Administrative Templates\Windows Components\Internet Explorer\Turn on Site Discovery XML output |Writes collected data to an XML file, which is stored in your specified location. |<ul><li>**XML file path.** Including this turns on XML recording.</li><li>**Blank.** Turns off XML recording.</li></ul> |
|Administrative Templates\Windows Components\Internet Explorer\Limit Site Discovery output by Zone |Manages which zone can collect data. |To specify which zones can collect data, you must include a binary number that represents your selected zones, based on this order:<p>0 – Restricted Sites zone<br>0 – Internet zone<br>0 – Trusted Sites zone<br>0 – Local Intranet zone<br>0 – Local Machine zone<p>**Example 1:** Include only the Local Intranet zone<p>Binary representation: *00010*, based on:<p>0 – Restricted Sites zone<br>0 – Internet zone<br>0 – Trusted Sites zone<br>1 – Local Intranet zone<br>0 – Local Machine zone<p>**Example 2:** Include only the Restricted Sites, Trusted Sites, and Local Intranet zones<p>Binary representation: *10110*, based on:<p>1 – Restricted Sites zone<br>0 – Internet zone<br>1 – Trusted Sites zone<br>1 – Local Intranet zone<br>1 – Local Machine zone |
|Administrative Templates\Windows Components\Internet Explorer\Limit Site Discovery output by domain |Manages which domains can collect data |To specify which domains can collect data, you must include your selected domains, one domain per line, in the provided box. It should look like:<p>microsoft.sharepoint.com<br>outlook.com<br>onedrive.com<br>timecard.contoso.com<br>LOBApp.contoso.com |
### Combining WMI and XML Group Policy settings
You can use both the WMI and XML settings individually or together, based on:
You can use both the WMI and XML settings individually or together:
![](images/wedge.gif) **To turn off Enterprise Site Discovery**
<ul>
<li><b>Turn on Site Discovery WMI output:</b> Off</li>
<li><b>Turn on Site Discovery XML output:</b> Blank</li>
</ul>
**To turn off Enterprise Site Discovery**
<table>
<tr>
<th>Setting name</th>
<th>Option</th>
</tr>
<tr>
<td>Turn on Site Discovery WMI output</td>
<td>Off</td>
</tr>
<tr>
<td>Turn on Site Discovery XML output</td>
<td>Blank</td>
</tr>
</table>
![](images/wedge.gif) **To turn on WMI recording only**
<ul>
<li><b>Turn on Site Discovery WMI output:</b> On</li>
<li><b>Turn on Site Discovery XML output:</b> Blank</li>
</ul>
**Turn on WMI recording only**
<table>
<tr>
<th>Setting name</th>
<th>Option</th>
</tr>
<tr>
<td>Turn on Site Discovery WMI output</td>
<td>On</td>
</tr>
<tr>
<td>Turn on Site Discovery XML output</td>
<td>Blank</td>
</tr>
</table>
![](images/wedge.gif) **To turn on XML recording only**
<ul>
<li><b>Turn on Site Discovery WMI output:</b> Off</li>
<li><b>Turn on Site Discovery XML output:</b> XML file path</li>
</ul>
**To turn on XML recording only**
<table>
<tr>
<th>Setting name</th>
<th>Option</th>
</tr>
<tr>
<td>Turn on Site Discovery WMI output</td>
<td>Off</td>
</tr>
<tr>
<td>Turn on Site Discovery XML output</td>
<td>XML file path</td>
</tr>
</table>
![](images/wedge.gif) **To turn on both WMI and XML recording**
<ul>
<li><b>Turn on Site Discovery WMI output:</b> On</li>
<li><b>Turn on Site Discovery XML output:</b> XML file path</li>
</ul>
**To turn on both WMI and XML recording**
<table>
<tr>
<th>Setting name</th>
<th>Option</th>
</tr>
<tr>
<td>Turn on Site Discovery WMI output</td>
<td>On</td>
</tr>
<tr>
<td>Turn on Site Discovery XML output</td>
<td>XML file path</td>
</tr>
</table>
## Use Configuration Manager to collect your data
After you’ve collected your data, you’ll need to get the local files off of your employee’s computers. To do this, use the hardware inventory process in Configuration Manager, using one of these options:
@ -183,7 +266,7 @@ After you’ve collected your data, you’ll need to get the local files off of
### Collect your hardware inventory using the MOF Editor while connected to a client device
You can collect your hardware inventory using the MOF Editor, while you’re connected to your client devices.
![](images/wedge.gif) **To collect your inventory**
**To collect your inventory**
1. From the Configuration Manager, click **Administration**, click **Client Settings**, double-click **Default Client Settings**, click **Hardware Inventory**, and then click **Set Classes**.
@ -209,7 +292,7 @@ Your environment is now ready to collect your hardware inventory and review the
### Collect your hardware inventory using the MOF Editor with a .MOF import file
You can collect your hardware inventory using the MOF Editor and a .MOF import file.
![](images/wedge.gif) **To collect your inventory**
**To collect your inventory**
1. From the Configuration Manager, click **Administration**, click **Client Settings**, double-click **Default Client Settings**, click **Hardware Inventory**, and then click **Set Classes**.
@ -223,7 +306,7 @@ Your environment is now ready to collect your hardware inventory and review the
### Collect your hardware inventory using the SMS\DEF.MOF file (System Center Configuration Manager 2007 only)
You can collect your hardware inventory using the using the Systems Management Server (SMS\DEF.MOF) file. Editing this file lets you collect your data for System Center Configuration Manager 2007. If you aren’t using this version of Configuration Manager, you won’t want to use this option.
![](images/wedge.gif) **To collect your inventory**
**To collect your inventory**
1. Using a text editor like Notepad, open the SMS\DEF.MOF file, located in your `<configmanager_install_location>\inboxes\clifiles.src\hinv` directory.
@ -291,8 +374,8 @@ You can collect your hardware inventory using the using the Systems Management S
};
```
3. Save the file and close it to the same location.<br>
Your environment is now ready to collect your hardware inventory and review the sample reports.
3. Save the file and close it to the same location.
Your environment is now ready to collect your hardware inventory and review the sample reports.
## View the sample reports with your collected data
The sample reports, **SCCM Report Sample – ActiveX.rdl** and **SCCM Report Sample – Site Discovery.rdl**, work with System Center 2012, so you can review your collected data.
@ -339,26 +422,27 @@ After the XML files are created, you can use your own solutions to extract and p
```
You can import this XML data into the correct version of the Enterprise Mode Site List Manager, automatically adding the included sites to your Enterprise Mode site list.
![](images/wedge.gif) **To add your XML data to your Enterprise Mode site list**
**To add your XML data to your Enterprise Mode site list**
1. Open the Enterprise Mode Site List Manager, click **File**, and then click **Bulk add from file**.
![Enterprise Mode Site List Manager with Bulk add from file option](images/bulkadd-emiesitelistmgr.png)
2. Go to your XML file to add the included sites to the tool, and then click **Open**.<br>
Each site is validated and if successful, added to the global site list when you click **OK** to close the menu. If a site doesn’t pass validation, you can try to fix the issues or pick the site and click **Add to list** to ignore the validation problem. For more information about fixing validation problems, see [Fix validation problems using the Enterprise Mode Site List Manager](fix-validation-problems-using-the-enterprise-mode-site-list-manager.md).
![Enterprise Mode Site List Manager with Bulk add from file option](images/bulkadd-emiesitelistmgr.png)
2. Go to your XML file to add the included sites to the tool, and then click **Open**.<br>Each site is validated and if successful, added to the global site list when you click **OK** to close the menu. If a site doesn’t pass validation, you can try to fix the issues or pick the site and click **Add to list** to ignore the validation problem. For more information about fixing validation problems, see [Fix validation problems using the Enterprise Mode Site List Manager](fix-validation-problems-using-the-enterprise-mode-site-list-manager.md).
3. Click **OK** to close the **Bulk add sites to the list** menu.
## Turn off data collection on your client devices
After you’ve collected your data, you’ll need to turn Enterprise Site Discovery off.
![](images/wedge.gif) **To stop collecting data, using PowerShell**
**To stop collecting data, using PowerShell**
- On your client computer, start Windows PowerShell in elevated mode (using admin privileges) and run `IETelemetrySetUp.ps1`, using this command: `powershell -ExecutionPolicy Bypass .\IETElemetrySetUp.ps1 –IEFeatureOff`.<p>**Note**<br>
Turning off data collection only disables the Enterprise Site Discovery feature – all data already written to WMI stays on your employee’s computer.
- On your client computer, start Windows PowerShell in elevated mode (using admin privileges) and run `IETelemetrySetUp.ps1`, using this command: `powershell -ExecutionPolicy Bypass .\IETElemetrySetUp.ps1 –IEFeatureOff`.
 
![](images/wedge.gif) **To stop collecting data, using Group Policy**
>**Note**<br>Turning off data collection only disables the Enterprise Site Discovery feature – all data already written to WMI stays on your employee’s computer.
**To stop collecting data, using Group Policy**
1. Open your Group Policy editor, go to `Administrative Templates\Windows Components\Internet Explorer\Turn on Site Discovery WMI output`, and click **Off**.
@ -367,7 +451,7 @@ Turning off data collection only disables the Enterprise Site Discovery feature
### Delete already stored data from client computers
You can completely remove the data stored on your employee’s computers.
![](images/wedge.gif) **To delete all existing data**
**To delete all existing data**
- On the client computer, start PowerShell in elevated mode (using admin privileges) and run these four commands:
@ -379,7 +463,7 @@ You can completely remove the data stored on your employee’s computers.
- `Remove-Item -Path 'HKCU:\Software\Microsoft\Internet Explorer\WMITelemetry'`
 ## Related topics
## Related topics
* [Enterprise Mode Site List Manager (schema v.2) download](http://go.microsoft.com/fwlink/?LinkId=746562)
* [Enterprise Mode for Internet Explorer 11 (IE11)](enterprise-mode-overview-for-ie11.md)
 

1
devices/surface-hub/accessibility-surface-hub.md
View File

@ -8,6 +8,7 @@ ms.mktglfcycl: manage
ms.pagetype: surfacehub
ms.sitesec: library
author: TrudyHa
localizationpriority: medium
---
# Accessibility (Surface Hub)

1
devices/surface-hub/admin-group-management-for-surface-hub.md
View File

@ -8,6 +8,7 @@ ms.mktglfcycl: manage
ms.sitesec: library
ms.pagetype: surfacehub, security
author: TrudyHa
localizationpriority: medium
---
# Admin group management (Surface Hub)

1
devices/surface-hub/appendix-a-powershell-scripts-for-surface-hub.md
View File

@ -8,6 +8,7 @@ ms.mktglfcycl: manage
ms.sitesec: library
ms.pagetype: surfacehub
author: TrudyHa
localizationpriority: medium
---
# Appendix: PowerShell (Surface Hub)

1
devices/surface-hub/apply-activesync-policies-for-surface-hub-device-accounts.md
View File

@ -8,6 +8,7 @@ ms.mktglfcycl: manage
ms.sitesec: library
ms.pagetype: surfacehub
author: TrudyHa
localizationpriority: medium
---
# Applying ActiveSync policies to device accounts (Surface Hub)

2
devices/surface-hub/change-surface-hub-device-account.md
View File

@ -8,7 +8,7 @@ ms.mktglfcycl: manage
ms.sitesec: library
ms.pagetype: surfacehub
author: TrudyHa
localizationpriority: high
localizationpriority: medium
---
# Change the Microsoft Surface Hub device account

1
devices/surface-hub/connect-and-display-with-surface-hub.md
View File

@ -7,6 +7,7 @@ ms.mktglfcycl: manage
ms.sitesec: library
ms.pagetype: surfacehub
author: TrudyHa
localizationpriority: medium
---
# Connect other devices and display with Surface Hub

2
devices/surface-hub/create-a-device-account-using-office-365.md
View File

@ -8,7 +8,7 @@ ms.mktglfcycl: manage
ms.sitesec: library
ms.pagetype: surfacehub
author: TrudyHa
localizationpriority: high
localizationpriority: medium
---
# Create a device account using UI (Surface Hub)

1
devices/surface-hub/create-and-test-a-device-account-surface-hub.md
View File

@ -8,6 +8,7 @@ ms.mktglfcycl: manage
ms.sitesec: library
ms.pagetype: surfacehub
author: TrudyHa
localizationpriority: medium
---
# Create and test a device account (Surface Hub)

1
devices/surface-hub/device-reset-surface-hub.md
View File

@ -8,6 +8,7 @@ ms.mktglfcycl: manage
ms.sitesec: library
ms.pagetype: surfacehub
author: TrudyHa
localizationpriority: medium
---
# Device reset (Surface Hub)

2
devices/surface-hub/exchange-properties-for-surface-hub-device-accounts.md
View File

@ -8,7 +8,7 @@ ms.mktglfcycl: manage
ms.sitesec: library
ms.pagetype: surfacehub
author: TrudyHa
localizationpriority: high
localizationpriority: medium
---
# Microsoft Exchange properties (Surface Hub)

1
devices/surface-hub/first-run-program-surface-hub.md
View File

@ -8,6 +8,7 @@ ms.mktglfcycl: manage
ms.sitesec: library
ms.pagetype: surfacehub
author: TrudyHa
localizationpriority: medium
---
# First-run program (Surface Hub)

2
devices/surface-hub/hybrid-deployment-surface-hub-device-accounts.md
View File

@ -8,7 +8,7 @@ ms.mktglfcycl: deploy
ms.sitesec: library
ms.pagetype: surfacehub
author: TrudyHa
localizationpriority: high
localizationpriority: medium
---
# Hybrid deployment (Surface Hub)

1
devices/surface-hub/i-am-done-finishing-your-surface-hub-meeting.md
View File

@ -7,6 +7,7 @@ ms.mktglfcycl: manage
ms.sitesec: library
ms.pagetype: surfacehub
author: TrudyHa
localizationpriority: medium
---
# End a Surface Hub meeting with I'm Done

2
devices/surface-hub/index.md
View File

@ -7,7 +7,7 @@ ms.mktglfcycl: explore
ms.sitesec: library
ms.pagetype: surfacehub
author: TrudyHa
localizationpriority: high
localizationpriority: medium
---
# Microsoft Surface Hub

1
devices/surface-hub/install-apps-on-surface-hub.md
View File

@ -8,6 +8,7 @@ ms.mktglfcycl: deploy
ms.sitesec: library
ms.pagetype: surfacehub, store
author: TrudyHa
localizationpriority: medium
---
# Install apps on your Microsoft Surface Hub

1
devices/surface-hub/intro-to-surface-hub.md
View File

@ -8,6 +8,7 @@ ms.mktglfcycl: explore
ms.sitesec: library
ms.pagetype: surfacehub
author: TrudyHa
localizationpriority: medium
---
# Intro to Microsoft Surface Hub

1
devices/surface-hub/manage-settings-with-local-admin-account-surface-hub.md
View File

@ -8,6 +8,7 @@ ms.mktglfcycl: manage
ms.sitesec: library
ms.pagetype: surfacehub
author: TrudyHa
localizationpriority: medium
---
# Manage settings with a local admin account (Surface Hub)

2
devices/surface-hub/manage-settings-with-mdm-for-surface-hub.md
View File

@ -8,7 +8,7 @@ ms.mktglfcycl: manage
ms.sitesec: library
ms.pagetype: surfacehub, mobility
author: TrudyHa
localizationpriority: high
localizationpriority: medium
---
# Manage settings with an MDM provider (Surface Hub)

1
devices/surface-hub/manage-surface-hub.md
View File

@ -8,6 +8,7 @@ ms.mktglfcycl: manage
ms.sitesec: library
ms.pagetype: surfacehub
author: TrudyHa
localizationpriority: medium
---
# Manage Microsoft Surface Hub

1
devices/surface-hub/manage-windows-updates-for-surface-hub.md
View File

@ -8,6 +8,7 @@ ms.mktglfcycl: manage
ms.sitesec: library
ms.pagetype: surfacehub
author: TrudyHa
localizationpriority: medium
---
# Windows updates (Surface Hub)

2
devices/surface-hub/monitor-surface-hub.md
View File

@ -8,7 +8,7 @@ ms.mktglfcycl: manage
ms.sitesec: library
ms.pagetype: surfacehub
author: TrudyHa
localizationpriority: high
localizationpriority: medium
---
# Monitor your Microsoft Surface Hub

2
devices/surface-hub/on-premises-deployment-surface-hub-device-accounts.md
View File

@ -8,7 +8,7 @@ ms.mktglfcycl: deploy
ms.sitesec: library
ms.pagetype: surfacehub
author: TrudyHa
localizationpriority: high
localizationpriority: medium
---
# On-premises deployment (Surface Hub)

2
devices/surface-hub/online-deployment-surface-hub-device-accounts.md
View File

@ -8,7 +8,7 @@ ms.mktglfcycl: deploy
ms.sitesec: library
ms.pagetype: surfacehub
author: TrudyHa
localizationpriority: high
localizationpriority: medium
---
# Online deployment with Office 365 (Surface Hub)

1
devices/surface-hub/password-management-for-surface-hub-device-accounts.md
View File

@ -8,6 +8,7 @@ ms.mktglfcycl: manage
ms.sitesec: library
ms.pagetype: surfacehub, security
author: TrudyHa
localizationpriority: medium
---
# Password management (Surface Hub)

2
devices/surface-hub/physically-install-your-surface-hub-device.md
View File

@ -8,7 +8,7 @@ ms.mktglfcycl: manage
ms.sitesec: library
ms.pagetype: surfacehub, readiness
author: TrudyHa
localizationpriority: high
localizationpriority: medium
---
# Physically install Microsoft Surface Hub

1
devices/surface-hub/prepare-your-environment-for-surface-hub.md
View File

@ -8,6 +8,7 @@ ms.mktglfcycl: plan
ms.sitesec: library
ms.pagetype: surfacehub
author: TrudyHa
localizationpriority: medium
---
# Prepare your environment for Microsoft Surface Hub

1
devices/surface-hub/provisioning-packages-for-certificates-surface-hub.md
View File

@ -8,6 +8,7 @@ ms.mktglfcycl: deploy
ms.sitesec: library
ms.pagetype: surfacehub
author: TrudyHa
localizationpriority: medium
---
# Create provisioning packages (Surface Hub)

2
devices/surface-hub/save-bitlocker-key-surface-hub.md
View File

@ -8,7 +8,7 @@ ms.mktglfcycl: manage
ms.sitesec: library
ms.pagetype: surfacehub, security
author: TrudyHa
localizationpriority: high
localizationpriority: medium
---
# Save your BitLocker key (Surface Hub)

2
devices/surface-hub/set-up-your-surface-hub.md
View File

@ -8,7 +8,7 @@ ms.mktglfcycl: deploy
ms.sitesec: library
ms.pagetype: surfacehub
author: TrudyHa
localizationpriority: high
localizationpriority: mediumh
---
# Set up Microsoft Surface Hub

2
devices/surface-hub/setup-worksheet-surface-hub.md
View File

@ -8,7 +8,7 @@ ms.mktglfcycl: deploy
ms.sitesec: library
ms.pagetype: surfacehub
author: TrudyHa
localizationpriority: high
localizationpriority: medium
---
# Setup worksheet (Surface Hub)

2
devices/surface-hub/surface-hub-administrators-guide.md
View File

@ -8,7 +8,7 @@ ms.mktglfcycl: deploy
ms.sitesec: library
ms.pagetype: surfacehub
author: TrudyHa
localizationpriority: high
localizationpriority: medium
---
# Microsoft Surface Hub administrator's guide

2
devices/surface-hub/troubleshoot-surface-hub.md
View File

@ -8,7 +8,7 @@ ms.mktglfcycl: support
ms.sitesec: library
ms.pagetype: surfacehub
author: TrudyHa
localizationpriority: high
localizationpriority: medium
---
# Troubleshoot Microsoft Surface Hub

2
devices/surface-hub/use-fully-qualified-domain-name-surface-hub.md
View File

@ -4,7 +4,7 @@ description: Troubleshoot common problems, including setup issues, Exchange Acti
ms.assetid: CF58F74D-8077-48C3-981E-FCFDCA34B34A
keywords: ["Troubleshoot common problems", "setup issues", "Exchange ActiveSync errors"]
author: TrudyHa
localizationpriority: high
localizationpriority: medium
---
# When to use a fully qualified domain name with Surface Hub

2
devices/surface-hub/use-room-control-system-with-surface-hub.md
View File

@ -8,7 +8,7 @@ ms.mktglfcycl: manage
ms.sitesec: library
ms.pagetype: surfacehub
author: TrudyHa
localizationpriority: high
localizationpriority: medium
---
# Using a room control system (Surface Hub)

2
devices/surface-hub/wireless-network-management-for-surface-hub.md
View File

@ -8,7 +8,7 @@ ms.mktglfcycl: manage
ms.sitesec: library
ms.pagetype: surfacehub, networking
author: TrudyHa
localizationpriority: high
localizationpriority: medium
---
# Wireless network management (Surface Hub)

1
windows/keep-secure/add-apps-to-protected-list-using-custom-uri.md
View File

@ -8,6 +8,7 @@ ms.mktglfcycl: explore
ms.pagetype: security
ms.sitesec: library
author: eross-msft
localizationpriority: high
---
# Add apps to your Windows Information Protection (WIP) policy by using the Microsoft Intune custom URI functionality

1
windows/keep-secure/create-and-verify-an-efs-dra-certificate.md
View File

@ -6,6 +6,7 @@ ms.prod: w10
ms.mktglfcycl: explore
ms.sitesec: library
ms.pagetype: security
localizationpriority: high
---
# Create and verify an Encrypting File System (EFS) Data Recovery Agent (DRA) certificate

1
windows/keep-secure/create-vpn-and-wip-policy-using-intune.md
View File

@ -8,6 +8,7 @@ ms.mktglfcycl: explore
ms.sitesec: library
ms.pagetype: security
author: eross-msft
localizationpriority: high
---
# Create and deploy a VPN policy for Windows Information Protection (WIP) using Microsoft Intune

1
windows/keep-secure/create-wip-policy-using-intune.md
View File

@ -7,6 +7,7 @@ ms.mktglfcycl: explore
ms.sitesec: library
ms.pagetype: security
author: eross-msft
localizationpriority: high
---
# Create a Windows Information Protection (WIP) policy using Microsoft Intune

1
windows/keep-secure/create-wip-policy-using-sccm.md
View File

@ -8,6 +8,7 @@ ms.mktglfcycl: explore
ms.sitesec: library
ms.pagetype: security
author: eross-msft
localizationpriority: high
---
# Create and deploy a Windows Information Protection (WIP) policy using System Center Configuration Manager

1
windows/keep-secure/deploy-wip-policy-using-intune.md
View File

@ -8,6 +8,7 @@ ms.mktglfcycl: explore
ms.sitesec: library
ms.pagetype: security
author: eross-msft
localizationpriority: high
---
# Deploy your Windows Information Protection (WIP) policy using Microsoft Intune

1
windows/keep-secure/enlightened-microsoft-apps-and-wip.md
View File

@ -8,6 +8,7 @@ ms.mktglfcycl: explore
ms.sitesec: library
ms.pagetype: security
author: eross-msft
localizationpriority: high
---
# List of enlightened Microsoft apps for use with Windows Information Protection (WIP)

1
windows/keep-secure/guidance-and-best-practices-wip.md
View File

@ -8,6 +8,7 @@ ms.mktglfcycl: explore
ms.sitesec: library
ms.pagetype: security
author: eross-msft
localizationpriority: high
---
# General guidance and best practices for Windows Information Protection (WIP)

1
windows/keep-secure/mandatory-settings-for-wip.md
View File

@ -6,6 +6,7 @@ ms.prod: w10
ms.mktglfcycl: explore
ms.sitesec: library
ms.pagetype: security
localizationpriority: high
---
# Mandatory tasks and settings required to turn on Windows Information Protection (WIP)

1
windows/keep-secure/overview-create-wip-policy.md
View File

@ -7,6 +7,7 @@ ms.mktglfcycl: explore
ms.sitesec: library
ms.pagetype: security
author: eross-msft
localizationpriority: high
---
# Create a Windows Information Protection (WIP) policy

1
windows/keep-secure/protect-enterprise-data-using-wip.md
View File

@ -8,6 +8,7 @@ ms.mktglfcycl: explore
ms.sitesec: library
ms.pagetype: security
author: eross-msft
localizationpriority: high
---
# Protect your enterprise data using Windows Information Protection (WIP)

1
windows/keep-secure/testing-scenarios-for-wip.md
View File

@ -8,6 +8,7 @@ ms.mktglfcycl: explore
ms.sitesec: library
ms.pagetype: security
author: eross-msft
localizationpriority: high
---
# Testing scenarios for Windows Information Protection (WIP)

1
windows/keep-secure/wip-enterprise-overview.md
View File

@ -5,6 +5,7 @@ ms.prod: w10
ms.mktglfcycl: explore
ms.sitesec: library
ms.pagetype: security
localizationpriority: high
---
# Windows Information Protection (WIP) overview

56
windows/manage/appv-about-appv.md
View File

@ -36,7 +36,7 @@ Review the following sections for information about significant changes that app
## <a href="" id="bkmk-51-prereq-configs"></a>App-V for Windows software prerequisites and supported configurations
See the following links for the App-V for Windows software prerequisites and supported configurations.
Review the following topics for information about App-V for Windows software prerequisites and supported configurations.
<table>
<colgroup>
@ -45,7 +45,7 @@ See the following links for the App-V for Windows software prerequisites and sup
</colgroup>
<thead>
<tr class="header">
<th align="left">Links to prerequisites and supported configurations</th>
<th align="left">Links to prerequisites and supported configurations topics</th>
<th align="left">Description</th>
</tr>
</thead>
@ -56,21 +56,20 @@ See the following links for the App-V for Windows software prerequisites and sup
</tr>
<tr class="even">
<td align="left"><p>[App-V Supported Configurations](appv-supported-configurations.md)</p></td>
<td align="left"><p>Supported operating systems and hardware requirements for the App-V Server, Sequencer, and Client components</p></td>
<td align="left"><p>Supported operating systems and hardware requirements for the App-V server, sequencer, and client components</p></td>
</tr>
</tbody>
</table>
 
**Support for using Configuration Manager with App-V:** App-V supports System Center 2012 R2 Configuration Manager SP1. See [Planning for App-V Integration with Configuration Manager](https://technet.microsoft.com/library/jj822982.aspx) for information about integrating your App-V environment with Configuration Manager.
## <a href="" id="bkmk-migrate-to-51"></a>Upgrade to App-V for Windows
Use the following information to upgrade to App-V for Windows from earlier versions. See [Migrating to App-V from a Previous Version](appv-migrating-to-appv-from-a-previous-version.md) for more information.
Use the following information to upgrade to App-V for Windows from earlier versions. See [Migrating to App-V for Windows from a Previous Version](appv-migrating-to-appv-from-a-previous-version.md) for more information.
### Before you start the upgrade
### Before you begin
Review the following information before you start the upgrade:
@ -103,7 +102,7 @@ Review the following information before you start the upgrade:
</tr>
<tr class="even">
<td align="left"><p>Upgrading from App-V 4.x</p></td>
<td align="left"><p>You must first upgrade to App-V 5.0. You cannot upgrade directly from App-V 4.x to App-V for Windows. For more information, see [Planning for Migrating from a Previous Version of App-V](appv-planning-for-migrating-from-a-previous-version-of-appv.md)</p></li>
<td align="left"><p>You cannot upgrade directly from App-V 4.x to App-V for Windows. You must first upgrade to App-V 5.0. For more information, see [Planning for Migrating from a Previous Version of App-V](appv-planning-for-migrating-from-a-previous-version-of-appv.md)</p></li>
</ul>
<p></p></td>
</tr>
@ -121,7 +120,6 @@ Review the following information before you start the upgrade:
</tr>
</tbody>
</table>
 
### <a href="" id="bkmk-steps-upgrd-infrastruc"></a>Steps to upgrade the App-V infrastructure
@ -141,10 +139,10 @@ Complete the following steps to upgrade each component of the App-V infrastructu
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>Step 1: Upgrade the App-V Server.</p>
<td align="left"><p>Step 1: Upgrade the App-V server components.</p>
<div class="alert">
<strong>Note</strong>  
<p>If you are not using the App-V Server, skip this step and go to the next step.</p>
<p>If you are not using the App-V server, skip this step and go to the next step.</p>
</div>
<div>
 
@ -166,7 +164,7 @@ Complete the following steps to upgrade each component of the App-V infrastructu
<tbody>
<tr class="odd">
<td align="left"><p>Windows Installer</p></td>
<td align="left"><p>Skip this step and go to step 2, “If you are upgrading the App-V Server...”</p></td>
<td align="left"><p>Skip this step and go to step 2, “If you are upgrading the App-V server...”</p></td>
</tr>
<tr class="even">
<td align="left"><p>SQL scripts</p></td>
@ -174,8 +172,8 @@ Complete the following steps to upgrade each component of the App-V infrastructu
</tr>
</tbody>
</table>
<li><p>If you are upgrading the App-V for Windows Server from App-V 5.0 SP1 Hotfix Package 3 or later, complete the steps in section [Check registry keys after installing the App-V 5.0 SP3 Server](https://technet.microsoft.com/en-us/itpro/mdop/appv-v5/check-reg-key-svr).</p></li>
<li><p>Follow the steps in [How to Deploy the App-V Server](appv-deploy-the-appv-server.md)</p></li>
<li><p>If you are upgrading to App-V for Windows server from App-V 5.0 SP1 Hotfix Package 3 or later, complete the steps in section [Check registry keys after installing the App-V 5.0 SP3 server](https://technet.microsoft.com/en-us/itpro/mdop/appv-v5/check-reg-key-svr).</p></li>
<li><p>Follow the steps in [How to Deploy the App-V server components](appv-deploy-the-appv-server.md)</p></li>
<p> </p></li>
</ol></td>
</tr>
@ -184,7 +182,7 @@ Complete the following steps to upgrade each component of the App-V infrastructu
<td align="left"><p>See [How to Install the Sequencer](appv-install-the-sequencer.md).</p></td>
</tr>
<tr class="odd">
<td align="left"><p>Step 3: Enable the in-box App-V Client.</p></td>
<td align="left"><p>Step 3: Enable the in-box App-V client.</p></td>
<td align="left"><p>See [Enable the App-V desktop client](appv-enable-the-app-v-desktop-client.md).</p></td>
</tr>
</tbody>
@ -194,7 +192,7 @@ Complete the following steps to upgrade each component of the App-V infrastructu
### Converting packages created using a prior version of App-V
Use the package converter utility to upgrade virtual application packages created using versions of App-V prior to App-V 5.0. The package converter uses PowerShell to convert packages and can help automate the process if you have many packages that require conversion.
Use the package converter utility to upgrade virtual application packages created using versions of App-V prior to App-V for Windows, version 1607. The package converter uses PowerShell to convert packages and can help automate the process if you have many packages that require conversion.
>**Note**  
App-V for Windows packages are exactly the same as App-V 5.0 packages. There has been no change in the package format between the versions and so there is no need to convert App-V 5.0 packages to App-V for Windows packages.
@ -225,7 +223,7 @@ The Management Console UI no longer requires Silverlight. The Management Console
<thead>
<tr class="header">
<th align="left">New in App-V for Windows</th>
<th align="left">Prior to App-V</th>
<th align="left">Prior to App-V for Windows</th>
</tr>
</thead>
<tbody>
@ -367,26 +365,26 @@ In the left pane of the Management Console, the OVERVIEW menu option and its ass
The following improvements have been made to the package editor in the App-V Sequencer.
### Import and export the manifest file
#### Import and export the manifest file
You can import and export the AppxManifest.xml file. To export the manifest file, select the **Advanced** tab and in the Manifest File box, click **Export...**. You can make changes to the manifest file, such as removing shell extensions or editing file type associations.
After you make your changes, click **Import...** and select the file you edited. After you successfully import it back in, the manifest file is immediately updated within the package editor.
**Caution**  
>**Caution**  
When you import the file, your changes are validated against the XML schema. If the file is not valid, you will receive an error. Be aware that it is possible to import a file that is validated against the XML schema, but that might still fail to run for other reasons.
 
### Addition of Windows 10 to operating systems list
#### Addition of Windows 10 to operating systems list
In the Deployment tab, Windows 10 32-bit and Windows 10-64 bit have been added to the list of operating systems for which you can sequence a package. If you select **Any Operating System**, Windows 10 is automatically included among the operating systems that the sequenced package will support.
### Current path displays at bottom of virtual registry editor
#### Current path displays at bottom of virtual registry editor
In the Virtual Registry tab, the path now displays at the bottom of the virtual registry editor, which enables you to determine the currently selected key. Previously, you had to scroll through the registry tree to find the currently selected key.
### <a href="" id="combined--find-and-replace--dialog-box-and-shortcut-keys-added-in-virtual-registry-editor"></a>Combined “find and replace” dialog box and shortcut keys added in virtual registry editor
#### <a href="" id="combined--find-and-replace--dialog-box-and-shortcut-keys-added-in-virtual-registry-editor"></a>Combined “find and replace” dialog box and shortcut keys added in virtual registry editor
In the virtual registry editor, shortcut keys have been added for the Find option (Ctrl+F), and a dialog box that combines the “find” and “replace” tasks has been added to enable you to find and replace values and data. To access this combined dialog box, select a key and do one of the following:
@ -398,19 +396,19 @@ In the virtual registry editor, shortcut keys have been added for the Find optio
Previously, the “Replace” dialog box did not exist, and you had to make changes manually.
### Rename registry keys and package files successfully
#### Rename registry keys and package files successfully
You can rename virtual registry keys and files without experiencing Sequencer issues. Previously, the Sequencer stopped working if you tried to rename a key.
### Import and export virtual registry keys
#### Import and export virtual registry keys
You can import and export virtual registry keys. To import a key, right-click the node under which to import the key, navigate to the key you want to import, and then click **Import**. To export a key, right-click the key and select **Export**.
### Import a directory into the virtual file system
#### Import a directory into the virtual file system
You can import a directory into the VFS. To import a directory, click the **Package Files** tab, and then click **View** &gt; **Virtual File System** &gt; **Import Directory**. If you try to import a directory that contains files that are already in the VFS, the import fails, and an explanatory message is displayed. Prior to App-V, you could not import directories.
### Import or export a VFS file without having to delete and then add it back to the package
#### Import or export a VFS file without having to delete and then add it back to the package
You can import files to or export files from the VFS without having to delete the file and then add it back to the package. For example, you might use this feature to export a change log to a local drive, edit the file using an external editor, and then re-import the file into the VFS.
@ -420,15 +418,15 @@ To import a file, select the **Package Files** tab and right-click the file that
After you import a file, you must save the package by clicking **File** &gt; **Save**.
### Menu for adding a package file has moved
#### Menu for adding a package file has moved
The menu option for adding a package file has been moved. To find the Add option, select the **Package Files** tab, then click **View** &gt; **Virtual File System** &gt; **Add File**. Previously, you right-clicked a folder under the VFS node, and chose **Add File**.
### Virtual registry node expands MACHINE and USER hives by default
#### Virtual registry node expands MACHINE and USER hives by default
When you open the virtual registry, the MACHINE and USER hives are shown below the top-level REGISTRY node. Previously, you had to expand the REGISTRY node to show the hives beneath.
### Enable or disable Browser Helper Objects
#### Enable or disable Browser Helper Objects
You can enable or disable Browser Helper Objects by selecting a new check box, Enable Browser Helper Objects, on the Advanced tab of the Sequencer user interface. If Browser Helper Objects:
@ -446,7 +444,7 @@ You can now use the package converter to convert App-V 4.6 packages that contain
For more information including examples, see [Migrating to App-V for Windows from a Previous Version](appv-migrating-to-appv-from-a-previous-version.md).
### <a href="" id="bkmk-supmultscripts"></a>Support for multiple scripts on a single event trigger
#### <a href="" id="bkmk-supmultscripts"></a>Support for multiple scripts on a single event trigger
App-V supports the use of multiple scripts on a single event trigger for App-V packages, including packages that you are converting from App-V 4.6 to App-V 5.0 or later. To enable the use of multiple scripts, App-V uses a script launcher application, named ScriptRunner.exe, which is installed as part of the App-V client installation.

46
windows/manage/appv-deploying-the-appv-server.md
View File

@ -14,24 +14,31 @@ You can install the App-V server features by using different deployment configur
For information about deploying the App-V Server, see [About App-V](appv-about-appv.md).
> [!IMPORTANT]
> Before you install and configure the App-V servers, you must specify a port where each component will be hosted. You must also add the associated firewall rules to allow incoming requests to access the specified ports. The installer does not modify firewall settings.
>**Important**<br>Before you install and configure the App-V servers, you must specify a port where each component will be hosted. You must also add the associated firewall rules to allow incoming requests to access the specified ports. The installer does not modify firewall settings.
## Download and install App-V Server components
## Download and install App-V server components
App-V offers the following five server components, each of which serves a specific purpose in an App-V environment. All five server components are included in the Microsoft Desktop Optimization Pack (MDOP) 2015 ISO package, which can be downloaded from the [Microsoft Developer Network (MSDN) subscription site](https://msdn.microsoft.com/en-us/subscriptions/downloads/default.aspx#FileId=65215). You must have a MSDN subscription to download MDOP.
App-V offers the following five server components, each of which serves a specific purpose in an App-V environment.
- **Management server**. Use the App-V management server and console to manage your App-V infrastructure. See [Administering App-V with the management console](appv-administering-virtual-applications-with-the-management-console.md) for more information about the management server.
- **Management server.** Use the App-V management server and console to manage your App-V infrastructure. See [Administering App-V with the management console](appv-administering-virtual-applications-with-the-management-console.md) for more information about the management server.
**Note**: If you are using App-V with your electronic software distribution solution, you don’t need to use the management server and console. However, you can still take advantage of the reporting and streaming capabilities in App-V.
>**Note**<br>If you are using App-V with your electronic software distribution solution, you don’t need to use the management server and console. However, you can still take advantage of the reporting and streaming capabilities in App-V.
- **Management database**. Use the App-V management database to facilitate database pre-deployments for App-V management. See [How to deploy the App-V server components](appv-deploy-the-appv-server.md) for more information about the management database.
- **Management database.** Use the App-V management database to facilitate database pre-deployments for App-V management. See [How to deploy the App-V server components](appv-deploy-the-appv-server.md) for more information about the management database.
- **Publishing server**. Use the App-V publishing server to host and stream virtual applications. The publishing server supports the HTTP and HTTPS protocols and does not require a database connection. See [How to install the App-V publishing server](appv-install-the-publishing-server-on-a-remote-computer.md) for more information about configuring the publishing server.
- **Publishing server.** Use the App-V publishing server to host and stream virtual applications. The publishing server supports the HTTP and HTTPS protocols and does not require a database connection. See [How to install the App-V publishing server](appv-install-the-publishing-server-on-a-remote-computer.md) for more information about configuring the publishing server.
- **Reporting server**. Use the App-V reporting server to generate reports that help you manage your App-V infrastructure. The reporting server requires a connection to the reporting database. See [About App-V reporting](appv-reporting.md) for more information about the reporting capabilities in App-V.
- **Reporting server.** Use the App-V reporting server to generate reports that help you manage your App-V infrastructure. The reporting server requires a connection to the reporting database. See [About App-V reporting](appv-reporting.md) for more information about the reporting capabilities in App-V.
- **Reporting database**. Use the App-V reporting database to facilitate database pre-deployments for App-V reporting. See [How to deploy the App-V server](appv-deploy-the-appv-server.md) for more information about the reporting database.
- **Reporting database.** Use the App-V reporting database to facilitate database pre-deployments for App-V reporting. See [How to deploy the App-V server](appv-deploy-the-appv-server.md) for more information about the reporting database.
All five App-V server components are included in the Microsoft Desktop Optimization Pack (MDOP) 2015 ISO package, which can be downloaded from:
- The [MSDN (Microsoft Developer Network) subscriptions site](https://msdn.microsoft.com/en-us/subscriptions/downloads/default.aspx#FileId=65215) You must have a MSDN subscription to download the MDOP ISO package from the MSDN subscriptions site.
- The [Volume Licensing Service Center](https://www.microsoft.com/en-us/licensing/default.aspx) if you're using [Windows 10 for Enterprise or Education](https://www.microsoft.com/en-us/WindowsForBusiness/windows-product-home).
>**Note**<br>If you're already using App-V 5.x, you don't need to re-deploy the App-V server components as they haven't changed since App-V 5.0 was released.
In large organizations, you might want to install more than one instance of the server components to get:
@ -42,34 +49,33 @@ In large organizations, you might want to install more than one instance of the
- Scalability to support a high load. For example, you can install additional servers behind a network load balancer.
## App-V standalone deployment
The App-V standalone deployment provides a good topology for a small deployment or a test environment. When you use this type of implementation, all server components are deployed to a single computer. The services and associated databases will compete for the resources on the computer that runs the App-V components. Therefore, you should not use this topology for larger deployments.
- [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)
## App-V Server distributed deployment
The distributed deployment topology can support a large App-V client base and it allows you to more easily manage and scale your environment. When you use this type of deployment, the App-V Server components are deployed across multiple computers, based on the structure and requirements of the organization.
- [How to Install the Management and Reporting Databases on Separate Computers from the Management and Reporting Services](appv-install-the-management-and-reporting-databases-on-separate-computers.md)
- [How to install the Management Server on a Standalone Computer and Connect it to the Database](appv-install-the-management-server-on-a-standalone-computer.md)
- [How to Deploy the App-V Server Using a Script](appv-deploy-the-appv-server-with-a-script.md)
- [How to Install the Publishing Server on a Remote Computer](appv-install-the-publishing-server-on-a-remote-computer.md)
- [How to install the Management Server on a Standalone Computer and Connect it to the Database](appv-install-the-management-server-on-a-standalone-computer.md)
## Using an Enterprise Software Distribution (ESD) solution and App-V
You can also deploy the App-V clients and packages by using an ESD without having to deploy App-V. The full capabilities for integration will vary depending on the ESD that you use.
> [!NOTE]
> The App-V reporting server and reporting database can still be deployed alongside the ESD to collect the reporting data from the App-V clients. However, the other three server components should not be deployed, because they will conflict with the ESD functionality.
>**Note**<br>The App-V reporting server and reporting database can still be deployed alongside the ESD to collect the reporting data from the App-V clients. However, the other three server components should not be deployed, because they will conflict with the ESD functionality.
[Deploying App-V Packages by Using Electronic Software Distribution (ESD)](appv-deploying-packages-with-electronic-software-distribution-solutions.md)
## App-V Server logs
You can use App-V server log information to help troubleshoot the server installation and operational events while using App-V. The server-related log information can be reviewed with the **Event Viewer**. The following line displays the specific path for Server-related events:
**Event Viewer \\ Applications and Services Logs \\ Microsoft \\ App V**
@ -79,7 +85,6 @@ Associated setup logs are saved in the following directory:
**%temp%**
## App-V reporting
App-V reporting allows App-V clients to collect data and then send it back to be stored in a central repository. You can use this information to get a better view of the virtual application usage within your organization. The following list displays some of the types of information the App-V client collects:
- Information about the computer that runs the App-V client.
@ -92,13 +97,10 @@ The reporting information will be maintained until it is successfully sent to th
If you want to retrieve report information, you must use Microsoft SQL Server Reporting Services (SSRS) which is available with Microsoft SQL. SSRS is not installed when you install the App-V reporting server and it must be deployed separately to generate the associated reports.
For more information, see [About App-V Reporting](appv-reporting.md) and [How to Enable Reporting on the App-V Client by Using PowerShell](appv-enable-reporting-on-the-appv-client-with-powershell.md).
## Other resources for the App-V server
- [Deploying App-V](appv-deploying-appv.md)
## 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).
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).

9
windows/manage/appv-getting-started.md
View File

@ -11,13 +11,14 @@ ms.prod: w10
# Getting Started with App-V
Microsoft Application Virtualization (App-V) enables organizations to deliver Win32 applications to users as virtual applications. Virtual applications are installed on centrally managed servers and delivered to users as a service – in real time and on as as-needed basis. Users launch virtual applications from familiar access points, including the Windows Store, and interact with them as if they were installed locally.
Microsoft Application Virtualization (App-V) enables organizations to deliver Win32 applications to users as virtual applications. Virtual applications are installed on centrally managed servers and delivered to users as a service – in real time and on as as-needed basis. Users launch virtual applications from familiar access points and interact with them as if they were installed locally.
With the release of Windows 10, version 1607, App-V is included with the [Windows 10 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).
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).
If you’re already using App-V, performing an in-place upgrade to Windows 10 on user devices automatically installs the App-V client and migrates users’ App-V applications and settings. For more information about how to configure an existing App-V installation after upgrading user devices to Windows 10, see [Upgrading to App-V for Windows 10 from an existing installation](appv-upgrading-to-app-v-for-windows-10-from-an-existing-installation.md).
Important: You can migrate your existing App-V installation to Windows 10 from App-V versions 5.0 SP2 and higher only. If you are using an earlier version of App-V, you’ll need to upgrade from that version to App-V 5.0 SP2 before you upgrade to Windows 10.
>**Important**
You can upgrade your existing App-V installation to App-V for Windows from App-V versions 5.0 SP2 and higher only. If you are using an earlier version of App-V, you’ll need to upgrade from that version to App-V 5.0 SP2 before you upgrade.
For information about previous versions of App-V, see [MDOP Information Experience](https://technet.microsoft.com/itpro/mdop/index).
@ -31,7 +32,7 @@ To start using App-V to deliver virtual applications to users, you’ll need to
|------------|--|------|
| App-V server components | App-V offers five server components that work together to allow you to host and publish virtual applications, generate usage reports, and manage your App-V environment. For information about the server components, see [Deploying the App-V Server](#_Deploying_the_App-V). | The App-V server components are included in the Microsoft Desktop Optimization Pack (MDOP) 2015 ISO package, which can be downloaded from the [MSDN (Microsoft Developer Network) subscriptions site](https://msdn.microsoft.com/en-us/subscriptions/downloads/default.aspx#FileId=65215). <br>You must have a MSDN subscription to download the MDOP ISO package.<br>See [Deploying the App-V Server](appv-deploying-the-appv-server.md) for more information about installing and using the server components. |
| App-V client and App-V Remote Desktop Services (RDS) client | 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 App-V client is automatically installed with Windows 10. <br>For information about enabling the client, see [Enable the App-V desktop client](appv-enable-the-app-v-desktop-client.md). |
| App-V Sequencer | Use the App-V Sequencer to convert Win32 applications into virtual packages for deployment to user devices. Devices must be running the App-V client to allow users to interact with virtual applications. | Installed with the [Windows 10 Assessment and Deployment Kit](https://developer.microsoft.com/en-us/windows/hardware/windows-assessment-deployment-kit) (Windows ADK). |
| App-V sequencer | Use the App-V sequencer to convert Win32 applications into virtual packages for deployment to user devices. Devices must be running the App-V client to allow users to interact with virtual applications. | Installed with the [Windows Assessment and Deployment kit (ADK) for Windows 10, version 1607](https://developer.microsoft.com/en-us/windows/hardware/windows-assessment-deployment-kit). |
For more information about these elements, see [High Level Architecture for App-V](appv-high-level-architecture.md).

14
windows/manage/appv-release-notes-for-appv-for-windows.md
View File

@ -9,32 +9,32 @@ ms.prod: w10
---
# Release Notes for App-V
# Release Notes for App-V for Windows 10, version 1607
Applies to: Windows 10, version 1607
The following are known issues in Microsoft Application Virtualization (App-V).
Review these known issues in Microsoft Application Virtualization (App-V) for Windows.
## Error occurs during publishing refresh between App-V 5.0 SP3 Management Server and App-V Client on Windows 10
An error is generated during publishing refresh when synchronizing packages from the App-V 5.0 SP3 management server to an App-V client on Windows 10 . This error occurs because the App-V 5.0 SP3 server does not understand the Windows 10 operating system that is specified in the publishing URL. The issue is fixed for App-V publishing server, but is not backported to versions of App-V 5.0 SP3 or earlier.
**Workaround**: Upgrade the App-V 5.0 Management server to the App-V Management server for Windows 10 Clients.
**Workaround**: Upgrade the App-V 5.0 management server to the App-V management server for Windows 10 clients.
## Custom configurations do not get applied for packages that will be published globally if they are set using the App-V Server
If you assign a package to an AD group that contains machine accounts and apply a custom configuration to that group using the App-V Server, the custom configuration will not be applied to those machines. The App-V Client will publish packages assigned to a machine account globally. However, it stores custom configuration files per user in each user’s profile. Globally published packages will not have access to this custom configuration.
**Workaround**: Do one of the following:
- Assign the package to groups containing only user accounts. This will ensure that the package’s custom configuration will be stored in each user’s profile and will be applied correctly.
- Assign the package to groups containing only user accounts. This will ensure that the package’s custom configuration is stored in each user’s profile and will be applied correctly.
- Create a custom deployment configuration file and apply it to the package on the client using the Add-AppvClientPackage cmdlet with the –DynamicDeploymentConfiguration parameter. See [About App-V Dynamic Configuration](appv-dynamic-configuration.md) for more information.
- Create a new package with the custom configuration using the App-V Sequencer.
- Create a new package with the custom configuration using the App-V sequencer.
## Server files not deleted after new App-V Server installation
## Server files not deleted after new App-V for Windows server installation
If you uninstall the App-V 5.0 SP1 Server and then install the App-V Server, the installation fails, the wrong version of the Management server is installed, and an error message is returned. The issue occurs because the Server files are not being deleted when you uninstall App-V 5.0 SP1, so the installation process does an upgrade instead of a new installation.

6
windows/manage/change-history-for-manage-and-update-windows-10.md
View File

@ -13,6 +13,12 @@ author: jdeckerMS
This topic lists new and updated topics in the [Manage and update Windows 10](index.md) documentation for [Windows 10 and Windows 10 Mobile](../index.md).
## August 2016
| New or changed topic | Description |
| --- | --- |
| [Configure Windows 10 taskbar](configure-windows-10-taskbar.md) | Updated sample XML for combined Start and taskbar layout |
## RELEASE: Windows 10, version 1607
The topics in this library have been updated for Windows 10, version 1607 (also known as the Anniversary Update). The following new topics have been added:

11
windows/manage/configure-windows-10-taskbar.md
View File

@ -62,7 +62,6 @@ The easiest way to find this data for an application is to:
xmlns:start="http://schemas.microsoft.com/Start/2014/StartLayout"
xmlns:taskbar="http://schemas.microsoft.com/Start/2014/TaskbarLayout"
Version="1">
<CustomTaskbarLayoutCollection>
<defaultlayout:TaskbarLayout>
<taskbar:TaskbarPinList>
@ -76,7 +75,14 @@ The easiest way to find this data for an application is to:
### Sample taskbar configuration added to Start layout XML
```xml
<LayoutModificationTemplate Version="1" xmlns="http://schemas.microsoft.com/Start/2014/LayoutModification">
<?xml version="1.0" encoding="utf-8"?>
<LayoutModificationTemplate
xmlns="http://schemas.microsoft.com/Start/2014/LayoutModification"
xmlns:defaultlayout="http://schemas.microsoft.com/Start/2014/FullDefaultLayout"
xmlns:start="http://schemas.microsoft.com/Start/2014/StartLayout"
xmlns:taskbar="http://schemas.microsoft.com/Start/2014/TaskbarLayout"
Version="1">
<LayoutOptions StartTileGroupCellWidth="6" StartTileGroupsColumnCount="1" />
<DefaultLayoutOverride>
<StartLayoutCollection>
<defaultlayout:StartLayout GroupCellWidth="6" xmlns:defaultlayout="http://schemas.microsoft.com/Start/2014/FullDefaultLayout">
@ -87,6 +93,7 @@ The easiest way to find this data for an application is to:
</start:Group>
</defaultlayout:StartLayout>
</StartLayoutCollection>
</DefaultLayoutOverride>
<CustomTaskbarLayoutCollection>
<defaultlayout:TaskbarLayout>
<taskbar:TaskbarPinList>

1
windows/manage/distribute-apps-from-your-private-store.md
View File

@ -7,6 +7,7 @@ ms.mktglfcycl: manage
ms.sitesec: library
ms.pagetype: store
author: TrudyHa
localizationpriority: high
---
# Distribute apps using your private store

1
windows/manage/manage-cortana-in-enterprise.md
View File

@ -6,6 +6,7 @@ ms.prod: w10
ms.mktglfcycl: manage
ms.sitesec: library
author: eross-msft
localizationpriority: high
---
# Cortana integration in your business or enterprise

2
windows/manage/manage-wifi-sense-in-enterprise.md
View File

@ -8,7 +8,7 @@ ms.mktglfcycl: manage
ms.sitesec: library
ms.pagetype: mobile
author: eross-msft
localizationpriority: high
localizationpriority: medium
---
# Manage Wi-Fi Sense in your company

1
windows/manage/settings-reference-windows-store-for-business.md
View File

@ -7,6 +7,7 @@ ms.mktglfcycl: manage
ms.sitesec: library
ms.pagetype: store
author: TrudyHa
localizationpriority: high
---
# Settings reference: Windows Store for Business

1
windows/manage/windows-store-for-business-overview.md
View File

@ -7,6 +7,7 @@ ms.pagetype: store, mobile
ms.mktglfcycl: manage
ms.sitesec: library
author: TrudyHa
localizationpriority: high
---
# Windows Store for Business overview