mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-18 20:03:40 +00:00
Merge remote-tracking branch 'refs/remotes/origin/master' into jd-sandbox
This commit is contained in:
jdeckerMS
@ -35,8 +35,9 @@
|
||||
#### [Windows Information Protection (WIP) overview](wip-enterprise-overview.md)
|
||||
#### [Mandatory tasks and settings required to turn on Windows Information Protection (WIP)](mandatory-settings-for-wip.md)
|
||||
#### [Enlightened apps for use with Windows Information Protection (WIP)](enlightened-microsoft-apps-and-wip.md)
|
||||
#### [Testing scenarios for Windows Information Protection](testing-scenarios-for-wip.md)
|
||||
#### [Testing scenarios for Windows Information Protection (WIP)](testing-scenarios-for-wip.md)
|
||||
## [Use Windows Event Forwarding to help with intrusion detection](use-windows-event-forwarding-to-assist-in-instrusion-detection.md)
|
||||
## [Override Process Mitigation Options to help enforce app-related security policies](override-mitigation-options-for-app-related-security-policies.md)
|
||||
## [VPN profile options](vpn-profile-options.md)
|
||||
## [Windows security baselines](windows-security-baselines.md)
|
||||
## [Security technologies](security-technologies.md)
|
||||
|
||||
@ -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
|
||||
|
||||
@ -12,6 +12,9 @@ author: brianlic-msft
|
||||
# Change history for Keep Windows 10 secure
|
||||
This topic lists new and updated topics in the [Keep Windows 10 secure](index.md) documentation for [Windows 10 and Windows 10 Mobile](../index.md).
|
||||
|
||||
## August 2016
|
||||
- [Override Process Mitigation Options to help enforce app-related security policies](override-mitigation-options-for-app-related-security-policies.md) |New |
|
||||
|
||||
## 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:
|
||||
|
||||
@ -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
|
||||
|
||||
@ -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
|
||||
|
||||
@ -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
|
||||
|
||||
@ -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
|
||||
|
||||
@ -6,6 +6,7 @@ ms.prod: w10
|
||||
ms.mktglfcycl: explore
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
localizationpriority: high
|
||||
author: brianlic-msft
|
||||
---
|
||||
# Protect derived domain credentials with Credential Guard
|
||||
@ -115,6 +116,11 @@ The PC must meet the following hardware and software requirements to use Credent
|
||||
<td align="left"><p>Virtual machine</p></td>
|
||||
<td align="left"><p>For PCs running Windows 10, version 1607, you can run Credential Guard on a Generation 2 virtual machine.</p></td>
|
||||
</tr>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Hypervisor</p></td>
|
||||
<td align="left"><p>You must use the Windows hypervisor.</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
@ -4,6 +4,7 @@ description: This article describes how to deploy catalog files to support code
|
||||
keywords: virtualization, security, malware
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
localizationpriority: high
|
||||
author: brianlic-msft
|
||||
---
|
||||
|
||||
|
||||
@ -4,6 +4,7 @@ description: This article provides information about two elements in code integr
|
||||
keywords: virtualization, security, malware
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
localizationpriority: high
|
||||
author: brianlic-msft
|
||||
---
|
||||
|
||||
|
||||
@ -4,6 +4,7 @@ description: This article describes how to deploy code integrity policies, one o
|
||||
keywords: virtualization, security, malware
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
localizationpriority: high
|
||||
author: brianlic-msft
|
||||
---
|
||||
|
||||
|
||||
@ -4,6 +4,7 @@ description: This article, and the articles it links to, describe how to create
|
||||
keywords: virtualization, security, malware
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
localizationpriority: high
|
||||
author: brianlic-msft
|
||||
---
|
||||
|
||||
|
||||
@ -4,6 +4,7 @@ description: This article describes how to enable virtualization-based security,
|
||||
keywords: virtualization, security, malware
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
localizationpriority: high
|
||||
author: brianlic-msft
|
||||
---
|
||||
|
||||
|
||||
@ -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
|
||||
|
||||
@ -5,6 +5,7 @@ ms.assetid: 4BA52AA9-64D3-41F3-94B2-B87EC2717486
|
||||
keywords: virtualization, security, malware
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
localizationpriority: high
|
||||
author: brianlic-msft
|
||||
---
|
||||
|
||||
|
||||
@ -32,7 +32,7 @@ Since the stakes are higher in an enterprise environment, the potential disaster
|
||||
|
||||
##Enable PUA protection in SCCM and Intune
|
||||
|
||||
The PUA feature is available for enterprise users who are running System Center Configuration Manager (SCCM) or Microsoft Intune in their infrastructure.
|
||||
The PUA feature is available for enterprise users who are running System Center Configuration Manager (SCCM) or Intune in their infrastructure.
|
||||
|
||||
###Configure PUA in SCCM
|
||||
|
||||
@ -53,10 +53,8 @@ You can use PowerShell to detect PUA without blocking them. In fact, you can run
|
||||
a. Click **Start**, type **powershell**, and press **Enter**.
|
||||
|
||||
b. Click **Windows PowerShell** to open the interface.
|
||||
|
||||
> [!NOTE]
|
||||
> You may need to open an administrator-level version of PowerShell. Right-click the item in the Start menu, click **Run as administrator** and click **Yes** at the permissions prompt.
|
||||
|
||||
2. Enter the PowerShell command:
|
||||
|
||||
```text
|
||||
@ -89,15 +87,12 @@ You can find a complete list of the Microsoft antimalware event IDs, the symbol,
|
||||
|
||||
##What PUA notifications look like
|
||||
|
||||
When a detection occurs, end users who enabled the PUA detection feature will see the following notification:<br>
|
||||
When a detection occurs, end users who enabled the PUA detection feature will see the following notification:
|
||||
|
||||
|
||||
|
||||
To see historical PUA detections that occurred on a PC, users can go to History, then **Quarantined items** or **All detected items**.<br>
|
||||
To see historical PUA detections that occurred on a PC, users can go to History, then **Quarantined items** or **All detected items**.
|
||||
|
||||
|
||||
|
||||
##PUA threat file-naming convention
|
||||
##PUA threat naming convention
|
||||
|
||||
When enabled, potentially unwanted applications are identified with threat names that start with “PUA:”, such as, PUA:Win32/Creprote.
|
||||
|
||||
@ -105,6 +100,5 @@ When enabled, potentially unwanted applications are identified with threat names
|
||||
|
||||
PUA protection quarantines the file so they won’t run. PUA will be blocked only at download or install-time. A file will be included for blocking if it has been identified as PUA and meets one of the following conditions:
|
||||
* The file is being scanned from the browser
|
||||
* The file has [Mark of the Web](https://msdn.microsoft.com/en-us/library/ms537628%28v=vs.85%29.aspx) set
|
||||
* The file is in the %downloads% folder
|
||||
* Or if the file in the %temp% folder
|
||||
|
||||
@ -8,13 +8,14 @@ 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)
|
||||
# List of enlightened Microsoft apps for use with Windows Information Protection (WIP)
|
||||
|
||||
**Applies to:**
|
||||
|
||||
- Windows 10, version 6017
|
||||
- Windows 10, version 1607
|
||||
- Windows 10 Mobile
|
||||
|
||||
Learn the difference between enlightened and unenlightened apps, and then review the list of enlightened apps provided by Microsoft along with the text you will need to use to add them to your allowed apps list.
|
||||
|
||||
@ -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)
|
||||
@ -21,6 +22,7 @@ This section includes info about the enlightened Microsoft apps, including how t
|
||||
## In this section
|
||||
|Topic |Description |
|
||||
|------|------------|
|
||||
|[Windows Information Protection (WIP) overview](wip-enterprise-overview.md) |High-level overview info about why to use WIP, the enterprise scenarios, and how to turn it off. |
|
||||
|[Mandatory settings for Windows Information Protection (WIP)](mandatory-settings-for-wip.md) |A list of all of the tasks and settings that are required for the operating system to turn on Windows Information Protection (WIP), formerly known as Windows Information Protection (WIP), in your enterprise. |
|
||||
|[Enlightened apps for use with Windows Information Protection (WIP)](enlightened-microsoft-apps-and-wip.md) |Learn the difference between enlightened and unenlightened apps, and then review the list of enlightened apps provided by Microsoft along with the text you will need to use to add them to your allowed apps list. |
|
||||
|[Testing scenarios for Windows Information Protection (WIP)](testing-scenarios-for-wip.md) |We've come up with a list of suggested testing scenarios that you can use to test WIP in your company. |
|
||||
Binary file not shown.
|
After Width: | Height: | Size: 3.7 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 20 KiB |
BIN
windows/keep-secure/images/gp-process-mitigation-options.png
Normal file
BIN
windows/keep-secure/images/gp-process-mitigation-options.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 136 KiB |
@ -25,6 +25,7 @@ Learn about keeping Windows 10 and Windows 10 Mobile secure.
|
||||
| [Protect Remote Desktop credentials with Remote Credential Guard](remote-credential-guard.md) | Remote Credential Guard helps you protect your credentials over a Remote Desktop connection by redirecting the Kerberos requests back to the device that's requesting the connection. |
|
||||
| [Protect your enterprise data using Windows Information Protection (WIP)](protect-enterprise-data-using-wip.md) | With the increase of employee-owned devices in the enterprise, there’s also an increasing risk of accidental data leak through apps and services, like email, social media, and the public cloud, which are outside of the enterprise’s control. For example, when an employee sends the latest engineering pictures from their personal email account, copies and pastes product info into a tweet, or saves an in-progress sales report to their public cloud storage. |
|
||||
| [Use Windows Event Forwarding to help with intrusion detection](use-windows-event-forwarding-to-assist-in-instrusion-detection.md) | Learn about an approach to collect events from devices in your organization. This article talks about events in both normal operations and when an intrusion is suspected. |
|
||||
|[Override Process Mitigation Options to help enforce app-related security policies](override-mitigation-options-for-app-related-security-policies.md) |Use Group Policy to override individual **Process Mitigation Options** settings and help to enforce specific app-related security policies. |
|
||||
| [VPN profile options](vpn-profile-options.md) | Virtual private networks (VPN) let you give your users secure remote access to your company network. Windows 10 adds useful new VPN profile options to help you manage how users connect. |
|
||||
| [Windows security baselines](windows-security-baselines.md) | Learn why you should use security baselines in your organization. |
|
||||
| [Security technologies](security-technologies.md) | Learn more about the different security technologies that are available in Windows 10 and Windows 10 Mobile. |
|
||||
|
||||
@ -4,6 +4,7 @@ description: Microsoft Device Guard is a feature set that consists of both hardw
|
||||
keywords: virtualization, security, malware
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
localizationpriority: high
|
||||
author: brianlic-msft
|
||||
---
|
||||
|
||||
|
||||
@ -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)
|
||||
|
||||
@ -4,6 +4,7 @@ description: This article describes how to create a code signing certificate for
|
||||
keywords: virtualization, security, malware
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
localizationpriority: high
|
||||
author: brianlic-msft
|
||||
---
|
||||
|
||||
|
||||
@ -0,0 +1,58 @@
|
||||
|
||||
---
|
||||
title: Override Process Mitigation Options to help enforce app-related security policies (Windows 10)
|
||||
description: How to use Group Policy to override individual Process Mitigation Options settings and to help enforce specific app-related security policies.
|
||||
keywords: Process Mitigation Options, Mitigation Options, Group Policy Mitigation Options
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
ms.pagetype: security
|
||||
ms.sitesec: library
|
||||
---
|
||||
|
||||
|
||||
# Override Process Mitigation Options to help enforce app-related security policies
|
||||
|
||||
**Applies to:**
|
||||
|
||||
- Windows 10, version 1607
|
||||
- Windows Server 2016
|
||||
|
||||
Use Group Policy to override individual **Process Mitigation Options** settings and help to enforce specific app-related security policies.
|
||||
|
||||
**To modify Process Mitigation Options**
|
||||
|
||||
1. Open your Group Policy editor and go to the **Administrative Templates\System\Mitigation Options\Process Mitigation Options** setting.
|
||||
|
||||
|
||||
|
||||
2. Click **Enabled**, and then in the **Options** area, click **Show** to open the **Show Contents** box, where you’ll be able to add your apps and the appropriate bit flag values, as shown in the [Setting the bit field](#setting-the-bit-field) and [Example](#example) sections of this topic.
|
||||
|
||||
**Important**<br>For each app you want to include, you must include:
|
||||
|
||||
- **Value name.** The app file name, including the extension. For example, iexplore.exe.
|
||||
- **Value.** A bit field with a series of bit flags in particular positions. Bits can be set to 0 (where the setting is forced off), 1 (where the setting is forced on), or ? (where the setting retains the previous, existing value).
|
||||
|
||||
**Note**<br>Setting bit flags in positions not specified here to anything other than ? might cause undefined behavior.
|
||||
|
||||
|
||||
|
||||
## Setting the bit field
|
||||
Here’s a visual representation of the bit flag locations for the various Process Mitigation Options settings:
|
||||
|
||||
|
||||
|
||||
Where the bit flags are read from right to left and are defined as:
|
||||
|
||||
|Flag |Bit location |Setting |Details |
|
||||
|-----|--------------|--------|--------|
|
||||
|A |0 |`PROCESS_CREATION_MITIGATION_POLICY_DEP_ENABLE (0x00000001)` |Turns on Data Execution Prevention (DEP) for child processes. |
|
||||
|B |1 |`PROCESS_CREATION_MITIGATION_POLICY_DEP_ATL_THUNK_ENABLE (0x00000002)` |Turns on DEP-ATL thunk emulation for child processes. DEP-ATL thunk emulation lets the system intercept non-executable (NX) faults that originate from the Active Template Library (ATL) thunk layer, and then emulate and handle the instructions so the process can continue to run. |
|
||||
|C |2 |`PROCESS_CREATION_MITIGATION_POLICY_SEHOP_ENABLE (0x00000004)` |Turns on Structured Exception Handler Overwrite Protection (SEHOP) for child processes. SEHOP helps to block exploits that use the Structured Exception Handler (SEH) overwrite technique. |
|
||||
|D |8 |`PROCESS_CREATION_MITIGATION_POLICY_FORCE_RELOCATE_IMAGES_ALWAYS_ON (0x00000100)` |Uses the force Address Space Layout Randomization (ASLR) setting to act as though an image base collision happened at load time, forcibly rebasing images that aren’t dynamic base compatible. Images without the base relocation section won’t be loaded if relocations are required. |
|
||||
|E |15 |`PROCESS_CREATION_MITIGATION_POLICY_BOTTOM_UP_ASLR_ALWAYS_ON (0x00010000)` |Turns on the bottom-up randomization policy, which includes stack randomization options and causes a random location to be used as the lowest user address. |
|
||||
|F |16 |`PROCESS_CREATION_MITIGATION_POLICY_BOTTOM_UP_ASLR_ALWAYS_OFF (0x00020000)` |Turns off the bottom-up randomization policy, which includes stack randomization options and causes a random location to be used as the lowest user address. |
|
||||
|
||||
## Example
|
||||
If you want to turn on the **PROCESS_CREATION_MITIGATION_POLICY_DEP_ENABLE** and **PROCESS_CREATION_MITIGATION_POLICY_FORCE_RELOCATE_IMAGES_ALWAYS_ON** settings, turn off the **PROCESS_CREATION_MITIGATION_POLICY_BOTTOM_UP_ASLR_ALWAYS_OFF** setting, and leave everything else as the default values, you’d want to type a value of `???????????????0???????1???????1`.
|
||||
|
||||
|
||||
@ -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
|
||||
|
||||
@ -4,6 +4,7 @@ description: To help you plan and begin the initial test stages of a deployment
|
||||
keywords: virtualization, security, malware
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
localizationpriority: high
|
||||
author: brianlic-msft
|
||||
---
|
||||
|
||||
|
||||
@ -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)
|
||||
@ -16,7 +17,7 @@ author: eross-msft
|
||||
- Windows 10, version 1607
|
||||
- Windows 10 Mobile
|
||||
|
||||
With the increase of employee-owned devices in the enterprise, there’s also an increasing risk of accidental data leak through apps and services, like email, social media, and the public cloud, which are outside of the enterprise’s control. For example, when an employee sends the latest engineering pictures to their personal email account, copies and pastes product info into a tweet, or saves an in-progress sales report to their public cloud storage.
|
||||
With the increase of employee-owned devices in the enterprise, there’s also an increasing risk of accidental data leak through apps and services, like email, social media, and the public cloud, which are outside of the enterprise’s control. For example, when an employee sends the latest engineering pictures from their personal email account, copies and pastes product info into a tweet, or saves an in-progress sales report to their public cloud storage.
|
||||
|
||||
Windows Information Protection (WIP) helps to protect against this potential data leakage without otherwise interfering with the employee experience. WIP also helps to protect enterprise apps and data against accidental data leak on enterprise-owned devices and personal devices that employees bring to work without requiring changes to your environment or other apps. Finally, another data protection technology, Azure Rights Management also works alongside WIP to extend data protection for data that leaves the device, such as when email attachments are sent from an enterprise aware version of a rights management mail client.
|
||||
|
||||
|
||||
@ -4,6 +4,7 @@ description: To help you plan a deployment of Microsoft Device Guard, this artic
|
||||
keywords: virtualization, security, malware
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
localizationpriority: high
|
||||
author: brianlic-msft
|
||||
---
|
||||
|
||||
|
||||
@ -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)
|
||||
|
||||
@ -5,6 +5,7 @@ ms.prod: w10
|
||||
ms.mktglfcycl: explore
|
||||
ms.sitesec: library
|
||||
ms.pagetype: security
|
||||
localizationpriority: high
|
||||
---
|
||||
|
||||
# Windows Information Protection (WIP) overview
|
||||
|
||||
@ -36,7 +36,7 @@
|
||||
## [Configure devices without MDM](configure-devices-without-mdm.md)
|
||||
## [Windows 10 servicing options](introduction-to-windows-10-servicing.md)
|
||||
## [Application development for Windows as a service](application-development-for-windows-as-a-service.md)
|
||||
## [Application Virtualization for Windows (App-V)](appv-for-windows.md)
|
||||
## [Application Virtualization (App-V) for Windows](appv-for-windows.md)
|
||||
### [Getting Started with App-V](appv-getting-started.md)
|
||||
#### [About App-V](appv-about-appv.md)
|
||||
##### [Release Notes for App-V](appv-release-notes-for-appv-for-windows.md)
|
||||
@ -133,7 +133,7 @@
|
||||
#### [Application Publishing and Client Interaction](appv-application-publishing-and-client-interaction.md)
|
||||
#### [Viewing App-V Server Publishing Metadata](appv-viewing-appv-server-publishing-metadata.md)
|
||||
#### [Running a Locally Installed Application Inside a Virtual Environment with Virtualized Applications](appv-running-locally-installed-applications-inside-a-virtual-environment.md)
|
||||
## [User Experience Virtualization (UE-V)](uev-for-windows.md)
|
||||
## [User Experience Virtualization (UE-V) for Windows](uev-for-windows.md)
|
||||
### [Get Started with UE-V](uev-getting-started.md)
|
||||
#### [What's New in UE-V for Windows 10, version 1607](uev-whats-new-in-uev-for-windows.md)
|
||||
#### [User Experience Virtualization Release Notes](uev-release-notes-1607.md)
|
||||
|
||||
@ -9,10 +9,11 @@ ms.prod: w10
|
||||
---
|
||||
|
||||
|
||||
# About App-V
|
||||
# About App-V for Windows
|
||||
|
||||
Applies to: Windows 10, version 1607
|
||||
|
||||
Use the following sections to review information about significant changes that apply to Application Virtualization (App-V):
|
||||
Review the following sections for information about significant changes that apply to Application Virtualization (App-V) for Windows:
|
||||
|
||||
[App-V software prerequisites and supported configurations](#bkmk-51-prereq-configs)
|
||||
|
||||
@ -32,10 +33,10 @@ Use the following sections to review information about significant changes that
|
||||
|
||||
[Hardcoded path to installation folder is redirected to virtual file system root](#bkmk-hardcodepath)
|
||||
|
||||
## <a href="" id="bkmk-51-prereq-configs"></a>App-V software prerequisites and supported configurations
|
||||
## <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 software prerequisites and supported configurations.
|
||||
Review the following topics for information about App-V for Windows software prerequisites and supported configurations.
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
@ -44,32 +45,31 @@ See the following links for the App-V software prerequisites and supported confi
|
||||
</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>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>[App-V Prerequisites](appv-prerequisites.md)</p></td>
|
||||
<td align="left"><p>Prerequisite software that you must install before starting the App-V installation</p></td>
|
||||
<td align="left"><p>Prerequisite software that you must install before you can get started with App-V for Windows</p></td>
|
||||
</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.
|
||||
|
||||
**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 and Configuration Manager.
|
||||
|
||||
## <a href="" id="bkmk-migrate-to-51"></a>Migrating to App-V
|
||||
## <a href="" id="bkmk-migrate-to-51"></a>Upgrade to App-V for Windows
|
||||
|
||||
|
||||
Use the following information to upgrade to App-V 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:
|
||||
|
||||
@ -102,33 +102,29 @@ 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 more information, see:</p>
|
||||
<ul>
|
||||
<li><p>“Differences between App-V 4.6 and App-V 5.0” in [About App-V 5.0](https://technet.microsoft.com/en-us/itpro/mdop/appv-v5/about-app-v-50.md)</p></li>
|
||||
<li><p>[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>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Upgrading from App-V 5.0 or later</p></td>
|
||||
<td align="left"><p>You can upgrade to App-V directly from any of the following versions:</p>
|
||||
<td align="left"><p>You can upgrade to App-V for Windows directly from any of the following versions:</p>
|
||||
<ul>
|
||||
<li><p>App-V 5.0</p></li>
|
||||
<li><p>App-V 5.0 SP1</p></li>
|
||||
<li><p>App-V 5.0 SP2</p></li>
|
||||
<li><p>App-V 5.0 SP3</p></li>
|
||||
</ul>
|
||||
<p>To upgrade to App-V, follow the steps in the remaining sections of this topic.</p>
|
||||
<p>Packages and connection groups will continue to work with App-V as they currently do.</p></td>
|
||||
<p>To upgrade to App-V for Windows, follow the steps in the remaining sections of this topic.</p>
|
||||
<p>Packages and connection groups will continue to work with App-V for Windows as they currently do.</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
### <a href="" id="bkmk-steps-upgrd-infrastruc"></a>Steps to upgrade the App-V infrastructure
|
||||
|
||||
Complete the following steps to upgrade each component of the App-V infrastructure to App-V. The following order is only a suggestion; you may upgrade components in any order.
|
||||
Complete the following steps to upgrade each component of the App-V infrastructure to App-V for Windows. The following order is only a suggestion; you can upgrade components in any order.
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
@ -143,17 +139,17 @@ 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>
|
||||
|
||||
</div></td>
|
||||
<td align="left"><p>Follow these steps:</p>
|
||||
<ol>
|
||||
<li><p>Do one of the following, depending on the method you are using to upgrade the Management database and/or Reporting database:</p>
|
||||
<li><p>Do one of the following, depending on the method you are using to upgrade the management database and/or reporting database:</p>
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="50%" />
|
||||
@ -168,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>
|
||||
@ -176,17 +172,17 @@ 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 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>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Step 2: Upgrade the App-V Sequencer.</p></td>
|
||||
<td align="left"><p>Step 2: Install the new App-V for Windows sequencer.</p></td>
|
||||
<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: Enabled the 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>
|
||||
@ -196,63 +192,26 @@ 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 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 packages.
|
||||
>**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.
|
||||
|
||||
|
||||
|
||||
## <a href="" id="bkmk-whatsnew"></a>What’s New in App-V
|
||||
|
||||
|
||||
These sections are for users who are already familiar with App-V and want to know what has changed in App-V. If you are not already familiar with App-V, you should start by reading [Planning for App-V](appv-planning-for-appv.md).
|
||||
These sections are for users who are already familiar with App-V and want to know what has changed in App-V for Windows. If you are not already familiar with App-V, you should start by reading [Planning for App-V](appv-planning-for-appv.md).
|
||||
|
||||
### <a href="" id="bkmk-win10support"></a>App-V support for Windows 10
|
||||
|
||||
The following table lists the Windows 10 support for App-V. Windows 10 is not supported in versions of App-V prior to App-V.
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
<col width="33%" />
|
||||
<col width="33%" />
|
||||
<col width="33%" />
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">Component</th>
|
||||
<th align="left">App-V</th>
|
||||
<th align="left">App-V 5.0</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>App-V Client</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>App-V RDS Client</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>App-V Sequencer</p></td>
|
||||
<td align="left"><p>Yes</p></td>
|
||||
<td align="left"><p>No</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
### <a href="" id="bkmk-mgmtconsole"></a>App-V Management Console Changes
|
||||
|
||||
This section compares the App-V Management Console’s current and previous functionality.
|
||||
This section compares the App-V for Windows Management Console’s current and previous functionality.
|
||||
|
||||
### Silverlight is no longer required
|
||||
|
||||
The Management Console UI no longer requires Silverlight. The 5.1 Management Console is built on HTML5 and Javascript.
|
||||
The Management Console UI no longer requires Silverlight. The Management Console is built on HTML5 and Javascript.
|
||||
|
||||
### Notifications and messages are displayed individually in a dialog box
|
||||
|
||||
@ -263,8 +222,8 @@ The Management Console UI no longer requires Silverlight. The 5.1 Management Con
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">New in App-V</th>
|
||||
<th align="left">Prior to App-V</th>
|
||||
<th align="left">New in App-V for Windows</th>
|
||||
<th align="left">Prior to App-V for Windows</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
@ -300,8 +259,8 @@ The Management Console UI no longer requires Silverlight. The 5.1 Management Con
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">New in App-V</th>
|
||||
<th align="left">Prior to App-V</th>
|
||||
<th align="left">New in App-V for Windows</th>
|
||||
<th align="left">Prior to App-V for Windows</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
@ -324,8 +283,8 @@ The Management Console UI no longer requires Silverlight. The 5.1 Management Con
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">New in App-V</th>
|
||||
<th align="left">Prior to App-V</th>
|
||||
<th align="left">New in App-V for Windows</th>
|
||||
<th align="left">Prior to App-V for Windows</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
@ -347,8 +306,8 @@ The Management Console UI no longer requires Silverlight. The 5.1 Management Con
|
||||
</colgroup>
|
||||
<thead>
|
||||
<tr class="header">
|
||||
<th align="left">New in App-V</th>
|
||||
<th align="left">Prior to App-V</th>
|
||||
<th align="left">New in App-V for Windows</th>
|
||||
<th align="left">Prior to App-V Windows</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
@ -406,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:
|
||||
|
||||
@ -437,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** > **Virtual File System** > **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.
|
||||
|
||||
@ -459,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** > **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** > **Virtual File System** > **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:
|
||||
|
||||
@ -483,26 +442,14 @@ You can enable or disable Browser Helper Objects by selecting a new check box, E
|
||||
|
||||
You can now use the package converter to convert App-V 4.6 packages that contain scripts, and registry information and scripts from source .osd files are now included in package converter output.
|
||||
|
||||
For more information including examples, see [Migrating to App-V from a Previous Version](appv-migrating-to-appv-from-a-previous-version.md).
|
||||
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.
|
||||
|
||||
For more information, including a list of event triggers and the context under which scripts can be run, see the Scripts section in [About App-V Dynamic Configuration](appv-dynamic-configuration.md).
|
||||
|
||||
### <a href="" id="bkmk-hardcodepath"></a>Hardcoded path to installation folder is redirected to virtual file system root
|
||||
|
||||
When you convert packages from App-V 4.6 to 5.1, the App-V package can access the hardcoded drive that you were required to use when you created 4.6 packages. The drive letter will be the drive you selected as the installation drive on the 4.6 sequencing machine. (The default drive letter is Q:\\.)
|
||||
|
||||
Previously, the 4.6 root folder was not recognized and could not be accessed by App-V 5.0 packages. App-V packages can access hardcoded files by their full path or can programmatically enumerate files under the App-V 4.6 installation root.
|
||||
|
||||
**Technical Details:** The App-V package converter will save the App-V 4.6 installation root folder and short folder names in the FilesystemMetadata.xml file in the Filesystem element. When the App-V client creates the virtual process, it will map requests from the App-V 4.6 installation root to the virtual file system root.
|
||||
|
||||
## How to Get MDOP Technologies
|
||||
|
||||
|
||||
App-V is a part of the Microsoft Desktop Optimization Pack (MDOP). MDOP is part of Microsoft Software Assurance. For more information about Microsoft Software Assurance and acquiring MDOP, see [How Do I Get MDOP](http://go.microsoft.com/fwlink/?LinkId=322049).
|
||||
|
||||
## Have a suggestion for App-V?
|
||||
|
||||
|
||||
@ -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).
|
||||
@ -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).
|
||||
|
||||
|
||||
@ -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.
|
||||
|
||||
@ -7,6 +7,7 @@ ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
ms.pagetype: store
|
||||
author: TrudyHa
|
||||
localizationpriority: high
|
||||
---
|
||||
|
||||
# Distribute apps using your private store
|
||||
|
||||
BIN
windows/manage/images/wsfb-private-store-gpo.PNG
Normal file
BIN
windows/manage/images/wsfb-private-store-gpo.PNG
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 24 KiB |
@ -27,6 +27,22 @@ The private store is a feature in Store for Business that organizations receive
|
||||
|
||||
Organizations using an MDM to manage apps can use a policy to show only the private store. When your MDM supports the Store for Business, the MDM can use the [Policy CSP](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx#group-policy-table). More specifically, the **ApplicationManagement/RequirePrivateStoreOnly** policy.
|
||||
|
||||
## Show private store only using Group Policy
|
||||
|
||||
If you're using Windows Store for Business and you want employees to only see apps you're managing in your private store, you can use Group Policy to show only the private store. Windows Store app will still be available, but employees can't view or purchase apps. Employees can view and install apps that the admin has added to your organization's private store.
|
||||
|
||||
**To show private store only in Windows Store app**
|
||||
|
||||
1. Type **gpedit** in the search bar, and then select **Edit group policy (Control panel)** to find and start Group Policy Editor.
|
||||
|
||||
2. In the console tree of the snap-in, go to **User Configuration** or **Computer Configuration** > **Administrative Templates** > **Windows Components**, and then click **Store**.
|
||||
|
||||
3. Right-click **Only display the private store within the Windows Store app** in the right pane, and click **Edit**.
|
||||
|
||||
This opens the **Only display the private store within the Windows Store app** policy settings.
|
||||
|
||||
4. On the **Only display the private store within the Windows Store app** setting page, click **Enabled**, and then click **OK**.
|
||||
|
||||
You can also prevent employees from using the Windows Store. For more information, see [Configure access to Windows Store](stop-employees-from-using-the-windows-store.md).
|
||||
|
||||
## Related topics
|
||||
|
||||
@ -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
|
||||
|
||||
@ -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
|
||||
|
||||
@ -7,6 +7,7 @@ ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
ms.pagetype: store
|
||||
author: TrudyHa
|
||||
localizationpriority: high
|
||||
---
|
||||
|
||||
# Settings reference: Windows Store for Business
|
||||
|
||||
@ -85,8 +85,25 @@ When your MDM tool supports Windows Store for Business, the MDM can use these CS
|
||||
- [EnterpriseAssignedAccess](https://msdn.microsoft.com/library/windows/hardware/mt157024.aspx) (Windows 10 Mobile, only)
|
||||
|
||||
For more information, see [Configure an MDM provider](configure-mdm-provider-windows-store-for-business.md).
|
||||
## Related topics
|
||||
|
||||
## Show private store only using Group Policy
|
||||
Applies to Windows 10 Enterprise, version 1607.
|
||||
|
||||
If you're using Windows Store for Business and you want employees to only see apps you're managing in your private store, you can use Group Policy to show only the private store. Windows Store app will still be available, but employees can't view or purchase apps. Employees can view and install apps that the admin has added to your organization's private store.
|
||||
|
||||
**To show private store only in Windows Store app**
|
||||
|
||||
1. Type **gpedit** in the search bar, and then select **Edit group policy (Control panel)** to find and start Group Policy Editor.
|
||||
|
||||
2. In the console tree of the snap-in, go to **User Configuration** or **Computer Configuration** > **Administrative Templates** > **Windows Components**, and then click **Store**.
|
||||
|
||||
3. Right-click **Only display the private store within the Windows Store app** in the right pane, and click **Edit**.
|
||||
|
||||
This opens the **Only display the private store within the Windows Store app** policy settings.
|
||||
|
||||
4. On the **Only display the private store within the Windows Store app** setting page, click **Enabled**, and then click **OK**.
|
||||
|
||||
## Related topics
|
||||
|
||||
[Distribute apps using your private store](distribute-apps-from-your-private-store.md)
|
||||
|
||||
|
||||
@ -24,7 +24,7 @@ With User Experience Virtualization (UE-V), you can capture user-customized Wind
|
||||
|
||||
- Recover settings after hardware replacement or upgrade, or after re-imaging a virtual machine to its initial state
|
||||
|
||||
With the release of Windows 10, version 1607, UE-V is included with the Windows 10 for Enterprise edition. If you are new to Windows 10 and EU-V or upgrading from a previous version of UE-V, you’ll need to download, activate, and install server- and client-side components to start synchronizing user-customized settings across devices.
|
||||
With the release of Windows 10, version 1607, UE-V is included with the Windows 10 for Enterprise edition. If you are new to Windows 10 and UE-V or upgrading from a previous version of UE-V, you’ll need to download, activate, and install server- and client-side components to start synchronizing user-customized settings across devices.
|
||||
|
||||
## Components of UE-V
|
||||
|
||||
@ -50,7 +50,7 @@ Use these UE-V components to create and manage custom templates for your third-p
|
||||
|
||||
| Component | Description |
|
||||
|-------------------------------|---------------|
|
||||
| **UE-V template generator** | Use the **UE-V template generator** to create custom settings location templates that you can then distribute to user computers. The UE-V template generator also lets you edit an existing template or validate a template that was created with a different XML editor. <br>With the Windows 10, version 1607 release, the UE-V template generator is installed with the [Windows 10 Assessment and Deployment kit](https://developer.microsoft.com/en-us/windows/hardware/windows-assessment-deployment-kit) (Windows ADK). <br>If you are upgrading from an existing UE-V installation, you’ll need to use the new generator to create new settings location templates. Application templates created with previous versions of the UE-V template generator are still supported, however. |
|
||||
| **UE-V template generator** | Use the **UE-V template generator** to create custom settings location templates that you can then distribute to user computers. The UE-V template generator also lets you edit an existing template or validate a template that was created with a different XML editor. <br>With the Windows 10, version 1607 release, the UE-V template generator is installed with the [Windows Assessment and Deployment kit for Windows 10, version 1607](https://developer.microsoft.com/en-us/windows/hardware/windows-assessment-deployment-kit) (Windows ADK). <br>If you are upgrading from an existing UE-V installation, you’ll need to use the new generator to create new settings location templates. Application templates created with previous versions of the UE-V template generator are still supported, however. |
|
||||
| **Settings template catalog** | The **settings template catalog** is a folder path on UE-V computers or a Server Message Block (SMB) network share that stores the custom settings location templates. The UE-V service checks this location once a day, retrieves new or updated templates, and updates its synchronization behavior.<br>If you use only the UE-V default settings location templates, then a settings template catalog is unnecessary. For more information about settings deployment catalogs, see [Deploy a UE-V settings template catalog](uev-deploy-uev-for-custom-applications.md#deploycatalogue). |
|
||||
|
||||
<!-- PRESERVING ORIGINAL IMAGE CODING JUST IN CASE - NOTE THAT UPDATED IMAGE IS A PNG FILE
|
||||
@ -65,7 +65,7 @@ UE-V synchronizes settings for these applications by default. For a complete lis
|
||||
|
||||
- Microsoft Office 2016, 2013, and 2010
|
||||
|
||||
- Internet Explorer 11, 10, and 9
|
||||
- Internet Explorer 11 and 10
|
||||
|
||||
- Many Windows applications, such as Xbox
|
||||
|
||||
@ -73,22 +73,22 @@ UE-V synchronizes settings for these applications by default. For a complete lis
|
||||
|
||||
- Many Windows settings, such as desktop background or wallpaper
|
||||
|
||||
**Note**
|
||||
>**Note**
|
||||
You can also [customize UE-V to synchronize settings](uev-deploy-uev-for-custom-applications.md) for applications other than those synchronized by default.
|
||||
|
||||
## Other resources for this feature
|
||||
|
||||
- [Get Started with UE-V](uev-getting-started.md)
|
||||
- [Get Started with UE-V for Windows 10](uev-getting-started.md)
|
||||
|
||||
- [UE-V Release Notes](uev-release-notes-1607.md)
|
||||
- [UE-V for Windows 10 Release Notes](uev-release-notes-1607.md)
|
||||
|
||||
- [Prepare a UE-V Deployment](uev-prepare-for-deployment.md)
|
||||
- [Prepare to deploy UE-V for Windows 10](uev-prepare-for-deployment.md)
|
||||
|
||||
- [Upgrade to UE-V for Windows 10](uev-upgrade-uev-from-previous-releases.md)
|
||||
|
||||
- [Administer UE-V](uev-administering-uev.md)
|
||||
- [Administer UE-V for Windows 10](uev-administering-uev.md)
|
||||
|
||||
- [Technical Reference for UE-V](uev-technical-reference.md)
|
||||
- [Technical Reference for UE-V for Windows 10](uev-technical-reference.md)
|
||||
|
||||
## Have a suggestion for UE-V?
|
||||
|
||||
|
||||
@ -7,6 +7,7 @@ ms.pagetype: store, mobile
|
||||
ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
author: TrudyHa
|
||||
localizationpriority: high
|
||||
---
|
||||
|
||||
# Windows Store for Business overview
|
||||
|
||||
Reference in New Issue
Block a user