Learn how Microsoft Edge kiosk mode works with assigned access to let IT administrators create a tailored browsing experience designed for kiosk devices.
View all available group policies for Microsoft Edge on Windows 10.
-
- image:
-
- src: https://docs.microsoft.com/media/common/i_policy.svg
-
- title: All group policies
+ ms.date: 08/28/2020 #Required; mm/dd/yyyy format.
+
+# linkListType: architecture | concept | deploy | download | get-started | how-to-guide | learn | overview | quickstart | reference | sample | tutorial | video | whats-new
+
+landingContent:
+# Cards and links should be based on top customer tasks or top subjects
+# Start card title with a verb
+ # Card (optional)
+ - title: What's new
+ linkLists:
+ - linkListType: whats-new
+ links:
+ - text: Documentation for Microsoft Edge version 77 or later
+ url: https://docs.microsoft.com/DeployEdge/
+ - text: Microsoft Edge Legacy desktop app will reach end of support on March 9, 2021
+ url: https://techcommunity.microsoft.com/t5/microsoft-365-blog/microsoft-365-apps-say-farewell-to-internet-explorer-11-and/ba-p/1591666
+
+ # Card (optional)
+ - title: Group policies configure guidance part 1
+ linkLists:
+ - linkListType: reference
+ links:
+ - text: All group policies
+ url: /microsoft-edge/deploy/available-policies
+ - text: Address bar
+ url: /microsoft-edge/deploy/group-policies/address-bar-settings-gp
+ - text: Adobe Flash
+ url: /microsoft-edge/deploy/group-policies/adobe-settings-gp
+ - text: Books Library
+ url: /microsoft-edge/deploy/group-policies/books-library-management-gp
+ - text: Browser experience
+ url: /microsoft-edge/deploy/group-policies/browser-settings-management-gp
+ - text: Developer tools
+ url: /microsoft-edge/deploy/group-policies/developer-settings-gp
+ - text: Extensions
+ url: /microsoft-edge/deploy/group-policies/extensions-management-gp
+ - text: Favorites
+ url: /microsoft-edge/deploy/group-policies/favorites-management-gp
+ - text: Home button
+ url: /microsoft-edge/deploy/group-policies/home-button-gp
+
+ # Card (optional)
+ - title: Group policies configure guidance part 2
+ linkLists:
+ - linkListType: reference
+ links:
+ - text: Interoperability and enterprise mode
+ url: /microsoft-edge/deploy/group-policies/interoperability-enterprise-guidance-gp
+ - text: New Tab page
+ url: /microsoft-edge/deploy/group-policies/new-tab-page-settings-gp
+ - text: Kiosk mode deployment in Microsoft Edge
+ url: /microsoft-edge/deploy/microsoft-edge-kiosk-mode-deploy
+ - text: Prelaunch Microsoft Edge and preload tabs
+ url: /microsoft-edge/deploy/group-policies/prelaunch-preload-gp
+ - text: Search engine customization
+ url: /microsoft-edge/deploy/group-policies/search-engine-customization-gp
+ - text: Security and privacy
+ url: /microsoft-edge/deploy/group-policies/security-privacy-management-gp
+ - text: Start page
+ url: /microsoft-edge/deploy/group-policies/start-pages-gp
+ - text: Sync browser
+ url: /microsoft-edge/deploy/group-policies/sync-browser-settings-gp
+ - text: Telemetry and data collection
+ url: /microsoft-edge/deploy/group-policies/telemetry-management-gp
+
diff --git a/browsers/edge/group-policies/sync-browser-settings-gp.md b/browsers/edge/group-policies/sync-browser-settings-gp.md
index cdce19d2e5..d948b2c862 100644
--- a/browsers/edge/group-policies/sync-browser-settings-gp.md
+++ b/browsers/edge/group-policies/sync-browser-settings-gp.md
@@ -6,17 +6,17 @@ manager: dansimp
ms.author: dansimp
author: dansimp
ms.date: 10/02/2018
-ms.reviewer:
+ms.reviewer:
ms.localizationpriority: medium
ms.topic: reference
---
-# Sync browser settings
+# Sync browser settings
> [!NOTE]
> You've reached the documentation for Microsoft Edge version 45 and earlier. To see the documentation for Microsoft Edge version 77 or later, go to the [Microsoft Edge documentation landing page](https://docs.microsoft.com/DeployEdge/).
-By default, the “browser” group syncs automatically between the user’s devices, letting users make changes. The “browser” group uses the Sync your Settings option in Settings to sync information like history and favorites. You can configure Microsoft Edge to prevent the “browser” group from syncing and prevent users from turning on the _Sync your Settings_ toggle in Settings. If you want syncing turned off by default but not disabled, select the _Allow users to turn “browser” syncing_ option in the Do not sync browser policy.
+By default, the “browser” group syncs automatically between the user’s devices, letting users make changes. The “browser” group uses the Sync your Settings option in Settings to sync information like history and favorites. You can configure Microsoft Edge to prevent the “browser” group from syncing and prevent users from turning on the _Sync your Settings_ toggle in Settings. If you want syncing turned off by default but not disabled, select the _Allow users to turn “browser” syncing_ option in the Do not sync browser policy.
## Relevant policies
@@ -38,7 +38,7 @@ You can find the Microsoft Edge Group Policy settings in the following location
To verify the settings:
1. In the upper-right corner of Microsoft Edge, click **More** \(**...**\).
2. Click **Settings**.
-3. Under Account, see if the setting is toggled on or off.
+3. Under Account, see if the setting is toggled on or off.
## Do not sync browser settings
diff --git a/browsers/edge/images/allow-smart-screen-validation.PNG b/browsers/edge/images/allow-smart-screen-validation.png
similarity index 100%
rename from browsers/edge/images/allow-smart-screen-validation.PNG
rename to browsers/edge/images/allow-smart-screen-validation.png
diff --git a/browsers/edge/images/sync-settings.PNG b/browsers/edge/images/sync-settings.png
similarity index 100%
rename from browsers/edge/images/sync-settings.PNG
rename to browsers/edge/images/sync-settings.png
diff --git a/browsers/edge/includes/configure-windows-defender-smartscreen-include.md b/browsers/edge/includes/configure-windows-defender-smartscreen-include.md
index c17f639024..375951a25c 100644
--- a/browsers/edge/includes/configure-windows-defender-smartscreen-include.md
+++ b/browsers/edge/includes/configure-windows-defender-smartscreen-include.md
@@ -2,7 +2,7 @@
author: eavena
ms.author: eravena
ms.date: 10/02/2018
-ms.reviewer:
+ms.reviewer:
audience: itpro
manager: dansimp
ms.prod: edge
@@ -25,9 +25,9 @@ ms.topic: include
---
-To verify Windows Defender SmartScreen is turned off (disabled):
+To verify Windows Defender SmartScreen is turned off (disabled):
1. Click or tap **More** (…) and select **Settings** > **View Advanced settings**.
-2. Verify the setting **Help protect me from malicious sites and download with Windows Defender SmartScreen** is disabled.
+2. Verify the setting **Help protect me from malicious sites and download with Windows Defender SmartScreen** is disabled.
### ADMX info and settings
@@ -40,7 +40,7 @@ To verify Windows Defender SmartScreen is turned off (disabled):
#### MDM settings
- **MDM name:** Browser/[AllowSmartScreen](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-browser#browser-allowsmartscreen)
- **Supported devices:** Desktop and Mobile
-- **URI full path:** ./Vendor/MSFT/Policy/Config/Browser/AllowSmartScreen
+- **URI full path:** ./Vendor/MSFT/Policy/Config/Browser/AllowSmartScreen
- **Data type:** Integer
#### Registry settings
diff --git a/browsers/edge/index.yml b/browsers/edge/index.yml
index 61b851adf2..0533a4dcb2 100644
--- a/browsers/edge/index.yml
+++ b/browsers/edge/index.yml
@@ -1,163 +1,93 @@
-### YamlMime:YamlDocument
+### YamlMime:Landing
-documentType: LandingData
-
-title: Microsoft Edge Legacy Group Policy configuration options
+title: Microsoft Edge Group Legacy Policy configuration options # < 60 chars
+summary: Learn how to deploy and configure group policies in Microsoft Edge Legacy on Windows 10. Some of the features coming to Microsoft Edge Legacy gives you the ability to set a custom URL for the New Tab page or Home button. Another new feature allows you to hide or show the Favorites bar, giving you more control over the favorites bar. # < 160 chars
metadata:
-
- document_id:
-
- title: Microsoft Edge Group Legacy Policy configuration options
-
- description:
-
- text: (Note - You've reached the documentation for Microsoft Edge version 45 and earlier. To see the documentation for Microsoft Edge version 77 or later, go to the [Microsoft Edge documentation landing page](https://docs.microsoft.com/DeployEdge/).) Learn how to deploy and configure group policies in Microsoft Edge Legacy on Windows 10. Some of the features coming to Microsoft Edge Legacy gives you the ability to set a custom URL for the New Tab page or Home button. Another new feature allows you to hide or show the Favorites bar, giving you more control over the favorites bar.
-
+ title: Microsoft Edge Group Legacy Policy configuration options # Required; page title displayed in search results. Include the brand. < 60 chars.
+ description: Learn about interoperability goals and enterprise guidance along with system requirements, language support and frequently asked questions. # Required; article description that is displayed in search results. < 160 chars.
+ ms.prod: microsoft-edge
keywords: Microsoft Edge Legacy, Windows 10
-
ms.localizationpriority: medium
-
- author: shortpatti
-
- ms.author: pashort
-
- ms.date: 08/09/2018
-
- ms.topic: article
-
- ms.devlang: na
-
-sections:
-
-- title:
-
-- items:
-
- - type: markdown
-
- text: (Note - You've reached the documentation for Microsoft Edge version 45 and earlier. To see the documentation for Microsoft Edge version 77 or later, go to the [Microsoft Edge documentation landing page](https://docs.microsoft.com/DeployEdge/).) Learn about interoperability goals and enterprise guidance along with system requirements, language support and frequently asked questions.
-
-- items:
-
- - type: list
-
- style: cards
-
- className: cardsE
-
- columns: 3
-
- items:
-
- - href: https://docs.microsoft.com/microsoft-edge/deploy/change-history-for-microsoft-edge
-
- html:
Learn more about the latest group policies and features added to Microsoft Edge.
-
-
-
-
-
-
+ ms.topic: landing-page # Required
+ ms.collection: collection # Optional; Remove if no collection is used.
+ author: shortpatti #Required; your GitHub user alias, with correct capitalization.
+ ms.author: pashort #Required; microsoft alias of author; optional team alias.
+ ms.date: 07/07/2020 #Required; mm/dd/yyyy format.
+
+# linkListType: architecture | concept | deploy | download | get-started | how-to-guide | learn | overview | quickstart | reference | sample | tutorial | video | whats-new
+
+landingContent:
+# Cards and links should be based on top customer tasks or top subjects
+# Start card title with a verb
+ # Card (optional)
+ - title: About Microsoft Edge
+ linkLists:
+ - linkListType: whats-new
+ links:
+ - text: Documentation for Microsoft Edge version 77 or later
+ url: /DeployEdge
+ - text: Microsoft 365 apps say farewell to Internet Explorer 11 and Windows 10 sunsets Microsoft Edge Legacy
+ url: https://techcommunity.microsoft.com/t5/microsoft-365-blog/microsoft-365-apps-say-farewell-to-internet-explorer-11-and/ba-p/1591666
+ - text: Latest group policies and features added to Microsoft Edge
+ url: /microsoft-edge/deploy/change-history-for-microsoft-edge
+ - linkListType: overview
+ links:
+ - text: System requirements and supported languages
+ url: /microsoft-edge/deploy/about-microsoft-edge
+ - text: Compare Windows 10 editions
+ url: https://www.microsoft.com/en-us/WindowsForBusiness/Compare
+ - text: Security & protection
+ url: /microsoft-edge/deploy/group-policies/security-privacy-management-gp
+ - text: Interoperability & enterprise guidance
+ url: /microsoft-edge/deploy/group-policies/interoperability-enterprise-guidance-gp
+ - text: Group policies & configuration options
+ url: /microsoft-edge/deploy/group-policies/
+
+ # Card (optional)
+ - title: Microsoft Edge resources
+ linkLists:
+ - linkListType: overview
+ links:
+ - text: Minimum system requirements
+ url: /microsoft-edge/deploy/about-microsoft-edge#minimum-system-requirements
+ - text: Supported languages
+ url: /microsoft-edge/deploy/about-microsoft-edge#supported-languages
+ - text: Document change history
+ url: /microsoft-edge/deploy/change-history-for-microsoft-edge
+ - text: Microsoft Edge Dev blog
+ url: https://blogs.windows.com/msedgedev
+ - text: Microsoft Edge Dev on Twitter
+ url: /microsoft-edge/deploy/about-microsoft-edge#supported-languages
+ - text: Microsoft Edge changelog
+ url: /microsoft-edge/deploy/change-history-for-microsoft-edge
+ - text: Measuring the impact of Microsoft Edge
+ url: https://blogs.windows.com/msedgedev
+
+ # Card (optional)
+ - title: IE11 resources
+ linkLists:
+ - linkListType: overview
+ links:
+ - text: Deploy Internet Explorer 11 (IE11) - IT Pros
+ url: https://go.microsoft.com/fwlink/p/?LinkId=760644
+ - text: Internet Explorer Administration Kit 11 (IEAK 11)
+ url: /internet-explorer/ie11-ieak
+ - linkListType: download
+ links:
+ - text: Download Internet Explorer 11
+ url: https://go.microsoft.com/fwlink/p/?linkid=290956
+
+ # Card (optional)
+ - title: Additional resources
+ linkLists:
+ - linkListType: overview
+ links:
+ - text: Group Policy and the Group Policy Management Console (GPMC)
+ url: https://go.microsoft.com/fwlink/p/?LinkId=617921
+ - text: Group Policy and the Local Group Policy Editor
+ url: https://go.microsoft.com/fwlink/p/?LinkId=617922
+ - text: Group Policy and the Advanced Group Policy Management (AGPM)
+ url: https://go.microsoft.com/fwlink/p/?LinkId=617923
+ - text: Group Policy and Windows PowerShell
+ url: https://go.microsoft.com/fwlink/p/?LinkId=617924
diff --git a/browsers/edge/microsoft-edge-faq.md b/browsers/edge/microsoft-edge-faq.md
deleted file mode 100644
index 632905e3cb..0000000000
--- a/browsers/edge/microsoft-edge-faq.md
+++ /dev/null
@@ -1,58 +0,0 @@
----
-title: Microsoft Edge - Frequently Asked Questions (FAQs) for IT Pros
-ms.reviewer:
-audience: itpro
-manager: dansimp
-description: Answers to frequently asked questions about Microsoft Edge features, integration, support, and potential problems.
-author: dansimp
-ms.author: dansimp
-ms.prod: edge
-ms.topic: article
-ms.mktglfcycl: general
-ms.sitesec: library
-ms.localizationpriority: medium
----
-
-# Frequently Asked Questions (FAQs) for IT Pros
-
->Applies to: Microsoft Edge on Windows 10 and Windows 10 Mobile
-
-> [!NOTE]
-> You've reached the documentation for Microsoft Edge version 45 and earlier. To see the documentation for Microsoft Edge version 77 or later, go to the [Microsoft Edge documentation landing page](https://docs.microsoft.com/DeployEdge/).
-
-## How can I get the next major version of Microsoft Edge, based on Chromium?
-In December 2018, Microsoft [announced](https://blogs.windows.com/windowsexperience/2018/12/06/microsoft-edge-making-the-web-better-through-more-open-source-collaboration/#8jv53blDvL6TIKuS.97) our intention to adopt the Chromium open source project in the development of Microsoft Edge on the desktop, to create better web compatibility for our customers and less fragmentation of the web for all web developers. You can get more information at the [Microsoft Edge Insiders site](https://www.microsoftedgeinsider.com/).
-
-## What’s the difference between Microsoft Edge and Internet Explorer 11? How do I know which one to use?
-Microsoft Edge is the default browser for all Windows 10 devices. It’s built to be highly compatible with the modern web. For some enterprise web apps and a small set of sites that were built to work with older technologies like ActiveX, [you can use Enterprise Mode](emie-to-improve-compatibility.md) to automatically send users to Internet Explorer 11.
-
-For more information on how Internet Explorer and Microsoft Edge work together to support your legacy web apps, while still defaulting to the higher security and modern experiences enabled by Microsoft Edge, see [Legacy apps in the enterprise](https://blogs.windows.com/msedgedev/2017/04/07/legacy-web-apps-enterprise/#RAbtRvJSYFaKu2BI.97).
-
-## Does Microsoft Edge work with Enterprise Mode?
-[Enterprise Mode](https://docs.microsoft.com/internet-explorer/ie11-deploy-guide/enterprise-mode-overview-for-ie11) helps you run many legacy web applications with better backward compatibility. You can configure both Microsoft Edge and Internet Explorer to use the same Enterprise Mode Site List, switching seamlessly between browsers to support both modern and legacy web apps.
-
-## How do I customize Microsoft Edge and related settings for my organization?
-You can use Group Policy or Microsoft Intune to manage settings related to Microsoft Edge, such as security settings, folder redirection, and preferences. See [Group Policy and Mobile Device Management (MDM) settings for Microsoft Edge](https://docs.microsoft.com/microsoft-edge/deploy/group-policies/) for a list of policies currently available for Microsoft Edge and configuration information. Note that the preview release of Chromium-based Microsoft Edge might not include management policies or other enterprise functionality; our focus during the preview is modern browser fundamentals.
-
-## Is Adobe Flash supported in Microsoft Edge?
-Adobe Flash is currently supported as a built-in feature of Microsoft Edge on PCs running Windows 10. In July 2017, Adobe announced that Flash support will end after 2020. With this change to Adobe support, we’ve started to phase Flash out of Microsoft Edge by adding the [Configure the Adobe Flash Click-to-Run setting group policy](https://docs.microsoft.com/microsoft-edge/deploy/available-policies#configure-the-adobe-flash-click-to-run-setting) - this lets you control which websites can run Adobe Flash content.
-
-To learn more about Microsoft’s plan for phasing Flash out of Microsoft Edge and Internet Explorer, see [The End of an Era — Next Steps for Adobe Flash](https://blogs.windows.com/msedgedev/2017/07/25/flash-on-windows-timeline/#3Bcc3QjRw0l7XsZ4.97) (blog article).
-
-## Does Microsoft Edge support ActiveX controls or BHOs like Silverlight or Java?
-No. Microsoft Edge doesn’t support ActiveX controls and BHOs like Silverlight or Java. If you’re running web apps that use ActiveX controls, x-ua-compatible headers, or legacy document modes, you need to keep running them in IE11. IE11 offers additional security, manageability, performance, backward compatibility, and standards support.
-
-## How often will Microsoft Edge be updated?
-In Windows 10, we’re delivering Windows as a service, updated on a cadence driven by quality and the availability of new features. Microsoft Edge security updates are released every two to four weeks, while bigger feature updates are included in the Windows 10 releases on a semi-annual cadence.
-
-## How can I provide feedback on Microsoft Edge?
-Microsoft Edge is an evergreen browser - we’ll continue to evolve both the web platform and the user interface with regular updates. To send feedback on user experience, or on broken or malicious sites, use the **Send Feedback** option under the ellipses icon (**...**) in the Microsoft Edge toolbar.
-
-## Will Internet Explorer 11 continue to receive updates?
-We’re committed to keeping Internet Explorer a supported, reliable, and safe browser. Internet Explorer is still a component of Windows and follows the support lifecycle of the OS on which it’s installed. For details, see [Lifecycle FAQ - Internet Explorer](https://support.microsoft.com/help/17454/). While we continue to support and update Internet Explorer, the latest features and platform updates will only be available in Microsoft Edge.
-
-## How do I find out what version of Microsoft Edge I have?
-In the upper right corner of Microsoft Edge, click the ellipses icon (**...**), and then click **Settings**. Look in the **About Microsoft Edge** section to find your version.
-
-## What is Microsoft EdgeHTML?
-Microsoft EdgeHTML is the web rendering engine that powers the current Microsoft Edge web browser and Windows 10 web app platform. (As opposed to *Microsoft Edge, based on Chromium*.)
diff --git a/browsers/edge/microsoft-edge-faq.yml b/browsers/edge/microsoft-edge-faq.yml
new file mode 100644
index 0000000000..751f40f4ea
--- /dev/null
+++ b/browsers/edge/microsoft-edge-faq.yml
@@ -0,0 +1,74 @@
+### YamlMime:FAQ
+metadata:
+ title: Microsoft Edge - Frequently Asked Questions (FAQ) for IT Pros
+ ms.reviewer:
+ audience: itpro
+ manager: dansimp
+ description: Answers to frequently asked questions about Microsoft Edge features, integration, support, and potential problems.
+ author: dansimp
+ ms.author: dansimp
+ ms.prod: edge
+ ms.topic: article
+ ms.mktglfcycl: general
+ ms.sitesec: library
+ ms.localizationpriority: medium
+
+title: Frequently Asked Questions (FAQ) for IT Pros
+summary: |
+ Applies to: Microsoft Edge on Windows 10 and Windows 10 Mobile
+
+ > [!NOTE]
+ > You've reached the documentation for Microsoft Edge version 45 and earlier. To see the documentation for Microsoft Edge version 77 or later, go to the [Microsoft Edge documentation landing page](https://docs.microsoft.com/DeployEdge/).
+
+
+sections:
+ - name: Ignored
+ questions:
+ - question: How can I get the next major version of Microsoft Edge, based on Chromium?
+ answer: |
+ In December 2018, Microsoft [announced](https://blogs.windows.com/windowsexperience/2018/12/06/microsoft-edge-making-the-web-better-through-more-open-source-collaboration/#8jv53blDvL6TIKuS.97) our intention to adopt the Chromium open source project in the development of Microsoft Edge on the desktop, to create better web compatibility for our customers and less fragmentation of the web for all web developers. You can get more information at the [Microsoft Edge Insiders site](https://www.microsoftedgeinsider.com/).
+
+ - question: What's the difference between Microsoft Edge and Internet Explorer 11? How do I know which one to use?
+ answer: |
+ Microsoft Edge is the default browser for all Windows 10 devices. It's built to be highly compatible with the modern web. For some enterprise web apps and a small set of sites that were built to work with older technologies like ActiveX, [you can use Enterprise Mode](emie-to-improve-compatibility.md) to automatically send users to Internet Explorer 11.
+
+ For more information on how Internet Explorer and Microsoft Edge work together to support your legacy web apps, while still defaulting to the higher security and modern experiences enabled by Microsoft Edge, see [Legacy apps in the enterprise](https://blogs.windows.com/msedgedev/2017/04/07/legacy-web-apps-enterprise/#RAbtRvJSYFaKu2BI.97).
+
+ - question: Does Microsoft Edge work with Enterprise Mode?
+ answer: |
+ [Enterprise Mode](https://docs.microsoft.com/internet-explorer/ie11-deploy-guide/enterprise-mode-overview-for-ie11) helps you run many legacy web applications with better backward compatibility. You can configure both Microsoft Edge and Internet Explorer to use the same Enterprise Mode Site List, switching seamlessly between browsers to support both modern and legacy web apps.
+
+ - question: How do I customize Microsoft Edge and related settings for my organization?
+ answer: |
+ You can use Group Policy or Microsoft Intune to manage settings related to Microsoft Edge, such as security settings, folder redirection, and preferences. See [Group Policy and Mobile Device Management (MDM) settings for Microsoft Edge](https://docs.microsoft.com/microsoft-edge/deploy/group-policies/) for a list of policies currently available for Microsoft Edge and configuration information. Note that the preview release of Chromium-based Microsoft Edge might not include management policies or other enterprise functionality; our focus during the preview is modern browser fundamentals.
+
+ - question: Is Adobe Flash supported in Microsoft Edge?
+ answer: |
+ Adobe Flash is currently supported as a built-in feature of Microsoft Edge on PCs running Windows 10. In July 2017, Adobe announced that Flash support will end after 2020. With this change to Adobe support, we've started to phase Flash out of Microsoft Edge by adding the [Configure the Adobe Flash Click-to-Run setting group policy](https://docs.microsoft.com/microsoft-edge/deploy/available-policies#configure-the-adobe-flash-click-to-run-setting) - this lets you control which websites can run Adobe Flash content.
+
+ To learn more about Microsoft's plan for phasing Flash out of Microsoft Edge and Internet Explorer, see [The End of an Era — Next Steps for Adobe Flash](https://blogs.windows.com/msedgedev/2017/07/25/flash-on-windows-timeline/#3Bcc3QjRw0l7XsZ4.97) (blog article).
+
+ - question: Does Microsoft Edge support ActiveX controls or BHOs like Silverlight or Java?
+ answer: |
+ No, Microsoft Edge doesn't support ActiveX controls and Browser Helper Objects (BHOs) like Silverlight or Java. If you're running web apps that use ActiveX controls, x-ua-compatible headers, or legacy document modes, you need to keep running them in Internet Explorer 11. Internet Explorer 11 offers additional security, manageability, performance, backward compatibility, and standards support.
+
+ - question: How often will Microsoft Edge be updated?
+ answer: |
+ In Windows 10, we're delivering Windows as a service, updated on a cadence driven by quality and the availability of new features. Microsoft Edge security updates are released every two to four weeks, while bigger feature updates are included in the Windows 10 releases on a semi-annual cadence.
+
+ - question: How can I provide feedback on Microsoft Edge?
+ answer: |
+ Microsoft Edge is an evergreen browser - we'll continue to evolve both the web platform and the user interface with regular updates. To send feedback on user experience, or on broken or malicious sites, use the **Send Feedback** option under the ellipses icon (**...**) in the Microsoft Edge toolbar.
+
+ - question: Will Internet Explorer 11 continue to receive updates?
+ answer: |
+ We're committed to keeping Internet Explorer a supported, reliable, and safe browser. Internet Explorer is still a component of Windows and follows the support lifecycle of the OS on which it's installed. For details, see [Lifecycle FAQ - Internet Explorer](https://support.microsoft.com/help/17454/). While we continue to support and update Internet Explorer, the latest features and platform updates will only be available in Microsoft Edge.
+
+ - question: How do I find out which version of Microsoft Edge I have?
+ answer: |
+ In the upper-right corner of Microsoft Edge, select the ellipses icon (**...**), and then select **Settings**. Look in the **About Microsoft Edge** section to find your version.
+
+ - question: What is Microsoft EdgeHTML?
+ answer: |
+ Microsoft EdgeHTML is the web rendering engine that powers the current Microsoft Edge web browser and Windows 10 web app platform (as opposed to *Microsoft Edge, based on Chromium*).
+
diff --git a/browsers/edge/microsoft-edge-kiosk-mode-deploy.md b/browsers/edge/microsoft-edge-kiosk-mode-deploy.md
index 8249262926..7c44ef1c3b 100644
--- a/browsers/edge/microsoft-edge-kiosk-mode-deploy.md
+++ b/browsers/edge/microsoft-edge-kiosk-mode-deploy.md
@@ -11,16 +11,18 @@ ms.prod: edge
ms.sitesec: library
ms.topic: article
ms.localizationpriority: medium
-ms.date: 01/17/2020
+ms.date: 02/16/2021
---
# Deploy Microsoft Edge Legacy kiosk mode
+> [!IMPORTANT]
+> Microsoft 365 apps and services will not support Internet Explorer 11 starting August 17, 2021 (Microsoft Teams will not support Internet Explorer 11 earlier, starting November 30, 2020). [Learn more](https://aka.ms/AA97tsw). Please note that Internet Explorer 11 will remain a supported browser. Internet Explorer 11 is a component of the Windows operating system and [follows the Lifecycle Policy](https://docs.microsoft.com/lifecycle/faq/internet-explorer-microsoft-edge) for the product on which it is installed.
> Applies to: Microsoft Edge Legacy (version 45 and earlier) on Windows 10, version 1809 or later
> Professional, Enterprise, and Education
> [!NOTE]
-> You've reached the documentation for Microsoft Edge Legacy (version 45 and earlier.) To see the documentation for Microsoft Edge version 77 or later, go to the [Microsoft Edge documentation landing page](https://docs.microsoft.com/DeployEdge/). For information about kiosk mode in the new version of Microsoft Edge, see [Microsoft Edge kiosk mode](https://docs.microsoft.com/DeployEdge/microsoft-edge-kiosk-mode).
+> You've reached the documentation for Microsoft Edge Legacy (version 45 and earlier.) To see the documentation for Microsoft Edge version 77 or later, go to the [Microsoft Edge documentation landing page](https://docs.microsoft.com/DeployEdge/). For information about kiosk mode in the new version of Microsoft Edge, see [Microsoft Edge kiosk mode](https://docs.microsoft.com/DeployEdge/microsoft-edge-configure-kiosk-mode).
In the Windows 10 October 2018 Update, we added the capability to use Microsoft Edge Legacy as a kiosk using assigned access. With assigned access, you create a tailored browsing experience locking down a Windows 10 device to only run as a single-app or multi-app kiosk. Assigned access restricts a local standard user account so that it only has access to one or more Windows app, such as Microsoft Edge Legacy in kiosk mode.
diff --git a/browsers/edge/microsoft-edge.yml b/browsers/edge/microsoft-edge.yml
index 5c105dcdc2..797d881911 100644
--- a/browsers/edge/microsoft-edge.yml
+++ b/browsers/edge/microsoft-edge.yml
@@ -1,61 +1,144 @@
-### YamlMime:YamlDocument
+### YamlMime:Landing
+
+title: Microsoft Edge Legacy # < 60 chars
+summary: Find the tools and resources you need to help deploy and use Microsoft Edge in your organization. # < 160 chars
-documentType: LandingData
-title: Microsoft Edge
metadata:
- document_id:
- title: Microsoft Edge
- description: Find the tools and resources you need to help deploy and use Microsoft Edge in your organization.
+ title: Microsoft Edge Legacy # Required; page title displayed in search results. Include the brand. < 60 chars.
+ description: Find the tools and resources you need to help deploy and use Microsoft Edge in your organization. # Required; article description that is displayed in search results. < 160 chars.
keywords: Microsoft Edge, issues, fixes, announcements, Windows Server, advisories
+ ms.prod: edge
ms.localizationpriority: medium
author: lizap
ms.author: elizapo
manager: dougkim
- ms.topic: article
+ ms.topic: landing-page
ms.devlang: na
+ ms.date: 08/19/2020 #Required; mm/dd/yyyy format.
-sections:
-- items:
- - type: markdown
- text: "
- Find the tools and resources you need to help deploy and use Microsoft Edge in your organization.
- "
-- title: What's new
-- items:
- - type: markdown
- text: "
- Find out the latest and greatest news on Microsoft Edge.
-
**The latest in Microsoft Edge** See what's new for users and developers in the next update to Microsoft Edge - now available with the Windows 10 April 2018 update! Find out more
**Evaluate the impact** Review the latest Forrester Total Economic Impact (TEI) report to learn about the impact Microsoft Edge can have in your organization. Download the reports
**Microsoft Edge for iOS and Android** Microsoft Edge brings familiar features across your PC and phone, which allows browsing to go with you, no matter what device you use. Learn more
**Application Guard** Microsoft Edge with Windows Defender Application Guard is the most secure browser on Windows 10 Enterprise. Learn more
-
- "
-- title: Compatibility
-- items:
- - type: markdown
- text: "
- Even if you still have legacy apps in your organization, you can default to the secure, modern experience of Microsoft Edge and provide a consistent level of compatibility with existing legacy applications.
-
**Web Application Compatibility Lab Kit** The Web Application Compatibility Lab Kit is a primer for the features and techniques used to provide web application compatibility during a typical enterprise migration to Microsoft Edge. Find out more
-
- "
-- title: Security
-- items:
- - type: markdown
- text: "
- Microsoft Edge uses Windows Hello and Windows Defender SmartScreen to defend against phishing and malware. Take a look at some of the additional features behind the strong defense that Microsoft Edge provides against web-based attacks.
-
**NSS Labs web browser security reports** See the results of two global tests measuring how effective browsers are at protecting against socially engineered malware and phishing attacks. Download the reports
**Microsoft Edge sandbox** See how Microsoft Edge has significantly reduced the attack surface of the sandbox by configuring the app container to further reduce its privilege. Find out more
**Windows Defender SmartScreen** Manage your organization's computer settings with Group Policy and MDM settings to display a warning page to employees or block a site entirely. Read the docs
-
- "
-- title: Deployment and end user readiness
-- items:
- - type: markdown
- text: "
- Find resources and learn about features to help you deploy Microsoft Edge in your organization to get your users up and running quickly.
-
**Sign up for the Windows IT Pro Insider** Get the latest tools, tips, and expert guidance on deployment, management, security, and more. Learn more
**Microsoft Edge Dev blog** Keep up with the latest browser trends, security tips, and news for IT professionals. Read the blog
**Microsoft Edge Dev on Twitter** Get the latest news and updates from the Microsoft Web Platform team. Visit Twitter
-
- "
+# linkListType: architecture | concept | deploy | download | get-started | how-to-guide | learn | overview | quickstart | reference | sample | tutorial | video | whats-new
+
+landingContent:
+# Cards and links should be based on top customer tasks or top subjects
+# Start card title with a verb
+ # Card (optional)
+ - title: What's new
+ linkLists:
+ - linkListType: whats-new
+ links:
+ - text: Documentation for Microsoft Edge version 77 or later
+ url: https://docs.microsoft.com/DeployEdge/
+ - text: Microsoft Edge Legacy desktop app will reach end of support on March 9, 2021
+ url: https://techcommunity.microsoft.com/t5/microsoft-365-blog/microsoft-365-apps-say-farewell-to-internet-explorer-11-and/ba-p/1591666
+ - text: The latest in Microsoft Edge
+ url: https://blogs.windows.com/msedgedev/2018/04/30/edgehtml-17-april-2018-update/#C7jCBdbPSG6bCXHr.97
+ - text: Microsoft Edge for iOS and Android
+ url: https://blogs.windows.com/windowsexperience/2017/11/30/microsoft-edge-now-available-for-ios-and-android
+ - text: Application Guard
+ url: https://docs.microsoft.com/windows/security/threat-protection/windows-defender-application-guard/wd-app-guard-overview
+ - linkListType: download
+ links:
+ - text: Evaluate the impact
+ url: /microsoft-edge/deploy/microsoft-edge-forrester
+
+ # Card (optional)
+ - title: Test your site on Microsoft Edge
+ linkLists:
+ - linkListType: overview
+ links:
+ - text: Test your site on Microsoft Edge for free on BrowserStack
+ url: https://developer.microsoft.com/microsoft-edge/tools/remote/
+ - text: Use sonarwhal to improve your website
+ url: https://sonarwhal.com/
+
+ # Card (optional)
+ - title: Improve compatibility with Enterprise Mode
+ linkLists:
+ - linkListType: how-to-guide
+ links:
+ - text: Use Enterprise mode to improve compatibility
+ url: /microsoft-edge/deploy/emie-to-improve-compatibility
+ - text: Turn on Enterprise Mode and use a site list
+ url: https://docs.microsoft.com/internet-explorer/ie11-deploy-guide/turn-on-enterprise-mode-and-use-a-site-list
+ - text: Enterprise Site List Portal
+ url: https://github.com/MicrosoftEdge/enterprise-mode-site-list-portal
+
+ # Card (optional)
+ - title: Web Application Compatibility Lab Kit
+ linkLists:
+ - linkListType: overview
+ links:
+ - text: Overview
+ url: /microsoft-edge/deploy/emie-to-improve-compatibility
+
+ # Card (optional)
+ - title: Security
+ linkLists:
+ - linkListType: download
+ links:
+ - text: NSS Labs web browser security reports
+ url: https://www.microsoft.com/download/details.aspx?id=54773
+ - linkListType: overview
+ links:
+ - text: Microsoft Edge sandbox
+ url: https://blogs.windows.com/msedgedev/2017/03/23/strengthening-microsoft-edge-sandbox/
+ - text: Windows Defender SmartScreen
+ url: https://docs.microsoft.com/windows/security/threat-protection/windows-defender-smartscreen/windows-defender-smartscreen-overview
+
+ # Card (optional)
+ - title: Deployment
+ linkLists:
+ - linkListType: overview
+ links:
+ - text: Microsoft Edge deployment guide
+ url: /microsoft-edge/deploy/
+ - text: Microsoft Edge FAQ
+ url: /microsoft-edge/deploy/microsoft-edge-faq
+ - text: System requirements and language support
+ url: /microsoft-edge/deploy/hardware-and-software-requirements
+ - text: Group Policy and MDM settings in Microsoft Edge
+ url: /microsoft-edge/deploy/available-policies
+ - text: Microsoft Edge training and demonstrations
+ url: /microsoft-edge/deploy/edge-technical-demos
+ - linkListType: download
+ links:
+ - text: Web Application Compatibility Lab Kit
+ url: https://www.microsoft.com/itpro/microsoft-edge/web-app-compat-toolkit
+
+ # Card (optional)
+ - title: End user readiness
+ linkLists:
+ - linkListType: video
+ links:
+ - text: Microsoft Edge tips and tricks (video, 20:26)
+ url: https://myignite.microsoft.com/sessions/56630?source=sessions
+ - linkListType: download
+ links:
+ - text: Quick Start - Microsoft Edge (PDF, .98 MB)
+ url: https://go.microsoft.com/fwlink/?linkid=825648
+ - text: Find it faster with Microsoft Edge (PDF, 605 KB)
+ url: https://go.microsoft.com/fwlink/?linkid=825661
+ - text: Use Microsoft Edge to collaborate (PDF, 468 KB)
+ url: https://go.microsoft.com/fwlink/?linkid=825653
+ - text: Group Policy and MDM settings in Microsoft Edge
+ url: /microsoft-edge/deploy/available-policies
+ - text: Microsoft Edge training and demonstrations
+ url: /microsoft-edge/deploy/edge-technical-demos
+ - linkListType: how-to-guide
+ links:
+ - text: Import bookmarks
+ url: https://microsoftedgetips.microsoft.com/2/39
+ - text: Password management
+ url: https://microsoftedgetips.microsoft.com/2/18
+
+ # Card (optional)
+ - title: Stay informed
+ linkLists:
+ - linkListType: overview
+ links:
+ - text: Sign up for the Windows IT Pro Insider
+ url: https://aka.ms/windows-it-pro-insider
+ - text: Microsoft Edge Dev blog
+ url: https://blogs.windows.com/msedgedev
+ - text: Microsoft Edge Dev on Twitter
+ url: https://twitter.com/MSEdgeDev
diff --git a/browsers/edge/troubleshooting-microsoft-edge.md b/browsers/edge/troubleshooting-microsoft-edge.md
index 3c50d4d50e..5479f689f3 100644
--- a/browsers/edge/troubleshooting-microsoft-edge.md
+++ b/browsers/edge/troubleshooting-microsoft-edge.md
@@ -9,7 +9,6 @@ author: dansimp
ms.author: dansimp
ms.prod: edge
ms.sitesec: library
-title: Deploy Microsoft Edge kiosk mode
ms.localizationpriority: medium
ms.date: 10/15/2018
---
diff --git a/browsers/edge/use-powershell-to manage-group-policy.md b/browsers/edge/use-powershell-to manage-group-policy.md
index 58a6b06b27..1b6d2e9338 100644
--- a/browsers/edge/use-powershell-to manage-group-policy.md
+++ b/browsers/edge/use-powershell-to manage-group-policy.md
@@ -5,7 +5,6 @@ ms.prod: edge
ms.mktglfcycl: explore
ms.sitesec: library
ms.pagetype: security
-title: Security enhancements for Microsoft Edge (Microsoft Edge for IT Pros)
ms.localizationpriority: medium
ms.date: 10/02/2018
ms.reviewer:
diff --git a/browsers/internet-explorer/TOC.md b/browsers/internet-explorer/TOC.md
index ceb4d9b0f2..060f6ffb99 100644
--- a/browsers/internet-explorer/TOC.md
+++ b/browsers/internet-explorer/TOC.md
@@ -188,5 +188,4 @@
### [Internet Explorer Setup command-line options and return codes](ie11-ieak/ie-setup-command-line-options-and-return-codes.md)
## KB Troubleshoot
-### [Clear the Internet Explorer cache from a command line](kb-support/clear-ie-cache-from-command-line.md)
### [Internet Explorer and Microsoft Edge FAQ for IT Pros](kb-support/ie-edge-faqs.md)
diff --git a/browsers/internet-explorer/docfx.json b/browsers/internet-explorer/docfx.json
index 50208546bb..a796135a6b 100644
--- a/browsers/internet-explorer/docfx.json
+++ b/browsers/internet-explorer/docfx.json
@@ -7,6 +7,7 @@
"**/*.yml"
],
"exclude": [
+ "**/includes/**",
"**/obj/**"
]
}
@@ -38,7 +39,16 @@
"folder_relative_path_in_docset": "./"
}
},
- "titleSuffix": "Internet Explorer"
+ "titleSuffix": "Internet Explorer",
+ "contributors_to_exclude": [
+ "rjagiewich",
+ "traya1",
+ "rmca14",
+ "claydetels19",
+ "jborsecnik",
+ "tiburd",
+ "garycentric"
+ ],
},
"externalReference": [],
"template": "op.html",
diff --git a/browsers/internet-explorer/ie11-deploy-guide/activex-installation-using-group-policy.md b/browsers/internet-explorer/ie11-deploy-guide/activex-installation-using-group-policy.md
index 8fe62f2f79..f09832c403 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/activex-installation-using-group-policy.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/activex-installation-using-group-policy.md
@@ -1,49 +1,53 @@
----
-ms.localizationpriority: medium
-ms.mktglfcycl: deploy
-ms.pagetype: security
-description: How to use Group Policy to install ActiveX controls.
-author: dansimp
-ms.prod: ie11
-ms.assetid: 59185370-558c-47e0-930c-8a5ed657e9e3
-ms.reviewer:
-audience: itpro
manager: dansimp
-ms.author: dansimp
-title: ActiveX installation using group policy (Internet Explorer 11 for IT Pros)
-ms.sitesec: library
-ms.date: 07/27/2017
----
-
-
-# Group Policy and ActiveX installation
-
-ActiveX controls are installed and invoked using the HTML object tag with the CODEBASE attribute. This attribute, through a URL, makes Internet Explorer:
-
-- Get the ActiveX control if it's not already installed.
-
-- Download the installation package.
-
-- Perform trust verification on the object.
-
-- Prompt for installation permission, using the IE Information Bar.
-
-During installation, the rendering page registers and invokes the control, so that after installation, any standard user can invoke the control.
-
-**Important** ActiveX control installation requires administrator-level permissions.
-
-## Group Policy for the ActiveX Installer Service
-
-You use the ActiveX Installer Service (AXIS) and Group Policy to manage your ActiveX control deployment. The AXIS-related settings can be changed using either the Group Policy Management Console (GPMC) or the Local Group Policy Editor, and include:
-
-- **Approved Installation Sites for ActiveX Controls.** A list of approved installation sites used by AXIS to determine whether it can install a particular ActiveX control.
-
-- **ActiveX installation policy for sites in trusted zones.** Identifies how AXIS should behave when a website tries to install an ActiveX control. First, AXIS looks to see if the site appears in either the list of approved installation sites or in the **Trusted sites** zone. If the does, then AXIS checks to make sure the control meets your company's policy requirements. If the ActiveX control meets all of these requirements, the control is installed.
-
-For more information about the ActiveX Installer Service, see [Administering the ActiveX Installer Service in Windows 7](https://go.microsoft.com/fwlink/p/?LinkId=214503).
-
-
-
-
-
-
-
+---
+ms.localizationpriority: medium
+ms.mktglfcycl: deploy
+ms.pagetype: security
+description: How to use Group Policy to install ActiveX controls.
+author: dansimp
+ms.prod: ie11
+ms.assetid: 59185370-558c-47e0-930c-8a5ed657e9e3
+ms.reviewer:
+audience: itpro
+manager: dansimp
+ms.author: dansimp
+title: ActiveX installation using group policy (Internet Explorer 11 for IT Pros)
+ms.sitesec: library
+ms.date: 07/27/2017
+---
+
+
+# Group Policy and ActiveX installation
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
+
+ActiveX controls are installed and invoked using the HTML object tag with the CODEBASE attribute. This attribute, through a URL, makes Internet Explorer:
+
+- Get the ActiveX control if it's not already installed.
+
+- Download the installation package.
+
+- Perform trust verification on the object.
+
+- Prompt for installation permission, using the IE Information Bar.
+
+During installation, the rendering page registers and invokes the control, so that after installation, any standard user can invoke the control.
+
+**Important** ActiveX control installation requires administrator-level permissions.
+
+## Group Policy for the ActiveX Installer Service
+
+You use the ActiveX Installer Service (AXIS) and Group Policy to manage your ActiveX control deployment. The AXIS-related settings can be changed using either the Group Policy Management Console (GPMC) or the Local Group Policy Editor, and include:
+
+- **Approved Installation Sites for ActiveX Controls.** A list of approved installation sites used by AXIS to determine whether it can install a particular ActiveX control.
+
+- **ActiveX installation policy for sites in trusted zones.** Identifies how AXIS should behave when a website tries to install an ActiveX control. First, AXIS looks to see if the site appears in either the list of approved installation sites or in the **Trusted sites** zone. If the does, then AXIS checks to make sure the control meets your company's policy requirements. If the ActiveX control meets all of these requirements, the control is installed.
+
+For more information about the ActiveX Installer Service, see [Administering the ActiveX Installer Service in Windows 7](https://go.microsoft.com/fwlink/p/?LinkId=214503).
+
+
+
+
+
+
+
diff --git a/browsers/internet-explorer/ie11-deploy-guide/add-employees-enterprise-mode-portal.md b/browsers/internet-explorer/ie11-deploy-guide/add-employees-enterprise-mode-portal.md
index 664bc596e1..455bae28bd 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/add-employees-enterprise-mode-portal.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/add-employees-enterprise-mode-portal.md
@@ -1,68 +1,72 @@
----
-ms.localizationpriority: medium
-ms.mktglfcycl: deploy
-ms.pagetype: appcompat
-description: Details about how to add employees to the Enterprise Mode Site List Portal.
-author: dansimp
-ms.prod: ie11
-title: Add employees to the Enterprise Mode Site List Portal (Internet Explorer 11 for IT Pros)
-ms.sitesec: library
-ms.date: 07/27/2017
-ms.reviewer:
-audience: itpro
manager: dansimp
-ms.author: dansimp
----
-
-# Add employees to the Enterprise Mode Site List Portal
-
-**Applies to:**
-
-- Windows 10
-- Windows 8.1
-- Windows 7
-- Windows Server 2012 R2
-- Windows Server 2008 R2 with Service Pack 1 (SP1)
-
-After you get the Enterprise Mode Site List Portal up and running, you must add your employees. During this process, you'll also assign roles and groups.
-
-The available roles are:
-
-- **Requester.** The primary role to assign to employees that need to access the Enterprise Mode Site List Portal. The Requester can create change requests, validate changes in the pre-production environment, rollback pre-production and production changes in case of failure, send personal approval requests, view personal change requests, and sign off and close personal change requests.
-
-- **App Manager.** This role is considered part of the Approvers group. The App Manager can approve change requests, validate changes in the pre-production environment, rollback pre-production and production changes in case of failure, send personal approval requests, view personal requests, and sign off and close personal requests.
-
-- **Group Head.** This role is considered part of the Approvers group. The Group Head can approve change requests, validate changes in the pre-production environment, rollback pre-production and production changes in case of failure, send personal approval requests, view personal requests, and sign off and close personal requests.
-
-- **Administrator.** The role with the highest-level rights; we recommend limiting the number of employees you grant this role. The Administrator can perform any task that can be performed by the other roles, in addition to adding employees to the portal, assigning employee roles, approving registrations to the portal, configuring portal settings (for example, determining the freeze schedule, determining the pre-production and production XML paths, and determining the attachment upload location), and using the standalone Enterprise Mode Site List Manager page.
-
-**To add an employee to the Enterprise Mode Site List Portal**
-1. Open the Enterprise Mode Site List Portal and click the **Employee Management** icon in the upper-right area of the page.
-
- The **Employee management** page appears.
-
-2. Click **Add a new employee**.
-
- The **Add a new employee** page appears.
-
-3. Fill out the fields for each employee, including:
-
- - **Email.** Add the employee's email address.
-
- - **Name.** This box autofills based on the email address.
-
- - **Role.** Pick a single role for the employee, based on the list above.
-
- - **Group name.** Pick the name of the employee's group. The group association also assigns a group of Approvers.
-
- - **Comments.** Add optional comments about the employee.
-
- - **Active.** Click the check box to make the employee active in the system. If you want to keep the employee in the system, but you want to prevent access, clear this check box.
-
-4. Click **Save**.
-
-**To export all employees to an Excel spreadsheet**
-1. On the **Employee management** page, click **Export to Excel**.
-
-2. Save the EnterpriseModeUsersList.xlsx file.
-
- The Excel file includes all employees with access to the Enterprise Mode Site List Portal, including user name, email address, role, and group name.
+---
+ms.localizationpriority: medium
+ms.mktglfcycl: deploy
+ms.pagetype: appcompat
+description: Details about how to add employees to the Enterprise Mode Site List Portal.
+author: dansimp
+ms.prod: ie11
+title: Add employees to the Enterprise Mode Site List Portal (Internet Explorer 11 for IT Pros)
+ms.sitesec: library
+ms.date: 07/27/2017
+ms.reviewer:
+audience: itpro
+manager: dansimp
+ms.author: dansimp
+---
+
+# Add employees to the Enterprise Mode Site List Portal
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
+
+**Applies to:**
+
+- Windows 10
+- Windows 8.1
+- Windows 7
+- Windows Server 2012 R2
+- Windows Server 2008 R2 with Service Pack 1 (SP1)
+
+After you get the Enterprise Mode Site List Portal up and running, you must add your employees. During this process, you'll also assign roles and groups.
+
+The available roles are:
+
+- **Requester.** The primary role to assign to employees that need to access the Enterprise Mode Site List Portal. The Requester can create change requests, validate changes in the pre-production environment, rollback pre-production and production changes in case of failure, send personal approval requests, view personal change requests, and sign off and close personal change requests.
+
+- **App Manager.** This role is considered part of the Approvers group. The App Manager can approve change requests, validate changes in the pre-production environment, rollback pre-production and production changes in case of failure, send personal approval requests, view personal requests, and sign off and close personal requests.
+
+- **Group Head.** This role is considered part of the Approvers group. The Group Head can approve change requests, validate changes in the pre-production environment, rollback pre-production and production changes in case of failure, send personal approval requests, view personal requests, and sign off and close personal requests.
+
+- **Administrator.** The role with the highest-level rights; we recommend limiting the number of employees you grant this role. The Administrator can perform any task that can be performed by the other roles, in addition to adding employees to the portal, assigning employee roles, approving registrations to the portal, configuring portal settings (for example, determining the freeze schedule, determining the pre-production and production XML paths, and determining the attachment upload location), and using the standalone Enterprise Mode Site List Manager page.
+
+**To add an employee to the Enterprise Mode Site List Portal**
+1. Open the Enterprise Mode Site List Portal and click the **Employee Management** icon in the upper-right area of the page.
+
+ The **Employee management** page appears.
+
+2. Click **Add a new employee**.
+
+ The **Add a new employee** page appears.
+
+3. Fill out the fields for each employee, including:
+
+ - **Email.** Add the employee's email address.
+
+ - **Name.** This box autofills based on the email address.
+
+ - **Role.** Pick a single role for the employee, based on the list above.
+
+ - **Group name.** Pick the name of the employee's group. The group association also assigns a group of Approvers.
+
+ - **Comments.** Add optional comments about the employee.
+
+ - **Active.** Click the check box to make the employee active in the system. If you want to keep the employee in the system, but you want to prevent access, clear this check box.
+
+4. Click **Save**.
+
+**To export all employees to an Excel spreadsheet**
+1. On the **Employee management** page, click **Export to Excel**.
+
+2. Save the EnterpriseModeUsersList.xlsx file.
+
+ The Excel file includes all employees with access to the Enterprise Mode Site List Portal, including user name, email address, role, and group name.
diff --git a/browsers/internet-explorer/ie11-deploy-guide/add-multiple-sites-to-enterprise-mode-site-list-using-the-version-1-schema-and-enterprise-mode-tool.md b/browsers/internet-explorer/ie11-deploy-guide/add-multiple-sites-to-enterprise-mode-site-list-using-the-version-1-schema-and-enterprise-mode-tool.md
index 8ead60630e..57c8991c7d 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/add-multiple-sites-to-enterprise-mode-site-list-using-the-version-1-schema-and-enterprise-mode-tool.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/add-multiple-sites-to-enterprise-mode-site-list-using-the-version-1-schema-and-enterprise-mode-tool.md
@@ -1,112 +1,116 @@
----
-ms.localizationpriority: medium
-ms.mktglfcycl: deploy
-ms.pagetype: appcompat
-description: You can add multiple sites to your Enterprise Mode site list by creating a custom text (TXT) or Extensible Markup Language (XML) file of problematic sites and then adding it in the Bulk add from file area of the Enterprise Mode Site List Manager.
-author: dansimp
-ms.prod: ie11
-ms.assetid: 20aF07c4-051a-451f-9c46-5a052d9Ae27c
-ms.reviewer:
-audience: itpro
manager: dansimp
-ms.author: dansimp
-title: Add multiple sites to the Enterprise Mode site list using a file and the Enterprise Mode Site List Manager (schema v.1) (Internet Explorer 11 for IT Pros)
-ms.sitesec: library
-ms.date: 07/27/2017
----
-
-
-# Add multiple sites to the Enterprise Mode site list using a file and the Enterprise Mode Site List Manager (schema v.1)
-
-**Applies to:**
-
-- Windows 8.1
-- Windows 7
-
-You can add multiple sites to your Enterprise Mode site list by creating a custom text (TXT) or Extensible Markup Language (XML) file of problematic sites and then adding it in the **Bulk add from file** area of the Enterprise Mode Site List Manager. You can only add specific URLs, not Internet or Intranet Zones.
-
-If you want to add your websites one at a time, see Add sites to the [Enterprise Mode site list using the Enterprise Mode Site List Manager (schema v.1)](add-single-sites-to-enterprise-mode-site-list-using-the-version-1-enterprise-mode-tool.md).
-
-## Create an Enterprise Mode site list (TXT) file
-You can create and use a custom text file to add multiple sites to your Enterprise Mode site list at the same time.
**Important** This text file is only lets you add multiple sites at the same time. You can’t use this file to deploy Enterprise Mode into your company.
-
-You must separate each site using commas or carriage returns. For example:
-
-```
-microsoft.com, bing.com, bing.com/images
-```
-**-OR-**
-
-```
-microsoft.com
-bing.com
-bing.com/images
-```
-
-## Create an Enterprise Mode site list (XML) file using the v.1 version of the Enterprise Mode schema
-You can create and use a custom XML file with the Enterprise Mode Site List Manager to add multiple sites to your Enterprise Mode site list at the same time. For more info about the v.1 version of the Enterprise Mode schema, see [Enterprise Mode schema v.1 guidance](enterprise-mode-schema-version-1-guidance.md).
-
-Each XML file must include:
-
-- **Version number.** This number must be incremented with each version of the Enterprise Mode site list, letting Internet Explorer know whether the list is new. Approximately 65 seconds after Internet Explorer 11 starts, it compares your site list version to the stored version number. If your file has a higher number, the newer version is loaded.
**Important** After this check, IE11 won’t look for an updated list again until you restart the browser.
-
-- **<emie> tag.** This tag specifies the domains and domain paths that must be rendered using IE7 Enterprise Mode, IE8 Enterprise Mode, or the default IE11 browser environment.
**Important** If you decide a site requires IE7 Enterprise Mode, you must add `forceCompatView=”true”` to your XML file. That code tells Enterprise Mode to check for a `DOCTYPE` tag on the specified webpage. If there is, the site renders using Windows Internet Explorer 7. If there’s no tag, the site renders using Microsoft Internet Explorer 5.
-
-- <docMode> tag.This tag specifies the domains and domain paths that need either to appear using the specific doc mode you assigned to the site. Enterprise Mode takes precedence over document modes, so sites that are already included in the Enterprise Mode site list won’t be affected by this update and will continue to load in Enterprise Mode, as usual. For more specific info about using document modes, see [Fix web compatibility issues using document modes and the Enterprise Mode site list](fix-compat-issues-with-doc-modes-and-enterprise-mode-site-list.md).
-
-### Enterprise Mode v.1 XML schema example
-The following is an example of what your XML file should look like when you’re done adding your sites. For more info about how to create your XML file, see [Enterprise Mode schema v.1 guidance](enterprise-mode-schema-version-1-guidance.md).
-
-```
-
-
- www.cpandl.com
- www.woodgrovebank.com
- adatum.com
- contoso.com
- relecloud.com
- /about
-
- fabrikam.com
- /products
-
-
-
- contoso.com
- /travel
-
- fabrikam.com
- /products
-
-
-
-```
-
-To make sure your site list is up-to-date; wait 65 seconds after opening IE and then check that the `CurrentVersion` value in the `HKEY\CURRENT\USER\Software\Microsoft\Internet Explorer\Main\EnterpriseMode\` registry key matches the version number in your file.
**Important** If `CurrentVersion` is not set or is wrong, it means that the XML parsing failed. This can mean that the XML file isn’t there, that there are access problems, or that the XML file format is wrong. Don’t manually change the `CurrentVersion` registry setting. You must make your changes to your site list and then update the list using the import function in the Enterprise Mode Site List Manager (.
-
-## Add multiple sites to the Enterprise Mode Site List Manager (schema v.1)
-After you create your .xml or .txt file, you can bulk add the sites to the Enterprise Mode Site List Manager (schema v.1).
-
- **To add multiple sites**
-
-1. In the Enterprise Mode Site List Manager (schema v.1), click **Bulk add from file**.
-
-2. Go to your site list (either .txt or .xml) to add the included sites to the tool, and then click **Open**.
-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-compat-issues-with-doc-modes-and-enterprise-mode-site-list.md).
-
-3. Click **OK** to close the **Bulk add sites to the list** menu.
-
-4. On the **File** menu, click **Save to XML**, and save your file.
-You can save the file locally or to a network share. However, you must make sure you deploy it to the location specified in your registry key. For more information about the registry key, see [Turn on Enterprise Mode and use a site list](turn-on-enterprise-mode-and-use-a-site-list.md).
-
-## Next steps
-After you’ve added all of your sites to the tool and saved the file to XML, you can configure the rest of the Enterprise Mode functionality to use it. You can also turn Enterprise Mode on locally, so your users have the option to use Enterprise Mode on individual websites from the **Tools** menu. For more information, see [Turn on local control and logging for Enterprise Mode](turn-on-local-control-and-logging-for-enterprise-mode.md).
-
-## Related topics
-- [Enterprise Mode schema v.1 guidance](enterprise-mode-schema-version-1-guidance.md)
-- [Download the Enterprise Mode Site List Manager (schema v.1)](https://go.microsoft.com/fwlink/p/?LinkID=394378)
-
-
-
-
-
-
+---
+ms.localizationpriority: medium
+ms.mktglfcycl: deploy
+ms.pagetype: appcompat
+description: You can add multiple sites to your Enterprise Mode site list by creating a custom text (TXT) or Extensible Markup Language (XML) file of problematic sites and then adding it in the Bulk add from file area of the Enterprise Mode Site List Manager.
+author: dansimp
+ms.prod: ie11
+ms.assetid: 20aF07c4-051a-451f-9c46-5a052d9Ae27c
+ms.reviewer:
+audience: itpro
+manager: dansimp
+ms.author: dansimp
+title: Add multiple sites to the Enterprise Mode site list using a file and the Enterprise Mode Site List Manager (schema v.1) (Internet Explorer 11 for IT Pros)
+ms.sitesec: library
+ms.date: 07/27/2017
+---
+
+
+# Add multiple sites to the Enterprise Mode site list using a file and the Enterprise Mode Site List Manager (schema v.1)
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
+
+**Applies to:**
+
+- Windows 8.1
+- Windows 7
+
+You can add multiple sites to your Enterprise Mode site list by creating a custom text (TXT) or Extensible Markup Language (XML) file of problematic sites and then adding it in the **Bulk add from file** area of the Enterprise Mode Site List Manager. You can only add specific URLs, not Internet or Intranet Zones.
+
+If you want to add your websites one at a time, see Add sites to the [Enterprise Mode site list using the Enterprise Mode Site List Manager (schema v.1)](add-single-sites-to-enterprise-mode-site-list-using-the-version-1-enterprise-mode-tool.md).
+
+## Create an Enterprise Mode site list (TXT) file
+You can create and use a custom text file to add multiple sites to your Enterprise Mode site list at the same time.
**Important** This text file is only lets you add multiple sites at the same time. You can’t use this file to deploy Enterprise Mode into your company.
+
+You must separate each site using commas or carriage returns. For example:
+
+```
+microsoft.com, bing.com, bing.com/images
+```
+**-OR-**
+
+```
+microsoft.com
+bing.com
+bing.com/images
+```
+
+## Create an Enterprise Mode site list (XML) file using the v.1 version of the Enterprise Mode schema
+You can create and use a custom XML file with the Enterprise Mode Site List Manager to add multiple sites to your Enterprise Mode site list at the same time. For more info about the v.1 version of the Enterprise Mode schema, see [Enterprise Mode schema v.1 guidance](enterprise-mode-schema-version-1-guidance.md).
+
+Each XML file must include:
+
+- **Version number.** This number must be incremented with each version of the Enterprise Mode site list, letting Internet Explorer know whether the list is new. Approximately 65 seconds after Internet Explorer 11 starts, it compares your site list version to the stored version number. If your file has a higher number, the newer version is loaded.
**Important** After this check, IE11 won’t look for an updated list again until you restart the browser.
+
+- **<emie> tag.** This tag specifies the domains and domain paths that must be rendered using IE7 Enterprise Mode, IE8 Enterprise Mode, or the default IE11 browser environment.
**Important** If you decide a site requires IE7 Enterprise Mode, you must add `forceCompatView=”true”` to your XML file. That code tells Enterprise Mode to check for a `DOCTYPE` tag on the specified webpage. If there is, the site renders using Windows Internet Explorer 7. If there’s no tag, the site renders using Microsoft Internet Explorer 5.
+
+- <docMode> tag.This tag specifies the domains and domain paths that need either to appear using the specific doc mode you assigned to the site. Enterprise Mode takes precedence over document modes, so sites that are already included in the Enterprise Mode site list won’t be affected by this update and will continue to load in Enterprise Mode, as usual. For more specific info about using document modes, see [Fix web compatibility issues using document modes and the Enterprise Mode site list](fix-compat-issues-with-doc-modes-and-enterprise-mode-site-list.md).
+
+### Enterprise Mode v.1 XML schema example
+The following is an example of what your XML file should look like when you’re done adding your sites. For more info about how to create your XML file, see [Enterprise Mode schema v.1 guidance](enterprise-mode-schema-version-1-guidance.md).
+
+```
+
+
+ www.cpandl.com
+ www.woodgrovebank.com
+ adatum.com
+ contoso.com
+ relecloud.com
+ /about
+
+ fabrikam.com
+ /products
+
+
+
+ contoso.com
+ /travel
+
+ fabrikam.com
+ /products
+
+
+
+```
+
+To make sure your site list is up-to-date; wait 65 seconds after opening IE and then check that the `CurrentVersion` value in the `HKEY\CURRENT\USER\Software\Microsoft\Internet Explorer\Main\EnterpriseMode\` registry key matches the version number in your file.
**Important** If `CurrentVersion` is not set or is wrong, it means that the XML parsing failed. This can mean that the XML file isn’t there, that there are access problems, or that the XML file format is wrong. Don’t manually change the `CurrentVersion` registry setting. You must make your changes to your site list and then update the list using the import function in the Enterprise Mode Site List Manager (.
+
+## Add multiple sites to the Enterprise Mode Site List Manager (schema v.1)
+After you create your .xml or .txt file, you can bulk add the sites to the Enterprise Mode Site List Manager (schema v.1).
+
+ **To add multiple sites**
+
+1. In the Enterprise Mode Site List Manager (schema v.1), click **Bulk add from file**.
+
+2. Go to your site list (either .txt or .xml) to add the included sites to the tool, and then click **Open**.
+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-compat-issues-with-doc-modes-and-enterprise-mode-site-list.md).
+
+3. Click **OK** to close the **Bulk add sites to the list** menu.
+
+4. On the **File** menu, click **Save to XML**, and save your file.
+You can save the file locally or to a network share. However, you must make sure you deploy it to the location specified in your registry key. For more information about the registry key, see [Turn on Enterprise Mode and use a site list](turn-on-enterprise-mode-and-use-a-site-list.md).
+
+## Next steps
+After you’ve added all of your sites to the tool and saved the file to XML, you can configure the rest of the Enterprise Mode functionality to use it. You can also turn Enterprise Mode on locally, so your users have the option to use Enterprise Mode on individual websites from the **Tools** menu. For more information, see [Turn on local control and logging for Enterprise Mode](turn-on-local-control-and-logging-for-enterprise-mode.md).
+
+## Related topics
+- [Enterprise Mode schema v.1 guidance](enterprise-mode-schema-version-1-guidance.md)
+- [Download the Enterprise Mode Site List Manager (schema v.1)](https://go.microsoft.com/fwlink/p/?LinkID=394378)
+
+
+
+
+
+
diff --git a/browsers/internet-explorer/ie11-deploy-guide/add-multiple-sites-to-enterprise-mode-site-list-using-the-version-2-schema-and-enterprise-mode-tool.md b/browsers/internet-explorer/ie11-deploy-guide/add-multiple-sites-to-enterprise-mode-site-list-using-the-version-2-schema-and-enterprise-mode-tool.md
index 78f0903d6f..37ef55dea6 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/add-multiple-sites-to-enterprise-mode-site-list-using-the-version-2-schema-and-enterprise-mode-tool.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/add-multiple-sites-to-enterprise-mode-site-list-using-the-version-2-schema-and-enterprise-mode-tool.md
@@ -16,7 +16,10 @@ ms.date: 10/24/2017
---
-# Add multiple sites to the Enterprise Mode site list using a file and the Enterprise Mode Site List Manager (schema v.2)
+# Add multiple sites to the Enterprise Mode site list using a file and the Enterprise Mode Site List Manager (schema v.2)
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
**Applies to:**
diff --git a/browsers/internet-explorer/ie11-deploy-guide/add-single-sites-to-enterprise-mode-site-list-using-the-version-1-enterprise-mode-tool.md b/browsers/internet-explorer/ie11-deploy-guide/add-single-sites-to-enterprise-mode-site-list-using-the-version-1-enterprise-mode-tool.md
index 8b8435daff..8c5e4b4426 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/add-single-sites-to-enterprise-mode-site-list-using-the-version-1-enterprise-mode-tool.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/add-single-sites-to-enterprise-mode-site-list-using-the-version-1-enterprise-mode-tool.md
@@ -1,66 +1,70 @@
----
-ms.localizationpriority: medium
-ms.mktglfcycl: deploy
-ms.pagetype: appcompat
-description: Enterprise Mode is a compatibility mode that runs on Internet Explorer 11, letting websites render using a modified browser configuration that's designed to emulate either Windows Internet Explorer 7 or Windows Internet Explorer 8, avoiding the common compatibility problems associated with web apps written and tested on older versions of Internet Explorer.
-author: dansimp
-ms.prod: ie11
-ms.assetid: 042e44e8-568d-4717-8fd3-69dd198bbf26
-ms.reviewer:
-audience: itpro
manager: dansimp
-ms.author: dansimp
-title: Add sites to the Enterprise Mode site list using the Enterprise Mode Site List Manager (schema v.1) (Internet Explorer 11 for IT Pros)
-ms.sitesec: library
-ms.date: 07/27/2017
----
-
-
-# Add single sites to the Enterprise Mode site list using the Enterprise Mode Site List Manager (schema v.1)
-
-**Applies to:**
-
-- Windows 8.1
-- Windows 7
-- Windows Server 2008 R2 with Service Pack 1 (SP1)
-
-Enterprise Mode is a compatibility mode that runs on Internet Explorer 11, letting websites render using a modified browser configuration that’s designed to emulate either Windows Internet Explorer 7 or Windows Internet Explorer 8, avoiding the common compatibility problems associated with web apps written and tested on older versions of Internet Explorer.
**Important** You can only add specific URLs, not Internet or Intranet Zones.
-
-
Note If you're using the v.2 version of the Enterprise Mode schema, you'll need to use the Enterprise Mode Site List Manager (schema v.1). For more info, see Add sites to the Enterprise Mode site list using the Enterprise Mode Site List Manager (schema v.2).
-
- **To add a site to your compatibility list using the Enterprise Mode Site List Manager (schema v.1)**
-
-1. In the Enterprise Mode Site List Manager (schema v.1), click **Add**.
-
-2. Type the URL for the website that’s experiencing compatibility problems, like *<domain>.com* or *<domain>.com*/*<path>* into the **URL** box.
-Don't include the `https://` or `https://` designation. The tool automatically tries both versions during validation.
-
-3. Type any comments about the website into the **Notes about URL** box.
-Administrators can only see comments while they’re in this tool.
-
-4. Choose **IE7 Enterprise Mode**, **IE8 Enterprise Mode**, or the appropriate document mode for sites that must be rendered using the emulation of a previous version of IE, or pick **Default IE** if the site should use the latest version of IE.
-
-The path within a domain can require a different compatibility mode from the domain itself. For example, the domain might look fine in the default IE11 browser, but the path might have problems and require the use of Enterprise Mode. If you added the domain previously, your original compatibility choice is still selected. However, if the domain is new, **IE8 Enterprise Mode** is automatically selected.
-
-Enterprise Mode takes precedence over document modes, so sites that are already included in the Enterprise Mode site list won’t be affected by this update and will continue to load in Enterprise Mode, as usual. For more specific info about using document modes, see [Fix web compatibility issues using document modes and the Enterprise Mode site list](fix-compat-issues-with-doc-modes-and-enterprise-mode-site-list.md).
-
-5. Click **Save** to validate your website and to add it to the site list for your enterprise.
- If your site passes validation, it’s added to the global compatibility list. If the site doesn’t pass validation, you’ll get an error message explaining the problem. You’ll then be able to either cancel the site or ignore the validation problem and add it to your list anyway.
-
-6. On the **File** menu, go to where you want to save the file, and then click **Save to XML**.
- You can save the file locally or to a network share. However, you must make sure you deploy it to the location specified in your registry key. For more information about the registry key, see [Turn on local control and logging for Enterprise Mode](turn-on-local-control-and-logging-for-enterprise-mode.md).
-
-## Next steps
-After you’ve added all of your sites to the tool and saved the file to XML, you can configure the rest of the Enterprise Mode functionality to use it. You can also turn Enterprise Mode on locally, so your users have the option to use Enterprise Mode on individual websites from the **Tools** menu. For more information, see [Turn on local control and logging for Enterprise Mode](turn-on-local-control-and-logging-for-enterprise-mode.md).
-
-## Related topics
-- [Download the Enterprise Mode Site List Manager (schema v.1)](https://go.microsoft.com/fwlink/p/?LinkID=394378)
-
-
-
-
-
-
+---
+ms.localizationpriority: medium
+ms.mktglfcycl: deploy
+ms.pagetype: appcompat
+description: Enterprise Mode is a compatibility mode that runs on Internet Explorer 11, letting websites render using a modified browser configuration that's designed to emulate either Windows Internet Explorer 7 or Windows Internet Explorer 8, avoiding the common compatibility problems associated with web apps written and tested on older versions of Internet Explorer.
+author: dansimp
+ms.prod: ie11
+ms.assetid: 042e44e8-568d-4717-8fd3-69dd198bbf26
+ms.reviewer:
+audience: itpro
+manager: dansimp
+ms.author: dansimp
+title: Add sites to the Enterprise Mode site list using the Enterprise Mode Site List Manager (schema v.1) (Internet Explorer 11 for IT Pros)
+ms.sitesec: library
+ms.date: 07/27/2017
+---
+
+
+# Add single sites to the Enterprise Mode site list using the Enterprise Mode Site List Manager (schema v.1)
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
+
+**Applies to:**
+
+- Windows 8.1
+- Windows 7
+- Windows Server 2008 R2 with Service Pack 1 (SP1)
+
+Enterprise Mode is a compatibility mode that runs on Internet Explorer 11, letting websites render using a modified browser configuration that’s designed to emulate either Windows Internet Explorer 7 or Windows Internet Explorer 8, avoiding the common compatibility problems associated with web apps written and tested on older versions of Internet Explorer.
**Important** You can only add specific URLs, not Internet or Intranet Zones.
+
+
Note If you're using the v.2 version of the Enterprise Mode schema, you'll need to use the Enterprise Mode Site List Manager (schema v.1). For more info, see Add sites to the Enterprise Mode site list using the Enterprise Mode Site List Manager (schema v.2).
+
+ **To add a site to your compatibility list using the Enterprise Mode Site List Manager (schema v.1)**
+
+1. In the Enterprise Mode Site List Manager (schema v.1), click **Add**.
+
+2. Type the URL for the website that’s experiencing compatibility problems, like *<domain>.com* or *<domain>.com*/*<path>* into the **URL** box.
+Don't include the `https://` or `https://` designation. The tool automatically tries both versions during validation.
+
+3. Type any comments about the website into the **Notes about URL** box.
+Administrators can only see comments while they’re in this tool.
+
+4. Choose **IE7 Enterprise Mode**, **IE8 Enterprise Mode**, or the appropriate document mode for sites that must be rendered using the emulation of a previous version of IE, or pick **Default IE** if the site should use the latest version of IE.
+
+The path within a domain can require a different compatibility mode from the domain itself. For example, the domain might look fine in the default IE11 browser, but the path might have problems and require the use of Enterprise Mode. If you added the domain previously, your original compatibility choice is still selected. However, if the domain is new, **IE8 Enterprise Mode** is automatically selected.
+
+Enterprise Mode takes precedence over document modes, so sites that are already included in the Enterprise Mode site list won’t be affected by this update and will continue to load in Enterprise Mode, as usual. For more specific info about using document modes, see [Fix web compatibility issues using document modes and the Enterprise Mode site list](fix-compat-issues-with-doc-modes-and-enterprise-mode-site-list.md).
+
+5. Click **Save** to validate your website and to add it to the site list for your enterprise.
+ If your site passes validation, it’s added to the global compatibility list. If the site doesn’t pass validation, you’ll get an error message explaining the problem. You’ll then be able to either cancel the site or ignore the validation problem and add it to your list anyway.
+
+6. On the **File** menu, go to where you want to save the file, and then click **Save to XML**.
+ You can save the file locally or to a network share. However, you must make sure you deploy it to the location specified in your registry key. For more information about the registry key, see [Turn on local control and logging for Enterprise Mode](turn-on-local-control-and-logging-for-enterprise-mode.md).
+
+## Next steps
+After you’ve added all of your sites to the tool and saved the file to XML, you can configure the rest of the Enterprise Mode functionality to use it. You can also turn Enterprise Mode on locally, so your users have the option to use Enterprise Mode on individual websites from the **Tools** menu. For more information, see [Turn on local control and logging for Enterprise Mode](turn-on-local-control-and-logging-for-enterprise-mode.md).
+
+## Related topics
+- [Download the Enterprise Mode Site List Manager (schema v.1)](https://go.microsoft.com/fwlink/p/?LinkID=394378)
+
+
+
+
+
+
diff --git a/browsers/internet-explorer/ie11-deploy-guide/add-single-sites-to-enterprise-mode-site-list-using-the-version-2-enterprise-mode-tool.md b/browsers/internet-explorer/ie11-deploy-guide/add-single-sites-to-enterprise-mode-site-list-using-the-version-2-enterprise-mode-tool.md
index 0977b87b94..63f0d7bd6f 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/add-single-sites-to-enterprise-mode-site-list-using-the-version-2-enterprise-mode-tool.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/add-single-sites-to-enterprise-mode-site-list-using-the-version-2-enterprise-mode-tool.md
@@ -16,7 +16,10 @@ ms.date: 07/27/2017
---
-# Add single sites to the Enterprise Mode site list using the Enterprise Mode Site List Manager (schema v.2)
+# Add single sites to the Enterprise Mode site list using the Enterprise Mode Site List Manager (schema v.2)
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
**Applies to:**
diff --git a/browsers/internet-explorer/ie11-deploy-guide/administrative-templates-and-ie11.md b/browsers/internet-explorer/ie11-deploy-guide/administrative-templates-and-ie11.md
index f08c08fcdb..23bb9ee14a 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/administrative-templates-and-ie11.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/administrative-templates-and-ie11.md
@@ -1,82 +1,86 @@
----
-ms.localizationpriority: medium
-ms.mktglfcycl: deploy
-ms.pagetype: security
-description: Administrative templates and Internet Explorer 11
-author: dansimp
-ms.prod: ie11
-ms.assetid: 2b390786-f786-41cc-bddc-c55c8a4c5af3
-ms.reviewer:
-audience: itpro
manager: dansimp
-ms.author: dansimp
-title: Administrative templates and Internet Explorer 11 (Internet Explorer 11 for IT Pros)
-ms.sitesec: library
-ms.date: 07/27/2017
----
-
-
-# Administrative templates and Internet Explorer 11
-
-Administrative Templates are made up of a hierarchy of policy categories and subcategories that define how your policy settings appear in the Local Group Policy Editor, including:
-
-- What registry locations correspond to each setting.
-
-- What value options or restrictions are associated with each setting.
-
-- The default value for many settings.
-
-- Text explanations about each setting and the supported version of Internet Explorer.
-
-For a conceptual overview of Administrative Templates, see [Managing Group Policy ADMX Files Step-by-Step Guide](https://go.microsoft.com/fwlink/p/?LinkId=214519).
-
-## What are Administrative Templates?
-Administrative Templates are XML-based, multi-language files that define the registry-based Group Policy settings in the Local Group Policy Editor. There are two types of Administrative Templates:
-
-- **ADMX.** A language-neutral setup file that states the number and type of policy setting, and the location by category, as it shows up in the Local Group Policy Editor.
-
-- **ADML.** A language-specific setup file that provides language-related information to the ADMX file. This file lets the policy setting show up in the right language in the Local Group Policy Editor. You can add new languages by adding new ADML files in the required language.
-
-## How do I store Administrative Templates?
-As an admin, you can create a central store folder on your SYSVOL directory, named **PolicyDefinitions**. For example, %*SystemRoot*%\\PolicyDefinitions. This folder provides a single, centralized storage location for your Administrative Templates (both ADMX and ADML) files, so they can be used by your domain-based Group Policy Objects (GPOs).
-
Important Your Group Policy tools use the ADMX files in your store, ignoring any local copies. For more information about creating a central store, see Scenario 1: Editing the Local GPO Using ADMX Files.
-
-## Administrative Templates-related Group Policy settings
-When you install Internet Explorer 11, it updates the local administrative files, Inetres.admx and Inetres.adml, both located in the **PolicyDefinitions** folder.
-
Note You won't see the new policy settings if you try to view or edit your policy settings on a computer that isn't running IE11. To fix this, you can either install IE11, or you can copy the updated Inetres.admx and Inetres.adml files from another computer to the PolicyDefinitions folder on this computer.
-
-IE11 provides these new policy settings, which are editable in the Local Group Policy Editor, and appear in the following policy paths:
-
-- Computer Configuration\\Administrative Templates\\Windows Components\\
-
-- User Configuration\\Administrative Templates\\Windows Components\\
-
-
-|Catalog |Description |
-| ------------------------------------------------ | --------------------------------------------|
-|IE |Turns standard IE configuration on and off. |
-|Internet Explorer\Accelerators |Sets up and manages Accelerators. |
-|Internet Explorer\Administrator Approved Controls |Turns ActiveX controls on and off. |
-|Internet Explorer\Application Compatibility |Turns the **Cut**, **Copy**, or **Paste** operations on or off. This setting also requires that `URLACTION_SCRIPT_PASTE` is set to **Prompt**. |
-|Internet Explorer\Browser Menus |Shows or hides the IE menus and menu options.|
-|Internet Explorer\Corporate Settings |Turns off whether you specify the code download path for each computer. |
-|Internet Explorer\Delete Browsing History |Turns the **Delete Browsing History** settings on and off. |
-|Internet Explorer\Internet Control Panel |Turns pages on and off in the **Internet Options** dialog box. Also turns on and off the subcategories that manage settings on the **Content**, **General**, **Security** and **Advanced** pages. |
-|Internet Explorer\Internet Settings |Sets up and manages the **Advanced settings**, **AutoComplete**, **Display Settings**, and **URL Encoding** options. |
-|Internet Explorer\Persistence Behavior |Sets up and manages the file size limits for Internet security zones. |
-|Internet Explorer\Privacy |Turns various privacy-related features on and off. |
-|Internet Explorer\Security Features |Turns various security-related features on and off in the browser, Windows Explorer, and other applications. |
-|Internet Explorer\Toolbars |Turns on and off the ability for users to edit toolbars in the browser. You can also set the default toolbar buttons here. |
-|RSS Feeds |Sets up and manages RSS feeds in the browser. |
-
-
-## Editing Group Policy settings
-Regardless which tool you're using to edit your Group Policy settings, you'll need to follow one of these guides for step-by-step editing instructions:
-
-- **If you're using the Group Policy Management Console (GPMC) or the Local Group Policy Editor.** See [Edit Administrative Template Policy Settings](https://go.microsoft.com/fwlink/p/?LinkId=214521) for step-by-step instructions about editing your Administrative Templates.
-
-- **If you're using GPMC with Advanced Group Policy Management (AGPM).** See [Checklist: Create, Edit, and Deploy a GPO](https://go.microsoft.com/fwlink/p/?LinkId=214522) for step-by-step instructions about how to check out a GPO from the AGPM archive, edit it, and request deployment.
-
-## Related topics
-- [Administrative templates (.admx) for Windows 10 April 2018 Update](https://www.microsoft.com/download/details.aspx?id=56880)
-- [Administrative templates (.admx) for Windows 10 October 2018 Update](https://www.microsoft.com/download/details.aspx?id=57576)
-- [Administrative Templates (.admx) for Windows 8.1 and Windows Server 2012 R2](https://go.microsoft.com/fwlink/p/?LinkId=746580)
+---
+ms.localizationpriority: medium
+ms.mktglfcycl: deploy
+ms.pagetype: security
+description: Administrative templates and Internet Explorer 11
+author: dansimp
+ms.prod: ie11
+ms.assetid: 2b390786-f786-41cc-bddc-c55c8a4c5af3
+ms.reviewer:
+audience: itpro
+manager: dansimp
+ms.author: dansimp
+title: Administrative templates and Internet Explorer 11 (Internet Explorer 11 for IT Pros)
+ms.sitesec: library
+ms.date: 07/27/2017
+---
+
+
+# Administrative templates and Internet Explorer 11
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
+
+Administrative Templates are made up of a hierarchy of policy categories and subcategories that define how your policy settings appear in the Local Group Policy Editor, including:
+
+- What registry locations correspond to each setting.
+
+- What value options or restrictions are associated with each setting.
+
+- The default value for many settings.
+
+- Text explanations about each setting and the supported version of Internet Explorer.
+
+For a conceptual overview of Administrative Templates, see [Managing Group Policy ADMX Files Step-by-Step Guide](https://go.microsoft.com/fwlink/p/?LinkId=214519).
+
+## What are Administrative Templates?
+Administrative Templates are XML-based, multi-language files that define the registry-based Group Policy settings in the Local Group Policy Editor. There are two types of Administrative Templates:
+
+- **ADMX.** A language-neutral setup file that states the number and type of policy setting, and the location by category, as it shows up in the Local Group Policy Editor.
+
+- **ADML.** A language-specific setup file that provides language-related information to the ADMX file. This file lets the policy setting show up in the right language in the Local Group Policy Editor. You can add new languages by adding new ADML files in the required language.
+
+## How do I store Administrative Templates?
+As an admin, you can create a central store folder on your SYSVOL directory, named **PolicyDefinitions**. For example, %*SystemRoot*%\\PolicyDefinitions. This folder provides a single, centralized storage location for your Administrative Templates (both ADMX and ADML) files, so they can be used by your domain-based Group Policy Objects (GPOs).
+
Important Your Group Policy tools use the ADMX files in your store, ignoring any local copies. For more information about creating a central store, see Scenario 1: Editing the Local GPO Using ADMX Files.
+
+## Administrative Templates-related Group Policy settings
+When you install Internet Explorer 11, it updates the local administrative files, Inetres.admx and Inetres.adml, both located in the **PolicyDefinitions** folder.
+
Note You won't see the new policy settings if you try to view or edit your policy settings on a computer that isn't running IE11. To fix this, you can either install IE11, or you can copy the updated Inetres.admx and Inetres.adml files from another computer to the PolicyDefinitions folder on this computer.
+
+IE11 provides these new policy settings, which are editable in the Local Group Policy Editor, and appear in the following policy paths:
+
+- Computer Configuration\\Administrative Templates\\Windows Components\\
+
+- User Configuration\\Administrative Templates\\Windows Components\\
+
+
+|Catalog |Description |
+| ------------------------------------------------ | --------------------------------------------|
+|IE |Turns standard IE configuration on and off. |
+|Internet Explorer\Accelerators |Sets up and manages Accelerators. |
+|Internet Explorer\Administrator Approved Controls |Turns ActiveX controls on and off. |
+|Internet Explorer\Application Compatibility |Turns the **Cut**, **Copy**, or **Paste** operations on or off. This setting also requires that `URLACTION_SCRIPT_PASTE` is set to **Prompt**. |
+|Internet Explorer\Browser Menus |Shows or hides the IE menus and menu options.|
+|Internet Explorer\Corporate Settings |Turns off whether you specify the code download path for each computer. |
+|Internet Explorer\Delete Browsing History |Turns the **Delete Browsing History** settings on and off. |
+|Internet Explorer\Internet Control Panel |Turns pages on and off in the **Internet Options** dialog box. Also turns on and off the subcategories that manage settings on the **Content**, **General**, **Security** and **Advanced** pages. |
+|Internet Explorer\Internet Settings |Sets up and manages the **Advanced settings**, **AutoComplete**, **Display Settings**, and **URL Encoding** options. |
+|Internet Explorer\Persistence Behavior |Sets up and manages the file size limits for Internet security zones. |
+|Internet Explorer\Privacy |Turns various privacy-related features on and off. |
+|Internet Explorer\Security Features |Turns various security-related features on and off in the browser, Windows Explorer, and other applications. |
+|Internet Explorer\Toolbars |Turns on and off the ability for users to edit toolbars in the browser. You can also set the default toolbar buttons here. |
+|RSS Feeds |Sets up and manages RSS feeds in the browser. |
+
+
+## Editing Group Policy settings
+Regardless which tool you're using to edit your Group Policy settings, you'll need to follow one of these guides for step-by-step editing instructions:
+
+- **If you're using the Group Policy Management Console (GPMC) or the Local Group Policy Editor.** See [Edit Administrative Template Policy Settings](https://go.microsoft.com/fwlink/p/?LinkId=214521) for step-by-step instructions about editing your Administrative Templates.
+
+- **If you're using GPMC with Advanced Group Policy Management (AGPM).** See [Checklist: Create, Edit, and Deploy a GPO](https://go.microsoft.com/fwlink/p/?LinkId=214522) for step-by-step instructions about how to check out a GPO from the AGPM archive, edit it, and request deployment.
+
+## Related topics
+- [Administrative templates (.admx) for Windows 10 April 2018 Update](https://www.microsoft.com/download/details.aspx?id=56880)
+- [Administrative templates (.admx) for Windows 10 October 2018 Update](https://www.microsoft.com/download/details.aspx?id=57576)
+- [Administrative Templates (.admx) for Windows 8.1 and Windows Server 2012 R2](https://go.microsoft.com/fwlink/p/?LinkId=746580)
diff --git a/browsers/internet-explorer/ie11-deploy-guide/approve-change-request-enterprise-mode-portal.md b/browsers/internet-explorer/ie11-deploy-guide/approve-change-request-enterprise-mode-portal.md
index 977e17394e..07687792a3 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/approve-change-request-enterprise-mode-portal.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/approve-change-request-enterprise-mode-portal.md
@@ -1,62 +1,66 @@
----
-ms.localizationpriority: medium
-ms.mktglfcycl: deploy
-ms.pagetype: appcompat
-description: Details about how Approvers can approve open change requests in the Enterprise Mode Site List Portal.
-author: dansimp
-ms.prod: ie11
-title: Approve a change request using the Enterprise Mode Site List Portal (Internet Explorer 11 for IT Pros)
-ms.sitesec: library
-ms.date: 07/27/2017
-ms.reviewer:
-audience: itpro
manager: dansimp
-ms.author: dansimp
----
-
-# Approve a change request using the Enterprise Mode Site List Portal
-
-**Applies to:**
-
-- Windows 10
-- Windows 8.1
-- Windows 7
-- Windows Server 2012 R2
-- Windows Server 2008 R2 with Service Pack 1 (SP1)
-
-After a change request is successfully submitted to the pre-defined Approver(s), employees granted the role of **App Manager**, **Group Head**, or **Administrator**, they must approve the changes.
-
-## Approve or reject a change request
-The Approvers get an email stating that a Requester successfully opened, tested, and submitted the change request to the Approvers group. The Approvers can accept or reject a change request.
-
-**To approve or reject a change request**
-1. The Approver logs onto the Enterprise Mode Site List Portal, **All Approvals** page.
-
- The Approver can also get to the **All Approvals** page by clicking **Approvals Pending** from the left pane.
-
-2. The Approver clicks the expander arrow (**\/**) to the right side of the change request, showing the list of Approvers and the **Approve** and **Reject** buttons.
-
-3. The Approver reviews the change request, making sure it's correct. If the info is correct, the Approver clicks **Approve** to approve the change request. If the info seems incorrect, or if the app shouldn't be added to the site list, the Approver clicks **Reject**.
-
- An email is sent to the Requester, the Approver(s) group, and the Administrator(s) group, with the updated status of the request.
-
-
-## Send a reminder to the Approver(s) group
-If the change request is sitting in the approval queue for too long, the Requester can send a reminder to the group.
-
-- From the **My Approvals** page, click the checkbox next to the name of each Approver to be reminded, and then click **Send reminder**.
-
- An email is sent to the selected Approver(s).
-
-
-## View rejected change requests
-The original Requester, the Approver(s) group, and the Administrator(s) group can all view the rejected change request.
-
-**To view the rejected change request**
-
-- In the Enterprise Mode Site List Portal, click **Rejected** from the left pane.
-
- All rejected change requests appear, with role assignment determining which ones are visible.
-
-
-## Next steps
-After an Approver approves the change request, it must be scheduled for inclusion in the production Enterprise Mode Site List. For the scheduling steps, see the [Schedule approved change requests for production using the Enterprise Mode Site List Portal](schedule-production-change-enterprise-mode-portal.md) topic.
+---
+ms.localizationpriority: medium
+ms.mktglfcycl: deploy
+ms.pagetype: appcompat
+description: Details about how Approvers can approve open change requests in the Enterprise Mode Site List Portal.
+author: dansimp
+ms.prod: ie11
+title: Approve a change request using the Enterprise Mode Site List Portal (Internet Explorer 11 for IT Pros)
+ms.sitesec: library
+ms.date: 07/27/2017
+ms.reviewer:
+audience: itpro
+manager: dansimp
+ms.author: dansimp
+---
+
+# Approve a change request using the Enterprise Mode Site List Portal
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
+
+**Applies to:**
+
+- Windows 10
+- Windows 8.1
+- Windows 7
+- Windows Server 2012 R2
+- Windows Server 2008 R2 with Service Pack 1 (SP1)
+
+After a change request is successfully submitted to the pre-defined Approver(s), employees granted the role of **App Manager**, **Group Head**, or **Administrator**, they must approve the changes.
+
+## Approve or reject a change request
+The Approvers get an email stating that a Requester successfully opened, tested, and submitted the change request to the Approvers group. The Approvers can accept or reject a change request.
+
+**To approve or reject a change request**
+1. The Approver logs onto the Enterprise Mode Site List Portal, **All Approvals** page.
+
+ The Approver can also get to the **All Approvals** page by clicking **Approvals Pending** from the left pane.
+
+2. The Approver clicks the expander arrow (**\/**) to the right side of the change request, showing the list of Approvers and the **Approve** and **Reject** buttons.
+
+3. The Approver reviews the change request, making sure it's correct. If the info is correct, the Approver clicks **Approve** to approve the change request. If the info seems incorrect, or if the app shouldn't be added to the site list, the Approver clicks **Reject**.
+
+ An email is sent to the Requester, the Approver(s) group, and the Administrator(s) group, with the updated status of the request.
+
+
+## Send a reminder to the Approver(s) group
+If the change request is sitting in the approval queue for too long, the Requester can send a reminder to the group.
+
+- From the **My Approvals** page, click the checkbox next to the name of each Approver to be reminded, and then click **Send reminder**.
+
+ An email is sent to the selected Approver(s).
+
+
+## View rejected change requests
+The original Requester, the Approver(s) group, and the Administrator(s) group can all view the rejected change request.
+
+**To view the rejected change request**
+
+- In the Enterprise Mode Site List Portal, click **Rejected** from the left pane.
+
+ All rejected change requests appear, with role assignment determining which ones are visible.
+
+
+## Next steps
+After an Approver approves the change request, it must be scheduled for inclusion in the production Enterprise Mode Site List. For the scheduling steps, see the [Schedule approved change requests for production using the Enterprise Mode Site List Portal](schedule-production-change-enterprise-mode-portal.md) topic.
diff --git a/browsers/internet-explorer/ie11-deploy-guide/auto-configuration-and-auto-proxy-problems-with-ie11.md b/browsers/internet-explorer/ie11-deploy-guide/auto-configuration-and-auto-proxy-problems-with-ie11.md
index d45374e404..7dbfc19776 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/auto-configuration-and-auto-proxy-problems-with-ie11.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/auto-configuration-and-auto-proxy-problems-with-ie11.md
@@ -1,62 +1,66 @@
----
-ms.localizationpriority: medium
-ms.mktglfcycl: deploy
-ms.pagetype: networking
-description: Auto configuration and auto proxy problems with Internet Explorer 11
-author: dansimp
-ms.prod: ie11
-ms.assetid: 3fbbc2c8-859b-4b2e-abc3-de2c299e0938
-ms.reviewer:
-audience: itpro
manager: dansimp
-ms.author: dansimp
-title: Auto configuration and auto proxy problems with Internet Explorer 11 (Internet Explorer 11 for IT Pros)
-ms.sitesec: library
-ms.date: 07/27/2017
----
-
-
-# Auto configuration and auto proxy problems with Internet Explorer 11
-You might experience some problems using automatic configuration and auto-proxy with Internet Explorer 11.
-
-## Branding changes aren't distributed using automatic configuration
-If you've turned on the **Disable external branding of Internet Explorer** Group Policy Object, you won't be able to use automatic configuration to distribute your branding changes to your users' computers. When this object is turned on, it prevents the branding of IE by a non-Microsoft company or entity, such as an Internet service provider or Internet content provider. For more information about automatic configuration, see [Auto configuration settings for Internet Explorer 11](auto-configuration-settings-for-ie11.md) and [Use the Automatic Configuration page in the IEAK 11 Wizard](../ie11-ieak/auto-config-ieak11-wizard.md). For more information about Group Policy settings, see [Group policy objects and Internet Explorer 11 (IE11)](group-policy-objects-and-ie11.md).
-
-## Proxy server setup issues
-If you experience issues while setting up your proxy server, you can try these troubleshooting steps:
-
-- Check to make sure the proxy server address is right.
-
-- Check that both **Automatically detect settings** and **Automatic configuration** are turned on in the browser.
-
-- Check that the browser is pointing to the right automatic configuration script location.
-
- **To check your proxy server address**
-
-1. On the **Tools** menu, click **Internet Options**, and then **Connections**.
-
-2. Click **Settings** or **LAN Settings**, and then look at your proxy server address.
-
-3. If you have multiple proxy servers, click **Advanced** to look at all of the additional addresses.
**Note** If IE11 uses a proxy server for local IP addresses, regardless whether you turned on the **Bypass Proxy Server for Local Addresses** option, see [Internet Explorer Uses Proxy Server for Local IP Address Even if the "Bypass Proxy Server for Local Addresses" Option Is Turned On](https://go.microsoft.com/fwlink/p/?LinkId=85652).
-
- **To check that you've turned on the correct settings**
-
-4. On the **Tools** menu, click **Internet Options**, and then click **Connections**.
-
-5. Click **Settings** or **LAN Settings**.
-
-6. In the **Automatic configuration** area, check that you've clicked the **Automatically detect settings** box. If you've turned on automatic configuration, check to make sure that you've also clicked the **Use automatic configuration script** box.
**Note** If at this point everything is set up correctly, but the proxy server still isn't behaving properly, click the **Detect my network settings** box in the **Error** dialog box to try to detect the proxy server, again.
-
- **To check that you're pointing to the correct automatic configuration script location**
-
-7. On the **Tools** menu, click **Internet Options**, and then click **Connections**.
-
-8. Click **Settings** or **LAN Settings**.
-
-9. In the **Automatic configuration** area, check that you've chosen the **Use automatic configuration script** box, and that it has the correct location to your automatic configuration script or for your automatic proxy URL.
-
-
-
-
-
-
-
+---
+ms.localizationpriority: medium
+ms.mktglfcycl: deploy
+ms.pagetype: networking
+description: Auto configuration and auto proxy problems with Internet Explorer 11
+author: dansimp
+ms.prod: ie11
+ms.assetid: 3fbbc2c8-859b-4b2e-abc3-de2c299e0938
+ms.reviewer:
+audience: itpro
+manager: dansimp
+ms.author: dansimp
+title: Auto configuration and auto proxy problems with Internet Explorer 11 (Internet Explorer 11 for IT Pros)
+ms.sitesec: library
+ms.date: 07/27/2017
+---
+
+
+# Auto configuration and auto proxy problems with Internet Explorer 11
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
+You might experience some problems using automatic configuration and auto-proxy with Internet Explorer 11.
+
+## Branding changes aren't distributed using automatic configuration
+If you've turned on the **Disable external branding of Internet Explorer** Group Policy Object, you won't be able to use automatic configuration to distribute your branding changes to your users' computers. When this object is turned on, it prevents the branding of IE by a non-Microsoft company or entity, such as an Internet service provider or Internet content provider. For more information about automatic configuration, see [Auto configuration settings for Internet Explorer 11](auto-configuration-settings-for-ie11.md) and [Use the Automatic Configuration page in the IEAK 11 Wizard](../ie11-ieak/auto-config-ieak11-wizard.md). For more information about Group Policy settings, see [Group policy objects and Internet Explorer 11 (IE11)](group-policy-objects-and-ie11.md).
+
+## Proxy server setup issues
+If you experience issues while setting up your proxy server, you can try these troubleshooting steps:
+
+- Check to make sure the proxy server address is right.
+
+- Check that both **Automatically detect settings** and **Automatic configuration** are turned on in the browser.
+
+- Check that the browser is pointing to the right automatic configuration script location.
+
+ **To check your proxy server address**
+
+1. On the **Tools** menu, click **Internet Options**, and then **Connections**.
+
+2. Click **Settings** or **LAN Settings**, and then look at your proxy server address.
+
+3. If you have multiple proxy servers, click **Advanced** to look at all of the additional addresses.
**Note** If IE11 uses a proxy server for local IP addresses, regardless whether you turned on the **Bypass Proxy Server for Local Addresses** option, see [Internet Explorer Uses Proxy Server for Local IP Address Even if the "Bypass Proxy Server for Local Addresses" Option Is Turned On](https://go.microsoft.com/fwlink/p/?LinkId=85652).
+
+ **To check that you've turned on the correct settings**
+
+4. On the **Tools** menu, click **Internet Options**, and then click **Connections**.
+
+5. Click **Settings** or **LAN Settings**.
+
+6. In the **Automatic configuration** area, check that you've clicked the **Automatically detect settings** box. If you've turned on automatic configuration, check to make sure that you've also clicked the **Use automatic configuration script** box.
**Note** If at this point everything is set up correctly, but the proxy server still isn't behaving properly, click the **Detect my network settings** box in the **Error** dialog box to try to detect the proxy server, again.
+
+ **To check that you're pointing to the correct automatic configuration script location**
+
+7. On the **Tools** menu, click **Internet Options**, and then click **Connections**.
+
+8. Click **Settings** or **LAN Settings**.
+
+9. In the **Automatic configuration** area, check that you've chosen the **Use automatic configuration script** box, and that it has the correct location to your automatic configuration script or for your automatic proxy URL.
+
+
+
+
+
+
+
diff --git a/browsers/internet-explorer/ie11-deploy-guide/auto-configuration-settings-for-ie11.md b/browsers/internet-explorer/ie11-deploy-guide/auto-configuration-settings-for-ie11.md
index 1b9a0ba9c8..82857ac50e 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/auto-configuration-settings-for-ie11.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/auto-configuration-settings-for-ie11.md
@@ -1,74 +1,78 @@
----
-ms.localizationpriority: medium
-ms.mktglfcycl: deploy
-ms.pagetype: networking
-description: Auto configuration settings for Internet Explorer 11
-author: dansimp
-ms.prod: ie11
-ms.assetid: 90308d59-45b9-4639-ab1b-497e5ba19023
-ms.reviewer:
-audience: itpro
manager: dansimp
-ms.author: dansimp
-title: Auto configuration settings for Internet Explorer 11 (Internet Explorer 11 for IT Pros)
-ms.sitesec: library
-ms.date: 07/27/2017
----
-
-
-# Auto configuration settings for Internet Explorer 11
-Automatic configuration lets you apply custom branding and graphics to your internal Internet Explorer installations, running on Windows 8.1 or Windows Server 2012 R2. For more information about adding custom branding and graphics to your IE package, see [Customize the toolbar button and Favorites List icons using IEAK 11](../ie11-ieak/guidelines-toolbar-and-favorites-list-ieak11.md).
**Important** You'll only see and be able to use the **IE Customization Wizard 11 - Automatic Configuration** page if you're creating an internal IE installation package. For more information about the **IE Customization Wizard 11 - Automatic Configuration** page, see [Use the Automatic Configuration page in the IEAK 11 Wizard](../ie11-ieak/auto-config-ieak11-wizard.md).
-
-## Adding the automatic configuration registry key
-For custom graphics and branding, add the `FEATURE\AUTOCONFIG\BRANDING` registry key to your IE installation package.
**Important** Follow these directions carefully because serious problems can occur if you update your registry incorrectly. For added protection, back up your registry so you can restore it if a problem occurs.
-
- **To add the registry key**
-
-1. On the **Start** screen, type **regedit**, and then click **Regedit.exe**.
-
-2. Right-click the `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\Main\FeatureControl` subkey, point to **New**, and then click **Key**.
-
-3. Enter the new key name, `FEATURE\AUTOCONFIG\BRANDING`, and then press Enter.
-
-4. Right-click `FEATURE\AUTOCONFIG\BRANDING`, point to **New**, and then click **DWORD (32-bit) Value**.
-
-5. Enter the new DWORD value name, **iexplore.exe**, and then press Enter.
-
-6. Right-click **iexplore.exe**, and then click **Modify**.
-
-7. In the **Value data** box, enter **1**, and then click **OK**.
-
-8. Exit the registry editor.
-
-## Updating your automatic configuration settings
-After adding the `FEATURE\AUTOCONFIG\BRANDING` registry key, you can change your automatic configuration settings to pick up the updated branding.
-
Important Your branding changes won't be added or updated if you've previously chosen the Disable external branding of IE setting in the User Configuration\Administrative Templates\Windows Components\Internet Explorer Group Policy object. This setting is intended to prevent branding by a third-party, like an Internet service or content provider. For more information about Group Policy, including videos and the latest technical documentation, see the Group Policy TechCenter.
-
- **To update your settings**
-
-1. Open the IE Customization Wizard 11, and go to the **Automatic Configuration** page.
-
-2. Choose the **Automatically detect configuration settings** check box to allow automatic detection of browser settings.
-
-3. Choose the **Enable Automatic Configuration** box to let you change the rest of the configuration options, including:
-
- - **Automatically configure every box:** Type how often IE should check for configuration updates. Typing **0** (zero), or not putting in any number, means that automatic configuration only happens when the computer restarts.
-
- - **Automatic Configuration URL (.INS file) box:** Type the location of your automatic configuration script.
-
- - **Automatic proxy URL (.JS, .JVS, or .PAC file) box:** Type the location of your automatic proxy script.
**Important** Internet Explorer 11 no longer supports using file server locations with your proxy configuration (.pac) files. To keep using your .pac files, you have to keep them on a web server and reference them using a URL, like `https://share/test.ins`.
-
-If your branding changes aren't correctly deployed after running through this process, see [Auto configuration and auto proxy problems with Internet Explorer 11](auto-configuration-and-auto-proxy-problems-with-ie11.md).
-
-## Locking your automatic configuration settings
-You have two options to restrict your users' ability to override the automatic configuration settings, based on your environment.
-
-- **Using Microsoft Active Directory.** Choose **Disable changing Automatic Configuration settings** from the Administrative Templates setting.
-
-- **Not Using Active Directory.** Choose the **Disable changing Automatic Configuration settings** setting in the `User Configuration\Administrative Templates\Windows Components\Internet Explorer` Group Policy object.
-
-
-
-
-
-
-
+---
+ms.localizationpriority: medium
+ms.mktglfcycl: deploy
+ms.pagetype: networking
+description: Auto configuration settings for Internet Explorer 11
+author: dansimp
+ms.prod: ie11
+ms.assetid: 90308d59-45b9-4639-ab1b-497e5ba19023
+ms.reviewer:
+audience: itpro
+manager: dansimp
+ms.author: dansimp
+title: Auto configuration settings for Internet Explorer 11 (Internet Explorer 11 for IT Pros)
+ms.sitesec: library
+ms.date: 07/27/2017
+---
+
+
+# Auto configuration settings for Internet Explorer 11
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
+Automatic configuration lets you apply custom branding and graphics to your internal Internet Explorer installations, running on Windows 8.1 or Windows Server 2012 R2. For more information about adding custom branding and graphics to your IE package, see [Customize the toolbar button and Favorites List icons using IEAK 11](../ie11-ieak/guidelines-toolbar-and-favorites-list-ieak11.md).
**Important** You'll only see and be able to use the **IE Customization Wizard 11 - Automatic Configuration** page if you're creating an internal IE installation package. For more information about the **IE Customization Wizard 11 - Automatic Configuration** page, see [Use the Automatic Configuration page in the IEAK 11 Wizard](../ie11-ieak/auto-config-ieak11-wizard.md).
+
+## Adding the automatic configuration registry key
+For custom graphics and branding, add the `FEATURE\AUTOCONFIG\BRANDING` registry key to your IE installation package.
**Important** Follow these directions carefully because serious problems can occur if you update your registry incorrectly. For added protection, back up your registry so you can restore it if a problem occurs.
+
+ **To add the registry key**
+
+1. On the **Start** screen, type **regedit**, and then click **Regedit.exe**.
+
+2. Right-click the `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\Main\FeatureControl` subkey, point to **New**, and then click **Key**.
+
+3. Enter the new key name, `FEATURE\AUTOCONFIG\BRANDING`, and then press Enter.
+
+4. Right-click `FEATURE\AUTOCONFIG\BRANDING`, point to **New**, and then click **DWORD (32-bit) Value**.
+
+5. Enter the new DWORD value name, **iexplore.exe**, and then press Enter.
+
+6. Right-click **iexplore.exe**, and then click **Modify**.
+
+7. In the **Value data** box, enter **1**, and then click **OK**.
+
+8. Exit the registry editor.
+
+## Updating your automatic configuration settings
+After adding the `FEATURE\AUTOCONFIG\BRANDING` registry key, you can change your automatic configuration settings to pick up the updated branding.
+
Important Your branding changes won't be added or updated if you've previously chosen the Disable external branding of IE setting in the User Configuration\Administrative Templates\Windows Components\Internet Explorer Group Policy object. This setting is intended to prevent branding by a third-party, like an Internet service or content provider. For more information about Group Policy, including videos and the latest technical documentation, see the Group Policy TechCenter.
+
+ **To update your settings**
+
+1. Open the IE Customization Wizard 11, and go to the **Automatic Configuration** page.
+
+2. Choose the **Automatically detect configuration settings** check box to allow automatic detection of browser settings.
+
+3. Choose the **Enable Automatic Configuration** box to let you change the rest of the configuration options, including:
+
+ - **Automatically configure every box:** Type how often IE should check for configuration updates. Typing **0** (zero), or not putting in any number, means that automatic configuration only happens when the computer restarts.
+
+ - **Automatic Configuration URL (.INS file) box:** Type the location of your automatic configuration script.
+
+ - **Automatic proxy URL (.JS, .JVS, or .PAC file) box:** Type the location of your automatic proxy script.
**Important** Internet Explorer 11 no longer supports using file server locations with your proxy configuration (.pac) files. To keep using your .pac files, you have to keep them on a web server and reference them using a URL, like `https://share/test.ins`.
+
+If your branding changes aren't correctly deployed after running through this process, see [Auto configuration and auto proxy problems with Internet Explorer 11](auto-configuration-and-auto-proxy-problems-with-ie11.md).
+
+## Locking your automatic configuration settings
+You have two options to restrict your users' ability to override the automatic configuration settings, based on your environment.
+
+- **Using Microsoft Active Directory.** Choose **Disable changing Automatic Configuration settings** from the Administrative Templates setting.
+
+- **Not Using Active Directory.** Choose the **Disable changing Automatic Configuration settings** setting in the `User Configuration\Administrative Templates\Windows Components\Internet Explorer` Group Policy object.
+
+
+
+
+
+
+
diff --git a/browsers/internet-explorer/ie11-deploy-guide/auto-detect-settings-for-ie11.md b/browsers/internet-explorer/ie11-deploy-guide/auto-detect-settings-for-ie11.md
index 6d58aac85b..3e2c898988 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/auto-detect-settings-for-ie11.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/auto-detect-settings-for-ie11.md
@@ -1,55 +1,59 @@
----
-ms.localizationpriority: medium
-ms.mktglfcycl: deploy
-ms.pagetype: networking
-description: Auto detect settings Internet Explorer 11
-author: dansimp
-ms.prod: ie11
-ms.assetid: c6753cf4-3276-43c5-aae9-200e9e82753f
-ms.reviewer:
-audience: itpro
manager: dansimp
-ms.author: dansimp
-title: Auto detect settings Internet Explorer 11 (Internet Explorer 11 for IT Pros)
-ms.sitesec: library
-ms.date: 07/27/2017
----
-
-
-# Auto detect settings Internet Explorer 11
-After you specify the specific settings related to automatic detection on your Dynamic Host Configuration Protocol (DHCP) and Domain Name System (DNS) servers, you can set up your users' browser settings from a central location.
-
-Automatic detection works even if the browser wasn't originally set up or installed by the administrator.
-
-- **Using DHCP servers:** For local area network (LAN)-based users. This server type lets you specify your global and subnet TCP/IP parameters centrally, defining your users' parameters by using reserved addresses. By doing it this way, a computer can move between subnets, automatically reconfiguring for TCP/IP when it starts.
-
-- **Using DNS servers:** For users on dial-up connections. This server type uses a set of protocols and services on a TCP/IP network, which lets users search for other computers by using hierarchical, user-friendly names (hosts), instead of numeric IP addresses.
**Note** DHCP has a higher priority than DNS for automatic configuration. If DHCP provides the URL to a .pac, .jvs, .js, or .ins configuration file, the process stops and the DNS lookup doesn't happen.
-
-## Updating your automatic detection settings
-To use automatic detection, you have to set up your DHCP and DNS servers.
**Note** Your DHCP servers must support the `DHCPINFORM` message, to obtain the DHCP options.
-
- **To turn on automatic detection for DHCP servers**
-
-1. Open the Internet Explorer Customization Wizard 11, and go to the **Automatic Configuration** page.
-
-2. Choose the **Automatically detect configuration settings** box to automatically detect your browser settings. For more information about the **Automatic Configuration** page, see [Use the Automatic Configuration page in the IEAK 11 Wizard](../ie11-ieak/auto-config-ieak11-wizard.md).
-
-3. Open the [DHCP Administrative Tool](https://go.microsoft.com/fwlink/p/?LinkId=302212), create a new option type, using the code number 252, and then associate it with the URL to your configuration file. For detailed instructions about how to do this, see [Create an option 252 entry in DHCP](https://go.microsoft.com/fwlink/p/?LinkId=294649).
-
- **To turn on automatic detection for DNS servers**
-
-4. Open the IE Customization Wizard 11, and go to the **Automatic Configuration** page.
-
-5. Choose the **Automatically detect configuration settings** box to automatically detect your browser settings.
-
-6. In your DNS database file, create a host record named, **WPAD**. This record has the IP address of the web server storing your automatic configuration (.js, .jvs, .pac, or .ins) file.
**-OR-**
Create a canonical name (CNAME) alias record named, **WPAD**. This record has the resolved name (not the IP address) of the server storing your automatic configuration (.pac) file.
**Note** For more information about creating a **WPAD** entry, see [Creating a WPAD entry in DNS](https://go.microsoft.com/fwlink/p/?LinkId=294651).
-
-7. After the database file propagates to the server, the DNS name, `wpad..com` resolves to the server name that includes your automatic configuration file.
**Note** Internet Explorer 11 creates a default URL template based on the host name, **wpad**. For example, `https://wpad..com/wpad.dat`. Because of this, you need to set up a file or redirection point in your web server **WPAD** record, named **wpad.dat**. The **wpad.dat** record delivers the contents of your automatic configuration file.
-
-
-
-
-
-
-
-
-
+---
+ms.localizationpriority: medium
+ms.mktglfcycl: deploy
+ms.pagetype: networking
+description: Auto detect settings Internet Explorer 11
+author: dansimp
+ms.prod: ie11
+ms.assetid: c6753cf4-3276-43c5-aae9-200e9e82753f
+ms.reviewer:
+audience: itpro
+manager: dansimp
+ms.author: dansimp
+title: Auto detect settings Internet Explorer 11 (Internet Explorer 11 for IT Pros)
+ms.sitesec: library
+ms.date: 07/27/2017
+---
+
+
+# Auto detect settings Internet Explorer 11
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
+After you specify the specific settings related to automatic detection on your Dynamic Host Configuration Protocol (DHCP) and Domain Name System (DNS) servers, you can set up your users' browser settings from a central location.
+
+Automatic detection works even if the browser wasn't originally set up or installed by the administrator.
+
+- **Using DHCP servers:** For local area network (LAN)-based users. This server type lets you specify your global and subnet TCP/IP parameters centrally, defining your users' parameters by using reserved addresses. By doing it this way, a computer can move between subnets, automatically reconfiguring for TCP/IP when it starts.
+
+- **Using DNS servers:** For users on dial-up connections. This server type uses a set of protocols and services on a TCP/IP network, which lets users search for other computers by using hierarchical, user-friendly names (hosts), instead of numeric IP addresses.
**Note** DHCP has a higher priority than DNS for automatic configuration. If DHCP provides the URL to a .pac, .jvs, .js, or .ins configuration file, the process stops and the DNS lookup doesn't happen.
+
+## Updating your automatic detection settings
+To use automatic detection, you have to set up your DHCP and DNS servers.
**Note** Your DHCP servers must support the `DHCPINFORM` message, to obtain the DHCP options.
+
+ **To turn on automatic detection for DHCP servers**
+
+1. Open the Internet Explorer Customization Wizard 11, and go to the **Automatic Configuration** page.
+
+2. Choose the **Automatically detect configuration settings** box to automatically detect your browser settings. For more information about the **Automatic Configuration** page, see [Use the Automatic Configuration page in the IEAK 11 Wizard](../ie11-ieak/auto-config-ieak11-wizard.md).
+
+3. Open the [DHCP Administrative Tool](https://go.microsoft.com/fwlink/p/?LinkId=302212), create a new option type, using the code number 252, and then associate it with the URL to your configuration file. For detailed instructions about how to do this, see [Create an option 252 entry in DHCP](https://go.microsoft.com/fwlink/p/?LinkId=294649).
+
+ **To turn on automatic detection for DNS servers**
+
+4. Open the IE Customization Wizard 11, and go to the **Automatic Configuration** page.
+
+5. Choose the **Automatically detect configuration settings** box to automatically detect your browser settings.
+
+6. In your DNS database file, create a host record named, **WPAD**. This record has the IP address of the web server storing your automatic configuration (.js, .jvs, .pac, or .ins) file.
**-OR-**
Create a canonical name (CNAME) alias record named, **WPAD**. This record has the resolved name (not the IP address) of the server storing your automatic configuration (.pac) file.
**Note** For more information about creating a **WPAD** entry, see [Creating a WPAD entry in DNS](https://go.microsoft.com/fwlink/p/?LinkId=294651).
+
+7. After the database file propagates to the server, the DNS name, `wpad..com` resolves to the server name that includes your automatic configuration file.
**Note** Internet Explorer 11 creates a default URL template based on the host name, **wpad**. For example, `https://wpad..com/wpad.dat`. Because of this, you need to set up a file or redirection point in your web server **WPAD** record, named **wpad.dat**. The **wpad.dat** record delivers the contents of your automatic configuration file.
+
+
+
+
+
+
+
+
+
diff --git a/browsers/internet-explorer/ie11-deploy-guide/auto-proxy-configuration-settings-for-ie11.md b/browsers/internet-explorer/ie11-deploy-guide/auto-proxy-configuration-settings-for-ie11.md
index bd7bd5c030..f285933bcb 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/auto-proxy-configuration-settings-for-ie11.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/auto-proxy-configuration-settings-for-ie11.md
@@ -1,50 +1,54 @@
----
-ms.localizationpriority: medium
-ms.mktglfcycl: deploy
-ms.pagetype: networking
-description: Auto proxy configuration settings for Internet Explorer 11
-author: dansimp
-ms.prod: ie11
-ms.assetid: 5120aaf9-8ead-438a-8472-3cdd924b7d9e
-ms.reviewer:
-audience: itpro
manager: dansimp
-ms.author: dansimp
-title: Auto proxy configuration settings for Internet Explorer 11 (Internet Explorer 11 for IT Pros)
-ms.sitesec: library
-ms.date: 07/27/2017
----
-
-
-# Auto proxy configuration settings for Internet Explorer 11
-Configure and maintain your proxy settings, like pointing your users' browsers to your automatic proxy script, through the Internet Explorer Customization Wizard 11 running on either Windows 8.1 or Windows Server 2012 R2.
-
-## Updating your auto-proxy settings
-You can use your Internet settings (.ins) files to set up your standard proxy settings. You can also specify script files (.js, .jvs, or .pac) to configure and maintain your advanced proxy settings. IE uses your auto-proxy script files to dynamically determine whether to connect to a host or use a proxy server. If a proxy server connection fails, Internet Explorer 11 automatically attempts to connect to another proxy server that you have specified.
-
- **To update your settings**
-
-1. Create a script file with your proxy information, copying it to a server location.
-
-2. Open the IE Customization Wizard 11, and go to the **Automatic Configuration** page.
-
-3. Choose the **Enable Automatic Configuration** box to let you change the rest of the configuration options, including:
-
- - **Automatically configure every box:** Type how often IE should check for configuration updates. Typing **0** (zero), or not putting in any number, means that updates only happen when the computer restarts.
-
- - **Automatic Configuration URL (.INS file) box:** Type the location of the .ins file you want to use for automatic configuration. For more information about setting up **Automatic Configuration**, see [Auto configuration settings for Internet Explorer 11](auto-configuration-settings-for-ie11.md).
-
- - **Automatic proxy URL (.JS, .JVS, or .PAC file) box:** Type the location of your automatic proxy script. This script runs whenever IE11 makes a network request and can include multiple proxy servers for each protocol type.
**Important** IE11 no longer supports using file server locations with your proxy configuration (.pac) files. To keep using your .pac files, you have to keep them on a web server and reference them using a URL, like `https://share/test.ins`.
-
-## Locking your auto-proxy settings
-You have two options to restrict your users' ability to override the automatic configuration settings, based on your environment.
-
-- **Using Microsoft Active Directory.** Choose **Disable changing proxy settings** from the Administrative Templates setting.
-
-- **Not Using Active Directory.** Choose the **Prevent changing proxy settings** setting in the `User Configuration\Administrative Templates\Windows Components\Internet Explorer` Group Policy object. For more information about Group Policy, see the [Group Policy TechCenter](https://go.microsoft.com/fwlink/p/?LinkId=214514).
-
-
-
-
-
-
-
+---
+ms.localizationpriority: medium
+ms.mktglfcycl: deploy
+ms.pagetype: networking
+description: Auto proxy configuration settings for Internet Explorer 11
+author: dansimp
+ms.prod: ie11
+ms.assetid: 5120aaf9-8ead-438a-8472-3cdd924b7d9e
+ms.reviewer:
+audience: itpro
+manager: dansimp
+ms.author: dansimp
+title: Auto proxy configuration settings for Internet Explorer 11 (Internet Explorer 11 for IT Pros)
+ms.sitesec: library
+ms.date: 07/27/2017
+---
+
+
+# Auto proxy configuration settings for Internet Explorer 11
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
+Configure and maintain your proxy settings, like pointing your users' browsers to your automatic proxy script, through the Internet Explorer Customization Wizard 11 running on either Windows 8.1 or Windows Server 2012 R2.
+
+## Updating your auto-proxy settings
+You can use your Internet settings (.ins) files to set up your standard proxy settings. You can also specify script files (.js, .jvs, or .pac) to configure and maintain your advanced proxy settings. IE uses your auto-proxy script files to dynamically determine whether to connect to a host or use a proxy server. If a proxy server connection fails, Internet Explorer 11 automatically attempts to connect to another proxy server that you have specified.
+
+ **To update your settings**
+
+1. Create a script file with your proxy information, copying it to a server location.
+
+2. Open the IE Customization Wizard 11, and go to the **Automatic Configuration** page.
+
+3. Choose the **Enable Automatic Configuration** box to let you change the rest of the configuration options, including:
+
+ - **Automatically configure every box:** Type how often IE should check for configuration updates. Typing **0** (zero), or not putting in any number, means that updates only happen when the computer restarts.
+
+ - **Automatic Configuration URL (.INS file) box:** Type the location of the .ins file you want to use for automatic configuration. For more information about setting up **Automatic Configuration**, see [Auto configuration settings for Internet Explorer 11](auto-configuration-settings-for-ie11.md).
+
+ - **Automatic proxy URL (.JS, .JVS, or .PAC file) box:** Type the location of your automatic proxy script. This script runs whenever IE11 makes a network request and can include multiple proxy servers for each protocol type.
**Important** IE11 no longer supports using file server locations with your proxy configuration (.pac) files. To keep using your .pac files, you have to keep them on a web server and reference them using a URL, like `https://share/test.ins`.
+
+## Locking your auto-proxy settings
+You have two options to restrict your users' ability to override the automatic configuration settings, based on your environment.
+
+- **Using Microsoft Active Directory.** Choose **Disable changing proxy settings** from the Administrative Templates setting.
+
+- **Not Using Active Directory.** Choose the **Prevent changing proxy settings** setting in the `User Configuration\Administrative Templates\Windows Components\Internet Explorer` Group Policy object. For more information about Group Policy, see the [Group Policy TechCenter](https://go.microsoft.com/fwlink/p/?LinkId=214514).
+
+
+
+
+
+
+
diff --git a/browsers/internet-explorer/ie11-deploy-guide/blocked-out-of-date-activex-controls.md b/browsers/internet-explorer/ie11-deploy-guide/blocked-out-of-date-activex-controls.md
index 12bd5502e3..17f6488e0a 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/blocked-out-of-date-activex-controls.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/blocked-out-of-date-activex-controls.md
@@ -1,43 +1,47 @@
----
-title: Blocked out-of-date ActiveX controls
-description: This page is periodically updated with new ActiveX controls blocked by this feature.
-author: dansimp
-ms.author: dansimp
-audience: itpro
manager: dansimp
-ms.date: 05/10/2018
-ms.topic: article
-ms.prod: ie11
-ms.localizationpriority: medium
-ms.mktglfcycl: deploy
-ms.pagetype: security
-ms.assetid: ''
-ms.reviewer:
-ms.sitesec: library
----
-
-# Blocked out-of-date ActiveX controls
-
-ActiveX controls are small apps that let websites provide content, like videos and games, and let you interact with content, like toolbars. Unfortunately, because many ActiveX controls aren't automatically updated, they can become outdated as new versions are released. It's very important that you keep your ActiveX controls up to date because malicious software (or malware) can target security flaws in outdated controls, damaging your computer by collecting info from it, installing unwanted software, or by letting someone else control it remotely. To help avoid this situation, Internet Explorer includes a security feature called _out-of-date ActiveX control blocking_.
-
-We'll periodically update this page with new ActiveX controls blocked by this feature. We'll typically provide one month's advance notice before adding new controls to the list.
-
-You will receive a notification if a webpage tries to load one of the following of ActiveX control versions:
-
-**Java**
-
-| Java 2 Platform, Standard Edition (J2SE) 1.4, everything below (but not including) update 43 |
-|----------------------------------------------------------------------------------------------|
-| J2SE 5.0, everything below (but not including) update 99 |
-| Java SE 6, everything below (but not including) update 181 |
-| Java SE 7, everything below (but not including) update 171 |
-| Java SE 8, everything below (but not including) update 161 |
-| Java SE 9, everything below (but not including) update 4 |
-
-**Silverlight**
-
-
-| Everything below (but not including) Silverlight 5.1.50907.0 |
-|--------------------------------------------------------------|
-| |
-
-For more information, see [Out-of-date ActiveX control blocking](out-of-date-activex-control-blocking.md) and [Internet Explorer begins blocking out-of-date ActiveX controls](https://blogs.msdn.com/b/ie/archive/2014/08/06/internet-explorer-begins-blocking-out-of-date-activex-controls.aspx). You can also view Microsoft's complete list of out-of-date ActiveX controls in the XML-based [version list](https://go.microsoft.com/fwlink/?LinkId=403864).
+---
+title: Blocked out-of-date ActiveX controls
+description: This page is periodically updated with new ActiveX controls blocked by this feature.
+author: dansimp
+ms.author: dansimp
+audience: itpro
+manager: dansimp
+ms.date: 05/10/2018
+ms.topic: article
+ms.prod: ie11
+ms.localizationpriority: medium
+ms.mktglfcycl: deploy
+ms.pagetype: security
+ms.assetid: ''
+ms.reviewer:
+ms.sitesec: library
+---
+
+# Blocked out-of-date ActiveX controls
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
+
+ActiveX controls are small apps that let websites provide content, like videos and games, and let you interact with content, like toolbars. Unfortunately, because many ActiveX controls aren't automatically updated, they can become outdated as new versions are released. It's very important that you keep your ActiveX controls up to date because malicious software (or malware) can target security flaws in outdated controls, damaging your computer by collecting info from it, installing unwanted software, or by letting someone else control it remotely. To help avoid this situation, Internet Explorer includes a security feature called _out-of-date ActiveX control blocking_.
+
+We'll periodically update this page with new ActiveX controls blocked by this feature. We'll typically provide one month's advance notice before adding new controls to the list.
+
+You will receive a notification if a webpage tries to load one of the following of ActiveX control versions:
+
+**Java**
+
+| Java 2 Platform, Standard Edition (J2SE) 1.4, everything below (but not including) update 43 |
+|----------------------------------------------------------------------------------------------|
+| J2SE 5.0, everything below (but not including) update 99 |
+| Java SE 6, everything below (but not including) update 181 |
+| Java SE 7, everything below (but not including) update 171 |
+| Java SE 8, everything below (but not including) update 161 |
+| Java SE 9, everything below (but not including) update 4 |
+
+**Silverlight**
+
+
+| Everything below (but not including) Silverlight 5.1.50907.0 |
+|--------------------------------------------------------------|
+| |
+
+For more information, see [Out-of-date ActiveX control blocking](out-of-date-activex-control-blocking.md) and [Internet Explorer begins blocking out-of-date ActiveX controls](https://blogs.msdn.com/b/ie/archive/2014/08/06/internet-explorer-begins-blocking-out-of-date-activex-controls.aspx). You can also view Microsoft's complete list of out-of-date ActiveX controls in the XML-based [version list](https://go.microsoft.com/fwlink/?LinkId=403864).
diff --git a/browsers/internet-explorer/ie11-deploy-guide/browser-cache-changes-and-roaming-profiles.md b/browsers/internet-explorer/ie11-deploy-guide/browser-cache-changes-and-roaming-profiles.md
index fe61c67cf5..9aca832f3e 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/browser-cache-changes-and-roaming-profiles.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/browser-cache-changes-and-roaming-profiles.md
@@ -1,38 +1,42 @@
----
-ms.localizationpriority: medium
-ms.mktglfcycl: deploy
-ms.pagetype: performance
-description: Browser cache changes and roaming profiles
-author: dansimp
-ms.prod: ie11
-ms.assetid: 85f0cd01-6f82-4bd1-9c0b-285af1ce3436
-ms.reviewer:
-audience: itpro
manager: dansimp
-ms.author: dansimp
-title: Browser cache changes and roaming profiles (Internet Explorer 11 for IT Pros)
-ms.sitesec: library
-ms.date: 10/16/2017
----
-
-
-# Browser cache changes and roaming profiles
-We’ve redesigned the browser cache to improve the performance, flexibility, reliability, and scalability of Internet Explorer and the apps that rely on the Windows Internet (WinINet) cache. Our new database design stops multiple clients from simultaneously accessing and using cached information, while also providing a higher level of data integrity.
-
-You won’t notice any changes to the management of your roaming profile data if you use our new database implementation in conjunction with the [roaming user profile guidelines](https://go.microsoft.com/fwlink/p/?LinkId=401544). This means that IE data that’s stored in the `AppData\Roaming` user profile folder is still be uploaded to your normal profile storage location after a user successfully logs off.
**Note** Cookies in a roaming profile can only be set by Internet Explorer for the desktop, with Enhanced Protected Mode turned off. Cookies set by the immersive version of IE or by Microsoft Store apps, can’t be part of a roaming profile. For more information about persistent cookies and roaming, see [Persistent cookies are not roamed in Internet Explorer](https://go.microsoft.com/fwlink/p/?LinkId=401545).
-
-To get the best results while using roaming profiles, we strongly recommend the following:
-
-- Create a separate roaming repository for each domain account that uses roaming.
-
-- Restrict roaming user profiles so they work on only one computer at a time. Using a single roaming profile on multiple computers isn’t supported (via console or Remote Desktop) and can cause unpredictable results, including cookie loss.
-
-- Allow all computers that let users sign-on with a roaming profile have identical IE cookie policies and settings.
-
-- Make sure to delete the user’s local roaming profile at sign off for any computer using user profile roaming. You can do this by turning on the **Delete cached copies of roaming profiles** Group Policy Object.
-
-
-
-
-
-
-
+---
+ms.localizationpriority: medium
+ms.mktglfcycl: deploy
+ms.pagetype: performance
+description: Browser cache changes and roaming profiles
+author: dansimp
+ms.prod: ie11
+ms.assetid: 85f0cd01-6f82-4bd1-9c0b-285af1ce3436
+ms.reviewer:
+audience: itpro
+manager: dansimp
+ms.author: dansimp
+title: Browser cache changes and roaming profiles (Internet Explorer 11 for IT Pros)
+ms.sitesec: library
+ms.date: 10/16/2017
+---
+
+
+# Browser cache changes and roaming profiles
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
+We’ve redesigned the browser cache to improve the performance, flexibility, reliability, and scalability of Internet Explorer and the apps that rely on the Windows Internet (WinINet) cache. Our new database design stops multiple clients from simultaneously accessing and using cached information, while also providing a higher level of data integrity.
+
+You won’t notice any changes to the management of your roaming profile data if you use our new database implementation in conjunction with the [roaming user profile guidelines](https://go.microsoft.com/fwlink/p/?LinkId=401544). This means that IE data that’s stored in the `AppData\Roaming` user profile folder is still be uploaded to your normal profile storage location after a user successfully logs off.
**Note** Cookies in a roaming profile can only be set by Internet Explorer for the desktop, with Enhanced Protected Mode turned off. Cookies set by the immersive version of IE or by Microsoft Store apps, can’t be part of a roaming profile. For more information about persistent cookies and roaming, see [Persistent cookies are not roamed in Internet Explorer](https://go.microsoft.com/fwlink/p/?LinkId=401545).
+
+To get the best results while using roaming profiles, we strongly recommend the following:
+
+- Create a separate roaming repository for each domain account that uses roaming.
+
+- Restrict roaming user profiles so they work on only one computer at a time. Using a single roaming profile on multiple computers isn’t supported (via console or Remote Desktop) and can cause unpredictable results, including cookie loss.
+
+- Allow all computers that let users sign-on with a roaming profile have identical IE cookie policies and settings.
+
+- Make sure to delete the user’s local roaming profile at sign off for any computer using user profile roaming. You can do this by turning on the **Delete cached copies of roaming profiles** Group Policy Object.
+
+
+
+
+
+
+
diff --git a/browsers/internet-explorer/ie11-deploy-guide/change-history-for-internet-explorer-11.md b/browsers/internet-explorer/ie11-deploy-guide/change-history-for-internet-explorer-11.md
index d3cae2a67a..f358312bbc 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/change-history-for-internet-explorer-11.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/change-history-for-internet-explorer-11.md
@@ -1,56 +1,60 @@
----
-ms.localizationpriority: medium
-title: Change history for Internet Explorer 11 (IE11) - Deployment Guide for IT Pros (Internet Explorer 11 for IT Pros)
-description: This topic lists new and updated topics in the Internet Explorer 11 Deployment Guide documentation for Windows 10 and Windows 10 Mobile.
-ms.mktglfcycl: deploy
-ms.prod: ie11
-ms.sitesec: library
-author: dansimp
-ms.date: 07/27/2017
-ms.reviewer:
-audience: itpro
manager: dansimp
-ms.author: dansimp
----
-
-
-# Change history for Internet Explorer 11
-This topic lists new and updated topics in the Internet Explorer 11 documentation for both Windows 10 and Windows 10 Mobile.
-
-## April 2017
-|New or changed topic | Description |
-|----------------------|-------------|
-|[Enterprise Mode for Internet Explorer 11](enterprise-mode-overview-for-ie11.md)|Updates to the Enterprise Mode section to include info about the Enterprise Mode Site List Portal. |
-
-## March 2017
-|New or changed topic | Description |
-|----------------------|-------------|
-|[New group policy settings for Internet Explorer 11](new-group-policy-settings-for-ie11.md) |Updated to add the Allow VBScript to run in Internet Explorer and the Hide the button (next to the New Tab button) that opens Microsoft Edge settings. |
-
-## November 2016
-|New or changed topic | Description |
-|----------------------|-------------|
-|[Collect data using Enterprise Site Discovery](collect-data-using-enterprise-site-discovery.md) |Updated the DocMode reason section to correct Code 8 and to add Code 9.|
-
-## August 2016
-|New or changed topic | Description |
-|----------------------|-------------|
-|[Enterprise Mode schema v.2 guidance](enterprise-mode-schema-version-2-guidance.md) |Updated to remove the IP range restrictions and to add code examples for both IPv4 and IPv6 addresses. |
-|[Enterprise Mode schema v.1 guidance](enterprise-mode-schema-version-1-guidance.md) |Updated to remove the IP range restrictions and to add code examples for both IPv4 and IPv6 addresses. |
-|[Collect data using Enterprise Site Discovery](collect-data-using-enterprise-site-discovery.md)|Added the Understanding the returned reason codes section to the topic. |
-
-## July 2016
-|New or changed topic | Description |
-|----------------------|-------------|
-|[New group policy settings for Internet Explorer 11](new-group-policy-settings-for-ie11.md) |Updated to include the comprehensive list of Group Policies that were added with Internet Explorer 11. |
-
-## June 2016
-|New or changed topic | Description |
-|----------------------|-------------|
-|[New group policy settings for Internet Explorer 11](new-group-policy-settings-for-ie11.md) |Updated with 2 new policies, Send all sites not included in the Enterprise Mode Site List to Microsoft Edge and Show message when opening sites in Microsoft Edge using Enterprise Mode. |
-
-
-## May 2016
-|New or changed topic | Description |
-|----------------------|-------------|
-|[Enterprise Mode schema v.1 guidance](enterprise-mode-schema-version-1-guidance.md) | Added info about using <emie> and <docMode> together. |
-
+---
+ms.localizationpriority: medium
+title: Change history for Internet Explorer 11 (IE11) - Deployment Guide for IT Pros (Internet Explorer 11 for IT Pros)
+description: This topic lists new and updated topics in the Internet Explorer 11 Deployment Guide documentation for Windows 10 and Windows 10 Mobile.
+ms.mktglfcycl: deploy
+ms.prod: ie11
+ms.sitesec: library
+author: dansimp
+ms.date: 07/27/2017
+ms.reviewer:
+audience: itpro
+manager: dansimp
+ms.author: dansimp
+---
+
+
+# Change history for Internet Explorer 11
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
+This topic lists new and updated topics in the Internet Explorer 11 documentation for both Windows 10 and Windows 10 Mobile.
+
+## April 2017
+|New or changed topic | Description |
+|----------------------|-------------|
+|[Enterprise Mode for Internet Explorer 11](enterprise-mode-overview-for-ie11.md)|Updates to the Enterprise Mode section to include info about the Enterprise Mode Site List Portal. |
+
+## March 2017
+|New or changed topic | Description |
+|----------------------|-------------|
+|[New group policy settings for Internet Explorer 11](new-group-policy-settings-for-ie11.md) |Updated to add the Allow VBScript to run in Internet Explorer and the Hide the button (next to the New Tab button) that opens Microsoft Edge settings. |
+
+## November 2016
+|New or changed topic | Description |
+|----------------------|-------------|
+|[Collect data using Enterprise Site Discovery](collect-data-using-enterprise-site-discovery.md) |Updated the DocMode reason section to correct Code 8 and to add Code 9.|
+
+## August 2016
+|New or changed topic | Description |
+|----------------------|-------------|
+|[Enterprise Mode schema v.2 guidance](enterprise-mode-schema-version-2-guidance.md) |Updated to remove the IP range restrictions and to add code examples for both IPv4 and IPv6 addresses. |
+|[Enterprise Mode schema v.1 guidance](enterprise-mode-schema-version-1-guidance.md) |Updated to remove the IP range restrictions and to add code examples for both IPv4 and IPv6 addresses. |
+|[Collect data using Enterprise Site Discovery](collect-data-using-enterprise-site-discovery.md)|Added the Understanding the returned reason codes section to the topic. |
+
+## July 2016
+|New or changed topic | Description |
+|----------------------|-------------|
+|[New group policy settings for Internet Explorer 11](new-group-policy-settings-for-ie11.md) |Updated to include the comprehensive list of Group Policies that were added with Internet Explorer 11. |
+
+## June 2016
+|New or changed topic | Description |
+|----------------------|-------------|
+|[New group policy settings for Internet Explorer 11](new-group-policy-settings-for-ie11.md) |Updated with 2 new policies, Send all sites not included in the Enterprise Mode Site List to Microsoft Edge and Show message when opening sites in Microsoft Edge using Enterprise Mode. |
+
+
+## May 2016
+|New or changed topic | Description |
+|----------------------|-------------|
+|[Enterprise Mode schema v.1 guidance](enterprise-mode-schema-version-1-guidance.md) | Added info about using <emie> and <docMode> together. |
+
diff --git a/browsers/internet-explorer/ie11-deploy-guide/check-for-new-enterprise-mode-site-list-xml-file.md b/browsers/internet-explorer/ie11-deploy-guide/check-for-new-enterprise-mode-site-list-xml-file.md
index 0b2d9ff141..9b4b3e6f1f 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/check-for-new-enterprise-mode-site-list-xml-file.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/check-for-new-enterprise-mode-site-list-xml-file.md
@@ -1,51 +1,55 @@
----
-title: Check for a new Enterprise Mode site list xml file (Internet Explorer 11 for IT Pros)
-description: You can have centralized control over Enterprise Mode by creating a single, global XML site list that includes the list of websites to render using Enterprise Mode.
-ms.assetid: 2bbc7017-622e-4baa-8981-c0bbda10e9df
-ms.reviewer:
-audience: itpro
manager: dansimp
-ms.prod: ie11
-ms.mktglfcycl: deploy
-ms.pagetype: appcompat
-ms.sitesec: library
-author: dansimp
-ms.author: dansimp
-ms.date: 08/14/2017
-ms.localizationpriority: medium
----
-
-
-# Check for a new Enterprise Mode site list xml file
-
-**Applies to:**
-
-- Windows 10
-- Windows 8.1
-- Windows 7
-- Windows Server 2012 R2
-- Windows Server 2008 R2 with Service Pack 1 (SP1)
-
-You can have centralized control over Enterprise Mode by creating a single, global XML site list that includes the list of websites to render using Enterprise Mode. You can add and remove sites from your XML list as frequently as you want, changing which sites should render in Enterprise Mode for your employees. For information about turning on Enterprise Mode and using site lists, see [Turn on Enterprise Mode and use a site list](turn-on-enterprise-mode-and-use-a-site-list.md).
-
-The information in this topic only covers HTTPS protocol. We strongly recommend that you use HTTPS protocol instead of file protocol due to increased performance.
-
-**How Internet Explorer 11 looks for an updated site list**
-
-1. Internet Explorer starts up and looks for an updated site list in the following places:
-
- 1. **In the cache container.** IE first checks the cache container to see if it finds your XML site list.
-
- 2. **In the local cache.** If there’s nothing in the cache container, IE checks your local cache for the site list.
-
- 3. **On the server.** Based on standard IE caching rules, IE might look for a copy of your site list in the location you put specified in the **SiteList** value of the registry.
-
-2. If there’s an .xml file in the cache container, IE waits 65 seconds and then checks the local cache for a newer version of the file from the server, based on standard caching rules. If the server file has a different version number than the version in the cache container, the server file is used and stored in the cache container.
**Note** If you’re already using a site list, enterprise mode continues to work during the 65 second wait; it just uses your existing site list instead of your new one.
-
-
-
-
-
-
-
-
-
+---
+title: Check for a new Enterprise Mode site list xml file (Internet Explorer 11 for IT Pros)
+description: You can have centralized control over Enterprise Mode by creating a single, global XML site list that includes the list of websites to render using Enterprise Mode.
+ms.assetid: 2bbc7017-622e-4baa-8981-c0bbda10e9df
+ms.reviewer:
+audience: itpro
+manager: dansimp
+ms.prod: ie11
+ms.mktglfcycl: deploy
+ms.pagetype: appcompat
+ms.sitesec: library
+author: dansimp
+ms.author: dansimp
+ms.date: 08/14/2017
+ms.localizationpriority: medium
+---
+
+
+# Check for a new Enterprise Mode site list xml file
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
+
+**Applies to:**
+
+- Windows 10
+- Windows 8.1
+- Windows 7
+- Windows Server 2012 R2
+- Windows Server 2008 R2 with Service Pack 1 (SP1)
+
+You can have centralized control over Enterprise Mode by creating a single, global XML site list that includes the list of websites to render using Enterprise Mode. You can add and remove sites from your XML list as frequently as you want, changing which sites should render in Enterprise Mode for your employees. For information about turning on Enterprise Mode and using site lists, see [Turn on Enterprise Mode and use a site list](turn-on-enterprise-mode-and-use-a-site-list.md).
+
+The information in this topic only covers HTTPS protocol. We strongly recommend that you use HTTPS protocol instead of file protocol due to increased performance.
+
+**How Internet Explorer 11 looks for an updated site list**
+
+1. Internet Explorer starts up and looks for an updated site list in the following places:
+
+ 1. **In the cache container.** IE first checks the cache container to see if it finds your XML site list.
+
+ 2. **In the local cache.** If there’s nothing in the cache container, IE checks your local cache for the site list.
+
+ 3. **On the server.** Based on standard IE caching rules, IE might look for a copy of your site list in the location you put specified in the **SiteList** value of the registry.
+
+2. If there’s an .xml file in the cache container, IE waits 65 seconds and then checks the local cache for a newer version of the file from the server, based on standard caching rules. If the server file has a different version number than the version in the cache container, the server file is used and stored in the cache container.
**Note** If you’re already using a site list, enterprise mode continues to work during the 65 second wait; it just uses your existing site list instead of your new one.
+
+
+
+
+
+
+
+
+
diff --git a/browsers/internet-explorer/ie11-deploy-guide/choose-how-to-deploy-ie11.md b/browsers/internet-explorer/ie11-deploy-guide/choose-how-to-deploy-ie11.md
index c35d115df7..810264c501 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/choose-how-to-deploy-ie11.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/choose-how-to-deploy-ie11.md
@@ -1,31 +1,35 @@
----
-ms.localizationpriority: medium
-ms.mktglfcycl: deploy
-description: Choose how to deploy Internet Explorer 11 (IE11)
-author: dansimp
-ms.prod: ie11
-ms.assetid: 21b6a301-c222-40bc-ad0b-27f66fc54d9d
-ms.reviewer:
-audience: itpro
manager: dansimp
-ms.author: dansimp
-title: Choose how to deploy Internet Explorer 11 (IE11) (Internet Explorer 11 for IT Pros)
-ms.sitesec: library
-ms.date: 07/27/2017
----
-
-
-# Choose how to deploy Internet Explorer 11 (IE11)
-In this section, you can learn about how to deploy your custom version of Internet Explorer using Automatic Version Synchronization (AVS) or using your software distribution tools.
-
-## In this section
-
-| Topic | Description |
-|------------------------------------------------------------- | ------------------------------------------------------ |
-|[Deploy IE11 using Automatic Version Synchronization (AVS)](deploy-ie11-using-automatic-version-synchronization-avs.md) |Guidance about how to deploy your custom browser packages using Automatic Version Synchronization (AVS). |
-|[Deploy IE11 using software distribution tools](deploy-ie11-using-software-distribution-tools.md) |Guidance about how to deploy your custom browser packages using System Center 2012 R2, Windows Server Update Services (WSUS), Group Policy software installation, or Microsoft Deployment toolkit (MDT). |
-
-
-
-
-
-
+---
+ms.localizationpriority: medium
+ms.mktglfcycl: deploy
+description: Choose how to deploy Internet Explorer 11 (IE11)
+author: dansimp
+ms.prod: ie11
+ms.assetid: 21b6a301-c222-40bc-ad0b-27f66fc54d9d
+ms.reviewer:
+audience: itpro
+manager: dansimp
+ms.author: dansimp
+title: Choose how to deploy Internet Explorer 11 (IE11) (Internet Explorer 11 for IT Pros)
+ms.sitesec: library
+ms.date: 07/27/2017
+---
+
+
+# Choose how to deploy Internet Explorer 11 (IE11)
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
+In this section, you can learn about how to deploy your custom version of Internet Explorer using Automatic Version Synchronization (AVS) or using your software distribution tools.
+
+## In this section
+
+| Topic | Description |
+|------------------------------------------------------------- | ------------------------------------------------------ |
+|[Deploy IE11 using Automatic Version Synchronization (AVS)](deploy-ie11-using-automatic-version-synchronization-avs.md) |Guidance about how to deploy your custom browser packages using Automatic Version Synchronization (AVS). |
+|[Deploy IE11 using software distribution tools](deploy-ie11-using-software-distribution-tools.md) |Guidance about how to deploy your custom browser packages using System Center 2012 R2, Windows Server Update Services (WSUS), Group Policy software installation, or Microsoft Deployment toolkit (MDT). |
+
+
+
+
+
+
diff --git a/browsers/internet-explorer/ie11-deploy-guide/choose-how-to-install-ie11.md b/browsers/internet-explorer/ie11-deploy-guide/choose-how-to-install-ie11.md
index 563f38160c..72a5766494 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/choose-how-to-install-ie11.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/choose-how-to-install-ie11.md
@@ -1,37 +1,41 @@
----
-ms.localizationpriority: medium
-ms.mktglfcycl: deploy
-description: Choose how to install Internet Explorer 11 (IE11)
-author: dansimp
-ms.prod: ie11
-ms.assetid: 9572f5f1-5d67-483e-bd63-ffea95053481
-ms.reviewer:
-audience: itpro
manager: dansimp
-ms.author: dansimp
-title: Choose how to install Internet Explorer 11 (IE11) (Internet Explorer 11 for IT Pros)
-ms.sitesec: library
-ms.date: 07/27/2017
----
-
-
-# Choose how to install Internet Explorer 11 (IE11)
-Before you install Internet Explorer 11, you should:
-
-- **Migrate Group Policy Objects.** Decide if your Group Policy Objects should migrate to the new version.
-
-- **Check vendor support for updated functionality.** Check whether third-party vendors have new versions or updates to necessary add-ons, apps, or code libraries.
-
-- **Choose the right version of Internet Explorer.** IE11 comes pre-installed on Windows 8.1 and Windows Server 2012 R2 or you can download it for Windows 7 SP1 or Windows Server 2008 R2 with Service Pack 1 (SP1) from the [Internet Explorer Downloads](https://go.microsoft.com/fwlink/p/?LinkId=214251) site.
-
-- **Choose how you'll deploy your installation package.** Your deployment method should be based on whether you're installing to computers already running Windows, or if you're deploying IE11 as part of a Windows installation.
-
- - **Existing computers running Windows.** Use System Center R2 2012 System Center 2012 R2 Configuration Manager, System Center Essentials 2010, Windows Server Updates Services (WSUS), or Microsoft Intune to deploy IE11. For more information about how to use these systems, see [System Center 2012 R2 Configuration Manager](https://go.microsoft.com/fwlink/p/?LinkID=276664), [System Center Essentials 2010](https://go.microsoft.com/fwlink/p/?LinkId=395200), [Windows Server Update Services](https://go.microsoft.com/fwlink/p/?LinkID=276790), and [Microsoft Intune Overview](https://www.microsoft.com/cloud-platform/microsoft-intune).
-
- - **As part of a Windows deployment.** Update your Windows images to include IE11, and then add the update to your MDT deployment share or to your Windows image. For instructions about how to create and use Windows images, see [Create and Manage a Windows Image Using DISM](https://go.microsoft.com/fwlink/p/?LinkId=299408). For general information about deploying IE, see [Microsoft Deployment Toolkit (MDT)](https://go.microsoft.com/fwlink/p/?LinkId=331148), [Windows ADK Overview](https://go.microsoft.com/fwlink/p/?LinkId=276669).
-
-
-
-
-
-
-
+---
+ms.localizationpriority: medium
+ms.mktglfcycl: deploy
+description: Choose how to install Internet Explorer 11 (IE11)
+author: dansimp
+ms.prod: ie11
+ms.assetid: 9572f5f1-5d67-483e-bd63-ffea95053481
+ms.reviewer:
+audience: itpro
+manager: dansimp
+ms.author: dansimp
+title: Choose how to install Internet Explorer 11 (IE11) (Internet Explorer 11 for IT Pros)
+ms.sitesec: library
+ms.date: 07/27/2017
+---
+
+
+# Choose how to install Internet Explorer 11 (IE11)
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
+Before you install Internet Explorer 11, you should:
+
+- **Migrate Group Policy Objects.** Decide if your Group Policy Objects should migrate to the new version.
+
+- **Check vendor support for updated functionality.** Check whether third-party vendors have new versions or updates to necessary add-ons, apps, or code libraries.
+
+- **Choose the right version of Internet Explorer.** IE11 comes pre-installed on Windows 8.1 and Windows Server 2012 R2 or you can download it for Windows 7 SP1 or Windows Server 2008 R2 with Service Pack 1 (SP1) from the [Internet Explorer Downloads](https://go.microsoft.com/fwlink/p/?LinkId=214251) site.
+
+- **Choose how you'll deploy your installation package.** Your deployment method should be based on whether you're installing to computers already running Windows, or if you're deploying IE11 as part of a Windows installation.
+
+ - **Existing computers running Windows.** Use System Center R2 2012 System Center 2012 R2 Configuration Manager, System Center Essentials 2010, Windows Server Updates Services (WSUS), or Microsoft Intune to deploy IE11. For more information about how to use these systems, see [System Center 2012 R2 Configuration Manager](https://go.microsoft.com/fwlink/p/?LinkID=276664), [System Center Essentials 2010](https://go.microsoft.com/fwlink/p/?LinkId=395200), [Windows Server Update Services](https://go.microsoft.com/fwlink/p/?LinkID=276790), and [Microsoft Intune Overview](https://www.microsoft.com/cloud-platform/microsoft-intune).
+
+ - **As part of a Windows deployment.** Update your Windows images to include IE11, and then add the update to your MDT deployment share or to your Windows image. For instructions about how to create and use Windows images, see [Create and Manage a Windows Image Using DISM](https://go.microsoft.com/fwlink/p/?LinkId=299408). For general information about deploying IE, see [Microsoft Deployment Toolkit (MDT)](https://go.microsoft.com/fwlink/p/?LinkId=331148), [Windows ADK Overview](https://go.microsoft.com/fwlink/p/?LinkId=276669).
+
+
+
+
+
+
+
diff --git a/browsers/internet-explorer/ie11-deploy-guide/collect-data-using-enterprise-site-discovery.md b/browsers/internet-explorer/ie11-deploy-guide/collect-data-using-enterprise-site-discovery.md
index 12049fdcb9..0ffe059374 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/collect-data-using-enterprise-site-discovery.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/collect-data-using-enterprise-site-discovery.md
@@ -16,6 +16,9 @@ ms.date: 07/27/2017
# Collect data using Enterprise Site Discovery
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
+
**Applies to:**
- Windows 10
diff --git a/browsers/internet-explorer/ie11-deploy-guide/configure-settings-enterprise-mode-portal.md b/browsers/internet-explorer/ie11-deploy-guide/configure-settings-enterprise-mode-portal.md
index d01fccf729..db62af6aab 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/configure-settings-enterprise-mode-portal.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/configure-settings-enterprise-mode-portal.md
@@ -16,6 +16,9 @@ ms.author: dansimp
# Use the Settings page to finish setting up the Enterprise Mode Site List Portal
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
+
**Applies to:**
- Windows 10
diff --git a/browsers/internet-explorer/ie11-deploy-guide/create-change-request-enterprise-mode-portal.md b/browsers/internet-explorer/ie11-deploy-guide/create-change-request-enterprise-mode-portal.md
index 278408ab38..ad4441c9e3 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/create-change-request-enterprise-mode-portal.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/create-change-request-enterprise-mode-portal.md
@@ -16,6 +16,9 @@ ms.author: dansimp
# Create a change request using the Enterprise Mode Site List Portal
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
+
**Applies to:**
- Windows 10
diff --git a/browsers/internet-explorer/ie11-deploy-guide/create-install-packages-for-multiple-operating-systems-or-languages.md b/browsers/internet-explorer/ie11-deploy-guide/create-install-packages-for-multiple-operating-systems-or-languages.md
index 6c260e93aa..395703b43d 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/create-install-packages-for-multiple-operating-systems-or-languages.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/create-install-packages-for-multiple-operating-systems-or-languages.md
@@ -16,6 +16,9 @@ ms.date: 07/27/2017
# Create packages for multiple operating systems or languages
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
You'll create multiple versions of your custom browser package if:
- You support more than 1 version of Windows®.
diff --git a/browsers/internet-explorer/ie11-deploy-guide/customize-ie11-install-packages.md b/browsers/internet-explorer/ie11-deploy-guide/customize-ie11-install-packages.md
index fc43585ae7..342b139714 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/customize-ie11-install-packages.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/customize-ie11-install-packages.md
@@ -16,6 +16,9 @@ ms.date: 07/27/2017
# Customize Internet Explorer 11 installation packages
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
You can customize Internet Explorer 11 to support various browser behaviors, multiple operating system versions and languages, and Setup information (.inf) files.
|Topic |Description |
diff --git a/browsers/internet-explorer/ie11-deploy-guide/delete-sites-from-your-enterprise-mode-site-list-in-the-enterprise-mode-site-list-manager.md b/browsers/internet-explorer/ie11-deploy-guide/delete-sites-from-your-enterprise-mode-site-list-in-the-enterprise-mode-site-list-manager.md
index b2c4c0f80a..843d917596 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/delete-sites-from-your-enterprise-mode-site-list-in-the-enterprise-mode-site-list-manager.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/delete-sites-from-your-enterprise-mode-site-list-in-the-enterprise-mode-site-list-manager.md
@@ -18,6 +18,9 @@ ms.date: 07/27/2017
# Delete sites from your Enterprise Mode site list in the Enterprise Mode Site List Manager
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
+
**Applies to:**
- Windows 10
diff --git a/browsers/internet-explorer/ie11-deploy-guide/deploy-ie11-using-automatic-version-synchronization-avs.md b/browsers/internet-explorer/ie11-deploy-guide/deploy-ie11-using-automatic-version-synchronization-avs.md
index b9089ee16a..0f0c56de35 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/deploy-ie11-using-automatic-version-synchronization-avs.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/deploy-ie11-using-automatic-version-synchronization-avs.md
@@ -15,6 +15,9 @@ ms.date: 07/27/2017
---
# Deploy Internet Explorer 11 using Automatic Version Synchronization (AVS)
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
You can deploy Internet Explorer 11 to your users' computers by using your custom browser packages and Automatic Version Synchronization (AVS).
## What is Automatic Version Synchronization?
diff --git a/browsers/internet-explorer/ie11-deploy-guide/deploy-ie11-using-software-distribution-tools.md b/browsers/internet-explorer/ie11-deploy-guide/deploy-ie11-using-software-distribution-tools.md
index dc31c3230e..c3940fbefd 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/deploy-ie11-using-software-distribution-tools.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/deploy-ie11-using-software-distribution-tools.md
@@ -16,6 +16,9 @@ ms.date: 07/27/2017
# Deploy Internet Explorer 11 using software distribution tools
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
If you already manage software distribution and updates on your network through software distribution tools, you can also use these tools for ongoing deployments of Internet Explorer. Software distribution tools include:
- **System Center R2 2012 System Center 2012 R2 Configuration Manager.** Deploy and install Internet Explorer 11 on your user's computers through a software distribution package. For more information about using this tool, see [System Center R2 2012 Configuration Manager](https://go.microsoft.com/fwlink/p/?LinkID=276664).
diff --git a/browsers/internet-explorer/ie11-deploy-guide/deploy-pinned-sites-using-mdt-2013.md b/browsers/internet-explorer/ie11-deploy-guide/deploy-pinned-sites-using-mdt-2013.md
index 567b8fbeb8..0177418299 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/deploy-pinned-sites-using-mdt-2013.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/deploy-pinned-sites-using-mdt-2013.md
@@ -17,6 +17,9 @@ ms.date: 07/27/2017
# Deploy pinned websites using Microsoft Deployment Toolkit (MDT) 2013
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
+
**Applies to:**
- Windows 10
diff --git a/browsers/internet-explorer/ie11-deploy-guide/deprecated-document-modes.md b/browsers/internet-explorer/ie11-deploy-guide/deprecated-document-modes.md
index f0f44c2897..e8d1ec3d7d 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/deprecated-document-modes.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/deprecated-document-modes.md
@@ -17,6 +17,9 @@ ms.date: 07/27/2017
# Deprecated document modes and Internet Explorer 11
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
+
**Applies to:**
- Windows 10
diff --git a/browsers/internet-explorer/ie11-deploy-guide/edit-the-enterprise-mode-site-list-using-the-enterprise-mode-site-list-manager.md b/browsers/internet-explorer/ie11-deploy-guide/edit-the-enterprise-mode-site-list-using-the-enterprise-mode-site-list-manager.md
index 8ad5f3e6ad..29574ab860 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/edit-the-enterprise-mode-site-list-using-the-enterprise-mode-site-list-manager.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/edit-the-enterprise-mode-site-list-using-the-enterprise-mode-site-list-manager.md
@@ -18,6 +18,9 @@ ms.date: 07/27/2017
# Edit the Enterprise Mode site list using the Enterprise Mode Site List Manager
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
+
**Applies to:**
- Windows 10
diff --git a/browsers/internet-explorer/ie11-deploy-guide/enable-and-disable-add-ons-using-administrative-templates-and-group-policy.md b/browsers/internet-explorer/ie11-deploy-guide/enable-and-disable-add-ons-using-administrative-templates-and-group-policy.md
index cb419efe7f..e21f3e41ed 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/enable-and-disable-add-ons-using-administrative-templates-and-group-policy.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/enable-and-disable-add-ons-using-administrative-templates-and-group-policy.md
@@ -17,6 +17,9 @@ ms.date: 4/12/2018
# Enable and disable add-ons using administrative templates and group policy
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
Add-ons let your employees personalize Internet Explorer. You can manage IE add-ons using Group Policy and Group Policy templates.
There are four types of add-ons:
diff --git a/browsers/internet-explorer/ie11-deploy-guide/enhanced-protected-mode-problems-with-ie11.md b/browsers/internet-explorer/ie11-deploy-guide/enhanced-protected-mode-problems-with-ie11.md
index d0998607dc..7f00307378 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/enhanced-protected-mode-problems-with-ie11.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/enhanced-protected-mode-problems-with-ie11.md
@@ -17,6 +17,9 @@ ms.date: 07/27/2017
# Enhanced Protected Mode problems with Internet Explorer
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
Enhanced Protected Mode further restricts Protected Mode to deny potential attackers access to sensitive or personal information. If this feature is turned on, users might start to see errors asking them to turn it off, like **This webpage wants to run "npctrl.dll. If you trust this site, you can disable Enhanced Protected Mode for this site to run the control**. If your users click the **Disable** box, Enhanced Protected Mode is turned off for only the single visit to that specific site. After the user leaves the site, Enhanced Protected Mode is automatically turned back on.
You can use your company’s Group Policy to turn Enhanced Protected Mode on or off for all users. For more information, see the [Group policy objects and Internet Explorer 11 (IE11)](group-policy-objects-and-ie11.md) information in this guide.
diff --git a/browsers/internet-explorer/ie11-deploy-guide/enterprise-mode-overview-for-ie11.md b/browsers/internet-explorer/ie11-deploy-guide/enterprise-mode-overview-for-ie11.md
index 71104a8786..e5e3c31095 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/enterprise-mode-overview-for-ie11.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/enterprise-mode-overview-for-ie11.md
@@ -18,6 +18,9 @@ ms.date: 07/27/2017
# Enterprise Mode for Internet Explorer 11
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
+
**Applies to:**
- Windows 10
diff --git a/browsers/internet-explorer/ie11-deploy-guide/enterprise-mode-schema-version-1-guidance.md b/browsers/internet-explorer/ie11-deploy-guide/enterprise-mode-schema-version-1-guidance.md
index 09160baadd..6832c2797b 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/enterprise-mode-schema-version-1-guidance.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/enterprise-mode-schema-version-1-guidance.md
@@ -18,6 +18,9 @@ ms.date: 07/27/2017
# Enterprise Mode schema v.1 guidance
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
+
**Applies to:**
- Windows 10
diff --git a/browsers/internet-explorer/ie11-deploy-guide/enterprise-mode-schema-version-2-guidance.md b/browsers/internet-explorer/ie11-deploy-guide/enterprise-mode-schema-version-2-guidance.md
index a321e5a744..299c6c093f 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/enterprise-mode-schema-version-2-guidance.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/enterprise-mode-schema-version-2-guidance.md
@@ -18,6 +18,9 @@ ms.date: 12/04/2017
# Enterprise Mode schema v.2 guidance
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
+
**Applies to:**
- Windows 10
diff --git a/browsers/internet-explorer/ie11-deploy-guide/export-your-enterprise-mode-site-list-from-the-enterprise-mode-site-list-manager.md b/browsers/internet-explorer/ie11-deploy-guide/export-your-enterprise-mode-site-list-from-the-enterprise-mode-site-list-manager.md
index cf235b25aa..ce2f14b162 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/export-your-enterprise-mode-site-list-from-the-enterprise-mode-site-list-manager.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/export-your-enterprise-mode-site-list-from-the-enterprise-mode-site-list-manager.md
@@ -18,6 +18,9 @@ ms.date: 07/27/2017
# Export your Enterprise Mode site list from the Enterprise Mode Site List Manager
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
+
**Applies to:**
- Windows 10
diff --git a/browsers/internet-explorer/ie11-deploy-guide/fix-compat-issues-with-doc-modes-and-enterprise-mode-site-list.md b/browsers/internet-explorer/ie11-deploy-guide/fix-compat-issues-with-doc-modes-and-enterprise-mode-site-list.md
index f1d72eb1a1..a5abdb8400 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/fix-compat-issues-with-doc-modes-and-enterprise-mode-site-list.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/fix-compat-issues-with-doc-modes-and-enterprise-mode-site-list.md
@@ -17,6 +17,9 @@ ms.date: 07/27/2017
# Fix web compatibility issues using document modes and the Enterprise Mode site list
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
The Internet Explorer 11 Enterprise Mode site list lets you specify document modes for specific websites, helping you fix compatibility issues without changing a single line of code on the site. This addition to the site list is a continuation of our commitment to help you upgrade and stay up-to-date on the latest version of Internet Explorer, while still preserving your investments in existing apps.
## What does this mean for me?
diff --git a/browsers/internet-explorer/ie11-deploy-guide/fix-validation-problems-using-the-enterprise-mode-site-list-manager.md b/browsers/internet-explorer/ie11-deploy-guide/fix-validation-problems-using-the-enterprise-mode-site-list-manager.md
index c3c7ead8ff..54da1d4ba1 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/fix-validation-problems-using-the-enterprise-mode-site-list-manager.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/fix-validation-problems-using-the-enterprise-mode-site-list-manager.md
@@ -18,6 +18,9 @@ ms.date: 07/27/2017
# Fix validation problems using the Enterprise Mode Site List Manager
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
+
**Applies to:**
- Windows 10
diff --git a/browsers/internet-explorer/ie11-deploy-guide/group-policy-and-advanced-group-policy-mgmt-ie11.md b/browsers/internet-explorer/ie11-deploy-guide/group-policy-and-advanced-group-policy-mgmt-ie11.md
index d2fadc609c..93486e7113 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/group-policy-and-advanced-group-policy-mgmt-ie11.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/group-policy-and-advanced-group-policy-mgmt-ie11.md
@@ -17,6 +17,9 @@ ms.date: 07/27/2017
# Group Policy, Advanced Group Policy Management (AGPM), and Internet Explorer 11
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
Advanced Group Policy Management (AGPM) is an add-on license that available for the Microsoft Desktop Optimization Pack (MDOP). This license gives you change control and a role assignment-model that helps optimize Group Policy management and reduce the risk of widespread failures.
From AGPM you can:
diff --git a/browsers/internet-explorer/ie11-deploy-guide/group-policy-and-group-policy-mgmt-console-ie11.md b/browsers/internet-explorer/ie11-deploy-guide/group-policy-and-group-policy-mgmt-console-ie11.md
index df5754f0b6..e1e763af4c 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/group-policy-and-group-policy-mgmt-console-ie11.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/group-policy-and-group-policy-mgmt-console-ie11.md
@@ -17,6 +17,9 @@ ms.date: 07/27/2017
# Group Policy, the Group Policy Management Console (GPMC), and Internet Explorer 11
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
A Microsoft Management Console (MMC)-based tool that uses scriptable interfaces to manage Group Policy. The 32-bit and 64-bit versions are included with Windows Server R2 with Service Pack 1 (SP1) and Windows Server 2012 R2.
## Why use the GPMC?
diff --git a/browsers/internet-explorer/ie11-deploy-guide/group-policy-and-ie11.md b/browsers/internet-explorer/ie11-deploy-guide/group-policy-and-ie11.md
index d80c5af350..7e8c419582 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/group-policy-and-ie11.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/group-policy-and-ie11.md
@@ -18,6 +18,9 @@ ms.date: 07/27/2017
# Group Policy and Internet Explorer 11 (IE11)
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
+
**Applies to:**
- Windows 10
diff --git a/browsers/internet-explorer/ie11-deploy-guide/group-policy-and-local-group-policy-editor-ie11.md b/browsers/internet-explorer/ie11-deploy-guide/group-policy-and-local-group-policy-editor-ie11.md
index 4ca3868ed5..dce572d812 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/group-policy-and-local-group-policy-editor-ie11.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/group-policy-and-local-group-policy-editor-ie11.md
@@ -17,6 +17,9 @@ ms.date: 07/27/2017
# Group Policy, the Local Group Policy Editor, and Internet Explorer 11
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
A Microsoft Management Console (MMC)-based tool that manages both computer and user-related configurations for an individual computer policy. This tool is included with Windows® 7 Service Pack 1 (SP1) and Windows 8.1.
Here's a list of the policy settings you can use, based on the configuration type. For more info, see [Local Group Policy Editor](https://go.microsoft.com/fwlink/p/?LinkId=294912).
diff --git a/browsers/internet-explorer/ie11-deploy-guide/group-policy-compatibility-with-ie11.md b/browsers/internet-explorer/ie11-deploy-guide/group-policy-compatibility-with-ie11.md
index 8a5b6d7859..12b360b126 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/group-policy-compatibility-with-ie11.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/group-policy-compatibility-with-ie11.md
@@ -17,6 +17,9 @@ ms.date: 07/27/2017
# Group Policy and compatibility with Internet Explorer 11
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
Internet Explorer 11 has many Group Policy entries that can be configured for keeping your environment managed and safe. This table includes all of our recommendations around security, performance, and compatibility with the previous versions of Internet Explorer, regardless of which Zone the website is in.
|Activity |Location |Setting the policy object |
diff --git a/browsers/internet-explorer/ie11-deploy-guide/group-policy-objects-and-ie11.md b/browsers/internet-explorer/ie11-deploy-guide/group-policy-objects-and-ie11.md
index 403471f4c7..3eafec01ac 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/group-policy-objects-and-ie11.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/group-policy-objects-and-ie11.md
@@ -17,6 +17,9 @@ ms.date: 07/27/2017
# Group Policy management tools
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
Group Policy, based on Microsoft Active Directory Domain Services (AD DS), lets you manage your organization's computer and user settings as part of your Group Policy objects (GPOs), which are added and changed in the Group Policy Management Console (GPMC). GPOs can include registry-based Administrative Template policy settings, security settings, software deployment information, scripts, folder redirection, and preferences. The most effective way to target a specific GPO is to use Windows Management Instrumentation (WMI) filters. Like, creating a WMI filter that applies a GPO only to computers with a specific make and model.
By using Group Policy, you can set up a policy setting once, and then copy that setting onto many computers. For example, you can set up multiple Internet Explorer 11 security settings in a GPO that's linked to a domain, and then apply all of those settings to every computer in the domain.
diff --git a/browsers/internet-explorer/ie11-deploy-guide/group-policy-preferences-and-ie11.md b/browsers/internet-explorer/ie11-deploy-guide/group-policy-preferences-and-ie11.md
index ae5c5f783e..938e3e036e 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/group-policy-preferences-and-ie11.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/group-policy-preferences-and-ie11.md
@@ -17,6 +17,9 @@ ms.date: 07/27/2017
# Group policy preferences and Internet Explorer 11
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
Group Policy preferences are less strict than Group Policy settings, based on:
| |Group Policy preferences |Group Policy settings |
diff --git a/browsers/internet-explorer/ie11-deploy-guide/group-policy-problems-ie11.md b/browsers/internet-explorer/ie11-deploy-guide/group-policy-problems-ie11.md
index d94601a9d5..26cf3ae659 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/group-policy-problems-ie11.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/group-policy-problems-ie11.md
@@ -17,6 +17,9 @@ ms.date: 07/27/2017
# Group Policy problems with Internet Explorer 11
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
If you're having problems with Group Policy and Internet Explorer 11, or if you're looking for high-level information about the concepts and techniques used to troubleshoot Group Policy, as well as links to detailed reference topics, procedures, and troubleshooting scenario guides, see [Group Policy Analysis and Troubleshooting Overview](https://go.microsoft.com/fwlink/p/?LinkId=279872).
## Group Policy Object-related Log Files
diff --git a/browsers/internet-explorer/ie11-deploy-guide/group-policy-shortcut-extensions-ie11.md b/browsers/internet-explorer/ie11-deploy-guide/group-policy-shortcut-extensions-ie11.md
index 1f0caf9bc3..cd9e8a1740 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/group-policy-shortcut-extensions-ie11.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/group-policy-shortcut-extensions-ie11.md
@@ -17,6 +17,9 @@ ms.date: 07/27/2017
# Group Policy, Shortcut Extensions, and Internet Explorer 11
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
Group Policy includes the Shortcuts preference extension, which lets you configure shortcuts to:
- **File system objects.** Traditional shortcuts that link to apps, files, folders, drives, shares, or computers. For example, linking a shortcut to an app from the **Start** screen.
diff --git a/browsers/internet-explorer/ie11-deploy-guide/group-policy-windows-powershell-ie11.md b/browsers/internet-explorer/ie11-deploy-guide/group-policy-windows-powershell-ie11.md
index 2de349942d..6f57e982ec 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/group-policy-windows-powershell-ie11.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/group-policy-windows-powershell-ie11.md
@@ -17,6 +17,9 @@ ms.date: 07/27/2017
# Group Policy, Windows Powershell, and Internet Explorer 11
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
Your domain-joined Group Policy Objects (GPOs) can use any of Group Policy-related “cmdlets” that run within Windows PowerShell.
Each cmdlet is a single-function command-line tool that can:
diff --git a/browsers/internet-explorer/ie11-deploy-guide/ie11-delivery-through-automatic-updates.md b/browsers/internet-explorer/ie11-deploy-guide/ie11-delivery-through-automatic-updates.md
index 9fe7dca247..bd0befaee9 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/ie11-delivery-through-automatic-updates.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/ie11-delivery-through-automatic-updates.md
@@ -17,6 +17,9 @@ ms.date: 05/22/2018
---
# Internet Explorer 11 delivery through automatic updates
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
Internet Explorer 11 makes browsing the web faster, easier, safer, and more reliable than ever. To help customers become more secure and up-to-date, Microsoft will distribute Internet Explorer 11 through Automatic Updates and the Windows Update and Microsoft Update sites. Internet Explorer 11 will be available for users of the 32-bit and 64-bit versions of Windows 7 Service Pack 1 (SP1), and 64-bit version of Windows Server 2008 R2 SP1. This article provides an overview of the delivery process and options available for IT administrators to control how and when Internet Explorer 11 is deployed to their organization through Automatic Updates.
- [Automatic updates delivery process](https://docs.microsoft.com/internet-explorer/ie11-deploy-guide/ie11-delivery-through-automatic-updates#automatic-updates-delivery-process)
@@ -65,7 +68,7 @@ Additional information on Internet Explorer 11, including a Readiness Toolkit, t
## Availability of Internet Explorer 11
-Automatic Updates will start to distribute Internet Explorer 11 shortly after the final release of the product and will distribute it through the Microsoft Endpoint Configuration Manager and WSUS.
+Automatic Updates will start to distribute Internet Explorer 11 shortly after the final release of the product and will distribute it through the Microsoft Endpoint Manager and WSUS.
## Prevent automatic installation of Internet Explorer 11 with WSUS
diff --git a/browsers/internet-explorer/ie11-deploy-guide/img-ie11-docmode-lg.md b/browsers/internet-explorer/ie11-deploy-guide/img-ie11-docmode-lg.md
index 6b34fcc195..30de0a2c97 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/img-ie11-docmode-lg.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/img-ie11-docmode-lg.md
@@ -11,6 +11,9 @@ ms.author: dansimp
# Full-sized flowchart detailing how document modes are chosen in IE11
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
+
Return to: [Deprecated document modes and Internet Explorer 11](deprecated-document-modes.md)
diff --git a/browsers/internet-explorer/ie11-deploy-guide/import-into-the-enterprise-mode-site-list-manager.md b/browsers/internet-explorer/ie11-deploy-guide/import-into-the-enterprise-mode-site-list-manager.md
index 5ab9dd5e58..f585e3210d 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/import-into-the-enterprise-mode-site-list-manager.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/import-into-the-enterprise-mode-site-list-manager.md
@@ -18,6 +18,9 @@ ms.date: 07/27/2017
# Import your Enterprise Mode site list to the Enterprise Mode Site List Manager
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
+
**Applies to:**
- Windows 10
diff --git a/browsers/internet-explorer/ie11-deploy-guide/index.md b/browsers/internet-explorer/ie11-deploy-guide/index.md
index 74f09e116d..c40ba230ff 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/index.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/index.md
@@ -14,6 +14,9 @@ manager: dansimp
# Internet Explorer 11 (IE11) - Deployment Guide for IT Pros
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
+
**Applies to:**
- Windows 10
diff --git a/browsers/internet-explorer/ie11-deploy-guide/install-and-deploy-ie11.md b/browsers/internet-explorer/ie11-deploy-guide/install-and-deploy-ie11.md
index e9fcf44f0e..47a4d07569 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/install-and-deploy-ie11.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/install-and-deploy-ie11.md
@@ -17,6 +17,9 @@ ms.date: 07/27/2017
# Install and Deploy Internet Explorer 11 (IE11)
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
+
**Applies to:**
- Windows 10
diff --git a/browsers/internet-explorer/ie11-deploy-guide/install-ie11-using-microsoft-intune.md b/browsers/internet-explorer/ie11-deploy-guide/install-ie11-using-microsoft-intune.md
index 7dd92ecc08..027cf25129 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/install-ie11-using-microsoft-intune.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/install-ie11-using-microsoft-intune.md
@@ -15,6 +15,9 @@ ms.date: 07/27/2017
# Install Internet Explorer 11 (IE11) using Microsoft Intune
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
Internet Explorer 11 is available as an update in Microsoft Intune. Microsoft Intune uses Windows cloud services to help you manage updates, monitor and protect your computers, provide remote assistance, track hardware and software inventory, and set security policies. For more information, see the [Documentation Library for Microsoft Intune](https://go.microsoft.com/fwlink/p/?LinkId=301805).
## Adding and deploying the IE11 package
diff --git a/browsers/internet-explorer/ie11-deploy-guide/install-ie11-using-operating-system-deployment-systems.md b/browsers/internet-explorer/ie11-deploy-guide/install-ie11-using-operating-system-deployment-systems.md
index 5dade69199..c6bd4e15e8 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/install-ie11-using-operating-system-deployment-systems.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/install-ie11-using-operating-system-deployment-systems.md
@@ -17,6 +17,9 @@ ms.date: 07/27/2017
# Install Internet Explorer 11 (IE11) using Microsoft Deployment Toolkit (MDT) and your Windows images
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
+
You can install Internet Explorer 11 (IE11) using Microsoft Deployment Toolkit (MDT) and your Windows images.
You'll need to extract the .cab file for each supported operating system and platform combination and the .msu file for each prerequisite update. Download the IE11 update and prerequisites here:
diff --git a/browsers/internet-explorer/ie11-deploy-guide/install-ie11-using-system-center-configuration-manager.md b/browsers/internet-explorer/ie11-deploy-guide/install-ie11-using-system-center-configuration-manager.md
index 2b40174159..e08ca5dffe 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/install-ie11-using-system-center-configuration-manager.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/install-ie11-using-system-center-configuration-manager.md
@@ -17,6 +17,9 @@ ms.date: 07/27/2017
# Install Internet Explorer 11 (IE11) using System Center 2012 R2 Configuration Manager
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
You can install Internet Explorer 11 (IE11) by using [System Center R2 2012 Configuration Manager](https://go.microsoft.com/fwlink/p/?linkid=276664). Complete these steps for each operating system and platform combination.
**To install IE11**
diff --git a/browsers/internet-explorer/ie11-deploy-guide/install-ie11-using-the-network.md b/browsers/internet-explorer/ie11-deploy-guide/install-ie11-using-the-network.md
index 9da3cd91fa..d0d9d17be1 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/install-ie11-using-the-network.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/install-ie11-using-the-network.md
@@ -16,6 +16,9 @@ ms.date: 07/27/2017
# Install Internet Explorer 11 (IE11) using your network
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
You can install Internet Explorer 11 (IE11) over your network by putting your custom IE11 installation package in a shared network folder and letting your employees run the Setup program on their own computers. You can create the network folder structure manually, or you can run Internet Explorer Administration Kit 11 (IEAK 11).
**Note** If you support multiple architectures and operating systems, create a subfolder for each combination. If you support multiple languages, create a subfolder for each localized installation file.
diff --git a/browsers/internet-explorer/ie11-deploy-guide/install-ie11-using-third-party-tools.md b/browsers/internet-explorer/ie11-deploy-guide/install-ie11-using-third-party-tools.md
index 5d230773e3..d593de27c6 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/install-ie11-using-third-party-tools.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/install-ie11-using-third-party-tools.md
@@ -16,6 +16,9 @@ ms.date: 07/27/2017
# Install Internet Explorer 11 (IE11) using third-party tools
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
You can install Internet Explorer 11 (IE11) using third-party electronic software distribution (ESD) systems and these command-line options:
## Setup Modes
diff --git a/browsers/internet-explorer/ie11-deploy-guide/install-ie11-using-windows-server-update-services-wsus.md b/browsers/internet-explorer/ie11-deploy-guide/install-ie11-using-windows-server-update-services-wsus.md
index 62bfab42b9..662514e102 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/install-ie11-using-windows-server-update-services-wsus.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/install-ie11-using-windows-server-update-services-wsus.md
@@ -16,6 +16,9 @@ ms.date: 07/27/2017
# Install Internet Explorer 11 (IE11) using Windows Server Update Services (WSUS)
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
Windows Server Update Services (WSUS) lets you download a single copy of the Microsoft product update and cache it on your local WSUS servers. You can then configure your computers to get the update from your local servers instead of Windows Update. For more information about WSUS, see [Windows Server Update Services](https://go.microsoft.com/fwlink/p/?LinkID=276790).
**To import from Windows Update to WSUS**
diff --git a/browsers/internet-explorer/ie11-deploy-guide/install-problems-with-ie11.md b/browsers/internet-explorer/ie11-deploy-guide/install-problems-with-ie11.md
index 3ebe727aeb..3e6ffbfad8 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/install-problems-with-ie11.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/install-problems-with-ie11.md
@@ -16,6 +16,9 @@ ms.date: 07/27/2017
# Install problems with Internet Explorer 11
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
Most Internet Explorer 11 installations are straightforward and work the way they should. But it's possible that you might have problems.
If you do, you can:
diff --git a/browsers/internet-explorer/ie11-deploy-guide/intranet-problems-and-ie11.md b/browsers/internet-explorer/ie11-deploy-guide/intranet-problems-and-ie11.md
index 16331ab49c..803fc7fb83 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/intranet-problems-and-ie11.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/intranet-problems-and-ie11.md
@@ -16,6 +16,9 @@ ms.date: 07/27/2017
# Fix intranet search problems with Internet Explorer 11
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
After upgrading to Internet Explorer 11, you might experience search issues while using your intranet site.
## Why is my intranet redirecting me to search results?
diff --git a/browsers/internet-explorer/ie11-deploy-guide/manage-ie11-overview.md b/browsers/internet-explorer/ie11-deploy-guide/manage-ie11-overview.md
index 2270749c81..66b29a20c4 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/manage-ie11-overview.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/manage-ie11-overview.md
@@ -17,6 +17,9 @@ ms.date: 07/27/2017
# Manage Internet Explorer 11
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
+
**Applies to:**
- Windows 10
diff --git a/browsers/internet-explorer/ie11-deploy-guide/missing-internet-explorer-maintenance-settings-for-ie11.md b/browsers/internet-explorer/ie11-deploy-guide/missing-internet-explorer-maintenance-settings-for-ie11.md
index c0087953b7..e0dbd2bdab 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/missing-internet-explorer-maintenance-settings-for-ie11.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/missing-internet-explorer-maintenance-settings-for-ie11.md
@@ -17,6 +17,9 @@ ms.date: 07/27/2017
# Missing Internet Explorer Maintenance settings for Internet Explorer 11
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
+
**Applies to:**
- Windows 10
diff --git a/browsers/internet-explorer/ie11-deploy-guide/missing-the-compatibility-view-button.md b/browsers/internet-explorer/ie11-deploy-guide/missing-the-compatibility-view-button.md
index fbc40cbf73..faa927931e 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/missing-the-compatibility-view-button.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/missing-the-compatibility-view-button.md
@@ -17,6 +17,9 @@ ms.date: 07/27/2017
# Missing the Compatibility View Button
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
+
**Applies to:**
- Windows 10
diff --git a/browsers/internet-explorer/ie11-deploy-guide/net-framework-problems-with-ie11.md b/browsers/internet-explorer/ie11-deploy-guide/net-framework-problems-with-ie11.md
index 3e564954a6..6c68a1ec01 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/net-framework-problems-with-ie11.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/net-framework-problems-with-ie11.md
@@ -16,6 +16,12 @@ ms.date: 07/27/2017
# .NET Framework problems with Internet Explorer 11
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
+
+## Summary
+
If you’re having problems launching your legacy apps while running Internet Explorer 11, it’s most likely because Internet Explorer no longer starts apps that use managed browser hosting controls, like in .NET Framework 1.1 and 2.0.
**To turn managed browser hosting controls back on**
@@ -24,11 +30,14 @@ If you’re having problems launching your legacy apps while running Internet Ex
2. **For 32-bit processes on x64 systems:** Go to the `HKLM\SOFTWARE\Wow6432Node\MICROSOFT\.NETFramework` registry key and change the **EnableIEHosting** value to **1**.
-For more information, see the [Web Applications](https://go.microsoft.com/fwlink/p/?LinkId=308903) section of the Application Compatibility in the .NET Framework 4.5 page.
+## More information
-
-
-
+IEHost is a Microsoft .NET Framework 1.1-based technology that provides a better model than ActiveX controls to host controls within the browser. The IEHost controls are lightweight and are operated under the .NET security model where they are operated inside a sandbox.
+From the .NET Framework 4, we remove the IEHost.dll file for the following reasons:
+- IEHost/HREF-EXE-style controls are exposed to the Internet. This poses a high security risk, and most customers who install the Framework are benefiting very little from this security risk.
+- Managed hosting controls and invoking random ActiveX controls may be unsafe, and this risk cannot be countered in the .NET Framework. Therefore, the ability to host is disabled. We strongly suggest that IEHost should be disabled in any production environment.
+- Potential security vulnerabilities and assembly versioning conflicts in the default application domain. By relying on COM Interop wrappers to load your assembly, it is implicitly loaded in the default application domain. If other browser extensions do the same function, they have the risks in the default application domain such as disclosing information, and so on. If you are not using strong-named assemblies as dependencies, type loading exceptions can occur. You cannot freely configure the common language runtime (CLR), because you do not own the host process, and you cannot run any code before your extension is loaded.
+For more information about .NET Framework application compatibility, see [Application compatibility in the .NET Framework](/dotnet/framework/migration-guide/application-compatibility).
diff --git a/browsers/internet-explorer/ie11-deploy-guide/new-group-policy-settings-for-ie11.md b/browsers/internet-explorer/ie11-deploy-guide/new-group-policy-settings-for-ie11.md
index 65e099eb37..9b8ab9eb33 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/new-group-policy-settings-for-ie11.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/new-group-policy-settings-for-ie11.md
@@ -17,6 +17,9 @@ ms.date: 07/27/2017
# New group policy settings for Internet Explorer 11
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
Internet Explorer 11 gives you some new Group Policy settings to help you manage your company's web browser configurations, including:
diff --git a/browsers/internet-explorer/ie11-deploy-guide/out-of-date-activex-control-blocking.md b/browsers/internet-explorer/ie11-deploy-guide/out-of-date-activex-control-blocking.md
index 5591606f32..a2f12352fd 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/out-of-date-activex-control-blocking.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/out-of-date-activex-control-blocking.md
@@ -18,6 +18,9 @@ ms.date: 05/10/2018
# Out-of-date ActiveX control blocking
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
+
**Applies to:**
- Windows 10
@@ -105,7 +108,10 @@ reg add "HKCU\Software\Microsoft\Internet Explorer\VersionManager" /v DownloadVe
```
Turning off this automatic download breaks the out-of-date ActiveX control blocking feature by not letting the version list update with newly outdated controls, potentially compromising the security of your computer. Use this configuration option at your own risk.
-## Out-of-date ActiveX control blocking on managed devices
+## Out-of-date ActiveX control blocking
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+ on managed devices
Out-of-date ActiveX control blocking includes four new Group Policy settings that you can use to manage your web browser configuration, based on your domain controller. You can download the administrative templates, including the new settings, from the [Administrative templates (.admx) for Windows 10](https://go.microsoft.com/fwlink/p/?LinkId=746579) page or the [Administrative Templates (.admx) for Windows 8.1 and Windows Server 2012 R2](https://go.microsoft.com/fwlink/p/?LinkId=746580) page, depending on your operating system.
### Group Policy settings
diff --git a/browsers/internet-explorer/ie11-deploy-guide/problems-after-installing-ie11.md b/browsers/internet-explorer/ie11-deploy-guide/problems-after-installing-ie11.md
index 80a59c9305..fbcbcbadb9 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/problems-after-installing-ie11.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/problems-after-installing-ie11.md
@@ -16,6 +16,9 @@ ms.date: 10/16/2017
# Problems after installing Internet Explorer 11
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
After you install Internet Explorer 11 in your organization, you might run into the following issues. By following these suggestions, you should be able to fix them.
## Internet Explorer is in an unusable state
diff --git a/browsers/internet-explorer/ie11-deploy-guide/remove-all-sites-from-your-enterprise-mode-site-list-in-the-enterprise-mode-site-list-manager.md b/browsers/internet-explorer/ie11-deploy-guide/remove-all-sites-from-your-enterprise-mode-site-list-in-the-enterprise-mode-site-list-manager.md
index df8a2b1707..4c973ffad6 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/remove-all-sites-from-your-enterprise-mode-site-list-in-the-enterprise-mode-site-list-manager.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/remove-all-sites-from-your-enterprise-mode-site-list-in-the-enterprise-mode-site-list-manager.md
@@ -18,6 +18,9 @@ ms.date: 07/27/2017
# Remove all sites from your Enterprise Mode site list using the Enterprise Mode Site List Manager
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
+
**Applies to:**
- Windows 10
diff --git a/browsers/internet-explorer/ie11-deploy-guide/remove-sites-from-a-local-compatibililty-view-list.md b/browsers/internet-explorer/ie11-deploy-guide/remove-sites-from-a-local-compatibililty-view-list.md
index 4995a12e9a..f30c495bb3 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/remove-sites-from-a-local-compatibililty-view-list.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/remove-sites-from-a-local-compatibililty-view-list.md
@@ -18,6 +18,9 @@ ms.date: 07/27/2017
# Remove sites from a local compatibility view list
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
+
**Applies to:**
- Windows 10
diff --git a/browsers/internet-explorer/ie11-deploy-guide/remove-sites-from-a-local-enterprise-mode-site-list.md b/browsers/internet-explorer/ie11-deploy-guide/remove-sites-from-a-local-enterprise-mode-site-list.md
index c9b859509b..93b323b78a 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/remove-sites-from-a-local-enterprise-mode-site-list.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/remove-sites-from-a-local-enterprise-mode-site-list.md
@@ -18,6 +18,9 @@ ms.date: 07/27/2017
# Remove sites from a local Enterprise Mode site list
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
+
**Applies to:**
- Windows 10
diff --git a/browsers/internet-explorer/ie11-deploy-guide/review-neutral-sites-with-site-list-manager.md b/browsers/internet-explorer/ie11-deploy-guide/review-neutral-sites-with-site-list-manager.md
index bb22b43b3f..acfe82d2a5 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/review-neutral-sites-with-site-list-manager.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/review-neutral-sites-with-site-list-manager.md
@@ -17,6 +17,9 @@ ms.date: 04/02/2020
# Review neutral sites for Internet Explorer mode using the Enterprise Mode Site List Manager
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
+
**Applies to:**
- Windows 10
diff --git a/browsers/internet-explorer/ie11-deploy-guide/save-your-site-list-to-xml-in-the-enterprise-mode-site-list-manager.md b/browsers/internet-explorer/ie11-deploy-guide/save-your-site-list-to-xml-in-the-enterprise-mode-site-list-manager.md
index 28b18117e1..7b80dd178d 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/save-your-site-list-to-xml-in-the-enterprise-mode-site-list-manager.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/save-your-site-list-to-xml-in-the-enterprise-mode-site-list-manager.md
@@ -18,6 +18,9 @@ ms.date: 07/27/2017
# Save your site list to XML in the Enterprise Mode Site List Manager
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
+
**Applies to:**
- Windows 10
diff --git a/browsers/internet-explorer/ie11-deploy-guide/schedule-production-change-enterprise-mode-portal.md b/browsers/internet-explorer/ie11-deploy-guide/schedule-production-change-enterprise-mode-portal.md
index 4565b9f0c1..4d5e66ec80 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/schedule-production-change-enterprise-mode-portal.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/schedule-production-change-enterprise-mode-portal.md
@@ -16,6 +16,9 @@ ms.author: dansimp
# Schedule approved change requests for production using the Enterprise Mode Site List Portal
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
+
**Applies to:**
- Windows 10
diff --git a/browsers/internet-explorer/ie11-deploy-guide/search-your-enterprise-mode-site-list-in-the-enterprise-mode-site-list-manager.md b/browsers/internet-explorer/ie11-deploy-guide/search-your-enterprise-mode-site-list-in-the-enterprise-mode-site-list-manager.md
index 0f35b04d1c..f96a952626 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/search-your-enterprise-mode-site-list-in-the-enterprise-mode-site-list-manager.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/search-your-enterprise-mode-site-list-in-the-enterprise-mode-site-list-manager.md
@@ -18,6 +18,9 @@ ms.date: 07/27/2017
# Search your Enterprise Mode site list in the Enterprise Mode Site List Manager
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
+
**Applies to:**
- Windows 10
diff --git a/browsers/internet-explorer/ie11-deploy-guide/set-the-default-browser-using-group-policy.md b/browsers/internet-explorer/ie11-deploy-guide/set-the-default-browser-using-group-policy.md
index b6c1af8258..6edccdda73 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/set-the-default-browser-using-group-policy.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/set-the-default-browser-using-group-policy.md
@@ -17,6 +17,9 @@ ms.date: 07/27/2017
# Set the default browser using Group Policy
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
You can use the Group Policy setting, **Set a default associations configuration file**, to set the default browser for your company devices running Windows 10.
**To set the default browser as Internet Explorer 11**
diff --git a/browsers/internet-explorer/ie11-deploy-guide/set-up-enterprise-mode-logging-and-data-collection.md b/browsers/internet-explorer/ie11-deploy-guide/set-up-enterprise-mode-logging-and-data-collection.md
index fd55a40ebd..94f9336c89 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/set-up-enterprise-mode-logging-and-data-collection.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/set-up-enterprise-mode-logging-and-data-collection.md
@@ -18,6 +18,9 @@ ms.date: 07/27/2017
# Set up Enterprise Mode logging and data collection
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
+
**Applies to:**
- Windows 10
diff --git a/browsers/internet-explorer/ie11-deploy-guide/set-up-enterprise-mode-portal.md b/browsers/internet-explorer/ie11-deploy-guide/set-up-enterprise-mode-portal.md
index 7b0dd491aa..c022c08569 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/set-up-enterprise-mode-portal.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/set-up-enterprise-mode-portal.md
@@ -16,6 +16,9 @@ ms.author: dansimp
# Set up the Enterprise Mode Site List Portal
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
+
**Applies to:**
- Windows 10
diff --git a/browsers/internet-explorer/ie11-deploy-guide/setup-problems-with-ie11.md b/browsers/internet-explorer/ie11-deploy-guide/setup-problems-with-ie11.md
index 7dd3e837c0..70d197c391 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/setup-problems-with-ie11.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/setup-problems-with-ie11.md
@@ -17,6 +17,9 @@ ms.date: 07/27/2017
# Setup problems with Internet Explorer 11
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
Installing Internet Explorer creates the following log files, which are stored in the Windows installation folder (typically, the C:\\Windows folder):
- `IE11_main.log`
diff --git a/browsers/internet-explorer/ie11-deploy-guide/system-requirements-and-language-support-for-ie11.md b/browsers/internet-explorer/ie11-deploy-guide/system-requirements-and-language-support-for-ie11.md
index a8953ad3f4..37b7bc16cf 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/system-requirements-and-language-support-for-ie11.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/system-requirements-and-language-support-for-ie11.md
@@ -17,6 +17,9 @@ ms.date: 07/27/2017
# System requirements and language support for Internet Explorer 11 (IE11)
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
+
**Applies to:**
- Windows 10
diff --git a/browsers/internet-explorer/ie11-deploy-guide/tips-and-tricks-to-manage-ie-compatibility.md b/browsers/internet-explorer/ie11-deploy-guide/tips-and-tricks-to-manage-ie-compatibility.md
index 1f9a047156..14bd40e745 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/tips-and-tricks-to-manage-ie-compatibility.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/tips-and-tricks-to-manage-ie-compatibility.md
@@ -17,6 +17,9 @@ ms.date: 05/10/2018
# Tips and tricks to manage Internet Explorer compatibility
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
+
Find out how to achieve better backward compatibility for your legacy web applications with the Enterprise Mode Site List.
Jump to:
diff --git a/browsers/internet-explorer/ie11-deploy-guide/troubleshoot-ie11.md b/browsers/internet-explorer/ie11-deploy-guide/troubleshoot-ie11.md
index 39d999c947..bf8ceeb867 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/troubleshoot-ie11.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/troubleshoot-ie11.md
@@ -17,6 +17,9 @@ ms.date: 07/27/2017
# Troubleshoot Internet Explorer 11 (IE11)
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
+
**Applies to:**
- Windows 10
diff --git a/browsers/internet-explorer/ie11-deploy-guide/turn-off-enterprise-mode.md b/browsers/internet-explorer/ie11-deploy-guide/turn-off-enterprise-mode.md
index 1df0d6b95e..7e4561fa2a 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/turn-off-enterprise-mode.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/turn-off-enterprise-mode.md
@@ -18,6 +18,9 @@ ms.date: 07/27/2017
# Turn off Enterprise Mode
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
+
**Applies to:**
- Windows 10
diff --git a/browsers/internet-explorer/ie11-deploy-guide/turn-off-natural-metrics.md b/browsers/internet-explorer/ie11-deploy-guide/turn-off-natural-metrics.md
index 90442b3bbc..178085c2ad 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/turn-off-natural-metrics.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/turn-off-natural-metrics.md
@@ -16,6 +16,9 @@ ms.date: 07/27/2017
# Fix font rendering problems by turning off natural metrics
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
By default, Internet Explorer 11 uses “natural metrics”. Natural metrics use inter-pixel spacing that creates more accurately rendered and readable text, avoiding many common font rendering problems with Windows Internet Explorer 9 or older sites.
However, you might find that many intranet sites need you to use Windows Graphics Device Interface (GDI) metrics. To avoid potential compatibility issues, you must turn off natural metrics for those sites.
diff --git a/browsers/internet-explorer/ie11-deploy-guide/turn-on-enterprise-mode-and-use-a-site-list.md b/browsers/internet-explorer/ie11-deploy-guide/turn-on-enterprise-mode-and-use-a-site-list.md
index 744df8c766..8c84054dc3 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/turn-on-enterprise-mode-and-use-a-site-list.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/turn-on-enterprise-mode-and-use-a-site-list.md
@@ -18,6 +18,9 @@ ms.localizationpriority: medium
# Turn on Enterprise Mode and use a site list
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
+
**Applies to:**
- Windows 10
diff --git a/browsers/internet-explorer/ie11-deploy-guide/turn-on-local-control-and-logging-for-enterprise-mode.md b/browsers/internet-explorer/ie11-deploy-guide/turn-on-local-control-and-logging-for-enterprise-mode.md
index 1324c12963..b4db0fb7a4 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/turn-on-local-control-and-logging-for-enterprise-mode.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/turn-on-local-control-and-logging-for-enterprise-mode.md
@@ -18,6 +18,9 @@ ms.date: 07/27/2017
# Turn on local control and logging for Enterprise Mode
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
+
**Applies to:**
- Windows 10
diff --git a/browsers/internet-explorer/ie11-deploy-guide/updated-features-and-tools-with-ie11.md b/browsers/internet-explorer/ie11-deploy-guide/updated-features-and-tools-with-ie11.md
index 446375289c..750bca0e82 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/updated-features-and-tools-with-ie11.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/updated-features-and-tools-with-ie11.md
@@ -18,6 +18,9 @@ ms.date: 07/27/2017
# List of updated features and tools - Internet Explorer 11 (IE11)
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
+
**Applies to:**
- Windows 10
diff --git a/browsers/internet-explorer/ie11-deploy-guide/use-the-enterprise-mode-portal.md b/browsers/internet-explorer/ie11-deploy-guide/use-the-enterprise-mode-portal.md
index c26e39ddcc..fe55abfdc6 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/use-the-enterprise-mode-portal.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/use-the-enterprise-mode-portal.md
@@ -16,6 +16,9 @@ author: dansimp
# Use the Enterprise Mode Site List Portal
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
+
**Applies to:**
- Windows 10
diff --git a/browsers/internet-explorer/ie11-deploy-guide/use-the-enterprise-mode-site-list-manager.md b/browsers/internet-explorer/ie11-deploy-guide/use-the-enterprise-mode-site-list-manager.md
index 3cbc140f4b..cbfcfecf93 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/use-the-enterprise-mode-site-list-manager.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/use-the-enterprise-mode-site-list-manager.md
@@ -18,6 +18,9 @@ ms.date: 12/04/2017
# Use the Enterprise Mode Site List Manager
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
+
**Applies to:**
- Windows 10
diff --git a/browsers/internet-explorer/ie11-deploy-guide/user-interface-problems-with-ie11.md b/browsers/internet-explorer/ie11-deploy-guide/user-interface-problems-with-ie11.md
index 14fcd048fc..b7669cf1ca 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/user-interface-problems-with-ie11.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/user-interface-problems-with-ie11.md
@@ -16,6 +16,9 @@ ms.date: 07/27/2017
# User interface problems with Internet Explorer 11
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
Some of the features in both Internet Explorer 11 and IEAK 11 have moved around. Here are some of the more common changes.
## Where did features go in the Internet Explorer Customization Wizard 11?
diff --git a/browsers/internet-explorer/ie11-deploy-guide/using-enterprise-mode.md b/browsers/internet-explorer/ie11-deploy-guide/using-enterprise-mode.md
index 6bff79cc82..677f1c974a 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/using-enterprise-mode.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/using-enterprise-mode.md
@@ -18,6 +18,9 @@ ms.date: 07/27/2017
# Using IE7 Enterprise Mode or IE8 Enterprise Mode
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
+
**Applies to:**
- Windows 10
diff --git a/browsers/internet-explorer/ie11-deploy-guide/using-ieak11-to-create-install-packages.md b/browsers/internet-explorer/ie11-deploy-guide/using-ieak11-to-create-install-packages.md
index 07e3ce2e2b..7015595563 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/using-ieak11-to-create-install-packages.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/using-ieak11-to-create-install-packages.md
@@ -16,6 +16,9 @@ ms.date: 07/27/2017
# Using Internet Explorer Administration Kit 11 (IEAK 11) to create packages
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
Internet Explorer Administration Kit 11 (IEAK 11) helps you set up, deploy, and maintain Internet Explorer 11.
**Note** IEAK 11 works in network environments, with or without Microsoft Active Directory.
diff --git a/browsers/internet-explorer/ie11-deploy-guide/using-inf-files-to-create-install-packages.md b/browsers/internet-explorer/ie11-deploy-guide/using-inf-files-to-create-install-packages.md
index 1f7b62dfa5..afc27104af 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/using-inf-files-to-create-install-packages.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/using-inf-files-to-create-install-packages.md
@@ -16,6 +16,9 @@ ms.date: 07/27/2017
# Using Setup Information (.inf) files to create install packages
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
IEAK 11 uses Setup information (.inf) files to provide uninstallation instructions. Uninstallation instructions let your employees remove components, like files, registry entries, or shortcuts, through the **Uninstall or change a program** box. For details about .inf files, see [INF File Sections and Directives](https://go.microsoft.com/fwlink/p/?LinkId=327959).
**To add uninstallation instructions to the .inf files**
diff --git a/browsers/internet-explorer/ie11-deploy-guide/verify-changes-preprod-enterprise-mode-portal.md b/browsers/internet-explorer/ie11-deploy-guide/verify-changes-preprod-enterprise-mode-portal.md
index a3fce1731d..a31c831abd 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/verify-changes-preprod-enterprise-mode-portal.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/verify-changes-preprod-enterprise-mode-portal.md
@@ -16,6 +16,9 @@ ms.author: dansimp
# Verify your changes using the Enterprise Mode Site List Portal
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
+
**Applies to:**
- Windows 10
diff --git a/browsers/internet-explorer/ie11-deploy-guide/verify-changes-production-enterprise-mode-portal.md b/browsers/internet-explorer/ie11-deploy-guide/verify-changes-production-enterprise-mode-portal.md
index 42db6c85c5..1ccd3e4d0c 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/verify-changes-production-enterprise-mode-portal.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/verify-changes-production-enterprise-mode-portal.md
@@ -16,6 +16,9 @@ ms.author: dansimp
# Verify the change request update in the production environment using the Enterprise Mode Site List Portal
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
+
**Applies to:**
- Windows 10
diff --git a/browsers/internet-explorer/ie11-deploy-guide/view-apps-enterprise-mode-site-list.md b/browsers/internet-explorer/ie11-deploy-guide/view-apps-enterprise-mode-site-list.md
index 2be252275c..9aa736bacb 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/view-apps-enterprise-mode-site-list.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/view-apps-enterprise-mode-site-list.md
@@ -16,6 +16,9 @@ ms.author: dansimp
# View the apps included in the active Enterprise Mode Site List from the Enterprise Mode Site List Portal
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
+
**Applies to:**
- Windows 10
diff --git a/browsers/internet-explorer/ie11-deploy-guide/view-enterprise-mode-reports-for-portal.md b/browsers/internet-explorer/ie11-deploy-guide/view-enterprise-mode-reports-for-portal.md
index 20ad5ac557..f2db72080d 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/view-enterprise-mode-reports-for-portal.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/view-enterprise-mode-reports-for-portal.md
@@ -16,6 +16,9 @@ ms.author: dansimp
# View the available Enterprise Mode reports from the Enterprise Mode Site List Portal
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
+
**Applies to:**
- Windows 10
diff --git a/browsers/internet-explorer/ie11-deploy-guide/virtualization-and-compatibility-with-ie11.md b/browsers/internet-explorer/ie11-deploy-guide/virtualization-and-compatibility-with-ie11.md
index e5de6fffdd..771f7b3439 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/virtualization-and-compatibility-with-ie11.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/virtualization-and-compatibility-with-ie11.md
@@ -17,6 +17,9 @@ ms.date: 07/27/2017
# Virtualization and compatibility with Internet Explorer 11
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
If your company is considering upgrading to the latest version of Internet Explorer, but is hesitant because of a large number of web apps that need to be tested and moved, we recommend that you consider virtualization. Virtualization lets you set up a virtual environment where you can run earlier versions of IE.
**Important**
diff --git a/browsers/internet-explorer/ie11-deploy-guide/what-is-enterprise-mode.md b/browsers/internet-explorer/ie11-deploy-guide/what-is-enterprise-mode.md
index 1a2c6fc17a..b9fb67f961 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/what-is-enterprise-mode.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/what-is-enterprise-mode.md
@@ -18,6 +18,9 @@ ms.date: 10/25/2018
# Enterprise Mode and the Enterprise Mode Site List
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
+
**Applies to:**
- Windows 10
@@ -61,7 +64,10 @@ Download the [Enterprise Mode Site List Manager (schema v.2)](https://go.microso
- **Data gathering.** You can configure Enterprise Mode to collect local override data, posting back to a named server. This lets you "crowd source" compatibility testing from key users; gathering their findings to add to your central site list.
-## Enterprise Mode and the Enterprise Mode Site List XML file
+## Enterprise Mode and the Enterprise Mode Site List
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+ XML file
The Enterprise Mode Site List is an XML document that specifies a list of sites, their compat mode, and their intended browser. Using [Enterprise Mode Site List Manager (schema v.2)](https://go.microsoft.com/fwlink/p/?LinkId=716853), you can automatically start a webpage using a specific browser. In the case of IE11, the webpage can also be launched in a specific compat mode, so it always renders correctly. Your employees can easily view this site list by typing _about:compat_ in either Microsoft Edge or IE11.
Starting with Windows 10, version 1511 (also known as the Anniversary Update), you can also [restrict IE11 to only the legacy web apps that need it](https://blogs.windows.com/msedgedev/2016/05/19/edge14-ie11-better-together/), automatically sending sites not included in the Enterprise Mode Site List to Microsoft Edge.
diff --git a/browsers/internet-explorer/ie11-deploy-guide/what-is-the-internet-explorer-11-blocker-toolkit.md b/browsers/internet-explorer/ie11-deploy-guide/what-is-the-internet-explorer-11-blocker-toolkit.md
index 4f1c56a922..1fd67f656b 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/what-is-the-internet-explorer-11-blocker-toolkit.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/what-is-the-internet-explorer-11-blocker-toolkit.md
@@ -19,6 +19,9 @@ ms.date: 05/10/2018
# What is the Internet Explorer 11 Blocker Toolkit?
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
+
**Applies to:**
- Windows 10
diff --git a/browsers/internet-explorer/ie11-deploy-guide/workflow-processes-enterprise-mode-portal.md b/browsers/internet-explorer/ie11-deploy-guide/workflow-processes-enterprise-mode-portal.md
index de71b3a8ff..dd8e3bcce6 100644
--- a/browsers/internet-explorer/ie11-deploy-guide/workflow-processes-enterprise-mode-portal.md
+++ b/browsers/internet-explorer/ie11-deploy-guide/workflow-processes-enterprise-mode-portal.md
@@ -17,6 +17,9 @@ ms.author: dansimp
# Workflow-based processes for employees using the Enterprise Mode Site List Portal
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
+
**Applies to:**
- Windows 10
diff --git a/browsers/internet-explorer/ie11-faq/faq-for-it-pros-ie11.md b/browsers/internet-explorer/ie11-faq/faq-for-it-pros-ie11.md
index 8917b1de22..c27e670fd6 100644
--- a/browsers/internet-explorer/ie11-faq/faq-for-it-pros-ie11.md
+++ b/browsers/internet-explorer/ie11-faq/faq-for-it-pros-ie11.md
@@ -16,6 +16,9 @@ ms.date: 10/16/2017
# Internet Explorer 11 - FAQ for IT Pros
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
Answering frequently asked questions about Internet Explorer 11 (IE11) features, operating system support, integration with the Windows operating system, Group Policy, and general configuration.
## Frequently Asked Questions
diff --git a/browsers/internet-explorer/ie11-faq/faq-ie11-blocker-toolkit.md b/browsers/internet-explorer/ie11-faq/faq-ie11-blocker-toolkit.md
index e35b64b8a4..cf59b670d6 100644
--- a/browsers/internet-explorer/ie11-faq/faq-ie11-blocker-toolkit.md
+++ b/browsers/internet-explorer/ie11-faq/faq-ie11-blocker-toolkit.md
@@ -16,6 +16,9 @@ ms.date: 05/10/2018
# Internet Explorer 11 Blocker Toolkit - Frequently Asked Questions
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
+
Get answers to commonly asked questions about the Internet Explorer 11 Blocker Toolkit.
> [!Important]
diff --git a/browsers/internet-explorer/ie11-faq/faq-ieak11.md b/browsers/internet-explorer/ie11-faq/faq-ieak11.md
index 7405392094..929acbed39 100644
--- a/browsers/internet-explorer/ie11-faq/faq-ieak11.md
+++ b/browsers/internet-explorer/ie11-faq/faq-ieak11.md
@@ -18,6 +18,9 @@ ms.date: 05/10/2018
# IEAK 11 - Frequently Asked Questions
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
+
Get answers to commonly asked questions about the Internet Explorer Administration Kit 11 (IEAK 11), and find links to additional material you might find helpful.
**What is IEAK 11?**
diff --git a/browsers/internet-explorer/ie11-ieak/accelerators-ieak11-wizard.md b/browsers/internet-explorer/ie11-ieak/accelerators-ieak11-wizard.md
index b211933353..40a7886b0a 100644
--- a/browsers/internet-explorer/ie11-ieak/accelerators-ieak11-wizard.md
+++ b/browsers/internet-explorer/ie11-ieak/accelerators-ieak11-wizard.md
@@ -16,6 +16,9 @@ ms.date: 07/27/2017
# Use the Accelerators page in the IEAK 11 Wizard
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
The **Accelerators** page of the Internet Explorer Administration Kit (IEAK 11) Customization Wizard lets you add accelerators to your employee computers. Accelerators are contextual menu options that can quickly get to a web service from any webpage. For example, an accelerator can look up a highlighted word in the dictionary or a selected location on a map.
**Note**
diff --git a/browsers/internet-explorer/ie11-ieak/add-and-approve-activex-controls-ieak11.md b/browsers/internet-explorer/ie11-ieak/add-and-approve-activex-controls-ieak11.md
index 7e89dab65d..b4d0459c78 100644
--- a/browsers/internet-explorer/ie11-ieak/add-and-approve-activex-controls-ieak11.md
+++ b/browsers/internet-explorer/ie11-ieak/add-and-approve-activex-controls-ieak11.md
@@ -16,6 +16,9 @@ ms.date: 07/27/2017
# Add and approve ActiveX controls using IEAK 11
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
There are two main approaches to how you can control the use of ActiveX controls in your company. For more info about ActiveX controls, including how to manage the controls using Group Policy, see [Group Policy and ActiveX installation](../ie11-deploy-guide/activex-installation-using-group-policy.md) in the [Internet Explorer 11 (IE11) - Deployment Guide for IT Pros](../ie11-deploy-guide/index.md).
**Note**
diff --git a/browsers/internet-explorer/ie11-ieak/add-root-certificate-ieak11-wizard.md b/browsers/internet-explorer/ie11-ieak/add-root-certificate-ieak11-wizard.md
index eae4f678e5..c04501eea7 100644
--- a/browsers/internet-explorer/ie11-ieak/add-root-certificate-ieak11-wizard.md
+++ b/browsers/internet-explorer/ie11-ieak/add-root-certificate-ieak11-wizard.md
@@ -16,6 +16,9 @@ ms.date: 07/27/2017
# Use the Add a Root Certificate page in the IEAK 11 Wizard
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
We’re sorry. While we continue to recommend that you digitally sign your package, we’ve removed all of the functionality that allowed you to add a root certificate using the Internet Explorer Customization Wizard 11. The wizard page itself will be removed in a future version of the IEAK.
Click **Next** to go to the [Programs](programs-ieak11-wizard.md) page or **Back** to go to the [Security and Privacy Settings](security-and-privacy-settings-ieak11-wizard.md) page.
diff --git a/browsers/internet-explorer/ie11-ieak/additional-settings-ieak11-wizard.md b/browsers/internet-explorer/ie11-ieak/additional-settings-ieak11-wizard.md
index 60be35bc0d..ebff04a24a 100644
--- a/browsers/internet-explorer/ie11-ieak/additional-settings-ieak11-wizard.md
+++ b/browsers/internet-explorer/ie11-ieak/additional-settings-ieak11-wizard.md
@@ -16,6 +16,9 @@ ms.date: 07/27/2017
# Use the Additional Settings page in the IEAK 11 Wizard
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
The **Additional Settings** page of the Internet Explorer Administration Kit (IEAK 11) Customization Wizard lets you pick additional custom, corporate, and Internet settings that relate to your employee’s desktop, operating system, and security. If you don’t change a setting, it’ll be ignored.
The additional settings appear in administration (.adm) files that are stored in your `:\Program Files\Windows IEAK 11\policies` folder. You can also create your own .adm files with options that can be configured using the wizard. Any edits you make to your own .adm file are stored as .ins files, which are used to build the .inf files for your custom install package.
diff --git a/browsers/internet-explorer/ie11-ieak/auto-config-ieak11-wizard.md b/browsers/internet-explorer/ie11-ieak/auto-config-ieak11-wizard.md
index d3883b39ca..879c328e43 100644
--- a/browsers/internet-explorer/ie11-ieak/auto-config-ieak11-wizard.md
+++ b/browsers/internet-explorer/ie11-ieak/auto-config-ieak11-wizard.md
@@ -16,6 +16,9 @@ ms.date: 07/27/2017
# Use the Automatic Configuration page in the IEAK 11 Wizard
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
The **Automatic Configuration** page of the Internet Explorer Administration Kit (IEAK 11) Customization Wizard lets you provide URLs to the files that’ll automatically configure Internet Explorer 11 for a group of employees or devices.
**Note**
diff --git a/browsers/internet-explorer/ie11-ieak/auto-detection-dhcp-or-dns-servers-ieak11.md b/browsers/internet-explorer/ie11-ieak/auto-detection-dhcp-or-dns-servers-ieak11.md
index 1a46247c5c..7d4f9344c9 100644
--- a/browsers/internet-explorer/ie11-ieak/auto-detection-dhcp-or-dns-servers-ieak11.md
+++ b/browsers/internet-explorer/ie11-ieak/auto-detection-dhcp-or-dns-servers-ieak11.md
@@ -16,6 +16,9 @@ ms.date: 07/27/2017
# Set up auto detection for DHCP or DNS servers using IEAK 11
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
Set up your network to automatically detect and customize Internet Explorer 11 when it’s first started. Automatic detection is supported on both Dynamic Host Configuration Protocol (DHCP) and Domain Name System (DNS), letting your servers detect and set up your employee’s browser settings from a central location, using a configuration URL (.ins file) or a JavaScript proxy configuration file (.js, .jvs, or .pac).
Before you can set up your environment to use automatic detection, you need to turn the feature on.
diff --git a/browsers/internet-explorer/ie11-ieak/auto-version-sync-ieak11-wizard.md b/browsers/internet-explorer/ie11-ieak/auto-version-sync-ieak11-wizard.md
index c317a46e0e..b4565ed485 100644
--- a/browsers/internet-explorer/ie11-ieak/auto-version-sync-ieak11-wizard.md
+++ b/browsers/internet-explorer/ie11-ieak/auto-version-sync-ieak11-wizard.md
@@ -16,6 +16,9 @@ ms.date: 07/27/2017
# Use the Automatic Version Synchronization page in the IEAK 11 Wizard
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
The **Automatic Version Synchronization** page of the Internet Explorer Customization Wizard 11 runs the synchronization process every time you run the wizard, downloading the Internet Explorer 11 Setup file to your computer. The Setup file includes the required full and express packages.
**Important**
diff --git a/browsers/internet-explorer/ie11-ieak/before-you-create-custom-pkgs-ieak11.md b/browsers/internet-explorer/ie11-ieak/before-you-create-custom-pkgs-ieak11.md
index 3508c186af..7271837b2e 100644
--- a/browsers/internet-explorer/ie11-ieak/before-you-create-custom-pkgs-ieak11.md
+++ b/browsers/internet-explorer/ie11-ieak/before-you-create-custom-pkgs-ieak11.md
@@ -18,6 +18,9 @@ ms.date: 04/24/2018
# Before you start using IEAK 11
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
+
Before you run IEAK 11 and the Customization Wizard, make sure you have met the following requirements:
- Have you determined which licensing version of the Internet Explorer Administration Kit 11 to install? For info, see [Determine the licensing version and features to use in IEAK 11](licensing-version-and-features-ieak11.md).
diff --git a/browsers/internet-explorer/ie11-ieak/branding-ins-file-setting.md b/browsers/internet-explorer/ie11-ieak/branding-ins-file-setting.md
index 5c9c189f24..351b1bbb76 100644
--- a/browsers/internet-explorer/ie11-ieak/branding-ins-file-setting.md
+++ b/browsers/internet-explorer/ie11-ieak/branding-ins-file-setting.md
@@ -16,6 +16,9 @@ ms.date: 07/27/2017
# Use the Branding .INS file to create custom branding and setup info
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
Info about the custom branding and setup information in your browser package.
|Name |Value | Description |
diff --git a/browsers/internet-explorer/ie11-ieak/browser-ui-ieak11-wizard.md b/browsers/internet-explorer/ie11-ieak/browser-ui-ieak11-wizard.md
index c1f3999a3a..0116384f6d 100644
--- a/browsers/internet-explorer/ie11-ieak/browser-ui-ieak11-wizard.md
+++ b/browsers/internet-explorer/ie11-ieak/browser-ui-ieak11-wizard.md
@@ -16,6 +16,9 @@ ms.date: 07/27/2017
# Use the Browser User Interface page in the IEAK 11 Wizard
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
The **Browser User Interface** page of the Internet Explorer Customization Wizard 11 lets you change the toolbar buttons and the title bar text in IE.
**Note** The customizations you make on this page apply only to Internet Explorer for the desktop.
diff --git a/browsers/internet-explorer/ie11-ieak/browsertoolbars-ins-file-setting.md b/browsers/internet-explorer/ie11-ieak/browsertoolbars-ins-file-setting.md
index b2b123ff69..05fb2324f7 100644
--- a/browsers/internet-explorer/ie11-ieak/browsertoolbars-ins-file-setting.md
+++ b/browsers/internet-explorer/ie11-ieak/browsertoolbars-ins-file-setting.md
@@ -16,6 +16,9 @@ ms.date: 07/27/2017
# Use the BrowserToolbars .INS file to customize the Internet Explorer toolbar and buttons
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
Info about how to customize the Internet Explorer toolbar.
|Name |Value |Description |
diff --git a/browsers/internet-explorer/ie11-ieak/browsing-options-ieak11-wizard.md b/browsers/internet-explorer/ie11-ieak/browsing-options-ieak11-wizard.md
index a39adaff3e..3214ea32c0 100644
--- a/browsers/internet-explorer/ie11-ieak/browsing-options-ieak11-wizard.md
+++ b/browsers/internet-explorer/ie11-ieak/browsing-options-ieak11-wizard.md
@@ -16,6 +16,9 @@ ms.date: 07/27/2017
# Use the Browsing Options page in the IEAK 11 Wizard
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
The **Browsing Options** page of the Internet Explorer Administration Kit (IEAK 11) Customization Wizard lets you decide how you want to manage items in the **Favorites, Favorites Bar, and Feeds** section, including the Microsoft-provided default items.
The choices that you make on this page affect only the items shown on the **Favorites, Favorites Bar, and Feeds** page.
diff --git a/browsers/internet-explorer/ie11-ieak/cabsigning-ins-file-setting.md b/browsers/internet-explorer/ie11-ieak/cabsigning-ins-file-setting.md
index e5bf7ebb40..321f45caf5 100644
--- a/browsers/internet-explorer/ie11-ieak/cabsigning-ins-file-setting.md
+++ b/browsers/internet-explorer/ie11-ieak/cabsigning-ins-file-setting.md
@@ -16,6 +16,9 @@ ms.date: 07/27/2017
# Use the CabSigning .INS file to customize the digital signature info for your apps
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
Info about how to customize the digital signature info for your apps.
|Name |Value |Description |
diff --git a/browsers/internet-explorer/ie11-ieak/compat-view-ieak11-wizard.md b/browsers/internet-explorer/ie11-ieak/compat-view-ieak11-wizard.md
index cda9702eb4..b6138064be 100644
--- a/browsers/internet-explorer/ie11-ieak/compat-view-ieak11-wizard.md
+++ b/browsers/internet-explorer/ie11-ieak/compat-view-ieak11-wizard.md
@@ -17,6 +17,9 @@ ms.date: 07/27/2017
# Use the Compatibility View page in the IEAK 11 Wizard
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
We’re sorry. We’ve changed the way Compatibility View works in Internet Explorer 11 and have removed all of the functionality included on the **Compatibility View** page of the Internet Explorer Customization Wizard 11. For more info about the changes we’ve made to the Compatibility View functionality, see [Missing the Compatibility View Button](../ie11-deploy-guide/missing-the-compatibility-view-button.md).
Click **Next** to go to the [Programs](programs-ieak11-wizard.md) page or **Back** to go to the [Security and Privacy Settings](security-and-privacy-settings-ieak11-wizard.md) page.
diff --git a/browsers/internet-explorer/ie11-ieak/connection-mgr-ieak11-wizard.md b/browsers/internet-explorer/ie11-ieak/connection-mgr-ieak11-wizard.md
index aaec7b0fa2..e9051c955b 100644
--- a/browsers/internet-explorer/ie11-ieak/connection-mgr-ieak11-wizard.md
+++ b/browsers/internet-explorer/ie11-ieak/connection-mgr-ieak11-wizard.md
@@ -16,6 +16,9 @@ ms.date: 07/27/2017
# Use the Connection Manager page in the IEAK 11 Wizard
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
We're sorry. We've removed all of the functionality included on the Connection Manager page of the Internet Explorer Customization Wizard 11.
Click **Next** to go to the [Connection Settings](connection-settings-ieak11-wizard.md) page or **Back** to go to the [Compatibility View](compat-view-ieak11-wizard.md) page.
diff --git a/browsers/internet-explorer/ie11-ieak/connection-settings-ieak11-wizard.md b/browsers/internet-explorer/ie11-ieak/connection-settings-ieak11-wizard.md
index 66beabdbca..bc00c58bec 100644
--- a/browsers/internet-explorer/ie11-ieak/connection-settings-ieak11-wizard.md
+++ b/browsers/internet-explorer/ie11-ieak/connection-settings-ieak11-wizard.md
@@ -16,6 +16,9 @@ ms.date: 07/27/2017
# Use the Connection Settings page in the IEAK 11 Wizard
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
The **Connection Settings** page of the Internet Explorer Administration Kit (IEAK 11) Customization Wizard lets you import the connection settings from your computer, to preset the connection settings on your employee’s computers.
**Note** Using the options on the **Additional Settings** page of the wizard, you can let your employees change their connection settings. For more information see the [Additional Settings](additional-settings-ieak11-wizard.md) page. You can also customize additional connection settings using the **Automatic Configuration** page in the wizard. For more information see the [Automatic Configuration](auto-config-ieak11-wizard.md) page.
diff --git a/browsers/internet-explorer/ie11-ieak/connectionsettings-ins-file-setting.md b/browsers/internet-explorer/ie11-ieak/connectionsettings-ins-file-setting.md
index 779e024e57..0e7777a64e 100644
--- a/browsers/internet-explorer/ie11-ieak/connectionsettings-ins-file-setting.md
+++ b/browsers/internet-explorer/ie11-ieak/connectionsettings-ins-file-setting.md
@@ -16,6 +16,9 @@ ms.date: 07/27/2017
# Use the ConnectionSettings .INS file to review the network connections for install
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
Info about the network connection settings used to install your custom package. This section creates a common configuration on all of your employee’s computers.
|Name |Value |Description |
diff --git a/browsers/internet-explorer/ie11-ieak/create-build-folder-structure-ieak11.md b/browsers/internet-explorer/ie11-ieak/create-build-folder-structure-ieak11.md
index 91f26adf5b..0befbc922f 100644
--- a/browsers/internet-explorer/ie11-ieak/create-build-folder-structure-ieak11.md
+++ b/browsers/internet-explorer/ie11-ieak/create-build-folder-structure-ieak11.md
@@ -16,6 +16,9 @@ ms.date: 07/27/2017
# Create the build computer folder structure using IEAK 11
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
Create your build environment on the computer that you’ll use to build your custom browser package. Your license agreement determines your folder structure and which version of Internet Explorer Administration Kit 11 (IEAK 11) you’ll use: **Internal** or **External**.
|Name |Version |Description |
diff --git a/browsers/internet-explorer/ie11-ieak/create-manage-deploy-custom-pkgs-ieak11.md b/browsers/internet-explorer/ie11-ieak/create-manage-deploy-custom-pkgs-ieak11.md
index 3e8043c959..e2a0fb48a9 100644
--- a/browsers/internet-explorer/ie11-ieak/create-manage-deploy-custom-pkgs-ieak11.md
+++ b/browsers/internet-explorer/ie11-ieak/create-manage-deploy-custom-pkgs-ieak11.md
@@ -16,6 +16,9 @@ ms.date: 07/27/2017
# Tasks and references to consider before creating and deploying custom packages using IEAK 11
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
Review this list of tasks and references to help you use the Internet Explorer Administration Kit 11 (IEAK 11) to set up, deploy, and manage Internet Explorer 11 in your company.
|Task |References |
diff --git a/browsers/internet-explorer/ie11-ieak/create-multiple-browser-packages-ieak11.md b/browsers/internet-explorer/ie11-ieak/create-multiple-browser-packages-ieak11.md
index 6196fabf79..5d88bfa81a 100644
--- a/browsers/internet-explorer/ie11-ieak/create-multiple-browser-packages-ieak11.md
+++ b/browsers/internet-explorer/ie11-ieak/create-multiple-browser-packages-ieak11.md
@@ -16,6 +16,9 @@ ms.date: 07/27/2017
# Create multiple versions of your custom package using IEAK 11
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
You'll need to create multiple versions of your custom browser package if:
- You support more than 1 version of the Windows operating system.
diff --git a/browsers/internet-explorer/ie11-ieak/create-uninstall-inf-files-for-custom-components.md b/browsers/internet-explorer/ie11-ieak/create-uninstall-inf-files-for-custom-components.md
index 3cf498605c..ba3904ae39 100644
--- a/browsers/internet-explorer/ie11-ieak/create-uninstall-inf-files-for-custom-components.md
+++ b/browsers/internet-explorer/ie11-ieak/create-uninstall-inf-files-for-custom-components.md
@@ -16,6 +16,9 @@ ms.date: 07/27/2017
# Use uninstallation .INF files to uninstall custom components
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
The Internet Explorer Administration Kit 11 (IEAK 11) uses Setup information (.inf) files to provide installation instructions for your custom browser packages. You can also use this file to uninstall your custom components by removing the files, registry entries, and shortcuts, and adding your custom component to the list of programs that can be uninstalled from **Uninstall or change a program**.
**To uninstall your custom components**
diff --git a/browsers/internet-explorer/ie11-ieak/custom-components-ieak11-wizard.md b/browsers/internet-explorer/ie11-ieak/custom-components-ieak11-wizard.md
index 571b73d327..1a981a5a16 100644
--- a/browsers/internet-explorer/ie11-ieak/custom-components-ieak11-wizard.md
+++ b/browsers/internet-explorer/ie11-ieak/custom-components-ieak11-wizard.md
@@ -16,6 +16,9 @@ ms.date: 07/27/2017
# Use the Custom Components page in the IEAK 11 Wizard
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
The **Custom Components** page of the Internet Explorer Customization Wizard 11 lets you add up to 10 additional components that your employees can install at the same time they install IE. These components can be created by Microsoft or your organization as either compressed cabinet (.cab) or self-extracting executable (.exe) files. If you’re using Microsoft components, make sure you have the latest version and software patches from the [Microsoft Support](https://go.microsoft.com/fwlink/p/?LinkId=258658) site. To include Microsoft Update components, you must bundle the associated files into a custom component.
**Important** You should sign any custom code that’s being downloaded over the Internet. The default settings of Internet Explorer 11 will automatically reject any unsigned code. For more info about digitally signing custom components, see [Security features and IEAK 11](security-and-ieak11.md).
diff --git a/browsers/internet-explorer/ie11-ieak/custombranding-ins-file-setting.md b/browsers/internet-explorer/ie11-ieak/custombranding-ins-file-setting.md
index e7469fa864..7a5556235d 100644
--- a/browsers/internet-explorer/ie11-ieak/custombranding-ins-file-setting.md
+++ b/browsers/internet-explorer/ie11-ieak/custombranding-ins-file-setting.md
@@ -16,6 +16,9 @@ ms.date: 07/27/2017
# Use the CustomBranding .INS file to create custom branding and setup info
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
Provide the URL to your branding cabinet (.cab) file.
diff --git a/browsers/internet-explorer/ie11-ieak/customize-automatic-search-for-ie.md b/browsers/internet-explorer/ie11-ieak/customize-automatic-search-for-ie.md
index 3c0af97192..9ed59cf64e 100644
--- a/browsers/internet-explorer/ie11-ieak/customize-automatic-search-for-ie.md
+++ b/browsers/internet-explorer/ie11-ieak/customize-automatic-search-for-ie.md
@@ -16,6 +16,9 @@ ms.date: 07/27/2017
# Customize Automatic Search for Internet Explorer using IEAK 11
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
Internet Explorer lets websites advertise any search provider that uses the open search standard described at the A9 website ( [OpenSearch 1.1 Draft 5](https://go.microsoft.com/fwlink/p/?LinkId=208582)). When IE detects new search providers, the **Search** box becomes active and adds the new providers to the drop-down list of providers.
Using the **Administrative Templates** section of Group Policy, you can prevent the search box from appearing, you can add a list of acceptable search providers, or you can restrict your employee’s ability to add or remove search providers.
diff --git a/browsers/internet-explorer/ie11-ieak/extreginf-ins-file-setting.md b/browsers/internet-explorer/ie11-ieak/extreginf-ins-file-setting.md
index 06e8d6c3f3..7d0a2f9882 100644
--- a/browsers/internet-explorer/ie11-ieak/extreginf-ins-file-setting.md
+++ b/browsers/internet-explorer/ie11-ieak/extreginf-ins-file-setting.md
@@ -16,6 +16,9 @@ ms.date: 07/27/2017
# Use the ExtRegInf .INS file to specify installation files and mode
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
Info about how to specify your Setup information (.inf) files and the installation mode for your custom components.
|Name |Value |Description |
diff --git a/browsers/internet-explorer/ie11-ieak/favorites-favoritesbar-and-feeds-ieak11-wizard.md b/browsers/internet-explorer/ie11-ieak/favorites-favoritesbar-and-feeds-ieak11-wizard.md
index 47bf04d6e2..030dc054d2 100644
--- a/browsers/internet-explorer/ie11-ieak/favorites-favoritesbar-and-feeds-ieak11-wizard.md
+++ b/browsers/internet-explorer/ie11-ieak/favorites-favoritesbar-and-feeds-ieak11-wizard.md
@@ -16,6 +16,9 @@ ms.date: 07/27/2017
# Use the Favorites, Favorites Bar, and Feeds page in the IEAK 11 Wizard
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
The **Favorites, Favorites Bar, and Feeds** page of the Internet Explorer Administration Kit (IEAK 11) Customization Wizard lets you add:
- **Links.** Used so your employees can quickly connect with your important websites. These links can appear in the **Links** folder or on the **Favorites Bar**.
diff --git a/browsers/internet-explorer/ie11-ieak/favoritesex-ins-file-setting.md b/browsers/internet-explorer/ie11-ieak/favoritesex-ins-file-setting.md
index 694b8d994d..ac736e20df 100644
--- a/browsers/internet-explorer/ie11-ieak/favoritesex-ins-file-setting.md
+++ b/browsers/internet-explorer/ie11-ieak/favoritesex-ins-file-setting.md
@@ -16,6 +16,9 @@ ms.date: 07/27/2017
# Use the FavoritesEx .INS file for your Favorites icon and URLs
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
Info about where you store your **Favorites** icon file, whether your **Favorites** are available offline, and the URLs for each **Favorites** site.
|Name |Value |Description |
diff --git a/browsers/internet-explorer/ie11-ieak/feature-selection-ieak11-wizard.md b/browsers/internet-explorer/ie11-ieak/feature-selection-ieak11-wizard.md
index b27bc3273a..f72747f486 100644
--- a/browsers/internet-explorer/ie11-ieak/feature-selection-ieak11-wizard.md
+++ b/browsers/internet-explorer/ie11-ieak/feature-selection-ieak11-wizard.md
@@ -15,6 +15,9 @@ ms.sitesec: library
# Use the Feature Selection page in the IEAK 11 Wizard
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
The **Feature Selection** page of the Internet Explorer Customization Wizard 11 lets you choose which parts of the setup processes and Internet Explorer 11 to change for your company, including:
- **Setup Customizations.** Lets you add custom components, decide which components to install, provide your download site information, and modify the Setup title bar and graphics.
diff --git a/browsers/internet-explorer/ie11-ieak/file-locations-ieak11-wizard.md b/browsers/internet-explorer/ie11-ieak/file-locations-ieak11-wizard.md
index f3224c2055..0aee908cd4 100644
--- a/browsers/internet-explorer/ie11-ieak/file-locations-ieak11-wizard.md
+++ b/browsers/internet-explorer/ie11-ieak/file-locations-ieak11-wizard.md
@@ -16,6 +16,9 @@ ms.date: 07/27/2017
# Use the File Locations page in the IEAK 11 Wizard
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
The **File Locations** page of the Internet Explorer Customization Wizard 11 lets you change the location of your folders, including:
- Where you’ll create and store your custom installation package.
diff --git a/browsers/internet-explorer/ie11-ieak/file-types-ieak11.md b/browsers/internet-explorer/ie11-ieak/file-types-ieak11.md
index 38703f9131..616e3b9938 100644
--- a/browsers/internet-explorer/ie11-ieak/file-types-ieak11.md
+++ b/browsers/internet-explorer/ie11-ieak/file-types-ieak11.md
@@ -16,6 +16,9 @@ ms.date: 07/27/2017
# File types used or created by IEAK 11
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
A list of the file types used or created by tools in IEAK 11:
|File type |Description |
diff --git a/browsers/internet-explorer/ie11-ieak/first-run-and-welcome-page-ieak11-wizard.md b/browsers/internet-explorer/ie11-ieak/first-run-and-welcome-page-ieak11-wizard.md
index 507450938d..9d6fe74f8a 100644
--- a/browsers/internet-explorer/ie11-ieak/first-run-and-welcome-page-ieak11-wizard.md
+++ b/browsers/internet-explorer/ie11-ieak/first-run-and-welcome-page-ieak11-wizard.md
@@ -16,6 +16,9 @@ ms.date: 07/27/2017
# Use the First Run Wizard and Welcome Page Options page in the IEAK 11 Wizard
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
The **First Run Wizard and Welcome Page Options** page of the Internet Explorer Customization Wizard 11 lets you decide what your employee’s see the first time they log on to IE, based on their operating system.
- **Windows 8.1 Update and newer.** No longer includes a **Welcome** page, so if you pick the **Use Internet Explorer 11 Welcome Page** or the **Use a custom Welcome page** option, IEAK creates an initial **Home** page that loads before all other **Home** pages, as the first tab. This only applies to the Internet Explorer for the desktop.
diff --git a/browsers/internet-explorer/ie11-ieak/guidelines-toolbar-and-favorites-list-ieak11.md b/browsers/internet-explorer/ie11-ieak/guidelines-toolbar-and-favorites-list-ieak11.md
index 0864538448..e3d95badec 100644
--- a/browsers/internet-explorer/ie11-ieak/guidelines-toolbar-and-favorites-list-ieak11.md
+++ b/browsers/internet-explorer/ie11-ieak/guidelines-toolbar-and-favorites-list-ieak11.md
@@ -16,6 +16,9 @@ ms.date: 07/27/2017
# Customize the Toolbar button and Favorites List icons using IEAK 11
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
Use these customization guidelines to change the browser toolbar button and the **Favorites List** icons, using your own branding and graphics.
**Important** Check your license agreement to make sure this customization is available.
diff --git a/browsers/internet-explorer/ie11-ieak/hardware-and-software-reqs-ieak11.md b/browsers/internet-explorer/ie11-ieak/hardware-and-software-reqs-ieak11.md
index 0ba0f580a8..2da43b7f38 100644
--- a/browsers/internet-explorer/ie11-ieak/hardware-and-software-reqs-ieak11.md
+++ b/browsers/internet-explorer/ie11-ieak/hardware-and-software-reqs-ieak11.md
@@ -16,6 +16,9 @@ ms.date: 07/27/2017
# Hardware and software requirements for Internet Explorer 11 and the IEAK 11
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
Before you can use the Internet Explorer Administration Kit 11 and the Internet Explorer Customization Wizard 11, you must first install Internet Explorer 11. For more info about installing IE11, see the [Determine the licensing version and features to use in IEAK 11](licensing-version-and-features-ieak11.md) page.
## Hardware requirements
diff --git a/browsers/internet-explorer/ie11-ieak/hidecustom-ins-file-setting.md b/browsers/internet-explorer/ie11-ieak/hidecustom-ins-file-setting.md
index 7d50512355..6c46e306f3 100644
--- a/browsers/internet-explorer/ie11-ieak/hidecustom-ins-file-setting.md
+++ b/browsers/internet-explorer/ie11-ieak/hidecustom-ins-file-setting.md
@@ -16,6 +16,9 @@ ms.date: 07/27/2017
# Use the HideCustom .INS file to hide the GUID for each custom component
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
Info about whether to hide the globally unique identifier (GUID) for each of your custom components.
|Name |Value |Description |
diff --git a/browsers/internet-explorer/ie11-ieak/ie-setup-command-line-options-and-return-codes.md b/browsers/internet-explorer/ie11-ieak/ie-setup-command-line-options-and-return-codes.md
index 51dc959759..c9d24160a9 100644
--- a/browsers/internet-explorer/ie11-ieak/ie-setup-command-line-options-and-return-codes.md
+++ b/browsers/internet-explorer/ie11-ieak/ie-setup-command-line-options-and-return-codes.md
@@ -16,6 +16,9 @@ ms.date: 07/27/2017
# Internet Explorer Setup command-line options and return codes
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
You can use command-line options along with a tool like IExpress to package your custom version of Internet Explorer and to perform a batch installation across your organization.
## IE Setup command-line options
diff --git a/browsers/internet-explorer/ie11-ieak/ieak-information-and-downloads.md b/browsers/internet-explorer/ie11-ieak/ieak-information-and-downloads.md
index b8c3d25c24..1d8b34786a 100644
--- a/browsers/internet-explorer/ie11-ieak/ieak-information-and-downloads.md
+++ b/browsers/internet-explorer/ie11-ieak/ieak-information-and-downloads.md
@@ -18,6 +18,9 @@ ms.date: 05/10/2018
# Internet Explorer Administration Kit (IEAK) information and downloads
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
+
>Applies to: Windows 10
The Internet Explorer Administration Kit (IEAK) simplifies the creation, deployment, and management of customized Internet Explorer packages. You can use the IEAK to configure the out-of-box Internet Explorer experience or to manage user settings after Internet Explorer deployment. To find more information on the IEAK, see [What IEAK can do for you](what-ieak-can-do-for-you.md).
diff --git a/browsers/internet-explorer/ie11-ieak/ieak11-wizard-custom-options.md b/browsers/internet-explorer/ie11-ieak/ieak11-wizard-custom-options.md
index f27ec8b5b9..0aa9964807 100644
--- a/browsers/internet-explorer/ie11-ieak/ieak11-wizard-custom-options.md
+++ b/browsers/internet-explorer/ie11-ieak/ieak11-wizard-custom-options.md
@@ -16,6 +16,9 @@ ms.date: 07/27/2017
# Internet Explorer Administration Kit 11 (IEAK 11) Customization Wizard options
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
Use the Internet Explorer Administration Kit 11 (IEAK 11) and the Internet Explorer Customization Wizard 11 to customize your browser install packages for deployment to your employee's devices.
## IE Customization Wizard 11 options
diff --git a/browsers/internet-explorer/ie11-ieak/iexpress-command-line-options.md b/browsers/internet-explorer/ie11-ieak/iexpress-command-line-options.md
index cd7c730569..57128dfefe 100644
--- a/browsers/internet-explorer/ie11-ieak/iexpress-command-line-options.md
+++ b/browsers/internet-explorer/ie11-ieak/iexpress-command-line-options.md
@@ -16,6 +16,9 @@ ms.date: 07/27/2017
# IExpress Wizard command-line options
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
+
**Applies to:**
- Windows Server 2008 R2 with SP1
diff --git a/browsers/internet-explorer/ie11-ieak/iexpress-wizard-for-win-server.md b/browsers/internet-explorer/ie11-ieak/iexpress-wizard-for-win-server.md
index 35dc9f9cc5..fe4bb3a985 100644
--- a/browsers/internet-explorer/ie11-ieak/iexpress-wizard-for-win-server.md
+++ b/browsers/internet-explorer/ie11-ieak/iexpress-wizard-for-win-server.md
@@ -16,6 +16,9 @@ ms.date: 07/27/2017
# IExpress Wizard for Windows Server 2008 R2 with SP1
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
Use the IExpress Wizard and its associated command-line options to create self-extracting files that automatically run your custom Internet Explorer Setup (.inf or .exe file) program that’s contained inside.
## IExpress Wizard location
diff --git a/browsers/internet-explorer/ie11-ieak/important-urls-home-page-and-support-ieak11-wizard.md b/browsers/internet-explorer/ie11-ieak/important-urls-home-page-and-support-ieak11-wizard.md
index 022767b179..b32b5bacab 100644
--- a/browsers/internet-explorer/ie11-ieak/important-urls-home-page-and-support-ieak11-wizard.md
+++ b/browsers/internet-explorer/ie11-ieak/important-urls-home-page-and-support-ieak11-wizard.md
@@ -16,6 +16,9 @@ ms.date: 07/27/2017
# Use the Important URLs - Home Page and Support page in the IEAK 11 Wizard
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
The **Important URLS – Home Page and Support** page of the Internet Explorer Customization Wizard 11 lets you choose one or more **Home** pages and an online support page for your customized version of IE.
**To use the Important URLS – Home Page and Support page**
diff --git a/browsers/internet-explorer/ie11-ieak/index.md b/browsers/internet-explorer/ie11-ieak/index.md
index 29b8c0ceca..946a42e72a 100644
--- a/browsers/internet-explorer/ie11-ieak/index.md
+++ b/browsers/internet-explorer/ie11-ieak/index.md
@@ -14,6 +14,9 @@ manager: dansimp
# Internet Explorer Administration Kit 11 (IEAK 11) - Administrator's Guide
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
+
The Internet Explorer Administration Kit (IEAK) simplifies the creation, deployment, and management of customized Internet Explorer packages. You can use the IEAK to configure the out-of-box Internet Explorer experience or to manage user settings after Internet Explorer deployment.
Use this guide to learn about the several options and processes you'll need to consider while you're using the Internet Explorer Administration Kit 11 (IEAK 11) to customize, deploy, and manage Internet Explorer 11 for your employee's devices.
diff --git a/browsers/internet-explorer/ie11-ieak/internal-install-ieak11-wizard.md b/browsers/internet-explorer/ie11-ieak/internal-install-ieak11-wizard.md
index 15db2bc20f..6936f198d0 100644
--- a/browsers/internet-explorer/ie11-ieak/internal-install-ieak11-wizard.md
+++ b/browsers/internet-explorer/ie11-ieak/internal-install-ieak11-wizard.md
@@ -16,6 +16,9 @@ ms.date: 07/27/2017
# Use the Internal Install page in the IEAK 11 Wizard
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
The **Internal Install** page of the Internet Explorer Customization Wizard 11 lets you customize Setup for the default browser and the latest browser updates, based on your company’s guidelines.
**Note** The customizations made on this page only apply to Internet Explorer for the desktop on Windows 7.
diff --git a/browsers/internet-explorer/ie11-ieak/isp-security-ins-file-setting.md b/browsers/internet-explorer/ie11-ieak/isp-security-ins-file-setting.md
index b625916fd1..666c5f8b17 100644
--- a/browsers/internet-explorer/ie11-ieak/isp-security-ins-file-setting.md
+++ b/browsers/internet-explorer/ie11-ieak/isp-security-ins-file-setting.md
@@ -16,6 +16,9 @@ ms.date: 07/27/2017
# Use the ISP_Security .INS file to add your root certificate
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
Info about where you store the root certificate you’re adding to your custom package.
|Name |Value |Description |
diff --git a/browsers/internet-explorer/ie11-ieak/language-selection-ieak11-wizard.md b/browsers/internet-explorer/ie11-ieak/language-selection-ieak11-wizard.md
index b2f66781b7..a343a30e51 100644
--- a/browsers/internet-explorer/ie11-ieak/language-selection-ieak11-wizard.md
+++ b/browsers/internet-explorer/ie11-ieak/language-selection-ieak11-wizard.md
@@ -16,6 +16,9 @@ ms.date: 07/27/2017
# Use the Language Selection page in the IEAK 11 Wizard
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
The **Language Selection** page of the Internet Explorer Customization Wizard 11 lets you choose the language for your Internet Explorer Administration Kit 11 (IEAK 11) custom package. You can create custom Internet Explorer 11 packages in any of the languages your operating system version is available in.
**Important** Make sure that the language of your IEAK 11 installation matches the language of your custom IE11 package. If the languages don’t match, IEAK 11 won’t work properly.
diff --git a/browsers/internet-explorer/ie11-ieak/licensing-version-and-features-ieak11.md b/browsers/internet-explorer/ie11-ieak/licensing-version-and-features-ieak11.md
index ea1f1cb9e1..4c14f5ec98 100644
--- a/browsers/internet-explorer/ie11-ieak/licensing-version-and-features-ieak11.md
+++ b/browsers/internet-explorer/ie11-ieak/licensing-version-and-features-ieak11.md
@@ -16,6 +16,9 @@ ms.date: 10/23/2018
# Determine the licensing version and features to use in IEAK 11
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
In addition to the Software License Terms for the Internet Explorer Administration Kit 11 (IEAK 11, referred to as the "software"), these Guidelines further define how you may and may not use the software to create versions of Internet Explorer 11 with optional customizations (referred to as the "customized browser") for internal use and distribution in accordance with the IEAK 11 Software License Terms. IEAK 11 is for testing purposes only and is not intended to be used in a production environment.
During installation, you must pick a version of IEAK 11, either **External** or **Internal**, based on your license agreement. Your version selection decides the options you can chose, the steps you follow to deploy your Internet Explorer 11 package, and how you manage the browser after deployment.
diff --git a/browsers/internet-explorer/ie11-ieak/media-ins-file-setting.md b/browsers/internet-explorer/ie11-ieak/media-ins-file-setting.md
index a441fe7be2..f628def610 100644
--- a/browsers/internet-explorer/ie11-ieak/media-ins-file-setting.md
+++ b/browsers/internet-explorer/ie11-ieak/media-ins-file-setting.md
@@ -16,6 +16,9 @@ ms.date: 07/27/2017
# Use the Media .INS file to specify your install media
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
The types of media on which your custom install package is available.
|Name |Value |Description |
diff --git a/browsers/internet-explorer/ie11-ieak/pkg-type-selection-ieak11-wizard.md b/browsers/internet-explorer/ie11-ieak/pkg-type-selection-ieak11-wizard.md
index ce2517bf60..ae7b3c6150 100644
--- a/browsers/internet-explorer/ie11-ieak/pkg-type-selection-ieak11-wizard.md
+++ b/browsers/internet-explorer/ie11-ieak/pkg-type-selection-ieak11-wizard.md
@@ -16,6 +16,9 @@ ms.date: 07/27/2017
# Use the Package Type Selection page in the IEAK 11 Wizard
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
The **Package Type Selection** page of the Internet Explorer Customization Wizard 11 lets you pick which type of media you’ll use to distribute your custom installation package. You can pick more than one type, if you need it.
**Important** You can't create a full installation package for deployment to Windows 10 computers. That option only works for computers running Windows 7 or Windows 8.1.
diff --git a/browsers/internet-explorer/ie11-ieak/platform-selection-ieak11-wizard.md b/browsers/internet-explorer/ie11-ieak/platform-selection-ieak11-wizard.md
index 342ac46d58..67d9caac65 100644
--- a/browsers/internet-explorer/ie11-ieak/platform-selection-ieak11-wizard.md
+++ b/browsers/internet-explorer/ie11-ieak/platform-selection-ieak11-wizard.md
@@ -15,6 +15,9 @@ ms.date: 07/27/2017
# Use the Platform Selection page in the IEAK 11 Wizard
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
The **Platform Selection** page of the Internet Explorer Customization Wizard 11 lets you pick the operating system and architecture (32-bit or 64-bit) for the devices on which you’re going to install the custom installation package.
**To use the Platform Selection page**
diff --git a/browsers/internet-explorer/ie11-ieak/prep-network-install-with-ieak11.md b/browsers/internet-explorer/ie11-ieak/prep-network-install-with-ieak11.md
index 809110fc8b..4720c446af 100644
--- a/browsers/internet-explorer/ie11-ieak/prep-network-install-with-ieak11.md
+++ b/browsers/internet-explorer/ie11-ieak/prep-network-install-with-ieak11.md
@@ -16,6 +16,9 @@ ms.date: 07/27/2017
# Before you install your package over your network using IEAK 11
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
Employees can install the custom browser package using a network server. However, you must either lower the intranet security level or make the server a trusted site.
**To lower your intranet security**
diff --git a/browsers/internet-explorer/ie11-ieak/programs-ieak11-wizard.md b/browsers/internet-explorer/ie11-ieak/programs-ieak11-wizard.md
index 8b46cc1615..acfbbc74ae 100644
--- a/browsers/internet-explorer/ie11-ieak/programs-ieak11-wizard.md
+++ b/browsers/internet-explorer/ie11-ieak/programs-ieak11-wizard.md
@@ -15,6 +15,9 @@ ms.date: 07/27/2017
# Use the Programs page in the IEAK 11 Wizard
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
The **Programs** page of the Internet Explorer Customization Wizard 11 lets you pick the default programs to use for Internet services, like email, contact lists, and newsgroups, by importing settings from your computer.
**Important** The customizations you make on this page only apply to Internet Explorer for the desktop.
diff --git a/browsers/internet-explorer/ie11-ieak/proxy-auto-config-examples.md b/browsers/internet-explorer/ie11-ieak/proxy-auto-config-examples.md
index 06213a78ae..56a0823f9a 100644
--- a/browsers/internet-explorer/ie11-ieak/proxy-auto-config-examples.md
+++ b/browsers/internet-explorer/ie11-ieak/proxy-auto-config-examples.md
@@ -16,6 +16,9 @@ ms.date: 07/27/2017
# Use proxy auto-configuration (.pac) files with IEAK 11
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
These are various ways you can use a proxy auto-configuration (.pac) file to specify an automatic proxy URL. We've included some examples here to help guide you, but you'll need to change the proxy names, port numbers, and IP addresses to match your organization's info.
Included examples:
diff --git a/browsers/internet-explorer/ie11-ieak/proxy-ins-file-setting.md b/browsers/internet-explorer/ie11-ieak/proxy-ins-file-setting.md
index 80e2e5d2c0..9def48f2d3 100644
--- a/browsers/internet-explorer/ie11-ieak/proxy-ins-file-setting.md
+++ b/browsers/internet-explorer/ie11-ieak/proxy-ins-file-setting.md
@@ -16,6 +16,9 @@ ms.date: 07/27/2017
# Use the Proxy .INS file to specify a proxy server
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
Info about whether to use a proxy server. If yes, this also includes the host names for the proxy server.
|Name |Value |Description |
diff --git a/browsers/internet-explorer/ie11-ieak/proxy-settings-ieak11-wizard.md b/browsers/internet-explorer/ie11-ieak/proxy-settings-ieak11-wizard.md
index a99dc70ae0..ba113af6cc 100644
--- a/browsers/internet-explorer/ie11-ieak/proxy-settings-ieak11-wizard.md
+++ b/browsers/internet-explorer/ie11-ieak/proxy-settings-ieak11-wizard.md
@@ -16,6 +16,9 @@ ms.date: 07/27/2017
# Use the Proxy Settings page in the IEAK 11 Wizard
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
The **Proxy Settings** page of the Internet Explorer Customization Wizard 11 lets you pick the proxy servers used by your employees to connect for services required by the custom install package.
Using a proxy server lets you limit access to the Internet. You can also use the **Additional Settings** page of the wizard to further restrict your employees from changing the proxy settings.
diff --git a/browsers/internet-explorer/ie11-ieak/register-uninstall-app-ieak11.md b/browsers/internet-explorer/ie11-ieak/register-uninstall-app-ieak11.md
index c6fb131002..f3b4414183 100644
--- a/browsers/internet-explorer/ie11-ieak/register-uninstall-app-ieak11.md
+++ b/browsers/internet-explorer/ie11-ieak/register-uninstall-app-ieak11.md
@@ -15,6 +15,9 @@ ms.date: 07/27/2017
# Register an uninstall app for custom components using IEAK 11
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
Register the uninstall apps for any custom components you’ve included in your Internet Explorer 11 package. Registering these apps lets your employees remove the components later, using **Uninstall or change a program** in the Control Panel.
## Register your uninstallation program
diff --git a/browsers/internet-explorer/ie11-ieak/rsop-snapin-for-policy-settings-ieak11.md b/browsers/internet-explorer/ie11-ieak/rsop-snapin-for-policy-settings-ieak11.md
index 8bf7232c7c..340327e916 100644
--- a/browsers/internet-explorer/ie11-ieak/rsop-snapin-for-policy-settings-ieak11.md
+++ b/browsers/internet-explorer/ie11-ieak/rsop-snapin-for-policy-settings-ieak11.md
@@ -16,6 +16,9 @@ ms.date: 07/27/2017
# Using the Resultant Set of Policy (RSoP) snap-in to review policy settings
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
After you’ve deployed your custom Internet Explorer package to your employees, you can use the Resultant Set of Policy (RSoP) snap-in to view your created policy settings. The RSoP snap-in is a two-step process. First, you run the RSoP wizard to determine what information should be viewed. Second, you open the specific items in the console window to view the settings. For complete instructions about how to use RSoP, see [Resultant Set of Policy](https://go.microsoft.com/fwlink/p/?LinkId=259479).
**To add the RSoP snap-in**
diff --git a/browsers/internet-explorer/ie11-ieak/search-providers-ieak11-wizard.md b/browsers/internet-explorer/ie11-ieak/search-providers-ieak11-wizard.md
index f66425a743..c092a2101b 100644
--- a/browsers/internet-explorer/ie11-ieak/search-providers-ieak11-wizard.md
+++ b/browsers/internet-explorer/ie11-ieak/search-providers-ieak11-wizard.md
@@ -16,6 +16,9 @@ ms.date: 07/27/2017
# Use the Search Providers page in the IEAK 11 Wizard
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
The **Search Providers** page of the Internet Explorer Customization Wizard 11 lets you add a default search provider (typically, Bing®) and additional providers to your custom version of IE.
**Note** The Internet Explorer Customization Wizard 11 offers improved and extended search settings. However, you can still optionally include support for Search Suggestions and Favicons, as well as Accelerator previews by using an .ins file from a previous version of IEAK.
diff --git a/browsers/internet-explorer/ie11-ieak/security-and-ieak11.md b/browsers/internet-explorer/ie11-ieak/security-and-ieak11.md
index 71d99f8b9f..336ad87ef1 100644
--- a/browsers/internet-explorer/ie11-ieak/security-and-ieak11.md
+++ b/browsers/internet-explorer/ie11-ieak/security-and-ieak11.md
@@ -16,6 +16,9 @@ ms.date: 07/27/2017
# Security features and IEAK 11
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
Use Internet Explorer in conjunction with your new and existing security measures, to make sure the computers in your company aren’t compromised while on the Internet.
## Enhanced Protection Mode
diff --git a/browsers/internet-explorer/ie11-ieak/security-and-privacy-settings-ieak11-wizard.md b/browsers/internet-explorer/ie11-ieak/security-and-privacy-settings-ieak11-wizard.md
index 16ffc69435..c78a131719 100644
--- a/browsers/internet-explorer/ie11-ieak/security-and-privacy-settings-ieak11-wizard.md
+++ b/browsers/internet-explorer/ie11-ieak/security-and-privacy-settings-ieak11-wizard.md
@@ -16,6 +16,9 @@ ms.date: 07/27/2017
# Use the Security and Privacy Settings page in the IEAK 11 Wizard
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
The **Security and Privacy Settings** page of the Internet Explorer Customization Wizard 11 lets you manage your security zones, privacy settings, and content ratings. These settings help restrict the types of content your employees can access from the Internet, including any content that might be considered offensive or otherwise inappropriate in a corporate setting.
**To use the Security and Privacy Settings page**
diff --git a/browsers/internet-explorer/ie11-ieak/security-imports-ins-file-setting.md b/browsers/internet-explorer/ie11-ieak/security-imports-ins-file-setting.md
index e65b0e2b77..b4fd0c45b2 100644
--- a/browsers/internet-explorer/ie11-ieak/security-imports-ins-file-setting.md
+++ b/browsers/internet-explorer/ie11-ieak/security-imports-ins-file-setting.md
@@ -16,6 +16,9 @@ ms.date: 07/27/2017
# Use the Security Imports .INS file to import security info
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
Info about how to import security information from your local device to your custom package.
|Name |Value |Description |
diff --git a/browsers/internet-explorer/ie11-ieak/troubleshooting-custom-browser-pkg-ieak11.md b/browsers/internet-explorer/ie11-ieak/troubleshooting-custom-browser-pkg-ieak11.md
index 9ae559b4b4..e4fcd7c739 100644
--- a/browsers/internet-explorer/ie11-ieak/troubleshooting-custom-browser-pkg-ieak11.md
+++ b/browsers/internet-explorer/ie11-ieak/troubleshooting-custom-browser-pkg-ieak11.md
@@ -16,6 +16,9 @@ ms.date: 07/27/2017
# Troubleshoot custom package and IEAK 11 problems
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
While the Internet Explorer Customization Wizard has been around for quite a while, there are still some known issues that you might encounter while deploying or managing your custom IE install package.
## I am unable to locate some of the wizard pages
diff --git a/browsers/internet-explorer/ie11-ieak/url-ins-file-setting.md b/browsers/internet-explorer/ie11-ieak/url-ins-file-setting.md
index 965fda174e..06a1d3c029 100644
--- a/browsers/internet-explorer/ie11-ieak/url-ins-file-setting.md
+++ b/browsers/internet-explorer/ie11-ieak/url-ins-file-setting.md
@@ -1,40 +1,44 @@
----
-ms.localizationpriority: medium
-ms.mktglfcycl: deploy
-description: Use the \[URL\] .INS file setting to decide whether to use an auto-configured proxy server.
-author: dansimp
-ms.prod: ie11
-ms.assetid: 05b09dfa-cf11-408d-92c2-b4ae434a59a7
-ms.reviewer:
-audience: itpro
manager: dansimp
-ms.author: dansimp
-title: Use the URL .INS file to use an auto-configured proxy server (Internet Explorer Administration Kit 11 for IT Pros)
-ms.sitesec: library
-ms.date: 07/27/2017
----
-
-
-# Use the URL .INS file to use an auto-configured proxy server
-Info about whether to use an auto-configured proxy server. If yes, this also includes the URLs to the pages that appear when your employees first connect to that server.
-
-|Name |Value |Description |
-|-----|------|------------|
-|AutoConfig |
**0.** Don’t automatically configure the browser.
**1.** Automatically configure the browser.
|Determines whether to automatically configure the customized browser on your employee’s device. |
-|AutoConfigJSURL |`` |The URL for the proxy auto-config file (.js or .jvs) |
-|AutoConfigTime |*integer* |Automatically configures the browser on your employee’s device after its run for a specified length of time. |
-|AutoConfigURL |`` |The URL for the proxy auto-config (.pac) file. |
-|FirstHomePage |`` |The page (URL) that appears the first time the custom browser is opened on the employee’s device. |
-|Help_Page |`` |The URL to your internal technical support site. |
-|Home_Page |`` |The URL to your default **Home** page. |
-|NoWelcome |
**0.** Display the **Welcome** page.
**1.** Don’t display the **Welcome** page.
|Determines whether to show the **Welcome** page the first time the browser’s used on an employee’s device. |
-|Quick_Link_1 |`` |The URL to your first Quick Link. |
-|Quick_Link_1_Name |`` |The name of the site associated with Quick_Link_1. |
-|Quick_Link_2 |`` |The URL to your second Quick Link. |
-|Quick_Link_2_Name |`` |The name of the site associated with Quick_Link_2. |
-|Quick_Link_X |`` |The URL to another Quick Link. |
-|Quick_Link_X_Icon |`` |A Quick Links icon (.ico) file. |
-|Quick_Link_X_Name |`` |The name of the site associated with another Quick Link. |
-|Quick_Link_X_Offline |
**0.** Don’t make the Quick Links available offline.
**1.** Make the Quick Links available offline.
|Determines whether to make the Quick Links available for offline browsing. |
-|Search_Page |`` |The URL to the default search page. |
-|UseLocalIns |
**0.** Don’t use a local .ins file.
**1.** Use a local .ins file.
|Determines whether to use a local Internet Settings (.ins) file |
-
+---
+ms.localizationpriority: medium
+ms.mktglfcycl: deploy
+description: Use the \[URL\] .INS file setting to decide whether to use an auto-configured proxy server.
+author: dansimp
+ms.prod: ie11
+ms.assetid: 05b09dfa-cf11-408d-92c2-b4ae434a59a7
+ms.reviewer:
+audience: itpro
+manager: dansimp
+ms.author: dansimp
+title: Use the URL .INS file to use an auto-configured proxy server (Internet Explorer Administration Kit 11 for IT Pros)
+ms.sitesec: library
+ms.date: 07/27/2017
+---
+
+
+# Use the URL .INS file to use an auto-configured proxy server
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
+Info about whether to use an auto-configured proxy server. If yes, this also includes the URLs to the pages that appear when your employees first connect to that server.
+
+|Name |Value |Description |
+|-----|------|------------|
+|AutoConfig |
**0.** Don’t automatically configure the browser.
**1.** Automatically configure the browser.
|Determines whether to automatically configure the customized browser on your employee’s device. |
+|AutoConfigJSURL |`` |The URL for the proxy auto-config file (.js or .jvs) |
+|AutoConfigTime |*integer* |Automatically configures the browser on your employee’s device after its run for a specified length of time. |
+|AutoConfigURL |`` |The URL for the proxy auto-config (.pac) file. |
+|FirstHomePage |`` |The page (URL) that appears the first time the custom browser is opened on the employee’s device. |
+|Help_Page |`` |The URL to your internal technical support site. |
+|Home_Page |`` |The URL to your default **Home** page. |
+|NoWelcome |
**0.** Display the **Welcome** page.
**1.** Don’t display the **Welcome** page.
|Determines whether to show the **Welcome** page the first time the browser’s used on an employee’s device. |
+|Quick_Link_1 |`` |The URL to your first Quick Link. |
+|Quick_Link_1_Name |`` |The name of the site associated with Quick_Link_1. |
+|Quick_Link_2 |`` |The URL to your second Quick Link. |
+|Quick_Link_2_Name |`` |The name of the site associated with Quick_Link_2. |
+|Quick_Link_X |`` |The URL to another Quick Link. |
+|Quick_Link_X_Icon |`` |A Quick Links icon (.ico) file. |
+|Quick_Link_X_Name |`` |The name of the site associated with another Quick Link. |
+|Quick_Link_X_Offline |
**0.** Don’t make the Quick Links available offline.
**1.** Make the Quick Links available offline.
|Determines whether to make the Quick Links available for offline browsing. |
+|Search_Page |`` |The URL to the default search page. |
+|UseLocalIns |
**0.** Don’t use a local .ins file.
**1.** Use a local .ins file.
|Determines whether to use a local Internet Settings (.ins) file |
+
diff --git a/browsers/internet-explorer/ie11-ieak/user-experience-ieak11-wizard.md b/browsers/internet-explorer/ie11-ieak/user-experience-ieak11-wizard.md
index ed8f2be8f1..364daedbbc 100644
--- a/browsers/internet-explorer/ie11-ieak/user-experience-ieak11-wizard.md
+++ b/browsers/internet-explorer/ie11-ieak/user-experience-ieak11-wizard.md
@@ -1,60 +1,64 @@
----
-ms.localizationpriority: medium
-ms.mktglfcycl: deploy
-description: How to use the User Experience page in the IEAK 11 Customization Wizard to decide user interaction with the Setup process.
-author: dansimp
-ms.prod: ie11
-ms.assetid: d3378058-e4f0-4a11-a888-b550af994bfa
-ms.reviewer:
-audience: itpro
manager: dansimp
-ms.author: dansimp
-title: Use the User Experience page in the IEAK 11 Wizard (Internet Explorer Administration Kit 11 for IT Pros)
-ms.sitesec: library
-ms.date: 07/27/2017
----
-
-
-# Use the User Experience page in the IEAK 11 Wizard
-The **User Experience** page of the Internet Explorer Customization Wizard 11 lets you decide how much you want your employees to interact with the custom package’s Setup process.
-
-**Note** You’ll only see this page if you are running the **Internal** version of the Internet Explorer Customization Wizard 11.
The customizations you make on this page only apply to Internet Explorer for the desktop on Windows 7.
-
-**To use the User Experience page**
-
-1. Choose how your employee should interact with Setup, including:
-
- - **Interactive installation**. Lets your employees change installation options while installing your custom package. This experience shows all of the progress and error messages throughout the process.
-
- - **Hands-free installation**. Lets you make all of the decisions for your employees. However, they’ll still see all of the progress and error messages throughout the process.
-
- - **Completely silent installation**. Lets you make all of the decisions for your employees and hides all of the progress and error messages. Because this mode is completely silent, if the installation fails, your employees won’t know and they won’t be able to run the installation package again.
-
Both the hands-free and completely silent installation options will:
-
- - Answer prompts so Setup can continue.
-
- - Accept the license agreement.
-
- - Determine that Internet Explorer 11 is installed and not just downloaded.
-
- - Perform your specific installation type.
-
- - Install IE in the default location, unless it is already installed. In that case, the new version of the browser is installed in the same location as the previous version.
-
-2. Choose if your employee’s device will restart at the end of Setup.
-
- - **Default**. Prompts your employees to restart after installing IE.
-
- - **No restart**. Doesn’t restart the computer after installing IE. The employee will have to manually restart later.
-
- - **Force restart**. Automatically restarts the computer after installing IE.
-
-3. Click **Next** to go to the [Browser User Interface](browser-ui-ieak11-wizard.md) page or **Back** to go to the [Internal Install](internal-install-ieak11-wizard.md) page.
-
-
-
-
-
-
-
-
-
+---
+ms.localizationpriority: medium
+ms.mktglfcycl: deploy
+description: How to use the User Experience page in the IEAK 11 Customization Wizard to decide user interaction with the Setup process.
+author: dansimp
+ms.prod: ie11
+ms.assetid: d3378058-e4f0-4a11-a888-b550af994bfa
+ms.reviewer:
+audience: itpro
+manager: dansimp
+ms.author: dansimp
+title: Use the User Experience page in the IEAK 11 Wizard (Internet Explorer Administration Kit 11 for IT Pros)
+ms.sitesec: library
+ms.date: 07/27/2017
+---
+
+
+# Use the User Experience page in the IEAK 11 Wizard
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
+The **User Experience** page of the Internet Explorer Customization Wizard 11 lets you decide how much you want your employees to interact with the custom package’s Setup process.
+
+**Note** You’ll only see this page if you are running the **Internal** version of the Internet Explorer Customization Wizard 11.
The customizations you make on this page only apply to Internet Explorer for the desktop on Windows 7.
+
+**To use the User Experience page**
+
+1. Choose how your employee should interact with Setup, including:
+
+ - **Interactive installation**. Lets your employees change installation options while installing your custom package. This experience shows all of the progress and error messages throughout the process.
+
+ - **Hands-free installation**. Lets you make all of the decisions for your employees. However, they’ll still see all of the progress and error messages throughout the process.
+
+ - **Completely silent installation**. Lets you make all of the decisions for your employees and hides all of the progress and error messages. Because this mode is completely silent, if the installation fails, your employees won’t know and they won’t be able to run the installation package again.
+
Both the hands-free and completely silent installation options will:
+
+ - Answer prompts so Setup can continue.
+
+ - Accept the license agreement.
+
+ - Determine that Internet Explorer 11 is installed and not just downloaded.
+
+ - Perform your specific installation type.
+
+ - Install IE in the default location, unless it is already installed. In that case, the new version of the browser is installed in the same location as the previous version.
+
+2. Choose if your employee’s device will restart at the end of Setup.
+
+ - **Default**. Prompts your employees to restart after installing IE.
+
+ - **No restart**. Doesn’t restart the computer after installing IE. The employee will have to manually restart later.
+
+ - **Force restart**. Automatically restarts the computer after installing IE.
+
+3. Click **Next** to go to the [Browser User Interface](browser-ui-ieak11-wizard.md) page or **Back** to go to the [Internal Install](internal-install-ieak11-wizard.md) page.
+
+
+
+
+
+
+
+
+
diff --git a/browsers/internet-explorer/ie11-ieak/using-internet-settings-ins-files.md b/browsers/internet-explorer/ie11-ieak/using-internet-settings-ins-files.md
index 3efd12ffa8..c9bb888bed 100644
--- a/browsers/internet-explorer/ie11-ieak/using-internet-settings-ins-files.md
+++ b/browsers/internet-explorer/ie11-ieak/using-internet-settings-ins-files.md
@@ -1,37 +1,41 @@
----
-ms.localizationpriority: medium
-ms.mktglfcycl: deploy
-description: Info about how to use Internet Settings (.ins) files and the IEAK 11 to configure your custom browser package.
-author: dansimp
-ms.prod: ie11
-ms.assetid: a24a7cdb-681e-4f34-a53c-6d8383c5f977
-ms.reviewer:
-audience: itpro
manager: dansimp
-ms.author: dansimp
-title: Using Internet Settings (.INS) files with IEAK 11 (Internet Explorer Administration Kit 11 for IT Pros)
-ms.sitesec: library
-ms.date: 07/27/2017
----
-
-
-# Using Internet Settings (.INS) files with IEAK 11
-Use the Internet Settings (.ins) files and the Internet Explorer Administration Kit 11 (IEAK 11) to configure your custom browser and its components. You can create multiple versions of your custom package by customizing copies of this file.
-
-Here's a list of the available .INS file settings:
-
-|Setting |Description |
-|-----------------------------------------|------------------------------------------------------------------------------|
-|[Branding](branding-ins-file-setting.md) |Customize the branding and setup information in your browser package. |
-|[BrowserToolbars](browsertoolbars-ins-file-setting.md) |Customize the appearance of the IE toolbar. |
-|[CabSigning](cabsigning-ins-file-setting.md) |Digital signature information for your programs. |
-|[ConnectionSettings](connectionsettings-ins-file-setting.md) |Info about the networking connection settings used to install your custom package. |
-|[CustomBranding](custombranding-ins-file-setting.md) |URL location to your branding cabinet (.cab) file. |
-|[ExtRegInf](extreginf-ins-file-setting.md) |Names of your Setup information (.inf) files and the installation mode for components. |
-|[FavoritesEx](favoritesex-ins-file-setting.md) |Add a path to your icon file for **Favorites**, decide whether **Favorites** are available offline, and add URLs to each**Favorites** site. |
-|[HideCustom](hidecustom-ins-file-setting.md) |Whether to hide the globally unique identifier (GUID) for each custom component. |
-|[ISP_Security](isp-security-ins-file-setting.md) |The root certificate you’re adding to your custom package. |
-|[Media](media-ins-file-setting.md) |Types of media in which your custom installation package is available. |
-|[Proxy](proxy-ins-file-setting.md) |Whether to use a proxy server. |
-|[Security Imports](security-imports-ins-file-setting.md) |Whether to import security information for your custom package. |
-|[URL](url-ins-file-setting.md) |Whether to use an auto-configured proxy server. |
-
+---
+ms.localizationpriority: medium
+ms.mktglfcycl: deploy
+description: Info about how to use Internet Settings (.ins) files and the IEAK 11 to configure your custom browser package.
+author: dansimp
+ms.prod: ie11
+ms.assetid: a24a7cdb-681e-4f34-a53c-6d8383c5f977
+ms.reviewer:
+audience: itpro
+manager: dansimp
+ms.author: dansimp
+title: Using Internet Settings (.INS) files with IEAK 11 (Internet Explorer Administration Kit 11 for IT Pros)
+ms.sitesec: library
+ms.date: 07/27/2017
+---
+
+
+# Using Internet Settings (.INS) files with IEAK 11
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
+Use the Internet Settings (.ins) files and the Internet Explorer Administration Kit 11 (IEAK 11) to configure your custom browser and its components. You can create multiple versions of your custom package by customizing copies of this file.
+
+Here's a list of the available .INS file settings:
+
+|Setting |Description |
+|-----------------------------------------|------------------------------------------------------------------------------|
+|[Branding](branding-ins-file-setting.md) |Customize the branding and setup information in your browser package. |
+|[BrowserToolbars](browsertoolbars-ins-file-setting.md) |Customize the appearance of the IE toolbar. |
+|[CabSigning](cabsigning-ins-file-setting.md) |Digital signature information for your programs. |
+|[ConnectionSettings](connectionsettings-ins-file-setting.md) |Info about the networking connection settings used to install your custom package. |
+|[CustomBranding](custombranding-ins-file-setting.md) |URL location to your branding cabinet (.cab) file. |
+|[ExtRegInf](extreginf-ins-file-setting.md) |Names of your Setup information (.inf) files and the installation mode for components. |
+|[FavoritesEx](favoritesex-ins-file-setting.md) |Add a path to your icon file for **Favorites**, decide whether **Favorites** are available offline, and add URLs to each**Favorites** site. |
+|[HideCustom](hidecustom-ins-file-setting.md) |Whether to hide the globally unique identifier (GUID) for each custom component. |
+|[ISP_Security](isp-security-ins-file-setting.md) |The root certificate you’re adding to your custom package. |
+|[Media](media-ins-file-setting.md) |Types of media in which your custom installation package is available. |
+|[Proxy](proxy-ins-file-setting.md) |Whether to use a proxy server. |
+|[Security Imports](security-imports-ins-file-setting.md) |Whether to import security information for your custom package. |
+|[URL](url-ins-file-setting.md) |Whether to use an auto-configured proxy server. |
+
diff --git a/browsers/internet-explorer/ie11-ieak/what-ieak-can-do-for-you.md b/browsers/internet-explorer/ie11-ieak/what-ieak-can-do-for-you.md
index 06b86bce15..d62e11e507 100644
--- a/browsers/internet-explorer/ie11-ieak/what-ieak-can-do-for-you.md
+++ b/browsers/internet-explorer/ie11-ieak/what-ieak-can-do-for-you.md
@@ -1,68 +1,72 @@
----
-ms.localizationpriority: medium
-ms.mktglfcycl: support
-ms.pagetype: security
-description: Internet Explorer Administration Kit (IEAK) helps corporations, Internet service providers (ISPs), Internet content providers (ICPs), and independent software vendors (ISVs) to deploy and manage web-based solutions.
-author: dansimp
-ms.author: dansimp
-ms.manager: elizapo
-ms.prod: ie11
-ms.assetid:
-ms.reviewer:
-audience: itpro
manager: dansimp
-title: What IEAK can do for you
-ms.sitesec: library
-ms.date: 05/10/2018
----
-
-# What IEAK can do for you
-
-Internet Explorer Administration Kit (IEAK) helps corporations, Internet service providers (ISPs), Internet content providers (ICPs), and independent software vendors (ISVs) to deploy and manage web-based solutions.
-
-IEAK 10 and newer includes the ability to install using one of the following installation modes:
-
-- Internal
-
-- External
-
-## IEAK 11 users
-Internet Explorer Administration Kit (IEAK) helps corporations, Internet service providers (ISPs), Internet content providers (ICPs), and independent software vendors (ISVs) to deploy and manage web-based solutions.
-
-IEAK 10 and newer includes the ability to install using one of the following installation modes:
-- Internal
-- External
-
-> [!NOTE]
-> IEAK 11 works in network environments, with or without Microsoft Active Directory service.
-
-
-### Corporations
-IEAK helps corporate administrators establish version control, centrally distribute and manage browser installation, configure automatic connection profiles, and customize large portions of Internet Explorer, including features, security, communications settings, and other important functionality.
-
-Corporate administrators install IEAK using Internal mode (for Internet Explorer 10 or newer) or Corporate mode (for Internet Explorer 9 or older).
-
-### Internet service providers
-IEAK helps ISPs customize, deploy and distribute, add third-party add-ons, search providers, and custom components, as well as include web slices and accelerators all as part of a custom Internet Explorer installation package.
-
-ISPs install IEAK using External mode (for Internet Explorer 10 or newer) or Internet Service Provider (ISP) mode (for Internet Explorer 9 or older).
-
-### Internet content providers
-IEAK helps ICPs customize the appearance of Internet Explorer and its Setup program, including letting you add your company name or specific wording to the Title bar, set up a customer support webpage, set up the user home page and search providers, add links to the Favorites and the Explorer bars, add optional components, web slices and accelerators, and determine which compatibility mode Internet Explorer should use.
-
-ICPs install IEAK using External mode (for Internet Explorer 10 or newer) or Internet Content Provider (ICP) mode (for Internet Explorer 9 or older)
-
-### Independent software vendors
-IEAK helps ISVs distribute (and redistribute) a custom version of Internet Explorer that can include custom components, programs, and controls (like the web browser control) that you create for your users. ISVs can also determine home pages, search providers, and add websites to the Favorites bar.
-
-ISVs install IEAK using External mode (for Internet Explorer 10 or newer) or Internet Content Provider (ICP) mode (for Internet Explorer 9 or older).
-
-## Additional resources
-
-- [IEAK 11 - Frequently Asked Questions](../ie11-faq/faq-ieak11.md)
-- [Download IEAK 11](ieak-information-and-downloads.md)
-- [IEAK 11 overview](index.md)
-- [IEAK 11 administrators guide](https://docs.microsoft.com/internet-explorer/ie11-ieak/index)
-- [IEAK 11 licensing guidelines](licensing-version-and-features-ieak11.md)
-- [Internet Explorer 11 - FAQ for IT Pros](../ie11-faq/faq-for-it-pros-ie11.md)
-- [Internet Explorer 11 (IE11) - Deployment Guide for IT Pros](../ie11-deploy-guide/index.md)
-- [Microsoft Edge - Deployment Guide for IT Pros](https://go.microsoft.com/fwlink/p/?LinkId=760643)
+---
+ms.localizationpriority: medium
+ms.mktglfcycl: support
+ms.pagetype: security
+description: Internet Explorer Administration Kit (IEAK) helps corporations, Internet service providers (ISPs), Internet content providers (ICPs), and independent software vendors (ISVs) to deploy and manage web-based solutions.
+author: dansimp
+ms.author: dansimp
+ms.manager: elizapo
+ms.prod: ie11
+ms.assetid:
+ms.reviewer:
+audience: itpro
+manager: dansimp
+title: What IEAK can do for you
+ms.sitesec: library
+ms.date: 05/10/2018
+---
+
+# What IEAK can do for you
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
+
+Internet Explorer Administration Kit (IEAK) helps corporations, Internet service providers (ISPs), Internet content providers (ICPs), and independent software vendors (ISVs) to deploy and manage web-based solutions.
+
+IEAK 10 and newer includes the ability to install using one of the following installation modes:
+
+- Internal
+
+- External
+
+## IEAK 11 users
+Internet Explorer Administration Kit (IEAK) helps corporations, Internet service providers (ISPs), Internet content providers (ICPs), and independent software vendors (ISVs) to deploy and manage web-based solutions.
+
+IEAK 10 and newer includes the ability to install using one of the following installation modes:
+- Internal
+- External
+
+> [!NOTE]
+> IEAK 11 works in network environments, with or without Microsoft Active Directory service.
+
+
+### Corporations
+IEAK helps corporate administrators establish version control, centrally distribute and manage browser installation, configure automatic connection profiles, and customize large portions of Internet Explorer, including features, security, communications settings, and other important functionality.
+
+Corporate administrators install IEAK using Internal mode (for Internet Explorer 10 or newer) or Corporate mode (for Internet Explorer 9 or older).
+
+### Internet service providers
+IEAK helps ISPs customize, deploy and distribute, add third-party add-ons, search providers, and custom components, as well as include web slices and accelerators all as part of a custom Internet Explorer installation package.
+
+ISPs install IEAK using External mode (for Internet Explorer 10 or newer) or Internet Service Provider (ISP) mode (for Internet Explorer 9 or older).
+
+### Internet content providers
+IEAK helps ICPs customize the appearance of Internet Explorer and its Setup program, including letting you add your company name or specific wording to the Title bar, set up a customer support webpage, set up the user home page and search providers, add links to the Favorites and the Explorer bars, add optional components, web slices and accelerators, and determine which compatibility mode Internet Explorer should use.
+
+ICPs install IEAK using External mode (for Internet Explorer 10 or newer) or Internet Content Provider (ICP) mode (for Internet Explorer 9 or older)
+
+### Independent software vendors
+IEAK helps ISVs distribute (and redistribute) a custom version of Internet Explorer that can include custom components, programs, and controls (like the web browser control) that you create for your users. ISVs can also determine home pages, search providers, and add websites to the Favorites bar.
+
+ISVs install IEAK using External mode (for Internet Explorer 10 or newer) or Internet Content Provider (ICP) mode (for Internet Explorer 9 or older).
+
+## Additional resources
+
+- [IEAK 11 - Frequently Asked Questions](../ie11-faq/faq-ieak11.md)
+- [Download IEAK 11](ieak-information-and-downloads.md)
+- [IEAK 11 overview](index.md)
+- [IEAK 11 administrators guide](https://docs.microsoft.com/internet-explorer/ie11-ieak/index)
+- [IEAK 11 licensing guidelines](licensing-version-and-features-ieak11.md)
+- [Internet Explorer 11 - FAQ for IT Pros](../ie11-faq/faq-for-it-pros-ie11.md)
+- [Internet Explorer 11 (IE11) - Deployment Guide for IT Pros](../ie11-deploy-guide/index.md)
+- [Microsoft Edge - Deployment Guide for IT Pros](https://go.microsoft.com/fwlink/p/?LinkId=760643)
diff --git a/browsers/internet-explorer/ie11-ieak/wizard-complete-ieak11-wizard.md b/browsers/internet-explorer/ie11-ieak/wizard-complete-ieak11-wizard.md
index e81b0eedea..03de7ed423 100644
--- a/browsers/internet-explorer/ie11-ieak/wizard-complete-ieak11-wizard.md
+++ b/browsers/internet-explorer/ie11-ieak/wizard-complete-ieak11-wizard.md
@@ -1,31 +1,35 @@
----
-ms.localizationpriority: medium
-ms.mktglfcycl: deploy
-description: How to use the Wizard Complete - Next Steps page in the IEAK 11 Customization Wizard to build your custom Internet Explorer install package.
-author: dansimp
-ms.prod: ie11
-ms.assetid: aaaac88a-2022-4d0b-893c-b2404b45cabc
-ms.reviewer:
-audience: itpro
manager: dansimp
-ms.author: dansimp
-title: Use the Wizard Complete - Next Steps page in the IEAK 11 Wizard (Internet Explorer Administration Kit 11 for IT Pros)
-ms.sitesec: library
-ms.date: 07/27/2017
----
-
-
-# Use the Wizard Complete - Next Steps page in the IEAK 11 Wizard
-The **Wizard Complete – Next Steps** page of the Internet Explorer Customization Wizard 11 lets you build your custom installation package, after you click **Finish**.
-
-In most cases, your next steps will be to prepare your files for installation from your network or from another distribution method. If you haven’t already done it, you’ll need to digitally sign any program or .cab files that are going to be distributed over the Internet or over an intranet that isn’t configured to allow downloads.
-
-After that, the steps you’ll use to distribute your customized browser will vary, depending on your version of IEAK (Internal or External) and the media you’re using to distribute the package. For more information, see the [Internet Explorer 11 (IE11) - Deployment Guide for IT Pros](../ie11-deploy-guide/index.md).
-
-
-
-
-
-
-
-
-
+---
+ms.localizationpriority: medium
+ms.mktglfcycl: deploy
+description: How to use the Wizard Complete - Next Steps page in the IEAK 11 Customization Wizard to build your custom Internet Explorer install package.
+author: dansimp
+ms.prod: ie11
+ms.assetid: aaaac88a-2022-4d0b-893c-b2404b45cabc
+ms.reviewer:
+audience: itpro
+manager: dansimp
+ms.author: dansimp
+title: Use the Wizard Complete - Next Steps page in the IEAK 11 Wizard (Internet Explorer Administration Kit 11 for IT Pros)
+ms.sitesec: library
+ms.date: 07/27/2017
+---
+
+
+# Use the Wizard Complete - Next Steps page in the IEAK 11 Wizard
+
+[!INCLUDE [Microsoft 365 workloads end of support for IE11](../includes/microsoft-365-ie-end-of-support.md)]
+
+The **Wizard Complete – Next Steps** page of the Internet Explorer Customization Wizard 11 lets you build your custom installation package, after you click **Finish**.
+
+In most cases, your next steps will be to prepare your files for installation from your network or from another distribution method. If you haven’t already done it, you’ll need to digitally sign any program or .cab files that are going to be distributed over the Internet or over an intranet that isn’t configured to allow downloads.
+
+After that, the steps you’ll use to distribute your customized browser will vary, depending on your version of IEAK (Internal or External) and the media you’re using to distribute the package. For more information, see the [Internet Explorer 11 (IE11) - Deployment Guide for IT Pros](../ie11-deploy-guide/index.md).
+
+
+
+
+
+
+
+
+
diff --git a/browsers/internet-explorer/includes/microsoft-365-ie-end-of-support.md b/browsers/internet-explorer/includes/microsoft-365-ie-end-of-support.md
new file mode 100644
index 0000000000..96a04e5f70
--- /dev/null
+++ b/browsers/internet-explorer/includes/microsoft-365-ie-end-of-support.md
@@ -0,0 +1,13 @@
+---
+author: pamgreen-msft
+ms.author: pamgreen
+ms.date: 10/02/2018
+ms.reviewer:
+audience: itpro
+manager: pamgreen
+ms.prod: ie11
+ms.topic: include
+---
+
+> [!IMPORTANT]
+> Microsoft 365 apps and services will not support Internet Explorer 11 starting August 17, 2021 (Microsoft Teams will not support Internet Explorer 11 earlier, starting November 30, 2020). [Learn more](https://aka.ms/AA97tsw). Please note that Internet Explorer 11 will remain a supported browser. Internet Explorer 11 is a component of the Windows operating system and [follows the Lifecycle Policy](https://docs.microsoft.com/lifecycle/faq/internet-explorer-microsoft-edge) for the product on which it is installed.
\ No newline at end of file
diff --git a/browsers/internet-explorer/internet-explorer.yml b/browsers/internet-explorer/internet-explorer.yml
index 4c11b5c85e..7a2759960e 100644
--- a/browsers/internet-explorer/internet-explorer.yml
+++ b/browsers/internet-explorer/internet-explorer.yml
@@ -1,69 +1,174 @@
-### YamlMime:YamlDocument
+### YamlMime:Landing
-documentType: LandingData
-title: Internet Explorer 11
+title: Internet Explorer 11 documentation
+summary: Consistent, reliable web browsing on Windows 7, Windows 8.1, and Windows 10, with the security, performance, backward compatibility, and modern standards support that large organizations need.
metadata:
- document_id:
- title: Internet Explorer 11
- description: Consistent, reliable web browsing on Windows 7, Windows 8.1, and Windows 10, with the security, performance, backward compatibility, and modern standards support that large organizations need.
- keywords: Internet Explorer 11. IE11
- ms.localizationpriority: medium
- author: lizap
+ title: Internet Explorer 11 documentation
+ description: Consistent, reliable web browsing on Windows 7, Windows 8.1, and Windows 10, with the security, performance, backward compatibility, and modern standards support that large organizations need.
+ ms.topic: landing-page
+ author: lizap
ms.author: elizapo
- manager: dougkim
- ms.topic: article
- ms.devlang: na
+ ms.date: 07/06/2020
-sections:
-- items:
- - type: markdown
- text: "
- Consistent, reliable web browsing on Windows 7, Windows 8.1, and Windows 10, with the security, performance, backward compatibility, and modern standards support that large organizations need.
- "
-- title: Explore
-- items:
- - type: markdown
- text: "
- Find tools, step-by-step guides, updates, and other resources to help you get started.
-
- "
-- title: Plan
-- items:
- - type: markdown
- text: "
- Find information and tips to help you assess compatibility and prioritize processes as you plan for Internet Explorer 11.
-
- "
-- title: Deploy
-- items:
- - type: markdown
- text: "
- Find the resources you need to successfully deploy Internet Explorer 11 in your organization.
-
- "
-- title: Manage
-- items:
- - type: markdown
- text: "
- Find everything you need to manage Internet Explorer 11 effectively in your organization. Get information on Group Policy, blocked out-of-date ActiveX controls, scripts, and more.
-
- "
-- title: Support
-- items:
- - type: markdown
- text: "
- Get help from product specialists and community experts, and find solutions to commonly encountered issues.
-
**Sign up for the Windows IT Pro Insider** Get the latest tools, tips, and expert guidance on deployment, management, security, and more. Learn more
**Microsoft Edge Dev blog** Keep up with the latest browser trends, security tips, and news for IT professionals. Read the blog
**Microsoft Edge Dev on Twitter** Get the latest news and updates from the Microsoft Web Platform team. Visit Twitter
-
- "
+# linkListType: architecture | concept | deploy | download | get-started | how-to-guide | learn | overview | quickstart | reference | sample | tutorial | video | whats-new
+
+landingContent:
+# Cards and links should be based on top customer tasks or top subjects
+# Start card title with a verb
+ # Card
+ - title: Explore
+ linkLists:
+ - linkListType: get-started
+ links:
+ - text: IE11 features and tools
+ url: /internet-explorer/ie11-deploy-guide/updated-features-and-tools-with-ie11
+ - text: System requirements and language support
+ url: /internet-explorer/ie11-deploy-guide/system-requirements-and-language-support-for-ie11
+ - text: Frequently asked questions
+ url: /internet-explorer/ie11-faq/faq-for-it-pros-ie11
+ - text: Internet Explorer 11 deployment guide
+ url: /internet-explorer/ie11-deploy-guide/
+ - text: Use Enterprise Mode to improve compatibility
+ url: /microsoft-edge/deploy/emie-to-improve-compatibility
+ - text: Lifecycle FAQ - Internet Explorer
+ url: https://support.microsoft.com/help/17454/lifecycle-faq-internet-explorer
+ - linkListType: download
+ links:
+ - text: Download IE11 with Windows 10
+ url: https://www.microsoft.com/evalcenter/evaluate-windows-10-enterprise
+ - text: Enterprise Mode Site List Manager (schema, v.2)
+ url: https://www.microsoft.com/download/details.aspx?id=49974
+ - text: Cumulative security updates for Internet Explorer 11
+ url: https://www.catalog.update.microsoft.com/Search.aspx?q=cumulative%20security%20update%20for%20internet%20explorer%2011
+ - linkListType: learn
+ links:
+ - text: Getting started with Windows 10 for IT professionals
+ url: https://mva.microsoft.com/training-courses/getting-started-with-windows-10-for-it-professionals-10629?l=fCowqpy8_5905094681
+ - text: 'Windows 10: Top Features for IT Pros'
+ url: https://mva.microsoft.com/training-courses/windows-10-top-features-for-it-pros-16319?l=xBnT2ihhC_7306218965
+ - text: Manage and modernize Internet Explorer with Enterprise Mode
+ url: https://channel9.msdn.com/events/teched/newzealand/2014/pcit307
+ - text: 'Virtual Lab: Enterprise Mode'
+ url: https://www.microsoft.com/handsonlabs/SelfPacedLabs/?storyGuid=e4155067-2c7e-4b46-8496-eca38bedca02
+
+ # Card
+ - title: Plan
+ linkLists:
+ - linkListType: get-started
+ links:
+ - text: What is Enterprise Mode?
+ url: /internet-explorer/ie11-deploy-guide/what-is-enterprise-mode
+ - text: Tips and tricks to manage Internet Explorer compatibility
+ url: /internet-explorer/ie11-deploy-guide/tips-and-tricks-to-manage-ie-compatibility
+ - text: Download the Enterprise Site Discovery Toolkit
+ url: https://www.microsoft.com/download/details.aspx?id=44570
+ - text: Collect data using Enterprise Site Discovery
+ url: /internet-explorer/ie11-deploy-guide/collect-data-using-enterprise-site-discovery
+ - text: Manage Windows upgrades with Upgrade Readiness
+ url: /windows/deployment/upgrade/manage-windows-upgrades-with-upgrade-readiness
+ - text: 'Demo: Plan and manage Windows 10 upgrades and feature updates with'
+ url: https://techcommunity.microsoft.com/t5/Microsoft-Ignite-Content-2017/Windows-Analytics-Plan-and-manage-Windows-10-upgrades-and/td-p/98639
+ - linkListType: how-to-guide
+ links:
+ - text: Turn on Enterprise Mode and use a site list
+ url: /internet-explorer/ie11-deploy-guide/turn-on-enterprise-mode-and-use-a-site-list
+ - text: Add sites to the Enterprise Mode site list
+ url: /internet-explorer/ie11-deploy-guide/add-multiple-sites-to-enterprise-mode-site-list-using-the-version-2-schema-and-enterprise-mode-tool
+ - text: Edit the Enterprise Mode site list
+ url: /internet-explorer/ie11-deploy-guide/edit-the-enterprise-mode-site-list-using-the-enterprise-mode-site-list-manager
+ - text: Turn on local control and logging for Enterprise Mode
+ url: /internet-explorer/ie11-deploy-guide/turn-on-local-control-and-logging-for-enterprise-mode
+
+ # Card
+ - title: Deploy
+ linkLists:
+ - linkListType: get-started
+ links:
+ - text: IEAK 11 user's guide
+ url: /internet-explorer/ie11-ieak/
+ - text: Download IEAK 11
+ url: /internet-explorer/ie11-ieak/ieak-information-and-downloads
+ - text: Frequently asked questions about IEAK 11
+ url: /internet-explorer/ie11-faq/faq-ieak11
+ - text: Customization and distribution guidelines
+ url: /internet-explorer/ie11-ieak/licensing-version-and-features-ieak11#customization-guidelines
+ - linkListType: deploy
+ links:
+ - text: Install Internet Explorer 11 through automatic updates (recommended)
+ url: /internet-explorer/ie11-deploy-guide/ie11-delivery-through-automatic-updates
+ - text: Install Internet Explorer 11 as part of an operating system deployment
+ url: /internet-explorer/ie11-deploy-guide/install-ie11-using-operating-system-deployment-systems
+ - text: Install Internet Explorer 11 over the network
+ url: /internet-explorer/ie11-deploy-guide/install-ie11-using-the-network
+ - text: Install Internet Explorer 11 with System Center 2012 R2 Configuration Manager
+ url: /internet-explorer/ie11-deploy-guide/install-ie11-using-system-center-configuration-manager
+ - text: Install Internet Explorer 11 with Windows Server Update Services (WSUS)
+ url: /internet-explorer/ie11-deploy-guide/install-ie11-using-windows-server-update-services-wsus
+ - text: Install Internet Explorer 11 with Microsoft Intune
+ url: /internet-explorer/ie11-deploy-guide/install-ie11-using-microsoft-intune
+ - text: Install Internet Explorer 11 with third-party tools
+ url: /internet-explorer/ie11-deploy-guide/install-ie11-using-third-party-tools
+
+ # Card
+ - title: Manage
+ linkLists:
+ - linkListType: tutorial
+ links:
+ - text: Group Policy for beginners
+ url: /previous-versions/windows/it-pro/windows-7/hh147307(v=ws.10)
+ - text: New Group Policy settings for IE11
+ url: /internet-explorer/ie11-deploy-guide/new-group-policy-settings-for-ie11
+ - text: Administrative templates for IE11
+ url: https://www.microsoft.com/download/details.aspx?id=40905
+ - text: Group Policy preferences for IE11
+ url: /internet-explorer/ie11-deploy-guide/group-policy-preferences-and-ie11
+ - text: Configure Group Policy preferences
+ url: https://support.microsoft.com/help/2898604/how-to-configure-group-policy-preference-settings-for-internet-explorer-11-in-windows-8.1-or-windows-server-2012-r2
+ - text: Blocked out-of-date ActiveX controls
+ url: /internet-explorer/ie11-deploy-guide/blocked-out-of-date-activex-controls
+ - text: Out-of-date ActiveX control blocking
+ url: /internet-explorer/ie11-deploy-guide/out-of-date-activex-control-blocking
+ - text: Update to block out-of-date ActiveX controls in Internet Explorer
+ url: https://support.microsoft.com/help/2991000/update-to-block-out-of-date-activex-controls-in-internet-explorer
+ - text: Script to join user to AD with automatic Local user Profile Migration
+ url: https://gallery.technet.microsoft.com/scriptcenter/script-to-join-active-7b16d9d3
+ - text: Scripts for IT professionals
+ url: https://gallery.technet.microsoft.com/scriptcenter/site/search?query=Microsoft%20Edge%20or%20Internet
+
+ # Card
+ - title: Support
+ linkLists:
+ - linkListType: get-started
+ links:
+ - text: Change or reset Internet Explorer settings
+ url: https://support.microsoft.com/help/17441/windows-internet-explorer-change-reset-settings
+ - text: Troubleshoot problems with setup, installation, auto configuration, and more
+ url: /internet-explorer/ie11-deploy-guide/troubleshoot-ie11
+ - text: Disable VBScript execution in Internet Explorer for Internet Zone and Restricted Sites Zone
+ url: https://support.microsoft.com/help/4012494/option-to-disable-vbscript-execution-in-internet-explorer-for-internet
+ - text: Frequently asked questions about IEAK 11
+ url: /internet-explorer/ie11-faq/faq-ieak11
+ - text: Internet Explorer 8, 9, 10, 11 forum
+ url: https://social.technet.microsoft.com/forums/ie/home?forum=ieitprocurrentver
+ - text: Contact a Microsoft support professional
+ url: https://support.microsoft.com/contactus
+ - text: Support options for Microsoft Partners
+ url: https://mspartner.microsoft.com/Pages/Support/get-support.aspx
+ - text: Microsoft Services Premier Support
+ url: https://www.microsoft.com/en-us/microsoftservices/support.aspx
+ - text: Microsoft Small Business Support Center
+ url: https://smallbusiness.support.microsoft.com/product/internet-explorer
+ - text: General support
+ url: https://support.microsoft.com/products/internet-explorer
+
+ # Card
+ - title: Stay informed
+ linkLists:
+ - linkListType: get-started
+ links:
+ - text: Sign up for the Windows IT Pro Insider
+ url: https://aka.ms/windows-it-pro-insider
+ - text: Microsoft Edge Dev blog
+ url: https://blogs.windows.com/msedgedev
+ - text: Microsoft Edge Dev on Twitter
+ url: https://twitter.com/MSEdgeDev
diff --git a/browsers/internet-explorer/kb-support/clear-ie-cache-from-command-line.md b/browsers/internet-explorer/kb-support/clear-ie-cache-from-command-line.md
deleted file mode 100644
index 7adcb24c17..0000000000
--- a/browsers/internet-explorer/kb-support/clear-ie-cache-from-command-line.md
+++ /dev/null
@@ -1,123 +0,0 @@
----
-title: Clear the Internet Explorer cache from a command line
-description: Introduces command-line commands and a sample batch file for clearing the IE cache.
-audience: ITPro
-manager: msmets
-author: ramakoni1
-ms.author: ramakoni
-ms.reviewer: ramakoni, DEV_Triage
-ms.prod: internet-explorer
-ms.technology:
-ms.topic: kb-support
-ms.custom: CI=111026
-ms.localizationpriority: Normal
-# localization_priority: medium
-# ms.translationtype: MT
-ms.date: 01/23/2020
----
-# How to clear Internet Explorer cache by using the command line
-
-This article outlines the procedure to clear the Internet Explorer cache by using the command line.
-
-## Command line commands to clear browser cache
-
-1. Delete history from the Low folder
- `del /s /q C:\Users\\%username%\AppData\Local\Microsoft\Windows\History\low\* /ah`
-
-2. Delete history
- `RunDll32.exe InetCpl.cpl, ClearMyTracksByProcess 1`
-
-3. Delete cookies
- `RunDll32.exe InetCpl.cpl,ClearMyTracksByProcess 2`
-
-4. Delete temporary internet files
- `RunDll32.exe InetCpl.cpl,ClearMyTracksByProcess 8`
-
-5. Delete form data
- `RunDll32.exe InetCpl.cpl,ClearMyTracksByProcess 16`
-
-6. Delete stored passwords
- `RunDll32.exe InetCpl.cpl,ClearMyTracksByProcess 32`
-
-7. Delete all
- `RunDll32.exe InetCpl.cpl,ClearMyTracksByProcess 255`
-
-8. Delete files and settings stored by add-ons
- `InetCpl.cpl,ClearMyTracksByProcess 4351`
-
-If you upgraded from a previous version of Internet Explorer, you have to use the following commands to delete the files from older versions:
-`RunDll32.exe InetCpl.cpl,ClearMyTracksByProcess 9`
-
-Command to reset Internet Explorer settings:
-`Rundll32.exe inetcpl.cpl ResetIEtoDefaults`
-
-## Sample batch file to clear Internet Explorer cache files
-
-A sample batch file is available that you can use to clear Internet Explorer cache files and other items. You can download the file from [https://msdnshared.blob.core.windows.net/media/2017/09/ClearIE_Cache.zip](https://msdnshared.blob.core.windows.net/media/2017/09/ClearIE_Cache.zip).
-
-The batch file offers the following options:
-
-- Delete Non-trusted web History (low-level hidden cleanup)
-- Delete History
-- Delete Cookies
-- Delete Temporary Internet Files
-- Delete Form Data
-- Delete Stored Passwords
-- Delete All
-- Delete All "Also delete files and settings stored by add-ons"
-- Delete IE10 and IE9 Temporary Internet Files
-- Resets IE Settings
-- EXIT
-
-**Contents of the batch file**
-
-```dos
-@echo off
-# This sample script is not supported under any Microsoft standard support program or service.
-# The sample script is provided AS IS without warranty of any kind. Microsoft further disclaims
-# all implied warranties including, without limitation, any implied warranties of merchantability
-# or of fitness for a particular purpose. The entire risk arising out of the use or performance of
-# the sample scripts and documentation remains with you. In no event shall Microsoft, its authors,
-# or anyone else involved in the creation, production, or delivery of the scripts be liable for any
-# damages whatsoever (including, without limitation, damages for loss of business profits, business
-# interruption, loss of business information, or other pecuniary loss) arising out of the use of or
-# inability to use the sample scripts or documentation, even if Microsoft has been advised of the
-# possibility of such damages
-
-:home
-cls
-COLOR 00
-echo Delete IE History
-echo Please select the task you wish to run.
-echo Pick one:
-echo.
-echo 1. Delete History
-echo 2. Delete Cookies
-echo 3. Delete Temporary Internet Files
-echo 4. Delete Form Data
-echo 5. Delete Stored Passwords
-echo 6. Delete All
-echo 7. Delete All "Also delete files and settings stored by add-ons"
-echo 8. Delete IE10 and 9 Temporary Internet Files
-echo 9. Reset IE Settings
-echo 00. EXIT
-:choice
-Echo Hit a number [1-10] and press enter.
-set /P CH=[1-10]
-
-if "%CH%"=="1" set x=RunDll32.exe InetCpl.cpl,ClearMyTracksByProcess 1
-if "%CH%"=="2" set x=RunDll32.exe InetCpl.cpl,ClearMyTracksByProcess 2
-if "%CH%"=="3" set x=RunDll32.exe InetCpl.cpl,ClearMyTracksByProcess 8
-if "%CH%"=="4" set x=RunDll32.exe InetCpl.cpl,ClearMyTracksByProcess 16
-if "%CH%"=="5" set x=RunDll32.exe InetCpl.cpl,ClearMyTracksByProcess 32
-if "%CH%"=="6" set x=RunDll32.exe InetCpl.cpl,ClearMyTracksByProcess 255
-if "%CH%"=="7" set x=RunDll32.exe InetCpl.cpl,ClearMyTracksByProcess 4351
-if "%CH%"=="8" set x=RunDll32.exe InetCpl.cpl,ClearMyTracksByProcess 9
-if "%CH%"=="9" set x=rundll32.exe inetcpl.cpl ResetIEtoDefaults
-if "%CH%"=="00" goto quit
-
-%x%
-
-goto Home
-:quit
-```
diff --git a/browsers/internet-explorer/kb-support/ie-edge-faqs.md b/browsers/internet-explorer/kb-support/ie-edge-faqs.md
index ef07a2a337..5c29be5126 100644
--- a/browsers/internet-explorer/kb-support/ie-edge-faqs.md
+++ b/browsers/internet-explorer/kb-support/ie-edge-faqs.md
@@ -1,6 +1,6 @@
---
title: IE and Microsoft Edge FAQ for IT Pros
-description: Describes frequently asked questions about Internet Explorer and Microsoft Edge for IT professionals.
+description: Describes frequently asked questions about Internet Explorer and Microsoft Edge for IT professionals.
audience: ITPro
manager: msmets
author: ramakoni1
@@ -10,9 +10,7 @@ ms.prod: internet-explorer
ms.technology:
ms.topic: kb-support
ms.custom: CI=111020
-ms.localizationpriority: Normal
-# localization_priority: medium
-# ms.translationtype: MT
+ms.localizationpriority: medium
ms.date: 01/23/2020
---
# Internet Explorer and Microsoft Edge frequently asked questions (FAQ) for IT Pros
diff --git a/devices/hololens/TOC.md b/devices/hololens/TOC.md
deleted file mode 100644
index 330bc3286e..0000000000
--- a/devices/hololens/TOC.md
+++ /dev/null
@@ -1,75 +0,0 @@
-# [Microsoft HoloLens](index.md)
-
-# Get started with HoloLens 2
-## [HoloLens 2 hardware](hololens2-hardware.md)
-## [Get your HoloLens 2 ready to use](hololens2-setup.md)
-## [Set up your HoloLens 2](hololens2-start.md)
-## [HoloLens 2 fit and comfort FAQ](hololens2-fit-comfort-faq.md)
-## [Frequently asked questions about cleaning HoloLens 2 devices](hololens2-maintenance.md)
-## [Supported languages for HoloLens 2](hololens2-language-support.md)
-## [Getting around HoloLens 2](hololens2-basic-usage.md)
-
-# Get started with HoloLens (1st gen)
-## [HoloLens (1st gen) hardware](hololens1-hardware.md)
-## [Get your HoloLens (1st gen) ready to use](hololens1-setup.md)
-## [Set up your HoloLens (1st gen)](hololens1-start.md)
-## [HoloLens (1st gen) fit and comfort FAQ](hololens1-fit-comfort-faq.md)
-## [Install localized version of HoloLens (1st gen)](hololens1-install-localized.md)
-## [Getting around HoloLens (1st gen)](hololens1-basic-usage.md)
-
-# Deploy HoloLens and mixed-reality apps in commercial environments
-## [Commercial features](hololens-commercial-features.md)
-## [Deploy HoloLens in a commercial environment](hololens-requirements.md)
-## [Determine what licenses you need](hololens-licenses-requirements.md)
-## [Configure your network for HoloLens](hololens-commercial-infrastructure.md)
-## [Unlock Windows Holographic for Business features](hololens1-upgrade-enterprise.md)
-## [Use a provisioning package to configure HoloLens](hololens-provisioning.md)
-## [Enroll HoloLens in MDM](hololens-enroll-mdm.md)
-## [Manage HoloLens updates](hololens-updates.md)
-## [Enable Bitlocker device encryption for HoloLens](hololens-encryption.md)
-
-# Navigating Windows Holographic
-## [Start menu and mixed reality home](holographic-home.md)
-## [Use your voice with HoloLens](hololens-cortana.md)
-## [Find, open, and save files](holographic-data.md)
-## [Create mixed reality photos and videos](holographic-photos-and-videos.md)
-
-# User management and access management
-## [Manage user identity and sign-in for HoloLens](hololens-identity.md)
-## [Share your HoloLens with multiple people](hololens-multiple-users.md)
-## [Set up HoloLens as a kiosk for specific applications](hololens-kiosk.md)
-
-# Holographic applications
-## [Use 3D Viewer on HoloLens](holographic-3d-viewer-beta.md)
-## [Find, install, and uninstall applications](holographic-store-apps.md)
-## [Manage custom apps for HoloLens](holographic-custom-apps.md)
-
-# Accessories and connectivity
-## [Connect to Bluetooth and USB-C devices](hololens-connect-devices.md)
-## [Use the HoloLens (1st gen) clicker](hololens1-clicker.md)
-## [Connect to a network](hololens-network.md)
-## [Manage connection endpoints for HoloLens](hololens-offline.md)
-
-# Hologram optics and placement in space
-## [Improve visual quality and comfort](hololens-calibration.md)
-## [Environment considerations for HoloLens](hololens-environment-considerations.md)
-## [Map physical spaces with HoloLens](hololens-spaces.md)
-
-# Update, troubleshoot, or recover HoloLens
-## [Update HoloLens](hololens-update-hololens.md)
-## [Restart, reset, or recover HoloLens](hololens-recovery.md)
-## [Troubleshoot HoloLens issues](hololens-troubleshooting.md)
-## [Collect diagnostic information from HoloLens devices](hololens-diagnostic-logs.md)
-## [Known issues for HoloLens](hololens-known-issues.md)
-## [Frequently asked questions](hololens-faq.md)
-## [Frequently asked security questions](hololens-faq-security.md)
-## [Status of the HoloLens services](hololens-status.md)
-## [Get support](https://support.microsoft.com/supportforbusiness/productselection?sapid=3ec35c62-022f-466b-3a1e-dbbb7b9a55fb)
-
-# Resources
-## [Windows Autopilot for HoloLens 2 evaluation guide](hololens2-autopilot.md)
-
-# [HoloLens release notes](hololens-release-notes.md)
-# [Give us feedback](hololens-feedback.md)
-# [Insider preview for Microsoft HoloLens](hololens-insider.md)
-# [Change history for Microsoft HoloLens documentation](change-history-hololens.md)
diff --git a/devices/hololens/breadcrumb/toc.yml b/devices/hololens/breadcrumb/toc.yml
deleted file mode 100644
index 2ac60b3585..0000000000
--- a/devices/hololens/breadcrumb/toc.yml
+++ /dev/null
@@ -1,7 +0,0 @@
-- name: Docs
- tocHref: /
- topicHref: /
- items:
- - name: Hololens
- tocHref: /hololens
- topicHref: /hololens/index
\ No newline at end of file
diff --git a/devices/hololens/change-history-hololens.md b/devices/hololens/change-history-hololens.md
deleted file mode 100644
index 9a1b48b3eb..0000000000
--- a/devices/hololens/change-history-hololens.md
+++ /dev/null
@@ -1,88 +0,0 @@
----
-title: Change history for Microsoft HoloLens documentation
-ms.reviewer:
-manager: laurawi
-description: This topic lists new and updated topics for HoloLens.
-keywords: change history
-ms.prod: hololens
-ms.mktglfcycl: manage
-ms.sitesec: library
-author: dansimp
-ms.author: dansimp
-ms.topic: article
-ms.localizationpriority: medium
----
-
-# Change history for Microsoft HoloLens documentation
-
-This topic lists new and updated topics in the [Microsoft HoloLens documentation](index.md).
-
-## April 2019
-
-New or changed topic | Description
---- | ---
-[Restore HoloLens 2 using Advanced Recovery Companion](hololens-recovery.md) | New
-
-## November 2018
-
-New or changed topic | Description
---- | ---
-[How HoloLens stores data for spaces](hololens-spaces.md) | New
-
-## Windows 10 Holographic for Business, version 1809
-
-The topics in this library have been updated for Windows 10 Holographic for Business, version 1809.
-
-
-## October 2018
-
-New or changed topic | Description
---- | ---
-[Preview new mixed reality apps for HoloLens](hololens-public-preview-apps.md) | Removed, and redirected to [Mixed reality apps](https://docs.microsoft.com/dynamics365/#pivot=mixed-reality-apps)
-[Microsoft Remote Assist app](hololens-microsoft-remote-assist-app.md) | Removed, and redirected to [Overview of Dynamics 365 Remote Assist](https://docs.microsoft.com/dynamics365/mixed-reality/remote-assist/)
-[Microsoft Dynamics 365 Layout app](hololens-microsoft-dynamics-365-layout-app.md) | Removed, and redirected to [Overview of Dynamics 365 Layout](https://docs.microsoft.com/dynamics365/mixed-reality/layout/)
-[Insider preview for Microsoft HoloLens](hololens-insider.md) | Added instructions for opting out of Insider builds.
-
-
-## July 2018
-
-New or changed topic | Description
---- | ---
-Insider preview for Microsoft HoloLens | New (topic retired on release of Windows 10, version 1809)
-
-
-## May 2018
-
-New or changed topic | Description
---- | ---
-[Preview new mixed reality apps for HoloLens](hololens-public-preview-apps.md) | New
-[Microsoft Remote Assist app](hololens-microsoft-remote-assist-app.md) | New
-[Microsoft Layout app](hololens-microsoft-layout-app.md) | New
-[Set up HoloLens in kiosk mode](hololens-kiosk.md) | Added instructions for setting up a guest account for kiosk mode.
-
-## Windows 10 Holographic for Business, version 1803
-
-The topics in this library have been updated for Windows 10 Holographic for Business, version 1803. The following new topics have been added:
-
-- [What's new in Microsoft HoloLens](hololens-whats-new.md)
-- [Manage updates to HoloLens](hololens-updates.md)
-- [Share HoloLens with multiple people](hololens-multiple-users.md)
-
-
-## February 2018
-
-New or changed topic | Description
---- | ---
-[Unlock Windows Holographic for Business features](hololens1-upgrade-enterprise.md) | Replaced the instructions for upgrading to Windows Holographic for Business using Microsoft Intune with a link to the new Intune topic.
-
-## December 2017
-
-New or changed topic | Description
---- | ---
-[Enable Bitlocker device encryption for HoloLens](hololens-encryption.md) | New
-
-## January 2017
-
-| New or changed topic | Description |
-| --- | --- |
-| All topics | Changed all references from **Windows Holographic Enterprise** to **Windows Holographic for Business** |
diff --git a/devices/hololens/docfx.json b/devices/hololens/docfx.json
index 4f53494c32..6d55b1a859 100644
--- a/devices/hololens/docfx.json
+++ b/devices/hololens/docfx.json
@@ -45,12 +45,19 @@
"folder_relative_path_in_docset": "./"
}
- }
+ },
+ "contributors_to_exclude": [
+ "rjagiewich",
+ "traya1",
+ "rmca14",
+ "claydetels19",
+ "jborsecnik",
+ "tiburd",
+ "garycentric"
+ ],
},
"fileMetadata": {},
- "template": [
- null
- ],
+ "template": [],
"dest": "devices/hololens",
"markdownEngineName": "markdig"
},
diff --git a/devices/hololens/holographic-3d-viewer-beta.md b/devices/hololens/holographic-3d-viewer-beta.md
deleted file mode 100644
index 90c5b236fd..0000000000
--- a/devices/hololens/holographic-3d-viewer-beta.md
+++ /dev/null
@@ -1,205 +0,0 @@
----
-title: Using 3D Viewer Beta on HoloLens
-description: Describes the types of files and features that 3D Viewer Beta on HoloLens (1st gen) supports, and how to use and troubleshoot the app.
-ms.prod: hololens
-ms.sitesec: library
-author: Teresa-Motiv
-ms.author: v-tea
-ms.topic: article
-ms.localizationpriority: high
-ms.date: 10/30/2019
-ms.reviewer: scooley
-audience: ITPro
-manager: jarrettr
-appliesto:
-- HoloLens (1st gen)
----
-
-# Using 3D Viewer Beta on HoloLens
-
-3D Viewer Beta lets you view 3D models on HoloLens (1st gen). You can open and view *supported* .fbx files from Microsoft Edge, OneDrive, and other apps.
-
->[!NOTE]
->This article applies to the immersive Unity **3D Viewer Beta** app, which supports .fbx files and is only available on HoloLens (1st gen). The pre-installed **3D Viewer** app on HoloLens 2 supports opening custom .glb 3D models in the mixed reality home (see [Asset requirements overview](https://docs.microsoft.com/windows/mixed-reality/creating-3d-models-for-use-in-the-windows-mixed-reality-home#asset-requirements-overview) for more details.
-
-If you're having trouble opening a 3D model in 3D Viewer Beta, or certain features of your 3D model are unsupported, see [Supported content specifications](#supported-content-specifications).
-
-To build or optimize 3D models for use with 3D Viewer Beta, see [Optimizing 3D models for 3D Viewer Beta](#optimizing-3d-models-for-3d-viewer-beta).
-
-There are two ways to open a 3D model on HoloLens. See [Viewing FBX files on HoloLens](#viewing-fbx-files-on-hololens) to learn more.
-
-If you're having trouble after reading these topics, see [Troubleshooting](#troubleshooting).
-
-## Supported content specifications
-
-### File format
-
-- FBX format
-- Maximum FBX release 2015.1.0
-
-### File size
-
-- Minimum 5 KB
-- Maximum 500 MB
-
-### Geometry
-
-- Polygonal models only. No subdivision surfaces or NURBs
-- Right-handed coordinate system
-- Shear in transformation matrices is not supported
-
-### Textures
-
-- Texture maps must be embedded in the FBX file
-- Supported image formats
- - JPEG and PNG images
- - BMP images (24-bit RGB true-color)
- - TGA images (24-bit RGB and 32-bit RGBQ true-color)
-- Maximum texture resolution of 2048x2048
-- Maximum of one diffuse map, one normal map, and one reflection cube map per mesh
-- Alpha channel in diffuse textures causes pixels to be discarded if below 50%
-
-### Animation
-
-- Scale/rotation/translation animation on individual objects
-- Skeletal (rigged) animation with skinning
- - Maximum of 4 influences per vertex
-
-### Materials
-
-- Lambert and Phong materials are supported, with adjustable parameters
-- Supported material properties for Lambert
- - Main Texture (RGB + Alpha Test)
- - Diffuse Color (RGB)
- - Ambient Color (RGB)
-- Supported material properties for Phong
- - Main Texture (RGB + Alpha Test)
- - Diffuse Color (RGB)
- - Ambient Color (RGB)
- - Specular Color (RGB)
- - Shininess
- - Reflectivity
-- Custom materials are not supported
-- Maximum of one material per mesh
-- Maximum of one material layer
-- Maximum of 8 materials per file
-
-### File and model limitations
-
-There are hard limits on the size of files, as well as the number of models, vertices, and meshes that can be open simultaneously in 3D Viewer Beta:
-
-- 500 MB maximum file size per model
-- Vertices: 600,000 combined on all open models
-- Meshes: 1,600 combined on all open models
-- Maximum of 40 models open at one time
-
-## Optimizing 3D models for 3D Viewer Beta
-
-### Special considerations
-
-- Avoid black materials or black areas in texture maps. Holograms are made of light, thus HoloLens renders black (the absence of light) as transparent.
-- Before exporting to FBX from your creation tool, ensure all geometry is visible and unlocked and no layers that contain geometry are turned off or templated. Visibility is not respected.
-- Avoid very large translation offsets between nodes (for example, 100,000 units). This can cause the model to jitter while being moved/scaled/rotated.
-
-### Performance optimization
-
-Keep performance in mind while authoring content and validate in the 3D Viewer Beta app on HoloLens during the authoring process for best results. 3D Viewer Beta renders content real-time and performance is subject to HoloLens hardware capabilities.
-
-There are many variables in a 3D model that can impact performance. 3D Viewer Beta will show a warning on load if there are more than 150,000 vertices or more than 400 meshes. Animations can have an impact on the performance of other open models. There are also hard limits on the total number models, vertices, and meshes that can be open simultaneously in 3D Viewer Beta (see [File and model limitations](#file-and-model-limitations)).
-
-If the 3D model isn't running well due to model complexity, consider:
-
-- Reducing polygon count
-- Reducing number of bones in rigged animation
-- Avoiding self-occlusion
-
-Double-sided rendering is supported in 3D Viewer Beta, although it is turned off by default for performance reasons. This can be turned on via the **Double Sided** button on the **Details** page. For best performance, avoid the need for double-sided rendering in your content.
-
-### Validating your 3D model
-
-Validate your model by opening it in 3D Viewer Beta on HoloLens. Select the **Details** button to view your model's characteristics and warnings of unsupported content (if present).
-
-### Rendering 3D models with true-to-life dimensions
-
-By default, 3D Viewer Beta displays 3D models at a comfortable size and position relative to the user. However, if rendering a 3D model with true-to-life measurements is important (for example, when evaluating furniture models in a room), the content creator can set a flag within the file's metadata to prevent resizing of that model by both the application and the user.
-
-To prevent scaling of the model, add a Boolean custom attribute to any object in the scene named Microsoft_DisableScale and set it to true. 3D Viewer Beta will then respect the FbxSystemUnit information baked into the FBX file. Scale in 3D Viewer Beta is 1 meter per FBX unit.
-
-## Viewing FBX files on HoloLens
-
-### Open an FBX file from Microsoft Edge
-
-FBX files can be opened directly from a website using Microsoft Edge on HoloLens.
-
-1. In Microsoft Edge, navigate to the webpage containing the FBX file you want to view.
-1. Select the file to download it.
-1. When the download is complete, select the **Open** button in Microsoft Edge to open the file in 3D Viewer Beta.
-
-The downloaded file can be accessed and opened again later by using Downloads in Microsoft Edge. To save a 3D model and ensure continued access, download the file on your PC and save it to your OneDrive account. The file can then be opened from the OneDrive app on HoloLens.
-
-> [!NOTE]
-> Some websites with downloadable FBX models provide them in compressed ZIP format. 3D Viewer Beta cannot open ZIP files directly. Instead, use your PC to extract the FBX file and save it to your OneDrive account. The file can then be opened from the OneDrive app on HoloLens.
-
-### Open an FBX file from OneDrive
-
-FBX files can be opened from OneDrive by using the OneDrive app on HoloLens. Be sure you've installed OneDrive using Microsoft Store app on HoloLens and that you've already uploaded the FBX file to OneDrive on your PC.
-
-Once in OneDrive, FBX files can be opened on HoloLens using 3D Viewer Beta in one of two ways:
-
-- Launch OneDrive on HoloLens and select the FBX file to open it in 3D Viewer Beta.
-- Launch 3D Viewer Beta, air tap to show the toolbar, and select **Open File**. OneDrive will launch, allowing you to select an FBX file.
-
-## Troubleshooting
-
-### I see a warning when I open a 3D model
-
-You will see a warning if you attempt to open a 3D model that contains features that are not supported by 3D Viewer Beta, or if the model is too complex and performance may be affected. 3D Viewer Beta will still load the 3D model, but performance or visual fidelity may be compromised.
-
-For more info, see [Supported content specifications](#supported-content-specifications) and [Optimizing 3D models for 3D Viewer Beta](#optimizing-3d-models-for-3d-viewer-beta).
-
-### I see a warning and the 3D model doesn't load
-
-You will see an error message when 3D Viewer Beta cannot load a 3D model due to complexity or file size, or if the FBX file is corrupt or invalid. You will also see an error message if you have reached the limit on the total number of models, vertices, or meshes that can be open simultaneously.
-
-For more info, see [Supported content specifications](#supported-content-specifications) and [File and model limitations](#file-and-model-limitations).
-
-If you feel your model meets the supported content specifications and has not exceeded the file or model limitations, you may send your FBX file to the 3D Viewer Beta team at holoapps@microsoft.com. We are not able to respond personally, but having examples of files that do not load properly will help our team improve on future versions of the app.
-
-### My 3D model loads, but does not appear as expected
-
-If your 3D model does not look as expected in 3D Viewer Beta, air tap to show the toolbar, then select **Details**. Aspects of the file which are not supported by 3D Viewer Beta will be highlighted as warnings.
-
-The most common issue you might see is missing textures, likely because they are not embedded in the FBX file. In this case, the model will appear white. This issue can be addressed in the creation process by exporting from your creation tool to FBX with the embed textures option selected.
-
-For more info, see [Supported content specifications](#supported-content-specifications) and [Optimizing 3D models for 3D Viewer Beta](#optimizing-3d-models-for-3d-viewer-beta).
-
-### I experience performance drops while viewing my 3D model
-
-Performance when loading and viewing a 3D model can be affected by the complexity of the model, number of models open simultaneously, or number of models with active animations.
-
-For more info, see [Optimizing 3D models for 3D Viewer Beta](#optimizing-3d-models-for-3d-viewer-beta) and [File and model limitations](#file-and-model-limitations).
-
-### When I open an FBX file on HoloLens, it doesn't open in 3D Viewer Beta
-
-3D Viewer Beta is automatically associated with the .fbx file extension when it is installed.
-
-If you try to open an FBX file and see a dialog box that directs you to Microsoft Store, you do not currently have an app associated with the .fbx file extension on HoloLens.
-
-Verify that 3D Viewer Beta is installed. If it is not installed, download it from Microsoft Store on HoloLens.
-
-If 3D Viewer Beta is already installed, launch 3D Viewer Beta, then try opening the file again. If the issue persists, uninstall and reinstall 3D Viewer Beta. This will re-associate the .fbx file extension with 3D Viewer Beta.
-
-If attempting to open an FBX file opens an app other than 3D Viewer Beta, that app was likely installed after 3D Viewer Beta and has taken over association with the .fbx file extension. If you prefer 3D Viewer Beta to be associated with the .fbx file extension, uninstall and reinstall 3D Viewer Beta.
-
-### The Open File button in 3D Viewer Beta doesn't launch an app
-
-The **Open File** button will open the app associated with the file picker function on HoloLens. If OneDrive is installed, the **Open File** button should launch OneDrive. However, if there is currently no app associated with the file picker function installed on HoloLens, you will be directed to Microsoft Store.
-
-If the **Open File** button launches an app other than OneDrive, that app was likely installed after OneDrive and has taken over association with the file picker function. If you prefer OneDrive to launch when selecting the **Open File** button in 3D Viewer Beta, uninstall and reinstall OneDrive.
-
-If the **Open File** button is not active, it's possible that you have reached the limit of models that can be open in 3D Viewer Beta at one time. If you have 40 models open in 3D Viewer Beta, you will need to close some before you will be able to open additional models.
-
-## Additional resources
-
-- [Support forums](http://forums.hololens.com/categories/3d-viewer-beta)
-- [Third-party notices](https://www.microsoft.com/{lang-locale}/legal/products)
diff --git a/devices/hololens/holographic-custom-apps.md b/devices/hololens/holographic-custom-apps.md
deleted file mode 100644
index 3cc01691d6..0000000000
--- a/devices/hololens/holographic-custom-apps.md
+++ /dev/null
@@ -1,57 +0,0 @@
----
-title: Manage custom apps for HoloLens
-description: Side load custom apps on HoloLens. Learn more about installing, and uninstalling holographic apps.
-ms.assetid: 6bd124c4-731c-4bcc-86c7-23f9b67ff616
-ms.date: 07/01/2019
-manager: v-miegge
-keywords: hololens, sideload, side load, side-load, store, uwp, app, install
-ms.prod: hololens
-ms.sitesec: library
-author: mattzmsft
-ms.author: mazeller
-ms.topic: article
-ms.localizationpriority: medium
-ms.custom:
-- CI 111456
-- CSSTroubleshooting
-appliesto:
-- HoloLens (1st gen)
-- HoloLens 2
----
-
-# Manage custom apps for HoloLens
-
-HoloLens supports many existing applications from the Microsoft Store, as well as new apps built specifically for HoloLens. This article focuses on custom holographic applications.
-
-For more information about store apps, see [Manage apps with the store](holographic-store-apps.md).
-
-## Install custom apps
-
-You can install your own applications on HoloLens either by using the Device Portal or by deploying the apps from Visual Studio.
-
-### Installing an application package with the Device Portal
-
-1. Establish a connection from [Device Portal](https://docs.microsoft.com/windows/mixed-reality/using-the-windows-device-portal) to the target HoloLens.
-1. In the left navigation, navigate to the **Apps** page .
-1. Under **App Package** browse to the .appx file that is associated with your application.
- > [!IMPORTANT]
- > Make sure to reference any associated dependency and certificate files.
-
-1. Select **Go**.
- 
-
-### Deploying from Microsoft Visual Studio 2015
-
-1. Open your app's Visual Studio solution (.sln file).
-1. Open the project's **Properties**.
-1. Select the following build configuration: **Master/x86/Remote Machine**.
-1. When you select **Remote Machine**:
- - Make sure the address points to the Wi-Fi IP address of your HoloLens.
- - Set authentication to **Universal (Unencrypted Protocol)**.
-1. Build your solution.
-1. To deploy the app from your development PC to your HoloLens, select **Remote Machine**. If you already have an existing build on the HoloLens, select **Yes** to install this newer version.
-
- 
-1. The application will install and auto launch on your HoloLens.
-
-After you've installed an app, you'll find it in the **All apps** list (**Start** > **All apps**).
diff --git a/devices/hololens/holographic-data.md b/devices/hololens/holographic-data.md
deleted file mode 100644
index 1f28c4fac9..0000000000
--- a/devices/hololens/holographic-data.md
+++ /dev/null
@@ -1,100 +0,0 @@
----
-title: Find and save files on HoloLens
-description: Use File Explorer on HoloLens to view and manage files on your device
-keywords: how-to, file picker, files, photos, videos, pictures, OneDrive, storage, file explorer
-ms.assetid: 77d2e357-f65f-43c8-b62f-6cd9bf37070a
-author: mattzmsft
-ms.author: mazeller
-manager: v-miegge
-ms.reviewer: jarrettrenshaw
-ms.date: 12/30/2019
-keywords: hololens
-ms.prod: hololens
-ms.sitesec: library
-ms.topic: article
-audience: ITPro
-ms.localizationpriority: medium
-appliesto:
-- HoloLens (1st gen)
-- HoloLens 2
----
-
-# Find, open, and save files on HoloLens
-
-Files you create on HoloLens, including photos and videos, are saved directly to your HoloLens device. View and manage them in the same way you would manage files on Windows 10:
-
-- Using the File Explorer app to access local folders.
-- Within an app's storage.
-- In a special folder (such as the video or music library).
-- Using a storage service that includes an app and file picker (such as OneDrive).
-- Using a desktop PC connected to your HoloLens by using a USB cable, using MTP (Media Transfer Protocol) support.
-
-## View files on HoloLens using File Explorer
-
-> Applies to all HoloLens 2 devices and HoloLens (1st gen) as of the [Windows 10 April 2018 Update (RS4) for HoloLens](https://docs.microsoft.com/windows/mixed-reality/release-notes-april-2018).
-
-Use File Explorer on HoloLens to view and manage files on your device, including 3D objects, documents, and pictures. Go to **Start** > **All apps** > **File Explorer** to get started.
-
-> [!TIP]
-> If there are no files listed in File Explorer, select **This Device** in the top left pane.
-
-If you don’t see any files in File Explorer, the "Recent" filter may be active (clock icon is highlighted in left pane). To fix this, select the **This Device** document icon in the left pane (beneath the clock icon), or open the menu and select **This Device**.
-
-## Find and view your photos and videos
-
-[Mixed reality capture](holographic-photos-and-videos.md) lets you take mixed reality photos and videos on HoloLens. These photos and videos are saved to the device's Camera Roll folder.
-
-You can access photos and videos taken with HoloLens by:
-
-- accessing the Camera Roll directly through the [Photos app](holographic-photos-and-videos.md).
-- uploading photos and videos to cloud storage by syncing your photos and videos to OneDrive.
-- using the Mixed Reality Capture page of the [Windows Device Portal](https://docs.microsoft.com/windows/mixed-reality/using-the-windows-device-portal#mixed-reality-capture).
-
-### Photos app
-
-The Photos app is one of the default apps on the **Start** menu, and comes built-in with HoloLens. Learn more about [using the Photos app to view content](holographic-photos-and-videos.md).
-
-You can also install the [OneDrive app](https://www.microsoft.com/p/onedrive/9wzdncrfj1p3) from the Microsoft Store to sync photos to other devices.
-
-### OneDrive app
-
-[OneDrive](https://onedrive.live.com/) lets you access, manage, and share your photos and videos with any device and with any user. To access the photos and videos captured on HoloLens, download the [OneDrive app](https://www.microsoft.com/p/onedrive/9wzdncrfj1p3) from the Microsoft Store on your HoloLens. Once downloaded, open the OneDrive app and select **Settings** > **Camera upload**, and turn on **Camera upload**.
-
-### Connect to a PC
-
-If your HoloLens is running the [Windows 10 April 2018 update](https://docs.microsoft.com/windows/mixed-reality/release-notes-april-2018) or later, you can connect your HoloLens to a Windows 10 PC by using a USB cable to browse photos and videos on the device by using MTP (media transfer protocol). You'll need to make sure the device is unlocked to browse files if you have a PIN or password set up on your device.
-
-If you have enabled the [Windows Device Portal](https://docs.microsoft.com/windows/mixed-reality/using-the-windows-device-portal), you can use it to browse, retrieve, and manage the photos and videos stored on your device.
-
-## Access files within an app
-
-If an application saves files on your device, you can use that application to access them.
-
-### Requesting files from another app
-
-An application can request to save a file or open a file from another app by using [file pickers](https://docs.microsoft.com/windows/mixed-reality/app-model#file-pickers).
-
-### Known folders
-
-HoloLens supports a number of [known folders](https://docs.microsoft.com/windows/mixed-reality/app-model#known-folders) that apps can request permission to access.
-
-## View HoloLens files on your PC
-
-Similar to other mobile devices, connect HoloLens to your desktop PC using MTP (Media Transfer Protocol) and open File Explorer on the PC to access your HoloLens libraries for easy transfer.
-
-To see your HoloLens files in File Explorer on your PC:
-
-1. Sign in to HoloLens, then plug it into the PC using the USB cable that came with the HoloLens.
-
-1. Select **Open Device to view files with File Explorer**, or open File Explorer on the PC and navigate to the device.
-
-To see info about your HoloLens, right-click the device name in File Explorer on your PC, then select **Properties**.
-
-> [!NOTE]
-> HoloLens (1st gen) does not support connecting to external hard drives or SD cards.
-
-## Sync to the cloud
-
-To sync photos and other files from your HoloLens to the cloud, install and set up OneDrive on HoloLens. To get OneDrive, search for it in the Microsoft Store on your HoloLens.
-
-HoloLens doesn't back up app files and data, so it's a good idea to save your important stuff to OneDrive. That way, if you reset your device or uninstall an app, your info will be backed up.
diff --git a/devices/hololens/holographic-home.md b/devices/hololens/holographic-home.md
deleted file mode 100644
index 9b554c0638..0000000000
--- a/devices/hololens/holographic-home.md
+++ /dev/null
@@ -1,87 +0,0 @@
----
-title: Start menu and mixed reality home
-description: Navigate the mixed reality home in Windows Holographic.
-ms.assetid: 742bc126-7996-4f3a-abb2-cf345dff730c
-ms.date: 08/07/2019
-keywords: hololens
-ms.prod: hololens
-ms.sitesec: library
-author: scooley
-ms.author: scooley
-ms.topic: article
-ms.localizationpriority: high
-appliesto:
-- HoloLens (1st gen)
-- HoloLens 2
----
-
-# Start menu and mixed reality home
-
-Just like the Windows PC experience starts with the desktop, Windows Holographic starts with mixed reality home. Using the Start menu you can open and place app windows, immersive app launchers, and 3D content in mixed reality home, and their placement in your physical space will be remembered.
-
-## Use the Start menu
-
-The Start menu on HoloLens is where you'll open apps, see important status info, and access tools like the camera.
-
-Wherever you are in HoloLens, you can always open the Start menu by using **Start gesture**. On HoloLens (1st gen) the Start gesture is [bloom](https://support.microsoft.com/help/12644/hololens-use-gestures). On HoloLens 2, the [Start gesture](hololens2-basic-usage.md#start-gesture) is to tap the Start icon that appears on your wrist. You can also open the Start menu using your voice by saying "Go to Start".
-
-> [!TIP]
-> When the Start menu is open, use the Start gesture to close it, or look at the Start menu and say "Close".
-
-At the top of the Start menu, you'll see status indicators for Wi-Fi, battery, volume, and a clock. On HoloLens 2 there is also a listening indicator that shows whether the device is speech enabled and is listening for voice commands. At the bottom you'll find the **Photo** and **Video** buttons which allow you to take photos and video recordings. There is also a **Connect** button that allows you to project what you see to another device using Miracast.
-
-### Find apps on Start menu
-
-The Start menu has a **Pinned apps** list and an **All apps** list.
-
-- The **Pinned apps** list shows apps that have been pinned. You can add and remove apps from the **Pinned apps** list using the context menu that appears when you **select and hold** on an app tile.
-
-- The **All apps** list shows all apps that are installed on the device. Select the **All apps** button on the right side of the **Start** menu to get to the list.
-
-On both app lists, use the **Page up** and **Page down** buttons on the right side of the Start menu to page through all the apps in the list. Both app lists will automatically open to the page that was last used during a device session.
-
-> [!TIP]
-> On HoloLens 2, you can directly scroll the app lists using your index finger. Just touch the list with your finger tip and drag upwards or downwards.
-
-### Open apps from Start menu
-
-To open an app from the Start menu, simply **select** an **app tile**. You can also say the name of an app to open it.
-
-When you open an app from the Start menu, one of the following will happen, depending on how the app is designed:
-
-- An **app window** is placed. The app is then loaded in the window and you can use it like a touch screen.
-- A **3D app launcher** for an immersive app is placed. You need to then **select** the launcher to open the immersive app.
-- An app window is placed which acts as a **launcher** for an immersive app. The immersive app will proceed to launch automatically.
-
-App windows and app launchers placed in mixed reality home will stay around until you decide to remove them. They give you a convenient shortcut in the world to use those app windows or to launch immersive apps without having to open them again from the Start menu.
-
-> [!NOTE]
->Like on a phone, system resources is managed automatically on HoloLens. For example, when you open a new immersive app, all other running apps will immediately become inactive. There is no need to remove app windows and launchers in mixed reality home to free up system resources.
-
-## Using apps on HoloLens
-
-Apps on HoloLens can use app window view or immersive view. With app window view the app simply shows its content inside a window. With immersive view an app takes you away from mixed realty home where it can then display its content in the physical environment all around you. Apps can also choose to use both views.
-
-### Use app windows
-
-On HoloLens (1st gen) app windows are placed and used in mixed reality home, where you can [move, resize, and rotate](hololens1-basic-usage.md#move-resize-and-rotate-apps) them as you like. In addition to using app windows with gaze and gesture, you can also use them with Bluetooth connected mouse and keyboard.
-
-On HoloLens 2, in addition to using app windows in mixed reality home, you can also use one app window at a time inside an immersive app. You can also put an app window into **Follow me** mode where it will stay in front of you as you walk around. When you open an app window while inside an immersive app, it will open in **Follow me** mode automatically. You can [move, resize, and rotate](hololens2-basic-usage.md#move-resize-and-rotate-holograms) app windows directly using your hands in both mixed reality home and inside an immersive app.
-
-> [!NOTE]
->
-> - Up to three app windows can be active in mixed reality home at a time. You can open more, but only three will remain active.
-> - When an app window is not active, it will show content that looks darkened compared to an active window. Some will simply show the app icon instead of any content. To activate an inactive window simply **select** it.
-> - Each open app can have one active window at a time, except Microsoft Edge, which can have up to three.
-
-### Close apps
-
-To close an app that uses an app window, simply close the app window with the **Close** button on the title bar. You can also look at the window and say "Close".
-
-To exit an app that uses immersive view, use the Start gesture to bring up the **Start menu**, then select the **Mixed reality home** button.
-
-If an immersive app is in a broken state and you need to restart it, you can make sure the app is first completely shut down by closing its launcher in mixed reality home, then launching it from the Start menu.
-
-## Related info
-
-[Find, Install, and Uninstall applications from the Microsoft Store](holographic-store-apps.md)
diff --git a/devices/hololens/holographic-photos-and-videos.md b/devices/hololens/holographic-photos-and-videos.md
deleted file mode 100644
index 10e6bb4756..0000000000
--- a/devices/hololens/holographic-photos-and-videos.md
+++ /dev/null
@@ -1,150 +0,0 @@
----
-title: Capture and manage mixed reality photos and videos
-description: Learn how to capture, view, and share mixed reality photos and videos, using HoloLens.
-keywords: hololens, photo, video, capture, mrc, mixed reality capture, photos, camera, stream, livestream, demo
-ms.assetid: 1b636ec3-6186-4fbb-81b2-71155aef0593
-ms.prod: hololens
-ms.sitesec: library
-author: mattzmsft
-ms.author: mazeller
-ms.topic: article
-audience: ITPro
-ms.localizationpriority: medium
-ms.date: 10/28/2019
-manager: jarrettr
-appliesto:
-- HoloLens (1st gen)
-- HoloLens 2
----
-
-# Create mixed reality photos and videos
-
-HoloLens gives users the experience of mixing the real world with the digital world. Mixed reality capture (MRC) lets you capture that experience as a photo or video, or share what you see with others in real-time.
-
-Mixed reality capture uses a first-person point of view so other people can see holograms as you see them. For a third-person point of view, use [spectator view](https://docs.microsoft.com/windows/mixed-reality/spectator-view). Spectator view is especially useful for demos.
-
-While it's fun to share videos amongst friends and colleagues, videos can also help teach other people to use an app or to communicate problems with apps and experiences.
-
-> [!NOTE]
-> If you can't launch mixed reality capture experiences and your HoloLens is a work device, check with your system administrator. Access to the camera can be restricted through company policy.
-
-## Capture a mixed reality photo
-
-There are several ways to take a photo of mixed reality on HoloLens; you can use hardware buttons, voice, or the Start menu.
-
-### Hardware buttons to take photos
-
-To take a quick photo of your current view, press the volume up and volume down buttons at the same time. This is a bit like the HoloLens version of a screenshot or print screen.
-
-- [Button locations on HoloLens 2](hololens2-hardware.md)
-- [Button locations on HoloLens (1st gen)](hololens1-hardware.md#hololens-components)
-
-> [!NOTE]
-> Holding the **volume up** and **volume down** buttons for three seconds will start recording a video rather than taking a photo. To stop recording, tap both **volume up** and **volume down** buttons simultaneously.
-
-### Voice commands to take photos
-
-Cortana can also take a picture. Say: "Hey Cortana, take a picture."
-
-### Start menu to take photos
-
-Use the Start gesture to go to **Start**, then select the **camera** icon.
-
-Point your head in the direction of what you want to capture, then [air tap](hololens2-basic-usage.md#touch-holograms-near-you) to take a photo. You can continue to air tap and capture additional photos. Any photos you capture will be saved to your device.
-
-Use the Start gesture again to end photo capture.
-
-## Capture a mixed reality video
-
-There are several ways to record a video of mixed reality on HoloLens; you can use hardware buttons, voice, or the Start menu.
-
-### Hardware buttons to record videos
-
-The quickest way to record a video is to press and hold the **volume up** and **volume down** buttons simultaneously until a three-second countdown begins. To stop recording, tap both buttons simultaneously.
-
-> [!NOTE]
-> Quickly pressing the **volume up** and **volume down** buttons at the same time will take a photo rather than recording a video.
-
-### Voice to record videos
-
-Cortana can also record a video. Say: "Hey Cortana, start recording." To stop a video, say "Hey Cortana, stop recording."
-
-### Start menu to record videos
-
-Use the Start gesture to go to **Start**, then select the **video** icon. Point your head in the direction of what you want to capture, then [air tap](hololens2-basic-usage.md#touch-holograms-near-you) to start recording. There will be a three second countdown and your recording will begin.
-
-To stop recording, use the Start gesture and select the highlighted **video** icon. The video will be saved to your device.
-
-> [!NOTE]
-> **Applies to HoloLens (1st gen) only**
-> The [Windows 10 October 2018 Update](https://docs.microsoft.com/windows/mixed-reality/release-notes-october-2018) changes how the Start gesture and Windows button behave on HoloLens (1st gen). Before the update, the Start gesture or Windows button would stop a video recording. After the update, however, the Start gesture or Windows button opens the **Start** menu (or the **quick actions menu** if you are in an immersive app), from which you can select the highlighted **video** icon to stop recording.
-
-## Share what you see in real-time
-
-You can share what you see in HoloLens with friends and colleagues in real-time. There are a few methods available:
-
-1. Connecting to a Miracast-enabled device or adapter to watch on a TV.
-1. Using [Windows Device Portal](https://docs.microsoft.com/windows/mixed-reality/using-the-windows-device-portal) to watch on a PC
-1. Using the [Microsoft HoloLens companion app](https://www.microsoft.com/store/productId/9NBLGGH4QWNX) to watch on a PC.
-1. Deploying the [Microsoft Dynamics 365 Remote Assist](https://dynamics.microsoft.com/en-us/mixed-reality/remote-assist) app, which enables front-line workers to stream what they see to a remote expert. The remote expert can then guide the front-line worker verbally or by annotating in their world.
-
-> [!NOTE]
-> Sharing what you see via Windows Device Portal or Microsoft HoloLens companion app requires your HoloLens to be in [Developer mode](https://docs.microsoft.com/windows/mixed-reality/using-the-windows-device-portal#setting-up-hololens-to-use-windows-device-portal).
-
-### Stream video with Miracast
-
-Use the Start gesture to go to **Start**, then select the **connect** icon. From the picker that appears, select the Miracast-enabled device or adapter to which you want to connect.
-
-To stop sharing, use the Start gesture and select the highlighted **connect** icon. Because you were streaming, nothing will be saved to your device.
-
-> [!NOTE]
-> Miracast support was enabled on HoloLens (1st gen) beginning with the [Windows 10 October 2018 Update](https://docs.microsoft.com/windows/mixed-reality/release-notes-october-2018).
-
-### Real time video with Windows Device Portal
-
-Because sharing via Windows Device Portal requires Developer mode to be enabled on HoloLens, follow the instructions in our developer documentation to [set up Developer mode and navigate Windows Device Portal](https://docs.microsoft.com/windows/mixed-reality/using-the-windows-device-portal).
-
-### Microsoft HoloLens companion app
-
-Because sharing via the Microsoft HoloLens companion app requires Developer mode to be enabled on HoloLens, follow the instructions in our developer documentation to [set up Developer mode](https://docs.microsoft.com/windows/mixed-reality/using-the-windows-device-portal). Then, download the [Microsoft HoloLens companion app](https://www.microsoft.com/store/productId/9NBLGGH4QWNX) and follow the instructions within the app to connect to your HoloLens.
-
-Once the app is set up with your HoloLens, select the **Live stream** option from the app's main menu.
-
-## View your mixed reality photos and videos
-
-Mixed reality photos and videos are saved to the device's "Camera Roll". You can browse the contents of this folder on your HoloLens with the File Explorer app (navigate to Pictures > Camera Roll).
-
-You can also view your mixed reality photos and videos in the Photos app, which is pre-installed on HoloLens. To pin a photo in your world, select it in the Photos app and choose **Place in mixed world**. You can move the photo around your world after it's been placed.
-
-To view and/or save your mixed reality photos and videos on a PC connected to HoloLens, you can use [Windows Device Portal](https://docs.microsoft.com/windows/mixed-reality/using-the-windows-device-portal#mixed-reality-capture) or your [PC's File Explorer via MTP](https://docs.microsoft.com/windows/mixed-reality/release-notes-april-2018#new-features-for-hololens).
-
-## Share your mixed reality photos and videos
-
-After capturing a mixed reality photo or video, a preview will appear. Select the **share** icon above the preview to bring up the share assistant. From there, you can select the end point to which you'd like to share that photo or video.
-
-You can also share mixed reality photos and videos from OneDrive, by automatically uploading your mixed reality photos and videos. Open the OneDrive app on HoloLens and sign in with a personal [Microsoft account](https://account.microsoft.com) if you haven't already. Select the **settings** icon and choose **Camera upload**. Turn Camera upload on. Your mixed reality photos and videos will now be uploaded to OneDrive each time you launch the app on HoloLens.
-
-> [!NOTE]
-> You can only enable camera upload in OneDrive if you’re signed into OneDrive with a personal Microsoft account. If you set up HoloLens with a work or school account, you can add a personal Microsoft account in the OneDrive app to enable this feature.
-
-## Limitations of mixed reality capture
-
-- While using mixed reality capture, the framerate of HoloLens will be halved to 30 Hz.
-- Videos have a maximum length of five minutes.
-- The resolution of photos and videos may be reduced if the photo/video camera is already in use by another application, while live streaming, or when system resources are low.
-
-## Default file format and resolution
-
-### Default photo format and resolution
-
-| Device | Format | Extension | Resolution |
-|----------|----------|----------|----------|
-| HoloLens 2 | [JPEG](https://en.wikipedia.org/wiki/JPEG) | .jpg | 3904x2196px |
-| HoloLens (1st gen) | [JPEG](https://en.wikipedia.org/wiki/JPEG) | .jpg | 1408x792px |
-
-### Recorded video format and resolution
-
-| Device | Format | Extension | Resolution | Speed | Audio |
-|----------|----------|----------|----------|----------|----------|
-| HoloLens 2 | [MPEG-4](https://en.wikipedia.org/wiki/MPEG-4) | .mp4 | 1920x1080px | 30fps | 48kHz Stereo |
-| HoloLens (1st gen) | [MPEG-4](https://en.wikipedia.org/wiki/MPEG-4) | .mp4 | 1216x684px | 24fps | 48kHz Stereo |
diff --git a/devices/hololens/holographic-store-apps.md b/devices/hololens/holographic-store-apps.md
deleted file mode 100644
index 085f14c50e..0000000000
--- a/devices/hololens/holographic-store-apps.md
+++ /dev/null
@@ -1,53 +0,0 @@
----
-title: Find, install, and uninstall applications
-description: The Microsoft Store is your source for apps and games that work with HoloLens. Learn more about finding, installing, and uninstalling holographic apps.
-ms.assetid: cbe9aa3a-884f-4a92-bf54-8d4917bc3435
-ms.reviewer: v-miegge
-ms.date: 08/30/2019
-manager: jarrettr
-keywords: hololens, store, uwp, app, install
-ms.prod: hololens
-ms.sitesec: library
-author: mattzmsft
-ms.author: mazeller
-ms.topic: article
-ms.localizationpriority: high
-appliesto:
-- HoloLens (1st gen)
-- HoloLens 2
----
-
-# Find, install, and uninstall applications from the Microsoft Store
-
-The Microsoft Store is your go-to source for apps and games that work with HoloLens. When you go to the Store on your HoloLens, any apps you see there will run on it.
-
-Apps on HoloLens use either 2D view or holographic view. Apps that use 2D view look like windows and can be positioned all around you. Apps that use holographic view surround you and become the only app you see.
-
-HoloLens supports many existing applications from the Microsoft Store, as well as new apps built specifically for HoloLens. This article focuses on holographic applications from the Microsoft Store.
-
-To learn more about installing and running custom apps, read [Custom holographic applications](holographic-custom-apps.md).
-
-## Find apps
-
-Open the Microsoft Store from the **Start** menu. Then browse for apps and games. You can use Cortana to search by saying "Hey, Cortana" and then saying your search terms.
-
-## Install apps
-
-To download apps, you'll need to be signed in with a Microsoft account. To buy them, you'll need a payment method associated with the Microsoft account you use on your HoloLens. To set up a payment method, go to [account.microsoft.com](https://account.microsoft.com/) and select **Payment & billing** > **Payment options** > **Add a payment option**.
-
-1. To open the [**Start** menu](holographic-home.md), perform a [bloom](hololens1-basic-usage.md) gesture or tap your wrist.
-2. Select the Store app and then tap to place this tile into your world.
-3. Once the Store app opens, use the search bar to look for any desired application.
-4. Select **Get** or **Install** on the application's page (a purchase may be required).
-
-## Uninstall apps
-
-There are two ways to uninstall applications. You can uninstall applications through the Microsoft Store or Start menu.
-
-### Uninstall from the Start menu
-
-On the **Start** menu or in the **All apps** list, gaze at the app. Tap and hold until the menu appears, then select **Uninstall**.
-
-### Uninstall from the Microsoft Store
-
-Open the Microsoft Store from the **Start** menu, and then browse for the application you'd like to uninstall. On the Store page, each application that you have installed has an **Uninstall** button.
diff --git a/devices/hololens/hololens-FAQ.md b/devices/hololens/hololens-FAQ.md
deleted file mode 100644
index 38964c7a7d..0000000000
--- a/devices/hololens/hololens-FAQ.md
+++ /dev/null
@@ -1,293 +0,0 @@
----
-title: Frequently asked questions about HoloLens devices and holograms
-description: Do you have a quick question about HoloLens or interacting with holograms? This article provides a quick answer and more resources.
-keywords: hololens, faq, known issue, help
-ms.prod: hololens
-ms.sitesec: library
-author: Teresa-Motiv
-ms.author: v-tea
-ms.topic: article
-audience: ITPro
-ms.localizationpriority: medium
-ms.date: 02/27/2020
-ms.reviewer:
-ms.custom:
-- CI 114606
-- CSSTroubleshooting
-manager: jarrettr
-appliesto:
-- HoloLens (1st gen)
-- HoloLens 2
----
-
-# Frequently asked questions about HoloLens devices and holograms
-
-This article answers some questions that you may have about how to use HoloLens, including how to place holograms, work with spaces, and more.
-
-Any time that you have problems, make sure that HoloLens is [charged up](https://support.microsoft.com/help/12627/hololens-charge-your-hololens). Try [restarting it](hololens-restart-recover.md) to see whether that fixes things. And please use the Feedback app to send us information about the issue. You'll find the Feedback app on the [**Start** menu](holographic-home.md).
-
-For tips about hwo to wear your HoloLens, see [HoloLens (1st gen) fit and comfort frequently asked questions](hololens1-fit-comfort-faq.md).
-
-This article addresses the following questions and issues:
-
-
-- [My holograms don't look right or are moving around](#my-holograms-dont-look-right-or-are-moving-around)
-- [I see a message that says "Finding your space"](#i-see-a-message-that-says-finding-your-space)
-- [I'm not seeing the holograms that I expect to see in my space](#im-not-seeing-the-holograms-that-i-expect-to-see-in-my-space)
-- [I can't place holograms where I want to](#i-cant-place-holograms-where-i-want-to)
-- [Holograms disappear or are encased in other holograms or objects](#holograms-disappear-or-are-encased-in-other-holograms-or-objects)
-- [I can see holograms that are on the other side of a wall](#i-can-see-holograms-that-are-on-the-other-side-of-a-wall)
-- [When I place a hologram on a wall, the hologram seems to float](#when-i-place-a-hologram-on-a-wall-the-hologram-seems-to-float)
-- [Apps appear too close to me when I'm trying to move them](#apps-appear-too-close-to-me-when-im-trying-to-move-them)
-- [I'm getting a low disk space error](#im-getting-a-low-disk-space-error)
-- [HoloLens doesn't respond to my gestures](#hololens-doesnt-respond-to-my-gestures)
-- [HoloLens doesn't respond to my voice](#hololens-doesnt-respond-to-my-voice)
-- [I'm having problems pairing or using a Bluetooth device](#im-having-problems-pairing-or-using-a-bluetooth-device)
-- [HoloLens Settings lists devices as available, but the devices don't work](#hololens-settings-lists-devices-as-available-but-the-devices-dont-work)
-- [I'm having problems using the HoloLens clicker](#im-having-problems-using-the-hololens-clicker)
-- [I can't connect to Wi-Fi](#i-cant-connect-to-wi-fi)
-- [My HoloLens isn't running well, is unresponsive, or won't start](#my-hololens-isnt-running-well-is-unresponsive-or-wont-start)
-- [I can't sign in to a HoloLens device because it was previously set up for someone else](#i-cant-sign-in-to-a-hololens-device-because-it-was-previously-set-up-for-someone-else)
-- [Questions about managing HoloLens devices](#questions-about-managing-hololens-devices)
-- [Questions about securing HoloLens devices](#questions-about-securing-hololens-devices)
-- [How do I delete all spaces?](#how-do-i-delete-all-spaces)
-- [I cannot find or use the keyboard to type in the HoloLens 2 Emulator](#i-cannot-find-or-use-the-keyboard-to-type-in-the-hololens-2-emulator)
-
-## My holograms don't look right or are moving around
-
-If your holograms don't look right (for example, they're jittery or shaky, or you see black patches on top of them), try one of these fixes:
-
-- [Clean your device visor](hololens1-hardware.md#care-and-cleaning) and make sure nothing is blocking the sensors.
-- Make sure that you're in a well-lit room that does not have a lot of direct sunlight.
-- Try walking around and gazing at your surroundings so that HoloLens can scan them more completely.
-- If you've placed a lot of holograms, try removing some.
-
-If you're still having problems, trying running the Calibration app. This app calibrates your HoloLens just for you to help keep your holograms looking their best. To do this, go to **Settings** > **System** > **Utilities**. Under **Calibration**, select **Open Calibration**.
-
-[Back to list](#list)
-
-## I see a message that says "Finding your space"
-
-When HoloLens is learning or loading a space, you may see a brief message that says "Finding your space." If this message displays for more than a few seconds, you'll see another message under the Start menu that says "Still looking for your space."
-
-These messages mean that HoloLens is having trouble mapping your space. When this happens, you can open apps, but you can't place holograms in your environment.
-
-If you see these messages often, try one or more of the following fixes:
-
-- Make sure that you're in a well-lit room that does not have a lot of direct sunlight.
-- Make sure that your device visor is clean. [Learn how to clean your visor](hololens1-hardware.md#care-and-cleaning).
-- Make sure that you have a strong Wi-Fi signal. If you enter a new environment that has no Wi-Fi or a weak Wi-Fi signal, HoloLens won't be able find your space. Check your Wi-Fi connection by going to **Settings** > **Network & Internet** > **Wi-Fi**.
-- Try moving more slowly.
-
-[Back to list](#list)
-
-## I'm not seeing the holograms that I expect to see in my space
-
-If you don't see the holograms that you placed, or if you're seeing some that you don't expect, try one or more of the following fixes:
-
-- Turn on some lights. HoloLens works best in a well-lit space.
-- Remove holograms that you don't need by going to **Settings** > **System** > **Holograms** > **Remove nearby holograms**. Or, if needed, select **Remove all holograms**.
-
- > [!NOTE]
- > If the layout or lighting in your space changes significantly, your device might have trouble identifying your space and showing your holograms.
-
-[Back to list](#list)
-
-## I can't place holograms where I want to
-
-Here are some things to try if you're having trouble placing holograms:
-
-- Stand between one and three meters from where you're trying to place the hologram.
-- Don't place holograms on black or reflective surfaces.
-- Make sure that you're in a well-lit room that does not have a lot of direct sunlight.
-- Walk around the rooms so HoloLens can rescan your surroundings. To see what's already been scanned, air tap to reveal the mapping mesh graphic.
-
-[Back to list](#list)
-
-## Holograms disappear or are encased in other holograms or objects
-
-If you get too close to a hologram, it will temporarily disappear—to restore the hologram, just move away from it. Also, if you've placed several holograms close together, some may disappear. Try removing a few.
-
-Holograms can also be blocked or encased by other holograms or by objects such as walls. If this happens, try one of the following fixes:
-
-- If the hologram is encased in another hologram, move the encased hologram to another location. To do this, select **Adjust**, then tap and hold to position it.
-- If the hologram is encased in a wall, select **Adjust**, then walk toward the wall until the hologram appears. Tap and hold, then pull the hologram forward and out of the wall.
-- If you can't move the hologram by using gestures, use your voice to remove it. Gaze at the hologram, then say "Remove." Then reopen the hologram and place it in a new location.
-
-[Back to list](#list)
-
-## I can see holograms that are on the other side of a wall
-
-If you're very close to a wall, or if HoloLens hasn't scanned the wall yet, you can see holograms that are in the next room. To scan the wall, stand between one and three meters from the wall and gaze at it.
-
-A black or reflective object (for example, a black couch or a stainless steel refrigerator) near the wall may cause problems when HoloLens tries to scan the wall. If there is such an object, scan the other side of the wall.
-
-[Back to list](#list)
-
-## When I place a hologram on a wall, the hologram seems to float
-
-A hologram that you place on a wall typically appears to be an inch or so away from the wall. If it appears to be farther away, try one or more of the following fixes:
-
-- When you place a hologram on a wall, stand between one and three meters from the wall and face the wall straight on.
-- Air tap the wall to reveal the mapping mesh graphic. Make sure that the mesh aligns with the wall. If it doesn't, remove the hologram, rescan the wall, and then try again.
-- If the issue persists, run the Calibration app. You'll find it in **Settings** > **System** > **Utilities**.
-
-[Back to list](#list)
-
-## Apps appear too close to me when I'm trying to move them
-
-Try walking around and looking at the area where you're placing the app so that HoloLens scans the area from different angles. [Cleaning your device visor](hololens1-hardware.md#care-and-cleaning) may also help.
-
-[Back to list](#list)
-
-## I'm getting a low disk space error
-
-Free up some storage space by doing one or more of the following:
-
-- Remove some of the holograms that you've placed, or remove some saved data from within apps. [How do I find my data?](holographic-data.md)
-- Delete some pictures and videos in the Photos app.
-- Uninstall some apps from your HoloLens. In the **All apps** list, tap and hold the app you want to uninstall, then select **Uninstall**. (Uninstalling the app also deletes any data that the app stores on the device.)
-
-[Back to list](#list)
-
-## HoloLens doesn't respond to my gestures
-
-To make sure that HoloLens can see your gestures, keep your hand in the gesture frame. The gesture frame extends a couple of feet on either side of you. HoloLens can also best see your hand when you hold it about 18 inches in front of your body (though you don't have to be precise about this). When HoloLens can see your hand, the cursor changes from a dot to a ring. Learn more about [using gestures in HoloLens 2](hololens2-basic-usage.md) or [using gestures in HoloLens (1st gen)](hololens1-basic-usage.md).
-
-[Back to list](#list)
-
-## HoloLens doesn't respond to my voice
-
-HoloLens (1st gen) and HoloLens 2 have built-in speech recognition, and also support Cortana (online speech recognition).
-
-### Built-in voice commands do not work
-
-On HoloLens (1st gen), built-in speech recognition is not configurable. It is always turned on. On HoloLens 2, you can choose whether to turn on both speech recognition and Cortana during device setup.
-
-If your HoloLens 2 is not responding to your voice, make sure Speech recognition is turned on. Go to **Start** > **Settings** > **Privacy** > **Speech** and turn on **Speech recognition**.
-
-### Cortana or Dictation doesn't work
-
-If Cortana or Dictation isn't responding to your voice, make sure online speech recognition is turned on. Go to **Start** > **Settings** > **Privacy** > **Speech** and verify the **Online speech recognition** settings.
-
-If Cortana is still not responding, do one of the following to verify that Cortana itself is turned on:
-
-- In **All apps**, select **Cortana** > select **Menu** > **Notebook** > **Settings** to make changes.
-- On HoloLens 2, select the **Speech settings** button or say "Speech settings."
-
-To learn more about what you can say, see [Use your voice with HoloLens](hololens-cortana.md).
-
-[Back to list](#list)
-
-## I'm having problems pairing or using a Bluetooth device
-
-If you're having problems [pairing a Bluetooth device](hololens-connect-devices.md), try the following:
-
-- Go to **Settings** > **Devices**, and make sure that Bluetooth is turned on. If it is, turn it off and on again.
-- Make sure that your Bluetooth device is fully charged or has fresh batteries.
-- If you still can't connect, [restart the HoloLens](hololens-recovery.md).
-
-[Back to list](#list)
-
-## HoloLens Settings lists devices as available, but the devices don't work
-
-HoloLens doesn't support Bluetooth audio profiles. Bluetooth audio devices, such as speakers and headsets, may appear as available in HoloLens settings, but they aren't supported.
-
-If you're having trouble using a Bluetooth device, make sure that it's a supported device. Supported devices include the following:
-
-- English-language QWERTY Bluetooth keyboards (you can use these anywhere that you use the holographic keyboard).
-- Bluetooth mice.
-- The [HoloLens clicker](hololens1-clicker.md).
-
-You can pair other Bluetooth HID and GATT devices together with your HoloLens. However, you may have to install corresponding companion apps from Microsoft Store to actually use the devices.
-
-[Back to list](#list)
-
-## I'm having problems using the HoloLens clicker
-
-Use the [clicker](hololens1-clicker.md) to select, scroll, move, and resize holograms. Individial apps may support additional clicker gestures.
-
-If you're having trouble using the clicker, make sure that it's charged and paired with your HoloLens. If the battery is low, the indicator light blinks amber. To verify that the clicker is paired, go to **Settings** > **Devices** and see if it shows up there. For more information, see [Pair the clicker](hololens-connect-devices.md#hololens-1st-gen-pair-the-clicker).
-
-If the clicker is charged and paired and you're still having problems, reset it by holding down the main button and the pairing button for 15 seconds. Then pair the clicker with your HoloLens again.
-
-If resetting the clicker doesn't help, see [Restart or recover the HoloLens clicker](hololens1-clicker.md#restart-or-recover-the-clicker).
-
-[Back to list](#list)
-
-## I can't connect to Wi-Fi
-
-Here are some things to try if you can't connect your HoloLens to a Wi-Fi network:
-
-- Make sure that Wi-Fi is turned on. To check, use the Start gesture, then select **Settings** > **Network & Internet** > **Wi-Fi**. If Wi-Fi is on, try turning it off and then on again.
-- Move closer to the router or access point.
-- Restart your Wi-Fi router, then [restart HoloLens](hololens-recovery.md). Try connecting again.
-- If none of these things work, check to make sure that your router is using the latest firmware. You can find this information on the manufacturer website.
-
-[Back to list](#list)
-
-## My HoloLens isn't running well, is unresponsive, or won't start
-
-If your device isn't performing properly, see [Restart, reset, or recover HoloLens](hololens-recovery.md).
-
-[Back to list](#list)
-
-## I can't sign in to a HoloLens device because it was previously set up for someone else
-
-If your device was previously set up for someone else, either for a client or for a former employee, and you don't have their password to unlock the device, you can do one of the following:
-
-- For a device that is enrolled in Intune mobile device management (MDM), you can use Intune to remotely [wipe](https://docs.microsoft.com/intune/remote-actions/devices-wipe) the device. The device then re-flashes itself.
- > [!IMPORTANT]
- > When you wipe the device, make sure to leave **Retain enrollment state and user account** unchecked.
-- For a non-MDM device, you can [put the device into **Flashing Mode** and use Advanced Recovery Companion](hololens-recovery.md#re-install-the-operating-system) to recover the device.
-
-[Back to list](#list)
-
-## Questions about managing HoloLens devices
-
-### Can I use System Center Configuration Manager (SCCM) to manage HoloLens devices?
-
-No. You have to use an MDM system to manage HoloLens devices.
-
-### Can I use Active Directory Domain Services (AD DS) to manage HoloLens user accounts?
-
-No. You have to use Azure Active Directory (AAD) to manage user accounts for HoloLens devices.
-
-### Is HoloLens capable of Automated Data Capture Systems (ADCS) auto-enrollment?
-
-No.
-
-### Can HoloLens participate in Integrated Windows Authentication?
-
-No.
-
-### Does HoloLens support branding?
-
-No. However, you can work around this issue by using one of the following approaches:
-
-- Create a custom app, and then [enable Kiosk mode](hololens-kiosk.md). The custom app can have branding, and can launch other apps (such as Remote Assist).
-- Change all of the user profile pictures in AAD to your company logo. However, this may not be desirable for all scenarios.
-
-### What logging capabilities do HoloLens (1st gen) and HoloLens 2 offer?
-
-Logging is limited to traces that can be captured in development or troubleshooting scenarios, or telemetry that the devices send to Microsoft servers.
-
-[Back to list](#list)
-
-## Questions about securing HoloLens devices
-
-See [frequently asked questions about securing HoloLens devices](hololens-faq-security.md).
-
-[Back to list](#list)
-
-## How do I delete all spaces?
-
-*Coming soon*
-
-[Back to list](#list)
-
-## I cannot find or use the keyboard to type in the HoloLens 2 Emulator
-
-*Coming soon*
-
-[Back to list](#list)
diff --git a/devices/hololens/hololens-calibration.md b/devices/hololens/hololens-calibration.md
deleted file mode 100644
index b03fb4479f..0000000000
--- a/devices/hololens/hololens-calibration.md
+++ /dev/null
@@ -1,154 +0,0 @@
----
-title: Improve visual quality and comfort
-description: Calibrating your IPD (interpupillary distance) can improve the quality of your visuals. Both HoloLens and Windows Mixed Reality immersive headsets offer ways to customize IPD.
-author: Teresa-Motiv
-ms.author: xerxesb
-ms.date: 9/13/2019
-ms.topic: article
-keywords: calibration, comfort, visuals, quality, ipd
-ms.prod: hololens
-ms.sitesec: library
-author: Teresa-Motiv
-ms.localizationpriority: high
-ms.reviewer:
-manager: jarrettr
-appliesto:
-- HoloLens (1st gen)
-- HoloLens 2
----
-
-# Improve visual quality and comfort
-
-HoloLens 2 and HoloLens (1st gen) both work better when they're calibrated to your unique eyes.
-
-While both devices need to calibrate for the best hologram viewing experience, they use different calibration technologies and techniques. Jump to [HoloLens 2 calibration](#calibrating-your-hololens-2) or [HoloLens (1st gen) calibration](#calibrating-your-hololens-1st-gen).
-
-## Calibrating your HoloLens 2
-
-HoloLens 2 uses eye-tracking technology to improve your experience seeing and interacting with the virtual environment. Calibrating the HoloLens 2 ensures that it can accurately track your eyes (and the eyes of anyone else who uses the device). After calibration, holograms will appear correctly even as the visor shifts on your head.
-
-HoloLens 2 prompts a user to calibrate the device under the following circumstances:
-
-- The user is using the device for the first time
-- The user previously opted out of the calibration process
-- The calibration process did not succeed the last time the user used the device
-- The user has deleted their calibration profiles
-- The device is taken off and put back on and any of the above circumstances apply
-
-
-
-
-During this process, you'll look at a set of targets (gems). It's fine if you blink or close your eyes during calibration but try not to stare at other objects in the room. This allows HoloLens to learn about your eye position to render your holographic world.
-
-
-
-
-
-
-
-If calibration was successful, you'll see a success screen. If not, read more about diagnosing calibration failures [here](#troubleshooting-hololens-2-calibration).
-
-
-
-### Calibration when sharing a device or session
-
-Multiple users can share a HoloLens 2 device, without a need for each person to go through device setup. When a new user puts the device on their head for th first time, HoloLens 2 automatically prompts the user to calibrate visuals. When a user that has previously calibrated visuals puts the device on their head, the display seamlessly adjusts for quality and a comfortable viewing experience.
-
-### Manually starting the calibration process
-
-1. Use the start gesture to open the [**Start** menu](hololens2-basic-usage.md#start-gesture).
-1. If the Settings app isn't pinned to **Start**, select **All Apps**.
-1. Select **Settings**, and then select **System** > **Calibration** > **Eye Calibration** > **Run eye calibration**.
-
- 
-
-### Troubleshooting HoloLens 2 calibration
-
-Calibration should work for most people, but there are cases where calibration fails.
-
-Some potential reasons for calibration failure include:
-
-- Getting distracted and not following the calibration targets
-- Dirty or scratched device visor or device visor not positioned properly
-- Dirty or scratched glasses
-- Certain types of contact lenses and glasses (colored contact lenses, some toric contact lenses, IR blocking glasses, some high prescription glasses, sunglasses, or similar)
-- More-pronounced makeup and some eyelash extensions
-- Hair or thick eyeglass frames if they are blocking the device from seeing your eyes
-- Certain eye physiology, eye conditions or eye surgery such as narrow eyes, long eyelashes, amblyopia, nystagmus, some cases of LASIK or other eye surgeries
-
-If calibration is unsuccessful try:
-
-- Cleaning your device visor
-- Cleaning your glasses
-- Pushing your device visor as close to your eyes as possible
-- Moving objects in your visor out of the way (such as hair)
-- Turning on a light in your room or moving out of direct sunlight
-
-If you followed all guidelines and calibration is still failing, please let us know by filing feedback in [Feedback Hub](hololens-feedback.md).
-
-Note that setting IPD is not applicable for Hololens 2, since eye positions are computed by the system.
-
-### Calibration data and security
-
-Calibration information is stored locally on the device and is not associated with any account information. There is no record of who has used the device without calibration. This mean new users will get prompted to calibrate visuals when they use the device for the first time, as well as users who opted out of calibration previously or if calibration was unsuccessful.
-
-Calibration information can always be deleted from the device in **Settings** > **Privacy** > **Eye tracker**.
-
-### Disable calibration
-
-You can also disable the calibration prompt by following these steps:
-
-1. Select **Settings** > **System** > **Calibration**.
-1. Turn off **When a new person uses this HoloLens, automatically ask to run eye calibration**.
-
-> [!IMPORTANT]
-> This setting may adversely affect hologram rendering quality and comfort. When you turn off this setting, features that depend on eye tracking (such as text scrolling) no longer work in immersive applications.
-
-### HoloLens 2 eye-tracking technology
-
-The device uses its eye-tracking technology to improve display quality, and to ensure that all holograms are positioned accurately and comfortable to view in 3D. Because it uses the eyes as landmarks, the device can adjust itself for every user and tune its visuals as the headset shifts slightly throughout use. All adjustments happen on the fly without a need for manual tuning.
-> [!NOTE]
-> Setting the IPD is not applicable for Hololens 2, since eye positions are computed by the system.
-
-HoloLens applications use eye tracking to track where you are looking in real time. This is the main capability developers can leverage to enable a whole new level of context, human understanding and interactions within the Holographic experience. Developers don’t need to do anything to leverage this capability.
-
-## Calibrating your HoloLens (1st gen)
-
-HoloLens (1st gen) adjusts hologram display according to the your [interpupillary distance](https://en.wikipedia.org/wiki/Interpupillary_distance) (IPD). If the IPD is not accurate, holograms may appear unstable or at an incorrect distance. You can improve the quality of your visuals by calibrating the device to your interpupillary distance (IPD).
-
-When you set up your Hololens (1st gen) device, it prompts to calibrate your visuals after Cortana introduces herself. It's recommended that you complete the calibration step during this setup phase. However you can skip it by waiting until Cortana prompts you and then saying "Skip."
-
-During the calibration process, HoloLens asks you to align your finger with a series of six targets per eye. HoloLens uses this process to set the IPD correctly for your eyes.
-
-
-
-### Manually start the calibration process
-
-If you need to update the calibration or if a new user needs to adjust it, you can manually run the Calibration app at any time. The Calibration app is installed by default. You can access it by using eihter the **Start** menu or the Settings app.
-
-To use the **Start** menu to run the Calibration app, follow these steps:
-
-1. Use the [bloom](hololens1-basic-usage.md) gesture to open the **Start** menu.
-1. To view all apps, select **+**.
-1. Select **Calibration**.
-
-
-
-
-
-To use the Settings app to run the Calibration app, follow these steps:
-
-1. Use the [bloom](hololens1-basic-usage.md) gesture to open the **Start** menu.
-1. If **Settings** isn't pinned to **Start**, select **+** to view all apps.
-1. Select **Settings**.
-1. Select **System** > **Utilities** > **Open Calibration**.
-
-
-
-## Immersive headsets
-
-Some immersive headsets provide the ability to customize the IPD setting. To change the IPD for your headset, open the Settings app and select **Mixed reality** > **Headset display**, and then move the slider control. You’ll see the changes in real time in your headset. If you know your IPD, maybe from a visit to the optometrist, you can enter it directly as well.
-
-You can also adjust this setting on your PC by selecting **Settings** > **Mixed reality** > **Headset display**.
-
-If your headset does not support IPD customization, this setting will be disabled.
diff --git a/devices/hololens/hololens-commercial-features.md b/devices/hololens/hololens-commercial-features.md
deleted file mode 100644
index f53558ec75..0000000000
--- a/devices/hololens/hololens-commercial-features.md
+++ /dev/null
@@ -1,81 +0,0 @@
----
-title: Commercial features
-description: The Microsoft HoloLens Commercial Suite includes features that make it easier for businesses to manage HoloLens devices. HoloLens 2 devices are equipped with commercial features by default.
-keywords: HoloLens, commercial, features, mdm, mobile device management, kiosk mode
-author: scooley
-ms.author: scooley
-ms.date: 08/26/2019
-ms.custom:
-- CI 111456
-- CSSTroubleshooting
-ms.topic: article
-audience: ITPro
-ms.prod: hololens
-ms.sitesec: library
-ms.localizationpriority: high
-ms.reviewer:
-manager: jarrettr
-appliesto:
-- HoloLens (1st gen)
-- HoloLens 2
----
-
-# Commercial features
-
-HoloLens includes features that make it easier for businesses to manage HoloLens devices.
-
-Every HoloLens 2 device has commercial features available.
-
-HoloLens (1st gen) came with two licensing options, the developer license and a commercial license. To unlock HoloLens's commercial capabilities, upgrade from the developer license to a commercial license. To purchase the Microsoft HoloLens Commercial Suite, contact your local Microsoft account manager.
-
->[!VIDEO https://www.youtube.com/embed/tNd0e2CiAkE]
-
-## Key commercial features
-
-- **Kiosk mode.** You can use HoloLens in demo or showcase experiences by using kiosk mode, to limit which apps can run.
-
- 
-
-- **Mobile Device Management (MDM) for HoloLens.** Your IT department can manage multiple HoloLens devices simultaneously by using solutions such as Microsoft Intune. You can manage settings, select apps to install, and set security configurations that are tailored to your organization's needs.
-
- 
-
-- **Windows Update for Business.** Windows Update for Business provides controlled operating system updates to devices and support for the long-term servicing channel.
-- **Data security.** BitLocker data encryption is enabled on HoloLens to provide the same level of security protection as any other Windows device.
-- **Work access.** Anyone in your organization can remotely connect to the corporate network through virtual private network (VPN) on a HoloLens. HoloLens can also access Wi-Fi networks that require credentials.
-- **Microsoft Store for Business.** Your IT department can also set up an enterprise private store, containing only your company's apps for your specific HoloLens usage. Securely distribute your enterprise software to selected group of enterprise users.
-
-## Feature comparison between editions
-
-|Features |HoloLens Development Edition |HoloLens Commercial Suite |HoloLens 2 |
-|---|:---:|:---:|:---:|
-|Device Encryption (BitLocker) | |✔️ |✔️ |
-|Virtual Private Network (VPN) | |✔️ |✔️ |
-|[Kiosk mode](hololens-kiosk.md) | |✔️ |✔️ |
-|**Management and deployment** | | | |
-|Mobile Device Management (MDM) | |✔️ |✔️ |
-|Ability to block unenrollment | |✔️ |✔️ |
-|Cert-based corporate Wi-Fi access | |✔️ |✔️ |
-|Microsoft Store (Consumer) |Consumer |Filter by using MDM |Filter by using MDM |
-|[Business Store Portal](https://docs.microsoft.com/microsoft-store/working-with-line-of-business-apps) | |✔️ |✔️ |
-|**Security and identity** | | | |
-|Sign in by using Azure Active Directory (AAD) account |✔️ |✔️ |✔️ |
-|Sign in by using Microsoft Account (MSA) |✔️ |✔️ |✔️ |
-|Next Generation Credentials with PIN unlock |✔️ |✔️ |✔️ |
-|[Secure boot](https://docs.microsoft.com/windows-hardware/design/device-experiences/oem-secure-boot) |✔️ |✔️ |✔️ |
-|**Servicing and support** | | | |
-|Automatic system updates as they arrive |✔️ |✔️ |✔️ |
-|[Windows Update for Business](https://docs.microsoft.com/windows/deployment/update/waas-manage-updates-wufb) | |✔️ |✔️ |
-|Long-Term Servicing Channel (LTSC) | |✔️ |✔️ |
-
-## Enabling commercial features
-
-Your organization's IT admin can set up commercial features such as Microsoft Store for Business, kiosk mode, and enterprise Wi-Fi access. The [Microsoft HoloLens](index.md) documentation provides step-by-step instructions for enrolling devices and installing apps from Microsoft Store for Business.
-
-## See also
-
-- [Microsoft HoloLens](index.md)
-- [Kiosk mode](hololens-kiosk.md)
-- [CSPs supported in HoloLens devices](/windows/client-management/mdm/configuration-service-provider-reference#csps-supported-in-hololens-devices)
-- [Microsoft Store For Business and line of business applications](https://blogs.technet.microsoft.com/sbucci/2016/04/13/windows-store-for-business-and-line-of-business-applications/)
-- [Working with line-of-business apps](/microsoft-store/working-with-line-of-business-apps)
diff --git a/devices/hololens/hololens-commercial-infrastructure.md b/devices/hololens/hololens-commercial-infrastructure.md
deleted file mode 100644
index 98ec5c6e06..0000000000
--- a/devices/hololens/hololens-commercial-infrastructure.md
+++ /dev/null
@@ -1,190 +0,0 @@
----
-title: Infrastructure Guidelines for HoloLens
-description:
-ms.prod: hololens
-ms.sitesec: library
-author: pawinfie
-ms.author: pawinfie
-audience: ITPro
-ms.topic: article
-ms.localizationpriority: high
-ms.date: 1/23/2020
-ms.reviewer:
-audience: ITPro
-manager: bradke
-appliesto:
-- HoloLens (1st gen)
-- HoloLens 2
----
-
-# Configure Your Network for HoloLens
-
-This portion of the document will require the following people:
-
-1. Network Admin with permissions to make changes to the proxy/firewall
-2. Azure Active Directory Admin
-3. Mobile Device Manager Admin
-
-## Infrastructure Requirements
-
-HoloLens is, at its core, a Windows mobile device integrated with Azure. It works best in commercial environments with wireless network availability (wi-fi) and access to Microsoft services.
-
-Critical cloud services include:
-
-- Azure active directory (AAD)
-- Windows Update (WU)
-
-Commercial customers will need enterprise mobility management (EMM) or mobile device management (MDM) infrastructure to manage HoloLens devices at scale. This guide uses [Microsoft Intune](https://www.microsoft.com/enterprise-mobility-security/microsoft-intune) as an example, though any provider with full support for Microsoft Policy can support HoloLens. Ask your mobile device management provider if they support HoloLens 2.
-
-HoloLens does support a limited set of cloud disconnected experiences.
-
-### Wireless network EAP support
-
-- PEAP-MS-CHAPv2
-- PEAP-TLS
-- TLS
-- TTLS-CHAP
-- TTLS-CHAPv2
-- TTLS-MS-CHAPv2
-- TTLS-PAP
-- TTLS-TLS
-
-### HoloLens Specific Network Requirements
-
-Make sure that [this list](hololens-offline.md) of endpoints are allowed on your network firewall. This will enable HoloLens to function properly.
-
-### Remote Assist Specific Network Requirements
-
-1. The recommended bandwidth for optimal performance of Remote Assist is 1.5Mbps. Detailed network requirements and additional information can be found [here](https://docs.microsoft.com/MicrosoftTeams/prepare-network).
-**(Please note, if you don’t network have network speeds of at least 1.5Mbps, Remote Assist will still work. However, quality may suffer).**
-1. Make sure that these ports and URLs are allowed on your network firewall. This will enable Microsoft Teams to function. The latest list can be found [here](https://docs.microsoft.com/office365/enterprise/urls-and-ip-address-ranges#skype-for-business-online-and-microsoft-teams).
-
-### Guides Specific Network Requirements
-
-Guides only require network access to download and use the app.
-
-## Azure Active Directory Guidance
-
-> [!NOTE]
-> This step is only necessary if your company plans on managing the HoloLens.
-
-1. Ensure that you have an Azure AD License.
-Please [HoloLens Licenses Requirements](hololens-licenses-requirements.md) for additional information.
-
-1. If you plan on using Auto Enrollment, you will have to [Configure Azure AD enrollment.](https://docs.microsoft.com/intune/deploy-use/.set-up-windows-device-management-with-microsoft-intune#azure-active-directory-enrollment)
-
-1. Ensure that your company’s users are in Azure Active Directory (Azure AD).
-Instructions for adding users can be found [here](https://docs.microsoft.com/azure/active-directory/fundamentals/add-users-azure-active-directory).
-
-1. We suggest that users who need similar licenses are added to the same group.
- 1. [Create a Group](https://docs.microsoft.com/azure/active-directory/fundamentals/active-directory-groups-create-azure-portal)
- 1. [Add users to groups](https://docs.microsoft.com/azure/active-directory/fundamentals/active-directory-groups-members-azure-portal)
-
-1. Ensure that your company’s users (or group of users) are assigned the necessary licenses.
-Directions for assigning licenses can be found [here](https://docs.microsoft.com/azure/active-directory/fundamentals/license-users-groups).
-
-1. Only do this step if users are expected to enroll their HoloLens/Mobile device into you (There are three options)
-These steps ensure that your company’s users (or a group of users) can add devices.
- 1. **Option 1:** Give all users permission to join devices to Azure AD.
-**Sign in to the Azure portal as an administrator** > **Azure Active Directory** > **Devices** > **Device Settings** >
-**Set Users may join devices to Azure AD to *All***
-
- 1. **Option 2:** Give selected users/groups permission to join devices to Azure AD
-**Sign in to the Azure portal as an administrator** > **Azure Active Directory** > **Devices** > **Device Settings** >
-**Set Users may join devices to Azure AD to *Selected***
-
-
- 1. **Option 3:** You can block all users from joining their devices to the domain. This means that all devices will need to be manually enrolled.
-
-## Mobile Device Manager Guidance
-
-### Ongoing device management
-
-> [!NOTE]
-> This step is only necessary if your company plans to manage the HoloLens.
-
-Ongoing device management will depend on your mobile device management infrastructure. Most have the same general functionality but the user interface may vary widely.
-
-1. [CSPs (Configuration Service Providers)](https://docs.microsoft.com/windows/client-management/mdm/configuration-service-provider-reference#csps-supported-in-hololens-devices) allows you to create and deploy management settings for the devices on your network. A list of CSPs for HoloLens can be found [here](https://docs.microsoft.com/windows/client-management/mdm/configuration-service-provider-reference#csps-supported-in-hololens-devices).
-
-1. [Compliance policies](https://docs.microsoft.com/intune/device-compliance-get-started) are rules and settings that devices must meet to be compliant in your corporate infrastructure. Use these policies with Conditional Access to block access to company resources for devices that are non-compliant. For example, you can create a policy that requires Bitlocker be enabled.
-
-1. [Create Compliance Policy](https://docs.microsoft.com/intune/protect/compliance-policy-create-windows).
-
-1. Conditional Access allows/denies mobile devices and mobile applications from accessing company resources. Two documents you may find helpful are [Plan your CA Deployment](https://docs.microsoft.com/azure/active-directory/conditional-access/plan-conditional-access) and [Best Practices](https://docs.microsoft.com/azure/active-directory/conditional-access/best-practices).
-
-1. [This article](https://docs.microsoft.com/intune/fundamentals/windows-holographic-for-business) talks about Intune's management tools for HoloLens.
-
-1. [Create a device profile](https://docs.microsoft.com/intune/configuration/device-profile-create)
-
-### Manage updates
-
-Intune includes a feature called Update rings for Windows 10 devices, including HoloLens 2 and HoloLens v1 (with Holographic for Business). Update rings include a group of settings that determine how and when updates are installed.
-
-For example, you can create a maintenance window to install updates, or choose to restart after updates are installed. You can also choose to pause updates indefinitely until you're ready to update.
-
-Read more about [configuring update rings with Intune](https://docs.microsoft.com/intune/windows-update-for-business-configure).
-
-### Application management
-
-Manage HoloLens applications through:
-
-1. Microsoft Store
- The Microsoft Store is the best way to distribute and consume applications on HoloLens. There is a great set of core HoloLens applications already available in the store or you can [publish your own](https://docs.microsoft.com/windows/uwp/publish/).
- All applications in the store are available publicly to everyone, but if it isn't acceptable, checkout the Microsoft Store for Business.
-
-1. [Microsoft Store for Business](https://docs.microsoft.com/microsoft-store/)
- Microsoft Store for Business and Education is a custom store for your corporate environment. It lets you use the Microsoft Store built into Windows 10 and HoloLens to find, acquire, distribute, and manage apps for your organization. It also lets you deploy apps that are specific to your commercial environment but not to the world.
-
-1. Application deployment and management via Intune or another mobile device management solution
- Most mobile device management solutions, including Intune, provide a way to deploy line of business applications directly to a set of enrolled devices. See this article for [Intune app install](https://docs.microsoft.com/intune/apps-deploy).
-
-1. _not recommended_ Device Portal
- Applications can also be installed on HoloLens directly using the Windows Device Portal. This isn't recommended since Developer Mode has to be enabled to use the device portal.
-
-Read more about [installing apps on HoloLens](https://docs.microsoft.com/hololens/hololens-install-apps).
-
-### Certificates
-
-You can distribute certificates through your MDM provider. If your company requires certificates, Intune supports PKCS, PFX, and SCEP. It is important to understand which certificate is right for your company. Please visit [here](https://docs.microsoft.com/intune/protect/certificates-configure) to determine which cert is best for you. If you plan to use certificates for HoloLens Authentication, PFX or SCEP may be right for you.
-
-Steps for SCEP can be found [here](https://docs.microsoft.com/intune/protect/certificates-profile-scep).
-
-### How to Upgrade to Holographics for Business Commercial Suite
-
-> [!NOTE]
-> Windows Holographics for Business (commercial suite) is only intended for HoloLens 1st gen devices. The profile will not be applied to HoloLens 2 devices.
-
-Directions for upgrading to the commercial suite can be found [here](https://docs.microsoft.com/intune/configuration/holographic-upgrade).
-
-### How to Configure Kiosk Mode Using Microsoft Intune
-
-1. Sync Microsoft Store to Intune ([Here](https://docs.microsoft.com/intune/apps/windows-store-for-business)).
-
-1. Check your app settings
- 1. Log into your Microsoft Store Business account
- 1. **Manage > Products and Services > Apps and Software > Select the app you want to sync > Private Store Availability > Select “Everyone” or “Specific Groups”**
- >[!NOTE]
- >If you don't see the app you want, you will have to "get" the app by searching the store for your app. **Click the "Search" bar in the upper right-hand corner > type in the name of the app > click on the app > select "Get"**.
- 1. If you do not see your apps in **Intune > Client Apps > Apps** , you may have to [sync your apps](https://docs.microsoft.com/intune/apps/windows-store-for-business#synchronize-apps) again.
-
-1. [Create a device profile for Kiosk mode](https://docs.microsoft.com/intune/configuration/kiosk-settings#create-the-profile)
-
-> [!NOTE]
-> You can configure different users to have different Kiosk Mode experiences by using “Azure AD” as the “User logon type”. However, this option is only available in Multi-App kiosk mode. Multi-App kiosk mode will work with only one app as well as multiple apps.
-
-
-
-For other MDM services, check your provider's documentation for instructions. If you need to use a custom setting and full XML configuration to set up a kiosk in your MDM service, additional directions can be found [here](hololens-kiosk.md#set-up-kiosk-mode-using-microsoft-intune-or-mdm-windows-10-version-1803)
-
-## Certificates and Authentication
-
-Certificates can be deployed via you MDM (see "certificates" in the [MDM Section](hololens-commercial-infrastructure.md#mobile-device-manager-guidance)). Certificates can also be deployed to the HoloLens through package provisioning. Please see [HoloLens Provisioning](hololens-provisioning.md) for additional information.
-
-### Additional Intune Quick Links
-
-1. [Create Profiles:](https://docs.microsoft.com/intune/configuration/device-profile-create) Profiles allow you to add and configure settings that will be pushed to the devices in your organization.
-
-## Next (Optional) Step: [Configure HoloLens using a provisioning package](hololens-provisioning.md)
-
-## Next Step: [Enroll your device](hololens-enroll-mdm.md)
diff --git a/devices/hololens/hololens-connect-devices.md b/devices/hololens/hololens-connect-devices.md
deleted file mode 100644
index 7926dab884..0000000000
--- a/devices/hololens/hololens-connect-devices.md
+++ /dev/null
@@ -1,76 +0,0 @@
----
-title: Connect to Bluetooth and USB-C devices
-description: This guide walks through connecting to Bluetooth and USB-C devices and accessories.
-ms.assetid: 01af0848-3b36-4c13-b797-f38ad3977e30
-ms.prod: hololens
-ms.sitesec: library
-author: Teresa-Motiv
-ms.author: v-tea
-ms.topic: article
-ms.localizationpriority: high
-ms.date: 03/11/2020
-manager: jarrettr
-appliesto:
-- HoloLens (1st gen)
-- HoloLens 2
----
-
-# Connect to Bluetooth and USB-C devices
-
-## Pair Bluetooth devices
-
-HoloLens 2 supports the following classes of Bluetooth devices:
-
-- Mouse
-- Keyboard
-- Bluetooth audio output (A2DP) devices
-
-HoloLens (1st gen) supports the following classes of Bluetooth devices:
-
-- Mouse
-- Keyboard
-- HoloLens (1st gen) clicker
-
-> [!NOTE]
-> Other types of Bluetooth devices, such as speakers, headsets, smartphones, and game pads, may be listed as available in HoloLens settings. However, these devices aren't supported on HoloLens (1st gen). For more information, see [HoloLens Settings lists devices as available, but the devices don't work](hololens-FAQ.md#hololens-settings-lists-devices-as-available-but-the-devices-dont-work).
-
-### Pair a Bluetooth keyboard or mouse
-
-1. Turn on your keyboard or mouse, and make it discoverable. To learn how to make the device discoverable, look for information on the device (or its documentation) or visit the manufacturer's website.
-
-1. Use the bloom gesture (HoloLens (1st gen)) or the start gesture (HoloLens 2) to go to **Start**, and then select **Settings**.
-1. Select **Devices**, and make sure that Bluetooth is on.
-1. When you see the device name, select **Pair**, and then follow the instructions.
-
-### HoloLens (1st gen): Pair the clicker
-
-1. Use the bloom gesture to go to **Start**, and then select **Settings**.
-1. Select **Devices**, and make sure that Bluetooth is on.
-1. Use the tip of a pen to press and hold the clicker pairing button until the clicker status light blinks white. Make sure to hold down the button until the light starts blinking.
- The pairing button is on the underside of the clicker, next to the finger loop.
- 
-1. On the pairing screen, select **Clicker** > **Pair**.
-
-## HoloLens 2: Connect USB-C devices
-
-HoloLens 2 supports the following classes of USB-C devices:
-
-- Mass storage devices (such as thumb drives)
-- Ethernet adapters (including ethernet plus charging)
-- USB-C-to-3.5mm digital audio adapters
-- USB-C digital audio headsets (including headset adapters plus charging)
-- Wired mouse
-- Wired keyboard
-- Combination PD hubs (USB A plus PD charging)
-
-## Connect to Miracast
-
-To use Miracast, follow these steps:
-
-1. Do one of the following:
-
- - Open the **Start** menu, and select the display icon.
- - Say "Connect" while you gaze at the **Start** menu.
-
-1. On the list of devices that appears, select an available device.
-1. Complete the pairing to begin projecting.
diff --git a/devices/hololens/hololens-cortana.md b/devices/hololens/hololens-cortana.md
deleted file mode 100644
index 89a01c0628..0000000000
--- a/devices/hololens/hololens-cortana.md
+++ /dev/null
@@ -1,140 +0,0 @@
----
-title: Use your voice with HoloLens
-description: Cortana can help you do all kinds of things on your HoloLens
-ms.assetid: fd96fb0e-6759-4dbe-be1f-58bedad66fed
-ms.date: 03/10/2020
-keywords: hololens
-ms.prod: hololens
-ms.sitesec: library
-author: Teresa-Motiv
-audience: ITPro
-ms.author: v-tea
-ms.topic: article
-manager: jarrettr
-ms.localizationpriority: high
-appliesto:
-- HoloLens (1st gen)
-- HoloLens 2
----
-
-# Use your voice with HoloLens
-
-You can use your voice to do almost anything on HoloLens, such as taking a quick photo or opening an app. Many voice commands are built into HoloLens, while others are available through Cortana.
-
-This article teaches you how to control HoloLens and your holographic world with your voice and with Cortana.
-
-> [!NOTE]
-> Speech is only supported in [some languages](hololens2-language-support.md). The speech language is based on the Windows display language, not the keyboard language.
->
-> You can verify the Windows display language by selecting **Settings** > **Time and Language** > **Language**.
-
-## Built-in voice commands
-
-Get around HoloLens faster with these basic commands. In order to use these, you need to enable Speech during the first run of the device or in **Settings** > **Privacy** > **Speech**. You can always check whether speech is enabled by looking at the status at the top of the Start menu. For the best speech recognition results, HoloLens 2 uses the Microsoft cloud-based services. However, you can use Settings to disable this feature. To do this, in Settings, turn off **Online speech recognition**. After you change this setting, HoloLens 2 will only process voice data locally to recognize commands and dictation, and Cortana will not be available.
-
-### General speech commands
-
-Use these commands throughout Windows Mixed Reality to get around faster. Some commands use the gaze cursor, which you bring up by saying “select.”
-
-> [!NOTE]
-> Hand rays are not supported on HoloLens (1st Gen).
-
-| Say this | To do this |
-| - | - |
-| "Select" | Say "select" to bring up the gaze cursor. Then, turn your head to position the cursor on the thing you want to select, and say “select” again. |
-|Open the Start menu | "Go to Start" |
-|Close the Start menu | "Close" |
-|Leave an immersive app | Say "Go to Start" to bring up the quick actions menu, then say "Mixed reality home." |
-|Hide and show hand ray | "Hide hand ray" / "Show hand ray" |
-|See available speech commands | "What can I say?" |
-
-Starting with version 19041.x of HoloLens 2, you can also use these commands:
-
-| Say this | To do this |
-| - | - |
-| "Restart device" | Bring up a dialogue to confirm you want to restart the device. You can say "yes" to restart. |
-| "Shutdown device" | Bring up a dialogue to confirm you want to turn off the device. You can say "yes" to confirm. |
-| "Brightness up/down" | Increase or decrease the display brightness by 10%. |
-| "Volume up/down" | Increase or decrease the volume by 10%. |
-| "What's my IP address" | Bring up a dialogue displaying your device's current IP address on the local network. |
-| "Take a picture" | Capture a mixed reality photo of what you are currently seeing. |
-| "Take a video" | Start recording a mixed reality video. |
-| "Stop recording" | Stops the current mixed reality video recording if one is in progress. |
-
-### Hologram commands
-
-To use these commands, gaze at a 3D object, hologram, or app window.
-
-| Say this | To do this |
-| - | - |
-| "Bigger" | Make it bigger |
-| "Smaller" | Make it smaller |
-| "Face me" | Turn it to face you |
-| "Move this" | Move it (follow your gaze) |
-| "Close" | Close it |
-| "Follow me" / "Stop following" | Make it follow you as you move around |
-
-### See it, say it
-
-Many buttons and other elements on HoloLens also respond to your voice—for example, **Follow me** and **Close** on the app bar, or the **Back** button in Edge. To find out if a button is voice-enabled, rest your **gaze cursor**,**touch cursor** or one **hand ray** on it for a moment. If the button is voice-enabled, you'll see a voice tip.
-
-### Dictation mode
-
-Tired of typing? Switch to dictation mode any time that the holographic keyboard is active. To get started, select the microphone button or say "Start dictating." To stop dictating, select the button again or say "Stop dictating." To delete what you just dictated, say "Delete that."
-
-> [!NOTE]
-> To use dictation mode, you have to have an internet connection.
-
-HoloLens dictation uses explicit punctuation, meaning that you say the name of the punctuation you want to use. For instance, you might say "Hey **comma** what are you up to **question mark**."
-
-Here are the punctuation keywords that you can use:
-
-- Period, comma, question mark, exclamation point/exclamation mark
-- New line/new paragraph
-- Semicolon, colon
-- Open quote(s), close quote(s)
-- Hashtag, smiley/smiley face, frowny, winky
-- Dollar, percent
-
-Sometimes it's helpful to spell out things like email addresses. For instance, to dictate example@outlook.com, you'd say "E X A M P L E at outlook dot com."
-
-## Do more with Cortana
-
-Cortana can help you do all kinds of things on your HoloLens, but depending on which version of Windows Holographic you're using, the capablities may be different. You can learn more about the updated capabilites of the latest version of Cortana [here](https://blogs.windows.com/windowsexperience/2020/02/28/cortana-in-the-upcoming-windows-10-release-focused-on-your-productivity-with-enhanced-security-and-privacy/).
-
-
-
-Here are some things you can try saying (remember to say "Hey Cortana" first).
-
-**Hey, Cortana**...
-
-- What can I say?
-- Launch <*app name*>.
-- What time is it?
-- Show me the latest NBA scores.
-- Tell me a joke.
-
-If you're using *version 18362.x or earlier*, you can also use these commands:
-
-**Hey, Cortana**...
-
-- Increase the volume.
-- Decrease the brightness.
-- Shut down.
-- Restart.
-- Go to sleep.
-- Mute.
-- Move <*app name*> here (gaze at the spot that you want the app to move to).
-- Go to Start.
-- Take a picture.
-- Start recording. (Starts recording a video.)
-- Stop recording. (Stops recording a video.)
-- How much battery do I have left?
-
-Some Cortana features that you're used to from Windows on your PC or phone (for example, reminders and notifications) aren't supported in Microsoft HoloLens, and the Cortana experience may vary from one region to another.
-
-### Turn Cortana off
-
-Cortana is on the first time you use HoloLens when you enable speech. You can turn her off in Cortana's settings. In the **All apps** list, select **Cortana** > **Settings**. Then turn off Cortana can give you suggestions, ideas, reminders, alerts, and more.
-
-If Cortana isn't responding to "Hey Cortana," check that speech is enabled on Start and go to Cortana's settings and check to make sure she's on.
diff --git a/devices/hololens/hololens-diagnostic-logs.md b/devices/hololens/hololens-diagnostic-logs.md
deleted file mode 100644
index 212f936079..0000000000
--- a/devices/hololens/hololens-diagnostic-logs.md
+++ /dev/null
@@ -1,269 +0,0 @@
----
-title: Collect and use diagnostic information from HoloLens devices
-description:
-author: Teresa-Motiv
-ms.author: v-tea
-ms.date: 03/23/2020
-ms.prod: hololens
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.topic: article
-ms.custom:
-- CI 115131
-- CSSTroubleshooting
-audience: ITPro
-ms.localizationpriority: medium
-keywords:
-manager: jarrettr
-appliesto:
-- HoloLens (1st gen)
-- HoloLens 2
----
-
-# Collect and use diagnostic information from HoloLens devices
-
-HoloLens users and administrators can choose from among four different methods to collect diagnostic information from HoloLens:
-
-- Feedback Hub app
-- DiagnosticLog CSP
-- Settings app
-- Fallback diagnostics
-
-> [!IMPORTANT]
-> Device diagnostic logs contain personally identifiable information (PII), such as about what processes or applications the user starts during typical operations. When multiple users share a HoloLens device (for example, users sign in to the same device by using different Microsoft Azure Active Directory (AAD) accounts) the diagnostic logs may contain PII information that applies to multiple users. For more information, see [Microsoft Privacy statement](https://privacy.microsoft.com/privacystatement).
-
-The following table compares the four collection methods. The method names link to more detailed information in the sections that follow the table.
-
-|Method |Prerequisites |Data locations |Data access and use |Data retention |
-| --- | --- | --- | --- | --- |
-|[Feedback Hub](#feedback-hub) |Network and internet connection
Feedback Hub app
Permission to upload files to the Microsoft cloud |Microsoft cloud
HoloLens device (optional) |User requests assistance, agrees to the terms of use, and uploads the data
Microsoft employees view the data, as consistent with the terms of use |Data in the cloud is retained for the period that is defined by Next Generation Privacy (NGP). Then the data is deleted automatically.
Data on the device can be deleted at any time by a user who has **Device owner** or **Admin** permissions. |
-|[Settings Troubleshooter](#settings-troubleshooter) |Settings app |HoloLens device
Connected computer (optional) |The user stores the data, and only the user accesses the data (unless the user specifically shares the data with another user). |The data is retained until the user deletes it. |
-|[DiagnosticLog CSP](#diagnosticlog-csp) |Network connection
MDM environment that supports the DiagnosticLog CSP |Administrator configures storage locations |In the managed environment, the user implicitly consents to administrator access to the data.
Connected computer |The user stores the data, and only the user accesses the data (unless the user specifically shares the data with another user). |The data is retained until the user deletes it. |
-
-## Feedback Hub
-
-A HoloLens user can use the Microsoft Feedback Hub desktop app to send diagnostic information to Microsoft Support. For details and complete instructions, see [Give us feedback](hololens-feedback.md).
-
-> [!NOTE]
-> **Commercial or enterprise users:** If you use the Feedback Hub app to report a problem that relates to MDM, provisioning, or any other device management aspect, change the app category to **Enterprise Management** > **Device category**.
-
-### Prerequisites
-
-- The device is connected to a network.
-- The Feedback Hub app is available on the user's desktop computer, and the user can upload files to the Microsoft cloud.
-
-### Data locations, access, and retention
-
-By agreeing to the terms-of-use of the Feedback Hub, the user explicitly consents to the storage and usage of the data (as defined by that agreement).
-
-The Feedback Hub provides two places for the user to store diagnostic information:
-
-- **The Microsoft cloud**. Data that the user uploads by using the Feedback Hub app is stored for the number of days that is consistent with Next Generation Privacy (NGP) requirements. Microsoft employees can use an NGP-compliant viewer to access the information during this period.
- > [!NOTE]
- > These requirements apply to data in all Feedback Hub categories.
-
-- **The HoloLens device**. While filing a report in Feedback Hub, the user can select **Save a local copy of diagnostics and attachments created when giving feedback**. If the user selects this option, the Feedback Hub stores a copy of the diagnostic information on the HoloLens device. This information remains accessible to the user (or anyone that uses that account to sign in to HoloLens). To delete this information, a user must have **Device owner** or **Admin** permissions on the device. A user who has the appropriate permissions can sign in to the Feedback Hub, select **Settings** > **View diagnostics logs**, and delete the information.
-
-## Settings Troubleshooter
-
-A HoloLens user can use the Settings app on the device to troubleshoot problems and collect diagnostic information. To do this, follow these steps:
-
-1. Open the Settings app and select **Update & Security** > **Troubleshoot** page.
-1. Select the appropriate area, and select **Start**.
-1. Reproduce the issue.
-1. After you reproduce the issue, return to Settings and then select **Stop**.
-
-### Prerequisites
-
-- The Settings app is installed on the device and is available to the user.
-
-### Data locations, access, and retention
-
-Because the user starts the data collection, the user implicitly consents to the storage of the diagnostic information. Only the user, or anyone with whom that the user shares the data, can access the data.
-
-The diagnostic information is stored on the device. If the device is connected to the user's computer, the information also resides on the computer in the following file:
-
-> This PC\\\<*HoloLens device name*>\\Internal Storage\\Documents\\Trace\<*ddmmyyhhmmss*>.etl
-
-> [!NOTE]
-> In this file path and name, \<*HoloLens device name*> represents the name of the HoloLens device, and \<*ddmmyyhhmmss*> represents the date and time that the file was created.
-
-The diagnostic information remains in these locations until the user deletes it.
-
-## DiagnosticLog CSP
-
-In a Mobile Device Management (MDM) environment, the IT administrator can use the the [DiagnosticLog configuration service provider (CSP)](https://docs.microsoft.com/windows/client-management/mdm/diagnosticlog-csp) to configure diagnostic settings on enrolled HoloLens devices. The IT administrator can configure these settings to collect logs from enrolled devices.
-
-### Prerequisites
-
-- The device is connected to a network.
-- The device is enrolled in an MDM environment that supports the DiagnosticLog CSP.
-
-### Data locations, access, and retention
-
-Because the device is part of the managed environment, the user implicitly consents to administrative access to diagnostic information.
-
-The IT administrator uses the DiagnosticLog CSP to configure the data storage, retention, and access policies, including the policies that govern the following:
-
-- The cloud infrastructure that stores the diagnostic information.
-- The retention period for the diagnostic information.
-- Permissions that control access to the diagnostic information.
-
-## Fallback diagnostics
-
-While device telemetry usually provides an initial understanding of a problem report, some issues require a broader and deeper understanding of the device state. When you (as a user or an administrator) investigate such issues, diagnostic logs that reside on the device are more useful than the basic device telemetry.
-
-The fallback diagnostics process provides a way for you to gather diagnostic information if no other methods are available. Such scenarios include the following:
-
-- The network or network-based resources (such as the Feedback Hub, MDM, and so on) are not available.
-- The device is "stuck" or locked in a state in which usual troubleshooting capabilities (such as the Settings app) are not available. Such scenarios include the Out-of-Box-Experience (OOBE), kiosk mode, and a locked or "hung" user interface.
-
-> [!IMPORTANT]
-> - On HoloLens 2 devices, you can use fallback diagnostics under the following conditions only:
-> - During the Out-of-the-Box-Experience (OOBE) and when you select **Send Full Diagnostics Data**.
-> - If the environment's Group Policy enforces the **System\AllowTelemetry** policy value of **Full**.
-> - On HoloLens (1st gen) devices, you can use fallback diagnostics on HoloLens version 17763.316 or a later version. This version is the version that the Windows Device Recovery Tool restores when it resets the device.
-
-### How to use fallback diagnostics
-
-Before you start the fallback diagnostics process, make sure of the following:
-
-- The device is connected to a computer by using a USB cable.
-- The device is powered on.
-- The Power and Volume buttons on the device are functioning correctly.
-
-To collect fallback diagnostic information, follow these steps:
-
-1. On the device, press the Power and Volume Down buttons at the same time and then release them.
-1. Wait for few seconds while the device collects the data.
-
-### Data locations
-
-The device stores the data locally. You can access that information from the connected desktop computer at the following location:
-
-> This PC\\\<*HoloLens device name*>\\Internal Storage\\Documents
-
-For more information about the files that the fallback diagnostics process collects, see [What diagnostics files does the fallback diagnostics process collect?](#what-diagnostics-files-does-the-fallback-diagnostics-process-collect).
-
-### Data access, use, and retention
-
-Because you store the data yourself, only you have access to the data. If you choose to share the data with another user, you implicitly grant permission for that user to access or store the data.
-
-The data remains until you delete it.
-
-### Frequently asked questions about fallback diagnostics on HoloLens
-
-#### Does the device have to be enrolled with an MDM system?
-
-No.
-
-#### How can I use fallback diagnostics on HoloLens?
-
-Before you start the fallback diagnostics process, make sure of the following:
-
-- The device is connected to a computer by using a USB cable.
-- The device is powered on.
-- The Power and Volume buttons on the device are functioning correctly.
-
-To collect fallback diagnostic information, follow these steps:
-
-1. On the device, press the Power and Volume Down buttons at the same time and then release them.
-1. Wait for few seconds while the device collects the data.
-
-#### How would I know that data collection finished?
-
-The fallback diagnostics process does not have a user interface. On HoloLens 2, when the process starts to collect data, it creates a file that is named HololensDiagnostics.temp. When the process finishes, it removes the file.
-
-#### What diagnostics files does the fallback diagnostics process collect?
-
-The fallback diagnostics process collects one or more .zip files, depending on the version of HoloLens. The following table lists each of the possible .zip files, and the applicable versions of HoloLens.
-
-|File |Contents |HoloLens (1st gen) |HoloLens 2 10.0.18362+ |HoloLens 2 10.0.19041+ |
-| --- | --- | --- | --- | --- |
-|HololensDiagnostics.zip |Files for tracing sessions that ran on the device.
Diagnostic information that's specific to Hololens. |✔️ |✔️ |✔️ |
-|DeviceEnrollmentDiagnostics.zip |Information that's related to MDM, device enrollment, CSPs, and policies. | |✔️ |✔️ |
-|AutoPilotDiagnostics.zip |Information that's related to autopilot and licensing.| | |✔️ |
-|TPMDiagnostics.zip |Information that's related to the trusted platform module (TPM) on the device | | |✔️ |
-
-> [!NOTE]
-> Starting on May 2, 2019, the fallback diagnostics process collects EventLog*.etl files only if the signed-in user is the device owner. This is because these files may contain PII data. Such data is accessible to device owners only. This behavior matches the behavior of Windows desktop computers, where administrators have access to event log files but other users do not.
-
-**Sample diagnostic content for HoloLens (1st gen)**
-
-HololensDiagnostics.zip contains files such as the following:
-
-- AuthLogon.etl
-- EventLog-HupRe.etl.001
-- FirstExperience.etl.001
-- HetLog.etl
-- HoloInput.etl.001
-- HoloShell.etl.001
-- WiFi.etl.001
-
-**Sample diagnostic content for HoloLens 2 10.0.18362+**
-
-HololensDiagnostics.zip contains files such as the following:
-
-- EventLog-Application.etl.001*
-- EventLog-System.etl.001*
-- AuthLogon.etl
-- EventLog-HupRe.etl.001
-- FirstExperience.etl.001
-- HetLog.etl
-- HoloInput.etl.001
-- HoloShell.etl.001
-- WiFi.etl.001
-- CSPsAndPolicies.etl.001
-- RadioMgr.etl
-- WiFiDriverIHVSession.etl
-
-DeviceEnrollmentDiagnostics.zip contains files such as the following:
-
-- MDMDiagHtmlReport.html
-- MdmDiagLogMetadata.json
-- MDMDiagReport.xml
-- MdmDiagReport_RegistryDump.reg
-- MdmLogCollectorFootPrint.txt
-
-**Sample diagnostic content for HoloLens 2 10.0.19041+**
-
-HololensDiagnostics.zip contains files such as the following:
-
-- EventLog-Application.etl.001*
-- EventLog-System.etl.001*
-- AuthLogon.etl
-- EventLog-HupRe.etl.001
-- FirstExperience.etl.001
-- HetLog.etl
-- HoloInput.etl.001
-- HoloShell.etl.001
-- WiFi.etl.001
-- CSPsAndPolicies.etl.001
-- RadioMgr.etl
-- WiFiDriverIHVSession.etl
-- DisplayDiagnosticData.json
-- HUP dumps
-
-DeviceEnrollmentDiagnostics.zip contains files such as the following:
-
-- MDMDiagHtmlReport.html
-- MdmDiagLogMetadata.json
-- MDMDiagReport.xml
-- MdmDiagReport_RegistryDump.reg
-- MdmLogCollectorFootPrint.txt
-
-AutoPilotDiagnostics.zip contains files such as the following:
-
-- DeviceHash_HoloLens-U5603.csv
-- LicensingDiag.cab
-- LicensingDiag_Output.txt
-- TpmHliInfo_Output.txt
-- DiagnosticLogCSP_Collector_DeviceEnrollment_\*.etl
-- DiagnosticLogCSP_Collector_Autopilot_*.etl
-
-TPMDiagnostics.zip contains files such as the following:
-
-- CertReq_enrollaik_Output.txt
-- CertUtil_tpminfo_Output.txt
-- TPM\*.etl
diff --git a/devices/hololens/hololens-encryption.md b/devices/hololens/hololens-encryption.md
deleted file mode 100644
index 6b2cfb74bc..0000000000
--- a/devices/hololens/hololens-encryption.md
+++ /dev/null
@@ -1,99 +0,0 @@
----
-title: Enable Bitlocker encryption for HoloLens (HoloLens)
-description: Enable Bitlocker device encryption to protect files stored on the HoloLens
-ms.prod: hololens
-ms.mktglfcycl: manage
-ms.sitesec: library
-author: dansimp
-ms.author: dansimp
-ms.topic: article
-ms.localizationpriority: medium
-ms.date: 01/26/2019
-ms.reviewer:
-manager: laurawi
-appliesto:
-- HoloLens (1st gen)
----
-
-# Enable encryption for HoloLens
-
-HoloLens (1st gen) and HoloLens 2 both support device encryption using BitLocker, however, BitLocker is always enabled on HoloLens 2.
-
-This article will help you enable and manage BitLocker on HoloLens (1st gen).
-
-On HoloLens (1st gen) you can enable BitLocker device encryption manually or using mobile device management (MDM). Follow these instructions to enable [BitLocker device encryption](https://docs.microsoft.com/windows/security/information-protection/bitlocker/bitlocker-device-encryption-overview-windows-10#bitlocker-device-encryption) to protect files and information stored on the HoloLens. Device encryption helps protect your data using the AES-CBC 128 encryption method, which is equivalent to [EncryptionMethodByDriveType method 3](https://docs.microsoft.com/windows/client-management/mdm/bitlocker-csp#encryptionmethodbydrivetype) in the BitLocker configuration service provider (CSP). Personnel who have the correct encryption key (such as a password) can decrypt it or perform a data recovery.
-
-## Enable device encryption using MDM
-
-You can use your Mobile Device Management (MDM) provider to apply a policy that requires device encryption. The policy to use is the [Security/RequireDeviceEncryption setting](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-security#security-requiredeviceencryption) in the Policy CSP.
-
-[See instructions for enabling device encryption using Microsoft Intune.](https://docs.microsoft.com/intune/compliance-policy-create-windows#windows-holographic-for-business)
-
-For other MDM tools, see your MDM provider's documentation for instructions. If your MDM provider requires custom URI for device encryption, use the following configuration:
-
-- **Name**: a name of your choice
-- **Description**: optional
-- **OMA-URI**: `./Vendor/MSFT/Policy/Config/Security/RequireDeviceEncryption`
-- **Data type**: integer
-- **Value**: `1`
-
-## Enable device encryption using a provisioning package
-
-Provisioning packages are files created by the Windows Configuration Designer tool that apply a specified configuration to a device.
-
-### Create a provisioning package that upgrades the Windows Holographic edition and enables encryption
-
-1. [Create a provisioning package for HoloLens.](hololens-provisioning.md)
-1. Go to **Runtime settings** > **Policies** > **Security**, and select **RequireDeviceEncryption**.
-
- 
-
-1. Find the XML license file that was provided when you purchased the Commercial Suite.
-
-1. Browse to and select the XML license file that was provided when you purchased the Commercial Suite.
- > [!NOTE]
- > You can configure [additional settings in the provisioning package](hololens-provisioning.md).
-
-1. On the **File** menu, click **Save**.
-
-1. Read the warning explaining that project files may contain sensitive information and click **OK**.
-
- > [!IMPORTANT]
- > When you build a provisioning package, you may include sensitive information in the project files and provisioning package (.ppkg) file. Although you have the option to encrypt the .ppkg file, project files are not encrypted. You should store the project files in a secure location and delete the project files when no longer needed.
-
-1. On the **Export** menu, click **Provisioning package**.
-1. Change **Owner** to **IT Admin**, which will set the precedence of this provisioning package higher than provisioning packages applied to this device from other sources, and then select **Next**.
-1. Set a value for **Package Version**.
-
- > [!TIP]
- > You can make changes to existing packages and change the version number to update previously applied packages.
-
-1. On the **Select security details for the provisioning package**, click **Next**.
-1. Click **Next** to specify the output location where you want the provisioning package to go once it's built. By default, Windows ICD uses the project folder as the output location.
-
- Optionally, you can click Browse to change the default output location.
-
-1. Click **Next**.
-1. Click **Build** to start building the package. The project information is displayed in the build page and the progress bar indicates the build status.
-1. When the build completes, click **Finish**.
-
-### Apply the provisioning package to HoloLens
-
-1. Connect the device via USB to a PC and start the device, but do not continue past the **fit** page of the initial setup experience (the first page with the blue box).
-1. Briefly press and release the **Volume Down** and **Power** buttons simultaneously.
-1. HoloLens will show up as a device in File Explorer on the PC.
-1. In File Explorer, drag and drop the provisioning package (.ppkg) onto the device storage.
-1. Briefly press and release the **Volume Down** and **Power** buttons simultaneously again while on the **fit** page.
-1. The device will ask you if you trust the package and would like to apply it. Confirm that you trust the package.
-1. You will see whether the package was applied successfully or not. If it failed, you can fix your package and try again. If it succeeded, proceed with device setup.
-
-> [!NOTE]
-> If the device was purchased before August 2016, you will need to sign into the device with a Microsoft account, get the latest OS update, and then reset the OS in order to apply the provisioning package.
-
-## Verify device encryption
-
-Encryption is silent on HoloLens. To verify the device encryption status:
-
-- On HoloLens, go to **Settings** > **System** > **About**. **BitLocker** is **enabled** if the device is encrypted.
-
- 
diff --git a/devices/hololens/hololens-enroll-mdm.md b/devices/hololens/hololens-enroll-mdm.md
deleted file mode 100644
index 0e557e9c50..0000000000
--- a/devices/hololens/hololens-enroll-mdm.md
+++ /dev/null
@@ -1,48 +0,0 @@
----
-title: Enroll HoloLens in MDM
-description: Enroll HoloLens in mobile device management (MDM) for easier management of multiple devices.
-ms.prod: hololens
-ms.sitesec: library
-ms.assetid: 2a9b3fca-8370-44ec-8b57-fb98b8d317b0
-author: scooley
-ms.author: scooley
-ms.topic: article
-ms.localizationpriority: medium
-ms.date: 07/15/2019
-ms.reviewer:
-manager: laurawi
-appliesto:
-- HoloLens (1st gen)
-- HoloLens 2
----
-
-# Enroll HoloLens in MDM
-
-You can manage multiple Microsoft HoloLens devices simultaneously using solutions like [Microsoft Intune](https://docs.microsoft.com/intune/windows-holographic-for-business). You will be able to manage settings, select apps to install and set security configurations tailored to your organization's need. See [Manage devices running Windows Holographic with Microsoft Intune](https://docs.microsoft.com/intune/windows-holographic-for-business), the [configuration service providers (CSPs) that are supported in Windows Holographic](https://msdn.microsoft.com/windows/hardware/commercialize/customize/mdm/configuration-service-provider-reference#hololens), and the [policies supported by Windows Holographic for Business](https://msdn.microsoft.com/windows/hardware/commercialize/customize/mdm/policy-configuration-service-provider#hololenspolicies).
-
-> [!NOTE]
-> Mobile device management (MDM), including the VPN, Bitlocker, and kiosk mode features, is only available when you [upgrade to Windows Holographic for Business](hololens1-upgrade-enterprise.md).
-
-## Requirements
-
- Your organization will need to have Mobile Device Management (MDM) set up in order to manage HoloLens devices. Your MDM provider can be Microsoft Intune or a 3rd party provider that uses Microsoft MDM APIs.
-
-## Auto-enrollment in MDM
-
-If your organization uses Azure Active Directory (Azure AD) and an MDM solution that accepts an AAD token for authentication (currently, only supported in Microsoft Intune and AirWatch), your IT admin can configure Azure AD to automatically allow MDM enrollment after the user signs in with their Azure AD account. [Learn how to configure Azure AD enrollment.](https://docs.microsoft.com/mem/intune/enrollment/windows-enroll#enable-windows-10-automatic-enrollment)
-
-When auto-enrollment is enabled, no additional manual enrollment is needed. When the user signs in with an Azure AD account, the device is enrolled in MDM after completing the first-run experience.
-
-## Enroll through Settings app
-
- When the device is not enrolled in MDM during the first-run experience, the user can manually enroll the device with the organization's MDM server using the Settings app.
-
-1. Go to **Settings** > **Accounts** > **Work access**.
-1. Select **Enroll into device management** and enter your organizational account. You will be redirected to your organization's sign in page.
-1. Upon successful authentication to the MDM server, a success message is shown.
-
-Your device is now enrolled with your MDM server. The device will need to restart to acquire policies, certificates, and apps. The Settings app will now reflect that the device is enrolled in device management.
-
-## Unenroll HoloLens from Intune
-
-You cannot [unenroll](https://docs.microsoft.com/intune-user-help/unenroll-your-device-from-intune-windows) HoloLens from Intune remotely. If the administrator unenrolls the device using MDM, the device will age out of the Intune dashboard.
diff --git a/devices/hololens/hololens-environment-considerations.md b/devices/hololens/hololens-environment-considerations.md
deleted file mode 100644
index bdd500b298..0000000000
--- a/devices/hololens/hololens-environment-considerations.md
+++ /dev/null
@@ -1,121 +0,0 @@
----
-title: Environment considerations for HoloLens
-description: Get the best possible experience using HoloLens when you optimize the device for your eyes and environment. Many different environmental factors are fused together to enable tracking, but as a Mixed Reality developer, there are several factors you can keep in mind to tune a space for better holograms.
-keywords: holographic frame, field of view, fov, calibration, spaces, environment, how-to
-author: dorreneb
-ms.author: dobrown
-manager: jarrettr
-ms.date: 8/29/2019
-ms.prod: hololens
-ms.topic: article
-audience: ITPro
-ms.localizationpriority: high
-appliesto:
-- HoloLens (1st gen)
-- HoloLens 2
----
-
-# Environment considerations for HoloLens
-
-HoloLens blends the holographic with the "real" world, placing holograms in your surroundings. A holographic app window "hangs" on the wall, a holographic ballerina spins on the tabletop, bunny ears sit on top of your unwitting friend’s head. When you’re using an immersive game or app, the holographic world will spread to fill your surroundings but you’ll still be able to see and move around the space.
-
-The holograms you place will stay where you’ve put them, even if you turn off your device.
-
-## Setting up an environment
-
-HoloLens devices know how to place stable and accurate holograms by *tracking* users in a space. Without proper tracking, the device does not understand the environment or the user within it so holograms can appear in the wrong places, not appear in the same spot every time, or not appear at all. The data used to track users is represented in the *spatial map*.
-
-Tracking performance is heavily influenced by the environment the user is in, and tuning an environment to induce stable and consistent tracking is an art rather than a science. Many different environmental factors are fused together to enable tracking, but as a Mixed Reality developer, there are several factors you can keep in mind to tune a space for better tracking.
-
-### Lighting
-
-Windows Mixed Reality uses visual light to track the user's location. When an environment is too bright, the cameras can get saturated, and nothing is seen. If the environment is too dark, the cameras cannot pick up enough information, and nothing is seen. Lighting should be even and sufficiently bright that a human can see without effort, but not so bright that the light is painful to look at.
-
-Areas where there are points of bright light in an overall dim area are also problematic, as the camera has to adjust when moving in and out of bright spaces. This can cause the device to "get lost" and think that the change in light equates to a change in location. Stable light levels in an area will lead to better tracking.
-
-Any outdoor lighting can also cause instability in the tracker, as the sun may vary considerably over time. For example, tracking in the same space in the summer vs. winter can produce drastically different results, as the secondhand light outside may be higher at different times of year.
-
-If you have a luxmeter, a steady 500-1000 lux is a good place to start.
-
-#### Types of lighting
-
-Different types of light in a space can also influence tracking. Light bulbs pulse with the AC electricity running through it - if the AC frequency is 50Hz, then the light pulses at 50Hz. For a human, this pulsing is not noticed. However, HoloLens' 30fps camera sees these changes - some frames will be well-lit, some will be poorly lit, and some will be over-exposed as the camera tries to compensate for light pulses.
-
-In the USA, electricity frequency standard is 60Hz, so light bulb pulses are harmonized with HoloLens' framerate - 60Hz pulses align with HoloLens' 30 FPS framerate. However, many countries have an AC frequency standard of 50Hz, which means some HoloLens frames will be taken during pulses, and others will not. In particular, fluorescent lighting in Europe has been known to cause issues.
-
-There are a few things you can try to resolve flickering issues. Temperature, bulb age, and warm-up cycles are common causes of fluorescent flickering and replacing bulbs may help. Tightening bulbs and making sure current draws are constant can also help.
-
-### Items in a space
-
-HoloLens uses unique environmental landmarks, also known as *features*, to locate itself in a space.
-
-A device can almost never track in a feature-poor area, as the device has no way of knowing where in space it is. Adding features to the walls of a space is usually a good way to improve tracking. Posters, symbols taped to a wall, plants, unique objects, or other similar items all help. A messy desk is a good example of an environment that leads to good tracking - there are a lot of different features in a single area.
-
-Additionally, use unique features in the same space. The same poster repeated multiple times over a wall, for example, will cause device confusion as the HoloLens won't know which of the repetitive posters it is looking at. One common way of adding unique features is to use lines of masking tape to create unique, non-repetitive patterns along the walls and floor of a space.
-
-A good question to ask yourself is: if you saw just a small amount of the scene, could you uniquely locate yourself in the space? If not, it's likely the device will have problems tracking as well.
-
-#### Wormholes
-
-If you have two areas or regions that look the same, the tracker may think they are the same. This results in the device tricking itself into thinking it is somewhere else. We call these types of repetitive areas *wormholes*.
-
-To prevent wormholes, try to prevent identical areas in the same space. Identical areas can sometimes include factory stations, windows on a building, server racks, or work stations. Labelling areas or adding unique features to each similar-looking areas can help mitigate wormholes.
-
-### Movement in a space
-
-If your environment is constantly shifting and changing, the device has no stable features to locate against.
-
-The more moving objects that are in a space, including people, the easier it is to lose tracking. Moving conveyor belts, items in different states of construction, and lots of people in a space have all been known to cause tracking issues.
-
-The HoloLens can quickly adapt to these changes, but only when that area is clearly visible to the device. Areas that are not seen as frequently may lag behind reality, which can cause errors in the spatial map. For example, a user scans a friend and then turns around while the friend leaves the room. A 'ghost' representation of the friend will persist in the spatial mapping data until the user re-scans the now empty space.
-
-### Proximity of the user to items in the space
-
-Similarly to how humans cannot focus well on objects close to the eyes, HoloLens struggles when objects are close to it's cameras. If an object is too close to be seen with both cameras, or if an object is blocking one camera, the device will have far more issues with tracking against the object.
-
-The cameras can see no closer than 15cm from an object.
-
-### Surfaces in a space
-
-Strongly reflective surfaces will likely look different depending on the angle, which affects tracking. Think of a brand new car - when you move around it, light reflects and you see different objects in the surface as you move. To the tracker, the different objects reflected in the surface represent a changing environment, and the device loses tracking.
-
-Less shiny objects are easier to track against.
-
-### Wi-Fi fingerprint considerations
-
-As long as Wi-Fi is enabled, map data will be correlated with a Wi-Fi fingerprint, even when not connected to an actual WiFi network/router. Without Wi-Fi info, the space and holograms may be slightly slower to recognize. If the Wi-Fi signals change significantly, the device may think it is in a different space altogether.
-
-Network identification (such as SSID or MAC address) is not sent to Microsoft, and all Wi-Fi references are kept local on the HoloLens.
-
-## Mapping new spaces
-
-When you enter a new space (or load an existing one), you’ll see a mesh graphic spreading over the space. This means your device is mapping your surroundings. While a HoloLens will learn a space over time, there are tips and tricks to map spaces.
-
-## Environment management
-
-There are two settings which enable users to “clean up” holograms and cause HoloLens to “forget" a space. They exist in **Holograms and environments** in the settings app, with the second setting also appearing under **Privacy** in the settings app.
-
-1. **Delete nearby holograms**. When you select this setting, HoloLens will erase all anchored holograms and all stored map data for the “current space” where the device is located. A new map section would be created and stored in the database for that location once holograms are again placed in that same space.
-
-1. **Delete all holograms**.By selecting this setting, HoloLens will erase ALL map data and anchored holograms in the entire databases of spaces. No holograms will be rediscovered and any holograms need to be newly placed to again store map sections in the database.
-
-## Hologram quality
-
-Holograms can be placed throughout your environment—high, low, and all around you—but you’ll see them through a [holographic frame](https://docs.microsoft.com/windows/mixed-reality/holographic-frame) that sits in front of your eyes. To get the best view, make sure to adjust your device so you can see the entire frame. And don’t hesitate to walk around your environment and explore!
-
-For your [holograms](https://docs.microsoft.com/windows/mixed-reality/hologram) to look crisp, clear, and stable, your HoloLens needs to be calibrated just for you. When you first set up your HoloLens, you’ll be guided through this process. Later on, if holograms don’t look right or you’re seeing a lot of errors, you can make adjustments.
-
-If you are having trouble mapping spaces, try deleting nearby holograms and remapping the space.
-
-### Calibration
-
-If your holograms look jittery or shaky, or if you’re having trouble placing holograms, the first thing to try is the [Calibration app](hololens-calibration.md). This app can also help if you’re experiencing any discomfort while using your HoloLens.
-
-To get to the Calibration app, go to **Settings** > **System** > **Utilities**. Select **Open Calibration** and follow the instructions.
-
-If someone else is going to be using your HoloLens, they should run the Calibration app first so the device is set up properly for them.
-
-## See also
-
-- [Spatial mapping design](https://docs.microsoft.com/windows/mixed-reality/spatial-mapping)
-- [Holograms](https://docs.microsoft.com/windows/mixed-reality/hologram)
diff --git a/devices/hololens/hololens-faq-security.md b/devices/hololens/hololens-faq-security.md
deleted file mode 100644
index 85f66c8318..0000000000
--- a/devices/hololens/hololens-faq-security.md
+++ /dev/null
@@ -1,125 +0,0 @@
----
-title: Frequently Asked Security Questions
-description: security questions frequently asked about the hololens
-ms.assetid: bd55ecd1-697a-4b09-8274-48d1499fcb0b
-author: pawinfie
-ms.author: pawinfie
-ms.date: 02/19/2020
-keywords: hololens, Windows Mixed Reality, security
-ms.prod: hololens
-ms.sitesec: library
-ms.topic: article
-audience: ITPro
-ms.localizationpriority: high
-ms.custom:
-- CI 111456
-- CSSTroubleshooting
-manager: bradke
-appliesto:
-- HoloLens 1 (1st gen)
-- HoloLens 2
----
-
-# Frequently asked questions about HoloLens security
-
-## HoloLens (1st gen) Security Questions
-
-1. **What type of wireless is used?**
- 1. 802.11ac and Bluetooth 4.1 LE
-1. **What type of architecture is incorporated? For example: point to point, mesh or something else?**
- 1. Wi-Fi can be used in infrastructure mode to communicate with other wireless access points.
- 1. Bluetooth can be used to talk peer to peer between multiple HoloLens if the customers application supports it or to other Bluetooth devices.
-1. **What is FCC ID?**
- 1. C3K1688
-1. **What frequency range and channels does the device operate on and is it configurable?**
- 1. Wi-Fi: The frequency range is not user configurable and depends on the country of use. In the US Wi-Fi uses both 2.4 GHz (1-11) channels and 5 GHz (36-64, 100-165) channels.
- 1. Bluetooth: Bluetooth uses the standard 2.4-2.48 GHz range.
-1. **Can the device blacklist or white list specific frequencies?**
- 1. This is not controllable by the user/device
-1. **What is the power level for both transmit and receive? Is it adjustable? What is the range of operation?**
- 1. Our emissions testing standards can be found [here](https://fccid.io/C3K1688). Range of operation is highly dependent on the access point and environment - but is roughly equivalent to other high-quality phones, tablets, or PCs.
-1. **What is the duty cycle/lifetime for normal operation?**
- 1. 2-3hrs of active use and up to 2 weeks of standby time
- 1. Battery lifetime is unavailable.
-1. **What is transmit and receive behavior when a tool is not in range?**
- 1. HoloLens transmit/receive follows the standard Wi-Fi/Bluetooth pattern. At the edge of its range, you'll probably notice input getting choppy until it fully disconnects, but after you get back in range it should quickly reconnect.
-1. **What is deployment density per square foot?**
- 1. This is dependent on your network infrastructure.
-1. **Can device use the infrastructure as a client?**
- 1. Yes
-1. **What protocol is used?**
- 1. HoloLens does not use any proprietary protocols
-1. **OS update frequency – What is the frequency of OS updates for the HL? Is there a set schedule? Does Microsoft release security patches as needed, etc.**
- 1. Microsoft does provide OS updates to HoloLens exactly the same way it is done for Windows 10. There are normally two major updates per year, one in spring, one in fall. As HoloLens is a Windows device, the update concept is the same as with any other Windows device. Microsoft releases Security patches as needed and follows the same concept as done on any other Windows device.
-1. **OS hardening – What options are there to harden the OS? Can we remove or shutdown unnecessary apps or services?**
- 1. HoloLens behaves like a smartphone. It is comparable to other modern Windows devices. HoloLens can be managed by either Microsoft Intune or other Modern Device Management Solutions, like MobileIron, Airwatch, or Soti. There are Policies you can set in these Management Systems to put Security policies on the device and in order to harden the device. There is also the option in deleting any unnecessary applications if wanted.
-1. **How will software applications be managed and updated? What control do we have to define what apps are loaded and app update process for apps that are living in the Microsoft store?**
- 1. HoloLens gets software applications only through the Windows store. Only Appx Application Packages can be installed, which are developed for the Use of HoloLens. You can see this in the Microsoft Store with a little logo next to the application which shows the HoloLens device. Any control that you have over the management of Store applications also applies to HoloLens. You can use the concept of the official store or the store for business. Apps can either be side-loaded (manual process to load an app on a Windows device) or can be managed through an MDM so that apps are automatically pulled from the store when needed.
-1. **What is the frequency of updates to apps in the store for HoloLens?**
- 1. As we follow the same concept of the Microsoft Store and pull apps from there, the update cycle is determined by the developer of the Application. All management options that you have to control the update mechanism in the store apply to HoloLens as well.
-1. **Is there a secure boot capability for the HoloLens?**
- 1. Yes
-1. **Is there an ability to disable or disconnect peripheral support from the device?**
- 1. Yes
-1. **Is there an ability to control or disable the use of ports on the device?**
- 1. The HoloLens only contains 2 ports (one for headphones and one for charging or connecting to PCs). There is not ability to disable the port due to functionality and recovery reasons.
-1. **Antivirus, end point detection, IPS, app control whitelist – Any ability to run antivirus, end point detection, IPS, app control whitelist, etc.**
- 1. Windows Holographic for Business (commercial suite) does support Windows Defender Smart Screen. If an antivirus company were to create and publish their app to the Universal Windows Platform, it could be downloaded on HoloLens. At present, no companies have done this for HoloLens.
- 1. Whitelisting apps is possible by using the Microsoft Enterprise Store, where you can choose only what specific apps can be downloaded. Also, through MDM you can lock what specific apps can be run or even seen on the device.
-1. **Can we quarantine the device from prod network until we update the device if it has been offline for an extended period of time? Ex. Device has been sitting in a drawer not powered up for a period (6 months) and has not received any updates, patches, etc. When it tries to come on the network can we flag it and say you must update on another network prior to being complaint to join the network.**
- 1. This is something that can be managed on the infrastructure level by either an MDM or an on-prem server. The device can be flagged as not compliant if it does not meet a specified Update version.
-1. **Does Microsoft include any back doors or access to services that allows Microsoft to connect to the device for screen sharing or remote support at will?**
- 1. No
-1. **When a PKI cert is being generated for trusted communication, we want the cert to be generated on the device so that we know it's only on that device, unique to that device, and can't be exported or used to impersonate the device. Is this true on HoloLens? If not is there a potential mitigation?**
- 1. CSR for SCEP is generated on the device itself. Intune and the on premise SCEP connector help secure the requests themselves by adding and verifying a challenge string that's sent to the client.
- 1. Since HoloLens (1st Gen and 2nd Gen) have a TPM module, these certs would be stored in the TPM module, and are unable to be extracted. Additionally, even if it could be extracted, the challenge strings couldn't be verified on a different device, rendering the certs/key unusable on different devices.
-
-## HoloLens 2nd Gen Security Questions
-
-1. **What type of wireless is used?**
- 1. 802.11ac and Bluetooth 5.0
-1. **What type of architecture is incorporated? For example: point to point, mesh or something else?**
- 1. Wi-Fi can be used in infrastructure mode to communicate with other wireless access points.
- 1. Bluetooth can be used to talk peer to peer between multiple HoloLens if the customers application supports it or to other Bluetooth devices.
-1. **What is FCC ID?**
- 1. C3K1855
-1. **What frequency range and channels does the device operate on and is it configurable?**
- 1. Wi-Fi: The frequency range is not user configurable and depends on the country of use. In the US Wi-Fi uses both 2.4 GHz (1-11) channels and 5 GHz (36-64, 100-165) channels.
-1. **Can the device blacklist or white list specific frequencies?**
- 1. This is not controllable by the user/device
-1. **What is the power level for both transmit and receive? Is it adjustable? What is the range of operation?**
- 1. Wireless power levels depend on the channel of operation. Devices are calibrated to perform at the highest power levels allowed based on the region's regulatory rules.
-1. **What is the duty cycle/lifetime for normal operation?**
- 1. *Currently unavailable.*
-1. **What is transmit and receive behavior when a tool is not in range?**
- 1. HoloLens transmit/receive follows the standard Wi-Fi/Bluetooth pattern. At the edge of its range, you'll probably notice input getting choppy until it fully disconnects, but after you get back in range it should quickly reconnect.
-1. **What is deployment density per square foot?**
- 1. This is dependent on your network infrastructure.
-1. **Can device use the infrastructure as a client?**
- 1. Yes
-1. **What protocol is used?**
- 1. HoloLens does not use any proprietary protocols
-1. **OS update frequency – What is the frequency of OS updates for the HL? Is there a set schedule? Does Microsoft release security patches as needed, etc.**
- 1. Microsoft does provide OS updates to HoloLens exactly the same way it is done for Windows 10. There are normally two major updates per year, one in spring, one in fall. As HoloLens is a Windows device, the update concept is the same as with any other Windows device. Microsoft releases Security patches as needed and follows the same concept as done on any other Windows device.
-1. **OS hardening – What options are there to harden the OS? Can we remove or shutdown unnecessary apps or services?**
- 1. HoloLens behaves like a smartphone. It is comparable to other modern Windows devices. HoloLens can be managed by either Microsoft Intune or other Modern Device Management Solutions, like MobileIron, Airwatch, or Soti. There are Policies you can set in these Management Systems to put Security policies on the device and in order to harden the device. There is also the option in deleting any unnecessary applications if wanted.
-1. **How will software applications be managed and updated? What control do we have to define what apps are loaded and app update process for apps that are living in the Microsoft store?**
- 1. HoloLens gets software applications only through the Windows store. Only Appx Application Packages can be installed, which are developed for the Use of HoloLens. You can see this in the Microsoft Store with a little logo next to the application which shows the HoloLens device. Any control that you have over the management of Store applications also applies to HoloLens. You can use the concept of the official store or the store for business. Apps can either be side-loaded (manual process to load an app on a Windows device) or can be managed through an MDM so that apps are automatically pulled from the store when needed.
-1. **What is the frequency of updates to apps in the store for HoloLens?**
- 1. As we follow the same concept of the Microsoft Store and pull apps from there, the update cycle is determined by the developer of the Application. All management options that you have to control the update mechanism in the store apply to HoloLens as well.
-1. **Is there a secure boot capability for the HoloLens?**
- 1. Yes
-1. **Is there an ability to disable or disconnect peripheral support from the device?**
- 1. Yes
-1. **Is there an ability to control or disable the use of ports on the device?**
- 1. The HoloLens only contains 2 ports (one for headphones and one for charging or connecting to PCs). There is not ability to disable the port due to functionality and recovery reasons.
-1. **Antivirus, end point detection, IPS, app control whitelist – Any ability to run antivirus, end point detection, IPS, app control whitelist, etc.**
- 1. HoloLens 2nd Gen supports Windows Defender Smart Screen. If an antivirus company were to create and publish their app to the Universal Windows Platform, it could be downloaded on HoloLens. At present, no companies have done this for HoloLens.
- 1. Whitelisting apps is possible by using the Microsoft Enterprise Store, where you can choose only what specific apps can be downloaded. Also, through MDM you can lock what specific apps can be run or even seen on the device.
-1. **Can we quarantine the device from prod network until we update the device if it has been offline for an extended period of time? Ex. Device has been sitting in a drawer not powered up for a period (6 months) and has not received any updates, patches, etc. When it tries to come on the network can we flag it and say you must update on another network prior to being complaint to join the network.**
- 1. This is something that can be managed on the infrastructure level by either an MDM or an on-prem server. The device can be flagged as not compliant if it does not meet a specified Update version.
-1. **Does Microsoft include any back doors or access to services that allows Microsoft to connect to the device for screen sharing or remote support at will?**
- 1. No
-1. **When a PKI cert is being generated for trusted communication, we want the cert to be generated on the device so that we know it's only on that device, unique to that device, and can't be exported or used to impersonate the device. Is this true on HoloLens? If not is there a potential mitigation?**
- 1. CSR for SCEP is generated on the device itself. Intune and the on premise SCEP connector help secure the requests themselves by adding and verifying a challenge string that's sent to the client.
- 1. Since HoloLens (1st Gen and 2nd Gen) have a TPM module, these certs would be stored in the TPM module, and are unable to be extracted. Additionally, even if it could be extracted, the challenge strings couldn't be verified on a different device, rendering the certs/key unusable on different devices.
diff --git a/devices/hololens/hololens-feedback.md b/devices/hololens/hololens-feedback.md
deleted file mode 100644
index 3199517a90..0000000000
--- a/devices/hololens/hololens-feedback.md
+++ /dev/null
@@ -1,82 +0,0 @@
----
-title: Give us feedback
-description: Create actionable feedback for HoloLens and Windows Mixed Reality developers by using the Feedback Hub.
-ms.assetid: b9b24c72-ff86-44a9-b30d-dd76c49479a9
-author: mattzmsft
-ms.author: mazeller
-ms.date: 09/13/2019
-ms.prod: hololens
-ms.topic: article
-keywords: feedback, bug, issue, error, troubleshoot, help
-manager: jarrettr
-ms.localizationpriority: medium
-appliesto:
-- HoloLens (1st gen)
-- HoloLens 2
----
-
-# Give us feedback
-
-Use the Feedback Hub to tell us which features you love, which features you could do without, or when something could be better.
-
-## Feedback for Windows Mixed Reality immersive headset on PC
-
-> [!IMPORTANT]
-> Before you report an issue, make sure that your environment meets the following requirements so that you can successfully upload logs and other information:
->
-> - Have a minimum of 3GB free disk space available on the main drive of the device.
-> - To upload cabs or other large files, connect to a non-metered network.
-
-1. Make sure that you have the immersive headset connected to your PC, and then on the desktop, select **Feedback Hub**.
-1. In the left pane, select **Feedback**.
- 
-1. To enter new feedback, select **Add new feedback**.
- 
-1. To make feedback actionable, in **What kind of feedback is this?** select **Problem**.
-1. In **Summarize your issue**, enter a meaningful title for your feedback.
-1. In **Give us more detail**, provide details and repro steps.
- 
-
- As the top category, select **Mixed Reality**. Then select an applicable subcategory, as explained in the following table:
-
- |Subcategory |Description |
- |----------|----------|
- | Apps | Issues about a specific application. |
- | Developer | Issues about authoring or running an app for Mixed Reality. |
- | Device | Issues about the head-mounted device (HMD) itself. |
- | Home experience | Issues about your VR environment and your interactions with the your mixed reality home. |
- | Input | Issues about input methods, such as motion controllers, speech, gamepad, or mouse and keyboard. |
- | Set up | Anything that is preventing you from setting up the device. |
- | All other issues | Anything else. |
-
-1. If possible, add traces or video to your feedback to help us identify and fix the issue more quickly. To do this, follow these steps:
- 1. To start collecting traces, select **Start capture**. The app starts collecting traces and a video capture of your mixed reality scenario.
-
- 
- 1. Do not close the Feedback Hub app, but switch to the scenario that produces the issue. Run through the scenario to produce the circumstances that you have described.
- 1. After you finish your scenario, go back to the Feedback Hub app and select **Stop capture**. The app stops collecting information, stores the information in a file, and attaches the file to your feedback.
-1. Select **Submit**.
- 
- The Thank You page indicates that your feedback has been successfully submitted.
- 
-
-To easily direct other people (such as co-workers, Microsoft staff, [forum](https://forums.hololens.com/) readers et al) to the issue, go to **Feedback** > **My Feedback**, select the issue, select **Share**. This action provides a shortened URL that you can give to others so that they can upvote or escalate your issue.
-
-## Feedback for HoloLens
-
-1. Use the **bloom** gesture to open the **Start** menu, and then select **Feedback Hub**.
-
- 
-1. Place the app in your environment and then select the app to launch it.
-1. To see if someone else has given similar feedback, in the Feedback search box, enter a few keywords about the topic.
-
- 
-1. If you find similar feedback, select it, add any details, then select **Upvote**.
-
- 
-1. If you don’t find any similar feedback, select **Add new feedback**, select a topic from **Select a category**, and then select a subcategory from **Select a subcategory**.
-
- 
-1. Enter your feedback.
-1. If you are reporting a reproducible issue, you can select **Reproduce**. Without closing Feedback Hub, reproduce the issue. After you finish, come back to Feedback Hub and select **I’m done**. The app adds a mixed reality capture of your repro and relevant diagnostic logs to your feedback.
-1. Select **Post feedback**, and you’re done.
diff --git a/devices/hololens/hololens-identity.md b/devices/hololens/hololens-identity.md
deleted file mode 100644
index e1fab33818..0000000000
--- a/devices/hololens/hololens-identity.md
+++ /dev/null
@@ -1,114 +0,0 @@
----
-title: Manage user identity and sign-in for HoloLens
-description: Manage user identity, security, and sign-in for HoloLens.
-keywords: HoloLens, user, account, aad, adfs, microsoft account, msa, credentials, reference
-ms.assetid: 728cfff2-81ce-4eb8-9aaa-0a3c3304660e
-author: scooley
-ms.author: scooley
-ms.date: 1/6/2020
-ms.prod: hololens
-ms.custom:
-- CI 111456
-- CSSTroubleshooting
-ms.topic: article
-ms.sitesec: library
-ms.topic: article
-ms.localizationpriority: medium
-audience: ITPro
-manager: jarrettr
-appliesto:
-- HoloLens (1st gen)
-- HoloLens 2
----
-
-# Manage user identity and sign-in for HoloLens
-
-> [!NOTE]
-> This article is a technical reference for IT Pros and tech enthusiasts. If you're looking for HoloLens set up instructions, read "[Setting up your HoloLens (1st gen)](hololens1-start.md)" or "[Setting up your HoloLens 2](hololens2-start.md)".
-
-Like other Windows devices, HoloLens always operates under a user context. There is always a user identity. HoloLens treats identity in almost the same manner as other Windows 10 devices do. This article is a deep-dive reference for identity on HoloLens, and focuses on how HoloLens differs from other Windows 10 devices.
-
-HoloLens supports several kinds of user identities. You can use one or more user accounts to sign in. Here's an overview of the identity types and authentication options on HoloLens:
-
-| Identity type | Accounts per device | Authentication options |
-| --- | --- | --- |
-| [Azure Active Directory (AAD)](https://docs.microsoft.com/azure/active-directory/) | 32 (see details) |
Azure web credential provider
Azure Authenticator App
Biometric (Iris) – HoloLens 2 only
PIN – Optional for HoloLens (1st gen), required for HoloLens 2
PIN – Optional for HoloLens (1st gen), required for HoloLens 2
Password
|
-| [Local account](https://docs.microsoft.com/windows/security/identity-protection/access-control/local-accounts) | 1 | Password |
-
-Cloud-connected accounts (AAD and MSA) offer more features because they can use Azure services.
-
-## Setting up users
-
-The most common way to set up a new user is during the HoloLens out-of-box experience (OOBE). During setup, HoloLens prompts for a user to sign in by using the account that they want to use on the device. This account can be a consumer Microsoft account or an enterprise account that has been configured in Azure. See Setting up your [HoloLens (1st gen)](hololens1-start.md) or [HoloLens 2](hololens2-start.md).
-
-Like Windows on other devices, signing in during setup creates a user profile on the device. The user profile stores apps and data. The same account also provides Single Sign-on for apps such as Edge or Skype by using the Windows Account Manager APIs.
-
-If you use an enterprise or organizational account to sign in to HoloLens, HoloLens enrolls in the organization's IT infrastructure. This enrollment allows your IT Admin to configure Mobile Device Management (MDM) to send group policies to your HoloLens.
-
-By default, as for other Windows 10 devices, you'll have to sign in again when HoloLens restarts or resumes from standby. You can use the Settings app to change this behavior, or the behavior can be controlled by group policy.
-
-### Linked accounts
-
-As in the Desktop version of Windows, you can link additional web account credentials to your HoloLens account. Such linking makes it easier to access resources across or within apps (such as the Store) or to combine access to personal and work resources. After you connect an account to the device, you can grant permission to use the device to apps so that you don't have to sign in to each app individually.
-
-Linking accounts does not separate the user data created on the device, such as images or downloads.
-
-### Setting up multi-user support (AAD only)
-
-> [!NOTE]
-> **HoloLens (1st gen)** began supporting multiple AAD users in the [Windows 10 April 2018 Update](https://docs.microsoft.com/windows/mixed-reality/release-notes-april-2018) as part of [Windows Holographic for Business](hololens-upgrade-enterprise.md).
-
-HoloLens supports multiple users from the same AAD tenant. To use this feature, you must use an account that belongs to your organization to set up the device. Subsequently, other users from the same tenant can sign in to the device from the sign-in screen or by tapping the user tile on the Start panel. Only one user can be signed in at a time. When a user signs in, HoloLens signs out the previous user.
-
-All users can use the apps installed on the device. However, each user has their own app data and preferences. Removing an app from the device removes it for all users.
-
-## Removing users
-
-You can remove a user from the device by going to **Settings** > **Accounts** > **Other people**. This action also reclaims space by removing all of that user's app data from the device.
-
-## Using single sign-on within an app
-
-As an app developer, you can take advantage of linked identities on HoloLens by using the [Windows Account Manager APIs](https://docs.microsoft.com/uwp/api/Windows.Security.Authentication.Web.Core), just as you would on other Windows devices. Some code samples for these APIs are available [here](https://go.microsoft.com/fwlink/p/?LinkId=620621).
-
-Any account interrupts that might occur, such as requesting user consent for account information, two-factor authentication, and so forth, must be handled when the app requests an authentication token.
-
-If your app requires a specific account type that hasn't been linked previously, your app can ask the system to prompt the user to add one. This request triggers the account settings pane to launch as a modal child of your app. For 2D apps, this window renders directly over the center of your app. For Unity apps, this request briefly takes the user out of your holographic app to render the child window. For information about customizing the commands and actions on this pane, see [WebAccountCommand Class](https://docs.microsoft.com/uwp/api/Windows.UI.ApplicationSettings.WebAccountCommand).
-
-## Enterprise and other authentication
-
-If your app uses other types of authentication, such as NTLM, Basic, or Kerberos, you can use [Windows Credential UI](https://docs.microsoft.com/uwp/api/Windows.Security.Credentials.UI) to collect, process, and store the user's credentials. The user experience for collecting these credentials is very similar to other cloud-driven account interrupts, and appears as a child app on top of your 2D app or briefly suspends a Unity app to show the UI.
-
-## Deprecated APIs
-
-One way in which developing for HoloLens differs from developing for Desktop is that the [OnlineIDAuthenticator](https://docs.microsoft.com/uwp/api/Windows.Security.Authentication.OnlineId.OnlineIdAuthenticator) API is not fully supported. Although the API returns a token if the primary account is in good-standing, interrupts such as those described in this article do not display any UI for the user and fail to correctly authenticate the account.
-
-## Frequently asked questions
-
-### Is Windows Hello for Business supported on HoloLens?
-
-Windows Hello for Business (which supports using a PIN to sign in) is supported for HoloLens. To allow Windows Hello for Business PIN sign-in on HoloLens:
-
-1. The HoloLens device must be [managed by MDM](hololens-enroll-mdm.md).
-1. You must enable Windows Hello for Business for the device. ([See instructions for Microsoft Intune.](https://docs.microsoft.com/intune/windows-hello))
-1. On HoloLens, the user can then use **Settings** > **Sign-in Options** > **Add PIN** to set up a PIN.
-
-> [!NOTE]
-> Users who sign in by using a Microsoft account can also set up a PIN in **Settings** > **Sign-in Options** > **Add PIN**. This PIN is associated with [Windows Hello](https://support.microsoft.com/help/17215/windows-10-what-is-hello), rather than [Windows Hello for Business](https://docs.microsoft.com/windows/security/identity-protection/hello-for-business/hello-overview).
-
-#### Does the type of account change the sign-in behavior?
-
-Yes, the behavior for the type of account affects the sign-in behavior. If you apply policies for sign-in, the policy is always respected. If no policy for sign-in is applied, these are the default behaviors for each account type:
-
-- **Microsoft account**: signs in automatically
-- **Local account**: always asks for password, not configurable in **Settings**
-- **Azure AD**: asks for password by default, and configurable by **Settings** to no longer ask for password.
-
-> [!NOTE]
-> Inactivity timers are currently not supported, which means that the **AllowIdleReturnWithoutPassword** policy is only respected when the device goes into StandBy.
-
-## Additional resources
-
-Read much more about user identity protection and authentication on [the Windows 10 security and identity documentation](https://docs.microsoft.com/windows/security/identity-protection/).
-
-Learn more about setting up hybrid identity infrastructure thorough the [Azure Hybrid identity documentation](https://docs.microsoft.com/azure/active-directory/hybrid/).
diff --git a/devices/hololens/hololens-insider.md b/devices/hololens/hololens-insider.md
deleted file mode 100644
index c4d1cee1a2..0000000000
--- a/devices/hololens/hololens-insider.md
+++ /dev/null
@@ -1,142 +0,0 @@
----
-title: Insider preview for Microsoft HoloLens
-description: It's simple to get started with Insider builds and to provide valuable feedback for our next major operating system update for HoloLens.
-ms.prod: hololens
-ms.sitesec: library
-author: scooley
-ms.author: scooley
-ms.topic: article
-ms.custom:
-- CI 111456
-- CSSTroubleshooting
-ms.localizationpriority: medium
-audience: ITPro
-ms.date: 4/14/2020
-ms.reviewer:
-manager: laurawi
-appliesto:
-- HoloLens 2
----
-
-# Insider preview for Microsoft HoloLens
-
-Welcome to the latest Insider Preview builds for HoloLens! It's simple to get started and provide valuable feedback for our next major operating system update for HoloLens.
-
-## Start receiving Insider builds
-
-On a HoloLens 2 device go to **Settings** -> **Update & Security** -> **Windows Insider Program** and select **Get started**. Link the account you used to register as a Windows Insider.
-
-Then, select **Active development of Windows**, choose whether you'd like to receive **Fast** or **Slow** builds, and review the program terms.
-
-Select **Confirm -> Restart Now** to finish up. After your device has rebooted, go to **Settings -> Update & Security -> Check for updates** to get the latest build.
-
-## Stop receiving Insider builds
-
-If you no longer want to receive Insider builds of Windows Holographic, you can opt out when your HoloLens is running a production build, or you can [recover your device](hololens-recovery.md) using the Advanced Recovery Companion to recover your device to a non-Insider version of Windows Holographic.
-
-To verify that your HoloLens is running a production build:
-
-1. Go to **Settings > System > About**, and find the build number.
-1. [See the release notes for production build numbers.](hololens-release-notes.md)
-
-To opt out of Insider builds:
-
-1. On a HoloLens running a production build, go to **Settings > Update & Security > Windows Insider Program**, and select **Stop Insider builds**.
-1. Follow the instructions to opt out your device.
-
-## Provide feedback and report issues
-
-Please use [the Feedback Hub app](hololens-feedback.md) on your HoloLens to provide feedback and report issues. Using Feedback Hub ensures that all necessary diagnostics information is included to help our engineers quickly debug and resolve the problem. Issues with the Chinese and Japanese version of HoloLens should be reported the same way.
-
-> [!NOTE]
-> Be sure to accept the prompt that asks whether you'd like Feedback Hub to access your Documents folder (select **Yes** when prompted).
-
-## Note for developers
-
-You are welcome and encouraged to try developing your applications using Insider builds of HoloLens. Check out the [HoloLens Developer Documentation](https://developer.microsoft.com/windows/mixed-reality/development) to get started. Those same instructions work with Insider builds of HoloLens. You can use the same builds of Unity and Visual Studio that you're already using for HoloLens development.
-
-
-## Windows Insider Release Notes
-
-HoloLens 2 Windows Insider builds are full of new features and improvements. Sign up for Windows Insider Fast or Slow flights to test them out!
-Here's a quick summary of what's new:
-
-- Support for FIDO2 Security Keys to enable secure and easy authentication for shared devices
-- Seamlessly apply a provisioning package from a USB drive to your HoloLens
-- Use a provisioning packages to enroll your HoloLens to your Mobile Device Management system
-- Use Windows Autopilot to set up and pre-configure new devices, quickly getting them ready for productive use. To participate in the program you'll need to meet a few requirements. While the program is in preview mode you'll need to be using Microsoft Intune. You'll need to use a tenant that is flighted for HoloLens. Lastly you'll need to have installed an insider preview buildon your HoloLens 2. To praticipate in the preview of this new program send a note to hlappreview@microsoft.com to join the preview.
-- Dark Mode - HoloLens customers can now choose the default mode for apps that support both color schemes! Based on customer feedback, with this update we are setting the default app mode to "dark," but you can easily change this setting at any time.
-- Support for additional system voice commands
-- An updated Cortana app with a focus on productivity
-- Hand Tracking improvements to reduce the tendency to close the index finger when pointing. This should make button pressing and 2D slate usage feel more accurate
-- Performance and stability improvements across the product
-- More information in settings on HoloLens about the policy pushed to the device
-
-Once you've had a chance to explore these new capabilities, use the Feedback Hub app to let us know what you think. Feedback you provide in the Feedback Hub goes directly to our engineers.
-
-### FIDO 2 support
-Many of you share a HoloLens with lots of people in a work or school environment. Whether devices are shared between students in a classroom or they're checked out from a device locker, it's important to be able to change users quickly and easily without typing long user names and passwords. FIDO lets anyone in your organization (AAD tenant) seamlessly sign in to HoloLens without entering a username or password.
-
-Read the [passwordless security docs](https://docs.microsoft.com/azure/active-directory/authentication/howto-authentication-passwordless-security-key) to get started.
-
-### Provisioning package updates
-Provisioning packages let you set HoloLens configuration through a config file rather than going through the HoloLens out of box experience. Previously, provisioning packages had to be copied onto HoloLens' internal memory, now they can be on a USB drive so they're easier to re-use on multiple HoloLens and so more people can provision HoloLens in parallel.
-
-1. To try it out, download the latest version of the Windows Configuration Designer from the Windows store onto your PC.
-1. Select **Provision HoloLens Devices** > Select **Provision HoloLens 2 devices**
-1. Build your configuration profile and, when you're done, copy all files created to a USB-C storage device.
-1. Plug it into any freshly flashed HoloLens and press **Volume down + Power** to apply your provisioning package.
-
-### System voice commands
-You can now can access these commands with your voice:
-- "Restart device"
-- "Shutdown device"
-- "Brightness up"
-- "Brightness down"
-- "Volume up"
-- "Volume down"
-- "What is my IP address?"
-- "Take a picture"
-- "Take a video" / "Stop recording"
-
-If you're running your system with a different language, please try the appropriate commands in that language.
-
-### Cortana updates
-The updated app integrates with Microsoft 365, currently in English (United States) only, to help you get more done across your devices. On HoloLens 2, Cortana will no longer support certain device-specific commands like adjusting the volume or restarting the device, which are now supported with the new system voice commands above. Learn more about the new Cortana app and its direction on our blog [here](https://blogs.windows.com/windowsexperience/2020/02/28/cortana-in-the-upcoming-windows-10-release-focused-on-your-productivity-with-enhanced-security-and-privacy/).
-
-There's currently an issue we're investigating that requires you to launch the app once after booting the device in order to use the "Hey Cortana" keyword activation, and if you updated from a 18362 build, you may see an app tile for the previous version of the Cortana app in Start that no longer works.
-
-### Dark mode
-Many Windows apps support both dark and light modes, and now HoloLens customers can choose the default mode for apps that support both. Once updated, the default app mode will be "dark," but can be changed easily. Navigate to **Settings > System > Colors to find "Choose your default app mode."**
-Here are some of the in-box apps that support Dark mode!
-- Settings
-- Microsoft Store
-- Mail
-- Calendar
-- File Explorer
-- Feedback Hub
-- OneDrive
-- Photos
-- 3D Viewer
-- Movies & TV
-
-### Windows Autopilot for HoloLens 2
-
-This Autopilot program supports Autopilot self-deploying mode to provision HoloLens 2 devices as shared devices under your tenant. Self-deploying mode leverages the device's preinstalled OEM image and drivers during the provisioning process. A user can provision the device without putting the device on and going through the Out-of-the-box Experience (OOBE).
-
-When a user starts the Autopilot self-deploying process, the process completes the following steps:
-1. Join the device to Azure Active Directory (Azure AD).
-2. Use Azure AD to enroll the device in Microsoft Intune (or another MDM service).
-3. Download the device-targeted policies, certificates, and networking profiles.
-4. Provision the device.
-5. Present the sign-in screen to the user.
-
-For full information about Autopilot, see [Windows Autopilot for HoloLens 2 evaluation guide](hololens2-autopilot.md).
-
-### FFU download and flash directions
-To test with a flight signed ffu, you first have to flight unlock your device prior to flashing the flight signed ffu.
-1. On PC
- 1. Download ffu to your PC from: [https://aka.ms/hololenspreviewdownload](https://aka.ms/hololenspreviewdownload)
- 1. Install ARC (Advanced Recovery Companion) from the Microsoft Store: [https://www.microsoft.com/store/productId/9P74Z35SFRS8](https://www.microsoft.com/store/productId/9P74Z35SFRS8)
-1. On HoloLens - Flight Unlock: Open **Settings** > **Update & Security** > **Windows Insider Program** then sign up, reboot device
-1. Flash FFU - Now you can flash the flight signed FFU using ARC
diff --git a/devices/hololens/hololens-kiosk.md b/devices/hololens/hololens-kiosk.md
deleted file mode 100644
index 2043128011..0000000000
--- a/devices/hololens/hololens-kiosk.md
+++ /dev/null
@@ -1,219 +0,0 @@
----
-title: Set up HoloLens as a kiosk for specific applications
-description: Use a kiosk configuration to lock down the apps on HoloLens.
-ms.prod: hololens
-ms.sitesec: library
-author: dansimp
-ms.author: dansimp
-ms.topic: article
-ms.localizationpriority: medium
-ms.date: 11/13/2018
-ms.custom:
-- CI 111456
-- CSSTroubleshooting
-ms.reviewer:
-manager: laurawi
-appliesto:
-- HoloLens (1st gen)
-- HoloLens 2
----
-
-# Set up HoloLens as a kiosk for specific applications
-
-In Windows 10, version 1803, you can configure your HoloLens devices to run as multi-app or single-app kiosks. You can also configure guest access for a HoloLens kiosk device by [designating a SpecialGroup account in your XML file.](#add-guest-access-to-the-kiosk-configuration-optional)
-
-When HoloLens is configured as a multi-app kiosk, only the allowed apps are available to the user. The benefit of a multi-app kiosk, or fixed-purpose device, is to provide an easy-to-understand experience for individuals by putting in front of them only the things they need to use, and removing from their view the things they don't need to access.
-
-Single-app kiosk mode starts the specified app when the user signs in, and restricts the user's ability to launch new apps or change the running app. When single-app kiosk mode is enabled for HoloLens, the [start gestures](https://docs.microsoft.com/hololens/hololens2-basic-usage#start-gesture) (including [Bloom](https://docs.microsoft.com/hololens/hololens1-basic-usage) on HoloLens (1st Gen)) and Cortana are disabled, and placed apps aren't shown in the user's surroundings.
-
-The following table lists the device capabilities in the different kiosk modes.
-
-Kiosk mode | Voice and Bloom commands | Quick actions menu | Camera and video | Miracast
---- | --- | --- | --- | ---
-Single-app kiosk |  |  |  | 
-Multi-app kiosk |  |  with **Home** and **Volume** (default)
Photo and video buttons shown in Quick actions menu if the Camera app is enabled in the kiosk configuration.
Miracast is shown if the Camera app and device picker app are enabled in the kiosk configuration. |  if the Camera app is enabled in the kiosk configuration. |  if the Camera app and device picker app are enabled in the kiosk configuration.
-
-> [!NOTE]
-> Use the Application User Model ID (AUMID) to allow apps in your kiosk configuration. The Camera app AUMID is `HoloCamera_cw5n1h2txyewy!HoloCamera`. The device picker app AUMID is `HoloDevicesFlow_cw5n1h2txyewy!HoloDevicesFlow`.
-
-The [AssignedAccess Configuration Service Provider (CSP)](https://docs.microsoft.com/windows/client-management/mdm/assignedaccess-csp) enables kiosk configuration.
-
-> [!WARNING]
-> The assigned access feature which enables kiosk mode is intended for corporate-owned fixed-purpose devices. When the multi-app assigned access configuration is applied on the device, certain policies are enforced system-wide, and will impact other users on the device. Deleting the multi-app configuration will remove the assigned access lockdown profiles associated with the users, but it cannot revert all [the enforced policies](https://docs.microsoft.com/windows/configuration/lock-down-windows-10-to-specific-apps#policies-set-by-multi-app-kiosk-configuration). A factory reset is needed to clear all the policies enforced via assigned access.
->
-> Be aware that voice commands are enabled for kiosk mode configured in Microsoft Intune or provisioning packages, even if the Cortana app is not selected as a kiosk app.
-
-For HoloLens devices running Windows 10, version 1803, there are three methods that you can use to configure the device as a kiosk:
-- You can use [Microsoft Intune or other mobile device management (MDM) service](#set-up-kiosk-mode-using-microsoft-intune-or-mdm-windows-10-version-1803) to configure single-app and multi-app kiosks.
-- You can [use a provisioning package](#set-up-kiosk-mode-using-a-provisioning-package-windows-10-version-1803) to configure single-app and multi-app kiosks.
-- You can [use the Windows Device Portal](#set-up-kiosk-mode-using-the-windows-device-portal-windows-10-version-1607-and-version-1803) to configure single-app kiosks. This method is recommended only for demonstrations, as it requires that developer mode be enabled on the device.
-
-For HoloLens devices running Windows 10, version 1607, you can [use the Windows Device Portal](#set-up-kiosk-mode-using-the-windows-device-portal-windows-10-version-1607-and-version-1803) to configure single-app kiosks.
-
-## Start layout for HoloLens
-
-If you use [MDM, Microsoft Intune](#set-up-kiosk-mode-using-microsoft-intune-or-mdm-windows-10-version-1803), or a [provisioning package](#set-up-kiosk-mode-using-a-provisioning-package-windows-10-version-1803) to configure a multi-app kiosk, the procedure requires a Start layout. Start layout customization isn't supported in Holographic for Business, so you'll need to use a placeholder Start layout.
-
-> [!NOTE]
-> Because a single-app kiosk launches the kiosk app when a user signs in, there is no Start screen displayed.
-
-### Start layout file for MDM (Intune and others)
-
-Save the following sample as an XML file. You can use this file when you configure the multi-app kiosk in Microsoft Intune (or in another MDM service that provides a kiosk profile).
-
-> [!NOTE]
-> If you need to use a custom setting and full XML configuration to set up a kiosk in your MDM service, use the [Start layout instructions for a provisioning package](#start-layout-for-a-provisioning-package).
-
-```xml
-
-
-
-
-
-
-
-
-
-```
-
-### Start layout for a provisioning package
-
-You will [create an XML file](#set-up-kiosk-mode-using-a-provisioning-package-windows-10-version-1803) to define the kiosk configuration to be included in a provisioning package. Use the following sample in the `StartLayout` section of your XML file.
-
-```xml
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- ]]>
-
-
-```
-
-## Set up kiosk mode using Microsoft Intune or MDM (Windows 10, version 1803)
-
-For HoloLens devices that are managed by Microsoft Intune, directions can be found [here](hololens-commercial-infrastructure.md#how-to-configure-kiosk-mode-using-microsoft-intune).
-
-For other MDM services, check your provider's documentation for instructions. If you need to use a custom setting and full XML configuration to set up a kiosk in your MDM service, [create an XML file that defines the kiosk configuration](#create-a-kiosk-configuration-xml-file), and make sure to include the [Start layout](#start-layout-for-a-provisioning-package) in the XML file.
-
-## Set up kiosk mode using a provisioning package (Windows 10, version 1803)
-
-Process:
-1. [Create an XML file that defines the kiosk configuration.](#create-a-kiosk-configuration-xml-file)
-2. [Add the XML file to a provisioning package.](#add-the-kiosk-configuration-xml-file-to-a-provisioning-package)
-3. [Apply the provisioning package to HoloLens.](#apply-the-provisioning-package-to-hololens)
-
-### Create a kiosk configuration XML file
-
-Follow [the instructions for creating a kiosk configuration XML file for desktop](https://docs.microsoft.com/windows/configuration/lock-down-windows-10-to-specific-apps#configure-a-kiosk-using-a-provisioning-package), with the following exceptions:
-
-- Do not include Classic Windows applications (Win32) since they aren't supported on HoloLens.
-- Use the [placeholder Start XML](#start-layout-for-hololens) for HoloLens.
-
-#### Add guest access to the kiosk configuration (optional)
-
-In the [Configs section of the XML file](https://docs.microsoft.com/windows/configuration/lock-down-windows-10-to-specific-apps#configs), you can configure a special group named **Visitor** to allow guests to use the kiosk. When the kiosk is configured with the **Visitor** special group, a "**Guest**" option is added to the sign-in page. The **Guest** account does not require a password, and any data associated with the account is deleted when the account signs out.
-
-Use the following snippet in your kiosk configuration XML to enable the **Guest** account:
-
-```xml
-
-
-
-
-
-
-```
-
-### Add the kiosk configuration XML file to a provisioning package
-
-1. Open [Windows Configuration Designer](https://www.microsoft.com/store/apps/9nblggh4tx22).
-2. Choose **Advanced provisioning**.
-3. Name your project, and click **Next**.
-4. Choose **Windows 10 Holographic** and click **Next**.
-5. Select **Finish**. The workspace for your package opens.
-6. Expand **Runtime settings** > **AssignedAccess** > **MultiAppAssignedAccessSettings**.
-7. In the center pane, click **Browse** to locate and select the kiosk configuration XML file that you created.
-
- 
-
-8. (**Optional**: If you want to apply the provisioning package after device initial setup and there is an admin user already available on the kiosk device, skip this step.) Create an admin user account in **Runtime settings** > **Accounts** > **Users**. Provide a **UserName** and **Password**, and select **UserGroup** as **Administrators**. With this account, you can view the provisioning status and logs if needed.
-9. (**Optional**: If you already have a non-admin account on the kiosk device, skip this step.) Create a local standard user account in **Runtime settings** > **Accounts** > **Users**. Make sure the **UserName** is the same as the account that you specify in the configuration XML. Select **UserGroup** as **Standard Users**.
-10. On the **File** menu, select **Save.**
-11. On the **Export** menu, select **Provisioning package**.
-12. Change **Owner** to **IT Admin**, which will set the precedence of this provisioning package higher than provisioning packages applied to this device from other sources, and then select **Next.**
-
-13. On the **Provisioning package security** page, do not select **Enable package encryption** or provisioning will fail on HoloLens. You can choose to enable package signing.
-
- - **Enable package signing** - If you select this option, you must select a valid certificate to use for signing the package. You can specify the certificate by clicking **Browse** and choosing the certificate you want to use to sign the package.
-
-14. Click **Next** to specify the output location where you want the provisioning package to go when it's built. By default, Windows Configuration Designer uses the project folder as the output location. Optionally, you can click **Browse** to change the default output location.
-
-15. Click **Next**.
-
-16. Click **Build** to start building the package. The provisioning package doesn't take long to build. The project information is displayed in the build page and the progress bar indicates the build status.
-
-
-### Apply the provisioning package to HoloLens
-
-1. Connect HoloLens via USB to a PC and start the device, but do not continue past the **Fit** page of OOBE (the first page with the blue box).
-
-3. HoloLens will show up as a device in File Explorer on the PC.
-
-4. In File Explorer, drag and drop the provisioning package (.ppkg) onto the device storage.
-
-5. Briefly press and release the **Volume Down** and **Power** buttons simultaneously again while on the **fit** page.
-
-6. The device will ask you if you trust the package and would like to apply it. Confirm that you trust the package.
-
-7. You will see whether the package was applied successfully or not. If it failed, you can fix your package and try again. If it succeeded, proceed with OOBE.
-
-
-## Set up kiosk mode using the Windows Device Portal (Windows 10, version 1607 and version 1803)
-
-1. [Set up the HoloLens to use the Windows Device Portal](https://developer.microsoft.com/windows/mixed-reality/using_the_windows_device_portal#setting_up_hololens_to_use_windows_device_portal). The Device Portal is a web server on your HoloLens that you can connect to from a web browser on your PC.
-
- > [!IMPORTANT]
- > When you set up HoloLens to use the Device Portal, you must enable **Developer Mode** on the device. **Developer Mode** on a device that has been upgraded to Windows Holographic for Business enables side-loading of apps, which risks the installation of apps that have not been certified by the Microsoft Store. Administrators can block the ability to enable **Developer Mode** using the **ApplicationManagement/AllowDeveloper Unlock** setting in the [Policy CSP](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx). [Learn more about Developer Mode.](https://msdn.microsoft.com/windows/uwp/get-started/enable-your-device-for-development#developer-mode)
-
-2. On a PC, connect to the HoloLens using [Wi-Fi](https://developer.microsoft.com/windows/mixed-reality/Using_the_Windows_Device_Portal.html#connecting_over_wi-fi) or [USB](https://developer.microsoft.com/windows/mixed-reality/Using_the_Windows_Device_Portal.html#connecting_over_usb).
-
-3. [Create a user name and password](https://developer.microsoft.com/windows/mixed-reality/Using_the_Windows_Device_Portal.html#creating_a_username_and_password) if this is the first time you connect to the Windows Device Portal, or enter the user name and password that you previously set up.
-
- > [!TIP]
- > If you see a certificate error in the browser, follow [these troubleshooting steps](https://developer.microsoft.com/windows/mixed-reality/Using_the_Windows_Device_Portal.html#security_certificate).
-
-4. In the Windows Device Portal, click **Kiosk Mode**.
-
- 
-
- > [!NOTE]
- > The kiosk mode option will be available if the device is [enrolled in device management](hololens-enroll-mdm.md) and has a [license to upgrade to Windows Holographic for Business](hololens1-upgrade-enterprise.md).
-
-5. Select **Enable Kiosk Mode**, choose an app to run when the device starts, and click **Save**.
-
-## Kiosk app recommendations
-
-- You cannot select Microsoft Edge, Microsoft Store, or the Shell app as a kiosk app.
-- We recommend that you do **not** select the Settings app and the File Explorer app as a kiosk app.
-- You can select Cortana as a kiosk app.
-- To enable photo or video capture, the HoloCamera app must be enabled as a kiosk app.
-
-## More information
-
-Watch how to configure a kiosk in a provisioning package.
-> [!VIDEO https://www.microsoft.com/videoplayer/embed/fa125d0f-77e4-4f64-b03e-d634a4926884?autoplay=false]
diff --git a/devices/hololens/hololens-known-issues.md b/devices/hololens/hololens-known-issues.md
deleted file mode 100644
index de39da5999..0000000000
--- a/devices/hololens/hololens-known-issues.md
+++ /dev/null
@@ -1,198 +0,0 @@
----
-title: Known issues for HoloLens
-description: This is the list of known issues that may affect HoloLens developers.
-keywords: troubleshoot, known issue, help
-author: mattzmsft
-ms.author: mazeller
-ms.date: 4/20/2020
-ms.topic: article
-ms.custom:
-- CI 111456
-- CSSTroubleshooting
-HoloLens and holograms: Frequently asked questions
-manager: jarrettr
-ms.prod: hololens
-appliesto:
-- HoloLens (1st Gen)
-- HoloLens 2
----
-
-# Known issues for HoloLens
-
-This is the current list of known issues for HoloLens devices. Check here first if you are seeing an odd behavior. This list will be kept updated as new issues are discovered or reported, or as issues are addressed in future HoloLens software updates.
-
->[!NOTE]
-> - If you discover an issue that is not blocking you please report it on your HoloLens device via [Feedback Hub](hololens-feedback.md).
-> - If the issue you are facing is blocking you, in addtion to filing feedback, please [file a support request](https://aka.ms/hlsupport).
-
-- [Known issues for all HoloLens generations](#known-issues-for-all-hololens-generations)
-- [Known issues for HoloLens 2 devices](#known-issues-for-hololens-2-devices)
-- [Known issues for HoloLens (1st Gen)](#known-issues-for-hololens-1st-gen)
-- [Known issues for HoloLens emulator](#known-issues-for-hololens-emulator)
-
-## Known issues for all HoloLens generations
-
-### Unity
-
-- See [Install the tools](https://docs.microsoft.com/windows/mixed-reality/install-the-tools) for the most up-to-date version of Unity recommended for HoloLens development.
-- Known issues with the Unity HoloLens Technical Preview are documented in the [HoloLens Unity forums](https://forum.unity3d.com/threads/known-issues.394627/).
-
-### Windows Device Portal
-
-- The Live Preview feature in Mixed Reality capture may exhibit several seconds of latency.
-- On the Virtual Input page, the Gesture and Scroll controls under the Virtual Gestures section are not functional. Using them will have no effect. The virtual keyboard on the same page works correctly.
-- After enabling Developer Mode in Settings, it may take a few seconds before the switch to turn on the Device Portal is enabled.
-
-## Known issues for HoloLens 2 devices
-
-### Blue screen is shown after unenrolling from Insider preview builds on a device reflashed with a Insider build
-
-This is an issue affecting that affects users who are were on an Insider preview build, reflashed their HoloLens 2 with a new insider preview build, and then unenrolled from the Insider program.
-
-This does not affect:
-- Users who are not enrolled in Windows Insider
-- Insiders:
- - If a device has been enrolled since Insider builds were version 18362.x
- - If they flashed a Insider signed 19041.x build AND stay enrolled in the Insider program
-
-Work-around:
-- Avoid the issue
- - Flash a non-insider build. One of the regular monthly updates.
- - Stay on Insider Preview
-- Reflash the device
- 1. Put the [HoloLens 2 into flashing mode](https://review.docs.microsoft.com/hololens/hololens-recovery?branch=master#hololens-2) manually by fully powering down while not connect. Then while holding Volume up, tap the Power button.
- 1. Connect to the PC and open Advanced Recovery Companion.
- 1. Flash the HoloLens 2 to the default build.
-
-## Known issues for HoloLens (1st Gen)
-
-### Unable to connect and deploy to HoloLens through Visual Studio
-
-> [!NOTE]
-> Last Update: 8/8 @ 5:11PM - Visual Studio has released VS 2019 Version 16.2 which includes a fix to this issue. We recommend updating to this newest version to avoid experiencing this error.
-
-Visual Studio has released VS 2019 Version 16.2 which includes a fix to this issue. We recommend updating to this newest version to avoid experiencing this error.
-
-Issue root-cause: Users who used Visual Studio 2015 or early releases of Visual Studio 2017 to deploy and debug applications on their HoloLens and then subsequently used the latest versions of Visual Studio 2017 or Visual Studio 2019 with the same HoloLens will be affected. The newer releases of Visual Studio deploy a new version of a component, but files from the older version are left over on the device, causing the newer version to fail. This causes the following error message: DEP0100: Please ensure that target device has developer mode enabled. Could not obtain a developer license on \ due to error 80004005.
-
-#### Workaround
-
-Our team is currently working on a fix. In the meantime, you can use the following steps to work around the issue and help unblock deployment and debugging:
-
-1. Open Visual Studio
-1. Select **File** > **New** > **Project**.
-1. Select **Visual C#** > **Windows Desktop** > **Console App (.NET Framework)**.
-1. Give the project a name (such as "HoloLensDeploymentFix") and make sure the Framework is set to at least .NET Framework 4.5, then Select **OK**.
-1. Right-click on the **References** node in Solution Explorer and add the following references (select to the **Browse** section and select **Browse**):
-
- ```CMD
- C:\Program Files (x86)\Windows Kits\10\bin\10.0.18362.0\x86\Microsoft.Tools.Deploy.dll
- C:\Program Files (x86)\Windows Kits\10\bin\10.0.18362.0\x86\Microsoft.Tools.Connectivity.dll
- C:\Program Files (x86)\Windows Kits\10\bin\10.0.18362.0\x86\SirepInterop.dll
- ```
-
- > [!NOTE]
- > If you don't have 10.0.18362.0 installed, use the most recent version that you have.
-
-1. Right-click on the project in Solution Explorer and select **Add** > **Existing Item**.
-1. Browse to C:\Program Files (x86)\Windows Kits\10\bin\10.0.18362.0\x86 and change the filter to **All Files (\*.\*)**.
-1. Select both SirepClient.dll and SshClient.dll, and Select **Add**.
-1. Locate and select both files in Solution Explorer (they should be at the bottom of the list of files) and change **Copy to Output Directory** in the **Properties** window to **Copy always**.
-1. At the top of the file, add the following to the existing list of `using` statements:
-
- ```CMD
- using Microsoft.Tools.Deploy;
- using System.Net;
- ```
-
-1. Inside of `static void Main(...)`, add the following code:
-
- ```PowerShell
- RemoteDeployClient client = RemoteDeployClient.CreateRemoteDeployClient();
- client.Connect(new ConnectionOptions()
- {
- Credentials = new NetworkCredential("DevToolsUser", string.Empty),
- IPAddress = IPAddress.Parse(args[0])
- });
- client.RemoteDevice.DeleteFile(@"C:\Data\Users\DefaultAccount\AppData\Local\DevelopmentFiles\VSRemoteTools\x86\CoreCLR\mscorlib.ni.dll");
- ```
-
-1. Select **Build** > **Build Solution**.
-1. Open a Command Prompt Window and cd to the folder that contains the compiled .exe file (for example, C:\MyProjects\HoloLensDeploymentFix\bin\Debug)
-1. Run the executable and provide the device's IP address as a command-line argument. (If connected using USB, you can use 127.0.0.1, otherwise use the device's Wi-Fi IP address.) For example, "HoloLensDeploymentFix 127.0.0.1"
-
-1. After the tool has exited without any messages (this should only take a few seconds), you will now be able to deploy and debug from Visual Studio 2017 or newer. Continued use of the tool is not necessary.
-
-We will provide further updates as they become available.
-
-### Issues launching the Microsoft Store and apps on HoloLens
-
-> [!NOTE]
-> Last Update: 4/2 @ 10 AM - Issue resolved.
-
-You may experience issues when trying to launch the Microsoft Store and apps on HoloLens. We've determined that the issue occurs when background app updates deploy a newer version of framework packages in specific sequences while one or more of their dependent apps are still running. In this case, an automatic app update delivered a new version of the .NET Native Framework (version 10.0.25531 to 10.0.27413) caused the apps that are running to not correctly update for all running apps consuming the prior version of the framework. The flow for framework update is as follows:
-
-1. The new framework package is downloaded from the store and installed
-1. All apps using the older framework are 'updated' to use the newer version
-
-If step 2 is interrupted before completion then any apps for which the newer framework wasn't registered will fail to launch from the start menu. We believe any app on HoloLens could be affected by this issue.
-
-Some users have reported that closing hung apps and launching other apps such as Feedback Hub, 3D Viewer or Photos resolves the issue for them—however, this does not work 100% of the time.
-
-We have root caused that this issue was not caused the update itself, but a bug in the OS that resulted in the .NET Native framework update being handled incorrectly. We are pleased to announce that we have identified a fix and have released an update (OS version 17763.380) containing the fix.
-
-To see if your device can take the update, please:
-
-1. Go to the Settings app and open **Update & Security**.
-1. Select **Check for Updates**.
-1. If update to 17763.380 is available, please update to this build to receive the fix for the App Hang bug
-1. Upon updating to this version of the OS, the Apps should work as expected.
-
-Additionally, as we do with every HoloLens OS release, we have posted the FFU image to the [Microsoft Download Center](https://aka.ms/hololensdownload/10.0.17763.380).
-
-If you would not like to take the update, we have released a new version of the Microsoft Store UWP app as of 3/29. After you have the updated version of the Store:
-
-1. Open the Store and confirm that it loads.
-1. Use the bloom gesture to open the menu.
-1. Attempt to open previously broken apps.
-1. If it still cannot be launched, tap and hold the icon of the broken app and select uninstall.
-1. Resinstall these apps from the store.
-
-If your device is still unable to load apps, you can sideload a version of the .NET Native Framework and Runtime through the download center by following these steps:
-
-1. Please download [this zip file](https://download.microsoft.com/download/8/5/C/85C23745-794C-419D-B8D7-115FBCCD6DA7/netfx_1.7.zip) from the Microsoft Download Center. Unzipping will produce two files. Microsoft.NET.Native.Runtime.1.7.appx and Microsoft.NET.Native.Framework.1.7.appx
-1. Please verify that your device is dev unlocked. If you haven't done that before the instructions to do that are [here](https://docs.microsoft.com/windows/mixed-reality/using-the-windows-device-portal).
-1. You then want to get into the Windows Device Portal. Our recommendation is to do this over USB and you would do that by typing http://127.0.0.1:10080 into your browser.
-1. After you have the Windows Device Portal up we need you to "side load" the two files that you downloaded. To do that you need to go down the left side bar until you get to the **Apps** section and select **Apps**.
-1. You will then see a screen that is similar to the below. You want to go to the section that says **Install App** and browse to where you unzipped those two APPX files. You can only do one at a time, so after you select the first one, then click on "Go" under the Deploy section. Then do this for the second APPX file.
-
- 
-1. At this point we believe your applications should start working again and that you can also get to the Store.
-1. In some cases, it is necessary run the additional step of launching the 3D Viewer app before affected apps will launch.
-
-We appreciate your patience as we have gone through the process to get this issue resolved, and we look forward to continued working with our community to create successful Mixed Reality experiences.
-
-### Device Update
-
-- 30 seconds after a new update, the shell may disappear one time. Please perform the **bloom** gesture to resume your session.
-
-### Visual Studio
-
-- See [Install the tools](https://docs.microsoft.com/windows/mixed-reality/install-the-tools) for the most up-to-date version of Visual Studio that is recommended for HoloLens development.
-- When deploying an app from Visual Studio to your HoloLens, you may see the error: **The requested operation cannot be performed on a file with a user-mapped section open. (Exception from HRESULT: 0x800704C8)**. If this happens, try again and your deployment will generally succeed.
-
-### API
-
-- If the application sets the [focus point](https://docs.microsoft.com/windows/mixed-reality/focus-point-in-unity) behind the user or the normal to camera.forward, holograms will not appear in Mixed Reality Capture photos or videos. Until this bug is fixed in Windows, if applications actively set the [focus point](https://docs.microsoft.com/windows/mixed-reality/focus-point-in-unity) they should ensure the plane normal is set opposite camera-forward (for example, normal = -camera.forward).
-
-### Xbox Wireless Controller
-
-- Xbox Wireless Controller S must be updated before it can be used with HoloLens. Ensure you are [up to date](https://support.xbox.com/xbox-one/accessories/update-controller-for-stereo-headset-adapter) before attempting to pair your controller with a HoloLens.
-- If you reboot your HoloLens while the Xbox Wireless Controller is connected, the controller will not automatically reconnect to HoloLens. The Guide button light will flash slowly until the controller powers off after 3 minutes. To reconnect your controller immediately, power off the controller by holding the Guide button until the light turns off. When you power your controller on again, it will reconnect to HoloLens.
-- If your HoloLens enters standby while the Xbox Wireless Controller is connected, any input on the controller will wake the HoloLens. You can prevent this by powering off your controller when you are done using it.
-
-## Known issues for HoloLens emulator
-
-- Not all apps in the Microsoft Store are compatible with the emulator. For example, Young Conker and Fragments are not playable on the emulator.
-- You cannot use the PC webcam in the Emulator.
-- The Live Preview feature of the Windows Device Portal does not work with the emulator. You can still capture Mixed Reality videos and images.
diff --git a/devices/hololens/hololens-licenses-requirements.md b/devices/hololens/hololens-licenses-requirements.md
deleted file mode 100644
index ef727bfc77..0000000000
--- a/devices/hololens/hololens-licenses-requirements.md
+++ /dev/null
@@ -1,64 +0,0 @@
----
-title: Licenses for Mixed Reality Deployment
-description:
-ms.prod: hololens
-ms.sitesec: library
-author: pawinfie
-ms.author: pawinfie
-audience: ITPro
-ms.topic: article
-ms.localizationpriority: high
-ms.date: 1/23/2020
-ms.reviewer:
-audience: ITPro
-manager: bradke
-appliesto:
-- HoloLens (1st gen)
-- HoloLens 2
----
-
-# Determine what licenses you need
-
-## Mobile Device Management (MDM) Licenses Guidance
-
-If you plan on managing your HoloLens devices, you will need Azure AD and an MDM. Active Director (AD) cannot be used to manage HoloLens devices.
-If you plan on using an MDM other than Intune, an [Azure Active Directory Licenses](https://docs.microsoft.com/azure/active-directory/fundamentals/active-directory-whatis) is required.
-If you plan on using Intune as your MDM, [here](https://docs.microsoft.com/intune/fundamentals/licenses) are a list of suites that includes Intune licenses. **Please note that Azure AD is included in the majority of these suites.**
-
-## Identify the licenses needed for your scenario and products
-
-### HoloLens Licenses Requirements
-
-You may need to upgrade your HoloLens 1st Gen Device to Windows Holographic for Business. (See [HoloLens commercial features](holoLens-commercial-features.md#feature-comparison-between-editions) to determine if you need to upgrade).
-
- If so, you will need to do the following:
-
-- Acquire a HoloLens Enterprise license XML file
-- Apply the XML file to the HoloLens. You can do this through a [Provisioning package](hololens-provisioning.md) or through your [Mobile Device Manager](https://docs.microsoft.com/intune/configuration/holographic-upgrade)
-
-### Remote Assist License Requirements
-
-Make sure you have the required licensing and device. Updated licensing and product requirements can be found [here](https://docs.microsoft.com/dynamics365/mixed-reality/remote-assist/requirements).
-
-1. [Remote Assist License](https://docs.microsoft.com/dynamics365/mixed-reality/remote-assist/buy-and-deploy-remote-assist)
-1. [Teams Freemium/Teams](https://products.office.com/microsoft-teams/free)
-1. [Azure Active Directory (Azure AD) License](https://docs.microsoft.com/azure/active-directory/fundamentals/active-directory-whatis)
-
-If you plan on implementing **[this cross-tenant scenario](https://docs.microsoft.com/dynamics365/mixed-reality/remote-assist/cross-tenant-overview#scenario-2-leasing-services-to-other-tenants)**, you may need an Information Barriers license. Please see [this article](https://docs.microsoft.com/dynamics365/mixed-reality/remote-assist/cross-tenant-licensing-implementation#step-1-determine-if-information-barriers-are-necessary) to determine if an Information Barrier License is required.
-
-### Guides License Requirements
-
-Updated licensing and device requirements can be found [here](https://docs.microsoft.com/dynamics365/mixed-reality/guides/requirements).
-
-1. [Azure Active Directory (Azure AD) License](https://docs.microsoft.com/azure/active-directory/fundamentals/active-directory-whatis)
-1. [Power BI](https://powerbi.microsoft.com/desktop/)
-1. [Guides](https://docs.microsoft.com/dynamics365/mixed-reality/guides/setup)
-
-### Scenario 1: Kiosk Mode
-
-1. If you are **not** planning to manage your device and you are planning to use a local account or an MSA as the login identity, you will not need any additional licenses. Kiosk mode can be accomplished using a provisioning packages.
-1. If you are planning to use an MDM to implement Kiosk mode, you will need an [Azure Active Directory (Azure AD) License](https://docs.microsoft.com/azure/active-directory/fundamentals/active-directory-whatis).
-
-Additional information regarding kiosk mode will be covered in [Configuring your Network for HoloLens](hololens-commercial-infrastructure.md#how-to-configure-kiosk-mode-using-microsoft-intune).
-
-## Next Step: [Configure your network for HoloLens](hololens-commercial-infrastructure.md)
\ No newline at end of file
diff --git a/devices/hololens/hololens-multiple-users.md b/devices/hololens/hololens-multiple-users.md
deleted file mode 100644
index d65929d676..0000000000
--- a/devices/hololens/hololens-multiple-users.md
+++ /dev/null
@@ -1,53 +0,0 @@
----
-title: Share your HoloLens with multiple people
-description: You can configure HoloLens to be shared by multiple Azure Active Directory accounts, or by multiple users that use a single account.
-ms.prod: hololens
-ms.sitesec: library
-author: scooley
-ms.author: scooley
-ms.topic: article
-ms.localizationpriority: medium
-ms.date: 09/16/2019
-ms.reviewer:
-manager: laurawi
-appliesto:
-- HoloLens (1st gen)
-- HoloLens 2
----
-
-# Share your HoloLens with multiple people
-
-It's common to share one HoloLens with many people or to have many people share a set of HoloLens devices. This article describes the different ways in which you can share a device.
-
-## Share with multiple people, each using their own account
-
-**Prerequisite**: The HoloLens device must be running Windows 10, version 1803 or later. HoloLens (1st gen) also need to be [upgraded to Windows Holographic for Business](hololens-upgrade-enterprise.md).
-
-When they use their own Azure Active Directory (Azure AD) accounts, multiple users can each keep their own user settings and user data on the device.
-
-To make sure that multiple people can use their own accounts on your HoloLens, follow these steps to configure it:
-
-1. Make sure the the device is running Windows 10, version 1803 or later.
- > [!IMPORTANT]
- > If you are using a HoloLens (1st gen) device, [upgrade the device to Windows Holographic for Business](hololens1-upgrade-enterprise.md).
-1. When you set up the device, select **My work or school owns it** and sign in by using an Azure AD account.
-1. After you finish setup, make sure that the account settings (**Settings** > **Accounts**) includes **Other users**.
-
-To use HoloLens, each user follows these steps:
-
-1. If another user has been using the device, do one of the following:
- - Press the power button once to go to standby, and then press the power button again to return to the lock screen
- - HoloLens 2 users may select the user tile on the top of the Pins panel to sign out the current user.
-
-1. Use your Azure AD account credentials to sign in to the device.
- If this is the first time that you have used the device, you have to [calibrate](hololens-calibration.md) HoloLens to your own eyes.
-
-To see a list of the device users or to remove a user from the device, go to **Settings** > **Accounts** > **Other users**.
-
-## Share with multiple people, all using the same account
-
-Multiple users can also share a HoloLens device while using a single user account.
-
-**On HoloLens 2**, when a new user puts the device on their head for the first time (while keeping the same account signed in), the device prompts the new user to quickly calibrate and personalize the viewing experience. The device can store the calibration information so that in the future, the device can automatically optimize the quality and comfort of each user's viewing experience. The users do not need to calibrate the device again.
-
-**On HoloLens (1st gen)** users sharing an account will need to ask to recalibrate in the Settings app. Read more about [calibration](hololens-calibration.md).
diff --git a/devices/hololens/hololens-network.md b/devices/hololens/hololens-network.md
deleted file mode 100644
index bd9286a91e..0000000000
--- a/devices/hololens/hololens-network.md
+++ /dev/null
@@ -1,98 +0,0 @@
----
-title: Connect to a network
-description: Instructions on how to connect to internet with HoloLens and how to identify the device's IP address.
-ms.assetid: 0895606e-96c0-491e-8b1c-52e56b00365d
-author: mattzmsft
-ms.author: mazeller
-keywords: HoloLens, wifi, wireless, internet, ip, ip address
-ms.prod: hololens
-ms.sitesec: library
-ms.localizationpriority: high
-ms.reviewer:
-manager: jarrettr
-appliesto:
-- HoloLens (1st gen)
-- HoloLens 2
----
-
-# Connect to a network
-
-To do most things on your HoloLens, you have to be connected to a network. This guide will help you:
-
-- Connect to a network using Wi-Fi or (for HoloLens 2 only) Ethernet over USB-C
-- Disable and re-enable Wi-Fi
-
-Read more about [using HoloLens offline](hololens-offline.md).
-
-## Connecting for the first time
-
-The first time you use your HoloLens, you'll be guided through connecting to a Wi-Fi network. If you have trouble connecting to Wi-Fi during setup, make sure that your network is either an open, password-protected network or a captive portal network. Make sure that the network doesn't require you to use a certificate to connect. After setup, you can connect to other types of Wi-Fi networks.
-
-## Connecting to Wi-Fi after setup
-
-1. Select **Start** > **Settings**.
- - *HoloLens (1st gen) only*: Use your gaze to position the Settings app, then air tap to place it, or say "Place."
-1. Select **Network & Internet** > **Wi-Fi**. If you don't see your network, scroll down the list.
-1. Select a network, then select **Connect**.
-1. If you are prompted for a network password type it and then select **Next**.
-
-## Connecting to Wi-Fi on HoloLens (1st gen)
-
-HoloLens contains a 802.11ac-capable, 2x2 Wi-Fi radio. Connecting HoloLens to a Wi-Fi network is similar to connecting a Windows 10 Desktop or Mobile device to a Wi-Fi network.
-
-
-
-1. Open the **Start** menu.
-1. Select the Settings app from **Start** or from the **All Apps** list on the right of the **Start** menu. The Settings app will be auto-placed in front of you.
-1. Select **Network & Internet**.
-1. Make sure Wi-Fi is turned on.
-1. Select a Wi-Fi network from the list.
-1. If needed, type in the Wi-Fi network password.
-
-You can also confirm you are connected to a Wi-Fi network by checking the Wi-Fi status in the **Start** menu:
-
-1. Open the **Start** menu.
-1. Look at the top left of the **Start** menu for Wi-Fi status. The state of Wi-Fi and the SSID of the connected network will be shown.
-
-## Troubleshooting your connection to Wi-Fi
-
-If you experience problems connecting to Wi-Fi, see [I can't connect to Wi-Fi](./hololens-faq.md#i-cant-connect-to-wi-fi).
-
-When you sign into an enterprise or organizational account on the device, it may also apply Mobile Device Management (MDM) policy, if the policy is configured by your IT administrator.
-
-## Disabling Wi-Fi on HoloLens (1st gen)
-
-### Using the Settings app on HoloLens
-
-1. Open the **Start** menu.
-1. Select the **Settings** app from **Start** or from the **All Apps** list on the right of the **Start** menu. The **Settings** app will be auto-placed in front of you.
-1. Select **Network & Internet**.
-1. Select the Wi-Fi slider switch to move it to the **Off** position. This will turn off the RF components of the Wi-Fi radio and disable all Wi-Fi functionality on HoloLens.
-
- > [!WARNING]
- > When the Wi-Fi radio is disabled, HoloLens will not be able to automatically load your [spaces](hololens-spaces.md).
-
-1. Move the slider switch to the **On** position to turn on the Wi-Fi radio and restore Wi-Fi functionality on Microsoft HoloLens. The selected Wi-Fi radio state (**On** or **Off**) will persist across reboots.
-
-## Identifying the IP Address of your HoloLens on the Wi-Fi network
-
-### By using the Settings app
-
-1. Open the **Start** menu.
-1. Select the **Settings** app from **Start** or from the **All Apps** list on the right of the **Start** menu. The **Settings** app will be auto-placed in front of you.
-1. Select **Network & Internet**.
-1. Scroll down to beneath the list of available Wi-Fi networks and select **Hardware properties**.
-
- 
-
- The IP address appears next to **IPv4 address**.
-
-### By using Cortana
-
-Say "Hey Cortana, What's my IP address?" and Cortana will display and read out your IP address.
-
-### By using Windows Device Portal
-
-1. In a web browser on your PC, open the [device portal](/windows/mixed-reality/using-the-windows-device-portal.md#networking).
-1. Navigate to the **Networking** section.
- This section displays your IP address and other network information. By using this method, you can copy and paste of the IP address on your development PC.
diff --git a/devices/hololens/hololens-offline.md b/devices/hololens/hololens-offline.md
deleted file mode 100644
index b9ee084421..0000000000
--- a/devices/hololens/hololens-offline.md
+++ /dev/null
@@ -1,163 +0,0 @@
----
-title: Manage connection endpoints for HoloLens
-description: To set up HoloLens, you'll need to connect to a Wi-Fi network
-keywords: hololens, offline, OOBE
-audience: ITPro
-ms.date: 07/01/2019
-ms.assetid: b86f603c-d25f-409b-b055-4bbc6edcd301
-author: Teresa-Motiv
-ms.author: v-tea
-ms.custom:
-- CI 111456
-- CSSTroubleshooting
-manager: jarrettr
-ms.topic: article
-ms.prod: hololens
-ms.sitesec: library
-ms.localizationpriority: high
-appliesto:
-- HoloLens (1st gen)
-- HoloLens 2
----
-
-# Manage connection endpoints for HoloLens
-
-Some HoloLens components, apps, and related services transfer data to Microsoft network endpoints. This article lists different endpoints and URLs that need to be whitelisted in your network configuration (e.g. proxy or firewall) for those components to be functional.
-
-## Near-offline setup
-
-HoloLens supports a limited set of offline experiences for customers who have network environment restrictions. However, HoloLens needs network connection to go through initial device set up and the following URLs have to be enabled:
-
-| Purpose | URL |
-|------|------|
-| IDPS | https://sdx.microsoft.com/frx/idps |
-| [NCSI](https://docs.microsoft.com/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services#bkmk-ncsi) | http://www.msftconnecttest.com/connecttest.txt |
-| AADv9 | https://login.microsoftonline.com/WebApp/CloudDomainJoin/9 |
-| AADv10 | https://login.microsoftonline.com/WebApp/CloudDomainJoin/10 |
-| AAD Pin | https://account.live.com/aadngc?uiflavor=win10&showSuccess=1 |
-| MSA | https://login.live.com/ppsecure/inlineconnect.srf?id=80600 |
-| MSA Pin | https://account.live.com/msangc?fl=enroll |
-
-## Endpoint configuration
-
-In addition to the list above, to take full advantage of HoloLens functionality, the following endpoints need to be enabled in your network configuration.
-
-
-| Purpose | URL |
-|------|------|
-| Azure | wd-prod-fe.cloudapp.azure.com | | |
-| | ris-prod-atm.trafficmanager.net | | | |
-| | validation-v2.sls.trafficmanager.net | | | |
-| Azure AD Multi-Factor Authentication | https://secure.aadcdn.microsoftonline-p.com | | | |
-| Intune and MDM Configurations | activation-v2.sls.microsoft.com/* | | | |
-| | cdn.onenote.net | | | |
-| | client.wns.windows.com | | | |
-| | crl.microsoft.com/pki/crl/* | | | |
-| | ctldl.windowsupdate.com | | | |
-| | *displaycatalog.mp.microsoft.com | | | |
-| | dm3p.wns.windows.com | | | |
-| | *microsoft.com/pkiops/* | | | |
-| | ocsp.digicert.com/* | | | |
-| | r.manage.microsoft.com | | | |
-| | tile-service.weather.microsoft.com | | | |
-| | settings-win.data.microsoft.com | | | |
-| Certificates | activation-v2.sls.microsoft.com/* | | | |
-| | crl.microsoft.com/pki/crl/* | | | |
-| | ocsp.digicert.com/* | | | |
-| | https://www.microsoft.com/pkiops/* | | | |
-| Cortana and Search | store-images.*microsoft.com | | | |
-| | www.bing.com/client | | | |
-| | www.bing.com | | | |
-| | www.bing.com/proactive | | | |
-| | www.bing.com/threshold/xls.aspx | | | |
-| | exo-ring.msedge.net | | | |
-| | fp.msedge.net | | | |
-| | fp-vp.azureedge.net | | | |
-| | odinvzc.azureedge.net | | | |
-| | spo-ring.msedge.net | | | |
-| Device Authentication | login.live.com* | | | |
-| Device metadata | dmd.metaservices.microsoft.com | | | |
-| Location | inference.location.live.net | | | |
-| | location-inference-westus.cloudapp.net | | | |
-| Diagnostic Data | v10.events.data.microsoft.com | | | |
-| | v10.vortex-win.data.microsoft.com/collect/v1 | | | |
-| | https://www.microsoft.com | | | |
-| | co4.telecommand.telemetry.microsoft.com | | | |
-| | cs11.wpc.v0cdn.net | | | |
-| | cs1137.wpc.gammacdn.net | | | |
-| | modern.watson.data.microsoft.com* | | | |
-| | watson.telemetry.microsoft.com | | | |
-| Licensing | licensing.mp.microsoft.com | | | |
-| Microsoft Account | login.msa.akadns6.net | | | |
-| | us.configsvc1.live.com.akadns.net | | | |
-| Microsoft Edge | iecvlist.microsoft.com | | | |
-| Microsoft forward link redirection service (FWLink) | go.microsoft.com | | | |
-| Microsoft Store | *.wns.windows.com | | | |
-| | storecatalogrevocation.storequality.microsoft.com | | | |
-| | img-prod-cms-rt-microsoft-com* | | | |
-| | store-images.microsoft.com | | | |
-| | .md.mp.microsoft.com | | |
-| | *displaycatalog.mp.microsoft.com | | | |
-| | pti.store.microsoft.com | | | |
-| | storeedgefd.dsx.mp.microsoft.com | | | |
-| | markets.books.microsoft.com | | | |
-| | share.microsoft.com | | | |
-| Network Connection Status Indicator (NCSI) | www.msftconnecttest.com* | | | |
-| Office | *.c-msedge.net | | | |
-| | *.e-msedge.net | | | |
-| | *.s-msedge.net | | | |
-| | nexusrules.officeapps.live.com | | | |
-| | ocos-office365-s2s.msedge.net | | | |
-| | officeclient.microsoft.com | | | |
-| | outlook.office365.com | | | |
-| | client-office365-tas.msedge.net | | | |
-| | https://www.office.com | | | |
-| | onecollector.cloudapp.aria | | | |
-| | v10.events.data.microsoft.com/onecollector/1.0/ | | | |
-| | self.events.data.microsoft.com | | | |
-| | to-do.microsoft.com | | | |
-| OneDrive | g.live.com/1rewlive5skydrive/* | | | |
-| | msagfx.live.com | | | |
-| | oneclient.sfx.ms | | | |
-| Photos App | evoke-windowsservices-tas.msedge.net | | | |
-| Settings | cy2.settings.data.microsoft.com.akadns.net | | | |
-| | settings.data.microsoft.com | | | |
-| | settings-win.data.microsoft.com | | | |
-| Windows Defender | wdcp.microsoft.com | | | |
-| | definitionupdates.microsoft.com | | | |
-| | go.microsoft.com | | | |
-| | *smartscreen.microsoft.com | | | |
-| | smartscreen-sn3p.smartscreen.microsoft.com | | | |
-| | unitedstates.smartscreen-prod.microsoft.com | | | |
-| Windows Spotlight | *.search.msn.com | | | |
-| | arc.msn.com | | | |
-| | g.msn.com* | | | |
-| | query.prod.cms.rt.microsoft.com | | | |
-| | ris.api.iris.microsoft.com | | | |
-| Windows Update | *.prod.do.dsp.mp.microsoft.com | | | |
-| | cs9.wac.phicdn.net | | | |
-| | emdl.ws.microsoft.com | | | |
-| | *.dl.delivery.mp.microsoft.com | | | |
-| | *.windowsupdate.com | | | |
-| | *.delivery.mp.microsoft.com | | | |
-| | *.update.microsoft.com | | | |
-
-
-
-## References
-
-> [!NOTE]
-> If you are deploying D365 Remote Assist, you will have to enable the endpoints on this [list](https://docs.microsoft.com/office365/enterprise/urls-and-ip-address-ranges#skype-for-business-online-and-microsoft-teams)
-- [Configure Windows diagnostic data in your organization](https://docs.microsoft.com/windows/privacy/configure-windows-diagnostic-data-in-your-organization)
-- [Manage connection endpoints for Windows 10 Enterprise, version 1903](https://docs.microsoft.com/windows/privacy/manage-windows-1903-endpoints)
-- [Manage connections from Windows 10 operating system components to Microsoft services](https://docs.microsoft.com/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services)
-- [Manage connections from Windows 10 operating system components to Microsoft services using Microsoft Intune MDM Server](https://docs.microsoft.com/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services-using-mdm)
-- [Intune network configuration requirements and bandwidth](https://docs.microsoft.com/intune/fundamentals/network-bandwidth-use#network-communication-requirements)
-- [Network endpoints for Microsoft Intune](https://docs.microsoft.com/intune/fundamentals/intune-endpoints)
-- [Office 365 URLs and IP address ranges](https://docs.microsoft.com/office365/enterprise/urls-and-ip-address-ranges)
-- [Prerequisites for Azure AD Connect](https://docs.microsoft.com/azure/active-directory/hybrid/how-to-connect-install-prerequisites)
-
-
-## HoloLens limitations
-
-After your HoloLens is set up, you can use it without a Wi-Fi connection, but apps that use Internet connections will have limited capabilities when you use HoloLens offline.
diff --git a/devices/hololens/hololens-provisioning.md b/devices/hololens/hololens-provisioning.md
deleted file mode 100644
index 5eea91fcbe..0000000000
--- a/devices/hololens/hololens-provisioning.md
+++ /dev/null
@@ -1,206 +0,0 @@
----
-title: Configure HoloLens by using a provisioning package (HoloLens)
-
-description: Windows provisioning makes it easy for IT administrators to configure end-user devices without imaging.
-ms.prod: hololens
-ms.sitesec: library
-ms.custom:
-- CI 111456
-- CSSTroubleshooting
-author: dansimp
-ms.author: dansimp
-ms.topic: article
-ms.custom:
-- CI 115190
-- CSSTroubleshooting
-ms.localizationpriority: medium
-ms.date: 03/10/2020
-ms.reviewer: Teresa-Motiv
-manager: laurawi
-appliesto:
-- HoloLens (1st gen)
-- HoloLens 2
----
-
-# Configure HoloLens by using a provisioning package
-
-[Windows provisioning](https://docs.microsoft.com/windows/configuration/provisioning-packages/provisioning-packages) makes it easy for IT administrators to configure end-user devices without imaging. Windows Configuration Designer is a tool for configuring images and runtime settings which are then built into provisioning packages.
-
-Some of the HoloLens configurations that you can apply in a provisioning package include the following:
-
-- Upgrade to Windows Holographic for Business [here](hololens1-upgrade-enterprise.md)
-- Set up a local account
-- Set up a Wi-Fi connection
-- Apply certificates to the device
-- Enable Developer Mode
-- Configure Kiosk mode (Detailed instructions for configuring kiosk mode can be found [here](hololens-kiosk.md#set-up-kiosk-mode-using-a-provisioning-package-windows-10-version-1803).
-
-## Provisioning package HoloLens wizard
-
-The HoloLens wizard helps you configure the following settings in a provisioning package:
-
-- Upgrade to the enterprise edition
-
- > [!NOTE]
- > This should only be used for HoloLens 1st gen devices. Settings in a provisioning package are only be applied if the provisioning package includes an edition upgrade license to Windows Holographic for Business or if [the device has already been upgraded to Windows Holographic for Business](hololens1-upgrade-enterprise.md).
-
-- Configure the HoloLens first experience (OOBE)
-- Configure the Wi-Fi network
-- Enroll the device in Azure Active Directory, or create a local account
-- Add certificates
-- Enable Developer Mode
-- Configure kiosk mode (for detailed instructions,see [Set up kiosk mode using a provisioning package](hololens-kiosk.md#set-up-kiosk-mode-using-a-provisioning-package-windows-10-version-1803)
-
-> [!WARNING]
-> You must run Windows Configuration Designer on Windows 10 to configure Azure Active Directory enrollment using any of the wizards.
-
-Provisioning packages can include management instructions and policies, custom network connections and policies, and more.
-
-> [!TIP]
-> Use the desktop wizard to create a package with the common settings, then switch to the advanced editor to add other settings, apps, policies, etc.
-
-## Steps for creating provisioning packages
-
-1. **Option 1:** [From Microsoft Store](https://www.microsoft.com/store/apps/9nblggh4tx22). This includes HoloLens 2 capabilities.
-2. **Option 2:** [From the Windows Assessment and Deployment Kit (ADK) for Windows 10](https://developer.microsoft.com/windows/hardware/windows-assessment-deployment-kit). If you install Windows Configuration Designer from the Windows ADK, select **Configuration Designer** from the **Select the features you want to install** dialog box. This option does not include HoloLens 2 capabilities.
-
-
-### 2. Create the provisioning package
-
-Use the Windows Configuration Designer tool to create a provisioning package.
-
-1. Open Windows Configuration Designer (by default, %windir%\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Imaging and Configuration Designer\x86\ICD.exe).
-
-2. Select **Provision HoloLens devices**.
-
- 
-
-3. Name your project and select **Finish**.
-
-4. Read the instructions on the **Getting started** page and select **Next**. The pages for desktop provisioning walk you through the following steps.
-
-> [!IMPORTANT]
-> When you build a provisioning package, you may include sensitive information in the project files and in the provisioning package (.ppkg) file. Although you have the option to encrypt the .ppkg file, project files are not encrypted. You should store the project files in a secure location and delete the project files when they are no longer needed.
-
-### Configure settings
-
-
-
Browse to and select the enterprise license file to upgrade the HoloLens edition.You can also toggle Yes or No to hide parts of the first experience.To set up the device without the need to connect to a Wi-Fi network, toggle Skip Wi-Fi setup to On.Select a region and timezone in which the device will be used.
-
In this section, you can enter the details of the Wi-Fi wireless network that the device should automatically connect to. To do this, select On, enter the SSID, the network type (Open or WPA2-Personal), and (if WPA2-Personal) the password for the wireless network.
-
You can enroll the device in Azure Active Directory, or create a local account on the deviceBefore you use a Windows Configuration Designer wizard to configure bulk Azure AD enrollment, set up Azure AD join in your organization. The maximum number of devices per user setting in your Azure AD tenant determines how many times the bulk token that you get in the wizard can be used. To enroll the device in Azure AD, select that option and enter a friendly name for the bulk token you will get using the wizard. Set an expiration date for the token (maximum is 30 days from the date you get the token). Select Get bulk token. In the Let's get you signed in window, enter an account that has permissions to join a device to Azure AD, and then the password. Select Accept to give Windows Configuration Designer the necessary permissions. To create a local account, select that option and enter a user name and password. Important: (For Windows 10, version 1607 only) If you create a local account in the provisioning package, you must change the password using the Settings app every 42 days. If the password is not changed during that period, the account might be locked out and unable to sign in.
-
To provision the device with a certificate, click Add a certificate. Enter a name for the certificate, and then browse to and select the certificate to be used.
Do not set a password to protect your provisioning package. If the provisioning package is protected by a password, provisioning the HoloLens device will fail.
-
-
-After you're done, select **Create**. It only takes a few seconds. When the package is built, the location where the package is stored is displayed as a hyperlink at the bottom of the page.
-
-### 3. Create a provisioning package for HoloLens by using advanced provisioning
-
-> [!NOTE]
-> A provisioning package that you create in **Advanced provisioning** does not need to include an edition upgrade license to Windows Holographic for Business to succesfully apply to a HoloLens (1st gen). [See more on Windows Holographic for Business for HoloLens (1st gen)](hololens1-upgrade-enterprise.md).
-
-1. On the Windows Configuration Designer start page, select **Advanced provisioning**.
-2. In the **Enter project details** window, specify a name for your project and the location for your project. Optionally, enter a brief description to describe your project.
-
-3. Select **Next**.
-
-4. In the **Choose which settings to view and configure** window, select **Windows 10 Holographic**, and then select **Next**.
-
-5. Select **Finish**.
-
-6. Expand **Runtime settings** and customize the package by using any of the settings [described later in this article](#what-you-can-configure).
-
- > [!IMPORTANT]
- > (For Windows 10, version 1607 only) If you create a local account in the provisioning package, you must change the password using the **Settings** app every 42 days. If the password is not changed during that period, the account might be locked out and unable to sign in. If the user account is locked out, you must [perform a full device recovery](https://developer.microsoft.com/windows/mixed-reality/reset_or_recover_your_hololens#perform_a_full_device_recovery).
-
-7. Select **File** > **Save**.
-
-8. Read the warning that project files may contain sensitive information, and select **OK**.
-
- > [!IMPORTANT]
- > When you build a provisioning package, you may include sensitive information in the project files and in the provisioning package (.ppkg) file. Although you have the option to encrypt the .ppkg file, project files are not encrypted. You should store the project files in a secure location and delete the project files when they are no longer needed.
-
-9. Select **Export** > **Provisioning package**.
-
-10. Change **Owner** to **IT Admin**. This sets the precedence of this provisioning package higher than provisioning packages applied to this device from other sources. Select **Next**.
-
-11. Set a value for **Package Version**.
-
- > [!TIP]
- > You can make changes to existing packages and change the version number to update previously applied packages.
-
-12. On the **Select security details for the provisioning package**, select **Next**.
-
- > [!WARNING]
- > If you encrypt the provisioning package, provisioning the HoloLens device will fail.
-
-13. Select **Next** to specify the output location where you want the provisioning package to go once it's built. By default, Windows Configuration Designer uses the project folder as the output location.
-
- Optionally, you can select **Browse** to change the default output location.
-
-14. Select **Next**.
-
-15. Select **Build** to start building the package. The project information is displayed in the build page and the progress bar indicates the build status.
-
-16. When the build completes, select **Finish**.
-
-
-
-## Apply a provisioning package to HoloLens during setup
-
-1. Use the USB cable to connect the device to a PC, and then start the device. Do not continue past the **First interactable moment** page of OOBE.
- - On HoloLens (1st gen), this page contains a blue box.
- - On HoloLens 2, this page contains the hummingbird.
-
-2. Briefly press and release the **Volume Down** and **Power** buttons simultaneously.
-
-3. HoloLens shows up as a device in File Explorer on the PC.
-
-4. In File Explorer, drag and drop the provisioning package (.ppkg) onto the device storage.
-
-5. Briefly press and release the **Volume Down** and **Power** buttons simultaneously again while on the **fit** page.
-
-6. The device asks you if you trust the package and would like to apply it. Confirm that you trust the package.
-
-7. You will see whether the package was applied successfully or not. If it failed, you can fix your package and try again. If it succeeded, proceed with OOBE.
-
-> [!NOTE]
-> If the device was purchased before August 2016, you will need to sign in to the device by using a Microsoft account, get the latest operating system update, and then reset the operating system in order to apply the provisioning package.
-
-### 4. Apply a provisioning package to HoloLens after setup
-
-> [!NOTE]
-> These steps apply only toWindows 10, version 1809.
-
-On your PC, follow these steps:
-1. Create a provisioning package as described at [Create a provisioning package for HoloLens using the HoloLens wizard](hololens-provisioning.md).
-2. Connect the HoloLens device to a PC by using a USB cable. HoloLens shows up as a device in File Explorer on the PC.
-3. Drag and drop the provisioning package to the Documents folder on the HoloLens.
-
-On your HoloLens, follow these steps:
-1. Go to **Settings** > **Accounts** > **Access work or school**.
-2. In **Related Settings**, select **Add or remove a provisioning package**.
-3. On the next page, select **Add a package** to launch the file picker and select your provisioning package. If the folder is empty, make sure you select **This Device** and select **Documents**.
-
-After your package has been applied, it shows up in the list of **Installed packages**. To view the package details or to remove the package from the device, select the listed package.
-
-## What you can configure
-
-Provisioning packages make use of configuration service providers (CSPs). If you're not familiar with CSPs, see [Introduction to configuration service providers (CSPs) for IT pros](https://docs.microsoft.com/windows/configuration/provisioning-packages/how-it-pros-can-use-configuration-service-providers).
-
-In Windows Configuration Designer, when you create a provisioning package for Windows Holographic, the settings in **Available customizations** are based on [CSPs that are supported in Windows Holographic](https://docs.microsoft.com/windows/client-management/mdm/configuration-service-provider-reference#csps-supported-in-hololens-devices). The following table describes settings that you might want to configure for HoloLens.
-
-
-
-| Setting | Description |
-| --- | --- |
-| **Certificates** | Deploy a certificate to HoloLens. |
-| **ConnectivityProfiles** | Deploy a Wi-Fi profile to HoloLens. |
-| **EditionUpgrade** | [Upgrade to Windows Holographic for Business.](hololens1-upgrade-enterprise.md) |
-| **Policies** | Allow or prevent developer mode on HoloLens. [Policies supported by Windows Holographic for Business](https://docs.microsoft.com/windows/client-management/mdm/policy-configuration-service-provider#hololenspolicies) |
-
-> [!NOTE]
-> HoloLens does not currently support installing apps (**UniversalAppInstall**) by using a provisioning package.
-
-## Next Step: [Enroll your device](hololens-enroll-mdm.md)
diff --git a/devices/hololens/hololens-recovery.md b/devices/hololens/hololens-recovery.md
deleted file mode 100644
index 60d46d7e1c..0000000000
--- a/devices/hololens/hololens-recovery.md
+++ /dev/null
@@ -1,134 +0,0 @@
----
-title: Restart, reset, or recover HoloLens
-ms.reviewer: Both basic and advanced instructions for rebooting or resetting your HoloLens.
-description: How to use Advanced Recovery Companion to flash an image to HoloLens 2.
-keywords: how-to, reboot, reset, recover, hard reset, soft reset, power cycle, HoloLens, shut down, arc, advanced recovery companion
-ms.prod: hololens
-ms.sitesec: library
-author: mattzmsft
-ms.author: mazeller
-ms.date: 08/30/2019
-ms.custom:
-- CI 111456
-- CSSTroubleshooting
-ms.topic: article
-ms.localizationpriority: high
-manager: jarrettr
-appliesto:
-- HoloLens (1st gen)
-- HoloLens 2
----
-
-# Restart, reset, or recover HoloLens
-
-If you're experiencing problems with your HoloLens you may want to try a restart, reset, or even re-flash with device recovery.
-
-Here are some things to try if your HoloLens isn't running well. This article will guide you through the recommended recovery steps in succession.
-
-This article focuses on the HoloLens device and software, if your holograms don't look right, [this article](hololens-environment-considerations.md) talks about environmental factors that improve hologram quality.
-
-## Restart your HoloLens
-
-First, try restarting the device.
-
-### Perform a safe restart by using Cortana
-
-The safest way to restart the HoloLens is by using Cortana. This is generally a great first-step when experiencing an issue with HoloLens:
-
-1. Put on your device
-1. Make sure it's powered on, a user is logged in, and the device is not waiting for a password to unlock it.
-1. Say "Hey Cortana, reboot" or "Hey Cortana, restart."
-1. When she acknowledges she will ask you for confirmation. Wait a second for a sound to play after she has finished her question, indicating she is listening to you and then say "Yes."
-1. The device will now restart.
-
-### Perform a safe restart by using the power button
-
-If you still can't restart your device, you can try to restart it by using the power button:
-
-1. Press and hold the power button for five seconds.
- 1. After one second, you will see all five LEDs illuminate, then slowly turn off from right to left.
- 1. After five seconds, all LEDs will be off, indicating the shutdown command was issued successfully.
- 1. Note that it's important to stop pressing the button immediately after all the LEDs have turned off.
-1. Wait one minute for the shutdown to cleanly succeed. Note that the shutdown may still be in progress even if the displays are turned off.
-1. Power on the device again by pressing and holding the power button for one second.
-
-### Perform a safe restart by using Windows Device Portal
-
-> [!NOTE]
-> To do this, HoloLens has to be configured as a developer device.
-> Read more about [Windows Device Portal](https://docs.microsoft.com/windows/mixed-reality/using-the-windows-device-portal).
-
-If the previous procedure doesn't work, you can try to restart the device by using [Windows Device Portal](https://docs.microsoft.com/windows/mixed-reality/using-the-windows-device-portal). In the upper right corner, there is an option to restart or shut down the device.
-
-### Perform an unsafe forced restart
-
-If none of the previous methods are able to successfully restart your device, you can force a restart. This method is equivalent to pulling the battery from the HoloLens. It is a dangerous operation which may leave your device in a corrupt state. If that happens, you'll have to flash your HoloLens.
-
-> [!WARNING]
-> This is a potentially harmful method and should only be used in the event none of the above methods work.
-
-1. Press and hold the power button for at least 10 seconds.
-
- - It's okay to hold the button for longer than 10 seconds.
- - It's safe to ignore any LED activity.
-1. Release the button and wait for two or three seconds.
-1. Power on the device again by pressing and holding the power button for one second.
-If you're still having problems, press the power button for 4 seconds, until all of the battery indicators fade out and the screen stops displaying holograms. Wait 1 minute, then press the power button again to turn on the device.
-
-## Reset to factory settings
-
-> [!NOTE]
-> The battery needs at least 40 percent charge to reset.
-
-If your HoloLens is still experiencing issues after restarting, try resetting it to factory state. Resetting your HoloLens keeps the version of the Windows Holographic software that's installed on it and returns everything else to factory settings.
-
-If you reset your device, all your personal data, apps, and settings will be erased. Resetting will only install the latest installed version of Windows Holographic and you will have to redo all the initialization steps (calibrate, connect to Wi-Fi, create a user account, download apps, and so forth).
-
-1. Launch the Settings app, and then select **Update** > **Reset**.
-1. Select the **Reset device** option and read the confirmation message.
-1. If you agree to reset your device, the device will restart and display a set of spinning gears with a progress bar.
-1. Wait about 30 minutes for this process to complete.
-1. The reset will complete and the device will restart into the out-of-the-box experience.
-
-## Re-install the operating system
-
-If the device is still having a problem after rebooting and resetting, you can use a recovery tool on your computer to reinstall the HoloLens' operating system and firmware.
-
-HoloLens (1st gen) and HoloLens 2 use different tools but both tools will auto-detect your HoloLens and install new software.
-
-All of the data HoloLens needs to reset is packaged in a Full Flash Update (ffu). This is similar to an iso, wim, or vhd. [Learn about FFU image file formats.](https://docs.microsoft.com/windows-hardware/manufacture/desktop/wim-vs-ffu-image-file-formats)
-
-### HoloLens 2
-
-The Advanced Recovery Companion is a new app in Microsoft Store restore the operating system image to your HoloLens 2 device.
-
-1. On your computer, get [Advanced Recovery Companion](https://www.microsoft.com/p/advanced-recovery-companion/9p74z35sfrs8?activetab=pivot:overviewtab) from Microsoft Store.
-2. Connect HoloLens 2 to your computer.
-3. Start Advanced Recovery Companion.
-4. On the **Welcome** page, select your device.
-5. On the **Device info** page, select **Install software** to install the default package. (If you have a Full Flash Update (FFU) image that you want to install instead, select **Manual package selection**.)
-6. Software installation will begin. Do not use the device or disconnect the cable during installation. When you see the **Installation finished** page, you can disconnect and use your device.
-
-> [!TIP]
-> In the event that a HoloLens 2 gets into a state where Advanced Recovery Companion cannot recognize the device, and it does not boot, try forcing the device into Flashing Mode and recovering it with Advanced Recovery Companion:
-
-1. Connect the HoloLens 2 to a PC with Advanced Recovery Companion installed.
-1. Press and hold the **Volume Up and Power buttons** until the device reboots. Release the Power button, but continue to hold the Volume Up button until the third LED is lit.
-1. The device should be visible in **Device Manager** as a **Microsoft HoloLens Recovery** device.
-1. Launch Advanced Recovery Companion, and follow the on-screen prompts to reflash the OS to the HoloLens 2.
-
-### HoloLens (1st gen)
-
-If necessary, you can install a completely new operating system on your HoloLens (1st gen) with the Windows Device Recovery Tool.
-
-Before you use this tool, determine if restarting or resetting your HoloLens fixes the problem. The recovery process may take some time. When you're done, the latest version of the Windows Holographic software approved for your HoloLens will be installed.
-
-To use the tool, you'll need a computer running Windows 10 or later, with at least 4 GB of free storage space. Please note that you can't run this tool on a virtual machine.
-
-To recover your HoloLens
-
-1. Download and install the [Windows Device Recovery Tool](https://support.microsoft.com/help/12379/windows-10-mobile-device-recovery-tool-faq) on your computer.
-1. Connect the HoloLens (1st gen) to your computer using the Micro USB cable that came with your HoloLens.
-1. Run the Windows Device Recovery Tool and follow the instructions.
-
-If the HoloLens (1st gen) isn't automatically detected, select **My device was not detected** and follow the instructions to put your device into recovery mode.
diff --git a/devices/hololens/hololens-release-notes.md b/devices/hololens/hololens-release-notes.md
deleted file mode 100644
index b289b56df1..0000000000
--- a/devices/hololens/hololens-release-notes.md
+++ /dev/null
@@ -1,150 +0,0 @@
----
-title: HoloLens release notes
-description: Learn about updates in each new HoloLens release.
-author: scooley
-ms.author: scooley
-manager: laurawi
-ms.prod: hololens
-ms.sitesec: library
-ms.topic: article
-ms.localizationpriority: medium
-ms.date: 12/02/2019
-ms.custom:
-- CI 111456
-- CSSTroubleshooting
-audience: ITPro
-appliesto:
-- HoloLens 1
-- HoloLens 2
-
----
-
-# HoloLens release notes
-
-## HoloLens 2
-
-> [!Note]
-> HoloLens Emulator Release Notes can be found [here](https://docs.microsoft.com/windows/mixed-reality/hololens-emulator-archive).
-
-### April Update - build 18362.1059
-
-**Dark mode for supported apps**
-
-Many Windows apps support both dark and light modes, and soon HoloLens 2 customers can choose the default mode for apps that support both color schemes! Based on overwhelmingly positive customer feedback, with this update we are setting the default app mode to "dark," but you can easily change this setting at any time.
-Navigate to **Settings > System > Colors** to find **"Choose your default app mode."**
-
-Here are some of the in-box apps that support dark mode:
-- Settings
-- Microsoft Store
-- Mail
-- Calendar
-- File Explorer
-- Feedback Hub
-- OneDrive
-- Photos
-- 3D Viewer
-- Movies & TV
-
-**Improvements and fixes also in the update:**
-- Ensure shell overlays are included in mixed reality captures.
-- Unreal developers are now able to use the 3D View page in Device Portal to test and debug their applications.
-- Improve hologram stability in mixed reality capture when the HolographicDepthReprojectionMethod DepthReprojection algorithm is used.
-- Fixed WinRT IStreamSocketListener API Class Not Registered error on 32-bit ARM app.
-
-### March Update - build 18362.1056
-
-- Improve hologram stability in mixed reality capture when the HolographicDepthReprojectionMethod AutoPlanar algorithm is used.
-- Ensures the coordinate system attached to a depth MF sample is consistent with public documentation.
-- Developers productivity improvement by enabling customers to paste large amount of text through device portal.
-
-### February Update - build 18362.1053
-
-- Temporarily disabled the HolographicSpace.UserPresence API for Unity applications to avoid an issue which causes some apps to pause when the visor is flipped up, even if the setting to run in the background is enabled.
-- Fixed a random HUP crash cased by hand tracking, in which user will notice an UI freeze then back to shell after several seconds.
-- We made an improvement in hand tracking so that while poking using index finger, the upper part of that finger will be less likely to curl unexpectedly.
-- Improved reliability of head tracking, spatial mapping, and other runtimes.
-
-### January Update - build 18362.1043
-
-- Stability improvements for exclusive apps when working with the HoloLens 2 emulator.
-
-### December Update - build 18362.1042
-
-- Introduces LSR (Last Stage Reproduction) fixes. Improves visual rendering of holograms to appear more stable and crisp by more accurately accounting for their depth. This will be more noticeable if apps do not set the depth of holograms correctly, after this update.
-- Fixes stability of exclusive apps and navigation between exclusive apps.
-- Resolves an issue where Mixed Reality Capture couldn't record video after device is left in standby state for multiple days.
-- Improves hologram stability.
-
-### November Update - build 18362.1039
-
-- Fixes for **"Select"** voice commands during initial set-up for en-CA and en-AU.
-- Improvements in visual quality of objects placed far away in latest Unity and MRTK versions.
-- Fixes addressing issues with holographic applications being stuck in a paused state on launch until the pins panel is brought up and dismissed again.
-- OpenXR runtime conformance fixes and improvements for HoloLens 2 and the emulator.
-
-## HoloLens (1st gen)
-
-### Windows 10 Holographic, version 1809
-
-> **Applies to:** Hololens (1st gen)
-
-| Feature | Details |
-|---|---|
-| **Quick actions menu** | When you're in an app, the Bloom gesture will now open a Quick actions menu to give you quick access to commonly used system features without having to leave the app. See [Set up HoloLens in kiosk mode](hololens-kiosk.md) for information about the Quick actions menu in kiosk mode.
 |
-| **Stop video capture from the Start or quick actions menu** | If you start video capture from the Start menu or quick actions menu, you'll be able to stop recording from the same place. (Don't forget, you can always do this with voice commands too.) |
-| **Project to a Miracast-enabled device** | Project your HoloLens content to a nearby Surface device or TV/Monitor if using Microsoft Display adapter. On **Start**, select **Connect**, and then select the device you want to project to. **Note:** You can deploy HoloLens to use Miracast projection without enabling developer mode. |
-| **New notifications** | View and respond to notification toasts on HoloLens, just like you do on a PC. Gaze to respond to or dismiss them (or if you're in an immersive experience, use the bloom gesture). |
-| **HoloLens overlays** (file picker, keyboard, dialogs, etc.) | You'll now see overlays such as the keyboard, dialogs, file picker, etc. when using immersive apps. |
-| **Visual feedback overlay UI for volume change** | When you use the volume up/down buttons on your HoloLens you'll see a visual display of the volume level. |
-| **New UI for device boot** | A loading indicator was added during the boot process to provide visual feedback that the system is loading. Reboot your device to see the new loading indicator—it's between the "Hello" message and the Windows boot logo. |
-| **Nearby sharing** | Addition of the Windows Nearby Sharing experience, allowing you to share a capture with a nearby Windows device. When you capture a photo or video on HoloLens (or use the share button from an app such as Microsoft Edge), select a nearby Windows device to share with. |
-| **Share from Microsoft Edge** | Share button is now available on Microsoft Edge windows on HoloLens. In Microsoft Edge, select **Share**. Use the HoloLens share picker to share web content. |
-
-#### For international customers
-
-| Feature | Details |
-| --- | --- |
-| Localized Chinese and Japanese builds | Use HoloLens with localized user interface for Simplified Chinese or Japanese, including localized Pinyin keyboard, dictation, and voice commands. [Learn how to install the Chinese and Japanese versions of HoloLens.](hololens1-install-localized.md) |
-| Speech Synthesis (TTS) | Speech synthesis feature now supports Chinese, Japanese, and English. |
-
-#### For administrators
-
-| Feature | Details |
-|---|----|
-| [Enable post-setup provisioning](hololens-provisioning.md) | You can now apply a runtime provisioning package at any time using **Settings**. |
-| Assigned access with Azure AD groups | You can now use Azure AD groups for configuration of Windows assigned access to set up single or multi-app kiosk configuration. |
-| PIN sign-in on profile switch from sign-in screen | PIN sign-in is now available for **Other User**. |
-| Sign in with Web Credential Provider using password | You can now select the Globe sign-in option to launch web sign-in with your password. From the sign-in screen, select **Sign-In options** and select the Globe option to launch web sign-in. Enter your user name if needed, then your password. **Note:** You can choose to bypass any PIN/Smartcard options when prompted during web sign-in. |
-| Read device hardware info through MDM so devices can be tracked by serial number | IT administrators can see and track HoloLens by device serial number in their MDM console. Refer to your MDM documentation for feature availability and instructions. |
-| Set HoloLens device name through MDM (rename) | IT administrators can see and rename HoloLens devices in their MDM console. Refer to your MDM documentation for feature availability and instructions. |
-
-### Windows 10, version 1803 for Microsoft HoloLens
-
-> **Applies to:** Hololens (1st gen)
-
-Windows 10, version 1803, is the first feature update to Windows Holographic for Business since its release in Windows 10, version 1607. This update introduces the following changes:
-
-- Previously, you could only verify that upgrade license for Commercial Suite had been applied to your HoloLens device by checking to see if VPN was an available option on the device. Now, **Settings** > **System** will display **Windows Holographic for Business** after the upgrade license is applied. [Learn how to unlock Windows Holographic for Business features](hololens1-upgrade-enterprise.md).
-
-- You can view the operating system build number in device properties in the File Explorer app and in the [Windows Device Recovery Tool (WDRT)](https://support.microsoft.com/help/12379/windows-10-mobile-device-recovery-tool-faq).
-- Provisioning a HoloLens device is now easier with the new **Provision HoloLens devices** wizard in the Windows Configuration Designer tool. In the wizard, you can configure the setup experience and network connections, set developer mode, and obtain bulk Azure AD tokens. [Learn how to use the simple provisioning wizard for HoloLens](hololens-provisioning.md#provisioning-package-hololens-wizard).
-
- 
-
-- When you create a local account in a provisioning package, the password no longer expires every 42 days.
-
-- You can [configure HoloLens as a single-app or multi-app kiosk](hololens-kiosk.md). Multi-app kiosk mode lets you set up a HoloLens to only run the apps that you specify, and prevents users from making changes.
-
-- Media Transfer Protocol (MTP) is enabled so that you can connect the HoloLens device to a PC by USB and transfer files between HoloLens and the PC. You can also use the File Explorer app to move and delete files from within HoloLens.
-
-- Previously, after you signed in to the device with an Azure Active Directory (Azure AD) account, you then had to **Add work access** in **Settings** to get access to corporate resources. Now, you sign in with an Azure AD account and enrollment happens automatically.
-
-- Before you sign in, you can choose the network icon below the password field to choose a different Wi-Fi network to connect to. You can also connect to a guest network, such as at a hotel, conference center, or business.
-
-- You can now easily [share HoloLens with multiple people](hololens-multiple-users.md) using Azure AD accounts.
-
-- When setup or sign-in fails, choose the new **Collect info** option to get diagnostic logs for troubleshooting.
-
-- Individual users can sync their corporate email without enrolling their device in mobile device management (MDM). You can use the device with a Microsoft Account, download and install the Mail app, and add an email account directly.
-
-- You can check the MDM sync status for a device in **Settings** > **Accounts** > **Access Work or School** > **Info**. In the **Device sync status** section, you can start a sync, see areas managed by MDM, and create and export an advanced diagnostics report.
diff --git a/devices/hololens/hololens-requirements.md b/devices/hololens/hololens-requirements.md
deleted file mode 100644
index 6cfcb281b0..0000000000
--- a/devices/hololens/hololens-requirements.md
+++ /dev/null
@@ -1,118 +0,0 @@
----
-title: Set up HoloLens in a commercial environment
-description: Learn more about deploying and managing HoloLens in enterprise environments.
-ms.prod: hololens
-ms.sitesec: library
-ms.assetid: 88bf50aa-0bac-4142-afa4-20b37c013001
-author: scooley
-ms.author: scooley
-audience: ITPro
-ms.topic: article
-ms.localizationpriority: medium
-ms.date: 07/15/2019
----
-
-# Deploy HoloLens in a commercial environment
-
-You can deploy and configure HoloLens at scale in a commercial setting. This article provides instructions for deploying HoloLens devices in a commercial environment. This guide assumes basic familiarity with HoloLens. Follow the [get started guide](hololens1-setup.md) to set up HoloLens for the first time.
-
-This document also assumes that the HoloLens has been evaluated by security teams as safe to use on the corporate network. Frequently asked security questions can be found [here](hololens-faq-security.md)
-
-## Overview of Deployment Steps
-
-1. [Determine what features you need](hololens-requirements.md#step-1-determine-what-you-need)
-1. [Determine what licenses you need](hololens-licenses-requirements.md)
-1. [Configure your network for HoloLens](hololens-commercial-infrastructure.md).
- 1. This section includes bandwidth requirements, URL, and ports that need to be whitelisted on your firewall; Azure AD guidance; Mobile Device Management (MDM) Guidance; app deployment/management guidance; and certificate guidance.
-1. (Optional) [Configure HoloLens using a provisioning package](hololens-provisioning.md)
-1. [Enroll Device](hololens-enroll-mdm.md)
-1. [Set up ring based updates for HoloLens](hololens-updates.md)
-1. [Enable Bitlocker device encryption for HoloLens](hololens-encryption.md)
-
-## Step 1. Determine what you need
-
-Before deploying the HoloLens in your environment, it is important to first determine what features, apps, and type of identities are needed. It is also important to ensure that your security team has approved of the use of the HoloLens on the company's network. Please see [Frequently ask security questions](hololens-faq-security.md) for additional security information.
-
-### Type of Identity
-
-Determine the type of identity that will be used to sign into the device.
-
-1. **Local Accounts:** This account is local to the device (like a local admin account on a windows PC). This will allow only 1 user to log into the device.
-2. **MSA:** This is a personal account (like outlook, hotmail, gmail, yahoo, etc.) This will allow only 1 user to log into the device.
-3. **Azure Active Directory (Azure AD) accounts:** This is an account created in Azure AD. This grants your corporation the ability to manage the HoloLens device. This will allow multiple users to log into the HoloLens 1st Gen Commercial Suite/the HoloLens 2 device.
-
-For more detailed information about identity types, please visit our [HoloLens Identity](hololens-identity.md) article.
-
-### Type of Features
-
-Your feature requirements will determine which HoloLens you need. One popular feature that we see deployed in customer environments frequently is Kiosk Mode. A list of HoloLens key features, and the editions of HoloLens that support them, can be found [here](hololens-commercial-features.md).
-
-**What is Kiosk Mode?**
-
-Kiosk mode is a way to restrict the apps that a user has access to. This means that users will only be allowed to access certain apps.
-
-**What Kiosk Mode do I require?**
-
-There are two types of Kiosk Modes: Single app and multi-app. Single app kiosk mode allows user to only access one app while multi-app kiosk mode allows users to access multiple, specified apps. To determine which kiosk mode is right for your corporation, the following two questions need to be answered:
-
-1. **Do different users require different experiences/restrictions?** Consider the following example: User A is a field service engineer who only needs access to Remote Assist. User B is a trainee who only needs access to Guides.
- 1. If yes, you will require the following:
- 1. Azure AD Accounts as the method of signing into the device.
- 1. **Multi-app** kiosk mode.
- 1. If no, continue to question two
-1. **Do you require a multi-app experience?**
- 1. If yes, **Multi-app** kiosk is mode is needed
- 1. If your answer to question 1 and 2 are both no, **single-app** kiosk mode can be used
-
-**How to Configure Kiosk Mode:**
-
-There are two main ways ([provisioning packages](hololens-kiosk.md#set-up-kiosk-mode-using-a-provisioning-package-windows-10-version-1803) and [MDM](hololens-kiosk.md#set-up-kiosk-mode-using-microsoft-intune-or-mdm-windows-10-version-1803)) to deploy kiosk mode for HoloLens. These options will be discussed later in the document; however, you can use the links above to jump to the respective sections in this doc.
-
-### Apps and App Specific Scenarios
-
-The majority of the steps found in this document will also apply to the following apps:
-
-| App | App Specific Scenarios |
-| --- | --- |
-| Remote Assist | [Cross Tenant Communication](https://docs.microsoft.com/dynamics365/mixed-reality/remote-assist/cross-tenant-overview)|
-| Guides | *Coming Soon* |
-|Custom Apps | *Coming Soon* |
-
-### Determine your enrollment method
-
-1. Bulk enrollment with a security token in a provisioning package.
- Pros: this is the most automated approach\
- Cons: takes initial server-side setup
-1. Auto-enroll on user sign in.
- Pros: easiest approach
- Cons: users will need to complete set up after the provisioning package has been applied
-1. _not recommended_ - Manually enroll post-setup.
- Pros: possible to enroll after set up
- Cons: most manual approach and devices aren't centrally manageable until they're manually enrolled.
-
- More information can be found [here](hololens-enroll-mdm.md)
-
-### Determine if you need to create a provisioning package
-
-There are two methods to configure a HoloLens device (Provisioning packages and MDMs). We suggest using your MDM to configure you HoloLens device. However, there are some scenarios where using a provisioning package is the better choice:
-
-1. You want to configure the HoloLens to skip the Out of Box Experience (OOBE)
-1. You are having trouble deploying certificate in a complex network. The majority of the time you can deploy certificates using MDM (even in complex environments). However, some scenarios require certificates to be deployed through the provisioning package.
-
-Some of the HoloLens configurations you can apply in a provisioning package:
-
-- Apply certificates to the device
-- Set up a Wi-Fi connection
-- Pre-configure out of box questions like language and locale
-- (HoloLens 2) bulk enroll in mobile device management
-- (HoloLens v1) Apply key to enable Windows Holographic for Business
-
-If you decide to use provisioning packages, follow [this guide](hololens-provisioning.md).
-
-## Next Step: [Determine what licenses you need](hololens-licenses-requirements.md)
-
-## Get support
-
-Get support through the Microsoft support site.
-
-[File a support request](https://support.microsoft.com/supportforbusiness/productselection?sapid=e9391227-fa6d-927b-0fff-f96288631b8f)
diff --git a/devices/hololens/hololens-spaces.md b/devices/hololens/hololens-spaces.md
deleted file mode 100644
index 485e56773e..0000000000
--- a/devices/hololens/hololens-spaces.md
+++ /dev/null
@@ -1,117 +0,0 @@
----
-title: Map physical spaces with HoloLens
-description: HoloLens learns what a space looks like over time. Users can facilitate this process by moving the HoloLens in certain ways through the space.
-ms.assetid: bd55ecd1-697a-4b09-8274-48d1499fcb0b
-author: dorreneb
-ms.author: dobrown
-ms.custom:
-- CI 111456
-- CSSTroubleshooting
-ms.date: 09/16/2019
-keywords: hololens, Windows Mixed Reality, design, spatial mapping, HoloLens, surface reconstruction, mesh, head tracking, mapping
-ms.prod: hololens
-ms.sitesec: library
-ms.topic: article
-ms.localizationpriority: high
-appliesto:
-- HoloLens 1 (1st gen)
-- HoloLens 2
----
-
-# Map physical spaces with HoloLens
-
-HoloLens blends holograms with your physical world. To do that, HoloLens has to learn about the physical world around you and remember where you place holograms within that space.
-
-Over time, the HoloLens builds up a *spatial map* of the environment that it has seen. HoloLens updates the map as the environment changes. As long as you are logged in and the device is turned on, HoloLens creates and updates your spatial maps. If you hold or wear the device with the cameras pointed at a space, the HoloLens tries to map the area. While the HoloLens learns a space naturally over time, there are ways in which you can help HoloLens map your space more quickly and efficiently.
-
-> [!NOTE]
-> If your HoloLens can't map your space or is out of calibration, HoloLens may enter Limited mode. In Limited mode, you won't be able to place holograms in your surroundings.
-
-This article explains how HoloLens maps spaces, how to improve spatial mapping, and how to manage the spatial data that HoloLens collects.
-
-## Choosing and setting up and your space
-
-Features in your environment can make it difficult for the HoloLens to interpret a space. Light levels, materials in the space, the layout of objects, and more can all affect how HoloLens maps an area.
-
-HoloLens works best in certain kinds of environments. To produce the best spatial map, choose a room that has adequate light and plenty of space. Avoid dark spaces and rooms that have a lot of dark, shiny, or translucent surfaces (for instance, mirrors or gauzy curtains).
-
-HoloLens is optimized for indoor use. Spatial mapping also works best when Wi-Fi is turned on, although it doesn't have to be connected to a network. HoloLens can obtain Wi-Fi access points even if it is not connected or authenticated. HoloLens functionality does not change whether the access points are internet-connected or intranet/local only.
-
-Only use HoloLens in safe places with no tripping hazards. [More on safety](https://support.microsoft.com/help/4023454/safety-information).
-
-## Mapping your space
-
-Now you're ready to start mapping your spare. When HoloLens starts mapping your surroundings, you'll see a mesh graphic spreading over the space. In mixed reality home, you can trigger the map to show by selecting on a mapped surface.
-
-Here are guidelines for building a great spatial map.
-
-### Understand the scenarios for the area
-
-It is important to spend the most time where you will be using the HoloLens, so that the map is relevant and complete. For example, if a user scenario for HoloLens involves moving from Point A to Point B, walk that path two to three times, looking in all directions as you move.
-
-### Walk slowly around the space
-
-If you walk too quickly around the area, it's likely that the HoloLens will miss mapping areas. Walk slowly around the space, stopping every 5-8 feet to look around at your surroundings.
-
-Smooth movements also help the HoloLens map more efficiently.
-
-### Look in all directions
-
-Looking around as you map the space gives the HoloLens more data on where points are relative to each other.
-
-If you don't look up, for example, the HoloLens may not know where the ceiling in a room is.
-
-Don't forget to look down at the floor as you map the space.
-
-### Cover key areas multiple times
-
-Moving through an area multiple times will help pick up features you may have missed on the first walkthrough. To build an ideal map, try traversing an area two to three times.
-
-If possible, while repeating these movements, spend time walking through an area in one direction, then turn around and walk back the way you came.
-
-### Take your time mapping the area
-
-It can take between 15 and 20 minutes for the HoloLens to fully map and adjust itself to its surroundings. If you have a space in which you plan to use a HoloLens frequently, taking that time up front to map the space can prevent issues later on.
-
-## Possible errors in the spatial map
-
-Errors in spatial mapping data fall into a few categories:
-
-- *Holes*: Real-world surfaces are missing from the spatial mapping data.
-- *Hallucinations*: Surfaces exist in the spatial mapping data that do not exist in the real world.
-- *Wormholes*: HoloLens 'loses' part of the spatial map by thinking it is in a different part of the map than it actually is.
-- *Bias*: Surfaces in the spatial mapping data are imperfectly aligned with real-world surfaces, either pushed in or pulled out.
-
-If you see any of these errors please use the [FeedbackHub](hololens-feedback.md) to send feedback.
-
-## Security and storage for spatial data
-
-Windows 10 version 1803 update for Microsoft HoloLens and later stores mapping data in a local (on-device) database.
-
-HoloLens users cannot directly access the map database, even when the device is plugged into a PC or when using the File Explorer app. When BitLocker is enabled on HoloLens, the stored map data is also encrypted along with the entire volume.
-
-### Remove map data and known spaces from HoloLens
-
-There are two options for deleting map data in **Settings > System > Holograms**:
-
-- To delete nearby holograms, select **Remove nearby holograms**. This command clears the map data and anchored holograms for the current space. If you continue to use the device in the same space, it creates and stores a brand new map section to replace the deleted information.
-
- > [!NOTE]
- > "Nearby" holograms are holograms that are anchored within the same map section in the current space.
-
- For example, you can use this option to clear work-related map data without affecting any home-related map data.
-
-- To delete all holograms, select **Remove all holograms**. This command clears all map data that is stored on the device as well as all anchored holograms. You will need to explicitly place any holograms. You will not be able to rediscover the previously-placed holograms.
-
-> [!NOTE]
-> After you remove nearby or all holograms, HoloLens immediately starts scanning and mapping the current space.
-
-### Wi-Fi data in spatial maps
-
-HoloLens stores Wi-Fi characteristics to help correlate hologram locations and map sections that are stored within the HoloLens database of known spaces. Information about Wi-Fi characteristics is not accessible to users, and not sent to Microsoft using the cloud or using telemetry.
-
-As long as Wi-Fi is enabled, HoloLens correlates map data with nearby Wi-Fi access points. There is no difference in behavior whether a network is connected or just detected nearby. If Wi-Fi is disabled, HoloLens still searches the space. However, HoloLens has to search more of the map data within the spaces database, and may need more time to find holograms. Without the Wi-Fi info, the HoloLens has to compare active scans to all hologram anchors and map sections that are stored on the device in order to locate the correct portion of the map.
-
-## Related topics
-
-- [Spatial mapping design](https://docs.microsoft.com/windows/mixed-reality/spatial-mapping-design)
diff --git a/devices/hololens/hololens-status.md b/devices/hololens/hololens-status.md
deleted file mode 100644
index a1209dd3c8..0000000000
--- a/devices/hololens/hololens-status.md
+++ /dev/null
@@ -1,39 +0,0 @@
----
-title: Status of the HoloLens services
-description: Shows the status of HoloLens online services.
-author: Teresa-Motiv
-ms.author: v-tea
-ms.reviewer: luoreill
-manager: jarrettr
-audience: Admin
-ms.custom:
-- CI 111456
-- CSSTroubleshooting
-ms.topic: article
-ms.prod: hololens
-ms.localizationpriority: high
-ms.sitesec: library
----
-
-# Status of the HoloLens services
-
-✔️ **All services are active**
-
-**Key** ✔️ Good, ⓘ Information, ⚠ Warning, ❌ Critical
-
-Area|HoloLens (1st gen)|HoloLens 2
-----|:----:|:----:
-[Azure services](https://status.azure.com/status)|✔️|✔️
-[Store app](https://www.microsoft.com/store/collections/hlgettingstarted/hololens)|✔️|✔️
-[Apps](https://www.microsoft.com/hololens/apps)|✔️|✔️
-[MDM](https://docs.microsoft.com/hololens/hololens-enroll-mdm)|✔️|✔️
-
-## Notes and related topics
-
-[Frequently asked questions about using Skype for HoloLens](https://support.skype.com/faq/FA34641/frequently-asked-questions-about-using-skype-for-hololens)
-
-For more details about the status of the myriad Azure Services that can connect to HoloLens, see [Azure status](https://azure.microsoft.com/status/).
-
-For more details about current known issues, see [HoloLens known issues](hololens-known-issues.md).
-
-Follow HoloLens on [Twitter](https://twitter.com/HoloLens) and subscribe on [Reddit](https://www.reddit.com/r/HoloLens/).
diff --git a/devices/hololens/hololens-troubleshooting.md b/devices/hololens/hololens-troubleshooting.md
deleted file mode 100644
index b4d107902a..0000000000
--- a/devices/hololens/hololens-troubleshooting.md
+++ /dev/null
@@ -1,97 +0,0 @@
----
-title: Troubleshoot HoloLens issues
-description: Solutions for common HoloLens issues.
-author: mattzmsft
-ms.author: mazeller
-ms.date: 12/02/2019
-ms.prod: hololens
-ms.topic: article
-ms.custom: CSSTroubleshooting
-audience: ITPro
-ms.localizationpriority: medium
-keywords: issues, bug, troubleshoot, fix, help, support, HoloLens
-manager: jarrettr
-ms.custom:
-- CI 111456
-- CSSTroubleshooting
-appliesto:
-- HoloLens (1st gen)
-- HoloLens 2
----
-
-# Troubleshoot HoloLens issues
-
-This article describes how to resolve several common HoloLens issues.
-
-## My HoloLens is unresponsive or won't start
-
-If your HoloLens won't start:
-
-- If the LEDs next to the power button don't light up, or only one LED briefly blinks, you may need to charge your HoloLens.
-- If the LEDs light up when you press the power button but you can't see anything on the displays, hold the power button until all five of the LEDs turn off.
-
-If your HoloLens becomes frozen or unresponsive:
-
-- Turn off your HoloLens by pressing the power button until all five of the LEDs turn themselves off, or for 10 seconds if the LEDs are unresponsive. To start your HoloLens, press the power button again.
-
-If these steps don't work, you can try [recovering your device](hololens-recovery.md).
-
-## Holograms don't look good
-
-If your holograms are unstable, jumpy, or don't look right, try:
-
-- Cleaning your device visor and sensor bar on the front of your HoloLens.
-- Increasing the light in your room.
-- Walking around and looking at your surroundings so that HoloLens can scan them more completely.
-- Calibrating your HoloLens for your eyes. Go to **Settings** > **System** > **Utilities**. Under **Calibration**, select **Open Calibration**.
-
-## HoloLens doesn't respond to gestures
-
-To make sure that HoloLens can see your gestures. Keep your hand in the gesture frame - when HoloLens can see your hand, the cursor changes from a dot to a ring.
-
-Learn more about using gestures on [HoloLens (1st gen)](hololens1-basic-usage.md#use-hololens-with-your-hands) or [HoloLens 2](hololens2-basic-usage.md#the-hand-tracking-frame).
-
-If your environment is too dark, HoloLens might not see your hand, so make sure that there's enough light.
-
-If your visor has fingerprints or smudges, use the microfiber cleaning cloth that came with the HoloLens to clean your visor gently.
-
-## HoloLens doesn't respond to my voice commands
-
-If Cortana isn't responding to your voice commands, make sure Cortana is turned on. On the All apps list, select **Cortana** > **Menu** > **Notebook** > **Settings** to make changes. To learn more about what you can say, see [Use your voice with HoloLens](hololens-cortana.md).
-
-## I can't place holograms or see holograms that I previously placed
-
-If HoloLens can't map or load your space, it enters Limited mode and you won't be able to place holograms or see holograms that you've placed. Here are some things to try:
-
-- Make sure that there's enough light in your environment so HoloLens can see and map the space.
-- Make sure that you're connected to a Wi-Fi network. If you're not connected to Wi-Fi, HoloLens can't identify and load a known space.
-- If you need to create a new space, connect to Wi-Fi, then restart your HoloLens.
-- To see if the correct space is active, or to manually load a space, go to **Settings** > **System** > **Spaces**.
-- If the correct space is loaded and you're still having problems, the space may be corrupt. To fix this issue, select the space, then select **Remove**. After you remove the space, HoloLens starts to map your surroundings and create a new space.
-
-## My HoloLens can't tell what space I'm in
-
-If your HoloLens can't identify and load the space you're in automatically, check the following factors:
-
-- Make sure that you're connected to Wi-Fi
-- Make sure that there's plenty of light in the room
-- Make sure that there haven't been any major changes to the surroundings.
-
-You can also load a space manually or manage your spaces by going to **Settings** > **System** > **Spaces**.
-
-## I'm getting a "low disk space" error
-
-You'll need to free up some storage space by doing one or more of the following:
-
-- Delete some unused spaces. Go to **Settings** > **System** > **Spaces**, select a space that you no longer need, and then select **Remove**.
-- Remove some of the holograms that you've placed.
-- Delete some pictures and videos from the Photos app.
-- Uninstall some apps from your HoloLens. In the **All apps** list, tap and hold the app you want to uninstall, and then select **Uninstall**.
-
-## My HoloLens can't create a new space
-
-The most likely problem is that you're running low on storage space. Try one of the [previous tips](#im-getting-a-low-disk-space-error) to free up some disk space.
-
-## The HoloLens emulators isn't working
-
-Information about the HoloLens emulator is located in our developer documentation. Read more about [troubleshooting the HoloLens emulator](https://docs.microsoft.com/windows/mixed-reality/using-the-hololens-emulator#troubleshooting).
diff --git a/devices/hololens/hololens-update-hololens.md b/devices/hololens/hololens-update-hololens.md
deleted file mode 100644
index 14d8993c95..0000000000
--- a/devices/hololens/hololens-update-hololens.md
+++ /dev/null
@@ -1,92 +0,0 @@
----
-title: Update HoloLens
-description: Check your HoloLens' build number, update, and roll back updates.
-keywords: how-to, update, roll back, HoloLens, check build, build number
-ms.prod: hololens
-ms.sitesec: library
-author: scooley
-ms.author: scooley
-ms.topic: article
-ms.localizationpriority: medium
-ms.date: 11/27/2019
-audience: ITPro
-ms.reviewer:
-manager: jarrettr
-appliesto:
-- HoloLens (1st gen)
-- HoloLens 2
----
-
-# Update HoloLens
-
-HoloLens uses Windows Update, just like other Windows 10 devices. Your HoloLens will automatically download and install system updates whenever it is plugged-in to power and connected to the Internet, even when it is in standby.
-
-This article will walk through HoloLens tools for:
-
-- viewing your current operating system version (build number)
-- checking for updates
-- manually updating HoloLens
-- rolling back to an older update
-
-## Check your operating system version (build number)
-
-You can verify the system version number, (build number) by opening the Settings app and selecting **System** > **About**.
-
-## Check for updates and manually update
-
-You can check for updates any time in settings. To see available updates and check for new updates:
-
-1. Open the **Settings** app.
-1. Navigate to **Update & Security** > **Windows Update**.
-1. Select **Check for updates**.
-
-If an update is available, it will start downloading the new version. After the download is complete, select the **Restart Now** button to trigger the installation. If your device is below 40% and not plugged in, restarting will not start installing the update.
-
-While your HoloLens is installing the update, it will display spinning gears and a progress indicator. Do not turn off your HoloLens during this time. It will restart automatically once it has completed the installation.
-
-HoloLens applies one update at a time. If your HoloLens is more than one version behind the latest you may need to run through the update process multiple times to get it fully up to date.
-
-## Go back to a previous version - HoloLens 2
-
-In some cases, you might want to go back to a previous version of the HoloLens software. You can do this by using the Advanced Recovery Companion to reset your HoloLens to the earlier version.
-
-> [!NOTE]
-> Going back to an earlier version deletes your personal files and settings.
-
-To go back to a previous version of HoloLens 2, follow these steps:
-
-1. Make sure that you don't have any phones or Windows devices plugged in to your PC.
-1. On your PC, download the [Advanced Recovery Companion](https://www.microsoft.com/p/advanced-recovery-companion/9p74z35sfrs8?activetab=pivot:overviewtab) from the Microsoft Store.
-1. Download the [most recent HoloLens 2 release](https://aka.ms/hololens2download).
-1. When you have finished these downloads, open **File explorer** > **Downloads**. Right-click the zipped folder that you just downloaded, and select **Extract all** > **Extract** to unzip it.
-1. Connect your HoloLens to your PC using a USB-A to USB-C cable. (Even if you've been using other cables to connect your HoloLens, this one works best.)
-1. The Advanced Recovery Companion automatically detects your HoloLens. Select the **Microsoft HoloLens** tile.
-1. On the next screen, select **Manual package selection** and then select the installation file contained in the folder that you unzipped in step 4. (Look for a file with the .ffu extension.)
-1. Select **Install software**, and follow the instructions.
-
-## Go back to a previous version - HoloLens (1st Gen)
-
-In some cases, you might want to go back to a previous version of the HoloLens software. You can do this by using the Windows Device Recovery Tool to reset your HoloLens to the earlier version.
-
-> [!NOTE]
-> Going back to an earlier version deletes your personal files and settings.
-
-To go back to a previous version of HoloLens 1, follow these steps:
-
-1. Make sure that you don't have any phones or Windows devices plugged in to your PC.
-1. On your PC, download the [Windows Device Recovery Tool (WDRT)](https://support.microsoft.com/help/12379).
-1. Download the [HoloLens Anniversary Update recovery package](https://aka.ms/hololensrecovery).
-1. When the downloads finish, open **File explorer** > **Downloads**. Right-click the zipped folder you just downloaded, and select **Extract all** > **Extract** to unzip it.
-1. Connect your HoloLens to your PC using the micro-USB cable that it came with. (Even if you've been using other cables to connect your HoloLens, this one works best.)
-1. The WDRT will automatically detect your HoloLens. Select the **Microsoft HoloLens** tile.
-1. On the next screen, select **Manual package selection** and choose the installation file contained in the folder you unzipped in step 4. (Look for a file with the .ffu extension.)
-1. Select **Install software**, and follow the instructions.
-
-> [!NOTE]
-> If the WDRT doesn't detect your HoloLens, try restarting your PC. If that doesn't work, select **My device was not detected**, select **Microsoft HoloLens**, and then follow the instructions.
-
-## Windows Insider Program on HoloLens
-
-Want to see the latest features in HoloLens? If so, join the Windows Insider Program; you'll get access to preview builds of HoloLens software updates before they're available to the general public.
-
-[Get Windows Insider preview for Microsoft HoloLens](hololens-insider.md).
diff --git a/devices/hololens/hololens-updates.md b/devices/hololens/hololens-updates.md
deleted file mode 100644
index 2b4e28a971..0000000000
--- a/devices/hololens/hololens-updates.md
+++ /dev/null
@@ -1,216 +0,0 @@
----
-title: Manage HoloLens updates
-description: Administrators can use mobile device management to manage updates to HoloLens devices.
-ms.prod: hololens
-ms.sitesec: library
-author: Teresa-Motiv
-ms.author: v-tea
-audience: ITPro
-ms.topic: article
-ms.localizationpriority: high
-ms.date: 03/24/2020
-ms.reviewer: jarrettr
-manager: jarrettr
-ms.custom:
-- CI 115825
-- CI 111456
-- CSSTroubleshooting
-appliesto:
-- HoloLens (1st gen)
-- HoloLens 2
----
-
-# Manage HoloLens updates
-
-HoloLens uses Windows Update in the same manner as other Windows 10 devices. When an update is available, it is automatically downloaded and installed the next time that your device is plugged in and connected to the internet. This article describes how to manage updates in an enterprise or other managed environment. For information about managing updates to individual HoloLens devices, see [Update HoloLens](hololens-update-hololens.md).
-
-## Manage updates automatically
-
-Windows Holographic for Business can use [Windows Update for Business](https://docs.microsoft.com/windows/deployment/update/waas-manage-updates-wufb) to manage updates. All HoloLens 2 devices can use Windows Holographic for Business. Make sure that they use Windows Holographic for Business build 10.0.18362.1042 or a later build. If you have HoloLens (1st gen) devices, you have to [upgrade them to Windows Holographic for Business](hololens1-upgrade-enterprise.md) to manage their updates.
-
-Windows Update for Business connects HoloLens devices directly to the Windows Update service. By using Windows Update for Business, you can control multiple aspects of the update process—that is, which devices get which updates at what time. For example, you can roll out updates to a subset of devices for testing, then roll out updates to the remaining devices at a later date. Or, you can define different update schedules for different types of updates.
-
-> [!NOTE]
-> For HoloLens devices, you can automatically manage feature updates (released twice a year) and quality updates (released monthly or as required, including critical security updates). For more information about update types, see [Types of updates managed by Windows Update for Business](https://docs.microsoft.com/windows/deployment/update/waas-manage-updates-wufb#types-of-updates-managed-by-windows-update-for-business).
-
-You can configure Windows Update for Business settings for HoloLens by using policies in a Mobile Device Management (MDM) solution such as Microsoft Intune.
-
-For a detailed discussion about how to use Intune to configure Windows Update for Business, see [Manage Windows 10 software updates in Intune](https://docs.microsoft.com/intune/protect/windows-update-for-business-configure).
-
-> [!IMPORTANT]
-> Intune provides two policy types for managing updates: *Windows 10 update ring* and *Windows 10 feature updates*. The Windows 10 feature update policy type is in public preview at this time and is not supported for HoloLens.
->
-> You can use Windows 10 update ring policies to manage HoloLens 2 updates.
-
-### Configure update policies for HoloLens 2 or HoloLens (1st gen)
-
-This section describes the policies that you can use to manage updates for either HoloLens 2 or HoloLens (1st gen). For information about additional functionality that is available for HoloLens 2, see [Plan and configure update rollouts for HoloLens 2](#plan-and-configure-update-rollouts-for-hololens-2).
-
-The [Policy configuration service provider (CSP)](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-update) defines the policies that configure Windows Update for Business.
-
-> [!NOTE]
-> For details about specific policies that are supported by specific editions of HoloLens, see [Policies supported by HoloLens devices](https://docs.microsoft.com/windows/client-management/mdm/policy-configuration-service-provider#policies-supported-by-hololens-devices).
-
-#### Configure automatic checks for updates
-
-You can use the **Update/AllowAutoUpdate** policy to manage automatic update behavior, such as scanning, downloading, and installing updates.
-
-This policy supports the following values:
-
-- **0** - Notify the user when there is an update that is ready to download that applies to the device.
-- **1** - Automatically install the update, and then notify the user to schedule a device restart.
-- **2** - Automatically install the update, and then restart the device. This is the recommended value, and it is the default value for this policy.
-
-- **3** - Automatically install the update, and then restart at a specified time. Specify the installation day and time. If no day and time are specified, the default is daily at 3 A.M.
-
-- **4** - Automatically install the update, and then restart the device. This option also sets the Settings page to read-only.
-
-- **5** - Turn off automatic updates.
-
-For more details about the available settings for this policy, see [Update/AllowAutoUpdate](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-update#update-allowautoupdate).
-
-> [!NOTE]
-> In Microsoft Intune, you can use **Automatic Update Behavior** to change this policy. For more information, see [Manage software updates in Microsoft Intune](https://docs.microsoft.com/intune/windows-update-for-business-configure).
-
-#### Configure an update schedule
-
-To configure how and when updates are applied, use the following policies:
-
-- [Update/ScheduledInstallDay](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-update#update-scheduledinstallday).
- - Values: **0**–**7** (0 = every day, 1 = Sunday, 7 = Saturday)
- - Default value: **0** (every day)
-- [Update/ScheduledInstallTime](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-update#update-scheduledinstalltime).
- - Values: 0–23 (0 = midnight, 23 = 11 P.M.)
- - Default value: 3 P.M.
-
-#### For devices that run Windows 10, version 1607 only
-
-You can use the following update policies to configure devices to get updates from the Windows Server Update Service (WSUS), instead of Windows Update:
-
-- [Update/AllowUpdateService](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-update#update-allowupdateservice)
-- [Update/RequireUpdateApproval](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-update#update-requireupdateapproval)
-- [Update/UpdateServiceUrl](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-update#update-updateserviceurl)
-
-### Plan and configure update rollouts for HoloLens 2
-
-HoloLens 2 supports more update automation features than HoloLens (1st gen). this is especially true if you use Microsoft Intune to manage Windows Update for Business policy. These features make it easier for you to plan and implement update rollouts across your organization.
-
-#### Plan the update strategy
-
-Windows Updates for Business supports deferral policies. After Microsoft releases an update, you can use a deferral policy to define how long to wait before installing that update on devices. By associating subsets of your devices (referred to as *update rings*) with different deferral policies, you can coordinate an update rollout strategy for your organization.
-
-For example, consider an organization that has 1,000 devices and has to update them in five ways. The organization can create five update rings, as shown in the following table.
-
-|Group |Number of devices |Deferral (days) |
-| ---| :---: | :---: |
-|Grp 1 (IT staff) |5 |0 |
-|Grp 2 (early adopters) |50 |60 |
-|Grp 3 (main 1) |250 |120 |
-|Grp 4 (main 2) |300 |150 |
-|Grp 5 (main 3) |395 |180 |
-
-Here's how the rollout progresses over time to the entire organization.
-
-
-
-#### Configure an update deferral policy
-
-A deferral policy specifies the number of days between the date that an update becomes available and the date that the update is offered to a device.
-
-You can configure different deferrals for feature updates and quality updates. The following table lists the specific policies to use for each type, as well as the maximum deferral for each.
-
-|Category |Policy |Maximum deferral |
-| --- | --- | --- |
-|Feature updates |DeferFeatureUpdatesPeriodInDays |365 days |
-|Quality updates |DeferQualityUpdatesPeriodInDays |30 days |
-
-#### Examples: Using Intune to manage updates
-
-**Example 1: Create and assign an update ring**
-
-For a more detailed version of this example, see [Create and assign update rings](https://docs.microsoft.com/mem/intune/protect/windows-update-for-business-configure#create-and-assign-update-rings).
-
-1. Sign in to the [Microsoft Endpoint Manager Admin Center](https://go.microsoft.com/fwlink/?linkid=2109431), and navigate to your Intune profiles.
-1. Select **Software Updates** > **Windows 10 update rings** > **Create**.
-1. Under **Basics**, specify a name and a description (optional), and then select **Next**.
-1. Under **Update ring settings**, for **Servicing channel**, select **Semi-Annual Channel**, and then change **Feature update deferral period** to **120**. Then, select **Next**.
-1. Under **Assignments**, select **+ Select groups to include**, and then assign the update ring to one or more groups. Use **+ Select groups to exclude** to fine-tune the assignments. Then, select **Next**.
-1. Under **Review + create**, review the settings. When you're ready to save the update ring configuration, select **Create**.
-
-The list of update rings now includes the new Windows 10 update ring.
-
-**Example 2: Pause an update ring**
-
-If you encounter a problem when you deploy a feature or quality update, you can pause the update for 35 days (starting from a specified date). This pause prevents other devices from installing the update until you resolve or mitigate the issue. If you pause a feature update, quality updates are still offered to devices to make sure that they stay secure. After the specified time has passed, the pause automatically expires. At that point, the update process resumes.
-
-To pause an update ring in Intune, follow these steps:
-
-1. On the overview page for the update ring, select **Pause**.
-1. Select the type of update (**Feature** or **Quality**) to pause, and then select **OK**.
-
-When an update type is paused, the Overview pane for that ring displays how many days remain before that update type resumes.
-
-While the update ring is paused, you can select either of the following options:
-
-- To extend the pause period for an update type for 35 days, select **Extend**.
-- To restore updates for that ring to active operation, select **Resume**. You can pause the update ring again if it is necessary.
-
-> [!NOTE]
-> The **Uninstall** operation for update rings is not supported for HoloLens 2 devices.
-
-## Manually check for updates
-
-Although HoloLens periodically checks for system updates so that you don't have to, there may be circumstances in which you want to manually check.
-
-To manually check for updates, go to **Settings** > **Update & Security** > **Check for updates**. If the Settings app indicates that your device is up to date, you have all the updates that are currently available.
-
-## Manually revert an update
-
-In some cases, you might want to go back to a previous version of the HoloLens software. The process for doing this depends on whether you are using HoloLens 2 or HoloLens (1st gen).
-
-### Go back to a previous version (HoloLens 2)
-
-You can roll back updates and return to a previous version of HoloLens 2 by using the Advanced Recovery Companion to reset your HoloLens to the earlier version.
-
-> [!NOTE]
-> Reverting to an earlier version deletes your personal files and settings.
-
-To go back to a previous version of HoloLens 2, follow these steps:
-
-1. Make sure that you don't have any phones or Windows devices plugged in to your computer.
-1. On your computer, download the [Advanced Recovery Companion](https://www.microsoft.com/p/advanced-recovery-companion/9p74z35sfrs8?activetab=pivot:overviewtab) from the Microsoft Store.
-1. Download the [most recent HoloLens 2 release](https://aka.ms/hololens2download).
-1. When you have finished these downloads, open **File explorer** > **Downloads**, right-click the compressed (zipped) folder that you just downloaded, and then select **Extract all** > **Extract** to expand the file.
-1. Use a USB-A to USB-C cable to connect your HoloLens device to your computer. Even if you've been using other cables to connect your HoloLens, this kind of cable works best.
-1. The Advanced Recovery Companion automatically detects your HoloLens device. Select the **Microsoft HoloLens** tile.
-1. On the next screen, select **Manual package selection**, and then open the folder that you previously expanded.
-1. Select the installation file (the file that has an .ffu extension).
-1. Select **Install software**, and then follow the instructions.
-
-### Go back to a previous version (HoloLens (1st gen))
-
-You can roll back updates and return to a previous version of HoloLens (1st gen) by using the Windows Device Recovery Tool to reset your HoloLens to the earlier version.
-
-> [!NOTE]
-> Reverting to an earlier version deletes your personal files and settings.
-
-To go back to a previous version of HoloLens (1st gen), follow these steps:
-
-1. Make sure that you don't have any phones or Windows devices plugged in to your computer.
-1. On your computer, download the [Windows Device Recovery Tool (WDRT)](https://support.microsoft.com/help/12379).
-1. Download the [HoloLens Anniversary Update recovery package](https://aka.ms/hololensrecovery).
-1. After the downloads finish, open **File explorer** > **Downloads**, right-click the compressed (zipped) folder that you just downloaded, and then select **Extract all** > **Extract** to expand the file.
-1. Use the micro-USB cable that was provided together with your HoloLens device to connect your HoloLens device to your computer. Even if you've been using other cables to connect your HoloLens device, this one works best.
-1. The WDRT automatically detects your HoloLens device. Select the **Microsoft HoloLens** tile.
-1. On the next screen, select **Manual package selection**, and then open the folder that you previously expanded.
-1. Select the installation file (the file that has an .ffu extension).
-1. Select **Install software**, and then follow the instructions.
-
-> [!NOTE]
-> If the WDRT doesn't detect your HoloLens device, try restarting your computer. If that doesn't work, select **My device was not detected**, select **Microsoft HoloLens**, and then follow the instructions.
-
-## Related articles
-
-- [Deploy updates using Windows Update for Business](https://docs.microsoft.com/windows/deployment/update/waas-manage-updates-wufb)
-- [Assign devices to servicing channels for Windows 10 updates](https://docs.microsoft.com/windows/deployment/update/waas-servicing-channels-windows-10-updates)
-- [Manage Windows 10 software updates in Intune](https://docs.microsoft.com/mem/intune/protect/windows-update-for-business-configure)
diff --git a/devices/hololens/hololens1-basic-usage.md b/devices/hololens/hololens1-basic-usage.md
deleted file mode 100644
index 282eaada0a..0000000000
--- a/devices/hololens/hololens1-basic-usage.md
+++ /dev/null
@@ -1,138 +0,0 @@
----
-title: Getting around HoloLens (1st gen)
-description: A brief tour of the HoloLens (1st gen) interface
-ms.assetid: 064f7eb0-190e-4643-abeb-ed3b09312042
-ms.date: 9/16/2019
-ms.reviewer: jarrettr
-manager: jarrettr
-keywords: hololens
-ms.prod: hololens
-ms.sitesec: library
-author: v-miegge
-ms.author: v-miegge
-ms.topic: article
-ms.localizationpriority: high
-appliesto:
-- HoloLens (1st gen)
----
-
-# Getting around HoloLens (1st gen)
-
-Ready to step into the world of holograms? Here's some information to get started.
-
-This guide provides an intro to mixed reality, gestures for interacting with holograms, and an intro to Windows Holographic.
-
-## Discover mixed reality
-
-On HoloLens, holograms blend with your physical environment to look and sound like they're part of your world. Even when holograms are all around you, you can still see your surroundings, move freely, and interact with other people and objects. We call this experience "mixed reality."
-
-The holographic frame positions your holograms where your eyes are most sensitive to detail, and the see-through lenses leave your peripheral vision unobscured. With spatial sound, you can pinpoint a hologram even if it’s behind you. And because HoloLens learns and understands your environment, you can place holograms on and around real objects—and so can your apps and games. So a character in a game might sit down on your sofa, or [space robots could bust out of your walls](https://www.microsoft.com/store/apps/9nblggh5fv3j).
-
-## Use HoloLens with your hands
-
-Getting around HoloLens is a lot like using your smart phone. You can use your hands to manipulate holographic windows, menus, and buttons. Instead of pointing, clicking, or tapping, you'll use your gaze, your [voice](hololens-cortana.md), and gestures to select apps and holograms and to get around HoloLens.
-
-When you know these basic interactions, getting around on HoloLens will be a snap.
-
-We'll walk you through the basics the first time you use your HoloLens. You'll also find a gesture tutorial on your **Start** menu—look for the Learn Gestures app.
-
-### The hand-tracking frame
-
-HoloLens has sensors that can see a few feet to either side of you. When you use your hands, you'll need to keep them inside that frame, or HoloLens won't see them. As you move around, the frame moves with you.
-
-
-
-### Open the Start menu with bloom
-
-To open the **Start** menu:
-
-1. Hold your hand in front of you so it's in the gesture frame.
-1. Bloom: bring all of your fingers together then open your hand.
- 
-
-### Select holograms with gaze and air tap
-
-To select an app or other hologram, air tap it while looking directly at the hologram you're selecting. To do this, follow these steps:
-
-1. Gaze at the hologram you want to select.
-1. Point your index finger straight up toward the ceiling.
-1. Air tap: lower your finger, then quickly raise it.
- 
-
-### Select a hologram by using your voice
-
-1. The gaze cursor is a dot that you move around by moving your head. You can use it to target voice commands with precision.
-1. Gaze at the hologram that you want to select.
-1. To select the hologram, say "Select."
-
-## Holograms and apps
-
-Now it's time to put gestures to the test!
-
-You'll find your installed apps in the [Start menu](holographic-home.md) and there are more apps for HoloLens (1st gen) in the Microsoft Store.
-
-Open the **Start** menu and select an app!
-
-Using apps on HoloLens is a little different from on a PC: Some apps use a 2D view and look like other Windows applications. Other apps (immersive apps) use a 3D view and when you launch them, they become the only app you see.
-
-When you place an app window or app launcher, it will stay put until you remove it. You can move or resize these holograms in your mixed reality home at any time.
-
-## Move, resize, and rotate apps
-
-Moving and resizing apps on HoloLens works a bit differently than it does on a PC. Instead of dragging the app, you'll use your gaze, along with a [gesture](https://support.microsoft.com/help/12644/hololens-use-gestures) or the [clicker](hololens1-clicker.md). You can also rotate an app window in 3D space.
-
-> [!TIP]
-> Rearrange apps using your voice - gaze at an app and say "Face me," "Bigger," or "Smaller." Or have Cortana move an app for you: say "Hey Cortana, move \**app name\** here."
-
-### Move an app
-
-Gaze at the app (at the title bar of an app window), and then do one of the following.
-
-- Tap and hold to select the app. Move your hand to position the app, and raise your finger to place it.
-- Select **Adjust**, tap and hold, and move your hand to position the app. Raise your finger to place it, then select **Done**.
-- Select **Adjust**, click and hold the clicker, and move your hand to position the app. Release the clicker, then select **Done**.
-
-> [!TIP]
-> If you drop apps when you move them, make sure to keep your hand in the gesture frame by following it with your gaze.
-
-### Resize an app
-
-Gaze at the app, and then do one of the following.
-
-- Gaze at a corner or edge of an app window, and tap and hold. Move your hand to change the app's size, and raise your finger when you're done.
-- Select **Adjust**. Gaze at one of the blue squares at the corners of the app, tap and hold, then move your hand to resize the app. Raise your finger to release it, then select **Done**.
-- Select **Adjust**. Gaze at one of the blue squares at the corners of the app, click and hold the clicker, then move your hand to resize the app. Release the clicker, then select **Done**.
-
-> [!TIP]
-> In Adjust mode, you can move or resize any hologram.
-
-### Rotate an app
-
-Gaze at the app, and tap and hold with both hands to select it. Rotate the app by keeping one hand steady and moving your other hand around it. When you're done, raise both index fingers.
-
-### Scroll content in an app window
-
-Gaze at the content of the app window. Tap and hold and then move your hand slightly upwards or downwards to scroll the content.
-
-## Meet the HoloLens (1st gen) Clicker
-
-The [HoloLens (1st Gen) clicker](hololens1-clicker.md) gives you another way to interact with holograms. [Pair it](hololens-connect-devices.md) with your HoloLens and then use it along with your gaze to select, scroll, and more.
-
-## Next steps
-
-Congratulations! you're ready to use HoloLens (1st gen).
-
-Now you can configure your HoloLens (1st gen) to meet your specific needs.
-
-[Connect bluetooth devices like mouse and keyboard](hololens-connect-devices.md)
-
-[Learn more about Voice and Cortana](hololens-cortana.md)
-
-### Help! I don't see my holograms
-
-If you don’t see holograms that you’ve placed while using HoloLens, here are some things to try:
-
-- Make sure that you’re looking in the right area—remember, holograms stay where you left them!
-- Make sure that you're in a well-lit room without a lot of direct sunlight.
-- Wait. When HoloLens has trouble recognizing your space, previously placed holograms can take up to a minute to reappear.
-- If issue persists, you may want to clear out your Holograms storage data in **Settings** > **System** > **Holograms**, then place holograms in mixed reality home again.
diff --git a/devices/hololens/hololens1-clicker.md b/devices/hololens/hololens1-clicker.md
deleted file mode 100644
index 9da6a40ba5..0000000000
--- a/devices/hololens/hololens1-clicker.md
+++ /dev/null
@@ -1,97 +0,0 @@
----
-title: Use the HoloLens clicker
-description: This article outlines how to use the HoloLens clicker, including clicker pairing, charging, and recovery.
-ms.assetid: 7d4a30fd-cf1d-4c9a-8eb1-1968ccecbe59
-ms.date: 09/16/2019
-manager: jarrettr
-keywords: hololens
-ms.prod: hololens
-ms.sitesec: library
-author: v-miegge
-ms.author: v-miegge
-ms.topic: article
-ms.localizationpriority: high
-appliesto:
-- HoloLens (1st gen)
----
-
-# Use the HoloLens (1st gen) clicker
-
-The clicker was designed specifically for HoloLens (1st gen) and gives you another way to interact with holograms. It comes with HoloLens (1st gen), in a separate box.
-
-Use it in place of hand gestures to select, scroll, move, and resize apps.
-
-## Clicker hardware and pairing
-
-The HoloLens (1st gen) clicker has a finger loop to make it easier to hold, and an indicator light.
-
-
-
-### Clicker indicator lights
-
-Here's what the lights on the clicker mean.
-
-- **Blinking white**. The clicker is in pairing mode.
-- **Fast-blinking white**. Pairing was successful.
-- **Solid white**. The clicker is charging.
-- **Blinking amber**. The battery is low.
-- **Solid amber**. The clicker ran into an error and you'll need to restart it. While pressing the pairing button, click and hold for 15 seconds.
-
-### Pair the clicker with your HoloLens (1st gen)
-
-1. Use the bloom gesture to go to **Start**, then select **Settings** > **Devices** and verify that Bluetooth is on.
-1. On the clicker, press and hold the pairing button until the status light blinks white.
-1. On the pairing screen, select **Clicker** > **Pair**.
-
-### Charge the clicker
-
-When the clicker battery is low, the battery indicator will blink amber. Plug the Micro USB cable into a USB power supply to charge the device.
-
-## Use the clicker with HoloLens (1st gen)
-
-### Hold the clicker
-
-To put on the clicker, slide the loop over your ring or middle finger so that the Micro USB port faces toward your wrist. Rest your thumb in the indentation.
-
-
-
-### Clicker gestures
-
-Clicker gestures are small wrist rotations, not the larger movements used for HoloLens hand gestures. And HoloLens recognizes your gestures and clicks even if the clicker is outside the [gesture frame](hololens1-basic-usage.md), so you can hold the clicker in the position that's most comfortable for you.
-
-- **Select**. To select a hologram, button, or other element, gaze at it, then click.
-
-- **Click and hold**. Click and hold your thumb down on the button to do some of the same things you would with tap and hold, such as move or resize a hologram.
-
-- **Scroll**. On the app bar, select **Scroll Tool**. Click and hold, then rotate the clicker up, down, left, or right. To scroll faster, move your hand farther from the center of the scroll tool.
-
-- **Zoom**. On the app bar, select **Zoom Tool**. Click and hold, then rotate the clicker up to zoom in, or down to zoom out.
-
-> [!TIP]
-> To zoom in or out when using Microsoft Edge, gaze at a page and double-click.
-
-## Restart or recover the clicker
-
-Here are some things to try if the HoloLens clicker is unresponsive or isn’t working well.
-
-### Restart the clicker
-
-Use the tip of a pen to press and hold the pairing button. At the same time, click and hold the clicker for 15 seconds. If the clicker was already paired with your HoloLens, it will stay paired after it restarts.
-
-If the clicker won't turn on or restart, try charging it by using the HoloLens charger. If the battery is very low, it might take a few minutes for the white indicator light to turn on.
-
-### Re-pair the clicker
-
-Select **Settings** > **Devices** and select the clicker. Select **Remove**, wait a few seconds, then pair the clicker again.
-
-### Recover the clicker
-
-If restarting and re-pairing the clicker don’t fix the problem, the Windows Device Recovery Tool can help you recover it. The recovery process may take some time, and it will install the latest version of the clicker software. To use the tool, you’ll need a computer running Windows 10 or later that has at least 4 GB of free storage space.
-
-To recover the clicker:
-
-1. Download and install the [Windows Device Recovery Tool](https://dev.azure.com/ContentIdea/ContentIdea/_queries/query/8a004dbe-73f8-4a32-94bc-368fc2f2a895/) on your computer.
-1. Connect the clicker to your computer by using the Micro USB cable that came with your HoloLens.
-1. Run the Windows Device Recovery Tool and follow the instructions.
-
-If the clicker isn’t automatically detected, select **My device was not detected** and follow the instructions to put your device into recovery mode.
diff --git a/devices/hololens/hololens1-fit-comfort-faq.md b/devices/hololens/hololens1-fit-comfort-faq.md
deleted file mode 100644
index d76375918c..0000000000
--- a/devices/hololens/hololens1-fit-comfort-faq.md
+++ /dev/null
@@ -1,64 +0,0 @@
----
-title: HoloLens (1st gen) fit and comfort frequently asked questions
-description: Answers to frequently asked questions about how to fit your HoloLens (1st gen).
-ms.prod: hololens
-ms.sitesec: library
-author: Teresa-Motiv
-ms.author: v-tea
-ms.topic: article
-ms.localizationpriority: high
-ms.date: 10/09/2019
-ms.reviewer: jarrettr
-audience: ITPro
-manager: jarrettr
-appliesto:
-- HoloLens (1st gen)
----
-
-# HoloLens (1st gen) fit and comfort frequently asked questions
-
-Here are some tips on how to stay comfortable and have the best experience using your HoloLens.
-
-For step-by-step instructions and a video about putting on and adjusting your device, see [Get your HoloLens (1st gen) ready to use](hololens1-setup.md).
-
-> [!NOTE]
-> The fit and comfort tips in this topic are meant only as general guidance—they don't replace any laws or regulations, or your good judgment when using HoloLens. Stay safe, and have fun!
-
-Here are some tips on how to stay comfortable and have the best experience using your HoloLens.
-
-## I'm experiencing discomfort when I use my device. What should I do?
-
-If you experience discomfort, take a break until you feel better. Try sitting in a well-lit room and relaxing for a bit. The next time your use your HoloLens, try using it for a shorter period of time at first.
-
-For more information, see [Health and safety on HoloLens](https://go.microsoft.com/fwlink/p/?LinkId=746661).
-
-## I can't see the whole holographic frame, or my holograms are cut off
-
-To see the top edge of the holographic frame, move the device so it sits higher on your head, or angle the headband up slightly in front. To see the bottom edge, move the device to sit lower on your head, or angle the headband down slightly in front. If the left or right edge of the view frame isn't visible, make sure the HoloLens visor is centered on your forehead.
-
-## I need to look up or down to see holograms
-
-Try adjusting the position of your device visor so the holographic frame matches your natural gaze. Here's how:
-
-- **If you need to look up to see holograms**. First, shift the back of the headband a bit higher on your head. Then use one hand to hold the headband in place and the other to gently rotate the visor so you have a good view of the holographic frame.
-- **If you need to look down to see holograms**. First, shift the back of the headband a bit lower on your head. Then place your thumbs under the device arms and your index fingers on top of the headband, and gently squeeze with your thumbs to rotate the visor so you have a good view of the holographic frame.
-
-## The device slides down when I'm using it, or I need to make the headband too tight to keep it secure
-
-The overhead strap can help keep your HoloLens secure on your head, particularly if you're moving around a lot. The strap may also let you loosen the headband a bit. [Learn how to use it](hololens1-setup.md#adjust-fit).
-
-You can also experiment with the positioning of the headband—depending on your head size and shape, you may need to slide it up or down to reposition it on your forehead.
-
-## My HoloLens feels heavy on my nose
-
-If your HoloLens is adjusted correctly, the nose pad should rest lightly on your nose. If it feels heavy on your nose, try rotating the visor up or adjusting the angle of the headband. You can also slide the device visor out—grasp the device arms just behind the visor and pull forward gently.
-
-## How can I adjust HoloLens to fit with my glasses?
-
-The device visor can slide in and out to accommodate eyewear. Grasp the device arms just behind the visor and pull forward gently to adjust it.
-
-## My arm gets tired when I use gestures. What can I do?
-
-When using gestures, there's no need to extend your arm out far from your body. Keep it closer to your side, where it's more comfortable and will get less tired. [Learn more about gestures](hololens1-basic-usage.md#use-hololens-with-your-hands).
-
-And be sure to try out [voice commands](hololens-cortana.md) and the [HoloLens clicker](hololens1-clicker.md).
diff --git a/devices/hololens/hololens1-hardware.md b/devices/hololens/hololens1-hardware.md
deleted file mode 100644
index 285f44dd6a..0000000000
--- a/devices/hololens/hololens1-hardware.md
+++ /dev/null
@@ -1,166 +0,0 @@
----
-title: HoloLens (1st gen) hardware
-description: An outline of the components that make up Microsoft HoloLens (1st gen), the world's first fully untethered holographic computer running Windows.
-ms.assetid: 527d494e-2ab6-46ca-bd5a-bfc6b43cc833
-ms.date: 09/16/2019
-keywords: hololens
-ms.prod: hololens
-ms.sitesec: library
-author: mattzmsft
-ms.author: mazeller
-ms.topic: article
-manager: jarrettr
-ms.localizationpriority: medium
-appliesto:
-- HoloLens (1st gen)
----
-
-# HoloLens (1st gen) hardware
-
-
-
-Microsoft HoloLens (1st gen) is the world's first fully untethered holographic computer. HoloLens redefines personal computing through holographic experiences to empower you in new ways. HoloLens blends cutting-edge optics and sensors to deliver 3D holograms pinned to the real world around you.
-
-## HoloLens components
-
-
-
-Your HoloLens includes the following features:
-
-- **Visor**. Contains the HoloLens sensors and displays. You can rotate the visor up while you are wearing the HoloLens.
-- **Headband**. To put the HoloLens on, use the adjustment wheel to expand the headband. With the HoloLens in place, tighten the adjustment wheel until the headband is comfortable.
-- **Brightness buttons**. When you're wearing the HoloLens, the brightness buttons are on the left side of the device.
-- **Volume buttons**. When you're wearing the HoloLens, the volume buttons are on the right side of the device.
-- **Device arms**. When you pick up, put on, or take off your HoloLens, always grasp or hold it by the device arms.
-
-## In the box
-
-> [!VIDEO https://www.microsoft.com/videoplayer/embed/c7ceb904-9d5f-4194-9e10-e8a949dbad7d]
-
-The HoloLens box contains the following items:
-
-- **Nose pads**. Select a nose pad that fits the shape of your nose and accommodates your eyewear.
-- **Overhead strap**. When you're wearing the HoloLens while you move around, use the overhead strap to help keep the device in place. Additionally, if you're wearing the HoloLens for extended periods, using the overhead strap may make the device more comfortable to wear.
-- **Micro USB cable**. Use the micro-USB cable to connect your HoloLens to the power supply for charging, or use it to connect your HoloLens to your computer.
-- **Power supply**. Plugs into a power outlet.
-- **Microfiber cloth**. Use the cloth to clean your HoloLens visor.
-
->[!TIP]
->The [clicker](hololens1-clicker.md) ships with HoloLens (1st Gen), in a separate box.
-
-### Power Supply details
-
-The power supply and the USB cable that come with the device are the best supported mechanism for charging. The power supply is an 18W charger. It supplies 9V at 2A.
-
-Charging rate and speed may vary depending on the environment in which the device is running.
-
-In order to maintain/advance Internal Battery Charge Percentage while the device is on, it must be connected minimum to a 15W charger.
-
-## Device specifications
-
-### Display
-
-
-
-| | |
-| - | - |
-| Optics | See-through holographic lenses (waveguides) |
-| Holographic resolution | 2 HD 16:9 light engines producing 2.3M total light points |
-| Holographic density | \>2.5k radiants (light points per radian) |
-| Eye-based rendering | Automatic pupillary distance calibration |
-
-### Sensors
-
-
-
-- 1 inertial measurement unit (IMU)
-- 4 environment understanding cameras
-- 1 depth camera
-- 1 2MP photo / HD video camera
-- Mixed reality capture
-- 4 microphones
-- 1 ambient light sensor
-
-### Input, output, and connectivity
-
-- Built-in speakers
-- Audio 3.5mm jack
-- Volume up/down
-- Brightness up/down
-- Power button
-- Battery status LEDs
-- Wi-Fi 802.11ac
-- Micro USB 2.0
-- Bluetooth 4.1 LE
-
-### Power
-
-- Battery Life
-- 2-3 hours of active use
-- Up to 2 weeks of standby time
-- Fully functional when charging
-- Passively cooled (no fans)
-
-### Processors
-
-
-
-- Intel 32-bit architecture with TPM 2.0 support
-- Custom-built Microsoft Holographic Processing Unit (HPU 1.0)
-
-### Memory
-
-- 64 GB Flash
-- 2 GB RAM
-
-### Fit
-
-| | |
-| - | - |
-| Sizing | Single size with adjustable band. Fits over glasses |
-| Weight | 579 grams |
-
-## Device capabilities
-
-Using the following to understand user actions:
-
-- Gaze tracking
-- Gesture input
-- Voice support
-
-Using the following to understand the environment:
-
-- Spatial sound
-
-## Pre-installed software
-
-- Windows 10
-- Windows Store
-- Holograms
-- Microsoft Edge
-- Photos
-- Settings
-- Windows Feedback
-- Calibration
-- Learn Gestures
-
-## Device certifications
-
-### Safety
-
-HoloLens has been tested and found to conform to the basic impact protection requirements of ANSI Z87.1, CSA Z94.3 and EN 166.
-
-## Care and cleaning
-
-Handle your HoloLens carefully. To lift, carry, and adjust your HoloLens, use the device arms—not the overhead strap. To keep the visor free of dust and fingerprints and avoid touching it. Repeated cleaning could damage the visor, so try to keep your device clean.
-
-Don't use any cleaners or solvents on your HoloLens, and don't submerge it in water or apply water directly to it.
-
-To clean the visor, remove any dust using a camel or goat hair lens brush or a bulb-style lens blower. Lightly moisten the microfiber cloth with a small amount of distilled water, then use it to wipe the visor gently in a circular motion.
-
-To clean the rest of the device, including the headband and device arms, use a lint-free cloth moistened with mild soap and water. Let your HoloLens dry completely before using it again.
-
-
-
-> [!div class="nextstepaction"]
-> [Set up and start your HoloLens (1st gen)](hololens1-setup.md)
diff --git a/devices/hololens/hololens1-install-localized.md b/devices/hololens/hololens1-install-localized.md
deleted file mode 100644
index 52e4862bbe..0000000000
--- a/devices/hololens/hololens1-install-localized.md
+++ /dev/null
@@ -1,39 +0,0 @@
----
-title: Install localized versions of HoloLens
-description: Learn how to install the Chinese or Japanese versions of HoloLens
-ms.prod: hololens
-ms.mktglfcycl: manage
-ms.sitesec: library
-author: dansimp
-ms.author: dansimp
-ms.topic: article
-ms.localizationpriority: high
-ms.date: 9/16/2019
-ms.reviewer:
-manager: jarrettr
-appliesto:
-- HoloLens (1st gen)
----
-
-# Install localized versions of HoloLens (1st gen)
-
-In order to switch to the Chinese or Japanese version of HoloLens, you’ll need to use the Windows Device Recovery Tool (WDRT) to download the build for the language on a PC and then install it on your HoloLens.
-
-> [!IMPORTANT]
-> Using WDRT to install the Chinese or Japanese builds of HoloLens deletes existing data, such as personal files and settings, from your HoloLens.
-
-1. On your PC, download and install [the Windows Device Recovery Tool (WDRT)](https://support.microsoft.com/help/12379).
-1. Download the package for the language you want to your PC: [Simplified Chinese](https://aka.ms/hololensdownload-ch) or [Japanese](https://aka.ms/hololensdownload-jp).
-1. When the download finishes, select **File Explorer** > **Downloads**. Right-click the zipped folder that you just downloaded, and select **Extract all** > **Extract** to unzip it.
-1. Connect your HoloLens to your PC using the micro-USB cable that it shipped with. (Even if you've been using other cables to connect your HoloLens, this one works best.)
-1. After the tool automatically detects your HoloLens, select the Microsoft HoloLens tile.
-1. On the next screen, select **Manual package selection** and select the installation file that resides in the folder that you unzipped in step 4. (Look for a file that has the extension “.ffu”.)
-1. Select **Install software** and follow the instructions.
-1. After the build installs, HoloLens setup automatically starts. Put on the device and follow the setup directions.
-
-When you’re done with setup, go to **Settings** > **Update & Security** > **Windows Insider Program**, and check that you’re configured to receive the latest preview builds. Like the English preview builds, the Windows Insider Program keeps the Chinese and Japanese versions of HoloLens up-to-date with the latest preview builds.
-
-> [!NOTE]
->
-> - You can’t use the Settings app to change the system language between English, Japanese, and Chinese. Flashing a new build is the only supported way to change the device system language.
-> - While you can use the on-screen Pinyin keyboard to enter Simplified Chinese or Japanese text, using a Bluetooth hardware keyboard to type Simplified Chinese or Japanese text is not supported at this time. However, on Chinese or Japanese HoloLens, you can continue to use a Bluetooth keyboard to type in English (to toggle a hardware keyboard to type in English, press the ~ key).
diff --git a/devices/hololens/hololens1-setup.md b/devices/hololens/hololens1-setup.md
deleted file mode 100644
index cbbc2315b7..0000000000
--- a/devices/hololens/hololens1-setup.md
+++ /dev/null
@@ -1,106 +0,0 @@
----
-title: Prepare a new HoloLens
-description: This guide walks through first time set up.
-ms.prod: hololens
-ms.sitesec: library
-author: JesseMcCulloch
-ms.author: jemccull
-ms.topic: article
-ms.localizationpriority: high
-ms.date: 8/12/2019
-ms.reviewer:
-manager: jarrettr
-appliesto:
-- Hololens (1st gen)
----
-
-# Get your HoloLens (1st gen) ready to use
-
-Follow along to set up a HoloLens (1st gen) for the first time.
-
-## Charge your HoloLens (1st gen)
-
-To charge your HoloLens, connect the power supply to the charging port by using the included Micro USB cable. Then plug the power supply into a power outlet. When the device is charging, the battery indicator will light up in a wave pattern.
-
-
-
-When your HoloLens is on, the battery indicator shows the battery level in increments. When only one of the five lights is on, the battery level is below 20 percent. If the battery level is critically low and you try to turn on the device, one light will blink briefly, then go out.
-
-> [!TIP]
-> To get an estimate of your current battery level, say "Hey Cortana, how much battery do I have left?"
-
-The power supply and USB cable that come with the device are the best way to charge your HoloLens (1st gen). The power supply provides 18W of power (9V 2A).
-
-Charging rate and speed may vary depending on the environment in which the device is running.
-
-## Adjust fit
-
-> [!VIDEO https://www.microsoft.com/videoplayer/embed/be3cb527-f2f1-4f85-b4f7-a34fbaba980d]
-
-| | |
-|:--- |:--- |
-|1. Rotate the headband up to about 20-30 degrees.||
-|2. Push the headband back. Do not pull it back, or manipulate the band behind the hinge, because over time this can break the band.||
-|3. Turn the adjustment wheel to extend the headband all the way out. ||
-|4. Hold the device by the device arms, and place it on your head. Make sure that the headband sits at the top of your forehead, and then tighten the adjustment wheel.||
-|5. Slide the visor back, and then check the fit of the device. The headband should sit at the top of the forehead, just below your hairline, with the speakers above your ears. The lenses should be centered over your eyes.||
-
-## Turn on your HoloLens
-
-Use the power button to turn HoloLens on and off or to put it in standby mode.
-
-
-
-If your device doesn't respond or won't start, see [Restart, reset, or recover HoloLens](hololens-restart-recover.md).
-
-When your HoloLens is off or in standby, turn it on by pressing the power button for one second. If it doesn't turn on, plug it in and charge it for at least 30 minutes.
-
-> [!TIP]
-> To restart HoloLens, say "Hey Cortana, reboot the device."
-
-### Put HoloLens in standby
-
-To put your HoloLens in standby while it's turned on, press the power button once. The battery indicators blink off. To wake it from standby, press the power button again.
-
-HoloLens automatically goes into standby after 3 minutes of inactivity. When it's in standby, it automatically shuts down after 4 hours, or after the battery level drops by 10 percent.
-
-### Shut down HoloLens
-
-To shut down (turn off) HoloLens, hold the power button down for four seconds. The battery indicators turn off one by one and the device shuts down.
-
-HoloLens automatically shuts down when the battery level drops to one percent, even if it's plugged in. After you've recharged the battery to three percent, you'll be able to turn HoloLens on again.
-
-## Adjust volume and brightness
-
-The brightness and volume buttons are on top of the device arms—volume to your right and brightness to your left.
-
-
-
-## HoloLens indicator lights
-
-
-
-Not sure what the indicator lights on your HoloLens mean? Here's some help.
-
-|When the lights do this |It means |
-| - | - |
-|Scroll from the center outward. |HoloLens is starting up. |
-|Stay lit (all or some). |HoloLens is on and ready to use. Battery life is shown in 20 percent increments. |
-|Scroll, then light up, then scroll. |HoloLens is on and charging. Battery life is shown in 20 percent increments. |
-|Turn off one by one. |HoloLens is shutting down. |
-|Turn off all at once. |HoloLens is going into standby. |
-|All light up, then one blinks briefly, then all turn off. |Battery is critically low. HoloLens needs to charge. |
-|All scroll, then one blinks, then all scroll. |Battery is critically low. HoloLens is charging. |
-
-## Safety and comfort
-
-### Use in safe surroundings
-
-Use your HoloLens in a safe space that’s free of obstructions and tripping hazards. Don’t use it when you need a clear field of view and your full attention, such as while you’re operating a vehicle or doing other potentially hazardous activities.
-
-### Stay comfortable
-
-Keep your first few sessions with HoloLens brief and be sure to take breaks. If you experience discomfort, stop and rest until you feel better. This might include temporary feelings of nausea, motion sickness, dizziness, disorientation, headache, fatigue, eye strain, or dry eyes.
-
-> [!div class="nextstepaction"]
-> [Start and configure your HoloLens (1st gen)](hololens1-start.md)
diff --git a/devices/hololens/hololens1-start.md b/devices/hololens/hololens1-start.md
deleted file mode 100644
index 8cb970020a..0000000000
--- a/devices/hololens/hololens1-start.md
+++ /dev/null
@@ -1,75 +0,0 @@
----
-title: Set up HoloLens (1st gen)
-description: This guide walks through first time set up. You'll need a Wi-Fi network and either a Microsoft (MSA) or Azure Active Directory (Azure AD) account.
-ms.assetid: 0136188e-1305-43be-906e-151d70292e87
-ms.prod: hololens
-author: Teresa-Motiv
-ms.author: v-tea
-ms.topic: article
-ms.date: 8/12/2019
-manager: jarrettr
-ms.topic: article
-ms.localizationpriority: high
-appliesto:
-- HoloLens (1st gen)
----
-
-# Set up your HoloLens (1st gen)
-
-The first time you turn on your HoloLens, you'll be guided through calibrating your device, setting up your device, and signing in. This article walks through the HoloLens (1st gen) first start and setup experience.
-
-In the next section, you'll learn how to work with HoloLens and interact with holograms. To skip ahead to that article, see [Get started with HoloLens (1st gen)](hololens1-basic-usage.md).
-
-## Before you start
-
-Before you get started, make sure you have the following available:
-
-**A Wi-Fi connection**. You'll need to connect your HoloLens to a Wi-Fi network to set it up. The first time you connect, you'll need an open or password-protected network that doesn't require navigating to a website or using certificates to connect. [Learn more about the websites that HoloLens uses](hololens-offline.md).
-
-**A Microsoft account or a work account**. You'll also need to use a Microsoft account (or a work account, if your organization owns the device) to sign in to HoloLens. If you don't have a Microsoft account, go to [account.microsoft.com](https://account.microsoft.com) and set one up for free.
-
-**A safe, well-lit space with no tripping hazards**. [Health and safety info](https://go.microsoft.com/fwlink/p/?LinkId=746661).
-
-**The optional comfort accessories** that came with your HoloLens, to help you get the most comfortable fit. [More on fit and comfort](https://support.microsoft.com/help/12632/hololens-fit-your-hololens).
-
-> [!NOTE]
->
-> - The first time that you use your HoloLens, [Cortana](hololens-cortana.md) is already on and ready to guide you (though she won't be able to respond to your questions until after you set up your device). You can turn Cortana off at any time in Cortana's settings.
-> - In order to switch to the Chinese or Japanese version of HoloLens, you’ll need to download the build for the language on a PC and then install it on your HoloLens. For more information, see [Install localized versions of HoloLens (1st gen)](hololens1-install-localized.md).
-
-## Start your Hololens and set up Windows
-
-The first time you start your HoloLens, your first task is to set up Windows Holographic on your device.
-
-1. Connect to the internet (HoloLens guides you to select Wi-Fi network).
-
-1. Sign in to your user account. Choose between **My work or school owns it** and **I own it**.
- - When you choose **My work or school owns it**, you sign in by using an Azure AD account. If your organization uses Azure AD Premium and has configured automatic MDM enrollment, HoloLens automatically enrolls in MDM. If your organization does not use Azure AD Premium, automatic MDM enrollment isn't available, so you will need to [manually enroll HoloLens in device management](hololens-enroll-mdm.md#enroll-through-settings-app). To sign in to your device the first time by using a work or school account, follow these steps:
- 1. Enter your organizational account information.
- 1. Accept the privacy statement.
- 1. Sign in by using your Azure AD credentials. This may redirect to your organization's sign-in page.
- 1. Continue setting up the device.
- - When you choose **I own it**, you sign in by using a Microsoft account. After setup is complete, you can [manually enroll HoloLens in device management](hololens-enroll-mdm.md#enroll-through-settings-app).
- 1. Enter your Microsoft account information.
- 1. Enter your password. If your Microsoft account requires [two-step verification (2FA)](https://blogs.technet.microsoft.com/microsoft_blog/2013/04/17/microsoft-account-gets-more-secure/), complete the verification process.
-
-1. The device sets your time zone based on information that it obtains from the Wi-Fi network.
-
-## Calibration
-
-After Cortana introduces herself, the next setup step is calibration. For the best HoloLens experience, you should complete the calibration process during setup.
-
-HoloLens (1st gen) uses the distance between your pupils (IPD or [interpupillary distance](https://en.wikipedia.org/wiki/Interpupillary_distance)) to make holograms clear and easy to interact with. If the IPD is not correct, holograms may appear to be unstable or at an incorrect distance.
-
-During calibration, HoloLens asks you to align your finger with a series of six targets per eye. HoloLens uses this process to set the correct IPD for your eyes. If the calibration needs to be updated or adjusted for a new user, the new user can run the Calibration app outside of setup.
-
-
-
-*IPD finger-alignment screen at second step*
-
-Congratulations! Setup is complete and you can begin using HoloLens.
-
-## Next steps
-
-> [!div class="nextstepaction"]
-> [Get started with HoloLens (1st gen)](hololens1-basic-usage.md)
diff --git a/devices/hololens/hololens1-upgrade-enterprise.md b/devices/hololens/hololens1-upgrade-enterprise.md
deleted file mode 100644
index 5e535af10d..0000000000
--- a/devices/hololens/hololens1-upgrade-enterprise.md
+++ /dev/null
@@ -1,91 +0,0 @@
----
-title: Unlock Windows Holographic for Business features
-description: When you upgrade to Windows Holographic for Business, HoloLens provides extra features that are designed for business.
-ms.prod: hololens
-ms.sitesec: library
-author: dansimp
-ms.author: dansimp
-ms.topic: article
-ms.localizationpriority: medium
-ms.date: 9/16/2019
-ms.reviewer:
-manager: jarrettr
-appliesto:
-- HoloLens (1st gen)
----
-
-# Unlock Windows Holographic for Business features
-
-Microsoft HoloLens is available in the *Development Edition*, which runs Windows Holographic (an edition of Windows 10 that is designed for HoloLens), and in the [Commercial Suite](hololens-commercial-features.md), which provides extra features designed for business.
-
-When you purchase the Commercial Suite, you receive a license that upgrades Windows Holographic to Windows Holographic for Business. You can apply this license to the device either by using the organization's [mobile device management (MDM) provider](#edition-upgrade-by-using-mdm) or a [provisioning package](#edition-upgrade-by-using-a-provisioning-package).
-
-> [!TIP]
-> In Windows 10, version 1803, you can check that the HoloLens has been upgraded to the business edition by selecting **Settings** > **System**.
-
-## Edition upgrade by using MDM
-
-The enterprise license can be applied by any MDM provider that supports the [WindowsLicensing configuration service provider (CSP)](https://msdn.microsoft.com/library/windows/hardware/dn904983.aspx). The latest version of the Microsoft MDM API will support WindowsLicensing CSP.
-
-For step-by-step instructions for upgrading HoloLens by using Microsoft Intune, see [Upgrade devices running Windows Holographic to Windows Holographic for Business](https://docs.microsoft.com/intune/holographic-upgrade).
-
- On other MDM providers, the specific steps for setting up and deploying the policy might vary.
-
-## Edition upgrade by using a provisioning package
-
-Provisioning packages are files created by the Windows Configuration Designer tool that apply a specified configuration to a device.
-
-### Create a provisioning package that upgrades the Windows Holographic edition
-
-1. [Create a provisioning package for HoloLens.](hololens-provisioning.md)
-1. Go to **Runtime settings** > **EditionUpgrade**, and select **EditionUpgradeWithLicense**.
-
- 
-
-1. Find the XML license file that was provided when you purchased the Commercial Suite.
-
- > [!NOTE]
- > You can configure [additional settings in the provisioning package](hololens-provisioning.md).
-
-1. On the **File** menu, select **Save**.
-
-1. Read the warning that project files may contain sensitive information and click **OK**.
-
- > [!IMPORTANT]
- > When you build a provisioning package, you may include sensitive information in the project files and provisioning package (.ppkg) file. Although you have the option to encrypt the .ppkg file, project files are not encrypted. You should store the project files in a secure location and delete the project files when no longer needed.
-
-1. On the **Export** menu, select **Provisioning package**.
-
-1. Change **Owner** to **IT Admin**, which sets the precedence of this provisioning package to be higher than others applied to this device from different sources, and then select **Next**.
-
-1. Set a value for **Package Version**.
-
- > [!TIP]
- > You can make changes to existing packages and change the version number to update previously applied packages.
-
-1. On **Select security details for the provisioning package**, select **Next**.
-
-1. Select **Next** to specify the output location where you want the provisioning package to go once it's built. By default, Windows ICD uses the project folder as the output location.
-
- Optionally, you can select **Browse** to change the default output location.
-
-1. Select **Next**.
-
-1. Select **Build** to start building the package. The build page displays the project information, and the progress bar indicates the build status.
-
-1. When the build completes, select **Finish**.
-
-### Apply the provisioning package to HoloLens
-
-1. Using the USB cable, connect the device to a PC. Start the device, but do not continue past the **fit** page of the initial setup experience (the first page with the blue box). On the PC, HoloLens shows up as a device in File Explorer.
-
- > [!NOTE]
- > If the HoloLens device is running Windows 10, version 1607 or earlier, open File Explorer by briefly pressing and releasing the **Volume Down** and **Power** buttons simultaneously on the device.
-
-1. In File Explorer, drag and drop the provisioning package (.ppkg) onto the device storage.
-
-1. While HoloLens is still on the **fit** page, briefly press and release the **Volume Down** and **Power** buttons simultaneously again.
-
-1. HoloLens asks you if you trust the package and would like to apply it. Confirm that you trust the package.
-
-1. You will see whether the package was applied successfully or not. If it was not applied successfully, you can fix your package and try again. If successful, proceed with device setup.
diff --git a/devices/hololens/hololens2-autopilot.md b/devices/hololens/hololens2-autopilot.md
deleted file mode 100644
index 5589ec096d..0000000000
--- a/devices/hololens/hololens2-autopilot.md
+++ /dev/null
@@ -1,248 +0,0 @@
----
-title: Windows Autopilot for HoloLens 2 evaluation guide
-description:
-author: Teresa-Motiv
-ms.author: v-tea
-ms.date: 4/10/2020
-ms.prod: hololens
-ms.topic: article
-ms.custom:
-- CI 116283
-- CSSTroubleshooting
-audience: ITPro
-ms.localizationpriority: high
-keywords: autopilot
-manager: jarrettr
-appliesto:
-- HoloLens 2
----
-
-# Windows Autopilot for HoloLens 2 evaluation guide
-
-When you set up HoloLens 2 devices for the Windows Autopilot program, your users can follow a simple process to provision the devices from the cloud.
-
-This Autopilot program supports Autopilot self-deploying mode to provision HoloLens 2 devices as shared devices under your tenant. Self-deploying mode leverages the device's preinstalled OEM image and drivers during the provisioning process. A user can provision the device without putting the device on and going through the Out-of-the-box Experience (OOBE).
-
-
-
-When a user starts the Autopilot self-deploying process, the process completes the following steps:
-
-1. Join the device to Azure Active Directory (Azure AD).
- > [!NOTE]
- > Autopilot for HoloLens does not support Active Directory join or Hybrid Azure AD join.
-1. Use Azure AD to enroll the device in Microsoft Intune (or another MDM service).
-1. Download the device-targeted policies, user-targeted apps, certificates, and networking profiles.
-1. Provision the device.
-1. Present the sign-in screen to the user.
-
-## Windows Autopilot for HoloLens 2: Get started
-
-The following steps summarize the process of setting up your environment for the Windows Autopilot for HoloLens 2. The rest of this section provides the details of these steps.
-
-1. Make sure that you meet the requirements for Windows Autopilot for HoloLens.
-1. Enroll in the Windows Autopilot for HoloLens 2 program.
-1. Verify that your tenant is flighted (enrolled to participate in the program).
-1. Register devices in Windows Autopilot.
-1. Create a device group.
-1. Create a deployment profile.
-1. Verify the ESP configuration.
-1. Configure a custom configuration profile for HoloLens devices (known issue).
-1. Verify the profile status of the HoloLens devices.
-
-### 1. Make sure that you meet the requirements for Windows Autopilot for HoloLens
-For the latest information about how to participate in the program, review [Windows Insider Release Notes](hololens-insider.md#windows-insider-release-notes).
-
-Review the following sections of the Windows Autopilot requirements article:
-
-- [Network requirements](https://docs.microsoft.com/windows/deployment/windows-autopilot/windows-autopilot-requirements#networking-requirements)
-- [Licensing requirements](https://docs.microsoft.com/windows/deployment/windows-autopilot/windows-autopilot-requirements#licensing-requirements)
-- [Configuration requirements](https://docs.microsoft.com/windows/deployment/windows-autopilot/windows-autopilot-requirements#configuration-requirements)
-> [!IMPORTANT]
-> Unlike other Windows Autopilot programs, Windows Autopilot for HoloLens 2 has specific operating system requirements.
-
-Review the "[Requirements](https://docs.microsoft.com/windows/deployment/windows-autopilot/self-deploying#requirements)" section of the Windows Autopilot Self-Deploying mode article. Your environment has to meet these requirements as well as the standard Windows Autopilot requirements.
-
-> [!NOTE]
-> You do not have to review the "Step by step" and "Validation" sections of the article. The procedures later in this article provide corresponding steps that are specific to HoloLens.
-
-> [!IMPORTANT]
-> For information about how to register devices and configure profiles, see [4. Register devices in Windows Autopilot](#4-register-devices-in-windows-autopilot) and [6. Create a deployment profile](#6-create-a-deployment-profile) in this article. These sections provide steps that are specific to HoloLens.
-
-Before you start the OOBE and provisioning process, make sure that the HoloLens devices meet the following requirements:
-
-- The devices are not already members of Azure AD, and are not enrolled in Intune (or another MDM system). The Autopilot self-deploying process completes these steps. To make sure that all the device-related information is cleaned up, check the **Devices** pages in both Azure AD and Intune.
-- Every device can connect to the internet. You can use a wired or wireless connection.
-- Every device can connect to a computer by using a USB-C cable, and that computer has the following available:
- - Advanced Recovery Companion (ARC)
- - The latest Windows update: Windows 10, version 19041.1002.200107-0909 or a later version)
-
-To configure and manage the Autopilot self-deploying mode profiles, make sure that you have access to [Microsoft Endpoint Manager admin center](https://endpoint.microsoft.com).
-
-### 2. Enroll in the Windows Autopilot for HoloLens 2 program
-
-To participate in the program, you have to use a tenant that is flighted for HoloLens. To do this, go to [Windows Autopilot for HoloLens Private Preview request](https://aka.ms/APHoloLensTAP) or use the following QR code to submit a request.
-
-
-
-In this request, provide the following information:
-
-- Tenant domain
-- Tenant ID
-- Number of HoloLens 2 devices that are participating in this evaluation
-- Number of HoloLens 2 devices that you plan to deploy by using Autopilot self-deploying mode
-
-### 3. Verify that your tenant is flighted
-
-To verify that your tenant is flighted for the Autopilot program after you submit your request, follow these steps:
-
-1. Sign in to [Microsoft Endpoint Manager admin center](https://endpoint.microsoft.com).
-1. Select **Devices** > **Windows** > **Windows enrollment** > **Windows Autopilot deployment profiles** > **Create profile**.
-
- 
- You should see a list that includes **HoloLens**. If this option is not present, use one of the [Feedback](#feedback) options to contact us.
-
-### 4. Register devices in Windows Autopilot
-
-To register a HoloLens device in the Windows Autopilot program, you have to obtain the hardware hash of the device (also known as the hardware ID). The device can record its hardware hash in a CSV file during the OOBE process, or later when a device owner starts the diagnostic log collection process (described in the following procedure). Typically, the device owner is the first user to sign in to the device.
-
-**Retrieve a device hardware hash**
-
-1. Start the HoloLens 2 device.
-1. On the device, press the Power and Volume Down buttons at the same time and then release them. The device collects diagnostic logs and the hardware hash, and stores them in a set of .zip files.
-1. Use a USB-C cable to connect the device to a computer.
-1. On the computer, open File Explorer. Open **This PC\\\<*HoloLens device name*>\\Internal Storage\\Documents**, and locate the AutopilotDiagnostics.zip file.
-
- > [!NOTE]
- > The .zip file may not immediately be available. If the file is not ready yet you may see a HoloLensDiagnostics.temp file in the Documents folder. To update the list of files, refresh the window.
-
-1. Extract the contents of the AutopilotDiagnostics.zip file.
-1. In the extracted files, locate the CSV file that has a file name prefix of "DeviceHash." Copy that file to a drive on the computer where you can access it later.
- > [!IMPORTANT]
- > The data in the CSV file should use the following header and line format:
- > ```
- > Device Serial Number,Windows Product ID,Hardware Hash,Group Tag,Assigned User ,,,,
- >```
-
-**Register the device in Windows Autopilot**
-
-1. In Microsoft Endpoint Manager Admin Center, select **Devices** > **Windows** > **Windows enrollment**, and then select **Devices** > **Import** under **Windows Autopilot Deployment Program**.
-
-1. Under **Add Windows Autopilot devices**, select the DeviceHash CSV file, select **Open**, and then select **Import**.
-
- 
-1. After the import finishes, select **Devices** > **Windows** > **Windows enrollment** > **Devices** > **Sync**. The process might take a few minutes to complete, depending on how many devices are being synchronized. To see the registered device, select **Refresh**.
-
- 
-
-### 5. Create a device group
-
-1. In Microsoft Endpoint Manager admin center, select **Groups** > **New group**.
-1. For **Group type**, select **Security**, and then enter a group name and description.
-1. For **Membership type**, select either **Assigned** or **Dynamic Device**.
-1. Do one of the following:
-
- - If you selected **Assigned** for **Membership type** in the previous step, select **Members**, and then add Autopilot devices to the group. Autopilot devices that aren't yet enrolled are listed by using the device serial number as the device name.
- - If you selected **Dynamic Devices** for **Membership type** in the previous step, select **Dynamic device members**, and then enter code in **Advanced rule** that resembles the following:
- - If you want to create a group that includes all of your Autopilot devices, type: `(device.devicePhysicalIDs -any _ -contains "[ZTDId]")`
- - Intune's group tag field maps to the **OrderID** attribute on Azure AD devices. If you want to create a group that includes all of your Autopilot devices that have a specific group tag (the Azure AD device OrderID), you must type: `(device.devicePhysicalIds -any _ -eq "[OrderID]:179887111881")`
- - If you want to create a group that includes all your Autopilot devices that have a specific Purchase Order ID, type: `(device.devicePhysicalIds -any _ -eq "[PurchaseOrderId]:76222342342")`
-
- > [!NOTE]
- > These rules target attributes that are unique to Autopilot devices.
-1. Select **Save**, and then select **Create**.
-
-### 6. Create a deployment profile
-
-1. In Microsoft Endpoint Manager admin center, select **Devices** > **Windows** > **Windows enrollment** > **Windows Autopilot deployment profiles** > **Create profile** > **HoloLens**.
-1. Enter a profile name and description, and then select **Next**.
-
- 
-1. On the **Out-of-box experience (OOBE)** page, most of the settings are pre-configured to streamline OOBE for this evaluation. Optionally, you can configure the following settings:
-
- - **Language (Region)**: Select the language for OOBE. We recommend that you select a language from the list of [supported languages for HoloLens 2](hololens2-language-support.md).
- - **Automatically configure keyboard**: To make sure that the keyboard matches the selected language, select **Yes**.
- - **Apply device name template**: To automatically set the device name during OOBE, select **Yes** and then enter the template phrase and placeholders in **Enter a name** For example, enter a prefix and `%RAND:4%`—a placeholder for a four-digit random number.
- > [!NOTE]
- > If you use a device name template, the OOBE process restarts the device one additional time after it applies the device name and before it joins the device to Azure AD. This restart enables the new name to take effect.
-
- 
-1. After you configure the settings, select **Next**.
-1. On the **Scope tags** page, optionally add the scope tags that you want to apply to this profile. For more information about scope tags, see [Use role-based access control and scope tags for distributed IT](https://docs.microsoft.com/mem/intune/fundamentals/scope-tags.md). When finished, select **Next**.
-1. On the **Assignments** page, select **Selected groups** for **Assign to**.
-1. Under **SELECTED GROUPS**, select **+ Select groups to include**.
-1. In the **Select groups to include** list, select the device group that you created for the Autopilot HoloLens devices, and then select **Next**.
-
- If you want to exclude any groups, select **Select groups to exclude**, and select the groups that you want to exclude.
-
- 
-1. On the **Review + Create** page, review the settings and then select **Create** to create the profile.
-
- 
-
-### 7. Verify the ESP configuration
-
-The Enrollment Status Page (ESP) displays the status of the complete device configuration process that runs when an MDM managed user signs into a device for the first time. Make sure that your ESP configuration resembles the following, and verify that the assignments are correct.
-
-
-
-### 8. Configure a custom configuration profile for HoloLens devices (known issue)
-
-1. In [Microsoft Endpoint Manager admin center](https://endpoint.microsoft.com), select **Devices** > **Configuration profiles** > **Create profile**.
-1. For **Platform**, specify **Windows 10 and later**, and for **Profile**, select **Custom**.
-1. Select **Create**.
-1. Enter a name for the profile, and then select **Settings** > **Configure**.
-
- 
-1. Select **Add**, and then specify the following information:
-
- - **Name**: SidecarPath
- - **OMA-URI**: ./images/Device/Vendor/MSFT/EnrollmentStatusTracking/DevicePreparation/PolicyProviders/Sidecar/InstallationState
- - **Data type**: Integer
- - **Value**: 2
-1. Select **OK** two times, and then select **Create** to create the profile.
-1. After Intune creates the configuration profile, assign the configuration profile to the device group for the HoloLens devices.
-
-### 9. Verify the profile status of the HoloLens devices
-
-1. In Microsoft Endpoint Manager Admin Center, select **Devices** > **Windows** > **Windows enrollment** > **Devices**.
-1. Verify that the HoloLens devices are listed, and that their profile status is **Assigned**.
- > [!NOTE]
- > It may take a few minutes for the profile to be assigned to the device.
-
- 
-
-## Windows Autopilot for HoloLens 2 User Experience
-
-Your HoloLens users can follow these steps to provision HoloLens devices.
-
-1. Use the USB-C cable to connect the HoloLens device to a computer that has Advanced Recovery Companion (ARC) installed and has the appropriate Windows update downloaded.
-1. Use ARC to flash the appropriate version of Windows on to the device.
-1. Connect the device to the network, and then restart the device.
- > [!IMPORTANT]
- > You must connect the device to the network before the Out-of-the-Box-Experience (OOBE) starts. The device determines whether it is provisioning as an Autopilot device while on the first OOBE screen. If the device cannot connect to the network, or if you choose not to provision the device as an Autopilot device, you cannot change to Autopilot provisioning at a later time. Instead, you would have to start this procedure over in order to provision the device as an Autopilot device.
-
- The device should automatically start OOBE. Do not interact with OOBE. Instead sit, back and relax! Let HoloLens 2 detect network connectivity and allow it complete OOBE automatically. The device may restart during OOBE. The OOBE screens should resemble the following.
-
- 
- 
- 
- 
-
-At the end of OOBE, you can sign in to the device by using your user name and password.
-
- 
-
-## Known Issues
-
-- The list of supported languages for Autopilot deployment profiles includes languages that HoloLens does not support. Select a language that [HoloLens supports](hololens2-language-support.md).
-
-## Feedback
-
-To provide feedback or report issues, use one of the following methods:
-
-- Use the Feedback Hub app. You can find this app on a HoloLens-connected computer. In Feedback Hub, select the **Enterprise Management** > **Device** category.
-
- When you provide feedback or report an issue, provide a detailed description. If applicable, include screenshots and logs.
-- Send an email message to [hlappreview@microsoft.com](mailto:hlappreview@microsoft.com). For the email subject, enter **\<*Tenant*> Autopilot for HoloLens 2 evaluation feedback** (where \<*Tenant*> is the name of your Intune tenant).
-
- Provide a detailed description in your message. However, unless Support personnel specifically request it, do not include data such as screenshots or logs. Such data might include private or personally identifiable information (PII).
diff --git a/devices/hololens/hololens2-basic-usage.md b/devices/hololens/hololens2-basic-usage.md
deleted file mode 100644
index 59426de18e..0000000000
--- a/devices/hololens/hololens2-basic-usage.md
+++ /dev/null
@@ -1,192 +0,0 @@
----
-title: Getting around HoloLens 2
-description: A guide to using HoloLens 2 with your hands
-ms.assetid: 5f791a5c-bdb2-4c5d-bf46-4a198de68f21
-ms.date: 9/17/2019
-keywords: hololens
-ms.prod: hololens
-ms.sitesec: library
-author: scooley
-ms.author: scooley
-ms.topic: article
-ms.localizationpriority: high
-appliesto:
-- HoloLens 2
----
-
-# Getting around HoloLens 2
-
-Ready to explore the world of holograms?
-
-This guide provides an intro to:
-
-- Interacting with mixed reality
-- Using your hands and voice for interacting with holograms on HoloLens 2
-- Navigating Windows 10 on HoloLens (Windows Holographic)
-
-## Discover mixed reality
-
-On HoloLens, holograms blend the digital world with your physical environment to look and sound like they're part of your world. Even when holograms are all around you, you can always see your surroundings, move freely, and interact with people and objects. We call this experience "mixed reality".
-
-The holographic frame positions your holograms where your eyes are most sensitive to detail and the see-through lenses leave your peripheral vision clear. With spatial sound, you can pinpoint a hologram by listening, even if it’s behind you. And, because HoloLens understands your physical environment, you can place holograms on and around real objects such as tables and walls.
-
-Getting around HoloLens is a lot like using your smart phone. You can use your hands to touch and manipulate holographic windows, menus, and buttons.
-
-Once you know these basic interactions, getting around on HoloLens will be a snap.
-
-> [!TIP]
-> If you have a HoloLens near you right now, the **Tips** app provides literal hands-on tutorials for hand interactions on HoloLens.
-> Use the start gesture to go to **Start** or say "Go to Start" and select **Tips**.
-
-## The hand-tracking frame
-
-HoloLens has sensors that can see a few feet to either side of you. When you use your hands, you'll need to keep them inside that frame, or HoloLens won't see them. However, the frame moves with you as you move around.
-
-
-
-## Touch holograms near you
-
-When a hologram is near you, bring your hand close to it and a white ring should appear on the tip of your index finger. This is the **touch cursor** which helps you touch and interact with holograms with precision. To **select** something, simply **tap** it with the touch cursor. **Scroll** content by **swiping** on the surface of the content with your finger, just like you're using a touch screen.
-
-To **grab** a hologram near you, pinch your **thumb** and **index finger** together on the hologram and hold. To let go, release your fingers. Use this **grab gesture** to move, resize, and rotate 3D objects and app windows in mixed reality home.
-
-To bring up a **context menu**, like the ones you'll find on an app tile in the Start menu, **tap and hold** like you do on a touch screen.
-
-## Use hand ray for holograms out of reach
-
-> [!VIDEO https://www.microsoft.com/videoplayer/embed/RE3ZOum]
-
-When there are no holograms near your hands, the **touch cursor** will hide automatically and **hand rays** will appear from the palm of your hands. Hand rays allow you to interact with holograms from a distance.
-
-> [!TIP]
-> If you find hand rays distracting, you can hide them by saying “Hide hand rays”. To make them reappear, say "Show hand rays."
-
-### Select using air tap
-
-To select something using **hand ray**, follow these steps:
-
-1. Use a hand ray from your palm to target the item. You don't need to raise your entire arm, you can keep your elbow low and comfortable.
-1. Point your index finger straight up toward the ceiling.
-1. To perform the **air tap** gesture, pinch your thumb and index finger together and then quickly release them.
-
- 
-
-### Grab using air tap and hold
-
-> [!VIDEO https://www.microsoft.com/videoplayer/embed/RE3Wxnh]
-
-To grab a hologram or scroll app window content using **hand ray**, start with an **air tap**, but keep your fingers together instead of releasing them.
-
-Use **air tap and hold** to perform the following actions with hand ray:
-
-- **Scroll**. To scroll app window content, air tap and hold on the content and then move your hand ray up and down or side to side.
-- **Grab**. To grab an app window or hologram, target the app title bar or hologram with your hand ray and then air tap and hold.
-- **Open context menus**. To open context menus, air tap and hold with your hand ray.
-
-## Start gesture
-
-> [!VIDEO https://www.microsoft.com/videoplayer/embed/RE3Wxng]
-
-The Start gesture opens the **Start menu**. To perform the Start gesture, hold out your hand with your palm facing you. You’ll see a **Start icon** appear over your inner wrist. Tap this icon using your other hand. The Start menu will open **where you’re looking**.
-
-> [!TIP]
->
-> - You can use the Start gesture as long as your hands are inside the hand-tracking frame. You do not need to be looking down at the Start icon. Keep your elbow low and comfortable, and look in the direction where you want the Start menu to open.
-> - If the Start menu didn't open at the position you want, simply move your head around to reposition it.
-> - If you have trouble reading the smaller text on the Start menu, step closer to it after it opens.
-> - If your hand is slightly off to the side of the frame, you may still be able to view the Start menu by tapping your inner wrist, even if you don't see the icon.
-
-
-
-To **close** the Start menu, do the Start gesture when the Start menu is open. You can also look at the Start menu and say "Close".
-
-### One-handed Start gesture
-
-> [!IMPORTANT]
-> For the one-handed Start gesture to work:
->
-> 1. You must update to the November 2019 update (build 18363.1039) or later.
-> 1. Your eyes must be calibrated on the device so that eye tracking functions correctly. If you do not see orbiting dots around the Start icon when you look at it, your eyes are not [calibrated](https://docs.microsoft.com/hololens/hololens-calibration#calibrating-your-hololens-2) on the device.
-
-You can also perform the Start gesture with only one hand. To do this, hold out your hand with your palm facing you and look at the **Start icon** on your inner wrist. **While keeping your eye on the icon**, pinch your thumb and index finger together.
-
-
-
-## Start menu, mixed reality home, and apps
-
-Ready to put all these hand interactions to the test?!
-
-You'll find your installed apps in the [Start menu](holographic-home.md) and you can find additional apps for HoloLens in the [Microsoft Store](holographic-store-apps.md).
-
-Just as Windows PC always starts its experience at the desktop, HoloLens always starts in **mixed reality home** when turned on. Using the Start menu, you can open and place app windows, as well as app launchers and 3D content in mixed reality home. Their placements in your physical space will be remembered by HoloLens.
-
-Open the **Start menu**, then select the **Settings** app tile. An app window will open in front of you.
-
-Settings is an example of a HoloLens app that uses a 2D **app window**. It's very similar to a Windows application on PC.
-
-Now you can open the **Start menu** again and select the **Tips** app tile. A 3D **app launcher** for the app will appear in front of you. To open the app, you need to select the **play** button on the launcher.
-
-Tips is an example of an **immersive app**. An immersive app takes you away from mixed reality home when it runs and becomes the only app you see. To exit, you need to bring up the Start menu and select the **mixed reality home** button at the bottom.
-
-[Go here to learn more](holographic-home.md) about Start menu and mixed reality home, including info on how to use and manage apps on HoloLens 2.
-
-## Move, resize, and rotate holograms
-
-In mixed reality home you can move, resize, and rotate app windows and 3D objects using your hands, hand ray and voice commands.
-
-### Moving holograms
-
-Move a hologram or app by following these steps:
-
-1. Grab the hologram by pinching your index finger and thumb on the hologram or face your hand down and then close your fist over it. Grab a 3D hologram anywhere inside its blue bounding box. For an app window, grab its title bar.
-1. Without letting go, move your hand to position the hologram. When moving an app window this way, the app window automatically turns to face you as it moves, making it easier to use at its new position.
-1. Release your fingers to place it.
-
-### Resizing holograms
-
-> [!VIDEO https://www.microsoft.com/videoplayer/embed/RE3ZYIb]
-
-Grab and use the **resize handles** that appear on the corners of 3D holograms and app windows to resize them.
-
-For an app window, when resized this way the window content correspondingly increases in size and becomes easier to read.
-
-If you want to resize an app window so that **more content** appears in the window, use the resize handles located on the sides and bottom edges of the app window.
-
-There are two ways to resize a hologram that's further away from you. You can either grab two corners of the hologram, or use the resize controls.
-
-### Rotating holograms
-
-For 3D holograms, grab and use the rotate handles that appear on the vertical edges of the bounding box.
-
-For app windows, moving an app window will cause it to automatically rotate and face you.
-
-You can also grab a 3D hologram or app window with **both hands** (or hand ray) at once and then:
-
-- Move your hands closer together or further apart to resize the hologram.
-- Move your hands closer and further away from your body to rotate the hologram.
-
-### Follow me, stop following
-
-Holograms and app windows stay where you placed them in the world. That's not always convenient if you need to move around and you want an application to stay visible. To ask an app to start or stop following you, select **Follow me** in the top right corner of the app window (next to the **Close** button). An app window that is following you will also follow you into, an out of, an immersive app.
-
-## Use HoloLens with your voice
-
-You can use your voice to do most of the same things you do with hands on HoloLens, like taking a quick photo or opening an app.
-
-| To do this | Say this |
-| - | - |
-| Open the Start menu | "Go to Start" |
-| Select | Say "select" to bring up the gaze cursor. Then, turn your head to position the cursor on the thing you want to select, and say “select” again. |
-| See available speech commands | "What can I say?" |
-
- [See more voice commands and ways to use speech with HoloLens](hololens-cortana.md)
-
-## Next steps
-
-Congratulations! You're ready to use HoloLens 2!
-
-Now you can configure your HoloLens 2 to meet your specific needs. Other things you may want to try include:
-
-- [Connecting bluetooth devices like a mouse and keyboard](hololens-connect-devices.md)
-- [Installing apps from the store](holographic-store-apps.md)
-- [Sharing your HoloLens with other people](hololens-multiple-users.md)
diff --git a/devices/hololens/hololens2-fit-comfort-faq.md b/devices/hololens/hololens2-fit-comfort-faq.md
deleted file mode 100644
index e97e03f502..0000000000
--- a/devices/hololens/hololens2-fit-comfort-faq.md
+++ /dev/null
@@ -1,69 +0,0 @@
----
-title: HoloLens 2 fit and comfort FAQ
-description: Answers to frequently asked questions about how to fit your HoloLens 2.
-ms.prod: hololens
-ms.sitesec: library
-author: Teresa-Motiv
-ms.author: v-tea
-ms.topic: article
-audience: ItPro
-ms.localizationpriority: high
-ms.date: 11/07/2019
-ms.reviewer: jarrettr
-manager: jarrettr
-appliesto:
-- HoloLens 2
----
-
-# HoloLens 2 fit and comfort frequently asked questions
-
-Here are some tips on how to stay comfortable and have the best experience using your HoloLens.
-
-For step-by-step instructions and a video about putting on and adjusting your device, see [Get your HoloLens 2 ready to use](hololens2-setup.md).
-
-> [!NOTE]
-> The fit and comfort tips in this topic are meant only as general guidance—they don't replace any laws or regulations, or your good judgment when using HoloLens. Stay safe, and have fun!
-
-Here are some tips on how to stay comfortable and have the best experience using your HoloLens.
-
-## I'm experiencing discomfort when I use my device. What should I do?
-
-If you experience discomfort, take a break until you feel better. Try sitting in a well-lit room and relaxing for a bit. The next time your use your HoloLens, try using it for a shorter period of time at first.
-
-For more information, see [Health and safety on HoloLens](https://go.microsoft.com/fwlink/p/?LinkId=746661).
-
-## I can't see the whole holographic frame, or my holograms are cut off
-
-To see the top edge of the holographic frame, move the device so it sits higher on your head, or angle the headband up slightly in front. To see the bottom edge, move the device to sit lower on your head, or angle the headband down slightly in front. If the left or right edge of the view frame isn't visible, make sure the HoloLens visor is centered on your forehead.
-
-## I need to look up or down to see holograms
-
-Try adjusting the position of your device visor so the holographic frame matches your natural gaze. Here's how:
-
-- **If you need to look up to see holograms**. First, shift the back of the headband a bit higher on your head. Then use one hand to hold the headband in place and the other to gently rotate the visor so you have a good view of the holographic frame.
-- **If you need to look down to see holograms**. First, shift the back of the headband a bit lower on your head. Then place your thumbs under the device arms and your index fingers on top of the headband, and gently squeeze with your thumbs to rotate the visor so you have a good view of the holographic frame.
-
-## Hologram image color or brightness does not look right
-
-For HoloLens 2, take the following steps to ensure the highest visual quality of holograms presented in displays:
-
-- **Increase brightness of the display.** Holograms look best when the display is at its brightest level.
-- **Bring visor closer to your eyes.** Swing the visor down to the closest position to your eyes.
-- **Shift visor down.** Try moving the brow pad on your forehead down, which will result in the visor moving down closer to your nose.
-- **Run eye calibration.** The display uses your IPD and eye gaze to optimize images on the display. If you don't run eye calibration, the image quality may be made worse.
-
-## The device slides down when I'm using it, or I need to make the headband too tight to keep it secure
-
-The overhead strap can help keep your HoloLens secure on your head, particularly if you're moving around a lot. The strap may also let you loosen the headband a bit. [Learn how to use it](hololens2-setup.md#adjust-fit).
-
-You can also experiment with the positioning of the headband—depending on your head size and shape, you may need to slide it up or down to reposition it on your forehead.
-
-## How can I adjust HoloLens to fit with my glasses?
-
-To accommodate eyewear, you can tilt the visor.
-
-## My arm gets tired when I use gestures. What can I do?
-
-When using gestures, there's no need to extend your arm out far from your body. Keep it closer to your side, where it's more comfortable and will get less tired. You can also use hand rays to interact with holograms without raising your arms [Learn more about gestures and hand rays](hololens2-basic-usage.md#the-hand-tracking-frame).
-
-And be sure to try out [voice commands](hololens-cortana.md).
diff --git a/devices/hololens/hololens2-hardware.md b/devices/hololens/hololens2-hardware.md
deleted file mode 100644
index ca62dbf852..0000000000
--- a/devices/hololens/hololens2-hardware.md
+++ /dev/null
@@ -1,162 +0,0 @@
----
-title: HoloLens 2 hardware
-description: An outline of the components that make up Microsoft HoloLens 2, the latest evolution of Microsoft's fully untethered holographic computer running Windows 10.
-ms.assetid: 651d0430-bfbc-4685-a4fd-db7c33ce9325
-ms.date: 9/17/2019
-keywords: hololens
-ms.prod: hololens
-ms.sitesec: library
-author: scooley
-ms.author: scooley
-ms.topic: article
-ms.localizationpriority: high
-appliesto:
-- HoloLens 2
----
-
-# HoloLens 2 hardware
-
-
-
-Microsoft HoloLens 2 is an untethered holographic computer. It refines the holographic computing journey started by HoloLens (1st gen) to provide a more comfortable and immersive experience paired with more options for collaborating in mixed reality.
-
-## HoloLens components
-
-- **Visor**. Contains the HoloLens sensors and displays. You can rotate the visor up while wearing the HoloLens.
-- **Headband**. To put the HoloLens on, use the adjustment wheel to expand the headband. With the HoloLens in place, tighten the adjustment wheel by turning to the right, until the headband is comfortable.
-- **Brightness buttons**. When wearing the HoloLens, the brightness buttons are on the left side of the device.
-- **Volume buttons**. When wearing the HoloLens, the volume buttons are on the right side of the device.
-
-## In the box
-
-- **Brow pad**. You can remove and replace the brow pad, as needed.
-- **Overhead strap**. When you're wearing the HoloLens while moving around, use the overhead strap to help keep the device in place. When wearing the HoloLens for extended periods, the overhead strap may make the device more comfortable to wear.
-- **USB-C cable**. Use the USB-C cable to connect your HoloLens to the power supply for charging, or to connect your HoloLens to your computer.
-- **Power supply**. Plugs into a power outlet.
-- **Microfiber cloth**. Use to clean your HoloLens visor.
-
-### Power Supply details
-
-The power supply and the USB cable that come with the device are the best supported mechanism for charging. The power supply is an 18W charger. It's supplies 9V at 2A.
-
-Charging rate and speed may vary depending on the environment in which the device is running.
-
-In order to maintain/advance Internal Battery Charge Percentage while the device is on, it must be connected minimum to a 15W charger.
-
-## Device specifications
-
-### Display
-
-| | |
-| - | - |
-| Optics | See-through holographic lenses (waveguides) |
-| Holographic resolution | 2k 3:2 light engines |
-| Holographic density | >2.5k radiants (light points per radian) |
-| Eye-based rendering | Display optimization for 3D eye position |
-
-### Sensors
-
-| | |
-| - | - |
-| Head tracking | 4 visible light cameras |
-| Eye tracking | 2 Infrared (IR) cameras |
-| Depth | 1-MP Time-of-Flight depth sensor |
-| Inertial measurement unit (IMU) | Accelerometer, gyroscope, magnetometer |
-| Camera | 8-MP stills, 1080p30 video |
-
-### Audio and speech
-
-| | |
-| - | - |
-| Microphone array | 5 channels |
-| Speakers | Built-in spatial sound |
-
-### Compute and connectivity
-
-| | |
-| - | - |
-| System on chip | Qualcomm Snapdragon 850 Compute Platform [details](https://www.qualcomm.com/products/snapdragon-850-mobile-compute-platform) |
-| Holographic processing unit | Second-generation custom-built holographic processing unit |
-| Memory | 4-GB LPDDR4x system DRAM |
-| Storage | 64-GB UFS 2.1 |
-| WiFi | 802.11ac 2x2 |
-| Bluetooth | 5.0 |
-| USB | USB Type-C |
-
-### Power
-
-| | |
-| - | - |
-| Battery Life | 2-3 hours of active use. Up to 2 weeks of standby time. |
-| Battery technology | [Lithium batteries](https://www.microsoft.com/download/details.aspx?id=43388) |
-| Charging behavior | Fully functional when charging |
-| Cooling type | Passively cooled (no fans) |
-| Power draw | In order to maintain/advance Internal Battery Charge Percentage while the device is on, it must be connected minimum to a 15W charger. |
-
-### Fit
-
-| | |
-| - | - |
-| Sizing | Single size with adjustable band. Fits over eyeglasses |
-| Weight | 566 grams |
-
-## Device capabilities
-
-### Human understanding
-
-| | |
-| - | - |
-| Hand tracking | Two-handed fully articulated model, direct manipulation |
-| Eye tracking | Real-time tracking |
-| Voice | Command and control on-device; Cortana natural language with internet connectivity |
-
-### Environment understanding
-
-| | |
-| - | - |
-| Six Degrees of Freedom (6DoF) tracking | World-scale positional tracking |
-| Spatial mapping | Real-time environment mesh |
-| Mixed reality capture | Mixed hologram and physical environment photos and videos |
-
-## Pre-installed software
-
-- Windows Holographic Operating System
-- Microsoft Edge
-- Dynamics 365 Remote Assist
-- Dynamics 365 Layout
-- Dynamics 365 Guides
-- 3D Viewer
-- OneDrive for Business
-- HoloLens Tips
-- Cortana
-
-## Device certifications
-
-### Safety
-
-HoloLens 2 has been tested and conforms to the basic impact protection requirements of ANSI Z87.1, CSA Z94.3 and EN 166.
-
-## Care and cleaning
-
-Handle your HoloLens carefully. Use the headband to lift and carry the HoloLens 2.
-
-As you would for eyeglasses or protective eye-wear, try to keep the HoloLens visor free of dust and fingerprints. When possible, avoid touching the visor. Repeated cleaning could damage the visor, so keep your device clean!
-
-Don't use any cleaners or solvents on your HoloLens, and don't submerge it in water or apply water directly to it.
-
-To clean the visor, remove any dust by using a camel or goat hair lens brush or a bulb-style lens blower. Lightly moisten the microfiber cloth with a small amount of distilled water, then use it to wipe the visor gently in a circular motion.
-
-Clean the rest of the device, including the headband and device arms, with a lint-free microfiber cloth moistened with mild soap and water. Let your HoloLens dry completely before reuse.
-
-
-
-### Replace the brow pad
-
-The brow pad is magnetically attached to the device. To detach it, pull gently away. To replace it, snap it back into place.
-
-
-
-## Next step
-
-> [!div class="nextstepaction"]
-> [Set up and start your HoloLens 2](hololens2-setup.md)
diff --git a/devices/hololens/hololens2-language-support.md b/devices/hololens/hololens2-language-support.md
deleted file mode 100644
index 955eec82e6..0000000000
--- a/devices/hololens/hololens2-language-support.md
+++ /dev/null
@@ -1,77 +0,0 @@
----
-title: Supported languages for HoloLens 2
-description:
-ms.prod: hololens
-ms.sitesec: library
-author: Teresa-Motiv
-ms.author: v-tea
-ms.topic: article
-ms.localizationpriority: medium
-ms.custom:
-- CI 115225
-- CSSTroubleshooting
-keywords: localize, language support, display language, keyboard language, IME, keyboard layout
-ms.date: 03/12/2020
-audience: ITPro
-ms.reviewer: jarrettr
-manager: jarrettr
-appliesto:
-- HoloLens 2
----
-
-# Supported languages for HoloLens 2
-
-HoloLens 2 is localized into the following languages. The localization features include speech commands and dictation, keyboard layouts, and OCR recognition within apps.
-
-- Chinese Simplified (China)
-- English (Australia)
-- English (Canada)
-- English (Great Britain)
-- English (United States)
-- French (Canada)
-- French (France)
-- German (Germany)
-- Italian (Italy)
-- Japanese (Japan)
-- Spanish (Spain)
-
-HoloLens 2 also supports the following languages. However, this support does not include speech commands or dictation features.
-
-- Chinese Traditional (Taiwan and Hong Kong)
-- Dutch (Netherlands)
-- Korean (Korea)
-
-Some features of HoloLens 2 use the Windows display language. The Windows display language affects the following settings for Windows and for apps that support localization:
-
-- The user interface text language.
-- The speech language.
-- The default layout of the on-screen keyboard.
-
-## Change the language or keyboard layout
-
-The setup process configures your HoloLens for a specific region and language. You can change this configuration by using the **Time & language** section of **Settings**.
-
-> [!NOTE]
-> Your speech and dictation language depends on (and is the same as) the Windows display language.
-
-### To change the Windows display language
-
-1. Open the **Start** menu, and then select **Settings** > **Time and language** > **Language**.
-2. Select **Windows display language**, and then select a language.
-
-If the supported language that you're looking for is not in the menu, follow these steps:
-
-1. Under **Preferred languages**, select **Add a language**.
-2. Locater and add the language.
-3. Select the **Windows display language** menu again, and then select the language that you added in the previous step.
-
-### To change the keyboard layout
-
-To add or remove a keyboard layout, open the **Start** menu, and then select **Settings** > **Time & language** > **Keyboard**.
-
-If your HoloLens has more than one keyboard layout, use the **Layout** key to switch between them. The **Layout** key is in the lower right corner of the on-screen keyboard.
-
-> [!NOTE]
-> The on-screen keyboard can use Input Method Editor (IME) to enter characters in languages such as Chinese. However, HoloLens does not support external Bluetooth keyboards that use IME.
->
-> While you use IME together with the on-screen keyboard, you can continue to use a Bluetooth keyboard to type in English. To switch between keyboards, press the tilde character button (**~**).
diff --git a/devices/hololens/hololens2-maintenance.md b/devices/hololens/hololens2-maintenance.md
deleted file mode 100644
index 845e36cba1..0000000000
--- a/devices/hololens/hololens2-maintenance.md
+++ /dev/null
@@ -1,84 +0,0 @@
----
-title: HoloLens 2 device care and cleaning FAQ
-description:
-author: Teresa-Motiv
-ms.author: v-tea
-ms.date: 4/14/2020
-ms.prod: hololens
-ms.topic: article
-ms.custom:
-- CI 115560
-- CSSTroubleshooting
-audience: ITPro
-ms.localizationpriority: medium
-keywords:
-manager: jarrettr
-appliesto:
-- HoloLens 2
----
-
-# Frequently asked questions about cleaning HoloLens 2 devices
-
-> [!IMPORTANT]
-> Microsoft cannot make a determination of the effectiveness of any given disinfectant product in fighting pathogens such as COVID-19. Please refer to your local public health authority's guidance about how to stay safe from potential infection.
-
-## What are the general cleaning instructions for HoloLens 2 devices?
-
-**To clean the device**
-
-1. Remove any dust by using a dry, lint-free microfiber cloth to gently wipe the surface of the device.
-1. Lightly moisten the cloth by using medical "70%" isopropyl alcohol, and then use the moistened cloth to gently wipe the surface of the device.
-
- 
-
-1. Let the device dry completely.
-
-**To clean the brow pad**
-
-1. Use water and a mild, antibiotic soap to moisten a cloth, and then use the moistened cloth to wipe the brow pad.
-1. Let the brow pad dry completely.
-
-## Can I use any lens cleaner for cleaning the HoloLens visor?
-
-No. Lens cleaners can be abrasive to the coatings on the visor. To clean the visor, follow these steps:
-
-1. Remove any dust by using a dry lint-free microfiber cloth to gently wipe the visor.
-1. Lightly moisten a cloth by using medical "70%" isopropyl alcohol, and then gently wipe the visor.
-1. Let the visor dry completely.
-
-## Can I use disinfecting wipes to clean the device?
-
-Yes, if the wipes do not contain bleach. You can use non-bleach disinfecting wipes to [gently wipe the HoloLens surfaces](#what-are-the-general-cleaning-instructions-for-hololens-2-devices).
-
-> [!CAUTION]
-> Avoid using disinfecting wipes that contains bleach to clean the HoloLens surfaces. It is acceptable to use bleach wipes in critical situations, when nothing else is available. However, bleach may damage the HoloLens visor or other surfaces.
-
-## Can I use alcohol to clean the device?
-
-Yes. You can use a solution of "70%" isopropyl alcohol and water to clean the hard surfaces of the device, including the visor. Lightly moisten the cloth by using a mix of isopropyl alcohol and water, and then gently wipe the surface of the device
-
-## Is the brow pad replaceable?
-
-Yes. The brow pad is magnetically attached to the device. To detach it, pull it gently away from the headband. To replace it, snap it back into place.
-
-
-
-## How can I clean the brow pad?
-
-To clean the brow pad, wipe it by using a cloth that's moistened by using water and a mild antibiotic soap. Let the brow pad dry completely before you use it again.
-
-## Can I use ultraviolet (UV) light to sanitize the device?
-
-UV-C germicidal irradiation has not been tested on HoloLens 2.
-
-> [!CAUTION]
-> High levels of UV-A and UV-B exposure can degrade the display quality of the device and damage the visor coating. Over-exposure to UV-A and UV-B radiation has the following effects, in order of the duration and intensity of exposure:
->
-> 1. The brow pad and device closures become discolored.
-> 1. Defects appear in the anti-reflective (AR) coating on the visor and on the sensor windows.
-> 1. Defects appear in the base materials of the visor and on the sensor windows.
-> 1. SRG performance degrades.
-
-## Is the rear pad replaceable?
-
-No.
diff --git a/devices/hololens/hololens2-setup.md b/devices/hololens/hololens2-setup.md
deleted file mode 100644
index 79189a7cf6..0000000000
--- a/devices/hololens/hololens2-setup.md
+++ /dev/null
@@ -1,120 +0,0 @@
----
-title: Prepare a new HoloLens 2
-description: This guide walks through first time set up and hardware guide.
-keywords: hololens, lights, fit, comfort, parts
-ms.assetid: 02692dcf-aa22-4d1e-bd00-f89f51048e32
-ms.date: 9/17/2019
-keywords: hololens
-ms.prod: hololens
-ms.sitesec: library
-author: scooley
-ms.author: scooley
-ms.topic: article
-ms.localizationpriority: high
-appliesto:
-- HoloLens 2
----
-
-# Get your HoloLens 2 ready to use
-
-The procedures below will help you set up a HoloLens 2 for the first time.
-
-## Charge your HoloLens
-
-Connect the power supply to the charging port by using the USB-C cable (included). Plug the power supply into a power outlet. The power supply and USB-C-to-C cable that come with the device are the best way to charge your HoloLens 2. The charger supplies 18W of power (9V at 2A).
-
-Charging rate and speed may vary depending on the environment in which the device is running.
-
-- When the device is charging, the battery indicator lights up to indicate the current level of charge. The last light will fade in and out to indicate active charging.
-- When your HoloLens is on, the battery indicator displays the battery level in increments.
-- When only one of the five lights is on, the battery level is below 20 percent.
-- If the battery level is critically low and you try to turn on the device, one light will blink briefly, then go out.
-
-## Adjust fit
-
-Place the HoloLens 2 on your head. If you wear eyeglasses, leave them on. The brow pad should sit comfortably on your forehead and the back band should sit in the middle-back of your head.
-
-If necessary, extend the headband by turning the adjustment wheel, and then loosen the overhead strap.
-
-
-
-### Attach and detach the overhead strap
-
-The overhead strap isn't required, but it can make wearing HoloLens 2 more comfortable during long periods of use.
-
-To detach the front of the overhead strap, unhook the strap and slide it through the retractable loop on the brow pad. To reattach it, pull out the loop and slide the strap back through.
-
-To detach the back of the overhead strap, press the button below each connection tab and pull gently. To reattach it, push the connection tabs back into the slots until they click.
-
-
-
-## Turn on the HoloLens 2
-
-To turn on your HoloLens 2, press the Power button. The LED lights below the Power button display the battery level.
-
-> [!NOTE]
-> To power on HoloLens 2 for the very first time, after unboxing, press and hold the power button for at least 4 seconds to turn it on. Next time you power on HoloLens 2, it’ll start after a short power button press.
-
-### Power button actions for different power transitions
-
-| To do this | Perform this action | The HoloLens 2 will do this |
-| - | - | - |
-| To turn on | Single button press. | All five lights turn on, then change to indicate the battery level. After four seconds, a sound plays. |
-| To sleep | Single button press. | All five lights turn on, then fade off one at a time. After the lights turn off, a sound plays and the screen displays "Goodbye." |
-| To wake from sleep | Single button press. | All five lights turn on, then change to indicate the battery level. A sound immediately plays. |
-| To turn off | Press and hold for 5s. | All five lights turn on, then fade off one at a time. After the lights turn off, a sound plays and the screen displays "Goodbye." |
-| To force the Hololens to restart if it is unresponsive | Press and hold for 10s. | All five lights turn on, then fade off one at a time. After the lights turn off. |
-
-## HoloLens behavior reference
-
-Not sure what the indicator lights on your HoloLens mean? Want to know how HoloLens should behave while charging? Here's some help!
-
-### Charging behavior
-
-| State of the Device | Action | HoloLens 2 will do this |
-| - | - | - |
-| OFF | Plug in USB Cable | Device transitions to ON with indicator lights showing battery level and device starts charging.
-| ON | Remove USB Cable | Device stops charging
-| ON | Plug in USB Cable | Device starts charging
-| SLEEP | Plug in USB Cable | Device starts charging
-| SLEEP | Remove USB Cable | Device stops charging
-| ON with USB cable plugged in | Turn off Device | Device transitions to ON with indicator lights showing battery level and device will start charging |
-
-### Lights that indicate the battery level
-
-| Number of lights | Battery level |
-| - | - |
-| Four solid lights, one light fading in and out | Between 100% and 81% (fully charged) |
-| Three solid lights, one light fading in and out | Between 80% and 61% |
-| Two solid lights, one light fading in and out | Between 60% and 41% |
-| One solid light, one light fading in and out | Between 40% and 21% |
-| One light fading in and out | Between 20% and 5% or lower (critical battery) |
-
-### Sleep Behavior
-
-| State of the Device | Action | HoloLens 2 will do this |
-| - | - | - |
-| ON | Single Power button press | Device transitions to SLEEP and turns off all indicator lights |
-| ON | No movement for 3 minutes | Device transition to SLEEP and turns off all indicator lights |
-| SLEEP | Single Power button Press | Device transitions to ON and turns on indicator lights |
-
-### Lights to indicate problems
-
-| When you do this | The lights do this | It means this |
-| - | - | - |
-| You press the Power button. | One light flashes five times, then turns off. | The HoloLens battery is critically low. Charge your HoloLens. |
-| You press the Power button. | All five lights flash five times, then turn off. | HoloLens cannot start correctly and is in an error state. [Reinstall the operating system](hololens-recovery.md) to recover your device. |
-| You press the Power button. | The 1st, 3rd, and 5th lights flash together continually. | HoloLens may have a hardware failure. To be sure, [reinstall the OS](hololens-recovery.md#hololens-2), and try again. After reinstalling the OS, if the light-flash pattern persists, contact [support](https://support.microsoft.com/en-us/supportforbusiness/productselection?sapid=3ec35c62-022f-466b-3a1e-dbbb7b9a55fb). |
-
-## Safety and comfort
-
-### Use HoloLens in safe surroundings
-
-Use your HoloLens in a safe space, free of obstructions and tripping hazards. Don’t use it when you need a clear field of view or can't commit your full attention, such as while you’re operating a vehicle or doing other potentially hazardous activities.
-
-### Stay comfortable
-
-Keep your first few sessions with HoloLens brief and be sure to take breaks. If you experience discomfort, stop and rest until you feel better. This might include temporary feelings of nausea, motion sickness, dizziness, disorientation, headache, fatigue, eye strain, or dry eyes.
-
-> [!div class="nextstepaction"]
-> [Start and configure your HoloLens 2](hololens2-start.md)
diff --git a/devices/hololens/hololens2-start.md b/devices/hololens/hololens2-start.md
deleted file mode 100644
index 78d3697f03..0000000000
--- a/devices/hololens/hololens2-start.md
+++ /dev/null
@@ -1,93 +0,0 @@
----
-title: Set up your HoloLens 2
-description: This guide walks through first time set up. You'll need a Wi-Fi network and either a Microsoft (MSA) or Azure Active Directory (AAD) account.
-ms.assetid: 507305f4-e85a-47c5-a055-a3400ae8a10e
-ms.date: 9/17/2019
-keywords: hololens
-ms.prod: hololens
-ms.sitesec: library
-author: scooley
-ms.author: scooley
-ms.topic: article
-ms.localizationpriority: high
-appliesto:
-- HoloLens 2
----
-
-# Set up your HoloLens 2
-
-The first time you turn on your HoloLens, you'll be guided through setting up your device, signing in with a user account, and calibrating the HoloLens to your eyes. This section walks through the HoloLens 2 initial setup experience.
-
-In the next section, you'll learn how to work with HoloLens and interact with holograms. To skip ahead to that article, see [Get started with HoloLens 2](hololens2-basic-usage.md).
-
-## Before you start
-
-Before you get started, make sure you have the following available:
-
-**A network connection**. You'll need to connect your HoloLens to a network to set it up. With HoloLens 2, you can connect with Wi-Fi or by using ethernet (you'll need a USB-C-to-Ethernet adapter). The first time you connect, you'll need an open or password-protected network that doesn't require navigating to a website or using certificates to connect. [Learn more about the websites that HoloLens uses](hololens-offline.md).
-
-**A Microsoft account**. You'll also need to sign in to HoloLens with a Microsoft account (or with your work account, if your organization owns the device). If you don't have a Microsoft account, go to [account.microsoft.com](https://account.microsoft.com) and set one up for free.
-
-**A safe, well-lit space with no tripping hazards**. [Health and safety info](https://go.microsoft.com/fwlink/p/?LinkId=746661).
-
-**The optional comfort accessories** that came with your HoloLens, to help you get the most comfortable fit. [More on fit and comfort](hololens2-setup.md#adjust-fit).
-
-## Set up Windows
-
-The first time you start your HoloLens 2, your first task is to set up Windows Holographic. When you start your HoloLens, you will hear music and see a Windows logo.
-
-
-
-HoloLens 2 will walk you through the following steps:
-
-1. Select your language.
- 
-
-1. Select your region.
- 
-
-1. Calibrate HoloLens to your eyes. If you choose to skip calibration, you'll be prompted the next time you log in.
-
- To calibrate, you'll look at a set of targets (referred to as gems). It's fine if you blink or close your eyes during calibration, but try not to stare at other objects in the room or physical space. HoloLens uses this process to learn about your eye position so that it can better render your holographic world. After calibration, holograms will appear correctly even as the visor shifts on your head.
-
- Calibration information is stored locally on the device and is not associated with any account information. For more information, see [Calibration data and security](hololens-calibration.md#calibration-data-and-security).
-
- 
-
-1. Connect to the internet (select Wi-Fi or your ethernet connection).
- HoloLens sets your time zone automatically based on information obtained from the Wi-Fi network. After setup finishes, you can change the time zone by using the Settings app.
-
- 
-> [!NOTE]
-> If you progress past the Wi-Fi step and later need to switch to a different network while still in setup, you can press the **Volume Down** and **Power** buttons simultaneously to return to this step if you are running an OS version from October 2019 or later. For earlier versions, you may need to [reset the device](hololens-recovery.md) or restart it in a location where the Wi-Fi network is not available to prevent it from automatically connecting.
->
-> Also note that during HoloLens Setup, there is a credential timeout of two minutes. The username/password needs to be entered within two minutes otherwise the username field will be automatically cleared.
-
-1. Sign in to your user account. You'll choose between **My work or school owns it** and **I own it**.
- - When you choose **My work or school owns it**, you sign in with an Azure AD account. If your organization uses Azure AD Premium and has configured automatic MDM enrollment, HoloLens automatically enrolls in MDM. If your organization does not use Azure AD Premium, automatic MDM enrollment isn't available. In that case, you need to [manually enroll HoloLens in device management](hololens-enroll-mdm.md#enroll-through-settings-app).
- 1. Enter your organizational account information.
- 1. Accept the privacy statement and the end user license agreement.
- 1. Sign in by using your Azure AD credentials. This may redirect to your organization's sign-in page.
- 1. Continue setting up the device.
- - When you choose **I own it**, you sign in with a Microsoft account. After setup is complete, you can [manually enroll HoloLens in device management](hololens-enroll-mdm.md#enroll-through-settings-app).
- 1. Enter your Microsoft account information.
- 2. Enter your password. If your Microsoft account requires [two-step verification (2FA)](https://blogs.technet.microsoft.com/microsoft_blog/2013/04/17/microsoft-account-gets-more-secure/), complete the verification process.
-
- 
-
-1. Select whether to enable speech on HoloLens 2, and whether to send diagnostic telemetry.
- 
-
-1. Select your telemetry level. If you can, please enable Full telemetry. This information really helps the HoloLens engineering team.
- 
-
-1. Learn how to use the start gesture on HoloLens 2.
- 
- 
-
-Congratulations! Setup is complete and you're ready to use HoloLens!
-
-## Next steps
-
-> [!div class="nextstepaction"]
-> [Get started with HoloLens 2](hololens2-basic-usage.md)
diff --git a/devices/hololens/images/01-magic-moment.png b/devices/hololens/images/01-magic-moment.png
deleted file mode 100644
index 0d55443b55..0000000000
Binary files a/devices/hololens/images/01-magic-moment.png and /dev/null differ
diff --git a/devices/hololens/images/02-00-magic-moment.png b/devices/hololens/images/02-00-magic-moment.png
deleted file mode 100644
index ae76fb70ea..0000000000
Binary files a/devices/hololens/images/02-00-magic-moment.png and /dev/null differ
diff --git a/devices/hololens/images/02-01-magic-moment-bird-intro.png b/devices/hololens/images/02-01-magic-moment-bird-intro.png
deleted file mode 100644
index ae76fb70ea..0000000000
Binary files a/devices/hololens/images/02-01-magic-moment-bird-intro.png and /dev/null differ
diff --git a/devices/hololens/images/02-02-bird-palm.png b/devices/hololens/images/02-02-bird-palm.png
deleted file mode 100644
index fda1f3dcdd..0000000000
Binary files a/devices/hololens/images/02-02-bird-palm.png and /dev/null differ
diff --git a/devices/hololens/images/02-03-bird-button.png b/devices/hololens/images/02-03-bird-button.png
deleted file mode 100644
index 749a1ab6fc..0000000000
Binary files a/devices/hololens/images/02-03-bird-button.png and /dev/null differ
diff --git a/devices/hololens/images/04-language.png b/devices/hololens/images/04-language.png
deleted file mode 100644
index 1106322c29..0000000000
Binary files a/devices/hololens/images/04-language.png and /dev/null differ
diff --git a/devices/hololens/images/05-region.png b/devices/hololens/images/05-region.png
deleted file mode 100644
index f350298813..0000000000
Binary files a/devices/hololens/images/05-region.png and /dev/null differ
diff --git a/devices/hololens/images/06-et-corners.png b/devices/hololens/images/06-et-corners.png
deleted file mode 100644
index af48472f60..0000000000
Binary files a/devices/hololens/images/06-et-corners.png and /dev/null differ
diff --git a/devices/hololens/images/07-et-adjust-for-your-eyes.png b/devices/hololens/images/07-et-adjust-for-your-eyes.png
deleted file mode 100644
index e127ba9a9d..0000000000
Binary files a/devices/hololens/images/07-et-adjust-for-your-eyes.png and /dev/null differ
diff --git a/devices/hololens/images/07-et-hold-head-still.png b/devices/hololens/images/07-et-hold-head-still.png
deleted file mode 100644
index a4952767bf..0000000000
Binary files a/devices/hololens/images/07-et-hold-head-still.png and /dev/null differ
diff --git a/devices/hololens/images/08-et-gems.png b/devices/hololens/images/08-et-gems.png
deleted file mode 100644
index 8eaba193f0..0000000000
Binary files a/devices/hololens/images/08-et-gems.png and /dev/null differ
diff --git a/devices/hololens/images/09-et-adjusting.png b/devices/hololens/images/09-et-adjusting.png
deleted file mode 100644
index 038dcab588..0000000000
Binary files a/devices/hololens/images/09-et-adjusting.png and /dev/null differ
diff --git a/devices/hololens/images/10-et-failure1.png b/devices/hololens/images/10-et-failure1.png
deleted file mode 100644
index 249abff7f6..0000000000
Binary files a/devices/hololens/images/10-et-failure1.png and /dev/null differ
diff --git a/devices/hololens/images/10-et-failure2.png b/devices/hololens/images/10-et-failure2.png
deleted file mode 100644
index f4b2f34334..0000000000
Binary files a/devices/hololens/images/10-et-failure2.png and /dev/null differ
diff --git a/devices/hololens/images/10-et-success.png b/devices/hololens/images/10-et-success.png
deleted file mode 100644
index c74c89056e..0000000000
Binary files a/devices/hololens/images/10-et-success.png and /dev/null differ
diff --git a/devices/hololens/images/11-network.png b/devices/hololens/images/11-network.png
deleted file mode 100644
index 1fc3884721..0000000000
Binary files a/devices/hololens/images/11-network.png and /dev/null differ
diff --git a/devices/hololens/images/12-agreement.png b/devices/hololens/images/12-agreement.png
deleted file mode 100644
index 96695c1888..0000000000
Binary files a/devices/hololens/images/12-agreement.png and /dev/null differ
diff --git a/devices/hololens/images/13-device-owner.png b/devices/hololens/images/13-device-owner.png
deleted file mode 100644
index fe66cd5386..0000000000
Binary files a/devices/hololens/images/13-device-owner.png and /dev/null differ
diff --git a/devices/hololens/images/14-sign-in-msa.png b/devices/hololens/images/14-sign-in-msa.png
deleted file mode 100644
index c0e3aa4d9e..0000000000
Binary files a/devices/hololens/images/14-sign-in-msa.png and /dev/null differ
diff --git a/devices/hololens/images/15-iris-enrollment.png b/devices/hololens/images/15-iris-enrollment.png
deleted file mode 100644
index 6bda392726..0000000000
Binary files a/devices/hololens/images/15-iris-enrollment.png and /dev/null differ
diff --git a/devices/hololens/images/16-iris-hold-head-still.png b/devices/hololens/images/16-iris-hold-head-still.png
deleted file mode 100644
index 09205015c0..0000000000
Binary files a/devices/hololens/images/16-iris-hold-head-still.png and /dev/null differ
diff --git a/devices/hololens/images/17-iris-dots.png b/devices/hololens/images/17-iris-dots.png
deleted file mode 100644
index 2ac6119b89..0000000000
Binary files a/devices/hololens/images/17-iris-dots.png and /dev/null differ
diff --git a/devices/hololens/images/18-iris-enrollment-done.png b/devices/hololens/images/18-iris-enrollment-done.png
deleted file mode 100644
index 6405ab8581..0000000000
Binary files a/devices/hololens/images/18-iris-enrollment-done.png and /dev/null differ
diff --git a/devices/hololens/images/19-pin-create.png b/devices/hololens/images/19-pin-create.png
deleted file mode 100644
index fd0c1ee5e8..0000000000
Binary files a/devices/hololens/images/19-pin-create.png and /dev/null differ
diff --git a/devices/hololens/images/20-pin-setup.png b/devices/hololens/images/20-pin-setup.png
deleted file mode 100644
index 752fc54e5c..0000000000
Binary files a/devices/hololens/images/20-pin-setup.png and /dev/null differ
diff --git a/devices/hololens/images/201608-enterprisemanagement-400px.png b/devices/hololens/images/201608-enterprisemanagement-400px.png
deleted file mode 100644
index 11c204f0f6..0000000000
Binary files a/devices/hololens/images/201608-enterprisemanagement-400px.png and /dev/null differ
diff --git a/devices/hololens/images/201608-kioskmode-400px.png b/devices/hololens/images/201608-kioskmode-400px.png
deleted file mode 100644
index 8d21453b8f..0000000000
Binary files a/devices/hololens/images/201608-kioskmode-400px.png and /dev/null differ
diff --git a/devices/hololens/images/20190322-DevicePortal.png b/devices/hololens/images/20190322-DevicePortal.png
deleted file mode 100644
index 7fdd2e34b3..0000000000
Binary files a/devices/hololens/images/20190322-DevicePortal.png and /dev/null differ
diff --git a/devices/hololens/images/22-do-more-with-voice.png b/devices/hololens/images/22-do-more-with-voice.png
deleted file mode 100644
index 2bf874c80d..0000000000
Binary files a/devices/hololens/images/22-do-more-with-voice.png and /dev/null differ
diff --git a/devices/hololens/images/23-do-more-with-voice-learn.png b/devices/hololens/images/23-do-more-with-voice-learn.png
deleted file mode 100644
index b805befc49..0000000000
Binary files a/devices/hololens/images/23-do-more-with-voice-learn.png and /dev/null differ
diff --git a/devices/hololens/images/24-telemetry.png b/devices/hololens/images/24-telemetry.png
deleted file mode 100644
index 004d1d5dff..0000000000
Binary files a/devices/hololens/images/24-telemetry.png and /dev/null differ
diff --git a/devices/hololens/images/25-telemetry-info.png b/devices/hololens/images/25-telemetry-info.png
deleted file mode 100644
index 4c4075a68f..0000000000
Binary files a/devices/hololens/images/25-telemetry-info.png and /dev/null differ
diff --git a/devices/hololens/images/26-01-startmenu-learning.png b/devices/hololens/images/26-01-startmenu-learning.png
deleted file mode 100644
index e24da1b854..0000000000
Binary files a/devices/hololens/images/26-01-startmenu-learning.png and /dev/null differ
diff --git a/devices/hololens/images/26-02-startmenu-learning.png b/devices/hololens/images/26-02-startmenu-learning.png
deleted file mode 100644
index 1a81a79178..0000000000
Binary files a/devices/hololens/images/26-02-startmenu-learning.png and /dev/null differ
diff --git a/devices/hololens/images/26-03-startmenu-learning.png b/devices/hololens/images/26-03-startmenu-learning.png
deleted file mode 100644
index 55d59d18f5..0000000000
Binary files a/devices/hololens/images/26-03-startmenu-learning.png and /dev/null differ
diff --git a/devices/hololens/images/26-04-startmenu-learning.png b/devices/hololens/images/26-04-startmenu-learning.png
deleted file mode 100644
index b7d62f5650..0000000000
Binary files a/devices/hololens/images/26-04-startmenu-learning.png and /dev/null differ
diff --git a/devices/hololens/images/B-Calibration-4-Gem.png b/devices/hololens/images/B-Calibration-4-Gem.png
deleted file mode 100644
index fbfd95cb32..0000000000
Binary files a/devices/hololens/images/B-Calibration-4-Gem.png and /dev/null differ
diff --git a/devices/hololens/images/C-Settings.Calibration.png b/devices/hololens/images/C-Settings.Calibration.png
deleted file mode 100644
index d27f3d754c..0000000000
Binary files a/devices/hololens/images/C-Settings.Calibration.png and /dev/null differ
diff --git a/devices/hololens/images/D-CheckThisOut-Prompt.png b/devices/hololens/images/D-CheckThisOut-Prompt.png
deleted file mode 100644
index a81a75a153..0000000000
Binary files a/devices/hololens/images/D-CheckThisOut-Prompt.png and /dev/null differ
diff --git a/devices/hololens/images/FitGuideSetep5.png b/devices/hololens/images/FitGuideSetep5.png
deleted file mode 100644
index 9529fe69b0..0000000000
Binary files a/devices/hololens/images/FitGuideSetep5.png and /dev/null differ
diff --git a/devices/hololens/images/FitGuideStep1.png b/devices/hololens/images/FitGuideStep1.png
deleted file mode 100644
index 846ef9fc0b..0000000000
Binary files a/devices/hololens/images/FitGuideStep1.png and /dev/null differ
diff --git a/devices/hololens/images/FitGuideStep2.png b/devices/hololens/images/FitGuideStep2.png
deleted file mode 100644
index 6ac59ff43b..0000000000
Binary files a/devices/hololens/images/FitGuideStep2.png and /dev/null differ
diff --git a/devices/hololens/images/FitGuideStep3.png b/devices/hololens/images/FitGuideStep3.png
deleted file mode 100644
index e255da8f15..0000000000
Binary files a/devices/hololens/images/FitGuideStep3.png and /dev/null differ
diff --git a/devices/hololens/images/FitGuideStep4.png b/devices/hololens/images/FitGuideStep4.png
deleted file mode 100644
index 77e99f3d55..0000000000
Binary files a/devices/hololens/images/FitGuideStep4.png and /dev/null differ
diff --git a/devices/hololens/images/HoloLens2_AppBarFollowing.gif b/devices/hololens/images/HoloLens2_AppBarFollowing.gif
deleted file mode 100644
index 84d7f2589e..0000000000
Binary files a/devices/hololens/images/HoloLens2_AppBarFollowing.gif and /dev/null differ
diff --git a/devices/hololens/images/HoloLens2_BoundingBox.gif b/devices/hololens/images/HoloLens2_BoundingBox.gif
deleted file mode 100644
index 451bcae997..0000000000
Binary files a/devices/hololens/images/HoloLens2_BoundingBox.gif and /dev/null differ
diff --git a/devices/hololens/images/HoloLens2_BoundingBox_Rotate.gif b/devices/hololens/images/HoloLens2_BoundingBox_Rotate.gif
deleted file mode 100644
index 43a764a954..0000000000
Binary files a/devices/hololens/images/HoloLens2_BoundingBox_Rotate.gif and /dev/null differ
diff --git a/devices/hololens/images/HoloLens2_Loader.gif b/devices/hololens/images/HoloLens2_Loader.gif
deleted file mode 100644
index 81d8232494..0000000000
Binary files a/devices/hololens/images/HoloLens2_Loader.gif and /dev/null differ
diff --git a/devices/hololens/images/HoloLens2_Proximity.gif b/devices/hololens/images/HoloLens2_Proximity.gif
deleted file mode 100644
index f39f326ea7..0000000000
Binary files a/devices/hololens/images/HoloLens2_Proximity.gif and /dev/null differ
diff --git a/devices/hololens/images/aad-kioskmode.PNG b/devices/hololens/images/aad-kioskmode.PNG
deleted file mode 100644
index c058f25241..0000000000
Binary files a/devices/hololens/images/aad-kioskmode.PNG and /dev/null differ
diff --git a/devices/hololens/images/about-encryption.png b/devices/hololens/images/about-encryption.png
deleted file mode 100644
index 348e493503..0000000000
Binary files a/devices/hololens/images/about-encryption.png and /dev/null differ
diff --git a/devices/hololens/images/account-management-details.png b/devices/hololens/images/account-management-details.png
deleted file mode 100644
index 20816830a4..0000000000
Binary files a/devices/hololens/images/account-management-details.png and /dev/null differ
diff --git a/devices/hololens/images/account-management.PNG b/devices/hololens/images/account-management.PNG
deleted file mode 100644
index da53cb74b8..0000000000
Binary files a/devices/hololens/images/account-management.PNG and /dev/null differ
diff --git a/devices/hololens/images/add-certificates-details.PNG b/devices/hololens/images/add-certificates-details.PNG
deleted file mode 100644
index 966a826a46..0000000000
Binary files a/devices/hololens/images/add-certificates-details.PNG and /dev/null differ
diff --git a/devices/hololens/images/add-certificates.PNG b/devices/hololens/images/add-certificates.PNG
deleted file mode 100644
index 7a16dffd26..0000000000
Binary files a/devices/hololens/images/add-certificates.PNG and /dev/null differ
diff --git a/devices/hololens/images/addnewfeedback-500px.jpg b/devices/hololens/images/addnewfeedback-500px.jpg
deleted file mode 100644
index 8948dd2dae..0000000000
Binary files a/devices/hololens/images/addnewfeedback-500px.jpg and /dev/null differ
diff --git a/devices/hololens/images/adk-install.png b/devices/hololens/images/adk-install.png
deleted file mode 100644
index c087d3bae5..0000000000
Binary files a/devices/hololens/images/adk-install.png and /dev/null differ
diff --git a/devices/hololens/images/apps.png b/devices/hololens/images/apps.png
deleted file mode 100644
index 4e00aa96fc..0000000000
Binary files a/devices/hololens/images/apps.png and /dev/null differ
diff --git a/devices/hololens/images/azure-ad-image.PNG b/devices/hololens/images/azure-ad-image.PNG
deleted file mode 100644
index e0215265f6..0000000000
Binary files a/devices/hololens/images/azure-ad-image.PNG and /dev/null differ
diff --git a/devices/hololens/images/backicon.png b/devices/hololens/images/backicon.png
deleted file mode 100644
index 3007e448b1..0000000000
Binary files a/devices/hololens/images/backicon.png and /dev/null differ
diff --git a/devices/hololens/images/calibration-livecube-200px.png b/devices/hololens/images/calibration-livecube-200px.png
deleted file mode 100644
index 44b0142e40..0000000000
Binary files a/devices/hololens/images/calibration-livecube-200px.png and /dev/null differ
diff --git a/devices/hololens/images/calibration-settings-500px.jpg b/devices/hololens/images/calibration-settings-500px.jpg
deleted file mode 100644
index 0419f0307f..0000000000
Binary files a/devices/hololens/images/calibration-settings-500px.jpg and /dev/null differ
diff --git a/devices/hololens/images/calibration-shell.png b/devices/hololens/images/calibration-shell.png
deleted file mode 100644
index f833452cc5..0000000000
Binary files a/devices/hololens/images/calibration-shell.png and /dev/null differ
diff --git a/devices/hololens/images/check_blu.png b/devices/hololens/images/check_blu.png
deleted file mode 100644
index d5c703760f..0000000000
Binary files a/devices/hololens/images/check_blu.png and /dev/null differ
diff --git a/devices/hololens/images/check_grn.png b/devices/hololens/images/check_grn.png
deleted file mode 100644
index f9f04cd6bd..0000000000
Binary files a/devices/hololens/images/check_grn.png and /dev/null differ
diff --git a/devices/hololens/images/checklistbox.gif b/devices/hololens/images/checklistbox.gif
deleted file mode 100644
index cbcf4a4f11..0000000000
Binary files a/devices/hololens/images/checklistbox.gif and /dev/null differ
diff --git a/devices/hololens/images/checklistdone.png b/devices/hololens/images/checklistdone.png
deleted file mode 100644
index 7e53f74d0e..0000000000
Binary files a/devices/hololens/images/checklistdone.png and /dev/null differ
diff --git a/devices/hololens/images/checkmark.png b/devices/hololens/images/checkmark.png
deleted file mode 100644
index f9f04cd6bd..0000000000
Binary files a/devices/hololens/images/checkmark.png and /dev/null differ
diff --git a/devices/hololens/images/cortana-on-hololens.png b/devices/hololens/images/cortana-on-hololens.png
deleted file mode 100644
index 6205d3d2fd..0000000000
Binary files a/devices/hololens/images/cortana-on-hololens.png and /dev/null differ
diff --git a/devices/hololens/images/crossmark.png b/devices/hololens/images/crossmark.png
deleted file mode 100644
index 69432ff71c..0000000000
Binary files a/devices/hololens/images/crossmark.png and /dev/null differ
diff --git a/devices/hololens/images/developer-setup-details.png b/devices/hololens/images/developer-setup-details.png
deleted file mode 100644
index d445bf5759..0000000000
Binary files a/devices/hololens/images/developer-setup-details.png and /dev/null differ
diff --git a/devices/hololens/images/developer-setup.png b/devices/hololens/images/developer-setup.png
deleted file mode 100644
index a7e49873b0..0000000000
Binary files a/devices/hololens/images/developer-setup.png and /dev/null differ
diff --git a/devices/hololens/images/device-encryption.PNG b/devices/hololens/images/device-encryption.PNG
deleted file mode 100644
index 651429dfe0..0000000000
Binary files a/devices/hololens/images/device-encryption.PNG and /dev/null differ
diff --git a/devices/hololens/images/deviceportal-appmanager.jpg b/devices/hololens/images/deviceportal-appmanager.jpg
deleted file mode 100644
index 68576fcfc7..0000000000
Binary files a/devices/hololens/images/deviceportal-appmanager.jpg and /dev/null differ
diff --git a/devices/hololens/images/displays-400px.jpg b/devices/hololens/images/displays-400px.jpg
deleted file mode 100644
index 0ed5558bdc..0000000000
Binary files a/devices/hololens/images/displays-400px.jpg and /dev/null differ
diff --git a/devices/hololens/images/doneicon.png b/devices/hololens/images/doneicon.png
deleted file mode 100644
index d80389f35b..0000000000
Binary files a/devices/hololens/images/doneicon.png and /dev/null differ
diff --git a/devices/hololens/images/encrypt-assign.png b/devices/hololens/images/encrypt-assign.png
deleted file mode 100644
index f5b0c85a3c..0000000000
Binary files a/devices/hololens/images/encrypt-assign.png and /dev/null differ
diff --git a/devices/hololens/images/encrypt-create-profile.png b/devices/hololens/images/encrypt-create-profile.png
deleted file mode 100644
index b0f06ef40f..0000000000
Binary files a/devices/hololens/images/encrypt-create-profile.png and /dev/null differ
diff --git a/devices/hololens/images/encrypt-custom.png b/devices/hololens/images/encrypt-custom.png
deleted file mode 100644
index b3635e9ee4..0000000000
Binary files a/devices/hololens/images/encrypt-custom.png and /dev/null differ
diff --git a/devices/hololens/images/encrypt-oma-uri.png b/devices/hololens/images/encrypt-oma-uri.png
deleted file mode 100644
index e2754b7db4..0000000000
Binary files a/devices/hololens/images/encrypt-oma-uri.png and /dev/null differ
diff --git a/devices/hololens/images/feedback1-600px.png b/devices/hololens/images/feedback1-600px.png
deleted file mode 100644
index ba7cec37da..0000000000
Binary files a/devices/hololens/images/feedback1-600px.png and /dev/null differ
diff --git a/devices/hololens/images/feedback2-600px.png b/devices/hololens/images/feedback2-600px.png
deleted file mode 100644
index 89d44622a6..0000000000
Binary files a/devices/hololens/images/feedback2-600px.png and /dev/null differ
diff --git a/devices/hololens/images/feedback3-600px.png b/devices/hololens/images/feedback3-600px.png
deleted file mode 100644
index 0431687b55..0000000000
Binary files a/devices/hololens/images/feedback3-600px.png and /dev/null differ
diff --git a/devices/hololens/images/feedback4-600px.png b/devices/hololens/images/feedback4-600px.png
deleted file mode 100644
index 35594f2ca8..0000000000
Binary files a/devices/hololens/images/feedback4-600px.png and /dev/null differ
diff --git a/devices/hololens/images/feedback5-600px.png b/devices/hololens/images/feedback5-600px.png
deleted file mode 100644
index 967987d6ae..0000000000
Binary files a/devices/hololens/images/feedback5-600px.png and /dev/null differ
diff --git a/devices/hololens/images/feedback6-600px.png b/devices/hololens/images/feedback6-600px.png
deleted file mode 100644
index 431a4da9da..0000000000
Binary files a/devices/hololens/images/feedback6-600px.png and /dev/null differ
diff --git a/devices/hololens/images/finish-details.png b/devices/hololens/images/finish-details.png
deleted file mode 100644
index ff3f53e5c8..0000000000
Binary files a/devices/hololens/images/finish-details.png and /dev/null differ
diff --git a/devices/hololens/images/finish.PNG b/devices/hololens/images/finish.PNG
deleted file mode 100644
index 975caba764..0000000000
Binary files a/devices/hololens/images/finish.PNG and /dev/null differ
diff --git a/devices/hololens/images/five.png b/devices/hololens/images/five.png
deleted file mode 100644
index 961f0e15b7..0000000000
Binary files a/devices/hololens/images/five.png and /dev/null differ
diff --git a/devices/hololens/images/four.png b/devices/hololens/images/four.png
deleted file mode 100644
index 0fef213b37..0000000000
Binary files a/devices/hololens/images/four.png and /dev/null differ
diff --git a/devices/hololens/images/hololens-2-air-tap.gif b/devices/hololens/images/hololens-2-air-tap.gif
deleted file mode 100644
index 9139718cdb..0000000000
Binary files a/devices/hololens/images/hololens-2-air-tap.gif and /dev/null differ
diff --git a/devices/hololens/images/hololens-2-button-sleep.png b/devices/hololens/images/hololens-2-button-sleep.png
deleted file mode 100644
index 29f75da34f..0000000000
Binary files a/devices/hololens/images/hololens-2-button-sleep.png and /dev/null differ
diff --git a/devices/hololens/images/hololens-2-button-turn-off.png b/devices/hololens/images/hololens-2-button-turn-off.png
deleted file mode 100644
index 8e3f4a2c72..0000000000
Binary files a/devices/hololens/images/hololens-2-button-turn-off.png and /dev/null differ
diff --git a/devices/hololens/images/hololens-2-button-turn-on.png b/devices/hololens/images/hololens-2-button-turn-on.png
deleted file mode 100644
index 25ce3fcc58..0000000000
Binary files a/devices/hololens/images/hololens-2-button-turn-on.png and /dev/null differ
diff --git a/devices/hololens/images/hololens-2-button-wake.png b/devices/hololens/images/hololens-2-button-wake.png
deleted file mode 100644
index 135b1e3a04..0000000000
Binary files a/devices/hololens/images/hololens-2-button-wake.png and /dev/null differ
diff --git a/devices/hololens/images/hololens-2-gesture-frame.png b/devices/hololens/images/hololens-2-gesture-frame.png
deleted file mode 100644
index cc1a9f667d..0000000000
Binary files a/devices/hololens/images/hololens-2-gesture-frame.png and /dev/null differ
diff --git a/devices/hololens/images/hololens-2-screenshot-with-callouts.png b/devices/hololens/images/hololens-2-screenshot-with-callouts.png
deleted file mode 100644
index 769310e749..0000000000
Binary files a/devices/hololens/images/hololens-2-screenshot-with-callouts.png and /dev/null differ
diff --git a/devices/hololens/images/hololens-2-start-alternative.png b/devices/hololens/images/hololens-2-start-alternative.png
deleted file mode 100644
index 763cd8600e..0000000000
Binary files a/devices/hololens/images/hololens-2-start-alternative.png and /dev/null differ
diff --git a/devices/hololens/images/hololens-2-start-gesture.png b/devices/hololens/images/hololens-2-start-gesture.png
deleted file mode 100644
index 109c6235bb..0000000000
Binary files a/devices/hololens/images/hololens-2-start-gesture.png and /dev/null differ
diff --git a/devices/hololens/images/hololens-air-tap.gif b/devices/hololens/images/hololens-air-tap.gif
deleted file mode 100644
index 9139718cdb..0000000000
Binary files a/devices/hololens/images/hololens-air-tap.gif and /dev/null differ
diff --git a/devices/hololens/images/hololens-ap-devices-assignments.png b/devices/hololens/images/hololens-ap-devices-assignments.png
deleted file mode 100644
index f99eaa367d..0000000000
Binary files a/devices/hololens/images/hololens-ap-devices-assignments.png and /dev/null differ
diff --git a/devices/hololens/images/hololens-ap-devices-sync.png b/devices/hololens/images/hololens-ap-devices-sync.png
deleted file mode 100644
index fe970f7983..0000000000
Binary files a/devices/hololens/images/hololens-ap-devices-sync.png and /dev/null differ
diff --git a/devices/hololens/images/hololens-ap-enrollment-profiles.png b/devices/hololens/images/hololens-ap-enrollment-profiles.png
deleted file mode 100644
index 1e3e8dfaa4..0000000000
Binary files a/devices/hololens/images/hololens-ap-enrollment-profiles.png and /dev/null differ
diff --git a/devices/hololens/images/hololens-ap-hash-import.png b/devices/hololens/images/hololens-ap-hash-import.png
deleted file mode 100644
index 078e73d78c..0000000000
Binary files a/devices/hololens/images/hololens-ap-hash-import.png and /dev/null differ
diff --git a/devices/hololens/images/hololens-ap-intro.png b/devices/hololens/images/hololens-ap-intro.png
deleted file mode 100644
index 8095114167..0000000000
Binary files a/devices/hololens/images/hololens-ap-intro.png and /dev/null differ
diff --git a/devices/hololens/images/hololens-ap-profile-assign-devicegroup.png b/devices/hololens/images/hololens-ap-profile-assign-devicegroup.png
deleted file mode 100644
index 9e6dc92a3c..0000000000
Binary files a/devices/hololens/images/hololens-ap-profile-assign-devicegroup.png and /dev/null differ
diff --git a/devices/hololens/images/hololens-ap-profile-name.png b/devices/hololens/images/hololens-ap-profile-name.png
deleted file mode 100644
index a427b437b8..0000000000
Binary files a/devices/hololens/images/hololens-ap-profile-name.png and /dev/null differ
diff --git a/devices/hololens/images/hololens-ap-profile-oobe.png b/devices/hololens/images/hololens-ap-profile-oobe.png
deleted file mode 100644
index e14226d7ad..0000000000
Binary files a/devices/hololens/images/hololens-ap-profile-oobe.png and /dev/null differ
diff --git a/devices/hololens/images/hololens-ap-profile-settings-oma.png b/devices/hololens/images/hololens-ap-profile-settings-oma.png
deleted file mode 100644
index 7528f55292..0000000000
Binary files a/devices/hololens/images/hololens-ap-profile-settings-oma.png and /dev/null differ
diff --git a/devices/hololens/images/hololens-ap-profile-settings.png b/devices/hololens/images/hololens-ap-profile-settings.png
deleted file mode 100644
index 5753814e1b..0000000000
Binary files a/devices/hololens/images/hololens-ap-profile-settings.png and /dev/null differ
diff --git a/devices/hololens/images/hololens-ap-profile-summ.png b/devices/hololens/images/hololens-ap-profile-summ.png
deleted file mode 100644
index 4fb955bbdf..0000000000
Binary files a/devices/hololens/images/hololens-ap-profile-summ.png and /dev/null differ
diff --git a/devices/hololens/images/hololens-ap-qrcode.png b/devices/hololens/images/hololens-ap-qrcode.png
deleted file mode 100644
index c5296e3e91..0000000000
Binary files a/devices/hololens/images/hololens-ap-qrcode.png and /dev/null differ
diff --git a/devices/hololens/images/hololens-ap-uex-1.png b/devices/hololens/images/hololens-ap-uex-1.png
deleted file mode 100644
index f89faa366a..0000000000
Binary files a/devices/hololens/images/hololens-ap-uex-1.png and /dev/null differ
diff --git a/devices/hololens/images/hololens-ap-uex-2.png b/devices/hololens/images/hololens-ap-uex-2.png
deleted file mode 100644
index 5bf1beb3f0..0000000000
Binary files a/devices/hololens/images/hololens-ap-uex-2.png and /dev/null differ
diff --git a/devices/hololens/images/hololens-ap-uex-3.png b/devices/hololens/images/hololens-ap-uex-3.png
deleted file mode 100644
index 59a7362269..0000000000
Binary files a/devices/hololens/images/hololens-ap-uex-3.png and /dev/null differ
diff --git a/devices/hololens/images/hololens-ap-uex-4.png b/devices/hololens/images/hololens-ap-uex-4.png
deleted file mode 100644
index f17557b5c4..0000000000
Binary files a/devices/hololens/images/hololens-ap-uex-4.png and /dev/null differ
diff --git a/devices/hololens/images/hololens-ap-uex-5.png b/devices/hololens/images/hololens-ap-uex-5.png
deleted file mode 100644
index 0bd23da48e..0000000000
Binary files a/devices/hololens/images/hololens-ap-uex-5.png and /dev/null differ
diff --git a/devices/hololens/images/hololens-bloom.gif b/devices/hololens/images/hololens-bloom.gif
deleted file mode 100644
index db7d8378e5..0000000000
Binary files a/devices/hololens/images/hololens-bloom.gif and /dev/null differ
diff --git a/devices/hololens/images/hololens-box-contents.png b/devices/hololens/images/hololens-box-contents.png
deleted file mode 100644
index 51b4b5e163..0000000000
Binary files a/devices/hololens/images/hololens-box-contents.png and /dev/null differ
diff --git a/devices/hololens/images/hololens-buttons.jpg b/devices/hololens/images/hololens-buttons.jpg
deleted file mode 100644
index 868487b0bf..0000000000
Binary files a/devices/hololens/images/hololens-buttons.jpg and /dev/null differ
diff --git a/devices/hololens/images/hololens-charging.png b/devices/hololens/images/hololens-charging.png
deleted file mode 100644
index a5dd4d7dcd..0000000000
Binary files a/devices/hololens/images/hololens-charging.png and /dev/null differ
diff --git a/devices/hololens/images/hololens-cleaning-visor.png b/devices/hololens/images/hololens-cleaning-visor.png
deleted file mode 100644
index 68f990d43b..0000000000
Binary files a/devices/hololens/images/hololens-cleaning-visor.png and /dev/null differ
diff --git a/devices/hololens/images/hololens-clicker-500px.jpg b/devices/hololens/images/hololens-clicker-500px.jpg
deleted file mode 100644
index 4dd7d954f4..0000000000
Binary files a/devices/hololens/images/hololens-clicker-500px.jpg and /dev/null differ
diff --git a/devices/hololens/images/hololens-frame.png b/devices/hololens/images/hololens-frame.png
deleted file mode 100644
index 5789f1b8c8..0000000000
Binary files a/devices/hololens/images/hololens-frame.png and /dev/null differ
diff --git a/devices/hololens/images/hololens-gaze.png b/devices/hololens/images/hololens-gaze.png
deleted file mode 100644
index d21ffef0b2..0000000000
Binary files a/devices/hololens/images/hololens-gaze.png and /dev/null differ
diff --git a/devices/hololens/images/hololens-lights.png b/devices/hololens/images/hololens-lights.png
deleted file mode 100644
index f3a19b84a3..0000000000
Binary files a/devices/hololens/images/hololens-lights.png and /dev/null differ
diff --git a/devices/hololens/images/hololens-power.png b/devices/hololens/images/hololens-power.png
deleted file mode 100644
index 80c3e7c215..0000000000
Binary files a/devices/hololens/images/hololens-power.png and /dev/null differ
diff --git a/devices/hololens/images/hololens-updates-timeline.png b/devices/hololens/images/hololens-updates-timeline.png
deleted file mode 100644
index 4b1e986948..0000000000
Binary files a/devices/hololens/images/hololens-updates-timeline.png and /dev/null differ
diff --git a/devices/hololens/images/hololens-vector-white.png b/devices/hololens/images/hololens-vector-white.png
deleted file mode 100644
index 583a307449..0000000000
Binary files a/devices/hololens/images/hololens-vector-white.png and /dev/null differ
diff --git a/devices/hololens/images/hololens.png b/devices/hololens/images/hololens.png
deleted file mode 100644
index ce54ae4281..0000000000
Binary files a/devices/hololens/images/hololens.png and /dev/null differ
diff --git a/devices/hololens/images/hololens2-exploded-large.png b/devices/hololens/images/hololens2-exploded-large.png
deleted file mode 100644
index fc639a0f62..0000000000
Binary files a/devices/hololens/images/hololens2-exploded-large.png and /dev/null differ
diff --git a/devices/hololens/images/hololens2-exploded-medium.png b/devices/hololens/images/hololens2-exploded-medium.png
deleted file mode 100644
index 3e1fbea7de..0000000000
Binary files a/devices/hololens/images/hololens2-exploded-medium.png and /dev/null differ
diff --git a/devices/hololens/images/hololens2-fit.png b/devices/hololens/images/hololens2-fit.png
deleted file mode 100644
index dacaf4cbd7..0000000000
Binary files a/devices/hololens/images/hololens2-fit.png and /dev/null differ
diff --git a/devices/hololens/images/hololens2-headstrap.png b/devices/hololens/images/hololens2-headstrap.png
deleted file mode 100644
index 805637214b..0000000000
Binary files a/devices/hololens/images/hololens2-headstrap.png and /dev/null differ
diff --git a/devices/hololens/images/hololens2-lift-visor.png b/devices/hololens/images/hololens2-lift-visor.png
deleted file mode 100644
index 4d83f2c730..0000000000
Binary files a/devices/hololens/images/hololens2-lift-visor.png and /dev/null differ
diff --git a/devices/hololens/images/hololens2-remove-browpad.png b/devices/hololens/images/hololens2-remove-browpad.png
deleted file mode 100644
index 619f14e4fd..0000000000
Binary files a/devices/hololens/images/hololens2-remove-browpad.png and /dev/null differ
diff --git a/devices/hololens/images/hololens2-side-render-medium.png b/devices/hololens/images/hololens2-side-render-medium.png
deleted file mode 100644
index d4650c05e2..0000000000
Binary files a/devices/hololens/images/hololens2-side-render-medium.png and /dev/null differ
diff --git a/devices/hololens/images/hololens2-side-render-small.png b/devices/hololens/images/hololens2-side-render-small.png
deleted file mode 100644
index a1a612e05a..0000000000
Binary files a/devices/hololens/images/hololens2-side-render-small.png and /dev/null differ
diff --git a/devices/hololens/images/hololens2-side-render-xs.png b/devices/hololens/images/hololens2-side-render-xs.png
deleted file mode 100644
index 08d5f966cd..0000000000
Binary files a/devices/hololens/images/hololens2-side-render-xs.png and /dev/null differ
diff --git a/devices/hololens/images/hololens2-side-render.png b/devices/hololens/images/hololens2-side-render.png
deleted file mode 100644
index 143fb8fc50..0000000000
Binary files a/devices/hololens/images/hololens2-side-render.png and /dev/null differ
diff --git a/devices/hololens/images/icd-create-options-1703.PNG b/devices/hololens/images/icd-create-options-1703.PNG
deleted file mode 100644
index 007e740683..0000000000
Binary files a/devices/hololens/images/icd-create-options-1703.PNG and /dev/null differ
diff --git a/devices/hololens/images/icd-export-menu.png b/devices/hololens/images/icd-export-menu.png
deleted file mode 100644
index 20bd5258eb..0000000000
Binary files a/devices/hololens/images/icd-export-menu.png and /dev/null differ
diff --git a/devices/hololens/images/icd-install.PNG b/devices/hololens/images/icd-install.PNG
deleted file mode 100644
index a0c80683ff..0000000000
Binary files a/devices/hololens/images/icd-install.PNG and /dev/null differ
diff --git a/devices/hololens/images/icd-settings.png b/devices/hololens/images/icd-settings.png
deleted file mode 100644
index 111b7f38c7..0000000000
Binary files a/devices/hololens/images/icd-settings.png and /dev/null differ
diff --git a/devices/hololens/images/icd-simple-edit.png b/devices/hololens/images/icd-simple-edit.png
deleted file mode 100644
index 421159ac17..0000000000
Binary files a/devices/hololens/images/icd-simple-edit.png and /dev/null differ
diff --git a/devices/hololens/images/icd1.PNG b/devices/hololens/images/icd1.PNG
deleted file mode 100644
index 25f905d4fe..0000000000
Binary files a/devices/hololens/images/icd1.PNG and /dev/null differ
diff --git a/devices/hololens/images/intune1.PNG b/devices/hololens/images/intune1.PNG
deleted file mode 100644
index c87c58d36a..0000000000
Binary files a/devices/hololens/images/intune1.PNG and /dev/null differ
diff --git a/devices/hololens/images/intune2.PNG b/devices/hololens/images/intune2.PNG
deleted file mode 100644
index 61ca386c3c..0000000000
Binary files a/devices/hololens/images/intune2.PNG and /dev/null differ
diff --git a/devices/hololens/images/intune3.png b/devices/hololens/images/intune3.png
deleted file mode 100644
index 39a812a1a7..0000000000
Binary files a/devices/hololens/images/intune3.png and /dev/null differ
diff --git a/devices/hololens/images/ipd-finger-alignment-300px.jpg b/devices/hololens/images/ipd-finger-alignment-300px.jpg
deleted file mode 100644
index 7a4c929867..0000000000
Binary files a/devices/hololens/images/ipd-finger-alignment-300px.jpg and /dev/null differ
diff --git a/devices/hololens/images/keyboard.png b/devices/hololens/images/keyboard.png
deleted file mode 100644
index 6962567b83..0000000000
Binary files a/devices/hololens/images/keyboard.png and /dev/null differ
diff --git a/devices/hololens/images/kiosk.png b/devices/hololens/images/kiosk.png
deleted file mode 100644
index 9cc771c779..0000000000
Binary files a/devices/hololens/images/kiosk.png and /dev/null differ
diff --git a/devices/hololens/images/launchicon.png b/devices/hololens/images/launchicon.png
deleted file mode 100644
index d469c68a2c..0000000000
Binary files a/devices/hololens/images/launchicon.png and /dev/null differ
diff --git a/devices/hololens/images/mdm-enrollment-error.png b/devices/hololens/images/mdm-enrollment-error.png
deleted file mode 100644
index 77b695d1cf..0000000000
Binary files a/devices/hololens/images/mdm-enrollment-error.png and /dev/null differ
diff --git a/devices/hololens/images/minimenu.png b/devices/hololens/images/minimenu.png
deleted file mode 100644
index 7aa0018011..0000000000
Binary files a/devices/hololens/images/minimenu.png and /dev/null differ
diff --git a/devices/hololens/images/motherboard-400px.jpg b/devices/hololens/images/motherboard-400px.jpg
deleted file mode 100644
index 5a2a085477..0000000000
Binary files a/devices/hololens/images/motherboard-400px.jpg and /dev/null differ
diff --git a/devices/hololens/images/multiappassignedaccesssettings.png b/devices/hololens/images/multiappassignedaccesssettings.png
deleted file mode 100644
index 86e2e0a451..0000000000
Binary files a/devices/hololens/images/multiappassignedaccesssettings.png and /dev/null differ
diff --git a/devices/hololens/images/one.png b/devices/hololens/images/one.png
deleted file mode 100644
index 7766e7d470..0000000000
Binary files a/devices/hololens/images/one.png and /dev/null differ
diff --git a/devices/hololens/images/provision-hololens-devices.png b/devices/hololens/images/provision-hololens-devices.png
deleted file mode 100644
index c5ece7102f..0000000000
Binary files a/devices/hololens/images/provision-hololens-devices.png and /dev/null differ
diff --git a/devices/hololens/images/recover-clicker-1.png b/devices/hololens/images/recover-clicker-1.png
deleted file mode 100644
index ad54e6ee09..0000000000
Binary files a/devices/hololens/images/recover-clicker-1.png and /dev/null differ
diff --git a/devices/hololens/images/recover-clicker-2.png b/devices/hololens/images/recover-clicker-2.png
deleted file mode 100644
index d7a9d6fd0d..0000000000
Binary files a/devices/hololens/images/recover-clicker-2.png and /dev/null differ
diff --git a/devices/hololens/images/searchfeedback-500px.jpg b/devices/hololens/images/searchfeedback-500px.jpg
deleted file mode 100644
index 952e29a6ec..0000000000
Binary files a/devices/hololens/images/searchfeedback-500px.jpg and /dev/null differ
diff --git a/devices/hololens/images/see-through-400px.jpg b/devices/hololens/images/see-through-400px.jpg
deleted file mode 100644
index d9fba1c9e0..0000000000
Binary files a/devices/hololens/images/see-through-400px.jpg and /dev/null differ
diff --git a/devices/hololens/images/sensor-bar-400px.jpg b/devices/hololens/images/sensor-bar-400px.jpg
deleted file mode 100644
index bf0b8f7f21..0000000000
Binary files a/devices/hololens/images/sensor-bar-400px.jpg and /dev/null differ
diff --git a/devices/hololens/images/set-up-device-details.PNG b/devices/hololens/images/set-up-device-details.PNG
deleted file mode 100644
index 7325e06e86..0000000000
Binary files a/devices/hololens/images/set-up-device-details.PNG and /dev/null differ
diff --git a/devices/hololens/images/set-up-device.PNG b/devices/hololens/images/set-up-device.PNG
deleted file mode 100644
index 577117a26a..0000000000
Binary files a/devices/hololens/images/set-up-device.PNG and /dev/null differ
diff --git a/devices/hololens/images/set-up-network-details-desktop.PNG b/devices/hololens/images/set-up-network-details-desktop.PNG
deleted file mode 100644
index 83911ccbd0..0000000000
Binary files a/devices/hololens/images/set-up-network-details-desktop.PNG and /dev/null differ
diff --git a/devices/hololens/images/set-up-network.PNG b/devices/hololens/images/set-up-network.PNG
deleted file mode 100644
index 19fd3ff7bb..0000000000
Binary files a/devices/hololens/images/set-up-network.PNG and /dev/null differ
diff --git a/devices/hololens/images/seven.png b/devices/hololens/images/seven.png
deleted file mode 100644
index 285a92df0b..0000000000
Binary files a/devices/hololens/images/seven.png and /dev/null differ
diff --git a/devices/hololens/images/six.png b/devices/hololens/images/six.png
deleted file mode 100644
index e8906332ec..0000000000
Binary files a/devices/hololens/images/six.png and /dev/null differ
diff --git a/devices/hololens/images/startmenu.jpg b/devices/hololens/images/startmenu.jpg
deleted file mode 100644
index b685db51ee..0000000000
Binary files a/devices/hololens/images/startmenu.jpg and /dev/null differ
diff --git a/devices/hololens/images/three.png b/devices/hololens/images/three.png
deleted file mode 100644
index 887fa270d7..0000000000
Binary files a/devices/hololens/images/three.png and /dev/null differ
diff --git a/devices/hololens/images/two.png b/devices/hololens/images/two.png
deleted file mode 100644
index b8c2d52eaf..0000000000
Binary files a/devices/hololens/images/two.png and /dev/null differ
diff --git a/devices/hololens/images/upvotefeedback-500px.jpg b/devices/hololens/images/upvotefeedback-500px.jpg
deleted file mode 100644
index f1eda89efa..0000000000
Binary files a/devices/hololens/images/upvotefeedback-500px.jpg and /dev/null differ
diff --git a/devices/hololens/images/use-hololens-clicker-1.png b/devices/hololens/images/use-hololens-clicker-1.png
deleted file mode 100644
index ad54e6ee09..0000000000
Binary files a/devices/hololens/images/use-hololens-clicker-1.png and /dev/null differ
diff --git a/devices/hololens/images/use-hololens-clicker-2.png b/devices/hololens/images/use-hololens-clicker-2.png
deleted file mode 100644
index d7a9d6fd0d..0000000000
Binary files a/devices/hololens/images/use-hololens-clicker-2.png and /dev/null differ
diff --git a/devices/hololens/images/uwp-dependencies.PNG b/devices/hololens/images/uwp-dependencies.PNG
deleted file mode 100644
index 4e2563169f..0000000000
Binary files a/devices/hololens/images/uwp-dependencies.PNG and /dev/null differ
diff --git a/devices/hololens/images/uwp-license.PNG b/devices/hololens/images/uwp-license.PNG
deleted file mode 100644
index ccb5cf7cf4..0000000000
Binary files a/devices/hololens/images/uwp-license.PNG and /dev/null differ
diff --git a/devices/hololens/images/vs2015-remotedeployment.jpg b/devices/hololens/images/vs2015-remotedeployment.jpg
deleted file mode 100644
index a7d6b43dc3..0000000000
Binary files a/devices/hololens/images/vs2015-remotedeployment.jpg and /dev/null differ
diff --git a/devices/hololens/images/wifi-hololens-600px.jpg b/devices/hololens/images/wifi-hololens-600px.jpg
deleted file mode 100644
index eb6930a29f..0000000000
Binary files a/devices/hololens/images/wifi-hololens-600px.jpg and /dev/null differ
diff --git a/devices/hololens/images/wifi-hololens-hwdetails.jpg b/devices/hololens/images/wifi-hololens-hwdetails.jpg
deleted file mode 100644
index e4b45047cf..0000000000
Binary files a/devices/hololens/images/wifi-hololens-hwdetails.jpg and /dev/null differ
diff --git a/devices/hololens/images/windows-device-portal-home-page.png b/devices/hololens/images/windows-device-portal-home-page.png
deleted file mode 100644
index 55e4b0eaad..0000000000
Binary files a/devices/hololens/images/windows-device-portal-home-page.png and /dev/null differ
diff --git a/devices/hololens/images/wizard-steps.png b/devices/hololens/images/wizard-steps.png
deleted file mode 100644
index d97bae9a05..0000000000
Binary files a/devices/hololens/images/wizard-steps.png and /dev/null differ
diff --git a/devices/hololens/images/wsfb-private.png b/devices/hololens/images/wsfb-private.png
deleted file mode 100644
index 35ce83829b..0000000000
Binary files a/devices/hololens/images/wsfb-private.png and /dev/null differ
diff --git a/devices/hololens/index.md b/devices/hololens/index.md
deleted file mode 100644
index 47862d7138..0000000000
--- a/devices/hololens/index.md
+++ /dev/null
@@ -1,62 +0,0 @@
----
-title: Microsoft HoloLens
-description: Landing page for Microsoft HoloLens.
-ms.prod: hololens
-ms.sitesec: library
-ms.assetid: 0947f5b3-8f0f-42f0-aa27-6d2cad51d040
-author: scooley
-ms.author: scooley
-ms.topic: article
-ms.localizationpriority: medium
-ms.date: 10/14/2019
-audience: ITPro
-ms.custom:
-- CI 111456
-- CSSTroubleshooting
-appliesto:
-- HoloLens (1st gen)
-- HoloLens 2
-
----
-
-# Microsoft HoloLens
-
-
-
-
Microsoft HoloLens is the first fully self-contained holographic computer running Windows 10.
-
-
Now, with the introduction of HoloLens 2, every device provides commercial ready management enhanced by the reliability, security, and scalability of cloud and AI services from Microsoft.
-
-## Guides in this section
-
-| Guide | Description |
-| --- | --- |
-| [Get started with HoloLens 2](hololens2-setup.md) | Set up HoloLens 2 for the first time. |
-| [Get started with HoloLens (1st gen)](hololens1-setup.md) | Set up HoloLens (1st gen) for the first time. |
-| [Get started with HoloLens in a commercial or classroom environment](hololens-requirements.md) | Plan for a multi-device HoloLens deployment and create a strategy for ongoing device management.This section is tailored to IT professionals managing devices with existing device management infrastructure. |
-
-## Quick reference by topic
-
-| Topic | Description |
-| --- | --- |
-| [What's new in HoloLens](hololens-whats-new.md) | Discover new features in the latest updates via HoloLens release notes. |
-| [Install and manage applications on HoloLens](hololens-install-apps.md) | Install and manage important applications on HoloLens at scale. |
-| [HoloLens update management](hololens-updates.md) | Use mobile device management (MDM) policies to configure settings for updates. |
-| [HoloLens user management](hololens-multiple-users.md) | Multiple users can share a HoloLens device by using their Azure Active Directory accounts. |
-| [HoloLens application access management](hololens-kiosk.md) | Manage application access for different user groups. |
-| [Recover and troubleshoot HoloLens issues](https://support.microsoft.com/products/hololens) | Learn how to gather logs from HoloLens, recover a misbehaving device, or reset HoloLens when necessary. |
-| [Contact Support](https://support.microsoft.com/supportforbusiness/productselection) | Create a new support request for the business support team. |
-| [More support options](https://support.microsoft.com/products/hololens) | Connect with Microsoft support resources for HoloLens in the enterprise. |
-
-## Related resources
-
-* [Documentation for Holographic app development](https://developer.microsoft.com/windows/mixed-reality/development)
-* [HoloLens release notes](https://docs.microsoft.com/hololens/hololens-release-notes)
diff --git a/devices/surface-hub/General-Data-Privacy-Regulation-and-Surface-Hub.md b/devices/surface-hub/General-Data-Privacy-Regulation-and-Surface-Hub.md
deleted file mode 100644
index e499178078..0000000000
--- a/devices/surface-hub/General-Data-Privacy-Regulation-and-Surface-Hub.md
+++ /dev/null
@@ -1,25 +0,0 @@
----
-title: General Data Privacy Regulation and Surface Hub
-description: Informs users who are subject to EU data protection laws of their options regarding how to delete or restrict diagnostic data produced by Surface Hub.
-ms.assetid: 087713CF-631D-477B-9CC6-EFF939DE0186
-keywords: GDPR
-ms.prod: surface-hub
-ms.sitesec: library
-author: Teresa-MOTIV
-ms.author: v-tea
-ms.topic: article
-ms.localizationpriority: medium
----
-
-# General Data Privacy Regulation and Surface Hub
-
-In May 2018, a European privacy law, the General Data Protection Regulation (GDPR), took effect. The GDPR imposes new rules on companies, government agencies, non-profits, and other organizations that offer goods and services to people in the European Union (EU), or that collect and analyze data tied to EU residents.
-
-Surface Hub customers concerned about privacy under the new GDPR regulations can manage their device privacy with the following options that are provided by Microsoft:
-
-* **Option 1:** Surface Hub devices in regions enforcing GDPR regulations will install KB4284830 when publicly available to automatically reduce diagnostic data emission to basic. Customers opting to provide a higher level of diagnostic data can use the Surface Hub Settings application or Mobile Device Management to override the default basic setting.
-
-* **Option 2:** Surface Hub customers who want to remove any existing diagnostic data can download the **Surface Hub Delete Diagnostic Data** application from the Microsoft Store. This app will allow customers to request deletion of associated diagnostic data directly from their Surface Hub device.
-
-Microsoft has extensive expertise in protecting data, championing privacy, and complying with complex regulations, and currently complies with both EU-U.S. Privacy Shield and EU Model Clauses. We believe that the GDPR is an important step forward for clarifying and enabling individual privacy rights. We want to help you focus on your core business while efficiently preparing for the GDPR.
-
diff --git a/devices/surface-hub/TOC.md b/devices/surface-hub/TOC.md
deleted file mode 100644
index 67516c9773..0000000000
--- a/devices/surface-hub/TOC.md
+++ /dev/null
@@ -1,132 +0,0 @@
-# [Microsoft Surface Hub](index.yml)
-
-# Surface Hub 2S
-
-## Overview
-### [What's new in Surface Hub 2S for IT admins](surface-hub-2s-whats-new.md)
-### [Surface Hub 2S tech specs](surface-hub-2s-techspecs.md)
-### [Operating system essentials (Surface Hub)](differences-between-surface-hub-and-windows-10-enterprise.md)
-### [Adjust Surface Hub 2S brightness, volume, and input](surface-hub-2s-onscreen-display.md)
-### [Use Microsoft Whiteboard on a Surface Hub](https://support.office.com/article/use-microsoft-whiteboard-on-a-surface-hub-5c594985-129d-43f9-ace5-7dee96f7621d)
-
-## Plan
-### [Surface Hub 2S Site Readiness Guide](surface-hub-2s-site-readiness-guide.md)
-#### [Site planning for Surface Hub 2S](surface-hub-2s-site-planning.md)
-#### [Surface Hub 2S quick start](surface-hub-2s-quick-start.md)
-#### [Install and mount Surface Hub 2S](surface-hub-2s-install-mount.md)
-#### [Customize wall mount of Surface Hub 2S](surface-hub-2s-custom-install.md)
-#### [Setup worksheet](setup-worksheet-surface-hub.md)
-#### [Surface Hub 2S ports and keypad overview](surface-hub-2s-port-keypad-overview.md)
-#### [Connect devices to Surface Hub 2S](surface-hub-2s-connect.md)
-### [Prepare your environment for Microsoft Surface Hub 2S](surface-hub-2s-prepare-environment.md)
-### [Configure Easy Authentication for Surface Hub 2S](surface-hub-2s-phone-authenticate.md)
-
-## Deploy
-### [Surface Hub 2S adoption and training](surface-hub-2s-adoption-kit.md)
-### [Surface Hub 2S adoption videos](surface-hub-2s-adoption-videos.md)
-
-### [First time setup for Surface Hub 2S](surface-hub-2s-setup.md)
-### [Connect devices to Surface Hub 2S](surface-hub-2s-connect.md)
-### [Surface Hub 2S deployment checklist](surface-hub-2s-deploy-checklist.md)
-### [Create Surface Hub 2S device account](surface-hub-2s-account.md)
-### [Create provisioning packages for Surface Hub 2S](surface-hub-2s-deploy.md)
-### [Deploy apps to Surface Hub 2S using Intune](surface-hub-2s-deploy-apps-intune.md)
-### [Create Surface Hub 2S on-premises accounts with PowerShell](surface-hub-2s-onprem-powershell.md)
-
-## Manage
-### [Manage Surface Hub 2S with Microsoft Intune](surface-hub-2s-manage-intune.md)
-### [Local management for Surface Hub 2S settings](local-management-surface-hub-settings.md)
-### [Manage device account password rotation](surface-hub-2s-manage-passwords.md)
-### [Manage Windows updates](manage-windows-updates-for-surface-hub.md)
-### [Miracast on existing wireless network or LAN](miracast-over-infrastructure.md)
-### [Save your BitLocker key](save-bitlocker-key-surface-hub.md)
-### [Microsoft Exchange properties](exchange-properties-for-surface-hub-device-accounts.md)
-### [Applying ActiveSync policies to device accounts](apply-activesync-policies-for-surface-hub-device-accounts.md)
-### [Update pen firmware on Surface Hub 2S](surface-hub-2s-pen-firmware.md)
-
-## Secure
-### [Surface Hub security overview](surface-hub-security.md)
-### [Secure and manage Surface Hub 2S with SEMM and UEFI](surface-hub-2s-secure-with-uefi-semm.md)
-### [How Surface Hub addresses Wi-Fi Direct security issues](surface-hub-wifi-direct.md)
-
-## Troubleshoot
-### [Recover and reset Surface Hub 2S](surface-hub-2s-recover-reset.md)
-### [Troubleshoot Miracast on Surface Hub](miracast-troubleshooting.md)
-### [How to pack and ship your Surface Hub 2S for service](surface-hub-2s-pack-components.md)
-### [Change history](surface-hub-2s-change-history.md)
-
-# Surface Hub
-## Overview
-### [What's new in Windows 10, version 1703 for Surface Hub?](surfacehub-whats-new-1703.md)
-### [Operating system essentials (Surface Hub)](differences-between-surface-hub-and-windows-10-enterprise.md)
-### [Technical information for 55" Microsoft Surface Hub](surface-hub-technical-55.md)
-### [Technical information for 84" Microsoft Surface Hub](surface-hub-technical-84.md)
-### [Use Microsoft Whiteboard on a Surface Hub](https://support.office.com/article/use-microsoft-whiteboard-on-a-surface-hub-5c594985-129d-43f9-ace5-7dee96f7621d)
-
-## Plan
-### [Prepare your environment for Microsoft Surface Hub](prepare-your-environment-for-surface-hub.md)
-### [Surface Hub Site Readiness Guide](surface-hub-site-readiness-guide.md)
-### [Physically install Microsoft Surface Hub](physically-install-your-surface-hub-device.md)
-
-## Deploy
-### [Create and test a device account](create-and-test-a-device-account-surface-hub.md)
-#### [Online deployment](online-deployment-surface-hub-device-accounts.md)
-#### [On-premises deployment (single forest)](on-premises-deployment-surface-hub-device-accounts.md)
-#### [On-premises deployment (multiple forests)](on-premises-deployment-surface-hub-multi-forest.md)
-#### [Hybrid deployment](hybrid-deployment-surface-hub-device-accounts.md)
-#### [Online or hybrid deployment using Skype Hybrid Voice environment](skype-hybrid-voice.md)
-#### [Create a device account using UI](create-a-device-account-using-office-365.md)
-#### [Microsoft Exchange properties](exchange-properties-for-surface-hub-device-accounts.md)
-#### [Applying ActiveSync policies to device accounts](apply-activesync-policies-for-surface-hub-device-accounts.md)
-#### [Password management](password-management-for-surface-hub-device-accounts.md)
-#### [Create provisioning packages](provisioning-packages-for-surface-hub.md)
-#### [Admin group management](admin-group-management-for-surface-hub.md)
-### [Set up Microsoft Surface Hub](set-up-your-surface-hub.md)
-#### [Setup worksheet](setup-worksheet-surface-hub.md)
-#### [First-run program](first-run-program-surface-hub.md)
-
-## Manage
-### [Manage Microsoft Surface Hub](manage-surface-hub.md)
-### [PowerShell for Surface Hub](appendix-a-powershell-scripts-for-surface-hub.md)
-### [Remote Surface Hub management](remote-surface-hub-management.md)
-#### [Manage settings with an MDM provider](manage-settings-with-mdm-for-surface-hub.md)
-#### [Monitor your Surface Hub](monitor-surface-hub.md)
-#### [Windows updates](manage-windows-updates-for-surface-hub.md)
-### [Manage Surface Hub settings](manage-surface-hub-settings.md)
-#### [Local management for Surface Hub settings](local-management-surface-hub-settings.md)
-#### [Accessibility](accessibility-surface-hub.md)
-#### [Change the Surface Hub device account](change-surface-hub-device-account.md)
-#### [Device reset](device-reset-surface-hub.md)
-#### [Use fully qualified domain name with Surface Hub](use-fully-qualified-domain-name-surface-hub.md)
-#### [Wireless network management](wireless-network-management-for-surface-hub.md)
-### [Implement Quality of Service on Surface Hub](surface-hub-qos.md)
-### [Install apps on your Surface Hub](install-apps-on-surface-hub.md)
-### [Configure Surface Hub Start menu](surface-hub-start-menu.md)
-### [Set up and use Microsoft Whiteboard](whiteboard-collaboration.md)
-### [End a Surface Hub meeting with End session](i-am-done-finishing-your-surface-hub-meeting.md)
-### [Connect other devices and display with Surface Hub](connect-and-display-with-surface-hub.md)
-### [Miracast on existing wireless network or LAN](miracast-over-infrastructure.md)
-### [Enable 802.1x wired authentication](enable-8021x-wired-authentication.md)
-### [Using a room control system](use-room-control-system-with-surface-hub.md)
-
-## Secure
-### [Sign in to Surface Hub with Microsoft Authenticator](surface-hub-authenticator-app.md)
-### [Save your BitLocker key](save-bitlocker-key-surface-hub.md)
-### [How Surface Hub addresses Wi-Fi Direct security issues](surface-hub-wifi-direct.md)
-
-## Troubleshoot
-### [Using the Surface Hub Recovery Tool](surface-hub-recovery-tool.md)
-### [Surface Hub SSD replacement](surface-hub-ssd-replacement.md)
-### [Top support solutions for Surface Hub](support-solutions-surface-hub.md)
-### [Troubleshoot Microsoft Surface Hub](troubleshoot-surface-hub.md)
-### [Surface Hub Update History](surface-hub-update-history.md)
-### [Known issues and additional information about Microsoft Surface Hub](known-issues-and-additional-info-about-surface-hub.md)
-### [How to use cloud recovery for BitLocker on a Surface Hub](use-cloud-recovery-for-bitlocker-on-surfacehub.md)
-### [Using the Surface Hub Hardware Diagnostic Tool to test a device account](use-surface-hub-diagnostic-test-device-account.md)
-### [Troubleshoot Miracast on Surface Hub](miracast-troubleshooting.md)
-### [Surface Hub Miracast channels 149-165 not supported in Europe, Japan, Israel](surfacehub-miracast-not-supported-europe-japan-israel.md)
-### [What to do if the Connect app in Surface Hub exits unexpectedly](connect-app-in-surface-hub-unexpectedly-exits.md)
-### [Surface Hub may install updates and restart outside maintenance hours](surface-hub-installs-updates-and-restarts-outside-maintenance-hours.md)
-### [General Data Privacy Regulation and Surface Hub](general-data-privacy-regulation-and-surface-hub.md)
-### [Useful downloads for Surface Hub administrators](surface-hub-downloads.md)
-### [Change history for Surface Hub](change-history-surface-hub.md)
diff --git a/devices/surface-hub/accessibility-surface-hub.md b/devices/surface-hub/accessibility-surface-hub.md
deleted file mode 100644
index 8237e61a08..0000000000
--- a/devices/surface-hub/accessibility-surface-hub.md
+++ /dev/null
@@ -1,68 +0,0 @@
----
-title: Accessibility (Surface Hub)
-description: Accessibility settings for the Microsoft Surface Hub can be changed by using the Settings app. You'll find them under Ease of Access. Your Surface Hub has the same accessibility options as Windows 10.
-ms.assetid: 1D44723B-1162-4DF6-99A2-8A3F24443442
-ms.reviewer:
-manager: laurawi
-keywords: Accessibility settings, Settings app, Ease of Access
-ms.prod: surface-hub
-ms.sitesec: library
-author: dansimp
-ms.author: dansimp
-ms.topic: article
-ms.localizationpriority: medium
----
-
-# Accessibility (Surface Hub)
-
-Microsoft Surface Hub has the same accessibility options as Windows 10.
-
-
-## Default accessibility settings
-
-The full list of accessibility settings are available to IT admins in the **Settings** app. The default accessibility settings for Surface Hub include:
-
-| Accessibility feature | Default settings |
-| --------------------- | ----------------- |
-| Magnifier | Off |
-| High contrast | No theme selected |
-| Closed captions | Defaults selected for Font and Background and window |
-| Keyboard | **On-screen Keyboard**, **Sticky Keys**, **Toggle Keys**, and **Filter Keys** are all off. |
-| Mouse | Defaults selected for **Pointer size**, **Pointer color** and **Mouse keys**. |
-| Other options | Defaults selected for **Visual options** and **Touch feedback**. |
-
-The accessibility feature Narrator is not available in the **Settings** app. By default, Narrator is turned off. To change the default settings for Narrator, perform the following steps using a keyboard and mouse.
-
-1. Dismiss the Welcome screen.
-2. Open **Quick Actions** > **Ease of Access** from the status bar.
-
- 
-
-3. Turn Narrator on.
-4. Click **Task Switcher**.
-5. Select **Narrator Settings** from Task Switcher. You can now edit the default Narrator settings.
-
-Additionally, these accessibility features and apps are returned to default settings when users press [End session](finishing-your-surface-hub-meeting.md):
-- Narrator
-- Magnifier
-- High contrast
-- Filter keys
-- Sticky keys
-- Toggle keys
-- Mouse keys
-
-
-## Change accessibility settings during a meeting
-
-During a meeting, users can toggle accessibility features and apps in a couple ways:
-- [Keyboard shortcuts](https://support.microsoft.com/help/13813/windows-10-microsoft-surface-hub-keyboard-shortcuts)
-- **Quick Actions** > **Ease of Access** from the status bar
-
-> 
-
-
-## Related topics
-
-[Manage Microsoft Surface Hub](manage-surface-hub.md)
-
-[Microsoft Surface Hub administrator's guide](surface-hub-administrators-guide.md)
diff --git a/devices/surface-hub/admin-group-management-for-surface-hub.md b/devices/surface-hub/admin-group-management-for-surface-hub.md
deleted file mode 100644
index 81c03b484c..0000000000
--- a/devices/surface-hub/admin-group-management-for-surface-hub.md
+++ /dev/null
@@ -1,86 +0,0 @@
----
-title: Admin group management (Surface Hub)
-description: Every Microsoft Surface Hub can be configured individually by opening the Settings app on the device.
-ms.assetid: FA67209E-B355-4333-B903-482C4A3BDCCE
-ms.reviewer:
-manager: laurawi
-keywords: admin group management, Settings app, configure Surface Hub
-ms.prod: surface-hub
-ms.sitesec: library
-author: dansimp
-ms.author: dansimp
-ms.topic: article
-ms.date: 07/27/2017
-ms.localizationpriority: medium
----
-
-# Admin group management (Surface Hub)
-
-
-Every Surface Hub can be configured locally using the Settings app on the device. To prevent unauthorized users from changing settings, the Settings app requires admin credentials to open the app.
-
-
-## Admin Group Management
-
-You can set up administrator accounts for the device in one of three ways:
-
-- Create a local admin account
-- Domain join the device to Active Directory (AD)
-- Azure Active Directory (Azure AD) join the device
-
-
-### Create a local admin account
-
-To create a local admin, [choose to use a local admin during first run](first-run-program-surface-hub.md#use-a-local-admin). This will create a single local admin account on the Surface Hub with the username and password of your choice. Use these credentials to open the Settings app.
-
-Note that the local admin account information is not backed by any directory service. We recommend you only choose a local admin if the device does not have access to Active Directory (AD) or Azure Active Directory (Azure AD). If you decide to change the local admin’s password, you can do so in Settings. However, if you want to change from using the local admin account to using a group from your domain or Azure AD tenant, then you’ll need to [reset the device](device-reset-surface-hub.md) and go through the first-time program again.
-
-### Domain join the device to Active Directory (AD)
-
-You can domain join the Surface Hub to your AD domain to allow users from a specified security group to configure settings. During first run, choose to use [Active Directory Domain Services](first-run-program-surface-hub.md#use-active-directory-domain-services). You'll need to provide credentials that are capable of joining the domain of your choice, and the name of an existing security group. Anyone who is a member of that security group can enter their credentials and unlock Settings.
-
-#### What happens when you domain join your Surface Hub?
-Surface Hubs use domain join to:
-- Grant admin rights to members of a specified security group in AD.
-- Backup the device's BitLocker recovery key by storing it under the computer object in AD. See [Save your BitLocker key](save-bitlocker-key-surface-hub.md) for details.
-- Synchronize the system clock with the domain controller for encrypted communication
-
-Surface Hub does not support applying group policies or certificates from the domain controller.
-
-> [!NOTE]
-> If your Surface Hub loses trust with the domain (for example, if you remove the Surface Hub from the domain after it is domain joined), you won't be able to authenticate into the device and open up Settings. If you decide to remove the trust relationship of the Surface Hub with your domain, [reset the device](device-reset-surface-hub.md) first.
-
-
-### Azure Active Directory (Azure AD) join the device
-
-You can Azure AD join the Surface Hub to allow IT pros from your Azure AD tenant to configure settings. During first run, choose to use [Microsoft Azure Active Directory](first-run-program-surface-hub.md#use-microsoft-azure-active-directory). You will need to provide credentials that are capable of joining the Azure AD tenant of your choice. After you successfully Azure AD join, the appropriate people will be granted admin rights on the device.
-
-By default, all **global administrators** will be given admin rights on an Azure AD joined Surface Hub. With **Azure AD Premium** or **Enterprise Mobility Suite (EMS)**, you can add additional administrators:
-1. In the [Azure classic portal](https://manage.windowsazure.com/), click **Active Directory**, and then click the name of your organization's directory.
-2. On the **Configure** page, under **Devices** > **Additional administrators on Azure AD joined devices**, click **Selected**.
-3. Click **Add**, and select the users you want to add as administrators on your Surface Hub and other Azure AD joined devices.
-4. When you have finished, click the checkmark button to save your change.
-
-#### What happens when you Azure AD join your Surface Hub?
-Surface Hubs use Azure AD join to:
-- Grant admin rights to the appropriate users in your Azure AD tenant.
-- Backup the device's BitLocker recovery key by storing it under the account that was used to Azure AD join the device. See [Save your BitLocker key](save-bitlocker-key-surface-hub.md) for details.
-
-### Automatic enrollment via Azure Active Directory join
-
-Surface Hub now supports the ability to automatically enroll in Intune by joining the device to Azure Active Directory.
-
-For more information, see [Enable Windows 10 automatic enrollment](https://docs.microsoft.com/intune/windows-enroll#enable-windows-10-automatic-enrollment).
-
-### Which should I choose?
-
-If your organization is using AD or Azure AD, we recommend you either domain join or Azure AD join, primarily for security reasons. People will be able to authenticate and unlock Settings with their own credentials, and can be moved in or out of the security groups associated with your domain.
-
-| Option | Requirements | Which credentials can be used to access the Settings app? |
-|---------------------------------------------------|-----------------------------------------|-------|
-| Create a local admin account | None | The user name and password specified during first run |
-| Domain join to Active Directory (AD) | Your organization uses AD | Any AD user from a specific security group in your domain |
-| Azure Active Directory (Azure AD) join the device | Your organization uses Azure AD Basic | Global administrators only |
-| | Your organization uses Azure AD Premium or Enterprise Mobility Suite (EMS) | Global administrators and additional administrators |
-
-
diff --git a/devices/surface-hub/appendix-a-powershell-scripts-for-surface-hub.md b/devices/surface-hub/appendix-a-powershell-scripts-for-surface-hub.md
deleted file mode 100644
index f74f2297fa..0000000000
--- a/devices/surface-hub/appendix-a-powershell-scripts-for-surface-hub.md
+++ /dev/null
@@ -1,1692 +0,0 @@
----
-title: PowerShell for Surface Hub (Surface Hub)
-description: PowerShell scripts to help set up and manage your Microsoft Surface Hub.
-ms.assetid: 3EF48F63-8E4C-4D74-ACD5-461F1C653784
-ms.reviewer:
-manager: laurawi
-keywords: PowerShell, set up Surface Hub, manage Surface Hub
-ms.prod: surface-hub
-ms.sitesec: library
-author: dansimp
-ms.author: dansimp
-ms.topic: article
-ms.date: 01/10/2018
-ms.localizationpriority: medium
----
-
-# PowerShell for Surface Hub
-
-
-PowerShell scripts to help set up and manage your Microsoft Surface Hub.
-
-- [PowerShell scripts for Surface Hub admins](#scripts-for-admins)
- - [Create an on-premises account](#create-on-premises-ps-scripts)
- - [Create a device account using Office 365](#create-os356-ps-scripts)
- - [Account verification script](#acct-verification-ps-scripts)
- - [Enable Skype for Business (EnableSfb.ps1)](#enable-sfb-ps-scripts)
-- [Useful cmdlets](#useful-cmdlets)
- - [Creating a Surface Hub-compatible Exchange ActiveSync policy](#create-compatible-as-policy)
- - [Allowing device IDs for ActiveSync](#whitelisting-device-ids-cmdlet)
- - [Auto-accepting and declining meeting requests](#auto-accept-meetings-cmdlet)
- - [Accepting external meeting requests](#accept-ext-meetings-cmdlet)
-
-
-## Prerequisites
-
-To successfully execute these PowerShell scripts, you will need to install the following prerequisites:
-
-- [Microsoft Online Services Sign-in Assistant for IT Professionals RTW](https://www.microsoft.com/download/details.aspx?id=41950)
-- [Microsoft Azure Active Directory Module for Windows PowerShell (64-bit version)](https://www.powershellgallery.com/packages/MSOnline/1.1.183.17)
-- [Windows PowerShell Module for Skype for Business Online](https://www.microsoft.com/download/details.aspx?id=39366)
-
-## PowerShell scripts for Surface Hub administrators
-
-
-What do the scripts do?
-
-- Create device accounts for setups using pure single-forest on-premises (Microsoft Exchange and Skype 2013 and later only) or online (Microsoft Office 365), that are configured correctly for your Surface Hub.
-- Validate existing device accounts for any setup (on-premises or online) to make sure they're compatible with Surface Hub.
-- Provide a base template for anyone wanting to create their own device account creation or validation scripts.
-
-What do you need in order to run the scripts?
-
-- Remote PowerShell access to your organization's domain or tenant, Exchange servers, and Skype for Business servers.
-- Admin credentials for your organization's domain or tenant, Exchange servers, and Skype for Business servers.
-
->[!NOTE]
->Whether you’re creating a new account or modifying an already-existing account, the validation script will verify that your device account is configured correctly. You should always run the validation script before adding a device account to Surface Hub.
-
-
-
-## Running the scripts
-
-
-The account creation scripts will:
-
-- Ask for administrator credentials
-- Create device accounts in your domain/tenant
-- Create or assign a Surface Hub-compatible ActiveSync policy to the device account(s)
-- Set various attributes for the created account(s) in Exchange and Skype for Business.
-- Assign licenses and permissions to the created account(s)
-
-These are the attributes that are set by the scripts:
-
-
-
-
-
-
-
-
-
-
Cmdlet
-
Attribute
-
Value
-
-
-
-
-
Set-Mailbox
-
RoomMailboxPassword
-
User-provided
-
-
-
-
EnableRoomMailboxAccount
-
True
-
-
-
-
Type
-
Room
-
-
-
Set-CalendarProcessing
-
AutomateProcessing
-
AutoAccept
-
-
-
-
RemovePrivateProperty
-
False
-
-
-
-
DeleteSubject
-
False
-
-
-
-
DeleteComments
-
False
-
-
-
-
AddOrganizerToSubject
-
False
-
-
-
-
AddAdditionalResponse
-
True
-
-
-
-
AdditionalResponse
-
"This is a Surface Hub room!"
-
-
-
New-MobileDeviceMailboxPolicy
-
PasswordEnabled
-
False
-
-
-
-
AllowNonProvisionableDevices
-
True
-
-
-
Enable-CSMeetingRoom
-
RegistrarPool
-
User-provided
-
-
-
-
SipAddress
-
Set to the User Principal Name (UPN) of the device account
-
-
-
Set-MsolUserLicense (O365 only)
-
AddLicenses
-
User-provided
-
-
-
Set-MsolUser (O365 only)
-
PasswordNeverExpires
-
True
-
-
-
Set-AdUser (On-prem only)
-
Enabled
-
True
-
-
-
Set-AdUser (On-prem only)
-
PasswordNeverExpires
-
True
-
-
-
-
-
-
-## Account creation scripts
-
-
-These scripts will create a device account for you. You can use the [Account verification script](#acct-verification-ps-scripts) to make sure they ran correctly.
-
-The account creation scripts cannot modify an already existing account, but can be used to help you understand which cmdlets need to be run to configure the existing account correctly.
-
-### Create an on-premises account
-
-Creates an account as described in [On-premises deployment](on-premises-deployment-surface-hub-device-accounts.md).
-
-```PowerShell
-# SHAccountCreateOnPrem.ps1
-
-$Error.Clear()
-$ErrorActionPreference = "Stop"
-$status = @{}
-
-# Cleans up set state such as remote powershell sessions
-function Cleanup()
-{
- if ($sessExchange)
- {
- Remove-PSSession $sessExchange
- }
- if ($sessCS)
- {
- Remove-PSSession $sessCS
- }
-}
-
-function PrintError($strMsg)
-{
- Write-Host $strMsg -foregroundcolor Red
-}
-
-function PrintSuccess($strMsg)
-{
- Write-Host $strMsg -foregroundcolor Green
-}
-
-function PrintAction($strMsg)
-{
- Write-Host $strMsg -ForegroundColor Cyan
-}
-
-
-# Cleans up and prints an error message
-function CleanupAndFail($strMsg)
-{
- if ($strMsg)
- {
- PrintError($strMsg);
- }
- Cleanup
- exit 1
-}
-
-# Exits if there is an error set and prints the given message
-function ExitIfError($strMsg)
-{
- if ($Error)
- {
- CleanupAndFail($strMsg);
- }
-}
-
-## Collect account data ##
-$credNewAccount = (Get-Credential -Message "Enter the desired UPN and password for this new account")
-$strUpn = $credNewAccount.UserName
-$strDisplayName = Read-Host "Please enter the display name you would like to use for $strUpn"
-if (!$credNewAccount -Or [System.String]::IsNullOrEmpty($strDisplayName) -Or [System.String]::IsNullOrEmpty($credNewAccount.UserName) -Or $credNewAccount.Password.Length -le 0)
-{
- CleanupAndFail "Please enter all of the requested data to continue."
- exit 1
-}
-
-
-## Sign in to remote powershell for exchange and lync online ##
-
-$credExchange = $null
-$credExchange=Get-Credential -Message "Enter credentials of an Exchange user with mailbox creation rights"
-if (!$credExchange)
-{
- CleanupAndFail("Valid credentials are required to create and prepare the account.");
-}
-$strExchangeServer = Read-Host "Please enter the FQDN of your exchange server (e.g. exch.contoso.com)"
-
-# Lync info
-$credLync = Get-Credential -Message "Enter credentials of a Skype for Business admin (or cancel if they are the same as Exchange)"
-if (!$credLync)
-{
- $credLync = $credExchange
-}
-$strLyncFQDN = Read-Host "Please enter the FQDN of your Lync server (e.g. lync.contoso.com) or enter to use [$strExchangeServer]"
-if ([System.String]::IsNullOrEmpty($strLyncFQDN))
-{
- $strLyncFQDN = $strExchangeServer
-}
-
-
-PrintAction "Connecting to remote sessions. This can occasionally take a while - please do not enter input..."
-try
-{
- $sessExchange = New-PSSession -ConfigurationName microsoft.exchange -Credential $credExchange -AllowRedirection -Authentication Kerberos -ConnectionUri "http://$strExchangeServer/powershell" -WarningAction SilentlyContinue
-}
-catch
-{
- CleanupAndFail("Failed to connect to exchange. Please check your credentials and try again. If this continues to fail, you may not have permission for remote powershell - if not, please perform the setup manually. Error message: $_")
-}
-PrintSuccess "Connected to Remote Exchange Shell"
-
-try
-{
- $sessLync = New-PSSession -Credential $credLync -ConnectionURI "https://$strLyncFQDN/OcsPowershell" -AllowRedirection -WarningAction SilentlyContinue
-}
-catch
-{
- CleanupAndFail("Failed to connect to Lync. Please check your credentials and try again. Error message: $_")
-}
-PrintSuccess "Connected to Lync Server Remote PowerShell"
-
-
-Import-PSSession $sessExchange -AllowClobber -WarningAction SilentlyContinue
-Import-PSSession $sessLync -AllowClobber -WarningAction SilentlyContinue
-
-## Create the Exchange mailbox ##
-# Note: These exchange commandlets do not always throw their errors as exceptions
-
-# Because Get-Mailbox will throw an error if the mailbox is not found
-$Error.Clear()
-PrintAction "Creating a new account..."
-try
-{
- $mailbox = $null
- $mailbox = (New-Mailbox -UserPrincipalName $credNewAccount.UserName -Alias $credNewAccount.UserName.substring(0,$credNewAccount.UserName.indexOf('@')) -room -Name $strDisplayName -RoomMailboxPassword $credNewAccount.Password -EnableRoomMailboxAccount $true)
-} catch { }
-ExitIfError "Failed to create a new mailbox on exchange.";
-$status["Mailbox Setup"] = "Successfully created a mailbox for the new account"
-
-
-$strEmail = $mailbox.WindowsEmailAddress
-PrintSuccess "The following mailbox has been created for this room: $strEmail"
-
-
-## Create or retrieve a policy that will be applied to surface hub devices ##
-# The policy disables requiring a device password so that the SurfaceHub does not need to be lockable to use Active Sync
-$strPolicy = Read-Host 'Please enter the name for a new Surface Hub ActiveSync policy that will be created and applied to this account.
-We will configure that policy to be compatible with Surface Hub devices.
-If this script has been used before, please enter the name of the existing policy.'
-
-$easpolicy = $null
-try {
- $easpolicy = Get-MobileDeviceMailboxPolicy $strPolicy
-}
-catch {}
-
-if ($easpolicy)
-{
- if (!$easpolicy.PasswordEnabled -and ($easpolicy.AllowNonProvisionableDevices -eq $null -or $easpolicy.AllowNonProvisionableDevices ))
- {
- PrintSuccess "An existing policy has been found and will be applied to this account."
- }
- else
- {
- PrintError "The policy you provided is incompatible with the surface hub."
- $easpolicy = $null
- $status["Device Password Policy"] = "Failed to apply the EAS policy to the account because the policy was invalid."
- }
-}
-else
-{
- $Error.Clear()
- PrintAction "Creating policy..."
- $easpolicy = New-MobileDeviceMailboxPolicy -Name $strPolicy -PasswordEnabled $false -AllowNonProvisionableDevices $true
- if ($easpolicy)
- {
- PrintSuccess "A new device policy has been created; you can use this same policy for all future Surface Hub device accounts."
- }
- else
- {
- PrintError "Could not create $strPolicy"
- }
-}
-
-if ($easpolicy)
-{
- # Convert mailbox to user type so we can apply the policy (necessary)
- # Sometimes it takes a while for this change to take affect so we have some nasty retry loops
- $Error.Clear();
- try
- {
- Set-Mailbox $credNewAccount.UserName -Type Regular
- } catch {}
- if ($Error)
- {
- $Error.Clear()
- $status["Device Password Policy"] = "Failed to apply the EAS policy to the account."
- }
- else
- {
- # Loop until resource type goes away, up to 5 times
- for ($i = 0; $i -lt 5 -And (Get-Mailbox $credNewAccount.UserName).ResourceType; $i++)
- {
- Start-Sleep -s 5
- }
- # If the mailbox is still a Room we cannot apply the policy
- if (!((Get-Mailbox $credNewAccount.UserName).ResourceType))
- {
- $Error.Clear()
- # Set policy for account
- Set-CASMailbox $credNewAccount.UserName -ActiveSyncMailboxPolicy $strPolicy
- if (!$Error)
- {
- $status["ActiveSync Policy"] = "Successfully applied $strPolicy to the account"
- }
- else
- {
- $status["ActiveSync Policy"] = "Failed to apply the EAS policy to the account."
- }
- $Error.Clear()
-
- # Convert back to room mailbox
- Set-Mailbox $credNewAccount.UserName -Type Room
- # Loop until resource type goes back to room
- for ($i = 0; ($i -lt 5) -And ((Get-Mailbox $credNewAccount.UserName).ResourceType -ne "Room"); $i++)
- {
- Start-Sleep -s 5
- }
- if ((Get-Mailbox $credNewAccount.UserName).ResourceType -ne "Room")
- {
- # A failure to convert the mailbox back to a room is unfortunate but means the mailbox is unusable.
- $status["Mailbox Setup"] = "A mailbox was created but we could not set it to a room resource type."
- }
- else
- {
- try
- {
- Set-Mailbox $credNewAccount.UserName -RoomMailboxPassword $credNewAccount.Password -EnableRoomMailboxAccount $true
- } catch { }
- if ($Error)
- {
- $status["Mailbox Setup"] = "A room mailbox was created but we could not set its password."
- }
- $Error.Clear()
- }
-
- }
- }
-}
-PrintSuccess "Account creation completed."
-
-PrintAction "Setting calendar processing rules..."
-
-$Error.Clear();
-## Prepare the calendar for automatic meeting responses ##
-try {
- Set-CalendarProcessing -Identity $credNewAccount.UserName -AutomateProcessing AutoAccept
-} catch { }
-if ($Error)
-{
- $status["Calendar Acceptance"] = "Failed to configure the account to automatically accept/decline meeting requests"
-}
-else
-{
- $status["Calendar Acceptance"] = "Successfully configured the account to automatically accept/decline meeting requests"
-}
-
-
-$Error.Clear()
-try {
- Set-CalendarProcessing -Identity $credNewAccount.UserName -RemovePrivateProperty $false -AddOrganizerToSubject $false -AddAdditionalResponse $true -DeleteSubject $false -DeleteComments $false -AdditionalResponse "This is a Surface Hub room!"
-} catch { }
-if ($Error)
-{
- $status["Calendar Response Configuration"] = "Failed to configure the account's response properties"
-}
-else
-{
- $status["Calendar Response Configuration"] = "Successfully configured the account's response properties"
-}
-
-$Error.Clear()
-## Configure the Account to not expire ##
-PrintAction "Configuring password not to expire..."
-Start-Sleep -s 20
-try
-{
- Set-AdUser $mailbox.UserPrincipalName -PasswordNeverExpires $true -Enabled $true
-}
-catch
-{
-
-}
-
-if ($Error)
-{
- $status["Password Expiration Policy"] = "Failed to set the password to never expire"
-}
-else
-{
- $status["Password Expiration Policy"] = "Successfully set the password to never expire"
-}
-
-PrintSuccess "Completed Exchange configuration"
-
-## Setup Skype for Business. This is somewhat optional and if it fails we SfbEnable can be used later ##
-PrintAction "Configuring account for Skype for Business."
-
-# Getting registrar pool
-$strRegPool = $strLyncFQDN
-$Error.Clear()
-$strRegPoolEntry = Read-Host "Enter a Skype for Business Registrar Pool, or leave blank to use [$strRegPool]"
-if (![System.String]::IsNullOrEmpty($strRegPoolEntry))
-{
- $strRegPool = $strRegPoolEntry
-}
-
-# Try to SfB-enable the account. Note that it may not work right away as the account needs to propagate to active directory
-PrintAction "Enabling Skype for Business..."
-Start-Sleep -s 10
-$Error.Clear()
-try {
- Enable-CsMeetingRoom -Identity $credNewAccount.UserName -RegistrarPool $strRegPool -SipAddressType EmailAddress
-}
-catch { }
-
-if ($Error)
-{
- $status["Skype for Business Account Setup"] = "Failed to setup the Skype for Business meeting room - you can run EnableSfb.ps1 to try again."
- $Error.Clear();
-}
-else
-{
- $status["Skype for Business Account Setup"] = "Successfully enabled account as a Skype for Business meeting room"
-}
-
-Write-Host
-
-## Cleanup and print results ##
-Cleanup
-$strDisplay = $mailbox.DisplayName
-$strUsr = $credNewAccount.UserName
-PrintAction "Summary for creation of $strUsr ($strDisplay)"
-if ($status.Count -gt 0)
-{
- ForEach($k in $status.Keys)
- {
- $v = $status[$k]
- $color = "yellow"
- if ($v[0] -eq "S") { $color = "green" }
- elseif ($v[0] -eq "F")
- {
- $color = "red"
- $v += " Go to https://aka.ms/shubtshoot"
- }
-
- Write-Host -NoNewline $k -ForegroundColor $color
- Write-Host -NoNewline ": "
- Write-Host $v
- }
-}
-else
-{
- PrintError "The account could not be created"
-}
-```
-
-### Create a device account using Office 365
-
-Creates an account as described in [Create a device account using Office 365](create-a-device-account-using-office-365.md)
-
-```PowerShell
-# SHAccountCreateO365.ps1
-
-$Error.Clear()
-$ErrorActionPreference = "Stop"
-$status = @{}
-
-# Cleans up set state such as remote powershell sessions
-function Cleanup()
-{
- if ($sessExchange)
- {
- Remove-PSSession $sessExchange
- }
- if ($sessCS)
- {
- Remove-PSSession $sessCS
- }
-}
-
-function PrintError($strMsg)
-{
- Write-Host $strMsg -foregroundcolor Red
-}
-
-function PrintSuccess($strMsg)
-{
- Write-Host $strMsg -foregroundcolor Green
-}
-
-function PrintAction($strMsg)
-{
- Write-Host $strMsg -ForegroundColor Cyan
-}
-
-
-# Cleans up and prints an error message
-function CleanupAndFail($strMsg)
-{
- if ($strMsg)
- {
- PrintError($strMsg);
- }
- Cleanup
- exit 1
-}
-
-# Exits if there is an error set and prints the given message
-function ExitIfError($strMsg)
-{
- if ($Error)
- {
- CleanupAndFail($strMsg);
- }
-}
-
-
-## Check dependencies ##
-try {
- Import-Module SkypeOnlineConnector
- Import-Module MSOnline
-}
-catch
-{
- PrintError "Some dependencies are missing"
- PrintError "Please install the Windows PowerShell Module for Lync Online. For more information go to https://www.microsoft.com/download/details.aspx?id=39366"
- PrintError "Please install the Azure Active Directory module for PowerShell from https://go.microsoft.com/fwlink/p/?linkid=236297"
- CleanupAndFail
-}
-
-
-
-## Collect account data ##
-$credNewAccount = (Get-Credential -Message "Enter the desired UPN and password for this new account")
-$strUpn = $credNewAccount.UserName
-$strDisplayName = Read-Host "Please enter the display name you would like to use for $strUpn"
-if (!$credNewAccount -Or [System.String]::IsNullOrEmpty($strDisplayName) -Or [System.String]::IsNullOrEmpty($credNewAccount.UserName) -Or $credNewAccount.Password.Length -le 0)
-{
- CleanupAndFail "Please enter all of the requested data to continue."
- exit 1
-}
-
-
-## Sign in to remote powershell for exchange and lync online ##
-$credAdmin = $null
-$credAdmin=Get-Credential -Message "Enter credentials of an Exchange and Skype for Business admin"
-if (!$credadmin)
-{
- CleanupAndFail "Valid admin credentials are required to create and prepare the account."
-}
-PrintAction "Connecting to remote sessions. This can occasionally take a while - please do not enter input..."
-try
-{
- $sessExchange = New-PSSession -ConfigurationName microsoft.exchange -Credential $credAdmin -AllowRedirection -Authentication basic -ConnectionUri "https://outlook.office365.com/powershell-liveid/" -WarningAction SilentlyContinue
-}
-catch
-{
- CleanupAndFail "Failed to connect to exchange. Please check your credentials and try again. Error message: $_"
-}
-
-try
-{
- $sessCS = New-CsOnlineSession -Credential $credAdmin
-}
-catch
-{
- CleanupAndFail "Failed to connect to Skype for Business Online Datacenter. Please check your credentials and try again. Error message: $_"
-}
-
-try
-{
- Connect-MsolService -Credential $credAdmin
-}
-catch
-{
- CleanupAndFail "Failed to connect to Azure Active Directory. Please check your credentials and try again. Error message: $_"
-}
-
-Import-PSSession $sessExchange -AllowClobber -WarningAction SilentlyContinue
-Import-PSSession $sessCS -AllowClobber -WarningAction SilentlyContinue
-
-## Create the Exchange mailbox ##
-# Note: These exchange commandlets do not always throw their errors as exceptions
-
-# Because Get-Mailbox will throw an error if the mailbox is not found
-$Error.Clear()
-PrintAction "Creating a new account..."
-try
-{
- $mailbox = $null
- $mailbox = (New-Mailbox -MicrosoftOnlineServicesID $credNewAccount.UserName -room -Name $strDisplayName -RoomMailboxPassword $credNewAccount.Password -EnableRoomMailboxAccount $true)
-} catch { }
-ExitIfError "Failed to create a new mailbox on exchange.";
-$status["Mailbox Setup"] = "Successfully created a mailbox for the new account"
-
-
-$strEmail = $mailbox.WindowsEmailAddress
-PrintSuccess "The following mailbox has been created for this room: $strEmail"
-
-
-## Create or retrieve a policy that will be applied to surface hub devices ##
-# The policy disables requiring a device password so that the SurfaceHub does not need to be lockable to use Active Sync
-$strPolicy = Read-Host 'Please enter the name for a new Surface Hub ActiveSync policy that will be created and applied to this account.
-We will configure that policy to be compatible with Surface Hub devices.
-If this script has been used before, please enter the name of the existing policy.'
-
-$easpolicy = $null
-try {
- $easpolicy = Get-MobileDeviceMailboxPolicy $strPolicy
-}
-catch {}
-
-if ($easpolicy)
-{
- if (!$easpolicy.PasswordEnabled -and ($easpolicy.AllowNonProvisionableDevices -eq $null -or $easpolicy.AllowNonProvisionableDevices ))
- {
- PrintSuccess "An existing policy has been found and will be applied to this account."
- }
- else
- {
- PrintError "The policy you provided is incompatible with the surface hub."
- $easpolicy = $null
- $status["ActiveSync Policy"] = "Failed to apply the EAS policy to the account because the policy was invalid."
- }
-}
-else
-{
- $Error.Clear()
- PrintAction "Creating policy..."
- $easpolicy = New-MobileDeviceMailboxPolicy -Name $strPolicy -PasswordEnabled $false -AllowNonProvisionableDevices $true
- if ($easpolicy)
- {
- PrintSuccess "A new device policy has been created; you can use this same policy for all future Surface Hub device accounts."
- }
- else
- {
- PrintError "Could not create $strPolicy"
- }
-}
-
-if ($easpolicy)
-{
- # Convert mailbox to user type so we can apply the policy (necessary)
- # Sometimes it takes a while for this change to take affect so we have some nasty retry loops
- $Error.Clear();
- try
- {
- Set-Mailbox $credNewAccount.UserName -Type Regular
- } catch {}
- if ($Error)
- {
- $Error.Clear()
- $status["Device Password Policy"] = "Failed to apply the EAS policy to the account."
- PrintError "Failed to convert to regular account"
- }
- else
- {
- # Loop until resource type goes away, up to 5 times
- for ($i = 0; $i -lt 5 -And (Get-Mailbox $credNewAccount.UserName).ResourceType; $i++)
- {
- Start-Sleep -s 5
- }
- # If the mailbox is still a Room we cannot apply the policy
- if (!((Get-Mailbox $credNewAccount.UserName).ResourceType))
- {
- $Error.Clear()
- # Set policy for account
- Set-CASMailbox $credNewAccount.UserName -ActiveSyncMailboxPolicy $strPolicy
- if (!$Error)
- {
- $status["Device Password Policy"] = "Successfully applied $strPolicy to the account"
- }
- else
- {
- $status["Device Password Policy"] = "Failed to apply the EAS policy to the account."
- PrintError "Failed to apply policy"
- }
- $Error.Clear()
-
- # Convert back to room mailbox
- Set-Mailbox $credNewAccount.UserName -Type Room
- # Loop until resource type goes back to room
- for ($i = 0; ($i -lt 5) -And ((Get-Mailbox $credNewAccount.UserName).ResourceType -ne "Room"); $i++)
- {
- Start-Sleep -s 5
- }
- if ((Get-Mailbox $credNewAccount.UserName).ResourceType -ne "Room")
- {
- # A failure to convert the mailbox back to a room is unfortunate but means the mailbox is unusable.
- $status["Mailbox Setup"] = "A mailbox was created but we could not set it to a room resource type."
- }
- else
- {
- Set-Mailbox $credNewAccount.UserName -RoomMailboxPassword $credNewAccount.Password -EnableRoomMailboxAccount $true
- if ($Error)
- {
- $status["Mailbox Setup"] = "A room mailbox was created but we could not set its password."
- }
- $Error.Clear()
- }
-
- }
- }
-}
-else
-{
- $status["Device Password Policy"] = "Failed to apply the EAS policy to the account."
- PrintError "Failed to obtain policy"
-}
-PrintSuccess "Account creation completed."
-
-PrintAction "Setting calendar processing rules..."
-
-$Error.Clear();
-## Prepare the calendar for automatic meeting responses ##
-try {
- Set-CalendarProcessing -Identity $credNewAccount.UserName -AutomateProcessing AutoAccept
-} catch { }
-if ($Error)
-{
- $status["Calendar Acceptance"] = "Failed to configure the account to automatically accept/decline meeting requests"
-}
-else
-{
- $status["Calendar Acceptance"] = "Successfully configured the account to automatically accept/decline meeting requests"
-}
-
-
-$Error.Clear()
-try {
- Set-CalendarProcessing -Identity $credNewAccount.UserName -RemovePrivateProperty $false -AddOrganizerToSubject $false -AddAdditionalResponse $true -DeleteSubject $false -DeleteComments $false -AdditionalResponse "This is a Surface Hub room!"
-} catch { }
-if ($Error)
-{
- $status["Calendar Response Configuration"] = "Failed to configure the account's response properties"
-}
-else
-{
- $status["Calendar Response Configuration"] = "Successfully configured the account's response properties"
-}
-
-$Error.Clear()
-## Configure the Account to not expire ##
-PrintAction "Configuring password not to expire..."
-try
-{
- Set-MsolUser -UserPrincipalName $credNewAccount.UserName -PasswordNeverExpires $true
-}
-catch
-{
-
-}
-
-if ($Error)
-{
- $status["Password Expiration Policy"] = "Failed to set the password to never expire"
-}
-else
-{
- $status["Password Expiration Policy"] = "Successfully set the password to never expire"
-}
-
-PrintSuccess "Completed Exchange configuration"
-
-## Setup Skype for Business. This is somewhat optional and if it fails we SfbEnable can be used later ##
-PrintAction "Configuring account for Skype for Business."
-
-# Getting registrar pool
-$strRegPool = $null
-try {
- $strRegPool = (Get-CsTenant).TenantPoolExtension
-}
-catch {}
-$Error.Clear()
-if (![System.String]::IsNullOrEmpty($strRegPool))
-{
- $strRegPool = $strRegPool.Substring($strRegPool[0].IndexOf(':') + 1)
-}
-<#
-$strRegPoolEntry = Read-Host "Enter a Skype for Business Registrar Pool, or leave blank to use [$strRegPool]"
-if (![System.String]::IsNullOrEmpty($strRegPoolEntry))
-{
- $strRegPool = $strRegPoolEntry
-}
-#>
-
-# Try to SfB-enable the account. Note that it may not work right away as the account needs to propagate to active directory
-PrintAction "Enabling Skype for Business on $strRegPool"
-Start-Sleep -s 10
-$Error.Clear()
-try {
- Enable-CsMeetingRoom -Identity $credNewAccount.UserName -RegistrarPool $strRegPool -SipAddressType EmailAddress
-}
-catch { }
-
-if ($Error)
-{
- $status["Skype for Business Account Setup"] = "Failed to setup the Skype for Business meeting room - you can run EnableSfb.ps1 to try again."
- $Error.Clear();
-}
-else
-{
- $status["Skype for Business Account Setup"] = "Successfully enabled account as a Skype for Business meeting room"
-}
-
-## Now we need to assign a Skype for Business license to the account ##
-# Assign a license to thes
-$countryCode = (Get-CsTenant).CountryAbbreviation
-$loc = Read-Host "Please enter the usage location for this device account (where the account is being used). This is a 2-character code that is used to assign licenses (e.g. $countryCode)"
-try {
- $Error.Clear()
- Set-MsolUser -UserPrincipalName $credNewAccount.UserName -UsageLocation $loc
-}
-catch{}
-if ($Error)
-{
- $status["Office 365 License"] = "Failed to assign an Office 365 license to the account"
- $Error.Clear()
-}
-else
-{
- PrintAction "We found the following licenses available for your tenant:"
- $skus = (Get-MsolAccountSku | Where-Object { !$_.AccountSkuID.Contains("INTUNE"); })
- $i = 1
- $skus | % {
- Write-Host -NoNewline $i
- Write-Host -NoNewLine ": AccountSKUID: "
- Write-Host -NoNewLine $_.AccountSkuid
- Write-Host -NoNewLine " Active Units: "
- Write-Host -NoNewLine $_.ActiveUnits
- Write-Host -NoNewLine " Consumed Units: "
- Write-Host $_.ConsumedUnits
- $i++
- }
- $iLicenseIndex = 0;
- do
- {
- $iLicenseIndex = Read-Host 'Choose the number for the SKU you want to pick'
- } while ($iLicenseIndex -lt 1 -or $iLicenseIndex -gt $skus.Length)
- $strLicenses = $skus[$iLicenseIndex - 1].AccountSkuId
-
- if (![System.String]::IsNullOrEmpty($strLicenses))
- {
- try
- {
- $Error.Clear()
- Set-MsolUserLicense -UserPrincipalName $credNewAccount.UserName -AddLicenses $strLicenses
- }
- catch
- {
-
- }
- if ($Error)
- {
- $Error.Clear()
- $status["Office 365 License"] = "Failed to add a license to the account. Make sure you have remaining licenses."
- }
- else
- {
- $status["Office 365 License"] = "Successfully added license to the account"
- }
- }
- else
- {
- $status["Office 365 License"] = "You opted not to install a license on this account"
- }
-}
-
-
-Write-Host
-
-## Cleanup and print results ##
-Cleanup
-$strDisplay = $mailbox.DisplayName
-$strUsr = $credNewAccount.UserName
-PrintAction "Summary for creation of $strUsr ($strDisplay)"
-if ($status.Count -gt 0)
-{
- ForEach($k in $status.Keys)
- {
- $v = $status[$k]
- $color = "yellow"
- if ($v[0] -eq "S") { $color = "green" }
- elseif ($v[0] -eq "F")
- {
- $color = "red"
- $v += " Go to https://aka.ms/shubtshoot for help"
- }
-
- Write-Host -NoNewline $k -ForegroundColor $color
- Write-Host -NoNewline ": "
- Write-Host $v
- }
-}
-else
-{
- PrintError "The account could not be created"
-}
-```
-
-## Account verification script
-
-
-This script will validate the previously-created device account on a Surface Hub, no matter which method was used to create it. This script is basically pass/fail. If one of the test errors out, it will show a detailed error message, but if all tests pass, the end result will be a summary report. For example, you might see:
-
-``` syntax
-15 tests executed
-0 failures
-2 warnings
-15 passed
-```
-
-Details of specific settings will not be shown.
-
-```PowerShell
-# SHAccountValidate.ps1
-
-$Error.Clear()
-$ErrorActionPreference = "Stop"
-
-
-# Cleans up set state such as remote powershell sessions
-function Cleanup()
-{
- if ($sessEx)
- {
- Remove-PSSession $sessEx
- }
- if ($sessSfb)
- {
- Remove-PSSession $sessSfb
- }
-}
-
-function PrintError($strMsg)
-{
- Write-Host $strMsg -foregroundcolor "red"
-}
-
-function PrintSuccess($strMsg)
-{
- Write-Host $strMsg -foregroundcolor "green"
-}
-
-function PrintAction($strMsg)
-{
- Write-Host $strMsg -ForegroundColor Cyan
-}
-
-
-# Cleans up and prints an error message
-function CleanupAndFail($strMsg)
-{
- if ($strMsg)
- {
- PrintError($strMsg);
- }
- Cleanup
- exit 1
-}
-
-# Exits if there is an error set and prints the given message
-function ExitIfError($strMsg)
-{
- if ($Error)
- {
- CleanupAndFail($strMsg);
- }
-}
-
-$strUpn = Read-Host "What is the email address of the account you wish to validate?"
-if (!$strUpn.Contains('@'))
-{
- CleanupAndFail "$strUpn is not a valid email address"
-}
-$strExServer = Read-Host "What is your exchange server? (leave blank for online tenants)"
-if ($strExServer.Equals(""))
-{
- $fExIsOnline = $true
-}
-else
-{
- $fExIsOnline = $false
-}
-$credEx = Get-Credential -Message "Please provide exchange user credentials"
-
-$strRegistrarPool = Read-Host ("What is the Skype for Business registrar pool for $strUpn" + "? (leave blank for online tenants)")
-$fSfbIsOnline = $strRegistrarPool.Equals("")
-
-$fHasOnPrem = $true
-if ($fSfbIsOnline -and $fExIsOnline)
-{
- do
- {
- $strHasOnPrem = (Read-Host "Do you have an on-premises Active Directory (Y/N) (No if your domain services are hosted entirely online)").ToUpper()
- } while ($strHasOnPrem -ne "Y" -and $strHasOnPrem -ne "N")
- $fHasOnPrem = $strHasOnPrem.Equals("Y")
-}
-
-$fHasOnline = $false
-if ($fSfbIsOnline -or $fExIsOnline)
-{
- $fHasOnline = $true
-}
-
-if ($fSfbIsOnline)
-{
- try {
- Import-Module SkypeOnlineConnector
- }
- catch
- {
- CleanupAndFail "To verify Skype for Business in online tenants you need the Lync Online Connector module from https://www.microsoft.com/download/details.aspx?id=39366"
- }
-}
-else
-{
- $credSfb = (Get-Credential -Message "Please enter Skype for Business admin credentials")
-}
-
-if ($fHasOnline)
-{
- $credSfb = $credEx
- try {
- Import-Module MSOnline
- }
- catch
- {
- CleanupAndFail "To verify accounts in online tenants you need the Azure Active Directory module for PowerShell from https://go.microsoft.com/fwlink/p/?linkid=236297"
- }
-}
-
-PrintAction "Connecting to Exchange Powershell Session..."
-[System.Management.Automation.Runspaces.AuthenticationMechanism] $authType = [System.Management.Automation.Runspaces.AuthenticationMechanism]::Kerberos
-if ($fExIsOnline)
-{
- $authType = [System.Management.Automation.Runspaces.AuthenticationMechanism]::Basic
-}
-try
-{
- $sessEx = $null
- if ($fExIsOnline)
- {
- $sessEx = New-PSSession -ConfigurationName microsoft.exchange -Credential $credEx -AllowRedirection -Authentication $authType -ConnectionUri "https://outlook.office365.com/powershell-liveid/" -WarningAction SilentlyContinue
- }
- else
- {
- $sessEx = New-PSSession -ConfigurationName microsoft.exchange -Credential $credEx -AllowRedirection -Authentication $authType -ConnectionUri https://$strExServer/powershell -WarningAction SilentlyContinue
- }
-}
-catch
-{
-}
-
-if (!$sessEx)
-{
- CleanupAndFail "Connecting to Exchange Powershell failed, please validate your server is accessible and credentials are correct"
-}
-
-PrintSuccess "Connected to Exchange Powershell Session"
-
-PrintAction "Connecting to Skype for Business Powershell Session..."
-
-if ($fSfbIsOnline)
-{
- $sessSfb = New-CsOnlineSession -Credential $credSfb
-}
-else
-{
- $sessSfb = New-PSSession -Credential $credSfb -ConnectionURI "https://$strRegistrarPool/OcsPowershell" -AllowRedirection -WarningAction SilentlyContinue
-}
-
-if (!$sessSfb)
-{
- CleanupAndFail "Connecting to Skype for Business Powershell failed, please validate your server is accessible and credentials are correct"
-}
-
-PrintSuccess "Connected to Skype for Business Powershell"
-
-if ($fHasOnline)
-{
- $credMsol = $null
- if ($fExIsOnline)
- {
- $credMsol = $credEx
- }
- elseif ($fSfbIsOnline)
- {
- $credMsol = $credSfb
- }
- else
- {
- CleanupAndFail "Internal error - could not determine MS Online credentials"
- }
- try
- {
- PrintAction "Connecting to Azure Active Directory Services..."
- Connect-MsolService -Credential $credMsol
- PrintSuccess "Connected to Azure Active Directory Services"
- }
- catch
- {
- # This really shouldn't happen unless there is a network error
- CleanupAndFail "Failed to connect to MSOnline"
- }
-}
-
-
-PrintAction "Importing remote sessions into the local session..."
-try
-{
- $importEx = Import-PSSession $sessEx -AllowClobber -WarningAction SilentlyContinue -DisableNameChecking
- $importSfb = Import-PSSession $sessSfb -AllowClobber -WarningAction SilentlyContinue -DisableNameChecking
-}
-catch
-{
-}
-if (!$importEx -or !$importSfb)
-{
- CleanupAndFail "Import failed"
-}
-PrintSuccess "Import successful"
-
-
-$mailbox = $null
-try
-{
- $mailbox = Get-Mailbox -Identity $strUpn
-}
-catch
-{
-}
-
-if (!$mailbox)
-{
- CleanupAndFail "Account exists check failed. Unable to find the mailbox for $strUpn - please make sure the Exchange account exists on $strExServer"
-}
-
-$exchange = $null
-if (!$fExIsOnline)
-{
- $exchange = Get-ExchangeServer
- if (!$exchange -or !$exchange.IsE14OrLater)
- {
- CleanupAndFail "A compatible exchange server version was not found. Please use at least exchange 2010."
- }
-}
-
-
-$strAlias = $mailbox.UserPrincipalName
-$strDisplayName = $mailbox.DisplayName
-
-$strLinkedAccount = $strLinkedDomain = $strLinkedUser = $strLinkedServer = $null
-$credLinkedDomain = $Null
-if (!$fExIsOnline -and ![System.String]::IsNullOrEmpty($mailbox.LinkedMasterAccount) -and !$mailbox.LinkedMasterAccount.EndsWith("\SELF"))
-{
- $strLinkedAccount = $mailbox.LinkedMasterAccount
- $strLinkedDomain = $strLinkedAccount.substring(0,$strLinkedAccount.IndexOf('\'))
- $strLinkedUser = $strLinkedAccount.substring($strLinkedAccount.IndexOf('\') + 1)
- $strLinkedServer = Read-Host "What is the domain controller for the $strLinkedDomain"
- $credLinkedDomain = (Get-Credential -Message "Please provide credentials for $strLinkedDomain")
-}
-
-
-
-
-
-
-
-Write-Host
-Write-Host
-Write-Host
-PrintAction "Performing verification checks on $strDisplayName..."
-$Global:iTotalFailures = 0
-$global:iTotalWarnings = 0
-$Global:iTotalPasses = 0
-
-function Validate()
-{
- Param(
- [string]$Test,
- [bool] $Condition,
- [string]$FailureMsg,
- [switch]$WarningOnly
- )
-
- Write-Host -NoNewline -ForegroundColor White $Test.PadRight(100,'.')
- if ($Condition)
- {
- Write-Host -ForegroundColor Green "Passed"
- $global:iTotalPasses++
- }
- else
- {
- if ($WarningOnly)
- {
- Write-Host -ForegroundColor Yellow ("Warning: "+$FailureMsg)
- $global:iTotalWarnings++
- }
- else
- {
- Write-Host -ForegroundColor Red ("Failed: "+$FailureMsg)
- $global:iTotalFailures++
- }
- }
-}
-
-## Exchange ##
-
-Validate -WarningOnly -Test "The mailbox $strUpn is enabled as a room account" -Condition ($mailbox.RoomMailboxAccountEnabled -eq $True) -FailureMsg "RoomMailboxEnabled - without a device account, the Surface Hub will not be able to use various key features."
-$calendarProcessing = Get-CalendarProcessing -Identity $strUpn -WarningAction SilentlyContinue -ErrorAction SilentlyContinue
-Validate -Test "The mailbox $strUpn is configured to accept meeting requests" -Condition ($calendarProcessing -ne $null -and $calendarProcessing.AutomateProcessing -eq 'AutoAccept') -FailureMsg "AutomateProcessing - the Surface Hub will not be able to send mail or sync its calendar."
-Validate -WarningOnly -Test "The mailbox $strUpn will not delete meeting comments" -Condition ($calendarProcessing -ne $null -and !$calendarProcessing.DeleteComments) -FailureMsg "DeleteComments - the Surface Hub may be missing some meeting information on the welcome screen and Skype."
-Validate -WarningOnly -Test "The mailbox $strUpn keeps private meetings private" -Condition ($calendarProcessing -ne $null -and !$calendarProcessing.RemovePrivateProperty) -FailureMsg "RemovePrivateProperty - the Surface Hub will make show private meetings."
-Validate -Test "The mailbox $strUpn keeps meeting subjects" -Condition ($calendarProcessing -ne $null -and !$calendarProcessing.DeleteSubject) -FailureMsg "DeleteSubject - the Surface Hub will not keep meeting subject information."
-Validate -WarningOnly -Test "The mailbox $strUpn does not prepend meeting organizers to subjects" -Condition ($calendarProcessing -ne $null -and !$calendarProcessing.AddOrganizerToSubject) -FailureMsg "AddOrganizerToSubject - the Surface Hub will not display meeting subjects as intended."
-
-if ($fExIsOnline)
-{
- #No online specifics
-}
-else
-{
- #No onprem specifics
-}
-
-#ActiveSync
-$casMailbox = Get-Casmailbox $strUpn -WarningAction SilentlyContinue -ErrorAction SilentlyContinue
-Validate -Test "The mailbox $strUpn has a mailbox policy" -Condition ($casMailbox -ne $null) -FailureMsg "PasswordEnabled - unable to find policy - the Surface Hub will not be able to send mail or sync its calendar."
-if ($casMailbox)
-{
- $policy = $null
- if ($fExIsOnline -or $exchange.IsE15OrLater)
- {
- $strPolicy = $casMailbox.ActiveSyncMailboxPolicy
- $policy = Get-MobileDeviceMailboxPolicy -Identity $strPolicy -WarningAction SilentlyContinue -ErrorAction SilentlyContinue
- Validate -Test "The policy $strPolicy does not require a device password" -Condition ($policy.PasswordEnabled -ne $True) -FailureMsg "PasswordEnabled - policy requires a device password - the Surface Hub will not be able to send mail or sync its calendar."
- }
- else
- {
- $strPolicy = $casMailbox.ActiveSyncMailboxPolicy
- $policy = Get-ActiveSyncMailboxPolicy -Identity $strPolicy -WarningAction SilentlyContinue -ErrorAction SilentlyContinue
- Validate -Test "The policy $strPolicy does not require a device password" -Condition ($policy.PasswordEnabled -ne $True) -FailureMsg "PasswordEnabled - policy requires a device password - the Surface Hub will not be able to send mail or sync its calendar."
- }
-
- if ($policy -ne $null)
- {
- Validate -Test "The policy $strPolicy allows non-provisionable devices" -Condition ($policy.AllowNonProvisionableDevices -eq $null -or $policy.AllowNonProvisionableDevices -eq $true) -FailureMsg "AllowNonProvisionableDevices - policy will not allow the SurfaceHub to sync"
- }
-
-}
-
-
-# Check the default access level
-$orgSettings = Get-ActiveSyncOrganizationSettings
-$strDefaultAccessLevel = $orgSettings.DefaultAccessLevel
-Validate -Test "ActiveSync devices are allowed" -Condition ($strDefaultAccessLevel -eq 'Allow') -FailureMsg "DeviceType Windows Mail is accessible - devices are not allowed by default - the surface hub will not be able to send mail or sync its calendar."
-
-# Check if there exists a device access rule that bans the device type Windows Mail
-$blockingRules = Get-ActiveSyncDeviceAccessRule | where {($_.AccessLevel -eq 'Block' -or $_.AccessLevel -eq 'Quarantine') -and $_.Characteristic -eq 'DeviceType'-and $_.QueryString -eq 'WindowsMail'}
-Validate -Test "Windows mail devices are not blocked or quarantined" -Condition ($blockingRules -eq $null -or $blockingRules.Length -eq 0) -FailureMsg "DeviceType Windows Mail is accessible - devices are blocked or quarantined - the surface hub will not be able to send mail or sync its calendar."
-
-## End Exchange ##
-
-
-
-## SfB ##
-$strLyncIdentity = $null
-if ($fSfbIsOnline)
-{
- $strLyncIdentity = $strUpn
-}
-else
-{
- $strLyncIdentity = $strAlias
-}
-
-$lyncAccount = $null
-try {
- $lyncAccount = Get-CsMeetingRoom -Identity $strLyncIdentity -WarningAction SilentlyContinue -ErrorAction SilentlyContinue
-} catch {
- try {
- $lyncAccount = Get-CsUser -Identity $strLyncIdentity -WarningAction SilentlyContinue -ErrorAction SilentlyContinue
- } catch { }
-}
-Validate -Test "There is a Lync or Skype for Business account for $strLyncIdentity" -Condition ($lyncAccount -ne $null -and $lyncAccount.Enabled) -FailureMsg "SfB Enabled - there is no Skype for Business account - meetings will not support Skype for Business"
-if ($lyncAccount)
-{
- Validate -Test "The meeting room has a SIP address" -Condition (![System.String]::IsNullOrEmpty($lyncAccount.SipAddress)) -FailureMsg "SfB Enabled - there is no SIP Address - the device account cannot be used to sign into Skype for Business."
-}
-## End SFB ##
-
-
-if ($fHasOnline)
-{
- #License validation and password expiry
- $accountOnline = Get-MsolUser -UserPrincipalName $strUpn -WarningAction SilentlyContinue -ErrorAction SilentlyContinue
- Validate -Test "There is an online user account for $strUpn" -Condition ($accountOnline -ne $null) -FailureMsg "Could not find a Microsoft Online account for this user even though some services are online"
- if ($accountOnline)
- {
- Validate -Test "The password for $strUpn will not expire" -Condition ($accountOnline.PasswordNeverExpires -eq $True) -FailureMsg "PasswordNeverExpires - the admin will need to update the device account's password on the Surface Hub when it expires."
- if ($fIsSfbOnline -and !$fIsExOnline)
- {
- $strLicenseFailureMsg = "Has O365 license - The devices will not be able to use Skype for Business services."
- }
- elseif ($fIsExOnline -and !$fIsSfbOnline)
- {
- $strLicenseFailureMsg = "Has O365 license - The devices will not be able to use Exchange Online services."
- }
- else
- {
- $strLicenseFailureMsg = "Has O365 license - The devices will not be able to use Skype for Business or Exchange Online services."
- }
- Validate -Test "$strUpn is licensed" -Condition ($accountOnline.IsLicensed -eq $True) -FailureMsg $strLicenseFailureMsg
-
- Validate -Test "$strUpn is allowed to sign in" -Condition ($accountOnline.BlockCredential -ne $True) -FailureMsg "BlockCredential - This user is not allowed to sign in."
- }
-}
-
-#If there is an on-prem component, we can get the authoritative AD user from mailbox
-if ($fHasOnPrem)
-{
- $accountOnPrem = $null
- if ($strLinkedAccount)
- {
- $accountOnPrem = Get-AdUser $strLinkedUser -server $strLinkedServer -credential $credLinkedDomain -properties PasswordNeverExpires -WarningAction SilentlyContinue -ErrorAction SilentlyContinue
- }
- else
- {
- #AD User enabled validation
- $accountOnPrem = Get-AdUser $mailbox.UserPrincipalName -properties PasswordNeverExpires -WarningAction SilentlyContinue -ErrorAction SilentlyContinue
- }
- $strOnPremUpn = $accountOnPrem.UserPrincipalName
- Validate -Test "There is a user account for $strOnPremUpn" -Condition ($accountOnprem -ne $null) -FailureMsg "Could not find an Active Directory account for this user"
- if ($accountOnPrem)
- {
- Validate -WarningOnly -Test "The password for $strOnPremUpn will not expire" -Condition ($accountOnprem.PasswordNeverExpires -eq $True) -FailureMsg "PasswordNeverExpires - the admin will need to update the device account's password on the Surface Hub when it expires."
- Validate -Test "$strOnPremUpn is enabled" -Condition $accountOnPrem.Enabled -FailureMsg "AccountEnabled - this device account will not sign in"
- }
-}
-
-
-$global:iTotalTests = ($global:iTotalFailures + $global:iTotalPasses + $global:iTotalWarnings)
-
-Write-Host -NoNewline $global:iTotalTests "tests executed: "
-Write-Host -NoNewline -ForegroundColor Red $Global:iTotalFailures "failures "
-Write-Host -NoNewline -ForegroundColor Yellow $Global:iTotalWarnings "warnings "
-Write-Host -ForegroundColor Green $Global:iTotalPasses "passes "
-
-Cleanup
-```
-
-## Enable Skype for Business
-
-
-This script will enable Skype for Business on a device account. Use it only if Skype for Business wasn't previously enabled during account creation.
-
-```PowerShell
-## This script performs only the Enable for Skype for Business step on an account. It should only be run if this step failed in SHAccountCreate and the other steps have been completed ##
-# EnableSfb.ps1
-
-$Error.Clear()
-$ErrorActionPreference = "Stop"
-
-# Cleans up set state such as remote powershell sessions
-function Cleanup()
-{
- if ($sessCS)
- {
- Remove-PSSession $sessCS
- }
-}
-
-function PrintError($strMsg)
-{
- Write-Host $strMsg -foregroundcolor "red"
-}
-
-function PrintSuccess($strMsg)
-{
- Write-Host $strMsg -foregroundcolor "green"
-}
-
-# Cleans up and prints an error message
-function CleanupAndFail($strMsg)
-{
- if ($strMsg)
- {
- PrintError($strMsg);
- }
- Cleanup
- exit 1
-}
-
-# Exits if there is an error set and prints the given message
-function ExitIfError($strMsg)
-{
- if ($Error)
- {
- CleanupAndFail($strMsg);
- }
-}
-
-## Check dependencies ##
-
-$input = Read-Host "Is the account you wish to enable part of an online environment (enter O) or on-premises environment (enter P)"
-if ($input -eq "P")
-{
- $online = $false
-}
-elseif ($input -eq "O")
-{
- $online = $true
-}
-else
-{
- CleanupAndFail "Invalid selection"
-}
-if ($online)
-{
- try {
- Import-Module SkypeOnlineConnector
- }
- catch
- {
- PrintError "Some dependencies are missing"
- PrintError "Please install the Windows PowerShell Module for Lync Online. For more information go to https://www.microsoft.com/download/details.aspx?id=39366"
- PrintError "Please install the Azure Active Directory module for PowerShell from https://go.microsoft.com/fwlink/p/?linkid=236297"
- CleanupAndFail
- }
-}
-else
-{
- $strRegPool = Read-Host "Enter the FQDN of your Skype for Business Registrar Pool"
-}
-
-
-## Collect account data ##
-Write-Host "----------- Enter info for the account to enable -----------." -foregroundcolor "magenta"
-$strRoomUri=Read-Host 'Please enter the UPN of the account you are enabling (e.g. confroom@surfacehub.microsoft.com)'
-
-if ([System.String]::IsNullOrEmpty($strRoomUri))
-{
- CleanupAndFail "Please enter all of the requested data to continue."
- exit 1
-}
-Write-Host "--------------------------------------------------------------." -foregroundcolor "magenta"
-
-
-
-## Sign in to remote powershell for exchange and lync online ##
-Write-Host "`n------------------ Establishing connection -----------------." -foregroundcolor "magenta"
-$credAdmin=Get-Credential -Message "Enter credentials of a Skype for Business admin"
-if (!$credadmin)
-{
- CleanupAndFail("Valid admin credentials are required to create and prepare the account.");
-}
-Write-Host "Connecting to remote sessions. This can occasionally take a while - please do not enter input..."
-
-try
-{
- if ($online)
- {
- $sessCS = New-CsOnlineSession -Credential $credAdmin
- }
- else
- {
- $sessCS = New-PSSession -Credential $credAdmin -ConnectionURI "https://$strRegPool/OcsPowershell" -AllowRedirection -WarningAction SilentlyContinue
- }
-}
-catch
-{
- CleanupAndFail("Failed to connect to Skype for Business server. Please check your credentials and try again. Error message: $_")
-}
-
-Import-PSSession $sessCS -AllowClobber
-
-
-Write-Host "--------------------------------------------------------------." -foregroundcolor "magenta"
-
-# Getting registrar pool
-if ($online)
-{
- try {
- $strRegPool = $null;
- $strRegPool = (Get-CsTenant).RegistrarPool
- } catch {}
- if ($Error)
- {
- $Error.Clear();
- $strRegPool = "";
- Write-Host "We failed to lookup your Skype for Business Registrar Pool, but you can still enter it manually"
- }
- else
- {
- $strRegPool = $strRegPool[0].Substring($strRegPool[0].IndexOf(':') + 1)
- }
-}
-
-
-$Error.Clear()
-try {
- Enable-CsMeetingRoom -Identity $strRoomUri -RegistrarPool $strRegPool -SipAddressType EmailAddress
-}
-catch {}
-
-ExitIfError("Failed to setup Skype for Business meeting room")
-
-PrintSuccess "Successfully enabled $strRoomUri as a Skype for Business meeting room"
-
-Cleanup
-```
-
-## Useful cmdlets
-
-
-### Creating a Surface Hub-compatible ActiveSync policy
-
-For Surface Hub to use Exchange services, a device account configured with a compatible ActiveSync policy must be provisioned on the device. This policy has the following requirements:
-
-``` syntax
-PasswordEnabled == 0
-```
-
-In the following cmdlets, `$strPolicy` is the name of the ActiveSync policy, and `$strRoomUpn` is the UPN of the device account you want to apply the policy to.
-
-Note that in order to run the cmdlets, you need to set up a remote PowerShell session and:
-
-- Your admin account must be remote-PowerShell-enabled. This allows the admin to use the PowerShell cmdlets that are needed by the script. (This permission can be set using `set-user $admin -RemotePowerShellEnabled $true`)
-- Your admin account must have the "Reset Password" role if you plan to run the creation scripts. This allows the admin to change the password of the account, which is needed for the script. The Reset Password Role can be enabled using the Exchange Admin Center.
-
-Create the policy.
-
-```PowerShell
-# Create new policy with PasswordEnabled == false
-New-MobileDeviceMailboxPolicy -Name $strPolicy -PasswordEnabled $false –AllowNonProvisionableDevices $true
-```
-
-To apply the policy, the mailbox cannot be a room type, so it has to be converted into a user first.
-
-```PowerShell
-# Convert user to regular type
-Set-Mailbox $strRoomUpn -Type Regular
-# Set policy for account
-Set-CASMailbox $strRoomUpn -ActiveSyncMailboxPolicy $strPolicy
-```
-
-Now the device account just needs to be converted back into a room type.
-
-```PowerShell
-# Convert back to room mailbox
-Set-Mailbox $strRoomUpn -Type Room
-```
-
-### Allowing device IDs for ActiveSync
-
-To allow an account `$strRoomUpn`, run the following command:
-
-```PowerShell
-Set-CASMailbox –Identity $strRoomUpn –ActiveSyncAllowedDeviceIDs “”
-```
-
-To find a device's ID, run:
-
-```PowerShell
-Get-ActiveSyncDevice -Mailbox $strRoomUpn
-```
-
-This retrieves device information for every device that the account has been provisioned on, Including the `DeviceId` property.
-
-### Auto-accepting and declining meeting requests
-
-For a device account to automatically accept or decline meeting requests based on its availability, the **AutomateProcessing** attribute must be set to **AutoAccept**. This is recommended as to prevent overlapping meetings.
-
-```PowerShell
-Set-CalendarProcessing $strRoomUpn -AutomateProcessing AutoAccept
-```
-
-### Accepting external meeting requests
-
-For a device account to accept external meeting requests (a meeting request from an account not in the same tenant/domain), the device account must be set to allow processing of external meeting requests. Once set, the device account will automatically accept or decline meeting requests from external accounts as well as local accounts.
-
->**Note** If the **AutomateProcessing** attribute is not set to **AutoAccept**, then setting this will have no effect.
-
-
-
-```PowerShell
-Set-CalendarProcessing $strRoomUpn -ProcessExternalMeetingMessages $true
-```
-
-
-
-
-
-
-
-
-
diff --git a/devices/surface-hub/apply-activesync-policies-for-surface-hub-device-accounts.md b/devices/surface-hub/apply-activesync-policies-for-surface-hub-device-accounts.md
deleted file mode 100644
index 66dd43f75c..0000000000
--- a/devices/surface-hub/apply-activesync-policies-for-surface-hub-device-accounts.md
+++ /dev/null
@@ -1,44 +0,0 @@
----
-title: Applying ActiveSync policies to device accounts (Surface Hub)
-description: The Microsoft Surface Hub's device account uses ActiveSync to sync mail and calendar. This allows people to join and start scheduled meetings from the Surface Hub, and allows them to email any whiteboards they have made during their meeting.
-ms.assetid: FAABBA74-3088-4275-B58E-EC1070F4D110
-ms.reviewer:
-manager: laurawi
-keywords: Surface Hub, ActiveSync policies
-ms.prod: surface-hub
-ms.sitesec: library
-author: dansimp
-ms.author: dansimp
-ms.topic: article
-ms.date: 06/20/2019
-ms.localizationpriority: medium
----
-
-# Applying ActiveSync policies to device accounts (Surface Hub)
-
-
-The Microsoft Surface Hub's device account uses ActiveSync to sync mail and calendar. This allows people to join and start scheduled meetings from the Surface Hub, and allows them to email any whiteboards they have made during their meeting.
-
-For these features to work, the ActiveSync policies for your organization must be configured as follows:
-
-- There can't be any global policies that block synchronization of the resource mailbox that's being used by the Surface Hub’s device account. If there is such a blocking policy, you need to whitelist the Surface Hub as an allowed device.
-- You must set a mobile device mailbox policy where the **PasswordEnabled** setting is set to False. Other mobile device mailbox policy settings are not compatible with the Surface Hub.
-
-## Whitelisting the DeviceID
-
-
-Your organization may have a global policy that prevents syncing of device accounts provisioned on Surface Hubs. To configure this property, see [Allowing device IDs for ActiveSync](appendix-a-powershell-scripts-for-surface-hub.md#whitelisting-device-ids-cmdlet).
-
-## Setting PasswordEnabled
-
-
-The device account must have an ActiveSync policy where the **PasswordEnabled** attribute is set to False or 0. To configure this property, see [Creating a Surface Hub-compatible Microsoft Exchange ActiveSync policy](appendix-a-powershell-scripts-for-surface-hub.md#create-compatible-as-policy).
-
-
-
-
-
-
-
-
-
diff --git a/devices/surface-hub/breadcrumb/toc.yml b/devices/surface-hub/breadcrumb/toc.yml
deleted file mode 100644
index d846a15189..0000000000
--- a/devices/surface-hub/breadcrumb/toc.yml
+++ /dev/null
@@ -1,7 +0,0 @@
-- name: Docs
- tocHref: /
- topicHref: /
- items:
- - name: Surface Hub
- tocHref: /surface-hub
- topicHref: /surface-hub/index
\ No newline at end of file
diff --git a/devices/surface-hub/change-history-surface-hub.md b/devices/surface-hub/change-history-surface-hub.md
deleted file mode 100644
index 77ce204725..0000000000
--- a/devices/surface-hub/change-history-surface-hub.md
+++ /dev/null
@@ -1,195 +0,0 @@
----
-title: Change history for Surface Hub
-ms.reviewer:
-manager: laurawi
-description: This topic lists new and updated topics for Surface Hub.
-keywords: change history
-ms.prod: surface-hub
-ms.sitesec: library
-author: dansimp
-ms.author: dansimp
-ms.topic: article
-ms.localizationpriority: medium
----
-
-# Change history for Surface Hub
-
-This topic lists new and updated topics in the [Surface Hub Admin Guide]( surface-hub-administrators-guide.md).
-
-## April 2019
-
-New or changed topic | Description
---- | ---
-[Surface Hub Site Readiness Guide](surface-hub-site-readiness-guide.md) | New; previously available for download only
-[Technical information for 55” Microsoft Surface Hub](surface-hub-technical-55.md) | New; previously available for download and on [Surface Hub Tech Spec](https://support.microsoft.com/help/4483539/surface-hub-tech-spec)
-[Technical information for 84” Microsoft Surface Hub](surface-hub-technical-84.md) | New; previously available for download and on [Surface Hub Tech Spec](https://support.microsoft.com/help/4483539/surface-hub-tech-spec)
-[Surface Hub SSD replacement](surface-hub-ssd-replacement.md) | New; previously available for download only
-[Implement Quality of Service on Surface Hub](surface-hub-qos.md) | New
-
-## July 2018
-
-New or changed topic | Description
---- | ---
-[Set up and use Whiteboard to Whiteboard collaboration](whiteboard-collaboration.md) | Added information and links for new Microsoft Whiteboard app release.
-
-## June 2018
-
-New or changed topic | Description
---- | ---
-[On-premises deployment (single forest)](on-premises-deployment-surface-hub-device-accounts.md) and [On-premises deployment (multiple forests)](on-premises-deployment-surface-hub-multi-forest.md) | Added (prerelease) instructions for disabling anonymous email and IM.
-
-## May 2018
-
-New or changed topic | Description
---- | ---
-[Using the Surface Hub Recovery Tool](surface-hub-recovery-tool.md) | New
-
-## April 2018
-
-New or changed topic | Description
---- | ---
-[Hybrid deployment](hybrid-deployment-surface-hub-device-accounts.md) | Updated instructions for Skype for Business Hybrid.
-
-
-## March 2018
-
-New or changed topic | Description
---- | ---
-[Create and test a device account (Surface Hub)](create-and-test-a-device-account-surface-hub.md) | Added section for account verification and testing, with link to new Surface Hub Hardware Diagnostic app.
-
-## February 2018
-
-New or changed topic | Description
---- | ---
-[Manage settings with an MDM provider (Surface Hub)](manage-settings-with-mdm-for-surface-hub.md) | Updated instructions for custom settings using Microsoft Intune.
-[Hybrid deployment](hybrid-deployment-surface-hub-device-accounts.md) | Updated instructions and scripts.
-| [Online deployment](online-deployment-surface-hub-device-accounts.md) | Updated instructions and scripts.
-
-## January 2018
-
-New or changed topic | Description
---- | ---
-[Configure Surface Hub Start menu](surface-hub-start-menu.md) | New
-[PowerShell for Surface Hub](appendix-a-powershell-scripts-for-surface-hub.md) | Added prerequisites for running the scripts
-
-## November 2017
-
-New or changed topic | Description
---- | ---
-[Enable 802.1x wired authentication](enable-8021x-wired-authentication.md) | New
-[Manage settings with an MDM provider (Surface Hub)](manage-settings-with-mdm-for-surface-hub.md) | Added settings for 802.1x wired authentication.
-
-## October 2017
-
-New or changed topic | Description |
---- | ---
-[Install apps on your Microsoft Surface Hub](install-apps-on-surface-hub.md) | Updated instructions to use Windows Team device family
-[Hybrid deployment](hybrid-deployment-surface-hub-device-accounts.md) | Updated the instructions for Exchange on-premises
-[Create a device account using UI](create-a-device-account-using-office-365.md) | Updated the instructions
-[Differences between Surface Hub and Windows 10 Enterprise](differences-between-surface-hub-and-windows-10-enterprise.md) | Clarified user sign-in on Surface Hub
-[Set up and use Whiteboard to Whiteboard collaboration](whiteboard-collaboration.md) | Removed **How to control and manage Whiteboard to Whiteboard collaboration** due to issues with the EnterpriseModernAppmanagement CSP losing state during End Session.
-| [Manage settings with an MDM provider (Surface Hub)](manage-settings-with-mdm-for-surface-hub.md) | Removed settings for managing Whiteboard collaboration. |
-[Top support solutions for Surface Hub](support-solutions-surface-hub.md) | Added link to Surface Hub warranty information
-
-
-## September 2017
-
-New or changed topic | Description
---- | ---
-[Top support solutions for Surface Hub](support-solutions-surface-hub.md) | New
-[PowerShell for Surface Hub](appendix-a-powershell-scripts-for-surface-hub.md) | Updated account creation scripts
-
-## August 2017
-
-
-| New or changed topic | Description |
-| --- | --- |
-[Accessibility](accessibility-surface-hub.md) | Added information about Narrator
-[Sign in to Surface Hub with Microsoft Authenticator](surface-hub-authenticator-app.md) | New
-
-
-
-
-
-## July 2017
-
-| New or changed topic | Description |
-| --- | --- |
-| [Windows updates](manage-windows-updates-for-surface-hub.md) | Changed deferral recommendations for Windows Updates |
-| [Set up and use Whiteboard to Whiteboard collaboration](whiteboard-collaboration.md) | Added Whiteboard URLs to prerequisites |
-| [Hybrid deployment](hybrid-deployment-surface-hub-device-accounts.md#skype-for-business-online) | Updated the Skype for Business Online requirements |
-| [Prepare your environment for Surface Hub](prepare-your-environment-for-surface-hub.md) | Added that Surface Hub supports 802.1X using PEAP-MSCHAPv2 |
-
-## June 2017
-
-| New or changed topic | Description |
-| --- | --- |
-| [Set up and use Whiteboard to Whiteboard collaboration](whiteboard-collaboration.md) | New |
-| [Manage settings with an MDM provider (Surface Hub)](manage-settings-with-mdm-for-surface-hub.md) | Added settings for managing Whiteboard collaboration |
-
-## RELEASE: Windows 10, version 1703
-
-The topics in this library have been updated for Windows 10, version 1703 (also known as the Creators Update). The following new topics have been added:
-
-- [Miracast on existing wireless network or LAN](miracast-over-infrastructure.md)
-
->[Looking for the Surface Hub admin guide for Windows 10, version 1607?](https://download.microsoft.com/download/7/2/5/7252051B-7E97-4781-B5DF-58D4B1A4BB88/surface-hub-admin-guide-1607.pdf)
-
-
-## May 2017
-
-| New or changed topic | Description |
-| --- | --- |
-| [Online or hybrid deployment using Skype Hybrid Voice environment](skype-hybrid-voice.md) | New |
-
-
-## February 2017
-
-| New or changed topic | Description |
-| --- | --- |
-| [Useful downloads for Surface Hub administrators](surface-hub-downloads.md) | New |
-
-## January 2017
-
-| New or changed topic | Description |
-| --- | --- |
-| [How Surface Hub addresses Wi-Fi Direct security issues](surface-hub-wifi-direct.md) | New |
-| [On-premises deployment (multiple forests)](on-premises-deployment-surface-hub-multi-forest.md) | New |
-| [Connect other devices and display with Surface Hub](connect-and-display-with-surface-hub.md) | Added graphics cards verified to work with 84" Surface Hubs and added information about the lengths of cables. |
-| [Online deployment](online-deployment-surface-hub-device-accounts.md) | Updated procedures for adding a device account for your Microsoft Surface Hub when you have a pure, online deployment. |
-
-## December 2016
-
-| New or changed topic | Description|
-| --- | --- |
-| [Connect other devices and display with Surface Hub](connect-and-display-with-surface-hub.md) | Added information about Bluetooth accessories. |
-| [Manage settings with an MDM provider](manage-settings-with-mdm-for-surface-hub.md) | Updated example procedures to include screenshots. |
-
-## November 2016
-
-| New or changed topic | Description |
-| --- | --- |
-| [Differences between Surface Hub and Windows 10 Enterprise](differences-between-surface-hub-and-windows-10-enterprise.md) | New |
-| [Connect other devices and display with Surface Hub](connect-and-display-with-surface-hub.md) | Added information for Video Out and a table to help select a display method. |
-| [Hybrid deployment](hybrid-deployment-surface-hub-device-accounts.md) | Added instructions for creating accounts for Surface Hub in a Skype for Business hybrid environment. |
-
-
-
-## RELEASE: Windows Anniversary Update for Surface Hub (Windows 10, version 1607)
-The topics in this library have been updated for Windows 10, version 1607 (also known as Windows Anniversary Update for Surface Hub). These topics had significant updates for this release:
-- [Windows Updates (Surface Hub)](manage-windows-updates-for-surface-hub.md)
-- [Manage settings with an MDM provider (Surface Hub)](manage-settings-with-mdm-for-surface-hub.md)
-- [Monitor your Microsoft Surface Hub](monitor-surface-hub.md)
-- [Create provisioning packages (Surface Hub)](provisioning-packages-for-certificates-surface-hub.md)
-- [Install apps on your Microsoft Surface Hub](install-apps-on-surface-hub.md)
-- [Device reset (Surface Hub)](device-reset-surface-hub.md)
-
-## October 2016
-| New or changed topic | Description |
-| --- | --- |
-| [Admin group management (Surface Hub)](admin-group-management-for-surface-hub.md) |Add note about automatic enrollment, and update table. |
-| [Password management (Surface Hub)](password-management-for-surface-hub-device-accounts.md) | Updates to content. |
-| [Create and test a device account (Surface Hub)](create-and-test-a-device-account-surface-hub.md) | Reorganize and streamline guidance on creating a device account. |
-| [Introduction to Surface Hub](intro-to-surface-hub.md) | Move Surface Hub dependencies table to [Prepare your environment for Surface Hub](prepare-your-environment-for-surface-hub.md). |
-| [Prepare your environment for Surface Hub](prepare-your-environment-for-surface-hub.md) | Add dependency table and reorganize topic. |
-| [Local management for Surface Hub settings](local-management-surface-hub-settings.md) | New topic. |
diff --git a/devices/surface-hub/change-surface-hub-device-account.md b/devices/surface-hub/change-surface-hub-device-account.md
deleted file mode 100644
index d20e57a184..0000000000
--- a/devices/surface-hub/change-surface-hub-device-account.md
+++ /dev/null
@@ -1,93 +0,0 @@
----
-title: Change the Microsoft Surface Hub device account
-description: You can change the device account in Settings to either add an account if one was not already provisioned, or to change any properties of an account that was already provisioned.
-ms.assetid: AFC43043-3319-44BC-9310-29B1F375E672
-ms.reviewer:
-manager: laurawi
-keywords: change device account, change properties, Surface Hub
-ms.prod: surface-hub
-ms.sitesec: library
-author: dansimp
-ms.author: dansimp
-ms.topic: article
-ms.date: 07/27/2017
-ms.localizationpriority: medium
----
-
-# Change the Microsoft Surface Hub device account
-
-
-You can change the device account in Settings to either add an account if one was not already provisioned, or to change any properties of an account that was already provisioned.
-
-## Details
-
-
-
-
-
-
-
-
-
-
Value
-
Description
-
-
-
-
-
User Principal Name
-
The user principal name (UPN) of the device account.
-
-
-
Password
-
The corresponding password of the device account.
-
-
-
Domain
-
The domain that the device account belongs to. This field does not need to be provided for Office 365 accounts.
-
-
-
User name
-
The user name of the device account. This field does not need to be provided for Office 365 accounts.
-
-
-
Session Initiation Protocol (SIP) address
-
The SIP address of the device account.
-
-
-
Microsoft Exchange server
-
This is the Exchange server of the device account. The device account’s username and password must be able to authenticate to the specified Exchange server.
-
-
-
Enable Exchange services
-
When checked, all Exchange services will be enabled (for example, calendar on the welcome screen, emailing whiteboards). When not checked, all Exchange services will be disabled, and the Exchange server does not need to be provided.
-
-
-
-
-
-
-## What happens?
-
-
-The UPN and password are used to validate the account in AD or Azure AD. If the validation fails, you may need to provide the domain and user name.
-
-Using the credentials provided, we will try to discover the SIP address. If a SIP address can't be found, then Skype for Business will use the UPN as the SIP address. If this is not the SIP address for the account, you will need to provide the SIP address.
-
-The Exchange server address will need to be provided if the device can't find a server associated with the login credentials. Microsoft Surface Hub will use the Exchange server to talk to ActiveSync, which enables several key features on the device.
-
-## Related topics
-
-
-[Manage Microsoft Surface Hub](manage-surface-hub.md)
-
-[Microsoft Surface Hub administrator's guide](surface-hub-administrators-guide.md)
-
-
-
-
-
-
-
-
-
diff --git a/devices/surface-hub/connect-and-display-with-surface-hub.md b/devices/surface-hub/connect-and-display-with-surface-hub.md
deleted file mode 100644
index d5f39c55db..0000000000
--- a/devices/surface-hub/connect-and-display-with-surface-hub.md
+++ /dev/null
@@ -1,494 +0,0 @@
----
-title: Connect other devices and display with Surface Hub
-description: You can connect other device to your Surface Hub to display content.
-ms.assetid: 8BB80FA3-D364-4A90-B72B-65F0F0FC1F0D
-ms.reviewer:
-manager: laurawi
-ms.prod: surface-hub
-ms.sitesec: library
-author: dansimp
-ms.author: dansimp
-ms.topic: article
-ms.date: 07/27/2017
-ms.localizationpriority: medium
----
-
-# Connect other devices and display with Surface Hub
-
-
-You can connect other devices to your Microsoft Surface Hub to display content. This topic describes the Guest Mode, Replacement PC Mode, and Video Out functionality available through wired connections, and also lists accessories that you can connect to Surface Hub using [Bluetooth](#bluetooth-accessories).
-
->[!NOTE]
->Surface Hub will use the video input that you select until a new connection is made, the existing connection is disrupted, or the Connect App is closed.
-
-## Which method should I choose?
-
-When connecting external devices and displays to a Surface Hub, there are several available options. The method you use will depend upon your scenario and needs.
-
-| When you want to: | Use this method: |
-| --- | --- |
-| Mirror the Surface Hub's display on another device. | [Video Out](#video-out) |
-| Present another device's display on the Surface Hub screen and interact with both the device's content and the built-in Surface Hub experience. | [Guest Mode](#guest-mode) |
-| Power the Surface Hub from an external Windows 10 PC, turning off the embedded computer of the Surface Hub. Cameras, microphones, speakers, and other peripherals, are sent to the external PC, in addition to pen and touch. | [Replacement PC Mode](#replacement-pc-mode) |
-
-
-## Guest Mode
-
-
-Guest Mode uses a wired connection, so people can display content from their devices to the Surface Hub. If the source device is Windows-based, that device can also provide Touchback and Inkback. Surface Hub's internal PC takes video and audio from the connected device and presents them on the Surface Hub. If Surface Hub encounters a High-Bandwidth Digital Content Protection (HDCP) signal, the source will be displayed as a black image. To display your content without violating HDCP requirements, use the keypad on the right side of the Surface Hub to directly choose the external source.
-
->[!NOTE]
->When an HDCP source is connected, use the side keypad to change source inputs.
-
-### Ports
-
-Use these ports on the Surface Hub for Guest Mode.
-
-
-
-
-
-
-
-
-
-
-
Interface
-
Type
-
Description
-
Capabilities
-
-
-
-
-
Display Port 1.1a
-
Video input
-
Guest input #1
-
-
Support simultaneous guest input display with guest input #2 and guest input #3 (one full resolution, two thumbnail).
-
HDCP compliant in bypass mode
-
Touchback enabled
-
-
-
-
HDMI 1.4
-
Video input
-
Guest input #2
-
-
Support simultaneous guest input display with guest input #1 and guest input #3 (one full resolution, two thumbnail).
-
HDCP compliant in bypass mode
-
Touchback enabled
-
-
-
-
VGA
-
Video input
-
Guest input #3
-
-
Support simultaneous guest input display with guest input #1 and guest input #2 (one full resolution, two thumbnail).
-
HDCP compliant in bypass mode
-
Touchback enabled
-
-
-
-
3.5 mm jack
-
Audio input
-
Analog audio input
-
-
Ingest into Surface Hub PC, usually with the VGA video input.
-
-
-
-
USB 2.0, type B
-
USB out
-
Touchback
-
-
Provides access to the HID input devices mouse, touch, keyboard, and stylus back to the guest PC.
-
-
-
-
-
-
-
-### Port locations
-
-These are the port connections used for Guest Mode on the 55" and 84" Surface Hubs.
-
-
-
-Wired port connections on 55" Surface Hub
-
-
-
-Wired port connections on 84" Surface Hub
-
-### Port enumeration
-
-When a Surface hub is connected to a guest computer with the wired connect USB port, a number of USB devices are discovered and configured. These peripheral devices are created for Touchback and Inkback. The peripheral devices can be viewed in Device Manager. Device Manager will show duplicate names for some devices.
-
-**Human interface devices**
-
-- HID-compliant consumer control device
-
-- HID-compliant pen
-
-- HID-compliant pen (duplicate item)
-
-- HID-compliant pen (duplicate item)
-
-- HID-compliant touch screen
-
-- USB Input Device
-
-- USB Input Device (duplicate item)
-
-**Keyboards**
-
-- Standard PS/2 keyboard
-
-**Mice and other pointing devices**
-
-- HID-compliant mouse
-
-**Universal serial bus controllers**
-
-- Generic USB hub
-
-- USB composite device
-
-### Guest Mode connectivity
-
-Your choice of video cable will be determined by what is available from your source input. The Surface Hub has three choices of video input: DisplayPort, HDMI, and VGA. See the following chart for available resolutions.
-
-
-
-
-
-
-
-
-
-
-
-
-
Signal Type
-
Resolution
-
Frame rate
-
HDMI - RGB
-
DisplayPort
-
VGA
-
-
-
-
-
PC
-
640 x 480
-
59.94/60
-
X
-
X
-
X
-
-
-
PC
-
720 x 480
-
59.94/60
-
X
-
X
-
-
-
-
PC
-
1024 x 768
-
60
-
X
-
X
-
X
-
-
-
HDTV
-
720p
-
59.94/60
-
X
-
X
-
X
-
-
-
HDTV
-
1080p
-
59.94/60
-
X
-
X
-
X
-
-
-
-
-
-
-Source audio is provided by DisplayPort and HDMI cables. If you must use VGA, Surface Hub has an audio input port that uses a 3.5 mm plug. Surface Hub also uses a USB cable that provides Touchback and Inkback from the Surface Hub to compatible Windows 10 devices. The USB cable can be used with any video input that is already connected with a cable.
-
-Someone using Guest Mode to connect a PC would use one of these options:
-
-**DisplayPort** -- DisplayPort cable and USB 2.0 cable
-
-**HDMI** -- HDMI cable and USB 2.0 cable
-
-**VGA** -- VGA cable, 3.5 mm audio cable, and USB 2.0 cable
-
-If the computer you are using for Guest Mode is not compatible with Touchback and Inkback, then you won't need the USB cable.
-
-## Replacement PC Mode
-
-
-In Replacement PC Mode, the embedded computer of the Surface Hub is turned off and an external PC is connected to the Surface Hub. Connections to replacement PC ports give access to key peripherals on the Surface Hub, including the screen, pen, and touch features. This does mean that your Surface Hub won’t have the benefit of the Windows Team experience, but you will have the flexibility offered by providing and managing your own Windows computer.
-
-### Software requirements
-
-You can run Surface Hub in Replacement PC Mode with 64-bit versions of Windows 10 Home, Windows 10 Pro, and Windows 10 Enterprise. You can download the [Surface Hub Replacement PC driver package](https://www.microsoft.com/download/details.aspx?id=52210) from the Microsoft Download Center. We recommend that you install these drivers on any computer you plan to use as a replacement PC.
-
-### Hardware requirements
-
-Surface Hub is compatible with a range of hardware. Choose the processor and memory confirmation for your replacement PC so that it supports the programs you'll be using. Your replacement PC hardware needs to support 64-bit versions of Windows 10.
-
-### Graphics adapter
-
-In Replacement PC Mode, Surface Hub supports any graphics adapter that can produce a DisplayPort signal. You'll improve your experience with a graphics adapter that can match Surface Hub's resolution and refresh rate. For example, the best and recommended replacement PC experience on the Surface Hub is with a 120Hz video signal.
-
-**55" Surface Hubs** - For best experience, use a graphics card capable of 1080p resolution at 120Hz.
-
-**84" Surface Hubs** - For best experience, use a graphics card capable of outputting four DisplayPort 1.2 streams to produce 2160p at 120Hz (3840 x 2160 at 120Hz vertical refresh). We've verified that this works with the NVIDIA Quadro K2200, NVIDIA Quadro K4200, NVIDIA Quadro M6000, AMD FirePro W5100, AMD FirePro W7100, and AMD FirePro W9100. These are not the only graphics cards - others are available from other vendors.
-
-Check directly with graphics card vendors for the latest drivers.
-
-
-
-
-
-### Ports
-
-Replacement PC ports on 55" Surface Hub
-
-
-
-
-
-
-
-
-
-
-
-
-
Description
-
Type
-
Interface
-
Details
-
-
-
-
-
PC video
-
Video input
-
DP 1.2
-
-
Full screen display of 1080p at 120 Hz, plus audio
-
HDCP compliant
-
-
-
-
Internal peripherals
-
USB output
-
USB 2.0 type B
-
-
Touch
-
Pen
-
Speakers
-
Microphone
-
Cameras
-
NFC sensor
-
Ambient light sensor
-
Passive infrared sensor
-
-
-
-
USB hub
-
USB output
-
USB 2.0 type B
-
-
Underneath USB ports
-
-
-
-
-
-
-
-Replacement PC ports on 84" Surface Hub
-
-
-
-
-
-
-
-
-
-
-
-
-
Description
-
Type
-
Interface
-
Details
-
-
-
-
-
PC video
-
Video input
-
DP 1.2 (2x)
-
-
Full screen display of 2160p at 120 Hz, plus audio
-
HDCP compliant
-
-
-
-
Internal peripherals
-
USB output
-
USB 2.0 type B
-
-
Touch
-
Pen
-
Speakers
-
Microphone
-
Cameras
-
NFC sensor
-
Ambient light sensor
-
Passive infrared sensor
-
-
-
-
USB hub
-
USB output
-
USB 2.0 type B
-
-
Underneath USB ports
-
-
-
-
-
-
-
-### Replacement PC setup instructions
-
-**To use Replacement PC Mode**
-
-1. Download and install the [Surface Hub Replacement PC driver package](https://www.microsoft.com/download/details.aspx?id=52210) on the replacement PC.
-
- >[!NOTE]
- >We recommend that you set sleep or hibernation on the replacement PC so the Surface Hub will turn off the display when it isn't being used.
-
-2. Turn off the Surface Hub using the power switch next to the power cable.
-
-3. Connect the cables from the Surface Hub's replacement PC ports to the replacement PC. These ports are usually covered by a removable plastic cover.
-
- 55" Surface Hub -- connect one DisplayPort cable, and two USB cables.
-
- 84" Surface Hub -- connect two DisplayPort cables, and two USB cables.
-
-4. Toggle the Mode switch to **Replacement PC**. The Mode switch is next to the Replacement PC ports.
-
-5. Turn on the Surface Hub using the power switch next to the power cable.
-
-6. Press the power button on the right side of the Surface Hub.
-
-You can switch the Surface Hub to use the internal PC.
-
-**To switch back to internal PC**
-
-1. Turn off the Surface Hub using the power switch next to the power cable.
-
-2. Toggle the Mode switch to Internal PC. The Mode switch is next to the Replacement PC ports.
-
-3. Turn on the Surface Hub using the power switch next to the power cable.
-
-
-## Video Out
-
-The Surface Hub includes a Video Out port for mirroring visual content from the Surface Hub to another display.
-
-### Ports
-
-Video Out port on the 55" Surface Hub
-
-
-
-Video Out port on the 84" Surface Hub
-
-
-
-
-
-
-
Description
-
Type
-
Interface
-
Capabilities
-
-
-
-
-
Video Output Mirror
-
Video Output
-
Video Output
-
-
Supports connection to a standard DisplayPort monitor (only supports an x4 Link displaying 1080p60 resolution at 24bpp)
-
Supports use with HDMI monitors (supporting 1080p60) by using a DisplayPort-to-HDMI adaptor
-
-
-
-
-
-## Cables
-
-Both the 55” and 84” Surface Hub devices have been tested to work with Certified DisplayPort and HDMI cables. While vendors do sell longer cables that may work with the Surface Hub, only those cables that have been certified by testing labs are certain to work with the Hub. For example, DisplayPort cables are certified only up to 3 meters, however many vendors sell cables that are 3 times that length. If a long cable is necessary, we strongly suggest using HDMI. HDMI has many cost-effective solutions for long-haul cables, including the use of repeaters. Nearly every DisplayPort source will automatically switch to HDMI signaling if a HDMI sink is detected.
-
-
-## Bluetooth accessories
-
-You can connect the following accessories to Surface Hub using Bluetooth:
-
-- Mice
-- Keyboards
-- Headsets
-- Speakers
-
->[!NOTE]
->After you connect a Bluetooth headset or speaker, you might need to change the [default microphone and speaker settings](local-management-surface-hub-settings.md).
diff --git a/devices/surface-hub/connect-app-in-surface-hub-unexpectedly-exits.md b/devices/surface-hub/connect-app-in-surface-hub-unexpectedly-exits.md
deleted file mode 100644
index 439d3c68d7..0000000000
--- a/devices/surface-hub/connect-app-in-surface-hub-unexpectedly-exits.md
+++ /dev/null
@@ -1,20 +0,0 @@
----
-title: What to do if the Connect app in Surface Hub exits unexpectedly
-description: Describes how to resolve an issue where the Connect app in Surface Hub exits to the Welcome screen after cycling through inputs.
-ms.assetid: 9576f4e4-d936-4235-8a03-d8a6fe9e8fec
-keywords: surface, hub, connect, input, displayport
-ms.prod: surface-hub
-ms.sitesec: library
-author: todmccoy
-ms.author: v-todmc
-ms.topic: article
-ms.localizationpriority: medium
----
-
-# What to do if the Connect app in Surface Hub exits unexpectedly
-
-At times, a wired Connect session that is started from the Welcome screen by connecting a DisplayPort input will exit back to the Welcome screen after using the side keypad or the source button to cycle through all source inputs.
-
-This is an issue in the Connect app and its default full-screen state. By changing the size of the app, or by selecting a DisplayPort input thumbnail in the Connect app, you can prevent input cycling from affecting the app.
-
-The way to resolve this issue is to first launch the Connect app from the Welcome screen, and THEN connect a DisplayPort input. If the input is already connected, manually select the thumbnail.
\ No newline at end of file
diff --git a/devices/surface-hub/create-a-device-account-using-office-365.md b/devices/surface-hub/create-a-device-account-using-office-365.md
deleted file mode 100644
index 29f9557045..0000000000
--- a/devices/surface-hub/create-a-device-account-using-office-365.md
+++ /dev/null
@@ -1,387 +0,0 @@
----
-title: Create a device account using UI (Surface Hub)
-description: If you prefer to use a graphical user interface, you can create a device account for your Microsoft Surface Hub with either the Office 365 UI or the Exchange Admin Center.
-ms.assetid: D11BCDC4-DABA-4B9A-9ECB-58E02CC8218C
-ms.reviewer:
-manager: laurawi
-keywords: create device account, Office 365 UI, Exchange Admin center, Microsoft 365 admin center, Skype for Business, mobile device mailbox policy
-ms.prod: surface-hub
-ms.sitesec: library
-author: dansimp
-ms.author: dansimp
-ms.topic: article
-ms.date: 05/04/2018
-ms.localizationpriority: medium
----
-
-# Create a device account using UI (Surface Hub)
-
-
-If you prefer to use a graphical user interface, you can create a device account for your Microsoft Surface Hub with either the [Office 365 UI](#create-device-acct-o365) or the [Exchange Admin Center](#create-device-acct-eac).
-
-## Create a device account using Office 365
-
-
-1. [Create the account in the Microsoft 365 Admin Center](#create-device-acct-o365-admin-ctr).
-2. [Create a mobile device mailbox (ActiveSync) policy from the Microsoft Exchange Admin Center](#create-device-acct-o365-mbx-policy).
-3. [Use PowerShell to complete device account creation](#create-device-acct-o365-complete-acct).
-4. [Use PowerShell to configure Exchange properties of the account](#create-device-acct-o365-configure-exch-prop).
-5. [Enable the account with Skype for Business](#create-device-acct-o365-skype-for-business).
-
-### Create the account in the admin center
-
-1. Sign in to Office 365 by visiting https://portal.office.com
-2. Provide the admin credentials for your Office 365 tenant. This will take you to your Microsoft 365 Admin Center.
-
- 
-
-3. In the admin center, navigate to **Resources** in the left panel, and then click **Rooms & equipment**.
-
- 
-
-4. Click **Add** to create a new Room account. Enter a display name and email address for the account, and then click **Add**.
-
- 
-
-5. Select the Room account you just created in the Active Users list. In the right panel, you can see the account properties and several optional actions. Click **Reset password** to change the password, and unselect **Make this user change their password when they first sign in**, because it is not possible to change the password from the Surface Hub sign-in flow.
-
-6. In the **Assigned license** section, click **Edit**, and then click the dropdown arrow next to the appropriate license to expand the details. Select a user location, and in the list of licenses, toggle on **Skype for Business Online (Plan 2)**, and then click **Save**. The license may vary depending on your organization (for example, you might have Plan 2 or Plan 3).
-
-### Create a mobile device mailbox (ActiveSync) policy from the Exchange Admin Center
-
-1. In the admin center’s left panel, click **ADMIN**, and then click **Exchange**.
-
- 
-
-2. This will open another tab on your browser to take you to the Exchange Admin Center, where you can create and set the Mailbox Setting for Surface Hub.
-
- 
-
-3. To create a Mobile Device Mailbox Policy, click **Mobile** from the left panel and then click **Mobile device mailbox policies**. Surface Hubs require an account with a mobile device mailbox policy that does not require a password, so if you already have an existing policy that matches this requirement, you can apply that policy to the account. Otherwise use the following steps to create a new one to be used only for Surface Hub device accounts.
-
- 
-
-4. To create a New Surface Hub mobile device mailbox policy, click the **+** button from the controls above the list of policies to add a new policy. For the name, provide a name that will help you distinguish this policy from other device accounts (for example, *SurfaceHubDeviceMobilePolicy*). Make sure the policy does not require a password for the devices assigned to, so make sure **Require a Password** remains unchecked, then click **Save**.
-
- 
-
-5. After you have created the new mobile device mailbox policy, go back to the **Exchange Admin Center** and you will see the new policy listed.
-
- 
-
-
-
-### Use PowerShell to complete device account creation
-
-From here on, you'll need to finish the account creation process using PowerShell to set up some configuration.
-
-In order to run cmdlets used by these PowerShell scripts, the following must be installed for the admin PowerShell console:
-
-- [Microsoft Online Services Sign-In Assistant for IT Professionals RTW](https://www.microsoft.com/download/details.aspx?id=41950)
-- [Windows Azure Active Directory Module for Windows PowerShell](https://www.microsoft.com/web/handlers/webpi.ashx/getinstaller/WindowsAzurePowershellGet.3f.3f.3fnew.appids)
-- [Skype for Business Online, Windows PowerShell Module](https://www.microsoft.com/download/details.aspx?id=39366)
-
-Install the following module in Powershell
-``` syntax
- install-module AzureAD
- Install-module MsOnline
-```
-
-### Connecting to online services
-
-1. Run Windows PowerShell as Administrator.
-
- 
-
-2. Create a Credentials object, then create a new session that connects to Skype for Business Online, and provide the global tenant administrator account, then click **OK**.
-
- 
-
-3. To connect to Microsoft Online Services, run:
-
- ``` syntax
- Connect-MsolService -Credential $Cred
- ```
-
- 
-
-4. Now to connect to Skype for Business Online Services, run:
-
- ``` syntax
- $sfbsession = New-CsOnlineSession -Credential $cred
- ```
-
- 
-
-5. Finally, to connect to Exchange Online Services, run:
-
- ``` syntax
- $exchangeSession = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri "https://outlook.office365.com/powershell-liveid/" -Credential $cred -Authentication "Basic" –AllowRedirection
- ```
-
- 
-
-6. Now you have to import the Skype for Business Online Session and the Exchange Online session you have just created, which will import the Exchange and Skype Commands so you can use them locally.
-
- ``` syntax
- Import-PSSession $exchangesession -AllowClobber -WarningAction SilentlyContinue
- Import-PSSession $sfbsession -AllowClobber -WarningAction SilentlyContinue
- ```
-
- Note that this could take a while to complete.
-
- 
-
-7. Once you’re connected to the online services you need to run a few more cmdlets to configure this account as a Surface Hub device account.
-
-### Use PowerShell to configure Exchange properties of the account
-
-Now that you're connected to the online services, you can finish setting up the device account. You'll use the device account email address to:
-
-- Change the mailbox type from regular to room.
-- Set the password and enable the room mailbox account
-- Change various Exchange properties
-- Set the user account password to never expire.
-
-1. You’ll need to enter the account’s mail address and create a variable with that value:
-
- ```powershell
- $mailbox = (Get-Mailbox )
- ```
-
- To store the value get it from the mailbox:
-
- ```powershell
- $strEmail = $mailbox.WindowsEmailAddress
- ```
-
- Print the value:
-
- ```powershell
- $strEmail
- ```
-
- You will see the correct email address.
-
- 
-
-2. Run the following cmdlet:
-
- ```powershell
- Set-CASMailbox $strEmail -ActiveSyncMailboxPolicy "SurfaceHubDeviceMobilePolicy"
- ```
-
-4. Various Exchange properties can be set on the device account to improve the meeting experience. You can see which properties need to be set in the [Exchange properties](exchange-properties-for-surface-hub-device-accounts.md) section.
-
- ``` syntax
- Set-CalendarProcessing -Identity $strEmail -AutomateProcessing AutoAccept -AddOrganizerToSubject $false –AllowConflicts $false –DeleteComments $false -DeleteSubject $false -RemovePrivateProperty $false
- Set-CalendarProcessing -Identity $strEmail -AddAdditionalResponse $true -AdditionalResponse "This is a Surface Hub room!"
- ```
-
- 
-
-5. If you decide to have the password not expire, you can set that with PowerShell cmdlets too. See [Password management](password-management-for-surface-hub-device-accounts.md) for more information.
-
- ``` syntax
- Set-MsolUser -UserPrincipalName $strEmail -PasswordNeverExpires $True
- ```
-
-### Enable the account with Skype for Business
-
-Enable the device account with Skype for Business.
-
-In order to enable Skype for Business, your environment will need to meet the following prerequisites:
-
-- You'll need to have Skype for Business Online Standalone Plan 2 or higher in your O365 plan. The plan needs to support conferencing capability.
-- If you need Enterprise Voice (PSTN telephony) using telephony service providers for the Surface Hub, you need Skype for Business Online Standalone Plan 3.
-- Your tenant users must have Exchange mailboxes.
-- Your Surface Hub account does require a Skype for Business Online Standalone Plan 2 or Skype for Business Online Standalone Plan 3 license, but it does not require an Exchange Online license.
-
-1. Start by creating a remote PowerShell session from a PC.
-
- ```PowerShell
- Import-Module SkypeOnlineConnector
- $cssess=New-CsOnlineSession -Credential $cred
- Import-PSSession $cssess -AllowClobber
- ```
-
-2. To enable your Surface Hub account for Skype for Business Server, run this cmdlet:
-
- ```PowerShell
- Enable-CsMeetingRoom -Identity $strEmail -RegistrarPool "sippoolbl20a04.infra.lync.com" -SipAddressType EmailAddress
- ```
-
- If you aren't sure what value to use for the `RegistrarPool` parameter in your environment, you can get the value from an existing Skype for Business user using this cmdlet:
-
- ```PowerShell
- Get-CsOnlineUser -Identity ‘alice@contoso.microsoft.com’| fl *registrarpool*
- ```
-
-## Create a device account using the Exchange Admin Center
-
->[!NOTE]
->This method will only work if you are syncing from an on-premises Active Directory.
-
-You can use the Exchange Admin Center to create a device account:
-
-1. [Create an account and mailbox with the Exchange Admin Center](#create-device-acct-exch-admin-ctr).
-2. [Create a mobile device mailbox policy from the Exchange Admin Center](#create-device-acct-exch-mbx-policy).
-3. [Use PowerShell to configure the account](#create-device-acct-exch-powershell-conf).
-4. [Enable the account with Skype for Business](#create-device-acct-exch-skype-for-business).
-
-### Create an account and mailbox with the Exchange Admin Center
-
-1. Sign in to your Exchange Admin Center using Exchange admin credentials.
-2. Once you are at the Exchange Admin Center (EAC), navigate to **Recipients** in the left panel.
-
- 
-
-3. On the controls above the list of mailboxess, choose **+** to create a new one, and provide a **Display name**, **Name**, and **User logon name**, and then click **Save**.
-
- 
-
-### Create a mobile device mailbox policy from the Exchange Admin Center
-
->[!NOTE]
->If you want to create and assign a policy to the account you created, and are using Exchange 2010, look up the corresponding information regarding policy creation and policy assignment when using the EMC (Exchange management console).
-
-
-
-1. Go to the Exchange Admin Center.
-
- 
-
-2. To create a mobile device mailbox policy, click **Mobile** from the left panel, then **Mobile device mailbox policies**. Surface Hubs require an account with a mobile device mailbox policy that does not require a password, so if you already have an existing policy that matches this requirement, you can apply that policy to the account. Otherwise use the following steps to create a new one to be used only for Surface Hub device accounts.
-
- 
-
-3. To create a new mobile device account mailbox policy, click the **+** button from the controls above the list of policies to add a new policy. For the name provide a name that will help you distinguish this policy from other device accounts (for example, *SurfaceHubDeviceMobilePolicy*). The policy must not be password-protected, so make sure **Require a Password** remains unchecked, then click **Save**.
-
- 
-
-4. After you have created the new mobile device mailbox policy, go back to the Exchange Admin Center and you will see the new policy listed.
-
- 
-
-5. To apply the ActiveSync policy without using PowerShell, you can do the following:
-
- - In the EAC, click **Recipients** > **Mailboxes** and select a mailbox.
-
- 
-
- - In the **Details** pane, scroll to **Phone and Voice Features** and click **View details** to display the **Mobile Device Details** screen.
-
- 
-
- - The mobile device mailbox policy that’s currently assigned is displayed. To change the mobile device mailbox policy, click **Browse**.
-
- 
-
- - Choose the appropriate mobile device mailbox policy from the list, click **OK** and then click **Save**.
-
- 
-
-### Use PowerShell to configure the account
-
-Now that you're connected to the online services, you can finish setting up the device account. You'll use the device account email address to:
-
-- Change the mailbox type from regular to room.
-- Change various Exchange properties
-- Set the user account password to never expire.
-
-1. You’ll need to enter the account’s mail address and create a variable with that value:
-
- ``` syntax
- $mailbox = (Get-Mailbox )
- ```
-
- To store the value got it from the mailbox:
-
- ``` syntax
- $strEmail = $mailbox.WindowsEmailAddress
- ```
-
- Print the value by running:
-
- ``` syntax
- $strEmail
- ```
-
- You will see the correct email address.
-
-2. You need to convert the account into a room mailbox, so run:
-
- ``` syntax
- Set-Mailbox $strEmail -Type Room
- ```
-
-3. In order for the device account to be authenticated on a Surface Hub, you need to enable the room mailbox account and set a password, so the account can be used by the device to get meeting information using ActiveSync and log in to Skype for Business.
-
- ``` syntax
- Set-Mailbox $strEmail -RoomMailboxPassword (ConvertTo-SecureString -String "" -AsPlainText -Force) -EnableRoomMailboxAccount $true
- ```
-
-4. Various Exchange properties can be set on the device account to improve the meeting experience. You can see which properties need to be set in the [Exchange properties](exchange-properties-for-surface-hub-device-accounts.md) section.
-
- ``` syntax
- Set-CalendarProcessing -Identity $strEmail -AutomateProcessing AutoAccept -AddOrganizerToSubject $false –AllowConflicts $false –DeleteComments $false -DeleteSubject $false -RemovePrivateProperty $false
- Set-CalendarProcessing -Identity $strEmail -AddAdditionalResponse $true -AdditionalResponse "This is a Surface Hub room!"
- ```
-
-5. Now we have to set some properties in AD. To do that, you need the alias of the account (this is the part of the UPN that becomes before the “@”).
-
- ``` syntax
- $strAlias = “”
- ```
-
-6. The user needs to be enabled in AD before it can authenticate with a Surface Hub. Run:
-
- ``` syntax
- Set-ADUser $strAlias -Enabled $True
- ```
-
-7. If you decide to have the password not expire, you can set that with PowerShell cmdlets too. See [Password management](password-management-for-surface-hub-device-accounts.md) for more information.
-
- ``` syntax
- Set-ADUser $strAlias -PasswordNeverExpires $True
- ```
-
-### Enable the account with Skype for Business
-
-Enable the device account with Skype for Business.
-
-In order to enable Skype for Business, your environment will need to meet the following prerequisites:
-
-- You'll need to have Skype for Business Online Standalone Plan 2 or higher in your O365 plan. The plan needs to support conferencing capability.
-- If you need Enterprise Voice (PSTN telephony) using telephony service providers for the Surface Hub, you need Skype for Business Online Standalone Plan 3.
-- Your tenant users must have Exchange mailboxes.
-- Your Surface Hub account does require a Skype for Business Online Standalone Plan 2 or Skype for Business Online Standalone Plan 3 license, but it does not require an Exchange Online license.
-
-1. Start by creating a remote PowerShell session from a PC.
-
- ```PowerShell
- Import-Module SkypeOnlineConnector
- $cssess=New-CsOnlineSession -Credential $cred
- Import-PSSession $cssess -AllowClobber
- ```
-
-2. Retrieve your Surface Hub account Registrar Pool
-
-If you aren't sure what value to use for the `RegistrarPool` parameter in your environment, you can get the value from an existing Skype for Business user using this cmdlet:
-
- ```PowerShell
- Get-CsOnlineUser -Identity ‘alice@contoso.microsoft.com’| fl *registrarpool*
- ```
-
-3. To enable your Surface Hub account for Skype for Business Server, run this cmdlet:
-
- ```PowerShell
- Enable-CsMeetingRoom -Identity $strEmail -RegistrarPool "sippoolbl20a04.infra.lync.com" -SipAddressType EmailAddress
- ```
-
-
-
-
-
-
-
diff --git a/devices/surface-hub/create-and-test-a-device-account-surface-hub.md b/devices/surface-hub/create-and-test-a-device-account-surface-hub.md
deleted file mode 100644
index 8985f70c9d..0000000000
--- a/devices/surface-hub/create-and-test-a-device-account-surface-hub.md
+++ /dev/null
@@ -1,75 +0,0 @@
----
-title: Create and test a device account (Surface Hub)
-description: This topic introduces how to create and test the device account that Microsoft Surface Hub uses to communicate with Microsoft Exchange and Skype.
-ms.assetid: C8605B5F-2178-4C3A-B4E0-CE32C70ECF67
-ms.reviewer: rikot
-manager: laurawi
-keywords: create and test device account, device account, Surface Hub and Microsoft Exchange, Surface Hub and Skype
-ms.prod: surface-hub
-ms.sitesec: library
-author: dansimp
-ms.author: dansimp
-ms.topic: article
-ms.date: 03/06/2018
-ms.localizationpriority: medium
-ms.audience: itpro
----
-
-# Create and test a device account (Surface Hub)
-
-
-This topic introduces how to create and test the device account that Microsoft Surface Hub uses to communicate with Microsoft Exchange and Skype.
-
-A **device account** is an Exchange resource account that Surface Hub uses to:
-
-- Display its meeting calendar
-- Join Teams or Skype for Business calls
-- Send email (for example, email whiteboard content from a meeting)
-
-Once the device account is provisioned to a Surface Hub, people can add this account to a meeting invitation the same way that they would invite a meeting room.
-
-## Configuration overview
-
-This table explains the main steps and configuration decisions when you create a device account.
-
-| Step | Description | Purpose |
-|------|---------------------------------|--------------------------------------|
-| 1 | Created a logon-enabled Exchange resource mailbox (Exchange 2013 or later, or Exchange Online) | This resource mailbox allows the device to maintain a meeting calendar, receive meeting requests, and send mail. It must be logon-enabled to be provisioned to a Surface Hub. |
-| 2 | Configure mailbox properties | The mailbox must be configured with the correct properties to enable the best meeting experience on Surface Hub. For more information on mailbox properties, see [Mailbox properties](exchange-properties-for-surface-hub-device-accounts.md). |
-| 3 | Apply a compatible mobile device mailbox policy to the mailbox | Surface Hub is managed using mobile device management (MDM) rather than through mobile device mailbox policies. For compatibility, the device account must have a mobile device mailbox policy where the **PasswordEnabled** setting is set to False. Otherwise, Surface Hub can't sync mail and calendar info. |
-| 4 | Enable mailbox with Skype for Business (Lync Server 2013 or later, or Skype for Business Online) | Skype for Business must be enabled to use conferencing features like video calls, IM, and screen sharing. |
-| 5 | (Optional) Whitelist ActiveSync Device ID | Your organization may have a global policy that prevents device accounts from syncing mail and calendar info. If so, you need to whitelist the ActiveSync Device ID of your Surface Hub. |
-| 6 | (Optional) Disable password expiration | To simplify management, you can turn off password expiration for the device account and allow Surface Hub to automatically rotate the device account password. For more information about password management, see [Password management](password-management-for-surface-hub-device-accounts.md). |
-
-## Detailed configuration steps
-
-We recommend setting up your device accounts using remote PowerShell. There are PowerShell scripts available to help create and validate device accounts For more information on PowerShell scripts and instructions, see [Appendix A: PowerShell](appendix-a-powershell-scripts-for-surface-hub.md).
-
-For detailed steps using PowerShell to provision a device account, choose an option from the table, based on your organization deployment.
-
-| Organization deployment | Description |
-|---------------------------------|--------------------------------------|
-| [Online deployment (Office 365)](online-deployment-surface-hub-device-accounts.md) | Your organization's environment is deployed entirely on Office 365. |
-| [On-premises deployment (single-forest)](on-premises-deployment-surface-hub-device-accounts.md) | Your organization has servers that it controls and uses to host Active Directory, Exchange, and Skype for Business (or Lync) in a single-forest environment. |
-| [On-premises deployment (multiple forests)](on-premises-deployment-surface-hub-multi-forest.md) | Your organization has servers that it controls and uses to host Active Directory, Exchange, and Skype for Business (or Lync) in a multi-forest environment. |
-| [Hybrid deployment](hybrid-deployment-surface-hub-device-accounts.md) | Your organization has a mix of services, with some hosted on-premises and some hosted online through Office 365. |
-| [Online or hybrid deployment using Skype Hybrid Voice environment](skype-hybrid-voice.md) | Your organization has Skype for Business home pools and Exchange servers in the cloud, and uses an on-premises pool of Skype for Business 2015 or Cloud Connector edition connected via Public Switched Telephone Network (PSTN). |
-
-
-If you prefer to use a graphical user interface (UI), some steps can be done using UI instead of PowerShell.
-For more information, see [Creating a device account using UI](create-a-device-account-using-office-365.md).
-
-## Account verification and testing
-
-There are two methods available that you can use to validate and test a Surface Hub device account: [account verifications scripts](appendix-a-powershell-scripts-for-surface-hub.md#acct-verification-ps-scripts) and the [Surface Hub Hardware Diagnostic app](https://www.microsoft.com/store/apps/9nblggh51f2g). The account verification script will validate a previously-created device account using PowerShell from your desktop. The Surface Hub Hardware Diagnostic app is installed on your Surface Hub and provides detailed feedback about signin and communication failures. Both are valuable tools to test newly created device accounts and should be used to ensure optimal account availability.
-
-
-
-
-
-
-
-
-
-
-
diff --git a/devices/surface-hub/device-reset-surface-hub.md b/devices/surface-hub/device-reset-surface-hub.md
deleted file mode 100644
index 8eb3486d7d..0000000000
--- a/devices/surface-hub/device-reset-surface-hub.md
+++ /dev/null
@@ -1,129 +0,0 @@
----
-title: Reset or recover a Surface Hub
-description: Describes the reset and recovery processes for the Surface Hub, and provides instructions.
-ms.assetid: 44E82EEE-1905-464B-A758-C2A1463909FF
-ms.reviewer:
-manager: laurawi
-keywords: reset Surface Hub, recover
-ms.prod: surface-hub
-ms.sitesec: library
-author: dansimp
-ms.author: dansimp
-ms.topic: article
-ms.date: 07/31/2019
-ms.localizationpriority: medium
----
-
-# Reset or recover a Surface Hub
-
-This article describes how to reset or recover a Microsoft Surface Hub.
-
-[Resetting the Surface Hub](#reset-a-surface-hub) returns its operating system to the last cumulative Windows update, and removes all local user files and configuration information. The information that is removed includes the following:
-
-- The device account
-- Account information for the device's local administrators
-- Domain-join or Azure AD-join information
-- Mobile Device Management (MDM) enrollment information
-- Configuration information that was set by using MDM or the Settings app
-
-[Recovering a Surface Hub from the cloud](#recover-a-surface-hub-from-the-cloud) also removes this information. In addition, the Surface Hub downloads a new operating system image and installs it. You can specify whether the recovery process preserves other information that is stored on the Surface Hub.
-
-## Reset a Surface Hub
-
-You may have to reset your Surface Hub for reasons such as the following:
-
-- You are re-purposing the device for a new meeting space and want to reconfigure it.
-- You want to change how you locally manage the device.
-- The user name or password for the device account or the Administrator account has been lost.
-- After you install an update, the performance of the device decreases.
-
-During the reset process, if you see a blank screen for long periods of time, please wait and do not take any action.
-
-> [!WARNING]
-> The device reset process may take up to six hours. Do not turn off or unplug the Surface Hub until the process has finished. If you interrupt the process, the device becomes inoperable. The device requires warranty service in order to become functional again.
-
-1. On your Surface Hub, open **Settings**.
-
- 
-
-1. Select **Update & Security**.
-
- 
-
-1. Select **Recovery**, and then, under **Reset device**, select **Get started**.
-
- 
-
- After the reset process finishes, the Surface Hub starts the [first run program](first-run-program-surface-hub.md) again. If the reset process encounters a problem, it rolls the Surface Hub back to the previously-existing operating system image and then displays the Welcome screen.
-
-
-
-## Recover a Surface Hub from the cloud
-
-If for some reason the Surface Hub becomes unusable, you can still recover it from the cloud without assistance from Microsoft Support. The Surface Hub can download a fresh operating system image from the cloud, and use that image to reinstall its operating system.
-
-You may have to use this type of recovery process under the following circumstances:
-
-- [The Surface Hub or its related accounts have entered an unstable state](#recover-a-surface-hub-in-a-bad-state)
-- [The Surface Hub is locked](#recover-a-locked-surface-hub)
-
->[!IMPORTANT]
->The **Recover from the cloud** process requires an open internet connection (no proxy or other authentications). An ethernet connection is recommended.
-
-### Recover a Surface Hub in a bad state
-
-If the device account gets into an unstable state or if the administrator account encounters problems, you can use the Settings app to start the cloud recovery process. You should only use the cloud recovery process when the [device reset](#reset-a-surface-hub) process doesn't fix the problem.
-
-1. On your Surface Hub, select **Settings** > **Update & security** > **Recovery**.
-
-1. Under **Recover from the cloud**, select **Restart now**.
-
- 
-
-### Recover a locked Surface Hub
-
-On rare occasions, a Surface Hub may encounter an error while cleaning up user and app data at the end of a session. When this happens, the device automatically restarts and tries the operation again. But if this operation fails repeatedly, the device automatically locks to protect user data. To unlock it, you must [reset the device](#reset-a-surface-hub) or, if that doesn't work, recover it from the cloud.
-
-1. Locate the power switch on the bottom of Surface Hub. The power switch is next to the power cord connection. For more information about the power switch, see the [Surface Hub Site Readiness Guide (PDF)](surface-hub-site-readiness-guide.md).
-
-1. While the Surface Hub displays the Welcome screen, use the power switch to turn off the Surface Hub.
-
-1. Use the power switch to turn the Surface Hub back on. The device starts and displays the Surface Hub Logo screen. When you see spinning dots under the Surface Hub Logo, use the power switch to turn the Surface Hub off again.
-
-1. Repeat step 3 three times, or until the Surface Hub displays the "Preparing Automatic Repair" message. After it displays this message, the Surface Hub displays the Windows RE screen.
-
-1. Select **Advanced Options**.
-
-1. Select **Recover from the cloud**. (Optionally, you can select **Reset**. However, **Recover from the cloud** is the recommended approach.)
-
- 
-1. If you are prompted to enter the Bitlocker key, do one of the following:
-
- - To preserve the information that Bitlocker protects on the Surface Hub, enter the Bitlocker key.
- - To discard the protected information, select **Skip this drive**
-
-1. When you are prompted, select **Reinstall**.
-
- 
-
-1. To repartition the disk, select **Yes**.
-
- 
-
- First, the recovery process downloads the operating system image from the cloud.
-
- 
-
- When the download finishes, the recovery process restores the Surface Hub according to the options that you selected.
-
-
-## Contact Support
-
-If you have questions or need help, you can [create a support request](https://support.microsoft.com/supportforbusiness/productselection).
-
-
-## Related topics
-
-[Manage Microsoft Surface Hub](manage-surface-hub.md)
-
-[Microsoft Surface Hub administrator's guide](surface-hub-administrators-guide.md)
diff --git a/devices/surface-hub/differences-between-surface-hub-and-windows-10-enterprise.md b/devices/surface-hub/differences-between-surface-hub-and-windows-10-enterprise.md
deleted file mode 100644
index 9309e9b2a3..0000000000
--- a/devices/surface-hub/differences-between-surface-hub-and-windows-10-enterprise.md
+++ /dev/null
@@ -1,172 +0,0 @@
----
-title: Operating system essentials (Surface Hub)
-description: This topic explains unique aspects of the Windows 10 Team operating system and how it differs from Windows 10 Enterprise.
-keywords: change history
-ms.prod: surface-hub
-ms.sitesec: library
-author: dansimp
-ms.author: dansimp
-ms.topic: article
-ms.date: 06/20/2019
-ms.reviewer:
-manager: laurawi
-ms.localizationpriority: medium
----
-
-# Operating system essentials (Surface Hub)
-
-The Surface Hub operating system, Windows 10 Team, is based on Windows 10 Enterprise, providing rich support for enterprise management, security, and other features. However, there are important differences between them. While the Enterprise edition is designed for PCs, Windows 10 Team is designed from the ground up for large screens and meeting rooms. When you evaluate security and management requirements for Surface Hub, it's best to consider it as a new operating system. This article is designed to help highlight the key differences between Windows 10 Team on Surface Hub and Windows 10 Enterprise, and what the differences mean for your organization.
-
-## User interface
-
-### Shell (OS user interface)
-
-The Surface Hub's shell is designed from the ground up to be large screen and touch optimized. It doesn't use the same shell as Windows 10 Enterprise.
-
-*Organization policies that this may affect:* Settings related to controls in the Windows 10 Enterprise shell don't apply for Surface Hub.
-
-### Lock screen and screensaver
-
-Surface Hub doesn't have a lock screen or a screen saver, but it has a similar feature called the welcome screen. The welcome screen shows scheduled meetings from the device account's calendar, and easy entry points to the Surface Hub's top apps - Skype for Business, Whiteboard, and Connect.
-
-*Organization policies that this may affect:* Settings for lock screen, screen timeout, and screen saver don't apply for Surface Hub.
-
-### User sign-in
-
-Surface Hub is designed to be used in communal spaces, such as meeting rooms. Unlike Windows PCs, anyone can walk up and use a Surface Hub without requiring a user to sign in. To enable this communal functionality, Surface Hub does not support Windows sign-in the same way that Windows 10 Enterprise does (e.g., signing in a user to the OS and using those credentials throughout the OS). Instead, there is always a local, auto signed-in, low-privilege user signed in to the Surface Hub. It doesn't support signing in any additional users, including admin users (e.g., when an admin signs in, they are not signed in to the OS).
-
-Users can sign in to a Surface Hub, but they will not be signed in to the OS. For example, when a user signs in to Apps or My Meetings and Files, the users is signed in only to the apps or services, not to the OS. As a result, the signed-in user is able to retrieve their cloud files and personal meetings stored in the cloud, and these credentials are discarded when **End session** is activated.
-
-
-*Organization policies that this may affect:* Generally, Surface Hub uses lockdown features rather than user access control to enforce security. Policies related to password requirements, interactive logon, user accounts, and access control don't apply for Surface Hub.
-
-### Saving and browsing files
-
-Users have access to a limited set of directories on the Surface Hub:
-- Music
-- Videos
-- Documents
-- Pictures
-- Downloads
-
-Files saved locally in these directories are deleted when users press **End session**. To save content created during a meeting, users should save files to a USB drive or to OneDrive.
-
-*Organization policies that this may affect:* Policies related to access permissions and ownership of files and folders don't apply for Surface Hub. Users can't browse and save files to system directories and network folders.
-
-## Applications
-
-### Default applications
-
-With few exceptions, the default Universal Windows Platform (UWP) apps on Surface Hub are also available on Windows 10 PCs.
-
-UWP apps pre-installed on Surface Hub:
-- Alarms & Clock
-- Calculator
-- Connect
-- Excel Mobile
-- Feedback Hub
-- File Explorer*
-- Get Started
-- Maps
-- Microsoft Edge
-- Microsoft Power BI
-- OneDrive
-- Photos
-- PowerPoint Mobile
-- Settings*
-- Skype for Business*
-- Store
-- Whiteboard*
-- Word Mobile
-
-*Apps with an asterisk (*) are unique to Surface Hub*
-
-*Organization policies that this may affect:* Use guidelines for Windows 10 Enterprise to determine the features and network requirements for default apps on the Surface Hub.
-
-### Installing apps, drivers, and services
-
-To help preserve the appliance-like nature of the device, Surface Hub only supports installing Universal Windows Platform (UWP) apps, and does not support installing classic Win32 apps, services and drivers. Furthermore, only admins have access to install UWP apps.
-
-*Organization policies that this may affect:* Employees can only use the apps that have been installed by admins, helping mitigate against unintended use. Surface Hub doesn't support installing Win32 agents required by most traditional PC management and monitoring tools.
-
-## Security and lockdown
-
-For Surface Hub to be used in communal spaces, such as meeting rooms, its custom OS implements many of the security and lockdown features available in Windows 10.
-
-Surface Hub implements these Windows 10 security features:
-- [UEFI Secure Boot](https://msdn.microsoft.com/windows/hardware/commercialize/manufacture/desktop/secure-boot-overview)
-- [User Mode Code Integrity (UMCI) with Device Guard](https://technet.microsoft.com/itpro/windows/keep-secure/introduction-to-device-guard-virtualization-based-security-and-code-integrity-policies)
-- [Application restriction policies using AppLocker](https://technet.microsoft.com/itpro/windows/keep-secure/applocker-overview)
-- [BitLocker Drive Encryption](https://technet.microsoft.com/itpro/windows/keep-secure/bitlocker-overview)
-- [Trusted Platform Module (TPM)](https://technet.microsoft.com/itpro/windows/keep-secure/trusted-platform-module-overview)
-- [Windows Defender](https://technet.microsoft.com/itpro/windows/keep-secure/windows-defender-in-windows-10)
-- [User Account Control (UAC)](https://technet.microsoft.com/itpro/windows/keep-secure/user-account-control-overview) for access to the Settings app
-
-These Surface Hub features provide additional security:
-- Custom UEFI firmware
-- Custom shell and Start menu limits device to meeting functions
-- Custom File Explorer only grants access to files and folders under My Documents
-- Custom Settings app only allows admins to modify device settings
-- Downloading advanced Plug and Play drivers is disabled
-
-*Organization policies that this may affect:* Consider these features when performing your security assessment for Surface Hub.
-
-## Management
-
-### Device settings
-
-Device settings can be configured through the Settings app. The Settings app is customized for Surface Hub, but also contains many familiar settings from Windows 10 Desktop. A User Accounts Control (UAC) prompt appears when opening up the Settings app to verify the admin's credentials, but this does not sign in the admin.
-
-*Organization policies that this may affect:* Employees can use the Surface Hub for meetings, but cannot modify any device settings. In addition to lockdown features, this ensures that employees only use the device for meeting functions.
-
-### Administrative features
-
-The administrative features in Windows 10 Enterprise, such as the Microsoft Management Console, Run, Command Prompt, PowerShell, registry editor, event viewer, and task manager are not supported on Surface Hub. The Settings app contains all of the administrative features locally available on Surface Hub.
-
-*Organization policies that this may affect:* Surface Hubs are not managed like traditional PCs. Use MDM to configure settings and OMS to monitor your Surface Hub.
-
-### Remote management and monitoring
-
-Surface Hub supports remote management through mobile device management (MDM) solutions such as [Microsoft Intune](https://docs.microsoft.com/intune/) and monitoring through [Azure Monitor](https://azure.microsoft.com/services/monitor/).
-
-*Organization policies that this may affect:* Surface Hub doesn't support installing Win32 agents required by most traditional PC management and monitoring tools, such as System Center Operations Manager.
-
-### Group Policy
-
-Surface Hub does not support Windows Group Policy, including auditing. Instead, use MDM to apply policies to your Surface Hub. For more information about MDM, see [Manage settings with an MDM provider](manage-settings-with-mdm-for-surface-hub.md).
-
-*Organization policies that this may affect:* Use MDM to manage Surface Hub rather than group policy.
-
-### Remote assistance
-
-Surface Hub does not support remote assistance.
-
-*Organization policies that this may affect:* Policies related to remote assistance don't apply for Surface Hub.
-
-## Network
-
-### Domain join and Azure Active Directory (Azure AD) join
-
-Surface Hub uses domain join and Azure AD join primarily to provide a directory-backed admin group. Users can't sign in with a domain account. For more information, see [Admin group management](admin-group-management-for-surface-hub.md).
-
-*Organization policies that this may affect:* Group policies are not applied when a Surface Hub is joined to your domain. Policies related to domain membership don't apply for Surface Hub.
-
-### Accessing domain resources
-
-Users can sign in to Microsoft Edge to access intranet sites and online resources (such as Office 365). If your Surface Hub is configured with a device account, the system uses it to access Exchange and Skype for Business. However, Surface Hub doesn't support accessing domain resources such as file shares and printers.
-
-*Organization policies that this may affect:* Policies related to accessing domain objects don't apply for Surface Hub.
-
-
-
-### Diagnostic data
-
-The Surface Hub OS uses the Windows 10 Connected User Experience and Telemetry component to gather and transmit diagnostic data. For more information, see [Configure Windows diagnostic data in your organization](https://technet.microsoft.com/itpro/windows/manage/configure-windows-diagnostic-data-in-your-organization).
-
-*Organization policies that this may affect:* Configure diagnostic data levels for Surface Hub in the same way as you do for Windows 10 Enterprise.
diff --git a/devices/surface-hub/downloads/Guide-SurfaceHub2S-Navigation.pptx b/devices/surface-hub/downloads/Guide-SurfaceHub2S-Navigation.pptx
deleted file mode 100644
index b06a6e8b44..0000000000
Binary files a/devices/surface-hub/downloads/Guide-SurfaceHub2S-Navigation.pptx and /dev/null differ
diff --git a/devices/surface-hub/downloads/Guide-SurfaceHub2S-Office365.pptx b/devices/surface-hub/downloads/Guide-SurfaceHub2S-Office365.pptx
deleted file mode 100644
index 4fa5e3abd9..0000000000
Binary files a/devices/surface-hub/downloads/Guide-SurfaceHub2S-Office365.pptx and /dev/null differ
diff --git a/devices/surface-hub/downloads/Guide-SurfaceHub2S-Teams.pptx b/devices/surface-hub/downloads/Guide-SurfaceHub2S-Teams.pptx
deleted file mode 100644
index 210102de52..0000000000
Binary files a/devices/surface-hub/downloads/Guide-SurfaceHub2S-Teams.pptx and /dev/null differ
diff --git a/devices/surface-hub/downloads/Guide-SurfaceHub2S-Whiteboard.pptx b/devices/surface-hub/downloads/Guide-SurfaceHub2S-Whiteboard.pptx
deleted file mode 100644
index 6d39d374a7..0000000000
Binary files a/devices/surface-hub/downloads/Guide-SurfaceHub2S-Whiteboard.pptx and /dev/null differ
diff --git a/devices/surface-hub/downloads/Outline-SurfaceHub2S-EndUser.pdf b/devices/surface-hub/downloads/Outline-SurfaceHub2S-EndUser.pdf
deleted file mode 100644
index 6c5b52d377..0000000000
Binary files a/devices/surface-hub/downloads/Outline-SurfaceHub2S-EndUser.pdf and /dev/null differ
diff --git a/devices/surface-hub/downloads/Outline-SurfaceHub2S-HelpDesk.pdf b/devices/surface-hub/downloads/Outline-SurfaceHub2S-HelpDesk.pdf
deleted file mode 100644
index ae296c8c08..0000000000
Binary files a/devices/surface-hub/downloads/Outline-SurfaceHub2S-HelpDesk.pdf and /dev/null differ
diff --git a/devices/surface-hub/downloads/Outline-SurfaceHub2S-PowerUser.pdf b/devices/surface-hub/downloads/Outline-SurfaceHub2S-PowerUser.pdf
deleted file mode 100644
index 9f64a7c4f2..0000000000
Binary files a/devices/surface-hub/downloads/Outline-SurfaceHub2S-PowerUser.pdf and /dev/null differ
diff --git a/devices/surface-hub/downloads/QRCConnectYourPC.pdf b/devices/surface-hub/downloads/QRCConnectYourPC.pdf
deleted file mode 100644
index fbdb9d9164..0000000000
Binary files a/devices/surface-hub/downloads/QRCConnectYourPC.pdf and /dev/null differ
diff --git a/devices/surface-hub/downloads/QRCJoinTeamsMeeting.pdf b/devices/surface-hub/downloads/QRCJoinTeamsMeeting.pdf
deleted file mode 100644
index 62b86d2a00..0000000000
Binary files a/devices/surface-hub/downloads/QRCJoinTeamsMeeting.pdf and /dev/null differ
diff --git a/devices/surface-hub/downloads/QRCManageTeamsMeeting.pdf b/devices/surface-hub/downloads/QRCManageTeamsMeeting.pdf
deleted file mode 100644
index a6af26dcf9..0000000000
Binary files a/devices/surface-hub/downloads/QRCManageTeamsMeeting.pdf and /dev/null differ
diff --git a/devices/surface-hub/downloads/QRCNavigationBasics.pdf b/devices/surface-hub/downloads/QRCNavigationBasics.pdf
deleted file mode 100644
index 6d8eb75ad5..0000000000
Binary files a/devices/surface-hub/downloads/QRCNavigationBasics.pdf and /dev/null differ
diff --git a/devices/surface-hub/downloads/QRCScheduleTeamsMeeting.pdf b/devices/surface-hub/downloads/QRCScheduleTeamsMeeting.pdf
deleted file mode 100644
index a33cf1b1e1..0000000000
Binary files a/devices/surface-hub/downloads/QRCScheduleTeamsMeeting.pdf and /dev/null differ
diff --git a/devices/surface-hub/downloads/QRCShareSendFile.pdf b/devices/surface-hub/downloads/QRCShareSendFile.pdf
deleted file mode 100644
index 56d5c9f8c2..0000000000
Binary files a/devices/surface-hub/downloads/QRCShareSendFile.pdf and /dev/null differ
diff --git a/devices/surface-hub/downloads/QRCSignInToViewMeetingsFiles.pdf b/devices/surface-hub/downloads/QRCSignInToViewMeetingsFiles.pdf
deleted file mode 100644
index 61caa64f94..0000000000
Binary files a/devices/surface-hub/downloads/QRCSignInToViewMeetingsFiles.pdf and /dev/null differ
diff --git a/devices/surface-hub/downloads/QRCStartNewTeamsMeeting.pdf b/devices/surface-hub/downloads/QRCStartNewTeamsMeeting.pdf
deleted file mode 100644
index d7a7c89268..0000000000
Binary files a/devices/surface-hub/downloads/QRCStartNewTeamsMeeting.pdf and /dev/null differ
diff --git a/devices/surface-hub/downloads/QRCWhiteboardAdvanced.pdf b/devices/surface-hub/downloads/QRCWhiteboardAdvanced.pdf
deleted file mode 100644
index aed2f55671..0000000000
Binary files a/devices/surface-hub/downloads/QRCWhiteboardAdvanced.pdf and /dev/null differ
diff --git a/devices/surface-hub/downloads/QRCWhiteboardTools.pdf b/devices/surface-hub/downloads/QRCWhiteboardTools.pdf
deleted file mode 100644
index c6dfcc3523..0000000000
Binary files a/devices/surface-hub/downloads/QRCWhiteboardTools.pdf and /dev/null differ
diff --git a/devices/surface-hub/downloads/SurfaceHubAdoptionToolKit.pdf b/devices/surface-hub/downloads/SurfaceHubAdoptionToolKit.pdf
deleted file mode 100644
index 79675aaaaa..0000000000
Binary files a/devices/surface-hub/downloads/SurfaceHubAdoptionToolKit.pdf and /dev/null differ
diff --git a/devices/surface-hub/downloads/TrainingGuide-SurfaceHub2S-EndUser.pdf b/devices/surface-hub/downloads/TrainingGuide-SurfaceHub2S-EndUser.pdf
deleted file mode 100644
index 9fa82b77c5..0000000000
Binary files a/devices/surface-hub/downloads/TrainingGuide-SurfaceHub2S-EndUser.pdf and /dev/null differ
diff --git a/devices/surface-hub/downloads/TrainingGuide-SurfaceHub2S-HelpDesk.pdf b/devices/surface-hub/downloads/TrainingGuide-SurfaceHub2S-HelpDesk.pdf
deleted file mode 100644
index 36d552a91a..0000000000
Binary files a/devices/surface-hub/downloads/TrainingGuide-SurfaceHub2S-HelpDesk.pdf and /dev/null differ
diff --git a/devices/surface-hub/downloads/TrainingGuide-SurfaceHub2S-PowerUser.pdf b/devices/surface-hub/downloads/TrainingGuide-SurfaceHub2S-PowerUser.pdf
deleted file mode 100644
index 216737e393..0000000000
Binary files a/devices/surface-hub/downloads/TrainingGuide-SurfaceHub2S-PowerUser.pdf and /dev/null differ
diff --git a/devices/surface-hub/enable-8021x-wired-authentication.md b/devices/surface-hub/enable-8021x-wired-authentication.md
deleted file mode 100644
index 8ac2baccb6..0000000000
--- a/devices/surface-hub/enable-8021x-wired-authentication.md
+++ /dev/null
@@ -1,62 +0,0 @@
----
-title: Enable 802.1x wired authentication
-description: 802.1x Wired Authentication MDM policies have been enabled on Surface Hub devices.
-ms.prod: surface-hub
-ms.sitesec: library
-author: dansimp
-ms.author: dansimp
-ms.topic: article
-ms.date: 11/15/2017
-ms.reviewer:
-manager: laurawi
-ms.localizationpriority: medium
----
-
-# Enable 802.1x wired authentication
-
-The [November 14, 2017 update to Windows 10](https://support.microsoft.com/help/4048954/windows-10-update-kb4048954) (build 15063.726) enables 802.1x wired authentication MDM policies on Surface Hub devices. The feature allows organizations to enforce standardized wired network authentication using the [IEEE 802.1x authentication protocol](http://www.ieee802.org/1/pages/802.1x-2010.html). This is already available for wireless authentication using WLAN profiles via MDM. This topic explains how to configure a Surface Hub for use with wired authentication.
-
-Enforcement and enablement of 802.1x wired authentication on Surface Hub can be done through MDM [OMA-URI definition](https://docs.microsoft.com/intune-classic/deploy-use/windows-10-policy-settings-in-microsoft-intune#oma-uri-settings).
-
-The primary configuration to set is the **LanProfile** policy. Depending on the authentication method selected, other policies may be required, either the **EapUserData** policy or through MDM policies for adding user or machine certificates (such as [ClientCertificateInstall](https://docs.microsoft.com/windows/client-management/mdm/clientcertificateinstall-csp) for user/device certificates or [RootCATrustedCertificates](https://docs.microsoft.com/windows/client-management/mdm/rootcacertificates-csp) for device certificates).
-
-## LanProfile policy element
-
-To configure Surface Hub to use one of the supported 802.1x authentication methods, utilize the following OMA-URI.
-
-```
-./Vendor/MSFT/SurfaceHub/Dot3/LanProfile
-```
-
-This OMA-URI node takes a text string of XML as a parameter. The XML provided as a parameter should conform to the [Wired LAN Profile Schema](https://msdn.microsoft.com/library/cc233002.aspx) including elements from the [802.1X schema](https://msdn.microsoft.com/library/cc233003.aspx).
-
-In most instances, an administrator or user can export the LanProfile XML from an existing PC that is already configured on the network for 802.1X using this following NETSH command.
-
-```
-netsh lan export profile folder=.
-```
-
-Running this command will give the following output and place a file titled **Ethernet.xml** in the current directory.
-
-```
-Interface: Ethernet
-Profile File Name: .\Ethernet.xml
-1 profile(s) were exported successfully.
-```
-
-## EapUserData policy element
-
-If your selected authentication method requires a username and password as opposed to a certificate, you can use the **EapUserData** element to specify credentials for the device to use to authenticate to the network.
-
-```
-./Vendor/MSFT/SurfaceHub/Dot3/EapUserData
-```
-
-This OMA-URI node takes a text string of XML as a parameter. The XML provided as a parameter should conform to the [PEAP MS-CHAPv2 User Properties example](https://msdn.microsoft.com/library/windows/desktop/bb891979). In the example, you will need to replace all instances of *test* and *ias-domain* with your information.
-
-
-
-## Adding certificates
-
-If your selected authentication method is certificate-based, you will need to [create a provisioning package](provisioning-packages-for-surface-hub.md), [utilize MDM](https://docs.microsoft.com/windows/client-management/mdm/clientcertificateinstall-csp), or import a certificate from settings (**Settings** > **Update and Security** > **Certificates**) to deploy those certificates to your Surface Hub device in the appropriate Certificate Store. When adding certificates, each PFX must contain only one certificate (a PFX cannot have multiple certificates).
-
diff --git a/devices/surface-hub/exchange-properties-for-surface-hub-device-accounts.md b/devices/surface-hub/exchange-properties-for-surface-hub-device-accounts.md
deleted file mode 100644
index 9a100d4a60..0000000000
--- a/devices/surface-hub/exchange-properties-for-surface-hub-device-accounts.md
+++ /dev/null
@@ -1,104 +0,0 @@
----
-title: Microsoft Exchange properties (Surface Hub)
-description: Some Microsoft Exchange properties of the device account must be set to particular values to have the best meeting experience on Microsoft Surface Hub.
-ms.assetid: 3E84393B-C425-45BF-95A6-D6502BA1BF29
-ms.reviewer:
-manager: laurawi
-keywords: Microsoft Exchange properties, device account, Surface Hub, Windows PowerShell cmdlet
-ms.prod: surface-hub
-ms.sitesec: library
-author: dansimp
-ms.author: dansimp
-ms.topic: article
-ms.date: 06/20/2019
-ms.localizationpriority: medium
----
-
-# Microsoft Exchange properties (Surface Hub)
-
-
-Some Microsoft Exchange properties of the device account must be set to particular values to have the best meeting experience on Microsoft Surface Hub. The following table lists various Exchange properties based on PowerShell cmdlet parameters, their purpose, and the values they should be set to.
-
-
-
-
-
-
-
-
-
-
-
Property
-
Description
-
Value
-
Impact
-
-
-
-
-
AutomateProcessing
-
The AutomateProcessing parameter enables or disables calendar processing on the mailbox.
-
AutoAccept
-
The Surface Hub will be able to automatically accept or decline meeting requests based on its availability.
-
-
-
AddOrganizerToSubject
-
The AddOrganizerToSubject parameter specifies whether the meeting organizer's name is used as the subject of the meeting request.
-
$False
-
The welcome screen will not show the meeting organizer twice (instead of showing it as both the organizer and in the meeting subject).
-
-
-
AllowConflicts
-
The AllowConflicts parameter specifies whether to allow conflicting meeting requests.
-
$False
-
The Surface Hub will decline meeting requests that conflict with another meeting’s time.
-
-
-
DeleteComments
-
The DeleteComments parameter specifies whether to remove or keep any text in the message body of incoming meeting requests.
-
$False
-
The message body of meetings can be retained and retrieved from a Surface Hub if you need it during a meeting.
-
-
-
DeleteSubject
-
The DeleteSubject parameter specifies whether to remove or keep the subject of incoming meeting requests.
-
$False
-
Meeting request subjects can be shown on the Surface Hub.
-
-
-
RemovePrivateProperty
-
The RemovePrivateProperty parameter specifies whether to clear the private flag for incoming meeting requests.
-
$False
-
Private meeting subjects will show as Private on the welcome screen.
-
-
-
AddAdditionalResponse
-
The AddAdditionalResponse parameter specifies whether additional information will be sent from the resource mailbox when responding to meeting requests.
-
$True
-
When a response is sent to a meeting request, custom text will be provided in the response.
-
-
-
AdditionalResponse
-
The AdditionalResponse parameter specifies the additional information to be included in responses to meeting requests.
-
-Note This text will not be sent unless AddAdditionalResponse is set to $True.
-
-
-
-
-
Your choice—the additional response can be used to inform people how to use a Surface Hub or point them towards resources.
-
Adding an additional response message can provide people an introduction to how they can use a Surface Hub in their meeting.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/devices/surface-hub/finishing-your-surface-hub-meeting.md b/devices/surface-hub/finishing-your-surface-hub-meeting.md
deleted file mode 100644
index 3e02c9bb0a..0000000000
--- a/devices/surface-hub/finishing-your-surface-hub-meeting.md
+++ /dev/null
@@ -1,95 +0,0 @@
----
-title: End session - ending a Surface Hub meeting
-description: To end a Surface Hub meeting, tap End session. Surface Hub cleans up the application state, operating system state, and the user interface so that Surface Hub is ready for the next meeting.
-keywords: I am Done, end Surface Hub meeting, finish Surface Hub meeting, clean up Surface Hub meeting
-ms.prod: surface-hub
-ms.sitesec: library
-author: dansimp
-ms.author: dansimp
-ms.topic: article
-ms.date: 07/27/2017
-ms.reviewer:
-manager: laurawi
-ms.localizationpriority: medium
----
-
-# End a Surface Hub meeting with End session
-Surface Hub is a collaboration device designed to be used in meeting spaces by different groups of people. At the end of a meeting, users can tap **End session** to clean up any sensitive data and prepare the device for the next meeting. Surface Hub will clean up, or reset, the following states:
-- Applications
-- Operating system
-- User interface
-
-This topic explains what **End session** resets for each of these states.
-
-## Applications
-When you start apps on Surface Hub, they are stored in memory and data is stored at the application level. Data is available to all users during that session (or meeting) until date is removed or overwritten. When **End session** is selected, Surface Hub application state is cleared out by closing applications, deleting browser history, resetting applications, and removing Skype logs.
-
-### Close applications
-Surface Hub closes all visible windows, including Win32 and Universal Windows Platform (UWP) applications. The application close stage uses the multitasking view to query the visible windows. Win32 windows that do not close within a certain timeframe are closed using **TerminateProcess**.
-
-### Delete browser history
-Surface Hub uses Delete Browser History (DBH) in Edge to clear Edge history and cached data. This is similar to how a user can clear out their browser history manually, but **End session** also ensures that application states are cleared and data is removed before the next session, or meeting, starts.
-
-### Reset applications
-**End session** resets the state of each application that is installed on the Surface Hub. Resetting an application clears all background tasks, application data, notifications, and user consent dialogs. Applications are returned to their first-run state for the next people that use Surface Hub.
-
-### Remove Skype logs
-Skype does not store personally-identifiable information on Surface Hub. Information is stored in the Skype service to meet existing Skype for Business guidance. Local Skype logging information is the only data removed when **End session** is selected. This includes Unified Communications Client Platform (UCCP) logs and media logs.
-
-## Operating System
-The operating system hosts a variety of information about the state of the sessions that needs to be cleared after each Surface Hub meeting.
-
-### File System
-Meeting attendees have access to a limited set of directories on the Surface Hub. When **End session** is selected, Surface Hub clears these directories:
-- Music
-- Videos
-- Documents
-- Pictures
-- Downloads
-
-Surface Hub also clears these directories, since many applications often write to them:
-- Desktop
-- Favorites
-- Recent
-- Public Documents
-- Public Music
-- Public Videos
-- Public Downloads
-
-### Credentials
-User credentials that are stored in **TokenBroker**, **PasswordVault**, or **Credential Manager** are cleared when you tap **End session**.
-
-## User interface
-User interface (UI) settings are returned to their default values when **End session** is selected.
-
-### UI items
-- Reset Quick Actions to default state
-- Clear Toast notifications
-- Reset volume levels
-- Reset sidebar width
-- Reset tablet mode layout
-- Sign user out of Office 365 meetings and files
-
-### Accessibility
-Accessibility features and apps are returned to default settings when **End session** is selected.
-- Filter keys
-- High contrast
-- Sticky keys
-- Toggle keys
-- Mouse keys
-- Magnifier
-- Narrator
-
-### Clipboard
-The clipboard is cleared to remove data that was copied to the clipboard during the session.
-
-## Frequently asked questions
-**What happens if I forget to tap End session at the end of a meeting, and someone else uses the Surface Hub later?**
-Surface Hub only cleans up meeting content when users tap **End session**. If you leave the meeting without tapping **End session**, the device will return to the welcome screen after some time. From the welcome screen, users have the option to resume the previous session or start a new one. You can also disable the ability to resume a session if **End session** is not pressed.
-
-**Are documents recoverable?**
-Removing files from the hard drive when **End session** is selected is just like any other file deletion from a hard disk drive. Third-party software might be able to recover data from the hard disk drive, but file recovery is not a supported feature on Surface Hub. To prevent data loss, always save the data you need before leaving a meeting.
-
-**Do the clean-up actions from End session comply with the US Department of Defense clearing and sanitizing standard: DoD 5220.22-M?**
-No. Currently, the clean-up actions from **End session** do not comply with this standard.
-
diff --git a/devices/surface-hub/first-run-program-surface-hub.md b/devices/surface-hub/first-run-program-surface-hub.md
deleted file mode 100644
index 8a3bfc6e91..0000000000
--- a/devices/surface-hub/first-run-program-surface-hub.md
+++ /dev/null
@@ -1,461 +0,0 @@
----
-title: First-run program (Surface Hub)
-description: The term \ 0034;first run \ 0034; refers to the series of steps you'll go through the first time you power up your Microsoft Surface Hub, and means the same thing as \ 0034;out-of-box experience \ 0034; (OOBE). This section will walk you through the process.
-ms.assetid: 07C9E84C-1245-4511-B3B3-75939AD57C49
-ms.reviewer:
-manager: laurawi
-keywords: first run, Surface Hub, out-of-box experience, OOBE
-ms.prod: surface-hub
-ms.sitesec: library
-author: dansimp
-ms.author: dansimp
-ms.topic: article
-ms.date: 07/27/2017
-ms.localizationpriority: medium
----
-
-# First-run program (Surface Hub)
-
-
-The term "first run" refers to the series of steps you'll go through the first time you power up your Microsoft Surface Hub, and means the same thing as "out-of-box experience" (OOBE). This section will walk you through the process.
-
-By now, you should have gone through all of the previous steps:
-
-- [Prepare your environment for Surface Hub](prepare-your-environment-for-surface-hub.md)
-- [Physically install your Surface Hub device](physically-install-your-surface-hub-device.md), and
-- [Setup worksheet](setup-worksheet-surface-hub.md)
-
-Assuming that's the case, first run should be both simple and quick.
-The normal procedure goes through six steps:
-
-1. [Hi there page](#first-page)
-2. [Set up for you page](#set-up-for-you)
-3. [Device account page](#device-account)
-4. [Name this device page](#name-this-device)
-5. [Set up admins for this device page](#setup-admins)
-6. [Update the Surface Hub](#update-surface-hub)
-
-Each of these sections also contains information about paths you might take when something is different. For example, most Surface Hubs will use a wired network connection, but some of them will be set up with wireless instead. Details are described where appropriate.
-
->[!NOTE]
->You should have the separate keyboard that came with your Surface Hub set up and ready before beginning. See the Surface Hub Setup Guide for details.
-
-
-
-## Hi there page
-
-
-This is the first screen you'll see when you power up the Surface Hub for the first time. It's where you input localization information for your device.
-
->[!NOTE]
->This is also where you begin the optional process of deploying a provisioning package. See [Create provisioning packages](provisioning-packages-for-certificates-surface-hub.md) if that's what you're doing.
-
- Select a language and the initial setup options are displayed.
-
-
-
-### Details
-
-If the default values shown are correct, then you can click **Next** to go on. Otherwise, you'll need to enter data in the appropriate boxes.
-
-- **Country/region:** Select the country or region where the Surface Hub will be used.
-- **App language:** Apps and features will display in this language and language format.
-- **Keyboard layout:** Select the keyboard layout for the on-screen and physical keyboards that will be used with your device.
-- **Time zone:** Select the time zone where the Surface Hub will be used.
-
-### What happens?
-
->[!NOTE]
-> Once the settings on this page are entered, you can't come back to this screen unless you reset the device (see [Device reset](device-reset-surface-hub.md)). Make sure that the settings are properly configured before proceeding.
-
-
-
-When the settings are accepted, the device will check for a wired network connection. If the connection is fine, it will display the [Set up for you page](#set-up-for-you). If there is a problem with the wired connection, the device will display the [Network setup page](#network-setup).
-
-If no wired connection can be found, then the device will attempt to set up a wireless connection, and will display the [Network setup page](#network-setup).
-
-## Network setup page
-
-
-If your device does not detect a wired connection that it can use to connect to a network or the Internet, you will see this page. Here you can either connect to a wireless network, or skip making the network connection.
-
-
-
-### Details
-
-This screen is shown only if the device fails to detect a wired network. If you see this screen, you have three choices:
-
-- You can select one of the wireless networks shown. If the network is secured, you'll be taken to a login page. See [Wireless network setup](#wireless) for details.
-- Click **Skip this step** to skip connecting to a network. You'll be taken to the [Set up for you page](#set-up-for-you).
- >[!NOTE]
- >If you skip this, the device will not have a network connection, and nothing that requires a network connection will work on your Surface Hub, including system updates and email and calendar synchronization. You can connect to a wireless network later using Settings (see [Wireless network management](wireless-network-management-for-surface-hub.md)).
-
-
-
-- You can plug in a network cable while this screen is visible. The device will detect it, and will add **Next** to the screen. Click **Next** to continue with making the wired connection.
-
-### What happens?
-
-If the device has a wired connection when it starts, and can establish a network or Internet connection, then this page will not be displayed. If you want to connect the device to a wireless connection, make sure no Ethernet cable is plugged in at first run, which will bring you to this screen. No matter what you choose to set up now, you can [use Settings](wireless-network-management-for-surface-hub.md) to set up different connections later.
-
-If you want to connect to a secured wireless network from this page, click on the network of your choice, and then provide the necessary information (password or account credentials) to connect. See [Wireless network setup](#wireless).
-
-## Wireless network setup
-
-
-This page will be shown when you've selected a secured wireless network.
-
-
-
-### Details
-
-- **User name:** Enter the user name for the selected wireless network.
-- **Password:** This is the password for the network.
-
-### What happens?
-
-The device will attempt to connect to the specified network. If it's successful, you'll be taken to the [Set up for you page](#set-up-for-you).
-
-## Network proxy setup
-
-
-This page will be shown when the device detects a wired connection with limited connectivity. You have three options:
-
-- You can select a wireless network to use instead of the limited wired connection.
-- You can skip connecting to a network by selecting **Skip this step**. You'll be taken to the [Set up for you page](#set-up-for-you).
- **Note** If you skip this, the device will not have a network connection, and nothing that requires a network connection will work on your Surface Hub, including things like email and calendar synchronization. You can connect to a wireless network later using Settings (see [Wireless network management](wireless-network-management-for-surface-hub.md)).
-
-
-
-- You can select **Enter proxy settings** which will allow you to specify how to use the network proxy. You'll be taken to the next screen.
-
-
-
-This is the screen you'll see if you clicked **Enter proxy settings** on the previous screen.
-
-
-
-### Details
-
-In order to make a network connection, you'll need to fill in either a script name, or the proxy server and port info.
-
-- **Proxy script:** Provide the address of a proxy script.
-- **Proxy server and port:** You can provide the proxy server address and port.
-
-### What happens?
-
-When you click **Next**, the device will attempt to connect to the proxy server. If successful, you'll be taken to the [Set up for you page](#set-up-for-you).
-
-You can skip connecting to a network by selecting **Skip this step**. You'll be taken to the [Set up for you page](#set-up-for-you).
-
->[!NOTE]
->If you skip this, the device will not have a network connection, and nothing that requires a network connection will work on your Surface Hub, including things like email and calendar synchronization. You can connect to a wireless network later using Settings (see [Wireless network management](wireless-network-management-for-surface-hub.md)).
-
-
-
-## Set up for you page
-
-
-This screen is purely informational, and shows which recommended settings have been enabled by default.
-
-
-
-### Details
-
-You should read this screen and note which services have been enabled by default. All of them can be changed using the Settings app if need be, but you should be careful about the effects of doing so. See [Intro to Surface Hub](intro-to-surface-hub.md) for details.
-
-Once you're done reviewing the settings, click **Next** to go on.
-
-### What happens?
-
-The settings shown on the page have already been made, and can't be changed until after first run is completed.
-
-## Device account page
-
-
-On this page, the Surface Hub will ask for credentials for the device account that you previously configured. (See [Create and test a device account](create-and-test-a-device-account-surface-hub.md).) The Surface Hub will attempt to discover various properties of the account, and may ask for more information on another page if it does not succeed.
-
->[!NOTE]
->This section does not cover specific errors that can happen during first run. See [Troubleshoot Surface Hub](troubleshoot-surface-hub.md) for more information on errors.
-
-
-
-
-### Details
-
-Use either a **user principal name (UPN)** or a **domain\\user name** as the account identifier in the first entry field. Use the format that matches your environment, and enter the password.
-
-
-| Environment | Required format for device account |
-|-------------------------------------------------------|------------------------------------|
-| Device account is hosted only online. | username@domain.com |
-| Device account is hosted only on-prem. | DOMAIN\username |
-| Device account is hosted online and on-prem (hybrid). | DOMAIN\username |
-
-Click **Skip setting up a device account** to skip setting up a device account. However, if you don't set up a device account, the device will not be fully integrated into your infrastructure. For example, people won't be able to:
-
-- See a meeting calendar on the Welcome screen
-- Start a meeting from the Welcome screen
-- Email whiteboards from OneNote
-- Use Skype for Business for meetings
-
-If you skip setting it up now, you can add a device account later by using the Settings app.
-
-If you click **Skip setting up a device account**, the device will display a dialog box showing what will happen if the device doesn't have a device account. If you choose **Yes, skip this**, you will be sent to the [Name this device page](#name-this-device).
-
-
-
-### What happens?
-
-The device will use the UPN or DOMAIN\\User name and password for the device account to do the following:
-
-- Check if the account exists in Active Directory (AD) or Azure Active Directory (Azure AD):
-
- - If a UPN was entered: the device will look for the account in Azure AD.
- - If a DOMAIN\\User name was entered: the device will look for the account in AD.
-- Look up the Microsoft Exchange server for the account’s mailbox.
-- Look up the Session Initiation Protocol (SIP) address for the account.
-- Pull the account’s display name and alias attributes.
-
-## Exchange server page
-
-
-This page will only be shown if there's a problem. Typically, it means that the device account that you provided was found in Active Directory (AD) or Azure Active Directory (Azure AD), but the Exchange server for the account was not discovered.
-
-
-
-### Details
-
-Enter the name of the Exchange server where the device account's mailbox is hosted.
-
-Click **Skip setting up Exchange services** to skip this step. If you do, people will not be able to:
-
-- See a meeting calendar on the welcome screen.
-- Start a meeting from the welcome screen.
-- Email whiteboards from OneNote.
-
-See [Intro to Surface Hub](intro-to-surface-hub.md) for details on setup dependencies.
-
-You can enable Exchange services for a device account later by using the Settings app.
-
-If you click **Skip setting up Exchange services**, the device will display a dialog showing what will happen. If you choose **Yes, skip this**, then Exchange services will not be set up.
-
-
-
-### What happens?
-
-The Surface Hub will attempt to validate the device account on the Exchange server that you enter here. If the Exchange server can be reached and validates, then first run will proceed.
-
-If you choose to skip setting up Exchange services, the Surface Hub will stop looking for the Exchange server, and no Exchange services (mail and calendar) will be enabled.
-
-## Exchange policies page
-
-
-This page will be shown when:
-
-- The device account is using an Exchange Active Sync (EAS) policy where the PasswordEnabled policy is set to 1.
-- There’s no connection to Exchange.
-- Exchange returns a status code indicating an error. (For example: The account has been provisioned to too many devices.)
-- Exchange supported protocols are not supported by the Surface Hub.
-- Exchange returns incorrect XML.
-
-
-
-### Details
-
-This page is purely informational, so no input is required. However, you have two options for proceeding: either skipping ahead or retrying the validation that caused the error. Before deciding which option is best, please read the following **What happens?** section. You may be able to fix the problem elsewhere before you click on one of the options.
-
-- **Click here to continue using unsupported policies**: click on this to continue first run. The Surface Hub will not be able to use Exchange services, or sync.
-- **Retry**: check the policy on the Exchange server again.
-
-### What happens?
-
-The Surface Hub checks whether the device account’s EAS policy has the PasswordEnabled policy set to 0 (False). If this is not the case, mail and calendar can't be synced and the Surface Hub can't use any Exchange services. You can use your Exchange management tools from a PC to check that the device account has the PasswordEnabled policy set to 0. If that's not the case, you can reconfigure the account and click **Retry** here.
-
-If the policy has already been configured properly, check that your device is properly connected to the network or Internet, and can reach your Exchange server, because this page will also be shown if the Surface Hub can't reach the Exchange server.
-
-Another possible reason for not being able to reach Exchange is because of certificate-based authentication. You may wind up on this page because of certificate issues. Note that if the device displays error codes 0x80072F0D or 0X800C0019, then a certificate is required. Because provisioning is done on the first page of the first run process, you must disable Exchange services by clicking **Click here to continue using unsupported policies**, and then install the correct certificates through the Settings app.
-
-If you choose to skip this check, the Surface Hub will stop looking for the Exchange server and validating EAS policies, and no Exchange services will be enabled. See [Intro to Surface Hub](intro-to-surface-hub.md) for details on setup dependencies.
-
-## Name this device page
-
-
-This page asks you to provide two names that will be used for identifying the Surface Hub.
-
-
-
-### Details
-
-If the default values shown are correct, then you can click **Next** to go on. Otherwise, enter data in one or both of the text boxes.
-
-- **Friendly name:** This is the name that people will see when they want to wirelessly connect to the Surface Hub.
-- **Device name:** Can be set to any unique name as described on the screen.
-
-As long as both names are within the length requirements and do not use restricted characters, clicking **Next** will take you to the next page, [Set up admins for this device](#setup-admins).
-
-### What happens?
-
-The Surface Hub requires two names for the device, which will default to:
-
-- **Friendly name:** Defaults to the Display Name of the device account
-- **Device name:** Defaults to the alias of the device account
-
-While either of the names can be changed later, keep in mind that:
-
-- The friendly name should be recognizable and different so that people can distinguish one Surface Hub from another when trying to wirelessly connect.
-- If you decide to domain join the device, the device name must not be the same as any other device on the account’s Active Directory domain. The device can't join the domain if it is using the same name as another domain-joined device.
-
->[!NOTE]
->If you want to enable [Miracast over Infrastructure](miracast-over-infrastructure.md), the device name needs to be discoverable via DNS. You can achieve this by either allowing your Surface Hub to register automatically via Dynamic DNS, or by manually creating an A or AAAA record for the Surface Hub's device name.
-
-## Set up admins for this device page
-
-
-On this page, you will choose from several options for how you want to set up admin accounts to locally manage your device.
-
-Because every Surface Hub can be used by any number of authenticated employees, settings are locked down so that they can't change from session to session. Only admins can configure the settings on the device, and on this page, you’ll choose which type of admins have that privilege.
-
->[!NOTE]
->The purpose of this page is primarily to determine who can configure the device from the device’s UI; that is, who can actually visit a device, log in, open up the Settings app, and make changes to the Settings.
-
-
-
-
-
-### Details
-
-Choose one of the three available options:
-
-- **Use Microsoft Azure Active Directory**
-- **Use Active Directory Domain Services**
-- **Use a local admin**
-
-### What happens?
-
-This is what happens when you choose an option.
-
-- **Use Microsoft Azure Active Directory**
-
- Clicking this option allows you to join the device to Azure AD. Once you click **Next**, the device will restart to apply some settings, and then you’ll be taken to the [Use Microsoft Azure Active Directory](#use-microsoft-azure) page and asked to enter credentials that can allow you to join Azure AD. Members of the Azure Global Admins role from the joined organization will be able to use the Settings app. The specific people that will be allowed depends on your Azure AD subscription and how you’ve configured the settings for your Azure AD organization.
-
- > [!IMPORTANT]
- > Administrators added to the Azure Device Administrators role after you join the device to Azure AD will be unable to use the Settings app.
- >
- > If you join Surface Hub to Azure AD during first-run setup, single sign-on (SSO) for Office apps will not work properly. Users will have to sign in to each Office app individually.
-
-- **Use Active Directory Domain Services**
-
- Click this option to join the device to AD. Once you click **Next**, you’ll be taken to the [Use Active Directory Domain Services](#use-active-directory) page and asked to enter credentials that allow you to join the specified domain. After joining, you can pick a security group from the joined domain, and people from that security group will be able to use the Settings app.
-
-- **Use a local admin**
-
- Choosing this option will allow you to create a single local admin. This admin won’t be backed by any directory service, so we recommend you only choose this case if the device does not have access to Azure AD or AD. Once you create an admin’s user name and password on the [Use a local admin](#use-a-local-admin) page, you will need to re-enter those same credentials whenever you open the Settings app.
-
- Note that a local admin must have physical access to the Surface Hub to log in.
-
->[!NOTE]
->After you finish this process, you won't be able to change the device's admin option unless you reset the device.
-
-
-
-### Use Microsoft Azure Active Directory
-
-If you've decided to join your Surface Hub to Azure Active Directory (Azure AD), you'll see this **What happens next** page. Read it and click **Next** to go to the **Let's get you signed in page**.
-
-Joining Azure AD has two primary benefits:
-
-1. Some employees from your organization will be able to access the device as admins, and will be able to start the Settings app and configure the device. People that have admin permissions will be defined in your Azure AD subscription.
-2. If your Azure AD is connected to a mobile device management (MDM) solution, the device will enroll with that MDM solution so you can apply policies and configuration.
-
-
-
-### Details
-
-The following input is required:
-
-- **User's UPN:** The user principal name (UPN) of an account that can join Azure AD.
-- **Password:** The password of the account you’re using to join Azure AD.
-
-
-
-If you get to this point and don't have valid credentials for an Azure AD account, the device will allow you to continue by creating a local admin account. Click **Set up Windows with a local account instead**.
-
-
-
-### What happens?
-
-Once you enter valid Azure AD account credentials, the device will try to join the associated Azure AD organization. If this succeeds, then the device will provision employees in that organization to be local admins on the device. If your Azure AD tenant was configured for it, the device will also enroll into MDM.
-
-### Use Active Directory Domain Services
-
-This page will ask for credentials to join a domain so that the Surface Hub can provision a security group as administrators of the device.
-
-Once the device has been domain joined, you must specify a security group from the domain you joined. This security group will be provisioned as administrators on the Surface Hub, and anyone from the security group can enter their domain credentials to access Settings.
-
-
-
-### Details
-
-The following input is required:
-
-- **Domain:** This is the fully qualified domain name (FQDN) of the domain that you want to join. A security group from this domain can be used to manage the device.
-- **User name:** The user name of an account that has sufficient permission to join the specified domain.
-- **Password:** The password for the account.
-
-After the credentials are verified, you will be asked to type a security group name. This input is required.
-
-
-
-### What happens?
-
-Using the provided domain, account credentials from the [Use Active Directory Domain Services page](#use-active-directory) and the device name from the [Name this device](#name-this-device) page, the Surface Hub will attempt to join the domain. If the join is successful, first run will continue, and will ask for a security group. If the join is not successful, first run will halt and ask you to change the information provided.
-
-If the join is successful, you'll see the **Enter a security group** page. When you click the **Select** button on this page, the device will search for the specified security group on your domain. If found, the group will be verified. Click **Finish** to complete the first run process.
-
->[!NOTE]
->If you domain join the Surface Hub, you can't unjoin the device without resetting it.
-
-
-
-### Use a local admin
-
-If you decide not to use Azure Active Directory (Azure AD) or Active Directory (AD) to manage the Surface Hub, you'll need to create a local admin account.
-
-
-
-### Details
-
-The following input is required:
-
-- **User name:** This is the user name of the local admin account that will be created for this Surface Hub.
-- **Password:** This is the password of the device account.
-- **Re-enter password:** Verifying the password as in the previous box.
-
-### What happens?
-
-This page will attempt to create a new admin account using the credentials that you enter here. If it's successful, then first run will end. If not, you'll be asked for different credentials.
-
-## Update the Surface Hub
-
-
->[!IMPORTANT]
->Before you do the updates, make sure you read [Save your BitLocker key](save-bitlocker-key-surface-hub.md) in order to make sure you have a backup of the key.
-
-
-
-In order to get the latest features and fixes, you should update your Surface Hub as soon as you finish all of the preceding first-run steps.
-
-1. Make sure the device has access to the Windows Update servers or to Windows Server Update Services (WSUS). To configure WSUS, see [Using WSUS](manage-windows-updates-for-surface-hub.md#use-windows-server-update-services).
-2. Open Settings, click **Update & security**, then **Windows Update**, and then click **Check for updates**.
-3. If updates are available, they will be downloaded. Once downloading is complete, click the **Update now** button to install the updates.
-4. Follow the onscreen prompts after the updates are installed. You may need to restart the device.
-
-
-
-
-
-
-
-
-
diff --git a/devices/surface-hub/hybrid-deployment-surface-hub-device-accounts.md b/devices/surface-hub/hybrid-deployment-surface-hub-device-accounts.md
deleted file mode 100644
index 329f00f931..0000000000
--- a/devices/surface-hub/hybrid-deployment-surface-hub-device-accounts.md
+++ /dev/null
@@ -1,413 +0,0 @@
----
-title: Hybrid deployment (Surface Hub)
-description: A hybrid deployment requires special processing to set up a device account for your Microsoft Surface Hub.
-ms.assetid: 7BFBB7BE-F587-422E-9CE4-C9DDF829E4F1
-ms.reviewer:
-manager: laurawi
-keywords: hybrid deployment, device account for Surface Hub, Exchange hosted on-prem, Exchange hosted online
-ms.prod: surface-hub
-ms.sitesec: library
-author: dansimp
-ms.author: dansimp
-ms.topic: article
-ms.date: 08/30/2018
-ms.localizationpriority: medium
----
-
-# Hybrid deployment (Surface Hub)
-
-A hybrid deployment requires special processing to set up a device account for your Microsoft Surface Hub. If you’re using a hybrid deployment, in which your organization has a mix of services, with some hosted on-premises and some hosted online, then your configuration will depend on where each service is hosted. This topic covers hybrid deployments for [Exchange hosted on-premises](#exchange-on-premises), [Exchange hosted online](#exchange-online), Skype for Business on-premises, Skype for Business online, and Skype for Business hybrid. Because there are so many different variations in this type of deployment, it's not possible to provide detailed instructions for all of them. The following process will work for many configurations. If the process isn't right for your setup, we recommend that you use PowerShell (see [Appendix: PowerShell](appendix-a-powershell-scripts-for-surface-hub.md)) to achieve the same end result as documented here, and for other deployment options. You should then use the provided Powershell script to verify your Surface Hub setup. (See [Account Verification Script](appendix-a-powershell-scripts-for-surface-hub.md#acct-verification-ps-scripts).)
-
-> [!NOTE]
-> In an Exchange hybrid environment, follow the steps for [Exchange on-premises](#exchange-on-premises). To move Exchange objects to Office 365, use the [New-MoveRequest](https://docs.microsoft.com/powershell/module/exchange/move-and-migration/new-moverequest?view=exchange-ps) cmdlet.
-
-## Exchange on-premises
-
-Use this procedure if you use Exchange on-premises.
-
-1. For this procedure, you'll be using AD admin tools to add an email address for your on-premises domain account. This account will be synced to Office 365.
-
-- In **Active Directory Users and Computers** AD tool, right-click on the folder or Organizational Unit that your Surface Hub accounts will be created in, click **New**, and **User**.
-- Type the display name from the previous cmdlet into the **Full name** box, and the alias into the **User logon name** box. Click **Next**.
-
-
-
-- Type the password for this account. You'll need to retype it for verification. Make sure the **Password never expires** checkbox is the only option selected.
-
-> **Important** Selecting **Password never expires** is a requirement for Skype for Business on the Surface Hub. Your domain rules may prohibit passwords that don't expire. If so, you'll need to create an exception for each Surface Hub device account.
-
-
-
-- Click **Finish** to create the account.
-
-
-
-2. Enable the remote mailbox.
-
-Open your on-premises Exchange Management Shell with administrator permissions, and run this cmdlet.
-
-```PowerShell
-Enable-RemoteMailbox 'HUB01@contoso.com' -RemoteRoutingAddress 'HUB01@contoso.com' -Room
-```
-
-> [!NOTE]
-> If you don't have an on-premises Exchange environment to run this cmdlet, you can make the same changes directly to the Active Directory object for the account.
->
-> msExchRemoteRecipientType = 33
->
-> msExchRecipientDisplayType = -2147481850
->
-> msExchRecipientTypeDetails = 8589934592
-
-3. After you've created the account, run a directory synchronization. When it's complete, go to the users page in your Microsoft 365 admin center and verify that the account created in the previous steps has merged to online.
-
-4. Connect to Microsoft Exchange Online and set some properties for the account in Office 365.
-
-Start a remote PowerShell session on a PC and connect to Microsoft Exchange. Be sure you have the right permissions set to run the associated cmdlets.
-
-The next steps will be run on your Office 365 tenant.
-
-```PowerShell
-Set-ExecutionPolicy RemoteSigned
-$cred=Get-Credential -Message "Please use your Office 365 admin credentials"
-$sess= New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri 'https://ps.outlook.com/powershell' -Credential $cred -Authentication Basic -AllowRedirection
-Import-PSSession $sess
-```
-
-5. Create a new Exchange ActiveSync policy, or use a compatible existing policy.
-
-After setting up the mailbox, you will need to either create a new Exchange ActiveSync policy or use a compatible existing policy.
-
-Surface Hubs are only compatible with device accounts that have an ActiveSync policy where the **PasswordEnabled** property is set to False. If this isn’t set properly, then Exchange services on the Surface Hub (mail, calendar, and joining meetings), will not be enabled.
-
-If you haven’t created a compatible policy yet, use the following cmdlet—this one creates a policy called "Surface Hubs". Once it’s created, you can apply the same policy to other device accounts.
-
-```PowerShell
-$easPolicy = New-MobileDeviceMailboxPolicy -Name “SurfaceHubs” -PasswordEnabled $false
-```
-
-Once you have a compatible policy, you will need to apply the policy to the device account.
-
-```PowerShell
-Set-CASMailbox 'HUB01@contoso.com' -ActiveSyncMailboxPolicy $easPolicy.id
-```
-
-6. Set Exchange properties.
-
-Setting Exchange properties on the device account to improve the meeting experience. You can see which properties need to be set in the [Exchange properties](exchange-properties-for-surface-hub-device-accounts.md) section.
-
-```PowerShell
-Set-CalendarProcessing -Identity 'HUB01@contoso.com' -AutomateProcessing AutoAccept -AddOrganizerToSubject $false –AllowConflicts $false –DeleteComments $false -DeleteSubject $false -RemovePrivateProperty $false
-Set-CalendarProcessing -Identity 'HUB01@contoso.com' -AddAdditionalResponse $true -AdditionalResponse 'This is a Surface Hub room!'
-```
-
-7. Connect to Azure AD.
-
-You first need to install Azure AD module for PowerShell version 2. In an elevated PowerShell prompt, run the following command:
-
-```PowerShell
-Install-Module -Name AzureAD
-```
-
-You need to connect to Azure AD to apply some account settings. You can run this cmdlet to connect.
-
-```PowerShell
-Import-Module AzureAD
-Connect-AzureAD -Credential $cred
-```
-
-8. Assign an Office 365 license.
-
-The device account needs to have a valid Office 365 (O365) license, or Exchange and Skype for Business will not work. If you have the license, you need to assign a usage location to your device account—this determines what license SKUs are available for your account.
-
-You can use `Get-AzureADSubscribedSku` to retrieve a list of available SKUs for your O365 tenant.
-
-Once you list out the SKUs, you'll need to assign the SkuId you want to the `$License.SkuId` variable.
-
-```PowerShell
-Set-AzureADUser -ObjectId "HUB01@contoso.com" -UsageLocation "US"
-
-Get-AzureADSubscribedSku | Select Sku*,*Units
-$License = New-Object -TypeName Microsoft.Open.AzureAD.Model.AssignedLicense
-$License.SkuId = SkuId You selected
-
-$AssignedLicenses = New-Object -TypeName Microsoft.Open.AzureAD.Model.AssignedLicenses
-$AssignedLicenses.AddLicenses = $License
-$AssignedLicenses.RemoveLicenses = @()
-
-Set-AzureADUserLicense -ObjectId "HUB01@contoso.com" -AssignedLicenses $AssignedLicenses
-```
-
-Next, you enable the device account with [Skype for Business Online](#skype-for-business-online), [Skype for Business on-premises](#skype-for-business-on-premises), or [Skype for Business hybrid](#skype-for-business-hybrid).
-
-### Skype for Business Online
-
-To enable Skype for Business online, your tenant users must have Exchange mailboxes (at least one Exchange mailbox in the tenant is required). The following table explains which plans or additional services you need.
-
-| Skype room system scenario | If you have Office 365 Premium, Microsoft 365 Apps for enterprise, or Skype for Business Standalone Plan 2, you need: | If you have an Enterprise-based plan, you need: | If you have Skype for Business Server 2015 (on-premises or hybrid), you need: |
-| --- | --- | --- | --- |
-| Join a scheduled meeting | Skype for Business Standalone Plan 1 | E1, 3, 4, or 5 | Skype for Business Server Standard CAL |
-| Initiate an ad-hoc meeting | Skype for Business Standalone Plan 2 | E 1, 3, 4, or 5 | Skype for Business Server Standard CAL or Enterprise CAL |
-| Initiate an ad-hoc meeting and dial out from a meeting to phone numbers | Skype for Business Standalone Plan 2 with Audio Conferencing**Note** PSTN consumption billing is optional | E1 or E3 with Audio Conferencing, or E5| Skype for Business Server Standard CAL or Enterprise CAL |
-| Give the room a phone number and make or receive calls from the room or join a dial-in conference using a phone number | Skype for Business Standalone Plan 2 with Phone System and a PSTN Voice Calling plan | E1 or E3 with Phone System and a PSTN Voice Calling plan, or E5 | Skype for Business Server Standard CAL or Plus CAL |
-
-The following table lists the Office 365 plans and Skype for Business options.
-
-| O365 Plan | Skype for Business | Phone System | Audio Conferencing | Calling Plans |
-| --- | --- | --- | --- | --- |
-| O365 Business Essentials | Included | | | |
-| O365 Business Premium | Included | | | |
-| E1 | Included | Add-on | Add-on | Add-on (requires Phone System add-on) |
-| E3 | Included | Add-on | Add-on | Add-on (requires Phone System add-on) |
-| E5 | Included | Included | Included | Add-on |
-
-1. Start by creating a remote PowerShell session from a PC to the Skype for Business online environment.
-
-```PowerShell
-Import-Module SkypeOnlineConnector
-$cssess=New-CsOnlineSession -Credential $cred
-Import-PSSession $cssess -AllowClobber
-```
-
-2. To enable your Surface Hub account for Skype for Business Server, run this cmdlet:
-
-```PowerShell
-Enable-CsMeetingRoom -Identity 'HUB01@contoso.com' -RegistrarPool 'sippoolbl20a04.infra.lync.com' -SipAddressType UserPrincipalName
-```
-
-If you aren't sure what value to use for the `RegistrarPool` parameter in your environment, you can get the value from an existing Skype for Business user using this cmdlet:
-
-```PowerShell
-Get-CsOnlineUser -Identity ‘HUB01@contoso.com’| fl *registrarpool*
-```
-
-3. Assign Skype for Business license to your Surface Hub account.
-
- Once you've completed the preceding steps to enable your Surface Hub account in Skype for Business Online, you need to assign a license to the Surface Hub. Using the O365 administrative portal, assign either a Skype for Business Online (Plan 2) or a Skype for Business Online (Plan 3) license to the device.
-
-- Login as a tenant administrator, open the O365 Administrative Portal, and click on the Admin app.
-
-- Click on **Users and Groups** and then **Add users, reset passwords, and more**.
-
-- Click the Surface Hub account, and then click the pen icon to edit the account information.
-
-- Click **Licenses**.
-
-- In **Assign licenses**, select Skype for Business (Plan 1) or Skype for Business (Plan 2), depending on your licensing and Enterprise Voice requirements. You'll have to use a Plan 2 license if you want to use Enterprise Voice on your Surface Hub.
-
-- Click **Save**.
-
-> [!NOTE]
-> You can also use the Windows Azure Active Directory Module for Windows Powershell to run the cmdlets needed to assign one of these licenses, but that's not covered here.
-
-For validation, you should be able to use any Skype for Business client (PC, Android, etc.) to sign in to this account.
-
-### Skype for Business on-premises
-
-To run this cmdlet, you will need to connect to one of the Skype front-ends. Open the Skype PowerShell and run:
-
-```PowerShell
-Enable-CsMeetingRoom -Identity 'HUB01@contoso.com' -RegistrarPool registrarpoolfqdn -SipAddressType UserPrincipalName
-```
-
-### Skype for Business hybrid
-
-If your organization has set up [hybrid connectivity between Skype for Business Server and Skype for Business Online](https://technet.microsoft.com/library/jj205403.aspx), the guidance for creating accounts differs from a standard Surface Hub deployment.
-
-The Surface Hub requires a Skype account of the type `meetingroom`, while a normal user would use a user type account in Skype. If your Skype server is set up for hybrid where you might have users on the local Skype server as well as users hosted in Office 365, you might run into a few issues when trying to create a Surface Hub account.
-
-In Skype for Business Server 2015 hybrid environment, any user that you want in Skype for Business Online must first be created in the on-premises deployment, so that the user account is created in Active Directory Domain Services. You can then move the user to Skype for Business Online. The move of a user account from on-premises to online is done via the [Move-CsUser](https://technet.microsoft.com/library/gg398528.aspx) cmdlet. To move a Csmeetingroom object, use the [Move-CsMeetingRoom](https://technet.microsoft.com/library/jj204889.aspx?f=255&mspperror=-2147217396) cmdlet.
-
-> [!NOTE]
-> To use the Move-CsMeetingRoom cmdlet, you must have installed [the May 2017 cumulative update 6.0.9319.281 for Skype for Business Server 2015](https://support.microsoft.com/help/4020991/enables-the-move-csmeetingroom-cmdlet-to-move-a-meeting-room-from-on-p) or [the July 2017 cumulative update 5.0.8308.992 for Lync Server 2013](https://support.microsoft.com/help/4034279/enables-the-move-csmeetingroom-cmdlet-to-move-a-meeting-room-from-on-p).
-
-
-## Exchange online
-
-Use this procedure if you use Exchange online.
-
-1. Create an email account in Office 365.
-
-Start a remote PowerShell session on a PC and connect to Exchange. Be sure you have the right permissions set to run the associated cmdlets.
-
-```PowerShell
-Set-ExecutionPolicy RemoteSigned
-$cred=Get-Credential -Message "Please use your Office 365 admin credentials"
-$sess= New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://outlook.office365.com/PowerShell-liveid/ -Credential $cred -Authentication Basic -AllowRedirection
-Import-PSSession $sess
-```
-
-2. Set up a mailbox.
-
-After establishing a session, you’ll either create a new mailbox and enable it as a RoomMailboxAccount, or change the settings for an existing room mailbox. This will allow the account to authenticate into the Surface Hub.
-
-If you're changing an existing resource mailbox:
-
-```PowerShell
-Set-Mailbox -Identity 'HUB01' -EnableRoomMailboxAccount $true -RoomMailboxPassword (ConvertTo-SecureString -String -AsPlainText -Force)
-```
-
-If you’re creating a new resource mailbox:
-
-```PowerShell
-New-Mailbox -MicrosoftOnlineServicesID 'HUB01@contoso.com' -Alias HUB01 -Name "Hub-01" -Room -EnableRoomMailboxAccount $true -RoomMailboxPassword (ConvertTo-SecureString -String -AsPlainText -Force)
-```
-
-3. Create Exchange ActiveSync policy.
-
-After setting up the mailbox, you will need to either create a new Exchange ActiveSync policy, or use a compatible existing policy.
-
-Surface Hubs are only compatible with device accounts that have an ActiveSync policy where the **PasswordEnabled** property is set to False. If this isn’t set properly, Exchange services on the Surface Hub (mail, calendar, and joining meetings) will not be enabled.
-
-If you haven’t created a compatible policy yet, use the following cmdlet—this one creates a policy called "Surface Hubs". Once it’s created, you can apply the same policy to other device accounts.
-
-```PowerShell
-$easPolicy = New-MobileDeviceMailboxPolicy -Name “SurfaceHubs” -PasswordEnabled $false
-```
-
-Once you have a compatible policy, you will need to apply the policy to the device account. However, policies can only be applied to user accounts and not resource mailboxes. You need to convert the mailbox into a user type, apply the policy, and then convert it back into a mailbox—you may need to re-enable it and set the password again too.
-
-```PowerShell
-Set-Mailbox 'HUB01@contoso.com' -Type Regular
-Set-CASMailbox 'HUB01@contoso.com' -ActiveSyncMailboxPolicy $easPolicy.id
-Set-Mailbox 'HUB01@contoso.com' -Type Room
-$credNewAccount = Get-Credential -Message "Please provide the Surface Hub username and password"
-Set-Mailbox 'HUB01@contoso.com' -RoomMailboxPassword $credNewAccount.Password -EnableRoomMailboxAccount $true
-```
-
-4. Set Exchange properties.
-
-Various Exchange properties must be set on the device account to improve the meeting experience. You can see which properties need to be set in the [Exchange properties](exchange-properties-for-surface-hub-device-accounts.md) section.
-
-```PowerShell
-Set-CalendarProcessing -Identity 'HUB01@contoso.com' -AutomateProcessing AutoAccept -AddOrganizerToSubject $false –AllowConflicts $false –DeleteComments $false -DeleteSubject $false -RemovePrivateProperty $false
-Set-CalendarProcessing -Identity 'HUB01@contoso.com' -AddAdditionalResponse $true -AdditionalResponse "This is a Surface Hub room!"
-```
-
-5. Add an email address for your on-premises domain account.
-
-For this procedure, you'll be using AD admin tools to add an email address for your on-premises domain account.
-
-- In **Active Directory Users and Computers** AD tool, right-click on the folder or Organizational Unit that your Surface Hub accounts will be created in, click **New**, and **User**.
-- Type the display name from the previous cmdlet into the **Full name** box, and the alias into the **User logon name** box. Click **Next**.
-
-
-
-- Type the password for this account. You'll need to retype it for verification. Make sure the **Password never expires** checkbox is the only option selected.
-
-> [!IMPORTANT]
-> Selecting **Password never expires** is a requirement for Skype for Business on the Surface Hub. Your domain rules may prohibit passwords that don't expire. If so, you'll need to create an exception for each Surface Hub device account.
-
-
-
-- Click **Finish** to create the account.
-
-
-
-6. Run directory synchronization.
-
-After you've created the account, run a directory synchronization. When it's complete, go to the users page and verify that the two accounts created in the previous steps have merged.
-
-7. Connect to Azure AD.
-
-You first need to install Azure AD module for PowerShell version 2. In an elevated PowerShell prompt, run the following command:
-
-```PowerShell
-Install-Module -Name AzureAD
-```
-
-You need to connect to Azure AD to apply some account settings. You can run this cmdlet to connect:
-
-```PowerShell
-Import-Module AzureAD
-Connect-AzureAD -Credential $cred
-```
-
-8. Assign an Office 365 license.
-
-The device account needs to have a valid Office 365 (O365) license, or Exchange and Skype for Business will not work. If you have the license, you need to assign a usage location to your device account—this determines what license SKUs are available for your account.
-
-Next, you can use `Get-AzureADSubscribedSku` to retrieve a list of available SKUs for your O365 tenant.
-
-Once you list out the SKUs, you'll need to assign the SkuId you want to the `$License.SkuId` variable.
-
-```PowerShell
-Set-AzureADUser -ObjectId "HUB01@contoso.com" -UsageLocation "US"
-
-Get-AzureADSubscribedSku | Select Sku*,*Units
-$License = New-Object -TypeName Microsoft.Open.AzureAD.Model.AssignedLicense
-$License.SkuId = SkuId You selected
-
-$AssignedLicenses = New-Object -TypeName Microsoft.Open.AzureAD.Model.AssignedLicenses
-$AssignedLicenses.AddLicenses = $License
-$AssignedLicenses.RemoveLicenses = @()
-
-Set-AzureADUserLicense -ObjectId "HUB01@contoso.com" -AssignedLicenses $AssignedLicenses
-```
-
-Next, you enable the device account with [Skype for Business Online](#skype-for-business-online), [Skype for Business on-premises](#skype-for-business-on-premises), or [Skype for Business hybrid](#skype-for-business-hybrid).
-
-### Skype for Business Online
-
-In order to enable Skype for Business, your environment will need to meet the [prerequisites for Skype for Business online](#skype-for-business-online).
-
-1. Start by creating a remote PowerShell session to the Skype for Business online environment from a PC.
-
-```PowerShell
-Import-Module SkypeOnlineConnector
-$cssess=New-CsOnlineSession -Credential $cred
-Import-PSSession $cssess -AllowClobber
-```
-
-2. To enable your Surface Hub account for Skype for Business Server, run this cmdlet:
-
-```PowerShell
-Enable-CsMeetingRoom -Identity 'HUB01@contoso.com' -RegistrarPool
-'sippoolbl20a04.infra.lync.com' -SipAddressType UserPrincipalName
-```
-
- If you aren't sure what value to use for the `RegistrarPool` parameter in your environment, you can get the value from an existing Skype for Business user using this cmdlet:
-
-```PowerShell
-Get-CsOnlineUser -Identity 'HUB01@contoso.com'| fl *registrarpool*
-```
-
-10. Assign Skype for Business license to your Surface Hub account
-
-Once you've completed the preceding steps to enable your Surface Hub account in Skype for Business Online, you need to assign a license to the Surface Hub. Using the O365 administrative portal, assign either a Skype for Business Online (Plan 2) or a Skype for Business Online (Plan 3) license to the device.
-
-- Sign in as a tenant administrator, open the O365 Administrative Portal, and click on the Admin app.
-
-- Click on **Users and Groups** and then **Add users, reset passwords, and more**.
-
-- Click the Surface Hub account, and then click the pen icon to edit the account information.
-
-- Click **Licenses**.
-
-- In **Assign licenses**, select Skype for Business (Plan 2) or Skype for Business (Plan 3), depending on your licensing and Enterprise Voice requirements. You'll have to use a Plan 3 license if you want to use Enterprise Voice on your Surface Hub.
-
-- Click **Save**.
-
-> [!NOTE]
-> You can also use the Windows Azure Active Directory Module for Windows PowerShell to run the cmdlets needed to assign one of these licenses, but that's not covered here.
-
-For validation, you should be able to use any Skype for Business client (PC, Android, etc) to sign in to this account.
-
-### Skype for Business on-premises
-
-To run this cmdlet, you will need to connect to one of the Skype front-ends. Open the Skype PowerShell and run:
-
-```PowerShell
-Enable-CsMeetingRoom -Identity 'HUB01@contoso.com' -RegistrarPool registrarpoolfqdn -SipAddressType UserPrincipalName
-```
-
-### Skype for Business hybrid
-
-If your organization has set up [hybrid connectivity between Skype for Business Server and Skype for Business Online](https://technet.microsoft.com/library/jj205403.aspx), the guidance for creating accounts differs from a standard Surface Hub deployment.
-
-The Surface Hub requires a Skype account of the type *meetingroom*, while a normal user would use a *user* type account in Skype. If your Skype server is set up for hybrid where you might have users on the local Skype server as well as users hosted in Office 365, you might run into a few issues when trying to create a Surface Hub account.
-
-In Skype for Business Server 2015 hybrid environment, any user that you want in Skype for Business Online must first be created in the on-premises deployment, so that the user account is created in Active Directory Domain Services. You can then move the user to Skype for Business Online. The move of a user account from on-premises to online is done via the [Move-CsUser](https://technet.microsoft.com/library/gg398528.aspx) cmdlet. To move a Csmeetingroom object, use the [Move-CsMeetingRoom](https://technet.microsoft.com/library/jj204889.aspx?f=255&mspperror=-2147217396) cmdlet.
-
-> [!NOTE]
-> To use the Move-CsMeetingRoom cmdlet, you must have installed [the May 2017 cumulative update 6.0.9319.281 for Skype for Business Server 2015](https://support.microsoft.com/help/4020991/enables-the-move-csmeetingroom-cmdlet-to-move-a-meeting-room-from-on-p) or [the July 2017 cumulative update 5.0.8308.992 for Lync Server 2013](https://support.microsoft.com/help/4034279/enables-the-move-csmeetingroom-cmdlet-to-move-a-meeting-room-from-on-p).
diff --git a/devices/surface-hub/images/01-diagnostic.png b/devices/surface-hub/images/01-diagnostic.png
deleted file mode 100644
index fde5951776..0000000000
Binary files a/devices/surface-hub/images/01-diagnostic.png and /dev/null differ
diff --git a/devices/surface-hub/images/01-escape.png b/devices/surface-hub/images/01-escape.png
deleted file mode 100644
index badfc5883d..0000000000
Binary files a/devices/surface-hub/images/01-escape.png and /dev/null differ
diff --git a/devices/surface-hub/images/02-all-apps.png b/devices/surface-hub/images/02-all-apps.png
deleted file mode 100644
index a29e9d8428..0000000000
Binary files a/devices/surface-hub/images/02-all-apps.png and /dev/null differ
diff --git a/devices/surface-hub/images/02-skip-this-drive.png b/devices/surface-hub/images/02-skip-this-drive.png
deleted file mode 100644
index 930f0b26d3..0000000000
Binary files a/devices/surface-hub/images/02-skip-this-drive.png and /dev/null differ
diff --git a/devices/surface-hub/images/03-recover-from-cloud.png b/devices/surface-hub/images/03-recover-from-cloud.png
deleted file mode 100644
index be422cecc8..0000000000
Binary files a/devices/surface-hub/images/03-recover-from-cloud.png and /dev/null differ
diff --git a/devices/surface-hub/images/03-welcome.png b/devices/surface-hub/images/03-welcome.png
deleted file mode 100644
index b71ebe0752..0000000000
Binary files a/devices/surface-hub/images/03-welcome.png and /dev/null differ
diff --git a/devices/surface-hub/images/04-test-results-1.png b/devices/surface-hub/images/04-test-results-1.png
deleted file mode 100644
index e0b53f2dc3..0000000000
Binary files a/devices/surface-hub/images/04-test-results-1.png and /dev/null differ
diff --git a/devices/surface-hub/images/04-yes.png b/devices/surface-hub/images/04-yes.png
deleted file mode 100644
index 9c26b795ce..0000000000
Binary files a/devices/surface-hub/images/04-yes.png and /dev/null differ
diff --git a/devices/surface-hub/images/05-test-results-2.png b/devices/surface-hub/images/05-test-results-2.png
deleted file mode 100644
index 55b7c7abed..0000000000
Binary files a/devices/surface-hub/images/05-test-results-2.png and /dev/null differ
diff --git a/devices/surface-hub/images/05a-reinstall.png b/devices/surface-hub/images/05a-reinstall.png
deleted file mode 100644
index 60d90928ba..0000000000
Binary files a/devices/surface-hub/images/05a-reinstall.png and /dev/null differ
diff --git a/devices/surface-hub/images/05b-downloading.png b/devices/surface-hub/images/05b-downloading.png
deleted file mode 100644
index 59393e7162..0000000000
Binary files a/devices/surface-hub/images/05b-downloading.png and /dev/null differ
diff --git a/devices/surface-hub/images/06-account-settings.png b/devices/surface-hub/images/06-account-settings.png
deleted file mode 100644
index 35a92f2ff8..0000000000
Binary files a/devices/surface-hub/images/06-account-settings.png and /dev/null differ
diff --git a/devices/surface-hub/images/06-out-of-box.png b/devices/surface-hub/images/06-out-of-box.png
deleted file mode 100644
index a513b46c5b..0000000000
Binary files a/devices/surface-hub/images/06-out-of-box.png and /dev/null differ
diff --git a/devices/surface-hub/images/07-account-settings-details.png b/devices/surface-hub/images/07-account-settings-details.png
deleted file mode 100644
index 421f372b03..0000000000
Binary files a/devices/surface-hub/images/07-account-settings-details.png and /dev/null differ
diff --git a/devices/surface-hub/images/07-cancel.png b/devices/surface-hub/images/07-cancel.png
deleted file mode 100644
index a788960011..0000000000
Binary files a/devices/surface-hub/images/07-cancel.png and /dev/null differ
diff --git a/devices/surface-hub/images/08-test-account.png b/devices/surface-hub/images/08-test-account.png
deleted file mode 100644
index d7cbf9620d..0000000000
Binary files a/devices/surface-hub/images/08-test-account.png and /dev/null differ
diff --git a/devices/surface-hub/images/08-troubleshoot.png b/devices/surface-hub/images/08-troubleshoot.png
deleted file mode 100644
index d2af1969bd..0000000000
Binary files a/devices/surface-hub/images/08-troubleshoot.png and /dev/null differ
diff --git a/devices/surface-hub/images/09-network.png b/devices/surface-hub/images/09-network.png
deleted file mode 100644
index d69f2d67ec..0000000000
Binary files a/devices/surface-hub/images/09-network.png and /dev/null differ
diff --git a/devices/surface-hub/images/09-recover-from-cloud2.png b/devices/surface-hub/images/09-recover-from-cloud2.png
deleted file mode 100644
index 64650a91bb..0000000000
Binary files a/devices/surface-hub/images/09-recover-from-cloud2.png and /dev/null differ
diff --git a/devices/surface-hub/images/10-cancel.png b/devices/surface-hub/images/10-cancel.png
deleted file mode 100644
index ffef745522..0000000000
Binary files a/devices/surface-hub/images/10-cancel.png and /dev/null differ
diff --git a/devices/surface-hub/images/10-environment.png b/devices/surface-hub/images/10-environment.png
deleted file mode 100644
index 376e077249..0000000000
Binary files a/devices/surface-hub/images/10-environment.png and /dev/null differ
diff --git a/devices/surface-hub/images/11-certificates.png b/devices/surface-hub/images/11-certificates.png
deleted file mode 100644
index 13b45396b3..0000000000
Binary files a/devices/surface-hub/images/11-certificates.png and /dev/null differ
diff --git a/devices/surface-hub/images/12-trust-model.png b/devices/surface-hub/images/12-trust-model.png
deleted file mode 100644
index 996bb4fdd4..0000000000
Binary files a/devices/surface-hub/images/12-trust-model.png and /dev/null differ
diff --git a/devices/surface-hub/images/2s-mount-pattern.png b/devices/surface-hub/images/2s-mount-pattern.png
deleted file mode 100644
index 92262fb428..0000000000
Binary files a/devices/surface-hub/images/2s-mount-pattern.png and /dev/null differ
diff --git a/devices/surface-hub/images/35mm.png b/devices/surface-hub/images/35mm.png
deleted file mode 100644
index 7a414337b6..0000000000
Binary files a/devices/surface-hub/images/35mm.png and /dev/null differ
diff --git a/devices/surface-hub/images/ICDstart-option.PNG b/devices/surface-hub/images/ICDstart-option.PNG
deleted file mode 100644
index 1ba49bb261..0000000000
Binary files a/devices/surface-hub/images/ICDstart-option.PNG and /dev/null differ
diff --git a/devices/surface-hub/images/OOBE-2.jpg b/devices/surface-hub/images/OOBE-2.jpg
deleted file mode 100644
index 0c615a2ec4..0000000000
Binary files a/devices/surface-hub/images/OOBE-2.jpg and /dev/null differ
diff --git a/devices/surface-hub/images/account-management-details.PNG b/devices/surface-hub/images/account-management-details.PNG
deleted file mode 100644
index 66712394ec..0000000000
Binary files a/devices/surface-hub/images/account-management-details.PNG and /dev/null differ
diff --git a/devices/surface-hub/images/account-management.PNG b/devices/surface-hub/images/account-management.PNG
deleted file mode 100644
index 34165dfcd6..0000000000
Binary files a/devices/surface-hub/images/account-management.PNG and /dev/null differ
diff --git a/devices/surface-hub/images/add-applications-details.PNG b/devices/surface-hub/images/add-applications-details.PNG
deleted file mode 100644
index 2efd3483ae..0000000000
Binary files a/devices/surface-hub/images/add-applications-details.PNG and /dev/null differ
diff --git a/devices/surface-hub/images/add-applications.PNG b/devices/surface-hub/images/add-applications.PNG
deleted file mode 100644
index 2316deb2fd..0000000000
Binary files a/devices/surface-hub/images/add-applications.PNG and /dev/null differ
diff --git a/devices/surface-hub/images/add-certificates-details.PNG b/devices/surface-hub/images/add-certificates-details.PNG
deleted file mode 100644
index 78cd783282..0000000000
Binary files a/devices/surface-hub/images/add-certificates-details.PNG and /dev/null differ
diff --git a/devices/surface-hub/images/add-certificates.PNG b/devices/surface-hub/images/add-certificates.PNG
deleted file mode 100644
index 24cb605d1c..0000000000
Binary files a/devices/surface-hub/images/add-certificates.PNG and /dev/null differ
diff --git a/devices/surface-hub/images/add-config-file-details.PNG b/devices/surface-hub/images/add-config-file-details.PNG
deleted file mode 100644
index c7b4db97e6..0000000000
Binary files a/devices/surface-hub/images/add-config-file-details.PNG and /dev/null differ
diff --git a/devices/surface-hub/images/add-config-file.PNG b/devices/surface-hub/images/add-config-file.PNG
deleted file mode 100644
index 5b779509d9..0000000000
Binary files a/devices/surface-hub/images/add-config-file.PNG and /dev/null differ
diff --git a/devices/surface-hub/images/adjust-room-audio.png b/devices/surface-hub/images/adjust-room-audio.png
deleted file mode 100644
index 3d0eef5ed7..0000000000
Binary files a/devices/surface-hub/images/adjust-room-audio.png and /dev/null differ
diff --git a/devices/surface-hub/images/analog.png b/devices/surface-hub/images/analog.png
deleted file mode 100644
index 1f1666903b..0000000000
Binary files a/devices/surface-hub/images/analog.png and /dev/null differ
diff --git a/devices/surface-hub/images/approve-signin.png b/devices/surface-hub/images/approve-signin.png
deleted file mode 100644
index 7736b95431..0000000000
Binary files a/devices/surface-hub/images/approve-signin.png and /dev/null differ
diff --git a/devices/surface-hub/images/approve-signin2.png b/devices/surface-hub/images/approve-signin2.png
deleted file mode 100644
index 2ccfc40ecc..0000000000
Binary files a/devices/surface-hub/images/approve-signin2.png and /dev/null differ
diff --git a/devices/surface-hub/images/apps.png b/devices/surface-hub/images/apps.png
deleted file mode 100644
index 5cb3b7ec8f..0000000000
Binary files a/devices/surface-hub/images/apps.png and /dev/null differ
diff --git a/devices/surface-hub/images/attendees.png b/devices/surface-hub/images/attendees.png
deleted file mode 100644
index fd468aa971..0000000000
Binary files a/devices/surface-hub/images/attendees.png and /dev/null differ
diff --git a/devices/surface-hub/images/caution.PNG b/devices/surface-hub/images/caution.PNG
deleted file mode 100644
index 0f87b07c0f..0000000000
Binary files a/devices/surface-hub/images/caution.PNG and /dev/null differ
diff --git a/devices/surface-hub/images/choose-package.png b/devices/surface-hub/images/choose-package.png
deleted file mode 100644
index 2bf7a18648..0000000000
Binary files a/devices/surface-hub/images/choose-package.png and /dev/null differ
diff --git a/devices/surface-hub/images/configmgr-additional.png b/devices/surface-hub/images/configmgr-additional.png
deleted file mode 100644
index 7c8fbf8e2f..0000000000
Binary files a/devices/surface-hub/images/configmgr-additional.png and /dev/null differ
diff --git a/devices/surface-hub/images/configmgr-create.png b/devices/surface-hub/images/configmgr-create.png
deleted file mode 100644
index 1db436d3ad..0000000000
Binary files a/devices/surface-hub/images/configmgr-create.png and /dev/null differ
diff --git a/devices/surface-hub/images/configmgr-oma-uri.png b/devices/surface-hub/images/configmgr-oma-uri.png
deleted file mode 100644
index 699bc054a1..0000000000
Binary files a/devices/surface-hub/images/configmgr-oma-uri.png and /dev/null differ
diff --git a/devices/surface-hub/images/configmgr-platform.png b/devices/surface-hub/images/configmgr-platform.png
deleted file mode 100644
index e857c50cc3..0000000000
Binary files a/devices/surface-hub/images/configmgr-platform.png and /dev/null differ
diff --git a/devices/surface-hub/images/configmgr-team.png b/devices/surface-hub/images/configmgr-team.png
deleted file mode 100644
index f99acd5738..0000000000
Binary files a/devices/surface-hub/images/configmgr-team.png and /dev/null differ
diff --git a/devices/surface-hub/images/connect-aad.png b/devices/surface-hub/images/connect-aad.png
deleted file mode 100644
index 8583866165..0000000000
Binary files a/devices/surface-hub/images/connect-aad.png and /dev/null differ
diff --git a/devices/surface-hub/images/deploy1.png b/devices/surface-hub/images/deploy1.png
deleted file mode 100644
index 1c5c119303..0000000000
Binary files a/devices/surface-hub/images/deploy1.png and /dev/null differ
diff --git a/devices/surface-hub/images/deploy2.png b/devices/surface-hub/images/deploy2.png
deleted file mode 100644
index 2b035e979f..0000000000
Binary files a/devices/surface-hub/images/deploy2.png and /dev/null differ
diff --git a/devices/surface-hub/images/deploy3.png b/devices/surface-hub/images/deploy3.png
deleted file mode 100644
index 56621a24dc..0000000000
Binary files a/devices/surface-hub/images/deploy3.png and /dev/null differ
diff --git a/devices/surface-hub/images/deploymentoptions-01.png b/devices/surface-hub/images/deploymentoptions-01.png
deleted file mode 100644
index 05a5eb45c6..0000000000
Binary files a/devices/surface-hub/images/deploymentoptions-01.png and /dev/null differ
diff --git a/devices/surface-hub/images/developer-setup.PNG b/devices/surface-hub/images/developer-setup.PNG
deleted file mode 100644
index 8c93d5ed91..0000000000
Binary files a/devices/surface-hub/images/developer-setup.PNG and /dev/null differ
diff --git a/devices/surface-hub/images/device-family.png b/devices/surface-hub/images/device-family.png
deleted file mode 100644
index 1efe12fc57..0000000000
Binary files a/devices/surface-hub/images/device-family.png and /dev/null differ
diff --git a/devices/surface-hub/images/dport.png b/devices/surface-hub/images/dport.png
deleted file mode 100644
index 2842f96ad4..0000000000
Binary files a/devices/surface-hub/images/dport.png and /dev/null differ
diff --git a/devices/surface-hub/images/dportio.png b/devices/surface-hub/images/dportio.png
deleted file mode 100644
index 02bf145d60..0000000000
Binary files a/devices/surface-hub/images/dportio.png and /dev/null differ
diff --git a/devices/surface-hub/images/dportout.png b/devices/surface-hub/images/dportout.png
deleted file mode 100644
index 4b6bb87663..0000000000
Binary files a/devices/surface-hub/images/dportout.png and /dev/null differ
diff --git a/devices/surface-hub/images/ease-of-access.png b/devices/surface-hub/images/ease-of-access.png
deleted file mode 100644
index 2cb79254f8..0000000000
Binary files a/devices/surface-hub/images/ease-of-access.png and /dev/null differ
diff --git a/devices/surface-hub/images/end-session.png b/devices/surface-hub/images/end-session.png
deleted file mode 100644
index 4b28583af4..0000000000
Binary files a/devices/surface-hub/images/end-session.png and /dev/null differ
diff --git a/devices/surface-hub/images/enroll-mdm-details.PNG b/devices/surface-hub/images/enroll-mdm-details.PNG
deleted file mode 100644
index f3a7fea8da..0000000000
Binary files a/devices/surface-hub/images/enroll-mdm-details.PNG and /dev/null differ
diff --git a/devices/surface-hub/images/enroll-mdm.PNG b/devices/surface-hub/images/enroll-mdm.PNG
deleted file mode 100644
index b7cfdbc767..0000000000
Binary files a/devices/surface-hub/images/enroll-mdm.PNG and /dev/null differ
diff --git a/devices/surface-hub/images/express-settings.png b/devices/surface-hub/images/express-settings.png
deleted file mode 100644
index 99e9c4825a..0000000000
Binary files a/devices/surface-hub/images/express-settings.png and /dev/null differ
diff --git a/devices/surface-hub/images/finish-details.png b/devices/surface-hub/images/finish-details.png
deleted file mode 100644
index 727efac696..0000000000
Binary files a/devices/surface-hub/images/finish-details.png and /dev/null differ
diff --git a/devices/surface-hub/images/finish.PNG b/devices/surface-hub/images/finish.PNG
deleted file mode 100644
index 7c65da1799..0000000000
Binary files a/devices/surface-hub/images/finish.PNG and /dev/null differ
diff --git a/devices/surface-hub/images/five.png b/devices/surface-hub/images/five.png
deleted file mode 100644
index 961f0e15b7..0000000000
Binary files a/devices/surface-hub/images/five.png and /dev/null differ
diff --git a/devices/surface-hub/images/four.png b/devices/surface-hub/images/four.png
deleted file mode 100644
index 0fef213b37..0000000000
Binary files a/devices/surface-hub/images/four.png and /dev/null differ
diff --git a/devices/surface-hub/images/getstarted.png b/devices/surface-hub/images/getstarted.png
deleted file mode 100644
index e5b85dd8ae..0000000000
Binary files a/devices/surface-hub/images/getstarted.png and /dev/null differ
diff --git a/devices/surface-hub/images/h2gen-platemount.png b/devices/surface-hub/images/h2gen-platemount.png
deleted file mode 100644
index 4a8ca76fd4..0000000000
Binary files a/devices/surface-hub/images/h2gen-platemount.png and /dev/null differ
diff --git a/devices/surface-hub/images/h2gen-railmount.png b/devices/surface-hub/images/h2gen-railmount.png
deleted file mode 100644
index 0c8bf8ffb6..0000000000
Binary files a/devices/surface-hub/images/h2gen-railmount.png and /dev/null differ
diff --git a/devices/surface-hub/images/hdmi.png b/devices/surface-hub/images/hdmi.png
deleted file mode 100644
index a2c69ace45..0000000000
Binary files a/devices/surface-hub/images/hdmi.png and /dev/null differ
diff --git a/devices/surface-hub/images/hub-sec-1.png b/devices/surface-hub/images/hub-sec-1.png
deleted file mode 100644
index fe4e25d084..0000000000
Binary files a/devices/surface-hub/images/hub-sec-1.png and /dev/null differ
diff --git a/devices/surface-hub/images/hub-sec-2.png b/devices/surface-hub/images/hub-sec-2.png
deleted file mode 100644
index fdf7af7ca6..0000000000
Binary files a/devices/surface-hub/images/hub-sec-2.png and /dev/null differ
diff --git a/devices/surface-hub/images/hub2s-rear.png b/devices/surface-hub/images/hub2s-rear.png
deleted file mode 100644
index f30a81159c..0000000000
Binary files a/devices/surface-hub/images/hub2s-rear.png and /dev/null differ
diff --git a/devices/surface-hub/images/hub2s-schematic.png b/devices/surface-hub/images/hub2s-schematic.png
deleted file mode 100644
index 28c328a005..0000000000
Binary files a/devices/surface-hub/images/hub2s-schematic.png and /dev/null differ
diff --git a/devices/surface-hub/images/hybriddeployment-01a.png b/devices/surface-hub/images/hybriddeployment-01a.png
deleted file mode 100644
index 9eb84f777f..0000000000
Binary files a/devices/surface-hub/images/hybriddeployment-01a.png and /dev/null differ
diff --git a/devices/surface-hub/images/hybriddeployment-02a.png b/devices/surface-hub/images/hybriddeployment-02a.png
deleted file mode 100644
index 85229d2d0d..0000000000
Binary files a/devices/surface-hub/images/hybriddeployment-02a.png and /dev/null differ
diff --git a/devices/surface-hub/images/hybriddeployment-03a.png b/devices/surface-hub/images/hybriddeployment-03a.png
deleted file mode 100644
index 42cd08d900..0000000000
Binary files a/devices/surface-hub/images/hybriddeployment-03a.png and /dev/null differ
diff --git a/devices/surface-hub/images/icd-common-settings.png b/devices/surface-hub/images/icd-common-settings.png
deleted file mode 100644
index c2a8eb807f..0000000000
Binary files a/devices/surface-hub/images/icd-common-settings.png and /dev/null differ
diff --git a/devices/surface-hub/images/icd-new-project.png b/devices/surface-hub/images/icd-new-project.png
deleted file mode 100644
index 8a5c64fa4e..0000000000
Binary files a/devices/surface-hub/images/icd-new-project.png and /dev/null differ
diff --git a/devices/surface-hub/images/icd-simple-edit.png b/devices/surface-hub/images/icd-simple-edit.png
deleted file mode 100644
index aea2e24c8a..0000000000
Binary files a/devices/surface-hub/images/icd-simple-edit.png and /dev/null differ
diff --git a/devices/surface-hub/images/idcfeatureschecklist.png b/devices/surface-hub/images/idcfeatureschecklist.png
deleted file mode 100644
index a58d20fcb2..0000000000
Binary files a/devices/surface-hub/images/idcfeatureschecklist.png and /dev/null differ
diff --git a/devices/surface-hub/images/iec.png b/devices/surface-hub/images/iec.png
deleted file mode 100644
index 7ca6e9237b..0000000000
Binary files a/devices/surface-hub/images/iec.png and /dev/null differ
diff --git a/devices/surface-hub/images/intune-save-policy.png b/devices/surface-hub/images/intune-save-policy.png
deleted file mode 100644
index f53cc85602..0000000000
Binary files a/devices/surface-hub/images/intune-save-policy.png and /dev/null differ
diff --git a/devices/surface-hub/images/intune-template.png b/devices/surface-hub/images/intune-template.png
deleted file mode 100644
index 047aed6502..0000000000
Binary files a/devices/surface-hub/images/intune-template.png and /dev/null differ
diff --git a/devices/surface-hub/images/key-55.png b/devices/surface-hub/images/key-55.png
deleted file mode 100644
index d0ee9a5d13..0000000000
Binary files a/devices/surface-hub/images/key-55.png and /dev/null differ
diff --git a/devices/surface-hub/images/license-terms.png b/devices/surface-hub/images/license-terms.png
deleted file mode 100644
index 8dd34b0a18..0000000000
Binary files a/devices/surface-hub/images/license-terms.png and /dev/null differ
diff --git a/devices/surface-hub/images/manage1.png b/devices/surface-hub/images/manage1.png
deleted file mode 100644
index 4caf53b809..0000000000
Binary files a/devices/surface-hub/images/manage1.png and /dev/null differ
diff --git a/devices/surface-hub/images/manage2.png b/devices/surface-hub/images/manage2.png
deleted file mode 100644
index cb232cffa6..0000000000
Binary files a/devices/surface-hub/images/manage2.png and /dev/null differ
diff --git a/devices/surface-hub/images/manage3.png b/devices/surface-hub/images/manage3.png
deleted file mode 100644
index 9da88b808e..0000000000
Binary files a/devices/surface-hub/images/manage3.png and /dev/null differ
diff --git a/devices/surface-hub/images/manage4.png b/devices/surface-hub/images/manage4.png
deleted file mode 100644
index 5c9553718e..0000000000
Binary files a/devices/surface-hub/images/manage4.png and /dev/null differ
diff --git a/devices/surface-hub/images/managesettingsmdm-enroll.png b/devices/surface-hub/images/managesettingsmdm-enroll.png
deleted file mode 100644
index fe33277b4e..0000000000
Binary files a/devices/surface-hub/images/managesettingsmdm-enroll.png and /dev/null differ
diff --git a/devices/surface-hub/images/mfa-options.png b/devices/surface-hub/images/mfa-options.png
deleted file mode 100644
index 5bd3defd01..0000000000
Binary files a/devices/surface-hub/images/mfa-options.png and /dev/null differ
diff --git a/devices/surface-hub/images/networkmgtwired-01.png b/devices/surface-hub/images/networkmgtwired-01.png
deleted file mode 100644
index d2c1748b0b..0000000000
Binary files a/devices/surface-hub/images/networkmgtwired-01.png and /dev/null differ
diff --git a/devices/surface-hub/images/networkmgtwired-02.png b/devices/surface-hub/images/networkmgtwired-02.png
deleted file mode 100644
index 7312b644d0..0000000000
Binary files a/devices/surface-hub/images/networkmgtwired-02.png and /dev/null differ
diff --git a/devices/surface-hub/images/networkmgtwireless-01.png b/devices/surface-hub/images/networkmgtwireless-01.png
deleted file mode 100644
index 0ccdc9f5c7..0000000000
Binary files a/devices/surface-hub/images/networkmgtwireless-01.png and /dev/null differ
diff --git a/devices/surface-hub/images/networkmgtwireless-02.png b/devices/surface-hub/images/networkmgtwireless-02.png
deleted file mode 100644
index 5e9ccb9d99..0000000000
Binary files a/devices/surface-hub/images/networkmgtwireless-02.png and /dev/null differ
diff --git a/devices/surface-hub/images/networkmgtwireless-03.png b/devices/surface-hub/images/networkmgtwireless-03.png
deleted file mode 100644
index 33954daf1a..0000000000
Binary files a/devices/surface-hub/images/networkmgtwireless-03.png and /dev/null differ
diff --git a/devices/surface-hub/images/networkmgtwireless-04.png b/devices/surface-hub/images/networkmgtwireless-04.png
deleted file mode 100644
index c1d0e6ec6d..0000000000
Binary files a/devices/surface-hub/images/networkmgtwireless-04.png and /dev/null differ
diff --git a/devices/surface-hub/images/new-user-hybrid-voice.png b/devices/surface-hub/images/new-user-hybrid-voice.png
deleted file mode 100644
index e291f9ebca..0000000000
Binary files a/devices/surface-hub/images/new-user-hybrid-voice.png and /dev/null differ
diff --git a/devices/surface-hub/images/new-user-password-hybrid-voice.png b/devices/surface-hub/images/new-user-password-hybrid-voice.png
deleted file mode 100644
index 1ae4d5560b..0000000000
Binary files a/devices/surface-hub/images/new-user-password-hybrid-voice.png and /dev/null differ
diff --git a/devices/surface-hub/images/oma-uri.png b/devices/surface-hub/images/oma-uri.png
deleted file mode 100644
index b6d4a325d0..0000000000
Binary files a/devices/surface-hub/images/oma-uri.png and /dev/null differ
diff --git a/devices/surface-hub/images/one.png b/devices/surface-hub/images/one.png
deleted file mode 100644
index 42b4742c49..0000000000
Binary files a/devices/surface-hub/images/one.png and /dev/null differ
diff --git a/devices/surface-hub/images/oobe.jpg b/devices/surface-hub/images/oobe.jpg
deleted file mode 100644
index 53a5dab6bf..0000000000
Binary files a/devices/surface-hub/images/oobe.jpg and /dev/null differ
diff --git a/devices/surface-hub/images/plan1.png b/devices/surface-hub/images/plan1.png
deleted file mode 100644
index 891e1e43a6..0000000000
Binary files a/devices/surface-hub/images/plan1.png and /dev/null differ
diff --git a/devices/surface-hub/images/plan2.png b/devices/surface-hub/images/plan2.png
deleted file mode 100644
index 3ad1f2b9fc..0000000000
Binary files a/devices/surface-hub/images/plan2.png and /dev/null differ
diff --git a/devices/surface-hub/images/plan3.png b/devices/surface-hub/images/plan3.png
deleted file mode 100644
index 1891d1d2b5..0000000000
Binary files a/devices/surface-hub/images/plan3.png and /dev/null differ
diff --git a/devices/surface-hub/images/ppkg-config.png b/devices/surface-hub/images/ppkg-config.png
deleted file mode 100644
index 10a2b7de58..0000000000
Binary files a/devices/surface-hub/images/ppkg-config.png and /dev/null differ
diff --git a/devices/surface-hub/images/ppkg-csv.png b/devices/surface-hub/images/ppkg-csv.png
deleted file mode 100644
index 0648f555e1..0000000000
Binary files a/devices/surface-hub/images/ppkg-csv.png and /dev/null differ
diff --git a/devices/surface-hub/images/product-license-hybrid-voice.png b/devices/surface-hub/images/product-license-hybrid-voice.png
deleted file mode 100644
index 3d16aeb467..0000000000
Binary files a/devices/surface-hub/images/product-license-hybrid-voice.png and /dev/null differ
diff --git a/devices/surface-hub/images/prov.jpg b/devices/surface-hub/images/prov.jpg
deleted file mode 100644
index 1593ccb36b..0000000000
Binary files a/devices/surface-hub/images/prov.jpg and /dev/null differ
diff --git a/devices/surface-hub/images/provisioningpackageoobe-01.png b/devices/surface-hub/images/provisioningpackageoobe-01.png
deleted file mode 100644
index 72774987c7..0000000000
Binary files a/devices/surface-hub/images/provisioningpackageoobe-01.png and /dev/null differ
diff --git a/devices/surface-hub/images/provisioningpackageoobe-02.png b/devices/surface-hub/images/provisioningpackageoobe-02.png
deleted file mode 100644
index 43d283a316..0000000000
Binary files a/devices/surface-hub/images/provisioningpackageoobe-02.png and /dev/null differ
diff --git a/devices/surface-hub/images/provisioningpackageoobe-03.png b/devices/surface-hub/images/provisioningpackageoobe-03.png
deleted file mode 100644
index 84b037292f..0000000000
Binary files a/devices/surface-hub/images/provisioningpackageoobe-03.png and /dev/null differ
diff --git a/devices/surface-hub/images/provisioningpackageoobe-04.png b/devices/surface-hub/images/provisioningpackageoobe-04.png
deleted file mode 100644
index 9c854e8084..0000000000
Binary files a/devices/surface-hub/images/provisioningpackageoobe-04.png and /dev/null differ
diff --git a/devices/surface-hub/images/provisioningpackagesettings-01.png b/devices/surface-hub/images/provisioningpackagesettings-01.png
deleted file mode 100644
index b42614c566..0000000000
Binary files a/devices/surface-hub/images/provisioningpackagesettings-01.png and /dev/null differ
diff --git a/devices/surface-hub/images/provisioningpackagesettings-02.png b/devices/surface-hub/images/provisioningpackagesettings-02.png
deleted file mode 100644
index f6cae68e8b..0000000000
Binary files a/devices/surface-hub/images/provisioningpackagesettings-02.png and /dev/null differ
diff --git a/devices/surface-hub/images/provisioningpackagesettings-03.png b/devices/surface-hub/images/provisioningpackagesettings-03.png
deleted file mode 100644
index e4538d7368..0000000000
Binary files a/devices/surface-hub/images/provisioningpackagesettings-03.png and /dev/null differ
diff --git a/devices/surface-hub/images/proxy-details.PNG b/devices/surface-hub/images/proxy-details.PNG
deleted file mode 100644
index fcc7b06a41..0000000000
Binary files a/devices/surface-hub/images/proxy-details.PNG and /dev/null differ
diff --git a/devices/surface-hub/images/proxy.PNG b/devices/surface-hub/images/proxy.PNG
deleted file mode 100644
index cdfc02c454..0000000000
Binary files a/devices/surface-hub/images/proxy.PNG and /dev/null differ
diff --git a/devices/surface-hub/images/qos-create.png b/devices/surface-hub/images/qos-create.png
deleted file mode 100644
index 7cd4726ddb..0000000000
Binary files a/devices/surface-hub/images/qos-create.png and /dev/null differ
diff --git a/devices/surface-hub/images/qos-setting.png b/devices/surface-hub/images/qos-setting.png
deleted file mode 100644
index d775d9a46f..0000000000
Binary files a/devices/surface-hub/images/qos-setting.png and /dev/null differ
diff --git a/devices/surface-hub/images/recover-from-cloud.png b/devices/surface-hub/images/recover-from-cloud.png
deleted file mode 100644
index 7d409edc5f..0000000000
Binary files a/devices/surface-hub/images/recover-from-cloud.png and /dev/null differ
diff --git a/devices/surface-hub/images/recover-from-the-cloud.png b/devices/surface-hub/images/recover-from-the-cloud.png
deleted file mode 100644
index 07c1e22851..0000000000
Binary files a/devices/surface-hub/images/recover-from-the-cloud.png and /dev/null differ
diff --git a/devices/surface-hub/images/recover-progress.png b/devices/surface-hub/images/recover-progress.png
deleted file mode 100644
index 316d830a57..0000000000
Binary files a/devices/surface-hub/images/recover-progress.png and /dev/null differ
diff --git a/devices/surface-hub/images/reinstall.png b/devices/surface-hub/images/reinstall.png
deleted file mode 100644
index 2f307841aa..0000000000
Binary files a/devices/surface-hub/images/reinstall.png and /dev/null differ
diff --git a/devices/surface-hub/images/repartition.png b/devices/surface-hub/images/repartition.png
deleted file mode 100644
index 26725a8c54..0000000000
Binary files a/devices/surface-hub/images/repartition.png and /dev/null differ
diff --git a/devices/surface-hub/images/replacement-port-55.PNG b/devices/surface-hub/images/replacement-port-55.PNG
deleted file mode 100644
index 5bf0b51b02..0000000000
Binary files a/devices/surface-hub/images/replacement-port-55.PNG and /dev/null differ
diff --git a/devices/surface-hub/images/replacement-port-84.PNG b/devices/surface-hub/images/replacement-port-84.PNG
deleted file mode 100644
index 45284b4ab9..0000000000
Binary files a/devices/surface-hub/images/replacement-port-84.PNG and /dev/null differ
diff --git a/devices/surface-hub/images/rj11.png b/devices/surface-hub/images/rj11.png
deleted file mode 100644
index f044354caa..0000000000
Binary files a/devices/surface-hub/images/rj11.png and /dev/null differ
diff --git a/devices/surface-hub/images/rj45.png b/devices/surface-hub/images/rj45.png
deleted file mode 100644
index ca88423217..0000000000
Binary files a/devices/surface-hub/images/rj45.png and /dev/null differ
diff --git a/devices/surface-hub/images/room-add.png b/devices/surface-hub/images/room-add.png
deleted file mode 100644
index 6b0597c41a..0000000000
Binary files a/devices/surface-hub/images/room-add.png and /dev/null differ
diff --git a/devices/surface-hub/images/room-control-wiring-diagram.png b/devices/surface-hub/images/room-control-wiring-diagram.png
deleted file mode 100644
index 5a2ecf613e..0000000000
Binary files a/devices/surface-hub/images/room-control-wiring-diagram.png and /dev/null differ
diff --git a/devices/surface-hub/images/room-equipment.png b/devices/surface-hub/images/room-equipment.png
deleted file mode 100644
index 131f8b8c75..0000000000
Binary files a/devices/surface-hub/images/room-equipment.png and /dev/null differ
diff --git a/devices/surface-hub/images/roomcontrolwiring.png b/devices/surface-hub/images/roomcontrolwiring.png
deleted file mode 100644
index 78da10ce77..0000000000
Binary files a/devices/surface-hub/images/roomcontrolwiring.png and /dev/null differ
diff --git a/devices/surface-hub/images/select-room-hybrid-voice.png b/devices/surface-hub/images/select-room-hybrid-voice.png
deleted file mode 100644
index 961f8355e8..0000000000
Binary files a/devices/surface-hub/images/select-room-hybrid-voice.png and /dev/null differ
diff --git a/devices/surface-hub/images/set-up-device-admins-details.PNG b/devices/surface-hub/images/set-up-device-admins-details.PNG
deleted file mode 100644
index 42c04b4b3b..0000000000
Binary files a/devices/surface-hub/images/set-up-device-admins-details.PNG and /dev/null differ
diff --git a/devices/surface-hub/images/set-up-device-admins.PNG b/devices/surface-hub/images/set-up-device-admins.PNG
deleted file mode 100644
index e0e037903c..0000000000
Binary files a/devices/surface-hub/images/set-up-device-admins.PNG and /dev/null differ
diff --git a/devices/surface-hub/images/set-up-device-details.PNG b/devices/surface-hub/images/set-up-device-details.PNG
deleted file mode 100644
index be565ac8d9..0000000000
Binary files a/devices/surface-hub/images/set-up-device-details.PNG and /dev/null differ
diff --git a/devices/surface-hub/images/set-up-device.PNG b/devices/surface-hub/images/set-up-device.PNG
deleted file mode 100644
index 0c9eb0e3ff..0000000000
Binary files a/devices/surface-hub/images/set-up-device.PNG and /dev/null differ
diff --git a/devices/surface-hub/images/set-up-network-details.PNG b/devices/surface-hub/images/set-up-network-details.PNG
deleted file mode 100644
index 7e1391326c..0000000000
Binary files a/devices/surface-hub/images/set-up-network-details.PNG and /dev/null differ
diff --git a/devices/surface-hub/images/set-up-network.PNG b/devices/surface-hub/images/set-up-network.PNG
deleted file mode 100644
index a0e856c103..0000000000
Binary files a/devices/surface-hub/images/set-up-network.PNG and /dev/null differ
diff --git a/devices/surface-hub/images/setupdeviceacct.png b/devices/surface-hub/images/setupdeviceacct.png
deleted file mode 100644
index 23c2f22171..0000000000
Binary files a/devices/surface-hub/images/setupdeviceacct.png and /dev/null differ
diff --git a/devices/surface-hub/images/setupdeviceacctexch-01.png b/devices/surface-hub/images/setupdeviceacctexch-01.png
deleted file mode 100644
index 10710fa4ca..0000000000
Binary files a/devices/surface-hub/images/setupdeviceacctexch-01.png and /dev/null differ
diff --git a/devices/surface-hub/images/setupdeviceacctexch-02.png b/devices/surface-hub/images/setupdeviceacctexch-02.png
deleted file mode 100644
index b55cb6b87e..0000000000
Binary files a/devices/surface-hub/images/setupdeviceacctexch-02.png and /dev/null differ
diff --git a/devices/surface-hub/images/setupdeviceacctexch-03.png b/devices/surface-hub/images/setupdeviceacctexch-03.png
deleted file mode 100644
index 4f15b6e025..0000000000
Binary files a/devices/surface-hub/images/setupdeviceacctexch-03.png and /dev/null differ
diff --git a/devices/surface-hub/images/setupdeviceacctexch-05.png b/devices/surface-hub/images/setupdeviceacctexch-05.png
deleted file mode 100644
index 40dced3c01..0000000000
Binary files a/devices/surface-hub/images/setupdeviceacctexch-05.png and /dev/null differ
diff --git a/devices/surface-hub/images/setupdeviceacctexch-06.png b/devices/surface-hub/images/setupdeviceacctexch-06.png
deleted file mode 100644
index f4f1686037..0000000000
Binary files a/devices/surface-hub/images/setupdeviceacctexch-06.png and /dev/null differ
diff --git a/devices/surface-hub/images/setupdeviceacctexch-07.png b/devices/surface-hub/images/setupdeviceacctexch-07.png
deleted file mode 100644
index aebb0ae29e..0000000000
Binary files a/devices/surface-hub/images/setupdeviceacctexch-07.png and /dev/null differ
diff --git a/devices/surface-hub/images/setupdeviceacctexch-08.png b/devices/surface-hub/images/setupdeviceacctexch-08.png
deleted file mode 100644
index 85c013f98d..0000000000
Binary files a/devices/surface-hub/images/setupdeviceacctexch-08.png and /dev/null differ
diff --git a/devices/surface-hub/images/setupdeviceacctexch-09.png b/devices/surface-hub/images/setupdeviceacctexch-09.png
deleted file mode 100644
index f36fb9817c..0000000000
Binary files a/devices/surface-hub/images/setupdeviceacctexch-09.png and /dev/null differ
diff --git a/devices/surface-hub/images/setupdeviceacctexch-10.png b/devices/surface-hub/images/setupdeviceacctexch-10.png
deleted file mode 100644
index 4a5d1aaee4..0000000000
Binary files a/devices/surface-hub/images/setupdeviceacctexch-10.png and /dev/null differ
diff --git a/devices/surface-hub/images/setupdeviceacctexch-11.png b/devices/surface-hub/images/setupdeviceacctexch-11.png
deleted file mode 100644
index 03d320cd55..0000000000
Binary files a/devices/surface-hub/images/setupdeviceacctexch-11.png and /dev/null differ
diff --git a/devices/surface-hub/images/setupdeviceaccto365-02.png b/devices/surface-hub/images/setupdeviceaccto365-02.png
deleted file mode 100644
index e0694bac42..0000000000
Binary files a/devices/surface-hub/images/setupdeviceaccto365-02.png and /dev/null differ
diff --git a/devices/surface-hub/images/setupdeviceaccto365-03.png b/devices/surface-hub/images/setupdeviceaccto365-03.png
deleted file mode 100644
index f93f0f1594..0000000000
Binary files a/devices/surface-hub/images/setupdeviceaccto365-03.png and /dev/null differ
diff --git a/devices/surface-hub/images/setupdeviceaccto365-04.png b/devices/surface-hub/images/setupdeviceaccto365-04.png
deleted file mode 100644
index 8484394faa..0000000000
Binary files a/devices/surface-hub/images/setupdeviceaccto365-04.png and /dev/null differ
diff --git a/devices/surface-hub/images/setupdeviceaccto365-05.png b/devices/surface-hub/images/setupdeviceaccto365-05.png
deleted file mode 100644
index 51150e3bcb..0000000000
Binary files a/devices/surface-hub/images/setupdeviceaccto365-05.png and /dev/null differ
diff --git a/devices/surface-hub/images/setupdeviceaccto365-06.png b/devices/surface-hub/images/setupdeviceaccto365-06.png
deleted file mode 100644
index 3f6567feca..0000000000
Binary files a/devices/surface-hub/images/setupdeviceaccto365-06.png and /dev/null differ
diff --git a/devices/surface-hub/images/setupdeviceaccto365-07.png b/devices/surface-hub/images/setupdeviceaccto365-07.png
deleted file mode 100644
index ce0eb99af2..0000000000
Binary files a/devices/surface-hub/images/setupdeviceaccto365-07.png and /dev/null differ
diff --git a/devices/surface-hub/images/setupdeviceaccto365-08.png b/devices/surface-hub/images/setupdeviceaccto365-08.png
deleted file mode 100644
index e174c7d54c..0000000000
Binary files a/devices/surface-hub/images/setupdeviceaccto365-08.png and /dev/null differ
diff --git a/devices/surface-hub/images/setupdeviceaccto365-09.png b/devices/surface-hub/images/setupdeviceaccto365-09.png
deleted file mode 100644
index 4820c18f0f..0000000000
Binary files a/devices/surface-hub/images/setupdeviceaccto365-09.png and /dev/null differ
diff --git a/devices/surface-hub/images/setupdeviceaccto365-10.png b/devices/surface-hub/images/setupdeviceaccto365-10.png
deleted file mode 100644
index bb461ddf8d..0000000000
Binary files a/devices/surface-hub/images/setupdeviceaccto365-10.png and /dev/null differ
diff --git a/devices/surface-hub/images/setupdeviceaccto365-11.png b/devices/surface-hub/images/setupdeviceaccto365-11.png
deleted file mode 100644
index f88d1246aa..0000000000
Binary files a/devices/surface-hub/images/setupdeviceaccto365-11.png and /dev/null differ
diff --git a/devices/surface-hub/images/setupdeviceaccto365-12.png b/devices/surface-hub/images/setupdeviceaccto365-12.png
deleted file mode 100644
index 29a2fa31d3..0000000000
Binary files a/devices/surface-hub/images/setupdeviceaccto365-12.png and /dev/null differ
diff --git a/devices/surface-hub/images/setupdeviceaccto365-13.png b/devices/surface-hub/images/setupdeviceaccto365-13.png
deleted file mode 100644
index 3e079c3092..0000000000
Binary files a/devices/surface-hub/images/setupdeviceaccto365-13.png and /dev/null differ
diff --git a/devices/surface-hub/images/setupdeviceaccto365-14.png b/devices/surface-hub/images/setupdeviceaccto365-14.png
deleted file mode 100644
index da2175f3d1..0000000000
Binary files a/devices/surface-hub/images/setupdeviceaccto365-14.png and /dev/null differ
diff --git a/devices/surface-hub/images/setupdeviceaccto365-15.png b/devices/surface-hub/images/setupdeviceaccto365-15.png
deleted file mode 100644
index 00e066f97e..0000000000
Binary files a/devices/surface-hub/images/setupdeviceaccto365-15.png and /dev/null differ
diff --git a/devices/surface-hub/images/setupdeviceaccto365-16.png b/devices/surface-hub/images/setupdeviceaccto365-16.png
deleted file mode 100644
index b6e467c72f..0000000000
Binary files a/devices/surface-hub/images/setupdeviceaccto365-16.png and /dev/null differ
diff --git a/devices/surface-hub/images/setupdeviceaccto365-17.png b/devices/surface-hub/images/setupdeviceaccto365-17.png
deleted file mode 100644
index e1501c92a1..0000000000
Binary files a/devices/surface-hub/images/setupdeviceaccto365-17.png and /dev/null differ
diff --git a/devices/surface-hub/images/setupdeviceaccto365-18.png b/devices/surface-hub/images/setupdeviceaccto365-18.png
deleted file mode 100644
index 8f1f3aba04..0000000000
Binary files a/devices/surface-hub/images/setupdeviceaccto365-18.png and /dev/null differ
diff --git a/devices/surface-hub/images/setupdeviceaccto365-19.png b/devices/surface-hub/images/setupdeviceaccto365-19.png
deleted file mode 100644
index 3e9b2a86fc..0000000000
Binary files a/devices/surface-hub/images/setupdeviceaccto365-19.png and /dev/null differ
diff --git a/devices/surface-hub/images/setupdeviceaccto365-20.png b/devices/surface-hub/images/setupdeviceaccto365-20.png
deleted file mode 100644
index 210cfb54c8..0000000000
Binary files a/devices/surface-hub/images/setupdeviceaccto365-20.png and /dev/null differ
diff --git a/devices/surface-hub/images/setupdeviceaccto365-21.png b/devices/surface-hub/images/setupdeviceaccto365-21.png
deleted file mode 100644
index 6ea80e548d..0000000000
Binary files a/devices/surface-hub/images/setupdeviceaccto365-21.png and /dev/null differ
diff --git a/devices/surface-hub/images/setupdeviceaccto365-22.png b/devices/surface-hub/images/setupdeviceaccto365-22.png
deleted file mode 100644
index cacd3294ad..0000000000
Binary files a/devices/surface-hub/images/setupdeviceaccto365-22.png and /dev/null differ
diff --git a/devices/surface-hub/images/setupdeviceaccto365-23.png b/devices/surface-hub/images/setupdeviceaccto365-23.png
deleted file mode 100644
index f15727c542..0000000000
Binary files a/devices/surface-hub/images/setupdeviceaccto365-23.png and /dev/null differ
diff --git a/devices/surface-hub/images/setupdeviceaccto365-24.png b/devices/surface-hub/images/setupdeviceaccto365-24.png
deleted file mode 100644
index a335591f17..0000000000
Binary files a/devices/surface-hub/images/setupdeviceaccto365-24.png and /dev/null differ
diff --git a/devices/surface-hub/images/setupdeviceaccto365-25.png b/devices/surface-hub/images/setupdeviceaccto365-25.png
deleted file mode 100644
index b49e3e9066..0000000000
Binary files a/devices/surface-hub/images/setupdeviceaccto365-25.png and /dev/null differ
diff --git a/devices/surface-hub/images/setupdeviceaccto365-26.png b/devices/surface-hub/images/setupdeviceaccto365-26.png
deleted file mode 100644
index 5a2841ec32..0000000000
Binary files a/devices/surface-hub/images/setupdeviceaccto365-26.png and /dev/null differ
diff --git a/devices/surface-hub/images/setupdomainjoin.png b/devices/surface-hub/images/setupdomainjoin.png
deleted file mode 100644
index c42a637981..0000000000
Binary files a/devices/surface-hub/images/setupdomainjoin.png and /dev/null differ
diff --git a/devices/surface-hub/images/setupexchangepolicies.png b/devices/surface-hub/images/setupexchangepolicies.png
deleted file mode 100644
index 63a4396364..0000000000
Binary files a/devices/surface-hub/images/setupexchangepolicies.png and /dev/null differ
diff --git a/devices/surface-hub/images/setupexchangeserver-01.png b/devices/surface-hub/images/setupexchangeserver-01.png
deleted file mode 100644
index f3b9dc9e18..0000000000
Binary files a/devices/surface-hub/images/setupexchangeserver-01.png and /dev/null differ
diff --git a/devices/surface-hub/images/setupexchangeserver-02.png b/devices/surface-hub/images/setupexchangeserver-02.png
deleted file mode 100644
index 58462ec244..0000000000
Binary files a/devices/surface-hub/images/setupexchangeserver-02.png and /dev/null differ
diff --git a/devices/surface-hub/images/setupjoiningazuread-1.png b/devices/surface-hub/images/setupjoiningazuread-1.png
deleted file mode 100644
index cd24be2c90..0000000000
Binary files a/devices/surface-hub/images/setupjoiningazuread-1.png and /dev/null differ
diff --git a/devices/surface-hub/images/setupjoiningazuread-2.png b/devices/surface-hub/images/setupjoiningazuread-2.png
deleted file mode 100644
index 9ec163f679..0000000000
Binary files a/devices/surface-hub/images/setupjoiningazuread-2.png and /dev/null differ
diff --git a/devices/surface-hub/images/setupjoiningazuread-3.png b/devices/surface-hub/images/setupjoiningazuread-3.png
deleted file mode 100644
index abe6691d92..0000000000
Binary files a/devices/surface-hub/images/setupjoiningazuread-3.png and /dev/null differ
diff --git a/devices/surface-hub/images/setuplocaladmin.png b/devices/surface-hub/images/setuplocaladmin.png
deleted file mode 100644
index 30ac056c5a..0000000000
Binary files a/devices/surface-hub/images/setuplocaladmin.png and /dev/null differ
diff --git a/devices/surface-hub/images/setuplocale.png b/devices/surface-hub/images/setuplocale.png
deleted file mode 100644
index e9aa468697..0000000000
Binary files a/devices/surface-hub/images/setuplocale.png and /dev/null differ
diff --git a/devices/surface-hub/images/setupmsg.jpg b/devices/surface-hub/images/setupmsg.jpg
deleted file mode 100644
index 12935483c5..0000000000
Binary files a/devices/surface-hub/images/setupmsg.jpg and /dev/null differ
diff --git a/devices/surface-hub/images/setupnamedevice.png b/devices/surface-hub/images/setupnamedevice.png
deleted file mode 100644
index 5baa35c487..0000000000
Binary files a/devices/surface-hub/images/setupnamedevice.png and /dev/null differ
diff --git a/devices/surface-hub/images/setupnetworksetup-1.png b/devices/surface-hub/images/setupnetworksetup-1.png
deleted file mode 100644
index 49dfbde566..0000000000
Binary files a/devices/surface-hub/images/setupnetworksetup-1.png and /dev/null differ
diff --git a/devices/surface-hub/images/setupnetworksetup-2.png b/devices/surface-hub/images/setupnetworksetup-2.png
deleted file mode 100644
index 4d96e95782..0000000000
Binary files a/devices/surface-hub/images/setupnetworksetup-2.png and /dev/null differ
diff --git a/devices/surface-hub/images/setupnetworksetup-3.png b/devices/surface-hub/images/setupnetworksetup-3.png
deleted file mode 100644
index 62d6e0a772..0000000000
Binary files a/devices/surface-hub/images/setupnetworksetup-3.png and /dev/null differ
diff --git a/devices/surface-hub/images/setupnetworksetup-4.png b/devices/surface-hub/images/setupnetworksetup-4.png
deleted file mode 100644
index 836bb208fb..0000000000
Binary files a/devices/surface-hub/images/setupnetworksetup-4.png and /dev/null differ
diff --git a/devices/surface-hub/images/setupsecuritygroup-1.png b/devices/surface-hub/images/setupsecuritygroup-1.png
deleted file mode 100644
index bab6e2f197..0000000000
Binary files a/devices/surface-hub/images/setupsecuritygroup-1.png and /dev/null differ
diff --git a/devices/surface-hub/images/setupsetupadmins.png b/devices/surface-hub/images/setupsetupadmins.png
deleted file mode 100644
index 109cb1ea92..0000000000
Binary files a/devices/surface-hub/images/setupsetupadmins.png and /dev/null differ
diff --git a/devices/surface-hub/images/setupsetupforyou.png b/devices/surface-hub/images/setupsetupforyou.png
deleted file mode 100644
index c0ea230caf..0000000000
Binary files a/devices/surface-hub/images/setupsetupforyou.png and /dev/null differ
diff --git a/devices/surface-hub/images/setupskipdeviceacct.png b/devices/surface-hub/images/setupskipdeviceacct.png
deleted file mode 100644
index 7a71c7f982..0000000000
Binary files a/devices/surface-hub/images/setupskipdeviceacct.png and /dev/null differ
diff --git a/devices/surface-hub/images/sh-55-bottom.png b/devices/surface-hub/images/sh-55-bottom.png
deleted file mode 100644
index 3d718d1226..0000000000
Binary files a/devices/surface-hub/images/sh-55-bottom.png and /dev/null differ
diff --git a/devices/surface-hub/images/sh-55-clearance.png b/devices/surface-hub/images/sh-55-clearance.png
deleted file mode 100644
index 12fc35ec49..0000000000
Binary files a/devices/surface-hub/images/sh-55-clearance.png and /dev/null differ
diff --git a/devices/surface-hub/images/sh-55-front.png b/devices/surface-hub/images/sh-55-front.png
deleted file mode 100644
index e1268ee328..0000000000
Binary files a/devices/surface-hub/images/sh-55-front.png and /dev/null differ
diff --git a/devices/surface-hub/images/sh-55-guest-ports.png b/devices/surface-hub/images/sh-55-guest-ports.png
deleted file mode 100644
index af42c738f8..0000000000
Binary files a/devices/surface-hub/images/sh-55-guest-ports.png and /dev/null differ
diff --git a/devices/surface-hub/images/sh-55-hand-rear.png b/devices/surface-hub/images/sh-55-hand-rear.png
deleted file mode 100644
index b1ff007ec2..0000000000
Binary files a/devices/surface-hub/images/sh-55-hand-rear.png and /dev/null differ
diff --git a/devices/surface-hub/images/sh-55-hand.png b/devices/surface-hub/images/sh-55-hand.png
deleted file mode 100644
index 6f8d96ba8e..0000000000
Binary files a/devices/surface-hub/images/sh-55-hand.png and /dev/null differ
diff --git a/devices/surface-hub/images/sh-55-rear.png b/devices/surface-hub/images/sh-55-rear.png
deleted file mode 100644
index 840b941e03..0000000000
Binary files a/devices/surface-hub/images/sh-55-rear.png and /dev/null differ
diff --git a/devices/surface-hub/images/sh-55-rpc-ports.png b/devices/surface-hub/images/sh-55-rpc-ports.png
deleted file mode 100644
index 7df98f2277..0000000000
Binary files a/devices/surface-hub/images/sh-55-rpc-ports.png and /dev/null differ
diff --git a/devices/surface-hub/images/sh-55-top.png b/devices/surface-hub/images/sh-55-top.png
deleted file mode 100644
index f8c93f5d1b..0000000000
Binary files a/devices/surface-hub/images/sh-55-top.png and /dev/null differ
diff --git a/devices/surface-hub/images/sh-84-bottom.png b/devices/surface-hub/images/sh-84-bottom.png
deleted file mode 100644
index d7252537e4..0000000000
Binary files a/devices/surface-hub/images/sh-84-bottom.png and /dev/null differ
diff --git a/devices/surface-hub/images/sh-84-clearance.png b/devices/surface-hub/images/sh-84-clearance.png
deleted file mode 100644
index 8fd0cd2c32..0000000000
Binary files a/devices/surface-hub/images/sh-84-clearance.png and /dev/null differ
diff --git a/devices/surface-hub/images/sh-84-front.png b/devices/surface-hub/images/sh-84-front.png
deleted file mode 100644
index 8afa0de18b..0000000000
Binary files a/devices/surface-hub/images/sh-84-front.png and /dev/null differ
diff --git a/devices/surface-hub/images/sh-84-guest-ports.png b/devices/surface-hub/images/sh-84-guest-ports.png
deleted file mode 100644
index 6c7060154b..0000000000
Binary files a/devices/surface-hub/images/sh-84-guest-ports.png and /dev/null differ
diff --git a/devices/surface-hub/images/sh-84-hand-top.png b/devices/surface-hub/images/sh-84-hand-top.png
deleted file mode 100644
index 1e52446eb0..0000000000
Binary files a/devices/surface-hub/images/sh-84-hand-top.png and /dev/null differ
diff --git a/devices/surface-hub/images/sh-84-hand.png b/devices/surface-hub/images/sh-84-hand.png
deleted file mode 100644
index 3e84a8a434..0000000000
Binary files a/devices/surface-hub/images/sh-84-hand.png and /dev/null differ
diff --git a/devices/surface-hub/images/sh-84-rear.png b/devices/surface-hub/images/sh-84-rear.png
deleted file mode 100644
index 5837d4e185..0000000000
Binary files a/devices/surface-hub/images/sh-84-rear.png and /dev/null differ
diff --git a/devices/surface-hub/images/sh-84-rpc-ports.png b/devices/surface-hub/images/sh-84-rpc-ports.png
deleted file mode 100644
index f3a0a52327..0000000000
Binary files a/devices/surface-hub/images/sh-84-rpc-ports.png and /dev/null differ
diff --git a/devices/surface-hub/images/sh-84-side.png b/devices/surface-hub/images/sh-84-side.png
deleted file mode 100644
index 6b1ad8385b..0000000000
Binary files a/devices/surface-hub/images/sh-84-side.png and /dev/null differ
diff --git a/devices/surface-hub/images/sh-84-top.png b/devices/surface-hub/images/sh-84-top.png
deleted file mode 100644
index badc94af0b..0000000000
Binary files a/devices/surface-hub/images/sh-84-top.png and /dev/null differ
diff --git a/devices/surface-hub/images/sh-84-wall.png b/devices/surface-hub/images/sh-84-wall.png
deleted file mode 100644
index 15d2e5a848..0000000000
Binary files a/devices/surface-hub/images/sh-84-wall.png and /dev/null differ
diff --git a/devices/surface-hub/images/sh-device-family-availability.png b/devices/surface-hub/images/sh-device-family-availability.png
deleted file mode 100644
index 30b8a954af..0000000000
Binary files a/devices/surface-hub/images/sh-device-family-availability.png and /dev/null differ
diff --git a/devices/surface-hub/images/sh-org-licensing.png b/devices/surface-hub/images/sh-org-licensing.png
deleted file mode 100644
index 48c7033715..0000000000
Binary files a/devices/surface-hub/images/sh-org-licensing.png and /dev/null differ
diff --git a/devices/surface-hub/images/sh-quick-action.png b/devices/surface-hub/images/sh-quick-action.png
deleted file mode 100644
index 3003e464b3..0000000000
Binary files a/devices/surface-hub/images/sh-quick-action.png and /dev/null differ
diff --git a/devices/surface-hub/images/sh-select-template.png b/devices/surface-hub/images/sh-select-template.png
deleted file mode 100644
index 58ab21481e..0000000000
Binary files a/devices/surface-hub/images/sh-select-template.png and /dev/null differ
diff --git a/devices/surface-hub/images/sh-settings-reset-device.png b/devices/surface-hub/images/sh-settings-reset-device.png
deleted file mode 100644
index f3a9a6dc5c..0000000000
Binary files a/devices/surface-hub/images/sh-settings-reset-device.png and /dev/null differ
diff --git a/devices/surface-hub/images/sh-settings-update-security.png b/devices/surface-hub/images/sh-settings-update-security.png
deleted file mode 100644
index 59212d1805..0000000000
Binary files a/devices/surface-hub/images/sh-settings-update-security.png and /dev/null differ
diff --git a/devices/surface-hub/images/sh-settings.png b/devices/surface-hub/images/sh-settings.png
deleted file mode 100644
index 0134fda740..0000000000
Binary files a/devices/surface-hub/images/sh-settings.png and /dev/null differ
diff --git a/devices/surface-hub/images/sh2-account2.png b/devices/surface-hub/images/sh2-account2.png
deleted file mode 100644
index 2a2267ab7c..0000000000
Binary files a/devices/surface-hub/images/sh2-account2.png and /dev/null differ
diff --git a/devices/surface-hub/images/sh2-account3.png b/devices/surface-hub/images/sh2-account3.png
deleted file mode 100644
index b67ff0da37..0000000000
Binary files a/devices/surface-hub/images/sh2-account3.png and /dev/null differ
diff --git a/devices/surface-hub/images/sh2-account4.png b/devices/surface-hub/images/sh2-account4.png
deleted file mode 100644
index 7495f28607..0000000000
Binary files a/devices/surface-hub/images/sh2-account4.png and /dev/null differ
diff --git a/devices/surface-hub/images/sh2-account5.png b/devices/surface-hub/images/sh2-account5.png
deleted file mode 100644
index 3dc9061733..0000000000
Binary files a/devices/surface-hub/images/sh2-account5.png and /dev/null differ
diff --git a/devices/surface-hub/images/sh2-add-group.png b/devices/surface-hub/images/sh2-add-group.png
deleted file mode 100644
index eb44ad8cf9..0000000000
Binary files a/devices/surface-hub/images/sh2-add-group.png and /dev/null differ
diff --git a/devices/surface-hub/images/sh2-add-room.png b/devices/surface-hub/images/sh2-add-room.png
deleted file mode 100644
index c53ee340bc..0000000000
Binary files a/devices/surface-hub/images/sh2-add-room.png and /dev/null differ
diff --git a/devices/surface-hub/images/sh2-apps-assign.png b/devices/surface-hub/images/sh2-apps-assign.png
deleted file mode 100644
index f6a91864c8..0000000000
Binary files a/devices/surface-hub/images/sh2-apps-assign.png and /dev/null differ
diff --git a/devices/surface-hub/images/sh2-assign-group.png b/devices/surface-hub/images/sh2-assign-group.png
deleted file mode 100644
index a2d79bcd34..0000000000
Binary files a/devices/surface-hub/images/sh2-assign-group.png and /dev/null differ
diff --git a/devices/surface-hub/images/sh2-cartridge.png b/devices/surface-hub/images/sh2-cartridge.png
deleted file mode 100644
index 3c7a2e83be..0000000000
Binary files a/devices/surface-hub/images/sh2-cartridge.png and /dev/null differ
diff --git a/devices/surface-hub/images/sh2-config-file.png b/devices/surface-hub/images/sh2-config-file.png
deleted file mode 100644
index d8293c8ff6..0000000000
Binary files a/devices/surface-hub/images/sh2-config-file.png and /dev/null differ
diff --git a/devices/surface-hub/images/sh2-deploy-apps-sync.png b/devices/surface-hub/images/sh2-deploy-apps-sync.png
deleted file mode 100644
index 060c29c17f..0000000000
Binary files a/devices/surface-hub/images/sh2-deploy-apps-sync.png and /dev/null differ
diff --git a/devices/surface-hub/images/sh2-keepout-zones.png b/devices/surface-hub/images/sh2-keepout-zones.png
deleted file mode 100644
index bf318963df..0000000000
Binary files a/devices/surface-hub/images/sh2-keepout-zones.png and /dev/null differ
diff --git a/devices/surface-hub/images/sh2-keypad.png b/devices/surface-hub/images/sh2-keypad.png
deleted file mode 100644
index 595bb19341..0000000000
Binary files a/devices/surface-hub/images/sh2-keypad.png and /dev/null differ
diff --git a/devices/surface-hub/images/sh2-mobile-stand.png b/devices/surface-hub/images/sh2-mobile-stand.png
deleted file mode 100644
index 75c64f06f3..0000000000
Binary files a/devices/surface-hub/images/sh2-mobile-stand.png and /dev/null differ
diff --git a/devices/surface-hub/images/sh2-mount-config.png b/devices/surface-hub/images/sh2-mount-config.png
deleted file mode 100644
index 5cde6108a1..0000000000
Binary files a/devices/surface-hub/images/sh2-mount-config.png and /dev/null differ
diff --git a/devices/surface-hub/images/sh2-onscreen-display.png b/devices/surface-hub/images/sh2-onscreen-display.png
deleted file mode 100644
index 4605f50734..0000000000
Binary files a/devices/surface-hub/images/sh2-onscreen-display.png and /dev/null differ
diff --git a/devices/surface-hub/images/sh2-pen-1.png b/devices/surface-hub/images/sh2-pen-1.png
deleted file mode 100644
index 71693c021e..0000000000
Binary files a/devices/surface-hub/images/sh2-pen-1.png and /dev/null differ
diff --git a/devices/surface-hub/images/sh2-pen-pressure.png b/devices/surface-hub/images/sh2-pen-pressure.png
deleted file mode 100644
index 67054ca972..0000000000
Binary files a/devices/surface-hub/images/sh2-pen-pressure.png and /dev/null differ
diff --git a/devices/surface-hub/images/sh2-pen.png b/devices/surface-hub/images/sh2-pen.png
deleted file mode 100644
index 06b344d8c5..0000000000
Binary files a/devices/surface-hub/images/sh2-pen.png and /dev/null differ
diff --git a/devices/surface-hub/images/sh2-ports.png b/devices/surface-hub/images/sh2-ports.png
deleted file mode 100644
index 2d30422911..0000000000
Binary files a/devices/surface-hub/images/sh2-ports.png and /dev/null differ
diff --git a/devices/surface-hub/images/sh2-proxy.png b/devices/surface-hub/images/sh2-proxy.png
deleted file mode 100644
index 81946a9906..0000000000
Binary files a/devices/surface-hub/images/sh2-proxy.png and /dev/null differ
diff --git a/devices/surface-hub/images/sh2-reset.png b/devices/surface-hub/images/sh2-reset.png
deleted file mode 100644
index 06b306ec5d..0000000000
Binary files a/devices/surface-hub/images/sh2-reset.png and /dev/null differ
diff --git a/devices/surface-hub/images/sh2-run1.png b/devices/surface-hub/images/sh2-run1.png
deleted file mode 100644
index 15aa540166..0000000000
Binary files a/devices/surface-hub/images/sh2-run1.png and /dev/null differ
diff --git a/devices/surface-hub/images/sh2-run10.png b/devices/surface-hub/images/sh2-run10.png
deleted file mode 100644
index 5e980fa334..0000000000
Binary files a/devices/surface-hub/images/sh2-run10.png and /dev/null differ
diff --git a/devices/surface-hub/images/sh2-run11.png b/devices/surface-hub/images/sh2-run11.png
deleted file mode 100644
index 02362bc5da..0000000000
Binary files a/devices/surface-hub/images/sh2-run11.png and /dev/null differ
diff --git a/devices/surface-hub/images/sh2-run12.png b/devices/surface-hub/images/sh2-run12.png
deleted file mode 100644
index f619ac4c42..0000000000
Binary files a/devices/surface-hub/images/sh2-run12.png and /dev/null differ
diff --git a/devices/surface-hub/images/sh2-run13.png b/devices/surface-hub/images/sh2-run13.png
deleted file mode 100644
index 77b9e3e2a6..0000000000
Binary files a/devices/surface-hub/images/sh2-run13.png and /dev/null differ
diff --git a/devices/surface-hub/images/sh2-run14.png b/devices/surface-hub/images/sh2-run14.png
deleted file mode 100644
index d88ca872ca..0000000000
Binary files a/devices/surface-hub/images/sh2-run14.png and /dev/null differ
diff --git a/devices/surface-hub/images/sh2-run2.png b/devices/surface-hub/images/sh2-run2.png
deleted file mode 100644
index fd379b2b05..0000000000
Binary files a/devices/surface-hub/images/sh2-run2.png and /dev/null differ
diff --git a/devices/surface-hub/images/sh2-run3.png b/devices/surface-hub/images/sh2-run3.png
deleted file mode 100644
index 8171beecbf..0000000000
Binary files a/devices/surface-hub/images/sh2-run3.png and /dev/null differ
diff --git a/devices/surface-hub/images/sh2-run4.png b/devices/surface-hub/images/sh2-run4.png
deleted file mode 100644
index 1a132dfebb..0000000000
Binary files a/devices/surface-hub/images/sh2-run4.png and /dev/null differ
diff --git a/devices/surface-hub/images/sh2-run5.png b/devices/surface-hub/images/sh2-run5.png
deleted file mode 100644
index ebfe53f3cb..0000000000
Binary files a/devices/surface-hub/images/sh2-run5.png and /dev/null differ
diff --git a/devices/surface-hub/images/sh2-run6.png b/devices/surface-hub/images/sh2-run6.png
deleted file mode 100644
index 896531f4ec..0000000000
Binary files a/devices/surface-hub/images/sh2-run6.png and /dev/null differ
diff --git a/devices/surface-hub/images/sh2-run7.png b/devices/surface-hub/images/sh2-run7.png
deleted file mode 100644
index 59e60d84de..0000000000
Binary files a/devices/surface-hub/images/sh2-run7.png and /dev/null differ
diff --git a/devices/surface-hub/images/sh2-run8.png b/devices/surface-hub/images/sh2-run8.png
deleted file mode 100644
index ec2daf8e4f..0000000000
Binary files a/devices/surface-hub/images/sh2-run8.png and /dev/null differ
diff --git a/devices/surface-hub/images/sh2-run9.png b/devices/surface-hub/images/sh2-run9.png
deleted file mode 100644
index 5bd3abea88..0000000000
Binary files a/devices/surface-hub/images/sh2-run9.png and /dev/null differ
diff --git a/devices/surface-hub/images/sh2-set-intune1.png b/devices/surface-hub/images/sh2-set-intune1.png
deleted file mode 100644
index 9993225210..0000000000
Binary files a/devices/surface-hub/images/sh2-set-intune1.png and /dev/null differ
diff --git a/devices/surface-hub/images/sh2-set-intune3.png b/devices/surface-hub/images/sh2-set-intune3.png
deleted file mode 100644
index f931d828fc..0000000000
Binary files a/devices/surface-hub/images/sh2-set-intune3.png and /dev/null differ
diff --git a/devices/surface-hub/images/sh2-set-intune5.png b/devices/surface-hub/images/sh2-set-intune5.png
deleted file mode 100644
index 9afb1c1445..0000000000
Binary files a/devices/surface-hub/images/sh2-set-intune5.png and /dev/null differ
diff --git a/devices/surface-hub/images/sh2-set-intune6.png b/devices/surface-hub/images/sh2-set-intune6.png
deleted file mode 100644
index 155cbb9930..0000000000
Binary files a/devices/surface-hub/images/sh2-set-intune6.png and /dev/null differ
diff --git a/devices/surface-hub/images/sh2-set-intune8.png b/devices/surface-hub/images/sh2-set-intune8.png
deleted file mode 100644
index a8d9bfe874..0000000000
Binary files a/devices/surface-hub/images/sh2-set-intune8.png and /dev/null differ
diff --git a/devices/surface-hub/images/sh2-setup-1.png b/devices/surface-hub/images/sh2-setup-1.png
deleted file mode 100644
index 1204020f9f..0000000000
Binary files a/devices/surface-hub/images/sh2-setup-1.png and /dev/null differ
diff --git a/devices/surface-hub/images/sh2-setup-2.png b/devices/surface-hub/images/sh2-setup-2.png
deleted file mode 100644
index 0d6501782b..0000000000
Binary files a/devices/surface-hub/images/sh2-setup-2.png and /dev/null differ
diff --git a/devices/surface-hub/images/sh2-setup-3.png b/devices/surface-hub/images/sh2-setup-3.png
deleted file mode 100644
index 2b827f4405..0000000000
Binary files a/devices/surface-hub/images/sh2-setup-3.png and /dev/null differ
diff --git a/devices/surface-hub/images/sh2-setup-4.png b/devices/surface-hub/images/sh2-setup-4.png
deleted file mode 100644
index 0825dadce4..0000000000
Binary files a/devices/surface-hub/images/sh2-setup-4.png and /dev/null differ
diff --git a/devices/surface-hub/images/sh2-thermal-audio.png b/devices/surface-hub/images/sh2-thermal-audio.png
deleted file mode 100644
index 5d9640df9b..0000000000
Binary files a/devices/surface-hub/images/sh2-thermal-audio.png and /dev/null differ
diff --git a/devices/surface-hub/images/sh2-token.png b/devices/surface-hub/images/sh2-token.png
deleted file mode 100644
index 115153a767..0000000000
Binary files a/devices/surface-hub/images/sh2-token.png and /dev/null differ
diff --git a/devices/surface-hub/images/sh2-token2.png b/devices/surface-hub/images/sh2-token2.png
deleted file mode 100644
index 324bc27f63..0000000000
Binary files a/devices/surface-hub/images/sh2-token2.png and /dev/null differ
diff --git a/devices/surface-hub/images/sh2-token3.png b/devices/surface-hub/images/sh2-token3.png
deleted file mode 100644
index 04e173d391..0000000000
Binary files a/devices/surface-hub/images/sh2-token3.png and /dev/null differ
diff --git a/devices/surface-hub/images/sh2-uefi1.png b/devices/surface-hub/images/sh2-uefi1.png
deleted file mode 100644
index ecb5aad455..0000000000
Binary files a/devices/surface-hub/images/sh2-uefi1.png and /dev/null differ
diff --git a/devices/surface-hub/images/sh2-uefi10.png b/devices/surface-hub/images/sh2-uefi10.png
deleted file mode 100644
index eafc0617a2..0000000000
Binary files a/devices/surface-hub/images/sh2-uefi10.png and /dev/null differ
diff --git a/devices/surface-hub/images/sh2-uefi2.png b/devices/surface-hub/images/sh2-uefi2.png
deleted file mode 100644
index 8dbcb3df84..0000000000
Binary files a/devices/surface-hub/images/sh2-uefi2.png and /dev/null differ
diff --git a/devices/surface-hub/images/sh2-uefi3.png b/devices/surface-hub/images/sh2-uefi3.png
deleted file mode 100644
index f9b0fdb754..0000000000
Binary files a/devices/surface-hub/images/sh2-uefi3.png and /dev/null differ
diff --git a/devices/surface-hub/images/sh2-uefi4.png b/devices/surface-hub/images/sh2-uefi4.png
deleted file mode 100644
index ae6f427772..0000000000
Binary files a/devices/surface-hub/images/sh2-uefi4.png and /dev/null differ
diff --git a/devices/surface-hub/images/sh2-uefi5.png b/devices/surface-hub/images/sh2-uefi5.png
deleted file mode 100644
index 18a780074f..0000000000
Binary files a/devices/surface-hub/images/sh2-uefi5.png and /dev/null differ
diff --git a/devices/surface-hub/images/sh2-uefi6.png b/devices/surface-hub/images/sh2-uefi6.png
deleted file mode 100644
index 7b4390574a..0000000000
Binary files a/devices/surface-hub/images/sh2-uefi6.png and /dev/null differ
diff --git a/devices/surface-hub/images/sh2-uefi7.png b/devices/surface-hub/images/sh2-uefi7.png
deleted file mode 100644
index 0302b41a43..0000000000
Binary files a/devices/surface-hub/images/sh2-uefi7.png and /dev/null differ
diff --git a/devices/surface-hub/images/sh2-uefi8.png b/devices/surface-hub/images/sh2-uefi8.png
deleted file mode 100644
index c5ccc27628..0000000000
Binary files a/devices/surface-hub/images/sh2-uefi8.png and /dev/null differ
diff --git a/devices/surface-hub/images/sh2-uefi9.png b/devices/surface-hub/images/sh2-uefi9.png
deleted file mode 100644
index 4747c398c8..0000000000
Binary files a/devices/surface-hub/images/sh2-uefi9.png and /dev/null differ
diff --git a/devices/surface-hub/images/sh2-wall-front.png b/devices/surface-hub/images/sh2-wall-front.png
deleted file mode 100644
index 349e124bb0..0000000000
Binary files a/devices/surface-hub/images/sh2-wall-front.png and /dev/null differ
diff --git a/devices/surface-hub/images/sh2-wall-side.png b/devices/surface-hub/images/sh2-wall-side.png
deleted file mode 100644
index f09cbda81e..0000000000
Binary files a/devices/surface-hub/images/sh2-wall-side.png and /dev/null differ
diff --git a/devices/surface-hub/images/sh2-wcd.png b/devices/surface-hub/images/sh2-wcd.png
deleted file mode 100644
index 8a945dfca4..0000000000
Binary files a/devices/surface-hub/images/sh2-wcd.png and /dev/null differ
diff --git a/devices/surface-hub/images/shrt-complete.png b/devices/surface-hub/images/shrt-complete.png
deleted file mode 100644
index 64525f76a3..0000000000
Binary files a/devices/surface-hub/images/shrt-complete.png and /dev/null differ
diff --git a/devices/surface-hub/images/shrt-done.png b/devices/surface-hub/images/shrt-done.png
deleted file mode 100644
index ea05c13051..0000000000
Binary files a/devices/surface-hub/images/shrt-done.png and /dev/null differ
diff --git a/devices/surface-hub/images/shrt-download.png b/devices/surface-hub/images/shrt-download.png
deleted file mode 100644
index 8eee758a54..0000000000
Binary files a/devices/surface-hub/images/shrt-download.png and /dev/null differ
diff --git a/devices/surface-hub/images/shrt-drive-start.png b/devices/surface-hub/images/shrt-drive-start.png
deleted file mode 100644
index 490998f214..0000000000
Binary files a/devices/surface-hub/images/shrt-drive-start.png and /dev/null differ
diff --git a/devices/surface-hub/images/shrt-drive.png b/devices/surface-hub/images/shrt-drive.png
deleted file mode 100644
index 9afeb4b7f3..0000000000
Binary files a/devices/surface-hub/images/shrt-drive.png and /dev/null differ
diff --git a/devices/surface-hub/images/shrt-guidance.png b/devices/surface-hub/images/shrt-guidance.png
deleted file mode 100644
index c878761704..0000000000
Binary files a/devices/surface-hub/images/shrt-guidance.png and /dev/null differ
diff --git a/devices/surface-hub/images/shrt-shortcut.png b/devices/surface-hub/images/shrt-shortcut.png
deleted file mode 100644
index d71d3e163c..0000000000
Binary files a/devices/surface-hub/images/shrt-shortcut.png and /dev/null differ
diff --git a/devices/surface-hub/images/shrt-start.png b/devices/surface-hub/images/shrt-start.png
deleted file mode 100644
index 93356c889b..0000000000
Binary files a/devices/surface-hub/images/shrt-start.png and /dev/null differ
diff --git a/devices/surface-hub/images/sign-in-prov.png b/devices/surface-hub/images/sign-in-prov.png
deleted file mode 100644
index 55c9276203..0000000000
Binary files a/devices/surface-hub/images/sign-in-prov.png and /dev/null differ
diff --git a/devices/surface-hub/images/sign-in.png b/devices/surface-hub/images/sign-in.png
deleted file mode 100644
index bd34f642a7..0000000000
Binary files a/devices/surface-hub/images/sign-in.png and /dev/null differ
diff --git a/devices/surface-hub/images/six.png b/devices/surface-hub/images/six.png
deleted file mode 100644
index 2816328ec3..0000000000
Binary files a/devices/surface-hub/images/six.png and /dev/null differ
diff --git a/devices/surface-hub/images/ssd-click.PNG b/devices/surface-hub/images/ssd-click.PNG
deleted file mode 100644
index 5dfcc57c42..0000000000
Binary files a/devices/surface-hub/images/ssd-click.PNG and /dev/null differ
diff --git a/devices/surface-hub/images/ssd-lift-door.PNG b/devices/surface-hub/images/ssd-lift-door.PNG
deleted file mode 100644
index d395ce91aa..0000000000
Binary files a/devices/surface-hub/images/ssd-lift-door.PNG and /dev/null differ
diff --git a/devices/surface-hub/images/ssd-location.PNG b/devices/surface-hub/images/ssd-location.PNG
deleted file mode 100644
index 9b774456b1..0000000000
Binary files a/devices/surface-hub/images/ssd-location.PNG and /dev/null differ
diff --git a/devices/surface-hub/images/ssd-lock-tab.PNG b/devices/surface-hub/images/ssd-lock-tab.PNG
deleted file mode 100644
index 17c11dc7a2..0000000000
Binary files a/devices/surface-hub/images/ssd-lock-tab.PNG and /dev/null differ
diff --git a/devices/surface-hub/images/ssd-pull-tab.PNG b/devices/surface-hub/images/ssd-pull-tab.PNG
deleted file mode 100644
index a306f08a13..0000000000
Binary files a/devices/surface-hub/images/ssd-pull-tab.PNG and /dev/null differ
diff --git a/devices/surface-hub/images/surface-hub-2s-repack-1.png b/devices/surface-hub/images/surface-hub-2s-repack-1.png
deleted file mode 100644
index c78a536083..0000000000
Binary files a/devices/surface-hub/images/surface-hub-2s-repack-1.png and /dev/null differ
diff --git a/devices/surface-hub/images/surface-hub-2s-repack-10.png b/devices/surface-hub/images/surface-hub-2s-repack-10.png
deleted file mode 100644
index ae99a0697a..0000000000
Binary files a/devices/surface-hub/images/surface-hub-2s-repack-10.png and /dev/null differ
diff --git a/devices/surface-hub/images/surface-hub-2s-repack-11.png b/devices/surface-hub/images/surface-hub-2s-repack-11.png
deleted file mode 100644
index 1d79a116ef..0000000000
Binary files a/devices/surface-hub/images/surface-hub-2s-repack-11.png and /dev/null differ
diff --git a/devices/surface-hub/images/surface-hub-2s-repack-12.png b/devices/surface-hub/images/surface-hub-2s-repack-12.png
deleted file mode 100644
index 67108c5110..0000000000
Binary files a/devices/surface-hub/images/surface-hub-2s-repack-12.png and /dev/null differ
diff --git a/devices/surface-hub/images/surface-hub-2s-repack-13.png b/devices/surface-hub/images/surface-hub-2s-repack-13.png
deleted file mode 100644
index 565d0469c5..0000000000
Binary files a/devices/surface-hub/images/surface-hub-2s-repack-13.png and /dev/null differ
diff --git a/devices/surface-hub/images/surface-hub-2s-repack-2.png b/devices/surface-hub/images/surface-hub-2s-repack-2.png
deleted file mode 100644
index 117f0d5899..0000000000
Binary files a/devices/surface-hub/images/surface-hub-2s-repack-2.png and /dev/null differ
diff --git a/devices/surface-hub/images/surface-hub-2s-repack-3.png b/devices/surface-hub/images/surface-hub-2s-repack-3.png
deleted file mode 100644
index 53afdbd11c..0000000000
Binary files a/devices/surface-hub/images/surface-hub-2s-repack-3.png and /dev/null differ
diff --git a/devices/surface-hub/images/surface-hub-2s-repack-4.png b/devices/surface-hub/images/surface-hub-2s-repack-4.png
deleted file mode 100644
index cc213389d9..0000000000
Binary files a/devices/surface-hub/images/surface-hub-2s-repack-4.png and /dev/null differ
diff --git a/devices/surface-hub/images/surface-hub-2s-repack-5.png b/devices/surface-hub/images/surface-hub-2s-repack-5.png
deleted file mode 100644
index 202963bcb5..0000000000
Binary files a/devices/surface-hub/images/surface-hub-2s-repack-5.png and /dev/null differ
diff --git a/devices/surface-hub/images/surface-hub-2s-repack-6.png b/devices/surface-hub/images/surface-hub-2s-repack-6.png
deleted file mode 100644
index d7617b8f1b..0000000000
Binary files a/devices/surface-hub/images/surface-hub-2s-repack-6.png and /dev/null differ
diff --git a/devices/surface-hub/images/surface-hub-2s-repack-7.png b/devices/surface-hub/images/surface-hub-2s-repack-7.png
deleted file mode 100644
index 18310ea9cb..0000000000
Binary files a/devices/surface-hub/images/surface-hub-2s-repack-7.png and /dev/null differ
diff --git a/devices/surface-hub/images/surface-hub-2s-repack-8.png b/devices/surface-hub/images/surface-hub-2s-repack-8.png
deleted file mode 100644
index fb5b8929bb..0000000000
Binary files a/devices/surface-hub/images/surface-hub-2s-repack-8.png and /dev/null differ
diff --git a/devices/surface-hub/images/surface-hub-2s-repack-9.png b/devices/surface-hub/images/surface-hub-2s-repack-9.png
deleted file mode 100644
index be9ceb2bee..0000000000
Binary files a/devices/surface-hub/images/surface-hub-2s-repack-9.png and /dev/null differ
diff --git a/devices/surface-hub/images/surface-hub-2s-replace-camera-1.png b/devices/surface-hub/images/surface-hub-2s-replace-camera-1.png
deleted file mode 100644
index 57ed3f50a6..0000000000
Binary files a/devices/surface-hub/images/surface-hub-2s-replace-camera-1.png and /dev/null differ
diff --git a/devices/surface-hub/images/surface-hub-2s-replace-camera-2.png b/devices/surface-hub/images/surface-hub-2s-replace-camera-2.png
deleted file mode 100644
index 888d417b0e..0000000000
Binary files a/devices/surface-hub/images/surface-hub-2s-replace-camera-2.png and /dev/null differ
diff --git a/devices/surface-hub/images/surface-hub-2s-replace-cartridge-1.png b/devices/surface-hub/images/surface-hub-2s-replace-cartridge-1.png
deleted file mode 100644
index 5924546a4c..0000000000
Binary files a/devices/surface-hub/images/surface-hub-2s-replace-cartridge-1.png and /dev/null differ
diff --git a/devices/surface-hub/images/surface-hub-2s-replace-cartridge-10.png b/devices/surface-hub/images/surface-hub-2s-replace-cartridge-10.png
deleted file mode 100644
index a1d6d6d163..0000000000
Binary files a/devices/surface-hub/images/surface-hub-2s-replace-cartridge-10.png and /dev/null differ
diff --git a/devices/surface-hub/images/surface-hub-2s-replace-cartridge-2.png b/devices/surface-hub/images/surface-hub-2s-replace-cartridge-2.png
deleted file mode 100644
index ddb0ccfc7d..0000000000
Binary files a/devices/surface-hub/images/surface-hub-2s-replace-cartridge-2.png and /dev/null differ
diff --git a/devices/surface-hub/images/surface-hub-2s-replace-cartridge-3.png b/devices/surface-hub/images/surface-hub-2s-replace-cartridge-3.png
deleted file mode 100644
index 1e9156e94f..0000000000
Binary files a/devices/surface-hub/images/surface-hub-2s-replace-cartridge-3.png and /dev/null differ
diff --git a/devices/surface-hub/images/surface-hub-2s-replace-cartridge-4.png b/devices/surface-hub/images/surface-hub-2s-replace-cartridge-4.png
deleted file mode 100644
index 9885cc6c7a..0000000000
Binary files a/devices/surface-hub/images/surface-hub-2s-replace-cartridge-4.png and /dev/null differ
diff --git a/devices/surface-hub/images/surface-hub-2s-replace-cartridge-5.png b/devices/surface-hub/images/surface-hub-2s-replace-cartridge-5.png
deleted file mode 100644
index 54cb393ff4..0000000000
Binary files a/devices/surface-hub/images/surface-hub-2s-replace-cartridge-5.png and /dev/null differ
diff --git a/devices/surface-hub/images/surface-hub-2s-replace-cartridge-6.png b/devices/surface-hub/images/surface-hub-2s-replace-cartridge-6.png
deleted file mode 100644
index e74270f93b..0000000000
Binary files a/devices/surface-hub/images/surface-hub-2s-replace-cartridge-6.png and /dev/null differ
diff --git a/devices/surface-hub/images/surface-hub-2s-replace-cartridge-7.png b/devices/surface-hub/images/surface-hub-2s-replace-cartridge-7.png
deleted file mode 100644
index 39fd3da31f..0000000000
Binary files a/devices/surface-hub/images/surface-hub-2s-replace-cartridge-7.png and /dev/null differ
diff --git a/devices/surface-hub/images/surface-hub-2s-replace-cartridge-8.png b/devices/surface-hub/images/surface-hub-2s-replace-cartridge-8.png
deleted file mode 100644
index c68b5fab64..0000000000
Binary files a/devices/surface-hub/images/surface-hub-2s-replace-cartridge-8.png and /dev/null differ
diff --git a/devices/surface-hub/images/surface-hub-2s-replace-cartridge-9.png b/devices/surface-hub/images/surface-hub-2s-replace-cartridge-9.png
deleted file mode 100644
index 6acb8a627d..0000000000
Binary files a/devices/surface-hub/images/surface-hub-2s-replace-cartridge-9.png and /dev/null differ
diff --git a/devices/surface-hub/images/surfaceblog.png b/devices/surface-hub/images/surfaceblog.png
deleted file mode 100644
index ae996a918c..0000000000
Binary files a/devices/surface-hub/images/surfaceblog.png and /dev/null differ
diff --git a/devices/surface-hub/images/surfacehub.png b/devices/surface-hub/images/surfacehub.png
deleted file mode 100644
index 1b9b484ab8..0000000000
Binary files a/devices/surface-hub/images/surfacehub.png and /dev/null differ
diff --git a/devices/surface-hub/images/surfacemechanics.png b/devices/surface-hub/images/surfacemechanics.png
deleted file mode 100644
index ad674466fa..0000000000
Binary files a/devices/surface-hub/images/surfacemechanics.png and /dev/null differ
diff --git a/devices/surface-hub/images/switch.png b/devices/surface-hub/images/switch.png
deleted file mode 100644
index 5ea0d21909..0000000000
Binary files a/devices/surface-hub/images/switch.png and /dev/null differ
diff --git a/devices/surface-hub/images/system-settings-add-fqdn.png b/devices/surface-hub/images/system-settings-add-fqdn.png
deleted file mode 100644
index ef00872a16..0000000000
Binary files a/devices/surface-hub/images/system-settings-add-fqdn.png and /dev/null differ
diff --git a/devices/surface-hub/images/three.png b/devices/surface-hub/images/three.png
deleted file mode 100644
index 887fa270d7..0000000000
Binary files a/devices/surface-hub/images/three.png and /dev/null differ
diff --git a/devices/surface-hub/images/trust-package.png b/devices/surface-hub/images/trust-package.png
deleted file mode 100644
index 8a293ea4da..0000000000
Binary files a/devices/surface-hub/images/trust-package.png and /dev/null differ
diff --git a/devices/surface-hub/images/twitter.png b/devices/surface-hub/images/twitter.png
deleted file mode 100644
index 25143adcf6..0000000000
Binary files a/devices/surface-hub/images/twitter.png and /dev/null differ
diff --git a/devices/surface-hub/images/two.png b/devices/surface-hub/images/two.png
deleted file mode 100644
index b8c2d52eaf..0000000000
Binary files a/devices/surface-hub/images/two.png and /dev/null differ
diff --git a/devices/surface-hub/images/usb.png b/devices/surface-hub/images/usb.png
deleted file mode 100644
index a743c6b634..0000000000
Binary files a/devices/surface-hub/images/usb.png and /dev/null differ
diff --git a/devices/surface-hub/images/vga.png b/devices/surface-hub/images/vga.png
deleted file mode 100644
index 016b42d1f4..0000000000
Binary files a/devices/surface-hub/images/vga.png and /dev/null differ
diff --git a/devices/surface-hub/images/video-out-55.png b/devices/surface-hub/images/video-out-55.png
deleted file mode 100644
index e386b7f3d9..0000000000
Binary files a/devices/surface-hub/images/video-out-55.png and /dev/null differ
diff --git a/devices/surface-hub/images/video-out-84.png b/devices/surface-hub/images/video-out-84.png
deleted file mode 100644
index 672ae78556..0000000000
Binary files a/devices/surface-hub/images/video-out-84.png and /dev/null differ
diff --git a/devices/surface-hub/images/wb-collab-example.png b/devices/surface-hub/images/wb-collab-example.png
deleted file mode 100644
index 0ed67c03ea..0000000000
Binary files a/devices/surface-hub/images/wb-collab-example.png and /dev/null differ
diff --git a/devices/surface-hub/images/wb-collab-link.png b/devices/surface-hub/images/wb-collab-link.png
deleted file mode 100644
index 9b0531d0c0..0000000000
Binary files a/devices/surface-hub/images/wb-collab-link.png and /dev/null differ
diff --git a/devices/surface-hub/images/wcd-wizard.PNG b/devices/surface-hub/images/wcd-wizard.PNG
deleted file mode 100644
index 706771f756..0000000000
Binary files a/devices/surface-hub/images/wcd-wizard.PNG and /dev/null differ
diff --git a/devices/surface-hub/images/whats-new-video-thumbnail.PNG b/devices/surface-hub/images/whats-new-video-thumbnail.PNG
deleted file mode 100644
index 44cbffcbb3..0000000000
Binary files a/devices/surface-hub/images/whats-new-video-thumbnail.PNG and /dev/null differ
diff --git a/devices/surface-hub/images/who-owns-pc.png b/devices/surface-hub/images/who-owns-pc.png
deleted file mode 100644
index d3ce1def8d..0000000000
Binary files a/devices/surface-hub/images/who-owns-pc.png and /dev/null differ
diff --git a/devices/surface-hub/images/wicd-screen-apps-02a.png b/devices/surface-hub/images/wicd-screen-apps-02a.png
deleted file mode 100644
index caf88b011e..0000000000
Binary files a/devices/surface-hub/images/wicd-screen-apps-02a.png and /dev/null differ
diff --git a/devices/surface-hub/images/wicd-screen-apps-03a.png b/devices/surface-hub/images/wicd-screen-apps-03a.png
deleted file mode 100644
index 20d4218c6b..0000000000
Binary files a/devices/surface-hub/images/wicd-screen-apps-03a.png and /dev/null differ
diff --git a/devices/surface-hub/images/wicd-screen-apps-04a.png b/devices/surface-hub/images/wicd-screen-apps-04a.png
deleted file mode 100644
index 494a661420..0000000000
Binary files a/devices/surface-hub/images/wicd-screen-apps-04a.png and /dev/null differ
diff --git a/devices/surface-hub/images/wicd-screen-apps-06a.png b/devices/surface-hub/images/wicd-screen-apps-06a.png
deleted file mode 100644
index 44e6e2cee7..0000000000
Binary files a/devices/surface-hub/images/wicd-screen-apps-06a.png and /dev/null differ
diff --git a/devices/surface-hub/images/wicd-screen-apps-08a.png b/devices/surface-hub/images/wicd-screen-apps-08a.png
deleted file mode 100644
index 19ce342449..0000000000
Binary files a/devices/surface-hub/images/wicd-screen-apps-08a.png and /dev/null differ
diff --git a/devices/surface-hub/images/wicd-screen-apps-10a.png b/devices/surface-hub/images/wicd-screen-apps-10a.png
deleted file mode 100644
index 820fd3efff..0000000000
Binary files a/devices/surface-hub/images/wicd-screen-apps-10a.png and /dev/null differ
diff --git a/devices/surface-hub/images/wicd-screen-apps-11a.png b/devices/surface-hub/images/wicd-screen-apps-11a.png
deleted file mode 100644
index 2bf0a692ef..0000000000
Binary files a/devices/surface-hub/images/wicd-screen-apps-11a.png and /dev/null differ
diff --git a/devices/surface-hub/images/wicd-screen-apps-12a.png b/devices/surface-hub/images/wicd-screen-apps-12a.png
deleted file mode 100644
index 8ab9d524f4..0000000000
Binary files a/devices/surface-hub/images/wicd-screen-apps-12a.png and /dev/null differ
diff --git a/devices/surface-hub/images/wicd-screen01a.png b/devices/surface-hub/images/wicd-screen01a.png
deleted file mode 100644
index 34b528951e..0000000000
Binary files a/devices/surface-hub/images/wicd-screen01a.png and /dev/null differ
diff --git a/devices/surface-hub/images/wicd-screen02a.png b/devices/surface-hub/images/wicd-screen02a.png
deleted file mode 100644
index f76eec1efb..0000000000
Binary files a/devices/surface-hub/images/wicd-screen02a.png and /dev/null differ
diff --git a/devices/surface-hub/images/wicd-screen02b.png b/devices/surface-hub/images/wicd-screen02b.png
deleted file mode 100644
index 6686186f8b..0000000000
Binary files a/devices/surface-hub/images/wicd-screen02b.png and /dev/null differ
diff --git a/devices/surface-hub/images/wicd-screen02c.png b/devices/surface-hub/images/wicd-screen02c.png
deleted file mode 100644
index eb8fd6b307..0000000000
Binary files a/devices/surface-hub/images/wicd-screen02c.png and /dev/null differ
diff --git a/devices/surface-hub/images/wicd-screen03a.png b/devices/surface-hub/images/wicd-screen03a.png
deleted file mode 100644
index afec8ef352..0000000000
Binary files a/devices/surface-hub/images/wicd-screen03a.png and /dev/null differ
diff --git a/devices/surface-hub/images/wicd-screen04a.png b/devices/surface-hub/images/wicd-screen04a.png
deleted file mode 100644
index 62ea7e595c..0000000000
Binary files a/devices/surface-hub/images/wicd-screen04a.png and /dev/null differ
diff --git a/devices/surface-hub/images/wicd-screen06a.png b/devices/surface-hub/images/wicd-screen06a.png
deleted file mode 100644
index 53c223746b..0000000000
Binary files a/devices/surface-hub/images/wicd-screen06a.png and /dev/null differ
diff --git a/devices/surface-hub/images/wicd-screen07a.png b/devices/surface-hub/images/wicd-screen07a.png
deleted file mode 100644
index e44f5cf0b7..0000000000
Binary files a/devices/surface-hub/images/wicd-screen07a.png and /dev/null differ
diff --git a/devices/surface-hub/images/wicd-screen08a.png b/devices/surface-hub/images/wicd-screen08a.png
deleted file mode 100644
index 7a2b5bbefb..0000000000
Binary files a/devices/surface-hub/images/wicd-screen08a.png and /dev/null differ
diff --git a/devices/surface-hub/images/wicd-screen09a.png b/devices/surface-hub/images/wicd-screen09a.png
deleted file mode 100644
index 29e14902bd..0000000000
Binary files a/devices/surface-hub/images/wicd-screen09a.png and /dev/null differ
diff --git a/devices/surface-hub/images/wicd-screen10a.png b/devices/surface-hub/images/wicd-screen10a.png
deleted file mode 100644
index 556c9fbdb5..0000000000
Binary files a/devices/surface-hub/images/wicd-screen10a.png and /dev/null differ
diff --git a/devices/surface-hub/images/wicd-screen11a.png b/devices/surface-hub/images/wicd-screen11a.png
deleted file mode 100644
index 9f7bf2ba64..0000000000
Binary files a/devices/surface-hub/images/wicd-screen11a.png and /dev/null differ
diff --git a/devices/surface-hub/images/wicd-screen12a.png b/devices/surface-hub/images/wicd-screen12a.png
deleted file mode 100644
index 7c55111ae4..0000000000
Binary files a/devices/surface-hub/images/wicd-screen12a.png and /dev/null differ
diff --git a/devices/surface-hub/images/~$rface-hub-site-readiness-guide-en-us.docx b/devices/surface-hub/images/~$rface-hub-site-readiness-guide-en-us.docx
deleted file mode 100644
index 1d44312447..0000000000
Binary files a/devices/surface-hub/images/~$rface-hub-site-readiness-guide-en-us.docx and /dev/null differ
diff --git a/devices/surface-hub/index.yml b/devices/surface-hub/index.yml
deleted file mode 100644
index 249deba5a0..0000000000
--- a/devices/surface-hub/index.yml
+++ /dev/null
@@ -1,127 +0,0 @@
-### YamlMime:Hub
-
-title: Surface Hub documentation # < 60 chars
-summary: Surface Hub 2S is an all-in-one digital interactive whiteboard, meetings platform, and collaborative computing device. # < 160 chars
-# brand: aspnet | azure | dotnet | dynamics | m365 | ms-graph | office | power-bi | power-platform | sql | sql-server | vs | visual-studio | windows | xamarin
-brand: windows
-
-metadata:
- title: Surface Hub documentation # Required; page title displayed in search results. Include the brand. < 60 chars.
- description: Get started with Microsoft Surface Hub. # Required; article description that is displayed in search results. < 160 chars.
- services: product-insights
- ms.service: product-insights #Required; service per approved list. service slug assigned to your service by ACOM.
- ms.topic: hub-page # Required
- ms.prod: surface-hub
- ms.technology: windows
- audience: ITPro
- ms.localizationpriority: medium
- author: greg-lindsay #Required; your GitHub user alias, with correct capitalization.
- ms.author: greglin #Required; microsoft alias of author; optional team alias.
- manager: laurawi
-
-# highlightedContent section (optional)
-# Maximum of 8 items
-highlightedContent:
-# itemType: architecture | concept | deploy | download | get-started | how-to-guide | learn | overview | quickstart | reference | sample | tutorial | video | whats-new
- items:
- # Card
- - title: What's new in Surface Hub 2S?
- itemType: whats-new
- url: surface-hub-2s-whats-new.md
- # Card
- - title: Surface Hub security overview
- itemType: learn
- url: surface-hub-security.md
- # Card
- - title: Manage Surface Hub 2S with Intune
- itemType: how-to-guide
- url: surface-hub-2s-manage-intune.md
- # Card
- - title: Operating system essentials
- itemType: learn
- url: differences-between-surface-hub-and-windows-10-enterprise.md
- # Card
- - title: Surface Hub 2S Site Readiness Guide
- itemType: learn
- url: surface-hub-2s-site-readiness-guide.md
- # Card
- - title: Customize Surface Hub 2S installation
- itemType: how-to-guide
- url: surface-hub-2s-custom-install.md
-
-# productDirectory section (optional)
-productDirectory:
- title: Deploy, manage, and support your Surface Hub devices # < 60 chars (optional)
- summary: Find related links to deploy, manage and support your Surface Hub devices. # < 160 chars (optional)
- items:
- # Card
- - title: Deploy
- # imageSrc should be square in ratio with no whitespace
- imageSrc: https://docs.microsoft.com/office/media/icons/deploy-blue.svg
- links:
- - url: surface-hub-2s-adoption-kit.md
- text: Surface Hub 2S adoption and training
- - url: surface-hub-2s-deploy-checklist.md
- text: Surface Hub 2S deployment checklist
- - url: surface-hub-2s-account.md
- text: Create device account
- # Card
- - title: Manage
- imageSrc: https://docs.microsoft.com/office/media/icons/process-flow-blue.svg
- links:
- - url: surface-hub-2s-manage-intune.md
- text: Manage with Intune
- - url: local-management-surface-hub-settings.md
- text: Manage local settings
- # Card
- - title: Secure
- imageSrc: https://docs.microsoft.com/office/media/icons/security-blue.svg
- links:
- - url: surface-hub-2s-secure-with-uefi-semm.md
- text: Secure with UEFI and SEMM
- - url: surface-hub-wifi-direct.md
- text: Wi-Fi security considerations
- # Card
- - title: Troubleshoot
- imageSrc: https://docs.microsoft.com/office/media/icons/connector-blue.svg
- links:
- - url: https://support.microsoft.com/help/4493926
- text: Service and warranty
- - url: surface-hub-2s-recover-reset.md
- text: Recover & reset Surface Hub 2S
- - url: support-solutions-surface-hub.md
- text: Surface Hub support solutions
- - url: https://support.office.com/article/Enable-Microsoft-Whiteboard-on-Surface-Hub-b5df4539-f735-42ff-b22a-0f5e21be7627
- text: Enable Microsoft Whiteboard on Surface Hub
-
-# additionalContent section (optional)
-# Card with links style
-additionalContent:
- # Supports up to 3 sections
- sections:
- - title: Other content # < 60 chars (optional)
- summary: Find related links for videos, community and support. # < 160 chars (optional)
- items:
- # Card
- - title: Get ready for Surface Hub 2S
- links:
- - text: Ordering Surface Hub 2S
- url: https://www.microsoft.com/p/surface-hub-2S/8P62MW6BN9G4?activetab=pivot:overviewtab
- - text: Prepare your environment for Surface Hub 2S
- url: surface-hub-2s-prepare-environment.md
- # Card
- - title: Surface Hub 2S Videos
- links:
- - text: Adoption and training videos
- url: surface-hub-2s-adoption-videos.md
- - text: Surface Hub 2S with Teams
- url: https://www.youtube.com/watch?v=CH2seLS5Wb0
- - text: Surface Hub 2S with Microsoft 365
- url: https://www.youtube.com/watch?v=I4N2lQX4WyI&list=PLXtHYVsvn_b__1Baibdu4elN4SoF3JTBZ&index=7
- # Card
- - title: Community
- links:
- - text: Join the Surface Hub Technical Community
- url: https://techcommunity.microsoft.com/t5/Surface-Hub/bd-p/SurfaceHub
- - text: Join the Surface Devices Technical Community
- url: https://techcommunity.microsoft.com/t5/Surface-Devices/ct-p/SurfaceDevices
diff --git a/devices/surface-hub/install-apps-on-surface-hub.md b/devices/surface-hub/install-apps-on-surface-hub.md
deleted file mode 100644
index 9e1c8767f5..0000000000
--- a/devices/surface-hub/install-apps-on-surface-hub.md
+++ /dev/null
@@ -1,188 +0,0 @@
----
-title: Install apps on your Microsoft Surface Hub
-description: Admins can install apps can from either the Microsoft Store or the Microsoft Store for Business.
-ms.assetid: 3885CB45-D496-4424-8533-C9E3D0EDFD94
-ms.reviewer:
-manager: laurawi
-keywords: install apps, Microsoft Store, Microsoft Store for Business
-ms.prod: surface-hub
-ms.sitesec: library
-author: dansimp
-ms.author: dansimp
-ms.topic: article
-ms.date: 10/23/2018
-ms.localizationpriority: medium
-audience: ITPro
----
-
-# Install apps on your Microsoft Surface Hub
-
-You can install additional apps on your Surface Hub to fit your team or organization's needs. There are different methods for installing apps depending on whether you are developing and testing an app, or deploying a released app. This topic describes methods for installing apps for either scenario.
-
-A few things to know about apps on Surface Hub:
-- Surface Hub only runs [Universal Windows Platform (UWP) apps](https://msdn.microsoft.com/windows/uwp/get-started/whats-a-uwp). Apps created using the [Desktop App Converter](https://docs.microsoft.com/windows/uwp/porting/desktop-to-uwp-run-desktop-app-converter) will not run on Surface Hub.
-- Apps must be targeted for the [Universal device family](https://msdn.microsoft.com/library/windows/apps/dn894631) or Windows Team device family.
-- Surface Hub only supports [offline-licensed apps](https://docs.microsoft.com/microsoft-store/distribute-offline-apps) from [Microsoft Store for Business](https://businessstore.microsoft.com/store).
-- By default, apps must be Store-signed to be installed. During testing and development, you can also choose to run developer-signed UWP apps by placing the device in developer mode.
-- When submitting an app to the Microsoft Store, developers need to set Device family availability and Organizational licensing options to make sure an app will be available to run on Surface Hub.
-- You need admin credentials to install apps on your Surface Hub. Since the device is designed to be used in communal spaces like meeting rooms, people can't access the Microsoft Store to download and install apps.
-
-
-## Develop and test apps
-While you're developing your own app, there are a few options for testing apps on Surface Hub.
-
-### Developer Mode
-By default, Surface Hub only runs UWP apps that have been published to and signed by the Microsoft Store. Apps submitted to the Microsoft Store go through security and compliance tests as part of the [app certification process](https://msdn.microsoft.com/windows/uwp/publish/the-app-certification-process), so this helps safeguard your Surface Hub against malicious apps.
-
-By enabling developer mode, you can also install developer-signed UWP apps.
-
-> [!IMPORTANT]
-> After developer mode has been enabled, you will need to reset the Surface Hub to disable it. Resetting the device removes all local user files and configurations and then reinstalls Windows.
-
-**To turn on developer mode**
-1. From your Surface Hub, start **Settings**.
-2. Type the device admin credentials when prompted.
-3. Navigate to **Update & security** > **For developers**.
-4. Select **Developer mode** and accept the warning prompt.
-
-### Visual Studio
-During development, the easiest way to test your app on a Surface Hub is using Visual Studio. Visual Studio's remote debugging feature helps you discover issues in your app before deploying it broadly. For more information, see [Test Surface Hub apps using Visual Studio](https://msdn.microsoft.com/windows/uwp/debug-test-perf/test-surface-hub-apps-using-visual-studio).
-
-### Provisioning package
-Use Visual Studio to [create an app package](https://msdn.microsoft.com/library/windows/apps/hh454036.aspx) for your UWP app, signed using a test certificate. Then use Windows Imaging and Configuration Designer (ICD) to create a provisioning package containing the app package. For more information, see [Create provisioning packages](provisioning-packages-for-certificates-surface-hub.md).
-
-
-## Submit apps to the Microsoft Store
-Once an app is ready for release, developers need to submit and publish it to the Microsoft Store. For more information, see [Publish Windows apps](https://developer.microsoft.com/store/publish-apps).
-
-During app submission, developers need to set **Device family availability** and **Organizational licensing** options to make sure the app will be available to run on Surface Hub.
-
-**To set device family availability**
-1. On the [Windows Dev Center](https://developer.microsoft.com), navigate to your app submission page.
-2. Select **Packages**.
-3. Under **Device family availability**, select these options:
-
- - **Windows 10 Team**
- - **Let Microsoft decide whether to make the app available to any future device families**
-
-
-
-For more information, see [Device family availability](https://msdn.microsoft.com/windows/uwp/publish/upload-app-packages#device-family-availability).
-
-**To set organizational licensing**
-1. On the [Windows Dev Center](https://developer.microsoft.com), navigate to your app submission page.
-2. Select **Pricing and availability**.
-3. Under Organizational licensing, select **Allow disconnected (offline) licensing for organizations**.
-
-
-
-> [!NOTE]
-> **Make my app available to organizations with Store-managed (online) licensing and distribution** is selected by default.
-
-> [!NOTE]
-> Developers can also publish line-of-business apps directly to enterprises without making them broadly available in the Store. For more information, see [Distribute LOB apps to enterprises](https://msdn.microsoft.com/windows/uwp/publish/distribute-lob-apps-to-enterprises).
-
-For more information, see [Organizational licensing options](https://msdn.microsoft.com/windows/uwp/publish/organizational-licensing).
-
-
-## Deploy released apps
-
-There are several options for installing apps that have been released to the Microsoft Store, depending on whether you want to evaluate them on a few devices, or deploy them broadly to your organization.
-
-To install released apps:
-- Download the app using the Microsoft Store app, or
-- Download the app package from the Microsoft Store for Business, and distribute it using a provisioning package or a supported MDM provider.
-
-### Microsoft Store app
-To evaluate apps released on the Microsoft Store, use the Microsoft Store app on the Surface Hub to browse and download apps.
-
-> [!NOTE]
-> Using the Microsoft Store app is not the recommended method of deploying apps at scale to your organization:
-> - To download apps, you must sign in to the Microsoft Store app with a Microsoft account or organizational account. However, you can only connect an account to a maximum of 10 devices at once. If you have more than 10 Surface Hubs, you will need to create multiple accounts or remove devices from your account between app installations.
-> - To install apps, you will need to manually sign in to the Microsoft Store app on each Surface Hub you own.
-
-**To browse the Microsoft Store on Surface Hub**
-1. From your Surface Hub, start **Settings**.
-2. Type the device admin credentials when prompted.
-3. Navigate to **This device** > **Apps & features**.
-4. Select **Open Store**.
-
-### Download app packages from Microsoft Store for Business
-To download the app package you need to install apps on your Surface Hub, visit the [Microsoft Store for Business](https://www.microsoft.com/business-store). The Store for Business is where you can find, acquire, and manage apps for the Windows 10 devices in your organization, including Surface Hub.
-
-> [!NOTE]
-> Currently, Surface Hub only supports offline-licensed apps available through the Store for Business. App developers set offline-license availability when they submit apps.
-
-Find and acquire the app you want, then download:
-- The offline-licensed app package (either an .appx or an .appxbundle)
-- The *unencoded* license file (if you're using provisioning packages to install the app)
-- The *encoded* license file (if you're using MDM to distribute the app)
-- Any necessary dependency files
-
-For more information, see [Download an offline-licensed app](https://technet.microsoft.com/itpro/windows/manage/distribute-offline-apps#download-an-offline-licensed-app).
-
-### Provisioning package
-You can manually install the offline-licensed apps that you downloaded from the Store for Business on a few Surface Hubs using provisioning packages. Use Windows Imaging and Configuration Designer (ICD) to create a provisioning package containing the app package and *unencoded* license file that you downloaded from the Store for Business. For more information, see [Create provisioning packages](provisioning-packages-for-certificates-surface-hub.md).
-
-### Supported MDM provider
-To deploy apps to a large number of Surface Hubs in your organization, use a supported MDM provider. The table below shows which MDM providers support deploying offline-licensed app packages.
-
-| MDM provider | Supports offline-licensed app packages |
-|-----------------------------|----------------------------------------|
-| On-premises MDM with Configuration Manager (beginning in version 1602) | Yes |
-|
-| Third-party MDM provider | Check to make sure your MDM provider supports deploying offline-licensed app packages. |
-
-**To deploy apps remotely using Microsoft Endpoint Configuration Manager**
-
-> [!NOTE]
-> These instructions are based on the current branch of Microsoft Endpoint Configuration Manager.
-
-1. Enroll your Surface Hubs to Configuration Manager. For more information, see [Enroll a Surface Hub into MDM](manage-settings-with-mdm-for-surface-hub.md#enroll-into-mdm).
-2. Download the offline-licensed app package, the *encoded* license file, and any necessary dependency files from the Store for Business. For more information, see [Download an offline-licensed app](https://technet.microsoft.com/itpro/windows/manage/distribute-offline-apps#download-an-offline-licensed-app). Place the downloaded files in the same folder on a network share.
-3. In the **Software Library** workspace of the Configuration Manager console, click **Overview** > **Application Management** > **Applications**.
-4. On the **Home** tab, in the **Create** group, click **Create Application**.
-5. On the **General** page of the **Create Application Wizard**, select the **Automatically detect information about this application from installation files** check box.
-6. In the **Type** drop-down list, select **Windows app package (\*.appx, \*.appxbundle)**.
-7. In the **Location** field, specify the UNC path in the form \\server\share\\filename for the offline-licensed app package that you downloaded from the Store for Business. Alternatively, click **Browse** to browse to the app package.
-8. On the **Import Information** page, review the information that was imported, and then click **Next**. If necessary, you can click **Previous** to go back and correct any errors.
-9. On the **General Information** page, complete additional details about the app. Some of this information might already be populated if it was automatically obtained from the app package.
-10. Click **Next**, review the application information on the Summary page, and then complete the Create Application Wizard.
-11. Create a deployment type for the application. For more information, see [Create deployment types for the application](https://docs.microsoft.com/sccm/apps/deploy-use/create-applications#create-deployment-types-for-the-application).
-12. Deploy the application to your Surface Hubs. For more information, see [Deploy applications with Microsoft Endpoint Configuration Manager](https://docs.microsoft.com/sccm/apps/deploy-use/deploy-applications).
-13. As needed, update the app by downloading a new package from the Store for Business, and publishing an application revision in Configuration Manager. For more information, see [Update and retire applications with Microsoft Endpoint Configuration Manager](https://technet.microsoft.com/library/mt595704.aspx).
-
-> [!NOTE]
-> If you are using Microsoft Endpoint Configuration Manager (current branch), you can bypass the above steps by connecting the Store for Business to Configuration Manager. By doing so, you can synchronize the list of apps you've purchased with Configuration Manager, view these in the Configuration Manager console, and deploy them like you would any other app. For more information, see [Manage apps from the Microsoft Store for Business with Configuration Manager](https://technet.microsoft.com/library/mt740630.aspx).
-
-
-## Summary
-
-There are a few different ways to install apps on your Surface Hub depending on whether you are developing apps, evaluating apps on a small number of devices, or deploying apps broadly to your organization. This table summarizes the supported methods:
-
-| Install method | Developing apps | Evaluating apps on a few devices | Deploying apps broadly to your organization |
-| -------------------------- | --------------- | ------------------------------------- | ---------------------- |
-| Visual Studio | X | | |
-| Provisioning package | X | X | |
-| Microsoft Store app | | X | |
-| Supported MDM provider | | | X |
-
-## More information
-
-- [Blog post: Deploy Windows Store apps to Surface Hub using Intune](https://blogs.technet.microsoft.com/y0av/2018/01/18/7-2/)
-
-
-## Related topics
-
-[Manage Microsoft Surface Hub](manage-surface-hub.md)
-
-[Microsoft Surface Hub administrator's guide](surface-hub-administrators-guide.md)
-
-
-
-
-
-
-
-
-
diff --git a/devices/surface-hub/juneworkspace.code-workspace b/devices/surface-hub/juneworkspace.code-workspace
deleted file mode 100644
index f23e17c3ca..0000000000
--- a/devices/surface-hub/juneworkspace.code-workspace
+++ /dev/null
@@ -1,11 +0,0 @@
-{
- "folders": [
- {
- "path": "C:\\github\\windows-docs-pr"
- },
- {
- "path": "."
- }
- ],
- "settings": {}
-}
\ No newline at end of file
diff --git a/devices/surface-hub/known-issues-and-additional-info-about-surface-hub.md b/devices/surface-hub/known-issues-and-additional-info-about-surface-hub.md
deleted file mode 100644
index 003795ec22..0000000000
--- a/devices/surface-hub/known-issues-and-additional-info-about-surface-hub.md
+++ /dev/null
@@ -1,26 +0,0 @@
----
-title: Known issues and additional information about Microsoft Surface Hub
-description: Outlines known issues with Microsoft Surface Hub.
-ms.assetid: aee90a0c-fb05-466e-a2b1-92de89d0f2b7
-keywords: surface, hub, issues
-ms.prod: surface-hub
-ms.sitesec: library
-author: todmccoy
-ms.author: v-todmc
-ms.topic: article
-ms.localizationpriority: medium
----
-
-# Known issues and additional information about Microsoft Surface Hub
-
-We're listening. Quality is a top priority, and we want to keep you informed about issues impacting customers. The following are some known issues of Microsoft Surface Hub:
-
-- **Skype for Business isn't using proxy for media traffic with RS2**
- For some Surface Hub users who are behind a proxy, Skype for Business won't use the proxy server for media. However, the Surface Hub will be able to sign in to the account. We received your feedback and are aware of the media traffic issue when you are using proxy. We're actively investigating this issue and will release fixes as soon as a solution is identified and tested.
-
-- **For AAD joined devices, when a user tries to sign in to "My meetings & files", Surface Hub reports that there is no Internet connection**
- We’re aware of a set of issues that affect sign-in and document access on Surface Hub. We're actively investigating these issues. As a workaround until a resolution is released, customers can reset their devices and set up their Hub to use a local admin account. After reconfiguring to use the local admin account, "My meetings and files" will work as expected.
-- **Single sign-in when Azure AD joined**
- Surface Hub was designed for communal spaces, which impacts the way user credentials are stored. Because of this, there are currently limitations in how single sign-in works when devices are Azure AD joined. Microsoft is aware of this limitation and is actively investigating options for a resolution.
-- **Miracast over Infrastructure projection to Surface Hub fails if the Surface Hub has a dot character (.) in the friendly name**
- Surface Hub users may experience issues projecting to their device if the Friendly Name includes a period or dot in the name (.) -- for example, "Conf.Room42". To work around the issue, change the Friendly Name of the Hub in **Settings** > **Surface Hub** > **About**, and then restart the device. Microsoft is working on a solution to this issue.
\ No newline at end of file
diff --git a/devices/surface-hub/local-management-surface-hub-settings.md b/devices/surface-hub/local-management-surface-hub-settings.md
deleted file mode 100644
index 886e4b79f3..0000000000
--- a/devices/surface-hub/local-management-surface-hub-settings.md
+++ /dev/null
@@ -1,62 +0,0 @@
----
-title: Local management Surface Hub settings
-description: How to manage Surface Hub settings with Settings.
-keywords: manage Surface Hub, Surface Hub settings
-ms.prod: surface-hub
-ms.sitesec: library
-author: dansimp
-ms.author: dansimp
-ms.topic: article
-ms.date: 07/08/2019
-ms.reviewer:
-manager: laurawi
-ms.localizationpriority: medium
----
-
-# Local management for Surface Hub settings
-
-After initial setup of Microsoft Surface Hub, the device’s settings can be locally managed through **Settings**.
-
-## Surface Hub settings
-
-Surface Hubs have many settings that are common to other Windows devices, but also have settings which are only configurable on Surface Hubs. This table lists settings only configurable on Surface Hubs.
-
-| Setting | Location | Description |
-| ------- | -------- | ----------- |
-| Device account | Surface Hub > Accounts | Set or change the Surface Hub's device account. |
-| Device account sync status | Surface Hub > Accounts | Check the sync status of the device account’s mail and calendar on the Surface Hub. |
-| Password rotation | Surface Hub > Accounts | Choose whether to let the Surface Hub automatically rotate the device account's password.|
-| Change admin account password | Surface Hub > Accounts | Change the password for the local admin account. This is only available if you configured the device to use a local admin during first run. |
-| Device Management | Surface Hub > Device management | Manage policies and business applications using mobile device management (MDM). |
-| Provisioning packages | Surface Hub > Device management | Set or change provisioning packages installed on the Surface Hub. |
-| Open the Microsoft Store app | Surface Hub > Apps & features | The Microsoft Store app is only available to admins through the Settings app. |
-| Skype for Business domain name | Surface Hub > Calling & Audio | Configure a domain name for your Skype for Business server. |
-| Default Speaker volume | Surface Hub > Calling & Audio | Configure the default speaker volume for the Surface Hub when it starts a session. |
-| Default microphone and speaker settings | Surface Hub > Calling & Audio | Configure a default microphone and speaker for calls, and a default speaker for media playback. |
-| Enable Dolby Audio X2 | Surface Hub > Calling & Audio | Configure the Dolby Audio X2 speaker enhancements. |
-| Open Connect App automatically | Surface Hub > Projection | Choose whether projection will automatically open the Connect app or wait for user input before opening. |
-| Turn off wireless projection using Miracast | Surface Hub > Projection | Choose whether presenters can wirelessly project to the Surface Hub using Miracast. |
-| Require a PIN for wireless projection | Surface Hub > Projection | Choose whether people are required to enter a PIN before they use wireless projection. |
-| Wireless projection (Miracast) channel | Surface Hub > Projection | Set the channel for Miracast projection. |
-| Meeting info shown on the welcome screen | Surface Hub > Welcome screen | Choose whether meeting organizer, time, and subject show up on the welcome screen. |
-| Welcome screen background | Surface Hub > Welcome screen | Choose a background image for the welcome screen. |
-| Idle timeout to Welcome screen | Surface Hub > Session & Power | Choose how long until the Surface Hub returns to the welcome screen after no motion is detected. |
-| Resume session | Surface Hub > Session & Power | Choose to allow users to resume a session after no motion is detected or to automatically clean up a session. |
-| Access to Office 365 meetings and files | Surface Hub > Session & Power | Choose whether a user can sign in to Office 365 to get access to their meetings and files. |
-| Turn on screen with motion sensors | Surface Hub > Session & clean up | Choose whether the screen turns on when motion is detected. |
-| Session time out | Surface Hub > Session & clean up | Choose how long the device needs to be inactive before returning to the welcome screen. |
-| Sleep time out | Surface Hub > Session & clean up | Choose how long the device needs to be inactive before going to sleep mode. |
-| Friendly name | Surface Hub > About | Set the Surface Hub name that people will see when connecting wirelessly. |
-| Maintenance hours | Update & security > Windows Update > Advanced options | Configure when updates can be installed. |
-| Configure Windows Server Update Services (WSUS) server | Update & security > Windows Update > Advanced options | Change whether Surface Hub receives updates from a WSUS server instead of Windows Update. |
-| Recover from the cloud | Update & security > Recovery | Reinstall the operating system on Surface Hub to a manufacturer build from the cloud. |
-| Save BitLocker key | Update & security > Recovery | Backup your Surface Hub's BitLocker key to a USB drive. |
-| Collect logs | Update & security > Recovery | Save logs to a USB drive to send to Microsoft later. |
-
-## Related topics
-
-[Manage Surface Hub settings](manage-surface-hub-settings.md)
-
-[Remote Surface Hub management](remote-surface-hub-management.md)
-
-[Microsoft Surface Hub administrator's guide](surface-hub-administrators-guide.md)
diff --git a/devices/surface-hub/manage-settings-with-mdm-for-surface-hub.md b/devices/surface-hub/manage-settings-with-mdm-for-surface-hub.md
deleted file mode 100644
index 3762de36a4..0000000000
--- a/devices/surface-hub/manage-settings-with-mdm-for-surface-hub.md
+++ /dev/null
@@ -1,280 +0,0 @@
----
-title: Manage settings with an MDM provider (Surface Hub)
-description: Microsoft Surface Hub provides an enterprise management solution to help IT administrators manage policies and business applications on these devices using a mobile device management (MDM) solution.
-ms.assetid: 18EB8464-6E22-479D-B0C3-21C4ADD168FE
-ms.reviewer:
-manager: laurawi
-keywords: mobile device management, MDM, manage policies
-ms.prod: surface-hub
-ms.sitesec: library
-author: dansimp
-ms.author: dansimp
-ms.topic: article
-ms.date: 03/07/2018
-ms.localizationpriority: medium
----
-
-# Manage settings with an MDM provider (Surface Hub)
-
-Surface Hub and other Windows 10 devices allow IT administrators to manage settings and policies using a mobile device management (MDM) provider. A built-in management component communicates with the management server, so there is no need to install additional clients on the device. For more information, see [Windows 10 mobile device management](https://msdn.microsoft.com/library/windows/hardware/dn914769.aspx).
-
-Surface Hub has been validated with Microsoft's first-party MDM providers:
-- Microsoft Intune standalone
-- On-premises MDM with Microsoft Endpoint Configuration Manager
-
-You can also manage Surface Hubs using any third-party MDM provider that can communicate with Windows 10 using the MDM protocol.
-
-## Enroll a Surface Hub into MDM
-You can enroll your Surface Hubs using bulk, manual, or automatic enrollment.
-
-### Bulk enrollment
-**To configure bulk enrollment**
-- Surface Hub supports the [Provisioning CSP](https://msdn.microsoft.com/library/windows/hardware/mt203665.aspx) for bulk enrollment into MDM. For more information, see [Windows 10 bulk enrollment](https://msdn.microsoft.com/library/windows/hardware/mt613115.aspx).
---OR--
-- If you have an on-premises Microsoft Endpoint Configuration Manager infrastructure, see [How to bulk enroll devices with On-premises Mobile Device Management in Microsoft Endpoint Configuration Manager](https://docs.microsoft.com/configmgr/mdm/deploy-use/bulk-enroll-devices-on-premises-mdm).
-
-### Manual enrollment
-**To configure manual enrollment**
-1. On your Surface Hub, open **Settings**.
-2. Type the device admin credentials when prompted.
-3. Select **This device**, and navigate to **Device management**.
-4. Under **Device management**, select **+ Device management**.
-5. Follow the instructions in the dialog to connect to your MDM provider.
-
-### Automatic enrollment via Azure Active Directory join
-
-Surface Hub now supports the ability to automatically enroll in Intune by joining the device to Azure Active Directory.
-
-First step is to set up Automatic MDM enrollment. See [Enable Windows 10 automatic enrollment](https://docs.microsoft.com/intune/windows-enroll#enable-windows-10-automatic-enrollment).
-
-Then, when devices are setup during First-run, pick the option to join to Azure Active Directory, see [Set up admins for this device page](https://docs.microsoft.com/surface-hub/first-run-program-surface-hub#set-up-admins-for-this-device-page)
-
-## Manage Surface Hub settings with MDM
-
-You can use MDM to manage some [Surface Hub CSP settings](#supported-surface-hub-csp-settings), and some [Windows 10 settings](#supported-windows-10-settings). Depending on the MDM provider that you use, you may set these settings using a built-in user interface, or by deploying custom SyncML. Microsoft Intune and Microsoft Endpoint Configuration Manager provide built-in experiences to help create policy templates for Surface Hub. Refer to documentation from your MDM provider to learn how to create and deploy SyncML.
-
-### Supported Surface Hub CSP settings
-
-You can configure the Surface Hub settings in the following table using MDM. The table identifies if the setting is supported with Microsoft Intune, Microsoft Endpoint Configuration Manager, or SyncML.
-
-For more information, see [SurfaceHub configuration service provider](https://msdn.microsoft.com/library/windows/hardware/mt608323).
-
-
-| Setting | Node in the SurfaceHub CSP | Supported with Intune? | Supported with Configuration Manager? | Supported with SyncML\*? |
-|----------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------|-------------------------------------------------|-----------------------------|
-| Maintenance hours | MaintenanceHoursSimple/Hours/StartTime MaintenanceHoursSimple/Hours/Duration | Yes | Yes | Yes |
-| Automatically turn on the screen using motion sensors | InBoxApps/Welcome/AutoWakeScreen | Yes | Yes | Yes |
-| Require a pin for wireless projection | InBoxApps/WirelessProjection/PINRequired | Yes | Yes | Yes |
-| Enable wireless projection | InBoxApps/WirelessProjection/Enabled | Yes | Yes. [Use a custom setting.](#example-manage-surface-hub-settings-with-microsoft-endpoint-configuration-manager) | Yes |
-| Miracast channel to use for wireless projection | InBoxApps/WirelessProjection/Channel | Yes | Yes. [Use a custom setting.](#example-manage-surface-hub-settings-with-microsoft-endpoint-configuration-manager) | Yes |
-| Connect to your Operations Management Suite workspace | MOMAgent/WorkspaceID MOMAgent/WorkspaceKey | Yes | Yes. [Use a custom setting.](#example-manage-surface-hub-settings-with-microsoft-endpoint-configuration-manager) | Yes |
-| Welcome screen background image | InBoxApps/Welcome/CurrentBackgroundPath | Yes | Yes. [Use a custom setting.](#example-manage-surface-hub-settings-with-microsoft-endpoint-configuration-manager) | Yes |
-| Meeting information displayed on the welcome screen | InBoxApps/Welcome/MeetingInfoOption | Yes | Yes. [Use a custom setting.](#example-manage-surface-hub-settings-with-microsoft-endpoint-configuration-manager | Yes |
-| Friendly name for wireless projection | Properties/FriendlyName | Yes [Use a custom policy.](#example-manage-surface-hub-settings-with-microsoft-intune) | Yes. [Use a custom setting.](#example-manage-surface-hub-settings-with-microsoft-endpoint-configuration-manager) | Yes |
-| Device account, including password rotation | DeviceAccount/*``* See [SurfaceHub CSP](https://msdn.microsoft.com/library/windows/hardware/mt608323.aspx). | No | No | Yes |
-| Specify Skype domain | InBoxApps/SkypeForBusiness/DomainName | Yes | Yes. [Use a custom setting.](#example-manage-surface-hub-settings-with-microsoft-endpoint-configuration-manager) | Yes |
-| Auto launch Connect App when projection is initiated | InBoxApps/Connect/AutoLaunch | Yes | Yes. [Use a custom setting.](#example-manage-surface-hub-settings-with-microsoft-endpoint-configuration-manager) | Yes |
-| Set default volume | Properties/DefaultVolume | Yes | Yes. [Use a custom setting.](#example-manage-surface-hub-settings-with-microsoft-endpoint-configuration-manager) | Yes |
-| Set screen timeout | Properties/ScreenTimeout | Yes | Yes. [Use a custom setting.](#example-manage-surface-hub-settings-with-microsoft-endpoint-configuration-manager) | Yes |
-| Set session timeout | Properties/SessionTimeout | Yes | Yes. [Use a custom setting.](#example-manage-surface-hub-settings-with-microsoft-endpoint-configuration-manager) | Yes |
-| Set sleep timeout | Properties/SleepTimeout | Yes | Yes. [Use a custom setting.](#example-manage-surface-hub-settings-with-microsoft-endpoint-configuration-manager) | Yes |
-| Allow session to resume after screen is idle | Properties/AllowSessionResume | Yes | Yes. [Use a custom setting.](#example-manage-surface-hub-settings-with-microsoft-endpoint-configuration-manager) | Yes |
-| Allow device account to be used for proxy authentication | Properties/AllowAutoProxyAuth | Yes | Yes. [Use a custom setting.](#example-manage-surface-hub-settings-with-microsoft-endpoint-configuration-manager) | Yes |
-| Disable auto-populating the sign-in dialog with invitees from scheduled meetings | Properties/DisableSignInSuggestions | Yes | Yes. [Use a custom setting.](#example-manage-surface-hub-settings-with-microsoft-endpoint-configuration-manager) | Yes |
-| Disable "My meetings and files" feature in Start menu | Properties/DoNotShowMyMeetingsAndFiles | Yes | Yes. [Use a custom setting.](#example-manage-surface-hub-settings-with-microsoft-endpoint-configuration-manager) | Yes |
-| Set the LanProfile for 802.1x Wired Auth | Dot3/LanProfile | Yes [Use a custom policy.](#example-manage-surface-hub-settings-with-microsoft-intune) | Yes. [Use a custom setting.](#example-manage-surface-hub-settings-with-microsoft-endpoint-configuration-manager) | Yes |
-| Set the EapUserData for 802.1x Wired Auth | Dot3/EapUserData | Yes [Use a custom policy.](#example-manage-surface-hub-settings-with-microsoft-intune) | Yes. [Use a custom setting.](#example-manage-surface-hub-settings-with-microsoft-endpoint-configuration-manager) | Yes |
-
-\*Settings supported with SyncML can also be configured in a Windows Configuration Designer provisioning package.
-
-### Supported Windows 10 settings
-
-In addition to Surface Hub-specific settings, there are numerous settings common to all Windows 10 devices. These settings are defined in the [Configuration service provider reference](https://docs.microsoft.com/windows/client-management/mdm/configuration-service-provider-reference).
-
-The following tables include info on Windows 10 settings that have been validated with Surface Hub. There is a table with settings for these areas: security, browser, Windows Updates, Windows Defender, remote reboot, certificates, and logs. Each table identifies if the setting is supported with Microsoft Intune, Microsoft Endpoint Configuration Manager, or SyncML.
-
-#### Security settings
-
-| Setting | Details | CSP reference | Supported with Intune? | Supported with Configuration Manager? | Supported with SyncML\*? |
-|--------------------|------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------|-------------------------------------------------|-----------------------------|
-| Allow Bluetooth | Keep this enabled to support Bluetooth peripherals. | [Connectivity/AllowBluetooth](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx#Connectivity_AllowBluetooth) | Yes. | Yes. [Use a custom setting.](#example-manage-surface-hub-settings-with-microsoft-endpoint-configuration-manager) | Yes |
-| Bluetooth policies | Use to set the Bluetooth device name, and block advertising, discovery, and automatic pairing. | Bluetooth/*``* See [Policy CSP](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx) | Yes. | Yes. [Use a custom setting.](#example-manage-surface-hub-settings-with-microsoft-endpoint-configuration-manager) | Yes |
-| Allow camera | Keep this enabled for Skype for Business. | [Camera/AllowCamera](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx#Camera_AllowCamera) | Yes. | Yes. [Use a custom setting.](#example-manage-surface-hub-settings-with-microsoft-endpoint-configuration-manager) | Yes |
-| Allow location | Keep this enabled to support apps such as Maps. | [System/AllowLocation](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx#System_AllowLocation) | Yes. . | Yes. [Use a custom setting.](#example-manage-surface-hub-settings-with-microsoft-endpoint-configuration-manager) | Yes |
-| Allow telemetry | Keep this enabled to help Microsoft improve Surface Hub. | [System/AllowTelemetry](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx#System_AllowTelemetry) | Yes. | Yes. [Use a custom setting.](#example-manage-surface-hub-settings-with-microsoft-endpoint-configuration-manager) | Yes |
-| Allow USB Drives | Keep this enabled to support USB drives on Surface Hub | [System/AllowStorageCard](https://msdn.microsoft.com/windows/hardware/commercialize/customize/mdm/policy-configuration-service-provider#system-allowstoragecard) | Yes [Use a custom policy.](#example-manage-surface-hub-settings-with-microsoft-intune) | Yes. [Use a custom setting.](#example-manage-surface-hub-settings-with-microsoft-endpoint-configuration-manager) | Yes |
-
-\*Settings supported with SyncML can also be configured in a Windows Configuration Designer provisioning package.
-
-#### Browser settings
-
-| Setting | Details | CSP reference | Supported with Intune? | Supported with Configuration Manager? | Supported with SyncML\*? |
-|-----------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------|-------------------------------------------------|-----------------------------|
-| Homepages | Use to configure the default homepages in Microsoft Edge. | [Browser/Homepages](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx#Browser_Homepages) | Yes [Use a custom policy.](#example-manage-surface-hub-settings-with-microsoft-intune) | Yes. [Use a custom setting.](#example-manage-surface-hub-settings-with-microsoft-endpoint-configuration-manager) | Yes |
-| Allow cookies | Surface Hub automatically deletes cookies at the end of a session. Use this to block cookies within a session. | [Browser/AllowCookies](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx#Browser_AllowCookies) | Yes [Use a custom policy.](#example-manage-surface-hub-settings-with-microsoft-intune) | Yes. [Use a custom setting.](#example-manage-surface-hub-settings-with-microsoft-endpoint-configuration-manager) | Yes |
-| Allow developer tools | Use to stop users from using F12 Developer Tools. | [Browser/AllowDeveloperTools](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx#Browser_AllowDeveloperTools) | Yes [Use a custom policy.](#example-manage-surface-hub-settings-with-microsoft-intune) | Yes. [Use a custom setting.](#example-manage-surface-hub-settings-with-microsoft-endpoint-configuration-manager) | Yes |
-| Allow Do Not Track | Use to enable Do Not Track headers. | [Browser/AllowDoNotTrack](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx#Browser_AllowDoNotTrack) | Yes [Use a custom policy.](#example-manage-surface-hub-settings-with-microsoft-intune) | Yes. [Use a custom setting.](#example-manage-surface-hub-settings-with-microsoft-endpoint-configuration-manager) | Yes |
-| Allow pop-ups | Use to block pop-up browser windows. | [Browser/AllowPopups](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx#Browser_AllowPopups) | Yes [Use a custom policy.](#example-manage-surface-hub-settings-with-microsoft-intune) | Yes. [Use a custom setting.](#example-manage-surface-hub-settings-with-microsoft-endpoint-configuration-manager) | Yes |
-| Allow search suggestions | Use to block search suggestions in the address bar. | [Browser/AllowSearchSuggestionsinAddressBar](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx#Browser_AllowSearchSuggestionsinAddressBar) | Yes [Use a custom policy.](#example-manage-surface-hub-settings-with-microsoft-intune) | Yes. [Use a custom setting.](#example-manage-surface-hub-settings-with-microsoft-endpoint-configuration-manager) | Yes |
-| Allow Windows Defender SmartScreen | Keep this enabled to turn on Windows Defender SmartScreen. | [Browser/AllowSmartScreen](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx#Browser_AllowSmartScreen) | Yes [Use a custom policy.](#example-manage-surface-hub-settings-with-microsoft-intune) | Yes. [Use a custom setting.](#example-manage-surface-hub-settings-with-microsoft-endpoint-configuration-manager) | Yes |
-| Prevent ignoring Windows Defender SmartScreen warnings for websites | For extra security, use to stop users from ignoring Windows Defender SmartScreen warnings and block them from accessing potentially malicious websites. | [Browser/PreventSmartScreenPromptOverride](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx#Browser_PreventSmartScreenPromptOverride) | Yes [Use a custom policy.](#example-manage-surface-hub-settings-with-microsoft-intune) | Yes. [Use a custom setting.](#example-manage-surface-hub-settings-with-microsoft-endpoint-configuration-manager) | Yes |
-| Prevent ignoring Windows Defender SmartScreen warnings for files | For extra security, use to stop users from ignoring Windows Defender SmartScreen warnings and block them from downloading unverified files from Microsoft Edge. | [Browser/PreventSmartScreenPromptOverrideForFiles](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx#Browser_PreventSmartScreenPromptOverrideForFiles) | Yes [Use a custom policy.](#example-manage-surface-hub-settings-with-microsoft-intune) | Yes. [Use a custom setting.](#example-manage-surface-hub-settings-with-microsoft-endpoint-configuration-manager) | Yes |
-
-\*Settings supported with SyncML can also be configured in a Windows Configuration Designer provisioning package.
-
-#### Windows Update settings
-
-| Setting | Details | CSP reference | Supported with Intune? | Supported with Configuration Manager? | Supported with SyncML\*? |
-|---------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------|-------------------------------------------------|-----------------------------|
-| Use Current Branch or Current Branch for Business | Use to configure Windows Update for Business – see [Windows updates](manage-windows-updates-for-surface-hub.md). | [Update/BranchReadinessLevel](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx#Update_BranchReadinessLevel) | Yes [Use a custom policy.](#example-manage-surface-hub-settings-with-microsoft-intune) | Yes. [Use a custom setting.](#example-manage-surface-hub-settings-with-microsoft-endpoint-configuration-manager) | Yes |
-| Defer feature updates | See above. | [Update/ DeferFeatureUpdatesPeriodInDays](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx#Update_DeferFeatureUpdatesPeriodInDays) | Yes [Use a custom policy.](#example-manage-surface-hub-settings-with-microsoft-intune) | Yes. [Use a custom setting.](#example-manage-surface-hub-settings-with-microsoft-endpoint-configuration-manager) | Yes |
-| Defer quality updates | See above. | [Update/DeferQualityUpdatesPeriodInDays](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx#Update_DeferQualityUpdatesPeriodInDays) | Yes [Use a custom policy.](#example-manage-surface-hub-settings-with-microsoft-intune) | Yes. [Use a custom setting.](#example-manage-surface-hub-settings-with-microsoft-endpoint-configuration-manager) | Yes |
-| Pause feature updates | See above. | [Update/PauseFeatureUpdates](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx#Update_PauseFeatureUpdates) | Yes [Use a custom policy.](#example-manage-surface-hub-settings-with-microsoft-intune) | Yes. [Use a custom setting.](#example-manage-surface-hub-settings-with-microsoft-endpoint-configuration-manager) | Yes |
-| Pause quality updates | See above. | [Update/PauseQualityUpdates](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx#Update_PauseQualityUpdates) | Yes [Use a custom policy.](#example-manage-surface-hub-settings-with-microsoft-intune) | Yes. [Use a custom setting.](#example-manage-surface-hub-settings-with-microsoft-endpoint-configuration-manager) | Yes |
-| Configure device to use WSUS | Use to connect your Surface Hub to WSUS instead of Windows Update – see [Windows updates](manage-windows-updates-for-surface-hub.md). | [Update/UpdateServiceUrl](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx#Update_UpdateServiceUrl) | Yes [Use a custom policy.](#example-manage-surface-hub-settings-with-microsoft-intune) | Yes. [Use a custom setting.](#example-manage-surface-hub-settings-with-microsoft-endpoint-configuration-manager) | Yes |
-| Delivery optimization | Use peer-to-peer content sharing to reduce bandwidth issues during updates. See [Configure Delivery Optimization for Windows 10](https://technet.microsoft.com/itpro/windows/manage/waas-delivery-optimization) for details. | DeliveryOptimization/*``* See [Policy CSP](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx) | Yes [Use a custom policy.](#example-manage-surface-hub-settings-with-microsoft-intune) | Yes. [Use a custom setting.](#example-manage-surface-hub-settings-with-microsoft-endpoint-configuration-manager) | Yes |
-
-\*Settings supported with SyncML can also be configured in a Windows Configuration Designer provisioning package.
-
-#### Windows Defender settings
-
-| Setting | Details | CSP reference | Supported with Intune? | Supported with Configuration Manager? | Supported with SyncML\*? |
-|-------------------|----------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------|-------------------------------------------------|-----------------------------|
-| Defender policies | Use to configure various Defender settings, including a scheduled scan time. | Defender/*``* See [Policy CSP](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx) | Yes [Use a custom policy.](#example-manage-surface-hub-settings-with-microsoft-intune) | Yes. [Use a custom setting.](#example-manage-surface-hub-settings-with-microsoft-endpoint-configuration-manager) | Yes |
-| Defender status | Use to initiate a Defender scan, force a Security intelligence update, query any threats detected. | [Defender CSP](https://msdn.microsoft.com/library/windows/hardware/mt187856.aspx) | Yes | Yes | Yes |
-
-\*Settings supported with SyncML can also be configured in a Windows Configuration Designer provisioning package.
-
-#### Remote reboot
-
-| Setting | Details | CSP reference | Supported with Intune? | Supported with Configuration Manager? | Supported with SyncML\*? |
-|------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------|-------------------------------------------------|-----------------------------|
-| Reboot the device immediately | Use in conjunction with OMS to minimize support costs – see [Monitor your Microsoft Surface Hub](monitor-surface-hub.md). | ./Vendor/MSFT/Reboot/RebootNow See [Reboot CSP](https://msdn.microsoft.com/library/windows/hardware/mt720802.aspx) | Yes | No | Yes |
-| Reboot the device at a scheduled date and time | See above. | ./Vendor/MSFT/Reboot/Schedule/Single See [Reboot CSP](https://msdn.microsoft.com/library/windows/hardware/mt720802.aspx) | Yes [Use a custom policy.](#example-manage-surface-hub-settings-with-microsoft-intune) | Yes. [Use a custom setting.](#example-manage-surface-hub-settings-with-microsoft-endpoint-configuration-manager) | Yes |
-| Reboot the device daily at a scheduled date and time | See above. | ./Vendor/MSFT/Reboot/Schedule/DailyRecurrent See [Reboot CSP](https://msdn.microsoft.com/library/windows/hardware/mt720802.aspx) | Yes [Use a custom policy.](#example-manage-surface-hub-settings-with-microsoft-intune) | Yes. [Use a custom setting.](#example-manage-surface-hub-settings-with-microsoft-endpoint-configuration-manager) | Yes |
-
-\*Settings supported with SyncML can also be configured in a Windows Configuration Designer provisioning package.
-
-#### Install certificates
-
-| Setting | Details | CSP reference | Supported with Intune? | Supported with Configuration Manager? | Supported with SyncML\*? |
-|---------------------------------|--------------------------------------------------------------|----------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------|
-| Install trusted CA certificates | Use to deploy trusted root and intermediate CA certificates. | [RootCATrustedCertificates CSP](https://msdn.microsoft.com/library/windows/hardware/dn904970.aspx) | Yes. See [Configure Intune certificate profiles](https://docs.microsoft.com/intune/deploy-use/configure-intune-certificate-profiles). | Yes. See [How to create certificate profiles in Microsoft Endpoint Configuration Manager](https://docs.microsoft.com/configmgr/protect/deploy-use/create-certificate-profiles). | Yes |
-
-
-\*Settings supported with SyncML can also be configured in a Windows Configuration Designer provisioning package.
-
-#### Collect logs
-
-| Setting | Details | CSP reference | Supported with Intune? | Supported with Configuration Manager? | Supported with SyncML\*? |
-|------------------|----------------------------------------------------|----------------------------------------------------------------------------------------|---------------------------|------------------------------------------|-----------------------------|
-| Collect ETW logs | Use to remotely collect ETW logs from Surface Hub. | [DiagnosticLog CSP](https://msdn.microsoft.com/library/windows/hardware/mt219118.aspx) | No | No | Yes |
-
-
-\*Settings supported with SyncML can also be configured in a Windows Configuration Designer provisioning package.
-
-#### Set network quality of service (QoS) policy
-
-| Setting | Details | CSP reference | Supported with Intune? | Supported with Configuration Manager? | Supported with SyncML\*? |
-|------------------------|--------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------|--------------------------------------------------|-------------------------------------------------|-----------------------------|
-| Set Network QoS Policy | Use to set a QoS policy to perform a set of actions on network traffic. This is useful for prioritizing Skype network packets. | [NetworkQoSPolicy CSP](https://msdn.microsoft.com/windows/hardware/commercialize/customize/mdm/networkqospolicy-csp) | Yes [Use a custom policy.](#example-manage-surface-hub-settings-with-microsoft-intune) | Yes. [Use a custom setting.](#example-manage-surface-hub-settings-with-microsoft-endpoint-configuration-manager) | Yes |
-
-\*Settings supported with SyncML can also be configured in a Windows Configuration Designer provisioning package.
-
-#### Set network proxy
-
-| Setting | Details | CSP reference | Supported with Intune? | Supported with Configuration Manager? | Supported with SyncML\*? |
-|-------------------|---------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------|--------------------------------------------------|-------------------------------------------------|-----------------------------|
-| Set Network proxy | Use to configure a proxy server for ethernet and Wi-Fi connections. | [NetworkProxy CSP](https://msdn.microsoft.com/windows/hardware/commercialize/customize/mdm/networkproxy-csp) | Yes [Use a custom policy.](#example-manage-surface-hub-settings-with-microsoft-intune) | Yes. [Use a custom setting.](#example-manage-surface-hub-settings-with-microsoft-endpoint-configuration-manager) | Yes |
-
-\*Settings supported with SyncML can also be configured in a Windows Configuration Designer provisioning package.
-
-#### Configure Start menu
-
-| Setting | Details | CSP reference | Supported with Intune? | Supported with Configuration Manager? | Supported with SyncML\*? |
-|----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------|-------------------------------------------------|-----------------------------|
-| Configure Start menu | Use to configure which apps are displayed on the Start menu. For more information, see [Configure Surface Hub Start menu](surface-hub-start-menu.md) | [Policy CSP: Start/StartLayout](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-start#start-startlayout) | Yes [Use a custom policy.](#example-manage-surface-hub-settings-with-microsoft-intune) | Yes. [Use a custom setting.](#example-manage-surface-hub-settings-with-microsoft-endpoint-configuration-manager) | Yes |
-
-\*Settings supported with SyncML can also be configured in a Windows Configuration Designer provisioning package.
-
-### Generate OMA URIs for settings
-You need to use a setting's OMA URI to create a custom policy in Intune, or a custom setting in Microsoft Endpoint Configuration Manager.
-
-**To generate the OMA URI for any setting in the CSP documentation**
-1. In the CSP documentation, identify the root node of the CSP. Generally, this looks like `./Vendor/MSFT/`
-*For example, the root node of the [SurfaceHub CSP](https://msdn.microsoft.com/library/windows/hardware/mt608323.aspx) is `./Vendor/MSFT/SurfaceHub`.*
-2. Identify the node path for the setting you want to use.
-*For example, the node path for the setting to enable wireless projection is `InBoxApps/WirelessProjection/Enabled`.*
-3. Append the node path to the root node to generate the OMA URI.
-*For example, the OMA URI for the setting to enable wireless projection is `./Vendor/MSFT/SurfaceHub/InBoxApps/WirelessProjection/Enabled`.*
-
-The data type is also stated in the CSP documentation. The most common data types are:
-- char (String)
-- int (Integer)
-- bool (Boolean)
-
-
-## Example: Manage Surface Hub settings with Microsoft Intune
-
-You can use Microsoft Intune to manage Surface Hub settings. For custom settings, follow the instructions in [How to configure custom device settings in Microsoft Intune](https://docs.microsoft.com/intune/custom-settings-configure). For **Platform**, select **Windows 10 and later**, and in **Profile type**, select **Device restrictions (Windows 10 Team)**.
-
-
-
-## Example: Manage Surface Hub settings with Microsoft Endpoint Configuration Manager
-Configuration Manager supports managing modern devices that do not require the Configuration Manager client to manage them, including Surface Hub. If you already use Configuration Manager to manage other devices in your organization, you can continue to use the Configuration Manager console as your single location for managing Surface Hubs.
-
-> [!NOTE]
-> These instructions are based on the current branch of Configuration Manager.
-
-**To create a configuration item for Surface Hub settings**
-
-1. On the **Assets and Compliance** workspace of the Configuration Manager console, click **Overview** > **Compliance Settings** > **Configuration Items**.
-2. On the **Home** tab, in the **Create** group, click **Create Configuration Item**.
-3. On the **General** page of the Create Configuration Item Wizard, specify a name and optional description for the configuration item.
-4. Under **Settings for devices managed without the Configuration Manager client**, select **Windows 8.1 and Windows 10**, and then click **Next**.
-
- 
-5. On the **Supported Platforms** page, expand **Windows 10** and select **All Windows 10 Team and higher**. Unselect the other Windows platforms, and then click **Next**.
-
- 
-7. On the **Device Settings** page, under **Device settings groups**, select **Windows 10 Team**.
-
-
-8. On the **Windows 10 Team** page, configure the settings you require.
-
- 
-9. You'll need to create custom settings to manage settings that are not available in the Windows 10 Team page. On the **Device Settings** page, select the check box **Configure additional settings that are not in the default setting groups**.
-
- 
-10. On the **Additional Settings** page, click **Add**.
-11. In the **Browse Settings** dialog, click **Create Setting**.
-12. In the **Create Setting** dialog, under the **General** tab, specify a name and optional description for the custom setting.
-13. Under **Setting type**, select **OMA URI**.
-14. Complete the form to create a new setting, and then click **OK**.
-
- 
-15. On the **Browse Settings** dialog, under **Available settings**, select the new setting you created, and then click **Select**.
-16. On the **Create Rule** dialog, complete the form to specify a rule for the setting, and then click **OK**.
-17. Repeat steps 9 to 15 for each custom setting you want to add to the configuration item.
-18. When you're done, on the **Browse Settings** dialog, click **Close**.
-19. Complete the wizard. You can view the new configuration item in the **Configuration Items** node of the **Assets and Compliance** workspace.
-
-For more information, see [Create configuration items for Windows 8.1 and Windows 10 devices managed without the Microsoft Endpoint Configuration Manager client](https://docs.microsoft.com/configmgr/compliance/deploy-use/create-configuration-items-for-windows-8.1-and-windows-10-devices-managed-without-the-client).
-
-## Related topics
-
-[Manage Microsoft Surface Hub](manage-surface-hub.md)
-
-
-
-
-
-
-
-
-
-
-
diff --git a/devices/surface-hub/manage-surface-hub-settings.md b/devices/surface-hub/manage-surface-hub-settings.md
deleted file mode 100644
index b217ccee4d..0000000000
--- a/devices/surface-hub/manage-surface-hub-settings.md
+++ /dev/null
@@ -1,27 +0,0 @@
----
-title: Manage Surface Hub settings
-description: This section lists topics for managing Surface Hub settings.
-keywords: Surface Hub accessibility settings, device account, device reset, windows updates, wireless network management
-ms.prod: surface-hub
-ms.sitesec: library
-author: dansimp
-ms.author: dansimp
-ms.topic: article
-ms.date: 07/27/2017
-ms.reviewer:
-manager: laurawi
-ms.localizationpriority: medium
----
-
-# Manage Surface Hub settings
-
-## In this section
-
-|Topic | Description|
-| ------ | --------------- |
-| [Local management for Surface Hub settings](local-management-surface-hub-settings.md) | Learn about Surface Hub settings. |
-| [Accessibility](accessibility-surface-hub.md) | Accessibility settings for the Surface Hub can be changed by using the Settings app. You'll find them under Ease of Access. Your Surface Hub has the same accessibility options as Windows 10.|
-| [Change the Surface Hub device account](change-surface-hub-device-account.md) | You can change the device account in Settings to either add an account if one was not already provisioned, or to change any properties of an account that was already provisioned.|
-| [Device reset](device-reset-surface-hub.md) | You may need to reset your Surface Hub.|
-| [Use fully qualified domain name with Surface Hub](use-fully-qualified-domain-name-surface-hub.md) | Options to configure domain name with Surface Hub. |
-| [Wireless network management](wireless-network-management-for-surface-hub.md) | Surface Hub offers two options for network connectivity to your corporate network and Internet: wireless, and wired. While both provide network access, we recommend you use a wired connection. |
diff --git a/devices/surface-hub/manage-surface-hub.md b/devices/surface-hub/manage-surface-hub.md
deleted file mode 100644
index 10240a192f..0000000000
--- a/devices/surface-hub/manage-surface-hub.md
+++ /dev/null
@@ -1,50 +0,0 @@
----
-title: Manage Microsoft Surface Hub
-description: How to manage your Surface Hub after finishing the first-run program.
-ms.assetid: FDB6182C-1211-4A92-A930-6C106BCD5DC1
-ms.reviewer:
-manager: laurawi
-keywords: manage Surface Hub
-ms.prod: surface-hub
-ms.sitesec: library
-author: dansimp
-ms.author: dansimp
-ms.topic: article
-ms.date: 01/17/2018
-ms.localizationpriority: medium
----
-
-# Manage Microsoft Surface Hub
-
-After initial setup of Microsoft Surface Hub, the device’s settings and configuration can be modified or changed in a couple ways:
-
-- **Local management** - Every Surface Hub can be configured locally using the **Settings** app on the device. To prevent unauthorized users from changing settings, the Settings app requires admin credentials to open the app. For more information, see [Local management for Surface Hub settings](local-management-surface-hub-settings.md).
-- **Remote management** - Surface Hub allow IT admins to manage settings and policies using a mobile device management (MDM) provider, such as Microsoft Intune, Microsoft Endpoint Configuration Manager, and other third-party providers. Additionally, admins can monitor Surface Hubs using Microsoft Operations Management Suite (OMS). For more information, see [Manage settings with an MDM provider](manage-settings-with-mdm-for-surface-hub.md), and [Monitor your Microsoft Surface Hub](monitor-surface-hub.md).
-
-> [!NOTE]
-> These management methods are not mutually exclusive. Devices can be both locally and remotely managed if you choose. However, MDM policies and settings will overwrite any local changes when the Surface Hub syncs with the management server.
-
-## In this section
-
-Learn about managing and updating Surface Hub.
-
-| Topic | Description |
-| ----- | ----------- |
-| [Remote Surface Hub management](remote-surface-hub-management.md) |Topics related to managing your Surface Hub remotely. Include install apps, managing settings with MDM and monitoring with Operations Management Suite. |
-| [Manage Surface Hub settings](manage-surface-hub-settings.md) |Topics related to managing Surface Hub settings: accessibility, device account, device reset, fully qualified domain name, Windows Update settings, and wireless network |
-| [Install apps on your Surface Hub]( https://technet.microsoft.com/itpro/surface-hub/install-apps-on-surface-hub) | Admins can install apps can from either the Microsoft Store or the Microsoft Store for Business.|
-[Configure Surface Hub Start menu](surface-hub-start-menu.md) | Use MDM to customize the Start menu for Surface Hub.
-| [Set up and use Microsoft Whiteboard](whiteboard-collaboration.md) | Microsoft Whiteboard’s latest update includes the capability for two Surface Hubs to collaborate in real time on the same board. |
-| [End a meeting with End session](https://technet.microsoft.com/itpro/surface-hub/i-am-done-finishing-your-surface-hub-meeting) | At the end of a meeting, users can tap **End session** to clean up any sensitive data and prepare the device for the next meeting.|
-| [Sign in to Surface Hub with Microsoft Authenticator](surface-hub-authenticator-app.md) | You can sign in to a Surface Hub without a password using the Microsoft Authenticator app, available on Android and iOS. |
-| [Save your BitLocker key](https://technet.microsoft.com/itpro/surface-hub/save-bitlocker-key-surface-hub) | Every Surface Hub is automatically set up with BitLocker drive encryption software. Microsoft strongly recommends that you make sure you back up your BitLocker recovery keys.|
-| [Connect other devices and display with Surface Hub](https://technet.microsoft.com/itpro/surface-hub/connect-and-display-with-surface-hub) | You can connect other device to your Surface Hub to display content.|
-| [Miracast on existing wireless network or LAN](miracast-over-infrastructure.md) | You can use Miracast on your wireless network or LAN to connect to Surface Hub. |
- [Enable 802.1x wired authentication](enable-8021x-wired-authentication.md) | 802.1x Wired Authentication MDM policies have been enabled on Surface Hub devices.
-| [Using a room control system](https://technet.microsoft.com/itpro/surface-hub/use-room-control-system-with-surface-hub) | Room control systems can be used with your Microsoft Surface Hub.|
-[Using the Surface Hub Recovery Tool](surface-hub-recovery-tool.md) | Use the Surface Hub Recovery Tool to re-image the Surface Hub SSD.
-[Surface Hub SSD replacement](surface-hub-ssd-replacement.md) | Learn how to remove and replace the solid state drive in your Surface Hub.
-
-## Related topics
-
-- [View Power BI presentation mode on Surface Hub & Windows 10](https://powerbi.microsoft.com/documentation/powerbi-mobile-win10-app-presentation-mode/)
diff --git a/devices/surface-hub/manage-windows-updates-for-surface-hub.md b/devices/surface-hub/manage-windows-updates-for-surface-hub.md
deleted file mode 100644
index 9dee3e2a4b..0000000000
--- a/devices/surface-hub/manage-windows-updates-for-surface-hub.md
+++ /dev/null
@@ -1,145 +0,0 @@
----
-title: Manage Windows updates on Surface Hub
-description: You can manage Windows updates on your Microsoft Surface Hub or Surface Hub 2S by setting the maintenance window, deferring updates, or using Windows Server Update Services (WSUS).
-ms.assetid: A737BD50-2D36-4DE5-A604-55053D549045
-ms.reviewer:
-manager: laurawi
-keywords: manage Windows updates, Surface Hub, Windows Server Update Services, WSUS
-ms.prod: surface-hub
-ms.sitesec: library
-author: dansimp
-ms.author: dansimp
-ms.topic: article
-ms.localizationpriority: medium
----
-
-# Manage Windows updates on Surface Hub
-
-New releases of the Surface Hub operating system are published through Windows Update, just like releases of Windows 10. There are a couple of ways you can manage which updates are installed on your Surface Hubs, and the timing for when updates are applied.
-- **Windows Update for Business** - New in Windows 10, Windows Update for Business is a set of features designed to provide enterprises additional control over how and when Windows Update installs releases, while reducing device management costs. Using this method, Surface Hubs are directly connected to Microsoft’s Windows Update service.
-- **Windows Server Update Services (WSUS)** - Set of services that enable IT administrators to obtain the updates that Windows Update determines are applicable to the devices in their enterprise, perform additional testing and evaluation on the updates, and select the updates they want to install. Using this method, Surface Hubs will receive updates from WSUS rather than Windows Update.
-
-You can also configure Surface Hub to receive updates from both Windows Update for Business and WSUS. See [Integrate Windows Update for Business with Windows Server Update Services](https://technet.microsoft.com/itpro/windows/manage/waas-integrate-wufb#integrate-windows-update-for-business-with-windows-server-update-services) for details.
-
-| Capabilities | Windows Update for Business | Windows Server Update Services (WSUS) |
-| ------------ | --------------------------- | ------------------------------------- |
-| Receive updates directly from Microsoft's Windows Update service, with no additional infrastructure required. | Yes | No |
-| Defer updates to provide additional time for testing and evaluation. | Yes | Yes |
-| Deploy updates to select groups of devices. | Yes | Yes |
-| Define maintenance windows for installing updates. | Yes | Yes |
-
-> [!TIP]
-> Use peer-to-peer content sharing to reduce bandwidth issues during updates. See [Optimize update delivery for Windows 10 updates](https://technet.microsoft.com/itpro/windows/manage/waas-optimize-windows-10-updates) for details.
-
-> [!NOTE]
-> Surface Hub does not currently support rolling back updates.
-
-
-## Surface Hub servicing model
-
-Surface Hub uses the Windows 10 servicing model, referred to as [Windows as a Service (WaaS)](https://docs.microsoft.com/windows/deployment/update/waas-overview). Traditionally, new features were added only in new versions of Windows that were released every few years. Each new version required lengthy and expensive processes to deploy in an organization. As a result, end users and organizations don't frequently enjoy the benefits of new innovation. The goal of Windows as a Service is to continually provide new capabilities while maintaining a high level of quality.
-
-Microsoft publishes two types of Surface Hub releases broadly on an ongoing basis:
-- **Feature updates** - Updates that install the latest new features, experiences, and capabilities. Microsoft expects to publish two new feature updates per year.
-- **Quality updates** - Updates that focus on the installation of security fixes, drivers, and other servicing updates. Microsoft expects to publish one cumulative quality update per month.
-
-In order to improve release quality and simplify deployments, all new releases that Microsoft publishes for Windows 10, including Surface Hub, will be cumulative. This means new feature updates and quality updates will contain the payloads of all previous releases (in an optimized form to reduce storage and networking requirements), and installing the release on a device will bring it completely up to date. Also, unlike earlier versions of Windows, you cannot install a subset of the contents of a Windows 10 quality update. For example, if a quality update contains fixes for three security vulnerabilities and one reliability issue, deploying the update will result in the installation of all four fixes.
-
-The Surface Hub operating system receives updates on the [Semi-Annual Channel](https://docs.microsoft.com/windows/deployment/update/waas-overview#naming-changes). Like other editions of Windows 10, the servicing lifetime is finite. You must install new feature updates on machines running these branches in order to continue receiving quality updates.
-
-For more information on Windows as a Service, see [Overview of Windows as a service](https://technet.microsoft.com/itpro/windows/manage/waas-overview).
-
-
-## Use Windows Update for Business
-Surface Hubs, like all Windows 10 devices, include **Windows Update for Business (WUfB)** to enable you to control how your devices are being updated. Windows Update for Business helps reduce device management costs, provide controls over update deployment, offer quicker access to security updates, as well as provide access to the latest innovations from Microsoft on an ongoing basis. For more information, see [Manage updates using Windows Update for Business](https://technet.microsoft.com/itpro/windows/manage/waas-manage-updates-wufb).
-
-**To set up Windows Update for Business:**
-1. [Group Surface Hub into deployment rings](#group-surface-hub-into-deployment-rings)
-2. [Configure when Surface Hub receives updates](#configure-when-surface-hub-receives-updates).
-
-> [!NOTE]
-> You can use Microsoft Intune, Microsoft Endpoint Configuration Manager, or a supported third-party MDM provider to set up WUfB. [Walkthrough: use Microsoft Intune to configure Windows Update for Business.](https://docs.microsoft.com/windows/deployment/update/waas-wufb-intune)
-
-
-### Group Surface Hub into deployment rings
-Use deployment rings to control when updates roll out to your Surface Hubs, giving you time to validate them. For example, you can update a small pool of devices first to verify quality before a broader roll-out to your organization. Depending on who manages Surface Hub in your organization, consider incorporating Surface Hub into the deployment rings that you've built for your other Windows 10 devices. For more information about deployment rings, see [Build deployment rings for Windows 10 updates](https://technet.microsoft.com/itpro/windows/manage/waas-deployment-rings-windows-10-updates).
-
-This table gives examples of deployment rings.
-
-| Deployment ring | Ring size | Servicing branch | Deferral for feature updates | Deferral for quality updates (security fixes, drivers, and other updates) | Validation step |
-| --------- | --------- | --------- | --------- | --------- | --------- |
-| Preview (e.g. non-critical or test devices) | Small | Windows Insider Preview | None. | None. | Manually test and evaluate new functionality. Pause updates if there are issues. |
-| Release (e.g. devices used by select teams) | Medium | Semi-annual channel | None. | None. | Monitor device usage and user feedback. Pause updates if there are issues. |
-| Broad deployment (e.g. most of the devices in your organization) | Large | Semi-annual channel | 120 days after release. | 7-14 days after release. | Monitor device usage and user feedback. Pause updates if there are issues. |
-| Mission critical (e.g. devices in executive boardrooms) | Small | Semi-annual channel | 180 days after release (maximum deferral for feature updates). | 30 days after release (maximum deferral for quality updates). | Monitor device usage and user feedback. |
-
-
-
-
-
-### Configure when Surface Hub receives updates
-Once you've determined deployment rings for your Surface Hubs, configure update deferral policies for each ring:
-- To defer feature updates, set an appropriate [Update/DeferFeatureUpdatesPeriodInDays](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-update#update-deferfeatureupdatesperiodindays) policy for each ring.
-- To defer quality updates, set an appropriate [Update/DeferQualityUpdatesPeriodInDays](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-update#update-deferqualityupdatesperiodindays) policy for each ring.
-
-> [!NOTE]
-> If you encounter issues during the update rollout, you can pause updates using [Update/PauseFeatureUpdates](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-update#update-pausefeatureupdates) and [Update/PauseQualityUpdates](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-update#update-pausequalityupdates).
-
-
-## Use Windows Server Update Services
-
-You can connect Surface Hub to your Windows Server Update Services (WSUS) server to manage updates. Updates will be controlled through approvals or automatic deployment rules configured in your WSUS server, so new upgrades will not be deployed until you choose to deploy them.
-
-**To manually connect a Surface Hub to a WSUS server:**
-1. Open **Settings** on your Surface Hub.
-2. Enter the device admin credentials when prompted.
-3. Navigate to **Update & security** > **Windows Update** > **Advanced options** > **Configure Windows Server Update Services (WSUS) server**.
-4. Click **Use WSUS Server to download updates** and type the URL of your WSUS server.
-
-To connect Surface Hub to a WSUS server using MDM, set an appropriate [Update/UpdateServiceUrl](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx#Update_UpdateServiceUrl) policy.
-
-**If you use a proxy server or other method to block URLs**
-
-If you use a method other than WSUS to block specific URLs and prevent updates, you will need to add the following Windows update trusted site URLs to the “allow list”:
-- `http(s)://*.update.microsoft.com`
-- `http://download.windowsupdate.com`
-- `http://windowsupdate.microsoft.com`
-
-Once the Windows 10 Team Anniversary Update is installed, you can remove these addresses to return your Surface Hub to its previous state.
-
-## Maintenance window
-
-To ensure the device is always available for use during business hours, Surface Hub performs its administrative functions during a specified maintenance window. During the maintenance window, the Surface Hub automatically installs updates through Windows Update or WSUS, and reboots the device if needed.
-
-Surface Hub follows these guidelines to apply updates:
-- Install the update during the next maintenance window. If a meeting is scheduled to start during a maintenance window, or the Surface Hub sensors detect that the device is being used, the pending update will be postponed to the following maintenance window.
-- If the next maintenance window is past the update’s prescribed grace period, the device will calculate the next available slot during business hours using the estimated install time from the update’s metadata. It will continue to postpone the update if a meeting is scheduled, or the Surface Hub sensors detect that the device is being used.
-- If the next maintenance window is **not** past the update's grace period, the Surface Hub will continue to postpone the update.
-- If a reboot is needed, the Surface Hub will automatically reboot during the next maintenance window.
-
-> [!NOTE]
-> Allow time for updates when you first setup your Surface Hub. For example, a backlog of virus definitions may be available, which should be immediately installed.
-
-A default maintenance window is set for all new Surface Hubs:
-- **Start time:** 3:00 AM
-- **Duration:** 1 hour
-
-**To manually change the maintenance window:**
-1. Open **Settings** on your Surface Hub.
-2. Navigate to **Update & security** > **Windows Update** > **Advanced options**.
-3. Under **Maintenance hours**, select **Change**.
-
-To change the maintenance window using MDM, set the **MOMAgent** node in the [SurfaceHub configuration service provider](https://msdn.microsoft.com/library/windows/hardware/mt608323.aspx). See [Manage settings with an MDM provider](manage-settings-with-mdm-for-surface-hub.md) for more details.
-
-
-## More information
-
-- [Blog post: Servicing, Flighting, and Managing updates for Surface Hub (With Intune, of course!)](https://blogs.technet.microsoft.com/y0av/2018/05/31/7-3/)
-
-
-## Related topics
-
-[Manage Microsoft Surface Hub](manage-surface-hub.md)
-
-[Microsoft Surface Hub administrator's guide](surface-hub-administrators-guide.md)
-
diff --git a/devices/surface-hub/miracast-over-infrastructure.md b/devices/surface-hub/miracast-over-infrastructure.md
deleted file mode 100644
index 5ef43af85c..0000000000
--- a/devices/surface-hub/miracast-over-infrastructure.md
+++ /dev/null
@@ -1,59 +0,0 @@
----
-title: Miracast on existing wireless network or LAN
-description: Windows 10 enables you to send a Miracast stream over a local network.
-ms.prod: surface-hub
-ms.sitesec: library
-author: dansimp
-ms.author: dansimp
-ms.topic: article
-ms.date: 04/24/2020
-ms.reviewer:
-manager: laurawi
-ms.localizationpriority: medium
----
-
-# Miracast over infrastructure
-
-In the Windows 10, version 1703, Microsoft has extended the ability to send a Miracast stream over a local network rather than over a direct wireless link. This functionality is based on the [Miracast over Infrastructure Connection Establishment Protocol (MS-MICE)](https://msdn.microsoft.com/library/mt796768.aspx).
-
-Miracast over Infrastructure offers a number of benefits:
-
-- Windows automatically detects when sending the video stream over this path is applicable.
-- Windows will only choose this route if the connection is over Ethernet or a secure Wi-Fi network.
-- Users do not have to change how they connect to a Miracast receiver. They use the same UX as for standard Miracast connections.
-- No changes to current wireless drivers or PC hardware are required.
-- It works well with older wireless hardware that is not optimized for Miracast over Wi-Fi Direct.
-- It leverages an existing connection which both reduces the time to connect and provides a very stable stream.
-
-
-## How it works
-
-Users attempt to connect to a Miracast receiver through their Wi-Fi adapter as they did previously. When the list of Miracast receivers is populated, Windows 10 will identify that the receiver is capable of supporting a connection over the infrastructure. When the user selects a Miracast receiver, Windows 10 will attempt to resolve the device's hostname via standard DNS, as well as via multicast DNS (mDNS). If the name is not resolvable via either DNS method, Windows 10 will fall back to establishing the Miracast session using the standard Wi-Fi direct connection.
-
-> [!NOTE]
-> For more information on the connection negotiation sequence, see [Miracast over Infrastructure Connection Establishment Protocol (MS-MICE)](https://msdn.microsoft.com/library/mt796768.aspx)
-
-
-
-
-## Enabling Miracast over Infrastructure
-
-If you have a Surface Hub or other Windows 10 device that has been updated to Windows 10, version 1703, then you automatically have this new feature. To take advantage of it in your environment, you need to ensure the following is true within your deployment:
-
-- The Surface Hub or device (Windows PC or phone) needs to be running Windows 10, version 1703.
-- Open TCP port: **7250**.
-- A Surface Hub or Windows PC can act as a Miracast over Infrastructure *receiver*. A Windows PC or phone can act as a Miracast over Infrastructure *source*.
- - As a Miracast receiver, the Surface Hub or device must be connected to your enterprise network via either Ethernet or a secure Wi-Fi connection (e.g. using either WPA2-PSK or WPA2-Enterprise security). If the Surface Hub or device is connected to an open Wi-Fi connection, Miracast over Infrastructure will disable itself.
- - As a Miracast source, the Windows PC or phone must be connected to the same enterprise network via Ethernet or a secure Wi-Fi connection.
-- The DNS Hostname (device name) of the Surface Hub or device needs to be resolvable via your DNS servers. You can achieve this by either allowing your Surface Hub to register automatically via Dynamic DNS, or by manually creating an A or AAAA record for the Surface Hub's hostname.
-- Windows 10 PCs must be connected to the same enterprise network via Ethernet or a secure Wi-Fi connection.
-- On Windows 10 PCs, the **Projecting to this PC** feature must be enabled in System Settings, and the device must have a Wi-Fi interface enabled in order to respond to discovery requests that only occur through the Wi-Fi adapter.
-
-
-It is important to note that Miracast over Infrastructure is not a replacement for standard Miracast. Instead, the functionality is complementary, and provides an advantage to users who are part of the enterprise network. Users who are guests to a particular location and don’t have access to the enterprise network will continue to connect using the Wi-Fi Direct connection method.
-
-The **InBoxApps/WirelessProjection/PinRequired** setting in the [SurfaceHub configuration service provider (CSP)](https://msdn.microsoft.com/windows/hardware/commercialize/customize/mdm/surfacehub-csp) is not required for Miracast over Infrastructure. This is because Miracast over Infrastructure only works when both devices are connected to the same enterprise network. This removes the security restriction that was previously missing from Miracast. We recommend that you continue using this setting (if you used it previously) as Miracast will fall back to regular Miracast if the infrastructure connection does not work.
-
-## FAQ
-**Why do I still need Wi-Fi to use Miracast over infrastructure?**
-Discovery requests to identify Miracast receivers can only occur through the Wi-Fi adapter. Once the receivers have been identified, Windows 10 can then attempt the connection to the network.
diff --git a/devices/surface-hub/miracast-troubleshooting.md b/devices/surface-hub/miracast-troubleshooting.md
deleted file mode 100644
index c4e2ff5b3e..0000000000
--- a/devices/surface-hub/miracast-troubleshooting.md
+++ /dev/null
@@ -1,84 +0,0 @@
----
-title: Troubleshoot Miracast on Surface Hub
-description: Learn how to resolve issues with Miracast on Surface Hub.
-ms.prod: surface-hub
-ms.sitesec: library
-author: dansimp
-ms.author: dansimp
-ms.topic: article
-ms.date: 06/20/2019
-ms.reviewer:
-manager: laurawi
-ms.localizationpriority: medium
----
-
-# Troubleshoot Miracast on Surface Hub
-
-Surface Hub supports wireless projection through the Miracast protocol. Most wireless monitors and adapters available today use the original implementation of Miracast. Surface Hub uses a slightly different version of Miracast known as **Miracast Autonomous Group Owner (AGO)**. A common troubleshooting step when projecting wirelessly to Surface Hub fails is to test projecting to another wireless monitor or adapter. However, in most cases, these devices are not using Miracast AGO and do not handle wireless projection the same way that Surface Hub does.
-
-In traditional Miracast, the projecting device will connect the access point set up by the Miracast-enabled monitor, and then the monitor will send traffic back to the projecting device using the network channel of the projecting device. Miracast AGO is a two-step connection process:
-
-- The first step is an initial connection using 2.4GHz.
-- After that initial handshake, the projecting device sends traffic to the monitor using the wireless channel settings on the monitor. If Surface Hub is connected to a Wi-Fi network, the access point, it will use the same channel as the connected network, otherwise it will use the Miracast channel from Settings.
-
-There are generally two types of issues with Miracast to Surface Hub: [connection](#connect-issues) and [performance](#performance-issues). In either case, it is a good idea to get a general picture of wireless network activity in the Surface Hub's location. Running a network scanning tool will show you the available networks and channel usage in the environment.
-
-## Connect issues
-
-Ensure both Wi-Fi and Miracast are both enabled in Settings on Surface Hub.
-
-If you ran a network scan, you should see Surface Hub Miracast listed as an access point. If Surface Hub's Miracast network shows up on the scan, but you cannot not see it as an available device, you can try to adjust the Miracast channel used by Surface Hub.
-
-When Surface Hub is connected to a Wi-Fi network it will use the same channel settings as the Wi-Fi access point for its Miracast access point. For troubleshooting purposes, disconnect Surface Hub from any Wi-Fi networks (but keep Wi-Fi enabled), so you can control the channel used for Miracast. You can manually select the Miracast channel in Settings. You will need to restart Surface Hub after each change. Generally speaking, you will want to use channels that do not show heavy utilization from the network scan.
-
-It is also possible that the connect issue can be the result of a problem on the connecting device. If the projecting device is running Windows, it should be Windows 8.1 or newer for full Miracast support. Again, for troubleshooting, disconnect the projecting device from any Wi-Fi networks. This will eliminate any channel switching between the access point channel and the Miracast channel set on Surface Hub. Also, some Group Policy and firewall settings may be tied to a Wi-Fi network.
-
-### Check drivers
-
-It is also a good idea to ensure the latest drivers and updates are installed on the projecting device. In Device Manager, open the Wi-Fi adapter and video adapter and check for an updated driver version. [Hotfix 3120232](https://support.microsoft.com/help/3120232/poor-wireless-performance-on-5-ghz-connections-on-surface-pro-3-and-surface-3) is highly recommended for Surface Pro 3 and Surface Pro 4 if they are on an older Wi-Fi driver.
-
-### Check for Miracast support
-
-Next, ensure Miracast is supported on the device.
-
-1. Press Windows Key + R and type `dxdiag`.
-2. Click "Save all information".
-3. Open the saved dxdiag.txt and find **Miracast**. It should say **Available, with HDCP**.
-
-### Check firewall
-
-The Windows firewall can block Miracast traffic. The simplest test is to disable the firewall and test projection. If Miracast works with the firewall disabled, add an exception for
-
- C:\Windows\System32\WUDFHost.exe
- Allow In/Out connections for TCP and UDP, Ports: All.
-
-### Check Group Policy settings
-
-On domain-joined devices, Group Policy can also block Miracast.
-
-1. Use the Windows Key + R and type `rsop.msc` to execute the **Resultant Set of Policy** snap-in. This will show the current policies applied to the PC.
-2. Review **Computer Configuration** > **Windows Settings** > **Security Settings** > **Wireless Network (IEEE 802.11) Policies**. There should be a setting for wireless policies.
-3. Double click the setting for wireless policies and a dialog box will appear.
-4. Open the **Network Permissions** tab and select **Allow everyone to create all user profiles**.
-
-### Check event logs
-
-The last place to check is in the Event logs. Miracast events will be logged to **Wlanautoconfig**. This is true on both Surface Hub and the projecting device. If you export Surface Hub logs, you can view Surface Hub's Wlanautoconfig in the **WindowsEventLog** folder. Errors in the event log can provide some additional details on where the connection fails.
-
-## Performance issues
-
-After wireless projection is connected, it is possible to see performance issues causing latency. This is generally a result of overall channel saturation or a situation that causes channel switching.
-
-For channel saturation, refer to the network scan and try to use channels with less traffic.
-
-Channel switching is caused when the Wi-Fi adapter needs to send traffic to multiple channels. Certain channels support Dynamic Frequency Selection (DFS). DFS is used on channels 49 through 148. Some Wi-Fi drivers will show poor performance when connected to a DFS channel. If you are seeing poor Miracast performance while connected to a DFS channel, try the projection on a non-DFS channel. Both Surface Hub and projecting device should use non-DFS channels.
-
-If Surface Hub and the projecting device are both connected to Wi-Fi but using different access points with different channels, this will force Surface Hub and the projecting device to channel switch while Miracast is connected. This will result in both poor wireless project and poor network performance over Wi-Fi. The channel switching will affect the performance of all wireless traffic, not just wireless projection.
-
-Channel switching will also occur if the projecting device is connected to an Wi-Fi network using a different channel than the channel that Surface Hub uses for Miracast. So, a best practice is to set Surface Hub's Miracast channel to the same channel as the most commonly used access point.
-
-If there are multiple Wi-Fi networks or access points in the environment, some channel switching is unavoidable. This is best addressed by ensuring all Wi-Fi drivers are up to date.
-
-## Contact Support
-
-If you have questions or need help, you can [create a support request](https://support.microsoft.com/supportforbusiness/productselection).
diff --git a/devices/surface-hub/monitor-surface-hub.md b/devices/surface-hub/monitor-surface-hub.md
deleted file mode 100644
index 9828a8a268..0000000000
--- a/devices/surface-hub/monitor-surface-hub.md
+++ /dev/null
@@ -1,159 +0,0 @@
----
-title: Monitor your Microsoft Surface Hub
-description: Monitoring for Microsoft Surface Hub devices is enabled through Microsoft Operations Management Suite (OMS).
-ms.assetid: 1D2ED317-DFD9-423D-B525-B16C2B9D6942
-ms.reviewer:
-manager: laurawi
-keywords: monitor Surface Hub, Microsoft Operations Management Suite, OMS
-ms.prod: surface-hub
-ms.sitesec: library
-author: dansimp
-ms.author: dansimp
-ms.topic: article
-ms.date: 07/27/2017
-ms.localizationpriority: medium
----
-
-# Monitor your Microsoft Surface Hub
-
-Monitoring for Microsoft Surface Hub devices is enabled through Microsoft Operations Management Suite (OMS). The [Operations Management Suite](https://go.microsoft.com/fwlink/?LinkId=718138) is Microsoft's IT management solution that helps you manage and protect your entire IT infrastructure, including your Surface Hubs.
-
-
-Surface Hub is offered as a Log Analytics solution in OMS, allowing you to collect and view usage and reliability data across all your Surface Hubs. Use the Surface Hub solution to:
-- Inventory your Surface Hubs.
-- View a snapshot of usage and reliability data for Skype meetings, wired and wireless projection, and apps on your Surface Hubs.
-- Create custom alerts to respond quickly if your Surface Hubs report software or hardware issues.
-
-## Add Surface Hub to Operations Management Suite
-
-1. **Sign in to Operations Management Suite (OMS)**. You can use either a Microsoft Account or a Work or School account to create a workspace. If your company is already using Azure Active Directory (Azure AD), use a Work or School account when you sign in to OMS. Using a Work or School account allows you to use identities from your Azure AD to manage permissions in OMS.
-2. **Create a new OMS workspace**. Enter a name for the workspace, select the workspace region, and provide the email address that you want associated with this workspace. Select **Create**.
-3. **Link Azure subscription to your workspace**. If your organization already has an Azure subscription, you can link it to your workspace. Note that you may need to request access from your organization’s Azure administrator.
-
- > [!NOTE]
- > If your organization does not have an Azure subscription, create a new one or select the default OMS Azure subscription from the list. Your workspace opens.
-
-4. **Add Surface Hub solution**. In the Solutions Gallery, select the **Surface Hub** tile in the gallery and then select **Add** on the solution’s details page. The solution is now visible on your workspace.
-
-## Use the Surface Hub dashboard
-From the **Overview** page in your OMS workspace, click the Surface Hub tile to see the Surface Hub dashboard. Use the dashboard to get a snapshot of usage and reliability data across your Surface Hubs. Click into each view on the dashboard to see detailed data, modify the query as desired, and create alerts.
-
-> [!NOTE]
-> Most of these views show data for the past 30 days, but this is subject to your subscription's data retention policy.
-
-**Active Surface Hubs**
-
-Use this view to get an inventory of all your Surface Hubs. Once connected to OMS, each Surface Hub periodically sends a "heartbeat" event to the server. This view shows Surface Hubs that have reported a heartbeat in the past 24 hours.
-
-
-
-**Wireless projection**
-
-Use this view to get usage and reliability data for wireless projection over the past 30 days. The graph shows the total number of wireless connections across all your Surface Hubs, which provides an indication whether people in your organization are using this feature. If it's a low number, it may suggest a need to provide training to help people in your organization learn how to wirelessly connect to a Surface Hub.
-
-Also, the graph shows a breakdown of successful and unsuccessful connections. If you see a high number of unsuccessful connections, devices may not properly support wireless projection using Miracast. For best performance, Microsoft suggests that devices run a WDI Wi-Fi driver and a WDDM 2.0 graphics driver. Use the details view to learn if wireless projection problems are common with particular devices.
-
-When a connection fails, users can also do the following if they are using a Windows laptop or phone:
-- Remove the paired device from **Settings** > **Devices** > **Connected devices**, then try to connect again.
-- Reboot the device.
-
-**Wired projection**
-
-Use this view to get usage and reliability data for wired projection over the past 30 days. If the graph shows a high number of unsuccessful connections, it may indicate a connectivity issue in your audio-visual pipeline. For example, if you use a HDMI repeater or a center-of-room control panel, they may need to be restarted.
-
-**Application usage**
-
-Use this view to get usage data for apps on your Surface Hubs over the past 30 days. The data comes from app launches on your Surface Hubs, not including Skype for Business. This view helps you understand which Surface Hub apps are the most valuable in your organization. If you are deploying new line-of-business apps in your environment, this can also help you understand how often they are being used.
-
-**Application Crashes**
-
-Use this view to get reliability data for apps on your Surface Hubs over the past 30 days. The data comes from app crashes on your Surface Hubs. This view helps you detect and notify app developers of poorly behaving in-box and line-of-business apps.
-
-**Sample Queries**
-
-Use this to create custom alerts based on a recommended set of queries. Alerts help you respond quickly if your Surface Hubs report software or hardware issues. For more inforamtion, see [Set up alerts using sample queries](#set-up-alerts-with-sample-queries).
-
-## Set up alerts with sample queries
-
-Use alerts to respond quickly if your Surface Hubs report software or hardware issues. Alert rules automatically run log searches according to a schedule, and runs one or more actions if the results match specific criteria. For more information, see [Alerts in Log Analytics](https://azure.microsoft.com/documentation/articles/log-analytics-alerts/).
-
-The Surface Hub Log Analytics solution comes with a set of sample queries to help you set up the appropriate alerts and understand how to resolve issues you may encounter. Use them as a starting point to plan your monitoring and support strategy.
-
-This table describes the sample queries in the Surface Hub solution:
-
-| Alert type | Impact | Recommended remediation | Details |
-| ---------- | ------ | ----------------------- | ------- |
-| Software | Error | **Reboot the device**. Reboot manually, or using the [Reboot configuration service provider](https://msdn.microsoft.com/library/windows/hardware/mt720802(v=vs.85).aspx). Suggest doing this between meetings to minimize impact to your people in your organization. | Trigger conditions: - A critical process in the Surface Hub operating system, such as the shell, projection, or Skype, crashes or becomes non-responsive. - The device hasn't reported a heartbeat in the past 24 hours. This may be due to network connectivity issue or network-related hardware failure, or an error with the diagnostic data reporting system. |
-| Software | Error | **Check your Exchange service**. Verify: - The service is available. - The device account password is up to date – see [Password management](password-management-for-surface-hub-device-accounts.md) for details.| Triggers when there's an error syncing the device calendar with Exchange. |
-| Software | Error | **Check your Skype for Business service**. Verify: - The service is available. - The device account password is up to date – see [Password management](password-management-for-surface-hub-device-accounts.md) for details. - The domain name for Skype for Business is properly configured - see [Configure a domain name](use-fully-qualified-domain-name-surface-hub.md). | Triggers when Skype fails to sign in. |
-| Software | Error | **Reset the device**. This takes some time, so you should take the device offline. For more information, see [Device reset](device-reset-surface-hub.md).| Triggers when there is an error cleaning up user and app data at the end of a session. When this operation repeatedly fails, the device is locked to protect user data. You must reset the device to continue. |
-| Hardware | Warning | **None**. Indicates negligible impact to functionality.| Triggers when there is an error with any of the following hardware components: - Virtual pen slots - NFC driver - USB hub driver - Bluetooth driver - Proximity sensor - Graphical performance (video card driver) - Mismatched hard drive - No keyboard/mouse detected |
-| Hardware | Error | **Contact Microsoft support**. Indicates impact to core functionality (such as Skype, projection, touch, and internet connectivity). **Note** Some events, including heartbeat, include the device’s serial number that you can use when contacting support.| Triggers when there is an error with any of the following hardware components. **Components that affect Skype**: - Speaker driver - Microphone driver - Camera driver **Components that affect wired and wireless projection**: - Wired touchback driver - Wired ingest driver - Wireless adapter driver - Wi-Fi Direct error **Other components**: - Touch digitizer driver - Network adapter error (not reported to OMS)|
-
-**To set up an alert**
-1. From the Surface Hub solution, select one of the sample queries.
-2. Modify the query as desired. See Log Analytics search reference to learn more.
-3. Click **Alert** at the top of the page to open the **Add Alert Rule** screen. See [Alerts in Log Analytics](https://azure.microsoft.com/documentation/articles/log-analytics-alerts/) for details on the options to configure the alert.
-4. Click **Save** to complete the alert rule. It will start running immediately.
-
-## Enroll your Surface Hub
-
-For Surface Hub to connect to and register with the OMS service, it must have access to the port number of your domains and the URLs. This table list the ports that OMS needs. For more information, see [Configure proxy and firewall settings in Log Analytics](https://azure.microsoft.com/documentation/articles/log-analytics-proxy-firewall/).
-
->[!NOTE]
->Surface Hub does not currently support the use of a proxy server to communicate with the OMS service.
-
-| Agent resource | Ports | Bypass HTTPS inspection? |
-| --------------------------- | ----- | ------------------------ |
-| *.ods.opinsights.azure.com | 443 | Yes |
-| *.oms.opinsights.azure.com | 443 | Yes |
-| *.blob.core.windows.net | 443 | Yes |
-| ods.systemcenteradvisor.com | 443 | No |
-
-The Microsoft Monitoring Agent, used to connect devices to OMS, is integrated with the Surface Hub operating system, so there is no need to install additional clients to connect Surface Hub to OMS.
-
-Once your OMS workspace is set up, there are several ways to enroll your Surface Hub devices:
-- [Settings app](#enroll-using-the-settings-app)
-- [Provisioning package](#enroll-using-a-provisioning-package)
-- [MDM provider](#enroll-using-a-mdm-provider), such as Microsoft Intune and Configuration Manager
-
-You'll need the workspace ID and primary key of your OMS workspace. You can get these from the OMS portal.
-
-### Enroll using the Settings app
-
-**To Enroll using the settings app**
-
-1. From your Surface Hub, start **Settings**.
-2. Enter the device admin credentials when prompted.
-3. Select **This device**, and navigate to **Device management**.
-4. Under **Monitoring**, select **Configure OMS settings**.
-5. In the OMS settings dialog, select **Enable monitoring**.
-6. Type the workspace ID and primary key of your OMS workspace. You can get these from the OMS portal.
-7. Click **OK** to complete the configuration.
-
-A confirmation dialog will appear telling you whether or not the OMS configuration was successfully applied to the device. If it was, the device will start sending data to OMS.
-
-### Enroll using a provisioning package
-You can use a provisioning package to enroll your Surface Hub. For more information, see [Create provisioning packages](provisioning-packages-for-certificates-surface-hub.md).
-
-### Enroll using a MDM provider
-You can enroll Surface Hub into OMS using the SurfaceHub CSP. Intune and Configuration Manager provide built-in experiences to help create policy templates for Surface Hub. For more information, see [Manage Surface Hub settings with an MDM provider](manage-settings-with-mdm-for-surface-hub.md).
-
-## Related topics
-
-[Manage Microsoft Surface Hub](manage-surface-hub.md)
-
-[Microsoft Surface Hub administrator's guide](surface-hub-administrators-guide.md)
-
-
-
-
-
-
-
-
-
diff --git a/devices/surface-hub/on-premises-deployment-surface-hub-device-accounts.md b/devices/surface-hub/on-premises-deployment-surface-hub-device-accounts.md
deleted file mode 100644
index d35f03b804..0000000000
--- a/devices/surface-hub/on-premises-deployment-surface-hub-device-accounts.md
+++ /dev/null
@@ -1,164 +0,0 @@
----
-title: On-premises deployment single forest (Surface Hub)
-description: This topic explains how you add a device account for your Microsoft Surface Hub when you have a single-forest, on-premises deployment.
-ms.assetid: 80E12195-A65B-42D1-8B84-ECC3FCBAAFC6
-ms.reviewer:
-manager: laurawi
-keywords: single forest deployment, on prem deployment, device account, Surface Hub
-ms.prod: surface-hub
-ms.sitesec: library
-author: dansimp
-ms.author: dansimp
-ms.date: 08/28/2018
-ms.localizationpriority: medium
----
-
-# On-premises deployment for Surface Hub in a single-forest environment
-
-
-This topic explains how you add a device account for your Microsoft Surface Hub when you have a single-forest, on-premises deployment.
-
-If you have a single-forest on-premises deployment with Microsoft Exchange 2013 or later and Skype for Business 2013 or later, then you can [use the provided PowerShell scripts](appendix-a-powershell-scripts-for-surface-hub.md#create-on-premises-ps-scripts) to create device accounts. If you’re using a multi-forest deployment, see [On-premises deployment for Surface Hub in a multi-forest environment](on-premises-deployment-surface-hub-multi-forest.md).
-
-1. Start a remote PowerShell session from a PC and connect to Exchange.
-
- Be sure you have the right permissions set to run the associated cmdlets.
-
- Note here that `$strExchangeServer` is the fully qualified domain name (FQDN) of your Exchange server, and `$strLyncFQDN` is the FQDN of your Skype for Business server.
-
- ```PowerShell
- Set-ExecutionPolicy Unrestricted
- $org='contoso.microsoft.com'
- $cred=Get-Credential $admin@$org
- $sessExchange = New-PSSession -ConfigurationName microsoft.exchange -Credential $cred -AllowRedirection -Authentication Kerberos -ConnectionUri "http://$strExchangeServer/powershell" -WarningAction SilentlyContinue
- $sessLync = New-PSSession -Credential $cred -ConnectionURI "https://$strLyncFQDN/OcsPowershell" -AllowRedirection -WarningAction SilentlyContinue
- Import-PSSession $sessExchange
- Import-PSSession $sessLync
- ```
-
-2. After establishing a session, you’ll either create a new mailbox and enable it as a RoomMailboxAccount, or change the settings for an existing room mailbox. This will allow the account to authenticate into the Surface Hub.
-
- If you're changing an existing resource mailbox:
-
- ```PowerShell
- Set-Mailbox -Identity 'HUB01' -EnableRoomMailboxAccount $true -RoomMailboxPassword (ConvertTo-SecureString -String -AsPlainText -Force)
- ```
-
- If you’re creating a new resource mailbox:
-
- ```PowerShell
- New-Mailbox -UserPrincipalName HUB01@contoso.com -Alias HUB01 -Name "Hub-01" -Room -EnableRoomMailboxAccount $true -RoomMailboxPassword (ConvertTo-SecureString -String -AsPlainText -Force)
- ```
-> [!IMPORTANT]
-> ActiveSync Virtual Directory Basic Authentication is required to be enabled as the Surface Hub is unable to authenticate using other authentication methods.
-
-3. After setting up the mailbox, you will need to either create a new Exchange ActiveSync policy, or use a compatible existing policy.
-
- Surface Hubs are only compatible with device accounts that have an ActiveSync policy where the **PasswordEnabled** property is set to False. If this isn’t set properly, then Exchange services on the Surface Hub (mail, calendar, and joining meetings), will not be enabled.
-
- If you haven’t created a compatible policy yet, use the following cmdlet—this one creates a policy called "Surface Hubs". Once it’s created, you can apply the same policy to other device accounts.
-
- ```PowerShell
- $easPolicy = New-MobileDeviceMailboxPolicy -Name “SurfaceHubs” -PasswordEnabled $false
- ```
-
- Once you have a compatible policy, then you will need to apply the policy to the device account. However, policies can only be applied to user accounts and not resource mailboxes. You need to convert the mailbox into a user type, apply the policy, and then convert it back into a mailbox—you may need to re-enable it and set the password again too.
-
- ```PowerShell
- $acctUpn = Get-Mailbox -Identity ""
- $credNewAccount.Password = ConvertTo-SecureString -String -AsPlainText -Force
- Set-Mailbox $acctUpn -Type Regular
- Set-CASMailbox $acctUpn -ActiveSyncMailboxPolicy $easPolicy
- Set-Mailbox $acctUpn -Type Room
- Set-Mailbox $acctUpn -RoomMailboxPassword $credNewAccount.Password -EnableRoomMailboxAccount $true
- ```
-
-4. Various Exchange properties can be set on the device account to improve the meeting experience for people. You can see which properties need to be set in the [Exchange properties](exchange-properties-for-surface-hub-device-accounts.md) section.
-
- ```PowerShell
- Set-CalendarProcessing -Identity $acctUpn -AutomateProcessing AutoAccept -AddOrganizerToSubject $false –AllowConflicts $false –DeleteComments $false -DeleteSubject $false -RemovePrivateProperty $false
- Set-CalendarProcessing -Identity $acctUpn -AddAdditionalResponse $true -AdditionalResponse "This is a Surface Hub room!"
- ```
-
-5. If you decide to have the password not expire, you can set that with PowerShell cmdlets too. See [Password management](password-management-for-surface-hub-device-accounts.md) for more information.
-
- ```PowerShell
- Set-AdUser $acctUpn -PasswordNeverExpires $true
- ```
-
-6. Enable the account in Active Directory so it will authenticate to the Surface Hub.
-
- ```PowerShell
- Set-AdUser $acctUpn -Enabled $true
- ```
-
-7. Enable the device account with Skype for Business by enabling your Surface Hub AD account on a Skype for Business Server pool:
-
- ```PowerShell
- Enable-CsMeetingRoom -SipAddress "sip:HUB01@contoso.com"
- -DomainController DC-ND-001.contoso.com -RegistrarPool LYNCPool15.contoso.com
- -Identity HUB01
- ```
-
- You'll need to use the Session Initiation Protocol (SIP) address and domain controller for the Surface Hub, along with your own Skype for Business Server pool identifier and user identity.
-
-8. OPTIONAL: You can also allow your Surface Hub to make and receive public switched telephone network (PSTN) phone calls by enabling Enterprise Voice for your account. Enterprise Voice isn't a requirement for Surface Hub, but if you want PSTN dialing functionality for the Surface Hub client, here's how to enable it:
-
- ```PowerShell
- Set-CsMeetingRoom -Identity HUB01 -DomainController DC-ND-001.contoso.com -LineURI "tel:+14255550555;ext=50555" -EnterpriseVoiceEnabled $true
- ```
-
- Again, you need to replace the provided domain controller and phone number examples with your own information. The parameter value `$true` stays the same.
-
-
- ## Disable anonymous email and IM
-
-
-
-
-Surface Hub uses a device account to provide email and collaboration services (IM, video, voice). This device account is used as the originating identity (the “from” party) when sending email, IM, and placing calls. As this account is not coming from an individual, identifiable user, it is deemed “anonymous” because it originated from the Surface Hub's device account.
-
-Assume you have a per-user client policy assigned to each meeting room device with an identity of **SurfaceHubPolicy**. To disable anonymous email and messaging, you add a clientPolicyEntry to this client policy by using the following commands.
-
-```
-$policyEntry = New-CsClientPolicyEntry -Name AllowResourceAccountSendMessage -value $false
-$clientPolicy = Get-CsClientPolicy -Identity SurfaceHubPolicy
-$clientPolicy.PolicyEntry.Add($policyEntry)
-Set-CsClientPolicy -Instance $clientPolicy
-```
-
-To verify that the policy has been set:
-
-```
-Select-Object -InputObject $clientPolicy -Property PolicyEntry
-```
-
-The output should be:
-
-```
-PolicyEntry
------------
-{Name=AllowResourceAccountSendMessage;Value=False}
-```
-
-
-To change the policy entry:
-
-```
-$policyEntry = New-CsClientPolicyEntry -Name AllowResourceAccountSendMessage -value $true
-$clientPolicy | Set-CsClientPolicy -PolicyEntry @{Replace = $policyEntry}
-```
-
-To remove the policy entry:
-
-```
-$policyEntry = New-CsClientPolicyEntry -Name AllowResourceAccountSendMessage -value $true
-$clientPolicy | Set-CsClientPolicy -PolicyEntry @{Remove = $policyEntry}
-```
-
-
-
-
-
-
-
diff --git a/devices/surface-hub/on-premises-deployment-surface-hub-multi-forest.md b/devices/surface-hub/on-premises-deployment-surface-hub-multi-forest.md
deleted file mode 100644
index 170dd03968..0000000000
--- a/devices/surface-hub/on-premises-deployment-surface-hub-multi-forest.md
+++ /dev/null
@@ -1,148 +0,0 @@
----
-title: On-premises deployment multi-forest (Surface Hub)
-description: This topic explains how you add a device account for your Microsoft Surface Hub when you have a multi-forest, on-premises deployment.
-keywords: multi forest deployment, on prem deployment, device account, Surface Hub
-ms.prod: surface-hub
-ms.sitesec: library
-author: dansimp
-ms.author: dansimp
-ms.date: 08/28/2018
-ms.reviewer:
-manager: laurawi
-ms.localizationpriority: medium
----
-
-# On-premises deployment for Surface Hub in a multi-forest environment
-
-
-This topic explains how you add a device account for your Microsoft Surface Hub when you have a multi-forest, on-premises deployment.
-
-If you have a multi-forest on-premises deployment with Microsoft Exchange 2013 or later and Skype for Business 2013 or later, then you can [use the provided PowerShell scripts](appendix-a-powershell-scripts-for-surface-hub.md#create-on-premises-ps-scripts) to create device accounts. If you’re using a single-forest deployment, see [On-premises deployment for Surface Hub in a single-forest environment](on-premises-deployment-surface-hub-device-accounts.md).
-
-1. Start a remote PowerShell session from a PC and connect to Exchange.
-
- Be sure you have the right permissions set to run the associated cmdlets.
-
- Note here that `$strExchangeServer` is the fully qualified domain name (FQDN) of your Exchange server, and `$strLyncFQDN` is the FQDN of your Skype for Business server.
-
- ```PowerShell
- Set-ExecutionPolicy Unrestricted
- $org='contoso.microsoft.com'
- $cred=Get-Credential $admin@$org
- $sessExchange = New-PSSession -ConfigurationName microsoft.exchange -Credential $cred -AllowRedirection -Authentication Kerberos -ConnectionUri "http://$strExchangeServer/powershell" -WarningAction SilentlyContinue
- $sessLync = New-PSSession -Credential $cred -ConnectionURI "https://$strLyncFQDN/OcsPowershell" -AllowRedirection -WarningAction SilentlyContinue
- Import-PSSession $sessExchange
- Import-PSSession $sessLync
- ```
-
-2. After establishing a session, create a new mailbox in the Resource Forest. This will allow the account to authenticate into the Surface Hub.
-
- If you're changing an existing resource mailbox:
-
- ```PowerShell
- New-Mailbox -UserPrincipalName HUB01@contoso.com -Alias HUB01 -Name "Hub-01"
- ```
-
-3. After setting up the mailbox, you will need to either create a new Exchange ActiveSync policy, or use a compatible existing policy.
-
- Surface Hubs are only compatible with device accounts that have an ActiveSync policy where the **PasswordEnabled** property is set to **False**. If this isn’t set properly, then Exchange services on the Surface Hub (mail, calendar, and joining meetings), will not be enabled.
-
- If you haven’t created a compatible policy yet, use the following cmdlet-—this one creates a policy called "Surface Hubs". Once it’s created, you can apply the same policy to other device accounts.
-
- ```PowerShell
- $easPolicy = New-MobileDeviceMailboxPolicy -Name “SurfaceHubs” -PasswordEnabled $false
- ```
-
- Once you have a compatible policy, then you will need to apply the policy to the device account.
-
- ```PowerShell
- Set-CASMailbox $acctUpn -ActiveSyncMailboxPolicy $easPolicy -ActiveSyncEnabled $true
- Set-Mailbox $acctUpn -Type Room
- ```
-
-4. Various Exchange properties can be set on the device account to improve the meeting experience for people. You can see which properties need to be set in the [Exchange properties](exchange-properties-for-surface-hub-device-accounts.md) section.
-
- ```PowerShell
- Set-CalendarProcessing -Identity $acctUpn -AutomateProcessing AutoAccept -AddOrganizerToSubject $false –AllowConflicts $false –DeleteComments $false -DeleteSubject $false -RemovePrivateProperty $false
- Set-CalendarProcessing -Identity $acctUpn -AddAdditionalResponse $true -AdditionalResponse "This is a Surface Hub room!"
- ```
-
-5. If you decide to have the password not expire, you can set that with PowerShell cmdlets too. See [Password management](password-management-for-surface-hub-device-accounts.md) for more information. This should be set in the User Forest.
-
- ```PowerShell
- Set-AdUser $acctUpn -PasswordNeverExpires $true
- ```
-
-6. Enable the account in Active Directory so it will authenticate to the Surface Hub. This should be set in the User Forest.
-
- ```PowerShell
- Set-AdUser $acctUpn -Enabled $true
- ```
-
-6. You now need to change the room mailbox to a linked mailbox:
-
- ```PowerShell
- $cred=Get-Credential AuthForest\ADAdmin
- Set-mailbox -Alias LinkedRoomTest1 -LinkedMasterAccount AuthForest\LinkedRoomTest1 -LinkedDomainController AuthForest-4939.AuthForest.extest.contoso.com -Name LinkedRoomTest1 -LinkedCredential $cred -Identity LinkedRoomTest1
- ```
-
-7. Enable the device account with Skype for Business by enabling your Surface Hub AD account on a Skype for Business Server pool:
-
- ```PowerShell
- Enable-CsMeetingRoom -SipAddress "sip:HUB01@contoso.com"
- -DomainController DC-ND-001.contoso.com -RegistrarPool LYNCPool15.contoso.com
- -Identity HUB01
- ```
-
- You'll need to use the Session Initiation Protocol (SIP) address and domain controller for the Surface Hub, along with your own Skype for Business Server pool identifier and user identity.
-
-
-## Disable anonymous email and IM
-
-
-
-Surface Hub uses a device account to provide email and collaboration services (IM, video, voice). This device account is used as the originating identity (the “from” party) when sending email, IM, and placing calls. As this account is not coming from an individual, identifiable user, it is deemed “anonymous” because it originated from the Surface Hub's device account.
-
-Assume you have a per-user client policy assigned to each meeting room device with an identity of **SurfaceHubPolicy**. To disable anonymous email and messaging, you add a clientPolicyEntry to this client policy by using the following commands.
-
-```
-$policyEntry = New-CsClientPolicyEntry -Name AllowResourceAccountSendMessage -value $false
-$clientPolicy = Get-CsClientPolicy -Identity SurfaceHubPolicy
-$clientPolicy.PolicyEntry.Add($policyEntry)
-Set-CsClientPolicy -Instance $clientPolicy
-```
-
-To verify that the policy has been set:
-
-```
-Select-Object -InputObject $clientPolicy -Property PolicyEntry
-```
-
-The output should be:
-
-```
-PolicyEntry
------------
-{Name=AllowResourceAccountSendMessage;Value=False}
-```
-
-
-To change the policy entry:
-
-```
-$policyEntry = New-CsClientPolicyEntry -Name AllowResourceAccountSendMessage -value $true
-$clientPolicy | Set-CsClientPolicy -PolicyEntry @{Replace = $policyEntry}
-```
-
-To remove the policy entry:
-
-```
-$policyEntry = New-CsClientPolicyEntry -Name AllowResourceAccountSendMessage -value $true
-$clientPolicy | Set-CsClientPolicy -PolicyEntry @{Remove = $policyEntry}
-```
-
-
-
-
-
-
diff --git a/devices/surface-hub/online-deployment-surface-hub-device-accounts.md b/devices/surface-hub/online-deployment-surface-hub-device-accounts.md
deleted file mode 100644
index 30f0e34b1f..0000000000
--- a/devices/surface-hub/online-deployment-surface-hub-device-accounts.md
+++ /dev/null
@@ -1,153 +0,0 @@
----
-title: Online deployment with Office 365 (Surface Hub)
-description: This topic has instructions for adding a device account for your Microsoft Surface Hub when you have a pure, online deployment.
-ms.assetid: D325CA68-A03F-43DF-8520-EACF7C3EDEC1
-ms.reviewer:
-manager: laurawi
-keywords: device account for Surface Hub, online deployment
-ms.prod: surface-hub
-ms.sitesec: library
-author: dansimp
-ms.author: dansimp
-ms.topic: article
-ms.date: 02/21/2018
-ms.localizationpriority: medium
----
-
-# Online deployment with Office 365 (Surface Hub)
-
-
-This topic has instructions for adding a device account for your Microsoft Surface Hub when you have a pure, online deployment.
-
-If you have a pure, online (O365) deployment, then you can [use the provided PowerShell scripts](appendix-a-powershell-scripts-for-surface-hub.md#create-os356-ps-scripts) to create device accounts.
-
-1. Start a remote PowerShell session on a PC and connect to Exchange.
-
- Be sure you have the right permissions set to run the associated cmdlets.
-
- ```PowerShell
- Set-ExecutionPolicy RemoteSigned
- $org='contoso.microsoft.com'
- $cred=Get-Credential admin@$org
- $sess= New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://outlook.office365.com/powershell-liveid/ -Credential $cred -Authentication Basic -AllowRedirection
- Import-PSSession $sess
- ```
-
-2. After establishing a session, you’ll either create a new mailbox and enable it as a RoomMailboxAccount, or change the settings for an existing room mailbox. This will allow the account to authenticate into the Surface Hub.
-
- If you're changing an existing resource mailbox:
-
- ```PowerShell
- Set-Mailbox -Identity 'HUB01' -EnableRoomMailboxAccount $true -RoomMailboxPassword (ConvertTo-SecureString -String -AsPlainText -Force)
- ```
-
- If you’re creating a new resource mailbox:
-
- ```PowerShell
- New-Mailbox -MicrosoftOnlineServicesID HUB01@contoso.com -Alias HUB01 -Name "Hub-01" -Room -EnableRoomMailboxAccount $true -RoomMailboxPassword (ConvertTo-SecureString -String -AsPlainText -Force)
- ```
-
-3. After setting up the mailbox, you will need to either create a new Exchange ActiveSync policy, or use a compatible existing policy.
-
- Surface Hubs are only compatible with device accounts that have an ActiveSync policy where the **PasswordEnabled** property is set to False. If this isn’t set properly, then Exchange services on the Surface Hub (mail, calendar, and joining meetings), will not be enabled.
-
- If you haven’t created a compatible policy yet, use the following cmdlet—this one creates a policy called "Surface Hubs". Once it’s created, you can apply the same policy to other device accounts.
-
- ```PowerShell
- $easPolicy = New-MobileDeviceMailboxPolicy -Name "SurfaceHubs" -PasswordEnabled $false -AllowNonProvisionableDevices $True
- ```
-
- Once you have a compatible policy, then you will need to apply the policy to the device account.
-
- ```PowerShell
- Set-CASMailbox 'HUB01@contoso.com' -ActiveSyncMailboxPolicy $easPolicy.Id
- ```
-
-4. Various Exchange properties must be set on the device account to improve the meeting experience. You can see which properties need to be set in the [Exchange properties](exchange-properties-for-surface-hub-device-accounts.md) section.
-
- ```PowerShell
- Set-CalendarProcessing -Identity 'HUB01@contoso.com' -AutomateProcessing AutoAccept -AddOrganizerToSubject $false –AllowConflicts $false –DeleteComments $false -DeleteSubject $false -RemovePrivateProperty $false
- Set-CalendarProcessing -Identity 'HUB01@contoso.com' -AddAdditionalResponse $true -AdditionalResponse "This is a Surface Hub room!"
- ```
-
-5. Connect to Azure AD.
-
- You first need to install Azure AD module for PowerShell version 2. In an elevated powershell prompt run the following command :
-
- ```PowerShell
- Install-Module -Name AzureAD
- ```
- You need to connect to Azure AD to apply some account settings. You can run this cmdlet to connect.
-
- ```PowerShell
- Import-Module AzureAD
- Connect-AzureAD -Credential $cred
- ```
-
-6. If you decide to have the password not expire, you can set that with PowerShell cmdlets too. See [Password management](password-management-for-surface-hub-device-accounts.md) for more information.
-
- ```PowerShell
- Set-AzureADUser -ObjectId "HUB01@contoso.com" -PasswordPolicies "DisablePasswordExpiration"
- ```
-
-7. Surface Hub requires a license for Skype for Business functionality. In order to enable Skype for Business, your environment will need to meet the [prerequisites for Skype for Business online](hybrid-deployment-surface-hub-device-accounts.md#skype-for-business-online).
-
- Next, you can use `Get-AzureADSubscribedSku` to retrieve a list of available SKUs for your O365 tenant.
-
- Once you list out the SKUs, you'll need to assign the SkuId you want to the `$License.SkuId` variable.
-
- ```PowerShell
- Set-AzureADUser -ObjectId "HUB01@contoso.com" -UsageLocation "US"
-
- Get-AzureADSubscribedSku | Select Sku*,*Units
- $License = New-Object -TypeName Microsoft.Open.AzureAD.Model.AssignedLicense
- $License.SkuId = SkuId You selected
-
- $AssignedLicenses = New-Object -TypeName Microsoft.Open.AzureAD.Model.AssignedLicenses
- $AssignedLicenses.AddLicenses = $License
- $AssignedLicenses.RemoveLicenses = @()
-
- Set-AzureADUserLicense -ObjectId "HUB01@contoso.com" -AssignedLicenses $AssignedLicenses
- ```
-
-8. Enable the device account with Skype for Business.
- If the Skype for Business PowerShell module is not installed, [download the Skype for Business Online Windows PowerShell Module](https://www.microsoft.com/download/details.aspx?id=39366).
-
- - Start by creating a remote PowerShell session from a PC.
-
- ```PowerShell
- Import-Module SkypeOnlineConnector
- $cssess=New-CsOnlineSession -Credential $cred
- Import-PSSession $cssess -AllowClobber
- ```
-
- - Next, if you aren't sure what value to use for the `RegistrarPool` parameter in your environment, you can get the value from an existing Skype for Business user using this cmdlet (for example, alice@contoso.com):
-
- ```PowerShell
- Get-CsOnlineUser -Identity 'alice@contoso.com' | fl registrarpool
- ```
- OR by setting a variable
-
- ```PowerShell
- $strRegistrarPool = Get-CsOnlineUser -Identity 'alice@contoso.com' | fl registrarpool | out-string
- $strRegistrarPool = $strRegistrarPool.Substring($strRegistrarPool.IndexOf(':') + 2)
- ```
-
- - Enable the Surface Hub account with the following cmdlet:
-
- ```PowerShell
- Enable-CsMeetingRoom -Identity 'HUB01@contoso.com' -RegistrarPool yourRegistrarPool -SipAddressType EmailAddress
- ```
-
- OR using the $strRegistarPool variable from above
-
- ```PowerShell
- Enable-CsMeetingRoom -Identity 'HUB01@contoso.com' -RegistrarPool $strRegistrarPool -SipAddressType EmailAddress
- ```
-
-For validation, you should be able to use any Skype for Business client (PC, Android, etc) to sign in to this account.
-
-
-
-
-
diff --git a/devices/surface-hub/password-management-for-surface-hub-device-accounts.md b/devices/surface-hub/password-management-for-surface-hub-device-accounts.md
deleted file mode 100644
index 1ef2fcaa46..0000000000
--- a/devices/surface-hub/password-management-for-surface-hub-device-accounts.md
+++ /dev/null
@@ -1,39 +0,0 @@
----
-title: Password management (Surface Hub)
-description: Every Microsoft Surface Hub device account requires a password to authenticate and enable features on the device.
-ms.assetid: 0FBFB546-05F0-430E-905E-87111046E4B8
-ms.reviewer:
-manager: laurawi
-keywords: password, password management, password rotation, device account
-ms.prod: surface-hub
-ms.sitesec: library
-author: dansimp
-ms.author: dansimp
-ms.topic: article
-ms.date: 07/27/2017
-ms.localizationpriority: medium
----
-
-# Password management (Surface Hub)
-
-Every Microsoft Surface Hub device account requires a password to authenticate and enable features on the device. For security reasons, you may want to change (or "rotate") this password regularly. However, if the device account’s password changes, the password that was previously stored on the Surface Hub will be invalid, and all features that depend on the device account will be disabled. You will need to update the device account’s password on the Surface Hub from the Settings app to re-enable these features.
-
-To simplify password management for your Surface Hub device accounts, there are two options:
-
-1. Turn off password expiration for the device account.
-2. Allow the Surface Hub to automatically rotate the device account’s password.
-
-
-## Turn off password rotation for the device account
-
-Set the device account’s **PasswordNeverExpires** property to True. You should verify whether this meets your organization’s security requirements.
-
-
-## Allow the Surface Hub to automatically rotate the device account’s password
-
-The Surface Hub can manage a device account’s password by changing it frequently without requiring you to manually update the device account’s information. You can enable this feature in **Settings**. Once enabled, the device account's password will change weekly during maintenance hours.
-
-Note that when the device account’s password is changed, you will not be shown the new password. If you need to sign in to the account, or to provide the password again (for example, if you want to change the device account settings on the Surface Hub), then you'll need use Active Directory or the Office 365 admin portal to reset the password.
-
-> [!IMPORTANT]
-> If your organization uses a hybrid topology (some services are hosted on-premises and some are hosted online through Office 365), you must setup the device account in **domain\username** format. Otherwise, password rotation will not work.
diff --git a/devices/surface-hub/physically-install-your-surface-hub-device.md b/devices/surface-hub/physically-install-your-surface-hub-device.md
deleted file mode 100644
index aeadcb900a..0000000000
--- a/devices/surface-hub/physically-install-your-surface-hub-device.md
+++ /dev/null
@@ -1,34 +0,0 @@
----
-title: Physically install Microsoft Surface Hub
-description: The Microsoft Surface Hub Readiness Guide will help make sure that your site is ready for the installation.
-ms.assetid: C764DBFB-429B-4B29-B4E8-D7F0073BC554
-ms.reviewer:
-manager: laurawi
-keywords: Surface Hub, readiness guide, installation location, mounting options
-ms.prod: surface-hub
-ms.sitesec: library
-author: dansimp
-ms.author: dansimp
-ms.topic: article
-ms.date: 07/27/2017
-ms.localizationpriority: medium
----
-
-# Physically install Microsoft Surface Hub
-
-
-The [Microsoft Surface Hub Readiness Guide](surface-hub-site-readiness-guide.md) will help make sure that your site is ready for the installation. It includes planning information for both the 55" and 84" devices, as well as info on moving the Surface Hub from receiving to the installation location, mounting options, and a list of what's in the box.
-
-You may also want to check out the Unpacking Guide. It will show you how to unpack the devices efficiently and safely. There are two guides, one for the 55" and one for the 84". A printed version of the Unpacking Guide is attached to the outside front of each unit's shipping crate.
-
-- Download the 55" Unpacking Guide from the [Microsoft Download Center](https://go.microsoft.com/fwlink/?LinkId=718145).
-- Download the 84" version from the [Microsoft Download Center](https://go.microsoft.com/fwlink/?LinkId=718146).
-
-
-
-
-
-
-
-
-
diff --git a/devices/surface-hub/prepare-your-environment-for-surface-hub.md b/devices/surface-hub/prepare-your-environment-for-surface-hub.md
deleted file mode 100644
index 69ca8e6c3e..0000000000
--- a/devices/surface-hub/prepare-your-environment-for-surface-hub.md
+++ /dev/null
@@ -1,133 +0,0 @@
----
-title: Prepare your environment for Microsoft Surface Hub
-description: This section contains an overview of the steps required to prepare your environment so that you can use all of the features of Microsoft Surface Hub.
-ms.assetid: 336A206C-5893-413E-A270-61BFF3DF7DA9
-ms.reviewer:
-manager: laurawi
-keywords: prepare environment, features of Surface Hub, create and test device account, check network availability
-ms.prod: surface-hub
-ms.sitesec: library
-author: dansimp
-ms.author: dansimp
-ms.topic: article
-ms.date: 12/04/2017
-ms.localizationpriority: medium
----
-
-# Prepare your environment for Microsoft Surface Hub
-
-
-This section contains an overview of setup dependencies and the setup process. Review the info in this section to help you prepare your environment and gather information needed to set up your Surface Hub.
-
-
-## Review infrastructure dependencies
-Review these dependencies to make sure Surface Hub features will work in your IT infrastructure.
-
-| Dependency | Purpose |
-|-------------|------------------|
-| Active Directory or Azure Active Directory (Azure AD) |
The Surface Hub's uses an Active Directory or Azure AD account (called a **device account**) to access Exchange and Skype for Business services. The Surface Hub must be able to connect to your Active Directory domain controller or to your Azure AD tenant in order to validate the device account’s credentials, as well as to access information like the device account’s display name, alias, Exchange server, and Session Initiation Protocol (SIP) address.
You can also domain join or Azure AD join your Surface Hub to allow a group of authorized users to configure settings on the Surface Hub. |
-| Exchange (Exchange 2013 or later, or Exchange Online) and Exchange ActiveSync |
Exchange is used for enabling mail and calendar features, and also lets people who use the device send meeting requests to the Surface Hub, enabling one-touch meeting join.
ActiveSync is used to sync the device account’s calendar and mail to the Surface Hub. If the device cannot use ActiveSync, it will not show meetings on the welcome screen, and joining meetings and emailing whiteboards will not be enabled. |
-| Skype for Business (Lync Server 2013 or later, or Skype for Business Online) | Skype for Business is used for various conferencing features, like video calls, instant messaging, and screen sharing.|
-| Mobile device management (MDM) solution (Microsoft Intune, Microsoft Endpoint Configuration Manager, or supported third-party MDM provider) | If you want to apply settings and install apps remotely, and to multiple devices at a time, you must set up a MDM solution and enroll the device to that solution. See [Manage settings with an MDM provider](manage-settings-with-mdm-for-surface-hub.md) for details. |
-| Microsoft Operations Management Suite (OMS) | OMS is used to monitor the health of Surface Hub devices. See [Monitor your Surface Hub](monitor-surface-hub.md) for details. |
-| Network and Internet access | In order to function properly, the Surface Hub should have access to a wired or wireless network. Overall, a wired connection is preferred. 802.1X Authentication is supported for both wired and wireless connections.**802.1X authentication:** In Windows 10, version 1703, 802.1X authentication for wired and wireless connections is enabled by default in Surface Hub. If your organization doesn't use 802.1X authentication, there is no configuration required and Surface Hub will continue to function as normal. If you use 802.1X authentication, you must ensure that the authentication certification is installed on Surface Hub. You can deliver the certificate to Surface Hub using the [ClientCertificateInstall CSP](https://msdn.microsoft.com/windows/hardware/commercialize/customize/mdm/clientcertificateinstall-csp) in MDM, or you can [create a provisioning package](provisioning-packages-for-surface-hub.md) and install it during first run or through the Settings app. After the certificate is applied to Surface Hub, 802.1X authentication will start working automatically.**Note:** For more information on enabling 802.1X wired authentication on Surface Hub, see [Enable 802.1x wired authentication](enable-8021x-wired-authentication.md).**Dynamic IP:** The Surface Hub cannot be configured to use a static IP. It must use DHCP to assign an IP address.**Proxy servers:** If your topology requires a connection to a proxy server to reach Internet services, then you can configure it during first run, or in Settings. Proxy credentials are stored across Surface Hub sessions and only need to be set once. |
-
-Additionally, note that Surface Hub requires the following open ports:
-- HTTPS: 443
-- HTTP: 80
-- NTP: 123
-
-If you are using Surface Hub with Skype for Business, you will need to open additional ports. Please follow the guidance below:
-- If you use Skype for Business Online, see [Office 365 IP URLs and IP address ranges](https://support.office.com/article/Office-365-URLs-and-IP-address-ranges-8548a211-3fe7-47cb-abb1-355ea5aa88a2?ui=en-US&rs=en-US&ad=US).
-- If you use Skype for Business Server, see [Skype for Business Server: Ports and protocols for internal servers](https://docs.microsoft.com/SkypeForBusiness/plan-your-deployment/network-requirements/ports-and-protocols).
-- If you use a hybrid of Skype for Business Online and Skype for Business Server, you need to open all documented ports from [Office 365 IP URLs and IP address ranges](https://support.office.com/article/Office-365-URLs-and-IP-address-ranges-8548a211-3fe7-47cb-abb1-355ea5aa88a2?ui=en-US&rs=en-US&ad=US) and [Skype for Business Server: Ports and protocols for internal servers](https://docs.microsoft.com/SkypeForBusiness/plan-your-deployment/network-requirements/ports-and-protocols?toc=/SkypeForBusiness/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json).
-
-Microsoft collects diagnostic data to help improve your Surface Hub experience. Add these sites to your allow list:
-- Diagnostic data client endpoint: `https://vortex.data.microsoft.com/`
-- Diagnostic data settings endpoint: `https://settings.data.microsoft.com/`
-
-### Proxy configuration
-
-If your organization restricts computers on your network from connecting to the Internet, there is a set of URLs that need to be available for devices to use Microsoft Store for Business. Some of the Store for Business features use Microsoft Store app and Microsoft Store services. Devices using Store for Business – either to acquire, install, or update apps – will need access to these URLs. If you use a proxy server to block traffic, your configuration needs to allow these URLs:
-
-- login.live.com
-- login.windows.net
-- account.live.com
-- clientconfig.passport.net
-- windowsphone.com
-- *.wns.windows.com
-- *.microsoft.com
-- www.msftncsi.com (prior to Windows 10, version 1607)
-- www.msftconnecttest.com/connecttest.txt (replaces www.msftncsi.com starting with Windows 10, version 1607)
-
-
-## Work with other admins
-
-Surface Hub interacts with a few different products and services. Depending on the size of your organization, there could be multiple people supporting different products in your environment. You'll want to include people who manage Exchange, Active Directory (or Azure Active Directory), mobile device management (MDM), and network resources in your planning and prep for Surface Hub deployments.
-
-
-## Create and verify device account
-
-A device account is an Exchange resource account that Surface Hub uses to display its meeting calendar, join Skype for Business calls, send email, and (optionally) to authenticate to Exchange. See [Create and test a device account](create-and-test-a-device-account-surface-hub.md) for details.
-
-After you've created your device account, to verify that it's setup correctly, run Surface Hub device account validation PowerShell scripts. For more information, see [PowerShell scripts for Surface Hub](appendix-a-powershell-scripts-for-surface-hub.md) later in this guide.
-
-
-
-## Prepare for first-run program
-There are a few more item to consider before you start the [first-run program](first-run-program-surface-hub.md).
-
-### Create provisioning packages (optional)
-You can use provisioning packages to add certificates, customize settings and install apps. See [Create provisioning packages](provisioning-packages-for-certificates-surface-hub.md) for details. You can [install provisioning packages at first-run](first-run-program-surface-hub.md#first-page).
-
-### Set up admin groups
-Every Surface Hub can be configured locally using the Settings app on the device. To prevent unauthorized users from changing settings, the Settings app requires admin credentials to open the app. See [Admin group management](admin-group-management-for-surface-hub.md) for details on how admin groups are set up and managed. You will [set up admins for the device at first run](first-run-program-surface-hub.md#setup-admins).
-
-### Review and complete Surface Hub setup worksheet (optional)
-When you go through the first-run program for your Surface Hub, there's some information that you'll need to supply. The setup worksheet summarizes that info, and provides lists of environment-specific info that you'll need when you go through the first-run program. For more information, see [Setup worksheet](setup-worksheet-surface-hub.md).
-
-
-## In this section
-
-
For Windows 10, settings that use the registry or a content services platform (CSP) can be configured using provisioning packages. You can also add certificates during first run using provisioning.
Every Surface Hub can be configured individually by opening the Settings app on the device. However, to prevent people who are not administrators from changing the settings, the Settings app requires administrator credentials to open the app and change settings.
-
The Settings app requires local administrator credentials to open the app.
-
-
-
-
-## More information
-
-- [Blog post: Surface Hub and the Skype for Business Trusted Domain List](https://blogs.technet.microsoft.com/y0av/2017/10/25/95/)
-- [Blog post: Surface Hub in a Multi-Domain Environment](https://blogs.technet.microsoft.com/y0av/2017/11/08/11/)
-- [Blog post: Configuring a proxy for your Surface Hub](https://blogs.technet.microsoft.com/y0av/2017/12/03/7/)
-
-
-
-
-
-
-
-
-
diff --git a/devices/surface-hub/provisioning-packages-for-surface-hub.md b/devices/surface-hub/provisioning-packages-for-surface-hub.md
deleted file mode 100644
index 305403b9dc..0000000000
--- a/devices/surface-hub/provisioning-packages-for-surface-hub.md
+++ /dev/null
@@ -1,322 +0,0 @@
----
-title: Create provisioning packages (Surface Hub)
-description: For Windows 10, settings that use the registry or a configuration service provider (CSP) can be configured using provisioning packages.
-ms.assetid: 8AA25BD4-8A8F-4B95-9268-504A49BA5345
-ms.reviewer:
-manager: laurawi
-keywords: add certificate, provisioning package
-ms.prod: surface-hub
-ms.sitesec: library
-author: dansimp
-ms.author: dansimp
-ms.topic: article
-ms.date: 03/16/2019
-ms.localizationpriority: medium
----
-
-# Create provisioning packages (Surface Hub)
-
-This topic explains how to create a provisioning package using the Windows Configuration Designer, and apply it to Surface Hub devices. For Surface Hub, you can use provisioning packages to add certificates, install Universal Windows Platform (UWP) apps, and customize policies and settings.
-
-You can apply a provisioning package using a USB stick during first-run setup, or through the **Settings** app.
-
-
-## Advantages
-- Quickly configure devices without using a mobile device management (MDM) provider.
-
-- No network connectivity required.
-
-- Simple to apply.
-
-[Learn more about the benefits and uses of provisioning packages.](https://technet.microsoft.com/itpro/windows/configure/provisioning-packages)
-
-
-## Requirements
-
-To create and apply a provisioning package to a Surface Hub, you'll need the following:
-
-- Windows Configuration Designer, which can be installed from Microsoft Store or from the Windows 10 Assessment and Deployment Kit (ADK). [Learn how to install Windows Configuration Designer.](https://technet.microsoft.com/itpro/windows/configure/provisioning-install-icd)
-- A USB stick.
-- If you apply the package using the **Settings** app, you'll need device admin credentials.
-
-You create the provisioning package on a PC running Windows 10, save the package to a USB drive, and then deploy it to your Surface Hub.
-
-
-## Supported items for Surface Hub provisioning packages
-
-Using the **Provision Surface Hub devices** wizard, you can:
-
-- Enroll in Active Directory, Azure Active Directory, or MDM
-- Create an device administrator account
-- Add applications and certificates
-- Configure proxy settings
-- Add a Surface Hub configuration file
-
->[!WARNING]
->You must run Windows Configuration Designer on Windows 10 to configure Azure Active Directory enrollment using the wizard.
-
-Using the advanced provisioning editor, you can add these items to provisioning packages for Surface Hub:
-
-- **Policies** - Surface Hub supports a subset of the policies in the [Policy configuration service provider](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx#surfacehubpolicies).
-- **Settings** - You can configure any setting in the [SurfaceHub configuration service provider](https://msdn.microsoft.com/library/windows/hardware/mt608323.aspx).
-
->[!TIP]
-> Use the wizard to create a package with the common settings, then switch to the advanced editor to add other settings.
->
->
-
-## Use the Surface Hub provisioning wizard
-
-After you [install Windows Configuration Designer](https://technet.microsoft.com/itpro/windows/configure/provisioning-install-icd), you can create a provisioning package.
-
-### Create the provisioning package
-
-1. Open Windows Configuration Designer:
- - From either the Start screen or Start menu search, type 'Windows Configuration Designer' and click on the Windows Configuration Designer shortcut,
-
- or
-
- - If you installed Windows Configuration Designer from the ADK, navigate to `C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Imaging and Configuration Designer\x86` (on an x64 computer) or `C:\Program Files\Windows Kits\10\Assessment and Deployment Kit\Imaging and Configuration Designer\x86\ICD.exe` (on an x86 computer), and then double-click **ICD.exe**.
-
-2. Click **Provision Surface Hub devices**.
-
-3. Name your project and click **Next**.
-
-### Configure settings
-
-
-
To provision the device with a certificate, click Add a certificate. Enter a name for the certificate, and then browse to and select the certificate to be used.
-
Toggle Yes or No for proxy settings. The default configuration for Surface Hub is to automatically detect proxy settings, so you can select No if that is the setting that you want. However, if your infrastructure previously required using a proxy server and has changed to not require a proxy server, you can use a provisioning package to revert your Surface Hub devices to the default settings by selecting Yes and Automatically detect settings. If you toggle Yes, you can select to automatically detect proxy settings, or you can manually configure the settings by entering a URL to a setup script, or a static proxy server address. You can also identify whether to use the proxy server for local addresses, and enter exceptions (addresses that Surface Hub should connect to directly without using the proxy server).
-
You can enroll the device in Active Directory and specify a security group to use the Settings app, enroll in Azure Active Directory to allow global admins to use the Settings app, or create a local administrator account on the device.To enroll the device in Active Directory, enter the credentials for a least-privileged user account to join the device to the domain, and specify the security group to have admin credentials on Surface Hub. If a provisioning package that enrolls a device in Active Directory is going to be applied to a Surface Hub that was reset, the same domain account can only be used if the account listed is a domain administrator or is the same account that set up the Surface Hub initially. Otherwise, a different domain account must be used in the provisioning package.Before you use a Windows Configuration Designer wizard to configure bulk Azure AD enrollment, set up Azure AD join in your organization. The maximum number of devices per user setting in your Azure AD tenant determines how many times the bulk token that you get in the wizard can be used. To enroll the device in Azure AD, select that option and enter a friendly name for the bulk token you will get using the wizard. Set an expiration date for the token (maximum is 30 days from the date you get the token). Click Get bulk token. In the Let's get you signed in window, enter an account that has permissions to join a device to Azure AD, and then the password. Click Accept to give Windows Configuration Designer the necessary permissions.To create a local administrator account, select that option and enter a user name and password. Important: If you create a local account in the provisioning package, you must change the password using the Settings app every 42 days. If the password is not changed during that period, the account might be locked out and unable to sign in.
-
Toggle Yes or No for enrollment in MDM. If you toggle Yes, you must provide a service account and password or certificate thumbprint that is authorized to enroll the device, and also specify the authentication type. If required by your MDM provider, also enter the URLs for the discovery service, enrollment service, and policy service. Learn more about managing Surface Hub with MDM.
-
You can install multiple Universal Windows Platform (UWP) apps in a provisioning package. For help with the settings, see Provision PCs with apps. Important: Although the wizard interface allows you to select a Classic Win32 app, only include UWP apps in a provisioning package that will be applied to Surface Hub. If you include a Classic Win32 app, provisioning will fail.
-
You don't configure any settings in this step. It provides instructions for including a configuration file that contains a list of device accounts. The configuration file must not contain column headers. When you apply the provisioning package to Surface Hub, if a Surface Hub configuration file is included on the USB drive, you can select the account and friendly name for the device from the file. See Sample configuration file for an example.Important: The configuration file can only be applied during the out-of-box setup experience (OOBE) and can only be used with provisioning packages created using the Windows Configuration Designer released with Windows 10, version 1703.
-
You can set a password to protect your provisioning package. You must enter this password when you apply the provisioning package to a device.
-
-
-After you're done, click **Create**. It only takes a few seconds. When the package is built, the location where the package is stored is displayed as a hyperlink at the bottom of the page.
-
-## Sample configuration file
-
-A Surface Hub configuration file contains a list of device accounts that your device can use to connect to Exchange and Skype for Business. When you apply a provisioning package to Surface Hub, you can include a configuration file in the root directory of the USB flash drive, and then select the desired account to apply to that device. The configuration file can only be applied during the out-of-box setup experience (OOBE) and can only be used with provisioning packages created using the Windows Configuration Designer released with Windows 10, version 1703.
-
-Use Microsoft Excel or other CSV editor to create a CSV file named `SurfaceHubConfiguration.csv`. In the file, enter a list of device accounts and friendly names in this format:
-
-```
-,,
-```
->[!IMPORTANT]
->Because the configuration file stores the device account passwords in plaintext, we recommend that you update the passwords after you've applied the provisioning package to your devices. You can use the [DeviceAccount node](https://msdn.microsoft.com/windows/hardware/commercialize/customize/mdm/surfacehub-csp#deviceaccount) in the [Surface Hub configuration service provider (CSP)](https://msdn.microsoft.com/windows/hardware/commercialize/customize/mdm/surfacehub-csp) to update the passwords via MDM.
-
-
-The following is an example of `SurfaceHubConfiguration.csv`.
-
-```
-Rainier@contoso.com,password,Rainier Surface Hub
-Adams@contoso.com,password,Adams Surface Hub
-Baker@contoso.com,password,Baker Surface Hub
-Glacier@constoso.com,password,Glacier Surface Hub
-Stuart@contoso.com,password,Stuart Surface Hub
-Fernow@contoso.com,password,Fernow Surface Hub
-Goode@contoso.com,password,Goode Surface Hub
-Shuksan@contoso.com,password,Shuksan Surface Hub
-Buckner@contoso.com,password,Buckner Surface Hub
-Logan@contoso.com,password,Logan Surface Hub
-Maude@consoto.com,password,Maude Surface hub
-Spickard@contoso.com,password,Spickard Surface Hub
-Redoubt@contoso.com,password,Redoubt Surface Hub
-Dome@contoso.com,password,Dome Surface Hub
-Eldorado@contoso.com,password,Eldorado Surface Hub
-Dragontail@contoso.com,password,Dragontail Surface Hub
-Forbidden@contoso.com,password,Forbidden Surface Hub
-Oval@contoso.com,password,Oval Surface Hub
-StHelens@contoso.com,password,St Helens Surface Hub
-Rushmore@contoso.com,password,Rushmore Surface Hub
-```
-
-## Use advanced provisioning
-
-After you [install Windows Configuration Designer](https://technet.microsoft.com/itpro/windows/configure/provisioning-install-icd), you can create a provisioning package.
-
-### Create the provisioning package (advanced)
-
-1. Open Windows Configuration Designer:
- - From either the Start screen or Start menu search, type 'Windows Configuration Designer' and click on the Windows Configuration Designer shortcut,
-
- or
-
- - If you installed Windows Configuration Designer from the ADK, navigate to `C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Imaging and Configuration Designer\x86` (on an x64 computer) or `C:\Program Files\Windows Kits\10\Assessment and Deployment Kit\Imaging and Configuration Designer\x86\ICD.exe` (on an x86 computer), and then double-click **ICD.exe**.
-
-2. Click **Advanced provisioning**.
-
-3. Name your project and click **Next**.
-
-4. Select **Common to Windows 10 Team edition**, click **Next**, and then click **Finish**.
-
- 
-
-5. In the project, under **Available customizations**, select **Common Team edition settings**.
-
- 
-
-
-### Add a certificate to your package
-You can use provisioning packages to install certificates that will allow the device to authenticate to Microsoft Exchange.
-
-> [!NOTE]
-> Provisioning packages can only install certificates to the device (local machine) store, and not to the user store. If your organization requires that certificates must be installed to the user store, use Mobile Device Management (MDM) to deploy these certificates. See your MDM solution documentation for details.
-
-1. In the **Available customizations** pane, go to **Runtime settings** > **Certificates** > **ClientCertificates**.
-
-2. Enter a **CertificateName** and then click **Add**.
-
-2. Enter the **CertificatePassword**.
-
-3. For **CertificatePath**, browse and select the certificate.
-
-4. Set **ExportCertificate** to **False**.
-
-5. For **KeyLocation**, select **Software only**.
-
-
-### Add a Universal Windows Platform (UWP) app to your package
-Before adding a UWP app to a provisioning package, you need the app package (either an .appx, or .appxbundle) and any dependency files. If you acquired the app from the Microsoft Store for Business, you will also need the *unencoded* app license. See [Distribute offline apps](https://technet.microsoft.com/itpro/windows/manage/distribute-offline-apps#download-an-offline-licensed-app) to learn how to download these items from the Microsoft Store for Business.
-
-1. In the **Available customizations** pane, go to **Runtime settings** > **UniversalAppInstall** > **DeviceContextApp**.
-
-2. Enter a **PackageFamilyName** for the app and then click **Add**. For consistency, use the app's package family name. If you acquired the app from the Microsoft Store for Business, you can find the package family name in the app license. Open the license file using a text editor, and use the value between the \...\ tags.
-
-3. For **ApplicationFile**, click **Browse** to find and select the target app (either an \*.appx or \*.appxbundle).
-
-4. For **DependencyAppxFiles**, click **Browse** to find and add any dependencies for the app. For Surface Hub, you will only need the x64 versions of these dependencies.
-
-If you acquired the app from the Microsoft Store for Business, you will also need to add the app license to your provisioning package.
-
-1. Make a copy of the app license, and rename it to use a **.ms-windows-store-license** extension. For example, "example.xml" becomes "example.ms-windows-store-license".
-
-2. In ICD, in the **Available customizations** pane, go to **Runtime settings** > **UniversalAppInstall** > **DeviceContextAppLicense**.
-
-3. Enter a **LicenseProductId** and then click **Add**. For consistency, use the app's license ID from the app license. Open the license file using a text editor. Then, in the \ tag, use the value in the **LicenseID** attribute.
-
-4. Select the new **LicenseProductId** node. For **LicenseInstall**, click **Browse** to find and select the license file that you renamed in Step 1.
-
-
-### Add a policy to your package
-Surface Hub supports a subset of the policies in the [Policy configuration service provider](https://msdn.microsoft.com/library/windows/hardware/dn904962.aspx). Some of those policies can be configured with ICD.
-
-1. In the **Available customizations** pane, go to **Runtime settings** > **Policies**.
-
-2. Select one of the available policy areas.
-
-3. Select and set the policy you want to add to your provisioning package.
-
-
-### Add Surface Hub settings to your package
-
-You can add settings from the [SurfaceHub configuration service provider](https://msdn.microsoft.com/library/windows/hardware/mt608323.aspx) to your provisioning package.
-
-1. In the **Available customizations** pane, go to **Runtime settings** > **WindowsTeamSettings**.
-
-2. Select one of the available setting areas.
-
-3. Select and set the setting you want to add to your provisioning package.
-
-
-## Build your package
-
-1. When you are done configuring the provisioning package, on the **File** menu, click **Save**.
-
-2. Read the warning that project files may contain sensitive information, and click **OK**.
-
- > [!IMPORTANT]
- > When you build a provisioning package, you may include sensitive information in the project files and in the provisioning package (.ppkg) file. Although you have the option to encrypt the .ppkg file, project files are not encrypted. You should store the project files in a secure location and delete the project files when they are no longer needed.
-
-3. On the **Export** menu, click **Provisioning package**.
-
-4. Change **Owner** to **IT Admin**, which will set the precedence of this provisioning package higher than provisioning packages applied to this device from other sources.
-
-5. Set a value for **Package Version**, and then select **Next.**
-
- > [!TIP]
- > You can make changes to existing packages and change the version number to update previously applied packages.
-
-6. Optional: You can choose to encrypt the package and enable package signing.
-
- - **Enable package encryption** - If you select this option, an auto-generated password will be shown on the screen.
-
- - **Enable package signing** - If you select this option, you must select a valid certificate to use for signing the package. You can specify the certificate by clicking **Browse...** and choosing the certificate you want to use to sign the package.
-
- > [!IMPORTANT]
- > We recommend that you include a trusted provisioning certificate in your provisioning package. When the package is applied to a device, the certificate is added to the system store and any package signed with that certificate thereafter can be applied silently.
-
-7. Click **Next** to specify the output location where you want the provisioning package to go once it's built. By default, Windows ICD uses the project folder as the output location.
-Optionally, you can click **Browse** to change the default output location.
-
-8. Click **Next**.
-
-9. Click **Build** to start building the package. The project information is displayed in the build page and the progress bar indicates the build status.
-If you need to cancel the build, click **Cancel**. This cancels the current build process, closes the wizard, and takes you back to the **Customizations Page**.
-
-10. If your build fails, an error message will show up that includes a link to the project folder. You can scan the logs to determine what caused the error. Once you fix the issue, try building the package again.
-If your build is successful, the name of the provisioning package, output directory, and project directory will be shown.
-
- - If you choose, you can build the provisioning package again and pick a different path for the output package. To do this, click **Back** to change the output package name and path, and then click **Next** to start another build.
-
- - If you are done, click **Finish** to close the wizard and go back to the **Customizations Page**.
-
-11. Select the **output location** link to go to the location of the package. Copy the .ppkg to an empty USB flash drive.
-
-
-## Apply a provisioning package to Surface Hub
-
-There are two options for deploying provisioning packages to a Surface Hub. [During the first run wizard](#apply-a-provisioning-package-during-first-run), you can apply a provisioning package that installs certificates, or after the first-run program is complete, you can apply a provisioning package that configures settings, apps, and certificates by using [Settings](#apply-a-package-using-settings).
-
-
-### Apply a provisioning package during first run
-
-> [!IMPORTANT]
-> During the first-run program, you can only use provisioning packages to install certificates. Use the **Settings** app to install apps and apply other settings.
-
-1. When you turn on the Surface Hub for the first time, the first-run program will display the [**Hi there page**](first-run-program-surface-hub.md#first-page). Make sure that the settings are properly configured before proceeding.
-
-2. Insert the USB flash drive containing the .ppkg file into the Surface Hub. If the package is in the root directory of the drive, the first-run program will recognize it and ask if you want to set up the device. Select **Set up**.
-
- 
-
-3. The next screen asks you to select a provisioning source. Select **Removable Media** and tap **Next**.
-
- 
-
-4. Select the provisioning package (\*.ppkg) that you want to apply, and tap **Next**. Note that you can only install one package during first run.
-
- 
-
-5. The first-run program will show you a summary of the changes that the provisioning package will apply. Select **Yes, add it**.
-
- 
-
-6. If a configuration file is included in the root directory of the USB flash drive, you will see **Select a configuration**. The first device account in the configuration file will be shown with a summary of the account information that will be applied to the Surface Hub.
-
- 
-
-7. In **Select a configuration**, select the device name to apply, and then click **Next**.
-
- 
-
-The settings from the provisioning package will be applied to the device and OOBE will be complete. After the device restarts, you can remove the USB flash drive.
-
-### Apply a package using Settings
-
-1. Insert the USB flash drive containing the .ppkg file into the Surface Hub.
-
-2. From the Surface Hub, start **Settings** and enter the admin credentials when prompted.
-
-3. Navigate to **Surface Hub** > **Device management**. Under **Provisioning packages**, select **Add or remove a provisioning package**.
-
-4. Select **Add a package**.
-
-5. Choose your provisioning package and select **Add**. You may have to re-enter the admin credentials if prompted.
-
-6. You'll see a summary of the changes that the provisioning package will apply. Select **Yes, add it**.
-
-
diff --git a/devices/surface-hub/remote-surface-hub-management.md b/devices/surface-hub/remote-surface-hub-management.md
deleted file mode 100644
index 1794a9bcac..0000000000
--- a/devices/surface-hub/remote-surface-hub-management.md
+++ /dev/null
@@ -1,24 +0,0 @@
----
-title: Remote Surface Hub management
-description: This section lists topics for managing Surface Hub.
-keywords: remote management, MDM, install apps, monitor Surface Hub, Operations Management Suite, OMS
-ms.prod: surface-hub
-ms.sitesec: library
-author: dansimp
-ms.author: dansimp
-ms.topic: article
-ms.date: 07/27/2017
-ms.reviewer:
-manager: laurawi
-ms.localizationpriority: medium
----
-
-# Remote Surface Hub management
-
-## In this section
-
-|Topic | Description|
-| ------ | --------------- |
-| [Manage settings with an MDM provider]( https://technet.microsoft.com/itpro/surface-hub/manage-settings-with-mdm-for-surface-hub) | Surface Hub provides an enterprise management solution to help IT administrators manage policies and business applications on these devices using a mobile device management (MDM) solution.|
-| [Monitor your Surface Hub]( https://technet.microsoft.com/itpro/surface-hub/monitor-surface-hub) | Monitoring for Surface Hub devices is enabled through Microsoft Operations Management Suite.|
-| [Windows updates](https://technet.microsoft.com/itpro/surface-hub/manage-windows-updates-for-surface-hub) | You can manage Windows updates on your Surface Hub by setting the maintenance window, deferring updates, or using WSUS.|
diff --git a/devices/surface-hub/save-bitlocker-key-surface-hub.md b/devices/surface-hub/save-bitlocker-key-surface-hub.md
deleted file mode 100644
index 12e59349d6..0000000000
--- a/devices/surface-hub/save-bitlocker-key-surface-hub.md
+++ /dev/null
@@ -1,46 +0,0 @@
----
-title: Save your BitLocker key (Surface Hub)
-description: Every Microsoft Surface Hub is automatically set up with BitLocker drive encryption software. Microsoft strongly recommends that you make sure you back up your BitLocker recovery keys.
-ms.assetid: E11E4AB6-B13E-4ACA-BCE1-4EDC9987E4F2
-ms.reviewer:
-manager: laurawi
-keywords: Surface Hub, BitLocker, Bitlocker recovery keys
-ms.prod: surface-hub
-ms.sitesec: library
-author: dansimp
-ms.author: dansimp
-ms.topic: article
-ms.date: 07/08/2019
-ms.localizationpriority: medium
----
-
-# Save your BitLocker key (Surface Hub)
-
-
-Every Microsoft Surface Hub is automatically set up with BitLocker drive encryption software. Microsoft strongly recommends that you make sure you back up your BitLocker recovery keys.
-
-There are several ways to manage your BitLocker key on the Surface Hub.
-
-1. If you’ve joined the Surface Hub to a domain, the device will back up the key on the domain and store it under the computer object.
-
- If you can’t find the BitLocker key after joining the device to a domain, it’s likely that your Active Directory schema doesn’t support BitLocker key backup. If you don’t want to change the schema, you can save the BitLocker key by going to Settings and following the procedure for using a local admin account, which is detailed later in this list.
-
-2. If you’ve joined the Surface Hub to Azure Active Directory (Azure AD), the BitLocker key will be stored under the account that was used to join the device.
-
-3. If you’re using a local admin account to manage the device, you can save the BitLocker key by going to the **Settings** app and navigating to **Update & security** > **Recovery**. Insert a USB drive and select the option to save the BitLocker key. The key will be saved to a text file on the USB drive.
-
-
-## Related topics
-
-[Manage Microsoft Surface Hub](manage-surface-hub.md)
-
-[Microsoft Surface Hub administrator's guide](surface-hub-administrators-guide.md)
-
-
-
-
-
-
-
-
-
diff --git a/devices/surface-hub/set-up-your-surface-hub.md b/devices/surface-hub/set-up-your-surface-hub.md
deleted file mode 100644
index 08ca875984..0000000000
--- a/devices/surface-hub/set-up-your-surface-hub.md
+++ /dev/null
@@ -1,59 +0,0 @@
----
-title: Set up Microsoft Surface Hub
-description: Set up instructions for Surface Hub include a setup worksheet, and a walkthrough of the first-run program.
-ms.assetid: 4D1722BC-704D-4471-BBBE-D0500B006221
-ms.reviewer:
-manager: laurawi
-keywords: set up instructions, Surface Hub, setup worksheet, first-run program
-ms.prod: surface-hub
-ms.sitesec: library
-author: dansimp
-ms.author: dansimp
-ms.topic: article
-ms.date: 07/27/2017
-ms.localizationpriority: medium
----
-
-# Set up Microsoft Surface Hub
-
-
-Set up instructions for Surface Hub include a setup worksheet, and a walkthrough of the first-run program.
-
-Before you turn on your Microsoft Surface Hub for the first time, make sure you've completed the checklist at the end of the [Prepare your environment for Surface Hub](prepare-your-environment-for-surface-hub.md) section, and that you have the information listed in the [Setup worksheet](setup-worksheet-surface-hub.md). When you do power it on, the device will walk you through a series of setup screens. If you haven't properly set up your environment, or don't have the required information, you'll have to do extra work afterward making sure the settings are correct.
-
-## In this section
-
-
-
When you've finished pre-setup and are ready to start first-time setup for your Surface Hub, make sure you have all the information listed in this section.
The term "first run" refers to the series of steps you'll go through the first time you power up your Surface Hub, and means the same thing as "out-of-box experience" (OOBE). This section will walk you through the process.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/devices/surface-hub/setup-worksheet-surface-hub.md b/devices/surface-hub/setup-worksheet-surface-hub.md
deleted file mode 100644
index e7352a5dbe..0000000000
--- a/devices/surface-hub/setup-worksheet-surface-hub.md
+++ /dev/null
@@ -1,252 +0,0 @@
----
-title: Setup worksheet (Surface Hub)
-description: When you've finished pre-setup and are ready to start first-time setup for your Microsoft Surface Hub, make sure you have all the information listed in this section.
-ms.assetid: AC6F925B-BADE-48F5-8D53-8B6FFF6EE3EB
-ms.reviewer:
-manager: laurawi
-keywords: Setup worksheet, pre-setup, first-time setup
-ms.prod: surface-hub
-ms.sitesec: library
-author: dansimp
-ms.author: dansimp
-ms.topic: article
-ms.date: 06/20/2019
-ms.localizationpriority: medium
----
-
-# Setup worksheet (Surface Hub)
-
-
-When you've finished pre-setup and are ready to start first-time setup for your Microsoft Surface Hub, make sure you have all the information listed in this section.
-
-You should fill out one list for each Surface Hub you need to configure, although some information can be used on all Surface Hubs, like the proxy information or domain credentials. Some of this information may not be needed, depending on how you've decided to configure your device, or depending on how the environment is configured for your organization's infrastructure.
-
-
-
-
Property
-
What this is used for
-
Example
-
Actual value
-
-
-
-
Proxy information
-
-
-
If your network uses a proxy for network and/or Internet access, you must provide a script or server/port information.
-
-
-
Proxy script: http://contoso/proxy.pa
-- OR -
-Server and port info: 10.10.10.100, port 80
-
-
-
-
-
-
-
-
-
Wireless network credentials (username and password)
-
-
-
If you decide to connect your device to Wi-Fi, and your wireless network requires user credentials.
-
-
-
admin1@contoso.com, #MyPassw0rd
-
-
-
-
-
-
-
-
Device account UPN or Domain\username and device account password
-
-
-
This is the User Principal Name (UPN) or the domain\username, and the password of the device account. Mail, calendar, and Skype for Business depend on a compatible device account.
-
-
-
UPN: ConfRoom15@contoso.com, #Passw0rd1
-- OR -
-Domain and username: CONTOSO\ConfRoom15, #Passw0rd1
-
-
-
-
-
-
-
-
Device account Microsoft Exchange server
-
-
-
This is the device account's Exchange server.
-Mail, calendar, and Skype for Business depend on a compatible device account.
-For mail and calendar to work, the device account must have a valid Exchange server. The device will try to find this automatically.
This is the device account's Skype for Business SIP address.
-Mail, calendar, and Skype for Business depend on a compatible device account.
-For Skype for Business to work, the device account must have a valid SIP address. The device will try to find this automatically.
-
-
-
sip: ConfRoom15@contoso.com
-
-
-
-
-
-
-
-
Friendly name
-
-
-
The friendly name of the device is the broadcast name that people will see when they try to wirelessly connect to the Surface Hub. This name will be displayed prominently on the Surface Hub's screen.
-We suggest that the friendly name you choose is recognizable and unique so that people can distinguish one Surface Hub from another when trying to connect.
-
-
-
Conference Room 15
-
-
-
-
-
-
-
-
Device name
-
-
-
The device name is the name that will be used for domain join, and is the identity you will see in your MDM provider if the device is enrolled into MDM.
-The device name you choose must not be the same name as any other device on the user’s Active Directory domain (if you decide to domain join the device). The device cannot join the domain if its name is not unique.
-
-
-
-
confroom15
-
-
-
-
-
-
-
-
IF YOU'RE JOINING AZURE AD
-
-
-
-
-
Azure AD tenant user credentials (username and password)
-
-
-
If you decide to have people in your Azure Active Directory (Azure AD) organization become admins on the device, then you'll need to join Azure AD.
-To join Azure AD, you will need valid user credentials.
-
-
-
admin1@contoso.com, #MyPassw0rd
-
-
-
-
-
-
-
-
IF YOU'RE JOINING A DOMAIN
-
-
-
-
-
Domain to join
-
-
-
This is the domain you will need to join so that a security group of your choice can be admins for the device.
-You may need the fully qualified domain name (FQDN).
-
-
-
contoso (short name) OR contoso.corp.com (FQDN)
-
-
-
-
-
-
-
-
Domain account credentials (username and password)
-
-
-
A domain can't be joined unless you provide sufficient account credentials to join the domain. Once you provide a domain to join and credentials to join the domain, then a security group of your choice can change settings on the device.
-
-
-
admin1, #MyPassw0rd
-
-
-
-
-
-
-
-
Admin security group alias
-
-
-
This is a security group in your Active Directory (AD); any members of this security group can change settings on the device.
-
-
-
SurfaceHubAdmins
-
-
-
-
-
-
-
-
IF YOU'RE USING A LOCAL ADMIN
-
-
-
-
-
Local admin account credentials (username and password)
-
-
-
If you decide not to join an AD domain or Azure AD, you can create a local admin account on the device.
-
-
-
admin1, #MyPassw0rd
-
-
-
-
-
-
-
-
IF YOU NEED TO INSTALL CERTIFICATES OR APPS
-
-
-
-
-
USB drive
-
-
-
If you know before first run that you want to install certificates or universal apps, follow the steps in Create provisioning packages. Your provisioning packages will be created on a USB drive.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/devices/surface-hub/skype-hybrid-voice.md b/devices/surface-hub/skype-hybrid-voice.md
deleted file mode 100644
index 910f2d0129..0000000000
--- a/devices/surface-hub/skype-hybrid-voice.md
+++ /dev/null
@@ -1,108 +0,0 @@
----
-title: Online or hybrid deployment using Skype Hybrid Voice environment (Surface Hub)
-description: This topic explains how to enable Skype for Business Cloud PBX with on premises PSTN connectivity via Cloud Connector Edition or Skype for Business 2015 pool.
-keywords: hybrid deployment, Skype Hybrid Voice
-ms.prod: surface-hub
-ms.sitesec: library
-author: dansimp
-ms.author: dansimp
-ms.topic: article
-ms.date: 07/27/2017
-ms.reviewer:
-manager: laurawi
-ms.localizationpriority: medium
----
-
-# Online or hybrid deployment using Skype Hybrid Voice environment (Surface Hub)
-
-This topic explains how to enable Skype for Business Cloud PBX with on-premises Public Switched Telephone Network (PSTN) connectivity via Cloud Connector Edition or Skype for Business 2015 pool. In this option. your Skype for Business home pools and Exchange servers are in the cloud, and are connected by PSTN via an on-premises pool running Skype for Business 2015 or Cloud Connector edition. [Learn more about different Cloud PBX options](https://technet.microsoft.com/library/mt612869.aspx).
-
-If you deployed Skype for Business Cloud PBX with one of the hybrid voice options, follow the steps below to enable the room account for Surface Hub. It is important to create a regular user account first, assign all hybrid voice options and phone numbers, and then convert the account to a room account. If you do not follow this order, you will not be able to assign a hybrid phone number.
-
->[!WARNING]
->If you create an account before configuration of Hybrid voice (you run Enable-CSMeetingRoom command), you will not be able to configure required hybrid voice parameters. In order to configure hybrid voice parameters for a previously configured account or to reconfigure a phone number, delete the E5 or E3 + Cloud PBX add-on license, and then follow the steps below, starting at step 3.
-
-1. Create a new user account for Surface Hub. This example uses surfacehub2@adatum.com. The account can be created in local Active Directory and synchronized to the cloud, or created directly in the cloud.
-
- 
-
-2. Select **Password Never Expires**. This is important for a Surface Hub device.
-
- 
-
-3. In Office 365, add **E5** license or **E3 and Cloud PBX** add-on to the user account created for the room. This is required for Hybrid Voice to work.
-
- 
-
-4. Wait approximately 15 minutes until the user account for the room appears in Skype for Business Online.
-
-5. After the user account for room is created in Skype for Business Online, enable it for Hybrid Voice in Skype for Business Remote PowerShell by running the following cmdlet:
-
- ```
- Set-csuser surfacehub2@adatum.com EnterpriseVoiceEnabled $true -HostedVoiceMail $true -onpremlineuri tel:+15005000102
- ```
-
-6. Validate Hybrid Voice call flow by placing test calls from the Surface Hub.
-
-7. Start a remote PowerShell session on a PC and connect to Exchange by running the following cmdlets.
-
- ```
- Set-ExecutionPolicy Unrestricted
- $cred=Get-Credential -Message "Please use your Office 365 admin credentials"
- $sess= New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://outlook.office365.com/ps1-liveid/ -Credential $cred -Authentication Basic -AllowRedirection
- Import-PSSession $sess
- ```
-
-8. After establishing a session, modify the user account for the room to enable it as a **RoomMailboxAccount** by running the following cmdlets. This allows the account to authenticate with Surface Hub.
-
- ```
- Set-Mailbox surfacehub2@adatum.com -Type Room
- Set-Mailbox surfacehub2@adatum.com -EnableRoomMailboxAccount $true -RoomMailboxPassword (ConvertTo-SecureString -String -AsPlainText -Force)
- ```
-
-9. After setting up the mailbox, you will need to either create a new Exchange ActiveSync policy, or use a compatible existing policy.
-
- Surface Hubs are only compatible with device accounts that have an ActiveSync policy where the **PasswordEnabled** property is set to **False**. If this isn’t set properly, then Exchange services on the Surface Hub (mail, calendar, and joining meetings), will not be enabled.
-
- If you haven’t created a compatible policy yet, use the following cmdlet (this one creates a policy called "Surface Hubs"). After it’s created, you can apply the same policy to other device accounts.
-
- ```
- $easPolicy = New-MobileDeviceMailboxPolicy -Name "SurfaceHubs" -PasswordEnabled $false
- ```
-
- After you have a compatible policy, then you will need to apply the policy to the device account. However, policies can only be applied to user accounts and not resource mailboxes. Run the following cmdlets to convert the mailbox into a user type, apply the policy, and then convert it back into a mailbox (you may need to re-enable the account and set the password again).
-
- ```
- Set-Mailbox surfacehub2@adatum.com -Type Regular
- Set-CASMailbox surfacehub2@adatum.com -ActiveSyncMailboxPolicy $easPolicy.id
- Set-Mailbox surfacehub2@adatum.com -Type Room
- $credNewAccount = Get-Credential -Message "Please provide the Surface Hub username and password"
- Set-Mailbox surfacehub2@adatum.com -RoomMailboxPassword $credNewAccount.Password -EnableRoomMailboxAccount $true
- ```
-
-10. Various Exchange properties must be set on the device account to improve the meeting experience. You can see which properties can be set in [Exchange properties](exchange-properties-for-surface-hub-device-accounts.md). The following cmdlets provide an example of setting Exchange properties.
-
- ```
- Set-CalendarProcessing surfacehub2@adatum.com -AutomateProcessing AutoAccept -AddOrganizerToSubject $false –AllowConflicts $false –DeleteComments $false -DeleteSubject $false -RemovePrivateProperty $false
- Set-CalendarProcessing surfacehub2@adatum.com -AddAdditionalResponse $true -AdditionalResponse "This is a Surface Hub room!"
- ```
-
-11. Enable the mailbox as a meeting device in Skype for Business Online. Run the following cmdlet which enables the account as a meeting device.
-
- ```
- Get-CsTenant | select registrarpool
- Enable-CsMeetingRoom surfacehub2@adatum.com -RegistrarPool 'sippoolbl20a04.infra.lync.com' -SipAddressType UserPrincipalName
- ```
-
- As a result of running this cmdlet, users will be asked if they are in a meeting room, as shown in the following image. **Yes** will mute the microphone and speaker.
-
- 
-
-
-
-At this moment the room account is fully configured, including Hybrid Voice. If you use Skype on-premises, you can configure additional attributes, like description, location, etc., on-premises. If you create a room in Skype Online, these parameters can be set online.
-
-In the following image, you can see how the device appears to users.
-
-
-
diff --git a/devices/surface-hub/support-solutions-surface-hub.md b/devices/surface-hub/support-solutions-surface-hub.md
deleted file mode 100644
index 9de0b753f9..0000000000
--- a/devices/surface-hub/support-solutions-surface-hub.md
+++ /dev/null
@@ -1,52 +0,0 @@
----
-title: Top support solutions for Microsoft Surface Hub
-description: Find top solutions for common issues using Surface Hub.
-ms.assetid: CF58F74D-8077-48C3-981E-FCFDCA34B34A
-ms.reviewer:
-manager: laurawi
-keywords: Troubleshoot common problems, setup issues
-ms.prod: surface-hub
-ms.sitesec: library
-author: dansimp
-ms.author: dansimp
-ms.topic: article
-ms.date: 10/24/2017
-ms.localizationpriority: medium
----
-
-# Top support solutions for Microsoft Surface Hub
-
-Microsoft regularly releases both updates and solutions for Surface Hub. To ensure your devices can receive future updates, including security updates, it's important to keep your Surface Hub devices updated. For a complete listing of the update history, see [Surface Hub update history](https://www.microsoft.com/surface/support/surface-hub/surface-hub-update-history) and [Known issues and additional information about Microsoft Surface Hub](https://support.microsoft.com/help/4025643).
-
->[!TIP]
->Looking for [Surface Hub warranty information](https://support.microsoft.com/help/4040687/surface-surface-documents)?
-
-These are the top Microsoft Support solutions for common issues experienced when using Surface Hub.
-
-## Setup and install issues
-
-- [Setup troubleshooting](troubleshoot-surface-hub.md#setup-troubleshooting)
-- [Exchange ActiveSync errors](troubleshoot-surface-hub.md#exchange-activesync-errors)
-
-## Miracast issues
-
-- [Troubleshoot Miracast on Surface Hub](miracast-troubleshooting.md)
-
-## Download updates issues
-
-- [Surface Hub can't download updates from Windows Update](https://support.microsoft.com/help/3191418/surface-hub-can-t-download-updates-from-windows-update)
-
-## Connect app issues
-
-- [The Connect app in Surface Hub exits unexpectedly](https://support.microsoft.com/help/3157417/the-connect-app-in-surface-hub-exits-unexpectedly)
-
-
-
-
-
-
-
-
-
-
-
diff --git a/devices/surface-hub/surface-Hub-installs-updates-and-restarts-outside-maintenance-hours.md b/devices/surface-hub/surface-Hub-installs-updates-and-restarts-outside-maintenance-hours.md
deleted file mode 100644
index 98ad30890e..0000000000
--- a/devices/surface-hub/surface-Hub-installs-updates-and-restarts-outside-maintenance-hours.md
+++ /dev/null
@@ -1,40 +0,0 @@
----
-title: Surface Hub may install updates and restart outside maintenance hours
-description: troubleshooting information for Surface Hub regarding automatic updates
-ms.assetid: 6C09A9F8-F9CF-4491-BBFB-67A1A1DED0AA
-keywords: surface hub, maintenance window, update
-ms.prod: surface-hub
-ms.sitesec: library
-author: Teresa-MOTIV
-ms.author: v-tea
-ms.topic: article
-ms.localizationpriority: medium
----
-
-# Surface Hub may install updates and restart outside maintenance hours
-
-Under specific circumstances, Surface Hub installs updates during business hours instead of during the regular maintenance window. The device then restarts if it is necessary. You cannot use the device until the process is completed.
-
-> [!NOTE]
-> This isn't expected behavior for missing a maintenance window. It occurs only if the device is out-of-date for a long time.
-
-## Cause
-To ensure that Surface Hub remains available for use during business hours, the Hub is configured to perform administrative functions during a maintenance window that is defined in Settings (see "References," below). During this maintenance period, the Hub automatically installs any available updates through Windows Update or Windows Server Update Service (WSUS). Once updates are complete, the Hub may restart.
-
-Updates can be installed during the maintenance window only if the Surface Hub is turned on but not in use or reserved. For example, if the Surface Hub is scheduled for a meeting that lasts 24 hours, any updates that are scheduled to be installed will be deferred until the Hub is available during the next maintenance window. If the Hub continues to be busy and misses multiple maintenance windows, the Hub will eventually begin to install and download updates. This can occur during or outside the maintenance window. Once the download and installation has begun, the device may restart.
-
-## To avoid this issue
-
-It's important that you set aside maintenance time for Surface Hub to perform administrative functions. Reserving the Surface Hub for 24 hour intervals or using the device during the maintenance window delays installing updates. We recommend that you not use or reserve the Hub during scheduled maintenance period. A two-hour window should be reserved for updating.
-
-One option that you can use to control the availability of updates is Windows Server Update Service (WSUS). WSUS provides control over what updates are installed and when.
-
-## References
-
-[Update the Surface Hub](first-run-program-surface-hub.md#update-the-surface-hub)
-
-[Maintenance window](manage-windows-updates-for-surface-hub.md#maintenance-window)
-
-[Deploy Windows 10 updates using Windows Server Update Services (WSUS)](/windows/deployment/update/waas-manage-updates-wsus)
-
-
diff --git a/devices/surface-hub/surface-hub-2s-account.md b/devices/surface-hub/surface-hub-2s-account.md
deleted file mode 100644
index fb93b0e7d9..0000000000
--- a/devices/surface-hub/surface-hub-2s-account.md
+++ /dev/null
@@ -1,96 +0,0 @@
----
-title: "Create Surface Hub 2S device account"
-description: "This page describes the procedure for creating the Surface Hub 2S device account."
-keywords: separate values with commas
-ms.prod: surface-hub
-ms.sitesec: library
-author: greg-lindsay
-ms.author: greglin
-manager: laurawi
-audience: Admin
-ms.topic: article
-ms.date: 06/20/2019
-ms.localizationpriority: Medium
----
-
-# Create Surface Hub 2S device account
-
-Creating a Surface Hub device account (also known as a Room mailbox) allows Surface Hub 2S to receive, approve, or decline meeting requests and join meetings using Microsoft Teams or Skype for Business. Configure the device account during OOBE setup. If needed you can change it later (without going through OOBE setup).
-
-Unlike standard Room mailboxes that remain disabled by default, you need to enable the Surface Hub 2S device account to sign on to Microsoft Teams and Skype for Business. Surface Hub 2S relies on Exchange ActiveSync, which requires an ActiveSync mailbox policy on the device account. Apply the default ActiveSync mailbox policy that comes with Exchange Online.
-
-Create the account using the Microsoft 365 admin center or by using PowerShell. You can use Exchange Online PowerShell to configure specific features including:
-
-- Calendar processing for every Surface Hub device account.
-- Custom auto replies to scheduling requests.
-- If the default ActiveSync mailbox policy has already been modified by someone else or another process, you will likely have to create and assign a new ActiveSync mailbox policy
-
-## Create account using Microsoft 365 admin center
-
-1. In the Microsoft 365 admin center, go to **Resources** and choose **Rooms & Equipment** and then select **+ Room**.
-
-2. Provide a name and email address for the device account. Leave remaining settings unchanged in the default state.
-
-
-
-
-
-3. Set the password for the device account. To set the password, choose **Users** and then select **Active Users**. Now search for the newly created user to set the password. Ensure that you **do not** select the option **Make this user change their password when they first sign in.**
-
-
-
-4. Assign the room with an Office 365 license. It’s recommended to assign the Office 365 **Meeting Room** license, a new option that automatically enables the account for Skype for Business Online and Microsoft Teams.
-
-
-
-### Finalize setup via PowerShell
-
-- **Skype for Business:** For Skype for Business only (on-premises or online), you can enable the Skype for Business object by running **Enable-CsMeetingRoom** to enable features such as Meeting room prompt for audio and Lobby hold.
-
-- **Microsoft Teams and Skype for Business Calendar:** Set [**Calendar Auto processing**](https://docs.microsoft.com/surface-hub/surface-hub-2s-account?source=docs#set-calendar-auto-processing) for this account.
-
-## Create account using PowerShell
-Instead of using the Microsoft Admin Center portal, you can create the account using PowerShell.
-
-### Connect to Exchange Online PowerShell
-
-```powershell
-$365Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://ps.outlook.com/powershell -Credential (Get-Credential) -Authentication Basic –AllowRedirection
-$ImportResults = Import-PSSession $365Session
-```
-
-### Create a new Room Mailbox
-
-```powershell
-New-Mailbox -MicrosoftOnlineServicesID account@YourDomain.com -Alias SurfaceHub2S -Name SurfaceHub2S -Room -EnableRoomMailboxAccount $true -RoomMailboxPassword (ConvertTo-SecureString -String "" -AsPlainText -Force)
-```
-
-### Set Calendar Auto processing
-
-```powershell
-Set-CalendarProcessing -Identity "account@YourDomain.com" -AutomateProcessing AutoAccept -AddOrganizerToSubject $false –AllowConflicts $false –DeleteComments $false -DeleteSubject $false -RemovePrivateProperty $false -AddAdditionalResponse $true -AdditionalResponse "This room is equipped with a Surface Hub"
-```
-
-### Assign a license
-
-```powershell
-Connect-MsolService
-Set-Msoluser -UserPrincipalName account@YourDomain.com -UsageLocation IE
-Set-MsolUserLicense -UserPrincipalName "account@YourDomain.com" -AddLicenses "contoso:MEETING_ROOM"
-```
-
-## Connect to Skype for Business Online using PowerShell
-
-### Install prerequisites
-
-- [Visual C++ 2017 Redistributable](https://aka.ms/vs/15/release/vc_redist.x64.exe)
-- [Skype for Business Online PowerShell Module](https://www.microsoft.com/download/confirmation.aspx?id=39366)
-
-```powershell
-Import-Module LyncOnlineConnector
-$SfBSession = New-CsOnlineSession -Credential (Get-Credential)
-Import-PSSession $SfBSession -AllowClobber
-
-# Enable the Skype for Business meeting room
-Enable-CsMeetingRoom -Identity account@YourDomain.com -RegistrarPool(Get-CsTenant).Registrarpool -SipAddressType EmailAddress
-```
diff --git a/devices/surface-hub/surface-hub-2s-adoption-kit.md b/devices/surface-hub/surface-hub-2s-adoption-kit.md
deleted file mode 100644
index 2cc29c519b..0000000000
--- a/devices/surface-hub/surface-hub-2s-adoption-kit.md
+++ /dev/null
@@ -1,59 +0,0 @@
----
-title: "Surface Hub 2S Adoption and training guides"
-description: "Microsoft has developed downloadable materials that you can make available for your users to aid in adoption of Surface Hub 2S."
-keywords: separate values with commas
-ms.prod: surface-hub
-ms.sitesec: library
-author: greg-lindsay
-ms.author: greglin
-manager: laurawi
-audience: Admin
-ms.topic: article
-ms.date: 11/04/2019
-ms.localizationpriority: Medium
----
-
-# Surface Hub 2S adoption and training guides
-
-Whether you're a small or large business, a Surface Hub adoption plan is critical in generating the right use cases and helping your users become comfortable with the device. Check out these downloadable guides designed to help you deliver training across your organization.
-
-## On-demand training
-
-- [Surface Hub 2S adoption and training videos](surface-hub-2s-adoption-videos.md)
-
-## Adoption toolkit
-
-- [Surface Hub adoption toolkit](downloads/SurfaceHubAdoptionToolKit.pdf)
-
-## Training guides
-
-- [Training guide – end user](downloads/TrainingGuide-SurfaceHub2S-EndUser.pdf)
-- [Training guide – power user](downloads/TrainingGuide-SurfaceHub2S-PowerUser.pdf)
-- [Training guide – help desk](downloads/TrainingGuide-SurfaceHub2S-HelpDesk.pdf)
-- [Training guide – Microsoft Teams desktop](downloads/Guide-SurfaceHub2S-Teams.pptx)
-
-[Download all training guides](https://download.microsoft.com/download/2/2/3/2234F70E-E65A-4790-93DF-F4C373A75B8E/SurfaceHub2S-TrainerGuides-July2019.zip)
-
-## End user guides
-
-- [Guide to Navigation on Surface Hub](downloads/Guide-SurfaceHub2S-Navigation.pptx)
-- [Guide to Office 365 on Surface Hub](downloads/Guide-SurfaceHub2S-Office365.pptx)
-- [Guide to Microsoft Whiteboard on Surface Hub](downloads/Guide-SurfaceHub2S-Whiteboard.pptx)
-- [Guide to Microsoft Teams on Surface Hub](downloads/Guide-SurfaceHub2S-Teams.pptx)
-
-[Download all end user guides](https://download.microsoft.com/download/E/7/F/E7FC6611-BB55-43E1-AF36-7BD5CE6E0FE0/SurfaceHub2S-EndUserGuides-July2019.zip)
-
-## Quick reference cards
-
-- [Connect your PC](downloads/QRCConnectYourPC.pdf)
-- [Join a Teams Meeting](downloads/QRCJoinTeamsMeeting.pdf)
-- [Manage a Teams meeting](downloads/QRCManageTeamsMeeting.pdf)
-- [Navigation basics](downloads/QRCNavigationBasics.pdf)
-- [Schedule a Teams meeting](downloads/QRCScheduleTeamsMeeting.pdf)
-- [Start a new Teams meeting](downloads/QRCStartNewTeamsMeeting.pdf)
-- [Share or send a file](downloads/QRCShareSendFile.pdf)
-- [Sign in to view meetings and files](downloads/QRCSignInToViewMeetingsFiles.pdf)
-- [Whiteboard advanced](downloads/QRCWhiteboardAdvanced.pdf)
-- [Whiteboard tools](downloads/QRCWhiteboardTools.pdf)
-
-[Download all quick reference cards](https://download.microsoft.com/download/E/7/F/E7FC6611-BB55-43E1-AF36-7BD5CE6E0FE0/SurfaceHub2S-EndUserGuides-July2019.zip)
diff --git a/devices/surface-hub/surface-hub-2s-adoption-videos.md b/devices/surface-hub/surface-hub-2s-adoption-videos.md
deleted file mode 100644
index 5e0419624f..0000000000
--- a/devices/surface-hub/surface-hub-2s-adoption-videos.md
+++ /dev/null
@@ -1,137 +0,0 @@
----
-title: "Surface Hub 2S on-demand adoption and training videos"
-description: "This page contains on-demand training for Surface Hub 2S."
-keywords: separate values with commas
-ms.prod: surface-hub
-ms.sitesec: library
-author: greg-lindsay
-ms.author: greglin
-manager: laurawi
-audience: Admin
-ms.topic: article
-ms.date: 11/04/2019
-ms.localizationpriority: Medium
----
-
-# Surface Hub 2S on-demand adoption and training videos
-
-This page contains comprehensive training for Surface Hub 2S, available on demand.
-
-## Chapter 1 - Training overview
-
-> ![VIDEO ]
-
-- Welcome and introduction
-- Training overview and agenda
-- Software and technology reference
-- Surface Hub messaging
-- Industries and user roles
-- Overview of training services
-- Training best practices
-
-## Chapter 2 - Getting started with Surface Hub
-
-> ![VIDEO ]
-
-- What is Surface Hub?
-- Technical overview
-- Steelcase Roam and the mobility story
-- Surface Hub services
-- Getting started with Surface Hub
-- Gathering expectations
-
-## Chapter 3 - Navigating Surface Hub
-
-> ![VIDEO ]
-
-- Welcome screen
-- Start menu
-- Full screen
-- Clip to Whiteboard
-- Task bar menu
-- Teams/Skype
-- End Session
-
-## Chapter 4 - Whiteboarding and collaboration
-
-> ![VIDEO ]
-
-- Whiteboard introduction
-- Starting the Whiteboard
-- Whiteboard tools
-- Inserting pictures
-- Changing the background
-- Sharing the whiteboard
-- Export the Whiteboard
-
-## Chapter 5 - Exploring Surface Hub apps
-
-> ![VIDEO ]
-
-- Surface Hub apps introduction
-- PowerPoint overview
-- Microsoft Word
-- Microsoft Excel
-- Microsoft Edge
-
-## Chapter 6 - Advanced apps and Office 365
-
-> ![VIDEO ]
-
-- Advanced apps introduction
-- Microsoft Maps
-- Photos
-- Power BI
-- Sign in to Office 365
-- OneDrive
-- CoAuthor documents
-
-## Chapter 7 - Connecting devices
-
-> ![VIDEO ]
-
-- Connect introduction
-- Miracast overview
-- Touch and Pen Input
-- Wired connect overview
-- Line of Business app workflows
-- Troubleshooting Miracast and wired connect
-
-## Chapter 8 - Skype for Business meetings
-
-> ![VIDEO ]
-
-- Introduction to Skype for Business
--Scheduling Skype for Business meetings
-- Start a meeting
-- Start an ad hoc meeting
-- Join a meeting on your calendar
-- Managing a Skype for Business meeting
-- Present content
-
-## Chapter 9 - Microsoft Teams meetings
-
-> ![VIDEO ]
-
-- Introduction to Microsoft Teams
-- Scheduling Microsoft Teams meetings
-- Start a meeting
-- Start an ad hoc meeting
-- Join a meeting on your calendar
-- Managing a Microsoft Teams meeting
-- Present content
-- Conclusion
-
-## Chapter 10 - Basic troubleshooting
-
-> ![VIDEO ]
-
-- Introduction to Surface Hub troubleshooting
-- Application troubleshooting
-- End Session
-- Restart the device
-- Power cycle the device
-- Factory reset
-- Settings
-- Manage Surface Hub
-- Conclusion
\ No newline at end of file
diff --git a/devices/surface-hub/surface-hub-2s-change-history.md b/devices/surface-hub/surface-hub-2s-change-history.md
deleted file mode 100644
index f629bd6bd6..0000000000
--- a/devices/surface-hub/surface-hub-2s-change-history.md
+++ /dev/null
@@ -1,38 +0,0 @@
----
-title: "Change history for Surface Hub 2S"
-description: "This page shows change history for Surface Hub 2S."
-keywords: separate values with commas
-ms.prod: surface-hub
-ms.sitesec: library
-author: greg-lindsay
-ms.author: greglin
-audience: Admin
-ms.manager: laurawi
-ms.topic: article
-ms.date: 06/20/2019
-ms.localizationpriority: Medium
----
-
-# Change history for Surface Hub 2S
-
-This topic summarizes new and updated content in the Surface Hub 2S documentation library.
-
-## August 2019
-
-Changes | Description
-|:--- |:---
-|Connect devices to Surface Hub 2S| Updated with guidance for connecting to a second display.
-
-## July 2019
-
-Changes | Description
-|:--- |:--- |
-| Reset and recovery for Surface Hub 2S | Added link to Surface recovery website that enables customers to download a recovery image for Surface Hub 2S |
-| Surface Hub 2S tech specs | Updated power consumption data |
-| Surface Hub 2S Adoption Kit | New |
-
-## June 2019
-
-Changes | Description
-|:--- |:--- |
-| Published new guidance for Surface Hub 2S | New |
diff --git a/devices/surface-hub/surface-hub-2s-connect.md b/devices/surface-hub/surface-hub-2s-connect.md
deleted file mode 100644
index a09044e60d..0000000000
--- a/devices/surface-hub/surface-hub-2s-connect.md
+++ /dev/null
@@ -1,135 +0,0 @@
----
-title: "Connect devices to Surface Hub 2S"
-description: "This page explains how to connect external devices to Surface Hub 2S."
-keywords: separate values with commas
-ms.prod: surface-hub
-ms.sitesec: library
-author: greg-lindsay
-ms.author: greglin
-manager: laurawi
-audience: Admin
-ms.topic: article
-ms.date: 02/24/2020
-ms.localizationpriority: Medium
----
-
-# Connect devices to Surface Hub 2S
-Surface Hub 2S enables you to connect external devices, mirror the display on Surface Hub 2S to another device, and connect multiple third-party peripherals including video conference cameras, conference phones, and room system devices.
-
-You can display content from your devices to Surface Hub 2S. If the source device is Windows-based, that device can also provide TouchBack and InkBack, which takes video and audio from the connected device and presents them on Surface Hub 2S. If Surface Hub 2S encounters a High-Bandwidth Digital Content Protection (HDCP) signal, such as a Blu-ray DVD player, the source is displayed as a black image.
-
-> [!NOTE]
-> Surface Hub 2S uses the video input selected until a new connection is made, the existing connection is disrupted, or the Connect app is closed.
-
-## Recommended wired configurations
-
-In general, it’s recommended to use native cable connections whenever possible such as USB-C to USB-C or HDMI to HDMI. Other combinations such as MiniDP to HDMI or MiniDP to USB-C will also work. Some additional configuration may be required to optimize the video-out experience, as described on this page.
-
-| **Connection** | **Functionality** | **Description**|
-| --- | --- | ---|
-| HDMI + USB-C | HDMI-in for audio and video
USB-C for TouchBack and InkBack | USB-C supports TouchBack and InkBack with the HDMI A/V connection.
Use USB-C to USB-A to connect to legacy computers.
**NOTE:** For best results, connect HDMI before connecting a USB-C cable. If the computer you're using for HDMI is not compatible with TouchBack and InkBack, you won't need a USB-C cable. |
-| USB-C (via compute module) | Video-in Audio-in | Single cable needed for A/V
TouchBack and InkBack is supported
HDCP enabled |
-| HDMI (in port) | Video, Audio into Surface Hub 2S | Single cable needed for A/V
TouchBack and InkBack not supported
HDCP enabled |
-| MiniDP 1.2 output | Video-out such as mirroring to a larger projector. | Single cable needed for A/V |
-
-When you connect a guest computer to Surface Hub 2S via the USB-C port, several USB devices are discovered and configured. These peripheral devices are created for TouchBack and InkBack. As shown in the following table, the peripheral devices can be viewed in Device Manager, which will show duplicate names for some devices, as shown in the following table.
-
-
-|**Peripheral**| **Listing in Device Manager** |
-| ---------------------------- |------------- | ------------------------------|
-| Human interface devices | HID-compliant consumer control device HID-compliant pen HID-compliant pen (duplicate item) HID-compliant pen (duplicate item) HID-compliant touch screen USB Input Device USB Input Device (duplicate item) |
-| Keyboards | Standard PS/2 keyboard |
-| Mice and other pointing devices | HID-compliant mouse |
-| USB controllers | Generic USB hub USB composite device |
-
-## Connecting video-in to Surface Hub 2S
-
-You can input video to Surface Hub 2S using USB-C or HDMI, as indicated in the following table.
-
-### Surface Hub 2S video-in settings
-
-| **Signal Type** | **Resolution** | **Frame rate** | **HDMI** | **USB-C** |
-| --------------- | -------------- | -------------- | -------- | --------- |
-| PC | 640 x 480 | 60 | X | X |
-| PC | 720 x 480 | 60 | X | X |
-| PC | 1024 x 768 | 60 | X | X |
-| PC | 1920 x 1080 | 60 | X | X |
-| PC | 3840x2560 | 30 | X | X |
-| HDTV | 720p | 60 | X | X |
-| HDTV | 1080p | 60 | X | X |
-| 4K UHD | 3840x2560 | 30 | X | X |
-
-> [!NOTE]
-> The 4K UHD resolution (3840×2560) is only supported when connecting to ports on the compute module. It is not supported on the “guest” USB ports located on the left, top, and right sides of the device.
-
-> [!NOTE]
-> Video from a connected external PC may appear smaller when displayed on Surface Hub 2S.
-
-## Mirroring Surface Hub 2S display on another device
-
-You can output video to another display using MiniDP, as indicated in the following table.
-
-### Surface Hub 2S video-out settings
-
-| **Signal Type** | **Resolution** | **Frame rate** | **MiniDP** |
-| --------------- | -------------- | -------------- | ---------- |
-| PC | 640 x 480 | 60 | X |
-| PC | 720 x 480 | 60 | X |
-| PC | 1024 x 768 | 60 | X |
-| PC | 1920 x 1080 | 60 | X |
-| PC | 3840 x 2560 | 60 | X |
-| HDTV | 720p | 60 | X |
-| HDTV | 1080p | 60 | X |
-| 4K UHD | 3840 x 2560 | 60 | X |
-
-
-
-Surface Hub 2S includes a MiniDP video-out port for projecting visual content from Surface Hub 2S to another display. If you plan to use Surface Hub 2S to project to another display, note the following recommendations:
-
-- **Keyboard required.** Before you begin, you’ll need to connect either a wired or Bluetooth-enabled external keyboard to Surface Hub 2S. Note that unlike the original Surface Hub, a keyboard for Surface Hub 2S is sold separately and is not included in the shipping package.
-- **Set duplicate mode.** Surface Hub 2S supports video-out in duplicate mode only. However, you will still need to manually configure the display mode when you connect for the first time:
- 1. Enter the **Windows logo key** + **P**, which opens the Project pane on the right side of Surface Hub 2S, and then select **Duplicate** mode.
- 2. When you’re finished with your Surface Hub 2S session, select **End Session**. This ensures that the duplicate setting is saved for the next session.
-- **Plan for different aspect ratios.** Like other Surface devices, Surface Hub 2S uses a 3:2 display aspect ratio (the relationship between the width and the height of the display). Projecting Surface Hub 2S onto displays with different aspect ratios is supported. Note however that because Surface Hub 2S duplicates the display, the MiniDP output will also only display in a 3:2 aspect ratio, which may result in letterboxing or curtaining depending on the aspect ratio of the receiving display.
-
-> [!NOTE]
-> if your second monitor uses a 16:9 aspect ratio (the predominant ratio for most TV monitors), black bars may appear on the left and right sides of the mirrored display. If this occurs, you may wish to inform your users that there is no need to adjust the second display.
-
-## Selecting cables
-
-Note the following recommendations:
-
-- **USB.** USB 3.1 Gen 2 cables.
-- **MiniDP.** DisplayPort cables certified for up to 3 meters in length.
-- **HDMI.** If a long cable is necessary, HDMI is recommended due to the wide availability of cost-effective, long-haul cables with the ability to install repeaters if needed.
-
-> [!NOTE]
-> Most DisplayPort sources will automatically switch to HDMI signaling if HDMI is detected.
-
-## Wirelessly connect to Surface Hub 2S
-
-Windows 10 natively supports Miracast, which lets you wireless connect to Surface Hub 2S.
-
-### To connect using Miracast:
-
-1. On your Windows 10 device, enter **Windows logo key** + **K**.
-2. In the Connect window, look for the name of your Surface Hub 2S in the list of nearby devices. You can find the name of your Surface Hub 2S in the bottom left corner of the display.
-3. Enter a PIN if your system administrator has enabled the PIN setting for Miracast connections. This requires you to enter a PIN number when you connect to Surface Hub 2S for the first time.
-
-> [!NOTE]
->If you do not see the name of the Surface Hub 2S device as expected, it’s possible the previous session was prematurely closed. If so, sign into Surface Hub 2S directly to end the previous session and then connect from your external device.
-
-## Connecting peripherals to Surface Hub 2S
-
-### Bluetooth accessories
-
-You can connect the following accessories to Surface Hub-2S using Bluetooth:
-
-- Mice
-- Keyboards
-- Headsets
-- Speakers
-- Surface Hub 2 pens
-
-> [!NOTE]
-> After you connect a Bluetooth headset or speaker, you might need to change the default microphone and speaker settings. For more information, see [**Local management for Surface Hub settings**](https://docs.microsoft.com/surface-hub/local-management-surface-hub-settings).
diff --git a/devices/surface-hub/surface-hub-2s-custom-install.md b/devices/surface-hub/surface-hub-2s-custom-install.md
deleted file mode 100644
index c86ac8b4b3..0000000000
--- a/devices/surface-hub/surface-hub-2s-custom-install.md
+++ /dev/null
@@ -1,86 +0,0 @@
----
-title: "Customize wall mount of Surface Hub 2S"
-description: "Learn how to perform a custom install of Surface Hub 2S."
-keywords: separate values with commas
-ms.prod: surface-hub
-ms.sitesec: library
-author: greg-lindsay
-ms.author: greglin
-manager: laurawi
-audience: Admin
-ms.topic: article
-ms.date: 06/20/2019
-ms.localizationpriority: Medium
----
-
-# Customize wall mount of Surface Hub 2S
-
-If you’re not using certified mounting solutions, you can mount Surface Hub 2S using readily available retail hardware.
-
-## Set wall mount measurements
-
-Surface Hub 2S recommended mounting measurements:
-
-|**Item**|**Description**|**Notes**|
-|:------ |:------------- |:------- |
-|**Height from bottom of Surface Hub 2S**| 1026.5 mm (40.41”) | Recommended |
-|**Height from top of Surface Hub 2S**| 1767.2 mm (69.57”) | Recommended |
-|**Height from center of mount**| 1397 mm (55”) | Recommended |
-
-1. Measure 1026.5 mm (40.41”) from the floor level to set the recommended minimum height.
-2. Measure 1767.2 mm (69.57”) from the floor level to set the recommended top height.
-
-
-
-3. Measure 1397 mm (55”) mm from the floor level to set the recommended center height.
-
-
-
-## Obstruction free mounting
-
-In addition to the visible ports on the sides of the device, certain integrated components must remain free of obstruction in order to function correctly. These include the Bluetooth, Wi-Fi, occupancy, and mic sensors as well thermal cooling vents.
- Keep out zones
-
-|**Item**|**Description**|**Notes**|
-|:---- |:----------- |:----- |
-|**Access**| Ensure unimpeded access to input/output ports, the compute cartridge, Bluetooth radio, Bluetooth sensor, Wi-Fi radio, Wi-Fi sensor, occupancy sensor. | See Figure 1. |
-|**Air flow**| Avoid blocking inlet and outlet air vent zones. | See Figure 2 |
-|**Audio**| Avoid blocking audio exit zone on rear of Surface Hub 2S. | See Figure 2. |
-
-
-***Figure 1. Keep out zones for Surface Hub 2S components***
-
-
-***Figure 2. Avoid blocking thermal inlet/outlet and audio exit zones. ***
-
-The removable compute cartridge containing the I/O ports must remain free of any obstructions or impediments of any kind.
-
-
-***Figure 3.View of compute cartridge on the underside of Surface Hub 2s.***
-
-
-***Figure 4. Unimpeded removal of compute cartridge***
-
-## Selecting a mounting system
-
-Surface Hub 2S uses a 350 mm x 350 mm mounting framework that meets most — but not all — of the criteria listed in the VESA Flat Display Mounting Interface Standard. You can install Surface Hub 2S using any of various off-the-shelf display brackets designed to accommodate displays that diverge from exact VESA specifications, as shown below.
-
-On the back of Surface Hub 2S, you’ll find a square pattern of four M6 x 1.0 threaded holes centered on the circular bump (565 mm in diameter). Attach your mount using four M6 x 1.0–12 mm-long metric bolts. Or, depending on preference, you can use longer bolts up to a maximum of 20 mm.
-Important considerations for mounting systems
-
-|**Item**|**Description**|**Notes**|
-|:------ |:------------- |:------- |
-|**Strength**| Only choose mounts that can safely support devices of at least 28 kg (62 lbs.). | Required |
-|**Stiffness**| Avoid flexible display mounts that can diminish the interactive pen and touch use experience. Most TV mounts are not designed to support touch displays. | Recommended |
-|**Depth**| Keep the device mounted tightly to the wall especially in corridors and along circulation paths within rooms.| Recommended |
-|**Versatility**| Ensure your mounting solution remains hidden from view in both the existing landscape mode and any potential portrait mode (subject to future availability). | Recommended |
-
-
-***Figure 5. Surface Hub 2S mounting configuration***
-
-## Mounting methods compatible with Surface Hub 2S
-
-Surface Hub 2S is compatible with mounts that allow you to place it at angles of 10-70 degrees from the vertical plane. Rail mounts typically have multiple holes and a set of slots, enabling compatibility across a wide range of displays. A rail attached to the wall and two mounts attached to the display enable you to securely install Surface Hub 2S to a wall. When evaluating rail mounts for compatibility, ensure they meet versatility requirements listed earlier.
-
-
-***Figure 6. Surface Hub 2S rail mounts***
diff --git a/devices/surface-hub/surface-hub-2s-deploy-apps-intune.md b/devices/surface-hub/surface-hub-2s-deploy-apps-intune.md
deleted file mode 100644
index 77fe0fa1ca..0000000000
--- a/devices/surface-hub/surface-hub-2s-deploy-apps-intune.md
+++ /dev/null
@@ -1,58 +0,0 @@
----
-title: "Deploy apps to Surface Hub 2S using Intune"
-description: "Learn how you can deploy apps to Surface Hub 2S using Intune."
-keywords: separate values with commas
-ms.prod: surface-hub
-ms.sitesec: library
-author: greg-lindsay
-ms.author: greglin
-manager: laurawi
-audience: Admin
-ms.topic: article
-ms.date: 06/20/2019
-ms.localizationpriority: Medium
----
-
-# Deploy apps to Surface Hub 2S using Intune
-
-You can install additional apps to fit your team or organization's needs.
-
-## Developer guidelines
-
-- Surface Hub only runs [Universal Windows Platform (UWP) apps](https://msdn.microsoft.com/windows/uwp/get-started/whats-a-uwp). Apps created using the [Desktop App Converter](https://docs.microsoft.com/windows/uwp/porting/desktop-to-uwp-run-desktop-app-converter) will not run on Surface Hub.
-- Apps must be targeted for the [Universal device family](https://msdn.microsoft.com/library/windows/apps/dn894631) or Windows Team device family.
-- Surface Hub only supports [offline-licensed apps](https://docs.microsoft.com/microsoft-store/distribute-offline-apps) from [Microsoft Store for Business](https://businessstore.microsoft.com/store).
-- By default, apps must be Store-signed to be installed. During testing and development, you can also choose to run developer-signed UWP apps by placing the device in developer mode.
-- When developing and submitting apps to the Microsoft Store, set Device family availability and Organizational licensing options to ensure that apps are available to run on Surface Hub.
-- You need admin credentials to install apps on Surface Hub. Designed for use in meeting rooms and other shared spaces, Surface Hub prevents regular users from accessing the Microsoft Store to download and install apps.
-
-## Deployment guidelines
-
-You can deploy Universal Windows Platform (UWP) apps to Surface Hub 2S using Intune, easing app deployment to devices.
-
-1. To deploy apps, enable MDM for your organization. In the Intune portal, select **Intune** as your MDM Authority (recommended).
-
- 
-
-2. Enable the Microsoft Store for Business in Intune. Open Intune, select **Client apps** > **Microsoft Store for Business.**
-
- 
-
-3. In Intune open **Microsoft Store for Business** and select **Settings** > **Distribute** > **Management tools**. Choose **Microsoft Intune** as your management tool.
-
- 
-
-4. In Microsoft Store for Business, select **Settings** > **Shop** > **Shopping Experience**, and then select **Show offline apps**. Offline apps refer to apps that can be synced to Intune and centrally deployed to a device.
-5. After enabling Offline shopping, you can acquire offline licenses for apps that you can sync to Intune and deploy as Device licensing.
-6. In **Intune** > **Client apps** > **Microsoft Store for Business**, select **Sync**.
-7. In the Client apps page, search for the app in the apps list. Assign the apps to the desired device group or groups. Select **Assignments** > **Add group**.
-
-
-
-8. Under assignment type, choose **Required**.
-
-
-
-9. For the selected groups, choose **Device licensing** and then select **OK** and save the assignment.
-
-
diff --git a/devices/surface-hub/surface-hub-2s-deploy-checklist.md b/devices/surface-hub/surface-hub-2s-deploy-checklist.md
deleted file mode 100644
index 08421ad2f6..0000000000
--- a/devices/surface-hub/surface-hub-2s-deploy-checklist.md
+++ /dev/null
@@ -1,65 +0,0 @@
----
-title: "Surface Hub 2S deployment checklists"
-description: "Verify your deployment of Surface Hub 2S using pre- and post-deployment checklists."
-keywords: separate values with commas
-ms.prod: surface-hub
-ms.sitesec: library
-author: greg-lindsay
-ms.author: greglin
-manager: laurawi
-audience: Admin
-ms.topic: article
-ms.date: 06/20/2019
-ms.localizationpriority: Medium
----
-
-# Surface Hub 2S deployment checklists
-
-## Surface Hub 2S pre-deployment checklist
-
-|**Item**|**Response**|
-|:------ |:------ |
-|**Device account name**| |
-|**Device account UPN**| |
-|**ActiveSync Policy**| |
-|**Calendar processing configuration completed**| ☐ Yes ☐ No |
-|**Device-friendly name**| |
-|**Device host name**| |
-|**Affiliation**| ☐ None ☐ Active Directory affiliation ☐ Azure Active Directory |
-|**Microsoft Teams Mode**| ☐ Mode 0 ☐ Mode 1 ☐ Mode 2 |
-|**Device Management**| ☐ Yes, Microsoft Intune ☐ Yes, other mobile device manager [MDM] ☐ None |
-|**Proxy**| ☐ Automatic configuration ☐ Proxy server ☐ Proxy auto-config (PAC) file |
-|**Proxy authentication**| ☐ Device account credentials ☐ Prompt for credentials |
-|**Password rotation**| ☐ On ☐ Off |
-|**Skype for Business additional domain names (on-premises only)**| |
-|**Session timeout time**| |
-|**Session timeout action**| ☐ End session ☐ Allow resume |
-|**My meetings and files**| ☐ Enabled ☐ Disabled |
-|**Lock screen timeout**| |
-|**Sleep idle timeout**| |
-|**Bluetooth**| ☐ On ☐ Off |
-|**Use only BitLocker USB drives**| ☐ On ☐ Off |
-|**Install additional certificates (on-premises only)**| |
-|**Windows update**| ☐ Windows Update for Business ☐ Windows Server Update Services [WSUS] |
-|**Surface app speaker setting**| ☐ Rolling stand ☐ Wall-mounted |
-|**IP Address**| ☐ Wired — DHCP ☐ Wired — DHCP reservation ☐ Wireless — DHCP ☐ Wireless — DHCP reservation |
-
-## Surface Hub 2S post-deployment checklist
-
-|**Check**|**Response**|
-|:------|:---------|
-|**Device account syncing**| ☐ Yes ☐ No |
-|**Bitlocker key**| ☐ Saved to file (no affiliation) ☐ Saved in Active Directory (AD affiliation) ☐ Saved in Azure AD (Azure AD affiliation) |
-|**Device OS updates**| ☐ Completed |
-|**Windows Store updates**| ☐ Automatic ☐ Manual |
-|**Microsoft Teams scheduled meeting**| ☐ Confirmation email received ☐ Meeting appears on start screen ☐ One-touch join functions ☐ Able to join audio ☐ Able to join video ☐ Able to share screen ||
-|**Skype for Business scheduled meeting**| ☐ Confirmation email received ☐ Meeting appears on start screen ☐ One-touch join functions correctly ☐ Able to join audio ☐ Able to join video ☐ Able to share screen ☐ Able to send/receive IM |
-|**Scheduled meeting when already invited**| ☐ Meeting declined |
-|**Microsoft Teams ad-hoc meeting**| ☐ Invite other users work ☐ Able to join audio ☐ Able to join video ☐ Able to share screen |
-|**Skype for Business scheduled meeting**| ☐ Invite other users work ☐ Able to join audio ☐ Able to join video ☐ Able to share screen ☐ Able to send/receive IM |
-|**Microsoft Whiteboard**| ☐ Launch from Welcome / Start screen ☐ Launch from Microsoft Teams |
-|**Incoming Skype/Teams call**| ☐ Able to join audio ☐ Able to join video ☐ Able to share screen ☐ Able to send/receive IM (Skype for Business only) |
-|**Incoming live video streams**| ☐ Maximum 2 (Skype for Business) ☐ Maximum 4 (Microsoft Teams) |
-|**Microsoft Teams Mode 0 behavior**| ☐ Skype for Business tile on Welcome/Start screen ☐ Can join scheduled Skype for Business meetings (Skype UI) ☐ Can join scheduled Teams meetings (Teams UI) |
-|**Microsoft Teams Mode 1 behavior**| ☐ Teams tile on Welcome/Start screen ☐ Can join scheduled Skype for Business meetings (Skype UI) ☐ Can join scheduled Teams meetings (Teams UI) |
-|**Microsoft Teams Mode 2 behavior**| ☐ Teams tile on Welcome / Start screen ☐ Can join scheduled Teams meetings ☐ Fail to join Skype for Business meetings |
diff --git a/devices/surface-hub/surface-hub-2s-deploy.md b/devices/surface-hub/surface-hub-2s-deploy.md
deleted file mode 100644
index 87908ed944..0000000000
--- a/devices/surface-hub/surface-hub-2s-deploy.md
+++ /dev/null
@@ -1,66 +0,0 @@
----
-title: "Create provisioning packages for Surface Hub 2S"
-description: "This page describes how to deploy Surface Hub 2S using provisioning packages and other tools."
-keywords: separate values with commas
-ms.prod: surface-hub
-ms.sitesec: library
-author: greg-lindsay
-ms.author: greglin
-manager: laurawi
-audience: Admin
-ms.topic: article
-ms.date: 06/20/2019
-ms.localizationpriority: Medium
----
-
-# Create provisioning packages for Surface Hub 2S
-
-You can use Windows Configuration Designer (WCD) to create provisioning packages to automate the deployment process of Surface Hub 2S. Use provisioning packages to add certificates, configure proxies, set up device administrators and device accounts. You can also use provisioning packages along with a configuration file to deploy multiple Surface Hubs with a single USB thumb drive.
-
-### Install Windows Configuration Designer
-
-Install Windows Configuration Designer from the Windows Assessment and Deployment Kit (ADK) for Windows 10. Download and install the [ADK for Windows 10, version 1703](https://go.microsoft.com/fwlink/p/?LinkId=845542). For more information, see [Download and install the Windows ADK](https://docs.microsoft.com/windows-hardware/get-started/adk-install).
-
-### Add certificates
-
-You can import Certificate Authority certificates to Surface Hub 2S.
-To add certificates to Surface Hub 2S, you need a copy of each certificate as X.509 in .cer format. You cannot import .crt, .pfx or other container formats. Certificates must be imported into Windows Configuration Designer and arranged by hierarchy:
-
- 
-
-### Configure proxy during OOBE
-
-In Windows Configuration Designer, go to the Configure proxy settings tab and enter the appropriate settings as shown below.
-
- 
-
-> [!NOTE]
-> When configuring proxy settings, turn off **Automatically detect settings** if you intend to use a setup script or a proxy server. You can use a setup script *or* a proxy server, not both.
-
-### Affiliate Surface Hub 2S with Azure Active Directory
-
-You can affiliate Surface Hub 2S with Azure Active Directory using a provisioning package:
-As an Azure Active Directory Global Administrator, you can join large numbers of new Windows devices to Azure Active Directory and Intune using a bulk token.
-
-To create a bulk token, give it a friendly name, configure the expiration date (maximum of 30 days) and use your Admin credentials to acquire the token as shown below:
-
- 
- 
- 
-
-### Provisioning multiple devices (.csv file)
-
-In addition to the provisioning package, you can use a Surface Hub configuration file to make it even easier to set up your devices. A Surface Hub configuration file contains a list of device accounts and friendly names for wireless projection. During first run, you get an option to choose a device account and friendly name from a configuration file.
-
-### To create a Surface Hub configuration file
-
-1. Using Microsoft Excel or another CSV editor, create a CSV file named: **SurfaceHubConfiguration.csv**
-2. Enter a list of device accounts and friendly names in this format:
-
-```
-,,
-```
-
-3. Save the file to the root of the USB thumb drive where you copied the PPKG file.
-
- 
diff --git a/devices/surface-hub/surface-hub-2s-install-mount.md b/devices/surface-hub/surface-hub-2s-install-mount.md
deleted file mode 100644
index 1ae4dcadb6..0000000000
--- a/devices/surface-hub/surface-hub-2s-install-mount.md
+++ /dev/null
@@ -1,36 +0,0 @@
----
-title: "Install and mount Surface Hub 2S"
-description: "Learn how to install and mount Surface Hub 2S."
-keywords: separate values with commas
-ms.prod: surface-hub
-ms.sitesec: library
-author: greg-lindsay
-ms.author: greglin
-manager: laurawi
-audience: Admin
-ms.topic: article
-ms.date: 06/20/2019
-ms.localizationpriority: Medium
----
-
-# Install and mount Surface Hub 2S
-
-Surface Hub 2S is designed for ease of mobility with a form factor that enables you to quickly install and begin using the device. Microsoft has partnered with Steelcase on the following certified mounting solutions: Roam Mobile Stand and Roam Wall Mount. Both fully integrate with the design of Surface Hub 2S, enabling unimpeded access to the compute cartridge, power, USB-A, USB-C, and other ports.
-
-You can mount Surface Hub 2S with the certified wall mount or the certified mobile stand, both developed in partnership with Steelcase. Both fully integrate with the design of Surface Hub 2S, enabling unimpeded access to the compute cartridge along with all I/O ports and power.
-
-For more information, see [Officially licensed third-party accessories](http://licensedhardware.azurewebsites.net/surface) and view installation demos from the Surface product team at [Steelcase mobile stand and APC battery set up](https://youtu.be/VTzdu4Skpkg).
-
- 
-
-If you’re not using licensed accessories, see [Customize wall mount of Surface Hub 2S](surface-hub-2s-custom-install.md).
-
-| 1. **Set up your mount first** | |
-|:------ |:-------- |
-| Leave your Surface Hub in the box until the mount is set up and mounting hardware is applied. Mount is not included. Your mount is sold separately. |  |
-| 2. **Attach hardware to the Surface Hub** | |
-| Mounting hardware and specific instructions are found in the box for your mount. |  |
-| 3. **Remove the instructional label before mounting.** | |
-| Get someone to help you lift and mount your Surface Hub. Make sure to hold and lift the Surface Hub from the bottom. |  |
-| 4. **Attach accessories and power on** | |
-| Install accessories and attach power cable as shown. See guides on the screen cling. Remove cling wrap from the screen. Press the power button to power on. |  |
diff --git a/devices/surface-hub/surface-hub-2s-manage-intune.md b/devices/surface-hub/surface-hub-2s-manage-intune.md
deleted file mode 100644
index c36d53f1f6..0000000000
--- a/devices/surface-hub/surface-hub-2s-manage-intune.md
+++ /dev/null
@@ -1,92 +0,0 @@
----
-title: "Manage Surface Hub 2S with Intune"
-description: "Learn how to update and manage Surface Hub 2S using Intune."
-keywords: separate values with commas
-ms.prod: surface-hub
-ms.sitesec: library
-author: greg-lindsay
-ms.author: greglin
-manager: laurawi
-audience: Admin
-ms.topic: article
-ms.date: 02/28/2020
-ms.localizationpriority: Medium
----
-
-# Manage Surface Hub 2S with Intune
-
-## Register Surface Hub 2S with Intune
-
-Surface Hub 2S allows IT administrators to manage settings and policies using a mobile device management (MDM) provider. Surface Hub 2S has a built-in management component to communicate with the management server, so there is no need to install additional clients on the device.
-
-### Manual registration
-
-1. Sign in as a local administrator on Surface Hub 2S and open the **Settings** app. Select **Surface Hub** > **Device management** and then select **+** to add.
-2. After authenticating, the device will automatically register with Intune.
-
- 
-
-### Auto registration — Azure Active Directory Affiliated
-
-During the initial setup process, when affiliating a Surface Hub with an Azure AD tenant that has Intune auto enrollment enabled, the device will automatically enroll with Intune. For more information, refer to [Intune enrollment methods for Windows devices](https://docs.microsoft.com/intune/enrollment/windows-enrollment-methods). Azure AD affiliation and Intune auto enrollment is required for the Surface Hub to be a "compliant device" in Intune.
-
-## Windows 10 Team Edition settings
-
-Select Windows 10 Team for preset device restriction settings for Surface Hub and Surface Hub 2S.
-
- 
-
-These settings include user experience and app behavior, Azure Log Analytics registration, Maintenance windows configuration, Session settings, and Miracast settings. For a complete list of available Windows 10 Team settings, see [SurfaceHub CSP](https://docs.microsoft.com/windows/client-management/mdm/surfacehub-csp).
-
-## Additional supported configuration service providers (CSPs)
-
-For additional supported CSPs, see [Surface Hub CSPs in Windows 10](https://docs.microsoft.com/windows/client-management/mdm/configuration-service-provider-reference#surfacehubcspsupport).
-
-## Quality of Service (QoS) settings
-
-To ensure optimal video and audio quality on Surface Hub 2S, add the following QoS settings to the device.
-
-### Microsoft Teams QoS settings
-
-|**Name**|**Description**|**OMA-URI**|**Type**|**Value**|
-|:------ |:------------- |:--------- |:------ |:------- |
-|**Audio Ports**| Audio Port range | ./Device/Vendor/MSFT/NetworkQoSPolicy/TeamsAudio/DestinationPortMatchCondition | String | 3478-3479 |
-|**Audio DSCP**| Audio ports marking | ./Device/Vendor/MSFT/NetworkQoSPolicy/TeamsAudio/DSCPAction | Integer | 46 |
-|**Video Port**| Video Port range | ./Device/Vendor/MSFT/NetworkQoSPolicy/TeamsVideo/DestinationPortMatchCondition | String | 3480 |
-|**Video DSCP**| Video ports marking | ./Device/Vendor/MSFT/NetworkQoSPolicy/TeamsVideo/DSCPAction | Integer | 34 |
-|**P2P Audio Ports**| Audio Port range | ./Device/Vendor/MSFT/NetworkQoSPolicy/TeamsP2PAudio/DestinationPortMatchCondition | String | 50000-50019 |
-|**P2P Audio DSCP**| Audio ports marking | ./Device/Vendor/MSFT/NetworkQoSPolicy/TeamsP2PAudio/DSCPAction | Integer | 46 |
-|**P2P Video Ports**| Video Port range | ./Device/Vendor/MSFT/NetworkQoSPolicy/TeamsP2PVideo/DestinationPortMatchCondition | String | 50020-50039 |
-|**P2P Video DSCP**| Video ports marking | ./Device/Vendor/MSFT/NetworkQoSPolicy/TeamsP2PVideo/DSCPAction | Integer | 34 |
-
-
-### Skype for Business QoS settings
-
-| Name | Description | OMA-URI | Type | Value |
-| ------------------ | ------------------- | ------------------------------------------------------------------------ | ------- | ------------------------------ |
-| Audio Ports | Audio Port range | ./Device/Vendor/MSFT/NetworkQoSPolicy/SfBAudio/SourcePortMatchCondition | String | 50000-50019 |
-| Audio DSCP | Audio ports marking | ./Device/Vendor/MSFT/NetworkQoSPolicy/SfBAudio/DSCPAction | Integer | 46 |
-| Audio Media Source | Skype App name | ./Device/Vendor/MSFT/NetworkQoSPolicy/SfBAudio/AppPathNameMatchCondition | String | Microsoft.PPISkype.Windows.exe |
-| Video Ports | Video Port range | ./Device/Vendor/MSFT/NetworkQoSPolicy/SfBVideo/SourcePortMatchCondition | String | 50020-50039 |
-| Video DSCP | Video ports marking | ./Device/Vendor/MSFT/NetworkQoSPolicy/SfBVideo/DSCPAction | Integer | 34 |
-| Video Media Source | Skype App name | ./Device/Vendor/MSFT/NetworkQoSPolicy/SfBVideo/AppPathNameMatchCondition | String | Microsoft.PPISkype.Windows.exe |
-
-> [!NOTE]
-> Both tables show default port ranges. Administrators may change the port ranges in the Skype for Business and Teams control panel.
-
-## Microsoft Teams Mode settings
-
-You can set the Microsoft Teams app mode using Intune. Surface Hub 2S comes installed with Microsoft Teams in mode 0, which supports both Microsoft Teams and Skype for Business. You can adjust the modes as shown below.
-
-### Modes:
-
-- Mode 0 — Skype for Business with Microsoft Teams functionality for scheduled meetings.
-- Mode 1 — Microsoft Teams with Skype for Business functionality for scheduled meetings.
-- Mode 2 — Microsoft Teams only.
-
-To set modes, add the following settings to a custom Device Configuration Profile.
-
-|**Name**|**Description**|**OMA-URI**|**Type**|**Value**|
-|:--- |:--- |:--- |:--- |:--- |
-|**Teams App ID**|App name|./Vendor/MSFT/SurfaceHub/Properties/VtcAppPackageId|String| Microsoft.MicrosoftTeamsforSurfaceHub_8wekyb3d8bbwe!Teams|
-|**Teams App Mode**|Teams mode|./Vendor/MSFT/SurfaceHub/Properties/SurfaceHubMeetingMode|Integer| 0 or 1 or 2|
diff --git a/devices/surface-hub/surface-hub-2s-manage-passwords.md b/devices/surface-hub/surface-hub-2s-manage-passwords.md
deleted file mode 100644
index accd5d7e84..0000000000
--- a/devices/surface-hub/surface-hub-2s-manage-passwords.md
+++ /dev/null
@@ -1,21 +0,0 @@
----
-title: "Manage device account password rotation"
-description: "Learn how to configure Surface Hub 2S on-premises accounts with PowerShell"
-keywords: separate values with commas
-ms.prod: surface-hub
-ms.sitesec: library
-author: greg-lindsay
-ms.author: greglin
-manager: laurawi
-audience: Admin
-ms.topic: article
-ms.date: 06/20/2019
-ms.localizationpriority: Medium
----
-# Manage device account password rotation
-
-You can configure Surface Hub 2S to automatically change a device account password without requiring you to manually update the device account information.
-
-If you turn on Password Rotation, Surface Hub 2S changes the password every 7 days. The automatically generated passwords contain 15-32 characters including a combination of uppercase and lowercase letters, numbers, and special characters.
-
-Passwords do not change during a meeting. If Surface Hub 2S is turned off, it attempts to change the password immediately when turned on or every 10 minutes until successful.
diff --git a/devices/surface-hub/surface-hub-2s-onprem-powershell.md b/devices/surface-hub/surface-hub-2s-onprem-powershell.md
deleted file mode 100644
index 6a0553f72e..0000000000
--- a/devices/surface-hub/surface-hub-2s-onprem-powershell.md
+++ /dev/null
@@ -1,66 +0,0 @@
----
-title: "Configure Surface Hub 2S on-premises accounts with PowerShell"
-description: "Learn how to configure Surface Hub 2S on-premises accounts with PowerShell"
-keywords: separate values with commas
-ms.prod: surface-hub
-ms.sitesec: library
-author: greg-lindsay
-ms.author: greglin
-manager: laurawi
-audience: Admin
-ms.topic: article
-ms.date: 06/20/2019
-ms.localizationpriority: Medium
----
-
-# Configure Surface Hub 2S on-premises accounts with PowerShell
-
-## Connect to Exchange Server PowerShell
-
-> [!IMPORTANT]
-> You'll need the Fully Qualified Domain Name (FQDN) for the Client Access service of the on-premises Exchange server for some of these cmdlets.
-
-```PowerShell
-$ExchServer = Read-Host "Please Enter the FQDN of your Exchange Server"
-$ExchSession = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri http://$ExchServer/PowerShell/ -Authentication Kerberos -Credential (Get-Credential)
-Import-PSSession $ExchSession
-```
-
-## Create the device account
-
-```PowerShell
-New-Mailbox -UserPrincipalName Hub01@contoso.com -Alias Hub01 -Name "Hub 01" -Room -EnableRoomMailboxAccount $true -RoomMailboxPassword (ConvertTo-SecureString -String -AsPlainText -Force)
-```
-
-## Set automatic calendar processing
-
-```PowerShell
-Set-CalendarProcessing -Identity "HUB01@contoso.com" -AutomateProcessing AutoAccept -AddOrganizerToSubject $false –AllowConflicts $false –DeleteComments $false -DeleteSubject $false -RemovePrivateProperty $false -AddAdditionalResponse $true -AdditionalResponse "This room is equipped with a Surface Hub"
-```
-
-## Enable the Skype for Business object
-
-> [!NOTE]
-> It is important that you know the FQDN of the Skype for Business Registrar Pool.
-
-```PowerShell
-Enable-CsMeetingRoom -Identity Contoso\HUB01 -SipAddressType emailaddress -RegistrarPool SfbIEFE01.contoso.local
-```
-
-## Mobile Device Mailbox Policy
-
-You may need to create a Mobile Device Mailbox Policy (also known as ActiveSync Policy) to allow your Surface Hub to connect to your online or on-premises environment.
-
-## Create a Surface Hub mobile device mailbox policy
-
-```PowerShell
-New-MobileDeviceMailboxPolicy -Name “Surface Hubs” -PasswordEnabled $false
-```
-
-## Additional settings
-
-It is recommended to add a MailTip to Surface Hub rooms so users remember to make the meeting a Skype for Business or Teams meeting:
-
-```PowerShell
-Set-Mailbox "Surface Hub 2S" -MailTip "This is a Surface Hub room. Please make sure this is a Microsoft Teams meeting."
-```
diff --git a/devices/surface-hub/surface-hub-2s-onscreen-display.md b/devices/surface-hub/surface-hub-2s-onscreen-display.md
deleted file mode 100644
index da4712505e..0000000000
--- a/devices/surface-hub/surface-hub-2s-onscreen-display.md
+++ /dev/null
@@ -1,39 +0,0 @@
----
-title: "Adjust Surface Hub 2S brightness, volume, and input"
-description: "Learn how to use the onscreen display to adjust brightness and other settings in Surface Hub 2S."
-keywords: separate values with commas
-ms.prod: surface-hub
-ms.sitesec: library
-author: greg-lindsay
-ms.author: greglin
-manager: laurawi
-audience: Admin
-ms.topic: article
-ms.date: 07/09/2019
-ms.localizationpriority: Medium
----
-# Adjust Surface Hub 2S brightness, volume, and input
-
-Surface Hub 2S provides an on-screen display for volume, brightness, and input control. The Source button functions as a toggle key to switch between the volume, brightness, and input control menus.
-
-## To show the on-screen display
-
-- Press and hold the **Source** button for 4 seconds.
-
- 
-
- When the on-screen display is visible, use one or more buttons to reach desired settings.
-
-## To adjust volume
-
-- Use the **Volume up/down** button to increase or decrease volume.
-
-## To adjust brightness
-
-1. Press the **Source** button again to switch to the brightness menu.
-2. Use the **Volume up/down** button to increase or decrease brightness.
-
-## To adjust input
-
-1. Press the **Source** button twice to switch to the Source menu.
-2. Use the **Volume up/down** button to switch between PC, HDMI, and USB-C inputs.
diff --git a/devices/surface-hub/surface-hub-2s-pack-components.md b/devices/surface-hub/surface-hub-2s-pack-components.md
deleted file mode 100644
index 2c713a0a21..0000000000
--- a/devices/surface-hub/surface-hub-2s-pack-components.md
+++ /dev/null
@@ -1,68 +0,0 @@
----
-title: "How to pack and ship your Surface Hub 2S for service"
-description: "Instructions for packing Surface Hub 2S components, replacing the Compute cartridge, and replacing the camera"
-keywords: pack, replace components, camera, compute cartridge
-ms.prod: surface-hub
-ms.sitesec: library
-author: greg-lindsay
-ms.author: greglin
-manager: laurawi
-audience: Admin
-ms.topic: article
-ms.date: 02/06/2019
-ms.localizationpriority: Medium
----
-
-# How to pack and ship your Surface Hub 2S for service
-
-If you replace your Surface Hub 2S, one of its components, or a related accessory, use the instructions in this article when you pack the device for shipment.
-
->[!IMPORTANT]
->When packing your device for shipment, make sure that you use the packaging in which your replacement device arrived.
-
-## How to pack your Surface Hub 2S 50”
-
-Use the following steps to pack your Surface Hub 2S 50" for shipment.
-
-
-| | | |
-| - | ----------------------------------------------------------------------------------------------------------------------------------------------- | ----- |
-| **1.** | Remove the pen and the camera. Do not pack them with the unit. |  |
-| **2.** | Remove the drive and the power cable. Do not pack them with the unit. Do not pack the Setup guide with the unit. |  |
-| **3.** | Unplug all cables, slide the cover sideways, and unscrew the locking screw of the Compute Cartridge. |  |
-| **4.** | Slide the Compute Cartridge out of the unit. |  |
-| **5.** | You will need the Compute Cartridge and a screwdriver. | |
-| **6.** | Remove the cover screw and the cover from the Compute Cartridge, and then remove the solid state drive (SSD). | |
-| **7.** | Replace the cover and slide the Compute Cartridge back into the unit. | |
-| **8.** | Re-fasten the locking screw and slide the cover into place. | |
-| **9.** | Remove any base or mounting hardware. Using two people, place the unit in the base of the shipping container. | |
-| **10.** | Replace the cover of the shipping container, and insert the four clips. | |
-| **11.** | Close the four clips. | |
-
-
-## How to replace and pack your Surface Hub 2S Compute Cartridge
-
-Use the following steps to remove the Surface Hub 2S Compute Cartridge, pack it for shipment, and install the new Compute Cartridge.
- 
-
-| | | |
-| - | ----------------------------------------------------------------------------------------------------------------------------------------------- | ----- |
-| **1.** | Unplug all cables, slide the cover sideways, and unscrew the locking screw of the Compute Cartridge. |  |
-| **2.** | Slide the Compute Cartridge out of the unit. |  |
-| **3.** | You will need the Compute Cartridge and a screwdriver. |  |
-| **4.** | Remove the cover screw and the cover from the Compute Cartridge, and then remove the solid state drive (SSD). When finished, replace the cover. |  |
-| **5.**| You will need the packaging fixtures that were used to package your replacement Compute Cartridge. |  |
-| **6.**| Place the old Compute Cartridge in the packaging fixtures. |  |
-| **7.** | Place the old Compute Cartridge and its packaging into the box that was used for the replacement Compute Cartridge. Reseal the box. | |
-| **8.**| Slide the replacement Compute Cartridge into the unit. |  |
-| **9.**| Fasten the locking screw and slide the cover into place |  |
-
-## How to replace your Surface Hub 2S Camera
-
-Use the following steps to remove the Surface Hub 2S camera and install the new camera.
-
-
-| | | |
-| - | ----------------------------------------------------------------------------------------------------------------------------------------------- | ----- |
-| **1.** | You will need the new camera and the two-millimeter allen wrench. | |
-| **2.** | Unplug the old camera from the unit. If needed, use the allen wrench to adjust the new camera. Plug the new camera into the unit. |  |
diff --git a/devices/surface-hub/surface-hub-2s-pen-firmware.md b/devices/surface-hub/surface-hub-2s-pen-firmware.md
deleted file mode 100644
index ce16a5cad3..0000000000
--- a/devices/surface-hub/surface-hub-2s-pen-firmware.md
+++ /dev/null
@@ -1,67 +0,0 @@
----
-title: "Update pen firmware on Surface Hub 2S"
-description: "This page describes how to update firmware for the Surface Hub 2 pen."
-keywords: separate values with commas
-ms.prod: surface-hub
-ms.sitesec: library
-author: greg-lindsay
-ms.author: greglin
-manager: laurawi
-audience: Admin
-ms.topic: article
-ms.date: 02/26/2020
-ms.localizationpriority: Medium
----
-
-# Update pen firmware on Surface Hub 2S
-
-You can update firmware on Surface Hub 2 pen from Windows Update for Business or by downloading the firmware update to a separate PC. Updated firmware is available from Windows Update beginning February 26, 2020.
-
-## Update pen firmware using Windows Update for Business
-
-This section describes how to update pen firmware via the automated maintenance cycles for Windows Update, configured by default to occur nightly at 3 a.m. You will need to plan for two maintenance cycles to complete before applying the update to the Surface Hub 2 pen. Alternately, like any other update, you can use Windows Server Update Services (WSUS) to apply the pen firmware. For more information, see [Managing Windows updates on Surface Hub](manage-windows-updates-for-surface-hub.md).
-
-1. Ensure the Surface Hub 2 pen is paired to Surface Hub 2S: Press and hold the **top** button until the white indicator LED light begins to blink.
-
-2. On Surface Hub, login as an Admin, open **Settings**, and then scan for new Bluetooth devices.
-3. Select the pen to complete the pairing process.
-4. Press the **top** button on the pen to apply the update. It may take up to two hours to complete.
-
-## Update pen firmware by downloading to separate PC
-
-You can update the firmware on Surface Hub 2 pen from a separate PC running Windows 10. This method also enables you to verify that the pen firmware has successfully updated to the latest version.
-
-1. Pair the Surface Hub 2 pen to your Bluetooth-capable PC: Press and hold the **top** button until the white indicator LED light begins to blink.
-
-2. On the PC, scan for new Bluetooth devices.
-3. Select the pen to complete the pairing process.
-4. Disconnect all other Surface Hub 2s pens before starting a new update.
-3. Download the [Surface Hub 2 Pen Firmware Update Tool](https://download.microsoft.com/download/8/3/F/83FD5089-D14E-42E3-AF7C-6FC36F80D347/Pen_Firmware_Tool.zip) to your PC.
-4. Run **PenCfu.exe.** The install progress is displayed in the tool. It may take several minutes to finish updating.
-
-
-## Check firmware version of Surface Hub 2 pen
-
-1. Run **get_version.bat** and press the **top** button on the pen.
-2. The tool will report the firmware version of the pen. Example:
- - Old firmware is 468.2727.368
- - New firmware is 468.2863.369
-
-## Command line options
-
-You can run Surface Hub 2 Pen Firmware Update Tool (PenCfu.exe) from the command line.
-
-1. Pair the pen to your PC and click the **top** button on the pen.
-2. Double click **PenCfu.exe** to initiate the firmware update. Note that the configuration file and the firmware image files must be stored in the same folder as the tool.
-3. For additional options, run **PenCfu.exe -h** to display the available parameters, as listed in the following table.
- - Example: PenCfu.exe -h
-4. Enter **Ctrl+C** to safely shut down the tool.
-
-
-
-| **Command** | **Description** |
-| -------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| -h help | Display tool command line interface help and exit. |
-| -v version | Display tool version and exit. |
-| -l log-filter | Set a filter level for the log file. Log messages have 4 possible levels: DEBUG (lowest), INFO, WARNING and ERROR (highest). Setting a log filter level filters log messages to only message with the same level or higher. For example, if the filter level is set to WARNING, only WARNING and ERROR messages will be logged. By default, this option is set to OFF, which disables logging. |
-| -g get-version | If specified, the tool will only get the FW version of the connected pen that matches the configuration file that is stored in the same folder as the tool.
\ No newline at end of file
diff --git a/devices/surface-hub/surface-hub-2s-phone-authenticate.md b/devices/surface-hub/surface-hub-2s-phone-authenticate.md
deleted file mode 100644
index f79bbca0d4..0000000000
--- a/devices/surface-hub/surface-hub-2s-phone-authenticate.md
+++ /dev/null
@@ -1,43 +0,0 @@
----
-title: "Configure password-less phone sign-in for Surface Hub 2S"
-description: "Learn how to simplify signing in to Surface Hub 2S using password-less phone sign-in on your mobile device."
-keywords: separate values with commas
-ms.prod: surface-hub
-ms.sitesec: library
-author: greg-lindsay
-ms.author: greglin
-manager: laurawi
-audience: Admin
-ms.topic: article
-ms.date: 06/20/2019
-ms.localizationpriority: Medium
----
-
-# Configure password-less phone sign-in for Surface Hub 2S
-
-Password-less phone sign-in simplifies signing-in to your meetings and files on Surface Hub 2S.
-
-> [!NOTE]
-> Password-less phone sign-in requires that your primary email address must match your UPN.
-
-## To set up password-less phone sign-in
-
-1. Download the [Microsoft Authenticator](https://www.microsoft.com/account/authenticator) app for iPhone or Android to your phone.
-2. From your PC, go to [https://aka.ms/MFASetup](https://aka.ms/MFASetup) , sign in with your account, and select **Next.**
-3. In the Additional security verification screen, select Mobile App and Use verification code, and then select **Setup**.
-
-## To configure mobile app
-
-1. In the Microsoft authenticator app on your phone, add an account, choose **Work or School Account**, and then scan the QR code displayed on your PC
-2. Send a notification to your phone and then approve the sign-in request.
-3. In the Authenticator app on your phone, use the drop-down menu next to your account and select **Enable phone sign-in**.
-4. If required, register your device with your organization and follow the on-screen instructions.
-
-## To sign in to Surface Hub
-
-1. On Surface Hub, sign into **My meetings and files** and select **Send notification** when prompted.
-2. Match the number displayed on your phone with the number displayed on Surface Hub to approve your sign-in request.
-3. If prompted, enter the PIN or biometric ID on your phone to complete sign-in.
-
-## Learn more
-For more information, see [Password-less phone sign-in with the Microsoft Authenticator app](https://docs.microsoft.com/azure/active-directory/authentication/howto-authentication-phone-sign-in).
diff --git a/devices/surface-hub/surface-hub-2s-port-keypad-overview.md b/devices/surface-hub/surface-hub-2s-port-keypad-overview.md
deleted file mode 100644
index 8a667d95ac..0000000000
--- a/devices/surface-hub/surface-hub-2s-port-keypad-overview.md
+++ /dev/null
@@ -1,43 +0,0 @@
----
-title: "Surface Hub 2S ports and keypad overview"
-description: "This page describes the ports, physical buttons, and configuration information essential for connecting to Surface Hub 2S."
-keywords: separate values with commas
-ms.prod: surface-hub
-ms.sitesec: library
-author: greg-lindsay
-ms.author: greglin
-manager: laurawi
-audience: Admin
-ms.topic: article
-ms.date: 06/20/2019
-ms.localizationpriority: Medium
----
-
-# Surface Hub 2S ports and keypad overview
-
-This page describes the ports, physical buttons, and configuration information essential for connecting to Surface Hub 2S whether via wired, Wi-Fi, or Bluetooth methods. It also includes best practice recommendations for key connectivity scenarios.
-
-> [!NOTE]
-> You can find the serial number on the outside of the packaging, on the display by the power cord, or by using the Surface app.
-
-The figure below shows the location of ports and physical buttons on a keypad attached to the underside of the device. The table includes detailed descriptions of each element.
-
- 
-
-## Port and keypad component reference
-
-|**Key**|**Component**|**Description**|**Key parameters**|
-|:--- |:--------- |:----------- |:-------------- |
-| 1 | **USB C** | **USB 3.1 Gen 1** Use as a walk-up port for plugging in peripherals such as thumb-drives. Guest ports are on each side of the device (4).
*NOTE: This is the recommended port for connecting an external camera. Additional camera mount features are incorporated into the design to help support retention of attached cameras.*
NOTE: TouchBack and video ingest are not supported on these ports. | Type C
15 W Port (5V/3A) |
-| 2 | **AC power** | **100-240 V input** Connect to standard AC power and Surface Hub 2S will auto switch to the local power standard such as110 volts in the US and Canada or 220 volts in the UK. | IEC 60320 C14 |
-| 3 | **DC power** | **24V DC input port** Use for connecting to mobile battery. | Xbox1 Dual barrel to Anderson connector |
-| 4 | **Ethernet** | **1000/100/10 Base-T** Use for providing a continuous connection in a corporate environment and related scenarios requiring maximum stability or capacity. | RJ45 |
-| 5 | **USB-A** | **USB 3.1 Gen 1** Use as a walk-up port for plugging in peripherals such as thumb-drives. | Type A 7.5 W Port (5V/1.5A) |
-| 6 | **USB-C** | **USB 3.1 Gen 1** Use as a walk-up port for connecting external PCs and related devices or plugging in peripherals such as thumb-drives.
*NOTE: This is the recommended input port for video, TouchBack, and InkBack.* | Type C 18 W Port (5V/3A, 9V/2A) |
-| 7 | **HDMI-in** | **HDMI 2.0, HDCP 2.2 /1.4** Use for multiple scenarios including HDMI-to-HDMI guest input. | Standard HDMI |
-| 8 | **Mini DP-out** | **Mini DP 1.2 output** Use for video-out scenarios such as mirroring the Surface Hub 2S display to a larger projector.
*NOTE: This supports a maximum resolution of 3840 x 2160 (4K UHD) @60Hz.* | Mini DP |
-| 9 | **Source** | Use to toggle among connected ingest sources — external PC, HDMI, and Mini DP modes. | n/a |
-| 10 | **Volume** | Use +/- to adjust audio locally on the device.
*NOTE: When navigating to the brightness control, use +/- on the volume slider to control display brightness.* | n/a |
-| 11 | **Power** | Power device on/off. Use also to navigate display menus and select items. | n/a |
-
- 
diff --git a/devices/surface-hub/surface-hub-2s-prepare-environment.md b/devices/surface-hub/surface-hub-2s-prepare-environment.md
deleted file mode 100644
index 5f10258934..0000000000
--- a/devices/surface-hub/surface-hub-2s-prepare-environment.md
+++ /dev/null
@@ -1,50 +0,0 @@
----
-title: "Prepare your environment for Surface Hub 2S"
-description: "Learn what you need to do to prepare your environment for Surface Hub 2S."
-keywords: separate values with commas
-ms.prod: surface-hub
-ms.sitesec: library
-author: greg-lindsay
-ms.author: greglin
-manager: laurawi
-audience: Admin
-ms.topic: article
-ms.date: 11/21/2019
-ms.localizationpriority: Medium
----
-
-# Prepare your environment for Surface Hub 2S
-
-## Office 365 readiness
-
-If you use Exchange Online, Skype for Business Online, Microsoft Teams, or Microsoft Whiteboard, and intend to manage Surface Hub 2S with Intune, first review the [Office 365 requirements for endpoints](https://docs.microsoft.com/office365/enterprise/office-365-endpoints).
-
-Office 365 endpoints help optimize your network by sending all trusted Office 365 network requests directly through your firewall, bypassing all additional packet-level inspection or processing. This feature reduces latency and your perimeter capacity requirements.
-
-Microsoft regularly updates the Office 365 service with new features and functionality, which may alter required ports, URLs, and IP addresses. To evaluate, configure, and stay up to date with changes, subscribe to the [Office 365 IP Address and URL Web service](https://docs.microsoft.com/office365/enterprise/office-365-ip-web-service).
-
-## Device affiliation
-
-Use Device affiliation to manage user access to the Settings app on Surface Hub 2S.
-With the Windows 10 Team Edition operating system (that runs on Surface Hub 2S), only authorized users can adjust settings using the Settings app. Since choosing the affiliation can impact feature availability, plan appropriately to ensure that users can access features as intended.
-
-> [!NOTE]
-> You can only set Device affiliation during the initial out-of-box experience (OOBE) setup. If you need to reset Device affiliation, you’ll have to repeat OOBE setup.
-
-## No affiliation
-
-No affiliation is like having Surface Hub 2S in a workgroup with a different local Administrator account on each Surface Hub 2S. If you choose No affiliation, you must locally save the [BitLocker Key to a USB thumb drive](https://docs.microsoft.com/windows/security/information-protection/bitlocker/bitlocker-key-management-faq). You can still enroll the device with Intune; however, only the local admin can access the Settings app using the account credentials configured during OOBE. You can change the Administrator account password from the Settings app.
-
-## Active Directory Domain Services
-
-If you affiliate Surface Hub 2S with on-premises Active Directory Domain Services, you need to manage access to the Settings app using a security group on your domain. This helps ensure that all security group members have permissions to change settings on Surface Hub 2S. Also note the following:
-
-- When Surface Hub 2S affiliates with your on-premises Active Directory Domain Services, the BitLocker key can be saved in the Active Directory Schema. For more information, see [Prepare your organization for BitLocker: Planning and policies](https://docs.microsoft.com/windows/security/information-protection/bitlocker/prepare-your-organization-for-bitlocker-planning-and-policies).
-- Your organization’s Trusted Root CAs are pushed to the same container in Surface Hub 2S, which means you don’t need to import them using a provisioning package.
-- You can still enroll the device with Intune to centrally manage settings on your Surface Hub 2S.
-
-## Azure Active Directory
-
-When you choose to affiliate your Surface Hub 2S with Azure Active Directory (Azure AD), any user in the Global Admins Security Group can sign in to the Settings app on Surface Hub 2S. Currently, no other group can be delegated to sign in to the Settings app on Surface Hub 2S.
-
-If you enabled Intune Automatic Enrollment for your organization, Surface Hub 2S will automatically enroll itself with Intune. The device’s BitLocker key is automatically saved in Azure AD. When affiliating Surface Hub 2S with Azure AD, single sign-on and Easy Authentication will not work.
diff --git a/devices/surface-hub/surface-hub-2s-quick-start.md b/devices/surface-hub/surface-hub-2s-quick-start.md
deleted file mode 100644
index 3d7f08641a..0000000000
--- a/devices/surface-hub/surface-hub-2s-quick-start.md
+++ /dev/null
@@ -1,46 +0,0 @@
----
-title: "Surface Hub 2S quick start"
-description: "View the quick start steps to begin using Surface Hub 2S."
-keywords: separate values with commas
-ms.prod: surface-hub
-ms.sitesec: library
-author: greg-lindsay
-ms.author: greglin
-manager: laurawi
-audience: Admin
-ms.topic: article
-ms.date: 06/20/2019
-ms.localizationpriority: Medium
----
-
-# Surface Hub 2S quick start
-
-## Unpack Surface Hub 2S
-
-1. Use the handles on each side of the box to move it to the space where you'll set it up.
-2. Before opening, remove the clips (4) on the front and back, and then lift the top off the box using the handles.
-3. In the base of the Surface Hub 2S, open the accessories box containing the setup guide, Surface Hub 2 pen, Surface Hub 2 camera, and the power cable.
-4. On the back of the Surface Hub, there's an instructional label showing you where to attach the mounting hardware. Install them in place and remove the label.
-
-See this video for more information about [unboxing and set up](https://youtu.be/fCrxdNXvru4).
-
-## Install and adjust pen
-
-1. Attach Surface Hub 2 pen magnetically to your preferred side of the device.
-
-
-
-2. To adjust pen pressure, open the Surface app on Surface Hub 2S, select Pen, and adjust the slider.
-
-
-
-## Install camera
-
-Remove the lens cling from the camera and attach it to the USB-C port on the top of the Surface Hub 2S.
-
-## Start Surface Hub 2S
-
-1. Insert the power cable into the back of the device and plug it into a power outlet. Run the cable through any cable guides on your mounting solution and remove the screen clang.
-2. To begin, press the power button on the bottom right.
-
-
diff --git a/devices/surface-hub/surface-hub-2s-recover-reset.md b/devices/surface-hub/surface-hub-2s-recover-reset.md
deleted file mode 100644
index 7493e10c3c..0000000000
--- a/devices/surface-hub/surface-hub-2s-recover-reset.md
+++ /dev/null
@@ -1,75 +0,0 @@
----
-title: "Reset and recovery for Surface Hub 2S"
-description: "Learn how to recover and reset Surface Hub 2S."
-keywords: separate values with commas
-ms.prod: surface-hub
-ms.sitesec: library
-author: greg-lindsay
-ms.author: greglin
-manager: laurawi
-audience: Admin
-ms.topic: article
-ms.date: 12/05/2019
-ms.localizationpriority: Medium
----
-
-# Reset and recovery for Surface Hub 2S
-
-If you encounter problems with Surface Hub 2S, you can reset the device to factory settings or restore by using a USB drive.
-
-To begin, sign in to Surface Hub 2S with admin credentials, open the **Settings** app, select **Update & security**, and then select **Recovery**.
-
-## Reset the device
-
-1. To reset the device, select **Get Started**.
-2. When the **Ready to reset this device** window appears, select **Reset**.
-
- >[!NOTE]
- >Surface Hub 2S reinstalls the operating system from the recovery partition. This may take up to one hour to complete.
-
-3. To reconfigure the device, run the first-time Setup program.
-4. If you manage the device using Microsoft Intune or another mobile device management solution, retire and delete the previous record, and then re-enroll the new device. For more information, see [Remove devices by using wipe, retire, or manually unenrolling the device](https://docs.microsoft.com/intune/devices-wipe).
-
-
-*Figure 1. Reset and recovery for Surface Hub 2S*
-
-## Recover Surface Hub 2S by using a USB recovery drive
-
-New in Surface Hub 2S, you can now reinstall the device by using a recovery image.
-
-### Recovery from a USB drive
-
-Using Surface Hub 2S, you can reinstall the device by using a recovery image. By doing this, you can reinstall the device to the factory settings if you lost the BitLocker key, or if you no longer have admin credentials to the Settings app.
-
->[!NOTE]
->Use a USB 3.0 drive with 8 GB or 16 GB of storage, formatted as FAT32.
-
-1. From a separate PC, download the .zip file recovery image from the [Surface Recovery website](https://support.microsoft.com/surfacerecoveryimage?devicetype=surfacehub2s) and then return to these instructions.
-1. Unzip the downloaded file onto the root of the USB drive.
-1. Connect the USB drive to any USB-C or USB-A port on Surface Hub 2S.
-1. Turn off the device:
- 1. While holding down the Volume down button, press the Power button.
- 1. Keep holding both buttons until you see the Windows logo.
- 1. Release the Power button but continue to hold the Volume until the Install UI begins.
-
- 
- **Figure 2. Volume and Power buttons**
-
-1. On the language selection screen, select the display language for your Surface Hub 2S.
-1. Select **Recover from a drive** and **Fully clean the drive**, and then select **Recover**. If you're prompted for a BitLocker key, select **Skip this drive**. Surface Hub 2S reboots several times and takes approximately 30 minutes to complete the recovery process.
-
-When the first-time setup screen appears,remove the USB drive.
-
-## Recover a locked Surface Hub
-
-At the end of a session, Surface Hub 2S may occasionally encounter an error during the cleanup of user and app data at the end of a session. If this occurs, the device automatically reboots and resumes the data cleanup. However, if this operation repeatedly fails, the device automatically locks to protect user data.
-
-**To unlock a Surface Hub 2S:**
-- Reset or recover the device from the Windows Recovery Environment. For more information, see [What is Windows RE?](https://technet.microsoft.com/library/cc765966.aspx)
-
-> [!NOTE]
-> To enter recovery mode, unplug the power cord and plug it in again three times.
-
-## Contact Support
-
-If you have questions or need help, you can [create a support request](https://support.microsoft.com/supportforbusiness/productselection).
diff --git a/devices/surface-hub/surface-hub-2s-secure-with-uefi-semm.md b/devices/surface-hub/surface-hub-2s-secure-with-uefi-semm.md
deleted file mode 100644
index 8d0768ba93..0000000000
--- a/devices/surface-hub/surface-hub-2s-secure-with-uefi-semm.md
+++ /dev/null
@@ -1,68 +0,0 @@
----
-title: "Secure and manage Surface Hub 2S with SEMM"
-description: "Learn more about securing Surface Hub 2S with SEMM."
-keywords: separate values with commas
-ms.prod: surface-hub
-ms.sitesec: library
-author: greg-lindsay
-ms.author: greglin
-manager: laurawi
-audience: Admin
-ms.topic: article
-ms.date: 06/20/2019
-ms.localizationpriority: Medium
----
-
-# Secure and manage Surface Hub 2S with SEMM and UEFI
-
-New in Surface Hub 2S, you can use SEMM to manage the UEFI setting of the device.
-Use the Microsoft Surface UEFI Configurator to control the following components:
-
-- Wired LAN
-- Cameras
-- Bluetooth
-- Wi-Fi
-- Occupancy sensor
-
-Use the Microsoft Surface UEFI Configurator to turn on or off the following UEFI settings:
-
-- Boot
-
- - IPv6 for PXE Boot
- - Alternate Boot
- - Boot Order Lock
- - USB Boot
-- UEFI Front Page
-
- - Devices
- - Boot
- - Date/Time
-
-## Create UEFI configuration image
-
-Unlike other Surface devices, you cannot use an MSI file or a Win PE image to apply these settings on Surface Hub 2S. Instead, you need to create a USB image to load into the device. To create a Surface Hub 2S UEFI configuration image, download and install the latest version of the Microsoft Surface UEFI Configurator from the [Surface Tools for IT](https://www.microsoft.com/download/details.aspx?id=46703) page in the Microsoft Download Center. For more information about using UEFI and SEMM, see [Microsoft Surface Enterprise Management Mode](https://docs.microsoft.com/surface/surface-enterprise-management-mode).
-
-## To configure UEFI on Surface Hub 2S
-
-1. Start the UEFI Configurator and on the first screen, choose **Configuration Package**.
-
-2. To add the certificate to your package, you must have a valid certificate with the private key in a .pfx file format to sign and protect the package. Select **+ Certificate Protection.**
-
-3. Enter the certificate’s private key’s password.
-
-4. After importing the private key, continue creating the package.
-
-5. Choose **Hub** and **Surface Hub 2S** as the target for the UEFI configuration package.
-
-6. Choose the components and settings you want to activate or deactivate on Surface Hub 2S.
-
-7. Use the USB option to export the file.
-
-8. Insert and choose the USB drive you’d like to use for this package. The USB drive will be formatted and you lose any information you have on it.
-
-9. Upon successful creation of the package, the Configurator will display the last two characters of your certificate’s thumbprint. You need these characters when you import to the configuration to Surface Hub 2S.
-
-
-## To boot into UEFI
-
-Turn off Surface Hub 2S. Press and hold the **Volume Up** button and press the **Power** Button. Keep holding the Volume Up button until the UEFI menu appears.
diff --git a/devices/surface-hub/surface-hub-2s-setup.md b/devices/surface-hub/surface-hub-2s-setup.md
deleted file mode 100644
index 08318020fb..0000000000
--- a/devices/surface-hub/surface-hub-2s-setup.md
+++ /dev/null
@@ -1,100 +0,0 @@
----
-title: "First time Setup for Surface Hub 2S"
-description: "Learn how to complete first time Setup for Surface Hub 2S."
-keywords: separate values with commas
-ms.prod: surface-hub
-ms.sitesec: library
-author: greg-lindsay
-ms.author: greglin
-manager: laurawi
-audience: Admin
-ms.topic: article
-ms.date: 07/03/2019
-ms.localizationpriority: Medium
----
-
-# First time Setup for Surface Hub 2S
-
-When you first start Surface Hub 2S, the device automatically enters first time Setup mode to guide you through account configuration and related settings.
-
-## Configuring Surface Hub 2S account
-
-1. **Configure your locale.** Enter region, language, keyboard layout and time zone information. Select **Next**.
-
- 
-1. **Connect to a wireless network.** Choose your preferred wireless network and select **Next.**
-
-- This option is not shown if connected using an Ethernet cable.
-- You cannot connect to a wireless network in hotspots (captive portals) that redirect sign-in requests to a provider’s website.
-
-3. **Enter device account info.** Use **domain\user** for on-premises and hybrid environments and **user\@example.com** for online environments. Select **Next.**
-
- 
-1. **Enter additional info.** If requested, provide your Exchange server address and then select **Next.**
-
- 
-
-1. **Name this device.** Enter a name for your device or use the suggested one based on your account’s display name and user principle name [UPN]. **Select Next**.
-
-- The **Friendly name** is visible on the bottom left corner of Surface Hub 2S and is shown when projecting to the device.
-
-- The **Device name** identifies the device when affiliated with Active Directory or Azure Active Directory, and when enrolling the device with Intune.
-
- 
-
-## Configuring device admin accounts
-
-You can only set up device admins during first time Setup. For more information, refer to [Surface Hub 2S device affiliation](https://docs.microsoft.com/surface-hub/surface-hub-2s-prepare-environment#device-affiliation).
-
- In the **Setup admins for this device** window, select one of the following options: Active Directory Domain Services, Azure Active Directory, or Local admin.
-
- 
-
-### Active Directory Domain Services
-
-1. Enter the credentials of a user who has permissions to join the device to Active Directory.
-
- 
-
-2. Select the Active Directory Security Group containing members allowed to log on to the Settings app on Surface Hub 2S.
-
- 
-1. Select **Finish**. The device will restart.
-
-### Azure Active Directory
-
-When choosing to affiliate your device with Azure Active Directory, the device will immediately restart and display the following page. Select **Next**.
-
-
-
-1. Enter the email address or UPN of an account **with Intune Plan 1** or greater and then select **Next.**
-
- 
-
-2. If redirected, authenticate using your organization’s sign-in page and provide additional logon information if requested. The device will restart.
-
-## Local Administrator account
-
-- Enter a username and password for your local admin. The device will restart.
-
- 
-
-## Using provisioning packages
-
-If you insert a USB thumb drive with a provisioning package into one of the USB ports when you start Surface Hub 2S, the device displays the following page.
-
-1. Enter the requested settings and select **Set up**.
-
- 
-
- 
-2. Choose the provisioning package you’d like to use.
-
- 
-
-3. If you created a multiple devices CSV file, you will be able to choose a device configuration. For more information, refer to [Create provisioning packages for Surface Hub 2S](https://docs.microsoft.com/surface-hub/surface-hub-2s-deploy#provisioning-multiple-devices-csv-file).
-
-
- 
-
-4. Follow the instructions to complete first time Setup.
diff --git a/devices/surface-hub/surface-hub-2s-site-planning.md b/devices/surface-hub/surface-hub-2s-site-planning.md
deleted file mode 100644
index 9b04ea0174..0000000000
--- a/devices/surface-hub/surface-hub-2s-site-planning.md
+++ /dev/null
@@ -1,43 +0,0 @@
----
-title: "Surface Hub 2S site planning"
-description: "Learn more about rooms for Surface Hub 2S."
-keywords: separate values with commas
-ms.prod: surface-hub
-ms.sitesec: library
-author: greg-lindsay
-ms.author: greglin
-manager: laurawi
-audience: Admin
-ms.topic: article
-ms.date: 06/20/2019
-ms.localizationpriority: Medium
----
-
-# Surface Hub 2S site planning
-
-## Introduction
-
-Designed for team collaboration, Surface Hub 2S can transform the way you work — not only in the conference rooms but any place you want to work. One of the biggest advantages of Surface Hub 2S is the ability to move it from one space to another when used with the Steelcase Roam mobile stand and mobile battery. Providing unplugged, uninterrupted teamwork capabilities, Surface Hub 2S can be integrated into almost any workspace.
-
-## Room considerations
-
-Designed for interactive use in smaller conference rooms and huddle spaces, Surface Hub 2S provides a 4K camera, microphone array, crystal clear speakers, and a brilliant 4K+ resolution display. Optimizing the user experience in larger spaces with more people further away from the display may require peripherals such as an extra camera, microphone, or room systems solution such as Microsoft Teams Rooms.
-
-As a general guideline, install Surface Hub 2S in a space that meets the following criteria:
-
-- People can reach all four edges of the touchscreen.
-- The screen is not in direct sunlight, which could affect viewing or damage the screen.
-- Ventilation openings are not blocked.
-- Microphones are not affected by noise sources, such as fans or vents.
-- Space is well lit with no reflective sources.
-
-Whether mounted to a wall or installed on the mobile stand, the areas where you use the device should maintain:
-
-- Room temperatures no cooler than 10°C (50° F) and no hotter than 35°C (95° F).
-- Relative humidity no lower than 20 percent and no higher than 80 percent.
-
-For detailed room planning guidance and more information about Microsoft Teams Rooms see [Plan Microsoft Teams Rooms.](https://docs.microsoft.com/MicrosoftTeams/room-systems/skype-room-systems-v2-0)
-
-## Managing Surface Hub 2S location
-
-If you plan to use Surface Hub 2S on a mobile stand, you may wish to explore third-party solutions that enable location services. For example, active RFID systems can provide real-time tracking throughout complex office or industrial spaces. For more information, see your A/V provider or other third-party expertise for guidance.
diff --git a/devices/surface-hub/surface-hub-2s-site-readiness-guide.md b/devices/surface-hub/surface-hub-2s-site-readiness-guide.md
deleted file mode 100644
index 8db9d3818e..0000000000
--- a/devices/surface-hub/surface-hub-2s-site-readiness-guide.md
+++ /dev/null
@@ -1,25 +0,0 @@
----
-title: "Surface Hub 2S site readiness guide"
-description: "Get familiar with site readiness requirements and recommendations for Surface Hub 2S."
-keywords: separate values with commas
-ms.prod: surface-hub
-ms.sitesec: library
-author: greg-lindsay
-ms.author: greglin
-manager: laurawi
-audience: Admin
-ms.topic: article
-ms.date: 06/20/2019
-ms.localizationpriority: Medium
----
-
-# Surface Hub 2S site readiness guide
-
-|**Topic**|**Description**|
-|:-------|:-------|
-| [Site planning for Surface Hub 2S](surface-hub-2s-site-planning.md) | Review room considerations and planning for peripherals. |
-| [Surface Hub 2S quick start](surface-hub-2s-quick-start.md) | Get an overview of required steps to unpack and start Surface Hub 2S. |
-| [Install and mount Surface Hub 2S](surface-hub-2s-install-mount.md) | Learn about licensed accessories to install and mount Surface Hub 2S. |
-| [Customizing installation of Surface Hub 2S](surface-hub-2s-custom-install.md) | Learn how to custom install without licensed mounting accessories.|
-| [Surface Hub 2S ports and keypad overview](surface-hub-2s-port-keypad-overview.md) | Get details for I/O ports and keypad power and selection controls. |
-| [Connect to Surface Hub 2S](surface-hub-2s-connect.md) | Learn about wired and wireless methods to connect to Surface Hub.|
diff --git a/devices/surface-hub/surface-hub-2s-techspecs.md b/devices/surface-hub/surface-hub-2s-techspecs.md
deleted file mode 100644
index 4e40f9ae25..0000000000
--- a/devices/surface-hub/surface-hub-2s-techspecs.md
+++ /dev/null
@@ -1,45 +0,0 @@
----
-title: "Surface Hub 2S tech specs"
-description: "View tech specs for Surface Hub 2S including pen, camera, and optional mobile battery specifications."
-keywords: separate values with commas
-ms.prod: surface-hub
-ms.sitesec: library
-author: greg-lindsay
-manager: laurawi
-ms.author: greglin
-audience: Admin
-ms.topic: article
-ms.date: 11/19/2019
-ms.localizationpriority: Medium
----
-
-# Surface Hub 2S tech specs
-
-|**Item**|**Details**|
-|:------ |:--------- |
-|**Dimensions**| 29.2" x 43.2" x 3.0” (741 mm x 1097 mm x 76 mm) |
-|**Shipping dimensions**| 47.64" x 36.89" x 9.92" (1,210 mm x 937 mm x 252 mm)|
-|**Weight**| 61.6 lbs. (28 kg) |
-|**Shipping Weight**| 81.08 lbs. (36.77 kg) |
-|**Resolution**| 3840 x 2560 |
-|**Display**| PixelSense Display, 3:2 aspect ratio, 10-bit color, 15.5 mm border, anti-glare, IPS LCD |
-|**Processor**| Quad-core 8th Generation Intel Core i5 processor, 8 GB RAM, 128 GB SSD 1 |
-|**Graphics**| Intel UHD Graphics 620 |
-|**Wireless**| Wi-Fi 5 (IEEE 802.11 a/b/g/n/ac compatible) Bluetooth Wireless 4.1 technology Miracast display |
-|**Connections**| USB-A Mini-DisplayPort 1.2 video output RJ45 gigabit Ethernet (1000/100/10 BaseT) HDMI video input (HDMI 2.0, HDCP 2.2 /1.4) USB-C with DisplayPort input Four USB-C (on display) |
-|**Sensors**| Doppler occupancy 2 Accelerometer Gyroscope |
-|**Audio/Video**| Full-range, front facing 3-way stereo speakers Full band 8-element MEMS microphone array Microsoft Surface Hub 2 Camera, 4K, USB-C connection, 90-degree HFOV |
-|**Pen**| Microsoft Surface Hub 2 Pen (active) |
-|**Software**| Windows 10 Microsoft Teams for Surface Hub 3 Skype for Business Microsoft Whiteboard Microsoft Office (Mobile) Microsoft Power BI 2 |
-|**Exterior**| Casing: Precision machined aluminum with mineral-composite resin Color: Platinum Physical Buttons: Power, Volume, Source |
-|**What’s in the box**| One Surface Hub 2S One Surface Hub 2 Pen One Surface Hub 2 Camera 2.5 m AC Power Cable Quick Start Guide |
-|**Warranty**| 1-year limited hardware warranty |
-|**BTU**| 1518 BTU/hr |
-|**Input Voltage**| 50/60Hz 110/230v nominal, 90-265v max |
-|**Input power, operating**| 445 W (495 W Surge Load) |
-|**Input Current**| 5.46 A |
-|**Input Power, standby**| 5 W max |
-
-> [!NOTE]
-> 1 System software uses significant storage space. Available storage is subject to change based on system software updates and apps usage. 1 GB= 1 billion bytes. See Surface.com/Storage for more details. 2 Doppler sensor not available in Hong Kong, India, Kuwait, and Oman due to government regulations.
- 3 Software license required for some features. Sold separately.
diff --git a/devices/surface-hub/surface-hub-2s-unpack.md b/devices/surface-hub/surface-hub-2s-unpack.md
deleted file mode 100644
index 950a5caa6f..0000000000
--- a/devices/surface-hub/surface-hub-2s-unpack.md
+++ /dev/null
@@ -1,36 +0,0 @@
----
-title: "Unpack Surface Hub 2S"
-description: "This page includes information about safely unpacking Surface Hub 2S."
-keywords: separate values with commas
-ms.prod: surface-hub
-ms.sitesec: library
-author: greg-lindsay
-ms.author: greglin
-manager: laurawi
-audience: Admin
-ms.topic: article
-ms.date: 06/20/2019
-ms.localizationpriority: Medium
----
-
-# Unpack Surface Hub 2S
-
-## Unpacking the Surface Hub 2S
-
-Before you remove Surface Hub 2S from the box, make sure that you have your mounting solution assembled and someone available to help you.
-
-1. Use the handles on each side of the box to move it to the space where you'll set it up.
-2. Before opening, remove the clips (4) on the front and back, and then lift the top off the box using the handles.
-3. In the base of the Surface Hub 2S, open the accessories box containing the setup guide, Surface Hub 2 pen, Surface Hub 2 camera, and the power cable.
-4. On the back of the surface hub, there's an instructional label that shows you where to attach the mounting hardware. Install them in place and remove the label.
-5. If you're using a mobile stand remember to lock the wheels to keep the stand in place
-6. Be sure to lift the Surface Hub 2S with both hands and support the bottom of the device.
-7. Align the installed hardware with the slots on the mount so it rests firmly in place.
-8. Follow any further instructions that came with your mounting solution.
-
-## Install pen and camera
-
-1. Unwrap your Surface Hub 2 pen and attach it magnetically to your preferred side of the device.
-2. Remove the lens cling from the camera and attach it to the USB-C port on the top of the Surface Hub 2S.
-3. Insert the power cable into the back of the device and plug it into a power outlet. Run the cable through any cable guides on your mounting solution and remove the screen clang.
-4. To begin, press the power button on the bottom right.
diff --git a/devices/surface-hub/surface-hub-2s-whats-new.md b/devices/surface-hub/surface-hub-2s-whats-new.md
deleted file mode 100644
index 82589b360e..0000000000
--- a/devices/surface-hub/surface-hub-2s-whats-new.md
+++ /dev/null
@@ -1,65 +0,0 @@
----
-title: "What's new in Surface Hub 2S for IT admins"
-description: "Learn more about new features in Surface Hub 2S."
-keywords: separate values with commas
-ms.prod: surface-hub
-ms.sitesec: library
-author: greg-lindsay
-ms.author: greglin
-manager: laurawi
-audience: Admin
-ms.topic: article
-ms.date: 06/20/2019
-ms.localizationpriority: Medium
----
-
-# What's new in Surface Hub 2S for IT admins
-
-Surface Hub 2S is an all-in-one collaboration canvas that’s built for teamwork delivering a digital whiteboard, meetings platform, and a Windows 10 computing experience in one device.
-
-|**Capability**|**Summary**|**Learn more**|
-|:-------|:------|:----|
-|**Mobile Device Management and UEFI manageability**| Manage settings and policies using a mobile device management (MDM) provider.
Full integration with Surface Enterprise Management Mode (SEMM) lets you manage hardware components and firmware. | [Managing Surface Hub 2S with Microsoft Intune](surface-hub-2s-manage-intune.md)
[Surface Enterprise Management Mode](https://docs.microsoft.com/surface/surface-enterprise-management-mode) |
-|**Cloud and on-premises coexistence**| Supports on-premises, hybrid, or online. | [Prepare your environment for Microsoft Surface Hub 2S](surface-hub-2s-prepare-environment.md) |
-|**Reset and recovery**| Restore from the cloud or USB drive. | [Recover and reset Surface Hub 2S](surface-hub-2s-recover-reset.md) |
-|**Microsoft Whiteboard**| Office 365 integration, intelligent ink, and Bing search bring powerful new capabilities, enabling a persistent digital canvas shareable across most browsers, Windows and iOS devices. | [Announcing a new whiteboard for your Surface Hub](https://techcommunity.microsoft.com/t5/Office-365-Blog/Announcing-a-new-Whiteboard-for-your-Surface-Hub/ba-p/637050) |
-|**Microsoft Teams Meeting Room License**| Extends Office 365 licensing options across Skype for Business, Microsoft Teams, and Intune. | [Teams Meeting Room Licensing Update](https://docs.microsoft.com/MicrosoftTeams/room-systems/skype-room-systems-v2-0) |
-|**On-screen display**| Adjust volume, brightness, and input control directly on the display. | |
-|**Sensor-activated Connected Standby**| Doppler sensor activates Connected Standby after 1 minute of inactivity.
Manage this setting remotely using Intune or directly on the device from the Settings app. | [Surface Hub 2S tech specs](surface-hub-2s-techspecs.md) |
-|**Surface Hub pen**| Ergonomically redesigned and easily attachable on the sides of the device. | |
-|**Surface app for Surface Hub 2S**| Change audio settings and view your device's information from the Surface app | |
-|**Ready for tomorrow**| Removable cartridge facilitates upgrading to new features. | |
-
-For more information about what’s new in Surface Hub 2S, see:
-
-- [Surface Hub 2S product site](https://www.microsoft.com/p/surface-hub-2S/8P62MW6BN9G4?activetab=pivot:overviewtab)
-- [Behind the Design Surface Hub 2S](https://techcommunity.microsoft.com/t5/Surface-IT-Pro-Blog/Behind-the-design-Surface-Hub-2S/ba-p/464099)
-
-## Surface Hub 2S compared with Surface Hub
-
-The following table details the differences between Surface Hub and Surface Hub 2S:
-
-|**Component**| **Surface Hub 55”**|**Surface Hub 84”**| **Surface Hub 2S**|
-|:----- |:---- |:---- |:----- |
-|**Form Factor**| 55” | 84” | 50” |
-|**Dimension**| 31.75” x 59.62” x 3.38” (806.4 mm x 1514.3 mm x 85.8 mm) | 46.12” x 86.7” x 4.15” (1171.5 mm x 2202.9 mm x 105.4 mm) | 29.2" x 43.2" x 3.0" (741 mm x 1097 mm x 76 mm) |
-|**Weight**| 105 lbs. (48 kg) | 280 lbs. (127 kg) | 61.6 lbs. (28 kg) |
-|**Display**| Resolution: 1920 x 1080 @ 120 Hz Contrast ratio: 1300:1 Touch: 100-point multi-touch Projective Capacitance optically bonded sensor | Resolution: 3840 x 2160 @ 120 Hz Contrast Ratio: 1400:1 Touch: 100-point multi-touch Projective Capacitance optically bonded sensor | Resolution: 3840 x 2560 @ 60 Hz |
-|**Aspect Ratio**| 16:9 | 16:9 | 3:2 |
-|**Storage**| SSD 128 GB | SSD 128 GB | SSD 128 GB |
-|**RAM**| 8 GB RAM | 8 GB RAM | 8 GB RAM |
-|**Processor**| 4th Generation Intel® Core i5 | 4th Generation Intel Core i7 | Quad-core 8th Generation Intel Core i5 processor |
-|**Graphics**| Intel HD 4600 | NVIDIA Quadro K2200 | Intel UHD Graphics 620 |
-|**Network**| Wi-Fi (802.11 a/b/g/n/ac) Ethernet 1 Gbps Bluetooth 4.0 low energy Miracast enabled | Wi-Fi (802.11 a/b/g/n/ac) Ethernet 1 Gbps Bluetooth 4.0 low energy Miracast enabled | Wi-Fi 5 (IEEE 802.11 a/b/g/n/ac) Ethernet 1 Gbps Bluetooth Wireless 4.1 technology Miracast Display |
-|**Ports**| (1) USB 3.0 (bottom) + (1) USB 3.0 (side access) (2) USB 2.0 DisplayPort Video Output 3.5 mm Stereo Out RJ11 Connector for system-level control
DisplayPort Video Input HDMI Video Input VGA Video Input 3.5 mm Stereo Input (1) USB 2.0 type B Touchback Output | (1) USB 3.0 (bottom) + (1) USB 3.0 (side access) (4) USB 2.0 DisplayPort Video Output 3.5 mm Stereo Out RJ11 Connector for system-level control
DisplayPort Video Input HDMI Video Input VGA Video Input 3.5 mm Stereo Input (1) USB 2.0 type B Touchback Output | (1) USB-A Mini-DisplayPort Video Output HDMI Video Input USB-C with DisplayPort Input (4) USB-C (on display) RJ45 Gigabit Ethernet |
-|**Sensors**| (2) Passive Infrared Presence Sensors, Ambient Light Sensors | (2) Passive Infrared Presence Sensors, Ambient Light Sensors | Doppler occupancy sensor, Accelerometer, Gyroscope |
-|**NFC**| NFC reader | NFC reader | N/A |
-|**Speakers**| (2) Front-facing stereo speakers | (2) Front-facing stereo speakers | Full range front facing 3-way stereo speakers |
-|**Microphone**| High-Performance, 4-Element Array | High-Performance, 4-Element Array | Full band 8-element MEMS microphone array |
-|**Camera**| (2) Wide angle HD cameras 1080p @ 30 fps | (2) Wide angle HD cameras 1080p @ 30 fps | (1) Microsoft Surface Hub 2 Camera, 4K, USB-C connection, 90-degree horizontal field of view |
-|**Pen**| (2) Powered, active, subpixel accuracy | (2) Powered, active, subpixel accuracy | (1) Microsoft Surface Hub 2 Pen (active) |
-|**Physical buttons**| Power, Input Select, Volume, Brightness | Power, Input Select, Volume, Brightness | Power, Volume, Source |
-|**Software**| Windows 10 + Office (Word, PowerPoint, Excel) | Windows 10 + Office (Word, PowerPoint, Excel) | Windows 10 + Office (Word, PowerPoint, Excel) |
-
-> [!NOTE]
-> The NFC reader available in the original Surface Hub is discontinued in Surface Hub 2S and is no longer available.
diff --git a/devices/surface-hub/surface-hub-authenticator-app.md b/devices/surface-hub/surface-hub-authenticator-app.md
deleted file mode 100644
index 80c7dbefd1..0000000000
--- a/devices/surface-hub/surface-hub-authenticator-app.md
+++ /dev/null
@@ -1,86 +0,0 @@
----
-title: Sign in to Surface Hub with Microsoft Authenticator
-description: Use Microsoft Authenticator on your mobile device to sign in to Surface Hub.
-ms.prod: surface-hub
-ms.sitesec: library
-author: dansimp
-ms.author: dansimp
-ms.topic: article
-ms.date: 08/28/2017
-ms.reviewer:
-manager: laurawi
-localizationpriority: medium
----
-
-# Sign in to Surface Hub with Microsoft Authenticator
-
-People in your organization can sign in to a Surface Hub without a password using the Microsoft Authenticator app, available on Android and iOS.
-
-## Organization prerequisites
-
-To let people in your organization sign in to Surface Hub with their phones and other devices instead of a password, you’ll need to make sure that your organization meets these prerequisites:
-
-- Your organization must be a hybrid or cloud-only organization, backed by Azure Active Directory (Azure AD). For more information, see [What is Azure Active Directory?](https://docs.microsoft.com/azure/active-directory/active-directory-whatis)
-
-- Make sure you have at minimum an Office 365 E3 subscription.
-
-- [Configure Multi-Factor Authentication](https://docs.microsoft.com/azure/active-directory/authentication/howto-mfa-mfasettings). Make sure **Notification through mobile app** is selected.
-
- 
-
-- Enable content hosting on Azure AD services such as Office, SharePoint, etc.
-
-- Surface Hub must be running Windows 10, version 1703 or later.
-
-- Surface Hub is set up with either a local or domain-joined account.
-
-Currently, you cannot use Microsoft Authenticator to sign in to Surface Hubs that are joined to Azure AD.
-
-## Individual prerequisites
-
-- An Android phone running 6.0 or later, or an iPhone or iPad running iOS9 or later
-
-- The most recent version of the Microsoft Authenticator app from the appropriate app store
-
- >[!NOTE]
- >On iOS, the app version must be 5.4.0 or higher.
- >
- >The Microsoft Authenticator app on phones running a Windows operating system can't be used to sign in to Surface Hub.
-
-- Passcode or screen lock on your device is enabled
-
-- A standard SMTP email address (example: joe@contoso.com). Non-standard or vanity SMTP email addresses (example: firstname.lastname@contoso.com) currently don’t work.
-
-## How to set up the Microsoft Authenticator app
-
->[!NOTE]
->If Company Portal is installed on your Android device, uninstall it before you set up Microsoft Authenticator. After you set up the app, you can reinstall Company Portal.
->
->If you have already set up Microsoft Authenticator on your phone and registered your device, go to the sign-in instructions.
-
-1. Add your work or school account to Microsoft Authenticator for Multi-Factor Authentication. You will need a QR code provided by your IT department. For help, see [Get started with the Microsoft Authenticator app](https://docs.microsoft.com/azure/multi-factor-authentication/end-user/microsoft-authenticator-app-how-to).
-2. Go to **Settings** and register your device.
-3. Return to the accounts page and choose **Enable phone sign-in** from the account dropdown menu.
-
-## How to sign in to Surface Hub during a meeting
-
-1. After you’ve set up a meeting, go to the Surface Hub and select **Sign in to see your meetings and files**.
-
- >[!NOTE]
- >If you’re not sure how to schedule a meeting on a Surface Hub, see [Schedule a meeting on Surface Hub](https://support.microsoft.com/help/17325/surfacehub-schedulemeeting).
-
- 
-
-2. You’ll see a list of the people invited to the meeting. Select yourself (or the person who wants to sign in – make sure this person has gone through the steps to set up their device before your meeting), and then select **Continue**.
-
- 
-
- You'll see a code on the Surface Hub.
-
- 
-
-3. To approve the sign-in, open the Authenticator app, enter the four-digit code that’s displayed on the Surface Hub, and select **Approve**. You will then be asked to enter the PIN or use your fingerprint to complete the sign in.
-
- 
-
-You can now access all files through the OneDrive app.
\ No newline at end of file
diff --git a/devices/surface-hub/surface-hub-downloads.md b/devices/surface-hub/surface-hub-downloads.md
deleted file mode 100644
index 79ff342ba9..0000000000
--- a/devices/surface-hub/surface-hub-downloads.md
+++ /dev/null
@@ -1,36 +0,0 @@
----
-title: Useful downloads for Microsoft Surface Hub
-description: Downloads related to the Microsoft Surface Hub.
-ms.prod: surface-hub
-ms.sitesec: library
-author: dansimp
-ms.author: dansimp
-ms.topic: article
-ms.date: 08/22/2017
-ms.reviewer:
-manager: laurawi
-ms.localizationpriority: medium
----
-
-# Useful downloads for Microsoft Surface Hub
-
-This topic provides links to useful Surface Hub documents, such as product datasheets and user's guide.
-
-| Link | Description |
-| --- | --- |
-| [Surface Hub Setup Guide (English, French, Spanish) (PDF)](https://download.microsoft.com/download/0/1/6/016363A4-8602-4F01-8281-9BE5C814DC78/Setup-Guide_EN-FR-SP.pdf) | Get a quick overview of how to set up the environment for your new Surface Hub. |
-| [Surface Hub Quick Reference Guide (PDF)](https://download.microsoft.com/download/9/E/E/9EE660F8-3FC6-4909-969E-89EA648F06DB/Surface%20Hub%20Quick%20Reference%20Guide_en-us.pdf) | Use this quick reference guide to get information about key features and functions of the Surface Hub. |
-| [Surface Hub User Guide (PDF)](https://download.microsoft.com/download/3/6/B/36B6331E-0C63-4E71-A05D-EE88D05081F8/surface-hub-user-guide-en-us.pdf) | Learn how to use Surface Hub in scheduled or ad-hoc meetings. Invite remote participants, use the built-in tools, save data from your meeting, and more. |
-| [Surface Hub Replacement PC Drivers](https://www.microsoft.com/download/details.aspx?id=52210) | The Surface Hub Replacement PC driver set is available for those customers who have chosen to disable the Surface Hub’s internal PC and use an external computer with their 84” or 55” Surface Hub. This download is meant to be used with the Surface Hub Admin Guide , which contains further details on configuring a Surface Hub Replacement PC. |
-| [Microsoft Surface Hub Rollout and Adoption Success Kit (ZIP)](https://download.microsoft.com/download/F/A/3/FA3ADEA4-4966-456B-8BDE-0A594FD52C6C/Surface_Hub_Adoption_Kit_Final_0519.pdf) | Best practices for generating awareness and implementing change management to maximize adoption, usage, and benefits of Microsoft Surface Hub. The Rollout and Adoption Success Kit zip file includes the Rollout and Adoption Success Kit detailed document, Surface Hub presentation, demo guidance, awareness graphics, and more. |
-| [Unpacking Guide for 84-inch Surface Hub (PDF)](https://download.microsoft.com/download/5/2/B/52B4007E-D8C8-4EED-ACA9-FEEF93F6055C/84_Unpacking_Guide_English_French-Spanish.pdf) | Learn how to unpack your 84-inch Surface Hub efficiently and safely. [Watch the video (opens in a pop-up media player)](http://compass.xbox.com/assets/75/2b/752b73dc-6e9d-4692-8ba1-0f9fc03bff6b.mov?n=04.07.16_installation_video_03_unpacking_84.mov) |
-| [Unpacking Guide for 55-inch Surface Hub (PDF)](https://download.microsoft.com/download/2/E/7/2E7616A2-F936-4512-8052-1E2D92DFD070/55_Unpacking_Guide_English-French-Spanish.PDF) | Learn how to unpack your 55-inch Surface Hub efficiently and safely. [Watch the video (opens in a pop-up media player)](http://compass.xbox.com/assets/a9/d6/a9d6b4d7-d33f-4e8b-be92-28f7fc2c06d7.mov?n=04.07.16_installation_video_02_unpacking_55.mov) |
-| [Wall Mounting and Assembly Guide (PDF)](https://download.microsoft.com/download/7/0/2/702485E3-B55E-4DE8-B5DD-3B56F90DCF5D/SH-Guide_WACG_Wall_Mounts_EN-FR-ES-NL-DE-IT-PT-AR-DA-FI-NO-SV.pdf) | Detailed instructions on how to safely and securely assemble the wall brackets, and how to mount your Surface Hub onto them. [Watch the video (opens in a pop-up media player)](http://compass.xbox.com/assets/bf/4d/bf4d6f06-370c-45ee-88e6-c409873914e8.mov?n=04.07.16_installation_video_05_wall_mount.mov) |
-| [Floor-Supported Mounting and Assembly Guide (PDF)](https://download.microsoft.com/download/7/0/2/702485E3-B55E-4DE8-B5DD-3B56F90DCF5D/SH-Guide_WACG_Floor_Support_Mount_EN-FR-ES-NL-DE-IT-AR-DA-FI-NO-SV.pdf) | Detailed instructions on how to safely and securely assemble the floor-supported brackets, and how to mount your Surface Hub onto them. [Watch the video (opens in a pop-up media player)](http://compass.xbox.com/assets/ed/de/edde468a-e1d4-4ce8-8b61-c4527dd25c81.mov?n=04.07.16_installation_video_06_floor_support_mount.mov) |
-| [Rolling Stand Mounting and Assembly Guide (PDF)](https://download.microsoft.com/download/7/0/2/702485E3-B55E-4DE8-B5DD-3B56F90DCF5D/SH-Guide_WACG_Rolling_Stands_EN-FR-ES-NL-DE-IT-AR-DA-FI-NO-SV.pdf) | Detailed instructions on how to safely and securely assemble the rolling stand, and how to mount your Surface Hub onto it. [Watch the video (opens in a pop-up media player)](http://compass.xbox.com/assets/1f/94/1f949613-3e4a-41e3-ad60-fe8aa7134115.mov?n=04.07.16_installation_video_04_rolling_stand_mount.mov) |
-| [Mounts and Stands Datasheet (PDF)](https://download.microsoft.com/download/5/0/1/501F98D9-1BCC-4448-A1DB-47056CEE33B6/20160711_Surface_Hub_Mounts_and_Stands_Datasheet.pdf) | Specifications and prices for all Surface Hub add-on stands and mounts that turn your workspace into a Surface Hub workspace. |
-| [Surface Hub Stand and Wall Mount Specifications (PDF)](https://download.microsoft.com/download/7/A/7/7A75BD0F-5A46-4BCE-B313-A80E47AEB581/20160720_Combined_Stand_Wall_Mount_Drawings.pdf) | Illustrated specifications for the 55” and 84” Surface Hub rolling stands, wall mounts, and floor-supported wall mounts. |
-
-
-
-
diff --git a/devices/surface-hub/surface-hub-qos.md b/devices/surface-hub/surface-hub-qos.md
deleted file mode 100644
index aa1b746b8d..0000000000
--- a/devices/surface-hub/surface-hub-qos.md
+++ /dev/null
@@ -1,53 +0,0 @@
----
-title: Implement Quality of Service on Surface Hub
-ms.reviewer:
-manager: laurawi
-description: Learn how to configure QoS on Surface Hub.
-ms.prod: surface-hub
-ms.sitesec: library
-author: dansimp
-ms.author: dansimp
-ms.topic: article
-ms.localizationpriority: medium
----
-
-# Implement Quality of Service (QoS) on Surface Hub
-
-Quality of Service (QoS) is a combination of network technologies that allows the administrators to optimize the experience of real time audio/video and application sharing communications.
-
-Configuring [QoS for Skype for Business](https://docs.microsoft.com/windows/client-management/mdm/networkqospolicy-csp) on the Surface Hub can be done using your [mobile device management (MDM) provider](manage-settings-with-mdm-for-surface-hub.md) or through a [provisioning package](provisioning-packages-for-surface-hub.md).
-
-
-This procedure explains how to configure QoS for Surface Hub using Microsoft Intune.
-
-1. In Intune, [create a custom policy](https://docs.microsoft.com/intune/custom-settings-configure).
-
- 
-
-2. In **Custom OMA-URI Settings**, select **Add**. For each setting that you add, you will enter a name, description (optional), data type, OMA-URI, and value.
-
- 
-
-3. Add the following custom OMA-URI settings:
-
- Name | Data type | OMA-URI ./Device/Vendor/MSFT/NetworkQoSPolicy | Value
- --- | --- | --- | ---
- Audio Source Port | String | /HubAudio/SourcePortMatchCondition | Get the values from your Skype administrator
- Audio DSCP | Integer | /HubAudio/DSCPAction | 46
- Video Source Port | String | /HubVideo/SourcePortMatchCondition | Get the values from your Skype administrator
- Video DSCP | Integer | /HubVideo/DSCPAction | 34
- Audio Process Name | String | /HubAudio/AppPathNameMatchCondition | Microsoft.PPISkype.Windows.exe
- Video Process Name | String | /HubVideo/AppPathNameMatchCondition | Microsoft.PPISkype.Windows.exe
-
- >[!IMPORTANT]
- >Each **OMA-URI** path begins with `./Device/Vendor/MSFT/NetworkQoSPolicy`. The full path for the audio source port setting, for example, will be `./Device/Vendor/MSFT/NetworkQoSPolicy/HubAudio/SourcePortMatchCondition`.
-
-
-
-
-4. When the policy has been created, [deploy it to the Surface Hub.](manage-settings-with-mdm-for-surface-hub.md#manage-surface-hub-settings-with-mdm)
-
-
->[!WARNING]
->Currently, you cannot configure the setting **IPProtocolMatchCondition** in the [NetworkQoSPolicy CSP](https://docs.microsoft.com/windows/client-management/mdm/networkqospolicy-csp). If this setting is configured, the policy will fail to apply.
-
diff --git a/devices/surface-hub/surface-hub-recovery-tool.md b/devices/surface-hub/surface-hub-recovery-tool.md
deleted file mode 100644
index 2db5f9706e..0000000000
--- a/devices/surface-hub/surface-hub-recovery-tool.md
+++ /dev/null
@@ -1,101 +0,0 @@
----
-title: Using the Surface Hub Recovery Tool
-description: How to use the Surface Hub Recovery Tool to re-image the SSD.
-ms.assetid: FDB6182C-1211-4A92-A930-6C106BCD5DC1
-ms.reviewer:
-manager: laurawi
-keywords: manage Surface Hub
-ms.prod: surface-hub
-ms.sitesec: library
-author: dansimp
-ms.author: dansimp
-ms.topic: article
-ms.date: 05/22/2018
-ms.localizationpriority: medium
----
-
-# Using the Surface Hub Recovery Tool
-
-The [Microsoft Surface Hub Recovery Tool](https://www.microsoft.com/download/details.aspx?id=52210) helps you re-image your Surface Hub Solid State Drive (SSD) using a Windows 10 desktop device, without calling support or replacing the SSD. With this tool, you can reimage an SSD that has an unknown Administrator password, boot errors, was unable to complete a cloud recovery, or for a device that has an older version of the operating system. The tool will not fix physically damaged SSDs.
-
-To re-image the Surface Hub SSD using the Recovery Tool, you'll need to remove the SSD from the Surface Hub, connect the drive to the USB-to-SATA cable, and then connect the cable to the desktop PC on which the Recovery Tool is installed. For more information on how to remove the existing drive from your Surface Hub, see [Surface Hub SSD replacement](surface-hub-ssd-replacement.md).
-
-> [!IMPORTANT]
-> Do not let the device go to sleep or interrupt the download of the image file.
-
-If the tool is unsuccessful in reimaging your drive, please contact [Surface Hub Support](https://support.microsoft.com/help/4037644/surface-contact-surface-warranty-and-software-support).
-
-## Prerequisites
-
-### Mandatory
-
-- Host PC running 64-bit version of Windows 10, version 1607 or higher.
-- Internet access
-- Open USB 2.0 or greater port
-- USB-to-SATA cable
-- 10 GB of free disk space on the host computer
-- SSDs shipped with Surface Hub or a SSD provided by Support as a replacement. SSDs not supplied by Microsoft are not supported.
-
-### Recommended
-
-- High-speed Internet connection
-- Open USB 3.0 port
-- USB 3.0 or higher USB-to-SATA cable
-- The imaging tool was tested with the following make and model of cables:
- - Startech USB312SAT3CB
- - Rosewill RCUC16001
- - Ugreen 20231
-
-## Download Surface Hub Recovery Tool
-
-Surface Hub Recovery Tool is available for download from [Surface Hub Tools for IT](https://www.microsoft.com/download/details.aspx?id=52210) under the file name **SurfaceHub_Recovery_v1.14.137.0.msi**.
-
-To start the download, click **Download**, choose **SurfaceHub_Recovery_v1.14.137.0.msi** from the list, and click **Next**. From the pop-up, choose one of the following:
-
-- Click **Run** to start the installation immediately.
-- Click **Save** to copy the download to your computer for later installation.
-
-Install Surface Hub Recovery Tool on the host PC.
-
-## Run Surface Hub Recovery Tool
-
-1. On the host PC, select the **Start** button, scroll through the alphabetical list on the left, and select the recovery tool shortcut.
-
- 
-
-2. Click **Start**.
-
- 
-
-3. In the **Guidance** window, click **Next**.
-
- 
-
-4. click **Yes** to download the image. Time to download the recovery image is dependent on internet connection speeds. On an average corporate connection, it can take up to an hour to download the 8GB image file.
-
- 
-
-5. When the download is complete, the tool instructs you to connect an SSD drive. If the tool is unable to locate the attached drive, there is a good chance that the cable being used is not reporting the name of the SSD to Windows. The imaging tool must find the name of the drive as "LITEON L CH-128V2S USB Device" before it can continue. For more information on how to remove the existing drive from your Surface Hub, see [Surface Hub SSD replacement](surface-hub-ssd-replacement.md).
-
- 
-
-6. When the drive is recognized, click **Start** to begin the re-imaging process. On the warning that all data on the drive will be erased, click **OK**.
-
- 
-
- Prior to applying the system image to the drive, the SSD is repartitioned and formatted. Copying the system binaries will take approximately 30 minutes, but can take longer depending on the speed of your USB bus, the cable being used, or antivirus software installed on your system.
-
- 
-
- 
-
-## Troubleshooting and common problems
-
-Issue | Notes
---- | ---
-The tool fails to image the SSD | Make sure you are using a factory-supplied SSD and one of the tested cables.
-The reimaging process appears halted/frozen | It is safe to close and restart the Surface Hub Recovery Tool with no ill effect to the SSD.
-The drive isn’t recognized by the tool | Verify that the Surface Hub SSD is enumerated as a Lite-On drive, "LITEON L CH-128V2S USB Device". If the drive is recognized as another named device, your current cable isn’t compatible. Try another cable or one of the tested cable listed above.
-Error: -2147024809 | Open Disk Manager and remove the partitions on the Surface Hub drive. Disconnect and reconnect the drive to the host machine. Restart the imaging tool again.
-
-If the tool is unsuccessful in reimaging your drive, please contact [Surface Hub Support](https://support.microsoft.com/help/4037644/surface-contact-surface-warranty-and-software-support).
diff --git a/devices/surface-hub/surface-hub-security.md b/devices/surface-hub/surface-hub-security.md
deleted file mode 100644
index 4dc2b7518e..0000000000
--- a/devices/surface-hub/surface-hub-security.md
+++ /dev/null
@@ -1,158 +0,0 @@
----
-title: "Surface Hub security overview"
-description: "This page explains the Defense in Depth design of Surface Hub and describes security enhancements in Surface Hub 2S, wireless security protections, and related features."
-keywords: separate values with commas
-ms.prod: surface-hub
-ms.sitesec: library
-author: coveminer
-ms.author: v-jokai
-manager: laurawi
-audience: Admin
-ms.topic: article
-ms.date: 03/27/2020
-ms.localizationpriority: High
----
-# Surface Hub security overview
-
-Surface Hub provides a locked-down computing appliance with custom platform firmware running the Windows 10 Team Edition operating system. The resulting device takes the traditional, "single use" secure kiosk, "only run what you need" philosophy and delivers a modern take on it. Built to support a rich collaborative user experience, Surface Hub is protected against continually evolving security threats.
-
-Built on Windows 10, Surface Hub delivers enterprise-grade modern security enabling IT admins to enforce data protection with BitLocker, Trusted Platform Module 2.0 (TPM), plus cloud-powered security with Windows Defender (also known as Microsoft Defender).
-
-## Defense in Depth security
-
-Security protocols begin as soon as Surface Hub is turned on. Starting at the firmware level, Surface Hub will only load the operating system and its components in response to multiple security checks. Surface Hub employs a strategy called Defense in Depth that involves layering independent defensive sub-components to protect the whole of the system in the event of partial failure. This industry practice has proven to be highly effective in mitigating against potential unilateral exploits and weakness in sub-components.
-
-The modern Unified Extensible Firmware Interface (UEFI) is statically and securely configured by Microsoft to only boot an authenticated Windows 10 Team Edition operating system from internal storage. Every line of code that runs on Surface Hub has its signature verified prior to execution. Only applications signed by Microsoft, either as part of the operating system or installed via the Microsoft Store, can run on the Surface Hub. Code or apps not meeting these requirements are blocked.
-
-Surface Hub security systems include the following:
-
-- **Boot-time defenses.** Loads only trusted Surface Hub operating system components.
-- **Operating system defenses.** Protects against execution of unintended or malicious software or code.
-- **User interface defenses.** Provides a user interface that's safe for end users, preventing access to potentially risky activities such as running executables from the command line.
-
-### Boot-time defenses
-
-The SoC has a security processor that's separate from every other core. When you first start Surface Hub, only the security processor starts before anything else can be loaded.
-
-
-
-#### Secure Boot
-
-Secure Boot is used to verify that the components of the boot process, including drivers and the operating system, are validated against a database of valid and known signatures. On Surface Hub, a platform-specific signature must first be validated before the authorized Windows Team operating system can be loaded. This helps prevent attacks from a cloned or modified system running malicious code hidden in what appears to be an otherwise normal user experience. For more information, see [Secure Boot overview](https://docs.microsoft.com/windows-hardware/design/device-experiences/oem-secure-boot).
-
-### Operating system defenses
-
-Once the operating system is verified as originating from Microsoft and Surface Hub successfully completes the boot process, the device scrutinizes the executable code. Our approach to securing the operating system involves identifying the code signature of all executables, allowing only those that pass our restrictions to be loaded into the runtime. This code signing method enables the operating system to verify the author and confirm that code was not altered prior to running on the device.
-
-Surface Hub uses a code signing feature known as User Mode Code Integrity (UMCI) in Windows Application Control (formerly known as Device Guard). Policy settings are configured to only allow apps that meet one of these requirements:
-
-- Universal Windows Platform (Microsoft Store) apps that are [officially certified](https://docs.microsoft.com/windows/uwp/publish/the-app-certification-process).
-- Apps signed with the unique Microsoft Production Root Certification Authority (CA), which can only be signed by Microsoft employees with authorized access to those certificates.
-- Apps signed with the unique Surface Hub Production Root C.
-
-The configuration file is signed using the Microsoft Production Root CA designed to prevent restrictions from being removed or modified by a third party. All other executables at this point are simply blocked at the operating system runtime level and prevented from accessing processing power. This attack surface reduction provides the following protections:
-
-- No legacy document modes
-- No legacy script engines
-- No Vector Markup Language
-- No Browser Helper Objects
-- No ActiveX controls
-
-In addition to blocking unsigned or incorrectly signed code via UMCI, Surface Hub uses Windows Application Control to block Windows components, such as the Command Prompt, PowerShell, and Task Manager. These safeguards reflect a key design feature of Surface Hub as a secure computing appliance. For more information, see the following:
-
-- [Application Control overview](https://docs.microsoft.com/windows/security/threat-protection/windows-defender-application-control/windows-defender-application-control)
-
-- [Windows Defender Application Control and virtualization-based protection of code integrity](https://docs.microsoft.com/windows/security/threat-protection/device-guard/introduction-to-device-guard-virtualization-based-security-and-windows-defender-application-control)
-
-### User interface defenses
-
-While boot-time defenses and operating system lockdown safeguards deliver foundational security, the user interface provides an additional layer designed to further reduce risk. To prevent malicious code from reaching the device through drivers, Surface Hub does not download advanced drivers for plug and play (PnP) devices. Devices that leverage basic drivers, such as USB flash drives or certified Surface Hub peripherals (speakers, microphones, cameras) work as expected, but advanced systems, such as printers, will not.
-
-User interface defenses also simplify the UI, further preventing the execution of malicious software or code. The following Surface Hub UI elements layer the core security provided by code signing:
-
-- **File Explorer.** Surface Hub has a custom File Explorer that enables quick access to Music, Videos, Documents, Pictures, and Downloads folders — without exposing users to system or program files. Other locations on the local hard drive are not available through File Explorer. In addition, many file types running such as .exe, and .msi installation files cannot run providing another layer of safety against potentially malicious executables.
-
-- **Start & All Apps.** The Start and All Apps components of Surface Hub do not expose access to Command Prompt, PowerShell, or other Windows components blocked via Application Control. In addition, Windows run functionality typically accessed on PCs from the Search box is turned off for Surface Hub.
-
-## Security enhancements in Surface Hub 2S
-
-Although Surface Hub and Surface Hub 2S both run the same operating system software, some features unique to Surface Hub 2S provide additional management and security capabilities enabling IT admins to perform the following tasks:
-
-- Manage UEFI settings with SEMM
-- Recover Hub with bootable USB
-- Harden device account with password rotation
-
-### Manage UEFI settings with SEMM
-
-UEFI is an interface between the underlying hardware platform pieces and the operating system. On Surface Hub, a custom UEFI implementation allows granular control over these settings and prevents any non-Microsoft entity from changing the UEFI settings of the device — or booting to a removable drive to modify or change the operating system.
-
-At a high level, during the factory provisioning process, Surface Hub UEFI is preconfigured to enable Secure Boot and is set to only boot from the internal solid-state drive (SSD), with access to UEFI menus locked down and shortcuts removed. This seals UEFI access and ensures the device can only boot into the Windows Team operating system installed on Surface Hub.
-
-When managed via Microsoft Surface Enterprise Management Mode (SEMM), IT admins can deploy UEFI settings on Hub devices across an organization. This includes the ability to enable or disable built-in hardware components, protect UEFI settings from being changed by unauthorized users, and adjust boot settings.
-
-
-
-Admins can implement SEMM and enrolled Surface Hub 2S devices using the downloadable [Microsoft Surface UEFI Configurator](https://www.microsoft.com/download/details.aspx?id=46703). For more information, see [Secure and manage Surface Hub 2S with SEMM and UEFI](https://docs.microsoft.com/surface-hub/surface-hub-2s-secure-with-uefi-semm).
-Secured using a certificate to protect the configuration from unauthorized tampering or removal, SEMM enables management of the following components:
-
-- Wired LAN
-- Camera
-- Bluetooth
-- Wi-Fi
-- Occupancy sensor
-- IPv6 for PXE Boot
-- Alternate Boot
-- Boot Order Lock
-- USB Boot
-- UEFI front page interface
- - Devices
- - Boot
- - Date/Time
-
-
-### Recover Hub with bootable USB
-
-Surface Hub 2S enables admins to reinstall the device to factory settings using a recovery image in as little as 20 minutes. Typically, you would only need to do this if your Surface Hub is no longer functioning. Recovery is also useful if you have lost the Bitlocker key or no longer have admin credentials to the Settings app.
-
-### Harden device account with password rotation
-
-Surface Hub uses a device account, also known as a "room account" to authenticate with Exchange, Microsoft Teams, and other services. When you enable password rotation, Hub 2S automatically generates a new password every 7 days, consisting of 15-32 characters with a combination of uppercase and lowercase letters, numbers, and special characters. Because no one knows the password, the device account password rotation effectively mitigates associated risk from human error and potential social engineering security attacks.
-
-## Windows 10 enterprise-grade security
-
-In addition to Surface Hub-specific configurations and features addressed in this document, Surface Hub also uses the standard security features of Windows 10. These include:
-
-- **BitLocker**. The Surface Hub SSD is equipped with BitLocker to protect the data on the device. Its configuration follows industry standards. For more information, see [BitLocker overview](https://docs.microsoft.com/windows-hardware/design/device-experiences/oem-secure-boot).
-- **Windows Defender.** The Windows Defender anti-malware engine runs continuously on Surface Hub and works to automatically remediate threats found on Surface Hub. The Windows Defender engine receives updates automatically and is manageable via remote management tools for IT admins. The Windows Defender engine is a perfect example of our Defense in Depth approach: If malware can find a way around our core code-signage-based security solution, it will be caught here. For more information, see [Windows Defender Application Control and virtualization-based protection of code integrity](https://docs.microsoft.com/windows/security/threat-protection/device-guard/introduction-to-device-guard-virtualization-based-security-and-windows-defender-application-control).
-- **Plug and play drivers.** To prevent malicious code from reaching the device through drivers, Surface Hub does not download advanced drivers for PnP devices. This allows devices that leverage basic drivers such as USB flash drives to work as expected while blocking more advanced systems such as printers.
-- **Trusted Platform Module 2.0.** Surface Hub has an industry standard discrete Trusted Platform Module (dTPM) for generating and storing cryptographic keys and hashes. The dTPM protects keys used for the verification of boot phases, the BitLocker master key, password-less sign-on key, and more. The dTPM meets [FIPS 140-2 Level 2](https://docs.microsoft.com/windows/security/threat-protection/fips-140-validation) certification, the U.S. government computer security standard, and is compliant with [Common Criteria](https://docs.microsoft.com/windows/security/threat-protection/windows-platform-common-criteria) certification used worldwide.
-
-## Wireless security for Surface Hub
-
-Surface Hub uses Wi-Fi Direct / Miracast technology and the associated 802.11, Wi-Fi Protected Access (WPA2), and Wireless Protected Setup (WPS) standards. Since the device only supports WPS (as opposed to WPA2 Pre-Shared Key (PSK) or WPA2 Enterprise), issues traditionally associated with 802.11 encryption are simplified by design.
-
-Miracast is part of the Wi-Fi Display standard, which itself is supported by the Wi-Fi Direct protocol. These standards are supported in modern mobile devices for screen sharing and collaboration.
-
-Wi-Fi Direct or Wi-Fi "peer to peer" (P2P) is a standard released by the Wi-Fi Alliance for "Ad-Hoc" networks. This allows supported devices to communicate directly and create groups of networks without requiring a traditional Wi-Fi Access Point or an Internet connection.
-
-Security for Wi-Fi Direct is provided by WPA2 using the WPS standard. Devices can be authenticated using a numerical pin, a physical or virtual push button, or an out-of-band message using near-field communication. Surface Hub supports both push button by default as well PIN methods. For more information, see [How Surface Hub addresses Wi-Fi Direct security issues](https://docs.microsoft.com/surface-hub/surface-hub-wifi-direct).
-
-## Learn more
-
-- [Secure Boot overview](https://docs.microsoft.com/windows-hardware/design/device-experiences/oem-secure-boot)
-
-- [BitLocker overview](https://docs.microsoft.com/windows/security/information-protection/bitlocker/bitlocker-overview)
-
-- [Application Control overview](https://docs.microsoft.com/windows/security/threat-protection/windows-defender-application-control/windows-defender-application-control)
-
-- [Secure and manage Surface Hub 2S with SEMM and UEFI](https://docs.microsoft.com/surface-hub/surface-hub-2s-secure-with-uefi-semm)
-
-- [How Surface Hub addresses Wi-Fi Direct security issues](https://docs.microsoft.com/surface-hub/surface-hub-wifi-direct)
-
-- [Windows Defender Application Control and virtualization-based protection of code integrity](https://docs.microsoft.com/windows/security/threat-protection/device-guard/introduction-to-device-guard-virtualization-based-security-and-windows-defender-application-control)
-
-- [Surface Tools for IT](https://www.microsoft.com/download/details.aspx?id=46703)
-
-- [FIPS 140-2 Level 2](https://docs.microsoft.com/windows/security/threat-protection/fips-140-validation)
-
-- [Common Criteria certification](https://docs.microsoft.com/windows/security/threat-protection/windows-platform-common-criteria)
diff --git a/devices/surface-hub/surface-hub-site-readiness-guide.md b/devices/surface-hub/surface-hub-site-readiness-guide.md
deleted file mode 100644
index d12281f55b..0000000000
--- a/devices/surface-hub/surface-hub-site-readiness-guide.md
+++ /dev/null
@@ -1,138 +0,0 @@
----
-title: Surface Hub Site Readiness Guide
-ms.reviewer:
-manager: laurawi
-description: Use this Site Readiness Guide to help plan your Surface Hub installation.
-ms.prod: surface-hub
-ms.sitesec: library
-author: greg-lindsay
-ms.author: greglin
-ms.topic: article
-ms.localizationpriority: medium
----
-
-# Surface Hub Site Readiness Guide
-
-Use this Site Readiness Guide to help plan your Surface Hub installation. In this guide, you’ll find:
-- Site readiness topics
-- Detailed hardware specifications on power, ports, and cables
-- Recommendations for moving and storage
-- Links to guidance on unpacking and mounting
-
-## Site readiness planning
-
-The room needs to be large enough to provide good viewing angles, but small enough for the microphones to pick up clear signals from the people in the room. Most rooms that are about 22 feet (seven meters) long will provide a good meeting experience. In the conference area, mount Surface Hub where:
-
-- Everyone in the room can see it.
-- People can reach all four edges of the touchscreen.
-- The screen is not in direct sunlight, which could affect viewing or damage the screen.
-- Ventilation openings are not blocked.
-- Microphones are not affected by noise sources, such as fans or vents.
-You can find more details in the [55” Microsoft Surface Hub technical information](surface-hub-technical-55.md) or [84” Microsoft Surface Hub technical information](surface-hub-technical-84.md) sections. For cleaning, care, and safety information, see the mounting guides and user guide at https://www.microsoft.com/surface/support/surface-hub.
-
-### Hardware considerations
-
-Surface Hub arrives with:
-- Two Microsoft Surface Hub pens
-- A Microsoft wireless keyboard, customized for Surface Hub
-- A 9-foot NEMA 5-15P (US Standard) to C13 power cable
-
-You’ll need to provide:
-- Cat-5e or Cat-6 network cables
-- Display cables (optional)
-- Audio cable (optional)
-- Type A to B USB cable (optional)
-
-For details about cable ports, see the [55” Microsoft Surface Hub technical information](surface-hub-technical-55.md) or [84” Microsoft Surface Hub technical information](surface-hub-technical-84.md) sections. For details about cables, see [Wired Connect](#wired).
-
-Microsoft Surface Hub has an internal PC and does not require an external computer system.
-
-For power recommendations, see [55” Microsoft Surface Hub technical information](surface-hub-technical-55.md) or [84” Microsoft Surface Hub technical information](surface-hub-technical-84.md). For power cable safety warnings, see the mounting guides at https://www.microsoft.com/surface/support/surface-hub.
-
-### Data and other connections
-
-To use Surface Hub, you need an active Ethernet port and a standard power outlet. In addition, you may want to:
-
-- Equip the conference table for Wired Connect.
-- Expand the wall outlet configuration to include:
- - Additional AC outlets
- - Ethernetports
- - Audio ports
- - Video ports (DisplayPort, HDMI, VGA, etc.)
-
-
-## When Surface Hub arrives
-
-Surface Hub is large and heavy, so let Receiving know when it will arrive and what they should do to handle it safely. For details on the packing weights and other specifications, see [55” Microsoft Surface Hub technical information](surface-hub-technical-55.md) or [84” Microsoft Surface Hub technical information](surface-hub-technical-84.md).
-
-Consider the following:
-- Wait to unpack Surface Hub from the shipping container until you’ve moved it to the conference area where you plan to install it.
-- Make sure your loading dock can accept a shipment on a pallet and hold it securely until it can be installed.
-- Check for local labor union rules that would require you to use union labor to unload or move Surface Hub.
-- Do not leave Surface Hub in a hot or humid environment. As with any computer-based or display equipment, heat and humidity can damage Surface Hub. The recommended storage temperatures are 32°F to 95°F with a relative humidity of less than 70 percent.
-
-### Moving Surface Hub
-
-Before you move Surface Hub, make sure that all the doorways, thresholds, hallways, and elevators are big enough to accommodate it. For information on the dimensions and weight of your Surface Hub in its shipping container, see [55” Microsoft Surface Hub technical information](surface-hub-technical-55.md) or [84” Microsoft Surface Hub technical information](surface-hub-technical-84.md).
-
-### Unpacking Surface Hub
-
-For unpacking information, refer to the unpacking guide included in the shipping container. You can open the unpacking instructions before you open the shipping container. These instructions can also be found here: https://www.microsoft.com/surface/support/surface-hub
-
->[!IMPORTANT]
->Retain and store all Surface Hub shipping materials—including the pallet, container, and screws—in case you need to ship Surface Hub to a new location or send it
-for repairs. For the 84” Surface Hub, retain the lifting handles.
-
-### Lifting Surface Hub
-
-The 55” Surface Hub requires two people to safely lift and mount. The 84” Surface Hub requires four people to safely lift and mount. Those assisting must be able to lift 70 pounds to waist height. Review the unpacking and mounting guide for details on lifting Surface Hub. You can find it at https://www.microsoft.com/surface/support/surface-hub.
-
-## Mounting and setup
-
-See your mounting guide at https://www.microsoft.com/surface/support/surface-hub for detailed instructions.
-
-There are three ways to mount your Surface Hub:
-
-- **Wall mount**: Lets you permanently hang Surface Hub on a conference space wall.
-- **Floor support mount**: Supports Surface Hub on the floor while it is permanently anchored to a conference space wall.
-- **Rolling stand**: Supports Surface Hub and lets you move it to other conference locations. For links to guides that provide details about each mounting method, including building requirements, see https://www.microsoft.com/surface/support/surface-hub.
-
-For specifications on available mounts for the original Surface Hub, see the following:
-
-- [Surface Hub Mounts and Stands Datasheet](https://download.microsoft.com/download/5/0/1/501F98D9-1BCC-4448-A1DB-47056CEE33B6/20160711_Surface_Hub_Mounts_and_Stands_Datasheet.pdf)
-- [Surface Hub Stand and Wall Mount Specifications](https://download.microsoft.com/download/7/A/7/7A75BD0F-5A46-4BCE-B313-A80E47AEB581/20160720_Combined_Stand_Wall_Mount_Drawings.pdf)
-
-## The Connect experience
-
-Connect lets people project their laptop, tablet, or phone to the Surface Hub screen. Connect allows wireless or wired connection types.
-
-#### Wireless connect
-
-Since wireless connect is based on Miracast, you don’t need cables or additional setup planning to use it. Your users can load Miracast on most Miracast-enabled Windows 8.1 and Windows 10 devices. Then they can project their display from their computer or phone to the Surface Hub screen.
-
-
-#### Wired connect
-
-With wired connect, a cable transmits information from computers, tablets, or phones to Surface Hub. There are three video cable options, and they all use the same USB 2.0 cable. The cable bundle can include one or all of these connection options.
-
-- DisplayPort (DisplayPort cable + USB 2.0 cable)
-- HDMI (HDMI cable + USB 2.0 cable)
-- VGA (VGA cable + 3.5mm audio cable + USB 2.0 cable)
-
-For example, to provide audio, video, and touchback capability to all three video options, your Wired Connect cable bundle must include:
-
-- A DisplayPort cable
-- An HDMI cable
-- A VGA cable
-- A USB 2.0 cable
-- A 3.5mm cable
-
-When you create your wired connect cable bundles, check the [55” Microsoft Surface Hub technical information](surface-hub-technical-55.md) or [84” Microsoft Surface Hub technical information](surface-hub-technical-84.md) sections for specific technical and physical details and port locations for each type of Surface Hub. Make the cables long enough to reach from Surface Hub to where the presenter will sit or stand.
-
-For details on Touchback and Inkback, see the user guide at https://www.microsoft.com/surface/support/surface-hub.
-
-
-
-## See also
-
-[Watch the video (opens in a pop-up media player)](https://compass.xbox.com/assets/27/aa/27aa7dd7-7cb7-40ea-9bd6-c7de0795f68c.mov?n=04.07.16_installation_video_01_site_readiness.mov)
diff --git a/devices/surface-hub/surface-hub-ssd-replacement.md b/devices/surface-hub/surface-hub-ssd-replacement.md
deleted file mode 100644
index 12f256388d..0000000000
--- a/devices/surface-hub/surface-hub-ssd-replacement.md
+++ /dev/null
@@ -1,54 +0,0 @@
----
-title: Surface Hub SSD replacement
-ms.reviewer:
-manager: laurawi
-description: Learn how to replace the solid state drive in a Surface Hub.
-ms.prod: surface-hub
-ms.sitesec: library
-author: dansimp
-ms.author: dansimp
-ms.topic: article
-ms.localizationpriority: medium
----
-
-# Surface Hub SSD replacement
-
-You might need to remove the solid state drive (SSD) from your Surface Hub so that you can reimage it using the [Surface Hub Recovery Tool](surface-hub-recovery-tool.md) or because you've been sent a replacement drive. You would reimage your SSD when the operating system is no longer bootable, such as from a Windows update failure, BitLocker issues, reset failure, or hardware failure.
-
-
->[!WARNING]
->Make sure the Surface Hub is turned off at the AC switch.
-
-1. Locate the SSD compartment door on the rear, upper portion of the Surface Hub in the locations illustrated below. The door is identifiable as it doesn't have open ventilation slots.
-
- 
-
- *Surface Hub hard drive locations*
-
-2. Locate the locking tab on the hard drive compartment door. On the Surface Hub 55, the locking tab will be located on the left-hand side of the door. On the Surface Hub 84, it will be on the right-hand side as shown in the illustration.
-
- 
-
- *Locking tab on hard drive compartment door*
-
-3. Lift open the compartment door to access the hard drive.
-
- 
-
- *Lift compartment door*
-
-4. Locate the pull tab, which may be partially hidden under the rear cover. Pull on the tab to eject the hard drive from the compartment.
-
- 
-
- *Pull tab*
-
-5. Slide the replacement drive into place until you hear it click.
-
- 
-
- *Slide replacement drive into place*
-
-6. Close the compartment door.
-
-7. Apply power to the Surface Hub.
diff --git a/devices/surface-hub/surface-hub-start-menu.md b/devices/surface-hub/surface-hub-start-menu.md
deleted file mode 100644
index 468e0d3329..0000000000
--- a/devices/surface-hub/surface-hub-start-menu.md
+++ /dev/null
@@ -1,184 +0,0 @@
----
-title: Configure Surface Hub Start menu
-description: Use MDM to customize the Start menu on Surface Hub.
-ms.prod: surface-hub
-ms.sitesec: library
-author: greg-lindsay
-ms.author: greglin
-ms.topic: article
-ms.date: 08/15/2018
-ms.reviewer:
-manager: laurawi
-ms.localizationpriority: medium
----
-
-# Configure Surface Hub Start menu
-
-The [January 17, 2018 update to Windows 10](https://support.microsoft.com/help/4057144) (build 15063.877) enables customized Start menus on Surface Hub devices. You apply the customized Start menu layout using mobile device management (MDM).
-
-When you apply a customized Start menu layout to Surface Hub, users cannot pin, unpin, or uninstall apps from Start.
-
-## How to apply a customized Start menu to Surface Hub
-
-The customized Start menu is defined in a Start layout XML file. You have two options for creating your Start layout XML file:
-
-- Edit the [default Surface Hub Start XML](#default)
-
- -or-
-
-- Configure the desired Start menu on a desktop (pinning only apps that are available on Surface Hub), and then [export the layout](https://docs.microsoft.com/windows/configuration/customize-and-export-start-layout#export-the-start-layout).
-
->[!TIP]
->To add a tile with a web link to your desktop start menu, go to the link in Microsoft Edge, select `...` in the top right corner, and select **Pin this page to Start**. See [a Start layout that includes a Microsoft Edge link](#edge) for an example of how links will appear in the XML.
-
-To edit the default XML or the exported layout, familiarize yourself with the [Start layout XML](https://docs.microsoft.com/windows/configuration/start-layout-xml-desktop). There are a few [differences between Start layout on a deskop and a Surface Hub.](#differences)
-
-When you have your Start menu defined in a Start layout XML, [create an MDM policy to apply the layout.](https://docs.microsoft.com/windows/configuration/customize-windows-10-start-screens-by-using-mobile-device-management#a-href-idbkmk-domaingpodeploymentacreate-a-policy-for-your-customized-start-layout)
-
-
-## Differences between Surface Hub and desktop Start menu
-
-There are a few key differences between Start menu customization for Surface Hub and a Windows 10 desktop:
-
-- You cannot use **DesktopApplicationTile** (https://docs.microsoft.com/windows/configuration/start-layout-xml-desktop#startdesktopapplicationtile) in your Start layout XML because Windows desktop applications (Win32) are not supported on Surface Hub.
-- You cannot use the Start layout XML to configure the taskbar or the Welcome screen for Surface Hub.
-- Surface Hub supports a maximum of 6 columns (6 1x1 tiles), however, you **must** define `GroupCellWidth=8` even though Surface Hub will only display tiles in columns 0-5, not columns 6 and 7.
-- Surface Hub supports a maximum 6 rows (6 1x1 tiles)
-- `SecondaryTile`, which is used for links, will open the link in Microsoft Edge.
-
-
-
-## Example: Default Surface Hub Start layout
-
-```xml
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-```
-
-
-## Example: Start layout that includes a Microsoft Edge link
-
-This example shows a link to a website and a link to a .pdf file. The secondary tile for Microsoft Edge uses a 150 x 150 pixel icon.
-
-```xml
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-```
-
->[!NOTE]
->The default value for `ForegroundText` is light; you don't need to include `ForegroundText` in your XML unless you're changing the value to dark.
diff --git a/devices/surface-hub/surface-hub-technical-55.md b/devices/surface-hub/surface-hub-technical-55.md
deleted file mode 100644
index 209e77df4c..0000000000
--- a/devices/surface-hub/surface-hub-technical-55.md
+++ /dev/null
@@ -1,153 +0,0 @@
----
-title: Technical information for 55" Surface Hub
-ms.reviewer:
-manager: laurawi
-description: Specifications for the 55" Surface Hub
-ms.prod: surface-hub
-ms.sitesec: library
-author: dansimp
-ms.author: dansimp
-ms.topic: article
-ms.localizationpriority: medium
----
-
-# Technical information for 55" Surface Hub
-
-## Measurements
-
-|
---- | ---
-Pricing | Starting at $8,999
-Size | 31.75” x 59.62” x 3.38” (806.4mm x 1514.3mm x 85.8mm)
-Storage/RAM | SSD 128GB with 8GB RAM
-Processor | 4th Generation Intel® Core™ i5
-Graphics | Intel® HD 4600
-Ports | **Internal PC** • (1) USB 3.0 (bottom) + (1) USB 3.0 (side access) • (2) USB 2.0 • Ethernet 1000 Base-T • DisplayPort • Video Output • 3.5mm Stereo Out • RJ11 Connector for system-level control **Alternate PC** • (2) USB 2.0 type B output • Connection for Camera, Sensors, Microphone, Speakers • (1) DisplayPort Video Input **Guest PC** • DisplayPort Video Input • HDMI Video Input • VGA Video Input • 3.5mm Stereo Input • (1) USB 2.0 type B Touchback™ Output
-Sensors | (2) Passive Infrared Presence Sensors, Ambient Light Sensors
-Speakers | (2) Front-facing stereo speakers
-Microphone | High-Performance, 4-Element Array
-Camera | (2) Wide angle HD cameras 1080p @ 30fps
-Pen | (2) Powered, active, subpixel accuracy
-Physical side buttons | Power, Input Select, Volume, Brightness
-Software | Windows 10 + Office (Word, PowerPoint, Excel)
-What’s in the box | • Surface Hub 55” • (2) Surface Hub Pens • Power Cable • Setup Guide • Start Guide • Safety and Warranty documents • Wireless All-in-One Keyboard
-Mounting features | 4X VESA standard, 400mm x 400mm plus 1150mm x 400mm pattern, 8X M6 X 1.0 threaded mounting locations
-Display height from floor | Recommended height of 55 inches (139.7 cm) to center of screen
-Product weight | Approx. 105 lb. (47.6 kg) without accessories
-Product shipping weight | Approx. 150 lb. (68 kg)
-Product dimensions HxWxD | 31.63 x 59.62 x 3.2 inches (80.34 x 151.44 x 8.14 cm)
-Product shipping dimensions HxWxD | 43 x 65 x 20 inches (109 x 165 x 51 cm)
-Product thickness | Touch surface to mounting surface: ≤ 2.4 inches (6 cm)
-Orientation | Landscape only. Display cannot be used in a portrait orientation.
-BTU | 1706 BTU/h
-Image resolution | 1920 x 1080
-Frame rate | 120Hz
-EDID preferred timing, replacement PC | 1920 x 1080, 120Hz vertical refresh
-EDID preferred timing, wired connect | 1920 x 1080, 60Hz vertical refresh
-Input voltage | (50/60Hz) 110/230v nominal, 90-265v max
-Input power, operating | 500W max
-Input power, standby | 5W nominal
-
-
-## Replacement PC connections
-
-Connector and location | Label | Description
---- | --- | ---
-Switch, bottom I/O |  | Switches the function between using internal PC or external PC.
-Display port, bottom I/O |  | Provides input for replacement PC.
-USB type B, bottom I/O |  | Provides USB connection for replacement PC to internal peripherals.
-USB type B, bottom I/O |  | Provides USB connection for integrated hub.
-
-
-## Wired connect connections
-
-Connector and location | Label | Description
---- | --- | ---
-Display port, bottom I/O |  | Provides input for wired connect PC.
-HDMI, bottom I/O |  | Provides HDMI input for wired connect PC.
-VGA, bottom I/O |  | Provides VGA input for wired connect PC.
-3.5mm, bottom I/O |  | Provides analog audio input.
-USB type B, bottom I/O |  | Provides USB connection for video ingest touchback.
-
-## Additional connections
-
-Connector and location | Label | Description
---- | --- | ---
-USB type A, side I/O |  | Provides 1 USB 3.0 connection for USB devices. Wake-on USB capable.
-USB type A, bottom I/O with blue insulator |  | Provides USB 3.0 connection.
-3.5mm, bottom I/O |  | Provides analog audio out.
-Display port, bottom I/O |  | Provides mirrored video out function to another display.
-IEC/EN60320-C13 receptacle with hard switch |  | Provides AC input and compliance with EU power requirements.
-RJ45, bottom I/O |  | Connects to Ethernet.
-RJ11, bottom I/O |  | Connects to room control systems.
-
-
-
-
-
-
-
-## Diagrams of ports and clearances
-
-***Top view of 55" Surface Hub***
-
-
-
----
-
-
-***Front view of 55" Surface Hub***
-
-
-
-
----
-
-***Bottom view of 55" Surface Hub***
-
-
-
-
----
-
-***Replacement PC ports on 55" Surface Hub***
-
-
-
-
----
-
-***Keypad on right side of 55" Surface Hub***
-
-
-
-
----
-
-***Rear view of 55" Surface Hub***
-
-
-
-
----
-
-***Clearances for 55" Surface Hub***
-
-
-
----
-
-
-***Front and bottom handholds and clearances for 55" Surface Hub***
-
-
-
-
----
-
-
-***Rear handholds and clearances for 55" Surface Hub***
-
-
-
-
diff --git a/devices/surface-hub/surface-hub-technical-84.md b/devices/surface-hub/surface-hub-technical-84.md
deleted file mode 100644
index 1c08da5a6b..0000000000
--- a/devices/surface-hub/surface-hub-technical-84.md
+++ /dev/null
@@ -1,159 +0,0 @@
----
-title: Technical information for 84" Surface Hub
-ms.reviewer:
-manager: laurawi
-description: Specifications for the 84" Surface Hub
-ms.prod: surface-hub
-ms.sitesec: library
-author: dansimp
-ms.author: dansimp
-ms.topic: article
-ms.localizationpriority: medium
----
-
-# Technical information for 84" Surface Hub
-
-## Measurements
-
-|
---- | ---
-Pricing | Starting at $21,999
-Size | 46.12” x 86.7” x 4.15” (1171.5mm x 2202.9mm x 105.4mm)
-Storage/RAM | SSD 128GB with 8GB RAM
-Processor | 4th Generation Intel® Core™ i7
-Graphics | NVIDIA Quadro K2200
-Ports | **Internal PC** • (1) USB 3.0 (bottom) + (1) USB 3.0 (side access) • (4) USB 2.0 • Ethernet 1000 Base-T • DisplayPort Video Output • 3.5mm Stereo Out • RJ11 Connector for system-level control **Alternate PC** • (2) USB 2.0 type B output • connection for Camera, Sensors, Microphone, Speakers • (2) DisplayPort Video Input **Guest PC** • DisplayPort Video Input • HDMI Video Input • VGA Video Input • 3.5mm Stereo Input • (1) USB 2.0 type B Touchback™ Output
-Sensors | (2) Passive Infrared Presence Sensors, Ambient Light Sensors
-Speakers | (2) Front-facing stereo speakers
-Microphone | High-Performance, 4-Element Array
-Camera | (2) Wide angle HD cameras 1080p @ 30fps
-Pen | (2) Powered, active, subpixel accuracy
-Physical side buttons | Power, Input Select, Volume, Brightness
-Software | Windows 10 + Office (Word, PowerPoint, Excel)
-What’s in the box | • Surface Hub 84” • (2) Surface Hub Pens • Power Cable • Setup Guide • Safety and Warranty documents • Wireless All-in-One Keyboard
-Mounting features | 4X VESA standard, 1200mm x 600mm pattern, 8X M8 X 1.25 threaded mounting locations
-Display height from floor | Recommended height of 54 inches (139.7 cm) to center of screen
-Product weight | Approx. 280 lb. (127 kg.)
-Product shipping weight | Approx. 580 lb. (263 kg.)
-Product dimensions HxWxD | 46 x 86.9 x 4.1 inches (116.8 x 220.6 x 10.4 cm)
-Product shipping dimensions HxWxD | 66.14 x 88.19 x 24.4 inches (168 x 224 x 62 cm)
-Product thickness | Touch surface to mounting surface: ≤ 3.1 inches (7.8 cm)
-Orientation | Landscape only. Display cannot be used in a portrait orientation.
-BTU | 3070.8 BTU/h
-Image resolution | 3840 x 2160
-Frame rate | 120Hz
-Contrast Ratio | 1400:1
-EDID preferred timing, replacement PC | 3840 x 2140, 120Hz vertical refresh
-EDID preferred timing, wired connect | 1920 x 1080, 60Hz vertical refresh
-Input voltage | 110/230v nominal, 90-265v max
-Input power, operating | 900W max
-Input power, standby | 5W nominal, 1-10W max
-
-
-## Replacement PC connections
-
-Connector and location | Label | Description
---- | --- | ---
-Switch, bottom I/O |  | Switches the function between using internal PC or external PC.
-Display port, bottom I/O |  | Provides input for replacement PC.
-Display port, bottom I/O |  | Provides second input for replacement PC.
-USB type B, bottom I/O |  | Provides USB connection for replacement PC to internal peripherals.
-USB type B, bottom I/O |  | Provides USB connection for integrated hub.
-
-
-## Wired connect connections
-
-Connector and location | Label | Description
---- | --- | ---
-Display port, bottom I/O |  | Provides input for wired connect PC.
-HDMI, bottom I/O |  | Provides HDMI input for wired connect PC.
-VGA, bottom I/O |  | Provides VGA input for wired connect PC.
-3.5mm, bottom I/O |  | Provides analog audio input.
-USB type B, bottom I/O |  | Provides USB connection for video ingest touchback.
-
-## Additional connections
-
-Connector and location | Label | Description
---- | --- | ---
-USB type A, side I/O |  | Provides 1 USB 3.0 connection for USB devices. Wake-on USB capable.
-USB type A, bottom I/O with blue insulator |  | Provides USB 3.0 connection.
-3.5mm, bottom I/O |  | Provides analog audio out.
-Display port, bottom I/O |  | Provides mirrored video out function to another display.
-IEC/EN60320-C13 receptacle with hard switch |  | Provides AC input and compliance with EU power requirements.
-RJ45, bottom I/O |  | Connects to Ethernet.
-RJ11, bottom I/O |  | Connects to room control systems.
-
-
-
-
-
-
-
-## Diagrams of ports and clearances
-
-***Top view of 84" Surface Hub***
-
-
-
----
-
-
-***Front view of 84" Surface Hub***
-
-
-
-
----
-
-***Bottom view of 84" Surface Hub***
-
-
-
-
----
-
-***Replacement PC ports on 84" Surface Hub***
-
-
-
-
-
----
-
-***Rear view of 84" Surface Hub***
-
-
-
-
----
-
-***Clearances for 84" Surface Hub***
-
-
-
----
-
-
-***Removable lifting handles on 84” Surface Hub ***
-
-
-
-
----
-
-
-***Wall mount threads on back of 84” Surface Hub ***
-
-
-
----
-***Lifting handles in top view of 84” Surface Hub***
-
-
-
----
-***Side view of 84” Surface Hub***
-
-
-
-
diff --git a/devices/surface-hub/surface-hub-update-history.md b/devices/surface-hub/surface-hub-update-history.md
deleted file mode 100644
index 8e584f17b3..0000000000
--- a/devices/surface-hub/surface-hub-update-history.md
+++ /dev/null
@@ -1,564 +0,0 @@
----
-title: Surface Hub update history
-description: Surface Hub update history
-ms.assetid: d66a9392-2b14-4cb2-95c3-92db0ae2de34
-keywords:
-ms.prod: surface-hub
-ms.sitesec: library
-author: v-miegge
-ms.author: v-miegge
-ms.topic: article
-ms.localizationpriority: medium
----
-
-# Surface Hub update history
-
-Windows 10 was designed to be a service, which means it automatically gets better through periodic software updates. The great news is that you usually don’t have to do anything to get the latest Windows 10 updates—they'll download and install whenever they’re available.
-
-Most Windows updates focus on performance and security improvements to keep you going 24/7.
-
-One thing we’re hearing from you is that you want to know more about what's in our Windows 10 updates, so we're providing more details on this page. In the list below, the most recent Windows update is listed first. Installing the most recent update ensures that you also get any previous updates you might have missed, including security updates. Microsoft Store apps are updated through the Microsoft Store (managed by the Surface Hub's system administrator). Details about app updates are provided on a per-app basis.
-We'll be refreshing this page as new updates are released, so stay tuned for the latest info. And thank you for helping us learn and get better with each update!
-
-Please refer to the “[Surface Hub Important Information](https://support.microsoft.com/products/surface-devices/surface-hub)” page for related topics on current and past releases that may require your attention.
-
-## Windows 10 Team Creators Update 1703
-
-
-February 28, 2020—update for Surface Hub 2S
-
-This update is specific to the Surface Hub 2S and provides the driver and firmware updates outlined below:
-
-* Surface Integration driver - 13.46.139.0
- * Improves display brightness scenarios.
-* Intel(R) Management Engine Interface driver - 1914.12.0.1256
- * Improves system stability.
-* Surface SMC Firmware update - 1.161.139.0
- * Improves pen battery performance.
-* Surface UEFI update - 694.2938.768.0
- * Improves system stability.
-
-
-
-February 11, 2020—update for Team edition based on KB4537765* (OS Build 15063.2284)
-
-This update to the Surface Hub includes quality improvements and security fixes. Key updates to Surface Hub, not already outlined in [Windows 10 Update History](https://support.microsoft.com/help/4018124/windows-10-update-history), include:
-
-* Resolves an issue where the Hub 2S cannot be heard well by other participants during Skype for Business calls.
-* Improves reliability for some Arabic, Hebrew, and other RTL language usage scenarios on Surface Hub.
-
-Please refer to the [Surface Hub Admin guide](https://docs.microsoft.com/surface-hub/) for enabling/disabling device features and services.
-*[KB4537765](https://support.microsoft.com/help/4537765)
-
-
-
-January 14, 2020—update for Team edition based on KB4534296* (OS Build 15063.2254)
-
-This update to the Surface Hub includes quality improvements and security fixes. Key updates to Surface Hub, not already outlined in [Windows 10 Update History](https://support.microsoft.com/help/4018124/windows-10-update-history), include:
-
-* Addresses an issue with log collection for Microsoft Surface Hub 2S.
-
-Please refer to the [Surface Hub Admin guide](https://docs.microsoft.com/surface-hub/) for enabling/disabling device features and services.
-*[KB4534296](https://support.microsoft.com/help/4534296)
-
-
-
-September 24, 2019—update for Team edition based on KB4516059* (OS Build 15063.2078)
-
-This update to the Surface Hub includes quality improvements and security fixes. Key updates to Surface Hub, not already outlined in [Windows 10 Update History](https://support.microsoft.com/help/4018124/windows-10-update-history), include:
-
- * Update to Surface Hub 2S Recovery Settings page to accurately reflect recovery options.
- * Update to Surface Hub 2S Welcome screen to improve device recognizability.
- * Addressed an issue with the Windows Team Edition shell background displaying incorrectly.
- * Addressed an issue with Start Menu layout persistence when configured using MDM policy.
- * Fixed an issue in Microsoft Edge that occurs when browsing some internal websites.
- * Fixed an issue in Skype for Business that occurs when presenting in full-screen mode.
-
-Please refer to the [Surface Hub Admin guide](https://docs.microsoft.com/surface-hub/) for enabling/disabling device features and services.
-*[KB4503289](https://support.microsoft.com/help/4503289)
-
-
-
-August 17, 2019—update for Team edition based on KB4512474* (OS Build 15063.2021)
-
-This update to the Surface Hub includes quality improvements and security fixes. Key updates to Surface Hub, not already outlined in [Windows 10 Update History](https://support.microsoft.com/help/4018124/windows-10-update-history), include:
-
- * Ensures that Video Out on Hub 2S defaults to "Duplicate" mode.
- * Improves reliability for some Arabic language usage scenarios on Surface Hub.
-
-Please refer to the [Surface Hub Admin guide](https://docs.microsoft.com/surface-hub/) for enabling/disabling device features and services.
-*[KB4503289](https://support.microsoft.com/help/4503289)
-
-
-
-June 18, 2019—update for Team edition based on KB4503289* (OS Build 15063.1897)
-
-This update to the Surface Hub includes quality improvements and security fixes. Key updates to Surface Hub, not already outlined in [Windows 10 Update History](https://support.microsoft.com/help/4018124/windows-10-update-history), include:
-
-* Addresses an issue preventing a user from signing in to a Microsoft Surface Hub device with an Azure Active Directory account. This issue occurs because a previous session did not end successfully.
-* Adds support for TLS 1.2 connections to identity providers and Exchange in device account setup scenarios.
-* Fixes to improve reliability of Hardware Diagnostic App on Hub 2S.
-* Fix to improve consistency of first-run setup experience on Hub 2S.
-
-Please refer to the [Surface Hub Admin guide](https://docs.microsoft.com/surface-hub/) for enabling/disabling device features and services.
-*[KB4503289](https://support.microsoft.com/help/4503289)
-
-
-
-May 28, 2019—update for Team edition based on KB4499162* (OS Build 15063.1835)
-
-This update to the Surface Hub includes quality improvements and security fixes. Key updates to Surface Hub, not already outlined in [Windows 10 Update History](https://support.microsoft.com/help/4018124/windows-10-update-history), include:
-
-* Ensures that Surface Hub users aren't prompted to enter proxy credentials after the "Use device account credentials" feature has been enabled.
-* Resolves an issue where Skype connections fail periodically because audio/video isn't using the correct proxy.
-* Adds support for TLS 1.2 in Skype for Business.
-* Resolves a SIP connection failure in the Skype client when the Skype server has TLS 1.0 or TLS 1.1 disabled.
-
-Please refer to the [Surface Hub Admin guide](https://docs.microsoft.com/surface-hub/) for enabling/disabling device features and services.
-*[KB4499162](https://support.microsoft.com/help/4499162)
-
-
-
-April 25, 2019—update for Team edition based on KB4493436* (OS Build 15063.1784)
-
-This update to the Surface Hub includes quality improvements and security fixes. Key updates to Surface Hub, not already outlined in [Windows 10 Update History](https://support.microsoft.com/help/4018124/windows-10-update-history), include:
-
-* Resolves video and audio sync issue with some USB devices that are connected to the Surface Hub.
-
-Please refer to the [Surface Hub Admin guide](https://docs.microsoft.com/surface-hub/) for enabling/disabling device features and services.
-*[KB4493436](https://support.microsoft.com/help/4493436)
-
-
-
-November 27, 2018—update for Team edition based on KB4467699* (OS Build 15063.1478)
-
-This update to the Surface Hub includes quality improvements and security fixes. Key updates to Surface Hub, not already outlined in [Windows 10 Update History](https://support.microsoft.com/help/4018124/windows-10-update-history), include:
-
-* Addresses an issue that prevents some users from Signing-In to “My Meetings and Files.”
-
-Please refer to the [Surface Hub Admin guide](https://docs.microsoft.com/surface-hub/) for enabling/disabling device features and services.
-*[KBKB4467699](https://support.microsoft.com/help/KB4467699)
-
-
-
-October 18, 2018 —update for Team edition based on KB4462939* (OS Build 15063.1418)
-
-This update to the Surface Hub includes quality improvements and security fixes. Key updates to Surface Hub, not already outlined in [Windows 10 Update History](https://support.microsoft.com/help/4018124/windows-10-update-history), include:
-
-* Skype for Business fixes:
- * Resolves Skype for Business connection issue when resuming from sleep
- * Resolves Skype for Business network connection issue, when device is connected to Internet
- * Resolves Skype for Business crash when searching for users from directory
-* Resolves issue where the Hub mistakenly reports “No Internet connection” in enterprise proxy environments.
-* Implemented a feature allowing customers to op-in to a new Whiteboard experience.
-
-Please refer to the [Surface Hub Admin guide](https://docs.microsoft.com/surface-hub/) for enabling/disabling device features and services.
-*[KB4462939](https://support.microsoft.com/help/4462939)
-
-
-
-August 31, 2018 —update for Team edition based on KB4343889* (OS Build 15063.1292)
-
-This update to the Surface Hub includes quality improvements and security fixes. Key updates to Surface Hub, not already outlined in [Windows 10 Update History](https://support.microsoft.com/help/4018124/windows-10-update-history), include:
-
-* Adds support for Microsoft Teams
-* Resolves task management issue with Intune registration
-* Enables Administrators to disable Instant Messaging and Email services for the Hub
-* Additional bug fixes and reliability improvements for the Surface Hub Skype for Business App
-
-Please refer to the [Surface Hub Admin guide](https://docs.microsoft.com/surface-hub/) for enabling/disabling device features and services.
-*[KB4343889](https://support.microsoft.com/help/4343889)
-
-
-
-June 21, 2018 —update for Team edition based on KB4284830* (OS Build 15063.1182)
-
-This update to the Surface Hub includes quality improvements and security fixes. Key updates to Surface Hub, not already outlined in [Windows 10 Update History](https://support.microsoft.com/help/4018124/windows-10-update-history), include:
-
-* Telemetry change in support of GDPR requirements in EMEA
-
-Please refer to the [Surface Hub Admin guide](https://docs.microsoft.com/surface-hub/) for enabling/disabling device features and services.
-*[KB4284830](https://support.microsoft.com/help/KB4284830)
-
-
-
-April 17, 2018 —update for Team edition based on KB4093117* (OS Build 15063.1058)
-
-This update to the Surface Hub includes quality improvements and security fixes. Key updates to Surface Hub, not already outlined in [Windows 10 Update History](https://support.microsoft.com/help/4018124/windows-10-update-history), include:
-
-* Resolves a wired projection issue
-* Enables bulk update for certain MDM (Mobile Device Management) policies
-* Resolves phone dialer issue with international calls
-* Addresses image resolution issue when 2 Surface Hubs join the same meeting
-* Resolves OMS (Operations Management Suite) certificate handling error
-* Addresses a security issue when cleaning up at the end of a session
-* Addresses Miracast issue, when Surface Hub is specified to channels 149 through 165
- * Channels 149 through 165 will continue to be unusable in Europe, Japan or Israel due to regional governmental regulations
-
-Please refer to the [Surface Hub Admin guide](https://docs.microsoft.com/surface-hub/) for enabling/disabling device features and services.
-*[KB4093117](https://support.microsoft.com/help/4093117)
-
-
-
-February 23, 2018 —update for Team edition based on KB4077528* (OS Build 15063.907)
-
-This update to the Surface Hub includes quality improvements and security fixes. Key updates to Surface Hub, not already outlined in [Windows 10 Update History](https://support.microsoft.com/help/4018124/windows-10-update-history), include:
-
-* Resolved an issue where MDM settings were not being correctly applied
-* Improved Cleanup process
-
-Please refer to the [Surface Hub Admin guide](https://docs.microsoft.com/surface-hub/) for enabling/disabling device features and services.
-*[KB4077528](https://support.microsoft.com/help/4077528)
-
-
-
-January 16, 2018 —update for Team edition based on KB4057144* (OS Build 15063.877)
-
-This update to the Surface Hub includes quality improvements and security fixes. Key updates to Surface Hub, not already outlined in [Windows 10 Update History](https://support.microsoft.com/help/4018124/windows-10-update-history), include:
-
-* Adds ability to manage Start Menu tile layout via MDM
-* MDM bug fix on password rotation configuration
-
-Please refer to the [Surface Hub Admin guide](https://docs.microsoft.com/surface-hub/) for enabling/disabling device features and services.
-*[KB4057144](https://support.microsoft.com/help/4057144)
-
-
-
-December 12, 2017 —update for Team edition based on KB4053580* (OS Build 15063.786)
-
-This update to the Surface Hub includes quality improvements and security fixes. Key updates to Surface Hub, not already outlined in [Windows 10 Update History](https://support.microsoft.com/help/4018124/windows-10-update-history), include:
-
-* Resolves camera video flashes (tearing or flickers) during Skype for Business calls
-* Resolves Notification Center SSD ID issue
-
-Please refer to the [Surface Hub Admin guide](https://docs.microsoft.com/surface-hub/) for enabling/disabling device features and services.
-*[KB4053580](https://support.microsoft.com/help/4053580)
-
-
-
-November 14, 2017 —update for Team edition based on KB4048954* (OS Build 15063.726)
-
-This update to the Surface Hub includes quality improvements and security fixes. Key updates to Surface Hub, not already outlined in [Windows 10 Update History](https://support.microsoft.com/help/4018124/windows-10-update-history), include:
-
-* Feature update that allows customers to enable 802.1x wired network authentication using MDM policy.
-* A feature update that enables users to dynamically select an application of their choice when opening a file.
-* Fix that ensures that End Session cleanup fully removes all connections between the user’s account and the device.
-* Performance fix that improves cleanup time as well as Miracast connection time.
-* Introduces Easy Authentication utilization during ad-hock meetings.
-* Fix that ensures service components to use the same proxy that is configured across the device.
-* Reduces and more thoroughly secures the telemetry transmitted by the device, reducing bandwidth utilization.
-* Enables a feature allowing users to provide feedback to Microsoft after a meeting concludes.
-
-Please refer to the [Surface Hub Admin guide](https://docs.microsoft.com/surface-hub/) for enabling/disabling device features and services.
-*[KB4048954](https://support.microsoft.com/help/4048954)
-
-
-
-October 10, 2017 —update for Team edition based on KB4041676* (OS Build 15063.674)
-
-This update to the Surface Hub includes quality improvements and security fixes. Key updates to Surface Hub, not already outlined in [Windows 10 Update History](https://support.microsoft.com/help/4018124/windows-10-update-history), include:
-
-* Skype for Business
- * Resolves issue that required a device reboot when resuming from sleep.
- * Fixes issue where external contacts did not resolve through Skype Online Hub account.
-* PowerPoint
- * Fixes problem where some PowerPoint presentations would not project on Hub.
-* General
- * Fix to resolve issue where USB port could not be disabled by System Administrator.
-
-*[KB4041676](https://support.microsoft.com/help/4041676)
-
-
-
-September 12, 2017 —update for Team edition based on KB4038788* (OS Build 15063.605)
-
-This update to the Surface Hub includes quality improvements and security fixes. Key updates to Surface Hub, not already outlined in [Windows 10 Update History](https://support.microsoft.com/help/4018124/windows-10-update-history), include:
-
-* Security
- * Resolves issue with Bitlocker when device wakes from sleep.
-* General
- * Reduces frequency/amount of device health telemetry, improving system performance.
- * Fixes issue that prevented device from collecting system logs.
-
-*[KB4038788](https://support.microsoft.com/help/4038788)
-
-
-
-August 1, 2017 — update for Team edition based on KB4032188* (OS Build 15063.498)
-
-* Skype for Business
- * Resolves Skype for Business Sign-In issue, which required retry or system reboot.
- * Resolves Skype for Business meeting time being incorrectly displayed.
- * Fixes to improve Surface Hub Skype for Business reliability.
-
-*[KB4032188](https://support.microsoft.com/help/4032188)
-
-
-
-June 27, 2017 — update for Team edition based on KB4022716* (OS Build 15063.442)
-
-This update to the Surface Hub includes quality improvements and security fixes. Key updates to Surface Hub, not already outlined in [Windows 10 Update History](https://support.microsoft.com/help/4018124/windows-10-update-history), include:
-
-* Address NVIDIA driver crashes that may necessitate sleeping 84” Surface Hub to power down, requiring a manual restart.
-* Resolved an issue where some apps fail to launch on an 84” Surface Hub.
-
-*[KB4022716](https://support.microsoft.com/help/4022716)
-
-
-
-June 13, 2017 — update for Team edition based on KB4022725* (OS Build 15063.413)
-
-This update to the Surface Hub includes quality improvements and security fixes. Key updates to Surface Hub, not already outlined in [Windows 10 Update History](https://support.microsoft.com/help/4018124/windows-10-update-history), include:
-
-* General
- * Resolved Pen ink dropping issues with pens
- * Resolved issue causing extended time to “cleanup” meeting
-
-*[KB4022725](https://support.microsoft.com/help/4022725)
-
-
-
-May 24, 2017 — update for Team edition based on KB4021573* (OS Build 15063.328)
-
-This update to the Surface Hub includes quality improvements and security fixes. Key updates to Surface Hub, not already outlined in [Windows 10 Update History](https://support.microsoft.com/help/4018124/windows-10-update-history), include:
-
-* General
- * Resolved issue with proxy setting retention during update issue
-
-*[KB4021573](https://support.microsoft.com/help/4021573)
-
-
-
-May 9, 2017 — update for Team edition based on KB4016871* (OS Build 15063.296)
-
-This update to the Surface Hub includes quality improvements and security fixes. Key updates to Surface Hub, not already outlined in [Windows 10 Update History](https://support.microsoft.com/help/4018124/windows-10-update-history), include:
-
-* General
- * Addressed sleep/wake cycle issue
- * Resolved several Reset and Recovery issues
- * Addressed Update History tab issue
- * Resolved Miracast service launch issue
-* Apps
- * Fixed App package update error
-
-*[KB4016871](https://support.microsoft.com/help/4016871)
-
-
-
-Windows 10 Team Creators Update 1703 for Surface Hub — General Release notes (OS Build 15063.0)
-
-This update to the Surface Hub includes quality improvements and security fixes. Key updates to Surface Hub, not already outlined in [Windows 10 Update History](https://support.microsoft.com/help/4018124/windows-10-update-history), include:
-
-* Evolving the large screen experience
- * Improved the meeting carousel in Welcome and Start
- * Join meetings and end the session directly from the Start menu
- * Apps can utilize more of the screen during a session
- * Simplified Skype controls
- * Improved mechanisms for providing feedback
-* Access My Personal Content*
- * Personal single sign-on from Welcome or Start
- * Join meetings and end the session directly from the Start menu
- * Access personal files through OneDrive for Business directly from Start
- * Pre-populated attendee sign-in
- * Streamlined authentication flows with “Authenticator” app**
-* Deployment & Manageability
- * Simplified OOBE experience through bulk provisioning
- * Cloud-based device recovery service
- * Enterprise client certificate support
- * Improved proxy credential support
- * Added and /improved Skype Quality of Service (QoS) configuration support
- * Added ability to set default device volume in Settings
- * Improved MDM support for Surface Hub [settings](https://docs.microsoft.com/surface-hub/remote-surface-hub-management)
-* Improved Security
- * Added ability to restrict USB drives to BitLocker only
- * Added ability to disable USB ports via MDM
- * Added ability to disable “Resume session” functionality on timeout
- * Addition of wired 802.1x support
-* Audio and Projection
- * Dolby Audio “Human Speaker” enhancements
- * Reduced “pen tap” sounds when using Pen during Skype for Business calls
- * Added support for Miracast infrastructure connections
-* Reliability and Performance fixes
- * Resolved several Reset and Recovery issues
- * Resolved Surface Hub Exchange authentication issue when utilizing client certificates
- * Improved Wi-Fi network connection and credentials stability
- * Fixed Miracast audio popping and sync issues during video playback
- * Included setting to disable auto connect behavior
-
-*Single sign-in feature requires use of Office365 and OneDrive for Business
-**Refer to Admin Guide for service requirements
-
-
-
-## Windows 10 Team Anniversary Update 1607
-
-
-March 14th, 2017 — update for Team edition based on KB4013429* (OS Build 14393.953)
-
-This update to the Surface Hub includes quality improvements and security fixes. Key updates to Surface Hub, not already outlined in [Windows 10 Update History](https://support.microsoft.com/help/4018124/windows-10-update-history), include:
-
-* General
- * Security fix for File Explorer to prevent navigation to restricted file locations
-* Skype for Business
- * Fix to address latency during Remote Desktop based screen sharing
-
-*[KB4013429](https://support.microsoft.com/help/4013429)
-
-
-
-January 10th, 2017 — update for Team edition based on KB4000825* (OS Build 14393.693)
-
-This update to the Surface Hub includes quality improvements and security fixes. Key updates to Surface Hub, not already outlined in [Windows 10 Update History](https://support.microsoft.com/help/4018124/windows-10-update-history), include:
-
-* Enabled selection of 106/109 Keyboard Layouts for use with physical Japanese keyboards
-
-*[KB4000825](https://support.microsoft.com/help/4000825)
-
-
-
-December 13, 2016 — update for Team edition based on KB3206632* (OS Build 14393.576)
-
-This update to the Surface Hub includes quality improvements and security fixes. Key updates to Surface Hub, not already outlined in [Windows 10 Update History](https://support.microsoft.com/help/4018124/windows-10-update-history), include:
-
-* Resolves wired connection audio distortion issue
-
-*[KB3206632](https://support.microsoft.com/help/3206632)
-
-
-
-November 4, 2016 — update for Windows 10 Team Anniversary edition based on KB3200970* (OS Build 14393.447)
-
-This update to the Windows 10 Team Anniversary Update (version 1607) for Surface Hub includes quality improvements and security fixes. Key updates to Surface Hub, not already outlined in [Windows 10 Update History](https://support.microsoft.com/help/4018124/windows-10-update-history), include:
-
-* Skype for Business bug fixes to improve reliability
-
-*[KB3200970](https://support.microsoft.com/help/3200970)
-
-
-
-October 25, 2016 — update for Team edition based on KB3197954* (OS Build 14393.351)
-
-This update to the Surface Hub includes quality improvements and security fixes. Key updates to Surface Hub, not already outlined in [Windows 10 Update History](https://support.microsoft.com/help/4018124/windows-10-update-history), include:
-
-* Enabling new Sleep feature in OS and Bios to reduce the Surface Hub’s power consumption and improve its long-term reliability
-* General
- * Resolves scenarios where the on-screen keyboard would sometimes not appear
- * Resolves Whiteboard application shift that occasionally occurs when opening scheduled meeting
- * Resolves issue that prevented Admins from changing the local administrator password, after device has been Reset
- * BIOS change resolving issue with status bar tracking during device Reset
- * UEFI update to resolve powering down issues
-
-*[KB3197954](https://support.microsoft.com/help/3197954)
-
-
-
-October 11, 2016 — update for Team edition based on KB3194496* (OS Build 14393.222)
-
-This update brings the Windows 10 Team Anniversary Update to Surface Hub and includes quality improvements and security fixes. (Your device will be running Windows 10 Version 1607 after it's installed.) Key updates to Surface Hub, not already outlined in [Windows 10 Update History](https://support.microsoft.com/help/4018124/windows-10-update-history), include:
-
-* Skype for Business
- * Performance improvements when joining meetings, including issues when joining a meeting using federated accounts
- * Video Based Screen Sharing (VBSS) support now available on Skype for Business for Surface Hub
- * Resolved disconnection after 5 minutes of idle time issue
- * Resolved Skype Hub-to-Hub screen sharing failure
- * Improvements to Skype video, including:
- * Loss of video during meeting with multiple video presenters
- * Video cropping during calls
- * Outgoing call video not displaying for other participants
- * Addressed issue with UPN sign in error
- * Addressed issue with dial pad during use of Session Initiation Protocol (SIP) calls
-* Whiteboard
- * User can now save and recall Whiteboard sessions using OneDrive online service (via Share functionality)
- * Improved launching Whiteboard when removing pen from dock
-* Apps
- * Pre-installed OneDrive app, for access to your personal and work files
- * Pre-installed Photos app, to view photos and video
- * Pre-installed PowerBI app, to view dashboards
- * The Office apps – Word, Excel, PowerPoint – are all ink-enabled
- * Edge on Surface Hub now supports Flash-based websites
-* General
- * Enabled Audio Device Selection (for Surface Hubs attached using external audio devices)
- * Enabled support for HDCP on DisplayPort output connector
- * System UI changes to settings for usability optimization (refer to [User and Admin Guides](https://www.microsoft.com/surface/support/surface-hub) for additional details)
- * Bug fixes and performance optimizations to speed up the Azure Active Directory sign-in flow
- * Significantly improved time needed to reset and restore Surface Hub
- * Windows Defender UI has been added within settings
- * Improved UX touch to start
- * Enabled support for greater than 1080p wireless projection via Miracast, on supported devices
- * Resolved “There’s no internet connection” and “Appointments may be out of date” false notification states from launch
- * Improved reliability of on-screen keyboard
- * Additional support for creating Surface Hub provisioning packages using Windows Imaging & Configuration Designer (ICD) and improved Surface Hub monitoring solution on Operations Management Suite (OMS)
-
-*[KB3194496](https://support.microsoft.com/help/3194496)
-
-
-## Updates for Windows 10 Version 1511
-
-
-November 4, 2016 — update for Windows 10 Team (version 1511) on KB3198586* (OS Build 10586.679)
-
-This update to the Windows 10 Team edition (version 1511) to Surface Hub includes quality improvements and security fixes that are outlined in [Windows 10 Update History](https://support.microsoft.com/help/4018124/windows-10-update-history). There are no Surface Hub specific items in this update.
-
-*[KB3198586](https://support.microsoft.com/help/3198586)
-
-
-
-July 12, 2016 — KB3172985* (OS Build 10586.494)
-
-This update includes quality improvements and security fixes. No new operating system features are being introduced in this update. Key changes specific to the Surface Hub (those not already included in the [Windows 10 Update History](https://support.microsoft.com/help/4018124/windows-10-update-history)), include:
-
-* Fixed issue that caused Windows system crashes
-* Fixed issue that caused repeated Edge crashes
-* Fixed issue causing pre-shutdown service crashes
-* Fixed issue where some app data wasn’t properly removed after a session
-* Updated Broadcom NFC driver to improve NFC performance
-* Updated Marvell Wi-Fi driver to improve Miracast performance
-* Updated Nvidia driver to fix a display bug in which 84" Surface Hub devices show dim or fuzzy content
-* Numerous Skype for Business issues fixed, including:
- * Issue that caused Skype for Business to disconnect during meetings
- * Issue in which users were unable to join meetings when the meeting organizer was on a federated configuration
- * Enabling Skype for Business application sharing
- * Issue that caused Skype application crashes
-* Added a prompt in “Settings” to inform users that the OS can become corrupted if device reset is interrupted before completion
-
-*[KB3172985](https://support.microsoft.com/help/3172985)
-
-
-
-June 14, 2016 — KB3163018* (OS Build 10586.420)
-
-This update to the Surface Hub includes quality improvements and security fixes. No new operating system features are being introduced in this update. Key updates to Surface Hub, not already outlined in [Windows 10 Update History](https://support.microsoft.com/help/4018124/windows-10-update-history), include:
-
-* Constrained release. Refer to July 12, 2016 — [KB3172985](https://support.microsoft.com/en-us/help/3172985) (OS Build 10586.494) for Surface Hub specific package details
-
-*[KB3163018](https://support.microsoft.com/help/3163018)
-
-
-
-May 10, 2016 — KB3156421* (OS Build 10586.318)
-
-This update to the Surface Hub includes quality improvements and security fixes. No new operating system features are being introduced in this update. Key updates to Surface Hub, not already outlined in [Windows 10 Update History](https://support.microsoft.com/help/4018124/windows-10-update-history), include:
-
-* Fixed issue that prevented certain Store apps (OneDrive) from installing
-* Fixed issue that caused touch input to stop responding in applications
-
-*[KB3156421](https://support.microsoft.com/help/3156421)
-
-
-
-April 12, 2016 — KB3147458* (OS Build 10586.218)
-
-This update to the Surface Hub includes quality improvements and security fixes. No new operating system features are being introduced in this update. Key updates to Surface Hub, not already outlined in [Windows 10 Update History](https://support.microsoft.com/help/4018124/windows-10-update-history), include:
-
-* Fixed issue where volume level wasn’t properly reset between sessions
-
-*[KB3147458](https://support.microsoft.com/help/3147458)
-
-
-## Related topics
-
-* [Windows 10 release information](https://go.microsoft.com/fwlink/p/?LinkId=724328)
-* [Windows 10 November update: FAQ](https://windows.microsoft.com/windows-10/windows-update-faq)
-* [Microsoft Surface update history](https://go.microsoft.com/fwlink/p/?LinkId=724327)
-* [Microsoft Lumia update history](https://go.microsoft.com/fwlink/p/?LinkId=785968)
-* [Get Windows 10](https://go.microsoft.com/fwlink/p/?LinkId=616447)
diff --git a/devices/surface-hub/surface-hub-wifi-direct.md b/devices/surface-hub/surface-hub-wifi-direct.md
deleted file mode 100644
index fc1ada3230..0000000000
--- a/devices/surface-hub/surface-hub-wifi-direct.md
+++ /dev/null
@@ -1,122 +0,0 @@
----
-title: How Surface Hub addresses Wi-Fi Direct security issues
-description: Guidance about Wi-Fi Direct security risks.
-keywords: change history
-ms.prod: surface-hub
-ms.sitesec: library
-author: dansimp
-ms.author: dansimp
-ms.topic: article
-ms.date: 11/27/2019
-ms.reviewer:
-manager: laurawi
-ms.localizationpriority: medium
----
-
-# How Surface Hub addresses Wi-Fi Direct security issues
-
-Microsoft Surface Hub is an all-in-one productivity device that enables teams to better brainstorm, collaborate, and share ideas. Surface Hub relies on Miracast for wireless projection through Wi-Fi Direct.
-
-This article describes Wi-Fi Direct security vulnerabilities, how Surface Hub addresses those risks, and how administrators can configure Surface Hub for the highest level of security. This information will help customers who have high security requirements protect their Surface Hub-connected networks and data in transit.
-
-The intended audiences for this article are IT and network administrators who want to deploy Surface Hub in their corporate environment with optimal security settings.
-
-## Overview
-
-Security for Surface Hub depends extensively on Wi-Fi Direct/Miracast and the associated 802.11, Wi-Fi Protected Access (WPA2), and Wireless Protected Setup (WPS) standards. Because the device only supports WPS (as opposed to WPA2 Pre-Shared Key [PSK] or WPA2 Enterprise), the issues often associated with 802.11 encryption are simplified.
-
-Surface Hub operates on par with the field of Miracast receivers. So, it's vulnerable to a similar set of exploits as all WPS-based wireless network devices. But the Surface Hub implementation of WPS has extra precautions built in. Also, its internal architecture helps prevent an attacker who has compromised the Wi-Fi Direct/Miracast layer from moving past the network interface onto other attack surfaces and connected enterprise networks.
-
-## Wi-Fi Direct background
-
-Miracast is part of the Wi-Fi Display standard, which is supported by the Wi-Fi Direct protocol. These standards are supported in modern mobile devices for screen sharing and collaboration.
-
-Wi-Fi Direct or Wi-Fi "peer to peer" (P2P) is a standard from the Wi-Fi Alliance for "Ad-Hoc" networks. Supported devices can communicate directly and create groups of networks without a conventional Wi-Fi access point or Internet connection.
-
-Security for Wi-Fi Direct is provided by WPA2 under the WPS standard. The authentication mechanism for devices can be a numerical pin (WPS-PIN), a physical or virtual push button (WPS-PBC), or an out-of-band message such as near field communication (WPS-OOO). Surface Hub supports both the PIN method and the push-button method, which is the default.
-
-In Wi-Fi Direct, groups are created as one of the following types:
-- *Persistent*, in which automatic reconnection can occur by using stored key material
-- *Temporary*, in which devices can't re-authenticate without user action
-
-Wi-Fi Direct groups determine a *group owner* (GO) through a negotiation protocol, which mimics the "station" or "access point" functionality for the established Wi-Fi Direct group. The Wi-Fi Direct GO provides authentication (via an "internal registrar") and facilitates upstream network connections. For Surface Hub, this GO negotiation doesn't occur. The network only operates in "autonomous" mode, and Surface Hub is always the group owner. Finally, Surface Hub itself doesn't join other Wi-Fi Direct networks as a client.
-
-## How Surface Hub addresses Wi-Fi Direct vulnerabilities
-
-**Vulnerabilities and attacks in the Wi-Fi Direct invitation, broadcast, and discovery process:** Wi-Fi Direct/Miracast attacks may target weaknesses in the group establishment, peer discovery, device broadcast, or invitation processes.
-
-|Wi-Fi Direct vulnerability | Surface Hub mitigation |
-| --- | --- |
-| The discovery process may remain active for an extended period of time, which could allow invitations and connections to be established without the approval of the device owner. | Surface Hub only operates as the group owner, which doesn't perform the client discovery or GO negotiation processes. You can fully disable wireless projection to turn off broadcast. |
-| Invitation and discovery through PBC allows an unauthenticated attacker to perform repeated connection attempts, or unauthenticated connections are automatically accepted. | By requiring WPS PIN security, administrators can reduce the potential for such unauthorized connections or "invitation bombs," in which invitations are repeatedly sent until a user mistakenly accepts one. |
-
-**Wi-Fi Protected Setup (WPS) push button connect (PBC) vs PIN entry:** Public weaknesses have been demonstrated in WPS-PIN method design and implementation. WPS-PBC has other vulnerabilities that could allow active attacks against a protocol that's designed for one-time use.
-
-| Wi-Fi Direct vulnerability | Surface Hub mitigation |
-| --- | --- |
-| WPS-PBC is vulnerable to active attackers. The WPS specification states: "The PBC method has zero bits of entropy and only protects against passive eavesdropping attacks. PBC protects against eavesdropping attacks and takes measures to prevent a device from joining a network that was not selected by the device owner. The absence of authentication, however, means that PBC does not protect against active attack." Attackers can use selective wireless jamming or other denial-of-service techniques to trigger an unintended Wi-Fi Direct GO or connection. Also, an active attacker who merely has physical proximity can repeatedly tear down any Wi-Fi Direct group and attempt the attack until it succeeds. | Enable WPS-PIN security in Surface Hub configuration. The Wi-Fi WPS specification states: "The PBC method should only be used if no PIN-capable registrar is available and the WLAN user is willing to accept the risks associated with PBC." |
-| WPS-PIN implementations can be subject to brute-force attacks that target a vulnerability in the WPS standard. The design of split PIN verification led to multiple implementation vulnerabilities over the past several years across a range of Wi-Fi hardware manufacturers. In 2011, researchers Stefan Viehböck and Craig Heffner released information about this vulnerability and tools such as "Reaver" as a proof of concept. | The Microsoft implementation of WPS in Surface Hub changes the PIN every 30 seconds. To crack the PIN, an attacker must complete the entire exploit in less than 30 seconds. Given the current state of tools and research in this area, a brute-force PIN-cracking attack through WPS is unlikely to succeed. |
-| WPS-PIN can be cracked by an offline attack because of weak initial key (E-S1,E S2) entropy. In 2014, Dominique Bongard described a "Pixie Dust" attack where poor initial randomness for the pseudo random number generator (PRNG) in the wireless device allowed an offline brute-force attack. | The Microsoft implementation of WPS in Surface Hub is not susceptible to this offline PIN brute-force attack. The WPS-PIN is randomized for each connection. |
-
-**Unintended exposure of network services:** Network daemons that are intended for Ethernet or WLAN services may be accidentally exposed because of misconfiguration (such as binding to "all"/0.0.0.0 interfaces). Other possible causes include a poorly configured device firewall or missing firewall rules.
-
-| Wi-Fi Direct vulnerability | Surface Hub mitigation |
-| --- | --- |
-| Misconfiguration binds a vulnerable or unauthenticated network service to "all" interfaces, which includes the Wi-Fi Direct interface. This can expose services that shouldn't be accessible to Wi-Fi Direct clients, which may be weakly or automatically authenticated. | In Surface Hub, the default firewall rules only permit the required TCP and UDP network ports and by default deny all inbound connections. Configure strong authentication by enabling the WPS-PIN mode.|
-
-**Bridging Wi-Fi Direct and other wired or wireless networks:** Network bridging between WLAN or Ethernet networks is a violation of the Wi-Fi Direct specification. Such a bridge or misconfiguration may effectively lower or remove wireless access controls for the internal corporate network.
-
-| Wi-Fi Direct vulnerability | Surface Hub mitigation |
-| --- | --- |
-| Wi-Fi Direct devices could allow unauthenticated or poorly authenticated access to bridged network connections. This might allow Wi-Fi Direct networks to route traffic to internal Ethernet LAN or other infrastructure or to enterprise WLAN networks in violation of existing IT security protocols. | Surface Hub can't be configured to bridge wireless interfaces or allow routing between disparate networks. The default firewall rules add defense in depth to any such routing or bridge connections. |
-
-**The use of Wi-Fi Direct "legacy" mode:** Exposure to unintended networks or devices may occur when you operate in "legacy" mode. Device spoofing or unintended connections could occur if WPS-PIN is not enabled.
-
-| Wi-Fi Direct vulnerability | Surface Hub mitigation |
-| --- | --- |
-| By supporting both Wi-Fi Direct and 802.11 infrastructure clients, the system is operating in a "legacy" support mode. This may expose the connection-setup phase indefinitely, allowing groups to be joined or devices invited to connect well after their intended setup phase terminates. | Surface Hub doesn't support Wi-Fi Direct legacy clients. Only Wi-Fi Direct connections can be made to Surface Hub even when WPS-PIN mode is enabled. |
-
-**Wi-Fi Direct GO negotiation during connection setup:** The group owner in Wi-Fi Direct is analogous to the "access point" in a conventional 802.11 wireless network. The negotiation can be gamed by a malicious device.
-
-|Wi-Fi Direct vulnerability | Surface Hub mitigation |
-| --- | --- |
-| If groups are dynamically established or the Wi-Fi Direct device can be made to join new groups, the group owner negotiation can be won by a malicious device that always specifies the maximum group owner "intent" value of 15. (But the connection fails if the device is configured to always be a group owner.) | Surface Hub takes advantage of Wi-Fi Direct "Autonomous mode," which skips the GO negotiation phase of connection setup. And Surface Hub is always the group owner. |
-
-**Unintended or malicious Wi-Fi deauthentication:** Wi-Fi deauthentication is an old attack in which a local attacker can expedite information leaks in the connection-setup process, trigger new four-way handshakes, target Wi-Fi Direct WPS-PBC for active attacks, or create denial-of-service attacks.
-
-| Wi-Fi Direct vulnerability | Surface Hub mitigation |
-| --- | --- |
-| Deauthentication packets can be sent by an unauthenticated attacker to cause the station to re-authenticate then to sniff the resulting handshake. Cryptographic or brute-force attacks can be attempted on the resulting handshake. Mitigation for these attack includes enforcing length and complexity policies for pre-shared keys, configuring the access point (if applicable) to detect malicious levels of deauthentication packets, and using WPS to automatically generate strong keys. In PBC mode, the user interacts with a physical or virtual button to allow arbitrary device association. This process should happen only at setup, within a short window. After the button is automatically "pushed," the device will accept any station that associates via a canonical PIN value (all zeros). Deauthentication can force a repeated setup process. | Surface Hub uses WPS in PIN or PBC mode. No PSK configuration is permitted. This method helps enforce generation of strong keys. It's best to enable WPS-PIN security for Surface Hub. |
-| In addition to denial-of-service attacks, deauthentication packets can be used to trigger a reconnect that re-opens the window of opportunity for active attacks against WPS-PBC. | Enable WPS-PIN security in the Surface Hub configuration. |
-
-**Basic wireless information disclosure:** Wireless networks, 802.11 or otherwise, are inherently at risk of information disclosure. Although this information is mostly connection or device metadata, this problem remains a known risk for any 802.11 network administrator. Wi-Fi Direct with device authentication via WPS-PIN effectively reveals the same information as a PSK or Enterprise 802.11 network.
-
-| Wi-Fi Direct vulnerability | Surface Hub mitigation |
-| --- | --- |
-| During broadcast, connection setup, or even normal operation of already-encrypted connections, basic information about devices and packet sizes is wirelessly transmitted. At a basic level, a local attacker who's within wireless range can examine the relevant 802.11 information elements to determine the names of wireless devices, the MAC addresses of communicating equipment, and possibly other details, such as the version of the wireless stack, packet sizes, or the configured access point or group owner options. | The Wi-Fi Direct network that Surface Hub uses can't be further protected from metadata leaks, just like for 802.11 Enterprise or PSK wireless networks. Physical security and removal of potential threats from wireless proximity can help reduce potential information leaks. |
-
-**Wireless evil twin or spoofing attacks:** Spoofing the wireless name is a simple, well-known exploit a local attacker can use to lure unsuspecting or mistaken users to connect.
-
-| Wi-Fi Direct vulnerability | Surface Hub mitigation |
-| --- | --- |
-| By spoofing or cloning the wireless name or "SSID" of the target network, an attacker may trick the user into connecting to a fake, malicious network. By supporting unauthenticated, auto-join Miracast, an attacker could capture the intended display materials or launch network attacks on the connecting device. | While there are no specific protections against joining a spoofed Surface Hub, this vulnerability is partially mitigated in two ways. First, any potential attack must be physically within Wi-Fi range. Second, this attack is only possible during the first connection. Subsequent connections use a persistent Wi-Fi Direct group, and Windows will remember and prioritize this prior connection during future Hub use. (Note: Spoofing the MAC address, Wi-Fi channel, and SSID simultaneously was not considered for this report and may result in inconsistent Wi-Fi behavior.) Overall, this weakness is a fundamental problem for any 802.11 wireless network that lacks Enterprise WPA2 protocols such as EAP-TLS or EAP-PWD, which Wi-Fi Direct doesn't support. |
-
-## Surface Hub hardening guidelines
-
-Surface Hub is designed to facilitate collaboration and allow users to start or join meetings quickly and efficiently. The default Wi-Fi Direct settings for Surface Hub are optimized for this scenario.
-
-For additional wireless interface security, Surface Hub users should enable the WPS-PIN security setting. This setting disables WPS-PBC mode and offers client authentication. It provides the strongest level of protection by preventing unauthorized connection to Surface Hub.
-
-If you still have concerns about authentication and authorization for Surface Hub, we recommend that you connect the device to a separate network. You could use Wi-Fi (such as a "guest" Wi-Fi network) or a separate Ethernet network, preferably an entirely different physical network. But a VLAN can also provide added security. Of course, this approach may preclude connections to internal network resources or services and may require additional network configuration to regain access.
-
-Also recommended:
-- [Install regular system updates](manage-windows-updates-for-surface-hub.md)
-- Update the Miracast settings to disable auto-present mode
-
-## Learn more
-
-- [Wi-Fi Direct specifications](http://www.wi-fi.org/discover-wi-fi/wi-fi-direct)
-- [Wireless Protected Setup (WPS) specification](http://www.wi-fi.org/discover-wi-fi/wi-fi-protected-setup)
-
-
-
diff --git a/devices/surface-hub/surface-hub.yml b/devices/surface-hub/surface-hub.yml
deleted file mode 100644
index dac70e8f37..0000000000
--- a/devices/surface-hub/surface-hub.yml
+++ /dev/null
@@ -1,62 +0,0 @@
-### YamlMime:YamlDocument
-
-documentType: LandingData
-title: Surface Hub
-metadata:
- document_id:
- title: Surface Hub
- description: Find tools and resources to help you install, set up, and manage a Surface Hub in your organization.
- keywords: Surface Hub, Windows 10
- ms.localizationpriority: medium
- author: lizap
- ms.author: elizapo
- manager: dougkim
- ms.topic: article
- ms.devlang: na
-
-sections:
-- items:
- - type: markdown
- text: "
- Find tools and resources to help you install, set up, and manage a Surface Hub in your organization.
- "
-- title: Explore
-- items:
- - type: markdown
- text: "
- Discover how this all-in-one productivity device enables teams to better brainstorm, collaborate, and share ideas.
-
-
- "
-- title: Plan
-- items:
- - type: markdown
- text: "
- Prepare to deploy Surface Hub in your organization. Explore site readiness, assembly, configuration, and Exchange and ActiveSync policies.
-
- "
-- title: Deploy
-- items:
- - type: markdown
- text: "
- Get information for setup, app management and installation, and network management of your Surface Hub.
-
**Surface IT Pro Blog** Get insight into new Surface products plus tips and tricks for IT professionals. Learn more
**Surface on Microsoft Mechanics** View technical demos and walkthroughs of Surface devices, features, and functionality. Get started
**Follow us on Twitter** Keep up with the latest news and see the latest product demonstrations. Visit Twitter
-
- "
diff --git a/devices/surface-hub/surfacehub-miracast-not-supported-europe-japan-israel.md b/devices/surface-hub/surfacehub-miracast-not-supported-europe-japan-israel.md
deleted file mode 100644
index 7a30ff1e37..0000000000
--- a/devices/surface-hub/surfacehub-miracast-not-supported-europe-japan-israel.md
+++ /dev/null
@@ -1,23 +0,0 @@
----
-title: Surface Hub Miracast channels 149-165 not supported in Europe, Japan, Israel
-description: Surface Hub Miracast channels 149-165 not supported in Europe, Japan, Israel
-ms.assetid: 8af3a832-0537-403b-823b-12eaa7a1af1f
-keywords:
-ms.prod: surface-hub
-ms.sitesec: library
-author: v-miegge
-ms.author: v-miegge
-ms.topic: article
-ms.localizationpriority: medium
----
-
-# Summary
-
-In compliance with regional governmental regulations, all 5-GHz wireless devices in Europe, Japan, and Israel do not support the U-NII-3 band. In Surface Hub, the channels that are associated with U-NII-3 are 149 through 165. This includes Miracast connection on these channels. Therefore, Surface Hubs that are used in Europe, Japan, and Israel can't use channels 149 through 165 for Miracast connection.
-
-## More Information
-
-For more information see the [U-NII](https://en.wikipedia.org/wiki/U-NII) topic on Wikipedia.
-
-> [!NOTE]
-> Microsoft provides third-party contact information to help you find additional information about this topic. This information may change without notice. Microsoft does not guarantee the accuracy of third-party information.
\ No newline at end of file
diff --git a/devices/surface-hub/surfacehub-whats-new-1703.md b/devices/surface-hub/surfacehub-whats-new-1703.md
deleted file mode 100644
index 4c324d33ce..0000000000
--- a/devices/surface-hub/surfacehub-whats-new-1703.md
+++ /dev/null
@@ -1,71 +0,0 @@
----
-title: What's new in Windows 10, version 1703 for Surface Hub
-description: Windows 10, version 1703 (Creators Update) brings new features to Microsoft Surface Hub.
-ms.prod: surface-hub
-ms.sitesec: library
-author: dansimp
-ms.author: dansimp
-ms.topic: article
-ms.date: 01/18/2018
-ms.reviewer:
-manager: laurawi
-ms.localizationpriority: medium
----
-
-# What's new in Windows 10, version 1703 for Microsoft Surface Hub?
-
-Watch Surface Hub engineer Jordan Marchese present updates to Microsoft Surface Hub with Windows 10, version 1703 (Creators Update).
-
-
-
-Windows 10, version 1703 (also called the Creators Update), introduces the following changes for Microsoft Surface Hub.
-
-## New settings
-
-Settings have been added to mobile device management (MDM) and configuration service providers (CSPs) to expand the Surface Hub management capabilities. [New settings include](manage-settings-with-mdm-for-surface-hub.md):
-
-- InBoxApps/SkypeForBusiness/DomainName
-- InBoxApps/Connect/AutoLaunch
-- Properties/DefaultVolume
-- Properties/ScreenTimeout
-- Properties/SessionTimeout
-- Properties/SleepTimeout
-- Properties/AllowSessionResume
-- Properties/AllowAutoProxyAuth
-- Properties/DisableSigninSuggestions
-- Properties/DoNotShowMyMeetingsAndFiles
-- System/AllowStorageCard
-
-Plus settings based on the new [NetworkQoSPolicy CSP](https://msdn.microsoft.com/windows/hardware/commercialize/customize/mdm/networkqospolicy-csp) and [NetworkProxy CSP](https://msdn.microsoft.com/windows/hardware/commercialize/customize/mdm/networkproxy-csp).
-
-
-## Provisioning wizard
-
-An easy-to-use wizard helps you quickly create provisioning packages that you can apply to multiple Surface Hub devices, and includes bulk join to Azure Active Directory. [Learn how to create a provisioning package for Surface Hub.](provisioning-packages-for-certificates-surface-hub.md)
-
-
-
-## Miracast on your existing wireless network or LAN
-
-Microsoft has extended the ability to [send a Miracast stream over a local network](miracast-over-infrastructure.md) rather than over a direct wireless link.
-
-## Cloud recovery
-
-When you reset a Surface Hub device, you now have the ability to download and install a factory build of the operating system from the cloud. [Learn more about cloud recovery.](device-reset-surface-hub.md#cloud-recovery)
-
->[!NOTE]
->Cloud recovery doesn't work if you use proxy servers.
-
-
-
-## End session
-
-**I'm done** is now **End session**. [Learn how to use End session.](i-am-done-finishing-your-surface-hub-meeting.md)
-
-
-
-
-
-
-
-
diff --git a/devices/surface-hub/troubleshoot-surface-hub.md b/devices/surface-hub/troubleshoot-surface-hub.md
deleted file mode 100644
index 4a30281eff..0000000000
--- a/devices/surface-hub/troubleshoot-surface-hub.md
+++ /dev/null
@@ -1,619 +0,0 @@
----
-title: Troubleshoot Microsoft Surface Hub
-description: Troubleshoot common problems, including setup issues, Exchange ActiveSync errors.
-ms.assetid: CF58F74D-8077-48C3-981E-FCFDCA34B34A
-ms.reviewer:
-manager: laurawi
-keywords: Troubleshoot common problems, setup issues, Exchange ActiveSync errors
-ms.prod: surface-hub
-ms.sitesec: library
-author: dansimp
-ms.author: dansimp
-ms.topic: article
-ms.date: 03/16/2018
-ms.localizationpriority: medium
----
-
-# Troubleshoot Microsoft Surface Hub
-
-
-Troubleshoot common problems, including setup issues, Exchange ActiveSync errors.
-
-The [Surface Hub Hardware Diagnostic tool](https://www.microsoft.com/store/p/surface-hub-hardware-diagnostic/9nblggh51f2g?rtc=1&activetab=pivot%3aoverviewtab) contains interactive tests which allow you to confirm essential functionality of your Hub is working as expected. In addition to testing hardware, the diagnostic can test the resource account to verify that it is configured properly for your environment. If problems are encountered, results can be saved and shared with the Surface Hub Support Team. For usage information, see [Using the Surface Hub Hardware Diagnostic Tool to test a device account](https://support.microsoft.com/help/4077574/using-the-surface-hub-hardware-diagnostic-tool-to-test-a-device-accoun).
-
-Common issues are listed in the following table, along with causes and possible fixes. The [Setup troubleshooting](#setup-troubleshooting) section contains a listing of on-device problems, along with several types of issues that may be encountered during the first-run experience. The [Exchange ActiveSync errors](#exchange-activesync-errors) section lists common errors the device may encounter when trying to synchronize with an Microsoft Exchange ActiveSync server.
-
-
-
-
-## Setup troubleshooting
-
-
-This section lists causes, and possible fixes to help troubleshoot issues you might find when you set up your Microsoft Surface Hub.
-
-### On-device
-
-Possible fixes for issues on the Surface Hub after you've completed the first-run program.
-
-
-
-
Issue
-
Causes
-
Possible fixes
-
-
-
-
Not receiving automatic accept/decline messages.
-
-
-
The device account isn't configured to automatically accept/decline messages.
-
-
-
Use PowerShell cmdlet Set-CalendarProcessing $upn -AutomateProcessing AutoAccept.
-
-
-
-
-
The device account isn't configured to process external meeting requests.
-
-
-
Use PowerShell cmdlet Set-CalendarProcessing $upn -ProcessExternalMeetingMessages $true.
-
-
-
-
-
Calendar is not showing on the Welcome screen, or message "Appointments of date (no account provisioned)" is being displayed.
-
-
-
No device account is set up on this Surface Hub.
-
-
-
Provision a device account through Settings.
-
-
-
-
-
Calendar is not showing on the Welcome screen or message "Appointments of date (overprovisioned)" is being displayed.
-
-
-
The device account is provisioned on too many devices.
-
-
-
Remove the device account from other devices that it's provisioned to. This can be done using the Exchange admin portal.
-
-
-
-
-
Calendar is not showing on the Welcome screen or message "Appointments of date (invalid credentials)" is being displayed.
-
-
-
The device account's password has expired and is no longer valid.
Calendar is not showing on the Welcome screen or message "Appointments of date (account policy)" is being displayed.
-
-
-
The device account is using an invalid ActiveSync policy.
-
-
-
Make sure the device account has an ActiveSync policy where PasswordEnabled == False.
-
-
-
-
-
Calendar is not showing on the Welcome screen or message "Appointments may be out of date" is being displayed.
-
-
-
Exchange is not enabled.
-
-
Enable the device account for Exchange services through Settings. You need to make sure you have the right set of ActiveSync policies and have also installed any necessary certificates for Exchange services to work.
-
-
-
-
Can't log in to Skype for Business.
-
-
-
The device account does not have a Session Initiation Protocol (SIP) address property.
-
-
-
The account does not have a SIP address property and its User Principal Name (UPN) does not match the actual SIP address. The account must have its SIP address set, or the SIP address should be added using the Settings app.
-
-
-
-
-
Can't log in to Skype for Business.
-
-
-
The device account requires a certificate to authenticate into Skype for Business.
-
-
-
Install the appropriate certificate using provisioning packages.
-
-
-
-
-
-### First run
-
-Possible fixes for issues with Surface Hub first-run program.
-
-
-
-
-
-
-
-
-
-
Issue
-
Causes
-
Possible fixes
-
-
-
-
-
Cannot find account when asked for domain and user name.
-
Domain needs to be the fully qualified domain name (FQDN).
-
The FQDN should be provided in the domain field.
-
-
-
-
-
-
-### Device account page, issues for new account settings
-
-
-
-
-
-
-
-
-
-
Issue
-
Causes
-
Possible fixes
-
-
-
-
-
Unable to find the provided account in Azure AD.
-
The provided account's User Principal Name (UPN) has a tenant that can't be reached in Azure AD.
-
Make sure that you have a working Internet connection, and that the device can reach Microsoft Online Services. Make sure the account credentials are entered correctly.
-
-
-
Unable to reach the specified directory.
-
The provided account domain specifies a domain that can't be reached.
-
Make sure that you have a working network connection, and that the device can reach the domain controller. Make sure the account credentials are entered correctly. You can also try using the FQDN instead.
-
-
-
Can't auto-discover Exchange server.
-
The Exchange server isn't configured for auto-discovery.
-
Enable auto-discovery of the Exchange server for the device account, or enter the account's Exchange server address manually.
-
-
-
Could not discover the SIP address after entering the account credentials.
-
There was no SIP address entry in Active Directory or Azure AD.
-
Make sure the account is enabled with Skype for Business and has a SIP address. If not, you can enter the SIP address manually into the text box.
Account could not authenticate with the specified credentials.
-
-
-
The account is not enabled as a user in Active Directory (AD), needs a password to authenticate, or the password is incorrect.
-
-
-
None
-
-
-
Make sure the credentials are entered correctly. Enable the account as a user in AD and add a password, or set the RoomMailboxPassword
.
-
-
-
-
Error 0x800C0019 is displayed when providing an Exchange server.
-
-
-
The device account requires a certificate to authenticate.
-
-
-
0x800C0019
-
-
-
Install the appropriate certificate using provisioning packages.
-
-
-
-
-
Device account credentials are not valid for the provided Exchange server.
-
-
-
The provided Exchange server is not where the device account's mailbox is hosted.
-
-
-
None
-
-
-
Make sure you are providing the correct Exchange mail server for the device account.
-
-
-
-
-
HTTP timeout while trying to reach Exchange server.
-
-
-
-
0x80072EE2
-
-
-
-
-
-
Couldn't find the provided Exchange server.
-
-
-
The Exchange server provided could not be found.
-
-
-
None
-
-
-
Ensure that you have a working network or Internet connection, and that the Exchange server you provided is correct.
-
-
-
-
-
http not supported.
-
-
-
An Exchange server with http:// instead of https:// was provided.
-
-
-
None
-
-
-
Use an Exchange server that uses https.
-
-
-
-
-
People land on the page titled "There's a problem with this account" regarding ActiveSync.
-
-
-
-
-
The ActiveSync policy PasswordEnabled is set to True (or 1).
-
-
-
None
-
-
-
Create a new ActiveSync policy where PasswordEnabled is set to False (or 0), and then apply that policy to the account.
-
-
-
-
-
The Surface Hub doesn't have a connection to Exchange.
-
-
-
None
-
-
-
Make sure that you have a working network or Internet connection.
-
-
-
-
-
Exchange returns a status code indicating an error.
-
-
-
None
-
-
-
Make sure that you have a working network or Internet connection.
-
-
-
-
-
-### First run, Domain join page issues
-
-
-
-
-
-
-
-
-
-
Issue
-
Causes
-
Possible fixes
-
-
-
-
-
When trying to join a domain, an error shows that the account couldn't authenticate using the specified credentials.
-
The credentials provided are not capable of joining the specified domain.
-
Enter correct credentials for an account that exists in the specified domain.
-
-
-
When specifying a group from a domain, an error shows that the group couldn't be found on the domain.
-
The group may have been removed or no longer exists.
-
Verify that the group exists within the domain.
-
-
-
-
-
-
-### First run, Exchange server page
-
-
-
-
-
-
-
-
-
-
Issue
-
Causes
-
Possible fixes
-
-
-
-
-
People land on this page and are asked for the Exchange server address.
-
The Exchange server isn't configured for auto-discovery.
-
Enable auto-discovery of the Exchange server for the device account, or enter the account's Exchange server address manually.
-
-
-
-
-
-
-### First run, On-device issues
-
-
-
-
-
-
-
-
-
-
-
Issue
-
Causes
-
Error codes
-
Possible fixes
-
-
-
-
-
Can't sync mail/calendar.
-
The account has not allowed the Surface Hub as an allowed device.
-
0x86000C1C
-
Add the Surface Hub device ID to the whitelist by setting the ActiveSyncAllowedDeviceIds property for the mailbox.
-
-
-
-
-
-
-
-
-
-
-## Exchange ActiveSync errors
-
-
-This section lists status codes, mapping, user messages, and actions an admin can take to solve Exchange ActiveSync errors.
-
-
-
-
-
-
-
-
-
-
-
Hex Code
-
Mapping
-
User-Friendly Message
-
Action admin should take
-
-
-
-
-
0x85010002
-
E_HTTP_DENIED
-
The password must be updated.
-
Update the password.
-
-
-
0x80072EFD
-
WININET_E_CANNOT_CONNECT
-
Can't connect to the server right now. Wait a while and try again, or check the account settings.
-
Verify that the server name is correct and reachable. Verify that the device is connected to the network.
The account is configured with policies not compatible with Surface Hub.
-
Disable the PasswordEnabled policy for this account.
-
We have a bug were we may surface policy errors if the account doesn't receive any server notifications within the policy refresh interval.
-
-
-
0x86000C4C
-
E_NEXUS_STATUS_MAXIMUMDEVICESREACHED
-
The account has too many device partnerships.
-
Delete one or more partnerships on the server.
-
-
-
0x86000C0A
-
E_NEXUS_STATUS_SERVERERROR_RETRYLATER
-
Can't connect to the server right now.
-
Wait until the server comes back online. If the issue persists, re-provision the account.
-
-
-
0x85050003
-
E_CREDENTIALS_EXPIRED (Credentials have expired and need to be updated)
-
The password must be updated.
-
Update the password.
-
-
-
0x8505000D
-
E_AIRSYNC_RESET_RETRY
-
Can't connect to the server right now. Wait a while or check the account's settings.
-
This is normally a transient error but if the issue persists check the number of devices associated with the account and delete some of them if the number is large.
-
-
-
0x86000C16
-
E_NEXUS_STATUS_USER_HASNOMAILBOX
-
The mailbox was migrated to a different server.
-
You should never see this error. If the issue persists, re-provision the account.
-
-
-
0x85010004
-
E_HTTP_FORBIDDEN
-
Can't connect to the server right now. Wait a while and try again, or check the account's settings.
-
Verify the server name to make sure it is correct. If the account is using cert based authentication make sure the certificate is still valid and update it if not.
-
-
-
0x85030028
-
E_ACTIVESYNC_PASSWORD_OR_GETCERT
-
The account's password or client certificate are missing or invalid.
-
Update the password and/or deploy the client certificate.
-
-
-
0x86000C2A
-
E_NEXUS_STATUS_DEVICE_POLICYREFRESH
-
The account is configured with policies not compatible with Surface Hub.
-
Disable the PasswordEnabled policy for this account.
-
-
-
0x85050002
-
E_CREDENTIALS_UNAVAILABLE
-
The password must be updated.
-
Update the password.
-
-
-
0x80072EE2
-
WININET_E_TIMEOUT
-
The network doesn't support the minimum idle timeout required to receive server notification, or the server is offline.
-
Verify that the server is running. Verify the NAT settings.
-
-
-
0x85002004
-
E_FAIL_ABORT
-
This error is used to interrupt the hanging sync, and will not be exposed to users. It will be shown in the diagnostic data if you force an interactive sync, delete the account, or update its settings.
-
Nothing.
-
-
-
0x85010017
-
E_HTTP_SERVICE_UNAVAIL
-
Can't connect to the server right now. Wait a while or check the account's settings.
-
Verify the server name to make sure it is correct. Wait until the server comes back online. If the issue persists, re-provision the account.
-
-
-
0x86000C0D
-
E_NEXUS_STATUS_MAILBOX_SERVEROFFLINE
-
Can't connect to the server right now. Wait a while or check the account's settings.
-
Verify the server name to make sure it is correct. Wait until the server comes back online. If the issue persists, re-provision the account.
-
-
-
0x85030027
-
E_ACTIVESYNC_GETCERT
-
The Exchange server requires a certificate.
-
Import the appropriate EAS certificate on the Surface Hub.
-
-
-
0x86000C2B
-
E_NEXUS_STATUS_INVALID_POLICYKEY
-
The account is configured with policies not compatible with Surface Hub.
-
Disable the PasswordEnabled policy for this account.
-
We have a bug were we may surface policy errors if the account doesn't receive any server notifications within the policy refresh interval.
-
-
-
0x85010005
-
E_HTTP_NOT_FOUND
-
The server name is invalid.
-
Verify the server name to make sure it is correct. If the issue persists, re-provision the account.
-
-
-
0x85010014
-
E_HTTP_SERVER_ERROR
-
Can't connect to the server.
-
Verify the server name to make sure it is correct. Trigger a sync and, if the issue persists, re-provision the account.
-
-
-
0x80072EE7
-
WININET_E_NAME_NOT_RESOLVED
-
The server name or address could not be resolved.
-
Make sure the server name is entered correctly.
-
-
-
0x8007052F
-
ERROR_ACCOUNT_RESTRICTION
-
While auto-discovering the Exchange server, a policy is applied that prevents the logged-in user from logging in to the server.
-
This is a timing issue. Re-verify the account's credentials. Try to re-provision when they're correct.
-
-
-
0x800C0019
-
INET_E_INVALID_CERTIFICATE
-
Security certificate required to access this resource is invalid.
-
Install the correct ActiveSync certificate needed for the provided device account.
-
-
-
0x80072F0D
-
WININET_E_INVALID_CA
-
The certificate authority is invalid or is incorrect. Could not auto-discover the Exchange server because a certificate is missing.
-
Install the correct ActiveSync certificate needed for the provided device account.
-
-
-
0x80004005
-
E_FAIL
-
The domain provided couldn't be found. The Exchange server could not be auto-discovered and was not provided in the settings.
-
Make sure that the domain entered is the FQDN, and that there is an Exchange server entered in the Exchange server text box.
-
-
-
-
-## Contact Support
-
-If you have questions or need help, you can [create a support request](https://support.microsoft.com/supportforbusiness/productselection).
-
-
-
-## Related content
-
-- [Troubleshooting Miracast connection to the Surface Hub](https://docs.microsoft.com/surface-hub/miracast-troubleshooting)
-
-
-
-
-
-
diff --git a/devices/surface-hub/use-cloud-recovery-for-bitlocker-on-surfacehub.md b/devices/surface-hub/use-cloud-recovery-for-bitlocker-on-surfacehub.md
deleted file mode 100644
index d03cfe3055..0000000000
--- a/devices/surface-hub/use-cloud-recovery-for-bitlocker-on-surfacehub.md
+++ /dev/null
@@ -1,77 +0,0 @@
----
-title: How to use cloud recovery for BitLocker on a Surface Hub
-description: How to use cloud recovery for BitLocker on a Surface Hub
-ms.assetid: c0bde23a-49de-40f3-a675-701e3576d44d
-keywords: Accessibility settings, Settings app, Ease of Access
-ms.prod: surface-hub
-ms.sitesec: library
-author: v-miegge
-ms.author: v-miegge
-ms.topic: article
-ms.localizationpriority: medium
----
-
-# Summary
-
-This article describes how to use the cloud recovery function if you are unexpectedly prompted by BitLocker on a Surface Hub device.
-
-> [!NOTE]
-> You should follow these steps only if a BitLocker recovery key isn't available.
-
-> [!WARNING]
-> * This recovery process deletes the contents of the internal drive. If the process fails, the internal drive will become completely unusable. If this occurs, you will have to log a service request with Microsoft for a resolution.
-> * After the recovery process is complete, the device will be reset to the factory settings and returned to its Out of Box Experience state.
-> * After the recovery, the Surface Hub must be completely reconfigured.
-
-> [!IMPORTANT]
-> This process requires an open Internet connection that does not use a proxy or other authentication method.
-
-## Cloud recovery process
-
-To perform a cloud recovery, follow these steps:
-
-1. Select **Press Esc for more recovery options**.
-
- 
-
-1. Select **Skip this drive**.
-
- 
-
-1. Select **Recover from the cloud**.
-
- 
-
-1. Select **Yes**.
-
- 
-
-1. Select **Reinstall**.
-
- 
-
- 
-
-1. After the cloud recovery process is complete, start the reconfiguration by using the **Out of Box Experience**.
-
- 
-
-## "Something went Wrong" error message
-
-This error is usually caused by network issues that occur during the recovery download. When this issue occurs, don't turn off the Hub because you won't be able to restart it. If you receive this error message, return to the "Recover from the cloud" step, and then restart the recovery process.
-
-1. Select **Cancel**.
-
- 
-
-1. Select **Troubleshoot**.
-
- 
-
-1. Select **Recover from the cloud**.
-
- 
-
-1. If the **Wired network isn't found** error occurs, select **Cancel**, and then let the Surface Hub rediscover the wired network.
-
- 
\ No newline at end of file
diff --git a/devices/surface-hub/use-fully-qualified-domain-name-surface-hub.md b/devices/surface-hub/use-fully-qualified-domain-name-surface-hub.md
deleted file mode 100644
index cf9f2b6339..0000000000
--- a/devices/surface-hub/use-fully-qualified-domain-name-surface-hub.md
+++ /dev/null
@@ -1,31 +0,0 @@
----
-title: Use fully qualified domain name with Surface Hub
-description: Troubleshoot common problems, including setup issues, Exchange ActiveSync errors.
-keywords: ["Troubleshoot common problems", "setup issues", "Exchange ActiveSync errors"]
-author: dansimp
-ms.author: dansimp
-ms.topic: article
-ms.date: 07/27/2017
-ms.reviewer:
-manager: laurawi
-ms.localizationpriority: medium
-ms.prod: surface-hub
-ms.sitesec: library
----
-
-# Configure domain name for Skype for Business
-
-There are a few scenarios where you need to specify the domain name of your Skype for Business server:
-- **Multiple DNS suffixes** - When your Skype for Business infrastructure has disjointed namespaces such that one or more servers have a DNS suffix that doesn't match the suffix of the sign-in address (SIP) for Skype for Business.
-- **Skype for Business and Exchange suffixes are different** - When the suffix of the sign-in address for Skype for Business differs from the suffix of the Exchange address used for the device account.
-- **Working with certificates** - Large organizations with on-premises Skype for Business servers commonly use certificates with their own root certificate authority (CA). It is common for the CA domain to be different than the domain of the Skype for Business server which causes the certificate to not be trusted, and sign-in fails. Skype needs to know the domain name of the certificate in order to set up a trust relationship. Enterprises typically use Group Policy to push this out to Skype desktop, but Group Policy is not supported on Surface Hub.
-
-**To configure the domain name for your Skype for Business server**
-1. On Surface Hub, open **Settings**.
-2. Click **Surface Hub**, and then click **Calling & Audio**.
-3. Under **Skype for Business configuration**, click **Configure domain name**.
-4. Type the domain name for your Skype for Business server, and then click **Ok**.
- > [!TIP]
- > You can type multiple domain names, separated by commas. For example: lync.com, outlook.com, lync.glbdns.microsoft.com
-
- 
diff --git a/devices/surface-hub/use-room-control-system-with-surface-hub.md b/devices/surface-hub/use-room-control-system-with-surface-hub.md
deleted file mode 100644
index 1ec1e19ab5..0000000000
--- a/devices/surface-hub/use-room-control-system-with-surface-hub.md
+++ /dev/null
@@ -1,179 +0,0 @@
----
-title: Using a room control system (Surface Hub)
-description: Room control systems can be used with your Microsoft Surface Hub.
-ms.assetid: DC365002-6B35-45C5-A2B8-3E1EB0CB8B50
-ms.reviewer:
-manager: laurawi
-keywords: room control system, Surface Hub
-ms.prod: surface-hub
-ms.sitesec: library
-author: dansimp
-ms.author: dansimp
-ms.topic: article
-ms.date: 07/27/2017
-ms.localizationpriority: medium
----
-
-# Using a room control system (Surface Hub)
-
-
-Room control systems can be used with your Microsoft Surface Hub.
-
-Using a room control system with your Surface Hub involves connecting room control hardware to the Surface Hub, usually through the RJ11 serial port on the bottom of the Surface Hub.
-
-## Terminal settings
-
-To connect to a room control system control panel, you don't need to configure any terminal settings on the Surface Hub. If you want to connect a PC or laptop to your Surface Hub and send serial commands from the Surface Hub, you can use a terminal emulator program like Tera Term or PuTTY.
-
-| Setting | Value |
-| --- | --- |
-| Baud rate | 115200 |
-| Data bits | 8 |
-| Stop bits | 1 |
-| Parity | none |
-| Flow control | none |
-| Line feed | every carriage return |
-
-
-## Wiring diagram
-
-You can use a standard RJ-11 (6P6C) connector to connect the Surface Hub serial port to a room control system. This is the recommended method. You can also use an RJ-11 4-conductor cable, but we do not recommend this method.
-
-This diagram shows the correct pinout used for an RJ-11 (6P6C) to DB9 cable.
-
-
-
-## Command sets
-
-Room control systems use common meeting-room scenarios for commands. Commands originate from the room control system, and are communicated over a serial connection to a Surface Hub. Commands are ASCII based, and the Surface Hub will acknowledge when state changes occur.
-
-The following command modifiers are available. Commands terminate with a new line character (\n). Responses can come at any time in response to state changes not triggered directly by a management port command.
-
-| Modifier | Result |
-| --- | --- |
-| + | Increment a value |
-| - | Decrease a value |
-| = | Set a discrete value |
-| ? | Queries for a current value |
-
-
-## Power
-
-Surface Hub can be in one of these power states.
-
-| State | Energy Star state| Description |
-| --- | --- | --- |
-| 0 | S5 | Off |
-| 1 | - | Power up (indeterminate) |
-| 2 | S3 | Sleep |
-| 5 | S0 | Ready |
-
-
-In Replacement PC mode, the power states are only Ready and Off and only change the display. The management port can't be used to power on the replacement PC.
-
-| State | Energy Star state| Description |
-| --- | --- | --- |
-| 0 | S5 | Off |
-| 5 | S0 | Ready |
-
-For a control device, anything other than 5 / Ready should be considered off. Each PowerOn command results in two state changes and responses.
-
-| Command | State change| Response |
-| --- | --- | --- |
-| PowerOn | Device turns on (display + PC).PC service notifies SMC that the PC is ready. | Power=0Power=5 |
-| PowerOff | Device transitions to ambient state (PC on, display dim). | Power=0 |
-| Power? | SMC reports the last-known power state. | Power=<#> |
-
-
-
-## Brightness
-
-The current brightness level is a range from 0 to 100.
-
-Changes to brightness levels can be sent by a room control system, or other system.
-
-| Command | State change |Response |
-| --- | --- | --- |
-| Brightness+ | System management controller (SMC) sends the brightness up command.PC service on the room control system notifies SMC of new brightness level. | Brightness = 51 |
-| Brightness- | SMC sends the brightness down command.PC service notifies SMC of new brightness level. | Brightness = 50 |
-
-## Volume
-
-The current volume level is a range from 0 to 100.
-
-Changes to volume levels can be sent by a room control system, or other system.
-
->[!NOTE]
->The Volume command will only control the volume for embedded or Replacement PC mode, not from [Guest sources](connect-and-display-with-surface-hub.md).
-
-| Command | State change | Response(On in [Replacement PC mode](connect-and-display-with-surface-hub.md#replacement-pc-mode)) |
-| --- | --- | --- |
-| Volume+ | SMC sends the volume up command.PC service notifies SMC of new volume level. | Volume = 51 |
-| Volume- | SMC sends the volume down command.PC service notifies SMC of new volume level. | Volume = 50 |
-
-
-
-
-## Mute for audio
-
-Audio can be muted.
-
-| Command | State change | Response |
-| --- | --- | --- |
-| AudioMute+ | SMC sends the audio mute command.PC service notifies SMC that audio is muted. | none |
-
-
-
-
-## Video source
-
-Several display sources can be used.
-
-| State | Description |
-| --- | --- |
-| 0 | Onboard PC |
-| 1 | DisplayPort |
-| 2 | HDMI |
-| 3 | VGA |
-
-
-
-
-Changes to display source can be sent by a room control system, or other system.
-
-| Command | State change | Response |
-| --- | --- | --- |
-| Source=# | SMC changes to the desired source.PC service notifies SMC that the display source has switched. | Source=<#> |
-| Source+ | SMC cycles to the next active input source.PC service notifies SMC of the current input source. | Source=<#> |
-| Source- | SMC cycles to the previous active input source.PC service notifies SMC of the current input source. | Source=<#> |
-| Source? | SMC queries PC service for the active input source.PC service notifies SMC of the current in;put source. | Source=<#> |
-
-## Errors
-
-Errors are returned following the format in this table.
-
-| Error | Notes |
-| --- | --- |
-| Error: Unknown command '<input>'. | The instruction contains an unknown initial command. For example, "VOL+" would be invalid and return " Error: Unknown command 'VOL'". |
-| Error: Unknown operator '<input>'. | The instruction contains an unknown operator. For example, "Volume!" would be invalid and return " Error: Unknown operator '!'". |
-| Error: Unknown parameter '<input>'. | The instruction contains an unknown parameter. For example, "Volume=abc" would be invalid and return " Error: Unknown parameter 'abc'". |
-| Error: Command not available when off '<input>'. | When the Surface Hub is off, commands other than Power return this error. For example, "Volume+" would be invalid and return " Error: Command not available when off 'Volume'". |
-
-
-
-
-## Related topics
-
-
-[Manage Microsoft Surface Hub](manage-surface-hub.md)
-
-[Microsoft Surface Hub administrator's guide](surface-hub-administrators-guide.md)
-
-
-
-
-
-
-
-
-
diff --git a/devices/surface-hub/use-surface-hub-diagnostic-test-device-account.md b/devices/surface-hub/use-surface-hub-diagnostic-test-device-account.md
deleted file mode 100644
index e01737c52e..0000000000
--- a/devices/surface-hub/use-surface-hub-diagnostic-test-device-account.md
+++ /dev/null
@@ -1,135 +0,0 @@
----
-title: Using the Surface Hub Hardware Diagnostic Tool to test a device account
-description: Using the Surface Hub Hardware Diagnostic Tool to test a device account
-ms.assetid: a87b7d41-d0a7-4acc-bfa6-b9070f99bc9c
-keywords: Accessibility settings, Settings app, Ease of Access
-ms.prod: surface-hub
-ms.sitesec: library
-author: v-miegge
-ms.author: v-miegge
-ms.topic: article
-ms.localizationpriority: medium
----
-
-# Using the Surface Hub Hardware Diagnostic Tool to test a device account
-
-## Introduction
-
-> [!NOTE]
-> The "Account Settings" section of the Surface Hub Hardware Diagnostic tool doesn’t collect any information. The email and password that are entered as input are used only directly on your environment and not collected or transferred to anyone. The login information persists only until the application is closed or you end the current session on the Surface Hub.
-
-> [!IMPORTANT]
-> * Administrator privileges are not required to run this application.
-> * The results of the diagnostic should be discussed with your local administrator before you open a service call with Microsoft.
-
-### Surface Hub Hardware Diagnostic
-
-By default, the [Surface Hub Hardware Diagnostic](https://www.microsoft.com/store/apps/9nblggh51f2g) application isn’t installed in earlier versions of the Surface Hub system. The application is available for free from the Microsoft Store. Administrator privileges are required to install the application.
-
- 
-
-## About the Surface Hub Hardware Diagnostic Tool
-
-The Surface Hub Hardware Diagnostic tool is an easy-to-navigate tool that lets the user test many of the hardware components within the Surface Hub device. This tool can also test and verify a Surface Hub device account. This article describes how to use the Account Settings test within the Surface Hub Hardware Diagnostic tool.
-
-> [!NOTE]
-> The device account for the Surface Hub should be created before any testing is done. The Surface Hub Administrator Guide provides instructions and PowerShell scripts to help you create on-premises, online (Office365), or hybrid device accounts. For more information, go to the [Create and test a device account (Surface Hub)](https://docs.microsoft.com/surface-hub/create-and-test-a-device-account-surface-hub) topic in the guide.
-
-### Device account testing process
-
-1. Navigate to **All Apps**, and then locate the Surface Hub Hardware Diagnostic application.
-
- 
-
-1. When the application starts, the **Welcome** page provides a text window to document the reason why you are testing the Hub. This note can be saved to USB together with the diagnostic results at the conclusion of testing. After you finish entering a note, select the **Continue** button.
-
- 
-
-1. The next screen provides you the option to test all or some of the Surface Hub components. To begin testing the device account, select the **Test Results** icon.
-
- 
-
- 
-
-1. Select **Account Settings**.
-
- 
-
- The Account Settings screen is used to test your device account.
-
- 
-
-1. Enter the email address of your device account. The password is optional but is recommended. Select the **Test Account** button when you are ready to continue.
-
- 
-
-1. After testing is finished, review the results for the four areas of testing. Each section can be expanded or collapsed by selecting the Plus or Minus sign next to each topic.
-
- **Network**
-
- 
-
- **Environment**
-
- 
-
- **Certificates**
-
- 
-
- **Trust Model**
-
- 
-
-## Appendix
-
-### Field messages and resolution
-
-#### Network
-
-Field |Success |Failure |Comment |Reference
-|------|------|------|------|------|
-Internet Connectivity |Device does have Internet connectivity |Device does not have Internet connectivity |Verifies internet connectivity, including proxy connection |
-HTTP Version |1.1 |1.0 |If HTTP 1.0 found, it will cause issue with WU and Store |
-Direct Internet Connectivity |Device has a Proxy configured Device has no Proxy configured |N/A |Informational. Is your device behind a proxy? |
-Proxy Address | | |If configured, returns proxy address. |
-Proxy Authentication |Proxy does not require Authentication |Proxy requires Proxy Auth |Result may be a false positive if a user already has an open session in Edge and has authenticated through the proxy. |
-Proxy Auth Types | | |If proxy authentication is used, return the Authentication methods advertised by the proxy. |
-
-#### Environment
-
-Field |Success |Failure |Comment |Reference
-|------|------|------|------|------|
-SIP Domain | | |Informational. |
-Skype Environment |Skype for Business Online, Skype for Business OnPrem, Skype for Business Hybrid |Informational. |What type of environment was detected. Note: Hybrid can only be detected if the password is entered.
-LyncDiscover FQDN | | |Informational. Displays the LyncDiscover DNS result |
-LyncDiscover URI | | |Informational. Displays the URL used to perform a LyncDiscover on your environment.|
-LyncDiscover |Connection Successful |Connection Failed |Response from LyncDiscover web service. |
-SIP Pool Hostname | | |Informational. Display the SIP pool name discovered from LyncDiscover |
-
-#### Certificates (in-premises hybrid only)
-
-LyncDiscover Certificate
-
-Field |Success |Failure |Comment |Reference
-|------|------|------|------|------|
-LyncDiscover Cert CN | | |Informational. Displays the LD cert Common name |
-LyncDiscover Cert CA | | |Informational. Displays the LD Cert CA |
-LyncDiscover Cert Root CA | | |Informational. Displays the LD Cert Root CA, if available. |
-LD Trust Status |Certificate is Trusted. |Certificate is not trusted, please add the Root CA. |Verify the certificate against the local cert store. Returns positive if the machine trusts the certificate.|[Download and deploy Skype for Business certificates using PowerShell](https://blogs.msdn.microsoft.com/surfacehub/2016/06/07/download-and-deploy-skype-for-business-certificates-using-powershell/)/[Supported items for Surface Hub provisioning packages](https://docs.microsoft.com/surface-hub/provisioning-packages-for-surface-hub#supported-items-for-surface-hub-provisioning-packages)
-
-SIP Pool Certification
-
-Field |Success |Failure |Comment |Reference
-|------|------|------|------|------|
-SIP Pool Cert CN | | |(CONTENTS) |
-SIP Pool Cert CA | | |(CONTENTS) |
-SIP Pool Trust Status |Certificate is Trusted. |Certificate is not trusted, please add the Root CA. |Verify the certificate against the local cert store and return a positive if the devices trusts the certificate. |
-SIP Pool Cert Root CA | | |Information. Display the SIP Pool Cert Root CA, if available. |
-
-#### Trust Model (on-premises hybrid only)
-
-Field |Success |Failure |Comment |Reference
-|------|------|------|------|------|
-Trust Model Status |No Trust Model Issue Detected. |SIP Domain and server domain are different please add the following domains. |Check the LD FQDN/ LD Server Name/ Pool Server name for Trust model issue.
-Domain Name(s) | | |Return the list of domains that should be added for SFB to connect. |
diff --git a/devices/surface-hub/whiteboard-collaboration.md b/devices/surface-hub/whiteboard-collaboration.md
deleted file mode 100644
index a1e05d92b5..0000000000
--- a/devices/surface-hub/whiteboard-collaboration.md
+++ /dev/null
@@ -1,74 +0,0 @@
----
-title: Set up and use Microsoft Whiteboard
-description: Microsoft Whiteboard's latest update includes the capability for two Surface Hubs to collaborate in real time on the same board.
-ms.prod: surface-hub
-ms.sitesec: library
-author: dansimp
-ms.author: dansimp
-ms.topic: article
-ms.date: 03/18/2019
-ms.reviewer:
-manager: laurawi
-ms.localizationpriority: medium
----
-
-# Set up and use Microsoft Whiteboard
-
-The Microsoft Whiteboard app includes the capability for Surface Hubs and other devices with the Microsoft Whiteboard app installed to collaborate in real time on the same board.
-
-## Prerequisites
-
-To use whiteboard collaboration complete the following actions:
-
-- Add Whiteboard.ms, whiteboard.microsoft.com, and wbd.ms to your list of allowed sites.
-- Open port: **HTTPS: 443** (normally configured when you first run Surface Hub.)
-
-## Office 365 requirements
-
-- Whiteboard collaboration is only supported in the Office 365 commercial environment and requires Office 365 with cloud-based Azure Active Directory (Azure AD).
-- You can only run collaborative sessions among users belonging to the same Office 365 tenant.
-- Office 365 Germany or Office 365 operated by 21Vianet do not support whiteboard collaboration.
-
-## Collaborating with whiteboards
-
-To start a collaboration session:
-
-1. In the Whiteboard app, tap the **Sign in** button.
-2. Sign in with your organization ID.
-3. Tap the **Invite** button next to your name at the top of the app.
-4. Write or type the names of the colleagues you wish to collaborate with.
-
-On the other device, such as a Surface Hub, when you are signed in, the shared board will now appear in the board gallery.
-
-### User tips
-- Log in to access your whiteboards. As you work, changes are saved automatically.
-- Name your whiteboards to help organize your content and find it quickly. Select the … to open the menu. Select the **Options** gear icon to access more tools and features of the Whiteboard.
-- Use **Ink to shape** to turn drawing into actual shapes like circles, squares, and triangles.
-- Use **Ink to table** to turn a drawn grid into a table with rows and columns.
-- You can also change the background color and design from solid to grid or dots. Pick the background, then choose the color from the wheel around it.
-- You can export a copy of the Whiteboard collaboration for yourself through the Share charm and leave the board for others to continue working.
-
-For more information, see [Use Microsoft Whiteboard on a Surface Hub](https://support.office.com/article/use-microsoft-whiteboard-on-a-surface-hub-5c594985-129d-43f9-ace5-7dee96f7621d).
-
-> [!NOTE]
-> If you are using Whiteboard and cannot sign in, you can collaborate by joining a Teams or Skype for Business meeting, and then sharing your screen. After you're done, tap **Settings** > **Export to email** or save a copy of the board. If you choose to export to SVG, it exports vector graphics and provides higher resolution than PNG and can be opened in a web browser.
-
-## New features in Whiteboard
-
-The Microsoft Whiteboard app, updated for Surface Hub on July 1, 2019 includes a host of new features including:
-
-- **Automatic Saving** - Boards are saved to the cloud automatically when you sign in, and can be found in the board gallery. There is no local folder name or directory.
-- **Extended collaboration across devices** - You can collaborate using new apps for Windows 10 PC and iOS, and a web version for other devices.
-- **Richer canvas** - In addition to ink and images, Whiteboard now includes sticky notes, text and GIFs, with more objects coming soon.
-- **Intelligence** – In addition to ink to shape and table, Whiteboard now includes ink beautification to improve handwriting and ink grab to convert images to ink.
-- **More color and background options** - Whiteboard now includes more pen colors and thickness options along with additional background colors and designs.
-- **Teams Integration** – You can automatically launch Whiteboard from a Teams meeting and share with participants (currently in preview).
-
-
-## Related topics
-
-- [Windows 10 Creators Update for Surface Hub](https://www.microsoft.com/surface/support/surface-hub/windows-10-creators-update-surface-hub)
-
-- [Support documentation for Microsoft Whiteboard](https://support.office.com/article/Whiteboard-Help-0c0f2aa0-b1bb-491c-b814-fd22de4d7c01)
-
-- [Use Microsoft Whiteboard on a Surface Hub](https://support.office.com/article/use-microsoft-whiteboard-on-a-surface-hub-5c594985-129d-43f9-ace5-7dee96f7621d)
diff --git a/devices/surface-hub/wireless-network-management-for-surface-hub.md b/devices/surface-hub/wireless-network-management-for-surface-hub.md
deleted file mode 100644
index 96162edafe..0000000000
--- a/devices/surface-hub/wireless-network-management-for-surface-hub.md
+++ /dev/null
@@ -1,71 +0,0 @@
----
-title: Wireless network management (Surface Hub)
-description: Microsoft Surface Hub offers two options for network connectivity to your corporate network and Internet wireless, and wired. While both provide network access, we recommend you use a wired connection.
-ms.assetid: D2CFB90B-FBAA-4532-B658-9AA33CAEA31D
-ms.reviewer:
-manager: laurawi
-keywords: network connectivity, wired connection
-ms.prod: surface-hub
-ms.sitesec: library
-author: dansimp
-ms.author: dansimp
-ms.topic: article
-ms.date: 07/27/2017
-ms.localizationpriority: medium
----
-
-# Wireless network management (Surface Hub)
-
-
-Microsoft Surface Hub offers two options for network connectivity to your corporate network and Internet: wireless, and wired. While both provide network access, we recommend you use a wired connection.
-
-## Modifying, adding, or reviewing a network connection
-
-
-If a wired network connection is not available, the Surface Hub can use a wireless network for internet access. A properly connected and configured Wi-Fi access point must be available and within range of the Surface Hub.
-
-### Choose a wireless access point
-
-1. On the Surface Hub, open **Settings** and enter your admin credentials.
-2. Click **Network & Internet**. Under **Wi-Fi**, choose an access point. If you want Surface Hub to automatically connect to this access point, click **Connect automatically**. Click **Connect**.
-
- 
-
-3. If the network is secured, you'll be asked to enter the security key. Click **Next** to connect.
-
- 
-
-### Review wireless settings
-
-1. On the Surface Hub, open **Settings** and enter your admin credentials.
-2. Click **Network & Internet**, then **Wi-Fi**, and then click **Advanced options**.
-3. Surface Hub shows you the properties for the wireless network connection.
-
- 
-
-### Review wired settings
-
-1. On the Surface Hub, open **Settings** and enter your admin credentials.
-2. Click **System**, click **Network & Internet**, then click on the network under Ethernet.
-
- 
-
-3. The system will show you the properties for the wired network connection.
-
- 
-
-## Related topics
-
-
-[Manage Microsoft Surface Hub](manage-surface-hub.md)
-
-[Microsoft Surface Hub administrator's guide](surface-hub-administrators-guide.md)
-
-
-
-
-
-
-
-
-
diff --git a/devices/surface/TOC.md b/devices/surface/TOC.md
deleted file mode 100644
index 7245176edd..0000000000
--- a/devices/surface/TOC.md
+++ /dev/null
@@ -1,69 +0,0 @@
-# [Surface](index.yml)
-
-## [Surface devices documentation](get-started.yml)
-
-## Overview
-
-### [Surface Pro 7 for Business](https://www.microsoft.com/surface/business/surface-pro-7)
-### [Surface Pro X for Business](https://www.microsoft.com/surface/business/surface-pro-x)
-### [Surface Laptop 3 for Business](https://www.microsoft.com/surface/business/surface-laptop-3)
-### [Surface Book 2 for Business](https://www.microsoft.com/surface/business/surface-book-2)
-### [Surface Studio 2 for Business](https://www.microsoft.com/surface/business/surface-studio-2)
-### [Surface Go](https://www.microsoft.com/surface/business/surface-go)
-### [Secure, work-anywhere mobility with LTE Advanced](https://www.microsoft.com/surface/business/lte-laptops-and-tablets)
-
-## Plan
-
-### [Surface device compatibility with Windows 10 Long-Term Servicing Branch](surface-device-compatibility-with-windows-10-ltsc.md)
-### [Long-Term Servicing Branch for Surface devices](ltsb-for-surface.md)
-### [Wake On LAN for Surface devices](wake-on-lan-for-surface-devices.md)
-### [Considerations for Surface and Endpoint Configuration Manager](considerations-for-surface-and-system-center-configuration-manager.md)
-### [Deploy Surface app with Microsoft Store for Business](deploy-surface-app-with-windows-store-for-business.md)
-### [Enable PEAP, EAP-FAST, and Cisco LEAP on Surface devices](enable-peap-eap-fast-and-cisco-leap-on-surface-devices.md)
-### [Ethernet adapters and Surface deployment](ethernet-adapters-and-surface-device-deployment.md)
-
-## Deploy
-
-### [Deploy Surface devices](deploy.md)
-### [Windows Autopilot and Surface devices](windows-autopilot-and-surface-devices.md)
-### [Deploying, managing, and servicing Surface Pro X](surface-pro-arm-app-management.md)
-### [Surface Pro X app compatibility](surface-pro-arm-app-performance.md)
-### [Manage and deploy Surface driver and firmware updates](manage-surface-driver-and-firmware-updates.md)
-### [Surface Deployment Accelerator](microsoft-surface-deployment-accelerator.md)
-### [Step by step: Surface Deployment Accelerator](step-by-step-surface-deployment-accelerator.md)
-### [Deploy Windows 10 to Surface devices with MDT](deploy-windows-10-to-surface-devices-with-mdt.md)
-### [Enable the Surface Laptop keyboard during MDT deployment](enable-surface-keyboard-for-windows-pe-deployment.md)
-### [Upgrade Surface devices to Windows 10 with MDT](upgrade-surface-devices-to-windows-10-with-mdt.md)
-### [Customize the OOBE for Surface deployments](customize-the-oobe-for-surface-deployments.md)
-### [Using the Surface Deployment Accelerator deployment share](using-the-sda-deployment-share.md)
-### [Surface System SKU reference](surface-system-sku-reference.md)
-
-## Manage
-
-### [Manage and deploy Surface driver and firmware updates](manage-surface-driver-and-firmware-updates.md)
-### [Optimize Wi-Fi connectivity for Surface devices](surface-wireless-connect.md)
-### [Best practice power settings for Surface devices](maintain-optimal-power-settings-on-Surface-devices.md)
-### [Surface Dock Firmware Update](surface-dock-firmware-update.md)
-### [Battery Limit setting](battery-limit.md)
-### [Surface Brightness Control](microsoft-surface-brightness-control.md)
-### [Surface Asset Tag](assettag.md)
-
-
-## Secure
-### [Intune management of Surface UEFI settings](surface-manage-dfci-guide.md)
-### [Manage Surface UEFI settings](manage-surface-uefi-settings.md)
-### [Advanced UEFI security features for Surface Pro 3](advanced-uefi-security-features-for-surface-pro-3.md)
-### [Surface Enterprise Management Mode](surface-enterprise-management-mode.md)
-### [Enroll and configure Surface devices with SEMM](enroll-and-configure-surface-devices-with-semm.md)
-### [Unenroll Surface devices from SEMM](unenroll-surface-devices-from-semm.md)
-### [Use Microsoft Endpoint Configuration Manager to manage devices with SEMM](use-system-center-configuration-manager-to-manage-devices-with-semm.md)
-### [Surface Data Eraser](microsoft-surface-data-eraser.md)
-
-## Troubleshoot
-### [Top support solutions for Surface devices](support-solutions-surface.md)
-### [Fix common Surface problems using the Surface Diagnostic Toolkit for Business](surface-diagnostic-toolkit-for-business-intro.md)
-#### [Deploy Surface Diagnostic Toolkit for Business](surface-diagnostic-toolkit-business.md)
-#### [Use Surface Diagnostic Toolkit for Business in desktop mode](surface-diagnostic-toolkit-desktop-mode.md)
-#### [Run Surface Diagnostic Toolkit for Business using commands](surface-diagnostic-toolkit-command-line.md)
-
-### [Change history for Surface documentation](change-history-for-surface.md)
diff --git a/devices/surface/advanced-uefi-security-features-for-surface-pro-3.md b/devices/surface/advanced-uefi-security-features-for-surface-pro-3.md
deleted file mode 100644
index 017f34559f..0000000000
--- a/devices/surface/advanced-uefi-security-features-for-surface-pro-3.md
+++ /dev/null
@@ -1,171 +0,0 @@
----
-title: Advanced UEFI security features for Surface Pro 3 (Surface)
-description: This article describes how to install and configure the v3.11.760.0 UEFI update to enable additional security options for Surface Pro 3 devices.
-ms.assetid: 90F790C0-E5FC-4482-AD71-60589E3C9C93
-ms.reviewer:
-manager: laurawi
-keywords: security, features, configure, hardware, device, custom, script, update
-ms.localizationpriority: medium
-ms.prod: w10
-ms.mktglfcycl: manage
-ms.pagetype: surface, devices, security
-ms.sitesec: library
-author: coveminer
-ms.author: v-jokai
-ms.topic: article
----
-
-# Advanced UEFI security features for Surface Pro 3
-
-
-This article describes how to install and configure the v3.11.760.0 UEFI update to enable additional security options for Surface Pro 3 devices.
-
-To address more granular control over the security of Surface devices, the v3.11.760.0 UEFI update provides additional security options that allow you to disable specific hardware devices or to prevent starting from those devices. After the UEFI update is installed on a device, you can configure it manually or automatically by running a script.
-
-## Manually install the UEFI update
-
-
-Before you can configure the advanced security features of your Surface device, you must first install the v3.11.760.0 UEFI update. This update is installed automatically if you receive your updates from Windows Update. For more information about how to configure Windows to update automatically by using Windows Update, see [How to configure and use Automatic Updates in Windows](https://support.microsoft.com/kb/306525).
-
-To update the UEFI on Surface Pro 3, you can download and install the Surface UEFI updates as part of the Surface Pro 3 Firmware and Driver Pack. These firmware and driver packs are available from the [Surface Pro 3 page](https://www.microsoft.com/download/details.aspx?id=38826) on the Microsoft Download Center. You can find out more about the firmware and driver packs at [Download the latest firmware and drivers for Surface devices](https://technet.microsoft.com/itpro/surface/deploy-the-latest-firmware-and-drivers-for-surface-devices). The firmware and driver packs are available as both self-contained Windows Installer (.msi) and archive (.zip) formats. You can find out more about these two formats and how you can use them to update your drivers at [Manage Surface driver and firmware updates](https://technet.microsoft.com/itpro/surface/manage-surface-pro-3-firmware-updates).
-
-## Manually configure additional security settings
-
-
->[!NOTE]
->To enter firmware setup on a Surface device, begin with the device powered off, press and hold the **Volume Up** button, then press and release the **Power** button, then release the **Volume Up** button after the device has begun to boot.
-
-After the v3.11.760.0 UEFI update is installed on a Surface device, an additional UEFI menu named **Advanced Device Security** becomes available. If you click this menu, the following options are displayed:
-
-| Option | Description | Available settings (default listed in bold) |
-|----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------|
-| Network Boot | Enables or disables the ability of your Surface device to boot from the network (also known as PXE boot). | **Enabled**, Not Bootable |
-| Side USB | Enables or disables the USB port on the side of the Surface device. Additionally, the USB port can be enabled, but not allow booting. | **Enabled**, Not Bootable, Disabled |
-| Docking Port | Enables or disables the ports on the Surface docking station. Additionally, the docking port can be enabled, but block booting from any USB or Ethernet port in the docking station. | **Enabled**, Not Bootable, Disabled |
-| Front Camera | Enables or disables the camera on the front of the Surface device. | **Enabled**, Disabled |
-| Rear Camera | Enables or disables the camera on the rear of the Surface device. | **Enabled**, Disabled |
-| On Board Audio | Enables or disables audio on the Surface device. | **Enabled**, Disabled |
-| microSD | Enables or disables the microSD slot on the Surface device. | **Enabled**, Disabled |
-| WiFi | Enables or disables the built-in Wi-Fi transceiver in the Surface device. This also disables Bluetooth. | **Enabled**, Disabled |
-| Bluetooth | Enables or disables the built-in Bluetooth transceiver in the Surface device. | **Enabled**, Disabled |
-
-
-
-## Automate additional security settings
-
-
-As an IT professional with administrative privileges, you can automate the configuration of UEFI settings by leveraging [Surface Pro 3 Firmware Tools (476 KB)](https://go.microsoft.com/fwlink/p/?LinkID=618038) available from the Microsoft Download Center. These tools install a .NET assembly that can be called from any custom application or script.
-
-**Prerequisites**
-
-- The sample scripts below leverage the previously mentioned extension and therefore assume that the tool has been installed on the device being managed.
-- The scripts must be run with administrative privilege.
-- The Windows PowerShell command [**Set-ExecutionPolicy Unrestricted**](https://technet.microsoft.com/library/ee176961.aspx) must be called prior to running sample scripts if they are not digitally signed.
-
-**Sample scripts**
-
->**Note**: The UEFI password used in the sample scripts below is presented in clear text. We strongly recommend saving the scripts in a protected location and running them in a controlled environment.
-
-
-Show all configurable options:
-
-```
-# Load the extension
-[System.Reflection.Assembly]::Load("SurfaceUefiManager, Version=1.0.5483.22783, Culture=neutral, PublicKeyToken=20606f4b5276c705")
-
-# Get the collection of all configurable settings
-$uefiOptions = [Microsoft.Surface.FirmwareOption]::All()
-
-foreach ($uefiOption in $uefiOptions)
-{
- Write-Host "Name:" $uefiOption.Name
- Write-Host " Description =" $uefiOption.Description
- Write-Host " Current Value =" $uefiOption.CurrentValue
- Write-Host " Default Value =" $uefiOption.DefaultValue
- Write-Host " Proposed Value =" $uefiOption.ProposedValue
-
- # This gives usage and validation information
- Write-Host " Allowed Values =" $uefiOption.FriendlyRegEx
- Write-Host " Regular Expression =" $uefiOption.RegEx
-
- Write-Host
-}
-```
-
-Set or change UEFI password:
-
-```
-# Load the extension
-[System.Reflection.Assembly]::Load("SurfaceUefiManager, Version=1.0.5483.22783, Culture=neutral, PublicKeyToken=20606f4b5276c705")
-
-# Must supply UEFI administrator Password if set
-# If it is not currently set this is ignored
-[Microsoft.Surface.FirmwareOption]::Unlock("1234")
-
-$Password = [Microsoft.Surface.FirmwareOption]::Find("Password")
-
-# Set New value to 12345
-$Password.ProposedValue = "12345"
-```
-
-Check status of proposed changes:
-
-```
-# Load the extension
-[System.Reflection.Assembly]::Load("SurfaceUefiManager, Version=1.0.5483.22783, Culture=neutral, PublicKeyToken=20606f4b5276c705")
-
-# Check update status
-$updateStatus = [Microsoft.Surface.FirmwareOption]::UpdateStatus
-$updateIteration = [Microsoft.Surface.FirmwareOption]::UpdateIteration
-Write-Host "Last Update Status =" $updateStatus
-Write-Host "Last Update Iteration =" $updateIteration
-
-# Get the individual results for the last proposed update
-# If the device has never had an update attempt this will be an empty list
-$details = [Microsoft.Surface.FirmwareOption]::UpdateStatusDetails
-Write-Host $details.Count "Settings were proposed"
-if ($details.Count -gt 0)
-{
- Write-Host "Result Details"
- foreach ($detail in $details.GetEnumerator())
- {
- Write-Host " " $detail.Key "=" $detail.Value
- }
-}
-```
-
-Revert UEFI to default values:
-
-```
-# Load the extension
-[System.Reflection.Assembly]::Load("SurfaceUefiManager, Version=1.0.5483.22783, Culture=neutral, PublicKeyToken=20606f4b5276c705")
-
-# Must supply UEFI administrator Password if set
-# If it is not currently set this is ignored
-[Microsoft.Surface.FirmwareOption]::Unlock("1234")
-
-# Get the collection of all configurable settings
-$uefiOptions = [Microsoft.Surface.FirmwareOption]::All()
-
-# Reset all options to the factory default
-foreach ($uefiOption in $uefiOptions)
-{
- $uefiOption.ProposedValue = $uefiOption.DefaultValue
-}
-```
-
-Status code interpretation
-
-- 00 - The proposed update was a success
-- 02 - One of the proposed values had an invalid value
-- 03 - There was a proposed value set that was not recognized
-- 0F - The unlock password did not match currently set password
-
-
-
-
-
-
-
-
-
diff --git a/devices/surface/assettag.md b/devices/surface/assettag.md
deleted file mode 100644
index 296a57b10e..0000000000
--- a/devices/surface/assettag.md
+++ /dev/null
@@ -1,117 +0,0 @@
----
-title: Surface Asset Tag Tool
-description: This topic explains how to use the Surface Asset Tag Tool.
-ms.prod: w10
-ms.mktglfcycl: manage
-ms.localizationpriority: medium
-ms.sitesec: library
-author: coveminer
-ms.author: v-jokai
-ms.topic: article
-ms.reviewer: hachidan
-manager: laurawi
----
-
-# Surface Asset Tag Tool
-
-Surface Asset Tag is a command line interface (CLI) utility
-that allows you to view, assign, and modify an assigned asset tag value
-for Surface devices. It works on Surface Pro 3 and all newer Surface devices.
-
-## System requirements
-
-- Surface Pro 3 or later
-
-- UEFI firmware version 3.9.150.0 or later
-
-## Using Surface Asset Tag
-
-To run Surface Asset Tag:
-
-1. On the Surface device, download **Surface Asset Tag.zip** from the [Microsoft Download
- Center](https://www.microsoft.com/download/details.aspx?id=46703),
- extract the zip file, and save AssetTag.exe in desired folder (in
- this example, C:\\assets).
-
- > [!NOTE]
- > For Surface Pro X, use the application named **AssetTag_x86** in the ZIP file.
-
-2. Open a command console as an Administrator and run AssetTag.exe,
- entering the full path to the tool.
-
-3. Restart Surface.
-
-### Asset Tag tool commands
-In the following examples, AssetTag.exe is saved in a directory on a local machine (C:\assets).
-
-To get the proposed asset tag, run AssetTag -g.
-
-**Example**
-
- ```
- C:\assets\AssetTag.exe -g
- ```
-
- To clear the proposed asset tag, run AssetTag -s.
-
- **Example**
-
- ```
-C:\assets\AssetTag.exe -s
- ```
-To set the proposed asset tag, run AssetTag -s testassettag12.
-
-**Example**
-
-```
-C:\assets\AssetTag.exe -s testassettag12
-```
-
->[!NOTE]
->The asset tag value must contain between 1 and 36 characters. Valid characters include A-Z, a-z, 0-9, period (.) and hyphen (-).
-
-
-## Managing asset tags
-
-You can view the existing asset tag in the UEFI settings under Device
-Information (**Control Panel > Recovery > Advanced Startup > Restart
-now**.)
-
-The figure below shows the results of running the Asset Tag Tool on
-Surface Go.
-
-
-
-> **Figure 1.** Results of running Surface Asset Tag tool on Surface Go
-
-Alternately, you can use WMI to query the existing asset tag on a device:
-
-(Get-WmiObject -query “Select * from Win32_SystemEnclosure”)
-
-**Example**
-
- ```
-C:\Windows\System32> (Get-WmiObject -query “Select * from Win32_SystemEnclosure”)
- ```
-
-### Using PowerShell
-
-You can use the script below as a way of getting the proposed value and
-interpreting any errors.
-
- ```
-AssetTag -g \> $asset\_tag 2\> $error\_message
-$asset\_tag\_return\_code = $LASTEXITCODE
-$asset\_tag = $asset\_tag.Trim(“\`r\`n”)
-
-if ($asset\_tag\_return\_code -eq 0) {
-Write-Output (“Good Tag = ” + $asset\_tag)
-} else {
-Write-Output (
-“Failure: Code = ” + $asset\_tag\_return\_code +
-“Tag = ” + $asset\_tag +
-“Message = ” + $error\_message)
-
-}
- ```
diff --git a/devices/surface/battery-limit.md b/devices/surface/battery-limit.md
deleted file mode 100644
index c260718254..0000000000
--- a/devices/surface/battery-limit.md
+++ /dev/null
@@ -1,89 +0,0 @@
----
-title: Battery Limit setting (Surface)
-description: Battery Limit is a UEFI setting that changes how the Surface device battery is charged and may prolong its longevity.
-ms.prod: w10
-ms.mktglfcycl: manage
-ms.pagetype: surface, devices
-ms.sitesec: library
-author: coveminer
-ms.reviewer:
-manager: laurawi
-ms.author: v-jokai
-ms.topic: article
-ms.localizationpriority: medium
-ms.audience: itpro
----
-
-# Battery Limit setting
-
-Battery Limit option is a UEFI setting that changes how the Surface device battery is charged and may prolong its longevity. This setting is recommended in cases in which the device is continuously connected to power, for example when devices are integrated into kiosk solutions.
-
-## How Battery Limit works
-
-Setting the device on Battery Limit changes the protocol for charging the device battery. When Battery Limit is enabled, the battery charge will be limited to 50% of its maximum capacity. The charge level reported in Windows will reflect this limit. Therefore, it will show that the battery is charged up to 50% and will not charge beyond this limit. If you enable Battery Limit while the device is above 50% charge, the Battery icon will show that the device is plugged in but discharging until the device reaches 50% of its maximum charge capacity.
-
-## Supported devices
-The Battery Limit UEFI setting is built into the latest Surface devices including Surface Pro 7 and Surface Laptop 3. Earlier devices require a
- [Surface UEFI firmware update](update.md), available through Windows Update or via the MSI driver and firmware packages on the [Surface Support site](https://support.microsoft.com/help/4023482/surface-download-drivers-and-firmware-for-surface). Check [Enable "Battery Limit" for Surface devices that have to be plugged in for extended periods of time](https://support.microsoft.com/help/4464941) for the specific Surface UEFI version required for each supported device.
-
-## Enabling Battery Limit in Surface UEFI (Surface Pro 4 and later)
-
-The Surface UEFI Battery Limit setting can be configured by booting into Surface UEFI (**Power + Vol Up** when turning on the device). Choose **boot configuration**, and then, under **Advanced Options**, toggle **Enable Battery Limit Mode** to **On**.
-
-
-
-## Enabling Battery Limit in Surface UEFI (Surface Pro 3)
-
-The Surface UEFI Battery Limit setting can be configured by booting into Surface UEFI (**Power + Vol Up** when turning on the device). Choose **Kiosk Mode**, select **Battery Limit**, and then choose **Enabled**.
-
-
-
-
-
-## Enabling Battery Limit using Surface Enterprise Management Mode (SEMM) or Surface Pro 3 firmware PowerShell scripts
-
-The Surface UEFI battery limit is also available for configuration via the following methods:
-
-- Surface Pro 4 and later
- - [Microsoft Surface UEFI Configurator](https://docs.microsoft.com/surface/surface-enterprise-management-mode)
- - Surface UEFI Manager Powershell scripts (SEMM_Powershell.zip) in the [Surface Tools for IT downloads](https://www.microsoft.com/download/details.aspx?id=46703)
-- Surface Pro 3
- - [SP3_Firmware_Powershell_Scripts.zip](https://www.microsoft.com/download/details.aspx?id=46703)
-
-### Using Microsoft Surface UEFI Configurator
-
-To configure Battery Limit mode, set the **Kiosk Overrides** setting on the **Advanced Settings** configuration page in SEMM (Surface Pro 4 and later).
-
-
-
-### Using Surface UEFI Manager PowerShell scripts
-
-The battery limit feature is controlled via the following setting:
-
-`407 = Battery Profile`
-
-**Description**: Active management scheme for battery usage pattern
-
-**Default**: `0`
-
-Set this to `1` to enable Battery Limit.
-
-### Using Surface Pro 3 firmware tools
-
-The battery limit feature is controlled via the following setting:
-
-**Name**: BatteryLimitEnable
-
-**Description**: BatteryLimit
-
-**Current Value**: `0`
-
-**Default Value**: `0`
-
-**Proposed Value**: `0`
-
-Set this to `1` to enable Battery Limit.
-
->[!NOTE]
->To configure this setting, you must use [SP3_Firmware_Powershell_Scripts.zip](https://www.microsoft.com/download/details.aspx?id=46703).
-
diff --git a/devices/surface/breadcrumb/toc.yml b/devices/surface/breadcrumb/toc.yml
deleted file mode 100644
index 1ab1f047c2..0000000000
--- a/devices/surface/breadcrumb/toc.yml
+++ /dev/null
@@ -1,7 +0,0 @@
-- name: Docs
- tocHref: /
- topicHref: /
- items:
- - name: Surface
- tocHref: /surface
- topicHref: /surface/index
\ No newline at end of file
diff --git a/devices/surface/change-history-for-surface.md b/devices/surface/change-history-for-surface.md
deleted file mode 100644
index 35be5e736d..0000000000
--- a/devices/surface/change-history-for-surface.md
+++ /dev/null
@@ -1,189 +0,0 @@
----
-title: Change history for Surface documentation (Windows 10)
-ms.reviewer:
-manager: laurawi
-description: This topic lists new and updated topics in the Surface documentation library.
-ms.prod: w10
-ms.mktglfcycl: manage
-ms.sitesec: library
-author: coveminer
-ms.author: v-jokai
-ms.topic: article
-ms.localizationpriority: medium
-ms.audience: itpro
----
-
-# Change history for Surface documentation
-
-This topic lists new and updated topics in the Surface documentation library.
-
-## January 2020
-| **New or changed topic** | **Description** |
-| ------------------------ | --------------- |
-| [Manage and deploy Surface driver and firmware updates](manage-surface-driver-and-firmware-updates.md)| Updated with the latest information and links to related articles.|
-
-
-## October 2019
-
-| **New or changed topic** | **Description** |
-| ------------------------ | --------------- |
-| [Intune management of Surface UEFI settings](surface-manage-dfci-guide.md)| New document explaining how to configure a DFCI environment in Microsoft Intune and manage firmware settings for targeted Surface devices.|
-| [Deploying, managing, and servicing Surface Pro X](surface-pro-arm-app-management.md)| New document highlighting key considerations for deploying, managing, and servicing Surface Pro X.|
-|Multiple topics| Updated with information on Surface Pro 7, Surface Pro X, and Surface Laptop 3.|
-
-## September 2019
-
-| **New or changed topic** | **Description** |
-| ------------------------ | --------------- |
-| [Surface Dock Firmware Update](surface-dock-firmware-update.md)| New document for Microsoft Surface Dock Firmware Update, newly redesigned to update Surface Dock firmware while running in the background on your Surface device.|
-
-## August 2019
-
-| **New or changed topic** | **Description** |
-| ------------------------ | --------------- |
-| [Optimizing wireless connectivity for Surface devices](surface-wireless-connect.md) | New document highlights key wireless connectivity considerations for Surface devices in mobile scenarios. |
-| [Manage and deploy Surface driver and firmware updates](manage-surface-driver-and-firmware-updates.md) | Updated to reflect minor changes in the file naming convention for Surface MSI files. |
-
-
-## July 2019
-
-| **New or changed topic** | **Description** |
-| ------------------------ | --------------- |
-| [Deploy Surface Diagnostic Toolkit for Business](surface-diagnostic-toolkit-business.md) | Renamed to reflect focus on deployment guidance for IT professionals. Covers minor changes in Version 2.41.139.0. |
-
-
-
-## June 2019
-
-| **New or changed topic** | **Description** |
-| ------------------------ | --------------- |
-|[Fix common Surface problems using the Surface Diagnostic Toolkit for Business](surface-diagnostic-toolkit-for-business-intro.md) | New introductory page for the Surface Diagnostic Toolkit for Business. |
-| [Best practice power settings for Surface devices](maintain-optimal-power-settings-on-Surface-devices.md) |Updated with summary of recommendations for managing power settings and optimizing battery life. |
-
-
-## March 2019
-
-| **New or changed topic** | **Description** |
-| ------------------------ | --------------- |
-| [Surface System SKU reference](surface-system-sku-reference.md) | New |
-
-
-## February 2019
-
-New or changed topic | Description
---- | ---
-[Surface Asset Tag](assettag.md) | New
-
-
-## January 2019
-
-New or changed topic | Description
---- | ---
-[Surface Brightness Control](microsoft-surface-brightness-control.md) | New
-[Maintain optimal power settings on Surface devices](maintain-optimal-power-settings-on-Surface-devices.md) | New
-|[Manage and deploy Surface driver and firmware updates](manage-surface-driver-and-firmware-updates.md) | Added Surface Studio 2 |
-
-
-## November 2018
-
-New or changed topic | Description
---- | ---
-|[Manage and deploy Surface driver and firmware updates](manage-surface-driver-and-firmware-updates.md) | Added Surface Pro 6 |
-[Surface Diagnostic Toolkit for Business](surface-diagnostic-toolkit-business.md) | New
-[Use Surface Diagnostic Toolkit for Business in desktop mode](surface-diagnostic-toolkit-desktop-mode.md) | New
-[Run Surface Diagnostic Toolkit for Business using commands](surface-diagnostic-toolkit-command-line.md) | New
-
-## October 2018
-
-New or changed topic | Description
---- | ---
-[Battery Limit setting](battery-limit.md) | New
-|[Manage and deploy Surface driver and firmware updates](manage-surface-driver-and-firmware-updates.md) | Added Surface GO |
-
-## May 2018
-
-|New or changed topic | Description |
-| --- | --- |
-|[Microsoft Surface Data Eraser](microsoft-surface-data-eraser.md) | Added version 3.2.58.0 information |
-|[Surface device compatibility with Windows 10 Long-Term Servicing Channel (LTSC)](surface-device-compatibility-with-windows-10-ltsc.md) | Removed note box around content |
-
-## February 2018
-
-|New or changed topic | Description |
-| --- | --- |
-|[Microsoft Surface Data Eraser](microsoft-surface-data-eraser.md) | Added version 3.2.46.0 information |
-
-## January 2018
-
-|New or changed topic | Description |
-| --- | --- |
-|[Windows Autopilot and Surface devices](windows-autopilot-and-surface-devices.md) | New article |
-|[Microsoft Surface Data Eraser](microsoft-surface-data-eraser.md) | Added version 3.2.45.0 information |
-|[Surface device compatibility with Windows 10 Long-Term Servicing Channel (LTSC)](surface-device-compatibility-with-windows-10-ltsc.md) | Updated Current Branch (CB) or Current Branch for Business (CBB) servicing options with Semi-Annual Channel (SAC) information |
-|[Wake On LAN for Surface devices](wake-on-lan-for-surface-devices.md) | Added Surface Book 2, Surface Laptop, Surface Pro, Surface Pro with LTE Advanced, and Surface Pro information |
-
-## December 2017
-
-|New or changed topic | Description |
-| --- | --- |
-|[Manage and deploy Surface driver and firmware updates](manage-surface-driver-and-firmware-updates.md) | Added Surface Book 2, Surface Laptop, Surface Pro, and Surface Pro with LTE Advanced information |
-
-## October 2017
-
-New or changed topics | Description
---- | ---
-Microsoft Surface Diagnostic Toolkit | Topic removed. The Microsoft Surface Diagnostic Toolkit is no longer available for download.
-
-## September 2017
-
-New or changed topic | Description
---- | ---
-[Top support solutions for Surface devices](support-solutions-surface.md) | New
-
-## June 2017
-
-|New or changed topic | Description |
-| --- | --- |
-|[Surface Data Eraser](microsoft-surface-data-eraser.md) | Update compatible devices, added version 3.2.36 information |
-|[Surface Deployment Accelerator](microsoft-surface-deployment-accelerator.md) | Added version 2.0.8.0 information |
-
-
-## April 2017
-
-|New or changed topic | Description |
-| --- | --- |
-|[Surface device compatibility with Windows 10 Long-Term Servicing Branch](surface-device-compatibility-with-windows-10-ltsc.md) | New (supersedes [Long-Term Servicing Branch for Surface devices](ltsb-for-surface.md))|
-
-
-## January 2017
-
-|New or changed topic | Description |
-| --- | --- |
-|[Wake On LAN for Surface devices](wake-on-lan-for-surface-devices.md) | New |
-
-## December 2016
-
-|New or changed topic | Description |
-| --- | --- |
-|[Manage and deploy Surface driver and firmware updates](manage-surface-driver-and-firmware-updates.md) | Added driver info for Surface Studio; updated info for Surface Book and Surface Pro 4 (Windows 10 .zip cumulative update), Surface Pro 3 (Windows8.1-KB2969817-x64.msu), and Surface 3 (UEFI Asset Tag management tool)|
-
-## November 2016
-
-|New or changed topic | Description |
-| --- | --- |
-|[Surface Enterprise Management Mode](surface-enterprise-management-mode.md) | Added procedure for viewing certificate thumbprint. |
-|[Use Microsoft Endpoint Configuration Manager to manage devices with SEMM](use-system-center-configuration-manager-to-manage-devices-with-semm.md) | New |
-
-
-
-## October 2016
-
-| New or changed topic | Description |
-| --- | --- |
-| [Considerations for Surface and Microsoft Endpoint Configuration Manager](considerations-for-surface-and-system-center-configuration-manager.md) | New |
-| [Long-term servicing branch for Surface devices](ltsb-for-surface.md) | New |
-
-
-
-
-
diff --git a/devices/surface/considerations-for-surface-and-system-center-configuration-manager.md b/devices/surface/considerations-for-surface-and-system-center-configuration-manager.md
deleted file mode 100644
index f68989b045..0000000000
--- a/devices/surface/considerations-for-surface-and-system-center-configuration-manager.md
+++ /dev/null
@@ -1,80 +0,0 @@
----
-title: Considerations for Surface and Microsoft Endpoint Configuration Manager
-description: The management and deployment of Surface devices with Configuration Manager is fundamentally the same as any other PC; this article describes scenarios that may require additional considerations.
-keywords: manage, deployment, updates, driver, firmware
-ms.prod: w10
-ms.mktglfcycl: deploy
-ms.pagetype: surface, devices
-ms.sitesec: library
-author: coveminer
-ms.author: v-jokai
-ms.topic: article
-ms.localizationpriority: medium
-ms.audience: itpro
-ms.reviewer:
-manager: laurawi
----
-
-# Considerations for Surface and Microsoft Endpoint Configuration Manager
-
-Fundamentally, management and deployment of Surface devices with Microsoft Endpoint Configuration Manager is the same as the management and deployment of any other PC. Like any other PC, a deployment to Surface devices includes importing drivers, importing a Windows image, preparing a deployment task sequence, and then deploying the task sequence to a collection. After deployment, Surface devices are like any other Windows client; to publish apps, settings, and policies, you use the same process as you would use for any other device.
-
-You can find more information about how to use Configuration Manager to deploy and manage devices in the [Documentation for Microsoft Endpoint Configuration Manager](https://docs.microsoft.com/sccm/index).
-
-Although the deployment and management of Surface devices is fundamentally the same as any other PC, there are some scenarios that may require additional considerations or steps. This article provides descriptions and guidance for these scenarios. The solutions documented in this article may apply to other devices and manufacturers as well.
-
-> [!NOTE]
-> For management of Surface devices it is recommended that you use the Current Branch of Microsoft Endpoint Configuration Manager.
-
-## Updating Surface device drivers and firmware
-
-For devices that recieve updates through Windows Update, drivers for Surface components (and even firmware updates) are applied automatically as part of the Windows Update process. For devices with managed updates, such as those updated through Windows Server Update Services (WSUS) or Configuration Manager, see [Manage Surface driver and firmware updates](https://docs.microsoft.com/surface/manage-surface-driver-and-firmware-updates/).
-
-> [!NOTE]
-> Surface device drivers and firmware are signed with SHA-256, which is not natively supported by Windows Server 2008 R2. A workaround is available for Configuration Manager environments running on Windows Server 2008 R2. For more information, see [Can't import drivers into Microsoft Endpoint Configuration Manager (KB3025419)](https://support.microsoft.com/kb/3025419).
-
-## Surface Ethernet adapters and Configuration Manager deployment
-
-The default mechanism that Configuration Manager uses to identify devices during deployment is the Media Access Control (MAC) address. Because the MAC address is associated with the Ethernet controller, an Ethernet adapter shared among multiple devices will cause Configuration Manager to identify each of the devices as only a single device. This can cause a Configuration Manager deployment of Windows to not be applied to intended devices.
-
-To ensure that Surface devices using the same Ethernet adapter are identified as unique devices during deployment, you can instruct Configuration Manager to identify devices using another method. This other method could be the MAC address of the wireless network adapter or the System Universal Unique Identifier (System UUID). You can specify that Configuration Manager use other identification methods with the following options:
-
-* Add an exclusion for the MAC addresses of Surface Ethernet adapters, which forces Configuration Manager to overlook the MAC address in preference of the System UUID, as documented in the [Reusing the same NIC for multiple PXE initiated deployments in SMicrosoft Endpoint Configuration Manager OSD](https://blogs.technet.microsoft.com/system_center_configuration_manager_operating_system_deployment_support_blog/2015/08/27/reusing-the-same-nic-for-multiple-pxe-initiated-deployments-in-system-center-configuration-manger-osd/) blog post.
-
-* Prestage devices by System UUID as documented in the [Reusing the same NIC for multiple PXE initiated deployments in Microsoft Endpoint Configuration Manager OSD](https://blogs.technet.microsoft.com/system_center_configuration_manager_operating_system_deployment_support_blog/2015/08/27/reusing-the-same-nic-for-multiple-pxe-initiated-deployments-in-system-center-configuration-manger-osd/) blog post.
-
-* Use a script to identify a newly deployed Surface device by the MAC address of its wireless adapter, as documented in the [How to Use The Same External Ethernet Adapter For Multiple SCCM OSD](https://blogs.technet.microsoft.com/askpfeplat/2014/07/27/how-to-use-the-same-external-ethernet-adapter-for-multiple-sccm-osd/) blog post.
-
-Another consideration for the Surface Ethernet adapter during deployments with Configuration Manager is the driver for the Ethernet controller. Beginning in Windows 10, version 1511, the driver for the Surface Ethernet adapter is included by default in Windows. For organizations that want to deploy the latest version of Windows 10 and use the latest version of WinPE, use of the Surface Ethernet adapter requires no additional actions.
-
-For versions of Windows prior to Windows 10, version 1511 (including Windows 10 RTM and Windows 8.1), you may still need to install the Surface Ethernet adapter driver and include the driver in your WinPE boot media. With its inclusion in Windows 10, the driver is no longer available for download from the Microsoft Download Center. To download the Surface Ethernet adapter driver, download it from the Microsoft Update Catalog as documented in the [Surface Ethernet Drivers](https://blogs.technet.microsoft.com/askcore/2016/08/18/surface-ethernet-drivers/) blog post from the Ask The Core Team blog.
-
-## Deploy Surface app with Configuration Manager
-
-With the release of Microsoft Store for Business, Surface app is no longer available as a driver and firmware download. Organizations that want to deploy Surface app to managed Surface devices or during deployment with the use of Configuration Manager, must acquire Surface app through Microsoft Store for Business and then deploy Surface app with PowerShell. You can find the PowerShell commands for deployment of Surface app, instructions to download Surface app, and prerequisite frameworks from Microsoft Store for Business in the [Deploy Surface app with Microsoft Store for Business](https://technet.microsoft.com/itpro/surface/deploy-surface-app-with-windows-store-for-business) article in the TechNet Library.
-
-## Use prestaged media with Surface clients
-
-If your organization uses prestaged media to pre-load deployment resources on to machines prior to deployment with Configuration Manager, the nature of Surface devices as UEFI devices may require you to take additional steps. Specifically, a native UEFI environment requires that you create multiple partitions on the boot disk of the system. If you are following along with the [documentation for prestaged media](https://technet.microsoft.com/library/79465d90-4831-4872-96c2-2062d80f5583?f=255&MSPPError=-2147217396#BKMK_CreatePrestagedMedia), the instructions provide for only single partition boot disks and therefore will fail when applied to Surface devices.
-
-Instructions for applying prestaged media to UEFI devices, such as Surface devices, can be found in the [How to apply Task Sequence Prestaged Media on multi-partitioned disks for BIOS or UEFI PCs in Microsoft Endpoint Configuration Manager](https://blogs.technet.microsoft.com/system_center_configuration_manager_operating_system_deployment_support_blog/2014/04/02/how-to-apply-task-sequence-prestaged-media-on-multi-partitioned-disks-for-bios-or-uefi-pcs-in-system-center-configuration-manager/) blog post.
-
-## Licensing conflicts with OEM Activation 3.0
-
-Surface devices come preinstalled with a licensed copy of Windows. For example, Surface Pro 4 is preinstalled with Windows 10 Professional. The license key for this preinstalled copy of Windows is embedded in the firmware of the device with OEM Activation 3.0 (OA 3.0). When you run Windows installation media on a device with an OA 3.0 key, Windows setup automatically reads the license key and uses it to install and activate Windows. In most situations, this simplifies the reinstallation of Windows, because the user does not have to find or enter a license key.
-
-When you reimage a device by using Windows Enterprise, this embedded license key does not cause a conflict. This is because the installation media for Windows Enterprise is configured to install only an Enterprise edition of Windows and therefore is incompatible with the license key embedded in the system firmware. If a product key is not specified (such as when you intend to activate with Key Management Services [KMS] or Active Directory Based Activation), a Generic Volume License Key (GVLK) is used until Windows is activated by one of those technologies.
-
-However, issues may arise when organizations intend to use versions of Windows that are compatible with the firmware embedded key. For example, an organization that wants to install Windows 10 Professional on a Surface 3 device that originally shipped with Windows 10 Home edition may encounter difficulty when Windows setup automatically reads the Home edition key during installation and installs as Home edition rather than Professional. To avoid this conflict, you can use the Ei.cfg or Pid.txt file to explicitly instruct Windows setup to prompt for a product key, or you can enter a specific product key in the deployment task sequence. For more information, see [Windows Setup Edition Configuration and Product ID Files](https://technet.microsoft.com/library/hh824952.aspx). If you do not have a specific key, you can use the default product keys for Windows, which you can find in [Customize and deploy a Windows 10 operating system](https://dpcenter.microsoft.com/en/Windows/Build/cp-Windows-10-build) on the Device Partner Center.
-
-## Apply an asset tag during deployment
-
-Surface Studio, Surface Book, Surface Pro 4, Surface Pro 3, and Surface 3 devices all support the application of an asset tag in UEFI. This asset tag can be used to identify the device from UEFI even if the operating system fails, and it can also be queried from within the operating system. To read more about the Surface Asset Tag function, see the [Asset Tag Tool for Surface Pro 3](https://blogs.technet.microsoft.com/askcore/2014/10/20/asset-tag-tool-for-surface-pro-3/) blog post.
-
-To apply an asset tag using the [Surface Asset Tag CLI Utility](https://www.microsoft.com/download/details.aspx?id=44076) during a Configuration Manager deployment task sequence, use the script and instructions found in the [Set Surface Asset Tag During a Configuration Manager Task Sequence](https://blogs.technet.microsoft.com/jchalfant/set-surface-pro-3-asset-tag-during-a-configuration-manager-task-sequence/) blog post.
-
-## Configure push-button reset
-
-When you deploy Windows to a Surface device, the push-button reset functionality of Windows is configured by default to revert the system back to a state where the environment is not yet configured. When the reset function is used, the system discards any installed applications and settings. Although in some situations it can be beneficial to restore the system to a state without applications and settings, in a professional environment this effectively renders the system unusable to the end user.
-
-Push-button reset can be configured, however, to restore the system configuration to a state where it is ready for use by the end user. Follow the process outlined in [Deploy push-button reset features](https://msdn.microsoft.com/windows/hardware/commercialize/manufacture/desktop/deploy-push-button-reset-features) to customize the push-button reset experience for your devices.
diff --git a/devices/surface/customize-the-oobe-for-surface-deployments.md b/devices/surface/customize-the-oobe-for-surface-deployments.md
deleted file mode 100644
index 70d53dae71..0000000000
--- a/devices/surface/customize-the-oobe-for-surface-deployments.md
+++ /dev/null
@@ -1,75 +0,0 @@
----
-title: Customize the OOBE for Surface deployments (Surface)
-description: This article will walk you through the process of customizing the Surface out-of-box experience for end users in your organization.
-ms.assetid: F6910315-9FA9-4297-8FA8-2C284A4B1D87
-ms.reviewer:
-manager: laurawi
-keywords: deploy, customize, automate, network, Pen, pair, boot
-ms.localizationpriority: medium
-ms.prod: w10
-ms.mktglfcycl: deploy
-ms.pagetype: surface, devices
-ms.sitesec: library
-author: coveminer
-ms.author: v-jokai
-ms.topic: article
-ms.audience: itpro
----
-
-# Customize the OOBE for Surface deployments
-
-This article describes customizing the Surface out-of-box experience for end users in your organization.
-
-It is common practice in a Windows deployment to customize the user experience for the first startup of deployed computers — the out-of-box experience, or OOBE.
-
->[!NOTE]
->OOBE is also often used to describe the phase, or configuration pass, of Windows setup during which the user experience is displayed. For more information about the OOBE phase of setup, see [How Configuration Passes Work](https://msdn.microsoft.com/library/windows/hardware/dn898581.aspx).
-
-In some scenarios, you may want to provide complete automation to ensure that at the end of a deployment, computers are ready for use without any interaction from the user. In other scenarios, you may want to leave key elements of the experience for users to perform necessary actions or select between important choices. For administrators deploying to Surface devices, each of these scenarios presents a unique challenge to overcome.
-
-> [!NOTE]
-> This article does not apply to Surface Pro X. For more information, refer to [Deploying, managing, and servicing Surface Pro X](surface-pro-arm-app-management.md)
-
-This article provides a summary of the scenarios where a deployment might require additional steps. It also provides the required information to ensure that the desired experience is achieved on any newly deployed Surface device. This article is intended for administrators who are familiar with the deployment process, as well as concepts such as answer files and [reference images](https://technet.microsoft.com/itpro/windows/deploy/create-a-windows-10-reference-image).
-
->[!NOTE]
->Although the OOBE phase of setup is still run during a deployment with an automated deployment solution such as the [Microsoft Deployment Toolkit (MDT)](https://go.microsoft.com/fwlink/p/?LinkId=618117) or Microsoft Endpoint Configuration Manager Operating System Deployment (OSD), it is automated by the settings supplied in the Deployment Wizard and task sequence. For more information see:
->- [Deploy Windows 10 with the Microsoft Deployment Toolkit](https://technet.microsoft.com/itpro/windows/deploy/deploy-windows-10-with-the-microsoft-deployment-toolkit)
->- [Deploy Windows 10 with System Center 2012 R2 Configuration Manager](https://technet.microsoft.com/itpro/windows/deploy/deploy-windows-10-with-system-center-2012-r2-configuration-manager)
-
-
-
-## Scenario 1: Wireless networking in OOBE with MDT 2013
-
-
-When a wireless network adapter is present during OOBE, the **Join a wireless network** page is displayed, which prompts a user to connect to a wireless network. This page is not automatically hidden by deployment technologies, including MDT 2013, and therefore will be displayed even when a deployment is configured for complete automation.
-
-To ensure that an automated deployment is not stopped by this page, the page must be hidden by configuring an additional setting in the answer file, **HideWirelessSetupInOOBE**. You can find additional information about the **HideWirelessSetupInOOBE** setting in [Unattended Windows Setup Reference](https://technet.microsoft.com/library/ff716213.aspx).
-
-## Scenario 2: Surface Pen pairing in OOBE
-
-
-When you first take a Surface Pro 3, Surface Pro 4, Surface Book, or Surface Studio out of the package and start it up, the first-run experience of the factory image includes a prompt that asks you to pair the included Surface Pen to the device. This prompt is only provided by the factory image that ships with the device and is not included in other images used for deployment, such as the Windows Enterprise installation media downloaded from the Volume Licensing Service Center. Because pairing the Bluetooth Surface Pen outside of this experience requires that you enter the Control Panel or PC Settings and manually pair a Bluetooth device, you may want to have users or a technician use this prompt to perform the pairing operation.
-
-To provide the factory Surface Pen pairing experience in OOBE, you must copy four files from the factory Surface image into the reference image. You can copy these files into the reference environment before you capture the reference image, or you can add them later by using Deployment Image Servicing and Management (DISM) to mount the image. The four required files are:
-
-- %windir%\\system32\\oobe\\info\\default\\1033\\oobe.xml
-- %windir%\\system32\\oobe\\info\\default\\1033\\PenPairing\_en-US.png
-- %windir%\\system32\\oobe\\info\\default\\1033\\PenError\_en-US.png
-- %windir%\\system32\\oobe\\info\\default\\1033\\PenSuccess\_en-US.png
-
->[!NOTE]
->You should copy the files from a factory image for the same model Surface device that you intend to deploy to. For example, you should use the files from a Surface Pro 7 to deploy to Surface Pro 7, and the files from Surface Book 2 to deploy Surface Book 2, but you should not use the files from a Surface Pro 7 to deploy Surface Book or Surface Pro 6.
-
-
-
-The step-by-step process for adding these required files to an image is described in [Deploying Surface Pro 3 Pen and OneNote Tips](https://blogs.technet.microsoft.com/askcore/2014/07/15/deploying-surface-pro-3-pen-and-onenote-tips/). This blog post also includes tips to ensure that the necessary updates for the Surface Pen Quick Note-Taking Experience are installed, which allows users to send notes to OneNote with a single click.
-
-
-
-
-
-
-
-
-
diff --git a/devices/surface/deploy-surface-app-with-windows-store-for-business.md b/devices/surface/deploy-surface-app-with-windows-store-for-business.md
deleted file mode 100644
index 121be61007..0000000000
--- a/devices/surface/deploy-surface-app-with-windows-store-for-business.md
+++ /dev/null
@@ -1,185 +0,0 @@
----
-title: Deploy Surface app with Microsoft Store for Business or Microsoft Store for Education (Surface)
-description: Find out how to add and download Surface app with Microsoft Store for Business or Microsoft Store for Education, as well as install Surface app with PowerShell and MDT.
-keywords: surface app, app, deployment, customize
-ms.prod: w10
-ms.mktglfcycl: deploy
-ms.pagetype: surface, store
-ms.sitesec: library
-author: coveminer
-ms.author: v-jokai
-ms.topic: article
-ms.localizationpriority: medium
-ms.audience: itpro
-ms.reviewer:
-manager: laurawi
----
-
-# Deploy Surface app with Microsoft Store for Business and Education
-
-**Applies to**
-
-- Surface Pro 7
-- Surface Laptop 3
-- Surface Pro 6
-- Surface Laptop 2
-- Surface Go
-- Surface Go with LTE
-- Surface Book 2
-- Surface Pro with LTE Advanced (Model 1807)
-- Surface Pro (Model 1796)
-- Surface Laptop
-- Surface Studio
-- Surface Studio 2
-- Surface Book
-- Surface Pro 4
-- Surface 3 LTE
-- Surface 3
-- Surface Pro 3
-
-
-The Surface app is a lightweight Microsoft Store app that provides control of many Surface-specific settings and options, including:
-
-* Enable or disable the Windows button on the Surface device
-
-* Adjust the sensitivity of a Surface Pen
-
-* Customize Surface Pen button actions
-
-* Enable or disable Surface audio enhancements
-
-* Quick access to support documentation and information for your device
-
-Customers using Windows Update will ordinarily receive Surface app as part of automatic updates. But if your organization is preparing images for deployment to your Surface devices, you may want to include the Surface app (formerly called the Surface Hub) in your imaging and deployment process instead of requiring users of each individual device to download and install the app from the Microsoft Store or your Microsoft Store for Business.
-
-> [!NOTE]
-> This article does not apply to Surface Pro X. For more information, refer to [Deploying, managing, and servicing Surface Pro X](surface-pro-arm-app-management.md)
-
-## Surface app overview
-
-The Surface app is available as a free download from the [Microsoft Store](https://www.microsoft.com/store/apps/Surface/9WZDNCRFJB8P). Users can download and install it from the Microsoft Store, but if your organization uses Microsoft Store for Business instead, you will need to add it to your store’s inventory and possibly include the app as part of your Windows deployment process. These processes are discussed throughout this article. For more information about Microsoft Store for Business, see [Microsoft Store for Business](https://docs.microsoft.com/microsoft-store/) in the Windows TechCenter.
-
-## Add Surface app to a Microsoft Store for Business account
-
-Before users can install or deploy an app from a company’s Microsoft Store for Business account, the desired app(s) must first be made available and licensed to the users of a business.
-
-1. If you have not already done so, create a [Microsoft Store for Business account](https://www.microsoft.com/business-store).
-
-2. Log on to the portal.
-
-3. Enable offline licensing: click **Manage->Store settings**, and then select the **Show offline licensed apps to people shopping in the store** checkbox, as shown in Figure 1. For more information about Microsoft Store for Business app licensing models, see [Apps in Microsoft Store for Business and Education](https://docs.microsoft.com/microsoft-store/).
- 
- *Figure 1. Enable apps for offline use*
-
-4. Add Surface app to your Microsoft Store for Business account by following this procedure:
- * Click the **Shop** menu.
- * In the search box, type **Surface app**, and then click the search icon.
- * After the Surface app is presented in the search results, click the app’s icon.
- * You are presented with a choice (select **Online** or **Offline**), as shown in Figure 2.
-
- 
-
- *Figure 2. Select the Offline licensing mode and add the app to your inventory*
-
- * Click **Offline** to select the Offline licensing mode.
- * Click **Get the app** to add the app to your Microsoft Store for Business inventory. As shown in Figure 3, you’ll see a dialog box that prompts you to acknowledge that offline apps can be deployed using a management tool or downloaded from the company’s inventory page in their private store.
-
- 
-
- *Figure 3. Offline-licensed app acknowledgement*
- * Click **OK**.
-
-## Download Surface app from a Microsoft Store for Business account
-After you add an app to the Microsoft Store for Business account in Offline mode, you can download and add the app as an AppxBundle to a deployment share.
-1. Log on to the Microsoft Store for Business account at https://businessstore.microsoft.com.
-2. Click **Manage->Apps & software**. A list of all of your company’s apps is displayed, including the Surface app you added in the [Add Surface app to a Microsoft Store for Business account](#add-surface-app-to-a-microsoft-store-for-business-account) section of this article.
-3. Under **Actions**, click the ellipsis (**…**), and then click **Download for offline use** for the Surface app.
-4. Select the desired **Platform** and **Architecture** options from the available selections for the selected app, as shown in Figure 4.
-
- 
-
- *Figure 4. Download the AppxBundle package for an app*
-5. Click **Download**. The AppxBundle package will be downloaded. Make sure you note the path of the downloaded file because you’ll need that later in this article.
-6. Click either the **Encoded license** or **Unencoded license** option. Use the Encoded license option with management tools like Microsoft Endpoint Configuration Manager or when you use Windows Configuration Designer to create a provisioning package. Select the Unencoded license option when you use Deployment Image Servicing and Management (DISM) or deployment solutions based on imaging, including the Microsoft Deployment Toolkit (MDT).
-7. Click **Generate** to generate and download the license for the app. Make sure you note the path of the license file because you’ll need that later in this article.
-
->[!NOTE]
->When you download an app for offline use, such as the Surface app, you may notice a section at the bottom of the page labeled **Required frameworks**. Your target computers must have the frameworks installed for the app to run, so you may need to repeat the download process for each of the required frameworks for your architecture (either x86 or x64) and also include them as part of your Windows deployment discussed later in this article.
-
-Figure 5 shows the required frameworks for the Surface app.
-
-
-
-*Figure 5. Required frameworks for the Surface app*
-
->[!NOTE]
->The version numbers of the Surface app and required frameworks will change as the apps are updated. Check for the latest version of Surface app and each framework in Microsoft Store for Business. Always use the Surface app and recommended framework versions as provided by Microsoft Store for Business. Using outdated frameworks or the incorrect versions may result in errors or application crashes.
-
-To download the required frameworks for the Surface app, follow these steps:
-1. Click the **Download** button under **Microsoft.VCLibs.140.00_14.0.23816.0_x64__8wekyb3d8bbwe**. This downloads the Microsoft.VCLibs.140.00_14.0.23816.0_x64__8wekyb3d8bbwe.Appx file to your specified folder.
-2. Click the **Download** button under **Microsoft.NET.Native.Runtime.1.1_1.1.23406.0_x64__8wekyb3d8bbwe**. This downloads the Microsoft.NET.Native.Runtime.1.1_1.1.23406.0_x64__8wekyb3d8bbwe.Appx file to your specified folder.
-
->[!NOTE]
->Only the 64-bit (x64) version of each framework is required for Surface devices. Surface devices are native 64-bit UEFI devices and are not compatible with 32-bit (x86) versions of Windows that would require 32-bit frameworks.
-
-## Install Surface app on your computer with PowerShell
-The following procedure provisions the Surface app onto your computer and makes it available for any user accounts created on the computer afterwards.
-1. Using the procedure described in the [How to download Surface app from a Microsoft Store for Business account](#download-surface-app-from-a-microsoft-store-for-business-account) section of this article, download the Surface app AppxBundle and license file.
-2. Begin an elevated PowerShell session.
-
- >[!NOTE]
- >If you don’t run PowerShell as an Administrator, the session won’t have the required permissions to install the app.
-
-3. In the elevated PowerShell session, copy and paste the following command:
- ```
- Add-AppxProvisionedPackage –Online –PackagePath \ Microsoft.SurfaceHub_10.0.342.0_neutral_~_8wekyb3d8bbwe.AppxBundle –LicensePath \ Microsoft.SurfaceHub_8wekyb3d8bbwe_a53ef8ab-9dbd-dec1-46c5-7b664d4dd003.xml
- ```
-
- Where `` is the folder where you downloaded the AppxBundle and license file from the Microsoft Store for Business account.
-
- For example, if you downloaded the files to c:\Temp, the command you run is:
- ````
- Add-AppxProvisionedPackage –Online –PackagePath c:\Temp\ Microsoft.SurfaceHub_10.0.342.0_neutral_~_8wekyb3d8bbwe.AppxBundle –LicensePath c:\Temp\ Microsoft.SurfaceHub_8wekyb3d8bbwe_a53ef8ab-9dbd-dec1-46c5-7b664d4dd003.xml
- ```
-
-4. The Surface app will now be available on your current Windows computer.
-
-Before the Surface app is functional on the computer where it has been provisioned, you must also provision the frameworks described earlier in this article. To provision these frameworks, use the following procedure in the elevated PowerShell session you used to provision the Surface app.
-
-5. In the elevated PowerShell session, copy and paste the following command:
- ```
- Add-AppxProvisionedPackage –Online –SkipLicense –PackagePath \Microsoft.VCLibs.140.00_14.0.23816.0_x64__8wekyb3d8bbwe.Appx
- ```
-6. In the elevated PowerShell session, copy and paste the following command:
- ```
- Add-AppxProvisionedPackage –Online –SkipLicense –PackagePath \Microsoft.NET.Native.Runtime.1.1_1.1.23406.0_x64__8wekyb3d8bbwe.Appx
- ```
-
-## Install Surface app with MDT
-The following procedure uses MDT to automate installation of the Surface app at the time of deployment. The application is provisioned automatically by MDT during deployment and thus you can use this process with existing images. This is the recommended process to deploy the Surface app as part of a Windows deployment to Surface devices because it does not reduce the cross platform compatibility of the Windows image.
-1. Using the procedure described [earlier in this article](#download-surface-app-from-a-microsoft-store-for-business-account), download the Surface app AppxBundle and license file.
-2. Using the New Application Wizard in the MDT Deployment Workbench, import the downloaded files as a new **Application with source files**.
-3. On the **Command Details** page of the New Application Wizard, specify the default **Working Directory** and for the **Command** specify the file name of the AppxBundle, as follows:
-
- * Command:
- ```
- Microsoft.SurfaceHub_10.0.342.0_neutral_~_8wekyb3d8bbwe.AppxBundle
- ```
- * Working Directory: %DEPLOYROOT%\Applications\SurfaceApp
-
-For the Surface app to function on the target computer, it will also require the frameworks described earlier in this article. Use the following procedure to import the frameworks required for the Surface app into MDT and to configure them as dependencies.
-1. Using the procedure described earlier in this article, download the framework files. Store each framework in a separate folder.
-2. Using the New Application Wizard in the MDT Deployment Workbench, import the downloaded files as a new **Application with source files**.
-3. On the **Command Details** page, type the file name of each application you downloaded in the **Command** field and the default Working Directory.
-
-To configure the frameworks as dependencies of the Surface app, use this process:
-1. Open the properties of the Surface app in the MDT Deployment Workbench.
-2. Click the **Dependencies** tab, and then click **Add**.
-3. Select the check box for each framework using the name you provided in the New Application Wizard.
-
-After import, the Surface app will be available for selection in the **Applications** step of the Windows Deployment Wizard. You can also install the application automatically by specifying the application in the deployment task sequence by following this process:
-1. Open your deployment task sequence in the MDT Deployment Workbench.
-2. Add a new **Install Application** task in the **State Restore** section of deployment.
-3. Select **Install a single application** and specify the **Surface App** as the **Application to be installed**.
-
-For more information about including apps into your Windows deployments, see [Deploy Windows 10 with the Microsoft Deployment Toolkit](https://technet.microsoft.com/itpro/windows/deploy/deploy-windows-10-with-the-microsoft-deployment-toolkit).
diff --git a/devices/surface/deploy-windows-10-to-surface-devices-with-mdt.md b/devices/surface/deploy-windows-10-to-surface-devices-with-mdt.md
deleted file mode 100644
index 47f14939db..0000000000
--- a/devices/surface/deploy-windows-10-to-surface-devices-with-mdt.md
+++ /dev/null
@@ -1,35 +0,0 @@
----
-title: Deploy Windows 10 to Surface devices with Microsoft Deployment Toolkit (Surface)
-description: Walk through the recommended process of how to deploy Windows 10 to your Surface devices with the Microsoft Deployment Toolkit.
-keywords: windows 10 surface, automate, customize, mdt
-ms.prod: w10
-ms.mktglfcycl: deploy
-ms.pagetype: surface
-ms.sitesec: library
-author: coveminer
-ms.author: v-jokai
-ms.topic: article
-ms.localizationpriority: medium
-ms.audience: itpro
-ms.reviewer:
-manager: laurawi
-ms.date: 04/24/2020
----
-
-# Deploy Windows 10 to Surface devices with Microsoft Deployment Toolkit
-
-**Applies to**
-
-- Surface Studio and later
-- Surface Pro 4 and later
-- Surface Book and later
-- Surface Laptop and later
-- Surface Go
-- Surface 3
-- Windows 10
-
-> [!NOTE]
-> MDT is not supported on Surface Pro X. For more information, refer to [Deploying, managing, and servicing Surface Pro X](surface-pro-arm-app-management.md).
-
-For the latest information about using MDT, refer to [Deploy a Windows 10 image using MDT](https://docs.microsoft.com/windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt).
-
diff --git a/devices/surface/deploy.md b/devices/surface/deploy.md
deleted file mode 100644
index a7220315da..0000000000
--- a/devices/surface/deploy.md
+++ /dev/null
@@ -1,46 +0,0 @@
----
-title: Deploy Surface devices (Surface)
-description: Get deployment guidance for your Surface devices including information about MDT, OOBE customization, Ethernet adaptors, and Surface Deployment Accelerator.
-ms.prod: w10
-ms.mktglfcycl: manage
-ms.pagetype: surface, devices
-ms.sitesec: library
-author: coveminer
-ms.reviewer:
-manager: laurawi
-ms.author: v-jokai
-ms.topic: article
-ms.localizationpriority: medium
-ms.audience: itpro
----
-
-# Deploy Surface devices
-
-Learn about about deploying ARM- and Intel-based Surface devices.
-
-## Deploying ARM-based devices
-
-| Topic | Description |
-| --- | --- |
-| [Deploying, managing, and servicing Surface Pro X](surface-pro-arm-app-management.md) | Get an overview of key considerations for deploying, managing, and servicing Surface Pro X running the Microsoft SQ1 ARM processor. |
-| [Windows Autopilot and Surface devices](windows-autopilot-and-surface-devices.md) | Learn about Autopilot, the recommended method for deploying Surface Pro X. |
-| [Windows 10 ARM-based PC app compatibility](surface-pro-arm-app-performance.md) | Review app compatibility guidance for Surface Pro X. |
-
-
-## Deploying Intel-based devices
-
-| Topic | Description |
-| --- | --- |
-| [Windows Autopilot and Surface devices](windows-autopilot-and-surface-devices.md) | Find out how to remotely deploy and configure devices with Windows Autopilot. |
-| [Surface device compatibility with Windows 10 Long-Term Servicing Channel](surface-device-compatibility-with-windows-10-ltsc.md) | Find out about compatibility and limitations of Surface devices running Windows 10 Enterprise LTSC edition. |
-| [Deploy Windows 10 to Surface devices with MDT](deploy-windows-10-to-surface-devices-with-mdt.md) | Walk through the recommended process of how to deploy Windows 10 to your Surface devices with the Microsoft Deployment Toolkit.|
-| [Upgrade Surface devices to Windows 10 with MDT](upgrade-surface-devices-to-windows-10-with-mdt.md)| Find out how to perform a Windows 10 upgrade deployment to your Surface devices. |
-| [Customize the OOBE for Surface deployments](customize-the-oobe-for-surface-deployments.md)| Walk through the process of customizing the Surface out-of-box experience for end users in your organization.|
-| [Ethernet adapters and Surface deployment](ethernet-adapters-and-surface-device-deployment.md)| Get guidance and answers to help you perform a network deployment to Surface devices.|
-| [Surface Deployment Accelerator](microsoft-surface-deployment-accelerator.md)| See how Microsoft Surface Deployment Accelerator provides a quick and simple deployment mechanism for organizations to reimage Surface devices. |
-[Battery Limit setting](battery-limit.md) | Learn how to use Battery Limit, a UEFI setting that changes how the Surface device battery is charged and may prolong its longevity.
-
-## Related topics
-
-[Surface IT Pro Blog](https://techcommunity.microsoft.com/t5/Surface-IT-Pro-Blog/bg-p/SurfaceITPro)
-
diff --git a/devices/surface/documentation/surface-system-sku-reference.md b/devices/surface/documentation/surface-system-sku-reference.md
deleted file mode 100644
index 0d49be965e..0000000000
--- a/devices/surface/documentation/surface-system-sku-reference.md
+++ /dev/null
@@ -1,54 +0,0 @@
----
-title: Surface System SKU reference
-description: This topic provides a reference of System SKU names that you can use to quickly determine the machine state of a specific device.
-ms.prod: w10
-ms.mktglfcycl: manage
-ms.sitesec: library
-author: coveminer
-ms.author: v-jokai
-ms.topic: article
----
-# Surface System SKU Reference
-This document provides a reference of System SKU names that you can use to quickly determine the machine state of a specific device using PowerShell, WMI, and related tools.
-
-System SKU is a variable (along with System Model and others) stored in System Management BIOS (SMBIOS) tables in the UEFI layer of Surface devices. Use the System SKU name whenever you need to differentiate between devices with the same System Model name, such as Surface Pro and Surface Pro with LTE Advanced.
-
-| **Device**| **System Model** | **System SKU**|
-| --- | ---| --- |
-| Surface 3 WiFI | Surface 3 | Surface_3 |
-| Surface 3 LTE AT&T | Surface 3 | Surface_3_US1 |
-| Surface 3 LTE Verizon | Surface 3 | Surface_3_US2 |
-| Surface 3 LTE North America | Surface 3 | Surface_3_NAG |
-| Surface 3 LTE Outside of North America and T-Mobile In Japan | Surface 3 | Surface_3_ROW |
-| Surface Pro | Surface Pro | Surface_Pro_1796 |
-| Surface Pro with LTE Advanced | Surface Pro | Surface_Pro_1807 |
-| Surface Book 2 13inch | Surface Book 2 | Surface_Book_1832 |
-| Surface Book 2 15inch | Surface Book 2 | Surface_Book_1793 |
-| Surface Go Consumer | Surface Go | Surface_Go_1824_Consumer |
-| Surface Go Commercial | Surface Go | Surface_Go_1824_Commercial |
-| Surface Pro 6 Consumer | Surface Pro 6 | Surface_Pro_6_1796_Consumer |
-| Surface Pro 6 Commercial | Surface Pro 6 | Surface_Pro_6_1796_Commercial |
-| Surface Laptop 2 Consumer | Surface Laptop 2 | Surface_Laptop_2_1769_Consumer |
-| Surface Laptop 2 Commercial | Surface Laptop 2 | Surface_Laptop_2_1769_Commercial |
-
-## Using System SKU variables
-
-### PowerShell
-
- gwmi -namespace root\wmi -class MS_SystemInformation | select SystemSKU
-
-### System Information
-You can also find the System SKU and System Model for a device in System Information.
-- Click **Start** > **MSInfo32**.
-
-### WMI
-You can use System SKU variables in a Task Sequence WMI Condition in the Microsoft Deployment Toolkit (MDT) or Microsoft Endpoint Configuration Manager. For example:
-
- - WMI Namespace – Root\WMI
- - WQL Query – SELECT * FROM MS_SystemInformation WHERE SystemSKU = "Surface_Pro_1796"
-
-
-
-
-
-
diff --git a/devices/surface/enable-peap-eap-fast-and-cisco-leap-on-surface-devices.md b/devices/surface/enable-peap-eap-fast-and-cisco-leap-on-surface-devices.md
deleted file mode 100644
index d51a90413e..0000000000
--- a/devices/surface/enable-peap-eap-fast-and-cisco-leap-on-surface-devices.md
+++ /dev/null
@@ -1,95 +0,0 @@
----
-title: Enable PEAP, EAP-FAST, and Cisco LEAP on Surface devices (Surface)
-description: Find out how to enable support for PEAP, EAP-FAST, or Cisco LEAP protocols on your Surface device.
-ms.assetid: A281EFA3-1552-467D-8A21-EB151E58856D
-ms.reviewer:
-manager: laurawi
-keywords: network, wireless, device, deploy, authentication, protocol
-ms.localizationpriority: medium
-ms.prod: w10
-ms.mktglfcycl: deploy
-ms.pagetype: surface, devices
-ms.sitesec: library
-author: coveminer
-ms.author: v-jokai
-ms.topic: article
----
-
-# Enable PEAP, EAP-FAST, and Cisco LEAP on Surface devices
-
-
-Find out how to enable support for PEAP, EAP-FAST, or Cisco LEAP protocols on your Surface device.
-
-If you use PEAP, EAP-FAST, or Cisco LEAP in your enterprise network, you probably already know that these three wireless authentication protocols are not supported by Surface devices out of the box. Some users may discover this when they attempt to connect to your wireless network; others may discover it when they are unable to gain access to resources inside the network, like file shares and internal sites. For more information, see [Extensible Authentication Protocol](https://technet.microsoft.com/network/bb643147).
-
-You can add support for each protocol by executing a small MSI package from a USB stick or from a file share. For organizations that want to enable EAP support on their Surface devices, the MSI package format supports deployment with many management and deployment tools, like the Microsoft Deployment Toolkit (MDT) and Microsoft Endpoint Configuration Manager.
-
-## Download PEAP, EAP-FAST, or Cisco LEAP installation files
-
-
-You can download the MSI installation files for PEAP, EAP-FAST, or Cisco LEAP in a single zip archive file from the Microsoft Download Center. To download this file, go to the [Surface Tools for IT](https://www.microsoft.com/download/details.aspx?id=46703) page on the Microsoft Download Center, click **Download**, and then select the **Cisco EAP-Supplicant Installer.zip** file.
-
-## Deploy PEAP, EAP-FAST, or Cisco LEAP with MDT
-
-
-If you are already performing a Windows deployment to Surface devices in your organization, it is quick and easy to add the installation files for each protocol to your deployment share and configure automatic installation during deployment. You can even configure a task sequence that updates previously deployed Surface devices to provide support for these protocols using the same process.
-
-To enable support for PEAP, EAP-FAST, or Cisco LEAP on newly deployed Surface devices, follow these steps:
-
-1. Download and extract the installation files for each protocol to separate folders in an easily accessible location.
-
-2. Open the MDT Deployment Workbench and expand your deployment share to the **Applications** folder.
-
-3. Select **New Application** from the **Action** pane.
-
-4. Choose **Application with source files** to copy the MSI files into the Deployment Share.
-
-5. Select the folder you created in step 1 for the desired protocol.
-
-6. Name the folder in the deployment share where the installation files will be stored.
-
-7. Specify the command line to deploy the application:
-
- - For PEAP use **EAP-PEAP.msi /qn /norestart**.
-
- - For LEAP use **EAP-LEAP.msi /qn /norestart**.
-
- - For EAP-FAST use **EAP-FAST.msi /qn /norestart**.
-
-8. Use the default options to complete the New Application Wizard.
-
-9. Repeat steps 3 through 8 for each desired protocol.
-
-After you’ve performed these steps to import the three MSI packages as applications into MDT, they will be available for selection in the Applications page of the Windows Deployment Wizard. Although in some simple deployment scenarios it might be sufficient to have technicians select each package at the time of deployment, it is not recommended. This practice introduces the possibility that a technician could attempt to apply these packages to computers other than Surface devices, or that a Surface device could be deployed without EAP support due to human error.
-
-To hide these applications from the Install Applications page, select the **Hide this application in the Deployment Wizard** checkbox in the properties of each application. After the applications are hidden, they will not be displayed as optional applications during deployment. To deploy them in your Surface deployment task sequence, they must be explicitly defined for installation through a separate step in the task sequence.
-
-To specify the protocol(s) explicitly, follow these steps:
-
-1. Open your Surface deployment task sequence properties from the MDT Deployment Workbench.
-
-2. On the **Task Sequence** tab, select the **Install Applications** step under **State Restore**. This is typically found between the pre-application and post-application Windows Update steps.
-
-3. Use the **Add** button to create a new **Install Application** step from the **General** category.
-
-4. Select **Install a single application** in the step **Properties** tab.
-
-5. Select the desired EAP protocol from the list.
-
-6. Repeat steps 2 through 5 for each desired protocol.
-
-## Deploy PEAP, EAP-FAST, or Cisco LEAP with Configuration Manager
-
-
-For organizations that manage Surface devices with Configuration Manager, it is even easier to deploy PEAP, EAP-FAST, or Cisco LEAP support to Surface devices. Simply import each MSI file as an application from the Software Library and configure a deployment to your Surface device collection.
-
-For more information on how to deploy applications with Configuration Manager see [How to Create Applications in Configuration Manager](https://technet.microsoft.com/library/gg682159.aspx) and [How to Deploy Applications in Configuration Manager](https://technet.microsoft.com/library/gg682082.aspx).
-
-
-
-
-
-
-
-
-
diff --git a/devices/surface/enable-surface-keyboard-for-windows-pe-deployment.md b/devices/surface/enable-surface-keyboard-for-windows-pe-deployment.md
deleted file mode 100644
index 18011a1ca5..0000000000
--- a/devices/surface/enable-surface-keyboard-for-windows-pe-deployment.md
+++ /dev/null
@@ -1,174 +0,0 @@
----
-title: How to enable the Surface Laptop keyboard during MDT deployment
-description: When you use MDT to deploy Windows 10 to Surface laptops, you need to import keyboard drivers to use in the Windows PE environment.
-keywords: windows 10 surface, automate, customize, mdt
-ms.prod: w10
-ms.mktglfcycl: deploy
-ms.pagetype: surface
-ms.sitesec: library
-author: Teresa-Motiv
-ms.author: v-tea
-ms.topic: article
-ms.reviewer: scottmca
-ms.localizationpriority: medium
-ms.audience: itpro
-manager: jarrettr
-appliesto:
-- Surface Laptop (1st Gen)
-- Surface Laptop 2
-- Surface Laptop 3
----
-
-# How to enable the Surface Laptop keyboard during MDT deployment
-
-This article addresses a deployment approach that uses Microsoft Deployment Toolkit (MDT). You can also apply this information to other deployment methodologies. On most types of Surface devices, the keyboard should work during Lite Touch Installation (LTI). However, Surface Laptop requires some additional drivers to enable the keyboard. For Surface Laptop (1st Gen) and Surface Laptop 2 devices, you must prepare the folder structure and selection profiles that allow you to specify keyboard drivers for use during the Windows Preinstallation Environment (Windows PE) phase of LTI. For more information about this folder structure, see [Deploy a Windows 10 image using MDT: Step 5: Prepare the drivers repository](https://docs.microsoft.com/windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt?redirectedfrom=MSDN#step-5-prepare-the-drivers-repository).
-
-> [!NOTE]
-> It is currently not supported to add Surface Laptop 2 and Surface Laptop 3 keyboard drivers in the same Windows PE boot instance due to a driver conflict; use separate instances instead.
-
-> [!IMPORTANT]
-> If you are deploying a Windows 10 image to a Surface Laptop that has Windows 10 in S mode preinstalled, see KB [4032347, Problems when deploying Windows to Surface devices with preinstalled Windows 10 in S mode](https://support.microsoft.com/help/4032347/surface-preinstall-windows10-s-mode-issues).
-
-To add the keyboard drivers to the selection profile, follow these steps:
-
-1. Download the latest Surface Laptop MSI file from the appropriate locations:
- - [Surface Laptop (1st Gen) Drivers and Firmware](https://www.microsoft.com/download/details.aspx?id=55489)
- - [Surface Laptop 2 Drivers and Firmware](https://www.microsoft.com/download/details.aspx?id=57515)
- - [Surface Laptop 3 with Intel Processor Drivers and Firmware](https://www.microsoft.com/download/details.aspx?id=100429)
-
-2. Extract the contents of the Surface Laptop MSI file to a folder that you can easily locate (for example, c:\surface_laptop_drivers). To extract the contents, open an elevated Command Prompt window and run the command from the following example:
-
- ```cmd
- Msiexec.exe /a SurfaceLaptop_Win10_15063_1703008_1.msi targetdir=c:\surface_laptop_drivers /qn
- ```
-
-3. Open the Deployment Workbench and expand the **Deployment Shares** node and your deployment share, then navigate to the **WindowsPEX64** folder.
-
- 
-
-4. Right-click the **WindowsPEX64** folder and select **Import Drivers**.
-5. Follow the instructions in the Import Driver Wizard to import the driver folders into the WindowsPEX64 folder.
-
-> [!NOTE]
-> Check the downloaded MSI package to determine the format and directory structure. The directory structure will start with either SurfacePlatformInstaller (older MSI files) or SurfaceUpdate (Newer MSI files) depending on when the MSI was released.
-
-To support Surface Laptop (1st Gen), import the following folders:
-
- - SurfacePlatformInstaller\Drivers\System\GPIO
- - SurfacePlatformInstaller\Drivers\System\SurfaceHidMiniDriver
- - SurfacePlatformInstaller\Drivers\System\SurfaceSerialHubDriver
- - SurfacePlatformInstaller\Drivers\System\PreciseTouch
-
-Or for newer MSI files beginning with "SurfaceUpdate", use:
-
-- SurfaceUpdate\SerialIOGPIO
-- SurfaceUpdate\SurfaceHidMiniDriver
-- SurfaceUpdate\SurfaceSerialHubDriver
-- SurfaceUpdate\Itouch
-
-To support Surface Laptop 2, import the following folders:
-
- - SurfacePlatformInstaller\Drivers\System\GPIO
- - SurfacePlatformInstaller\Drivers\System\SurfaceHIDMiniDriver
- - SurfacePlatformInstaller\Drivers\System\SurfaceSerialHubDriver
- - SurfacePlatformInstaller\Drivers\System\I2C
- - SurfacePlatformInstaller\Drivers\System\SPI
- - SurfacePlatformInstaller\Drivers\System\UART
- - SurfacePlatformInstaller\Drivers\System\PreciseTouch
-
-Or for newer MSI files beginning with "SurfaceUpdate", use:
-
-- SurfaceUpdate\SerialIOGPIO
-- SurfaceUpdate\IclSerialIOI2C
-- SurfaceUpdate\IclSerialIOSPI
-- SurfaceUpdate\IclSerialIOUART
-- SurfaceUpdate\SurfaceHidMini
-- SurfaceUpdate\SurfaceSerialHub
-- SurfaceUpdate\Itouch
-
-
-To support Surface Laptop 3 with Intel Processor, import the following folders:
-
-- SurfaceUpdate\IclSerialIOGPIO
-- SurfaceUpdate\IclSerialIOI2C
-- SurfaceUpdate\IclSerialIOSPI
-- SurfaceUpdate\IclSerialIOUART
-- SurfaceUpdate\SurfaceHidMini
-- SurfaceUpdate\SurfaceSerialHub
-- SurfaceUpdate\SurfaceHotPlug
-- SurfaceUpdate\Itouch
- > [!NOTE]
- > Check the downloaded MSI package to determine the format and directory structure. The directory structure will start with either SurfacePlatformInstaller (older MSI files) or SurfaceUpdate (Newer MSI files) depending on when the MSI was released.
-
- To support Surface Laptop (1st Gen), import the following folders:
-
- - SurfacePlatformInstaller\Drivers\System\GPIO
- - SurfacePlatformInstaller\Drivers\System\SurfaceHidMiniDriver
- - SurfacePlatformInstaller\Drivers\System\SurfaceSerialHubDriver
- - SurfacePlatformInstaller\Drivers\System\PreciseTouch
-
- Or for newer MSI files beginning with "SurfaceUpdate", use:
-
- - SurfaceUpdate\SerialIOGPIO
- - SurfaceUpdate\SurfaceHidMiniDriver
- - SurfaceUpdate\SurfaceSerialHubDriver
- - SurfaceUpdate\Itouch
-
- To support Surface Laptop 2, import the following folders:
-
- - SurfacePlatformInstaller\Drivers\System\GPIO
- - SurfacePlatformInstaller\Drivers\System\SurfaceHIDMiniDriver
- - SurfacePlatformInstaller\Drivers\System\SurfaceSerialHubDriver
- - SurfacePlatformInstaller\Drivers\System\I2C
- - SurfacePlatformInstaller\Drivers\System\SPI
- - SurfacePlatformInstaller\Drivers\System\UART
- - SurfacePlatformInstaller\Drivers\System\PreciseTouch
-
- Or for newer MSI files beginning with "SurfaceUpdate", use:
-
- - SurfaceUpdate\SerialIOGPIO
- - SurfaceUpdate\IclSerialIOI2C
- - SurfaceUpdate\IclSerialIOSPI
- - SurfaceUpdate\IclSerialIOUART
- - SurfaceUpdate\SurfaceHidMini
- - SurfaceUpdate\SurfaceSerialHub
- - SurfaceUpdate\Itouch
-
- To support Surface Laptop 3 with Intel Processor, import the following folders:
-
- - SurfaceUpdate\IclSerialIOGPIO
- - SurfaceUpdate\IclSerialIOI2C
- - SurfaceUpdate\IclSerialIOSPI
- - SurfaceUpdate\IclSerialIOUART
- - SurfaceUpdate\SurfaceHidMini
- - SurfaceUpdate\SurfaceSerialHub
- - SurfaceUpdate\SurfaceHotPlug
- - SurfaceUpdate\Itouch
-
- > [!NOTE]
- > For Surface Laptop 3 with Intel processor, the model is Surface Laptop 3. The remaining Surface Laptop drivers are located in the \MDT Deployment Share\Out-of-Box Drivers\Windows10\X64\Surface Laptop 3 folder.
-
-6. Verify that the WindowsPEX64 folder now contains the imported drivers. The folder should resemble the following:
-
- 
-
-7. Configure a selection profile that uses the WindowsPEX64 folder. The selection profile should resemble the following:
-
- 
-
-8. Configure the Windows PE properties of the MDT deployment share to use the new selection profile, as follows:
-
- - For **Platform**, select **x64**.
- - For **Selection profile**, select the new profile.
- - Select **Include all drivers from the selection profile**.
-
- 
-
-9. Verify that you have configured the remaining Surface Laptop drivers by using either a selection profile or a **DriverGroup001** variable.
- - For Surface Laptop (1st Gen), the model is **Surface Laptop**. The remaining Surface Laptop drivers should reside in the \MDT Deployment Share\Out-of-Box Drivers\Windows10\X64\Surface Laptop folder as shown in the figure that follows this list.
- - For Surface Laptop 2, the model is **Surface Laptop 2**. The remaining Surface Laptop drivers should reside in the \MDT Deployment Share\Out-of-Box Drivers\Windows10\X64\Surface Laptop 2 folder.
- - For Surface Laptop 3 with Intel processor, the model is Surface Laptop 3. The remaining Surface Laptop drivers are located in the \MDT Deployment Share\Out-of-Box Drivers\Windows10\X64\Surface Laptop 3 folder.
-
- 
-
-After configuring the MDT Deployment Share to use the new selection profile and related settings, continue the deployment process as described in [Deploy a Windows 10 image using MDT: Step 6: Create the deployment task sequence](https://docs.microsoft.com/windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt#step-6-create-the-deployment-task-sequence).
diff --git a/devices/surface/enroll-and-configure-surface-devices-with-semm.md b/devices/surface/enroll-and-configure-surface-devices-with-semm.md
deleted file mode 100644
index 0147596761..0000000000
--- a/devices/surface/enroll-and-configure-surface-devices-with-semm.md
+++ /dev/null
@@ -1,149 +0,0 @@
----
-title: Enroll and configure Surface devices with SEMM (Surface)
-description: Learn how to create a Surface UEFI configuration package to control the settings of Surface UEFI, as well as enroll a Surface device in SEMM.
-keywords: surface enterprise management
-ms.prod: w10
-ms.mktglfcycl: manage
-ms.pagetype: surface, devices, security
-ms.sitesec: library
-author: coveminer
-ms.author: v-jokai
-ms.topic: article
-ms.localizationpriority: medium
-ms.audience: itpro
-ms.reviewer:
-manager: laurawi
----
-
-# Enroll and configure Surface devices with SEMM
-
-With Microsoft Surface Enterprise Management Mode (SEMM), you can securely configure the settings of Surface UEFI on a Surface device and manage those settings on Surface devices in your organization. When a Surface device is managed by SEMM, that device is considered to be *enrolled* (sometimes referred to as activated). This article shows you how to create a Surface UEFI configuration package that will not only control the settings of Surface UEFI, but will also enroll a Surface device in SEMM.
-
-For a more high-level overview of SEMM, see [Microsoft Surface Enterprise Management Mode](https://technet.microsoft.com/itpro/surface/surface-enterprise-management-mode).
-
-A streamlined method of managing firmware from the cloud on Surface Pro 7,Surface Pro X and Surface Laptop 3 is now available via public preview. For more information,refer to [Intune management of Surface UEFI settings](surface-manage-dfci-guide.md).
-
-> [!NOTE]
-> SEMM is not supported on Surface Pro X. For more information, refer to [Deploying, managing, and servicing Surface Pro X](surface-pro-arm-app-management.md).
-
-#### Download and install Microsoft Surface UEFI Configurator
-The tool used to create SEMM packages is Microsoft Surface UEFI Configurator. You can download Microsoft Surface UEFI Configurator from the [Surface Tools for IT](https://www.microsoft.com/download/details.aspx?id=46703) page in the Microsoft Download Center.
-Run the Microsoft Surface UEFI Configurator Windows Installer (.msi) file to start the installation of the tool. When the installer completes, find Microsoft Surface UEFI Configurator in the All Apps section of your Start menu.
-
->[!NOTE]
->Microsoft Surface UEFI Configurator is supported only on Windows 10.
-
-## Create a Surface UEFI configuration package
-
-The Surface UEFI configuration package performs both the role of applying a new configuration of Surface UEFI settings to a Surface device managed with SEMM and the role of enrolling Surface devices in SEMM. The creation of a configuration package requires you to have a signing certificate to be used with SEMM to secure the configuration of UEFI settings on each Surface device. For more information about the requirements for the SEMM certificate, see [Microsoft Surface Enterprise Management Mode](https://technet.microsoft.com/itpro/surface/surface-enterprise-management-mode).
-
-To create a Surface UEFI configuration package, follow these steps:
-
-1. Open Microsoft Surface UEFI Configurator from the Start menu.
-2. Click **Start**.
-3. Click **Configuration Package**, as shown in Figure 1.
-
- 
-
- *Figure 1. Select Configuration Package to create a package for SEMM enrollment and configuration*
-
-4. Click **Certificate Protection** to add your exported certificate file with private key (.pfx), as shown in Figure 2. Browse to the location of your certificate file, select the file, and then click **OK**.
-
- 
-
- *Figure 2. Add the SEMM certificate and Surface UEFI password to a Surface UEFI configuration package*
-
-5. When you are prompted to confirm the certificate password, enter and confirm the password for your certificate file, and then click **OK**.
-6. Click **Password Protection** to add a password to Surface UEFI. This password will be required whenever you boot to UEFI. If this password is not entered, only the **PC information**, **About**, **Enterprise management**, and **Exit** pages will be displayed. This step is optional.
-7. When you are prompted, enter and confirm your chosen password for Surface UEFI, and then click **OK**. If you want to clear an existing Surface UEFI password, leave the password field blank.
-8. If you do not want the Surface UEFI package to apply to a particular device, on the **Choose which Surface type you want to target** page, click the slider beneath the corresponding Surface Book or Surface Pro 4 image so that it is in the **Off** position. (As shown in Figure 3.)
-
- 
-
- *Figure 3. Choose the devices for package compatibility*
-
-9. Click **Next**.
-10. If you want to deactivate a component on managed Surface devices, on the **Choose which components you want to activate or deactivate** page, click the slider next to any device or group of devices you want to deactivate so that the slider is in the **Off** position. (Shown in Figure 4.) The default configuration for each device is **On**. Click the **Reset** button if you want to return all sliders to the default position.
-
- 
-
- *Figure 4. Disable or enable individual Surface components*
-
-11. Click **Next**.
-12. To enable or disable advanced options in Surface UEFI or the display of Surface UEFI pages, on the **Choose the advanced settings for your devices** page, click the slider beside the desired setting to configure that option to **On** or **Off** (shown in Figure 5). In the **UEFI Front Page** section, you can use the sliders for **Security**, **Devices**, and **Boot** to control what pages are available to users who boot into Surface UEFI. (For more information about Surface UEFI settings, see [Manage Surface UEFI settings](https://technet.microsoft.com/itpro/surface/manage-surface-uefi-settings).) Click **Build** when you have finished selecting options to generate and save the package.
-
- 
-
- *Figure 5. Control advanced Surface UEFI settings and Surface UEFI pages with SEMM*
-
-13. In the **Save As** dialog box, specify a name for the Surface UEFI configuration package, browse to the location where you would like to save the file, and then click **Save**.
-14. When the package is created and saved, the **Successful** page is displayed.
-
->[!NOTE]
->Record the certificate thumbprint characters that are displayed on this page, as shown in Figure 6. You will need these characters to confirm enrollment of new Surface devices in SEMM. Click **End** to complete package creation and close Microsoft Surface UEFI Configurator.
-
-
-
-*Figure 6. The last two characters of the certificate thumbprint are displayed on the Successful page*
-
-Now that you have created your Surface UEFI configuration package, you can enroll or configure Surface devices.
-
->[!NOTE]
->When a Surface UEFI configuration package is created, a log file is created on the desktop with details of the configuration package settings and options.
-
-## Enroll a Surface device in SEMM
-When the Surface UEFI configuration package is executed, the SEMM certificate and Surface UEFI configuration files are staged in the firmware storage of the Surface device. When the Surface device reboots, Surface UEFI processes these files and begins the process of applying the Surface UEFI configuration or enrolling the Surface device in SEMM, as shown in Figure 7.
-
-
-
-*Figure 7. The SEMM process for configuration of Surface UEFI or enrollment of a Surface device*
-
-Before you begin the process to enroll a Surface device in SEMM, ensure that you have the last two characters of the certificate thumbprint on hand. You will need these characters to confirm the device’s enrollment (see Figure 6).
-
-To enroll a Surface device in SEMM with a Surface UEFI configuration package, follow these steps:
-
-1. Run the Surface UEFI configuration package .msi file on the Surface device you want to enroll in SEMM. This will provision the Surface UEFI configuration file in the device’s firmware.
-2. Select the **I accept the terms in the License Agreement** check box to accept the End User License Agreement (EULA), and then click **Install** to begin the installation process.
-3. Click **Finish** to complete the Surface UEFI configuration package installation and restart the Surface device when you are prompted to do so.
-4. Surface UEFI will load the configuration file and determine that SEMM is not enabled on the device. Surface UEFI will then begin the SEMM enrollment process, as follows:
- * Surface UEFI will verify that the SEMM configuration file contains a SEMM certificate.
- * Surface UEFI will prompt you to enter to enter the last two characters of the certificate thumbprint to confirm enrollment of the Surface device in SEMM, as shown in Figure 8.
-
- 
-
- *Figure 8. Enrollment in SEMM requires the last two characters of the certificate thumbprint*
-
- * Surface UEFI will store the SEMM certificate in firmware and apply the configuration settings that are specified in the Surface UEFI configuration file.
-
-5. The Surface device is now enrolled in SEMM and will boot to Windows.
-
-You can verify that a Surface device has been successfully enrolled in SEMM by looking for **Microsoft Surface Configuration Package** in **Programs and Features** (as shown in Figure 9), or in the events stored in the **Microsoft Surface UEFI Configurator** log, found under **Applications and Services Logs** in Event Viewer (as shown in Figure 10).
-
-
-
-*Figure 9. Verify the enrollment of a Surface device in SEMM in Programs and Features*
-
-
-
-*Figure 10. Verify the enrollment of a Surface device in SEMM in Event Viewer*
-
-You can also verify that the device is enrolled in SEMM in Surface UEFI – while the device is enrolled, Surface UEFI will contain the **Enterprise management** page (as shown in Figure 11).
-
-
-
-*Figure 11. The Surface UEFI Enterprise management page*
-
-
-## Configure Surface UEFI settings with SEMM
-
-After a device is enrolled in SEMM, you can run Surface UEFI configuration packages signed with the same SEMM certificate to apply new Surface UEFI settings. These settings are applied automatically the next time the device boots, without any interaction from the user. You can use application deployment solutions like Microsoft Endpoint Configuration Manager to deploy Surface UEFI configuration packages to Surface devices to change or manage the settings in Surface UEFI.
-
-For more information about how to deploy Windows Installer (.msi) files with Configuration Manager, see [Deploy and manage applications with Microsoft Endpoint Configuration Manager](https://technet.microsoft.com/library/mt627959).
-
-If you have secured Surface UEFI with a password, users without the password who attempt to boot to Surface UEFI will only have the **PC information**, **About**, **Enterprise management**, and **Exit** pages displayed to them.
-
-If you have not secured Surface UEFI with a password or a user enters the password correctly, settings that are configured with SEMM will be dimmed (unavailable) and the text Some settings are managed by your organization will be displayed at the top of the page, as shown in Figure 12.
-
-
-
-*Figure 12. Settings managed by SEMM will be disabled in Surface UEFI*
diff --git a/devices/surface/ethernet-adapters-and-surface-device-deployment.md b/devices/surface/ethernet-adapters-and-surface-device-deployment.md
deleted file mode 100644
index c35dbe0630..0000000000
--- a/devices/surface/ethernet-adapters-and-surface-device-deployment.md
+++ /dev/null
@@ -1,97 +0,0 @@
----
-title: Ethernet adapters and Surface deployment (Surface)
-description: This article provides guidance and answers to help you perform a network deployment to Surface devices.
-ms.assetid: 5273C59E-6039-4E50-96B3-426BB38A64C0
-ms.reviewer:
-manager: laurawi
-keywords: ethernet, deploy, removable, network, connectivity, boot, firmware, device, adapter, PXE boot, USB
-ms.localizationpriority: medium
-ms.prod: w10
-ms.mktglfcycl: deploy
-ms.pagetype: surface, devices
-ms.sitesec: library
-author: coveminer
-ms.author: v-jokai
-ms.topic: article
-ms.audience: itpro
----
-
-# Ethernet adapters and Surface deployment
-
-
-This article provides guidance and answers to help you perform a network deployment to Surface devices including Surface Pro 3 and later.
-
-Network deployment to Surface devices can pose some unique challenges for system administrators. Due to the lack of a native wired Ethernet adapter, administrators must provide connectivity through a removable Ethernet adapter.
-
-## Select an Ethernet adapter for Surface devices
-
-
-Before you can address the concerns of how you will boot to your deployment environment or how devices will be recognized by your deployment solution, you have to use a wired network adapter.
-
-The primary concern when selecting an Ethernet adapter is how that adapter will boot your Surface device from the network. If you are pre-staging clients with Windows Deployment Services (WDS) or if you are using Microsoft Endpoint Configuration Manager, you may also want to consider whether the removable Ethernet adapters will be dedicated to a specific Surface device or shared among multiple devices. See the [Manage MAC addresses with removable Ethernet adapters](#manage-mac-addresses) section of this article for more information on potential conflicts with shared adapters.
-
-Booting from the network (PXE boot) is only supported when you use an Ethernet adapter or docking station from Microsoft. To boot from the network, the chipset in the Ethernet adapter or dock must be detected and configured as a boot device in the firmware of the Surface device. Microsoft Ethernet adapters, such as the Surface Ethernet Adapter and the [Surface Dock](https://www.microsoft.com/surface/accessories/surface-dock) use a chipset that is compatible with the Surface firmware.
-
-The following Ethernet devices are supported for network boot with Surface devices:
-
-- Surface USB-C to Ethernet and USB 3.0 Adapter
-
-- Surface USB 3.0 to Gigabit Ethernet Adapter
-
-- Surface Dock
-
-- Surface 3 Docking Station
-
-- Surface Pro 3 Docking Station
-
-- Docking Station for Surface Pro and Surface Pro 2
-
-Third-party Ethernet adapters are also supported for network deployment, although they do not support PXE boot. To use a third-party Ethernet adapter, you must load the drivers into the deployment boot image and you must launch that boot image from a separate storage device, such as a USB stick.
-
-## Boot Surface devices from the network
-
-To boot from the network or a connected USB stick, you must instruct the Surface device to boot from an alternate boot device. You can alter the boot order in the system firmware to prioritize USB boot devices, or you can instruct it to boot from an alternate boot device during the boot up process.
-
-To boot a Surface device from an alternative boot device, follow these steps:
-
-1. Ensure the Surface device is powered off.
-2. Press and hold the **Volume Down** button.
-3. Press and release the **Power** button.
-4. After the system begins to boot from the USB stick or Ethernet adapter, release the **Volume Down** button.
-
->[!NOTE]
->In addition to an Ethernet adapter, a keyboard must also be connected to the Surface device to enter the preinstallation environment and navigate the deployment wizard.
-
-
-For Windows 10, version 1511 and later – including the Windows Assessment and Deployment Kit (Windows ADK) for Windows 10, version 1511 – the drivers for Microsoft Surface Ethernet Adapters are present by default. If you are using a deployment solution that uses Windows Preinstallation Environment (WinPE), like the Microsoft Deployment Toolkit, and booting from the network with PXE, ensure that your deployment solution is using the latest version of the Windows ADK.
-
-## Manage MAC addresses with removable Ethernet adapters
-
-
-Another consideration for administrators performing Windows deployment over the network is how you will identify computers when you use the same Ethernet adapter to deploy to more than one computer. A common identifier used by deployment technologies is the Media Access Control (MAC) address that is associated with each Ethernet adapter. However, when you use the same Ethernet adapter to deploy to multiple computers, you cannot use a deployment technology that inspects MAC addresses because there is no way to differentiate the MAC address of the removable adapter when used on the different computers.
-
-The simplest solution to avoid MAC address conflicts is to provide a dedicated removable Ethernet adapter for each Surface device. This can make sense in many scenarios where the Ethernet adapter or the additional functionality of the docking station will be used regularly. However, not all scenarios call for the additional connectivity of a docking station or support for wired networks.
-
-Another potential solution to avoid conflict when adapters are shared is to use the [Microsoft Deployment Toolkit (MDT)](https://technet.microsoft.com/windows/dn475741) to perform deployment to Surface devices. MDT does not use the MAC address to identify individual computers and thus is not subject to this limitation. However, MDT does use Windows Deployment Services to provide PXE boot functionality, and is subject to the limitations regarding pre-staged clients which is covered later in this section.
-
-When you use a shared adapter for deployment, the solution for affected deployment technologies is to use another means to identify unique systems. For Configuration Manager and WDS, both of which can be affected by this issue, the solution is to use the System Universal Unique Identifier (System UUID) that is embedded in the computer firmware by the computer manufacturer. For Surface devices, you can see this entry in the computer firmware under **Device Information**.
-
-To access the firmware of a Surface device, follow these steps:
-
-1. Ensure the Surface device is powered off.
-2. Press and hold the **Volume Up** button.
-3. Press and release the **Power** button.
-4. After the device begins to boot, release the **Volume Up** button.
-
-When deploying with WDS, the MAC address is only used to identify a computer when the deployment server is configured to respond only to known, pre-staged clients. When pre-staging a client, an administrator creates a computer account in Active Directory and defines that computer by the MAC address or the System UUID. To avoid the identity conflicts caused by shared Ethernet adapters, you should use [System UUID to define pre-staged clients](https://technet.microsoft.com/library/cc742034). Alternatively, you can configure WDS to respond to unknown clients that do not require definition by either MAC address or System UUID by selecting the **Respond to all client computers (known and unknown)** option on the [**PXE Response** tab](https://technet.microsoft.com/library/cc732360) in **Windows Deployment Server Properties**.
-
-The potential for conflicts with shared Ethernet adapters is much higher with Configuration Manager. Where WDS only uses MAC addresses to define individual systems when configured to do so, Configuration Manager uses the MAC address to define individual systems whenever performing a deployment to new or unknown computers. This can result in improperly configured devices or even the inability to deploy more than one system with a shared Ethernet adapter. There are several potential solutions for this situation that are described in detail in the [How to Use The Same External Ethernet Adapter For Multiple SCCM OSD](https://blogs.technet.microsoft.com/askpfeplat/2014/07/27/how-to-use-the-same-external-ethernet-adapter-for-multiple-sccm-osd/) blog post on the Ask Premier Field Engineering (PFE) Platforms TechNet blog.
-
-
-
-
-
-
-
-
-
diff --git a/devices/surface/get-started.yml b/devices/surface/get-started.yml
deleted file mode 100644
index edb22aac8c..0000000000
--- a/devices/surface/get-started.yml
+++ /dev/null
@@ -1,122 +0,0 @@
-### YamlMime:Landing
-
-title: Surface devices documentation # < 60 chars
-summary: Harness the power of Surface, Windows, and Office connected together through the cloud. # < 160 chars
-
-metadata:
- title: Surface devices documentation # Required; page title displayed in search results. Include the brand. < 60 chars.
- description: Get started with Microsoft Surface devices # Required; article description that is displayed in search results. < 160 chars.
- ms.service: product-insights #Required; service per approved list. service slug assigned to your service by ACOM.
- ms.topic: landing-page # Required
- manager: laurawi
- author: greg-lindsay #Required; your GitHub user alias, with correct capitalization.
- ms.author: greglin #Required; microsoft alias of author; optional team alias.
- audience: itpro
- ms.localizationpriority: High
-
-# linkListType: architecture | concept | deploy | download | get-started | how-to-guide | learn | overview | quickstart | reference | sample | tutorial | video | whats-new
-
-landingContent:
-# Cards and links should be based on top customer tasks or top subjects
-# Start card title with a verb
- # Card (optional)
- - title: Surface devices
- linkLists:
- - linkListType: overview
- links:
- - text: Surface Pro 7 for Business
- url: https://www.microsoft.com/surface/business/surface-pro-7
- - text: Surface Pro X for Business
- url: https://www.microsoft.com/surface/business/surface-pro-x
- - text: Surface Laptop 3 for Business
- url: https://www.microsoft.com/surface/business/surface-laptop-3
- - text: Surface Book 2 for Business
- url: https://www.microsoft.com/surface/business/surface-book-2
- - text: Surface Studio 2 for Business
- url: https://www.microsoft.com/surface/business/surface-studio-2
- - text: Surface Go
- url: https://www.microsoft.com/surface/business/surface-go
- - linkListType: video
- links:
- - text: Microsoft Mechanics Surface videos
- url: https://www.youtube.com/watch?v=Uk2kJ5FUZxY&list=PLXtHYVsvn_b__1Baibdu4elN4SoF3JTBZ
-
- # Card (optional)
- - title: Get started
- linkLists:
- - linkListType: get-started
- links:
- - text: Surface and Endpoint Configuration Manager considerations
- url: considerations-for-surface-and-system-center-configuration-manager.md
- - text: Wake On LAN for Surface devices
- url: wake-on-lan-for-surface-devices.md
-
- # Card
- - title: Deploy Surface devices
- linkLists:
- - linkListType: deploy
- links:
- - text: Manage and deploy Surface driver and firmware updates
- url: manage-surface-driver-and-firmware-updates.md
- - text: Autopilot and Surface devices
- url: windows-autopilot-and-surface-devices.md
- - text: Deploying, managing, and servicing Surface Pro X
- url: surface-pro-arm-app-management.md
-
- # Card
- - title: Manage Surface devices
- linkLists:
- - linkListType: how-to-guide
- links:
- - text: Optimize Wi-Fi connectivity for Surface devices
- url: surface-wireless-connect.md
- - text: Best practice power settings for Surface devices
- url: maintain-optimal-power-settings-on-Surface-devices.md
- - text: Manage battery limit with UEFI
- url: battery-limit.md
-
- # Card
- - title: Secure Surface devices
- linkLists:
- - linkListType: how-to-guide
- links:
- - text: Intune management of Surface UEFI settings
- url: surface-manage-dfci-guide.md
- - text: Surface Enterprise Management Mode (SEMM)
- url: surface-enterprise-management-mode.md
- - text: Surface Data Eraser tool
- url: microsoft-surface-data-eraser.md
-
- # Card
- - title: Discover Surface tools
- linkLists:
- - linkListType: how-to-guide
- links:
- - text: Surface Dock Firmware Update
- url: surface-dock-firmware-update.md
- - text: Surface Diagnostic Toolkit for Business
- url: surface-diagnostic-toolkit-for-business-intro.md
- - text: SEMM and UEFI
- url: surface-enterprise-management-mode.md
- - text: Surface Brightness Control
- url: microsoft-surface-brightness-control.md
- - text: Battery Limit setting
- url: battery-limit.md
-
- # Card
- - title: Support and community
- linkLists:
- - linkListType: learn
- links:
- - text: Top support solutions
- url: support-solutions-surface.md
- - text: Maximize your Surface battery life
- url: https://support.microsoft.com/help/4483194/maximize-surface-battery-life
- - text: Troubleshoot Surface Dock and docking stations
- url: https://support.microsoft.com/help/4023468/surface-troubleshoot-surface-dock-and-docking-stations
- - linkListType: reference
- links:
- - text: Surface IT Pro blog
- url: https://techcommunity.microsoft.com/t5/Surface-IT-Pro-Blog/bg-p/SurfaceITPro
- - text: Surface Devices Tech Community
- url: https://techcommunity.microsoft.com/t5/Surface-Devices/ct-p/SurfaceDevices
diff --git a/devices/surface/images/Surface-Devices-400x140.svg b/devices/surface/images/Surface-Devices-400x140.svg
deleted file mode 100644
index 4414de0f16..0000000000
--- a/devices/surface/images/Surface-Devices-400x140.svg
+++ /dev/null
@@ -1,25 +0,0 @@
-
-
-
diff --git a/devices/surface/images/Surface-Hub-400x140.svg b/devices/surface/images/Surface-Hub-400x140.svg
deleted file mode 100644
index f5a5c12a56..0000000000
--- a/devices/surface/images/Surface-Hub-400x140.svg
+++ /dev/null
@@ -1,51 +0,0 @@
-
-
-
diff --git a/devices/surface/images/Surface-Workplace-400x140.svg b/devices/surface/images/Surface-Workplace-400x140.svg
deleted file mode 100644
index 9bb3779192..0000000000
--- a/devices/surface/images/Surface-Workplace-400x140.svg
+++ /dev/null
@@ -1,33 +0,0 @@
-
-
-
diff --git a/devices/surface/images/assettag-fig1.png b/devices/surface/images/assettag-fig1.png
deleted file mode 100644
index 5ccb36c85f..0000000000
Binary files a/devices/surface/images/assettag-fig1.png and /dev/null differ
diff --git a/devices/surface/images/config-mgr-semm-fig1.png b/devices/surface/images/config-mgr-semm-fig1.png
deleted file mode 100644
index 7ff888c2e2..0000000000
Binary files a/devices/surface/images/config-mgr-semm-fig1.png and /dev/null differ
diff --git a/devices/surface/images/config-mgr-semm-fig2.png b/devices/surface/images/config-mgr-semm-fig2.png
deleted file mode 100644
index 33836c09eb..0000000000
Binary files a/devices/surface/images/config-mgr-semm-fig2.png and /dev/null differ
diff --git a/devices/surface/images/config-mgr-semm-fig3.png b/devices/surface/images/config-mgr-semm-fig3.png
deleted file mode 100644
index e699359552..0000000000
Binary files a/devices/surface/images/config-mgr-semm-fig3.png and /dev/null differ
diff --git a/devices/surface/images/data-eraser-3.png b/devices/surface/images/data-eraser-3.png
deleted file mode 100644
index eed3836aa7..0000000000
Binary files a/devices/surface/images/data-eraser-3.png and /dev/null differ
diff --git a/devices/surface/images/dataeraser-arch.png b/devices/surface/images/dataeraser-arch.png
deleted file mode 100644
index 5010120cf1..0000000000
Binary files a/devices/surface/images/dataeraser-arch.png and /dev/null differ
diff --git a/devices/surface/images/dataeraser-complete-process.png b/devices/surface/images/dataeraser-complete-process.png
deleted file mode 100644
index c7d0ee1d09..0000000000
Binary files a/devices/surface/images/dataeraser-complete-process.png and /dev/null differ
diff --git a/devices/surface/images/dataeraser-start-tool.png b/devices/surface/images/dataeraser-start-tool.png
deleted file mode 100644
index a727d8a870..0000000000
Binary files a/devices/surface/images/dataeraser-start-tool.png and /dev/null differ
diff --git a/devices/surface/images/dataeraser-usb-selection.png b/devices/surface/images/dataeraser-usb-selection.png
deleted file mode 100644
index 6c5382c7b0..0000000000
Binary files a/devices/surface/images/dataeraser-usb-selection.png and /dev/null differ
diff --git a/devices/surface/images/deploysurfapp-fig2-selectingofflinelicense.png b/devices/surface/images/deploysurfapp-fig2-selectingofflinelicense.png
deleted file mode 100644
index eb7a2ef787..0000000000
Binary files a/devices/surface/images/deploysurfapp-fig2-selectingofflinelicense.png and /dev/null differ
diff --git a/devices/surface/images/deploysurfapp-fig3-acknowledge.png b/devices/surface/images/deploysurfapp-fig3-acknowledge.png
deleted file mode 100644
index dd59593baf..0000000000
Binary files a/devices/surface/images/deploysurfapp-fig3-acknowledge.png and /dev/null differ
diff --git a/devices/surface/images/deploysurfapp-fig4-downloadappxbundle.png b/devices/surface/images/deploysurfapp-fig4-downloadappxbundle.png
deleted file mode 100644
index 59b96e327b..0000000000
Binary files a/devices/surface/images/deploysurfapp-fig4-downloadappxbundle.png and /dev/null differ
diff --git a/devices/surface/images/deploysurfapp-fig5-requiredframework.png b/devices/surface/images/deploysurfapp-fig5-requiredframework.png
deleted file mode 100644
index 24d6e7edd8..0000000000
Binary files a/devices/surface/images/deploysurfapp-fig5-requiredframework.png and /dev/null differ
diff --git a/devices/surface/images/deploysurfapp-figure1-enablingapps.png b/devices/surface/images/deploysurfapp-figure1-enablingapps.png
deleted file mode 100644
index 78bfef9e8b..0000000000
Binary files a/devices/surface/images/deploysurfapp-figure1-enablingapps.png and /dev/null differ
diff --git a/devices/surface/images/df1.png b/devices/surface/images/df1.png
deleted file mode 100644
index 92aff587bc..0000000000
Binary files a/devices/surface/images/df1.png and /dev/null differ
diff --git a/devices/surface/images/df2a.png b/devices/surface/images/df2a.png
deleted file mode 100644
index 2a755ac374..0000000000
Binary files a/devices/surface/images/df2a.png and /dev/null differ
diff --git a/devices/surface/images/df3.png b/devices/surface/images/df3.png
deleted file mode 100644
index c5263ce83f..0000000000
Binary files a/devices/surface/images/df3.png and /dev/null differ
diff --git a/devices/surface/images/df3b.png b/devices/surface/images/df3b.png
deleted file mode 100644
index 60370c5541..0000000000
Binary files a/devices/surface/images/df3b.png and /dev/null differ
diff --git a/devices/surface/images/dfciconfig.png b/devices/surface/images/dfciconfig.png
deleted file mode 100644
index 2e8b0b4fee..0000000000
Binary files a/devices/surface/images/dfciconfig.png and /dev/null differ
diff --git a/devices/surface/images/discovertools.png b/devices/surface/images/discovertools.png
deleted file mode 100644
index 2568398824..0000000000
Binary files a/devices/surface/images/discovertools.png and /dev/null differ
diff --git a/devices/surface/images/enable-bl-sp3-2.png b/devices/surface/images/enable-bl-sp3-2.png
deleted file mode 100644
index f1940c403f..0000000000
Binary files a/devices/surface/images/enable-bl-sp3-2.png and /dev/null differ
diff --git a/devices/surface/images/enable-bl-sp3.png b/devices/surface/images/enable-bl-sp3.png
deleted file mode 100644
index 7fa99786f1..0000000000
Binary files a/devices/surface/images/enable-bl-sp3.png and /dev/null differ
diff --git a/devices/surface/images/enable-bl.png b/devices/surface/images/enable-bl.png
deleted file mode 100644
index a99cb994fb..0000000000
Binary files a/devices/surface/images/enable-bl.png and /dev/null differ
diff --git a/devices/surface/images/fig1-downloads-msi.png b/devices/surface/images/fig1-downloads-msi.png
deleted file mode 100644
index 4d8b1410ff..0000000000
Binary files a/devices/surface/images/fig1-downloads-msi.png and /dev/null differ
diff --git a/devices/surface/images/manage-surface-dock-fig1-updateprocess.png b/devices/surface/images/manage-surface-dock-fig1-updateprocess.png
deleted file mode 100644
index e779fa33ef..0000000000
Binary files a/devices/surface/images/manage-surface-dock-fig1-updateprocess.png and /dev/null differ
diff --git a/devices/surface/images/manage-surface-uefi-fig10.png b/devices/surface/images/manage-surface-uefi-fig10.png
deleted file mode 100644
index daccc0efbb..0000000000
Binary files a/devices/surface/images/manage-surface-uefi-fig10.png and /dev/null differ
diff --git a/devices/surface/images/manage-surface-uefi-fig11.png b/devices/surface/images/manage-surface-uefi-fig11.png
deleted file mode 100644
index 34d2dc5342..0000000000
Binary files a/devices/surface/images/manage-surface-uefi-fig11.png and /dev/null differ
diff --git a/devices/surface/images/manage-surface-uefi-fig12.png b/devices/surface/images/manage-surface-uefi-fig12.png
deleted file mode 100644
index b7a58d16c2..0000000000
Binary files a/devices/surface/images/manage-surface-uefi-fig12.png and /dev/null differ
diff --git a/devices/surface/images/manage-surface-uefi-fig13.png b/devices/surface/images/manage-surface-uefi-fig13.png
deleted file mode 100644
index ee4691bf9e..0000000000
Binary files a/devices/surface/images/manage-surface-uefi-fig13.png and /dev/null differ
diff --git a/devices/surface/images/manage-surface-uefi-fig14.png b/devices/surface/images/manage-surface-uefi-fig14.png
deleted file mode 100644
index 8224fb5bab..0000000000
Binary files a/devices/surface/images/manage-surface-uefi-fig14.png and /dev/null differ
diff --git a/devices/surface/images/manage-surface-uefi-fig15.png b/devices/surface/images/manage-surface-uefi-fig15.png
deleted file mode 100644
index 8973b83528..0000000000
Binary files a/devices/surface/images/manage-surface-uefi-fig15.png and /dev/null differ
diff --git a/devices/surface/images/manage-surface-uefi-fig16.png b/devices/surface/images/manage-surface-uefi-fig16.png
deleted file mode 100644
index cac0f7c1c1..0000000000
Binary files a/devices/surface/images/manage-surface-uefi-fig16.png and /dev/null differ
diff --git a/devices/surface/images/manage-surface-uefi-fig17.png b/devices/surface/images/manage-surface-uefi-fig17.png
deleted file mode 100644
index 8b66d3605f..0000000000
Binary files a/devices/surface/images/manage-surface-uefi-fig17.png and /dev/null differ
diff --git a/devices/surface/images/manage-surface-uefi-fig18.png b/devices/surface/images/manage-surface-uefi-fig18.png
deleted file mode 100644
index 8845608fbd..0000000000
Binary files a/devices/surface/images/manage-surface-uefi-fig18.png and /dev/null differ
diff --git a/devices/surface/images/manage-surface-uefi-fig19.png b/devices/surface/images/manage-surface-uefi-fig19.png
deleted file mode 100644
index 8845608fbd..0000000000
Binary files a/devices/surface/images/manage-surface-uefi-fig19.png and /dev/null differ
diff --git a/devices/surface/images/manage-surface-uefi-fig2.png b/devices/surface/images/manage-surface-uefi-fig2.png
deleted file mode 100644
index 6d8e4b41c8..0000000000
Binary files a/devices/surface/images/manage-surface-uefi-fig2.png and /dev/null differ
diff --git a/devices/surface/images/manage-surface-uefi-fig3.png b/devices/surface/images/manage-surface-uefi-fig3.png
deleted file mode 100644
index 4ae63c2a49..0000000000
Binary files a/devices/surface/images/manage-surface-uefi-fig3.png and /dev/null differ
diff --git a/devices/surface/images/manage-surface-uefi-fig4.png b/devices/surface/images/manage-surface-uefi-fig4.png
deleted file mode 100644
index 480b1d7f46..0000000000
Binary files a/devices/surface/images/manage-surface-uefi-fig4.png and /dev/null differ
diff --git a/devices/surface/images/manage-surface-uefi-fig5-a.png b/devices/surface/images/manage-surface-uefi-fig5-a.png
deleted file mode 100644
index 7605291e93..0000000000
Binary files a/devices/surface/images/manage-surface-uefi-fig5-a.png and /dev/null differ
diff --git a/devices/surface/images/manage-surface-uefi-fig5.png b/devices/surface/images/manage-surface-uefi-fig5.png
deleted file mode 100644
index 00bb44ea76..0000000000
Binary files a/devices/surface/images/manage-surface-uefi-fig5.png and /dev/null differ
diff --git a/devices/surface/images/manage-surface-uefi-fig5a.png b/devices/surface/images/manage-surface-uefi-fig5a.png
deleted file mode 100644
index 7baecb2fff..0000000000
Binary files a/devices/surface/images/manage-surface-uefi-fig5a.png and /dev/null differ
diff --git a/devices/surface/images/manage-surface-uefi-fig6.png b/devices/surface/images/manage-surface-uefi-fig6.png
deleted file mode 100644
index e424e84f4b..0000000000
Binary files a/devices/surface/images/manage-surface-uefi-fig6.png and /dev/null differ
diff --git a/devices/surface/images/manage-surface-uefi-fig7.png b/devices/surface/images/manage-surface-uefi-fig7.png
deleted file mode 100644
index b0a49134f3..0000000000
Binary files a/devices/surface/images/manage-surface-uefi-fig7.png and /dev/null differ
diff --git a/devices/surface/images/manage-surface-uefi-fig7a.png b/devices/surface/images/manage-surface-uefi-fig7a.png
deleted file mode 100644
index 62e6536ea8..0000000000
Binary files a/devices/surface/images/manage-surface-uefi-fig7a.png and /dev/null differ
diff --git a/devices/surface/images/manage-surface-uefi-fig8.png b/devices/surface/images/manage-surface-uefi-fig8.png
deleted file mode 100644
index 2269fe6c17..0000000000
Binary files a/devices/surface/images/manage-surface-uefi-fig8.png and /dev/null differ
diff --git a/devices/surface/images/manage-surface-uefi-fig9.png b/devices/surface/images/manage-surface-uefi-fig9.png
deleted file mode 100644
index 7d36f66808..0000000000
Binary files a/devices/surface/images/manage-surface-uefi-fig9.png and /dev/null differ
diff --git a/devices/surface/images/manage-surface-uefi-figure-1.png b/devices/surface/images/manage-surface-uefi-figure-1.png
deleted file mode 100644
index cd5a789d70..0000000000
Binary files a/devices/surface/images/manage-surface-uefi-figure-1.png and /dev/null differ
diff --git a/devices/surface/images/managefirmware.png b/devices/surface/images/managefirmware.png
deleted file mode 100644
index 392bcc601c..0000000000
Binary files a/devices/surface/images/managefirmware.png and /dev/null differ
diff --git a/devices/surface/images/managesettings.png b/devices/surface/images/managesettings.png
deleted file mode 100644
index 0f0567f97c..0000000000
Binary files a/devices/surface/images/managesettings.png and /dev/null differ
diff --git a/devices/surface/images/mdt.png b/devices/surface/images/mdt.png
deleted file mode 100644
index e185c8c501..0000000000
Binary files a/devices/surface/images/mdt.png and /dev/null differ
diff --git a/devices/surface/images/powerintrofig1.png b/devices/surface/images/powerintrofig1.png
deleted file mode 100644
index d33b9922fd..0000000000
Binary files a/devices/surface/images/powerintrofig1.png and /dev/null differ
diff --git a/devices/surface/images/powerintrofig1a.png b/devices/surface/images/powerintrofig1a.png
deleted file mode 100644
index e704b940c9..0000000000
Binary files a/devices/surface/images/powerintrofig1a.png and /dev/null differ
diff --git a/devices/surface/images/powerintrofig2.png b/devices/surface/images/powerintrofig2.png
deleted file mode 100644
index eea52a8f3d..0000000000
Binary files a/devices/surface/images/powerintrofig2.png and /dev/null differ
diff --git a/devices/surface/images/powerintrofig2a.png b/devices/surface/images/powerintrofig2a.png
deleted file mode 100644
index e00fe81105..0000000000
Binary files a/devices/surface/images/powerintrofig2a.png and /dev/null differ
diff --git a/devices/surface/images/powerintrofig3.png b/devices/surface/images/powerintrofig3.png
deleted file mode 100644
index 08e9cd36a3..0000000000
Binary files a/devices/surface/images/powerintrofig3.png and /dev/null differ
diff --git a/devices/surface/images/powerintrofig4.png b/devices/surface/images/powerintrofig4.png
deleted file mode 100644
index f983673f35..0000000000
Binary files a/devices/surface/images/powerintrofig4.png and /dev/null differ
diff --git a/devices/surface/images/preparewindowsdeployment.png b/devices/surface/images/preparewindowsdeployment.png
deleted file mode 100644
index d7c04abc9e..0000000000
Binary files a/devices/surface/images/preparewindowsdeployment.png and /dev/null differ
diff --git a/devices/surface/images/regeditDock.png b/devices/surface/images/regeditDock.png
deleted file mode 100644
index e074712665..0000000000
Binary files a/devices/surface/images/regeditDock.png and /dev/null differ
diff --git a/devices/surface/images/sccm.png b/devices/surface/images/sccm.png
deleted file mode 100644
index 754f2ef89f..0000000000
Binary files a/devices/surface/images/sccm.png and /dev/null differ
diff --git a/devices/surface/images/sda-fig1-select-steps.png b/devices/surface/images/sda-fig1-select-steps.png
deleted file mode 100644
index cb5c24c2e0..0000000000
Binary files a/devices/surface/images/sda-fig1-select-steps.png and /dev/null differ
diff --git a/devices/surface/images/sda-fig2-specify-local.png b/devices/surface/images/sda-fig2-specify-local.png
deleted file mode 100644
index a7eb4d5b33..0000000000
Binary files a/devices/surface/images/sda-fig2-specify-local.png and /dev/null differ
diff --git a/devices/surface/images/sda-fig5-erase.png b/devices/surface/images/sda-fig5-erase.png
deleted file mode 100644
index 8ac3e174a7..0000000000
Binary files a/devices/surface/images/sda-fig5-erase.png and /dev/null differ
diff --git a/devices/surface/images/sda.png b/devices/surface/images/sda.png
deleted file mode 100644
index b9433dcd4a..0000000000
Binary files a/devices/surface/images/sda.png and /dev/null differ
diff --git a/devices/surface/images/sdasteps-fig1.png b/devices/surface/images/sdasteps-fig1.png
deleted file mode 100644
index 2f83597305..0000000000
Binary files a/devices/surface/images/sdasteps-fig1.png and /dev/null differ
diff --git a/devices/surface/images/sdasteps-fig10-rules.png b/devices/surface/images/sdasteps-fig10-rules.png
deleted file mode 100644
index 581c6f1492..0000000000
Binary files a/devices/surface/images/sdasteps-fig10-rules.png and /dev/null differ
diff --git a/devices/surface/images/sdasteps-fig11-bootstrap.ini.png b/devices/surface/images/sdasteps-fig11-bootstrap.ini.png
deleted file mode 100644
index 64a4bd9aad..0000000000
Binary files a/devices/surface/images/sdasteps-fig11-bootstrap.ini.png and /dev/null differ
diff --git a/devices/surface/images/sdasteps-fig12-updatemedia.png b/devices/surface/images/sdasteps-fig12-updatemedia.png
deleted file mode 100644
index 01a677ba02..0000000000
Binary files a/devices/surface/images/sdasteps-fig12-updatemedia.png and /dev/null differ
diff --git a/devices/surface/images/sdasteps-fig13-taskseq.png b/devices/surface/images/sdasteps-fig13-taskseq.png
deleted file mode 100644
index 1fe51f0b60..0000000000
Binary files a/devices/surface/images/sdasteps-fig13-taskseq.png and /dev/null differ
diff --git a/devices/surface/images/sdasteps-fig14-credentials.png b/devices/surface/images/sdasteps-fig14-credentials.png
deleted file mode 100644
index d2944325f4..0000000000
Binary files a/devices/surface/images/sdasteps-fig14-credentials.png and /dev/null differ
diff --git a/devices/surface/images/sdasteps-fig15-deploy.png b/devices/surface/images/sdasteps-fig15-deploy.png
deleted file mode 100644
index 14cc461225..0000000000
Binary files a/devices/surface/images/sdasteps-fig15-deploy.png and /dev/null differ
diff --git a/devices/surface/images/sdasteps-fig16-computername.png b/devices/surface/images/sdasteps-fig16-computername.png
deleted file mode 100644
index 1960c5b138..0000000000
Binary files a/devices/surface/images/sdasteps-fig16-computername.png and /dev/null differ
diff --git a/devices/surface/images/sdasteps-fig17-installprogresswindow.png b/devices/surface/images/sdasteps-fig17-installprogresswindow.png
deleted file mode 100644
index ab2c456857..0000000000
Binary files a/devices/surface/images/sdasteps-fig17-installprogresswindow.png and /dev/null differ
diff --git a/devices/surface/images/sdasteps-fig2.png b/devices/surface/images/sdasteps-fig2.png
deleted file mode 100644
index 4edeb35ca3..0000000000
Binary files a/devices/surface/images/sdasteps-fig2.png and /dev/null differ
diff --git a/devices/surface/images/sdasteps-fig3.png b/devices/surface/images/sdasteps-fig3.png
deleted file mode 100644
index 728ddab514..0000000000
Binary files a/devices/surface/images/sdasteps-fig3.png and /dev/null differ
diff --git a/devices/surface/images/sdasteps-fig4-select.png b/devices/surface/images/sdasteps-fig4-select.png
deleted file mode 100644
index 15d4df2af7..0000000000
Binary files a/devices/surface/images/sdasteps-fig4-select.png and /dev/null differ
diff --git a/devices/surface/images/sdasteps-fig5-installwindow.png b/devices/surface/images/sdasteps-fig5-installwindow.png
deleted file mode 100644
index 66f1814146..0000000000
Binary files a/devices/surface/images/sdasteps-fig5-installwindow.png and /dev/null differ
diff --git a/devices/surface/images/sdasteps-fig6-specify-driver-app-files.png b/devices/surface/images/sdasteps-fig6-specify-driver-app-files.png
deleted file mode 100644
index cb82d3fec7..0000000000
Binary files a/devices/surface/images/sdasteps-fig6-specify-driver-app-files.png and /dev/null differ
diff --git a/devices/surface/images/sdasteps-fig7-diskpart.png b/devices/surface/images/sdasteps-fig7-diskpart.png
deleted file mode 100644
index 70b517f3f1..0000000000
Binary files a/devices/surface/images/sdasteps-fig7-diskpart.png and /dev/null differ
diff --git a/devices/surface/images/sdasteps-fig8-mediafolder.png b/devices/surface/images/sdasteps-fig8-mediafolder.png
deleted file mode 100644
index f6a862e60f..0000000000
Binary files a/devices/surface/images/sdasteps-fig8-mediafolder.png and /dev/null differ
diff --git a/devices/surface/images/sdasteps-fig9-location.png b/devices/surface/images/sdasteps-fig9-location.png
deleted file mode 100644
index c8247de908..0000000000
Binary files a/devices/surface/images/sdasteps-fig9-location.png and /dev/null differ
diff --git a/devices/surface/images/sdt-1.png b/devices/surface/images/sdt-1.png
deleted file mode 100644
index fb10753608..0000000000
Binary files a/devices/surface/images/sdt-1.png and /dev/null differ
diff --git a/devices/surface/images/sdt-2.png b/devices/surface/images/sdt-2.png
deleted file mode 100644
index be951967f0..0000000000
Binary files a/devices/surface/images/sdt-2.png and /dev/null differ
diff --git a/devices/surface/images/sdt-3.png b/devices/surface/images/sdt-3.png
deleted file mode 100644
index 0d3077cc1b..0000000000
Binary files a/devices/surface/images/sdt-3.png and /dev/null differ
diff --git a/devices/surface/images/sdt-4.png b/devices/surface/images/sdt-4.png
deleted file mode 100644
index babddbb240..0000000000
Binary files a/devices/surface/images/sdt-4.png and /dev/null differ
diff --git a/devices/surface/images/sdt-5.png b/devices/surface/images/sdt-5.png
deleted file mode 100644
index 5c5346d93a..0000000000
Binary files a/devices/surface/images/sdt-5.png and /dev/null differ
diff --git a/devices/surface/images/sdt-6.png b/devices/surface/images/sdt-6.png
deleted file mode 100644
index acf8e684b3..0000000000
Binary files a/devices/surface/images/sdt-6.png and /dev/null differ
diff --git a/devices/surface/images/sdt-7.png b/devices/surface/images/sdt-7.png
deleted file mode 100644
index 5e16961c6b..0000000000
Binary files a/devices/surface/images/sdt-7.png and /dev/null differ
diff --git a/devices/surface/images/sdt-desk-1.png b/devices/surface/images/sdt-desk-1.png
deleted file mode 100644
index f1ecc03b30..0000000000
Binary files a/devices/surface/images/sdt-desk-1.png and /dev/null differ
diff --git a/devices/surface/images/sdt-desk-2.png b/devices/surface/images/sdt-desk-2.png
deleted file mode 100644
index 3d066cb3e5..0000000000
Binary files a/devices/surface/images/sdt-desk-2.png and /dev/null differ
diff --git a/devices/surface/images/sdt-desk-3.png b/devices/surface/images/sdt-desk-3.png
deleted file mode 100644
index bbd9709300..0000000000
Binary files a/devices/surface/images/sdt-desk-3.png and /dev/null differ
diff --git a/devices/surface/images/sdt-desk-4.png b/devices/surface/images/sdt-desk-4.png
deleted file mode 100644
index f533646605..0000000000
Binary files a/devices/surface/images/sdt-desk-4.png and /dev/null differ
diff --git a/devices/surface/images/sdt-desk-5.png b/devices/surface/images/sdt-desk-5.png
deleted file mode 100644
index 664828762e..0000000000
Binary files a/devices/surface/images/sdt-desk-5.png and /dev/null differ
diff --git a/devices/surface/images/sdt-desk-6.png b/devices/surface/images/sdt-desk-6.png
deleted file mode 100644
index 1b9ce9f7e2..0000000000
Binary files a/devices/surface/images/sdt-desk-6.png and /dev/null differ
diff --git a/devices/surface/images/sdt-install.png b/devices/surface/images/sdt-install.png
deleted file mode 100644
index ce0fe297d7..0000000000
Binary files a/devices/surface/images/sdt-install.png and /dev/null differ
diff --git a/devices/surface/images/semm-bl.png b/devices/surface/images/semm-bl.png
deleted file mode 100644
index 3f8a375057..0000000000
Binary files a/devices/surface/images/semm-bl.png and /dev/null differ
diff --git a/devices/surface/images/surface-deploymdt-fig1.png b/devices/surface/images/surface-deploymdt-fig1.png
deleted file mode 100644
index d2fe0995a7..0000000000
Binary files a/devices/surface/images/surface-deploymdt-fig1.png and /dev/null differ
diff --git a/devices/surface/images/surface-deploymdt-fig10.png b/devices/surface/images/surface-deploymdt-fig10.png
deleted file mode 100644
index 96cb86b56f..0000000000
Binary files a/devices/surface/images/surface-deploymdt-fig10.png and /dev/null differ
diff --git a/devices/surface/images/surface-deploymdt-fig11.png b/devices/surface/images/surface-deploymdt-fig11.png
deleted file mode 100644
index a78c147322..0000000000
Binary files a/devices/surface/images/surface-deploymdt-fig11.png and /dev/null differ
diff --git a/devices/surface/images/surface-deploymdt-fig12.png b/devices/surface/images/surface-deploymdt-fig12.png
deleted file mode 100644
index 6200a677ec..0000000000
Binary files a/devices/surface/images/surface-deploymdt-fig12.png and /dev/null differ
diff --git a/devices/surface/images/surface-deploymdt-fig13.png b/devices/surface/images/surface-deploymdt-fig13.png
deleted file mode 100644
index c04c8f6d19..0000000000
Binary files a/devices/surface/images/surface-deploymdt-fig13.png and /dev/null differ
diff --git a/devices/surface/images/surface-deploymdt-fig14.png b/devices/surface/images/surface-deploymdt-fig14.png
deleted file mode 100644
index f02bc1fdb9..0000000000
Binary files a/devices/surface/images/surface-deploymdt-fig14.png and /dev/null differ
diff --git a/devices/surface/images/surface-deploymdt-fig15.png b/devices/surface/images/surface-deploymdt-fig15.png
deleted file mode 100644
index 4eb72e98cc..0000000000
Binary files a/devices/surface/images/surface-deploymdt-fig15.png and /dev/null differ
diff --git a/devices/surface/images/surface-deploymdt-fig16.png b/devices/surface/images/surface-deploymdt-fig16.png
deleted file mode 100644
index 0c5abc40a3..0000000000
Binary files a/devices/surface/images/surface-deploymdt-fig16.png and /dev/null differ
diff --git a/devices/surface/images/surface-deploymdt-fig17.png b/devices/surface/images/surface-deploymdt-fig17.png
deleted file mode 100644
index 3ccd548a70..0000000000
Binary files a/devices/surface/images/surface-deploymdt-fig17.png and /dev/null differ
diff --git a/devices/surface/images/surface-deploymdt-fig18.png b/devices/surface/images/surface-deploymdt-fig18.png
deleted file mode 100644
index f510c5b884..0000000000
Binary files a/devices/surface/images/surface-deploymdt-fig18.png and /dev/null differ
diff --git a/devices/surface/images/surface-deploymdt-fig19.png b/devices/surface/images/surface-deploymdt-fig19.png
deleted file mode 100644
index 535a139991..0000000000
Binary files a/devices/surface/images/surface-deploymdt-fig19.png and /dev/null differ
diff --git a/devices/surface/images/surface-deploymdt-fig2.png b/devices/surface/images/surface-deploymdt-fig2.png
deleted file mode 100644
index ad18f2ad58..0000000000
Binary files a/devices/surface/images/surface-deploymdt-fig2.png and /dev/null differ
diff --git a/devices/surface/images/surface-deploymdt-fig20.png b/devices/surface/images/surface-deploymdt-fig20.png
deleted file mode 100644
index 045801b6ac..0000000000
Binary files a/devices/surface/images/surface-deploymdt-fig20.png and /dev/null differ
diff --git a/devices/surface/images/surface-deploymdt-fig21.png b/devices/surface/images/surface-deploymdt-fig21.png
deleted file mode 100644
index 7660a618c8..0000000000
Binary files a/devices/surface/images/surface-deploymdt-fig21.png and /dev/null differ
diff --git a/devices/surface/images/surface-deploymdt-fig22.png b/devices/surface/images/surface-deploymdt-fig22.png
deleted file mode 100644
index 1852197dc7..0000000000
Binary files a/devices/surface/images/surface-deploymdt-fig22.png and /dev/null differ
diff --git a/devices/surface/images/surface-deploymdt-fig23.png b/devices/surface/images/surface-deploymdt-fig23.png
deleted file mode 100644
index 306a662236..0000000000
Binary files a/devices/surface/images/surface-deploymdt-fig23.png and /dev/null differ
diff --git a/devices/surface/images/surface-deploymdt-fig24.png b/devices/surface/images/surface-deploymdt-fig24.png
deleted file mode 100644
index 546a310733..0000000000
Binary files a/devices/surface/images/surface-deploymdt-fig24.png and /dev/null differ
diff --git a/devices/surface/images/surface-deploymdt-fig25.png b/devices/surface/images/surface-deploymdt-fig25.png
deleted file mode 100644
index a58b7fba71..0000000000
Binary files a/devices/surface/images/surface-deploymdt-fig25.png and /dev/null differ
diff --git a/devices/surface/images/surface-deploymdt-fig3.png b/devices/surface/images/surface-deploymdt-fig3.png
deleted file mode 100644
index 7d87a1c986..0000000000
Binary files a/devices/surface/images/surface-deploymdt-fig3.png and /dev/null differ
diff --git a/devices/surface/images/surface-deploymdt-fig4.png b/devices/surface/images/surface-deploymdt-fig4.png
deleted file mode 100644
index 944fd37f41..0000000000
Binary files a/devices/surface/images/surface-deploymdt-fig4.png and /dev/null differ
diff --git a/devices/surface/images/surface-deploymdt-fig5.png b/devices/surface/images/surface-deploymdt-fig5.png
deleted file mode 100644
index 8fa0679886..0000000000
Binary files a/devices/surface/images/surface-deploymdt-fig5.png and /dev/null differ
diff --git a/devices/surface/images/surface-deploymdt-fig6.png b/devices/surface/images/surface-deploymdt-fig6.png
deleted file mode 100644
index 53c923be28..0000000000
Binary files a/devices/surface/images/surface-deploymdt-fig6.png and /dev/null differ
diff --git a/devices/surface/images/surface-deploymdt-fig7.png b/devices/surface/images/surface-deploymdt-fig7.png
deleted file mode 100644
index 48892a9ef0..0000000000
Binary files a/devices/surface/images/surface-deploymdt-fig7.png and /dev/null differ
diff --git a/devices/surface/images/surface-deploymdt-fig8.png b/devices/surface/images/surface-deploymdt-fig8.png
deleted file mode 100644
index 59028f2a82..0000000000
Binary files a/devices/surface/images/surface-deploymdt-fig8.png and /dev/null differ
diff --git a/devices/surface/images/surface-deploymdt-fig9.png b/devices/surface/images/surface-deploymdt-fig9.png
deleted file mode 100644
index 6044405883..0000000000
Binary files a/devices/surface/images/surface-deploymdt-fig9.png and /dev/null differ
diff --git a/devices/surface/images/surface-diagnostic-kit-fig1-options.png b/devices/surface/images/surface-diagnostic-kit-fig1-options.png
deleted file mode 100644
index 8e10b877f9..0000000000
Binary files a/devices/surface/images/surface-diagnostic-kit-fig1-options.png and /dev/null differ
diff --git a/devices/surface/images/surface-diagnostic-kit-fig2-testdepth.png b/devices/surface/images/surface-diagnostic-kit-fig2-testdepth.png
deleted file mode 100644
index 061c7748b3..0000000000
Binary files a/devices/surface/images/surface-diagnostic-kit-fig2-testdepth.png and /dev/null differ
diff --git a/devices/surface/images/surface-diagnostic-kit-fig3-results.png b/devices/surface/images/surface-diagnostic-kit-fig3-results.png
deleted file mode 100644
index e02087d6d9..0000000000
Binary files a/devices/surface/images/surface-diagnostic-kit-fig3-results.png and /dev/null differ
diff --git a/devices/surface/images/surface-diagnostic-kit-fig4-notes.png b/devices/surface/images/surface-diagnostic-kit-fig4-notes.png
deleted file mode 100644
index 02726648db..0000000000
Binary files a/devices/surface/images/surface-diagnostic-kit-fig4-notes.png and /dev/null differ
diff --git a/devices/surface/images/surface-diagnostic-kit-gear-icon.png b/devices/surface/images/surface-diagnostic-kit-gear-icon.png
deleted file mode 100644
index fe6be488b1..0000000000
Binary files a/devices/surface/images/surface-diagnostic-kit-gear-icon.png and /dev/null differ
diff --git a/devices/surface/images/surface-enroll-semm-fig1.png b/devices/surface/images/surface-enroll-semm-fig1.png
deleted file mode 100644
index 0db814ae84..0000000000
Binary files a/devices/surface/images/surface-enroll-semm-fig1.png and /dev/null differ
diff --git a/devices/surface/images/surface-ent-mgmt-fig1-uefi-configurator.png b/devices/surface/images/surface-ent-mgmt-fig1-uefi-configurator.png
deleted file mode 100644
index e8fb93a1a7..0000000000
Binary files a/devices/surface/images/surface-ent-mgmt-fig1-uefi-configurator.png and /dev/null differ
diff --git a/devices/surface/images/surface-ent-mgmt-fig2-securepackage.png b/devices/surface/images/surface-ent-mgmt-fig2-securepackage.png
deleted file mode 100644
index fa47419ca0..0000000000
Binary files a/devices/surface/images/surface-ent-mgmt-fig2-securepackage.png and /dev/null differ
diff --git a/devices/surface/images/surface-ent-mgmt-fig3-enabledisable.png b/devices/surface/images/surface-ent-mgmt-fig3-enabledisable.png
deleted file mode 100644
index 0a34907def..0000000000
Binary files a/devices/surface/images/surface-ent-mgmt-fig3-enabledisable.png and /dev/null differ
diff --git a/devices/surface/images/surface-ent-mgmt-fig4-advancedsettings.png b/devices/surface/images/surface-ent-mgmt-fig4-advancedsettings.png
deleted file mode 100644
index f425466056..0000000000
Binary files a/devices/surface/images/surface-ent-mgmt-fig4-advancedsettings.png and /dev/null differ
diff --git a/devices/surface/images/surface-ent-mgmt-fig5-success.png b/devices/surface/images/surface-ent-mgmt-fig5-success.png
deleted file mode 100644
index e671570fee..0000000000
Binary files a/devices/surface/images/surface-ent-mgmt-fig5-success.png and /dev/null differ
diff --git a/devices/surface/images/surface-ent-mgmt-fig6-enrollconfirm.png b/devices/surface/images/surface-ent-mgmt-fig6-enrollconfirm.png
deleted file mode 100644
index a1421da21c..0000000000
Binary files a/devices/surface/images/surface-ent-mgmt-fig6-enrollconfirm.png and /dev/null differ
diff --git a/devices/surface/images/surface-ent-mgmt-fig7-semmrecovery.png b/devices/surface/images/surface-ent-mgmt-fig7-semmrecovery.png
deleted file mode 100644
index 91c03fef5e..0000000000
Binary files a/devices/surface/images/surface-ent-mgmt-fig7-semmrecovery.png and /dev/null differ
diff --git a/devices/surface/images/surface-laptop-keyboard-1.png b/devices/surface/images/surface-laptop-keyboard-1.png
deleted file mode 100644
index 090ca2b58e..0000000000
Binary files a/devices/surface/images/surface-laptop-keyboard-1.png and /dev/null differ
diff --git a/devices/surface/images/surface-laptop-keyboard-2.png b/devices/surface/images/surface-laptop-keyboard-2.png
deleted file mode 100644
index 2a2cb8b3be..0000000000
Binary files a/devices/surface/images/surface-laptop-keyboard-2.png and /dev/null differ
diff --git a/devices/surface/images/surface-laptop-keyboard-3.png b/devices/surface/images/surface-laptop-keyboard-3.png
deleted file mode 100644
index 80ccc1fc3c..0000000000
Binary files a/devices/surface/images/surface-laptop-keyboard-3.png and /dev/null differ
diff --git a/devices/surface/images/surface-laptop-keyboard-4.png b/devices/surface/images/surface-laptop-keyboard-4.png
deleted file mode 100644
index cf08e7a292..0000000000
Binary files a/devices/surface/images/surface-laptop-keyboard-4.png and /dev/null differ
diff --git a/devices/surface/images/surface-laptop-keyboard-5.png b/devices/surface/images/surface-laptop-keyboard-5.png
deleted file mode 100644
index cf4bc9109c..0000000000
Binary files a/devices/surface/images/surface-laptop-keyboard-5.png and /dev/null differ
diff --git a/devices/surface/images/surface-semm-enroll-fig1.png b/devices/surface/images/surface-semm-enroll-fig1.png
deleted file mode 100644
index 0db814ae84..0000000000
Binary files a/devices/surface/images/surface-semm-enroll-fig1.png and /dev/null differ
diff --git a/devices/surface/images/surface-semm-enroll-fig10.png b/devices/surface/images/surface-semm-enroll-fig10.png
deleted file mode 100644
index e61cf3d70a..0000000000
Binary files a/devices/surface/images/surface-semm-enroll-fig10.png and /dev/null differ
diff --git a/devices/surface/images/surface-semm-enroll-fig11.png b/devices/surface/images/surface-semm-enroll-fig11.png
deleted file mode 100644
index 91c03fef5e..0000000000
Binary files a/devices/surface/images/surface-semm-enroll-fig11.png and /dev/null differ
diff --git a/devices/surface/images/surface-semm-enroll-fig12.png b/devices/surface/images/surface-semm-enroll-fig12.png
deleted file mode 100644
index d6c0505c16..0000000000
Binary files a/devices/surface/images/surface-semm-enroll-fig12.png and /dev/null differ
diff --git a/devices/surface/images/surface-semm-enroll-fig3.png b/devices/surface/images/surface-semm-enroll-fig3.png
deleted file mode 100644
index 2d66b485f9..0000000000
Binary files a/devices/surface/images/surface-semm-enroll-fig3.png and /dev/null differ
diff --git a/devices/surface/images/surface-semm-enroll-fig4.png b/devices/surface/images/surface-semm-enroll-fig4.png
deleted file mode 100644
index 39b0c797e7..0000000000
Binary files a/devices/surface/images/surface-semm-enroll-fig4.png and /dev/null differ
diff --git a/devices/surface/images/surface-semm-enroll-fig5.png b/devices/surface/images/surface-semm-enroll-fig5.png
deleted file mode 100644
index b3d3db34c7..0000000000
Binary files a/devices/surface/images/surface-semm-enroll-fig5.png and /dev/null differ
diff --git a/devices/surface/images/surface-semm-enroll-fig6.png b/devices/surface/images/surface-semm-enroll-fig6.png
deleted file mode 100644
index 95b1c1b24b..0000000000
Binary files a/devices/surface/images/surface-semm-enroll-fig6.png and /dev/null differ
diff --git a/devices/surface/images/surface-semm-enroll-fig7.png b/devices/surface/images/surface-semm-enroll-fig7.png
deleted file mode 100644
index 26a640ac0c..0000000000
Binary files a/devices/surface/images/surface-semm-enroll-fig7.png and /dev/null differ
diff --git a/devices/surface/images/surface-semm-enroll-fig8.png b/devices/surface/images/surface-semm-enroll-fig8.png
deleted file mode 100644
index a1421da21c..0000000000
Binary files a/devices/surface/images/surface-semm-enroll-fig8.png and /dev/null differ
diff --git a/devices/surface/images/surface-semm-enroll-fig9.png b/devices/surface/images/surface-semm-enroll-fig9.png
deleted file mode 100644
index 9229ee255d..0000000000
Binary files a/devices/surface/images/surface-semm-enroll-fig9.png and /dev/null differ
diff --git a/devices/surface/images/surface-semm-enrollment-fig2.png b/devices/surface/images/surface-semm-enrollment-fig2.png
deleted file mode 100644
index 1a5649b01e..0000000000
Binary files a/devices/surface/images/surface-semm-enrollment-fig2.png and /dev/null differ
diff --git a/devices/surface/images/surface-semm-unenroll-fig1.png b/devices/surface/images/surface-semm-unenroll-fig1.png
deleted file mode 100644
index b0247d3871..0000000000
Binary files a/devices/surface/images/surface-semm-unenroll-fig1.png and /dev/null differ
diff --git a/devices/surface/images/surface-semm-unenroll-fig10.png b/devices/surface/images/surface-semm-unenroll-fig10.png
deleted file mode 100644
index 968bf44d8c..0000000000
Binary files a/devices/surface/images/surface-semm-unenroll-fig10.png and /dev/null differ
diff --git a/devices/surface/images/surface-semm-unenroll-fig11.png b/devices/surface/images/surface-semm-unenroll-fig11.png
deleted file mode 100644
index c5e86d2b65..0000000000
Binary files a/devices/surface/images/surface-semm-unenroll-fig11.png and /dev/null differ
diff --git a/devices/surface/images/surface-semm-unenroll-fig12.png b/devices/surface/images/surface-semm-unenroll-fig12.png
deleted file mode 100644
index d9a3e0617b..0000000000
Binary files a/devices/surface/images/surface-semm-unenroll-fig12.png and /dev/null differ
diff --git a/devices/surface/images/surface-semm-unenroll-fig13.png b/devices/surface/images/surface-semm-unenroll-fig13.png
deleted file mode 100644
index cfe16c3a99..0000000000
Binary files a/devices/surface/images/surface-semm-unenroll-fig13.png and /dev/null differ
diff --git a/devices/surface/images/surface-semm-unenroll-fig14.png b/devices/surface/images/surface-semm-unenroll-fig14.png
deleted file mode 100644
index 5c95097c8d..0000000000
Binary files a/devices/surface/images/surface-semm-unenroll-fig14.png and /dev/null differ
diff --git a/devices/surface/images/surface-semm-unenroll-fig2.png b/devices/surface/images/surface-semm-unenroll-fig2.png
deleted file mode 100644
index 5affd8cef6..0000000000
Binary files a/devices/surface/images/surface-semm-unenroll-fig2.png and /dev/null differ
diff --git a/devices/surface/images/surface-semm-unenroll-fig3.png b/devices/surface/images/surface-semm-unenroll-fig3.png
deleted file mode 100644
index 45c1ae38ed..0000000000
Binary files a/devices/surface/images/surface-semm-unenroll-fig3.png and /dev/null differ
diff --git a/devices/surface/images/surface-semm-unenroll-fig4.png b/devices/surface/images/surface-semm-unenroll-fig4.png
deleted file mode 100644
index c4ecf92b1b..0000000000
Binary files a/devices/surface/images/surface-semm-unenroll-fig4.png and /dev/null differ
diff --git a/devices/surface/images/surface-semm-unenroll-fig5.png b/devices/surface/images/surface-semm-unenroll-fig5.png
deleted file mode 100644
index 9229ee255d..0000000000
Binary files a/devices/surface/images/surface-semm-unenroll-fig5.png and /dev/null differ
diff --git a/devices/surface/images/surface-semm-unenroll-fig6.png b/devices/surface/images/surface-semm-unenroll-fig6.png
deleted file mode 100644
index 91c03fef5e..0000000000
Binary files a/devices/surface/images/surface-semm-unenroll-fig6.png and /dev/null differ
diff --git a/devices/surface/images/surface-semm-unenroll-fig7.png b/devices/surface/images/surface-semm-unenroll-fig7.png
deleted file mode 100644
index 0dcbace491..0000000000
Binary files a/devices/surface/images/surface-semm-unenroll-fig7.png and /dev/null differ
diff --git a/devices/surface/images/surface-semm-unenroll-fig8.png b/devices/surface/images/surface-semm-unenroll-fig8.png
deleted file mode 100644
index 77e7e05407..0000000000
Binary files a/devices/surface/images/surface-semm-unenroll-fig8.png and /dev/null differ
diff --git a/devices/surface/images/surface-semm-unenroll-fig9.png b/devices/surface/images/surface-semm-unenroll-fig9.png
deleted file mode 100644
index b40ccb2449..0000000000
Binary files a/devices/surface/images/surface-semm-unenroll-fig9.png and /dev/null differ
diff --git a/devices/surface/images/surface-upgrademdt-fig1.png b/devices/surface/images/surface-upgrademdt-fig1.png
deleted file mode 100644
index 094f5d700b..0000000000
Binary files a/devices/surface/images/surface-upgrademdt-fig1.png and /dev/null differ
diff --git a/devices/surface/images/surface-upgrademdt-fig2.png b/devices/surface/images/surface-upgrademdt-fig2.png
deleted file mode 100644
index 88ec207691..0000000000
Binary files a/devices/surface/images/surface-upgrademdt-fig2.png and /dev/null differ
diff --git a/devices/surface/images/surface-upgrademdt-fig3.png b/devices/surface/images/surface-upgrademdt-fig3.png
deleted file mode 100644
index 7660a618c8..0000000000
Binary files a/devices/surface/images/surface-upgrademdt-fig3.png and /dev/null differ
diff --git a/devices/surface/images/surface-upgrademdt-fig4.png b/devices/surface/images/surface-upgrademdt-fig4.png
deleted file mode 100644
index 1852197dc7..0000000000
Binary files a/devices/surface/images/surface-upgrademdt-fig4.png and /dev/null differ
diff --git a/devices/surface/images/surface-upgrademdt-fig5.png b/devices/surface/images/surface-upgrademdt-fig5.png
deleted file mode 100644
index 306a662236..0000000000
Binary files a/devices/surface/images/surface-upgrademdt-fig5.png and /dev/null differ
diff --git a/devices/surface/images/surfaceblog.png b/devices/surface/images/surfaceblog.png
deleted file mode 100644
index d5bef3dc3d..0000000000
Binary files a/devices/surface/images/surfaceblog.png and /dev/null differ
diff --git a/devices/surface/images/surfacebook.png b/devices/surface/images/surfacebook.png
deleted file mode 100644
index d27cf05820..0000000000
Binary files a/devices/surface/images/surfacebook.png and /dev/null differ
diff --git a/devices/surface/images/surfacedockupdater-fig1-uptodate-568pix.png b/devices/surface/images/surfacedockupdater-fig1-uptodate-568pix.png
deleted file mode 100644
index 900ffd9269..0000000000
Binary files a/devices/surface/images/surfacedockupdater-fig1-uptodate-568pix.png and /dev/null differ
diff --git a/devices/surface/images/surfacedockupdater-fig2a-needsupdating.png b/devices/surface/images/surfacedockupdater-fig2a-needsupdating.png
deleted file mode 100644
index 4c690e0a7f..0000000000
Binary files a/devices/surface/images/surfacedockupdater-fig2a-needsupdating.png and /dev/null differ
diff --git a/devices/surface/images/surfacedockupdater-fig3-progress.png b/devices/surface/images/surfacedockupdater-fig3-progress.png
deleted file mode 100644
index aa56e090e9..0000000000
Binary files a/devices/surface/images/surfacedockupdater-fig3-progress.png and /dev/null differ
diff --git a/devices/surface/images/surfacedockupdater-fig4-disconnect.png b/devices/surface/images/surfacedockupdater-fig4-disconnect.png
deleted file mode 100644
index 4892dce1ba..0000000000
Binary files a/devices/surface/images/surfacedockupdater-fig4-disconnect.png and /dev/null differ
diff --git a/devices/surface/images/surfacedockupdater-fig5-success.png b/devices/surface/images/surfacedockupdater-fig5-success.png
deleted file mode 100644
index 790ff235e9..0000000000
Binary files a/devices/surface/images/surfacedockupdater-fig5-success.png and /dev/null differ
diff --git a/devices/surface/images/surfacedockupdater-fig6-countdown.png b/devices/surface/images/surfacedockupdater-fig6-countdown.png
deleted file mode 100644
index fa208e0e4a..0000000000
Binary files a/devices/surface/images/surfacedockupdater-fig6-countdown.png and /dev/null differ
diff --git a/devices/surface/images/surfacedockupdater-fig7-error.png b/devices/surface/images/surfacedockupdater-fig7-error.png
deleted file mode 100644
index c18ef16b4c..0000000000
Binary files a/devices/surface/images/surfacedockupdater-fig7-error.png and /dev/null differ
diff --git a/devices/surface/images/surfacedockupdater-fig8-737test.png b/devices/surface/images/surfacedockupdater-fig8-737test.png
deleted file mode 100644
index c101313b96..0000000000
Binary files a/devices/surface/images/surfacedockupdater-fig8-737test.png and /dev/null differ
diff --git a/devices/surface/images/surfacemechanics.png b/devices/surface/images/surfacemechanics.png
deleted file mode 100644
index 3d42daaed2..0000000000
Binary files a/devices/surface/images/surfacemechanics.png and /dev/null differ
diff --git a/devices/surface/images/surfacepro.png b/devices/surface/images/surfacepro.png
deleted file mode 100644
index c036b2ad3a..0000000000
Binary files a/devices/surface/images/surfacepro.png and /dev/null differ
diff --git a/devices/surface/images/surfacestudio.png b/devices/surface/images/surfacestudio.png
deleted file mode 100644
index c41bbbf0f7..0000000000
Binary files a/devices/surface/images/surfacestudio.png and /dev/null differ
diff --git a/devices/surface/images/twitter.png b/devices/surface/images/twitter.png
deleted file mode 100644
index c61827284e..0000000000
Binary files a/devices/surface/images/twitter.png and /dev/null differ
diff --git a/devices/surface/images/uefidfci.png b/devices/surface/images/uefidfci.png
deleted file mode 100644
index ec95181145..0000000000
Binary files a/devices/surface/images/uefidfci.png and /dev/null differ
diff --git a/devices/surface/images/using-sda-driverfiles-fig1.png b/devices/surface/images/using-sda-driverfiles-fig1.png
deleted file mode 100644
index 51244bfe16..0000000000
Binary files a/devices/surface/images/using-sda-driverfiles-fig1.png and /dev/null differ
diff --git a/devices/surface/images/using-sda-installcommand-fig2.png b/devices/surface/images/using-sda-installcommand-fig2.png
deleted file mode 100644
index 61a4fbd1f2..0000000000
Binary files a/devices/surface/images/using-sda-installcommand-fig2.png and /dev/null differ
diff --git a/devices/surface/images/using-sda-newinstall-fig3.png b/devices/surface/images/using-sda-newinstall-fig3.png
deleted file mode 100644
index ff18b67e3e..0000000000
Binary files a/devices/surface/images/using-sda-newinstall-fig3.png and /dev/null differ
diff --git a/devices/surface/images/wifi-band.png b/devices/surface/images/wifi-band.png
deleted file mode 100644
index 38681a9dc8..0000000000
Binary files a/devices/surface/images/wifi-band.png and /dev/null differ
diff --git a/devices/surface/images/wifi-roaming.png b/devices/surface/images/wifi-roaming.png
deleted file mode 100644
index eb539c9bd6..0000000000
Binary files a/devices/surface/images/wifi-roaming.png and /dev/null differ
diff --git a/devices/surface/images/windows10.png b/devices/surface/images/windows10.png
deleted file mode 100644
index e48690853c..0000000000
Binary files a/devices/surface/images/windows10.png and /dev/null differ
diff --git a/devices/surface/images/windows10upgradepath.png b/devices/surface/images/windows10upgradepath.png
deleted file mode 100644
index c008e446ea..0000000000
Binary files a/devices/surface/images/windows10upgradepath.png and /dev/null differ
diff --git a/devices/surface/index.yml b/devices/surface/index.yml
deleted file mode 100644
index d9d7043dc2..0000000000
--- a/devices/surface/index.yml
+++ /dev/null
@@ -1,64 +0,0 @@
-### YamlMime:Hub
-
-title: Microsoft Surface # < 60 chars
-summary: Learn how to plan, deploy, and manage Microsoft Surface and Surface Hub devices. # < 160 chars
-# brand: aspnet | azure | dotnet | dynamics | m365 | ms-graph | office | power-platform | project | sharepoint | sql | sql-server | teams | vs | visual-studio | windows | xamarin
-brand: windows
-
-metadata:
- title: Microsoft Surface # Required; page title displayed in search results. Include the brand. < 60 chars.
- description: Learn how to plan, deploy, and manage Microsoft Surface and Surface Hub devices. # Required; article description that is displayed in search results. < 160 chars.
- ms.prod: surface #Required; service per approved list. service slug assigned to your service by ACOM.
- ms.topic: hub-page # Required
- audience: ITPro
- author: samanro #Required; your GitHub user alias, with correct capitalization.
- ms.author: samanro #Required; microsoft alias of author; optional team alias.
- ms.date: 07/03/2019 #Required; mm/dd/yyyy format.
- localization_priority: Priority
-
-# additionalContent section (optional)
-# Card with summary style
-additionalContent:
- # Supports up to 3 sections
- sections:
- - title: For IT Professionals # < 60 chars (optional)
- items:
- # Card
- - title: Surface devices documentation
- summary: Harness the power of Surface, Windows, and Office connected together through the cloud. Find tools, step-by-step guides, and other resources to help you plan, deploy, and manage Surface devices in your organization.
- url: https://docs.microsoft.com/en-us/surface/get-started
- # Card
- - title: Surface Hub documentation
- summary: Learn how to deploy and manage Surface Hub 2S, the all-in-one digital interactive whiteboard, meetings platform, and collaborative computing device.
- url: https://docs.microsoft.com/surface-hub/index
- # Card
- - title: Surface Hub adoption guidance
- summary: Get best practices for technical readiness and adoption across your lines of business.
- url: https://docs.microsoft.com/surface-hub/surface-hub-2s-adoption-kit
-
- - title: Other resources # < 60 chars (optional)
- items:
- # Card
- - title: Communities
- links:
- - text: Surface IT Pro blog
- url: https://techcommunity.microsoft.com/t5/Surface-IT-Pro-Blog/bg-p/SurfaceITPro
- - text: Surface Devices Tech Community
- url: https://techcommunity.microsoft.com/t5/Surface-Devices/ct-p/SurfaceDevices
- # Card
- - title: Learn
- links:
- - text: Surface training on Microsoft Learn
- url: https://docs.microsoft.com/learn/browse/?term=Surface
- - text: Microsoft Mechanics Surface videos
- url: https://www.youtube.com/watch?v=Uk2kJ5FUZxY&list=PLXtHYVsvn_b__1Baibdu4elN4SoF3JTBZ
-
- # Card
- - title: Need help?
- links:
- - text: Surface devices
- url: https://support.microsoft.com/products/surface-devices
- - text: Surface Hub
- url: https://support.microsoft.com/hub/4343507/surface-hub-help
- - text: Contact Surface Hub Support
- url: https://support.microsoft.com/supportforbusiness/productselection?sapId=bb7066fb-e329-c1c0-9c13-8e9949c6a64e
diff --git a/devices/surface/ltsb-for-surface.md b/devices/surface/ltsb-for-surface.md
deleted file mode 100644
index c250085467..0000000000
--- a/devices/surface/ltsb-for-surface.md
+++ /dev/null
@@ -1,36 +0,0 @@
----
-title: Long-Term Servicing Channel for Surface devices (Surface)
-description: LTSB is not supported for general-purpose Surface devices and should be used for specialized devices only.
-ms.prod: w10
-ms.mktglfcycl: manage
-ms.pagetype: surface, devices
-ms.sitesec: library
-author: coveminer
-ms.author: v-jokai
-ms.topic: article
-ms.reviewer:
-manager: laurawi
-ms.localizationpriority: medium
-ms.audience: itpro
----
-
-# Long-Term Servicing Channel (LTSC) for Surface devices
-
->[!WARNING]
->For updated information on this topic, see [Surface device compatibility with Windows 10 Long-Term Servicing Channel](surface-device-compatibility-with-windows-10-ltsc.md). For additional information on this update, see the [Documentation Updates for Surface and Windows 10 LTSB Compatibility](https://blogs.technet.microsoft.com/surface/2017/04/11/documentation-updates-for-surface-and-windows-10-ltsb-compatibility) post on the Surface Blog for IT Pros.
-
-General-purpose Surface devices in the Long-Term Servicing Channel (LTSC) are not supported. As a general guideline, if a Surface device runs productivity software, such as Microsoft Office, it is a general-purpose device that does not qualify for LTSC and should instead be on the Semi-Annual Channel.
-
->[!NOTE]
->For more information about the servicing branches, see [Overview of Windows as a service](https://technet.microsoft.com/itpro/windows/manage/waas-overview).
-
-LTSC prevents Surface devices from receiving critical Windows 10 feature updates and certain non-security servicing updates. Customers with poor experiences using Surface devices in the LTSC configuration will be instructed to switch to the Semi-Annual Channel. Furthermore, the Windows 10 Enterprise LTSB edition removes core features of Surface devices, including seamless inking and touch-friendly applications. It does not contain key in-box applications including Microsoft Edge, OneNote, Calendar or Camera. Therefore, productivity is impacted and functionality is limited. LTSC is not supported as a suitable servicing solution for general-purpose Surface devices.
-
-General-purpose Surface devices are intended to run on the Semi-Annual Channel to receive full servicing and firmware updates and forward compatibility with the introduction of new Surface features. In the Semi-Annual Channel, feature updates are available as soon as Microsoft releases them.
-
-Surface devices in specialized scenarios–such as PCs that control medical equipment, point-of-sale systems, and ATMs–might consider the use of LTSC. These special-purpose systems typically perform a single task and do not require feature updates as frequently as other devices in the organization.
-
-## Related topics
-
-- [Surface IT Pro Blog](https://techcommunity.microsoft.com/t5/Surface-IT-Pro-Blog/bg-p/SurfaceITPro)
-
diff --git a/devices/surface/maintain-optimal-power-settings-on-Surface-devices.md b/devices/surface/maintain-optimal-power-settings-on-Surface-devices.md
deleted file mode 100644
index 36197ca93f..0000000000
--- a/devices/surface/maintain-optimal-power-settings-on-Surface-devices.md
+++ /dev/null
@@ -1,181 +0,0 @@
----
-title: Best practice power settings for Surface devices
-description: This topic provides best practice recommendations for maintaining optimal power settings and explains how Surface streamlines the power management experience. This article applies to all currently supported Surface devices including Surface Pro 7, Surface Pro X, and Surface Laptop 3.
-ms.prod: w10
-ms.mktglfcycl: manage
-ms.sitesec: library
-author: coveminer
-ms.author: v-jokai
-ms.topic: article
-ms.reviewer:
-manager: laurawi
-ms.localizationpriority: medium
-ms.audience: itpro
-ms.date: 10/28/2019
----
-
-# Best practice power settings for Surface devices
-
-Surface devices are designed to take advantage of the latest advances in
-mobile device energy consumption to deliver a streamlined experience
-optimized across workloads. Depending on what you’re doing, Surface
-dynamically fine tunes how power flows to individual hardware
-components, momentarily waking up system components to handle background
-tasks -- such as an incoming email or network traffic -- before returning to a
-low power idle state (S0ix).
-
-## Summary of recommendations for IT administrators
-
-To ensure Surface devices across your organization fully benefit from Surface power optimization features:
-
-- Install the latest drivers and firmware from Windows Update or the Surface Driver and Firmware MSI. This creates the balanced power plan (aka power profile) by default and configures optimal power settings. For more information, refer to [Manage and deploy Surface driver and firmware updates](manage-surface-driver-and-firmware-updates.md).
-- Avoid creating custom power profiles or adjusting advanced power settings not visible in the default UI (**System** > **Power & sleep**).
-- If you must manage the power profile of devices across your network (such as in highly managed organizations), use the powercfg command tool to export the power plan from the factory image of the Surface device and then import it into the provisioning package for your Surface devices.
-
- >[!NOTE]
- >You can only export a power plan across the same type of Surface device. For example, you cannot export a power plan from Surface Laptop and import it on Surface Pro. For more information, refer to [Configure power settings](https://docs.microsoft.com/windows-hardware/customize/power-settings/configure-power-settings).
-
-- Exclude Surface devices from any existing power management policy settings.
-
-## Background
-
-The way Surface implements power management differs significantly from
-the earlier OS standard that gradually reduces and turns off power via a
-series of sleep states; for example, cycling through S1, S2, S3, and so on.
-
-Instead, Surface is imaged with a custom power profile that replaces
-legacy sleep and energy consumption functionality with modern standby
-features and dynamic fine tuning. This custom power profile is
-implemented via the Surface Serial Hub Driver and the system aggregator
-module (SAM). The SAM chip functions as the Surface device power-policy
-owner, using algorithms to calculate optimal power requirements. It
-works in conjunction with Windows power manager to allocate or throttle
-only the exact amount of power required for hardware components to
-function. This article applies to all currently supported Surface devices including Surface Pro 7, Surface Pro X, and Surface Laptop 3.
-
-## Utilizing the custom power profile in Surface
-
-If you go into the power options on a surface device, you'll see that there's a single power plan available. This is the custom power profile. And if you go to the advanced power settings, you’ll see a much smaller subset of power options compared to a generic PC running Windows 10. Unlike generic devices, Surface has firmware and custom components to manage these power options.
-
-
-## Modern Standby
-
-The algorithmically embedded custom power profile enables modern standby
-connectivity for Surface by maintaining a low power state for
-instant on/instant off functionality typical of smartphones. S0ix, also
-known as Deepest Runtime Idle Platform State (DRIPS), is the default
-power mode for Surface devices. Modern standby has two modes:
-
-- **Connected standby.** The default mode for up-to-the minute
- delivery of emails, messaging, and cloud-synced data, connected
- standby keeps Wi-Fi on and maintains network connectivity.
-
-- **Disconnected standby.** An optional mode for extended battery
- life, disconnected standby delivers the same instant-on experience
- and saves power by turning off Wi-Fi, Bluetooth, and related network
- connectivity.
-
-To learn more about modern standby, refer to the [Microsoft Hardware Dev
-Center](https://docs.microsoft.com/windows-hardware/design/device-experiences/modern-standby-wake-sources).
-
-## How Surface streamlines the power management experience
-
-Surface integrates the following features designed to help users
-optimize the power management experience:
-
-- [Singular power plan](#singular-power-plan)
-
-- [Simplified power settings user
- interface](#simplified-power-settings-user-interface)
-
-- [Windows performance power
- slider](#windows-performance-power-slider)
-
-### Singular power plan
-
-Surface is designed for a streamlined power management experience that
-eliminates the need to create custom power plans or manually configure
-power settings. Microsoft streamlines the user
-experience by delivering a single power plan (balanced) that replaces
-the multiple power plans from standard Windows builds.
-
-### Simplified power settings user interface
-
-Surface provides a simplified UI in accord with best practice power
-setting recommendations. In general, it's recommended to only adjust settings visible in the default user interface and avoid configuring advanced power settings or Group Policy settings. Using the default screen and sleep timeouts while avoiding maximum
-brightness levels are the most effective ways for users to maintain
-extended battery life.
-
-
-
-Figure 1. Simplified power and sleep settings
-
-### Windows performance power slider
-
-Surface devices running Windows 10 build 1709 and later include a power
-slider allowing you to prioritize battery life when needed or favor performance if desired. You
-can access the power slider from the taskbar by clicking on the battery
-icon. Slide left for longer battery life (battery saver mode) or slide
-right for faster performance.
-
-
-
-Figure 2. Power slider
-
-Power slider enables four states as described in the following table:
-
-| Slider mode| Description |
-|---|---|
-| Battery saver| Helps conserve power and prolong battery life when the system is disconnected from a power source. When battery saver is on, some Windows features are disabled, throttled, or behave differently. Screen brightness is also reduced. Battery saver is only available when using battery power (DC). To learn more, see [Battery Saver](https://docs.microsoft.com/windows-hardware/design/component-guidelines/battery-saver).|
-| Recommended | Delivers longer battery life than the default settings in earlier versions of Windows. |
-| Better Performance | Slightly favors performance over battery life, functioning as the default slider mode. |
-| Best Performance | Favors performance over power for workloads requiring maximum performance and responsiveness, regardless of battery power consumption.|
-
-Power slider modes directly control specific hardware components shown
-in the following table.
-
-| Component | Slider functionality |
-|---|---|
-| Intel Speed Shift (CPU energy registers) and Energy Performance Preference hint. | Selects the best operating frequency and voltage for optimal performance and power. The Energy Performance Preference (PERFEPP) is a global power efficiency hint to the CPU. |
-| Fan speed (RPM)| Where applicable, adjusts for changing conditions such as keeping fan silent in battery saver slider mode.|
-| Processor package power limits (PL1/PL2).| Requires the CPU to manage its frequency choices to accommodate a running average power limit for both steady state (PL1) and turbo (PL2) workloads.|
-| Processor turbo frequency limits (IA turbo limitations). | Adjusts processor and graphics performance allowing processor cores to run faster or slower than the rated operating frequency. |
-
->[!NOTE]
->The power slider is entirely independent of operating system power settings whether configured from Control Panel/ Power Options, Group Policy, or related methods.
-
-To learn more, see:
-
-- [Customize the Windows performance power
- slider](https://docs.microsoft.com/windows-hardware/customize/desktop/customize-power-slider)
-
-- [Battery
- saver.](https://docs.microsoft.com/windows-hardware/design/component-guidelines/battery-saver)
-
-## Best practices for extended battery life
-
-
-| Best practice | Go to | Next steps |
-|---|---|---|
-| Ensure your Surface device is up to date| Windows Update | In the taskbar search box, type **Windows Update** and select **Check for updates**. |
-| Choose the best power setting for what you’re doing | Power slider | In the taskbar, select the battery icon, then choose **Best performance**, **Best battery life**, or somewhere in between.|
-| Conserve battery when it’s low | Battery saver | In the taskbar, select the battery icon and click **Battery settings**. Select **Turn battery saver on automatically if my battery falls below** and then move the slider further to the right for longer battery life. |
-| Configure optimal screen brightness | Battery saver | In the taskbar, select the battery icon and click **Battery settings**, select **Lower screen brightness while in battery saver**. |
-| Conserve power whenever you’re not plugged in | Battery saver| Select **Turn on battery saver status until next charge**.|
-| Investigate problems with your power settings. | Power troubleshooter | In the Taskbar search for troubleshoot, select **Troubleshoot**, and then select **Power** and follow the instructions.|
-| Check app usage | Your apps | Close apps.|
-| Check your power cord for any damage.| Your power cord | Replace power cord if worn or damaged.|
-
-## Learn more
-
-- [Modern
- standby](https://docs.microsoft.com/windows-hardware/design/device-experiences/modern-standby-wake-sources)
-
-
-
-- [Customize the Windows performance power
- slider](https://docs.microsoft.com/windows-hardware/customize/desktop/customize-power-slider)
-
-- [Battery
- saver](https://docs.microsoft.com/windows-hardware/design/component-guidelines/battery-saver)
-- [Manage and deploy Surface driver and firmware updates](manage-surface-driver-and-firmware-updates.md)
diff --git a/devices/surface/manage-surface-driver-and-firmware-updates.md b/devices/surface/manage-surface-driver-and-firmware-updates.md
deleted file mode 100644
index 75ccff3070..0000000000
--- a/devices/surface/manage-surface-driver-and-firmware-updates.md
+++ /dev/null
@@ -1,160 +0,0 @@
----
-title: Manage and deploy Surface driver and firmware updates
-description: This article describes the available options to manage and deploy firmware and driver updates for Surface devices.
-ms.assetid: CD1219BA-8EDE-4BC8-BEEF-99B50C211D73
-ms.reviewer:
-manager: laurawi
-keywords: Surface, Surface Pro 3, firmware, update, device, manage, deploy, driver, USB
-ms.localizationpriority: medium
-ms.prod: w10
-ms.mktglfcycl: manage
-ms.pagetype: surface, devices
-ms.sitesec: library
-author: coveminer
-ms.author: v-jokai
-ms.topic: article
-ms.audience: itpro
----
-
-# Manage and deploy Surface driver and firmware updates
-
-How you manage Surface driver and firmware updates varies depending on your environment and organizational requirements. On Surface devices, firmware is exposed to the operating system as a driver and is visible in Device Manager, enabling device firmware and drivers to be automatically updated using Windows Update or Windows Update for Business. Although this simplified approach may be feasible for startups and small or medium-sized businesses, larger organizations typically need IT admins to distribute updates internally. This may involve comprehensive planning, application compatibility testing, piloting and validating updates, before final approval and distribution across the network.
-
-> [!NOTE]
-> This article is intended for technical support agents and IT professionals and applies to Surface devices only. If you're looking for help to install Surface updates or firmware on a home device, see [Update Surface firmware and Windows 10](https://support.microsoft.com/help/4023505).
-
-While enterprise-grade software distribution solutions continue to evolve, the business rationale for centrally managing updates remains the same: Maintain the security of Surface devices and keep them updated with the latest operating system and feature improvements. This is essential for sustaining a stable production environment and ensuring users aren't blocked from being productive. This article provides an overview of recommended tools and processes for larger organizations to accomplish these goals.
-
-## Central update management in commercial environments
-
-Microsoft has streamlined tools for managing devices – including driver and firmware updates -- into a single unified experience called [Microsoft Endpoint Manager admin center](https://devicemanagement.microsoft.com/) accessed from devicemanagement.microsoft.com.
-
-### Manage updates with Configuration Manager and Intune
-
-Microsoft Endpoint Configuration Manager allows you to synchronize and deploy Surface firmware and driver updates with the Configuration Manager client. Integration with Microsoft Intune lets you see all your managed, co-managed, and partner-managed devices in one place. This is the recommended solution for large organizations to manage Surface updates.
-
-For detailed steps, see the following resources:
-
-- [How to manage Surface driver updates in Configuration Manager.](https://support.microsoft.com/help/4098906/manage-surface-driver-updates-in-configuration-manager)
-- [Deploy applications with Configuration Manager](https://docs.microsoft.com/configmgr/apps/deploy-use/deploy-applications).
-- [Endpoint Configuration Manager documentation](https://docs.microsoft.com/configmgr/)
-
-
-### Manage updates with Microsoft Deployment Toolkit
-
-Included in Endpoint Configuration Manager, the Microsoft Deployment Toolkit (MDT) contains optional deployment tools that you may wish to use depending on your environment. These include the Windows Assessment and Deployment Kit (Windows ADK), Windows System Image Manager (Windows SIM), Deployment Image Servicing and Management (DISM), and User State Migration Tool (USMT). You can download the latest version of MDT from the [Microsoft Deployment Toolkit download page](https://www.microsoft.com/download/details.aspx?id=54259).
-
-For detailed steps, see the following resources:
-
-- [Microsoft Deployment Toolkit documentation](https://docs.microsoft.com/configmgr/mdt/)
-- [Deploy Windows 10 with the Microsoft Deployment Toolkit](https://docs.microsoft.com/windows/deployment/deploy-windows-mdt/deploy-windows-10-with-the-microsoft-deployment-toolkit)
-- [Deploy Windows 10 to Surface devices with Microsoft Deployment Toolkit](https://docs.microsoft.com/surface/deploy-windows-10-to-surface-devices-with-mdt)
-
-Surface driver and firmware updates are packaged as Windows Installer (*.msi) files. To deploy these Windows Installer packages, you can use Endpoint Configuration Manager or MDT. For information about selecting the correct .msi file for a device and operating system, refer to the guidance below about downloading .msi files.
-
-For instructions on how to deploy updates by using Endpoint Configuration Manager refer to [Deploy applications with Configuration Manager](https://docs.microsoft.com/configmgr/apps/deploy-use/deploy-applications). For instructions on how to deploy updates by using MDT, see [Deploy a Windows 10 image using MDT](https://docs.microsoft.com/windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt).
-
-
-**WindowsPE and Surface firmware and drivers**
-
-Endpoint Configuration Manager and MDT both use the Windows Preinstallation Environment (WindowsPE) during the deployment process. WindowsPE only supports a limited set of basic drivers such as those for network adapters and storage controllers. Drivers for Windows components that are not part of WindowsPE might produce errors. As a best practice, you can prevent such errors by configuring the deployment process to use only the required drivers during the WindowsPE phase.
-
-### Endpoint Configuration Manager
-
-Starting in Endpoint Configuration Manager, you can synchronize and deploy Microsoft Surface firmware and driver updates by using the Configuration Manager client. For additional information, see KB 4098906, [How to manage Surface driver updates in Configuration Manager](https://support.microsoft.com/help/4098906/manage-surface-driver-updates-in-configuration-manager).
-
-## Supported devices
-
-Downloadable .msi files are available for Surface devices from Surface Pro 2 and later. Information about .msi files for the newest Surface devices such as Surface Pro 7, Surface Pro X, and Surface Laptop 3 will be available from this page upon release.
-
-
-## Managing firmware with DFCI
-
-With Device Firmware Configuration Interface (DFCI) profiles built into Intune (now available in [public preview](https://docs.microsoft.com/intune/configuration/device-firmware-configuration-interface-windows)), Surface UEFI management extends the modern management stack down to the UEFI hardware level. DFCI supports zero-touch provisioning, eliminates BIOS passwords, provides control of security settings including boot options and built-in peripherals, and lays the groundwork for advanced security scenarios in the future. For more information, see:
-
-- [Intune management of Surface UEFI settings](https://docs.microsoft.com/surface/surface-manage-dfci-guide)
-- [Ignite 2019: Announcing remote management of Surface UEFI settings from Intune](https://techcommunity.microsoft.com/t5/Surface-IT-Pro-Blog/Ignite-2019-Announcing-remote-management-of-Surface-UEFI/ba-p/978333).
-
-## Best practices for update deployment processes
-
-To maintain a stable environment, it's strongly recommended to maintain parity with the most recent version of Windows 10. For best practice recommendations, see [Build deployment rings for Windows 10 updates](https://docs.microsoft.com/windows/deployment/update/waas-deployment-rings-windows-10-updates).
-
-## Downloadable Surface update packages
-
-Specific versions of Windows 10 have separate .msi files, each containing all required cumulative driver and firmware updates for Surface devices. Update packages may include some or all of the following components:
-
-- Wi-Fi and LTE
-- Video
-- Solid state drive
-- System aggregator module (SAM)
-- Battery
-- Keyboard controller
-- Embedded controller (EC)
-- Management engine (ME)
-- Unified extensible firmware interface (UEFI)
-
-
-### Downloading .msi files
-
-1. Browse to [Download drivers and firmware for Surface](https://support.microsoft.com/help/4023482/surface-download-drivers-and-firmware) on the Microsoft Download Center.
-2. Select the .msi file name that matches the Surface model and version of Windows. The .msi file name includes the minimum supported Windows build number required to install the drivers and firmware. For example, as shown in the following figure, to update a Surface Book 2 with build 18362 of Windows 10, choose **SurfaceBook2_Win10_18362_19.101.13994.msi.** For a Surface Book 2 with build 16299 of Windows 10, choose **SurfaceBook2_Win10_16299_1803509_3.msi**.
-
- 
-
- *Figure 1. Downloading Surface updates*
-
-
-### Surface .msi naming convention
-
-Since August 2019, .msi files have used the following naming convention:
-
-- *Product*_*Windows release*_*Windows build number*_*Version number*_*Revision of version number (typically zero)*.
-
-**Example**
-
-- SurfacePro6_Win10_18362_19.073.44195_0.msi
-
-This file name provides the following information:
-
-- **Product:** SurfacePro6
-- **Windows release:** Win10
-- **Build:** 18362
-- **Version:** 19.073.44195 – This shows the date and time that the file was created, as follows:
- - **Year:** 19 (2019)
- - **Month and week:** 073 (third week of July)
- - **Minute of the month:** 44195
-- **Revision of version:** 0 (first release of this version)
-
-### Legacy Surface .msi naming convention
-Legacy .msi files (files built before August 2019) followed the same overall naming formula but used a different method to derive the version number.
- ****
-**Example**
-
-- SurfacePro6_Win10_16299_1900307_0.msi
-
-This file name provides the following information:
-
-- **Product:** SurfacePro6
-- **Windows release:** Win10
-- **Build:** 16299
-- **Version:** 1900307 – This shows the date that the file was created and its position in the release sequence, as follows:
- - **Year:** 19 (2019)
- - **Number of release:** 003 (third release of the year)
- - **Product version number:** 07 (Surface Pro 6 is officially the seventh version of Surface Pro)
-- **Revision of version:** 0 (first release of this version)
-
-
-
-## Learn more
-
-- [Download drivers and firmware for Surface](https://support.microsoft.com/help/4023482/surface-download-drivers-and-firmware)
-- [How to manage Surface driver updates in Configuration Manager.](https://support.microsoft.com/help/4098906/manage-surface-driver-updates-in-configuration-manager)
-- [Deploy applications with Configuration Manager](https://docs.microsoft.com/configmgr/apps/deploy-use/deploy-applications).
-- [Endpoint Configuration Manager documentation](https://docs.microsoft.com/configmgr/)
-- [Microsoft Deployment Toolkit documentation](https://docs.microsoft.com/configmgr/mdt/)
-- [Deploy Windows 10 with the Microsoft Deployment Toolkit](https://docs.microsoft.com/windows/deployment/deploy-windows-mdt/deploy-windows-10-with-the-microsoft-deployment-toolkit)
-- [Deploy Windows 10 to Surface devices with Microsoft Deployment Toolkit](https://docs.microsoft.com/surface/deploy-windows-10-to-surface-devices-with-mdt)
-- [Intune management of Surface UEFI settings](https://docs.microsoft.com/surface/surface-manage-dfci-guide)
-- [Ignite 2019: Announcing remote management of Surface UEFI settings from Intune](https://techcommunity.microsoft.com/t5/Surface-IT-Pro-Blog/Ignite-2019-Announcing-remote-management-of-Surface-UEFI/ba-p/978333).
-- [Build deployment rings for Windows 10 updates](https://docs.microsoft.com/windows/deployment/update/waas-deployment-rings-windows-10-updates)
-
diff --git a/devices/surface/manage-surface-uefi-settings.md b/devices/surface/manage-surface-uefi-settings.md
deleted file mode 100644
index c5f41821d3..0000000000
--- a/devices/surface/manage-surface-uefi-settings.md
+++ /dev/null
@@ -1,221 +0,0 @@
----
-title: Manage Surface UEFI settings
-description: Use Surface UEFI settings to enable or disable devices or components, configure security settings, and adjust Surface device boot settings.
-keywords: firmware, security, features, configure, hardware
-ms.localizationpriority: medium
-ms.prod: w10
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.pagetype: devices, surface
-author: coveminer
-ms.author: v-jokai
-ms.topic: article
-ms.reviewer:
-manager: laurawi
----
-
-# Manage Surface UEFI settings
-
-All current and future generations of Surface devices use a unique Unified Extensible Firmware Interface (UEFI) engineered by Microsoft specifically for these devices. Surface UEFI settings provide the ability to enable or disable built-in devices and components, protect UEFI settings from being changed, and adjust the Surface device boot settings.
-
-## Support for cloud-based management
-
-With Device Firmware Configuration Interface (DFCI) profiles built into Microsoft Intune (now available in public preview), Surface UEFI management extends the modern management stack down to the UEFI hardware level. DFCI supports zero-touch provisioning, eliminates BIOS passwords, provides control of security settings including boot options and built-in peripherals, and lays the groundwork for advanced security scenarios in the future. DFCI is currently available for Surface Pro 7, Surface Pro X, and Surface Laptop 3. For more information, refer to [Intune management of Surface UEFI settings](surface-manage-dfci-guide.md).
-
-## Open Surface UEFI menu
-
-To adjust UEFI settings during system startup:
-
-1. Shut down your Surface and wait about 10 seconds to make sure it's off.
-2. Press and hold the **Volume-up** button and - at the same time - press and release the **Power button.**
-3. As the Microsoft or Surface logo appears on your screen, continue to hold the **Volume-up** button until the UEFI screen appears.
-
-## UEFI PC information page
-
-The PC information page includes detailed information about your Surface device:
-
-- **Model** – Your Surface device’s model will be displayed here, such as Surface Book 2 or Surface Pro 7. The exact configuration of your device is not shown, (such as processor, disk size, or memory size).
-- **UUID** – This Universally Unique Identification number is specific to your device and is used to identify the device during deployment or management.
-
-- **Serial Number** – This number is used to identify this specific Surface device for asset tagging and support scenarios.
-- **Asset Tag** – The asset tag is assigned to the Surface device with the [Asset Tag Tool](https://docs.microsoft.com/surface/assettag).
-
-You will also find detailed information about the firmware of your Surface device. Surface devices have several internal components that each run different versions of firmware. The firmware version of each of the following devices is displayed on the **PC information** page (as shown in Figure 1):
-
-- System UEFI
-
-- SAM Controller
-
-- Intel Management Engine
-
-- System Embedded Controller
-
-- Touch Firmware
-
-
-
-*Figure 1. System information and firmware version information*
-
-You can find up-to-date information about the latest firmware version for your Surface device in the [Surface Update History](https://www.microsoft.com/surface/support/install-update-activate/surface-update-history) for your device.
-
-## UEFI Security page
-
-
-
-*Figure 2. Configure Surface UEFI security settings*
-
-The Security page allows you to set a password to protect UEFI settings. This password must be entered when you boot the Surface device to UEFI. The password can contain the following characters (as shown in Figure 3):
-
-- Uppercase letters: A-Z
-
-- Lowercase letters: a-z
-
-- Numbers: 1-0
-
-- Special characters: !@#$%^&*()?<>{}[]-_=+|.,;:’`”
-
-The password must be at least 6 characters and is case sensitive.
-
-
-
-*Figure 3. Add a password to protect Surface UEFI settings*
-
-On the Security page you can also change the configuration of Secure Boot on your Surface device. Secure Boot technology prevents unauthorized boot code from booting on your Surface device, which protects against bootkit and rootkit-type malware infections. You can disable Secure Boot to allow your Surface device to boot third-party operating systems or bootable media. You can also configure Secure Boot to work with third-party certificates, as shown in Figure 4. Read more about [Secure Boot](https://msdn.microsoft.com/windows/hardware/commercialize/manufacture/desktop/secure-boot-overview) in the TechNet Library.
-
-
-
-*Figure 4. Configure Secure Boot*
-
-Depending on your device, you may also be able to see if your TPM is enabled or disabled. If you do not see the **Enable TPM** setting, open tpm.msc in Windows to check the status, as shown in Figure 5. The TPM is used to authenticate encryption for your device’s data with BitLocker. To learn more, see [BitLocker overview](https://docs.microsoft.com/windows/security/information-protection/bitlocker/bitlocker-overview).
-
-
-
-*Figure 5. TPM console*
-
-
-## UEFI menu: Devices
-
-The Devices page allows you to enable or disable specific devices and components including:
-
-- Docking and USB Ports
-
-- MicroSD or SD Card Slot
-
-- Rear Camera
-
-- Front Camera
-
-- Infrared (IR) Camera
-
-- Wi-Fi and Bluetooth
-
-- Onboard Audio (Speakers and Microphone)
-
-Each device is listed with a slider button that you can move to **On** (enabled) or **Off** (disabled) position, as shown in Figure 6.
-
-
-
-*Figure 6. Enable and disable specific devices*
-
-## UEFI menu: Boot configuration
-
-The Boot Configuration page allows you to change the order of your boot devices as well as enable or disable boot of the following devices:
-
-- Windows Boot Manager
-
-- USB Storage
-
-- PXE Network
-
-- Internal Storage
-
-You can boot from a specific device immediately, or you can swipe left on that device’s entry in the list using the touchscreen. You can also boot immediately to a USB device or USB Ethernet adapter when the Surface device is powered off by pressing the **Volume Down** button and the **Power** button simultaneously.
-
-For the specified boot order to take effect, you must set the **Enable Alternate Boot Sequence** option to **On**, as shown in Figure 7.
-
-
-
-*Figure 7. Configure the boot order for your Surface device*
-
-You can also turn on and off IPv6 support for PXE with the **Enable IPv6 for PXE Network Boot** option, for example when performing a Windows deployment using PXE where the PXE server is configured for IPv4 only.
-
-## UEFI menu: Management
-The Management page allows you to manage use of Zero Touch UEFI Management and other features on eligible devices including Surface Pro 7, Surface Pro X, and Surface Laptop 3.
-
-
-*Figure 8. Manage access to Zero Touch UEFI Management and other features*
-
-
-Zero Touch UEFI Management lets you remotely manage UEFI settings by using a device profile within Intune called Device Firmware Configuration Interface (DFCI). If you do not configure this setting, the ability to manage eligible devices with DFCI is set to **Ready**. To prevent DFCI, select **Opt-Out**.
-
-> [!NOTE]
-> The UEFI Management settings page and use of DFCI is only available on Surface Pro 7, Surface Pro X, and Surface Laptop 3.
-
-For more information, refer to [Intune management of Surface UEFI settings](surface-manage-dfci-guide.md).
-
-## UEFI menu: Exit
-
-Use the **Restart Now** button on the **Exit** page to exit UEFI settings, as shown in Figure 9.
-
-
-
-*Figure 9. Click Restart Now to exit Surface UEFI and restart the device*
-
-## Surface UEFI boot screens
-
-When you update Surface device firmware, by using either Windows Update or manual installation, the updates are not applied immediately to the device, but instead during the next reboot cycle. You can find out more about the Surface firmware update process in [Manage Surface driver and firmware updates](https://docs.microsoft.com/surface/manage-surface-pro-3-firmware-updates). The progress of the firmware update is displayed on a screen with progress bars of differing colors to indicate the firmware for each component. Each component’s progress bar is shown in Figures 9 through 18.
-
-
-
-*Figure 10. The Surface UEFI firmware update displays a blue progress bar*
-
-
-
-*Figure 11. The System Embedded Controller firmware update displays a green progress bar*
-
-
-
-*Figure 12. The SAM Controller firmware update displays an orange progress bar*
-
-
-
-*Figure 13. The Intel Management Engine firmware update displays a red progress bar*
-
-
-
-*Figure 14. The Surface touch firmware update displays a gray progress bar*
-
-
-
-*Figure 15. The Surface KIP firmware update displays a light green progress bar*
-
-
-
-*Figure 16 The Surface ISH firmware update displays a light pink progress bar*
-
-
-
-*Figure 17. The Surface Trackpad firmware update displays a pink progress bar*
-
-
-
-*Figure 18. The Surface TCON firmware update displays a light gray progress bar*
-
-
-
-
-*Figure 19. The Surface TPM firmware update displays a purple progress bar*
-
-
->[!NOTE]
->An additional warning message that indicates Secure Boot is disabled is displayed, as shown in Figure 19.
-
-
-
-*Figure 20. Surface boot screen that indicates Secure Boot has been disabled in Surface UEFI settings*
-
-## Related topics
-
-- [Intune management of Surface UEFI settings](surface-manage-dfci-guide.md)
-
-- [Surface Enterprise Management Mode](surface-enterprise-management-mode.md)
diff --git a/devices/surface/microsoft-surface-brightness-control.md b/devices/surface/microsoft-surface-brightness-control.md
deleted file mode 100644
index f0e6c5d221..0000000000
--- a/devices/surface/microsoft-surface-brightness-control.md
+++ /dev/null
@@ -1,81 +0,0 @@
----
-title: Surface Brightness Control
-description: This topic describes how you can use the Surface Brightness Control app to manage display brightness in point-of-sale and kiosk scenarios.
-ms.prod: w10
-ms.mktglfcycl: manage
-ms.pagetype: surface, devices
-ms.sitesec: library
-author: coveminer
-ms.author: v-jokai
-ms.topic: article
-ms.reviewer: hachidan
-manager: laurawi
-ms.localizationpriority: medium
-ms.audience: itpro
----
-
-# Surface Brightness Control
-
-When deploying Surface devices in point of sale or other “always-on”
-kiosk scenarios, you can optimize power management using the new Surface
-Brightness Control app.
-
-Available for download with [Surface Tools for IT](https://www.microsoft.com/download/details.aspx?id=46703).
-Surface Brightness Control is designed to help reduce thermal load and lower the overall carbon footprint for deployed Surface devices.
-If you plan to get only this tool from the download page, select the file **Surface_Brightness_Control_v1.16.137.0.msi** in the available list.
-The tool automatically dims the screen when not in use and includes the following configuration options:
-
-- Period of inactivity before dimming the display.
-
-- Brightness level when dimmed.
-
-- Maximum brightness level when in use.
-
-**To run Surface Brightness Control:**
-
-- Install surfacebrightnesscontrol.msi on the target device and Surface Brightness Control
- will begin working immediately.
-
-## Configuring Surface Brightness Control
-
-You can adjust the default values via the Windows Registry. For more
-information about using the Windows Registry, refer to the [Registry
-documentation](https://docs.microsoft.com/windows/desktop/sysinfo/registry).
-
-1. Run regedit from a command prompt to open the Windows Registry
- Editor.
-
- - Computer\HKEY\_LOCAL\_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Surface\Surface
- Brightness Control\
-
- If you're running an older version of Surface Brightness control, run the following command instead:
-
- - Computer\HKEY\_LOCAL\_MACHINE\SOFTWARE\Microsoft\Surface\Surface
- Brightness Control\
-
-
-| Registry Setting | Data| Description
-|-----------|------------|---------------
-| Brightness Control Enabled | Default: 01 Option: 01, 00 Type: REG_BINARY | This setting allows you to turn Surface Brightness Control on or off. To disable Surface Brightness Control, set the value to 00. If you do not configure this setting, Surface Brightness Control is on. |
-| Brightness Control On Power Enabled| Default: 01 Options: 01, 00 Type: REG_BINARY | This setting allows you to turn off Surface Brightness Control when the device is directly connected to power. To disable Surface Brightness Control when power is plugged in, set the value to 00. If you do not configure this setting, Surface Brightness Control is on. |
-| Dimmed Brightness | Default: 20 Option: Range of 0-100 percent of screen brightness Data Type: Positive integer Type: REG_DWORD | This setting allows you to manage brightness range during periods of inactivity. If you do not configure this setting, the brightness level will drop to 20 percent of full brightness after 30 seconds of inactivity. |
-Full Brightness | Default: 100 Option: Range of 0-100 percent of screen brightness Data Type: Positive integer Type: REG_DWORD | This setting allows you to manage the maximum brightness range for the device. If you do not configure this setting, the maximum brightness range is 100 percent.|
-| Inactivity Timeout| Default: 30 seconds Option: Any numeric value Data Type: Integer Type: REG_DWORD | This setting allows you to manage the period of inactivity before dimming the device. If you do not configure this setting, the inactivity timeout is 30 seconds.|
-| Telemetry Enabled | Default: 01 Option: 01, 00 Type: REG_BINARY | This setting allows you to manage the sharing of app usage information to improve software and provide better user experience. To disable telemetry, set the value to 00. If you do not configure this setting, telemetry information is shared with Microsoft in accordance with the [Microsoft Privacy Statement](https://privacy.microsoft.com/privacystatement). |
-
-## Changes and updates
-
-### Version 1.16.137
-*Release Date: 22 October 2019*
-This version of Surface Brightness Control adds support for the following:
--Recompiled for x86, adding support for Surface Pro 7, Surface Pro X, and Surface Laptop 3.
-
-### Version 1.12.239.0
-*Release Date: 26 April 2019*
-This version of Surface Brightness Control adds support for the following:
-- Touch delay fixes.
-
-
-## Related topics
-
-- [Battery limit setting](battery-limit.md)
diff --git a/devices/surface/microsoft-surface-data-eraser.md b/devices/surface/microsoft-surface-data-eraser.md
deleted file mode 100644
index 0cbf9dac52..0000000000
--- a/devices/surface/microsoft-surface-data-eraser.md
+++ /dev/null
@@ -1,242 +0,0 @@
----
-title: Microsoft Surface Data Eraser (Surface)
-description: Find out how the Microsoft Surface Data Eraser tool can help you securely wipe data from your Surface devices.
-ms.assetid: 8DD3F9FE-5458-4467-BE26-E9200341CF10
-ms.reviewer: hachidan
-manager: laurawi
-ms.localizationpriority: medium
-keywords: tool, USB, data, erase
-ms.prod: w10
-ms.mktglfcycl: manage
-ms.pagetype: surface, devices, security
-ms.sitesec: library
-author: coveminer
-ms.author: v-jokai
-ms.topic: article
-ms.audience: itpro
----
-
-# Microsoft Surface Data Eraser
-
-
-Find out how the Microsoft Surface Data Eraser tool can help you securely wipe data from your Surface devices.
-
-[Microsoft Surface Data Eraser](https://www.microsoft.com/download/details.aspx?id=46703) is a tool that boots from a USB stick and allows you to perform a secure wipe of all data from a compatible Surface device. A Microsoft Surface Data Eraser USB stick requires only the ability to boot from USB. The USB stick is easy to create by using the provided wizard, the Microsoft Surface Data Eraser wrapper, and is easy to use with a simple graphic interface, no command line needed. To learn more about the data wiping capabilities and practices Microsoft uses during the service process for Surface, see [Protecting your data if you send your Surface in for service](https://www.microsoft.com/surface/support/security-sign-in-and-accounts/data-wiping-policy).
-
->[!IMPORTANT]
->Microsoft Surface Data Eraser uses the NVM Express (NVMe) format command to erase data as authorized in [NIST Special Publication 800-88 Revision 1](http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-88r1.pdf).
-
-Compatible Surface devices include:
-
-* Surface Pro 7
-* Surface Pro X
-* Surface Laptop 3
-* Surface Pro 6
-* Surface Laptop 2
-* Surface Go
-* Surface Book 2
-* Surface Pro with LTE Advanced (Model 1807)
-* Surface Pro (Model 1796)
-* Surface Laptop
-* Surface Studio
-* Surface Studio 2
-* Surface Book
-* Surface Pro 4
-* Surface 3 LTE
-* Surface 3
-* Surface Pro 3
-* Surface Pro 2
-
-Some scenarios where Microsoft Surface Data Eraser can be helpful include:
-
-- Prepare a Surface device to be sent for repair
-
-- Decommission a Surface device to be removed from corporate or organizational use
-
-- Repurpose a Surface device for use in a new department or for use by a new user
-
-- Standard practice when performing reimaging for devices used with sensitive data
-
->[!NOTE]
->Third-party devices, Surface devices running Windows RT (including Surface and Surface 2), and Surface Pro are not compatible with Microsoft Surface Data Eraser.
-
->[!NOTE]
->Because the ability to boot to USB is required to run Microsoft Surface Data Eraser, if the device is not configured to boot from USB or if the device is unable to boot or POST successfully, the Microsoft Surface Data Eraser tool will not function.
-
->[!NOTE]
->Surface Data Eraser on Surface Studio and Surface Studio 2 can take up to 6 minutes to boot into WinPE before disk erasure can occur.
-
-
-## How to create a Microsoft Surface Data Eraser USB stick
-
-
-To create a Microsoft Surface Data Eraser USB stick, first install the Microsoft Surface Data Eraser setup tool from the Microsoft Download Center using the link provided at the beginning of this article. You do not need a Surface device to *create* the USB stick. After you have downloaded the installation file to your computer, follow these steps to install the Microsoft Surface Data Eraser creation tool:
-
-1. Run the DataEraserSetup.msi installation file that you downloaded from the [Microsoft Download Center](https://www.microsoft.com/download/details.aspx?id=46703).
-
-2. Select the check box to accept the terms of the license agreement, and then click **Install**.
-
-3. Click **Finish** to close the Microsoft Surface Data Eraser setup window.
-
-After the creation tool is installed, follow these steps to create a Microsoft Surface Data Eraser USB stick. Before you begin these steps, ensure that you have a USB 3.0 stick that is 4 GB or larger connected to the computer.
-
-1. Start Microsoft Surface Data Eraser from the Start menu or Start screen.
-
-2. Click **Build** to begin the Microsoft Surface Data Eraser USB creation process.
-
-3. Click **Start** to acknowledge that you have a USB stick of at least 4 GB connected, as shown in Figure 1.
-
- 
-
- *Figure 1. Start the Microsoft Surface Data Eraser tool*
-4. Choose **x64** for most Surface devices or **ARM64** for Surface Pro X from the **Architecture Selection** page, as shown in Figure 2. Select **Continue**.
-
- 
- *Figure 2. Select device architecture*
-
-
-4. Select the USB drive of your choice from the **USB Thumb Drive Selection** page as shown in Figure 3, and then click **Start** to begin the USB creation process. The drive you select will be formatted and any existing data on this drive will be lost.
-
- >[!NOTE]
- >If the Start button is disabled, check that your removable drive has a total capacity of at least 4 GB.
-
- 
-
- *Figure 3. USB thumb drive selection*
-
-5. After the creation process is finished, the USB drive has been formatted and all binaries are copied to the USB drive. Click **Success**.
-
-6. When the **Congratulations** screen is displayed, you can eject and remove the thumb drive. This thumb drive is now ready to be inserted into a Surface device, booted from, and wipe any data on the device. Click **Complete** to finish the USB creation process, as shown in Figure 4.
-
- 
-
- *Figure 4. Complete the Microsoft Surface Data Eraser USB creation process*
-
-7. Click **X** to close Microsoft Surface Data Eraser.
-
-## How to use a Microsoft Surface Data Eraser USB stick
-
-
-After you create a Microsoft Surface Data Eraser USB stick, you can boot a supported Surface device from the USB stick by following this procedure:
-
-1. Insert the bootable Microsoft Surface Data Eraser USB stick into the supported Surface device.
-
-2. Boot your Surface device from the Microsoft Surface Data Eraser USB stick. To boot your device from the USB stick follow these steps:
-
- a. Turn off your Surface device.
-
- b. Press and hold the **Volume Down** button.
-
- c. Press and release the **Power** button.
-
- d. Release the **Volume Down** button.
-
- >[!NOTE]
- >If your device does not boot to USB using these steps, you may need to turn on the **Enable Alternate Boot Sequence** option in Surface UEFI. You can read more about Surface UEFI boot configuration in [Manage Surface UEFI Settings](https://technet.microsoft.com/itpro/surface/manage-surface-uefi-settings).
-
-3. When the Surface device boots, a **SoftwareLicenseTerms** text file is displayed, as shown in Figure 5.
-
- 
-
- *Figure 5. Booting the Microsoft Surface Data Eraser USB stick*
-
-4. Read the software license terms, and then close the Notepad file.
-
-5. Accept or decline the software license terms by typing **Accept** or **Decline**. You must accept the license terms to continue.
-
-6. The Microsoft Surface Data Eraser script detects the storage devices that are present in your Surface device and displays the details of the native storage device. To continue, press **Y** (this action runs Microsoft Surface Data Eraser and removes all data from the storage device) or press **N** (this action shuts down the device without removing data).
-
- >[!NOTE]
- >The Microsoft Surface Data Eraser tool will delete all data, including Windows operating system files required to boot the device, in a secure and unrecoverable way. To boot a Surface device that has been wiped with Microsoft Surface Data Eraser, you will first need to reinstall the Windows operating system. To remove data from a Surface device without removing the Windows operating system, you can use the **Reset your PC** function. However, this does not prevent your data from being recovered with forensic or data recovery capabilities. See [Recovery options in Windows 10](https://support.microsoft.com/help/12415/windows-10-recovery-options) for more information.
-
- 
-
- *Figure 6. Partition to be erased is displayed in Microsoft Surface Data Eraser*
-
-7. If you pressed **Y** in step 6, due to the destructive nature of the data erasure process, an additional dialog box is displayed to confirm your choice.
-
-8. Click the **Yes** button to continue erasing data on the Surface device.
-
- >[!NOTE]
- >When you run Surface Data Eraser on the Surface Data Eraser USB drive, a log file is generated in the **SurfaceDataEraserLogs** folder.
-
-## Changes and updates
-
-Microsoft Surface Data Eraser is periodically updated by Microsoft. For information about the changes provided in each new version, see the following:
-
-### 3.28.137
-*Release Date: 11 Nov 2019*
-This version of Surface Data Eraser:
-
-- Includes bug fixes
-
-### Version 3.21.137
-*Release Date: 21 Oct 2019*
-This version of Surface Data Eraser is compiled for x86 and adds support for the following devices:
-
-- Supports Surface Pro 7, Surface Pro X, and Surface Laptop 3
-
-### Version 3.2.78.0
-*Release Date: 4 Dec 2018*
-
-This version of Surface Data Eraser:
-
-- Includes bug fixes
-
-
-### Version 3.2.75.0
-*Release Date: 12 November 2018*
-
-This version of Surface Data Eraser:
-
-- Adds support to Surface Studio 2
-- Fixes issues with SD card
-
-### Version 3.2.69.0
-*Release Date: 12 October 2018*
-
-This version of Surface Data Eraser adds support for the following:
-
-- Surface Pro 6
-- Surface Laptop 2
-
-### Version 3.2.68.0
-This version of Microsoft Surface Data Eraser adds support for the following:
-
-- Surface Go
-
-
-### Version 3.2.58.0
-This version of Microsoft Surface Data Eraser adds support for the following:
-
-- Additional storage devices (drives) for Surface Pro and Surface Laptop devices
-
-
-### Version 3.2.46.0
-This version of Microsoft Surface Data Eraser adds support for the following:
-
-- Surface Pro with LTE Advanced
-
-
-### Version 3.2.45.0
-
-This version of Microsoft Surface Data Eraser adds support for the following:
-
-- Surface Book 2
-
-- Surface Pro 1TB
-
- >[!NOTE]
- >Surface Data Eraser v3.2.45.0 and above can be used to restore Surface Pro or Surface Laptop devices with the 1TB storage option in the scenario that the device shows two separate 512GB volumes or encounters errors when attempting to deploy or install Windows 10. See [Surface Pro Model 1796 and Surface Laptop 1TB display two drives](https://support.microsoft.com/help/4046105/surface-pro-model-1796-and-surface-laptop-1tb-display-two-drives) for more information.
-
-
-### Version 3.2.36.0
-
-This version of Microsoft Surface Data Eraser adds support for the following:
-
-- Surface Pro
-
-- Surface Laptop
-
->[!NOTE]
->The Microsoft Surface Data Eraser USB drive creation tool is unable to run on Windows 10 S. To wipe a Surface Laptop running Windows 10 S, you must first create the Microsoft Surface Data Eraser USB drive on another computer with Windows 10 Pro or Windows 10 Enterprise.
diff --git a/devices/surface/microsoft-surface-deployment-accelerator.md b/devices/surface/microsoft-surface-deployment-accelerator.md
deleted file mode 100644
index 6c25746e2a..0000000000
--- a/devices/surface/microsoft-surface-deployment-accelerator.md
+++ /dev/null
@@ -1,144 +0,0 @@
----
-title: Microsoft Surface Deployment Accelerator (Surface)
-description: Microsoft Surface Deployment Accelerator provides a quick and simple deployment mechanism for organizations to reimage Surface devices.
-ms.assetid: E7991E90-4AAE-44B6-8822-58BFDE3EADE4
-ms.reviewer: hachidan
-manager: laurawi
-ms.localizationpriority: medium
-keywords: deploy, install, tool
-ms.prod: w10
-ms.mktglfcycl: deploy
-ms.pagetype: surface, devices
-ms.sitesec: library
-author: coveminer
-ms.author: v-jokai
-ms.topic: article
-ms.audience: itpro
----
-
-# Microsoft Surface Deployment Accelerator
-
-Microsoft Surface Deployment Accelerator (SDA) automates the creation and configuration of a Microsoft recommended deployment experience by using free Microsoft deployment tools.
-
-> [!NOTE]
-> SDA is not supported on Surface Pro 7, Surface Pro X, and Surface Laptop 3. For more information refer to [Deploy Surface devices](deploy.md).
-
-SDA is built on the powerful suite of deployment tools available from Microsoft including the Windows Assessment and Deployment Kit (ADK), the Microsoft Deployment Toolkit (MDT), and Windows Deployment Services (WDS). The resulting deployment share encompasses the recommended best practices for managing drivers during deployment and automating image creation and can serve as a starting point upon which you build your own customized deployment solution.
-
-**Download Microsoft Surface Deployment Accelerator**
-
-You can download the installation files for SDA from the Microsoft Download Center. To download the installation files:
-
-1. Go to the [Surface Tools for IT](https://www.microsoft.com/download/details.aspx?id=46703) page on the Microsoft Download Center.
-
-2. Click the **Download** button, select the **Surface\_Deployment\_Accelerator\_xxxx.msi** file, and then click **Next**.
-
-## Microsoft Surface Deployment Accelerator prerequisites
-
-
-Before you install SDA, your environment must meet the following prerequisites:
-
-- SDA must be installed on Windows Server 2012 R2 or later
-
-- PowerShell Script Execution Policy must be set to **Unrestricted**
-
-- DHCP and DNS must be enabled on the network where the Windows Server 2012 R2 environment is connected
-
-- To download Surface drivers and apps automatically the Windows Server 2012 R2 environment must have Internet access and Internet Explorer Enhanced Security Configuration must be disabled
-
-- To support network boot, the Windows Server 2012 R2 environment must have Windows Deployment Services installed and configured to respond to PXE requests
-
-- Access to Windows source files or installation media is required when you prepare a deployment with SDA
-
-- At least 6 GB of free space for each version of Windows you intend to deploy
-
-## How Microsoft Surface Deployment Accelerator works
-
-
-As you progress through the SDA wizard, you will be asked some basic questions about how your deployment solution should be configured. As you select the desired Surface models to be supported and apps to be installed (see Figure 1), the wizard will prepare scripts that download, install, and configure everything needed to perform a complete deployment and capture of a reference image. By using the network boot (PXE) capabilities of Windows Deployment Services (WDS), the resulting solution enables you to boot a Surface device from the network and perform a clean deployment of Windows.
-
-
-
-*Figure 1. Select desired apps and drivers*
-
-When the SDA completes, you can use the deployment share to deploy over the network immediately. Simply boot your Surface device from the network using a Surface Ethernet Adapter and select the Surface deployment share you created with the SDA wizard. Select the **1- Deploy Microsoft Surface** task sequence and the wizard will walk you through an automated deployment of Windows to your Surface device.
-
-You can modify the task sequence in the MDT Deployment Workbench to [include your own apps](https://technet.microsoft.com/itpro/windows/deploy/deploy-a-windows-10-image-using-mdt#sec04), or to [pause the automated installation routine](https://blogs.technet.microsoft.com/mniehaus/2009/06/26/mdt-2010-new-feature-3-suspend-and-resume-a-lite-touch-task-sequence/). While the installation is paused, you can make changes to customize your reference image. After the image is captured, you can configure a deployment task sequence and distribute this custom configuration by using the same network boot capabilities as before.
-
->[!NOTE]
->With SDA v1.9.0258, Surface Pro 3, Surface Pro 4, and Surface Book are supported for Windows 10 deployment, and Surface Pro 3 is supported for Windows 8.1 deployment.
-
-
-
-## Use Microsoft Surface Deployment Accelerator without an Internet connection
-
-
-For environments where the SDA server will not be able to connect to the Internet, the required Surface files can be downloaded separately. To specify a local source for Surface driver and app files, select the **Copy from a local directory** option and specify the location of your downloaded files (see Figure 2). All of the driver and app files for your selected choices must be placed in the specified folder.
-
-
-
-*Figure 2. Specify a local source for Surface driver and app files*
-
-You can find a full list of available driver downloads at [Manage and deploy Surface driver and firmware updates](manage-surface-driver-and-firmware-updates.md)
-
->[!NOTE]
->Downloaded files do not need to be extracted. The downloaded files can be left as .zip files as long as they are stored in one folder.
-
->[!NOTE]
->Using files from a local directory is not supported when including Office 365 in your deployment share. To include Office 365 in your deployment share, select the **Download from the Internet** check box.
-
-## Changes and updates
-
-SDA is periodically updated by Microsoft. For instructions on how these features are used, see [Step-by-Step: Microsoft Surface Deployment Accelerator](https://technet.microsoft.com/itpro/surface/step-by-step-surface-deployment-accelerator).
-
->[!NOTE]
->To install a newer version of SDA on a server with a previous version of SDA installed, you only need to run the installation file for the new version of SDA. The installer will handle the upgrade process automatically. If you used SDA to create a deployment share prior to the upgrade and want to use new features of the new version of SDA, you will need to create a new deployment share. SDA does not support upgrades of an existing deployment share.
-
-### Version 2.8.136.0
-This version of SDA supports deployment of the following:
-* Surface Book 2
-* Surface Laptop
-* Surface Pro LTE
-
-### Version 2.0.8.0
-This version of SDA supports deployment of the following:
-* Surface Pro
-
->[!NOTE]
->SDA version 2.0.8.0 includes support only for Surface Pro, and does not support other Surface devices such as Surface Pro 4 or Surface Book. To deploy these devices, please continue to use SDA version 1.96.0405.
-
-### Version 1.96.0405
-This version of SDA adds support for the following:
-* Microsoft Deployment Toolkit (MDT) 2013 Update 2
-* Office 365 Click-to-Run
-* Surface 3 and Surface 3 LTE
-* Reduced Windows Assessment and Deployment Kit (Windows ADK) footprint, only the following Windows ADK components are installed:
- * Deployment tools
- * Windows Preinstallation Environment (WinPE)
- * User State Migration Tool (USMT)
-
-### Version 1.90.0258
-This version of SDA adds support for the following:
-* Surface Book
-* Surface Pro 4
-* Windows 10
-
-### Version 1.90.0000
-This version of SDA adds support for the following:
-* Local driver and app files can be used to create a deployment share without access to the Internet
-
-### Version 1.70.0000
-This version is the original release of SDA. This version of SDA includes support for:
-* MDT 2013 Update 1
-* Windows ADK
-* Surface Pro 3
-* Windows 8.1
-
-
-## Related topics
-
-[Step by step: Surface Deployment Accelerator](step-by-step-surface-deployment-accelerator.md)
-
-[Using the Surface Deployment Accelerator deployment share](using-the-sda-deployment-share.md)
-
-
diff --git a/devices/surface/step-by-step-surface-deployment-accelerator.md b/devices/surface/step-by-step-surface-deployment-accelerator.md
deleted file mode 100644
index e10b8209c9..0000000000
--- a/devices/surface/step-by-step-surface-deployment-accelerator.md
+++ /dev/null
@@ -1,410 +0,0 @@
----
-title: Step by step Surface Deployment Accelerator (Surface)
-description: This article shows you how to install Microsoft Surface Deployment Accelerator (SDA), configure a deployment share for the deployment of Windows to Surface devices, and perform a deployment to Surface devices.
-ms.assetid: A944FB9C-4D81-4868-AFF6-B9D1F5CF1032
-ms.reviewer:
-manager: laurawi
-ms.localizationpriority: medium
-keywords: deploy, configure
-ms.prod: w10
-ms.mktglfcycl: deploy
-ms.pagetype: surface, devices
-ms.sitesec: library
-author: coveminer
-ms.author: v-jokai
-ms.topic: article
-ms.date: 10/31/2019
----
-
-# Step by step: Surface Deployment Accelerator
-
-This article shows you how to install Microsoft Surface Deployment Accelerator (SDA), configure a deployment share for the deployment of Windows to Surface devices, and perform a deployment to Surface devices. This article also contains instructions on how to perform these tasks without an Internet connection or without support for Windows Deployment Services network boot (PXE).
-
-> [!NOTE]
-> SDA is not supported on Surface Pro 7, Surface Pro X, and Surface Laptop 3. For more information refer to [Deploy Surface devices](deploy.md).
-
-## How to install Surface Deployment Accelerator
-
-For information about prerequisites and instructions for how to download and install SDA, see [Microsoft Surface Deployment Accelerator](microsoft-surface-deployment-accelerator.md).
-
-1. Download SDA, which is included in [Surface Tools for IT](https://www.microsoft.com/download/details.aspx?id=46703) on the Microsoft Download Center.
-
-2. Run the SDA installation file, named **Surface\_Deployment\_Accelerator\_*xxxx*.msi**, where *xxxx* is the current version number.
-
-3. Accept the End User License Agreement (EULA) by selecting the check box, and then click **Install**, as shown in Figure 1.
-
- 
-
- *Figure 1. SDA setup*
-
-4. Click **Finish** to complete the installation of SDA.
-
-The tool installs in the SDA program group, as shown in Figure 2.
-
-
-
-*Figure 2. The SDA program group and icon*
-
->[!NOTE]
->At this point, the tool has not yet prepared any deployment environment or downloaded any materials from the Internet.
-
-## Create a deployment share
-
-The following steps show you how to create a deployment share for Windows 10 that supports Surface 3, Surface Pro 3, Surface Pro 4, Surface Book, the Surface Firmware Tool, the Surface Asset Tag Tool, and Office 365. As you follow the steps below, make the selections that are applicable for your organization. For example, you could choose to deploy Windows 10 to Surface Book only, without any of the Surface apps.
-
->[!NOTE]
->SDA lets you create deployment shares for both Windows 8.1 and Windows 10 deployments, but you can only create a single deployment share at a time. Therefore, to create both Windows 8.1 and Windows 10 deployment shares, you will need to run the tool twice.
-
-1. Open the SDA wizard by double-clicking the icon in the **Surface Deployment Accelerator** program group on the Start screen.
-
-2. On the **Welcome** page, click **Next** to continue.
-
-3. On the **Verify System** page, the SDA wizard verifies the prerequisites required for an SDA deployment share. This process also checks for the presence of the Windows Assessment and Deployment Kit (Windows ADK) for Windows 10 and the Microsoft Deployment Toolkit (MDT) 2013 Update 2. If these tools are not detected, they are downloaded and installed automatically. Click **Next** to continue.
-
- >[!NOTE]
- >As of SDA version 1.96.0405, SDA will install only the components of the Windows ADK that are required for deployment, as follows:
- > * Deployment tools
- > * User State Migration Tool (USMT)
- > * Windows Preinstallation Environment (WinPE)
-
- > [!NOTE]
- > As of SDA version 1.96.0405, SDA will install and use MDT 2013 Update 2. Earlier versions of SDA are compatible only with MDT 2013 Update 1.
-
-4. On the **Windows 8.1** page, to create a Windows 10 deployment share, do not select the **Would you like to support Windows 8.1** check box. Click **Next** to continue.
-
-5. On the **Windows 10** page, to create a Windows 10 deployment share, select the **Would you like to support Windows 10** check box. Supply the following information before you click **Next** to continue:
-
- - **Configure Deployment Share for Windows 10**
-
- - **Local Path** – Specify or browse to a location on the local storage device where you would like to store the deployment share files for the Windows 10 SDA deployment share. For example, **E:\\SDAWin10\\** is the location specified in Figure 3.
-
- - **Share Name** – Specify a name for the file share that will be used to access the deployment share on this server from the network. For example, **SDAWin10** is the deployment share name shown in Figure 3. The local path folder is automatically shared by the SDA scripts under this name to the group **Everyone** with a permission level of **Full Control**.
-
- - **Windows 10 Deployment Services**
-
- - Select the **Import boot media into the local Windows Deployment Service** check box if you would like to boot your Surface devices from the network to perform the Windows deployment. Windows Deployment Services must be installed and configured to respond to PXE boot requests. See [Windows Deployment Services Getting Started Guide for Windows Server 2012](https://technet.microsoft.com/library/jj648426.aspx) for more information about how to configure Windows Deployment Services for PXE boot.
-
- - **Windows 10 Source Files**
-
- - **Local Path** – Specify or browse to the root directory of Windows 10 installation files. If you have an ISO file, mount it and browse to the root of the mounted drive. You must have a full set of source files, not just **Install.wim**.
-
- 
-
- *Figure 3. Specify Windows 10 deployment share options*
-
-6. On the **Configure** page, select the check box next to each device or app that you want to include in your deployment share. Note that Surface Pro 4 and Surface Book only support Windows 10 and are not available for the deployment of Windows 8.1. The Surface Firmware Tool is only applicable to Surface 3 and Surface Pro 3 and cannot be selected unless Surface 3 or Surface Pro 3 drivers are selected, as shown in Figure 4. Click **Next** to continue.
-
- 
-
- *Figure 4. Selecting Surface Firmware Tool requires Surface Pro 3 drivers*
-
- >[!NOTE]
- >You cannot select both Surface 3 and Surface 3 LTE models at the same time.
-
-7. On the **Summary** page confirm your selections and click **Finish** to begin the creation of your deployment share. The process can take several minutes as files are downloaded, the tools are installed, and the deployment share is created. While the SDA scripts are creating your deployment share, an **Installation Progress** window will be displayed, as shown in Figure 5. A typical SDA process includes:
-
- - Download of Windows ADK
-
- - Installation of Windows ADK
-
- - Download of MDT
-
- - Installation of MDT
-
- - Download of Surface apps and drivers
-
- - Creation of the deployment share
-
- - Import of Windows installation files into the deployment share
-
- - Import of the apps and drivers into the deployment share
-
- - Creation of rules and task sequences for Windows deployment
-
- 
-
- *Figure 5. The Installation Progress window*
-
- ### Optional: Workaround for Webclient exception
-
- You may see this error message while installing the latest version of ADK or MDT: _An exception occurred during a WebClient request._ This is due to incompatibility between the Surface Deployment Accelerator (SDA) and Background Intelligent Transfer Service (BITS). To work around this issue, do the following.
-
- In the two PowerShell scripts:
-
- ```PowerShell
- %ProgramFiles%\Microsoft\Surface\Deployment Accelerator\Data\PowerShell\Install-MDT.ps1
- %ProgramFiles%\Microsoft\Surface\Deployment Accelerator\Data\PowerShell\INSTALL-WindowsADK.ps1
- ```
-
- Edit the $BITSTransfer variable in the input parameters to $False as shown below:
-
- ```PowerShell
- Param(
- [Parameter(
- Position=0,
- Mandatory=$False,
- HelpMessage="Download via BITS bool true/false"
- )]
- [string]$BITSTransfer = $False
- )
- ```
-
-8. When the SDA process completes the creation of your deployment share, a **Success** window is displayed. Click **Finish** to close the window. At this point your deployment share is now ready to perform a Windows deployment to Surface devices.
-
- ### Optional: Create a deployment share without an Internet connection
-
- If you are unable to connect to the Internet with your deployment server, or if you want to download the Surface drivers and apps separately, you can specify a local source for the driver and app files at the time of deployment share creation. On the **Configure** page of the SDA wizard, select the **Copy from a Local Directory** check box, as shown in Figure 6. The **Download from the Internet** check box will be automatically deselected. Enter the folder location where you have placed the driver and app files in the **Local Path** field, as shown in Figure 6.
-
- >[!NOTE]
- >All of the downloaded driver and applications files must be located in the same folder. If a required driver or application file is missing from the selected folder when you click **Next**, a warning is displayed and the wizard will not proceed to the next step.
-
- >[!NOTE]
- >The driver and app files do not need to be extracted from the downloaded .zip files.
-
- >[!NOTE]
- >Including Office 365 in your deployment share requires an Internet connection and cannot be performed if you use local files.
-
- 
-
- *Figure 6. Specify the Surface driver and app files from a local path*
-
- >[!NOTE]
- >The **Copy from a Local Directory** check box is only available in SDA version 1.90.0221 or later.
-
- ### Optional: Prepare offline USB media
-
- You can use USB media to perform an SDA deployment if your Surface device is unable to boot from the network. For example, if you do not have a Microsoft Surface Ethernet Adapter or Microsoft Surface dock to facilitate network boot (PXE boot). The USB drive produced by following these steps includes a complete copy of the SDA deployment share and can be run on a Surface device without a network connection.
-
- >[!NOTE]
- >The offline media files for the complete SDA deployment share are approximately 9 GB in size. Your USB drive must be at least 9 GB in size. A 16 GB USB drive is recommended.
-
- Before you can create bootable media files within the MDT Deployment Workbench or copy those files to a USB drive, you must first configure that USB drive to be bootable. Using [DiskPart](https://go.microsoft.com/fwlink/p/?LinkId=761073), create a partition, format the partition as FAT32, and set the partition to be active. To run DiskPart, open an administrative PowerShell or Command Prompt window, and then run the following sequence of commands, as shown in Figure 7:
-
- 1. **diskpart** – Opens DiskPart to manage disks and partitions.
-
- 2. **list disk** – Displays a list of the disks available in your system; use this list to identify the disk number that corresponds with your USB drive.
-
- 3. **sel disk 2** – Selects your USB drive; use the number that corresponds with the disk in your system.
-
- 4. **clean** – Removes all configuration from your USB drive.
-
- >[!WARNING]
- >This step will remove all information from your drive. Verify that your USB drive does not contain any needed data before you perform the **clean** command.
-
- 5. **create part pri** – Creates a primary partition on the USB drive.
-
- 6. **format fs=fat32 quick** – Formats the partition with the FAT32 file system, performing a quick format. FAT32 is required to boot the device from UEFI systems like Surface devices.
-
- 7. **assign** – Assigns the next available drive letter to the newly created FAT32 volume.
-
- 8. **active** – Sets the partition to be active, which is required to boot the volume.
-
- 9. **exit** – Exits DiskPart, after which you can close the PowerShell or Command Prompt window.
-
- 
-
- *Figure 7. Use DiskPart to prepare a USB drive for boot*
-
- >[!NOTE]
- >You can format your USB drive with FAT32 from Disk Management, but you must still use DiskPart to set the partition as active for the drive to boot properly.
-
- After you have prepared the USB drive for boot, the next step is to generate offline media from the SDA deployment share. To create this media, follow these steps:
-
- 1. Open the **Deployment Workbench** from the **Microsoft Deployment Toolkit** group on your Start screen.
-
- 2. Expand the **Deployment Shares** node and the **Microsoft Surface Deployment Accelerator** deployment share.
-
- 3. Expand the folder **Advanced Configuration** and select the **Media** folder.
-
-4. Right-click the **Media** folder and click **New Media** as shown in Figure 8 to start the New Media Wizard.
-
- 
-
- *Figure 8. The Media folder of the SDA deployment share*
-
- 5. On the **General Settings** page in the **Media path** field, enter or browse to a folder where you will create the files for the new offline media. See the example **E:\\SDAMedia** in Figure 9. Leave the default profile **Everything** selected in the **Selection profile** drop-down menu, and then click **Next**.
-
- 
-
- *Figure 9. Specify a location and selection profile for your offline media*
-
- 6. On the **Summary** page verify your selections, and then click **Next** to begin creation of the media.
-
- 7. A **Progress** page is displayed while the media is created.
-
- 8. On the **Confirmation** page, click **Finish** to complete creation of the media.
-
- 9. Right-click the **Microsoft Surface Deployment Accelerator** deployment share folder, click **Properties**, and then click the **Rules** tab as shown in Figure 10.
-
- 
-
- *Figure 10. Rules of the SDA deployment share*
-
- 10. Use your mouse to highlight all of the text displayed in the text box of the **Rules** tab, and then press **Ctrl+C** to copy the text.
-
- 11. Click **OK** to close the **Microsoft Surface Deployment Accelerator** deployment share properties.
-
- 12. Right-click the newly created **MEDIA001** item in the **Media** folder, click **Properties**, and then click the **Rules** tab.
-
- 13. Use your mouse to highlight all of the text displayed in the text box of the **Rules** tab, and then press **Ctrl+V** to paste the text you copied from the **Microsoft Surface Deployment Accelerator** deployment share rules.
-
- 14. Right-click the **Microsoft Surface Deployment Accelerator** deployment share folder, click **Properties**, and then click the **Rules** tab again. Click the **Bootstrap.ini** button to open Bootstrap.ini in Notepad.
-
- 15. Press **Ctrl+A** to select all of the text in the window, and then press **Ctrl+C** to copy the text.
-
- 16. Close Bootstrap.ini and click **OK** in **Microsoft Surface Deployment Accelerator** deployment share properties to close the window.
-
- 17. Right-click the newly created **MEDIA001** item in the **Media** folder, click **Properties**, and then click the **Rules** tab again. Click the **Bootstrap.ini** button to open Bootstrap.ini in Notepad.
-
- 18. Press **Ctrl+A** to select all of the text in the window, then press **Ctrl+V** to paste the text from the SDA deployment share Bootstrap.ini file.
-
- 19. Delete the following lines from the Bootstrap.ini as shown in Figure 11, and then save the file:
-
- ```PowerShell
- UserID=
- UserDomain=
- UserPassword=
- DeployRoot=\\SDASERVER\SDAWin10
- UserID=
- UserDomain=
- UserPassword=
- ```
-
- 
-
- *Figure 11. The Bootstrap.ini file of MEDIA001*
-
- 20. Close Bootstrap.ini and click **OK** in **MEDIA001** deployment share properties to close the window.
-
- 21. In the **Deployment Workbench** under the **Media** folder, right-click the newly created **MEDIA001** and click **Update Media Content**, as shown in Figure 12. This will update the media files with the content of the **Microsoft Surface Deployment Accelerator** deployment share.
-
- 
-
- *Figure 12. Select the Update Media Content option*
-
- 22. The **Update Media Content** window is displayed and shows the progress as the media files are created. When the process completes, click **Finish.**
-
- The final step is to copy the offline media files to your USB drive.
-
- 1. In File Explorer, open the path you specified in Step 5, for example **E:\\SDAMedia**.
-
- 2. Copy all of the files from the Content folder to the root of the USB drive.
-
- Your USB drive is now configured as bootable offline media that contains all of the resources required to perform a deployment to a Surface device.
-
-## SDA task sequences
-
-The SDA deployment share is configured with all of the resources required to perform a Windows deployment to a Surface device. These resources include Windows source files, image, Surface drivers, and Surface apps. The deployment share also contains two pre-configured task sequences, as shown in Figure 13. These task sequences contain the steps required to perform a deployment to a Surface device using the default Windows image from the installation media or to create a reference image complete with Windows updates and applications. To learn more about task sequences, see [MDT 2013 Update 2 Lite Touch components](https://technet.microsoft.com/itpro/windows/deploy/mdt-2013-lite-touch-components).
-
-
-
-*Figure 13. Task sequences in the Deployment Workbench*
-
-### Deploy Microsoft Surface
-
-The **1 – Deploy Microsoft Surface** task sequence is used to perform a complete deployment of Windows to a Surface device. This task sequence is pre-configured by the SDA wizard and is ready to perform a deployment as soon as the wizard completes. Running this task sequence on a Surface device deploys the unaltered Windows image copied directly from the Windows installation media you specified in the SDA wizard, along with the Surface drivers for your device. The drivers for your Surface device will be automatically selected through the pre-configured deployment share rules.
-
-When you run the task sequence, you will be prompted to provide the following information:
-
-- A computer name
-
-- Your domain information and the credentials required to join the domain
-
-- A product key, if one is required
-
- >[!NOTE]
- >If you are deploying the same version of Windows as the version that came on your device, no product key is required.
-
-- A time zone
-
-- An Administrator password
-
-The Surface apps you specified on the **Configure** page of the SDA wizard are automatically installed when you run this task sequence on a Surface device.
-
-### Create Windows reference image
-
-The **2 – Create Windows Reference Image** task sequence is used to perform a deployment to a virtual machine for the purpose of capturing an image complete with Windows Updates for use in a deployment to Surface devices. By installing Windows Updates in your reference image, you eliminate the need to download and install those updates on each deployed Surface device. The deployment process with an up-to-date image is significantly faster and more efficient than performing a deployment first and then installing Windows Updates on each device.
-
-Like the **1 – Deploy Microsoft Surface** task sequence, the **2 – Create Windows Reference Image** task sequence performs a deployment of the unaltered Windows image directly from the installation media. Creation of a reference image should always be performed on a virtual machine. Using a virtual machine as your reference system helps to ensure that the resulting image is compatible with different hardware configurations.
-
->[!NOTE]
->Using a virtual machine when you create a reference image for Windows deployment is a recommended practice for performing Windows deployments with Microsoft deployment tools including the Microsoft Deployment Toolkit and Microsoft Endpoint Configuration Manager. These Microsoft deployment technologies use the hardware agnostic images produced from a virtual machine and a collection of managed drivers to deploy to different configurations of hardware. For more information, see [Deploy a Windows 10 image using MDT 2013 Update 2](https://technet.microsoft.com/itpro/windows/deploy/deploy-a-windows-10-image-using-mdt).
-
-In addition to the information required by the **1 – Deploy Microsoft Surface** task sequence, you will also be prompted to capture an image when you run this task sequence on your reference virtual machine. The **Location** and **File name** fields are automatically populated with the proper information for your deployment share. All that you need to do is select the **Capture an image of this reference computer** option when you are prompted on the **Capture Image** page of the Windows Deployment Wizard.
-
-## Deployment to Surface devices
-
-
-To perform a deployment from the SDA deployment share, follow this process on the Surface device:
-
-1. Boot the Surface device to MDT boot media for the SDA deployment share. You can do this over the network by using PXE boot, or from a USB drive as described in the [Optional: Prepare offline USB media](#optional) section of this article.
-
-2. Select the deployment share for the version of Windows you intend to deploy and enter your credentials when you are prompted.
-
-3. Select the task sequence you want to run, usually the **1 – Deploy Microsoft Surface** task sequence.
-
-4. Address the task sequence prompts to pick applications, supply a password, and so on.
-
-5. The task sequence performs the automated deployment using the options specified.
-
-### Boot the Surface device from the network
-
-To boot the Surface device from the network, the Microsoft Surface Deployment Accelerator wizard must have been run on a Windows Server 2012 R2 or later environment that was configured with the Windows Deployment Services (WDS). WDS must have been configured to respond to network boot (PXE boot) requests and the boot files must have been imported into WDS. The SDA wizard will import these file automatically if the **Import boot media into the local Windows Deployment Service** check box was selected on the page for the version of Windows you intend to deploy.
-
-To boot the Surface device from the network, you must also use a Microsoft Surface Ethernet Adapter or the Ethernet port on a Microsoft Surface Dock. Third-party Ethernet adapters are not supported for network boot (PXE boot). A keyboard is also required. Both the Microsoft Surface Type Cover and keyboards connected via USB to the device or dock are supported.
-
-To instruct your Surface device to boot from the network, start with the device powered off and follow these steps:
-
-1. Press and hold the **Volume Down** button, press and release the **Power** button. Continue holding the **Volume Down** button until the device has begun to boot from the network.
-
-2. Press **Enter** when prompted by the dialog on the screen. This prompt indicates that your device has found the WDS PXE server over the network.
-
-3. If you have configured more than one deployment share on this device, you will be prompted to select between the boot images for each deployment share. For example, if you created both a Windows 10 and a Windows 8.1 deployment share, you will be prompted to choose between these two options.
-
-4. Enter the domain credentials that you use to log on to the server where SDA is installed when you are prompted, as shown in Figure 14.
-
- 
-
- *Figure 14. The prompt for credentials to the deployment share*
-
-5. The Windows Deployment Wizard will start from the deployment share to walk you through the deployment process.
-
-### Alternatively boot the devices from the USB stick
-
-To boot a device from the USB stick:
-
-1. Press and hold the **Volume Down** button, press and release the **Power** button. Continue holding the **Volume Down** button until the device has begun to boot from the USB drive.
-
-2. The Windows Deployment Wizard will start from the deployment share to walk you through the deployment process.
-
-### Run the Deploy Microsoft Surface task sequence
-
-To run the Deploy Microsoft Surface task sequence:
-
-1. On the **Task Sequence** page, select the **1 – Deploy Microsoft Surface** task sequence as shown in Figure 15, and then click **Next.**
-
- 
-
- *Figure 15. Select the 1 – Deploy Microsoft Surface task sequence*
-
-2. On the **Computer Details** page, type a name for the Surface device in the **Computer Name** box. In the **Join a domain** section, type your domain name and credentials as shown in Figure 16, and then click **Next**.
-
- 
-
- *Figure 16. Enter the computer name and domain information*
-
-3. On the **Product Key** page, keep the **No product key is required** check box selected if you are deploying the same version and edition of Windows to your Surface devices as they came with from the factory. If you are deploying a different version or edition of Windows to the device, such as Windows Enterprise, select the licensing option that is applicable to your scenario.
-
-4. On the **Locale and Time** page, select your desired **Language Settings** and **Time Zone**, and then click **Next.**
-
-5. On the **Administrator Password** page, type a password for the local Administrator account on the Surface device, and then click **Next.**
-
-6. On the **BitLocker** page, select the **Enable BitLocker** option along with your desired configuration of BitLocker protectors if you want to encrypt the device. Otherwise, keep the **Do not enable BitLocker for this computer** check box selected, and then click **Next.**
-
-7. On the **Ready** page, verify your selections and then click **Begin** to start the automated deployment to this device. The deployment will not require user interaction again. The Windows Deployment Wizard will close and an **Installation Progress** window is displayed to show progress of the task sequence as the image is applied and applications are installed (Figure 17).
-
- 
-
- *Figure 17. The Installation Progress window*
-
-8. When the deployment task sequence completes, a **Success** window is displayed. Click **Finish** to complete the deployment and begin using your Surface device.
diff --git a/devices/surface/support-solutions-surface.md b/devices/surface/support-solutions-surface.md
deleted file mode 100644
index ab4c3a46c4..0000000000
--- a/devices/surface/support-solutions-surface.md
+++ /dev/null
@@ -1,78 +0,0 @@
----
-title: Top support solutions for Surface devices in the enterprise
-description: Find top solutions for common issues using Surface devices in the enterprise.
-ms.assetid: CF58F74D-8077-48C3-981E-FCFDCA34B34A
-ms.reviewer:
-manager: laurawi
-keywords: Troubleshoot common problems, setup issues
-ms.prod: w10
-ms.mktglfcycl: support
-ms.sitesec: library
-ms.pagetype: surfacehub
-author: coveminer
-ms.author: v-jokai
-ms.topic: article
-ms.date: 09/26/2019
-ms.localizationpriority: medium
-ms.audience: itpro
----
-
-# Top support solutions for Surface devices
-
-> [!Note]
-> **Home users**: This article is only intended for use by IT professionals and technical support agents, and applies only to Surface devices. If you're looking for help with a problem with your home device, please see [Surface Devices Help](https://support.microsoft.com/products/surface-devices).
-
-These are the Microsoft Support solutions for common issues you may experience using Surface devices in an enterprise. If your issue is not listed here, [contact Microsoft Support](https://support.microsoft.com/supportforbusiness/productselection).
-
-## Surface Drivers and Firmware
-
-Microsoft regularly releases both updates and solutions for Surface devices. To ensure your devices can receive future updates, including security updates, it's important to keep your Surface devices updated.
-
-- [Surface update history](https://www.microsoft.com/surface/support/install-update-activate/surface-update-history)
-- [Install Surface and Windows updates](https://www.microsoft.com/surface/support/performance-and-maintenance/install-software-updates-for-surface?os=windows-10&=undefined)
-- [Download drivers and firmware for Surface](https://support.microsoft.com/help/4023482)
-- [Deploy the latest firmware and drivers for Surface devices](https://docs.microsoft.com/surface/deploy-the-latest-firmware-and-drivers-for-surface-devices)
-- [Manage Surface driver and firmware updates](https://docs.microsoft.com/surface/manage-surface-pro-3-firmware-updates)
-- [How to manage Surface driver updates in Configuration Manager](https://support.microsoft.com/help/4098906)
-
-## Surface Dock Issues
-
-- [Troubleshoot Surface Dock and docking stations](https://support.microsoft.com/help/4023468/surface-troubleshoot-surface-dock-and-docking-stations)
-
-- [Troubleshoot connecting Surface to a second screen](https://support.microsoft.com/help/4023496)
-
-- [Microsoft Surface Dock Firmware Update](https://docs.microsoft.com/surface/surface-dock-updater)
-
-## Device cover or keyboard issues
-
-- [Troubleshoot your Surface Type Cover or keyboard](https://www.microsoft.com/surface/support/hardware-and-drivers/troubleshoot-surface-keyboards)
-
-## Screen cracked or scratched issues
-
-- [Contact Microsoft Support](https://support.microsoft.com/supportforbusiness/productselection)
-
-## Surface Power or battery Issues
-
-- [How to Charge Surface(Surface PSU information)](https://support.microsoft.com/help/4023496)
-
-- [Surface battery won’t charge or Surface won’t run on battery](https://support.microsoft.com/help/4023536)
-
-- [Surface won’t turn on or wake from sleep](https://support.microsoft.com/help/4023537)
-
-- [Maximize your Surface battery life](https://support.microsoft.com/help/4483194)
-
-## Reset device
-
-- [Creating and using a USB recovery drive for Surface](https://support.microsoft.com/help/4023512)
-
-- [FAQ: Protecting your data if you send your Surface in for Service](https://support.microsoft.com/help/4023508)
-
-- [Microsoft Surface Data Eraser](https://docs.microsoft.com/surface/microsoft-surface-data-eraser)
-
-## Deployment Issues
-
-- [DISK0 not found when you deploy Windows on Surface Pro Model 1796 or Surface Laptop](https://support.microsoft.com/help/4046108)
-
-- [Surface Pro Model 1796 and Surface Laptop 1TB display two drives](https://support.microsoft.com/help/4046105)
-
-- [System SKU reference](https://docs.microsoft.com/surface/surface-system-sku-reference)
diff --git a/devices/surface/surface-device-compatibility-with-windows-10-ltsc.md b/devices/surface/surface-device-compatibility-with-windows-10-ltsc.md
deleted file mode 100644
index 044b0e0437..0000000000
--- a/devices/surface/surface-device-compatibility-with-windows-10-ltsc.md
+++ /dev/null
@@ -1,63 +0,0 @@
----
-title: Surface device compatibility with Windows 10 Long-Term Servicing Channel (Surface)
-description: Find out about compatibility and limitations of Surface devices running Windows 10 Enterprise LTSB edition.
-keywords: ltsb, update, surface servicing options
-ms.prod: w10
-ms.mktglfcycl: manage
-ms.pagetype: surface, devices
-ms.sitesec: library
-author: coveminer
-ms.author: v-jokai
-ms.topic: article
-ms.localizationpriority: medium
-ms.audience: itpro
-ms.reviewer: scottmca
-manager: laurawi
----
-
-# Surface device compatibility with Windows 10 Long-Term Servicing Channel (LTSC)
-
-Surface devices are designed to provide best-in-class experiences in productivity and general-purpose scenarios. Regular updates enable Surface devices to bring to life new innovations and to evolve with the new capabilities delivered by Windows 10 Feature Updates. Feature Updates are available only in Windows 10 Pro or Windows 10 Enterprise editions that receive continuous updates through the Semi-Annual Channel (SAC).
-
-In contrast to the SAC servicing option, formerly known as the Current Branch (CB) or Current Branch for Business (CBB) servicing options, you cannot select the Long-Term Servicing Channel (LTSC) option in Windows 10 settings. To use the LTSC servicing option, you must install a separate edition of Windows 10 Enterprise, known as Windows 10 Enterprise LTSC, formerly known as Windows 10 Enterprise LTSB (Long-Term Servicing Branch. In addition to providing an extended servicing model, the Windows 10 Enterprise LTSC edition also provides an environment with several Windows components removed. The core Surface experiences that are impacted by LTSC include:
-
-* Windows Feature Updates, including enhancements such as:
-
- * Improvements to Direct Ink and palm rejection provided in Windows 10, version 1607 (also referred to as the Anniversary Update)
- * Improved support for high DPI applications provided in Windows 10, version 1703 (also referred to as the Creators Update)
-
-* Pressure sensitivity settings provided by the Surface app
-
-* The Windows Ink Workspace
-
-* Key touch-optimized in-box applications including Microsoft Edge, OneNote, Calendar, and Camera
-
-The use of the Windows 10 Enterprise LTSC environment on Surface devices results in sub-optimal end-user experiences and you should avoid using it in environments where users want and expect a premium, up-to-date user experience.
-
-The LTSC servicing option is designed for device types and scenarios where the key attribute is for features or functionality to never change. Examples include systems that power manufacturing or medical equipment, or embedded systems in kiosks, such as ATMs or airport ticketing systems.
-
->[!NOTE]
->For general information about Windows servicing branches, including LTSC, see [Overview of Windows as a service](https://technet.microsoft.com/itpro/windows/update/waas-overview#long-term-servicing-branch).
-
-As a general guideline, devices that fulfill the following criteria are considered general-purpose devices and should be paired with Windows 10 Pro or Windows 10 Enterprise using the Semi-Annual Channel servicing option:
-
-* Devices that run productivity software such as Microsoft Office
-
-* Devices that use Microsoft Store applications
-
-* Devices that are used for general Internet browsing (for example, research or access to social media)
-
-Before you choose to use Windows 10 Enterprise LTSC edition on Surface devices, consider the following limitations:
-
-* Driver and firmware updates are not explicitly tested against releases of Windows 10 Enterprise LTSC.
-
-* If you encounter problems, Microsoft Support will provide troubleshooting assistance. However, due to the servicing nature of the Windows LTSC, issue resolution may require that devices be upgraded to a more recent version of Windows 10 Enterprise LTSC, or to Windows 10 Pro or Enterprise with the SAC servicing option.
-
-* Surface device replacements (for example, devices replaced under warranty) may contain subtle variations in hardware components that require updated device drivers and firmware. Compatibility with these updates may require the installation of a more recent version of Windows 10 Enterprise LTSC or Windows 10 Pro or Enterprise with the SAC servicing option.
-
->[!NOTE]
->Organizations that standardize on a specific version of Windows 10 Enterprise LTSC may be unable to adopt new generations of Surface hardware such as Surface Pro 7, Surface Pro X, or Surface Laptop 3 without also updating to a later version of Windows 10 Enterprise LTSC or Windows 10 Pro or Enterprise. For more information, see the **How will Windows 10 LTSBs be supported?** topic in the **Supporting the latest processor and chipsets on Windows** section of [Lifecycle Policy FAQ—Windows products](https://support.microsoft.com/help/18581/lifecycle-policy-faq-windows-products#b4).
-
-Surface devices running Windows 10 Enterprise LTSC edition will not receive new features. In many cases these features are requested by customers to improve the usability and capabilities of Surface hardware. For example, new improvements for High DPI applications in Windows 10, version 1703. Customers that use Surface devices in the LTSC configuration will not see the improvements until they either update to a new Windows 10 Enterprise LTSC release or upgrade to a version of Windows 10 with support for the SAC servicing option.
-
-Devices can be changed from Windows 10 Enterprise LTSC to a more recent version of Windows 10 Enterprise, with support for the SAC servicing option, without the loss of user data by performing an upgrade installation. You can also perform an upgrade installation on multiple devices by leveraging the Upgrade Task Sequence Templates available in the Microsoft Deployment Toolkit (MDT) and Microsoft Endpoint Configuration Manager. For more information, see [Upgrade Surface devices to Windows 10 with Microsoft Deployment Toolkit](https://technet.microsoft.com/itpro/surface/upgrade-surface-devices-to-windows-10-with-mdt).
diff --git a/devices/surface/surface-diagnostic-toolkit-business.md b/devices/surface/surface-diagnostic-toolkit-business.md
deleted file mode 100644
index 11a032fb45..0000000000
--- a/devices/surface/surface-diagnostic-toolkit-business.md
+++ /dev/null
@@ -1,199 +0,0 @@
----
-title: Deploy Surface Diagnostic Toolkit for Business
-description: This topic explains how to use the Surface Diagnostic Toolkit for Business.
-ms.prod: w10
-ms.mktglfcycl: manage
-ms.localizationpriority: medium
-ms.sitesec: library
-author: coveminer
-ms.author: v-jokai
-ms.topic: article
-ms.date: 10/31/2019
-ms.reviewer: hachidan
-manager: laurawi
-ms.audience: itpro
----
-
-# Deploy Surface Diagnostic Toolkit for Business
-
-The Microsoft Surface Diagnostic Toolkit for Business (SDT) enables IT administrators to quickly investigate, troubleshoot, and resolve hardware, software, and firmware issues with Surface devices. You can run a range of diagnostic tests and software repairs in addition to obtaining device health insights and guidance for resolving issues.
-
-Specifically, SDT for Business enables you to:
-
-- [Customize the package.](#create-custom-sdt)
-- [Run the app using commands.](surface-diagnostic-toolkit-command-line.md)
-- [Run multiple hardware tests to troubleshoot issues.](surface-diagnostic-toolkit-desktop-mode.md#multiple)
-- [Generate logs for analyzing issues.](surface-diagnostic-toolkit-desktop-mode.md#logs)
-- [Obtain detailed report comparing device vs optimal configuration.](surface-diagnostic-toolkit-desktop-mode.md#detailed-report)
-
-
-## Primary scenarios and download resources
-
-To run SDT for Business, download the components listed in the following table.
-
-
-Mode | Primary scenarios | Download | Learn more
---- | --- | --- | ---
-Desktop mode | Assist users in running SDT on their Surface devices to troubleshoot issues. Create a custom package to deploy on one or more Surface devices allowing users to select specific logs to collect and analyze. | SDT distributable MSI package: Microsoft Surface Diagnostic Toolkit for Business Installer [Surface Tools for IT](https://www.microsoft.com/download/details.aspx?id=46703) | [Use Surface Diagnostic Toolkit in desktop mode](surface-diagnostic-toolkit-desktop-mode.md)
-Command line | Directly troubleshoot Surface devices remotely without user interaction, using standard tools such as Configuration Manager. It includes the following commands: `-DataCollector` collects all log files `-bpa` runs health diagnostics using Best Practice Analyzer. `-windowsupdate` checks Windows Update for missing firmware or driver updates. `-warranty` checks warranty information.
| SDT console app: Microsoft Surface Diagnostics App Console [Surface Tools for IT](https://www.microsoft.com/download/details.aspx?id=46703) | [Run Surface Diagnostic Toolkit using commands](surface-diagnostic-toolkit-command-line.md)
-
-## Supported devices
-
-SDT for Business is supported on Surface 3 and later devices, including:
-
-- Surface Pro 7
-- Surface Laptop 3
-- Surface Pro 6
-- Surface Laptop 2
-- Surface Go
-- Surface Go with LTE
-- Surface Book 2
-- Surface Pro with LTE Advanced (Model 1807)
-- Surface Pro (Model 1796)
-- Surface Laptop
-- Surface Studio
-- Surface Studio 2
-- Surface Book
-- Surface Pro 4
-- Surface 3 LTE
-- Surface 3
-- Surface Pro 3
-
-## Installing Surface Diagnostic Toolkit for Business
-
-To create an SDT package that you can distribute to users in your organization:
-
-1. Sign in to your Surface device using the Administrator account.
-2. Download SDT Windows Installer Package (.msi) from the [Surface Tools for IT download page](https://www.microsoft.com/download/details.aspx?id=46703) and copy it to a preferred location on your Surface device, such as Desktop.
-3. The SDT setup wizard appears, as shown in figure 1. Click **Next**.
-
- >[!NOTE]
- >If the setup wizard does not appear, ensure that you are signed into the Administrator account on your computer.
-
- 
-
- *Figure 1. Surface Diagnostic Toolkit setup wizard*
-
-4. When the SDT setup wizard appears, click **Next**, accept the End User License Agreement (EULA)
-
-5. On the Install Options screen, change the default install location if desired.
-6. Under Setup Type, select **Advanced**.
-
- >[!NOTE]
- >The standard option allows users to run the diagnostic tool directly on their Surface device provided they are signed into their device using an Administrator account.
-
- 
-
-7. Click **Next** and then click **Install**.
-
-## Installing using the command line
-If desired, you can install SDT at a command prompt and set a custom flag to install the tool in admin mode. SDT contains the following install option flags:
-
-- `SENDTELEMETRY` sends telemetry data to Microsoft. The flag accepts `0` for disabled or `1` for enabled. The default value is `1` to send telemetry.
-- `ADMINMODE` configures the tool to be installed in admin mode. The flag accepts `0` for client mode or `1` for IT Administrator mode. The default value is `0`.
-
-### To install SDT from the command line:
-
-1. Open a command prompt and enter:
-
- ```
- msiexec.exe /i ADMINMODE=1.
- ```
- **Example:**
-
- ```
- C:\Users\Administrator> msiexec.exe/I"C:\Users\Administrator\Desktop\Microsoft_Surface_Diagnostic_Toolkit_for_Business_Installer.msi" ADMINMODE=1
- ```
-
-## Locating SDT on your Surface device
-
-Both SDT and the SDT app console are installed at `C:\Program Files\Microsoft\Surface\Microsoft Surface Diagnostic Toolkit for Business`.
-
-In addition to the .exe file, SDT installs a JSON file and an admin.dll file (modules\admin.dll), as shown in figure 2.
-
-
-
-*Figure 2. Files installed by SDT*
-
-
-## Preparing the SDT package for distribution
-
-Creating a custom package allows you to target the tool to specific known issues.
-
-1. Click **Start > Run**, enter **Surface** and then click **Surface Diagnostic Toolkit for Business**.
-2. When the tool opens, click **Create Custom Package**, as shown in figure 3.
-
- 
-
- *Figure 3. Create custom package*
-
-### Language and telemetry settings
-
- When creating a package, you can select language settings or opt out of sending telemetry information to Microsoft. By default, SDT sends telemetry to Microsoft that is used to improve the application in accordance with the [Microsoft Privacy Statement](https://privacy.microsoft.com/privacystatement). If you wish to decline, clear the check box when creating a custom package, as shown below. Or clear the **Send telemetry to Microsoft** check box on the **Install Options** page during SDT Setup.
-
->[!NOTE]
->This setting does not affect the minimal telemetry automatically stored on Microsoft servers when running tests and repairs that require an Internet connection, such as Windows Update and Software repair, or providing feedback using the Smile or Frown buttons in the app toolbar.
-
-
-
-
-*Figure 4. Select language and telemetry settings*
-
-
-### Windows Update page
-
-Select the option appropriate for your organization. Most organizations with multiple users will typically select to receive updates via Windows Server Update Services (WSUS), as shown in figure 5. If using local Windows Update packages or WSUS, enter the path as appropriate.
-
-
-
-*Figure 5. Windows Update option*
-
-### Software repair page
-
-This allows you to select or remove the option to run software repair updates.
-
-
-
-*Figure 6. Software repair option*
-
-### Collecting logs and saving package page
-
-You can select to run a wide range of logs across applications, drivers, hardware, and the operating system. Click the appropriate area and select from the menu of available logs. You can then save the package to a software distribution point or equivalent location that users can access.
-
-
-
-*Figure 7. Log option and save package*
-
-## Next steps
-
-- [Use Surface Diagnostic Toolkit for Business in desktop mode](surface-diagnostic-toolkit-desktop-mode.md)
-- [Use Surface Diagnostic Toolkit for Business using commands](surface-diagnostic-toolkit-command-line.md)
-
-## Changes and updates
-### Version 2.43.139.0
-*Release date: October 21, 2019*
-This version of Surface Diagnostic Toolkit for Business adds support for the following:
-
-- Surface Pro 7
-- Surface Laptop 3
-
-### Version 2.42.139.0
-*Release date: September 24, 2019*
-This version of Surface Diagnostic Toolkit for Business adds support for the following:
-- Ability to download hardware reports.
-- Ability to contact Microsoft Support directly from the tool.
-
-### Version 2.41.139.0
-*Release date: June 24, 2019*
-This version of Surface Diagnostic Toolkit for Business adds support for the following:
-- Driver version information included in logs and report.
-- Ability to provide feedback about the app.
-
-
-### Version 2.36.139.0
-*Release date: April 26, 2019*
-This version of Surface Diagnostic Toolkit for Business adds support for the following:
-- Advanced Setup option to unlock admin capabilities through the installer UI, without requiring command line configuration.
-- Accessibility improvements.
-- Surface brightness control settings included in logs.
-- External monitor compatibility support link in report generator.
diff --git a/devices/surface/surface-diagnostic-toolkit-command-line.md b/devices/surface/surface-diagnostic-toolkit-command-line.md
deleted file mode 100644
index 035eec60da..0000000000
--- a/devices/surface/surface-diagnostic-toolkit-command-line.md
+++ /dev/null
@@ -1,151 +0,0 @@
----
-title: Run Surface Diagnostic Toolkit for Business using commands
-description: How to run Surface Diagnostic Toolkit in a command console
-ms.prod: w10
-ms.mktglfcycl: manage
-ms.sitesec: library
-author: coveminer
-ms.author: v-jokai
-ms.topic: article
-ms.reviewer: hachidan
-manager: laurawi
-ms.localizationpriority: medium
-ms.audience: itpro
----
-
-# Run Surface Diagnostic Toolkit for Business using commands
-
-Running the Surface Diagnostic Toolkit (SDT) at a command prompt requires downloading the STD app console. After it's installed, you can run SDT at a command prompt via the Windows command console (cmd.exe) or using Windows PowerShell, including PowerShell Integrated Scripting Environment (ISE), which provides support for autocompletion of commands, copy/paste, and other features. For a list of supported Surface devices in SDT, refer to [Deploy Surface Diagnostic Toolkit for Business](surface-diagnostic-toolkit-business.md).
-
->[!NOTE]
->To run SDT using commands, you must be signed in to the Administrator account or signed in to an account that is a member of the Administrator group on your Surface device.
-
-## Running SDT app console
-
-Download and install SDT app console from the [Surface Tools for IT download page](https://www.microsoft.com/download/details.aspx?id=46703). You can use the Windows command prompt (cmd.exe) or Windows PowerShell to:
-
-- Collect all log files.
-- Run health diagnostics using Best Practice Analyzer.
-- Check update for missing firmware or driver updates.
-
->[!NOTE]
->In this release, the SDT app console supports single commands only. Running multiple command line options requires running the console exe separately for each command.
-
-By default, output files are saved in the same location as the console app. Refer to the following table for a complete list of commands.
-
-Command | Notes
---- | ---
--DataCollector "output file" | Collects system details into a zip file. "output file" is the file path to create system details zip file.
**Example**: `Microsoft.Surface.Diagnostics.App.Console.exe -DataCollector SDT_DataCollection.zip`
--bpa "output file" | Checks several settings and health indicators in the device. “output file" is the file path to create the HTML report.
**Example**: `Microsoft.Surface.Diagnostics.App.Console.exe -bpa BPA.html`
--windowsupdate | Checks Windows Update online servers for missing firmware and/or driver updates.
**Example**: Microsoft.Surface.Diagnostics.App.Console.exe -windowsupdate
--warranty "output file" | Checks warranty information on the device (valid or invalid). The optional “output file” is the file path to create the xml file.
**Example**: Microsoft.Surface.Diagnostics.App.Console.exe –warranty “warranty.xml”
-
-
->[!NOTE]
->To run the SDT app console remotely on target devices, you can use a configuration management tool such as Microsoft Endpoint Configuration Manager. Alternatively, you can create a .zip file containing the console app and appropriate console commands and deploy per your organization’s software distribution processes.
-
-## Running Best Practice Analyzer
-
-You can run BPA tests across key components such as BitLocker, Secure Boot, and Trusted Platform Module (TPM) and then output the results to a shareable file. The tool generates a series of tables with color-coded headings and condition descriptors along with guidance about how to approach resolving the issue.
-
-- Green indicates the component is running in an optimal condition (optimal).
-- Orange indicates the component is not running in an optimal condition (not optimal).
-- Red indicates the component is in an abnormal state.
-
-### Sample BPA results output
-
-
-
BitLocker
-
Description:
Checks if BitLocker is enabled on the system drive.
-
Value:
Protection On
-
Condition:
Optimal
-
Guidance:
It is highly recommended to enable BitLocker to protect your data.
-
-
-
-
Secure Boot
-
Description:
Checks if Secure Boot is enabled.
-
Value:
True
-
Condition:
Optimal
-
Guidance:
It is highly recommended to enable Secure Boot to protect your PC.
-
-
-
-
Trusted Platform Module
-
Description:
Ensures that the TPM is functional.
-
Value:
True
-
Condition:
Optimal
-
Guidance:
Without a functional TPM, security-based functions such as BitLocker may not work properly.
-
-
-
-
Connected Standby
-
Description:
Checks if Connected Standby is enabled.
-
Value:
True
-
Condition:
Optimal
-
Guidance:
Connected Standby allows a Surface device to receive updates and notifications while not being used. For best experience, Connected Standby should be enabled.
-
-
-
-
Bluetooth
-
Description:
Checks if Bluetooth is enabled.
-
Value:
Enabled
-
Condition:
Optimal
-
Guidance:
-
-
-
-
Debug Mode
-
Description:
Checks if the operating system is in Debug mode.
-
Value:
Normal
-
Condition:
Optimal
-
Guidance:
The debug boot option enables or disables kernel debugging of the Windows operating system. Enabling this option can cause system instability and can prevent DRM (digital rights managemend) protected media from playing.
-
-
-
-
Test Signing
-
Description:
Checks if Test Signing is enabled.
-
Value:
Normal
-
Condition:
Optimal
-
Guidance:
Test Signing is a Windows startup setting that should only be used to test pre-release drivers.
-
-
-
-
Active Power Plan
-
Description:
Checks that the correct power plan is active.
-
Value:
Balanced
-
Condition:
Optimal
-
Guidance:
It is highly recommended to use the "Balanced" power plan to maximize productivity and battery life.
-
-
-
-
Windows Update
-
Description:
Checks if the device is up to date with Windows updates.
-
Value:
Microsoft Silverlight (KB4023307), Definition Update for Windows Defender Antivirus - KB2267602 (Definition 1.279.1433.0)
-
Condition:
Not Optimal
-
Guidance:
Updating to the latest windows makes sure you are on the latest firmware and drivers. It is recommended to always keep your device up to date
-
-
-
-
Free Hard Drive Space
-
Description:
Checks for low free hard drive space.
-
Value:
66%
-
Condition:
Optimal
-
Guidance:
For best performance, your hard drive should have at least 10% of its capacity as free space.
-
-
-
-
Non-Functioning Devices
-
Description:
List of non-functioning devices in Device Manager.
-
Value:
-
Condition:
Optimal
-
Guidance:
Non-functioning devices in Device Manager may cause unpredictable problems with Surface devices such as, but not limited to, no power savings for the respective hardware component.
-
-
-
-
External Monitor
-
Description:
Checks for an external monitor that may have compatibility issues.
-
Value:
-
Condition:
Optimal
-
Guidance:
Check with the original equipment manufacturer for compatibility with your Surface device.
-
diff --git a/devices/surface/surface-diagnostic-toolkit-desktop-mode.md b/devices/surface/surface-diagnostic-toolkit-desktop-mode.md
deleted file mode 100644
index 795bff7f7f..0000000000
--- a/devices/surface/surface-diagnostic-toolkit-desktop-mode.md
+++ /dev/null
@@ -1,94 +0,0 @@
----
-title: Use Surface Diagnostic Toolkit for Business in desktop mode
-description: How to use SDT to help users in your organization run the tool to identify and diagnose issues with the Surface device.
-ms.prod: w10
-ms.mktglfcycl: manage
-ms.sitesec: library
-author: coveminer
-ms.author: v-jokai
-ms.topic: article
-ms.reviewer: hachidan
-manager: laurawi
-ms.localizationpriority: medium
-ms.audience: itpro
----
-
-# Use Surface Diagnostic Toolkit for Business in desktop mode
-
-This topic explains how to use the Surface Diagnostic Toolkit (SDT) to help users in your organization run the tool to identify and diagnose issues with the Surface device. Successfully running SDT can quickly determine if a reported issue is caused by failed hardware or user error. For a list of supported Surface devices in SDT, refer to [Deploy Surface Diagnostic Toolkit for Business](surface-diagnostic-toolkit-business.md).
-
-
-1. Direct the user to install [the SDT package](surface-diagnostic-toolkit-business.md#create-custom-sdt) from a software distribution point or network share. After it is installed, you’re ready to guide the user through a series of tests.
-
-2. Begin at the home page, which allows users to enter a description of the issue, and click **Continue**, as shown in figure 1.
-
- 
-*Figure 1. SDT in desktop mode*
-
-3. When SDT indicates the device has the latest updates, click **Continue** to advance to the catalog of available tests, as shown in figure 2.
-
- 
-*Figure 2. Select from SDT options*
-
-4. You can choose to run all the diagnostic tests. Or, if you already suspect a particular issue such as a faulty display or a power supply problem, click **Select** to choose from the available tests and click **Run Selected**, as shown in figure 3. See the following table for details of each test.
-
- 
-*Figure 3. Select hardware tests*
-
- Hardware test | Description
- --- | ---
- Power Supply and Battery | Checks Power supply is functioning optimally
- Display and Sound | Checks brightness, stuck or dead pixels, speaker and microphone functioning
- Ports and Accessories | Checks accessories, screen attach and USB functioning
- Connectivity | Checks Bluetooth, wireless and LTE connectivity
- Security | Checks security related issues
- Touch | Checks touch related issues
- Keyboard and touch | Checks integrated keyboard connection and type cover
- Sensors | Checks functioning of different sensors in the device
- Hardware | Checks issues with different hardware components such as graphics card and camera
-
-
-
-
-
-
-
-## Running multiple hardware tests to troubleshoot issues
-
-SDT is designed as an interactive tool that runs a series of tests. For each test, SDT provides instructions summarizing the nature of the test and what users should expect or look for in order for the test to be successful. For example, to diagnose if the display brightness is working properly, SDT starts at zero and increases the brightness to 100 percent, asking users to confirm – by answering **Yes** or **No** -- that brightness is functioning as expected, as shown in figure 4.
-
-For each test, if functionality does not work as expected and the user clicks **No**, SDT generates a report of the possible causes and ways to troubleshoot it.
-
-
-*Figure 4. Running hardware diagnostics*
-
-1. If the brightness successfully adjusts from 0-100 percent as expected, direct the user to click **Yes** and then click **Continue**.
-2. If the brightness fails to adjust from 0-100 percent as expected, direct the user to click **No** and then click **Continue**.
-3. Guide users through remaining tests as appropriate. When finished, SDT automatically provides a high-level summary of the report, including the possible causes of any hardware issues along with guidance for resolution.
-
-
-### Repairing applications
-
-SDT enables you to diagnose and repair applications that may be causing issues, as shown in figure 5.
-
-
-*Figure 5. Running repairs*
-
-
-### Generating logs for analyzing issues
-
-SDT provides extensive log-enabled diagnosis support across applications, drivers, hardware, and operating system issues, as shown in figure 6.
-
-
-*Figure 6. Generating logs*
-
-
-
-### Generating detailed report comparing device vs. optimal configuration
-
-Based on the logs, SDT generates a report for software- and firmware-based issues that you can save to a preferred location.
-
-## Related topics
-
-- [Run Surface Diagnostic Toolkit for Business using commands](surface-diagnostic-toolkit-command-line.md)
-
diff --git a/devices/surface/surface-diagnostic-toolkit-for-business-intro.md b/devices/surface/surface-diagnostic-toolkit-for-business-intro.md
deleted file mode 100644
index 2b19282899..0000000000
--- a/devices/surface/surface-diagnostic-toolkit-for-business-intro.md
+++ /dev/null
@@ -1,43 +0,0 @@
----
-title: Fix common Surface problems using the Surface Diagnostic Toolkit for Business
-description: This page provides an introduction to the Surface Diagnostic Toolkit for Business for use in commercial environments.
-ms.prod: w10
-ms.mktglfcycl: manage
-ms.sitesec: library
-author: coveminer
-ms.author: v-jokai
-ms.topic: article
-ms.reviewer: cottmca
-manager: laurawi
-ms.localizationpriority: medium
-ms.audience: itpro
----
-
-# Fix common Surface problems using the Surface Diagnostic Toolkit for Business
-
-If your Surface isn’t working properly, the Microsoft Surface Diagnostic Toolkit for Business can help you or your administrator find and solve problems.
-
-> [!NOTE]
-> Surface Diagnostic Toolkit for Business is built for commercial devices. If your device is a personal device and not managed by your work or school run the [Surface Diagnostic Toolkit](https://support.microsoft.com/en-us/help/4037239/surface-fix-common-surface-problems-using-surface-diagnostic-toolkit) instead.
-
-## Run the Surface Diagnostic Toolkit for Business
-
-Before you run the diagnostic tool, make sure you have the latest Windows updates. Go to [Install Surface and Windows 10 updates](https://support.microsoft.com/en-us/help/4023505/surface-install-surface-and-windows-updates) for more information. If that doesn't solve the problem, you'll need to run the diagnostic tool.
-
-> [!NOTE]
-> The Surface Diagnostic Toolkit for Business only works on Surface devices running Windows 10. It does not work on Surface Pro, Surface Pro 2, or Surface devices configured in S mode.
-
-**To run the Surface Diagnostic Toolkit for Business:**
-
-1. Download the Surface Diagnostic Toolkit for Business. To do this, go to the [**Surface Tools for IT** download page](https://www.microsoft.com/download/details.aspx?id=46703), choose **Download**, select **Surface Diagnostic Toolkit for Business** from the provided list, and choose **Next**.
-2. Select Run and follow the on-screen instructions. For full details, refer to [Deploy Surface Diagnostic Toolkit for Business](https://docs.microsoft.com/surface/surface-diagnostic-toolkit-business).
-
-The diagnosis and repair time averages 15 minutes but could take an hour or longer, depending on internet connection speed and the number of updates or repairs required.
-
-## If you still need help
-
-If the Surface Diagnostic Toolkit for Business didn’t fix the problem, you can also:
-
-- Make an in-store appointment: We might be able to fix the problem or provide a replacement Surface at your local Microsoft Store. [Locate a Microsoft Store near you](https://www.microsoft.com/store/locations/find-a-store?WT.mc_id=MSC_Solutions_en_us_scheduleappt).
-- Contact customer support: If you want to talk to someone about how to fix your problem, [contact us](https://support.microsoft.com/en-us/help/4037645/contact-surface-warranty-and-software-support-for-business).
-- Get your Surface serviced: If your Surface product needs service, [request it online](https://mybusinessservice.surface.com/).
diff --git a/devices/surface/surface-dock-firmware-update.md b/devices/surface/surface-dock-firmware-update.md
deleted file mode 100644
index 26264b1509..0000000000
--- a/devices/surface/surface-dock-firmware-update.md
+++ /dev/null
@@ -1,235 +0,0 @@
----
-title: Microsoft Surface Dock Firmware Update - Technical information for IT administrators
-description: This article explains how to use Microsoft Surface Dock Firmware Update to update Surface Dock firmware. When installed on your Surface device, it will update any Surface Dock attached to your Surface device.
-ms.localizationpriority: medium
-ms.prod: w10
-ms.mktglfcycl: manage
-ms.sitesec: library
-author: greg-lindsay
-ms.author: greglin
-ms.topic: article
-ms.reviewer: scottmca
-manager: laurawi
-ms.audience: itpro
----
-# Microsoft Surface Dock Firmware Update: Technical information for IT administrators
-
-> [!IMPORTANT]
-> This article contains technical instructions for IT administrators. If you are a home user, please see [How to update your Surface Dock Firmware](https://support.microsoft.com/help/4023478/surface-update-your-surface-dock) on the Microsoft Support site. The instructions at the support site are the same as the general installation steps below, but this article has additional information for monitoring, verifying, and deploying the update to multiple devices on a network.
-
-This article explains how to use Microsoft Surface Dock Firmware Update to update Surface Dock firmware. When installed on your Surface device, it will update any Surface Dock attached to your Surface device.
-
-This tool supersedes the earlier Microsoft Surface Dock Updater tool, previously available for download as part of Surface Tools for IT. The earlier tool was named Surface_Dock_Updater_vx.xx.xxx.x.msi (where x indicates the version number) and is no longer available for download and should not be used.
-
-## Install the Surface Dock Firmware Update
-
-This section describes how to manually install the firmware update.
-
-> [!NOTE]
-> Microsoft periodically releases new versions of Surface Dock Firmware Update. The MSI file is not self-updating. If you have deployed the MSI to Surface devices and a new version of the firmware is released, you will need to deploy the new version.
-
-1. Download and install [Microsoft Surface Dock Firmware Update](https://www.microsoft.com/download/details.aspx?id=46703).
- - The update requires a Surface device running Windows 10, version 1803 or later.
- - Installing the MSI file might prompt you to restart Surface. However, restarting is not required to perform the update.
-
-2. Disconnect your Surface device from the Surface Dock (using the power adapter), wait ~5 seconds, and then reconnect. The Surface Dock Firmware Update will update the dock silently in background. The process can take a few minutes to complete and will continue even if interrupted.
-
-## Monitor the Surface Dock Firmware Update
-
-This section is optional and provides an overview of how to monitor installation of the firmware update.
-
-To monitor the update:
-
-1. Open Event Viewer, browse to **Windows Logs > Application**, and then under **Actions** in the right-hand pane click **Filter Current Log**, enter **SurfaceDockFwUpdate** next to **Event sources**, and then click **OK**.
-
-2. Type the following command at an elevated command prompt:
-
- ```cmd
- Reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\WUDF\Services\SurfaceDockFwUpdate\Parameters"
- ```
-3. Install the update as described in the [next section](#install-the-surface-dock-firmware-update) of this article.
-4. Event 2007 with the following text indicates a successful update: **Firmware update finished. hr=0 DriverTelementry EventCode = 2007**.
- - If the update is not successful, then event ID 2007 will be displayed as an **Error** event rather than **Information**. Additionally, the version reported in the Windows Registry will not be current.
-5. When the update is complete, updated DWORD values will be displayed in the Windows Registry, corresponding to the current version of the tool. See the [Versions reference](#versions-reference) section in this article for details. For example:
- - Component10CurrentFwVersion 0x04ac3970 (78395760)
- - Component20CurrentFwVersion 0x04915a70 (76634736)
-
->[!TIP]
->If you see "The description for Event ID xxxx from source SurfaceDockFwUpdate cannot be found" in event text, this is expected and can be ignored.
-
-Also see the following sections in this article:
- - [How to verify completion of firmware update](#how-to-verify-completion-of-the-firmware-update)
- - [Event logging](#event-logging)
- - [Troubleshooting tips](#troubleshooting-tips)
- - [Versions reference](#versions-reference)
-
-## Network deployment
-
-You can use Windows Installer commands (Msiexec.exe) to deploy Surface Dock Firmware Update to multiple devices across your network. When using Microsoft Endpoint Configuration Manager or other deployment tool, enter the following syntax to ensure the installation is silent:
-
-- **Msiexec.exe /i \ /quiet /norestart**
-
- For example:
- ```
- msiexec /i "\\share\folder\Surface_Dock_FwUpdate_1.42.139_Win10_17134_19.084.31680_0.msi" /quiet /norestart
- ```
-
- > [!NOTE]
- > A log file is not created by default. In order to create a log file, you will need to append "/l*v [path]". For example: Msiexec.exe /i \ /l*v %windir%\logs\ SurfaceDockFWI.log"
-
- For more information, refer to [Command line options](https://docs.microsoft.com/windows/win32/msi/command-line-options) documentation.
-
-> [!IMPORTANT]
-> If you want to keep your Surface Dock updated using any other method, refer to [Update your Surface Dock](https://support.microsoft.com/help/4023478/surface-update-your-surface-dock) for details.
-
-## Intune deployment
-
-You can use Intune to distribute Surface Dock Firmware Update to your devices. First you will need to convert the MSI file to the .intunewin format, as described in the following documentation: [Intune Standalone - Win32 app management](https://docs.microsoft.com/intune/apps/apps-win32-app-management).
-
-Use the following command:
- - **msiexec /i \ /quiet /q**
-
-## How to verify completion of the firmware update
-
-Surface dock firmware consists of two components:
-
-- **Component10:** Micro controller unit (MCU) firmware
-- **Component20:** Display port (DP) firmware.
-
-Successful completion of Surface Dock Firmware Update results in new registry key values for these firmware components.
-
-**To verify updates:**
-
-1. Open Regedit and navigate to the following registry path:
-
- - **HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\WUDF\Services\SurfaceDockFwUpdate\Parameters**
-
-2. Look for the registry keys: **Component10CurrentFwVersion and Component20CurrentFwVersion**, which refer to the firmware that is currently on the device.
-
- 
-
-3. Verify the new registry key values match the updated registry key values listed in the Versions reference at the end of this document. If the values match, the firmware was updated successfully.
-
-4. If unable to verify, review Event logging and Troubleshooting tips in the next section.
-
-## Event logging
-
-**Table 1. Log files for Surface Dock Firmware Update**
-
-| Log | Location | Notes |
-| -------------------------------- | --------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Surface Dock Firmware Update log | Path needs to be specified (see note) | Earlier versions of this tool wrote events to Applications and Services Logs\Microsoft Surface Dock Updater. |
-| Windows Device Install log | %windir%\inf\setupapi.dev.log | For more information about using Device Install Log, refer to [SetupAPI Logging](https://docs.microsoft.com/windows-hardware/drivers/install/setupapi-logging--windows-vista-and-later-) documentation. |
-
-
-**Table 2. Event log IDs for Surface Dock Firmware Update**
-Events are logged in the Application Event Log. Note: Earlier versions of this tool wrote events to Applications and Services Logs\Microsoft Surface Dock Updater.
-
-| Event ID | Event type |
-| -------- | -------------------------------------------------------------------- |
-| 2001 | Dock firmware update has started. |
-| 2002 | Dock firmware update skipped because dock is known to be up to date. |
-| 2003 | Dock firmware update failed to get firmware version. |
-| 2004 | Querying the firmware version. |
-| 2005 | Dock firmware failed to start update. |
-| 2006 | Failed to send offer/payload pairs. |
-| 2007 | Firmware update finished. |
-| 2008 | BEGIN dock telemetry. |
-| 2011 | END dock telemetry. |
-
-## Troubleshooting tips
-
-- Completely disconnect power for Surface dock from the AC power to reset the Surface Dock.
-- Disconnect all peripherals except for the Surface Dock.
-- Uninstall any current Surface Dock Firmware Update and then install the latest version.
-- Ensure that the Surface Dock is disconnected, and then allow enough time for the update to complete as monitored via an LED in the Ethernet port of the dock. Wait until the LED stops blinking before you unplug Surface Dock from power.
-- Connect the Surface Dock to a different device to see if it is able to update the dock.
-
-## Versions reference
-
->[!NOTE]
->The installation file is released with the following naming format: **Surface_Dock_FwUpdate_X.XX.XXX_Win10_XXXXX_XX.XXX.XXXXX_X.MSI** (ex: Surface_Dock_FwUpdate_1.42.139_Win10_17134_19.084.31680_0.msi) and installs by default to C:\Program Files\SurfaceUpdate.
-
-### Version 1.42.139
-*Release Date: September 18 2019*
-
-This version, contained in Surface_Dock_FwUpdate_1.42.139_Win10_17134_19.084.31680_0.MSI, updates firmware in the background.
-**Updated registry key values:**
-
-- Component10CurrentFwVersion updated to **4ac3970**.
-- Component20CurrentFwVersion updated to **4a1d570**.
-
-It adds support for Surface Pro 7 and Surface Laptop 3.
-
-## Legacy versions
-
-### Version 2.23.139.0
-*Release Date: 10 October 2018*
-
-This version of Surface Dock Updater adds support for the following:
-
-- Add support for Surface Pro 6
-- Add support for Surface Laptop 2
-
-
-### Version 2.22.139.0
-*Release Date: 26 July 2018*
-
-This version of Surface Dock Updater adds support for the following:
-
-- Increase update reliability
-- Add support for Surface Go
-
-### Version 2.12.136.0
-*Release Date: 29 January 2018*
-
-This version of Surface Dock Updater adds support for the following:
-* Update for Surface Dock Main Chipset Firmware
-* Update for Surface Dock DisplayPort Firmware
-* Improved display stability for external displays when used with Surface Book or Surface Book 2
-
-Additionally, installation of this version of Surface Dock Updater on Surface Book devices includes the following:
-* Update for Surface Book Base Firmware
-* Added support for Surface Dock firmware updates with improvements targeted to Surface Book devices
-
-
-### Version 2.9.136.0
-*Release date: November 3, 2017*
-
-This version of Surface Dock Updater adds support for the following:
-
-* Update for Surface Dock DisplayPort Firmware
-* Resolves an issue with audio over passive display port adapters
-
-### Version 2.1.15.0
-*Release date: June 19, 2017*
-
-This version of Surface Dock Updater adds support for the following:
-
-* Surface Laptop
-* Surface Pro
-
-### Version 2.1.6.0
-*Release date: April 7, 2017*
-
-This version of Surface Dock Updater adds support for the following:
-
-* Update for Surface Dock DisplayPort firmware
-* Requires Windows 10
-
-### Version 2.0.22.0
-*Release date: October 21, 2016*
-
-This version of Surface Dock Updater adds support for the following:
-
-* Update for Surface Dock USB firmware
-* Improved reliability of Ethernet, audio, and USB ports
-
-### Version 1.0.8.0
-*Release date: April 26, 2016*
-
-This version of Surface Dock Updater adds support for the following:
-
-* Update for Surface Dock Main Chipset firmware
-* Update for Surface Dock DisplayPort firmware
-
diff --git a/devices/surface/surface-enterprise-management-mode.md b/devices/surface/surface-enterprise-management-mode.md
deleted file mode 100644
index fc88993c64..0000000000
--- a/devices/surface/surface-enterprise-management-mode.md
+++ /dev/null
@@ -1,268 +0,0 @@
----
-title: Surface Enterprise Management Mode (Surface)
-description: See how this feature of Surface devices with Surface UEFI helps you secure and manage firmware settings within your organization.
-keywords: uefi, configure, firmware, secure, semm
-ms.prod: w10
-ms.mktglfcycl: manage
-ms.pagetype: surface, devices, security
-ms.sitesec: library
-author: coveminer
-ms.author: v-jokai
-ms.topic: article
-ms.reviewer: scottmca
-manager: laurawi
-ms.localizationpriority: medium
-ms.audience: itpro
----
-
-# Microsoft Surface Enterprise Management Mode
-
-Microsoft Surface Enterprise Management Mode (SEMM) is a feature of Surface devices with Surface UEFI that allows you to secure and manage firmware settings within your organization. With SEMM, IT professionals can prepare configurations of UEFI settings and install them on a Surface device. In addition to the ability to configure UEFI settings, SEMM also uses a certificate to protect the configuration from unauthorized tampering or removal.
-
->[!NOTE]
->SEMM is only available on devices with Surface UEFI firmware. This includes most Surface devices including Surface Pro 7, Surface Pro X, and Surface Laptop 3 commercial SKUs with an Intel processor. SEMM is not supported on the 15" Surface Laptop 3 SKU with AMD processor (only available as a retail SKU).
-
-When Surface devices are configured by SEMM and secured with the SEMM certificate, they are considered *enrolled* in SEMM. When the SEMM certificate is removed and control of UEFI settings is returned to the user of the device, the Surface device is considered *unenrolled* in SEMM.
-
-There are two administrative options you can use to manage SEMM and enrolled Surface devices – a standalone tool or integration with Microsoft Endpoint Configuration Manager. The SEMM standalone tool, called the Microsoft Surface UEFI Configurator, is described in this article. For more information about how to manage SEMM with Microsoft Endpoint Configuration Manager, see [Use Microsoft Endpoint Configuration Manager to manage devices with SEMM](https://technet.microsoft.com/itpro/surface/use-system-center-configuration-manager-to-manage-devices-with-semm).
-
-
-## Microsoft Surface UEFI Configurator
-
-The primary workspace of SEMM is Microsoft Surface UEFI Configurator, as shown in Figure 1. Microsoft Surface UEFI Configurator is a tool that is used to create Windows Installer (.msi) packages or WinPE images that are used to enroll, configure, and unenroll SEMM on a Surface device. These packages contain a configuration file where the settings for UEFI are specified. SEMM packages also contain a certificate that is installed and stored in firmware and used to verify the signature of configuration files before UEFI settings are applied.
-
-
-
-*Figure 1. Microsoft Surface UEFI Configurator*
-
-
-You can use the Microsoft Surface UEFI Configurator tool in three modes:
-
-* [Surface UEFI Configuration Package](#configuration-package). Use this mode to create a Surface UEFI configuration package to enroll a Surface device in SEMM and to configure UEFI settings on enrolled devices.
-* [Surface UEFI Reset Package](#reset-package). Use this mode to unenroll a Surface device from SEMM.
-* [Surface UEFI Recovery Request](#recovery-request). Use this mode to respond to a recovery request to unenroll a Surface device from SEMM where a Reset Package operation is not successful.
-
-
-#### Download Microsoft Surface UEFI Configurator
-
-You can download Microsoft Surface UEFI Configurator from the [Surface Tools for IT](https://www.microsoft.com/download/details.aspx?id=46703) page in the Microsoft Download Center.
-
-### Configuration package
-
-Surface UEFI configuration packages are the primary mechanism to implement and manage SEMM on Surface devices. These packages contain a configuration file of UEFI settings specified during creation of the package in Microsoft Surface UEFI Configurator and a certificate file, as shown in Figure 2. When a configuration package is run for the first time on a Surface device that is not already enrolled in SEMM, it provisions the certificate file in the device’s firmware and enrolls the device in SEMM. When enrolling a device in SEMM, you will be prompted to confirm the operation by providing the last two digits of the SEMM certificate thumbprint before the certificate file is stored and the enrollment can complete. This confirmation requires that a user be present at the device at the time of enrollment to perform the confirmation.
-
-
-
-*Figure 2. Secure a SEMM configuration package with a certificate*
-
-See the [Surface Enterprise Management Mode certificate requirements](#surface-enterprise-management-mode-certificate-requirements) section of this article for more information about the requirements for the SEMM certificate.
-
->[!NOTE]
->You can also specify a UEFI password with SEMM that is required to view the **Security**, **Devices**, **Boot Configuration**, or **Enterprise Management** pages of Surface UEFI.
-
-After a device is enrolled in SEMM, the configuration file is read and the settings specified in the file are applied to UEFI. When you run a configuration package on a device that is already enrolled in SEMM, the signature of the configuration file is checked against the certificate that is stored in the device firmware. If the signature does not match, no changes are applied to the device.
-
-### Enable or disable devices in Surface UEFI with SEMM
-
-The following list shows all the available devices you can manage in SEMM:
-
-* Docking USB Port
-* On-board Audio
-* DGPU
-* Type Cover
-* Micro SD Card
-* Front Camera
-* Rear Camera
-* Infrared Camera, for Windows Hello
-* Bluetooth Only
-* Wi-Fi and Bluetooth
-* LTE
-
- >[!NOTE]
->The built-in devices that appear in the UEFI Devices page may vary depending on your device or corporate environment. For example, the UEFI Devices page is not supported on Surface Pro X; LTE only appears on LTE-equipped devices.
-### Configure advanced settings with SEMM
-**Table 1. Advanced settings**
-
-| Setting | Description |
-| ---------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| IPv6 for PXE Boot | Allows you to manage Ipv6 support for PXE boot. If you do not configure this setting, IPv6 support for PXE boot is disabled. |
-| Alternate Boot | Allows you to manage use of an Alternate boot order to boot directly to a USB or Ethernet device by pressing both the Volume Down button and Power button during boot. If you do not configure this setting, Alternate boot is enabled. |
-| Boot Order Lock | Allows you to lock the boot order to prevent changes. If you do not configure this setting, Boot Order Lock is disabled. |
-| USB Boot | Allows you to manage booting to USB devices. If you do not configure this setting, USB Boot is enabled. |
-| Network Stack | Allows you to manage Network Stack boot settings. If you do not configure this setting, the ability to manage Network Stack boot settings is disabled. |
-| Auto Power On | Allows you to manage Auto Power On boot settings. If you do not configure this setting, Auto Power on is enabled. |
-| Simultaneous Multi-Threading (SMT) | Allows you to manage Simultaneous Multi-Threading (SMT) to enable or disable hyperthreading. If you do not configure this setting, SMT is enabled. |
-|Enable Battery limit| Allows you to manage Battery limit functionality. If you do not configure this setting, Battery limit is enabled |
-| Security | Displays the Surface UEFI **Security** page. If you do not configure this setting, the Security page is displayed. |
-| Devices | Displays the Surface UEFI **Devices** page. If you do not configure this setting, the Devices page is displayed. |
-| Boot | Displays the Surface UEFI **Boot** page. If you do not configure this setting, the DateTime page is displayed. |
-| DateTime | Displays the Surface UEFI **DateTime** page. If you do not configure this setting, the DateTime page is displayed. |
-
-
-
->[!NOTE]
->When you create a SEMM configuration package, two characters are shown on the **Successful** page, as shown in Figure 3.
-
-
-
-*Figure 3. Display of the last two characters of the certificate thumbprint on the Successful page*
-
-These characters are the last two characters of the certificate thumbprint and should be written down or recorded. The characters are required to confirm enrollment in SEMM on a Surface device, as shown in Figure 4.
-
-
-
-*Figure 4. Enrollment confirmation in SEMM with the SEMM certificate thumbprint*
-
->[!NOTE]
->Administrators with access to the certificate file (.pfx) can read the thumbprint at any time by opening the .pfx file in CertMgr. To view the thumbprint with CertMgr, follow this process:
->1. Right-click the .pfx file, and then click **Open**.
->2. Expand the folder in the navigation pane.
->3. Click **Certificates**.
->4. Right-click your certificate in the main pane, and then click **Open**.
->5. Click the **Details** tab.
->6. **All** or **Properties Only** must be selected in the **Show** drop-down menu.
->7. Select the field **Thumbprint**.
-
-To enroll a Surface device in SEMM or to apply the UEFI configuration from a configuration package, all you need to do is run the .msi file with administrative privileges on the intended Surface device. You can use application deployment or operating system deployment technologies such as [Microsoft Endpoint Configuration Manager](https://technet.microsoft.com/library/mt346023) or the [Microsoft Deployment Toolkit](https://technet.microsoft.com/windows/dn475741). When you enroll a device in SEMM you must be present to confirm the enrollment on the device. User interaction is not required when you apply a configuration to devices that are already enrolled in SEMM.
-
-For a step-by-step walkthrough of how to enroll a Surface device in SEMM or apply a Surface UEFI configuration with SEMM, see [Enroll and configure Surface devices with SEMM](https://technet.microsoft.com/itpro/surface/enroll-and-configure-surface-devices-with-semm).
-
-### Reset package
-
-A Surface UEFI reset package is used to perform only one task — to unenroll a Surface device from SEMM. The reset package contains signed instructions to remove the SEMM certificate from the device’s firmware and to reset UEFI settings to factory default. Like a Surface UEFI configuration package, a reset package must be signed with the same SEMM certificate that is provisioned on the Surface device. When you create a SEMM reset package, you are required to supply the serial number of the Surface device you intend to reset. SEMM reset packages are not universal and are specific to one device.
-
-### Recovery request
-
-In some scenarios, it may be impossible to use a Surface UEFI reset package. (For example, if Windows becomes unusable on the Surface device.) In these scenarios you can unenroll the Surface device from SEMM through the **Enterprise Management** page of Surface UEFI (shown in Figure 5) with a Recovery Request operation.
-
-
-
-*Figure 5. Initiate a SEMM recovery request on the Enterprise Management page*
-
-When you use the process on the **Enterprise Management** page to reset SEMM on a Surface device, you are provided with a Reset Request. This Reset Request can be saved as a file to a USB drive, copied as text, or read as a QR Code with a mobile device to be easily emailed or messaged. Use the Microsoft Surface UEFI Configurator Reset Request option to load a Reset Request file or enter the Reset Request text or QR Code. Microsoft Surface UEFI Configurator will generate a verification code that can be entered on the Surface device. If you enter the code on the Surface device and click **Restart**, the device will be unenrolled from SEMM.
-
->[!NOTE]
->A Reset Request expires two hours after it is created.
-
-For a step-by-step walkthrough of how to unenroll Surface devices from SEMM, see [Unenroll Surface devices from SEMM](https://technet.microsoft.com/itpro/surface/unenroll-surface-devices-from-semm).
-
-## Surface Enterprise Management Mode certificate requirements
-
->[!NOTE]
->The SEMM certificate is required to perform any modification to SEMM or Surface UEFI settings on enrolled Surface devices. If the SEMM certificate is corrupted or lost, SEMM cannot be removed or reset. Manage your SEMM certificate accordingly with an appropriate solution for backup and recovery.
-
-Packages created with the Microsoft Surface UEFI Configurator tool are signed with a certificate. This certificate ensures that after a device is enrolled in SEMM, only packages created with the approved certificate can be used to modify the settings of UEFI. The following settings are recommended for the SEMM certificate:
-
-* **Key Algorithm** – RSA
-* **Key Length** – 2048
-* **Hash Algorithm** – SHA-256
-* **Type** – SSL Server Authentication
-* **Key Usage** – Digital signature, Key Encipherment
-* **Provider** – Microsoft Enhanced RSA and AES Cryptographic Provider
-* **Expiration Date** – 15 Months from certificate creation
-* **Key Export Policy** – Exportable
-
-It is also recommended that the SEMM certificate be authenticated in a two-tier public key infrastructure (PKI) architecture where the intermediate certification authority (CA) is dedicated to SEMM, enabling certificate revocation. For more information about a two-tier PKI configuration, see [Test Lab Guide: Deploying an AD CS Two-Tier PKI Hierarchy](https://technet.microsoft.com/library/hh831348).
-
->[!NOTE]
->You can use the following PowerShell script to create a self-signed certificate for use in proof-of-concept scenarios.
- > To use this script, copy the following text into Notepad and save the file as a PowerShell script (.ps1). This script creates a certificate with a password of `12345678`.
The certificate generated by this script is not recommended for production environments.
-
- ```
-if (-not (Test-Path "Demo Certificate")) { New-Item -ItemType Directory -Force -Path "Demo Certificate" }
-if (Test-Path "Demo Certificate\TempOwner.pfx") { Remove-Item "Demo Certificate\TempOwner.pfx" }
-
-# Generate the Ownership private signing key with password 12345678
-$pw = ConvertTo-SecureString "12345678" -AsPlainText -Force
-
-$TestUefiV2 = New-SelfSignedCertificate `
- -Subject "CN=Surface Demo Kit, O=Contoso Corporation, C=US" `
- -Type SSLServerAuthentication `
- -HashAlgorithm sha256 `
- -KeyAlgorithm RSA `
- -KeyLength 2048 `
- -KeyUsage KeyEncipherment `
- -KeyUsageProperty All `
- -Provider "Microsoft Enhanced RSA and AES Cryptographic Provider" `
- -NotAfter (Get-Date).AddYears(25) `
- -TextExtension @("2.5.29.37={text}1.2.840.113549.1.1.1") `
- -KeyExportPolicy Exportable
-
-$TestUefiV2 | Export-PfxCertificate -Password $pw -FilePath "Demo Certificate\TempOwner.pfx"
- ```
-
-For use with SEMM and Microsoft Surface UEFI Configurator, the certificate must be exported with the private key and with password protection. Microsoft Surface UEFI Configurator will prompt you to select the SEMM certificate file (.pfx) and certificate password when it is required.
-
->[!NOTE]
->For organizations that use an offline root in their PKI infrastructure, Microsoft Surface UEFI Configurator must be run in an environment connected to the root CA to authenticate the SEMM certificate. The packages generated by Microsoft Surface UEFI Configurator can be transferred as files and therefore can be transferred outside the offline network environment with removable storage, such as a USB stick.
-
-### Managing certificates FAQ
-
-The recommended *minimum* length is 15 months. You can use a
-certificate that expires in less than 15 months or use a certificate
-that expires in longer than 15 months.
-
->[!NOTE]
->When a certificate expires, it does not automatically renew.
-
-**Will existing machines continue to apply the bios settings after 15
-months?**
-
-Yes, but only if the package itself was signed when the certificate was
-valid.
-
-**Will** **the SEMM package and certificate need to be updated on all
-machines that have it?**
-
-If you want SEMM reset or recovery to work, the certificate needs to be
-valid and not expired.
-
-**Can bulk reset packages be created for each surface that we order? Can
-one be built that resets all machines in our environment?**
-
-The PowerShell samples that create a config package for a specific
-device type can also be used to create a reset package that is
-serial-number independent. If the certificate is still valid, you can
-create a reset package using PowerShell to reset SEMM.
-
-## Version History
-
-### Version 2.59.
-* Support to Surface Pro 7, Surface Pro X, and Surface Laptop 3 13.5" and 15" models with Intel processor. Note: Surface Laptop 3 15" AMD processor is not supported.
-- Support to Wake on Power feature
-
-### Version 2.54.139.0
-* Support to Surface Hub 2S
-* Bug fixes
-
-### Version 2.43.136.0
-* Support to enable/disable simulatenous multithreating
-* Separate options for WiFi and Bluetooth for some devices
-* Battery Limit removed for Surface Studio
-
-### Version 2.26.136.0
-* Add support to Surface Studio 2
-* Battery Limit feature
-
-### Version 2.21.136.0
-* Add support to Surface Pro 6
-* Add support to Surface Laptop 2
-
-### Version 2.14.136.0
-* Add support to Surface Go
-
-### Version 2.9.136.0
-* Add support to Surface Book 2
-* Add support to Surface Pro LTE
-* Accessibility improvements
-
-### Version 1.0.74.0
-* Add support to Surface Laptop
-* Add support to Surface Pro
-* Bug fixes and general improvement
-
-## Related topics
-
-[Enroll and configure Surface devices with SEMM](enroll-and-configure-surface-devices-with-semm.md)
-
-[Unenroll Surface devices from SEMM](unenroll-surface-devices-from-semm.md)
diff --git a/devices/surface/surface-manage-dfci-guide.md b/devices/surface/surface-manage-dfci-guide.md
deleted file mode 100644
index f21805f1a7..0000000000
--- a/devices/surface/surface-manage-dfci-guide.md
+++ /dev/null
@@ -1,188 +0,0 @@
----
-title: Intune management of Surface UEFI settings
-description: This article explains how to configure a DFCI environment in Microsoft Intune and manage firmware settings for targeted Surface devices.
-ms.localizationpriority: medium
-ms.prod: w10
-ms.mktglfcycl: manage
-ms.sitesec: library
-author: coveminer
-ms.author: v-jokai
-ms.topic: article
-ms.date: 11/13/2019
-ms.reviewer: jesko
-manager: laurawi
-ms.audience: itpro
----
-# Intune management of Surface UEFI settings
-
-## Introduction
-
-The ability to manage devices from the cloud has dramatically simplified IT deployment and provisioning across the lifecycle. With Device Firmware Configuration Interface (DFCI) profiles built into Microsoft Intune (now available in [public preview](https://docs.microsoft.com/intune/configuration/device-firmware-configuration-interface-windows)), Surface UEFI management extends the modern management stack down to the UEFI hardware level. DFCI supports zero-touch provisioning, eliminates BIOS passwords, provides control of security settings including boot options and built-in peripherals, and lays the groundwork for advanced security scenarios in the future. For answers to frequently asked questions, see [Ignite 2019: Announcing remote management of Surface UEFI settings from Intune](https://techcommunity.microsoft.com/t5/Surface-IT-Pro-Blog/Ignite-2019-Announcing-remote-management-of-Surface-UEFI/ba-p/978333).
-
-### Background
-
-Like any computer running Windows 10, Surface devices rely on code stored in the SoC that enables the CPU to interface with hard drives, display devices, USB ports, and other devices. The programs stored in this read-only memory (ROM) are known as firmware (while programs stored in dynamic media are known as software).
-
-In contrast to other Windows 10 devices available in the market today, Surface provides IT admins with the ability to configure and manage firmware through a rich set of UEFI configuration settings. This provides a layer of hardware control on top of software-based policy management as implemented via mobile device management (MDM) policies, Configuration Manager or Group Policy. For example, organizations deploying devices in highly secure areas with sensitive information can prevent camera use by removing functionality at the hardware level. From a device standpoint, turning the camera off via a firmware setting is equivalent to physically removing the camera. Compare the added security of managing at the firmware level to relying only on operating system software settings. For example, if you disable the Windows audio service via a policy setting in a domain environment, a local admin could still re-enable the service.
-
-### DFCI versus SEMM
-
-Until now, managing firmware required enrolling devices into Surface Enterprise Management Mode (SEMM) with the overhead of ongoing manual IT-intensive tasks. As an example, SEMM requires IT staff to physically access each PC to enter a two-digit pin as part of the certificate management process. Although SEMM remains a good solution for organizations in a strictly on-premises environment, its complexity and IT-intensive requirements make it costly to use.
-
-Now with newly integrated UEFI firmware management capabilities in Microsoft Intune, the ability to lock down hardware is simplified and easier to use with new features for provisioning, security, and streamlined updating all in a single console, now unified as [Microsoft Endpoint Manager](https://www.microsoft.com/microsoft-365/microsoft-endpoint-manager). The following figure shows UEFI settings viewed directly on the device (left) and viewed in the Endpoint Manager console (right).
-
-
-
-Crucially, DFCI enables zero touch management, eliminating the need for manual interaction by IT admins. DFCI is deployed via Windows Autopilot using the device profiles capability in Intune. A device profile allows you to add and configure settings which can then be deployed to devices enrolled in management within your organization. Once the device receives the device profile, the features and settings are applied automatically. Examples of common device profiles include Email, Device restrictions, VPN, Wi-Fi, and Administrative templates. DFCI is simply an additional device profile that enables you to manage UEFI configuration settings from the cloud without having to maintain on-premises infrastructure.
-
-## Supported devices
-
-At this time, DFCI is supported in the following devices:
-
-- Surface Pro 7
-- Surface Pro X
-- Surface Laptop 3
-
-> [!NOTE]
-> Surface Pro X does not support DFCI settings management for built-in camera, audio, and Wi-Fi/Bluetooth.
-
-## Prerequisites
-
-- Devices must be registered with Windows Autopilot by a [Microsoft Cloud Solution Provider (CSP) partner](https://partner.microsoft.com/membership/cloud-solution-provider) or OEM distributor.
-
-- Before configuring DFCI for Surface, you should be familiar with Autopilot configuration requirements in [Microsoft Intune](https://docs.microsoft.com/intune/) and [Azure Active Directory](https://docs.microsoft.com/azure/active-directory/) (Azure AD).
-
-## Before you begin
-
-Add your target Surface devices to an Azure AD security group. For more information about creating and managing security groups, refer to [Intune documentation](https://docs.microsoft.com/intune/configuration/device-firmware-configuration-interface-windows#create-your-azure-ad-security-groups).
-
-## Configure DFCI management for Surface devices
-
-A DFCI environment requires setting up a DFCI profile that contains the settings and an Autopilot profile to apply the settings to registered devices. An enrollment status profile is also recommended to ensure settings are pushed down during OOBE setup when users first start the device. This guide explains how to configure the DFCI environment and manage UEFI configuration settings for targeted Surface devices.
-
-## Create DFCI profile
-
-Before configuring DFCI policy settings, first create a DFCI profile and assign it to the Azure AD security group that contains your target devices.
-
-1. Sign into your tenant at devicemanagement.microsoft.com.
-2. In the Microsoft Endpoint Manager Admin Center, select **Devices > Configuration profiles > Create profile** and enter a name; for example, **DFCI Configuration Policy.**
-3. Select **Windows 10 and later** for platform type.
-4. In the Profile type drop down list, select **Device Firmware Configuration Interface** to open the DFCI blade containing all available policy settings. For information on DFCI settings, refer to Table 1 on this page or the [Intune documentation](https://docs.microsoft.com/intune/configuration/device-firmware-configuration-interface-windows). You can configure DFCI settings during the initial setup process or later by editing the DFCI profile.
-
- 
-
-5. Click **OK** and then select **Create**.
-6. Select **Assignments** and under **Select groups to include** select the Azure AD security group that contains your target devices, as shown in the following figure. Click **Save**.
-
- 
-
-## Create Autopilot profile
-
-1. In Endpoint Manager at devicemanagement.microsoft.com, select **devices > Windows enrollment** and scroll down to **Deployment profiles**.
-2. Select **Create profile** and enter a name; for example, **My Autopilot profile**, and select **Next**.
-3. Select the following settings:
-
- - Deployment mode: **User-Driven**.
- - Join type: Azure **AD joined**.
-
-4. Leave the remaining default settings unchanged and select **Next**, as shown in the following figure.
-
- 
-
-5. On the Assignments page, choose **Select groups to include** and click your Azure AD security group. Select **Next**.
-6. Accept the summary and then select **Create**. The Autopilot profile is now created and assigned to the group.
-
-## Configure Enrollment Status Page
-
-To ensure that devices apply the DFCI configuration during OOBE before users sign in, you need to configure enrollment status.
-
-For more information, refer to [Set up an enrollment status page](https://docs.microsoft.com/intune/enrollment/windows-enrollment-status).
-
-
-## Configure DFCI settings on Surface devices
-
-DFCI includes a streamlined set of UEFI configuration policies that provide an extra level of security by locking down devices at the hardware level. DFCI is designed to be used in conjunction with mobile device management settings at the software level. Note that DFCI settings only affect hardware components built into Surface devices and do not extend to attached peripherals such as USB webcams. (However, you can use Device restriction policies in Intune to turn off access to attached peripherals at the software level).
-
-You configure DFCI policy settings by editing the DFCI profile from Endpoint Manager, as shown in the figure below.
-
-- In Endpoint Manager at devicemanagement.microsoft.com, select **Devices > Windows > Configuration Profiles > “DFCI profile name” > Properties > Settings**.
-
- 
-
-### Block user access to UEFI settings
-
-For many customers, the ability to block users from changing UEFI settings is critically important and a primary reason to use DFCI. As listed in Table 1, this is managed via the setting **Allow local user to change UEFI settings**. If you do not edit or configure this setting, local users will be able to change any UEFI setting not managed by Intune. Therefore, it’s highly recommended to disable **Allow local user to change UEFI settings.**
-The rest of the DFCI settings enable you to turn off functionality that would otherwise be available to users. For example, if you need to protect sensitive information in highly secure areas, you can disable the camera, and if you don’t want users booting from USB drives, you can disable that also.
-
-### Table 1. DFCI scenarios
-
-| Device management goal | Configuration steps |
-| --------------------------------------------- | --------------------------------------------------------------------------------------------- |
-| Block local users from changing UEFI settings | Under **Security Features > Allow local user to change UEFI settings**, select **None**. |
-| Disable cameras | Under **Built in Hardware > Cameras**, select **Disabled**. |
-| Disable Microphones and speakers | Under **Built in Hardware > Microphones and speakers**, select **Disabled**. |
-| Disable radios (Bluetooth, Wi-Fi) | Under **Built in Hardware > Radios (Bluetooth, Wi-Fi, etc…)**, select **Disabled**. |
-| Disable Boot from external media (USB, SD) | Under **Built in Hardware > Boot Options > Boot from external media (USB, SD)**, select **Disabled**. |
-
-> [!CAUTION]
-> The **Disable radios (Bluetooth, Wi-Fi)** setting should only be used on devices that have a wired Ethernet connection.
-
-> [!NOTE]
-> DFCI in Intune includes two settings that do not currently apply to Surface devices: (1) CPU and IO virtualization and (2) Disable Boot from network adapters.
-
-Intune provides Scope tags to delegate administrative rights and Applicability Rules to manage device types. For more information about policy management support and full details on all DFCI settings, refer to [Microsoft Intune documentation](https://docs.microsoft.com/intune/configuration/device-firmware-configuration-interface-windows).
-
-## Register devices in Autopilot
-
-As stated above, DFCI can only be applied on devices registered in Windows Autopilot by your reseller or distributor and is only supported, at this time, on Surface Pro 7, Surface Pro X, and Surface Laptop 3. For security reasons, it’s not possible to “self-provision” your devices into Autopilot.
-
-## Manually Sync Autopilot devices
-
-Although Intune policy settings typically get applied almost immediately, there may be a delay of 10 minutes before the settings take effect on targeted devices. In rare circumstances, delays of up to 8 hours are possible. To ensure settings apply as soon as possible, (such as in test scenarios), you can manually sync the target devices.
-
-- In Endpoint Manager at devicemanagement.microsoft.com, go to **Devices > Device enrollment > Windows enrollment > Windows Autopilot Devices** and select **Sync**.
-
- For more information, refer to [Sync your Windows device manually](https://docs.microsoft.com/intune-user-help/sync-your-device-manually-windows).
-
-> [!NOTE]
-> When adjusting settings directly in UEFI, you need to ensure the device fully restarts to the standard Windows login.
-
-## Verifying UEFI settings on DFCI-managed devices
-
-In a test environment, you can verify settings in the Surface UEFI interface.
-
-1. Open Surface UEFI, which involves pressing the **Volume +** and **Power** buttons at the same time.
-2. Select **Devices**. The UEFI menu will reflect configured settings, as shown in the following figure.
-
- 
-
- Note how:
-
- - The settings are greyed out because **Allow local user to change UEFI setting** is set to None.
- - Audio is set to off because **Microphones and speakers** are set to **Disabled**.
-
-## Removing DFCI policy settings
-
-When you create a DFCI profile, all configured settings will remain in effect across all devices within the profile’s scope of management. You can only remove DFCI policy settings by editing the DFCI profile directly.
-
-If the original DFCI profile has been deleted, you can remove policy settings by creating a new profile and then editing the settings, as appropriate.
-
-## Removing DFCI management
-
-**To remove DFCI management and return device to factory new state:**
-
-1. Retire the device from Intune:
- 1. In Endpoint Manager at devicemanagement.microsoft.com, choose **Groups > All Devices**. Select the devices you want to retire, and then choose **Retire/Wipe.** To learn more refer to [Remove devices by using wipe, retire, or manually unenrolling the device](https://docs.microsoft.com/intune/remote-actions/devices-wipe).
-2. Delete the Autopilot registration from Intune:
- 1. Choose **Device enrollment > Windows enrollment > Devices**.
- 2. Under Windows Autopilot devices, choose the devices you want to delete, and then choose **Delete**.
-3. Connect device to wired internet with Surface-branded ethernet adapter. Restart device and open the UEFI menu (press and hold the volume-up button while also pressing and releasing the power button).
-4. Select **Management > Configure > Refresh from Network** and then choose **Opt-out.**
-
-To keep managing the device with Intune, but without DFCI management, self-register the device to Autopilot and enroll it to Intune. DFCI will not be applied to self-registered devices.
-
-## Learn more
-- [Ignite 2019: Announcing remote management of Surface UEFI settings from Intune](https://techcommunity.microsoft.com/t5/Surface-IT-Pro-Blog/Ignite-2019-Announcing-remote-management-of-Surface-UEFI/ba-p/978333)
-[Windows Autopilot](https://www.microsoft.com/microsoft-365/windows/windows-autopilot)
-- [Windows Autopilot and Surface devices](windows-autopilot-and-surface-devices.md)
-- [Use DFCI profiles on Windows devices in Microsoft Intune](https://docs.microsoft.com/intune/configuration/device-firmware-configuration-interface-windows)
diff --git a/devices/surface/surface-pro-arm-app-management.md b/devices/surface/surface-pro-arm-app-management.md
deleted file mode 100644
index f3d922c048..0000000000
--- a/devices/surface/surface-pro-arm-app-management.md
+++ /dev/null
@@ -1,174 +0,0 @@
----
-title: Deploying, managing, and servicing Surface Pro X
-description: This article provides an overview of key considerations for deploying, managing, and servicing Surface Pro X.
-ms.prod: w10
-ms.mktglfcycl: manage
-ms.localizationpriority: high
-ms.sitesec: library
-author: coveminer
-ms.author: v-jokai
-ms.topic: article
-ms.date: 4/15/2020
-ms.reviewer: jessko
-manager: laurawi
-ms.audience: itpro
----
-# Deploying, managing, and servicing Surface Pro X
-
-## Introduction
-
-Built to handle high performance commercial requirements, Surface Pro X breaks new ground by incorporating the most powerful processor ever released on an ARM device, the Microsoft SQ1 ARM chipset.
-
-Powered by a 3GHz CPU and a 2.1 teraflop GPU, Surface Pro X provides a full Windows experience. Its 13-hour battery life and built-in 4G LTE make it ideally suited for mobile first-line workers and professionals across the financial, legal, and medical fields or any role demanding extended battery life and continuous connectivity capabilities.
-
-Surface Pro X is designed almost exclusively for a modern, cloud-based environment centered around Microsoft 365, Intune and Windows Autopilot. This article highlights what that looks like and outlines key considerations for deploying, managing, and servicing Surface Pro X.
-
-## Deploying Surface Pro X
-
-For the best experience, deploy Surface Pro X using Windows Autopilot either with the assistance of a Microsoft Cloud Solution Provider or self-provisioned using Autopilot deployment profiles and related features. For more information, refer to:
-
-- [Windows Autopilot and Surface devices](windows-autopilot-and-surface-devices.md)
-- [Overview of Windows Autopilot](https://docs.microsoft.com/windows/deployment/windows-autopilot/windows-autopilot)
-
-Autopilot deployment has several advantages: It allows you to use the factory provisioned operating system, streamlined for zero-touch deployment, to include pre-installation of Office Pro Plus.
-
-Organizations already using modern management, security, and productivity solutions are well positioned to take advantage of the unique performance features in Surface Pro X. Customers using modernized line of business apps, Microsoft store (UWP) apps, or remote desktop solutions also stand to benefit.
-
-## Image-based deployment considerations
-
-Microsoft Deployment Toolkit (MDT) and Microsoft Endpoint Configuration Manager (formerly System Center Configuration Manager) currently do not support Surface Pro X for operating system deployment. Customers relying on image-based deployment should consider Surface Pro 7 while they continue to evaluate the right time to transition to the cloud.
-
-## Managing Surface Pro X devices
-
-### Intune
-
-A component of Microsoft Enterprise Mobility + Security, Intune integrates with Azure Active Directory for identity and access control and provides granular management of enrolled Surface Pro X devices. Intune mobile device management (MDM) policies have a number of advantages over older on-premises tools such as Windows Group Policy. This includes faster device login times and a more streamlined catalog of policies enabling full device management from the cloud. For example, you can manage LTE using eSIM profiles to configure data plans and deploy activation codes to multiple devices.
-
-For more information about using Intune, refer to the [Intune documentation](https://docs.microsoft.com/intune/).
-
-### Co-management
-
-Once deployed in Autopilot, you can join Surface Pro X devices to Azure AD or Active Directory (Hybrid Azure AD Join) where you will be able to manage the devices with Intune or co-manage them with Endpoint Configuration Manager, which will install the 32-bit x86 ConfigMgr client.
-
-### Third party MDM solutions
-
-You may be able to use third-party MDM tools to manage Surface Pro X devices. For details, contact your MDM provider.
-
-### Antivirus software
-
-Windows Defender will help protect Windows 10 on ARM-based PCs for the supported lifetime of the Windows 10 device.
-
-Some third-party antivirus software cannot be installed on a Windows 10 PC running on an ARM-based processor. Collaboration with third-party antivirus software providers is continuing for AV app readiness on ARM-based PCs. Contact your antivirus software provider to understand when their apps will be available.
-
-## Servicing Surface Pro X
-
-Surface Pro X supports Windows 10, version 1903 and later. As an ARM-based device, it has specific requirements for maintaining the latest drivers and firmware.
-
-Surface Pro X was designed to use Windows Update to simplify the process of keeping drivers and firmware up to date for both home users and small business users. Use the default settings to receive Automatic updates. To verify:
-
-1. Go to **Start** > **Settings > Update & Security > Windows Update** > **Advanced Options.**
-2. Under **Choose how updates are installed,** select **Automatic (recommended)**.
-
-### Recommendations for commercial customers
-
-- Use Windows Update or Windows Update for Business for maintaining the latest drivers and firmware. For more information, see [Deploy Updates using Windows Update for Business](https://docs.microsoft.com/windows/deployment/update/waas-manage-updates-wufb).
-- If your procedures require using a Windows Installer .msi file, contact [Surface for Business support](https://support.microsoft.com/help/4037645).
-- For more information about deploying and managing updates on Surface devices, see [Manage and deploy Surface driver and firmware updates](manage-surface-driver-and-firmware-updates.md).
-- Note that Windows Server Update Services (WSUS) does not support the ability to deliver drivers and firmware to Surface Pro X.
-
-## Running apps on Surface Pro X
-
-Most apps run on ARM-based Windows 10 PCs with limited exclusions.
-
-### Supported apps
-
-- Most x86 Win32 apps run on Surface Pro X.
-- Native ARM64 and Microsoft Store UWP apps provide an excellent user experience utilizing the full native speed of the ARM-based processor while optimizing battery life.
-- Apps that use drivers designed for a Windows 10 PC running on an ARM-based processor.
-
-### Not supported
-
-- x64 apps won't run on a Windows 10 PC on an ARM-based processor.
-
-For more information about running apps on Surface Pro X, refer to:
-
-- [Windows 10 ARM-based PCs Support FAQ](https://support.microsoft.com/help/4521606)
-- [Windows 10 on ARM documentation](https://docs.microsoft.com/windows/arm)
-
-## Virtual Desktops (VDI)
-
-Windows Virtual Desktop enables access to Windows desktops,applications, and data on any computing device or platform, from any location. To learn more, refer to the [Windows Virtual Desktop site](https://aka.ms/wvd).
-
-## Browsing with Surface Pro X
-
-Popular browsers run on Surface Pro X:
-
-- In-box Edge, Firefox, Chrome, and Internet Explorer all run on Surface Pro X.
-- In-box Edge and Firefox run natively and therefore have enhanced performance on a Windows 10 PC on an ARM-based processor.
-
-## Installing and using Microsoft Office
-
-- Use Office 365 for the best experience on a Windows 10 PC on an ARM-based processor.
-- Office 365 "click-to-run" installs Outlook, Word, Excel, and PowerPoint, optimized to run on a Windows 10 PC on an ARM-based processor.
-- Microsoft Teams runs great on Surface Pro X.
-- For "perpetual versions" of Office such as Office 2019, install the 32-bit version.
-
-## VPN
-
-To confirm if a specific third-party VPN supports a Windows 10 PC on an ARM-based processor, contact the VPN provider.
-
-## Comparing key features
-
-The following tables show the availability of selected key features on Surface Pro X with Windows 10 on ARM compared to Intel-based Surface Pro 7.
-
-| Deployment | Surface Pro 7 | Surface Pro X | Notes |
-| --------------------------------------- | ------------- | ------------- | ------------------------------------------------------------------------------------------------------------------------------- |
-| Windows Autopilot | Yes | Yes | |
-| Support for Network Boot (PXE) | Yes | No | |
-| Windows Configuration Designer | Yes | No | Not recommended for Surface Pro X. |
-| WinPE | Yes | Yes | Not recommended for Surface Pro X. Microsoft does not provide the necessary .ISO and drivers to support WinPE with Surface Pro X. |
-| Endpoint Configuration Manager: Operating System Deployment (OSD) | Yes | No | Not supported on Surface Pro X. |
-| MDT | Yes | No | Not supported on Surface Pro X. |
-
-
-| Management | Surface Pro 7 | Surface Pro X | Notes |
-| --------------------------------------------- | ------------------- | ------------- | ------------------------------------------------------------------------------------- |
-| Intune | Yes | Yes | Manage LTE with eSIM profiles. |
-| Windows Autopilot | Yes | Yes | |
-| Azure AD (co-management) | Yes | Yes | Ability to join Surface Pro X to Azure AD or Active Directory (Hybrid Azure AD Join). |
-| Endpoint Configuration Manager | Yes | Yes | |
-| Power on When AC Restore | Yes | Yes | |
-| Surface Diagnostic Toolkit (SDT) for Business | Yes | Yes | |
-| Surface Dock Firmware Update | Yes | Yes | |
-| Asset Tag Utility | Yes | Yes | |
-| Surface Enterprise management Mode (SEMM) | Yes | Partial | No option to disable hardware on Surface Pro X at the firmware level. |
-| Surface UEFI Configurator | Yes | | No option to disable hardware. on Surface Pro X at the firmware level. |
-| Surface UEFI Manager | Yes | Partial | No option to disable hardware on Surface Pro X at the firmware level. |
-
-
-| Security | Surface Pro 7 | Surface Pro X | Notes |
-| --------------------------------- | ------------- | ------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| BitLocker | Yes | Yes | |
-| Windows Defender | Yes | Yes | |
-| Support for third-party antivirus | Yes | See note |Some third-party antivirus software cannot be installed on a Windows 10 PC running on an ARM-based processor. Collaboration with third-party antivirus software providers is continuing for AV app readiness on ARM-based PCs. Contact your antivirus software provider to understand when their apps will be available. |
-| Conditional Access | Yes | Yes | |
-| Secure Boot | Yes | Yes | |
-| Windows Information Protection | Yes | Yes | |
-| Surface Data Eraser (SDE) | Yes | Yes |
-## FAQ
-
-### Can I deploy Surface Pro X with MDT or Endpoint Configuration Manager?
-
-The Microsoft Deployment Toolkit (MDT) and Microsoft Endpoint Configuration Manager currently do not support Surface Pro X for operating system deployment.Customers relying on image-based deployment should consider Surface Pro 7 while they continue to evaluate the right time to transition to the cloud.
-
-### How can I deploy Surface Pro X?
-
-Deploy Surface Pro X using Windows Autopilot.
-
-### Will a BMR be available?
-
-Yes.
-
-### Is Intune required to manage Surface Pro X?
-
-Intune is recommended but not required. Once deployed in Autopilot, you can join Surface Pro X devices to Azure AD or Active Directory (Hybrid Azure AD Join) where you will be able to manage the devices with Intune or co-manage them with Endpoint Configuration Manager, which will install the 32-bit x86 ConfigMgr client.
diff --git a/devices/surface/surface-pro-arm-app-performance.md b/devices/surface/surface-pro-arm-app-performance.md
deleted file mode 100644
index 4459d6052b..0000000000
--- a/devices/surface/surface-pro-arm-app-performance.md
+++ /dev/null
@@ -1,27 +0,0 @@
----
-title: Surface Pro X app compatibility
-description: This article provides introductory app compatibility information for Surface Pro X ARM-based PCs.
-ms.prod: w10
-ms.localizationpriority: medium
-ms.mktglfcycl: manage
-ms.sitesec: library
-author: coveminer
-ms.author: v-jokai
-ms.topic: article
-ms.date: 10/03/2019
-ms.reviewer: jessko
-manager: laurawi
-ms.audience: itpro
----
-# Surface Pro X app compatibility
-
-Applications run differently on ARM-based Windows 10 PCs such as Surface Pro X. Limitations include the following:
-
-- **Drivers for hardware, games and apps will only work if they're designed for a Windows 10 ARM-based PC**. For more info, check with the hardware manufacturer or the organization that developed the driver. Drivers are software programs that communicate with hardware devices—they're commonly used for antivirus and antimalware software, printing or PDF software, assistive technologies, CD and DVD utilities, and virtualization software. If a driver doesn’t work, the app or hardware that relies on it won’t work either (at least not fully). Peripherals and devices only work if the drivers they depend on are built into Windows 10, or if the hardware developer has released ARM64 drivers for the device.
-- **64-bit (x64) apps won’t work**. You'll need 64-bit (ARM64) apps, 32-bit (ARM32) apps, or 32-bit (x86) apps. You can usually find 32-bit (x86) versions of apps, but some app developers only offer 64-bit (x64) apps.
-- **Certain games won’t work**. Games and apps won't work if they use a version of OpenGL greater than 1.1, or if they rely on "anti-cheat" drivers that haven't been made for Windows 10 ARM-based PCs. Check with your game publisher to see if a game will work.
-- **Apps that customize the Windows experience might have problems**. This includes some input method editors (IMEs), assistive technologies, and cloud storage apps. The organization that develops the app determines whether their app will work on a Windows 10 ARM-based PC.
-- **Some third-party antivirus software can’t be installed**. You won't be able to install some third-party antivirus software on a Windows 10 ARM-based PC. However, Windows Security will help keep you safe for the supported lifetime of your Windows 10 device.
-- **Windows Fax and Scan isn’t available**. This feature isn’t available on a Windows 10 ARM-based PC.
-
-For more information about app compatibility, refer to [Windows 10 ARM-based PCs FAQ](https://support.microsoft.com/en-us/help/4521606)
diff --git a/devices/surface/surface-system-sku-reference.md b/devices/surface/surface-system-sku-reference.md
deleted file mode 100644
index c0de20193f..0000000000
--- a/devices/surface/surface-system-sku-reference.md
+++ /dev/null
@@ -1,72 +0,0 @@
----
-title: System SKU reference (Surface)
-description: See a reference of System Model and System SKU names.
-keywords: uefi, configure, firmware, secure, semm
-ms.prod: w10
-ms.mktglfcycl: manage
-ms.pagetype: surface, devices, security
-ms.sitesec: library
-author: coveminer
-ms.author: v-jokai
-ms.topic: article
-ms.date: 03/09/2020
-ms.reviewer:
-manager: laurawi
-ms.localizationpriority: medium
-ms.audience: itpro
----
-
-# System SKU reference
-
-This document provides a reference of System Model and System SKU names that you can use to quickly determine the machine state of a specific device by using PowerShell or WMI.
-
-System Model and System SKU are variables that are stored in the System Management BIOS (SMBIOS) tables in the UEFI layer of Surface devices. The System SKU name is required to differentiate between devices that have the same System Model name, such as Surface Pro and Surface Pro with LTE Advanced.
-
-| Device | System Model | System SKU |
-| ---------- | ----------- | -------------- |
-| Surface 3 WiFI | Surface 3 | Surface_3 |
-| Surface 3 LTE AT&T | Surface 3 | Surface_3_US1 |
-| Surface 3 LTE Verizon | Surface 3 | Surface_3_US2 |
-| Surface 3 LTE North America | Surface 3 | Surface_3_NAG |
-| Surface 3 LTE outside of North America and Y!mobile in Japan | Surface 3 | Surface_3_ROW |
-| Surface Pro | Surface Pro | Surface_Pro_1796 |
-| Surface Pro with LTE Advanced | Surface Pro | Surface_Pro_1807 |
-| Surface Book 2 13" | Surface Book 2 | Surface_Book_1832 |
-| Surface Book 2 15" | Surface Book 2 | Surface_Book_1793 |
-| Surface Go LTE Consumer | Surface Go | Surface_Go_1825_Consumer |
-| Surface Go LTE Commercial | System Go | Surface_Go_1825_Commercial |
-| Surface Go Consumer | Surface Go | Surface_Go_1824_Consumer |
-| Surface Go Commercial | Surface Go | Surface_Go_1824_Commercial |
-| Surface Pro 6 Consumer | Surface Pro 6 | Surface_Pro_6_1796_Consumer |
-| Surface Pro 6 Commercial | Surface Pro 6 | Surface_Pro_6_1796_Commercial |
-| Surface Laptop | Surface Laptop | Surface_Laptop |
-| Surface Laptop 2 Consumer | Surface Laptop 2 | Surface_Laptop_2_1769_Consumer |
-| Surface Laptop 2 Commercial | Surface Laptop 2 | Surface_Laptop_2_1769_Commercial |
-| Surface Pro 7 | Surface Pro 7 | Surface_Pro_7_1866 |
-| Surface Pro X | Surface Pro X | Surface_Pro_X_1876 |
-| Surface Laptop 3 13" Intel | Surface Laptop 3 | Surface_Laptop_3_1867:1868 |
-| Surface Laptop 3 15" Intel | Surface Laptop 3 | Surface_Laptop_3_1872 |
-| Surface Laptop 3 15" AMD | Surface Laptop 3 | Surface_Laptop_3_1873 |
-
-## Examples
-
-**Retrieving the SKU by using PowerShell**
-Use the following PowerShell command to pull the System SKU information:
-
- ``` powershell
-gwmi -namespace root\wmi -class MS_SystemInformation | select SystemSKU
-```
-
-**Retrieving the SKU by using System Information**
-You can also find the System SKU and System Model for a device in **System Information**. To do this, follow these steps:
-
-1. Select **Start**, and then type **MSInfo32** in the search box.
-1. Select **System Information**.
-
-**Using the SKU in a task sequence WMI condition**
-You can use the System SKU information in the Microsoft Deployment Toolkit (MDT) or Microsoft Endpoint Configuration Manager as part of a task sequence WMI condition.
-
- ``` powershell
- - WMI Namespace – Root\WMI
- - WQL Query – SELECT * FROM MS_SystemInformation WHERE SystemSKU = "Surface_Pro_1796"
- ```
diff --git a/devices/surface/surface-wireless-connect.md b/devices/surface/surface-wireless-connect.md
deleted file mode 100644
index 24a358065b..0000000000
--- a/devices/surface/surface-wireless-connect.md
+++ /dev/null
@@ -1,83 +0,0 @@
----
-title: Optimize Wi-Fi connectivity for Surface devices
-description: This topic describes recommended Wi-Fi settings to ensure Surface devices stay connected in congested network environments and mobile scenarios.
-ms.prod: w10
-ms.mktglfcycl: manage
-ms.sitesec: library
-author: coveminer
-ms.audience: itpro
-ms.localizationpriority: medium
-ms.author: v-jokai
-ms.topic: article
-ms.reviewer: tokatz
-manager: laurawi
----
-# Optimize Wi-Fi connectivity for Surface devices
-
-
-To stay connected with all-day battery life, Surface devices implement wireless connectivity settings that balance performance and power conservation. Outside of the most demanding mobility scenarios, users can maintain sufficient wireless connectivity without modifying default network adapter or related settings.
-
-In congested network environments, organizations can implement purpose-built wireless protocols across multiple network access points to facilitate roaming. This page highlights key wireless connectivity considerations in mobile scenarios utilizing Surface Pro 3 and later, Surface Book, Surface Laptop, and Surface Go.
-
-## Prerequisites
-
-This document assumes you have successfully deployed a wireless network that supports 802.11n (Wi-Fi 4) or later in accordance with best practice recommendations from leading equipment vendors.
-
-## Configuring access points for optimal roaming capabilities
-
-If you’re managing a wireless network that’s typically accessed by many different types of client devices, it’s recommended to enable specific protocols on access points (APs) in your WLAN, as described in [Fast Roaming with 802.11k, 802.11v, and 802.11r](https://docs.microsoft.com/windows-hardware/drivers/network/fast-roaming-with-802-11k--802-11v--and-802-11r). Surface devices can take advantage of the following wireless protocols:
-
-- **802.11r.** “**Fast BSS Transition”** accelerates connecting to new wireless access points by reducing the number of frames required before your device can access another AP as you move around with your device.
-- **802.11k.** **“Neighbor Reports”** provides devices with information on current conditions at neighboring access points. It can help your Surface device choose the best AP using criteria other than signal strength such as AP utilization.
-
-Specific Surface devices can also use 802.11v “BSS Transition Management Frames,” which functions much like 802.11k in providing information on nearby candidate APs. These include Surface Go, Surface Pro 7, Surface Pro X, and Surface Laptop 3.
-
-## Managing user settings
-
-You can achieve optimal roaming capabilities through a well-designed network that supports 802.11r and 802.11k across all access points. Ensuring that your network is properly configured to provide users with the best wireless experience is the recommended approach versus attempting to manage user settings on individual devices. Moreover, in many corporate environments Surface device users won’t be able to access advanced network adapter settings without explicit permissions or local admin rights. In other lightly managed networks, users can benefit by knowing how specific settings can impact their ability to remain connected.
-
-### Recommended user settings and best practices
-
-In certain situations, modifying advanced network adapter settings built into Surface devices may facilitate a more reliable connection. Keep in mind however that an inability to connect to wireless resources is more often due to an access point issue, networking design flaw, or environmental site issue.
-
-> [!NOTE]
-> How you hold your Surface Pro or Surface Go can also affect signal strength. If you’re experiencing a loss of bandwidth, check that you’re not holding the top of the display, where the Wi-Fi radio receiver is located. Although holding the top of the display does not block wireless signals, it can trigger the device driver to initiate changes that reduce connectivity.
-
-### Keep default Auto setting for dual bandwidth capability
-On most Surface devices, you can configure client network adapter settings to only connect to wireless APs over 5 gigahertz (GHz), only connect over 2.4 GHz, or let the operating system choose the best option (default Auto setting).
-
-**To access network adapter settings go to:**
-
-- **Start** > **Control panel** > **Network and Sharing Center** > **your Wi-Fi adapter** > **Properties** > **Configure** > **Advanced**.
-
-
-
-Keep in mind that 2.4 GHz has some advantages over 5 GHz: It extends further and more easily penetrates through walls or other solid objects. Unless you have a clear use case that warrants connecting to 5 GHz, it’s recommended to leave the Band setting in the default state to avoid possible adverse consequences. For example:
-
-
-- Many hotspots found in hotels, coffee shops, and airports still only use 2.4 GHz, effectively blocking access to devices if Band is set to 5 GHz Only.
-- Since Miracast wireless display connections require the initial handshake to be completed over 2.4 GHz channels, devices won’t be able to connect at 5 GHz Only.
-
-> [!NOTE]
-> By default Surface devices will prefer connecting to 5 GHz if available. However, to preserve power in a low battery state, Surface will first look for a 2.4 GHz connection.
-
-You can also toggle the band setting as needed to suit your environment. For example, users living in high density apartment buildings with multiple Wi-Fi hotspots — amid the presence of consumer devices all broadcasting via 2.4 GHz — will likely benefit by setting their Surface device to connect on 5 GHz only and then revert to Auto when needed.
-
-### Roaming aggressiveness settings on Surface Go
-
-Front-line workers using Surface Go may wish to select a signal strength threshold that prompts the device to search for a new access point when signal strength drops (roaming aggressiveness). By default, Surface devices attempt to roam to a new access point if the signal strength drops below **Medium** (50 percent signal strength). Note that whenever you increase roaming aggressiveness, you accelerate battery power consumption.
-
-Leave the roaming aggressiveness setting in the default state unless you’re encountering connectivity issues in specific mobile scenarios such as conducting environmental site inspections while also maintaining voice and video connectivity during a conference meeting. If you don’t notice any improvement revert to the default **Medium** state.
-
-**To enable roaming aggressiveness on Surface Go:**
-
-1. Go to **Start > Control Panel** > **Network and Internet** > **Network and Sharing Center.**
-2. Under **Connections** select **Wi-Fi** and then select **Properties.**
-3. Select **Client for Microsoft Networks** and then select **Configure**
-4. Select **Advanced** > **Roaming Aggressiveness** and choose your preferred value from the drop-down menu.
-
-
-
-## Conclusion
-
-Surface devices are designed with default settings for optimal wireless connectivity balanced alongside the need to preserve battery life. The most effective way of enabling reliable connectivity for Surface devices is through a well-designed network that supports 802.11r and 802.11k. Users can adjust network adapter settings or roaming aggressiveness but should only do so in response to specific environmental factors and revert to default state if there’s no noticeable improvement.
diff --git a/devices/surface/unenroll-surface-devices-from-semm.md b/devices/surface/unenroll-surface-devices-from-semm.md
deleted file mode 100644
index 0caea932ab..0000000000
--- a/devices/surface/unenroll-surface-devices-from-semm.md
+++ /dev/null
@@ -1,158 +0,0 @@
----
-title: Unenroll Surface devices from SEMM (Surface)
-description: Learn how to unenroll a device from SEMM by using a Surface UEFI reset package or the Recovery Request option.
-keywords: surface enterprise management
-ms.prod: w10
-ms.mktglfcycl: manage
-ms.pagetype: surface, devices, security
-ms.sitesec: library
-author: coveminer
-ms.author: v-jokai
-ms.topic: article
-ms.reviewer:
-manager: laurawi
-ms.localizationpriority: medium
-ms.audience: itpro
----
-
-# Unenroll Surface devices from SEMM
-
-When a Surface device is enrolled in Surface Enterprise Management Mode (SEMM), a certificate is stored in the firmware of that device. The presence of that certificate and the enrollment in SEMM prevent any unauthorized changes to Surface UEFI settings or options while the device is enrolled in SEMM. To restore control of Surface UEFI settings to the user, the Surface device must be unenrolled from SEMM, a process sometimes described as reset or recovery. There are two methods you can use to unenroll a device from SEMM—a Surface UEFI reset package and a Recovery Request.
-
->[!WARNING]
->To unenroll a device from SEMM and restore user control of Surface UEFI settings, you must have the SEMM certificate that was used to enroll the device in SEMM. If this certificate becomes lost or corrupted, it is not possible to unenroll from SEMM. Back up and protect your SEMM certificate accordingly.
-
-For more information about SEMM, see [Microsoft Surface Enterprise Management Mode](https://technet.microsoft.com/itpro/surface/surface-enterprise-management-mode).
-
-## Unenroll a Surface device from SEMM with a Surface UEFI reset package
-
-The Surface UEFI reset package is the primary method you use to unenroll a Surface device from SEMM. Like a Surface UEFI configuration package, the reset package is a Windows Installer (.msi) file that configures SEMM on the device. Unlike the configuration package, the reset package will reset the Surface UEFI configuration on a Surface device to its default settings, remove the SEMM certificate, and unenroll the device from SEMM.
-
-Reset packages are created specifically for an individual Surface device. To begin the process of creating a reset package, you will need the serial number of the device you want to unenroll, as well as the SEMM certificate used to enroll the device. You can find the serial number of your Surface device on the **PC information** page of Surface UEFI, as shown in Figure 1. This page is displayed even if Surface UEFI is password protected and the incorrect password is entered.
-
-
-
-*Figure 1. The serial number of the Surface device is displayed on the Surface UEFI PC information page*
-
->[!NOTE]
->To boot to Surface UEFI, press **Volume Up** and **Power** simultaneously while the device is off. Hold **Volume Up** until the Surface logo is displayed and the device begins to boot.
-
-To create a Surface UEFI reset package, follow these steps:
-
-1. Open Microsoft Surface UEFI Configurator from the Start menu.
-2. Click **Start**.
-3. Click **Reset Package**, as shown in Figure 2.
-
- 
-
- *Figure 2. Click Reset Package to create a package to unenroll a Surface device from SEMM*
-
-4. Click **Certificate Protection** to add your SEMM certificate file with private key (.pfx), as shown in Figure 3. Browse to the location of your certificate file, select the file, and then click **OK**.
-
- 
-
- *Figure 3. Add the SEMM certificate to a Surface UEFI reset package*
-
-5. Click **Next**.
-6. Type the serial number of the device you want to unenroll from SEMM (as shown in Figure 4), and then click **Build** to generate the Surface UEFI reset package.
-
- 
-
- *Figure 4. Use the serial number of your Surface device to create a Surface UEFI reset package*
-
-7. In the **Save As** dialog box, specify a name for the Surface UEFI reset package, browse to the location where you would like to save the file, and then click **Save**.
-8. When the package generation has completed, the **Successful** page is displayed. Click **End** to complete package creation and close Microsoft Surface UEFI Configurator.
-
-Run the Surface UEFI reset package Windows Installer (.msi) file on the Surface device to unenroll the device from SEMM. The reset package will require a reboot to perform the unenroll operation. After the device has been unenrolled, you can verify the successful removal by ensuring that the **Microsoft Surface Configuration Package** item in **Programs and Features** (shown in Figure 5) is no longer present.
-
-
-
-*Figure 5. The presence of the Microsoft Surface Configuration Package item in Programs and Features indicates that the device is enrolled in SEMM*
-
-## Unenroll a Surface device from SEMM with a Recovery Request
-
-In some scenarios, a Surface UEFI reset package may not be a viable option to unenroll a Surface device from SEMM (for example, where Windows has become unusable). In these scenarios you can unenroll the device by using a Recovery Request generated from within Surface UEFI. The Recovery Request process can be initiated even on devices where you do not have the Surface UEFI password.
-
-The Recovery Request process is initiated from Surface UEFI on the Surface device, approved with Microsoft Surface UEFI Configurator on another computer, and then completed in Surface UEFI. Like the reset package, approving a Recovery Request with Microsoft Surface UEFI Configurator requires access to the SEMM certificate that was used to enroll the Surface device.
-
-To initiate a Recovery Request, follow these steps:
-
-1. Boot the Surface device that is to be unenrolled from SEMM to Surface UEFI.
-2. Type the Surface UEFI password if you are prompted to do so.
-3. Click the **Enterprise management** page, as shown in Figure 6.
-
- 
-
- *Figure 6. The Enterprise management page is displayed in Surface UEFI on devices enrolled in SEMM*
-
-4. Click or press **Get Started**.
-5. Click or press **Next** to begin the Recovery Request process.
- >[!NOTE]
- >A Recovery Request expires two hours after it is created. If a Recovery Request is not completed in this time, you will have to restart the Recovery Request process.
-6. Select **SEMM Certificate** from the list of certificates displayed on the **Choose a SEMM reset key** page (shown in Figure 7), and then click or press **Next**.
-
- 
-
- *Figure 7. Choose SEMM Certificate for your Recovery Request (Reset Request)*
-
-7. On the **Enter SEMM reset verification code** page you can click the **QR Code** or **Text** buttons to display your Recovery Request (Reset Request) as shown in Figure 8, or the **USB** button to save your Recovery Request (Reset Request) as a file to a USB drive, as shown in Figure 9.
-
- 
-
- *Figure 8. A Recovery Request (Reset Request) displayed as a QR Code*
-
- 
-
- *Figure 9. Save a Recovery Request (Reset Request) to a USB drive*
-
- * To use a QR Code Recovery Request (Reset Request), use a QR reader app on a mobile device to read the code. The QR reader app will translate the QR code into an alphanumeric string. You can then email or message that string to the administrator that will produce the reset verification code with Microsoft Surface UEFI Configurator.
- * To use a Recovery Request (Reset Request) saved to a USB drive as a file, use the USB drive to transfer the file to the computer where Microsoft Surface UEFI Configurator will be used to produce the Reset Verification Code. The file can also be copied from the USB drive on another device to be emailed or transferred over the network.
- * To use the Recovery Request (Reset Request) as text, simply type the text directly into Microsoft Surface UEFI Configurator.
-
-8. Open Microsoft Surface UEFI Configurator from the Start menu on another computer.
- >[!NOTE]
- >Microsoft Surface UEFI Configurator must run in an environment that is able to authenticate the certificate chain for the SEMM certificate.
-9. Click **Start**.
-10. Click **Recovery Request**, as shown in Figure 10.
-
- 
-
- *Figure 10. Click Recovery Request to begin the process to approve a Recovery Request*
-
-11. Click **Certificate Protection** to authenticate the Recovery Request with the SEMM certificate.
-12. Browse to and select your SEMM certificate file, and then click **OK**.
-13. When you are prompted to enter the certificate password as shown in Figure 11, type and confirm the password for the certificate file, and then click **OK**.
-
- 
-
- *Figure 11. Type the password for the SEMM certificate*
-
-14. Click **Next**.
-15. Enter the Recovery Request (Reset Request), and then click **Generate** to create a reset verification code (as shown in Figure 12).
-
- 
-
- *Figure 12. Enter the Recovery Request (Reset Request)*
-
- * If you displayed the Recovery Request (Reset Request) as text on the Surface device being reset, use the keyboard to type the Recovery Request (Reset Request) in the provided field.
- * If you displayed the Recovery Request (Reset Request) as a QR Code and then used a messaging or email application to send the code to the computer with Microsoft Surface UEFI Configurator, copy and paste the code into the provided field.
- * If you saved the Recovery Request (Reset Request) as a file to a USB drive, click the **Import** button, browse to and select the Recovery Request (Reset Request) file, and then click **OK**.
-
-16. The reset verification code is displayed in Microsoft Surface UEFI Configurator, as shown in Figure 13.
-
- 
-
- *Figure 13. The reset verification code displayed in Microsoft Surface UEFI Configurator*
-
- * Click the **Share** button to send the reset verification code by email.
-
-17. Enter the reset verification code in the provided field on the Surface device (shown in Figure 8), and then click or press **Verify** to reset the device and unenroll the device from SEMM.
-18. Click or press **Restart now** on the **SEMM reset successful** page to complete the unenrollment from SEMM, as shown in Figure 14.
-
- 
-
- *Figure 14. Successful unenrollment from SEMM*
-
-19. Click **End** in Microsoft Surface UEFI Configurator to complete the Recovery Request (Reset Request) process and close Microsoft Surface UEFI Configurator.
-
-
diff --git a/devices/surface/upgrade-surface-devices-to-windows-10-with-mdt.md b/devices/surface/upgrade-surface-devices-to-windows-10-with-mdt.md
deleted file mode 100644
index c9345502d8..0000000000
--- a/devices/surface/upgrade-surface-devices-to-windows-10-with-mdt.md
+++ /dev/null
@@ -1,44 +0,0 @@
----
-title: Upgrade Surface devices to Windows 10 with Microsoft Deployment Toolkit (Surface)
-description: Find out how to perform a Windows 10 upgrade deployment to your Surface devices.
-keywords: windows 10 surface, upgrade, customize, mdt
-ms.prod: w10
-ms.mktglfcycl: deploy
-ms.pagetype: surface
-ms.sitesec: library
-author: coveminer
-ms.author: v-jokai
-ms.topic: article
-ms.localizationpriority: medium
-ms.audience: itpro
-ms.reviewer:
-manager: laurawi
-ms.date: 04/24/2020
----
-
-# Upgrade Surface devices to Windows 10 with Microsoft Deployment Toolkit
-
-#### Applies to
-- Surface Pro 6
-- Surface Laptop 2
-- Surface Go
-- Surface Go with LTE
-- Surface Book 2
-- Surface Pro with LTE Advanced (Model 1807)
-- Surface Pro (Model 1796)
-- Surface Laptop
-- Surface Studio
-- Surface Studio 2
-- Surface Book
-- Surface Pro 4
-- Surface 3 LTE
-- Surface 3
-- Surface Pro 3
-- Surface Pro 2
-- Surface Pro
-- Windows 10
-
-In addition to the traditional deployment method of reimaging devices, administrators who want to upgrade Surface devices that are running Windows 8.1 or Windows 10 have the option of deploying upgrades. By performing an upgrade deployment, Windows 10 can be applied to devices without removing users, apps, or configuration. The users of the deployed devices can simply continue using the devices with the same apps and settings that they used prior to the upgrade.
-
-For the latest information about upgrading surface devices using MDT, refer to [Perform an in-place upgrade to Windows 10 with MDT](https://docs.microsoft.com/windows/deployment/deploy-windows-mdt/upgrade-to-windows-10-with-the-microsoft-deployment-toolkit).
-
diff --git a/devices/surface/use-system-center-configuration-manager-to-manage-devices-with-semm.md b/devices/surface/use-system-center-configuration-manager-to-manage-devices-with-semm.md
deleted file mode 100644
index 42c6d6f42f..0000000000
--- a/devices/surface/use-system-center-configuration-manager-to-manage-devices-with-semm.md
+++ /dev/null
@@ -1,536 +0,0 @@
----
-title: Use Microsoft Endpoint Configuration Manager to manage devices with SEMM (Surface)
-description: Learn how to manage Microsoft Surface Enterprise Management Mode (SEMM) with Endpoint Configuration Manager.
-keywords: enroll, update, scripts, settings
-ms.prod: w10
-ms.mktglfcycl: manage
-ms.pagetype: surface, devices
-ms.sitesec: library
-author: coveminer
-ms.author: v-jokai
-ms.topic: article
-ms.reviewer:
-manager: laurawi
-ms.localizationpriority: medium
-ms.audience: itpro
----
-
-# Use Microsoft Endpoint Configuration Manager to manage devices with SEMM
-
-The Microsoft Surface Enterprise Management Mode (SEMM) feature of Surface UEFI devices lets administrators manage and help secure the configuration of Surface UEFI settings. For most organizations, this process is accomplished by creating Windows Installer (.msi) packages with the Microsoft Surface UEFI Configurator tool. These packages are then run or deployed to the client Surface devices to enroll the devices in SEMM and to update the Surface UEFI settings configuration.
-
-For organizations with Microsoft Endpoint Configuration Manager there is an alternative to using the Microsoft Surface UEFI Configurator .msi process to deploy and administer SEMM. Microsoft Surface UEFI Manager is a lightweight installer that makes required assemblies for SEMM management available on a device. By installing these assemblies with Microsoft Surface UEFI Manager on a managed client, SEMM can be administered by Configuration Manager with PowerShell scripts, deployed as applications. With this process, SEMM management is performed within Configuration Manager, which eliminates the need for the external Microsoft Surface UEFI Configurator tool.
-
-> [!Note]
-> Although the process described in this article may work with earlier versions of Endpoint Configuration Manager or with other third-party management solutions, management of SEMM with Microsoft Surface UEFI Manager and PowerShell is supported only with the Current Branch of Endpoint Configuration Manager.
-
-#### Prerequisites
-
-Before you begin the process outlined in this article, familiarize yourself with the following technologies and tools:
-
-* [Surface UEFI](https://technet.microsoft.com/itpro/surface/manage-surface-uefi-settings)
-* [Surface Enterprise Management Mode (SEMM)](https://technet.microsoft.com/itpro/surface/surface-enterprise-management-mode)
-* [PowerShell scripting](https://technet.microsoft.com/scriptcenter/dd742419)
-* [System Center Configuration Manager application deployment](https://docs.microsoft.com/sccm/apps/deploy-use/deploy-applications)
-* Certificate management
-
-> [!Note]
-> You will also need access to the certificate that you intend to use to secure SEMM. For details about the requirements for this certificate, see [Surface Enterprise Management Mode certificate requirements](https://technet.microsoft.com/itpro/surface/surface-enterprise-management-mode#surface-enterprise-management-mode-certificate-requirements).
->
-> It is very important that this certificate be kept in a safe location and properly backed up. If this certificate becomes lost or unusable, it is not possible to reset Surface UEFI, change managed Surface UEFI settings, or remove SEMM from an enrolled Surface device.
-
-#### Download Microsoft Surface UEFI Manager
-
-Management of SEMM with Configuration Manager requires the installation of Microsoft Surface UEFI Manager on each client Surface device. You can download Microsoft Surface UEFI Manager (SurfaceUEFIManager.msi) from the [Surface Tools for IT](https://www.microsoft.com/download/details.aspx?id=46703) page on the Microsoft Download Center.
-
-#### Download SEMM scripts for Configuration Manager
-
-After Microsoft Surface UEFI Manager is installed on the client Surface device, SEMM is deployed and managed with PowerShell scripts. You can download samples of the [SEMM management scripts](https://www.microsoft.com/download/details.aspx?id=46703) from the Download Center.
-
-## Deploy Microsoft Surface UEFI Manager
-
-Deployment of Microsoft Surface UEFI Manager is a typical application deployment. The Microsoft Surface UEFI Manager installer file is a standard Windows Installer file that you can install with the [standard quiet option](https://msdn.microsoft.com/library/windows/desktop/aa367988).
-
-The command to install Microsoft Surface UEFI Manager is as follows.
-
-`msiexec /i "SurfaceUEFIManagerSetup.msi" /q`
-
-The command to uninstall Microsoft Surface UEFI Manager is as follows.
-
-`msiexec /x {541DA890-1AEB-446D-B3FD-D5B3BB18F9AF} /q`
-
-To create a new application and deploy it to a collection that contains your Surface devices, perform the following steps:
-
-1. Open Configuration Manager Console from the **Start** screen or **Start** menu.
-2. Select **Software Library** in the bottom left corner of the window.
-3. Expand the **Application Management** node of the Software Library, and then select **Applications**.
-4. Select the **Create Application** button under the **Home** tab at the top of the window. This starts the Create Application Wizard.
-5. The Create Application Wizard presents a series of steps:
-
- * **General** – The **Automatically detect information about this application from installation files** option is selected by default. In the **Type** field, **Windows Installer (.msi file)** is also selected by default. Select **Browse** to navigate to and select **SurfaceUEFIManagerSetup.msi**, and then select **Next**.
-
- > [!Note]
- > The location of SurfaceUEFIManagerSetup.msi must be on a network share and located in a folder that contains no other files. A local file location cannot be used.
-
- * **Import Information** – The Create Application Wizard will parse the .msi file and read the **Application Name** and **Product Code**. SurfaceUEFIManagerSetup.msi should be listed as the only file under the line **Content Files**, as shown in Figure 1. Select **Next** to proceed.
-
- 
-
- *Figure 1. Information from Microsoft Surface UEFI Manager setup is automatically parsed*
-
- * **General Information** – You can modify the name of the application and information about the publisher and version, or add comments on this page. The installation command for Microsoft Surface UEFI Manager is displayed in the Installation Program field. The default installation behavior of Install for system will allow Microsoft Surface UEFI Manager to install the required assemblies for SEMM even if a user is not logged on to the Surface device. Select **Next** to proceed.
- * **Summary** – The information that was parsed in the **Import Information** step and your selections from the **General Information** step is displayed on this page. Select **Next** to confirm your selections and create the application.
- * **Progress** – Displays a progress bar and status as the application is imported and added to the Software Library.
- * **Completion** – Confirmation of the successful application creation is displayed when the application creation process is complete. Select **Close** to finish the Create Application Wizard.
-
-After the application is created in Configuration Manager, you can distribute it to your distribution points and deploy it to the collections including your Surface devices. This application will not install or enable SEMM on the Surface device. It only provides the assemblies required for SEMM to be enabled using the PowerShell script.
-
-If you do not want to install the Microsoft Surface UEFI Manager assemblies on devices that will not be managed with SEMM, you can configure Microsoft Surface UEFI Manager as a dependency of the SEMM Configuration Manager scripts. This scenario is covered in the [Deploy SEMM Configuration Manager Scripts](#deploy-semm-configuration-manager-scripts) section later in this article.
-
-## Create or modify the SEMM Configuration Manager scripts
-
-After the required assemblies have been installed on the devices, the process of enrolling the devices in SEMM and configuring Surface UEFI is done with PowerShell scripts and deployed as a script application with Configuration Manager. These scripts can be modified to fit the needs of your organization and environment. For example, you can create multiple configurations for managed Surface devices in different departments or roles. You can download samples of the scripts for SEMM and Configuration Manager from the link in the [Prerequisites](#prerequisites) section at the beginning of this article.
-
-There are two primary scripts you will need in order to perform a SEMM deployment with Configuration Manager:
-
-* **ConfigureSEMM.ps1** – Use this script to create configuration packages for your Surface devices with your desired Surface UEFI settings to apply the specified settings to a Surface device, to enroll the device in SEMM, and to set a registry key used to identify the enrollment of the device in SEMM.
-* **ResetSEMM.ps1** – Use this script to reset SEMM on a Surface device, which unenrolls it from SEMM and removes the control over Surface UEFI settings.
-
-The sample scripts include examples of how to set Surface UEFI settings and how to control permissions to those settings. These settings can be modified to secure Surface UEFI and set Surface UEFI settings according to the needs of your environment. The following sections of this article explain the ConfigureSEMM.ps1 script and explore the modifications you need to make to the script to fit your requirements.
-
-> [!NOTE]
-> The SEMM Configuration Manager scripts and the exported SEMM certificate file (.pfx) should be placed in the same folder with no other files before they are added to Configuration Manager.
-
-### Specify certificate and package names
-
-The first region of the script that you need to modify is the portion that specifies and loads the SEMM certificate, and also indicates SurfaceUEFIManager version, and the names for the SEMM configuration package and SEMM reset package. The certificate name and SurfaceUEFIManager version are specified on lines 56 through 73 in the ConfigureSEMM.ps1 script.
-
- ```powershell
- 56 $WorkingDirPath = split-path -parent $MyInvocation.MyCommand.Definition
- 57 $packageRoot = "$WorkingDirPath\Config"
- 58 $certName = "FabrikamSEMMSample.pfx"
- 59 $DllVersion = "2.26.136.0"
- 60
- 61 $certNameOnly = [System.IO.Path]::GetFileNameWithoutExtension($certName)
- 62 $ProvisioningPackage = $certNameOnly + "ProvisioningPackage.pkg"
- 63 $ResetPackage = $certNameOnly + "ResetPackage.pkg"
- 64
- 65 if (-not (Test-Path $packageRoot)) { New-Item -ItemType Directory -Force -Path $packageRoot }
- 66 Copy-Item "$WorkingDirPath\$certName" $packageRoot
- 67
- 68 $privateOwnerKey = Join-Path -Path $packageRoot -ChildPath $certName
- 69 $ownerPackageName = Join-Path -Path $packageRoot -ChildPath $ProvisioningPackage
- 70 $resetPackageName = Join-Path -Path $packageRoot -ChildPath $ResetPackage
- 71
- 72 # If your PFX file requires a password then it can be set here, otherwise use a blank string.
- 73 $password = "1234"
- ```
-
-Replace the **FabrikamSEMMSample.pfx** value for the **$certName** variable with the name of your SEMM Certificate file on line 58. The script will create a working directory (named Config) in the folder where your scripts are located, and then copies the certificate file to this working directory.
-
-Owner package and reset package will also be created in the Config directory and hold the configuration for Surface UEFI settings and permissions generated by the script.
-
-On line 73, replace the value of the **$password** variable, from **1234** to the password for your certificate file. If a password is not required, delete the **1234** text.
-
-> [!Note]
-> The last two characters of the certificate thumbprint are required to enroll a device in SEMM. This script will display these digits to the user, which allows the user or technician to record these digits before the system reboots to enroll the device in SEMM. The script uses the following code, found on lines 150-155, to accomplish this.
-
-```powershell
-150 # Device owners will need the last two characters of the thumbprint to accept SEMM ownership.
-151 # For convenience we get the thumbprint here and present to the user.
-152 $pw = ConvertTo-SecureString $password -AsPlainText -Force
-153 $certPrint = New-Object System.Security.Cryptography.X509Certificates.X509Certificate2
-154 $certPrint.Import($privateOwnerKey, $pw, [System.Security.Cryptography.X509Certificates.X509KeyStorageFlags]::DefaultKeySet)
-155 Write-Host "Thumbprint =" $certPrint.Thumbprint
-```
-
-Administrators with access to the certificate file (.pfx) can read the thumbprint at any time by opening the .pfx file in CertMgr. To view the thumbprint with CertMgr, follow this process:
-
-1. Right-click the .pfx file, and then select **Open**.
-2. Expand the folder in the navigation pane.
-3. Select **Certificates**.
-4. Right-click your certificate in the main pane, and then select **Open**.
-5. Select the **Details** tab.
-6. **All** or **Properties Only** must be selected in the **Show** drop-down menu.
-7. Select the field **Thumbprint**.
-
-> [!NOTE]
-> The SEMM certificate name and password must also be entered in this section of the ResetSEMM.ps1 script to enable Configuration Manager to remove SEMM from the device with the uninstall action.
-
-### Configure permissions
-
-The first region of the script where you will specify the configuration for Surface UEFI is the **Configure Permissions** region. This region begins at line 210 in the sample script with the comment **# Configure Permissions** and continues to line 247. The following code fragment first sets permissions to all Surface UEFI settings so that they may be modified by SEMM only, then adds explicit permissions to allow the local user to modify the Surface UEFI password, TPM, and front and rear cameras.
-
-```powershell
-210 # Configure Permissions
-211 foreach ($uefiV2 IN $surfaceDevices.Values) {
-212 if ($uefiV2.SurfaceUefiFamily -eq $Device.Model) {
-213 Write-Host "Configuring permissions"
-214 Write-Host $Device.Model
-215 Write-Host "======================="
-216
-217 # Here we define which "identities" will be allowed to modify which settings
-218 # PermissionSignerOwner = The primary SEMM enterprise owner identity
-219 # PermissionLocal = The user when booting to the UEFI pre-boot GUI
-220 # PermissionSignerUser, PermissionSignerUser1, PermissionSignerUser2 =
-221 # Additional user identities created so that the signer owner
-222 # can delegate permission control for some settings.
-223 $ownerOnly = [Microsoft.Surface.IUefiSetting]::PermissionSignerOwner
-224 $ownerAndLocalUser = ([Microsoft.Surface.IUefiSetting]::PermissionSignerOwner -bor [Microsoft.Surface.IUefiSetting]::PermissionLocal)
-225
-226 # Make all permissions owner only by default
-227 foreach ($setting IN $uefiV2.Settings.Values) {
-228 $setting.ConfiguredPermissionFlags = $ownerOnly
-229 }
-230
-231 # Allow the local user to change their own password
-232 $uefiV2.SettingsById[501].ConfiguredPermissionFlags = $ownerAndLocalUser
-233
-234 Write-Host ""
-235
-236 # Create a unique package name based on family and LSV.
-237 # We will choose a name that can be parsed by later scripts.
-238 $packageName = $uefiV2.SurfaceUefiFamily + "^Permissions^" + $lsv + ".pkg"
-239 $fullPackageName = Join-Path -Path $packageRoot -ChildPath $packageName
-240
-241 # Build and sign the Permission package then save it to a file.
-242 $permissionPackageStream = $uefiV2.BuildAndSignPermissionPackage($privateOwnerKey, $password, "", $null, $lsv)
-243 $permissionPackage = New-Object System.IO.Filestream($fullPackageName, [System.IO.FileMode]::CreateNew, [System.IO.FileAccess]::Write)
-244 $permissionPackageStream.CopyTo($permissionPackage)
-245 $permissionPackage.Close()
-246 }
-247 }
-```
-
-Each **$uefiV2** variable identifies a Surface UEFI setting by setting name or ID, and then configures the permissions to one of the following values:
-
-* **$ownerOnly** – Permission to modify this setting is granted only to SEMM.
-* **$ownerAndLocalUser** – Permission to modify this setting is granted to a local user booting to Surface UEFI, as well as to SEMM.
-
-You can find information about the available settings names and IDs for Surface UEFI in the [Settings Names and IDs](#settings-names-and-ids) section of this article.
-
-### Configure settings
-
-The second region of the script where you will specify the configuration for Surface UEFI is the **Configure Settings** region of the ConfigureSEMM.ps1 script, which configures whether each setting is enabled or disabled. The sample script includes instructions to set all settings to their default values. The script then provides explicit instructions to disable IPv6 for PXE Boot and to leave the Surface UEFI Administrator password unchanged. You can find this region beginning with the **# Configure Settings** comment at line 291 through line 335 in the sample script. The region appears as follows.
-
-```powershell
-291 # Configure Settings
-292 foreach ($uefiV2 IN $surfaceDevices.Values) {
-293 if ($uefiV2.SurfaceUefiFamily -eq $Device.Model) {
-294 Write-Host "Configuring settings"
-295 Write-Host $Device.Model
-296 Write-Host "===================="
-297
-298 # In this demo, we will start by setting every setting to the default factory setting.
-299 # You may want to start by doing this in your scripts
-300 # so that every setting gets set to a known state.
-301 foreach ($setting IN $uefiV2.Settings.Values) {
-302 $setting.ConfiguredValue = $setting.DefaultValue
-303 }
-304
-305 $EnabledValue = "Enabled"
-306 $DisabledValue = "Disabled"
-307
-308 # If you want to set something to a different value from the default,
-309 # here are examples of how to accomplish this.
-310 # This disables IPv6 PXE boot by name:
-311 $uefiV2.Settings["IPv6 for PXE Boot"].ConfiguredValue = $DisabledValue
-312
-313 # This disables IPv6 PXE Boot by ID:
-314 $uefiV2.SettingsById[400].ConfiguredValue = $DisabledValue
-315
-316 Write-Host ""
-317
-318 # If you want to leave the setting unmodified, set it to $null
-319 # PowerShell has issues setting things to $null so ClearConfiguredValue()
-320 # is supplied to do this explicitly.
-321 # Here is an example of leaving the UEFI administrator password as-is,
-322 # even after we initially set it to factory default above.
-323 $uefiV2.SettingsById[501].ClearConfiguredValue()
-324
-325 # Create a unique package name based on family and LSV.
-326 # We will choose a name that can be parsed by later scripts.
-327 $packageName = $uefiV2.SurfaceUefiFamily + "^Settings^" + $lsv + ".pkg"
-328 $fullPackageName = Join-Path -Path $packageRoot -ChildPath $packageName
-329
-330 # Build and sign the Settings package then save it to a file.
-331 $settingsPackageStream = $uefiV2.BuildAndSignSecuredSettingsPackage($privateOwnerKey, $password, "", $null, $lsv)
-332 $settingsPackage = New-Object System.IO.Filestream($fullPackageName, [System.IO.FileMode]::CreateNew, [System.IO.FileAccess]::Write)
-333 $settingsPackageStream.CopyTo($settingsPackage)
-334 $settingsPackage.Close()
-335 }
-```
-
-Like the permissions set in the **Configure Permissions** section of the script, the configuration of each Surface UEFI setting is performed by defining the **$uefiV2** variable. For each line defining the **$uefiV2** variable, a Surface UEFI setting is identified by setting name or ID and the configured value is set to **Enabled** or **Disabled**.
-
-If you do not want to alter the configuration of a Surface UEFI setting, for example to ensure that the Surface UEFI administrator password is not cleared by the action of resetting all Surface UEFI settings to their default, you can use **ClearConfiguredValue()** to enforce that this setting will not be altered. In the sample script, this is used on line 323 to prevent the clearing of the Surface UEFI Administrator password, identified in the sample script by its setting ID, **501**.
-
-You can find information about the available settings names and IDs for Surface UEFI in the [Settings Names and IDs](#settings-names-and-ids) section later in this article.
-
-### Settings registry key
-
-To identify enrolled systems for Configuration Manager, the ConfigureSEMM.ps1 script writes registry keys that can be used to identify enrolled systems as having been installed with the SEMM configuration script. These keys can be found at the following location.
-
-`HKLM\SOFTWARE\Microsoft\Surface\SEMM`
-
-The following code fragment, found on lines 380-477, is used to write these registry keys.
-
-```powershell
-380 # For Endpoint Configuration Manager or other management solutions that wish to know what version is applied, tattoo the LSV and current DateTime (in UTC) to the registry:
-381 $UTCDate = (Get-Date).ToUniversalTime().ToString()
-382 $certIssuer = $certPrint.Issuer
-383 $certSubject = $certPrint.Subject
-384
-385 $SurfaceRegKey = "HKLM:\SOFTWARE\Microsoft\Surface\SEMM"
-386 New-RegKey $SurfaceRegKey
-387 $LSVRegValue = Get-ItemProperty $SurfaceRegKey LSV -ErrorAction SilentlyContinue
-388 $DateTimeRegValue = Get-ItemProperty $SurfaceRegKey LastConfiguredUTC -ErrorAction SilentlyContinue
-389 $OwnershipSessionIdRegValue = Get-ItemProperty $SurfaceRegKey OwnershipSessionId -ErrorAction SilentlyContinue
-390 $PermissionSessionIdRegValue = Get-ItemProperty $SurfaceRegKey PermissionSessionId -ErrorAction SilentlyContinue
-391 $SettingsSessionIdRegValue = Get-ItemProperty $SurfaceRegKey SettingsSessionId -ErrorAction SilentlyContinue
-392 $IsResetRegValue = Get-ItemProperty $SurfaceRegKey IsReset -ErrorAction SilentlyContinue
-393 $certUsedRegValue = Get-ItemProperty $SurfaceRegKey CertName -ErrorAction SilentlyContinue
-394 $certIssuerRegValue = Get-ItemProperty $SurfaceRegKey CertIssuer -ErrorAction SilentlyContinue
-395 $certSubjectRegValue = Get-ItemProperty $SurfaceRegKey CertSubject -ErrorAction SilentlyContinue
-396
-397
-398 If ($LSVRegValue -eq $null)
-399 {
-400 New-ItemProperty -Path $SurfaceRegKey -Name LSV -PropertyType DWORD -Value $lsv | Out-Null
-401 }
-402 Else
-403 {
-404 Set-ItemProperty -Path $SurfaceRegKey -Name LSV -Value $lsv
-405 }
-406
-407 If ($DateTimeRegValue -eq $null)
-408 {
-409 New-ItemProperty -Path $SurfaceRegKey -Name LastConfiguredUTC -PropertyType String -Value $UTCDate | Out-Null
-410 }
-411 Else
-412 {
-413 Set-ItemProperty -Path $SurfaceRegKey -Name LastConfiguredUTC -Value $UTCDate
-414 }
-415
-416 If ($OwnershipSessionIdRegValue -eq $null)
-417 {
-418 New-ItemProperty -Path $SurfaceRegKey -Name OwnershipSessionId -PropertyType String -Value $ownerSessionIdValue | Out-Null
-419 }
-420 Else
-421 {
-422 Set-ItemProperty -Path $SurfaceRegKey -Name OwnershipSessionId -Value $ownerSessionIdValue
-423 }
-424
-425 If ($PermissionSessionIdRegValue -eq $null)
-426 {
-427 New-ItemProperty -Path $SurfaceRegKey -Name PermissionSessionId -PropertyType String -Value $permissionSessionIdValue | Out-Null
-428 }
-429 Else
-430 {
-431 Set-ItemProperty -Path $SurfaceRegKey -Name PermissionSessionId -Value $permissionSessionIdValue
-432 }
-433
-434 If ($SettingsSessionIdRegValue -eq $null)
-435 {
-436 New-ItemProperty -Path $SurfaceRegKey -Name SettingsSessionId -PropertyType String -Value $settingsSessionIdValue | Out-Null
-437 }
-438 Else
-439 {
-440 Set-ItemProperty -Path $SurfaceRegKey -Name SettingsSessionId -Value $settingsSessionIdValue
-441 }
-442
-443 If ($IsResetRegValue -eq $null)
-444 {
-445 New-ItemProperty -Path $SurfaceRegKey -Name IsReset -PropertyType DWORD -Value 0 | Out-Null
-446 }
-447 Else
-448 {
-449 Set-ItemProperty -Path $SurfaceRegKey -Name IsReset -Value 0
-450 }
-451
-452 If ($certUsedRegValue -eq $null)
-453 {
-454 New-ItemProperty -Path $SurfaceRegKey -Name CertName -PropertyType String -Value $certName | Out-Null
-455 }
-456 Else
-457 {
-458 Set-ItemProperty -Path $SurfaceRegKey -Name CertName -Value $certName
-459 }
-460
-461 If ($certIssuerRegValue -eq $null)
-462 {
-463 New-ItemProperty -Path $SurfaceRegKey -Name CertIssuer -PropertyType String -Value $certIssuer | Out-Null
-464 }
-465 Else
-466 {
-467 Set-ItemProperty -Path $SurfaceRegKey -Name CertIssuer -Value $certIssuer
-468 }
-469
-470 If ($certSubjectRegValue -eq $null)
-471 {
-472 New-ItemProperty -Path $SurfaceRegKey -Name CertSubject -PropertyType String -Value $certSubject | Out-Null
-473 }
-474 Else
-475 {
-476 Set-ItemProperty -Path $SurfaceRegKey -Name CertSubject -Value $certSubject
-477 }
-```
-
-### Settings names and IDs
-
-To configure Surface UEFI settings or permissions for Surface UEFI settings, you must refer to each setting by either its setting name or setting ID. With each new update for Surface UEFI, new settings may be added. The best way to get a complete list of the settings available on a Surface device, along with the settings name and settings IDs, is to use the ShowSettingsOptions.ps1 script from SEMM_Powershell.zip in [Surface Tools for IT Downloads](https://www.microsoft.com/download/details.aspx?id=46703)
-
-The computer where ShowSettingsOptions.ps1 is run must have Microsoft Surface UEFI Manager installed, but the script does not require a Surface device.
-
-The following tables show the available settings for Surface Pro 4 and later including Surface Pro 7, Surface Book, Surface Laptop 3, and Surface Go.
-
-*Table 1. Surface UEFI settings for Surface Pro 4*
-
-| Setting ID | Setting Name | Description | Default Setting |
-| --- | --- | --- | --- |
-|501| Password | UEFI System Password | |
-|200| Secure Boot Keys | Secure Boot signing keys to enable for EFI applications | MsPlus3rdParty |
-|300| Trusted Platform Module (TPM) | TPM device enabled or disabled | Enabled |
-|301| Docking USB Port | Docking USB Port enabled or disabled | Enabled |
-|302| Front Camera | Front Camera enabled or disabled | Enabled |
-|303| Bluetooth | Bluetooth radio enabled or disabled | Enabled |
-|304| Rear Camera | Rear Camera enabled or disabled | Enabled |
-|305| IR Camera | InfraRed Camera enabled or disabled | Enabled |
-|308| Wi-Fi and Bluetooth | Wi-Fi and Bluetooth enabled or disabled | Enabled |
-|310| Type Cover | Surface Type Cover connector | Enabled |
-|320| On-board Audio | On-board audio enabled or disabled | Enabled |
-|330| Micro SD Card | Micro SD Card enabled or disabled | Enabled |
-|370| USB Port 1 | Side USB Port (1) | UsbPortEnabled |
-|400| IPv6 for PXE Boot | Enable IPv6 PXE boot before IPv4 PXE boot |Disabled |
-|401| Alternate Boot | Alternate Boot allows users to override the boot order by holding the volume down button when powering up the device | Enabled |
-|402| Boot Order Lock | Boot Order variable lock enabled or disabled | Disabled |
-|403| USB Boot | Enable booting from USB devices | Enabled |
-|500| TPM clear EFI protocol | Enable EFI protocol for invoking TPM clear | Disabled |
-|600| Security | UEFI Security Page Display enabled or disabled | Enabled |
-|601| Devices | UEFI Devices Page Display enabled or disabled | Enabled |
-|602| Boot | UEFI Boot Manager Page Display enabled or disabled | Enabled |
-
-*Table 2. Surface UEFI settings for Surface Book*
-
-| Setting ID | Setting Name | Description | Default Setting |
-| --- | --- | --- | --- |
-| 501 | Password | UEFI System Password | |
-| 200 | Secure Boot Keys | Secure Boot signing keys to enable for EFI applications | MsPlus3rdParty |
-| 300 | Trusted Platform Module (TPM) | TPM device enabled or disabled | Enabled |
-| 301 | Docking USB Port | Docking USB Port enabled or disabled | Enabled |
-| 302 | Front Camera | Front Camera enabled or disabled | Enabled |
-| 303 | Bluetooth | Bluetooth radio enabled or disabled | Enabled |
-| 304 | Rear Camera | Rear Camera enabled or disabled | Enabled |
-| 305 | IR Camera | InfraRed Camera enabled or disabled | Enabled |
-| 308 | Wi-Fi and Bluetooth | Wi-Fi and Bluetooth enabled or disabled | Enabled |
-| 320 | On-board Audio | On-board audio enabled or disabled | Enabled |
-| 400 | IPv6 for PXE Boot Enable | IPv6 PXE boot before IPv4 PXE boot | Disabled |
-| 401 | Alternate Boot | Alternate Boot allows users to override the boot order by holding the volume down button when powering up the device | Enabled |
-| 402 | Boot Order Lock | Boot Order variable lock enabled or disabled | Disabled |
-| 403 | USB Boot | Enable booting from USB devices | Enabled |
-| 500 | TPM clear EFI protocol | Enable EFI protocol for invoking TPM clear | Disabled |
-| 600 | Security | UEFI Security Page Display enabled or disabled | Enabled |
-| 601 | Devices | UEFI Devices Page Display enabled or disabled | Enabled |
-| 602 | Boot | UEFI Boot Manager Page Display enabled or disabled | Enabled |
-
-## Deploy SEMM Configuration Manager scripts
-
-After your scripts are prepared to configure and enable SEMM on the client device, the next step is to add these scripts as an application in Configuration Manager. Before you open Configuration Manager, ensure that the following files are in a shared folder that does not include other files:
-
-* ConfigureSEMM.ps1
-* ResetSEMM.ps1
-* Your SEMM certificate (for example SEMMCertificate.pfx)
-
-The SEMM Configuration Manager scripts will be added to Configuration Manager as a script application. The command to install SEMM with ConfigureSEMM.ps1 is as follows.
-
-`Powershell.exe -file ".\ConfigureSEMM.ps1"`
-
-The command to uninstall SEMM with ResetSEMM.ps1 is as follows.
-
-`Powershell.exe -file ".\ResetSEMM.ps1"`
-
-To add the SEMM Configuration Manager scripts to Configuration Manager as an application, use the following process:
-
-1. Start the Create Application Wizard using Step 1 through Step 5 from the [Deploy Microsoft Surface UEFI Manager](#deploy-microsoft-surface-uefi-manager) section earlier in this article.
-
-2. Proceed through The Create Application Wizard as follows:
-
- - **General** – Select **Manually specify the application information**, and then select **Next**.
-
- - **General Information** – Enter a name for the application (for example SEMM) and any other information you want such as publisher, version, or comments on this page. Select **Next** to proceed.
-
- - **Application Catalog** – The fields on this page can be left with their default values. Select **Next**.
-
- - **Deployment Types** – Select **Add** to start the Create Deployment Type Wizard.
-
- - Proceed through the steps of the Create Deployment Type Wizard, as follows:
-
- * **General** – Select **Script Installer** from the **Type** drop-down menu. The **Manually specify the deployment type information** option will automatically be selected. Select **Next** to proceed.
- * **General Information** – Enter a name for the deployment type (for example SEMM Configuration Scripts), and then select **Next** to continue.
- * **Content** – Select **Browse** next to the **Content Location** field, and then select the folder where your SEMM Configuration Manager scripts are located. In the **Installation Program** field, type the [installation command](#deploy-semm-configuration-manager-scripts) found earlier in this article. In the **Uninstall Program** field, enter the [uninstallation command](#deploy-semm-configuration-manager-scripts) found earlier in this article (shown in Figure 2). Select **Next** to move to the next page.
-
- 
-
- *Figure 2. Set the SEMM Configuration Manager scripts as the install and uninstall commands*
-
- * **Detection Method** – Select **Add Clause** to add the SEMM Configuration Manager script registry key detection rule. The **Detection Rule** window is displayed, as shown in Figure 3. Use the following settings:
-
- - Select **Registry** from the **Setting Type** drop-down menu.
- - Select **HKEY_LOCAL_MACHINE** from the **Hive** drop-down menu.
- - Enter **SOFTWARE\Microsoft\Surface\SEMM** in the **Key** field.
- - Enter **CertName** in the **Value** field.
- - Select **String** from the **Data Type** drop-down menu.
- - Select the **This registry setting must satisfy the following rule to indicate the presence of this application** button.
- - Enter the name of the certificate you entered in line 58 of the script in the **Value** field.
- - Select **OK** to close the **Detection Rule** window.
-
- 
-
- *Figure 3. Use a registry key to identify devices enrolled in SEMM*
-
- * Select **Next** to proceed to the next page.
-
- * **User Experience** – Select **Install for system** from the **Installation Behavior** drop-down menu. If you want your users to record and enter the certificate thumbprint themselves, leave the logon requirement set to **Only when a user is logged on**. If you want your administrators to enter the thumbprint for users and the users do not need to see the thumbprint, select **Whether or not a user is logged on** from the **Logon Requirement** drop-down menu.
-
- * **Requirements** – The ConfigureSEMM.ps1 script automatically verifies that the device is a Surface device before attempting to enable SEMM. However, if you intend to deploy this script application to a collection with devices other than those to be managed with SEMM, you could add requirements here to ensure this application would run only on Surface devices or devices you intend to manage with SEMM. Select **Next** to continue.
-
- * **Dependencies** – Select **Add** to open the **Add Dependency** window.
-
- * Select **Add** to open the **Specify Required Application** window.
-
- - Enter a name for the SEMM dependencies in the **Dependency Group Name** field (for example, *SEMM Assemblies*).
-
- - Select **Microsoft Surface UEFI Manager** from the list of **Available Applications** and the MSI deployment type, and then select **OK** to close the **Specify Required Application** window.
-
- * Keep the **Auto Install** check box selected if you want Microsoft Surface UEFI Manager installed automatically on devices when you attempt to enable SEMM with the Configuration Manager scripts. Select **OK** to close the **Add Dependency** window.
-
- * Select **Next** to proceed.
-
- * **Summary** – The information you have entered throughout the Create Deployment Type wizard is displayed on this page. Select **Next** to confirm your selections.
-
- * **Progress** – A progress bar and status as the deployment type is added for the SEMM script application is displayed on this page.
-
- * **Completion** – Confirmation of the deployment type creation is displayed when the process is complete. Select **Close** to finish the Create Deployment Type Wizard.
-
- - **Summary** – The information that you entered throughout the Create Application Wizard is displayed. Select **Next** to create the application.
-
- - **Progress** – A progress bar and status as the application is added to the Software Library is displayed on this page.
-
- - **Completion** – Confirmation of the successful application creation is displayed when the application creation process is complete. Select **Close** to finish the Create Application Wizard.
-
-After the script application is available in the Software Library of Configuration Manager, you can distribute and deploy SEMM using the scripts you prepared to devices or collections. If you have configured the Microsoft Surface UEFI Manager assemblies as a dependency that will be automatically installed, you can deploy SEMM in a single step. If you have not configured the assemblies as a dependency, they must be installed on the devices you intend to manage before you enable SEMM.
-
-When you deploy SEMM using this script application and with a configuration that is visible to the end user, the PowerShell script will start and the thumbprint for the certificate will be displayed by the PowerShell window. You can have your users record this thumbprint and enter it when prompted by Surface UEFI after the device reboots.
-
-Alternatively, you can configure the application installation to reboot automatically and to install invisibly to the user. In this scenario, a technician will be required to enter the thumbprint on each device as it reboots. Any technician with access to the certificate file can read the thumbprint by viewing the certificate with CertMgr. Instructions for viewing the thumbprint with CertMgr are in the [Create or modify the SEMM Configuration Manager scripts](#create-or-modify-the-semm-configuration-manager-scripts) section of this article.
-
-Removal of SEMM from a device deployed with Configuration Manager using these scripts is as easy as uninstalling the application with Configuration Manager. This action starts the ResetSEMM.ps1 script and properly unenrolls the device with the same certificate file that was used during the deployment of SEMM.
-
-> [!NOTE]
-> Microsoft Surface recommends that you create reset packages only when you need to unenroll a device. These reset packages are typically valid for only one device, identified by its serial number. You can, however, create a universal reset package that would work for any device enrolled in SEMM with this certificate.
->
-> We strongly recommend that you protect your universal reset package as carefully as the certificate you used to enroll devices in SEMM. Please remember that, just like the certificate itself, this universal reset package can be used to unenroll any of your organization’s Surface devices from SEMM.
->
-> When you install a reset package, the Lowest Supported Value (LSV) is reset to a value of 1. You can reenroll a device by using an existing configuration package. The device will prompt for the certificate thumbprint before ownership is taken.
->
-> For this reason, the reenrollment of a device in SEMM would require a new package to be created and installed on that device. Because this action is a new enrollment and not a change in configuration on a device already enrolled in SEMM, the device will prompt for the certificate thumbprint before ownership is taken.
diff --git a/devices/surface/using-the-sda-deployment-share.md b/devices/surface/using-the-sda-deployment-share.md
deleted file mode 100644
index 0309d071ec..0000000000
--- a/devices/surface/using-the-sda-deployment-share.md
+++ /dev/null
@@ -1,172 +0,0 @@
----
-title: Using the Microsoft Surface Deployment Accelerator deployment share (Surface)
-description: Explore the scenarios where you can use SDA to meet the deployment needs of your organization including Proof of Concept, pilot deployment, as well as import additional drivers and applications.
-keywords: deploy, install, automate, deployment solution
-ms.prod: w10
-ms.mktglfcycl: deploy
-ms.pagetype: surface, devices
-ms.sitesec: library
-author: coveminer
-ms.author: v-jokai
-ms.topic: article
-ms.localizationpriority: medium
-ms.audience: itpro
-ms.reviewer:
-manager: laurawi
----
-
-# Using the Microsoft Surface Deployment Accelerator deployment share
-
-With Microsoft Surface Deployment Accelerator (SDA), you can quickly and easily set up a deployment solution that is ready to deploy Windows to Surface devices. The prepared environment is built on powerful deployment technologies available from Microsoft, such as the [Microsoft Deployment Toolkit (MDT)](https://technet.microsoft.com/windows/dn475741), and is capable of immediately performing a deployment after configuration. See [Step-by-Step: Surface Deployment Accelerator](https://technet.microsoft.com/itpro/surface/step-by-step-surface-deployment-accelerator) for a comprehensive walkthrough of using the SDA wizard to set up a deployment share and perform a deployment.
-
-For more information about SDA and information on how to download SDA, see [Microsoft Surface Deployment Accelerator (SDA)](https://technet.microsoft.com/itpro/surface/microsoft-surface-deployment-accelerator).
-
-> [!NOTE]
-> SDA is not supported on Surface Pro 7, Surface Pro X, and Surface Laptop 3. For more information refer to [Deploy Surface devices](deploy.md).
-
-Using SDA provides these primary benefits:
-
-* With SDA, you can create a ready-to-deploy environment that can deploy to target devices as fast as your download speeds allow. The wizard experience enables you to check a few boxes and then the automated process builds your deployment environment for you.
-
-* With SDA, you prepare a deployment environment built on the industry leading deployment solution of MDT. With MDT you can scale from a relatively basic deployment of a few Surface devices to a solution capable of deploying to thousands of devices including all of the different makes and models in your organization and all of the applications required by each device and user.
-
-This article explores four scenarios where you can use SDA to meet the needs of your organization. See [Deploy Windows 10](https://technet.microsoft.com/itpro/windows/deploy/index) to explore the capabilities of MDT and the Windows deployment technologies available from Microsoft in greater detail.
-
-## Perform a Proof of Concept deployment
-
-One of the primary scenarios for use of SDA is as a Proof of Concept. A *Proof of Concept* (PoC) enables you to test or evaluate the capabilities of a solution or technology. A PoC is often used to illustrate the benefits of the solution or technology to decision makers. For example, if you want to recommend Surface devices as a replacement of older point of sale (POS) systems, you could perform a PoC to demonstrate how Surface devices provide superior computing power, flexibility, and connectivity when compared to alternate options.
-
-Using SDA to prepare a PoC of Surface devices enables you to very quickly prepare a demonstration of Surface device or devices, which gives you more time for customization or preparation. The flexibility of SDA even lets you import resources, like applications and drivers, from existing MDT deployment infrastructure. See the [Work with existing deployment shares](#work-with-existing-deployment-shares) section later in this article for more information.
-
-SDA is also an excellent PoC of the capabilities of MDT. SDA demonstrates just how quickly an MDT deployment environment can be prepared and made ready for deployment to devices. It also shows just how flexible and customizable the MDT solution can be, with support for Windows 10 and Windows 8.1, for Microsoft Store and desktop applications, and several models of Surface devices.
-
-Some recommendations for a successful PoC with SDA are:
-
-* Keep your SDA deployment environment separate from your production network. This ensures optimal performance and reduces potential for conflicts during your PoC deployment.
-
-* Use a fresh and updated instance of Windows Server to house your SDA deployment share to maintain the simplicity and performance of the demonstration environment.
-
-* Test the deployment process before you demonstrate your PoC. This reduces the potential for unexpected situations and keeps the demonstration focused on the deployment process and Surface devices.
-
-* Use offline files with SDA to further reduce installation times.
-
-* For help with your PoC, contact [Surface Support](https://www.microsoft.com/surface/support/contact-us-business).
-
-## Perform a pilot deployment
-
-A pilot deployment differs from a PoC. Where a PoC is usually a closed demonstration that is performed prior to the deployment process in order to get approval for the use of certain technologies or solutions, a *pilot deployment* is performed during the deployment process as a limited scope deployment for testing and validation. The focus of a pilot deployment can be as narrow as only a handful of devices, or wide enough to include a significant portion of your organization.
-
->[!NOTE]
->A pilot deployment should not replace the testing process that should be performed regularly in the lab as the deployment environment is built and developed. A deployment solution should be tested in virtual and physical environments as new applications and drivers are added and when task sequences are modified and before a pilot deployment is performed.
-
-For example, you are tasked with deploying Surface devices to mobile workers and you want to test the organization’s MDT deployment process by providing a small number of devices to executives. You can use SDA to create an isolated Surface deployment environment and then copy the task sequence, applications, and drivers needed from the production deployment share. This not only enables you to quickly create a Surface deployment, but it also minimizes the risk to the production deployment process used for other types of devices.
-
-For small organizations, the pilot deployment environment of SDA may suffice as a complete deployment solution. Even if you do not have an existing deployment environment, you can import drivers and applications (covered later in this article) to provide a complete deployment solution based on MDT. Even without previous knowledge of MDT or Windows deployment, you can follow the [Step-by-Step: Surface Deployment Accelerator](https://technet.microsoft.com/itpro/surface/step-by-step-surface-deployment-accelerator) article to get started with a deployment to Surface devices.
-
-## Import additional drivers
-
-The SDA deployment share includes all of the drivers needed for Surface devices. This includes the drivers for the components inside the Surface device, such as the wireless network adapter and the main chipset, as well as drivers for Surface accessories, such as the Surface Dock or Surface USB Ethernet adapters. The SDA deployment share does not, however, include drivers for third-party devices or peripherals.
-
-For example, you may intend to use your Surface device with a thermal printer, credit card reader, and barcode scanner as a POS terminal. In this scenario, the thermal printer, credit card reader, and barcode scanner will very likely require installation of drivers to operate properly. You could potentially download and install these drivers from Windows Update when each peripheral is connected, or you could install the driver package from the manufacturer manually on each Surface device, but the ideal solution is to have these drivers already present in Windows so that when the peripheral is connected, it will just work.
-
-Because SDA is built on MDT, adding the drivers to the SDA deployment share is easy and simple.
-
->[!NOTE]
->The drivers must be in the Setup Information File (.inf) format. If the drivers for your device come as an executable file (.exe), they may need to be extracted or installed to procure the .inf file. Some device drivers come packaged with applications, for example an all-in-one printer bundled with scan software. These applications will need to be installed separately from the drivers.
-
-To import drivers for a peripheral device:
-
-1. Download the drivers for your device from the manufacturer web site.
-
-2. Open the MDT Deployment Workbench.
-
-3. Expand the **Deployment Shares** node and expand the SDA deployment share.
-
-4. Expand the **Out-of-Box Drivers** folder.
-
-5. Select the folder of the Surface model for which you would like to include this driver.
-
-6. Click **Import Drivers** to start the Import Drivers Wizard, as shown in Figure 1.
-
- 
-
- *Figure 1. Provide the location of your driver files*
-
-7. The Import Drivers Wizard presents a series of steps:
-
- - **Specify Directory** – Click **Browse** and navigate to the folder where you stored the drivers in Step 1.
- - **Summary** – Review the specified configuration on this page before you click **Next** to begin the import process.
- - **Progress** – While the drivers are imported, a progress bar is displayed on this page.
- - **Confirmation** – When the import process completes, the success of the process is displayed on this page. Click **Finish** to complete the Import Drivers Wizard.
-
-8. Repeat Steps 5-7 for each Surface model on which you would like to include this driver.
-
-9. Close the Deployment Workbench.
-
-After the drivers are imported for the Surface model, the deployment task sequence will automatically select the drivers during the deployment process and include them in the Windows environment. When you connect your device, such as the barcode scanner in the example, Windows should automatically detect the device and you should be able to use it immediately.
-
->[!NOTE]
->You can even import drivers for other computer makes and models to support other devices. See **Step 5: Prepare the drivers repository** in [Deploy a Windows 10 image using MDT 2013 Update 2](https://technet.microsoft.com/itpro/windows/deploy/deploy-a-windows-10-image-using-mdt) for more information about how to import drivers for other makes and models.
-
-## Import additional applications
-
-As with drivers, the SDA deployment share can be pre-configured with apps like the Surface App and Microsoft Office 365. You can also add applications to the SDA deployment share and configure them to be installed on your Surface devices during deployment of Windows. In the ideal scenario, your Surface devices deployed with the SDA deployment share will include all of the applications needed to be ready for your end users.
-
-In the previous example for including drivers for a POS system, you would also need to include POS software for processing transactions and recording the input from the barcode scanner and credit card reader. To import an application and prepare it for installation on your Surface devices during Windows deployment:
-
-1. Download the application installation files or locate the installation media for your application.
-
-2. Determine the command line instruction for silent installation, usually provided by the developer of the application. For Windows Installer files (.msi), see [Standard Installer Command-Line Options](https://msdn.microsoft.com/library/windows/desktop/aa372024) in the Windows Dev Center.
-
-3. Open the MDT Deployment Workbench.
-
-4. Expand the **Deployment Shares** node and expand the SDA deployment share.
-
-5. Expand the **Applications** folder.
-
-6. Click **New Application** to start the New Application Wizard, as shown in Figure 2.
-
- 
-
- *Figure 2: Provide the command to install your application*
-
-7. Follow the steps of the New Application Wizard:
-
- - **Application Type** – Click **Application with Source Files**, and then click **Next**.
- - **Details** – Enter a name for the application in the **Application Name** field. Enter publisher, version, and language information in the **Publisher**, **Version**, and **Language** fields if desired. Click **Next**.
- - **Source** – Click **Browse** to navigate to and select the folder with the application installation files procured in Step 1, and then click **Next**.
- - **Destination** – Enter a name for the folder where the application files will be stored in the **Specify the Name of the Directory that Should Be Created** field or click **Next** to accept the default name.
- - **Command Details** – Enter the silent command-line instruction, for example `setup.msi /quiet /norestart`
- - **Summary** – Review the specified configuration on this page before you click **Next** to begin the import process.
- - **Progress** – While the installation files are imported, a progress bar is displayed on this page.
- - **Confirmation** – When the import process completes, the success of the process is displayed on this page. Click **Finish** to complete the New Application Wizard.
-
-8. Click the **Task Sequences** folder, right-click **1 - Deploy Microsoft Surface**, and then click **Properties**.
-
-9. Click the **Task Sequence** tab to view the steps that are included in the new task sequence.
-
-10. Select the **Windows Update (Pre-Application Installation)** step, and then click **Add**.
-
-11. Hover the mouse over **General** under the **Add** menu, and then click **Install Application**. This will add a new step after the selected step for the installation of a specific application as shown in Figure 3.
-
- 
-
- *Figure 3. A new Install Application step for Sample POS App*
-
-12. On the **Properties** tab of the new **Install Application** step, enter **Install - Sample POS App** in the **Name** field, where *Sample POS App* is the name of your app.
-
-13. Click **Install a Single Application**, and then click **Browse** to view available applications that have been imported into the deployment share.
-
-14. Select your app from the list of applications, and then click **OK**.
-
-15. Click **OK** to close the task sequence properties.
-
-16. Close the Deployment Workbench.
-
-## Work with existing deployment shares
-
-One of the many benefits of an MDT deployment share is the simplicity of how deployment resources are stored. The MDT deployment share is, at its core, just a standard network file share. All deployment resources, such as Windows images, application installation files, and drivers, are stored in a share that can be browsed with File Explorer, copied and pasted, and moved just like any other file share, provided that you have the necessary permissions. This makes working with deployment resources extremely easy. MDT even allows you to make it easier by allowing you to open multiple deployment shares from the Deployment Workbench and to transfer or copy resources between them.
-
-This ability gives SDA some extra capabilities when used in an environment with an existing MDT infrastructure. For example, if you install SDA on an isolated server to prepare a PoC and then log on to your production MDT deployment share from the Deployment Workbench on your SDA server, you can copy applications, drivers, task sequences, and other components into the SDA deployment share that is prepared with Surface apps and drivers. With this process, in a very short amount time, you can have a deployment environment ready to deploy your organization’s precise requirements to Surface devices.
-
-You can also use this capability in reverse. For example, you can copy the Surface drivers, deployment task sequences, and apps directly into a lab or testing environment following a successful PoC. Using these resources, you can immediately begin to integrate Surface deployment into your existing deployment infrastructure.
diff --git a/devices/surface/wake-on-lan-for-surface-devices.md b/devices/surface/wake-on-lan-for-surface-devices.md
deleted file mode 100644
index a6686dcf69..0000000000
--- a/devices/surface/wake-on-lan-for-surface-devices.md
+++ /dev/null
@@ -1,94 +0,0 @@
----
-title: Wake On LAN for Surface devices (Surface)
-description: See how you can use Wake On LAN to remotely wake up devices to perform management or maintenance tasks, or to enable management solutions automatically – even if the devices are powered down.
-keywords: update, deploy, driver, wol, wake-on-lan
-ms.prod: w10
-ms.mktglfcycl: manage
-ms.pagetype: surface, devices
-ms.sitesec: library
-ms.localizationpriority: medium
-author: coveminer
-ms.author: v-jokai
-ms.topic: article
-ms.reviewer: scottmca
-manager: laurawi
-ms.audience: itpro
----
-
-# Wake On LAN for Surface devices
-
-Surface devices that run Windows 10, version 1607 (also known as Windows 10 Anniversary Update) or later and use a Surface Ethernet adapter to connect to a wired network, are capable of Wake On LAN (WOL) from Connected Standby. With WOL, you can remotely wake up devices to perform management or maintenance tasks or enable management solutions (such as Microsoft Endpoint Configuration Manager) automatically. For example, you can deploy applications to Surface devices left docked with a Surface Dock or Surface Pro 3 Docking Station by using Microsoft Endpoint Configuration Manager during a window in the middle of the night, when the office is empty.
-
->[!NOTE]
->Surface devices must be connected to AC power and in Connected Standby (Sleep) to support WOL. WOL is not possible from devices that are in hibernation or powered off.
-
-## Supported devices
-
-The following devices are supported for WOL:
-
-* Surface Ethernet adapter
-* Surface USB-C to Ethernet and USB Adapter
-* Surface Dock
-* Surface Docking Station for Surface Pro 3
-* Surface 3
-* Surface Pro 3
-* Surface Pro 4
-* Surface Pro (5th Gen)
-* Surface Pro (5th Gen) with LTE Advanced
-* Surface Book
-* Surface Laptop (1st Gen)
-* Surface Pro 6
-* Surface Book 2
-* Surface Laptop 2
-* Surface Go
-* Surface Go with LTE Advanced
-* Surface Studio 2 (see Surface Studio 2 instructions below)
-* Surface Pro 7
-* Surface Laptop 3
-
-## WOL driver
-
-To enable WOL support on Surface devices, a specific driver for the Surface Ethernet adapter is required. This driver is not included in the standard driver and firmware pack for Surface devices – you must download and install it separately. You can download the Surface WOL driver (SurfaceWOL.msi) from the [Surface Tools for IT](https://www.microsoft.com/download/details.aspx?id=46703) page in the Microsoft Download Center.
-
-You can run this Microsoft Windows Installer (.msi) file on a Surface device to install the Surface WOL driver, or you can distribute it to Surface devices with an application deployment solution, such as Microsoft Endpoint Configuration Manager. To include the Surface WOL driver during deployment, you can install the .msi file as an application during the deployment process. You can also extract the Surface WOL driver files to include them in the deployment process. For example, you can include them in your Microsoft Deployment Toolkit (MDT) deployment share. You can read more about Surface deployment with MDT in [Deploy Windows 10 to Surface devices with Microsoft Deployment Toolkit](https://technet.microsoft.com/itpro/surface/deploy-windows-10-to-surface-devices-with-mdt).
-
-> [!NOTE]
-> During the installation of SurfaceWOL.msi, the following registry key is set to a value of 1, which allows easy identification of systems where the WOL driver has been installed. If you chose to extract and install these drivers separately during deployment, this registry key will not be configured and must be configured manually or with a script.
->
-> **HKLM\SYSTEM\CurrentControlSet\Control\Power AllowSystemRequiredPowerRequests**
-
-To extract the contents of SurfaceWOL.msi, use the MSIExec administrative installation option (**/a**), as shown in the following example, to extract the contents to the C:\WOL\ folder:
-
- `msiexec /a surfacewol.msi targetdir=C:\WOL /qn`
-
-## Surface Studio 2 instructions
-
-To enable WOL on Surface Studio 2, you must use the following procedure
-
-1. Create the following registry keys:
-
- ```console
- ; Set CONNECTIVITYINSTANDBY to 1:
- [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\F15576E8-98B7-4186-B944-EAFA664402D9]
- "Attributes"=dword:00000001
- ; Set EnforceDisconnectedStandby to 0 and AllowSystemRequiredPowerRequests to 1:
- [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power]
- "EnforceDisconnectedStandby"=dword:00000000
- "AllowSystemRequiredPowerRequests"=dword:00000001
- ```
-
-2. Run the following command
-
- ```powercfg /SETACVALUEINDEX SCHEME_BALANCED SUB_NONE CONNECTIVITYINSTANDBY 1```
-
-## Using Surface WOL
-
-The Surface WOL driver conforms to the WOL standard, whereby the device is woken by a special network communication known as a magic packet. The magic packet consists of 6 bytes of 255 (or FF in hexadecimal) followed by 16 repetitions of the target computer’s MAC address. You can read more about the magic packet and the WOL standard on [Wikipedia](https://wikipedia.org/wiki/Wake-on-LAN#Magic_packet).
-
->[!NOTE]
->To send a magic packet and wake up a device by using WOL, you must know the MAC address of the target device and Ethernet adapter. Because the magic packet does not use the IP network protocol, it is not possible to use the IP address or DNS name of the device.
-
-Many management solutions, such as Configuration Manager, provide built-in support for WOL. There are also many solutions, including Microsoft Store apps, PowerShell modules, third-party applications, and third-party management solutions that allow you to send a magic packet to wake up a device. For example, you can use the [Wake On LAN PowerShell module](https://gallery.technet.microsoft.com/scriptcenter/Wake-On-Lan-815424c4) from the TechNet Script Center.
-
->[!NOTE]
->After a device has been woken up with a magic packet, the device will return to sleep if an application is not actively preventing sleep on the system or if the AllowSystemRequiredPowerRequests registry key is not configured to 1, which allows applications to prevent sleep. See the [WOL driver](#wol-driver) section of this article for more information about this registry key.
diff --git a/devices/surface/windows-autopilot-and-surface-devices.md b/devices/surface/windows-autopilot-and-surface-devices.md
deleted file mode 100644
index 0860600d05..0000000000
--- a/devices/surface/windows-autopilot-and-surface-devices.md
+++ /dev/null
@@ -1,64 +0,0 @@
----
-title: Windows Autopilot and Surface devices
-ms.reviewer:
-manager: laurawi
-description: Find out about Windows Autopilot deployment options for Surface devices.
-keywords: autopilot, windows 10, surface, deployment
-ms.prod: w10
-ms.mktglfcycl: deploy
-ms.pagetype: surface, devices
-ms.sitesec: library
-author: coveminer
-ms.author: v-jokai
-ms.topic: article
-ms.localizationpriority: medium
-ms.audience: itpro
----
-
-# Windows Autopilot and Surface devices
-
-Windows Autopilot is a cloud-based deployment technology in Windows 10. You can use Windows Autopilot to remotely deploy and configure devices in a zero-touch process right out of the box.
-
-Windows Autopilot-registered devices are identified over the Internet at first startup through a unique device signature that's called a *hardware hash*. They're automatically enrolled and configured by using modern management solutions such as Azure Active Directory (Azure AD) and mobile device management.
-
-You can register Surface devices at the time of purchase from a Surface partner that's enabled for Windows Autopilot. These partners can ship new devices directly to your users. The devices will be automatically enrolled and configured when they are first turned on. This process eliminates reimaging during deployment, which lets you implement new, agile methods of device management and distribution.
-
-## Modern management
-
-Autopilot is the recommended deployment option for Surface devices, including Surface Pro 7, Surface Laptop 3, and Surface Pro X, which is specifically designed for deployment through Autopilot.
-
- It's best to enroll your Surface devices with the help of a Microsoft Cloud Solution Provider. This step allows you to manage UEFI firmware settings on Surface directly from Intune. It eliminates the need to physically touch devices for certificate management. See [Intune management of Surface UEFI settings](surface-manage-dfci-guide.md) for details.
-
-## Windows version considerations
-
-Broad deployment of Surface devices through Windows Autopilot, including enrollment by Surface partners at the time of purchase, requires Windows 10 Version 1709 (Fall Creators Update) or later.
-
-These Windows versions support a 4,000-byte (4k) hash value that uniquely identifies devices for Windows Autopilot, which is necessary for deployments at scale. All new Surface devices, including Surface Pro 7, Surface Pro X, and Surface Laptop 3, ship with Windows 10 Version 1903 or later.
-
-## Exchange experience on Surface devices in need of repair or replacement
-
-Microsoft automatically checks every Surface for Autopilot enrollment and will deregister the device from the customer’s tenant. Microsoft ensures the replacement device is enrolled into Windows Autopilot once a replacement is shipped back to the customer. This service is available on all device exchange service orders directly with Microsoft.
-
-> [!NOTE]
-> When customers use a Partner to return devices, the Partner is responsible for managing the exchange process including deregistering and enrolling devices into Windows Autopilot.
-
-## Surface partners enabled for Windows Autopilot
-
-Select Surface partners can enroll Surface devices in Windows Autopilot for you at the time of purchase. They can also ship enrolled devices directly to your users. The devices can be configured entirely through a zero-touch process by using Windows Autopilot, Azure AD, and mobile device management.
-
-Surface partners that are enabled for Windows Autopilot include:
-
-| US partners | Global partners | US distributors |
-|--------------|---------------|-------------------|
-| * [CDW](https://www.cdw.com/) | * [ALSO](https://www.also.com/ec/cms5/de_1010/1010_anbieter/microsoft/windows-autopilot/index.jsp) | * [Synnex](https://www.synnexcorp.com/us/microsoft/surface-autopilot/) |
-| * [Connection](https://www.connection.com/brand/microsoft/microsoft-surface) | * [ATEA](https://www.atea.com/) | * [Techdata](https://www.techdata.com/) |
-| * [Insight](https://www.insight.com/en_US/buy/partner/microsoft/surface/windows-autopilot.html) | * [Bechtle](https://www.bechtle.com/marken/microsoft/microsoft-windows-autopilot) | |
-| * [SHI](https://www.shi.com/Surface) | * [Cancom](https://www.cancom.de/) | |
-| * [LDI Connect](https://www.myldi.com/managed-it/) | * [Computacenter](https://www.computacenter.com/uk) | |
-| * [F1](https://www.functiononeit.com/#empower) | |
-
-## Learn more
-
-For more information about Windows Autopilot, see:
-- [Overview of Windows Autopilot](https://docs.microsoft.com/windows/deployment/windows-autopilot/windows-10-autopilot)
-- [Windows Autopilot requirements](https://docs.microsoft.com/windows/deployment/windows-autopilot/windows-autopilot-requirements)
\ No newline at end of file
diff --git a/education/developers.yml b/education/developers.yml
index 9e21b6d27f..6533d8c51c 100644
--- a/education/developers.yml
+++ b/education/developers.yml
@@ -18,16 +18,16 @@ additionalContent:
# Card
- title: UWP apps for education
summary: Learn how to write universal apps for education.
- url: https://docs.microsoft.com/en-us/windows/uwp/apps-for-education/
+ url: https://docs.microsoft.com/windows/uwp/apps-for-education/
# Card
- title: Take a test API
summary: Learn how web applications can use the API to provide a locked down experience for taking tests.
- url: https://docs.microsoft.com/en-us/windows/uwp/apps-for-education/take-a-test-api
+ url: https://docs.microsoft.com/windows/uwp/apps-for-education/take-a-test-api
# Card
- title: Office Education Dev center
summary: Integrate with Office 365 across devices and services to extend Microsoft enterprise-scale compliance and security to students, teachers, and staff in your education app
- url: https://dev.office.com/industry-verticals/edu
+ url: https://developer.microsoft.com/office/edu
# Card
- title: Data Streamer
summary: Bring new STEM experiences into the classroom with real-time data in Excel using Data Streamer. Data Streamer can send data to Excel from a sensor or application.
- url: https://docs.microsoft.com/en-us/microsoft-365/education/data-streamer
\ No newline at end of file
+ url: https://docs.microsoft.com/microsoft-365/education/data-streamer
diff --git a/education/docfx.json b/education/docfx.json
index 809a2da28f..8ba1394c6d 100644
--- a/education/docfx.json
+++ b/education/docfx.json
@@ -7,7 +7,8 @@
"**/**.yml"
],
"exclude": [
- "**/obj/**"
+ "**/obj/**",
+ "**/includes/**"
]
}
],
@@ -19,7 +20,8 @@
"**/*.svg"
],
"exclude": [
- "**/obj/**"
+ "**/obj/**",
+ "**/includes/**"
]
}
],
diff --git a/education/includes/education-content-updates.md b/education/includes/education-content-updates.md
new file mode 100644
index 0000000000..156feee1de
--- /dev/null
+++ b/education/includes/education-content-updates.md
@@ -0,0 +1,11 @@
+
+
+
+
+## Week of January 11, 2021
+
+
+| Published On |Topic title | Change |
+|------|------------|--------|
+| 1/14/2021 | [Chromebook migration guide (Windows 10)](/education/windows/chromebook-migration-guide) | modified |
+| 1/14/2021 | [Deploy Windows 10 in a school district (Windows 10)](/education/windows/deploy-windows-10-in-a-school-district) | modified |
diff --git a/education/windows/autopilot-reset.md b/education/windows/autopilot-reset.md
index e74ce568f1..8ba6fec5bb 100644
--- a/education/windows/autopilot-reset.md
+++ b/education/windows/autopilot-reset.md
@@ -64,7 +64,7 @@ Autopilot Reset is a two-step process: trigger it and then authenticate. Once yo
**To trigger Autopilot Reset**
-1. From the Windows device lock screen, enter the keystroke: **CTRL +  + R**.
+1. From the Windows device lock screen, enter the keystroke: **CTRL + Windows key + R**.
diff --git a/education/windows/chromebook-migration-guide.md b/education/windows/chromebook-migration-guide.md
index cbbdb3502b..3cd18bebdd 100644
--- a/education/windows/chromebook-migration-guide.md
+++ b/education/windows/chromebook-migration-guide.md
@@ -457,7 +457,7 @@ Table 5. Select on-premises AD DS, Azure AD, or hybrid
X
-
Use Microsoft Endpoint Configuration Manager for management
+
Use Microsoft Endpoint Manager for management
X
X
diff --git a/education/windows/configure-windows-for-education.md b/education/windows/configure-windows-for-education.md
index 688b66c92b..71f603bec9 100644
--- a/education/windows/configure-windows-for-education.md
+++ b/education/windows/configure-windows-for-education.md
@@ -9,7 +9,7 @@ ms.pagetype: edu
ms.localizationpriority: medium
author: dansimp
ms.author: dansimp
-ms.date: 08/31/2017
+ms.date:
ms.reviewer:
manager: dansimp
---
@@ -32,7 +32,7 @@ In Windows 10, version 1703 (Creators Update), it is straightforward to configur
| **Microsoft consumer experiences** | **SetEduPolicies** | Disables suggested content from Windows such as app recommendations | This is already set | This is already set | The policy must be set |
| **Cortana** | **AllowCortana** | Disables Cortana * Cortana is enabled by default on all editions in Windows 10, version 1703 | If using Windows 10 Education, upgrading from Windows 10, version 1607 to Windows 10, version 1703 will enable Cortana. See the [Recommended configuration](#recommended-configuration) section below for recommended Cortana settings. | If using Windows 10 Pro Education, upgrading from Windows 10, version 1607 to Windows 10, version 1703 will enable Cortana. See the [Recommended configuration](#recommended-configuration) section below for recommended Cortana settings. | See the [Recommended configuration](#recommended-configuration) section below for recommended Cortana settings. |
| **Safe search** | **SetEduPolicies** | Locks Bing safe search to Strict in Microsoft Edge | This is already set | This is already set | The policy must be set |
-| **Bing search advertising** | Ad free search with Bing | Disables ads when searching the internet with Bing in Microsoft Edge | Depending on your specific requirements, there are different ways to configure this as detailed in [Ad-free search with Bing](#ad-free-search-with-bing) | Depending on your specific requirements, there are different ways to configure this as detailed in [Ad-free search with Bing](#ad-free-search-with-bing) | Depending on your specific requirements, there are different ways to configure this as detailed in [Ad-free search with Bing](#ad-free-search-with-bing) |
+| **Bing search advertising** | Ad free search with Bing | Disables ads when searching the internet with Bing in Microsoft Edge. See [Ad-free search with Bing](#ad-free-search-with-bing | View configuration instructions as detailed in [Ad-free search with Bing](#ad-free-search-with-bing) | View configuration instructions as detailed in [Ad-free search with Bing](#ad-free-search-with-bing) | View configuration instructions as detailed in [Ad-free search with Bing](#ad-free-search-with-bing) |
| **Apps** | **SetEduPolicies** | Preinstalled apps like Microsoft Edge, Movies & TV, Groove, and Skype become education ready * Any app can detect Windows is running in an education ready configuration through [IsEducationEnvironment](https://docs.microsoft.com/uwp/api/windows.system.profile.educationsettings) | This is already set | This is already set | The policy must be set |
@@ -150,34 +150,10 @@ For example:
## Ad-free search with Bing
-Provide an ad-free experience that is a safer, more private search option for K–12 education institutions in the United States. Additional information is available at https://www.bing.com/classroom/about-us.
-
-> [!NOTE]
-> If you enable the guest account in shared PC mode, students using the guest account will not have an ad-free experience searching with Bing in Microsoft Edge unless the PC is connected to your school network and your school network has been configured as described in [IP registration for entire school network using Microsoft Edge](#ip-registration-for-entire-school-network-using-microsoft-edge).
+Provide an ad-free experience that is a safer, more private search option for K–12 education institutions in the United States.
### Configurations
-#### IP registration for entire school network using Microsoft Edge
-Ad-free searching with Bing in Microsoft Edge can be configured at the network level. To configure this, email bingintheclassroom@microsoft.com with the subject "New Windows 10, version 1703 (Creators Update) Registration: [School District Name]" and the include the following information in the body of the email.
-
-**District information**
-- **District or School Name:**
-- **Outbound IP Addresses (IP Range + CIDR):**
-- **Address:**
-- **City:**
-- **State Abbreviation:**
-- **Zip Code:**
-
-**Registrant information**
-- **First Name:**
-- **Last Name:**
-- **Job Title:**
-- **Email Address:**
-- **Opt-In for Email Announcements?:**
-- **Phone Number:**
-
-This will suppress ads when searching with Bing on Microsoft Edge when the PC is connected to the school network.
-
#### Azure AD and Office 365 Education tenant
To suppress ads when searching with Bing on Microsoft Edge on any network, follow these steps:
@@ -185,6 +161,8 @@ To suppress ads when searching with Bing on Microsoft Edge on any network, follo
2. Domain join the Windows 10 PCs to your Azure AD tenant (this is the same as your Office 365 tenant).
3. Configure **SetEduPolicies** according to one of the methods described in the previous sections in this topic.
4. Have students sign in with their Azure AD identity, which is the same as your Office 365 identity, to use the PC.
+> [!NOTE]
+> If you are verifying your Office 365 domain to prove education status (step 1 above), you may need to wait up to 7 days for the ad-free experience to take effect. Microsoft recommends not to roll out the browser to your students until that time.
#### Office 365 sign-in to Bing
To suppress ads only when the student signs into Bing with their Office 365 account in Microsoft Edge, follow these steps:
@@ -192,8 +170,6 @@ To suppress ads only when the student signs into Bing with their Office 365 acco
1. Configure **SetEduPolicies** according to one of the methods described in the previous sections in this topic.
2. Have students sign into Bing with their Office 365 account.
-### More information
-For more information on all the possible Bing configuration methods, see https://aka.ms/e4ahor.
## Related topics
[Deployment recommendations for school IT administrators](edu-deployment-recommendations.md)
diff --git a/education/windows/deploy-windows-10-in-a-school-district.md b/education/windows/deploy-windows-10-in-a-school-district.md
index 280778ccb4..d2a18c7393 100644
--- a/education/windows/deploy-windows-10-in-a-school-district.md
+++ b/education/windows/deploy-windows-10-in-a-school-district.md
@@ -26,69 +26,106 @@ This guide shows you how to deploy the Windows 10 operating system in a school d
Proper preparation is essential for a successful district deployment. To avoid common mistakes, your first step is to plan a typical district configuration. Just as with building a house, you need a blueprint for what your district and individual schools should look like when it’s finished. The second step in preparation is to learn how you will manage the users, apps, and devices in your district. Just as a builder needs to have the right tools to build a house, you need the right set of tools to deploy your district.
->**Note** This guide focuses on Windows 10 deployment and management in a district. For management of other devices and operating systems in education environments, see [Manage BYOD and corporate-owned devices with MDM solutions](https://www.microsoft.com/cloud-platform/mobile-device-management).
+> [!NOTE]
+> This guide focuses on Windows 10 deployment and management in a district. For management of other devices and operating systems in education environments, see [Manage BYOD and corporate-owned devices with MDM solutions](https://www.microsoft.com/cloud-platform/mobile-device-management).
### Plan a typical district configuration
As part of preparing for your district deployment, you need to plan your district configuration — the focus of this guide. Figure 1 illustrates a typical finished district configuration that you can use as a model (the blueprint in our builder analogy) for the finished state.
-
+> [!div class="mx-imgBorder"]
+> 
*Figure 1. Typical district configuration for this guide*
A *district* consists of multiple schools, typically at different physical locations. Figure 2 illustrates a typical school configuration within the district that this guide uses.
-
+> [!div class="mx-imgBorder"]
+> 
*Figure 2. Typical school configuration for this guide*
Finally, each school consists of multiple classrooms. Figure 3 shows the classroom configuration this guide uses.
-
+> [!div class="mx-imgBorder"]
+> 
*Figure 3. Typical classroom configuration in a school*
This district configuration has the following characteristics:
* It contains one or more admin devices.
+
* It contains two or more schools.
+
* Each school contains two or more classrooms.
+
* Each classroom contains one teacher device.
+
* The classrooms connect to each other through multiple subnets.
+
* All devices in each classroom connect to a single subnet.
+
* All devices have high-speed, persistent connections to each other and to the Internet.
+
* All teachers and students have access to Microsoft Store or Microsoft Store for Business.
+
* You install a 64-bit version of Windows 10 on the admin device.
+
* You install the Windows Assessment and Deployment Kit (Windows ADK) on the admin device.
+
* You install the 64-bit version of the Microsoft Deployment Toolkit (MDT) 2013 Update 2 on the admin device.
- >**Note** In this guide, all references to MDT refer to the 64-bit version of MDT 2013 Update 2.
+
+ > [!NOTE]
+ > In this guide, all references to MDT refer to the 64-bit version of MDT 2013 Update 2.
+
* The devices use Azure AD in Office 365 Education for identity management.
+
* If you have on-premises AD DS, you can [integrate Azure AD with on-premises AD DS](https://azure.microsoft.com/documentation/articles/active-directory-aadconnect/).
+
* Use [Intune](https://docs.microsoft.com/intune/), [Mobile Device Management for Office 365](https://support.office.com/en-us/article/Set-up-Mobile-Device-Management-MDM-in-Office-365-dd892318-bc44-4eb1-af00-9db5430be3cd?ui=en-US&rs=en-US&ad=US), or [Group Policy in AD DS](https://technet.microsoft.com/library/cc725828.aspx) to manage devices.
+
* Each device supports a one-student-per-device or multiple-students-per-device scenario.
+
* The devices can be a mixture of different make, model, and processor architecture (32-bit or 64-bit) or be identical.
+
* To initiate Windows 10 deployment, use a USB flash drive, DVD-ROM or CD-ROM, or Pre-Boot Execution Environment (PXE) boot.
+
* The devices can be a mixture of different Windows 10 editions, such as Windows 10 Pro, Windows 10 Enterprise, or Windows 10 Education.
Use these characteristics at a minimum as you deploy your schools. If your district deployment is less complex, you may want to review the guidance in [Deploy Windows 10 in a school](https://technet.microsoft.com/edu/windows/deploy-windows-10-in-a-school).
->**Note** This guide focuses on Intune as the mobile device management (MDM) solution. If you want to use an MDM solution other than Intune, ignore the Intune-specific content in this guide. For each section, contact your MDM provider to determine the features and management capabilities for your institution.
+> [!NOTE]
+> This guide focuses on Intune as the mobile device management (MDM) solution. If you want to use an MDM solution other than Intune, ignore the Intune-specific content in this guide. For each section, contact your MDM provider to determine the features and management capabilities for your institution.
Office 365 Education allows:
* Students and faculty to use Microsoft Office to create and edit Microsoft Word, OneNote, PowerPoint, and Excel documents in a browser.
+
* Teachers to use the [OneNote Class Notebook app](https://www.onenote.com/classnotebook) to share content and collaborate with students.
+
* Faculty to use the [OneNote Staff Notebooks app](https://www.onenote.com/staffnotebookedu) to collaborate with other teachers, the administration, and faculty.
+
* Teachers to employ Sway to create interactive educational digital storytelling.
+
* Students and faculty to use email and calendars, with mailboxes up to 50 GB per user.
+
* Faculty to use advanced email features like email archiving and legal hold capabilities.
+
* Faculty to help prevent unauthorized users from accessing documents and email by using Microsoft Azure Rights Management.
+
* Faculty to use advanced compliance tools on the unified eDiscovery pages in the Office 365 Compliance Center.
+
* Faculty to host online classes, parent–teacher conferences, and other collaboration in Skype for Business.
+
* Students and faculty to access up to 1 TB of personal cloud storage that users inside and outside the educational institution can share through OneDrive for Business.
+
* Teachers to provide collaboration in the classroom through Microsoft SharePoint Online team sites.
+
* Students and faculty to use Office 365 Video to manage videos.
+
* Students and faculty to use Yammer to collaborate through private social networking.
+
* Students and faculty to access classroom resources from anywhere on any device (including Windows 10 Mobile, iOS, and Android devices).
For more information about Office 365 Education features and an FAQ, go to [Office 365 Education plans and pricing](https://products.office.com/en-us/academic).
@@ -105,7 +142,7 @@ This guide focuses on LTI deployments to deploy the reference device. You can us
MDT includes the Deployment Workbench, a console from which you can manage the deployment of Windows 10 and your apps. You configure the deployment process in the Deployment Workbench, including the management of operating systems, device drivers, apps, and migration of user settings on existing devices.
-LTI performs deployment from a *deployment share* — a network-shared folder on the device on which you installed MDT. You can perform over-the-network deployments from the deployment share or perform deployments from a local copy of the deployment share on a USB drive or DVD. You will learn more about MDT in the [Prepare the admin device](#prepare-the-admin-device) section.
+LTI performs deployment from a *deployment share* — a network-shared folder on the device on which you installed MDT. You can perform over-the-network deployments from the deployment share or perform deployments from a local copy of the deployment share on a USB drive or DVD. You will learn more about MDT in [Prepare the admin device](#prepare-the-admin-device), earlier in this article.
The focus of MDT is deployment, so you also need tools that help you manage your Windows 10 devices and apps. You can manage Windows 10 devices and apps with Intune, the Compliance Management feature in Office 365, or Group Policy in AD DS. You can use any combination of these tools based on your school requirements.
@@ -114,9 +151,13 @@ ZTI performs fully automated deployments using Configuration Manager and MDT. Al
The configuration process requires the following devices:
* **Admin device.** This is the device you use for your day-to-day job functions. It’s also the one you use to create and manage the Windows 10 and app deployment process. You install the Windows ADK, MDT, and the Configuration Manager Console on this device.
+
* **Reference devices.** These are the devices that you will use as a template for the faculty and student devices. You install Windows 10 and Windows desktop apps on these devices, and then capture an image (.wim file) of the devices.
+
You will have a reference device for each type of device in your district. For example, if your district has Surface, HP Stream, Dell Inspiron, and Lenovo Yoga devices, then you would have a reference device for each model. For more information about approved Windows 10 devices, see [Explore devices](https://www.microsoft.com/windows/view-all).
+
* **Faculty and staff devices.** These are the devices that the teachers, faculty, and staff use for their day-to-day job functions. You use the admin device to deploy (or upgrade) Windows 10 and apps to these devices.
+
* **Student devices.** The students will use these devices. You will use the admin device deploy (or upgrade) Windows 10 and apps to them.
The high-level process for deploying and configuring devices within individual classrooms, individual schools, and the district as a whole is as follows and illustrated in Figure 4:
@@ -139,7 +180,8 @@ The high-level process for deploying and configuring devices within individual c
9. On the admin device, manage the Windows 10 devices and apps, the Office 365 subscription, and the AD DS–Azure AD integration.
-
+> [!div class="mx-imgBorder"]
+> 
*Figure 4. How district configuration works*
@@ -160,7 +202,7 @@ Before you select the deployment and management methods, you need to review the
|Scenario feature |Cloud-centric|On-premises and cloud|
|---|---|---|
|Identity management | Azure AD (stand-alone or integrated with on-premises AD DS) | AD DS integrated with Azure AD |
-|Windows 10 deployment | MDT only | Microsoft Endpoint Configuration Manager with MDT |
+|Windows 10 deployment | MDT only | Microsoft Endpoint Manager with MDT |
|Configuration setting management | Intune | Group Policy
Intune|
@@ -174,14 +216,14 @@ These scenarios assume the need to support:
Some constraints exist in these scenarios. As you select the deployment and management methods for your device, keep the following constraints in mind:
* You can use Group Policy or Intune to manage configuration settings on a device but not both.
-* You can use Microsoft Endpoint Configuration Manager or Intune to manage apps and updates on a device but not both.
+* You can use Microsoft Endpoint Manager or Intune to manage apps and updates on a device but not both.
* You cannot manage multiple users on a device with Intune if the device is AD DS domain joined.
Use the cloud-centric scenario and on-premises and cloud scenario as a guide for your district. You may need to customize these scenarios, however, based on your district. As you go through the [Select the deployment methods](#select-the-deployment-methods), [Select the configuration setting management methods](#select-the-configuration-setting-management-methods), and the [Select the app and update management products](#select-the-app-and-update-management-products) sections, remember these scenarios and use them as the basis for your district.
### Select the deployment methods
-To deploy Windows 10 and your apps, you can use MDT by itself or Microsoft Endpoint Configuration Manager and MDT together. For a district, there are a few ways to deploy Windows 10 to devices. Table 2 lists the methods that this guide describes and recommends. Use this information to determine which combination of deployment methods is right for your institution.
+To deploy Windows 10 and your apps, you can use MDT by itself or Microsoft Endpoint Manager and MDT together. For a district, there are a few ways to deploy Windows 10 to devices. Table 2 lists the methods that this guide describes and recommends. Use this information to determine which combination of deployment methods is right for your institution.
@@ -249,7 +291,7 @@ Select this method when you:
The disadvantages of this method are that it:
-
Carries an additional cost for Microsoft Endpoint Configuration Manager server licenses (if the institution does not have Configuration Manager already).
+
Carries an additional cost for Microsoft Endpoint Manager server licenses (if the institution does not have Configuration Manager already).
Can deploy Windows 10 only to domain-joined (institution-owned devices).
Requires an AD DS infrastructure (if the institution does not have AD DS already).
@@ -265,7 +307,7 @@ Record the deployment methods you selected in Table 3.
|Selection | Deployment method|
|--------- | -----------------|
| |MDT by itself |
-| |Microsoft Endpoint Configuration Manager and MDT|
+| |Microsoft Endpoint Manager and MDT|
*Table 3. Deployment methods selected*
@@ -441,12 +483,12 @@ Select this method when you:
-
Microsoft Endpoint Configuration Manager and Intune (hybrid)
+
Microsoft Endpoint Manager and Intune (hybrid)
Configuration Manager and Intune together extend Configuration Manager from an on-premises management system for domain-joined devices to a solution that can manage devices regardless of their location and connectivity options. This hybrid option provides the benefits of both Configuration Manager and Intune.
Configuration Manager and Intune in the hybrid configuration allow you to support application management throughout the entire application life cycle. You can deploy, upgrade, manage multiple versions, and retire applications by using Configuration Manager, and you can manage Windows desktop and Microsoft Store applications for both institution-owned and personal devices.
Select this method when you:
-
Selected Microsoft Endpoint Configuration Manager to deploy Windows 10.
+
Selected Microsoft Endpoint Manager to deploy Windows 10.
Want to manage institution-owned and personal devices (does not require that the device be domain joined).
Want to manage domain-joined devices.
Want to manage Azure AD domain-joined devices.
@@ -483,9 +525,9 @@ Record the app and update management methods that you selected in Table 7.
|Selection | Management method|
|----------|------------------|
-| |Microsoft Endpoint Configuration Manager by itself|
+| |Microsoft Endpoint Manager by itself|
| |Intune by itself|
-| |Microsoft Endpoint Configuration Manager and Intune (hybrid mode)|
+| |Microsoft Endpoint Manager and Intune (hybrid mode)|
*Table 7. App and update management methods selected*
@@ -512,7 +554,8 @@ For more information about installing the Windows ADK, see [Step 2-2: Install Wi
Next, install MDT. MDT uses the Windows ADK to help you manage and perform Windows 10 and app deployment. It is a free tool available directly from Microsoft.
You can use MDT to deploy 32-bit or 64-bit versions of Windows 10. Install the 64-bit version of MDT to support deployment of 32-bit and 64-bit operating systems.
->**Note** If you install the 32-bit version of MDT, you can install only 32-bit versions of Windows 10. Ensure that you download and install the 64-bit version of MDT so that you can install 64-bit and 32-bit versions of the operating system.
+> [!NOTE]
+> If you install the 32-bit version of MDT, you can install only 32-bit versions of Windows 10. Ensure that you download and install the 64-bit version of MDT so that you can install 64-bit and 32-bit versions of the operating system.
For more information about installing MDT on the admin device, see [Installing a New Instance of MDT](https://technet.microsoft.com/library/dn759415.aspx#InstallingaNewInstanceofMDT).
@@ -526,15 +569,17 @@ For more information about how to create a deployment share, see [Step 3-1: Crea
### Install the Configuration Manager console
->**Note** If you selected Microsoft Endpoint Configuration Manager to deploy Windows 10 or manage your devices (in the [Select the deployment methods](#select-the-deployment-methods) and [Select the configuration setting management methods](#select-the-configuration-setting-management-methods) sections, respectively), perform the steps in this section. Otherwise, skip this section and continue to the next.
+> [!NOTE]
+> If you selected Microsoft Endpoint Manager to deploy Windows 10 or manage your devices (in the [Select the deployment methods](#select-the-deployment-methods) and [Select the configuration setting management methods](#select-the-configuration-setting-management-methods) sections, respectively), perform the steps in this section. Otherwise, skip this section and continue to the next.
You can use Configuration Manager to manage Windows 10 deployments, Windows desktop apps, Microsoft Store apps, and software updates. To manage Configuration Manager, you use the Configuration Manager console. You must install the Configuration Manager console on every device you use to manage Configuration Manager (specifically, the admin device). The Configuration Manager console is automatically installed when you install Configuration Manager primary site servers.
-For more information about how to install the Configuration Manager console, see [Install Microsoft Endpoint Configuration Manager consoles](https://technet.microsoft.com/library/mt590197.aspx#bkmk_InstallConsole).
+For more information about how to install the Configuration Manager console, see [Install Microsoft Endpoint Manager consoles](https://technet.microsoft.com/library/mt590197.aspx#bkmk_InstallConsole).
### Configure MDT integration with the Configuration Manager console
->**Note** If you selected MDT only to deploy Windows 10 and your apps (and not Microsoft Endpoint Configuration Manager) in the [Select the deployment methods](#select-the-deployment-methods) section, then skip this section and continue to the next.
+> [!NOTE]
+> If you selected MDT only to deploy Windows 10 and your apps (and not Microsoft Endpoint Configuration Manager) in [Select the deployment methods](#select-the-deployment-methods), earlier in this article, then skip this section and continue to the next.
You can use MDT with Configuration Manager to make ZTI operating system deployment easier. To configure MDT integration with Configuration Manager, run the Configure ConfigMgr Integration Wizard. This wizard is installed when you install MDT.
@@ -544,7 +589,7 @@ For more information, see [Enable Configuration Manager Console Integration for
#### Summary
-In this section, you installed the Windows ADK and MDT on the admin device. You also created the MDT deployment share that you will configure and use later to capture a reference image. You can also use the MDT deployment share to deploy Windows 10 and your apps to faculty and students (if that’s the method you selected in the [Select the deployment methods](#select-the-deployment-methods) section). Finally, you installed the Configuration Manager console and configured MDT integration with the Configuration Manager console.
+In this section, you installed the Windows ADK and MDT on the admin device. You also created the MDT deployment share that you will configure and use later to capture a reference image. You can also use the MDT deployment share to deploy Windows 10 and your apps to faculty and students (if that’s the method you selected in [Select the deployment methods](#select-the-deployment-methods), earlier in this article). Finally, you installed the Configuration Manager console and configured MDT integration with the Configuration Manager console.
## Create and configure Office 365
@@ -590,13 +635,19 @@ You will use the Office 365 Education license plan information you record in Tab
To create a new Office 365 Education subscription for use in the classroom, use your educational institution’s email account. There are no costs to you or to students for signing up for Office 365 Education subscriptions.
->**Note** If you already have an Office 365 Education subscription, you can use that subscription and continue to the next section, [Create user accounts in Office 365](#create-user-accounts-in-office-365).
+> [!NOTE]
+> If you already have an Office 365 Education subscription, you can use that subscription and continue to the next section, [Create user accounts in Office 365](#create-user-accounts-in-office-365).
#### To create a new Office 365 subscription
1. In Microsoft Edge or Internet Explorer, type `https://portal.office.com/start?sku=faculty` in the address bar.
- > **Note** If you have already used your current sign-in account to create a new Office 365 subscription, you will be prompted to sign in. If you want to create a new Office 365 subscription, start an In-Private Window by using one of the following methods:
- >
In Microsoft Edge, open the Microsoft Edge app (press Ctrl+Shift+P, or click or tap More actions), and then click or tap New InPrivate window.
In Internet Explorer 11, open Internet Explorer 11 (press Ctrl+Shift+P, or click or tap Settings), click or tap Safety, and then click or tap InPrivate Browsing.
This policy setting allows you to specify a default AGPM Server for all domains. This is used only by AGPM Clients, and restricts Group Policy administrators from connecting to another archive. You can override this default for individual domains using the AGPM: Specify AGPM Servers setting.
-
-
-
AGPM: Specify AGPM Servers
-
This policy setting allows you to specify the AGPM Servers for individual domains. This is used only by AGPM Clients, and restricts Group Policy administrators from connecting to a different archive for the specified domain. To specify a default AGPM Server, use the AGPM: Specify default AGPM Server (all domains) setting and use this policy setting to override the default on a per domain basis.
-
-
-
-
-
-
-### Additional references
-
-- [Administrative Templates Folder](administrative-templates-folder-agpm30ops.md)
-
-- [Performing AGPM Administrator Tasks](performing-agpm-administrator-tasks-agpm30ops.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/agpm-server-connection-settings-agpm40.md b/mdop/agpm/agpm-server-connection-settings-agpm40.md
deleted file mode 100644
index c713631290..0000000000
--- a/mdop/agpm/agpm-server-connection-settings-agpm40.md
+++ /dev/null
@@ -1,62 +0,0 @@
----
-title: AGPM Server Connection Settings
-description: AGPM Server Connection Settings
-author: dansimp
-ms.assetid: cc67f122-6309-4820-92c2-f6a27d897123
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# AGPM Server Connection Settings
-
-
-You can use Administrative template settings for Advanced Group Policy Management (AGPM) to centrally configure AGPM Server connections for Group Policy administrators to whom a Group Policy Object (GPO) with these settings is applied.
-
-The following settings are available under User Configuration\\Policies\\Administrative Templates\\Windows Components\\AGPM when editing a GPO.
-
-
-
-
-
-
-
-
-
Setting
-
Effect
-
-
-
-
-
AGPM: Specify default AGPM Server (all domains)
-
This policy setting allows you to specify a default AGPM Server for all domains. This is used only by AGPM Clients, and restricts Group Policy administrators from connecting to another archive. You can override this default for individual domains using the AGPM: Specify AGPM Servers setting.
-
-
-
AGPM: Specify AGPM Servers
-
This policy setting allows you to specify the AGPM Servers for individual domains. This is used only by AGPM Clients, and restricts Group Policy administrators from connecting to a different archive for the specified domain. To specify a default AGPM Server, use the AGPM: Specify default AGPM Server (all domains) setting and use this policy setting to override the default on a per domain basis.
-
-
-
-
-
-
-### Additional references
-
-- [Administrative Templates Folder](administrative-templates-folder-agpm40.md)
-
-- [Performing AGPM Administrator Tasks](performing-agpm-administrator-tasks-agpm40.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/agpm-server-connection-settings.md b/mdop/agpm/agpm-server-connection-settings.md
deleted file mode 100644
index a615120897..0000000000
--- a/mdop/agpm/agpm-server-connection-settings.md
+++ /dev/null
@@ -1,64 +0,0 @@
----
-title: AGPM Server Connection Settings
-description: AGPM Server Connection Settings
-author: dansimp
-ms.assetid: faf78e5b-2b0d-4069-9b8c-910add892200
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# AGPM Server Connection Settings
-
-
-You can use Administrative template settings for Advanced Group Policy Management (AGPM) to centrally configure AGPM Server connections for Group Policy administrators to whom a Group Policy object (GPO) with these settings is applied.
-
-The following settings are available under User Configuration\\Administrative Templates\\Windows Components\\AGPM when editing a GPO. If this path is not visible, right-click **Administrative Templates**, and add the agpm.admx or agpm.adm template.
-
-
-
-
-
-
-
-
-
Setting
-
Effect
-
-
-
-
-
AGPM Server (all domains)
-
If enabled, this setting centrally configures one AGPM Server connection for use by all domains and disables the settings on the AGPM Server tab for Group Policy administrators. For multiple AGPM Servers, configure this setting with a default server and then configure the AGPM Server setting in the Administrative template to override this server for other domains.
-
If disabled or not configured, each Group Policy administrator must select the AGPM Server to display for each domain on the AGPM Server tab in AGPM.
-
-
-
AGPM Server
-
If enabled, this setting centrally configures multiple domain-specific AGPM Servers, overriding the AGPM Server (all domains) setting in the Administrative template. If your environment requires only a single AGPM Server, use only the AGPM Server (all domains) setting in the Administrative template.
-
If disabled or not configured, the AGPM Server (all domains) setting in the Administrative template configures the AGPM Server connection.
-
-
-
-
-
-
-### Additional references
-
-- [Administrative Template Settings](administrative-template-settings.md)
-
-- [Performing AGPM Administrator Tasks](performing-agpm-administrator-tasks.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/agpm-server-tab-agpm30ops.md b/mdop/agpm/agpm-server-tab-agpm30ops.md
deleted file mode 100644
index 1732bd6a6e..0000000000
--- a/mdop/agpm/agpm-server-tab-agpm30ops.md
+++ /dev/null
@@ -1,56 +0,0 @@
----
-title: AGPM Server Tab
-description: AGPM Server Tab
-author: dansimp
-ms.assetid: fb3b0265-53ed-4bf6-88a4-c409f5f1bed4
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# AGPM Server Tab
-
-
-The **AGPM Server** tab on the **Change Control** pane enables you to select an AGPM Server by entering a fully-qualified computer name and port, and to delete older versions of Group Policy Objects (GPOs) from the archive to conserve disk space on the AGPM Server.
-
-## Specifying the AGPM Server
-
-
-The AGPM Server selected determines which archive is displayed for you on the **Contents** tab and to which location the **Domain Delegation** settings are applied. The default port for Advanced Group Policy Management (AGPM) is port 4600.
-
-If the AGPM Server connection is centrally configured using Administrative template settings, the options on this tab for configuring the connection are unavailable. For more information, see [Configure AGPM Server Connections](configure-agpm-server-connections-agpm30ops.md).
-
-## Deleting old GPO versions
-
-
-By default, all versions of every controlled GPO are retained in the archive. However, you can configure the AGPM Service to limit the number of versions retained for each GPO and automatically delete the oldest version when that limit is exceeded. Only GPO versions displayed on the **Unique Versions** tab of the **History** window count toward the limit.
-
-**Note**
-The maximum number of unique versions to store for each GPO does not include the current version, so entering 0 retains only the current version. The limit must be no greater than 999 versions.
-
-When a GPO version is deleted, a record of that version remains in the history of the GPO, but the GPO version itself is deleted from the archive. You can prevent a GPO version from being deleted by marking it in the history as not deletable.
-
-
-
-### Additional references
-
-- [User Interface: Advanced Group Policy Management](user-interface-advanced-group-policy-management-agpm30ops.md)
-
-- [Performing AGPM Administrator Tasks](performing-agpm-administrator-tasks-agpm30ops.md)
-
-- [Performing Reviewer Tasks](performing-reviewer-tasks-agpm30ops.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/agpm-server-tab-agpm40.md b/mdop/agpm/agpm-server-tab-agpm40.md
deleted file mode 100644
index b2974b2c84..0000000000
--- a/mdop/agpm/agpm-server-tab-agpm40.md
+++ /dev/null
@@ -1,56 +0,0 @@
----
-title: AGPM Server Tab
-description: AGPM Server Tab
-author: dansimp
-ms.assetid: a6689437-233e-4f33-a0d6-f7d432c96c00
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# AGPM Server Tab
-
-
-The **AGPM Server** tab on the **Change Control** pane enables you to select an AGPM Server by entering a fully-qualified computer name and port, and to delete older versions of Group Policy Objects (GPOs) from the archive to conserve disk space on the AGPM Server.
-
-## Specifying the AGPM Server
-
-
-The AGPM Server selected determines which archive is displayed for you on the **Contents** tab and to which location the **Domain Delegation** settings are applied. The default port for Advanced Group Policy Management (AGPM) is port 4600.
-
-If the AGPM Server connection is centrally configured using Administrative template settings, the options on this tab for configuring the connection are unavailable. For more information, see [Configure AGPM Server Connections](configure-agpm-server-connections-agpm40.md).
-
-## Deleting old GPO versions
-
-
-By default, all versions of every controlled GPO are retained in the archive. However, you can configure the AGPM Service to limit the number of versions retained for each GPO and automatically delete the oldest version when that limit is exceeded. Only GPO versions displayed on the **Unique Versions** tab of the **History** window count toward the limit.
-
-**Note**
-The maximum number of unique versions to store for each GPO does not include the current version, so entering 0 retains only the current version. The limit must be no greater than 999 versions.
-
-When a GPO version is deleted, a record of that version remains in the history of the GPO, but the GPO version itself is deleted from the archive. You can prevent a GPO version from being deleted by marking it in the history as not deletable.
-
-
-
-### Additional references
-
-- [User Interface: Advanced Group Policy Management](user-interface-advanced-group-policy-management-agpm40.md)
-
-- [Performing AGPM Administrator Tasks](performing-agpm-administrator-tasks-agpm40.md)
-
-- [Performing Reviewer Tasks](performing-reviewer-tasks-agpm40.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/agpm-server-tab.md b/mdop/agpm/agpm-server-tab.md
deleted file mode 100644
index ad3006d8b0..0000000000
--- a/mdop/agpm/agpm-server-tab.md
+++ /dev/null
@@ -1,41 +0,0 @@
----
-title: AGPM Server Tab
-description: AGPM Server Tab
-author: dansimp
-ms.assetid: ce4490b7-b564-49af-8962-858ee39e0016
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# AGPM Server Tab
-
-
-The **AGPM Server** tab on the **Change Control** pane enables you to select an AGPM Server by entering a fully-qualified computer name and port. The default port for Advanced Group Policy Management (AGPM) is port 4600.
-
-The AGPM Server selected determines which archive is displayed for you on the **Contents** tab and to which location the **Domain Delegation** settings are applied.
-
-If the AGPM Server connection is centrally configured using Administrative template settings, the options on this tab are unavailable. For more information, see [Configure the AGPM Server Connection](configure-the-agpm-server-connection.md).
-
-### Additional references
-
-- [User Interface: Advanced Group Policy Management](user-interface-advanced-group-policy-management.md)
-
-- [Performing AGPM Administrator Tasks](performing-agpm-administrator-tasks.md)
-
-- [Performing Reviewer Tasks](performing-reviewer-tasks.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/approve-or-reject-a-pending-action-agpm30ops.md b/mdop/agpm/approve-or-reject-a-pending-action-agpm30ops.md
deleted file mode 100644
index 3d7d96b30b..0000000000
--- a/mdop/agpm/approve-or-reject-a-pending-action-agpm30ops.md
+++ /dev/null
@@ -1,62 +0,0 @@
----
-title: Approve or Reject a Pending Action
-description: Approve or Reject a Pending Action
-author: dansimp
-ms.assetid: 6d78989a-b600-4876-9dd9-bc6207ff2ce7
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Approve or Reject a Pending Action
-
-
-The core responsibility of an Approver is to evaluate and then approve or reject requests for Group Policy Object (GPO) creation, deployment, and deletion from Editors or Reviewers who do not have permission to complete those actions. Reports can assist an Approver with evaluating a new version of a GPO.
-
-A user account with the Approver or AGPM Administrator (Full Control) role or necessary permissions in Advanced Group Policy Management (AGPM) is required to complete this procedure. Review the details in "Additional considerations" in this topic.
-
-**To approve or reject a pending request**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. On the **Contents** tab, click the **Pending** tab to display the pending GPOs.
-
-3. Right-click a pending GPO, and then click either **Approve** or **Reject**.
-
-4. If approving deployment, click **Advanced** in the **Approve Pending Operation** dialog box to review links to the GPO. Pause the mouse pointer on an item in the tree to display details.
-
- - By default, all links to the GPO will be restored.
-
- - To prevent a link from being restored, clear the check box for that link.
-
- - To prevent all links from being restored, clear the **Restore Links** check box in the **Deploy GPO** dialog box.
-
-5. Click **Yes** or **OK** to confirm approval or rejection of the pending action. If you have approved the request, the GPO is moved to the appropriate tab for the action performed.
-
- **Note**
- If an Approver's e-mail address is included in the **To e-mail address** field on the **Domain** **Delegation** tab, the Approver will receive e-mail from the AGPM alias when an Editor or Reviewer submits a request.
-
-
-
-### Additional considerations
-
-- By default, you must be an Approver or an AGPM Administrator (Full Control) to perform this procedure. Specifically, you must have the permissions required to perform the request that you are approving.
-
-### Additional references
-
-- [Performing Approver Tasks](performing-approver-tasks-agpm30ops.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/approve-or-reject-a-pending-action-agpm40.md b/mdop/agpm/approve-or-reject-a-pending-action-agpm40.md
deleted file mode 100644
index c03d30ec60..0000000000
--- a/mdop/agpm/approve-or-reject-a-pending-action-agpm40.md
+++ /dev/null
@@ -1,62 +0,0 @@
----
-title: Approve or Reject a Pending Action
-description: Approve or Reject a Pending Action
-author: dansimp
-ms.assetid: 078ea8b5-9ac5-45fc-9ac1-a1aa629c10b4
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Approve or Reject a Pending Action
-
-
-The core responsibility of an Approver is to evaluate and then approve or reject requests for Group Policy Object (GPO) creation, deployment, and deletion from Editors or Reviewers who do not have permission to complete those actions. Reports can assist an Approver with evaluating a new version of a GPO.
-
-A user account with the Approver or AGPM Administrator (Full Control) role or necessary permissions in Advanced Group Policy Management (AGPM) is required to complete this procedure. Review the details in "Additional considerations" in this topic.
-
-**To approve or reject a pending request**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. On the **Contents** tab, click the **Pending** tab to display the pending GPOs.
-
-3. Right-click a pending GPO, and then click either **Approve** or **Reject**.
-
-4. If approving deployment, click **Advanced** in the **Approve Pending Operation** dialog box to review links to the GPO. Pause the mouse pointer on an item in the tree to display details.
-
- - By default, all links to the GPO will be restored.
-
- - To prevent a link from being restored, clear the check box for that link.
-
- - To prevent all links from being restored, clear the **Restore Links** check box in the **Deploy GPO** dialog box.
-
-5. Click **Yes** or **OK** to confirm approval or rejection of the pending action. If you have approved the request, the GPO is moved to the appropriate tab for the action performed.
-
- **Note**
- If an Approver's e-mail address is included in the **To e-mail address** field on the **Domain** **Delegation** tab, the Approver will receive e-mail from the AGPM alias when an Editor or Reviewer submits a request.
-
-
-
-### Additional considerations
-
-- By default, you must be an Approver or an AGPM Administrator (Full Control) to perform this procedure. Specifically, you must have the permissions required to perform the request that you are approving.
-
-### Additional references
-
-- [Performing Approver Tasks](performing-approver-tasks-agpm40.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/approve-or-reject-a-pending-action.md b/mdop/agpm/approve-or-reject-a-pending-action.md
deleted file mode 100644
index 7d7dea9ee8..0000000000
--- a/mdop/agpm/approve-or-reject-a-pending-action.md
+++ /dev/null
@@ -1,62 +0,0 @@
----
-title: Approve or Reject a Pending Action
-description: Approve or Reject a Pending Action
-author: dansimp
-ms.assetid: 22921a51-50fb-4a47-bec1-4f563f523675
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Approve or Reject a Pending Action
-
-
-The core responsibility of an Approver is to evaluate and then approve or reject requests for Group Policy object (GPO) creation, deployment, and deletion from Editors or Reviewers who do not have permission to complete those actions. The report capabilities of Advanced Group Policy Management (AGPM) can assist an Approver with evaluating a new version of a GPO.
-
-A user account with the Approver or AGPM Administrator (Full Control) role or necessary permissions in Advanced Group Policy Management is required to complete this procedure. Review the details in "Additional considerations" in this topic.
-
-**To approve or reject a pending request**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. On the **Contents** tab, click the **Pending** tab to display the pending GPOs.
-
-3. Right-click a pending GPO, and then click either **Approve** or **Reject**.
-
-4. If approving deployment, click **Advanced** in the **Approve Pending Operation** dialog box to review links to the GPO. Pause the mouse pointer on a node in the tree to display details.
-
- - By default, all links to the GPO will be restored.
-
- - To prevent a link from being restored, clear the check box for that link.
-
- - To prevent all links from being restored, clear the **Restore Links** check box in the **Deploy GPO** dialog box.
-
-5. Click **Yes** or **OK** to confirm approval or rejection of the pending action. If you have approved the request, the GPO is moved to the appropriate tab for the action performed.
-
- **Note**
- If an Approver's e-mail address is included in the **To** field on the **Domain** **Delegation** tab, the Approver will receive e-mail from the AGPM alias when an Editor or Reviewer submits a request.
-
-
-
-### Additional considerations
-
-- By default, you must be an Approver or an AGPM Administrator (Full Control) to perform this procedure. Specifically, you must have the permissions required to perform the request that you are approving.
-
-### Additional references
-
-- [Performing Approver Tasks](performing-approver-tasks.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/back-up-the-archive-agpm40.md b/mdop/agpm/back-up-the-archive-agpm40.md
deleted file mode 100644
index af468e9671..0000000000
--- a/mdop/agpm/back-up-the-archive-agpm40.md
+++ /dev/null
@@ -1,54 +0,0 @@
----
-title: Back Up the Archive
-description: Back Up the Archive
-author: dansimp
-ms.assetid: 538d85eb-3596-4c1d-bbd7-26bc28857c28
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Back Up the Archive
-
-
-To help in the recovery of the archive for Advanced Group Policy Management (AGPM) if there is a disaster, an AGPM Administrator (Full Control) should back up the archive frequently. By default, the archive is created in %ProgramData%\\Microsoft\\AGPM. However, you can specify a different path during the setup of Microsoft Advanced Group Policy Management - Server.
-
-A user account that has access to both the AGPM Server—the computer on which the AGPM Service is installed—and to the folder that contains the archive is required to complete this procedure.
-
-**To back up the archive**
-
-1. Stop the AGPM Service. For more information, see [Start and Stop the AGPM Service](start-and-stop-the-agpm-service-agpm40.md).
-
-2. Back up the archive folder by using Windows Explorer, Xcopy, Windows Server® Backup, or another backup tool. Make sure that you back up hidden, system, and read-only files.
-
-3. Store the archive backup in a secure location.
-
-4. Restart the AGPM Service. For more information, see [Start and Stop the AGPM Service](start-and-stop-the-agpm-service-agpm40.md).
-
-**Note**
-If an AGPM Administrator backs up the archive infrequently, the Group Policy Objects (GPOs) in the archive backup will not be current. To better ensure that the archive backup is current, back up the archive as part of your organization’s daily backup strategy.
-
-
-
-### Additional references
-
-- [Restore the Archive from a Backup](restore-the-archive-from-a-backup-agpm40.md)
-
-- [Move the AGPM Server and the Archive](move-the-agpm-server-and-the-archive-agpm40.md)
-
-- [Managing the Archive](managing-the-archive-agpm40.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/back-up-the-archive.md b/mdop/agpm/back-up-the-archive.md
deleted file mode 100644
index 71c30b98c3..0000000000
--- a/mdop/agpm/back-up-the-archive.md
+++ /dev/null
@@ -1,54 +0,0 @@
----
-title: Back Up the Archive
-description: Back Up the Archive
-author: dansimp
-ms.assetid: 400176da-3518-4475-ad19-c96cda6ca7ba
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Back Up the Archive
-
-
-To help in the recovery of the archive for Advanced Group Policy Management (AGPM) if there is a disaster, an AGPM Administrator (Full Control) should back up the archive frequently. By default, the archive is created in %ProgramData%\\Microsoft\\AGPM. However, you can specify a different path during the setup of Microsoft Advanced Group Policy Management - Server.
-
-A user account that has access to both the AGPM Server—the computer on which the AGPM Service is installed—and to the folder that contains the archive is required to complete this procedure.
-
-**To back up the archive**
-
-1. Stop the AGPM Service. For more information, see [Start and Stop the AGPM Service](start-and-stop-the-agpm-service-agpm30ops.md).
-
-2. Back up the archive folder by using Windows Explorer, Xcopy, Windows Server® Backup, or another backup tool. Make sure that you back up hidden, system, and read-only files.
-
-3. Store the archive backup in a secure location.
-
-4. Restart the AGPM Service. For more information, see [Start and Stop the AGPM Service](start-and-stop-the-agpm-service-agpm30ops.md).
-
-**Note**
-If an AGPM Administrator backs up the archive infrequently, the Group Policy Objects (GPOs) in the archive backup will not be current. To better ensure that the archive backup is current, back up the archive as part of your organization’s daily backup strategy.
-
-
-
-### Additional references
-
-- [Restore the Archive from a Backup](restore-the-archive-from-a-backup.md)
-
-- [Move the AGPM Server and the Archive](move-the-agpm-server-and-the-archive.md)
-
-- [Managing the Archive](managing-the-archive.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/best-practices-for-version-control-agpm40.md b/mdop/agpm/best-practices-for-version-control-agpm40.md
deleted file mode 100644
index 59b5394a61..0000000000
--- a/mdop/agpm/best-practices-for-version-control-agpm40.md
+++ /dev/null
@@ -1,45 +0,0 @@
----
-title: Best Practices for Version Control
-description: Best Practices for Version Control
-author: dansimp
-ms.assetid: 4a2a1ac7-67f3-4ba3-ab07-860d33da0efe
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Best Practices for Version Control
-
-
-Microsoft Advanced Group Policy Management (AGPM) provides version control for Group Policy Objects (GPOs) much like Microsoft Visual SourceSafe® provides version control for source code. Developers can use Visual SourceSafe to manage multiple versions of each source file. Group Policy administrators can use AGPM to do the same for GPOs. When you use AGPM, Group Policy administrators should be aware of best practices that apply to any version control system:
-
-- **Date and time:** AGPM stamps each version of a GPO with the date and time. To ensure that history is accurate, especially when you edit GPOs on more than one computer, make sure that each computer synchronizes its clock with one authoritative time source.
-
-- **Check in GPOs when you are finished editing them:** It is common for Editors to check out GPOs and forget to check them back into the archive. However, this can prevent other Group Policy administrators from changing the GPO. Always check GPOs back in to AGPM immediately when you are finished editing.
-
-- **Save changes frequently:** When you edit a GPO, save changes frequently. Most Editors check out a GPO, make many changes, and then check the GPO into the archive. Instead, check the GPO into the archive regularly, and then check it out again. The detail can be as small as checking in the GPO after you change every setting (not recommended) or checking in the GPO after you make groups of related changes. The result is a better-documented history for each GPO that can help when troubleshooting issues.
-
-- **Deploy GPOs frequently:** Do not let new and edited GPOs that have not yet been deployed accumulate in large numbers in the archive. Instead, deploy new and edited GPOs as soon as possible so that they have a minimum effect on the production environment. Deploying many new and edited GPOs at one time can jeopardize the production environment.
-
-- **Document the purpose of changes when you check in GPOs:** Any Reviewer can compare versions of a GPO to see specific changes between the two. Documenting those specific changes adds no value. Instead, document the intent and purpose of a change instead of documenting what Reviewers can see by viewing difference reports. Version comments should add value to the comparison report and help a Reviewer understand why the Editor changed the GPO.
-
-- **Test GPOs in a test environment:** Deploying GPOs to the production environment without testing them is risky. Instead, test your GPOs in a domain in a test forest, and then export the GPOs to files and import them to a domain in a production forest. Also, you can link GPOs to an organizational unit that contains test computers and users. Verify that each GPO functions correctly in the test environment and then deploy the GPOs to the production environment.
-
-### Additional references
-
-- [Advanced Group Policy Management 4.0](advanced-group-policy-management-40.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/best-practices-for-version-control.md b/mdop/agpm/best-practices-for-version-control.md
deleted file mode 100644
index e9e4d02c9b..0000000000
--- a/mdop/agpm/best-practices-for-version-control.md
+++ /dev/null
@@ -1,45 +0,0 @@
----
-title: Best Practices for Version Control
-description: Best Practices for Version Control
-author: dansimp
-ms.assetid: 89067f6a-f7ea-4dad-999d-118284cf6c5a
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Best Practices for Version Control
-
-
-Microsoft Advanced Group Policy Management (AGPM) provides version control for Group Policy Objects (GPOs) much like Microsoft Visual SourceSafe® provides version control for source code. Developers can use Visual SourceSafe to manage multiple versions of each source file. Group Policy administrators can use AGPM to do the same for GPOs. When you use AGPM, Group Policy administrators should be aware of best practices that apply to any version control system:
-
-- **Date and time:** AGPM stamps each version of a GPO with the date and time. To ensure that history is accurate, especially when you edit GPOs on more than one computer, make sure that each computer synchronizes its clock with one authoritative time source.
-
-- **Check in GPOs when you are finished editing them:** It is common for Editors to check out GPOs and forget to check them back into the archive. However, this can prevent other Group Policy administrators from changing the GPO. Always check GPOs back in to AGPM immediately when you are finished editing.
-
-- **Save changes frequently:** When you edit a GPO, save changes frequently. Most Editors check out a GPO, make many changes, and then check the GPO into the archive. Instead, check the GPO into the archive regularly, and then check it out again. The detail can be as small as checking in the GPO after you change every setting (not recommended) or checking in the GPO after you make groups of related changes. The result is a better-documented history for each GPO that can help when troubleshooting issues.
-
-- **Deploy GPOs frequently:** Do not let new and edited GPOs that have not yet been deployed accumulate in large numbers in the archive. Instead, deploy new and edited GPOs as soon as possible so that they have a minimum effect on the production environment. Deploying many new and edited GPOs at one time can jeopardize the production environment.
-
-- **Document the purpose of changes when you check in GPOs:** Any Reviewer can compare versions of a GPO to see specific changes between the two. Documenting those specific changes adds no value. Instead, document the intent and purpose of a change instead of documenting what Reviewers can see by viewing difference reports. Version comments should add value to the comparison report and help a Reviewer understand why the Editor changed the GPO.
-
-- **Test GPOs in a lab before you deploy:** Deploying GPOs to the production environment without first testing them is risky. Instead, test GPOs in a lab environment by linking them to an organizational unit that contains test computers and users, and then verifying that they function correctly. After verifying each GPO in the lab, deploy the GPO to the production environment.
-
-### Additional references
-
-- [Operations Guide for Microsoft Advanced Group Policy Management 3.0](operations-guide-for-microsoft-advanced-group-policy-management-30-agpm30ops.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/check-in-a-gpo-agpm30ops.md b/mdop/agpm/check-in-a-gpo-agpm30ops.md
deleted file mode 100644
index f23e725ea1..0000000000
--- a/mdop/agpm/check-in-a-gpo-agpm30ops.md
+++ /dev/null
@@ -1,55 +0,0 @@
----
-title: Check In a GPO
-description: Check In a GPO
-author: dansimp
-ms.assetid: 437397db-c94b-4940-b1a4-05442619ebee
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Check In a GPO
-
-
-Ordinarily, Editors should check in Group Policy Objects (GPOs) that they have edited when their modifications are complete. (For details, see [Edit a GPO Offline](edit-a-gpo-offline-agpm30ops.md).) However, if the Editor is unavailable, an Approver can also check in a GPO.
-
-A user account with the Editor, Approver, or AGPM Administrator (Full Control) role or necessary permissions in Advanced Group Policy Management (AGPM) is required to complete this procedure. Review the details in "Additional considerations" in this topic.
-
-**To check in a GPO that has been checked out by an Editor**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. On the **Contents** tab, click the **Controlled** tab to display the controlled GPOs.
-
- - To discard any changes made by the Editor, right-click the GPO, click **Undo Check Out**, and then click **Yes** to confirm.
-
- - To retain changes made by the Editor, right-click the GPO and then click **Check In**.
-
-3. Type a comment to be displayed in the audit trail of the GPO, and then click **OK**.
-
-4. When the **Progress** window indicates that overall progress is complete, click **Close**. On the **Controlled** tab, the state of the GPO is identified as **Checked In**.
-
-### Additional considerations
-
-- By default, you must be an Editor, an Approver, or an AGPM Administrator (Full Control) to perform this procedure. Specifically, you must have **List Contents** and either **Edit Settings** or **Deploy GPO** permissions for the GPO. If you are not an Approver or AGPM Administrator (or other Group Policy administrator with **Deploy GPO** permission), you must be the Editor who has checked out the GPO.
-
-### Additional references
-
-- [Performing Approver Tasks](performing-approver-tasks-agpm30ops.md)
-
-- [Edit a GPO Offline](edit-a-gpo-offline-agpm30ops.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/check-in-a-gpo-agpm40.md b/mdop/agpm/check-in-a-gpo-agpm40.md
deleted file mode 100644
index fb203386c7..0000000000
--- a/mdop/agpm/check-in-a-gpo-agpm40.md
+++ /dev/null
@@ -1,55 +0,0 @@
----
-title: Check In a GPO
-description: Check In a GPO
-author: dansimp
-ms.assetid: b838c8a2-eb9e-4e5b-8740-d7701a4294ac
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Check In a GPO
-
-
-Ordinarily, Editors should check in Group Policy Objects (GPOs) that they have edited when their modifications are complete. (For details, see [Edit a GPO Offline](edit-a-gpo-offline-agpm40.md).) However, if the Editor is unavailable, an Approver can also check in a GPO.
-
-A user account with the Editor, Approver, or AGPM Administrator (Full Control) role or necessary permissions in Advanced Group Policy Management (AGPM) is required to complete this procedure. Review the details in "Additional considerations" in this topic.
-
-**To check in a GPO that has been checked out by an Editor**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. On the **Contents** tab, click the **Controlled** tab to display the controlled GPOs.
-
- - To discard any changes made by the Editor, right-click the GPO, click **Undo Check Out**, and then click **Yes** to confirm.
-
- - To retain changes made by the Editor, right-click the GPO and then click **Check In**.
-
-3. Type a comment to be displayed in the audit trail of the GPO, and then click **OK**.
-
-4. When the **Progress** window indicates that overall progress is complete, click **Close**. On the **Controlled** tab, the state of the GPO is identified as **Checked In**.
-
-### Additional considerations
-
-- By default, you must be an Editor, an Approver, or an AGPM Administrator (Full Control) to perform this procedure. Specifically, you must have **List Contents** and either **Edit Settings** or **Deploy GPO** permissions for the GPO. If you are not an Approver or AGPM Administrator (or other Group Policy administrator with **Deploy GPO** permission), you must be the Editor who has checked out the GPO.
-
-### Additional references
-
-- [Performing Approver Tasks](performing-approver-tasks-agpm40.md)
-
-- [Edit a GPO Offline](edit-a-gpo-offline-agpm40.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/check-in-a-gpo-approver.md b/mdop/agpm/check-in-a-gpo-approver.md
deleted file mode 100644
index 7547a20849..0000000000
--- a/mdop/agpm/check-in-a-gpo-approver.md
+++ /dev/null
@@ -1,55 +0,0 @@
----
-title: Check In a GPO
-description: Check In a GPO
-author: dansimp
-ms.assetid: e428cfff-651f-4903-bf01-d742714d2fa9
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Check In a GPO
-
-
-Ordinarily, Editors should check in Group Policy objects (GPOs) that they have edited when their modifications are complete. (For details, see [Edit a GPO Offline](edit-a-gpo-offline.md).) However, if the Editor is unavailable, an Approver can also check in a GPO.
-
-A user account with the Editor, Approver, or AGPM Administrator (Full Control) role or necessary permissions in Advanced Group Policy Management is required to complete this procedure. Review the details in "Additional considerations" in this topic.
-
-**To check in a GPO that has been checked out by an Editor**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. On the **Contents** tab in the details pane, click the **Controlled** tab to display the controlled GPOs.
-
- - To discard any changes made by the Editor, right-click the GPO, click **Undo Check Out**, and then click **Yes** to confirm.
-
- - To retain changes made by the Editor, right-click the GPO and then click **Check In**.
-
-3. Type a comment to be displayed in the audit trail of the GPO, and then click **OK**.
-
-4. When the **Progress** window indicates that overall progress is complete, click **Close**. On the **Controlled** tab, the state of the GPO is identified as **Checked In**.
-
-### Additional considerations
-
-- By default, you must be an Editor, an Approver, or an AGPM Administrator (Full Control) to perform this procedure. Specifically, you must have **List Contents** and either **Edit Settings** or **Deploy GPO** permissions for the GPO. If you are not an Approver or AGPM Administrator (or other Group Policy administrator with **Deploy GPO** permission), you must be the Editor who has checked out the GPO.
-
-### Additional references
-
-- [Performing Approver Tasks](performing-approver-tasks.md)
-
-- [Edit a GPO Offline](edit-a-gpo-offline.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/checklist-administer-the-agpm-server-and-archive-agpm40.md b/mdop/agpm/checklist-administer-the-agpm-server-and-archive-agpm40.md
deleted file mode 100644
index f04859c49f..0000000000
--- a/mdop/agpm/checklist-administer-the-agpm-server-and-archive-agpm40.md
+++ /dev/null
@@ -1,93 +0,0 @@
----
-title: Checklist Administer the AGPM Server and Archive
-description: Checklist Administer the AGPM Server and Archive
-author: dansimp
-ms.assetid: d9c60203-90c2-48a7-9318-197e0ec5038b
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Checklist: Administer the AGPM Server and Archive
-
-
-In Advanced Group Policy Management (AGPM), both the AGPM Service and the archive are managed by AGPM Administrators (Full Control). The following are typical tasks for an AGPM Administrator.
-
-
-
-
-
-
-
-
-
Frequent Task
-
Reference
-
-
-
-
-
Delegate access to Group Policy Objects (GPOs) in the archive.
-
-
-
-### Additional references
-
-- [Advanced Group Policy Management 4.0](advanced-group-policy-management-40.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/checklist-administer-the-agpm-server-and-archive.md b/mdop/agpm/checklist-administer-the-agpm-server-and-archive.md
deleted file mode 100644
index ff4a199b6e..0000000000
--- a/mdop/agpm/checklist-administer-the-agpm-server-and-archive.md
+++ /dev/null
@@ -1,93 +0,0 @@
----
-title: Checklist Administer the AGPM Server and Archive
-description: Checklist Administer the AGPM Server and Archive
-author: dansimp
-ms.assetid: 0b2eb536-c3cc-462f-a42f-27a53f57bc55
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Checklist: Administer the AGPM Server and Archive
-
-
-In Advanced Group Policy Management (AGPM), both the AGPM Service and the archive are managed by AGPM Administrators (Full Control). The following are typical tasks for an AGPM Administrator.
-
-
-
-
-
-
-
-
-
Frequent Task
-
Reference
-
-
-
-
-
Delegate access to Group Policy Objects (GPOs) in the archive.
-
-
-
-### Additional references
-
-- [Operations Guide for Microsoft Advanced Group Policy Management 3.0](operations-guide-for-microsoft-advanced-group-policy-management-30-agpm30ops.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/checklist-create-edit-and-deploy-a-gpo-agpm30ops.md b/mdop/agpm/checklist-create-edit-and-deploy-a-gpo-agpm30ops.md
deleted file mode 100644
index 5c37765df2..0000000000
--- a/mdop/agpm/checklist-create-edit-and-deploy-a-gpo-agpm30ops.md
+++ /dev/null
@@ -1,75 +0,0 @@
----
-title: Checklist Create, Edit, and Deploy a GPO
-description: Checklist Create, Edit, and Deploy a GPO
-author: dansimp
-ms.assetid: a7a17706-304a-4455-9ada-52508ec620f1
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Checklist: Create, Edit, and Deploy a GPO
-
-
-In an environment where multiple people make changes to Group Policy Objects (GPOs) using Advanced Group Policy Management (AGPM), an AGPM Administrator (Full Control) delegates permission to Editors, Approvers, and Reviewers, either as groups or as individuals. The following is a typical GPO development process for an Editor and an Approver.
-
-
-
-
-
-
-
-
-
Task
-
Reference
-
-
-
-
-
Editor requests the creation of a new GPO or an Approver creates a new GPO.
Editor checks out a copy of the GPO from the archive, so no one else can modify the GPO. Editor makes changes to the GPO, and then checks the modified GPO into the archive.
-
-
-
-### Additional references
-
-[Operations Guide for Microsoft Advanced Group Policy Management 3.0](operations-guide-for-microsoft-advanced-group-policy-management-30-agpm30ops.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/checklist-create-edit-and-deploy-a-gpo-agpm40.md b/mdop/agpm/checklist-create-edit-and-deploy-a-gpo-agpm40.md
deleted file mode 100644
index 7df4177133..0000000000
--- a/mdop/agpm/checklist-create-edit-and-deploy-a-gpo-agpm40.md
+++ /dev/null
@@ -1,79 +0,0 @@
----
-title: Checklist Create, Edit, and Deploy a GPO
-description: Checklist Create, Edit, and Deploy a GPO
-author: dansimp
-ms.assetid: 44631bed-16d2-4b5a-af70-17a73fb5f6af
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Checklist: Create, Edit, and Deploy a GPO
-
-
-In an environment where multiple people change Group Policy Objects (GPOs) by using Advanced Group Policy Management (AGPM), an AGPM Administrator (Full Control) delegates permission to Editors, Approvers, and Reviewers either as groups or as individuals. The following is a typical GPO development process for an Editor and an Approver.
-
-
-
-
-
-
-
-
-
Task
-
Reference
-
-
-
-
-
Editor requests that a new GPO be created or an Approver creates a new GPO.
Editor checks out a copy of the GPO from the archive so that no one else can modify the GPO. Editor makes changes to the GPO, and then checks the modified GPO into the archive.
If developing in a test forest, Editor exports the GPO to a file, transfers the file to the production forest, and imports the file. Additionally, an Editor can link the GPO to an organizational unit that contains test computers and users.
-
-
-
-### Additional references
-
-[Advanced Group Policy Management 4.0](advanced-group-policy-management-40.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/checklist-create-edit-and-deploy-a-gpo.md b/mdop/agpm/checklist-create-edit-and-deploy-a-gpo.md
deleted file mode 100644
index a6b860cc5d..0000000000
--- a/mdop/agpm/checklist-create-edit-and-deploy-a-gpo.md
+++ /dev/null
@@ -1,71 +0,0 @@
----
-title: Checklist Create, Edit, and Deploy a GPO
-description: Checklist Create, Edit, and Deploy a GPO
-author: dansimp
-ms.assetid: 614e2d9a-c18b-4f62-99fd-e17a2ac8559d
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Checklist: Create, Edit, and Deploy a GPO
-
-
-In an environment where multiple people make changes to Group Policy objects (GPOs), an AGPM Administrator (Full Control) delegates permission to Editors, Approvers, and Reviewers, either as groups or as individuals. The following is a typical GPO development process for an Editor and an Approver.
-
-
-
-
-
-
-
-
-
Task
-
Reference
-
-
-
-
-
Editor requests the creation of a new GPO or an Approver creates a new GPO.
Editor checks out a copy of the GPO from the archive, so no one else can modify the GPO. Editor makes changes to the GPO, and then checks the modified GPO into the archive.
-
-
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/choosing-which-version-of-agpm-to-install.md b/mdop/agpm/choosing-which-version-of-agpm-to-install.md
deleted file mode 100644
index 792101fd83..0000000000
--- a/mdop/agpm/choosing-which-version-of-agpm-to-install.md
+++ /dev/null
@@ -1,309 +0,0 @@
----
-title: Choosing Which Version of AGPM to Install
-description: Choosing Which Version of AGPM to Install
-author: dansimp
-ms.assetid: 31357d2a-bc23-4e15-93f4-0beda8ab7a7b
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 04/05/2017
----
-
-
-# Choosing Which Version of AGPM to Install
-
-
-Each release of Microsoft Advanced Group Policy Management (AGPM) supports specific versions of the Windows operating system. We strongly recommend that you run the AGPM Client and AGPM Server on the same line of operating systems. For example, Windows 10 with Windows Server 2016, Windows 8.1 with Windows Server 2012 R2, and so on.
-
-We recommend that you install the AGPM Server on the most recent version of the operating system in the domain. AGPM uses the Group Policy Management Console (GPMC) to back up and restore Group Policy Objects (GPOs). Because newer versions of the GPMC provide additional policy settings that are not available in earlier versions, you can manage more policy settings by using the most recent version of the operating system.
-
-All versions of AGPM can manage only the policy settings that were introduced in the same version or an earlier version of the operating system on which AGPM is running. For example, if you install AGPM 4.0 SP2 on Windows Server 2012, you can manage policy settings that were introduced in Windows Server 2012 or earlier, but you cannot manage policy settings that were introduced later, in Windows 8.1 or Windows Server 2012 R2.
-
-If the version of the GPMC on your AGPM Server is older than the version on the computers that administrators use to manage Group Policy, the AGPM Server will be unable to store any policy settings that are not available in the older version of the GPMC. For a spreadsheet of Group Policy settings included in Windows, see [Group Policy Settings Reference for Windows and Windows Server](https://go.microsoft.com/fwlink/p/?LinkId=613627).
-
-## AGPM 4.0 SP3
-
-
-If you are using computers that are running Windows 10 to manage GPOs, you must use AGPM 4.0 SP3. You cannot install earlier versions of AGPM on computers that are running the Windows 10 operating system.
-
-Table 1 lists the operating systems on which you can install AGPM 4.0 SP3, and the policy settings that you can manage by using AGPM 4.0 SP3.
-
-**Table 1: AGPM 4.0 SP3 supported operating systems and policy settings**
-
-
-
-
-
-
-
-
-
-
Supported configurations for the AGPM Server
-
Supported configurations for the AGPM Client
-
AGPM Support
-
-
-
-
-
Windows Server 2016 or Windows 10
-
Windows Server 2016 or Windows 10
-
Supported
-
-
-
Windows Server 2012 R2
-
Windows 10
-
Supported with the caveats outlined in KB 4015786
-
-
-
-
Windows Server 2012 R2 or Windows 8.1
-
Windows Server 2012 R2 or Windows 8.1
-
Supported
-
-
-
Windows Server 2012 R2, Windows Server 2012, or Windows 8.1
-
Windows Server 2012 or Windows 8.1
-
Supported, but cannot edit policy settings or preference items that exist only in Windows 8.1
-
-
-
Windows Server 2008 R2 or Windows 7
-
Windows Server 2008 R2 or Windows 7
-
Supported, but cannot edit policy settings or preference items that exist only in Windows 8.1
-
-
-
Windows Server 2012, Windows Server 2008 R2, or Windows 7
-
Windows Server 2008 or Windows Vista with Service Pack 1 (SP1)
-
Supported, but cannot edit policy settings or preference items that exist only in Windows Server 2012 R2, Windows Server 2012, Windows Server 2008 R2, Windows 8.1, or Windows 7
-
-
-
Windows Server 2008 or Windows Vista with SP1
-
Windows Server 2012, Windows Server 2008 R2, Windows 8, or Windows 7
-
Not supported
-
-
-
Windows Server 2008 or Windows Vista with SP1
-
Windows Server 2008 or Windows Vista with SP1
-
Supported, but cannot report or edit policy settings or preference items that exist only in Windows Server 2012 R2, Windows Server 2012, Windows Server 2008 R2, Windows 8.1, or Windows 7
-
-
-
-
-
-
-## AGPM 4.0 SP2
-
-
-If you are using computers that are running Windows Server 2012 R2 or Windows 8.1 to manage GPOs, you must use AGPM 4.0 SP2. You cannot install earlier versions of AGPM on computers that are running those operating systems.
-
-Table 1 lists the operating systems on which you can install AGPM 4.0 SP2, and the policy settings that you can manage by using AGPM 4.0 SP2.
-
-**Table 2: AGPM 4.0 SP2 supported operating systems and policy settings**
-
-
-
-
-
-
-
-
-
-
Supported configurations for the AGPM Server
-
Supported configurations for the AGPM Client
-
AGPM Support
-
-
-
-
-
Windows Server 2012 R2 or Windows 8.1
-
Windows Server 2012 R2 or Windows 8.1
-
Supported
-
-
-
Windows Server 2012 R2, Windows Server 2012, or Windows 8.1
-
Windows Server 2012 or Windows 8.1
-
Supported, but cannot edit policy settings or preference items that exist only in Windows 8.1
-
-
-
Windows Server 2008 R2 or Windows 7
-
Windows Server 2008 R2 or Windows 7
-
Supported, but cannot edit policy settings or preference items that exist only in Windows 8.1
-
-
-
Windows Server 2012, Windows Server 2008 R2, or Windows 7
-
Windows Server 2008 or Windows Vista with Service Pack 1 (SP1)
-
Supported, but cannot edit policy settings or preference items that exist only in Windows Server 2012 R2, Windows Server 2012, Windows Server 2008 R2, Windows 8.1, or Windows 7
-
-
-
Windows Server 2008 or Windows Vista with SP1
-
Windows Server 2012, Windows Server 2008 R2, or Windows 7
-
Not supported
-
-
-
Windows Server 2008 or Windows Vista with SP1
-
Windows Server 2008 or Windows Vista with SP1
-
Supported, but cannot report or edit policy settings or preference items that exist only in Windows Server 2012 R2, Windows Server 2012, Windows Server 2008 R2, Windows 8.1, or Windows 7
-
-
-
-
-
-
-## AGPM 4.0 SP1
-
-
-Table 2 lists the operating systems on which you can install AGPM 4.0 SP1, and the policy settings that you can manage by using AGPM 4.0 SP1.
-
-**Table 3: AGPM 4.0 SP1 supported operating systems and policy settings**
-
-
-
-
-
-
-
-
-
-
Supported configurations for the AGPM Server
-
Supported configurations for the AGPM Client
-
AGPM Support
-
-
-
-
-
Windows Server 2012
-
Windows Server 2012
-
Supported
-
-
-
Windows Server 2008 R2 or Windows 7
-
Windows Server 2008 R2 or Windows 7
-
Supported, but cannot edit policy settings or preference items that exist only in Windows 8.1
-
-
-
Windows Server 2012, Windows Server 2008 R2, or Windows 7
-
Windows Server 2008 or Windows Vista with SP1
-
Supported, but cannot edit policy settings or preference items that exist only in Windows Server 2008 R2, or Windows 7
-
-
-
Windows Server 2008 or Windows Vista with SP1
-
Windows Server 2012, Windows Server 2008 R2, or Windows 7
-
Supported
-
-
-
Windows Server 2008 or Windows Vista with SP1
-
Windows Server 2008 or Windows Vista with SP1
-
Supported, but cannot report or edit policy settings or preference items that exist only in Windows Server 2008 R2, or Windows 7
-
-
-
-
-
-
-## AGPM 4.0
-
-
-Table 3 lists the operating systems on which you can install AGPM 4.0, and the policy settings that you can manage by using AGPM 4.0.
-
-**Table 4: AGPM 4.0 supported operating systems and policy settings**
-
-
-
-
-
-
-
-
-
-
Supported operating systems for the AGPM Server
-
Supported operating systems for the AGPM Client
-
AGPM Support
-
-
-
-
-
Windows Server 2008 R2 or Windows 7
-
Windows Server 2008 R2 or Windows 7
-
Supported
-
-
-
Windows Server 2008 R2 or Windows 7
-
Windows Server 2008 or Windows Vista with SP1
-
Supported, but cannot edit policy settings or preference items that exist only in Windows Server 2008 R2 or Windows 7
-
-
-
Windows Server 2008 or Windows Vista with SP1
-
Windows Server 2008 R2 or Windows 7
-
Not supported
-
-
-
Windows Server 2008 or Windows Vista with SP1
-
Windows Server 2008 or Windows Vista with SP1
-
Supported, but cannot report or edit policy settings or preference items that exist only in Windows Server 2008 R2 or Windows 7
-
-
-
-
-
-
-## Versions of AGPM that precede AGPM 4.0
-
-
-Table 4 lists the operating systems on which you can install the versions of AGPM that precede AGPM 4.0. If an operating system is not listed, you cannot install AGPM on that operating system.
-
-**Table 5: Supported operating systems for versions of AGPM that precede AGPM 4.0**
-
-
-
-
-
-
-
-
-
Operating system
-
Version of AGPM that can be installed
-
-
-
-
-
Windows Server 2008
-
3.0
-
-
-
Windows Vista with SP1
-
3.0
-
-
-
Windows Vista with no service pack installed (32-bit)
-
2.5
-
-
-
Windows Server 2003 (32-bit)
-
2.5
-
-
-
-
-
-
-## How to Get MDOP Technologies
-
-
-AGPM 4.0 SP2 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](https://go.microsoft.com/fwlink/?LinkId=322049) (https://go.microsoft.com/fwlink/?LinkId=322049).
-
-## Related topics
-
-
-[Advanced Group Policy Management](index.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/common-secondary-tab-features.md b/mdop/agpm/common-secondary-tab-features.md
deleted file mode 100644
index b54804d0eb..0000000000
--- a/mdop/agpm/common-secondary-tab-features.md
+++ /dev/null
@@ -1,136 +0,0 @@
----
-title: Common Secondary Tab Features
-description: Common Secondary Tab Features
-author: dansimp
-ms.assetid: 44a15c28-944c-49c1-8534-115ce1c362ed
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Common Secondary Tab Features
-
-
-Each secondary tab has two sections—**Group Policy objects** and **Groups and Users**.
-
-## Group Policy objects section
-
-
-The **Group Policy objects** section displays a filtered list of Group Policy objects (GPOs) and identifies the following characteristics for each GPO:
-
-
-
-
-
-
-
-
-
GPO Characteristic
-
Description
-
-
-
-
-
Name
-
Name of the Group Policy object.
-
-
-
Computer (Comp.)
-
Automatically generated version of the Computer Configuration portion of the GPO.
-
-
-
User
-
Automatically generated version of the User Configuration portion of the GPO.
-
-
-
State
-
The state of the selected GPO:
-
Uncontrolled: Not managed by AGPM.
-
Checked In: Available for authorized Editors to check out for editing or for a Group Policy administrator to deploy.
-
Checked Out: Currently being edited. Unavailable for other Editors to check out until the Editor who checked it out or an AGPM Administrator checks it in.
-
Pending: Awaiting approval from a Group Policy administrator before being created, controlled, deployed, or deleted.
-
Deleted: Deleted from the archive, but still able to be restored.
-
Template: A static version of a GPO for use as a starting point when creating new GPOs.
-
Template (default): By default, this template is the starting point used when creating a new GPO.
-
-
-
GPO Status
-
The Computer Configuration and the User Configuration can be managed separately. The GPO Status indicates which portions of the GPO are enabled.
-
-
-
WMI Filter
-
Display any WMI filters that are applied to this GPO. WMI filters are managed under the WMI Filters node for the domain in the console tree of the GPMC.
-
-
-
Modified
-
For a controlled GPO, the most recent date when it was checked in after being modified or checked out to be modified. For an uncontrolled GPO, the date when it was last modified.
-
-
-
Owner
-
The Editor who checked in or the Approver who deployed the selected GPO.
-
-
-
-
-
-
-## Groups and Users section
-
-
-When a GPO is selected, the **Groups and Users** section displays a list of the groups and users with access to that GPO. The allowed permissions and inheritance are displayed for each group or user. An AGPM Administrator can configure permissions using either standard AGPM roles (Editor, Approver, and Reviewer) or a customized combination of permissions.
-
-
-
-
-
-
-
-
-
Button
-
Effect
-
-
-
-
-
Add
-
Add a new entry to the security descriptor. Any user or group in Active Directory can be added.
-
-
-
Remove
-
Remove the selected entry from the Access Control List.
-
-
-
Properties
-
Display the properties for the selected object. The properties page is the same one displayed for an object in Active Directory Users and Computers.
-
-
-
Advanced
-
Open the Access Control List Editor.
-
-
-
-
-
-
-### Additional considerations
-
-- For information about roles and permissions related to specific tasks, see the tasks under [Performing AGPM Administrator Tasks](performing-agpm-administrator-tasks.md), [Performing Editor Tasks](performing-editor-tasks.md), [Performing Approver Tasks](performing-approver-tasks.md), and [Performing Reviewer Tasks](performing-reviewer-tasks.md).
-
-### Additional references
-
-- [Contents Tab](contents-tab.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/configure-agpm-server-connections-agpm30ops.md b/mdop/agpm/configure-agpm-server-connections-agpm30ops.md
deleted file mode 100644
index 01c078c958..0000000000
--- a/mdop/agpm/configure-agpm-server-connections-agpm30ops.md
+++ /dev/null
@@ -1,110 +0,0 @@
----
-title: Configure AGPM Server Connections
-description: Configure AGPM Server Connections
-author: dansimp
-ms.assetid: 6062b77b-2fd7-442c-ad1b-6f14419ebd5f
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Configure AGPM Server Connections
-
-
-All versions of each controlled Group Policy Object (GPO) are stored in a central archive so that Group Policy administrators can view and modify GPOs offline without immediately impacting the deployed version of each GPO.
-
-A user account with the AGPM Administrator (Full Control) role, the user account of the Approver who created the GPO used in these procedures, or a user account with the necessary permissions in Advanced Group Policy Management (AGPM) is required to complete these procedures for centrally configuring archive locations for all Group Policy administrators. Review the details in "Additional considerations" in this topic.
-
-## Configuring AGPM Server connections
-
-
-As an AGPM Administrator, you can ensure that all Group Policy administrators connect to the same AGPM Server by centrally configuring the associated setting. If your environment requires separate AGPM Servers for some or all domains, configure those additional AGPM Servers as exceptions to the default. If you do not centrally configure AGPM Server connections, each Group Policy administrator must manually configure the AGPM Server to be displayed for each domain.
-
-- [Configure an AGPM Server connection for all Group Policy administrators](#bkmk-defaultarchiveloc)
-
-- [Configure additional AGPM Server connections for all Group Policy administrators](#bkmk-additionalarchiveloc)
-
-- [Manually configure an AGPM Server connection for your account](#bkmk-manuallyconfigurearchiveloc)
-
-###
-
-**To configure an AGPM Server connection for all Group Policy administrators**
-
-1. In the **Group Policy Management Console** tree, edit a GPO that is applied to all Group Policy administrators. (For more information, see [Editing a GPO](editing-a-gpo-agpm30ops.md).)
-
-2. In the **Group Policy Management Editor** window, click **User Configuration**, **Policies**, **Administrative Templates**, **Windows Components**, and **AGPM**.
-
-3. In the details pane, double-click **AGPM: Specify default AGPM Server (all domains)**.
-
-4. In the **Properties** window, select the **Enabled** check box, and type the fully-qualified computer name and port (for example, server.contoso.com:4600).
-
-5. Click **OK**. Unless you want to configure additional AGPM Server connections, close the **Group Policy Management Editor** window and deploy the GPO. (For more information, see [Deploy a GPO](deploy-a-gpo-agpm30ops.md).) When Group Policy is updated, the AGPM Server connection is configured for all Group Policy administrators.
-
-###
-
-**To configure additional AGPM Server connections for all Group Policy administrators**
-
-1. If no AGPM Server connection has been configured, follow the preceding procedure to configure a default AGPM Server for all domains.
-
-2. To configure separate AGPM Servers for some or all domains (overriding the default AGPM Server), in the **Group Policy Management Console** tree, edit a GPO that is applied to all Group Policy administrators. (For more information, see [Editing a GPO](editing-a-gpo-agpm30ops.md).)
-
-3. In the **Group Policy Management Editor** window, click **User Configuration**, **Policies**, **Administrative Templates**, **Windows Components**, and then **AGPM**.
-
-4. In the details pane, double-click **AGPM: Specify AGPM Servers**.
-
-5. In the **Properties** window, select the **Enabled** check box, and click **Show**.
-
-6. In the **Show Contents** window:
-
- 1. Click **Add**.
-
- 2. For **Value Name**, type the domain name (for example, server1.contoso.com).
-
- 3. For **Value**, type the AGPM Server name and port to use for this domain (for example, server2.contoso.com:4600), and then click **OK**. (By default, the AGPM Service listens on port 4600. To use a different port, see [Modify the AGPM Service](modify-the-agpm-service-agpm30ops.md).)
-
- 4. Repeat for each domain not using the default AGPM Server.
-
-7. Click **OK** to close the **Show Contents** and **Properties** windows.
-
-8. Close the **Group Policy Management Editor** window. (For more information, see [Deploy a GPO](deploy-a-gpo-agpm30ops.md).) When Group Policy is updated, the new AGPM Server connections are configured for all Group Policy administrators.
-
-###
-
-If you have centrally configured the AGPM Server connection, the option to manually configure it is unavailable for all Group Policy administrators.
-
-**To manually configure which AGPM Server to display for your account**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. In the details pane, click the **AGPM Server** tab.
-
-3. Enter the fully-qualified computer name for the AGPM Server that manages the archive used for this domain (for example, server.contoso.com) and the port on which the AGPM Service listens (by default, port 4600).
-
-4. Click **Apply**, then click **Yes** to confirm.
-
-### Additional considerations
-
-- You must be able to edit and deploy a GPO to perform the procedures for centrally configuring AGPM Server connections for all Group Policy administrators. See [Editing a GPO](editing-a-gpo-agpm30ops.md) and [Deploy a GPO](deploy-a-gpo-agpm30ops.md) for additional detail.
-
-- The selected AGPM Server determines which GPOs are displayed on the **Contents** tab and to what location the **Domain Delegation** tab settings are applied. If not centrally managed through the Administrative template, each Group Policy administrator must configure this setting to point to the AGPM Server for the domain.
-
-- Membership in the Group Policy Creator Owners group should be restricted, so it is not used to circumvent AGPM management of access to GPOs. (In the **Group Policy Management Console**, click **Group Policy Objects** in the forest and domain in which you want to manage GPOs, click **Delegation**, and then configure the settings to meet the needs of your organization.)
-
-### Additional references
-
-- [Configuring Advanced Group Policy Management](configuring-advanced-group-policy-management.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/configure-agpm-server-connections-agpm40.md b/mdop/agpm/configure-agpm-server-connections-agpm40.md
deleted file mode 100644
index c41c27ec1a..0000000000
--- a/mdop/agpm/configure-agpm-server-connections-agpm40.md
+++ /dev/null
@@ -1,110 +0,0 @@
----
-title: Configure AGPM Server Connections
-description: Configure AGPM Server Connections
-author: dansimp
-ms.assetid: bbbb15e8-35e7-403c-b695-7a6ebeb87839
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Configure AGPM Server Connections
-
-
-All versions of each controlled Group Policy Object (GPO) are stored in a central archive so that Group Policy administrators can view and modify GPOs offline without immediately impacting the deployed version of each GPO.
-
-A user account with the AGPM Administrator (Full Control) role, the user account of the Approver who created the GPO used in these procedures, or a user account with the necessary permissions in Advanced Group Policy Management (AGPM) is required to complete these procedures for centrally configuring archive locations for all Group Policy administrators. Review the details in "Additional considerations" in this topic.
-
-## Configuring AGPM Server connections
-
-
-As an AGPM Administrator, you can ensure that all Group Policy administrators connect to the same AGPM Server by centrally configuring the associated setting. If your environment requires separate AGPM Servers for some or all domains, configure those additional AGPM Servers as exceptions to the default. If you do not centrally configure AGPM Server connections, each Group Policy administrator must manually configure the AGPM Server to be displayed for each domain.
-
-- [Configure an AGPM Server connection for all Group Policy administrators](#bkmk-defaultarchiveloc)
-
-- [Configure additional AGPM Server connections for all Group Policy administrators](#bkmk-additionalarchiveloc)
-
-- [Manually configure an AGPM Server connection for your account](#bkmk-manuallyconfigurearchiveloc)
-
-###
-
-**To configure an AGPM Server connection for all Group Policy administrators**
-
-1. In the **Group Policy Management Console** tree, edit a GPO that is applied to all Group Policy administrators. (For more information, see [Editing a GPO](editing-a-gpo-agpm40.md).)
-
-2. In the **Group Policy Management Editor** window, click **User Configuration**, **Policies**, **Administrative Templates**, **Windows Components**, and **AGPM**.
-
-3. In the details pane, double-click **AGPM: Specify default AGPM Server (all domains)**.
-
-4. In the **Properties** window, select the **Enabled** check box, and type the fully-qualified computer name and port (for example, server.contoso.com:4600).
-
-5. Click **OK**. Unless you want to configure additional AGPM Server connections, close the **Group Policy Management Editor** window and deploy the GPO. (For more information, see [Deploy a GPO](deploy-a-gpo-agpm40.md).) When Group Policy is updated, the AGPM Server connection is configured for all Group Policy administrators.
-
-###
-
-**To configure additional AGPM Server connections for all Group Policy administrators**
-
-1. If no AGPM Server connection has been configured, follow the preceding procedure to configure a default AGPM Server for all domains.
-
-2. To configure separate AGPM Servers for some or all domains (overriding the default AGPM Server), in the **Group Policy Management Console** tree, edit a GPO that is applied to all Group Policy administrators. (For more information, see [Editing a GPO](editing-a-gpo-agpm40.md).)
-
-3. In the **Group Policy Management Editor** window, click **User Configuration**, **Policies**, **Administrative Templates**, **Windows Components**, and then **AGPM**.
-
-4. In the details pane, double-click **AGPM: Specify AGPM Servers**.
-
-5. In the **Properties** window, select the **Enabled** check box, and click **Show**.
-
-6. In the **Show Contents** window:
-
- 1. Click **Add**.
-
- 2. For **Value Name**, type the domain name (for example, server1.contoso.com).
-
- 3. For **Value**, type the AGPM Server name and port to use for this domain (for example, server2.contoso.com:4600), and then click **OK**. (By default, the AGPM Service listens on port 4600. To use a different port, see [Modify the AGPM Service](modify-the-agpm-service-agpm40.md).)
-
- 4. Repeat for each domain not using the default AGPM Server.
-
-7. Click **OK** to close the **Show Contents** and **Properties** windows.
-
-8. Close the **Group Policy Management Editor** window. (For more information, see [Deploy a GPO](deploy-a-gpo-agpm40.md).) When Group Policy is updated, the new AGPM Server connections are configured for all Group Policy administrators.
-
-###
-
-If you have centrally configured the AGPM Server connection, the option to manually configure it is unavailable for all Group Policy administrators.
-
-**To manually configure which AGPM Server to display for your account**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. In the details pane, click the **AGPM Server** tab.
-
-3. Enter the fully-qualified computer name for the AGPM Server that manages the archive used for this domain (for example, server.contoso.com) and the port on which the AGPM Service listens (by default, port 4600).
-
-4. Click **Apply**, then click **Yes** to confirm.
-
-### Additional considerations
-
-- You must be able to edit and deploy a GPO to perform the procedures for centrally configuring AGPM Server connections for all Group Policy administrators. See [Editing a GPO](editing-a-gpo-agpm40.md) and [Deploy a GPO](deploy-a-gpo-agpm40.md) for additional detail.
-
-- The selected AGPM Server determines which GPOs are displayed on the **Contents** tab and to what location the **Domain Delegation** tab settings are applied. If not centrally managed through the Administrative template, each Group Policy administrator must configure this setting to point to the AGPM Server for the domain.
-
-- Membership in the Group Policy Creator Owners group should be restricted, so it is not used to circumvent AGPM management of access to GPOs. (In the **Group Policy Management Console**, click **Group Policy Objects** in the forest and domain in which you want to manage GPOs, click **Delegation**, and then configure the settings to meet the needs of your organization.)
-
-### Additional references
-
-- [Configuring Advanced Group Policy Management](configuring-advanced-group-policy-management-agpm40.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/configure-an-agpm-server-connection-agpm40.md b/mdop/agpm/configure-an-agpm-server-connection-agpm40.md
deleted file mode 100644
index 3fec7b9300..0000000000
--- a/mdop/agpm/configure-an-agpm-server-connection-agpm40.md
+++ /dev/null
@@ -1,47 +0,0 @@
----
-title: Configure an AGPM Server Connection
-description: Configure an AGPM Server Connection
-author: dansimp
-ms.assetid: 409cbbcf-3b0e-459d-9bd2-75cb7b9430b0
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Configure an AGPM Server Connection
-
-
-To ensure that you are connected to the correct central archive, review the configuration of the AGPM Server connection. If an AGPM Administrator (Full Control) has not configured an AGPM Server connection for you, then you must manually configure it.
-
-**To select an AGPM Server**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. In the details pane, click the **AGPM Server** tab:
-
- - If the options on the **AGPM Server** tab are unavailable, they have been centrally configured by an AGPM Administrator.
-
- - If the options on the **AGPM Server** tab are available, type the fully-qualified computer name for the AGPM Server (for example, server.contoso.com) and the port on which the AGPM Service listens (by default, port 4600). Click **Apply**, then click **Yes** to confirm.
-
-### Additional considerations
-
-- The AGPM Servers selected determine which GPOs are displayed on the **Contents** tab and to what location the **Domain Delegation** tab settings are applied. If not centrally managed through the Administrative template, each Group Policy administrator must configure this setting to point to the AGPM Server for the domain.
-
-### Additional references
-
-- [Performing Reviewer Tasks](performing-reviewer-tasks-agpm40.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/configure-an-agpm-server-connection-reviewer-agpm30ops.md b/mdop/agpm/configure-an-agpm-server-connection-reviewer-agpm30ops.md
deleted file mode 100644
index 196bbbed79..0000000000
--- a/mdop/agpm/configure-an-agpm-server-connection-reviewer-agpm30ops.md
+++ /dev/null
@@ -1,51 +0,0 @@
----
-title: Configure an AGPM Server Connection
-description: Configure an AGPM Server Connection
-author: dansimp
-ms.assetid: ae78dc74-111d-4509-b0a6-e8b8b451c22a
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Configure an AGPM Server Connection
-
-
-To ensure that you are connected to the correct central archive, review the configuration of the AGPM Server connection. If an AGPM Administrator (Full Control) has not configured an AGPM Server connection for you, then you must manually configure it.
-
-**To select an AGPM Server**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. In the details pane, click the **AGPM Server** tab:
-
- - If the options on the **AGPM Server** tab are unavailable, they have been centrally configured by an AGPM Administrator.
-
- - If the options on the **AGPM Server** tab are available, type the fully-qualified computer name for the AGPM Server (for example, server.contoso.com) and the port on which the AGPM Service listens (by default, port 4600). Click **Apply**, then click **Yes** to confirm.
-
-### Additional considerations
-
-- The AGPM Servers selected determine which GPOs are displayed on the **Contents** tab and to what location the **Domain Delegation** tab settings are applied. If not centrally managed through the Administrative template, each Group Policy administrator must configure this setting to point to the AGPM Server for the domain.
-
-### Additional references
-
-- [Performing Editor Tasks](performing-editor-tasks-agpm30ops.md)
-
-- [Performing Approver Tasks](performing-approver-tasks-agpm30ops.md)
-
-- [Performing Reviewer Tasks](performing-reviewer-tasks-agpm30ops.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/configure-e-mail-notification-agpm30ops.md b/mdop/agpm/configure-e-mail-notification-agpm30ops.md
deleted file mode 100644
index 7a4f5887a8..0000000000
--- a/mdop/agpm/configure-e-mail-notification-agpm30ops.md
+++ /dev/null
@@ -1,59 +0,0 @@
----
-title: Configure E-Mail Notification
-description: Configure E-Mail Notification
-author: dansimp
-ms.assetid: b32ce395-d1b9-4c5b-b765-97cdbf455f9e
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Configure E-Mail Notification
-
-
-When an Editor or a Reviewer attempts to create, deploy, or delete a Group Policy Object (GPO), a request for this action is sent to a designated e-mail address or addresses so that an Approver can evaluate the request and implement or deny it. You determine the e-mail address or addresses to which notifications are sent, as well as the alias from which notifications are sent.
-
-A user account with the AGPM Administrator (Full Control) role or necessary permissions in Advanced Group Policy Management (AGPM) is required to complete this procedure. Review the details in "Additional considerations" in this topic.
-
-**To configure e-mail notification for AGPM**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. In the details pane, click the **Domain Delegation** tab.
-
-3. In the **From e-mail address** field, type the e-mail alias for AGPM from which notifications should be sent.
-
-4. In the **To e-mail address** field, type a comma-delimited list of e-mail addresses of Approvers who should receive requests for approval.
-
-5. In the **SMTP server** field, type a valid SMTP mail server.
-
-6. In the **User name** and **Password** fields, type the credentials of a user with access to the SMTP service.
-
-7. Click **Apply**.
-
-### Additional considerations
-
-- By default, you must be an AGPM Administrator (Full Control) to perform this procedure. Specifically, you must have **List Contents** and **Modify Options** permissions for the domain.
-
-- E-mail notification for AGPM is a domain-level setting. You can provide different Approver e-mail addresses or AGPM e-mail aliases on each domain's **Domain Delegation** tab, or use the same e-mail addresses throughout your environment.
-
-- By default, e-mail messages sent as a result of actions in Advanced Group Policy Management (AGPM) are not encrypted. However, you can configure e-mail security for AGPM using registry settings to specify whether to use Secure Sockets Layer (SSL) encryption and which SMTP port to use. For more information, see [Configure E-Mail Security for AGPM](configure-e-mail-security-for-agpm-agpm30ops.md)
-
-### Additional references
-
-- [Configuring Advanced Group Policy Management](configuring-advanced-group-policy-management.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/configure-e-mail-notification-agpm40.md b/mdop/agpm/configure-e-mail-notification-agpm40.md
deleted file mode 100644
index 19f24e340c..0000000000
--- a/mdop/agpm/configure-e-mail-notification-agpm40.md
+++ /dev/null
@@ -1,59 +0,0 @@
----
-title: Configure E-Mail Notification
-description: Configure E-Mail Notification
-author: dansimp
-ms.assetid: 06f19556-f296-4a80-86a4-4f446c992204
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Configure E-Mail Notification
-
-
-When an Editor or a Reviewer attempts to create, deploy, or delete a Group Policy Object (GPO), a request for this action is sent to a designated e-mail address or addresses so that an Approver can evaluate the request and implement or deny it. You determine the e-mail address or addresses to which notifications are sent, as well as the alias from which notifications are sent.
-
-A user account with the AGPM Administrator (Full Control) role or necessary permissions in Advanced Group Policy Management (AGPM) is required to complete this procedure. Review the details in "Additional considerations" in this topic.
-
-**To configure e-mail notification for AGPM**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. In the details pane, click the **Domain Delegation** tab.
-
-3. In the **From e-mail address** field, type the e-mail alias for AGPM from which notifications should be sent.
-
-4. In the **To e-mail address** field, type a comma-delimited list of e-mail addresses of Approvers who should receive requests for approval.
-
-5. In the **SMTP server** field, type a valid SMTP mail server.
-
-6. In the **User name** and **Password** fields, type the credentials of a user with access to the SMTP service.
-
-7. Click **Apply**.
-
-### Additional considerations
-
-- By default, you must be an AGPM Administrator (Full Control) to perform this procedure. Specifically, you must have **List Contents** and **Modify Options** permissions for the domain.
-
-- E-mail notification for AGPM is a domain-level setting. You can provide different Approver e-mail addresses or AGPM e-mail aliases on each domain's **Domain Delegation** tab, or use the same e-mail addresses throughout your environment.
-
-- By default, e-mail messages sent as a result of actions in Advanced Group Policy Management (AGPM) are not encrypted. However, you can configure e-mail security for AGPM using registry settings to specify whether to use Secure Sockets Layer (SSL) encryption and which SMTP port to use. For more information, see [Configure E-Mail Security for AGPM](configure-e-mail-security-for-agpm-agpm40.md).
-
-### Additional references
-
-- [Configuring Advanced Group Policy Management](configuring-advanced-group-policy-management-agpm40.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/configure-e-mail-notification.md b/mdop/agpm/configure-e-mail-notification.md
deleted file mode 100644
index 7bda0b1a9c..0000000000
--- a/mdop/agpm/configure-e-mail-notification.md
+++ /dev/null
@@ -1,57 +0,0 @@
----
-title: Configure E-Mail Notification
-description: Configure E-Mail Notification
-author: dansimp
-ms.assetid: 6e152de0-4376-4963-8d1a-3e7f5866d30f
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Configure E-Mail Notification
-
-
-When an Editor or a Reviewer attempts to create, deploy, or delete a Group Policy object (GPO), a request for this action is sent to a designated e-mail address or addresses so that an Approver can evaluate the request and implement or deny it. You determine the e-mail address or addresses to which notifications are sent, as well as the alias from which notifications are sent.
-
-A user account with the AGPM Administrator (Full Control) role or necessary permissions in Advanced Group Policy Management is required to complete this procedure. Review the details in "Additional considerations" in this topic.
-
-**To configure e-mail notification for AGPM**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. In the details pane, click the **Domain Delegation** tab.
-
-3. In the **From** field, type the e-mail alias for AGPM from which notifications should be sent.
-
-4. In the **To** field, type a comma-delimited list of e-mail addresses of Approvers who should receive requests for approval.
-
-5. In the **SMTP server** field, type a valid SMTP mail server.
-
-6. In the **User name** and **Password** fields, type the credentials of a user with access to the SMTP service.
-
-7. Click **Apply**.
-
-### Additional considerations
-
-- By default, you must be an AGPM Administrator (Full Control) to perform this procedure. Specifically, you must have **List Contents** and **Modify Options** permissions for the domain.
-
-- E-mail notification for AGPM is a domain-level setting. You can provide different Approver e-mail addresses or AGPM e-mail aliases on each domain's **Domain Delegation** tab, or use the same e-mail addresses throughout your environment.
-
-### Additional references
-
-- [Performing AGPM Administrator Tasks](performing-agpm-administrator-tasks.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/configure-e-mail-security-for-agpm-agpm30ops.md b/mdop/agpm/configure-e-mail-security-for-agpm-agpm30ops.md
deleted file mode 100644
index ed184df8d5..0000000000
--- a/mdop/agpm/configure-e-mail-security-for-agpm-agpm30ops.md
+++ /dev/null
@@ -1,92 +0,0 @@
----
-title: Configure E-Mail Security for AGPM
-description: Configure E-Mail Security for AGPM
-author: dansimp
-ms.assetid: 4850ed8e-a1c6-43f0-95c5-853aa66a94ae
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Configure E-Mail Security for AGPM
-
-
-By default, e-mail notifications sent because of actions in Advanced Group Policy Management (AGPM) are not encrypted and are sent through SMTP port 25. However, you can configure e-mail security for AGPM by using registry settings to specify whether to use Secure Sockets Layer (SSL) encryption and which SMTP port to use.
-
-By encrypting AGPM e-mail notifications, you can better protect those that could reveal sensitive information about your organization’s security. Encrypting e-mail notifications is recommended when they are being relayed through remote mail servers, and may be required by some compliance regulations.
-
-**Caution**
-Incorrectly editing the registry may severely damage your system. Before making changes to the registry, you should back up any valued data on the computer.
-
-
-
-A user account that has the AGPM Administrator (Full Control) role, the user account of the Approver who created the Group Policy Object (GPO) used in these procedures, or a user account that has the necessary permissions in AGPM is required to complete these procedures. Review the details in "Additional considerations" in this topic.
-
-**To configure e-mail security for AGPM by using Group Policy preferences**
-
-1. In the **Group Policy Management Console** tree, edit a GPO that is applied to all AGPM Servers for which you want to configure e-mail security. (For more information, see [Editing a GPO](editing-a-gpo-agpm30ops.md).)
-
-2. In the **Group Policy Management Editor** window, expand the **Computer Configuration**, **Preferences**, **Windows Settings**, and **Registry** folders.
-
-3. In the console tree, right-click **Registry**, point to **New**, click **Collection Item**, and type **AGPM e-mail security**.
-
-4. Create a Registry preference item to turn on encryption:
-
- 1. In the console tree, right-click **AGPM e-mail security**, point to **New**, and then click **Registry Item**.
-
- 2. In the **New Registry Properties** dialog box, select the **Update** action.
-
- 3. For **Hive**, select **HKEY\_LOCAL\_MACHINE**.
-
- 4. For **Key Path**, type **SOFTWARE\\Microsoft\\AGPM**.
-
- 5. For **Value name**, type **EncryptSmtp**.
-
- 6. For **Value type**, select **REG\_DWORD**.
-
- 7. For **Base**, select **Decimal**, and for **Value data**, type **1** to use SSL encryption, or **0** to let e-mail to be sent without encryption. By default, e-mail is sent without encryption.
-
- 8. Click **OK**.
-
-5. Create a Registry preference item to specify the SMTP port:
-
- 1. In the console tree, right-click **AGPM E-mail security**, point to **New**, and then click **Registry Item**.
-
- 2. In the **New Registry Properties** dialog box, select the **Update** action.
-
- 3. For **Hive**, select **HKEY\_LOCAL\_MACHINE**.
-
- 4. For **Key Path** dialog box, type **SOFTWARE\\Microsoft\\AGPM**.
-
- 5. For **Value name**, type **SmtpPort**.
-
- 6. For **Value type**, select **REG\_DWORD**.
-
- 7. For **Base**, select **Decimal**, and for **Value data**, type a port number for the SMTP port. By default, the SMTP port is port 25 if encryption is not enabled or port 587 if SSL encryption is enabled.
-
- 8. Click **OK**.
-
-6. Close the **Group Policy Management Editor** window, and then check in and deploy the GPO. For more information, see [Deploy a GPO](deploy-a-gpo-agpm30ops.md).
-
-### Additional considerations
-
-- You must be able to edit and deploy a GPO to configure registry settings by using Group Policy Preferences. See [Editing a GPO](editing-a-gpo-agpm30ops.md) and [Deploy a GPO](deploy-a-gpo-agpm30ops.md) for additional detail.
-
-### Additional references
-
-- [Configuring Advanced Group Policy Management](configuring-advanced-group-policy-management.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/configure-e-mail-security-for-agpm-agpm40.md b/mdop/agpm/configure-e-mail-security-for-agpm-agpm40.md
deleted file mode 100644
index 6b62a3bc2a..0000000000
--- a/mdop/agpm/configure-e-mail-security-for-agpm-agpm40.md
+++ /dev/null
@@ -1,88 +0,0 @@
----
-title: Configure E-Mail Security for AGPM
-description: Configure E-Mail Security for AGPM
-author: dansimp
-ms.assetid: b9c48894-0a10-4d03-8027-50ed3b02485a
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Configure E-Mail Security for AGPM
-
-
-By default, e-mail notifications sent because of actions in Advanced Group Policy Management (AGPM) are not encrypted and are sent through SMTP port 25. However, you can configure e-mail security for AGPM by using registry settings to specify whether to use Secure Sockets Layer (SSL) encryption and which SMTP port to use.
-
-By encrypting AGPM e-mail notifications, you can better protect those that could reveal sensitive information about your organization’s security. Encrypting e-mail notifications is recommended when they are being relayed through remote mail servers, and may be required by some compliance regulations.
-
-**Caution**
-Incorrectly editing the registry may severely damage your system. Before making changes to the registry, you should back up any valued data on the computer.
-
-
-
-A user account that has the AGPM Administrator (Full Control) role, the user account of the Approver who created the Group Policy Object (GPO) used in these procedures, or a user account that has the necessary permissions in AGPM is required to complete these procedures. Review the details in "Additional considerations" in this topic.
-
-**To configure e-mail security for AGPM by using Group Policy preferences**
-
-1. In the **Group Policy Management Console** tree, edit a GPO that is applied to all AGPM Servers for which you want to configure e-mail security. (For more information, see [Editing a GPO](editing-a-gpo-agpm40.md).)
-
-2. In the **Group Policy Management Editor** window, expand the **Computer Configuration**, **Preferences**, **Windows Settings**, and **Registry** folders.
-
-3. In the console tree, right-click **Registry**, point to **New**, click **Collection Item**, and type **AGPM e-mail security**.
-
-4. Create a Registry preference item to turn on encryption:
-
- 1. In the console tree, right-click **AGPM e-mail security**, point to **New**, and then click **Registry Item**.
-
- 2. In the **New Registry Properties** dialog box, select the **Update** action.
-
- 3. For **Hive**, select **HKEY\_LOCAL\_MACHINE**.
-
- 4. For **Key Path**, type **SOFTWARE\\Microsoft\\AGPM**.
-
- 5. For **Value name**, type **EncryptSmtp**.
-
- 6. For **Value type**, select **REG\_DWORD**.
-
- 7. For **Base**, select **Decimal**, and for **Value data**, type **1** to use SSL encryption, or **0** to let e-mail to be sent without encryption. By default, e-mail is sent without encryption. Click **OK**.
-
-5. Create a Registry preference item to specify the SMTP port:
-
- 1. In the console tree, right-click **AGPM E-mail security**, point to **New**, and then click **Registry Item**.
-
- 2. In the **New Registry Properties** dialog box, select the **Update** action.
-
- 3. For **Hive**, select **HKEY\_LOCAL\_MACHINE**.
-
- 4. For **Key Path** dialog box, type **SOFTWARE\\Microsoft\\AGPM**.
-
- 5. For **Value name**, type **SmtpPort**.
-
- 6. For **Value type**, select **REG\_DWORD**.
-
- 7. For **Base**, select **Decimal**, and for **Value data**, type a port number for the SMTP port. By default, the SMTP port is port 25 if encryption is not enabled or port 587 if SSL encryption is enabled. Click **OK**.
-
-6. Close the **Group Policy Management Editor** window, and then check in and deploy the GPO. For more information, see [Deploy a GPO](deploy-a-gpo-agpm40.md).
-
-### Additional considerations
-
-- You must be able to edit and deploy a GPO to configure registry settings by using Group Policy Preferences. See [Editing a GPO](editing-a-gpo-agpm40.md) and [Deploy a GPO](deploy-a-gpo-agpm40.md) for additional detail.
-
-### Additional references
-
-- [Configuring Advanced Group Policy Management](configuring-advanced-group-policy-management-agpm40.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/configure-logging-and-tracing-agpm30ops.md b/mdop/agpm/configure-logging-and-tracing-agpm30ops.md
deleted file mode 100644
index dd666e4815..0000000000
--- a/mdop/agpm/configure-logging-and-tracing-agpm30ops.md
+++ /dev/null
@@ -1,59 +0,0 @@
----
-title: Configure Logging and Tracing
-description: Configure Logging and Tracing
-author: dansimp
-ms.assetid: 4f89552f-e949-48b0-9325-23746034eaa4
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Configure Logging and Tracing
-
-
-You can centrally configure optional logging and tracing using Administrative templates. This may be helpful when diagnosing any problems related to Advanced Group Policy Management (AGPM).
-
-A user account with the AGPM Administrator (Full Control) role, the user account of the Approver who created the Group Policy Object (GPO) used in these procedures, or a user account with the necessary permissions in AGPM is required to complete these procedures. Additionally, a user account with access to the AGPM Server is required to initiate logging on the AGPM Server. Review the details in "Additional considerations" in this topic.
-
-**To configure logging and tracing for AGPM**
-
-1. In the **Group Policy Management Console** tree, edit a GPO that is applied to all Group Policy administrators for which you want to turn on logging and tracing. (For more information, see [Editing a GPO](editing-a-gpo-agpm30ops.md).)
-
-2. In the **Group Policy Management Editor** window, click **Computer Configuration**, **Policies**, **Administrative Templates**, **Windows Components**, and **AGPM**.
-
-3. In the details pane, double-click **AGPM: Configure logging**.
-
-4. In the **Properties** window, click **Enabled**, and configure the level of detail to record in the logs.
-
-5. Click **OK**.
-
-6. Close the **Group Policy Management Editor** window. (For more information, see [Deploy a GPO](deploy-a-gpo-agpm30ops.md).) After Group Policy is updated, you must restart the AGPM Service to start, modify, or stop logging on the AGPM Server. Group Policy administrators must close and restart the GPMC to start, modify, or stop logging on their computers.
-
- **Trace file locations**:
-
- - Client: %LocalAppData%\\Microsoft\\AGPM\\agpm.log
-
- - Server: %ProgramData%\\Microsoft\\AGPM\\agpmserv.log
-
-### Additional considerations
-
-- You must be able to edit and deploy a GPO to configure AGPM logging and tracing. See [Editing a GPO](editing-a-gpo-agpm30ops.md) and [Deploy a GPO](deploy-a-gpo-agpm30ops.md) for additional detail.
-
-### Additional references
-
-- [Configuring Advanced Group Policy Management](configuring-advanced-group-policy-management.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/configure-logging-and-tracing-agpm40.md b/mdop/agpm/configure-logging-and-tracing-agpm40.md
deleted file mode 100644
index c1e150c7bd..0000000000
--- a/mdop/agpm/configure-logging-and-tracing-agpm40.md
+++ /dev/null
@@ -1,59 +0,0 @@
----
-title: Configure Logging and Tracing
-description: Configure Logging and Tracing
-author: dansimp
-ms.assetid: 2418cb6a-7189-4080-8fe2-9c8d47dec62c
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Configure Logging and Tracing
-
-
-You can centrally configure optional logging and tracing using Administrative templates. This may be helpful when diagnosing any problems related to Advanced Group Policy Management (AGPM).
-
-A user account with the AGPM Administrator (Full Control) role, the user account of the Approver who created the Group Policy Object (GPO) used in these procedures, or a user account with the necessary permissions in AGPM is required to complete these procedures. Additionally, a user account with access to the AGPM Server is required to initiate logging on the AGPM Server. Review the details in "Additional considerations" in this topic.
-
-**To configure logging and tracing for AGPM**
-
-1. In the **Group Policy Management Console** tree, edit a GPO that is applied to all Group Policy administrators for which you want to turn on logging and tracing. (For more information, see [Editing a GPO](editing-a-gpo-agpm40.md).)
-
-2. In the **Group Policy Management Editor** window, click **Computer Configuration**, **Policies**, **Administrative Templates**, **Windows Components**, and **AGPM**.
-
-3. In the details pane, double-click **AGPM: Configure logging**.
-
-4. In the **Properties** window, click **Enabled**, and configure the level of detail to record in the logs.
-
-5. Click **OK**.
-
-6. Close the **Group Policy Management Editor** window. (For more information, see [Deploy a GPO](deploy-a-gpo-agpm40.md).) After Group Policy is updated, you must restart the AGPM Service to start, modify, or stop logging on the AGPM Server. Group Policy administrators must close and restart the GPMC to start, modify, or stop logging on their computers.
-
- **Trace file locations**:
-
- - Client: %LocalAppData%\\Microsoft\\AGPM\\agpm.log
-
- - Server: %ProgramData%\\Microsoft\\AGPM\\agpmserv.log
-
-### Additional considerations
-
-- You must be able to edit and deploy a GPO to configure AGPM logging and tracing. See [Editing a GPO](editing-a-gpo-agpm40.md) and [Deploy a GPO](deploy-a-gpo-agpm40.md) for additional detail.
-
-### Additional references
-
-- [Configuring Advanced Group Policy Management](configuring-advanced-group-policy-management-agpm40.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/configure-logging-and-tracing.md b/mdop/agpm/configure-logging-and-tracing.md
deleted file mode 100644
index 8f9b6b9e07..0000000000
--- a/mdop/agpm/configure-logging-and-tracing.md
+++ /dev/null
@@ -1,67 +0,0 @@
----
-title: Configure Logging and Tracing
-description: Configure Logging and Tracing
-author: dansimp
-ms.assetid: 419231f9-e9db-4f91-a7cf-a0a73db25256
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Configure Logging and Tracing
-
-
-You can centrally configure optional logging and tracing for Advanced Group Policy Management (AGPM) using Administrative templates.
-
-A user account with the AGPM Administrator (Full Control) role, the user account of the Approver who created the GPO used in these procedures, or a user account with the necessary permissions in Advanced Group Policy Management is required to complete these procedures. Additionally, a user account with access to the AGPM Server is required to initiate logging on the AGPM Server. Review the details in "Additional considerations" in this topic.
-
-**To configure logging and tracing for AGPM**
-
-1. In the **Group Policy Management Console** tree, edit a GPO that is applied to all Group Policy administrators for which you want to turn on logging and tracing. (For more information, see [Editing a GPO](editing-a-gpo.md).)
-
-2. In the **Group Policy Object Editor**, click **Computer Configuration**, **Administrative Templates**, and **Windows Components**.
-
-3. If **AGPM** is not listed under **Windows Components**:
-
- 1. Right-click **Administrative Templates** and click **Add/Remove Templates**.
-
- 2. Click **Add**, select **agpm.admx** or **agpm.adm**, click **Open**, and then click **Close**.
-
-4. Under **Windows Components**, double-click **AGPM**.
-
-5. In the details pane, double-click **AGPM Logging**.
-
-6. In the **AGPM Logging Properties** window, click **Enabled**, and configure the level of detail to record in the logs.
-
-7. Click **OK**.
-
-8. Close the **Group Policy Object Editor**. (For more information, see [Deploy a GPO](deploy-a-gpo.md).) After Group Policy is updated, you must restart the AGPM Service to begin logging on the AGPM Server. Group Policy administrators must close and restart the GPMC to begin logging on their computers.
-
- **Trace file locations**:
-
- - Client: %LocalAppData%\\Microsoft\\AGPM\\agpm.log
-
- - Server: %ProgramData%\\Microsoft\\AGPM\\agpmserv.log
-
-### Additional considerations
-
-- You must be able to edit and deploy a GPO to configure AGPM logging and tracing. See [Editing a GPO](editing-a-gpo.md) and [Deploy a GPO](deploy-a-gpo.md) for additional detail.
-
-### Additional references
-
-- [Performing AGPM Administrator Tasks](performing-agpm-administrator-tasks.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/configure-the-agpm-server-connection-reviewer.md b/mdop/agpm/configure-the-agpm-server-connection-reviewer.md
deleted file mode 100644
index ba9b7f9381..0000000000
--- a/mdop/agpm/configure-the-agpm-server-connection-reviewer.md
+++ /dev/null
@@ -1,51 +0,0 @@
----
-title: Configure the AGPM Server Connection
-description: Configure the AGPM Server Connection
-author: dansimp
-ms.assetid: 74e8f348-a8ed-4d69-a8e0-9c974aaeca2d
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Configure the AGPM Server Connection
-
-
-To ensure that you are connected to the correct central archive, review the configuration of the AGPM Server connection. If an AGPM Administrator (Full Control) has not configured the AGPM Server connection for you, then you must manually configure it.
-
-**To select an AGPM Server**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. In the details pane, click the **AGPM Server** tab:
-
- - If the options on the **AGPM Server** tab are unavailable, they have been centrally configured by an AGPM Administrator.
-
- - If the options on the **AGPM Server** tab are available, type the fully-qualified computer name for the AGPM Server (for example, server.contoso.com) and the port on which the AGPM Service listens (by default, port 4600). Click **Apply**, then click **Yes** to confirm.
-
-### Additional considerations
-
-- The AGPM Servers selected determine which GPOs are displayed on the **Contents** tab and to what location the **Domain Delegation** tab settings are applied. If not centrally managed through the Administrative template, each Group Policy administrator must configure this setting to point to the AGPM Server for the domain.
-
-### Additional references
-
-- [Performing Editor Tasks](performing-editor-tasks.md)
-
-- [Performing Approver Tasks](performing-approver-tasks.md)
-
-- [Performing Reviewer Tasks](performing-reviewer-tasks.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/configure-the-agpm-server-connection.md b/mdop/agpm/configure-the-agpm-server-connection.md
deleted file mode 100644
index a6322bd687..0000000000
--- a/mdop/agpm/configure-the-agpm-server-connection.md
+++ /dev/null
@@ -1,118 +0,0 @@
----
-title: Configure the AGPM Server Connection
-description: Configure the AGPM Server Connection
-author: dansimp
-ms.assetid: 9a42b5bc-41be-44ef-a6e2-6f56e2cf1996
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Configure the AGPM Server Connection
-
-
-Advanced Group Policy Management (AGPM) stores all versions of each controlled Group Policy object (GPO) in a central archive, so Group Policy administrators can view and modify GPOs offline without immediately impacting the deployed version of each GPO.
-
-A user account with the AGPM Administrator (Full Control) role, the user account of the Approver who created the GPO used in these procedures, or a user account with the necessary permissions in Advanced Group Policy Management is required to complete these procedures for centrally configuring archive locations for all Group Policy administrators. Review the details in "Additional considerations" in this topic.
-
-## Configuring the AGPM Server connection
-
-
-As an AGPM Administrator (Full Control), you can ensure that all Group Policy administrators connect to the same AGPM Server by centrally configuring the setting. If your environment requires separate AGPM Servers for some or all domains, configure those additional AGPM Servers as exceptions to the default. If you do not centrally configure AGPM Server connections, each Group Policy administrator must manually configure the AGPM Server to be displayed for each domain.
-
-- [Configure an AGPM Server for all Group Policy administrators](#bkmk-defaultarchiveloc)
-
-- [Configure additional AGPM Servers for all Group Policy administrators](#bkmk-additionalarchiveloc)
-
-- [Manually configure an AGPM Server for your account](#bkmk-manuallyconfigurearchiveloc)
-
-###
-
-**To configure an AGPM Server for all Group Policy administrators**
-
-1. In the **Group Policy Management Console** tree, edit a GPO that is applied to all Group Policy administrators. (For more information, see [Editing a GPO](editing-a-gpo.md).)
-
-2. In the **Group Policy Object Editor**, click **User Configuration**, **Administrative Templates**, and **Windows Components**.
-
-3. If **AGPM** is not listed under **Windows Components**:
-
- 1. Right-click **Administrative Templates** and click **Add/Remove Templates**.
-
- 2. Click **Add**, select **agpm.admx** or **agpm.adm**, click **Open**, and then click **Close**.
-
-4. Under **Windows Components**, double-click **AGPM**.
-
-5. In the details pane, double-click **AGPM Server (all domains)**.
-
-6. In the **AGPM Server (all domains) Properties** window, select the **Enabled** check box, and type the fully-qualified computer name and port (for example, server.contoso.com:4600).
-
-7. Click **OK**. Unless you want to configure additional AGPM Server connections, close the **Group Policy Object Editor** and deploy the GPO. (For more information, see [Deploy a GPO](deploy-a-gpo.md).) When Group Policy is updated, the AGPM Server connection is configured for all Group Policy administrators.
-
-###
-
-**To configure additional AGPM Servers for all Group Policy administrators**
-
-1. If no AGPM Server connection has been configured, follow the preceding procedure to configure a default AGPM Server for all domains.
-
-2. To configure separate AGPM Servers for some or all domains (overriding the default AGPM Server), in the **Group Policy Management Console** tree, edit a GPO that is applied to all Group Policy administrators. (For more information, see [Editing a GPO](editing-a-gpo.md).)
-
-3. Under **User Configuration** in the **Group Policy Object Editor**, double-click **Administrative Templates**, **Windows Components**, and then **AGPM**.
-
-4. In the details pane, double-click **AGPM Server**.
-
-5. In the **AGPM Server Properties** window, select the **Enabled** check box, and click **Show**.
-
-6. In the **Show Contents** window:
-
- 1. Click **Add**.
-
- 2. For **Value Name**, type the domain name (for example, server1.contoso.com).
-
- 3. For **Value**, type the AGPM Server name and port to use for this domain (for example, server2.contoso.com:4600), and then click **OK**. (By default, the AGPM Service listens on port 4600. To use a different port, see [Modify the Port on Which the AGPM Service Listens](modify-the-port-on-which-the-agpm-service-listens.md).)
-
- 4. Repeat for each domain not using the default AGPM Server.
-
-7. Click **OK** to close the **Show Contents** and **AGPM Server Properties** windows.
-
-8. Close the **Group Policy Object Editor**. (For more information, see [Deploy a GPO](deploy-a-gpo.md).) When Group Policy is updated, the new AGPM Server connections are configured for all Group Policy administrators.
-
-###
-
-If you have centrally configured the AGPM Server connection, the option to manually it is unavailable for all Group Policy administrators.
-
-**To manually configure the AGPM Server to display for your account**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. In the details pane, click the **AGPM Server** tab.
-
-3. Enter the fully-qualified computer name for the AGPM Server that manages the archive used for this domain (for example, server.contoso.com) and the port on which the AGPM Service listens (by default, port 4600).
-
-4. Click **Apply**, then click **Yes** to confirm.
-
-### Additional considerations
-
-- You must be able to edit and deploy a GPO to perform the procedures for centrally configuring AGPM Server connections for all Group Policy administrators. See [Editing a GPO](editing-a-gpo.md) and [Deploy a GPO](deploy-a-gpo.md) for additional detail.
-
-- The AGPM Server selected determines which GPOs are displayed on the **Contents** tab and to what location the **Domain Delegation** tab settings are applied. If not centrally managed through the Administrative Template, each Group Policy administrator must configure this setting to point to the AGPM Server for the domain.
-
-- Membership in the Group Policy Creator Owners group should be restricted so that it is not used to circumvent the management of access to GPOs by AGPM. (In the **Group Policy Management Console**, click **Group Policy Objects** in the forest and domain in which you want to manage GPOs, click **Delegation**, and then configure the settings to meet the needs of your organization.)
-
-### Additional references
-
-- [Performing AGPM Administrator Tasks](performing-agpm-administrator-tasks.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/configuring-advanced-group-policy-management-agpm40.md b/mdop/agpm/configuring-advanced-group-policy-management-agpm40.md
deleted file mode 100644
index 837ee68502..0000000000
--- a/mdop/agpm/configuring-advanced-group-policy-management-agpm40.md
+++ /dev/null
@@ -1,47 +0,0 @@
----
-title: Configuring Advanced Group Policy Management
-description: Configuring Advanced Group Policy Management
-author: dansimp
-ms.assetid: 8c978ddf-2789-44e4-9c08-de7b4cd1afa0
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Configuring Advanced Group Policy Management
-
-
-In Advanced Group Policy Management (AGPM), as an AGPM Administrator (Full Control), you can centrally configure AGPM Server connections for Group Policy administrators, configure e-mail notification for AGPM, configure optional e-mail security for AGPM, delegate access to Group Policy Objects (GPOs) in the production environment of the domain, and configure logging and tracing for troubleshooting.
-
-- [Configure AGPM Server Connections](configure-agpm-server-connections-agpm40.md)
-
-- [Configure E-Mail Notification](configure-e-mail-notification-agpm40.md)
-
-- [Configure E-Mail Security for AGPM](configure-e-mail-security-for-agpm-agpm40.md)
-
-- [Delegate Access to the Production Environment](delegate-access-to-the-production-environment-agpm40.md)
-
-- [Configure Logging and Tracing](configure-logging-and-tracing-agpm40.md)
-
-### Additional references
-
-- For information about delegating access to GPOs in the archive, see [Managing the Archive](managing-the-archive-agpm40.md).
-
-- For information about how to restrict the number of versions of each GPO stored in the archive, see [Limit the GPO Versions Stored](limit-the-gpo-versions-stored-agpm40.md).
-
-- [Performing AGPM Administrator Tasks](performing-agpm-administrator-tasks-agpm40.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/configuring-advanced-group-policy-management.md b/mdop/agpm/configuring-advanced-group-policy-management.md
deleted file mode 100644
index 2617957e16..0000000000
--- a/mdop/agpm/configuring-advanced-group-policy-management.md
+++ /dev/null
@@ -1,47 +0,0 @@
----
-title: Configuring Advanced Group Policy Management
-description: Configuring Advanced Group Policy Management
-author: dansimp
-ms.assetid: 836f4a49-2c77-4f6b-8727-9df7ef443141
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Configuring Advanced Group Policy Management
-
-
-In Advanced Group Policy Management (AGPM), as an AGPM Administrator (Full Control), you can centrally configure AGPM Server connections for Group Policy administrators, configure e-mail notification for AGPM, configure optional e-mail security for AGPM, delegate access to Group Policy Objects (GPOs) in the production environment, and configure logging and tracing for troubleshooting.
-
-- [Configure AGPM Server Connections](configure-agpm-server-connections-agpm30ops.md)
-
-- [Configure E-Mail Notification](configure-e-mail-notification-agpm30ops.md)
-
-- [Configure E-Mail Security for AGPM](configure-e-mail-security-for-agpm-agpm30ops.md)
-
-- [Delegate Access to the Production Environment](delegate-access-to-the-production-environment-agpm30ops.md)
-
-- [Configure Logging and Tracing](configure-logging-and-tracing-agpm30ops.md)
-
-### Additional references
-
-- For information about delegating access to GPOs in the archive, see [Managing the Archive](managing-the-archive.md).
-
-- For information about how to restrict the number of versions of each GPO stored in the archive, see [Limit the GPO Versions Stored](limit-the-gpo-versions-stored-agpm30ops.md).
-
-- [Performing AGPM Administrator Tasks](performing-agpm-administrator-tasks-agpm30ops.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/contents-tab-agpm30ops.md b/mdop/agpm/contents-tab-agpm30ops.md
deleted file mode 100644
index 4e3f28a7a2..0000000000
--- a/mdop/agpm/contents-tab-agpm30ops.md
+++ /dev/null
@@ -1,63 +0,0 @@
----
-title: Contents Tab
-description: Contents Tab
-author: dansimp
-ms.assetid: 6ada6430-cd93-47aa-af6e-d7f5b5620132
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Contents Tab
-
-
-The **Contents** tab on the **Change Control** pane provides access to Group Policy Objects (GPOs) and a shortcut menu for managing GPOs. The options displayed when right-clicking items are dependent on your role, your permissions, and your ownership stake in the GPO being managed. Additionally, these shortcut menus differ with the state of the GPO being managed.
-
-The following secondary tabs filter the list of GPOs displayed:
-
-- **Controlled**: GPOs managed by Advanced Group Policy Management (AGPM)
-
-- **Uncontrolled**: GPOs not managed by AGPM
-
-- **Pending**: GPO changes awaiting approval by an Approver
-
-- **Templates**: GPO templates for creating new GPOs and comparing to existing GPOs
-
-- **Recycle Bin**: Deleted GPOs
-
-The **Contents** tab and its secondary tabs provide details about each GPO and access to the history of each GPO:
-
-- [Contents Tab Features](contents-tab-features-agpm30ops.md)
-
-- [History Window](history-window-agpm30ops.md)
-
-When you right-click GPOs on any secondary tab, a shortcut menu unique to that tab is displayed, providing commands for managing the GPOs:
-
-- [Controlled GPO Commands](controlled-gpo-commands-agpm30ops.md)
-
-- [Uncontrolled GPO Commands](uncontrolled-gpo-commands-agpm30ops.md)
-
-- [Pending GPO Commands](pending-gpo-commands-agpm30ops.md)
-
-- [Template Commands](template-commands-agpm30ops.md)
-
-- [Recycle Bin Commands](recycle-bin-commands-agpm30ops.md)
-
-### Additional references
-
-- [User Interface: Advanced Group Policy Management](user-interface-advanced-group-policy-management-agpm30ops.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/contents-tab-agpm40.md b/mdop/agpm/contents-tab-agpm40.md
deleted file mode 100644
index 695acca3e9..0000000000
--- a/mdop/agpm/contents-tab-agpm40.md
+++ /dev/null
@@ -1,63 +0,0 @@
----
-title: Contents Tab
-description: Contents Tab
-author: dansimp
-ms.assetid: cf9d1f17-3c3d-422f-bd6b-3db87be45554
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Contents Tab
-
-
-The **Contents** tab on the **Change Control** pane provides access to Group Policy Objects (GPOs) and a shortcut menu for managing GPOs. The options displayed when right-clicking items are dependent on your role, your permissions, and your ownership stake in the GPO being managed. Additionally, these shortcut menus differ with the state of the GPO being managed.
-
-The following secondary tabs filter the list of GPOs displayed:
-
-- **Controlled**: GPOs managed by Advanced Group Policy Management (AGPM)
-
-- **Uncontrolled**: GPOs not managed by AGPM
-
-- **Pending**: GPO changes awaiting approval by an Approver
-
-- **Templates**: GPO templates for creating new GPOs and comparing to existing GPOs
-
-- **Recycle Bin**: Deleted GPOs
-
-The **Contents** tab and its secondary tabs provide details about each GPO and access to the history of each GPO:
-
-- [Contents Tab Features](contents-tab-features-agpm40.md)
-
-- [History Window](history-window-agpm40.md)
-
-When you right-click GPOs on any secondary tab, a shortcut menu unique to that tab is displayed, providing commands for managing the GPOs:
-
-- [Controlled GPO Commands](controlled-gpo-commands-agpm40.md)
-
-- [Uncontrolled GPO Commands](uncontrolled-gpo-commands-agpm40.md)
-
-- [Pending GPO Commands](pending-gpo-commands-agpm40.md)
-
-- [Template Commands](template-commands-agpm40.md)
-
-- [Recycle Bin Commands](recycle-bin-commands-agpm40.md)
-
-### Additional references
-
-- [User Interface: Advanced Group Policy Management](user-interface-advanced-group-policy-management-agpm40.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/contents-tab-features-agpm30ops.md b/mdop/agpm/contents-tab-features-agpm30ops.md
deleted file mode 100644
index b902fc0724..0000000000
--- a/mdop/agpm/contents-tab-features-agpm30ops.md
+++ /dev/null
@@ -1,133 +0,0 @@
----
-title: Contents Tab Features
-description: Contents Tab Features
-author: dansimp
-ms.assetid: 725f025a-c30a-4d07-add1-4e0ed9a1a5fd
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Contents Tab Features
-
-
-Each secondary tab within the **Contents** tab has two sections—**Group Policy objects** and **Groups and Users**.
-
-## Group Policy objects section
-
-
-The **Group Policy objects** section displays a filtered list of Group Policy Objects (GPOs) and identifies the following attributes for each GPO:
-
-
-
-
-
-
-
-
-
GPO attribute
-
Description
-
-
-
-
-
Name
-
Name of the GPO.
-
-
-
State
-
The state of the selected GPO
-
-
-
Changed By
-
The Editor who checked in or the Approver who deployed the selected GPO.
-
-
-
Change Date
-
For a controlled GPO, the most recent date it was checked in after being modified or checked out to be modified. For an uncontrolled GPO, the date when it was last modified.
-
-
-
Comment
-
A comment entered by the person who checked in or deployed a GPO at the time that it was modified. Useful for identifying the specifics of the version in case of the need to roll back to a previous version.
-
-
-
Computer Version
-
Automatically generated version of the Computer Configuration portion of the GPO.
-
-
-
User Version
-
Automatically generated version of the User Configuration portion of the GPO.
-
-
-
GPO Status
-
The Computer Configuration and the User Configuration can be managed separately. The GPO Status indicates which portions of the GPO are enabled.
-
-
-
WMI Filter
-
Display any WMI filters that are applied to this GPO. WMI filters are managed under the WMI Filters folder for the domain in the console tree of the GPMC.
-
-
-
-
-
-
-## Groups and Users section
-
-
-When a GPO is selected, the **Groups and Users** section displays a list of the groups and users with access to that GPO. The allowed permissions and inheritance are displayed for each group or user. An AGPM Administrator can configure permissions using either standard AGPM roles (Editor, Approver, Reviewer, and AGPM Administrator) or a customized combination of permissions.
-
-
-
-
-
-
-
-
-
Button
-
Effect
-
-
-
-
-
Add
-
Add a new entry to the security descriptor. Any user or group in Active Directory can be added.
-
-
-
Remove
-
Remove the selected entry from the Access Control List.
-
-
-
Properties
-
Display the properties for the selected object. The properties page is the same one displayed for an object in Active Directory Users and Computers.
-
-
-
Advanced
-
Open the Access Control List Editor.
-
-
-
-
-
-
-### Additional considerations
-
-- For information about roles and permissions related to specific tasks, see the tasks under [Performing AGPM Administrator Tasks](performing-agpm-administrator-tasks-agpm30ops.md), [Performing Editor Tasks](performing-editor-tasks-agpm30ops.md), [Performing Approver Tasks](performing-approver-tasks-agpm30ops.md), and [Performing Reviewer Tasks](performing-reviewer-tasks-agpm30ops.md).
-
-### Additional references
-
-- [Contents Tab](contents-tab-agpm30ops.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/contents-tab-features-agpm40.md b/mdop/agpm/contents-tab-features-agpm40.md
deleted file mode 100644
index 7b909fc508..0000000000
--- a/mdop/agpm/contents-tab-features-agpm40.md
+++ /dev/null
@@ -1,133 +0,0 @@
----
-title: Contents Tab Features
-description: Contents Tab Features
-author: dansimp
-ms.assetid: f1f4849d-bf94-47d5-ad81-0eee33abcaca
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Contents Tab Features
-
-
-Each secondary tab within the **Contents** tab has two sections—**Group Policy objects** and **Groups and Users**.
-
-## Group Policy objects section
-
-
-The **Group Policy objects** section displays a filtered list of Group Policy Objects (GPOs) and identifies the following attributes for each GPO. You can use the **Search** box to search for GPOs with specific attributes. For more information, see [Search and Filter the List of GPOs](search-and-filter-the-list-of-gpos.md).
-
-
-
-
-
-
-
-
-
GPO attribute
-
Description
-
-
-
-
-
Name
-
Name of the GPO.
-
-
-
State
-
The state of the selected GPO
-
-
-
Changed By
-
The Editor who checked in or the Approver who deployed the selected GPO.
-
-
-
Change Date
-
For a controlled GPO, the most recent date it was checked in after being modified or checked out to be modified. For an uncontrolled GPO, the date when it was last modified.
-
-
-
Comment
-
A comment entered by the person who checked in or deployed a GPO at the time that it was modified. Useful for identifying the specifics of the version in case of the need to roll back to an earlier version.
-
-
-
Computer Version
-
Automatically generated version of the Computer Configuration part of the GPO.
-
-
-
User Version
-
Automatically generated version of the User Configuration part of the GPO.
-
-
-
GPO Status
-
The Computer Configuration and the User Configuration can be managed separately. The GPO Status indicates which portions of the GPO are enabled.
-
-
-
WMI Filter
-
Display any WMI filters that are applied to this GPO. WMI filters are managed under the WMI Filters folder for the domain in the console tree of the GPMC.
-
-
-
-
-
-
-## Groups and Users section
-
-
-When a GPO is selected, the **Groups and Users** section displays a list of the groups and users with access to that GPO. The allowed permissions and inheritance are displayed for each group or user. An AGPM Administrator can configure permissions using either standard AGPM roles (Editor, Approver, Reviewer, and AGPM Administrator) or a customized combination of permissions.
-
-
-
-
-
-
-
-
-
Button
-
Effect
-
-
-
-
-
Add
-
Add a new entry to the security descriptor. Any user or group in Active Directory can be added.
-
-
-
Remove
-
Remove the selected entry from the Access Control List.
-
-
-
Properties
-
Display the properties for the selected object. The properties page is the same one displayed for an object in Active Directory Users and Computers.
-
-
-
Advanced
-
Open the Access Control List Editor.
-
-
-
-
-
-
-### Additional considerations
-
-- For information about roles and permissions related to specific tasks, see the tasks under [Performing AGPM Administrator Tasks](performing-agpm-administrator-tasks-agpm40.md), [Performing Editor Tasks](performing-editor-tasks-agpm40.md), [Performing Approver Tasks](performing-approver-tasks-agpm40.md), and [Performing Reviewer Tasks](performing-reviewer-tasks-agpm40.md).
-
-### Additional references
-
-- [Contents Tab](contents-tab-agpm40.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/contents-tab.md b/mdop/agpm/contents-tab.md
deleted file mode 100644
index 4d154e05f6..0000000000
--- a/mdop/agpm/contents-tab.md
+++ /dev/null
@@ -1,51 +0,0 @@
----
-title: Contents Tab
-description: Contents Tab
-author: dansimp
-ms.assetid: 8a756bc1-3900-4d83-93c4-7ebc4705d956
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Contents Tab
-
-
-The **Contents** tab on the **Change Control** pane provides access to Group Policy objects (GPOs) and a shortcut menu for managing GPOs. The options displayed when right-clicking items are dependent on your role, your permissions, and your ownership stake in the GPO being managed. Additionally, these shortcut menus differ with the state of the GPO being managed.
-
-The secondary tabs filter the list of GPOs displayed.
-
-- [Controlled Tab](controlled-tab.md): GPOs managed by AGPM
-
-- [Uncontrolled Tab](uncontrolled-tab.md): GPOs not managed by AGPM
-
-- [Pending Tab](pending-tab.md): GPO changes awaiting approval by an Approver
-
-- [Templates Tab](templates-tab.md): GPO templates for creating new GPOs and comparing to existing GPOs
-
-- [Recycle Bin Tab](recycle-bin-tab.md): Deleted GPOs
-
-Additionally, the secondary tabs provide access to the History of each GPO and to other features:
-
-- [Common Secondary Tab Features](common-secondary-tab-features.md)
-
-- [History Window](history-window.md)
-
-### Additional references
-
-- [User Interface: Advanced Group Policy Management](user-interface-advanced-group-policy-management.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/control-a-previously-uncontrolled-gpo.md b/mdop/agpm/control-a-previously-uncontrolled-gpo.md
deleted file mode 100644
index 6932d224a9..0000000000
--- a/mdop/agpm/control-a-previously-uncontrolled-gpo.md
+++ /dev/null
@@ -1,51 +0,0 @@
----
-title: Control a Previously Uncontrolled GPO
-description: Control a Previously Uncontrolled GPO
-author: dansimp
-ms.assetid: 452689a9-4e32-4e3b-8208-56353a82bf36
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Control a Previously Uncontrolled GPO
-
-
-To use Advanced Group Policy Management (AGPM) to provide change control for a Group Policy object (GPO), you must first control the GPO with AGPM.
-
-A user account with the Approver or AGPM Administrator (Full Control) role or necessary permissions in Advanced Group Policy Management is required to complete this procedure. Review the details in "Additional considerations" in this topic.
-
-**To control a previously uncontrolled GPO**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. On the **Contents** tab in the details pane, click the **Uncontrolled** tab to display the uncontrolled GPOs.
-
-3. Right-click the GPO to be controlled with AGPM, and then click **Control**.
-
-4. Type a comment to be displayed in the history of the GPO, and then click **OK**.
-
-5. When the **Progress** window indicates that overall progress is complete, click **Close**. The GPO is removed from the list on the **Uncontrolled** tab and added to the **Controlled** tab.
-
-### Additional considerations
-
-- By default, you must be an Approver or an AGPM Administrator (Full Control) to perform this procedure. Specifically, you must have **List Contents** and **Create GPO** permissions for the domain.
-
-### Additional references
-
-- [Creating, Controlling, or Importing a GPO](creating-controlling-or-importing-a-gpo-approver.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/control-an-uncontrolled-gpo-agpm30ops.md b/mdop/agpm/control-an-uncontrolled-gpo-agpm30ops.md
deleted file mode 100644
index 87d980d262..0000000000
--- a/mdop/agpm/control-an-uncontrolled-gpo-agpm30ops.md
+++ /dev/null
@@ -1,51 +0,0 @@
----
-title: Control an Uncontrolled GPO
-description: Control an Uncontrolled GPO
-author: dansimp
-ms.assetid: 603f00f9-1e65-4b2f-902a-e53dafedbd8d
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Control an Uncontrolled GPO
-
-
-To provide change control for a Group Policy Object (GPO), you must first control the GPO.
-
-A user account with the Approver or AGPM Administrator (Full Control) role or necessary permissions in Advanced Group Policy Management (AGPM) is required to complete this procedure. Review the details in "Additional considerations" in this topic.
-
-**To control an uncontrolled GPO**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. On the **Contents** tab in the details pane, click the **Uncontrolled** tab to display the uncontrolled GPOs.
-
-3. Right-click the GPO to be controlled with AGPM, and then click **Control**.
-
-4. Type a comment to be displayed in the history of the GPO, and then click **OK**.
-
-5. When the **Progress** window indicates that overall progress is complete, click **Close**. The GPO is removed from the list on the **Uncontrolled** tab and added to the **Controlled** tab.
-
-### Additional considerations
-
-- By default, you must be an Approver or an AGPM Administrator (Full Control) to perform this procedure. Specifically, you must have **List Contents** and **Create GPO** permissions for the domain.
-
-### Additional references
-
-- [Creating, Controlling, or Importing a GPO](creating-controlling-or-importing-a-gpo-editor-agpm30ops.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/control-an-uncontrolled-gpo-agpm40.md b/mdop/agpm/control-an-uncontrolled-gpo-agpm40.md
deleted file mode 100644
index 438609f31c..0000000000
--- a/mdop/agpm/control-an-uncontrolled-gpo-agpm40.md
+++ /dev/null
@@ -1,51 +0,0 @@
----
-title: Control an Uncontrolled GPO
-description: Control an Uncontrolled GPO
-author: dansimp
-ms.assetid: dc81545c-8da5-4b6f-b266-f01a82e27c6b
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Control an Uncontrolled GPO
-
-
-To provide change control for a Group Policy Object (GPO), you must first control the GPO.
-
-A user account with the Approver or AGPM Administrator (Full Control) role or necessary permissions in Advanced Group Policy Management (AGPM) is required to complete this procedure. Review the details in "Additional considerations" in this topic.
-
-**To control an uncontrolled GPO**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. On the **Contents** tab in the details pane, click the **Uncontrolled** tab to display the uncontrolled GPOs.
-
-3. Right-click the GPO to be controlled with AGPM, and then click **Control**.
-
-4. Type a comment to be displayed in the history of the GPO, and then click **OK**.
-
-5. When the **Progress** window indicates that overall progress is complete, click **Close**. The GPO is removed from the list on the **Uncontrolled** tab and added to the **Controlled** tab.
-
-### Additional considerations
-
-- By default, you must be an Approver or an AGPM Administrator (Full Control) to perform this procedure. Specifically, you must have **List Contents** and **Create GPO** permissions for the domain.
-
-### Additional references
-
-- [Creating or Controlling a GPO](creating-or-controlling-a-gpo-agpm40-app.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/controlled-gpo-commands-agpm30ops.md b/mdop/agpm/controlled-gpo-commands-agpm30ops.md
deleted file mode 100644
index 494e7b2c47..0000000000
--- a/mdop/agpm/controlled-gpo-commands-agpm30ops.md
+++ /dev/null
@@ -1,211 +0,0 @@
----
-title: Controlled GPO Commands
-description: Controlled GPO Commands
-author: dansimp
-ms.assetid: 82db4772-154a-4a8d-99cd-2c69e1738698
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Controlled GPO Commands
-
-
-The **Controlled** tab:
-
-- Displays a list of Group Policy Objects (GPOs) managed by Advanced Group Policy Management (AGPM).
-
-- Provides a shortcut menu with commands for managing GPOs and for displaying the history and reports for GPOs.
-
-- Displays a list of the groups and users who have permission to access a selected GPO.
-
-Right-clicking the **Group Policy Objects** list on this tab displays a shortcut menu, including whichever of the following options are applicable.
-
-## Control and history
-
-
-
-
-
-
-
-
-
-
Command
-
Effect
-
-
-
-
-
New Controlled GPO
-
Create a new GPO with change control managed through AGPM and deploy it to the production environment. If you do not have permission to create a GPO, you will be prompted to submit a request. (This option is displayed if no GPO is selected when right-clicking in the Group Policy Objects list.)
-
-
-
History
-
Open a window listing all versions of the selected GPO saved within the archive. From the history, you can obtain a report of the settings within a GPO, compare two versions of a GPO, compare a GPO to a template, or roll back to a previous version of a GPO.
-
-
-
-
-
-
-## Reports
-
-
-
-
-
-
-
-
-
-
Command
-
Effect
-
-
-
-
-
Settings
-
Generate an HTML-based or XML-based report displaying the settings within the selected GPO or display links to the selected GPO(s) from organizational units as of when the GPO(s) was most recently controlled, imported, or checked in.
-
-
-
Differences
-
Generate an HTML-based or XML-based report comparing the settings within two selected GPOs or within the selected GPO and a template.
-
-
-
-
-
-
-## Editing
-
-
-
-
-
-
-
-
-
-
Command
-
Effect
-
-
-
-
-
Edit
-
Open the Group Policy Management Editor window to make changes to the selected GPO.
-
-
-
Check Out
-
Obtain a copy of the selected GPO from the archive for offline editing and prohibit anyone else from editing it until it is checked back into the archive. (Check Out can be overridden by an AGPM Administrator (Full Control).)
-
-
-
Check In
-
Check the edited version of the selected GPO into the archive, so other authorized Editors can make changes or an Approver can deploy it to the production environment.
-
-
-
Undo Check Out
-
Return a checked out GPO to the archive without any changes.
-
-
-
-
-
-
-## Version management
-
-
-
-
-
-
-
-
-
-
Command
-
Effect
-
-
-
-
-
Import from Production
-
For the selected GPO, copy the version in the production environment to the archive.
-
-
-
Delete
-
Move the selected GPO to the Recycle Bin and indicate whether to leave the deployed version (if one exists) in production or to delete it as well as the version in the archive. If you do not have permission to delete a GPO, you will be prompted to submit a request.
-
-
-
Deploy
-
Move the selected GPO that is checked into the archive to the production environment. This action makes it active on the network and overwrites the previously active version of the GPO if one existed. If you do not have permission to deploy a GPO, you will be prompted to submit a request.
-
-
-
Label
-
Mark the selected GPO with a descriptive label (such as "Known good") and comment for record keeping. Labels appear in the State column and comments in the Comment column of the History window, enabling you to easily identify previous versions of a GPO identified with a particular label, so you can roll back if a problem occurs.
-
-
-
Rename
-
Change the name of the selected GPO. If the GPO has already been deployed, the name will be updated in the production environment when the GPO is redeployed.
-
-
-
Save as Template
-
Create a new template based on the settings of the selected GPO.
-
-
-
-
-
-
-## Miscellaneous
-
-
-
-
-
-
-
-
-
-
Command
-
Effect
-
-
-
-
-
Refresh
-
Update the display of the Group Policy Management Console (GPMC) to incorporate any changes. Some changes are not visible until the display is refreshed.
-
-
-
Help
-
Display help for AGPM.
-
-
-
-
-
-
-### Additional references
-
-- [Contents Tab](contents-tab-agpm30ops.md)
-
-- [Performing Editor Tasks](performing-editor-tasks-agpm30ops.md)
-
-- [Performing Approver Tasks](performing-approver-tasks-agpm30ops.md)
-
-- [Performing Reviewer Tasks](performing-reviewer-tasks-agpm30ops.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/controlled-gpo-commands-agpm40.md b/mdop/agpm/controlled-gpo-commands-agpm40.md
deleted file mode 100644
index 38253ca7d8..0000000000
--- a/mdop/agpm/controlled-gpo-commands-agpm40.md
+++ /dev/null
@@ -1,219 +0,0 @@
----
-title: Controlled GPO Commands
-description: Controlled GPO Commands
-author: dansimp
-ms.assetid: 370d3db9-4efc-4799-983d-e29ba5f32b07
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Controlled GPO Commands
-
-
-The **Controlled** tab:
-
-- Displays a list of Group Policy Objects (GPOs) managed by Advanced Group Policy Management (AGPM).
-
-- Provides a shortcut menu with commands for managing GPOs and for displaying the history and reports for GPOs.
-
-- Displays a list of the groups and users who have permission to access a selected GPO.
-
-Right-clicking the **Group Policy Objects** list on this tab displays a shortcut menu. This menu includes whichever of the following options are applicable.
-
-## Control and history
-
-
-
-
-
-
-
-
-
-
Command
-
Effect
-
-
-
-
-
New Controlled GPO
-
Create a new GPO with change control managed through AGPM and deploy it to the production environment of the domain. If you do not have permission to create a GPO, you are prompted to submit a request. (This option is displayed if no GPO is selected when right-clicking in the Group Policy Objects list.)
-
-
-
History
-
Open a window listing all versions of the selected GPO saved within the archive. From the history, you can obtain a report of the settings within a GPO, compare two versions of a GPO, compare a GPO to a template, or roll back to an earlier version of a GPO.
-
-
-
-
-
-
-## Reports
-
-
-
-
-
-
-
-
-
-
Command
-
Effect
-
-
-
-
-
Settings
-
Generate an HTML-based or XML-based report displaying the settings within the selected GPO or display links to the selected GPO(s) from organizational units as of when the GPO(s) was most recently controlled, imported, or checked in.
-
-
-
Differences
-
Generate an HTML-based or XML-based report comparing the settings within two selected GPOs or within the selected GPO and a template.
-
-
-
-
-
-
-## Editing
-
-
-
-
-
-
-
-
-
-
Command
-
Effect
-
-
-
-
-
Edit
-
Open the Group Policy Management Editor window to change the selected GPO.
-
-
-
Check Out
-
Obtain a copy of the selected GPO from the archive for offline editing and prohibit anyone else from editing the GPO until it is checked back into the archive. Check Out can be overridden by an AGPM Administrator (Full Control).
-
-
-
Check In
-
Check the edited version of the selected GPO into the archive, so other authorized Editors can make changes or an Approver can deploy the GPO to the production environment of the domain.
-
-
-
Undo Check Out
-
Return a checked out GPO to the archive without any changes.
-
-
-
-
-
-
-## Version management
-
-
-
-
-
-
-
-
-
-
Command
-
Effect
-
-
-
-
-
Import from Production
-
For the selected GPO, copy the version in the production environment of the domain to the archive.
-
-
-
Import from File
-
Replace the policy settings of the selected, checked-out GPO with those from a GPO backup file.
-
-
-
Delete
-
Move the selected GPO to the Recycle Bin and indicate whether to leave the deployed version (if one exists) in production or to delete the deployed version in addition to the version in the archive. If you do not have permission to delete a GPO, you are prompted to submit a request.
-
-
-
Deploy
-
Move the selected GPO that is checked into the archive to the production environment of the domain. This action makes it active on the network and overwrites the previously active version of the GPO if one existed. If you do not have permission to deploy a GPO, you will be prompted to submit a request.
-
-
-
Export to
-
Save the selected GPO to a backup file so that you can copy it to another domain.
-
-
-
Label
-
Mark the selected GPO with a descriptive label (such as "Known good") and comment for record keeping. Labels appear in the State column and comments in the Comment column of the History window. They help you identify earlier versions of a GPO so that you can roll back if a problem occurs.
-
-
-
Rename
-
Change the name of the selected GPO. If the GPO has already been deployed, the name will be updated in the production environment of the domain when the GPO is redeployed.
-
-
-
Save as Template
-
Create a new template based on the settings of the selected GPO.
-
-
-
-
-
-
-## Miscellaneous
-
-
-
-
-
-
-
-
-
-
Command
-
Effect
-
-
-
-
-
Refresh
-
Update the display of the Group Policy Management Console (GPMC) to incorporate any changes. Some changes are not visible until the display is refreshed.
-
-
-
Help
-
Display help for AGPM.
-
-
-
-
-
-
-### Additional references
-
-- [Contents Tab](contents-tab-agpm40.md)
-
-- [Performing Editor Tasks](performing-editor-tasks-agpm40.md)
-
-- [Performing Approver Tasks](performing-approver-tasks-agpm40.md)
-
-- [Performing Reviewer Tasks](performing-reviewer-tasks-agpm40.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/controlled-tab.md b/mdop/agpm/controlled-tab.md
deleted file mode 100644
index 64d9853749..0000000000
--- a/mdop/agpm/controlled-tab.md
+++ /dev/null
@@ -1,211 +0,0 @@
----
-title: Controlled Tab
-description: Controlled Tab
-author: dansimp
-ms.assetid: 8995a9e1-ace4-40b7-a47b-e1e9924541ba
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Controlled Tab
-
-
-The **Controlled** tab:
-
-- Displays a list of Group Policy objects (GPOs) managed by Advanced Group Policy Management (AGPM).
-
-- Provides a shortcut menu with commands for managing GPOs and for displaying the history and reports for GPOs.
-
-- Displays a list of the groups and users who have permission to access a selected GPO.
-
-Right-clicking the **Group Policy Objects** list on this tab displays a shortcut menu, including whichever of the following options are applicable.
-
-## Control and history
-
-
-
-
-
-
-
-
-
-
Command
-
Effect
-
-
-
-
-
New Controlled GPO
-
Create a new GPO with change control managed through AGPM and deploy it to the production environment. If you do not have permission to create a GPO, you will be prompted to submit a request. (This option is displayed if no GPO is selected when right-clicking in the Group Policy Objects list.)
-
-
-
History
-
Open a window listing all versions of the selected GPO saved within the archive. From the history, you can obtain a report of the settings within a GPO, compare two versions of a GPO, compare a GPO to a template, or roll back to a previous version of a GPO.
-
-
-
-
-
-
-## Reports
-
-
-
-
-
-
-
-
-
-
Command
-
Effect
-
-
-
-
-
Settings
-
Generate an HTML-based or XML-based report displaying the settings within the selected GPO or display links to the selected GPO(s) from organizational units as of when the GPO(s) was most recently controlled, imported, or checked in.
-
-
-
Differences
-
Generate an HTML-based or XML-based report comparing the settings within two selected GPOs or within the selected GPO and a template.
-
-
-
-
-
-
-## Editing
-
-
-
-
-
-
-
-
-
-
Command
-
Effect
-
-
-
-
-
Edit
-
Open the Group Policy Object Editor to make changes to the selected GPO.
-
-
-
Check Out
-
Obtain a copy of the selected GPO from the archive for offline editing and prohibit anyone else from editing it until it is checked back into the archive. (Check Out can be overridden by an AGPM Administrator (Full Control).)
-
-
-
Check In
-
Check the edited version of the selected GPO into the archive, so other authorized Editors can make changes or an Approver can deploy it to the production environment.
-
-
-
Undo Check Out
-
Return a checked out GPO to the archive without any changes.
-
-
-
-
-
-
-## Version management
-
-
-
-
-
-
-
-
-
-
Command
-
Effect
-
-
-
-
-
Import from Production
-
For the selected GPO, copy the version in the production environment to the archive.
-
-
-
Delete
-
Move the selected GPO to the Recycle Bin and indicate whether to leave the deployed version (if one exists) in production or to delete it as well as the version in the archive. If you do not have permission to delete a GPO, you will be prompted to submit a request.
-
-
-
Deploy
-
Move the selected GPO that is checked into the archive to the production environment. This action makes it active on the network and overwrites the previously active version of the GPO if one existed. If you do not have permission to deploy a GPO, you will be prompted to submit a request.
-
-
-
Label
-
Mark the selected GPO with a descriptive label (such as "Known good") and comment for record keeping. Labels appear in the State column and comments in the Comment column of the History window, enabling you to easily identify previous versions of a GPO identified with a particular label, so you can roll back if a problem occurs.
-
-
-
Rename
-
Change the name of the selected GPO. If the GPO has already been deployed, the name will be updated in the production environment when the GPO is redeployed.
-
-
-
Save as Template
-
Create a new template based on the settings of the selected GPO.
-
-
-
-
-
-
-## Miscellaneous
-
-
-
-
-
-
-
-
-
-
Command
-
Effect
-
-
-
-
-
Refresh
-
Update the display of the Group Policy Management Console to incorporate any changes. Some changes are not visible until the display is refreshed.
-
-
-
Help
-
Display help for AGPM.
-
-
-
-
-
-
-### Additional references
-
-- [Contents Tab](contents-tab.md)
-
-- [Performing Editor Tasks](performing-editor-tasks.md)
-
-- [Performing Approver Tasks](performing-approver-tasks.md)
-
-- [Performing Reviewer Tasks](performing-reviewer-tasks.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/create-a-new-controlled-gpo-agpm30ops.md b/mdop/agpm/create-a-new-controlled-gpo-agpm30ops.md
deleted file mode 100644
index 2b6c82070c..0000000000
--- a/mdop/agpm/create-a-new-controlled-gpo-agpm30ops.md
+++ /dev/null
@@ -1,59 +0,0 @@
----
-title: Create a New Controlled GPO
-description: Create a New Controlled GPO
-author: dansimp
-ms.assetid: f89eaae8-7858-4222-ba3f-a93a9d7ea5a3
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Create a New Controlled GPO
-
-
-New Group Policy Objects (GPOs) created through the **Change Control** folder will automatically be controlled, enabling you to manage them.
-
-A user account with the Approver or AGPM Administrator (Full Control) role or necessary permissions in Advanced Group Policy Management (AGPM) is required to complete this procedure. Review the details in "Additional considerations" in this topic.
-
-**To create a new GPO with change control managed through AGPM**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. Right-click **Change Control**, and then click **New Controlled GPO**.
-
-3. In the **New Controlled GPO** dialog box:
-
- 1. Type a name for the new GPO.
-
- 2. Optional: Type a comment for the new GPO to be displayed in the **History** for the GPO.
-
- 3. To immediately deploy the new GPO to the production environment, click **Create live**. To create the new GPO offline without immediately deploying it, click **Create offline**.
-
- 4. Select the GPO template to use as a starting point for the new GPO.
-
- 5. Click **OK**.
-
-4. When the **Progress** window indicates that overall progress is complete, click **Close**. The new GPO is displayed in the list of GPOs on the **Controlled** tab.
-
-### Additional considerations
-
-- By default, you must be an Approver or an AGPM Administrator (Full Control) to perform this procedure. Specifically, you must have **List Contents** and **Create GPO** permissions for the domain.
-
-### Additional references
-
-- [Creating, Controlling, or Importing a GPO](creating-controlling-or-importing-a-gpo-editor-agpm30ops.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/create-a-new-controlled-gpo-agpm40.md b/mdop/agpm/create-a-new-controlled-gpo-agpm40.md
deleted file mode 100644
index e688f80ebc..0000000000
--- a/mdop/agpm/create-a-new-controlled-gpo-agpm40.md
+++ /dev/null
@@ -1,57 +0,0 @@
----
-title: Create a New Controlled GPO
-description: Create a New Controlled GPO
-author: dansimp
-ms.assetid: 5ce760f6-9f05-42b4-b787-7835ab8e324e
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Create a New Controlled GPO
-
-
-New Group Policy Objects (GPOs) created through the **Change Control** folder will automatically be controlled, enabling you to manage them.
-
-A user account with the Approver or AGPM Administrator (Full Control) role or necessary permissions in Advanced Group Policy Management (AGPM) is required to complete this procedure. Review the details in "Additional considerations" in this topic.
-
-**To create a new GPO with change control managed through AGPM**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. Right-click **Change Control**, and then click **New Controlled GPO**.
-
-3. In the **New Controlled GPO** dialog box:
-
- 1. Type a name for the new GPO.
-
- 2. Optional: Type a comment for the new GPO to be displayed in the **History** for the GPO.
-
- 3. To immediately deploy the new GPO to the production environment of the domain, click **Create live**. To create the new GPO offline without immediately deploying it, click **Create offline**.
-
- 4. Select the GPO template to use as a starting point for the new GPO, and then click **OK**.
-
-4. When the **Progress** window indicates that overall progress is complete, click **Close**. The new GPO is displayed in the list of GPOs on the **Controlled** tab.
-
-### Additional considerations
-
-- By default, you must be an Approver or an AGPM Administrator (Full Control) to perform this procedure. Specifically, you must have **List Contents** and **Create GPO** permissions for the domain.
-
-### Additional references
-
-- [Creating or Controlling a GPO](creating-or-controlling-a-gpo-agpm40-app.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/create-a-new-controlled-gpo.md b/mdop/agpm/create-a-new-controlled-gpo.md
deleted file mode 100644
index dc4d11b70b..0000000000
--- a/mdop/agpm/create-a-new-controlled-gpo.md
+++ /dev/null
@@ -1,59 +0,0 @@
----
-title: Create a New Controlled GPO
-description: Create a New Controlled GPO
-author: dansimp
-ms.assetid: b43ce0f4-4519-4278-83c4-c7d5163ddd11
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Create a New Controlled GPO
-
-
-New Group Policy objects (GPOs) created through the **Change Control** node will automatically be controlled, enabling you to manage them with Advanced Group Policy Management (AGPM).
-
-A user account with the Approver or AGPM Administrator (Full Control) role or necessary permissions in Advanced Group Policy Management is required to complete this procedure. Review the details in "Additional considerations" in this topic.
-
-**To create a new GPO with change control managed through AGPM**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. Right-click the **Change Control** node, and then click **New Controlled GPO**.
-
-3. In the **New Controlled GPO** dialog box:
-
- 1. Type a name for the new GPO.
-
- 2. Optional: Type a comment for the new GPO to be displayed in the **History** for the GPO.
-
- 3. To immediately deploy the new GPO to the production environment, click **Create live**. To create the new GPO offline without immediately deploying it, click **Create offline**.
-
- 4. Select the GPO template to use as a starting point for the new GPO.
-
- 5. Click **OK**.
-
-4. When the **Progress** window indicates that overall progress is complete, click **Close**. The new GPO is displayed in the list of GPOs on the **Controlled** tab.
-
-### Additional considerations
-
-- By default, you must be an Approver or an AGPM Administrator (Full Control) to perform this procedure. Specifically, you must have **List Contents** and **Create GPO** permissions for the domain.
-
-### Additional references
-
-- [Creating, Controlling, or Importing a GPO](creating-controlling-or-importing-a-gpo-approver.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/create-a-template-agpm30ops.md b/mdop/agpm/create-a-template-agpm30ops.md
deleted file mode 100644
index 0af27e71f6..0000000000
--- a/mdop/agpm/create-a-template-agpm30ops.md
+++ /dev/null
@@ -1,62 +0,0 @@
----
-title: Create a Template
-description: Create a Template
-author: dansimp
-ms.assetid: 8208f14a-5c18-43a7-8564-118230398cca
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Create a Template
-
-
-Creating a template enables you to save all of the settings of a particular version of a Group Policy Object (GPO) to use as a starting point for creating new GPOs.
-
-**Note**
-A template is an uneditable, static version of a GPO for use as a starting point for creating new, editable GPOs.
-
-
-
-A user account with the Editor or AGPM Administrator (Full Control) role or necessary permissions in Advanced Group Policy Management (AGPM) is required to complete this procedure. Review the details in "Additional considerations" in this topic.
-
-**To create a template based on an existing GPO**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. On the **Contents** tab in the details pane, click the **Controlled** or **Uncontrolled** tab to display available GPOs.
-
-3. Right-click the GPO from which you want to create a template, and then click **Save as Template**.
-
-4. Type a name for the template and a comment, and then click **OK**.
-
-5. When the **Progress** window indicates that overall progress is complete, click **Close**. The new template appears on the **Templates** tab.
-
-### Additional considerations
-
-- By default, you must be an Editor or an AGPM Administrator (Full Control) to perform this procedure. Specifically, you must have **List Contents** and **Create Template** permissions for the domain.
-
-- Renaming or deleting a template does not impact GPOs created from that template.
-
-- Because it cannot be altered, a template does not have a history.
-
-### Additional references
-
-- [Creating a Template and Setting a Default Template](creating-a-template-and-setting-a-default-template-agpm30ops.md)
-
-- [Request the Creation of a New Controlled GPO](request-the-creation-of-a-new-controlled-gpo-agpm30ops.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/create-a-template-agpm40.md b/mdop/agpm/create-a-template-agpm40.md
deleted file mode 100644
index bb0d209a5b..0000000000
--- a/mdop/agpm/create-a-template-agpm40.md
+++ /dev/null
@@ -1,62 +0,0 @@
----
-title: Create a Template
-description: Create a Template
-author: dansimp
-ms.assetid: b38423af-7d24-437a-98bc-01f1ae891127
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Create a Template
-
-
-Creating a template enables you to save all of the settings of a particular version of a Group Policy Object (GPO) to use as a starting point for creating new GPOs.
-
-**Note**
-A template is an uneditable, static version of a GPO for use as a starting point for creating new, editable GPOs.
-
-
-
-A user account with the Editor or AGPM Administrator (Full Control) role or necessary permissions in Advanced Group Policy Management (AGPM) is required to complete this procedure. Review the details in "Additional considerations" in this topic.
-
-**To create a template based on an existing GPO**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. On the **Contents** tab in the details pane, click the **Controlled** or **Uncontrolled** tab to display available GPOs.
-
-3. Right-click the GPO from which you want to create a template, and then click **Save as Template**.
-
-4. Type a name for the template and a comment, and then click **OK**.
-
-5. When the **Progress** window indicates that overall progress is complete, click **Close**. The new template appears on the **Templates** tab.
-
-### Additional considerations
-
-- By default, you must be an Editor or an AGPM Administrator (Full Control) to perform this procedure. Specifically, you must have **List Contents** and **Create Template** permissions for the domain.
-
-- Renaming or deleting a template does not impact GPOs created from that template.
-
-- Because it cannot be altered, a template does not have a history.
-
-### Additional references
-
-- [Creating a Template and Setting a Default Template](creating-a-template-and-setting-a-default-template-agpm40.md)
-
-- [Request the Creation of a New Controlled GPO](request-the-creation-of-a-new-controlled-gpo-agpm40.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/create-a-template.md b/mdop/agpm/create-a-template.md
deleted file mode 100644
index f25308b5ea..0000000000
--- a/mdop/agpm/create-a-template.md
+++ /dev/null
@@ -1,62 +0,0 @@
----
-title: Create a Template
-description: Create a Template
-author: dansimp
-ms.assetid: 6992bd55-4a4f-401f-9815-c468bac598ef
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Create a Template
-
-
-Creating a template enables you to save all of the settings of a particular version of a Group Policy object (GPO) to use as a starting point for creating new GPOs.
-
-**Note**
-A template is an uneditable, static version of a GPO for use as a starting point for creating new, editable GPOs.
-
-
-
-A user account with the Editor or AGPM Administrator (Full Control) role or necessary permissions in Advanced Group Policy Management is required to complete this procedure. Review the details in "Additional considerations" in this topic.
-
-**To create a template based on an existing GPO**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. On the **Contents** tab in the details pane, click the **Controlled** or **Uncontrolled** tab to display available GPOs.
-
-3. Right-click the GPO from which you want to create a template, then click **Save as Template**.
-
-4. Type a name for the template and a comment, then click **OK**.
-
-5. When the **Progress** window indicates that overall progress is complete, click **Close**. The new template appears on the **Templates** tab.
-
-### Additional considerations
-
-- By default, you must be an Editor or an AGPM Administrator (Full Control) to perform this procedure. Specifically, you must have **List Contents** and **Create Template** permissions for the domain.
-
-- Renaming or deleting a template does not impact GPOs created from that template.
-
-- Because it cannot be altered, a template does not have a history.
-
-### Additional references
-
-- [Creating a Template and Setting a Default Template](creating-a-template-and-setting-a-default-template.md)
-
-- [Request the Creation of a New Controlled GPO](request-the-creation-of-a-new-controlled-gpo.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/creating-a-template-and-setting-a-default-template-agpm30ops.md b/mdop/agpm/creating-a-template-and-setting-a-default-template-agpm30ops.md
deleted file mode 100644
index 946f6e4a3c..0000000000
--- a/mdop/agpm/creating-a-template-and-setting-a-default-template-agpm30ops.md
+++ /dev/null
@@ -1,50 +0,0 @@
----
-title: Creating a Template and Setting a Default Template
-description: Creating a Template and Setting a Default Template
-author: dansimp
-ms.assetid: acce0e0f-7e67-479c-9daa-e678fccd7ced
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Creating a Template and Setting a Default Template
-
-
-Creating a template enables you to save all the settings of a particular version of a Group Policy Object (GPO) to use as a starting point for creating new GPOs. As an Editor, you can also specify which of the available templates will be the default template for all Group Policy administrators creating new GPOs.
-
-Some potential uses for a template include the following:
-
-- Create a security baseline that your organization can reuse across domains.
-
-- Create a template to manage folder redirection and offline files that your organization can customize for each department.
-
-- Create a wireless networking template that your organization can use to configure wireless network connections for different geographical areas.
-
-- Create regulatory compliance templates for local network administrators.
-
-- Create a read-only snapshot of an existing GPO.
-
-**Note**
-A template is a static version of a GPO that cannot be edited, yet can be used as a starting point for creating new, editable GPOs. Renaming or deleting a template does not affect GPOs created from that template.
-
-
-
-- [Create a Template](create-a-template-agpm30ops.md)
-
-- [Set a Default Template](set-a-default-template-agpm30ops.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/creating-a-template-and-setting-a-default-template-agpm40.md b/mdop/agpm/creating-a-template-and-setting-a-default-template-agpm40.md
deleted file mode 100644
index 7b81b2a43d..0000000000
--- a/mdop/agpm/creating-a-template-and-setting-a-default-template-agpm40.md
+++ /dev/null
@@ -1,50 +0,0 @@
----
-title: Creating a Template and Setting a Default Template
-description: Creating a Template and Setting a Default Template
-author: dansimp
-ms.assetid: ffa72c2a-64eb-4492-8072-c3a66179b546
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Creating a Template and Setting a Default Template
-
-
-Creating a template enables you to save all the settings of a particular version of a Group Policy Object (GPO) to use as a starting point for creating new GPOs. As an Editor, you can also specify which of the available templates will be the default template for all Group Policy administrators creating new GPOs.
-
-Some potential uses for a template include the following:
-
-- Create a security baseline that your organization can reuse across domains.
-
-- Create a template to manage folder redirection and offline files that your organization can customize for each department.
-
-- Create a wireless networking template that your organization can use to configure wireless network connections for different geographical areas.
-
-- Create regulatory compliance templates for local network administrators.
-
-- Create a read-only snapshot of an existing GPO.
-
-**Note**
-A template is a static version of a GPO that cannot be edited, yet can be used as a starting point for creating new, editable GPOs. Renaming or deleting a template does not affect GPOs created from that template.
-
-
-
-- [Create a Template](create-a-template-agpm40.md)
-
-- [Set a Default Template](set-a-default-template-agpm40.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/creating-a-template-and-setting-a-default-template.md b/mdop/agpm/creating-a-template-and-setting-a-default-template.md
deleted file mode 100644
index 049e02aff3..0000000000
--- a/mdop/agpm/creating-a-template-and-setting-a-default-template.md
+++ /dev/null
@@ -1,38 +0,0 @@
----
-title: Creating a Template and Setting a Default Template
-description: Creating a Template and Setting a Default Template
-author: dansimp
-ms.assetid: 8771b4b5-4dea-4be1-a675-f60cfd3ec5dc
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Creating a Template and Setting a Default Template
-
-
-Creating a template enables you to save all of the settings of a particular version of a Group Policy object (GPO) to use as a starting point for creating new GPOs. As an Editor, you can also specify which of the available templates will be the default template for all Group Policy administrators creating new GPOs.
-
-**Note**
-A template is an uneditable, static version of a GPO for use as a starting point for creating new, editable GPOs. Renaming or deleting a template does not impact GPOs created from that template.
-
-
-
-- [Create a Template](create-a-template.md)
-
-- [Set a Default Template](set-a-default-template.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/creating-controlling-or-importing-a-gpo-agpm30ops.md b/mdop/agpm/creating-controlling-or-importing-a-gpo-agpm30ops.md
deleted file mode 100644
index 5415bea6ec..0000000000
--- a/mdop/agpm/creating-controlling-or-importing-a-gpo-agpm30ops.md
+++ /dev/null
@@ -1,35 +0,0 @@
----
-title: Creating, Controlling, or Importing a GPO
-description: Creating, Controlling, or Importing a GPO
-author: dansimp
-ms.assetid: ce8b232e-7758-4a6a-9e2f-18967da6cdad
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Creating, Controlling, or Importing a GPO
-
-
-To use Advanced Group Policy Management (AGPM) to provide change control for a Group Policy Object (GPO), the GPO must first be controlled by AGPM. New GPOs created through the **Change Control** folder will automatically be controlled. As an Editor, you may not have permission to complete the control, creation, or deletion of a GPO, but you do have the permission necessary to begin the process and submit your request to an Approver.
-
-- [Request Control of an Uncontrolled GPO](request-control-of-an-uncontrolled-gpo-agpm30ops.md)
-
-- [Request the Creation of a New Controlled GPO](request-the-creation-of-a-new-controlled-gpo-agpm30ops.md)
-
-- [Import a GPO from Production](import-a-gpo-from-production-agpm30ops.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/creating-controlling-or-importing-a-gpo-approver.md b/mdop/agpm/creating-controlling-or-importing-a-gpo-approver.md
deleted file mode 100644
index 99e2495711..0000000000
--- a/mdop/agpm/creating-controlling-or-importing-a-gpo-approver.md
+++ /dev/null
@@ -1,37 +0,0 @@
----
-title: Creating, Controlling, or Importing a GPO
-description: Creating, Controlling, or Importing a GPO
-author: dansimp
-ms.assetid: f2c8bef5-b654-4864-99d4-9207cfb0a137
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Creating, Controlling, or Importing a GPO
-
-
-To use Advanced Group Policy Management (AGPM) to provide change control for a Group Policy object (GPO), you must first control the GPO with AGPM. New GPOs created through the **Change Control** node will automatically be controlled.
-
-- [Control a Previously Uncontrolled GPO](control-a-previously-uncontrolled-gpo.md)
-
-- [Create a New Controlled GPO](create-a-new-controlled-gpo.md)
-
-- [Delegate Access to a GPO](delegate-access-to-a-gpo.md)
-
-- [Import a GPO from Production](import-a-gpo-from-production-approver.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/creating-controlling-or-importing-a-gpo-editor-agpm30ops.md b/mdop/agpm/creating-controlling-or-importing-a-gpo-editor-agpm30ops.md
deleted file mode 100644
index 489ce5e692..0000000000
--- a/mdop/agpm/creating-controlling-or-importing-a-gpo-editor-agpm30ops.md
+++ /dev/null
@@ -1,37 +0,0 @@
----
-title: Creating, Controlling, or Importing a GPO
-description: Creating, Controlling, or Importing a GPO
-author: dansimp
-ms.assetid: 0cc1b6ee-3335-4d84-9e1c-d1aefabfef51
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Creating, Controlling, or Importing a GPO
-
-
-To use Advanced Group Policy Management (AGPM) to provide change control for a Group Policy Object (GPO), you must first control the GPO with AGPM. New GPOs created through the **Change Control** folder will automatically be controlled.
-
-- [Control an Uncontrolled GPO](control-an-uncontrolled-gpo-agpm30ops.md)
-
-- [Create a New Controlled GPO](create-a-new-controlled-gpo-agpm30ops.md)
-
-- [Delegate Management of a Controlled GPO](delegate-management-of-a-controlled-gpo-agpm30ops.md)
-
-- [Import a GPO from Production](import-a-gpo-from-production-editor-agpm30ops.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/creating-controlling-or-importing-a-gpo-editor.md b/mdop/agpm/creating-controlling-or-importing-a-gpo-editor.md
deleted file mode 100644
index 39ac25e986..0000000000
--- a/mdop/agpm/creating-controlling-or-importing-a-gpo-editor.md
+++ /dev/null
@@ -1,35 +0,0 @@
----
-title: Creating, Controlling, or Importing a GPO
-description: Creating, Controlling, or Importing a GPO
-author: dansimp
-ms.assetid: 5259ce25-f570-4346-9f50-6b051724a998
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Creating, Controlling, or Importing a GPO
-
-
-To use Advanced Group Policy Management (AGPM) to provide change control for a Group Policy object (GPO), the GPO must first be controlled by AGPM. New GPOs created through the **Change Control** node will automatically be controlled. As an Editor, you may not have permission to complete the control, creation, or deletion of a GPO, but you do have the permission necessary to begin the process and submit your request to an Approver.
-
-- [Request Control of a Previously Uncontrolled GPO](request-control-of-a-previously-uncontrolled-gpo.md)
-
-- [Request the Creation of a New Controlled GPO](request-the-creation-of-a-new-controlled-gpo.md)
-
-- [Import a GPO from Production](import-a-gpo-from-production-editor.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/creating-or-controlling-a-gpo-agpm40-app.md b/mdop/agpm/creating-or-controlling-a-gpo-agpm40-app.md
deleted file mode 100644
index 2206a562b7..0000000000
--- a/mdop/agpm/creating-or-controlling-a-gpo-agpm40-app.md
+++ /dev/null
@@ -1,37 +0,0 @@
----
-title: Creating or Controlling a GPO
-description: Creating or Controlling a GPO
-author: dansimp
-ms.assetid: ca2fa40e-c6e9-4c57-9da1-e5375df4a2fd
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Creating or Controlling a GPO
-
-
-To use Advanced Group Policy Management (AGPM) to provide change control for a Group Policy Object (GPO), you must first control the GPO with AGPM. New GPOs created through the **Change Control** folder will automatically be controlled.
-
-- [Control an Uncontrolled GPO](control-an-uncontrolled-gpo-agpm40.md)
-
-- [Create a New Controlled GPO](create-a-new-controlled-gpo-agpm40.md)
-
-- [Delegate Management of a Controlled GPO](delegate-management-of-a-controlled-gpo-agpm40.md)
-
-- [Import a GPO from Production](import-a-gpo-from-production-agpm40-app.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/creating-or-controlling-a-gpo-agpm40-ed.md b/mdop/agpm/creating-or-controlling-a-gpo-agpm40-ed.md
deleted file mode 100644
index 37b7564e65..0000000000
--- a/mdop/agpm/creating-or-controlling-a-gpo-agpm40-ed.md
+++ /dev/null
@@ -1,35 +0,0 @@
----
-title: Creating or Controlling a GPO
-description: Creating or Controlling a GPO
-author: dansimp
-ms.assetid: 807f3b3f-ad3d-4851-9772-7f54a065632a
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Creating or Controlling a GPO
-
-
-To use Advanced Group Policy Management (AGPM) to provide change control for a Group Policy Object (GPO), the GPO must first be controlled by AGPM. New GPOs created through the **Change Control** folder will automatically be controlled. As an Editor, you may not have permission to complete the control, creation, or deletion of a GPO, but you do have the permission necessary to begin the process and submit your request to an Approver.
-
-- [Request Control of an Uncontrolled GPO](request-control-of-an-uncontrolled-gpo-agpm40.md)
-
-- [Request the Creation of a New Controlled GPO](request-the-creation-of-a-new-controlled-gpo-agpm40.md)
-
-- [Import a GPO from Production](import-a-gpo-from-production-agpm40-ed.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/delegate-access-to-a-gpo.md b/mdop/agpm/delegate-access-to-a-gpo.md
deleted file mode 100644
index 86bb7646c4..0000000000
--- a/mdop/agpm/delegate-access-to-a-gpo.md
+++ /dev/null
@@ -1,51 +0,0 @@
----
-title: Delegate Access to a GPO
-description: Delegate Access to a GPO
-author: dansimp
-ms.assetid: f1d6bb6c-d5bf-4080-a6cb-32774689f804
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Delegate Access to a GPO
-
-
-An Approver can delegate the management of a controlled Group Policy object (GPO) that was **created by that Approver**. Like an AGPM Administrator (Full Control), the Approver can delegate access to such a GPO, so selected Editors can edit it, Reviewers can review it, and other Approvers can approve it. By default, an Approver cannot delegate access to GPOs created by another Group Policy administrator.
-
-A user account with the AGPM Administrator (Full Control) role, the user account of the Approver who created the GPO, or a user account with the necessary permissions in Advanced Group Policy Management is required to complete this procedure. Review the details in "Additional considerations" in this topic.
-
-**To delegate the management of a controlled GPO**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. On the **Contents** tab in the details pane, click the **Controlled** tab to display controlled GPOs, and then click the GPO to delegate.
-
-3. Click the **Add** button, select the users or groups to be permitted access, and then click **OK**.
-
-4. To customize the permissions for each, click the **Advanced** button on the **Contents** tab and check role permissions to allow or deny. (For more detailed control, click **Advanced** in the **Permissions** dialog box.)
-
-5. Click **Apply**, and then click **OK** in the **Permissions** dialog box.
-
-### Additional considerations
-
-- By default, you must be the Approver who created or controlled the GPO or an AGPM Administrator (Full Control) to perform this procedure. Specifically, you must have **List Contents** permission for the domain and **Modify Security** permission for the GPO.
-
-### Additional references
-
-- [Creating, Controlling, or Importing a GPO](creating-controlling-or-importing-a-gpo-approver.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/delegate-access-to-an-individual-gpo-in-the-archive-agpm30ops.md b/mdop/agpm/delegate-access-to-an-individual-gpo-in-the-archive-agpm30ops.md
deleted file mode 100644
index 12617d0f27..0000000000
--- a/mdop/agpm/delegate-access-to-an-individual-gpo-in-the-archive-agpm30ops.md
+++ /dev/null
@@ -1,67 +0,0 @@
----
-title: Delegate Access to an Individual GPO in the Archive
-description: Delegate Access to an Individual GPO in the Archive
-author: dansimp
-ms.assetid: 7b37b188-2b6b-4e52-be97-8ef899e9893b
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Delegate Access to an Individual GPO in the Archive
-
-
-As an AGPM Administrator (Full Control), you can delegate the management of a controlled Group Policy Object (GPO) in the archive so that selected groups and Editors can edit it, Reviewers can review it, and Approvers can approve it.
-
-A user account with the AGPM Administrator (Full Control) role, the user account of the Approver who created the GPO, or a user account with the necessary permissions in Advanced Group Policy Management (AGPM) is required to complete this procedure. Review the details in "Additional considerations" in this topic.
-
-**To delegate the management of a controlled GPO**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. On the **Contents** tab in the details pane, click the **Controlled** tab to display controlled GPOs, and then click the GPO to delegate:
-
- 1. To add access for a user or group, click the **Add** button, select the user or group, and click **OK**. In the **Add Group or User** dialog box, select a role and click **OK**.
-
- 2. To remove access for a user or group, select the user or group, and click the **Remove** button.
-
- **Note**
- If a user or group inherits domain-wide access, the **Remove** button is unavailable. You can modify domain-wide access on the **Domain Delegation** tab.
-
-
-
- 3. To modify the roles and permissions delegated to a user or group, click the **Advanced** button. In the **Permissions** dialog box, select the user or group, select the check box for each role to be assigned to that user or group, and click **OK**.
-
- **Note**
- Editor and Approver include Reviewer permissions.
-
-
-
-### Additional considerations
-
-- By default, you must be the Approver who created or controlled the GPO or an AGPM Administrator (Full Control) to perform this procedure. Specifically, you must have **List Contents** permission for the domain and **Modify Security** permission for the GPO.
-
-- To delegate read access to Group Policy administrators who use AGPM, you must grant them **List Contents** as well as **Read Settings** permissions. This enables them to view GPOs on the **Contents** tab of AGPM. Other permissions must be explicitly delegated.
-
-- Editors must have **Read** permission for the deployed copy of a GPO to make full use of Group Policy Software Installation.
-
-- Membership in the Group Policy Creator Owners group should be restricted, so it is not used to circumvent AGPM management of access to GPOs. (In the **Group Policy Management Console**, click **Group Policy Objects** in the forest and domain in which you want to manage GPOs, click **Delegation**, and then configure the settings to meet the needs of your organization.)
-
-### Additional references
-
-- [Managing the Archive](managing-the-archive.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/delegate-access-to-an-individual-gpo-in-the-archive-agpm40.md b/mdop/agpm/delegate-access-to-an-individual-gpo-in-the-archive-agpm40.md
deleted file mode 100644
index d8d548450f..0000000000
--- a/mdop/agpm/delegate-access-to-an-individual-gpo-in-the-archive-agpm40.md
+++ /dev/null
@@ -1,67 +0,0 @@
----
-title: Delegate Access to an Individual GPO in the Archive
-description: Delegate Access to an Individual GPO in the Archive
-author: dansimp
-ms.assetid: 284d2aa2-7c10-4ffa-8978-bbe30867c1c1
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Delegate Access to an Individual GPO in the Archive
-
-
-As an AGPM Administrator (Full Control), you can delegate the management of a controlled Group Policy Object (GPO) in the archive so that selected groups and Editors can edit it, Reviewers can review it, and Approvers can approve it.
-
-A user account with the AGPM Administrator (Full Control) role, the user account of the Approver who created the GPO, or a user account with the necessary permissions in Advanced Group Policy Management (AGPM) is required to complete this procedure. Review the details in "Additional considerations" in this topic.
-
-**To delegate the management of a controlled GPO**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. On the **Contents** tab in the details pane, click the **Controlled** tab to display controlled GPOs, and then click the GPO to delegate:
-
- 1. To add access for a user or group, click the **Add** button, select the user or group, and click **OK**. In the **Add Group or User** dialog box, select a role and click **OK**.
-
- 2. To remove access for a user or group, select the user or group, and click the **Remove** button.
-
- **Note**
- If a user or group inherits domain-wide access, the **Remove** button is unavailable. You can modify domain-wide access on the **Domain Delegation** tab.
-
-
-
- 3. To modify the roles and permissions delegated to a user or group, click the **Advanced** button. In the **Permissions** dialog box, select the user or group, select the check box for each role to be assigned to that user or group, and click **OK**.
-
- **Note**
- Editor and Approver include Reviewer permissions.
-
-
-
-### Additional considerations
-
-- By default, you must be the Approver who created or controlled the GPO or an AGPM Administrator (Full Control) to perform this procedure. Specifically, you must have **List Contents** permission for the domain and **Modify Security** permission for the GPO.
-
-- To delegate read access to Group Policy administrators who use AGPM, you must grant them **List Contents** as well as **Read Settings** permissions. This enables them to view GPOs on the **Contents** tab of AGPM. Other permissions must be explicitly delegated.
-
-- Editors must have **Read** permission for the deployed copy of a GPO to make full use of Group Policy Software Installation.
-
-- Membership in the Group Policy Creator Owners group should be restricted, so it is not used to circumvent AGPM management of access to GPOs. (In the **Group Policy Management Console**, click **Group Policy Objects** in the forest and domain in which you want to manage GPOs, click **Delegation**, and then configure the settings to meet the needs of your organization.)
-
-### Additional references
-
-- [Managing the Archive](managing-the-archive-agpm40.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/delegate-access-to-an-individual-gpo.md b/mdop/agpm/delegate-access-to-an-individual-gpo.md
deleted file mode 100644
index ef1ebe53fa..0000000000
--- a/mdop/agpm/delegate-access-to-an-individual-gpo.md
+++ /dev/null
@@ -1,57 +0,0 @@
----
-title: Delegate Access to an Individual GPO
-description: Delegate Access to an Individual GPO
-author: dansimp
-ms.assetid: b2a7d550-14bf-4b41-b6e4-2cc091eedd2d
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Delegate Access to an Individual GPO
-
-
-As an AGPM Administrator (Full Control), you can delegate the management of a controlled Group Policy object (GPO), so selected groups and Editors can edit it, Reviewers can review it, and Approvers can approve it.
-
-A user account with the AGPM Administrator (Full Control) role, the user account of the Approver who created the GPO, or a user account with the necessary permissions in Advanced Group Policy Management is required to complete this procedure. Review the details in "Additional considerations" in this topic.
-
-**To delegate the management of a controlled GPO**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. On the **Contents** tab in the details pane, click the **Controlled** tab to display controlled GPOs, and then click the GPO to delegate.
-
-3. Click the **Add** button, select the users or groups to be permitted access, and then click **OK**.
-
-4. To customize the permissions for each user or group, click the **Advanced** button on the **Contents** tab and check role permissions to allow or deny. (For more detailed control, click **Advanced** in the **Permissions** dialog box.)
-
-5. Click **Apply**, and then click **OK** in the **Permissions** dialog box.
-
-### Additional considerations
-
-- By default, you must be the Approver who created or controlled the GPO or an AGPM Administrator (Full Control) to perform this procedure. Specifically, you must have **List Contents** permission for the domain and **Modify Security** permission for the GPO.
-
-- To delegate read access to Group Policy administrators who use AGPM, you must grant them **List Contents** as well as **Read Settings** permissions. This enables them to view GPOs on the **Contents** tab of AGPM. Set the permission to apply to **This object and nested objects**. Other permissions must be explicitly delegated.
-
-- Editors must have **Read** permission for the deployed copy of a GPO to make full use of Group Policy Software Installation.
-
-- Membership in the Group Policy Creator Owners group should be restricted so that it is not used to circumvent AGPM management of access to GPOs. (In the **Group Policy Management Console**, click **Group Policy Objects** in the forest and domain in which you want to manage GPOs, click **Delegation**, and then configure the settings to meet the needs of your organization.)
-
-### Additional references
-
-- [Performing AGPM Administrator Tasks](performing-agpm-administrator-tasks.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/delegate-access-to-the-production-environment-agpm30ops.md b/mdop/agpm/delegate-access-to-the-production-environment-agpm30ops.md
deleted file mode 100644
index 6a0eaaf9c7..0000000000
--- a/mdop/agpm/delegate-access-to-the-production-environment-agpm30ops.md
+++ /dev/null
@@ -1,107 +0,0 @@
----
-title: Delegate Access to the Production Environment
-description: Delegate Access to the Production Environment
-author: dansimp
-ms.assetid: c1ebae2e-909b-4e64-b368-b7d3cc67b1eb
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Delegate Access to the Production Environment
-
-
-You can change access to Group Policy Objects (GPOs) in the production environment, replacing any existing permissions on those GPOs. You can configure permissions at the domain level to either allow or prevent users from editing, deleting, or modifying the security of GPOs in the production environment when they are not using the **Change Control** folder in the Group Policy Management Console (GPMC).
-
-**Note**
-- Delegating access to the production environment does not affect users’ ability to link GPOs.
-
-- When GPOs are controlled or deployed, access for any other accounts except those with **Read** and **Apply** permissions is removed.
-
-
-
-A user account that has either the necessary permissions in Advanced Group Policy Management (AGPM) or the role of AGPM Administrator (Full Control) is required to complete this procedure. Review the details in "Additional considerations" in this topic.
-
-**To change access to GPOs in the production environment**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. Click the **Production Delegation** tab.
-
-3. To add permissions for a user or group that does not have access to the production environment, or to replace the permissions for a user or group that does have access:
-
- 1. Click **Add**, select a user or group, and then click **OK**.
-
- 2. Select permissions to delegate to that user or group for the production environment, and then click **OK**.
-
-4. To remove all permissions to the production environment for a user or group, select the user or group, click **Remove**, and then click **OK**.
-
-### Additional considerations
-
-- By default, you must be an AGPM Administrator (Full Control) to perform this procedure. Specifically, you must have **Modify Security** permission for the domain.
-
-- Permissions for the AGPM Service Account cannot be changed on the **Production Delegation** tab.
-
-- By default, the following accounts have permissions for GPOs in the production environment:
-
-
-
-
-
-
-
-
-
Account
-
Default Permissions for GPOs
-
-
-
-
-
<AGPM Service Account>
-
Edit Settings, Delete, Modify Security
-
-
-
Authenticated Users
-
Read, Apply
-
-
-
Domain Admins
-
Edit Settings, Delete, Modify Security
-
-
-
Enterprise Admins
-
Edit Settings, Delete, Modify Security
-
-
-
Enterprise Domain Controllers
-
Read
-
-
-
System
-
Edit Settings, Delete, Modify Security
-
-
-
-
-
-
-- Membership in the Group Policy Creator Owners group should be restricted, so it is not used to circumvent AGPM management of access to GPOs. (In the **Group Policy Management Console**, click **Group Policy Objects** in the forest and domain in which you want to manage GPOs, click **Delegation**, and then configure the settings to meet the needs of your organization.)
-
-### Additional references
-
-- [Configuring Advanced Group Policy Management](configuring-advanced-group-policy-management.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/delegate-access-to-the-production-environment-agpm40.md b/mdop/agpm/delegate-access-to-the-production-environment-agpm40.md
deleted file mode 100644
index 79476c9882..0000000000
--- a/mdop/agpm/delegate-access-to-the-production-environment-agpm40.md
+++ /dev/null
@@ -1,107 +0,0 @@
----
-title: Delegate Access to the Production Environment
-description: Delegate Access to the Production Environment
-author: dansimp
-ms.assetid: 4c670581-8c47-41ea-80eb-02846ff1ec1f
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Delegate Access to the Production Environment
-
-
-In Advanced Group Policy Management (AGPM), you can change access to Group Policy Objects (GPOs) in the production environment of the domain, replacing any existing permissions on those GPOs. You can configure permissions at the domain level to either allow or prevent users from editing, deleting, or modifying the security of GPOs in the production environment when they are not using the **Change Control** folder in the Group Policy Management Console (GPMC).
-
-**Note**
-- Changing how access to the production environment is delegated does not affect users' ability to link GPOs.
-
-- When GPOs are controlled or deployed, access for any other accounts except those with **Read** and **Apply** permissions is removed.
-
-
-
-A user account that has either the role of AGPM Administrator (Full Control) or the necessary permissions in Advanced Group Policy Management (AGPM) is required to complete this procedure. Review the details in "Additional considerations" in this topic.
-
-**To change access to GPOs in the production environment of the domain**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. Click the **Production Delegation** tab.
-
-3. To add permissions for a user or group that does not have access to the production environment, or to replace the permissions for a user or group that does have access:
-
- 1. Click **Add**, select a user or group, and then click **OK**.
-
- 2. Select permissions to delegate to that user or group for the production environment, and then click **OK**.
-
-4. To remove all permissions to the production environment for a user or group, select the user or group, click **Remove**, and then click **OK**.
-
-### Additional considerations
-
-- By default, you must be an AGPM Administrator (Full Control) to perform this procedure. Specifically, you must have **Modify Security** permission for the domain.
-
-- Permissions for the AGPM Service Account cannot be changed on the **Production Delegation** tab.
-
-- By default, the following accounts have permissions for GPOs in the production environment:
-
-
-
-
-
-
-
-
-
Account
-
Default Permissions for GPOs
-
-
-
-
-
<AGPM Service Account>
-
Edit Settings, Delete, Modify Security
-
-
-
Authenticated Users
-
Read, Apply
-
-
-
Domain Admins
-
Edit Settings, Delete, Modify Security
-
-
-
Enterprise Admins
-
Edit Settings, Delete, Modify Security
-
-
-
Enterprise Domain Controllers
-
Read
-
-
-
System
-
Edit Settings, Delete, Modify Security
-
-
-
-
-
-
-- Membership in the Group Policy Creator Owners group should be restricted, so it is not used to circumvent AGPM management of access to GPOs. (In the **Group Policy Management Console**, click **Group Policy Objects** in the forest and domain in which you want to manage GPOs, click **Delegation**, and then configure the settings to meet the needs of your organization.)
-
-### Additional references
-
-- [Configuring Advanced Group Policy Management](configuring-advanced-group-policy-management-agpm40.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/delegate-domain-level-access-to-the-archive-agpm30ops.md b/mdop/agpm/delegate-domain-level-access-to-the-archive-agpm30ops.md
deleted file mode 100644
index 367806c7ef..0000000000
--- a/mdop/agpm/delegate-domain-level-access-to-the-archive-agpm30ops.md
+++ /dev/null
@@ -1,62 +0,0 @@
----
-title: Delegate Domain-Level Access to the Archive
-description: Delegate Domain-Level Access to the Archive
-author: dansimp
-ms.assetid: d232069e-71d5-4b4d-b22e-bef11de1cfd4
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Delegate Domain-Level Access to the Archive
-
-
-Set up delegation for your environment so that Group Policy administrators have the appropriate access to and control over Group Policy Objects (GPOs) in the archive. There are baseline permissions you can apply to make operation more efficient. You can grant permissions in any manner that meets the needs of your organization.
-
-A user account with the AGPM Administrator (Full Control) role or necessary permissions in Advanced Group Policy Management (AGPM) is required to complete this procedure. Review the details in "Additional considerations" in this topic.
-
-**To delegate access so that users and groups have appropriate permissions to all GPOs throughout a domain**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. Click the **Domain Delegation** tab, and configure access to all GPOs in the domain:
-
- 1. To add access for a user or group, click the **Add** button, select the user or group, and click **OK**. In the **Add Group or User** dialog box, select a role and click **OK**.
-
- 2. To remove access for a user or group, select the user or group, and click the **Remove** button.
-
- 3. To modify the roles and permissions delegated to a user or group, select click the **Advanced** button. In the **Permissions** dialog box, select the user or group, select the check box for each role to be assigned to that user or group, and then click **OK**.
-
- **Note**
- Editor and Approver include Reviewer permissions.
-
-
-
-### Additional considerations
-
-- By default, you must be an AGPM Administrator (Full Control) to perform this procedure. Specifically, you must have **Modify Security** permission for the domain.
-
-- To delegate read access to Group Policy administrators who use AGPM, you must grant them **List Contents** as well as **Read Settings** permissions. This enables them to view GPOs on the **Contents** tab of AGPM. Other permissions must be explicitly delegated.
-
-- Editors must be granted **Read** permission for the deployed copy of a GPO to make full use of Group Policy Software Installation.
-
-- Membership in the Group Policy Creator Owners group should be restricted, so it is not used to circumvent AGPM management of access to GPOs. (In the **Group Policy Management Console**, click **Group Policy Objects** in the forest and domain in which you want to manage GPOs, click **Delegation**, and then configure the settings to meet the needs of your organization.)
-
-### Additional references
-
-- [Managing the Archive](managing-the-archive.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/delegate-domain-level-access-to-the-archive-agpm40.md b/mdop/agpm/delegate-domain-level-access-to-the-archive-agpm40.md
deleted file mode 100644
index 2a6a673529..0000000000
--- a/mdop/agpm/delegate-domain-level-access-to-the-archive-agpm40.md
+++ /dev/null
@@ -1,62 +0,0 @@
----
-title: Delegate Domain-Level Access to the Archive
-description: Delegate Domain-Level Access to the Archive
-author: dansimp
-ms.assetid: 11ca1d40-4b5c-496e-8922-d01412717858
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Delegate Domain-Level Access to the Archive
-
-
-Set up delegation for your environment so that Group Policy administrators have the appropriate access to and control over Group Policy Objects (GPOs) in the archive. There are baseline permissions you can apply to make operation more efficient. You can grant permissions in any manner that meets the needs of your organization.
-
-A user account with the AGPM Administrator (Full Control) role or necessary permissions in Advanced Group Policy Management (AGPM) is required to complete this procedure. Review the details in "Additional considerations" in this topic.
-
-**To delegate access so that users and groups have appropriate permissions to all GPOs throughout a domain**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. Click the **Domain Delegation** tab, and configure access to all GPOs in the domain:
-
- 1. To add access for a user or group, click the **Add** button, select the user or group, and click **OK**. In the **Add Group or User** dialog box, select a role and click **OK**.
-
- 2. To remove access for a user or group, select the user or group, and click the **Remove** button.
-
- 3. To modify the roles and permissions delegated to a user or group, select click the **Advanced** button. In the **Permissions** dialog box, select the user or group, select the check box for each role to be assigned to that user or group, and then click **OK**.
-
- **Note**
- Editor and Approver include Reviewer permissions.
-
-
-
-### Additional considerations
-
-- By default, you must be an AGPM Administrator (Full Control) to perform this procedure. Specifically, you must have **Modify Security** permission for the domain.
-
-- To delegate read access to Group Policy administrators who use AGPM, you must grant them **List Contents** as well as **Read Settings** permissions. This enables them to view GPOs on the **Contents** tab of AGPM. Other permissions must be explicitly delegated.
-
-- Editors must be granted **Read** permission for the deployed copy of a GPO to make full use of Group Policy Software Installation.
-
-- Membership in the Group Policy Creator Owners group should be restricted, so it is not used to circumvent AGPM management of access to GPOs. (In the **Group Policy Management Console**, click **Group Policy Objects** in the forest and domain in which you want to manage GPOs, click **Delegation**, and then configure the settings to meet the needs of your organization.)
-
-### Additional references
-
-- [Managing the Archive](managing-the-archive-agpm40.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/delegate-domain-level-access.md b/mdop/agpm/delegate-domain-level-access.md
deleted file mode 100644
index 3facfda7f0..0000000000
--- a/mdop/agpm/delegate-domain-level-access.md
+++ /dev/null
@@ -1,66 +0,0 @@
----
-title: Delegate Domain-Level Access
-description: Delegate Domain-Level Access
-author: dansimp
-ms.assetid: 64c8e773-38cc-4991-9ed2-5a801094d06e
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Delegate Domain-Level Access
-
-
-Set up delegation for your environment so Group Policy administrators have the appropriate access to and control over Group Policy objects (GPOs). There are baseline permissions you can apply to make the operation of Advanced Group Policy Management (AGPM) more efficient. You can grant permissions in any manner that meets the needs of your organization.
-
-A user account with the AGPM Administrator (Full Control) role or necessary permissions in Advanced Group Policy Management is required to complete this procedure. Review the details in "Additional considerations" in this topic.
-
-**To delegate access so users and groups have appropriate permissions to all GPOs throughout a domain**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. Click the **Domain Delegation** tab, then click the **Advanced** button.
-
-3. In the **Permissions** dialog box, click the check box for each role to be assigned to an individual, and then click the **Advanced** button.
-
- **Note**
- Editor and Approver include Reviewer permissions.
-
-
-
-4. In the **Advanced Security Settings** dialog box, select a Group Policy administrator, and then click **Edit**.
-
-5. For **Apply onto**, select **This object and nested objects**, configure any special permissions beyond the standard AGPM roles, then click **OK** in the **Permission** **Entry** dialog box.
-
-6. In the **Advanced Security Settings** dialog box, click **OK**.
-
-7. In the **Permissions** dialog box, click **OK**.
-
-### Additional considerations
-
-- By default, you must be an AGPM Administrator (Full Control) to perform this procedure. Specifically, you must have **Modify Security** permission for the domain.
-
-- To delegate read access to Group Policy administrators who use AGPM, you must grant them **List Contents** as well as **Read Settings** permissions. This enables them to view GPOs on the **Contents** tab of AGPM. Set the permission to apply to **This object and nested objects**. Other permissions must be explicitly delegated.
-
-- Editors must be granted **Read** permission for the deployed copy of a GPO to make full use of Group Policy Software Installation.
-
-- Membership in the Group Policy Creator Owners group should be restricted so that it is not used to circumvent AGPM management of access to GPOs. (In the **Group Policy Management Console**, click **Group Policy Objects** in the forest and domain in which you want to manage GPOs, click **Delegation**, and then configure the settings to meet the needs of your organization.)
-
-### Additional references
-
-- [Performing AGPM Administrator Tasks](performing-agpm-administrator-tasks.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/delegate-management-of-a-controlled-gpo-agpm30ops.md b/mdop/agpm/delegate-management-of-a-controlled-gpo-agpm30ops.md
deleted file mode 100644
index 20c4c7176a..0000000000
--- a/mdop/agpm/delegate-management-of-a-controlled-gpo-agpm30ops.md
+++ /dev/null
@@ -1,65 +0,0 @@
----
-title: Delegate Management of a Controlled GPO
-description: Delegate Management of a Controlled GPO
-author: dansimp
-ms.assetid: 509b02e7-ce0b-4919-b58a-c3a33051152e
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Delegate Management of a Controlled GPO
-
-
-An Approver can delegate the management of a controlled Group Policy Object (GPO) that was created by that Approver. Like an AGPM Administrator (Full Control), the Approver can delegate access to such a GPO so that selected Editors can edit it, Reviewers can review it, and other Approvers can approve it. By default, an Approver cannot delegate access to GPOs created by another Group Policy administrator.
-
-A user account with the AGPM Administrator (Full Control) role, the user account of the Approver who created the GPO, or a user account with the necessary permissions in Advanced Group Policy Management (AGPM) is required to complete this procedure. Review the details in "Additional considerations" in this topic.
-
-**To delegate the management of a controlled GPO**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. On the **Contents** tab in the details pane, click the **Controlled** tab to display controlled GPOs, and then click the GPO to delegate:
-
- 1. To add access for a user or group, click the **Add** button, select the user or group, and click **OK**. In the **Add Group or User** dialog box, select a role and click **OK**.
-
- 2. To remove access for a user or group, select the user or group, and then click the **Remove** button.
-
- **Note**
- If a user or group inherits domain-wide access, the **Remove** button is unavailable. You can modify domain-wide access on the **Domain Delegation** tab.
-
-
-
- 3. To modify the roles and permissions delegated to a user or group, click the **Advanced** button. In the **Permissions** dialog box, select the user or group, select the check box for each role to be assigned to that user or group, and then click **OK**.
-
- **Note**
- Editor and Approver include Reviewer permissions.
-
-
-
-### Additional considerations
-
-- By default, you must be the Approver who created or controlled the GPO or an AGPM Administrator (Full Control) to perform this procedure. Specifically, you must have **List Contents** permission for the domain and **Modify Security** permission for the GPO.
-
-- To delegate read access to Group Policy administrators who use AGPM, you must grant them **List Contents** as well as **Read Settings** permissions. This enables them to view GPOs on the **Contents** tab of AGPM. Other permissions must be explicitly delegated.
-
-- Editors must have **Read** permission for the deployed copy of a GPO to make full use of Group Policy Software Installation.
-
-### Additional references
-
-- [Creating, Controlling, or Importing a GPO](creating-controlling-or-importing-a-gpo-editor-agpm30ops.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/delegate-management-of-a-controlled-gpo-agpm40.md b/mdop/agpm/delegate-management-of-a-controlled-gpo-agpm40.md
deleted file mode 100644
index 6401b24ac5..0000000000
--- a/mdop/agpm/delegate-management-of-a-controlled-gpo-agpm40.md
+++ /dev/null
@@ -1,65 +0,0 @@
----
-title: Delegate Management of a Controlled GPO
-description: Delegate Management of a Controlled GPO
-author: dansimp
-ms.assetid: 96b4bfb3-5657-4267-8326-85d7a0db87ce
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Delegate Management of a Controlled GPO
-
-
-An Approver can delegate the management of a controlled Group Policy Object (GPO) that was created by that Approver. Like an AGPM Administrator (Full Control), the Approver can delegate access to such a GPO so that selected Editors can edit it, Reviewers can review it, and other Approvers can approve it. By default, an Approver cannot delegate access to GPOs created by another Group Policy administrator.
-
-A user account with the AGPM Administrator (Full Control) role, the user account of the Approver who created the GPO, or a user account with the necessary permissions in Advanced Group Policy Management (AGPM) is required to complete this procedure. Review the details in "Additional considerations" in this topic.
-
-**To delegate the management of a controlled GPO**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. On the **Contents** tab in the details pane, click the **Controlled** tab to display controlled GPOs, and then click the GPO to delegate:
-
- 1. To add access for a user or group, click the **Add** button, select the user or group, and click **OK**. In the **Add Group or User** dialog box, select a role and click **OK**.
-
- 2. To remove access for a user or group, select the user or group, and then click the **Remove** button.
-
- **Note**
- If a user or group inherits domain-wide access, the **Remove** button is unavailable. You can modify domain-wide access on the **Domain Delegation** tab.
-
-
-
- 3. To modify the roles and permissions delegated to a user or group, click the **Advanced** button. In the **Permissions** dialog box, select the user or group, select the check box for each role to be assigned to that user or group, and then click **OK**.
-
- **Note**
- Editor and Approver include Reviewer permissions.
-
-
-
-### Additional considerations
-
-- By default, you must be the Approver who created or controlled the GPO or an AGPM Administrator (Full Control) to perform this procedure. Specifically, you must have **List Contents** permission for the domain and **Modify Security** permission for the GPO.
-
-- To delegate read access to Group Policy administrators who use AGPM, you must grant them **List Contents** as well as **Read Settings** permissions. This enables them to view GPOs on the **Contents** tab of AGPM. Other permissions must be explicitly delegated.
-
-- Editors must have **Read** permission for the deployed copy of a GPO to make full use of Group Policy Software Installation.
-
-### Additional references
-
-- [Creating or Controlling a GPO](creating-or-controlling-a-gpo-agpm40-app.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/delete-a-controlled-gpo-agpm30ops.md b/mdop/agpm/delete-a-controlled-gpo-agpm30ops.md
deleted file mode 100644
index 15a7b0ca84..0000000000
--- a/mdop/agpm/delete-a-controlled-gpo-agpm30ops.md
+++ /dev/null
@@ -1,57 +0,0 @@
----
-title: Delete a Controlled GPO
-description: Delete a Controlled GPO
-author: dansimp
-ms.assetid: f51c1737-c116-4faf-a6f6-c72303f60a3b
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Delete a Controlled GPO
-
-
-Approvers can delete a controlled Group Policy Object (GPO), moving it to the Recycle Bin.
-
-A user account with the Approver or AGPM Administrator (Full Control) role or necessary permissions in Advanced Group Policy Management (AGPM) is required to complete this procedure. Review the details in "Additional considerations" in this topic.
-
-**To delete a controlled GPO**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. On the **Contents** tab, click the **Controlled** tab to display the controlled GPOs.
-
-3. Right-click the GPO you want to delete, and then click **Delete**.
-
- - To delete the GPO from the archive while leaving the deployed version of the GPO untouched in the production environment, click **Delete GPO from archive only**.
-
- - To delete the GPO from both the archive and production environment, click **Delete GPO from archive and production**.
-
-4. Type a comment to be displayed in the audit trail for the GPO, and then click **OK**.
-
-5. When the **Progress** window indicates that overall progress is complete, click **Close**. The GPO is removed from the **Controlled** tab and is displayed on the **Recycle Bin** tab, where it can be restored or destroyed. If the GPO was deleted only from the archive, it is also displayed on the **Uncontrolled** tab.
-
-### Additional considerations
-
-- By default, you must be an Approver or an AGPM Administrator (Full Control) to perform this procedure. Specifically, you must have **List Contents** and **Delete GPO** permissions for the GPO.
-
-- To delete an uncontrolled GPO from the production environment without first controlling it, in the **Group Policy Management Console**, click **Forest**, click **Domains**, click **<MyDomain>**, and then click **Group Policy Objects**. Right-click the uncontrolled GPO, and then click **Delete**.
-
-### Additional references
-
-- [Deleting, Restoring, or Destroying a GPO](deleting-restoring-or-destroying-a-gpo-agpm30ops.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/delete-a-controlled-gpo-agpm40.md b/mdop/agpm/delete-a-controlled-gpo-agpm40.md
deleted file mode 100644
index df8fd91963..0000000000
--- a/mdop/agpm/delete-a-controlled-gpo-agpm40.md
+++ /dev/null
@@ -1,57 +0,0 @@
----
-title: Delete a Controlled GPO
-description: Delete a Controlled GPO
-author: dansimp
-ms.assetid: 2a461018-aa0b-4ae3-b079-efc554ca4a3d
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Delete a Controlled GPO
-
-
-Approvers can delete a controlled Group Policy Object (GPO), moving it to the Recycle Bin.
-
-A user account with the Approver or AGPM Administrator (Full Control) role or necessary permissions in Advanced Group Policy Management (AGPM) is required to complete this procedure. Review the details in "Additional considerations" in this topic.
-
-**To delete a controlled GPO**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. On the **Contents** tab, click the **Controlled** tab to display the controlled GPOs.
-
-3. Right-click the GPO you want to delete, and then click **Delete**.
-
- - To delete the GPO from the archive while leaving the deployed version of the GPO untouched in the production environment, click **Delete GPO from archive only**.
-
- - To delete the GPO from both the archive and production environment of the domain, click **Delete GPO from archive and production**.
-
-4. Type a comment to be displayed in the audit trail for the GPO, and then click **OK**.
-
-5. When the **Progress** window indicates that overall progress is complete, click **Close**. The GPO is removed from the **Controlled** tab and is displayed on the **Recycle Bin** tab, where it can be restored or destroyed. If the GPO was deleted only from the archive, it is also displayed on the **Uncontrolled** tab.
-
-### Additional considerations
-
-- By default, you must be an Approver or an AGPM Administrator (Full Control) to perform this procedure. Specifically, you must have **List Contents** and **Delete GPO** permissions for the GPO.
-
-- To delete an uncontrolled GPO from the production environment without first controlling it, in the **Group Policy Management Console**, click **Forest**, click **Domains**, click **<MyDomain>**, and then click **Group Policy Objects**. Right-click the uncontrolled GPO, and then click **Delete**.
-
-### Additional references
-
-- [Deleting, Restoring, or Destroying a GPO](deleting-restoring-or-destroying-a-gpo-agpm40.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/delete-a-gpo-approver.md b/mdop/agpm/delete-a-gpo-approver.md
deleted file mode 100644
index b690ae67d6..0000000000
--- a/mdop/agpm/delete-a-gpo-approver.md
+++ /dev/null
@@ -1,59 +0,0 @@
----
-title: Delete a GPO
-description: Delete a GPO
-author: dansimp
-ms.assetid: 85fca371-5707-49c1-aa51-813fc3a58dfc
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Delete a GPO
-
-
-Advanced Group Policy Management (AGPM) enables Approvers to delete a controlled Group Policy object (GPO), moving it to the Recycle Bin.
-
-A user account with the Approver or AGPM Administrator (Full Control) role or necessary permissions in Advanced Group Policy Management is required to complete this procedure. Review the details in "Additional considerations" in this topic.
-
-**To delete a controlled GPO**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. On the **Contents** tab, click the **Controlled** tab to display the controlled GPOs.
-
-3. Right-click the GPO to delete, and then click **Delete**.
-
- - To delete the GPO from the archive while leaving the deployed version of the GPO untouched in the production environment, click **Delete GPO from archive only (uncontrol)**.
-
- - To delete the GPO from both the archive and production environment, click **Delete GPO from archive and production**.
-
-4. Type a comment to be displayed in the audit trail for the GPO, and then click **OK**.
-
-5. When the **Progress** window indicates that overall progress is complete, click **Close**. The GPO is removed from the **Controlled** tab and is displayed on the **Recycle Bin** tab, where it can be restored or destroyed. If the GPO was deleted only from the archive, it is also displayed on the **Uncontrolled** tab.
-
-### Additional considerations
-
-- By default, you must be an Approver or an AGPM Administrator (Full Control) to delete a deployed GPO. Specifically, you must have **List Contents** and **Delete GPO** permissions for the GPO.
-
-- By default, you must be an Editor, an Approver, or an AGPM Administrator (Full Control) to delete a GPO from the archive. Specifically, you must have **List Contents** and either **Edit Settings** or **Delete GPO** permissions for the GPO.
-
-- To delete an uncontrolled GPO from the production environment without first controlling it, in the **Group Policy Management Console**, click **Forest**, click **Domains**, click **<MyDomain>**, and then click **Group Policy Objects**. Right-click the uncontrolled GPO, and then click **Delete**.
-
-### Additional references
-
-- [Deleting, Restoring, or Destroying a GPO](deleting-restoring-or-destroying-a-gpo.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/delete-a-gpo-editor.md b/mdop/agpm/delete-a-gpo-editor.md
deleted file mode 100644
index 151980b771..0000000000
--- a/mdop/agpm/delete-a-gpo-editor.md
+++ /dev/null
@@ -1,61 +0,0 @@
----
-title: Delete a GPO
-description: Delete a GPO
-author: dansimp
-ms.assetid: 66be3dde-653e-4c25-8cb7-00e7090c8d31
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Delete a GPO
-
-
-As an Editor, you may not have permission to complete the deletion of a Group Policy object (GPO), but you do have the permission necessary to begin the process and submit your request to an Approver.
-
-A user account with the Editor role or necessary permissions in Advanced Group Policy Management is required to complete this procedure. Review the details in "Additional considerations" in this topic.
-
-**To request the deletion of a controlled GPO**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. On the **Contents** tab, click the **Controlled** tab to display the controlled GPOs.
-
-3. Right-click the GPO to delete, and then click **Delete**.
-
- - To delete the GPO from the archive while leaving the deployed version of the GPO untouched in the production environment, click **Delete GPO from archive only (uncontrol)**.
-
- - To delete the GPO from both the archive and production environment, click **Delete GPO from archive and production**.
-
- Unless you have special permission to delete GPOs, you must submit a request for deletion of the deployed GPO. To receive a copy of the request, type your e-mail address in the **Cc** field. Type a comment to be displayed in the audit trail for the GPO, and then click **Submit**.
-
-4. When the **Progress** window indicates that overall progress is complete, click **Close**. The GPO is displayed on the list of GPOs on the **Pending** tab. When an Approver has approved your request, the GPO will be moved from the **Pending** tab to the **Recycle Bin** tab, where it can be restored or destroyed.
-
-### Additional considerations
-
-- By default, you must be an Editor to request the deletion of a deployed GPO. Specifically, you must have **List Contents** and **Edit Settings** permissions for the GPO.
-
-- By default, you must be an Editor, an Approver, or an AGPM Administrator (Full Control) to delete a GPO from the archive. Specifically, you must have **List Contents** and either **Edit Settings** or **Delete GPO** permissions for the GPO.
-
-- To withdraw your request before it has been approved, click the **Pending** tab. Right-click the GPO, and then click **Withdraw**. The GPO will be returned to the **Controlled** tab.
-
-- To delete an uncontrolled GPO from the production environment without first controlling it, in the **Group Policy Management Console**, click **Forest**, click **Domains**, click **<MyDomain>**, and then click **Group Policy Objects**. Right-click the uncontrolled GPO, and then click **Delete**.
-
-### Additional references
-
-- [Performing Editor Tasks](performing-editor-tasks.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/deleting-or-restoring-a-gpo-agpm30ops.md b/mdop/agpm/deleting-or-restoring-a-gpo-agpm30ops.md
deleted file mode 100644
index b50eaff2eb..0000000000
--- a/mdop/agpm/deleting-or-restoring-a-gpo-agpm30ops.md
+++ /dev/null
@@ -1,33 +0,0 @@
----
-title: Deleting or Restoring a GPO
-description: Deleting or Restoring a GPO
-author: dansimp
-ms.assetid: ee4a467a-187a-48e3-8f0d-548de0606a56
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Deleting or Restoring a GPO
-
-
-To use Advanced Group Policy Management (AGPM) to delete a Group Policy Object (GPO) from the archive or restore a deleted GPO from the Recycle Bin, the GPO must be controlled by AGPM. As an Editor, you may not have permission to complete the deletion or restoration of a GPO, but you do have the permission necessary to begin the process and submit your request to an Approver.
-
-- [Request Deletion of a GPO](request-deletion-of-a-gpo-agpm30ops.md)
-
-- [Request Restoration of a Deleted GPO](request-restoration-of-a-deleted-gpo-agpm30ops.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/deleting-or-restoring-a-gpo-agpm40.md b/mdop/agpm/deleting-or-restoring-a-gpo-agpm40.md
deleted file mode 100644
index f45ac8dc42..0000000000
--- a/mdop/agpm/deleting-or-restoring-a-gpo-agpm40.md
+++ /dev/null
@@ -1,33 +0,0 @@
----
-title: Deleting or Restoring a GPO
-description: Deleting or Restoring a GPO
-author: dansimp
-ms.assetid: d4f92f4d-eba7-4e6e-b166-13670864d298
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Deleting or Restoring a GPO
-
-
-To use Advanced Group Policy Management (AGPM) to delete a Group Policy Object (GPO) from the archive or restore a deleted GPO from the Recycle Bin, the GPO must be controlled by AGPM. As an Editor, you may not have permission to complete the deletion or restoration of a GPO, but you do have the permission necessary to begin the process and submit your request to an Approver.
-
-- [Request Deletion of a GPO](request-deletion-of-a-gpo-agpm40.md)
-
-- [Request Restoration of a Deleted GPO](request-restoration-of-a-deleted-gpo-agpm40.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/deleting-restoring-or-destroying-a-gpo-agpm30ops.md b/mdop/agpm/deleting-restoring-or-destroying-a-gpo-agpm30ops.md
deleted file mode 100644
index 2c2c5983b2..0000000000
--- a/mdop/agpm/deleting-restoring-or-destroying-a-gpo-agpm30ops.md
+++ /dev/null
@@ -1,35 +0,0 @@
----
-title: Deleting, Restoring, or Destroying a GPO
-description: Deleting, Restoring, or Destroying a GPO
-author: dansimp
-ms.assetid: 3e1b862e-007a-4b60-900f-0489069f5c75
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Deleting, Restoring, or Destroying a GPO
-
-
-As an Approver, you can delete a Group Policy Object (GPO) (moving it to the Recycle Bin), restore a GPO from the Recycle Bin (returning it to the archive), or destroy a GPO (permanently deleting it so that it can no longer be restored).
-
-- [Delete a Controlled GPO](delete-a-controlled-gpo-agpm30ops.md)
-
-- [Restore a Deleted GPO](restore-a-deleted-gpo-agpm30ops.md)
-
-- [Destroy a GPO](destroy-a-gpo-agpm30ops.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/deleting-restoring-or-destroying-a-gpo-agpm40.md b/mdop/agpm/deleting-restoring-or-destroying-a-gpo-agpm40.md
deleted file mode 100644
index 7373c4011f..0000000000
--- a/mdop/agpm/deleting-restoring-or-destroying-a-gpo-agpm40.md
+++ /dev/null
@@ -1,35 +0,0 @@
----
-title: Deleting, Restoring, or Destroying a GPO
-description: Deleting, Restoring, or Destroying a GPO
-author: dansimp
-ms.assetid: 3af6c396-61c8-4b32-9fd8-28e9f15e575c
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Deleting, Restoring, or Destroying a GPO
-
-
-As an Approver, you can delete a Group Policy Object (GPO) (moving it to the Recycle Bin), restore a GPO from the Recycle Bin (returning it to the archive), or destroy a GPO (permanently deleting it so that it can no longer be restored).
-
-- [Delete a Controlled GPO](delete-a-controlled-gpo-agpm40.md)
-
-- [Restore a Deleted GPO](restore-a-deleted-gpo-agpm40.md)
-
-- [Destroy a GPO](destroy-a-gpo-agpm40.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/deleting-restoring-or-destroying-a-gpo.md b/mdop/agpm/deleting-restoring-or-destroying-a-gpo.md
deleted file mode 100644
index 86d70a45a4..0000000000
--- a/mdop/agpm/deleting-restoring-or-destroying-a-gpo.md
+++ /dev/null
@@ -1,35 +0,0 @@
----
-title: Deleting, Restoring, or Destroying a GPO
-description: Deleting, Restoring, or Destroying a GPO
-author: dansimp
-ms.assetid: 089c68e7-c1a5-418a-8776-cf23960f10c4
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Deleting, Restoring, or Destroying a GPO
-
-
-As an Approver, you can delete a Group Policy object (GPO) (moving it to the Recycle Bin), restore a GPO from the Recycle Bin (returning it to the archive), or destroy a GPO (permanently deleting it so that it can no longer be restored).
-
-- [Delete a GPO](delete-a-gpo-approver.md)
-
-- [Restore a Deleted GPO](restore-a-deleted-gpo.md)
-
-- [Destroy a GPO](destroy-a-gpo.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/deploy-a-gpo-agpm30ops.md b/mdop/agpm/deploy-a-gpo-agpm30ops.md
deleted file mode 100644
index 1e51162115..0000000000
--- a/mdop/agpm/deploy-a-gpo-agpm30ops.md
+++ /dev/null
@@ -1,62 +0,0 @@
----
-title: Deploy a GPO
-description: Deploy a GPO
-author: dansimp
-ms.assetid: 3767b722-db43-40f1-a714-bb8e38bcaa10
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Deploy a GPO
-
-
-An Approver can deploy a new or edited Group Policy Object (GPO) to the production environment. For information about redeploying a previous version of a GPO, see [Roll Back to a Previous Version of a GPO](roll-back-to-a-previous-version-of-a-gpo-agpm30ops.md).
-
-A user account with the Approver or AGPM Administrator (Full Control) role or necessary permissions in Advanced Group Policy Management (AGPM) is required to complete this procedure. Review the details in "Additional considerations" in this topic.
-
-**To deploy a GPO to the production environment**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. On the **Contents** tab, click the **Controlled** tab to display the controlled GPOs.
-
-3. Right-click the GPO to be deployed and then click **Deploy**.
-
-4. To review links to the GPO, click **Advanced**. Pause the mouse pointer on an item in the tree to display details.
-
- - By default, all links to the GPO will be restored.
-
- - To prevent a link from being restored, clear the check box for that link.
-
- - To prevent all links from being restored, clear the **Restore Links** check box in the **Deploy GPO** dialog box.
-
-5. Click **Yes**. When the **Progress** window indicates that overall progress is complete, click **Close**.
-
-**Note**
-To verify whether the most recent version of a GPO has been deployed, on the **Controlled** tab, double-click the GPO to display its **History**. In the **History** for the GPO, the **State** column indicates whether a GPO has been deployed.
-
-
-
-### Additional considerations
-
-- By default, you must be an Approver or an AGPM Administrator (Full Control) to perform this procedure. Specifically, you must have **List Contents** and **Deploy GPO** permissions for the GPO.
-
-### Additional references
-
-- [Performing Approver Tasks](performing-approver-tasks-agpm30ops.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/deploy-a-gpo-agpm40.md b/mdop/agpm/deploy-a-gpo-agpm40.md
deleted file mode 100644
index 6c16327cc3..0000000000
--- a/mdop/agpm/deploy-a-gpo-agpm40.md
+++ /dev/null
@@ -1,62 +0,0 @@
----
-title: Deploy a GPO
-description: Deploy a GPO
-author: dansimp
-ms.assetid: a6febeaa-144b-4c02-99af-d972f0f2b544
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Deploy a GPO
-
-
-An Approver can deploy a new or edited Group Policy Object (GPO) to the production environment. For information about redeploying an earlier version of a GPO, see [Roll Back to an Earlier Version of a GPO](roll-back-to-an-earlier-version-of-a-gpo-agpm40.md).
-
-A user account with the Approver or AGPM Administrator (Full Control) role or necessary permissions in Advanced Group Policy Management (AGPM) is required to complete this procedure. Review the details in "Additional considerations" in this topic.
-
-**To deploy a GPO to the production environment**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. On the **Contents** tab, click the **Controlled** tab to display the controlled GPOs.
-
-3. Right-click the GPO to be deployed and then click **Deploy**.
-
-4. To review links to the GPO, click **Advanced**. Pause the mouse pointer on an item in the tree to display details.
-
- - By default, all links to the GPO will be restored.
-
- - To prevent a link from being restored, clear the check box for that link.
-
- - To prevent all links from being restored, clear the **Restore Links** check box in the **Deploy GPO** dialog box.
-
-5. Click **Yes**. When the **Progress** window indicates that overall progress is complete, click **Close**.
-
-**Note**
-To verify whether the most recent version of a GPO has been deployed, on the **Controlled** tab, double-click the GPO to display its **History**. In the **History** for the GPO, the **State** column indicates whether a GPO has been deployed.
-
-
-
-### Additional considerations
-
-- By default, you must be an Approver or an AGPM Administrator (Full Control) to perform this procedure. Specifically, you must have **List Contents** and **Deploy GPO** permissions for the GPO.
-
-### Additional references
-
-- [Performing Approver Tasks](performing-approver-tasks-agpm40.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/deploy-a-gpo.md b/mdop/agpm/deploy-a-gpo.md
deleted file mode 100644
index fcb0ff6fe7..0000000000
--- a/mdop/agpm/deploy-a-gpo.md
+++ /dev/null
@@ -1,62 +0,0 @@
----
-title: Deploy a GPO
-description: Deploy a GPO
-author: dansimp
-ms.assetid: a0a3f292-e3ab-46ae-a0fd-d7b2b4ad8883
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Deploy a GPO
-
-
-Advanced Group Policy Management (AGPM) enables an Approver to deploy a new or edited Group Policy object (GPO) to the production environment. For information about redeploying a previous version of a GPO, see [Roll Back to a Previous Version of a GPO](roll-back-to-a-previous-version-of-a-gpo.md).
-
-A user account with the Approver or AGPM Administrator (Full Control) role or necessary permissions in Advanced Group Policy Management is required to complete this procedure. Review the details in "Additional considerations" in this topic.
-
-**To deploy a GPO to the production environment**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. On the **Contents** tab, click the **Controlled** tab to display the controlled GPOs.
-
-3. Right-click the GPO to be deployed and then click **Deploy**.
-
-4. To review links to the GPO, click **Advanced**. Pause the mouse pointer on a node in the tree to display details.
-
- - By default, all links to the GPO will be restored.
-
- - To prevent a link from being restored, clear the check box for that link.
-
- - To prevent all links from being restored, clear the **Restore Links** check box in the **Deploy GPO** dialog box.
-
-5. Click **Yes**. When the **Progress** window indicates that overall progress is complete, click **Close**.
-
-**Note**
-To verify whether the most recent version of a GPO has been deployed, on the **Controlled** tab, double-click the GPO to display its **History**. In the **History** for the GPO, the **State** column indicates whether a GPO has been deployed.
-
-
-
-### Additional considerations
-
-- By default, you must be an Approver or an AGPM Administrator (Full Control) to perform this procedure. Specifically, you must have **List Contents** and **Deploy GPO** permissions for the GPO.
-
-### Additional references
-
-- [Performing Approver Tasks](performing-approver-tasks.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/destroy-a-gpo-agpm30ops.md b/mdop/agpm/destroy-a-gpo-agpm30ops.md
deleted file mode 100644
index 12697f828f..0000000000
--- a/mdop/agpm/destroy-a-gpo-agpm30ops.md
+++ /dev/null
@@ -1,51 +0,0 @@
----
-title: Destroy a GPO
-description: Destroy a GPO
-author: dansimp
-ms.assetid: bfabd71a-47f3-462e-b86f-5f15762b9e28
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Destroy a GPO
-
-
-Approvers can destroy a Group Policy Object (GPO), removing it from the Recycle Bin and permanently deleting it so that it can no longer be restored.
-
-A user account with the Approver or AGPM Administrator (Full Control) role or necessary permissions in Advanced Group Policy Management (AGPM) is required to complete this procedure. Review the details in "Additional considerations" in this topic.
-
-**To permanently delete a GPO so it can no longer be restored**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. On the **Contents** tab, click the **Recycle Bin** tab to display the deleted GPOs.
-
-3. Right-click the GPO to destroy, and then click **Destroy**.
-
-4. Click **Yes** to confirm that you want to permanently delete the selected GPO and all backups from the archive.
-
-5. When the **Progress** window indicates that overall progress is complete, click **Close**. The GPO is removed from the **Recycle Bin** tab and is permanently deleted.
-
-### Additional considerations
-
-- By default, you must be an Approver or an AGPM Administrator (Full Control) to perform this procedure. Specifically, you must have **List Contents** and **Delete GPO** permissions for the GPO.
-
-### Additional references
-
-- [Deleting, Restoring, or Destroying a GPO](deleting-restoring-or-destroying-a-gpo-agpm30ops.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/destroy-a-gpo-agpm40.md b/mdop/agpm/destroy-a-gpo-agpm40.md
deleted file mode 100644
index 9762120942..0000000000
--- a/mdop/agpm/destroy-a-gpo-agpm40.md
+++ /dev/null
@@ -1,51 +0,0 @@
----
-title: Destroy a GPO
-description: Destroy a GPO
-author: dansimp
-ms.assetid: 09bce8c4-f75b-4633-b80b-d894bbec95c9
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Destroy a GPO
-
-
-Approvers can destroy a Group Policy Object (GPO), removing it from the Recycle Bin and permanently deleting it so that it can no longer be restored.
-
-A user account with the Approver or AGPM Administrator (Full Control) role or necessary permissions in Advanced Group Policy Management (AGPM) is required to complete this procedure. Review the details in "Additional considerations" in this topic.
-
-**To permanently delete a GPO so it can no longer be restored**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. On the **Contents** tab, click the **Recycle Bin** tab to display the deleted GPOs.
-
-3. Right-click the GPO to destroy, and then click **Destroy**.
-
-4. Click **Yes** to confirm that you want to permanently delete the selected GPO and all backups from the archive.
-
-5. When the **Progress** window indicates that overall progress is complete, click **Close**. The GPO is removed from the **Recycle Bin** tab and is permanently deleted.
-
-### Additional considerations
-
-- By default, you must be an Approver or an AGPM Administrator (Full Control) to perform this procedure. Specifically, you must have **List Contents** and **Delete GPO** permissions for the GPO.
-
-### Additional references
-
-- [Deleting, Restoring, or Destroying a GPO](deleting-restoring-or-destroying-a-gpo-agpm40.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/destroy-a-gpo.md b/mdop/agpm/destroy-a-gpo.md
deleted file mode 100644
index f1b33449d2..0000000000
--- a/mdop/agpm/destroy-a-gpo.md
+++ /dev/null
@@ -1,51 +0,0 @@
----
-title: Destroy a GPO
-description: Destroy a GPO
-author: dansimp
-ms.assetid: d74941a3-beef-46cd-a4ca-80a324dcfadf
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Destroy a GPO
-
-
-Advanced Group Policy Management (AGPM) enables Approvers to destroy a Group Policy object (GPO), removing it from the Recycle Bin and permanently deleting it so that it can no longer be restored.
-
-A user account with the Approver or AGPM Administrator (Full Control) role or necessary permissions in Advanced Group Policy Management is required to complete this procedure. Review the details in "Additional considerations" in this topic.
-
-**To permanently delete a GPO so it can no longer be restored**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. On the **Contents** tab, click the **Recycle Bin** tab to display the deleted GPOs.
-
-3. Right-click the GPO to destroy, and then click **Destroy**.
-
-4. Click **Yes** to confirm that you want to permanently delete the selected GPO and all backups from the archive.
-
-5. When the **Progress** window indicates that overall progress is complete, click **Close**. The GPO is removed from the **Recycle Bin** tab and is permanently deleted.
-
-### Additional considerations
-
-- By default, you must be an Approver or an AGPM Administrator (Full Control) to perform this procedure. Specifically, you must have **List Contents** and **Delete GPO** permissions for the GPO.
-
-### Additional references
-
-- [Deleting, Restoring, or Destroying a GPO](deleting-restoring-or-destroying-a-gpo.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/domain-delegation-tab-agpm30ops.md b/mdop/agpm/domain-delegation-tab-agpm30ops.md
deleted file mode 100644
index d2989bdb1a..0000000000
--- a/mdop/agpm/domain-delegation-tab-agpm30ops.md
+++ /dev/null
@@ -1,123 +0,0 @@
----
-title: Domain Delegation Tab
-description: Domain Delegation Tab
-author: dansimp
-ms.assetid: 523cdf39-f4b8-4d20-a917-3485756658ce
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Domain Delegation Tab
-
-
-The **Domain Delegation** tab on the **Change Control** pane provides a list of Group Policy administrators who have domain-level access to the archive and indicates the roles of each. Additionally, this tab enables AGPM Administrators (Full Control) to configure domain-level permissions for Editors, Approvers, Reviewers, and other AGPM Administrators. There are two sections on the **Domain Delegation** tab—configuration of e-mail notification and role-based delegation for Advanced Group Policy Management (AGPM) at the domain level.
-
-## Configuration of e-mail notification
-
-
-The e-mail notification section of this tab identifies the Approvers that will receive notification when operations are pending in AGPM.
-
-
-
-
-
-
-
-
-
Setting
-
Description
-
-
-
-
-
From e-mail address
-
The AGPM alias from which notification is sent to Approvers. In an environment with multiple domains, this can be the same alias throughout the environment or a different alias for each domain.
-
-
-
To e-mail address
-
A comma-delimited list of e-mail addresses of Approvers to whom notification is to be sent
-
-
-
SMTP server
-
The name of the e-mail server, such as mail.contoso.com
-
-
-
User name
-
A user with access to the SMTP server
-
-
-
Password
-
User's password for authentication to the SMTP server
-
-
-
Confirm password
-
Confirm user's password
-
-
-
-
-
-
-## Domain-level role-based delegation
-
-
-The role-based delegation section of this tab displays and enables an AGPM Administrator to delegate allowed, denied, and inherited permissions for each group and user on the domain with access to the archive. An AGPM Administrator can configure domain-wide permissions using either standard AGPM roles (Editor, Approver, Reviewer, and AGPM Administrator) or a customized combination of permissions for each Group Policy administrator.
-
-
-
-
-
-
-
-
-
Button
-
Effect
-
-
-
-
-
Add
-
Add a new entry to the security descriptor. Any users or groups in Active Directory can be added as Group Policy administrators.
-
-
-
Remove
-
Remove the selected Group Policy administrators from the Access Control List.
-
-
-
Properties
-
Display the properties for the selected Group Policy administrators.
-
-
-
Advanced
-
Open the Access Control List Editor.
-
-
-
-
-
-
-### Additional considerations
-
-- For information about roles and permissions related to specific tasks, see the tasks under [Performing AGPM Administrator Tasks](performing-agpm-administrator-tasks-agpm30ops.md), [Performing Editor Tasks](performing-editor-tasks-agpm30ops.md), [Performing Approver Tasks](performing-approver-tasks-agpm30ops.md), and [Performing Reviewer Tasks](performing-reviewer-tasks-agpm30ops.md).
-
-### Additional references
-
-- [User Interface: Advanced Group Policy Management](user-interface-advanced-group-policy-management-agpm30ops.md)
-
-- [Performing AGPM Administrator Tasks](performing-agpm-administrator-tasks-agpm30ops.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/domain-delegation-tab-agpm40.md b/mdop/agpm/domain-delegation-tab-agpm40.md
deleted file mode 100644
index 4a847fcdba..0000000000
--- a/mdop/agpm/domain-delegation-tab-agpm40.md
+++ /dev/null
@@ -1,123 +0,0 @@
----
-title: Domain Delegation Tab
-description: Domain Delegation Tab
-author: dansimp
-ms.assetid: 5be5841e-92fb-4af6-aa68-0ae50f8d5141
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Domain Delegation Tab
-
-
-The **Domain Delegation** tab on the **Change Control** pane provides a list of Group Policy administrators who have domain-level access to the archive and indicates the roles of each. Additionally, this tab enables AGPM Administrators (Full Control) to configure domain-level permissions for Editors, Approvers, Reviewers, and other AGPM Administrators. There are two sections on the **Domain Delegation** tab—configuration of e-mail notification and role-based delegation for Advanced Group Policy Management (AGPM) at the domain level.
-
-## Configuration of e-mail notification
-
-
-The e-mail notification section of this tab identifies the Approvers that will receive notification when operations are pending in AGPM.
-
-
-
-
-
-
-
-
-
Setting
-
Description
-
-
-
-
-
From e-mail address
-
The AGPM alias from which notification is sent to Approvers. In an environment with multiple domains, this can be the same alias throughout the environment or a different alias for each domain.
-
-
-
To e-mail address
-
A comma-delimited list of e-mail addresses of Approvers to whom notification is to be sent
-
-
-
SMTP server
-
The name of the e-mail server, such as mail.contoso.com
-
-
-
User name
-
A user with access to the SMTP server
-
-
-
Password
-
User's password for authentication to the SMTP server
-
-
-
Confirm password
-
Confirm user's password
-
-
-
-
-
-
-## Domain-level role-based delegation
-
-
-The role-based delegation section of this tab displays and enables an AGPM Administrator to delegate allowed, denied, and inherited permissions for each group and user on the domain with access to the archive. An AGPM Administrator can configure domain-wide permissions using either standard AGPM roles (Editor, Approver, Reviewer, and AGPM Administrator) or a customized combination of permissions for each Group Policy administrator.
-
-
-
-
-
-
-
-
-
Button
-
Effect
-
-
-
-
-
Add
-
Add a new entry to the security descriptor. Any users or groups in Active Directory can be added as Group Policy administrators.
-
-
-
Remove
-
Remove the selected Group Policy administrators from the Access Control List.
-
-
-
Properties
-
Display the properties for the selected Group Policy administrators.
-
-
-
Advanced
-
Open the Access Control List Editor.
-
-
-
-
-
-
-### Additional considerations
-
-- For information about roles and permissions related to specific tasks, see the tasks under [Performing AGPM Administrator Tasks](performing-agpm-administrator-tasks-agpm40.md), [Performing Editor Tasks](performing-editor-tasks-agpm40.md), [Performing Approver Tasks](performing-approver-tasks-agpm40.md), and [Performing Reviewer Tasks](performing-reviewer-tasks-agpm40.md).
-
-### Additional references
-
-- [User Interface: Advanced Group Policy Management](user-interface-advanced-group-policy-management-agpm40.md)
-
-- [Performing AGPM Administrator Tasks](performing-agpm-administrator-tasks-agpm40.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/domain-delegation-tab.md b/mdop/agpm/domain-delegation-tab.md
deleted file mode 100644
index 01cb0b02be..0000000000
--- a/mdop/agpm/domain-delegation-tab.md
+++ /dev/null
@@ -1,123 +0,0 @@
----
-title: Domain Delegation Tab
-description: Domain Delegation Tab
-author: dansimp
-ms.assetid: 15a9bfff-e25b-4b62-9ebc-521a5f4eae96
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Domain Delegation Tab
-
-
-The **Domain Delegation** tab on the **Change Control** pane provides a list of Group Policy administrators who have domain-level access to the archive and indicates the roles of each. Additionally, this tab enables AGPM Administrators (Full Control) to configure domain-level permissions for Editors, Approvers, Reviewers, and other AGPM Administrators. There are two sections on the **Domain Delegation** tab—configuration of e-mail notification and role-based delegation for Advanced Group Policy Management (AGPM) at the domain level.
-
-## Configuration of e-mail notification
-
-
-The e-mail notification section of this tab identifies the Approvers that will receive notification when operations are pending in AGPM.
-
-
-
-
-
-
-
-
-
Setting
-
Description
-
-
-
-
-
From
-
The AGPM alias from which notification is sent to Approvers. In an environment with multiple domains, this can be the same alias throughout the environment or a different alias for each domain.
-
-
-
To
-
A comma-delimited list of e-mail addresses of Approvers to whom notification is to be sent
-
-
-
SMTP server
-
The name of the e-mail server, such as mail.contoso.com
-
-
-
User name
-
A user with access to the SMTP server
-
-
-
Password
-
User's password for authentication to the SMTP server
-
-
-
Confirm password
-
Confirm user's password
-
-
-
-
-
-
-## Domain-level role-based delegation
-
-
-The role-based delegation section of this tab displays and enables an AGPM Administrator to delegate allowed, denied, and inherited permissions for each group and user on the domain with access to the archive. An AGPM Administrator can configure domain-wide permissions using either standard AGPM roles (Editor, Approver, Reviewer, and AGPM Administrator) or a customized combination of permissions for each Group Policy administrator.
-
-
-
-
-
-
-
-
-
Button
-
Effect
-
-
-
-
-
Add
-
Add a new entry to the security descriptor. Any users or groups in Active Directory can be added as Group Policy administrators.
-
-
-
Remove
-
Remove the selected Group Policy administrators from the Access Control List.
-
-
-
Properties
-
Display the properties for the selected Group Policy administrators. The properties page is the same one displayed for an object in Active Directory User and Computers.
-
-
-
Advanced
-
Open the Access Control List Editor.
-
-
-
-
-
-
-### Additional considerations
-
-- For information about roles and permissions related to specific tasks, see the tasks under [Performing AGPM Administrator Tasks](performing-agpm-administrator-tasks.md), [Performing Editor Tasks](performing-editor-tasks.md), [Performing Approver Tasks](performing-approver-tasks.md), and [Performing Reviewer Tasks](performing-reviewer-tasks.md).
-
-### Additional references
-
-- [User Interface: Advanced Group Policy Management](user-interface-advanced-group-policy-management.md)
-
-- [Performing AGPM Administrator Tasks](performing-agpm-administrator-tasks.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/edit-a-gpo-offline-agpm30ops.md b/mdop/agpm/edit-a-gpo-offline-agpm30ops.md
deleted file mode 100644
index 8e84747307..0000000000
--- a/mdop/agpm/edit-a-gpo-offline-agpm30ops.md
+++ /dev/null
@@ -1,111 +0,0 @@
----
-title: Edit a GPO Offline
-description: Edit a GPO Offline
-author: dansimp
-ms.assetid: 51677d8a-6209-41b5-82ed-4f3be817abc0
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Edit a GPO Offline
-
-
-To make changes to a controlled Group Policy Object (GPO), you must first check out a copy of the GPO from the archive. No one else will be able to modify the GPO until it is checked in again, preventing the introduction of conflicting changes by multiple Group Policy administrators. When you have finished modifying the GPO, you check it into the archive so that it can be reviewed and deployed to the production environment.
-
-A user account with the Editor or AGPM Administrator (Full Control) role, the user account of the Approver who created the GPO, or a user account with the necessary permissions in Advanced Group Policy Management (AGPM) is required to complete this procedure. Review the details in "Additional considerations" in this topic.
-
-## Editing a GPO offline
-
-
-To edit a GPO, you check out the GPO from the archive, edit the GPO offline, and then check the GPO into the archive so that it can be reviewed and deployed (or modified by other Editors).
-
-- [Check out a GPO from the archive for editing](#bkmk-checkout)
-
-- [Edit a GPO offline](#bkmk-edit)
-
-- [Check a GPO into the archive](#bkmk-checkin)
-
-###
-
-**To check out a GPO from the archive for editing**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. On the **Contents** tab, click the **Controlled** tab to display the controlled GPOs.
-
-3. Right-click the GPO to be edited, and then click **Check Out**.
-
-4. Type a comment to be displayed in the History of the GPO while it is checked out, and then click **OK**.
-
-5. When the **Progress** window indicates that overall progress is complete, click **Close**. On the **Controlled** tab, the state of the GPO is now identified as **Checked Out**.
-
-###
-
-**To edit a GPO offline**
-
-1. On the **Controlled** tab, right-click the GPO to be edited, and then click **Edit**.
-
-2. In the **Group Policy Management Editor** window, make changes to an offline copy of the GPO.
-
- **Note**
- To disable all Computer Configuration settings or all User Configuration settings, right-click the GPO in the **Group Policy Management Editor** window and click **Properties**. Select **Disable Computer Configuration settings** or **Disable User Configuration settings** as appropriate.
-
-
-
-3. When you have finished modifying the GPO, close the **Group Policy Management Editor** window.
-
-###
-
-**To check a GPO into the archive**
-
-1. On the **Controlled** tab:
-
- - If you have made no changes to the GPO, right-click the GPO and click **Undo Check Out**, and then click **Yes** to confirm.
-
- - If you have made changes to the GPO, right-click the GPO and click **Check In**.
-
-2. Type a comment to be displayed in the audit trail of the GPO, and then click **OK**.
-
-3. When the **Progress** window indicates that overall progress is complete, click **Close**. On the **Controlled** tab, the state of the GPO is identified as **Checked In**.
-
-### Additional considerations
-
-- To check out and edit a GPO, by default you must be the Approver who created or controlled the GPO, an Editor, or an AGPM Administrator (Full Control). Specifically, you must have **List Contents** and **Edit Settings** permissions for the GPO. Additionally, to edit the GPO you must be the individual who has checked out the GPO.
-
-- To check in a GPO, by default, you must be an Editor, an Approver, or an AGPM Administrator (Full Control). Specifically, you must have **List Contents** and either **Edit Settings** or **Deploy GPO** permissions for the GPO. If you are not an Approver or AGPM Administrator (or other Group Policy administrator with **Deploy GPO** permission), you must be the Editor who has checked out the GPO.
-
-- When editing a GPO, any Group Policy Software Installation upgrade of a package in another GPO should reference the deployed GPO, and not the checked-out copy.
-
-### Additional references
-
-- [Editing a GPO](editing-a-gpo-agpm30ops.md)
-
-- Reviewing a GPO
-
- - [Review GPO Settings](review-gpo-settings-agpm30ops.md)
-
- - [Review GPO Links](review-gpo-links-agpm30ops.md)
-
- - [Identify Differences Between GPOs, GPO Versions, or Templates](identify-differences-between-gpos-gpo-versions-or-templates-agpm30ops.md)
-
-- Deploying a GPO
-
- - [Request Deployment of a GPO](request-deployment-of-a-gpo-agpm30ops.md)
-
- - [Deploy a GPO](deploy-a-gpo-agpm30ops.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/edit-a-gpo-offline-agpm40.md b/mdop/agpm/edit-a-gpo-offline-agpm40.md
deleted file mode 100644
index 6288426883..0000000000
--- a/mdop/agpm/edit-a-gpo-offline-agpm40.md
+++ /dev/null
@@ -1,111 +0,0 @@
----
-title: Edit a GPO Offline
-description: Edit a GPO Offline
-author: dansimp
-ms.assetid: 9c75eb3c-d4d5-41e0-b65e-8b4464a42cd9
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Edit a GPO Offline
-
-
-To make changes to a controlled Group Policy Object (GPO), you must first check out a copy of the GPO from the archive. No one else will be able to modify the GPO until it is checked in again, preventing the introduction of conflicting changes by multiple Group Policy administrators. When you have finished modifying the GPO, you check it into the archive so that it can be reviewed and deployed to the production environment.
-
-A user account with the Editor or AGPM Administrator (Full Control) role, the user account of the Approver who created the GPO, or a user account with the necessary permissions in Advanced Group Policy Management (AGPM) is required to complete this procedure. Review the details in "Additional considerations" in this topic.
-
-## Editing a GPO offline
-
-
-To edit a GPO, you check out the GPO from the archive, edit the GPO offline, and then check the GPO into the archive so that it can be reviewed and deployed (or modified by other Editors).
-
-- [Check out a GPO from the archive for editing](#bkmk-checkout)
-
-- [Edit a GPO offline](#bkmk-edit)
-
-- [Check a GPO into the archive](#bkmk-checkin)
-
-###
-
-**To check out a GPO from the archive for editing**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. On the **Contents** tab, click the **Controlled** tab to display the controlled GPOs.
-
-3. Right-click the GPO to be edited, and then click **Check Out**.
-
-4. Type a comment to be displayed in the History of the GPO while it is checked out, and then click **OK**.
-
-5. When the **Progress** window indicates that overall progress is complete, click **Close**. On the **Controlled** tab, the state of the GPO is now identified as **Checked Out**.
-
-###
-
-**To edit a GPO offline**
-
-1. On the **Controlled** tab, right-click the GPO to be edited, and then click **Edit**.
-
-2. In the **Group Policy Management Editor** window, make changes to an offline copy of the GPO.
-
- **Note**
- To disable all Computer Configuration settings or all User Configuration settings, right-click the GPO in the **Group Policy Management Editor** window and click **Properties**. Select **Disable Computer Configuration settings** or **Disable User Configuration settings** as appropriate.
-
-
-
-3. When you have finished modifying the GPO, close the **Group Policy Management Editor** window.
-
-###
-
-**To check a GPO into the archive**
-
-1. On the **Controlled** tab:
-
- - If you have made no changes to the GPO, right-click the GPO and click **Undo Check Out**, and then click **Yes** to confirm.
-
- - If you have made changes to the GPO, right-click the GPO and click **Check In**.
-
-2. Type a comment to be displayed in the audit trail of the GPO, and then click **OK**.
-
-3. When the **Progress** window indicates that overall progress is complete, click **Close**. On the **Controlled** tab, the state of the GPO is identified as **Checked In**.
-
-### Additional considerations
-
-- To check out and edit a GPO, by default you must be the Approver who created or controlled the GPO, an Editor, or an AGPM Administrator (Full Control). Specifically, you must have **List Contents** and **Edit Settings** permissions for the GPO. Additionally, to edit the GPO you must be the individual who has checked out the GPO.
-
-- To check in a GPO, by default, you must be an Editor, an Approver, or an AGPM Administrator (Full Control). Specifically, you must have **List Contents** and either **Edit Settings** or **Deploy GPO** permissions for the GPO. If you are not an Approver or AGPM Administrator (or other Group Policy administrator with **Deploy GPO** permission), you must be the Editor who has checked out the GPO.
-
-- When editing a GPO, any Group Policy Software Installation upgrade of a package in another GPO should reference the deployed GPO, and not the checked-out copy.
-
-### Additional references
-
-- [Editing a GPO](editing-a-gpo-agpm40.md)
-
-- Reviewing a GPO
-
- - [Review GPO Settings](review-gpo-settings-agpm40.md)
-
- - [Review GPO Links](review-gpo-links-agpm40.md)
-
- - [Identify Differences Between GPOs, GPO Versions, or Templates](identify-differences-between-gpos-gpo-versions-or-templates-agpm40.md)
-
-- Deploying a GPO
-
- - [Request Deployment of a GPO](request-deployment-of-a-gpo-agpm40.md)
-
- - [Deploy a GPO](deploy-a-gpo-agpm40.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/edit-a-gpo-offline.md b/mdop/agpm/edit-a-gpo-offline.md
deleted file mode 100644
index bc1aba3836..0000000000
--- a/mdop/agpm/edit-a-gpo-offline.md
+++ /dev/null
@@ -1,106 +0,0 @@
----
-title: Edit a GPO Offline
-description: Edit a GPO Offline
-author: dansimp
-ms.assetid: 4a148952-9fe9-4ec4-8df1-b25e37c97a54
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Edit a GPO Offline
-
-
-To make changes to a controlled Group Policy object (GPO), you must first check out a copy of the GPO from the archive. No one else will be able to modify the GPO until it is checked in again, preventing the introduction of conflicting changes by multiple Group Policy administrators. When you have finished modifying the GPO, you check it into the archive, so it can be reviewed and deployed to the production environment.
-
-A user account with the Editor or AGPM Administrator (Full Control) role, the user account of the Approver who created the GPO, or a user account with the necessary permissions in Advanced Group Policy Management is required to complete this procedure. Review the details in "Additional considerations" in this topic.
-
-## Editing a GPO offline
-
-
-To edit a GPO, you check out the GPO from the archive, edit the GPO offline, and then check the GPO into the archive, so it can be reviewed and deployed (or modified by other Editors).
-
-- [Check out a GPO](#bkmk-checkout)
-
-- [Edit a GPO](#bkmk-edit)
-
-- [Check in a GPO](#bkmk-checkin)
-
-###
-
-**To check out a GPO from the archive for editing**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. On the **Contents** tab in the details pane, click the **Controlled** tab to display the controlled GPOs.
-
-3. Right-click the GPO to be edited, and then click **Check Out**.
-
-4. Type a comment to be displayed in the History of the GPO while it is checked out, then click **OK**.
-
-5. When the **Progress** window indicates that overall progress is complete, click **Close**. On the **Controlled** tab, the state of the GPO is now identified as **Checked Out**.
-
-###
-
-**To edit a GPO offline**
-
-1. On the **Controlled** tab, right-click the GPO to be edited, and then click **Edit**.
-
-2. In the **Group Policy Object Editor**, make changes to an offline copy of the GPO.
-
-3. When you have finished modifying the GPO, close the **Group Policy Object Editor**.
-
-###
-
-**To check a GPO into the archive**
-
-1. On the **Controlled** tab:
-
- - If you have made no changes to the GPO, right-click the GPO and click **Undo Check Out**, then click **Yes** to confirm.
-
- - If you have made changes to the GPO, right-click the GPO and click **Check In**.
-
-2. Type a comment to be displayed in the audit trail of the GPO, and then click **OK**.
-
-3. When the **Progress** window indicates that overall progress is complete, click **Close**. On the **Controlled** tab, the state of the GPO is identified as **Checked In**.
-
-### Additional considerations
-
-- To check out and edit a GPO, by default, you must be the Approver who created or controlled the GPO, an Editor, or an AGPM Administrator (Full Control). Specifically, you must have **List Contents** and **Edit Settings** permissions for the GPO. Additionally, to edit the GPO you must be the individual who has checked out the GPO.
-
-- To check in a GPO, by default, you must be an Editor, an Approver, or an AGPM Administrator (Full Control). Specifically, you must have **List Contents** and either **Edit Settings** or **Deploy GPO** permissions for the GPO. If you are not an Approver or AGPM Administrator (or other Group Policy administrator with **Deploy GPO** permission), you must be the Editor who has checked out the GPO.
-
-- When editing a GPO, any Group Policy Software Installation upgrade of a package in another GPO should reference the deployed GPO, not the checked-out copy.
-
-### Additional references
-
-- [Editing a GPO](editing-a-gpo.md)
-
-- Reviewing a GPO
-
- - [Review GPO Settings](review-gpo-settings.md)
-
- - [Review GPO Links](review-gpo-links.md)
-
- - [Identify Differences Between GPOs, GPO Versions, or Templates](identify-differences-between-gpos-gpo-versions-or-templates.md)
-
-- Deploying a GPO
-
- - [Request Deployment of a GPO](request-deployment-of-a-gpo.md)
-
- - [Deploy a GPO](deploy-a-gpo.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/editing-a-gpo-agpm30ops.md b/mdop/agpm/editing-a-gpo-agpm30ops.md
deleted file mode 100644
index 59b629a5c0..0000000000
--- a/mdop/agpm/editing-a-gpo-agpm30ops.md
+++ /dev/null
@@ -1,41 +0,0 @@
----
-title: Editing a GPO
-description: Editing a GPO
-author: dansimp
-ms.assetid: 3024051a-ff33-46d0-9c3e-68ebae7f6b60
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Editing a GPO
-
-
-A Group Policy Object (GPO) must be controlled by Advanced Group Policy Management (AGPM) before you can edit it. See [Creating, Controlling, or Importing a GPO](creating-controlling-or-importing-a-gpo-agpm30ops.md) for more information about controlling a GPO.
-
-To make changes to a GPO offline without immediately impacting the deployed copy of the GPO in the production environment, check out a copy of the GPO from the archive. When changes are complete, check the GPO back into the archive and request deployment of the GPO to the production environment.
-
-- [Edit a GPO Offline](edit-a-gpo-offline-agpm30ops.md)
-
-- [Use a Test Environment](use-a-test-environment-agpm30ops.md)
-
-- [Request Deployment of a GPO](request-deployment-of-a-gpo-agpm30ops.md)
-
-- [Label the Current Version of a GPO](label-the-current-version-of-a-gpo-agpm30ops.md)
-
-- [Rename a GPO or Template](rename-a-gpo-or-template-agpm30ops.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/editing-a-gpo-agpm40.md b/mdop/agpm/editing-a-gpo-agpm40.md
deleted file mode 100644
index affa8b706e..0000000000
--- a/mdop/agpm/editing-a-gpo-agpm40.md
+++ /dev/null
@@ -1,37 +0,0 @@
----
-title: Editing a GPO
-description: Editing a GPO
-author: dansimp
-ms.assetid: ef42eefe-7705-46b2-954d-18966335cbbf
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Editing a GPO
-
-
-A Group Policy Object (GPO) must be controlled by Advanced Group Policy Management (AGPM) before you can edit it. See [Creating or Controlling a GPO](creating-or-controlling-a-gpo-agpm40-ed.md) for more information about controlling a GPO.
-
-To make changes to a GPO offline without immediately impacting the deployed copy of the GPO in the production environment, check out a copy of the GPO from the archive. When changes are complete, check the GPO back into the archive, test it, and request deployment of the GPO to the production environment.
-
-- [Edit a GPO Offline](edit-a-gpo-offline-agpm40.md)
-
-- [Label the Current Version of a GPO](label-the-current-version-of-a-gpo-agpm40.md)
-
-- [Rename a GPO or Template](rename-a-gpo-or-template-agpm40.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/editing-a-gpo.md b/mdop/agpm/editing-a-gpo.md
deleted file mode 100644
index 8569b51552..0000000000
--- a/mdop/agpm/editing-a-gpo.md
+++ /dev/null
@@ -1,41 +0,0 @@
----
-title: Editing a GPO
-description: Editing a GPO
-author: dansimp
-ms.assetid: ec77d3bb-8a64-4d8e-9c28-87763de02ec0
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Editing a GPO
-
-
-A Group Policy object (GPO) must be controlled by Advanced Group Policy Management (AGPM) before you can edit it. See [Creating, Controlling, or Importing a GPO](creating-controlling-or-importing-a-gpo-editor.md) for more information about controlling a GPO.
-
-To make changes to a GPO offline without immediately impacting the deployed copy of the GPO in the production environment, check out a copy of the GPO from the archive. When changes are complete, check the GPO back into the archive and request deployment of the GPO to the production environment.
-
-- [Edit a GPO Offline](edit-a-gpo-offline.md)
-
-- [Use a Test Environment](use-a-test-environment.md)
-
-- [Request Deployment of a GPO](request-deployment-of-a-gpo.md)
-
-- [Label the Current Version of a GPO](label-the-current-version-of-a-gpo.md)
-
-- [Rename a GPO or Template](rename-a-gpo-or-template.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/export-a-gpo-to-a-file.md b/mdop/agpm/export-a-gpo-to-a-file.md
deleted file mode 100644
index 6cbcfe2245..0000000000
--- a/mdop/agpm/export-a-gpo-to-a-file.md
+++ /dev/null
@@ -1,49 +0,0 @@
----
-title: Export a GPO to a File
-description: Export a GPO to a File
-author: dansimp
-ms.assetid: 0d01b1f7-a6a4-4d0d-9aa7-2d6f1ae93d9d
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Export a GPO to a File
-
-
-You can export a controlled Group Policy Object (GPO) to a CAB file so that you can copy it to a domain in another forest and import the GPO into Advanced Group Policy Management (AGPM) in that domain. For information about how to import GPO settings into a new or existing GPO, see [Import a GPO from a File](import-a-gpo-from-a-file-ed.md).
-
-A user account with the Editor or AGPM Administrator (Full Control) role or necessary permissions in Advanced Group Policy Management (AGPM) is required to complete this procedure. Review the details in "Additional considerations" in this topic.
-
-**To export a GPO to a file**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. On the **Contents** tab, click the **Controlled** tab to display the controlled GPOs.
-
-3. Right-click the GPO, and then click **Export to**.
-
-4. Enter a file name for the file to which you want to export the GPO, and then click **Export**. If the file does not exist, it is created. If it already exists, it is replaced.
-
-### Additional considerations
-
-- By default, you must be an Editor or an AGPM Administrator (Full Control) to perform this procedure. Specifically, you must have **List Contents**, **Read Settings**, and **Export GPO** permissions for the GPO.
-
-### Additional references
-
-- [Using a Test Environment](using-a-test-environment.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/feature-visibility-settings-agpm30ops.md b/mdop/agpm/feature-visibility-settings-agpm30ops.md
deleted file mode 100644
index 5a6f4b5583..0000000000
--- a/mdop/agpm/feature-visibility-settings-agpm30ops.md
+++ /dev/null
@@ -1,64 +0,0 @@
----
-title: Feature Visibility Settings
-description: Feature Visibility Settings
-author: dansimp
-ms.assetid: 6a844478-a6b0-490d-923f-5a6f82467831
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Feature Visibility Settings
-
-
-The Administrative template settings for Advanced Group Policy Management (AGPM) enable you to centrally configure the visibility of the **Change Control** folder and **History** tab for Group Policy administrators to whom a Group Policy Object (GPO) with these settings is applied.
-
-The following settings are available under User Configuration\\Policies\\Administrative Templates\\Windows Components\\Microsoft Management Console\\Restricted/Permitted Snap-ins\\Extension Snap-ins when editing a GPO.
-
-
-
-
-
-
-
-
-
Setting
-
Effect
-
-
-
-
-
AGPM: Show Change Control tab
-
This policy setting allows you to control the visibility of the Change Control folder in the Group Policy Management Console (GPMC).
-
-
-
AGPM: Show History tab for linked GPOs
-
This policy setting allows you to control the visibility of the History tab provided by AGPM when you view a linked GPO in the GPMC.
-
-
-
AGPM: Show History tab for GPOs
-
This policy setting allows you to control the visibility of the History tab provided by AGPM when you view a GPO in the GPMC.
-
-
-
-
-
-
-### Additional references
-
-- [Administrative Templates Folder](administrative-templates-folder-agpm30ops.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/feature-visibility-settings-agpm40.md b/mdop/agpm/feature-visibility-settings-agpm40.md
deleted file mode 100644
index 126b1eb425..0000000000
--- a/mdop/agpm/feature-visibility-settings-agpm40.md
+++ /dev/null
@@ -1,64 +0,0 @@
----
-title: Feature Visibility Settings
-description: Feature Visibility Settings
-author: dansimp
-ms.assetid: d3c0b02a-b943-4001-8b9c-dfac8fe58789
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Feature Visibility Settings
-
-
-The Administrative template settings for Advanced Group Policy Management (AGPM) enable you to centrally configure the visibility of the **Change Control** folder and **History** tab for Group Policy administrators to whom a Group Policy Object (GPO) with these settings is applied.
-
-The following settings are available under User Configuration\\Policies\\Administrative Templates\\Windows Components\\Microsoft Management Console\\Restricted/Permitted Snap-ins\\Extension Snap-ins when editing a GPO.
-
-
-
-
-
-
-
-
-
Setting
-
Effect
-
-
-
-
-
AGPM: Show Change Control tab
-
This policy setting allows you to control the visibility of the Change Control folder in the Group Policy Management Console (GPMC).
-
-
-
AGPM: Show History tab for linked GPOs
-
This policy setting allows you to control the visibility of the History tab provided by AGPM when you view a linked GPO in the GPMC.
-
-
-
AGPM: Show History tab for GPOs
-
This policy setting allows you to control the visibility of the History tab provided by AGPM when you view a GPO in the GPMC.
-
-
-
-
-
-
-### Additional references
-
-- [Administrative Templates Folder](administrative-templates-folder-agpm40.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/feature-visibility-settings.md b/mdop/agpm/feature-visibility-settings.md
deleted file mode 100644
index 7a3848854c..0000000000
--- a/mdop/agpm/feature-visibility-settings.md
+++ /dev/null
@@ -1,67 +0,0 @@
----
-title: Feature Visibility Settings
-description: Feature Visibility Settings
-author: dansimp
-ms.assetid: 9db2ba03-fb75-4f95-9138-ec89b9fc8d01
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Feature Visibility Settings
-
-
-The Administrative template settings for Advanced Group Policy Management (AGPM) enable you to centrally configure the visibility of the **Change Control** node and **History** tab for Group Policy administrators to whom a Group Policy object (GPO) with these settings is applied.
-
-The following settings are available under User Configuration\\Administrative Templates\\Windows Components\\Microsoft Management Console\\Restricted/Permitted Snap-ins\\Extension Snap-ins in the **Group Policy Object Editor** when editing a GPO in the Group Policy Management Console (GPMC). If this path is not visible, right-click **Administrative Templates**, and add the agpm.admx or agpm.adm template.
-
-
-
-
-
-
-
-
-
Setting
-
Effect
-
-
-
-
-
AGPM Change Control
-
If enabled or not configured, the Change Control node is visible in the GPMC.
-
If disabled, the Change Control node is not visible in the GPMC.
-
-
-
AGPM Link Extension
-
If enabled or not configured, a History tab appears in the GPMC for each linked GPO.
-
If disabled, the History tab is not visible for linked GPOs.
-
-
-
AGPM GPO Extension
-
If enabled or not configured, a History tab appears in the GPMC for each GPO.
-
If disabled, the History tab is not visible for GPOs.
-
-
-
-
-
-
-### Additional references
-
-- [Administrative Template Settings](administrative-template-settings.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/history-window-agpm30ops.md b/mdop/agpm/history-window-agpm30ops.md
deleted file mode 100644
index bc85f0fee8..0000000000
--- a/mdop/agpm/history-window-agpm30ops.md
+++ /dev/null
@@ -1,204 +0,0 @@
----
-title: History Window
-description: History Window
-author: dansimp
-ms.assetid: 114f50a4-508d-4589-b006-6cd05cffe6b7
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# History Window
-
-
-The history of a Group Policy Object (GPO) can be displayed by double-clicking a GPO or by right-clicking a GPO and then clicking **History**. It is also displayed in the **Group Policy Management Console** (GPMC) as a tab for each GPO.
-
-The history provides a record of events in the lifetime of the selected GPO. From the **History** window, you can obtain a report of the settings within a version of the GPO, compare multiple versions of a GPO, or roll back to a previous version of a GPO.
-
-## Filtering events in the History window
-
-
-The tabs within the **History** window filter the states in the history of the GPO.
-
-
-
-
-
-
-
-
-
Tabs
-
Filtering
-
-
-
-
-
All States
-
Display all states in the history of the GPO.
-
-
-
Unique Versions
-
Display only unique versions of the GPO checked into the archive. The version deployed to the production environment, shortcuts to unique versions, and informational states are omitted from this list.
-
-
-
-
-
-
-## Event information
-
-
-Information is provided for each state in the history of the GPO.
-
-
-
-
-
-
-
-
-
GPO attribute
-
Description
-
-
-
-
-
Change Date
-
Time stamp of when the action in the State column was performed.
-
-
-
State
-
A state in the history of the GPO.
-
-
-
Changed By
-
The person who checked in or deployed the GPO.
-
-
-
Comment
-
A comment entered by the person who checked in or deployed a GPO at the time that this version was modified. Useful for identifying the specifics of the version in case of the need to roll back to a previous version.
-
-
-
Deletable
-
Whether this version of the GPO can be deleted if the number of unique versions of each GPO retained in the archive is limited.
-
-Note
You can modify whether a version of a GPO is deletable by right-clicking it and then clicking Do Not Allow Deletion or Allow Deletion.
-
-
-
-
-
-
-
Computer Version
-
Automatically generated version of the Computer Configuration portion of the GPO.
-
-
-
User Version
-
Automatically generated version of the User Configuration portion of the GPO.
-
-
-
GPO Status
-
The Computer Configuration and the User Configuration can be managed separately from each other. This status shows which portions of the GPO are enabled.
-
-
-
WMI Filter
-
Display any WMI filters that are applied to this GPO. WMI filters are managed under the WMI Filters folder for the domain in the console tree of the GPMC.
-
-
-
-
-
-
-## Reports
-
-
-The **Settings** and **Differences** buttons display reports about GPO settings for the GPO version or versions selected. Right-clicking GPO versions provides the option to display XML-based reports as well.
-
-
-
-
-
-
-
-
-
Button
-
Effect
-
-
-
-
-
Settings
-
Generate an HTML-based report displaying the settings within the selected version of the GPO.
-
-
-
Differences
-
Generate an HTML-based report comparing the settings within multiple selected versions of the GPO.
-
-
-
-
-
-
-### Key to difference reports
-
-
-
-
-
-
-
-
-
-
Symbol
-
Meaning
-
Color
-
-
-
-
-
None
-
Item exists with identical settings in both GPOs
-
Varies with level
-
-
-
[#]
-
Item exists in both GPOs, but with changed settings
-
Blue
-
-
-
[-]
-
Item exists only in the first GPO
-
Red
-
-
-
[+]
-
Item exists only in the second GPO
-
Green
-
-
-
-
-
-
-- For items with changed settings, the changed settings are identified when the item is expanded. The value for the attribute in each GPO is displayed in the same order that the GPOs are displayed in the report.
-
-- Some changes to settings may cause an item to be reported as two different items (one present only in the first GPO, one present only in the second), rather than as one item that has changed.
-
-### Additional references
-
-- [Contents Tab](contents-tab-agpm30ops.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/history-window-agpm40.md b/mdop/agpm/history-window-agpm40.md
deleted file mode 100644
index 0d1f91b021..0000000000
--- a/mdop/agpm/history-window-agpm40.md
+++ /dev/null
@@ -1,204 +0,0 @@
----
-title: History Window
-description: History Window
-author: dansimp
-ms.assetid: 5bea62e7-d267-40b2-a66d-fb1be7373a1c
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# History Window
-
-
-The history of a Group Policy Object (GPO) can be displayed by double-clicking a GPO or by right-clicking a GPO and then clicking **History**. It is also displayed in the Group Policy Management Console (GPMC) as a tab for each GPO.
-
-The history provides a record of events in the lifetime of the selected GPO. From the **History** window, you can obtain a report of the settings in a version of the GPO, compare multiple versions of a GPO, or roll back to an earlier version of a GPO.
-
-## Filtering events in the History window
-
-
-The tabs within the **History** window filter the states in the history of the GPO.
-
-
-
-
-
-
-
-
-
Tabs
-
Filtering
-
-
-
-
-
All States
-
Display all states in the history of the GPO.
-
-
-
Unique Versions
-
Display only unique versions of the GPO checked into the archive. The version deployed to the production environment, shortcuts to unique versions, and informational states are omitted from this list.
-
-
-
-
-
-
-## Event information
-
-
-Information is provided for each state in the history of the GPO.
-
-
-
-
-
-
-
-
-
GPO attribute
-
Description
-
-
-
-
-
Change Date
-
Time stamp of when the action in the State column was performed.
-
-
-
State
-
A state in the history of the GPO.
-
-
-
Changed By
-
The person who checked in or deployed the GPO.
-
-
-
Comment
-
A comment entered by the person who checked in or deployed a GPO at the time that this version was changed, useful for identifying the specifics of the version in case of the need to roll back to an earlier version.
-
-
-
Deletable
-
Whether this version of the GPO can be deleted if the number of unique versions of each GPO retained in the archive is limited.
-
-Note
You can change whether a version of a GPO can be deleted by right-clicking the GPO and then clicking Do Not Allow Deletion or Allow Deletion.
-
-
-
-
-
-
-
Computer Version
-
Automatically generated version of the Computer Configuration part of the GPO.
-
-
-
User Version
-
Automatically generated version of the User Configuration part of the GPO.
-
-
-
GPO Status
-
The Computer Configuration and the User Configuration can be managed separately from each other. This status shows which portions of the GPO are enabled.
-
-
-
Source GPO Information
-
For a GPO that has been imported from another forest, the original GPO name, domain, and user and date associated with the last change.
-
-
-
-
-
-
-## Reports
-
-
-The **Settings** and **Differences** buttons display reports about GPO settings for the GPO version or versions selected. Also, right-clicking a GPO version or versions provides the option to display XML-based reports.
-
-
-
-
-
-
-
-
-
Button
-
Effect
-
-
-
-
-
Settings
-
Generate an HTML-based report displaying the settings within the selected version of the GPO.
-
-
-
Differences
-
Generate an HTML-based report comparing the settings within multiple selected versions of the GPO.
-
-
-
-
-
-
-### Key to difference reports
-
-
-
-
-
-
-
-
-
-
Symbol
-
Meaning
-
Color
-
-
-
-
-
None
-
Item exists with identical settings in both GPOs
-
Varies with level
-
-
-
[#]
-
Item exists in both GPOs, but with changed settings
-
Blue
-
-
-
[-]
-
Item exists only in the first GPO
-
Red
-
-
-
[+]
-
Item exists only in the second GPO
-
Green
-
-
-
-
-
-
-- For items with changed settings, the changed settings are identified when the item is expanded. The value for the attribute in each GPO is displayed in the same order that the GPOs are displayed in the report.
-
-- Some changes to settings may cause an item to be reported as two items (one present only in the first GPO, one present only in the second), instead of one item that has changed.
-
-### Additional references
-
-- [Contents Tab](contents-tab-agpm40.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/history-window.md b/mdop/agpm/history-window.md
deleted file mode 100644
index 7de100917a..0000000000
--- a/mdop/agpm/history-window.md
+++ /dev/null
@@ -1,199 +0,0 @@
----
-title: History Window
-description: History Window
-author: dansimp
-ms.assetid: f11f9ad9-bffe-4c56-8c46-fe9c0a8e55c1
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# History Window
-
-
-The history of a Group Policy object (GPO) can be displayed by double-clicking a GPO or by right-clicking a GPO and then clicking **History**. It is also displayed in the **Group Policy Management Console** (GPMC) as a tab for each GPO.
-
-The history provides a list of all versions of the selected GPO saved within the archive. From the **History** window, you can obtain a report of the settings within a GPO, compare multiple versions of a GPO, or roll back to a previous version of a GPO.
-
-## Filtering events in the History window
-
-
-The tabs within the **History** window filter the events displayed.
-
-
-
-
-
-
-
-
-
Tabs
-
Filtering
-
-
-
-
-
Show All
-
Display all versions of the GPO.
-
-
-
Checked In
-
Display only checked-in versions of the GPO. The deployed version is omitted from this list.
-
-
-
Labels Only
-
Display only GPOs that have labels associated with them.
-
-
-
-
-
-
-## Event information
-
-
-Information is provided for each event in the history of the selected GPO.
-
-
-
-
-
-
-
-
-
GPO Characteristic
-
Description
-
-
-
-
-
Computer
-
Automatically generated version of the Computer Configuration portion of the GPO.
-
-
-
User
-
Automatically generated version of the User Configuration portion of the GPO.
-
-
-
Time
-
Timestamp of the version of the GPO when the action in the status field was performed.
-
-
-
State
-
The state of the selected version of the GPO:
-
Deployed: This version of the GPO is currently live in the production environment.
-
Checked In: This version of the GPO is available for authorized Editors to check out for editing or for a Group Policy administrator to deploy.
-
Checked Out: This version of the GPO is currently checked out by an Editor and is unavailable for other Editors. (The checked out state is not recorded in the History except to indicate if a GPO is currently checked out.)
-
Created: Identifies the date and time of the initial creation of the GPO.
-
Labeled: Identifies a labeled version of the GPO.
-
-
-
GPO Status
-
The Computer Configuration and the User Configuration can be managed separately from each other. This status shows which portions of the GPO are enabled.
-
-
-
Owner
-
The person who checked in or deployed the GPO.
-
-
-
Comment
-
A comment entered by the owner of a GPO at the time that this version was modified. Useful for identifying the specifics of the version in case of the need to roll back to a previous version.
-
-
-
-
-
-
-## Reports
-
-
-Depending on whether a single GPO version or multiple GPO versions are selected, the **Settings** and **Differences** buttons display reports on GPO settings. Right-clicking GPO versions provides the option to display XML-based reports as well.
-
-
-
-
-
-
-
-
-
Button
-
Effect
-
-
-
-
-
Settings
-
Generate an HTML-based report displaying the settings within the selected version of the GPO.
-
-
-
Differences
-
Generate an HTML-based report comparing the settings within multiple selected versions of the GPO.
-
-
-
-
-
-
-### Key to difference reports
-
-
-
-
-
-
-
-
-
-
Symbol
-
Meaning
-
Color
-
-
-
-
-
None
-
Item exists with identical settings in both GPOs
-
Varies with level
-
-
-
[#]
-
Item exists in both GPOs, but with changed settings
-
Blue
-
-
-
[-]
-
Item exists only in the first GPO
-
Red
-
-
-
[+]
-
Item exists only in the second GPO
-
Green
-
-
-
-
-
-
-- For items with changed settings, the changed settings are identified when the item is expanded. The value for the attribute in each GPO is displayed in the same order that the GPOs are displayed in the report.
-
-- Some changes to settings may cause an item to be reported as two different items (one present only in the first GPO, one present only in the second), rather than as one item that has changed.
-
-### Additional references
-
-- [Contents Tab](contents-tab.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/identify-differences-between-gpos-gpo-versions-or-templates-agpm30ops.md b/mdop/agpm/identify-differences-between-gpos-gpo-versions-or-templates-agpm30ops.md
deleted file mode 100644
index b7d575576e..0000000000
--- a/mdop/agpm/identify-differences-between-gpos-gpo-versions-or-templates-agpm30ops.md
+++ /dev/null
@@ -1,147 +0,0 @@
----
-title: Identify Differences Between GPOs, GPO Versions, or Templates
-description: Identify Differences Between GPOs, GPO Versions, or Templates
-author: dansimp
-ms.assetid: e391fa91-3956-4150-9d43-900cfc88d543
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Identify Differences Between GPOs, GPO Versions, or Templates
-
-
-You can generate HTML-based or XML-based difference reports to analyze the differences between Group Policy Objects (GPOs), templates, or different versions of a GPO.
-
-A user account with the Reviewer, Editor, Approver, or AGPM Administrator (Full Control) role or necessary permissions in Advanced Group Policy Management (AGPM) is required to complete this procedure. Review the details in "Additional considerations" in this topic.
-
-## Identifying differences between GPOs, GPO versions, or templates
-
-
-- [Between two GPOs or templates](#bkmk-two-gpos)
-
-- [Between a GPO and a template](#bkmk-gpo-and-template)
-
-- [Between two versions of one GPO](#bkmk-two-versions)
-
-- [Between a GPO version and a template](#bkmk-gpo-version-and-template)
-
-##
-
-
-**To identify differences between two GPOs or templates**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. On the **Contents** tab in the details pane, click a tab to display GPOs (or templates, if comparing two templates).
-
-3. Select the two GPOs or templates.
-
-4. Right-click one of the GPOs or templates, click **Differences**, and then click **HTML Report** or **XML Report** to display a difference report summarizing the settings of the GPOs or templates.
-
-###
-
-**To identify differences between a GPO and a template**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. On the **Contents** tab in the details pane, click a tab to display GPOs (or templates, if comparing two templates).
-
-3. Right-click the GPO, click **Differences**, and then click **Template**.
-
-4. Select the template and type of report, and then click **OK** to display a difference report summarizing the settings of the GPO and template.
-
-###
-
-**To identify differences between two versions of one GPO**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. On the **Contents** tab in the details pane, click a tab to display GPOs (or templates, if comparing two templates).
-
-3. Double-click the GPO to display its history, and then highlight the versions to be compared.
-
-4. Right-click one of the versions, click **Differences**, and then click **HTML Report** or **XML Report** to display a difference report summarizing the settings of the GPOs.
-
-###
-
-**To identify differences between a GPO version and a template**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. On the **Contents** tab in the details pane, click a tab to display GPOs (or templates, if comparing two templates).
-
-3. Double-click the GPO to display its history.
-
-4. Right-click the GPO version of interest, click **Differences**, and then click **Template**.
-
-5. Select the template and type of report, and then click **OK** to display a difference report summarizing the settings of the GPO version and template.
-
-## Key to difference reports
-
-
-
-
-
-
-
-
-
-
-
Symbol
-
Meaning
-
Color
-
-
-
-
-
None
-
Item exists with identical settings in both GPOs
-
Varies with level
-
-
-
[#]
-
Item exists in both GPOs, but with changed settings
-
Blue
-
-
-
[-]
-
Item exists only in the first GPO
-
Red
-
-
-
[+]
-
Item exists only in the second GPO
-
Green
-
-
-
-
-
-
-- For items with changed settings, the changed settings are identified when the item is expanded. The value for the attribute in each GPO is displayed in the same order that the GPOs are displayed in the report.
-
-- Some changes to settings may cause an item to be reported as two different items (one present only in the first GPO, one present only in the second) rather than as one item that has changed.
-
-### Additional considerations
-
-- By default, you must be a Reviewer, an Editor, an Approver, or an AGPM Administrator (Full Control) to perform this procedure. Specifically, you must have **List Contents** and **Read Settings** permissions for the GPO. Also, to display the list of GPOs, you must have **List Contents** permission for the domain.
-
-### Additional references
-
-- [Performing Reviewer Tasks](performing-reviewer-tasks-agpm30ops.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/identify-differences-between-gpos-gpo-versions-or-templates-agpm40.md b/mdop/agpm/identify-differences-between-gpos-gpo-versions-or-templates-agpm40.md
deleted file mode 100644
index 6201499127..0000000000
--- a/mdop/agpm/identify-differences-between-gpos-gpo-versions-or-templates-agpm40.md
+++ /dev/null
@@ -1,147 +0,0 @@
----
-title: Identify Differences Between GPOs, GPO Versions, or Templates
-description: Identify Differences Between GPOs, GPO Versions, or Templates
-author: dansimp
-ms.assetid: 3f03c368-162b-450f-be6c-2807c3e8d741
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Identify Differences Between GPOs, GPO Versions, or Templates
-
-
-You can generate HTML-based or XML-based difference reports to analyze the differences between Group Policy Objects (GPOs), templates, or different versions of a GPO.
-
-A user account with the Reviewer, Editor, Approver, or AGPM Administrator (Full Control) role or necessary permissions in Advanced Group Policy Management (AGPM) is required to complete this procedure. Review the details in "Additional considerations" in this topic.
-
-## Identifying differences between GPOs, GPO versions, or templates
-
-
-- [Between two GPOs or templates](#bkmk-two-gpos)
-
-- [Between a GPO and a template](#bkmk-gpo-and-template)
-
-- [Between two versions of one GPO](#bkmk-two-versions)
-
-- [Between a GPO version and a template](#bkmk-gpo-version-and-template)
-
-##
-
-
-**To identify differences between two GPOs or templates**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. On the **Contents** tab in the details pane, click a tab to display GPOs (or templates, if comparing two templates).
-
-3. Select the two GPOs or templates.
-
-4. Right-click one of the GPOs or templates, click **Differences**, and then click **HTML Report** or **XML Report** to display a difference report summarizing the settings of the GPOs or templates.
-
-###
-
-**To identify differences between a GPO and a template**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. On the **Contents** tab in the details pane, click a tab to display GPOs (or templates, if comparing two templates).
-
-3. Right-click the GPO, click **Differences**, and then click **Template**.
-
-4. Select the template and type of report, and then click **OK** to display a difference report summarizing the settings of the GPO and template.
-
-###
-
-**To identify differences between two versions of one GPO**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. On the **Contents** tab in the details pane, click a tab to display GPOs (or templates, if comparing two templates).
-
-3. Double-click the GPO to display its history, and then highlight the versions to be compared.
-
-4. Right-click one of the versions, click **Differences**, and then click **HTML Report** or **XML Report** to display a difference report summarizing the settings of the GPOs.
-
-###
-
-**To identify differences between a GPO version and a template**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. On the **Contents** tab in the details pane, click a tab to display GPOs (or templates, if comparing two templates).
-
-3. Double-click the GPO to display its history.
-
-4. Right-click the GPO version of interest, click **Differences**, and then click **Template**.
-
-5. Select the template and type of report, and then click **OK** to display a difference report summarizing the settings of the GPO version and template.
-
-## Key to difference reports
-
-
-
-
-
-
-
-
-
-
-
Symbol
-
Meaning
-
Color
-
-
-
-
-
None
-
Item exists with identical settings in both GPOs
-
Varies with level
-
-
-
[#]
-
Item exists in both GPOs, but with changed settings
-
Blue
-
-
-
[-]
-
Item exists only in the first GPO
-
Red
-
-
-
[+]
-
Item exists only in the second GPO
-
Green
-
-
-
-
-
-
-- For items with changed settings, the changed settings are identified when the item is expanded. The value for the attribute in each GPO is displayed in the same order that the GPOs are displayed in the report.
-
-- Some changes to settings may cause an item to be reported as two different items (one present only in the first GPO, one present only in the second) rather than as one item that has changed.
-
-### Additional considerations
-
-- By default, you must be a Reviewer, an Editor, an Approver, or an AGPM Administrator (Full Control) to perform this procedure. Specifically, you must have **List Contents** and **Read Settings** permissions for the GPO. Also, to display the list of GPOs, you must have **List Contents** permission for the domain.
-
-### Additional references
-
-- [Performing Reviewer Tasks](performing-reviewer-tasks-agpm40.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/identify-differences-between-gpos-gpo-versions-or-templates.md b/mdop/agpm/identify-differences-between-gpos-gpo-versions-or-templates.md
deleted file mode 100644
index 684eac2b0a..0000000000
--- a/mdop/agpm/identify-differences-between-gpos-gpo-versions-or-templates.md
+++ /dev/null
@@ -1,147 +0,0 @@
----
-title: Identify Differences Between GPOs, GPO Versions, or Templates
-description: Identify Differences Between GPOs, GPO Versions, or Templates
-author: dansimp
-ms.assetid: 6320afc4-af81-47e8-9f4c-463ff99d5a53
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Identify Differences Between GPOs, GPO Versions, or Templates
-
-
-You can generate HTML-based or XML-based difference reports to analyze the differences between Group Policy objects (GPOs), templates, or different versions of a GPO.
-
-A user account with the Reviewer, Editor, Approver, or AGPM Administrator (Full Control) role or necessary permissions in Advanced Group Policy Management is required to complete this procedure. Review the details in "Additional considerations" in this topic.
-
-## Identifying differences between GPOs, GPO versions, or templates
-
-
-- [Between two GPOs or templates](#bkmk-two-gpos)
-
-- [Between a GPO and a template](#bkmk-gpo-and-template)
-
-- [Between two versions of one GPO](#bkmk-two-versions)
-
-- [Between a GPO version and a template](#bkmk-gpo-version-and-template)
-
-##
-
-
-**To identify differences between two GPOs or templates**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. On the **Contents** tab in the details pane, click a tab to display GPOs (or templates, if comparing two templates).
-
-3. Select the two GPOs or templates.
-
-4. Right-click one of the GPOs or templates, click **Differences**, and then click **HTML Report** or **XML Report** to display a difference report summarizing the settings of the GPOs or templates.
-
-###
-
-**To identify differences between a GPO and a template**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. On the **Contents** tab in the details pane, click a tab to display GPOs (or templates, if comparing two templates).
-
-3. Right-click the GPO, click **Differences**, and then click **Template**.
-
-4. Select the template and type of report, and then click **OK** to display a difference report summarizing the settings of the GPO and template.
-
-###
-
-**To identify differences between two versions of one GPO**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. On the **Contents** tab in the details pane, click a tab to display GPOs (or templates, if comparing two templates).
-
-3. Double-click the GPO to display its history, and then highlight the versions to be compared.
-
-4. Right-click one of the versions, click **Differences**, and then click **HTML Report** or **XML Report** to display a difference report summarizing the settings of the GPOs.
-
-###
-
-**To identify differences between a GPO version and a template**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. On the **Contents** tab in the details pane, click a tab to display GPOs (or templates, if comparing two templates).
-
-3. Double-click the GPO to display its history.
-
-4. Right-click the GPO version of interest, click **Differences**, and then click **Template**.
-
-5. Select the template and type of report, and then click **OK** to display a difference report summarizing the settings of the GPO version and template.
-
-## Key to difference reports
-
-
-
-
-
-
-
-
-
-
-
Symbol
-
Meaning
-
Color
-
-
-
-
-
None
-
Item exists with identical settings in both GPOs
-
Varies with level
-
-
-
[#]
-
Item exists in both GPOs, but with changed settings
-
Blue
-
-
-
[-]
-
Item exists only in the first GPO
-
Red
-
-
-
[+]
-
Item exists only in the second GPO
-
Green
-
-
-
-
-
-
-- For items with changed settings, the changed settings are identified when the item is expanded. The value for the attribute in each GPO is displayed in the same order that the GPOs are displayed in the report.
-
-- Some changes to settings may cause an item to be reported as two different items (one present only in the first GPO, one present only in the second) rather than as one item that has changed.
-
-### Additional considerations
-
-- By default, you must be a Reviewer, an Editor, an Approver, or an AGPM Administrator (Full Control) to perform this procedure. Specifically, you must have **List Contents** and **Read Settings** permissions for the GPO. Also, to display the list of GPOs, you must have **List Contents** permission for the domain.
-
-### Additional references
-
-- [Performing Reviewer Tasks](performing-reviewer-tasks.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/images/0840a6a3-54a6-4528-98a9-7b122243c1a5.gif b/mdop/agpm/images/0840a6a3-54a6-4528-98a9-7b122243c1a5.gif
deleted file mode 100644
index 92fb2d9983..0000000000
Binary files a/mdop/agpm/images/0840a6a3-54a6-4528-98a9-7b122243c1a5.gif and /dev/null differ
diff --git a/mdop/agpm/images/327623bd-0842-4372-be1f-bdc4b8c3481c.gif b/mdop/agpm/images/327623bd-0842-4372-be1f-bdc4b8c3481c.gif
deleted file mode 100644
index c44fbda129..0000000000
Binary files a/mdop/agpm/images/327623bd-0842-4372-be1f-bdc4b8c3481c.gif and /dev/null differ
diff --git a/mdop/agpm/images/36f6b687-f5cc-40d1-805f-b191d1fb1ace.gif b/mdop/agpm/images/36f6b687-f5cc-40d1-805f-b191d1fb1ace.gif
deleted file mode 100644
index 08cd486435..0000000000
Binary files a/mdop/agpm/images/36f6b687-f5cc-40d1-805f-b191d1fb1ace.gif and /dev/null differ
diff --git a/mdop/agpm/images/57b610a5-1c71-4d26-9173-d04abd495fcc.gif b/mdop/agpm/images/57b610a5-1c71-4d26-9173-d04abd495fcc.gif
deleted file mode 100644
index 7cde9d24a1..0000000000
Binary files a/mdop/agpm/images/57b610a5-1c71-4d26-9173-d04abd495fcc.gif and /dev/null differ
diff --git a/mdop/agpm/images/8356fcdc-1279-425b-ab14-a23bcfe391da.gif b/mdop/agpm/images/8356fcdc-1279-425b-ab14-a23bcfe391da.gif
deleted file mode 100644
index a911ef77d0..0000000000
Binary files a/mdop/agpm/images/8356fcdc-1279-425b-ab14-a23bcfe391da.gif and /dev/null differ
diff --git a/mdop/agpm/images/8e7a7c4e-809a-435a-8b29-30d797936210.gif b/mdop/agpm/images/8e7a7c4e-809a-435a-8b29-30d797936210.gif
deleted file mode 100644
index 9514d106f5..0000000000
Binary files a/mdop/agpm/images/8e7a7c4e-809a-435a-8b29-30d797936210.gif and /dev/null differ
diff --git a/mdop/agpm/images/9b65829d-253c-4f30-9295-c816a6521ed2.gif b/mdop/agpm/images/9b65829d-253c-4f30-9295-c816a6521ed2.gif
deleted file mode 100644
index 7fa479c173..0000000000
Binary files a/mdop/agpm/images/9b65829d-253c-4f30-9295-c816a6521ed2.gif and /dev/null differ
diff --git a/mdop/agpm/images/ab77a1f3-f430-4e7d-be58-ee8f9bd1140e.gif b/mdop/agpm/images/ab77a1f3-f430-4e7d-be58-ee8f9bd1140e.gif
deleted file mode 100644
index e5c857fb6a..0000000000
Binary files a/mdop/agpm/images/ab77a1f3-f430-4e7d-be58-ee8f9bd1140e.gif and /dev/null differ
diff --git a/mdop/agpm/images/cd349b8d-c4d8-45ff-b17f-7db882502c58.gif b/mdop/agpm/images/cd349b8d-c4d8-45ff-b17f-7db882502c58.gif
deleted file mode 100644
index 0a689c5b02..0000000000
Binary files a/mdop/agpm/images/cd349b8d-c4d8-45ff-b17f-7db882502c58.gif and /dev/null differ
diff --git a/mdop/agpm/import-a-gpo-from-a-file-agpmadmin.md b/mdop/agpm/import-a-gpo-from-a-file-agpmadmin.md
deleted file mode 100644
index ae05829359..0000000000
--- a/mdop/agpm/import-a-gpo-from-a-file-agpmadmin.md
+++ /dev/null
@@ -1,76 +0,0 @@
----
-title: Import a GPO from a File
-description: Import a GPO from a File
-author: dansimp
-ms.assetid: 2cbcda72-4de3-47ad-aaf8-4fc7341d5a00
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Import a GPO from a File
-
-
-In Advanced Group Policy Management (AGPM), if you are an AGPM Administrator (Full Control) and you have exported a Group Policy Object (GPO) to a CAB file, you can import the policy settings from that GPO into a new GPO or an existing GPO in a domain in another forest. For information about exporting GPO settings to a CAB file, see [Export a GPO to a File](export-a-gpo-to-a-file.md).
-
-A user account with the AGPM Administrator role or the necessary permissions in AGPM is required to import policy settings into a new controlled GPO. A user account with the Editor or AGPM Administrator role or necessary permissions in AGPM is required to import policy settings into an existing GPO. Review the details in "Additional considerations" in this topic.
-
-## Importing policy settings from a file
-
-
-When you import policy settings from a file, you can import them into a new GPO or an existing GPO. However, if you import policy settings into an existing GPO, all policy settings within it are replaced.
-
-- [Import policy settings into a new controlled GPO](#bkmk-new)
-
-- [Import policy settings into an existing GPO](#bkmk-existing)
-
-###
-
-**To import policy settings into a new controlled GPO**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the domain to which you want to import policy settings.
-
-2. On the **Contents** tab, click the **Controlled** tab to display the controlled GPOs.
-
-3. Create a new controlled GPO. In the **New Controlled GPO** dialog box, click **Import** and then click **Launch Wizard**. For more information about how to create a GPO, see [Create a New Controlled GPO](create-a-new-controlled-gpo-agpm40.md).
-
-4. Follow the instructions in the **Import Settings Wizard** to select a GPO backup, import policy settings from it for the new GPO, and enter a comment for the audit trail of the new GPO.
-
-###
-
-**To import policy settings into an existing GPO**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the domain to which you want to import policy settings.
-
-2. On the **Contents** tab, click the **Controlled** tab to display the controlled GPOs.
-
-3. Check out the destination GPO to which you want to import policy settings.
-
-4. Right-click the destination GPO, point to **Import from**, and then click **File**.
-
-5. Follow the instructions in the **Import Settings Wizard** to select a GPO backup, import its policy settings to replace those in the destination GPO, and enter a comment for the audit trail of the destination GPO. By default, the destination GPO is checked in when the wizard is finished.
-
-### Additional considerations
-
-- To import policy settings to a new controlled GPO, you must have **List Contents**, **Import GPO**, and **Create GPO** permissions for the domain. By default, you must be an AGPM Administrator to perform this procedure.
-
-- To import policy settings to an existing GPO, you must have **List Contents**, **Edit Settings**, and **Import GPO** permissions for the domain, and the GPO must be checked out by you. By default, you must be an Editor or an AGPM Administrator (Full Control) to perform this procedure.
-
-### Additional references
-
-- [Managing the Archive](managing-the-archive-agpm40.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/import-a-gpo-from-a-file-ed.md b/mdop/agpm/import-a-gpo-from-a-file-ed.md
deleted file mode 100644
index 7029d3c69e..0000000000
--- a/mdop/agpm/import-a-gpo-from-a-file-ed.md
+++ /dev/null
@@ -1,56 +0,0 @@
----
-title: Import a GPO from a File
-description: Import a GPO from a File
-author: dansimp
-ms.assetid: 6e901a52-1101-4fed-9f90-3819b573b378
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Import a GPO from a File
-
-
-In Advanced Group Policy Management (AGPM), if you have exported a Group Policy Object (GPO) to a CAB file, you can import the policy settings from that GPO into an existing GPO in a domain in another forest. Importing policy settings into an existing GPO replaces all policy settings within that GPO. For information about exporting GPO settings to a CAB file, see [Export a GPO to a File](export-a-gpo-to-a-file.md).
-
-A user account with the Editor or AGPM Administrator (Full Control) role or necessary permissions in Advanced Group Policy Management (AGPM) is required to complete this procedure. Review the details in "Additional considerations" in this topic.
-
-##
-
-
-**To import policy settings into an existing GPO**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the domain to which you want to import policy settings.
-
-2. On the **Contents** tab, click the **Controlled** tab to display the controlled GPOs.
-
-3. Check out the destination GPO to which you want to import policy settings.
-
-4. Right-click the destination GPO, point to **Import from**, and then click **File**.
-
-5. Follow the instructions in the **Import Settings Wizard** to select a GPO backup, import its policy settings to replace those in the destination GPO, and enter a comment for the audit trail of the destination GPO. By default, the destination GPO is checked in when the wizard is finished.
-
-### Additional considerations
-
-- By default, you must be an Editor or an AGPM Administrator (Full Control) to perform this procedure. Specifically, you must have **List Contents**, **Edit Settings**, and **Import GPO** permissions for the domain, and the GPO must be checked out by you.
-
-- Although an Editor cannot import policy settings into a new GPO during its creation, an Editor can request the creation of a new GPO and then import policy settings into it after it is created.
-
-### Additional references
-
-- [Using a Test Environment](using-a-test-environment.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/import-a-gpo-from-production-agpm30ops.md b/mdop/agpm/import-a-gpo-from-production-agpm30ops.md
deleted file mode 100644
index 7754206dd0..0000000000
--- a/mdop/agpm/import-a-gpo-from-production-agpm30ops.md
+++ /dev/null
@@ -1,49 +0,0 @@
----
-title: Import a GPO from Production
-description: Import a GPO from Production
-author: dansimp
-ms.assetid: 35c2a682-ece8-4577-a083-7e3e9facfd13
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Import a GPO from Production
-
-
-If changes are made to a controlled Group Policy Object (GPO) outside of Advanced Group Policy Management (AGPM), you can import a copy of the GPO from the production environment and save it to the archive to bring the archive and the production environment to a consistent state. (To import an uncontrolled GPO, control the GPO. See [Request Control of an Uncontrolled GPO](request-control-of-an-uncontrolled-gpo-agpm30ops.md).)
-
-A user account with the Editor, Approver, or AGPM Administrator (Full Control) role or necessary permissions in AGPM is required to complete this procedure. Review the details in "Additional considerations" in this topic.
-
-**To import a GPO from the production environment**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. On the **Contents** tab, click the **Controlled** tab to display the controlled GPOs.
-
-3. Right-click the GPO, and then click **Import from Production**.
-
-4. Type a comment for the audit trail of the GPO, and then click **OK**.
-
-### Additional considerations
-
-- By default, you must be an Editor, Approver, or AGPM Administrator (Full Control) to perform this procedure. Specifically, you must have **List Contents** and either **Edit Settings**, **Deploy GPO**, or **Delete GPO** permissions for the GPO.
-
-### Additional references
-
-- [Creating, Controlling, or Importing a GPO](creating-controlling-or-importing-a-gpo-agpm30ops.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/import-a-gpo-from-production-agpm40-app.md b/mdop/agpm/import-a-gpo-from-production-agpm40-app.md
deleted file mode 100644
index cc8288be07..0000000000
--- a/mdop/agpm/import-a-gpo-from-production-agpm40-app.md
+++ /dev/null
@@ -1,49 +0,0 @@
----
-title: Import a GPO from Production
-description: Import a GPO from Production
-author: dansimp
-ms.assetid: c5b2f40d-1dc7-4dbf-b8b3-4d97ad73e1e5
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Import a GPO from Production
-
-
-If changes are made to a controlled Group Policy Object (GPO) outside of Advanced Group Policy Management (AGPM), you can import a copy of the GPO from the production environment of the domain and save it to the archive to bring the archive and the production environment to a consistent state. (To import an uncontrolled GPO, control the GPO. See [Control an Uncontrolled GPO](control-an-uncontrolled-gpo-agpm40.md).)
-
-A user account with the Editor, Approver, or AGPM Administrator (Full Control) role or necessary permissions in AGPM is required to complete this procedure. Review the details in "Additional considerations" in this topic.
-
-**To import a GPO from the production environment of the domain**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. On the **Contents** tab, click the **Controlled** tab to display the controlled GPOs.
-
-3. Right-click the GPO, and then click **Import from Production**.
-
-4. Type a comment for the audit trail of the GPO, and then click **OK**.
-
-### Additional considerations
-
-- By default, you must be an Editor, Approver, or AGPM Administrator (Full Control) to perform this procedure. Specifically, you must have **List Contents** and either **Edit Settings**, **Deploy GPO**, or **Delete GPO** permissions for the GPO.
-
-### Additional references
-
-- [Creating or Controlling a GPO](creating-or-controlling-a-gpo-agpm40-app.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/import-a-gpo-from-production-agpm40-ed.md b/mdop/agpm/import-a-gpo-from-production-agpm40-ed.md
deleted file mode 100644
index fcddfd97af..0000000000
--- a/mdop/agpm/import-a-gpo-from-production-agpm40-ed.md
+++ /dev/null
@@ -1,49 +0,0 @@
----
-title: Import a GPO from Production
-description: Import a GPO from Production
-author: dansimp
-ms.assetid: ad14203a-2e6a-41d4-a05e-4508c80045fd
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Import a GPO from Production
-
-
-If changes are made to a controlled Group Policy Object (GPO) outside of Advanced Group Policy Management (AGPM), you can import a copy of the GPO from the production environment of the domain and save it to the archive to bring the archive and the production environment to a consistent state. (To import an uncontrolled GPO, control the GPO. See [Request Control of an Uncontrolled GPO](request-control-of-an-uncontrolled-gpo-agpm40.md).)
-
-A user account with the Editor, Approver, or AGPM Administrator (Full Control) role or necessary permissions in AGPM is required to complete this procedure. Review the details in "Additional considerations" in this topic.
-
-**To import a GPO from the production environment of the domain**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. On the **Contents** tab, click the **Controlled** tab to display the controlled GPOs.
-
-3. Right-click the GPO, and then click **Import from Production**.
-
-4. Type a comment for the audit trail of the GPO, and then click **OK**.
-
-### Additional considerations
-
-- By default, you must be an Editor, Approver, or AGPM Administrator (Full Control) to perform this procedure. Specifically, you must have **List Contents** and either **Edit Settings**, **Deploy GPO**, or **Delete GPO** permissions for the GPO.
-
-### Additional references
-
-- [Creating or Controlling a GPO](creating-or-controlling-a-gpo-agpm40-ed.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/import-a-gpo-from-production-approver.md b/mdop/agpm/import-a-gpo-from-production-approver.md
deleted file mode 100644
index 0f31b8a9c4..0000000000
--- a/mdop/agpm/import-a-gpo-from-production-approver.md
+++ /dev/null
@@ -1,49 +0,0 @@
----
-title: Import a GPO from Production
-description: Import a GPO from Production
-author: dansimp
-ms.assetid: 071270fa-1890-40ce-ab89-ce070a54aa59
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Import a GPO from Production
-
-
-If changes are made to a controlled Group Policy object (GPO) outside of Advanced Group Policy Management (AGPM), you can import a copy of the GPO from the production environment and save it to the archive to bring the archive and the production environment to a consistent state. (To import an uncontrolled GPO, control the GPO. See [Control a Previously Uncontrolled GPO](control-a-previously-uncontrolled-gpo.md).)
-
-A user account with the Editor, Approver, or AGPM Administrator (Full Control) role or necessary permissions in Advanced Group Policy Management is required to complete this procedure. Review the details in "Additional considerations" in this topic.
-
-**To import a GPO from the production environment**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. On the **Contents** tab, click the **Controlled** tab to display the controlled GPOs.
-
-3. Right-click the GPO, and then click **Import from Production**.
-
-4. Type a comment for the audit trail of the GPO, and then click **OK**.
-
-### Additional considerations
-
-- By default, you must be an Editor, Approver, or AGPM Administrator (Full Control) to perform this procedure. Specifically, you must have **List Contents** and either **Edit Settings**, **Deploy GPO**, or **Delete GPO** permissions for the GPO.
-
-### Additional references
-
-- [Creating, Controlling, or Importing a GPO](creating-controlling-or-importing-a-gpo-approver.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/import-a-gpo-from-production-editor-agpm30ops.md b/mdop/agpm/import-a-gpo-from-production-editor-agpm30ops.md
deleted file mode 100644
index 272f402550..0000000000
--- a/mdop/agpm/import-a-gpo-from-production-editor-agpm30ops.md
+++ /dev/null
@@ -1,49 +0,0 @@
----
-title: Import a GPO from Production
-description: Import a GPO from Production
-author: dansimp
-ms.assetid: ad90f13e-e73c-400f-b86f-c12f2e75d19d
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Import a GPO from Production
-
-
-If changes are made to a controlled Group Policy Object (GPO) outside of Advanced Group Policy Management (AGPM), you can import a copy of the GPO from the production environment and save it to the archive to bring the archive and the production environment to a consistent state. (To import an uncontrolled GPO, control the GPO. See [Control an Uncontrolled GPO](control-an-uncontrolled-gpo-agpm30ops.md).)
-
-A user account with the Editor, Approver, or AGPM Administrator (Full Control) role or necessary permissions in AGPM is required to complete this procedure. Review the details in "Additional considerations" in this topic.
-
-**To import a GPO from the production environment**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. On the **Contents** tab, click the **Controlled** tab to display the controlled GPOs.
-
-3. Right-click the GPO, and then click **Import from Production**.
-
-4. Type a comment for the audit trail of the GPO, and then click **OK**.
-
-### Additional considerations
-
-- By default, you must be an Editor, Approver, or AGPM Administrator (Full Control) to perform this procedure. Specifically, you must have **List Contents** and either **Edit Settings**, **Deploy GPO**, or **Delete GPO** permissions for the GPO.
-
-### Additional references
-
-- [Creating, Controlling, or Importing a GPO](creating-controlling-or-importing-a-gpo-editor-agpm30ops.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/import-a-gpo-from-production-editor.md b/mdop/agpm/import-a-gpo-from-production-editor.md
deleted file mode 100644
index 15f7c96a1f..0000000000
--- a/mdop/agpm/import-a-gpo-from-production-editor.md
+++ /dev/null
@@ -1,49 +0,0 @@
----
-title: Import a GPO from Production
-description: Import a GPO from Production
-author: dansimp
-ms.assetid: ffa02b2a-2a43-4fc0-a06e-7d4b59022cc3
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Import a GPO from Production
-
-
-If changes are made to a controlled Group Policy object (GPO) outside of Advanced Group Policy Management (AGPM), you can import a copy of the GPO from the production environment and save it to the archive to bring the archive and the production environment to a consistent state. (To import an uncontrolled GPO, control the GPO. See [Request Control of a Previously Uncontrolled GPO](request-control-of-a-previously-uncontrolled-gpo.md).)
-
-A user account with the Editor, Approver, or AGPM Administrator (Full Control) role or necessary permissions in Advanced Group Policy Management is required to complete this procedure. Review the details in "Additional considerations" in this topic.
-
-**To import a GPO from the production environment**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. On the **Contents** tab, click the **Controlled** tab to display the controlled GPOs.
-
-3. Right-click the GPO, and then click **Import from Production**.
-
-4. Type a comment for the audit trail of the GPO, then click **OK**.
-
-### Additional considerations
-
-- By default, you must be an Editor, Approver, or AGPM Administrator (Full Control) to perform this procedure. Specifically, you must have **List Contents** and either **Edit Settings**, **Deploy GPO**, or **Delete GPO** permissions for the GPO.
-
-### Additional references
-
-- [Creating, Controlling, or Importing a GPO](creating-controlling-or-importing-a-gpo-editor.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/index.md b/mdop/agpm/index.md
deleted file mode 100644
index bd78561b83..0000000000
--- a/mdop/agpm/index.md
+++ /dev/null
@@ -1,80 +0,0 @@
----
-title: Advanced Group Policy Management
-description: Advanced Group Policy Management
-author: dansimp
-ms.assetid: 493ca3c3-c3d6-4bb1-9430-dc1e43c86bb0
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 11/23/2017
----
-
-
-# Advanced Group Policy Management
-
-
-Microsoft Advanced Group Policy Management (AGPM) extends the capabilities of the Group Policy Management Console (GPMC) to provide comprehensive change control and improved management for Group Policy Objects (GPOs). AGPM is available as part of the Microsoft Desktop Optimization Pack (MDOP) for Software Assurance.
-
-## AGPM Version Information
-
-
-[AGPM 4.0 SP3](agpm-40-sp3-navengl.md) supports Windows 10, Windows Server 2019, Windows Server 2016, Windows Server 2012 R2, Windows 8.1, Windows Server 2012, Windows Server 2008 R2, Windows 7, Windows Server 2008, and Windows Vista with SP1.
-
-[AGPM 4.0 SP2](agpm-40-sp2-navengl.md) supports Windows Server 2012 R2, Windows 8.1, Windows Server 2012, Windows Server 2008 R2, Windows 7, Windows Server 2008, and Windows Vista with SP1.
-
-[AGPM 4.0 SP1](agpm-40-sp1-navengl.md) supports Windows Server 2012, Windows Server 2008 R2, Windows 7, Windows Server 2008, and Windows Vista with SP1.
-
-[AGPM 4](agpm-4-navengl.md) supports Windows Server 2008 R2, Windows 7, Windows Server 2008, and Windows Vista with SP1.
-
-[AGPM 3](agpm-3-navengl.md) supports Windows Server 2008 and Windows Vista with SP1.
-
-[AGPM 2.5](agpm-25-navengl.md) supports Windows Vista (32-bit) with no service pack and Windows Server 2003 (32-bit).
-
-## Supplemental MDOP Product Guidance
-
-
-In addition to the product documentation available online, supplemental product guidance such as informational videos and virtual labs are available for most MDOP products.
-
-
-
-
-
-## How to Get MDOP
-
-
-MDOP is a suite of products that can help streamline desktop deployment, management, and support across the enterprise. MDOP is available as an additional subscription for Software Assurance customers.
-
-**Evaluate MDOP**
-MDOP is also available for test and evaluation to [MSDN](https://msdn.microsoft.com/subscriptions/downloads/default.aspx?PV=42:178) and [TechNet](https://technet.microsoft.com/subscriptions/downloads/default.aspx?PV=42:178) subscribers in accordance with MSDN and TechNet agreements.
-
-**Download MDOP**
-MDOP subscribers can download the software at the [Microsoft Volume Licensing website (MVLS)](https://go.microsoft.com/fwlink/?LinkId=166331).
-
-**Purchase MDOP**
-Visit the enterprise [Purchase Windows Enterprise Licensing](https://www.microsoft.com/windows/enterprise/how-to-buy.aspx) website to find out how to purchase MDOP for your business.
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/label-the-current-version-of-a-gpo-agpm30ops.md b/mdop/agpm/label-the-current-version-of-a-gpo-agpm30ops.md
deleted file mode 100644
index 12807c514e..0000000000
--- a/mdop/agpm/label-the-current-version-of-a-gpo-agpm30ops.md
+++ /dev/null
@@ -1,51 +0,0 @@
----
-title: Label the Current Version of a GPO
-description: Label the Current Version of a GPO
-author: dansimp
-ms.assetid: 3845211a-0bc9-4875-9906-cb758c443825
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Label the Current Version of a GPO
-
-
-You can label the current version of a Group Policy Object (GPO) for easy identification in its history. You can use a label to identify a known good version to which you could roll back if a problem occurs. Also, by labeling multiple GPOs with the same label at one time, you can mark related GPOs that should be rolled back to the same point if rollback should later be necessary.
-
-A user account with the Editor, Approver, or AGPM Administrator (Full Control) role or necessary permissions in Advanced Group Policy Management (AGPM) is required to complete this procedure. Review the details in "Additional considerations" in this topic.
-
-**To label the current version of GPOs in their histories**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. On the **Contents** tab, click the **Controlled** tab to display the controlled GPOs.
-
-3. Click a GPO for which to label the current version. To select multiple GPOs, press SHIFT and click the last GPO in a contiguous group of GPOs, or press CTRL and click individual GPOs. Right-click a selected GPO, and then click **Label**.
-
-4. Type a label and a comment to be displayed in the history of each GPO selected, and then click **OK**.
-
-5. When the **Progress** window indicates that overall progress is complete, click **Close**.
-
-### Additional considerations
-
-- By default, you must be an Editor, an Approver, or an AGPM Administrator (Full Control) to perform this procedure. Specifically, you must have **List Contents** and either **Edit Settings** or **Deploy GPO** permissions for the GPO.
-
-### Additional references
-
-- [Editing a GPO](editing-a-gpo-agpm30ops.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/label-the-current-version-of-a-gpo-agpm40.md b/mdop/agpm/label-the-current-version-of-a-gpo-agpm40.md
deleted file mode 100644
index 9374aa08cd..0000000000
--- a/mdop/agpm/label-the-current-version-of-a-gpo-agpm40.md
+++ /dev/null
@@ -1,51 +0,0 @@
----
-title: Label the Current Version of a GPO
-description: Label the Current Version of a GPO
-author: dansimp
-ms.assetid: cadc8769-21da-44b0-8122-6cafdb448913
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Label the Current Version of a GPO
-
-
-You can label the current version of a Group Policy Object (GPO) for easy identification in its history. You can use a label to identify a known good version to which you could roll back if a problem occurs. Also, by labeling multiple GPOs with the same label at one time, you can mark related GPOs that should be rolled back to the same point if rollback should later be necessary.
-
-A user account with the Editor, Approver, or AGPM Administrator (Full Control) role or necessary permissions in Advanced Group Policy Management (AGPM) is required to complete this procedure. Review the details in "Additional considerations" in this topic.
-
-**To label the current version of GPOs in their histories**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. On the **Contents** tab, click the **Controlled** tab to display the controlled GPOs.
-
-3. Click a GPO for which to label the current version. To select multiple GPOs, press SHIFT and click the last GPO in a contiguous group of GPOs, or press CTRL and click individual GPOs. Right-click a selected GPO, and then click **Label**.
-
-4. Type a label and a comment to be displayed in the history of each GPO selected, and then click **OK**.
-
-5. When the **Progress** window indicates that overall progress is complete, click **Close**.
-
-### Additional considerations
-
-- By default, you must be an Editor, an Approver, or an AGPM Administrator (Full Control) to perform this procedure. Specifically, you must have **List Contents** and either **Edit Settings** or **Deploy GPO** permissions for the GPO.
-
-### Additional references
-
-- [Editing a GPO](editing-a-gpo-agpm40.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/label-the-current-version-of-a-gpo.md b/mdop/agpm/label-the-current-version-of-a-gpo.md
deleted file mode 100644
index e4608abdad..0000000000
--- a/mdop/agpm/label-the-current-version-of-a-gpo.md
+++ /dev/null
@@ -1,51 +0,0 @@
----
-title: Label the Current Version of a GPO
-description: Label the Current Version of a GPO
-author: dansimp
-ms.assetid: 5e4e50f8-e4a8-4bda-aac4-1569d5fbd6a7
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Label the Current Version of a GPO
-
-
-You can label the current version of a Group Policy object (GPO) for easy identification in its history. You can use a label to identify a known good version to which you could roll back if a problem occurs. Also, by labeling multiple GPOs with the same label at one time, you can mark related GPOs that should be rolled back to the same point if rollback should later be necessary.
-
-A user account with the Editor, Approver, or AGPM Administrator (Full Control) role or necessary permissions in Advanced Group Policy Management is required to complete this procedure. Review the details in "Additional considerations" in this topic.
-
-**To label the current version of GPOs in their histories**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. On the **Contents** tab, click the **Controlled** tab to display the controlled GPOs.
-
-3. Click a GPO for which to label the current version. To select multiple GPOs, press SHIFT and click the last GPO in a contiguous group of GPOs, or press CTRL and click individual GPOs. Right-click a selected GPO, and then click **Label**.
-
-4. Type a label and a comment to be displayed in the history of each GPO selected, and then click **OK**.
-
-5. When the **Progress** window indicates that overall progress is complete, click **Close**.
-
-### Additional considerations
-
-- By default, you must be an Editor, an Approver, or an AGPM Administrator (Full Control) to perform this procedure. Specifically, you must have **List Contents** and either **Edit Settings** or **Deploy GPO** permissions for the GPO.
-
-### Additional references
-
-- [Editing a GPO](editing-a-gpo.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/limit-the-gpo-versions-stored-agpm30ops.md b/mdop/agpm/limit-the-gpo-versions-stored-agpm30ops.md
deleted file mode 100644
index 35f49b04fd..0000000000
--- a/mdop/agpm/limit-the-gpo-versions-stored-agpm30ops.md
+++ /dev/null
@@ -1,56 +0,0 @@
----
-title: Limit the GPO Versions Stored
-description: Limit the GPO Versions Stored
-author: dansimp
-ms.assetid: da14edc5-0c36-4c54-b122-861c86b99eb1
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Limit the GPO Versions Stored
-
-
-By default, all versions of every controlled Group Policy Object (GPO) are retained in the archive on the AGPM Server. However, you can limit the number of versions retained for each GPO and delete older versions when that limit is exceeded. When GPO versions are deleted, a record of the version remains in the history of the GPO, but the GPO version itself is deleted from the archive.
-
-A user account with the AGPM Administrator (Full Control) role or necessary permissions in Advanced Group Policy Management (AGPM) is required to complete this procedure. Review the details in "Additional considerations" in this topic.
-
-**To limit the number of GPO versions stored**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. In the details pane, click the **AGPM Server** tab.
-
-3. Select the **Delete old versions of each GPO from the archive** check box, and type the maximum number of GPO versions to store for each GPO, not including the current version. To retain only the current version, enter 0. The maximum must be no greater than 999.
-
- **Important**
- Only GPO versions displayed on the **Unique Versions** tab of the **History** window count toward the limit.
-
-
-
-4. Click the **Apply** button.
-
-### Additional considerations
-
-- By default, you must be an AGPM Administrator (Full Control) to perform this procedure. Specifically, you must have **List Contents** and **Modify Options** permissions for the domain.
-
-- You can prevent a GPO version from being deleted by marking it in the history as ineligible for deletion. To do so, right-click the version in the history of the GPO and click **Do Not Delete**.
-
-### Additional references
-
-- [Managing the Archive](managing-the-archive.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/limit-the-gpo-versions-stored-agpm40.md b/mdop/agpm/limit-the-gpo-versions-stored-agpm40.md
deleted file mode 100644
index 6d48c8c1eb..0000000000
--- a/mdop/agpm/limit-the-gpo-versions-stored-agpm40.md
+++ /dev/null
@@ -1,56 +0,0 @@
----
-title: Limit the GPO Versions Stored
-description: Limit the GPO Versions Stored
-author: dansimp
-ms.assetid: d802c7b6-f303-4b23-aefd-f19f1300b0ff
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Limit the GPO Versions Stored
-
-
-By default, all versions of every controlled Group Policy Object (GPO) are retained in the archive on the AGPM Server. However, you can limit the number of versions retained for each GPO and delete older versions when that limit is exceeded. When GPO versions are deleted, a record of the version remains in the history of the GPO, but the GPO version itself is deleted from the archive.
-
-A user account with the AGPM Administrator (Full Control) role or necessary permissions in Advanced Group Policy Management (AGPM) is required to complete this procedure. Review the details in "Additional considerations" in this topic.
-
-**To limit the number of GPO versions stored**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. In the details pane, click the **AGPM Server** tab.
-
-3. Select the **Delete old versions of each GPO from the archive** check box, and type the maximum number of GPO versions to store for each GPO, not including the current version. To retain only the current version, enter 0. The maximum must be no greater than 999.
-
- **Important**
- Only GPO versions displayed on the **Unique Versions** tab of the **History** window count toward the limit.
-
-
-
-4. Click the **Apply** button.
-
-### Additional considerations
-
-- By default, you must be an AGPM Administrator (Full Control) to perform this procedure. Specifically, you must have **List Contents** and **Modify Options** permissions for the domain.
-
-- You can prevent a GPO version from being deleted by marking it in the history as ineligible for deletion. To do so, right-click the version in the history of the GPO and click **Do Not Delete**.
-
-### Additional references
-
-- [Managing the Archive](managing-the-archive-agpm40.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/logging-and-tracing-settings-agpm30ops.md b/mdop/agpm/logging-and-tracing-settings-agpm30ops.md
deleted file mode 100644
index 82b6e1ce94..0000000000
--- a/mdop/agpm/logging-and-tracing-settings-agpm30ops.md
+++ /dev/null
@@ -1,62 +0,0 @@
----
-title: Logging and Tracing Settings
-description: Logging and Tracing Settings
-author: dansimp
-ms.assetid: 858b6fbf-65b4-42fa-95a9-69b04e5734d7
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Logging and Tracing Settings
-
-
-The Administrative template settings for Advanced Group Policy Management (AGPM) enable you to centrally configure logging and tracing options for AGPM Servers and clients to which a Group Policy Object (GPO) with these settings is applied.
-
-The following setting is available under Computer Configuration\\Policies\\Administrative Templates\\Windows Components\\AGPM when editing a GPO.
-
-**Trace file locations**:
-
-- Client: %LocalAppData%\\Microsoft\\AGPM\\agpm.log
-
-- Server: %ProgramData%\\Microsoft\\AGPM\\agpmserv.log
-
-
-
-
-
-
-
-
-
Setting
-
Effect
-
-
-
-
-
AGPM: Configure logging
-
This policy setting allows you to turn on and configure logging for AGPM. This setting affects both client and server components of AGPM.
-
-
-
-
-
-
-### Additional references
-
-- [Administrative Templates Folder](administrative-templates-folder-agpm30ops.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/logging-and-tracing-settings-agpm40.md b/mdop/agpm/logging-and-tracing-settings-agpm40.md
deleted file mode 100644
index fd2477a527..0000000000
--- a/mdop/agpm/logging-and-tracing-settings-agpm40.md
+++ /dev/null
@@ -1,62 +0,0 @@
----
-title: Logging and Tracing Settings
-description: Logging and Tracing Settings
-author: dansimp
-ms.assetid: 66d03306-80d8-4132-bf71-2827157b1fc9
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Logging and Tracing Settings
-
-
-The Administrative template settings for Advanced Group Policy Management (AGPM) enable you to centrally configure logging and tracing options for AGPM Servers and clients to which a Group Policy Object (GPO) with these settings is applied.
-
-The following setting is available under Computer Configuration\\Policies\\Administrative Templates\\Windows Components\\AGPM when editing a GPO.
-
-**Trace file locations**:
-
-- Client: %LocalAppData%\\Microsoft\\AGPM\\agpm.log
-
-- Server: %ProgramData%\\Microsoft\\AGPM\\agpmserv.log
-
-
-
-
-
-
-
-
-
Setting
-
Effect
-
-
-
-
-
AGPM: Configure logging
-
This policy setting allows you to turn on and configure logging for AGPM. This setting affects both client and server components of AGPM.
-
-
-
-
-
-
-### Additional references
-
-- [Administrative Templates Folder](administrative-templates-folder-agpm40.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/logging-and-tracing-settings.md b/mdop/agpm/logging-and-tracing-settings.md
deleted file mode 100644
index ff3a6190db..0000000000
--- a/mdop/agpm/logging-and-tracing-settings.md
+++ /dev/null
@@ -1,63 +0,0 @@
----
-title: Logging and Tracing Settings
-description: Logging and Tracing Settings
-author: dansimp
-ms.assetid: db6b43c7-fdde-4d11-b5ab-a81346e56940
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Logging and Tracing Settings
-
-
-The Administrative Template settings for Advanced Group Policy Management (AGPM) enable you to centrally configure logging and tracing options for AGPM Servers and clients to which a Group Policy object (GPO) with these settings is applied.
-
-The following setting is available under Computer Configuration\\Administrative Templates\\Windows Components\\AGPM in the **Group Policy Object Editor** when editing a GPO in the Group Policy Management Console (GPMC). If this path is not visible, right-click **Administrative Templates**, and add the agpm.admx or agpm.adm template.
-
-**Trace file locations**:
-
-- Client: %LocalAppData%\\Microsoft\\AGPM\\agpm.log
-
-- Server: %CommonAppData%\\Microsoft\\AGPM\\agpmserv.log
-
-
-
-
-
-
-
-
-
Setting
-
Effect
-
-
-
-
-
AGPM Logging
-
If enabled, this setting configures whether tracing is turned on and the level of detail. This setting affects both client and server components of AGPM.
-
If disabled or not configured, this setting has no effect.
-
-
-
-
-
-
-### Additional references
-
-- [Administrative Template Settings](administrative-template-settings.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/managing-the-agpm-service-agpm30ops.md b/mdop/agpm/managing-the-agpm-service-agpm30ops.md
deleted file mode 100644
index 91793ce0d5..0000000000
--- a/mdop/agpm/managing-the-agpm-service-agpm30ops.md
+++ /dev/null
@@ -1,44 +0,0 @@
----
-title: Managing the AGPM Service
-description: Managing the AGPM Service
-author: dansimp
-ms.assetid: a522b1f1-c57b-43aa-9d75-acc6f9bedbf9
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Managing the AGPM Service
-
-
-The AGPM Service is a Windows service that acts as a security proxy, managing client access to Group Policy Objects (GPOs) in the archive and production environment. It enforces Advanced Group Policy Management (AGPM) delegation and provides an enhanced level of security. The AGPM Service is hosted on the server on which the Microsoft Advanced Group Policy Management - Server is installed.
-
-**Caution**
-Do not modify settings for the AGPM Service through **Administrative Tools** and **Services** in the operating system. Doing so can prevent the AGPM Service from starting.
-
-
-
-- [Start and Stop the AGPM Service](start-and-stop-the-agpm-service-agpm30ops.md)
-
-- [Modify the AGPM Service](modify-the-agpm-service-agpm30ops.md)
-
-### Additional references
-
-- [Move the AGPM Server and the Archive](move-the-agpm-server-and-the-archive.md)
-
-- [Performing AGPM Administrator Tasks](performing-agpm-administrator-tasks-agpm30ops.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/managing-the-agpm-service-agpm40.md b/mdop/agpm/managing-the-agpm-service-agpm40.md
deleted file mode 100644
index 01b91e94ad..0000000000
--- a/mdop/agpm/managing-the-agpm-service-agpm40.md
+++ /dev/null
@@ -1,44 +0,0 @@
----
-title: Managing the AGPM Service
-description: Managing the AGPM Service
-author: dansimp
-ms.assetid: 48ca02aa-6acf-403b-afd4-66ae8a953246
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Managing the AGPM Service
-
-
-The AGPM Service is a Windows service that acts as a security proxy, managing client access to Group Policy Objects (GPOs) in the archive and production environment of the domain. It enforces Advanced Group Policy Management (AGPM) delegation and provides an enhanced level of security. The AGPM Service is hosted on the server on which the Microsoft Advanced Group Policy Management - Server is installed.
-
-**Caution**
-Do not modify settings for the AGPM Service through **Administrative Tools** and **Services** in the operating system. Doing so can prevent the AGPM Service from starting.
-
-
-
-- [Start and Stop the AGPM Service](start-and-stop-the-agpm-service-agpm40.md)
-
-- [Modify the AGPM Service](modify-the-agpm-service-agpm40.md)
-
-### Additional references
-
-- [Move the AGPM Server and the Archive](move-the-agpm-server-and-the-archive-agpm40.md)
-
-- [Performing AGPM Administrator Tasks](performing-agpm-administrator-tasks-agpm40.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/managing-the-agpm-service.md b/mdop/agpm/managing-the-agpm-service.md
deleted file mode 100644
index 43064fd9ba..0000000000
--- a/mdop/agpm/managing-the-agpm-service.md
+++ /dev/null
@@ -1,42 +0,0 @@
----
-title: Managing the AGPM Service
-description: Managing the AGPM Service
-author: dansimp
-ms.assetid: 331f64d2-1236-4711-81b4-1b92f019bfa5
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Managing the AGPM Service
-
-
-The AGPM Service is a Windows service that acts as a security proxy, managing client access to Group Policy objects (GPOs) in the archive and production environment. It enforces Advanced Group Policy Management (AGPM) delegation and provides an enhanced level of security. The AGPM Service is hosted on the server on which the Microsoft Advanced Group Policy Management - Server is installed.
-
-**Caution**
-Do not modify settings for the AGPM Service through **Administrative Tools** and **Services** in the operating system. Doing so can prevent the AGPM Service from starting.
-
-
-
-- [Start and Stop the AGPM Service](start-and-stop-the-agpm-service.md)
-
-- [Modify the Archive Path](modify-the-archive-path.md)
-
-- [Modify the AGPM Service Account](modify-the-agpm-service-account.md)
-
-- [Modify the Port on Which the AGPM Service Listens](modify-the-port-on-which-the-agpm-service-listens.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/managing-the-archive-agpm40.md b/mdop/agpm/managing-the-archive-agpm40.md
deleted file mode 100644
index ea712c84ad..0000000000
--- a/mdop/agpm/managing-the-archive-agpm40.md
+++ /dev/null
@@ -1,51 +0,0 @@
----
-title: Managing the Archive
-description: Managing the Archive
-author: dansimp
-ms.assetid: b11a3d71-74ea-4dd7-b243-6f2880b7af2d
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Managing the Archive
-
-
-In Advanced Group Policy Management (AGPM), as an AGPM Administrator (Full Control), you manage access to the archive and have the option to limit the number of versions of each Group Policy Object (GPO) stored in the archive. You can delegate access to GPOs in the archive at the domain level or GPO level. Additionally, you can back up the archive so that you may be able to recover it if a disaster occurs.
-
-As an AGPM Administrator, you can export a GPO to a file, copy the file to another forest, and then import the GPO into a domain in that forest. Unlike an Editor, you can import policy settings from a GPO backup directly into a new controlled GPO when you create it. For information about how to export a GPO, see [Export a GPO to a File](export-a-gpo-to-a-file.md).
-
-- [Delegate Domain-Level Access to the Archive](delegate-domain-level-access-to-the-archive-agpm40.md)
-
-- [Delegate Access to an Individual GPO in the Archive](delegate-access-to-an-individual-gpo-in-the-archive-agpm40.md)
-
-- [Limit the GPO Versions Stored](limit-the-gpo-versions-stored-agpm40.md)
-
-- [Import a GPO from a File](import-a-gpo-from-a-file-agpmadmin.md)
-
-- [Back Up the Archive](back-up-the-archive-agpm40.md)
-
-- [Restore the Archive from a Backup](restore-the-archive-from-a-backup-agpm40.md)
-
-### Additional references
-
-- For information about how to delegate access to GPOs in the production environment, see [Delegate Access to the Production Environment](delegate-access-to-the-production-environment-agpm40.md).
-
-- For information about how to move the archive, see [Move the AGPM Server and the Archive](move-the-agpm-server-and-the-archive-agpm40.md).
-
-- [Performing AGPM Administrator Tasks](performing-agpm-administrator-tasks-agpm40.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/managing-the-archive.md b/mdop/agpm/managing-the-archive.md
deleted file mode 100644
index eeacbaf3a0..0000000000
--- a/mdop/agpm/managing-the-archive.md
+++ /dev/null
@@ -1,47 +0,0 @@
----
-title: Managing the Archive
-description: Managing the Archive
-author: dansimp
-ms.assetid: 7c7654e9-ab0e-4531-8ef7-ae77ef391620
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Managing the Archive
-
-
-In Advanced Group Policy Management (AGPM), as an AGPM Administrator (Full Control), you manage access to the archive and have the option to limit the number of versions of each Group Policy Object (GPO) stored in the archive. You can delegate access to GPOs in the archive at the domain level or GPO level.
-
-- [Delegate Domain-Level Access to the Archive](delegate-domain-level-access-to-the-archive-agpm30ops.md)
-
-- [Delegate Access to an Individual GPO in the Archive](delegate-access-to-an-individual-gpo-in-the-archive-agpm30ops.md)
-
-- [Limit the GPO Versions Stored](limit-the-gpo-versions-stored-agpm30ops.md)
-
-- [Back Up the Archive](back-up-the-archive.md)
-
-- [Restore the Archive from a Backup](restore-the-archive-from-a-backup.md)
-
-### Additional references
-
-- For information about how to delegate access to GPOs in the production environment, see [Delegate Access to the Production Environment](delegate-access-to-the-production-environment-agpm30ops.md).
-
-- For information about how to move the archive, see [Move the AGPM Server and the Archive](move-the-agpm-server-and-the-archive.md).
-
-- [Performing AGPM Administrator Tasks](performing-agpm-administrator-tasks-agpm30ops.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/modify-the-agpm-service-account.md b/mdop/agpm/modify-the-agpm-service-account.md
deleted file mode 100644
index 4481c6d031..0000000000
--- a/mdop/agpm/modify-the-agpm-service-account.md
+++ /dev/null
@@ -1,67 +0,0 @@
----
-title: Modify the AGPM Service Account
-description: Modify the AGPM Service Account
-author: dansimp
-ms.assetid: 0d8d8c7b-f299-4fee-8414-406492156942
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Modify the AGPM Service Account
-
-
-The AGPM Service is a Windows service that acts as a security proxy, managing client access to Group Policy objects (GPOs) in the archive and production environment. If this service is stopped or disabled, AGPM clients cannot perform operations through the server.
-
-The archive path and AGPM Service Account are configured during the installation of AGPM Server and can be changed afterward through **Add or Remove Programs** on the AGPM Server.
-
-**Caution**
-Do not modify settings for the AGPM Service through **Administrative Tools** and **Services** in the operating system. Doing so can prevent the AGPM Service from starting.
-
-
-
-A user account that is a member of the Domain Admins group and has access to the AGPM Server (the computer on which Microsoft Advanced Group Policy Management - Server is installed) is required to complete this procedure.
-
-**Important**
-The AGPM Service Account must have full access to the GPOs that it will manage and will be granted **Log On As A Service** permission. If you will be managing GPOs on a single domain, you can make the Local System account for the primary domain controller the AGPM Service Account.
-
-If you will be managing GPOs on multiple domains or if a member server will be the AGPM Server, you should configure a different account as the AGPM Service Account because the Local System account for one domain controller cannot access GPOs on other domains.
-
-
-
-**To modify the AGPM Service Account**
-
-1. On the computer on which Microsoft Advanced Group Policy Management - Server is installed, click **Start**, click **Control Panel**, click **Add or Remove Programs**.
-
-2. Click **Microsoft Advanced Group Policy Management - Server**, and then click **Change**.
-
-3. Click **Next**, and then click **Modify**.
-
-4. Follow the instructions on screen to configure settings for the AGPM Service:
-
- 1. For the archive path, confirm or change the location for the archive relative to the AGPM Server. The archive path can point to a folder on the AGPM Server or elsewhere, but the location should have sufficient space to store all GPOs and history data managed by this AGPM Server.
-
- 2. Enter new credentials for the AGPM Service Account.
-
- 3. For the archive owner, enter the credentials of an AGPM Administrator (Full Control).
-
-5. Click **Change**, and when the installation is complete click **Finish**.
-
-### Additional references
-
-- [Managing the AGPM Service](managing-the-agpm-service.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/modify-the-agpm-service-agpm30ops.md b/mdop/agpm/modify-the-agpm-service-agpm30ops.md
deleted file mode 100644
index 814f3ad6d7..0000000000
--- a/mdop/agpm/modify-the-agpm-service-agpm30ops.md
+++ /dev/null
@@ -1,94 +0,0 @@
----
-title: Modify the AGPM Service
-description: Modify the AGPM Service
-author: dansimp
-ms.assetid: 3485f85f-59d1-48dc-8748-36826214dcb1
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Modify the AGPM Service
-
-
-The AGPM Service is a Windows service that acts as a security proxy, managing client access to Group Policy Objects (GPOs) in the archive and production environment. If this service is stopped or disabled, AGPM Clients cannot perform operations through the server. You can modify the archive path, the AGPM Service Account, and the port on which the AGPM Service listens.
-
-**Caution**
-Do not modify settings for the AGPM Service through **Administrative Tools** and **Services** in the operating system. Doing so can prevent the AGPM Service from starting.
-
-
-
-A user account that is a member of the Domain Admins group and has access to the AGPM Server (the computer on which Microsoft Advanced Group Policy Management - Server is installed) is required to complete this procedure. Additionally, you must provide credentials for the AGPM Service Account to complete this procedure.
-
-**To modify the AGPM Service**
-
-1. On the computer on which Microsoft Advanced Group Policy Management - Server is installed:
-
- - For Windows Server 2008, click **Start**, **Control Panel**, and **Programs and Features**.
-
- - For Windows Vista, click **Start**, **Control Panel**, **Programs**, and **Programs and Features**.
-
-2. Right-click **Microsoft Advanced Group Policy Management - Server**, and then click **Change**.
-
-3. Click **Next**, and then click **Modify**.
-
-4. Follow the instructions to configure the AGPM Service:
-
- 1. In the **Archive Path** dialog box, enter a new location for the archive relative to the AGPM Server, or confirm the current archive path, and then click **Next**.
-
- **Important**
- The archive path can point to a folder on the AGPM Server or elsewhere, but the location should have sufficient space to store all GPOs and history data managed by this AGPM Server.
-
-
-
- 2. In the **AGPM Service Account** dialog box, enter credentials for a service account under which the AGPM Service will run, and click **Next**.
-
- **Important**
- Modifying the installation clears the credentials for the AGPM Service Account. You must re-enter credentials, but they are not required to match the credentials used during the original installation.
-
- The AGPM Service Account must have full access to the GPOs that it will manage and will be granted **Log On As A Service** permission. If you will be managing GPOs on a single domain, you can make the Local System account for the primary domain controller the AGPM Service Account.
-
- If you will be managing GPOs on multiple domains or if a member server will be the AGPM Server, you should configure a different account as the AGPM Service Account because the Local System account for one domain controller cannot access GPOs on other domains.
-
-
-
- 3. In the **Archive Owner** dialog box, enter the user name of an AGPM Administrator (Full Control) or group of AGPM Administrators, and click **Next**.
-
- **Note**
- Modifying the installation clears the credentials for the Archive Owner. You must re-enter credentials, but they are not required to match the credentials used during the original installation.
-
-
-
- 4. In the **Port Configuration** dialog box, type a new port on which the AGPM Service should listen or confirm the port currently selected, and click **Next**.
-
- **Note**
- By default, the AGPM Service listens on port 4600.
-
- If you manually configure port exceptions or have rules configuring port exceptions, you can clear the **Add port exception to firewall** check box.
-
-
-
-5. Click **Change**, and when the installation is complete click **Finish**.
-
-6. If you have changed the port on which the AGPM Service listens, modify the port in the AGPM Server connection for each Group Policy administrator. (For more information, see [Configure AGPM Server Connections](configure-agpm-server-connections-agpm30ops.md).)
-
-7. Repeat for each AGPM Server to which the configuration changes should be applied.
-
-### Additional references
-
-- [Managing the AGPM Service](managing-the-agpm-service-agpm30ops.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/modify-the-agpm-service-agpm40.md b/mdop/agpm/modify-the-agpm-service-agpm40.md
deleted file mode 100644
index 31925f9da1..0000000000
--- a/mdop/agpm/modify-the-agpm-service-agpm40.md
+++ /dev/null
@@ -1,90 +0,0 @@
----
-title: Modify the AGPM Service
-description: Modify the AGPM Service
-author: dansimp
-ms.assetid: 3239d088-bb86-4ec4-bc56-dbe8f1c710f5
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Modify the AGPM Service
-
-
-The AGPM Service is a Windows service that acts as a security proxy, managing client access to Group Policy Objects (GPOs) in the archive and production environment of the domain. If this service is stopped or disabled, AGPM Clients cannot perform operations through the server. You can modify the archive path, the AGPM Service Account, and the port on which the AGPM Service listens.
-
-**Caution**
-Do not modify settings for the AGPM Service through **Administrative Tools** and **Services** in the operating system. Doing so can prevent the AGPM Service from starting.
-
-
-
-A user account that is a member of the Domain Admins group and has access to the AGPM Server (the computer on which Microsoft Advanced Group Policy Management - Server is installed) is required to complete this procedure. Additionally, you must provide credentials for the AGPM Service Account to complete this procedure.
-
-**To modify the AGPM Service**
-
-1. On the computer on which Microsoft Advanced Group Policy Management - Server is installed, click **Start**, **Control Panel**, **Programs**, and **Programs and Features**.
-
-2. Right-click **Microsoft Advanced Group Policy Management - Server**, and then click **Change**.
-
-3. Click **Next**, and then click **Modify**.
-
-4. Follow the instructions to configure the AGPM Service:
-
- 1. In the **Archive Path** dialog box, enter a new location for the archive relative to the AGPM Server, or confirm the current archive path, and then click **Next**.
-
- **Important**
- The archive path can point to a folder on the AGPM Server or elsewhere, but the location should have sufficient space to store all GPOs and history data managed by this AGPM Server.
-
-
-
- 2. In the **AGPM Service Account** dialog box, enter credentials for a service account under which the AGPM Service will run, and click **Next**.
-
- **Important**
- Modifying the installation clears the credentials for the AGPM Service Account. You must re-enter credentials, but they are not required to match the credentials used during the original installation.
-
- The AGPM Service Account must have full access to the GPOs that it will manage and will be granted **Log On As A Service** permission. If you will be managing GPOs on a single domain, you can make the Local System account for the primary domain controller the AGPM Service Account.
-
- If you will be managing GPOs on multiple domains or if a member server will be the AGPM Server, you should configure a different account as the AGPM Service Account because the Local System account for one domain controller cannot access GPOs on other domains.
-
-
-
- 3. In the **Archive Owner** dialog box, enter the user name of an AGPM Administrator (Full Control) or group of AGPM Administrators, and click **Next**.
-
- **Note**
- Modifying the installation clears the credentials for the Archive Owner. You must re-enter credentials, but they are not required to match the credentials used during the original installation.
-
-
-
- 4. In the **Port Configuration** dialog box, type a new port on which the AGPM Service should listen or confirm the port currently selected, and click **Next**.
-
- **Note**
- By default, the AGPM Service listens on port 4600.
-
- If you manually configure port exceptions or have rules configuring port exceptions, you can clear the **Add port exception to firewall** check box.
-
-
-
-5. Click **Change**, and when the installation is complete click **Finish**.
-
-6. If you have changed the port on which the AGPM Service listens, modify the port in the AGPM Server connection for each Group Policy administrator. (For more information, see [Configure AGPM Server Connections](configure-agpm-server-connections-agpm40.md).)
-
-7. Repeat for each AGPM Server to which the configuration changes should be applied.
-
-### Additional references
-
-- [Managing the AGPM Service](managing-the-agpm-service-agpm40.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/modify-the-archive-path.md b/mdop/agpm/modify-the-archive-path.md
deleted file mode 100644
index a442dba78a..0000000000
--- a/mdop/agpm/modify-the-archive-path.md
+++ /dev/null
@@ -1,64 +0,0 @@
----
-title: Modify the Archive Path
-description: Modify the Archive Path
-author: dansimp
-ms.assetid: 6d90daf9-58db-4166-b5b3-e84bb261164a
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Modify the Archive Path
-
-
-The archive path is the location of the archive relative to the AGPM Server. The archive path can point to a folder on the AGPM Server or on another server in the same forest.
-
-The archive path and AGPM Service Account are configured during the installation of AGPM Server and can be changed afterward through **Add or Remove Programs** on the AGPM Server.
-
-A user account that is a member of the Domain Admins group and has access to the AGPM Server (the computer on which Microsoft Advanced Group Policy Management - Server is installed) is required to complete this procedure.
-
-**To modify the archive path**
-
-1. On the computer on which Microsoft Advanced Group Policy Management - Server is installed, click **Start**, click **Control Panel**, click **Add or Remove Programs**.
-
-2. Click **Microsoft Advanced Group Policy Management - Server**, and then click **Change**.
-
-3. Click **Next**, and then click **Modify**.
-
-4. Follow the instructions on screen to configure settings for the AGPM Service:
-
- 1. For the archive path, enter a new location for the archive relative to the AGPM Server. The archive path can point to a folder on the AGPM Server or elsewhere, but the location should have sufficient space to store all GPOs and history data managed by this AGPM Server.
-
- 2. Enter credentials for the AGPM Service Account.
-
- **Important**
- Modifying the installation clears the credentials for the AGPM Service Account. You must re-enter credentials, but they are not required to match the credentials used during the original installation.
-
- The AGPM Service Account must have full access to the GPOs that it will manage. If you will be managing GPOs on a single domain, you can make the Local System account for the primary domain controller the AGPM Service Account.
-
- If you will be managing GPOs on multiple domains or if a member server will be the AGPM Server, you should configure a different account as the AGPM Service Account because the Local System account for one domain controller cannot access GPOs on other domains.
-
-
-
- 3. For the archive owner, enter the credentials of an AGPM Administrator (Full Control).
-
-5. Click **Change**, and when the installation is complete click **Finish**.
-
-### Additional references
-
-- [Managing the AGPM Service](managing-the-agpm-service.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/modify-the-port-on-which-the-agpm-service-listens.md b/mdop/agpm/modify-the-port-on-which-the-agpm-service-listens.md
deleted file mode 100644
index d4481a3d70..0000000000
--- a/mdop/agpm/modify-the-port-on-which-the-agpm-service-listens.md
+++ /dev/null
@@ -1,54 +0,0 @@
----
-title: Modify the Port on Which the AGPM Service Listens
-description: Modify the Port on Which the AGPM Service Listens
-author: dansimp
-ms.assetid: a82c6873-e916-4a04-b263-aa612cd6956b
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Modify the Port on Which the AGPM Service Listens
-
-
-The AGPM Service is a Windows service that acts as a security proxy, managing client access to Group Policy objects (GPOs) in the archive and production environment. By default, the AGPM Service listens on port 4600. You can change this port by modifying the Advanced Group Policy Management (AGPM) archive index file for each archive.
-
-**Note**
-Before modifying the port on which the AGPM Service listens, it is recommended that you back up the AGPM archive index file (gpostate.xml). This file is located in the folder entered as the archive path during the installation of Advanced Group Policy Management - Server. By default, this location of this file is %CommonAppData%\\Microsoft\\AGPM\\gpostate.xml on the AGPM Server. If you do not know which computer hosts the archive, you can follow the procedure for modifying the archive path to display the current archive path. For more information, see [Modify the Archive Path](modify-the-archive-path.md).
-
-
-
-A user account with access to the AGPM Server (the computer on which the AGPM Service is installed) and the archive index file is required to complete this procedure.
-
-**To modify the port on which the AGPM Service listens**
-
-1. On the computer hosting the archive, open the archive index file (gpostate.xml) in a text editor.
-
-2. In the file, search for **agpm:port="4600"**.
-
-3. Replace **4600** with the port on which the AGPM Service should listen; then, save and close the file.
-
-4. On the AGPM Server, restart the AGPM Service. (For more information, see [Start and Stop the AGPM Service](start-and-stop-the-agpm-service.md).)
-
-5. Modify the port in the AGPM Server connection for each Group Policy administrator. (For more information, see [Configure the AGPM Server Connection](configure-the-agpm-server-connection.md).)
-
-6. Repeat for each archive and AGPM Server.
-
-### Additional references
-
-- [Managing the AGPM Service](managing-the-agpm-service.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/move-the-agpm-server-and-the-archive-agpm40.md b/mdop/agpm/move-the-agpm-server-and-the-archive-agpm40.md
deleted file mode 100644
index 065322c6a7..0000000000
--- a/mdop/agpm/move-the-agpm-server-and-the-archive-agpm40.md
+++ /dev/null
@@ -1,82 +0,0 @@
----
-title: Move the AGPM Server and the Archive
-description: Move the AGPM Server and the Archive
-author: dansimp
-ms.assetid: 9ec48d3a-c293-45f0-8939-32ccdc062303
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 08/30/2016
----
-
-
-# Move the AGPM Server and the Archive
-
-
-If you are replacing the AGPM Server and the server on which the archive is hosted, you must move the AGPM Service and the archive. If you prefer, you can move the AGPM Service and the archive separately.
-
-**Note**
-- The AGPM Server is the computer that hosts the AGPM Service and the computer on which Microsoft Advanced Group Policy Management – Server is installed.
-
-- By default, the archive is hosted on the AGPM Server, but you can specify an archive path to host it on another server instead.
-
-
-
-A user account that is a member of the Domain Admins group and has access to the previous and new AGPM Servers is required to complete this procedure. Additionally, you must provide credentials for the AGPM Service Account to be used by the new AGPM Server to complete this procedure.
-
-**To move the AGPM Service and the archive to a different server or servers**
-
-1. Back up the archive. For more information, see [Back Up the Archive](back-up-the-archive-agpm40.md).
-
-2. Move the AGPM Service:
-
- 1. Stop the AGPM Service. For more information, see [Start and Stop the AGPM Service](start-and-stop-the-agpm-service-agpm40.md).
-
- 2. Install Microsoft Advanced Group Policy Management - Server on the new server that will host the AGPM Service. During this process, you specify the new archive path, the location for the archive in relation to the AGPM Server. For more information, see [Step-by-Step Guide for Microsoft Advanced Group Policy Management 4.0](https://go.microsoft.com/fwlink/?LinkId=153505) (https://go.microsoft.com/fwlink/?LinkId=153505) and [Planning Guide for Microsoft Advanced Group Policy Management](https://go.microsoft.com/fwlink/?LinkId=156883) (https://go.microsoft.com/fwlink/?LinkId=156883).
-
- 3. Either an AGPM Administrator (Full Control) must configure the AGPM Server connection for all Group Policy administrators who will use the new AGPM Server and remove the connection for the old AGPM Server, or else each Group Policy administrator must manually configure the new AGPM Server connection and remove the old AGPM Server connection for the AGPM snap-in on their computer. For more information, see [Configure AGPM Server Connections](configure-agpm-server-connections-agpm40.md).
-
- **Note**
- As a best practice, you should uninstall Microsoft Advanced Group Policy Management – Server from the previous AGPM Server. This will ensure that the AGPM Service cannot be unintentionally restarted on that server and potentially cause confusion if any AGPM Server connections to it remain.
-
-
-
-3. Copy the archive from the backup to the new server that will host the archive. For more information, see [Restore the Archive from a Backup](restore-the-archive-from-a-backup-agpm40.md).
-
- **Important**
- If you moved the archive without moving the AGPM Service at the same time:
-
- 1. You must change the archive path to point to the new location for the archive in relation to the AGPM Server. For more information, see [Modify the AGPM Service](modify-the-agpm-service-agpm40.md).
-
- 2. You must re-enter and confirm the password on the **Domain Delegation** tab. For more information, see [Configure E-Mail Notification](configure-e-mail-notification-agpm40.md).
-
-
-
-### Additional references
-
-- [Back Up the Archive](back-up-the-archive-agpm40.md)
-
-- [Restore the Archive from a Backup](restore-the-archive-from-a-backup-agpm40.md)
-
-- [Configure AGPM Server Connections](configure-agpm-server-connections-agpm40.md)
-
-- [Modify the AGPM Service](modify-the-agpm-service-agpm40.md)
-
-- [Step-by-Step Guide for Microsoft Advanced Group Policy Management 4.0](https://go.microsoft.com/fwlink/?LinkId=153505) (https://go.microsoft.com/fwlink/?LinkId=153505)
-
-- [Planning Guide for Microsoft Advanced Group Policy Management](https://go.microsoft.com/fwlink/?LinkId=156883) (https://go.microsoft.com/fwlink/?LinkId=156883)
-
-- [Performing AGPM Administrator Tasks](performing-agpm-administrator-tasks-agpm40.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/move-the-agpm-server-and-the-archive.md b/mdop/agpm/move-the-agpm-server-and-the-archive.md
deleted file mode 100644
index 1c4ba6015e..0000000000
--- a/mdop/agpm/move-the-agpm-server-and-the-archive.md
+++ /dev/null
@@ -1,82 +0,0 @@
----
-title: Move the AGPM Server and the Archive
-description: Move the AGPM Server and the Archive
-author: dansimp
-ms.assetid: 13cb83c4-bb42-4e81-8660-5b7540f473d8
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 08/30/2016
----
-
-
-# Move the AGPM Server and the Archive
-
-
-If you are replacing the AGPM Server and the server on which the archive is hosted, you must move the AGPM Service and the archive. If you prefer, you can move the AGPM Service and the archive separately.
-
-**Note**
-- The AGPM Server is the computer that hosts the AGPM Service and the computer on which Microsoft Advanced Group Policy Management – Server is installed.
-
-- By default, the archive is hosted on the AGPM Server, but you can specify an archive path to host it on another server instead.
-
-
-
-A user account that is a member of the Domain Admins group and has access to the previous and new AGPM Servers is required to complete this procedure. Additionally, you must provide credentials for the AGPM Service Account to be used by the new AGPM Server to complete this procedure.
-
-**To move the AGPM Service and the archive to a different server or servers**
-
-1. Back up the archive. For more information, see [Back Up the Archive](back-up-the-archive.md).
-
-2. Move the AGPM Service:
-
- 1. Stop the AGPM Service. For more information, see [Start and Stop the AGPM Service](start-and-stop-the-agpm-service-agpm30ops.md).
-
- 2. Install Microsoft Advanced Group Policy Management - Server on the new server that will host the AGPM Service. During this process, you specify the new archive path, the location for the archive in relation to the AGPM Server. For more information, see Step-by-Step Guide for Microsoft Advanced Group Policy Management 3.0 () and Planning Guide for Microsoft Advanced Group Policy Management ().
-
- 3. Either an AGPM Administrator (Full Control) must configure the AGPM Server connection for all Group Policy administrators who will use the new AGPM Server and remove the connection for the old AGPM Server, or else each Group Policy administrator must manually configure the new AGPM Server connection and remove the old AGPM Server connection for the AGPM snap-in on their computer. For more information, see [Configure AGPM Server Connections](configure-agpm-server-connections-agpm30ops.md).
-
- **Note**
- As a best practice, you should uninstall Microsoft Advanced Group Policy Management – Server from the previous AGPM Server. This will ensure that the AGPM Service cannot be unintentionally restarted on that server and potentially cause confusion if any AGPM Server connections to it remain.
-
-
-
-3. Copy the archive from the backup to the new server that will host the archive. For more information, see [Restore the Archive from a Backup](restore-the-archive-from-a-backup.md).
-
- **Important**
- If you moved the archive without moving the AGPM Service at the same time:
-
- 1. You must change the archive path to point to the new location for the archive in relation to the AGPM Server. For more information, see [Modify the AGPM Service](modify-the-agpm-service-agpm30ops.md).
-
- 2. You must re-enter and confirm the password on the **Domain Delegation** tab. For more information, see [Configure E-Mail Notification](configure-e-mail-notification-agpm30ops.md).
-
-
-
-### Additional references
-
-- [Back Up the Archive](back-up-the-archive.md)
-
-- [Restore the Archive from a Backup](restore-the-archive-from-a-backup.md)
-
-- [Configure AGPM Server Connections](configure-agpm-server-connections-agpm30ops.md)
-
-- [Modify the AGPM Service](modify-the-agpm-service-agpm30ops.md)
-
-- Step-by-Step Guide for Microsoft Advanced Group Policy Management 3.0 ()
-
-- Planning Guide for Microsoft Advanced Group Policy Management ()
-
-- [Performing AGPM Administrator Tasks](performing-agpm-administrator-tasks-agpm30ops.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/operations-guide-for-microsoft-advanced-group-policy-management-25.md b/mdop/agpm/operations-guide-for-microsoft-advanced-group-policy-management-25.md
deleted file mode 100644
index d84f580b21..0000000000
--- a/mdop/agpm/operations-guide-for-microsoft-advanced-group-policy-management-25.md
+++ /dev/null
@@ -1,61 +0,0 @@
----
-title: Operations Guide for Microsoft Advanced Group Policy Management 2.5
-description: Operations Guide for Microsoft Advanced Group Policy Management 2.5
-author: dansimp
-ms.assetid: 005f0bb5-789f-42a9-bcaf-7e8c31a8df66
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Operations Guide for Microsoft Advanced Group Policy Management 2.5
-
-
-You can use Microsoft Advanced Group Policy Management (AGPM) to extend the capabilities of the Group Policy Management Console (GPMC), providing comprehensive change control and enhanced management for Group Policy objects (GPOs).
-
-With AGPM you can:
-
-- Perform offline editing of GPOs, so you can create and test them before deploying to a production environment.
-
-- Retain multiple versions of a GPO in a central archive, so you can roll back if a problem occurs.
-
-- Share the responsibility for editing, approving, and reviewing GPOs among multiple people using role-based delegation.
-
-- Eliminate the danger of multiple Group Policy administrators overwriting each other's work by using a check-in/check-out capability for GPOs.
-
-- Analyze changes to a GPO, comparing it to another GPO or another version of the same GPO using difference reporting.
-
-- Simplify the creation of new GPOs by using GPO templates, storing standard settings to use as starting points for new GPOs.
-
-AGPM adds a **Change Control** node under each domain displayed in the GPMC, as well as **History** and **Extensions** tabs for each GPO and Group Policy link displayed in the GPMC.
-
-- [Overview of Advanced Group Policy Management](overview-of-advanced-group-policy-management.md)
-
-- [Checklist: Create, Edit, and Deploy a GPO](checklist-create-edit-and-deploy-a-gpo.md)
-
-- [Performing AGPM Administrator Tasks](performing-agpm-administrator-tasks.md)
-
-- [Performing Editor Tasks](performing-editor-tasks.md)
-
-- [Performing Approver Tasks](performing-approver-tasks.md)
-
-- [Performing Reviewer Tasks](performing-reviewer-tasks.md)
-
-- [Troubleshooting Advanced Group Policy Management](troubleshooting-advanced-group-policy-management.md)
-
-- [User Interface: Advanced Group Policy Management](user-interface-advanced-group-policy-management.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/operations-guide-for-microsoft-advanced-group-policy-management-30-agpm30ops.md b/mdop/agpm/operations-guide-for-microsoft-advanced-group-policy-management-30-agpm30ops.md
deleted file mode 100644
index 1b9ebfc6e4..0000000000
--- a/mdop/agpm/operations-guide-for-microsoft-advanced-group-policy-management-30-agpm30ops.md
+++ /dev/null
@@ -1,65 +0,0 @@
----
-title: Operations Guide for Microsoft Advanced Group Policy Management 3.0
-description: Operations Guide for Microsoft Advanced Group Policy Management 3.0
-author: dansimp
-ms.assetid: aaefe6d1-a9e5-43eb-b4d8-85880798cb8b
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Operations Guide for Microsoft Advanced Group Policy Management 3.0
-
-
-You can use Microsoft Advanced Group Policy Management (AGPM) to extend the capabilities of the Group Policy Management Console (GPMC), providing comprehensive change control and enhanced management for Group Policy Objects (GPOs).
-
-With AGPM you can:
-
-- Perform offline editing of GPOs, so you can create and test them before deploying to a production environment.
-
-- Retain multiple versions of a GPO in a central archive, so you can roll back if a problem occurs.
-
-- Share the responsibility for editing, approving, and reviewing GPOs among multiple people using role-based delegation.
-
-- Eliminate the danger of multiple Group Policy administrators overwriting each other's work by using a check-in/check-out capability for GPOs.
-
-- Analyze changes to a GPO, comparing it to another GPO or another version of the same GPO using difference reporting.
-
-- Simplify the creation of new GPOs by using GPO templates, storing standard settings to use as starting points for new GPOs.
-
-AGPM adds a **Change Control** folder under each domain displayed in the GPMC, as well as a **History** tab for each GPO and Group Policy link displayed in the GPMC.
-
-- [Overview of Advanced Group Policy Management](overview-of-advanced-group-policy-management-agpm30ops.md)
-
-- [Best Practices for Version Control](best-practices-for-version-control.md)
-
-- [Checklist: Administer the AGPM Server and Archive](checklist-administer-the-agpm-server-and-archive.md)
-
-- [Checklist: Create, Edit, and Deploy a GPO](checklist-create-edit-and-deploy-a-gpo-agpm30ops.md)
-
-- [Performing AGPM Administrator Tasks](performing-agpm-administrator-tasks-agpm30ops.md)
-
-- [Performing Editor Tasks](performing-editor-tasks-agpm30ops.md)
-
-- [Performing Approver Tasks](performing-approver-tasks-agpm30ops.md)
-
-- [Performing Reviewer Tasks](performing-reviewer-tasks-agpm30ops.md)
-
-- [Troubleshooting Advanced Group Policy Management](troubleshooting-advanced-group-policy-management-agpm30ops.md)
-
-- [User Interface: Advanced Group Policy Management](user-interface-advanced-group-policy-management-agpm30ops.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/operations-guide-for-microsoft-advanced-group-policy-management-40.md b/mdop/agpm/operations-guide-for-microsoft-advanced-group-policy-management-40.md
deleted file mode 100644
index c4c260282d..0000000000
--- a/mdop/agpm/operations-guide-for-microsoft-advanced-group-policy-management-40.md
+++ /dev/null
@@ -1,73 +0,0 @@
----
-title: Operations Guide for Microsoft Advanced Group Policy Management 4.0
-description: Operations Guide for Microsoft Advanced Group Policy Management 4.0
-author: dansimp
-ms.assetid: 0bafeba3-20a9-4360-be5d-03f786df11ee
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Operations Guide for Microsoft Advanced Group Policy Management 4.0
-
-
-You can use Microsoft Advanced Group Policy Management (AGPM) to extend the capabilities of the Group Policy Management Console (GPMC). AGPM provides comprehensive change control and improved management of Group Policy Objects (GPOs).
-
-Using AGPM, you can do these tasks:
-
-- Perform offline editing of GPOs so that you can create and test them before you deploy them to a production environment.
-
-- Maintain multiple versions of a GPO in a central archive so that you can roll back if a problem occurs.
-
-- Share the responsibility for editing, approving, and reviewing GPOs among multiple people by using role-based delegation.
-
-- Eliminate the danger of multiple Group Policy administrators overwriting one another's work by using the check-in and check-out capability for GPOs.
-
-- Analyze changes to a GPO, comparing it to another GPO or another version of the same GPO by using difference reporting.
-
-- Simplify creating new GPOs by using GPO templates, storing common policy settings and preference settings to use as starting points for new GPOs.
-
-- Delegate access to the production environment.
-
-- Search for GPOs with specific attributes and filter the list of GPOs displayed.
-
-- Export a GPO to a file so that you can copy it from a domain in a test forest to a domain in a production forest.
-
-AGPM adds a **Change Control** folder under each domain displayed in the GPMC, in addition to a **History** tab for each GPO and Group Policy link displayed in the GPMC.
-
-- [Overview of Advanced Group Policy Management](overview-of-advanced-group-policy-management-agpm40.md)
-
-- [Best Practices for Version Control](best-practices-for-version-control-agpm40.md)
-
-- [Checklist: Administer the AGPM Server and Archive](checklist-administer-the-agpm-server-and-archive-agpm40.md)
-
-- [Checklist: Create, Edit, and Deploy a GPO](checklist-create-edit-and-deploy-a-gpo-agpm40.md)
-
-- [Search and Filter the List of GPOs](search-and-filter-the-list-of-gpos.md)
-
-- [Performing AGPM Administrator Tasks](performing-agpm-administrator-tasks-agpm40.md)
-
-- [Performing Editor Tasks](performing-editor-tasks-agpm40.md)
-
-- [Performing Approver Tasks](performing-approver-tasks-agpm40.md)
-
-- [Performing Reviewer Tasks](performing-reviewer-tasks-agpm40.md)
-
-- [Troubleshooting AGPM](troubleshooting-agpm-agpm40.md)
-
-- [User Interface: Advanced Group Policy Management](user-interface-advanced-group-policy-management-agpm40.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/other-enhancements-to-the-gpmc.md b/mdop/agpm/other-enhancements-to-the-gpmc.md
deleted file mode 100644
index b4bf662f24..0000000000
--- a/mdop/agpm/other-enhancements-to-the-gpmc.md
+++ /dev/null
@@ -1,43 +0,0 @@
----
-title: Other Enhancements to the GPMC
-description: Other Enhancements to the GPMC
-author: dansimp
-ms.assetid: ef344101-17e1-4e06-9dc8-2f20ca796774
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Other Enhancements to the GPMC
-
-
-Advanced Group Policy Management (AGPM) adds a **History** tab and an **Extensions** tab to extend the functionality of the **Group Policy Management Console** (GPMC).
-
-## History tab
-
-
-AGPM adds a **History** tab to all Group Policy objects (GPOs) and Group Policy links displayed in the GPMC. The features of the **History** tab in the details pane of a GPO are the same as those of the **History** window displayed through the **Change Control** tab. For information about these features, see [History Window](history-window.md).
-
-## Extensions tab
-
-
-In the Microsoft Windows Server® 2003 operating system, AGPM adds an **Extensions** tab to all GPOs and Group Policy links displayed in the GPMC. This tab lists all extensions that have settings in the GPO (or all registered extensions if **Show all registered extensions** is checked) and identifies them as part of the user or computer context.
-
-### Additional references
-
-- [User Interface: Advanced Group Policy Management](user-interface-advanced-group-policy-management.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/overview-of-advanced-group-policy-management-agpm30ops.md b/mdop/agpm/overview-of-advanced-group-policy-management-agpm30ops.md
deleted file mode 100644
index 19cb9b5a66..0000000000
--- a/mdop/agpm/overview-of-advanced-group-policy-management-agpm30ops.md
+++ /dev/null
@@ -1,66 +0,0 @@
----
-title: Overview of Advanced Group Policy Management
-description: Overview of Advanced Group Policy Management
-author: dansimp
-ms.assetid: 3a8d1e58-12b9-42bd-898f-6d57514dfbb9
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Overview of Advanced Group Policy Management
-
-
-You can use Advanced Group Policy Management (AGPM) to extend the capabilities of the Group Policy Management Console (GPMC) to provide comprehensive change control and improved management for Group Policy Objects (GPOs).
-
-## Group Policy object development with change control
-
-
-With AGPM, you can store a copy of each GPO in a central archive so that Group Policy administrators can view and change it offline without immediately affecting the deployed version of the GPO. Additionally, AGPM stores a copy of each version of each controlled GPO in the archive so that you can roll back to an earlier version if necessary.
-
-The terms "check in" and "check out" are used just as in a library (or in applications that provide change control, version control, or source control for programming development). To use a book that is in a library, you check it out from the library. No one else can use it while you have it checked out. When you are finished with the book, you check it back into the library, so others can use it.
-
-When you develop GPOs by using AGPM:
-
-1. Create a new controlled GPO or control a previously uncontrolled GPO.
-
-2. Check out the GPO, so that you and only you can change it.
-
-3. Edit the GPO.
-
-4. Check in the edited GPO, so that others can change it, or so that it can be deployed.
-
-5. Review the changes.
-
-6. Deploy the GPO to the production environment.
-
-## Role-based delegation
-
-
-AGPM provides comprehensive, easy-to-use role-based delegation for managing access to GPOs in the archive. Domain-level permissions enable AGPM Administrators to provide access to individual domains without providing access to other domains. GPO-based delegation enables AGPM Administrators to provide access to specific GPOs without providing domain-wide access.
-
-Within AGPM, there are specifically defined roles: AGPM Administrator (Full Control), Approver, Editor, and Reviewer. The AGPM Administrator role includes the permissions for all other roles. By default, only Approvers have the power to deploy GPOs to the production environment, protecting the environment from mistakes by less experienced Editors. Also by default, all roles include the Reviewer role and therefore the ability to view GPO settings in reports. However, AGPM provides an AGPM Administrator with the flexibility to customize GPO access to fit the needs of your organization.
-
-## Delegation in a multiple Group Policy administrator environment
-
-
-In an environment where multiple people change GPOs, an AGPM Administrator delegates permission to Editors, Approvers, and Reviewers, either as groups or as individuals. For a typical GPO development process for an Editor and an Approver, see [Checklist: Create, Edit, and Deploy a GPO](checklist-create-edit-and-deploy-a-gpo-agpm30ops.md).
-
-### Additional references
-
-- [Operations Guide for Microsoft Advanced Group Policy Management 3.0](operations-guide-for-microsoft-advanced-group-policy-management-30-agpm30ops.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/overview-of-advanced-group-policy-management-agpm40.md b/mdop/agpm/overview-of-advanced-group-policy-management-agpm40.md
deleted file mode 100644
index a9b6c13c20..0000000000
--- a/mdop/agpm/overview-of-advanced-group-policy-management-agpm40.md
+++ /dev/null
@@ -1,68 +0,0 @@
----
-title: Overview of Advanced Group Policy Management
-description: Overview of Advanced Group Policy Management
-author: dansimp
-ms.assetid: 2c12f3b4-8472-4c5b-b7f8-1c98a80d6b47
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Overview of Advanced Group Policy Management
-
-
-You can use Advanced Group Policy Management (AGPM) to extend the capabilities of the Group Policy Management Console (GPMC) to provide comprehensive change control and improved management for Group Policy Objects (GPOs).
-
-## Group Policy object development with change control
-
-
-With AGPM, you can store a copy of each GPO in a central archive so that Group Policy administrators can view and change it offline without immediately affecting the deployed version of the GPO. Additionally, AGPM stores a copy of each version of each controlled GPO in the archive so that you can roll back to an earlier version if necessary.
-
-The terms "check in" and "check out" are used just as in a library (or in applications that provide change control, version control, or source control for programming development). To use a book that is in a library, you check it out from the library. No one else can use it while you have it checked out. When you are finished with the book, you check it back into the library, so others can use it.
-
-To use these GPO control features, you will click a Change Control node in the Group Policy Management editor. The Change Control node appears only if you have installed the AGPM Client.
-
-When you develop GPOs by using AGPM:
-
-1. Create a new controlled GPO or control a previously uncontrolled GPO.
-
-2. Check out the GPO, so that you and only you can change it.
-
-3. Edit the GPO.
-
-4. Check in the edited GPO, so that others can change it, or so that it can be deployed.
-
-5. Review the changes.
-
-6. Deploy the GPO to the production environment.
-
-## Role-based delegation
-
-
-AGPM provides comprehensive, easy-to-use role-based delegation for managing access to GPOs in the archive. Domain-level permissions enable AGPM Administrators to provide access to individual domains without providing access to other domains. GPO-based delegation enables AGPM Administrators to provide access to specific GPOs without providing domain-wide access.
-
-Within AGPM, there are specifically defined roles: AGPM Administrator (Full Control), Approver, Editor, and Reviewer. The AGPM Administrator role includes the permissions for all other roles. By default, only Approvers have the power to deploy GPOs to the production environment of a domain, protecting the environment from mistakes by less experienced Editors. Also by default, all roles include the Reviewer role and therefore the ability to view GPO settings in reports. However, AGPM provides an AGPM Administrator with the flexibility to customize GPO access to fit the needs of your organization.
-
-## Delegation in a multiple Group Policy administrator environment
-
-
-In an environment where multiple people change GPOs, an AGPM Administrator delegates permission to Editors, Approvers, and Reviewers, either as groups or as individuals. For a typical GPO development process for an Editor and an Approver, see [Checklist: Create, Edit, and Deploy a GPO](checklist-create-edit-and-deploy-a-gpo-agpm40.md).
-
-### Additional references
-
-- [Advanced Group Policy Management 4.0](advanced-group-policy-management-40.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/overview-of-advanced-group-policy-management.md b/mdop/agpm/overview-of-advanced-group-policy-management.md
deleted file mode 100644
index ab987de9d0..0000000000
--- a/mdop/agpm/overview-of-advanced-group-policy-management.md
+++ /dev/null
@@ -1,78 +0,0 @@
----
-title: Overview of Advanced Group Policy Management
-description: Overview of Advanced Group Policy Management
-author: dansimp
-ms.assetid: 028de9dd-848b-42bc-a982-65ba5c433772
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Overview of Advanced Group Policy Management
-
-
-You can use Advanced Group Policy Management (AGPM) to extend the capabilities of the Group Policy Management Console (GPMC), providing comprehensive change control and enhanced management for Group Policy objects (GPOs).
-
-## Group Policy object development with change control
-
-
-With AGPM, you can store a copy of each GPO in a central archive, so Group Policy administrators can view and modify it offline without immediately impacting the deployed version of the GPO. Additionally, AGPM stores a copy of each version of each controlled GPO in the archive so that you can roll back to an earlier version if needed.
-
-The terms "check in" and "check out" are used in much the same way as in a library (or in applications that provide change control, version control, or source code control for programming development). To use a book that is in a library, you check it out from the library. No one else can use it while you have it checked out. When you are finished with the book, you check it back into the library, so others can use it.
-
-When developing GPOs using AGPM:
-
-1. Create a new controlled GPO or control a previously uncontrolled GPO.
-
-2. Check out the GPO, so you and only you can modify it.
-
-3. Edit the GPO.
-
-4. Check in the edited GPO, so others can modify it, or so it can be deployed.
-
-5. Review the changes.
-
-6. Deploy the GPO to the production environment.
-
-## Role-based delegation
-
-
-AGPM provides comprehensive, easy-to-use role-based delegation. Domain-level permissions allow AGPM Administrators to provide access to individual domains without providing access to other domains. GPO-based delegation enables AGPM Administrators to allow access only to specific GPOs.
-
-Within AGPM, there are specifically defined roles: AGPM Administrator (Full Control), Approver, Editor, and Reviewer. The AGPM Administrator role includes the permissions for all other roles. By default, only Approvers have the power to deploy GPOs to the production environment, protecting the environment from inadvertent mistakes by less experienced Editors. Also by default, all roles include the Reviewer role and therefore the ability to view GPO settings in reports. However, AGPM provides an AGPM Administrator with the flexibility to customize GPO access to fit the needs of your organization.
-
-## Delegation in a multiple Group Policy administrator environment
-
-
-In an environment where multiple people make changes to GPOs, an AGPM Administrator delegates permission to Editors, Approvers, and Reviewers, either as groups or as individuals. For a typical GPO development process for an Editor and an Approver, see [Checklist: Create, Edit, and Deploy a GPO](checklist-create-edit-and-deploy-a-gpo.md).
-
-### Additional references
-
-- [Checklist: Create, Edit, and Deploy a GPO](checklist-create-edit-and-deploy-a-gpo.md)
-
-- [Performing AGPM Administrator Tasks](performing-agpm-administrator-tasks.md)
-
-- [Performing Editor Tasks](performing-editor-tasks.md)
-
-- [Performing Approver Tasks](performing-approver-tasks.md)
-
-- [Performing Reviewer Tasks](performing-reviewer-tasks.md)
-
-- [Troubleshooting Advanced Group Policy Management](troubleshooting-advanced-group-policy-management.md)
-
-- [User Interface: Advanced Group Policy Management](user-interface-advanced-group-policy-management.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/pending-gpo-commands-agpm30ops.md b/mdop/agpm/pending-gpo-commands-agpm30ops.md
deleted file mode 100644
index 335ce54580..0000000000
--- a/mdop/agpm/pending-gpo-commands-agpm30ops.md
+++ /dev/null
@@ -1,137 +0,0 @@
----
-title: Pending GPO Commands
-description: Pending GPO Commands
-author: dansimp
-ms.assetid: 3868dda0-8a41-4bba-9b0c-9f656f9a3cd5
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Pending GPO Commands
-
-
-The **Pending** tab:
-
-- Displays a list of Group Policy Objects (GPOs) with pending requests for GPO management actions (such as creation, control, deployment, or deletion).
-
-- Provides a shortcut menu with commands for responding to pending requests and for displaying the history and reports for GPOs.
-
-- Displays a list of the groups and users who have permission to access a selected GPO.
-
-Right-clicking the **Group Policy Objects** list on this tab displays a shortcut menu, including whichever of the following options are applicable.
-
-## Control and history
-
-
-
-
-
-
-
-
-
-
Command
-
Effect
-
-
-
-
-
History
-
Open a window listing all versions of the selected GPO saved within the archive. From the history, you can obtain a report of the settings within a GPO, compare two versions of a GPO, compare a GPO to a template, or roll back to a previous version of a GPO.
-
-
-
Withdraw
-
Withdraw your pending request to create, control, or delete the selected GPO before the request has been approved.
-
-
-
Approve
-
Complete a pending request from an Editor to create, control, or delete the selected GPO.
-
-
-
Reject
-
Deny a pending request from an Editor to create, control, or delete the selected GPO.
-
-
-
-
-
-
-## Reports
-
-
-
-
-
-
-
-
-
-
Command
-
Effect
-
-
-
-
-
Settings
-
Generate an HTML-based or XML-based report displaying the settings within the selected GPO or display links to the selected GPOs from organizational units as of when the GPOs are most recently controlled, imported, or checked in.
-
-
-
Differences
-
Generate an HTML-based or XML-based report comparing the settings within two selected GPOs or within the selected GPO and a template.
-
-
-
-
-
-
-## Miscellaneous
-
-
-
-
-
-
-
-
-
-
Command
-
Effect
-
-
-
-
-
Refresh
-
Update the display of the Group Policy Management Console (GPMC) to incorporate any changes. Some changes are not visible until the display is refreshed.
-
-
-
Help
-
Display help for AGPM.
-
-
-
-
-
-
-### Additional references
-
-- [Contents Tab](contents-tab-agpm30ops.md)
-
-- [Performing Approver Tasks](performing-approver-tasks-agpm30ops.md)
-
-- [Performing Reviewer Tasks](performing-reviewer-tasks-agpm30ops.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/pending-gpo-commands-agpm40.md b/mdop/agpm/pending-gpo-commands-agpm40.md
deleted file mode 100644
index 828e0f34aa..0000000000
--- a/mdop/agpm/pending-gpo-commands-agpm40.md
+++ /dev/null
@@ -1,137 +0,0 @@
----
-title: Pending GPO Commands
-description: Pending GPO Commands
-author: dansimp
-ms.assetid: b62f49e1-43ab-4c93-8102-96cd97a4adad
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Pending GPO Commands
-
-
-The **Pending** tab:
-
-- Displays a list of Group Policy Objects (GPOs) with pending requests for GPO management actions (such as creation, control, deployment, or deletion).
-
-- Provides a shortcut menu with commands for responding to pending requests and for displaying the history and reports for GPOs.
-
-- Displays a list of the groups and users who have permission to access a selected GPO.
-
-Right-clicking the **Group Policy Objects** list on this tab displays a shortcut menu, including whichever of the following options are applicable.
-
-## Control and history
-
-
-
-
-
-
-
-
-
-
Command
-
Effect
-
-
-
-
-
History
-
Open a window listing all versions of the selected GPO saved within the archive. From the history, you can obtain a report of the settings within a GPO, compare two versions of a GPO, compare a GPO to a template, or roll back to an earlier version of a GPO.
-
-
-
Withdraw
-
Withdraw your pending request to create, control, or delete the selected GPO before the request has been approved.
-
-
-
Approve
-
Complete a pending request from an Editor to create, control, or delete the selected GPO.
-
-
-
Reject
-
Deny a pending request from an Editor to create, control, or delete the selected GPO.
-
-
-
-
-
-
-## Reports
-
-
-
-
-
-
-
-
-
-
Command
-
Effect
-
-
-
-
-
Settings
-
Generate an HTML-based or XML-based report displaying the settings within the selected GPO or display links to the selected GPOs from organizational units as of when the GPOs are most recently controlled, imported, or checked in.
-
-
-
Differences
-
Generate an HTML-based or XML-based report comparing the settings within two selected GPOs or within the selected GPO and a template.
-
-
-
-
-
-
-## Miscellaneous
-
-
-
-
-
-
-
-
-
-
Command
-
Effect
-
-
-
-
-
Refresh
-
Update the display of the Group Policy Management Console (GPMC) to incorporate any changes. Some changes are not visible until the display is refreshed.
-
-
-
Help
-
Display help for AGPM.
-
-
-
-
-
-
-### Additional references
-
-- [Contents Tab](contents-tab-agpm40.md)
-
-- [Performing Approver Tasks](performing-approver-tasks-agpm40.md)
-
-- [Performing Reviewer Tasks](performing-reviewer-tasks-agpm40.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/pending-tab.md b/mdop/agpm/pending-tab.md
deleted file mode 100644
index b3797e17cc..0000000000
--- a/mdop/agpm/pending-tab.md
+++ /dev/null
@@ -1,137 +0,0 @@
----
-title: Pending Tab
-description: Pending Tab
-author: dansimp
-ms.assetid: 54a9a977-c0bc-4553-922b-b2e10e162df9
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Pending Tab
-
-
-The **Pending** tab:
-
-- Displays a list of Group Policy objects (GPOs) with pending requests for GPO management actions (such as creation, control, deployment, or deletion).
-
-- Provides a shortcut menu with commands for responding to pending requests and for displaying the history and reports for GPOs.
-
-- Displays a list of the groups and users who have permission to access a selected GPO.
-
-Right-clicking the **Group Policy Objects** list on this tab displays a shortcut menu, including whichever of the following options are applicable.
-
-## Control and history
-
-
-
-
-
-
-
-
-
-
Command
-
Effect
-
-
-
-
-
History
-
Open a window listing all versions of the selected GPO saved within the archive. From the history, you can obtain a report of the settings within a GPO, compare two versions of a GPO, compare a GPO to a template, or roll back to a previous version of a GPO.
-
-
-
Withdraw
-
Withdraw your pending request to create, control, or delete the selected GPO before the request has been approved.
-
-
-
Approve
-
Complete a pending request from an Editor to create, control, or delete the selected GPO.
-
-
-
Reject
-
Deny a pending request from an Editor to create, control, or delete the selected GPO.
-
-
-
-
-
-
-## Reports
-
-
-
-
-
-
-
-
-
-
Command
-
Effect
-
-
-
-
-
Settings
-
Generate an HTML-based or XML-based report displaying the settings within the selected GPO or display links to the selected GPOs from organizational units as of when the GPOs are most recently controlled, imported, or checked in.
-
-
-
Differences
-
Generate an HTML-based or XML-based report comparing the settings within two selected GPOs or within the selected GPO and a template.
-
-
-
-
-
-
-## Miscellaneous
-
-
-
-
-
-
-
-
-
-
Command
-
Effect
-
-
-
-
-
Refresh
-
Update the display of the Group Policy Management Console to incorporate any changes. Some changes are not visible until the display is refreshed.
-
-
-
Help
-
Display help for AGPM.
-
-
-
-
-
-
-### Additional references
-
-- [Contents Tab](contents-tab.md)
-
-- [Performing Approver Tasks](performing-approver-tasks.md)
-
-- [Performing Reviewer Tasks](performing-reviewer-tasks.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/performing-agpm-administrator-tasks-agpm30ops.md b/mdop/agpm/performing-agpm-administrator-tasks-agpm30ops.md
deleted file mode 100644
index d3dd8dcca6..0000000000
--- a/mdop/agpm/performing-agpm-administrator-tasks-agpm30ops.md
+++ /dev/null
@@ -1,71 +0,0 @@
----
-title: Performing AGPM Administrator Tasks
-description: Performing AGPM Administrator Tasks
-author: dansimp
-ms.assetid: 9678b0f4-70a5-411e-a896-afa4dc9ea6c4
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Performing AGPM Administrator Tasks
-
-
-In Advanced Group Policy Management (AGPM), an AGPM Administrator (Full Control) configures domain-wide options and delegates permissions to Approvers, Editors, Reviewers, and other AGPM Administrators. By default, an AGPM Administrator is an individual with Full Control—all AGPM permissions—and who therefore can perform tasks associated with any role.
-
-In an environment in which multiple people develop Group Policy Objects (GPOs), you can choose whether all AGPM users perform the same tasks and have the same level of access or whether AGPM Administrators delegate permissions to Editors who make changes to GPOs and to Approvers who deploy GPOs to the production environment. AGPM Administrators can configure permissions to meet the needs of your organization.
-
-- [Configuring Advanced Group Policy Management](configuring-advanced-group-policy-management.md): Configure the AGPM Server Connection and e-mail notification, delegate access to GPOs in the production environment, and configure logging and tracing for troubleshooting.
-
-- [Managing the Archive](managing-the-archive.md): Delegate access to GPOs in the archive and limit the number of versions of each GPO stored.
-
-- [Managing the AGPM Service](managing-the-agpm-service-agpm30ops.md): Stop and start the AGPM Service or change the archive path, the AGPM Service Account, or the port on which the AGPM Service listens.
-
-- [Move the AGPM Server and the Archive](move-the-agpm-server-and-the-archive.md): Move the AGPM Service, the archive, or both to a different server.
-
-Also, because the AGPM Administrator role includes the permissions for all other roles, an AGPM Administrator can perform the tasks normally associated with any other role.
-
-- [Performing Approver Tasks](performing-approver-tasks-agpm30ops.md), such as creating, deploying, or deleting GPOs
-
-- [Performing Editor Tasks](performing-editor-tasks-agpm30ops.md), such as editing, renaming, labeling, or importing GPOs, creating templates, or setting a default template
-
-- [Performing Reviewer Tasks](performing-reviewer-tasks-agpm30ops.md), such as reviewing settings and comparing GPOs
-
-### Additional considerations
-
-By default, the AGPM Administrator role has Full Control—all AGPM permissions:
-
-- List Contents
-
-- Read Settings
-
-- Edit Settings
-
-- Create GPO
-
-- Deploy GPO
-
-- Delete GPO
-
-- Modify Options
-
-- Modify Security
-
-- Create Template
-
-The **Modify Options** and **Modify Security** permissions are unique to the role of AGPM Administrator.
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/performing-agpm-administrator-tasks-agpm40.md b/mdop/agpm/performing-agpm-administrator-tasks-agpm40.md
deleted file mode 100644
index 73153462b6..0000000000
--- a/mdop/agpm/performing-agpm-administrator-tasks-agpm40.md
+++ /dev/null
@@ -1,78 +0,0 @@
----
-title: Performing AGPM Administrator Tasks
-description: Performing AGPM Administrator Tasks
-author: dansimp
-ms.assetid: bc746f39-bdc9-4e2a-bc48-c3c7905de098
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Performing AGPM Administrator Tasks
-
-
-Advanced Group Policy Management (AGPM) lets an AGPM Administrator (Full Control) configure domain-wide options and delegate permissions to Approvers, Editors, Reviewers, and AGPM Administrators. By default, an AGPM Administrator is someone who has Full Control— all AGPM permissions—and who therefore can perform tasks associated with any role.
-
-In an environment in which multiple people develop Group Policy Objects (GPOs), you can choose to let all Group Policy administrators perform the same tasks and have the same level of access. Or, you can choose to let AGPM Administrators delegate permissions to Editors who can change GPOs and to Approvers who deploy GPOs to the production environment. AGPM Administrators can configure permissions to meet the needs of your organization.
-
-- [Configuring Advanced Group Policy Management](configuring-advanced-group-policy-management-agpm40.md): Configure the AGPM Server Connection and e-mail notification, delegate access to GPOs in the production environment, and configure logging and tracing for troubleshooting.
-
-- [Managing the Archive](managing-the-archive-agpm40.md): Delegate access to GPOs in the archive, limit the number of versions of each GPO stored, import a GPO from another domain, and back up and restore the archive.
-
-- [Managing the AGPM Service](managing-the-agpm-service-agpm40.md): Stop and start the AGPM Service or change the archive path, the AGPM Service Account, or the port on which the AGPM Service listens.
-
-- [Move the AGPM Server and the Archive](move-the-agpm-server-and-the-archive-agpm40.md): Move the AGPM Service, the archive, or both to a different server.
-
-**Note**
-Because the AGPM Administrator role includes the permissions for all other roles, an AGPM Administrator can perform the tasks usually associated with any other role.
-
-[Performing Approver Tasks](performing-approver-tasks-agpm40.md), such as creating, deploying, or deleting GPOs
-
-[Performing Editor Tasks](performing-editor-tasks-agpm40.md), such as editing, renaming, labeling, or importing GPOs, creating templates, or setting a default template
-
-[Performing Reviewer Tasks](performing-reviewer-tasks-agpm40.md), such as reviewing settings and comparing GPOs
-
-
-
-### Additional considerations
-
-By default, the AGPM Administrator role has Full Control—all AGPM permissions:
-
-- List Contents
-
-- Read Settings
-
-- Edit Settings
-
-- Create GPO
-
-- Deploy GPO
-
-- Delete GPO
-
-- Export GPO
-
-- Import GPO
-
-- Create Template
-
-- Modify Options
-
-- Modify Security
-
-The **Modify Options** and **Modify Security** permissions are unique to the role of AGPM Administrator.
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/performing-agpm-administrator-tasks.md b/mdop/agpm/performing-agpm-administrator-tasks.md
deleted file mode 100644
index 621841c925..0000000000
--- a/mdop/agpm/performing-agpm-administrator-tasks.md
+++ /dev/null
@@ -1,83 +0,0 @@
----
-title: Performing AGPM Administrator Tasks
-description: Performing AGPM Administrator Tasks
-author: dansimp
-ms.assetid: 32e694a7-be64-4943-bce2-2a3a15e5341f
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Performing AGPM Administrator Tasks
-
-
-An AGPM Administrator (Full Control) configures domain-wide options and delegates permissions to Approvers, Editors, Reviewers, and other AGPM Administrators. By default, an AGPM Administrator is an individual with Full Control (all Advanced Group Policy Management \[AGPM\] permissions) and therefore can also perform tasks associated with any role.
-
-In an environment in which multiple people develop Group Policy objects (GPOs), you can choose whether all Advanced Group Policy Management (AGPM) users perform the same tasks and have the same level of access or whether AGPM Administrators delegate permissions to Editors who make changes to GPOs and to Approvers who deploy GPOs to the production environment. AGPM Administrators can configure permissions to meet the needs of your organization.
-
-- [Configure the AGPM Server Connection](configure-the-agpm-server-connection.md)
-
-- [Configure E-Mail Notification](configure-e-mail-notification.md)
-
-- [Delegate Domain-Level Access](delegate-domain-level-access.md)
-
-- [Delegate Access to an Individual GPO](delegate-access-to-an-individual-gpo.md)
-
-- [Configure Logging and Tracing](configure-logging-and-tracing.md)
-
-- [Managing the AGPM Service](managing-the-agpm-service.md)
-
- - [Start and Stop the AGPM Service](start-and-stop-the-agpm-service.md)
-
- - [Modify the Archive Path](modify-the-archive-path.md)
-
- - [Modify the AGPM Service Account](modify-the-agpm-service-account.md)
-
- - [Modify the Port on Which the AGPM Service Listens](modify-the-port-on-which-the-agpm-service-listens.md)
-
-Also, because the AGPM Administrator role includes the permissions for all other roles, an AGPM Administrator can perform the tasks normally associated with any other role.
-
-- [Performing Approver Tasks](performing-approver-tasks.md), such as creating, deploying, or deleting GPOs
-
-- [Performing Editor Tasks](performing-editor-tasks.md), such as editing, renaming, labeling, or importing GPOs, creating templates, or setting a default template
-
-- [Performing Reviewer Tasks](performing-reviewer-tasks.md), such as reviewing settings and comparing GPOs
-
-### Additional considerations
-
-By default, the AGPM Administrator role has Full Control—all AGPM permissions:
-
-- List Contents
-
-- Read Settings
-
-- Edit Settings
-
-- Create GPO
-
-- Deploy GPO
-
-- Delete GPO
-
-- Modify Options
-
-- Modify Security
-
-- Create Template
-
-The **Modify Options** and **Modify Security** permissions are unique to the role of AGPM Administrator.
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/performing-approver-tasks-agpm30ops.md b/mdop/agpm/performing-approver-tasks-agpm30ops.md
deleted file mode 100644
index 354cf61ee9..0000000000
--- a/mdop/agpm/performing-approver-tasks-agpm30ops.md
+++ /dev/null
@@ -1,67 +0,0 @@
----
-title: Performing Approver Tasks
-description: Performing Approver Tasks
-author: dansimp
-ms.assetid: 9f711824-191b-4b4b-a1c6-a3b2116006a4
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Performing Approver Tasks
-
-
-An Approver is a person authorized by an AGPM Administrator (Full Control) to create, deploy, and delete Group Policy Objects (GPOs) and to approve or reject requests (typically from Editors) to create, deploy, or delete GPOs.
-
-**Important**
-Make sure that you are connecting to the central archive for GPOs. For more information, see [Configure an AGPM Server Connection](configure-an-agpm-server-connection-reviewer-agpm30ops.md).
-
-
-
-- [Approve or Reject a Pending Action](approve-or-reject-a-pending-action-agpm30ops.md)
-
-- [Creating, Controlling, or Importing a GPO](creating-controlling-or-importing-a-gpo-editor-agpm30ops.md)
-
-- [Check In a GPO](check-in-a-gpo-agpm30ops.md)
-
-- [Deploy a GPO](deploy-a-gpo-agpm30ops.md)
-
-- [Roll Back to a Previous Version of a GPO](roll-back-to-a-previous-version-of-a-gpo-agpm30ops.md)
-
-- [Deleting, Restoring, or Destroying a GPO](deleting-restoring-or-destroying-a-gpo-agpm30ops.md)
-
-**Note**
-Before approving a GPO, an Approver should review the policy settings that it contains. The Approver role includes the permissions for the Reviewer role, so that an Approver can review policy settings and compare GPOs. See [Performing Reviewer Tasks](performing-reviewer-tasks-agpm30ops.md) for more information.
-
-
-
-### Additional considerations
-
-By default, the following permissions are provided for the Approver role:
-
-- List Contents
-
-- Read Settings
-
-- Create GPO
-
-- Deploy GPO
-
-- Delete GPO
-
-Also, an Approver has full control over GPOs that he created or controlled.
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/performing-approver-tasks-agpm40.md b/mdop/agpm/performing-approver-tasks-agpm40.md
deleted file mode 100644
index 85377d6b65..0000000000
--- a/mdop/agpm/performing-approver-tasks-agpm40.md
+++ /dev/null
@@ -1,67 +0,0 @@
----
-title: Performing Approver Tasks
-description: Performing Approver Tasks
-author: dansimp
-ms.assetid: e0a4b7fe-ce69-4755-9104-c7f523ea6b62
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Performing Approver Tasks
-
-
-An Approver is a person authorized by an AGPM Administrator (Full Control) to create, deploy, and delete Group Policy Objects (GPOs) and to approve or reject requests (typically from Editors) to create, deploy, or delete GPOs.
-
-**Important**
-Make sure that you are connecting to the central archive for GPOs. For more information, see [Configure an AGPM Server Connection](configure-an-agpm-server-connection-agpm40.md).
-
-
-
-- [Approve or Reject a Pending Action](approve-or-reject-a-pending-action-agpm40.md)
-
-- [Creating or Controlling a GPO](creating-or-controlling-a-gpo-agpm40-app.md)
-
-- [Check In a GPO](check-in-a-gpo-agpm40.md)
-
-- [Deploy a GPO](deploy-a-gpo-agpm40.md)
-
-- [Roll Back to an Earlier Version of a GPO](roll-back-to-an-earlier-version-of-a-gpo-agpm40.md)
-
-- [Deleting, Restoring, or Destroying a GPO](deleting-restoring-or-destroying-a-gpo-agpm40.md)
-
-**Note**
-Before approving a GPO, an Approver should review the policy settings that it contains. The Approver role includes the permissions for the Reviewer role, so that an Approver can review policy settings and compare GPOs. See [Performing Reviewer Tasks](performing-reviewer-tasks-agpm40.md) for more information.
-
-
-
-### Additional considerations
-
-By default, the following permissions are provided for the Approver role:
-
-- List Contents
-
-- Read Settings
-
-- Create GPO
-
-- Deploy GPO
-
-- Delete GPO
-
-Also, an Approver has full control over GPOs that he created or controlled.
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/performing-approver-tasks.md b/mdop/agpm/performing-approver-tasks.md
deleted file mode 100644
index 643f462b96..0000000000
--- a/mdop/agpm/performing-approver-tasks.md
+++ /dev/null
@@ -1,67 +0,0 @@
----
-title: Performing Approver Tasks
-description: Performing Approver Tasks
-author: dansimp
-ms.assetid: 6f6310b3-19c1-47c9-8615-964ddd10ce14
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Performing Approver Tasks
-
-
-An Approver is a person authorized by an AGPM Administrator (Full Control) to create, deploy, and delete Group Policy objects (GPOs) and to approve or reject requests (typically from Editors) to create, deploy, or delete GPOs.
-
-**Important**
-Ensure that you are connecting to the central archive for GPOs. For more information, see [Configure the AGPM Server Connection](configure-the-agpm-server-connection-reviewer.md).
-
-
-
-- [Approve or Reject a Pending Action](approve-or-reject-a-pending-action.md)
-
-- [Creating, Controlling, or Importing a GPO](creating-controlling-or-importing-a-gpo-approver.md)
-
-- [Check In a GPO](check-in-a-gpo-approver.md)
-
-- [Deploy a GPO](deploy-a-gpo.md)
-
-- [Roll Back to a Previous Version of a GPO](roll-back-to-a-previous-version-of-a-gpo.md)
-
-- [Deleting, Restoring, or Destroying a GPO](deleting-restoring-or-destroying-a-gpo.md)
-
-**Note**
-Because the Approver role includes the permissions for the Reviewer role, an Approver can also review settings and compare GPOs. See [Performing Reviewer Tasks](performing-reviewer-tasks.md) for more information.
-
-
-
-### Additional considerations
-
-By default, the following permissions are provided for the Approver role:
-
-- List Contents
-
-- Read Settings
-
-- Create GPO
-
-- Deploy GPO
-
-- Delete GPO
-
-Also, an Approver has full control over GPOs that he created or controlled.
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/performing-editor-tasks-agpm30ops.md b/mdop/agpm/performing-editor-tasks-agpm30ops.md
deleted file mode 100644
index 56a79bf8fa..0000000000
--- a/mdop/agpm/performing-editor-tasks-agpm30ops.md
+++ /dev/null
@@ -1,59 +0,0 @@
----
-title: Performing Editor Tasks
-description: Performing Editor Tasks
-author: dansimp
-ms.assetid: d4ac3277-2557-41cf-ac90-5adb6c30687c
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Performing Editor Tasks
-
-
-An Editor is a person authorized by an AGPM Administrator (Full Control) to make changes to Group Policy Objects (GPOs) and create GPO templates. Additionally, an Editor can initiate the process of creating, deleting, or restoring a GPO, but by default must request approval from an Approver.
-
-**Important**
-Ensure that you are connecting to the central archive for GPOs. For more information, see [Configure an AGPM Server Connection](configure-an-agpm-server-connection-reviewer-agpm30ops.md).
-
-
-
-- [Creating, Controlling, or Importing a GPO](creating-controlling-or-importing-a-gpo-agpm30ops.md)
-
-- [Editing a GPO](editing-a-gpo-agpm30ops.md)
-
-- [Creating a Template and Setting a Default Template](creating-a-template-and-setting-a-default-template-agpm30ops.md)
-
-- [Deleting or Restoring a GPO](deleting-or-restoring-a-gpo-agpm30ops.md)
-
-**Note**
-Because the Editor role includes the permissions for the Reviewer role, an Editor can also review settings and compare GPOs. See [Performing Reviewer Tasks](performing-reviewer-tasks-agpm30ops.md) for more information.
-
-
-
-### Additional considerations
-
-By default, the following permissions are provided for the Editor role:
-
-- List Contents
-
-- Read Settings
-
-- Edit Settings
-
-- Create Template
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/performing-editor-tasks-agpm40.md b/mdop/agpm/performing-editor-tasks-agpm40.md
deleted file mode 100644
index cdac449d72..0000000000
--- a/mdop/agpm/performing-editor-tasks-agpm40.md
+++ /dev/null
@@ -1,67 +0,0 @@
----
-title: Performing Editor Tasks
-description: Performing Editor Tasks
-author: dansimp
-ms.assetid: 81976a01-2a95-4256-b703-9fb3c884ef34
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Performing Editor Tasks
-
-
-In Advanced Group Policy Management (AGPM), an Editor is a person authorized by an AGPM Administrator (Full Control) to change Group Policy Objects (GPOs) and create GPO templates. Additionally, an Editor can request that a GPO be created, deleted, or restored. An Approver must approve the request for it to be implemented. An Editor can export a GPO to a file so that it can be copied to a domain in another forest, and import a GPO that was copied from another domain.
-
-**Important**
-Make sure that you are connecting to the central archive for GPOs. For more information, see [Configure an AGPM Server Connection](configure-an-agpm-server-connection-agpm40.md).
-
-
-
-- [Creating or Controlling a GPO](creating-or-controlling-a-gpo-agpm40-ed.md)
-
-- [Editing a GPO](editing-a-gpo-agpm40.md)
-
-- [Using a Test Environment](using-a-test-environment.md)
-
-- [Request Deployment of a GPO](request-deployment-of-a-gpo-agpm40.md)
-
-- [Creating a Template and Setting a Default Template](creating-a-template-and-setting-a-default-template-agpm40.md)
-
-- [Deleting or Restoring a GPO](deleting-or-restoring-a-gpo-agpm40.md)
-
-**Note**
-Because the Editor role includes the permissions for the Reviewer role, an Editor can also review settings and compare GPOs. See [Performing Reviewer Tasks](performing-reviewer-tasks-agpm40.md) for more information.
-
-
-
-### Additional considerations
-
-By default, the following permissions are provided for the Editor role:
-
-- List Contents
-
-- Read Settings
-
-- Edit Settings
-
-- Export GPO
-
-- Import GPO
-
-- Create Template
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/performing-editor-tasks.md b/mdop/agpm/performing-editor-tasks.md
deleted file mode 100644
index e2b158f4f9..0000000000
--- a/mdop/agpm/performing-editor-tasks.md
+++ /dev/null
@@ -1,59 +0,0 @@
----
-title: Performing Editor Tasks
-description: Performing Editor Tasks
-author: dansimp
-ms.assetid: b1e62615-2e02-460e-81d1-4a3fbe59f62d
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Performing Editor Tasks
-
-
-An Editor is a person authorized by an AGPM Administrator (Full Control) to make changes to Group Policy objects (GPOs) and create GPO templates. Additionally, an Editor can initiate the process of creating or deleting a GPO, but by default must request approval from an Approver.
-
-**Important**
-Ensure that you are connecting to the central archive for GPOs. For more information, see [Configure the AGPM Server Connection](configure-the-agpm-server-connection-reviewer.md).
-
-
-
-- [Creating, Controlling, or Importing a GPO](creating-controlling-or-importing-a-gpo-editor.md)
-
-- [Editing a GPO](editing-a-gpo.md)
-
-- [Creating a Template and Setting a Default Template](creating-a-template-and-setting-a-default-template.md)
-
-- [Delete a GPO](delete-a-gpo-editor.md)
-
-**Note**
-Because the Editor role includes the permissions for the Reviewer role, an Editor can also review settings and compare GPOs. See [Performing Reviewer Tasks](performing-reviewer-tasks.md) for more information.
-
-
-
-### Additional considerations
-
-By default, the following permissions are provided for the Editor role:
-
-- List Contents
-
-- Read Settings
-
-- Edit Settings
-
-- Create Template
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/performing-reviewer-tasks-agpm30ops.md b/mdop/agpm/performing-reviewer-tasks-agpm30ops.md
deleted file mode 100644
index dc9f09707d..0000000000
--- a/mdop/agpm/performing-reviewer-tasks-agpm30ops.md
+++ /dev/null
@@ -1,45 +0,0 @@
----
-title: Performing Reviewer Tasks
-description: Performing Reviewer Tasks
-author: dansimp
-ms.assetid: 1faf396d-be0d-49ac-b063-0722fda2e43d
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Performing Reviewer Tasks
-
-
-A Reviewer is a person authorized by an AGPM Administrator (Full Control) to review or audit Group Policy Objects (GPOs). An individual with only the Reviewer role cannot modify GPOs; however, all other roles include the Reviewer role.
-
-- [Configure an AGPM Server Connection](configure-an-agpm-server-connection-reviewer-agpm30ops.md)
-
-- [Review GPO Settings](review-gpo-settings-agpm30ops.md)
-
-- [Review GPO Links](review-gpo-links-agpm30ops.md)
-
-- [Identify Differences Between GPOs, GPO Versions, or Templates](identify-differences-between-gpos-gpo-versions-or-templates-agpm30ops.md)
-
-### Additional considerations
-
-By default, the following permissions are provided for the Reviewer role:
-
-- List Contents
-
-- Read Settings
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/performing-reviewer-tasks-agpm40.md b/mdop/agpm/performing-reviewer-tasks-agpm40.md
deleted file mode 100644
index 03929f7e0b..0000000000
--- a/mdop/agpm/performing-reviewer-tasks-agpm40.md
+++ /dev/null
@@ -1,45 +0,0 @@
----
-title: Performing Reviewer Tasks
-description: Performing Reviewer Tasks
-author: dansimp
-ms.assetid: b5f0805c-da55-45a5-a94c-2473af92b54a
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Performing Reviewer Tasks
-
-
-A Reviewer is a person authorized by an AGPM Administrator (Full Control) to review or audit Group Policy Objects (GPOs). An individual with only the Reviewer role cannot modify GPOs; however, all other roles include the Reviewer role.
-
-- [Configure an AGPM Server Connection](configure-an-agpm-server-connection-agpm40.md)
-
-- [Review GPO Settings](review-gpo-settings-agpm40.md)
-
-- [Review GPO Links](review-gpo-links-agpm40.md)
-
-- [Identify Differences Between GPOs, GPO Versions, or Templates](identify-differences-between-gpos-gpo-versions-or-templates-agpm40.md)
-
-### Additional considerations
-
-By default, the following permissions are provided for the Reviewer role:
-
-- List Contents
-
-- Read Settings
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/performing-reviewer-tasks.md b/mdop/agpm/performing-reviewer-tasks.md
deleted file mode 100644
index efab9279e1..0000000000
--- a/mdop/agpm/performing-reviewer-tasks.md
+++ /dev/null
@@ -1,45 +0,0 @@
----
-title: Performing Reviewer Tasks
-description: Performing Reviewer Tasks
-author: dansimp
-ms.assetid: 4bdd43fa-5c73-4900-8947-b45906f47f60
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Performing Reviewer Tasks
-
-
-A Reviewer is a person authorized by an AGPM Administrator (Full Control) to review or audit Group Policy objects (GPOs). An individual with only the Reviewer role cannot modify GPOs; however, all other roles include the Reviewer role.
-
-- [Configure the AGPM Server Connection](configure-the-agpm-server-connection-reviewer.md)
-
-- [Review GPO Settings](review-gpo-settings.md)
-
-- [Review GPO Links](review-gpo-links.md)
-
-- [Identify Differences Between GPOs, GPO Versions, or Templates](identify-differences-between-gpos-gpo-versions-or-templates.md)
-
-### Additional considerations
-
-By default, the following permissions are provided for the Reviewer role:
-
-- List Contents
-
-- Read Settings
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/production-delegation-tab-agpm30ops.md b/mdop/agpm/production-delegation-tab-agpm30ops.md
deleted file mode 100644
index a66636f4d2..0000000000
--- a/mdop/agpm/production-delegation-tab-agpm30ops.md
+++ /dev/null
@@ -1,66 +0,0 @@
----
-title: Production Delegation Tab
-description: Production Delegation Tab
-author: dansimp
-ms.assetid: 9851637d-d5c1-4d29-8582-e8779500a14e
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Production Delegation Tab
-
-
-The **Production Delegation** tab on the **Change Control** pane provides a list of users and groups who have domain-level access to controlled Group Policy Objects (GPOs) in the production environment and indicates the allowed permissions of each user or group.
-
-This tab allows an AGPM Administrator (Full Control) to modify the default delegation of access to GPOs in the production environment, adding or removing users and groups, and modifying the allowed permissions for each user and group.
-
-
-
-
-
-
-
-
-
Button
-
Effect
-
-
-
-
-
Add
-
Add a new entry to the security descriptor.
-
-
-
Remove
-
Remove the selected users or groups from the Access Control List.
-
-
-
Properties
-
Display the properties for the selected user or group. The properties page is the same one displayed for an object in Active Directory User and Computers.
-
-
-
-
-
-
-### Additional references
-
-- [User Interface: Advanced Group Policy Management](user-interface-advanced-group-policy-management-agpm30ops.md)
-
-- [Performing AGPM Administrator Tasks](performing-agpm-administrator-tasks-agpm30ops.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/production-delegation-tab-agpm40.md b/mdop/agpm/production-delegation-tab-agpm40.md
deleted file mode 100644
index 12e0ac126a..0000000000
--- a/mdop/agpm/production-delegation-tab-agpm40.md
+++ /dev/null
@@ -1,66 +0,0 @@
----
-title: Production Delegation Tab
-description: Production Delegation Tab
-author: dansimp
-ms.assetid: 046bb9bc-769a-4306-bc49-c159a9533552
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Production Delegation Tab
-
-
-The **Production Delegation** tab on the **Change Control** pane provides a list of users and groups who have domain-level access to controlled Group Policy Objects (GPOs) in the production environment and indicates the allowed permissions of each user or group.
-
-This tab allows an AGPM Administrator (Full Control) to modify the default delegation of access to GPOs in the production environment of the domain, adding or removing users and groups, and modifying the allowed permissions for each user and group.
-
-
-
-
-
-
-
-
-
Button
-
Effect
-
-
-
-
-
Add
-
Add a new entry to the security descriptor.
-
-
-
Remove
-
Remove the selected users or groups from the Access Control List.
-
-
-
Properties
-
Display the properties for the selected user or group. The properties page is the same one displayed for an object in Active Directory User and Computers.
-
-
-
-
-
-
-### Additional references
-
-- [User Interface: Advanced Group Policy Management](user-interface-advanced-group-policy-management-agpm40.md)
-
-- [Performing AGPM Administrator Tasks](performing-agpm-administrator-tasks-agpm40.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/recycle-bin-commands-agpm30ops.md b/mdop/agpm/recycle-bin-commands-agpm30ops.md
deleted file mode 100644
index 7f252a28e7..0000000000
--- a/mdop/agpm/recycle-bin-commands-agpm30ops.md
+++ /dev/null
@@ -1,129 +0,0 @@
----
-title: Recycle Bin Commands
-description: Recycle Bin Commands
-author: dansimp
-ms.assetid: ffe8f020-7aa9-40ad-8019-cc99901a7840
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Recycle Bin Commands
-
-
-The **Recycle Bin** tab:
-
-- Displays a list of Group Policy Objects (GPOs) that have been deleted from the archive.
-
-- Provides a shortcut menu with commands for managing GPOs and for displaying reports for GPOs.
-
-- Displays a list of the groups and users who have permission to access a selected GPO.
-
-Right-clicking the **Group Policy Objects** list on this tab displays a shortcut menu, including whichever of the following options are applicable:
-
-## Reports
-
-
-
-
-
-
-
-
-
-
Command
-
Effect
-
-
-
-
-
Settings
-
Generate an HTML-based or XML-based report displaying the settings within the selected GPO or display links to the selected GPOs from organizational units as of when the GPOs were most recently controlled, imported, or checked in.
-
-
-
Differences
-
Generate an HTML-based or XML-based report comparing the settings within two selected GPOs or within the selected GPO and a template.
-
-
-
-
-
-
-## Version management
-
-
-
-
-
-
-
-
-
-
Command
-
Effect
-
-
-
-
-
Destroy
-
Remove the selected GPO from the Recycle Bin, so it can no longer be restored.
-
-
-
Restore
-
Move the selected GPO from the Recycle Bin to the Controlled tab. This does not restore the GPO to the production environment.
-
-
-
-
-
-
-## Miscellaneous
-
-
-
-
-
-
-
-
-
-
Command
-
Effect
-
-
-
-
-
Refresh
-
Update the display of the Group Policy Management Console (GPMC) to incorporate any changes. Some changes are not visible until the display is refreshed.
-
-
-
Help
-
Display help for Advanced Group Policy Management (AGPM).
-
-
-
-
-
-
-### Additional references
-
-- [Contents Tab](contents-tab-agpm30ops.md)
-
-- [Performing Approver Tasks](performing-approver-tasks-agpm30ops.md)
-
-- [Performing Reviewer Tasks](performing-reviewer-tasks-agpm30ops.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/recycle-bin-commands-agpm40.md b/mdop/agpm/recycle-bin-commands-agpm40.md
deleted file mode 100644
index e25387fa75..0000000000
--- a/mdop/agpm/recycle-bin-commands-agpm40.md
+++ /dev/null
@@ -1,129 +0,0 @@
----
-title: Recycle Bin Commands
-description: Recycle Bin Commands
-author: dansimp
-ms.assetid: 347a101f-0ba0-4afc-bd59-752cc06bb904
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Recycle Bin Commands
-
-
-The **Recycle Bin** tab:
-
-- Displays a list of Group Policy Objects (GPOs) that have been deleted from the archive.
-
-- Provides a shortcut menu with commands for managing GPOs and for displaying reports for GPOs.
-
-- Displays a list of the groups and users who have permission to access a selected GPO.
-
-Right-clicking the **Group Policy Objects** list on this tab displays a shortcut menu, including whichever of the following options are applicable:
-
-## Reports
-
-
-
-
-
-
-
-
-
-
Command
-
Effect
-
-
-
-
-
Settings
-
Generate an HTML-based or XML-based report displaying the settings within the selected GPO or display links to the selected GPOs from organizational units as of when the GPOs were most recently controlled, imported, or checked in.
-
-
-
Differences
-
Generate an HTML-based or XML-based report comparing the settings within two selected GPOs or within the selected GPO and a template.
-
-
-
-
-
-
-## Version management
-
-
-
-
-
-
-
-
-
-
Command
-
Effect
-
-
-
-
-
Destroy
-
Remove the selected GPO from the Recycle Bin, so it can no longer be restored.
-
-
-
Restore
-
Move the selected GPO from the Recycle Bin to the Controlled tab. This does not restore the GPO to the production environment.
-
-
-
-
-
-
-## Miscellaneous
-
-
-
-
-
-
-
-
-
-
Command
-
Effect
-
-
-
-
-
Refresh
-
Update the display of the Group Policy Management Console (GPMC) to incorporate any changes. Some changes are not visible until the display is refreshed.
-
-
-
Help
-
Display help for Advanced Group Policy Management (AGPM).
-
-
-
-
-
-
-### Additional references
-
-- [Contents Tab](contents-tab-agpm40.md)
-
-- [Performing Approver Tasks](performing-approver-tasks-agpm40.md)
-
-- [Performing Reviewer Tasks](performing-reviewer-tasks-agpm40.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/recycle-bin-tab.md b/mdop/agpm/recycle-bin-tab.md
deleted file mode 100644
index 5b47c0650b..0000000000
--- a/mdop/agpm/recycle-bin-tab.md
+++ /dev/null
@@ -1,129 +0,0 @@
----
-title: Recycle Bin Tab
-description: Recycle Bin Tab
-author: dansimp
-ms.assetid: 9ce62e98-c03e-4a75-90e0-51be83c6d2db
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Recycle Bin Tab
-
-
-The **Recycle Bin** tab:
-
-- Displays a list of Group Policy objects (GPOs) that have been deleted from the archive.
-
-- Provides a shortcut menu with commands for managing GPOs and for displaying reports for GPOs.
-
-- Displays a list of the groups and users who have permission to access a selected GPO.
-
-Right-clicking the **Group Policy Objects** list on this tab displays a shortcut menu, including whichever of the following options are applicable:
-
-## Reports
-
-
-
-
-
-
-
-
-
-
Command
-
Effect
-
-
-
-
-
Settings
-
Generate an HTML-based or XML-based report displaying the settings within the selected GPO or display links to the selected GPOs from organizational units as of when the GPOs were most recently controlled, imported, or checked in.
-
-
-
Differences
-
Generate an HTML-based or XML-based report comparing the settings within two selected GPOs or within the selected GPO and a template.
-
-
-
-
-
-
-## Version management
-
-
-
-
-
-
-
-
-
-
Command
-
Effect
-
-
-
-
-
Destroy
-
Remove the selected GPO from the Recycle Bin, so it can no longer be restored.
-
-
-
Restore
-
Move the selected GPO from the Recycle Bin to the Controlled tab. This does not restore the GPO to the production environment.
-
-
-
-
-
-
-## Miscellaneous
-
-
-
-
-
-
-
-
-
-
Command
-
Effect
-
-
-
-
-
Refresh
-
Update the display of the Group Policy Management Console to incorporate any changes. Some changes are not visible until the display is refreshed.
-
-
-
Help
-
Display help for AGPM.
-
-
-
-
-
-
-### Additional references
-
-- [Contents Tab](contents-tab.md)
-
-- [Performing Approver Tasks](performing-approver-tasks.md)
-
-- [Performing Reviewer Tasks](performing-reviewer-tasks.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/release-notes-for-microsoft-advanced-group-policy-management-40-sp1.md b/mdop/agpm/release-notes-for-microsoft-advanced-group-policy-management-40-sp1.md
deleted file mode 100644
index d727f2d26b..0000000000
--- a/mdop/agpm/release-notes-for-microsoft-advanced-group-policy-management-40-sp1.md
+++ /dev/null
@@ -1,91 +0,0 @@
----
-title: Release Notes for Microsoft Advanced Group Policy Management 4.0 SP1
-description: Release Notes for Microsoft Advanced Group Policy Management 4.0 SP1
-author: dansimp
-ms.assetid: 91835bf8-e53c-4202-986e-8d37050d1267
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 08/30/2016
----
-
-
-# Release Notes for Microsoft Advanced Group Policy Management 4.0 SP1
-
-
-To search these release notes, press Ctrl+F.
-
-Read these release notes thoroughly before you install Microsoft Advanced Group Policy Management (AGPM) 4.0 SP1. These release notes contain information that is required to successfully install AGPM 4.0 SP1 and contain information that is not available in the product documentation. If there is a difference between these release notes and other AGPM documentation, the latest change should be considered authoritative. These release notes supersede the content included with this product.
-
-## AGPM 4.0 SP1 known issues
-
-
-This section contains release notes for AGPM 4.0 SP1.
-
-### Control Panel’s “Uninstall” tool may not work when you try to change AGPM Server settings
-
-The tool in Control Panel that lets you uninstall or change a program may not work when you try to change AGPM server settings.
-
-WORKAROUND: Before you try to change AGPM server settings by using Control Panel, make a copy of the AGPM Archive folder. You can then use Setup.exe to reinstall the AGPM server and choose the configuration parameters that you want.
-
-### Reports do not display the links that were added to a Group Policy Object
-
-The AGPM settings and difference reports do not display the links that were added to a Group Policy Object (GPO).
-
-WORKAROUND: To view the links in the reports, select the GPO in the Group Policy Management Console (GPMC), and click the **Settings** tab in the right pane.
-
-### Reports do not display all “Choice Options Properties” settings
-
-The AGPM settings and difference reports do not display all of the settings that were selected on the Choice Options Properties window in the Group Policy Object Editor.
-
-WORKAROUND: Use the GPMC to view the selected Choice Options Properties settings in the reports.
-
-### Reports do not display the Show and Hide tabs in certain browsers
-
-The Show and Hide tabs, shown on the right side of the AGPM settings and difference reports, are not displayed when you view the reports in Google Chrome or Mozilla Firefox.
-
-WORKAROUND: View the reports by using Internet Explorer.
-
-### AGPM settings and difference reports may show different content from GPMC reports
-
-The AGPM settings and difference reports may not show the same content as reports in the Group Policy Management Console (GPMC).
-
-WORKAROUND: Use the GPMC to view the AGPM reports.
-
-### AGPM Service does not start if the domain controller is not online
-
-When the AGPM Service is installed on a domain controller on Windows 8, the Service does not start if the domain controller is not online.
-
-WORKAROUND: Manually start the AGPM Service after the domain controller is online.
-
-### Upgrade of AGPM Server to AGPM 4.0 SP1 is blocked when you upgrade from the AGPM 4.0 release plus the hotfix
-
-If you try to upgrade the AGPM server to AGPM 4.0. SP1 after installing AGPM 4.0 and then installing the AGPM hotfix (see Knowledge Base article [2643502](https://go.microsoft.com/fwlink/?LinkId=254474)), the upgrade fails and cannot be completed.
-
-WORKAROUND: Uninstall the AGPM 4.0 Server and then install AGPM 4.0 SP1.
-
-### Reports do not display organizational unit links
-
-If you link an uncontrolled GPO to an organizational unit and then control that GPO using AGPM, the AGPM settings and difference reports do not display the organizational unit links.
-
-WORKAROUND: From the **Controlled** tab of the **Change Settings** node, right-click the GPO and click **Settings** and then click **GPO Links** to view the organizational links. Alternatively, you can use the GPMC to view the links to a GPO from the **Scope** tab.
-
-## Related topics
-
-
-[Advanced Group Policy Management](index.md)
-
-[What's New in AGPM 4.0 SP1](whats-new-in-agpm-40-sp1.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/release-notes-for-microsoft-advanced-group-policy-management-40-sp2.md b/mdop/agpm/release-notes-for-microsoft-advanced-group-policy-management-40-sp2.md
deleted file mode 100644
index 5ce4c30b65..0000000000
--- a/mdop/agpm/release-notes-for-microsoft-advanced-group-policy-management-40-sp2.md
+++ /dev/null
@@ -1,103 +0,0 @@
----
-title: Release Notes for Microsoft Advanced Group Policy Management 4.0 SP2
-description: Release Notes for Microsoft Advanced Group Policy Management 4.0 SP2
-author: dansimp
-ms.assetid: 0593cd11-3308-4942-bf19-8a7bb9447f01
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 08/30/2016
----
-
-
-# Release Notes for Microsoft Advanced Group Policy Management 4.0 SP2
-
-
-To search these release notes, press Ctrl+F.
-
-Read these release notes thoroughly before you install Microsoft Advanced Group Policy Management (AGPM) 4.0 Service Pack 2 (SP2). These release notes contain information that is required to successfully install AGPM 4.0 SP2 and contain information that is not available in the product documentation. If there is a difference between these release notes and other AGPM documentation, consider the latest change authoritative. These release notes supersede the content included with this product.
-
-## AGPM 4.0 SP2 known issues
-
-
-This section describes the known issues for AGPM 4.0 SP2.
-
-### Control Panel’s “Uninstall” tool may not work when you try to change AGPM Server settings
-
-The tool in Control Panel that you use to uninstall or change a program may not work when you try to change AGPM Server settings.
-
-**Workaround:** Before you try to change AGPM Server settings by using Control Panel, make a copy of the AGPM Archive folder. You can then use Setup.exe to reinstall the AGPM Server and choose the configuration parameters that you want.
-
-### Reports do not display the links that were added to a Group Policy Object
-
-The AGPM settings and difference reports do not display the links that were added to a Group Policy Object (GPO).
-
-**Workaround:** To view the links in the reports, select the GPO in the Group Policy Management Console (GPMC), and then click the **Settings** tab in the right pane.
-
-### Reports do not display all Choice Options Properties settings
-
-The AGPM settings and difference reports do not display all of the settings that were selected in the **Choice Options Properties** window in the Group Policy Object Editor.
-
-**Workaround:** Use the GPMC to view the selected **Choice Options Properties** settings in the reports.
-
-### Reports may not display the Show and Hide tabs in certain browsers
-
-The **Show** and **Hide** tabs, on the right side of the AGPM settings and difference reports, may not appear when you view the reports in Google Chrome or Mozilla Firefox.
-
-**Workaround:** View the reports by using the Internet Explorer browser.
-
-### AGPM settings and difference reports may show different content from GPMC reports
-
-The AGPM settings and difference reports may not show the same content as reports in the GPMC.
-
-**Workaround:** Use the GPMC to view the AGPM reports.
-
-### AGPM Service does not start if the domain controller is offline
-
-When the AGPM Service is installed on a domain controller on the Windows® 8 operating systems or later operating systems, the service does not start if the domain controller is offline.
-
-**Workaround:** Manually start the AGPM Service after the domain controller is online.
-
-### Upgrade of AGPM Server to AGPM 4.0 SP2 is blocked when you upgrade from the AGPM 4.0 release plus hotfix 1
-
-If you try to upgrade the AGPM server to AGPM 4.0. SP2 after installing AGPM 4.0 Server and then installing the AGPM hotfix named AGPM 4.0 reports incorrect differences in the HTML report (see Knowledge Base article [2643502](https://go.microsoft.com/fwlink/?LinkId=254474)), the upgrade fails and cannot be completed.
-
-**Workaround:** Uninstall the AGPM 4.0 Server and then install AGPM 4.0 SP2.
-
-### Reports do not display organizational unit links
-
-If you link an uncontrolled GPO to an organizational unit and then control that GPO by using AGPM, the AGPM settings and difference reports do not display the organizational unit links.
-
-**Workaround:** On the **Controlled** tab of the **Change Settings** node, right-click the GPO, click **Settings**, and then click **GPO Links** to view the organizational links. Alternatively, you can use the GPMC to view the links to a GPO from the **Scope** tab.
-
-### AGPM displays an error if you click the Back button from the Change, Repair, or Remove AGPM Client dialog box
-
-If you browse to **Programs and Features** in Control Panel and then select **Microsoft Advanced Group Policy Management – Client**, AGPM displays an error if you click **Modify** and then click the **Back** button in the **Change, Repair, or Remove AGPM Client** dialog box.
-
-**Workaround:** Click **Cancel** to clear the error, and then start the process again. Do not click the **Back** button after you click **Modify** .
-
-### Comment fails to appear in the History window when the Approver deploys a GPO and enters a comment
-
-If a user who has the Editor role submits a request to deploy a GPO, and the user who has the Approver role then deploys the GPO and enters a comment, the comment fails to appear in the **History** window.
-
-**Workaround:** None.
-
-## Related topics
-
-
-[Advanced Group Policy Management](index.md)
-
-[What's New in AGPM 4.0 SP2](whats-new-in-agpm-40-sp2.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/release-notes-for-microsoft-advanced-group-policy-management-40-sp3.md b/mdop/agpm/release-notes-for-microsoft-advanced-group-policy-management-40-sp3.md
deleted file mode 100644
index 24f3ccb1f0..0000000000
--- a/mdop/agpm/release-notes-for-microsoft-advanced-group-policy-management-40-sp3.md
+++ /dev/null
@@ -1,113 +0,0 @@
----
-title: Release Notes for Microsoft Advanced Group Policy Management 4.0 SP3
-description: Release Notes for Microsoft Advanced Group Policy Management 4.0 SP3
-author: dansimp
-ms.assetid: 955d7674-a8d9-4fc5-b18a-5a1639e38014
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 09/27/2016
----
-
-
-# Release Notes for Microsoft Advanced Group Policy Management 4.0 SP3
-
-
-To search these release notes, press Ctrl+F.
-
-Read these release notes thoroughly before you install Microsoft Advanced Group Policy Management (AGPM) 4.0 Service Pack 3 (SP3). These release notes contain information that is required to successfully install AGPM 4.0 SP3 and contain information that is not available in the product documentation. If there is a difference between these release notes and other AGPM documentation, consider the latest change authoritative. These release notes supersede the content included with this product.
-
-## AGPM 4.0 SP3 known issues
-
-
-This section describes the known issues for AGPM 4.0 SP3.
-
-### AGPM installation fails in Windows 10
-
-AGPM internally enables the Windows Communication Foundation (WCF)-NonHTTP-Activation feature during installation. In Windows 10, WCF now includes a requirement to restart Windows after enabling the WCF NonHTTP-Activation feature. However, the current AGPM installer code does not handle this restart requirement and stops responding while it waits for the service to be activated.
-
-**Workaround:** Before you run the AGPM installer, enable the WCF Non-HTTP Activation feature and then restart Windows.
-
-### Control Panel’s “Uninstall” tool may not work when you try to change AGPM Server settings
-
-The tool in Control Panel that you use to uninstall or change a program may not work when you try to change AGPM Server settings.
-
-**Workaround:** Before you try to change AGPM Server settings by using Control Panel, make a copy of the AGPM Archive folder. You can then use Setup.exe to reinstall the AGPM Server and choose the configuration parameters that you want.
-
-### Reports do not display the links that were added to a Group Policy Object
-
-The AGPM settings and difference reports do not display the links that were added to a Group Policy Object (GPO).
-
-**Workaround:** To view the links in the reports, select the GPO in the Group Policy Management Console (GPMC), and then click the **Settings** tab in the right pane.
-
-### Reports do not display all Choice Options Properties settings
-
-The AGPM settings and difference reports do not display all of the settings that were selected in the **Choice Options Properties** window in the Group Policy Object Editor.
-
-**Workaround:** Use the GPMC to view the selected **Choice Options Properties** settings in the reports.
-
-### Reports may not display the Show and Hide tabs in certain browsers
-
-The **Show** and **Hide** tabs, on the right side of the AGPM settings and difference reports, may not appear when you view the reports in Google Chrome or Mozilla Firefox.
-
-**Workaround:** View the reports by using the Internet Explorer browser.
-
-### AGPM settings and difference reports may show different content from GPMC reports
-
-The AGPM settings and difference reports may not show the same content as reports in the GPMC.
-
-**Workaround:** Use the GPMC to view the AGPM reports.
-
-### AGPM Service does not start if the domain controller is offline
-
-When the AGPM Service is installed on a domain controller on the Windows® 8 operating systems or later operating systems, the service does not start if the domain controller is offline.
-
-**Workaround:** Manually start the AGPM Service after the domain controller is online.
-
-### Upgrade of AGPM Server to AGPM 4.0 SP2 is blocked when you upgrade from the AGPM 4.0 release plus hotfix 1
-
-If you try to upgrade the AGPM server to AGPM 4.0. SP2 after installing AGPM 4.0 Server and then installing the AGPM hotfix named AGPM 4.0 reports incorrect differences in the HTML report (see Knowledge Base article [2643502](https://go.microsoft.com/fwlink/?LinkId=254474)), the upgrade fails and cannot be completed.
-
-**Workaround:** Uninstall the AGPM 4.0 Server and then install AGPM 4.0 SP2.
-
-### Reports do not display organizational unit links
-
-If you link an uncontrolled GPO to an organizational unit and then control that GPO by using AGPM, the AGPM settings and difference reports do not display the organizational unit links.
-
-**Workaround:** On the **Controlled** tab of the **Change Settings** node, right-click the GPO, click **Settings**, and then click **GPO Links** to view the organizational links. Alternatively, you can use the GPMC to view the links to a GPO from the **Scope** tab.
-
-### AGPM displays an error if you click the Back button from the Change, Repair, or Remove AGPM Client dialog box
-
-If you browse to **Programs and Features** in Control Panel and then select **Microsoft Advanced Group Policy Management – Client**, AGPM displays an error if you click **Modify** and then click the **Back** button in the **Change, Repair, or Remove AGPM Client** dialog box.
-
-**Workaround:** Click **Cancel** to clear the error, and then start the process again. Do not click the **Back** button after you click **Modify** .
-
-### Comment fails to appear in the History window when the Approver deploys a GPO and enters a comment
-
-If a user who has the Editor role submits a request to deploy a GPO, and the user who has the Approver role then deploys the GPO and enters a comment, the comment fails to appear in the **History** window.
-
-**Workaround:** None.
-
-### Added mechanism to override AGPM default behavior of removing GPO permission changes
-
-As of HF02, AGPM has added a registry key to enable overriding the default AGPM GPO permission behavior. For more information, please see [Changes to Group Policy object permissions through AGPM are ignored](https://support.microsoft.com/kb/3174540)
-
-## Related topics
-
-
-[Advanced Group Policy Management](index.md)
-
-[What's New in AGPM 4.0 SP3](whats-new-in-agpm-40-sp3.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/release-notes-for-microsoft-advanced-group-policy-management-40.md b/mdop/agpm/release-notes-for-microsoft-advanced-group-policy-management-40.md
deleted file mode 100644
index 5fa848da03..0000000000
--- a/mdop/agpm/release-notes-for-microsoft-advanced-group-policy-management-40.md
+++ /dev/null
@@ -1,110 +0,0 @@
----
-title: Release Notes for Microsoft Advanced Group Policy Management 4.0
-description: Release Notes for Microsoft Advanced Group Policy Management 4.0
-author: dansimp
-ms.assetid: 44c19e61-c8e8-48aa-a2c2-20396d14d5bb
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 08/30/2016
----
-
-
-# Release Notes for Microsoft Advanced Group Policy Management 4.0
-
-
-October 2009
-
-## About Microsoft Advanced Group Policy Management 4.0
-
-
-Microsoft Advanced Group Policy Management (AGPM) 4.0 extends the capabilities of the Group Policy Management Console (GPMC). AGPM provides comprehensive change control and improved management of Group Policy Objects (GPOs).
-
-The following documents can help you get started with AGPM 4.0.
-
-- For an overview of the capabilities of AGPM, see [Overview of Microsoft Advanced Group Policy Management](https://go.microsoft.com/fwlink/?LinkID=162671) (https://go.microsoft.com/fwlink/?LinkID=162671).
-
-- For information about how AGPM 4.0 differs from AGPM 3.0, see [What's New in AGPM 4.0](https://go.microsoft.com/fwlink/?LinkId=160058) (https://go.microsoft.com/fwlink/?LinkId=160058).
-
-- For guidance about how to determine whether AGPM 4.0, AGPM 3.0, or AGPM 2.5 is appropriate for your environment, see [Choosing Which Version of AGPM to Install](https://go.microsoft.com/fwlink/?LinkId=145981) (https://go.microsoft.com/fwlink/?LinkId=145981).
-
-- For basic guidance about how to install AGPM and a sample scenario for using AGPM, see [Step-by-Step Guide for Microsoft Advanced Group Policy Management 4.0](https://go.microsoft.com/fwlink/?LinkID=153505) (https://go.microsoft.com/fwlink/?LinkID=153505). This guide is primarily designed to help evaluators and first-time users.
-
-- For information about how to upgrade from an earlier version of AGPM or detailed guidance about how to plan the deployment of AGPM in your organization, see the [Planning Guide for Microsoft Advanced Group Policy Management 4.0](https://go.microsoft.com/fwlink/?LinkID=156883) (https://go.microsoft.com/fwlink/?LinkID=156883).
-
-- For information about how to use AGPM to perform specific tasks, see the Advanced Group Policy Management 4.0 Help, which is also available on TechNet as the [Operations Guide for AGPM 4.0](https://go.microsoft.com/fwlink/?LinkId=159872) (https://go.microsoft.com/fwlink/?LinkId=159872).
-
-## More information
-
-
-For more information about AGPM, see the following:
-
-- [Advanced Group Policy Management TechNet Library](https://go.microsoft.com/fwlink/?LinkID=146846) (https://go.microsoft.com/fwlink/?LinkID=146846)
-
-- [Microsoft Desktop Optimization Pack TechCenter](https://go.microsoft.com/fwlink/?LinkId=159870) (https://www.microsoft.com/technet/mdop)
-
-- [Group Policy TechCenter](https://go.microsoft.com/fwlink/?LinkId=145531) (https://www.microsoft.com/gp)
-
-## Providing feedback
-
-
-You can post feedback or questions about AGPM to the [Group Policy Forum](https://go.microsoft.com/fwlink/?LinkId=145532) (https://go.microsoft.com/fwlink/?LinkId=145532).
-
-## Known issues with AGPM 4.0
-
-
-### Import from Production command does not import settings into a GPO that is checked out
-
-If you edit a GPO in the production environment, you must import the GPO from production to update the GPO in the offline archive. The **Import from Production** command is intended to let you perform a final production backup before you finish editing so that you can roll back to the production backup if it is necessary.
-
-If the GPO is checked out when you run the **Import from Production** command, then the production changes are not incorporated into the checked out version of the GPO. However, the imported version of the GPO is added to the history of the GPO even though that version is not available to be edited. When the GPO is checked in, that version will supersede the imported version in the archive, but both are available in the history of the GPO.
-
-**Workaround:** Make sure that the GPO is checked in before you import it from production. If the GPO was not checked in before you imported it, you can use the **Undo Check Out** command to discard your changes and roll back to the version of the GPO that you imported from production.
-
-### Checked out GPOs cannot be edited for several minutes in an environment that uses a multiple site Active Directory topology
-
-AGPM uses a client/server model. The AGPM Server and the AGPM Client each determine their own closest domain controller for Group Policy operations. When you check out a GPO by using an AGPM Client, it is actually the AGPM Server that checks the GPO out from the offline archive to a temporary folder in the SYSVOL folder.
-
-If the AGPM Server and the AGPM Client are in different sites, then the temporary checked out GPO may not be present on the local site's domain controller for several minutes or up to 30 minutes due to SYSVOL replication latency. In this situation, you cannot edit the checked out GPO using the GPMC on an AGPM Client until SYSVOL replication of the checked out GPO has occurred.
-
-**Workaround:** As a best practice, you should position AGPM Clients in the same site as the AGPM Server to which they connect so that you do not have to wait for SYSVOL replication to occur before you can edit a checked out GPO.
-
-### AGPM cannot read the backup limit if your account does not have permissions for the archive
-
-On an AGPM Client, if you log on by using an account that has not been delegated permissions to the AGPM archive, start the Group Policy Management Console (GPMC), and then click **Change Control**, you receive the following error.
-
-``` syntax
-Failed to read backup purge limit for this domain.
-
-The following error occurred:
-You do not have sufficient permissions to perform this operation.
-Microsoft.Agpm.AccessDeniedException (80070005)
-```
-
-**Workaround:** Contact an AGPM Administrator (Full Control) and request that they delegate access to AGPM for your account. If you are an AGPM Administrator, log on by using an account to which the AGPM Administrator role is assigned so that you can delegate access for the additional account. For more information, see "Delegate Domain-Level Access to the Archive" in the AGPM Help.
-
-## Release notes copyright information
-
-
-Information in this document, including URL and other Internet Web site references, is subject to change without notice, and is provided for informational purposes only. The entire risk of the use or results of the use of this document remains with the user, and Microsoft Corporation makes no warranties, either express or implied. The example companies, organizations, products, people and events depicted herein are fictitious. No association with any real company, organization, product, person or event is intended or should be inferred. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.
-
-Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.
-
-
-
-Microsoft, MS-DOS, Windows, Windows Server, and Windows Vista are either registered trademarks or trademarks of Microsoft Corporation in the U.S.A. and/or other countries.
-
-The names of actual companies and products mentioned herein may be the trademarks of their respective owners.
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/rename-a-gpo-or-template-agpm30ops.md b/mdop/agpm/rename-a-gpo-or-template-agpm30ops.md
deleted file mode 100644
index 891a770b95..0000000000
--- a/mdop/agpm/rename-a-gpo-or-template-agpm30ops.md
+++ /dev/null
@@ -1,53 +0,0 @@
----
-title: Rename a GPO or Template
-description: Rename a GPO or Template
-author: dansimp
-ms.assetid: 19d17ddf-8b58-4677-929e-9550fa388b93
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Rename a GPO or Template
-
-
-You can rename a controlled Group Policy Object (GPO) or a template.
-
-A user account with the Editor or AGPM Administrator (Full Control) role, the user account of the Approver who created the GPO, or a user account with the necessary permissions in Advanced Group Policy Management (AGPM) is required to complete this procedure. Review the details in "Additional considerations" in this topic.
-
-**To rename a GPO or template**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. On the **Contents** tab, click the **Controlled** or **Templates** tab to display the item to rename.
-
-3. Right-click the GPO or template to rename and click **Rename**.
-
-4. Type the new name for the GPO or template and a comment, and then click **OK**.
-
-5. When the **Progress** window indicates that overall progress is complete, click **Close**. The GPO or template appears under the new name on the **Contents** tab.
-
-### Additional considerations
-
-- By default, you must be the Approver who created or controlled the GPO, an Editor, or an AGPM Administrator (Full Control) to perform this procedure. Specifically, you must have **List Contents** and **Edit Settings** permission for the GPO.
-
-- When you rename a GPO that has been deployed, the name is immediately changed in the archive. The name is changed in the production environment only when the GPO is redeployed. Until the GPO is redeployed (or the production copy is deleted), the old name is still in use in the production environment and therefore cannot be used for another GPO. Likewise, the GPO in the archive cannot be renamed back to its original name until the GPO has been deployed (changing the name of the production copy) or the production copy has been deleted.
-
-### Additional references
-
-- [Editing a GPO](editing-a-gpo-agpm30ops.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/rename-a-gpo-or-template-agpm40.md b/mdop/agpm/rename-a-gpo-or-template-agpm40.md
deleted file mode 100644
index 6eddae8e9e..0000000000
--- a/mdop/agpm/rename-a-gpo-or-template-agpm40.md
+++ /dev/null
@@ -1,53 +0,0 @@
----
-title: Rename a GPO or Template
-description: Rename a GPO or Template
-author: dansimp
-ms.assetid: 84293f7a-4ff7-497e-bdbc-cabb70189a03
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Rename a GPO or Template
-
-
-You can rename a controlled Group Policy Object (GPO) or a template.
-
-A user account with the Editor or AGPM Administrator (Full Control) role, the user account of the Approver who created the GPO, or a user account with the necessary permissions in Advanced Group Policy Management (AGPM) is required to complete this procedure. Review the details in "Additional considerations" in this topic.
-
-**To rename a GPO or template**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. On the **Contents** tab, click the **Controlled** or **Templates** tab to display the item to rename.
-
-3. Right-click the GPO or template to rename and click **Rename**.
-
-4. Type the new name for the GPO or template and a comment, and then click **OK**.
-
-5. When the **Progress** window indicates that overall progress is complete, click **Close**. The GPO or template appears under the new name on the **Contents** tab.
-
-### Additional considerations
-
-- By default, you must be the Approver who created or controlled the GPO, an Editor, or an AGPM Administrator (Full Control) to perform this procedure. Specifically, you must have **List Contents** and **Edit Settings** permission for the GPO.
-
-- When you rename a GPO that has been deployed, the name is immediately changed in the archive. The name is changed in the production environment only when the GPO is redeployed. Until the GPO is redeployed (or the production copy is deleted), the old name is still in use in the production environment and therefore cannot be used for another GPO. Likewise, the GPO in the archive cannot be renamed back to its original name until the GPO has been deployed (changing the name of the production copy) or the production copy has been deleted.
-
-### Additional references
-
-- [Editing a GPO](editing-a-gpo-agpm40.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/rename-a-gpo-or-template.md b/mdop/agpm/rename-a-gpo-or-template.md
deleted file mode 100644
index b4f6b328cf..0000000000
--- a/mdop/agpm/rename-a-gpo-or-template.md
+++ /dev/null
@@ -1,55 +0,0 @@
----
-title: Rename a GPO or Template
-description: Rename a GPO or Template
-author: dansimp
-ms.assetid: 64a1aaf4-f672-48b5-94c6-473bf1076cf3
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Rename a GPO or Template
-
-
-You can rename a controlled Group Policy object (GPO) or a template.
-
-A user account with the Editor or AGPM Administrator (Full Control) role, the user account of the Approver who created the GPO, or a user account with the necessary permissions in Advanced Group Policy Management is required to complete this procedure. Review the details in "Additional considerations" in this topic.
-
-**To rename a GPO or template**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. On the **Contents** tab, click the **Controlled** or **Templates** tab to display the item to rename.
-
-3. Right-click the GPO or template to rename and click **Rename**.
-
-4. Type the new name for the GPO or template and a comment, then click **OK**.
-
-5. When the **Progress** window indicates that overall progress is complete, click **Close**. The GPO or template appears under the new name on the **Contents** tab.
-
-### Additional considerations
-
-- By default, you must be the Approver who created or controlled the GPO, an Editor, or an AGPM Administrator (Full Control) to perform this procedure. Specifically, you must have **List Contents** and **Edit Settings** permission for the GPO.
-
-- When you rename a GPO that has been deployed, the name is immediately changed in the archive. The name is changed in the production environment only when the GPO is redeployed.
-
- Until the GPO is redeployed (or the production copy is deleted), the old name is still in use in the production environment and therefore cannot be used for another GPO. Likewise, the GPO in the archive cannot be renamed back to its original name until the GPO has been deployed (changing the name of the production copy) or the production copy has been deleted.
-
-### Additional references
-
-- [Editing a GPO](editing-a-gpo.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/request-control-of-a-previously-uncontrolled-gpo.md b/mdop/agpm/request-control-of-a-previously-uncontrolled-gpo.md
deleted file mode 100644
index 48168f5274..0000000000
--- a/mdop/agpm/request-control-of-a-previously-uncontrolled-gpo.md
+++ /dev/null
@@ -1,53 +0,0 @@
----
-title: Request Control of a Previously Uncontrolled GPO
-description: Request Control of a Previously Uncontrolled GPO
-author: dansimp
-ms.assetid: 00e8725d-5d7f-4eed-a5e6-c3631632cfbd
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Request Control of a Previously Uncontrolled GPO
-
-
-To use Advanced Group Policy Management (AGPM) to provide change control for an existing Group Policy object (GPO), the GPO must be controlled with AGPM. Unless you are an Approver or an AGPM Administrator (Full Control), you must request that the GPO be controlled.
-
-A user account with the Editor or Reviewer role or necessary permissions in Advanced Group Policy Management is required to complete this procedure. Review the details in "Additional considerations" in this topic.
-
-**To control a previously uncontrolled GPO**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. On the **Contents** tab in the details pane, click the **Uncontrolled** tab to display the uncontrolled GPOs.
-
-3. Right-click the GPO to be controlled with AGPM, and then click **Control**.
-
-4. Unless you have special permission to control GPOs, you must submit a request for control. To receive a copy of the request, type your e-mail address in the **Cc** field. Type a comment to be displayed in the **History** of the GPO, and then click **Submit**.
-
-5. When the **Progress** window indicates that overall progress is complete, click **Close**. The GPO is removed from the list on the **Uncontrolled** tab and added to the **Pending** tab. When an Approver has approved your request, the GPO will be moved to the **Controlled** tab.
-
-### Additional considerations
-
-- By default, you must be an Editor or a Reviewer to perform this procedure. Specifically, you must have **List Contents** and **Read Settings** permissions for the domain.
-
-- To withdraw your request before it has been approved, click the **Pending** tab. Right-click the GPO, and then click **Withdraw**. The GPO will be returned to the **Uncontrolled** tab.
-
-### Additional references
-
-- [Creating, Controlling, or Importing a GPO](creating-controlling-or-importing-a-gpo-editor.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/request-control-of-an-uncontrolled-gpo-agpm30ops.md b/mdop/agpm/request-control-of-an-uncontrolled-gpo-agpm30ops.md
deleted file mode 100644
index 90dde7498f..0000000000
--- a/mdop/agpm/request-control-of-an-uncontrolled-gpo-agpm30ops.md
+++ /dev/null
@@ -1,53 +0,0 @@
----
-title: Request Control of an Uncontrolled GPO
-description: Request Control of an Uncontrolled GPO
-author: dansimp
-ms.assetid: b668a67a-5a2c-4f6a-8b1c-efa3ca0794d4
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Request Control of an Uncontrolled GPO
-
-
-To provide change control for an existing Group Policy Object (GPO), the GPO must be controlled. Unless you are an Approver or an AGPM Administrator (Full Control), you must request that the GPO be controlled.
-
-A user account with the Editor or Reviewer role or necessary permissions in Advanced Group Policy Management (AGPM) is required to complete this procedure. Review the details in "Additional considerations" in this topic.
-
-**To control an uncontrolled GPO**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. On the **Contents** tab in the details pane, click the **Uncontrolled** tab to display the uncontrolled GPOs.
-
-3. Right-click the GPO to be controlled with AGPM, and then click **Control**.
-
-4. Unless you have special permission to control GPOs, you must submit a request for control. To receive a copy of the request, type your e-mail address in the **Cc** field. Type a comment to be displayed in the **History** of the GPO, and then click **Submit**.
-
-5. When the **Progress** window indicates that overall progress is complete, click **Close**. The GPO is removed from the list on the **Uncontrolled** tab and added to the **Pending** tab. When an Approver has approved your request, the GPO will be moved to the **Controlled** tab.
-
-### Additional considerations
-
-- By default, you must be an Editor or a Reviewer to perform this procedure. Specifically, you must have **List Contents** and **Read Settings** permissions for the domain.
-
-- To withdraw your request before it has been approved, click the **Pending** tab. Right-click the GPO, and then click **Withdraw**. The GPO will be returned to the **Uncontrolled** tab.
-
-### Additional references
-
-- [Creating, Controlling, or Importing a GPO](creating-controlling-or-importing-a-gpo-agpm30ops.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/request-control-of-an-uncontrolled-gpo-agpm40.md b/mdop/agpm/request-control-of-an-uncontrolled-gpo-agpm40.md
deleted file mode 100644
index aca66f0620..0000000000
--- a/mdop/agpm/request-control-of-an-uncontrolled-gpo-agpm40.md
+++ /dev/null
@@ -1,53 +0,0 @@
----
-title: Request Control of an Uncontrolled GPO
-description: Request Control of an Uncontrolled GPO
-author: dansimp
-ms.assetid: a34e0aeb-33a1-4c9f-b187-1d08493a785c
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Request Control of an Uncontrolled GPO
-
-
-To provide change control for an existing Group Policy Object (GPO), the GPO must be controlled. Unless you are an Approver or an AGPM Administrator (Full Control), you must request that the GPO be controlled.
-
-A user account with the Editor or Reviewer role or necessary permissions in Advanced Group Policy Management (AGPM) is required to complete this procedure. Review the details in "Additional considerations" in this topic.
-
-**To control an uncontrolled GPO**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. On the **Contents** tab in the details pane, click the **Uncontrolled** tab to display the uncontrolled GPOs.
-
-3. Right-click the GPO to be controlled with AGPM, and then click **Control**.
-
-4. Unless you have special permission to control GPOs, you must submit a request for control. To receive a copy of the request, type your e-mail address in the **Cc** field. Type a comment to be displayed in the **History** of the GPO, and then click **Submit**.
-
-5. When the **Progress** window indicates that overall progress is complete, click **Close**. The GPO is removed from the list on the **Uncontrolled** tab and added to the **Pending** tab. When an Approver has approved your request, the GPO will be moved to the **Controlled** tab.
-
-### Additional considerations
-
-- By default, you must be an Editor or a Reviewer to perform this procedure. Specifically, you must have **List Contents** and **Read Settings** permissions for the domain.
-
-- To withdraw your request before it has been approved, click the **Pending** tab. Right-click the GPO, and then click **Withdraw**. The GPO will be returned to the **Uncontrolled** tab.
-
-### Additional references
-
-- [Creating or Controlling a GPO](creating-or-controlling-a-gpo-agpm40-ed.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/request-deletion-of-a-gpo-agpm30ops.md b/mdop/agpm/request-deletion-of-a-gpo-agpm30ops.md
deleted file mode 100644
index 6ef7e4a702..0000000000
--- a/mdop/agpm/request-deletion-of-a-gpo-agpm30ops.md
+++ /dev/null
@@ -1,59 +0,0 @@
----
-title: Request Deletion of a GPO
-description: Request Deletion of a GPO
-author: dansimp
-ms.assetid: 576ece5c-dc6d-4b5e-8628-01c15ae2c9a8
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Request Deletion of a GPO
-
-
-Unless you are an Approver or an AGPM Administrator (Full Control), you must request the deletion of a Group Policy Object (GPO).
-
-A user account with the Editor role or necessary permissions in Advanced Group Policy Management (AGPM) is required to complete this procedure. Review the details in "Additional considerations" in this topic.
-
-**To request the deletion of a controlled GPO**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. On the **Contents** tab, click the **Controlled** tab to display the controlled GPOs.
-
-3. Right-click the GPO you want to delete, and then click **Delete**.
-
- - To delete the GPO from the archive while leaving the deployed version of the GPO untouched in the production environment, click **Delete GPO from archive only**.
-
- - To delete the GPO from both the archive and production environment, click **Delete GPO from archive and production**.
-
-4. Unless you have special permission to delete GPOs, you must submit a request for deletion of the deployed GPO. To receive a copy of the request, type your e-mail address in the **Cc** field. Type a comment to be displayed in the audit trail for the GPO, and then click **Submit**.
-
-5. When the **Progress** window indicates that overall progress is complete, click **Close**. The GPO is displayed on the list of GPOs on the **Pending** tab. When an Approver has approved your request, the GPO will be moved from the **Pending** tab to the **Recycle Bin** tab, where it can be restored or destroyed.
-
-### Additional considerations
-
-- By default, you must be an Editor to perform this procedure. Specifically, you must have **List Contents** and **Edit Settings** permissions for the GPO.
-
-- To withdraw your request before it has been approved, click the **Pending** tab. Right-click the GPO, and then click **Withdraw**. The GPO will be returned to the **Controlled** tab.
-
-- To delete an uncontrolled GPO from the production environment without first controlling it, in the **Group Policy Management Console**, click **Forest**, click **Domains**, click **<MyDomain>**, and then click **Group Policy Objects**. Right-click the uncontrolled GPO, and then click **Delete**.
-
-### Additional references
-
-- [Performing Editor Tasks](performing-editor-tasks-agpm30ops.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/request-deletion-of-a-gpo-agpm40.md b/mdop/agpm/request-deletion-of-a-gpo-agpm40.md
deleted file mode 100644
index 7d9ad25c8e..0000000000
--- a/mdop/agpm/request-deletion-of-a-gpo-agpm40.md
+++ /dev/null
@@ -1,59 +0,0 @@
----
-title: Request Deletion of a GPO
-description: Request Deletion of a GPO
-author: dansimp
-ms.assetid: 2410f7a1-ccca-44cf-ab26-76ad474409e7
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Request Deletion of a GPO
-
-
-Unless you are an Approver or an AGPM Administrator (Full Control), you must request the deletion of a Group Policy Object (GPO).
-
-A user account with the Editor role or necessary permissions in Advanced Group Policy Management (AGPM) is required to complete this procedure. Review the details in "Additional considerations" in this topic.
-
-**To request the deletion of a controlled GPO**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. On the **Contents** tab, click the **Controlled** tab to display the controlled GPOs.
-
-3. Right-click the GPO you want to delete, and then click **Delete**.
-
- - To delete the GPO from the archive while leaving the deployed version of the GPO untouched in the production environment, click **Delete GPO from archive only**.
-
- - To delete the GPO from both the archive and production environment of the domain, click **Delete GPO from archive and production**.
-
-4. Unless you have special permission to delete GPOs, you must submit a request for deletion of the deployed GPO. To receive a copy of the request, type your e-mail address in the **Cc** field. Type a comment to be displayed in the audit trail for the GPO, and then click **Submit**.
-
-5. When the **Progress** window indicates that overall progress is complete, click **Close**. The GPO is displayed on the list of GPOs on the **Pending** tab. When an Approver has approved your request, the GPO will be moved from the **Pending** tab to the **Recycle Bin** tab, where it can be restored or destroyed.
-
-### Additional considerations
-
-- By default, you must be an Editor to perform this procedure. Specifically, you must have **List Contents** and **Edit Settings** permissions for the GPO.
-
-- To withdraw your request before it has been approved, click the **Pending** tab. Right-click the GPO, and then click **Withdraw**. The GPO will be returned to the **Controlled** tab.
-
-- To delete an uncontrolled GPO from the production environment without first controlling it, in the **Group Policy Management Console**, click **Forest**, click **Domains**, click **<MyDomain>**, and then click **Group Policy Objects**. Right-click the uncontrolled GPO, and then click **Delete**.
-
-### Additional references
-
-- [Deleting or Restoring a GPO](deleting-or-restoring-a-gpo-agpm40.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/request-deployment-of-a-gpo-agpm30ops.md b/mdop/agpm/request-deployment-of-a-gpo-agpm30ops.md
deleted file mode 100644
index 7179891f76..0000000000
--- a/mdop/agpm/request-deployment-of-a-gpo-agpm30ops.md
+++ /dev/null
@@ -1,53 +0,0 @@
----
-title: Request Deployment of a GPO
-description: Request Deployment of a GPO
-author: dansimp
-ms.assetid: f44ae0fb-bcf7-477b-b99e-9dd6a55ee597
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Request Deployment of a GPO
-
-
-After you have modified and checked in a Group Policy Object (GPO), deploy the GPO, so it will take effect in the production environment.
-
-A user account with the Editor role or necessary permissions in Advanced Group Policy Management (AGPM) is required to complete this procedure. Review the details in "Additional considerations" in this topic.
-
-**To request the deployment of a GPO to the production environment**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. On the **Contents** tab, click the **Controlled** tab to display the controlled GPOs.
-
-3. Right-click the GPO to be deployed, and then click **Deploy**.
-
-4. Unless you are an Approver or AGPM Administrator or have special permission to deploy GPOs, you must submit a request for deployment. To receive a copy of the request, type your e-mail address in the **Cc** field. Type a comment to be displayed in the **History** for the GPO, and then click **Submit**.
-
-5. When the **Progress** window indicates that overall progress is complete, click **Close**. The GPO is displayed on the list of GPOs on the **Pending** tab. When an Approver has approved your request, the GPO will be moved from the **Pending** tab to the **Controlled** tab and be deployed.
-
-### Additional considerations
-
-- By default, you must be an Editor to perform this procedure. Specifically, you must have **List Contents** and **Edit Settings** permissions for the GPO.
-
-- To withdraw your request before it has been approved, click the **Pending** tab. Right-click the GPO, and then click **Withdraw**. The GPO will be returned to the **Controlled** tab.
-
-### Additional references
-
-- [Editing a GPO](editing-a-gpo-agpm30ops.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/request-deployment-of-a-gpo-agpm40.md b/mdop/agpm/request-deployment-of-a-gpo-agpm40.md
deleted file mode 100644
index 11a8af4db4..0000000000
--- a/mdop/agpm/request-deployment-of-a-gpo-agpm40.md
+++ /dev/null
@@ -1,53 +0,0 @@
----
-title: Request Deployment of a GPO
-description: Request Deployment of a GPO
-author: dansimp
-ms.assetid: 5783cfd0-bd93-46b4-8fa0-684bd39aa8fc
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Request Deployment of a GPO
-
-
-After you have modified and checked in a Group Policy Object (GPO), deploy the GPO, so it will take effect in the production environment.
-
-A user account with the Editor role or necessary permissions in Advanced Group Policy Management (AGPM) is required to complete this procedure. Review the details in "Additional considerations" in this topic.
-
-**To request the deployment of a GPO to the production environment of the domain**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. On the **Contents** tab, click the **Controlled** tab to display the controlled GPOs.
-
-3. Right-click the GPO to be deployed, and then click **Deploy**.
-
-4. Unless you are an Approver or AGPM Administrator or have special permission to deploy GPOs, you must submit a request for deployment. To receive a copy of the request, type your e-mail address in the **Cc** field. Type a comment to be displayed in the **History** for the GPO, and then click **Submit**.
-
-5. When the **Progress** window indicates that overall progress is complete, click **Close**. The GPO is displayed on the list of GPOs on the **Pending** tab. When an Approver has approved your request, the GPO will be moved from the **Pending** tab to the **Controlled** tab and be deployed.
-
-### Additional considerations
-
-- By default, you must be an Editor to perform this procedure. Specifically, you must have **List Contents** and **Edit Settings** permissions for the GPO.
-
-- To withdraw your request before it has been approved, click the **Pending** tab. Right-click the GPO, and then click **Withdraw**. The GPO will be returned to the **Controlled** tab.
-
-### Additional references
-
-- [Performing Editor Tasks](performing-editor-tasks-agpm40.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/request-deployment-of-a-gpo.md b/mdop/agpm/request-deployment-of-a-gpo.md
deleted file mode 100644
index 6c6043c1c1..0000000000
--- a/mdop/agpm/request-deployment-of-a-gpo.md
+++ /dev/null
@@ -1,53 +0,0 @@
----
-title: Request Deployment of a GPO
-description: Request Deployment of a GPO
-author: dansimp
-ms.assetid: 9aa9af29-4754-4f72-b624-bb3e1087cbe1
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Request Deployment of a GPO
-
-
-After you have modified and checked in a Group Policy object (GPO), deploy the GPO, so it will take effect in the production environment.
-
-A user account with the Editor role or necessary permissions in Advanced Group Policy Management is required to complete this procedure. Review the details in "Additional considerations" in this topic.
-
-**To request the deployment of a GPO to the production environment**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. On the **Contents** tab in the details pane, click the **Controlled** tab to display the controlled GPOs.
-
-3. Right-click the GPO to be deployed, and then click **Deploy**.
-
-4. Unless you are an Approver or AGPM Administrator or have special permission to deploy GPOs, you must submit a request for deployment. To receive a copy of the request, type your e-mail address in the **Cc** field. Type a comment to be displayed in the **History** for the GPO, and then click **Submit**.
-
-5. When the **Progress** window indicates that overall progress is complete, click **Close**. The GPO is displayed on the list of GPOs on the **Pending** tab. When an Approver has approved your request, the GPO will be moved from the **Pending** tab to the **Controlled** tab and be deployed.
-
-### Additional considerations
-
-- By default, you must be an Editor to perform this procedure. Specifically, you must have **List Contents** and **Edit Settings** permissions for the GPO.
-
-- To withdraw your request before it has been approved, click the **Pending** tab. Right-click the GPO, and then click **Withdraw**. The GPO will be returned to the **Controlled** tab.
-
-### Additional references
-
-- [Editing a GPO](editing-a-gpo.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/request-restoration-of-a-deleted-gpo-agpm30ops.md b/mdop/agpm/request-restoration-of-a-deleted-gpo-agpm30ops.md
deleted file mode 100644
index 0b1f4ef213..0000000000
--- a/mdop/agpm/request-restoration-of-a-deleted-gpo-agpm30ops.md
+++ /dev/null
@@ -1,58 +0,0 @@
----
-title: Request Restoration of a Deleted GPO
-description: Request Restoration of a Deleted GPO
-author: dansimp
-ms.assetid: dcc3baea-8af7-4886-a301-98b6ac5819cd
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Request Restoration of a Deleted GPO
-
-
-Unless you are an Approver or an AGPM Administrator (Full Control), you must request the restoration of a deleted Group Policy Object (GPO) from the Recycle Bin to return it to the archive.
-
-A user account with the Editor role or necessary permissions in Advanced Group Policy Management (AGPM) is required to complete this procedure. Review the details in "Additional considerations" in this topic.
-
-**To request the restoration of a deleted GPO**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. On the **Contents** tab, click the **Recycle Bin** tab to display the deleted GPOs.
-
-3. Right-click the GPO you want to restore, and then click **Restore**.
-
-4. Unless you have special permission to restore GPOs, you must submit a request for restoration of the deleted GPO. To receive a copy of the request, type your e-mail address in the **Cc** field. Type a comment to be displayed in the audit trail for the GPO, and then click **Submit**.
-
-5. When the **Progress** window indicates that overall progress is complete, click **Close**. The GPO is removed from the **Recycle Bin** tab and is displayed on the **Controlled** tab.
-
-**Note**
-If a GPO was deleted from the production environment, restoring it to the archive will not automatically redeploy it to the production environment. To return the GPO to the production environment, deploy the GPO. For information, see [Deploy a GPO](deploy-a-gpo-agpm30ops.md).
-
-
-
-### Additional considerations
-
-- By default, you must be an Editor to perform this procedure. Specifically, you must have **List Contents** and **Edit Settings** permission for the GPO.
-
-- To withdraw your request before it has been approved, click the **Pending** tab. Right-click the GPO, and then click **Withdraw**. The GPO will be returned to the **Recycle Bin** tab.
-
-### Additional references
-
-- [Deleting, Restoring, or Destroying a GPO](deleting-restoring-or-destroying-a-gpo-agpm30ops.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/request-restoration-of-a-deleted-gpo-agpm40.md b/mdop/agpm/request-restoration-of-a-deleted-gpo-agpm40.md
deleted file mode 100644
index 2ce8f77638..0000000000
--- a/mdop/agpm/request-restoration-of-a-deleted-gpo-agpm40.md
+++ /dev/null
@@ -1,58 +0,0 @@
----
-title: Request Restoration of a Deleted GPO
-description: Request Restoration of a Deleted GPO
-author: dansimp
-ms.assetid: bac5ca3b-be47-49b5-bf1b-96280625fda8
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Request Restoration of a Deleted GPO
-
-
-Unless you are an Approver or an AGPM Administrator (Full Control), you must request the restoration of a deleted Group Policy Object (GPO) from the Recycle Bin to return it to the archive.
-
-A user account with the Editor role or necessary permissions in Advanced Group Policy Management (AGPM) is required to complete this procedure. Review the details in "Additional considerations" in this topic.
-
-**To request the restoration of a deleted GPO**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. On the **Contents** tab, click the **Recycle Bin** tab to display the deleted GPOs.
-
-3. Right-click the GPO you want to restore, and then click **Restore**.
-
-4. Unless you have special permission to restore GPOs, you must submit a request for restoration of the deleted GPO. To receive a copy of the request, type your e-mail address in the **Cc** field. Type a comment to be displayed in the audit trail for the GPO, and then click **Submit**.
-
-5. When the **Progress** window indicates that overall progress is complete, click **Close**. The GPO is removed from the **Recycle Bin** tab and is displayed on the **Controlled** tab.
-
-**Note**
-If a GPO was deleted from the production environment, restoring it to the archive will not automatically redeploy it to the production environment. To return the GPO to the production environment, deploy the GPO. For information, see [Request Deployment of a GPO](request-deployment-of-a-gpo-agpm40.md).
-
-
-
-### Additional considerations
-
-- By default, you must be an Editor to perform this procedure. Specifically, you must have **List Contents** and **Edit Settings** permission for the GPO.
-
-- To withdraw your request before it has been approved, click the **Pending** tab. Right-click the GPO, and then click **Withdraw**. The GPO will be returned to the **Recycle Bin** tab.
-
-### Additional references
-
-- [Deleting or Restoring a GPO](deleting-or-restoring-a-gpo-agpm40.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/request-the-creation-of-a-new-controlled-gpo-agpm30ops.md b/mdop/agpm/request-the-creation-of-a-new-controlled-gpo-agpm30ops.md
deleted file mode 100644
index 7a8c1a3ab6..0000000000
--- a/mdop/agpm/request-the-creation-of-a-new-controlled-gpo-agpm30ops.md
+++ /dev/null
@@ -1,63 +0,0 @@
----
-title: Request the Creation of a New Controlled GPO
-description: Request the Creation of a New Controlled GPO
-author: dansimp
-ms.assetid: 4194c2f3-8116-4a35-be1a-81c84072daec
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Request the Creation of a New Controlled GPO
-
-
-Unless you are an Approver or an AGPM Administrator (Full Control), you must request the creation of a new Group Policy Object (GPO).
-
-A user account with the Editor or Reviewer role or necessary permissions in Advanced Group Policy Management (AGPM) is required to complete this procedure. Review the details in "Additional considerations" in this topic.
-
-**To create a new GPO with change control managed through AGPM**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. Right-click **Change Control**, and then click **New Controlled GPO**.
-
-3. Unless you have special permission to create GPOs, you must submit a request for creation. In the **New Controlled GPO** dialog box:
-
- 1. To receive a copy of the request, enter your e-mail address in the **Cc** field.
-
- 2. Type a name for the new GPO.
-
- 3. Optional: Type a comment for the new GPO.
-
- 4. To deploy the new GPO to the production environment immediately upon approval, click **Create live**. To create the new GPO offline without immediately deploying it upon approval, click **Create offline**.
-
- 5. Select the GPO template to use as a starting point for the new GPO.
-
- 6. Click **Submit**.
-
-4. When the **Progress** window indicates that overall progress is complete, click **Close**. The new GPO is displayed in the list of GPOs on the **Pending** tab. When an Approver has approved your request, the GPO will be moved to the **Controlled** tab.
-
-### Additional considerations
-
-- By default, you must be an Editor or a Reviewer to perform this procedure. Specifically, you must have **List Contents** permission for the domain.
-
-- To withdraw your request before it has been approved, click the **Pending** tab. Right-click the GPO, then click **Withdraw**. The GPO will be destroyed.
-
-### Additional references
-
-- [Creating, Controlling, or Importing a GPO](creating-controlling-or-importing-a-gpo-agpm30ops.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/request-the-creation-of-a-new-controlled-gpo-agpm40.md b/mdop/agpm/request-the-creation-of-a-new-controlled-gpo-agpm40.md
deleted file mode 100644
index bee0c5410d..0000000000
--- a/mdop/agpm/request-the-creation-of-a-new-controlled-gpo-agpm40.md
+++ /dev/null
@@ -1,63 +0,0 @@
----
-title: Request the Creation of a New Controlled GPO
-description: Request the Creation of a New Controlled GPO
-author: dansimp
-ms.assetid: cb265238-386f-4780-a59a-0c9a4a87d736
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Request the Creation of a New Controlled GPO
-
-
-Unless you are an Approver or an AGPM Administrator (Full Control), you must request the creation of a new Group Policy Object (GPO).
-
-A user account with the Editor or Reviewer role or necessary permissions in Advanced Group Policy Management (AGPM) is required to complete this procedure. Review the details in "Additional considerations" in this topic.
-
-**To create a new GPO with change control managed through AGPM**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. Right-click **Change Control**, and then click **New Controlled GPO**.
-
-3. Unless you have special permission to create GPOs, you must submit a request for creation. In the **New Controlled GPO** dialog box:
-
- 1. To receive a copy of the request, enter your e-mail address in the **Cc** field.
-
- 2. Type a name for the new GPO.
-
- 3. Optional: Type a comment for the new GPO.
-
- 4. To deploy the new GPO to the production environment of the domain immediately upon approval, click **Create live**. To create the new GPO offline without immediately deploying it upon approval, click **Create offline**.
-
- 5. Select the GPO template to use as a starting point for the new GPO.
-
- 6. Click **Submit**.
-
-4. When the **Progress** window indicates that overall progress is complete, click **Close**. The new GPO is displayed in the list of GPOs on the **Pending** tab. When an Approver has approved your request, the GPO will be moved to the **Controlled** tab.
-
-### Additional considerations
-
-- By default, you must be an Editor or a Reviewer to perform this procedure. Specifically, you must have **List Contents** permission for the domain.
-
-- To withdraw your request before it has been approved, click the **Pending** tab. Right-click the GPO, then click **Withdraw**. The GPO will be destroyed.
-
-### Additional references
-
-- [Creating or Controlling a GPO](creating-or-controlling-a-gpo-agpm40-ed.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/request-the-creation-of-a-new-controlled-gpo.md b/mdop/agpm/request-the-creation-of-a-new-controlled-gpo.md
deleted file mode 100644
index d7c1fe6de4..0000000000
--- a/mdop/agpm/request-the-creation-of-a-new-controlled-gpo.md
+++ /dev/null
@@ -1,63 +0,0 @@
----
-title: Request the Creation of a New Controlled GPO
-description: Request the Creation of a New Controlled GPO
-author: dansimp
-ms.assetid: e1875d81-8553-42ee-8f3a-023d6ced86ca
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Request the Creation of a New Controlled GPO
-
-
-Unless you are an Approver or an AGPM Administrator (Full Control), you must request the creation of a new Group Policy object (GPO) if it is to be managed using Advanced Group Policy Management (AGPM).
-
-A user account with the Editor or Reviewer role or necessary permissions in Advanced Group Policy Management is required to complete this procedure. Review the details in "Additional considerations" in this topic.
-
-**To create a new GPO with change control managed through AGPM**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. Right-click the **Change Control** node, and then click **New Controlled GPO**.
-
-3. Unless you have special permission to create GPOs, you must submit a request for creation. In the **New Controlled GPO** dialog box:
-
- 1. To receive a copy of the request, enter your e-mail address in the **Cc** field.
-
- 2. Type a name for the new GPO.
-
- 3. Optional: Type a comment for the new GPO.
-
- 4. To deploy the new GPO to the production environment immediately upon approval, click **Create live**. To create the new GPO offline without immediately deploying it upon approval, click **Create offline**.
-
- 5. Select the GPO template to use as a starting point for the new GPO.
-
- 6. Click **Submit**.
-
-4. When the **Progress** window indicates that overall progress is complete, click **Close**. The new GPO is displayed in the list of GPOs on the **Pending** tab. When an Approver has approved your request, the GPO will be moved to the **Controlled** tab.
-
-### Additional considerations
-
-- By default, you must be an Editor or a Reviewer to perform this procedure. Specifically, you must have **List Contents** permission for the domain.
-
-- To withdraw your request before it has been approved, click the **Pending** tab. Right-click the GPO, then click **Withdraw**. The GPO will be destroyed.
-
-### Additional references
-
-- [Creating, Controlling, or Importing a GPO](creating-controlling-or-importing-a-gpo-editor.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/resources-for-agpm.md b/mdop/agpm/resources-for-agpm.md
deleted file mode 100644
index 5aa2774df3..0000000000
--- a/mdop/agpm/resources-for-agpm.md
+++ /dev/null
@@ -1,45 +0,0 @@
----
-title: Resources for AGPM
-description: Resources for AGPM
-author: dansimp
-ms.assetid: b44b58c0-2810-40d6-9677-f2f64e1add75
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 08/30/2016
----
-
-
-# Resources for AGPM
-
-
-### Documents for download
-
-- [Advanced Group Policy Management 4.0 documents](https://www.microsoft.com/download/details.aspx?id=13975)
-
-### Microsoft Desktop Optimization Pack resources
-
-- [Microsoft Desktop Optimization Pack (MDOP) for Software Assurance TechCenter](https://go.microsoft.com/fwlink/?LinkID=159870) (https://www.microsoft.com/technet/mdop): Links to MDOP videos and resources.
-
-- [Enterprise products: MDOP](https://go.microsoft.com/fwlink/?LinkID=160297): Overviews and information about the benefits of applications in MDOP.
-
-### Group Policy resources
-
-- [Group Policy TechCenter](https://go.microsoft.com/fwlink/?LinkID=145531) (https://www.microsoft.com/grouppolicy): Links to Group Policy documentation, tools, and downloads.
-
-- [Group Policy Team Blog](https://go.microsoft.com/fwlink/?LinkID=75192) (https://blogs.technet.com/GroupPolicy): Stay current on the latest news about Group Policy with articles by the Group Policy Team and other experts.
-
-- [Group Policy Forum](https://go.microsoft.com/fwlink/?LinkID=145532): Do you have questions about Group Policy or AGPM? You can post your questions to the forum, and receive answers from the experts.
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/restore-a-deleted-gpo-agpm30ops.md b/mdop/agpm/restore-a-deleted-gpo-agpm30ops.md
deleted file mode 100644
index 37a1bcf1c0..0000000000
--- a/mdop/agpm/restore-a-deleted-gpo-agpm30ops.md
+++ /dev/null
@@ -1,56 +0,0 @@
----
-title: Restore a Deleted GPO
-description: Restore a Deleted GPO
-author: dansimp
-ms.assetid: 853feb0a-d2d9-4be9-a07e-e113a56a9968
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Restore a Deleted GPO
-
-
-Approvers can restore a deleted Group Policy Object (GPO) from the Recycle Bin, returning it to the archive.
-
-A user account with the Approver or AGPM Administrator (Full Control) role or necessary permissions in Advanced Group Policy Management (AGPM) is required to complete this procedure. Review the details in "Additional considerations" in this topic.
-
-**To restore a deleted GPO**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. On the **Contents** tab, click the **Recycle Bin** tab to display the deleted GPOs.
-
-3. Right-click the GPO to restore, and then click **Restore**.
-
-4. Type a comment to be displayed in the history of the GPO, and then click **OK**.
-
-5. When the **Progress** window indicates that overall progress is complete, click **Close**. The GPO is removed from the **Recycle Bin** tab and is displayed on the **Controlled** tab.
-
-**Note**
-If a GPO was deleted from the production environment, restoring it to the archive will not automatically redeploy it to the production environment. To return the GPO to the production environment, deploy the GPO. For information, see [Deploy a GPO](deploy-a-gpo-agpm30ops.md).
-
-
-
-### Additional considerations
-
-- By default, you must be an Approver or an AGPM Administrator (Full Control) to perform this procedure. Specifically, you must have **List Contents** and either **Deploy GPO** or **Delete GPO** permissions for the GPO.
-
-### Additional references
-
-- [Deleting, Restoring, or Destroying a GPO](deleting-restoring-or-destroying-a-gpo-agpm30ops.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/restore-a-deleted-gpo-agpm40.md b/mdop/agpm/restore-a-deleted-gpo-agpm40.md
deleted file mode 100644
index 173a4d8932..0000000000
--- a/mdop/agpm/restore-a-deleted-gpo-agpm40.md
+++ /dev/null
@@ -1,56 +0,0 @@
----
-title: Restore a Deleted GPO
-description: Restore a Deleted GPO
-author: dansimp
-ms.assetid: 0a131d26-a741-4a51-b612-c0bc7dbba06b
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Restore a Deleted GPO
-
-
-Approvers can restore a deleted Group Policy Object (GPO) from the Recycle Bin, returning it to the archive.
-
-A user account with the Approver or AGPM Administrator (Full Control) role or necessary permissions in Advanced Group Policy Management (AGPM) is required to complete this procedure. Review the details in "Additional considerations" in this topic.
-
-**To restore a deleted GPO**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. On the **Contents** tab, click the **Recycle Bin** tab to display the deleted GPOs.
-
-3. Right-click the GPO to restore, and then click **Restore**.
-
-4. Type a comment to be displayed in the history of the GPO, and then click **OK**.
-
-5. When the **Progress** window indicates that overall progress is complete, click **Close**. The GPO is removed from the **Recycle Bin** tab and is displayed on the **Controlled** tab.
-
-**Note**
-If a GPO was deleted from the production environment, restoring it to the archive will not automatically redeploy it to the production environment. To return the GPO to the production environment, deploy the GPO. For information, see [Deploy a GPO](deploy-a-gpo-agpm40.md).
-
-
-
-### Additional considerations
-
-- By default, you must be an Approver or an AGPM Administrator (Full Control) to perform this procedure. Specifically, you must have **List Contents** and either **Deploy GPO** or **Delete GPO** permissions for the GPO.
-
-### Additional references
-
-- [Deleting, Restoring, or Destroying a GPO](deleting-restoring-or-destroying-a-gpo-agpm40.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/restore-a-deleted-gpo.md b/mdop/agpm/restore-a-deleted-gpo.md
deleted file mode 100644
index a70c7bb3ae..0000000000
--- a/mdop/agpm/restore-a-deleted-gpo.md
+++ /dev/null
@@ -1,56 +0,0 @@
----
-title: Restore a Deleted GPO
-description: Restore a Deleted GPO
-author: dansimp
-ms.assetid: e6953296-7b7d-4d1e-ad82-d4a23044cdd7
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Restore a Deleted GPO
-
-
-Advanced Group Policy Management (AGPM) enables Approvers to restore a deleted Group Policy object (GPO) from the Recycle Bin, returning it to the archive.
-
-A user account with the Editor, Approver, or AGPM Administrator (Full Control) role or necessary permissions in Advanced Group Policy Management is required to complete this procedure. Review the details in "Additional considerations" in this topic.
-
-**To restore a deleted GPO**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. On the **Contents** tab, click the **Recycle Bin** tab to display the deleted GPOs.
-
-3. Right-click the GPO to restore, and then click **Restore**.
-
-4. Type a comment to be displayed in the history of the GPO, and then click **OK**.
-
-5. When the **Progress** window indicates that overall progress is complete, click **Close**. The GPO is removed from the **Recycle Bin** tab and is displayed on the **Controlled** tab.
-
-**Note**
-If a GPO was deleted from the production environment, restoring it to the archive will not automatically redeploy it to the production environment. To return the GPO to the production environment, deploy the GPO. For information, see [Deploy a GPO](deploy-a-gpo.md).
-
-
-
-### Additional considerations
-
-- By default, you must be an Editor, an Approver, or an AGPM Administrator (Full Control) to perform this procedure. Specifically, you must have **List Contents** and either **Edit Settings**, **Deploy GPO**, or **Delete GPO** permissions for the GPO.
-
-### Additional references
-
-- [Deleting, Restoring, or Destroying a GPO](deleting-restoring-or-destroying-a-gpo.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/restore-the-archive-from-a-backup-agpm40.md b/mdop/agpm/restore-the-archive-from-a-backup-agpm40.md
deleted file mode 100644
index 48e9b29395..0000000000
--- a/mdop/agpm/restore-the-archive-from-a-backup-agpm40.md
+++ /dev/null
@@ -1,53 +0,0 @@
----
-title: Restore the Archive from a Backup
-description: Restore the Archive from a Backup
-author: dansimp
-ms.assetid: b83f6173-a236-4da2-b16e-8df20920d4cc
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Restore the Archive from a Backup
-
-
-If a disaster occurs and the archive for Advanced Group Policy Management (AGPM) is damaged or destroyed, an AGPM Administrator (Full Control) can restore the archive from a backup copy prepared in advance and then import from the production environment of the domain any Group Policy Objects (GPOs) that are not in the archive or for which the version in production is more current than that in the archive. For information about how to restore an archive backup to a different server, see [Move the AGPM Server and the Archive](move-the-agpm-server-and-the-archive-agpm40.md).
-
-A user account that has access to the AGPM Server (the computer on which the AGPM Service is installed) and to the folder that contains the archive is required to complete this procedure.
-
-**To restore the archive from a backup**
-
-1. Stop the AGPM Service. For more information, see [Start and Stop the AGPM Service](start-and-stop-the-agpm-service-agpm40.md).
-
-2. Remove the existing archive. By default, the archive folder is %ProgramData%\\Microsoft\\AGPM, however the AGPM Administrator who installed Microsoft Advanced Group Policy Management - Server may have entered a different location during setup.
-
-3. Re-create the archive folder by configuring the archive path, AGPM Service Account, Archive Owner, and listening port. Using the same values as used during the original installation is not necessary. For more information, see [Modify the AGPM Service](modify-the-agpm-service-agpm40.md).
-
-4. Copy the contents of the archive backup to the archive folder, copying the subfolders and files to make sure that each subfolder and file inherits the permissions of the archive folder. Be careful not to overwrite the archive folder.
-
-5. If you not sure about whether a GPO in the archive backup is more current than the copy of that GPO in production, generate a difference report and compare their settings. For more information, see [Identify Differences Between GPOs, GPO Versions, or Templates](identify-differences-between-gpos-gpo-versions-or-templates-agpm40.md).
-
-6. Restart the AGPM Service. For more information, see [Start and Stop the AGPM Service](start-and-stop-the-agpm-service-agpm40.md).
-
-### Additional references
-
-- [Back Up the Archive](back-up-the-archive-agpm40.md)
-
-- [Move the AGPM Server and the Archive](move-the-agpm-server-and-the-archive-agpm40.md)
-
-- [Managing the Archive](managing-the-archive-agpm40.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/restore-the-archive-from-a-backup.md b/mdop/agpm/restore-the-archive-from-a-backup.md
deleted file mode 100644
index 14a140fd80..0000000000
--- a/mdop/agpm/restore-the-archive-from-a-backup.md
+++ /dev/null
@@ -1,53 +0,0 @@
----
-title: Restore the Archive from a Backup
-description: Restore the Archive from a Backup
-author: dansimp
-ms.assetid: 49666337-d72c-4e44-99e4-9eb59b2355a9
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Restore the Archive from a Backup
-
-
-If a disaster occurs and the archive for Advanced Group Policy Management (AGPM) is damaged or destroyed, an AGPM Administrator (Full Control) can restore the archive from a backup copy prepared in advance and then import from the production environment any Group Policy Objects (GPOs) that are not in the archive or for which the version in production is more current than that in the archive. For information about how to restore an archive backup to a different server, see [Move the AGPM Server and the Archive](move-the-agpm-server-and-the-archive.md).
-
-A user account that has access to the AGPM Server (the computer on which the AGPM Service is installed) and to the folder that contains the archive is required to complete this procedure.
-
-**To restore the archive from a backup**
-
-1. Stop the AGPM Service. For more information, see [Start and Stop the AGPM Service](start-and-stop-the-agpm-service-agpm30ops.md).
-
-2. Remove the existing archive. By default, the archive folder is %ProgramData%\\Microsoft\\AGPM, however the AGPM Administrator who installed Microsoft Advanced Group Policy Management - Server may have entered a different location during setup.
-
-3. Re-create the archive folder by configuring the archive path, AGPM Service Account, Archive Owner, and listening port. Using the same values as used during the original installation is not necessary. For more information, see [Modify the AGPM Service](modify-the-agpm-service-agpm30ops.md).
-
-4. Copy the contents of the archive backup to the archive folder, copying the subfolders and files to make sure that each subfolder and file inherits the permissions of the archive folder. Be careful not to overwrite the archive folder.
-
-5. If you not sure about whether a GPO in the archive backup is more current than the copy of that GPO in production, generate a difference report and compare their settings. For more information, see [Identify Differences Between GPOs, GPO Versions, or Templates](identify-differences-between-gpos-gpo-versions-or-templates-agpm30ops.md).
-
-6. Restart the AGPM Service. For more information, see [Start and Stop the AGPM Service](start-and-stop-the-agpm-service-agpm30ops.md).
-
-### Additional references
-
-- [Back Up the Archive](back-up-the-archive.md)
-
-- [Move the AGPM Server and the Archive](move-the-agpm-server-and-the-archive.md)
-
-- [Managing the Archive](managing-the-archive.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/review-gpo-links-agpm30ops.md b/mdop/agpm/review-gpo-links-agpm30ops.md
deleted file mode 100644
index 344d2114e2..0000000000
--- a/mdop/agpm/review-gpo-links-agpm30ops.md
+++ /dev/null
@@ -1,68 +0,0 @@
----
-title: Review GPO Links
-description: Review GPO Links
-author: dansimp
-ms.assetid: 5ae95afc-2b89-45cf-916c-efe2d43b2211
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Review GPO Links
-
-
-You can display a diagram showing where a Group Policy Object (GPO) or GPOs that you select are linked to organizational units. GPO link diagrams are updated each time the GPO is controlled, imported, or checked in.
-
-A user account with the Reviewer, Editor, Approver, or AGPM Administrator (Full Control) role or necessary permissions in Advanced Group Policy Management (AGPM) is required to complete this procedure. Review the details in "Additional considerations" in this topic.
-
-## Reviewing GPO links
-
-
-- [For one or more GPOs](#bkmk-gpos)
-
-- [For one or more versions of a GPO](#bkmk-gpo-versions)
-
-###
-
-**To display GPO links for one or more GPOs**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. On the **Contents** tab in the details pane, click the **Controlled**, **Pending**, or **Recycle Bin** tab to display GPOs.
-
-3. Select one or more GPOs for which to display links, right-click a selected GPO, click **Settings**, and then click **GPO Links** to display a diagram of domains and organizational units with links to the selected GPO(s).
-
-###
-
-**To display GPO links for one or more versions of a GPO**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. On the **Contents** tab in the details pane, click the **Controlled** or **Recycle Bin** tab to display GPOs.
-
-3. Double-click the GPO to display its history.
-
-4. Right-click the GPO version for which to review the settings, click **Settings**, and then click **HTML Report** or **XML Report** to display a summary of the GPO's settings.
-
-### Additional considerations
-
-- By default, you must be a Reviewer, an Editor, an Approver, or an AGPM Administrator (Full Control) to perform this procedure. Specifically, you must have **List Contents** and **Read Settings** permissions for the GPO. Also, to display the list of GPOs, you must have **List Contents** permission for the domain.
-
-### Additional references
-
-- [Performing Reviewer Tasks](performing-reviewer-tasks-agpm30ops.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/review-gpo-links-agpm40.md b/mdop/agpm/review-gpo-links-agpm40.md
deleted file mode 100644
index 0aa1c8288a..0000000000
--- a/mdop/agpm/review-gpo-links-agpm40.md
+++ /dev/null
@@ -1,68 +0,0 @@
----
-title: Review GPO Links
-description: Review GPO Links
-author: dansimp
-ms.assetid: 3aaba9da-f0aa-466f-bd1c-49f11d00ea54
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Review GPO Links
-
-
-You can display a diagram showing where a Group Policy Object (GPO) or GPOs that you select are linked to organizational units. GPO link diagrams are updated each time the GPO is controlled, imported, or checked in.
-
-A user account with the Reviewer, Editor, Approver, or AGPM Administrator (Full Control) role or necessary permissions in Advanced Group Policy Management (AGPM) is required to complete this procedure. Review the details in "Additional considerations" in this topic.
-
-## Reviewing GPO links
-
-
-- [For one or more GPOs](#bkmk-gpos)
-
-- [For one or more versions of a GPO](#bkmk-gpo-versions)
-
-###
-
-**To display GPO links for one or more GPOs**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. On the **Contents** tab in the details pane, click the **Controlled**, **Pending**, or **Recycle Bin** tab to display GPOs.
-
-3. Select one or more GPOs for which to display links, right-click a selected GPO, click **Settings**, and then click **GPO Links** to display a diagram of domains and organizational units with links to the selected GPO(s).
-
-###
-
-**To display GPO links for one or more versions of a GPO**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. On the **Contents** tab in the details pane, click the **Controlled** or **Recycle Bin** tab to display GPOs.
-
-3. Double-click the GPO to display its history.
-
-4. Right-click the GPO version for which to review the settings, click **Settings**, and then click **HTML Report** or **XML Report** to display a summary of the GPO's settings.
-
-### Additional considerations
-
-- By default, you must be a Reviewer, an Editor, an Approver, or an AGPM Administrator (Full Control) to perform this procedure. Specifically, you must have **List Contents** and **Read Settings** permissions for the GPO. Also, to display the list of GPOs, you must have **List Contents** permission for the domain.
-
-### Additional references
-
-- [Performing Reviewer Tasks](performing-reviewer-tasks-agpm40.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/review-gpo-links.md b/mdop/agpm/review-gpo-links.md
deleted file mode 100644
index 5df2d37d92..0000000000
--- a/mdop/agpm/review-gpo-links.md
+++ /dev/null
@@ -1,68 +0,0 @@
----
-title: Review GPO Links
-description: Review GPO Links
-author: dansimp
-ms.assetid: 3c472448-f16a-493c-a229-5ca60a470965
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Review GPO Links
-
-
-You can display a diagram showing where a Group Policy object (GPO) or GPOs that you select are linked to organizational units. GPO link diagrams are updated each time the GPO is controlled, imported, or checked in.
-
-A user account with the Reviewer, Editor, Approver, or AGPM Administrator (Full Control) role or necessary permissions in Advanced Group Policy Management is required to complete this procedure. Review the details in "Additional considerations" in this topic.
-
-## Reviewing GPO links
-
-
-- [For one or more GPOs](#bkmk-gpos)
-
-- [For one or more versions of a GPO](#bkmk-gpo-versions)
-
-###
-
-**To display GPO links for one or more GPOs**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. On the **Contents** tab in the details pane, click the **Controlled**, **Pending**, or **Recycle Bin** tab to display GPOs.
-
-3. Select one or more GPOs for which to display links, right-click a selected GPO, click **Settings**, and then click **GPO Links** to display a diagram of domains and organizational units with links to the selected GPO(s).
-
-###
-
-**To display GPO links for one or more versions of a GPO**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. On the **Contents** tab in the details pane, click the **Controlled** or **Recycle Bin** tab to display GPOs.
-
-3. Double-click the GPO to display its history.
-
-4. Right-click the GPO version for which to review the settings, click **Settings**, and then click **HTML Report** or **XML Report** to display a summary of the GPO's settings.
-
-### Additional considerations
-
-- By default, you must be a Reviewer, an Editor, an Approver, or an AGPM Administrator (Full Control) to perform this procedure. Specifically, you must have **List Contents** and **Read Settings** permissions for the GPO. Also, to display the list of GPOs, you must have **List Contents** permission for the domain.
-
-### Additional references
-
-- [Performing Reviewer Tasks](performing-reviewer-tasks.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/review-gpo-settings-agpm30ops.md b/mdop/agpm/review-gpo-settings-agpm30ops.md
deleted file mode 100644
index e8287b80ff..0000000000
--- a/mdop/agpm/review-gpo-settings-agpm30ops.md
+++ /dev/null
@@ -1,49 +0,0 @@
----
-title: Review GPO Settings
-description: Review GPO Settings
-author: dansimp
-ms.assetid: bed956d0-082e-4fa9-bf1e-572d0d3d02ec
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Review GPO Settings
-
-
-You can generate HTML-based and XML-based reports for reviewing settings within any version of a Group Policy Object (GPO).
-
-A user account with the Reviewer, Editor, Approver, or AGPM Administrator (Full Control) role or necessary permissions in Advanced Group Policy Management (AGPM) is required to complete this procedure. Review the details in "Additional considerations" in this topic.
-
-**To review settings in any version of a GPO**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. On the **Contents** tab in the details pane, click a tab to display GPOs.
-
-3. Double-click the GPO to display its history.
-
-4. Right-click the GPO version for which to review the settings, click **Settings**, and then click **HTML Report** or **XML Report** to display a summary of the GPO's settings.
-
-### Additional considerations
-
-- By default, you must be a Reviewer, an Editor, an Approver, or an AGPM Administrator (Full Control) to perform this procedure. Specifically, you must have **List Contents** and **Read Settings** permissions for the GPO. Also, to display the list of GPOs, you must have **List Contents** permission for the domain.
-
-### Additional references
-
-- [Performing Reviewer Tasks](performing-reviewer-tasks-agpm30ops.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/review-gpo-settings-agpm40.md b/mdop/agpm/review-gpo-settings-agpm40.md
deleted file mode 100644
index 86d54adf3c..0000000000
--- a/mdop/agpm/review-gpo-settings-agpm40.md
+++ /dev/null
@@ -1,49 +0,0 @@
----
-title: Review GPO Settings
-description: Review GPO Settings
-author: dansimp
-ms.assetid: c346bcde-dd6a-4775-aeab-721ca3a361b2
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Review GPO Settings
-
-
-You can generate HTML-based and XML-based reports for reviewing settings within any version of a Group Policy Object (GPO).
-
-A user account with the Reviewer, Editor, Approver, or AGPM Administrator (Full Control) role or necessary permissions in Advanced Group Policy Management (AGPM) is required to complete this procedure. Review the details in "Additional considerations" in this topic.
-
-**To review settings in any version of a GPO**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. On the **Contents** tab in the details pane, click a tab to display GPOs.
-
-3. Double-click the GPO to display its history.
-
-4. Right-click the GPO version for which to review the settings, click **Settings**, and then click **HTML Report** or **XML Report** to display a summary of the GPO's settings.
-
-### Additional considerations
-
-- By default, you must be a Reviewer, an Editor, an Approver, or an AGPM Administrator (Full Control) to perform this procedure. Specifically, you must have **List Contents** and **Read Settings** permissions for the GPO. Also, to display the list of GPOs, you must have **List Contents** permission for the domain.
-
-### Additional references
-
-- [Performing Reviewer Tasks](performing-reviewer-tasks-agpm40.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/review-gpo-settings.md b/mdop/agpm/review-gpo-settings.md
deleted file mode 100644
index 31cdb5b678..0000000000
--- a/mdop/agpm/review-gpo-settings.md
+++ /dev/null
@@ -1,49 +0,0 @@
----
-title: Review GPO Settings
-description: Review GPO Settings
-author: dansimp
-ms.assetid: e82570b2-d8ce-4bf0-8ad7-8910409f3041
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Review GPO Settings
-
-
-You can generate HTML-based and XML-based reports for reviewing settings within any version of a Group Policy object (GPO).
-
-A user account with the Reviewer, Editor, Approver, or AGPM Administrator (Full Control) role or necessary permissions in Advanced Group Policy Management is required to complete this procedure. Review the details in "Additional considerations" in this topic.
-
-**To review settings in any version of a GPO**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. On the **Contents** tab in the details pane, click a tab to display GPOs.
-
-3. Double-click the GPO to display its history.
-
-4. Right-click the GPO version for which to review the settings, click **Settings**, and then click **HTML Report** or **XML Report** to display a summary of the GPO's settings.
-
-### Additional considerations
-
-- By default, you must be a Reviewer, an Editor, an Approver, or an AGPM Administrator (Full Control) to perform this procedure. Specifically, you must have **List Contents** and **Read Settings** permissions for the GPO. Also, to display the list of GPOs, you must have **List Contents** permission for the domain.
-
-### Additional references
-
-- [Performing Reviewer Tasks](performing-reviewer-tasks.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/roll-back-to-a-previous-version-of-a-gpo-agpm30ops.md b/mdop/agpm/roll-back-to-a-previous-version-of-a-gpo-agpm30ops.md
deleted file mode 100644
index 5317c7cad8..0000000000
--- a/mdop/agpm/roll-back-to-a-previous-version-of-a-gpo-agpm30ops.md
+++ /dev/null
@@ -1,56 +0,0 @@
----
-title: Roll Back to a Previous Version of a GPO
-description: Roll Back to a Previous Version of a GPO
-author: dansimp
-ms.assetid: 2a98ad8f-32cb-41eb-ab99-0318f2a55d81
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Roll Back to a Previous Version of a GPO
-
-
-An Approver can roll back changes to a Group Policy Object (GPO) by redeploying an earlier version of the GPO from its history. Deploying an earlier version of a GPO overwrites the version of the GPO currently in production.
-
-A user account with the Approver or AGPM Administrator (Full Control) role or necessary permissions in Advanced Group Policy Management (AGPM) is required to complete this procedure. Review the details in "Additional considerations" in this topic.
-
-**To deploy a previous version of a GPO to the production environment**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. On the **Contents** tab, click the **Controlled** tab to display the controlled GPOs.
-
-3. Double-click the GPO to be deployed to display its **History**.
-
-4. Right-click the version to be deployed, click **Deploy**, and then click **Yes**.
-
-5. When the **Progress** window indicates that overall progress is complete, click **Close**. In the **History** window, click **Close**.
-
-**Note**
-To verify that the version that has been redeployed matches the version intended, examine a difference report for the two versions. In the **History** window for the GPO, highlight the two versions, and then right-click and select **Difference** and either **HTML Report** or **XML Report**.
-
-
-
-### Additional considerations
-
-- By default, you must be an Approver or an AGPM Administrator (Full Control) to perform this procedure. Specifically, you must have **List Contents** and **Deploy GPO** permissions for the GPO.
-
-### Additional references
-
-- [Performing Approver Tasks](performing-approver-tasks-agpm30ops.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/roll-back-to-a-previous-version-of-a-gpo.md b/mdop/agpm/roll-back-to-a-previous-version-of-a-gpo.md
deleted file mode 100644
index 1f984420dd..0000000000
--- a/mdop/agpm/roll-back-to-a-previous-version-of-a-gpo.md
+++ /dev/null
@@ -1,56 +0,0 @@
----
-title: Roll Back to a Previous Version of a GPO
-description: Roll Back to a Previous Version of a GPO
-author: dansimp
-ms.assetid: 028631c0-4cb9-4642-90ad-04cd813051b7
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Roll Back to a Previous Version of a GPO
-
-
-Advanced Group Policy Management (AGPM) enables an Approver to roll back changes to a Group Policy object (GPO) by redeploying an earlier version of the GPO from its history. Deploying an earlier version of a GPO overwrites the version of the GPO currently in production.
-
-A user account with the Approver or AGPM Administrator (Full Control) role or necessary permissions in Advanced Group Policy Management is required to complete this procedure. Review the details in "Additional considerations" in this topic.
-
-**To deploy a previous version of a GPO to the production environment**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. On the **Contents** tab, click the **Controlled** tab to display the controlled GPOs.
-
-3. Double-click the GPO to be deployed to display its **History**.
-
-4. Right-click the version to be deployed, click **Deploy**, and then click **Yes**.
-
-5. When the **Progress** window indicates that overall progress is complete, click **Close**. In the **History** window, click **Close**.
-
-**Note**
-To verify that the version that has been redeployed matches the version intended, examine a difference report for the two versions. In the **History** window for the GPO, highlight the two versions, and then right-click and select **Difference** and either **HTML Report** or **XML Report**.
-
-
-
-### Additional considerations
-
-- By default, you must be an Approver or an AGPM Administrator (Full Control) to perform this procedure. Specifically, you must have **List Contents** and **Deploy GPO** permissions for the GPO.
-
-### Additional references
-
-- [Performing Approver Tasks](performing-approver-tasks.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/roll-back-to-an-earlier-version-of-a-gpo-agpm40.md b/mdop/agpm/roll-back-to-an-earlier-version-of-a-gpo-agpm40.md
deleted file mode 100644
index eda0e2c1fe..0000000000
--- a/mdop/agpm/roll-back-to-an-earlier-version-of-a-gpo-agpm40.md
+++ /dev/null
@@ -1,56 +0,0 @@
----
-title: Roll Back to an Earlier Version of a GPO
-description: Roll Back to an Earlier Version of a GPO
-author: dansimp
-ms.assetid: 06ce9251-95e0-46d0-99c2-b9a0690e5891
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Roll Back to an Earlier Version of a GPO
-
-
-An Approver can roll back changes to a Group Policy Object (GPO) by redeploying an earlier version of the GPO from its history. Deploying an earlier version of a GPO overwrites the version of the GPO currently in production.
-
-A user account with the Approver or AGPM Administrator (Full Control) role or necessary permissions in Advanced Group Policy Management (AGPM) is required to complete this procedure. Review the details in "Additional considerations" in this topic.
-
-**To deploy an earlier version of a GPO to the production environment of the domain**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. On the **Contents** tab, click the **Controlled** tab to display the controlled GPOs.
-
-3. Double-click the GPO to be deployed to display its **History**.
-
-4. Right-click the version to be deployed, click **Deploy**, and then click **Yes**.
-
-5. When the **Progress** window indicates that overall progress is complete, click **Close**. In the **History** window, click **Close**.
-
-**Note**
-To verify that the version that has been redeployed matches the version intended, examine a difference report for the two versions. In the **History** window for the GPO, highlight the two versions, and then right-click and select **Difference** and either **HTML Report** or **XML Report**.
-
-
-
-### Additional considerations
-
-- By default, you must be an Approver or an AGPM Administrator (Full Control) to perform this procedure. Specifically, you must have **List Contents** and **Deploy GPO** permissions for the GPO.
-
-### Additional references
-
-- [Performing Approver Tasks](performing-approver-tasks-agpm40.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/search-and-filter-the-list-of-gpos.md b/mdop/agpm/search-and-filter-the-list-of-gpos.md
deleted file mode 100644
index 0266fdfa89..0000000000
--- a/mdop/agpm/search-and-filter-the-list-of-gpos.md
+++ /dev/null
@@ -1,128 +0,0 @@
----
-title: Search and Filter the List of GPOs
-description: Search and Filter the List of GPOs
-author: dansimp
-ms.assetid: 1bc58a38-033c-4aed-9eb4-c239827f5501
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Search and Filter the List of GPOs
-
-
-In Advanced Group Policy Management (AGPM), you can search the list of Group Policy Objects (GPOs) and their attributes to filter the list of GPOs displayed. For example, you can search for GPOs with a particular name, state, or comment. You can also search for GPOs that were last changed by a particular Group Policy administrator or on a particular date.
-
-## Performing a complex search
-
-
-You can perform a complex search by using the format *GPO attribute 1: search string 1 GPO attribute 2: search string 2…all-column search strings*. The search is not case-sensitive.
-
-- **GPO attribute:** Any column heading in the list of GPOs in AGPM other than **Computer Version** or **User Version**. GPO attributes include the GPO name, state, user who most recently changed the GPO, date and time when the GPO was most recently changed, comment, GPO status, and WMI filter applied to the GPO.
-
-- **Search string:** Text for which to search in the specified column. If a string includes spaces, you must enclose the string with quotation marks.
-
-- **All-column search strings:** Text for which to search in all columns in the list of GPOs in AGPM other than **Computer Version** and **User Version**. You can include multiple strings separated by spaces. If a string includes spaces, you must enclose the string with quotation marks.
-
-Each GPO attribute and search string pair and each all-column search string are combined by using a logical AND operation. The result is a list of all GPOs for which each specified attribute includes the specified search string and for which any all-column search strings appear in at least one column. The search returns any partial matches for strings so that you can enter part of a GPO name or user name and view a list of all GPOs that include that text in their name.
-
-The following are examples of searches:
-
-
-
-
-
-
-
-
-
Description of search result
-
Search query
-
-
-
-
-
All GPOs with names that include the text security and North America.
-
name:securityname: "North America"
-
-
-
All checked out GPOs.
-
state: "checked out"
-
-
-
All GPOs most recently changed by the user named Administrator and most recently changed within the previous month.
-
changed by:Administratorchange date:lastmonth
-
-
-
All GPOs in which the word firewall is included in the most recent comment and in which the word security appears in any column.
-
comment:firewallsecurity
-
-
-
All GPOs that have a status of All Settings Disabled.
-
gpo status:all
-
-
-
All GPOs that have a WMI filter named My WMI Filter applied and that have a status of User Configuration Settings Disabled.
-
wmi filter: "My WMI Filter" gpo status:user
-
-
-
-
-
-
-## Specifying dates
-
-
-You can search for GPOs changed on a specific date, at a specific time, or during a span of time by using the same special terms available when you search in Windows. If entering a specific date or time, you must use the format that is used in the **Change Date** column. The following are examples of searches of the **Change Date** column:
-
-- **change date:** **10/10/2009**
-
-- **change date:** **10/10/2009 9:00:00 AM**
-
-- **change date:** **thisweek**
-
-You can use the following special terms, which are not case-sensitive, when you search the **Change Date** column:
-
-- **Today**
-
-- **Yesterday**
-
-- **ThisWeek**
-
-- **LastWeek**
-
-- **ThisMonth**
-
-- **LastMonth**
-
-- **TwoMonths**
-
-- **ThreeMonths**
-
-- **ThisYear**
-
-- **LastYear**
-
-### Additional considerations
-
-- By default, you must be a Reviewer, an Editor, an Approver, or an AGPM Administrator (Full Control) to perform this procedure. Specifically, you must have **List Contents** permission for the domain.
-
-- For more information about GPO attributes, see [Contents Tab Features](contents-tab-features-agpm40.md).
-
-### Additional references
-
-- [Advanced Group Policy Management 4.0](advanced-group-policy-management-40.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/set-a-default-template-agpm30ops.md b/mdop/agpm/set-a-default-template-agpm30ops.md
deleted file mode 100644
index 8da4e564b8..0000000000
--- a/mdop/agpm/set-a-default-template-agpm30ops.md
+++ /dev/null
@@ -1,64 +0,0 @@
----
-title: Set a Default Template
-description: Set a Default Template
-author: dansimp
-ms.assetid: 84edbd69-451b-4c10-a898-781d4b75d09c
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Set a Default Template
-
-
-As an Editor, you can specify which of the available templates will be the default template suggested for all Group Policy administrators creating new Group Policy Objects (GPOs).
-
-**Note**
-A template is an uneditable, static version of a GPO for use as a starting point for creating new, editable GPOs.
-
-
-
-A user account with the Editor or AGPM Administrator (Full Control) role or necessary permissions in Advanced Group Policy Management (AGPM) is required to complete this procedure. Review the details in "Additional considerations" in this topic.
-
-**To set the default template for use when creating new GPOs**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. On the **Contents** tab in the details pane, click the **Templates** tab to display available templates.
-
-3. Right-click the template that you want to set as the default, and then click **Set as Default**.
-
-4. Click **Yes** to confirm.
-
-5. When the **Progress** window indicates that overall progress is complete, click **Close**. The default template has a blue icon and the state is identified as **Template (default)** on the **Templates** tab.
-
-### Additional considerations
-
-- By default, you must be an Editor or an AGPM Administrator (Full Control) to perform this procedure. Specifically, you must have **List Contents** and **Create Template** permissions for the domain.
-
-- After you set a template as the default, that template will be the one initially selected in the **New Controlled GPO** dialog box when Group Policy administrators create new GPOs. However, they will have the option to select any other GPO template, including **<Empty GPO>**, which does not include any settings.
-
-- Renaming or deleting a template does not impact GPOs created from that template.
-
-- Because it cannot be altered, a template does not have a history.
-
-### Additional references
-
-- [Creating a Template and Setting a Default Template](creating-a-template-and-setting-a-default-template-agpm30ops.md)
-
-- [Request the Creation of a New Controlled GPO](request-the-creation-of-a-new-controlled-gpo-agpm30ops.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/set-a-default-template-agpm40.md b/mdop/agpm/set-a-default-template-agpm40.md
deleted file mode 100644
index c6b0a93381..0000000000
--- a/mdop/agpm/set-a-default-template-agpm40.md
+++ /dev/null
@@ -1,64 +0,0 @@
----
-title: Set a Default Template
-description: Set a Default Template
-author: dansimp
-ms.assetid: 07208b6b-cb3a-4f6c-9c84-36d4dc1486d8
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Set a Default Template
-
-
-As an Editor, you can specify which of the available templates will be the default template suggested for all Group Policy administrators creating new Group Policy Objects (GPOs).
-
-**Note**
-A template is an uneditable, static version of a GPO for use as a starting point for creating new, editable GPOs.
-
-
-
-A user account with the Editor or AGPM Administrator (Full Control) role or necessary permissions in Advanced Group Policy Management (AGPM) is required to complete this procedure. Review the details in "Additional considerations" in this topic.
-
-**To set the default template for use when creating new GPOs**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. On the **Contents** tab in the details pane, click the **Templates** tab to display available templates.
-
-3. Right-click the template that you want to set as the default, and then click **Set as Default**.
-
-4. Click **Yes** to confirm.
-
-5. When the **Progress** window indicates that overall progress is complete, click **Close**. The default template has a blue icon and the state is identified as **Template (default)** on the **Templates** tab.
-
-### Additional considerations
-
-- By default, you must be an Editor or an AGPM Administrator (Full Control) to perform this procedure. Specifically, you must have **List Contents** and **Create Template** permissions for the domain.
-
-- After you set a template as the default, that template will be the one initially selected in the **New Controlled GPO** dialog box when Group Policy administrators create new GPOs. However, they will have the option to select any other GPO template, including **<Empty GPO>**, which does not include any settings.
-
-- Renaming or deleting a template does not impact GPOs created from that template.
-
-- Because it cannot be altered, a template does not have a history.
-
-### Additional references
-
-- [Creating a Template and Setting a Default Template](creating-a-template-and-setting-a-default-template-agpm40.md)
-
-- [Request the Creation of a New Controlled GPO](request-the-creation-of-a-new-controlled-gpo-agpm40.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/set-a-default-template.md b/mdop/agpm/set-a-default-template.md
deleted file mode 100644
index 26a7b044a5..0000000000
--- a/mdop/agpm/set-a-default-template.md
+++ /dev/null
@@ -1,64 +0,0 @@
----
-title: Set a Default Template
-description: Set a Default Template
-author: dansimp
-ms.assetid: e0acf980-437f-4357-b237-298aaebe490d
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Set a Default Template
-
-
-As an Editor, you can specify which of the available templates will be the default template suggested for all Group Policy administrators creating new Group Policy objects (GPOs).
-
-**Note**
-A template is an uneditable, static version of a GPO for use as a starting point for creating new, editable GPOs.
-
-
-
-A user account with the Editor or AGPM Administrator (Full Control) role or necessary permissions in Advanced Group Policy Management is required to complete this procedure. Review the details in "Additional considerations" in this topic.
-
-**To set the default template for use when creating new GPOs**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. On the **Contents** tab in the details pane, click the **Templates** tab to display available templates.
-
-3. Right-click the template that you want to set as the default, and then click **Set as Default**.
-
-4. Click **Yes** to confirm.
-
-5. When the **Progress** window indicates that overall progress is complete, click **Close**. The default template has a blue icon and the state is identified as **Template (default)** on the **Templates** tab.
-
-### Additional considerations
-
-- By default, you must be an Editor or an AGPM Administrator (Full Control) to perform this procedure. Specifically, you must have **List Contents** and **Create Template** permissions for the domain.
-
-- After you set a template as the default, that template will be the one initially selected in the **New Controlled GPO** dialog box when Group Policy administrators create new GPOs. However, they will have the option to select any other GPO template, including **<Empty GPO>**, which does not include any settings.
-
-- Renaming or deleting a template does not impact GPOs created from that template.
-
-- Because it cannot be altered, a template does not have a history.
-
-### Additional references
-
-- [Creating a Template and Setting a Default Template](creating-a-template-and-setting-a-default-template.md)
-
-- [Request the Creation of a New Controlled GPO](request-the-creation-of-a-new-controlled-gpo.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/start-and-stop-the-agpm-service-agpm30ops.md b/mdop/agpm/start-and-stop-the-agpm-service-agpm30ops.md
deleted file mode 100644
index 4618d3c9fd..0000000000
--- a/mdop/agpm/start-and-stop-the-agpm-service-agpm30ops.md
+++ /dev/null
@@ -1,51 +0,0 @@
----
-title: Start and Stop the AGPM Service
-description: Start and Stop the AGPM Service
-author: dansimp
-ms.assetid: b9d26920-c439-4992-9a78-73e4fba8309d
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Start and Stop the AGPM Service
-
-
-The AGPM Service is a Windows service that acts as a security proxy, managing client access to Group Policy Objects (GPOs) in the archive and production environment.
-
-**Important**
-Stopping or disabling the AGPM Service will prevent AGPM Clients from performing any operations (such as listing or editing GPOs) through the server.
-
-
-
-A user account with access to the AGPM Server (the computer on which the AGPM Service is installed) is required to complete this procedure.
-
-**To start or stop the AGPM Service**
-
-1. On the computer on which Microsoft Advanced Group Policy Management - Server (and therefore the AGPM Service) is installed, click **Start**, click **Control Panel**, click **Administrative Tools**, and then click **Services**.
-
-2. In the list of services, right-click **AGPM Service** and select **Start**, **Restart**, or **Stop**.
-
- **Caution**
- Do not modify settings for the AGPM Service through **Administrative Tools** and **Services** in the operating system. Doing so can prevent the AGPM Service from starting.
-
-
-
-### Additional references
-
-- [Managing the AGPM Service](managing-the-agpm-service-agpm30ops.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/start-and-stop-the-agpm-service-agpm40.md b/mdop/agpm/start-and-stop-the-agpm-service-agpm40.md
deleted file mode 100644
index 3cc649d89b..0000000000
--- a/mdop/agpm/start-and-stop-the-agpm-service-agpm40.md
+++ /dev/null
@@ -1,51 +0,0 @@
----
-title: Start and Stop the AGPM Service
-description: Start and Stop the AGPM Service
-author: dansimp
-ms.assetid: dcc9566c-c515-4fbe-b7f5-8ac030141307
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Start and Stop the AGPM Service
-
-
-The AGPM Service is a Windows service that acts as a security proxy, managing client access to Group Policy Objects (GPOs) in the archive and production environment.
-
-**Important**
-Stopping or disabling the AGPM Service will prevent AGPM Clients from performing any operations (such as listing or editing GPOs) through the server.
-
-
-
-A user account with access to the AGPM Server (the computer on which the AGPM Service is installed) is required to complete this procedure.
-
-**To start or stop the AGPM Service**
-
-1. On the computer on which Microsoft Advanced Group Policy Management - Server (and therefore the AGPM Service) is installed, click **Start**, click **Control Panel**, click **Administrative Tools**, and then click **Services**.
-
-2. In the list of services, right-click **AGPM Service** and select **Start**, **Restart**, or **Stop**.
-
- **Caution**
- Do not modify settings for the AGPM Service through **Administrative Tools** and **Services** in the operating system. Doing so can prevent the AGPM Service from starting.
-
-
-
-### Additional references
-
-- [Managing the AGPM Service](managing-the-agpm-service-agpm40.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/start-and-stop-the-agpm-service.md b/mdop/agpm/start-and-stop-the-agpm-service.md
deleted file mode 100644
index e81cfefbbd..0000000000
--- a/mdop/agpm/start-and-stop-the-agpm-service.md
+++ /dev/null
@@ -1,51 +0,0 @@
----
-title: Start and Stop the AGPM Service
-description: Start and Stop the AGPM Service
-author: dansimp
-ms.assetid: 769aa0ce-224a-446f-9958-9518af4ad159
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Start and Stop the AGPM Service
-
-
-The AGPM Service is a Windows service that acts as a security proxy, managing client access to Group Policy objects (GPOs) in the archive and production environment.
-
-**Important**
-Stopping or disabling the AGPM Service will prevent AGPM clients from performing any operations (such as listing or editing GPOs) through the server.
-
-
-
-A user account with access to the AGPM Server (the computer on which the AGPM Service is installed) is required to complete this procedure.
-
-**To start or stop the AGPM Service**
-
-1. On the computer on which Microsoft Advanced Group Policy Management - Server (and therefore the AGPM Service) is installed, click **Start**, click **Control Panel**, click **Administrative Tools**, and then click **Services**.
-
-2. In the list of services, right-click **AGPM Service** and select **Start**, **Restart**, or **Stop**.
-
- **Caution**
- Do not modify settings for the AGPM Service through **Administrative Tools** and **Services** in the operating system. Doing so can prevent the AGPM Service from starting. To modify settings for the service, see [Managing the AGPM Service](managing-the-agpm-service.md).
-
-
-
-### Additional references
-
-- [Managing the AGPM Service](managing-the-agpm-service.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/step-by-step-guide-for-microsoft-advanced-group-policy-management-25.md b/mdop/agpm/step-by-step-guide-for-microsoft-advanced-group-policy-management-25.md
deleted file mode 100644
index e177ef9954..0000000000
--- a/mdop/agpm/step-by-step-guide-for-microsoft-advanced-group-policy-management-25.md
+++ /dev/null
@@ -1,541 +0,0 @@
----
-title: Step-by-Step Guide for Microsoft Advanced Group Policy Management 2.5
-description: Step-by-Step Guide for Microsoft Advanced Group Policy Management 2.5
-author: dansimp
-ms.assetid: 454298c9-0fab-497a-9808-c0246a4c8db5
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 08/30/2016
----
-
-
-# Step-by-Step Guide for Microsoft Advanced Group Policy Management 2.5
-
-
-This step-by-step guide demonstrates advanced techniques for Group Policy management using the Group Policy Management Console (GPMC) and Microsoft Advanced Group Policy Management (AGPM). AGPM increases the capabilities of the GPMC, providing:
-
-- Standard roles for delegating permissions to manage Group Policy objects (GPOs) to multiple Group Policy administrators.
-
-- An archive to enable Group Policy administrators to create and modify GPOs offline before deploying them to a production environment.
-
-- The ability to roll back to any previous version of a GPO.
-
-- Check-in/check-out capability for GPOs to ensure that Group Policy administrators do not inadvertently overwrite each other's work.
-
-## AGPM scenario overview
-
-
-For this scenario, you will use a separate user account for each role in AGPM to demonstrate how Group Policy can be managed in an environment with multiple Group Policy administrators who have different levels of permissions. Specifically, you will perform the following tasks:
-
-- Using an account that is a member of the Domain Admins group, install AGPM Server and assign the AGPM Administrator role to an account or group.
-
-- Using accounts to which you will assign AGPM roles, install AGPM Client.
-
-- Using an account with the AGPM Administrator role, configure AGPM and delegate access to GPOs by assigning roles to other accounts.
-
-- Using an account with the Editor role, request the creation of a GPO, which you then approve using an account with the Approver role. With the Editor account, check the GPO out of the archive, edit the GPO, check the GPO into the archive, and request deployment.
-
-- Using an account with the Approver role, review the GPO and deploy it to your production environment.
-
-- Using an account with the Editor role, create a GPO template and use it as a starting point to create a new GPO.
-
-- Using an account with the Approver role, delete and restore a GPO.
-
-
-
-## Requirements
-
-
-Computers on which you want to install AGPM must meet the following requirements, and you must create accounts for use in this scenario.
-
-### AGPM Server requirements
-
-AGPM Server 2.5 requires Windows Vista® (32-bit version) with no service packs installed or Windows Server® 2003 (32-bit version), as well as the GPMC. Additionally, you must be a member of the Domain Admins group to install AGPM Server.
-
-You should install AGPM Server on a member server or domain controller with the most recent version of the GPMC that is available to you and supported by AGPM. AGPM uses the GPMC to back up and restore GPOs, and newer versions of the GPMC provide additional policy settings not available in preceding versions. If the version of the GPMC on your AGPM Server is older than the version on the computers that administrators use to manage Group Policy, the AGPM Server will be unable to store those policy settings not available in the older version of the GPMC.
-
-Specifically, if your AGPM Server is running Windows Server 2003 and the version of the GPMC that accompanied it, and your Group Policy administrators’ computers are running Windows Vista and the version of the GPMC that accompanied it, you can still manage most policy settings. However, policy settings from the GPMC in Windows Vista that are not available in the GPMC in Windows Server 2003—such as those related to folder redirection, wireless networking (IEEE 802.11), and deployed printers—cannot be stored by the AGPM Server, even though administrators can configure them using AGPM on their computers.
-
-If you must install AGPM Server on a computer with an older version of GPMC than your Group Policy administrators are running, see the Group Policy Settings Reference for details about which policy settings are available with which operating systems. To download the Group Policy Settings Reference, see .
-
-**Note**
-Archives cannot be migrated from an AGPM Server or a GPOVault Server running Windows Server 2003 to an AGPM Server running Windows Vista.
-
-For Windows Server 2003, if GPOVault Server is installed on the computer on which you want to install AGPM Server, it is recommended that you do not uninstall GPOVault Server before beginning the installation. The installation of AGPM Server will uninstall GPOVault Server and automatically transfer your existing GPOVault archive data to an AGPM archive.
-
-
-
-### AGPM Client requirements
-
-AGPM Client 2.5 requires Windows Vista (32-bit version) with no service packs installed or Windows Server 2003 (32-bit version), as well as the GPMC. AGPM Client can be installed on a computer running AGPM Server.
-
-### Scenario requirements
-
-Before you begin this scenario, create four user accounts. During the scenario, you will assign one of the following AGPM roles to each of these accounts: AGPM Administrator (Full Control), Approver, Editor, and Reviewer. These accounts must be able to send and receive e-mail messages. Assign **Link GPOs** permission to the accounts with the AGPM Administrator, Approver, and (optionally) Editor roles.
-
-**Note**
-**Link GPOs** permission is assigned to members of Domain Administrators and Enterprise Administrators by default. To assign **Link GPOs** permission to additional users or groups (such as accounts with the roles of AGPM Administrator or Approver), click the node for the domain and then click the **Delegation** tab, select **Link GPOs**, click **Add**, and select users or groups to which to assign the permission.
-
-
-
-For this scenario, you perform actions with different accounts. You can either log on with each account as indicated, or you can use the **Run as** command to start the GPMC with the indicated account.
-
-**Note**
-To use the **Run as** command with GPMC on Windows Server 2003, click **Start**, point to **Administrative Tools**, right-click **Group Policy Management**, and click **Run as**. Click **The following user** and enter credentials for an account.
-
-To use the **Run as** command with GPMC on Windows Vista, click the **Start** button, point to **Run**, and type **runas /user:**DomainName\\UserName**"mmc %windir%\\system32\\gpmc.msc"**, and click **OK**. Type the password for the account when prompted.
-
-
-
-## Steps for installing and configuring AGPM
-
-
-You must complete the following steps to install and configure AGPM.
-
-[Step 1: Install AGPM Server](#bkmk-config1)
-
-[Step 2: Install AGPM Client](#bkmk-config2)
-
-[Step 3: Configure an AGPM Server connection](#bkmk-config3)
-
-[Step 4: Configure e-mail notification](#bkmk-config4)
-
-[Step 5: Delegate access](#bkmk-config5)
-
-### Step 1: Install AGPM Server
-
-In this step, you install AGPM Server on the member server or domain controller that will run the AGPM Service, and you configure the archive. All AGPM operations are managed through this Windows service and are executed with the service's credentials. The archive managed by an AGPM Server can be hosted on that server or on another server in the same forest.
-
-**To install AGPM Server on the computer that will host the AGPM Service**
-
-1. Log on with an account that is a member of the Domain Admins group.
-
-2. Start the Microsoft Desktop Optimization Pack CD and follow the instructions on screen to select **Advanced Group Policy Management - Server**.
-
-3. In the **Welcome** dialog box, click **Next**.
-
-4. In the **Microsoft Software License Terms** dialog box, accept the terms and click **Next**.
-
-5. In the **Application Path** dialog box, select a location in which to install AGPM Server. The computer on which AGPM Server is installed will host the AGPM Service and manage the archive. Click **Next**.
-
-6. In the **Archive Path** dialog box, select a location for the archive relative to the AGPM Server. The archive path can point to a folder on the AGPM Server or elsewhere, but you should select a location with sufficient space to store all GPOs and history data managed by this AGPM Server. Click **Next**.
-
-7. In the **AGPM Service Account** dialog box, select a service account under which the AGPM Service will run and then click **Next**.
-
-8. In the **Archive Owner** dialog box, select an account or group to which to initially assign the AGPM Administrator (Full Control) role. This AGPM Administrator can assign AGPM roles and permissions to other Group Policy administrators (including the role of AGPM Administrator). For this scenario, select the account to serve in the AGPM Administrator role. Click **Next**.
-
-9. Click **Install**, and then click **Finish** to exit the Setup Wizard.
-
- **Caution**
- Do not modify settings for the AGPM Service through **Administrative Tools** and **Services** in the operating system. Doing so can prevent the AGPM Service from starting. For information on how to modify settings for the service, see Help for Advanced Group Policy Management.
-
-
-
-### Step 2: Install AGPM Client
-
-Each Group Policy administrator—anyone who creates, edits, deploys, reviews, or deletes GPOs—must have AGPM Client installed on computers that they use to manage GPOs. For this scenario, you install AGPM Client on at least one computer. You do not need to install AGPM Client on the computers of end users who do not perform Group Policy administration.
-
-**To install AGPM Client on the computer of a Group Policy administrator**
-
-1. Start the Microsoft Desktop Optimization Pack CD and follow the instructions on screen to select **Advanced Group Policy Management - Client**.
-
-2. In the **Welcome** dialog box, click **Next**.
-
-3. In the **Microsoft Software License Terms** dialog box, accept the terms and click **Next**.
-
-4. In the **Application Path** dialog box, select a location in which to install AGPM Client. Click **Next**.
-
-5. In the **AGPM Server** dialog box, type the fully-qualified computer name and the port for the AGPM Server to which to connect. The default port for the AGPM Service is 4600. Click **Next**.
-
-6. Click **Install**, and then click **Finish** to exit the Setup Wizard.
-
-### Step 3: Configure an AGPM Server connection
-
-AGPM stores all versions of each controlled Group Policy object (GPO)—a GPO for which AGPM provides change control—in a central archive, so Group Policy administrators can view and modify GPOs offline without immediately impacting the deployed version of each GPO.
-
-In this step, you configure an AGPM Server connection and ensure that all Group Policy administrators connect to the same AGPM Server. (For information about configuring multiple AGPM Servers, see Help for Advanced Group Policy Management.)
-
-**To configure an AGPM Server connection for all Group Policy administrators**
-
-1. On a computer on which you have installed AGPM Client, log on with the user account that you selected as the Archive Owner. This user has the role of AGPM Administrator (Full Control).
-
-2. Click **Start**, point to **Administrative Tools**, and click **Group Policy Management** to open the **Group Policy Management Console (GPMC)**.
-
-3. In the **Group Policy Management Console** tree, edit a GPO that is applied to all Group Policy administrators.
-
-4. In the **Group Policy Object Editor** window, click **User Configuration**, **Administrative Templates**, and **Windows Components**.
-
-5. If **AGPM** is not listed under **Windows Components**:
-
- 1. Right-click **Administrative Templates** and select **Add/Remove Templates**.
-
- 2. Click **Add**, select **agpm.admx** or **agpm.adm**, click **Open**, and then click **Close**.
-
-6. Under **Windows Components**, double-click **AGPM**.
-
-7. In the details pane, double-click **AGPM Server (all domains)**.
-
-8. In the **AGPM Server (all domains) Properties** window, select **Enabled** and type the fully-qualified computer name and port (for example, server.contoso.com:4600) for the server hosting the archive. The port used by the AGPM Service is port 4600.
-
-9. Click **OK**, and then close the **Group Policy Object Editor** window. When Group Policy is updated, the AGPM Server connection is configured for each Group Policy administrator.
-
-### Step 4: Configure e-mail notification
-
-As an AGPM Administrator (Full Control), you designate the e-mail addresses of Approvers and AGPM Administrators to whom an e-mail message containing a request is sent when an Editor attempts to create, deploy, or delete a GPO. You also determine the alias from which these messages are sent.
-
-**To configure e-mail notification for AGPM**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. In the details pane, click the **Domain Delegation** tab.
-
-3. In the **From** field, type the e-mail alias for AGPM from which notifications should be sent.
-
-4. In the **To** field, type the e-mail address for the user account to which you intend to assign the Approver role.
-
-5. In the **SMTP server** field, type a valid SMTP mail server.
-
-6. In the **User name** and **Password** fields, type the credentials of a user with access to the SMTP service.
-
-7. Click **Apply**.
-
-### Step 5: Delegate access
-
-As an AGPM Administrator (Full Control), you delegate domain-level access to GPOs, assigning roles to the account of each Group Policy administrator.
-
-**Note**
-You can also delegate access at the GPO level rather than the domain level. For details, see Help for Advanced Group Policy Management.
-
-
-
-**Important**
-You should restrict membership in the Group Policy Creator Owners group, so it cannot be used to circumvent AGPM management of access to GPOs. (In the **Group Policy Management Console**, click **Group Policy Objects** in the forest and domain in which you want to manage GPOs, click **Delegation**, and then configure the settings to meet the needs of your organization.)
-
-
-
-**To delegate access to all GPOs throughout a domain**
-
-1. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-2. On the **Domain Delegation** tab, click the **Advanced** button.
-
-3. In the **Permissions** dialog box:
-
- 1. Click the user account of a Group Policy administrator, and then select the **Approver** check box to assign that role to the account. Clear the **Editor** check box. (This role includes the Reviewer role.)
-
- 2. Click the user account of another Group Policy administrator, and then select the **Editor** check box to assign that role to the account. (This role includes the Reviewer role.)
-
- 3. Click a third account and then select the **Reviewer** check box to assign only the Reviewer role to the account of that Group Policy administrator. Clear the **Editor** check box.
-
- 4. Click the **Advanced** button.
-
-4. In the **Advanced Security Settings** dialog box:
-
- 1. Select a Group Policy administrator, and then click **Edit**.
-
- 2. For **Apply onto**, select **This object and nested objects**, and then click **OK** in the **Permission** **Entry** dialog box.
-
- 3. Repeat for each Group Policy administrator.
-
-5. In the **Advanced Security Settings** dialog box, click **OK**.
-
-6. In the **Permissions** dialog box, click **OK**.
-
-## Steps for managing GPOs
-
-
-You must complete the following steps to create, edit, review, and deploy GPOs using AGPM. Additionally, you will create a template, delete a GPO, and restore a deleted GPO.
-
-[Step 1: Create a GPO](#bkmk-manage1)
-
-[Step 2: Edit a GPO](#bkmk-manage2)
-
-[Step 3: Review and deploy a GPO](#bkmk-manage3)
-
-[Step 4: Use a template to create a GPO](#bkmk-manage4)
-
-[Step 5: Delete and restore a GPO](#bkmk-manage5)
-
-### Step 1: Create a GPO
-
-In an environment with multiple Group Policy administrators, those with the Editor role have the ability to request the creation of new GPOs, but such a request must be approved by someone with the Approver role because the creation of a new GPO impacts the production environment.
-
-In this step, you use an account with the Editor role to request the creation of a new GPO. Using an account with the Approver role, you approve this request and complete the creation of a GPO.
-
-**To request the creation of a new GPO managed through AGPM**
-
-1. On a computer on which you have installed AGPM Client, log on with a user account that has been assigned the Editor role in AGPM.
-
-2. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-3. Right-click the **Change Control** node, and then click **New Controlled GPO**.
-
-4. In the **New Controlled GPO** dialog box:
-
- 1. To receive a copy of the request, type your e-mail address in the **Cc** field.
-
- 2. Type **MyGPO** as the name for the new GPO.
-
- 3. Type a comment for the new GPO.
-
- 4. Click **Create live** so the new GPO will be deployed to the production environment immediately upon approval.
-
- 5. Click **Submit**.
-
-5. When the **AGPM Progress** window indicates that overall progress is complete, click **Close**. The new GPO is displayed on the **Pending** tab.
-
-**To approve the pending request to create a GPO**
-
-1. On a computer on which you have installed AGPM Client, log on with a user account that has been assigned the role of Approver in AGPM.
-
-2. Open the e-mail inbox for the account, and note that you have received an e-mail message from the AGPM alias with the Editor's request to create a GPO.
-
-3. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-4. On the **Contents** tab, click the **Pending** tab to display the pending GPOs.
-
-5. Right-click **MyGPO**, and then click **Approve**.
-
-6. Click **Yes** to confirm approval of the creation of the GPO. The GPO is moved to the **Controlled** tab.
-
-### Step 2: Edit a GPO
-
-You can use GPOs to configure computer or user settings and deploy them to many computers or users. In this step, you use an account with the Editor role to check out a GPO from the archive, edit the GPO offline, check the edited GPO into the archive, and request deployment of the GPO to the production environment. For this scenario, you configure a setting in the GPO to require that the password be at least eight characters in length.
-
-**To check the GPO out from the archive for editing**
-
-1. On a computer on which you have installed AGPM Client, log on with a user account that has been assigned the role of Editor in AGPM.
-
-2. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-3. On the **Contents** tab in the details pane, click the **Controlled** tab to display the controlled GPOs.
-
-4. Right-click **MyGPO**, and then click **Check Out**.
-
-5. Type a comment to be displayed in the **History** of the GPO while it is checked out, and then click **OK**.
-
-6. When the **AGPM Progress** window indicates that overall progress is complete, click **Close**. On the **Controlled** tab, the state of the GPO is identified as **Checked Out**.
-
-**To edit the GPO offline and configure the minimum password length**
-
-1. On the **Controlled** tab, right-click **MyGPO**, and then click **Edit** to open the **Group Policy Object Editor** window and make changes to an offline copy of the GPO. For this scenario, configure the minimum password length:
-
- 1. Under **Computer Configuration**, double-click **Windows Settings**, double-click **Security Settings**, double-click **Account Policies**, and double-click **Password Policy**.
-
- 2. In the details pane, double-click **Minimum password length**.
-
- 3. In the properties window, select the **Define this policy setting** check box, set the number of characters to **8**, and then click **OK**.
-
-2. Close the **Group Policy Object Editor** window.
-
-**To check the GPO into the archive**
-
-1. On the **Controlled** tab, right-click **MyGPO** and then click **Check In**.
-
-2. Type a comment, and then click **OK**.
-
-3. When the **AGPM Progress** window indicates that overall progress is complete, click **Close**. On the **Controlled** tab, the state of the GPO is identified as **Checked In**.
-
-**To request the deployment of the GPO to the production environment**
-
-1. On the **Controlled** tab, right-click **MyGPO** and then click **Deploy**.
-
-2. Because this account is not an Approver or AGPM Administrator, you must submit a request for deployment. To receive a copy of the request, type your e-mail address in the **Cc** field. Type a comment to be displayed in the **History** of the GPO, and then click **Submit**.
-
-3. When the **AGPM Progress** window indicates that overall progress is complete, click **Close**. **MyGPO** is displayed on the list of GPOs on the **Pending** tab.
-
-### Step 3: Review and deploy a GPO
-
-In this step, you act as an Approver, creating reports and analyzing the settings and changes to settings in the GPO to determine whether you should approve them. After evaluating the GPO, you deploy it to the production environment and link it to a domain or an organizational unit (OU) so that it takes effect when Group Policy is refreshed for computers in that domain or OU.
-
-**To review settings in the GPO**
-
-1. On a computer on which you have installed AGPM Client, log on with a user account that has been assigned the role of Approver in AGPM. (Any Group Policy administrator with the Reviewer role, which is included in all of the other roles, can review the settings in a GPO.)
-
-2. Open the e-mail inbox for the account and note that you have received an e-mail message from the AGPM alias with an Editor's request to deploy a GPO.
-
-3. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-4. On the **Contents** tab in the details pane, click the **Pending** tab.
-
-5. Double-click **MyGPO** to display its history.
-
-6. Review the settings in the most recent version of MyGPO:
-
- 1. In the **History** window, right-click the GPO version with the most recent timestamp, click **Settings**, and then click **HTML Report** to display a summary of the GPO's settings.
-
- 2. In the Web browser, click **show all** to display all of the settings in the GPO.
-
- 3. Close the browser.
-
-7. Compare the most recent version of MyGPO to the first version checked in to the archive:
-
- 1. In the **History** window, click the GPO version with the most recent timestamp. Press **CTRL** and click the oldest GPO version that has a state of **Checked In**.
-
- 2. Click the **Differences** button. The **Account Policies/Password Policy** section is highlighted in green and preceded by **\[+\]**, indicating that this setting is configured only in the latter version of the GPO.
-
- 3. Click **Account Policies/Password Policy**. The **Minimum password length** setting is also highlighted in green and preceded by **\[+\]**, indicating that it is configured only in the latter version of the GPO.
-
- 4. Close the Web browser.
-
-**To deploy the GPO to the production environment**
-
-1. On the **Pending** tab, right-click **MyGPO** and then click **Approve**.
-
-2. Type a comment to include in the history of the GPO.
-
-3. Click **Yes**. When the **AGPM Progress** window indicates that overall progress is complete, click **Close**. The GPO is deployed to the production environment.
-
-**To link the GPO to a domain or organizational unit**
-
-1. In the GPMC, right-click the domain or an OU to which to apply the GPO that you configured, and then click **Link an Existing GPO**.
-
-2. In the **Select GPO** dialog box, click **MyGPO**, and then click **OK**.
-
-### Step 4: Use a template to create a GPO
-
-In this step, you use an account with the Editor role to create a template—an uneditable, static version of a GPO for use as a starting point for creating new GPOs—and then create a new GPO based upon that template. Templates are useful for quickly creating multiple GPOs that include many of the same settings.
-
-**To create a template based on an existing GPO**
-
-1. On a computer on which you have installed AGPM Client, log on with a user account that has been assigned the role of Editor in AGPM.
-
-2. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-3. On the **Contents** tab in the details pane, click the **Controlled** tab.
-
-4. Right-click **MyGPO**, and then click **Save as Template** to create a template incorporating all settings currently in MyGPO.
-
-5. Type **MyTemplate** as the name for the template and a comment, and then click **OK**.
-
-6. When the **AGPM Progress** window indicates that overall progress is complete, click **Close**. The new template appears on the **Templates** tab.
-
-**To request the creation of a new GPO managed through AGPM**
-
-1. Click the **Controlled** tab.
-
-2. Right-click the **Change Control** node, and then click **New Controlled GPO**.
-
-3. In the **New Controlled GPO** dialog box:
-
- 1. To receive a copy of the request, type your e-mail address in the **Cc** field.
-
- 2. Type **MyOtherGPO** as the name for the new GPO.
-
- 3. Type a comment for the new GPO.
-
- 4. Click **Create live**, so the new GPO will be deployed to the production environment immediately upon approval.
-
- 5. For **From GPO template**, select **MyTemplate**.
-
- 6. Click **Submit**.
-
-4. When the **AGPM Progress** window indicates that overall progress is complete, click **Close**. The new GPO is displayed on the **Pending** tab.
-
-Use an account that has been assigned the role of Approver to approve the pending request to create the GPO as you did in [Step 1: Create a GPO](#bkmk-manage1). MyTemplate incorporates all of the settings that you configured in MyGPO. Because MyOtherGPO was created using MyTemplate, it initially contains all of the settings that MyGPO contained at the time that MyTemplate was created. You can confirm this by generating a difference report to compare MyOtherGPO to MyTemplate.
-
-**To check the GPO out from the archive for editing**
-
-1. On a computer on which you have installed AGPM Client, log on with a user account that has been assigned the role of Editor in AGPM.
-
-2. Right-click **MyOtherGPO**, and then click **Check Out**.
-
-3. Type a comment to be displayed in the history of the GPO while it is checked out, and then click **OK**.
-
-4. When the **AGPM Progress** window indicates that overall progress is complete, click **Close**. On the **Controlled** tab, the state of the GPO is identified as **Checked Out**.
-
-**To edit the GPO offline and configure the account lockout duration**
-
-1. On the **Controlled** tab, right-click **MyOtherGPO**, and then click **Edit** to open the **Group Policy Object Editor** window and make changes to an offline copy of the GPO. For this scenario, configure the minimum password length:
-
- 1. Under **Computer Configuration**, double-click **Windows Settings**, double-click **Security Settings**, double-click **Account Policies**, and double-click **Account Lockout Policy**.
-
- 2. In the details pane, double-click **Account lockout duration**.
-
- 3. In the properties window, check **Define this policy setting**, set the duration to **30** minutes, and then click **OK**.
-
-2. Close the **Group Policy Object Editor** window.
-
-Check MyOtherGPO into the archive and request deployment as you did for MyGPO in [Step 2: Edit a GPO](#bkmk-manage2). You can compare MyOtherGPO to MyGPO or to MyTemplate using difference reports. Any account that includes the Reviewer role (AGPM Administrator \[Full Control\], Approver, Editor, or Reviewer) can generate reports.
-
-**To compare a GPO to another GPO and to a template**
-
-1. To compare MyGPO and MyOtherGPO:
-
- 1. On the **Controlled** tab, click **MyGPO**. Press **CTRL** and then click **MyOtherGPO**.
-
- 2. Right-click **MyOtherGPO**, point to **Differences**, and click **HTML Report**.
-
-2. To compare MyOtherGPO and MyTemplate:
-
- 1. On the **Controlled** tab, click **MyOtherGPO**.
-
- 2. Right-click **MyOtherGPO**, point to **Differences**, and click **Template**.
-
- 3. Select **MyTemplate** and **HTML Report**, and then click **OK**.
-
-### Step 5: Delete and restore a GPO
-
-In this step, you act as an Approver to delete a GPO.
-
-**To delete a GPO**
-
-1. On a computer on which you have installed AGPM Client, log on with a user account that has been assigned the role of Approver.
-
-2. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-3. On the **Contents** tab, click the **Controlled** tab to display the controlled GPOs.
-
-4. Right-click **MyGPO**, and then click **Delete**. Click **Delete GPO from archive and production** to delete both the version in the archive as well as the deployed version of the GPO in the production environment.
-
-5. Type a comment to be displayed in the audit trail for the GPO, and then click **OK**.
-
-6. When the **AGPM Progress** window indicates that overall progress is complete, click **Close**. The GPO is removed from the **Controlled** tab and is displayed on the **Recycle Bin** tab, where it can be restored or destroyed.
-
-Occasionally you may discover after deleting a GPO that it is still needed. In this step, you act as an Approver to restore a GPO that has been deleted.
-
-**To restore a deleted GPO**
-
-1. On the **Contents** tab, click the **Recycle Bin** tab to display deleted GPOs.
-
-2. Right-click **MyGPO**, and then click **Restore**.
-
-3. Type a comment to be displayed in the history of the GPO, and then click **OK**.
-
-4. When the **AGPM Progress** window indicates that overall progress is complete, click **Close**. The GPO is removed from the **Recycle Bin** tab and is displayed on the **Controlled** tab.
-
- **Note**
- Restoring a GPO to the archive does not automatically redeploy it to the production environment. To return the GPO to the production environment, deploy the GPO as in [Step 3: Review and deploy a GPO](#bkmk-manage3).
-
-
-
-After editing and deploying a GPO, you may discover that recent changes to the GPO are causing a problem. In this step, you act as an Approver to roll back to a previous version of the GPO. You can roll back to any version in the history of the GPO. You can use comments and labels to identify known good versions and when specific changes were made.
-
-**To roll back to a previous version of a GPO**
-
-1. On the **Contents** tab, click the **Controlled** tab to display the controlled GPOs.
-
-2. Double-click **MyGPO** to display its history.
-
-3. Right-click the version to be deployed, click **Deploy**, and then click **Yes**.
-
-4. When the **Progress** window indicates that overall progress is complete, click **Close**. In the **History** window, click **Close**.
-
- **Note**
- To verify that the version that has been redeployed is the version intended, examine a difference report for the two versions. In the **History** window for the GPO, select the two versions, right-click them, point to **Difference**, and then click either **HTML Report** or **XML Report**.
-
-
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/step-by-step-guide-for-microsoft-advanced-group-policy-management-30.md b/mdop/agpm/step-by-step-guide-for-microsoft-advanced-group-policy-management-30.md
deleted file mode 100644
index f0fa732a4c..0000000000
--- a/mdop/agpm/step-by-step-guide-for-microsoft-advanced-group-policy-management-30.md
+++ /dev/null
@@ -1,530 +0,0 @@
----
-title: Step-by-Step Guide for Microsoft Advanced Group Policy Management 3.0
-description: Step-by-Step Guide for Microsoft Advanced Group Policy Management 3.0
-author: dansimp
-ms.assetid: d067f465-d7c8-4f6d-b311-66b9b06874f7
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 08/30/2016
----
-
-
-# Step-by-Step Guide for Microsoft Advanced Group Policy Management 3.0
-
-
-This step-by-step guide demonstrates advanced techniques for Group Policy management using the Group Policy Management Console (GPMC) and Microsoft Advanced Group Policy Management (AGPM). AGPM increases the capabilities of the GPMC, providing:
-
-- Standard roles for delegating permissions to manage Group Policy objects (GPOs) to multiple Group Policy administrators, as well as the ability to delegate access to GPOs in the production environment.
-
-- An archive to enable Group Policy administrators to create and modify GPOs offline before deploying them to a production environment.
-
-- The ability to roll back to any previous version of a GPO in the archive and to limit the number of versions stored in the archive.
-
-- Check-in/check-out capability for GPOs to ensure that Group Policy administrators do not inadvertently overwrite each other's work.
-
-## AGPM scenario overview
-
-
-For this scenario, you will use a separate user account for each role in AGPM to demonstrate how Group Policy can be managed in an environment with multiple Group Policy administrators who have different levels of permissions. Specifically, you will perform the following tasks:
-
-- Using an account that is a member of the Domain Admins group, install AGPM Server and assign the AGPM Administrator role to an account or group.
-
-- Using accounts to which you will assign AGPM roles, install AGPM Client.
-
-- Using an account with the AGPM Administrator role, configure AGPM and delegate access to GPOs by assigning roles to other accounts.
-
-- Using an account with the Editor role, request the creation of a GPO, which you then approve using an account with the Approver role. With the Editor account, check the GPO out of the archive, edit the GPO, check the GPO into the archive, and request deployment.
-
-- Using an account with the Approver role, review the GPO and deploy it to your production environment.
-
-- Using an account with the Editor role, create a GPO template and use it as a starting point to create a new GPO.
-
-- Using an account with the Approver role, delete and restore a GPO.
-
-
-
-## Requirements
-
-
-Computers on which you want to install AGPM must meet the following requirements, and you must create accounts for use in this scenario.
-
-**Note**
-If you have AGPM 2.5 installed and are upgrading from Windows Server® 2003 to Windows Server 2008 or Windows Vista® with no service packs installed to Windows Vista with Service Pack 1, you must upgrade the operating system before you can upgrade to AGPM 3.0.
-
-
-
-### AGPM Server requirements
-
-AGPM Server 3.0 requires Windows Server 2008 or Windows Vista with Service Pack 1 and the GPMC from Remote Server Administration Tools (RSAT) installed. Both 32-bit and 64-bit versions are supported.
-
-Before you install AGPM Server, you must be a member of the Domain Admins group and the following Windows features must be present unless otherwise noted:
-
-- GPMC
-
- - Windows Server 2008: The GPMC is automatically installed by AGPM if not present.
-
- - Windows Vista: You must install the GPMC from RSAT before you install AGPM. For more information, see .
-
-- .NET Framework 3.5
-
-The following Windows features are required by AGPM Server and will be automatically installed if not present:
-
-- WCF Activation; Non-HTTP Activation
-
-- Windows Process Activation Service
-
- - Process Model
-
- - .NET Environment
-
- - Configuration APIs
-
-### AGPM Client requirements
-
-AGPM Client 3.0 requires Windows Server 2008 or Windows Vista with Service Pack 1 and the GPMC from Remote Server Administration Tools (RSAT) installed. Both 32-bit and 64-bit versions are supported. AGPM Client can be installed on a computer running AGPM Server.
-
-The following Windows features are required by AGPM Client and will be automatically installed if not present unless otherwise noted:
-
-- GPMC
-
- - Windows Server 2008: The GPMC is automatically installed by AGPM if not present.
-
- - Windows Vista: You must install the GPMC from RSAT before you install AGPM. For more information, see .
-
-- .NET Framework 3.0
-
-### Scenario requirements
-
-Before you begin this scenario, create four user accounts. During the scenario, you will assign one of the following AGPM roles to each of these accounts: AGPM Administrator (Full Control), Approver, Editor, and Reviewer. These accounts must be able to send and receive e-mail messages. Assign **Link GPOs** permission to the accounts with the AGPM Administrator, Approver, and (optionally) Editor roles.
-
-**Note**
-**Link GPOs** permission is assigned to members of Domain Administrators and Enterprise Administrators by default. To assign **Link GPOs** permission to additional users or groups (such as accounts with the roles of AGPM Administrator or Approver), click the node for the domain and then click the **Delegation** tab, select **Link GPOs**, click **Add**, and select users or groups to which to assign the permission.
-
-
-
-## Steps for installing and configuring AGPM
-
-
-You must complete the following steps to install and configure AGPM.
-
-[Step 1: Install AGPM Server](#bkmk-config1)
-
-[Step 2: Install AGPM Client](#bkmk-config2)
-
-[Step 3: Configure an AGPM Server connection](#bkmk-config3)
-
-[Step 4: Configure e-mail notification](#bkmk-config4)
-
-[Step 5: Delegate access](#bkmk-config5)
-
-### Step 1: Install AGPM Server
-
-In this step, you install AGPM Server on the member server or domain controller that will run the AGPM Service, and you configure the archive. All AGPM operations are managed through this Windows service and are executed with the service's credentials. The archive managed by an AGPM Server can be hosted on that server or on another server in the same forest.
-
-**To install AGPM Server on the computer that will host the AGPM Service**
-
-1. Log on with an account that is a member of the Domain Admins group.
-
-2. Start the Microsoft Desktop Optimization Pack CD and follow the instructions on screen to select **Advanced Group Policy Management - Server**.
-
-3. In the **Welcome** dialog box, click **Next**.
-
-4. In the **Microsoft Software License Terms** dialog box, accept the terms and click **Next**.
-
-5. In the **Application Path** dialog box, select a location in which to install AGPM Server. The computer on which AGPM Server is installed will host the AGPM Service and manage the archive. Click **Next**.
-
-6. In the **Archive Path** dialog box, select a location for the archive relative to the AGPM Server. The archive path can point to a folder on the AGPM Server or elsewhere, but you should select a location with sufficient space to store all GPOs and history data managed by this AGPM Server. Click **Next**.
-
-7. In the **AGPM Service Account** dialog box, select a service account under which the AGPM Service will run and then click **Next**.
-
-8. In the **Archive Owner** dialog box, select an account or group to which to initially assign the AGPM Administrator (Full Control) role. This AGPM Administrator can assign AGPM roles and permissions to other Group Policy administrators (including the role of AGPM Administrator). For this scenario, select the account to serve in the AGPM Administrator role. Click **Next**.
-
-9. In the **Port Configuration** dialog box, type a port on which the AGPM Service should listen. Do not clear the **Add port exception to firewall** check box unless you manually configure port exceptions or use rules to configure port exceptions. Click **Next**.
-
-10. In the **Languages** dialog box, select one or more display languages to install for AGPM Server.
-
-11. Click **Install**, and then click **Finish** to exit the Setup Wizard.
-
- **Caution**
- Do not modify settings for the AGPM Service through **Administrative Tools** and **Services** in the operating system. Doing so can prevent the AGPM Service from starting. For information on how to modify settings for the service, see Help for Advanced Group Policy Management.
-
-
-
-### Step 2: Install AGPM Client
-
-Each Group Policy administrator—anyone who creates, edits, deploys, reviews, or deletes GPOs—must have AGPM Client installed on computers that they use to manage GPOs. For this scenario, you install AGPM Client on at least one computer. You do not need to install AGPM Client on the computers of end users who do not perform Group Policy administration.
-
-**To install AGPM Client on the computer of a Group Policy administrator**
-
-1. Start the Microsoft Desktop Optimization Pack CD and follow the instructions on screen to select **Advanced Group Policy Management - Client**.
-
-2. In the **Welcome** dialog box, click **Next**.
-
-3. In the **Microsoft Software License Terms** dialog box, accept the terms and click **Next**.
-
-4. In the **Application Path** dialog box, select a location in which to install AGPM Client. Click **Next**.
-
-5. In the **AGPM Server** dialog box, type the fully-qualified computer name for the AGPM Server and the port to which to connect. The default port for the AGPM Service is 4600. Do not clear the **Allow Microsoft Management Console through the firewall** check box unless you manually configure port exceptions or use rules to configure port exceptions. Click **Next**.
-
-6. In the **Languages** dialog box, select one or more display languages to install for AGPM Client.
-
-7. Click **Install**, and then click **Finish** to exit the Setup Wizard.
-
-### Step 3: Configure an AGPM Server connection
-
-AGPM stores all versions of each controlled Group Policy object (GPO)—a GPO for which AGPM provides change control—in a central archive, so Group Policy administrators can view and modify GPOs offline without immediately impacting the deployed version of each GPO.
-
-In this step, you configure an AGPM Server connection and ensure that all Group Policy administrators connect to the same AGPM Server. (For information about configuring multiple AGPM Servers, see Help for Advanced Group Policy Management.)
-
-**To configure an AGPM Server connection for all Group Policy administrators**
-
-1. On a computer on which you have installed AGPM Client, log on with the user account that you selected as the Archive Owner. This user has the role of AGPM Administrator (Full Control).
-
-2. Click **Start**, point to **Administrative Tools**, and click **Group Policy Management** to open the GPMC.
-
-3. Edit a GPO that is applied to all Group Policy administrators.
-
-4. In the **Group Policy Management Editor** window, double-click **User Configuration**, **Policies**, **Administrative Templates**, **Windows Components**, and **AGPM**.
-
-5. In the details pane, double-click **AGPM: Specify default AGPM Server (all domains)**.
-
-6. In the **Properties** window, select **Enabled** and type the fully-qualified computer name and port (for example, **server.contoso.com:4600**) for the server hosting the archive. By default, the AGPM Service uses port 4600.
-
-7. Click **OK**, and then close the **Group Policy Management Editor** window. When Group Policy is updated, the AGPM Server connection is configured for each Group Policy administrator.
-
-### Step 4: Configure e-mail notification
-
-As an AGPM Administrator (Full Control), you designate the e-mail addresses of Approvers and AGPM Administrators to whom an e-mail message containing a request is sent when an Editor attempts to create, deploy, or delete a GPO. You also determine the alias from which these messages are sent.
-
-**To configure e-mail notification for AGPM**
-
-1. In the details pane, click the **Domain Delegation** tab.
-
-2. In the **From e-mail address** field, type the e-mail alias for AGPM from which notifications should be sent.
-
-3. In the **To e-mail address** field, type the e-mail address for the user account to which you intend to assign the Approver role.
-
-4. In the **SMTP server** field, type a valid SMTP mail server.
-
-5. In the **User name** and **Password** fields, type the credentials of a user with access to the SMTP service. Click **Apply**.
-
-### Step 5: Delegate access
-
-As an AGPM Administrator (Full Control), you delegate domain-level access to GPOs, assigning roles to the account of each Group Policy administrator.
-
-**Note**
-You can also delegate access at the GPO level rather than the domain level. For details, see Help for Advanced Group Policy Management.
-
-
-
-**Important**
-You should restrict membership in the Group Policy Creator Owners group, so it cannot be used to circumvent AGPM management of access to GPOs. (In the **Group Policy Management Console**, click **Group Policy Objects** in the forest and domain in which you want to manage GPOs, click **Delegation**, and then configure the settings to meet the needs of your organization.)
-
-
-
-**To delegate access to all GPOs throughout a domain**
-
-1. On the **Domain Delegation** tab, click the **Add** button, select the user account of the Group Policy administrator to serve as Approver, and then click **OK**.
-
-2. In the **Add Group or User** dialog box, select the **Approver** role to assign that role to the account, and then click **OK**. (This role includes the Reviewer role.)
-
-3. Click the **Add** button, select the user account of the Group Policy administrator to serve as Editor, and then click **OK**.
-
-4. In the **Add Group or User** dialog box, select the **Editor** role to assign that role to the account, and then click **OK**. (This role includes the Reviewer role.)
-
-5. Click the **Add** button, select the user account of the Group Policy administrator to serve as Reviewer, and then click **OK**.
-
-6. In the **Add Group or User** dialog box, select the **Reviewer** role to assign only that role to the account.
-
-## Steps for managing GPOs
-
-
-You must complete the following steps to create, edit, review, and deploy GPOs using AGPM. Additionally, you will create a template, delete a GPO, and restore a deleted GPO.
-
-[Step 1: Create a GPO](#bkmk-manage1)
-
-[Step 2: Edit a GPO](#bkmk-manage2)
-
-[Step 3: Review and deploy a GPO](#bkmk-manage3)
-
-[Step 4: Use a template to create a GPO](#bkmk-manage4)
-
-[Step 5: Delete and restore a GPO](#bkmk-manage5)
-
-### Step 1: Create a GPO
-
-In an environment with multiple Group Policy administrators, those with the Editor role have the ability to request the creation of new GPOs, but such a request must be approved by someone with the Approver role because the creation of a new GPO impacts the production environment.
-
-In this step, you use an account with the Editor role to request the creation of a new GPO. Using an account with the Approver role, you approve this request and complete the creation of a GPO.
-
-**To request the creation of a new GPO managed through AGPM**
-
-1. On a computer on which you have installed AGPM Client, log on with a user account that has been assigned the Editor role in AGPM.
-
-2. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-3. Right-click the **Change Control** node, and then click **New Controlled GPO**.
-
-4. In the **New Controlled GPO** dialog box:
-
- 1. To receive a copy of the request, type your e-mail address in the **Cc** field.
-
- 2. Type **MyGPO** as the name for the new GPO.
-
- 3. Type a comment for the new GPO.
-
- 4. Click **Create live** so the new GPO will be deployed to the production environment immediately upon approval. Click **Submit**.
-
-5. When the **AGPM Progress** window indicates that overall progress is complete, click **Close**. The new GPO is displayed on the **Pending** tab.
-
-**To approve the pending request to create a GPO**
-
-1. On a computer on which you have installed AGPM Client, log on with a user account that has been assigned the role of Approver in AGPM.
-
-2. Open the e-mail inbox for the account, and note that you have received an e-mail message from the AGPM alias with the Editor's request to create a GPO.
-
-3. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-4. On the **Contents** tab, click the **Pending** tab to display the pending GPOs.
-
-5. Right-click **MyGPO**, and then click **Approve**.
-
-6. Click **Yes** to confirm approval of the creation of the GPO. The GPO is moved to the **Controlled** tab.
-
-### Step 2: Edit a GPO
-
-You can use GPOs to configure computer or user settings and deploy them to many computers or users. In this step, you use an account with the Editor role to check out a GPO from the archive, edit the GPO offline, check the edited GPO into the archive, and request deployment of the GPO to the production environment. For this scenario, you configure a setting in the GPO to require that the password be at least eight characters in length.
-
-**To check the GPO out from the archive for editing**
-
-1. On a computer on which you have installed AGPM Client, log on with a user account that has been assigned the role of Editor in AGPM.
-
-2. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-3. On the **Contents** tab in the details pane, click the **Controlled** tab to display the controlled GPOs.
-
-4. Right-click **MyGPO**, and then click **Check Out**.
-
-5. Type a comment to be displayed in the history of the GPO while it is checked out, and then click **OK**.
-
-6. When the **AGPM Progress** window indicates that overall progress is complete, click **Close**. On the **Controlled** tab, the state of the GPO is identified as **Checked Out**.
-
-**To edit the GPO offline and configure the minimum password length**
-
-1. On the **Controlled** tab, right-click **MyGPO**, and then click **Edit** to open the **Group Policy Management Editor** window and make changes to an offline copy of the GPO. For this scenario, configure the minimum password length:
-
- 1. Under **Computer Configuration**, double-click **Policies**, **Windows Settings**, **Security Settings**, **Account Policies**, and **Password Policy**.
-
- 2. In the details pane, double-click **Minimum password length**.
-
- 3. In the properties window, select the **Define this policy setting** check box, set the number of characters to **8**, and then click **OK**.
-
-2. Close the **Group Policy Management Editor** window.
-
-**To check the GPO into the archive**
-
-1. On the **Controlled** tab, right-click **MyGPO** and then click **Check In**.
-
-2. Type a comment, and then click **OK**.
-
-3. When the **AGPM Progress** window indicates that overall progress is complete, click **Close**. On the **Controlled** tab, the state of the GPO is identified as **Checked In**.
-
-**To request the deployment of the GPO to the production environment**
-
-1. On the **Controlled** tab, right-click **MyGPO** and then click **Deploy**.
-
-2. Because this account is not an Approver or AGPM Administrator, you must submit a request for deployment. To receive a copy of the request, type your e-mail address in the **Cc** field. Type a comment to be displayed in the history of the GPO, and then click **Submit**.
-
-3. When the **AGPM Progress** window indicates that overall progress is complete, click **Close**. **MyGPO** is displayed on the list of GPOs on the **Pending** tab.
-
-### Step 3: Review and deploy a GPO
-
-In this step, you act as an Approver, creating reports and analyzing the settings and changes to settings in the GPO to determine whether you should approve them. After evaluating the GPO, you deploy it to the production environment and link it to a domain or an organizational unit (OU) so that it takes effect when Group Policy is refreshed for computers in that domain or OU.
-
-**To review settings in the GPO**
-
-1. On a computer on which you have installed AGPM Client, log on with a user account that has been assigned the role of Approver in AGPM. (Any Group Policy administrator with the Reviewer role, which is included in all of the other roles, can review the settings in a GPO.)
-
-2. Open the e-mail inbox for the account and note that you have received an e-mail message from the AGPM alias with an Editor's request to deploy a GPO.
-
-3. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-4. On the **Contents** tab in the details pane, click the **Pending** tab.
-
-5. Double-click **MyGPO** to display its history.
-
-6. Review the settings in the most recent version of MyGPO:
-
- 1. In the **History** window, right-click the GPO version with the most recent timestamp, click **Settings**, and then click **HTML Report** to display a summary of the GPO's settings.
-
- 2. In the Web browser, click **show all** to display all of the settings in the GPO. Close the browser.
-
-7. Compare the most recent version of MyGPO to the first version checked in to the archive:
-
- 1. In the **History** window, click the GPO version with the most recent time stamp. Press CTRL and click the oldest GPO version for which the **Computer Version** is not **\\***.
-
- 2. Click the **Differences** button. The **Account Policies/Password Policy** section is highlighted in green and preceded by **\[+\]**, indicating that this setting is configured only in the latter version of the GPO.
-
- 3. Click **Account Policies/Password Policy**. The **Minimum password length** setting is also highlighted in green and preceded by **\[+\]**, indicating that it is configured only in the latter version of the GPO.
-
- 4. Close the Web browser.
-
-**To deploy the GPO to the production environment**
-
-1. On the **Pending** tab, right-click **MyGPO** and then click **Approve**.
-
-2. Type a comment to include in the history of the GPO.
-
-3. Click **Yes**. When the **AGPM Progress** window indicates that overall progress is complete, click **Close**. The GPO is deployed to the production environment.
-
-**To link the GPO to a domain or organizational unit**
-
-1. In the GPMC, right-click the domain or an OU to which to apply the GPO that you configured, and then click **Link an Existing GPO**.
-
-2. In the **Select GPO** dialog box, click **MyGPO**, and then click **OK**.
-
-### Step 4: Use a template to create a GPO
-
-In this step, you use an account with the Editor role to create a template—an uneditable, static version of a GPO for use as a starting point for creating new GPOs—and then create a new GPO based upon that template. Templates are useful for quickly creating multiple GPOs that include many of the same settings.
-
-**To create a template based on an existing GPO**
-
-1. On a computer on which you have installed AGPM Client, log on with a user account that has been assigned the role of Editor in AGPM.
-
-2. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-3. On the **Contents** tab in the details pane, click the **Controlled** tab.
-
-4. Right-click **MyGPO**, and then click **Save as Template** to create a template incorporating all settings currently in MyGPO.
-
-5. Type **MyTemplate** as the name for the template and a comment, and then click **OK**.
-
-6. When the **AGPM Progress** window indicates that overall progress is complete, click **Close**. The new template appears on the **Templates** tab.
-
-**To request the creation of a new GPO managed through AGPM**
-
-1. Click the **Controlled** tab.
-
-2. Right-click the **Change Control** node, and then click **New Controlled GPO**.
-
-3. In the **New Controlled GPO** dialog box:
-
- 1. To receive a copy of the request, type your e-mail address in the **Cc** field.
-
- 2. Type **MyOtherGPO** as the name for the new GPO.
-
- 3. Type a comment for the new GPO.
-
- 4. Click **Create live**, so the new GPO will be deployed to the production environment immediately upon approval.
-
- 5. For **From GPO template**, select **MyTemplate**. Click **Submit**.
-
-4. When the **AGPM Progress** window indicates that overall progress is complete, click **Close**. The new GPO is displayed on the **Pending** tab.
-
-Use an account that has been assigned the role of Approver to approve the pending request to create the GPO as you did in [Step 1: Create a GPO](#bkmk-manage1). MyTemplate incorporates all of the settings that you configured in MyGPO. Because MyOtherGPO was created using MyTemplate, it initially contains all of the settings that MyGPO contained at the time that MyTemplate was created. You can confirm this by generating a difference report to compare MyOtherGPO to MyTemplate.
-
-**To check the GPO out from the archive for editing**
-
-1. On a computer on which you have installed AGPM Client, log on with a user account that has been assigned the role of Editor in AGPM.
-
-2. Right-click **MyOtherGPO**, and then click **Check Out**.
-
-3. Type a comment to be displayed in the history of the GPO while it is checked out, and then click **OK**.
-
-4. When the **AGPM Progress** window indicates that overall progress is complete, click **Close**. On the **Controlled** tab, the state of the GPO is identified as **Checked Out**.
-
-**To edit the GPO offline and configure the account lockout duration**
-
-1. On the **Controlled** tab, right-click **MyOtherGPO**, and then click **Edit** to open the **Group Policy Management Editor** window and make changes to an offline copy of the GPO. For this scenario, configure the minimum password length:
-
- 1. Under **Computer Configuration**, double-click **Policies**, **Windows Settings**, **Security Settings**, **Account Policies**, and **Account Lockout Policy**.
-
- 2. In the details pane, double-click **Account lockout duration**.
-
- 3. In the properties window, check **Define this policy setting**, set the duration to **30** minutes, and then click **OK**.
-
-2. Close the **Group Policy Management Editor** window.
-
-Check MyOtherGPO into the archive and request deployment as you did for MyGPO in [Step 2: Edit a GPO](#bkmk-manage2). You can compare MyOtherGPO to MyGPO or to MyTemplate using difference reports. Any account that includes the Reviewer role (AGPM Administrator \[Full Control\], Approver, Editor, or Reviewer) can generate reports.
-
-**To compare a GPO to another GPO and to a template**
-
-1. To compare MyGPO and MyOtherGPO:
-
- 1. On the **Controlled** tab, click **MyGPO**. Press CTRL and then click **MyOtherGPO**.
-
- 2. Right-click **MyOtherGPO**, point to **Differences**, and click **HTML Report**.
-
-2. To compare MyOtherGPO and MyTemplate:
-
- 1. On the **Controlled** tab, click **MyOtherGPO**.
-
- 2. Right-click **MyOtherGPO**, point to **Differences**, and click **Template**.
-
- 3. Select **MyTemplate** and **HTML Report**, and then click **OK**.
-
-### Step 5: Delete and restore a GPO
-
-In this step, you act as an Approver to delete a GPO.
-
-**To delete a GPO**
-
-1. On a computer on which you have installed AGPM Client, log on with a user account that has been assigned the role of Approver.
-
-2. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-3. On the **Contents** tab, click the **Controlled** tab to display the controlled GPOs.
-
-4. Right-click **MyGPO**, and then click **Delete**. Click **Delete GPO from archive and production** to delete both the version in the archive as well as the deployed version of the GPO in the production environment.
-
-5. Type a comment to be displayed in the audit trail for the GPO, and then click **OK**.
-
-6. When the **AGPM Progress** window indicates that overall progress is complete, click **Close**. The GPO is removed from the **Controlled** tab and is displayed on the **Recycle Bin** tab, where it can be restored or destroyed.
-
-Occasionally you may discover after deleting a GPO that it is still needed. In this step, you act as an Approver to restore a GPO that has been deleted.
-
-**To restore a deleted GPO**
-
-1. On the **Contents** tab, click the **Recycle Bin** tab to display deleted GPOs.
-
-2. Right-click **MyGPO**, and then click **Restore**.
-
-3. Type a comment to be displayed in the history of the GPO, and then click **OK**.
-
-4. When the **AGPM Progress** window indicates that overall progress is complete, click **Close**. The GPO is removed from the **Recycle Bin** tab and is displayed on the **Controlled** tab.
-
- **Note**
- Restoring a GPO to the archive does not automatically redeploy it to the production environment. To return the GPO to the production environment, deploy the GPO as in [Step 3: Review and deploy a GPO](#bkmk-manage3).
-
-
-
-After editing and deploying a GPO, you may discover that recent changes to the GPO are causing a problem. In this step, you act as an Approver to roll back to a previous version of the GPO. You can roll back to any version in the history of the GPO. You can use comments and labels to identify known good versions and when specific changes were made.
-
-**To roll back to a previous version of a GPO**
-
-1. On the **Contents** tab, click the **Controlled** tab to display the controlled GPOs.
-
-2. Double-click **MyGPO** to display its history.
-
-3. Right-click the version to be deployed, click **Deploy**, and then click **Yes**.
-
-4. When the **Progress** window indicates that overall progress is complete, click **Close**. In the **History** window, click **Close**.
-
- **Note**
- To verify that the version that has been redeployed is the version intended, examine a difference report for the two versions. In the **History** window for the GPO, select the two versions, right-click them, point to **Difference**, and then click either **HTML Report** or **XML Report**.
-
-
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/step-by-step-guide-for-microsoft-advanced-group-policy-management-40.md b/mdop/agpm/step-by-step-guide-for-microsoft-advanced-group-policy-management-40.md
deleted file mode 100644
index fa3516b9a3..0000000000
--- a/mdop/agpm/step-by-step-guide-for-microsoft-advanced-group-policy-management-40.md
+++ /dev/null
@@ -1,601 +0,0 @@
----
-title: Step-by-Step Guide for Microsoft Advanced Group Policy Management 4.0
-description: Step-by-Step Guide for Microsoft Advanced Group Policy Management 4.0
-author: dansimp
-ms.assetid: dc6f9b16-b1d4-48f3-88bb-f29301f0131c
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 08/30/2016
----
-
-
-# Step-by-Step Guide for Microsoft Advanced Group Policy Management 4.0
-
-
-This step-by-step guide demonstrates advanced techniques for Group Policy management that use the Group Policy Management Console (GPMC) and Microsoft Advanced Group Policy Management (AGPM). AGPM increases the capabilities of the GPMC, providing:
-
-- Standard roles for delegating permissions to manage Group Policy Objects (GPOs) to multiple Group Policy administrators, in addition to the ability to delegate access to GPOs in the production environment.
-
-- An archive to enable Group Policy administrators to create and modify GPOs offline before the GPOs are deployed into a production environment.
-
-- The ability to roll back to any earlier version of a GPO in the archive and to limit the number of versions stored in the archive.
-
-- Check-in and check-out capability for GPOs to make sure that Group Policy administrators do not unintentionally overwrite each other's work.
-
-- The ability to search for GPOs with specific attributes and to filter the list of GPOs displayed.
-
-## AGPM scenario overview
-
-
-For this scenario, you will use a separate user account for each role in AGPM to demonstrate how Group Policy can be managed in an environment that has multiple Group Policy administrators who have different levels of permissions. Specifically, you will perform the following tasks:
-
-- Using an account that is a member of the Domain Admins group, install AGPM Server and assign the AGPM Administrator role to an account or group.
-
-- Using accounts to which you will assign AGPM roles, install AGPM Client.
-
-- Using an account that has the AGPM Administrator role, configure AGPM and delegate access to GPOs by assigning roles to other accounts.
-
-- From an account that has the Editor role, request that a new GPO be created that you then approve by using an account that has the Approver role. Use the Editor account to check the GPO out of the archive, edit the GPO, check the GPO into the archive, and then request deployment.
-
-- Using an account that has the Approver role, review the GPO and deploy it to your production environment.
-
-- Using an account that has the Editor role, create a GPO template and use it as a starting point to create a new GPO.
-
-- Using an account that has the Approver role, delete and restore a GPO.
-
-
-
-## Requirements
-
-
-Computers on which you want to install AGPM must meet the following requirements, and you must create accounts for use in this scenario.
-
-**Note**
-If you have AGPM 2.5 installed and are upgrading from Windows Server® 2003 to Windows Server 2008 R2 or Windows Server 2008, or are upgrading from Windows Vista with no service packs installed to Windows 7 or Windows Vista® with Service Pack 1 (SP1), you must upgrade the operating system before you can upgrade to AGPM 4.0.
-
-If you have AGPM 3.0 installed, you do not have to upgrade the operating system before you upgrade to AGPM 4.0
-
-
-
-In a mixed environment that includes both newer and older operating systems, there are some limitations to functionality, as indicated in the following table.
-
-
-
-
-
-
-
-
-
-
Operating system on which AGPM Server 4.0 runs
-
Operating system on which AGPM Client 4.0 runs
-
Status of AGPM 4.0 support
-
-
-
-
-
Windows Server 2008 R2 or Windows 7
-
Windows Server 2008 R2 or Windows 7
-
Supported
-
-
-
Windows Server 2008 R2 or Windows 7
-
Windows Server 2008 or Windows Vista with SP1
-
Supported, but cannot edit policy settings or preference items that exist only in Windows Server 2008 R2 or Windows 7
-
-
-
Windows Server 2008 or Windows Vista with SP1
-
Windows Server 2008 R2 or Windows 7
-
Unsupported
-
-
-
Windows Server 2008 or Windows Vista with SP1
-
Windows Server 2008 or Windows Vista with SP1
-
Supported, but cannot report or edit policy settings or preference items that exist only in Windows Server 2008 R2 or Windows 7
-
-
-
-
-
-
-### AGPM Server requirements
-
-AGPM Server 4.0 requires Windows Server 2008 R2, Windows Server 2008, Windows 7 and the GPMC from Remote Server Administration Tools (RSAT), or Windows Vista with SP1 and the GPMC from RSAT installed. Both 32-bit and 64-bit versions are supported.
-
-Before you install AGPM Server, you must be a member of the Domain Admins group and the following Windows features must be present unless otherwise noted:
-
-- GPMC
-
- - Windows Server 2008 R2 or Windows Server 2008: If the GPMC is not present, it is automatically installed by AGPM.
-
- - Windows 7: You must install the GPMC from RSAT before you install AGPM. For more information, see [Remote Server Administration Tools for Windows 7](https://go.microsoft.com/fwlink/?LinkID=131280) (https://go.microsoft.com/fwlink/?LinkID=131280).
-
- - Windows Vista with SP1: You must install the GPMC from RSAT before you install AGPM. For more information, see [Remote Server Administration Tools for Windows Vista with Service Pack 1](https://go.microsoft.com/fwlink/?LinkID=116179) (https://go.microsoft.com/fwlink/?LinkID=116179).
-
-- The .NET Framework 3.5 or later versions
-
- - Windows Server 2008 R2 or Windows 7: If the .NET Framework 3.5 or later version is not present, the .NET Framework 3.5 is automatically installed by AGPM.
-
- - Windows Server 2008 or Windows Vista with SP1: You must install the .NET Framework 3.5 or a later version before you install AGPM.
-
-The following Windows features are required by AGPM Server and will be automatically installed if they are not present:
-
-- WCF Activation; Non-HTTP Activation
-
-- Windows Process Activation Service
-
- - Process Model
-
- - The .NET Environment
-
- - Configuration APIs
-
-### AGPM Client requirements
-
-AGPM Client 4.0 requires Windows Server 2008 R2, Windows Server 2008, Windows 7 and the GPMC from RSAT, or Windows Vista with SP1 and the GPMC from RSAT installed. Both 32-bit and 64-bit versions are supported. AGPM Client can be installed on a computer that is running AGPM Server.
-
-The following Windows features are required by AGPM Client and unless otherwise noted are automatically installed if they are not present:
-
-- GPMC
-
- - Windows Server 2008 R2 or Windows Server 2008: If the GPMC is not present, it is automatically installed by AGPM.
-
- - Windows 7: You must install the GPMC from RSAT before you install AGPM. For more information, see [Remote Server Administration Tools for Windows 7](https://go.microsoft.com/fwlink/?LinkID=131280) (https://go.microsoft.com/fwlink/?LinkID=131280).
-
- - Windows Vista with SP1: You must install the GPMC from RSAT before you install AGPM. For more information, see [Remote Server Administration Tools for Windows Vista with Service Pack 1](https://go.microsoft.com/fwlink/?LinkID=116179) (https://go.microsoft.com/fwlink/?LinkID=116179).
-
-- The .NET Framework 3.0 or later version
-
- - Windows Server 2008 R2 or Windows 7: If the .NET Framework 3.0 or later version is not present, the .NET Framework 3.5 is automatically installed by AGPM.
-
- - Windows Server 2008 or Windows Vista with SP1: If the .NET Framework 3.0 or later version is not present, the .NET Framework 3.0 is automatically installed by AGPM.
-
-### Scenario requirements
-
-Before you begin this scenario, create four user accounts. During the scenario, you will assign one of the following AGPM roles to each of these accounts: AGPM Administrator (Full Control), Approver, Editor, and Reviewer. These accounts must be able to send and receive e-mail messages. Assign **Link GPOs** permission to the accounts that have the AGPM Administrator, Approver, and (optionally) Editor roles.
-
-**Note**
-**Link GPOs** permission is assigned to members of Domain Administrators and Enterprise Administrators by default. To assign **Link GPOs** permission to additional users or groups (such as accounts that have the roles of AGPM Administrator or Approver), click the node for the domain and then click the **Delegation** tab, select **Link GPOs**, click **Add**, and select users or groups to which you want to assign the permission.
-
-
-
-## Steps for installing and configuring AGPM
-
-
-You must complete the following steps to install and configure AGPM.
-
-[Step 1: Install AGPM Server](#bkmk-config1)
-
-[Step 2: Install AGPM Client](#bkmk-config2)
-
-[Step 3: Configure an AGPM Server connection](#bkmk-config3)
-
-[Step 4: Configure e-mail notification](#bkmk-config4)
-
-[Step 5: Delegate access](#bkmk-config5)
-
-### Step 1: Install AGPM Server
-
-In this step, you install AGPM Server on the member server or domain controller that will run the AGPM Service, and you configure the archive. All AGPM operations are managed through this Windows service and are executed with the service's credentials. The archive managed by an AGPM Server can be hosted on that server or on another server in the same forest.
-
-**To install AGPM Server on the computer that will host the AGPM Service**
-
-1. Log on with an account that is a member of the Domain Admins group.
-
-2. Start the Microsoft Desktop Optimization Pack CD and follow the instructions on screen to select **Advanced Group Policy Management - Server**.
-
-3. In the **Welcome** dialog box, click **Next**.
-
-4. In the **Microsoft Software License Terms** dialog box, accept the terms and then click **Next**.
-
-5. In the **Application Path** dialog box, select a location in which to install AGPM Server. The computer on which AGPM Server is installed will host the AGPM Service and manage the archive. Click **Next**.
-
-6. In the **Archive Path** dialog box, select a location for the archive in relation to the AGPM Server. The archive path can point to a folder on the AGPM Server or elsewhere. However, you should select a location with sufficient space to store all GPOs and history data managed by this AGPM Server. Click **Next**.
-
-7. In the **AGPM Service Account** dialog box, select a service account under which the AGPM Service will run and then click **Next**.
-
- This account must be a member of the either the Domain Admins group or, for a least-privilege configuration, the following groups in each domain managed by the AGPM Server:
-
- - Group Policy Creator Owners
-
- - Backup Operators
-
- Additionally, this account requires Full Control permission for the following folders:
-
- - The AGPM archive folder, for which this permission is automatically granted during the installation of AGPM Server if it is installed on a local drive.
-
- - The local system temp folder, typically %windir%\\temp.
-
-8. In the **Archive Owner** dialog box, select an account or group to which you assign the AGPM Administrator (Full Control) role. AGPM Administrators can assign AGPM roles and permissions to other Group Policy administrators, so that later you can assign the role of AGPM Administrator to additional Group Policy administrators. For this scenario, select the account to serve in the AGPM Administrator role. Click **Next**.
-
-9. In the **Port Configuration** dialog box, type a port on which the AGPM Service should listen. Do not clear the **Add port exception to firewall** check box unless you manually configure port exceptions or use rules to configure port exceptions. Click **Next**.
-
-10. In the **Languages** dialog box, select one or more display languages to install for AGPM Server.
-
-11. Click **Install**, and then click **Finish** to exit the Setup Wizard.
-
- **Caution**
- Do not change settings for the AGPM Service through **Administrative Tools** and **Services** in the operating system. Doing this can prevent the AGPM Service from starting. For information about how to change settings for the service, see Help for Advanced Group Policy Management.
-
-
-
-### Step 2: Install AGPM Client
-
-Each Group Policy administrator—anyone who creates, edits, deploys, reviews, or deletes GPOs—must have AGPM Client installed on computers that they use to manage GPOs. The Change Control node, which you use to perform many of the GPO management tasks, appears in the Group Policy Management Console only if you install the AGPM Client. For this scenario, you install AGPM Client on at least one computer. You do not need to install AGPM Client on the computers of end users who do not perform Group Policy administration.
-
-**To install AGPM Client on the computer of a Group Policy administrator**
-
-1. Start the Microsoft Desktop Optimization Pack CD and follow the instructions on screen to select **Advanced Group Policy Management - Client**.
-
-2. In the **Welcome** dialog box, click **Next**.
-
-3. In the **Microsoft Software License Terms** dialog box, accept the terms and then click **Next**.
-
-4. In the **Application Path** dialog box, select a location in which to install AGPM Client. Click **Next**.
-
-5. In the **AGPM Server** dialog box, type the DNS name or IP address for the AGPM Server and the port to which you want to connect. The default port for the AGPM Service is 4600. Do not clear the **Allow Microsoft Management Console through the firewall** check box unless you manually configure port exceptions or use rules to configure port exceptions. Click **Next**.
-
-6. In the **Languages** dialog box, select one or more display languages to install for AGPM Client.
-
-7. Click **Install**, and then click **Finish** to exit the Setup Wizard.
-
-### Step 3: Configure an AGPM Server connection
-
-AGPM stores all versions of each controlled Group Policy Object (GPO), that is, each GPO for which AGPM provides change control, in a central archive. This lets Group Policy administrators view and change GPOs offline without immediately affecting the deployed version of each GPO.
-
-In this step, you configure an AGPM Server connection and ensure that all Group Policy administrators connect to the same AGPM Server. (For information about how to configure multiple AGPM Servers, see Help for Advanced Group Policy Management.)
-
-**To configure an AGPM Server connection for all Group Policy administrators**
-
-1. On a computer on which you have installed AGPM Client, log on with the user account that you selected as the Archive Owner. This user has the role of AGPM Administrator (Full Control).
-
-2. Click **Start**, point to **Administrative Tools**, and then click **Group Policy Management** to open the GPMC.
-
-3. Edit a GPO that is applied to all Group Policy administrators.
-
-4. In the **Group Policy Management Editor** window, double-click **User Configuration**, **Policies**, **Administrative Templates**, **Windows Components**, and **AGPM**.
-
-5. In the details pane, double-click **AGPM: Specify default AGPM Server (all domains)**.
-
-6. In the **Properties** window, select **Enabled** and type the DNS name or IP address and port (for example, **server.contoso.com:4600**) for the server hosting the archive. By default, the AGPM Service uses port 4600.
-
-7. Click **OK**, and then close the **Group Policy Management Editor** window. When Group Policy is updated, the AGPM Server connection is configured for each Group Policy administrator.
-
-### Step 4: Configure e-mail notification
-
-As an AGPM Administrator (Full Control), you designate the e-mail addresses of Approvers and AGPM Administrators to whom an e-mail message that contains a request is sent when an Editor tries to create, deploy, or delete a GPO. You also determine the alias from which these messages are sent.
-
-**To configure e-mail notification for AGPM**
-
-1. In **Group Policy Management Editor** , navigate to the **Change Control** folder
-
-2. In the details pane, click the **Domain Delegation** tab.
-
-3. In the **From e-mail address** field, type the e-mail alias for AGPM from which notifications should be sent.
-
-4. In the **To e-mail address** field, type the e-mail address for the user account to which you intend to assign the Approver role.
-
-5. In the **SMTP server** field, type a valid SMTP mail server.
-
-6. In the **User name** and **Password** fields, type the credentials of a user who has access to the SMTP service. Click **Apply**.
-
-### Step 5: Delegate access
-
-As an AGPM Administrator (Full Control), you delegate domain-level access to GPOs, assigning roles to the account of each Group Policy administrator.
-
-**Note**
-You can also delegate access at the GPO level instead of the domain level. For more information, see Help for Advanced Group Policy Management.
-
-
-
-**Important**
-You should restrict membership in the Group Policy Creator Owners group so that it cannot be used to circumvent AGPM management of access to GPOs. (In the **Group Policy Management Console**, click **Group Policy Objects** in the forest and domain in which you want to manage GPOs, click **Delegation**, and then configure the settings to meet the needs of your organization.)
-
-
-
-**To delegate access to all GPOs throughout a domain**
-
-1. On the **Domain Delegation** tab, click the **Add** button, select the user account of the Group Policy administrator to serve as Approver, and then click **OK**.
-
-2. In the **Add Group or User** dialog box, select the **Approver** role to assign that role to the account, and then click **OK**. (This role includes the Reviewer role.)
-
-3. Click the **Add** button, select the user account of the Group Policy administrator to serve as Editor, and then click **OK**.
-
-4. In the **Add Group or User** dialog box, select the **Editor** role to assign that role to the account, and then click **OK**. (This role includes the Reviewer role.)
-
-5. Click the **Add** button, select the user account of the Group Policy administrator to serve as Reviewer, and then click **OK**.
-
-6. In the **Add Group or User** dialog box, select the **Reviewer** role to assign only that role to the account.
-
-## Steps for managing GPOs
-
-
-You must complete the following steps to create, edit, review, and deploy GPOs by using AGPM. Additionally, you will create a template, delete a GPO, and restore a deleted GPO.
-
-[Step 1: Create a GPO](#bkmk-manage1)
-
-[Step 2: Edit a GPO](#bkmk-manage2)
-
-[Step 3: Review and deploy a GPO](#bkmk-manage3)
-
-[Step 4: Use a template to create a GPO](#bkmk-manage4)
-
-[Step 5: Delete and restore a GPO](#bkmk-manage5)
-
-### Step 1: Create a GPO
-
-In an environment that has multiple Group Policy administrators, those with the Editor role can request that new GPOs be created. However, that request must be approved by someone with the Approver role.
-
-In this step, you use an account that has the Editor role to request that a new GPO be created. Using an account that has the Approver role, you approve this request to create the GPO.
-
-**To request that a new GPO be created and managed through AGPM**
-
-1. On a computer on which you have installed AGPM Client, log on with a user account that is assigned the Editor role in AGPM.
-
-2. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-3. Right-click the **Change Control** node, and then click **New Controlled GPO**.
-
-4. In the **New Controlled GPO** dialog box:
-
- 1. To receive a copy of the request, type your e-mail address in the **Cc** field.
-
- 2. Type **MyGPO** as the name for the new GPO.
-
- 3. Type a comment for the new GPO.
-
- 4. Click **Create live** so that the new GPO will be deployed to the production environment immediately upon approval. Click **Submit**.
-
-5. When the **AGPM Progress** window indicates that overall progress is complete, click **Close**. The new GPO is displayed on the **Pending** tab.
-
-**To approve the pending request to create a GPO**
-
-1. On a computer on which you have installed AGPM Client, log on with a user account that has the role of Approver in AGPM.
-
-2. Open the e-mail inbox for the account, and notice that you have received an e-mail message from the AGPM alias with the Editor's request to create a GPO.
-
-3. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-4. On the **Contents** tab, click the **Pending** tab to display the pending GPOs.
-
-5. Right-click **MyGPO**, and then click **Approve**.
-
-6. Click **Yes** to confirm approval and move the GPO to the **Controlled** tab.
-
-### Step 2: Edit a GPO
-
-You can use GPOs to configure computer or user settings and deploy them to many computers or users. In this step, you use an account that has the Editor role to check out a GPO from the archive, edit the GPO offline, check the edited GPO into the archive, and request deployment of the GPO to the production environment. For this scenario, you configure a setting in the GPO to require that the password be at least eight characters long.
-
-**To check the GPO out from the archive for editing**
-
-1. On a computer on which you have installed AGPM Client, log on with a user account that has the role of Editor in AGPM.
-
-2. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-3. On the **Contents** tab in the details pane, click the **Controlled** tab to display the controlled GPOs.
-
-4. Right-click **MyGPO**, and then click **Check Out**.
-
-5. Type a comment to be displayed in the history of the GPO while it is checked out, and then click **OK**.
-
-6. When the **AGPM Progress** window indicates that overall progress is complete, click **Close**. On the **Controlled** tab, the state of the GPO is identified as **Checked Out**.
-
-**To edit the GPO offline and configure the minimum password length**
-
-1. On the **Controlled** tab, right-click **MyGPO**, and then click **Edit** to open the **Group Policy Management Editor** window and change an offline copy of the GPO. For this scenario, configure the minimum password length:
-
- 1. Under **Computer Configuration**, double-click **Policies**, **Windows Settings**, **Security Settings**, **Account Policies**, and **Password Policy**.
-
- 2. In the details pane, double-click **Minimum password length**.
-
- 3. In the properties window, select the **Define this policy setting** check box, set the number of characters to **8**, and then click **OK**.
-
-2. Close the **Group Policy Management Editor** window.
-
-**To check the GPO into the archive**
-
-1. On the **Controlled** tab, right-click **MyGPO** and then click **Check In**.
-
-2. Type a comment, and then click **OK**.
-
-3. When the **AGPM Progress** window indicates that overall progress is complete, click **Close**. On the **Controlled** tab, the state of the GPO is identified as **Checked In**.
-
-**To request the deployment of the GPO to the production environment**
-
-1. On the **Controlled** tab, right-click **MyGPO** and then click **Deploy**.
-
-2. Because this account is not an Approver or AGPM Administrator, you must submit a request for deployment. To receive a copy of the request, type your e-mail address in the **Cc** field. Type a comment to be displayed in the history of the GPO, and then click **Submit**.
-
-3. When the **AGPM Progress** window indicates that overall progress is complete, click **Close**. **MyGPO** is displayed on the list of GPOs on the **Pending** tab.
-
-### Step 3: Review and deploy a GPO
-
-In this step, you act as an Approver, creating reports and analyzing the settings and changes to settings in the GPO to determine whether you should approve them. After you evaluate the GPO, you deploy it to the production environment and link the GPO to a domain or an organizational unit (OU). The GPO takes effect when Group Policy is refreshed for computers in that domain or OU.
-
-**To review settings in the GPO**
-
-1. On a computer on which you have installed AGPM Client, log on with a user account that is assigned the role of Approver in AGPM. Any Group Policy administrator with the Reviewer role, which is included in all of the other roles, can review the settings in a GPO.
-
-2. Open the e-mail inbox for the account and notice that you have received an e-mail message from the AGPM alias with an Editor's request to deploy a GPO.
-
-3. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-4. On the **Contents** tab in the details pane, click the **Pending** tab.
-
-5. Double-click **MyGPO** to display its history.
-
-6. Review the settings in the most recent version of MyGPO:
-
- 1. In the **History** window, right-click the GPO version with the most recent time stamp, click **Settings**, and then click **HTML Report** to display a summary of the GPO's settings.
-
- 2. In the Web browser, click **show all** to display all the settings in the GPO. Close the browser.
-
-7. Compare the most recent version of MyGPO to the first version checked in to the archive:
-
- 1. In the **History** window, click the GPO version with the most recent time stamp. Press CTRL and then click the oldest GPO version for which the **Computer Version** is not **\\***.
-
- 2. Click the **Differences** button. The **Account Policies/Password Policy** section is highlighted in green and preceded by **\[+\]**. This indicates that the setting is configured only in the latter version of the GPO.
-
- 3. Click **Account Policies/Password Policy**. The **Minimum password length** setting is also highlighted in green and preceded by **\[+\]**, indicating that it is configured only in the latter version of the GPO.
-
- 4. Close the Web browser.
-
-**To deploy the GPO to the production environment**
-
-1. On the **Pending** tab, right-click **MyGPO** and then click **Approve**.
-
-2. Type a comment to include in the history of the GPO.
-
-3. Click **Yes**. When the **AGPM Progress** window indicates that overall progress is complete, click **Close**. The GPO is deployed to the production environment.
-
-**To link the GPO to a domain or organizational unit**
-
-1. In the GPMC, right-click either the domain or an organizational unit (OU) to which you want to apply the GPO that you configured, and then click **Link an Existing GPO**.
-
-2. In the **Select GPO** dialog box, click **MyGPO**, and then click **OK**.
-
-### Step 4: Use a template to create a GPO
-
-In this step, you use an account that has the Editor role to create and use a template. That template is a static version of a GPO for use as a starting point for creating new GPOs. Although you cannot edit a template, you can create a new GPO based on a template. Templates are useful for quickly creating multiple GPOs that include many of the same policy settings.
-
-**To create a template based on an existing GPO**
-
-1. On a computer on which you have installed AGPM Client, log on with a user account that is assigned the role of Editor in AGPM.
-
-2. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-3. On the **Contents** tab in the details pane, click the **Controlled** tab.
-
-4. Right-click **MyGPO**, and then click **Save as Template** to create a template incorporating all settings currently in MyGPO.
-
-5. Type **MyTemplate** as the name for the template and a comment, and then click **OK**.
-
-6. When the **AGPM Progress** window indicates that overall progress is complete, click **Close**. The new template appears on the **Templates** tab.
-
-**To request that a new GPO be created and managed through AGPM**
-
-1. Click the **Controlled** tab.
-
-2. Right-click the **Change Control** node, and then click **New Controlled GPO**.
-
-3. In the **New Controlled GPO** dialog box:
-
- 1. To receive a copy of the request, type your e-mail address in the **Cc** field.
-
- 2. Type **MyOtherGPO** as the name for the new GPO.
-
- 3. Type a comment for the new GPO.
-
- 4. Click **Create live** so that the new GPO will be deployed to the production environment immediately upon approval.
-
- 5. For **From GPO template**, select **MyTemplate**. Click **Submit**.
-
-4. When the **AGPM Progress** window indicates that overall progress is complete, click **Close**. The new GPO is displayed on the **Pending** tab.
-
-Use an account that is assigned the role of Approver to approve the pending request to create the GPO as you did in [Step 1: Create a GPO](#bkmk-manage1). MyTemplate incorporates all the settings that you configured in MyGPO. Because MyOtherGPO was created using MyTemplate, it at first contains all the settings that MyGPO contained at the time that MyTemplate was created. You can confirm this by generating a difference report to compare MyOtherGPO to MyTemplate.
-
-**To check the GPO out from the archive for editing**
-
-1. On a computer on which you have installed AGPM Client, log on with a user account that is assigned the role of Editor in AGPM.
-
-2. Right-click **MyOtherGPO**, and then click **Check Out**.
-
-3. Type a comment to be displayed in the history of the GPO while it is checked out, and then click **OK**.
-
-4. When the **AGPM Progress** window indicates that overall progress is complete, click **Close**. On the **Controlled** tab, the state of the GPO is identified as **Checked Out**.
-
-**To edit the GPO offline and configure the account lockout duration**
-
-1. On the **Controlled** tab, right-click **MyOtherGPO**, and then click **Edit** to open the **Group Policy Management Editor** window and change an offline copy of the GPO. For this scenario, configure the minimum password length:
-
- 1. Under **Computer Configuration**, double-click **Policies**, **Windows Settings**, **Security Settings**, **Account Policies**, and **Account Lockout Policy**.
-
- 2. In the details pane, double-click **Account lockout duration**.
-
- 3. In the properties window, check **Define this policy setting**, set the duration to **30** minutes, and then click **OK**.
-
-2. Close the **Group Policy Management Editor** window.
-
-Check MyOtherGPO into the archive and request deployment as you did for MyGPO in [Step 2: Edit a GPO](#bkmk-manage2). You can compare MyOtherGPO to MyGPO or to MyTemplate by using difference reports. Any account that includes the Reviewer role (AGPM Administrator \[Full Control\], Approver, Editor, or Reviewer) can generate reports.
-
-**To compare a GPO to another GPO and to a template**
-
-1. To compare MyGPO and MyOtherGPO:
-
- 1. On the **Controlled** tab, click **MyGPO**. Press CTRL and then click **MyOtherGPO**.
-
- 2. Right-click **MyOtherGPO**, point to **Differences**, and then click **HTML Report**.
-
-2. To compare MyOtherGPO and MyTemplate:
-
- 1. On the **Controlled** tab, click **MyOtherGPO**.
-
- 2. Right-click **MyOtherGPO**, point to **Differences**, and then click **Template**.
-
- 3. Select **MyTemplate** and **HTML Report**, and then click **OK**.
-
-### Step 5: Delete and restore a GPO
-
-In this step, you act as an Approver to delete a GPO.
-
-**To delete a GPO**
-
-1. On a computer on which you have installed AGPM Client, log on with a user account that is assigned the role of Approver.
-
-2. In the **Group Policy Management Console** tree, click **Change Control** in the forest and domain in which you want to manage GPOs.
-
-3. On the **Contents** tab, click the **Controlled** tab to display the controlled GPOs.
-
-4. Right-click **MyGPO**, and then click **Delete**. Click **Delete GPO from archive and production** to delete both the version in the archive and the deployed version of the GPO in the production environment.
-
-5. Type a comment to be displayed in the audit trail for the GPO, and then click **OK**.
-
-6. When the **AGPM Progress** window indicates that overall progress is complete, click **Close**. The GPO is removed from the **Controlled** tab and is displayed on the **Recycle Bin** tab, where it can be restored or destroyed.
-
-Occasionally you may discover after you delete a GPO that it is still needed. In this step, you act as an Approver to restore a GPO that was deleted.
-
-**To restore a deleted GPO**
-
-1. On the **Contents** tab, click the **Recycle Bin** tab to display deleted GPOs.
-
-2. Right-click **MyGPO**, and then click **Restore**.
-
-3. Type a comment to be displayed in the history of the GPO, and then click **OK**.
-
-4. When the **AGPM Progress** window indicates that overall progress is complete, click **Close**. The GPO is removed from the **Recycle Bin** tab and is displayed on the **Controlled** tab.
-
- **Note**
- Restoring a GPO to the archive does not automatically redeploy it to the production environment. To return the GPO to the production environment, deploy the GPO as in [Step 3: Review and deploy a GPO](#bkmk-manage3).
-
-
-
-After editing and deploying a GPO, you may discover that recent changes to the GPO are causing a problem. In this step, you act as an Approver to roll back to an earlier version of the GPO. You can roll back to any version in the history of the GPO. You can use comments and labels to identify known good versions and when specific changes were made.
-
-**To roll back to an earlier version of a GPO**
-
-1. On the **Contents** tab, click the **Controlled** tab to display the controlled GPOs.
-
-2. Double-click **MyGPO** to display its history.
-
-3. Right-click the version to be deployed, click **Deploy**, and then click **Yes**.
-
-4. When the **Progress** window indicates that overall progress is complete, click **Close**. In the **History** window, click **Close**.
-
- **Note**
- To verify that the version that was redeployed is the version intended, examine a difference report for the two versions. In the **History** window for the GPO, select the two versions, right-click them, point to **Difference**, and then click either **HTML Report** or **XML Report**.
-
-
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/technical-overview-of-agpm.md b/mdop/agpm/technical-overview-of-agpm.md
deleted file mode 100644
index 3ea90686e5..0000000000
--- a/mdop/agpm/technical-overview-of-agpm.md
+++ /dev/null
@@ -1,284 +0,0 @@
----
-title: Technical Overview of AGPM
-description: Technical Overview of AGPM
-author: dansimp
-ms.assetid: 36bc0ab5-f752-474c-8559-721ea95169c2
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 08/30/2016
----
-
-
-# Technical Overview of AGPM
-
-
-Microsoft Advanced Group Policy Management (AGPM) is a client/server application. The AGPM Server stores Group Policy Objects (GPOs) offline in the archive that AGPM creates on the server's file system. Group Policy administrators use the AGPM snap-in for the Group Policy Management Console (GPMC) to work with GPOs on the server that hosts the archive. Understanding the parts of AGPM and related items, how they store GPOs in the file system, and how permissions control the actions available to each user role can improve Group Policy administrators' effectiveness with AGPM.
-
-## Terminology
-
-
-The following explains the basic AGPM terms.
-
-- **AGPM Client:** A computer that runs the AGPM snap-in for the Group Policy Management Console (GPMC) and from which Group Policy administrators manage GPOs.
-
-- **AGPM snap-in:** The software component of AGPM installed on AGPM Clients so that they can manage GPOs.
-
-- **AGPM Server:** A server that runs the AGPM Service and manages an archive. Each AGPM Server can manage only one archive, but one AGPM Server can manage archive data for multiple domains in one archive. An archive can be hosted on a computer other than an AGPM Server.
-
-- **AGPM Service:** The software component of AGPM that runs on an AGPM Server as a service. The service manages GPOs in the archive and in the production environment in that forest.
-
-- **Archive:** In AGPM, a central store that contains the controlled GPOs that the associated AGPM Server manages, in addition to the history for each of those GPOs. This includes all previous controlled versions of each GPO. An archive consists of an archive index file and associated archive data that may include data for GPOs in multiple domains. An archive can be hosted on a computer other than an AGPM Server.
-
-- **Controlled GPO:** A GPO that is being managed by AGPM. AGPM manages the history and permissions of controlled GPOs, which it stores in the archive.
-
-- **Uncontrolled GPO:** A GPO in the production environment for a domain and not managed by AGPM.
-
-## What AGPM installs, creates, and affects
-
-
-On an AGPM Server, the AGPM Setup program installs the AGPM Service. AGPM does not alter the Active Directory® directory service or the schema. By default, the AGPM Server program files are installed in %ProgramFiles%\\Microsoft\\AGPM\\Server. You can install the AGPM Service on a domain controller if you have to; however, we recommend that you install the AGPM Service on a member server.
-
-On an AGPM Client, the AGPM Setup program installs the AGPM snap-in, adding a **Change Control** folder to each domain that appears in the GPMC. By default, the AGPM Client program files are installed in %ProgramFiles%\\Microsoft\\AGPM\\Client.
-
-Table 1 describes both the items that AGPM installs or creates and the parts of the operating system that affect AGPM operation.
-
-**Table 1: Items installed, created, or affected by AGPM**
-
-
-
-
-
-
-
-
-
Item
-
Description
-
-
-
-
-
AGPM Service
-
The AGPM Service runs on the AGPM Server. The service manages the archive, which contains offline GPOs, and controlled GPOs in the production environment. The default configuration of the AGPM Service is as follows:
-
-
Service name: AGPM Service
-
Display name: AGPM Service
-
Path to executable: %ProgramFiles%\Microsoft\AGPM\Server\Agpm.exe
-
Startup: Automatic
-
Log on as: AGPM Service Account specified during installation of AGPM Server, which can be changed using Programs and Features in the Control Panel.
-
-
-
-
AGPM archive
-
By default, AGPM creates the archive in %ProgramData%\Microsoft\AGPM on the AGPM Server. The archive provides storage for offline GPOs, and it can store multiple versions of each GPO. Changes that AGPM makes to GPOs in the archive do not affect the production environment until an AGPM Administrator or Approver deploys the GPO to the production environment and links the GPO to an organizational unit (OU).
-
-
-
Windows Firewall
-
During installation, AGPM enables an inbound Windows Firewall rule that allows the AGPM Client to communicate with the AGPM Server. The default Windows Firewall rule is the following:
-
-
Name: AGPM Service
-
Action: Allow the connection
-
Programs: All programs that meet the specified conditions
-
Protocol type: TCP
-
Local port: 4600
-
Remote port: All ports
-
Local IP address: Any
-
Remote IP address: Any
-
-
-
-
E-mail server
-
AGPM uses Simple Mail Transfer Protocol (SMTP) to send e-mail requests to the addresses configured on the Domain Delegation tab. For example, when an Editor requests that a new GPO be created, AGPM notifies each e-mail address specified on the Domain Delegation tab.
-
-
-
AGPM snap-in
-
The AGPM snap-in for the GPMC runs on AGPM Clients and is used by Group Policy administrators to manage GPOs. The snap-in appears in the GPMC as a Change Control folder in each domain.
-
-
-
-
-
-
-### Additional references
-
-For more information about the files installed by AGPM, see the [Planning Guide for AGPM](https://go.microsoft.com/fwlink/?LinkId=160060).
-
-## Archive
-
-
-By default, the AGPM Server installation process creates the archive on the local hard disk of the AGPM Server at %ProgramData%\\Microsoft\\AGPM. However, you can change the path during installation and even create the archive on a server other than the AGPM Server.
-
-The archive contains a subfolder for each version of each GPO the archive contains. The name of each subfolder is a GUID that identifies a version of the GPO.
-
-The gpostate.xml file records the state of each GPO in the archive. The file is a manifest that describes the contents of the archive. For example, a GPO can have many versions, and each version is in its own subfolder in the archive. The gpostate.xml file indicates which subfolders contain different versions of a single GPO. Additionally, GPO templates have subfolders in the archive, but gpostate.xml indicates that these are templates and not controlled GPOs. Similarly, when Group Policy administrators delete GPOs, AGPM changes their states in gpostate.xml to indicate that they are in the **Recycle Bin** but does not actually remove the GPOs' subfolders from the archive.
-
-**Caution**
-Do not manually edit gpostate.xml or the GPOs the archive contains. This information is provided only to enhance understanding of the AGPM archive. Instead, use the AGPM snap-in to change GPOs.
-
-
-
-When AGPM creates the archive, it gives Full Control to SYSTEM, Administrators, and the AGPM Service Account (specified in the setup of AGPM Server). Changing permissions by using the AGPM user interface on the AGPM snap-in does not alter permissions on the archive, because the AGPM Service Account performs all operations on behalf of the logged-on user.
-
-### Additional references
-
-For information about how to back up the archive, restore the archive from a backup, or move both the AGPM Server and the archive, see the "Performing AGPM Administrator Tasks" section in the [Operations Guide for AGPM](https://go.microsoft.com/fwlink/?LinkId=160061).
-
-## Roles and permissions
-
-
-Roles simplify delegation. Instead of assigning detailed permissions to Group Policy administrators, AGPM Administrators can assign one of four roles to Group Policy administrators to let them perform work related to that role:
-
-- **AGPM Administrator:** Group Policy administrators assigned the AGPM Administrator (Full Control) role can perform any task in AGPM. AGPM Administrators can configure domain-wide options and delegate permissions to other Group Policy administrators.
-
-- **Approver:** Group Policy administrators assigned the Approver role can deploy GPOs to the production environment for a domain. Approvers can also create and delete GPOs and approve or reject requests from Editors. Approvers can view the list of GPOs in a domain, view the policy settings in GPOs, and create and view reports of the policy settings in a GPO. They cannot edit the policy settings in GPOs unless they are also assigned the Editor role.
-
-- **Editor:** Group Policy administrators assigned the Editor role can view the list of GPOs in a domain, view the policy settings in GPOs, edit the policy settings in GPOs, and create and view reports of the policy settings in a GPO. Unless they are also assigned the Approver role, Editors cannot create, deploy, or delete GPOs. However, they can request that GPOs be created, deployed, or deleted.
-
-- **Reviewer:** Group Policy administrators assigned the Reviewer role can view the list of GPOs in a domain and create and view reports of the policy settings in a GPO. Unless they are also assigned the Editor role, they cannot edit policy settings in a GPO.
-
-AGPM gives AGPM Administrators the flexibility to configure permissions at a more detailed level than roles by using the AGPM snap-in. Table 2 describes these permissions and indicates the permissions granted to each role by default.
-
-
-
-
-
-
-
-
-
-
-
-
-
Permission
-
Description
-
AGPM Administrator
-
Approver
-
Editor
-
Reviewer
-
-
-
-
-
Full Control
-
Have all permissions.
-
Yes
-
-
-
-
-
-
Create GPO
-
Create GPOs in a domain.
-
Yes
-
Yes
-
-
-
-
-
List Contents
-
List the GPOs in a domain.
-
Yes
-
Yes
-
Yes
-
Yes
-
-
-
Read Settings
-
Read the policy settings within a GPO.
-
Yes
-
Yes
-
Yes
-
Yes
-
-
-
Edit Settings
-
Change the policy settings in a GPO.
-
Yes
-
-
Yes
-
-
-
-
Delete GPO
-
Delete a GPO.
-
Yes
-
Yes
-
-
-
-
-
Modify Security
-
Delegate domain-level access, delegate access to a single GPO, and delegate access to the production environment.
-
Yes
-
-
-
-
-
-
Deploy GPO
-
Deploy a GPO from the archive to the production environment.
-
Yes
-
Yes
-
-
-
-
-
Create Template
-
Create a GPO template in AGPM.
-
Yes
-
-
Yes
-
-
-
-
Modify Options
-
Configure AGPM e-mail notification and limit the GPO versions stored in the archive.
-
Yes
-
-
-
-
-
-
Export GPO
-
Export a GPO to a file.
-
Yes
-
-
Yes
-
-
-
-
Import GPO
-
Import a GPO from a file.
-
Yes
-
-
Yes
-
-
-
-
-
-
-
-**Note**
-**Export GPO** and **Import GPO** permissions are not available in AGPM 3.0 or 2.5.
-
-The ability to delegate access to GPOs in the production environment for a domain and the ability to limit the number of GPO versions stored are not available in AGPM 2.5.
-
-
-
-### Additional references
-
-For information about what tasks can be performed by Group Policy administrators assigned a particular role or about which permissions are required to perform a specific task, see the [Operations Guide for AGPM](https://go.microsoft.com/fwlink/?LinkId=160061).
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/template-commands-agpm30ops.md b/mdop/agpm/template-commands-agpm30ops.md
deleted file mode 100644
index cd6beac689..0000000000
--- a/mdop/agpm/template-commands-agpm30ops.md
+++ /dev/null
@@ -1,164 +0,0 @@
----
-title: Template Commands
-description: Template Commands
-author: dansimp
-ms.assetid: 2ec11b3f-0c5c-4788-97bd-bd4bf64ba51a
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Template Commands
-
-
-The **Templates** tab:
-
-- Displays a list of available templates that you can use to create new Group Policy Objects (GPOs).
-
-- Provides a shortcut menu with commands for creating a GPO based on a selected template, managing templates, and displaying reports for templates.
-
-- Displays a list of the groups and users who have permission to access a selected template.
-
-Because a template cannot be altered, templates have no history. However, like any GPO version, the settings of a template can be displayed with a settings report or compared to another GPO with a difference report.
-
-**Note**
-A template is an uneditable, static version of a GPO for use as a starting point for creating new, editable GPOs.
-
-
-
-Right-clicking the **Group Policy Objects** list on this tab displays a shortcut menu, including whichever of the following options are applicable.
-
-## Control
-
-
-
-
-
-
-
-
-
-
Command
-
Effect
-
-
-
-
-
New Controlled GPO
-
Create a new GPO based on the selected template. The option to deploy the new GPO to the production environment is provided. If you do not have permission to create a GPO, you will be prompted to submit a request. (This option is displayed if no GPO is selected when right-clicking in the Group Policy Objects list.)
-
-
-
-
-
-
-## Reports
-
-
-
-
-
-
-
-
-
-
Command
-
Effect
-
-
-
-
-
Settings
-
Generate an HTML-based or XML-based report displaying the settings within the selected GPO.
-
-
-
Differences
-
Generate an HTML-based or XML-based report comparing the settings within two selected GPO templates.
-
-
-
-
-
-
-## Template management
-
-
-
-
-
-
-
-
-
-
Command
-
Effect
-
-
-
-
-
Set as Default
-
Set the selected template as the default to be used automatically when creating a new GPO.
-
-
-
Delete
-
Move the selected template to the Recycle Bin. If you do not have permission to delete a GPO, you will be prompted to submit a request.
-
-
-
Rename
-
Change the name of the selected template.
-
-
-
-
-
-
-## Miscellaneous
-
-
-
-
-
-
-
-
-
-
Command
-
Effect
-
-
-
-
-
Refresh
-
Update the display of the Group Policy Management Console to incorporate any changes. Some changes are not visible until the display is refreshed.
-
-
-
Help
-
Display help for Advanced Group Policy Management (AGPM).
-
-
-
-
-
-
-### Additional references
-
-- [Contents Tab](contents-tab-agpm30ops.md)
-
-- [Performing Editor Tasks](performing-editor-tasks-agpm30ops.md)
-
-- [Performing Reviewer Tasks](performing-reviewer-tasks-agpm30ops.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/template-commands-agpm40.md b/mdop/agpm/template-commands-agpm40.md
deleted file mode 100644
index ad999f7a40..0000000000
--- a/mdop/agpm/template-commands-agpm40.md
+++ /dev/null
@@ -1,164 +0,0 @@
----
-title: Template Commands
-description: Template Commands
-author: dansimp
-ms.assetid: 243a9b18-bf3f-44fa-94d7-5c793f7322da
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Template Commands
-
-
-The **Templates** tab:
-
-- Displays a list of available templates that you can use to create new Group Policy Objects (GPOs).
-
-- Provides a shortcut menu with commands for creating a GPO based on a selected template, managing templates, and displaying reports for templates.
-
-- Displays a list of the groups and users who have permission to access a selected template.
-
-Because a template cannot be altered, templates have no history. However, like any GPO version, the settings of a template can be displayed with a settings report or compared to another GPO with a difference report.
-
-**Note**
-A template is an uneditable, static version of a GPO for use as a starting point for creating new, editable GPOs.
-
-
-
-Right-clicking the **Group Policy Objects** list on this tab displays a shortcut menu, including whichever of the following options are applicable.
-
-## Control
-
-
-
-
-
-
-
-
-
-
Command
-
Effect
-
-
-
-
-
New Controlled GPO
-
Create a new GPO based on the selected template. The option to deploy the new GPO to the production environment of the domain is provided. If you do not have permission to create a GPO, you will be prompted to submit a request. (This option is displayed if no GPO is selected when right-clicking in the Group Policy Objects list.)
-
-
-
-
-
-
-## Reports
-
-
-
-
-
-
-
-
-
-
Command
-
Effect
-
-
-
-
-
Settings
-
Generate an HTML-based or XML-based report displaying the settings within the selected GPO.
-
-
-
Differences
-
Generate an HTML-based or XML-based report comparing the settings within two selected GPO templates.
-
-
-
-
-
-
-## Template management
-
-
-
-
-
-
-
-
-
-
Command
-
Effect
-
-
-
-
-
Set as Default
-
Set the selected template as the default to be used automatically when creating a new GPO.
-
-
-
Delete
-
Move the selected template to the Recycle Bin. If you do not have permission to delete a GPO, you will be prompted to submit a request.
-
-
-
Rename
-
Change the name of the selected template.
-
-
-
-
-
-
-## Miscellaneous
-
-
-
-
-
-
-
-
-
-
Command
-
Effect
-
-
-
-
-
Refresh
-
Update the display of the Group Policy Management Console to incorporate any changes. Some changes are not visible until the display is refreshed.
-
-
-
Help
-
Display help for Advanced Group Policy Management (AGPM).
-
-
-
-
-
-
-### Additional references
-
-- [Contents Tab](contents-tab-agpm40.md)
-
-- [Performing Editor Tasks](performing-editor-tasks-agpm40.md)
-
-- [Performing Reviewer Tasks](performing-reviewer-tasks-agpm40.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/templates-tab.md b/mdop/agpm/templates-tab.md
deleted file mode 100644
index 75b67d4b89..0000000000
--- a/mdop/agpm/templates-tab.md
+++ /dev/null
@@ -1,164 +0,0 @@
----
-title: Templates Tab
-description: Templates Tab
-author: dansimp
-ms.assetid: 5676e9f9-eb52-49e1-a55d-15c1059af368
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Templates Tab
-
-
-The **Templates** tab:
-
-- Displays a list of available templates that you can use to create new Group Policy objects (GPOs).
-
-- Provides a shortcut menu with commands for creating a GPO based on a selected template, managing templates, and displaying reports for templates.
-
-- Displays a list of the groups and users who have permission to access a selected template.
-
-Because a template cannot be altered, templates have no history. However, like any GPO version, the settings of a template can be displayed with a settings report or compared to another GPO with a difference report.
-
-**Note**
-A template is an uneditable, static version of a GPO for use as a starting point for creating new, editable GPOs.
-
-
-
-Right-clicking the **Group Policy Objects** list on this tab displays a shortcut menu, including whichever of the following options are applicable.
-
-## Control
-
-
-
-
-
-
-
-
-
-
Command
-
Effect
-
-
-
-
-
New Controlled GPO
-
Create a new GPO based on the selected template. The option to deploy the new GPO to the production environment is provided. If you do not have permission to create a GPO, you will be prompted to submit a request. (This option is displayed if no GPO is selected when right-clicking in the Group Policy Objects list.)
-
-
-
-
-
-
-## Reports
-
-
-
-
-
-
-
-
-
-
Command
-
Effect
-
-
-
-
-
Settings
-
Generate an HTML-based or XML-based report displaying the settings within the selected GPO.
-
-
-
Differences
-
Generate an HTML-based or XML-based report comparing the settings within two selected GPO templates.
-
-
-
-
-
-
-## Template management
-
-
-
-
-
-
-
-
-
-
Command
-
Effect
-
-
-
-
-
Set as Default
-
Set the selected template as the default to be used automatically when creating a new GPO.
-
-
-
Delete
-
Move the selected template to the Recycle Bin. If you do not have permission to delete a GPO, you will be prompted to submit a request.
-
-
-
Rename
-
Change the name of the selected template.
-
-
-
-
-
-
-## Miscellaneous
-
-
-
-
-
-
-
-
-
-
Command
-
Effect
-
-
-
-
-
Refresh
-
Update the display of the Group Policy Management Console to incorporate any changes. Some changes are not visible until the display is refreshed.
-
-
-
Help
-
Display help for Advanced Group Policy Management (AGPM).
-
-
-
-
-
-
-### Additional references
-
-- [Contents Tab](contents-tab.md)
-
-- [Performing Editor Tasks](performing-editor-tasks.md)
-
-- [Performing Reviewer Tasks](performing-reviewer-tasks.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/test-a-gpo-in-a-separate-organizational-unit-agpm40.md b/mdop/agpm/test-a-gpo-in-a-separate-organizational-unit-agpm40.md
deleted file mode 100644
index e3ebc0c30b..0000000000
--- a/mdop/agpm/test-a-gpo-in-a-separate-organizational-unit-agpm40.md
+++ /dev/null
@@ -1,47 +0,0 @@
----
-title: Test a GPO in a Separate Organizational Unit
-description: Test a GPO in a Separate Organizational Unit
-author: dansimp
-ms.assetid: 9a9e6d22-74e6-41d8-ac2f-12a1b76ad5a0
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Test a GPO in a Separate Organizational Unit
-
-
-If you use a testing organizational unit (OU) to test Group Policy Objects (GPOs) within the same domain before deployment to the production environment, you must have the necessary permissions to access the test OU. Using a test OU is optional.
-
-**To use a test OU**
-
-1. Although you have the GPO checked out for editing, in the **Group Policy Management Console**, click **Group Policy Objects** in the forest and domain in which you are managing GPOs.
-
-2. Click the checked out copy of the GPO to be tested. The name will be preceded by **\[AGPM\]**. (If it is not listed, click **Action**, then **Refresh**. Sort the names alphabetically, and **\[AGPM\]** GPOs will typically appear at the top of the list.)
-
-3. Drag the GPO to the test OU.
-
-4. Click **OK** in the dialog box that asks whether to create a link to the GPO in the test OU.
-
-### Additional considerations
-
-- When testing is complete, checking in the GPO automatically deletes the link to the checked-out copy of the GPO.
-
-### Additional references
-
-- [Using a Test Environment](using-a-test-environment.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/troubleshooting-advanced-group-policy-management-agpm30ops.md b/mdop/agpm/troubleshooting-advanced-group-policy-management-agpm30ops.md
deleted file mode 100644
index 9b374f5a81..0000000000
--- a/mdop/agpm/troubleshooting-advanced-group-policy-management-agpm30ops.md
+++ /dev/null
@@ -1,151 +0,0 @@
----
-title: Troubleshooting Advanced Group Policy Management
-description: Troubleshooting Advanced Group Policy Management
-author: dansimp
-ms.assetid: f7ece97c-e9f8-4b18-8c7a-a615c98d5c60
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Troubleshooting Advanced Group Policy Management
-
-
-This section lists common issues that you may encounter when you use Advanced Group Policy Management (AGPM) to manage Group Policy Objects (GPOs). To diagnose issues not listed here, it may be helpful for an AGPM Administrator (Full Control) to use logging and tracing. For more information, see [Configure Logging and Tracing](configure-logging-and-tracing-agpm30ops.md).
-
-**Note**
-- For information about rolling back to an earlier version of a GPO if there are problems, see [Roll Back to a Previous Version of a GPO](roll-back-to-a-previous-version-of-a-gpo-agpm30ops.md).
-
-- For information about how to recover from a disaster by restoring the complete archive from a backup, see [Restore the Archive from a Backup](restore-the-archive-from-a-backup.md).
-
-
-
-## What problems are you having?
-
-
-- [I am unable to access an archive](#bkmk-access-an-archive)
-
-- [The GPO state varies for different Group Policy administrators](#bkmk-state-varies)
-
-- [I am unable to modify the AGPM Server connection](#bkmk-modify-archive-location)
-
-- [I am unable to change the default template or view, create, edit, rename, deploy, or delete GPOs](#bkmk-perform-task)
-
-- [I am unable to use a particular GPO name](#bkmk-use-particular-name)
-
-- [I am not receiving AGPM e-mail notifications](#bkmk-email)
-
-- [I cannot use port 4600 for the AGPM Service](#bkmk-port)
-
-- [The AGPM Service will not start](#bkmk-not-start)
-
-- [Group Policy Software Installation fails to install software](#bkmk-software-installation)
-
-- [An error occurred when I restored the archive to a new AGPM Server](#bkmk-error-on-restore)
-
-### I am unable to access an archive
-
-- **Cause**: You have not selected the correct server and port for the archive.
-
-- **Solution**:
-
- - If you are an AGPM Administrator: See [Configure AGPM Server Connections](configure-agpm-server-connections-agpm30ops.md).
-
- - If you are not an AGPM Administrator: Request connection details for the AGPM Server from an AGPM Administrator. See [Configure an AGPM Server Connection](configure-an-agpm-server-connection-reviewer-agpm30ops.md).
-
-- **Cause**: The AGPM Service is not running.
-
-- **Solution**:
-
- - If you are an AGPM Administrator: Start the AGPM Service. For more information, see [Start and Stop the AGPM Service](start-and-stop-the-agpm-service-agpm30ops.md).
-
- - If you are not an AGPM Administrator: Contact an AGPM Administrator for assistance.
-
-### The GPO state varies for different Group Policy administrators
-
-- **Cause**: Different Group Policy administrators have selected different AGPM Servers for the same archive.
-
-- **Solution**:
-
- - If you are an AGPM Administrator: See [Configure AGPM Server Connections](configure-agpm-server-connections-agpm30ops.md).
-
- - If you are not an AGPM Administrator: Request connection details for the AGPM Server from an AGPM Administrator. See [Configure an AGPM Server Connection](configure-an-agpm-server-connection-reviewer-agpm30ops.md).
-
-### I am unable to modify the AGPM Server connection
-
-- **Cause**: If the settings on the **AGPM Server** tab are unavailable, the AGPM Server has been centrally configured using an Administrative template.
-
-- **Solution**:
-
- - If you are an AGPM Administrator: If the settings on the **AGPM Server** tab are unavailable, see [Configure AGPM Server Connections](configure-agpm-server-connections-agpm30ops.md).
-
- - If you are not an AGPM Administrator: If the settings on the **AGPM Server** tab are unavailable, you do not need to modify the AGPM Server.
-
-### I am unable to change the default template or view, create, edit, rename, deploy, or delete GPOs
-
-- **Cause**: You have not been assigned a role with the permissions required to perform the task or tasks.
-
-- **Solution**:
-
- - If you are an AGPM Administrator: See [Delegate Domain-Level Access to the Archive](delegate-domain-level-access-to-the-archive-agpm30ops.md) and [Delegate Access to an Individual GPO in the Archive](delegate-access-to-an-individual-gpo-in-the-archive-agpm30ops.md). AGPM permissions will cascade from the domain to all GPOs currently in the archive. For details about which roles can perform a task and which permissions are necessary to perform a task, refer to the help for that task.
-
- - If you are not an AGPM Administrator and you require additional roles or permissions: Contact an AGPM Administrator for assistance. Be aware that if you are an Editor, you can begin the process of creating a GPO, deploying a GPO, or deleting a GPO from the production environment, but an Approver or AGPM Administrator must approve your request.
-
-### I am unable to use a particular GPO name
-
-- **Cause**: Either the GPO name is already in use or you lack permission to list the GPO.
-
-- **Solution**:
-
- - If the GPO name appears on the **Controlled**, **Uncontrolled**, or **Pending** tab, choose another name. If a GPO that was deployed is renamed but not yet redeployed, it will be displayed under its old name in the production environment. Therefore, the old name is still being used. Redeploy the GPO to update its name in the production environment and release that name for use by another GPO.
-
- - If the GPO name does not appear on the **Controlled**, **Uncontrolled**, or **Pending** tab, you may lack permission to list the GPO. To request permission, contact an AGPM Administrator.
-
-### I am not receiving AGPM e-mail notifications
-
-- **Cause**: A valid SMTP e-mail server and e-mail address has not been provided, or no action has been taken that generates an e-mail notification.
-
-- **Solution**:
-
- - If you are an AGPM Administrator: For e-mail notifications about pending actions to be sent by AGPM, an AGPM Administrator must provide a valid SMTP e-mail server and e-mail addresses for Approvers on the **Domain Delegation** tab. For more information, see [Configure E-Mail Notification](configure-e-mail-notification-agpm30ops.md).
-
- - E-mail notifications are generated only when an Editor, Reviewer, or other Group Policy administrator who lacks the permission necessary to create, deploy, or delete a GPO submits a request for one of those actions to occur. There is no automatic notification of approval or rejection of a request.
-
-### I cannot use port 4600 for the AGPM Service
-
-- **Cause**: By default, the port on which the AGPM Service listens is port 4600.
-
-- **Solution**: If port 4600 is not available for the AGPM Service, modify the port configuration on the AGPM Server to use another port and then update the port in the AGPM Server connection for AGPM Clients. For more information, see [Modify the AGPM Service](modify-the-agpm-service-agpm30ops.md).
-
-### The AGPM Service will not start
-
-- **Cause**: You have modified settings for the AGPM Service in the operating system under **Administrative Tools** and **Services**.
-
-- **Solution**: Modify the settings for **Microsoft Advanced Group Policy Management - Server** under **Programs and Features** in Control Panel. For more information, see [Modify the AGPM Service](modify-the-agpm-service-agpm30ops.md).
-
-### Group Policy Software Installation fails to install software
-
-- **Cause**: AGPM preserves the integrity of Group Policy Software Installation packages. Although GPOs are edited offline, links between packages in addition to cached client information are preserved. This is by design.
-
-- **Solution**: When you edit a GPO offline with AGPM, configure any Group Policy Software Installation upgrade of a package in another GPO to reference the deployed GPO, not the checked-out copy. The Editor must have **Read** permission for the deployed GPO.
-
-### An error occurred when I restored the archive to a new AGPM Server
-
-- **Cause**: For security reasons, the encryption protecting the password entered on the **Domain Delegation** tab causes the password to fail if the archive is moved to another computer.
-
-- **Solution**: Re-enter and confirm the password on the **Domain Delegation** tab. For more information, see [Configure E-Mail Notification](configure-e-mail-notification-agpm30ops.md).
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/troubleshooting-advanced-group-policy-management.md b/mdop/agpm/troubleshooting-advanced-group-policy-management.md
deleted file mode 100644
index 4284e54ffd..0000000000
--- a/mdop/agpm/troubleshooting-advanced-group-policy-management.md
+++ /dev/null
@@ -1,136 +0,0 @@
----
-title: Troubleshooting Advanced Group Policy Management
-description: Troubleshooting Advanced Group Policy Management
-author: dansimp
-ms.assetid: f58849cf-6c5b-44d8-b356-0ed7a5b24cee
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Troubleshooting Advanced Group Policy Management
-
-
-This section lists a few common issues you may encounter when using Advanced Group Policy Management (AGPM) to manage Group Policy objects (GPOs).
-
-## What problems are you having?
-
-
-- [I am unable to access an archive](#bkmk-access-an-archive)
-
-- [The GPO state varies for different Group Policy administrators](#bkmk-state-varies)
-
-- [I am unable to modify the AGPM Server connection](#bkmk-modify-archive-location)
-
-- [I am unable to change the default template or view, create, edit, rename, deploy, or delete GPOs](#bkmk-perform-task)
-
-- [I am unable to use a particular GPO name](#bkmk-use-particular-name)
-
-- [I am not receiving AGPM e-mail notifications](#bkmk-email)
-
-- [I cannot use port 4600 for the AGPM Service](#bkmk-port)
-
-- [The AGPM Service will not start](#bkmk-not-start)
-
-- [Group Policy Software Installation fails to install software](#bkmk-software-installation)
-
-### I am unable to access an archive
-
-- **Cause**: You have not selected the correct server and port for the archive.
-
-- **Solution**:
-
- - If you are an AGPM Administrator: See [Configure the AGPM Server Connection](configure-the-agpm-server-connection.md).
-
- - If you are not an AGPM Administrator: Request connection details for the AGPM Server from an AGPM Administrator. See [Configure the AGPM Server Connection](configure-the-agpm-server-connection-reviewer.md).
-
-- **Cause**: The Advanced Group Policy Management Service is not running.
-
-- **Solution**:
-
- - If you are an AGPM Administrator: Start the AGPM Service. For more information, see [Start and Stop the AGPM Service](start-and-stop-the-agpm-service.md).
-
- - If you are not an AGPM Administrator: Contact an AGPM Administrator for assistance.
-
-### The GPO state varies for different Group Policy administrators
-
-- **Cause**: Different Group Policy administrators have selected different AGPM Servers for the same archive.
-
-- **Solution**:
-
- - If you are an AGPM Administrator: See [Configure the AGPM Server Connection](configure-the-agpm-server-connection.md).
-
- - If you are not an AGPM Administrator: Request connection details for the AGPM Server from an AGPM Administrator. See [Configure the AGPM Server Connection](configure-the-agpm-server-connection-reviewer.md).
-
-### I am unable to modify the AGPM Server connection
-
-- **Cause**: If the settings on the **AGPM Server** tab are unavailable, the AGPM Server has been centrally configured using an Administrative template.
-
-- **Solution**:
-
- - If you are an AGPM Administrator: If the settings on the **AGPM Server** tab are unavailable, see [Configure the AGPM Server Connection](configure-the-agpm-server-connection.md).
-
- - If you are not an AGPM Administrator: If the settings on the **AGPM Server** tab are unavailable, you do not need to modify the AGPM Server.
-
-### I am unable to change the default template or view, create, edit, rename, deploy, or delete GPOs
-
-- **Cause**: You have not been assigned a role with the permissions required to perform the task or tasks.
-
-- **Solution**:
-
- - If you are an AGPM Administrator: See [Delegate Domain-Level Access](delegate-domain-level-access.md) and [Delegate Access to an Individual GPO](delegate-access-to-an-individual-gpo.md). AGPM permissions will cascade from the domain to all GPOs currently in the archive. As new Group Policy administrators are added at the domain level, their permissions must be set to apply to **This object and nested objects**. For details about which roles can perform a task and what permissions are necessary to perform a task, refer to the help for that task.
-
- - If you are not an AGPM Administrator and you require additional roles or permissions: Contact an AGPM Administrator for assistance. Note that if you are an Editor, you can begin the process of creating a GPO, deploying a GPO, or deleting a GPO from the production environment, but an Approver or AGPM Administrator must approve your request.
-
-### I am unable to use a particular GPO name
-
-- **Cause**: Either the GPO name is already in use or you lack permission to list the GPO.
-
-- **Solution**:
-
- - If the GPO name appears on the **Controlled**, **Uncontrolled**, or **Pending** tab, choose another name. If a GPO that has been deployed is renamed but not yet redeployed, it will be displayed under its old name in the production environment—therefore, the old name is still in use. Redeploy the GPO to update its name in the production environment and release that name for use by another GPO.
-
- - If the GPO name does not appear on the **Controlled**, **Uncontrolled**, or **Pending** tab, you may lack permission to list the GPO. To request permission, contact an AGPM Administrator.
-
-### I am not receiving AGPM e-mail notifications
-
-- **Cause**: A valid SMTP e-mail server and e-mail address has not been provided, or no action has been taken that generates an e-mail notification.
-
-- **Solution**:
-
- - If you are an AGPM Administrator: For e-mail notifications about pending actions to be sent by AGPM, an AGPM Administrator must provide a valid SMTP e-mail server and e-mail addresses for Approvers on the **Domain Delegation** tab. For more information, see [Configure E-Mail Notification](configure-e-mail-notification.md).
-
- - E-mail notifications are generated only when an Editor, Reviewer, or other Group Policy administrator who lacks the permission necessary to create, deploy, or delete a GPO submits a request for one of those actions to occur. There is no automatic notification of approval or rejection of a request.
-
-### I cannot use port 4600 for the AGPM Service
-
-- **Cause**: By default, the port on which the AGPM Service listens is port 4600.
-
-- **Solution**: If port 4600 is not available for the AGPM Service, modify each archive index file to use another port and then update the AGPM Server for all Group Policy administrators. For more information, see [Modify the Port on Which the AGPM Service Listens](modify-the-port-on-which-the-agpm-service-listens.md).
-
-### The AGPM Service will not start
-
-- **Cause**: You have modified settings for the AGPM Service in the operating system under **Administrative Tools** and **Services**.
-
-- **Solution**: Modify the settings for **Microsoft Advanced Group Policy Management - Server** under **Add or Remove Programs**. For more information, see [Modify the AGPM Service Account](modify-the-agpm-service-account.md).
-
-### Group Policy Software Installation fails to install software
-
-- **Cause**: AGPM preserves the integrity of Group Policy Software Installation packages. Although GPOs are edited offline, links between packages as well as cached client information are preserved. This is by design.
-
-- **Solution**: When editing a GPO offline with AGPM, configure any Group Policy Software Installation upgrade of a package in another GPO to reference the deployed GPO, not the checked-out copy. The Editor must have **Read** permission for the deployed GPO.
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/troubleshooting-agpm-agpm40.md b/mdop/agpm/troubleshooting-agpm-agpm40.md
deleted file mode 100644
index 27451ca6e3..0000000000
--- a/mdop/agpm/troubleshooting-agpm-agpm40.md
+++ /dev/null
@@ -1,151 +0,0 @@
----
-title: Troubleshooting AGPM
-description: Troubleshooting AGPM
-author: dansimp
-ms.assetid: bedcd817-beb2-47bf-aebd-e3923c4fd06f
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Troubleshooting AGPM
-
-
-This section lists common issues that you may encounter when you use Advanced Group Policy Management (AGPM) to manage Group Policy Objects (GPOs). To diagnose issues not listed here, it may be helpful for an AGPM Administrator (Full Control) to use logging and tracing. For more information, see [Configure Logging and Tracing](configure-logging-and-tracing-agpm40.md).
-
-**Note**
-- For information about rolling back to an earlier version of a GPO if there are problems, see [Roll Back to an Earlier Version of a GPO](roll-back-to-an-earlier-version-of-a-gpo-agpm40.md).
-
-- For information about how to recover from a disaster by restoring the complete archive from a backup, see [Restore the Archive from a Backup](restore-the-archive-from-a-backup-agpm40.md).
-
-
-
-## What problems are you having?
-
-
-- [I am unable to access an archive](#bkmk-access-an-archive)
-
-- [The GPO state varies for different Group Policy administrators](#bkmk-state-varies)
-
-- [I am unable to modify the AGPM Server connection](#bkmk-modify-archive-location)
-
-- [I am unable to change the default template or view, create, edit, rename, deploy, or delete GPOs](#bkmk-perform-task)
-
-- [I am unable to use a particular GPO name](#bkmk-use-particular-name)
-
-- [I am not receiving AGPM e-mail notifications](#bkmk-email)
-
-- [I cannot use port 4600 for the AGPM Service](#bkmk-port)
-
-- [The AGPM Service will not start](#bkmk-not-start)
-
-- [Group Policy Software Installation fails to install software](#bkmk-software-installation)
-
-- [An error occurred when I restored the archive to a new AGPM Server](#bkmk-error-on-restore)
-
-### I am unable to access an archive
-
-- **Cause**: You have not selected the correct server and port for the archive.
-
-- **Solution**:
-
- - If you are an AGPM Administrator: See [Configure AGPM Server Connections](configure-agpm-server-connections-agpm40.md).
-
- - If you are not an AGPM Administrator: Request connection details for the AGPM Server from an AGPM Administrator. See [Configure an AGPM Server Connection](configure-an-agpm-server-connection-agpm40.md).
-
-- **Cause**: The AGPM Service is not running.
-
-- **Solution**:
-
- - If you are an AGPM Administrator: Start the AGPM Service. For more information, see [Start and Stop the AGPM Service](start-and-stop-the-agpm-service-agpm40.md).
-
- - If you are not an AGPM Administrator: Contact an AGPM Administrator for assistance.
-
-### The GPO state varies for different Group Policy administrators
-
-- **Cause**: Different Group Policy administrators have selected different AGPM Servers for the same archive.
-
-- **Solution**:
-
- - If you are an AGPM Administrator: See [Configure AGPM Server Connections](configure-agpm-server-connections-agpm40.md).
-
- - If you are not an AGPM Administrator: Request connection details for the AGPM Server from an AGPM Administrator. See [Configure an AGPM Server Connection](configure-an-agpm-server-connection-agpm40.md).
-
-### I am unable to modify the AGPM Server connection
-
-- **Cause**: If the settings on the **AGPM Server** tab are unavailable, the AGPM Server has been centrally configured using an Administrative template.
-
-- **Solution**:
-
- - If you are an AGPM Administrator: If the settings on the **AGPM Server** tab are unavailable, see [Configure AGPM Server Connections](configure-agpm-server-connections-agpm40.md).
-
- - If you are not an AGPM Administrator: If the settings on the **AGPM Server** tab are unavailable, you do not need to modify the AGPM Server.
-
-### I am unable to change the default template or view, create, edit, rename, deploy, or delete GPOs
-
-- **Cause**: You have not been assigned a role with the permissions required to perform the task or tasks.
-
-- **Solution**:
-
- - If you are an AGPM Administrator: See [Delegate Domain-Level Access to the Archive](delegate-domain-level-access-to-the-archive-agpm40.md) and [Delegate Access to an Individual GPO in the Archive](delegate-access-to-an-individual-gpo-in-the-archive-agpm40.md). AGPM permissions will cascade from the domain to all GPOs currently in the archive. For details about which roles can perform a task and which permissions are necessary to perform a task, refer to the help for that task.
-
- - If you are not an AGPM Administrator and you require additional roles or permissions: Contact an AGPM Administrator for assistance. Be aware that if you are an Editor, you can begin the process of creating a GPO, deploying a GPO, or deleting a GPO from the production environment of the domain, but an Approver or AGPM Administrator must approve your request.
-
-### I am unable to use a particular GPO name
-
-- **Cause**: Either the GPO name is already in use or you lack permission to list the GPO.
-
-- **Solution**:
-
- - If the GPO name appears on the **Controlled**, **Uncontrolled**, or **Pending** tab, choose another name. If a GPO that was deployed is renamed but not yet redeployed, it will be displayed under its old name in the production environment of the domain. Therefore, the old name is still being used. Redeploy the GPO to update its name in the production environment and release that name for use by another GPO.
-
- - If the GPO name does not appear on the **Controlled**, **Uncontrolled**, or **Pending** tab, you may lack permission to list the GPO. To request permission, contact an AGPM Administrator.
-
-### I am not receiving AGPM e-mail notifications
-
-- **Cause**: A valid SMTP e-mail server and e-mail address has not been provided, or no action has been taken that generates an e-mail notification.
-
-- **Solution**:
-
- - If you are an AGPM Administrator: For e-mail notifications about pending actions to be sent by AGPM, an AGPM Administrator must provide a valid SMTP e-mail server and e-mail addresses for Approvers on the **Domain Delegation** tab. For more information, see [Configure E-Mail Notification](configure-e-mail-notification-agpm40.md).
-
- - E-mail notifications are generated only when an Editor, Reviewer, or other Group Policy administrator who lacks the permission necessary to create, deploy, or delete a GPO submits a request for one of those actions to occur. There is no automatic notification of approval or rejection of a request.
-
-### I cannot use port 4600 for the AGPM Service
-
-- **Cause**: By default, the port on which the AGPM Service listens is port 4600.
-
-- **Solution**: If port 4600 is not available for the AGPM Service, modify the port configuration on the AGPM Server to use another port and then update the port in the AGPM Server connection for AGPM Clients. For more information, see [Modify the AGPM Service](modify-the-agpm-service-agpm40.md).
-
-### The AGPM Service will not start
-
-- **Cause**: You have modified settings for the AGPM Service in the operating system under **Administrative Tools** and **Services**.
-
-- **Solution**: Modify the settings for **Microsoft Advanced Group Policy Management - Server** under **Programs and Features** in Control Panel. For more information, see [Modify the AGPM Service](modify-the-agpm-service-agpm40.md).
-
-### Group Policy Software Installation fails to install software
-
-- **Cause**: AGPM preserves the integrity of Group Policy Software Installation packages. Although GPOs are edited offline, links between packages in addition to cached client information are preserved. This is by design.
-
-- **Solution**: When you edit a GPO offline with AGPM, configure any Group Policy Software Installation upgrade of a package in another GPO to reference the deployed GPO, not the checked-out copy. The Editor must have **Read** permission for the deployed GPO.
-
-### An error occurred when I restored the archive to a new AGPM Server
-
-- **Cause**: For security reasons, the encryption protecting the password entered on the **Domain Delegation** tab causes the password to fail if the archive is moved to another computer.
-
-- **Solution**: Re-enter and confirm the password on the **Domain Delegation** tab. For more information, see [Configure E-Mail Notification](configure-e-mail-notification-agpm40.md).
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/troubleshooting-agpm40-upgrades.md b/mdop/agpm/troubleshooting-agpm40-upgrades.md
deleted file mode 100644
index 0275e8dc91..0000000000
--- a/mdop/agpm/troubleshooting-agpm40-upgrades.md
+++ /dev/null
@@ -1,56 +0,0 @@
----
-title: Troubleshooting AGPM Upgrades
-description: Troubleshooting AGPM Upgrades
-author: dansimp
-ms.assetid: 1abbf0c1-fd32-46a8-a3ba-c005f066523d
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Troubleshooting AGPM Upgrades
-
-This section lists common issues that you may encounter when you upgrade your Advanced Group Policy Management (AGPM) server to a newer version (e.g. AGPM 4.0 to AGPM 4.3). To diagnose issues not listed here, it may be helpful to view the [Troubleshooting AGPM](troubleshooting-agpm-agpm40.md) or for an AGPM Administrator (Full Control) to use logging and tracing. For more information, see [Configure Logging and Tracing](configure-logging-and-tracing-agpm40.md).
-
-## What problems are you having?
-
-- [Failed to generate a HTML GPO difference report (Error code 80004003)](#bkmk-error-80004003)
-
-### Failed to generate a HTML GPO difference report (Error code 80004003)
-
-- **Cause**: You have installed the AGPM upgrade package with an incorrect account.
-
-- **Solution**: You will need to be an AGPM administrator in order to fix this issue.
-
- - Ensure you know the username & password of your **AGPM service account**.
-
- - Log onto your AGPM server interactively as your AGPM service account.
-
- - This is critically important, as the install will fail if you use a different account.
-
- - Shutdown the AGPM service.
-
- - Install the required hotfix.
-
- - Connect to AGPM using an AGPM client to test that your difference reports are now functioning.
-
-## Install Hotfix Package 1 for Microsoft Advanced Group Policy Management 4.0 SP3
-
-**Issue fixed in this hotfix**: AGPM can't generate difference reports when it controls or manages new Group Policy Objects (GPOs).
-
-**How to get this update**: Install the latest version of Microsoft Desktop Optimization Pack ([March 2017 Servicing Release](https://www.microsoft.com/download/details.aspx?id=54967)). See [KB 4014009](https://support.microsoft.com/help/4014009/) for more information.
-
-More specifically, you can choose to download only the first file, `AGPM4.0SP1_Server_X64_KB4014009.exe`, from the list presented after pressing the download button.
-
-The download link to the Microsoft Desktop Optimization Pack (March 2017 Servicing Release) can be found [here](https://www.microsoft.com/download/details.aspx?id=54967).
-
-
-## Reference link
-https://support.microsoft.com/help/3127165/hotfix-package-1-for-microsoft-advanced-group-policy-management-4-0-sp
-
diff --git a/mdop/agpm/uncontrolled-gpo-commands-agpm30ops.md b/mdop/agpm/uncontrolled-gpo-commands-agpm30ops.md
deleted file mode 100644
index 1ad9a2806a..0000000000
--- a/mdop/agpm/uncontrolled-gpo-commands-agpm30ops.md
+++ /dev/null
@@ -1,135 +0,0 @@
----
-title: Uncontrolled GPO Commands
-description: Uncontrolled GPO Commands
-author: dansimp
-ms.assetid: 94c07b09-cb96-4ff2-b963-b25f103e73e9
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Uncontrolled GPO Commands
-
-
-The **Uncontrolled** tab:
-
-- Displays a list of Group Policy Objects (GPOs) not managed by Advanced Group Policy Management (AGPM).
-
-- Provides a shortcut menu with commands for bringing uncontrolled GPOs under the management of AGPM and for displaying the history and reports for GPOs.
-
-- Displays a list of the groups and users who have permission to access a selected GPO.
-
-Right-clicking the **Group Policy Objects** list on this tab displays a shortcut menu, including whichever of the following options are applicable.
-
-## Control and history
-
-
-
-
-
-
-
-
-
-
Command
-
Effect
-
-
-
-
-
History
-
Open a window listing all versions of the selected GPO saved within the archive. From the history, you can obtain a report of the settings within a GPO, compare two versions of a GPO, compare a GPO to a template, or roll back to a previous version of a GPO.
-
-
-
Control
-
Bring the selected uncontrolled GPO under the change control management of AGPM. If you do not have permission to control a GPO, you will be prompted to submit a request.
-
-
-
Save as Template
-
Create a new template based on the settings of the selected GPO.
-
-
-
-
-
-
-## Reports
-
-
-
-
-
-
-
-
-
-
Command
-
Effect
-
-
-
-
-
Settings
-
Generate an HTML-based or XML-based report displaying the settings within the selected GPO.
-
-
-
Differences
-
Generate an HTML-based or XML-based report comparing the settings within two selected GPOs or within the selected GPO and a template.
-
-
-
-
-
-
-## Miscellaneous
-
-
-
-
-
-
-
-
-
-
Command
-
Effect
-
-
-
-
-
Refresh
-
Update the display of the Group Policy Management Console (GPMC) to incorporate any changes. Some changes are not visible until the display is refreshed.
-
-
-
Help
-
Display help for AGPM.
-
-
-
-
-
-
-### Additional references
-
-- [Contents Tab](contents-tab-agpm30ops.md)
-
-- [Performing Editor Tasks](performing-editor-tasks-agpm30ops.md)
-
-- [Performing Approver Tasks](performing-approver-tasks-agpm30ops.md)
-
-- [Performing Reviewer Tasks](performing-reviewer-tasks-agpm30ops.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/uncontrolled-gpo-commands-agpm40.md b/mdop/agpm/uncontrolled-gpo-commands-agpm40.md
deleted file mode 100644
index 0b74dd5b18..0000000000
--- a/mdop/agpm/uncontrolled-gpo-commands-agpm40.md
+++ /dev/null
@@ -1,135 +0,0 @@
----
-title: Uncontrolled GPO Commands
-description: Uncontrolled GPO Commands
-author: dansimp
-ms.assetid: 05a8050f-adc3-465b-8524-bbe95745165c
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Uncontrolled GPO Commands
-
-
-The **Uncontrolled** tab:
-
-- Displays a list of Group Policy Objects (GPOs) not managed by Advanced Group Policy Management (AGPM).
-
-- Provides a shortcut menu with commands for bringing uncontrolled GPOs under the management of AGPM and for displaying the history and reports for GPOs.
-
-- Displays a list of the groups and users who have permission to access a selected GPO.
-
-Right-clicking the **Group Policy Objects** list on this tab displays a shortcut menu, including whichever of the following options are applicable.
-
-## Control and history
-
-
-
-
-
-
-
-
-
-
Command
-
Effect
-
-
-
-
-
History
-
Open a window listing all versions of the selected GPO saved within the archive. From the history, you can obtain a report of the settings within a GPO, compare two versions of a GPO, compare a GPO to a template, or roll back to an earlier version of a GPO.
-
-
-
Control
-
Bring the selected uncontrolled GPO under the change control management of AGPM. If you do not have permission to control a GPO, you will be prompted to submit a request.
-
-
-
Save as Template
-
Create a new template based on the settings of the selected GPO.
-
-
-
-
-
-
-## Reports
-
-
-
-
-
-
-
-
-
-
Command
-
Effect
-
-
-
-
-
Settings
-
Generate an HTML-based or XML-based report displaying the settings within the selected GPO.
-
-
-
Differences
-
Generate an HTML-based or XML-based report comparing the settings within two selected GPOs or within the selected GPO and a template.
-
-
-
-
-
-
-## Miscellaneous
-
-
-
-
-
-
-
-
-
-
Command
-
Effect
-
-
-
-
-
Refresh
-
Update the display of the Group Policy Management Console (GPMC) to incorporate any changes. Some changes are not visible until the display is refreshed.
-
-
-
Help
-
Display help for AGPM.
-
-
-
-
-
-
-### Additional references
-
-- [Contents Tab](contents-tab-agpm40.md)
-
-- [Performing Editor Tasks](performing-editor-tasks-agpm40.md)
-
-- [Performing Approver Tasks](performing-approver-tasks-agpm40.md)
-
-- [Performing Reviewer Tasks](performing-reviewer-tasks-agpm40.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/uncontrolled-tab.md b/mdop/agpm/uncontrolled-tab.md
deleted file mode 100644
index 49a863ddc3..0000000000
--- a/mdop/agpm/uncontrolled-tab.md
+++ /dev/null
@@ -1,135 +0,0 @@
----
-title: Uncontrolled Tab
-description: Uncontrolled Tab
-author: dansimp
-ms.assetid: d7e658bf-a72b-4813-bdc8-2fdb7251e742
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Uncontrolled Tab
-
-
-The **Uncontrolled** tab:
-
-- Displays a list of Group Policy objects (GPOs) not managed by Advanced Group Policy Management (AGPM).
-
-- Provides a shortcut menu with commands for bringing uncontrolled GPOs under the management of AGPM and for displaying the history and reports for GPOs.
-
-- Displays a list of the groups and users who have permission to access a selected GPO.
-
-Right-clicking the **Group Policy Objects** list on this tab displays a shortcut menu, including whichever of the following options are applicable.
-
-## Control and history
-
-
-
-
-
-
-
-
-
-
Command
-
Effect
-
-
-
-
-
History
-
Open a window listing all versions of the selected GPO saved within the archive. From the history, you can obtain a report of the settings within a GPO, compare two versions of a GPO, compare a GPO to a template, or roll back to a previous version of a GPO.
-
-
-
Control
-
Bring the selected uncontrolled GPO under the change control management of AGPM. If you do not have permission to control a GPO, you will be prompted to submit a request.
-
-
-
Save as Template
-
Create a new template based on the settings of the selected GPO.
-
-
-
-
-
-
-## Reports
-
-
-
-
-
-
-
-
-
-
Command
-
Effect
-
-
-
-
-
Settings
-
Generate an HTML-based or XML-based report displaying the settings within the selected GPO.
-
-
-
Differences
-
Generate an HTML-based or XML-based report comparing the settings within two selected GPOs or within the selected GPO and a template.
-
-
-
-
-
-
-## Miscellaneous
-
-
-
-
-
-
-
-
-
-
Command
-
Effect
-
-
-
-
-
Refresh
-
Update the display of the Group Policy Management Console to incorporate any changes. Some changes are not visible until the display is refreshed.
-
-
-
Help
-
Display help for AGPM.
-
-
-
-
-
-
-### Additional references
-
-- [Contents Tab](contents-tab.md)
-
-- [Performing Editor Tasks](performing-editor-tasks.md)
-
-- [Performing Approver Tasks](performing-approver-tasks.md)
-
-- [Performing Reviewer Tasks](performing-reviewer-tasks.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/use-a-test-environment-agpm30ops.md b/mdop/agpm/use-a-test-environment-agpm30ops.md
deleted file mode 100644
index 825a592d62..0000000000
--- a/mdop/agpm/use-a-test-environment-agpm30ops.md
+++ /dev/null
@@ -1,47 +0,0 @@
----
-title: Use a Test Environment
-description: Use a Test Environment
-author: dansimp
-ms.assetid: 86295084-b39e-4040-bb3f-15c3c1e99b1a
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Use a Test Environment
-
-
-If you use a testing organizational unit (OU) to test Group Policy Objects (GPOs) before deployment to the production environment, you must have the necessary permissions to access the test OU. The use of a test OU is optional.
-
-**To use a test OU**
-
-1. While you have the GPO checked out for editing, in the **Group Policy Management Console**, click **Group Policy Objects** in the forest and domain in which you are managing GPOs.
-
-2. Click the checked out copy of the GPO to be tested. The name will be preceded with **\[Checked Out\]**. (If it is not listed, click **Action**, then **Refresh**. Sort the names alphabetically, and **\[Checked Out\]** GPOs will typically appear at the top of the list.)
-
-3. Drag and drop the GPO to the test OU.
-
-4. Click **OK** in the dialog box asking whether to create a link to the GPO in the test OU.
-
-### Additional considerations
-
-- When testing is complete, checking in the GPO automatically deletes the link to the checked-out copy of the GPO.
-
-### Additional references
-
-- [Editing a GPO](editing-a-gpo-agpm30ops.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/use-a-test-environment.md b/mdop/agpm/use-a-test-environment.md
deleted file mode 100644
index ca6badb289..0000000000
--- a/mdop/agpm/use-a-test-environment.md
+++ /dev/null
@@ -1,47 +0,0 @@
----
-title: Use a Test Environment
-description: Use a Test Environment
-author: dansimp
-ms.assetid: b8d7b3ee-030a-4b5b-8223-4a3276fd47a7
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Use a Test Environment
-
-
-If you use a testing organizational unit (OU) to test Group Policy objects (GPOs) before deployment to the production environment, you must have the necessary permissions to access the test OU. The use of a test OU is optional.
-
-**To use a test OU**
-
-1. While you have the GPO checked out for editing, in the **Group Policy Management Console**, click **Group Policy Objects** in the forest and domain in which you are managing GPOs.
-
-2. Click the checked out copy of the GPO to be tested. The name will be preceded with **\[AGPM\]**. (If it is not listed, click **Action**, then **Refresh**. Sort the names alphabetically, and **\[AGPM\]** GPOs will typically appear at the top of the list.)
-
-3. Drag and drop the GPO to the test OU.
-
-4. Click **OK** in the dialog box asking whether to create a link to the GPO in the test OU.
-
-### Additional considerations
-
-- When testing is complete, checking in the GPO automatically deletes the link to the checked-out copy of the GPO.
-
-### Additional references
-
-- [Editing a GPO](editing-a-gpo.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/user-interface-advanced-group-policy-management-agpm30ops.md b/mdop/agpm/user-interface-advanced-group-policy-management-agpm30ops.md
deleted file mode 100644
index 870b709194..0000000000
--- a/mdop/agpm/user-interface-advanced-group-policy-management-agpm30ops.md
+++ /dev/null
@@ -1,41 +0,0 @@
----
-title: User Interface Advanced Group Policy Management
-description: User Interface Advanced Group Policy Management
-author: dansimp
-ms.assetid: 19aab694-8283-4d97-9425-1845404b461f
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# User Interface: Advanced Group Policy Management
-
-
-Advanced Group Policy Management (AGPM) adds a **Change Control** folder to each domain displayed in the **Group Policy Management Console** (GPMC). In an environment where multiple domains are managed with the GPMC, each domain is listed under the **Domains** folder in the console tree. Each domain has a **Change Control** folder under it, and there is one archive of Group Policy Objects (GPOs) per domain.
-
-Within the details pane there are four primary tabs, providing access to both GPO-level settings and domain-level settings and commands for AGPM. Additionally, there are Administrative template settings specific to AGPM.
-
-- [Contents Tab](contents-tab-agpm30ops.md): GPO settings and commands and GPO-level delegation
-
-- [Domain Delegation Tab](domain-delegation-tab-agpm30ops.md): AGPM e-mail notification settings and domain-level delegation
-
-- [AGPM Server Tab](agpm-server-tab-agpm30ops.md): Domain-level archive connection settings
-
-- [Production Delegation Tab](production-delegation-tab-agpm30ops.md): Production environment delegation
-
-- [Administrative Templates Folder](administrative-templates-folder-agpm30ops.md): Central configuration of logging and tracking, archive locations, and the visibility of features
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/user-interface-advanced-group-policy-management-agpm40.md b/mdop/agpm/user-interface-advanced-group-policy-management-agpm40.md
deleted file mode 100644
index 7104e96d2a..0000000000
--- a/mdop/agpm/user-interface-advanced-group-policy-management-agpm40.md
+++ /dev/null
@@ -1,41 +0,0 @@
----
-title: User Interface Advanced Group Policy Management
-description: User Interface Advanced Group Policy Management
-author: dansimp
-ms.assetid: 1bf67f6a-4f24-4020-a8c1-fe440de9caa3
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# User Interface: Advanced Group Policy Management
-
-
-Advanced Group Policy Management (AGPM) adds a **Change Control** folder to each domain displayed in the **Group Policy Management Console** (GPMC). In an environment where multiple domains are managed with the GPMC, each domain is listed under the **Domains** folder in the console tree. Each domain has a **Change Control** folder under it, and there is one archive of Group Policy Objects (GPOs) per domain.
-
-Within the details pane there are four primary tabs, providing access to both GPO-level settings and domain-level settings and commands for AGPM. Additionally, there are Administrative template settings specific to AGPM.
-
-- [Contents Tab](contents-tab-agpm40.md): GPO settings and commands and GPO-level delegation
-
-- [Domain Delegation Tab](domain-delegation-tab-agpm40.md): AGPM e-mail notification settings and domain-level delegation
-
-- [AGPM Server Tab](agpm-server-tab-agpm40.md): Domain-level archive connection settings
-
-- [Production Delegation Tab](production-delegation-tab-agpm40.md): Production environment delegation
-
-- [Administrative Templates Folder](administrative-templates-folder-agpm40.md): Central configuration of logging and tracking, archive locations, and the visibility of features
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/user-interface-advanced-group-policy-management.md b/mdop/agpm/user-interface-advanced-group-policy-management.md
deleted file mode 100644
index b8a2fbc5b2..0000000000
--- a/mdop/agpm/user-interface-advanced-group-policy-management.md
+++ /dev/null
@@ -1,43 +0,0 @@
----
-title: User Interface Advanced Group Policy Management
-description: User Interface Advanced Group Policy Management
-author: dansimp
-ms.assetid: 73324c99-adca-46dc-b516-ef78b7235f59
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# User Interface: Advanced Group Policy Management
-
-
-Advanced Group Policy Management (AGPM) adds a **Change Control** node to each domain displayed in the **Group Policy Management Console** (GPMC). In an environment where multiple domains are managed with the GPMC, each domain is listed under the **Domains** node in the console tree. Each domain has a **Change Control** node under it, and there is one archive of Group Policy objects (GPOs) per domain.
-
-Within the details pane there are three primary tabs, providing access to both GPO-level settings and domain-level settings and commands for AGPM.
-
-- [Contents Tab](contents-tab.md): GPO settings and commands and GPO-level delegation
-
-- [Domain Delegation Tab](domain-delegation-tab.md): AGPM e-mail notification settings and domain-level delegation
-
-- [AGPM Server Tab](agpm-server-tab.md): Domain-level archive connection settings
-
-Other enhancements and settings:
-
-- [Administrative Template Settings](administrative-template-settings.md): Central configuration of logging and tracing, archive locations, and the visibility of features
-
-- [Other Enhancements to the GPMC](other-enhancements-to-the-gpmc.md): AGPM adds a **History** tab and an **Extensions** tab for each GPO and Group Policy link
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/using-a-test-environment.md b/mdop/agpm/using-a-test-environment.md
deleted file mode 100644
index 37535bf276..0000000000
--- a/mdop/agpm/using-a-test-environment.md
+++ /dev/null
@@ -1,40 +0,0 @@
----
-title: Using a Test Environment
-description: Using a Test Environment
-author: dansimp
-ms.assetid: fc5fcc7c-1ac8-483a-a6bd-2279ae2ee3fb
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Using a Test Environment
-
-
-Before you request that a Group Policy Object (GPO) be deployed to the production environment, you should test the GPO in a lab environment. If you develop the GPO in a domain in a test forest, you can export the GPO to a file and import the file to a domain in the production forest. You can then test the GPO by linking it to an organizational unit (OU) that contains test computers and users.
-
-- [Export a GPO to a File](export-a-gpo-to-a-file.md)
-
-- [Import a GPO from a File](import-a-gpo-from-a-file-ed.md)
-
-- [Test a GPO in a Separate Organizational Unit](test-a-gpo-in-a-separate-organizational-unit-agpm40.md)
-
-**Note**
-You can also import a GPO from the production environment of the domain. For more information, see [Import a GPO from Production](import-a-gpo-from-production-agpm40-ed.md).
-
-
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/whats-new-in-agpm-30.md b/mdop/agpm/whats-new-in-agpm-30.md
deleted file mode 100644
index 0483edc1f5..0000000000
--- a/mdop/agpm/whats-new-in-agpm-30.md
+++ /dev/null
@@ -1,75 +0,0 @@
----
-title: What's New in AGPM 3.0
-description: What's New in AGPM 3.0
-author: dansimp
-ms.assetid: 0d082b86-63c5-45ce-9529-6e5f37254f9d
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# What's New in AGPM 3.0
-
-
-Microsoft Advanced Group Policy Management (AGPM) 3.0 includes the following new or changed features:
-
-- Support for Windows Server 2008 and Windows Vista with Service Pack 1 that includes 32-bit and 64-bit versions
-
-- Improved installation process
-
-- Simplified procedure for modifying the port on which the AGPM Server listens
-
-- More detailed information in the History of each GPO
-
-- Ability to delegate access to the production environment from AGPM
-
-- Ability to limit the number of GPO versions stored in the archive
-
-- Ability to configure e-mail security for AGPM
-
-- Friendlier names for AGPM policy settings
-
-- The Editor role now requires permission to delete GPOs from the archive
-
-Additionally, AGPM 3.0 is localized for the following languages:
-
-- Chinese (Simplified)
-
-- Chinese (Taiwan)
-
-- English (U.S.)
-
-- French
-
-- German
-
-- Italian
-
-- Japanese
-
-- Korean
-
-- Portuguese (Brazil)
-
-- Russian
-
-- Spanish
-
-### Additional considerations
-
-AGPM 3.0 supports Windows Server 2008 and Windows Vista with SP1. It does not support Windows Server 2003 or Windows Vista with no service packs installed. AGPM 2.5 supports those environments. For more information, see [Choosing Which Version of AGPM to Install](choosing-which-version-of-agpm-to-install.md).
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/whats-new-in-agpm-40-sp1.md b/mdop/agpm/whats-new-in-agpm-40-sp1.md
deleted file mode 100644
index 6151532df1..0000000000
--- a/mdop/agpm/whats-new-in-agpm-40-sp1.md
+++ /dev/null
@@ -1,213 +0,0 @@
----
-title: What's New in AGPM 4.0 SP1
-description: What's New in AGPM 4.0 SP1
-author: dansimp
-ms.assetid: c6a3d94a-13c3-44e6-a466-c3011879999e
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 08/30/2016
----
-
-
-# What's New in AGPM 4.0 SP1
-
-
-This “What’s New” content describes enhancements and supported configurations for Microsoft Advanced Group Policy Management (AGPM) 4.0 SP1. If there is a difference between this content and other AGPM documentation, this content should be considered authoritative and should supersede the content included with this product.
-
-## What’s new
-
-
-AGPM 4.0 SP1 supports the following enhancements:
-
-### New and changed client-side extensions
-
-Group Policy client-side extensions (CSEs) have been added or changed for AGPM to support new Group Policies in Windows 8 and Windows Server 2012. These group policies enable Group Policy administrators to manage and track Windows 8-specific Group Policy settings that change between two Group Policy Objects (GPOs) or templates. You can also create custom GPOs, with Windows 8-specific settings, and configure and save the GPOs as a template. To view your CSEs, use the settings and difference reports that are available in the AGPM 4.0 SP1 client.
-
-The new and changed Group Policy client-side extensions are:
-
-- **Central Access Policy:** Enables Group Policy administrators to specify Central Access Policies on Group Policy servers, for example, file servers. Central Access Policy is an authorization policy that is specified by a GPO item and applied to policy targets to facilitate centralized access and control of resources. These Central Access Policies must be configured on a Group Policy client computer from within Active Directory. A Group Policy distributes the knowledge of an applicable Central Access Policy to the computers that have to enforce it.
-
-- **Name Resolution Policy changes:** Enables Group Policy administrators to configure settings for DNS security and DirectAccess on DNS client computers. New tabs for configuring Generic DNS Server settings and Encoding settings have been added.
-
-- **Group Policy Preference changes:** Adds support for the configuration and management of Internet Explorer 10 settings that were added for Windows 8.
-
-- **Remote Application and Desktop Connections:** Lets Group Policy administrators specify the default connection URL that is used for Remote Application and Desktop Connections.
-
-- **Windows To Go Startup Options:** Lets Group Policy administrators configure whether the computer will boot to Windows To Go if a USB device that contains a Windows To Go workspace is connected.
-
-- **Windows To Go Hibernate Options:** Lets Group Policy administrators configure whether a computer can use the hibernation sleep state (S4) when the computer is started from a Windows To Go workspace.
-
-### Customer feedback and hotfix rollup
-
-AGPM 4.0 SP1 includes a rollup of fixes to address issues found since the AGPM 4.0 release. AGPM 4.0 SP1 contains the latest fixes up to and including Microsoft Advanced Group Policy Management 4.0 Hotfix 1.
-
-### Settings and difference reports show new Group Policy extensions
-
-The new Group Policy extensions have been added to the settings and difference reports.
-
-### Installer changes and support
-
-The changes and support for the AGPM 4.0 SP1 installer are:
-
-- If you install AGPM 4.0 SP1 on Windows 8 or Windows Server 2012, the AGPM installer verifies that the required prerequisite software (Group Policy Management Console and the .NET 3.5 Framework) is installed. If these prerequisites are not installed, the AGPM 4.0 SP1 installation is blocked.
-
-- When you install AGPM 4.0 SP1, WCF Activation, Non-HTTP Activation, and Windows Process Activation Service are automatically enabled.
-
-- On Windows Vista, Windows 7, and Windows 8 client operating systems, download the appropriate version of the Remote System Administration Toolkit for your operating system before you install AGPM 4.0 SP1.
-
-- Backward compatibility with older supported operating systems is supported.
-
-### Ability to upgrade or update to AGPM 4.0 SP1 without re-entering configuration parameters
-
-You can upgrade the AGPM client or server to AGPM 4.0 SP1 only from AGPM 4.0 without being prompted to re-enter configuration parameters (called “Smart Upgrade”), as shown in the following table. If you are upgrading to AGPM 4.0 SP1 from other versions of AGPM, as shown in the table, you must use the “Classic Upgrade,” which requires you to re-enter the configuration parameters. Since each version of AGPM is associated with a particular operating system, refer to [Choosing Which Version of AGPM to Install](https://go.microsoft.com/fwlink/?LinkId=254350), and be sure to upgrade your operating system as appropriate before performing an upgrade.
-
-
-
-
-
-
-
-
-
-
-
-
AGPM Version From Which You Can Upgrade
-
2.5
-
3.0
-
4.0
-
4.0 SP1
-
-
-
2.5
-
Not Applicable
-
Classic Upgrade
-
Classic Upgrade
-
Installation is blocked
-
-
-
3.0
-
Not Applicable
-
Not Applicable
-
Classic Upgrade
-
Installation is blocked
-
-
-
4.0
-
Not Applicable
-
Not Applicable
-
Not Applicable
-
Smart Upgrade
-
-
-
-
-
-
-## Supported configurations
-
-
-AGPM supports the configurations in the following table. Although AGPM supports mixed configurations, it is strongly recommended that you run the AGPM client and server on the same operating system family, for example, Windows 8 with Windows Server 2012, Windows 7 with Windows Server 2008 R2, and so on.
-
-
-
-
-
-
-
-
-
-
Supported Configurations for AGPM 4.0 SP1 Server
-
Supported Configurations for AGPM 4.0 SP1 Client
-
AGPM 4.0 SP1 Support
-
-
-
Windows 8 or Windows Server 2012
-
Windows 8 or Windows Server 2012
-
Supported
-
-
-
Windows Server 2008 R2 or Windows 7
-
Windows Server 2008 R2 or Windows 7
-
Supported, but cannot edit policy settings or preference items that exist only in Windows 8
-
-
-
Windows Server 2008 R2 or Windows 7 or Windows 8 or Windows Server 2012
-
Windows Server 2008 or Windows Vista with SP1
-
Supported, but cannot edit policy settings or preference items that exist only in Windows Server 2008 R2 or Windows 7 or Windows 8.
-
-
-
Windows Server 2008 or Windows Vista with SP1
-
Windows Server 2008 R2 or Windows 7 or Windows 8 or Windows Server 2012
-
Supported
-
-
-
Windows Server 2008 or Windows Vista with SP1
-
Windows Server 2008 or Windows Vista with SP1
-
Supported, but cannot report or edit policy settings or preference items that exist only in Windows Server 2008 R2 or Windows 7 or Windows 8
-
-
-
-
-
-
-## Prerequisites for installing AGPM 4.0 SP1
-
-
-The following table describes the behavior on Windows 8 of AGPM 4.0 SP1 client and server installers when .NET 3.5 or the Group Policy Management Console in the Remote Server Administration Tools (RSAT) is missing.
-
-**AGPM Client 4.0 SP1**
-
-**AGPM Server 4.0 SP1**
-
-**Operating System**
-
-**.NET**
-
-**RSAT**
-
-**.NET**
-
-**RSAT**
-
-**Windows 8**
-
-If .NET 3.5 is not enabled or installed, the installer blocks the installation.
-
-If GPMC is not enabled or installed on the system, the installer blocks the installation.
-
-If .NET 3.5 is not enabled or installed, the installer blocks the installation.
-
-If GPMC is not enabled or installed on the system, the installer blocks the installation.
-
-**Windows Server 2012**
-
-If .NET 3.5 is not enabled or installed, the installer blocks the installation.
-
-If GPMC is not enabled, the installer enables it during the installation.
-
-If .NET 3.5 is not enabled or installed, the installer blocks the installation.
-
-If GPMC is not enabled, the installer enables it during the installation.
-
-
-
-## Related topics
-
-
-[Advanced Group Policy Management](index.md)
-
-[Release Notes for Microsoft Advanced Group Policy Management 4.0 SP1](release-notes-for-microsoft-advanced-group-policy-management-40-sp1.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/whats-new-in-agpm-40-sp2.md b/mdop/agpm/whats-new-in-agpm-40-sp2.md
deleted file mode 100644
index 407487d485..0000000000
--- a/mdop/agpm/whats-new-in-agpm-40-sp2.md
+++ /dev/null
@@ -1,242 +0,0 @@
----
-title: What's New in AGPM 4.0 SP2
-description: What's New in AGPM 4.0 SP2
-author: dansimp
-ms.assetid: 5c0dcab4-f27d-4153-8b8e-b280b080be51
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 08/30/2016
----
-
-
-# What's New in AGPM 4.0 SP2
-
-
-This content describes enhancements and supported configurations for Microsoft Advanced Group Policy Management (AGPM) 4.0 Service Pack 2 (SP2). If there is a difference between this content and other AGPM documentation, consider this content authoritative and assume that it supersedes the other documentation.
-
-## What’s new
-
-
-AGPM 4.0 SP2 supports the following features and functionality.
-
-### Support for Windows 8.1 and Windows Server 2012 R2
-
-AGPM 4.0 SP2 adds support for the Windows 8.1 and Windows Server 2012 R2 operating systems.
-
-### New and changed client-side extensions
-
-Group Policy client-side extensions have been added or changed for AGPM to support new policy settings in Windows 8.1. These policy settings enable Group Policy administrators to manage and track Windows 8.1–specific policy settings that change between two Group Policy Objects (GPOs) or templates. To view your client-side extensions, use the settings and difference reports that are available in the AGPM Client.
-
-The new and changed Group Policy client-side extensions are:
-
-- **Specify Work Folders settings**. If you enable this policy setting, IT administrators can configure Work Folders to be created automatically. The Work Folders feature enables end users to synchronize files from their Windows desktop devices to their other devices. Use this policy setting to create the synchronization relationship on an end user’s devices and to configure how to identify the file server that stores the user’s Work Folders. If you select the **Auto provision synchronization** check box, the synchronization partnership will be created without user input, and data will automatically start synchronizing to the user’s device. If you do not select the **Auto provision synchronization** check box, users must provide input to start the synchronization.
-
-- **Force automatic setup for all users**. If you enable this policy setting, IT administrators can determine whether to create the Work Folders partnership automatically on end-user devices without input from end users. If you enable this policy setting, the synchronization will be set up according to how you configure the **Specify Work Folders settings** policy setting. If you set the **Force automatic setup for all users** policy setting to **Disabled** or **Not configured**, the Work Folders partnership will be configured according to how you set the **Automatic Provisioning** option in the **Specify Work Folders settings** policy setting.
-
-For more information about the Work Folders feature, see [Work Folders Overview](https://go.microsoft.com/fwlink/?LinkId=330444).
-
-### Customer feedback and hotfix rollup
-
-AGPM 4.0 SP2 includes a rollup of hotfixes to address issues found since the AGPM 4.0 Service Pack 1 (SP1) release. AGPM 4.0 SP2 contains the latest fixes up to and including Microsoft Advanced Group Policy Management 4.0 SP1 Hotfix 1. For more information, see Knowledge Base article [2873472](https://go.microsoft.com/fwlink/?LinkId=325400)).
-
-### New Group Policy extensions in settings and difference reports
-
-The new Group Policy extensions have been added to the settings and difference reports.
-
-### Installer changes and support
-
-The changes and support for the AGPM 4.0 SP2 installer are:
-
-- If you install AGPM 4.0 SP2 on the Windows 8 or Windows Server 2012 operating system or later operating systems, the AGPM installer verifies that the required prerequisite software (the Group Policy Management Console (GPMC) and the Microsoft .NET Framework 3.5) is installed. If this prerequisite software is not installed, the AGPM 4.0 SP2 installation is blocked.
-
-- When you install the AGPM Server, WCF Activation, Non-HTTP Activation, and Windows Process Activation Service are automatically enabled.
-
-- On the Windows Vista client operating system and later operating systems, download the appropriate version of the Remote System Administration Tools for your operating system before you install AGPM 4.0 SP2.
-
-- AGPM 4.0 SP2 supports backward compatibility with older supported operating systems.
-
-### Ability to upgrade to AGPM 4.0 SP2 without reentering configuration parameters
-
-You can upgrade the AGPM Client or AGPM Server to AGPM 4.0 SP2 without being prompted to reenter configuration parameters (called the Smart Upgrade) only from AGPM 4.0 onward, as shown in the following table. If you are upgrading to AGPM 4.0 SP2 from other versions of AGPM, as shown in the table, you must use the Classic Upgrade, which requires you to reenter the configuration parameters. Because each version of AGPM is associated with a particular operating system, see [Choosing Which Version of AGPM to Install](https://go.microsoft.com/fwlink/?LinkId=254350) and make sure that you upgrade your operating system as appropriate before you upgrade AGPM.
-
-**AGPM 4.0 SP2 supported upgrades**
-
-
-
-
-
-
-
-
-
-
-
-
-
AGPM version from which you can upgrade
-
2.5
-
3.0
-
4.0
-
4.0 SP1
-
4.0 SP2
-
-
-
2.5
-
Not applicable
-
Classic Upgrade
-
Classic Upgrade
-
Installation is blocked
-
Installation is blocked
-
-
-
3.0
-
Not applicable
-
Not applicable
-
Classic Upgrade
-
Installation is blocked
-
Installation is blocked
-
-
-
4.0
-
Not applicable
-
Not applicable
-
Not applicable
-
Smart Upgrade
-
Smart Upgrade
-
-
-
4.0 SP1
-
Not applicable
-
Not applicable
-
Not applicable
-
Not applicable
-
Smart Upgrade
-
-
-
-
-
-
-## Supported configurations
-
-
-AGPM 4.0 SP2 supports the configurations in the following table. Although AGPM supports mixed configurations, we strongly recommend that you run the AGPM Client and AGPM Server on the same operating system line—for example, Windows 8.1 with Windows Server 2012 R2, Windows 8 with Windows Server 2012, and so on.
-
-**AGPM 4.0 SP2 supported operating systems and policy settings**
-
-
-
-
-
-
-
-
-
-
Supported configurations for the AGPM Server
-
Supported configurations for the AGPM Client
-
AGPM Support
-
-
-
-
-
Windows Server 2012 R2 or Windows 8.1
-
Windows Server 2012 R2 or Windows 8.1
-
Supported
-
-
-
Windows Server 2012 R2, Windows Server 2012, Windows 8.1, or Windows 8
-
Windows Server 2012 or Windows 8
-
Supported, but cannot edit policy settings or preference items that exist only in Windows 8.1
-
-
-
Windows Server 2008 R2 or Windows 7
-
Windows Server 2008 R2 or Windows 7
-
Supported, but cannot edit policy settings or preference items that exist only in Windows 8.1 or Windows 8
-
-
-
Windows Server 2012, Windows Server 2008 R2, Windows 8, or Windows 7
-
Windows Server 2008 or Windows Vista with Service Pack 1 (SP1)
-
Supported, but cannot edit policy settings or preference items that exist only in Windows Server 2012 R2, Windows Server 2012, Windows Server 2008 R2, Windows 8.1, Windows 8, or Windows 7
-
-
-
Windows Server 2008 or Windows Vista with SP1
-
Windows Server 2012, Windows Server 2008 R2, Windows 8, or Windows 7
-
Not supported
-
-
-
Windows Server 2008 or Windows Vista with SP1
-
Windows Server 2008 or Windows Vista with SP1
-
Supported, but cannot report or edit policy settings or preference items that exist only in Windows Server 2012 R2, Windows Server 2012, Windows Server 2008 R2, Windows 8.1, Windows 8, or Windows 7
-
-
-
-
-
-
-## Prerequisites for installing AGPM 4.0 SP2
-
-
-The following table describes the behavior of AGPM 4.0 SP2 Client and Server installers on Windows 8.1 when the .NET Framework 3.5 or the GPMC in the Remote Server Administration Tools is missing.
-
-**AGPM Client**
-
-**AGPM Server**
-
-**Operating system**
-
-**.NET Framework**
-
-**Remote Server Administration Tools**
-
-**.NET Framework**
-
-**Remote Server Administration Tools**
-
-**Windows 8.1**
-
-If the .NET Framework 3.5 is not enabled or installed, the installer blocks the installation.
-
-If the GPMC is not enabled or installed, the installer blocks the installation.
-
-If the .NET Framework 3.5 is not enabled or installed, the installer blocks the installation.
-
-If the GPMC is not enabled or installed, the installer blocks the installation.
-
-**Windows Server 2012 R2**
-
-If the .NET Framework 3.5 is not enabled or installed, the installer blocks the installation.
-
-If the GPMC is not enabled, the installer enables it during the installation.
-
-If the .NET Framework 3.5 is not enabled or installed, the installer blocks the installation.
-
-If the GPMC is not enabled, the installer enables it during the installation.
-
-
-
-## How to Get MDOP Technologies
-
-
-AGPM 4.0 SP2 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](https://go.microsoft.com/fwlink/?LinkId=322049) (https://go.microsoft.com/fwlink/?LinkId=322049).
-
-## Related topics
-
-
-[Advanced Group Policy Management](index.md)
-
-[Release Notes for Microsoft Advanced Group Policy Management 4.0 SP2](release-notes-for-microsoft-advanced-group-policy-management-40-sp2.md)
-
-[Choosing Which Version of AGPM to Install](choosing-which-version-of-agpm-to-install.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/whats-new-in-agpm-40-sp3.md b/mdop/agpm/whats-new-in-agpm-40-sp3.md
deleted file mode 100644
index d60031b011..0000000000
--- a/mdop/agpm/whats-new-in-agpm-40-sp3.md
+++ /dev/null
@@ -1,210 +0,0 @@
----
-title: What's New in AGPM 4.0 SP3
-description: What's New in AGPM 4.0 SP3
-author: dansimp
-ms.assetid: df495d55-9fbf-4f7e-a7af-3905f4f8790e
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 09/27/2016
----
-
-
-# What's New in AGPM 4.0 SP3
-
-
-This content describes enhancements and supported configurations for Microsoft Advanced Group Policy Management (AGPM) 4.0 Service Pack 3 (SP3). If there is a difference between this content and other AGPM documentation, consider this content authoritative and assume that it supersedes the other documentation.
-
-## What’s new
-
-
-AGPM 4.0 SP3 supports the following features and functionality.
-
-### Support for Windows 10
-
-AGPM 4.0 SP3 adds support for the Windows 10 and Windows Server 2016 operating systems.
-
-### Support for PowerShell
-
-AGPM 4.0 SP3 adds support for PowerShell cmdlets. For a list of the cmdlets available in AGPM 4.0 SP3, including descriptions and syntax, see [Microsoft Desktop Optimization Pack Automation with Windows PowerShell](https://docs.microsoft.com/powershell/mdop/get-started?view=win-mdop2-ps).
-
-### Customer feedback and hotfix rollup
-
-AGPM 4.0 SP3 includes a rollup of all fixes up to and including Microsoft Advanced Group Policy Management 4.0 SP2 and any fixes for issues found since AGPM 4.0 SP2.
-
-### Ability to upgrade to AGPM 4.0 SP3 without re-entering configuration parameters
-
-You can upgrade the AGPM Client or AGPM Server to AGPM 4.0 SP3 without being prompted to re-enter configuration parameters (called the Smart Upgrade) only from AGPM 4.0 and later, as shown in the following table. If you are upgrading to AGPM 4.0 SP3 from other versions of AGPM, as shown in the table, you must use the Classic Upgrade, which requires you to re-enter the configuration parameters. Because each version of AGPM is associated with a particular operating system, see [Choosing Which Version of AGPM to Install](https://go.microsoft.com/fwlink/?LinkId=254350) and make sure that you upgrade your operating system as appropriate before you upgrade AGPM.
-
-**AGPM 4.0 SP3 supported upgrades**
-
-
-
-
-
-
-
-
-
-
-
-
-
-
AGPM version from which you can upgrade
-
2.5
-
3.0
-
4.0
-
4.0 SP1
-
4.0 SP2
-
4.0 SP3
-
-
-
2.5
-
Not applicable
-
Classic Upgrade
-
Classic Upgrade
-
Installation is blocked
-
Installation is blocked
-
Installation is blocked
-
-
-
3.0
-
Not applicable
-
Not applicable
-
Classic Upgrade
-
Installation is blocked
-
Installation is blocked
-
Installation is blocked
-
-
-
4.0
-
Not applicable
-
Not applicable
-
Not applicable
-
Smart Upgrade
-
Smart Upgrade
-
Smart Upgrade
-
-
-
4.0 SP1
-
Not applicable
-
Not applicable
-
Not applicable
-
Not applicable
-
Smart Upgrade
-
Smart Upgrade
-
-
-
4.0 SP2
-
Not applicable
-
Not applicable
-
Not applicable
-
Not applicable
-
Not applicable
-
Smart Upgrade
-
-
-
-
-
-
-## Supported configurations
-
-
-AGPM 4.0 SP3 supports the configurations in the following table. Although AGPM supports mixed configurations, we strongly recommend that you run the AGPM Client and AGPM Server on the same operating system line—for example, Windows 10 with Windows Server 2016, Windows 8.1 with Windows Server 2012 R2, and so on.
-
-**AGPM 4.0 SP3 supported operating systems and policy settings**
-
-
-
-
-
-
-
-
-
-
Supported configurations for the AGPM Server
-
Supported configurations for the AGPM Client
-
AGPM Support
-
-
-
-
-
Windows Server 2016 or Windows 10
-
Windows 10
-
Supported
-
-
-
Windows Server 2012 R2 or Windows 8.1
-
Windows Server 2012 R2 or Windows 8.1
-
Supported
-
-
-
Windows Server 2012 R2, Windows Server 2012, or Windows 8.1
-
Windows Server 2012
-
Supported, but cannot edit policy settings or preference items that exist only in Windows 8.1
-
-
-
Windows Server 2008 R2 or Windows 7
-
Windows Server 2008 R2 or Windows 7
-
Supported, but cannot edit policy settings or preference items that exist only in Windows 8.1
-
-
-
Windows Server 2012, Windows Server 2008 R2, or Windows 7
-
Windows Server 2008 or Windows Vista with Service Pack 1 (SP1)
-
Supported, but cannot edit policy settings or preference items that exist only in Windows Server 2012 R2, Windows Server 2012, Windows Server 2008 R2, Windows 8.1, or Windows 7
-
-
-
Windows Server 2008 or Windows Vista with SP1
-
Windows Server 2012, Windows Server 2008 R2, or Windows 7
-
Not supported
-
-
-
Windows Server 2008 or Windows Vista with SP1
-
Windows Server 2008 or Windows Vista with SP1
-
Supported, but cannot report or edit policy settings or preference items that exist only in Windows Server 2012 R2, Windows Server 2012, Windows Server 2008 R2, Windows 8.1, or Windows 7
-
-
-
-
-
-
-## Prerequisites for installing AGPM 4.0 SP3
-
-The following table describes the behavior of AGPM 4.0 SP3 Client and Server installers when the .NET Framework 4.5.1, PowerShell 3.0, or the GPMC in the Remote Server Administration Tools is missing.
-
-| AGPM Client | | | AGPM Server | | |
-|------------------------|-------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------|---------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------|
-| Operating system | .NET Framework | PowerShell | Remote Server Administration Tools | .NET Framework | Remote Server Administration Tools |
-| Windows 10 | If the .NET Framework 4.5.1 is not enabled or installed, the installer blocks the installation. | If Powershell 3.0 is not installed, the installer blocks the installation. | If the GPMC is not enabled or installed, the installer blocks the installation. | If the .NET Framework 4.5.1 is not enabled or installed, the installer blocks the installation. | If the GPMC is not enabled or installed, the installer blocks the installation. |
-| Windows 8.1 | If the .NET Framework 4.5.1 is not enabled or installed, the installer blocks the installation. | If Powershell 3.0 is not installed, the installer blocks the installation. | If the GPMC is not enabled or installed, the installer blocks the installation. | If the .NET Framework 4.5.1 is not enabled or installed, the installer blocks the installation. | If the GPMC is not enabled or installed, the installer blocks the installation. |
-| Windows Server 2012 R2 | If the .NET Framework 4.5.1 is not enabled or installed, the installer blocks the installation. | If Powershell 3.0 is not installed, the installer blocks the installation. | If the GPMC is not enabled, the installer enables it during the installation. | If the .NET Framework 4.5.1 is not enabled or installed, the installer blocks the installation. | If the GPMC is not enabled, the installer enables it during the installation. |
-
-
-
-## How to Get MDOP Technologies
-
-
-AGPM 4.0 SP3 is a part of the Microsoft Desktop Optimization Pack (MDOP) since MDOP 2015. MDOP is part of Microsoft Software Assurance. For more information about Microsoft Software Assurance and acquiring MDOP, see [How Do I Get MDOP](https://go.microsoft.com/fwlink/?LinkId=322049) (https://go.microsoft.com/fwlink/?LinkId=322049).
-
-## Related topics
-
-
-[Advanced Group Policy Management](index.md)
-
-[Release Notes for Microsoft Advanced Group Policy Management 4.0 SP3](release-notes-for-microsoft-advanced-group-policy-management-40-sp3.md)
-
-[Choosing Which Version of AGPM to Install](choosing-which-version-of-agpm-to-install.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/agpm/whats-new-in-agpm-40.md b/mdop/agpm/whats-new-in-agpm-40.md
deleted file mode 100644
index 280c395196..0000000000
--- a/mdop/agpm/whats-new-in-agpm-40.md
+++ /dev/null
@@ -1,87 +0,0 @@
----
-title: What's New in AGPM 4.0
-description: What's New in AGPM 4.0
-author: dansimp
-ms.assetid: 31775f7f-a59c-4e64-a875-0adc9f5bc835
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop
-ms.mktglfcycl: manage
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# What's New in AGPM 4.0
-
-
-Microsoft Advanced Group Policy Management (AGPM) 4.0 includes new features that let you search for Group Policy Objects (GPOs), filter the list of GPOs displayed, export and import a GPO to a different forest, and install AGPM on computers running Windows 7 and Windows Server 2008 R2.
-
-## Search and filter GPOs
-
-
-In AGPM 4.0, you can search the list of GPOs for specific attributes to filter the list of GPOs displayed. For example, you can search for GPOs with a particular name, state, or comment. You can also search for GPOs that were last changed by a particular Group Policy administrator or on a particular date.
-
-You can create a complex search string by using the format *GPO attribute 1: search text 1 GPO attribute 2: search text 2…*, where a GPO attribute is any column heading in the list of GPOs in AGPM. For example, to search for all GPOs with names including the text "MyGPO" that are checked in and were last changed by the user Editor03, you would type the following in the Search box: **name: MyGPO state:** **checked in** **changed by: Editor03**. The search returns partial matches so that you can enter part of a GPO name or user name and view a list of all GPOs that include that text in their name.
-
-Additionally, you can use the same special terms available when you search in Windows to search for GPOs changed on a specific date or range of dates. For example, **change date:** **lastmonth** or **change date:** **thisweek**.
-
-## Export and import GPOs to different forests
-
-
-Using AGPM 4.0, you can copy a controlled GPO from a domain in one forest to a domain in a second forest. For example, you can export a GPO from a domain in one forest to a CAB file by using AGPM, copy that CAB file to a USB drive, plug the USB drive into a computer in a domain in a second forest, and import the GPO into AGPM in a domain in the second forest. You can either import the GPO as a new controlled GPO, or import it to replace the settings of an existing GPO that is checked out.
-
-## Support for Windows Server 2008 R2 and Windows 7
-
-
-AGPM 4.0 supports Windows Server 2008 R2 and Windows 7, yet still supports Windows Server 2008 and Windows Vista® with Service Pack 1 (SP1). However, there are limitations in a mixed environment that includes both the newer and older operating systems, as indicated in the following table.
-
-
-
-
-
-
-
-
-
-
Operating system on which AGPM Server 4.0 runs
-
Operating system on which AGPM Client 4.0 runs
-
Status of AGPM 4.0 support
-
-
-
-
-
Windows Server 2008 R2 or Windows 7
-
Windows Server 2008 R2 or Windows 7
-
Supported
-
-
-
Windows Server 2008 R2 or Windows 7
-
Windows Server 2008 or Windows Vista with SP1
-
Supported, but cannot edit policy settings or preference items that exist only in Windows Server 2008 R2 or Windows 7
-
-
-
Windows Server 2008 or Windows Vista with SP1
-
Windows Server 2008 R2 or Windows 7
-
Unsupported
-
-
-
Windows Server 2008 or Windows Vista with SP1
-
Windows Server 2008 or Windows Vista with SP1
-
Supported, but cannot report or edit policy settings or preference items that exist only in Windows Server 2008 R2 or Windows 7
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/TOC.md b/mdop/appv-v4/TOC.md
deleted file mode 100644
index 743199d765..0000000000
--- a/mdop/appv-v4/TOC.md
+++ /dev/null
@@ -1,649 +0,0 @@
-# [Application Virtualization 4](index.md)
-## [Getting Started Guide](microsoft-application-virtualization-getting-started-guide.md)
-### [Overview of Application Virtualization](overview-of-application-virtualization.md)
-### [Planning for Application Virtualization System Deployment](planning-for-application-virtualization-system-deployment.md)
-#### [Best Practices for the Application Virtualization Sequencer](best-practices-for-the-application-virtualization-sequencer-sp1.md)
-#### [Planning the Application Virtualization Sequencer Implementation](planning-the-application-virtualization-sequencer-implementation.md)
-#### [Using Electronic Software Distribution as a Package Management Solution](using-electronic-software-distribution-as-a-package-management-solution.md)
-##### [Publishing Virtual Applications Using Electronic Software Distribution](publishing-virtual-applications-using-electronic-software-distribution.md)
-##### [Planning Your Streaming Solution in an Electronic Software Distribution Implementation](planning-your-streaming-solution-in-an-electronic-software-distribution-implementation.md)
-#### [Using Application Virtualization Servers as a Package Management Solution](using-application-virtualization-servers-as-a-package-management-solution.md)
-##### [Overview of the Application Virtualization System Components](overview-of-the-application-virtualization-system-components.md)
-##### [Publishing Virtual Applications Using Application Virtualization Management Servers](publishing-virtual-applications-using-application-virtualization-management-servers.md)
-##### [Planning Your Streaming Solution in an Application Virtualization Server-Based Implementation](planning-your-streaming-solution-in-an-application-virtualization-server-based-implementation.md)
-#### [Planning for Application Virtualization Client Deployment](planning-for-application-virtualization-client-deployment.md)
-#### [Planning for Migration from Previous Versions](planning-for-migration-from-previous-versions.md)
-#### [Planning for Security and Protection](planning-for-security-and-protection.md)
-##### [Security and Protection Overview](security-and-protection-overview.md)
-##### [Planning for Server Security](planning-for-server-security.md)
-##### [Planning for Client Security](planning-for-client-security.md)
-##### [Planning for Sequencer Security](planning-for-sequencer-security.md)
-### [Application Virtualization Deployment and Upgrade Considerations](application-virtualization-deployment-and-upgrade-considerations-copy.md)
-#### [Application Virtualization Deployment Requirements](application-virtualization-deployment-requirements.md)
-##### [Application Virtualization System Requirements](application-virtualization-system-requirements.md)
-##### [Application Virtualization Sequencer Hardware and Software Requirements](application-virtualization-sequencer-hardware-and-software-requirements.md)
-##### [Application Virtualization Client Hardware and Software Requirements](application-virtualization-client-hardware-and-software-requirements.md)
-#### [Application Virtualization Deployment and Upgrade Checklists](application-virtualization-deployment-and-upgrade-checklists.md)
-##### [App-V Pre-Installation Checklist](app-v-pre-installation-checklist.md)
-##### [App-V Installation Checklist](app-v-installation-checklist.md)
-##### [App-V Postinstallation Checklist](app-v-postinstallation-checklist.md)
-##### [App-V Upgrade Checklist](app-v-upgrade-checklist.md)
-#### [How to Install the Servers and System Components](how-to-install-the-servers-and-system-components.md)
-##### [How to Install Application Virtualization Management Server](how-to-install-application-virtualization-management-server.md)
-##### [How to Install the Application Virtualization Streaming Server](how-to-install-the-application-virtualization-streaming-server.md)
-##### [How to Install the Management Web Service](how-to-install-the-management-web-service.md)
-##### [How to Install the Management Console](how-to-install-the-management-console.md)
-##### [How to Install a Database](how-to-install-a-database.md)
-##### [How to Remove the Application Virtualization System Components](how-to-remove-the-application-virtualization-system-components.md)
-#### [How to Manually Install the Application Virtualization Client](how-to-manually-install-the-application-virtualization-client.md)
-#### [How to Install the Application Virtualization Sequencer](how-to-install-the-application-virtualization-sequencer.md)
-#### [How to Upgrade the Application Virtualization Client](how-to-upgrade-the-application-virtualization-client.md)
-#### [How to Upgrade the Servers and System Components](how-to-upgrade-the-servers-and-system-components.md)
-#### [How to Upgrade the Application Virtualization Sequencer](how-to-upgrade-the-application-virtualization-sequencer.md)
-### [About Microsoft Application Virtualization 4.5](about-microsoft-application-virtualization-45.md)
-#### [App-V 4.5 Release Notes](microsoft-application-virtualization-management-system-release-notes.md)
-### [About Microsoft Application Virtualization 4.5 SP1](about-microsoft-application-virtualization-45-sp1.md)
-#### [App-V 4.5 SP1 Release Notes](microsoft-application-virtualization-management-system-release-notes-45-sp1.md)
-### [About Microsoft Application Virtualization 4.5 SP2](about-microsoft-application-virtualization-45-sp2.md)
-#### [App-V 4.5 SP2 Release Notes](app-v-45-sp2-release-notes.md)
-### [About Microsoft Application Virtualization 4.6](about-microsoft-application-virtualization-46.md)
-#### [App-V 4.6 Release Notes](app-v-46-release-notes.md)
-### [About Microsoft Application Virtualization 4.6 SP1](about-microsoft-application-virtualization-46-sp1.md)
-#### [App-V 4.6 SP1 Release Notes](app-v-46-sp1-release-notes.md)
-### [About Microsoft Application Virtualization 4.6 SP2](about-microsoft-application-virtualization-46-sp2.md)
-#### [App-V 4.6 SP2 Release Notes](app-v-46-sp2-release-notes.md)
-### [About Microsoft Application Virtualization 4.6 SP3](about-microsoft-application-virtualization-46-sp3.md)
-#### [App-V 4.6 SP3 Release Notes](app-v-46-sp3-release-notes.md)
-## [Planning and Deployment](planning-and-deployment-guide-for-the-application-virtualization-system.md)
-### [Planning for Application Virtualization System Deployment](planning-for-application-virtualization-system-deployment.md)
-#### [Best Practices for the Application Virtualization Sequencer](best-practices-for-the-application-virtualization-sequencer-sp1.md)
-#### [Planning the Application Virtualization Sequencer Implementation](planning-the-application-virtualization-sequencer-implementation.md)
-#### [Using Electronic Software Distribution as a Package Management Solution](using-electronic-software-distribution-as-a-package-management-solution.md)
-##### [Publishing Virtual Applications Using Electronic Software Distribution](publishing-virtual-applications-using-electronic-software-distribution.md)
-##### [Planning Your Streaming Solution in an Electronic Software Distribution Implementation](planning-your-streaming-solution-in-an-electronic-software-distribution-implementation.md)
-#### [Using Application Virtualization Servers as a Package Management Solution](using-application-virtualization-servers-as-a-package-management-solution.md)
-##### [Overview of the Application Virtualization System Components](overview-of-the-application-virtualization-system-components.md)
-##### [Publishing Virtual Applications Using Application Virtualization Management Servers](publishing-virtual-applications-using-application-virtualization-management-servers.md)
-##### [Planning Your Streaming Solution in an Application Virtualization Server-Based Implementation](planning-your-streaming-solution-in-an-application-virtualization-server-based-implementation.md)
-#### [Planning for Application Virtualization Client Deployment](planning-for-application-virtualization-client-deployment.md)
-#### [Planning for Migration from Previous Versions](planning-for-migration-from-previous-versions.md)
-#### [Planning for Security and Protection](planning-for-security-and-protection.md)
-##### [Security and Protection Overview](security-and-protection-overview.md)
-##### [Planning for Server Security](planning-for-server-security.md)
-##### [Planning for Client Security](planning-for-client-security.md)
-##### [Planning for Sequencer Security](planning-for-sequencer-security.md)
-### [Application Virtualization Deployment and Upgrade Considerations](application-virtualization-deployment-and-upgrade-considerations.md)
-#### [Application Virtualization Deployment Requirements](application-virtualization-deployment-requirements.md)
-##### [Application Virtualization System Requirements](application-virtualization-system-requirements.md)
-##### [Application Virtualization Sequencer Hardware and Software Requirements](application-virtualization-sequencer-hardware-and-software-requirements.md)
-##### [Application Virtualization Client Hardware and Software Requirements](application-virtualization-client-hardware-and-software-requirements.md)
-##### [Configuring Prerequisite Groups in Active Directory for App-V](configuring-prerequisite-groups-in-active-directory-for-app-v.md)
-##### [How to Configure Windows Server 2008 for App-V Management Servers](how-to-configure-windows-server-2008-for-app-v-management-servers.md)
-#### [How to Upgrade the Servers and System Components](how-to-upgrade-the-servers-and-system-components.md)
-#### [How to Upgrade the Application Virtualization Client](how-to-upgrade-the-application-virtualization-client.md)
-#### [How to Upgrade the Application Virtualization Sequencer](how-to-upgrade-the-application-virtualization-sequencer.md)
-#### [How to Install the Application Virtualization Sequencer](how-to-install-the-application-virtualization-sequencer.md)
-### [Electronic Software Distribution-Based Scenario](electronic-software-distribution-based-scenario.md)
-#### [Electronic Software Distribution-Based Scenario Overview](electronic-software-distribution-based-scenario-overview.md)
-##### [Determine Your Publishing Method](determine-your-publishing-method.md)
-##### [Determine Your Streaming Method](determine-your-streaming-method.md)
-#### [How to Configure Servers for ESD-Based Deployment](how-to-configure-servers-for-esd-based-deployment.md)
-##### [How to Configure the Application Virtualization Streaming Servers](how-to-configure-the-application-virtualization-streaming-servers.md)
-##### [How to Configure the Server for IIS](how-to-configure-the-server-for-iis.md)
-##### [How to Configure the File Server](how-to-configure-the-file-server.md)
-#### [How to Install the Client by Using the Command Line](how-to-install-the-client-by-using-the-command-line-new.md)
-##### [How to Install the App-V Client by Using Setup.exe](how-to-install-the-app-v-client-by-using-setupexe-new.md)
-##### [How to Install the App-V Client by Using Setup.msi](how-to-install-the-app-v-client-by-using-setupmsi-new.md)
-#### [How to Uninstall the App-V Client](how-to-uninstall-the-app-v-client.md)
-#### [How to Publish a Virtual Application on the Client](how-to-publish-a-virtual-application-on-the-client.md)
-### [Application Virtualization Server-Based Scenario](application-virtualization-server-based-scenario.md)
-#### [Application Virtualization Server-Based Scenario Overview](application-virtualization-server-based-scenario-overview.md)
-#### [How to Install the Servers and System Components](how-to-install-the-servers-and-system-components.md)
-##### [How to Install Application Virtualization Management Server](how-to-install-application-virtualization-management-server.md)
-##### [How to Install the Application Virtualization Streaming Server](how-to-install-the-application-virtualization-streaming-server.md)
-##### [How to Install the Management Web Service](how-to-install-the-management-web-service.md)
-##### [How to Install the Management Console](how-to-install-the-management-console.md)
-##### [How to Install a Database](how-to-install-a-database.md)
-##### [How to Remove the Application Virtualization System Components](how-to-remove-the-application-virtualization-system-components.md)
-#### [How to Configure Servers for Server-Based Deployment](how-to-configure-servers-for-server-based-deployment.md)
-##### [How to Configure the Application Virtualization Management Servers](how-to-configure-the-application-virtualization-management-servers.md)
-##### [How to Configure the Application Virtualization Streaming Servers](how-to-configure-the-application-virtualization-streaming-servers.md)
-##### [How to Configure the Server for IIS](how-to-configure-the-server-for-iis.md)
-##### [How to Configure the Server to be Trusted for Delegation](how-to-configure-the-server-to-be-trusted-for-delegation.md)
-##### [Configuring the Firewall for the App-V Servers](configuring-the-firewall-for-the-app-v-servers.md)
-##### [How to Install and Configure the Default Application](how-to-install-and-configure-the-default-application.md)
-#### [How to Configure a Read-only Cache on the App-V Client (VDI)](how-to-configure-a-read-only-cache-on-the-app-v-client--vdi-.md)
-#### [How to Configure a Read-only Cache on the App-V Client (RDS)](how-to-configure-a-read-only-cache-on-the-app-v-client--rds--sp1.md)
-#### [How to Configure Microsoft SQL Server Mirroring Support for App-V](how-to-configure-microsoft-sql-server-mirroring-support-for-app-v.md)
-### [Stand-Alone Delivery Scenario for Application Virtualization Clients](stand-alone-delivery-scenario-for-application-virtualization-clients.md)
-#### [Stand-Alone Delivery Scenario Overview](stand-alone-delivery-scenario-overview.md)
-#### [How to Manually Install the Application Virtualization Client](how-to-manually-install-the-application-virtualization-client.md)
-#### [How to Publish a Virtual Application on the Client](how-to-publish-a-virtual-application-on-the-client.md)
-### [Application Virtualization Reference](application-virtualization-reference.md)
-#### [Application Virtualization Client Installer Command-Line Parameters](application-virtualization-client-installer-command-line-parameters.md)
-#### [SFTMIME Command Reference](sftmime--command-reference.md)
-##### [ADD APP](add-app.md)
-##### [ADD PACKAGE](add-package.md)
-##### [ADD SERVER](add-server.md)
-##### [ADD TYPE](add-type.md)
-##### [CLEAR APP](clear-app.md)
-##### [CLEAR OBJ](clear-obj.md)
-##### [CONFIGURE APP](configure-app.md)
-##### [CONFIGURE PACKAGE](configure-package.md)
-##### [CONFIGURE SERVER](configure-server.md)
-##### [CONFIGURE TYPE](configure-type.md)
-##### [DELETE APP](delete-app.md)
-##### [DELETE OBJ](delete-obj.md)
-##### [DELETE PACKAGE](delete-package.md)
-##### [DELETE SERVER](delete-server.md)
-##### [DELETE TYPE](delete-type.md)
-##### [HELP](help.md)
-##### [LOAD APP](load-app.md)
-##### [LOAD PACKAGE](load-package.md)
-##### [LOCK APP](lock-app.md)
-##### [PUBLISH APP](publish-app.md)
-##### [PUBLISH PACKAGE](publish-package.md)
-##### [QUERY OBJ](query-obj.md)
-##### [REFRESH SERVER](refresh-server.md)
-##### [REPAIR APP](repair-app.md)
-##### [UNLOAD APP](unload-app.md)
-##### [UNLOAD PACKAGE](unload-package.md)
-##### [UNLOCK APP](unlock-app.md)
-##### [UNPUBLISH PACKAGE](unpublish-package.md)
-## [Operations](operations-guide-for-the-application-virtualization-system.md)
-### [Application Virtualization Client](application-virtualization-client.md)
-#### [How to Use the Desktop Notification Area for Application Virtualization Client Management](how-to-use-the-desktop-notification-area-for-application-virtualization-client-management.md)
-##### [How to Refresh Virtual Applications from the Desktop Notification Area](how-to-refresh-virtual-applications-from-the-desktop-notification-area.md)
-##### [How to Load Virtual Applications from the Desktop Notification Area](how-to-load-virtual-applications-from-the-desktop-notification-area.md)
-##### [How to Cancel Loading of Virtual Applications from the Desktop Notification Area](how-to-cancel-loading-of-virtual-applications-from-the-desktop-notification-area.md)
-##### [How to Work Offline or Online with Application Virtualization](how-to-work-offline-or-online-with-application-virtualization.md)
-##### [How to Exit the App-V Client from the Notification Area](how-to-exit-the-app-v-client-from-the-notification-area.md)
-#### [How to Manage Virtual Applications Manually](how-to-manage-virtual-applications-manually.md)
-##### [How to Load or Unload an Application](how-to-load-or-unload-an-application.md)
-##### [How to Clear an Application](how-to-clear-an-application.md)
-##### [How to Repair an Application](how-to-repair-an-application.md)
-##### [How to Import an Application](how-to-import-an-application.md)
-##### [How to Lock or Unlock an Application](how-to-lock-or-unlock-an-application.md)
-##### [How to Delete an Application](how-to-delete-an-application.md)
-##### [How to Change an Application Icon](how-to-change-an-application-icon.md)
-##### [How to Add an Application](how-to-add-an-application.md)
-##### [How to Publish Application Shortcuts](how-to-publish-application-shortcuts.md)
-##### [How to Add a File Type Association](how-to-add-a-file-type-association.md)
-##### [How to Delete a File Type Association](how-to-delete-a-file-type-association.md)
-#### [How to Configure the Application Virtualization Client Settings Manually](how-to-configure-the-application-virtualization-client-settings-manually.md)
-##### [How to Perform General Administrative Tasks in the App-V Client Management Console](how-to-perform-general-administrative-tasks-in-the-app-v-client-management-console.md)
-###### [How to Set Up Publishing Servers](how-to-set-up-publishing-servers.md)
-###### [How to Refresh the Publishing Servers](how-to-refresh-the-publishing-servers.md)
-###### [How to Disable or Modify Disconnected Operation Mode Settings](how-to-disable-or-modify-disconnected-operation-mode-settings.md)
-###### [User Access Permissions in Application Virtualization Client](user-access-permissions-in-application-virtualization-client.md)
-###### [Disconnected Operation Mode](disconnected-operation-mode.md)
-##### [How to Configure the Client in the Application Virtualization Client Management Console](how-to-configure-the-client-in-the-application-virtualization-client-management-console.md)
-###### [How to Change the Cache Size and the Drive Letter Designation](how-to-change-the-cache-size-and-the-drive-letter-designation.md)
-###### [How to Change the Log Reporting Levels and Reset the Log Files](how-to-change-the-log-reporting-levels-and-reset-the-log-files.md)
-###### [How to Change User Access Permissions](how-to-change-user-access-permissions.md)
-###### [How to Change Import Search Paths](how-to-change-import-search-paths.md)
-###### [How to Set Up Periodic Publishing Refresh](how-to-set-up-periodic-publishing-refresh.md)
-###### [How to Set Up Publishing Refresh on Login](how-to-set-up-publishing-refresh-on-login.md)
-#### [How to Manage Virtual Applications by Using the Command Line](how-to-manage-virtual-applications-by-using-the-command-line.md)
-##### [How to Add a Package by Using the Command Line](how-to-add-a-package-by-using-the-command-line.md)
-##### [How to Remove a Package by Using the Command Line](how-to-remove-a-package-by-using-the-command-line.md)
-##### [How to Delete All Virtual Applications by Using the Command Line](how-to-delete-all-virtual-applications-by-using-the-command-line.md)
-##### [How to Manage the App-V Client Cache Using Performance Counters](how-to-manage-the-app-v-client-cache-using-performance-counters.md)
-#### [How to Configure the App-V Client Registry Settings by Using the Command Line](how-to-configure-the-app-v-client-registry-settings-by-using-the-command-line.md)
-##### [How to Reset the FileSystem Cache](how-to-reset-the-filesystem-cache.md)
-##### [How to Change the Size of the FileSystem Cache](how-to-change-the-size-of-the-filesystem-cache.md)
-##### [How to Use the Cache Space Management Feature](how-to-use-the-cache-space-management-feature.md)
-##### [How to Configure the Client Log File](how-to-configure-the-client-log-file.md)
-##### [How to Configure User Permissions](how-to-configure-user-permissions.md)
-##### [How to Configure the Client for Application Package Retrieval](how-to-configure-the-client-for-application-package-retrieval.md)
-##### [How to Configure the Client for Disconnected Operation Mode](how-to-configure-the-client-for-disconnected-operation-mode.md)
-##### [How to Configure Shortcut and File Type Association Behavior](how-to-configure-shortcut-and-file-type-association-behavior-46-only.md)
-##### [How to Configure the Client for MIT Kerberos Realm Support](how-to-configure-the-client-for-mit-kerberos-realm-support.md)
-#### [Troubleshooting Information for the Application Virtualization Client](troubleshooting-information-for-the-application-virtualization-client.md)
-#### [Application Virtualization Client Reference](application-virtualization-client-reference.md)
-##### [SFTMIME Command Reference](sftmime--command-reference.md)
-###### [ADD APP](add-app.md)
-###### [ADD PACKAGE](add-package.md)
-###### [ADD SERVER](add-server.md)
-###### [ADD TYPE](add-type.md)
-###### [CLEAR APP](clear-app.md)
-###### [CLEAR OBJ](clear-obj.md)
-###### [CONFIGURE APP](configure-app.md)
-###### [CONFIGURE PACKAGE](configure-package.md)
-###### [CONFIGURE SERVER](configure-server.md)
-###### [CONFIGURE TYPE](configure-type.md)
-###### [DELETE APP](delete-app.md)
-###### [DELETE OBJ](delete-obj.md)
-###### [DELETE PACKAGE](delete-package.md)
-###### [DELETE SERVER](delete-server.md)
-###### [DELETE TYPE](delete-type.md)
-###### [HELP](help.md)
-###### [LOAD APP](load-app.md)
-###### [LOAD PACKAGE](load-package.md)
-###### [LOCK APP](lock-app.md)
-###### [PUBLISH APP](publish-app.md)
-###### [PUBLISH PACKAGE](publish-package.md)
-###### [QUERY OBJ](query-obj.md)
-###### [REFRESH SERVER](refresh-server.md)
-###### [REPAIR APP](repair-app.md)
-###### [UNLOAD APP](unload-app.md)
-###### [UNLOAD PACKAGE](unload-package.md)
-###### [UNLOCK APP](unlock-app.md)
-###### [UNPUBLISH PACKAGE](unpublish-package.md)
-##### [SFTTRAY Command Reference](sfttray-command-reference.md)
-##### [Application Virtualization Client WMI Provider](application-virtualization-client-wmi-provider.md)
-###### [App-V Application WMI Class](app-v-application-wmi-class.md)
-###### [App-V Package WMI Class](app-v-package-wmi-class.md)
-##### [Log File for the Application Virtualization Client](log-file-for-the-application-virtualization-client.md)
-##### [App-V Client Registry Values](app-v-client-registry-values-sp1.md)
-##### [App-V Interoperability with Windows AppLocker](app-v-interoperability-with-windows-applocker.md)
-##### [Support for Client Reporting over HTTP](support-for-client-reporting-over-http.md)
-### [Application Virtualization Server](application-virtualization-server.md)
-#### [Monitoring Application Virtualization Servers](monitoring-application-virtualization-servers.md)
-#### [How to Load Files and Packages](how-to-load-files-and-packages.md)
-#### [How to Perform Administrative Tasks in the Application Virtualization Server Management Console](how-to-perform-administrative-tasks-in-the-application-virtualization-server-management-console.md)
-##### [How to Connect to an Application Virtualization System](how-to-connect-to-an-application-virtualization-system.md)
-##### [How to Manage Applications in the Server Management Console](how-to-manage-applications-in-the-server-management-console.md)
-###### [How to Import an Application](how-to-import-an-applicationserver.md)
-###### [How to Rename an Application](how-to-rename-an-application.md)
-###### [How to Delete an Application](how-to-delete-an-application-server.md)
-###### [How to Manually Add an Application](how-to-manually-add-an-application.md)
-###### [How to Move an Application](how-to-move-an-application.md)
-###### [How to Grant Access to an Application](how-to-grant-access-to-an-application.md)
-###### [How to Deny Access to an Application](how-to-deny-access-to-an-application.md)
-###### [How to Change an Application Icon](how-to-change-an-application-iconserver.md)
-##### [How to Manage Application Groups in the Server Management Console](how-to-manage-application-groups-in-the-server-management-console.md)
-###### [How to Create an Application Group](how-to-create-an-application-group.md)
-###### [How to Move an Application Group](how-to-move-an-application-group.md)
-###### [How to Rename an Application Group](how-to-rename-an-application-group.md)
-###### [How to Remove an Application Group](how-to-remove-an-application-group.md)
-##### [How to Manage Packages in the Server Management Console](how-to-manage-packages-in-the-server-management-console.md)
-###### [How to Add a Package](how-to-add-a-package.md)
-###### [How to Add a Package Version](how-to-add-a-package-version.md)
-###### [How to Delete a Package](how-to-delete-a-packageserver.md)
-###### [How to Delete a Package Version](how-to-delete-a-package-version.md)
-###### [How to Upgrade a Package](how-to-upgrade-a-package.md)
-##### [How to Manage Reports in the Server Management Console](how-to-manage-reports-in-the-server-management-console.md)
-###### [Application Virtualization Report Types](application-virtualization-report-types.md)
-####### [System Utilization Report](system-utilization-reportserver.md)
-####### [Software Audit Report](software-audit-reportserver.md)
-####### [Application Utilization Report](application-utilization-reportserver.md)
-####### [System Error Report](system-error-reportserver.md)
-###### [How to Create a Report](how-to-create-a-reportserver.md)
-###### [How to Run a Report](how-to-run-a-reportserver.md)
-###### [How to Print a Report](how-to-print-a-reportserver.md)
-###### [How to Export a Report](how-to-export-a-reportserver.md)
-###### [How to Delete a Report](how-to-delete-a-reportserver.md)
-##### [How to Manage Servers in the Server Management Console](how-to-manage-servers-in-the-server-management-console.md)
-###### [How to Create a Server Group](how-to-create-a-server-group.md)
-###### [How to Remove a Server Group](how-to-remove-a-server-group.md)
-###### [How to Add a Server](how-to-add-a-server.md)
-###### [How to Remove a Server](how-to-remove-a-server.md)
-###### [How to Change the Server Cache Size](how-to-change-the-server-cache-size.md)
-###### [How to Change the Server Port](how-to-change-the-server-port.md)
-##### [How to Manage Application Licenses in the Server Management Console](how-to-manage-application-licenses-in-the-server-management-console.md)
-###### [How to Create an Application License Group](how-to-create-an-application-license-group.md)
-###### [How to Associate an Application with a License Group](how-to-associate-an-application-with-a-license-group.md)
-###### [How to Remove an Application from a License Group](how-to-remove-an-application-from-a-license-group.md)
-###### [How to Remove an Application License Group](how-to-remove-an-application-license-group.md)
-###### [How to Set Up an Unlimited License Group](how-to-set-up-an-unlimited-license-group.md)
-###### [How to Set Up a Concurrent License Group](how-to-set-up-a-concurrent-license-group.md)
-###### [How to Set Up a Named License Group](how-to-set-up-a-named-license-group.md)
-##### [How to Customize an Application Virtualization System in the Server Management Console](how-to-customize-an-application-virtualization-system-in-the-server-management-console.md)
-###### [How to Set Up and Enable or Disable Authentication](how-to-set-up-and-enable-or-disable-authentication.md)
-###### [How to Set Up or Disable Usage Reporting](how-to-set-up-or-disable-usage-reporting.md)
-###### [How to Set Up or Disable Database Size](how-to-set-up-or-disable-database-size.md)
-###### [How to Set Up or Disable Application Licensing](how-to-set-up-or-disable-application-licensing.md)
-###### [How to Add an Administrator Group](how-to-add-an-administrator-group.md)
-###### [How to Delete an Administrator Group](how-to-delete-an-administrator-group.md)
-##### [How to Change the Server Logging Level and the Database Parameters](how-to-change-the-server-logging-level-and-the-database-parameters.md)
-#### [How to Configure the App-V System for Package Upgrade](how-to-configure-the-app-v-system-for-package-upgrade.md)
-#### [Troubleshooting Information for the Application Virtualization Server](troubleshooting-information-for-the-application-virtualization-server.md)
-#### [How to Migrate the App-V SQL Database to a Different SQL Server](how-to-migrate-the-app-v-sql-database-to-a-different-sql-server.md)
-### [Application Virtualization Sequencer](application-virtualization-sequencer.md)
-#### [Application Virtualization Sequencer Console Overview](application-virtualization-sequencer-console-overview.md)
-#### [About Sequencing Phases](about-sequencing-phases.md)
-#### [About App-V Package Accelerators (App-V 4.6 SP1)](about-app-v-package-accelerators--app-v-46-sp1-.md)
-#### [How to Determine Whether to Edit or Upgrade a Virtual Application Package](how-to-determine-whether-to-edit-or-upgrade-a-virtual-application-package.md)
-#### [How to Configure the App-V Sequencer](how-to-configure-the-app-v-sequencer.md)
-##### [How to Modify the Log Directory Location](how-to-modify-the-log-directory-location.md)
-##### [How to Create the Sequencer Package Root Directory](how-to-create-the-sequencer-package-root-directory.md)
-##### [How to Modify the Scratch Directory Location](how-to-modify-the-scratch-directory-location.md)
-#### [Configuring the Application Virtualization Sequencer (App-V 4.6 SP1)](configuring-the-application-virtualization-sequencer--app-v-46-sp1-.md)
-##### [How to Install the Sequencer (App-V 4.6 SP1)](how-to-install-the-sequencer---app-v-46-sp1-.md)
-##### [How to Create an App-V Project Template (App-V 4.6 SP1)](how-to-create-an-app-v-project-template--app-v-46-sp1-.md)
-#### [How to Create or Upgrade Virtual Applications Using the App-V Sequencer](how-to-create-or-upgrade-virtual-applications-using--the-app-v-sequencer.md)
-##### [How to Sequence an Application](how-to-sequence-an-application.md)
-##### [How to Sequence a New Application (App-V 4.6)](how-to-sequence-a-new-application--app-v-46-.md)
-##### [How to Edit an Existing Virtual Application](how-to-edit-an-existing-virtual-application.md)
-##### [How to Modify a Virtual Application Package (App-V 4.6)](how-to-modify-a-virtual-application-package--app-v-46-.md)
-##### [How to Upgrade an Existing Virtual Application](how-to-upgrade-an-existing-virtual-application.md)
-##### [How to Upgrade a Virtual Application Package (App-V 4.6)](how-to-upgrade-a-virtual-application-package--app-v-46-.md)
-##### [How to Modify the Operating Systems Associated With an Existing Windows Installer File](how-to-modify-the-operating-systems-associated-with-an-existing-windows-installer-file.md)
-##### [How to Sequence a New Application by Using the Command Line](how-to-sequence-a-new-application-by-using-the-command-line.md)
-##### [How to Upgrade a Virtual Application by Using the Command Line](how-to-upgrade-a-virtual-application-by-using-the-command-line.md)
-##### [How To Use Dynamic Suite Composition](how-to-use-dynamic-suite-composition.md)
-##### [How to Use the Differential SFT File](how-to-use-the-differential-sft-file.md)
-#### [Tasks for the Application Virtualization Sequencer (App-V 4.6 SP1)](tasks-for-the-application-virtualization-sequencer--app-v-46-sp1-.md)
-##### [How to Determine Which Type of Application to Sequence (App-V 4.6 SP1)](how-to-determine-which-type-of-application-to-sequence---app-v-46-sp1-.md)
-##### [How to Sequence a New Standard Application (App-V 4.6 SP1)](how-to-sequence-a-new-standard-application--app-v-46-sp1-.md)
-##### [How to Sequence a New Add-on or Plug-in Application (App-V 4.6 SP1)](how-to-sequence-a-new-add-on-or-plug-in-application--app-v-46-sp1-.md)
-##### [How to Sequence a New Middleware Application (App-V 4.6 SP1)](how-to-sequence-a-new-middleware-application--app-v-46-sp1-.md)
-##### [How to Modify an Existing Virtual Application Package (App-V 4.6 SP1)](how-to-modify-an-existing-virtual-application-package--app-v-46-sp1-.md)
-##### [How to Apply a Package Accelerator to Create a Virtual Application Package (App-V 4.6 SP1)](how-to-apply-a-package-accelerator-to-create-a-virtual-application-package---app-v-46-sp1-.md)
-##### [How to Apply an App-V Project Template (App-V 4.6 SP1)](how-to-apply-an-app-v-project-template--app-v-46-sp1-.md)
-##### [How to Create App-V Package Accelerators (App-V 4.6 SP1)](how-to-create-app-v-package-accelerators--app-v-46-sp1-.md)
-#### [Troubleshooting Application Virtualization Sequencer Issues](troubleshooting-application-virtualization-sequencer-issues.md)
-#### [Application Virtualization Sequencer Reference](application-virtualization-sequencer-reference.md)
-##### [Log Files for the Application Virtualization Sequencer](log-files-for-the-application-virtualization-sequencer.md)
-##### [Sequencer Command-Line Parameters](sequencer-command-line-parameters.md)
-##### [Sequencer Command-Line Error Codes](sequencer-command-line-error-codes.md)
-##### [Dialog Boxes (AppV 4.6 SP1)](dialog-boxes--appv-46-sp1-.md)
-###### [Incompatible Installer Dialog Box (App-V 4.6 SP1)](incompatible-installer-dialog-box--app-v-46-sp1-.md)
-###### [Failed Launch Dialog Box (App-V 4.6 SP1)](failed-launch-dialog-box--app-v-46-sp1-.md)
-###### [Oversized Package Dialog Box (App-V 4.6 SP1)](oversized-package-dialog-box--app-v-46-sp1-.md)
-###### [Restart Task Failure Dialog Box (App-V 4.6 SP1)](restart-task-failure-dialog-box--app-v-46-sp1-.md)
-###### [Side-by-side Privatization Failed Dialog Box (App-V 4.6 SP1)](side-by-side-privatization-failed-dialog-box--app-v-46-sp1-.md)
-###### [SXS Conflict Detected Dialog Box (App-V 4.6 SP1)](sxs-conflict-detected-dialog-box--app-v-46-sp1-.md)
-###### [Files Excluded Page Dialog Box (App-V 4.6 SP1)](files-excluded-page-dialog-box--app-v-46-sp1-.md)
-###### [Defender Running Dialog Box (App-V 4.6 SP1)](defender-running-dialog-box--app-v-46-sp1-.md)
-###### [Defrag Running Dialog Box (App-V 4.6 SP1)](defrag-running-dialog-box--app-v-46-sp1-.md)
-###### [Antivirus Running Dialog Box (App-V 4.6 SP1)](antivirus-running-dialog-box--app-v-46-sp1-.md)
-##### [Wizard Pages (AppV 4.6 SP1)](wizard-pages--appv-46-sp1-.md)
-###### [Create Package Accelerator Wizard (AppV 4.6 SP1)](create-package-accelerator-wizard--appv-46-sp1-.md)
-####### [About Sharing Package Accelerators Page](about-sharing-package-accelerators-page.md)
-####### [Select Package (Learn More) Page](select-package--learn-more--page.md)
-####### [Installation Files Page](installation-files-page.md)
-####### [Gathering Information Page (Learn More)](gathering-information-page--learn-more-.md)
-####### [Select Files Page](select-files-page.md)
-####### [Verify Applications Page (Package Accelerators)](verify-applications-page--package-accelerators-.md)
-####### [Select Guidance Page (Package Accelerators)](select-guidance-page--package-accelerators-.md)
-####### [Create Package Accelerator Page](create-package-accelerator-page.md)
-####### [Create Package Accelerator (Review Errors) Page](create-package-accelerator--review-errors--page.md)
-####### [Completion Page](completion-page.md)
-###### [Create New Package Wizard (AppV 4.6 SP1)](create-new-package-wizard---appv-46-sp1-.md)
-####### [Packaging Method Page (Learn More)](packaging-method-page--learn-more-.md)
-####### [Prepare Computer Page (Learn More)](prepare-computer-page--learn-more-.md)
-####### [Type of Application Page (Learn More)](type-of-application-page--learn-more-.md)
-####### [Select Installer Page (Learn More)](select-installer-page--learn-more-.md)
-####### [Package Name Page (Learn More)](package-name-page---learn-more-.md)
-####### [Installation Page (Learn More)](installation-page--learn-more-.md)
-####### [Configure Software Page (Learn More)](configure-software-page--learn-more-.md)
-####### [Installation Report Page (Learn More)](installation-report-page--learn-more-.md)
-####### [Customize Page (Learn More)](customize-page--learn-more-.md)
-######## [Edit Shortcuts](edit-shortcuts-learn-more.md)
-######## [Streaming Page](streaming-page-learn-more.md)
-######## [Target OS Page](target-os-page-learn-more.md)
-####### [Select Primary Page (Learn More)](select-primary-page--learn-more-.md)
-###### [Open Package Wizard (AppV 4.6 SP1)](open-package-wizard---appv-46-sp1-.md)
-####### [Select Task Page (Learn More)](select-task-page--learn-more-.md)
-####### [Packaging Method (Learn More)](packaging-method--learn-more-.md)
-###### [Sequencer Wizard - Package Accelerator (AppV 4.6 SP1)](sequencer-wizard---package-accelerator--appv-46-sp1-.md)
-####### [Select Package Accelerator Page](select-package-accelerator-page.md)
-####### [Select Package Accelerator (Learn More) Page](select-package-accelerator--learn-more--page.md)
-####### [Guidance Page [App-V 4.6 SP1]](guidance-page-app-v-46-sp1.md)
-####### [Select Installation Files Page [App-V 4.6 SP1]](select-installation-files-page-app-v-46-sp1.md)
-####### [Package Name Page [App-V 4.6 SP1]](package-name-page--app-v-46-sp1.md)
-####### [Create Package Page [App-V 4.6 SP1]](create-package-page--app-v-46-sp1.md)
-####### [Configure Software Page [App-V 4.6 SP1]](configure-software-page-app-v-46-sp1.md)
-####### [Run Each Program Page [App-V 4.6 SP1]](run-each-program-page-app-v-46-sp1.md)
-####### [Completion Page [Package Accelerator]](completion-page-package-accelerator.md)
-## [Online Help for Application Virtualization](online-help-for-application-virtualization.md)
-### [Application Virtualization Client Help](microsoft-application-virtualization-client-management-help.md)
-#### [Application Virtualization Client Management Console Roadmap](application-virtualization-client-management-console-roadmap.md)
-#### [About Virtual Environments](about-virtual-environments.md)
-#### [How to Use the Desktop Notification Area for Application Virtualization Client Management](how-to-use-the-desktop-notification-area-for-application-virtualization-client-management.md)
-##### [How to Refresh Virtual Applications from the Desktop Notification Area](how-to-refresh-virtual-applications-from-the-desktop-notification-area.md)
-##### [How to Load Virtual Applications from the Desktop Notification Area](how-to-load-virtual-applications-from-the-desktop-notification-area.md)
-##### [How to Cancel Loading of Virtual Applications from the Desktop Notification Area](how-to-cancel-loading-of-virtual-applications-from-the-desktop-notification-area.md)
-##### [How to Work Offline or Online with Application Virtualization](how-to-work-offline-or-online-with-application-virtualization.md)
-##### [How to Exit the App-V Client from the Notification Area](how-to-exit-the-app-v-client-from-the-notification-area.md)
-#### [Application Virtualization Client Management Console](application-virtualization-client-management-console.md)
-##### [Application Virtualization Client Management Console Overview](application-virtualization-client-management-console-overview.md)
-###### [About Application Virtualization Servers](about-application-virtualization-servers.md)
-###### [User Access Permissions in Application Virtualization Client](user-access-permissions-in-application-virtualization-client.md)
-###### [Disconnected Operation Mode](disconnected-operation-mode.md)
-##### [How to Perform General Administrative Tasks in the Client Management Console](how-to-perform-general-administrative-tasks-in-the-client-management-console.md)
-###### [How to Set Up Publishing Servers](how-to-set-up-publishing-servers.md)
-###### [How to Refresh the Publishing Servers](how-to-refresh-the-publishing-servers.md)
-###### [How to Disable or Modify Disconnected Operation Mode Settings](how-to-disable-or-modify-disconnected-operation-mode-settings.md)
-##### [How to Manage Applications in the Client Management Console](how-to-manage-applications-in-the-client-management-console.md)
-###### [How to Load or Unload an Application](how-to-load-or-unload-an-application.md)
-###### [How to Clear an Application](how-to-clear-an-application.md)
-###### [How to Repair an Application](how-to-repair-an-application.md)
-###### [How to Import an Application](how-to-import-an-application.md)
-###### [How to Lock or Unlock an Application](how-to-lock-or-unlock-an-application.md)
-###### [How to Delete an Application](how-to-delete-an-application.md)
-###### [How to Change an Application Icon](how-to-change-an-application-icon.md)
-##### [How to Configure the Client in the Application Virtualization Client Management Console](how-to-configure-the-client-in-the-application-virtualization-client-management-console.md)
-###### [How to Change the Cache Size and the Drive Letter Designation](how-to-change-the-cache-size-and-the-drive-letter-designation.md)
-###### [How to Change the Log Reporting Levels and Reset the Log Files](how-to-change-the-log-reporting-levels-and-reset-the-log-files.md)
-###### [How to Change User Access Permissions](how-to-change-user-access-permissions.md)
-###### [How to Change Import Search Paths](how-to-change-import-search-paths.md)
-###### [How to Set Up Periodic Publishing Refresh](how-to-set-up-periodic-publishing-refresh.md)
-###### [How to Set Up Publishing Refresh on Login](how-to-set-up-publishing-refresh-on-login.md)
-##### [How to Manually Manage Applications in the Client Management Console](how-to-manually-manage-applications-in-the-client-management-console.md)
-###### [How to Add an Application](how-to-add-an-application.md)
-###### [How to Publish Application Shortcuts](how-to-publish-application-shortcuts.md)
-###### [How to Add a File Type Association](how-to-add-a-file-type-association.md)
-###### [How to Delete a File Type Association](how-to-delete-a-file-type-association.md)
-#### [Application Virtualization Client Management Console Reference](application-virtualization-client-management-console-reference.md)
-##### [Client Management Console: Application Virtualization Node](client-management-console-application-virtualization-node.md)
-##### [Client Management Console: About Dialog Boxes](client-management-console-about-dialog-boxes.md)
-##### [Client Management Console: Applications Node](client-management-console-applications-node.md)
-###### [Applications Node](applications-node.md)
-###### [Applications Results Pane](applications-results-pane.md)
-###### [Applications Results Pane Columns](applications-results-pane-columns.md)
-##### [Client Management Console: File Type Associations Node](client-management-console-file-type-associations-node.md)
-###### [File Type Associations Node](file-type-associations-node-client.md)
-###### [File Type Association Results Pane](file-type-association-results-pane.md)
-###### [File Type Association Results Pane Columns](file-type-association-results-pane-columns.md)
-##### [Client Management Console: Publishing Servers Node](client-management-console-publishing-servers-node.md)
-###### [Publishing Servers Node](publishing-servers-node.md)
-###### [Publishing Servers Results Pane](publishing-servers-results-pane.md)
-###### [Publishing Servers Results Pane Columns](publishing-servers-results-pane-columns.md)
-##### [Client Management Console: Application Virtualization Properties](client-management-console-application-virtualization-properties.md)
-###### [Application Virtualization Properties: General Tab](application-virtualization-properties-general-tab.md)
-###### [Application Virtualization Properties: Interface Tab](application-virtualization-properties-interface-tab.md)
-###### [Application Virtualization Properties: File System Tab](application-virtualization-properties-file-system-tab.md)
-###### [Application Virtualization Properties: Import Search Path Tab](application-virtualization-properties-import-search-path-tab.md)
-###### [Application Virtualization Properties: Connectivity Tab](application-virtualization-properties-connectivity-tab.md)
-###### [Application Virtualization Properties: Permissions Tab](application-virtualization-properties-permissions-tab.md)
-### [Application Virtualization Server Help](application-virtualization-server-management-help.md)
-#### [About the Application Virtualization Server Management Console](about-the-application-virtualization-server-management-console.md)
-##### [About Application Virtualization Applications](about-application-virtualization-applications.md)
-##### [About Application Virtualization Packages](about-application-virtualization-packages.md)
-##### [About Publishing](about-publishing.md)
-##### [About Application Licensing](about-application-licensing.md)
-#### [How to Perform Administrative Tasks in the Application Virtualization Server Management Console](how-to-perform-administrative-tasks-in-the-application-virtualization-server-management-console.md)
-##### [How to Connect to an Application Virtualization System](how-to-connect-to-an-application-virtualization-system.md)
-##### [How to Manage Applications in the Server Management Console](how-to-manage-applications-in-the-server-management-console.md)
-###### [How to Import an Application](how-to-import-an-applicationserver.md)
-###### [How to Rename an Application](how-to-rename-an-application.md)
-###### [How to Delete an Application](how-to-delete-an-application-server.md)
-###### [How to Manually Add an Application](how-to-manually-add-an-application.md)
-###### [How to Move an Application](how-to-move-an-application.md)
-###### [How to Grant Access to an Application](how-to-grant-access-to-an-application.md)
-###### [How to Deny Access to an Application](how-to-deny-access-to-an-application.md)
-###### [How to Change an Application Icon](how-to-change-an-application-iconserver.md)
-##### [How to Manage Application Groups in the Server Management Console](how-to-manage-application-groups-in-the-server-management-console.md)
-###### [How to Create an Application Group](how-to-create-an-application-group.md)
-###### [How to Move an Application Group](how-to-move-an-application-group.md)
-###### [How to Rename an Application Group](how-to-rename-an-application-group.md)
-###### [How to Remove an Application Group](how-to-remove-an-application-group.md)
-##### [How to Manage Packages in the Server Management Console](how-to-manage-packages-in-the-server-management-console.md)
-###### [How to Add a Package](how-to-add-a-package.md)
-###### [How to Add a Package Version](how-to-add-a-package-version.md)
-###### [How to Delete a Package](how-to-delete-a-packageserver.md)
-###### [How to Delete a Package Version](how-to-delete-a-package-version.md)
-###### [How to Upgrade a Package](how-to-upgrade-a-package.md)
-##### [How to Manage Reports in the Server Management Console](how-to-manage-reports-in-the-server-management-console.md)
-###### [Application Virtualization Report Types](application-virtualization-report-types.md)
-####### [System Utilization Report](system-utilization-reportserver.md)
-####### [Software Audit Report](software-audit-reportserver.md)
-####### [Application Utilization Report](application-utilization-reportserver.md)
-####### [System Error Report](system-error-reportserver.md)
-###### [How to Create a Report](how-to-create-a-reportserver.md)
-###### [How to Run a Report](how-to-run-a-reportserver.md)
-###### [How to Print a Report](how-to-print-a-reportserver.md)
-###### [How to Export a Report](how-to-export-a-reportserver.md)
-###### [How to Delete a Report](how-to-delete-a-reportserver.md)
-##### [How to Manage Servers in the Server Management Console](how-to-manage-servers-in-the-server-management-console.md)
-###### [How to Create a Server Group](how-to-create-a-server-group.md)
-###### [How to Remove a Server Group](how-to-remove-a-server-group.md)
-###### [How to Add a Server](how-to-add-a-server.md)
-###### [How to Remove a Server](how-to-remove-a-server.md)
-###### [How to Change the Server Cache Size](how-to-change-the-server-cache-size.md)
-###### [How to Change the Server Port](how-to-change-the-server-port.md)
-##### [How to Manage Application Licenses in the Server Management Console](how-to-manage-application-licenses-in-the-server-management-console.md)
-###### [How to Create an Application License Group](how-to-create-an-application-license-group.md)
-###### [How to Associate an Application with a License Group](how-to-associate-an-application-with-a-license-group.md)
-###### [How to Remove an Application from a License Group](how-to-remove-an-application-from-a-license-group.md)
-###### [How to Remove an Application License Group](how-to-remove-an-application-license-group.md)
-###### [How to Set Up an Unlimited License Group](how-to-set-up-an-unlimited-license-group.md)
-###### [How to Set Up a Concurrent License Group](how-to-set-up-a-concurrent-license-group.md)
-###### [How to Set Up a Named License Group](how-to-set-up-a-named-license-group.md)
-##### [How to Customize an Application Virtualization System in the Server Management Console](how-to-customize-an-application-virtualization-system-in-the-server-management-console.md)
-###### [How to Set Up and Enable or Disable Authentication](how-to-set-up-and-enable-or-disable-authentication.md)
-###### [How to Set Up or Disable Usage Reporting](how-to-set-up-or-disable-usage-reporting.md)
-###### [How to Set Up or Disable Database Size](how-to-set-up-or-disable-database-size.md)
-###### [How to Set Up or Disable Application Licensing](how-to-set-up-or-disable-application-licensing.md)
-###### [How to Add an Administrator Group](how-to-add-an-administrator-group.md)
-###### [How to Delete an Administrator Group](how-to-delete-an-administrator-group.md)
-##### [How to Change the Server Logging Level and the Database Parameters](how-to-change-the-server-logging-level-and-the-database-parameters.md)
-##### [How to Configure Microsoft SQL Server Mirroring Support for App-V](how-to-configure-microsoft-sql-server-mirroring-support-for-app-v.md)
-#### [Application Virtualization Server Management Console Reference](application-virtualization-server-management-console-reference.md)
-##### [Server Management Console: Application Virtualization System Node](server-management-console-application-virtualization-system-node.md)
-##### [Server Management Console: About Dialog Boxes](server-management-console-about-dialog-boxes.md)
-##### [Server Management Console: Applications Node](server-management-console-applications-node.md)
-###### [Applications Node](applications-node-in-server-management-console.md)
-###### [Applications Results Pane](applications-results-pane-in-server-management-console.md)
-###### [Applications Results Pane Columns](applications-results-pane-columns-in-server-management-console.md)
-##### [Server Management Console: File Type Associations Node](server-management-console-file-type-associations-node.md)
-###### [File Type Associations Node](file-type-associations-node.md)
-###### [File Type Associations Results Pane](file-type-associations-results-pane.md)
-###### [File Type Associations Results Pane Columns](file-type-associations-results-pane-columns.md)
-##### [Server Management Console: Packages Node](server-management-console-packages-node.md)
-###### [Packages Node](packages-node.md)
-###### [Package Results Pane](package-results-pane.md)
-###### [Package Results Pane Columns](package-results-pane-columns.md)
-##### [Server Management Console: Application Licenses Node](server-management-console-application-licenses-node.md)
-###### [Applications Licenses Node](applications-licenses-node.md)
-###### [Applications Licenses Results Pane](applications-licenses-results-pane.md)
-###### [Applications Licenses Results Pane Columns](applications-licenses-results-pane-columns.md)
-##### [Server Management Console: Server Groups Node](server-management-console-server-groups-node.md)
-###### [Server Groups Node](server-groups-node.md)
-###### [Server Groups Results Pane](server-groups-results-pane.md)
-###### [Server Groups Results Pane Columns](server-groups-results-pane-columns.md)
-##### [Server Management Console: Provider Policies Node](server-management-console-provider-policies-node.md)
-###### [Provider Policies Node](provider-policies-node.md)
-###### [Provider Policies Results Pane](provider-policies-results-pane.md)
-###### [Provider Policies Results Pane Columns](provider-policies-results-pane-columns.md)
-##### [Server Management Console: Administrators Node](server-management-console-administrators-node.md)
-###### [Administrators Node](administrators-node.md)
-###### [Administrators Results Pane](administrators-results-pane.md)
-###### [Administrators Results Pane Columns](administrators-results-pane-columns.md)
-##### [Server Management Console: Reports Node](server-management-console-reports-node.md)
-###### [Reports Node](reports-node.md)
-###### [Reports Results Pane](reports-results-pane.md)
-###### [Reports Results Pane Columns](reports-results-pane-columns.md)
-### [Application Virtualization Sequencer Online Help](application-virtualization-sequencer-online-help.md)
-#### [Application Virtualization Sequencer Overview](application-virtualization-sequencer-overview.md)
-##### [About the Application Virtualization Sequencer](about-the-application-virtualization-sequencer.md)
-##### [About the Sequencer Console](about-the-sequencer-console.md)
-##### [About Using the Sequencer Command Line](about-using-the-sequencer-command-line.md)
-##### [Best Practices for the Application Virtualization Sequencer](best-practices-for-the-application-virtualization-sequencer-sp1.md)
-#### [Sequencer Hardware and Software Requirements](sequencer-hardware-and-software-requirements.md)
-#### [Configuring the Application Virtualization Sequencer](configuring-the-application-virtualization-sequencer.md)
-##### [How to Install the Sequencer](how-to-install-the-sequencer.md)
-##### [How to Create the Package Root Directory](how-to-create-the-package-root-directory.md)
-##### [How to Modify the Location of the Log Directory](how-to-modify-the-location-of-the-log-directory.md)
-##### [How to Modify the Location of the Scratch Directory](how-to-modify-the-location-of-the-scratch-directory.md)
-#### [Tasks for the Application Virtualization Sequencer](tasks-for-the-application-virtualization-sequencer.md)
-##### [How to Sequence a New Application](how-to-sequence-a-new-application.md)
-##### [How to Create a Virtual Environment for a Web-Based Application](how-to-create-a-virtual-environment-for-a-web-based-application.md)
-##### [How to Upgrade a Sequenced Virtual Application Package](how-to-upgrade-a-sequenced-virtual-application-package.md)
-##### [How to Branch a Package](how-to-branch-a-package.md)
-##### [How to Upgrade a Package Using the Open Package Command](how-to-upgrade-a-package-using-the-open-package-command.md)
-##### [How to Manage Virtual Applications Using the Command Line](how-to-manage-virtual-applications-using-the-command-line.md)
-###### [How to Open a Sequenced Application Using the Command Line](how-to-open-a-sequenced-application-using-the-command-line.md)
-###### [How to Sequence a New Application Package Using the Command Line](how-to-sequence-a-new-application-package-using-the-command-line.md)
-###### [How to Upgrade a Sequenced Application Package Using the Command Line](how-to-upgrade-a-sequenced-application-package-using-the-command-line.md)
-#### [Troubleshooting the Application Virtualization Sequencer](troubleshooting-the-application-virtualization-sequencer.md)
-#### [Application Virtualization Sequencer Technical Reference](application-virtualization-sequencer-technical-reference-keep.md)
-##### [Sequencer Dialog Boxes](sequencer-dialog-boxes.md)
-###### [Application Virtualization Sequencer Options Dialog Box](application-virtualization-sequencer-options-dialog-box.md)
-####### [General Tab](general-tab-keep.md)
-####### [Parse Items Tab](parse-items-tab-keep.md)
-####### [Exclusion Items Tab](exclusion-items-tab-keep.md)
-####### [Exclusion Item Dialog Box](exclusion-item-dialog-box.md)
-###### [Application Virtualization Sequencing Wizard-Add Application Dialog Box](application-virtualization-sequencing-wizard-add-application-dialog-box.md)
-###### [Application Virtualization Sequencing Wizard-Add File Type Association Dialog Box](application-virtualization-sequencing-wizard-add-file-type-association-dialog-box.md)
-###### [Application Virtualization Sequencing Wizard-Shortcut Locations Dialog Box](application-virtualization-sequencing-wizard-shortcut-locations-dialog-box.md)
-##### [Sequencing Wizard](sequencing-wizard.md)
-###### [Package Information Page](application-virtualization-sequencing-wizard-package-information-page-keep.md)
-###### [Advanced Options Page](application-virtualization-sequencing-wizard-advanced-options-page.md)
-###### [Monitor Installation Page](application-virtualization-sequencing-wizard-monitor-installation-page.md)
-###### [Add Files to Virtual File System Page](application-virtualization-sequencing-wizard-add-files-to-virtual-file-system-page.md)
-###### [Virtual Application Package Additional Components](virtual-application-package-additional-components.md)
-###### [Configure Application Page](application-virtualization-sequencing-wizard-configure-application-page-keep.md)
-###### [Launch Applications Page](application-virtualization-sequencing-wizard-launch-applications-page.md)
-###### [Sequence Package Page](application-virtualization-sequencing-wizard-sequence-package-page.md)
-##### [Sequencer Console](sequencer-console.md)
-###### [Properties Tab](properties-tab-keep.md)
-####### [About the Properties Tab](about-the-properties-tab.md)
-####### [How to Change Package Properties](how-to-change-package-properties.md)
-###### [Deployment Tab](deployment-tab.md)
-####### [About the Deployment Tab](about-the-deployment-tab.md)
-####### [How to Change Deployment Properties](how-to-change-deployment-properties.md)
-###### [Change History Tab](change-history-tab-keep.md)
-###### [Files Tab](files-tab-keep.md)
-####### [About the Files Tab](about-the-files-tab.md)
-####### [How to Modify the Files Included in a Package](how-to-modify-the-files-included-in-a-package.md)
-###### [Virtual Registry Tab](virtual-registry-tab-keep.md)
-####### [About the Virtual Registry Tab](about-the-virtual-registry-tab.md)
-####### [How to Modify Virtual Registry Key Information](how-to-modify-virtual-registry-key-information.md)
-###### [Virtual File System Tab](virtual-file-system-tab-keep.md)
-####### [About the Virtual File System Tab](about-the-virtual-file-system-tab.md)
-####### [How to Modify File-Mapping Information](how-to-modify-file-mapping-information.md)
-###### [Virtual Services Tab](virtual-services-tab-keep.md)
-####### [About the Virtual Services Tab](about-the-virtual-services-tab.md)
-####### [How to Modify Attributes of Embedded Services](how-to-modify-attributes-of-embedded-services.md)
-###### [OSD Tab](osd-tab-keep.md)
-####### [About the OSD Tab](about-the-osd-tab.md)
-######## [OSD File Elements](osd-file-elements.md)
-####### [How to Edit an OSD File](how-to-edit-an-osd-file.md)
-####### [How to Edit an OSD File Using a Text Editor](how-to-edit-an-osd-file-using-a-text-editor.md)
-##### [Application Virtualization Sequencer Command Line](application-virtualization-sequencer-command-line.md)
-###### [Command-Line Parameters](command-line-parameters.md)
-###### [Command-Line Errors](command-line-errors.md)
-## [Glossary](application-virtualization-glossary.md)
-## [Application Virtualization Technical Publications](application-virtualization-technical-publications-white-papers.md)
-### [Microsoft Application Virtualization Security Guide](microsoft-application-virtualization-security-guide.md)
-#### [Introduction](introduction-to-the-application-virtualization-security-guide.md)
-#### [Installing App-V Management Server or Streaming Server Securely](installing-app-v-management-server-or-streaming-server-securely.md)
-##### [Configuring Certificates to Support Secure Streaming](configuring-certificates-to-support-secure-streaming.md)
-##### [How to Modify Private Key Permissions to Support Management Server or Streaming Server](how-to-modify-private-key-permissions-to-support-management-server-or-streaming-server.md)
-##### [Configuring Certificates to Support App-V Management Server or Streaming Server](configuring-certificates-to-support-app-v-management-server-or-streaming-server.md)
-#### [Configuring Management or Streaming Server for Secure Communications Post-Installation](configuring-management-or-streaming-server-for-secure-communications-post-installation.md)
-##### [How to Configure Management Server Security Post-Installation](how-to-configure-management-server-security-post-installation.md)
-##### [How to Configure Streaming Server Security Post-Installation](how-to-configure-streaming-server-security-post-installation.md)
-##### [Troubleshooting Certificate Permission Issues](troubleshooting-certificate-permission-issues.md)
-#### [Configuring Windows Firewall for App-V](configuring-windows-firewall-for-app-v.md)
-##### [How to Configure Windows Server 2003 Firewall for App-V](how-to-configure-windows-server-2003-firewall-for-app-v.md)
-##### [How to Configure Windows Server 2008 Firewall for App-V](how-to-configure-windows-server-2008-firewall-for-app-v.md)
-#### [Configuring App-V for Secure Administration](configuring-app-v-for-secure-administration.md)
-##### [Configuring Certificates to Support the App-V Web Management Service](configuring-certificates-to-support-the-app-v-web-management-service.md)
-##### [How to Install and Configure the App-V Management Console for a More Secure Environment](how-to-install-and-configure-the-app-v-management-console-for-a-more-secure-environment.md)
-#### [Configuring App-V Administration for a Distributed Environment](configuring-app-v-administration-for-a-distributed-environment.md)
-#### [Configuring IIS for Secure Streaming](configuring-iis-for-secure-streaming.md)
-#### [App-V Desktop Client Security](app-v-desktop-client-security.md)
-#### [Improving Security During App-V Sequencing](improving-security-during-app-v-sequencing.md)
-#### [Internet-Facing Server Scenarios for Perimeter Networks](internet-facing-server-scenarios-for-perimeter-networks.md)
-#### [Internet-Facing Considerations for App-V Clients](internet-facing-considerations-for-app-v-clients.md)
-##### [Domain-Joined and Non-Domain-Joined Clients](domain-joined-and-non-domain-joined-clients.md)
-##### [How to Assign the Proper Credentials for Windows XP](how-to-assign--the-proper-credentials-for-windows-xp.md)
-##### [How to Assign the Proper Credentials for Windows Vista](how-to-assign--the-proper-credentials-for-windows-vista.md)
-## [Microsoft Application Virtualization 4.6 Service Pack 1 Privacy Statement](microsoft-application-virtualization-46-service-pack-1-privacy-statement.md)
-## [Microsoft Application Virtualization 4.6 Service Pack 2 Privacy Statement](microsoft-application-virtualization-46-service-pack-2-privacy-statement.md)
-
diff --git a/mdop/appv-v4/about-app-v-package-accelerators--app-v-46-sp1-.md b/mdop/appv-v4/about-app-v-package-accelerators--app-v-46-sp1-.md
deleted file mode 100644
index 638fd0e895..0000000000
--- a/mdop/appv-v4/about-app-v-package-accelerators--app-v-46-sp1-.md
+++ /dev/null
@@ -1,70 +0,0 @@
----
-title: About App-V Package Accelerators (App-V 4.6 SP1)
-description: About App-V Package Accelerators (App-V 4.6 SP1)
-author: manikadhiman
-ms.assetid: fc2d2375-8f17-4a6d-b374-771cb947cb8c
-ms.reviewer:
-manager: dansimp
-ms.author: v-madhi
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 08/30/2016
----
-
-
-# About App-V Package Accelerators (App-V 4.6 SP1)
-
-
-You can use App-V Package Accelerators to automatically sequence large, complex applications. Additionally, when you apply an App-V Package Accelerator, you are not always required to manually install an application to create the virtual application package.
-
-**Note**
-In some cases, you are prompted to install an application locally to the computer running the App-V Sequencer before you can use the Package Accelerator. If you have to install an application, you must install the application to the application’s default location. This installation is not monitored by App-V Sequencer. When the App-V Package Accelerator is created, the author of the Package Accelerator determines whether to install an application locally is required.
-
-
-
-App-V Sequencer extracts the required files from the App-V Package Accelerator and associated installation media to create a virtual package without having to monitor the installation of the application.
-
-**Important**
-Disclaimer: The Microsoft Application Virtualization Sequencer does not give you any license rights to the software application you are using to create a Package Accelerator. You must abide by all end user license terms for such application. It is your responsibility to make sure the software application’s license terms allow you to create a Package Accelerator using Application Virtualization Sequencer.
-
-
-
-App-V Package Accelerators and project templates differ from each other. Package Accelerators are application-specific. Project templates enable users to save commonly used settings specific to an organization and apply them to multiple applications. You can also create project templates at the command prompt, while in contrast, you must use the App-V Sequencer console to create Package Accelerators. Additionally, creating a package by using a Package Accelerator and applying a project template is not supported.
-
-## Sharing App-V Package Accelerators
-
-
-This section provides best practice information about how to share Package Accelerators. If you plan to share Package Accelerators, information such as computer names, user account information, and information about the associated applications might be included in the Package Accelerators.The following list describes methods you should consider when creating Package Accelerators:
-
-- **User name**. When you log on to the computer running App-V Sequencer, you should use a generic user account, such as the built-in **administrator** account for administering the computer / domain. You should not use an account that is based on an existing user name.
-
-- **Computer Name**. Specify a general, non-identifying name for the computer running the Sequencer.
-
-- **Server URL**. In the Sequencer console, on the **Deployment** tab, use the default settings for the server URL configuration information.
-
-- **Applications**. If you do not want to share the list of applications that were installed on the computer running the Sequencer when you created the Package Accelerator, you must delete the **appv\_manifest.xml** file. This file is located in the package root directory of the virtual application package.
-
-You should also review any settings or configuration files associated with the virtual application package to ensure the applications do not contain any personal information.
-
-## Securing App-V Package Accelerators
-
-
-Always save App-V Package Accelerators and any associated installation media in a secure location on the network to protect the App-V Package Accelerators and the installation files from being tampered with or becoming corrupted. Because Package Accelerators can also contain password and user-specific information, you must save App-V Package Accelerators in a secure location, and you must digitally sign the Package Accelerator after you create it so that the publisher can be verified when the Package Accelerator is applied. For more information about digital signatures, see [Application Guidelines on Digital Signature Practices for Common Criteria Security](https://go.microsoft.com/fwlink/?LinkId=204705) (https://go.microsoft.com/fwlink/?LinkId=204705).
-
-## Related topics
-
-
-[How to Create App-V Package Accelerators (App-V 4.6 SP1)](how-to-create-app-v-package-accelerators--app-v-46-sp1-.md)
-
-[How to Apply a Package Accelerator to Create a Virtual Application Package (App-V 4.6 SP1)](how-to-apply-a-package-accelerator-to-create-a-virtual-application-package---app-v-46-sp1-.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/about-application-licensing.md b/mdop/appv-v4/about-application-licensing.md
deleted file mode 100644
index 039444d39d..0000000000
--- a/mdop/appv-v4/about-application-licensing.md
+++ /dev/null
@@ -1,85 +0,0 @@
----
-title: About Application Licensing
-description: About Application Licensing
-author: dansimp
-ms.assetid: 6b487641-1627-4e91-b829-04f001008176
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# About Application Licensing
-
-
-You can manage application licenses directly from the Application Virtualization Server Management Console.
-
-## License Types
-
-
-The System Center Application Virtualization System currently supports the following license types:
-
-- **Unlimited License**—Allows access to the application by any number of simultaneous users. This method of licensing is appropriate when you want to associate an enterprise-wide license with an application.
-
-- **Concurrent License**—Enables you to define the maximum number of concurrent users who are allowed to use the application.
-
-- **Named License**—Enables you to assign a license to an individual user. A named license can be used to ensure that a particular user will always be able to run the application.
-
-You can combine concurrent and named licenses for the same application.
-
-Licensing is disabled by default, but you can enable it from the **Provider Pipeline** tab of the **Provider Properties** dialog. For details about enabling and disabling licensing, see [How to Set Up or Disable Application Licensing](how-to-set-up-or-disable-application-licensing.md).
-
-## Provider Policies
-
-
-Provider policies were developed for the Application Service Provider (ASP) model. In this model, a single ASP can host a single Application Virtualization System for multiple clients, where each client needs to remain isolated. Clients might have dramatically different requirements—for example, one client might require authentication while another does not. You can use provider policies to associate permissions with clients so that only the approved users can access each virtual application or virtual application package.
-
-For the enterprise customer, you can use this feature when you have strict licensing requirements for one or more applications. Under this situation, the licensing component is disabled on the **Provider Pipeline** tab of the **Provider Properties** dialog.
-
-The **Provider Pipeline** tab also has check boxes to enable authentication, authorization (**Enforce Access Permission Settings**), and metering (**Log Usage Information**). If your configuration has special requirements, you can write your own pipeline components and add them to the system by clicking the **Advanced** button.
-
-## Account Authorities
-
-
-The account authority is the domain in which the Application Virtualization Server is installed. As you proceed through the server installation, you are prompted to supply a domain name; the domain in which the computer is installed is detected and used by default. When users attempt to log in to the system, they are prompted for their credentials before they can access that domain.
-
-The Application Virtualization System supports multiple domains. You can grant application access to user groups in other domains if a trust relationship is established between domains. Users must supply credentials that are recognized by each domain.
-
-In the Application Virtualization Server Management Console, you can change the primary domain (account authority) and the credentials that are used to access it.
-
-## Authentication
-
-
-Authentication is the mechanism used to confirm a user's identity. Any user with a recognized user name and password has access.
-
-In the Application Virtualization System, you can enable or disable authentication through a check box on the **Provider Pipeline** tab. By default, Windows Authentication is enabled.
-
-## Authorization
-
-
-Authorization is the process used to confirm a user’s identity. After confirming the user's identity, the system determines whether the user was granted access to the system and to which applications the user was granted access. The Application Virtualization Server Management Console has an **Enforce Access Permission Settings** check box on the **Provider Pipeline** tab to enable or disable authorization.
-
-In the Application Virtualization System, access is granted to a user group only, not to individual users.
-
-## Related topics
-
-
-[How to Manage Application Licenses in the Server Management Console](how-to-manage-application-licenses-in-the-server-management-console.md)
-
-[How to Set Up or Disable Application Licensing](how-to-set-up-or-disable-application-licensing.md)
-
-[Server Management Console: Provider Policies Node](server-management-console-provider-policies-node.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/about-application-virtualization-applications.md b/mdop/appv-v4/about-application-virtualization-applications.md
deleted file mode 100644
index 81f4351171..0000000000
--- a/mdop/appv-v4/about-application-virtualization-applications.md
+++ /dev/null
@@ -1,55 +0,0 @@
----
-title: About Application Virtualization Applications
-description: About Application Virtualization Applications
-author: dansimp
-ms.assetid: 3bf833b7-d172-4eef-a9e8-4b4f0c7eb15b
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# About Application Virtualization Applications
-
-
-In Application Virtualization, an *application* is an executable program, such as Microsoft Visio, that is streamed to the Application Virtualization Desktop Client or Client for Remote Desktop Services (formerly Terminal Services) from an Application Virtualization Management Server. Before an application can be streamed to a client, the application must be prepared for streaming by processing it with the Application Virtualization Sequencer.
-
-## Managing Applications
-
-
-You must add applications to the system before you can make the applications available to users. The most common method for adding applications to the system is to import them. To access this feature, right-click the **Applications** node in the Application Virtualization Server Management Console and choose **Import Applications**.
-
-You can import more than one Open Software Descriptor (OSD) file at the same time, or you can import a Sequencer Project file (SPRJ) that can contain multiple OSD files. This functionality enables you to configure related applications similarly.
-
-You can also use the following features to help you manage your applications:
-
-- **Application Groups**—Enables you to create logical groups of applications for simplified management. When changes are made to a group (for example, access permissions), the changes are applied to all applications in the group. Applications in a group can come from different packages.
-
-- **Multi Select**—Enables you to select multiple applications at once by holding the CTRL key when you click an application to modify the application properties. However, if you want to maintain a relationship between the applications, you should create an application group to hold the applications.
-
-- **Cross System Copy**—Enables you to copy applications from one environment to another environment that is running the same version of App-V in one step. For example, you might have a user acceptance test environment where you initially deploy and configure applications. After you finish your testing phase, you might want to replicate the same set of applications (including permissions) to the production environment.
-
-## Related topics
-
-
-[About Application Virtualization Packages](about-application-virtualization-packages.md)
-
-[About the Application Virtualization Server Management Console](about-the-application-virtualization-server-management-console.md)
-
-[How to Manage Application Groups in the Server Management Console](how-to-manage-application-groups-in-the-server-management-console.md)
-
-[How to Manage Applications in the Server Management Console](how-to-manage-applications-in-the-server-management-console.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/about-application-virtualization-packages.md b/mdop/appv-v4/about-application-virtualization-packages.md
deleted file mode 100644
index 63e1915d67..0000000000
--- a/mdop/appv-v4/about-application-virtualization-packages.md
+++ /dev/null
@@ -1,67 +0,0 @@
----
-title: About Application Virtualization Packages
-description: About Application Virtualization Packages
-author: dansimp
-ms.assetid: 69bd35c1-7af3-43db-931b-3074780aa926
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# About Application Virtualization Packages
-
-
-In Application Virtualization, a *package* is the output of the sequencing process. You use packages when you first deploy applications on your servers and when you upgrade applications with a new version. Packages enable you to control virtual application versions on your Application Virtualization Management Servers. A single package can contain one or more applications. Each application package contains a set of files as a self-contained unit.
-
-## Managing Packages
-
-
-After the Sequencer creates a package of one or more applications as part of its process, you can copy the Sequencer-generated files to a Application Virtualization Management Server and make them available for streaming.
-
-Available packages appear under the **Packages** container in the left pane of the Application Virtualization Management Console. When you import an application with a Sequencer Project (SPRJ) file or an Open Software Descriptor (OSD) file, a related entry appears in the **Packages** container. From the Application Virtualization Server Management Console, you can then deploy, upgrade, or delete packages and versions of them.
-
-Each virtual application has an associated package. This package includes the following files:
-
-- SFT—The file that streams the application to clients.
-
-- OSD—The Open Software Descriptor file contains the information needed to find and launch the application.
-
-- ICO—The icon file that visually represents the application in user interfaces and shortcuts.
-
-- SPRJ—The Sequencer Project file.
-
-When you import the SPRJ file, all sequenced applications are available for deployment, by default, but the applications are not enabled for streaming. You can choose to stream all or some of the applications in the package. For example, if you sequenced and imported Microsoft Office, you can choose not to deploy some applications, such as the Save My Settings Wizard. In this case, right-click each application you want to deploy, choose **Properties**, and make sure that the **Enabled** box is cleared (blank). Only the applications with the **Enabled** box selected will stream to client computers.
-
-After you resequence a package and produce a new SFT file for streaming, you can upgrade the old package quickly and easily through the Application Virtualization Server Management Console.
-
-The only operational scenario that requires you to use the **Packages** node is when you introduce a new version (SFT file) for the package. Whenever you import applications, assign access and licenses to applications, and so on, the Application Virtualization System tracks this information at the package level. This means that when you authorize a user to use an application, you are giving the user permission to run any application in the same package.
-
-### Package Version
-
-A package version is represented by a specific SFT file. When you upgrade a package (apply an update to an application or add an application to a package), you generate a new SFT file. Each time you create a new SFT file, you are creating a new package version.
-
-When you import applications through the Application Virtualization Server Management Console, the software automatically creates a package and a package version if they do not already exist.
-
-## Related topics
-
-
-[About Application Virtualization Applications](about-application-virtualization-applications.md)
-
-[About the Application Virtualization Server Management Console](about-the-application-virtualization-server-management-console.md)
-
-[How to Manage Packages in the Server Management Console](how-to-manage-packages-in-the-server-management-console.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/about-application-virtualization-servers.md b/mdop/appv-v4/about-application-virtualization-servers.md
deleted file mode 100644
index 6078a1f5cb..0000000000
--- a/mdop/appv-v4/about-application-virtualization-servers.md
+++ /dev/null
@@ -1,47 +0,0 @@
----
-title: About Application Virtualization Servers
-description: About Application Virtualization Servers
-author: dansimp
-ms.assetid: 60a45509-2112-44ca-8e28-c73b0c2ff85e
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# About Application Virtualization Servers
-
-
-Application Virtualization Management Servers, also called *application publishing servers*, control access to the applications that are processed to run in a virtual environment. Virtual applications are stored on the Application Virtualization Management Servers. When a virtual application is called for by the client, the application package is streamed to the client from the Application Virtualization Management Servers.
-
-**Note**
-You can also stream applications to clients from Application Virtualization Streaming Servers. Streaming Servers do not offer some of the services that are available from the Management Servers, such as publishing, management, and reporting.
-
-You can stream applications to the client directly from a file or disk. Some application virtualization deployment scenarios, which are characterized by low or unreliable connectivity or where bandwidth is limited, are ideally suited for streaming from file or disk.
-
-
-
-One or more Application Virtualization Management Servers that share a single data store make up an *Application Virtualization system*.
-
-## Related topics
-
-
-[Application Virtualization Client Management Console Overview](application-virtualization-client-management-console-overview.md)
-
-[How to Refresh Virtual Applications from the Desktop Notification Area](how-to-refresh-virtual-applications-from-the-desktop-notification-area.md)
-
-[How to Set Up Publishing Servers](how-to-set-up-publishing-servers.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/about-microsoft-application-virtualization-45-sp1.md b/mdop/appv-v4/about-microsoft-application-virtualization-45-sp1.md
deleted file mode 100644
index 2379da3dff..0000000000
--- a/mdop/appv-v4/about-microsoft-application-virtualization-45-sp1.md
+++ /dev/null
@@ -1,43 +0,0 @@
----
-title: About Microsoft Application Virtualization 4.5 SP1
-description: About Microsoft Application Virtualization 4.5 SP1
-author: dansimp
-ms.assetid: f5dcff12-5956-41ef-bc36-b59200f90807
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 08/30/2016
----
-
-
-# About Microsoft Application Virtualization 4.5 SP1
-
-
-This service pack contains the following changes:
-
-- Support for Windows 7 and Windows Server 2008 R2: App-V 4.5 SP1 provides support for Windows 7 and Windows Server 2008 R2, including support for Windows 7 features such as the taskbar, AppLocker, BranchCache, and BitLocker To Go. Windows Server 2008 R2 support applies only to Application Virtualization Server. For more information about AppLocker support in Windows 7, see [Windows AppLocker](https://go.microsoft.com/fwlink/?LinkID=156732) (https://go.microsoft.com/fwlink/?LinkID=156732).
-
-- Support for third-party Kerberos realms: App-V 4.5 SP1 provides support for environments that have a trust relationship and mapped user accounts between a Windows domain and an MIT Kerberos realm, which is a scenario commonly used at many universities. For information about how to enable this support, see [How to Configure the Client for MIT Kerberos Realm Support](https://go.microsoft.com/fwlink/?LinkId=166004) (https://go.microsoft.com/fwlink/?LinkId=166004).
-
-- Improved support for application publishing and streaming through HTTP/HTTPS: App-V 4.5 SP1 provides support for application publishing and streaming through the HTTP/HTTPS protocols for Windows XP Home Edition, Windows Vista Home Basic, and Windows 7 Home Basic.
-
-- Customer Feedback and Hotfix Rollup: App-V 4.5 SP1 also includes a rollup of fixes to address issues found after the Microsoft Application Virtualization (App-V) 4.5 CU1 release. The updates result from a combination of known issues and customer feedback from our internal teams, partners, and customers who are using App-V 4.5. For a full list of the updates, see [article 976338](https://go.microsoft.com/fwlink/?LinkId=167121) in the Microsoft Knowledge Base (https://go.microsoft.com/fwlink/?LinkId=167121).
-
-## In This Section
-
-
-[Microsoft Application Virtualization Management System Release Notes 4.5 SP1](microsoft-application-virtualization-management-system-release-notes-45-sp1.md)
-Provides the most up-to-date information about known issues with Microsoft Application Virtualization (App-V) 4.5 SP1.
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/about-microsoft-application-virtualization-45-sp2.md b/mdop/appv-v4/about-microsoft-application-virtualization-45-sp2.md
deleted file mode 100644
index 80134f7a39..0000000000
--- a/mdop/appv-v4/about-microsoft-application-virtualization-45-sp2.md
+++ /dev/null
@@ -1,41 +0,0 @@
----
-title: About Microsoft Application Virtualization 4.5 SP2
-description: About Microsoft Application Virtualization 4.5 SP2
-author: dansimp
-ms.assetid: c498adbe-e331-42c8-99fe-29623fae2345
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 08/30/2016
----
-
-
-# About Microsoft Application Virtualization 4.5 SP2
-
-
-This service pack contains the following changes:
-
-- Support for Office 2010: Microsoft Application Virtualization (App-V) 4.5 SP2 now supports the virtualization of Microsoft Office 2010. For prescriptive guidance for sequencing Office 2010 with App-V 4.5 SP2, see [Prescriptive guidance for sequencing Office 2010 in Microsoft App-V 4.6](https://go.microsoft.com/fwlink/?LinkId=191539) (https://go.microsoft.com/fwlink/?LinkId=191539).
-
-- Support for Database Mirroring: App-V 4.5 SP2 now supports Microsoft SQL Server Database Mirroring. For more information about configuring database mirroring in your App-V environment, see [How to Configure Microsoft SQL Server Mirroring Support for App-V](https://go.microsoft.com/fwlink/?LinkId=190880) (https://go.microsoft.com/fwlink/?LinkId=190880).
-
-- Customer Feedback and Hotfix Rollup: App-V 4.5 SP2 also includes a rollup of fixes to address issues found after the App-V 4.5 SP1 release. The updates address a combination of known issues and customer feedback from Microsoft internal teams, partners, and customers who are using App-V 4.5. For a full list of the updates, see article 980847 in the Microsoft Knowledge Base (KB) at [Description of Microsoft Application Virtualization 4.5 Service Pack 2](https://go.microsoft.com/fwlink/?LinkId=191540) (https://go.microsoft.com/fwlink/?LinkId=191540).
-
-## In This Section
-
-
-[App-V 4.5 SP2 Release Notes](app-v-45-sp2-release-notes.md)
-Provides the most up-to-date information about known issues with App-V 4.5 SP2.
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/about-microsoft-application-virtualization-45.md b/mdop/appv-v4/about-microsoft-application-virtualization-45.md
deleted file mode 100644
index 40b58ca9d6..0000000000
--- a/mdop/appv-v4/about-microsoft-application-virtualization-45.md
+++ /dev/null
@@ -1,49 +0,0 @@
----
-title: About Microsoft Application Virtualization 4.5
-description: About Microsoft Application Virtualization 4.5
-author: dansimp
-ms.assetid: 39f45a6f-ac55-4fd7-8a83-865e1a7034f8
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# About Microsoft Application Virtualization 4.5
-
-
-Formerly known as SoftGrid Application Virtualization, Microsoft Application Virtualization (App-V) 4.5 is the first Microsoft-branded release of the product. It includes new capabilities that make it easy for enterprise IT organizations to support large-scale, global application virtualization implementations.
-
-- Dynamic Virtualization: App-V 4.5 provides the flexibility to control virtual application interaction. Administrators who want to consolidate virtual environments and enable faster, easier administration, can use the product’s Dynamic Suite Composition, which sequences and manages packages for middleware applications separately from the main application. It shrinks potential package size by eliminating redundant packaging of middleware. This lets multiple Web applications communicate with the same single instance of a virtualized application of, for example, Microsoft .NET Framework or Sun Java Runtime Environment (JRE). Updates for the common virtual middleware are simplified and one virtual application is updated instead of several. This “many-to-one” capability greatly reduces the cost of updates. It also makes it easier to deploy and manage applications that use multiple plug-ins and add-ins, and improves management of plug-in distribution to different user groups.
-
-- Extended Scalability: Choose among three flexible deployment modes:
-
- 1. Application Virtualization Management Server, which ships as part of the Microsoft Desktop Optimization Pack and Microsoft Application Virtualization for Remote Desktop Services packages, enables dynamic streaming including package and active upgrades, and requires Microsoft Active Directory Domain Services and Microsoft SQL Server.
-
- 2. Application Virtualization Streaming Server, a lightweight version which also ships as part of the Microsoft Desktop Optimization Pack and Microsoft Application Virtualization for Remote Desktop Services packages, offers application streaming including package and active upgrades without the Active Directory Domain Services and database overheads, and enables administrators to deploy to existing servers or add streaming to Electronic Software Delivery (ESD) systems.
-
- 3. Standalone mode enables virtual applications to run without streaming and is interoperable with Microsoft Endpoint Configuration Manager and third-party ESD systems.
-
-- Globalization: The product is localized across 11 languages, includes support for foreign language applications that use special characters, and supports foreign language Active Directory and servers and runtime locale detection.
-
-- Microsoft Security Standards: Microsoft Application Virtualization (App-V) 4.5 complies with Microsoft security standards including Trustworthy Computing, Secure Windows Initiative and Security Development Lifecycle. It includes support for Internet-facing scenarios and provides Secure by Default configuration out of the box.
-
-## In This Section
-
-
-[Microsoft Application Virtualization Management System Release Notes](microsoft-application-virtualization-management-system-release-notes.md)
-Provides the most up-to-date information about known issues with Microsoft Application Virtualization (App-V) 4.5.
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/about-microsoft-application-virtualization-46-sp1.md b/mdop/appv-v4/about-microsoft-application-virtualization-46-sp1.md
deleted file mode 100644
index f2d49596f4..0000000000
--- a/mdop/appv-v4/about-microsoft-application-virtualization-46-sp1.md
+++ /dev/null
@@ -1,53 +0,0 @@
----
-title: About Microsoft Application Virtualization 4.6 SP1
-description: About Microsoft Application Virtualization 4.6 SP1
-author: dansimp
-ms.assetid: 20917eb6-c998-43f8-aefa-307eb322dc8d
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# About Microsoft Application Virtualization 4.6 SP1
-
-
-Microsoft Application Virtualization (App-V) 4.6 SP1 provides the following enhancements and new features:
-
-- Improved App-V sequencer – the App-V 4.6 SP1 sequencer has been updated to help improve the sequencing process. The enhancements include a more predictable packaging experience, and help at each step of the sequencing process. Click any of the following links for more information about the new version of the App-V sequencer.
-
- - App-V Package Accelerators can be used to automatically sequence large, complex applications. Additionally, when you apply an App-V Package Accelerator, you are not always required to manually install an application to create the virtual application package. For more information about App-V package accelerators, see [About App-V Package Accelerators (App-V 4.6 SP1)](about-app-v-package-accelerators--app-v-46-sp1-.md).
-
- - Enhanced support for sequencing different types of applications. For more information about the different types of applications, see [How to Determine Which Type of Application to Sequence (App-V 4.6 SP1)](how-to-determine-which-type-of-application-to-sequence---app-v-46-sp1-.md).
-
- - Enhanced support for using App-V project templates. For more information about App-V project templates, see [How to Create an App-V Project Template (App-V 4.6 SP1)](how-to-create-an-app-v-project-template--app-v-46-sp1-.md).
-
- - Step-by-step help during sequencing. For an example of the new step-by-step see [Type of Application Page (Learn More)](type-of-application-page--learn-more-.md).
-
- - Enhanced reporting to help identify sequencing issues. For an example of the new reporting, see [Files Excluded Page Dialog Box (App-V 4.6 SP1)](files-excluded-page-dialog-box--app-v-46-sp1-.md).
-
-- Support for using a read-only cache on RDS - App-V 4.6 SP1 now supports using a shared, read-only cache in both VDI and RDS environments. For more information about sharing a read-only cache on RDS, see [How to Configure a Read-only Cache on the App-V Client (RDS)](how-to-configure-a-read-only-cache-on-the-app-v-client--rds--sp1.md).
-
-- Support for sequencing the Microsoft .NET Framework 4 - App-V 4.6 SP1 now supports sequencing the Microsoft .NET Framework 4.
-
-- Customer Feedback and Hotfix Rollup – App-V 4.6 SP1 also includes a rollup up of fixes to address issues found since the App-V 4.6 release.
-
-## In This Section
-
-
-[App-V 4.6 SP1 Release Notes](app-v-46-sp1-release-notes.md)
-Provides the most up-to-date information about known issues with Microsoft Application Virtualization (App-V) 4.6 SP1.
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/about-microsoft-application-virtualization-46-sp2.md b/mdop/appv-v4/about-microsoft-application-virtualization-46-sp2.md
deleted file mode 100644
index ece900187a..0000000000
--- a/mdop/appv-v4/about-microsoft-application-virtualization-46-sp2.md
+++ /dev/null
@@ -1,108 +0,0 @@
----
-title: About Microsoft Application Virtualization 4.6 SP2
-description: About Microsoft Application Virtualization 4.6 SP2
-author: dansimp
-ms.assetid: 1429e314-9c38-472b-8687-3bed6cf0015c
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 08/30/2016
----
-
-
-# About Microsoft Application Virtualization 4.6 SP2
-
-
-Microsoft Application Virtualization (App-V) 4.6 SP2 provides several enhancements and new features, which are described in this topic.
-
-**Caution**
-This topic describes how to change the Windows registry by using Registry Editor. If you change the Windows registry incorrectly, you can cause serious problems that might require you to reinstall Windows. You should make a backup copy of the registry files (System.dat and User.dat) before you change the registry. Microsoft cannot guarantee that the problems that might occur when you change the registry can be resolved. Change the registry at your own risk.
-
-
-
-**Support for Windows 8 and Windows Server 2012**
-
-App-V 4.6 SP2 adds support for Windows 8 and Windows Server 2012 Remote Desktop Services.
-
-**Support for coexistence with App-V 5.0 client**
-
-App-V 4.6 SP2 provides support for coexistence with the Microsoft Application Virtualization 5.0 client. Review the App-V 5.0 documentation for instructions on how to configure the App-V 5.0 client for coexistence with the App-V 4.6 SP2 client. For more information about App-V 5.0, see [Application Virtualization 5](https://go.microsoft.com/fwlink/?LinkId=267599) on TechNet.
-
-**Ability to virtualize Adobe Reader X with Protected Mode**
-
-You can virtualize Adobe Reader X with its Protected Mode feature turned on by using the following procedures. Previously you had to disable Protected Mode in order to virtualize Adobe Reader X.
-
-Before launching the App-V Sequencer, create the following registry value under HKEY\_LOCAL\_MACHINE\\SOFTWARE \\Microsoft\\SoftGrid\\4.5\\SystemGuard\\Overrides:
-
-
-
-
-
-
-
-
-
-
-
Name
-
Type
-
Data
-
Description
-
-
-
EnableVFSPassthrough
-
DWORD
-
1
-
Set this value to 1 in order to start Adobe Reader X in Protected Mode during the launch phase.
-
-
-
-
-
-
-**Note**
-On a computer running a 64-bit operating system, create the registry value under HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Wow6432Node\\Microsoft\\SoftGrid\\4.5\\SystemGuard\\Overrides.
-
-
-
-For each OSD-file in your Adobe Reader X package, add the following items under the <POLICIES> element:
-
-`TRUE`
-
-`TRUE`
-
-`TRUE`
-
-**New Sequencer command-line parameter**
-
-When you create a Package Accelerator (PA) through the Sequencer GUI, you can select an RTF or TXT file that provides packaging and deployment guidance to the administrators who will apply the Package Accelerator. This functionality is now available using the Sequencer CLI.
-
-`/ACCELERATORDESCRIPTIONFILE:PathToDescriptionFile`
-
-Specify a path to an RTF or TXT file that provides packaging and deployment guidance when creating a Package Accelerator.
-
-**Microsoft Application Error Reporting no longer needs to be installed**
-
-When you are installing the App-V 4.6 SP2 client by using setup.msi, you no longer need to install Microsoft Application Error Reporting (dw20shared.msi). App-V 4.6 SP2 now uses Microsoft Error Reporting. For more information, see [How to Install the App-V Client by Using Setup.msi](https://go.microsoft.com/fwlink/?LinkId=267237).
-
-**Customer feedback and hotfix rollup**
-
-App-V 4.6 SP2 includes a rollup of fixes to address issues found since the App-V 4.6 SP1 release. App-V 4.6 SP2 contains the latest fixes up to and including Microsoft Application Virtualization 4.6 SP1 Hotfix 6.
-
-## In This Section
-
-
-[App-V 4.6 SP2 Release Notes](https://go.microsoft.com/fwlink/?LinkId=267600)
-Provides the most up-to-date information about known issues with App-V 4.6 SP2.
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/about-microsoft-application-virtualization-46-sp3.md b/mdop/appv-v4/about-microsoft-application-virtualization-46-sp3.md
deleted file mode 100644
index ef4f01c277..0000000000
--- a/mdop/appv-v4/about-microsoft-application-virtualization-46-sp3.md
+++ /dev/null
@@ -1,44 +0,0 @@
----
-title: About Microsoft Application Virtualization 4.6 SP3
-description: About Microsoft Application Virtualization 4.6 SP3
-author: dansimp
-ms.assetid: a6374fb0-1dfa-41f7-9a6a-3d2688492a8b
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 08/30/2016
----
-
-
-# About Microsoft Application Virtualization 4.6 SP3
-
-
-Microsoft Application Virtualization (App-V) 4.6 SP3 provides the following enhancements and new features, which are described in this topic.
-
-## Support for Windows Server 2012 R2 and Windows 8.1
-
-
-App-V 4.6 SP3 includes support for Windows Server 2012 R2 and Windows 8.1
-
-## 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](https://go.microsoft.com/fwlink/?LinkId=322049) (https://go.microsoft.com/fwlink/?LinkId=322049).
-
-## Related topics
-
-
-[App-V 4.6 SP3 Release Notes](app-v-46-sp3-release-notes.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/about-microsoft-application-virtualization-46.md b/mdop/appv-v4/about-microsoft-application-virtualization-46.md
deleted file mode 100644
index 4e2161b45f..0000000000
--- a/mdop/appv-v4/about-microsoft-application-virtualization-46.md
+++ /dev/null
@@ -1,50 +0,0 @@
----
-title: About Microsoft Application Virtualization 4.6
-description: About Microsoft Application Virtualization 4.6
-author: dansimp
-ms.assetid: 34150f34-ee74-45a6-957e-9ea6c5a497de
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# About Microsoft Application Virtualization 4.6
-
-
-Microsoft Application Virtualization (App-V) 4.6 provides the following enhancements and new features for the App-V Desktop Client, Client for Remote Desktop Services and App-V Sequencer:
-
-- Support for 64-bit applications—provides the ability to sequence and run 32-bit and 64-bit applications on 64-bit versions of Windows 7, Windows Vista, Windows XP, Windows Server 2008, Windows Server 2008 R2, Windows Server 2003 and Windows Server 2003 R2. For more information about supported operating systems, see [Application Virtualization Deployment Requirements](application-virtualization-deployment-requirements.md).
-
-- Support for Windows 7 and Windows Server 2008 R2—provides support for Windows 7 and Windows Server 2008 R2, including support for Windows 7 features such as the taskbar, Jump Lists, AppLocker, BranchCache, and BitLocker To Go.
-
-- Expands globalization and localization—provides support for 12 additional languages.
-
-- Support for Virtual Desktop Infrastructure (VDI) systems—provides the capability for the read-only shared cache to help optimize server disk storage in VDI scenarios.
-
-- Improved sequencing experience—provides improvements to the sequencing wizard and support for sequencing 32-bit and 64-bit applications.
-
-**Note**
-The App-V Management Server and Streaming Server have not been updated to version 4.6. Until they are updated, use App-V Management Server and Streaming Server 4.5 with the most recent service pack.
-
-
-
-## In This Section
-
-
-[App-V 4.6 Release Notes](app-v-46-release-notes.md)
-Provides the most up-to-date information about known issues with Microsoft Application Virtualization (App-V) 4.6.
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/about-publishing.md b/mdop/appv-v4/about-publishing.md
deleted file mode 100644
index 0aab27b334..0000000000
--- a/mdop/appv-v4/about-publishing.md
+++ /dev/null
@@ -1,43 +0,0 @@
----
-title: About Publishing
-description: About Publishing
-author: dansimp
-ms.assetid: 295074d7-123f-4740-b938-e4a371ee72fd
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# About Publishing
-
-
-You can centrally manage publishing applications to the Application Virtualization Client from the Application Virtualization Server Management Console. For example, you can assign access to applications and define when and how often the Application Virtualization Desktop Client and Client for Remote Desktop Services (formerly Terminal Services) need to refresh that information. You can set the clients to refresh this information on a set schedule or every time the user logs in to the client. Also, you can use the console's application publishing functionality to enable users to see which applications are published (or available) to the client.
-
-**Note**
-Before the client can refresh the publishing information, the client must know about the Application Virtualization Management Server. You configure the client with the necessary information about the server when you install the client.
-
-
-
-When a client contacts the server for application publishing information, the server provides the client with the list of applications that the user has permission to access and the location of the corresponding Open Software Descriptor (OSD) files. The server also provides the relevant information about icons, file type associations, and shortcuts.
-
-## Related topics
-
-
-[About Application Licensing](about-application-licensing.md)
-
-[About Application Virtualization Applications](about-application-virtualization-applications.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/about-sequencing-phases.md b/mdop/appv-v4/about-sequencing-phases.md
deleted file mode 100644
index e9f821e89a..0000000000
--- a/mdop/appv-v4/about-sequencing-phases.md
+++ /dev/null
@@ -1,49 +0,0 @@
----
-title: About Sequencing Phases
-description: About Sequencing Phases
-author: dansimp
-ms.assetid: c1cb7b6c-204c-48f2-848c-4bd5a3d5ecb6
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# About Sequencing Phases
-
-
-Sequencing is the process by which you create a sequenced application package by using the Microsoft Application Virtualization (App-V) Sequencer. During sequencing, the Sequencer monitors and records all installation and setup processes for an application and creates the following files: ICO, OSD, SFT, and SPRJ. These files contain all the necessary information about an application, and they allow that application to run in a virtual environment.
-
-The four phases to sequencing an application and creating a virtual application package are installation, launch, customization, and save. The following list provides information about each of the phases:
-
-1. **Installation phase**—During the installation phase, you specify the package name and an optional associated comment that will be associated with the package. You can also configure advanced monitoring options during this phase. Advanced monitoring options include specifying the block size and whether you will install automatic updates during monitoring. The sequencer records all necessary information and configurations required to create a virtual application package and the associated file and registry settings.
-
- **Important**
- To view the advanced options select **Show Advanced Monitoring Options** on the **Package Information** page.
-
-
-
-2. **Launch phase**—During the launch phase, you can specify any required file associations and security descriptors that should be configured with the package. You should open the application as many times as necessary to ensure application functionality and stability.
-
-3. **Customization phase**—During the customization phase, you can configure your package by using the associated .osd files. You can specify whether any associated scripts should run inside or outside of the virtual environment, specify additional actions that should be performed, specify how associated scripts run (synchronously or asynchronously), and specify any additional scripts that should be run under the user context.
-
-4. **Save phase**—During the save phase, all required files for the virtual application package are created. The files created are .sprj, .sft, .osd, .ico, .xml manifest, and the Windows installer (.msi) file.
-
-## Related topics
-
-
-[Application Virtualization Sequencer](application-virtualization-sequencer.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/about-sharing-package-accelerators-page.md b/mdop/appv-v4/about-sharing-package-accelerators-page.md
deleted file mode 100644
index 880688dd13..0000000000
--- a/mdop/appv-v4/about-sharing-package-accelerators-page.md
+++ /dev/null
@@ -1,44 +0,0 @@
----
-title: About Sharing Package Accelerators Page
-description: About Sharing Package Accelerators Page
-author: dansimp
-ms.assetid: 9630cde0-e2c3-476f-8fa1-58b3c9f7d3f7
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# About Sharing Package Accelerators Page
-
-
-This following information provides best practice information about how to share Package Accelerators. If you plan to share Package Accelerators files, information such as computer names, user account information, and information about applications included in the transforms might be included in the Package Accelerators file. You should review any settings or configuration files associated with the virtual application package to ensure the applications do not contain any personal information.This page contains the following elements.
-
-- **Username**. When you log on to the computer running the Microsoft App-V Sequencer, you should use a generic user account, such as the built-in **administrator** account. You should not use an account that is based on an existing user name.
-
-- **Computer Name**. Specify a general, non-identifying name of the computer running the Sequencer.
-
-- **Server URL**. In the App-V Sequencer console, on the **Deployment** tab, use the default settings for the server URL configuration information.
-
-- **Applications**. If you do not want to share the list of applications that were installed on the computer running the Sequencer when you created the Package Accelerator, you must delete the **appv\_manifest.xml** file. This file is located in the package root directory of the virtual application package.
-
-## Related topics
-
-
-[Create Package Accelerator Wizard (AppV 4.6 SP1)](create-package-accelerator-wizard--appv-46-sp1-.md)
-
-[About App-V Package Accelerators (App-V 4.6 SP1)](about-app-v-package-accelerators--app-v-46-sp1-.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/about-the-application-virtualization-sequencer.md b/mdop/appv-v4/about-the-application-virtualization-sequencer.md
deleted file mode 100644
index c51d335407..0000000000
--- a/mdop/appv-v4/about-the-application-virtualization-sequencer.md
+++ /dev/null
@@ -1,100 +0,0 @@
----
-title: About the Application Virtualization Sequencer
-description: About the Application Virtualization Sequencer
-author: dansimp
-ms.assetid: bee193ca-58bd-40c9-b41a-310435633895
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# About the Application Virtualization Sequencer
-
-
-The Microsoft Application Virtualization (App-V) Sequencer monitors and records all installation and setup processes for an application and creates the following files: **ICO**, **OSD**, **SFT**, and **SPRJ**. These files contain all the necessary information about an application so the application can run in a virtual environment on target computers. You can use the Microsoft Application Virtualization (App-V) Sequencer to create virtual applications. After you sequence an application, it can be streamed to target computers, or target computers can run the virtual application by downloading the contents of the virtual application package and running the application locally.
-
-**Important**
-To run a virtual application package the target computer must be running the appropriate version of the App-V client.
-
-
-
-Virtual application packages run on target computers without interacting with the underlying operating system on the target computer because each application runs in a virtual environment and is isolated from other applications that are installed or running on the target computer. This isolation can reduce application conflicts and can help decrease the required amount of application pre-deployment testing.
-
-## Sequencer Terminology
-
-
-Application Virtualization drive
-The application virtualization drive is the default drive (Q:\) on the target computer from which sequenced applications are run.
-
-ICO file
-The icon file on the client desktop which is used to launch a sequenced application.
-
-Installation directory
-The directory used by the sequencer to place installation files during setup.
-
-Open Software Descriptor (OSD) file
-An XML-based file that instructs the App-V client how to retrieve the sequenced application from the App-V streaming server and how to run the sequenced application in the virtual environment.
-
-Package root directory
-The directory on the sequencing computer on which files for the sequenced application package are installed. This directory also exists virtually on the computer to which a sequenced application will be streamed.
-
-Sequenced application
-An application that has been monitored by the sequencer, broken up into primary and secondary feature blocks, streamed to a target computer running the App-V client t, and runs a virtual environment.
-
-Sequenced application package
-The files that comprise a virtual application and allow a virtual application to run. These files are created after sequencing and specifically include **.osd**, **.sft**, **.sprj**, and **.ico** files.
-
-Sequencing
-The process of creating an application package using the App-V Sequencer. In this process, an application is monitored, its shortcuts are configured, and a sequenced application package is created.
-
-Sequencing computer
-The computer used to sequence an application.
-
-Virtual application
-An application packaged by the Sequencer to run in a self-contained, virtual environment. The virtual environment contains the information necessary to run the application on the client without installing the application locally.
-
-Primary feature block
-The minimum content in a virtual application package that is necessary for an application to run on a target computer. The content in the primary feature block is identified during the application phase of sequencing and typically consists of the content for the most used application features.
-
-## Sequencing Applications
-
-
-There are two methods to create and modify virtual application packages in your environment. The first method is by using the **Sequencing** wizard. The **Sequencing** wizard allows you to create new, or modify existing virtual application packages. For more information about using the **Sequencing** wizard see, [How to Sequence a New Application](how-to-sequence-a-new-application.md). The second method is by using the command-line. The command-line allows you to create new, or modify existing virtual application packages using the command prompt. For more information about using the command line see, [How to Manage Virtual Applications Using the Command Line](how-to-manage-virtual-applications-using-the-command-line.md).
-
-The **Sequencing** wizard provides the following functions for creating virtual application packages:
-
-1. **Package Configuration**: The **Sequencing** Wizard prompts for package configuration information necessary to complete the Open Software Descriptor (OSD) file, which is a required file for starting a sequenced application package.
-
-2. **Application Installation**: The **Sequencing** Wizard gathers information about an application’s installation and startup configurations. It monitors and records the installation and startup information associated with the application to create the files necessary for a virtual application package.
-
-3. **Application Startup**: The **Sequencing** Wizard gathers information for compiling and ordering the blocks of code necessary to perform the initial startup of the sequenced application package on the target computer. The compilation of the code block is referred to as the primary feature block.
-
-## Application Virtualization Sequencer Security Considerations
-
-
-The App-V Sequencer runs all services detected at sequencing time using the Local System account and does not enforce security descriptors on service control requests. If the service was installed using a different user account or if the security descriptors are intended to grant different user groups specific service permissions, consider carefully whether the service should be virtualized. In some cases, you should install the service locally to ensure that the intended service security is preserved.
-
-**Important**
-You should always save virtual application packages in a secure location.
-
-
-
-## Related topics
-
-
-[Application Virtualization Sequencer Overview](application-virtualization-sequencer-overview.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/about-the-application-virtualization-server-management-console.md b/mdop/appv-v4/about-the-application-virtualization-server-management-console.md
deleted file mode 100644
index e3654b07e0..0000000000
--- a/mdop/appv-v4/about-the-application-virtualization-server-management-console.md
+++ /dev/null
@@ -1,54 +0,0 @@
----
-title: About the Application Virtualization Server Management Console
-description: About the Application Virtualization Server Management Console
-author: dansimp
-ms.assetid: 108d0e4b-08fa-47b4-a737-d2c36c2641de
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# About the Application Virtualization Server Management Console
-
-
-This section of the Application Virtualization Server Management Help describes some of the concepts you should understand while working with the Application Virtualization Server Management Console.
-
-## In This Section
-
-
-[About Application Virtualization Applications](about-application-virtualization-applications.md)
-Provides an overview of managing applications from the Application Virtualization Server Management Console.
-
-[About Application Virtualization Packages](about-application-virtualization-packages.md)
-Provides an overview of managing packages from the Application Virtualization Server Management Console.
-
-[About Publishing](about-publishing.md)
-Provides an overview of how you can publish applications from the Application Virtualization Server Management Console.
-
-[About Application Licensing](about-application-licensing.md)
-Provides an overview of how you can manage application licensing from the Application Virtualization Server Management Console and the types of licenses available.
-
-## Reference
-
-
-[Application Virtualization Server Management Console Reference](application-virtualization-server-management-console-reference.md)
-
-## Related Sections
-
-
-[How to Perform Administrative Tasks in the Application Virtualization Server Management Console](how-to-perform-administrative-tasks-in-the-application-virtualization-server-management-console.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/about-the-deployment-tab.md b/mdop/appv-v4/about-the-deployment-tab.md
deleted file mode 100644
index 7a0a6c25b4..0000000000
--- a/mdop/appv-v4/about-the-deployment-tab.md
+++ /dev/null
@@ -1,154 +0,0 @@
----
-title: About the Deployment Tab
-description: About the Deployment Tab
-author: dansimp
-ms.assetid: 12891798-baa4-45a5-b845-b9505ab95633
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 08/30/2016
----
-
-
-# About the Deployment Tab
-
-
-Use the **Deployment** tab in the Application Virtualization Sequencer Console to change the information for an application you are about to sequence. This tab contains the following elements.
-
-## Server URL
-
-
-Use the **Server URL** controls to specify the virtual application server configuration settings.
-
-
-
-
-
-
-
-
-
Control
-
Description
-
-
-
-
-
Protocol
-
Enables you to select the protocol that will stream the sequenced application package from a virtual application server to an Application Virtualization Desktop Client. The following protocols are available:
-
-
RTSP—The default, it specifies that the Real-Time Streaming Protocol controls the exchange of virtualization-enabled applications.
-
RTSPS—Specifies that the Real-Time Streaming Protocol with Transport Layer Security controls the exchange of a sequenced application package.
-
File—Specifies that the sequenced application will be streamed from a file share.
-
HTTPS—Specifies that Secure Hypertext Transport Protocol controls the exchange of a package.
-
-
-
-
Hostname
-
Enables you to select the virtual application server or the load balancer in front of a group of virtual application servers that will stream the software package to an Application Virtualization Desktop Client. You must complete this item to create a sequenced application package, but you can change from the default %SFT_SOFTGRIDSERVER% environment variable to the actual hostname or IP address of a virtual application server.
-
-Note
If you choose not to specify a static hostname or IP address, on each Application Virtualization Desktop Client you must set up an environment variable called SFT_SOFTGRIDSERVER. Its value must be the hostname or IP address of the virtual application server or load balancer that is this client's source of applications. You should make this environment variable a system variable rather than a user variable. Any Application Virtualization Desktop Client session that is running on this computer during your assignment of this variable must be closed and then opened so that the resumed session will be aware of its new application source.
-
-
-
-
-
-
-
Port
-
Enables you to specify the port on which the virtual application server or the load balancer will listen for an Application Virtualization Desktop Client's request for the package. This information is required to create a package, but you can change it. The default port is 554.
-
-
-
Path
-
Enables you to specify the relative path on the virtual application server where the software package is stored and from which it will be streamed. This information is required to create a package if the SFT file will be stored in a subdirectory of CONTENT; otherwise, this information is not required.
-
-
-
-
-
-
-## Operating Systems
-
-
-Use the **Operating Systems** controls to specify the application's operating system requirements. If an Application Virtualization Desktop Client cannot support any of the selected operating systems, the application will not start.
-
-
-
-
-
-
-
-
-
Controls
-
Description
-
-
-
-
-
Available Operating Systems
-
Displays a list of operating systems that can support the applications in the package.
-
-
-
Selected Operating Systems
-
Displays a list of selected operating systems that support the applications in the package.
-
-
-
-
-
-
-## Output Options
-
-
-Use the **Output Options** controls to specify the output options for the application to be installed.
-
-
-
-
-
-
-
-
-
Control
-
Description
-
-
-
-
-
Compression Algorithm
-
Use to select the method for compressing the SFT file for streaming across a network. Select one of the following compression methods:
-
-
Compressed—Specifies that the SFT file be compressed in the ZLIB format.
-
Not Compressed—The default; specifies that the SFT file not be compressed.
-
-
-
-
Enforce Security Descriptors
-
Select to enforce security descriptors of the applications in the package after it is deployed to the client.
-
-
-
Generate Microsoft Windows Installer (MSI) Package
-
Select to install or deploy a sequenced application package with the Windows Installer. If you have made any changes using the sequencer the changes will not be included with the Windows Installer file. The Windows Installer file will always be created using the .sft file saved on the hard disk.
-
-
-
-
-
-
-## Related topics
-
-
-[How to Change Deployment Properties](how-to-change-deployment-properties.md)
-
-[Sequencer Console](sequencer-console.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/about-the-files-tab.md b/mdop/appv-v4/about-the-files-tab.md
deleted file mode 100644
index 2281e4a415..0000000000
--- a/mdop/appv-v4/about-the-files-tab.md
+++ /dev/null
@@ -1,75 +0,0 @@
----
-title: About the Files Tab
-description: About the Files Tab
-author: dansimp
-ms.assetid: 3c20e720-4b0f-465b-b7c4-3013dae1c815
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# About the Files Tab
-
-
-The **Files** tab displays the complete list of files that are included in a sequenced application package. The left pane displays, in a standard file browse format, the complete list of files in the package that was created during the application sequencing. These files include the package root directory (the directory you specified during the application installation phase), the Virtual File System (VFS) folder, and the virtual environment files. The right pane displays the file name, file attributes, and the Sequencer attributes.
-
-## File Name and Short Name
-
-
-**File Name**
-The name of the file is in the left pane. The files displayed in the left pane are created during sequencing.
-
-**Short Name**
-This is the name of a file selected in the left pane, written in the 8.3 format naming convention.
-
-## File Attributes
-
-
-**File Size**
-The size of the file in bytes.
-
-**File Version**
-The version of the selected file.
-
-**Date Created**
-The date and time the selected file was created.
-
-**Date Modified**
-The date and time the selected file was last modified.
-
-**File ID**
-The file GUID.
-
-## Sequencer Attributes
-
-
-**User Data**
-Select this attribute to specify that an application must retain the information of an individual user.
-
-**Application Data**
-Select this attribute to specify that an application must retain the general information of a group of users.
-
-**Override**
-When selected, the Application Virtualization Desktop Client overwrites the corresponding file when the sequenced application package is upgraded and streamed to the client. If this check box is not selected, the client determines whether or not to overwrite the selected file.
-
-## Related topics
-
-
-[How to Modify the Files Included in a Package](how-to-modify-the-files-included-in-a-package.md)
-
-[Sequencer Console](sequencer-console.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/about-the-osd-tab.md b/mdop/appv-v4/about-the-osd-tab.md
deleted file mode 100644
index cd15ddc088..0000000000
--- a/mdop/appv-v4/about-the-osd-tab.md
+++ /dev/null
@@ -1,64 +0,0 @@
----
-title: About the OSD Tab
-description: About the OSD Tab
-author: dansimp
-ms.assetid: 7c78cd3a-91f2-4377-8c62-e52912906197
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# About the OSD Tab
-
-
-An OSD (Open Software Descriptor) file is produced after sequencing. It provides instructions for how a client is to retrieve and run a sequenced application package. Use the **OSD** tab to display and modify the OSD files in the sequenced application package.
-
-## Drop-Down List
-
-
-**Drop down**
-Displays a list of sequenced applications. Select a sequenced application package to modify the elements of an OSD file.
-
-## Navigation Pane
-
-
-**Navigation Pane**
-Displays a list of elements in the OSD file.
-
-## Results Pane
-
-
-**Attribute**
-Displays one or more attributes of an element.
-
-**Value**
-Displays the value that corresponds to an attribute.
-
-**Element Text**
-Displays an editable comment that corresponds to an element.
-
-## Related topics
-
-
-[How to Edit an OSD File Using a Text Editor](how-to-edit-an-osd-file-using-a-text-editor.md)
-
-[How to Edit an OSD File](how-to-edit-an-osd-file.md)
-
-[OSD File Elements](osd-file-elements.md)
-
-[Sequencer Console](sequencer-console.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/about-the-properties-tab.md b/mdop/appv-v4/about-the-properties-tab.md
deleted file mode 100644
index 49f24affb3..0000000000
--- a/mdop/appv-v4/about-the-properties-tab.md
+++ /dev/null
@@ -1,88 +0,0 @@
----
-title: About the Properties Tab
-description: About the Properties Tab
-author: dansimp
-ms.assetid: a6cf6f51-3778-4c8d-9632-3af4005775d2
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# About the Properties Tab
-
-
-Use the **Properties** tab to view basic statistical information about a sequenced application package. The information is automatically generated unless otherwise noted. This tab contains the following elements.
-
-## Package Information
-
-
-**Package Name**
-The single name used for a sequenced application package that might contain one or more applications—for example, Microsoft Office could be used to label a sequenced application package that contains Microsoft Word and Microsoft Excel applications that run in the same virtual environment.
-
-**Comments**
-Displays a short description of the software package that will appear in the Open Software Descriptor (OSD) file ABSTRACT element. This item is optional.
-
-**Package Version**
-The sequenced application package version.
-
-**Package GUID**
-The globally unique identifier (GUID) automatically assigned to the sequenced application package to distinguish it from other sequenced application packages that might be running on the computer to which a sequenced application package is streamed.
-
-**Package Version GUID**
-The sequenced application package version GUID.
-
-**Root Directory**
-The directory on the sequencing computer in which files for the sequenced application package are installed. This directory is also created on the computer to which a sequenced application package will be streamed. It is recommended for backwards compatibility that this be an 8.3 format directory name at the root of the Q drive, such as Q:\\MyApp.1\\.
-
-**Created**
-The date and time the sequenced application package was created.
-
-**Modified**
-The date and time the sequenced application package was last modified.
-
-**Package Size**
-The size of the package in megabytes.
-
-**Launch Size**
-The size in megabytes of the portion of the SFT file that is required to start the application.
-
-## Sequencing Parameters
-
-
-**Block Size**
-Specifies the size of the primary and secondary feature blocks into which the SFT file is divided for streaming across a network. All blocks equal the specified size; however, the last block might be smaller than specified. You will see one of the following values:
-
-- 4 KB
-
-- 16 KB
-
-- 32 KB
-
-- 64 KB
-
-**Note**
-After the initial package has been created, the block size value is not changeable.
-
-
-
-## Related topics
-
-
-[How to Change Package Properties](how-to-change-package-properties.md)
-
-[Sequencer Console](sequencer-console.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/about-the-sequencer-console.md b/mdop/appv-v4/about-the-sequencer-console.md
deleted file mode 100644
index c9ade6aad8..0000000000
--- a/mdop/appv-v4/about-the-sequencer-console.md
+++ /dev/null
@@ -1,83 +0,0 @@
----
-title: About the Sequencer Console
-description: About the Sequencer Console
-author: dansimp
-ms.assetid: 36ecba89-a0f5-4d4d-981c-7f581aa43695
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# About the Sequencer Console
-
-
-Before you start using the Microsoft Application Virtualization (App-V) sequencer, you should be familiar with the following information about the App-V sequencer console. The following sections describe the tools available in the Sequencer console.
-
-## Application Virtualization Sequencer Console Menu Options
-
-
-The following menu items are available in the App-V Sequencer Console:
-
-- **File** - Contains various commands to help create, open, modify, and save sequenced applications.
-
-- **Edit** - Contains various commands for editing existing virtual applications.
-
-- **View** - Contains various commands for viewing properties of a virtual application.
-
-- **Tools** - Contains various tools and diagnostics for configuring virtual applications.
-
-## Application Virtualization Sequencer Console Toolbar Options
-
-
-The following toolbar buttons are available in the App-V Sequencer Console:
-
-- **New Package** - Click to create a new sequenced application.
-
-- **Open** - Click to open a sequenced application package in the App-V Sequencer Console.
-
-- **Open for Upgrade** - Click to open a sequenced application to upgrade or apply an update.
-
-- **Save** - Click to save a sequenced virtual application.
-
-- **Sequencing Wizard** - Click to open the Sequencing Wizard. You should use this button to start the Sequencing Wizard if you make any changes on the **General** tab under **Tools** / **Options**.
-
-## Virtual Application Tabs
-
-
-The following tabs are displayed when you view a virtual application in the App-V Sequencer Console:
-
-- **Properties** - Displays information about the selected virtual application. You can update the Package Name and Comments associated with the virtual application.
-
-- **Deployment** - Displays information about how the virtual application will be accessed by target computers. You can configure the virtual application delivery method, and you can configure which operating systems must be running on the target computer. You can also configure the associated output options. If you plan to have clients access a virtual application from a file, use the following format when specifying the path: **File://server/share/path/.sft**. Select **Enforce Security Descriptors** to preserve security associated with the package during an upgrade, or the permissions will be reset during the upgrade.
-
-- **Change History** - Displays information about updates that have been made to the virtual application.
-
-- **Files** - Displays the files associated with the selected virtual application. You can make minor revisions to the associated file properties by using the appropriate fields.
-
-- **Virtual Registry** - Displays the virtual registry associated with the selected virtual application. You can add or delete registry keys by right-clicking the appropriate entry.
-
-- **Virtual File System** - Displays the virtual file systems associated with the selected virtual application. You can add, delete, or edit file system entries on this tab by right-clicking the appropriate entry and selecting the option.
-
-- **Virtual Services** - Displays the services associated with the selected virtual application.
-
-- **OSD** - Displays information about the Open Software Descriptor (OSD) associated with the virtual application. You can update the files associated with the OSD file by right-clicking the appropriate entry and selecting the action that you want.
-
-## Related topics
-
-
-[Application Virtualization Sequencer Overview](application-virtualization-sequencer-overview.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/about-the-virtual-file-system-tab.md b/mdop/appv-v4/about-the-virtual-file-system-tab.md
deleted file mode 100644
index c63df76467..0000000000
--- a/mdop/appv-v4/about-the-virtual-file-system-tab.md
+++ /dev/null
@@ -1,47 +0,0 @@
----
-title: About the Virtual File System Tab
-description: About the Virtual File System Tab
-author: dansimp
-ms.assetid: 4d2e344d-3f3b-49fd-bbbd-fa5177e7af50
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 08/30/2016
----
-
-
-# About the Virtual File System Tab
-
-
-The virtual file system is created during sequencing. It maps directories and files that are added or modified outside the package root directory. The **Virtual File System** tab displays the entire virtual file system for a sequenced application package. It also allows you to add, edit, and delete file associations.
-
-For information about the virtual file system and its use, see the section “VFS Installs” of [Advanced Sequencing Topics](https://go.microsoft.com/fwlink/?LinkId=114543), at https://go.microsoft.com/fwlink/?LinkId=114543.
-
-## Columns
-
-
-**From**
-Displays the application's component files in the SFT file as they will be distributed on an Application Virtualization Desktop Client.
-
-**To**
-Displays the application's component files as they have been distributed by the application installer on the Application Virtualization Sequencer.
-
-## Related topics
-
-
-[How to Modify File-Mapping Information](how-to-modify-file-mapping-information.md)
-
-[Sequencer Console](sequencer-console.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/about-the-virtual-registry-tab.md b/mdop/appv-v4/about-the-virtual-registry-tab.md
deleted file mode 100644
index 580a4456c0..0000000000
--- a/mdop/appv-v4/about-the-virtual-registry-tab.md
+++ /dev/null
@@ -1,62 +0,0 @@
----
-title: About the Virtual Registry Tab
-description: About the Virtual Registry Tab
-author: dansimp
-ms.assetid: ca8d837f-8218-4f86-95fd-13a44dccd022
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# About the Virtual Registry Tab
-
-
-A virtual registry is created during sequencing. The **Virtual Registry** tab displays all the registry keys and values that are required for a sequenced application package to run. Use this tab to add, edit, and delete registry keys and registry values.
-
-You can also choose to ignore the hosting system’s keys by selecting **Override Local Key**, or you can create a merged view of the key from within the virtual environment by selecting **Merge with Local Key**.
-
-The changes to the virtual registry **Settings** tab affect applications that are part of the specific sequenced application package, but they do not affect the operation of other applications that are streamed to or locally installed on the Application Virtualization Desktop Client.
-
-**Note**
- Exercise caution when changing virtual registry keys and values. Changing these keys and values might render your sequenced application package inoperable.
-
-
-
-The left pane of the **Virtual Registry** tab displays the full list of virtual registries created during the sequencing of an application.
-
-## Columns
-
-
-**Name**
-The name for the entry in the virtual registry.
-
-**Type**
-How the entry stores its data.
-
-**Data**
-The value stored by the entry.
-
-**Attributes**
-Displays the file attributes.
-
-## Related topics
-
-
-[How to Modify Virtual Registry Key Information](how-to-modify-virtual-registry-key-information.md)
-
-[Sequencer Console](sequencer-console.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/about-the-virtual-services-tab.md b/mdop/appv-v4/about-the-virtual-services-tab.md
deleted file mode 100644
index 9da1a5c4f1..0000000000
--- a/mdop/appv-v4/about-the-virtual-services-tab.md
+++ /dev/null
@@ -1,54 +0,0 @@
----
-title: About the Virtual Services Tab
-description: About the Virtual Services Tab
-author: dansimp
-ms.assetid: d31eea1b-9a37-42f1-8d7c-95881716e753
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# About the Virtual Services Tab
-
-
-During sequencing, a list of embedded services are identified and sequenced. Embedded services help an operating system run. The **Virtual Services** tab displays a list of embedded services. It also allows you to edit the properties of the individual services.
-
-## Columns
-
-
-**Name**
-The name of the service.
-
-**Description**
-A description of the service.
-
-**Startup Type**
-Indicates whether virtual services on the client are set to manual or automatic start-up.
-
-**Logon As**
-Indicates the client log-on identity—for example, LocalSystem.
-
-**Services Type**
-Indicates the type of service running on the Client.
-
-## Related topics
-
-
-[How to Modify Attributes of Embedded Services](how-to-modify-attributes-of-embedded-services.md)
-
-[Sequencer Console](sequencer-console.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/about-using-the-sequencer-command-line.md b/mdop/appv-v4/about-using-the-sequencer-command-line.md
deleted file mode 100644
index b54eeb6152..0000000000
--- a/mdop/appv-v4/about-using-the-sequencer-command-line.md
+++ /dev/null
@@ -1,58 +0,0 @@
----
-title: About Using the Sequencer Command Line
-description: About Using the Sequencer Command Line
-author: dansimp
-ms.assetid: 0fd5f81b-17f9-4065-bce2-8785e8aac7c7
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# About Using the Sequencer Command Line
-
-
-You can use the command line to create sequenced application packages. Using the command line to create virtual applications is useful in the following scenarios:
-
-- You need to create a large number of sequenced application packages.
-
-- You need to create a sequenced application package on a recurring basis.
-
-**Important**
-Sequencing at the command prompt allows for default sequencing only. If you need to change default sequencing parameters, you must either manually modify a sequenced application package or re-sequence the application.
-
-
-
-All subsequent modifications to existing sequenced application packages must be made using the sequencing wizard.
-
-## Prerequisites
-
-
-To sequence an application by using the command prompt, the following conditions must be met:
-
-- The application that is about to be sequenced must not require changes or workarounds made to it outside the installer or Windows Installer package.
-
-- Before sequencing, you must prepare a list of batch files for creating the sequenced application packages.
-
-- Review For more information about the command line parameters, see [Command-Line Parameters](command-line-parameters.md).
-
-- Review the errors that might be displayed when creating a sequenced application package by using the command line. For more information, see these errors, see [Command-Line Errors](command-line-errors.md).
-
-## Related topics
-
-
-[How to Manage Virtual Applications Using the Command Line](how-to-manage-virtual-applications-using-the-command-line.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/about-virtual-environments.md b/mdop/appv-v4/about-virtual-environments.md
deleted file mode 100644
index 263e550a58..0000000000
--- a/mdop/appv-v4/about-virtual-environments.md
+++ /dev/null
@@ -1,54 +0,0 @@
----
-title: About Virtual Environments
-description: About Virtual Environments
-author: dansimp
-ms.assetid: e03a8c72-56c1-4ae9-aa45-0283c50a154c
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# About Virtual Environments
-
-
-Virtual applications run in virtual environments. Virtual environments enable each application to run on a desktop, laptop, or Remote Desktop Session Host (RD Session Host) server without installation and alteration of the host operating system. Each application carries its own configuration information in the virtual environment. As a result, many applications run side by side with other applications on the same computer without any conflicts.
-
-Virtual applications run locally, so they run with the full performance, functionality, and access to local services that you would expect from any application installed locally.
-
-Because each application runs in a virtual environment, the following problems are reduced:
-
-- Application conflicts—In environments that do not use Application Virtualization, you must thoroughly test every application to ensure that it does not interfere with other installed applications.
-
-- Regression testing—Because the application does not change the underlying operating system, lengthy regression testing is eliminated.
-
-- Version incompatibilities—Different versions of the same application can run simultaneously on the same computer.
-
-- Multiuser access—Applications that do not run in multiuser mode, and therefore cannot run within an RD Session Host, can now do so and function correctly for multiple users on a single RD Session Host.
-
-- Multitenancy issues—Two instances of the same application that use different configurations can run on the same computer at the same time.
-
-- Server siloing—The need for many separate server farms is eliminated.
-
-Virtual environments include a virtual registry for each application. Registry settings created by one application cannot be seen by other applications or utilities such as Regedit. Rather than copying the entire registry, the virtual registry uses an *overlay* method. Items in the client registry can be read by the application as long as a virtual copy of that registry item is not included in the virtual registry. All application writes to the registry are contained in the virtual registry.
-
-Virtual environments also include a virtual file system and other virtual components, including virtual services and virtual COM.
-
-## Related topics
-
-
-[Application Virtualization Client Management Console Overview](application-virtualization-client-management-console-overview.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/add-app.md b/mdop/appv-v4/add-app.md
deleted file mode 100644
index be8e8866ee..0000000000
--- a/mdop/appv-v4/add-app.md
+++ /dev/null
@@ -1,99 +0,0 @@
----
-title: ADD APP
-description: ADD APP
-author: dansimp
-ms.assetid: 329fd0c8-a795-49be-b0fd-1367c5b4a34b
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# ADD APP
-
-
-Adds an application record.
-
-`SFTMIME ADD APP:application /OSD osd-pathname [/ICON icon-pathname] [/LOG log-pathname | /CONSOLE | /GUI]`
-
-
-
-
-
-
-
-
-
Parameter
-
Description
-
-
-
-
-
APP:<application>
-
The name and version (optional) of the application.
-
-
-
/OSD <osd-pathname>
-
The path or URL for the OSD file.
-
-
-
/ICON <icon-pathname>
-
The path or URL for the icon file.
-
-
-
/LOG
-
If specified, output is logged to the specified path name.
-
-
-
/CONSOLE
-
If specified, output is presented in the active console window (default).
-
-
-
/GUI
-
If specified, output is presented in a Windows dialog box.
-
-
-
-
-
-
-For version 4.6, the following option has been added.
-
-
-
-
-
-
-
-
-
/LOGU
-
If specified, output is logged to the specified path name in UNICODE format.
-
-
-
-
-
-
-**Note**
-The resulting name of the application will be taken from the OSD file and not from the name provided in APP:<application>.
-
-
-
-## Related topics
-
-
-[SFTMIME Command Reference](sftmime--command-reference.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/add-package.md b/mdop/appv-v4/add-package.md
deleted file mode 100644
index 80ed132da5..0000000000
--- a/mdop/appv-v4/add-package.md
+++ /dev/null
@@ -1,126 +0,0 @@
----
-title: ADD PACKAGE
-description: ADD PACKAGE
-author: dansimp
-ms.assetid: aa83928d-a234-4395-831e-2a7ef786ff53
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# ADD PACKAGE
-
-
-Adds a package record. If the package already exists, this command will update the configuration of the existing package.
-
-`SFTMIME ADD PACKAGE:package-name /MANIFEST manifest-path [/OVERRIDEURL url [/AUTOLOADONREFRESH] [/AUTOLOADONLOGIN] [/AUTOLOADONLAUNCH] [/AUTOLOADTARGET {NONE|ALL|PREVUSED}] [/GLOBAL] [/LOG log-pathname | /CONSOLE | /GUI]`
-
-
-
-
-
-
-
-
-
Parameter
-
Description
-
-
-
-
-
PACKAGE:<package-name>
-
User-visible and user-friendly name for the package.
-
-
-
/MANIFEST <manifest-path>
-
The path of the manifest file that lists the applications included in the package and all of their publishing information.
-
-
-
/OVERRIDEURL <URL>
-
The location of the package's SFT file.
-
-
-
/AUTOLOADONREFRESH
-
Background loading is performed after a publishing refresh.
-
-
-
/AUTOLOADONLOGIN
-
Background loading is performed when a user logs in.
-
-
-
/AUTOLOADONLAUNCH
-
Background loading is performed after a user starts an application from the package.
-
-
-
/AUTOLOADTARGET target
-
Indicates which applications from the package will be autoloaded.
-
-
-
NONE
-
No autoloading will be performed, despite the presence of any /AUTOLOADONxxx flags.
-
-
-
ALL
-
If an autoload trigger is enabled, all applications in the package will be loaded into cache whether or not they have been previously started.
-
-
-
PREVUSED
-
If an autoload trigger is enabled, the package will load if any applications in this package have previously been started by a user.
-
-
-
/GLOBAL
-
If present, the package will be available for all users on this computer.
-
-
-
/LOG
-
If specified, output is logged to the specified path name.
-
-
-
/CONSOLE
-
If specified, output is presented in the active console window (default).
-
-
-
/GUI
-
If specified, output is presented in a Windows dialog box.
-
-
-
-
-
-
-For version 4.6, the following option has been added.
-
-
-
-
-
-
-
-
-
/LOGU
-
If specified, output is logged to the specified path name in UNICODE format.
The host name or IP address for the publishing server.
-
-
-
/TYPE {HTTP|RTSP}
-
Indicates whether the publishing server is a Web server ("HTTP") or an Application Virtualization Server ("RTSP").
-
-
-
/PORT <port>
-
The port on which the publishing server listens. Defaults to 80 for normal HTTP servers, 443 for HTTP servers using enhanced security, 554 for normal Application Virtualization Servers, and 322 for servers using enhanced security.
-
-
-
/PATH <path>
-
The path portion of the URL used in a publishing request. If the TYPE parameter is set to RTSP, the path is optional and defaults to "/".
-
-
-
/REFRESH
-
If set to ON, publishing information will be refreshed when the user logs in. Defaults to ON.
-
-
-
/SECURE
-
If present, indicates that a connection with enhanced security should be established to the publishing server.
-
-
-
/LOG
-
If specified, output is logged to the specified path name.
-
-
-
/CONSOLE
-
If specified, output is presented in the active console window (default).
-
-
-
/GUI
-
If specified, output is presented in a Windows dialog box.
-
-
-
-
-
-
-For version 4.6, the following option has been added.
-
-
-
-
-
-
-
-
-
/LOGU
-
If specified, output is logged to the specified path name in UNICODE format.
The file name extension that will be associated with the application specified.
-
-
-
/APP <application>
-
The name and version (optional) of the application.
-
-
-
/ICON <icon-pathname>
-
The path or URL for the icon file.
-
-
-
/DESCRIPTION <type-desc>
-
The user-friendly name for the file type. Defaults to "EXTENSION File."
-
-
-
/CONTENT-TYPE <content-type>
-
The content type of the file. Defaults to "application/softricity-extension."
-
-
-
/GLOBAL
-
If present, the package will be available for all users on this computer.
-
-
-
/PERCEIVED-TYPE <perceived-type>
-
The perceived type of the file. Defaults to nothing.
-
-
-
/PROGID <progid>
-
The programmatic identifier for the file type. Defaults to App Virt.extension.File.
-
-
-
/CONFIRMOPEN
-
Indicates whether users downloading a file of this type should be asked whether to open or save the file. Defaults to YES.
-
-
-
/SHOWEXT
-
Indicates whether the file's extension should always be shown, even if the user has requested that all extensions be hidden. Defaults to NO.
-
-
-
/NEWMENU
-
Indicates whether an entry should be added to the shell's New menu. Defaults to NO.
-
-
-
/LOG
-
If specified, output is logged to the specified path name.
-
-
-
/CONSOLE
-
If specified, output is presented in the active console window (default).
-
-
-
/GUI
-
If specified, output is presented in a Windows dialog box.
-
-
-
-
-
-
-For version 4.6, the following option has been added.
-
-
-
-
-
-
-
-
-
/LOGU
-
If specified, output is logged to the specified path name in UNICODE format.
-
-
-
-
-
-
-## Related topics
-
-
-[SFTMIME Command Reference](sftmime--command-reference.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/administrators-node.md b/mdop/appv-v4/administrators-node.md
deleted file mode 100644
index 633c1da358..0000000000
--- a/mdop/appv-v4/administrators-node.md
+++ /dev/null
@@ -1,51 +0,0 @@
----
-title: Administrators Node
-description: Administrators Node
-author: dansimp
-ms.assetid: 5f462a0d-af53-4464-9891-7b712193c7e8
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Administrators Node
-
-
-The **Administrators** node is one level below the Application Virtualization System node in the **Scope** pane in the Application Virtualization Server Management Console. When you select this node, the **Results** pane displays a list of administrator groups. Right-click the **Administrators** node to display a pop-up menu that contains the following elements.
-
-**Add Administrator Group**
-Displays the **Select Groups** dialog to find and add the desired administrator group. Click **Finish** to add the group.
-
-**View**
-Changes the appearance and content of the **Results** pane.
-
-**New Window from Here**
-Opens a new management console with the selected node as the root node.
-
-**Refresh**
-Refreshes the view of the server.
-
-**Help**
-Displays the help system for the Application Virtualization Server Management Console.
-
-## Related topics
-
-
-[How to Perform Administrative Tasks in the Application Virtualization Server Management Console](how-to-perform-administrative-tasks-in-the-application-virtualization-server-management-console.md)
-
-[Server Management Console: Administrators Node](server-management-console-administrators-node.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/administrators-results-pane-columns.md b/mdop/appv-v4/administrators-results-pane-columns.md
deleted file mode 100644
index 57de6d3cde..0000000000
--- a/mdop/appv-v4/administrators-results-pane-columns.md
+++ /dev/null
@@ -1,61 +0,0 @@
----
-title: Administrators Results Pane Columns
-description: Administrators Results Pane Columns
-author: dansimp
-ms.assetid: 2ac86625-15a8-471a-846b-a42eae37ed72
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Administrators Results Pane Columns
-
-
-The **Administrators Results** pane in the Application Virtualization Server Management Console displays two columns that are described in the following table.
-
-
-
-
-
-
-
-
-
Column
-
Contents
-
-
-
-
-
Domain
-
Displays the name of the domain.
-
-
-
Group
-
Displays the name of the administrators group.
-
-
-
-
-
-
-## Related topics
-
-
-[How to Perform Administrative Tasks in the Application Virtualization Server Management Console](how-to-perform-administrative-tasks-in-the-application-virtualization-server-management-console.md)
-
-[Server Management Console: Administrators Node](server-management-console-administrators-node.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/administrators-results-pane.md b/mdop/appv-v4/administrators-results-pane.md
deleted file mode 100644
index 88516a4348..0000000000
--- a/mdop/appv-v4/administrators-results-pane.md
+++ /dev/null
@@ -1,36 +0,0 @@
----
-title: Administrators Results Pane
-description: Administrators Results Pane
-author: dansimp
-ms.assetid: 92f4f924-c73b-45d6-8905-26f0f30aa189
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Administrators Results Pane
-
-
-The **Administrators Results** pane in the Application Virtualization Server Management Console displays a list of the available administrator groups.
-
-## Related topics
-
-
-[How to Perform Administrative Tasks in the Application Virtualization Server Management Console](how-to-perform-administrative-tasks-in-the-application-virtualization-server-management-console.md)
-
-[Server Management Console: Administrators Node](server-management-console-administrators-node.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/antivirus-running-dialog-box--app-v-46-sp1-.md b/mdop/appv-v4/antivirus-running-dialog-box--app-v-46-sp1-.md
deleted file mode 100644
index 4eec31af83..0000000000
--- a/mdop/appv-v4/antivirus-running-dialog-box--app-v-46-sp1-.md
+++ /dev/null
@@ -1,43 +0,0 @@
----
-title: Antivirus Running Dialog Box (App-V 4.6 SP1)
-description: Antivirus Running Dialog Box (App-V 4.6 SP1)
-author: dansimp
-ms.assetid: b720e308-8597-4470-a03e-fc36ffef84aa
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Antivirus Running Dialog Box (App-V 4.6 SP1)
-
-
-Antivirus software is running on the computer running the App-V Sequencer. Running antivirus software during the creation of a virtual application package can interfere with the process by accessing required files that must to be added to the virtual application package or by adding extraneous data to the virtual application package.
-
-Use the following procedure to stop the antivirus software from running during sequencing:
-
-- On the computer running the App-V Sequencer, you must scan the computer and then stop the antivirus software from running.
-
- **Important**
- Remember to restart the antivirus software when you have finished sequencing the application.
-
-
-
-## Related topics
-
-
-[Dialog Boxes (AppV 4.6 SP1)](dialog-boxes--appv-46-sp1-.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/app-v-45-sp2-release-notes.md b/mdop/appv-v4/app-v-45-sp2-release-notes.md
deleted file mode 100644
index ab0e856ca4..0000000000
--- a/mdop/appv-v4/app-v-45-sp2-release-notes.md
+++ /dev/null
@@ -1,222 +0,0 @@
----
-title: App-V 4.5 SP2 Release Notes
-description: App-V 4.5 SP2 Release Notes
-author: dansimp
-ms.assetid: 1b3a8a83-4523-4634-9f75-29bc22ca5815
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 08/30/2016
----
-
-
-# App-V 4.5 SP2 Release Notes
-
-
-To search these Release Notes, press CTRL+F.
-
-**Important**
-Read these Release Notes thoroughly before you install the Microsoft Application Virtualization Management System. These Release Notes contain information that you need to successfully install the Application Virtualization Management System. These Release Notes contain information that is not available in the product documentation. If there is a discrepancy between these Release Notes and other Application Virtualization Management System documentation, the latest change should be considered authoritative.
-
-
-
-For updated information about known issues, please visit the Microsoft TechNet Library at [App-V 4.5 SP2 Release Notes](https://go.microsoft.com/fwlink/?LinkId=184640) (https://go.microsoft.com/fwlink/?LinkId=184640).
-
-## About Microsoft Application Virtualization 4.5 Service Pack 2
-
-
-These Release Notes have been updated to reflect the changes introduced with Microsoft Application Virtualization (App-V) 4.5 Service Pack 2 (SP2). This service pack contains the following changes:
-
-- Support for Office 2010: App-V 4.5 SP2 now supports the virtualization of Microsoft Office 2010. For prescriptive guidance for sequencing Microsoft Office 2010 with App-V 4.5 SP2, see [Prescriptive guidance for sequencing Office 2010 in Microsoft App-V 4.6](https://go.microsoft.com/fwlink/?LinkId=191539) (https://go.microsoft.com/fwlink/?LinkId=191539).
-
-- Support for Database Mirroring: App-V 4.5 SP2 now supports Microsoft SQL Server Database Mirroring. For more information about configuring database mirroring in your App-V environment, see [How to Configure Microsoft SQL Server Mirroring Support for App-V](https://go.microsoft.com/fwlink/?LinkId=190880) (https://go.microsoft.com/fwlink/?LinkId=190880).
-
-- Customer Feedback and Hotfix Rollup: App-V 4.5 SP2 also includes a rollup of fixes to address issues found after the App-V 4.5 SP1 release. The updates address a combination of known issues and customer feedback from Microsoft internal teams, partners, and customers who are using App-V 4.5. For a full list of the updates, see article 980847 in the Microsoft Knowledge Base (KB) at [Description of Microsoft Application Virtualization 4.5 Service Pack 2](https://go.microsoft.com/fwlink/?LinkId=191540) (https://go.microsoft.com/fwlink/?LinkId=191540).
-
-## About the Product Documentation
-
-
-Comprehensive documentation for Application Virtualization (App-V) is available on Microsoft TechNet in the [Application Virtualization TechCenter Library](https://go.microsoft.com/fwlink/?LinkId=122939) (https://go.microsoft.com/fwlink/?LinkId=122939). The TechNet documentation includes the online Help for the Application Virtualization Sequencer, the Application Virtualization Clients, and the Application Virtualization Server. It also includes the Application Virtualization Planning and Deployment Guide and the Application Virtualization Operations Guide.
-
-## Protect Against Security Vulnerabilities and Viruses
-
-
-To help protect against security vulnerabilities and viruses, we recommend that you install the latest available security updates for any new software being installed. For more information, see [Microsoft Security](https://go.microsoft.com/fwlink/?LinkId=3482) (https://go.microsoft.com/fwlink/?LinkId=3482).
-
-## Provide Feedback
-
-
-You can provide feedback, make a suggestion, or report an issue with the Microsoft Application Virtualization (App-V) Management System through the community forum on the Application Virtualization TechCenter [App-V Documentation Forum](https://go.microsoft.com/fwlink/?LinkId=122917) (https://go.microsoft.com/fwlink/?LinkId=122917).
-
-You can also send your documentation feedback directly to the App-V documentation team at .
-
-## Known Issues with Application Virtualization 4.5 SP2
-
-
-This section provides the most up-to-date information about issues with Microsoft Application Virtualization (App-V) 4.5 SP2. These issues do not appear in the product documentation and in some cases might contradict existing product documentation. Whenever possible, these issues will be addressed in later releases of the software.
-
-### Guidance for installing Server Management Console
-
-If you have to install management software on systems other than the primary Application Virtualization publishing and streaming server, the server installation supports installing the Application Virtualization Management Console and Application Virtualization Management Web service on separate servers from the primary App-V Management Server. To distribute the management components across multiple servers, Kerberos delegation must be enabled on the server where the Application Virtualization Web service is installed. For information about how to enable this support, see [How to Configure the Server to be Trusted for Delegation](https://go.microsoft.com/fwlink/?LinkId=166682) (https://go.microsoft.com/fwlink/?LinkId=166682).
-
-### Guidance for installing or upgrading clients to App-V 4.5 SP2 by using Setup.msi
-
-When installing or upgrading your App-V Clients to App-V 4.5 SP2 by using Setup.msi, the prerequisites are not installed automatically.
-
-WORKAROUND You must manually install the prerequisites before installing or upgrading the App-V Clients to App-V 4.5 SP2. For detailed procedures about how to install the prerequisites and the App-V Client, see [How to Install the Client by Using the Command Line](https://go.microsoft.com/fwlink/?LinkId=144106) (https://go.microsoft.com/fwlink/?LinkId=144106).
-
-When this has been completed, install the App-V 4.5 SP2 Clients by using Setup.msi with administrative credentials. This file is available on the App-V 4.5 SP2 release media in the Installers\\Client folder.
-
-When installing Microsoft Application Error Reporting, use the following command if you are installing or upgrading to the App-V 4.5 SP2 Desktop Client:
-
-**msiexec /i dw20shared.msi APPGUID={C6FC75B9-7D86-4C44-8BDB-EAFE1F0E200D} allusers=1 reboot=suppress REINSTALL=all REINSTALLMODE=vomus**
-
-Alternatively, if you are installing or upgrading to the App-V 4.5 SP2 Client for Remote Desktop Services (formerly Terminal Services), use the following command:
-
-**msiexec /i dw20shared.msi APPGUID={ECF80BBA-CA07-4A74-9ED6-E064F38AF1F5} allusers=1 reboot=suppress REINSTALL=all REINSTALLMODE=vomus**
-
-**Note**
-- The APPGUID parameter references the product code of the App-V Clients that you install or upgrade. The product code is unique for each Setup.msi. You can use the Orca Database Editor or a similar tool to examine Windows Installer files and determine the product code. This step is required for all installations or upgrades to App-V 4.5 SP2.
-
-- This step is not required if you are upgrading and have previously installed Dw20shared.msi.
-
-
-
-### Improving performance when sequencing the .NET Framework
-
-When sequencing the Microsoft .NET Framework, you might experience reduced system performance because the .NET Framework NGEN service attempts to precompile assemblies as a background task.
-
-WORKAROUND When sequencing the .NET Framework, disable the .NET Framework NGEN service (Mscorsvw.exe) after completing the monitoring phase. You must use the **Virtual Services** tab in the App-V Sequencer and change the startup type to **Disabled**.
-
-### When you uninstall the Microsoft Application Virtualization Client, user settings associated with the user performing the uninstallation are deleted
-
-When you uninstall the App-V Client, the Windows Installer removes Application Virtualization settings from the current user's profile. If your computer uses roaming profiles, do not use your personal network account to uninstall the client because it will remove settings for your virtual applications on all of your computers.
-
-WORKAROUND You must uninstall the App-V Client with an administrative account that is not used for running virtual applications.
-
-### Edits made on the virtual file system and virtual registry tabs must be saved while running the Sequencing wizard
-
-If you open a package to perform an upgrade, or if you have already run the Sequencing wizard with a new package and make changes to the package in the virtual file system or virtual registry tabs, those changes are not automatically saved.
-
-WORKAROUND Save the changes before re-running the wizard, to ensure that they are reflected inside the wizard’s virtual environment.
-
-### Command-line Sequencer must be run from an elevated command prompt
-
-When you use the command-line Sequencer, it does not prompt for elevation.
-
-WORKAROUND Run the command-line Sequencer by using an elevated command prompt.
-
-### Short path variable names in OSD files can cause errors
-
-If you receive error 450478-1F702339-0000010B "The directory name is invalid" when starting a virtual application on the client, it is possible that the variable in the OSD is set incorrectly. This can happen if the application’s installer sets a short path name during sequencing.
-
-WORKAROUND Remove the trailing tilde from any CSIDL variable that exists in the OSD file.
-
-### Correct syntax for DECODEPATH parameter for command-line Sequencer
-
-In the command-line Sequencer, when opening a package for upgrade and decoding it to the root of drive Q, the syntax for the *DECODEPATH* parameter should not include a trailing slash.
-
-WORKAROUND You can use **Q:** rather than **Q:\\** (omitting the trailing "\\" character).
-
-### When upgrading APP-V 4.2 packages, you encounter problems caused by Windows Installer files in the Virtual File System
-
-When upgrading a package from APP-V 4.2, you might experience issues relating to a mismatch of Windows Installer system files that were included by default in APP-V 4.2 and the Windows Installer libraries locally installed on your Sequencing workstation. The following files are located in CSIDL\_SYSTEM\\:
-
-Cabinet.dll
-
-Msi.dll
-
-Msiexec.exe
-
-Msihnd.dll
-
-Msimsg.dlll
-
-WORKAROUND Delete all of the preceding files from the package. Delete the mappings on the **VFS** tab and the actual files in the CSIDL\_SYSTEM folder in your decode path.
-
-### On Windows XP, by default, client installation logging is not enabled
-
-When installing the client, to ensure that any install errors are captured for troubleshooting, you must enable logging by using the command line.
-
-WORKAROUND Add the parameter */l\*vx! log.txt* to the command line, as shown in the following example:
-
-**setup.exe /s /v”/qn /l\*vx! log.txt”**
-
-**msiexec.exe /i setup.msi /qn /l\*vx! log.txt**
-
-Alternatively, you can set the registry key to the following value:
-
-**\[HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Policies\\Microsoft\\Windows\\Installer\] "Logging"="voicewarmupx!"**
-
-### For Kerberos authentication to work, Service Principal Names (SPNs) must be registered for IIS
-
-When using Internet Information Services (IIS) 6.0 or IIS 7.0 for icon or OSD file retrieval and streaming of packages, to enable Kerberos authentication, the SPNs must be registered as follows:
-
-- On the IIS server, run the following commands by using the SETSPN.EXE Resource Kit tool. The server fully qualified domain name (FQDN) must be used.
-
- **Setspn -r SOFTGRID/<Server FQDN>**
-
- **Setspn -r HTTP/<Server FQDN>**
-
-For more information, see [Integrated Windows Authentication (IIS 6.0)](https://go.microsoft.com/fwlink/?LinkId=131407) (https://go.microsoft.com/fwlink/?LinkId=131407).
-
-### .NET compatibility changes
-
-Microsoft Application Virtualization (App-V) Cumulative Update 1 or later supports sequencing the .NET Framework on Windows XP SP2 or later. Sequencing routines for .NET applications that were written for SoftGrid 4.2 might have to be updated when used with the App-V 4.5 Sequencer. For details and workarounds, see the Application Virtualization TechCenter article at [Support for .NET in Microsoft Application Virtualization 4.5](https://go.microsoft.com/fwlink/?LinkId=123412) (https://go.microsoft.com/fwlink/?LinkId=123412).
-
-### After client upgrade from App-V 4.2, some applications are not shown
-
-Check for the following error in the log: "The Application Virtualization Client could not parse the OSD file". The App-V 4.5 Client filters out applications that have an OSD file that contains an empty OS tag (<OS></OS>).
-
-WORKAROUND Delete the empty OS tag from the OSD file.
-
-### The App-V server requires exemptions in its firewall for certain processes
-
-For the server to stream applications correctly, the server's core processes, including the dispatcher, require access through the firewall.
-
-WORKAROUND Set exemptions in the server's firewall for the following processes: Sghwsvr.exe and Sghwdsptr.exe. This applies to the App-V Management Server and App-V Streaming Server.
-
-### When the server installer is run in silent mode, it does not correctly check for MSXML6
-
-The App-V Management Server depends on MSXML6. However, if you run the installer in silent mode—for example, by using the command **msiexec -i setup.msi /qn** on a system where MSXML6 is not already installed—the installer does not detect the missing dependency and installs anyway. Therefore, when clients attempt to refresh publishing information from the App-V Management Server, they will get errors.
-
-WORKAROUND Verify that MSXML6 is installed on the system before attempting a silent installation of the App-V Management Server.
-
-### Error code 000C800 when attempting to connect to the Application Virtualization Management Console
-
-An Application Virtualization administrator who is not a local administrator on the App-V Management Web Service server receives an error (Error code: 000C800) when attempting to connect to the App-V Management Console, and the Sftmmc.log entry indicates that access to SftMgmt.udl is denied. To successfully connect to the App-V Management Console, an administrator who does not have local administrator rights on the App-V Management Web Service server must have at least Read and Execute permissions to the SftMgmt.udl file.
-
-Application Virtualization administrators must have Read and Execute permissions to the SftMgmt.UDL file in folder %systemdrive%\\Program Files\\Microsoft System Center App Virt Management Server\\App Virt Management Service.
-
-### Client installer command-line parameters are ignored when used in conjunction with KEEPCURRENTSETTINGS=1
-
-When used in conjunction with KEEPCURRENTSETTINGS=1, the following client installer command-line parameters are ignored: SWICACHESIZE, MINFREESPACEMB, ALLOWINDEPENDENTFILESTREAMING, APPLICATIONSOURCEROOT, ICONSOURCEROOT, OSDSOURCEROOT, SYSTEMEVENTLOGLEVEL, SWIGLOBALDATA, DOTIMEOUTMINUTES, SWIFSDRIVE, AUTOLOADTARGET, AUTOLOADTRIGGERS, SWIUSERDATA, and REQUIRESECURECONNECTION.
-
-WORKAROUND If you have settings you want to retain, use KEEPCURRENTSETTINGS=1, and then set the other parameters after deployment. The App-V ADM Template can be used to set the following client settings: APPLICATIONSOURCEROOT, ICONSOURCEROOT, OSDSOURCEROOT, AUTOLOADTARGET, AUTOLOADTRIGGERS, DOTIMEOUTMINUTES, and ALLOWINDEPENDENTFILESTREAMING. You can download the ADM Template from the Microsoft DownLoad Center at [Microsoft Application Virtualization Administrative Template (ADM Template)](https://go.microsoft.com/fwlink/?LinkId=121835) (https://go.microsoft.com/fwlink/?LinkId=121835).
-
-### Release Notes Copyright Information
-
-This document is provided "as-is". Information and views expressed in this document, including URL and other Internet Web site references, may change without notice. You bear the risk of using it.
-
-Some examples depicted herein are provided for illustration only and are fictitious. No real association or connection is intended or should be inferred.
-
-This document does not provide you with any legal rights to any intellectual property in any Microsoft product. You may copy and use this document for your internal, reference purposes. You may modify this document for your internal, reference purposes.
-
-
-
-Microsoft, Active Directory, ActiveSync, MS-DOS, Windows, Windows Server, and Windows Vista are trademarks of the Microsoft group of companies.
-
-All other trademarks are property of their respective owners.
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/app-v-46-release-notes.md b/mdop/appv-v4/app-v-46-release-notes.md
deleted file mode 100644
index 08a8ca5d64..0000000000
--- a/mdop/appv-v4/app-v-46-release-notes.md
+++ /dev/null
@@ -1,69 +0,0 @@
----
-title: App-V 4.6 Release Notes
-description: App-V 4.6 Release Notes
-author: dansimp
-ms.assetid: a3eba129-edac-48bf-a933-3bf43a9873e5
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 08/30/2016
----
-
-
-# App-V 4.6 Release Notes
-
-
-To search these Release Notes, press CTRL+F.
-
-**Important**
-Read these Release Notes thoroughly before you install the Microsoft Application Virtualization (App-V) Management System. These Release Notes contain information that you need to successfully install Application Virtualization (App-V) 4.6. This document contains information that is not available in the product documentation. If there is a discrepancy between these Release Notes and other App-V documentation, the latest change should be considered authoritative.
-
-
-
-## Protect Against Security Vulnerabilities and Viruses
-
-
-To help protect against security vulnerabilities and viruses, it is important to install the latest available security updates for any new software being installed. For more information, see the [Microsoft Security Web site](https://go.microsoft.com/fwlink/?LinkId=3482) (https://go.microsoft.com/fwlink/?LinkId=3482).
-
-## Known Issues with Application Virtualization 4.6
-
-
-This section provides the most up-to-date information about issues with Microsoft Application Virtualization (App-V) 4.6. These issues do not appear in the product documentation and in some cases might contradict existing product documentation. Whenever possible, these issues will be addressed in later releases.
-
-### Load/install error running a Windows Installer file generated by the App-V 4.5 Sequencer
-
-Running a Windows Installer file generated by the App-V 4.5 Sequencer produces a load/install error when trying to run it on an App-V 4.6 client. You will see the following message: "This package requires Microsoft Application Virtualization Client 4.5 or later". Please use the following workaround.
-
-WORKAROUND Open the old package with either the App-V 4.5 SP1 Sequencer or the App-V 4.6 Sequencer and generate a new .msi file for the package.
-
-**Note**
-Alternatively, at the command prompt, the App-V Sequencer can generate the new .msi file by using the */OPEN* and */MSI* parameters, for example, `SFTSequencer /Open:”package.sprj” /MSI`. For more information, see [How to Upgrade a Virtual Application by Using the Command Line](how-to-upgrade-a-virtual-application-by-using-the-command-line.md).
-
-
-
-### Release Notes Copyright Information
-
-This document is provided “as-is”. Information and views expressed in this document, including URL and other Internet Web site references, may change without notice. You bear the risk of using it.
-
-Some examples depicted herein are provided for illustration only and are fictitious. No real association or connection is intended or should be inferred.
-
-This document does not provide you with any legal rights to any intellectual property in any Microsoft product. You may copy and use this document for your internal, reference purposes. You may modify this document for your internal, reference purposes.
-
-
-
-Microsoft, Active Directory, ActiveSync, ActiveX, Excel, SQL Server, Windows, Windows PowerShell, Windows Server, and Windows Vista are trademarks of the Microsoft group of companies.
-
-All other trademarks are property of their respective owners.
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/app-v-46-sp1-release-notes.md b/mdop/appv-v4/app-v-46-sp1-release-notes.md
deleted file mode 100644
index dd7fa73a1b..0000000000
--- a/mdop/appv-v4/app-v-46-sp1-release-notes.md
+++ /dev/null
@@ -1,108 +0,0 @@
----
-title: App-V 4.6 SP1 Release Notes
-description: App-V 4.6 SP1 Release Notes
-author: dansimp
-ms.assetid: aeb6784a-864a-4f4e-976b-40c34dcfd8d6
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 08/30/2016
----
-
-
-# App-V 4.6 SP1 Release Notes
-
-
-To search these Release Notes, press CTRL+F.
-
-**Important**
-Read these Release Notes thoroughly before you install the Microsoft Application Virtualization (App-V) Management System. These Release Notes contain information that helps you successfully install Application Virtualization (App-V) 4.6 SP1. This document contains information that is not available in the product documentation. If there is a difference between these Release Notes and other App-V documentation, the latest change should be considered authoritative.
-
-
-
-## Protect Against Security Vulnerabilities and Viruses
-
-
-To help protect against security vulnerabilities and viruses, it is important to install the latest available security updates for any new software being installed. For more information, see the [Microsoft Security website](https://go.microsoft.com/fwlink/?LinkId=3482) (https://go.microsoft.com/fwlink/?LinkId=3482).
-
-## Known Issues with Application Virtualization 4.6 SP1
-
-
-This section provides the most up-to-date information about issues with Microsoft Application Virtualization (App-V) 4.6 SP1. These issues do not appear in the product documentation and in some cases might contradict existing product documentation. When it is possible, these issues will be addressed in later releases.
-
-### Path from SPRT is lost if it does not end in forward slash ( / )
-
-When the path in an HREF in a project template does not end with a forward slash (**/**), the generated HREF does not include the path. This occurs when the user manually manipulates the **.sprt** file. If you use the sequencer it always adds the forward slash (**/**) after the path.
-
-WORKAROUND Make sure that the HREF has a trailing forward slash (**/**).
-
-### User folder name do not correspond to the package name
-
-Folders that contain user and global .pkg files no longer include the package name. Previously, the App-V client used to use the package root folder 8.3 short name as part of the folder name. This lets you easily identify it. When you use the App-V 4.6 SP1 sequencer, the package root folder 8.3 short names are now random strings. This makes it difficult to identify the folders that contain the package’s **.pkg** files on the computer that is running the App-V client.
-
-WORKAROUND Use one of the following methods to more easily identify these package folders:
-
-1. When you create the package by using the Sequencer, specify a folder name that follows the 8.3 naming convention for the primary application folder. This name will then be used as part of the user folder name as was the case in App-V 4.6.
-
-2. The .sprj file now contains a tag that displays the string that is used as the beginning of the user folder name. You can use the **SHORTNAME** element of the **PACKAGEROOTFOLDER** element to determine the name.
-
-### Running App-V 4.6 SP1 on computers that have more than 64 processors
-
-When you run App-V 4.6 SP1 on computers that have more than 64 processors installed, the App-V client fails.
-
-WORKAROUND None. This configuration is not supported. You must run App-V 4.6 SP1on computers that have fewer than 64 processors.
-
-### Application Virtualization 4.6 SP1 update is not offered on all locales that use Microsoft Update
-
-When you use Microsoft Update, the update for App-V 4.6 SP1 is not available for the following language locales:
-
-- Kazakh
-
-- Hindi
-
-- Serbian-Cyrillic
-
-WORKAROUND If you are using Microsoft Windows Server Update Services (WSUS) use the English version of the update or download the update from the Microsoft Update Catalog.
-
-### After expanding the parent package, you cannot sequence a plug-in with side by side components
-
-When you expand a parent package by using **Tools** / **Expand Package to Local System** in the App-V Sequencer console and you sequence a plug-in with side by side components, an installation error is returned. For example:
-
-- **HRESULT 0x80073712**
-
-This is caused when the sequencer writes the side-by-side component to the registry but does not clear the value for the following registry key:
-
-HKEY\_LOCAL\_MACHINE\\COMPONENTS\\StoreDirty
-
-WORKAROUND After expanding the parent package on the computer that is running the sequencer, you have to delete the value for the following registry key:
-
-HKEY\_LOCAL\_MACHINE\\COMPONENTS\\StoreDirty
-
-After you have deleted the value, sequence the plug-in.
-
-### Release Notes Copyright Information
-
-This document is provided “as-is”. Information and views expressed in this document, such as URL and other Internet website references, may change without notice. You bear the risk of using it.
-
-Some examples depicted herein are provided for illustration only and are fictitious. No real association or connection is intended or should be inferred.
-
-This document does not provide you with any legal rights to any intellectual property in any Microsoft product. You may copy and use this document for your internal, reference purposes. You may modify this document for your internal, reference purposes.
-
-
-
-Microsoft, Active Directory, ActiveSync, ActiveX, Excel, SQL Server, Windows, Windows PowerShell, Windows Server, and Windows Vista are trademarks of the Microsoft group of companies.
-
-All other trademarks are property of their respective owners.
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/app-v-46-sp2-release-notes.md b/mdop/appv-v4/app-v-46-sp2-release-notes.md
deleted file mode 100644
index 227967a34a..0000000000
--- a/mdop/appv-v4/app-v-46-sp2-release-notes.md
+++ /dev/null
@@ -1,114 +0,0 @@
----
-title: App-V 4.6 SP2 Release Notes
-description: App-V 4.6 SP2 Release Notes
-author: dansimp
-ms.assetid: abb536f0-e187-4c5b-952a-f837abd10ad2
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 08/30/2016
----
-
-
-# App-V 4.6 SP2 Release Notes
-
-
-**To search these release notes, press CTRL+F.**
-
-Read these release notes thoroughly before you install Microsoft Application Virtualization (App-V) 4.6 SP2.
-
-These release notes contain information that is required to successfully install Application Virtualization 4.6 SP2. The release notes also contain information that is not available in the product documentation. If there is a difference between these release notes and other App-V 4.6 SP2 documentation, the latest change should be considered authoritative. These release notes supersede the content that is included with this product.
-
-## About the Product Documentation
-
-
-For more information about documentation for App-V, see the [Application Virtualization](https://go.microsoft.com/fwlink/?LinkID=232982) page on Microsoft TechNet.
-
-## Providing feedback
-
-
-We are interested in your feedback on App-V 4.6 SP2. You can send your feedback to .
-
-**Note**
-This email address is not a support channel, but your feedback will help us to plan future changes for our documentation and product releases.
-
-
-
-For the latest information about MDOP and additional learning resources, see the [MDOP Information Experience](https://go.microsoft.com/fwlink/p/?LinkId=236032) page.
-
-For more information about new updates or to provide feedback, follow us on [Facebook](https://go.microsoft.com/fwlink/p/?LinkId=242445) or [Twitter](https://go.microsoft.com/fwlink/p/?LinkId=242447).
-
-## Known Issues with App-V 4.6 SP2
-
-
-### Short file name support is disabled for non-system physical drives when you sequence
-
-When you sequence on Windows 8 or Windows Server 2012, support for short file names (8.3) is disabled by default for non-system physical drives.
-
-The underlying physical drive associated with the primary virtual application directory (for example, “Q:\\appname”) on the sequencing station must provide short file name (8.3) support in order for the App-V 4.6 SP2 Sequencer to generate short file names when creating virtual application packages. Short file name (8.3) support is disabled by default for non-system physical drives on Windows 8 or Windows Server 2012.
-
-**Workaround:** Enable short file name (8.3) support on non-system physical drives. You can use the following command to enable short file name support on Windows 8 or Windows Server 2012.
-
-``` syntax
-fsutil 8dot3name set :
-```
-
-For example, use the following command if the drive letter is “Q:”:
-
-``` syntax
-fsutil 8dot3name set Q: 0
-```
-
-**Note**
-You do not need to change this setting on the App-V client because the App-V file system properly handles short paths on Windows 8 or Windows Server 2012.
-
-
-
-### App-V does not override the default handler for file type or protocol associations on Windows 8
-
-If you select a default application by using **Default Programs** in **Control Panel** on Windows 8, App-V will not override the associated file type associations for that application.
-
-**Workaround:** None.
-
-### Virtualized Outlook 2010 is not offered as an option for mailto clickable links on Windows 8
-
-The mailto shell extension does not offer virtualized Outlook 2010 on Windows 8. For example, if you click a mailto: link from virtualized Outlook 2010 that is running on Windows 8, a new email window is not created. This option works correctly on Windows 7 and earlier versions of the Windows operating system.
-
-**Workaround:** None.
-
-### Application Virtualization 4.6 SP2 update is not offered on all locales that use Microsoft Update
-
-When you use Microsoft Update, the update for App-V 4.6 SP2 is not available for the following language locales:
-
-- Kazakh
-
-- Hindi
-
-- Serbian-Cyrillic
-
-**Workaround:** If you are using Microsoft Windows Server Update Services (WSUS), use the English version of the update or download the update from the Microsoft Update Catalog.
-
-## Release Notes Copyright Information
-
-
-Microsoft, Active Directory, ActiveX, Bing, Excel, Silverlight, SQL Server, Windows, Microsoft Intune, and Windows PowerShell are trademarks of the Microsoft group of companies. All other trademarks are property of their respective owners.
-
-
-
-## Related topics
-
-
-[About Microsoft Application Virtualization 4.6 SP2](about-microsoft-application-virtualization-46-sp2.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/app-v-46-sp3-release-notes.md b/mdop/appv-v4/app-v-46-sp3-release-notes.md
deleted file mode 100644
index d62afda16b..0000000000
--- a/mdop/appv-v4/app-v-46-sp3-release-notes.md
+++ /dev/null
@@ -1,52 +0,0 @@
----
-title: App-V 4.6 SP3 Release Notes
-description: App-V 4.6 SP3 Release Notes
-author: dansimp
-ms.assetid: 206fadeb-59cc-47b4-836f-191ab1c27ff8
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 08/30/2016
----
-
-
-# App-V 4.6 SP3 Release Notes
-
-
-To search these Release Notes, press CTRL+F.
-
-Read these Release Notes thoroughly before you install the Microsoft Application Virtualization (App-V) Management System. These Release Notes contain information that helps you successfully install Application Virtualization (App-V) 4.6 SP3. This document contains information that is not available in the product documentation. If there is a difference between these Release Notes and other App-V documentation, the latest change should be considered authoritative. These release notes supersede the content that is included with this product.
-
-## Protect Against Security Vulnerabilities and Viruses
-
-
-To help protect against security vulnerabilities and viruses, it is important to install the latest available security updates for any new software being installed. For more information, see the [Microsoft Security website](https://go.microsoft.com/fwlink/?LinkId=3482) (https://go.microsoft.com/fwlink/?LinkId=3482).
-
-## Known Issues with Application Virtualization 4.6 SP3
-
-
-This section provides the most up-to-date information about issues with Microsoft Application Virtualization (App-V) 4.6 SP3. These issues do not appear in the product documentation and in some cases might contradict existing product documentation. When it is possible, these issues will be addressed in later releases.
-
-### Unable to open hyperlinks using Internet Explorer 11 on Microsoft Windows 8.1 within the Virtual Environment
-
-Attempting to open hyperlinks from within a virtual environment will fail on Windows 8.1 using Internet Explorer 11. This is because Internet Explorer 11 now ships with the Enhanced Protection Mode (EPM) enabled by default and this causes App-V to be unable to access required registry keys, files and communication port objects.
-
-WORKAROUND: Disable EPM in Internet Explorer 11 before opening an App-V package. This will allow you to open Internet Explorer from within the virtual environment.
-
-## Related topics
-
-
-[About Microsoft Application Virtualization 4.6 SP3](about-microsoft-application-virtualization-46-sp3.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/app-v-application-wmi-class.md b/mdop/appv-v4/app-v-application-wmi-class.md
deleted file mode 100644
index 3567a8da0e..0000000000
--- a/mdop/appv-v4/app-v-application-wmi-class.md
+++ /dev/null
@@ -1,126 +0,0 @@
----
-title: App-V Application WMI Class
-description: App-V Application WMI Class
-author: dansimp
-ms.assetid: b79b0d5a-ba57-442f-8bb4-d7154fc056f9
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# App-V Application WMI Class
-
-
-In the Application Virtualization (App-V) Client, the **Application** class is a Windows Management Instrumentation (WMI) class that represents all the virtual applications on the client.
-
-The following syntax is simplified from Managed Object Format (MOF) code. The code includes all the inherited properties.
-
-## Syntax
-
-
-``` syntax
-class Application
-{
- string Name;
- string Version;
- string PackageGUID;
- datetime LastLaunchOnSystem;
- uint32 GlobalRunningCount;
- boolean Loading;
- string OriginalOsdPath;
- string CachedOsdPath;
-};
-```
-
-## Requirements
-
-
-## Properties
-
-
-**Name**
-Data type: **String**
-
-Access type: Read-only
-
-Qualifiers: Key
-
-The display name of the virtual application.
-
-**Version**
-Data type: **String**
-
-Access type: Read-only
-
-Qualifiers: Key
-
-The version of the virtual application.
-
-**PackageGUID**
-Data type: **String**
-
-Access type: Read-only
-
-Qualifiers: None
-
-The GUID of the package that the virtual application is associated with.
-
-**LastLaunchOnSystem**
-Data type: **DateTime**
-
-Access type: Read-only
-
-Qualifiers: None
-
-The last date and time that the virtual application was launched.
-
-**GlobalRunningCount**
-Data type: **UInt32**
-
-Access type: Read-only
-
-Qualifiers: None
-
-A count of the running instances of the virtual application that were started directly.
-
-**Loading**
-Data type: **Boolean**
-
-Access type: Read-only
-
-Qualifiers: None
-
-**true** if the virtual application is being started; otherwise **false**.
-
-**OriginalOsdPath**
-Data type: **String**
-
-Access type: Read-only
-
-Qualifiers: None
-
-The original file path of the OSD file that was registered with the App-V Client.
-
-**CachedOsdPath**
-Data type: **String**
-
-Access type: Read-only
-
-Qualifiers: None
-
-The file path of the OSD file if the App-V Client has cached the OSD file locally.
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/app-v-client-registry-values-sp1.md b/mdop/appv-v4/app-v-client-registry-values-sp1.md
deleted file mode 100644
index 5edc5870e2..0000000000
--- a/mdop/appv-v4/app-v-client-registry-values-sp1.md
+++ /dev/null
@@ -1,826 +0,0 @@
----
-title: App-V Client Registry Values
-description: App-V Client Registry Values
-author: dansimp
-ms.assetid: 46af5209-9762-47b9-afdb-9a2947e013f7
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 08/30/2016
----
-
-
-# App-V Client Registry Values
-
-
-The Microsoft Application Virtualization (App-V) client stores its configuration in the registry. You can gather some useful information about the client if you understand the format of data in the registry. You can also configure many client actions by changing registry entries. This topic lists all the Application Virtualization (App-V) client registry keys and explains their uses.
-
-**Important**
-On a computer running a 64-bit operating system, the keys and values described in the following sections will be under HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Wow6432Node\\Microsoft\\SoftGrid\\4.5\\Client.
-
-
-
-## Configuration Key
-
-
-The following table provides information about the registry values associated with the HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Microsoft\\SoftGrid\\4.5\\Client\\Configuration key.
-
-
-
-
-
-
-
-
-
-
-
Name
-
Type
-
Data (Examples)
-
Description
-
-
-
-
-
ProductName
-
String
-
Microsoft Application Virtualization Desktop Client
-
Do not modify.
-
-
-
Version
-
String
-
4.5.0.xxx
-
Do not modify.
-
-
-
Drivers
-
String
-
Sftfs.sys
-
If this key value is present, it contains the name of the driver that caused a stop error the last time the core was starting. After you have fixed the stop error, you must delete this key value so that sftlist can start.
If you are running an earlier version than App-V 4.6, SP1 and you modify the log file name or location, you must restart the sftlist service for the change to take effect.
-
-
-
-
-
-
-
-
LogMinSeverity
-
DWORD
-
Default=4, Informational
-
Controls which messages are written to the log. The value indicates a threshold of what is logged—everything less than or equal to that value is logged. For example, a value of 0x3 (Warning) indicates that Warnings (0x3), Errors (0x2), and Critical Errors (0x1) are logged.
The log level is configurable from the Application Virtualization (App-V) client console and from the command prompt. At a command prompt, the command sftlist.exe /verboselog will increase the log level to verbose. For more information on command-line details see
Defines the number of backup copies of the log file that are kept when it is reset. The valid range is 0–9999. The default is 4. A value of 0 means no copies will be kept.
-
-
-
LogMaxSize
-
DWORD
-
Default=256
-
Defines the maximum size in megabytes (MB) that the log file can grow before being reset. The default size is 256 MB. When this size is reached, a log reset will be forced on the next write attempt.
-
-
-
SystemEventLogLevel
-
DWORD
-
Default=0x4 (App-V 4.5)
-
Default=0x3 (App-V 4.6)
-
Indicates the logging level at which log messages are written to the NT event log. The value indicates a threshold of what is logged—that is, everything equal to or less than that value is logged. For example, a value of 0x3 (Warning) indicates that Warnings (0x3), Errors (0x2), and Critical Errors (0x1) are logged.
-
Value Range
-
0x0 = None
-
0x1 = Critical
-
0x2 = Error
-
0x3 = Warning
-
0x4 = Information (Default)
-
0x5 = Verbose
-
-
-
AllowIndependentFileStreaming
-
DWORD
-
Default=0
-
Indicates whether streaming from file will be enabled regardless of how the client has been configured with the APPLICATIONSOURCEROOT parameter. If set to FALSE, the transport will not enable streaming from files even if the OSD HREF or the APPLICATIONSOURCEROOT parameter contains a file path.
Enables an administrator or electronic software distribution (ESD) system to ensure application loading is performed according to the topology management scheme. Use this key value to override the OSD CODEBASE for the HREF element (for example, the source location) for an application. Application Source Root supports URLs and Universal Naming Convention (UNC) path formats.
-
The correct format for the URL path is protocol://servername:[port][/path][/], where port and path are optional. If a port is not specified, the default port for the protocol is used. Only the protocol://server:port portion of the OSD URL is replaced.
-
The correct format for the UNC path is \computername\sharefolder[folder][], where folder is optional. The computer name can be a fully qualified domain name (FQDN) or an IP address, and sharefolder can be a drive letter. Only the \computername\sharefolder or drive letter portion of the OSD path is replaced.
Enables an administrator to specify a source location for OSD file retrieval for a sequenced application package during publication. Acceptable formats for the OSDSourceRoot include UNC paths and URLs (http or https).
Enables an administrator to specify a source location for icon file retrieval for a sequenced application package during publication. Acceptable formats for the IconSourceRoot include UNC paths and URLs (http or https).
-
-
-
AutoLoadTriggers
-
DWORD
-
Default=5
-
AutoLoad is a client runtime policy configuration parameter that enables the secondary feature block of a virtualized application to be streamed to the client automatically in the background. The AutoLoad triggers are flags to indicate events that initiate auto-loading of applications. AutoLoad implicitly uses background streaming to enable the application to be fully loaded into cache. The primary feature block will be loaded first, and the remaining feature blocks will be loaded in the background to enable foreground operations, such as user interaction with applications, to take place and provide optimal perceived performance.
-
Bit mask values:
-
(0) Never: No bits are set (value is 0), no auto loading will be performed, because there are no triggers set.
-
(1) OnLaunch: Loading starts when a user starts an application.
-
(2) OnRefresh: Loading starts when the application is published. This occurs whenever the package record is added or updated—for example, when a publishing refresh occurs.
-
(4) OnLogin: Loading starts when a user logs in.
-
(5) OnLaunch and OnLogin: Default.
-
-
-
AutoLoadTarget
-
DWORD
-
Default=1
-
Indicates what will be auto-loaded when any given AutoLoad triggers occur. Bit mask values:
-
(0) None: No auto-loading, regardless of what triggers may be set.
-
(1) PreviouslyUsed (default): If any AutoLoad trigger is enabled, load only the packages where at least one application in the package has been previously used—that is, started or precached.
-
(2) All: If any AutoLoad trigger is enabled, all applications in the package (per package) or all packages (set for client) will be automatically loaded, whether or not they have ever been started.
-
-
-
RequireAuthorizationIfCached
-
DWORD
-
Default=1
-
Indicates that authorization is always required, whether or not an application is already in cache. Possible values:
-
0=False: Always try to connect to the server. If a connection to the server cannot be established, the client still allows the user to launch an application that has previously been loaded into cache.
-
1=True (default): Application always must be authorized at startup. For RTSP streamed applications, the user authorization token is sent to the server for authorization. For file-based applications, file ACLs control whether a user may access the application.
-
Restart the sftlist service for the change to take effect.
-
-
-
UserDataDirectory
-
String
-
%APPDATA%
-
Location where the icon cache and user settings are stored.
-
-
-
GlobalDataDirectory
-
String
-
C:\Users\Public\Documents
-
Directory to use for global App-V data, including caches for OSD files, icon files, shortcut information, and SystemGuard resources such as .ini files.
-
-
-
AllowCrashes
-
DWORD
-
0 or 1
-
Default=0: A value of 0 means that the client tries to catch internal program exceptions so that other user applications can recover and continue when a crash happens. A value of 1 means that the client allows the internal program exceptions to occur so that they can be captured in a debugger.
-
-
-
CoreInternalTimeout
-
DWORD
-
60
-
Time-out in seconds for internal IPC requests between core and front-end. Do not modify.
-
-
-
DefaultSuiteCombineTime
-
DWORD
-
10
-
This value is used to indicate how soon after being started that a program can shut down and not generate any error messages when another application in the same suite is running.
-
-
-
SerializedSuiteLaunchTimeout
-
DWORD
-
Default=60000
-
Defines how long in milliseconds the client will wait as it tries to serialize program starts in the same suite. If the client times out, the program start will continue but it will not be serialized.
-
-
-
ScriptTimeout
-
DWORD
-
300
-
Default time-out in seconds for scripts in OSD file if WAIT=TRUE. You can specify per-script time-outs with TIMEOUT instead of WAIT. A value of 0 means no wait, and 0xFFFFFFFF means wait forever.
-
-
-
LaunchRecordLogPath
-
String
-
-
If, under either HKLM or HKCU, this value contains a valid path to a log file, SFTTray will write to this log when programs start, shut down, fail to launch, and enter or exit disconnected mode.
-
-
-
LaunchRecordMask
-
DWORD
-
0x1A (26) log launch errors and disconnected mode entry and exit activity.
-
0x1F (31) logs everything.
-
0x0 (0) logs nothing.
-
Specifies which of the five events are logged (bitmask values):
-
1 for program starts
-
2 for launch failure errors
-
4 for shutdowns
-
8 for entering disconnected mode
-
16 for exiting disconnected mode to reconnect to a server
-
Add any combination of those numbers to turn on the respective messages. Defaults to 0x1F if not in registry.
-
-
-
LaunchRecordWriteTimeout
-
DWORD
-
Default=3000
-
Specifies in milliseconds how long the tray will wait when trying to write to the launch record log if another process is using it.
-
-
-
ImportSearchPath
-
String
-
d:\files;C:\documents and settings\user1\SFTs
-
A semicolon delimited list of up to five directories to search for portable SFT files before prompting the user to select a directory. Trailing backslash in paths is optional. This value is not present by default and must be set manually.
-
-
-
UserImportPath
-
String
-
D:\SFTs\
-
Valid only under HKCU. The last location the user browsed to while finding a SFT file for package import. Set automatically if the SFT is found successfully. This is used on successive imports when trying to automatically locate SFT files.
-
-
-
-
-
-
-## Shared Key
-
-
-The HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Microsoft\\SoftGrid\\4.5\\Shared key controls values that are shared across App-V components. The following table provides information about the registry values associated with the Shared key.
-
-
-
-
-
-
-
-
-
-
-
Name
-
Type
-
Data (Examples)
-
Description
-
-
-
-
-
DumpPath
-
String
-
Default=C:\
-
Default path to create dump files when generating a minidump on an exception. This defaults to C:\ if not specified. The Client installer sets this key to the <App Virtualization global data directory>\Dumps. The Sequencer installer sets this key to the installation directory.
-
-
-
DumpPathSizeLimit
-
DWORD
-
1000
-
Specifies the maximum total amount of disk space in megabytes that can be used to store minidumps. Default = 1000 MB.
-
-
-
-
-
-
-## Network Key
-
-
-The HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Microsoft\\SoftGrid\\4.5\\Client\\Network key controls a variety of network-related parameters. This key is primarily used by the network transport agent. The following table provides information about the registry values associated with the Network key.
-
-
-
-
-
-
-
-
-
-
-
Name
-
Type
-
Data (Examples)
-
Description
-
-
-
-
-
Online
-
DWORD
-
Default=1
-
Enables or disables offline mode. If set to 0, the client will not communicate with App-V Management Servers or publishing servers. In disconnected operations, the client can start a loaded application even when it is not connected to an App-V Management Server. In offline mode, the client does not attempt to connect to an App-V Management Server or publishing server. You must allow disconnected operations to be able to work offline. Default value is 1 enabled (online), and 0 is disabled (offline).
-
-
-
AllowDisconnectedOperation
-
DWORD
-
Default=1
-
Enables or disables disconnected operation. Default value is 1 enabled, and 0 is disabled. When disconnected operations are enabled, the App-V client can start a loaded application even when it is not connected to an App-V Management Server.
-
-
-
FastConnectTimeout
-
DWORD
-
Default=1000
-
This value specifies the TCP connect time-out in milliseconds to determine when to go into disconnected operations mode. This value can be used to override the default ConnectTimeout of 20 seconds (App-V connect time-out for network transactions) or the system’s TCP time-out of approximately 25 seconds. This brings the client into disconnected operations mode quickly. Applied on the next connect.
-
-
-
LimitDisconnectedOperation
-
DWORD
-
Default=1
-
Applicable only if AllowDisconnectedOperation is 1, enabled. This value determines whether there will be a time limit for how long the client will be allowed to operate in disconnected operations. 1=limited. 0=unlimited.
-
-
-
DOTimeoutMinutes
-
DWORD
-
Default=129,600
-
Indicates how many minutes an application may be used in disconnected operation mode.
-
-
-
-
-
-
The valid values are 1–999,999 in days expressed in minutes (1–1,439,998,560 minutes). The default value is 90 days or 129,600 minutes.
-
-
-
Protocol
-
DWORD
-
Default=8
-
Default protocol to use (TCP vs SSL). Configure in Options Dialog.
-
-
-
ReadTimeout
-
DWORD
-
20
-
Read time-out for network transactions, in seconds. Do not modify.
-
-
-
WriteTimeout
-
DWORD
-
20
-
Write time-out for network transactions, in seconds. Do not modify.
-
-
-
ConnectTimeout
-
DWORD
-
20
-
Connect time-out for network transactions, in seconds. Do not modify.
-
-
-
ReestablishmentRetries
-
DWORD
-
3
-
The number of times to try to reestablish a dropped session.
-
-
-
ReestablishmentInterval
-
DWORD
-
15
-
The number of seconds to wait between tries to reestablish a dropped session.
-
-
-
-
-
-
-## Http Key
-
-
-The HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Microsoft\\SoftGrid\\4.5\\Client\\Network\\Http key controls the parameters that are related to Http streaming. This key is used primarily by the network transport agent. The following table provides information about the registry values that are associated with the Http key.
-
-
-
-
-
-
-
-
-
-
-
Name
-
Type
-
Data (Examples)
-
Description
-
-
-
-
-
LaunchIfNotFound
-
DWORD
-
Default=0
-
Controls the behavior of HTTP streaming when a connection to the HTTP server can be established and the package file no longer exists on the HTTP server. If the value does not exist or if it is not set to 1, the App-V client does not let you launch an application that has previously been loaded into cache.
-
-
-
-
-
1
-
If this value is set to 1, the App-V client lets you launch an application that has previously been loaded into cache.
-
-
-
-
-
-
-## File System Key
-
-
-The values that are contained under the HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Microsoft\\SoftGrid\\4.5\\Client\\AppFS key control the file system parameters for App-V. The following table provides information about the registry values associated with the AppFS key.
-
-
-
-
-
-
-
-
-
-
-
Name
-
Type
-
Data (Examples)
-
Description
-
-
-
-
-
FileSize
-
DWORD
-
4096
-
Maximum size in megabytes of file system cache file. If you change this value in the registry, you must set State to 0 and reboot.
Location of file system cache file. If you change this value in the registry, you must either leave FileSize the same and reboot or set State to 0 and reboot.
-
-
-
DriveLetter
-
String
-
Q:
-
Drive where App-V file system will be mounted, if it is available. This value is set either by the listener or the installer, and it is read by the file system.
-
-
-
State
-
DWORD
-
0x100
-
State of file system. Set to 0 and reboot to completely clear the file system cache.
-
-
-
FileSystemStorage
-
String
-
C:\Profiles\Joe\SG
-
Path for symlinks, set under HKCU. Do not modify (use data directory under Configuration to change).
Specifies the maximum percentage of the file system cache file that can be locked. Do not modify.
-
-
-
UnloadLeastRecentlyUsed
-
DWORD
-
Default=1
-
The file system cache space management feature uses a Least Recently Used (LRU) algorithm and is enabled by default. If the space that is required for a new package would exceed the available free space in the cache, the App-V Client uses this feature to determine which, if any, existing packages it can delete from the cache to make room for the new package. The client deletes the package with the oldest last-accessed date if it is older than the value specified in the MinPkgAge registry value. Values are 0 (disabled) and 1 (default, enabled).
-
-
-
MinPackageAge
-
DWORD
-
1
-
To determine when the package can be selected for discard, set this registry value to equal the minimum number of days you want to elapse since the package was last accessed. Packages that have been used more recently are not discarded.
-
-
-
-
-
-
-## Permissions Key
-
-
-To help to prevent users from making mistakes, administrators can use the HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Microsoft\\SoftGrid\\4.5\\Client\\Permissions key to control access to some actions for non-administrative users—for example, to prevent users from accidentally unloading programs. Users with administrative rights can give themselves any of these permissions. On shared systems, such as a Remote Desktop Session Host (RD Session Host) server (formerly Terminal Server) system, be careful when granting additional permissions to users because some of these permissions would enable users to control the applications used by all users on the system. Possible values for these settings are 1 (allow) and 0 (disallow).
-
-The Permissions key settings control all interfaces that enable the named actions. This includes the Options Dialog, SFTTray, and SFTMime. These settings do not affect administrators. The following table provides information about the registry values associated with the Permissions key.
-
-Name
-Type
-Data (Examples)
-Description
-ChangeFSDrive
-
-DWORD
-
-Default=0
-
-A value of 1 allows users to pick a different drive letter to be used as the file system drive.
-
-ChangeCacheSize
-
-DWORD
-
-Default=0
-
-A value of 1 allows users to change the cache size.
-
-ChangeLogSettings
-
-DWORD
-
-Default=0
-
-A value of 1 allows users to modify the log level, change its location, and reset it through the user interface.
-
-AddApp
-
-DWORD
-
-Default=0
-
-A value of 1 allows users to add applications explicitly. This does not affect applications that are added through publishing refresh nor does it prevent users from starting (and thereby implicitly adding) applications that have not already been added. Values are 0 or 1.
-
-LoadApp
-
-DWORD
-
-0
-
-Does not allow a user to load an application. This is the default for RD Session Hosts. If you are a mobile user, you might want to fully load your applications in the cache to use them during disconnected operation or offline mode. To stream applications from the App-V Management Server or the App-V Streaming Server, you must be connected to a server to load applications.
-
-1
-
-Allows a user to load an application. This is the default for Windows desktops.
-
-UnloadApp
-
-DWORD
-
-0
-
-Does not allow a user to unload an application. When you load or unload a package, all the applications in the package are loaded into or removed from cache.
-
-1
-
-Allows a user to unload an application.
-
-LockApp
-
-DWORD
-
-0
-
-Does not allow a user to lock and unlock an application. This is the default for RD Session Hosts. A locked application cannot be removed from the cache to make room for new applications. To remove a locked application from the App-V Desktop or Client for Remote Desktop Services (formerly Terminal Services) cache, you must unlock it.
-
-1
-
-Allows a user to lock and unlock an application. This is the default for Windows Desktops.
-
-ManageTypes
-
-DWORD
-
-0
-
-Does not allow a user to add, edit, or remove file type associations for that User alone. This is the default for RD Session Hosts.
-
-1
-
-Allows a user to add, edit, and remove file type associations for that user only and not globally. This is the default for Windows Desktops.
-
-RefreshServer
-
-DWORD
-
-0
-
-Does not allow a user to trigger a refresh of MIME settings. This is the default for RD Session Hosts.
-
-1
-
-Enables a user to trigger a refresh of MIME settings. This is the default for Windows Desktops.
-
-UpdateOSDFile
-
-DWORD
-
-Default= 0
-
-A value of 1 enables a user to use a modified OSD file.
-
-ImportApp
-
-DWORD
-
-0
-
-Does not allow a user to import applications into cache. The difference between Load and Import is that when a Load is triggered, the client gets the package from the currently configured location contained in the OSD, ASR, or Override URL. When using Import, a location to get the package from must be specified.
-
-1
-
-Allows a user to import applications into cache.
-
-ChangeRefreshSettings
-
-DWORD
-
-Default=0
-
-A value of 1 allows users to modify the refresh settings for servers (refresh on login and periodic refresh). This does not imply that the user can modify other server settings (path, host, and so on).
-
-ManageServers
-
-DWORD
-
-Default=0
-
-A value of 1 allows the user to add, edit, and remove servers, except for editing the refresh settings, which is controlled by the ChangeRefreshSettings permission.
-
-PublishShortcut
-
-DWORD
-
-Default=0
-
-A value of 1 allows users to publish shortcuts through the user interface. This does not affect shortcuts that are published during a publishing refresh.
-
-ViewAllApplications
-
-DWORD
-
-Default=0
-
-A value of 1 displays all applications through the user interface; otherwise, only the user’s applications are displayed.
-
-RepairApp
-
-DWORD
-
-Default=1
-
-A value of 1 allows the user to use the Repair action on applications in SFTMime or the Client Management Console. When you repair an application, you remove any custom user settings and restore the default settings. This action does not change or delete shortcuts or file type associations, and it does not remove the application from cache.
-
-ClearApp
-
-DWORD
-
-Default=1
-
-A value of 1 allows the user to use the Clear action on applications in SFTMime or the Client Management Console. When you clear an application from the console, you can no longer use that application. However, the application remains in cache and is still available to other users on the same system. After a publishing refresh, the cleared applications will again become available to you.
-
-DeleteApp
-
-DWORD
-
-Default=0
-
-A value of 1 allows the user to use the Delete action on applications in SFTMime or the Client Management Console. When you delete an application, the selected application will no longer be available to any users on that client. Shortcuts and file type associations are deleted and the application is deleted from cache. However, if another application refers to data in the file system cache or settings data for the selected application, these items will not be deleted.
-
-After a publishing refresh, the deleted applications will again become available to you.
-
-ToggleOfflineMode
-
-DWORD
-
-A value of 1 allows the users to select to run the client in Offline Mode. In Offline Mode, the Application Virtualization client can start a loaded application even when it is not connected to an Application Virtualization Server.
-
-
-
-## Custom Settings
-
-
-The HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Microsoft\\SoftGrid\\4.5\\Client\\CustomSettings key contains values specific to front-end components. All custom settings are stored as strings. The following table provides information about the registry values associated with the CustomSettings key.
-
-
-
-
-
-
-
-
-
-
-
Name
-
Type
-
Data (Examples)
-
Description
-
-
-
-
-
TrayErrorDelay
-
DWORD
-
Default=30
-
Time in seconds that the Application Virtualization notification area will display error messages like "Launch failed". Minimum value of 1.
-
-
-
TraySuccessDelay
-
DWORD
-
Default=10
-
Time in seconds that the appvmed notification area will display success messages like "Word launched" or "Excel shut down". If 0, those messages will be suppressed.
-
-
-
TrayVisibility
-
DWORD
-
Default=0
-
0=Show Tray when virtualized applications are in use.
-
1=Show Tray always.
-
2=Never show Tray.
-
-
-
TrayShowRefresh
-
DWORD
-
-
When present and set to a value of 1, allows menu item Refresh Applications to be displayed on the Tray menu and is accessible by the user.
-
-
-
TrayShowLoad
-
DWORD
-
-
When present and set to a value of 1, allows menu item Load Applications to be displayed on the Tray menu and is accessible by the user.
-
-
-
-
-
-
-## Reporting Settings
-
-
-The HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Microsoft\\SoftGrid\\4.5\\Client\\Reporting key contains values specific to reporting to an App-V Management Server. The following table provides information about the registry values associated with the Reporting key.
-
-
-
-
-
-
-
-
-
-
-
Name
-
Type
-
Data (Examples)
-
Description
-
-
-
-
-
DataCacheLimit
-
DWORD
-
Default=20
-
This value specifies the maximum size in megabytes (MB) of the XML cache for storing reporting information. The size applies to the cache in memory. When the limit is reached, the log file will roll over. When a new record is added (bottom of the list), one or more of the oldest records (top of the list) will be deleted to make room. A warning will be logged to the Client log and the event log the first time this occurs, and it will not be logged again until after the cache has been successfully cleared on transmission and the log has filled up again.
-
-
-
DataBlockSize
-
DWORD
-
Default=65536
-
This value specifies the maximum size in bytes to transmit to the server at once on publishing refresh, to avoid permanent transmission failures when the log has reached a significant size. The default value is 65536. When transmitting report data to the server, one block of application records—less than or equal to the block size in bytes of XML data—will be removed from the cache and sent to the server. Each block will have the general Client data and global package list data prepended, and these will not factor into the block size calculations; the potential exists for an extremely large package list to result in transmission failures over low bandwidth or unreliable connections.
-
-
-
-
-
-
-## Related topics
-
-
-[Application Virtualization Client Reference](application-virtualization-client-reference.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/app-v-desktop-client-security.md b/mdop/appv-v4/app-v-desktop-client-security.md
deleted file mode 100644
index 2bf8723032..0000000000
--- a/mdop/appv-v4/app-v-desktop-client-security.md
+++ /dev/null
@@ -1,77 +0,0 @@
----
-title: App-V Desktop Client Security
-description: App-V Desktop Client Security
-author: dansimp
-ms.assetid: 216b9c16-7bb4-4f94-b9d8-810501285008
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 08/30/2016
----
-
-
-# App-V Desktop Client Security
-
-
-The App-V Desktop Client provides many security enhancements that were not available in previous versions of the product. These changes provide higher levels of security by default and through configuration of the client settings.
-
-**Note**
-When you install the App-V Desktop Client on a computer, the software defaults to the most secure settings. However, when upgrading, the previous settings of the client persist.
-
-
-
-By default, the App-V Desktop Client is configured only with the permissions required to allow a non-administrative user to perform a publishing refresh and stream applications. Additional security enhancements provided in the App-V Desktop Client include the following:
-
-- By default, an OSD cache update is allowed only by the publishing refresh process.
-
-- The log file (`sftlog.txt`) is accessible only by accounts with local administrative access to the client.
-
-- The log file now has a maximum size.
-
-- The log files are managed through archive settings.
-
-- System Event logging is now performed.
-
-## Permissions
-
-
-After you install the Desktop Client, you can configure other security settings through the MMC, or on an individual client by using the registry or the ADM Template provided by Microsoft. The App-V Desktop Client has permissions that you can set to restrict non-administrative users from accessing all the features of the Desktop Client. For a full list of permissions, please see the App-V Client Help file or App-V Operations Guide.
-
-**Important**
-Carefully consider the consequences of changing access rights, especially on systems that are shared by multiple users, such as Terminal Servers.
-
-
-
-**Note**
-If users in the environment have local administrator privileges for their computers, the permissions are ignored.
-
-
-
-### ADM Template
-
-Microsoft Application Virtualization (App-V) introduces an ADM Template that you can use to configure the most common client settings through Group Policies. This template enables administrators to implement and change many of the client settings through a centralized administration model. Some of the settings available in the ADM Template are security settings.
-
-**Important**
-When using the ADM Template, remember that the settings are Group Policy preference settings and not fully managed Group Policies.
-
-
-
-For a full description of the ADM Template, the specific settings, and guidance to successfully deploy clients in your environment, see the App-V ADM Template white paper at [https://go.microsoft.com/fwlink/LinkId=122063](https://go.microsoft.com/fwlink/?LinkId=122063).
-
-## Removing OSD File Type Associations
-
-
-If your organization does not require users to open applications directly from an OSD file, you can enhance security by removing the file type associations on the client. Remove the `HKEY_CURRENT_USERS` keys for OSD and `Softgird.osd.file` by using the registry editor. You can put this process into a logon script or into a post-installation script to automate these changes.
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/app-v-installation-checklist.md b/mdop/appv-v4/app-v-installation-checklist.md
deleted file mode 100644
index 68208f051d..0000000000
--- a/mdop/appv-v4/app-v-installation-checklist.md
+++ /dev/null
@@ -1,90 +0,0 @@
----
-title: App-V Installation Checklist
-description: App-V Installation Checklist
-author: dansimp
-ms.assetid: b17efaab-cd6d-4c30-beb7-c6e7c9c87657
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# App-V Installation Checklist
-
-
-The following checklist is intended to provide a high-level list of items to consider and outlines the steps you should take to install the Microsoft Application Virtualization (App-V) servers.
-
-
-
-
-
-
-
-
-
Step
-
Reference
-
-
-
-
-
Install the App-V Management Server. If you are installing the Management Web Service, Management Console, or the Data Store on different servers, you can use the custom installation option.
-
-
-
-¹ This is required only if you are installing the App-V Management Web Service, Management Console, or the Data Store on a different computer.
-
-## Related topics
-
-
-[Application Virtualization Deployment and Upgrade Checklists](application-virtualization-deployment-and-upgrade-checklists.md)
-
-[App-V Postinstallation Checklist](app-v-postinstallation-checklist.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/app-v-interoperability-with-windows-applocker.md b/mdop/appv-v4/app-v-interoperability-with-windows-applocker.md
deleted file mode 100644
index b4fc7f6ba0..0000000000
--- a/mdop/appv-v4/app-v-interoperability-with-windows-applocker.md
+++ /dev/null
@@ -1,41 +0,0 @@
----
-title: App-V Interoperability with Windows AppLocker
-description: App-V Interoperability with Windows AppLocker
-author: dansimp
-ms.assetid: 9a488034-607d-411c-b495-ff184c726f49
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 08/30/2016
----
-
-
-# App-V Interoperability with Windows AppLocker
-
-
-Version 4.5 SP1 of the Microsoft Application Virtualization (App-V) client supports the AppLocker feature of Windows 7. The AppLocker feature enables IT administrators to specify which applications are restricted from running on computers. This document describes how to configure the AppLocker rules to work with the App-V virtual environment and virtualized applications.
-
-**Note**
-Windows AppLocker must first be enabled before configuring Windows AppLocker rules for virtual applications. For more information about enabling Windows AppLocker, [Windows AppLocker](https://go.microsoft.com/fwlink/?LinkId=156732) (https://go.microsoft.com/fwlink/?LinkId=156732).
-
-
-
-## Configuring Windows AppLocker Rules for Virtual Applications
-
-
-Local administrators can create Windows AppLocker rules that restrict the running of program executables (.exe files), Windows Installer files (.msi and .msp files), and scripts (.ps, .bat, .cmd, .vbs and .js files). The administrator does this by using a reference computer that has the App-V client installed and that has all the relevant virtual applications streamed to the client cache. The administrator then uses the Windows AppLocker section of the Local Security Policy Microsoft Management Console (MMC) snap-in on the reference computer to create the rules.
-
-When you browse to find a directory path or specific file for which you want to create a rule, you can access the App-V drive by using the path to the hidden share. For example, you can browse to \\\\localhost\\Q$, where the App-V drive is drive Q. However, to create the rule, you must edit the path to remove the reference to \\\\localhost\\Q$ and use Q:\\ instead. You must start each application on the reference computer to access the application’s files, and administrative rights are required to browse to \\\\localhost\\Q$.
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/app-v-package-wmi-class.md b/mdop/appv-v4/app-v-package-wmi-class.md
deleted file mode 100644
index f9efeee4ce..0000000000
--- a/mdop/appv-v4/app-v-package-wmi-class.md
+++ /dev/null
@@ -1,161 +0,0 @@
----
-title: App-V Package WMI Class
-description: App-V Package WMI Class
-author: dansimp
-ms.assetid: 0fc26c3b-9706-4804-be2d-645771dc33ae
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# App-V Package WMI Class
-
-
-In the Application Virtualization (App-V) Client, the **Package** class is a Windows Management Instrumentation (WMI) class that represents all the virtual packages on the client. The virtual packages can contain many virtual applications.
-
-## Syntax
-
-
-``` syntax
-class Package
-{
- string Name;
- string Version;
- string PackageGUID;
- string SftPath;
- uint64 TotalSize;
- uint64 CachedSize;
- uint64 LaunchSize;
- uint64 CachedLaunchSize;
- boolean InUse;
- boolean Locked;
- uint16 CachedPercentage;
- string VersionGUID;
- };
-```
-
-## Properties
-
-
-**Name**
-Data type: **String**
-
-Access type: Read-only
-
-Qualifiers: None
-
-The user-friendly name of the virtual package.
-
-**Version**
-Data type: **String**
-
-Access type: Read-only
-
-Qualifiers: None
-
-The version of the virtual package.
-
-**PackageGUID**
-Data type: **String**
-
-Access type: Read-only
-
-Qualifiers: Key
-
-The GUID identifier of the package configuration and source files.
-
-**SftPath**
-Data type: **String**
-
-Access type: Read-only
-
-Qualifiers: None
-
-The file path of the SFT file.
-
-**TotalSize**
-Data type: **UInt64**
-
-Access type: Read-only
-
-Qualifiers: None
-
-The total size of the virtual package, in kilobytes.
-
-**CachedSize**
-Data type: **UInt64**
-
-Access type: Read-only
-
-Qualifiers: None
-
-The total size of the cache for the virtual package, in kilobytes.
-
-**LaunchSize**
-Data type: **UInt64**
-
-Access type: Read-only
-
-Qualifiers: None
-
-The total size of the virtual package’s primary feature block, in kilobytes.
-
-**CachedLaunchSize**
-Data type: **UInt64**
-
-Access type: Read-only
-
-Qualifiers: None
-
-Total size of the virtual package’s primary feature block that has been cached, in kilobytes.
-
-**InUse**
-Data type: **Boolean**
-
-Access type: Read-only
-
-Qualifiers: None
-
-**true** if any virtual application in the virtual package is running; otherwise **false**.
-
-**Locked**
-Data type: **Boolean**
-
-Access type: Read-only
-
-Qualifiers: None
-
-**true** if the virtual package is locked; otherwise **false**.
-
-**CachedPercentage**
-Data type: **UInt16**
-
-Access type: Read-only
-
-Qualifiers: None
-
-The percentage of the cache files. Based on the following formula: CachedSize / TotalSize × 100.
-
-**VersionGUID**
-Data type: **String**
-
-Access type: Read-only
-
-Qualifiers: None
-
-The GUID identifier of the package version.
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/app-v-postinstallation-checklist.md b/mdop/appv-v4/app-v-postinstallation-checklist.md
deleted file mode 100644
index 814811b75f..0000000000
--- a/mdop/appv-v4/app-v-postinstallation-checklist.md
+++ /dev/null
@@ -1,71 +0,0 @@
----
-title: App-V Postinstallation Checklist
-description: App-V Postinstallation Checklist
-author: dansimp
-ms.assetid: 74db297e-a744-4287-bcc6-0e096ca8b57a
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# App-V Postinstallation Checklist
-
-
-The following checklist provides a high-level list of items to consider and outlines the steps you should take after you have completed the installation of the Microsoft Application Virtualization (App-V) Management Server, App-V Streaming Server, and the App-V Desktop Client.
-
-
-
-
-
-
-
-
-
Step
-
Reference
-
-
-
-
-
Create firewall exceptions for the App-V Management Server or Streaming Server services.
Configure the App-V Client to use the App-V Streaming Server or other server for streaming by means of the ApplicationSourceRoot, IconSourceRoot, and OSDSourceRoot settings.
Configure the server that is running IIS to be trusted for delegation.
-
-Note
This is required only if you are installing the App-V Management Server by using a distributed system architecture, that is, if you install the App-V Management Console, the Management Web Service, and the database on different computers.
-
-
-
-## Related topics
-
-
-[Application Virtualization Deployment and Upgrade Checklists](application-virtualization-deployment-and-upgrade-checklists.md)
-
-[App-V Installation Checklist](app-v-installation-checklist.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/app-v-upgrade-checklist.md b/mdop/appv-v4/app-v-upgrade-checklist.md
deleted file mode 100644
index b81818e567..0000000000
--- a/mdop/appv-v4/app-v-upgrade-checklist.md
+++ /dev/null
@@ -1,213 +0,0 @@
----
-title: App-V Upgrade Checklist
-description: App-V Upgrade Checklist
-author: dansimp
-ms.assetid: 64e317d2-d260-4b67-8a49-ba9ac513087a
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 08/30/2016
----
-
-
-# App-V Upgrade Checklist
-
-
-Before trying to upgrade to Microsoft Application Virtualization (App-V) 4.5 or later versions, any version earlier than App-V 4.1 must be upgraded to App-V 4.1. You should plan to upgrade clients first, and then upgrade the server components. App-V clients that have been upgraded to App-V 4.5 continue to work with App-V servers that have not yet been upgraded. Earlier versions of the client are not supported on servers that have been upgraded to App-V 4.5.
-
-
If you have more than one server sharing access to the App-V database, all those servers must be taken offline while the database is being upgraded. You should follow your regular business practices for the database upgrade, but we recommend that you test the database upgrade by using a backup copy of the database first on a test server. Then, you should select one of the servers for the first upgrade, which will upgrade the database schema. After the production database has been successfully upgraded, you can upgrade the App-V software on the other servers.
This step applies only if the Management Web Service is on a separate server, which would require that you run the server installer program on that separate server to upgrade the Management Web service. Otherwise, the previous server upgrade step will automatically upgrade the Management Web Service.
This step applies only if the Management Console is on a separate computer, which would require that you run the server installer program on that separate computer to upgrade the console. Otherwise, the previous server upgrade step will upgrade the Management Console.
-
-
-
-## Additional Upgrade Considerations
-
-
-- Any virtual application packages sequenced in version 4.2 will not have to be sequenced again for use with version 4.5. However, you should consider upgrading the virtual packages to the Microsoft Application Virtualization 4.5 format if you want to apply default access control lists (ACLs) or generate a Windows Installer file. This is a simple process and requires only that the existing virtual application package be opened and saved with the App-V 4.5 Sequencer. This can be automated by using the App-VSequencer command-line interface. For more information, see [How to Create or Upgrade Virtual Applications Using the App-V Sequencer](how-to-create-or-upgrade-virtual-applications-using--the-app-v-sequencer.md)
-
-- One of the features of the 4.5 Sequencer is the ability to create Windows Installer (.msi) files as control points for virtual application package interoperability with electronic software distribution (ESD) systems, such as Microsoft Endpoint Configuration Manager. Previous Windows Installer files created with the MSI tool for Application Virtualization that were installed on a App-V 4.1 or 4.2 client that is subsequently upgraded to App-V 4.5 will continue to work, although they cannot be installed on the App-V 4.5 client. However, they cannot be removed or upgraded unless they are upgraded in the App-V 4.5 Sequencer. The original App-V package earlier than 4.5 has to be opened in the App-V 4.5 Sequencer and then saved as a Windows Installer File.
-
- **Note**
- If the App-V 4.2 Client has already been upgraded to App-V 4.5, it is possible to script a workaround to preserve the version 4.2 packages on version 4.5 clients and allow them to be managed. This script must copy two files, msvcp71.dll and msvcr71.dll, to the App-V installation folder and set the following registry key values under the registry key:\[HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Microsoft\\SoftGrid\\4.5\\Client\\Configuration\]:
-
- "ClientVersion"="4.2.1.20"
-
- "GlobalDataDirectory"="C:\\\\Documents and Settings\\\\All Users\\\\Documents\\\\" (a globally writeable location)
-
-
-
-- Windows Installer files generated by the App-V 4.5 Sequencer display the error message "This package requires Microsoft Application Virtualization Client 4.5 or later" when trying to run them on an App-V 4.6 Client. Open the old package with either the App-V 4.5 SP1 Sequencer or the App-V 4.6 Sequencer and generate a new .msi file for the package.
-
-- Any version 4.2 reports that were created and saved will be overwritten when the server is upgraded to version 4.5. If you have to keep these reports, you must save a backup copy of the SftMMC.msc file located in the SoftGrid Management Console folder on the server and use that copy to replace the new SftMMC.msc that is installed during the upgrade.
-
-- For additional information about upgrading from previous versions, see [Upgrading to Microsoft Application Virtualization 4.5 FAQ](https://go.microsoft.com/fwlink/?LinkId=120358) (https://go.microsoft.com/fwlink/?LinkId=120358).
-
-## App-V 4.6 Client Package Support
-
-
-You can deploy packages created in previous versions of App-V to App-V 4.6 clients. However, you must modify the associated .osd file so that it includes the appropriate operating system and chip architecture information. The following values can be used:
-
-
-
-
-
-
-
-
OS Value
-
-
-
-
-
<OS VALUE=”Win2003TS”/>
-
-
-
<OS VALUE=”Win2003TS64”/>
-
-
-
<OS VALUE=”Win2008TS”/>
-
-
-
<OS VALUE=”Win2008TS64”/>
-
-
-
<OS VALUE=”Win2008R2TS64”/>
-
-
-
<OS VALUE=”Win7”/>
-
-
-
<OS VALUE=”Win764”/>
-
-
-
<OS VALUE=”WinVista”/>
-
-
-
<OS VALUE=”WinVista64”/>
-
-
-
<OS VALUE=”WinXP”/>
-
-
-
<OS VALUE=”WinXP64”/>
-
-
-
-
-
-
-To run a newly created 32-bit package, you must sequence the application on a computer running a 32-bit operating system with the App-V 4.6 Sequencer installed. After you have sequenced the application, in the Sequencer console, click the **Deployment** tab and then specify the appropriate operating system and chip architecture as required.
-
-**Important**
-Applications sequenced on a computer running a 64-bit operating system must be deployed to computers running a 64-bit operating system. New 32-bit packages created by using the App-V 4.6 Sequencer do not run on computers running the App-V 4.5 client.
-
-
-
-To run new 64-bit packages on the App-V 4.6 Client, you must sequence the application on a computer running the App-V 4.6 Sequencer and that is running a 64-bit operating system. After you have sequenced the application, in the Sequencer console, click the **Deployment** tab, and then specify the appropriate operating system and chip architecture as required.
-
-The following table lists which client versions will run packages created by using the various versions of the sequencer.
-
-
-
-
-
-
-
-
-
-
-
-
-
Sequenced by using the App-V 4.2 Sequencer
-
Sequenced by using the App-V 4.5 Sequencer
-
Sequenced by using the 32-bit App-V 4.6 Sequencer
-
Sequenced by using the 64-bit App-V 4.6 Sequencer
-
-
-
-
-
4.2 Client
-
Yes
-
No
-
No
-
No
-
-
-
4.5 Client ¹
-
Yes
-
Yes
-
No
-
No
-
-
-
4.6 Client (32-bit)
-
Yes
-
Yes
-
Yes
-
No
-
-
-
4.6 Client (64-bit)
-
Yes
-
Yes
-
Yes
-
Yes
-
-
-
-
-
-
-¹Applies to all versions of the App-V 4.5 client, including App-V 4.5, App-V 4.5 CU1, and App-V 4.5 SP1.
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/application-utilization-reportserver.md b/mdop/appv-v4/application-utilization-reportserver.md
deleted file mode 100644
index 78ed55aaad..0000000000
--- a/mdop/appv-v4/application-utilization-reportserver.md
+++ /dev/null
@@ -1,60 +0,0 @@
----
-title: Application Utilization Report
-description: Application Utilization Report
-author: dansimp
-ms.assetid: cb961969-c9a3-4d46-8303-121d737d76d8
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Application Utilization Report
-
-
-Use the Application Utilization Report to track usage information for a specified application defined in the database. You can use this report to determine how heavily a specific application is used.
-
-This report generates a graph that displays the total daily usage over time during the reporting period.
-
-This report also lists the following information:
-
-- Number of sessions—Number of times an application was used
-
-The Application Utilization Report also includes a summary of the total usage.
-
-When you create a report, you specify the parameters that are used for collecting the data when the report is run.
-
-Reports are not run automatically; you must run them explicitly to generate output data. The length of time it takes to run a report is determined by the amount of data collected in the data store.
-
-After you run a report and the output is displayed in the Application Virtualization Server Management Console, you can export the report into the following formats:
-
-- Adobe Acrobat (PDF)
-
-- Microsoft Office Excel
-
-## Related topics
-
-
-[How to Create a Report](how-to-create-a-reportserver.md)
-
-[How to Delete a Report](how-to-delete-a-reportserver.md)
-
-[How to Export a Report](how-to-export-a-reportserver.md)
-
-[How to Print a Report](how-to-print-a-reportserver.md)
-
-[How to Run a Report](how-to-run-a-reportserver.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/application-virtualization-client-hardware-and-software-requirements.md b/mdop/appv-v4/application-virtualization-client-hardware-and-software-requirements.md
deleted file mode 100644
index e7bf14bd06..0000000000
--- a/mdop/appv-v4/application-virtualization-client-hardware-and-software-requirements.md
+++ /dev/null
@@ -1,274 +0,0 @@
----
-title: Application Virtualization Client Hardware and Software Requirements
-description: Application Virtualization Client Hardware and Software Requirements
-author: dansimp
-ms.assetid: 8b877a2c-5721-4b22-a47f-e2838d58ab12
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 08/30/2016
----
-
-
-# Application Virtualization Client Hardware and Software Requirements
-
-
-This topic describes the recommended minimum hardware and software configuration for the installation of the Application Virtualization Desktop Client and the Application Virtualization Client for Remote Desktop Services (formerly Terminal Services).
-
-## Application Virtualization Desktop Client
-
-
-The following list includes the recommended minimum hardware and software requirements for the Application Virtualization Desktop Client. The requirements are listed first for Microsoft Application Virtualization (App-V) 4.6 SP2, followed by the requirements for versions that preceded App-V 4.6 SP2.
-
-**Note**
-The Application Virtualization (App-V) Desktop Client requires no additional processor or RAM resources beyond the requirements of the host operating system.
-
-
-
-### Hardware Requirements
-
-The hardware requirements are applicable to all versions.
-
-- Processor—See recommended system requirements for the operating system you are using.
-
-- RAM—See recommended system requirements for the operating system you are using.
-
-- Disk—30 MB for installation and 6 GB for the cache.
-
-### Software Requirements for App-V 4.6 SP2
-
-
-
-
-
-
-
-
-
-
-
Operating System
-
Edition
-
Service Pack
-
Architectural SKU
-
-
-
-
-
Windows XP
-
Professional Edition
-
SP3
-
x86
-
-
-
Windows Vista
-
Business, Enterprise, or Ultimate Edition
-
SP2
-
x86
-
-
-
Windows 7
-
Professional, Enterprise, or Ultimate Edition
-
No service pack or SP1
-
x86 and x64
-
-
-
Windows 8
-
Pro or Enterprise Edition
-
-
x86 and x64
-
-
-
-
-The following software prerequisites are installed automatically if you are using the Setup.exe method. If you are using the Setup.msi installation program, the following products must be installed first.
-- **Microsoft Visual C++ 2005 SP1 Redistributable Package (x86)**—For more information about installing Microsoft Visual C++ 2005 SP1 Redistributable Package (x86), see [Microsoft Visual C++ 2005 SP1 Redistributable Package (x86)](https://go.microsoft.com/fwlink/?LinkId=119961) (https://go.microsoft.com/fwlink/?LinkId=119961). For version 4.5 SP2 of the App-V client, download Vcredist\_x86.exe from [Microsoft Visual C++ 2005 Service Pack 1 Redistributable Package ATL Security Update](https://go.microsoft.com/fwlink/?LinkId=169360) (https://go.microsoft.com/fwlink/?LinkId=169360).
- - **Microsoft Core XML Services (MSXML) 6.0 SP1 (x86)**—For more information about installing Microsoft Core XML Services (MSXML) 6.0 SP1 (x86), see [Microsoft Core XML Services (MSXML) 6.0 SP1 (x86)](https://go.microsoft.com/fwlink/?LinkId=63266) (https://go.microsoft.com/fwlink/?LinkId=63266).
-
-For the Application Virtualization (App-V) 4.6 Desktop Client, the following additional software prerequisite is installed automatically if you are using the Setup.exe method. If you are using the Setup.msi installation program, you must also install with the other prerequisites listed.
-
-- **Microsoft Visual C++ 2008 SP1 Redistributable Package (x86)**—For more information about installing Microsoft Visual C++ 2008 SP1 Redistributable Package (x86), see [Microsoft Visual C++ 2008 SP1 Redistributable Package (x86)](https://go.microsoft.com/fwlink/?LinkId=150700) (https://go.microsoft.com/fwlink/?LinkId=150700).
-
-### Software Requirements for Versions that Precede App-V 4.6 SP2
-
-
-
-
-
-
-
-
-
-
-
Operating System
-
Edition
-
Service Pack
-
Architectural SKU
-
-
-
-
-
Windows XP
-
Professional Edition
-
SP2 or SP3
-
x86 and x64
-
-
-
Windows Vista
-
Business, Enterprise, or Ultimate Edition
-
No service pack, SP1, or SP2
-
x86 and x64
-
-
-
Windows 7¹
-
Professional, Enterprise, or Ultimate Edition
-
No service pack or SP1
-
x86 and x64
-
-
-
-¹Supported for App-V 4.5 SP1 and SP2, App-V 4.6 and 4.6 SP1 only
-
-The Application Virtualization (App-V) 4.6 Desktop Client supports x86 and x64 SKUs of these operating systems.
-
-The following software prerequisites are installed automatically if you are using the Setup.exe method. If you are using the Setup.msi installation program, the following products must be installed first.
-
-- Microsoft Visual C++ 2005 SP1 Redistributable Package (x86)—For more information about installing Microsoft Visual C++ 2005 SP1 Redistributable Package (x86), see Microsoft Visual C++ 2005 SP1 Redistributable Package (x86) (https://go.microsoft.com/fwlink/?LinkId=119961). For version 4.5 SP2 of the App-V client, download Vcredist_x86.exe from Microsoft Visual C++ 2005 Service Pack 1 Redistributable Package ATL Security Update (https://go.microsoft.com/fwlink/?LinkId=169360).
-
-- Microsoft Core XML Services (MSXML) 6.0 SP1 (x86)—For more information about installing Microsoft Core XML Services (MSXML) 6.0 SP1 (x86), see Microsoft Core XML Services (MSXML) 6.0 SP1 (x86) (https://go.microsoft.com/fwlink/?LinkId=63266).
-
-- Microsoft Application Error Reporting—The installation program for this software is included in the Support\Watson folder in the self-extracting archive file.
-
-For the Application Virtualization (App-V) 4.6 Desktop Client, the following additional software prerequisite is installed automatically if you are using the Setup.exe method. If you are using the Setup.msi installation program, you must also install with the other prerequisites listed.
-
-- Microsoft Visual C++ 2008 SP1 Redistributable Package (x86)—For more information about installing Microsoft Visual C++ 2008 SP1 Redistributable Package (x86), see Microsoft Visual C++ 2008 SP1 Redistributable Package (x86) (https://go.microsoft.com/fwlink/?LinkId=150700).
-
-## Application Virtualization Client for Remote Desktop Services
-
-Following are the recommended hardware and software requirements for the Application Virtualization Client for Remote Desktop Services. The requirements are listed first for appv461_3, followed by the requirements for versions that preceded App-V 4.6 SP2.
-
-The Application Virtualization (App-V) Client for Remote Desktop Services requires no additional processor or RAM resources beyond the requirements of the host operating system.
-
-### Hardware Requirements
-
-The hardware requirements are applicable to all versions.
-
-- Processor—See recommended system requirements for the operating system you are using.
-
-- RAM—See recommended system requirements for the operating system you are using. These requirements also depend on the number of users and applications.
-
-- Disk—30 MB for installation and 6 GB for the cache.
-
-### Software Requirements for App-V 4.6 SP2
-
-
-
-
-
-
-
-
-
-
-
Operating System
-
Edition
-
Service Pack
-
Architectural SKU
-
-
-
-
-
Windows Server 2003 R2
-
Standard Edition, Enterprise Edition, or Datacenter Edition
-
SP2
-
x86 and x64
-
-
-
Windows Server 2008
-
Standard, Enterprise, or Datacenter Edition
-
SP2
-
x86 and x64
-
-
-
Windows Server 2008 R2
-
Standard, Enterprise, or Datacenter Edition
-
No service pack or SP1
-
x64
-
-
-
Windows Server 2012
-
Standard, Enterprise, or Datacenter Edition
-
-
x64
-
-
-
-
-The following software prerequisites are installed automatically if you are using the Setup.exe method. If you are using the Setup.msi installation program, the following products must be installed first.
-
-- **Microsoft Visual C++ 2005 SP1 Redistributable Package (x86)**—For more information about installing Microsoft Visual C++ 2005 SP1 Redistributable Package (x86), see [Microsoft Visual C++ 2005 SP1 Redistributable Package (x86)](https://go.microsoft.com/fwlink/?LinkId=119961) (https://go.microsoft.com/fwlink/?LinkId=119961). For version 4.5 SP2 of the App-V client, download Vcredist\_x86.exe from [Microsoft Visual C++ 2005 Service Pack 1 Redistributable Package ATL Security Update](https://go.microsoft.com/fwlink/?LinkId=169360) (https://go.microsoft.com/fwlink/?LinkId=169360).
-
-- **Microsoft Core XML Services (MSXML) 6.0 SP1 (x86)**—For more information about installing Microsoft Core XML Services (MSXML) 6.0 SP1 (x86), see [Microsoft Core XML Services (MSXML) 6.0 SP1 (x86)](https://go.microsoft.com/fwlink/?LinkId=63266) (https://go.microsoft.com/fwlink/?LinkId=63266).
-
-- **Microsoft Application Error Reporting**—The installation program for this software is included in the **Support\\Watson** folder in the self-extracting archive file.
-
-For the Application Virtualization (App-V) 4.6 Desktop Client, the following additional software prerequisite is installed automatically if you are using the Setup.exe method. If you are using the Setup.msi installation program, you must also install with the other prerequisites listed.
-
-- **Microsoft Visual C++ 2008 SP1 Redistributable Package (x86)**—For more information about installing Microsoft Visual C++ 2008 SP1 Redistributable Package (x86), see [Microsoft Visual C++ 2008 SP1 Redistributable Package (x86)](https://go.microsoft.com/fwlink/?LinkId=150700) (https://go.microsoft.com/fwlink/?LinkId=150700).
-
-### Software Requirements for Versions that Precede App-V 4.6 SP2
-
-
-
-
-
-
-
-
-
-
-
Operating System
-
Edition
-
Service Pack
-
Architectural SKU
-
-
-
-
-
Windows Server 2003
-
Standard Edition, Enterprise Edition, or Datacenter Edition
-
SP1 or SP2
-
x86 and x64
-
-
-
Windows Server 2003 R2
-
Standard Edition, Enterprise Edition, or Datacenter Edition
-
No service pack or SP2
-
x86 and x64
-
-
-
Windows Server 2008
-
Standard, Enterprise, or Datacenter Edition
-
SP1 or SP2
-
x86 and x64
-
-
-
Windows Server 2008 R2
-
Standard, Enterprise, or Datacenter Edition
-
No service pack or SP1
-
x64
-
-
-
-
-The Application Virtualization (App-V) 4.6 Client for Remote Desktop Services supports x86 and x64 SKUs of these operating systems.
-
-## Related topics
-- [Application Virtualization Sequencer Hardware and Software Requirements](application-virtualization-sequencer-hardware-and-software-requirements.md)
-- [Application Virtualization System Requirements](application-virtualization-system-requirements.md)
-- [How to Install the Client by Using the Command Line](how-to-install-the-client-by-using-the-command-line-new.md)
-- [How to Manually Install the Application Virtualization Client](how-to-manually-install-the-application-virtualization-client.md)
-- [How to Upgrade the Application Virtualization Client](how-to-upgrade-the-application-virtualization-client.md)
diff --git a/mdop/appv-v4/application-virtualization-client-installer-command-line-parameters.md b/mdop/appv-v4/application-virtualization-client-installer-command-line-parameters.md
deleted file mode 100644
index 2f13cd29a0..0000000000
--- a/mdop/appv-v4/application-virtualization-client-installer-command-line-parameters.md
+++ /dev/null
@@ -1,311 +0,0 @@
----
-title: Application Virtualization Client Installer Command-Line Parameters
-description: Application Virtualization Client Installer Command-Line Parameters
-author: dansimp
-ms.assetid: 508fa404-52a5-4919-8788-2a3dfb00639b
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 08/30/2016
----
-
-
-# Application Virtualization Client Installer Command-Line Parameters
-
-
-The following table lists all available Microsoft Application Virtualization Client installer command-line parameters, their values, and a brief description of each parameter. Parameters are case-sensitive and must be entered as all-uppercase letters. All parameter values must be enclosed in double quotes.
-
-**Note**
-- For App-V version 4.6, command-line parameters cannot be used during a client upgrade.
-
-- The *SWICACHESIZE* and *MINFREESPACEMB* parameters cannot be combined on the command line. If both are used, the *SWICACHESIZE* parameter will be ignored.
-
-
-
-
-
-
-
-
-
-
-
-
Parameter
-
Values
-
Description
-
-
-
-
-
ALLOWINDEPENDENTFILESTREAMING
-
TRUE
-
FALSE
-
Indicates whether streaming from file will be enabled regardless of how the client has been configured with the APPLICATIONSOURCEROOT parameter. If set to FALSE, the transport will not enable streaming from files even if the OSD HREF or the APPLICATIONSOURCEROOT parameter contains a file path.
-
Possible values:
-
-
TRUE—Manually deployed application may be loaded from disk.
-
FALSE—All applications must come from source streaming server.
-
-
-
-
APPLICATIONSOURCEROOT
-
RTSP:// URL (for dynamic package delivery)
-
File:// URL or UNC (for load from file package delivery)
-
To enable an administrator or an electronic software distribution system to ensure that application loading is performed in compliance with the topology management scheme, allows an override of the OSD CODEBASE for the application HREF element (the source location). If the value is “”, which is the default value, the existing OSD file settings are used.
If the APPLICATIONSOURCEROOT parameter is specified on a client, the client will break the URL or UNC path from an OSD file into its constituent parts and replace the OSD sections with the corresponding APPLICATIONSOURCEROOT sections.
-
-Important
Be sure to use the correct format when using file:// with a UNC path. The correct format is file://<server><share>.
-
-
-
-
-
-
-
ICONSOURCEROOT
-
UNC
-
HTTP://URL or HTTPS://URL
-
Enables an administrator to specify a source location for icon retrieval for a sequenced application package during publication. Icon source roots support UNC paths and URLs (HTTP or HTTPS). If the value is “”, which is the default value, the existing OSD file settings are used.
Be sure to use the correct format when using a UNC path. Acceptable formats are <server><share> or <drive letter>:<folder>.
-
-
-
-
-
-
-
OSDSOURCEROOT
-
UNC
-
HTTP://URL or HTTPS://URL
-
Enables an administrator to specify a source location for OSD file retrieval for an application package during publication. OSD source roots support UNC paths and URLs (HTTP or HTTPS). If the value is “”, which is the default value, the existing OSD file settings are used.
Be sure to use the correct format when using a UNC path. Acceptable formats are <server><share> or <drive letter>:<folder>.
-
-
-
-
-
-
-
AUTOLOADONLOGIN
-
AUTOLOADONLAUNCH
-
AUTOLOADONREFRESH
-
[0|1]
-
The AutoLoad triggers that define the events that initiate auto-loading of applications. AutoLoad implicitly uses background streaming to enable the application to be fully loaded into cache.
-
The primary feature block will be loaded as quickly as possible. Remaining feature blocks will be loaded in the background to enable foreground operations, such as user interaction with applications, to take priority and provide optimal performance.
-
-Note
The AUTOLOADTARGET parameter determines which applications are auto-loaded. By default, packages that have been used are auto-loaded unless AUTOLOADTARGET is set.
-
-
-
-
-
Each parameter affects loading behavior as follows:
-
-
AUTOLOADONLOGIN—Loading starts when the user logs in.
-
AUTOLOADONLAUNCH—Loading starts when the user starts an application.
-
AUTOLOADONREFRESH—Loading starts when a publishing refresh occurs.
-
-
The three values can be combined. In the following example, AutoLoad triggers are enabled both at user login and when publishing refresh occurs:
-
AUTOLOADONLOGIN AUTOLOADONREFRESH
-
-Note
If the client is configured with these values at first install, Autoload will not be triggered until the next time the user logs off and logs back on.
-
-
-
-
-
-
-
AUTOLOADTARGET
-
NONE
-
ALL
-
PREVUSED
-
Indicates what will be auto-loaded when any given AutoLoad triggers occur.
-
Possible values:
-
-
NONE—No auto-loading, regardless of what triggers might be set.
-
ALL—If any AutoLoad trigger is enabled, all packages are automatically loaded, whether or not they have ever been launched.
-
-Note
This setting is configured for individual packages by using the SFTMIME ADD PACKAGE and CONFIGURE PACKAGE commands. For more information about these commands, see SFTMIME Command Reference.
-
-
-
-
-
PREVUSED—If any AutoLoad trigger is enabled, load only the packages where at least one application in the package has been previously used (that is, launched or precached).
-
-
-Note
When you install the App-V client to use a read-only cache, (for example, as a VDI server implementation), you must set the AUTOLOADTARGET parameter to NONE to prevent the client from trying to update applications in the read-only cache.
-
-
-
-
-
-
-
DOTIMEOUTMINUTES
-
29600 (default)
-
1–1439998560 minutes (range)
-
Indicates how many minutes an application may be used in disconnected operation.
-
-
-
INSTALLDIR
-
<pathname>
-
Specifies the installation directory of the App-V Client.
Microsoft Application Virtualization Client components will be upgradable through Microsoft Update when updates are made available to the general public. The Microsoft Update Agent installed on Windows operating systems requires a user to explicitly opt-in to use the service. This opt-in is required only one time for all applications on the device. If you have already opted into Microsoft Update, the Microsoft Application Virtualization components on the device will automatically take advantage of the service.
-
For command-line installation, use of Microsoft Update is by default opt-out (unless a previous application already enabled the device to be opted in) due to the requirement for manually opting into Microsoft Update. Therefore, opting in must be explicit for command-line installations. Setting the command-line parameter OPTIN to TRUE forces the Microsoft Update opt-in to be set.
-
-
-
REQUIREAUTHORIZATIONIFCACHED
-
TRUE
-
FALSE
-
Indicates whether authorization is always required, whether or not an application is already in cache.
-
Possible values:
-
-
TRUE—Application always must be authorized at startup. For RTSP streamed applications, the user authorization token is sent to the server for authorization. For file-based applications, file ACLs dictate whether a user may access the application.
-
FALSE—Always try to connect to the server. If a connection to the server cannot be established, the client still allows the user to launch an application that has previously been loaded into cache.
-
-
-
-
SWICACHESIZE
-
Cache size in MB
-
Specifies the size in megabytes of the client cache. The default size is 4096 MB, and the maximum size is 1,048,576 MB (1 TB). The system checks for the available space at installation time, but the space is not reserved.
-
Example: SWICACHESIZE="1024"
-
-
-
SWIPUBSVRDISPLAY
-
Display name
-
Specifies the displayed name of the publishing server; required when SWIPUBSVRHOST is used.
Specifies the publishing server type. The default server type is Application Virtualization Server. The /secure switch is not case sensitive.
-
-
HTTP—Standard HTTP Server
-
HTTP /secure—Enhanced Security HTTP Server
-
RTSP—Application Virtualization Server
-
RTSP /secure—Enhanced Security Application Virtualization Server
-
-
Example: SWIPUBSVRTYPE="HTTP /secure"
-
-
-
SWIPUBSVRHOST
-
IP address|host name
-
Specifies either the IP address of the Application Virtualization Server or a host name of the server that resolves into the server's IP address; required when SWIPUBSVRDISPLAY is used.
-
Example: SWIPUBSVRHOST="SERVER01"
-
-
-
SWIPUBSVRPORT
-
Port number
-
Specifies the logical port that is used by this Application Virtualization Server to listen for requests from the client (default = 554).
Specifies the location on the publishing server of the file that defines file type associations (default = /); required when the SWIPUBSVRTYPE parameter value is HTTP.
-
Example: SWIPUBSVRPATH="/AppVirt/appsntypes.xml"
-
-
-
SWIPUBSVRREFRESH
-
[ON|OFF]
-
Specifies whether the client automatically queries the publishing server for file type associations and applications when a user logs in to the client (default = ON).
-
Example: SWIPUBSVRREFRESH="off"
-
-
-
SWIGLOBALDATA
-
Global data directory
-
Specifies the directory where data will be stored that is not specific to particular users (default = C:\Documents and Settings\All Users\Documents).
Corresponds to the drive letter that you selected for the virtual drive.
-
Example: SWIFSDRIVE="S"
-
-
-
SYSTEMEVENTLOGLEVEL
-
0–4
-
Indicates the logging level at which log messages are written to the NT event Log. The value indicates a threshold of what is logged—that is, everything equal to or less than that value is logged. For example, a value of 0x3 (Warning) indicates that Warnings (0x3), Errors (0x2), and Critical Errors (0x1) are logged.
-
Possible values:
-
-
0 == None
-
1 == Critical
-
2 == Error
-
3 == Warning
-
4 == Information
-
-
-
-
MINFREESPACEMB
-
In MB
-
Specifies the amount of free space (in megabytes) that must be available on the host before the cache size can increase. The following example would configure the client to ensure at least 5 GB of free space on the disk before allowing the size of the cache to increase. The default is 5000 MB of free space available on disk at installation time.
-
Example: MINFREESPACEMB ="5000" (5 GB)
-
-
-
KEEPCURRENTSETTINGS
-
[0|1]
-
Used when you have applied registry settings prior to deploying a client—for example, by using Group Policy. When a client is deployed, set this parameter to a value of 1 so that it will not overwrite the registry settings.
-
-Important
If set to a value of 1, the following client installer command-line parameters are ignored:
For further information about setting these values after installation, see “How to Configure the App-V Client Registry Settings by Using the Command Line” in the Application Virtualization (App-V) Operations Guide (https://go.microsoft.com/fwlink/?LinkId=122939).
-
-
-
-
-
-
-
-
-
-
-## Related topics
-
-
-[How to Manually Install the Application Virtualization Client](how-to-manually-install-the-application-virtualization-client.md)
-
-[How to Upgrade the Application Virtualization Client](how-to-upgrade-the-application-virtualization-client.md)
-
-[SFTMIME Command Reference](sftmime--command-reference.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/application-virtualization-client-management-console-overview.md b/mdop/appv-v4/application-virtualization-client-management-console-overview.md
deleted file mode 100644
index 1f514c7ba3..0000000000
--- a/mdop/appv-v4/application-virtualization-client-management-console-overview.md
+++ /dev/null
@@ -1,46 +0,0 @@
----
-title: Application Virtualization Client Management Console Overview
-description: Application Virtualization Client Management Console Overview
-author: dansimp
-ms.assetid: 21d648cc-eca5-475c-be42-228879b7a45a
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Application Virtualization Client Management Console Overview
-
-
-The Microsoft Application Virtualization Client Management Console is a snap-in to the Microsoft Management Console. Administrators and users can use the Application Virtualization Management Console to configure the Desktop Client and Client for Remote Desktop Services (formerly Terminal Services) and manage applications.
-
-## In This Section
-
-
-[About Application Virtualization Servers](about-application-virtualization-servers.md)
-Provides a brief description of the Application Virtualization Management Servers.
-
-[User Access Permissions in Application Virtualization Client](user-access-permissions-in-application-virtualization-client.md)
-Provides the list of user access permissions.
-
-[Disconnected Operation Mode](disconnected-operation-mode.md)
-Describes the disconnected operation mode and circumstances that affect it.
-
-## Related topics
-
-
-[Application Virtualization Client Management Console](application-virtualization-client-management-console.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/application-virtualization-client-management-console-reference.md b/mdop/appv-v4/application-virtualization-client-management-console-reference.md
deleted file mode 100644
index e13ceabe61..0000000000
--- a/mdop/appv-v4/application-virtualization-client-management-console-reference.md
+++ /dev/null
@@ -1,55 +0,0 @@
----
-title: Application Virtualization Client Management Console Reference
-description: Application Virtualization Client Management Console Reference
-author: dansimp
-ms.assetid: aa27537d-e053-45b5-b0ee-cf6606849e0c
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Application Virtualization Client Management Console Reference
-
-
-The topics in this section provide detailed information about each of the functional areas of the Application Virtualization Client Management Console.
-
-## In This Section
-
-
-[Client Management Console: Application Virtualization Node](client-management-console-application-virtualization-node.md)
-Describes the screens in the **Application Virtualization** node.
-
-[Client Management Console: About Dialog Boxes](client-management-console-about-dialog-boxes.md)
-Describes the screens in the **About Dialog** node.
-
-[Client Management Console: Applications Node](client-management-console-applications-node.md)
-Describes the screens in the **Applications** node.
-
-[Client Management Console: File Type Associations Node](client-management-console-file-type-associations-node.md)
-Describes the screens in the **File Type Association** node.
-
-[Client Management Console: Publishing Servers Node](client-management-console-publishing-servers-node.md)
-Describes the screens in the **Publishing Servers** node.
-
-[Client Management Console: Application Virtualization Properties](client-management-console-application-virtualization-properties.md)
-Describes the screens for **Application Virtualization Properties**.
-
-## Related topics
-
-
-[Application Virtualization Client Management Console](application-virtualization-client-management-console.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/application-virtualization-client-management-console-roadmap.md b/mdop/appv-v4/application-virtualization-client-management-console-roadmap.md
deleted file mode 100644
index a65de90286..0000000000
--- a/mdop/appv-v4/application-virtualization-client-management-console-roadmap.md
+++ /dev/null
@@ -1,68 +0,0 @@
----
-title: Application Virtualization Client Management Console Roadmap
-description: Application Virtualization Client Management Console Roadmap
-author: dansimp
-ms.assetid: 3aca02c4-728c-4c34-b90f-4e6f188937b0
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Application Virtualization Client Management Console Roadmap
-
-
-The Application Virtualization Client Management Console is a snap-in to the Microsoft Management Console. Administrators and users can use the Application Virtualization Client Management Console to configure the Desktop Client and Client for Remote Desktop Services (formerly Terminal Services) and manage desktops and applications. The following lists represent some of the available procedures in the Client Management Console.
-
-The following topics detail some general administrative tasks you can perform:
-
-- [How to Set Up Publishing Servers](how-to-set-up-publishing-servers.md)
-
-- [How to Refresh the Publishing Servers](how-to-refresh-the-publishing-servers.md)
-
-The following topics detail what you can do when configuring the Application Virtualization client:
-
-- [How to Change the Cache Size and the Drive Letter Designation](how-to-change-the-cache-size-and-the-drive-letter-designation.md)
-
-- [How to Change the Log Reporting Levels and Reset the Log Files](how-to-change-the-log-reporting-levels-and-reset-the-log-files.md)
-
-- [How to Change User Access Permissions](how-to-change-user-access-permissions.md)
-
-- [How to Change Import Search Paths](how-to-change-import-search-paths.md)
-
-- [How to Set Up Publishing Refresh on Login](how-to-set-up-publishing-refresh-on-login.md)
-
-- [How to Set Up Periodic Publishing Refresh](how-to-set-up-periodic-publishing-refresh.md)
-
-The following topics detail what you can do when managing applications:
-
-- [How to Delete an Application](how-to-delete-an-application.md)
-
-- [How to Load or Unload an Application](how-to-load-or-unload-an-application.md)
-
-- [How to Clear an Application](how-to-clear-an-application.md)
-
-- [How to Import an Application](how-to-import-an-application.md)
-
-- [How to Change an Application Icon](how-to-change-an-application-icon.md)
-
-- [How to Lock or Unlock an Application](how-to-lock-or-unlock-an-application.md)
-
-## Related topics
-
-
-[About Virtual Environments](about-virtual-environments.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/application-virtualization-client-management-console.md b/mdop/appv-v4/application-virtualization-client-management-console.md
deleted file mode 100644
index e8e5980d13..0000000000
--- a/mdop/appv-v4/application-virtualization-client-management-console.md
+++ /dev/null
@@ -1,54 +0,0 @@
----
-title: Application Virtualization Client Management Console
-description: Application Virtualization Client Management Console
-author: dansimp
-ms.assetid: 18635688-8cbe-40d1-894e-acb2749b4e69
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Application Virtualization Client Management Console
-
-
-The Microsoft Application Virtualization Client Management Console is a snap-in to the Microsoft Management Console. Administrators and users can use the Application Virtualization Management Console to configure the Desktop Client and Client for Remote Desktop Services (formerly Terminal Services) and manage applications.
-
-## In This Section
-
-
-[Application Virtualization Client Management Console Overview](application-virtualization-client-management-console-overview.md)
-Provides general information about the tasks you can perform by using the Virtualization Client Management Console.
-
-[How to Perform General Administrative Tasks in the Client Management Console](how-to-perform-general-administrative-tasks-in-the-client-management-console.md)
-Provides procedures that you can use to set up the Publishing Server and to refresh applications.
-
-[How to Manage Applications in the Client Management Console](how-to-manage-applications-in-the-client-management-console.md)
-Provides procedures that you can use to manage applications.
-
-[How to Configure the Client in the Application Virtualization Client Management Console](how-to-configure-the-client-in-the-application-virtualization-client-management-console.md)
-Provides procedures that you can use to configure Desktop Client and Client for Remote Desktop Services.
-
-[How to Manually Manage Applications in the Client Management Console](how-to-manually-manage-applications-in-the-client-management-console.md)
-Provides procedures that you can use to manually manage applications.
-
-## Related topics
-
-
-[Application Virtualization Client Management Console Reference](application-virtualization-client-management-console-reference.md)
-
-[How to Use the Desktop Notification Area for Application Virtualization Client Management](how-to-use-the-desktop-notification-area-for-application-virtualization-client-management.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/application-virtualization-client-reference.md b/mdop/appv-v4/application-virtualization-client-reference.md
deleted file mode 100644
index bc3dbef0d8..0000000000
--- a/mdop/appv-v4/application-virtualization-client-reference.md
+++ /dev/null
@@ -1,58 +0,0 @@
----
-title: Application Virtualization Client Reference
-description: Application Virtualization Client Reference
-author: dansimp
-ms.assetid: 5107f567-9ac8-43e1-89c8-5e0762e3ddd8
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Application Virtualization Client Reference
-
-
-This section provides reference information that is related to installing and managing the Application Virtualization (App-V) Client and the virtual application packages that are created by the Application Virtualization (App-V) Sequencer.
-
-## In This Section
-
-
-[SFTMIME Command Reference](sftmime--command-reference.md)
-Provides a detailed list of all SFTMIME parameters.
-
-[SFTTRAY Command Reference](sfttray-command-reference.md)
-Lists and describes all SFTTRAY commands and command-line switches.
-
-[Application Virtualization Client WMI Provider](application-virtualization-client-wmi-provider.md)
-Describes the Windows Management Instrumentation (WMI) classes that are available in the App-V Client WMI Provider.
-
-[Log File for the Application Virtualization Client](log-file-for-the-application-virtualization-client.md)
-Provides information about the log file for the App-V Client.
-
-[App-V Client Registry Values](app-v-client-registry-values-sp1.md)
-Provides a detailed list and descriptions of registry key values.
-
-[App-V Interoperability with Windows AppLocker](app-v-interoperability-with-windows-applocker.md)
-Provides information on how to configure AppLocker rules for virtual applications.
-
-[Support for Client Reporting over HTTP](support-for-client-reporting-over-http.md)
-Provides an overview of the Client Reporting process for HTTP publishing.
-
-## Related topics
-
-
-[Application Virtualization Client](application-virtualization-client.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/application-virtualization-client-wmi-provider.md b/mdop/appv-v4/application-virtualization-client-wmi-provider.md
deleted file mode 100644
index dd3b3f8eae..0000000000
--- a/mdop/appv-v4/application-virtualization-client-wmi-provider.md
+++ /dev/null
@@ -1,45 +0,0 @@
----
-title: Application Virtualization Client WMI Provider
-description: Application Virtualization Client WMI Provider
-author: dansimp
-ms.assetid: 384e33e0-6689-4e28-af84-53acee8a5c24
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Application Virtualization Client WMI Provider
-
-
-This section contains detailed information about the Application Virtualization (App-V) Client Windows Management Instrumentation (WMI) Provider. All the classes that are described are in the WMI root\\microsoft\\appvirt\\client namespace.
-
-You can use a query tool such as wbemtest.exe or a scripting language such as Windows PowerShell or VBScript to retrieve key information about packages and applications from the clients for reporting purposes. The information available includes details on package status, cache size, and usage data.
-
-## In This Section
-
-
-[App-V Application WMI Class](app-v-application-wmi-class.md)
-Represents an individual application object in a package.
-
-[App-V Package WMI Class](app-v-package-wmi-class.md)
-Represents an individual virtual package that can contain multiple applications.
-
-## Related topics
-
-
-[Application Virtualization Client Reference](application-virtualization-client-reference.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/application-virtualization-client.md b/mdop/appv-v4/application-virtualization-client.md
deleted file mode 100644
index 819dd8bed1..0000000000
--- a/mdop/appv-v4/application-virtualization-client.md
+++ /dev/null
@@ -1,60 +0,0 @@
----
-title: Application Virtualization Client
-description: Application Virtualization Client
-author: dansimp
-ms.assetid: d9e1939b-eb9c-49a0-855d-f4c323b84c2f
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Application Virtualization Client
-
-
-You can use the procedures in this section to configure and manage the Microsoft Application Virtualization (App-V) Client. Procedures are provided for manual interaction with the App-V Client by using the App-V Client Management Console and also by using the command line.
-
-## In This Section
-
-
-[How to Use the Desktop Notification Area for Application Virtualization Client Management](how-to-use-the-desktop-notification-area-for-application-virtualization-client-management.md)
-Includes information about using the features and commands that are available from the Windows desktop notification area.
-
-[How to Manage Virtual Applications Manually](how-to-manage-virtual-applications-manually.md)
-Provides information about how to manage the virtual applications by using the App-V Client Management Console.
-
-[How to Configure the Application Virtualization Client Settings Manually](how-to-configure-the-application-virtualization-client-settings-manually.md)
-Provides a set of procedures that you can use to configure App-V Client settings by using the App-V Client Management Console.
-
-[How to Manage Virtual Applications by Using the Command Line](how-to-manage-virtual-applications-by-using-the-command-line.md)
-Provides important procedures you can use to manage virtual applications and packages by using the SFTMIME command-line language.
-
-[How to Configure the App-V Client Registry Settings by Using the Command Line](how-to-configure-the-app-v-client-registry-settings-by-using-the-command-line.md)
-Provides a set of procedures you can use to change the configuration of the App-V Client.
-
-[Troubleshooting Information for the Application Virtualization Client](troubleshooting-information-for-the-application-virtualization-client.md)
-Provides information about troubleshooting the App-V Client.
-
-[Application Virtualization Client Reference](application-virtualization-client-reference.md)
-Contains detailed technical reference material related to installing and managing system components.
-
-## Related topics
-
-
-[Application Virtualization Sequencer](application-virtualization-sequencer.md)
-
-[Application Virtualization Server](application-virtualization-server.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/application-virtualization-deployment-and-upgrade-checklists.md b/mdop/appv-v4/application-virtualization-deployment-and-upgrade-checklists.md
deleted file mode 100644
index 4bd4d4fe49..0000000000
--- a/mdop/appv-v4/application-virtualization-deployment-and-upgrade-checklists.md
+++ /dev/null
@@ -1,49 +0,0 @@
----
-title: Application Virtualization Deployment and Upgrade Checklists
-description: Application Virtualization Deployment and Upgrade Checklists
-author: dansimp
-ms.assetid: 462e5119-cb83-4548-98f2-df668aa0958b
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Application Virtualization Deployment and Upgrade Checklists
-
-
-The topics in this section provide checklists that you can use when installing the Microsoft Application Virtualization (App-V) system.
-
-## In This Section
-
-
-[App-V Pre-Installation Checklist](app-v-pre-installation-checklist.md)
-Describes the tasks that must be completed before starting the installation of the App-V system.
-
-[App-V Installation Checklist](app-v-installation-checklist.md)
-Describes the tasks that must be completed while installing the App-V system.
-
-[App-V Postinstallation Checklist](app-v-postinstallation-checklist.md)
-Describes the tasks that must be completed after the installation of the App-V system.
-
-[App-V Upgrade Checklist](app-v-upgrade-checklist.md)
-Describes the tasks to be completed when upgrading the App-V system and the correct sequence for those tasks.
-
-## Related topics
-
-
-[Application Virtualization Deployment Requirements](application-virtualization-deployment-requirements.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/application-virtualization-deployment-and-upgrade-considerations-copy.md b/mdop/appv-v4/application-virtualization-deployment-and-upgrade-considerations-copy.md
deleted file mode 100644
index d71379b47f..0000000000
--- a/mdop/appv-v4/application-virtualization-deployment-and-upgrade-considerations-copy.md
+++ /dev/null
@@ -1,67 +0,0 @@
----
-title: Application Virtualization Deployment and Upgrade Considerations
-description: Application Virtualization Deployment and Upgrade Considerations
-author: dansimp
-ms.assetid: c3c38930-0da3-43e6-b240-945edfd00a01
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Application Virtualization Deployment and Upgrade Considerations
-
-
-Before you begin the deployment of Microsoft Application Virtualization (App-V), you might have to review your environment requirements that includes the hardware and software requirements for installing the various Application Virtualization components. Also, if you are upgrading from an earlier version, the topics in this section provide information about how to upgrade your current Sequencer, Server, and Client versions.
-
-## In This Section
-
-
-[Application Virtualization Deployment Requirements](application-virtualization-deployment-requirements.md)
-Provides general information about system requirements and upgrade considerations for your Application Virtualization deployment.
-
-[Application Virtualization Deployment and Upgrade Checklists](application-virtualization-deployment-and-upgrade-checklists.md)
-Provides detailed lists of installation and upgrade tasks with links to the specific procedures.
-
-[How to Install the Servers and System Components](how-to-install-the-servers-and-system-components.md)
-Describes how to install the Application Virtualization (App-V) platform components required for your server-based deployment.
-
-[How to Manually Install the Application Virtualization Client](how-to-manually-install-the-application-virtualization-client.md)
-Describes how to install the Application Virtualization Client software.
-
-[How to Install the Application Virtualization Sequencer](how-to-install-the-application-virtualization-sequencer.md)
-Describes how to install the Application Virtualization Sequencer.
-
-[How to Upgrade the Application Virtualization Client](how-to-upgrade-the-application-virtualization-client.md)
-Describes how to upgrade the Application Virtualization Desktop Client or the Application Virtualization Client for Remote Desktop Services (formerly Terminal Services).
-
-[How to Upgrade the Servers and System Components](how-to-upgrade-the-servers-and-system-components.md)
-Describes how to upgrade the software components installed on all Application Virtualization Management System computers.
-
-[How to Upgrade the Application Virtualization Sequencer](how-to-upgrade-the-application-virtualization-sequencer.md)
-Describes how to upgrade the Sequencer on computers that are running Windows Vista or Windows XP.
-
-## Related topics
-
-
-[Application Virtualization Reference](application-virtualization-reference.md)
-
-[Application Virtualization Server-Based Scenario](application-virtualization-server-based-scenario.md)
-
-[Electronic Software Distribution-Based Scenario](electronic-software-distribution-based-scenario.md)
-
-[Stand-Alone Delivery Scenario for Application Virtualization Clients](stand-alone-delivery-scenario-for-application-virtualization-clients.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/application-virtualization-deployment-and-upgrade-considerations.md b/mdop/appv-v4/application-virtualization-deployment-and-upgrade-considerations.md
deleted file mode 100644
index c09ced741d..0000000000
--- a/mdop/appv-v4/application-virtualization-deployment-and-upgrade-considerations.md
+++ /dev/null
@@ -1,58 +0,0 @@
----
-title: Application Virtualization Deployment and Upgrade Considerations
-description: Application Virtualization Deployment and Upgrade Considerations
-author: dansimp
-ms.assetid: adc562ee-7276-4b14-b10a-da17f05e1682
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Application Virtualization Deployment and Upgrade Considerations
-
-
-Before you begin the deployment of Microsoft Application Virtualization, you might need to review your environment requirements, including the hardware and software requirements for installing the various Application Virtualization components. Also, if you are upgrading from a previous version, the topics in this section provide information about upgrading your current Sequencer, server, and client versions.
-
-## In This Section
-
-
-[Application Virtualization Deployment Requirements](application-virtualization-deployment-requirements.md)
-Provides general information about system requirements and upgrade considerations for your Application Virtualization deployment.
-
-[How to Upgrade the Application Virtualization Client](how-to-upgrade-the-application-virtualization-client.md)
-Provides step-by-step procedures for upgrading the Application Virtualization Desktop Client or the Application Virtualization Client for Remote Desktop Services (formerly Terminal Services).
-
-[How to Upgrade the Servers and System Components](how-to-upgrade-the-servers-and-system-components.md)
-Provides a step-by-step procedure you can use to upgrade the software components installed on all Application Virtualization System computers.
-
-[How to Upgrade the Application Virtualization Sequencer](how-to-upgrade-the-application-virtualization-sequencer.md)
-Provides step-by-step procedures for upgrading the Sequencer on computers running Windows Vista or Windows XP.
-
-[How to Install the Application Virtualization Sequencer](how-to-install-the-application-virtualization-sequencer.md)
-Provides a step-by-step procedure for installing the Sequencer.
-
-## Related topics
-
-
-[Application Virtualization Reference](application-virtualization-reference.md)
-
-[Application Virtualization Server-Based Scenario](application-virtualization-server-based-scenario.md)
-
-[Electronic Software Distribution-Based Scenario](electronic-software-distribution-based-scenario.md)
-
-[Stand-Alone Delivery Scenario for Application Virtualization Clients](stand-alone-delivery-scenario-for-application-virtualization-clients.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/application-virtualization-deployment-requirements.md b/mdop/appv-v4/application-virtualization-deployment-requirements.md
deleted file mode 100644
index 9baee67d59..0000000000
--- a/mdop/appv-v4/application-virtualization-deployment-requirements.md
+++ /dev/null
@@ -1,55 +0,0 @@
----
-title: Application Virtualization Deployment Requirements
-description: Application Virtualization Deployment Requirements
-author: dansimp
-ms.assetid: 9564e974-a853-45ae-b605-0a2e3e5cf212
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Application Virtualization Deployment Requirements
-
-
-Before you deploy Microsoft Application Virtualization (App-V) in your environment, you should verify that you can meet the hardware and software requirements for the components you plan to deploy, according to your chosen deployment scenario.
-
-## In This Section
-
-
-[Application Virtualization System Requirements](application-virtualization-system-requirements.md)
-Describes the recommended hardware and software requirements for each of the Application Virtualization System components.
-
-[Application Virtualization Sequencer Hardware and Software Requirements](application-virtualization-sequencer-hardware-and-software-requirements.md)
-Describes the minimum recommended hardware and software configuration for your Microsoft Application Virtualization Sequencer workstation.
-
-[Application Virtualization Client Hardware and Software Requirements](application-virtualization-client-hardware-and-software-requirements.md)
-Describes the recommended minimum hardware and software configuration for your installation of the Application Virtualization Desktop Client and the Application Virtualization Client for Remote Desktop Services (formerly Terminal Services).
-
-[Configuring Prerequisite Groups in Active Directory for App-V](configuring-prerequisite-groups-in-active-directory-for-app-v.md)
-Describes the objects that you must install in Active Directory groups before you install the App-V system.
-
-[How to Configure Windows Server 2008 for App-V Management Servers](how-to-configure-windows-server-2008-for-app-v-management-servers.md)
-Describes how to configure the server running Windows Server 2008 by installing Internet Information Services (IIS) as a role so that you can install the App-V Management Web Service.
-
-[Application Virtualization Deployment and Upgrade Checklists](application-virtualization-deployment-and-upgrade-checklists.md)
-Provides checklists of tasks to guide you through the correct sequence when installing or upgrading the App-V system.
-
-## Related topics
-
-
-[Application Virtualization Deployment and Upgrade Considerations](application-virtualization-deployment-and-upgrade-considerations.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/application-virtualization-glossary.md b/mdop/appv-v4/application-virtualization-glossary.md
deleted file mode 100644
index 3669509527..0000000000
--- a/mdop/appv-v4/application-virtualization-glossary.md
+++ /dev/null
@@ -1,208 +0,0 @@
----
-title: Application Virtualization Glossary
-description: Application Virtualization Glossary
-author: dansimp
-ms.assetid: 9eb71774-e288-4f94-8f94-5b98e0d012a7
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Application Virtualization Glossary
-
-
-
-
-
-
-
-
-
-
Term
-
Definition
-
-
-
-
-
active upgrade
-
An upgrade that enables a new version of an application to be added to an App-V Management Server or Streaming Server without affecting users currently running the application.
-
-
-
Application Source Root
-
Reference to a registry key that allows an override of the OSD CODEBASE for the HREF element (for example, the source location). This registry value enables an administrator or ESD system to ensure application loading is performed according to a planned topology management scheme.
-
-
-
Application Virtualization drive
-
The default virtual application client drive (Q:) from which sequenced applications are run.
-
-
-
Application Virtualization reporting
-
Virtual application information gathered for data analysis. Data is collected for assembly of custom views and interpretation.
-
-
-
AutoLoad configuration parameter
-
A client runtime policy configuration parameter that enables the secondary feature block of a virtualized application to be streamed to the client automatically in the background.
-
-
-
branch a package
-
To upgrade an existing sequenced application package and run it side-by-side with the original sequenced application package.
-
-
-
Dynamic Suite Composition
-
An Application Virtualization feature that enables a virtual application package to allow dependent plug-ins or middleware packages to use the virtual environment. This feature enables plug-ins and middleware packages to use the primary package's registry settings, and the packages behave and interact with one another in the same way as if they were installed locally on a comuter.
-
-
-
ICO file
-
The file for the icon on the client's desktop used to launch a sequenced application.
-
-
-
Icon Source Root
-
Reference to a registry key that allows specification of a source location for icon retrieval for a sequenced application package during publication. Icon Source Roots support UNC formats only (not URLs).
-
-
-
Installation directory
-
The directory where the installer for the application virtualization sequencer places its files.
-
-
-
Microsoft Application Virtualization Desktop Client
-
An application that resides on a Windows-based computer desktop and which communicates and authenticates with the Microsoft System Center Virtual Application Server to receive the application code and allow a sequenced application to be run locally.
-
-
-
Microsoft Application Virtualization for Terminal Services
-
The Application Virtualization feature, including both client and server components, running in a Terminal Services environment.
-
-
-
Microsoft Application Virtualization Management Console
-
Centralized snap-in to the Microsoft Management Console, which you use to administer the Application Virtualization Management System.
-
-
-
Microsoft Application Virtualization Management System
-
A specific deployment of the Application Virtualization platform that includes all of the components that are managed by a single data store.
-
-
-
Microsoft Application Virtualization Management Web Service
-
A service that acts as an intermediary between the Application Virtualization Management Console and the data store. First it authenticates its users, and then it allows authorized administrators to manipulate data in the data store.
-
-
-
Microsoft Application Virtualization platform
-
Name for the Microsoft products that are used to create, store, distribute, and run virtualized applications.
-
-
-
Microsoft Application Virtualization Sequencer
-
Application that monitors and records the installation and setup process for applications so that an application can be sequenced and run in the virtual environment.
-
-
-
Microsoft Application Virtualization Terminal Services Client
-
An application that resides on a Terminal Server and which communicates and authenticates with the Microsoft Virtual Application Server to receive the application code and allow a sequenced application to be run locally.
-
-
-
Microsoft System Center Application Virtualization Management Server
-
One of two Application Virtualization server types from which a sequenced application package can be streamed. In addition to streaming virtual application packages, the Application Virtualization Management Server offers other services such as publishing, management, reporting, and so on.
-
-
-
Microsoft System Center Application Virtualization Streaming Server
-
One of two Application Virtualization server types from which a sequenced application package can be streamed. The Streaming Server streams applications to the client computers only and does not offer other services such as publishing, management, reporting, and so on.
-
-
-
Open Software Descriptor (OSD) file
-
An XML-based file that instructs the client on how to retrieve the sequenced application from the Application Virtualization Management/Streaming Server and how to run the sequenced application in its virtual environment.
-
-
-
OSD Source Root
-
Reference to a registry key that allows specification of a source location for OSD file retrieval for an application package during publication. OSD Source Roots support UNC formats only (not URLs).
-
-
-
package root directory
-
The directory on the sequencing computer on which files for the sequenced application package are installed. This directory also exists virtually on the computer to which a sequenced application will be streamed.
-
-
-
primary feature block
-
The minimum content in an application package that is necessary for an application to run. The content in the primary feature block is identified during the application phase of sequencing and typically consists of the content for the most used application features.
-
-
-
secondary feature block
-
The remainder of the application package that is not contained in the primary feature block. This content is streamed to the client on demand as application features are used.
-
-
-
sequenced application
-
An application that has been monitored by the Sequencer, broken up into primary and secondary feature blocks, streamed to a computer running the Microsoft Application Virtualization Terminal Services Client or the Microsoft Application Virtualization Desktop Client, and can run inside of its own virtual environment.
-
-
-
sequenced application package
-
The files that comprise a virtual application and allow a virtual application to run. These files are created after sequencing and specifically include .osd, .sft, .sprj, and .ico files.
-
-
-
sequencing
-
The process of creating an application package by using the Application Virtualization Sequencer. In this process, an application is monitored, its shortcuts are configured, and a sequenced application package is created containing the .osd, .sft, .sprj, and .ico files.
-
-
-
sequencing computer
-
The computer used to perform sequencing and create a sequenced application package.
-
-
-
Sequencing Wizard
-
Step-by-step wizard that walks the user through sequencing an application, including package configuration, installing the application or applications to be sequenced, and sequencing the application package for streaming.
-
-
-
SFT
-
A file that contains one or more sequenced applications that the Sequencer has packaged into streaming blocks, as well as the associated delivery information. The SFT file is stored on each server that must stream the packaged applications to a client.
-
-
-
SFTMIME
-
A command-line interface for setting up and managing applications, file type associations, and desktop configuration servers managed by Application Virtualization Desktop and Terminal Services Clients.
-
-
-
SPRJ file
-
An XML-based Sequencer Project file, in which the Sequencer stores its Exclusion Items and Parse Items information. The SPRJ file is used heavily in the creation of application records as well as during an upgrade to a package.
-
-
-
virtual application
-
An application packaged by the Sequencer to run in a self-contained, virtual environment. The virtual environment contains the information necessary to run the application on the client without installing the application locally.
-
-
-
Virtual COM
-
The subsystem that manages COM objects created by application processes running in a virtual environment and prevents conflict with the same objects created outside the virtual environment.
-
-
-
virtual directory
-
An opaque directory where only files and subdirectories defined in the application package or created through interaction with an application in a virtual environment are visible. Any files in an identically named local directory are not visible to the application.
-
-
-
virtual environment
-
A runtime container that defines the resources available to application processes launched from a sequenced application package.
-
-
-
virtual file
-
A file name within the virtual environment that is mapped to an alternate target location. A virtual file appears alongside other files in the containing directory, regardless of whether that directory is virtual or local.
-
-
-
virtual file system
-
The subsystem that intercepts and redirects file system requests from application processes running in a virtual environment. These requests are processed based on the virtual files and directories defined in the application package and created or modified through interaction with a virtual application.
-
-
-
virtual registry
-
The subsystem that intercepts and redirects registry requests for keys and values from application processes running in a virtual environment. The redirection is based on the registry information defined in the application package and created or modified through interaction with a virtual application.
-
-
-
virtual services
-
The subsystem that acts as the Service Control Manager (SCM) for services running in a virtual environment.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/application-virtualization-properties-connectivity-tab.md b/mdop/appv-v4/application-virtualization-properties-connectivity-tab.md
deleted file mode 100644
index 9b480ae5f3..0000000000
--- a/mdop/appv-v4/application-virtualization-properties-connectivity-tab.md
+++ /dev/null
@@ -1,45 +0,0 @@
----
-title: Application Virtualization Properties Connectivity Tab
-description: Application Virtualization Properties Connectivity Tab
-author: dansimp
-ms.assetid: e07c1352-a2be-4d99-9968-daba515bcde2
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Application Virtualization Properties: Connectivity Tab
-
-
-Use the **Connectivity** tab of the **Application Virtualization Properties** dialog box to specify the connectivity settings.
-
-This tab contains the following elements.
-
-**Allow disconnected operation**
-Use this check box to enable or disable disconnected operation.
-
-**Limit disconnected operation to \_\_\_\_ days**
-Use this check box and field to set an expiration time-out for disconnected operation. The expiration length in days can be any number from 1–999999.
-
-**Work offline**
-Use this check box to enable and disable offline operation.
-
-## Related topics
-
-
-[Client Management Console: Application Virtualization Properties](client-management-console-application-virtualization-properties.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/application-virtualization-properties-file-system-tab.md b/mdop/appv-v4/application-virtualization-properties-file-system-tab.md
deleted file mode 100644
index fe4acb134a..0000000000
--- a/mdop/appv-v4/application-virtualization-properties-file-system-tab.md
+++ /dev/null
@@ -1,50 +0,0 @@
----
-title: Application Virtualization Properties File System Tab
-description: Application Virtualization Properties File System Tab
-author: dansimp
-ms.assetid: c7d56d36-8c50-4dfc-afee-83dea06376d4
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Application Virtualization Properties: File System Tab
-
-
-Use the **File System** tab of the **Application Virtualization Properties** dialog box to view and monitor file system settings.
-
-This tab contains the following elements.
-
-**Client Cache Configuration Settings**
-This section enables you to configure the client cache settings. Click one of the following radio buttons to choose how to manage the cache space:
-
-- **Use maximum cache size**
-
- Enter a numeric value from 100 to 1,048,576 (1 TB) in the **Maximum size (MB)** field to specify the maximum size in MB of the cache. The value shown in **Reserved Cache Size** indicates the amount of cache in use.
-
-- **Use free disk space threshold**
-
- Enter a numeric value to specify the amount of free disk space, in MB, that the cache must leave available on the disk. This allows the cache to grow until the amount of free disk space reaches this limit. The value shown in **Free disk space remaining** indicates how much disk space is unused.
-
-**Drive Letter**
-This field displays the current drive being used. To change the drive, select any drive letter from the drop-down list of available drives. This setting becomes effective when the computer is rebooted.
-
-## Related topics
-
-
-[Client Management Console: Application Virtualization Properties](client-management-console-application-virtualization-properties.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/application-virtualization-properties-general-tab.md b/mdop/appv-v4/application-virtualization-properties-general-tab.md
deleted file mode 100644
index 375209e344..0000000000
--- a/mdop/appv-v4/application-virtualization-properties-general-tab.md
+++ /dev/null
@@ -1,67 +0,0 @@
----
-title: Application Virtualization Properties General Tab
-description: Application Virtualization Properties General Tab
-author: dansimp
-ms.assetid: be7449d9-171a-4a11-9382-83b7008ccbdd
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Application Virtualization Properties: General Tab
-
-
-Use the **General** tab of the **Application Virtualization Properties** dialog box to modify log settings and data locations.
-
-This tab contains the following elements.
-
-**Log Level**
-Select the level from the drop-down list. The default level is **Information**.
-
-**Reset Log**
-Click this button to back up the current log file and immediately start a new log file.
-
-**Location**
-Enter or browse to the location where you want to save the log file sftlog.txt. The default locations are as follows:
-
-- For Windows XP, Windows Server 2003—*C:\\Documents and Settings\\All Users\\Application Data\\Microsoft\\Application Virtualization Client*
-
-- For Windows Vista, Windows 7, Windows Server 2008—*C:\\ProgramData\\Microsoft\\Application Virtualization Client*
-
-**System Log Level**
-Select the level from the drop-down list. The default level is **Warning**.
-
-**Note**
-The **System Log Level** setting controls the level of messages sent to the system event log. The logged messages are identical to the messages that get logged to the client event log, but they are stored in a different location that does not have the space limitations of the client event log. Because the system event log does not have space limitations, it is ideally suited for situations where verbose logging is necessary.
-
-
-
-**Global Data Directory**
-Enter or browse to the location of the directory of the log file. The default locations are as follows:
-
-- For Windows XP, Windows Server 2003—*C:\\Documents and Settings\\All Users\\Application Data\\Microsoft\\Application Virtualization Client*
-
-- For Windows Vista, Windows 7, Windows Server 2008—*C:\\ProgramData\\Microsoft\\Application Virtualization Client*
-
-**User Data Directory**
-Enter or browse to the location of the directory where user-specific data is stored. The default is %APPDATA%. This path must be a valid environment variable on the client computer.
-
-## Related topics
-
-
-[Client Management Console: Application Virtualization Properties](client-management-console-application-virtualization-properties.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/application-virtualization-properties-import-search-path-tab.md b/mdop/appv-v4/application-virtualization-properties-import-search-path-tab.md
deleted file mode 100644
index ada91ffa6f..0000000000
--- a/mdop/appv-v4/application-virtualization-properties-import-search-path-tab.md
+++ /dev/null
@@ -1,45 +0,0 @@
----
-title: Application Virtualization Properties Import Search Path Tab
-description: Application Virtualization Properties Import Search Path Tab
-author: dansimp
-ms.assetid: 7f94d472-1d0a-49d8-b307-330936071e13
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Application Virtualization Properties: Import Search Path Tab
-
-
-Use the **Import Search Path** tab of the **Application Virtualization Properties** dialog to view and manage the search paths for importing SFT files.
-
-This tab contains the following elements.
-
-**Path Window**
-This window displays the SFT paths.
-
-**Add** and **Remove**
-Use these buttons to add or remove SFT search paths.
-
-**Move up** and **Move Down**
-Use these buttons to organize the SFT search paths.
-
-## Related topics
-
-
-[Client Management Console: Application Virtualization Properties](client-management-console-application-virtualization-properties.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/application-virtualization-properties-interface-tab.md b/mdop/appv-v4/application-virtualization-properties-interface-tab.md
deleted file mode 100644
index fedbe93af5..0000000000
--- a/mdop/appv-v4/application-virtualization-properties-interface-tab.md
+++ /dev/null
@@ -1,45 +0,0 @@
----
-title: Application Virtualization Properties Interface Tab
-description: Application Virtualization Properties Interface Tab
-author: dansimp
-ms.assetid: bb9cb54e-315a-48bf-a396-b33e2cbd030a
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Application Virtualization Properties: Interface Tab
-
-
-Use the **Interface** tab of the **Application Virtualization Properties** dialog box to control default settings for user-interface components.
-
-This tab contains the following elements.
-
-**Run Settings** radio buttons
-Select **Always**, **Only**, or **Do not show** to determine when the Application Virtualization Client is visible in the Windows desktop notification area.
-
-**Error message display time**
-Enter a duration (in seconds) to determine how long error messages are visible in the desktop notification area. The minimum allowable value is 10.
-
-**Information message display time**
-Enter a duration (in seconds) to determine how long information messages are visible in the desktop notification area. If you set this value to zero, all messages except error messages are suppressed.
-
-## Related topics
-
-
-[Client Management Console: Application Virtualization Properties](client-management-console-application-virtualization-properties.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/application-virtualization-properties-permissions-tab.md b/mdop/appv-v4/application-virtualization-properties-permissions-tab.md
deleted file mode 100644
index b830275c12..0000000000
--- a/mdop/appv-v4/application-virtualization-properties-permissions-tab.md
+++ /dev/null
@@ -1,36 +0,0 @@
----
-title: Application Virtualization Properties Permissions Tab
-description: Application Virtualization Properties Permissions Tab
-author: dansimp
-ms.assetid: 5219bc7c-7c7a-4e2f-8fba-7039933d1124
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Application Virtualization Properties: Permissions Tab
-
-
-Use the **Permissions** tab of the **Application Virtualization Properties** dialog box to specify which activities are available for non-administrators on the local computer. Select the check boxes that correspond to the items you want to make available to all users. Users who do not have administrative rights can view this page and see which items are selected, but they cannot modify the list.
-
-## Related topics
-
-
-[Client Management Console: Application Virtualization Properties](client-management-console-application-virtualization-properties.md)
-
-[User Access Permissions in Application Virtualization Client](user-access-permissions-in-application-virtualization-client.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/application-virtualization-reference.md b/mdop/appv-v4/application-virtualization-reference.md
deleted file mode 100644
index 11b374d4e3..0000000000
--- a/mdop/appv-v4/application-virtualization-reference.md
+++ /dev/null
@@ -1,47 +0,0 @@
----
-title: Application Virtualization Reference
-description: Application Virtualization Reference
-author: dansimp
-ms.assetid: 5f994be7-41fa-416b-8a4c-6ed52fcd9b72
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Application Virtualization Reference
-
-
-This section provides reference information related to installing and managing the Microsoft Application Virtualization Client and the virtual application packages created by the Application Virtualization Sequencer.
-
-## In This Section
-
-
-[Application Virtualization Client Installer Command-Line Parameters](application-virtualization-client-installer-command-line-parameters.md)
-Provides details of all the command-line parameters that are available for use when installing the client.
-
-[SFTMIME Command Reference](sftmime--command-reference.md)
-Provides a detailed list of all SFTMIME parameters.
-
-## Related topics
-
-
-[Application Virtualization Server-Based Scenario](application-virtualization-server-based-scenario.md)
-
-[Electronic Software Distribution-Based Scenario](electronic-software-distribution-based-scenario.md)
-
-[Stand-Alone Delivery Scenario for Application Virtualization Clients](stand-alone-delivery-scenario-for-application-virtualization-clients.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/application-virtualization-report-types.md b/mdop/appv-v4/application-virtualization-report-types.md
deleted file mode 100644
index 3e81bdd8f6..0000000000
--- a/mdop/appv-v4/application-virtualization-report-types.md
+++ /dev/null
@@ -1,49 +0,0 @@
----
-title: Application Virtualization Report Types
-description: Application Virtualization Report Types
-author: dansimp
-ms.assetid: 232ef25e-11a0-49fb-b4b3-54ac83577383
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Application Virtualization Report Types
-
-
-From the Application Virtualization Server Management Console, you can generate a variety of reports that provide information about the system. This information includes usage information for applications and system error tracking.
-
-## In This Section
-
-
-[System Utilization Report](system-utilization-reportserver.md)
-Graphs the total daily usage, to help you determine the load on your Application Virtualization System.
-
-[Software Audit Report](software-audit-reportserver.md)
-Lists the usage information during the reporting period for all applications defined in the database, to help you determine which applications are the most heavily used.
-
-[Application Utilization Report](application-utilization-reportserver.md)
-Tracks usage information for a specified application, to help you determine how heavily a specific application is used.
-
-[System Error Report](system-error-reportserver.md)
-Tracks the number of errors and warnings logged over time during the specified reporting period for the specified server or for the specified server group.
-
-## Related topics
-
-
-[How to Manage Reports in the Server Management Console](how-to-manage-reports-in-the-server-management-console.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/application-virtualization-sequencer-command-line.md b/mdop/appv-v4/application-virtualization-sequencer-command-line.md
deleted file mode 100644
index abbc660844..0000000000
--- a/mdop/appv-v4/application-virtualization-sequencer-command-line.md
+++ /dev/null
@@ -1,38 +0,0 @@
----
-title: Application Virtualization Sequencer Command Line
-description: Application Virtualization Sequencer Command Line
-author: dansimp
-ms.assetid: a6d5ec9f-cc66-4869-9250-5c65d7e1e58e
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Application Virtualization Sequencer Command Line
-
-
-You can use the Microsoft Application Virtualization (App-V) Sequencer to create virtual application packages using the command line. This method of sequencing is faster than sequencing using the **Sequencing** Wizard and is ideal if you are sequencing a large number of applications.
-
-## In This Section
-
-
-[Command-Line Parameters](command-line-parameters.md)
-Provides information about the Sequencer command line parameters.
-
-[Command-Line Errors](command-line-errors.md)
-Provides information about common command line errors.
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/application-virtualization-sequencer-console-overview.md b/mdop/appv-v4/application-virtualization-sequencer-console-overview.md
deleted file mode 100644
index 1669e0fe12..0000000000
--- a/mdop/appv-v4/application-virtualization-sequencer-console-overview.md
+++ /dev/null
@@ -1,88 +0,0 @@
----
-title: Application Virtualization Sequencer Console Overview
-description: Application Virtualization Sequencer Console Overview
-author: dansimp
-ms.assetid: 681bb40d-2937-4645-82aa-4a44775232d8
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Application Virtualization Sequencer Console Overview
-
-
-The Application Virtualization (App-V) Sequencer creates applications so that they can be run in a virtual environment, as virtual applications. After an application has been sequenced, it can run from an App-V Server to target computers that are running the App-V Desktop Client or the App-V Client for Remote Desktop Services (formerly Terminal Services) by using a process called streaming. The App-V Sequencer monitors the installation and setup process for applications, and it records all the information necessary for the application to run in the virtual environment. This process also determines which files and configurations are applicable to all users and which configurations users can customize. Virtual applications run on target computers and have no effect on the operating system running on the target computer or on any applications that are installed on the target computer.
-
-## Application Virtualization Sequencer Security Considerations
-
-
-The App-V Sequencer runs all services detected at sequencing time using the Local System account and does not enforce security descriptors on service control requests. If the service was installed using a different user account or if the security descriptors are intended to grant different user groups specific service permissions, consider carefully whether the service should be virtualized. In some cases, you should install the service locally to ensure that the intended service security is preserved.
-
-## Application Virtualization Sequencer Console Menu Options
-
-
-The following menu items are available in the App-V Sequencer Console:
-
-- **File**—Contains various commands to help create, open, modify, and save sequenced applications.
-
-- **Edit**—Contains various commands for editing existing virtual applications.
-
-- **View**—Contains various commands for viewing properties of a virtual application.
-
-- **Tools**—Contains various tools and diagnostics for configuring virtual applications.
-
-## Application Virtualization Sequencer Console Toolbar Options
-
-
-The following toolbar buttons are available in the App-V Sequencer Console:
-
-- **New Package**—Click to create a new sequenced application.
-
-- **Open**—Click to open a sequenced application package in the App-V Sequencer Console.
-
-- **Open for Upgrade**—Click to open a sequenced application to upgrade or apply an update.
-
-- **Save**—Click to save a sequenced virtual application.
-
-- **Sequencing Wizard**—Click to open the Sequencing Wizard. You should use this button to start the Sequencing Wizard if you make any changes on the **General** tab under **Tools** / **Options**.
-
-## Virtual Application Tabs
-
-
-The following tabs are displayed when you view a virtual application in the App-V Sequencer Console:
-
-- **Properties**—Displays information about the selected virtual application. You can update the **Package Name** and **Comments** associated with the virtual application.
-
-- **Deployment**—Displays information about how the virtual application will be accessed by target computers. You can configure the virtual application delivery method, and you can configure which operating systems must be running on the target computer. You can also configure the associated output options. If you plan to have clients access a virtual application from a file, use the following format when specifying the path: **File://server/share/path/.sft**. Select **Enforce Security Descriptors** to preserve security associated with the package during an upgrade, or the permissions will be reset during the upgrade.
-
-- **Change History**—Displays information about updates that have been made to the virtual application.
-
-- **Files**—Displays the files associated with the selected virtual application. You can make minor revisions to the associated file properties by using the appropriate fields.
-
-- **Virtual Registry**—Displays the virtual registry associated with the selected virtual application. You can add or delete registry keys by right-clicking the appropriate entry.
-
-- **Virtual File System**—Displays the virtual file systems associated with the selected virtual application. You can add, delete, or edit file system entries on this tab by right-clicking the appropriate entry and selecting the option.
-
-- **Virtual Services**—Displays the services associated with the selected virtual application.
-
-- **OSD**—Displays information about the Open Software Descriptor (OSD) associated with the virtual application. You can update the files associated with the OSD file by right-clicking the appropriate entry and selecting the action that you want.
-
-## Related topics
-
-
-[Application Virtualization Sequencer](application-virtualization-sequencer.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/application-virtualization-sequencer-hardware-and-software-requirements.md b/mdop/appv-v4/application-virtualization-sequencer-hardware-and-software-requirements.md
deleted file mode 100644
index cc7fa3c205..0000000000
--- a/mdop/appv-v4/application-virtualization-sequencer-hardware-and-software-requirements.md
+++ /dev/null
@@ -1,282 +0,0 @@
----
-title: Application Virtualization Sequencer Hardware and Software Requirements
-description: Application Virtualization Sequencer Hardware and Software Requirements
-author: dansimp
-ms.assetid: c88a1b5b-23e1-4460-afa9-a5f37e32eb05
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Application Virtualization Sequencer Hardware and Software Requirements
-
-
-This topic describes the minimum recommended hardware and software requirements for the computer running the Microsoft Application Virtualization (App-V) Sequencer.
-
-**Important**
-You must run the App-V sequencer (**SFTSequencer.exe**) using an account that has administrator privileges because of the changes the sequencer makes to the local system. These changes can include writing files to the **C:\\Program Files** directory, making registry changes, starting and stopping services, updating security descriptors for files, and changing permissions.
-
-
-
-Before you install the Sequencer and after you sequence each application, you must restore a clean operating system image to the sequencing computer. You can use one of the following methods to restore the computer running the Sequencer:
-
-- Reformat the hard drive and reinstall the operating system.
-
-- Restore the hard drive on the computer running the Sequencer image by using another disk-imaging software.
-
-- Revert a virtual operating system image such as a Microsoft Virtual PC image. Using a virtual machine allows for clean sequencing environments to be easily reused with minimal administration.
-
-The following list outlines the recommended hardware requirements for running the App-V Sequencer.
-
-The requirements are listed first for Microsoft Application Virtualization (App-V) 4.6 SP2, followed by the requirements for versions that preceded App-V 4.6 SP2.
-
-### Hardware Requirements
-
-- Processor—Intel Pentium III, 1 GHz (32-bit or 64-bit). The sequencing process is a single-threaded process and does not take advantage of dual processors.
-
-- Memory—1 GB or above, 2 GB recommended.
-
-- Hard disk—40 gigabyte (GB) hard disk space with a minimum of 15 GB available hard disk space. We recommend that you have at least three times the hard disk space that the application you are sequencing requires.
-
- **Note**
- Sequencing requires heavy disk usage. A fast disk speed can decrease the sequencing time.
-
-
-
-### Software Requirements for App-V 4.6 SP2
-
-The following list outlines the supported operating systems for running the App-V 4.6 SP2 Sequencer.
-
-
-
-
-
-
-
-
-
-
-
Operating System
-
Edition
-
Service Pack
-
System Architecture
-
-
-
-
-
Windows XP
-
Professional
-
SP3
-
x86
-
-
-
Windows Vista
-
Business, Enterprise, or Ultimate
-
SP2
-
x86
-
-
-
Windows 7
-
Professional, Enterprise, or Ultimate
-
No service pack or SP1
-
x86 and x64
-
-
-
Windows 8
-
Pro or Enterprise Edition
-
-
x86 and x64
-
-
-
-
-
-
-**Note**
-The Application Virtualization (App-V) 4.6 SP2 Sequencer supports 32-bit and 64-bit versions of these operating systems.
-
-
-
-You should configure computers running the Sequencer with the same applications that are installed on targeted computers.
-
-### Software Requirements for Versions that Precede App-V 4.6 SP2
-
-The following list outlines the supported operating systems for running the Sequencer for versions that precede App-V 4.6 SP2.
-
-
-
-
-
-
-
-
-
-
-
Operating System
-
Edition
-
Service Pack
-
System Architecture
-
-
-
-
-
Windows XP
-
Professional
-
SP2 or SP3
-
x86
-
-
-
Windows Vista
-
Business, Enterprise, or Ultimate
-
No service pack, SP1, or SP2
-
x86
-
-
-
Windows 7¹
-
Professional, Enterprise, or Ultimate
-
-
x86
-
-
-
-
-
-
-¹Supported for App-V 4.5 with SP1 or SP2, and App-V 4.6 only
-
-**Note**
-The Application Virtualization (App-V) 4.6 Sequencer supports 32-bit and 64-bit versions of these operating systems.
-
-
-
-You should configure computers running the Sequencer with the same applications that are installed on targeted computers.
-
-### Software Requirements for Remote Desktop Services for App-V 4.6 SP2
-
-
-
-
-
-
-
-
-
-
-
Operating System
-
Edition
-
Service Pack
-
System Architecture
-
-
-
-
-
Windows Server 2003 R2
-
Standard Edition, Enterprise Edition, or Datacenter Edition
-
SP2
-
x86
-
-
-
Windows Server 2008
-
Standard, Enterprise, or Datacenter Edition
-
SP2
-
x86
-
-
-
Windows Server 2008 R2
-
Standard, Enterprise, or Datacenter Edition
-
No service pack or SP1
-
x64
-
-
-
Windows Server 2012
-
Standard, Enterprise, or Datacenter Edition
-
-
x86 or x64
-
-
-
-
-
-
-**Note**
-Application Virtualization (App-V) 4.6 SP2 for Remote Desktop Services supports 32-bit and 64-bit versions of these operating systems.
-
-
-
-### Software Requirements for Remote Desktop Services for Versions that Precede App-V 4.6 SP2
-
-
-
-
-
-
-
-
-
-
-
Operating System
-
Edition
-
Service Pack
-
System Architecture
-
-
-
-
-
Windows Server 2003
-
Standard Edition, Enterprise Edition, or Datacenter Edition
-
SP1 or SP2
-
x86
-
-
-
Windows Server 2003 R2
-
Standard Edition, Enterprise Edition, or Datacenter Edition
-
No service pack or SP2
-
x86
-
-
-
Windows Server 2008
-
Standard, Enterprise, or Datacenter Edition
-
SP1 or SP2
-
x86
-
-
-
Windows Server 2008 R2
-
Standard, Enterprise, or Datacenter Edition
-
No service pack or SP1
-
x64
-
-
-
-
-
-
-**Note**
-Application Virtualization (App-V) 4.6 SP2 for Remote Desktop Services supports 32-bit and 64-bit versions of these operating systems.
-
-
-
-## Related topics
-
-
-[Application Virtualization Client Hardware and Software Requirements](application-virtualization-client-hardware-and-software-requirements.md)
-
-[Application Virtualization System Requirements](application-virtualization-system-requirements.md)
-
-[How to Install the Application Virtualization Sequencer](how-to-install-the-application-virtualization-sequencer.md)
-
-[How to Upgrade the Application Virtualization Sequencer](how-to-upgrade-the-application-virtualization-sequencer.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/application-virtualization-sequencer-online-help.md b/mdop/appv-v4/application-virtualization-sequencer-online-help.md
deleted file mode 100644
index 3164dedaf1..0000000000
--- a/mdop/appv-v4/application-virtualization-sequencer-online-help.md
+++ /dev/null
@@ -1,43 +0,0 @@
----
-title: Application Virtualization Sequencer Online Help
-description: Application Virtualization Sequencer Online Help
-author: dansimp
-ms.assetid: 0ddeae59-314f-4c61-b85f-6b137b959fa6
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Application Virtualization Sequencer Online Help
-
-
-The Microsoft Application Virtualization (App-V) Sequencer monitors and records the installation and setup processes for software applications. Use the Sequencer to create a sequenced application that runs inside a virtual environment. The Sequencer packages the sequenced application and creates a virtual application that can be distributed to target computers and that runs in a self-contained, virtual environment. The virtual environment contains the information necessary to run the virtual application on the target computer without interacting with the operating system installed on the target computer.
-
-For more information about the App-V Sequencer, see the following topics:
-
-- [Application Virtualization Sequencer Overview](application-virtualization-sequencer-overview.md)
-
-- [Sequencer Hardware and Software Requirements](sequencer-hardware-and-software-requirements.md)
-
-- [Configuring the Application Virtualization Sequencer](configuring-the-application-virtualization-sequencer.md)
-
-- [Tasks for the Application Virtualization Sequencer](tasks-for-the-application-virtualization-sequencer.md)
-
-- [Troubleshooting the Application Virtualization Sequencer](troubleshooting-the-application-virtualization-sequencer.md)
-
-- [Application Virtualization Sequencer Technical Reference](application-virtualization-sequencer-technical-reference-keep.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/application-virtualization-sequencer-options-dialog-box.md b/mdop/appv-v4/application-virtualization-sequencer-options-dialog-box.md
deleted file mode 100644
index 894504a132..0000000000
--- a/mdop/appv-v4/application-virtualization-sequencer-options-dialog-box.md
+++ /dev/null
@@ -1,45 +0,0 @@
----
-title: Application Virtualization Sequencer Options Dialog Box
-description: Application Virtualization Sequencer Options Dialog Box
-author: dansimp
-ms.assetid: f71eda8d-8270-439f-a093-867b3a43ebff
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Application Virtualization Sequencer Options Dialog Box
-
-
-Use the **Options** dialog box to configure and view the Microsoft Application Virtualization (App-V) settings.
-
-## In This Section
-
-
-- [General Tab](general-tab-keep.md)
-
-- [Parse Items Tab](parse-items-tab-keep.md)
-
-- [Exclusion Items Tab](exclusion-items-tab-keep.md)
-
-- [Exclusion Item Dialog Box](exclusion-item-dialog-box.md)
-
-## Related topics
-
-
-[Sequencer Dialog Boxes](sequencer-dialog-boxes.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/application-virtualization-sequencer-overview.md b/mdop/appv-v4/application-virtualization-sequencer-overview.md
deleted file mode 100644
index efe77f6f0e..0000000000
--- a/mdop/appv-v4/application-virtualization-sequencer-overview.md
+++ /dev/null
@@ -1,46 +0,0 @@
----
-title: Application Virtualization Sequencer Overview
-description: Application Virtualization Sequencer Overview
-author: dansimp
-ms.assetid: e6422a28-633e-4dff-8abb-7cf6a5468112
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Application Virtualization Sequencer Overview
-
-
-The Microsoft Application Virtualization (App-V) Sequencer monitors and records all installation and setup processes for an application and creates the following files: **ICO**, **OSD**, **SFT**, and **SPRJ**. These files contain all the necessary information about an application so the application can run in a virtual environment.
-
-Click the associated link for more information about the App-V Sequencer:
-
-## In This Section
-
-
-[About the Application Virtualization Sequencer](about-the-application-virtualization-sequencer.md)
-Provides general information about the sequencer.
-
-[About the Sequencer Console](about-the-sequencer-console.md)
-Provides information about the App-V sequencer console.
-
-[About Using the Sequencer Command Line](about-using-the-sequencer-command-line.md)
-Provides information about using the command line to sequence applications.
-
-[Best Practices for the Application Virtualization Sequencer](best-practices-for-the-application-virtualization-sequencer-sp1.md)
-Provides important security-related planning information about setting up the Application Virtualization Sequencer to sequence application packages.
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/application-virtualization-sequencer-reference.md b/mdop/appv-v4/application-virtualization-sequencer-reference.md
deleted file mode 100644
index 69240cc62a..0000000000
--- a/mdop/appv-v4/application-virtualization-sequencer-reference.md
+++ /dev/null
@@ -1,46 +0,0 @@
----
-title: Application Virtualization Sequencer Reference
-description: Application Virtualization Sequencer Reference
-author: dansimp
-ms.assetid: a2aef256-98c0-4f81-83a2-af4b64208088
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Application Virtualization Sequencer Reference
-
-
-This section provides reference information related to managing the Application Virtualization (App-V) Sequencer.
-
-## In This Section
-
-
-[Log Files for the Application Virtualization Sequencer](log-files-for-the-application-virtualization-sequencer.md)
-Provides detailed information about the App-V Sequencer log files.
-
-[Sequencer Command-Line Parameters](sequencer-command-line-parameters.md)
-Provides information about parameters you can use to sequence an application and to upgrade an existing virtual application.
-
-[Sequencer Command-Line Error Codes](sequencer-command-line-error-codes.md)
-Provides a list of errors that are related to sequencing applications.
-
-## Related topics
-
-
-[Application Virtualization Sequencer](application-virtualization-sequencer.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/application-virtualization-sequencer-technical-reference-keep.md b/mdop/appv-v4/application-virtualization-sequencer-technical-reference-keep.md
deleted file mode 100644
index 36c372bd1c..0000000000
--- a/mdop/appv-v4/application-virtualization-sequencer-technical-reference-keep.md
+++ /dev/null
@@ -1,45 +0,0 @@
----
-title: Application Virtualization Sequencer Technical Reference
-description: Application Virtualization Sequencer Technical Reference
-author: dansimp
-ms.assetid: 4aa515ce-64f0-4998-8100-f87dc77aed70
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Application Virtualization Sequencer Technical Reference
-
-
-The Microsoft Application Virtualization (App-V) Sequencer Reference section contains technical information that you might find helpful as you work with the App-V Sequencer.
-
-## In This Section
-
-
-- [Sequencer Dialog Boxes](sequencer-dialog-boxes.md)
-
-- [Sequencing Wizard](sequencing-wizard.md)
-
-- [Sequencer Console](sequencer-console.md)
-
-- [Application Virtualization Sequencer Command Line](application-virtualization-sequencer-command-line.md)
-
-## Related topics
-
-
-[Application Virtualization Sequencer Online Help](application-virtualization-sequencer-online-help.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/application-virtualization-sequencer.md b/mdop/appv-v4/application-virtualization-sequencer.md
deleted file mode 100644
index 3f31f87b42..0000000000
--- a/mdop/appv-v4/application-virtualization-sequencer.md
+++ /dev/null
@@ -1,63 +0,0 @@
----
-title: Application Virtualization Sequencer
-description: Application Virtualization Sequencer
-author: dansimp
-ms.assetid: f078f3c9-7b5c-4ff1-b319-4c076b88bc39
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Application Virtualization Sequencer
-
-
-Sequencing is the process by which you create an application package using the Microsoft Application Virtualization (App-V) Sequencer. The App-V Sequencer monitors and records all installation and setup processes for an application and creates the following files: ICO, OSD, SFT, and SPRJ. These files contain all the necessary information about an application, and they allow that application to run in a virtual environment.
-
-## In This Section
-
-
-[Application Virtualization Sequencer Console Overview](application-virtualization-sequencer-console-overview.md)
-Provides information about the menu, toolbar, and tabs on the Application Virtualization Sequencer Console.
-
-[About Sequencing Phases](about-sequencing-phases.md)
-Provides information about sequencing an application.
-
-[How to Configure the App-V Sequencer](how-to-configure-the-app-v-sequencer.md)
-Provides a set of procedures you can use to configure the Application Virtualization Sequencer.
-
-[Configuring the Application Virtualization Sequencer (App-V 4.6 SP1)](configuring-the-application-virtualization-sequencer--app-v-46-sp1-.md)
-Provides a set of procedures you can use to configure the Application Virtualization Sequencer.
-
-[How to Create or Upgrade Virtual Applications Using the App-V Sequencer](how-to-create-or-upgrade-virtual-applications-using--the-app-v-sequencer.md)
-Provides step-by-step procedures for sequencing or upgrading virtual application, using either the user interface or the command line.
-
-[Tasks for the Application Virtualization Sequencer (App-V 4.6 SP1)](tasks-for-the-application-virtualization-sequencer--app-v-46-sp1-.md)
-Provides step-by-step procedures for sequencing or upgrading virtual application.
-
-[Troubleshooting Application Virtualization Sequencer Issues](troubleshooting-application-virtualization-sequencer-issues.md)
-Provides troubleshooting tips for a variety of issues that you might encounter when working with the App-V Sequencer.
-
-[Application Virtualization Sequencer Reference](application-virtualization-sequencer-reference.md)
-Provides detailed technical reference material related to working with the Application Virtualization Sequencer.
-
-## Related topics
-
-
-[Application Virtualization Client](application-virtualization-client.md)
-
-[Application Virtualization Server](application-virtualization-server.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/application-virtualization-sequencing-wizard-add-application-dialog-box.md b/mdop/appv-v4/application-virtualization-sequencing-wizard-add-application-dialog-box.md
deleted file mode 100644
index e3b9b48948..0000000000
--- a/mdop/appv-v4/application-virtualization-sequencing-wizard-add-application-dialog-box.md
+++ /dev/null
@@ -1,46 +0,0 @@
----
-title: Application Virtualization Sequencing Wizard-Add Application Dialog Box
-description: Application Virtualization Sequencing Wizard-Add Application Dialog Box
-author: dansimp
-ms.assetid: 247eac0e-830d-4d72-be48-af7d1525eefd
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Application Virtualization Sequencing Wizard-Add Application Dialog Box
-
-
-Use the **Add Application** dialog box to add an application to a sequenced application package for sequencing. This dialog box contains the following elements.
-
-**Application Path**
-Specifies the path of the application.
-
-**Name**
-Specifies the name of the application as listed in the OSD file.
-
-**Version**
-Specifies the version of the application as listed in the OSD file.
-
-**OSD File Name**
-Specifies the name of the OSD file that causes the application shortcut to open the application.
-
-## Related topics
-
-
-[Sequencer Dialog Boxes](sequencer-dialog-boxes.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/application-virtualization-sequencing-wizard-add-file-type-association-dialog-box.md b/mdop/appv-v4/application-virtualization-sequencing-wizard-add-file-type-association-dialog-box.md
deleted file mode 100644
index 7d58727b72..0000000000
--- a/mdop/appv-v4/application-virtualization-sequencing-wizard-add-file-type-association-dialog-box.md
+++ /dev/null
@@ -1,55 +0,0 @@
----
-title: Application Virtualization Sequencing Wizard-Add File Type Association Dialog Box
-description: Application Virtualization Sequencing Wizard-Add File Type Association Dialog Box
-author: dansimp
-ms.assetid: f7656053-3d92-448e-8759-b6b09cef6025
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Application Virtualization Sequencing Wizard-Add File Type Association Dialog Box
-
-
-Use the **Add File Type Association** dialog box to add a file type association for the application. To access this dialog box, click **File Type** associations on the **Configure Application** page and click **Add**. This dialog box contains the following elements.
-
-**Extension**
-Use to specify the file name extension for the file type associated with the application.
-
-**File Type Description**
-Use to specify a brief description of the file type.
-
-**Content Type**
-Use to specify a brief description of the MIME type.
-
-**Perceived Type**
-Use to select a file type.
-
-**Confirm open after download**
-Select to confirm that the file is opened after a download.
-
-**Always show extension**
-Select to display the extension with the file name.
-
-**Add to New menu**
-Select to add the file type to the **New** menu.
-
-## Related topics
-
-
-[Sequencer Dialog Boxes](sequencer-dialog-boxes.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/application-virtualization-sequencing-wizard-add-files-to-virtual-file-system-page.md b/mdop/appv-v4/application-virtualization-sequencing-wizard-add-files-to-virtual-file-system-page.md
deleted file mode 100644
index 1a7aceec55..0000000000
--- a/mdop/appv-v4/application-virtualization-sequencing-wizard-add-files-to-virtual-file-system-page.md
+++ /dev/null
@@ -1,79 +0,0 @@
----
-title: Application Virtualization Sequencing Wizard Add Files to Virtual File System Page
-description: Application Virtualization Sequencing Wizard Add Files to Virtual File System Page
-author: dansimp
-ms.assetid: 6b01333b-08bd-4b96-a123-a07a7aafddd1
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Application Virtualization Sequencing Wizard Add Files to Virtual File System Page
-
-
-Use the **Add Files to Virtual File System** page of the Application Virtualization Sequencing Wizard to select files to add to the virtual file system. The page contains the elements described in the following table.
-
-
-
-
-
-
-
-
-
Name
-
Description
-
-
-
-
-
Add the following files to the VFS
-
Select to add the listed files to the virtual file system.
-
-
-
Remove
-
Click to remove a selected file from the list so that it will not be added to the virtual file system.
-
-
-
Add
-
Click to add a file so that you can add a file to the virtual file system.
-
-
-
Reset
-
Click to restore the default list of files under Add the following files to the VFS.
-
-
-
Back
-
Accesses the Sequencing Wizard's previous page.
-
-
-
Next
-
Accesses the Sequencing Wizard's next page.
-
-
-
Cancel
-
Terminates operation of the Sequencing Wizard.
-
-
-
-
-
-
-## Related topics
-
-
-[Sequencing Wizard](sequencing-wizard.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/application-virtualization-sequencing-wizard-advanced-options-page.md b/mdop/appv-v4/application-virtualization-sequencing-wizard-advanced-options-page.md
deleted file mode 100644
index c195624f90..0000000000
--- a/mdop/appv-v4/application-virtualization-sequencing-wizard-advanced-options-page.md
+++ /dev/null
@@ -1,130 +0,0 @@
----
-title: Application Virtualization Sequencing Wizard Advanced Options Page
-description: Application Virtualization Sequencing Wizard Advanced Options Page
-author: dansimp
-ms.assetid: 2c4c5d95-d55e-463d-a851-8486f6a724f2
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Application Virtualization Sequencing Wizard Advanced Options Page
-
-
-Use the **Advanced Options** page of the Application Virtualization (App-V) Sequencing Wizard to specify advanced options for the application to be installed. The page contains the elements described in the following table.
-
-
-
-
-
-
-
-
-
Name
-
Description
-
-
-
-
-
Block Size
-
Use to specify the size of blocks that the SFT file will be divided into when streamed across a network. All blocks equal the specified size; however, the last block might be smaller than specified. Select one of the following values:
-
-
4 KB
-
16 KB
-
32 KB
-
64 KB
-
-
-Note
When you select a block size, consider the size of the SFT file and your network bandwidth. A file with a smaller block size takes longer to stream over the network but is less bandwidth-intensive. Files with larger block sizes might stream faster, but they use more network bandwidth. Through experimentation, you can discover the optimum block size for streaming applications on your network.
-
-
-
-
-
-
-
Enable Microsoft Update During Monitoring
-
Enables installation of Microsoft Updates during the Sequencing Wizard's monitoring phase.
-
-
-
Rebase DLLs
-
Enables remapping of supported dynamic-link libraries to a contiguous space in RAM, saving memory and improving performance.
-
-
-
Back
-
Accesses the Sequencing Wizard's previous page.
-
-
-
Next
-
Accesses the Sequencing Wizard's next page.
-
-
-
Cancel
-
Terminates operation of the Sequencing Wizard.
-
-
-
-
-
-
-\[Template Token Value\]
-
-Use the **Advanced Options** page of the App-V Sequencing Wizard to specify advanced options for the application you are sequencing. This page contains the elements described in the following table.
-
-
-
-
-
-
-
-
-
Name
-
Description
-
-
-
-
-
Allow Microsoft Update to run during monitoring
-
Specifies whether software updates will be applied to the application during the monitoring phase of application sequencing. This option is helpful if updates are required to successfully complete the application installation. This option is not selected by default.
-
-
-
Rebase Dlls
-
Enables remapping of supported dynamic-link libraries to a contiguous space in RAM. Selecting this option can help manage memory and improve application performance. This option is not selected by default.
-
-
-
Back
-
Goes to the previous page of the wizard.
-
-
-
Next
-
Goes to the next page of the wizard.
-
-
-
Cancel
-
Discards the settings and exits the wizard.
-
-
-
-
-
-
-\[Template Token Value\]
-
-## Related topics
-
-
-[Sequencing Wizard](sequencing-wizard.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/application-virtualization-sequencing-wizard-configure-application-page-keep.md b/mdop/appv-v4/application-virtualization-sequencing-wizard-configure-application-page-keep.md
deleted file mode 100644
index 0fa1b9ca03..0000000000
--- a/mdop/appv-v4/application-virtualization-sequencing-wizard-configure-application-page-keep.md
+++ /dev/null
@@ -1,91 +0,0 @@
----
-title: Application Virtualization Sequencing Wizard Configure Application Page
-description: Application Virtualization Sequencing Wizard Configure Application Page
-author: dansimp
-ms.assetid: 2927debd-de4b-41d2-9e1c-e8927231f4cc
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Application Virtualization Sequencing Wizard Configure Application Page
-
-
-Use the **Configure Applications** page of the App-V Sequencing Wizard to add applications to a sequenced application package and to add or delete shortcuts and file type associations. The page contains the elements described in the following table.
-
-
-
-
-
-
-
-
-
Name
-
Description
-
-
-
-
-
Application
-
Displays a list of applications, which can be expanded to add or edit file type associations.
-
-
-
Name
-
Displays the name of the application you are sequencing.
-
-
-
Version
-
Displays the version number for the application you are sequencing.
-
-
-
Command Line
-
Displays any command-line directive of the application you are sequencing.
-
-
-
Add
-
Adds a selected application to a package.
-
-
-
Remove
-
Deletes a selected application from a package.
-
-
-
Edit
-
Enables editing of the application path and OSD file properties of the selected application.
-
-
-
Back
-
Goes to the previous page of the wizard.
-
-
-
Next
-
Goes to the next page of the wizard
-
-
-
Cancel
-
Discards the settings and closes the wizard.
-
-
-
-
-
-
-## Related topics
-
-
-[Sequencing Wizard](sequencing-wizard.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/application-virtualization-sequencing-wizard-launch-applications-page.md b/mdop/appv-v4/application-virtualization-sequencing-wizard-launch-applications-page.md
deleted file mode 100644
index 995ae0facc..0000000000
--- a/mdop/appv-v4/application-virtualization-sequencing-wizard-launch-applications-page.md
+++ /dev/null
@@ -1,79 +0,0 @@
----
-title: Application Virtualization Sequencing Wizard Launch Applications Page
-description: Application Virtualization Sequencing Wizard Launch Applications Page
-author: dansimp
-ms.assetid: 69b1d6e1-00ff-49e3-a245-a4aca225d681
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Application Virtualization Sequencing Wizard Launch Applications Page
-
-
-Use the **Launch Applications** page of the App-V sequencing wizard to run applications so that the Sequencer can optimize the package for streaming and you can configure how the application should be initially started on target computers. The page contains the elements described in the following table.
-
-
-
-
-
-
-
-
-
Name
-
Description
-
-
-
-
-
Name
-
Displays the name of application you are sequencing.
-
-
-
Command Line
-
Displays any command-line directive for the application you are sequencing.
-
-
-
Launch All
-
Starts each application displayed, exercises each application sufficiently to cover the actions that users typically take immediately after they open the application, and then exits each application.
-
-
-
Launch
-
Starts a selected application and exercises the application sufficiently to cover the actions that users typically take immediately after they open the application.
-
-
-
Back
-
Goes to the previous page of the wizard.
-
-
-
Next
-
Goes to the next page of the wizard.
-
-
-
Cancel
-
Discards the settings and closes the wizard.
-
-
-
-
-
-
-## Related topics
-
-
-[Sequencing Wizard](sequencing-wizard.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/application-virtualization-sequencing-wizard-monitor-installation-page.md b/mdop/appv-v4/application-virtualization-sequencing-wizard-monitor-installation-page.md
deleted file mode 100644
index 8f834f6d26..0000000000
--- a/mdop/appv-v4/application-virtualization-sequencing-wizard-monitor-installation-page.md
+++ /dev/null
@@ -1,126 +0,0 @@
----
-title: Application Virtualization Sequencing Wizard Monitor Installation Page
-description: Application Virtualization Sequencing Wizard Monitor Installation Page
-author: dansimp
-ms.assetid: b54b8145-a57e-4d0d-b776-b5319aadb78e
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Application Virtualization Sequencing Wizard Monitor Installation Page
-
-
-Use the **Monitor Installation** page of the Application Virtualization Sequencing Wizard to start the sequencing process so that the Sequencer can monitor the application installation activities. The page contains the elements described in the following table.
-
-
-
-
-
-
-
-
-
Name
-
Description
-
-
-
-
-
Begin Monitoring
-
Starts the monitoring of the sequencing process.
-
-Note
The Sequencer will minimize so that you can run your application's installer, except on Vista.
-
-
-
-
-
-
-
Stop Monitoring
-
Stops the monitoring of the sequencing process.
-
-Note
The Stop Monitoring button is displayed only after the monitoring process starts.
-
-
-
-
-
-
-
Back
-
Accesses the Sequencing Wizard's previous page.
-
-
-
Next
-
Accesses the Sequencing Wizard's next page.
-
-
-
Cancel
-
Terminates operation of the Sequencing Wizard.
-
-
-
-
-
-
-\[Template Token Value\]
-
-Use the **Monitor Installation** page of the App-V sequencing wizard to monitor the installation of an application. The page contains the elements described in the following table.
-
-
-
-
-
-
-
-
-
Name
-
Description
-
-
-
-
-
Begin Monitoring
-
Starts the monitoring of the application installation by the sequencer. This option enables the sequencer to record the installation process. After you click Start Monitoring, you must wait while sequencer prepares the computer for sequencing. All new and changed application components will be added to the virtual application package.
-
-
-
Stop Monitoring
-
Stops the sequencer from recording the installation process. This button is not available until you click Begin Monitoring.
-
-
-
Back
-
Goes to the previous page of the wizard.
-
-
-
Next
-
Goes to the next page of the wizard.
-
-
-
Cancel
-
Discards the settings and closes the wizard.
-
-
-
-
-
-
-\[Template Token Value\]
-
-## Related topics
-
-
-[Sequencing Wizard](sequencing-wizard.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/application-virtualization-sequencing-wizard-package-information-page-keep.md b/mdop/appv-v4/application-virtualization-sequencing-wizard-package-information-page-keep.md
deleted file mode 100644
index 996fff81b1..0000000000
--- a/mdop/appv-v4/application-virtualization-sequencing-wizard-package-information-page-keep.md
+++ /dev/null
@@ -1,71 +0,0 @@
----
-title: Application Virtualization Sequencing Wizard Package Information Page
-description: Application Virtualization Sequencing Wizard Package Information Page
-author: dansimp
-ms.assetid: e52efd08-1b05-4bd6-a6e7-5f6bdbde7df7
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Application Virtualization Sequencing Wizard Package Information Page
-
-
-Use the **Package Information** page of the Application Virtualization (App-V) wizard to specify information that will be associated with the application you sequence. This page contains the following elements.
-
-
-
-
-
-
-
-
-
Name
-
Description
-
-
-
-
-
Package Name
-
Specifies the name that will be associated with the virtual application package. This is a required field.
-
-
-
Comments
-
Specifies identifying information that will be associated with the package. The information will be added to OSD file ABSTRACT element. This field is optional.
-
-
-
Show Advanced Monitoring Options
-
Displays the Advanced Options page of the Sequencing Wizard.
-
-
-
Next
-
Goes to the next page of the wizard.
-
-
-
Cancel
-
Discards the settings and exits the wizard.
-
-
-
-
-
-
-## Related topics
-
-
-[Sequencing Wizard](sequencing-wizard.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/application-virtualization-sequencing-wizard-sequence-package-page.md b/mdop/appv-v4/application-virtualization-sequencing-wizard-sequence-package-page.md
deleted file mode 100644
index 6a9437812a..0000000000
--- a/mdop/appv-v4/application-virtualization-sequencing-wizard-sequence-package-page.md
+++ /dev/null
@@ -1,55 +0,0 @@
----
-title: Application Virtualization Sequencing Wizard Sequence Package Page
-description: Application Virtualization Sequencing Wizard Sequence Package Page
-author: dansimp
-ms.assetid: 4c603d6a-9139-4867-a085-c6d6b517917e
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Application Virtualization Sequencing Wizard Sequence Package Page
-
-
-Use the **Sequence Package** page of the Application Virtualization Sequencing Wizard to create the sequenced package. After you click **Finish**, save the application by clicking **File / Save** in the Sequencer console. This page contains the elements described in the following table.
-
-
-
-
-
-
-
-
-
Name
-
Description
-
-
-
-
-
Finish
-
Closes the Sequencing Wizard and displays the virtual application package in the Sequence console.
-
-
-
-
-
-
-## Related topics
-
-
-[Sequencing Wizard](sequencing-wizard.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/application-virtualization-sequencing-wizard-shortcut-locations-dialog-box.md b/mdop/appv-v4/application-virtualization-sequencing-wizard-shortcut-locations-dialog-box.md
deleted file mode 100644
index 87689f417f..0000000000
--- a/mdop/appv-v4/application-virtualization-sequencing-wizard-shortcut-locations-dialog-box.md
+++ /dev/null
@@ -1,49 +0,0 @@
----
-title: Application Virtualization Sequencing Wizard-Shortcut Locations Dialog Box
-description: Application Virtualization Sequencing Wizard-Shortcut Locations Dialog Box
-author: dansimp
-ms.assetid: d79d7085-228e-4be2-abe6-2760b9b983d5
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Application Virtualization Sequencing Wizard-Shortcut Locations Dialog Box
-
-
-Use the **Shortcut Locations** dialog box to specify where to publish application shortcuts on the Application Virtualization Desktop Client. This dialog box is found on the **Configure Applications** page of the Sequencing Wizard and contains the following elements.
-
-**Desktop**
-Select to publish the application shortcut to the Application Virtualization Desktop Client.
-
-**Send To Menu**
-Select to publish the application shortcut to the **Send To** menu.
-
-**Quick Launch Toolbar**
-Select to publish the application shortcut to the Quick Launch toolbar.
-
-**Start Menu**
-Select to publish the application shortcuts to a designated subfolder of the **Start** menu.
-
-**Advanced**
-Click to publish application shortcuts to additional locations.
-
-## Related topics
-
-
-[Sequencer Dialog Boxes](sequencer-dialog-boxes.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/application-virtualization-server-based-scenario-overview.md b/mdop/appv-v4/application-virtualization-server-based-scenario-overview.md
deleted file mode 100644
index 8a53cc64f2..0000000000
--- a/mdop/appv-v4/application-virtualization-server-based-scenario-overview.md
+++ /dev/null
@@ -1,178 +0,0 @@
----
-title: Application Virtualization Server-Based Scenario Overview
-description: Application Virtualization Server-Based Scenario Overview
-author: dansimp
-ms.assetid: 2d91392b-5085-4a5d-94f2-15eed1ed2928
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Application Virtualization Server-Based Scenario Overview
-
-
-If you plan to use a server-based deployment scenario for your Microsoft Application Virtualization environment, it is important to understand the differences between the *Application Virtualization Management Server* and the *Application Virtualization Streaming Server*. This topic describes those differences and also provides information about package delivery methods, transmission protocols, and external components that you will need to consider as you proceed with your deployment.
-
-## Application Virtualization Management Server
-
-
-The Application Virtualization Management Server performs both the publishing function and the streaming function. The server publishes application icons, shortcuts, and file type associations to the App-V clients for authorized users. When user requests for applications are received the server streams that data on-demand to authorized users using RTSP or RTSPS protocols. In most configurations using this server, one or more Management Servers share a common data store for configuration and package information.
-
-The Application Virtualization Management Servers use Active Directory groups to manage user authorization. In addition to Active Directory Domain Services, these servers have SQL Server installed to manage the database and data store. The Management Server is controlled through the Application Virtualization Management Console, a snap-in to the Microsoft Management Console.
-
-Because the Application Virtualization Management Servers stream applications to end-users on demand, these servers are ideally suited for system configurations that have reliable, high-bandwidth LANs.
-
-## Application Virtualization Streaming Server
-
-
-The Application Virtualization Streaming Server delivers the same streaming and package upgrade capabilities provided by the Management Server, but without its Active Directory or SQL Server requirements. However, the Streaming Server does not have a publishing service, nor does it have licensing or metering capabilities. The publishing service of a separate App-V Management Server is used in conjunction with the App-V Streaming Server. The App-V Streaming Server addresses the needs of businesses that want to use Application Virtualization in multiple locations with the streaming capabilities of the classic server configuration but might not have the infrastructure to support App-V Management Servers in every location.
-
-The Application Virtualization Streaming Server can also be used in environments with an existing electronic software distribution system (ESD). You use the ESD to manage streaming applications. Unlike the Application Virtualization Management Server, the Streaming Server does not use SQL or a management console. These servers use access control lists (ACLs) to grant user authorization.
-
-## Package Delivery Methods
-
-
-If you plan to use an Application Virtualization Server as the publishing delivery method, you need to determine which of the following package delivery methods your scenario employs:
-
-- *Dynamic package delivery*
-
-- *Load from file package delivery*
-
-### Dynamic Package Delivery
-
-During dynamic package delivery, the server (Application Virtualization Management Server, Application Virtualization Streaming Server, or IIS server) delivers the virtualized applications to the end users through on-demand deployment. The server delivers the virtualized applications and packages to a client computer only when a user first attempts to launch an application (on demand). The server streams only the blocks needed to start the application (primary feature block). After the primary feature block is delivered to the client, the application runs; the client does not receive the complete application (incremental deployment) unless the client needs access to a part of the application that is not included in the primary feature block. When this occurs, the client performs an out-of-sequence request and the secondary feature block is streamed to the client. Dynamic package delivery allows for rapid application launch.
-
-### Load from File Package Delivery
-
-For load from file package delivery, the server delivers the entire virtualized application package to a client computer before the user launches the application. In this scenario, virtualized applications are delivered as a full package, rather than through the dynamic, incremental method used by the dynamic delivery model.
-
-**Note**
-For each delivery method, the initial virtual application delivery process and the virtual application update process are the same; the updated virtual application package replaces the original application package.
-
-
-
-The following table compares the advantages and disadvantages of each package delivery method.
-
-
-
-
-
-
-
-
-
-
-
Method
-
Advantages
-
Disadvantages
-
Comments
-
-
-
-
-
Dynamic package delivery
-
Applications are delivered and updated on demand.
-
Applications are delivered and updated incrementally to optimize launch time.
-
Updates are delivered automatically to the client desktop.
-
Larger footprint in enterprise topology because of server requirements.
-
Application streaming should be over a LAN; deployment scenarios over a WAN or that use an unreliable or intermittent connection between the server and client might be unusable.
-
Requires a streaming infrastructure.
-
Windows Installer used to deploy Application Virtualization Desktop Client software to end-user computers.
-
Large enterprises should use Application Virtualization Streaming Servers as distribution points.
-
-
-
Load from file package delivery
-
Consistent with typical enterprise management practices.
-
Supports stand-alone configuration scenario.
-
Provides solution to micro–branch office problem.
-
Application delivery and update is not possible on-demand.
-
Application delivery and update is not incremental; it increases resource consumption relative to dynamic delivery.
-
The IT organization is often responsible for managing application licenses, user authorization, and authentication.
-
-
-
-
-
-
-## Server-Related Protocols and External Components
-
-
-The following table lists the server types that can be used in an Application Virtualization Server-based scenarios, along with their corresponding transmission protocols and the external components needed to support the specific server configuration. The table also includes the reporting mechanism and the active upgrade mechanism for each server type. Because these scenarios all use the Application Virtualization Management Server, you can use the internal reporting functionality that is built into the system. If you use an Application Virtualization Management or an Application Virtualization Streaming Server to deliver packages to the client, packages on the server are automatically upgraded when a user logs into the client; if you use IIS servers or a file to deliver the packages to the client, the packages on the client must be upgraded manually.
-
-
-
-
-
-
-
-
-
-
-
-
Server Type
-
Protocols
-
External Components Needed
-
Reporting
-
Active Upgrade
-
-
-
-
-
Application Virtualization Management Server
-
RTSP
-
RTSPS
-
When using HTTPS, use an IIS server to download ICO and OSD files and a firewall to protect the server from exposure to the Internet.
-
Internal
-
Supported
-
-
-
Application Virtualization Streaming Server
-
RTSP
-
RTSPS
-
Use a mechanism to synchronize the content between the Management Server and the Streaming Server. When using HTTPS, use an IIS server to download ICO and OSD files and use a firewall to protect the server from exposure to the Internet.
-
Internal
-
Supported
-
-
-
IIS server
-
HTTP
-
HTTPS
-
Use a mechanism to synchronize the content between the Management Server and the Streaming Server. When using HTTP or HTTPS, use an IIS server to download ICO and OSD files and a firewall to protect the server from exposure to the Internet.
-
Internal
-
Not Supported
-
-
-
File
-
SMB
-
You need a way to synchronize the content between the Management Server and the Streaming Server. You need a client computer with file sharing or streaming capability.
-
Internal
-
Not Supported
-
-
-
-
-
-
-## Related topics
-
-
-[Electronic Software Distribution-Based Scenario](electronic-software-distribution-based-scenario.md)
-
-[How to Configure Servers for Server-Based Deployment](how-to-configure-servers-for-server-based-deployment.md)
-
-[How to Install the Servers and System Components](how-to-install-the-servers-and-system-components.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/application-virtualization-server-based-scenario.md b/mdop/appv-v4/application-virtualization-server-based-scenario.md
deleted file mode 100644
index 84336dad16..0000000000
--- a/mdop/appv-v4/application-virtualization-server-based-scenario.md
+++ /dev/null
@@ -1,67 +0,0 @@
----
-title: Application Virtualization Server-Based Scenario
-description: Application Virtualization Server-Based Scenario
-author: dansimp
-ms.assetid: 10ed0b18-087d-470f-951b-5083f4cb076f
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Application Virtualization Server-Based Scenario
-
-
-If you plan to use a server-based deployment scenario for your Microsoft Application Virtualization (App-V) environment, you should understand the differences between the Application Virtualization Management Server and the Application Virtualization Streaming Server. The topics in this section describe those differences and also provide information about package delivery methods, transmission protocols, and external components that you have to consider as you continue with your deployment. This section also provides step-by-step procedures for installing and configuring the App-V Management Server and the Application Virtualization Streaming Servers.
-
-## In This Section
-
-
-[Application Virtualization Server-Based Scenario Overview](application-virtualization-server-based-scenario-overview.md)
-Provides important deployment information about the Application Virtualization Management Server, the Application Virtualization Streaming Server, and the package delivery methods, protocols, and external components relevant to your server-based deployment plan.
-
-[How to Install the Servers and System Components](how-to-install-the-servers-and-system-components.md)
-Describes how to install the Microsoft Application Virtualization platform components required for your server-based deployment.
-
-[How to Configure Servers for Server-Based Deployment](how-to-configure-servers-for-server-based-deployment.md)
-Describes how to configure the Application Virtualization Management Server, the Application Virtualization Streaming Server, the Internet Information Integration (IIS) server, and the file server.
-
-[How to Configure a Read-only Cache on the App-V Client (VDI)](how-to-configure-a-read-only-cache-on-the-app-v-client--vdi-.md)
-Describes how to configure the App-V client to use read-only cache.
-
-[How to Configure a Read-only Cache on the App-V Client (RDS)](how-to-configure-a-read-only-cache-on-the-app-v-client--rds--sp1.md)
-Describes how to configure the App-V client to use read-only cache.
-
-[How to Configure Microsoft SQL Server Mirroring Support for App-V](how-to-configure-microsoft-sql-server-mirroring-support-for-app-v.md)
-Describes how to configure database mirroring by using Microsoft SQL Server for your App-V system.
-
-## Reference
-
-
-[Application Virtualization Client Installer Command-Line Parameters](application-virtualization-client-installer-command-line-parameters.md)
-
-## Related Sections
-
-
-[Electronic Software Distribution-Based Scenario](electronic-software-distribution-based-scenario.md)
-
-## Related topics
-
-
-[Application Virtualization Deployment and Upgrade Considerations](application-virtualization-deployment-and-upgrade-considerations.md)
-
-[Stand-Alone Delivery Scenario for Application Virtualization Clients](stand-alone-delivery-scenario-for-application-virtualization-clients.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/application-virtualization-server-management-console-reference.md b/mdop/appv-v4/application-virtualization-server-management-console-reference.md
deleted file mode 100644
index c36cd7f3fd..0000000000
--- a/mdop/appv-v4/application-virtualization-server-management-console-reference.md
+++ /dev/null
@@ -1,69 +0,0 @@
----
-title: Application Virtualization Server Management Console Reference
-description: Application Virtualization Server Management Console Reference
-author: dansimp
-ms.assetid: 7c9890f4-7230-44dd-bbe8-95a4b65dc796
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Application Virtualization Server Management Console Reference
-
-
-This section of the Application Virtualization Server Management Console Help provides detailed information about each of the functional areas of the interface.
-
-## In This Section
-
-
-[Server Management Console: About Dialog Boxes](server-management-console-about-dialog-boxes.md)
-Describes the available **About** dialog boxes and how to view them.
-
-[Server Management Console: Application Virtualization System Node](server-management-console-application-virtualization-system-node.md)
-Describes the screens in the Application Virtualization System node.
-
-[Server Management Console: Applications Node](server-management-console-applications-node.md)
-Describes the screens in the **Applications** node.
-
-[Server Management Console: File Type Associations Node](server-management-console-file-type-associations-node.md)
-Describes the screens in the **File Type Association** node.
-
-[Server Management Console: Packages Node](server-management-console-packages-node.md)
-Describes the screens in the **Packages** node.
-
-[Server Management Console: Application Licenses Node](server-management-console-application-licenses-node.md)
-Describes the screens in the **Application Licenses** node.
-
-[Server Management Console: Server Groups Node](server-management-console-server-groups-node.md)
-Describes the screens in the **Server Groups** node.
-
-[Server Management Console: Provider Policies Node](server-management-console-provider-policies-node.md)
-Describes the screens in the **Provider Policies** node.
-
-[Server Management Console: Administrators Node](server-management-console-administrators-node.md)
-Describes the screens in the **Administrators** node.
-
-[Server Management Console: Reports Node](server-management-console-reports-node.md)
-Describes the screens in the **Reports** node.
-
-## Related topics
-
-
-[About the Application Virtualization Server Management Console](about-the-application-virtualization-server-management-console.md)
-
-[How to Perform Administrative Tasks in the Application Virtualization Server Management Console](how-to-perform-administrative-tasks-in-the-application-virtualization-server-management-console.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/application-virtualization-server-management-help.md b/mdop/appv-v4/application-virtualization-server-management-help.md
deleted file mode 100644
index 7ae7b3aab4..0000000000
--- a/mdop/appv-v4/application-virtualization-server-management-help.md
+++ /dev/null
@@ -1,41 +0,0 @@
----
-title: Application Virtualization Server Management Help
-description: Application Virtualization Server Management Help
-author: dansimp
-ms.assetid: 4f67265c-58f5-4d77-bfff-95474d8f1bb6
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Application Virtualization Server Management Help
-
-
-This help file supports the Application Virtualization Management Server.
-
-## In This Section
-
-
-[About the Application Virtualization Server Management Console](about-the-application-virtualization-server-management-console.md)
-Includes overview information about the Application Virtualization Management Server.
-
-[How to Perform Administrative Tasks in the Application Virtualization Server Management Console](how-to-perform-administrative-tasks-in-the-application-virtualization-server-management-console.md)
-Includes an overview as well as step-by-step procedures for using the features and commands that are available in the Application Virtualization Server.
-
-[Application Virtualization Server Management Console Reference](application-virtualization-server-management-console-reference.md)
-Includes reference information about the windows and dialogs that are available in the Application Virtualization Server Management Console.
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/application-virtualization-server.md b/mdop/appv-v4/application-virtualization-server.md
deleted file mode 100644
index db3ac34238..0000000000
--- a/mdop/appv-v4/application-virtualization-server.md
+++ /dev/null
@@ -1,57 +0,0 @@
----
-title: Application Virtualization Server
-description: Application Virtualization Server
-author: dansimp
-ms.assetid: feea99b2-5e3d-42b1-ad41-157429e5fceb
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Application Virtualization Server
-
-
-This section provides important information and procedures that you can use to configure and manage the Microsoft Application Virtualization (App-V) Servers.
-
-## In This Section
-
-
-[Monitoring Application Virtualization Servers](monitoring-application-virtualization-servers.md)
-Provides information about monitoring the App-V Servers.
-
-[How to Load Files and Packages](how-to-load-files-and-packages.md)
-Provides information about loading files and packages.
-
-[How to Perform Administrative Tasks in the Application Virtualization Server Management Console](how-to-perform-administrative-tasks-in-the-application-virtualization-server-management-console.md)
-Provides detailed procedures for managing the App-V Servers by using the Server Management Console.
-
-[How to Configure the App-V System for Package Upgrade](how-to-configure-the-app-v-system-for-package-upgrade.md)
-Provides detailed information about upgrading packages in different scenarios.
-
-[Troubleshooting Information for the Application Virtualization Server](troubleshooting-information-for-the-application-virtualization-server.md)
-Provides information that you can use to troubleshoot various issues on the Application Virtualization (App-V) Server.
-
-[How to Migrate the App-V SQL Database to a Different SQL Server](how-to-migrate-the-app-v-sql-database-to-a-different-sql-server.md)
-Provides detailed procedures for migrating the App-V SQL Database to a different SQL Server.
-
-## Related topics
-
-
-[Application Virtualization Client](application-virtualization-client.md)
-
-[Application Virtualization Sequencer](application-virtualization-sequencer.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/application-virtualization-system-requirements.md b/mdop/appv-v4/application-virtualization-system-requirements.md
deleted file mode 100644
index d912bfff73..0000000000
--- a/mdop/appv-v4/application-virtualization-system-requirements.md
+++ /dev/null
@@ -1,363 +0,0 @@
----
-title: Application Virtualization System Requirements
-description: Application Virtualization System Requirements
-author: dansimp
-ms.assetid: a2798dd9-168e-45eb-8103-e12e128fae7c
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Application Virtualization System Requirements
-
-
-This topic describes the minimum hardware and software requirements for the Microsoft Application Virtualization (App-V) Management Server and Streaming Server.
-
-## Application Virtualization Management and Streaming Servers
-
-
-The following list includes the minimum recommended hardware and software requirements for the App-V Management Server and App-V Streaming Server.
-
-### Hardware Requirements
-
-- Processor—Intel Pentium III, 1 GHz
-
-- RAM—512 MB
-
-- Disk space—200 MB available hard disk space, not including the Content directory
-
-### Software Requirements
-
-
-
-
-
-
-
-
-
-
-
Operating System
-
Edition
-
Service Pack
-
System Architecture
-
-
-
-
-
Windows Server 2003
-
Standard Edition
-
SP1 or SP2
-
x86 or x64
-
-
-
Windows Server 2003
-
Enterprise Edition or Datacenter Edition
-
SP1 or SP2
-
x86 or x64
-
-
-
Windows Server 2003 R2
-
Standard Edition
-
No service pack or SP2
-
x86 or x64
-
-
-
Windows Server 2003 R2
-
Enterprise Edition or Datacenter Edition
-
No service pack or SP2
-
x86 or x64
-
-
-
Windows Server 2008
-
Standard, Enterprise, or Datacenter Edition
-
SP1 or SP2
-
x86 or x64
-
-
-
Windows Server 2008 R2¹
-
Standard, Enterprise, or Datacenter Edition
-
-
x64
-
-
-
-
-
-
-¹Applies to App-V 4.5 SP1 and SP2 only.
-
-## Data Store
-
-
-The following list includes the minimum recommended hardware and software requirements for the computer that is used when you install the data store on a separate server. The data store is required only for the Application Virtualization Management Server.
-
-### Hardware Requirements
-
-- Processor—Intel Pentium III, 850 MHz
-
-- RAM—512 MB
-
-- Disk space—200 MB available hard disk space
-
-### Software Requirements
-
-
-
-
-
-
-
-
-
-
-
Operating System
-
Edition
-
Service Pack
-
System Architecture
-
-
-
-
-
Windows Server 2003
-
Standard Edition
-
SP1 or SP2
-
x86 or x64
-
-
-
Windows Server 2003
-
Enterprise Edition or Datacenter Edition
-
SP1 or SP2
-
x86 or x64
-
-
-
Windows Server 2003 R2
-
Standard Edition
-
No service pack or SP2
-
x86 or x64
-
-
-
Windows Server 2003 R2
-
Enterprise Edition or Datacenter Edition
-
No service pack or SP2
-
x86 or x64
-
-
-
Windows Server 2008
-
Standard, Enterprise, or Datacenter Edition
-
SP1 or SP2
-
x86 or x64
-
-
-
Windows Server 2008 R2¹
-
Standard, Enterprise, or Datacenter Edition
-
-
x64
-
-
-
-
-
-
-¹Applies to App-V 4.5 SP1 and SP2 only.
-
-- Database—Microsoft SQL Server 2000 SP3a or SP4, SQL Server 2005 SP1, SP2, or SP3, or SQL Server 2008, no service pack or SP1 or SQL Server 2008 R2 (32-bit or 64-bit)
-
-- Microsoft Data Access Components—MDAC 2.7
-
-- Domain controller—Active Directory Domain Services or Windows NT 4.0-based primary domain controller (PDC) as the central authentication authority
-
-## Management Web Service
-
-
-The following list includes the minimum recommended hardware and software requirements for the Application Virtualization Management Web Service when it is installed on a separate computer.
-
-### Hardware Requirements
-
-- Processor—Intel Pentium III, 800 MHz
-
-- RAM—256 MB
-
-- Disk space—50 MB available hard disk space
-
-### Software Requirements
-
-
-
-
-
-
-
-
-
-
-
Operating System
-
Edition
-
Service Pack
-
System Architecture
-
-
-
-
-
Windows Server 2003
-
Standard Edition
-
SP1 or SP2
-
x86 or x64
-
-
-
Windows Server 2003
-
Enterprise Edition or Datacenter Edition
-
SP1 or SP2
-
x86 or x64
-
-
-
Windows Server 2003 R2
-
Standard Edition
-
No service pack or SP2
-
x86 or x64
-
-
-
Windows Server 2003 R2
-
Enterprise Edition or Datacenter Edition
-
No service pack or SP2
-
x86 or x64
-
-
-
Windows Server 2008
-
Standard, Enterprise, or Datacenter Edition
-
SP1 or SP2
-
x86 or x64
-
-
-
Windows Server 2008 R2¹
-
Standard, Enterprise, or Datacenter Edition
-
-
x64
-
-
-
-
-
-
-¹Applies to App-V 4.5 SP1 and SP2 only.
-
-- Internet Information Services—Internet Information Services (IIS) 6.0 configured with Microsoft ASP.NET, IIS 7
-
-- Microsoft .NET Framework 2.0
-
-## Management Console
-
-
-The following list includes the minimum recommended hardware and software requirements for the Application Virtualization Management Console when it is installed on a separate computer.
-
-### Hardware Requirements
-
-- Processor—Intel Pentium III, 450 MHz
-
-- RAM—256 MB
-
-- Disk space—200 MB available hard disk space
-
-### Software Requirements
-
-
-
-
-
-
-
-
-
-
-
Operating System
-
Edition
-
Service Pack
-
System Architecture
-
-
-
-
-
Windows XP
-
Professional Edition
-
SP2 or SP3
-
x86 or x64
-
-
-
Windows Vista
-
Business, Enterprise, or Ultimate Edition
-
No service pack, SP1, or SP2
-
x86 or x64
-
-
-
Windows 7
-
Professional, Enterprise, or Ultimate Edition
-
-
x86 or x64
-
-
-
Windows Server 2003
-
Standard Edition, Enterprise Edition, or Datacenter Edition
-
SP1 or SP2
-
x86 or x64
-
-
-
Windows Server 2003 R2
-
Standard Edition, Enterprise Edition, or Datacenter Edition
-
No service pack or SP2
-
x86 or x64
-
-
-
Windows Server 2008
-
Standard, Enterprise, or Datacenter Edition
-
SP1 or SP2
-
x86 or x64
-
-
-
Windows Server 2008 R2¹
-
Standard, Enterprise, or Datacenter Edition
-
-
x64
-
-
-
-
-
-
-¹Applies to App-V 4.5 SP1 and SP2 only.
-
-- Microsoft Management Console—MMC 3.0 or later
-
-- Microsoft .NET Framework 2.0 SP2 (minimum)
-
- **Important**
- The minimum requirement is .NET Framework 2.0 SP2 if you must install App-V hotfix KB980850 or subsequent App-V hotfixes on the computer that is running the App-V Management Console.
-
-
-
-## Related topics
-
-
-[Application Virtualization Client Hardware and Software Requirements](application-virtualization-client-hardware-and-software-requirements.md)
-
-[Application Virtualization Sequencer Hardware and Software Requirements](application-virtualization-sequencer-hardware-and-software-requirements.md)
-
-[How to Configure Servers for Server-Based Deployment](how-to-configure-servers-for-server-based-deployment.md)
-
-[How to Install the Servers and System Components](how-to-install-the-servers-and-system-components.md)
-
-[How to Upgrade the Servers and System Components](how-to-upgrade-the-servers-and-system-components.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/application-virtualization-technical-publications-white-papers.md b/mdop/appv-v4/application-virtualization-technical-publications-white-papers.md
deleted file mode 100644
index 3420240770..0000000000
--- a/mdop/appv-v4/application-virtualization-technical-publications-white-papers.md
+++ /dev/null
@@ -1,34 +0,0 @@
----
-title: Application Virtualization Technical Publications
-description: Application Virtualization Technical Publications
-author: dansimp
-ms.assetid: 86606647-3b9b-4459-9638-64626051ac94
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Application Virtualization Technical Publications
-
-
-In this section, you can find additional technical support information for Microsoft Application Virtualization.
-
-## Technical Publications
-
-
-The following technical publications support Microsoft Application Virtualization.
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/applications-licenses-node.md b/mdop/appv-v4/applications-licenses-node.md
deleted file mode 100644
index 3bc727a6b1..0000000000
--- a/mdop/appv-v4/applications-licenses-node.md
+++ /dev/null
@@ -1,126 +0,0 @@
----
-title: Applications Licenses Node
-description: Applications Licenses Node
-author: dansimp
-ms.assetid: 2b8752ff-aa56-483e-b844-966941af2d94
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Applications Licenses Node
-
-
-The **Applications Licenses** node is one level below the Application Virtualization System node in the **Scope** pane in the Application Virtualization Server Management Console. When you select this node, the **Results** pane displays a list of licenses and license groups. The following license types are available:
-
-- **Unlimited License**—Provides access for any number of simultaneous users. This method of licensing is appropriate when you want to associate an enterprise-wide license with an application.
-
-- **Concurrent License**—Enables you to define the maximum number of concurrent users who are allowed to use the application.
-
-- **Named License**—Enables you to assign a license to an individual user. A named license can be used to ensure that a particular user will always be able to run the application.
-
-**Note**
-You can combine concurrent and named licenses for the same application.
-
-
-
-Right-click the **Applications Licenses** node to display a pop-up menu that contains the following elements.
-
-**New Unlimited License**
-Displays the New Unlimited License Wizard. This wizard consists of the following pages:
-
-1. Enter the name of the license group in the **Applications License Group Name** field, and enter a value (in minutes) in the **License Expiration Warning** field. (You can enter any value from 0 through 100.) You can also use the up and down arrows to select the number of minutes.
-
-2. Enter brief descriptive text in the **License Description** field, and select the **Enabled** check box to enable the license.
-
- Optionally, you can use the **Expiration Date** field to specify an expiration date for the license. You can select the check box to use the displayed expiration date, or you can use the calendar utility to browse to the desired expiration date.
-
-3. Click **Finish** to add the new license.
-
-**New Concurrent License**
-Displays the New Concurrent License Wizard. This wizard consists of the following three pages and is almost identical to the New Unlimited License Wizard:
-
-1. Enter the name of the license group in the **Applications License Group Name** field, and enter a value (in minutes) in the **License Expiration Warning** field. (You can enter any value from 0 through 100.) You can also use the up and down arrows to select the number of minutes.
-
-2. Enter brief descriptive text in the **License Description** field, and enter a value in the **Concurrent License Quantity** field.
-
- You can also use the up and down arrows to specify the number of concurrent licenses. Select the **Enabled** check box to enable the license.
-
- Optionally, you can use the **Expiration Date** field to specify an expiration date for the license. You can select the check box to use the displayed expiration date, or you can use the calendar utility to browse to the desired expiration date.
-
-3. Click **Finish** to add the new licenses.
-
-**New Named License**
-Displays the New Named License Wizard. This wizard consists of the following four pages:
-
-1. Enter the name of the license group in the **Applications License Group Name** field, and enter a value (in minutes) in the **License Expiration Warning** field. (You can enter any value from 0 through 100). You can also use the up and down arrows to select the number of minutes.
-
-2. Enter brief descriptive text in the **License Description** field, and select the **Enabled** check box to enable the license.
-
- Optionally, you can use the **Expiration Date** field to specify an expiration date for the license. You can select the check box to use the displayed expiration date, or you can use the calendar utility to browse to the desired expiration date.
-
-3. Click **Add**, **Edit**, or **Remove** named users.
-
-4. Click **Finish** to add the new license.
-
-**View**
-Changes the appearance and content of the **Results** pane.
-
-**New Window from Here**
-Opens a new management console with the selected node as the root node.
-
-**Refresh**
-Refreshes the view of the server.
-
-**Export List**
-Creates a tab-delimited text file that contains the contents of the **Results** pane. This item displays a standard **File Save** dialog box where you specify the location for the text file you are creating.
-
-**Help**
-Displays the help system for the Application Virtualization Server Management Console.
-
-If you click a license group or license that appears under the **Application Licenses** node in the **Scope** pane, the following elements are available.
-
-**View**
-Changes the appearance and content of the **Results** pane.
-
-**New Window from Here**
-Opens a new management console with the selected node as the root node.
-
-**Delete**
-Deletes a package from the **Results** pane.
-
-**Rename**
-Changes the name of a package in the **Results** pane.
-
-**Export List**
-Creates a tab-delimited text file that contains the contents of the **Results** pane. This item displays a standard **File Save** dialog box where you specify the location for the text file you are creating.
-
-**Properties**
-Displays the **Properties** dialog box for the selected license group. The **General** tab of the **Properties** dialog box displays information about the license group and lets you change the time value in the **License Expiration Warning** field. The **Applications** tab displays the list of applications associated with the license group.
-
-**Help**
-Displays the help system for the Application Virtualization Server Management Console.
-
-## Related topics
-
-
-[About Application Licensing](about-application-licensing.md)
-
-[How to Manage Application Licenses in the Server Management Console](how-to-manage-application-licenses-in-the-server-management-console.md)
-
-[Server Management Console: Application Licenses Node](server-management-console-application-licenses-node.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/applications-licenses-results-pane-columns.md b/mdop/appv-v4/applications-licenses-results-pane-columns.md
deleted file mode 100644
index 9fe5dbaaf8..0000000000
--- a/mdop/appv-v4/applications-licenses-results-pane-columns.md
+++ /dev/null
@@ -1,77 +0,0 @@
----
-title: Applications Licenses Results Pane Columns
-description: Applications Licenses Results Pane Columns
-author: dansimp
-ms.assetid: bd56b36a-655e-4fc4-9f83-d2ed68882402
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Applications Licenses Results Pane Columns
-
-
-The **Results** pane in the Application Virtualization Server Management Console displays a variety of columns. These columns are visible when licenses are visible and when the **Results** pane displays licenses.
-
-You can use the standard Microsoft Windows **Add/Remove Columns** dialog box to select which columns are displayed in the **Results** pane.
-
-To see the **Add/Remove Columns** dialog box, expand the **Application Licenses** node, right-click a license and select **View > Add/Remove Columns** from the pop-up menu.
-
-The following table displays the column name and its contents.
-
-
-
-
-
-
-
-
-
Column
-
Contents
-
-
-
-
-
Description
-
Describes the license.
-
-
-
Type
-
Lists the type of license. The available types are Unlimited (any number or users), Concurrent (a specified number of concurrent users), and Named (licenses reserved for specific users).
-
-
-
Expiration Date
-
Displays the date the license is set to expire.
-
-
-
Enabled
-
Displays the enabled status of the license as true or false.
-
-
-
-
-
-
-## Related topics
-
-
-[About Application Licensing](about-application-licensing.md)
-
-[How to Manage Application Licenses in the Server Management Console](how-to-manage-application-licenses-in-the-server-management-console.md)
-
-[Server Management Console: Application Licenses Node](server-management-console-application-licenses-node.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/applications-licenses-results-pane.md b/mdop/appv-v4/applications-licenses-results-pane.md
deleted file mode 100644
index 3339644301..0000000000
--- a/mdop/appv-v4/applications-licenses-results-pane.md
+++ /dev/null
@@ -1,140 +0,0 @@
----
-title: Applications Licenses Results Pane
-description: Applications Licenses Results Pane
-author: dansimp
-ms.assetid: 8b519715-b2fe-451e-ad9b-e9b73f454961
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Applications Licenses Results Pane
-
-
-The **Applications Licenses Results** pane in the Application Virtualization Server Management Console displays a list of the available application license groups and application licenses.
-
-Right-click any application license group to display a pop-up menu that contains the following elements.
-
-**New Unlimited License**
-Displays the New Unlimited License Wizard. This option is available only when the license group has no licenses. This wizard consists of three pages:
-
-1. Enter a group name in the **Applications License Group Name** field and a value (in minutes) in the **License Expiration Warning** field. (You can enter any value from 0–100.) You can also use the up and down arrows to select the number of minutes.
-
-2. Enter brief descriptive text in the **License Description** field, and select the **Enabled** check box. Optionally, you can use the **Expiration Date** field to specify an expiration date for the license. You can select the default check box or use the calendar utility to browse to the desired expiration date.
-
-3. Click **Finish** to add the new license.
-
-**New Concurrent License**
-Displays the New Concurrent License Wizard. This option is available only when the license group has no unlimited licenses. This wizard consists of the following pages and is almost identical to the New Unlimited License Wizard:
-
-1. Enter a group name in the **Applications License Group Name** field and a value (in minutes) in the **License Expiration Warning** field. (You can enter any value from 0–100.) You can also use the up and down arrows to select the number of minutes.
-
-2. Enter brief descriptive text in the **License Description** field, and enter a value in the **Concurrent License Quantity** field. You can also use the up and down arrows to specify the number of concurrent licenses. Select the **Enabled** check box to enable the license. Optionally, you can use the **Expiration Date** field to select an expiration date for the license. You can select the check box to use the displayed expiration date, or you can use the calendar utility to browse to the desired expiration date.
-
-3. Click **Finish** to add the new licenses.
-
-**New Named License**
-Displays the New Named License Wizard. This option is available only when the license group has no unlimited licenses. This wizard consists of the following pages:
-
-1. Enter a group name in the **Applications License Group Name** field and a value (in minutes) in the **License Expiration Warning** field. (You can enter any value from 0–100.) You can also use the up and down arrows to select the number of minutes.
-
-2. Enter brief descriptive text in the **License Description**, and select the **Enabled** check box. Optionally, you can use the **Expiration Date** field to specify an expiration date for the license. You can select the check box to use the displayed expiration date, or use the calendar utility to browse to the desired expiration date.
-
-3. Click **Add**, **Edit**, or **Remove** named users.
-
-4. Click **Finish** to add the new license.
-
-**New Window from Here**
-Opens a new management console with the selected node as the root node.
-
-**Delete**
-Deletes the license group from the list.
-
-**Rename**
-Changes the name of the applications license group.
-
-**Properties**
-Displays the **Properties** dialog box for the selected application license groups. This dialog box has the following tabs:
-
-- **General** tab—Displays general information about the license group. From this tab, you can change the time value (in minutes) in the **License Expiration Warning** field. You can enter any value from 0–100.
-
-- **Applications** tab—Displays the list of applications associated with the license group.
-
-**Help**
-Displays the Application Virtualization Server Management Console help system.
-
-When the **Results** pane displays application license groups, right-click anywhere in the **Results** pane, except on a license group, to display a pop-up menu that contains the following elements.
-
-**Refresh**
-Refreshes the view of the server.
-
-**Export List**
-Creates a tab-delimited text file that contains the contents of the **Results** pane. This item displays a standard **File Save** dialog box where you specify the location for the text file you are creating.
-
-**View**
-Changes the appearance and content of the **Results** pane.
-
-**Arrange/Line Up Icons**
-Changes how the icons are displayed in the **Results** pane.
-
-**Help**
-Displays the help system for the Application Virtualization Server Management Console.
-
-When the **Results** pane displays licenses, right-click any application license to display a pop-up menu that contains the following elements.
-
-**Delete**
-Deletes the license from the list.
-
-**Rename**
-Changes the name of the license.
-
-**Properties**
-Displays the **Properties** dialog box for the selected application license.
-
-The **General** tab of the **Properties** dialog box displays information about the license and lets you change the enabled status, license expiration date, and license key information.
-
-**Help**
-Displays the server management console help system.
-
-When the **Results** pane displays licenses, right-click anywhere in the **Results** pane, except on a license, to display a pop-up menu that contains the following elements.
-
-**Export List**
-Creates a tab-delimited text file that contains the contents of the **Results** pane. This item displays a standard **File Save** dialog box where you specify the location for the text file you are creating.
-
-**View**
-Changes the appearance and content of the **Results** pane.
-
-**Arrange/Line Up Icons**
-Changes how the icons are displayed in the **Results** pane.
-
-**Properties**
-Displays the **Properties** dialog box for the selected license.
-
-The **General** tab of the **Properties** dialog box displays information about the license and lets you change the enabled status, license expiration date, and license key information.
-
-**Help**
-Displays the help system for the Application Virtualization Server Management Console.
-
-## Related topics
-
-
-[About Application Licensing](about-application-licensing.md)
-
-[How to Manage Application Licenses in the Server Management Console](how-to-manage-application-licenses-in-the-server-management-console.md)
-
-[Server Management Console: Application Licenses Node](server-management-console-application-licenses-node.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/applications-node-in-server-management-console.md b/mdop/appv-v4/applications-node-in-server-management-console.md
deleted file mode 100644
index 0dd4066e35..0000000000
--- a/mdop/appv-v4/applications-node-in-server-management-console.md
+++ /dev/null
@@ -1,74 +0,0 @@
----
-title: Applications Node in Server Management Console
-description: Applications Node in Server Management Console
-author: dansimp
-ms.assetid: 27edbd83-0fc2-4a40-9834-d5db5be06681
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Applications Node in Server Management Console
-
-
-The **Applications** node is one level below the Application Virtualization System node in the **Scope** pane. When you select this node, the **Results** pane displays a list of applications. Right-click the **Applications** node to display a pop-up menu that contains the following elements:
-
-**New Application Group**
-Displays the New Application Group Wizard.
-
-**New Application**
-Displays the New Application Wizard.
-
-**Import Applications**
-Imports Open Software Descriptor (OSD) files or Sequencer Project (SPRJ) files.
-
-**New Window from Here**
-Opens a new management console with the selected node as the root node.
-
-**Refresh**
-Refreshes the view of the server.
-
-**Help**
-Displays the help system for the Application Virtualization Management Console.
-
-When you right-click any application group that appears under the **Applications** node in the **Scope** pane, the following additional elements are available.
-
-**View**
-Changes the appearance and content of the **Results** pane.
-
-**Move**
-Moves the application to another application group.
-
-**Copy**
-Copies an application to a new Application Virtualization System.
-
-**Delete**
-Deletes an application.
-
-**Rename**
-Renames an application.
-
-**Export List**
-Creates a tab-delimited text file that contains the contents of the **Results** pane. This item displays a standard **File Save** dialog box where you specify the location for the text file you are creating.
-
-## Related topics
-
-
-[How to Manually Add an Application](how-to-manually-add-an-application.md)
-
-[Server Management Console: Applications Node](server-management-console-applications-node.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/applications-node.md b/mdop/appv-v4/applications-node.md
deleted file mode 100644
index 760ebc733a..0000000000
--- a/mdop/appv-v4/applications-node.md
+++ /dev/null
@@ -1,62 +0,0 @@
----
-title: Applications Node
-description: Applications Node
-author: dansimp
-ms.assetid: ded79569-8a3f-47ab-b135-0836bbb039f3
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Applications Node
-
-
-The **Applications** node is one level below the **Application Virtualization** node in the **Scope** pane of the Application Virtualization Client Management Console. When you select this node, the **Results** pane displays a list of applications. Right-click the **Applications** node to display a pop-up menu that contains the following elements.
-
-**New Application**
-This menu item displays the New Application Wizard. This wizard consists of one page where you can select an icon for the application and browse to or enter a URL or a path to the Open Software Descriptor (OSD) file.
-
-- **Change Icon**—Displays a standard Windows icon browser. Browse to and select the desired icon.
-
-- **OSD File Path or URL**—Enter a local absolute path, a full Universal Naming Convention (UNC) path, or an HTTP URL.
-
-- **... (OSD browse button)**—Displays the standard Windows **Open File** dialog box. Browse to find the desired file.
-
-**New Window from Here**
-Select this menu item to open a new management console with the selected node as the root node.
-
-**Export List**
-You can use this menu item to create a tab-delimited text file that contains the contents of the **Results** pane. This item displays a standard **File Save** dialog box where you specify the location for the text file you are creating.
-
-**View**
-This pop-up list of menu items enables you to change the appearance and content of the **Results** pane.
-
-**Refresh**
-Select this item to refresh the management console.
-
-**Help**
-This item displays the help system for the management console.
-
-## Related topics
-
-
-[Applications Results Pane](applications-results-pane.md)
-
-[Applications Results Pane Columns](applications-results-pane-columns.md)
-
-[Application Virtualization Client Management Console Reference](application-virtualization-client-management-console-reference.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/applications-results-pane-columns-in-server-management-console.md b/mdop/appv-v4/applications-results-pane-columns-in-server-management-console.md
deleted file mode 100644
index 55a7172da2..0000000000
--- a/mdop/appv-v4/applications-results-pane-columns-in-server-management-console.md
+++ /dev/null
@@ -1,93 +0,0 @@
----
-title: Applications Results Pane Columns in Server Management Console
-description: Applications Results Pane Columns in Server Management Console
-author: dansimp
-ms.assetid: 8757e3bc-450b-4550-81d2-624906523147
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Applications Results Pane Columns in Server Management Console
-
-
-The **Applications Results** pane in the Application Virtualization Management Console displays a variety of columns.
-
-You can use the standard Microsoft Windows **Add/Remove Columns** dialog box to select which columns are displayed in the **Results** pane.
-
-To see the **Add/Remove Columns** dialog box, right-click in the **Results** pane and select **View > Add/Remove Columns** from the pop-up menu.
-
-The following table displays the column name and its contents.
-
-
-
-
-
-
-
-
-
Column
-
Contents
-
-
-
-
-
Name
-
Displays the application name.
-
-
-
Version
-
Displays the application version.
-
-
-
Package
-
Displays the name of the package.
-
-
-
OSD Path
-
Displays the full original path or URL to the Open Software Descriptor (OSD) file.
-
-
-
Icon File
-
Displays the complete path to the icon file.
-
-
-
Enabled
-
Displays the enabled status of the file; the status is either true or false.
-
-
-
Application License
-
Displays the name of the application license.
-
-
-
Type
-
Displays the application or application group type.
-
-
-
Description
-
Displays a brief description of the application.
-
-
-
-
-
-
-## Related topics
-
-
-[Server Management Console: Applications Node](server-management-console-applications-node.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/applications-results-pane-columns.md b/mdop/appv-v4/applications-results-pane-columns.md
deleted file mode 100644
index c7c7c41ec3..0000000000
--- a/mdop/appv-v4/applications-results-pane-columns.md
+++ /dev/null
@@ -1,137 +0,0 @@
----
-title: Applications Results Pane Columns
-description: Applications Results Pane Columns
-author: dansimp
-ms.assetid: abae5ce2-40df-4f47-8062-f5eb6295c88c
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Applications Results Pane Columns
-
-
-The **Results** pane of the **Applications** node in the Application Virtualization Client Management Console can display a variety of columns. **Application**, **Running**, **Locked**, and **Package Status** are shown by default.
-
-**Note**
-You can add or remove columns by right-clicking in the **Results** pane, selecting **View**, and then selecting **Add/Remove Columns**.
-
-
-
-The list can be sorted by any column. Columns that contain dates and times are sorted in chronological order, not alphabetical. For columns that contain a mix of dates and times and text, dates and times are considered to come before any other text.
-
-The following columns are available.
-
-**Application**
-The application name and version, separated by a space.
-
-**Application In Use**
-Displays **Yes** or **No** depending on whether any user is using the application (that is, running it or loading it).
-
-**App Virt Server**
-The Application Virtualization server from which the package was streamed.
-
-**Cached Icon File**
-The name of the icon files in cache (a GUID in the current implementation).
-
-**Cached Icon Path**
-The full path to the icon files in cache.
-
-**Cached Launch Percent**
-The percentage of the application’s launch data currently in cache.
-
-**Cached Launch Size (MB)**
-The amount of the application’s launch data currently in cache.
-
-**Cached OSD File**
-The name of the OSD file in the cache (which is a GUID in the current implementation).
-
-**Cached OSD Path**
-The full path to the OSD file in the cache.
-
-**Cached Package Percent**
-The percentage of the package currently in cache.
-
-**Cached Package Size (MB)**
-The size of the portion of the package currently in cache.
-
-**Icon File**
-The original name of the icon file.
-
-**Icon Path**
-The original path or URL for the icon file.
-
-**Last System Launch**
-The last time the application was launched by the system.
-
-**Last User Launch**
-The last time the application was launched by the user.
-
-**Launch Size (MB)**
-The uncompressed size of the package data needed to launch the application.
-
-**Locked**
-Displays **Yes** or **No** depending on whether the application’s package is locked in the cache.
-
-**Name**
-The application name.
-
-**OSD File**
-The original name of the Open Software Descriptor (OSD) file.
-
-**OSD Path**
-The full original path or URL to the OSD file.
-
-**Package Name**
-The name of the package.
-
-**Package GUID**
-The GUID for the package.
-
-**Package Size (MB)**
-The total size of the uncompressed data in the package.
-
-**Package Status**
-The current operational status of the package.
-
-**Package URL**
-The URL for the package.
-
-**Package Version**
-The version for the package.
-
-**Package Version GUID**
-The GUID for the package version.
-
-**Running**
-Displays **Yes** or **No** depending on whether the current user is running the application.
-
-**Source**
-Where the application came from—either the name of an application publishing server or "Local" for applications added from OSD files directly.
-
-**Version**
-The application version.
-
-## Related topics
-
-
-[Applications Node](applications-node.md)
-
-[Applications Results Pane](applications-results-pane.md)
-
-[Application Virtualization Client Management Console Reference](application-virtualization-client-management-console-reference.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/applications-results-pane-in-server-management-console.md b/mdop/appv-v4/applications-results-pane-in-server-management-console.md
deleted file mode 100644
index ea36979d73..0000000000
--- a/mdop/appv-v4/applications-results-pane-in-server-management-console.md
+++ /dev/null
@@ -1,149 +0,0 @@
----
-title: Applications Results Pane in Server Management Console
-description: Applications Results Pane in Server Management Console
-author: dansimp
-ms.assetid: 686218bc-6156-40e2-92aa-90981c3d112a
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Applications Results Pane in Server Management Console
-
-
-The **Applications Results** pane displays a list of the available applications.
-
-Right-click anywhere in the **Results** pane, except on an application or application group, to display a pop-up menu that contains the following elements.
-
-**Refresh**
-Refreshes the list of applications.
-
-**Export List**
-Creates a tab-delimited text file that contains the contents of the **Results** pane. This item displays a standard **File Save** dialog box where you specify the location for the text file you are creating. For more information about the **Export List** feature, refer to the documentation for the Microsoft Management Console.
-
-**View**
-Changes the appearance and content of the **Results** pane.
-
-**Arrange/Line up Icons**
-Organizes the icons in the **Results** pane.
-
-**Help**
-Displays the help system for the Application Virtualization Management Console.
-
-Right-click any application in the **Results** pane to display a pop-up menu that contains the following elements.
-
-**Move**
-Moves the applications into and out of application groups.
-
-**Copy**
-Copies the application to another Application Virtualization System.
-
-**Duplicate**
-Duplicates the application in the **Results** pane.
-
-**Delete**
-Removes the application from the Application Virtualization System.
-
-**Rename**
-Enables you to change the name of the application.
-
-**Properties**
-Displays the **Properties** dialog box for the selected application. This dialog box has the following tabs:
-
-- **General** tab—Displays the application icon, application name, and package name. This tab also displays the following specific information about the application that you can change:
-
- - **Version**—Enables you to enter the appropriate version number. Select the **Enable** check box to enable version numbering.
-
- - **Description**—Enables you to enter a brief description of the application.
-
- - **OSD Path**—Enables you to enter or browse to the location of the appropriated Open Software Descriptor (OSD) file.
-
- - **Icon Path**—Enables you to enter or browse to the location of the icon file that you want to associate with the application.
-
- - **Application License Group**—Enables you to select the license group from the drop-down list of license groups.
-
- - **Server Group**—Enables you to select the server group from the drop-down list of server groups.
-
-- **Shortcuts** tab—Displays the check boxes that correspond to the locations where the shortcuts are published. You can select or clear check boxes from this tab.
-
-- **File Type Associations** tab—Displays a list of the file types associated with the selected application. From this tab, you can add, edit, or delete the file type association.
-
-- **Access Permissions** tab—Displays the list of groups that have access permission to the selected application. From this tab, you can add, edit, or delete groups.
-
-**Help**
-Displays the help system for the Application Virtualization Management Console.
-
-Right-click any application group to display a pop-up menu that contains the following elements.
-
-**New Application Group**
-Displays the New Application Group Wizard. Add the name of the new application group in the appropriate field, and then click **Finish**.
-
-**New Application**
-Displays the New Application Wizard. Navigate through the wizard to add applications.
-
-**Import Applications**
-Displays a browse dialog box that you can use to import existing applications into the Application Virtualization Management Console. You can import an OSD file or a Sequencer Project (SPRJ) file.
-
-**Move**
-Moves the application group into and out of application groups.
-
-**Copy**
-Copies the application group to a new server.
-
-**New Window from Here**
-Opens a new management console with the selected node as the root node.
-
-**Delete**
-Removes the application group from the server.
-
-**Rename**
-Changes the name of the application group.
-
-**Refresh**
-Refreshes the application group. If the **Results** pane is displaying the entire application node, the pane will switch to display the contents of the application group.
-
-**Properties**
-Displays the **Properties** dialog box for the selected application group. This dialog box has the following tabs:
-
-- **General** tab—Displays the application group icon and application group name. This tab also displays the following, limited information about the application group that you can change.
-
- - **Version**—Enables you to enter a version number for the application group.
-
- - **Description**—Enables you to enter a brief description of the application group.
-
- - **OSD Path**—Enables you to enter or browse to the location where the OSD file is located.
-
- - **Icon Path**—Enables you to enter or browse to the location where the icon file is located.
-
- - **Application License Group**—Enables you to select the license group from the drop-down list of license groups.
-
- - **Server Group**—Enables you to select the server group from the drop-down list of server groups.
-
-- **Shortcuts** tab—Displays the check boxes that correspond to the locations where the shortcuts are published. You can select or clear check boxes from this tab.
-
-- **File Associations** tab—Displays the list of file type associations. You can add, edit, or delete file type associations from this tab.
-
-- **Access Permissions** tab—Displays the list of groups that have access permission to the selected application group. From this tab, you can add, edit, or delete groups.
-
-**Help**
-Displays the help system for the Application Virtualization Management Console.
-
-## Related topics
-
-
-[Server Management Console: Applications Node](server-management-console-applications-node.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/applications-results-pane.md b/mdop/appv-v4/applications-results-pane.md
deleted file mode 100644
index ad52fe65d1..0000000000
--- a/mdop/appv-v4/applications-results-pane.md
+++ /dev/null
@@ -1,142 +0,0 @@
----
-title: Applications Results Pane
-description: Applications Results Pane
-author: dansimp
-ms.assetid: 977a4d35-5344-41fa-af66-14957b38ed47
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Applications Results Pane
-
-
-The **Applications Results** pane in the Application Virtualization Client Management Console displays a list of the available applications. Users can see a list of applications for which they have been granted access privileges.
-
-For more information about the procedures you can perform from this pane, see [How to Manage Applications in the Client Management Console](how-to-manage-applications-in-the-client-management-console.md).
-
-Right-click any application to display a pop-up menu that contains the following elements.
-
-**New Shortcut**
-This menu item displays the New Shortcut Wizard. This wizard consists of three pages:
-
-1. Select an icon, and specify a name for the shortcut:
-
- 1. **Change Icon**—Displays a standard Windows icon browser. Browse to and select the desired icon.
-
- 2. **Shortcut Title**—Enter the name you want to give the shortcut. This field defaults to the existing name and version of the application.
-
-2. Determine the location of the published shortcut.
-
- 1. **Location of shortcut**—Select a location by selecting one of the check boxes. The available locations are **Desktop**, **Quick Launch Toolbar**, **Send to Menu**, **Start Menu**, and **Another location**.
-
- 2. **Programs in the Start Menu**—When you select the **Start Menu** check box, this field becomes active. Leave this field blank to publish the shortcut directly to the root of the Programs folder, or enter a folder name or hierarchy—for example, "My\_Computer\\Office Applications." Shortcuts created this way are available only for the current user.
-
- 3. **Another location** and browse button—When you select the **Another location** check box, this field becomes active. Enter any valid location on the computer or any available Universal Naming Convention (UNC) path(shared file or directory on a network). The browse button displays a standard Windows **File Open** dialog box.
-
-3. Enter the desired command-line parameters, and then click **Finish** to exit the wizard.
-
-**New Association**
-This menu item displays the New Association Wizard. This wizard consists of two pages:
-
-1. Enter a file name extension, and associate the extension with a file type.
-
- 1. **Extension**—Enter a file name extension. This field is blank by default.
-
- 2. **Create a new file type with this description**—Select this radio button to enter a new file type description in the active field. This button is selected by default, and the active field is blank.
-
- 3. **Apply this file type to all users**—Select this check box when you want this association to be global for all users. By default, this box is not selected.
-
- 4. **Link this extension with an existing file type**—Select this radio button to associate the extension with an existing file type. Choose a file type from the drop-down list. When you choose this option, **Next** is changed to **Finish**.
-
-2. Select the application that will open files with the specified extension:
-
- 1. **Open files with the selected application**—Select this radio button to open the file with an existing application. Choose an application from the drop-down list of available applications.
-
- 2. **Open file with the association described in this OSD file**—Select this radio button to specify an Open Software Descriptor (OSD) file that determines the application used to open the file. Use the browse button to select an existing location, or enter a path or HTTP-formatted URL in this field.
-
-**Repair**
-Resets the application default settings and eliminates all user-defined settings for the selected application.
-
-**Load** or **Unload**
-Loads or unloads the selected application into the cache. This command is not available if 100 percent of the application is in the cache.
-
-**Clear**
-Removes the user's settings, shortcuts, and file type associations for the selected application. This item is not available if a user is running any application from a suite of applications. Displays a confirmation prompt.
-
-**Lock** or **Unlock**
-Locks or unlocks an application in the cache. When an application is locked, it cannot be deleted or overwritten.
-
-**Import**
-Imports an application into the cache directly from this command in the **Applications** node.
-
-**Delete**
-Deletes an application from the **Results** pane and from the computer, and clears the application from cache.
-
-**Refresh**
-Refreshes the contents of the **Results** pane.
-
-**Properties**
-Displays the **Properties** dialog box for the selected application. This dialog box has two tabs:
-
-1. The **General** tab displays the application icon and name, the location from where the application was streamed, and the path to the local OSD file. From this tab, you can change the icon for the application or you can clear the settings (which removes the shortcuts and the file type associations).
-
-2. The **Package** tab displays information about the application package, and you can **Lock**, **Unlock**, **Load**, **Unload**, and **Import** applications.
-
-**Help**
-Displays the Client Management Console help system.
-
-## Displaying General Options for the Results pane
-
-
-Right-click anywhere in the **Results** pane to display a pop-up menu that contains the following elements.
-
-**New Application**
-This menu item displays the New Application Wizard. This wizard consists of one page where you can select an icon for the application and browse to or enter a URL or a path to the OSD file:
-
-1. **Change Icon**—Displays a standard Windows icon browser. Browse to and select the desired icon.
-
-2. **OSD File Path or URL**—Enter a local absolute path, a full UNC path, or an HTTP URL.
-
-3. **... (OSD browse button)**—Displays the standard Windows **Open File** dialog box. Browse to find the desired file.
-
-**Refresh**
-Refreshes the **Results** pane.
-
-**Export List**
-You can use this menu item to create a tab-delimited text file that contains the contents of the **Results** pane. This item displays a standard **File Save** dialog box where you specify the location for the text file you are creating.
-
-**View**
-This pop-up list of menu items lets you change the appearance and content of the **Results** pane.
-
-**Arrange/Line Up Icons**
-These menu items can be used to change how the icons are displayed in the **Results** pane.
-
-**Help**
-Displays the help system for the management console.
-
-## Related topics
-
-
-[Applications Node](applications-node.md)
-
-[Applications Results Pane Columns](applications-results-pane-columns.md)
-
-[Application Virtualization Client Management Console Reference](application-virtualization-client-management-console-reference.md)
-
-[How to Manage Applications in the Client Management Console](how-to-manage-applications-in-the-client-management-console.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/best-practices-for-the-application-virtualization-sequencer-sp1.md b/mdop/appv-v4/best-practices-for-the-application-virtualization-sequencer-sp1.md
deleted file mode 100644
index 8ac9a89ec9..0000000000
--- a/mdop/appv-v4/best-practices-for-the-application-virtualization-sequencer-sp1.md
+++ /dev/null
@@ -1,105 +0,0 @@
----
-title: Best Practices for the Application Virtualization Sequencer
-description: Best Practices for the Application Virtualization Sequencer
-author: dansimp
-ms.assetid: 95e5e216-864f-41a1-90d4-b8d7e1eb42a0
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Best Practices for the Application Virtualization Sequencer
-
-
-This topic provides best practices for running the Microsoft Application Virtualization (App-V) Sequencer. Review and consider the following recommendations when planning and using the Sequencer in your environment.
-
-## Sequencing Computer Configuration Best Practices
-
-
-The following best practices should be considered when configuring the computer running the App-V Sequencer:
-
-- **Sequence on a computer that has a similar configuration and that is running an earlier version of the operating system than the target computers.**
-
- Ensure that the computer that is running the Sequencer is running an earlier version of the operating system than the target computers. This includes the service pack and update versions. For example, if the target computers are running Windows Vista and Windows XP, you should sequence applications on a computer that is running Windows XP. The ability to sequence on one operating system and run the virtualized application on a different operating system is not guaranteed, and depends on the particular application and operating system. If you encounter issues, you may be required to sequence on the same operating system environment as the one on which the App-V client is running.
-
-- **Configure the computer running the Sequencer with multiple partitions.**
-
- You should configure the computer running the Sequencer with at least two primary partitions. The first partition (**C:**) should contain the operating system, and it should be formatted using the NTFS file system. The second partition (**Q:**) is used as the destination path for the virtual application installation and should also be formatted using the NTFS file system.
-
-- **Configure the temp directory with enough free disk space.**
-
- The Sequencer uses the **%TMP%** or **%TEMP%** directory and the **Scratch** directory to store temporary files during sequencing. You should configure these directories on the computer running the Sequencer with free disk space equivalent to the estimated application installation requirements. You can verify the location of the **Scratch** directory by opening the Sequencer console and selecting **Tools**, **Options**, and then selecting the **Paths** tab. Configuring the temp directories and the **Scratch** directory on different hard drive partitions can improve performance during sequencing.
-
-- **Sequence applications by using Microsoft Virtual PC.**
-
- You will sequence most applications more than once. To help facilitate this, you should consider sequencing on a computer running in a virtual environment. This will allow you to sequence an application and revert to a clean state, with minimal reconfiguration, on the computer that is running the Sequencer.
-
- If you are running Microsoft Hyper-V in your environment the App-V sequencer will run when the Hyper-V virtual computer it is running on is:
-
- - paused and resumed.
-
- - has its state saved and restored.
-
- - saved as a snapshot and is restored.
-
- - migrated to different hardware as part of a live migration.
-
-- **Before you sequence a new application, shut down other running programs.**
-
- Processes and scheduled tasks that normally run on the sequencing computer can slow down the sequencing process and cause irrelevant data to be gathered during sequencing. All unnecessary applications and programs should be shut down before you begin sequencing.
-
-- **Sequence on a computer that is running Terminal Services**
-
- You should not configure the install mode on a computer that is running Terminal Services before you install the sequencer.
-
-## Sequencing Best Practices
-
-
-The following best practices should be considered when sequencing a new application:
-
--
-
- **Note**
- If you are running App-V 4.6 SP1 you do not need to sequence to a directory that follows the 8.3 naming convention.
-
-
-
-- **Sequence to a unique directory that follows the 8.3 naming convention.**
-
- You should sequence all applications to a directory that follows the 8.3 naming convention. The specified directory name cannot contain more than eight characters, followed by a three-character file name extension—for example, **Q:\\MYAPP.ABC**.
-
-- **Sequence to a destination folder on the root of the drive, not to a subdirectory.**
-
- If the application suite has multiple parts, install each application to a subdirectory of the main directory. For example, if a package contains an application along with a client, use **Q:\\AppSuite** as the main directory and sequence the main application to **Q:\\AppSuite\\Main**, and sequence the client to **Q:\\AppSuite\\Client**.
-
-- **Configure and test the application during the installation phase.**
-
- Completing the installation of an application often requires performing several manual steps that are not part of the application installation process. These steps can involve configuring a connection to a database or copying updated files. You should perform these configurations during the installation phase and then run the application to make sure it works.
-
-- **Run the application, multiple times if necessary, until the program is stable.**
-
- You should run the application multiple times during the installation to ensure all associated registration and dialog box configurations have been completed. Opening the application multiple times during installation will ensure that only the relevant application features are loaded into the **primary feature block**.
-
-- **Disable all automatic update features associated with the application.**
-
- Some applications have the ability to check for the latest updates automatically during installation. To assist with versioning of virtual application packages, you should disable this feature during sequencing. If there are required updates, you should sequence a new virtual application package with the associated updates installed.
-
-## Related topics
-
-
-[Planning for Application Virtualization System Deployment](planning-for-application-virtualization-system-deployment.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/change-history-tab-keep.md b/mdop/appv-v4/change-history-tab-keep.md
deleted file mode 100644
index 7de068d479..0000000000
--- a/mdop/appv-v4/change-history-tab-keep.md
+++ /dev/null
@@ -1,108 +0,0 @@
----
-title: Change History Tab
-description: Change History Tab
-author: dansimp
-ms.assetid: 652ef2f0-3a3e-4844-a472-9fa99ec5ee32
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Change History Tab
-
-
-After you sequence an application and before you save it, you can use the **Change History** tab to view the historical information about a sequenced application package. This tab is read only and cannot be modified. It contains the following elements.
-
-## Modification Date
-
-
-**Modification Date**
-The date a sequenced application package was modified.
-
-## Package Information
-
-
-**Package Version GUID**
-The GUID for the version of the sequenced application package that is loaded, which can be used during deployment to specify a particular version of the package.
-
-## Sequencer Information
-
-
-This section of the **Change History** tab displays specific information about the Application Virtualization Sequencer (the Sequencer) that was used to create the sequenced application package. It contains the following elements.
-
-**Sequencer Version**
-The version of the Sequencer used to create the package.
-
-**Sequenced By**
-The name of the sequencing engineer.
-
-**Sequencing Station**
-The sequencing computer used to create the sequenced application package.
-
-**Package Upgrade**
-Indicates whether the sequenced application package was upgraded and saved.
-
-**Save Mode**
-Indicates the method used to save the application package.
-
-## Windows Information
-
-
-**Windows Version**
-The version of Windows used to create a sequenced application package.
-
-**System Folder**
-The path on the Sequencing computer of its System folder.
-
-**Windows Folder**
-The location on the sequencing computer of its Windows folder.
-
-**User Folder**
-The location on the sequencing computer of its User folder.
-
-**System Type**
-The type of operating system on the sequencing computer.
-
-## System Information
-
-
-**Processor**
-The processor of the sequencing computer system.
-
-**Last Boot Normal**
-Indicates whether or not the sequencing computer's most recent boot-up was normal.
-
-**Terminal Services**
-Indicates whether Terminal Services are operant on the sequencing computer system.
-
-**Remote Desktop**
-Indicates whether Remote Desktop is operant on the sequencing computer.
-
-**.NET Framework Version**
-Indicates the availability of any version of the .NET Framework on the sequencing computer.
-
-**Internet Explorer Version**
-Indicates the availability of any version of Internet Explorer on the sequencing computer.
-
-**Windows Media Player Version**
-Indicates the availability of any version of Windows Media Player on the sequencing computer.
-
-## Related topics
-
-
-[Sequencer Console](sequencer-console.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/clear-app.md b/mdop/appv-v4/clear-app.md
deleted file mode 100644
index ce8c9d4c5f..0000000000
--- a/mdop/appv-v4/clear-app.md
+++ /dev/null
@@ -1,86 +0,0 @@
----
-title: CLEAR APP
-description: CLEAR APP
-author: dansimp
-ms.assetid: c2e63031-5941-45e4-9863-127231cfa25b
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# CLEAR APP
-
-
-Clears the current user's settings and publishing configurations for an application.
-
-`SFTMIME CLEAR APP:application [/LOG log-pathname | /CONSOLE | /GUI]`
-
-
-
-
-
-
-
-
-
Parameter
-
Description
-
-
-
-
-
APP:<application>
-
The name and version (optional) of the application.
-
-
-
/LOG
-
If specified, output is logged to the specified path name.
-
-
-
/CONSOLE
-
If specified, output is presented in the active console window (default).
-
-
-
/GUI
-
If specified, output is presented in a Windows dialog box.
-
-
-
-
-
-
-For version 4.6, the following option has been added.
-
-
-
-
-
-
-
-
-
/LOGU
-
If specified, output is logged to the specified path name in UNICODE format.
If specified, output is logged to the specified path name.
-
-
-
/CONSOLE
-
If specified, output is presented in the active console window (default).
-
-
-
/GUI
-
If specified, output is presented in a Windows dialog box.
-
-
-
-
-
-
-For version 4.6, the following option has been added.
-
-
-
-
-
-
-
-
-
/LOGU
-
If specified, output is logged to the specified path name in UNICODE format.
-
-
-
-
-
-
-## Related topics
-
-
-[SFTMIME Command Reference](sftmime--command-reference.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/client-management-console-about-dialog-boxes.md b/mdop/appv-v4/client-management-console-about-dialog-boxes.md
deleted file mode 100644
index 67b7ff9eaa..0000000000
--- a/mdop/appv-v4/client-management-console-about-dialog-boxes.md
+++ /dev/null
@@ -1,36 +0,0 @@
----
-title: Client Management Console About Dialog Boxes
-description: Client Management Console About Dialog Boxes
-author: dansimp
-ms.assetid: eaf4a05e-513d-4eac-a549-76e63a70893d
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Client Management Console: About Dialog Boxes
-
-
-The **About** dialog boxes display information about the specific version of the Microsoft Management Console or the specific version of the Application Virtualization Desktop Client or Client for Remote Desktop Services (formerly Terminal Services) Management Console.
-
-To display these dialog boxes, click **Help** and select **About Microsoft Management Console** or **About Application Virtualization Client Management Console**.
-
-## Related topics
-
-
-[Application Virtualization Client Management Console Reference](application-virtualization-client-management-console-reference.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/client-management-console-application-virtualization-node.md b/mdop/appv-v4/client-management-console-application-virtualization-node.md
deleted file mode 100644
index 9ea64120a9..0000000000
--- a/mdop/appv-v4/client-management-console-application-virtualization-node.md
+++ /dev/null
@@ -1,50 +0,0 @@
----
-title: Client Management Console Application Virtualization Node
-description: Client Management Console Application Virtualization Node
-author: dansimp
-ms.assetid: cf74e112-ddff-4e30-a3cc-7f4c643366c6
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Client Management Console: Application Virtualization Node
-
-
-The **Application Virtualization** node is the top-level node in the **Scope** pane of the Application Virtualization Client Management Console. This node displays the name of the computer the console is currently controlling, or it displays "Local" if the console is connected to the local computer.
-
-By right-clicking the **Application Virtualization** node, you can display the **Properties** dialog box to configure the Application Virtualization Desktop Client or Client for Remote Desktop Services (formerly Terminal Services).
-
-The **Properties** dialog box contains the following elements:
-
-[Application Virtualization Properties: General Tab](application-virtualization-properties-general-tab.md)
-
-[Application Virtualization Properties: Interface Tab](application-virtualization-properties-interface-tab.md)
-
-[Application Virtualization Properties: File System Tab](application-virtualization-properties-file-system-tab.md)
-
-[Application Virtualization Properties: Permissions Tab](application-virtualization-properties-permissions-tab.md)
-
-[Application Virtualization Properties: Connectivity Tab](application-virtualization-properties-connectivity-tab.md)
-
-[Application Virtualization Properties: Import Search Path Tab](application-virtualization-properties-import-search-path-tab.md)
-
-## Related topics
-
-
-[Application Virtualization Client Management Console Reference](application-virtualization-client-management-console-reference.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/client-management-console-application-virtualization-properties.md b/mdop/appv-v4/client-management-console-application-virtualization-properties.md
deleted file mode 100644
index 85513a0959..0000000000
--- a/mdop/appv-v4/client-management-console-application-virtualization-properties.md
+++ /dev/null
@@ -1,55 +0,0 @@
----
-title: Client Management Console Application Virtualization Properties
-description: Client Management Console Application Virtualization Properties
-author: dansimp
-ms.assetid: 70319e4c-5032-4cb3-bbb8-4292809dcea2
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Client Management Console: Application Virtualization Properties
-
-
-You can display the **Properties** dialog simply by right-clicking the **Application Virtualization** node in the Application Virtualization Client Management Console and selecting **Properties** from the pop-up menu.
-
-## In This Section
-
-
-[Application Virtualization Properties: General Tab](application-virtualization-properties-general-tab.md)
-Use the **General** tab of the **Properties** dialog box to modify log settings and data locations.
-
-[Application Virtualization Properties: Interface Tab](application-virtualization-properties-interface-tab.md)
-Use the **Interface** tab of the **Properties** dialog box to control default settings for user-interface components.
-
-[Application Virtualization Properties: File System Tab](application-virtualization-properties-file-system-tab.md)
-Use the **File System** tab of the **Properties** dialog box to view and monitor file system settings.
-
-[Application Virtualization Properties: Import Search Path Tab](application-virtualization-properties-import-search-path-tab.md)
-Use the **Import Search Path** tab of the **Properties** dialog box to add, view, or change import search paths.
-
-[Application Virtualization Properties: Connectivity Tab](application-virtualization-properties-connectivity-tab.md)
-Use the **Connectivity** tab of the **Properties** dialog box to specify the connectivity settings.
-
-[Application Virtualization Properties: Permissions Tab](application-virtualization-properties-permissions-tab.md)
-Use the **Permissions** tab of the **Properties** dialog box to specify which activities are available for non-administrators on the local computer.
-
-## Related topics
-
-
-[Application Virtualization Client Management Console Reference](application-virtualization-client-management-console-reference.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/client-management-console-applications-node.md b/mdop/appv-v4/client-management-console-applications-node.md
deleted file mode 100644
index 6661141ad2..0000000000
--- a/mdop/appv-v4/client-management-console-applications-node.md
+++ /dev/null
@@ -1,46 +0,0 @@
----
-title: Client Management Console Applications Node
-description: Client Management Console Applications Node
-author: dansimp
-ms.assetid: 20cf533c-e0b0-4b81-af4b-b5b519594d1e
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Client Management Console: Applications Node
-
-
-The topics in this section provide information about the screen reference for the **Applications** node in the Application Virtualization Client Management Console.
-
-## In This Section
-
-
-[Applications Node](applications-node.md)
-Describes the features and commands available from the **Applications** node.
-
-[Applications Results Pane](applications-results-pane.md)
-Describes the features and commands available from the **Applications** node **Results** pane.
-
-[Applications Results Pane Columns](applications-results-pane-columns.md)
-Describes the columns available in the **Applications** node **Results** pane.
-
-## Related topics
-
-
-[Application Virtualization Client Management Console Reference](application-virtualization-client-management-console-reference.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/client-management-console-file-type-associations-node.md b/mdop/appv-v4/client-management-console-file-type-associations-node.md
deleted file mode 100644
index f0c5570f3c..0000000000
--- a/mdop/appv-v4/client-management-console-file-type-associations-node.md
+++ /dev/null
@@ -1,46 +0,0 @@
----
-title: Client Management Console File Type Associations Node
-description: Client Management Console File Type Associations Node
-author: dansimp
-ms.assetid: f0bc05ce-2cb2-4b06-961b-6c42d0274d28
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Client Management Console: File Type Associations Node
-
-
-The topics in this section provide information about the screen reference for the **File Associations** node in the Application Virtualization Client Management Console.
-
-## In This Section
-
-
-[File Type Associations Node](file-type-associations-node-client.md)
-Describes the features and commands available from the **File Associations** node.
-
-[File Type Association Results Pane](file-type-association-results-pane.md)
-Describes the features and commands available from the **File Associations** node **Results** pane.
-
-[File Type Association Results Pane Columns](file-type-association-results-pane-columns.md)
-Describes the columns available in the **File Associations** node **Results** pane.
-
-## Related topics
-
-
-[Application Virtualization Client Management Console Reference](application-virtualization-client-management-console-reference.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/client-management-console-publishing-servers-node.md b/mdop/appv-v4/client-management-console-publishing-servers-node.md
deleted file mode 100644
index f863e5d717..0000000000
--- a/mdop/appv-v4/client-management-console-publishing-servers-node.md
+++ /dev/null
@@ -1,46 +0,0 @@
----
-title: Client Management Console Publishing Servers Node
-description: Client Management Console Publishing Servers Node
-author: dansimp
-ms.assetid: 03f2038f-b5f7-4e5b-a8f0-98f5e9d5f644
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Client Management Console: Publishing Servers Node
-
-
-The topics in this section provide information about the screen reference for the **Publishing Servers** node in the Application Virtualization Client Management Console.
-
-## In This Section
-
-
-[Publishing Servers Node](publishing-servers-node.md)
-Describes the features and commands available from the **Publishing Servers** node.
-
-[Publishing Servers Results Pane](publishing-servers-results-pane.md)
-Describes the features and commands available from the **Publishing Servers** node **Results** pane.
-
-[Publishing Servers Results Pane Columns](publishing-servers-results-pane-columns.md)
-Describes the columns available in the **Publishing Servers** node **Results** pane.
-
-## Related topics
-
-
-[Application Virtualization Client Management Console Reference](application-virtualization-client-management-console-reference.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/command-line-errors.md b/mdop/appv-v4/command-line-errors.md
deleted file mode 100644
index 3da8e0d9f9..0000000000
--- a/mdop/appv-v4/command-line-errors.md
+++ /dev/null
@@ -1,101 +0,0 @@
----
-title: Command-Line Errors
-description: Command-Line Errors
-author: dansimp
-ms.assetid: eea62568-4e90-4877-9cc7-e27ef5c05068
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Command-Line Errors
-
-
-Use the following list of errors to identify the reasons why command-line sequencing is not working properly. You can also see these errors by viewing the sequencer log file.
-
-**Note**
-More than one error might be displayed when sequencing. Furthermore, the error code displayed might be the sum of two error codes. For example, if the */InstallPath* and */OutputFile* parameters are missing, the Microsoft System Center Application Virtualization Sequencer will return 96—the sum of the two error codes.
-
-
-
-01
-There is an unspecified error.
-
-02
-The specified installation directory (/INSTALLPACKAGE) specified is not valid.
-
-04
-The specified package root directory (/INSTALLPATH) is not valid.
-
-08
-The */OutputFile* parameter that was specified is not valid.
-
-16
-The installation directory (/INSTALLPACKAGE) was not specified.
-
-32
-The package root directory (/INSTALLPATH) was not specified.
-
-64
-The */OutputFile* parameter was not specified.
-
-128
-The specified application virtualization drive is not valid.
-
-256
-The installer failed.
-
-512
-Sequencing the application failed.
-
-1024
-Evaluating installed shortcuts failed.
-
-2048
-The sequenced application package cannot be saved.
-
-4096
-The specified package name (/PACKAGENAME) is not valid.
-
-8192
-The specified block size (/BLOCKSIZE) is not valid.
-
-16384
-The specified compression type (/COMPRESSION) is not valid.
-
-32768
-The specified project path is not valid.
-
-65536
-The specified upgrade parameter is not valid.
-
-131072
-The specified upgrade project parameter is not valid.
-
-262144
-The specified decode path parameter is not valid.
-
-525288
-The package name was not specified.
-
-## Related topics
-
-
-[About Using the Sequencer Command Line](about-using-the-sequencer-command-line.md)
-
-[Command-Line Parameters](command-line-parameters.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/command-line-parameters.md b/mdop/appv-v4/command-line-parameters.md
deleted file mode 100644
index 2c67aced2f..0000000000
--- a/mdop/appv-v4/command-line-parameters.md
+++ /dev/null
@@ -1,97 +0,0 @@
----
-title: Command-Line Parameters
-description: Command-Line Parameters
-author: dansimp
-ms.assetid: d90a0591-f1ce-4cb8-b244-85cc70461922
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Command-Line Parameters
-
-
-Use the following Application Virtualization Sequencer parameters to sequence an application and to upgrade a sequenced application package at the command prompt. In the Microsoft Application Virtualization Sequencer directory, you would enter **SFTSequencer**, followed by the appropriate parameter.
-
-*/HELP* or */?*
-Use to display the list of parameters available for command-line sequencing.
-
-*/INSTALLPACKAGE* or */I*
-Use to specify the installer or a batch file for the application to be sequenced.
-
-*/INSTALLPATH* or */P*
-Use to specify the package root directory.
-
-*/OUTPUTFILE* or */O*
-Use to specify the path and file name of the SPRJ file that will be generated.
-
-**Important**
-The */OUTPUTFILE* parameter is not available when opening a package that you do not intend to upgrade.
-
-
-
-*/FULLLOAD* or */F*
-Use to specify whether to put everything in the primary feature block.
-
-*/PACKAGENAME* or */K*
-Use to specify the package name of the sequenced application.
-
-*/BLOCKSIZE*
-Specifies the SFT file block size that will be used to stream the package to client computers. You can select one of the following values:
-
-- 4 KB
-
-- 16 KB
-
-- 32 KB
-
-- 64 KB
-
-You should consider the size of the SFT file when you specify the block size. A file with a smaller block size takes longer to stream over the network but is less bandwidth-intensive. Files with larger block sizes use more network bandwidth.
-
-*/COMPRESSION*
-Use to specify the method for compressing the SFT file as it is streamed to the client.
-
-*/MSI* or */M*
-Use to specify generating a Microsoft Windows Installer package for the sequenced application.
-
-*/DEFAULT*
-Specifies the default SPRJ file that will be used when creating a virtual application package. This file is used as the .sprj template when the application is sequenced for the first time.
-
-*/UPGRADE*
-Specifies the path and file name of the SPRJ file that will be upgraded.
-
-*/DECODEPATH*
-Specifies the directory on the sequencing computer where the files associated with the sequenced application package are installed. Use one of the following formats when specifying the directory:
-
-- /decodepath:Q:
-
-- /decodepath:Q:.
-
-- /decodepath:”Q:.”
-
-- /decodepath:”Q:”
-
-## Related topics
-
-
-[About Using the Sequencer Command Line](about-using-the-sequencer-command-line.md)
-
-[How to Open a Sequenced Application Using the Command Line](how-to-open-a-sequenced-application-using-the-command-line.md)
-
-[How to Upgrade a Package Using the Open Package Command](how-to-upgrade-a-package-using-the-open-package-command.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/completion-page-package-accelerator.md b/mdop/appv-v4/completion-page-package-accelerator.md
deleted file mode 100644
index 7542c71906..0000000000
--- a/mdop/appv-v4/completion-page-package-accelerator.md
+++ /dev/null
@@ -1,39 +0,0 @@
----
-title: Completion Page
-description: Completion Page
-author: dansimp
-ms.assetid: b2c7776c-2c35-4d25-92b4-6cd8c2bdff42
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Completion Page
-
-
-Use the **Completion** page to review the package completion report. Any issues experienced during sequencing are displayed in the **Successful Virtual Application Package Report** pane. This information is also available in the directory where the package is saved in a file named Report.xml.
-
-This page contains the following elements:
-
-**Close**
-Closes the **Create New Package Wizard**.
-
-## Related topics
-
-
-[Sequencer Wizard - Package Accelerator (AppV 4.6 SP1)](sequencer-wizard---package-accelerator--appv-46-sp1-.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/completion-page.md b/mdop/appv-v4/completion-page.md
deleted file mode 100644
index c733a56d5d..0000000000
--- a/mdop/appv-v4/completion-page.md
+++ /dev/null
@@ -1,34 +0,0 @@
----
-title: Completion Page
-description: Completion Page
-author: dansimp
-ms.assetid: b284d362-b9e1-4d04-88cd-fe9980652188
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Completion Page
-
-
-Always save App-V Package Accelerators and any associated installation media in a secure location on the network to protect App-V Package Accelerators and the installation files from being tampered with or becoming corrupted. Transforms can also contain password and user-specific information so that you must save App-V Package Accelerators in a secure location. You must also digitally sign the Package Accelerator after you create it so the publisher can be verified when the Package Accelerator is applied. A digital signature is an electronic security mark that can help indicate the publisher of the software and whether the package has been tampered with, after the transform was originally signed.
-
-## Related topics
-
-
-[Create Package Accelerator Wizard (AppV 4.6 SP1)](create-package-accelerator-wizard--appv-46-sp1-.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/configure-app.md b/mdop/appv-v4/configure-app.md
deleted file mode 100644
index 407824e6a0..0000000000
--- a/mdop/appv-v4/configure-app.md
+++ /dev/null
@@ -1,90 +0,0 @@
----
-title: CONFIGURE APP
-description: CONFIGURE APP
-author: dansimp
-ms.assetid: fcfb4f86-8b7c-4208-bca3-955fd067079f
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# CONFIGURE APP
-
-
-Enables the user to change the icon associated with an application but does not update the icon on existing shortcuts or file type associations.
-
-`SFTMIME CONFIGURE APP:application /ICON icon-pathname [/LOG log-pathname | /CONSOLE | /GUI]`
-
-
-
-
-
-
-
-
-
Parameter
-
Description
-
-
-
-
-
APP:<application>
-
The name and version (optional) of the application.
-
-
-
/ICON <icon-pathname>
-
The path or URL for the icon file.
-
-
-
/LOG
-
If specified, output is logged to the specified path name.
-
-
-
/CONSOLE
-
If specified, output is presented in the active console window (default).
-
-
-
/GUI
-
If specified, output is presented in a Windows dialog box.
-
-
-
-
-
-
-For version 4.6, the following option has been added.
-
-
-
-
-
-
-
-
-
/LOGU
-
If specified, output is logged to the specified path name in UNICODE format.
User-visible and user-friendly name for the package.
-
-
-
/MANIFEST <manifest-path>
-
The path or URL of the manifest file that lists the applications included in the package and all of their publishing information.
-
-
-
/OVERRIDEURL <URL>
-
The location of the package's SFT file.
-
-
-
/AUTOLOADNEVER
-
Background loading is turned off for the package.
-
-
-
/AUTOLOADONREFRESH
-
Background loading is performed after a publishing refresh.
-
-
-
/AUTOLOADONLOGIN
-
Background loading is performed when a user logs in.
-
-
-
/AUTOLOADONLAUNCH
-
Background loading is performed after a user starts an application from the package.
-
-
-
/AUTOLOADTARGET <target>
-
Indicates which applications from the package will be autoloaded.
-
-
-
NONE
-
No autoloading will be performed despite the presence of any /AUTOLOADONxxx flags.
-
-
-
ALL
-
If an autoload trigger is enabled, all applications in the package will be loaded into cache regardless of whether they have ever been launched.
-
-
-
PREVUSED
-
If an autoload trigger is enabled, the package will load if any applications in this package have previously been started by a user.
-
-
-
/LOG
-
If specified, output is logged to the specified path name.
-
-
-
/CONSOLE
-
If specified, output is presented in the active console window (default).
-
-
-
/GUI
-
If specified, output is presented in a Windows dialog box.
-
-
-
-
-
-
-For version 4.6, the following option has been added.
-
-
-
-
-
-
-
-
-
/LOGU
-
If specified, output is logged to the specified path name in UNICODE format.
-
-
-
-
-
-
-For version 4.6 SP2, the following option has been added.
-
-
-
-
-
-
-
-
-
[/NO-UPDATE-FTA-SHORTCUT {TRUE|FALSE} {/GLOBAL}]
-
If set to TRUE, a registry value is created for the package, either per user, or globally if the /GLOBAL flag is specified.
-
If set to FALSE, the registry value is removed and the file type associations (FTA) for the package are reinstalled.
-
If not specified, normal FTA and shortcut publishing behavior occurs. If you perform any subsequent publishing refresh operations on the App-V 4.6 SP2 client, the shortcuts and FTAs for packages that have this registry value set will not be changed, and the shortcuts and FTAs will not be registered at system startup or user login unless you reset the flag.
-
-
-
/GLOBAL
-
Works in conjunction with the /NO-UPDATE-FTA-SHORTCUT flag. If the /GLOBAL flag is present, it indicates that a registry value will be created for that package for all users. By default, the registry value is created only for this user.
-
-
-
-
-
-
-## Related topics
-
-
-[SFTMIME Command Reference](sftmime--command-reference.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/configure-server.md b/mdop/appv-v4/configure-server.md
deleted file mode 100644
index ed7f5ca4d8..0000000000
--- a/mdop/appv-v4/configure-server.md
+++ /dev/null
@@ -1,114 +0,0 @@
----
-title: CONFIGURE SERVER
-description: CONFIGURE SERVER
-author: dansimp
-ms.assetid: c916eddd-74f2-46e4-953d-120b23284e37
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# CONFIGURE SERVER
-
-
-Enables a user to change the setup of a server; any settings not specified will not be modified.
-
-`SFTMIME CONFIGURE SERVER:server-name [/NAME display-name] [/HOST hostname] [/PORT port] [/PATH path] [/TYPE {HTTP|RTSP}] [/REFRESH {ON|OFF}] [/SECURE] [/LOG log-pathname | /CONSOLE | /GUI]`
-
-
-
-
-
-
-
-
-
Parameter
-
Description
-
-
-
-
-
SERVER:<server-name>
-
The display name for the publishing server.
-
-
-
/NAME <display-name>
-
New display name for the server.
-
-
-
/HOST <hostname>
-
The host name or IP address for the publishing server.
-
-
-
/PORT <port>
-
The port on which the publishing server listens. Defaults to 80 for normal HTTP servers, 443 for HTTP servers using enhanced security, 554 for normal Application Virtualization Servers, and 322 for servers using enhanced security.
-
-
-
/PATH <path>
-
The path portion of the URL used in a publishing request. If the TYPE parameter is set to RTSP, the path is optional and defaults to "/".
-
-
-
/TYPE
-
Indicates whether the publishing server is a Web server ("HTTP") or an Application Virtualization Server ("RTSP").
-
-
-
/REFRESH
-
If set to ON, publishing information will be refreshed when the user logs in. Defaults to ON.
-
-
-
/SECURE
-
If present, indicates that a connection with enhanced security should be established to the publishing server.
-
-
-
/LOG
-
If specified, output is logged to the specified path name.
-
-
-
/CONSOLE
-
If specified, output is presented in the active console window (default).
-
-
-
/GUI
-
If specified, output is presented in a Windows dialog box.
-
-
-
-
-
-
-For version 4.6, the following option has been added.
-
-
-
-
-
-
-
-
-
/LOGU
-
If specified, output is logged to the specified path name in UNICODE format.
-
-
-
-
-
-
-## Related topics
-
-
-[SFTMIME Command Reference](sftmime--command-reference.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/configure-software-page--learn-more-.md b/mdop/appv-v4/configure-software-page--learn-more-.md
deleted file mode 100644
index 87abcb67dd..0000000000
--- a/mdop/appv-v4/configure-software-page--learn-more-.md
+++ /dev/null
@@ -1,42 +0,0 @@
----
-title: Configure Software Page (Learn More)
-description: Configure Software Page (Learn More)
-author: dansimp
-ms.assetid: 9a0cd4a5-88da-4897-a13a-5d21fc04afda
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Configure Software Page (Learn More)
-
-
-Use the **Configure Software** page to run each program to complete any configuration tasks after the installation. For example, this step helps configure any associated application license agreements.
-
-This page contains the following elements:
-
-**Run Selected**
-Opens only the selected programs associated with the application.
-
-**Run All**
-Opens all programs associated with the application.
-
-## Related topics
-
-
-[Create New Package Wizard (AppV 4.6 SP1)](create-new-package-wizard---appv-46-sp1-.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/configure-software-page-app-v-46-sp1.md b/mdop/appv-v4/configure-software-page-app-v-46-sp1.md
deleted file mode 100644
index 7d201afb8d..0000000000
--- a/mdop/appv-v4/configure-software-page-app-v-46-sp1.md
+++ /dev/null
@@ -1,42 +0,0 @@
----
-title: Configure Software Page
-description: Configure Software Page
-author: dansimp
-ms.assetid: 50596eba-ce20-4d36-8e57-bd4b6c6cf92e
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Configure Software Page
-
-
-Use the **Configure Software** page to manage the application first-use tasks.
-
-This page contains the following elements:
-
-**Configure Software**
-Click **Configure Software** to manually configure application first-use tasks. Selecting this option can increase the overall sequencing time depending on the size of the package you are creating.
-
-**Skip this step**
-Click **Skip this step** to skip configuring the application. If you choose to skip this step, end users have to perform any required first-use tasks such as accepting any license agreements and first-use questions.
-
-## Related topics
-
-
-[Sequencer Wizard - Package Accelerator (AppV 4.6 SP1)](sequencer-wizard---package-accelerator--appv-46-sp1-.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/configure-type.md b/mdop/appv-v4/configure-type.md
deleted file mode 100644
index 42307e58cb..0000000000
--- a/mdop/appv-v4/configure-type.md
+++ /dev/null
@@ -1,126 +0,0 @@
----
-title: CONFIGURE TYPE
-description: CONFIGURE TYPE
-author: dansimp
-ms.assetid: 2caf9433-5449-486f-ab94-83ee8e44d7f1
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# CONFIGURE TYPE
-
-
-Enables the user to change settings for a file type association.
-
-`SFTMIME CONFIGURE TYPE:file-extension [/GLOBAL] [/APP application] [/ICON icon-pathname] [/DESCRIPTION type-desc] [/CONTENT-TYPE content-type] [/PERCEIVED-TYPE perceived-type] [/PROGID progid] [/CONFIRMOPEN {YES|NO}] [/SHOWEXT {YES|NO}] [/NEWMENU {YES|NO}] [/LOG log-pathname | /CONSOLE | /GUI]`
-
-
-
-
-
-
-
-
-
Parameter
-
Description
-
-
-
-
-
TYPE:<file-extension>
-
The file name extension to be configured.
-
-
-
/APP <application>
-
The name and version (optional) of the application to associate this file type with. Cannot be specified with PROGID.
-
-
-
/ICON <icon-pathname>
-
The path or URL for the icon file.
-
-
-
/DESCRIPTION <type-desc>
-
The user-friendly name for the file type.
-
-
-
/CONTENT-TYPE <content-type>
-
The content type of the file.
-
-
-
/GLOBAL
-
If present, indicates that the association that applies to all users should be edited, not the user-specific one.
-
-
-
/PERCEIVED-TYPE <perceived-type>
-
The perceived type of the file.
-
-
-
/PROGID <progid>
-
Indicates that the extension should be associated with a different file type. The previous file type is not deleted. Cannot be specified with APP, ICON, DESCRIPTION, CONFIRMOPEN, or SHOWEXT.
-
-
-
/CONFIRMOPEN
-
Indicates whether users downloading a file of this type should be asked whether to open or save the file.
-
-
-
/SHOWEXT
-
Indicates whether the file's extension should always be shown, even if the user has requested that all extensions be hidden.
-
-
-
/NEWMENU
-
Indicates whether an entry should be added to the shell's New menu.
-
-
-
/LOG
-
If specified, output is logged to the specified path name.
-
-
-
/CONSOLE
-
If specified, output is presented in the active console window (default).
-
-
-
/GUI
-
If specified, output is presented in a Windows dialog box.
-
-
-
-
-
-
-For version 4.6, the following option has been added.
-
-
-
-
-
-
-
-
-
/LOGU
-
If specified, output is logged to the specified path name in UNICODE format.
-
-
-
-
-
-
-## Related topics
-
-
-[SFTMIME Command Reference](sftmime--command-reference.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/configuring-app-v-administration-for-a-distributed-environment.md b/mdop/appv-v4/configuring-app-v-administration-for-a-distributed-environment.md
deleted file mode 100644
index 1fe3f100c5..0000000000
--- a/mdop/appv-v4/configuring-app-v-administration-for-a-distributed-environment.md
+++ /dev/null
@@ -1,64 +0,0 @@
----
-title: Configuring App-V Administration for a Distributed Environment
-description: Configuring App-V Administration for a Distributed Environment
-author: dansimp
-ms.assetid: 53971fa9-8319-435c-be74-c37feb9af1da
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 08/30/2016
----
-
-
-# Configuring App-V Administration for a Distributed Environment
-
-
-When designing the infrastructure for your specific organization, you can install the App-V Management Web Service on a computer other than the computer where you install the App-V Management Server. Common reasons for separating these App-V components include the following:
-
-- Performance
-
-- Reliability
-
-- Availability
-
-- Scalability
-
-Separating the Management Server and Management Web Service requires additional configuration for the infrastructure to operate correctly. When you separate these two features but do not complete the procedures described in this topic, the Management Console will connect to the Management Web Service but will not be able to properly authenticate with the data store. The Management Console will not load properly, and the administrator will not be able to complete any administrative tasks.
-
-This behavior occurs because the Management Web Service cannot use the credentials, passed to it from the Management Console, to access the data store. The solution is to configure the Management Web Service server to be “Trusted for delegation.”
-
-## Configuring Active Directory Domain Services
-
-
-It is also necessary to configure Active Directory Domain Services properly to work in a distributed environment. This section includes the information you need configure Active Directory Domain Services.
-
-### When SQL Service Uses Local System account
-
-To set up the environment where the SQL Service uses the local system account, change the properties of the machine account of the Management Web Service to be trusted for delegation. For detailed procedures about how to do this, see [How to Configure the Server to be Trusted for Delegation](how-to-configure-the-server-to-be-trusted-for-delegation.md)
-
-### When SQL Service Uses Domain-Based Account
-
-To set up the environment where SQL Servers use domain-based service accounts, you need to consider whether or not a variety of factors apply, including the following:
-
-- Clustering of SQL Server
-
-- Replication
-
-- Automated tasks
-
-- Linked servers
-
-For information about configuring Active Directory Domain Services when the SQL service uses a domain-based account, see .
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/configuring-app-v-for-secure-administration.md b/mdop/appv-v4/configuring-app-v-for-secure-administration.md
deleted file mode 100644
index a71fffa3c7..0000000000
--- a/mdop/appv-v4/configuring-app-v-for-secure-administration.md
+++ /dev/null
@@ -1,42 +0,0 @@
----
-title: Configuring App-V for Secure Administration
-description: Configuring App-V for Secure Administration
-author: dansimp
-ms.assetid: 4543fa81-c8cc-4b10-83b7-060778eb1349
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Configuring App-V for Secure Administration
-
-
-In an environment where securing administrative operations is important, App-V allows for secure communication between the App-V Web Management Service and the App-V Management Console. Because the Management Service is a Web-based application, it requires securing the App-V Management Server application on the Web server that hosts the Management Service. As shown in the following illustration, this process includes using HTTPS for communication and configuring the IIS server to allow only Windows Integrated Authentication.
-
-
-
-The App-V Web Management Service is installed as a Web-based application on IIS. For the Web Management Service to support secure (SSL) connections between the App-V Management Console and the Web Management Service, you will need to configure the IIS server where the Web Management Service is installed and configure the App-V Management Console.
-
-## In This Section
-
-
-[Configuring Certificates to Support the App-V Web Management Service](configuring-certificates-to-support-the-app-v-web-management-service.md)
-Provides helpful information about configuring certificates to support SSL-based connections, to help secure communication for the App-V Web Management Service.
-
-[How to Install and Configure the App-V Management Console for a More Secure Environment](how-to-install-and-configure-the-app-v-management-console-for-a-more-secure-environment.md)
-Provides a step-by-step procedure for connecting to an App-V Web Management Service by using a secure connection.
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/configuring-certificates-to-support-app-v-management-server-or-streaming-server.md b/mdop/appv-v4/configuring-certificates-to-support-app-v-management-server-or-streaming-server.md
deleted file mode 100644
index fe8ec7d8bc..0000000000
--- a/mdop/appv-v4/configuring-certificates-to-support-app-v-management-server-or-streaming-server.md
+++ /dev/null
@@ -1,61 +0,0 @@
----
-title: Configuring Certificates to Support App-V Management Server or Streaming Server
-description: Configuring Certificates to Support App-V Management Server or Streaming Server
-author: dansimp
-ms.assetid: 2f24e550-585e-4b7e-b486-22a3f181f543
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 08/30/2016
----
-
-
-# Configuring Certificates to Support App-V Management Server or Streaming Server
-
-
-After you complete the certificate provisioning process and change the private key permissions to support the App-V installation, you can launch the setup of the Management Server or the Streaming Server. During setup, if a certificate is provisioned before running the setup program, the wizard displays the certificate in the **Connection Security Mode** screen and, by default, the **Use enhanced security** check box is selected.
-
-**Note**
-Select the certificate that was configured for App-V if there is more than one certificate provisioned for this server.
-
-
-
-**Important**
-When upgrading from version 4.2 to version 4.5, the setup has an option for **Use enhanced security**; however, selecting this option will not disable streaming over RTSP. You must use the Management Console to disable RTSP after installation.
-
-
-
-Select the TCP port that the service will use for client communications. The default port is TCP 322; however, you can change the port to a custom port for your environment.
-
-The remaining steps of the wizard are the same as if you were deploying an App-V Management or Streaming Server without using the **Enhanced security** feature.
-
-## Configuring Certificates for NLB Environments
-
-
-To support large enterprises, often the Management Server is placed into a Network Load Balancing (NLB) cluster to support the large number of connections. This requires at least two Management Servers that appear to be a single Management Server. When your environment uses an NLB cluster with several Management Servers, you need an advanced configuration of the certificate used for the NLB cluster.
-
-The App-V certificate is submitted to a certification authority (CA) that is configured on a computer running Windows Server 2003. The SAN lets you connect to a specific Management Server NLB cluster host name by using a Domain Name System (DNS) name that might differ from the actual computer names, because there can be up to 32 servers that comprise the NLB cluster.
-
-This configuration is necessary only when using an NLB cluster. When the client connects to the server, it will connect using the fully qualified domain name (FQDN) of the NLB cluster and not the FQDN of an individual server. If you do not add the SAN property with the FQDN of the server nodes in the cluster, all client connections are refused because the common name of the certificate won’t match the server name.
-
-For more detailed information about configuring certificates with the SAN attribute, see .
-
-## Related topics
-
-
-[Configuring Certificates to Support Secure Streaming](configuring-certificates-to-support-secure-streaming.md)
-
-[How to Modify Private Key Permissions to Support Management Server or Streaming Server](how-to-modify-private-key-permissions-to-support-management-server-or-streaming-server.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/configuring-certificates-to-support-secure-streaming.md b/mdop/appv-v4/configuring-certificates-to-support-secure-streaming.md
deleted file mode 100644
index 86f2485e5c..0000000000
--- a/mdop/appv-v4/configuring-certificates-to-support-secure-streaming.md
+++ /dev/null
@@ -1,57 +0,0 @@
----
-title: Configuring Certificates to Support Secure Streaming
-description: Configuring Certificates to Support Secure Streaming
-author: dansimp
-ms.assetid: 88dc76d8-7745-4729-92a1-af089c921244
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 08/30/2016
----
-
-
-# Configuring Certificates to Support Secure Streaming
-
-
-By default, the App-V service runs under the Network Service account. However, you can create a service account in Active Directory Domain Services and replace the Network Service account with the Active Directory Domain account.
-
-The security context under which the service runs is important for configuring enhanced secure communications. This security context must have read permissions for the certificate private key. When a PKCS\#10 *Certificate Signing Request* (CSR) is generated for the App-V server, the Windows *Cryptographic Service Provider* is called and a private key is generated. The private key is secured with permissions given to the System and Administrator accounts only.
-
-You must modify the access control lists (ACLs) on the private key to let the App-V Management or Streaming Server access the private key required for successful TLS secured communication.
-
-## Obtaining and Installing a Certificate
-
-
-The scenarios for obtaining and installing a certificate for App-V are as follows:
-
-- Internal public key infrastructure (PKI).
-
-- Third-party certificate issuing certification authority (CA).
-
- **Note**
- If you need to obtain a certificate from a third-party CA, follow the documentation available on that CA’s Web site.
-
-
-
-If a PKI infrastructure has been deployed, consult with the PKI administrators to acquire a certificate that complies with the requirements described in this topic. If a PKI infrastructure is not available, use a third-party CA to obtain a valid certificate.
-
-For step-by-step guidance for obtaining and installing a certificate, see .
-
-## Related topics
-
-
-Configuring Certificates to Support Secure Streaming
-[How to Modify Private Key Permissions to Support Management Server or Streaming Server](how-to-modify-private-key-permissions-to-support-management-server-or-streaming-server.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/configuring-certificates-to-support-the-app-v-web-management-service.md b/mdop/appv-v4/configuring-certificates-to-support-the-app-v-web-management-service.md
deleted file mode 100644
index 7999d55e32..0000000000
--- a/mdop/appv-v4/configuring-certificates-to-support-the-app-v-web-management-service.md
+++ /dev/null
@@ -1,51 +0,0 @@
----
-title: Configuring Certificates to Support the App-V Web Management Service
-description: Configuring Certificates to Support the App-V Web Management Service
-author: dansimp
-ms.assetid: b7960161-2c19-4cbf-a98a-d4b06f547dce
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 08/30/2016
----
-
-
-# Configuring Certificates to Support the App-V Web Management Service
-
-
-The App-V Web Management Service must be configured to support SSL-based connections to help secure the communication. This process requires that the Web server or computer on which the Management Service is installed has a certificate issued to the service or computer.
-
-The following scenarios illustrate how to obtain a certificate for this purpose:
-
-1. The company infrastructure already has a public key infrastructure (PKI) in place that automatically issues certificates to computers.
-
-2. The company infrastructure already has a PKI in place, although it does not automatically issue certificates to computers.
-
-3. The company infrastructure has no PKI in place.
-
-In each of the preceding scenarios, the method for obtaining a certificate is different, but the end result is the same. The administrator must assign a certificate to the IIS Default Web Site and configure the App-V Web Management Service to require secure communications.
-
-**Important**
-The name of the certificate must match the name of the server. It is a best practice to use fully qualified domain names (FQDNs) for the common name of the certificate.
-
-
-
-App-V can use IIS servers to support different infrastructure configurations. For more information about configuring IIS servers to support HTTPS, see .
-
-## Related topics
-
-
-[How to Install and Configure the App-V Management Console for a More Secure Environment](how-to-install-and-configure-the-app-v-management-console-for-a-more-secure-environment.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/configuring-iis-for-secure-streaming.md b/mdop/appv-v4/configuring-iis-for-secure-streaming.md
deleted file mode 100644
index 1e5c0be5b8..0000000000
--- a/mdop/appv-v4/configuring-iis-for-secure-streaming.md
+++ /dev/null
@@ -1,65 +0,0 @@
----
-title: Configuring IIS for Secure Streaming
-description: Configuring IIS for Secure Streaming
-author: dansimp
-ms.assetid: 9a80a703-4642-4bec-b7af-dc7cb6b76925
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 08/30/2016
----
-
-
-# Configuring IIS for Secure Streaming
-
-
-With the release of Microsoft Application Virtualization (App-V) version 4.5, you can use HTTP and HTTPS as protocols for streaming application packages to the App-V clients. This option enables organizations to leverage the additional scalability that IIS typically offers. When you use IIS as a streaming server, you can help secure the communications between the client and server by using HTTPS instead of HTTP.
-
-**Note**
-If you want to stream applications from a file server, you should enhance the security of the communications to the application packages. This can be achieved using IPsec. For more information see the following topics in the TechNet Library:
-
-- For Windows Server 2003,
-
-- For Windows Server 2008,
-
-
-
-## MIME Types
-
-
-When you use IIS to stream virtual applications with HTTP or HTTPS, to support App-V, the following MIME types must be added to the IIS server:
-
-- .OSD=TXT
-
-- .SFT=Binary
-
-Use the following KB articles as guidance for adding MIME types:
-
-IIS 6.0:
-
-IIS 7.0:
-
-## Kerberos Authentication
-
-
-When you use HTTP or HTTPS and Kerberos authentication to stream ICO, OSD, or SFT files, you are enhancing the security of your environment. However, for IIS to support Kerberos authentication, you must configure a proper Service Principal Name (SPN). The `setspn.exe` tool is available for Windows Server 2003 from the Support Tools on the installation CD and is built-in to Windows Server 2008.
-
-To create an SPN, run `setspn.exe` from a command prompt while logged in as a member of Domain Administrators—for example, `setspn.exe –A HTTP/FQDN of Server ServerName`.
-
-## Related topics
-
-
-[Configuring Management or Streaming Server for Secure Communications Post-Installation](configuring-management-or-streaming-server-for-secure-communications-post-installation.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/configuring-management-or-streaming-server-for-secure-communications-post-installation.md b/mdop/appv-v4/configuring-management-or-streaming-server-for-secure-communications-post-installation.md
deleted file mode 100644
index 022b096208..0000000000
--- a/mdop/appv-v4/configuring-management-or-streaming-server-for-secure-communications-post-installation.md
+++ /dev/null
@@ -1,41 +0,0 @@
----
-title: Configuring Management or Streaming Server for Secure Communications Post-Installation
-description: Configuring Management or Streaming Server for Secure Communications Post-Installation
-author: dansimp
-ms.assetid: 1062a213-470b-4ae2-b12f-b3e28a6ab745
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Configuring Management or Streaming Server for Secure Communications Post-Installation
-
-
-If the proper certificate was not provisioned before the installation of the App-V Management Server or the App-V Streaming Server, App-V can be configured for enhanced security after the initial installation. You can configure the App-V Management Server through the App-V Management Console. However, the App-V Streaming Server is managed through the registry. In either case, the certificate must include the proper *extended key usage* (EKU) for Server authentication and the Network Service must have read access to the private key.
-
-## In This Section
-
-
-[How to Configure Management Server Security Post-Installation](how-to-configure-management-server-security-post-installation.md)
-Provides a procedure that can be performed post-installation, using the App-V Management Console, to add the certificate and configure the App-V Management Server for enhanced security.
-
-[How to Configure Streaming Server Security Post-Installation](how-to-configure-streaming-server-security-post-installation.md)
-Provides a procedure that can be performed post-installation, to add the certificate and configure the App-V Streaming Server for enhanced security.
-
-[Troubleshooting Certificate Permission Issues](troubleshooting-certificate-permission-issues.md)
-Provides troubleshooting guidance for when the private key has not been configured with the proper ACL for the Network Service.
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/configuring-prerequisite-groups-in-active-directory-for-app-v.md b/mdop/appv-v4/configuring-prerequisite-groups-in-active-directory-for-app-v.md
deleted file mode 100644
index 92700f1f2a..0000000000
--- a/mdop/appv-v4/configuring-prerequisite-groups-in-active-directory-for-app-v.md
+++ /dev/null
@@ -1,74 +0,0 @@
----
-title: Configuring Prerequisite Groups in Active Directory for App-V
-description: Configuring Prerequisite Groups in Active Directory for App-V
-author: dansimp
-ms.assetid: 0010d534-46c0-44a3-b5c1-621b4d5e2c31
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Configuring Prerequisite Groups in Active Directory for App-V
-
-
-Before you install the Microsoft Application Virtualization (App-V) Management Server, you must create the following objects in Active Directory. App-V uses Active Directory groups to control access to applications and administrative functions. You will use these groups during the server installation process and when publishing applications.
-
-## Configuring Prerequisite Groups in Active Directory for Application Virtualization
-
-
-This table lists the Active Directory groups that are required for installing App-V.
-
-
-
-
-
-
-
-
-
Object
-
Description
-
-
-
-
-
Organizational Unit (OU)
-
Create an OU in Active Directory for the specific groups required for App-V.
-
-
-
App-V Administrative Group
-
During installation of the App-V Management Server, you must select an Active Directory group to use as the App-V Administrators group to control administrative access to the Management Console. Create a security group for App-V administrators, and add to this group every user who needs to use the Management Console. You cannot create this group directly from the App-V Management Server installer.
-
-
-
App-V Users Group
-
App-V requires that every User account that accesses App-V functions be a member of a provider policy associated with a single group for general platform access. Use an existing group; for example, Domain Users, if all users are to have access to App-V, or create a new group.
-
-
-
Application Groups
-
App-V associates the right to use an individual application with an Active Directory group. Create an Active Directory group for each application, and assign users to these groups as needed to control user access to the applications.
-
-
-
-
-
-
-## Related topics
-
-
-[Application Virtualization Deployment Requirements](application-virtualization-deployment-requirements.md)
-
-[How to Configure Windows Server 2008 for App-V Management Servers](how-to-configure-windows-server-2008-for-app-v-management-servers.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/configuring-the-application-virtualization-sequencer--app-v-46-sp1-.md b/mdop/appv-v4/configuring-the-application-virtualization-sequencer--app-v-46-sp1-.md
deleted file mode 100644
index f8ec256bdd..0000000000
--- a/mdop/appv-v4/configuring-the-application-virtualization-sequencer--app-v-46-sp1-.md
+++ /dev/null
@@ -1,43 +0,0 @@
----
-title: Configuring the Application Virtualization Sequencer (App-V 4.6 SP1)
-description: Configuring the Application Virtualization Sequencer (App-V 4.6 SP1)
-author: dansimp
-ms.assetid: af775165-5b99-4c74-807f-f504377c7be4
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Configuring the Application Virtualization Sequencer (App-V 4.6 SP1)
-
-
-Use any of the following links for more information about configuring the App-V Sequencer.
-
-## In This Section
-
-
-[How to Install the Sequencer (App-V 4.6 SP1)](how-to-install-the-sequencer---app-v-46-sp1-.md)
-Describes how to install the App-V Sequencer.
-
-[How to Create an App-V Project Template (App-V 4.6 SP1)](how-to-create-an-app-v-project-template--app-v-46-sp1-.md)
-Describes how to create a project template.
-
-## Related topics
-
-
-[Tasks for the Application Virtualization Sequencer (App-V 4.6 SP1)](tasks-for-the-application-virtualization-sequencer--app-v-46-sp1-.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/configuring-the-application-virtualization-sequencer.md b/mdop/appv-v4/configuring-the-application-virtualization-sequencer.md
deleted file mode 100644
index 571b263abc..0000000000
--- a/mdop/appv-v4/configuring-the-application-virtualization-sequencer.md
+++ /dev/null
@@ -1,51 +0,0 @@
----
-title: Configuring the Application Virtualization Sequencer
-description: Configuring the Application Virtualization Sequencer
-author: dansimp
-ms.assetid: cae1c368-9fcd-454e-8fc9-0893345d55bf
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Configuring the Application Virtualization Sequencer
-
-
-To configure your environment for the Microsoft Application Virtualization (App-V) Sequencer, you need to perform certain tasks.
-
-Click any link in the following section for information about configuring your environment for running the Sequencer.
-
-## In This Section
-
-
-[How to Install the Sequencer](how-to-install-the-sequencer.md)
-Contains the steps for installing the App-V Sequencer.
-
-[How to Create the Package Root Directory](how-to-create-the-package-root-directory.md)
-Contains the steps necessary to configure the directory where sequenced applications will be installed.
-
-[How to Modify the Location of the Log Directory](how-to-modify-the-location-of-the-log-directory.md)
-Contains the steps necessary to configure where the Sequencer logs will be saved.
-
-[How to Modify the Location of the Scratch Directory](how-to-modify-the-location-of-the-scratch-directory.md)
-Contains the steps necessary to configure the location where the Sequencer temporarily stores files during sequencing.
-
-## Related topics
-
-
-[Application Virtualization Sequencer Online Help](application-virtualization-sequencer-online-help.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/configuring-the-firewall-for-the-app-v-servers.md b/mdop/appv-v4/configuring-the-firewall-for-the-app-v-servers.md
deleted file mode 100644
index 688c137ae2..0000000000
--- a/mdop/appv-v4/configuring-the-firewall-for-the-app-v-servers.md
+++ /dev/null
@@ -1,46 +0,0 @@
----
-title: Configuring the Firewall for the App-V Servers
-description: Configuring the Firewall for the App-V Servers
-author: dansimp
-ms.assetid: f779c450-6c6f-46a8-ac66-5e82e0689d55
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Configuring the Firewall for the App-V Servers
-
-
-After you install the Microsoft Application Virtualization (App-V) Management Server or Streaming Server and configure it to use the RTSP or RTSPS protocol, you must create firewall exceptions for the App-V programs.
-
-## Configuring Firewall Exceptions for Application Virtualization Management Server
-
-
-Create a firewall exception for **sghwdsptr.exe** and **sghwsvr.exe**. These programs are found in the folder C:\\Program Files\\Microsoft System Center App Virt Management Server\\App Virt Management Server\\bin on a 32-bit operating system. If you are using a 64-bit operating system version, the folder is located under C:\\Program Files (x86)\\Microsoft System Center App Virt Management Server\\App Virt Management Server\\bin.
-
-## Configuring Firewall Exceptions for Application Virtualization Streaming Server
-
-
-Create a firewall exception for **sglwdsptr.exe** and **sglwsvr.exe**. These programs are found in the folder C:\\Program Files\\Microsoft System Center App Virt Streaming Server\\App Virt Streaming Server\\bin on a 32-bit operating system. If you are using a 64-bit operating system version, the folder is located under C:\\Program Files (x86)\\Microsoft System Center App Virt Streaming Server\\App Virt Streaming Server\\bin.
-
-## Related topics
-
-
-[How to Configure Servers for Server-Based Deployment](how-to-configure-servers-for-server-based-deployment.md)
-
-[How to Install and Configure the Default Application](how-to-install-and-configure-the-default-application.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/configuring-windows-firewall-for-app-v.md b/mdop/appv-v4/configuring-windows-firewall-for-app-v.md
deleted file mode 100644
index f97d412295..0000000000
--- a/mdop/appv-v4/configuring-windows-firewall-for-app-v.md
+++ /dev/null
@@ -1,38 +0,0 @@
----
-title: Configuring Windows Firewall for App-V
-description: Configuring Windows Firewall for App-V
-author: dansimp
-ms.assetid: 6b5e253c-473f-4afc-a48b-631eda11d9ca
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Configuring Windows Firewall for App-V
-
-
-Securing the communication between components in an App-V infrastructure is only one element in securing the environment. Using a firewall program on the server can help reduce the attack surface area. The topics in this section provide procedures for configuring Windows built-in firewall capabilities that support App-V. These procedures assume that you installed a Management Server and that it has been configured for RTSPS communication. Notes are included in the procedures for Streaming Servers and environments where RTSP is being used for communication.
-
-## In This Section
-
-
-[How to Configure Windows Server 2003 Firewall for App-V](how-to-configure-windows-server-2003-firewall-for-app-v.md)
-Provides a procedure you can use to configure the Windows Server 2003 firewall for App-V.
-
-[How to Configure Windows Server 2008 Firewall for App-V](how-to-configure-windows-server-2008-firewall-for-app-v.md)
-Provides a procedure you can use to configure the Windows Server 2008 firewall for App-V.
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/create-new-package-wizard---appv-46-sp1-.md b/mdop/appv-v4/create-new-package-wizard---appv-46-sp1-.md
deleted file mode 100644
index 11cb5f957c..0000000000
--- a/mdop/appv-v4/create-new-package-wizard---appv-46-sp1-.md
+++ /dev/null
@@ -1,59 +0,0 @@
----
-title: Create New Package Wizard (AppV 4.6 SP1)
-description: Create New Package Wizard (AppV 4.6 SP1)
-author: dansimp
-ms.assetid: 1f73d044-b364-4c95-8ae1-daedd316d87e
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Create New Package Wizard (AppV 4.6 SP1)
-
-
-Use any of the following links for more information about the App-V Create New Package wizard.
-
-## In This Section
-
-
-[Packaging Method Page (Learn More)](packaging-method-page--learn-more-.md)
-
-[Prepare Computer Page (Learn More)](prepare-computer-page--learn-more-.md)
-
-[Type of Application Page (Learn More)](type-of-application-page--learn-more-.md)
-
-[Select Installer Page (Learn More)](select-installer-page--learn-more-.md)
-
-[Package Name Page (Learn More)](package-name-page---learn-more-.md)
-
-[Installation Page (Learn More)](installation-page--learn-more-.md)
-
-[Configure Software Page (Learn More)](configure-software-page--learn-more-.md)
-
-[Installation Files Page](installation-files-page.md)
-
-[Installation Report Page (Learn More)](installation-report-page--learn-more-.md)
-
-[Customize Page (Learn More)](customize-page--learn-more-.md)
-
-[Select Primary Page (Learn More)](select-primary-page--learn-more-.md)
-
-## Related topics
-
-
-[Wizard Pages (AppV 4.6 SP1)](wizard-pages--appv-46-sp1-.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/create-package-accelerator--review-errors--page.md b/mdop/appv-v4/create-package-accelerator--review-errors--page.md
deleted file mode 100644
index 63cdf9f7e1..0000000000
--- a/mdop/appv-v4/create-package-accelerator--review-errors--page.md
+++ /dev/null
@@ -1,39 +0,0 @@
----
-title: Create Package Accelerator (Review Errors) Page
-description: Create Package Accelerator (Review Errors) Page
-author: dansimp
-ms.assetid: ea3f531d-1887-4b42-a30f-b875d0ccb916
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Create Package Accelerator (Review Errors) Page
-
-
-Use the **Completion** page to review the Package Accelerator completion report. Any issues experienced during sequencing are displayed.
-
-This page contains the following elements:
-
-**Close**
-Closes the **Create Package Accelerator** wizard.
-
-## Related topics
-
-
-[Sequencer Wizard - Package Accelerator (AppV 4.6 SP1)](sequencer-wizard---package-accelerator--appv-46-sp1-.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/create-package-accelerator-page.md b/mdop/appv-v4/create-package-accelerator-page.md
deleted file mode 100644
index 2d86172bf5..0000000000
--- a/mdop/appv-v4/create-package-accelerator-page.md
+++ /dev/null
@@ -1,39 +0,0 @@
----
-title: Create Package Accelerator Page
-description: Create Package Accelerator Page
-author: dansimp
-ms.assetid: 51cdc262-beda-4a4f-bb3e-66458062a7bd
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Create Package Accelerator Page
-
-
-Use the **Create Package Accelerator** page to specify the location where to save the Package Accelerator.
-
-This page contains the following elements:
-
-**Browse**
-Click **Browse** to specify the location where to save the Package Accelerator.
-
-## Related topics
-
-
-[Create Package Accelerator Wizard (AppV 4.6 SP1)](create-package-accelerator-wizard--appv-46-sp1-.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/create-package-accelerator-wizard--appv-46-sp1-.md b/mdop/appv-v4/create-package-accelerator-wizard--appv-46-sp1-.md
deleted file mode 100644
index 65aba0176a..0000000000
--- a/mdop/appv-v4/create-package-accelerator-wizard--appv-46-sp1-.md
+++ /dev/null
@@ -1,57 +0,0 @@
----
-title: Create Package Accelerator Wizard (AppV 4.6 SP1)
-description: Create Package Accelerator Wizard (AppV 4.6 SP1)
-author: dansimp
-ms.assetid: 976d84e1-86d7-4a9b-a747-2b6eef790c1f
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Create Package Accelerator Wizard (AppV 4.6 SP1)
-
-
-Use any of the following links for more information about the use of page elements in the App-V Create Package Accelerator wizard.
-
-## In This Section
-
-
-[About Sharing Package Accelerators Page](about-sharing-package-accelerators-page.md)
-
-[Select Package (Learn More) Page](select-package--learn-more--page.md)
-
-[Installation Files Page](installation-files-page.md)
-
-[Gathering Information Page (Learn More)](gathering-information-page--learn-more-.md)
-
-[Select Files Page](select-files-page.md)
-
-[Verify Applications Page (Package Accelerators)](verify-applications-page--package-accelerators-.md)
-
-[Select Guidance Page (Package Accelerators)](select-guidance-page--package-accelerators-.md)
-
-[Create Package Accelerator Page](create-package-accelerator-page.md)
-
-[Completion Page](completion-page.md)
-
-[Create Package Accelerator (Review Errors) Page](create-package-accelerator--review-errors--page.md)
-
-## Related topics
-
-
-[Wizard Pages (AppV 4.6 SP1)](wizard-pages--appv-46-sp1-.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/create-package-page--app-v-46-sp1.md b/mdop/appv-v4/create-package-page--app-v-46-sp1.md
deleted file mode 100644
index cfd5f7b2fc..0000000000
--- a/mdop/appv-v4/create-package-page--app-v-46-sp1.md
+++ /dev/null
@@ -1,50 +0,0 @@
----
-title: Create Package Page
-description: Create Package Page
-author: dansimp
-ms.assetid: dd7a8709-74cc-459a-88ac-b63d8dcf2ddf
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Create Package Page
-
-
-Use the **Create Package** page to add optional comments and to specify where the package will be saved. You can also specify whether the package should be compressed. After you have configured the options on this page, click **Create** to create the new virtual application package.
-
-This page contains the following elements:
-
-**Comments**
-Add optional comments that will be associated with the new virtual application package. The comments that you add help identify the purpose or version of the virtual application package.
-
-**Save Location**
-Click **Browse** and specify to which location you want to save the package (.**sprj** file).
-
-**Compress Package**
-Select the **Compress Package** check box to compress the package, which can help enhance package streaming to target computers. We recommend that you select this option for packages that are larger than 4 GB. The current uncompressed package size is also displayed.
-
-**Note**
-If the original package size is more than 4 GB and compressed, by default, the checkbox is checked and cannot be changed. If the original package is compressed and less than 4 GB, the check box is checked, but can be cleared.
-
-
-
-## Related topics
-
-
-[Sequencer Wizard - Package Accelerator (AppV 4.6 SP1)](sequencer-wizard---package-accelerator--appv-46-sp1-.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/customize-page--learn-more-.md b/mdop/appv-v4/customize-page--learn-more-.md
deleted file mode 100644
index 0bed35f090..0000000000
--- a/mdop/appv-v4/customize-page--learn-more-.md
+++ /dev/null
@@ -1,48 +0,0 @@
----
-title: Customize Page (Learn More)
-description: Customize Page (Learn More)
-author: dansimp
-ms.assetid: 893df614-7058-4fcf-ba34-d0f16c856374
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Customize Page (Learn More)
-
-
-Use the **Customize** page to finish creating the virtual application package or to configure the virtual application package further.
-
-This page contains the following elements:
-
-**Stop Now**
-Creates a basic virtual application package. If you select this option, the package creation will finish, and the package will be available in the Sequencer console.
-
-**Customize**
-Enables you to configure the virtual application package further. You can perform the following configuration items:
-
-- **Edit Shortcuts**. Add, remove, or change the shortcuts, and configure the file type associations associated with the virtual application package that will be created on target computers.
-
-- **Prepare virtual application package for streaming to improve the initial end user experience**. Optimize the virtual application package for streaming across the network.
-
-- **Restrict operating systems that can run this package**. Specify the operating systems that can run the virtual application package.
-
-## Related topics
-
-
-[Create New Package Wizard (AppV 4.6 SP1)](create-new-package-wizard---appv-46-sp1-.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/defender-running-dialog-box--app-v-46-sp1-.md b/mdop/appv-v4/defender-running-dialog-box--app-v-46-sp1-.md
deleted file mode 100644
index a4d6ce5126..0000000000
--- a/mdop/appv-v4/defender-running-dialog-box--app-v-46-sp1-.md
+++ /dev/null
@@ -1,42 +0,0 @@
----
-title: Defender Running Dialog Box (App-V 4.6 SP1)
-description: Defender Running Dialog Box (App-V 4.6 SP1)
-author: dansimp
-ms.assetid: 716ec7f9-ddad-45dd-a3c7-4a9d81cfcfd0
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Defender Running Dialog Box (App-V 4.6 SP1)
-
-
-Microsoft Windows Defender is running. You should stop Windows Defender before continuing with the installation. Windows Defender can interfere with creation of a package by accessing files that must be added to the virtual application package or by adding extraneous data to the virtual application package.
-
-Use the following procedure to stop Microsoft Windows Defender from running during sequencing.
-
-1. On the computer running the App-V Sequencer, click **Start**, right-click **Computer**, and then click **Manage**.
-
-2. In the **Computer Management** console, double click **Services and Applications**, and then double-click **Services** to expand **Services**.
-
-3. Locate it in the list. Right-click Windows Defender, click **Stop** to stop Microsoft Windows Defender, and then click **Ok**.
-
-## Related topics
-
-
-[Dialog Boxes (AppV 4.6 SP1)](dialog-boxes--appv-46-sp1-.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/defrag-running-dialog-box--app-v-46-sp1-.md b/mdop/appv-v4/defrag-running-dialog-box--app-v-46-sp1-.md
deleted file mode 100644
index 0fc1fd41be..0000000000
--- a/mdop/appv-v4/defrag-running-dialog-box--app-v-46-sp1-.md
+++ /dev/null
@@ -1,42 +0,0 @@
----
-title: Defrag Running Dialog Box (App-V 4.6 SP1)
-description: Defrag Running Dialog Box (App-V 4.6 SP1)
-author: dansimp
-ms.assetid: 0ceb0897-377e-4754-a7ab-3bc2b5af1452
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Defrag Running Dialog Box (App-V 4.6 SP1)
-
-
-The Disk Defragmenter service is running. The Disk Defragmenter service uses system resources and can cause degradation in performance or increase the time it takes to create virtual application package.
-
-Use the following procedure to stop the Disk Defragmenter service from running during sequencing.
-
-1. On the computer running the App-V Sequencer, click **Start**, right-click **Computer**, and then click **Manage**.
-
-2. In the **Computer Management** console, double-click **Services and Applications**, and then double-click **Services** to expand **Services**,.
-
-3. Locate it in the list. Right-click **Disk Defragmenter**, click **More Actions**, click **Stop** to stop Disk Defragmenter, and then click **OK**.
-
-## Related topics
-
-
-[Dialog Boxes (AppV 4.6 SP1)](dialog-boxes--appv-46-sp1-.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/delete-app.md b/mdop/appv-v4/delete-app.md
deleted file mode 100644
index a5a5189fe4..0000000000
--- a/mdop/appv-v4/delete-app.md
+++ /dev/null
@@ -1,86 +0,0 @@
----
-title: DELETE APP
-description: DELETE APP
-author: dansimp
-ms.assetid: 2f89c0c0-373b-4389-a26d-67b3f9712957
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# DELETE APP
-
-
-Removes an application record from the file system cache to make it no longer visible. Users’ shortcuts and file type associations are hidden but not deleted. No user settings are removed.
-
-`SFTMIME DELETE APP:application [/LOG log-pathname | /CONSOLE | /GUI]`
-
-
-
-
-
-
-
-
-
Parameter
-
Description
-
-
-
-
-
APP:<application>
-
The name and version (optional) of the application to be removed.
-
-
-
/LOG
-
If specified, output is logged to the specified path name.
-
-
-
/CONSOLE
-
If specified, output is presented in the active console window (default).
-
-
-
/GUI
-
If specified, output is presented in a Windows dialog box.
-
-
-
-
-
-
-For version 4.6, the following option has been added.
-
-
-
-
-
-
-
-
-
/LOGU
-
If specified, output is logged to the specified path name in UNICODE format.
If specified, output is logged to the specified path name.
-
-
-
/CONSOLE
-
If specified, output is presented in the active console window (default).
-
-
-
/GUI
-
If specified, output is presented in a Windows dialog box.
-
-
-
-
-
-
-For version 4.6, the following option has been added.
-
-
-
-
-
-
-
-
-
/LOGU
-
If specified, output is logged to the specified path name in UNICODE format.
-
-
-
-
-
-
-**Important**
-The DELETE PACKAGE command always performs a global delete of the package and deletes only global file types and shortcuts.
-
-If the package is global, this command must be run as local Administrator; otherwise, only **DeleteApp** permission is needed.
-
-
-
-## Related topics
-
-
-[SFTMIME Command Reference](sftmime--command-reference.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/delete-server.md b/mdop/appv-v4/delete-server.md
deleted file mode 100644
index 7425b0751b..0000000000
--- a/mdop/appv-v4/delete-server.md
+++ /dev/null
@@ -1,91 +0,0 @@
----
-title: DELETE SERVER
-description: DELETE SERVER
-author: dansimp
-ms.assetid: 4c929639-1c1d-47c3-9225-cc4d7a8736f0
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# DELETE SERVER
-
-
-Removes a publishing server.
-
-**Note**
-This command does not remove any applications or packages published to the client by the server. For each application, use the SFTMIME **CLEAR APP** command followed by the **DELETE PACKAGE** command to completely remove those applications and packages from the client.
-
-
-
-`SFTMIME DELETE SERVER:server-name [/LOG log-pathname | /CONSOLE | /GUI]`
-
-
-
-
-
-
-
-
-
Parameter
-
Description
-
-
-
-
-
SERVER:<server-name>
-
The display name of the publishing server.
-
-
-
/LOG
-
If specified, output is logged to the specified path name.
-
-
-
/CONSOLE
-
If specified, output is presented in the active console window (default).
-
-
-
/GUI
-
If specified, output is presented in a Windows dialog box.
-
-
-
-
-
-
-For version 4.6, the following option has been added.
-
-
-
-
-
-
-
-
-
/LOGU
-
If specified, output is logged to the specified path name in UNICODE format.
If specified, indicates that the global association for the file name extension should be removed.
-
-
-
/LOG
-
If specified, output is logged to the specified path name.
-
-
-
/CONSOLE
-
If specified, output is presented in the active console window (default).
-
-
-
/GUI
-
If specified, output is presented in a Windows dialog box.
-
-
-
-
-
-
-For version 4.6, the following option has been added.
-
-
-
-
-
-
-
-
-
/LOGU
-
If specified, output is logged to the specified path name in UNICODE format.
-
-
-
-
-
-
-## Related topics
-
-
-[SFTMIME Command Reference](sftmime--command-reference.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/deployment-tab.md b/mdop/appv-v4/deployment-tab.md
deleted file mode 100644
index 0b872aa0ce..0000000000
--- a/mdop/appv-v4/deployment-tab.md
+++ /dev/null
@@ -1,43 +0,0 @@
----
-title: Deployment Tab
-description: Deployment Tab
-author: dansimp
-ms.assetid: 4510188b-eade-445d-a90f-b9127dd479a7
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Deployment Tab
-
-
-The **Deployment** tab in the Application Virtualization Sequencer Console enables you to specify parameters for the deployment of a sequenced application package.
-
-## In This Section
-
-
-[About the Deployment Tab](about-the-deployment-tab.md)
-Provides general information about the **Deployment** tab.
-
-[How to Change Deployment Properties](how-to-change-deployment-properties.md)
-Provides procedures for changing package properties by using the **Deployment** tab.
-
-## Related topics
-
-
-[Sequencer Console](sequencer-console.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/determine-your-publishing-method.md b/mdop/appv-v4/determine-your-publishing-method.md
deleted file mode 100644
index 683549aa16..0000000000
--- a/mdop/appv-v4/determine-your-publishing-method.md
+++ /dev/null
@@ -1,102 +0,0 @@
----
-title: Determine Your Publishing Method
-description: Determine Your Publishing Method
-author: dansimp
-ms.assetid: 1f2d0d39-5d65-457a-b826-4f45b00c8c85
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Determine Your Publishing Method
-
-
-After you sequence an application by using the Application Virtualization Sequencer, you need to *publish* that application to your users. Publishing the application consists of delivering the icons, package definition information, and content source location to each computer where the Application Virtualization Client has been installed. The following table describes publishing methods that are supported when you deploy Application Virtualization by using an electronic software distribution (ESD) system.
-
-
-
-
-
-
-
-
-
-
Method
-
Advantages
-
Disadvantages
-
-
-
-
-
Generate a Windows Installer file during sequencing, as a stand-alone solution.
-
-
Very simple to use.
-
Package loaded into cache locally on each computer.
-
Icons displayed to user.
-
Similar to traditional software deployment.
-
No need for streaming servers.
-
-
-
No flexibility in location of package contents on computers—same location on all computers.
-
Must use only Add/Remove Programs or msiexec to remove applications.
-
Removal and replacement with new version required for package updating.
-
-
-
-
Generate a Windows Installer file during sequencing, used with MODE, LOAD, and OVERRIDEURL command-line properties and the package manifest.
-
-
Simple to use but with added flexibility.
-
Icons displayed to user.
-
SFT file containing the applications can be placed on a streaming source location, with clients configured to use that location.
-
-
-
Limited flexibility—only the location of the package content can be controlled at run time.
-
Must use only Add/Remove Programs or msiexec to remove the application.
-
Removal and replacement with new version required for package updating, unless using streaming server.
-
-
-
-
Run SFTMIME commands.
-
-
Complete flexibility—full control of all package management functions.
-
-
-
Commands must be scripted for use with the ESD system.
-
Commands must be run on each computer in correct sequence.
-
Detailed understanding of command language and careful planning required.
-
-
-
-
-
-
-
-For more information about using these publishing methods, see [How to Publish a Virtual Application on the Client](how-to-publish-a-virtual-application-on-the-client.md).
-
-## Related topics
-
-
-[Determine Your Streaming Method](determine-your-streaming-method.md)
-
-[Electronic Software Distribution-Based Scenario](electronic-software-distribution-based-scenario.md)
-
-[Electronic Software Distribution-Based Scenario Overview](electronic-software-distribution-based-scenario-overview.md)
-
-[How to Publish a Virtual Application on the Client](how-to-publish-a-virtual-application-on-the-client.md)
-
-[SFTMIME Command Reference](sftmime--command-reference.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/determine-your-streaming-method.md b/mdop/appv-v4/determine-your-streaming-method.md
deleted file mode 100644
index 0033aa3003..0000000000
--- a/mdop/appv-v4/determine-your-streaming-method.md
+++ /dev/null
@@ -1,116 +0,0 @@
----
-title: Determine Your Streaming Method
-description: Determine Your Streaming Method
-author: dansimp
-ms.assetid: 50d5e0ec-7f48-4cea-8711-5882bd89153b
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Determine Your Streaming Method
-
-
-The first time that a user double-clicks the icon that has been placed on a computer through the publishing process, the Application Virtualization client will obtain the virtual application package content from a streaming source location.
-
-**Note**
-*Streaming* is the term used to describe the process of obtaining content from a sequenced application package, starting with the primary feature block and then obtaining additional blocks as needed.
-
-
-
-The streaming source location is usually a server that is accessible by the user’s computer; however, some electronic distribution systems, such as Microsoft Endpoint Configuration Manager, can distribute the SFT file to the user’s computer and then stream the virtual application package locally from that computer’s cache.
-
-**Note**
-A streaming source location for virtual packages can be set up on a computer that is not a server. This is especially useful in a small branch office that has no server.
-
-
-
-The streaming sources that can be used to store sequenced applications are described in the following table.
-
-
-
-
-
-
-
-
-
-
-
-
Server Type
-
Protocol
-
Advantages
-
Disadvantages
-
Links
-
-
-
-
-
File server
-
File
-
-
Simple low-cost solution to configure existing file server with \CONTENT share
-
-
-
-## Related topics
-
-
-[Electronic Software Distribution-Based Scenario](electronic-software-distribution-based-scenario.md)
-
-[Electronic Software Distribution-Based Scenario Overview](electronic-software-distribution-based-scenario-overview.md)
-
-[Determine Your Publishing Method](determine-your-publishing-method.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/dialog-boxes--appv-46-sp1-.md b/mdop/appv-v4/dialog-boxes--appv-46-sp1-.md
deleted file mode 100644
index a61b7c716f..0000000000
--- a/mdop/appv-v4/dialog-boxes--appv-46-sp1-.md
+++ /dev/null
@@ -1,52 +0,0 @@
----
-title: Dialog Boxes (AppV 4.6 SP1)
-description: Dialog Boxes (AppV 4.6 SP1)
-author: dansimp
-ms.assetid: f76b95df-cba4-4a69-8cd8-a888edf437be
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Dialog Boxes (AppV 4.6 SP1)
-
-
-Use any of the following links for more information about the App-V Sequencer dialog boxes.
-
-## In This Section
-
-
-[Incompatible Installer Dialog Box (App-V 4.6 SP1)](incompatible-installer-dialog-box--app-v-46-sp1-.md)
-
-[Failed Launch Dialog Box (App-V 4.6 SP1)](failed-launch-dialog-box--app-v-46-sp1-.md)
-
-[Oversized Package Dialog Box (App-V 4.6 SP1)](oversized-package-dialog-box--app-v-46-sp1-.md)
-
-[Restart Task Failure Dialog Box (App-V 4.6 SP1)](restart-task-failure-dialog-box--app-v-46-sp1-.md)
-
-[Side-by-side Privatization Failed Dialog Box (App-V 4.6 SP1)](side-by-side-privatization-failed-dialog-box--app-v-46-sp1-.md)
-
-[SXS Conflict Detected Dialog Box (App-V 4.6 SP1)](sxs-conflict-detected-dialog-box--app-v-46-sp1-.md)
-
-[Files Excluded Page Dialog Box (App-V 4.6 SP1)](files-excluded-page-dialog-box--app-v-46-sp1-.md)
-
-[Defender Running Dialog Box (App-V 4.6 SP1)](defender-running-dialog-box--app-v-46-sp1-.md)
-
-[Defrag Running Dialog Box (App-V 4.6 SP1)](defrag-running-dialog-box--app-v-46-sp1-.md)
-
-[Antivirus Running Dialog Box (App-V 4.6 SP1)](antivirus-running-dialog-box--app-v-46-sp1-.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/disconnected-operation-mode.md b/mdop/appv-v4/disconnected-operation-mode.md
deleted file mode 100644
index b123b249f9..0000000000
--- a/mdop/appv-v4/disconnected-operation-mode.md
+++ /dev/null
@@ -1,38 +0,0 @@
----
-title: Disconnected Operation Mode
-description: Disconnected Operation Mode
-author: dansimp
-ms.assetid: 3f9849ea-ba53-4c68-85d3-87a4218f59c6
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Disconnected Operation Mode
-
-
-The disconnected operation mode settings—accessible by right-clicking the **Application Virtualization** node, selecting **Properties**, and clicking the **Connectivity** tab—enables the Application Virtualization Desktop Client or Client for Remote Desktop Services (formerly Terminal Services) to run applications that are stored in the file system cache of the client when the client is unable to connect to the Application Virtualization Management Server.
-
-Reasons for failure to connect to the server include server failure, network outage, or disconnection from the network. If any failure occurs, the client will automatically switch to disconnected operation. After it is disconnected, if the client needs additional data from the server to continue to run an application or if the disconnected operation time-out expires, the client will attempt to reconnect to the server. If this connection attempt fails, the application will be shut down.
-
-By default, disconnected operation is enabled and the time-out is set to 90 days. The time-out value is specified as the number of days you want to limit disconnected operation mode, and you can enter a value from 1–999.
-
-## Related topics
-
-
-[How to Disable or Modify Disconnected Operation Mode Settings](how-to-disable-or-modify-disconnected-operation-mode-settings.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/domain-joined-and-non-domain-joined-clients.md b/mdop/appv-v4/domain-joined-and-non-domain-joined-clients.md
deleted file mode 100644
index 7abf4bd3a7..0000000000
--- a/mdop/appv-v4/domain-joined-and-non-domain-joined-clients.md
+++ /dev/null
@@ -1,50 +0,0 @@
----
-title: Domain-Joined and Non-Domain-Joined Clients
-description: Domain-Joined and Non-Domain-Joined Clients
-author: dansimp
-ms.assetid: a935dc98-de60-45f3-ab74-2444ce082e88
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Domain-Joined and Non-Domain-Joined Clients
-
-
-The App-V Desktop Client can be configured to allow connection to a network regardless of whether the client is domain joined or non-domain joined.
-
-## Domain-Joined Clients
-
-
-Clients that are domain joined, but outside the internal network, can communicate with the App-V infrastructure by using a VPN connection. When you want to provide users the ability to leave the internal network but still communicate in an App-V infrastructure, your environment requires very little setup. Because the users are already part of the domain, you simply need to ensure that Cached Credentials are supported on the client. This is the default configuration, and any changes to this setting can be accomplished from Group Policies.
-
-As mentioned in the App-V Security Best Practices Guide, the user will attempt to send their user ticket to the App-V infrastructure for authentication. If the ticket is expired, it will revert to using NTLM and the cached credentials on the computer. To allow roaming, administrators must ensure that the publishing server being accessed internally is available at the same name externally for the names to resolve properly.
-
-## Non-Domain-Joined Clients
-
-
-Clients that are non-domain joined but need to communicate in the App-V infrastructure must be configured to ensure that authentication to the App-V infrastructure is successful. The App-V Desktop Client does not permit prompting for the publishing refresh process, so the client must be configured to present the proper credentials to the App-V Management Server.
-
-The publishing server, which is configured for publishing refresh from the non-domain joined client, requires that the external name that clients access is configured as the common name or a subject alternate name (SAN) on the publishing server’s certificate.
-
-## Related topics
-
-
-[How to Assign the Proper Credentials for Windows Vista](how-to-assign--the-proper-credentials-for-windows-vista.md)
-
-[How to Assign the Proper Credentials for Windows XP](how-to-assign--the-proper-credentials-for-windows-xp.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/edit-shortcuts-learn-more.md b/mdop/appv-v4/edit-shortcuts-learn-more.md
deleted file mode 100644
index 830abacbd3..0000000000
--- a/mdop/appv-v4/edit-shortcuts-learn-more.md
+++ /dev/null
@@ -1,45 +0,0 @@
----
-title: Edit Shortcuts
-description: Edit Shortcuts
-author: dansimp
-ms.assetid: a0ca75aa-1059-4d0c-894c-2e3474e9f519
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Edit Shortcuts
-
-
-Use the **Edit Shortcuts** page to configure the shortcuts and file type associations (FTA) that are installed when you deploy the virtual application package to target computers.
-
-This page contains the following elements:
-
-**Add**
-Adds an icon or specifies an FTA for the package. Click **Browse** to specify the file or program to add.
-
-**Remove**
-Removes an icon or FTA from the package.
-
-**Edit**
-Enables you to configure the properties associated with an icon or FTA in the package. You can update the associated **Application Path**, **Name**, **Version**, and **OSD File Name**.
-
-## Related topics
-
-
-[Create New Package Wizard (AppV 4.6 SP1)](create-new-package-wizard---appv-46-sp1-.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/electronic-software-distribution-based-scenario-overview.md b/mdop/appv-v4/electronic-software-distribution-based-scenario-overview.md
deleted file mode 100644
index ebdfacc6c9..0000000000
--- a/mdop/appv-v4/electronic-software-distribution-based-scenario-overview.md
+++ /dev/null
@@ -1,85 +0,0 @@
----
-title: Electronic Software Distribution-Based Scenario Overview
-description: Electronic Software Distribution-Based Scenario Overview
-author: dansimp
-ms.assetid: e9e94b8a-6cba-4de8-9b57-73897796b6a0
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 08/30/2016
----
-
-
-# Electronic Software Distribution-Based Scenario Overview
-
-
-If you plan to use an electronic software distribution (ESD) solution to deploy virtual applications, it is important to understand the factors that go into and are affected by that decision. This topic describes the benefits of using an ESD-based scenario and provides information about the publishing and package streaming methods that you will need to consider as you proceed with your deployment.
-
-**Important**
-Whichever ESD solution you use, you must be familiar with the requirements of your particular solution. If you are using Microsoft Endpoint Configuration Manager, see the Configuration Manager documentation at .
-
-
-
-Using an existing ESD system provides you with the following benefits:
-
-- Eliminates dual management infrastructures
-
-- Reduces the cost of additional hardware
-
-- Reduces the cost of additional operating system and database licenses
-
-## Publishing Methods
-
-
-When using an ESD-based scenario, you have the following choices for publishing the application to the clients:
-
-- **Stand-alone Windows Installer.** The Windows Installer file contains the manifest and the OSD and ICO files the clients use to configure a package. The Windows Installer file also copies the SFT file to the client because this scenario does not use a server.
-
-- **Windows Installer with the package manifest.** The Windows Installer file contains the manifest and the OSD and ICO files the clients use to configure a package. The SFT file is stored on a server. A command-line parameter directs the client to the location of the SFT file.
-
-- **SFTMIME commands.** SFTMIME commands are used with the manifest, OSD, ICO, and SFT files to add packages to the client. The manifest file must be on the client computer, or it must be accessible through a UNC path. Depending on the client configuration and the command-line options, the OSD, ICO, and SFT files can be on the client computer or on a server.
-
-For more detailed information about the preceding publishing methods, see [Determine Your Publishing Method](determine-your-publishing-method.md).
-
-## Package Streaming Methods
-
-
-You will need to determine the method your Application Virtualization System will use to stream the virtual application packages, or SFT files, from the server to the clients. The following streaming options are available:
-
-- **Application Virtualization Streaming Server.** If you use an Application Virtualization Streaming Server in your configuration, the SFT files are streamed to the clients from that server using RTSP or RTSPS protocols. You must install the server software on a computer and you must configure it through the registry, but this configuration does not depend on services such as SQL or Active Directory Domain Services. The SFT files are stored on the server at a location accessible by the clients. Publishing information can be distributed to the clients through any distribution mechanism. However, when configured, the client receives package upgrades automatically and active upgrade is supported.
-
-- **Application Virtualization Management Server.** If you use an Application Virtualization Management Server in your configuration, the SFT files are streamed to the clients from that server using RTSP or RTSPS protocols. You manage this server through the Application Virtualization Management Console. This configuration uses a SQL database and Active Directory services. The server can distribute publishing information to the clients, so additional publishing mechanisms are not needed.
-
-- **File server.** If you use a file server in your configuration, the SFT files are streamed to the other client computers by using SMB protocols. File servers used in this configuration are managed by creating access control lists (ACLs) on the file shares and SFT files. Care must be taken to direct the clients to the correct files on the file server.
-
-- **IIS server.** If you use an IIS server in your configuration, the SFT files are streamed to the clients from that server using HTTP or HTTPS protocols. The IIS server is easy to configure and manage. Care must be taken to direct the clients to the correct files on the IIS server.
-
-For more detailed information about the preceding streaming methods, see [Determine Your Streaming Method](determine-your-streaming-method.md).
-
-## Related topics
-
-
-[Application Virtualization Client Installer Command-Line Parameters](application-virtualization-client-installer-command-line-parameters.md)
-
-[Application Virtualization Server-Based Scenario](application-virtualization-server-based-scenario.md)
-
-[Determine Your Publishing Method](determine-your-publishing-method.md)
-
-[Determine Your Streaming Method](determine-your-streaming-method.md)
-
-[Electronic Software Distribution-Based Scenario](electronic-software-distribution-based-scenario.md)
-
-[SFTMIME Command Reference](sftmime--command-reference.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/electronic-software-distribution-based-scenario.md b/mdop/appv-v4/electronic-software-distribution-based-scenario.md
deleted file mode 100644
index d99c4ce90f..0000000000
--- a/mdop/appv-v4/electronic-software-distribution-based-scenario.md
+++ /dev/null
@@ -1,64 +0,0 @@
----
-title: Electronic Software Distribution-Based Scenario
-description: Electronic Software Distribution-Based Scenario
-author: dansimp
-ms.assetid: 18be0f8d-60ee-449b-aa83-93c86d1a908e
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Electronic Software Distribution-Based Scenario
-
-
-If you plan to use an electronic software distribution (ESD) deployment scenario for your Microsoft Application Virtualization environment, it is important to understand the factors that go into and are affected by that decision. The topics in this section describe the ESD scenario and provide information about package delivery methods, transmission protocols, and external components that you will need to consider in your deployment strategy. You can also use the procedures in this section to complete your deployment, from the server configuration phase through the deployment verification phase.
-
-## In This Section
-
-
-[Electronic Software Distribution-Based Scenario Overview](electronic-software-distribution-based-scenario-overview.md)
-Provides important information about the publishing and streaming methods you can use for an ESD-based deployment.
-
-[How to Configure Servers for ESD-Based Deployment](how-to-configure-servers-for-esd-based-deployment.md)
-This section provides procedures you can use to configure the Application Virtualization Streaming Servers, the IIS server, and the file server for your electronic software distribution–based deployment strategy.
-
-[How to Install the Client by Using the Command Line](how-to-install-the-client-by-using-the-command-line-new.md)
-Provides command-line procedures for installing the Application Virtualization Client, using either the setup.exe or the setup.msi file.
-
-[How to Uninstall the App-V Client](how-to-uninstall-the-app-v-client.md)
-Provides a step-by-step procedure you can use to confirm that the Application Virtualization Client has been installed and is functioning correctly.
-
-[How to Publish a Virtual Application on the Client](how-to-publish-a-virtual-application-on-the-client.md)
-Provides command-line procedures for publishing an application package, using either Windows Installer or SFTMIME.
-
-## Reference
-
-
-[Application Virtualization Client Installer Command-Line Parameters](application-virtualization-client-installer-command-line-parameters.md)
-
-## Related Sections
-
-
-[Application Virtualization Server-Based Scenario](application-virtualization-server-based-scenario.md)
-
-## Related topics
-
-
-[Application Virtualization Deployment and Upgrade Considerations](application-virtualization-deployment-and-upgrade-considerations.md)
-
-[Stand-Alone Delivery Scenario for Application Virtualization Clients](stand-alone-delivery-scenario-for-application-virtualization-clients.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/exclusion-item-dialog-box.md b/mdop/appv-v4/exclusion-item-dialog-box.md
deleted file mode 100644
index 250a430862..0000000000
--- a/mdop/appv-v4/exclusion-item-dialog-box.md
+++ /dev/null
@@ -1,51 +0,0 @@
----
-title: Exclusion Item Dialog Box
-description: Exclusion Item Dialog Box
-author: dansimp
-ms.assetid: 5523c6d4-95f2-47af-8c06-3ab18004a207
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Exclusion Item Dialog Box
-
-
-Use the **Exclusion Item** dialog box to assign or change a mapping rule and to assign or change an expression for exclusion. This dialog box contains the following elements.
-
-**Important**
-Adding files from an excluded directory to the virtual files system is not supported.
-
-
-
-**Exclude Path**
-Use to specify variable name that the Application Virtualization Sequencer will exclude if encountered while parsing virtual file system items or virtual registry items.
-
-**Mapping Type**
-Use to select the mapping rules the Application Virtualization Sequencer will apply to parse items in the virtual file system or virtual registry. One of the following values can occur:
-
-- VRG—Specifies that this mapping rule applies when parsing an item in the virtual registry.
-
-- VFS—Specifies that this mapping rule applies when parsing an item in the virtual file system.
-
-- VRG & VFS—Specifies that this mapping rule applies when parsing an item in either the virtual file system or the virtual registry.
-
-## Related topics
-
-
-[Sequencer Dialog Boxes](sequencer-dialog-boxes.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/exclusion-items-tab-keep.md b/mdop/appv-v4/exclusion-items-tab-keep.md
deleted file mode 100644
index e4dcff97c2..0000000000
--- a/mdop/appv-v4/exclusion-items-tab-keep.md
+++ /dev/null
@@ -1,68 +0,0 @@
----
-title: Exclusion Items Tab
-description: Exclusion Items Tab
-author: dansimp
-ms.assetid: 864e46dd-3d6e-4a1b-acf4-9dc00548117e
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Exclusion Items Tab
-
-
-The **Exclusion Items** tab displays the expressions that the Application Virtualization Sequencer excludes from the virtual file system or virtual registry. These expressions are excluded to ensure that the sequenced application package can run on Application Virtualization Desktop Clients. You can also exclude non-standard installation directories that might be unwanted in the sequencing.
-
-This tab contains the following elements.
-
-**Exclude Path**
-Displays variable names that the Sequencer excludes if encountered while parsing virtual file system items or virtual registry items.
-
-**Resolves To**
-Displays the actual paths that correspond to the Sequencer variables.
-
-**Map Type**
-Displays mapping rules that the Sequencer applies to parse items in the virtual file system or virtual registry. One of the following values can occur:
-
-**New**
-Click to enter a new exclusion item.
-
-**Edit**
-Click to edit a selected exclusion.
-
-**Delete**
-Click to remove a selected exclusion.
-
-**Save As Default**
-Click to save the current exclusion items as your default.
-
-**Restore Defaults**
-Click to restore default-assigned exclusion items and remove any items you added.
-
-**OK**
-Click to accept the displayed exceptions.
-
-**Cancel**
-Click to cancel any changes you have made.
-
-## Related topics
-
-
-[Application Virtualization Sequencer Options Dialog Box](application-virtualization-sequencer-options-dialog-box.md)
-
-[Exclusion Item Dialog Box](exclusion-item-dialog-box.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/failed-launch-dialog-box--app-v-46-sp1-.md b/mdop/appv-v4/failed-launch-dialog-box--app-v-46-sp1-.md
deleted file mode 100644
index a08aea1e5d..0000000000
--- a/mdop/appv-v4/failed-launch-dialog-box--app-v-46-sp1-.md
+++ /dev/null
@@ -1,42 +0,0 @@
----
-title: Failed Launch Dialog Box (App-V 4.6 SP1)
-description: Failed Launch Dialog Box (App-V 4.6 SP1)
-author: dansimp
-ms.assetid: 55669552-51b4-48aa-8bd0-6d78c2c930d9
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Failed Launch Dialog Box (App-V 4.6 SP1)
-
-
-The application did not start successfully.
-
-Use the following list to help identify why the application did not run successfully.
-
-1. Verify that all required prerequisites have been installed on the computer running the App-V Sequencer.
-
-2. Verify that any resources required by the application are available and not in use by another process.
-
-3. Verify that the application you are installing is supported by the operating system running on the computer that is running the App-V Sequencer.
-
-## Related topics
-
-
-[Dialog Boxes (AppV 4.6 SP1)](dialog-boxes--appv-46-sp1-.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/file-type-association-results-pane-columns.md b/mdop/appv-v4/file-type-association-results-pane-columns.md
deleted file mode 100644
index 1cdc78f1cc..0000000000
--- a/mdop/appv-v4/file-type-association-results-pane-columns.md
+++ /dev/null
@@ -1,96 +0,0 @@
----
-title: File Type Association Results Pane Columns
-description: File Type Association Results Pane Columns
-author: dansimp
-ms.assetid: eab48e20-9c92-459d-a06b-8e20202d73f6
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# File Type Association Results Pane Columns
-
-
-In the Application Virtualization Client Management Console, the **Results** pane of the **File Associations** node can display a variety of columns. **Extension**, **Description**, and **Application** are shown by default.
-
-**Note**
-You can add or remove a column simply by right-clicking in the **Results** pane, selecting **View**, then selecting **Add/Remove Columns**.
-
-
-
-The list can be sorted by any of the columns. Columns that contain dates and times are sorted in chronological order, not alphabetical. For columns that contain a mix of dates and times and text, dates and times are considered to come before any other text.
-
-The available column names contain the following elements.
-
-**Extension**
-The extension, such as DOC or HTML. This is the field by which the list is organized, so each extension is displayed once on the list.
-
-**Description**
-The description or user-friendly name.
-
-**Application**
-The name and version of the application associated with the default action of this file type.
-
-**Parameters**
-The parameters for the default action.
-
-**Default Action**
-The name of the default action.
-
-**DDE**
-Displays **Enabled** or **Disabled** depending on whether Dynamic Data Exchange (DDE) is enabled for the default action.
-
-**Linked Extensions**
-A comma-separated list of other extensions that are associated with the same type.
-
-**Confirm Open**
-Displays **Yes** or **No** depending on whether **Confirm open after download** is selected.
-
-**Always Show**
-Displays **Yes** or **No** depending on whether **Always show extension** is selected.
-
-**Shell New**
-Displays **Yes** or **No** depending on whether the extension is added to the shell’s **New** menu.
-
-**Applies To**
-Displays **User** or **Computer** depending on whether this is a user-specific or computer-wide association.
-
-**Icon File**
-The original name of the icon file.
-
-**Icon Path**
-The original path or URL for the icon file.
-
-**Cached Icon File**
-The name of the icon files in cache (which is a GUID in the current implementation).
-
-**Cached Icon Path**
-The full path to the icon files in cache.
-
-**Content Type**
-The content type.
-
-**Perceived Type**
-The perceived type or blank.
-
-## Related topics
-
-
-[File Type Associations Node](file-type-associations-node-client.md)
-
-[File Type Association Results Pane](file-type-association-results-pane.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/file-type-association-results-pane.md b/mdop/appv-v4/file-type-association-results-pane.md
deleted file mode 100644
index 3b6a32eb71..0000000000
--- a/mdop/appv-v4/file-type-association-results-pane.md
+++ /dev/null
@@ -1,117 +0,0 @@
----
-title: File Type Association Results Pane
-description: File Type Association Results Pane
-author: dansimp
-ms.assetid: bc5ceb48-1b9f-45d9-a770-1bac90629c76
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# File Type Association Results Pane
-
-
-The **File Association** **Results** pane is one level below the **System** pane in the Application Virtualization Client Management Console, and it displays a list of the available file type associations. Users can see a list of file type extensions and the applications to which they correspond.
-
-To display specific options for file types, right-click any application extension to display a pop-up menu that contains the following elements.
-
-**Delete**
-Deletes the file name extension from the list and removes the association to the file type.
-
-**Properties**
-Displays the **Properties** dialog box for the selected application extension. This dialog box has two tabs:
-
-- The **General** tab displays general information about the file type association, including the application icon and name:
-
- - **Icon**—Displays the selected icon for the associated file type.
-
- - **Association Name**—Displays the name of the file type.
-
- - **Change Icon**—Click this button to change the icon for the file type association.
-
- - **Extension**—Displays the extension or extensions associated with a particular file type.
-
- - **Unlink**—This button is enabled when more than one extension is associated with an application. Click **Unlink** to manage the file type extension separately from the extension it is currently linked with.
-
- - **Specified application**—Select this radio button, and choose an application from the drop-down list of available applications. You are changing the application that is used by the default action. You can also browse to find an application if it isn't available on the drop-down list.
-
- - **OSD file**—Select this radio button, and specify a path to an Open Software Descriptor (OSD) file. You can also browse to an OSD file.
-
-- The **Advanced** tab displays detailed information about the file type association:
-
- - **Action**—Displays a list of the available actions for the associated file type.
-
- - **Content Type**—Displays a description of the contents of the file type. If this field is left blank, the client will fill it.
-
- - **Perceived Type**—Displays the file type. You can select one of the options from the drop-down list or add your own.
-
- - **Confirm open after download**—Select this check box to display a confirmation message after a file is loaded. If this box is selected, when you attempt to open a file of this type by downloading it into a Web browser, the browser prompts you to see whether you want to save the file rather than open it directly into the browser without confirmation.
-
- - **Always show extension**—Select this check box to specify that extensions should be shown even when the user requests that the system should hide extensions for known file types.
-
- - **Add to new menu**—Select this check box to specify that the extension or extensions should be listed in the shell's **New** context menu.
-
- - **Apply to all users**—Select this check box to specify that extensions should be available to all users.
-
-**Help**
-Displays the Client Management Console help system.
-
-To display general options for the **Results** pane, right-click anywhere in the **Results** pane to display a pop-up menu that contains the following elements.
-
-**New Association**
-This menu item displays the New Association Wizard. This wizard consists of two pages:
-
-1. Enter a new or existing file name extension, and associate the extension with a file type:
-
- - **Extension**—Enter a new file name extension. This field is blank by default.
-
- - **Create a new file type with this description**—Select this radio button to enter a new file type description in the active field. This button is selected by default, and the active field is blank.
-
- - **Apply this file type to all users**—Select this check box when you want this association to be global for all users. By default, this box is not selected.
-
- - **Link this extension with an existing file type**—Select this radio button to associate the extension with an existing file type. Pick a file type from the drop-down list. When you choose this option, **Next** is changed to **Finish**.
-
-2. Select the application that will open files with the specified extension:
-
- - **Open files with the selected application**—Select this radio button to open the file with an existing application. Choose an application from the drop-down list of available applications.
-
- - **Open file with the association described in this OSD file**—Select this radio button to specify an OSD file that determines the application used to open the file. Use the browse button to select an existing location, or enter a path or HTTP-formatted URL in this field.
-
-**Refresh**
-This item refreshes the **Results** pane.
-
-**Export List**
-With this menu item, you can create a tab-delimited text file that contains the contents of the **Results** pane. This item displays a standard **File Save** dialog box where you specify the location for the text file you are creating.
-
-**View**
-This pop-up list of menu item lets you change the appearance and content of the **Results** pane.
-
-**Arrange/Line Up Icons**
-These menu items can be used to change how the icons are displayed in the **Results** pane.
-
-**Help**
-This item displays the help system for the management console.
-
-## Related topics
-
-
-[How to Change an Application Icon](how-to-change-an-application-icon.md)
-
-[File Type Associations Node](file-type-associations-node-client.md)
-
-[File Type Association Results Pane Columns](file-type-association-results-pane-columns.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/file-type-associations-node-client.md b/mdop/appv-v4/file-type-associations-node-client.md
deleted file mode 100644
index 4182a0dbbf..0000000000
--- a/mdop/appv-v4/file-type-associations-node-client.md
+++ /dev/null
@@ -1,72 +0,0 @@
----
-title: File Type Associations Node
-description: File Type Associations Node
-author: dansimp
-ms.assetid: 48e4d9eb-00bd-4231-a68a-f8597ab683ff
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# File Type Associations Node
-
-
-The **File Type Associations** node is one level below the **Application Virtualization** node in the **Scope** pane of the Application Virtualization Client Management Console. When you select this node, the **Results** pane displays a list of file type associations.
-
-Right-click the **File Type Associations** node to display a pop-up menu that contains the following elements.
-
-**New Association**
-This menu item displays the New Association Wizard. This wizard consists of two pages:
-
-1. Enter a new or existing file name extension, and associate the extension with a file type:
-
- - **Extension**—Enter a new or existing file name extension. This field is blank by default.
-
- - **Create a new file type with this description**—Select this radio button to enter a new file type description in the active field. This button is selected by default, and the active field is blank.
-
- - **Apply this file type to all users**—Select this check box when you want this association to be global for all users. By default, this box is not selected.
-
- - **Link this extension with an existing file type**—Select this radio button to associate the extension with an existing file type. Choose a file type from the drop-down list. When you choose this option, **Next** is changed to **Finish**.
-
-2. Select the application that will open files with the specified extension:
-
- - **Open files with the selected application**—Select this radio button to open the file with an existing application. Choose an application from the drop-down list of available applications.
-
- - **Open files with the application described in this OSD file**—Select this radio button to specify an Open Software Descriptor (OSD) file that determines the application used to open the file. Browse to select an existing location, or enter a path or HTTP-formatted URL in this field.
-
-**New Window from Here**
-Select this menu item to open a new management console with the selected node as the root node.
-
-**Export List**
-You can use this menu item to create a tab-delimited text file that contains the contents of the **Results** pane. This item displays a standard **File Save** dialog box where you specify the location for the text file you are creating.
-
-**View**
-This pop-up list of menu items enables you to change the appearance and content of the **Results** pane.
-
-**Refresh**
-Select this item to refresh the management console.
-
-**Help**
-With this menu item, you can display the help system for the management console.
-
-## Related topics
-
-
-[File Type Association Results Pane](file-type-association-results-pane.md)
-
-[File Type Association Results Pane Columns](file-type-association-results-pane-columns.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/file-type-associations-node.md b/mdop/appv-v4/file-type-associations-node.md
deleted file mode 100644
index f739cf0208..0000000000
--- a/mdop/appv-v4/file-type-associations-node.md
+++ /dev/null
@@ -1,66 +0,0 @@
----
-title: File Type Associations Node
-description: File Type Associations Node
-author: dansimp
-ms.assetid: a3f35562-32d0-4a43-8604-3a54189ade92
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# File Type Associations Node
-
-
-The **File Type Associations** node is one level below the Application Virtualization System node in the **Scope** pane in the Application Virtualization Server Management Console. When you select this node, the **Results** pane displays a list of file type associations. Right-click the **File Type Association** node to display a pop-up menu that contains the following elements.
-
-**New File Type Association**
-Displays the New File Type Association Wizard. This wizard consists of the following two pages:
-
-1. Enter a new or existing file name extension, and associate the extension with a file type.
-
- 1. **Extension**—Enables you to enter a new or existing file name extension. This field is blank by default.
-
- 2. **Create a new file type with this description**—Select this radio button to enter a new file type description in the active field. This button is selected by default, and the active field is blank.
-
- 3. **Link this extension with an existing file type**—Select this radio button to associate the extension with an existing file type. Pick a file type from the drop-down list.
-
-2. Select the application that will open files with the specified extension.
-
- 1. **Open files with the selected application**—Enables you to choose an application from the drop-down list of available applications.
-
- 2. **Icon Path**—Enables you to enter the complete path to the ICO file or to browse for the ICO file.
-
-**View**
-Changes the appearance and content of the **Results** pane.
-
-**New Window from Here**
-Opens a new management console with the selected node as the root node.
-
-**Refresh**
-Refreshes the view of the server.
-
-**Export List**
-Creates a tab-delimited text file that contains the contents of the **Results** pane. This item displays a standard **File Save** dialog box where you specify the location for the text file you are creating.
-
-**Help**
-Displays the help system.
-
-## Related topics
-
-
-[Server Management Console: File Type Associations Node](server-management-console-file-type-associations-node.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/file-type-associations-results-pane-columns.md b/mdop/appv-v4/file-type-associations-results-pane-columns.md
deleted file mode 100644
index 1458316d50..0000000000
--- a/mdop/appv-v4/file-type-associations-results-pane-columns.md
+++ /dev/null
@@ -1,65 +0,0 @@
----
-title: File Type Associations Results Pane Columns
-description: File Type Associations Results Pane Columns
-author: dansimp
-ms.assetid: 8cbb63e4-f93b-4066-ba06-30103e6d0c3e
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# File Type Associations Results Pane Columns
-
-
-The **Results** pane in the Application Virtualization Server Management Console displays two columns.
-
-You can use the standard Microsoft Windows **Add/Remove Columns** dialog box to select which columns are displayed in the **Results** pane.
-
-To see the **Add/Remove Columns** dialog box, right-click in the **Results** pane and select **View > Add/Remove Columns** from the pop-up menu.
-
-The following table displays the column name and its contents.
-
-
-
-
-
-
-
-
-
Column
-
Description
-
-
-
-
-
Extension
-
Displays the extension, such as DOC or HTML. This is the field by which the list is organized, so each extension is displayed once on the list.
-
-
-
File Type
-
Displays the file type.
-
-
-
-
-
-
-## Related topics
-
-
-[Server Management Console: File Type Associations Node](server-management-console-file-type-associations-node.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/file-type-associations-results-pane.md b/mdop/appv-v4/file-type-associations-results-pane.md
deleted file mode 100644
index b1f2badd96..0000000000
--- a/mdop/appv-v4/file-type-associations-results-pane.md
+++ /dev/null
@@ -1,88 +0,0 @@
----
-title: File Type Associations Results Pane
-description: File Type Associations Results Pane
-author: dansimp
-ms.assetid: 881d7fa7-ecde-4a05-b6ee-132fe2c09900
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# File Type Associations Results Pane
-
-
-The **File Type Associations Results** pane in the Application Virtualization Server Management Console displays a list of the available file type associations. Users can see a list of file type extensions and the applications to which they correspond.
-
-Right-click any application extension to display a pop-up menu that contains the following elements.
-
-**Delete**
-Deletes the file name extension from the list.
-
-**Properties**
-Displays the **Properties** dialog box for the selected application extension. This dialog box has the following tabs:
-
-- **General** tab—Displays general information about the file type association, including the application icon and name.
-
- - **Icon**—Displays the selected icon for the associated file type.
-
- - **Extension**—Displays the extension for the file type.
-
- - **File Type Description**—Displays a brief description of the file type. You can edit this field.
-
- - **Open files with this application**—Enables you to choose an application from the drop-down list of available applications.
-
- - **Icon Path**—Enables you to enter the complete path to the icon file (ICO) or to browse for the ICO file.
-
-- **Advanced** tab—Displays detailed information about the file type.
-
- - **Action**—Displays a list of the available actions for the associated file type. You can add new actions, edit existing actions, set an action as a default, or delete actions.
-
- - **Content Type**—Displays a description of the contents of the file type. If this field is left blank, the client will fill it.
-
- - **Perceived Type**—Displays the kind of file type. You can select one of the options from the drop-down list or add your own.
-
- - **Confirm open after download**—Select this check box to display a confirmation message after an application is loaded.
-
- - **Always show extension**—Select this check box to specify that extensions should be shown even when the user requests that the system hide the extensions for known file types.
-
- - **Add to new menu**—Select this check box to specify that the extension or extensions should be listed in the shell's **New Extensions** list.
-
-**Help**
-Displays the Application Virtualization Server Management Console help system.
-
-Right-click anywhere in the **Results** pane that is not on an extension to display a pop-up menu that contains the following elements.
-
-**Refresh**
-Refreshes the **Results** pane.
-
-**Export List**
-Creates a tab-delimited text file that contains the contents of the **Results** pane. This item displays a standard **File Save** dialog box where you specify the location for the text file you are creating.
-
-**View**
-Changes the appearance and content of the **Results** pane.
-
-**Arrange/Line up Icons**
-Organizes the icons in the **Results** pane.
-
-**Help**
-Displays the help system.
-
-## Related topics
-
-
-[Server Management Console: File Type Associations Node](server-management-console-file-type-associations-node.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/files-excluded-page-dialog-box--app-v-46-sp1-.md b/mdop/appv-v4/files-excluded-page-dialog-box--app-v-46-sp1-.md
deleted file mode 100644
index c994c8d5e0..0000000000
--- a/mdop/appv-v4/files-excluded-page-dialog-box--app-v-46-sp1-.md
+++ /dev/null
@@ -1,50 +0,0 @@
----
-title: Files Excluded Page Dialog Box (App-V 4.6 SP1)
-description: Files Excluded Page Dialog Box (App-V 4.6 SP1)
-author: dansimp
-ms.assetid: 9718c7bf-7ed2-44d8-bdac-df013cd0d6c6
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Files Excluded Page Dialog Box (App-V 4.6 SP1)
-
-
-All required files were not added to the package because they are located in excluded paths. Use the following steps to remove the files from the exclusion list.
-
-1. Open the package in the App-V Sequencer console.
-
-2. Click **Tools** / **Options**, and then click the **Exclusion Items** tab.
-
-3. Select the **Exclude Path** entry, and then click **Delete**.
-
-4. Click **Ok**.
-
-You must then add the file to the package. You can use the following steps to add files:
-
-1. In the App-V Sequencer console, click the **Virtual File System** tab.
-
-2. To add a new virtual file system mapping, right-click, and then click **Add**.
-
-3. In the **New Virtual File System Mapping** dialog box, to specify the file, click **Browse** and select the file. Click **OK**. To save the package, click **File** / **Save**.
-
-## Related topics
-
-
-[Dialog Boxes (AppV 4.6 SP1)](dialog-boxes--appv-46-sp1-.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/files-tab-keep.md b/mdop/appv-v4/files-tab-keep.md
deleted file mode 100644
index aaeebd7805..0000000000
--- a/mdop/appv-v4/files-tab-keep.md
+++ /dev/null
@@ -1,43 +0,0 @@
----
-title: Files Tab
-description: Files Tab
-author: dansimp
-ms.assetid: 14191e51-11a2-40ab-8855-3408a4bc5a9d
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Files Tab
-
-
-Use the **Files** tab to specify whether a file in a sequenced application package will be available to a specific user or to all users in the community.
-
-## In This Section
-
-
-[About the Files Tab](about-the-files-tab.md)
-Provides general information about the **Files** tab.
-
-[How to Modify the Files Included in a Package](how-to-modify-the-files-included-in-a-package.md)
-Provides the procedure to modify the files included in a package.
-
-## Related topics
-
-
-[Sequencer Console](sequencer-console.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/g b/mdop/appv-v4/g
deleted file mode 100644
index e69de29bb2..0000000000
diff --git a/mdop/appv-v4/gathering-information-page--learn-more-.md b/mdop/appv-v4/gathering-information-page--learn-more-.md
deleted file mode 100644
index 2fb6c6cc6f..0000000000
--- a/mdop/appv-v4/gathering-information-page--learn-more-.md
+++ /dev/null
@@ -1,42 +0,0 @@
----
-title: Gathering Information Page (Learn More)
-description: Gathering Information Page (Learn More)
-author: dansimp
-ms.assetid: f8d5ec6b-a3d3-4e80-b1c2-3f8441b04aaa
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Gathering Information Page (Learn More)
-
-
-Use the **Gathering Information** page to review the installation files that could not be located in the directory specified on the **Installation Files** page of this wizard. You must either locate the missing files and then click **Previous** to recreate the Package Accelerator, or select the **Remove these files** check box before you advance to the next page of this wizard.
-
-This page contains the following elements:
-
-**Review Missing Files**
-Displays a list of the installation files that were not found in the specified directory.
-
-**Remove these files**
-Specifies whether the missing installation files should be removed from the package. Only select this option if the files displayed in the **Review Missing Files** pane are not required to successfully run the application. All files that are removed will not be part of the Package Accelerator and also will not be part of any virtual application packages created by using the Package Accelerator. Ensure that removing these files will not cause the package to fail when running on target computers.
-
-## Related topics
-
-
-[Create Package Accelerator Wizard (AppV 4.6 SP1)](create-package-accelerator-wizard--appv-46-sp1-.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/general-tab-keep.md b/mdop/appv-v4/general-tab-keep.md
deleted file mode 100644
index 58ae9340d1..0000000000
--- a/mdop/appv-v4/general-tab-keep.md
+++ /dev/null
@@ -1,61 +0,0 @@
----
-title: General Tab
-description: General Tab
-author: dansimp
-ms.assetid: aeefae39-60cd-4ad4-9575-c07d7e2b1e59
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# General Tab
-
-
-Use the **General** tab to configure options for Microsoft Application Virtualization (App-V) Sequencer.
-
-**Scratch Directory**
-Specifies the path to the location where the Sequencer will temporarily save files generated during sequencing. The default path is C:\\Program Files\\Microsoft Application Virtualization Sequencer\\Scratch. To specify a new path, click **Browse**.
-
-**Log Directory**
-Specifies the path to the directory where the Sequencer will save log files. The default path is C:\\Program Files\\Microsoft Application Virtualization Sequencer\\Logs. To specify a new path, click **Browse**
-
-**Allow Use of MSI Installer**
-Select this option to allow interaction between the Sequencer and the application installer. This option is selected by default.
-
-**Allow Virtualization of Events**
-Select this option to allow low-level operating system activities of the application to be virtualized when a sequenced application package is run on App-V Desktop Clients. This option is selected by default.
-
-**Allow Virtualization of Services**
-Select this option to allow services required by the application to be virtualized when the application is run on App-V Desktop Clients. This option is selected by default.
-
-**Append Package Version to Filename**
-Select this option to automatically append the sequenced application package version number to the file name. This option is selected by default.
-
-**OK**
-Saves changes and closes the dialog box.
-
-**Cancel**
-Exits the dialog box without saving any changes.
-
-**Apply**
-Saves the changes and remains in the dialog box.
-
-## Related topics
-
-
-[Application Virtualization Sequencer Options Dialog Box](application-virtualization-sequencer-options-dialog-box.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/guidance-page-app-v-46-sp1.md b/mdop/appv-v4/guidance-page-app-v-46-sp1.md
deleted file mode 100644
index 6af524a1e1..0000000000
--- a/mdop/appv-v4/guidance-page-app-v-46-sp1.md
+++ /dev/null
@@ -1,39 +0,0 @@
----
-title: Guidance Page
-description: Guidance Page
-author: dansimp
-ms.assetid: 2d461f7e-bde0-4f20-bfc1-46d52feb701e
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Guidance Page
-
-
-Use the **Guidance** page to review the publishing guidance associated with the Package Accelerator. This information was created with the Package Accelerator and includes information about creating and publishing a new virtual application package based on the specified Package Accelerator.
-
-This page contains the following elements:
-
-**Export**
-Click **Export** to export the guidance information to a Rich Text Format (.rtf) or text (.txt) file. Exporting the information is helpful if you have to review the guidance information later in the sequencing process.
-
-## Related topics
-
-
-[Sequencer Wizard - Package Accelerator (AppV 4.6 SP1)](sequencer-wizard---package-accelerator--appv-46-sp1-.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/help.md b/mdop/appv-v4/help.md
deleted file mode 100644
index 1b14a81bf2..0000000000
--- a/mdop/appv-v4/help.md
+++ /dev/null
@@ -1,174 +0,0 @@
----
-title: HELP
-description: HELP
-author: dansimp
-ms.assetid: 0ddb5f18-0c0a-45ea-b7c7-2d4749e3d35d
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# HELP
-
-
-Displays information about the various SFTMIME commands that can be used in Application Virtualization (App-V).
-
-## HELP
-
-
-`SFTMIME [/? | /HELP [VERB:]]`
-
-
-
-
-
-
-
-
-
Parameter
-
Description
-
-
-
-
-
/?, /HELP
-
Displays usage information.
-
-
-
verb
-
The command to run, such as ADD, REFRESH, HELP or REMOVE.
-
-
-
object
-
What the command applies to, such as APP:"Default Application."
-
-
-
parameters
-
Optional parameters for the specified verb and object.
-
-
-
/LOG
-
Log output to the specified path name.
-
-
-
/CONSOLE
-
Displays output in the active console window (default).
-
-
-
/GUI
-
Displays errors in a dialog box (not valid for queries).
-
-
-
-
-
-
-For version 4.6, the following option has been added.
-
-
-
-
-
-
-
-
-
/LOGU
-
If specified, output is logged to the specified path name in UNICODE format.
-
-
-
-
-
-
-The verbs described in the following table are supported.
-
-
-
-
-
-
-
-
-
ADD
-
Adds a new application, package, file type association, or publishing server to the App-V Client.
-
-
-
CONFIGURE
-
Changes the configuration of an application, a package, a file type association, or a publishing server.
-
-
-
DELETE
-
Removes applications, packages, file type associations, or servers.
-
-
-
LOAD
-
Loads a package into the file system cache.
-
-
-
REPAIR
-
Resets your personal settings for an application.
-
-
-
REFRESH
-
Triggers a publishing server refresh.
-
-
-
PUBLISH
-
Publishes an application shortcut to the user's Start menu, desktop, or other specified location, or can be used to publish the contents of an entire package.
-
-
-
UNPUBLISH
-
Removes the shortcuts and file types for an entire package.
-
-
-
QUERY
-
Gets a current list of applications, packages, file type associations, or publishing servers.
-
-
-
CLEAR
-
Removes your personal settings and desktop configurations for one or more applications.
-
-
-
UNLOAD
-
Unloads a package from the file system cache.
-
-
-
LOCK
-
Locks the application specified in the file system cache.
-
-
-
UNLOCK
-
Unlocks the application specified in the file system cache.
-
-
-
-
-
-
-For more information about the preceding actions, use the following command:
-
-`SFTMIME /HELP VERB:verb`
-
-For example, the following command will display information for the ADD verb:
-
-`SFTMIME /HELP VERB:ADD`
-
-## Related topics
-
-
-[SFTMIME Command Reference](sftmime--command-reference.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-add-a-file-type-association.md b/mdop/appv-v4/how-to-add-a-file-type-association.md
deleted file mode 100644
index bd5e1a7cb5..0000000000
--- a/mdop/appv-v4/how-to-add-a-file-type-association.md
+++ /dev/null
@@ -1,60 +0,0 @@
----
-title: How to Add a File Type Association
-description: How to Add a File Type Association
-author: dansimp
-ms.assetid: cccfbd00-51ba-4a60-a598-ee97f5ea1215
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Add a File Type Association
-
-
-You can use the following procedure to add a file type association, using the **File Type Associations** node in the Application Virtualization Client Management Console.
-
-**To add a file type association**
-
-1. Right-click the **File Type Associations** node, and select **New Association** from the pop-up menu.
-
-2. Complete the first step of the dialog box by completing the following information, and then click **Next**:
-
- 1. **Extension**—Enter a new file name extension. This field is blank by default.
-
- 2. **Create a new file type with this description**—Select this radio button to enter a new file type description in the active field. This button is selected by default, and the active field is blank.
-
- 3. **Apply this file type to all users**—Select this check box when you want this association to be global for all users. By default, this box is cleared.
-
- 4. **Link this extension with an existing file type**—Select this radio button to associate the extension with an existing file type. Pick a file type from the drop-down list. When you choose this option, **Next** is changed to **Finish**.
-
-3. Complete the second step of the dialog box by completing the following information, and then click **Finish** to return to the Client Management Console:
-
- 1. **Change Icon**—Click this button to change the application icon. Select one of the available icons, or browse to a new location and select an icon.
-
- 2. **Open files with the selected application**—Select this radio button to open the file with an existing application. Choose an application from the drop-down list of available applications.
-
- 3. **Open file with the association described in this OSD file**—Select this radio button to specify an Open Software Descriptor (OSD) file that determines the application used to open the file. Use the browse button to select an existing location, or enter a path or HTTP-formatted URL in this field.
-
-## Related topics
-
-
-[How to Add an Application](how-to-add-an-application.md)
-
-[How to Publish Application Shortcuts](how-to-publish-application-shortcuts.md)
-
-[How to Delete a File Type Association](how-to-delete-a-file-type-association.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-add-a-package-by-using-the-command-line.md b/mdop/appv-v4/how-to-add-a-package-by-using-the-command-line.md
deleted file mode 100644
index 6b9c002b72..0000000000
--- a/mdop/appv-v4/how-to-add-a-package-by-using-the-command-line.md
+++ /dev/null
@@ -1,64 +0,0 @@
----
-title: How to Add a Package by Using the Command Line
-description: How to Add a Package by Using the Command Line
-author: dansimp
-ms.assetid: e75af49e-811a-407a-a7f0-6de8562b9188
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Add a Package by Using the Command Line
-
-
-The following procedures list the steps that are necessary to add a virtual application package to the Application Virtualization (App-V) Client on a specific computer.
-
-**To add a virtual application package for a specific user**
-
-- Run the following command under the user account of the person who is to get the package. The command adds and publishes the package for that user.
-
- `SFTMIME ADD PACKAGE:”name” /MANIFEST `
-
-**To add a virtual application package for all users**
-
-- Run the following command under an account that has administrator rights. The package is added and published for all users on the computer.
-
- `SFTMIME ADD PACKAGE:”name” /MANIFEST /GLOBAL`
-
-**To add a package using an electronic software distribution system**
-
-1. If you are using an electronic software distribution system that runs the commands under the computer’s **SYSTEM** account, the package is published for that account only, unless you use the /GLOBAL switch. Run the following command to add and publish the package for all users on the computer:
-
- `SFTMIME ADD PACKAGE:”name” /MANIFEST /GLOBAL`
-
-2.
-
- If you want to add the package for specific users only, run the **ADD PACKAGE** command, and then explicitly publish the package for each user by running the following **PUBLISH PACKAGE** command under each person’s user account:
-
- `SFTMIME ADD PACKAGE:”name” /MANIFEST `
-
- `SFTMIME PUBLISH PACKAGE:”name” /MANIFEST `
-
- Publishing the package without the GLOBAL parameter grants the user access to the applications in the package and publishes the file types and shortcuts that are listed in the manifest to the user’s profile. Permissions required are “Manage file type associations” (**ManageTypes**) and “Publish shortcuts” (**PublishShortcut**).
-
-## Related topics
-
-
-[How to Delete All Virtual Applications by Using the Command Line](how-to-delete-all-virtual-applications-by-using-the-command-line.md)
-
-[How to Remove a Package by Using the Command Line](how-to-remove-a-package-by-using-the-command-line.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-add-a-package-version.md b/mdop/appv-v4/how-to-add-a-package-version.md
deleted file mode 100644
index 6a4b7c4372..0000000000
--- a/mdop/appv-v4/how-to-add-a-package-version.md
+++ /dev/null
@@ -1,57 +0,0 @@
----
-title: How to Add a Package Version
-description: How to Add a Package Version
-author: dansimp
-ms.assetid: dbb829c1-e5cb-4a2f-bc17-9a9bb50c671c
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Add a Package Version
-
-
-In the Application Virtualization Server Management Console, when you resequence a package, you can use the following procedure to add the new version to your servers for streaming.
-
-**Note**
-When you upgrade a package with a new version, you can leave the existing version in place or delete it and leave only the newest one. You might want to leave the old version in place for compatibility with legacy documents or so that you can test the new version before making it available to all users.
-
-
-
-**To add a package version**
-
-1. Copy the new SFT file to the application server's content folder. If resequencing did not add changes to the Open Software Descriptor (OSD), icon (ICO), or Sequencer Project (SPRJ) files, you do not need to copy those. You can include those files if you want all the files to display the same date.
-
-2. In left pane of the Application Virtualization Server Management Console, expand the **Packages** node.
-
-3. Right-click the package you want to upgrade, and choose **Add Version**.
-
-4. In the **Add Package Version** dialog box, browse for or type the path name for the new application file in the **Full path for package file** field. This must be an SFT file.
-
-5. Click **Next**.
-
-6. The **Summary** dialog box shows the file location and prompts you to copy the file there if you have not already done so. Click **Finish** after you have verified the information.
-
- The new version is now complete and ready to stream.
-
-## Related topics
-
-
-[How to Delete a Package](how-to-delete-a-packageserver.md)
-
-[How to Manage Packages in the Server Management Console](how-to-manage-packages-in-the-server-management-console.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-add-a-package.md b/mdop/appv-v4/how-to-add-a-package.md
deleted file mode 100644
index b9f409c2cb..0000000000
--- a/mdop/appv-v4/how-to-add-a-package.md
+++ /dev/null
@@ -1,66 +0,0 @@
----
-title: How to Add a Package
-description: How to Add a Package
-author: dansimp
-ms.assetid: 5407fdbe-e658-44f6-a9b8-a566b81dedce
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Add a Package
-
-
-You can add a package from the Application Virtualization Server Management Console in the following ways:
-
-- Import an application, which creates the package automatically in the process.
-
-- Add a package manually.
-
-It is recommended that you import applications instead of adding them manually. For more information about importing applications, see [How to Import an Application](how-to-import-an-applicationserver.md).
-
-**To add a package manually**
-
-1. In the Application Virtualization Server Management Console, right-click the **Packages** node in the left pane and choose **New Package**.
-
-2. In the **New Package** dialog box, type a name in the **Package Name** field.
-
-3. Browse for or type a path name in the **Full path for package file** field. This must be an SFT file.
-
- **Note**
- If you browse to the SFT file, replace the local path (such as C:\\Program Files\\User\_Apps\\Virtual\_App\_Server\\content) with the server's static host name or IP address. Using the variable *%SFT\_SOFTGRIDSERVER%* requires per-client computer configuration.
-
- In dialog boxes that refer to Virtual Application Servers, you must use a network location, such as the server's static host name or IP address, that your users can access. The application's Open Software Descriptor (OSD) file can replace the placeholder variable *%SFT\_SOFTGRIDSERER%* with the server's static host name or IP address. If you leave the placeholder variable, you must set this variable on each client computer that will access that server. Set a User or System variable on each computer for SFT\_SOFTGRIDSERVER. The variable value must be the server's static host name or IP address. If you set a variable, exit the Client session, log out of and back into Microsoft Windows, and then restart the session on each computer that had a session running and had the variable set.
-
-
-
-4. Click **Next**.
-
-5. The **Summary** dialog box shows the file location and prompts you to copy the file to the location if you have not already done so. Click **Finish** after you have verified the information.
-
- **Note**
- If you are managing applications on a remote server, in the next dialog box, type only the path of the file relative to the server's content root.
-
-
-
-## Related topics
-
-
-[How to Import an Application](how-to-import-an-applicationserver.md)
-
-[How to Manage Packages in the Server Management Console](how-to-manage-packages-in-the-server-management-console.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-add-a-server.md b/mdop/appv-v4/how-to-add-a-server.md
deleted file mode 100644
index 0fb467e68f..0000000000
--- a/mdop/appv-v4/how-to-add-a-server.md
+++ /dev/null
@@ -1,61 +0,0 @@
----
-title: How to Add a Server
-description: How to Add a Server
-author: dansimp
-ms.assetid: 1f31678a-8edf-4d35-a812-e4a2abfd979b
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Add a Server
-
-
-To help you manage your Application Virtualization Management Servers more efficiently, organize them into server groups. After you create a server group in the Application Virtualization Server Management Console, you can use the following procedure to add a server to the group.
-
-**Note**
-All servers in a server group must be connected to the same data store.
-
-
-
-**To add a server to a group**
-
-1. Click the **Server Groups** node in the left pane to expand the list of server groups.
-
-2. Right-click the desired server group, and select **New Application Virtualization Management Server**.
-
-3. In the **New Server Group Wizard**, enter the **Display Name** and the **DNS Host Name**.
-
-4. Leave the default values in the **Maximum Memory Allocation** field for the server cache and the **Warn Memory Allocation** field to specify the threshold warning level.
-
-5. Click **Next**.
-
-6. In the **Connection Security Mode** dialog, check the **Use enhanced security** box to select enhanced security mode, if desired. If necessary, complete the **Certificate Wizard** or view existing certificates.
-
-7. Click **Next**.
-
-8. In the **App Virt Port Setting** dialog, select the **Use Default Port** or the **User Custom Port** radio button and enter the custom port number.
-
-9. Click **Finish**.
-
-## Related topics
-
-
-[How to Create a Server Group](how-to-create-a-server-group.md)
-
-[How to Remove a Server](how-to-remove-a-server.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-add-an-administrator-group.md b/mdop/appv-v4/how-to-add-an-administrator-group.md
deleted file mode 100644
index 27067fbc52..0000000000
--- a/mdop/appv-v4/how-to-add-an-administrator-group.md
+++ /dev/null
@@ -1,54 +0,0 @@
----
-title: How to Add an Administrator Group
-description: How to Add an Administrator Group
-author: dansimp
-ms.assetid: 2611f33e-6082-4269-b0ba-394174701492
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Add an Administrator Group
-
-
-From the **Administrators** node of the Application Virtualization Server Management Console, you can use the following procedure to add an administrator group.
-
-**To add an administrator group**
-
-1. In the left pane of the Application Virtualization Server Management Console, right-click the **Administrators** node and select **Add Administrator Group**.
-
-2. Complete the **Select Groups** dialog box to add groups.
-
- **Important**
- When completing the **Select Groups** dialog box, you might see the **Multiple Names Found** dialog box, which can display multiple group names. To add more than one group at a time, press **Ctrl** and click the name of each group you want to add. Click **OK** to exit the **Multiple Names Found** dialog box.
-
-
-
-3. Click **OK**.
-
- **Note**
- To add administrator groups to the Application Virtualization Management Server, you must have system administrator or security administrator privileges on the associated data store. If you attempt to create a group without sufficient privileges, the system generates an error message.
-
-
-
-## Related topics
-
-
-[How to Customize an Application Virtualization System in the Server Management Console](how-to-customize-an-application-virtualization-system-in-the-server-management-console.md)
-
-[How to Delete an Administrator Group](how-to-delete-an-administrator-group.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-add-an-application.md b/mdop/appv-v4/how-to-add-an-application.md
deleted file mode 100644
index 760c7f8540..0000000000
--- a/mdop/appv-v4/how-to-add-an-application.md
+++ /dev/null
@@ -1,52 +0,0 @@
----
-title: How to Add an Application
-description: How to Add an Application
-author: dansimp
-ms.assetid: 0147233d-f369-4796-8e34-fb1d894af732
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Add an Application
-
-
-You can use the following procedure to add an application directly from the **Results** pane of the **Application** node in the Application Virtualization Client Management Console.
-
-**To add an application**
-
-1. In the **Results** pane, right-click and select **New Application** from the pop-up menu.
-
-2. On the wizard page, you can perform the following tasks:
-
- 1. **Change Icon**—Displays a standard Windows icon browser. Browse to and select the desired icon.
-
- 2. **OSD File Path or URL**—Enter a local absolute path, a full UNC path (shared file or directory on a network), or an HTTP URL.
-
- 3. **(OSD browse button)**—Displays the standard Windows **Open File** dialog box. Browse to find the desired file.
-
-3. Click **Finish** to add the application to the **Results** pane.
-
-## Related topics
-
-
-[How to Add a File Type Association](how-to-add-a-file-type-association.md)
-
-[How to Publish Application Shortcuts](how-to-publish-application-shortcuts.md)
-
-[How to Delete a File Type Association](how-to-delete-a-file-type-association.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-apply-a-package-accelerator-to-create-a-virtual-application-package---app-v-46-sp1-.md b/mdop/appv-v4/how-to-apply-a-package-accelerator-to-create-a-virtual-application-package---app-v-46-sp1-.md
deleted file mode 100644
index 2616fee08d..0000000000
--- a/mdop/appv-v4/how-to-apply-a-package-accelerator-to-create-a-virtual-application-package---app-v-46-sp1-.md
+++ /dev/null
@@ -1,110 +0,0 @@
----
-title: How to Apply a Package Accelerator to Create a Virtual Application Package (App-V 4.6 SP1)
-description: How to Apply a Package Accelerator to Create a Virtual Application Package (App-V 4.6 SP1)
-author: dansimp
-ms.assetid: ca0bd514-2bbf-4130-8c77-98d991cbe016
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Apply a Package Accelerator to Create a Virtual Application Package (App-V 4.6 SP1)
-
-
-You can use App-V Package Accelerators to automatically generate a new virtual application package. For more information about Package Accelerators, see [About App-V Package Accelerators (App-V 4.6 SP1)](about-app-v-package-accelerators--app-v-46-sp1-.md).
-
-**Important**
-Disclaimer: The Application Virtualization Sequencer does not give you any license rights to the software application you are using to create a Package Accelerator. You must abide by all end user license terms for such application. It is your responsibility to make sure the software application’s license terms allow you to create a Package Accelerator using Application Virtualization Sequencer.
-
-
-
-**Note**
-Before starting this procedure, copy the required Package Accelerator locally to the computer running the App-V Sequencer. You should also copy all required installation files for the package to a local directory on the computer running the Sequencer. This is the directory that you have to specify in step 5 of this procedure.
-
-
-
-Use the following procedure to create a virtual application package by using a Package Accelerator.
-
-**To create a virtual application package by using an App-V Package Accelerator**
-
-1. To start the App-V Sequencer, on the computer that is running the App-V Sequencer, click **Start** / **All Programs** / **Microsoft Application Virtualization** / **Microsoft Application Virtualization Sequencer**.
-
-2. To start the **Create New Package Wizard**, click **Create a New Virtual Application Package**. To create the package, select the **Create Package using a Package Accelerator** check box, and then click **Next**.
-
-3. On the **Select Package Accelerator** page, to specify the Package Accelerator that will be used to create the new virtual application package, click **Browse** to locate the Package Accelerator that you want to use. Click **Next**.
-
- **Important**
- If the publisher of the Package Accelerator cannot be verified and does not contain a valid digital signature, in the **Security Warning** dialog box, you must confirm that you trust the source of the Package Accelerator before you click **Run**.
-
-
-
-4. On the **Guidance** page, review the publishing guidance information displayed in the information pane. The information displayed was added when the Package Accelerator was created and contains information about creating and publishing the package. To export the guidance information to a text (.txt) file, click **Export** and specify the location where the file should be saved, and then click **Next**.
-
-5. On the **Select Installation Files** page, to create a local folder that contains all required installation files for the package, click **Make New Folder** and specify where the folder should be saved. You must also specify a name to be assigned to the folder. You must then copy all required installation files to the location that you specified. If the folder that contains the installation files already exists on the computer running the Sequencer, click **Browse** to select the folder.
-
- Alternatively, if you have already copied the installation files to a directory on this computer, click **Make New Folder**, browse to the folder that contains the installation files, and then click **Next**.
-
- **Note**
- You can specify the following types of supported installation files:
-
- - Windows Installer files(**.msi**
-
- - .cab files
-
- - Compressed files with a .zip file name extension
-
- - The actual application files
-
- The following file types are not supported: **.msp** and.exe files. If you specify an **.exe** file you must extract the installation files manually.
-
-
-
-~~~
-If the Package Accelerator requires an application be installed prior to applying the Package Accelerator and you have installed the application, on the **Local Installation** page, select the check box **I have installed all applications**, and then click **Next**.
-~~~
-
-6. On the **Package Name** page, specify a name that will be associated with the package. The name specified identifies the package in the App-V Management Console. Click **Next**.
-
-7. On the **Create Package** page, provide comments that will be associated with the package. The comments should contain identifying information about the package you are creating. To confirm the location where the package is created, review the information displayed in **Save Location**. To compress the package, select **Compress Package**. Select the **Compress Package** check box if the package will be streamed across the network, or when the package size exceeds 4 GB.
-
- To create the package, click **Create**. After the package has been created, click **Next**.
-
-8. On the **Configure Software** page, to enable the Sequencer to configure the applications contained in the package, select **Configure Software**. This step is useful for configuring any associated tasks that must be completed to run the application on target computers, such as configuring any associated license agreements.
-
- If you select **Configure Software**, the following items are configured by the Sequencer as part of this step:
-
- - **Load Package**. The Sequencer loads the files associated with the package. It can take several seconds to up to an hour to decode the package.
-
- - **Run Each Program**. Optionally run the programs contained in the package. This step is helpful for completing any associated license or configuration tasks that are required to run the application before you deploy and run the package on target computers. To run all the programs at one time, select at least one program, and then click **Run All**. To run specific programs, select the program or programs you want to run, and then click **Run Selected**. Complete the required configuration tasks, and then close the applications. It can take several minutes for all programs to run. Click **Next**.
-
- - **Save Package**. The Sequencer saves the package.
-
- - **Primary Feature Block**. The Sequencer optimizes the package for streaming by rebuilding the primary feature block.
-
- If you do not want to configure the applications, click **Skip this step**, and to go to step 9 of this procedure, and then click **Next**.
-
-9. On the **Completion** page, after you have reviewed the information displayed in the **Virtual Application Package Report** pane, click **Close**.
-
- The package is now available in the Sequencer. To edit the package properties, click **Edit \[Package Name\]**. For more information about modifying a package, see [How to Modify an Existing Virtual Application Package (App-V 4.6 SP1)](how-to-modify-an-existing-virtual-application-package--app-v-46-sp1-.md).
-
-## Related topics
-
-
-[Configuring the Application Virtualization Sequencer (App-V 4.6 SP1)](configuring-the-application-virtualization-sequencer--app-v-46-sp1-.md)
-
-[How to Create App-V Package Accelerators (App-V 4.6 SP1)](how-to-create-app-v-package-accelerators--app-v-46-sp1-.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-apply-an-app-v-project-template--app-v-46-sp1-.md b/mdop/appv-v4/how-to-apply-an-app-v-project-template--app-v-46-sp1-.md
deleted file mode 100644
index ca8c706037..0000000000
--- a/mdop/appv-v4/how-to-apply-an-app-v-project-template--app-v-46-sp1-.md
+++ /dev/null
@@ -1,53 +0,0 @@
----
-title: How to Apply an App-V Project Template (App-V 4.6 SP1)
-description: How to Apply an App-V Project Template (App-V 4.6 SP1)
-author: dansimp
-ms.assetid: 8ef120ab-8cfb-438c-8136-671167b7bd9d
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Apply an App-V Project Template (App-V 4.6 SP1)
-
-
-You can use an App-V project template to apply common settings associated with an existing virtual application package to a new virtual application package. Using App-V project templates can help streamline the process of creating virtual application packages by configuring common settings before you begin sequencing an application.
-
-**Note**
-You can only apply an App-V project template when you are creating a new virtual application package. Applying project templates to existing virtual application packages is not supported. Additionally, you cannot use a project template in conjunction with a Package Accelerator.
-
-
-
-For more information about creating App-V project templates, see [How to Create an App-V Project Template (App-V 4.6 SP1)](how-to-create-an-app-v-project-template--app-v-46-sp1-.md).
-
-**To apply an App-V project template**
-
-1. To start the Microsoft Application Virtualization Sequencer, on the computer on which App-V Sequencer is installed, click **Start** / **All Programs** / **Microsoft Application Virtualization** / **Microsoft Application Virtualization Sequencer**.
-
-2. To create a new virtual application package by using an App-V project template, click **File** / **New From Template**.
-
-3. To select the project template that you want to use, browse to the directory where the project template is saved, select the project template, and then click **Open**.
-
-4. Create the new virtual application package. The settings saved with the specified template will be applied to the new virtual application package that you are creating. For more information about creating a new virtual application package, see [How to Determine Which Type of Application to Sequence (App-V 4.6 SP1)](how-to-determine-which-type-of-application-to-sequence---app-v-46-sp1-.md), and select the appropriate procedure.
-
-## Related topics
-
-
-[Tasks for the Application Virtualization Sequencer (App-V 4.6 SP1)](tasks-for-the-application-virtualization-sequencer--app-v-46-sp1-.md)
-
-[How to Create an App-V Project Template (App-V 4.6 SP1)](how-to-create-an-app-v-project-template--app-v-46-sp1-.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-assign--the-proper-credentials-for-windows-vista.md b/mdop/appv-v4/how-to-assign--the-proper-credentials-for-windows-vista.md
deleted file mode 100644
index f24d17b75f..0000000000
--- a/mdop/appv-v4/how-to-assign--the-proper-credentials-for-windows-vista.md
+++ /dev/null
@@ -1,61 +0,0 @@
----
-title: How to Assign the Proper Credentials for Windows Vista
-description: How to Assign the Proper Credentials for Windows Vista
-author: dansimp
-ms.assetid: cc11d2af-a350-4d16-ba7b-f9c1d89e14b4
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Assign the Proper Credentials for Windows Vista
-
-
-Use the following procedure to configure the App-V Desktop Client for proper Windows Vista credentials.
-
-**Note**
-This procedure must be completed on each non-domain joined computer. Depending on the number of non-domain joined computers in your environment, this could be a very tedious operation. You can use scripts and the command-line interface for Credential Manager to help administrators automate this process.
-
-
-
-**To assign the proper credentials for App-V clients running Windows Vista**
-
-1. With administrator privileges on the App-V Desktop Client running Windows Vista, open the **User Accounts** control panel (Classic Control Panel).
-
-2. Select **Manage your network passwords** from **User Accounts** in the left tasks pane.
-
-3. Select **Add** on the **Stored User Names and Passwords** screen.
-
-4. On the **Stored Credential Properties** screen, provide the information for the App-V infrastructure:
-
- 1. **Log on to:** External name of the publishing server.
-
- 2. **User name:** User name for the external user in the form Domain\\Username.
-
- 3. **Password:** Password for the user account entered in the **User name** field.
-
- 4. Leave **Credential Type** selected, and click **OK**.
-
-5. Click **Close**. The credentials are stored in the credential store for proper authentication to the App-V infrastructure.
-
-## Related topics
-
-
-[Domain-Joined and Non-Domain-Joined Clients](domain-joined-and-non-domain-joined-clients.md)
-
-[How to Assign the Proper Credentials for Windows XP](how-to-assign--the-proper-credentials-for-windows-xp.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-assign--the-proper-credentials-for-windows-xp.md b/mdop/appv-v4/how-to-assign--the-proper-credentials-for-windows-xp.md
deleted file mode 100644
index 9e1d52e3fc..0000000000
--- a/mdop/appv-v4/how-to-assign--the-proper-credentials-for-windows-xp.md
+++ /dev/null
@@ -1,59 +0,0 @@
----
-title: How to Assign the Proper Credentials for Windows XP
-description: How to Assign the Proper Credentials for Windows XP
-author: dansimp
-ms.assetid: cddbd556-d8f9-4981-a947-6e8e3f552b70
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Assign the Proper Credentials for Windows XP
-
-
-Use the following procedure to configure the App-V Desktop Client for proper Windows XP credentials.
-
-**Note**
-After finishing this procedure, the non-domain joined client can perform a publishing refresh without being joined to a domain.
-
-
-
-**To assign the proper credentials for App-V clients running Windows XP**
-
-1. With administrator privileges on the App-V Client running Windows XP, open the **User Accounts** control panel (Classic Control Panel).
-
-2. Click the **Advanced Tab**, and select **Manage Passwords**.
-
-3. On the **Stored User Names and Passwords** screen, click **Add**.
-
-4. On the **Logon Information Properties** screen, fill out the following fields with information from the App-V infrastructure:
-
- 1. **Server:** Name of publishing server external name.
-
- 2. **User name:** User name for external user in the form Domain\\username.
-
- 3. **Password:** Password for the user account entered in the **User name** field.
-
-5. Click **OK**. The credentials will be stored on the client.
-
-## Related topics
-
-
-[Domain-Joined and Non-Domain-Joined Clients](domain-joined-and-non-domain-joined-clients.md)
-
-[How to Assign the Proper Credentials for Windows Vista](how-to-assign--the-proper-credentials-for-windows-vista.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-associate-an-application-with-a-license-group.md b/mdop/appv-v4/how-to-associate-an-application-with-a-license-group.md
deleted file mode 100644
index 84d62ca579..0000000000
--- a/mdop/appv-v4/how-to-associate-an-application-with-a-license-group.md
+++ /dev/null
@@ -1,58 +0,0 @@
----
-title: How to Associate an Application with a License Group
-description: How to Associate an Application with a License Group
-author: dansimp
-ms.assetid: 85639db3-5751-497e-a9e7-ce4770c0b55f
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Associate an Application with a License Group
-
-
-You can enforce licensing restrictions on an application by associating the application with a license group in the Application Virtualization Server Management Console. Depending on the type of license group, you control who has access to the application and how many users can access an application at a time. You can also access license compliance reports for the application.
-
-**Important**
-One or more application license groups must exist for you to associate an application with a license group.
-
-
-
-**To associate an application with a license group**
-
-1. In the left pane of the management console, expand the **Applications** node.
-
-2. Right-click the application you want to add to a license group, and choose **Properties**.
-
-3. On the **General** tab, use the **Application License Group** pull-down menu to choose the group.
-
-4. Click **OK**.
-
- **Note**
- You can alter the **Properties** tab of one application at a time.
-
-
-
-## Related topics
-
-
-[How to Create an Application License Group](how-to-create-an-application-license-group.md)
-
-[How to Manage Application Licenses in the Server Management Console](how-to-manage-application-licenses-in-the-server-management-console.md)
-
-[How to Manage Reports in the Server Management Console](how-to-manage-reports-in-the-server-management-console.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-branch-a-package.md b/mdop/appv-v4/how-to-branch-a-package.md
deleted file mode 100644
index 9b2ab8c069..0000000000
--- a/mdop/appv-v4/how-to-branch-a-package.md
+++ /dev/null
@@ -1,55 +0,0 @@
----
-title: How to Branch a Package
-description: How to Branch a Package
-author: dansimp
-ms.assetid: bfe46a8a-f0ee-4a71-9e9c-64ac08aac9c1
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Branch a Package
-
-
-Use this procedure to modify an existing sequenced application package so you can run it side-by-side with the original sequenced application package. This process is called branching. When you branch a virtual application package you are able to run two versions of the same package. For example, you can apply a service pack to an existing package, and run it side-by-side with the original sequenced virtual application package.
-
-Use the following procedure to branch a sequenced virtual application package.
-
-**To branch a sequenced virtual application package**
-
-1. Open the Microsoft Application Virtualization (App-V) Sequencer. To specify the destination directory that contains the package (.sprj) you want to branch select **File**, **Open**.
-
-2. Navigate to the directory that contains the sequenced application you plan to branch and click **Open**.
-
-3. To save a copy of the package, in the App-V Sequencer, select **File**, **Save As**. Specify a new, unique name, and specify a new unique package root directory for the copy of the package. Click **Save**.
-
- **Important**
- You must specify a new package name or you will overwrite the existing version of the package.
-
-
-
-~~~
-The sequencer will automatically generate new GUID files for the new package. The version number associated with the package will also be automatically appended to the OSD file name.
-~~~
-
-4. After you save the new version you can apply the required configuration changes and save the associated ICO, OSD, SFT, and SPRJ files to correct location on the Application Virtualization (App-V) server.
-
-## Related topics
-
-
-[Tasks for the Application Virtualization Sequencer](tasks-for-the-application-virtualization-sequencer.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-cancel-loading-of-virtual-applications-from-the-desktop-notification-area.md b/mdop/appv-v4/how-to-cancel-loading-of-virtual-applications-from-the-desktop-notification-area.md
deleted file mode 100644
index 32dfc28858..0000000000
--- a/mdop/appv-v4/how-to-cancel-loading-of-virtual-applications-from-the-desktop-notification-area.md
+++ /dev/null
@@ -1,48 +0,0 @@
----
-title: How to Cancel Loading of Virtual Applications from the Desktop Notification Area
-description: How to Cancel Loading of Virtual Applications from the Desktop Notification Area
-author: dansimp
-ms.assetid: 4420a091-a344-48e9-a354-93bc0e2470eb
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Cancel Loading of Virtual Applications from the Desktop Notification Area
-
-
-From the desktop notification area, you can cancel the loading of applications into the cache. Applications are loaded one application at a time; the progress bar shows you the application name, the percentage of application loaded, and the number of applications already processed compared to the total number of the applications queued. You can cancel any application load in progress before it is 100% loaded. You can skip the loading of all remaining applications as well.
-
-**To cancel loading applications**
-
-1. Right-click the Application Virtualization System icon in the notification area.
-
-2. Select **Cancel** and **Load All** from the pop-up menu.
-
-3. Click one of the following buttons in the **Microsoft App Virt - Confirm Cancel** dialog to achieve the desired results:
-
- 1. **Skip**—To skip the currently loading application.
-
- 2. **Skip All**—To skip all remaining applications.
-
- 3. **Continue**—To cancel the dialog box and continue loading applications.
-
-## Related topics
-
-
-[How to Use the Desktop Notification Area for Application Virtualization Client Management](how-to-use-the-desktop-notification-area-for-application-virtualization-client-management.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-change-an-application-icon.md b/mdop/appv-v4/how-to-change-an-application-icon.md
deleted file mode 100644
index 9e9dbf95b0..0000000000
--- a/mdop/appv-v4/how-to-change-an-application-icon.md
+++ /dev/null
@@ -1,39 +0,0 @@
----
-title: How to Change an Application Icon
-description: How to Change an Application Icon
-author: dansimp
-ms.assetid: bd6cfb22-086b-43fd-b6f9-1907b5f16e83
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Change an Application Icon
-
-
-You can use the following procedure to change an icon associated with the selected application directly from the **Results** pane of the **Application** node in the Application Virtualization Client Management Console.
-
-**To change an application icon**
-
-1. Move the cursor to the **Results** pane, and right-click the desired application.
-
-2. Select **Properties**.
-
-3. On the **General** tab, click **Change Icon**.
-
-4. Select the desired icon, or browse to another location to select the icon. After you've selected the icon, click **OK**. The new icon appears in the **Results** pane.
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-change-an-application-iconserver.md b/mdop/appv-v4/how-to-change-an-application-iconserver.md
deleted file mode 100644
index 19445774d2..0000000000
--- a/mdop/appv-v4/how-to-change-an-application-iconserver.md
+++ /dev/null
@@ -1,44 +0,0 @@
----
-title: How to Change an Application Icon
-description: How to Change an Application Icon
-author: dansimp
-ms.assetid: 52c870eb-4a54-410b-8abf-79395a53f846
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Change an Application Icon
-
-
-You can use the following procedure to change an icon associated with the selected application directly from the **Results** pane of the **Application** node in the Application Virtualization Server Management Console.
-
-**To change an application icon**
-
-1. Right-click the application, and select **Properties** from the pop-up menu.
-
-2. On the **General** tab, click the **Browse** button next to **Icon Path**.
-
-3. Select the desired icon, or browse to another location to select the icon. After you've selected the icon, click **Open**. Click **OK** to apply.
-
- The new icon appears in the **Results** pane. The new icon is also displayed in the menus and in the client desktop notification area.
-
-## Related topics
-
-
-[How to Manage Applications in the Server Management Console](how-to-manage-applications-in-the-server-management-console.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-change-deployment-properties.md b/mdop/appv-v4/how-to-change-deployment-properties.md
deleted file mode 100644
index f9eb0b5d3f..0000000000
--- a/mdop/appv-v4/how-to-change-deployment-properties.md
+++ /dev/null
@@ -1,62 +0,0 @@
----
-title: How to Change Deployment Properties
-description: How to Change Deployment Properties
-author: dansimp
-ms.assetid: 0a214a7a-cc83-4d04-89f9-5727153be918
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Change Deployment Properties
-
-
-You can use the following procedures to change the **Deployment** tab information for an application you are sequencing, including the Application Virtualization server URL, the operating systems required by the virtualized applications, and the output options for the virtual application to be installed.
-
-**To change the server URL**
-
-1. Select the streaming protocol from the drop-down list box.
-
-2. Enter the host name of the virtual application server or the server group's load balancer. You can use the actual host name or IP address.
-
-3. Specify the port number on which the virtual application server or load balancer will listen for an Application Virtualization Desktop Client request for the streamed application.
-
-4. Specify the relative path on the virtual application server where the software package is stored.
-
-**To change the application operating systems requirements**
-
-1. To add the required operating system(s), select it in the **Available** list and click the arrow button pointing to the **Selected** operating systems list control.
-
-2. To remove an operating system, select it in the **Selected** list control, and click the arrow button pointing to the **Available** operating systems list control.
-
-**To change the application output options**
-
-1. From the **Compression Algorithm** drop-down list, select the compression method to use when streaming the application.
-
-2. Select the **Enforce Security Descriptors** check box to ensure security descriptors of the packaged applications are enforced when deployed.
-
-3. Select **Generate Difference File** to generate a difference file for the application from the previous sequenced version.
-
-4. Select **Generate Microsoft Windows Installer (MSI) Package** to create an installer package.
-
-## Related topics
-
-
-[About the Deployment Tab](about-the-deployment-tab.md)
-
-[Sequencer Console](sequencer-console.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-change-import-search-paths.md b/mdop/appv-v4/how-to-change-import-search-paths.md
deleted file mode 100644
index fef1c273d9..0000000000
--- a/mdop/appv-v4/how-to-change-import-search-paths.md
+++ /dev/null
@@ -1,48 +0,0 @@
----
-title: How to Change Import Search Paths
-description: How to Change Import Search Paths
-author: dansimp
-ms.assetid: 0125f2bf-4958-4854-a5a4-a63afe5bb986
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Change Import Search Paths
-
-
-You can use the following procedure to change the import search path directly from the **Application Virtualization** node in the Application Virtualization Client Management Console. The import search path is used by the client to find the SFT file when you use the console to import an SFT file. If it can find the file in this search path, it will not need to prompt you for a path.
-
-**To change the import search path**
-
-1. Right-click the **Application Virtualization** node, and select **Properties** from the pop-up menu.
-
-2. On the **Import Search Path** tab in the **Properties** dialog box, click **Add** to display a standard **Browse** dialog box and browse to the desired location.
-
-3. Highlight a path, and click **Remove** to delete this path.
-
-4. Use the **Move Up** and **Move Down** buttons to control the order in which the paths will be searched.
-
-5. Click **OK** or **Apply** to change the setting.
-
-## Related topics
-
-
-[How to Configure the Client in the Application Virtualization Client Management Console](how-to-configure-the-client-in-the-application-virtualization-client-management-console.md)
-
-[How to Import an Application](how-to-import-an-application.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-change-package-properties.md b/mdop/appv-v4/how-to-change-package-properties.md
deleted file mode 100644
index 565e4c27e9..0000000000
--- a/mdop/appv-v4/how-to-change-package-properties.md
+++ /dev/null
@@ -1,63 +0,0 @@
----
-title: How to Change Package Properties
-description: How to Change Package Properties
-author: dansimp
-ms.assetid: 6050916a-d4fe-4dac-8f2a-47308dbbf481
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Change Package Properties
-
-
-You can use the following procedures to modify an Application Virtualization package name and its associated comments.
-
-If this is the first time the package has been created, you can also change the sequencing parameter block size, which determines how a sequenced application package is streamed from an Application Virtualization Server to an Application Virtualization Desktop Client.
-
-**Note**
-When selecting a block size, consider the size of the SFT file and your network bandwidth. A file with a smaller block size takes longer to stream over the network, but it is less bandwidth intensive. Files with larger block sizes might stream faster, but they use more network bandwidth. Through experimentation, you can discover the optimum block size for streaming applications on your network.
-
-
-
-The remainder of the package properties on the **Properties** tab is automatically generated and cannot be modified on this tab.
-
-**To change the package name or comments**
-
-1. Click the **Properties** tab.
-
-2. In the **Package Name** text box, enter or edit the single name used for the package, which can contain multiple applications.
-
-3. In the **Comments** text box, optionally enter or edit any comments. The suggested best practice is to provide detail information about the package and sequencing.
-
-4. From the **File** menu, select **Save**.
-
-**To change the block size**
-
-1. Click the **Properties** tab.
-
-2. On the **Block Size** drop-down list, select **4 KB**, **16 KB**, **32 KB**, or **64 KB**.
-
-3. From the **File** menu, select **Save**.
-
-## Related topics
-
-
-[About the Properties Tab](about-the-properties-tab.md)
-
-[Sequencer Console](sequencer-console.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-change-the-cache-size-and-the-drive-letter-designation.md b/mdop/appv-v4/how-to-change-the-cache-size-and-the-drive-letter-designation.md
deleted file mode 100644
index 0aed8a88e3..0000000000
--- a/mdop/appv-v4/how-to-change-the-cache-size-and-the-drive-letter-designation.md
+++ /dev/null
@@ -1,70 +0,0 @@
----
-title: How to Change the Cache Size and the Drive Letter Designation
-description: How to Change the Cache Size and the Drive Letter Designation
-author: dansimp
-ms.assetid: e7d7b635-079e-41aa-a5e6-655f33b4e317
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Change the Cache Size and the Drive Letter Designation
-
-
-You can change the cache size and drive letter designation directly from the **Application Virtualization** node in the Application Virtualization Client Management Console.
-
-**Note**
-After the cache size has been set, it cannot be made smaller.
-
-
-
-**To change the cache size**
-
-1. Right-click the **Application Virtualization** node, and select **Properties** from the pop-up menu.
-
-2. Select the **File System** tab on the **Properties** dialog box. In the **Client Cache Configuration Settings** section, click one of the following radio buttons to choose how to manage the cache space:
-
- **Important**
- If you select the **Use free disk space threshold** setting, the value you enter will set the cache size to the total disk size minus the free disk space threshold number you entered. If you then want revert to using the **Use maximum cache size** setting, you must specify a larger number than the existing cache size. Otherwise, the error “New size must be larger than the existing cache size” will appear.
-
-
-
-~~~
-- **Use maximum cache size**
-
- Enter a numeric value from 100 to 1,048,576 (1 TB) in the **Maximum size (MB)** field to specify the maximum size of the cache. The value shown in **Reserved Cache Size** indicates the amount of cache in use.
-
-- **Use free disk space threshold**
-
- Enter a numeric value to specify the amount of free disk space, in MB, that the cache must leave available on the disk. This allows the cache to grow until the amount of free disk space reaches this limit. The value shown in **Free disk space remaining** indicates how much disk space is unused.
-~~~
-
-3. Click **OK** or **Apply** to change the setting.
-
-**To change the drive letter designation**
-
-1. Right-click the **Application Virtualization** node, and select **Properties** from the pop-up menu.
-
-2. On the **File System** tab in the **Properties** dialog box, in the **Drive to use** field, select the desired drive letter from the drop-down list of available drive letters. This setting becomes effective when the computer is rebooted.
-
-3. Click **OK** or **Apply** to change the setting.
-
-## Related topics
-
-
-[How to Configure the Client in the Application Virtualization Client Management Console](how-to-configure-the-client-in-the-application-virtualization-client-management-console.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-change-the-log-reporting-levels-and-reset-the-log-files.md b/mdop/appv-v4/how-to-change-the-log-reporting-levels-and-reset-the-log-files.md
deleted file mode 100644
index 4c3247ee57..0000000000
--- a/mdop/appv-v4/how-to-change-the-log-reporting-levels-and-reset-the-log-files.md
+++ /dev/null
@@ -1,64 +0,0 @@
----
-title: How to Change the Log Reporting Levels and Reset the Log Files
-description: How to Change the Log Reporting Levels and Reset the Log Files
-author: dansimp
-ms.assetid: 9561d6fb-b35c-491b-a355-000064583194
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Change the Log Reporting Levels and Reset the Log Files
-
-
-You can use the following procedure to change the log reporting level from the **Application Virtualization** node in the Application Virtualization Management Console. When the log file reaches the maximum size (default is 256 MB), a reset is forced when the next write to the log occurs. A reset causes a new log file to be created, and the old file is renamed as a backup.
-
-**To change the log reporting level**
-
-1. Right-click the **Application Virtualization** node, and select **Properties** from the pop-up menu.
-
-2. On the **General** tab in the **Properties** dialog box, from the **Log Level** drop-down list, select the desired log level.
-
- **Note**
- If you choose **Verbose** as the logging level, the log files will grow large very quickly. This might inhibit client performance, so best practice is to use this log level only for diagnosing specific problems.
-
-
-
-3. On the **General** tab in the **Properties** dialog box, from the **System Log Level** drop-down list, select the desired log level.
-
- **Note**
- The **System Log Level** setting controls the level of messages sent to the system event log. The logged messages are identical to the messages that get logged to the client event log, but they are stored in a different location.
-
-
-
-4. Click **OK** or **Apply** to change the setting.
-
-**To reset the log file**
-
-1. Right-click the **Application Virtualization** node, and select **Properties** from the pop-up menu.
-
-2. On the **General** tab in the **Properties** dialog box, click **Reset Log** to back up the current log file and immediately start a new log file. The backup log files are stored in the same folder.
-
-3. Click **OK** or **Apply** to change the setting.
-
-## Related topics
-
-
-[How to Configure the Client in the Application Virtualization Client Management Console](how-to-configure-the-client-in-the-application-virtualization-client-management-console.md)
-
-[User Access Permissions in Application Virtualization Client](user-access-permissions-in-application-virtualization-client.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-change-the-server-cache-size.md b/mdop/appv-v4/how-to-change-the-server-cache-size.md
deleted file mode 100644
index 5b61e12a03..0000000000
--- a/mdop/appv-v4/how-to-change-the-server-cache-size.md
+++ /dev/null
@@ -1,57 +0,0 @@
----
-title: How to Change the Server Cache Size
-description: How to Change the Server Cache Size
-author: dansimp
-ms.assetid: 24e63744-21c3-458e-b137-9592f4fe785c
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Change the Server Cache Size
-
-
-You can use the following procedure to change the cache size for any server directly from the Application Virtualization Server Management Console.
-
-**Note**
-Although you can change the cache size, unless your configuration specifically requires you to change the size, it is recommended that you leave the cache size set to the default values.
-
-
-
-**To change the server cache size**
-
-1. Click the **Server Groups** node in the left pane to expand the list of server groups.
-
-2. In the **Results** pane, double-click the desired server group to display the list of servers in the group.
-
-3. In the **Results** pane, right-click the desired server and select **Properties**.
-
-4. Select the **Advanced** tab.
-
-5. Enter a value in the **Maximum Memory Allocation** field for the server cache, and enter a value for the threshold warning level in the **Warn Memory Allocation** field.
-
-6. Enter a value in the **Maximum Block Size** field. This number must be greater than or equal to the maximum block size of the largest package that will be streamed from the server.
-
-7. Click **OK**.
-
-## Related topics
-
-
-[How to Change the Server Port](how-to-change-the-server-port.md)
-
-[How to Manage Servers in the Server Management Console](how-to-manage-servers-in-the-server-management-console.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-change-the-server-logging-level-and-the-database-parameters.md b/mdop/appv-v4/how-to-change-the-server-logging-level-and-the-database-parameters.md
deleted file mode 100644
index baeeef43e1..0000000000
--- a/mdop/appv-v4/how-to-change-the-server-logging-level-and-the-database-parameters.md
+++ /dev/null
@@ -1,142 +0,0 @@
----
-title: How to Change the Server Logging Level and the Database Parameters
-description: How to Change the Server Logging Level and the Database Parameters
-author: dansimp
-ms.assetid: e3ebaee5-6c4c-4aa8-9766-c5aeb00f477a
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Change the Server Logging Level and the Database Parameters
-
-
-You can use the following procedures to change the logging level and the database log parameters from the Application Virtualization Server Management Console.
-
-The following logging levels are available:
-
-- Transaction Only
-
-- Fatal Errors
-
-- Errors
-
-- Warnings/Errors
-
-- Info/Warnings/Errors
-
-- Verbose
-
-**Note**
-Because of the size of the log file produced when you use **Verbose** mode, the recommendation is that you do not run production servers with this level of logging set.
-
-
-
-The database logging parameters determine the database driver type, access credentials, and location of the logging database.
-
-**To change the logging level for Management Servers**
-
-1. Click the **Server Groups** node to display the server groups.
-
-2. Right-click the server group, and select **Properties**.
-
-3. In the **Properties** dialog box, select the **Logging** tab.
-
-4. In the **Server Group Properties** dialog box, select the server and then click **Edit**.
-
-5. In the **Add/Edit Log Module** dialog box, select the logging level from the **Event Type** drop-down list.
-
-6. Click **OK**.
-
-7. In the **Server Group Properties** dialog box, click **OK** or **Apply**.
-
-**To change the logging level for Streaming Servers**
-
-1. Edit the following registry key value to change the logging level:
-
- - HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Microsoft\\SoftGrid\\4.5\\DistributionServer\\LogLevel
-
-2. Select one of the following values to set the logging level.
-
-
-
-
-
-
-
-
-
Value
-
Logging Level
-
-
-
-
-
0
-
Transactions Only
-
-
-
1
-
Fatal Errors
-
-
-
2
-
Errors
-
-
-
3
-
Warnings/Errors
-
-
-
4
-
Information/ Warnings/Errors
-
-
-
5
-
Verbose
-
-
-
-
-
-
-**To change database log parameters**
-
-1. Click the **Server Groups** node to display the server groups.
-
-2. Right-click the server group, and select **Properties**.
-
-3. In the **Properties** dialog box, select the **Logging** tab.
-
-4. In the **Server Group Properties** dialog box, select the server and then click **Edit**.
-
-5. In the **Add/Edit Log Module** dialog box, select a database driver from the **Database Driver** drop-down list.
-
-6. Enter a **DNS Host Name**.
-
-7. Click the **Dynamically Determine Port** check box, or enter a port number in the **Port** field.
-
-8. Enter a **Service Name** in the corresponding field.
-
-9. Click **OK**.
-
-10. On the **Server Group Properties** dialog box, click **OK** or **Apply**.
-
-## Related topics
-
-
-[How to Customize an Application Virtualization System in the Server Management Console](how-to-customize-an-application-virtualization-system-in-the-server-management-console.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-change-the-server-port.md b/mdop/appv-v4/how-to-change-the-server-port.md
deleted file mode 100644
index 14d1933fb9..0000000000
--- a/mdop/appv-v4/how-to-change-the-server-port.md
+++ /dev/null
@@ -1,59 +0,0 @@
----
-title: How to Change the Server Port
-description: How to Change the Server Port
-author: dansimp
-ms.assetid: 0b4a262c-4816-48d0-b7c6-e496bb0d7370
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Change the Server Port
-
-
-From the Application Virtualization Server Management Console, you can use the following procedure to change the server communication port for any server.
-
-**To change the server port**
-
-1. Click the **Server Groups** node in the left pane to expand the list of server groups.
-
-2. In the **Results** pane, double-click the desired server group to display the list of servers in the group.
-
-3. In the **Results** pane, right-click the desired server and select **Properties.**
-
-4. Select the **Ports** tab.
-
-5. Enter the **Port** number.
-
- **Note**
- The port number can be any value between 1 and 65,535. The default values are 554 for RTSP and 322 for RTSPS.
-
-
-
-6. Click **OK** to change the port number.
-
-7. Click **OK** to exit the dialog box.
-
-8. Click **OK** at the prompt.
-
-## Related topics
-
-
-[How to Change the Server Cache Size](how-to-change-the-server-cache-size.md)
-
-[How to Manage Servers in the Server Management Console](how-to-manage-servers-in-the-server-management-console.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-change-the-size-of-the-filesystem-cache.md b/mdop/appv-v4/how-to-change-the-size-of-the-filesystem-cache.md
deleted file mode 100644
index db72c07843..0000000000
--- a/mdop/appv-v4/how-to-change-the-size-of-the-filesystem-cache.md
+++ /dev/null
@@ -1,46 +0,0 @@
----
-title: How to Change the Size of the FileSystem Cache
-description: How to Change the Size of the FileSystem Cache
-author: dansimp
-ms.assetid: 6ed17ba3-293b-4482-b3fa-31e5f606dad6
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Change the Size of the FileSystem Cache
-
-
-You can change the size of the FileSystem cache by using the command line. This action requires a complete reset of the cache, and it requires administrative rights.
-
-**To change the size of the FileSystem cache**
-
-1. Set the following registry value to 0 (zero):
-
- HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Microsoft\\SoftGrid\\4.5\\Client\\AppFS\\State
-
-2. Set the following registry value to the maximum cache size, in MB, that is necessary to hold the packages—for example, 8192 MB:
-
- HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Microsoft\\SoftGrid\\4.5\\Client\\AppFS\\FileSize
-
-3. Restart the computer.
-
-## Related topics
-
-
-[How to Configure the App-V Client Registry Settings by Using the Command Line](how-to-configure-the-app-v-client-registry-settings-by-using-the-command-line.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-change-user-access-permissions.md b/mdop/appv-v4/how-to-change-user-access-permissions.md
deleted file mode 100644
index e935af3cad..0000000000
--- a/mdop/appv-v4/how-to-change-user-access-permissions.md
+++ /dev/null
@@ -1,49 +0,0 @@
----
-title: How to Change User Access Permissions
-description: How to Change User Access Permissions
-author: dansimp
-ms.assetid: 21b60cc7-5395-401e-a374-6ef0d58872b7
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Change User Access Permissions
-
-
-Use the following procedure to change user access permissions in the Application Virtualization Client Management Console.
-
-**Note**
-Before changing users access permissions, ensure that any permissions changes are consistent with the organization's guidelines for granting user access.
-
-
-
-**To change user access permissions**
-
-1. Right-click the **Application Virtualization** node, and select **Properties** from the pop-up menu.
-
-2. On the **Permissions** tab on the **Properties** dialog box, scroll through the list of permissions and select the check boxes that correspond to the permissions you want to grant to users of this computer. Administrators have access to all the permissions regardless of the settings on this tab.
-
-3. Click **OK** or **Apply** to change the setting.
-
-## Related topics
-
-
-[How to Configure the Client in the Application Virtualization Client Management Console](how-to-configure-the-client-in-the-application-virtualization-client-management-console.md)
-
-[User Access Permissions in Application Virtualization Client](user-access-permissions-in-application-virtualization-client.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-clear-an-application.md b/mdop/appv-v4/how-to-clear-an-application.md
deleted file mode 100644
index 2fba3e47a3..0000000000
--- a/mdop/appv-v4/how-to-clear-an-application.md
+++ /dev/null
@@ -1,40 +0,0 @@
----
-title: How to Clear an Application
-description: How to Clear an Application
-author: dansimp
-ms.assetid: 247b8f40-531c-413e-a2e5-fc990ed0a51a
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Clear an Application
-
-
-You can clear an application from the console directly from the **Results** pane of the **Application** node in the Application Virtualization Client Management Console. When you clear an application, the system removes the settings, shortcuts, and file type associations that correspond to the application and also removes the application from the user’s list of applications.
-
-**Note**
-When you clear an application from the console, you can no longer use that application. However, the application remains in cache and is still available to other users on the same system. After a publishing refresh, the cleared applications will again become available to you. If there are multiple applications in a package, the user's settings are not removed until all of the applications are cleared.
-
-
-
-**To clear an application from the console**
-
-1. Move the cursor to the **Results** pane, right-click the desired application, and select **Clear** from the pop-up menu.
-
-2. At the confirmation prompt, click **Yes** to remove the application or click **No** to cancel the operation.
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-configure-a-read-only-cache-on-the-app-v-client--rds--sp1.md b/mdop/appv-v4/how-to-configure-a-read-only-cache-on-the-app-v-client--rds--sp1.md
deleted file mode 100644
index 0a694a6795..0000000000
--- a/mdop/appv-v4/how-to-configure-a-read-only-cache-on-the-app-v-client--rds--sp1.md
+++ /dev/null
@@ -1,186 +0,0 @@
----
-title: How to Configure a Read-only Cache on the App-V Client (RDS)
-description: How to Configure a Read-only Cache on the App-V Client (RDS)
-author: dansimp
-ms.assetid: b6607fe2-6f92-4567-99f1-d8e3c8a591e0
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 08/30/2016
----
-
-
-# How to Configure a Read-only Cache on the App-V Client (RDS)
-
-
-**Important**
-You must be running App-V 4.6, SP1 to use this procedure.
-
-
-
-You can deploy the App-V client by using a shared cache that is populated with all the applications required for all users. Then you configure the App-V Remote Desktop Services (RDS) Clients to use the same cache file. Users are granted access to specific applications by using the App-V publishing process. Because the cache is already preloaded with all applications, no streaming occurs when a user starts an application. However, the packages used to prepopulate the cache must be put on an App-V server that supports Real Time Streaming Protocol (RTSP) streaming and that grants access permissions to the App-V Clients. If you publish the applications by using an App-V Management Server, you can use it to provide this streaming function.
-
-**Note**
-The details outlined in these procedures are intended as examples only. You might use different methods to complete the overall process.
-
-
-
-## Deploying the App-V Client in an RDS Scenario
-
-
-The deployment process consists of four primary tasks:
-
-- Creating and populating the master shared cache file
-
-- Copying the shared cache file to the server storage
-
-- Configuring the App-V client software
-
-- Managing the update deployment cycle for the shared cache file after the initial deployment
-
-These tasks require careful planning. We recommend that you prepare and document a methodical, reproducible process for your organization to follow. This is especially important for the preparation and deployment of the master shared cache file, and for the ongoing management of application updates, each of which require an update to the master shared cache. Use the following procedures to complete these primary tasks.
-
-**Note**
-Although you can publish the applications by using several different methods, the following procedures are based on your using an App-V Management Server for publishing.
-
-
-
-**To configure the read-only cache for initial deployment**
-
-1. Set up and configure an App-V Management Server to provide user authentication and publishing support.
-
-2. Populate the Content folder of this Management Server with all the application packages required for all users.
-
-3. Set up a staging computer that has the App-V Client installed. Log on to the staging computer by using an account that has access to all applications so that the complete set of applications are published to the computer, and then stream the applications to cache so that they are fully loaded.
-
- **Important**
- The staging computer must use the same operating system type and system architecture as those used by the VMs on which the App-V Client will run.
-
-
-
-4. Restart the staging computer in safe mode to make sure that the drivers are not started, because this would lock the cache file.
-
- **Note**
- Or, you can stop and disable the Application Virtualization service, and then restart the computer. After the file is copied, remember to enable and start the service again.
-
-
-
-5. Copy the Sftfs.fsd cache file to a SAN where all the RDS servers can access it, such as in a shared folder. Set the folder access permissions to Read-only for the group Everyone and to Full Control for administrators who will manage the cache file updates. The location of the cache file can be obtained from the registry AppFS\\FileName.
-
- **Important**
- You must put the FSD file in a location that has the responsiveness and reliability equal to locally attached storage performance, for example, a SAN.
-
-
-
-6. Install the App-V RDS Client on each RDS server, and then configure it to use the read-only cache by adding the following registry key values to the AppFS key on the client. The AppFS key is located at HKEY\_LOCAL\_MACHINE\\SOFTWARE\\\]Microsoft\\SoftGrid\\4.5\\Client\\AppFS for 32-bit computers and at HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Wow6432Node\\Microsoft\\SoftGrid\\4.5\\Client\\AppFS for 64-bit computers.
-
-
-
-
-
-
-
-
-
-
-
Key
-
Type
-
Value
-
Purpose
-
-
-
-
-
FileName
-
String
-
path of FSD
-
Specifies the path of the shared cache file, for example, \RDSServername\Sharefolder\SFTFS.FSD (Required).
-
-
-
ReadOnlyFSD
-
DWORD
-
1
-
Configures the client to operate in Read-Only mode. This ensures that the client will not try to stream updates to the package cache. (Required)
-
-
-
ErrorLogLocation
-
String
-
path of error log (.etl) file
-
Entry used to specify the path of the error log. (Recommended. Use a local path such as C:\Logs\Sftfs.etl).
-
-
-
-
-
-
-7. Configure each RDS server in the farm to use the publishing server and to use publishing update when users log on. As users log on to the RDS servers, a publishing update cycle occurs and publishes all the applications for which their account is authorized. These applications are run from the shared cache.
-
-**To configure the RDS client for package upgrade**
-
-1. Complete the upgrade and testing of the application package.
-
-2. Upgrade the package on the App-V server. Then, publish and stream the new version of the applications to the client on the staging computer so that they are fully loaded into cache.
-
-3. Restart the staging computer in safe mode to ensure the drivers are not started.
-
- **Note**
- Or, you can first stop and then disable the Application Virtualization service in the Services.msc, and restart the computer. After the file has been copied, remember to enable and start the service again.
-
-
-
-4. Copy the Sftfs.fsd cache file to a SAN where all the RDS servers can access it, such as in a shared folder. You can use a different file name, for example, SFTFS\_V2.FSD, to distinguish the new version.
-
-5. To configure the App-V RDS Client on each RDS server in the farm to use the updated shared cache file, change the AppFS registry key FILENAME value to point to the location of the updated file, for example, \\\\RDSServername\\Sharefolder\\SFTFS\_V2.FSD. This guarantees that each RDS server receives the updated copy of the cache when the App-Vclient drivers restart.
-
- **Important**
- You must restart the RDS servers in order to use the updated shared cache file.
-
-
-
-## How to Use Symbolic Links when Upgrading the Cache
-
-
-Instead of changing the AppFS key FILENAME value every time that a new cache file is deployed that contains new or upgraded packages, you can use a symbolic link in the following operating systems: Windows Vista, Windows 7, and Windows Server 2008. For more information about symbolic links, see [Symbolic Links](https://go.microsoft.com/fwlink/?LinkId=157626) (https://go.microsoft.com/fwlink/?LinkId=157626). In contrast, Windows XP does not support the use of symbolic links, and you must use junction points instead. For more information about junctions, see [article 205524](https://go.microsoft.com/fwlink/?LinkId=182553) in the Microsoft Knowledge Base (https://go.microsoft.com/fwlink/?LinkId=182553), and also the tool [Junction v1.05](https://go.microsoft.com/fwlink/?LinkId=182554) (https://go.microsoft.com/fwlink/?LinkId=182554).
-
-**To configure a symbolic link to reference the cache**
-
-1. During the initial deployment stage, open a Command Prompt window as a local administrator on the RDS server host operating system.
-
-2. Create a symbolic link by using the MKLINK command, and then configure it to point to the Sftfs.fsd file.
-
- ** mklink symlinkname \\\\rdshostserver\\sharefolder\\sftfs.fsd**
-
-3. On the VDI Master VM Image, open a Command Prompt window by using the **Run as administrator** option and grant remote link permissions so that the VM can access the symbolic link on the VDI Host operating system. By default, remote link permissions are disabled.
-
- **fsutil behavior set SymlinkEvaluation R2R:1**
-
- **Note**
- On the storage server, appropriate link permissions must be enabled. Depending on the location of link and the Sftfs.fsd file, the permissions are **L2L:1** or **L2R:1** or **R2L:1** or **R2R:1**.
-
-
-
-4. When you configure the App-V RDS Client, set the AppFS key FILENAME value equal to the UNC path of the FSD file that is using the symbolic link. For example, set the file name to \\\\VDIHostserver\\Symlinkname. When the App-V client first accesses the cache, the symbolic link passes to the client a handle to the cache file. The client continues to use that handle as long as the client is running. The value of the symbolic link can safely be updated even if existing clients have the old shared cache open.
-
-5. When you must upgrade a package or to add a new package to the cache, follow steps 1 through 4 of the upgrade procedure. Then, delete the symbolic link and re-create it to point to the new version of the shared cache file. This guarantees that each RDS server receives the updated copy of the cache when the App-V client drivers restart. When the RDS server is restarted, the App-V client receives a handle to the updated copy of the cache because the client uses the path that contains the updated symbolic link. Then, the users have access to the new and updated applications.
-
-## Related topics
-
-
-[How to Install Application Virtualization Management Server](how-to-install-application-virtualization-management-server.md)
-
-[How to Manually Install the Application Virtualization Client](how-to-manually-install-the-application-virtualization-client.md)
-
-[How to Install the Client by Using the Command Line](how-to-install-the-client-by-using-the-command-line-new.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-configure-a-read-only-cache-on-the-app-v-client--vdi-.md b/mdop/appv-v4/how-to-configure-a-read-only-cache-on-the-app-v-client--vdi-.md
deleted file mode 100644
index 8fd997eafd..0000000000
--- a/mdop/appv-v4/how-to-configure-a-read-only-cache-on-the-app-v-client--vdi-.md
+++ /dev/null
@@ -1,197 +0,0 @@
----
-title: How to Configure a Read-only Cache on the App-V Client (VDI)
-description: How to Configure a Read-only Cache on the App-V Client (VDI)
-author: dansimp
-ms.assetid: 7a41e017-9e23-4a6a-a659-04d23f008b83
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 08/30/2016
----
-
-
-# How to Configure a Read-only Cache on the App-V Client (VDI)
-
-
-In Microsoft Application Virtualization (App-V) 4.6 the Client supports using a shared read-only cache. The shared read-only cache enables the Client to use disk space efficiently in a Virtual Desktop Infrastructure (VDI) system, where users run applications on Virtual Machines (VM) that are hosted in a data center server environment and share network storage on a Storage Area Network (SAN). The following procedures provide an overview of the process that is required to implement the App-V Client in either of the primary VDI architectures, known as “Pooled VM” or “Static VM”. It is assumed that you are familiar with the planning, deployment, and operation of the App-V system and its components, and also the operation and management of the VDI server. For more information about App-V, see [Application Virtualization](https://go.microsoft.com/fwlink/?LinkId=122939) (https://go.microsoft.com/fwlink/?LinkId=122939)
-
-**Note**
-The details outlined in these procedures are intended as examples only. You might use different methods to complete the overall process.
-
-
-
-## Deploying the App-V Client in a VDI Scenario
-
-
-You can deploy the App-V Client in a VDI scenario by using a shared read-only cache that has been populated with all the applications required for all users. You then configure the VDI Master VM Image so that all the App-V Clients use the same cache file. Users are granted access to specific applications by using the App-V publishing process. Since the cache is already preloaded with all applications, no streaming occurs when a user starts an application. However, the packages used to prepopulate the cache must be put on an App-V server that supports Real Time Streaming Protocol (RTSP) streaming and that grants access permissions to the App-V Clients. If you publish the applications by using an App-V Management Server, you can use it to provide this streaming function.
-
-The deployment process consists of four primary tasks:
-
-- Creating and populating the master shared cache file
-
-- Copying the shared cache file to the VDI server storage
-
-- Configuring the App-V client software on the VDI Master Image
-
-- Managing the update deployment cycle for the shared cache file after the initial deployment
-
-These tasks require careful planning. We recommend that you prepare and document a methodical, reproducible process for your organization to follow. This is especially important for the initial preparation and deployment of the master shared cache file, and for the on-going management of application updates, each of which require an update to the master shared cache. Use the following procedures to complete these primary tasks.
-
-**Note**
-Although you can publish the applications by using several different methods, the following procedures are based on the use of an App-V Management Server for publishing.
-
-
-
-**To configure the read-only cache for initial deployment in a Pooled VM VDI or Static VM VDI scenario**
-
-1. Set up and configure an App-V Management Server in a VM on the VDI server to provide user authentication and publishing support.
-
-2. Populate the Content folder of this Management Server with all the application packages required for all users.
-
-3. Set up a staging computer that has the App-V Client installed. Log on to the staging computer with an account that has access to all applications so that the complete set of applications are published to the computer, and then stream the applications to cache so that they are fully loaded.
-
- **Important**
- The staging computer must use the same operating system type and system architecture as those used by the VMs on which the App-V Client will run.
-
-
-
-4. Restart the staging computer in Safe Mode to ensure the drivers are not started, which would lock the cache file.
-
- **Note**
- Alternatively, you can stop and disable the Application Virtualization service, and then restart the computer. After the file has been copied, remember to enable and start the service again.
-
-
-
-5. Copy the Sftfs.fsd cache file to the VDI server’s SAN where all the VMs can access it, such as in a shared folder. Set the folder access permissions to Read-only for the group Everyone and to Full Control for administrators who will manage the cache file updates. The location of the cache file can be obtained from the registry AppFS\\FileName.
-
- **Important**
- You must put the FSD file in a location that has the responsiveness and reliability equivalent to locally attached storage performance, for example, a SAN.
-
-
-
-6. Install the App-V Desktop Client on the VDI Master VM Image, and then configure it to use the read-only cache by adding the following registry key values to the AppFS key on the client. The AppFS key is located at HKEY\_LOCAL\_MACHINE\\SOFTWARE\\\[Wow6432Node\\\]Microsoft\\SoftGrid\\4.5\\Client\\AppFS.
-
-
-
-
-
-
-
-
-
-
-
Key
-
Type
-
Value
-
Purpose
-
-
-
-
-
FileName
-
String
-
path to FSD
-
Specifies the path to the shared cache file, for example, \VDIServername\Sharefolder\SFTFS.FSD (Required).
-
-
-
ReadOnlyFSD
-
DWORD
-
1
-
Configures the client to operate in Read-Only mode. This ensures that the client will not attempt to stream updates to the package cache. (Required)
-
-
-
ErrorLogLocation
-
String
-
path to error log (.etl) file
-
Entry used to specify the path to the error log. (Recommended. Use a local path such as C:\Logs\Sftfs.etl).
-
-
-
-
-
-
-7. Configure the Master VM Image client to use the publishing server and to use publishing refresh at logon. As users log on to the VDI system and their VM is built from the Master VM Image, a publishing refresh cycle occurs and publishes all the applications for which their account is authorized. These applications are run from the shared cache.
-
-**To configure the client for package upgrade in a Pooled VM scenario**
-
-1. Complete the upgrade and testing of the application package.
-
-2. Upgrade the package on the App-V server. Then, publish and stream the new version of the applications to the client on the staging computer so that they are fully loaded into cache.
-
-3. Restart the staging computer in Safe Mode to ensure the drivers are not started.
-
- **Note**
- Alternatively, you can stop and disable the Application Virtualization service in the Services.msc, and then restart the computer. After the file has been copied, remember to enable and start the service again.
-
-
-
-4. Copy the Sftfs.fsd cache file to the VDI server’s SAN where all the VMs can access it, such as in a shared folder. You can use a different filename, for example, SFTFS\_V2.FSD, to distinguish the new version.
-
-5. To configure the App-V Desktop Client on the VDI Master VM Image to use the updated shared cache file, change the AppFS registry key FILENAME value to point to the location of the updated file, for example, \\\\VDIServername\\Sharefolder\\SFTFS\_V2.FSD. When users log off and then log on again, a new VM is created for them by using the updated Master Image. All their user settings will be retained and applied to the new VM. Then they have access to the updated applications.
-
-**To configure the client for package upgrade in a Static VM scenario**
-
-1. Complete the upgrade and testing of the application package.
-
-2. Upgrade the package on the App-V server. Then, publish and stream the new version of the applications to the client on the staging computer so that the applications are fully loaded into cache.
-
-3. Restart the staging computer in Safe Mode to ensure that the drivers are not started.
-
- **Note**
- Alternatively, you can stop and disable the Application Virtualization service in the Services.msc, and then restart the computer. After the file has been copied, remember to enable and start the service again.
-
-
-
-4. Copy the Sftfs.fsd cache file to the VDI server’s SAN where all the VMs can access it, such as in a shared folder. You can use a different filename, for example, SFTFS\_V2.FSD, to distinguish the new version.
-
-5. To configure the App-V Desktop Client on the VDI Master VM Image to use the updated shared cache file, change the AppFS registry key FILENAME value to point to the location of the updated file, for example, \\\\VDIServername\\Sharefolder\\SFTFS\_V2.FSD. This ensures that new users get the new version.
-
-6. Create a script that edits the AppFS key FILENAME value to set it to the location of the updated cache, for example, \\\\VDIServername\\Sharefolder\\SFTFS\_V2.FSD. Configure this script to run when the user logs off or logs on so that it runs before the App-V client drivers start, for example, by using Group Policy settings. When users log off and log on again, their existing VM is updated, and they will use the updated copy of the cache. Then, they have access to the updated applications.
-
-## How to Use Symbolic Links when Upgrading the Cache
-
-
-Instead of modifying the AppFS key FILENAME value every time that a new cache file is deployed that contains new or upgraded packages, you can use a symbolic link in the following operating systems: Windows Vista, Windows 7, and Windows Server 2008. For more information about symbolic links, see [Symbolic Links](https://go.microsoft.com/fwlink/?LinkId=157626) (https://go.microsoft.com/fwlink/?LinkId=157626). In contrast, Windows XP does not support the use of symbolic links, and you must use junction points instead. For more information about junctions, see [article 205524](https://go.microsoft.com/fwlink/?LinkId=182553) in the Microsoft Knowledge Base (https://go.microsoft.com/fwlink/?LinkId=182553), and also the tool [Junction v1.05](https://go.microsoft.com/fwlink/?LinkId=182554) (https://go.microsoft.com/fwlink/?LinkId=182554).
-
-**To configure a symbolic link to reference the cache**
-
-1. During the initial deployment stage, open a Command Prompt window as a local administrator on the VDI server host operating system.
-
-2. Create a symbolic link by using the MKLINK command, and then configure it to point to the Sftfs.fsd file.
-
- ** mklink symlinkname \\\\vdihostserver\\sharefolder\\sftfs.fsd**
-
-3. On the VDI Master VM Image, open a Command Prompt window by using the **Run as administrator** option and grant remote link permissions so that the VM can access the symbolic link on the VDI Host operating system. By default, remote link permissions are disabled.
-
- **fsutil behavior set SymlinkEvaluation R2R:1**
-
- **Note**
- On the storage server, appropriate link permissions must be enabled. Depending on the location of link and the Sftfs.fsd file, the permissions are **L2L:1** or **L2R:1** or **R2L:1** or **R2R:1**.
-
-
-
-4. When you configure the App-V Desktop Client on the VDI Master VM Image, set the AppFS key FILENAME value equal to the UNC path of the FSD file that is using the symbolic link; for example, set it to \\\\VDIHostserver\\Symlinkname. When the App-V client first accesses the cache, the symbolic link passes to the client a handle to the cache file. The client continues to use that handle as long as the client is running. The value of the symbolic link can safely be updated even if existing clients have the old shared cache open.
-
-5. When you must upgrade a package or to add a new package to the cache, follow steps 1 through 5 of the upgrade procedure for either the Static VM or Pooled VM scenario. Then, delete the symbolic link and re-create it to point to the new version of the shared cache file. When the VM is restarted, the client receives a handle to the updated copy of the cache because the VM uses the path that contains the updated symbolic link. Then, the users have access to the new and updated applications.
-
-## Related topics
-
-
-[How to Install Application Virtualization Management Server](how-to-install-application-virtualization-management-server.md)
-
-[How to Manually Install the Application Virtualization Client](how-to-manually-install-the-application-virtualization-client.md)
-
-[How to Install the Client by Using the Command Line](how-to-install-the-client-by-using-the-command-line-new.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-configure-management-server-security-post-installation.md b/mdop/appv-v4/how-to-configure-management-server-security-post-installation.md
deleted file mode 100644
index c14a8c48a6..0000000000
--- a/mdop/appv-v4/how-to-configure-management-server-security-post-installation.md
+++ /dev/null
@@ -1,61 +0,0 @@
----
-title: How to Configure Management Server Security Post-Installation
-description: How to Configure Management Server Security Post-Installation
-author: dansimp
-ms.assetid: 71979fa6-3d0b-4a8b-994e-cb728d013090
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Configure Management Server Security Post-Installation
-
-
-Use the App-V Management Console to add the certificate and configure the App-V Management Server for enhanced security. You can use the following procedure to configure security post-installation.
-
-**To configure Management Server security post-installation**
-
-1. Open the App-V Management Console, and connect to the **Management Service** with App-V administrator privileges.
-
-2. Expand the server, expand **Server Groups**, and then select the appropriate server group with which the Management Server was registered.
-
-3. Right-click the Management Server object, and select **Properties**.
-
-4. On the **Ports** tab, click **Server Certificate** and complete the wizard to select the properly provisioned certificate.
-
- **Note**
- If no certificates are displayed in the wizard, a certificate has not been provisioned or the certificate does meet the requirements of App-V.
-
-
-
-5. Click **Next** to continue on to the **Welcome To Certificate Wizard** page.
-
-6. Select the correct certificate in the **Available Certificates** screen.
-
-7. Click **Finish**.
-
-8. After completing the wizard, clear **RTSP** as an available listening port. This prevents connections from being made over a non-secure communication channel.
-
-9. Click **Apply**, and restart the **Microsoft Virtual Application Server** service. Use the service’s MMC snap-in to accomplish this task.
-
-## Related topics
-
-
-[How to Configure Streaming Server Security Post-Installation](how-to-configure-streaming-server-security-post-installation.md)
-
-[Troubleshooting Certificate Permission Issues](troubleshooting-certificate-permission-issues.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-configure-microsoft-sql-server-mirroring-support-for-app-v.md b/mdop/appv-v4/how-to-configure-microsoft-sql-server-mirroring-support-for-app-v.md
deleted file mode 100644
index 2b4a53819a..0000000000
--- a/mdop/appv-v4/how-to-configure-microsoft-sql-server-mirroring-support-for-app-v.md
+++ /dev/null
@@ -1,92 +0,0 @@
----
-title: How to Configure Microsoft SQL Server Mirroring Support for App-V
-description: How to Configure Microsoft SQL Server Mirroring Support for App-V
-author: dansimp
-ms.assetid: 6d069eb5-109f-460a-836a-de49473b7035
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 08/30/2016
----
-
-
-# How to Configure Microsoft SQL Server Mirroring Support for App-V
-
-
-You can use the following procedure to configure your Microsoft Application Virtualization (App-V) environment to use Microsoft SQL Server database mirroring. Configuring database mirroring can help with disaster recovery and failover scenarios. App-V 4.5 SP2 supports all modes of database mirroring currently available for Microsoft SQL Server 2005 and SQL Server 2008.
-
-**Note**
-This procedure is written for administrators who are familiar with setting up and configuring SQL Server databases and database mirroring with Microsoft SQL Server, and therefore covers only the specific configuration settings that are unique to App-V.
-
-
-
-**To configure your App-V environment to use Microsoft SQL Server database mirroring**
-
-1. Set up SQL Server database mirroring of the App-V database following your standard business practices for database mirroring. Use the following links for general information about implementing Microsoft SQL Server database mirroring:
-
- - **Microsoft SQL 2005**—[Setting Up Database Mirroring](https://go.microsoft.com/fwlink/?LinkId=187478) (https://go.microsoft.com/fwlink/?LinkId=187478)
-
- - **Microsoft SQL 2008**—[Setting Up Database Mirroring](https://go.microsoft.com/fwlink/?LinkId=187477) (https://go.microsoft.com/fwlink/?LinkId=187477)
-
- In addition, you can find Best Practices information in [Database Mirroring Best Practices and Performance Considerations](https://go.microsoft.com/fwlink/?LinkId=190270) (https://go.microsoft.com/fwlink/?LinkId=190270).
-
-2. After mirroring has been set up, verify that the App-V database shows a status of **(Principal, Synchronized)**, and the mirrored database shows a status of **(Mirror, Synchronized / Restoring)**. Resolve any mirroring issues before proceeding to the next step. For additional information about monitoring the status, see [Monitoring Mirroring Status](https://go.microsoft.com/fwlink/?LinkId=190279) (https://go.microsoft.com/fwlink/?LinkId=190279).
-
-3. On the SQL Server computer that hosts the mirror of the App-V database, create the SQL Server Login for the network service account of the App-V Management Server by using the account name **<domain>\\<ManagementServerHostName>$**.
-
-4. Install the Microsoft SQL Server Native Client on the App-V Management Server, and on the computer running the App-V Management Web Service if installed on a different computer. If you plan to have additional App-V Management Servers connect to the mirrored SQL database for load balancing, you must install the Microsoft SQL Server Native Client on those computers as well. You can download the Microsoft SQL Server Native Client from the [Microsoft SQL Server 2008 Feature Pack](https://go.microsoft.com/fwlink/?LinkId=187479) page in the Microsoft Download Center (https://go.microsoft.com/fwlink/?LinkId=187479).
-
-5. Check the registry key **HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Microsoft\\Softgrid\\4.5\\Server\\SQLServerName** and make sure that it contains only the host name of the SQL Server. If it includes an instance name, for example *serverhostname\\instancename*, the instance name must be removed.
-
- **Important**
- The App-V Management Server uses the TCP/IP networking library to communicate with the SQL Server when database mirroring is enabled, and therefore instance names cannot be used. The port numbers must be specified in the registry keys instead.
-
-
-
-6. Check the registry key **HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Microsoft\\Softgrid\\4.5\\Server\\SQLServerPort** and make sure that it contains the port number that is used for SQL on the SQL Server computer. If you are using a named instance this key value must be set to the port that is used for the named instance.
-
-7. Create the registry key **HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Microsoft\\Softgrid\\4.5\\Server\\SQLFailoverServerName** as REG\_SZ and then set the value to the host name of the SQL Server that hosts the mirror.
-
-8. Create the registry key **HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Microsoft\\Softgrid\\4.5\\Server\\SQLFailoverServerPort** as DWORD and then set the value to the port number that is used for SQL on the computer that is running SQL Server to host the mirror. If you are using a named instance for the mirror this key value must be set to the port number that is used for the named instance.
-
-9. On the computer that is running the App-V Management Web Service, configure the Universal Data Link (UDL) text file. In the directory where App-V is installed, double-click **SftMgmt.udl** and specify the following values:
-
- - On the **Provider** tab, select the OLE DB provider **SQL Server Native Client 10.0**.
-
- - Click **Next** to select the **Connection** tab. In the **Server Name** box, enter the server name of the SQL Server. Next, select **Use Windows NT Integrated Security**. Finally, click the list **Select the database**, and then select the App-V database name.
-
- - Click the **All** tab, and then select the entry **Failover Partner**. Click **Edit Value**, and then enter the server name of the failover SQL Server. Click **OK**.
-
- **Important**
- The App-V system uses Kerberos authentication. Therefore, when you configure SQL mirroring where Kerberos Authentication is enabled on the SQL Server and the SQL Server service runs under a domain user account, you must manually configure an SPN. For more information, see “When SQL Service Uses Domain-Based Account” in the article [Configuring App-V Administration for a Distributed Environment](https://go.microsoft.com/fwlink/?LinkId=203186) (https://go.microsoft.com/fwlink/?LinkId=203186).
-
-
-
-10. To verify that database mirroring is running correctly, test the failover and confirm that the App-V Management Server continues to function correctly.
-
- **Important**
- Proceed with care, and follow your standard business practices to ensure that system operations are not disrupted in the event of a failure.
-
-
-
-~~~
-After the failover has occurred successfully, as verified by using the SQL Server status monitoring information, right-click the **Applications** node in the App-V Management Console, and then select **Refresh**. The list of applications should display normally if the system is working correctly.
-~~~
-
-## Related topics
-
-
-[How to Perform Administrative Tasks in the Application Virtualization Server Management Console](how-to-perform-administrative-tasks-in-the-application-virtualization-server-management-console.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-configure-servers-for-esd-based-deployment.md b/mdop/appv-v4/how-to-configure-servers-for-esd-based-deployment.md
deleted file mode 100644
index 1c79254fd6..0000000000
--- a/mdop/appv-v4/how-to-configure-servers-for-esd-based-deployment.md
+++ /dev/null
@@ -1,50 +0,0 @@
----
-title: How to Configure Servers for ESD-Based Deployment
-description: How to Configure Servers for ESD-Based Deployment
-author: dansimp
-ms.assetid: 96208522-3a0c-4606-a10b-fc0ec0a12021
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Configure Servers for ESD-Based Deployment
-
-
-This section provides procedures you can use to configure the Application Virtualization Streaming Servers, the IIS server, and the file server for your electronic software distribution–based deployment strategy.
-
-## In This Section
-
-
-[How to Configure the Application Virtualization Streaming Servers](how-to-configure-the-application-virtualization-streaming-servers.md)
-Provides a step-by-step procedure for configuring the Application Virtualization Streaming Servers.
-
-[How to Configure the Server for IIS](how-to-configure-the-server-for-iis.md)
-Provides a step-by-step procedure for configuring the IIS server for your electronic software distribution deployment.
-
-[How to Configure the File Server](how-to-configure-the-file-server.md)
-Provides a step-by-step procedure for configuring a local computer that is used as a file share and that streams applications to the Application Virtualization Desktop Client and the Client for Remote Desktop Services (formerly Terminal Services), for a deployment strategy where your site does not have server-class hardware installed.
-
-## Related topics
-
-
-[Electronic Software Distribution-Based Scenario](electronic-software-distribution-based-scenario.md)
-
-[How to Install the Servers and System Components](how-to-install-the-servers-and-system-components.md)
-
-[How to Upgrade the Servers and System Components](how-to-upgrade-the-servers-and-system-components.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-configure-servers-for-server-based-deployment.md b/mdop/appv-v4/how-to-configure-servers-for-server-based-deployment.md
deleted file mode 100644
index 5a4d8e1932..0000000000
--- a/mdop/appv-v4/how-to-configure-servers-for-server-based-deployment.md
+++ /dev/null
@@ -1,59 +0,0 @@
----
-title: How to Configure Servers for Server-Based Deployment
-description: How to Configure Servers for Server-Based Deployment
-author: dansimp
-ms.assetid: 6371c37a-46eb-44e8-ad6b-4430c866c8b4
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Configure Servers for Server-Based Deployment
-
-
-This section provides procedures you can use to configure the Microsoft System Center Application Virtualization (App-V) Management Servers and Microsoft System Center Application Virtualization Streaming Servers, and the Internet Information Services (IIS) and file servers, as appropriate for your Application Virtualization Server-based deployment strategy.
-
-## In This Section
-
-
-[How to Configure the Application Virtualization Management Servers](how-to-configure-the-application-virtualization-management-servers.md)
-Provides a step-by-step procedure for configuring the Application Virtualization Management Servers.
-
-[How to Configure the Application Virtualization Streaming Servers](how-to-configure-the-application-virtualization-streaming-servers.md)
-Provides a step-by-step procedure for configuring the Application Virtualization Streaming Servers.
-
-[How to Configure the Server for IIS](how-to-configure-the-server-for-iis.md)
-Provides a step-by-step procedure for configuring the IIS server for your server-based deployment.
-
-[How to Configure the Server to be Trusted for Delegation](how-to-configure-the-server-to-be-trusted-for-delegation.md)
-Provides detailed instructions about how to configure the server to be trusted for delegation.
-
-[Configuring the Firewall for the App-V Servers](configuring-the-firewall-for-the-app-v-servers.md)
-Describes the firewall settings required for the App-V servers.
-
-[How to Install and Configure the Default Application](how-to-install-and-configure-the-default-application.md)
-Describes how to install and configure the default application for testing the App-V system.
-
-## Related topics
-
-
-[Application Virtualization Server-Based Scenario Overview](application-virtualization-server-based-scenario-overview.md)
-
-[Electronic Software Distribution-Based Scenario](electronic-software-distribution-based-scenario.md)
-
-[How to Install the Servers and System Components](how-to-install-the-servers-and-system-components.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-configure-shortcut-and-file-type-association-behavior-46-only.md b/mdop/appv-v4/how-to-configure-shortcut-and-file-type-association-behavior-46-only.md
deleted file mode 100644
index c668b902eb..0000000000
--- a/mdop/appv-v4/how-to-configure-shortcut-and-file-type-association-behavior-46-only.md
+++ /dev/null
@@ -1,80 +0,0 @@
----
-title: How to Configure Shortcut and File Type Association Behavior
-description: How to Configure Shortcut and File Type Association Behavior
-author: dansimp
-ms.assetid: d6fd1728-4de6-4066-b36b-d4837d593d40
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Configure Shortcut and File Type Association Behavior
-
-
-Shortcut and File Type Association (FTA) publishing policy is defined and controlled by the publishing XML file, which is sent to clients by a publishing server during a publishing refresh operation. When the client receives this information, it adds any newly published data about applications such as the icons and FTAs. Then, it removes any outdated publishing data.
-
-In App-V version 4.6, two registry key values have been defined to enable administrators to control this behavior. By default, shortcuts that are created locally by using the client console are now retained.
-
-## How to Change Shortcut and FTA Behavior
-
-
-Two new DWORD registry values have been defined for the client Configuration registry key, “FileTypePolicy” and “ShortcutPolicy”. These DWORD registry values are not present by default, but they can be added manually. The Configuration registry key is located at HKEY\_LOCAL\_MACHINE\\SOFTWARE\\\[Wow6432Node\\\]Microsoft\\SoftGrid\\4.5\\Client\\Configuration.
-
-There are four policy values defined in the following table and these apply to both registry key values. The following list shows the numeric values for the registry settings, and the behavior applied to file types or shortcuts on a publishing refresh operation.
-
-
-
-
-
-
-
-
-
-
-
Name
-
Type
-
Data (Examples)
-
Description
-
-
-
FileTypePolicy
-
DWORD
-
Default=0x2 (App-V 4.6)
-
(0x0) – “ClientOnly”- remove any existing items from the same publishing information source, and keep only items that are added locally
-
(0x1) – “ServerOnly” - remove any outdated items from the same publishing information source and any items that are added locally, and add the new items
-
(0x2) – “ClientAndServer”- remove any outdated items from the same publishing information source, keep items added locally, and add the new items (default if not present for App-V 4.6)
-
(0x3) – “NoChange” - make no changes to file types or shortcuts
-
-
-
ShortcutPolicy
-
DWORD
-
Default=0x2
-
(0x0) – “ClientOnly”- remove any existing items from the same publishing information source, and keep only items added locally
-
(0x1) – “ServerOnly” - remove any outdated items from the same publishing information source and any items added locally, and add the new items
-
(0x2) – “ClientAndServer”- remove any outdated items from the same publishing information source, keep items added locally, and add the new items (default if not present)
-
(0x3) – “NoChange” - make no changes to file types or shortcuts
-
-
-
-
-
-
-**Note**
-The text values refer to the values for the XML attributes in the publishing XML file. You can set these values manually if you have implemented a custom HTTP publishing solution.
-
-
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-configure-streaming-server-security-post-installation.md b/mdop/appv-v4/how-to-configure-streaming-server-security-post-installation.md
deleted file mode 100644
index afe7d0a2da..0000000000
--- a/mdop/appv-v4/how-to-configure-streaming-server-security-post-installation.md
+++ /dev/null
@@ -1,54 +0,0 @@
----
-title: How to Configure Streaming Server Security Post-Installation
-description: How to Configure Streaming Server Security Post-Installation
-author: dansimp
-ms.assetid: 9bde3677-d1aa-4dcc-904e-bb49a268d748
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Configure Streaming Server Security Post-Installation
-
-
-Configure the App-V Streaming Server for enhanced security through the registry. As with the App-V Management Server, a certificate must be correctly provisioned with the correct EKU identifier for Server Authentication before you complete the following post-installation procedure.
-
-**To configure Streaming Server security post-installation**
-
-1. Create an MMC, add the **Certificates** snap-in, and select **Local Machine certificate store**.
-
-2. Open the **Personal** certificates for the computer, and open the certificate provisioned for App-V.
-
-3. On the **Details** tab, scroll down to the thumbprint and copy the hash in the details pane.
-
-4. Open the registry editor, and navigate to `HKLM\Software\Microsoft\SoftGrid\4.5\Distribution server`.
-
-5. Edit the `X509CertHash` value, paste the thumbprint hash in the value field, and remove all spaces. Click **OK** to accept the edit.
-
-6. In the registry editor, navigate to `HKLM\Software\Microsoft\SoftGrid\4.5\Distribution server\RtspsPorts`.
-
-7. Create a new **DWORD** value named "322," and then enter the decimal value as 322 or the hexadecimal value as 142.
-
-8. Restart the streaming service.
-
-## Related topics
-
-
-[How to Configure Management Server Security Post-Installation](how-to-configure-management-server-security-post-installation.md)
-
-[Troubleshooting Certificate Permission Issues](troubleshooting-certificate-permission-issues.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-configure-the-app-v-client-registry-settings-by-using-the-command-line.md b/mdop/appv-v4/how-to-configure-the-app-v-client-registry-settings-by-using-the-command-line.md
deleted file mode 100644
index 03e3ac7409..0000000000
--- a/mdop/appv-v4/how-to-configure-the-app-v-client-registry-settings-by-using-the-command-line.md
+++ /dev/null
@@ -1,79 +0,0 @@
----
-title: How to Configure the App-V Client Registry Settings by Using the Command Line
-description: How to Configure the App-V Client Registry Settings by Using the Command Line
-author: dansimp
-ms.assetid: 3e3d873f-13d2-402f-97b4-f62d0c399171
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 08/30/2016
----
-
-
-# How to Configure the App-V Client Registry Settings by Using the Command Line
-
-
-After the Application Virtualization (App-V) Client has been deployed and configured during the installation by using the command line, it might be necessary to change one or more client configuration settings. This is accomplished by editing the appropriate registry keys, using one of the following methods:
-
-- Using the Registry Editor directly
-
-- Using a .reg file
-
-- Using a scripting language such as VBScript or Windows PowerShell
-
-There is also an ADM template that you can use. For more information about the ADM template, see .
-
-**Caution**
-Use care when you edit the registry because errors can leave the computer in an unusable state. Be sure to follow your standard business practices that relate to registry edits. Thoroughly test all proposed changes in a test environment before you deploy them to production computers.
-
-
-
-## In This Section
-
-
-**Important**
-On a 64-bit computer, the keys and values described in the following sections will be under HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Wow6432Node\\Microsoft\\SoftGrid\\4.5\\Client.
-
-
-
-[How to Reset the FileSystem Cache](how-to-reset-the-filesystem-cache.md)
-Provides the information that is required to reset the FileSystem cache.
-
-[How to Change the Size of the FileSystem Cache](how-to-change-the-size-of-the-filesystem-cache.md)
-Explains how you can change the size of the cache.
-
-[How to Use the Cache Space Management Feature](how-to-use-the-cache-space-management-feature.md)
-Describes how you can configure the cache space management feature.
-
-[How to Configure the Client Log File](how-to-configure-the-client-log-file.md)
-Describes the various registry key values that control the client log file and how you can change them.
-
-[How to Configure User Permissions](how-to-configure-user-permissions.md)
-Identifies the registry key that controls the user permissions and gives examples of how you can change some permissions.
-
-[How to Configure the Client for Application Package Retrieval](how-to-configure-the-client-for-application-package-retrieval.md)
-Explains how to configure the client to retrieve package content, icons, and file type associations from different sources, and provides several examples of the correct path format.
-
-[How to Configure the Client for Disconnected Operation Mode](how-to-configure-the-client-for-disconnected-operation-mode.md)
-Provides information about how to configure the various settings associated with disconnected operations mode.
-
-[How to Configure Shortcut and File Type Association Behavior](how-to-configure-shortcut-and-file-type-association-behavior-46-only.md)
-Describes the registry key values that control shortcuts and file type associations in the App-V client, and provides details on how to configure them.
-
-## Related topics
-
-
-[Application Virtualization Client](application-virtualization-client.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-configure-the-app-v-sequencer.md b/mdop/appv-v4/how-to-configure-the-app-v-sequencer.md
deleted file mode 100644
index 615d3a60b6..0000000000
--- a/mdop/appv-v4/how-to-configure-the-app-v-sequencer.md
+++ /dev/null
@@ -1,46 +0,0 @@
----
-title: How to Configure the App-V Sequencer
-description: How to Configure the App-V Sequencer
-author: dansimp
-ms.assetid: 0f43f618-80b0-4715-af17-90f5c673d838
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Configure the App-V Sequencer
-
-
-The topics in this section provide detailed information about the associated Application Virtualization (App-V) Sequencer configuration tasks.
-
-## In This Section
-
-
-[How to Modify the Log Directory Location](how-to-modify-the-log-directory-location.md)
-Provides a step-by-step procedure you can use to modify the location of the log directory.
-
-[How to Create the Sequencer Package Root Directory](how-to-create-the-sequencer-package-root-directory.md)
-Provides a step-by-step procedure you can use to create the package root directory.
-
-[How to Modify the Scratch Directory Location](how-to-modify-the-scratch-directory-location.md)
-Provides a step-by-step procedure you can use to modify the location of scratch directory.
-
-## Related topics
-
-
-[Application Virtualization Sequencer](application-virtualization-sequencer.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-configure-the-app-v-system-for-package-upgrade.md b/mdop/appv-v4/how-to-configure-the-app-v-system-for-package-upgrade.md
deleted file mode 100644
index 85ccb5fd59..0000000000
--- a/mdop/appv-v4/how-to-configure-the-app-v-system-for-package-upgrade.md
+++ /dev/null
@@ -1,126 +0,0 @@
----
-title: How to Configure the App-V System for Package Upgrade
-description: How to Configure the App-V System for Package Upgrade
-author: dansimp
-ms.assetid: de133898-f887-46c1-9bc9-fbb03feac66a
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Configure the App-V System for Package Upgrade
-
-
-When you deploy a new version of an existing application package that has been upgraded in the App-V Sequencer, you can deploy it so that the App-V clients automatically stream the new version to the local cache. Depending on the streaming solution you use, there are different procedures for configuring the package upgrade. The following sections describe the most typical scenarios for publishing and streaming, and include the procedures necessary for configuring the package upgrade for each scenario.
-
-## Using a Management Server for both publishing and streaming
-
-
-In this scenario, a single App-V Management Server is used for both publishing and streaming of packages and applications, and the RTSP(S) protocol is required. When the original package is imported to the App-V Management Server, the administrator copies the package folder that contains the files created by the sequencer to the CONTENT folder, for example, to \\\\server\\CONTENT\\packagename. The administrator also edits the HREF entry in the OSD file to point to the SFT file in the package folder, and then imports the package to the server.
-
-When a user is authenticated by the Management Server, the server publishes the user’s applications by sending the applist.xml file to the client. The client then retrieves the OSD files and icons for the applications from the Management Server. When the user double-clicks an application icon, the application content is streamed to the client cache from the path that is specified in the OSD file, and the application is started.
-
-### To upgrade the package
-
-To add a new version of an application that has been upgraded in the App-V Sequencer, the administrator must copy the new SFT file and any other modified files to the same folder as the original version of the application. The administrator will then use **Add Version** in the server management console to add the new version of the package.
-
-When the user next starts the application, the server streams the new version to the client automatically. This specific method of upgrading a package was formerly known as an active upgrade.
-
-## Using a Management Server for publishing and a Streaming Server for streaming
-
-
-In this scenario, the App-V Management Server is used for publishing the packages, and the Streaming Server is used for streaming packages and applications. The RTSP(S) protocol is required. When the original package is imported to the Management Server, the administrator copies the package folder that contains the files created by the sequencer to the CONTENT folder, for example, to \\\\server\\CONTENT\\packagename. The administrator edits the HREF entry in the OSD file to point to the SFT file on the Streaming Server, and then imports the package to the Management Server.
-
-To set up the Streaming Server, the administrator copies the package folder from the Management Server to the CONTENT folder on the Streaming Server. This folder must have the same name and relative path under the Streaming Server’s CONTENT folder as on the Management Server, for example, \\\\streamingserver\\CONTENT\\packagename.
-
-If the client’s Application Source Root (ASR) setting is configured to point to the Streaming Server, the client uses this setting instead of the server name in the HREF entry in the OSD file. The ISR and OSR fields on the client can optionally be configured to point to either the Management Server or the Streaming Server, depending on the specific system architecture that is used.
-
-When a user is authenticated by the Management Server, the server publishes the user’s applications by sending the applist.xml file to the client. The client retrieves the OSD files and icons for the applications from either the Streaming Server or the Management Server, depending on the settings in the OSR and ISR fields.
-
-When the user double-clicks an application icon, the client uses the path to the package content file (SFT) that is contained in the OSD file HREF element. If the ASR is used the client replaces the server name (and port and protocol, if used) in the HREF element with the path to the Streaming Server that is specified in the ASR. The application is then streamed from the Streaming Server to the client cache and is started.
-
-### To upgrade the package
-
-To add a new version of an application that has been upgraded in the App-V Sequencer, the administrator must copy the new version of the SFT file and any other modified files to the same folder as the original version of the application on the Streaming Server.
-
-For consistency, we recommend that you copy new files to the folder on the Management Server as well. In particular, if you use the client’s OSR or ISR fields, copy the updated OSD file and icons to the server that is specified in the OSR and ISR fields.
-
-After the Streaming Server detects the new version, the next time the user starts the application, the server streams the new version to the client automatically.
-
-## Using a Management Server for publishing and an IIS Server for streaming
-
-
-In this scenario, the App-V Management Server is used for publishing the packages, and the IIS server is used for streaming packages and applications. When the original package is imported to the Management Server, the administrator copies the package folder that contains the files created by the sequencer to the CONTENT folder, for example, to \\\\server\\CONTENT\\packagename. The administrator edits the HREF entry in the OSD file so it points to the SFT file on the IIS server, and then imports the package to the Management Server.
-
-To set up the IIS server for streaming, the administrator copies the package folder from the Management Server to the CONTENT folder on the IIS Server. This folder must have the same name and relative path under the IIS server’s Web Content folder as on the Management Server; for example, the URL on the IIS Server can be accessed by using http://IISserver/CONTENT/packagename or https://IISserver/CONTENT/packagename.
-
-If the client’s Application Source Root (ASR) setting is configured to point to the IIS Server, the client uses the ASR instead of the server name in the HREF entry in the OSD file. You can optionally configure the ISR and OSR fields on the client to point to either the Management Server or the IIS Server, depending on the specific system architecture that you use.
-
-When the Management Server authenticates the user, the server publishes the user’s applications by sending the applist.xml file to the client. The client retrieves the OSD files and icons for the applications from either the IIS Server or the Management Server, depending on the settings in the ISR and OSR fields.
-
-When the user double-clicks an application icon, the client uses the path to the package content file (SFT) that is contained in the OSD file HREF element. If the ASR is used the client replaces the server name (and port and protocol, if used) in the HREF element with the path to the IIS Server that is specified in the ASR. The application is then streamed from the IIS server to the client cache by using the HTTP(S) protocol and is started.
-
-### To upgrade the package
-
-The procedure to upgrade the package is as follows:
-
-- Copy the new version of the OSD file to the original version’s folder under the Management Server’s CONTENT folder, for example \\\\server\\CONTENT\\packagename, and replace the existing OSD file. For consistency, copy any other modified files, too. If the client’s OSR or ISR fields are used, then also copy the updated OSD file and icons to the server that is specified in the OSR and ISR fields.
-
-- Copy the new version of the SFT file to the package folder under the Web Content folder on the IIS server; for example, the URL on the IIS Server can be accessed by using http://IISserver/CONTENT/packagename or https://IISserver/CONTENT/packagename.
-
-At the next publishing refresh, the client is updated with the new version of the OSD file. This file now points to the new version of the SFT file; therefore, when the user next double-clicks an application icon, the new version is started.
-
-## Using a Management Server for publishing and a File Share for Streaming
-
-
-In this scenario, the App-V Management Server is used for publishing the packages, and the file server is used for streaming packages and applications. When the original package is imported to the Management Server, the administrator copies the package folder that contains the files created by the sequencer to the CONTENT folder, for example, to \\\\server\\CONTENT\\packagename. The administrator edits the HREF entry in the OSD file so that it points to the SFT file on the file server, and imports the package to the Management Server.
-
-To set up the file server for streaming, the administrator copies the package folder from the Management Server to the CONTENT folder on the file server. This folder must have the same name and relative path under the file server’s CONTENT folder as on the Management Server, for example \\\\fileserver\\CONTENT\\packagename.
-
-If the client’s Application Source Root (ASR) setting is configured to point to the file server by using a UNC path, for example \\\\fileserver\\content, the client uses this setting instead of the server name in the HREF entry in the OSD file. The administrator can optionally configure the ISR and OSR fields on the client to point to either the Management Server or the file server, depending on the specific system architecture being used.
-
-When the Management Server authenticates the user, the server publishes the user’s applications by sending the applist.xml file to the client. The client retrieves the OSD files and icons for the applications from either the file server or the Management Server, depending on the settings in the ISR and OSR fields.
-
-When the user double-clicks an application icon, the client uses the path to the package content file (SFT) that is contained in the OSD file HREF element. If the ASR is used, the client replaces the server name (and port and protocol, if used) in the HREF element with the path to the file server that is specified in the ASR. The application is then streamed from the file server to the client cache and is started.
-
-### To upgrade the package
-
-The procedure to upgrade the package is as follows:
-
-- Copy the new version of the OSD file to the original version’s folder under the Management Server’s CONTENT folder, for example \\\\server\\CONTENT\\packagename, replacing the existing OSD file. Any other modified files should be copied as well for consistency. If the client’s OSR or ISR fields are used, then also copy the updated OSD file and icons to the server that is specified in the OSR and ISR fields.
-
-- Copy the new version of the SFT file to the package folder under the CONTENT folder on the file server, for example \\\\fileserver\\CONTENT\\packagename. Copy the V2 SFT file to the folder under the CONTENT share on the file server, for example \\\\fileserver\\CONTENT\\packagename\\V1.
-
-At the next publishing refresh the client is updated with the new version of the OSD file. This file now points to new version of the SFT file, so when the user next double-clicks an application icon, the new version is started.
-
-## Upgrading the package by using MSI Streaming mode
-
-
-When you generate a Windows Installer (MSI) file during sequencing a package, the sequencer creates a .MSI file that contains all the necessary publishing information. The administrator must copy the .MSI file to the client and the .SFT file containing the package content to a network share accessible by the client computer.
-
-To publish the application to the client, run the following command on the client computer:
-
- **Msiexec.exe /i \\\\PathToMsi\\packagename.msi MODE=STREAMING OVERRIDEURL=\\\\\\\\server\\share\\package.sft**
-
-The .MSI file publishes the applications to the client and then streams the .SFT file to the client cache.
-
-### To upgrade the package
-
-To add a new version, an administrator must deploy a new .MSI file to the client and a new .SFT file to the network share. The administrator must then run the same command used to deploy the package, but use the new .MSI file and the new .SFT file, for example:
-
- **Msiexec.exe /i \\\\PathToMsi\\packagename\_2.msi MODE=STREAMING OVERRIDEURL=\\\\\\\\server\\share\\package\_2.sft**
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-configure-the-application-virtualization-client-settings-manually.md b/mdop/appv-v4/how-to-configure-the-application-virtualization-client-settings-manually.md
deleted file mode 100644
index 5dab5d7b35..0000000000
--- a/mdop/appv-v4/how-to-configure-the-application-virtualization-client-settings-manually.md
+++ /dev/null
@@ -1,43 +0,0 @@
----
-title: How to Configure the Application Virtualization Client Settings Manually
-description: How to Configure the Application Virtualization Client Settings Manually
-author: dansimp
-ms.assetid: 53bd21d8-49eb-4c77-9692-c093ffe4c17c
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Configure the Application Virtualization Client Settings Manually
-
-
-This section contains procedures that administrators can use to configure the Application Virtualization (App-V) Desktop Client and the Application Virtualization (App-V) Client for Remote Desktop Services (formerly Terminal Services) and to manage applications by using the App-V Client Management Console.
-
-## In This Section
-
-
-[How to Perform General Administrative Tasks in the App-V Client Management Console](how-to-perform-general-administrative-tasks-in-the-app-v-client-management-console.md)
-Provides procedures that you can use to set up the Publishing Server and to refresh applications.
-
-[How to Configure the Client in the Application Virtualization Client Management Console](how-to-configure-the-client-in-the-application-virtualization-client-management-console.md)
-Provides procedures that you can use to configure App-V Desktop Client and the App-V Client for Remote Desktop Services.
-
-## Related topics
-
-
-[Application Virtualization Client](application-virtualization-client.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-configure-the-application-virtualization-management-servers.md b/mdop/appv-v4/how-to-configure-the-application-virtualization-management-servers.md
deleted file mode 100644
index 8225fe37da..0000000000
--- a/mdop/appv-v4/how-to-configure-the-application-virtualization-management-servers.md
+++ /dev/null
@@ -1,60 +0,0 @@
----
-title: How to Configure the Application Virtualization Management Servers
-description: How to Configure the Application Virtualization Management Servers
-author: dansimp
-ms.assetid: a9f96148-bf2d-486f-98c2-23409bfb0935
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Configure the Application Virtualization Management Servers
-
-
-Before virtualized applications can be streamed to the Application Virtualization Desktop Client or the Client for Remote Desktop Services (formerly Terminal Services), the Application Virtualization Management Server must be configured. When you configure the server, you are setting up the *content directory* where the SFT files are loaded and stored. The SFT files contain the virtualized application (or applications).
-
-**Important**
-Application Virtualization Servers stream SFT files to the Desktop Client and the Client for Remote Desktop Services using only RTSP or RTSPS protocols. The ICO (icon) file and the OSD (open software descriptor) file can be configured to stream from a different file or HTTP server.
-
-
-
-**To configure the Application Virtualization Management Server**
-
-1. Complete the following procedure:
-
- [How to Install Application Virtualization Management Server](how-to-install-application-virtualization-management-server.md)
-
- **Note**
- During the installation procedure, you specify the location of the \\Content directory on the **Content Path** screen.
-
-
-
-2. Navigate to the location that you specified for the \\Content directory, and if necessary, create the directory.
-
-3. When the content directory is created, configure this directory as a standard file share.
-
-## Related topics
-
-
-[Application Virtualization Server-Based Scenario](application-virtualization-server-based-scenario.md)
-
-[Application Virtualization System Requirements](application-virtualization-system-requirements.md)
-
-[Electronic Software Distribution-Based Scenario](electronic-software-distribution-based-scenario.md)
-
-[How to Configure Servers for Server-Based Deployment](how-to-configure-servers-for-server-based-deployment.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-configure-the-application-virtualization-streaming-servers.md b/mdop/appv-v4/how-to-configure-the-application-virtualization-streaming-servers.md
deleted file mode 100644
index 8671c8e401..0000000000
--- a/mdop/appv-v4/how-to-configure-the-application-virtualization-streaming-servers.md
+++ /dev/null
@@ -1,57 +0,0 @@
----
-title: How to Configure the Application Virtualization Streaming Servers
-description: How to Configure the Application Virtualization Streaming Servers
-author: dansimp
-ms.assetid: 3e2dde35-9d72-40ba-9fdf-d0338bd4d561
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Configure the Application Virtualization Streaming Servers
-
-
-Before virtual applications can be streamed to the Application Virtualization Desktop Client or the Client for Remote Desktop Services (formerly Terminal Services), the Application Virtualization Streaming Servers must be configured. When you configure the servers, you are setting up the *content directory* where the SFT files are loaded and stored. The SFT files contain the virtual application (or applications).
-
-**Important**
-Application Virtualization Servers stream SFT files to the Desktop Client and the Client for Remote Desktop Services using only RTSP or RTSPS protocols. The ICO (icon) file and the OSD (open software descriptor) file can be configured to stream from a different file or HTTP server.
-
-
-
-**To configure the Application Virtualization Streaming Servers**
-
-1. Complete the installation procedure for the Application Virtualization Streaming Server. During the installation procedure, you specify the location of the \\Content directory on the **Content Path** screen.
-
-2. Navigate to the location that you specified for the \\Content directory, and if you have to, create the directory.
-
-3. When the Content directory is created, configure this directory as a standard file share.
-
-4. Configure the NTFS file system permissions to the Content directory and the package folders under the Content directory. You should use Security Groups in Active Directory Domain Services that define which users can access each application.
-
-## Related topics
-
-
-[Application Virtualization Server-Based Scenario](application-virtualization-server-based-scenario.md)
-
-[Electronic Software Distribution-Based Scenario](electronic-software-distribution-based-scenario.md)
-
-[How to Configure the Application Virtualization Management Servers](how-to-configure-the-application-virtualization-management-servers.md)
-
-[How to Configure the File Server](how-to-configure-the-file-server.md)
-
-[How to Configure the Server for IIS](how-to-configure-the-server-for-iis.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-configure-the-client-for-application-package-retrieval.md b/mdop/appv-v4/how-to-configure-the-client-for-application-package-retrieval.md
deleted file mode 100644
index 04f4c05542..0000000000
--- a/mdop/appv-v4/how-to-configure-the-client-for-application-package-retrieval.md
+++ /dev/null
@@ -1,169 +0,0 @@
----
-title: How to Configure the Client for Application Package Retrieval
-description: How to Configure the Client for Application Package Retrieval
-author: dansimp
-ms.assetid: 891f2739-da7a-46da-b452-b8c0af075525
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Configure the Client for Application Package Retrieval
-
-
-When the client is configured with an Application Virtualization (App-V) Management Server as its publishing server, by default at the next publishing refresh cycle, the client retrieves from the server the Open Software Descriptor (OSD) and package manifest files for each package that the user is authorized to use. The client uses the package source information that is defined in these files to determine where to find the package content, icons, and file type associations.
-
-If you want the client to obtain the package content (SFT file) from a local App-V Streaming Server or other alternate source such as a Web server or file server, instead of from the App-V Management Server, you can configure the ApplicationSourceRoot registry key value on the computer to point to the local content share on the other server. The OSD file still defines the original source path for the package content. However the client uses the value of the ApplicationSourceRoot setting in place of the server and share that are specified in the content path in the OSD file. This redirects the client to retrieve the content from the other server.
-
-You can also configure the OSDSourceRoot and IconSourceRoot registry key values if you want to override those settings in the package manifest file or in the paths sent by a publishing server. The OSDSourceRoot specifies a source location for OSD file retrieval for an application package during publication. The IconSourceRoot specifies a source location for icon retrieval for an application package during publication.
-
-**Note**
-- The IconSourceRoot and OSDSourceRoot settings override the values in the package manifest file, so if you try to deploy a package by using the Windows Installer (.msi) file method, it will also override the values in the package manifest file that is contained within that .msi file.
-
-- During both the publishing and HTTP(S) streaming operations,App-V 4.5 SP1 clients use the proxy server settings that are configured in Internet Explorer on the user’s computer.
-
-
-
-**To configure the ApplicationSourceRoot registry key value**
-
-- Configure the ApplicationSourceRoot in the following registry key value with either a UNC path or a URL:
-
- HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Microsoft\\SoftGrid\\4.5\\Client\\Configuration\\ApplicationSourceRoot
-
- The correct format for the Universal Naming Convention (UNC) path is **\\\\computername\\sharefolder\\\[folder\]\[\\\]**, where **folder** is optional. The **computername** can be a Fully Qualified Domain Name (FQDN) or an IP address, and **sharefolder** can be a drive letter. Only the **\\\\computername\\sharedfolder** or drive letter portion of the OSD path is replaced.
-
- The correct format for the URL path is **protocol://servername:\[port\]\[/path\]\[/\]**, where **port** and **path** are optional. If **port** is not specified, the default port for the protocol is used. Only the **protocol://server:port** portion of the OSD URL is replaced.
-
- **Important**
- Environment variables are not supported in the ApplicationSourceRoot definition.
-
-
-
-~~~
-The following table lists examples of acceptable URL and UNC path formats.
-
-
‘/’ converted to ‘\’ and parameter dropped when converting to UNC path
-
-
-
M:
-
\\uncserver\share\productivity\office2k3.sft
-
M:\productivity\office2k3.sft
-
-
-
-
M:\prodapps
-
\\uncserver\share\productivity\office2k3.sft
-
M:\prodapps\productivity\office2k3.sft
-
-
-
-
-~~~
-
-
-
-**To configure the OSDSourceRoot value**
-
-- Configure the OSDSourceRoot in the following registry key value with either a UNC path or a URL:
-
- HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Microsoft\\SoftGrid\\4.5\\Client\\Configuration\\OSDSourceRoot
-
- Acceptable formats for the OSDSourceRoot include UNC paths and URLs, as in the following example:
-
- **\\\\computername\\sharefolder\\resource** or **\\\\computername\\content** or **<drive>:\\foldername**
-
- **http://computername/productivity/** or **https://computername/productivity/**
-
-**To configure the IconSourceRoot value**
-
-- Configure the IconSourceRoot in the following registry key value with either a UNC path or a URL:
-
- HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Microsoft\\SoftGrid\\4.5\\Client\\Configuration\\IconSourceRoot
-
- Acceptable formats for the IconSourceRoot include UNC paths and URLs, as in the following example:
-
- **\\\\computername\\sharefolder\\resource** or **\\\\computername\\content** or **<drive>:\\foldername**
-
- **http://computername/productivity/** or **https://computername/productivity/**
-
-## Related topics
-
-
-[How to Configure the App-V Client Registry Settings by Using the Command Line](how-to-configure-the-app-v-client-registry-settings-by-using-the-command-line.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-configure-the-client-for-disconnected-operation-mode.md b/mdop/appv-v4/how-to-configure-the-client-for-disconnected-operation-mode.md
deleted file mode 100644
index fe5c5331d3..0000000000
--- a/mdop/appv-v4/how-to-configure-the-client-for-disconnected-operation-mode.md
+++ /dev/null
@@ -1,69 +0,0 @@
----
-title: How to Configure the Client for Disconnected Operation Mode
-description: How to Configure the Client for Disconnected Operation Mode
-author: dansimp
-ms.assetid: 3b48464a-b8b4-494b-93e3-9a6d9bd74652
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Configure the Client for Disconnected Operation Mode
-
-
-The disconnected operation mode enables the Application Virtualization (App-V) Desktop Client or the Application Virtualization (App-V) Client for Remote Desktop Services (formerly Terminal Services) to run applications that are stored in the file system cache of the client when the client cannot connect to the App-V Management Server.
-
-**Important**
-In a large organization where multiple Remote Desktop Session Host (RD°Session Host) servers (formerly Terminal Servers) are linked in a farm to support many users, using a single App-V Management Server to support the farm represents a single point of failure. To provide high availability to support the RD Session Host farm, consider linking two or more App-V Management Servers to use the same database.
-
-
-
-**To enable disconnected operation mode**
-
-- Set the following registry key value equal to 1 to enable disconnected operation mode:
-
- HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Microsoft\\SoftGrid\\4.5\\Client\\Network\\AllowDisconnectedOperation
-
-**To set a time limit on disconnected operation mode use**
-
-1. Set the following registry key value to 1:
-
- HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Microsoft\\SoftGrid\\4.5\\Client\\Network\\LimitDisconnectedOperation
-
-2. Set the following registry key value to the number of minutes you want to limit disconnected operation mode. The valid range of values is 1–999999. The default value is 90 days or 129,600 minutes.
-
- HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Microsoft\\SoftGrid\\4.5\\Client\\Network\\DOTimeoutMinutes
-
-**To configure the Client for Remote Desktop Services for disconnected operation mode**
-
-1. Set the following registry key value to 1 to enable disconnected operation mode:
-
- HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Microsoft\\SoftGrid\\4.5\\Client\\Network\\AllowDisconnectedOperation
-
-2. Set the following registry key value to 0 (zero) to allow unlimited use of disconnected operation mode:
-
- HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Microsoft\\SoftGrid\\4.5\\Client\\Network\\LimitDisconnectedOperation
-
-3. Ensure that all packages are preloaded into the cache to improve performance.
-
-## Related topics
-
-
-[Disconnected Operation Mode](disconnected-operation-mode.md)
-
-[How to Configure the App-V Client Registry Settings by Using the Command Line](how-to-configure-the-app-v-client-registry-settings-by-using-the-command-line.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-configure-the-client-for-mit-kerberos-realm-support.md b/mdop/appv-v4/how-to-configure-the-client-for-mit-kerberos-realm-support.md
deleted file mode 100644
index ee1c92f759..0000000000
--- a/mdop/appv-v4/how-to-configure-the-client-for-mit-kerberos-realm-support.md
+++ /dev/null
@@ -1,35 +0,0 @@
----
-title: How to Configure the Client for MIT Kerberos Realm Support
-description: How to Configure the Client for MIT Kerberos Realm Support
-author: dansimp
-ms.assetid: 46102f4c-270c-4115-8eb4-7ff5ae3be32d
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Configure the Client for MIT Kerberos Realm Support
-
-
-In Application Virtualization (App-V) 4.5 SP1, support was added for MIT Kerberos realms. This topic provides detailed information on how to enable that support.
-
-**To enable support for MIT Kerberos Realms**
-
-- Create a new registry key named **UseMitKerberos** of type DWORD, as follows, and then set it to a value of 1.
-
- HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Microsoft\\SoftGrid\\4.5\\Client\\Network\\UseMitKerberos
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-configure-the-client-in-the-application-virtualization-client-management-console.md b/mdop/appv-v4/how-to-configure-the-client-in-the-application-virtualization-client-management-console.md
deleted file mode 100644
index 951cbbb2d7..0000000000
--- a/mdop/appv-v4/how-to-configure-the-client-in-the-application-virtualization-client-management-console.md
+++ /dev/null
@@ -1,50 +0,0 @@
----
-title: How to Configure the Client in the Application Virtualization Client Management Console
-description: How to Configure the Client in the Application Virtualization Client Management Console
-author: dansimp
-ms.assetid: d0868c9f-8fe9-442f-a9ad-ef30efb0f6b1
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Configure the Client in the Application Virtualization Client Management Console
-
-
-You can use the Application Virtualization Client Management Console to configure the Application Virtualization Desktop Client and the Client for Remote Desktop Services (formerly Terminal Services).
-
-## In This Section
-
-
-[How to Change the Cache Size and the Drive Letter Designation](how-to-change-the-cache-size-and-the-drive-letter-designation.md)
-Provides procedures you can use to change the cache size and the drive designation letter that represents the virtual drive.
-
-[How to Change the Log Reporting Levels and Reset the Log Files](how-to-change-the-log-reporting-levels-and-reset-the-log-files.md)
-Provides procedures you can use to change the log reporting levels and to reset the log files.
-
-[How to Change User Access Permissions](how-to-change-user-access-permissions.md)
-Provides a procedure you can use to change the user access permissions.
-
-[How to Change Import Search Paths](how-to-change-import-search-paths.md)
-Provides a procedure you can use to set up client import search paths.
-
-[How to Set Up Periodic Publishing Refresh](how-to-set-up-periodic-publishing-refresh.md)
-Provides a procedure you can use to establish a schedule for Application Virtualization Server refresh.
-
-[How to Set Up Publishing Refresh on Login](how-to-set-up-publishing-refresh-on-login.md)
-Provides a procedure you can use to force Application Virtualization Server refresh on system login.
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-configure-the-client-log-file.md b/mdop/appv-v4/how-to-configure-the-client-log-file.md
deleted file mode 100644
index e4a46cd129..0000000000
--- a/mdop/appv-v4/how-to-configure-the-client-log-file.md
+++ /dev/null
@@ -1,110 +0,0 @@
----
-title: How to Configure the Client Log File
-description: How to Configure the Client Log File
-author: dansimp
-ms.assetid: dd79f8ce-61e2-4dc8-af03-2a353554a1b2
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Configure the Client Log File
-
-
-You can use the following procedures to configure the Application Virtualization (App-V) Client log file.
-
-**To change the log file location**
-
-- Edit the following registry key value to specify the new path for the log file. You must restart the **sftlist** service after changing this value. This location can also be changed interactively after installation.
-
- HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Microsoft\\SoftGrid\\4.5\\Client\\Configuration\\LogFileName
-
-**To change the log reporting level**
-
-- By default, the type of messages that are written to the log include all events of severity level 4 (Informational) or higher. The severity level is stored in the following key value. Set this key value to 5 to enable verbose logging. Use verbose logging only for short periods during troubleshooting because it will generate a very large volume of messages and cause the log to fill up quickly.
-
- HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Microsoft\\SoftGrid\\4.5\\Client\\Configuration\\LogMinSeverity
-
-**To change the log size**
-
-- In Application Virtualization (App-V) 4.5, the log size is controlled by the following registry key value. This value defaults to 256 MB and defines the maximum size, in MB, that the log can grow to before being reset.
-
- HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Microsoft\\SoftGrid\\4.5\\Client\\Configuration\\LogMaxSize
-
- **Caution**
- This registry key value must be set to a value greater than zero to ensure the log file does get reset.
-
-
-
-**To change the number of backup copies**
-
-- When the log file reaches the maximum size, a reset is forced when the next write to the log occurs. A reset causes a new log file to be created, and the old file is renamed as a backup. The following registry setting controls the number of backup copies of the log file that are kept when the file is reset. The default value is 4.
-
- HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Microsoft\\SoftGrid\\4.5\\Client\\Configuration\\LogRolloverCount
-
- The format of the backup log file names is: **sftlog\_YYYYMMDD\_hhmmss-uuu.txt** and is based on the reset time, in Universal Coordinated Time (UTC). The following table lists the symbols used in creating the file names and their descriptions.
-
-
-
-
-
-
-
-
-
Symbol
-
Description
-
-
-
-
-
YYYY
-
4-digit year
-
-
-
MM
-
2-digit month (01–12)
-
-
-
DD
-
2-digit day of the month (01–31)
-
-
-
hh
-
hour (00–23)
-
-
-
mm
-
minutes (00–59)
-
-
-
ss
-
seconds (00–59)
-
-
-
uuu
-
milliseconds (000–999)
-
-
-
-
-
-
-## Related topics
-
-
-[How to Configure the App-V Client Registry Settings by Using the Command Line](how-to-configure-the-app-v-client-registry-settings-by-using-the-command-line.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-configure-the-file-server.md b/mdop/appv-v4/how-to-configure-the-file-server.md
deleted file mode 100644
index c9d01b4dba..0000000000
--- a/mdop/appv-v4/how-to-configure-the-file-server.md
+++ /dev/null
@@ -1,69 +0,0 @@
----
-title: How to Configure the File Server
-description: How to Configure the File Server
-author: dansimp
-ms.assetid: 0977554c-1741-411b-85e7-7e1cd017542f
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Configure the File Server
-
-
-You can use the following procedure to configure a local computer that is used as a file share and streams applications to the Application Virtualization Desktop Client and the Client for Remote Desktop Services (formerly Terminal Services). This scenario is used when you do not want to add an additional server infrastructure to your existing hardware environment.
-
-If you are using an Application Virtualization Management Server as a distribution point to the file share installed in local offices, you must configure this server before virtual applications can be streamed to the computers that are used as file shares. When you configure the servers and the file shares, you are setting up the content directory where the SFT files are loaded and stored. The SFT files contain the virtual application (or applications).
-
-**Important**
-For applications to stream properly to the Application Virtualization Desktop Client and the Client for Remote Desktop Services, the SFT file streams from the content directory on the server where you store the virtual application; the ICO (icon) file and the OSD (open software descriptor) file can be configured to stream from a different server.
-
-
-
-**To configure the Application Virtualization file server**
-
-1. Complete the following installation procedure to configure the server that is used as the distribution point:
-
- [How to Install Application Virtualization Management Server](how-to-install-application-virtualization-management-server.md)
-
- **Note**
- During the installation procedure, you specify the location of the \\Content directory on the **Content Path** screen.
-
-
-
-2. Create a \\Content directory, which corresponds to the directory you specified when you installed the server, on each computer that you are using as a file share.
-
- **Important**
- Configure the Application Virtualization Desktop Clients to stream applications from the computer you are using as a file share rather than from an Application Virtualization Server or IIS server.
-
-
-
-3. When the \\Content directory is created, configure this directory as a standard file share.
-
-## Related topics
-
-
-[Application Virtualization Server-Based Scenario](application-virtualization-server-based-scenario.md)
-
-[Electronic Software Distribution-Based Scenario](electronic-software-distribution-based-scenario.md)
-
-[How to Configure the Application Virtualization Management Servers](how-to-configure-the-application-virtualization-management-servers.md)
-
-[How to Configure the Application Virtualization Streaming Servers](how-to-configure-the-application-virtualization-streaming-servers.md)
-
-[How to Configure the Server for IIS](how-to-configure-the-server-for-iis.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-configure-the-server-for-iis.md b/mdop/appv-v4/how-to-configure-the-server-for-iis.md
deleted file mode 100644
index 4290cc9bf5..0000000000
--- a/mdop/appv-v4/how-to-configure-the-server-for-iis.md
+++ /dev/null
@@ -1,59 +0,0 @@
----
-title: How to Configure the Server for IIS
-description: How to Configure the Server for IIS
-author: dansimp
-ms.assetid: 1fcfc583-322f-4a38-90d0-e64bfa9ee3d8
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Configure the Server for IIS
-
-
-Before virtual applications can be streamed to the Application Virtualization Desktop Client and the Client for Remote Desktop Services (formerly Terminal Services), the IIS servers must be configured. When you configure the servers, you are setting up the content directory where the SFT files are loaded and stored. The SFT files contain the virtual application (or applications).
-
-**To configure the content directory on the IIS server**
-
-1. On the server that is running IIS, locate the directory that you want to use as the content directory, or create the directory if it does not exist. Configure this directory as a standard file share.
-
-2. On the server that is running IIS, open **IIS Manager**, and under the default website, create a virtual directory that corresponds to the content directory that you created on the server. Make sure that **Read** is checked.
-
-3. Give the newly created virtual directory the alias **Content**.
-
-4. Accept all other default settings for this virtual directory.
-
-5. Configure the NTFS file system permissions to the content directory and the package folders under the content directory by using the Security Groups in Active Directory Domain Services that you defined earlier.
-
-**Note**
-If you are using IIS to publish the ICO and OSD files, you must configure a MIME type for OSD=TXT; otherwise, IIS will not serve the ICO and OSD files to clients. If you are using IIS to publish packages (SFT files), you must configure a MIME type for SFT=Binary; otherwise, IIS will not serve the SFT files to clients.
-
-
-
-## Related topics
-
-
-[Application Virtualization Server-Based Scenario](application-virtualization-server-based-scenario.md)
-
-[Electronic Software Distribution-Based Scenario](electronic-software-distribution-based-scenario.md)
-
-[How to Configure the Application Virtualization Management Servers](how-to-configure-the-application-virtualization-management-servers.md)
-
-[How to Configure the Application Virtualization Streaming Servers](how-to-configure-the-application-virtualization-streaming-servers.md)
-
-[How to Configure the File Server](how-to-configure-the-file-server.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-configure-the-server-to-be-trusted-for-delegation.md b/mdop/appv-v4/how-to-configure-the-server-to-be-trusted-for-delegation.md
deleted file mode 100644
index fec2c858fe..0000000000
--- a/mdop/appv-v4/how-to-configure-the-server-to-be-trusted-for-delegation.md
+++ /dev/null
@@ -1,136 +0,0 @@
----
-title: How to Configure the Server to be Trusted for Delegation
-description: How to Configure the Server to be Trusted for Delegation
-author: dansimp
-ms.assetid: d8d11588-17c0-4bcb-a7e6-86b5e4ba7e1c
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Configure the Server to be Trusted for Delegation
-
-
-When you install the Microsoft Application Virtualization (App-V) Management Server software, you can choose to install it by using a distributed system architecture. If you install the console, the Management Web Service, and the database on different computers, you must configure the Internet Information Services (IIS) server to be trusted for delegation. This is necessary because the Management Web Service will attempt to connect to the App-V data store by using the credentials of the App-V administrator who is using the console. The database server on which the data store is installed will not accept the administrator’s credentials from the IIS server unless the IIS server is configured to be trusted for delegation, and so the Management Web Service will not be able to connect to the App-V data store.
-
-**Note**
-If you install the App-V Management Server software on a single server and place the data store on a separate server, there is one situation in which you must still configure the server to be trusted for delegation even though the Management Web Service and Management Console are on the same server. This situation occurs if you need to connect to the Management Web Service in the console by using the **Use Alternate Credentials** option.
-
-
-
-The type of delegation that you can use depends on the Domain Functional Level that you have configured in your Active Directory Domain Services (AD DS) infrastructure. The following table lists the types of delegation that can be configured for each Domain Functional Level for App-V. Detailed instructions follow the table.
-
-
-
-
-
-
-
-
-
Domain Functional Level
-
Delegation Levels Available
-
-
-
-
-
Windows 2000 native
-
-
No delegation (default)
-
Unconstrained delegation
-
-
-
-
Windows Server 2003, Windows Server 2008, or Windows Server 2008 R2
-
-
No delegation (default)
-
Unconstrained delegation¹
-
Constrained delegation (Use Kerberos Only Protocols)
-
Constrained delegation (Use any authentication protocol) ¹
-
-
-
-
-
-
-
-¹ Not recommended.
-
-## To configure unconstrained delegation when the Domain Functional Level is Windows 2000 native
-
-
-On the domain controller for your Web server’s domain, complete the following steps.
-
-****
-
-1. Click **Start**, **Administrative Tools**, and then click **Active Directory Users and Computers**.
-
-2. Expand domain, and then expand the Computers folder.
-
-3. In the right pane, right-click the computer name for the Web server, and then click **Properties**.
-
-4. On the **General** tab, ensure that the **Trust computer for delegation** check box is selected.
-
-5. Click **OK**.
-
-## To configure unconstrained delegation when the Domain Functional Level is Windows Server 2003, Windows Server 2008, or Windows Server 2008 R2
-
-
-On the domain controller for your Web server’s domain, complete the following steps.
-
-****
-
-1. Click **Start**, click **Administrative Tools**, and then click **Active Directory Users and Computers**.
-
-2. Expand domain, and expand the Computers folder.
-
-3. In the right pane, right-click the computer name for the Web server, select **Properties**, and then click the **Delegation** tab.
-
-4. Click to select **Trust this computer for delegation to any service (Kerberos only)**.
-
-5. Click **OK**.
-
-## To configure constrained delegation when the Domain Functional Level is Windows Server 2003, Windows Server 2008, or Windows Server 2008 R2
-
-
-On the domain controller for your Web server’s domain, complete the following steps.
-
-****
-
-1. Click **Start**, click **Administrative Tools**, and then click **Active Directory Users and Computers**.
-
-2. Expand domain, and then expand the Computers folder.
-
-3. In the right pane, right-click the computer name for the Web server, select **Properties**, and then click the **Delegation** tab.
-
-4. Click to select **Trust this computer for delegation to specified services only**.
-
-5. Ensure that **Use Kerberos only** is selected, and then click **OK**.
-
-6. Click the **Add** button. In the **Add Services** dialog box, click **Users or Computers**, and then browse to or type the name of the Microsoft SQL server that has the App-V data store and is to receive the users credentials from IIS. Click **OK**.
-
-7. In the **Available Services** list, select the MSSQLSvc service that lists port number on which the Microsoft SQL Server is accepting connections for the App-V database (the default port is 1433). Click **OK**.
-
-### Additional steps to configure IIS 7 for constrained delegation
-
-If you are running the Management Web Service on an IIS 7 server, you must complete the following steps to set the IIS 7 *useAppPoolCredentials* variable to True.
-
-1. Open an elevated Command Prompt window. To open an elevated Command Prompt window, click **Start**, click **All Programs**, click **Accessories**, right-click **Command Prompt**, and then click **Run as administrator**.
-
-2. Navigate to %windir%\\system32\\inetsrv.
-
-3. Type **appcmd.exe set config -section:system.webServer/security/authentication/windowsAuthentication -useAppPoolCredentials:true**, and then press ENTER.
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-configure-user-permissions.md b/mdop/appv-v4/how-to-configure-user-permissions.md
deleted file mode 100644
index 88e1049577..0000000000
--- a/mdop/appv-v4/how-to-configure-user-permissions.md
+++ /dev/null
@@ -1,46 +0,0 @@
----
-title: How to Configure User Permissions
-description: How to Configure User Permissions
-author: dansimp
-ms.assetid: 54e69f46-b028-4ad1-9b80-f06ef5c8f559
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 08/30/2016
----
-
-
-# How to Configure User Permissions
-
-
-You can enable and disable some actions for users who do not have administrative rights by editing the key values under the **Permissions** registry key (HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Microsoft\\SoftGrid\\4.5\\Client\\Permissions). This key is primarily designed to help prevent users from making mistakes rather than to provide any special security, because users with administrative rights can edit any of these key values. The following procedures are examples of how to change the key values. For more information about the Application Virtualization (App-V) Client registry keys and values, see .
-
-**To change user permissions**
-
-1. To enable the users to choose to run the client in offline mode, set the following key value to 1:
-
- HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Microsoft\\SoftGrid\\4.5\\Client\\Permissions\\ToggleOfflineMode
-
-2. To enable the users to view all applications through the user interface, set the following key value to 1. Setting the value to 0 (zero) allows the users to see only the applications that are available to them.
-
- HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Microsoft\\SoftGrid\\4.5\\Client\\Permissions\\ViewAllApplications
-
-## Related topics
-
-
-[How to Configure the App-V Client Registry Settings by Using the Command Line](how-to-configure-the-app-v-client-registry-settings-by-using-the-command-line.md)
-
-[User Access Permissions in Application Virtualization Client](user-access-permissions-in-application-virtualization-client.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-configure-windows-server-2003-firewall-for-app-v.md b/mdop/appv-v4/how-to-configure-windows-server-2003-firewall-for-app-v.md
deleted file mode 100644
index 3ec2889648..0000000000
--- a/mdop/appv-v4/how-to-configure-windows-server-2003-firewall-for-app-v.md
+++ /dev/null
@@ -1,61 +0,0 @@
----
-title: How to Configure Windows Server 2003 Firewall for App-V
-description: How to Configure Windows Server 2003 Firewall for App-V
-author: dansimp
-ms.assetid: 2c0e80f8-41e9-4164-ac83-b23b132b489a
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Configure Windows Server 2003 Firewall for App-V
-
-
-Use the following procedure to configure the Windows Server 2003 firewall for App-V.
-
-**To configure Windows Server 2003 firewall for App-V**
-
-1. In **Control Panel**, open the **Windows Firewall**.
-
- **Note**
- If the server has not been configured to run the firewall service before this step, you will be prompted to start the firewall service.
-
-
-
-2. If ICO and OSD files are published through SMB, ensure that **File and Printer Sharing** is enabled on the **Exceptions** tab.
-
- **Note**
- If ICO and OSD files are published through HTTP/HTTPS on the Management Server, you might need to add an exception for HTTP or HTTPS. If the IIS server hosting the ICO and OSD files is hosted on a computer separate from the Management Server, you need to add the exception to that computer. To maximize performance, it is recommended that you host the ICO and OSD files on a separate server from the Management Server.
-
-
-
-3. Add a program exception for `sghwdsptr.exe`, which is the Management Server service executable. The default path to this executable is `%ProgramFiles%\Microsoft System Center App Virt Management Server\App Virt Management Server\bin`.
-
- **Note**
- If the Management Server uses RTSP for communication, you must also add a program exception for `sghwsvr.exe`.
-
- The App-V Streaming Server requires a program exception `sglwdsptr.exe` for RTSPS communication. The App-V Streaming Server that uses RTSP for communication also requires a program exception for `sglwsvr.exe`.
-
-
-
-4. Ensure that the proper scope is configured for each exception. To reduce risk, remove any computer and strictly limit the IP addresses to which the server will respond.
-
-## Related topics
-
-
-[How to Configure Windows Server 2008 Firewall for App-V](how-to-configure-windows-server-2008-firewall-for-app-v.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-configure-windows-server-2008-firewall-for-app-v.md b/mdop/appv-v4/how-to-configure-windows-server-2008-firewall-for-app-v.md
deleted file mode 100644
index 7e516a89fd..0000000000
--- a/mdop/appv-v4/how-to-configure-windows-server-2008-firewall-for-app-v.md
+++ /dev/null
@@ -1,59 +0,0 @@
----
-title: How to Configure Windows Server 2008 Firewall for App-V
-description: How to Configure Windows Server 2008 Firewall for App-V
-author: dansimp
-ms.assetid: 57f4ed17-0651-4a3c-be1e-29d9520c6aeb
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 08/30/2016
----
-
-
-# How to Configure Windows Server 2008 Firewall for App-V
-
-
-With the introduction of Windows Server 2008, the firewall and IPsec components were merged into one service, and the capabilities of this service were enhanced. The new firewall service supports incoming and outgoing stateful inspection. Also, you can configure specific firewall rules and IPsec policies through group policies. For additional information about the Windows firewall in Windows Server 2008, see .
-
-The following procedure does not include adding an exception for ICO and OSD publishing through SMB or HTTP/HTTPS. Those exceptions are automatically added based on the network profile and roles installed on the Windows Server 2008 firewall.
-
-**Note**
-If the Management Server is configured to use RTSP, repeat this procedure to add the `sghwsvr.exe` program as an exception.
-
-The App-V Streaming Server requires the program exception `sglwdsptr.exe` for RTSPS communication. An App-V Streaming Server that uses RTSP for communication also requires a program exception for `sglwsvr.exe`.
-
-
-
-**To configure Windows Server 2008 firewall for App-V**
-
-1. Open the **Windows Firewall with Advanced Security** management console through the Control Panel or by typing `wf.msc` on the Run line.
-
-2. Create a new inbound rule, and select **Program**.
-
-3. Select the program path, and browse to `sghwdsptr.exe`, which is located by default at `%ProgramFiles%\Microsoft System Center App Virt Management Server\App Virt Management Server\bin`.
-
-4. Click **Next**.
-
-5. On the **Action** page, select **Allow the connection**, and then click **Next**.
-
-6. Select the appropriate **Profiles** to apply to the inbound rule.
-
-7. Provide a name and description for the rule, and click **Finish**.
-
-## Related topics
-
-
-[How to Configure Windows Server 2003 Firewall for App-V](how-to-configure-windows-server-2003-firewall-for-app-v.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-configure-windows-server-2008-for-app-v-management-servers.md b/mdop/appv-v4/how-to-configure-windows-server-2008-for-app-v-management-servers.md
deleted file mode 100644
index 8368dd56f8..0000000000
--- a/mdop/appv-v4/how-to-configure-windows-server-2008-for-app-v-management-servers.md
+++ /dev/null
@@ -1,56 +0,0 @@
----
-title: How to Configure Windows Server 2008 for App-V Management Servers
-description: How to Configure Windows Server 2008 for App-V Management Servers
-author: dansimp
-ms.assetid: 38b4016f-de82-4209-9159-387d20ddee25
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Configure Windows Server 2008 for App-V Management Servers
-
-
-The Windows Server 2008 server on which you install the Microsoft Application Virtualization (App-V) Management Web Service requires Internet Information Services (IIS) to be installed as a role on the server. Use the following procedure to configure Windows Server 2008 to support App-V server installation.
-
-**To install IIS on a Windows Server 2008 computer**
-
-1. On the Windows Server 2008 computer, click **Start**, click **All Programs**, click **Administrative Tools**, and then click **Server Manager** to start Server Manager. In Server Manager, right-click the **Roles** node, and click **Add Roles** to start the **Add Roles Wizard**.
-
-2. In the **Add Roles Wizard**, on the **Select Server Roles** page, select **Web Server (IIS)**. When prompted, click **Add Required Features** to add the dependent features.
-
-3. On the **Select Server Roles** page, Click **Next**, and then click **Next** again.
-
-4. In the **Add Roles Wizard**, on the **Select Role Services** page:
-
- 1. Under **Application Development**, select **ASP.NET** and, when prompted, click **Add Required Role Services** to add the dependent roles services and features.
-
- 2. Under **Security**, select **Windows Authentication**.
-
- 3. In the **Management Tools** node, select **IIS Management Scripts and Tools**. Under **IIS 6 Management Compatibility**, ensure that both **IIS 6 Metabase Compatibility** and **IIS 6 WMI Compatibility** are selected, and then click **Next**.
-
-5. On the **Confirm Installation Selections** page, click **Install**, and then complete the rest of the wizard.
-
-6. Click **Close** to exit the **Add Roles Wizard**, and then close Server Manager.
-
-## Related topics
-
-
-[Application Virtualization Deployment Requirements](application-virtualization-deployment-requirements.md)
-
-[Application Virtualization Deployment and Upgrade Checklists](application-virtualization-deployment-and-upgrade-checklists.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-connect-to-an-application-virtualization-system.md b/mdop/appv-v4/how-to-connect-to-an-application-virtualization-system.md
deleted file mode 100644
index 169761167e..0000000000
--- a/mdop/appv-v4/how-to-connect-to-an-application-virtualization-system.md
+++ /dev/null
@@ -1,71 +0,0 @@
----
-title: How to Connect to an Application Virtualization System
-description: How to Connect to an Application Virtualization System
-author: dansimp
-ms.assetid: ac38216c-5464-4c0b-a4d3-3949ba6358ac
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 08/30/2016
----
-
-
-# How to Connect to an Application Virtualization System
-
-
-You must connect the Application Virtualization Server Management Console to an Application Virtualization System before you can use the management console to manage applications, file type associations, packages, application licenses, server groups, provider policies and administrators. The following procedure outlines the steps you must follow to connect the console to an Application Virtualization System.
-
-**To connect to an Application Virtualization System**
-
-1. Right-click the Application Virtualization System node in the **Scope** pane, and select **Connect to Application Virtualization System** from the pop-up menu.
-
- **Note**
- There are three components to Application Virtualization server management: the Application Virtualization Management Console, the Management Web Service, and the SQL Datastore. If these components are distributed across different physical machines, you must configure security properly for the components to communicate across the system. For more information, see the following manuals and articles:
-
- [How to Configure the Server to be Trusted for Delegation](https://go.microsoft.com/fwlink/?LinkID=166682) (https://go.microsoft.com/fwlink/?LinkID=166682)
-
- [Planning and Deployment Guide for the Application Virtualization System](https://go.microsoft.com/fwlink/?LinkID=122063) (https://go.microsoft.com/fwlink/?LinkID=122063)
-
- [Operations Guide for the Application Virtualization System](https://go.microsoft.com/fwlink/?LinkID=133129) (https://go.microsoft.com/fwlink/?LinkID=133129)
-
- [Article 930472](https://go.microsoft.com/fwlink/?LinkId=114647) in the Microsoft Knowledge Base (https://go.microsoft.com/fwlink/?LinkId=114647)
-
- [Article 930565](https://go.microsoft.com/fwlink/?LinkId=114648) in the Microsoft Knowledge Base (https://go.microsoft.com/fwlink/?LinkId=114648)
-
-
-
-2. Complete the fields in the **Connect to Application Virtualization System** dialog box:
-
- 1. **Web Service Host Name**—Enter the name of the Application Virtualization System to which you want to connect, or enter **localhost** to connect to the local server.
-
- 2. **Use Secure Connection**—Select this check box if you want to connect to the server with a secure connection.
-
- 3. **Port**—Enter the port number you want to use for the connection. **80** is the default regular port number, and **443** is the secure-port number.
-
- 4. **Use Current Windows Account**—Select this radio button to use the current Windows account credentials.
-
- 5. **Specify Windows Account**—Select this radio button when you want to connect to the server as a different user.
-
- 6. **Name**—Enter the name of the new user by using either the *DOMAIN\\username* or the username@domain format.
-
- 7. **Password**—Enter the password that corresponds to the new user.
-
-3. Click **OK**.
-
-## Related topics
-
-
-[How to Perform Administrative Tasks in the Application Virtualization Server Management Console](how-to-perform-administrative-tasks-in-the-application-virtualization-server-management-console.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-create-a-reportserver.md b/mdop/appv-v4/how-to-create-a-reportserver.md
deleted file mode 100644
index abdfd7298e..0000000000
--- a/mdop/appv-v4/how-to-create-a-reportserver.md
+++ /dev/null
@@ -1,61 +0,0 @@
----
-title: How to Create a Report
-description: How to Create a Report
-author: dansimp
-ms.assetid: 70938167-d3b9-45ce-b459-a953c93769b0
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Create a Report
-
-
-The process for creating a report from the Application Virtualization Server Management Console is the same regardless of the report type. When you select a report type, the window displays a brief description of the selected report.
-
-**Note**
- When you create a report, you specify the parameters that are used for collecting the data when the report is run. Until you run a report, no data is collected.
-
-
-
-**To create a report**
-
-1. Run the New Report Wizard by right-clicking the **Reports** node and selecting **New Report** from the pop-up menu.
-
-2. On the first page of the New Report Wizard, enter a name in the **Report Name** field and select the **Report Type** from the drop-down list of reports. Depending on which report you select, the remaining pages in the wizard change according the requirements of that report type. Scan the following list of pages to find the pages that refer to your report:
-
- 1. **Report Period**—Select a radio button to specify the frequency for running the report.
-
- 2. **Server**—Select the **Server**, **Server Group**, or **Enterprise** radio button, and then select the server group and server from the corresponding drop-down list and field as enabled.
-
- 3. **Application**—Select an application from the drop-down list of available applications.
-
-3. Click **Finish**.
-
-## Related topics
-
-
-[Application Virtualization Report Types](application-virtualization-report-types.md)
-
-[How to Delete a Report](how-to-delete-a-reportserver.md)
-
-[How to Export a Report](how-to-export-a-reportserver.md)
-
-[How to Print a Report](how-to-print-a-reportserver.md)
-
-[How to Run a Report](how-to-run-a-reportserver.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-create-a-server-group.md b/mdop/appv-v4/how-to-create-a-server-group.md
deleted file mode 100644
index bc12c0bd0a..0000000000
--- a/mdop/appv-v4/how-to-create-a-server-group.md
+++ /dev/null
@@ -1,48 +0,0 @@
----
-title: How to Create a Server Group
-description: How to Create a Server Group
-author: dansimp
-ms.assetid: 29ada98b-1024-483d-a3ee-67d4bb263df7
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Create a Server Group
-
-
-To help you manage your Application Virtualization Management Servers more efficiently, you can use the Application Virtualization Server Management Console to organize them into server groups.
-
-**To create a server group**
-
-1. Click the **Server Groups** node in the left pane, and choose **New Server Group**.
-
-2. In the **New Server Group Wizard**, enter a name in the **Server Group Name** field, and select the default provider policy from the drop-down list of provider policies.
-
-3. Be sure the **Enabled** check box is selected to enable the server group.
-
-4. Click **Finish**.
-
-## Related topics
-
-
-[How to Add a Server](how-to-add-a-server.md)
-
-[How to Remove a Server Group](how-to-remove-a-server-group.md)
-
-[How to Remove a Server](how-to-remove-a-server.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-create-a-virtual-environment-for-a-web-based-application.md b/mdop/appv-v4/how-to-create-a-virtual-environment-for-a-web-based-application.md
deleted file mode 100644
index 23e2b3570b..0000000000
--- a/mdop/appv-v4/how-to-create-a-virtual-environment-for-a-web-based-application.md
+++ /dev/null
@@ -1,48 +0,0 @@
----
-title: How to Create a Virtual Environment for a Web-Based Application
-description: How to Create a Virtual Environment for a Web-Based Application
-author: dansimp
-ms.assetid: d2b16e9d-369c-4bd6-b2a0-16dd24c0e32c
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Create a Virtual Environment for a Web-Based Application
-
-
-You can create separate virtual environments for web applications you want to isolate. Creating separate web environments is useful if the web-based applications require plug-ins of have configurations that conflict with each other.
-
-**To create a virtual environment for a Web-based application**
-
-1. Open the sequencing wizard. For more information about sequencing an application see [How to Sequence a New Application](how-to-sequence-a-new-application.md).
-
-2. On the **Monitor Installation** page, to start monitoring the installation of the application, click **Begin Monitoring**. Open a web browser and navigate to the installer file associated with the application. Install the application, and perform any required post installation configuration tasks.
-
-3. To ensure the applications starts, open the application three times.
-
-4. Install and configure any additional applications that need to reside in the same virtual environment.
-
-5. Complete the remainder of the Sequencing Wizard.
-
-6. To save the application, select **File**, and click **Save**.
-
-## Related topics
-
-
-[Tasks for the Application Virtualization Sequencer](tasks-for-the-application-virtualization-sequencer.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-create-an-app-v-project-template--app-v-46-sp1-.md b/mdop/appv-v4/how-to-create-an-app-v-project-template--app-v-46-sp1-.md
deleted file mode 100644
index 26aae4b1ea..0000000000
--- a/mdop/appv-v4/how-to-create-an-app-v-project-template--app-v-46-sp1-.md
+++ /dev/null
@@ -1,65 +0,0 @@
----
-title: How to Create an App-V Project Template (App-V 4.6 SP1)
-description: How to Create an App-V Project Template (App-V 4.6 SP1)
-author: dansimp
-ms.assetid: 7e87fba2-b72a-4bc9-92b8-220e25aae99a
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Create an App-V Project Template (App-V 4.6 SP1)
-
-
-You can use an App-V project template to save commonly applied settings associated with an existing virtual application package. These settings can then be applied when you create new virtual application packages in your environment which can help streamline the process of creating virtual application packages.
-
-**Note**
-You can only apply an App-V project template when you are creating a new virtual application package. Applying project templates to existing virtual application packages is not supported.
-
-
-
-For more information about applying an App-V project template, see [How to Apply an App-V Project Template (App-V 4.6 SP1)](how-to-apply-an-app-v-project-template--app-v-46-sp1-.md).
-
-App-V project templates differ from App-V Application Accelerators because App-V Application Accelerators are application-specific, and App-V project templates can be applied to multiple applications. Additionally, you cannot use a project template when you use a Package Accelerator to create a virtual application package.
-
-The following general settings are saved with an App-V project template:
-
-- **Advanced Monitoring Options**. Enables Microsoft Update to run during monitoring, Rebase **.dll’s**.
-
-- **Package Deployment Settings**. Contains **Protocol**, **Host Name**, **Port**, **Path**, **Operating Systems**, **Enforce Security Descriptors**, **Create MSI**, **Compress Package**.
-
-- **General Options**. Allows you to **Generate Microsoft Windows Installer (MSI)** package, **Allow Virtualization of Events**, **Allow Virtualization of Services**, **Append Package Version to Filename**.
-
-- **Exclusion Items**. Contains the Exclusion pattern list.
-
-**To create a project template**
-
-1. To start the App-V Sequencer, on the computer that is running the App-V Sequencer, click **Start** / **All Programs** / **Microsoft Application Virtualization** / **Microsoft Application Virtualization Sequencer**.
-
-2. If the virtual application package is currently open in the App-V Sequencer, skip to step 3 of this procedure. To open the existing virtual application package that contains the settings you want to save with the App-V project template, click **File** / **Open** and click **Edit** **Package**. On the **Select Package** page, click **Browse** and locate the virtual application package that you want to open. Click **Edit**.
-
-3. In the App-V Sequencer console, click **File** / **Save As Template**. After you have reviewed the settings that will be saved with the new template, click **OK**. Specify a name that will be associated with the new App-V project template. Click **Save**.
-
- The new App-V project template is saved in the directory specified in step 3 of this procedure.
-
-## Related topics
-
-
-[Tasks for the Application Virtualization Sequencer (App-V 4.6 SP1)](tasks-for-the-application-virtualization-sequencer--app-v-46-sp1-.md)
-
-[How to Apply an App-V Project Template (App-V 4.6 SP1)](how-to-apply-an-app-v-project-template--app-v-46-sp1-.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-create-an-application-group.md b/mdop/appv-v4/how-to-create-an-application-group.md
deleted file mode 100644
index ac2fba82be..0000000000
--- a/mdop/appv-v4/how-to-create-an-application-group.md
+++ /dev/null
@@ -1,56 +0,0 @@
----
-title: How to Create an Application Group
-description: How to Create an Application Group
-author: dansimp
-ms.assetid: 32751511-3d1e-40e5-b21f-d88ea39c76a3
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Create an Application Group
-
-
-In the Application Virtualization Server Management Console, you can use the following procedure to create application groups to organize your applications.
-
-**To create an application group**
-
-1. In the Application Virtualization Server Management Console, click the **Applications** node in the left pane or expand it and highlight an existing application group.
-
-2. Right-click the **Applications** node or the existing application group where you want to put the new group, and choose **New Application Group**.
-
-3. In the **New Application Group Wizard**, type the name for the group and click **OK**.
-
- Now you can populate the new group by importing applications. You can also move applications between groups. For more information about moving applications, see [How to Move an Application](how-to-move-an-application.md).
-
-## Related topics
-
-
-[How to Grant Access to an Application](how-to-grant-access-to-an-application.md)
-
-[How to Import an Application](how-to-import-an-applicationserver.md)
-
-[How to Manually Add an Application](how-to-manually-add-an-application.md)
-
-[How to Move an Application](how-to-move-an-application.md)
-
-[How to Move an Application Group](how-to-move-an-application-group.md)
-
-[How to Remove an Application Group](how-to-remove-an-application-group.md)
-
-[How to Rename an Application Group](how-to-rename-an-application-group.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-create-an-application-license-group.md b/mdop/appv-v4/how-to-create-an-application-license-group.md
deleted file mode 100644
index 76da2668b9..0000000000
--- a/mdop/appv-v4/how-to-create-an-application-license-group.md
+++ /dev/null
@@ -1,58 +0,0 @@
----
-title: How to Create an Application License Group
-description: How to Create an Application License Group
-author: dansimp
-ms.assetid: b385324a-8a11-41ee-86e8-8f809235454c
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Create an Application License Group
-
-
-The Application Virtualization Server Management Console enables you to organize and manage application licenses. Depending on the type of license group, you can control who has access to the application and how many users can access an application at a time. You can use the following procedure to create an application license group.
-
-**To create an application license group**
-
-1. In the left pane of the Application Virtualization Server Management Console, right-click the **Application Licenses** node.
-
-2. Select one of the following menu items that corresponds to the type of license group you want to create, and complete the pages in the associated **New License Wizard**:
-
- 1. **New Unlimited License**
-
- 2. **New Concurrent License**
-
- 3. **New Named License**
-
-3. Click **Finish**.
-
-## Related topics
-
-
-[How to Associate an Application with a License Group](how-to-associate-an-application-with-a-license-group.md)
-
-[How to Remove an Application from a License Group](how-to-remove-an-application-from-a-license-group.md)
-
-[How to Remove an Application License Group](how-to-remove-an-application-license-group.md)
-
-[How to Set Up a Concurrent License Group](how-to-set-up-a-concurrent-license-group.md)
-
-[How to Set Up a Named License Group](how-to-set-up-a-named-license-group.md)
-
-[How to Set Up an Unlimited License Group](how-to-set-up-an-unlimited-license-group.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-create-app-v-package-accelerators--app-v-46-sp1-.md b/mdop/appv-v4/how-to-create-app-v-package-accelerators--app-v-46-sp1-.md
deleted file mode 100644
index bf6769fb47..0000000000
--- a/mdop/appv-v4/how-to-create-app-v-package-accelerators--app-v-46-sp1-.md
+++ /dev/null
@@ -1,103 +0,0 @@
----
-title: How to Create App-V Package Accelerators (App-V 4.6 SP1)
-description: How to Create App-V Package Accelerators (App-V 4.6 SP1)
-author: dansimp
-ms.assetid: 585e692e-cebb-48ac-93ab-b2e7eb7ae7ad
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Create App-V Package Accelerators (App-V 4.6 SP1)
-
-
-You can use App-V Package Accelerators to automatically generate a new virtual application package. After you have successfully created a Package Accelerator, you can reuse and share the Package Accelerator. For more information about Package Accelerators, see [About App-V Package Accelerators (App-V 4.6 SP1)](about-app-v-package-accelerators--app-v-46-sp1-.md). Creating App-V Package Accelerators is an advanced task. Package Accelerators can contain password and user-specific information. Therefore you must save Package Accelerators and the associated installation media in a secure location, and you should digitally sign the Package Accelerator after you create it so that the publisher can be verified when the App-V Package Accelerator is applied.
-
-In some situations, to create the Package Accelerator, you might have to install the application locally on the computer running the Sequencer. First try to create the Package Accelerator by using the installation media, and if there are a number of missing files that are required, install the application locally to the computer running the Sequencer, and then create the Package Accelerator.
-
-**Important**
-Before you begin the following procedure, you should do the following:
-
-- Copy the virtual application package that you must use to create the Package Accelerator locally to the computer running the Sequencer.
-
-- Copy all required installation files associated with the virtual application package to the computer running the Sequencer.
-
-
-
-**Important**
-Disclaimer: The Microsoft Application Virtualization Sequencer does not give you any license rights to the software application you are using to create a Package Accelerator. You must abide by all end user license terms for such application. It is your responsibility to make sure the software application’s license terms allow you to create a Package Accelerator using Application Virtualization Sequencer.
-
-
-
-**To create an App-V Package Accelerator**
-
-1. To start the App-V Sequencer, on the computer that is running the App-V Sequencer, click **Start** / **All Programs** / **Microsoft Application Virtualization** / **Microsoft Application Virtualization Sequencer**.
-
-2. To start the App-V **Create Package Accelerator** wizard, in the App-V Sequencer, click **Tools** / **Create Package Accelerator**.
-
-3. On the **Select Package** page, to specify an existing virtual application package to use to create the Package Accelerator, click **Browse**, and locate the existing virtual application package (.sprj file).
-
- **Tip**
- Copy the files associated with the virtual application package you plan to use locally to the computer running the Sequencer.
-
-
-
-~~~
-Click **Next**.
-~~~
-
-4. On the **Installation Files** page, to specify the folder that contains the installation files that you used to create the original virtual application package, click **Browse**, and then select the directory that contains the installation files.
-
- **Tip**
- Copy the folder that contains the required installation files to the computer running the Sequencer.
-
-
-
-~~~
-If the application is already installed on the computer running the Sequencer, to specify the installation file, select **Files installed on local system**. To use this option, the application must already be installed in the default installation location.
-~~~
-
-5. On the **Gathering Information** page, review the files that were not found in the location specified on the **Installation Files** page of this wizard. If the files displayed are not required, select **Remove these files**, and then click **Next**. If the files are required, click **Previous** and copy the required files to the directory specified on the **Installation Files** page.
-
- **Note**
- You must either remove the unrequired files, or click **Previous** and locate the required files to advance to the next page of this wizard.
-
-
-
-6. On the **Select Files** page, carefully review the files that were detected, and clear any file that should be removed from the Package Accelerator. Select only files that are required for the application to run successfully, and then click **Next**.
-
-7. On the **Verify Applications** page, confirm that all installation files that are required to build the package are displayed. When the Package Accelerator is used to create a new package, all installation files displayed in the **Applications** pane are required to create the package.
-
- If necessary, to add additional Installer files, click **Add**. To remove unnecessary installation files, select the Installer file, and then click **Delete**. To edit the properties associated with an installer, click **Edit**. The installation files specified in this step will be required when the Package Accelerator is used to create a new virtual application package. After you have confirmed the information displayed, click **Next**.
-
-8. On the **Select Guidance** page, to specify a file that contains information about how the Package Accelerator, click **Browse**. For example, this file can contain information about how the computer running the Sequencer should be configured, application prerequisite information for target computers, and general notes. You should provide all required information for the Package Accelerator to be successfully applied. The file you select must be in rich text (.rtf) or text file (.txt) format. Click **Next**.
-
-9. On the **Create Package Accelerator** page, to specify where to save the Package Accelerator, click **Browse** and select the directory.
-
-10. On the **Completion** page, to close the **Create Package Accelerator** wizard, click **Close**.
-
- **Important**
- To help ensure that the Package Accelerator is as secure as possible, and so that the publisher can be verified when the Package Accelerator is applied, you should always digitally sign the Package Accelerator.
-
-
-
-## Related topics
-
-
-Configuring the Application Virtualization Sequencer (App-V 4.6 SP1)
-[How to Apply a Package Accelerator to Create a Virtual Application Package (App-V 4.6 SP1)](how-to-apply-a-package-accelerator-to-create-a-virtual-application-package---app-v-46-sp1-.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-create-or-upgrade-virtual-applications-using--the-app-v-sequencer.md b/mdop/appv-v4/how-to-create-or-upgrade-virtual-applications-using--the-app-v-sequencer.md
deleted file mode 100644
index c4db220dcf..0000000000
--- a/mdop/appv-v4/how-to-create-or-upgrade-virtual-applications-using--the-app-v-sequencer.md
+++ /dev/null
@@ -1,64 +0,0 @@
----
-title: How to Create or Upgrade Virtual Applications Using the App-V Sequencer
-description: How to Create or Upgrade Virtual Applications Using the App-V Sequencer
-author: dansimp
-ms.assetid: 661d4f8c-2527-4654-9d92-15ecc652c0db
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Create or Upgrade Virtual Applications Using the App-V Sequencer
-
-
-The following topics provide detailed information about the associated Application Virtualization (App-V) Sequencer task.
-
-## In This Section
-
-
-[How to Sequence an Application](how-to-sequence-an-application.md)
-Provides a step-by-step procedure you can use to sequence an application.
-
-[How to Sequence a New Application (App-V 4.6)](how-to-sequence-a-new-application--app-v-46-.md)
-Provides a step-by-step procedure you can use to sequence an application.
-
-[How to Upgrade an Existing Virtual Application](how-to-upgrade-an-existing-virtual-application.md)
-Provides a step-by-step procedure you can use to upgrade an existing virtual application to a new version.
-
-[How to Upgrade a Virtual Application Package (App-V 4.6)](how-to-upgrade-a-virtual-application-package--app-v-46-.md)
-Provides a step-by-step procedure you can use to upgrade an existing virtual application to a new version.
-
-[How to Modify a Virtual Application Package (App-V 4.6)](how-to-modify-a-virtual-application-package--app-v-46-.md)
-Provides a step-by-step procedure you can use to modify an existing virtual application package.
-
-[How to Sequence a New Application by Using the Command Line](how-to-sequence-a-new-application-by-using-the-command-line.md)
-Provides a step-by-step procedure you can use to sequence a new application by using a command line.
-
-[How to Upgrade a Virtual Application by Using the Command Line](how-to-upgrade-a-virtual-application-by-using-the-command-line.md)
-Provides a step-by-step procedure you can use to upgrade a virtual application by using a command line.
-
-[How To Use Dynamic Suite Composition](how-to-use-dynamic-suite-composition.md)
-Provides information about how to define an application as being dependent on another application such as middleware or a plug-in.
-
-[How to Use the Differential SFT File](how-to-use-the-differential-sft-file.md)
-Provides a step-by-step procedure you can use to create and deploy the Differential SFT file.
-
-## Related topics
-
-
-[Application Virtualization Sequencer](application-virtualization-sequencer.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-create-the-package-root-directory.md b/mdop/appv-v4/how-to-create-the-package-root-directory.md
deleted file mode 100644
index 8e00793ee2..0000000000
--- a/mdop/appv-v4/how-to-create-the-package-root-directory.md
+++ /dev/null
@@ -1,47 +0,0 @@
----
-title: How to Create the Package Root Directory
-description: How to Create the Package Root Directory
-author: dansimp
-ms.assetid: bcfe3bd4-6c60-409a-8ffa-cc22f27194b1
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Create the Package Root Directory
-
-
-The package root directory is the directory on the computer running the App-V Sequencer where files for the sequenced application are installed. This directory also exists virtually on the computer to which a sequenced application will be streamed. You should create the package root directory before you monitor the installation of a new application.
-
-After you have created the package root directory, you can begin sequencing applications. For more information about sequencing a new application, see [How to Install the Sequencer](how-to-install-the-sequencer.md).
-
-**To create the package root directory**
-
-1. To create the package root directory, on the computer running the App-V Sequencer, map the Q:\\ drive to the specified network location. The location you specify should have sufficient space to save the application you are sequencing.
-
-2. To create a directory that you can use for a new virtual application, create a folder on the Q:\\ drive and assign it a name.
-
- **Important**
- The name you assign to virtual application files that will be saved in the package root directory should use the 8.3 naming format. The file names should be no longer than 8 characters with a three-character file name extension.
-
-
-
-## Related topics
-
-
-[Tasks for the Application Virtualization Sequencer](tasks-for-the-application-virtualization-sequencer.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-create-the-sequencer-package-root-directory.md b/mdop/appv-v4/how-to-create-the-sequencer-package-root-directory.md
deleted file mode 100644
index b745ddf86a..0000000000
--- a/mdop/appv-v4/how-to-create-the-sequencer-package-root-directory.md
+++ /dev/null
@@ -1,51 +0,0 @@
----
-title: How to Create the Sequencer Package Root Directory
-description: How to Create the Sequencer Package Root Directory
-author: dansimp
-ms.assetid: 23fe28f1-c284-43ee-b8b7-1dfbed94eea5
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Create the Sequencer Package Root Directory
-
-
-The package root directory is the directory on the computer running the App-V Sequencer where files for the sequenced application are installed. This directory also exists virtually on the computer to which a sequenced application will be streamed. You should create the package root directory before you monitor the installation of a new application.
-
-After you have created the package root directory, you can begin sequencing applications. For more information about sequencing a new application, see [How to Sequence an Application](how-to-sequence-an-application.md).
-
-**To create the package root directory**
-
-1. To create the package root directory, on the computer running the App-V Sequencer, map the Q:\\ drive to the specified network location. The location you specify should have sufficient space to save the application you are sequencing.
-
-2. To create a directory that you can use for a new virtual application, create a folder on the Q:\\ drive and assign it a name.
-
- **Important**
- The name you assign to virtual application files that will be saved in the package root directory should use the 8.3 naming format. The file names should be no longer than 8 characters with a three-character file name extension.
-
-
-
-## Related topics
-
-
-[Application Virtualization Sequencer](application-virtualization-sequencer.md)
-
-[How to Modify the Log Directory Location](how-to-modify-the-log-directory-location.md)
-
-[How to Modify the Scratch Directory Location](how-to-modify-the-scratch-directory-location.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-customize-an-application-virtualization-system-in-the-server-management-console.md b/mdop/appv-v4/how-to-customize-an-application-virtualization-system-in-the-server-management-console.md
deleted file mode 100644
index f1e04f6d1e..0000000000
--- a/mdop/appv-v4/how-to-customize-an-application-virtualization-system-in-the-server-management-console.md
+++ /dev/null
@@ -1,55 +0,0 @@
----
-title: How to Customize an Application Virtualization System in the Server Management Console
-description: How to Customize an Application Virtualization System in the Server Management Console
-author: dansimp
-ms.assetid: e3a51d1d-451d-46a5-8ae5-f5792d49495b
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Customize an Application Virtualization System in the Server Management Console
-
-
-You can choose a variety of options to customize an Application Virtualization System. These options are available through the user interface of the Application Virtualization Server Management Console.
-
-## In This Section
-
-
-[How to Set Up and Enable or Disable Authentication](how-to-set-up-and-enable-or-disable-authentication.md)
-Provides procedures you can use to establish the levels of authentication for defining who has access to the system.
-
-[How to Set Up or Disable Usage Reporting](how-to-set-up-or-disable-usage-reporting.md)
-Provides procedures for setting up or disabling usage reporting.
-
-[How to Set Up or Disable Database Size](how-to-set-up-or-disable-database-size.md)
-Provides procedures for setting up the database size limits and determining when the server will clean up the database.
-
-[How to Set Up or Disable Application Licensing](how-to-set-up-or-disable-application-licensing.md)
-Provides procedures for setting up or disabling application licensing.
-
-[How to Add an Administrator Group](how-to-add-an-administrator-group.md)
-Provides a procedure for adding an administrator group.
-
-[How to Delete an Administrator Group](how-to-delete-an-administrator-group.md)
-Provides a procedure for deleting an administrator group.
-
-## Related topics
-
-
-[How to Perform Administrative Tasks in the Application Virtualization Server Management Console](how-to-perform-administrative-tasks-in-the-application-virtualization-server-management-console.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-delete-a-file-type-association.md b/mdop/appv-v4/how-to-delete-a-file-type-association.md
deleted file mode 100644
index 16c96b8513..0000000000
--- a/mdop/appv-v4/how-to-delete-a-file-type-association.md
+++ /dev/null
@@ -1,46 +0,0 @@
----
-title: How to Delete a File Type Association
-description: How to Delete a File Type Association
-author: dansimp
-ms.assetid: bb2dd1cf-9a5d-45a9-aca1-3c53144b73ec
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Delete a File Type Association
-
-
-You can use the following procedure to delete a file type association. The **File Type Associations** node is one level below the **Application Virtualization** node in the **Scope** pane. When you select this node, the **Results** pane displays a list of file type associations.
-
-**To remove a file type association**
-
-1. In the **Results** pane, right-click the extension of the file type association you want to delete.
-
-2. Select **Delete** from the pop-up menu.
-
-3. Click **Yes** to delete the association, or click **No** to return to the **Results** pane.
-
-## Related topics
-
-
-[How to Add a File Type Association](how-to-add-a-file-type-association.md)
-
-[How to Add an Application](how-to-add-an-application.md)
-
-[How to Publish Application Shortcuts](how-to-publish-application-shortcuts.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-delete-a-package-version.md b/mdop/appv-v4/how-to-delete-a-package-version.md
deleted file mode 100644
index c1d92e1264..0000000000
--- a/mdop/appv-v4/how-to-delete-a-package-version.md
+++ /dev/null
@@ -1,56 +0,0 @@
----
-title: How to Delete a Package Version
-description: How to Delete a Package Version
-author: dansimp
-ms.assetid: a55adb9d-ffa6-4df3-a2d1-5e0c73c35e1b
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Delete a Package Version
-
-
-From the Application Virtualization Server Management Console, for a package that has multiple versions, you can use the following procedure to delete one or more versions and still stream the remaining versions of the package. You might do this to more effectively manage files on the server or to remove an obsolete version.
-
-**Note**
-When you choose to delete a version, a confirmation box reminds you that client computers might still be using it. You should advise users to exit and unload any applications before you remove a version that is in use.
-
-
-
-**To delete a package version**
-
-1. In the left panel of the Application Virtualization Server Management Console, expand **Packages**.
-
-2. Click the package that contains the version you want to delete.
-
-3. In the center pane, right-click the version of the package you want to delete and choose **Delete**.
-
-4. Read the confirmation window, and click **Yes** to complete the action.
-
- **Note**
- If you have users in disconnected operation, their applications will be replaced with the new versions the next time they connect to the servers. After you are sure all users have updated applications, you can delete old versions.
-
-
-
-## Related topics
-
-
-[How to Delete a Package](how-to-delete-a-packageserver.md)
-
-[How to Manage Packages in the Server Management Console](how-to-manage-packages-in-the-server-management-console.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-delete-a-packageserver.md b/mdop/appv-v4/how-to-delete-a-packageserver.md
deleted file mode 100644
index 7f2bd13bae..0000000000
--- a/mdop/appv-v4/how-to-delete-a-packageserver.md
+++ /dev/null
@@ -1,49 +0,0 @@
----
-title: How to Delete a Package
-description: How to Delete a Package
-author: dansimp
-ms.assetid: 23f9c0e9-8910-47df-9fc0-7bbb5bbf2dc9
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Delete a Package
-
-
-You can use the following procedure to delete a package, including all versions of the package, from the Application Virtualization Server Management Console. You might do this for easier management of files on the server or to remove a package and replace it with a more stable one.
-
-**Important**
-When you choose to delete a package, a confirmation box reminds you that this action deletes all its versions. The server will no longer be able to stream the application.
-
-
-
-**To delete a package**
-
-1. In the left pane of the Application Virtualization Server Management Console, expand **Packages**.
-
-2. In the menu tree pane, right-click the package you want to delete and choose **Delete**.
-
-3. Read the confirmation window, and click **Yes** to complete the action.
-
-## Related topics
-
-
-[How to Delete a Package Version](how-to-delete-a-package-version.md)
-
-[How to Manage Packages in the Server Management Console](how-to-manage-packages-in-the-server-management-console.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-delete-a-reportserver.md b/mdop/appv-v4/how-to-delete-a-reportserver.md
deleted file mode 100644
index 14ac327bbf..0000000000
--- a/mdop/appv-v4/how-to-delete-a-reportserver.md
+++ /dev/null
@@ -1,48 +0,0 @@
----
-title: How to Delete a Report
-description: How to Delete a Report
-author: dansimp
-ms.assetid: 53350b71-1fb5-4f7e-a684-9ea1116c5c3f
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Delete a Report
-
-
-From the Application Virtualization Server Management Console, the process for deleting a report is the same regardless of the report type.
-
-**To delete a report**
-
-1. Click the **Reports** node to expand the list of reports.
-
-2. Right-click the desired report (either in the **Reports** node or the **Results** pane), and select **Delete**.
-
-## Related topics
-
-
-[Application Virtualization Report Types](application-virtualization-report-types.md)
-
-[How to Create a Report](how-to-create-a-reportserver.md)
-
-[How to Export a Report](how-to-export-a-reportserver.md)
-
-[How to Print a Report](how-to-print-a-reportserver.md)
-
-[How to Run a Report](how-to-run-a-reportserver.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-delete-all-virtual-applications-by-using-the-command-line.md b/mdop/appv-v4/how-to-delete-all-virtual-applications-by-using-the-command-line.md
deleted file mode 100644
index 1fdb2c31c6..0000000000
--- a/mdop/appv-v4/how-to-delete-all-virtual-applications-by-using-the-command-line.md
+++ /dev/null
@@ -1,52 +0,0 @@
----
-title: How to Delete All Virtual Applications by Using the Command Line
-description: How to Delete All Virtual Applications by Using the Command Line
-author: dansimp
-ms.assetid: bfe13b5c-825a-4eb1-a979-6c4b8d8b2a9c
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Delete All Virtual Applications by Using the Command Line
-
-
-You can use the following procedure to delete all virtual applications from a specific computer.
-
-**Note**
-When all applications are deleted from a package, the Application Virtualization (App-V) Client also deletes the package.
-
-
-
-**To delete all applications**
-
-- Run the following command to delete all applications for the user account under which the command is run. If you run the command with the optional /GLOBAL switch, using an account with administrative rights, all applications are deleted for all users.
-
- `SFTMIME DELETE OBJ:APP [/GLOBAL]`
-
- **Note**
- When all applications are deleted from a package, the Application Virtualization (App-V) Client also deletes the package.
-
-
-
-## Related topics
-
-
-[How to Add a Package by Using the Command Line](how-to-add-a-package-by-using-the-command-line.md)
-
-[How to Remove a Package by Using the Command Line](how-to-remove-a-package-by-using-the-command-line.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-delete-an-administrator-group.md b/mdop/appv-v4/how-to-delete-an-administrator-group.md
deleted file mode 100644
index d538220e01..0000000000
--- a/mdop/appv-v4/how-to-delete-an-administrator-group.md
+++ /dev/null
@@ -1,44 +0,0 @@
----
-title: How to Delete an Administrator Group
-description: How to Delete an Administrator Group
-author: dansimp
-ms.assetid: 398a8028-e128-4020-bbe2-59ba63b5cd48
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Delete an Administrator Group
-
-
-From the **Administrators** node of the Application Virtualization Server Management Console, you can use the following procedure to delete an administrator group.
-
-**To delete an administrator group**
-
-1. Click the **Administrators** node to display the list of administrator groups in the **Results** pane.
-
-2. In the **Actions** pane (far right pane), click **Delete**.
-
-3. Click **Yes**.
-
-## Related topics
-
-
-[How to Add an Administrator Group](how-to-add-an-administrator-group.md)
-
-[How to Customize an Application Virtualization System in the Server Management Console](how-to-customize-an-application-virtualization-system-in-the-server-management-console.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-delete-an-application-server.md b/mdop/appv-v4/how-to-delete-an-application-server.md
deleted file mode 100644
index 55f77b412f..0000000000
--- a/mdop/appv-v4/how-to-delete-an-application-server.md
+++ /dev/null
@@ -1,51 +0,0 @@
----
-title: How to Delete an Application
-description: How to Delete an Application
-author: dansimp
-ms.assetid: 421e7df0-fea3-4cb2-a884-3d04f2223da7
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Delete an Application
-
-
-You can delete an application through the Application Virtualization Server Management Console. This does not delete its Open Software Descriptor (.osd) file for other files from the Application Virtualization Server. After it is deleted, however, the application no longer streams to end users.
-
-**Note**
-If this is the only application in a package, deleting it also removes related package data and file associations.
-
-
-
-**To delete an application**
-
-1. In the left pane of the management console, click the **Applications** node.
-
-2. In the right pane, highlight one or more applications you want to delete. You can use CTRL or Shift key combinations to highlight multiple applications.
-
-3. Right-click the application or applications, and choose **Delete**.
-
-4. In the **Remove Application** confirmation prompt, click **Yes** to complete the action.
-
-## Related topics
-
-
-[How to Import an Application](how-to-import-an-applicationserver.md)
-
-[How to Manage Applications in the Server Management Console](how-to-manage-applications-in-the-server-management-console.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-delete-an-application.md b/mdop/appv-v4/how-to-delete-an-application.md
deleted file mode 100644
index c1e441347c..0000000000
--- a/mdop/appv-v4/how-to-delete-an-application.md
+++ /dev/null
@@ -1,42 +0,0 @@
----
-title: How to Delete an Application
-description: How to Delete an Application
-author: dansimp
-ms.assetid: 03b0912d-b14a-4522-916d-71f8b77a8a82
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Delete an Application
-
-
-When you select the **Application** node in the Application Virtualization Client Management Console, the **Results** pane displays a list of applications. You can use the following procedure to delete an application from the **Results** pane, which also removes the application from the cache.
-
-**Note**
-When you delete an application, the selected application will no longer be available to any users on that client. Shortcuts and file type associations are hidden, and the application is deleted from cache. However, if another application refers to data in the file system cache data for the selected application, these items will not be deleted.
-
-After a publishing refresh, the deleted applications will again become available to you.
-
-
-
-**To delete an application**
-
-1. Move the cursor to the **Results** pane, right-click the desired application, and select **Delete** from the pop-up menu.
-
-2. At the confirmation prompt, click **Yes** to remove the application or click **No** to cancel the operation.
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-deny-access-to-an-application.md b/mdop/appv-v4/how-to-deny-access-to-an-application.md
deleted file mode 100644
index 1dd6b7fdf5..0000000000
--- a/mdop/appv-v4/how-to-deny-access-to-an-application.md
+++ /dev/null
@@ -1,53 +0,0 @@
----
-title: How to Deny Access to an Application
-description: How to Deny Access to an Application
-author: dansimp
-ms.assetid: 14f5e201-7265-462c-b738-57938dc3fc30
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Deny Access to an Application
-
-
-Users must be in an application's **Access Permissions** list to load and use the application. Although the Application Virtualization Server Management Console does not support explicitly denying a user group access to an application, you can remove the user groups from an application’s properties to achieve this.
-
-**To deny access to an application**
-
-1. For an existing application, click the **Applications** node in the left pane.
-
-2. Right-click an application in the right pane, and choose **Properties**. Then select the **Access Permissions** tab.
-
-3. To remove access for a user group, highlight the user group and click **Remove**.
-
-4. Click **OK**.
-
- **Note**
- To control access to applications, you can also limit the application licenses. Setting up the proper user groups in Active Directory Domain Services provides the easiest way to grant and deny access to specific sets of users.
-
-
-
-## Related topics
-
-
-[How to Grant Access to an Application](how-to-grant-access-to-an-application.md)
-
-[How to Manage Application Licenses in the Server Management Console](how-to-manage-application-licenses-in-the-server-management-console.md)
-
-[How to Manage Applications in the Server Management Console](how-to-manage-applications-in-the-server-management-console.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-determine-whether-to-edit-or-upgrade-a-virtual-application-package.md b/mdop/appv-v4/how-to-determine-whether-to-edit-or-upgrade-a-virtual-application-package.md
deleted file mode 100644
index 6fda63581a..0000000000
--- a/mdop/appv-v4/how-to-determine-whether-to-edit-or-upgrade-a-virtual-application-package.md
+++ /dev/null
@@ -1,160 +0,0 @@
----
-title: How to Determine Whether to Edit or Upgrade a Virtual Application Package
-description: How to Determine Whether to Edit or Upgrade a Virtual Application Package
-author: dansimp
-ms.assetid: 33dd5332-6802-46e0-9748-43fcc8f80aa3
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Determine Whether to Edit or Upgrade a Virtual Application Package
-
-
-Use the following table to help determine whether a virtual application package can be opened for edit, whether you need to create a new version of the package, or whether either option is available, using the App-V Sequencer.
-
-
-
-
-
-
-
-
-
-
Action
-
Open for edit
-
Open for upgrade
-
-
-
-
-
View package properties.
-
Yes
-
Yes
-
-
-
View package change history.
-
Yes
-
Yes
-
-
-
View associated package files.
-
Yes
-
Yes
-
-
-
Edit registry settings.
-
Yes
-
Yes
-
-
-
Review additional package settings (except operating system file properties).
-
Yes
-
Yes
-
-
-
Create associated Windows Installer (MSI).
-
Yes
-
Yes
-
-
-
Modify OSD file.
-
Yes
-
Yes
-
-
-
Compress and uncompress package.
-
Yes
-
Yes
-
-
-
Add file type associations.
-
Yes
-
Yes
-
-
-
Rename shortcuts.
-
Yes
-
Yes
-
-
-
Set virtualized registry key state (override / merge).
-
Yes
-
Yes
-
-
-
Set virtualized folder state.
-
Yes
-
Yes
-
-
-
Edit virtual file system mappings.
-
Yes
-
Yes
-
-
-
Review all associated operating system file properties for a package.
-
No
-
Yes
-
-
-
Add additional services.
-
No
-
Yes
-
-
-
Add additional files.
-
No
-
Yes
-
-
-
Collect and configure associated security descriptors.
-
No
-
Yes
-
-
-
Apply security updates or upgrade to a new version.
-
No
-
Yes
-
-
-
Add an additional application.
-
No
-
Yes
-
-
-
Apply updates that require the application to open.
-
No
-
Yes
-
-
-
Apply updates that require the computer to restart.
-
No
-
Yes
-
-
-
-
-
-
-## Related topics
-
-
-[How to Edit an Existing Virtual Application](how-to-edit-an-existing-virtual-application.md)
-
-[How to Upgrade an Existing Virtual Application](how-to-upgrade-an-existing-virtual-application.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-determine-which-type-of-application-to-sequence---app-v-46-sp1-.md b/mdop/appv-v4/how-to-determine-which-type-of-application-to-sequence---app-v-46-sp1-.md
deleted file mode 100644
index 5394ec7bb3..0000000000
--- a/mdop/appv-v4/how-to-determine-which-type-of-application-to-sequence---app-v-46-sp1-.md
+++ /dev/null
@@ -1,73 +0,0 @@
----
-title: How to Determine Which Type of Application to Sequence (App-V 4.6 SP1)
-description: How to Determine Which Type of Application to Sequence (App-V 4.6 SP1)
-author: dansimp
-ms.assetid: 936abee2-98f1-45fb-9f0d-786e1d7464b1
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 08/30/2016
----
-
-
-# How to Determine Which Type of Application to Sequence (App-V 4.6 SP1)
-
-
-You can sequence three basic types of applications by using Microsoft Application Virtualization (App-V) Sequencer.
-
-## To determine which type of application to sequence
-
-
-Use the following table to determine which type of application you should sequence and to obtain more information about how to sequence the application.
-
-
-
-
-
-
-
-
-
-
Application Type
-
Description
-
More Information
-
-
-
-
-
Standard
-
Select this option to create a package that contains an application or a suite of applications. You should select this option for most applications that you plan to sequence.
Select this option to create a package that extends the functionality of a standard application, for example, a plug-in for Microsoft Excel. Additionally, you can use plug-ins for natively installed applications, or another package that is linked by using Dynamic Suite Composition. For more information about Dynamic Suite Composition, see How To Use Dynamic Suite Composition (https://go.microsoft.com/fwlink/?LinkId=203804).
Select this option to create a package that is required by a standard application, for example, the Microsoft .NET Framework. Middleware packages are used for linking to other packages by using Dynamic Suite Composition. For more information about Dynamic Suite Composition, see How To Use Dynamic Suite Composition (https://go.microsoft.com/fwlink/?LinkId=203804).
-
-
-
-## Related topics
-
-
-[Tasks for the Application Virtualization Sequencer (App-V 4.6 SP1)](tasks-for-the-application-virtualization-sequencer--app-v-46-sp1-.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-disable-or-modify-disconnected-operation-mode-settings.md b/mdop/appv-v4/how-to-disable-or-modify-disconnected-operation-mode-settings.md
deleted file mode 100644
index fc1d34c067..0000000000
--- a/mdop/appv-v4/how-to-disable-or-modify-disconnected-operation-mode-settings.md
+++ /dev/null
@@ -1,62 +0,0 @@
----
-title: How to Disable or Modify Disconnected Operation Mode Settings
-description: How to Disable or Modify Disconnected Operation Mode Settings
-author: dansimp
-ms.assetid: 39f166d7-2d25-4899-8405-b45f051facb8
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Disable or Modify Disconnected Operation Mode Settings
-
-
-Use the following procedures in Application Virtualization Client to disable or modify disconnected operation mode settings.
-
-**To disable disconnected operation**
-
-1. Right-click the **Application Virtualization** node in the console, and select **Properties** from the pop-up menu.
-
-2. Click the **Connectivity** tab, and then clear **Allow disconnected operation** check box.
-
-3. Click **OK** to accept the change.
-
-**To change the time-out**
-
-1. Right-click the **Application Virtualization** node in the console, and select **Properties** from the pop-up menu.
-
-2. Click the **Connectivity** tab, and then select the **Limit disconnected operation to** check box.
-
-3. In the field, enter a value from 1–999999 (representing days). The default value is 90 days.
-
-4. Click **OK** to accept the change.
-
-**To work offline**
-
-1. Right-click the **Application Virtualization** node in the console, and select **Properties** from the pop-up menu.
-
-2. Click the **Connectivity** tab, and then select the **Work offline** check box.
-
-3. Click **OK** to accept the change.
-
-## Related topics
-
-
-[Disconnected Operation Mode](disconnected-operation-mode.md)
-
-[How to Work Offline or Online with Application Virtualization](how-to-work-offline-or-online-with-application-virtualization.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-edit-an-existing-virtual-application.md b/mdop/appv-v4/how-to-edit-an-existing-virtual-application.md
deleted file mode 100644
index 822fe72dd9..0000000000
--- a/mdop/appv-v4/how-to-edit-an-existing-virtual-application.md
+++ /dev/null
@@ -1,46 +0,0 @@
----
-title: How to Edit an Existing Virtual Application
-description: How to Edit an Existing Virtual Application
-author: dansimp
-ms.assetid: 358b9a69-5695-4c6f-92e1-7ed2b69a2def
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Edit an Existing Virtual Application
-
-
-You can use the following procedure to edit the properties associated with an existing virtual application package by using the Application Virtualization (App-V) Sequencer. You must open the existing virtual application, make the necessary updates, and then save the updated virtual application package.
-
-**To modify an existing virtual application**
-
-1. To start the App-V Sequencer Console, on the computer running the App-V Sequencer, select **Start**/**Programs**/**Microsoft Application Virtualization**/**Microsoft Application Virtualization Sequencer**.
-
-2. To open the existing virtual application, in the App-V Console, select **File**/**Open**. Use the **Open** dialog box to locate the associated SPRJ file you want to modify.
-
-3. Modify the virtual application package. For more information about what properties can be modified, see [How to Determine Whether to Edit or Upgrade a Virtual Application Package](how-to-determine-whether-to-edit-or-upgrade-a-virtual-application-package.md).
-
-4. To save the modifications, select **File** / **Save**.
-
-## Related topics
-
-
-[How to Create or Upgrade Virtual Applications Using the App-V Sequencer](how-to-create-or-upgrade-virtual-applications-using--the-app-v-sequencer.md)
-
-[How to Upgrade an Existing Virtual Application](how-to-upgrade-an-existing-virtual-application.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-edit-an-osd-file-using-a-text-editor.md b/mdop/appv-v4/how-to-edit-an-osd-file-using-a-text-editor.md
deleted file mode 100644
index 41b7631eb1..0000000000
--- a/mdop/appv-v4/how-to-edit-an-osd-file-using-a-text-editor.md
+++ /dev/null
@@ -1,57 +0,0 @@
----
-title: How to Edit an OSD File Using a Text Editor
-description: How to Edit an OSD File Using a Text Editor
-author: dansimp
-ms.assetid: f4263a1b-824f-49b9-8060-b8229c9d9960
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Edit an OSD File Using a Text Editor
-
-
-Use the following procedure to edit an Open Software Descriptor (OSD) file by using a text editor.
-
-**To edit an OSD file by using a text editor**
-
-1. Open the OSD file using any XML or ASCII text editor—for example, Microsoft Notepad.
-
- **Note**
- Before modifying the OSD file, read the schema prescribed by the XSD file in the install directory. Failing to follow this schema might introduce errors that prevent a sequenced application from starting successfully.
-
-
-
-2. Edit the OSD file using your XML or ASCII text editor of choice, adhering to the prescribed schema and the following guidelines:
-
- 1. Ensure that named elements are nested within the <SOFTPKG> root element.
-
- 2. Ensure that element names are in all uppercase letters.
-
- 3. Be aware that attribute values are case sensitive.
-
- 4. Type carefully, and observe the XML specifications.
-
-## Related topics
-
-
-[About the OSD Tab](about-the-osd-tab.md)
-
-[How to Edit an OSD File](how-to-edit-an-osd-file.md)
-
-[OSD File Elements](osd-file-elements.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-edit-an-osd-file.md b/mdop/appv-v4/how-to-edit-an-osd-file.md
deleted file mode 100644
index 6f19e9a7b7..0000000000
--- a/mdop/appv-v4/how-to-edit-an-osd-file.md
+++ /dev/null
@@ -1,92 +0,0 @@
----
-title: How to Edit an OSD File
-description: How to Edit an OSD File
-author: dansimp
-ms.assetid: 0d126ba7-72fb-42ce-982e-90ed01a852c8
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Edit an OSD File
-
-
-Use the following procedures to modify a sequenced application package's Open Software Descriptor (OSD) file by adding or deleting an element or an attribute.
-
-**Note**
- Some elements do not have an attribute, so it is not possible to add an attribute to every element.
-
-
-
-**Important**
-If you use the OSD editor to change the .sft file name, the HREF attribute of the CODEBASE element in the OSD file, you must use the **Save As** command to save the change to the project files.
-
-
-
-**To add an element**
-
-1. Click the **OSD File** tab.
-
-2. In the navigation pane, select the sequenced application package's OSD file you want to modify.
-
-3. In the navigation pane, right-click the element that you want to modify. On the menu, select **Element** and select **Add**.
-
-4. From the menu, select the element you want to add—for example, **Codebase**.
-
-5. From the **File** menu, select **Save**.
-
-**To delete an element**
-
-1. Click the **OSD File** tab.
-
-2. In the navigation pane, select the sequenced application package's OSD file you want to modify.
-
-3. In the navigation pane, right-click the element that you want to delete. On the menu, select **Element** and select **Delete**.
-
-4. From the **File** menu, select **Save**.
-
-**To add an attribute**
-
-1. Click the **OSD File** tab.
-
-2. In the navigation pane, select the sequenced application package's OSD file you want to modify.
-
-3. In the left pane, right-click the element to which you want to add an attribute. On the menu, select **Attribute** and select **Add**, choosing from the listed available attributes.
-
-4. From the **File** menu, select **Save**.
-
-**To delete an attribute**
-
-1. Click the **OSD File** tab.
-
-2. In the navigation pane, select the sequenced application package's OSD file you want to modify.
-
-3. In the navigation pane, right-click the element from which you want to delete an attribute. On the menu, select **Attribute** and then select **Delete**, choosing the attribute you wish to delete.
-
-4. From the **File** menu, select **Save**.
-
-## Related topics
-
-
-[About the OSD Tab](about-the-osd-tab.md)
-
-[How to Edit an OSD File Using a Text Editor](how-to-edit-an-osd-file-using-a-text-editor.md)
-
-[OSD File Elements](osd-file-elements.md)
-
-[Sequencer Console](sequencer-console.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-exit-the-app-v-client-from-the-notification-area.md b/mdop/appv-v4/how-to-exit-the-app-v-client-from-the-notification-area.md
deleted file mode 100644
index 480c2d8d34..0000000000
--- a/mdop/appv-v4/how-to-exit-the-app-v-client-from-the-notification-area.md
+++ /dev/null
@@ -1,40 +0,0 @@
----
-title: How to Exit the App-V Client from the Notification Area
-description: How to Exit the App-V Client from the Notification Area
-author: dansimp
-ms.assetid: 71ebf88b-ef51-41a5-ae34-4e197d9d6ee6
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Exit the App-V Client from the Notification Area
-
-
-You can use the following procedure to exit the Application Virtualization Desktop Client or Client for Remote Desktop Services.
-
-**To exit the client**
-
-- Right-click the Application Virtualization System icon in the notification area, and select **Exit** from the pop-up menu.
-
- If you choose to exit from the client while virtual applications are open, the system displays a prompt telling you that you will lose unsaved data. Select **OK** or **Cancel** to acknowledge and close the prompt.
-
-## Related topics
-
-
-[How to Use the Desktop Notification Area for Application Virtualization Client Management](how-to-use-the-desktop-notification-area-for-application-virtualization-client-management.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-export-a-reportserver.md b/mdop/appv-v4/how-to-export-a-reportserver.md
deleted file mode 100644
index f7eb70e1aa..0000000000
--- a/mdop/appv-v4/how-to-export-a-reportserver.md
+++ /dev/null
@@ -1,56 +0,0 @@
----
-title: How to Export a Report
-description: How to Export a Report
-author: dansimp
-ms.assetid: 2f917130-db02-4c72-a45a-7928e51e689e
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Export a Report
-
-
-The process for exporting a report, using the Application Virtualization Console, is the same regardless of the report type.
-
-**To export a report**
-
-1. Right-click the report displayed in the **Results** pane, and select **Export** from the drop down menu.
-
-2. Select the report type from the list of types.
-
-3. In the **Save As** dialog box, navigate to the location where you want to save the output.
-
-4. Enter a name for the report in the **File Name** field, or select a file from the drop-down list of files.
-
-5. Select an output type from the **Save as Type** drop-down list of types.
-
-6. Click the **Save** button to save the file.
-
-## Related topics
-
-
-[Application Virtualization Report Types](application-virtualization-report-types.md)
-
-[How to Create a Report](how-to-create-a-reportserver.md)
-
-[How to Delete a Report](how-to-delete-a-reportserver.md)
-
-[How to Print a Report](how-to-print-a-reportserver.md)
-
-[How to Run a Report](how-to-run-a-reportserver.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-grant-access-to-an-application.md b/mdop/appv-v4/how-to-grant-access-to-an-application.md
deleted file mode 100644
index 89a6cf8277..0000000000
--- a/mdop/appv-v4/how-to-grant-access-to-an-application.md
+++ /dev/null
@@ -1,59 +0,0 @@
----
-title: How to Grant Access to an Application
-description: How to Grant Access to an Application
-author: dansimp
-ms.assetid: e54d9e84-21f5-488f-b040-25f374d9289f
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Grant Access to an Application
-
-
-As the administrator, you can use the Application Virtualization Server Management Console to determine which users can access which applications. You can do this when you import the Sequencer Project (SPRJ) or Open Software Descriptor (OSD) file or at anytime using the application's **Properties** dialog box. With both methods, use the **Access Permissions** options to add users.
-
-**To grant access to an application**
-
-1. For an existing application, click the **Applications** node in the left pane. Right-click an application in the right pane, and choose **Properties**.
-
-2. Select the **Access Permissions** tab.
-
-3. To add user groups, click **Add**.
-
-4. In the **Add/Edit User Group** dialog box, navigate to the user group. You can also enter the domain and group by typing the information in the respective fields.
-
-5. Click **OK**. You can add other groups with the same pages.
-
-6. When the wizard reappears, click **OK**.
-
- **Note**
- You must set up your groups in Active Directory Domain Services before you attempt to grant access to applications.
-
-
-
-## Related topics
-
-
-[How to Deny Access to an Application](how-to-deny-access-to-an-application.md)
-
-[How to Manage Application Groups in the Server Management Console](how-to-manage-application-groups-in-the-server-management-console.md)
-
-[How to Manage Application Licenses in the Server Management Console](how-to-manage-application-licenses-in-the-server-management-console.md)
-
-[How to Manually Add an Application](how-to-manually-add-an-application.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-import-an-application.md b/mdop/appv-v4/how-to-import-an-application.md
deleted file mode 100644
index 2fc950a033..0000000000
--- a/mdop/appv-v4/how-to-import-an-application.md
+++ /dev/null
@@ -1,40 +0,0 @@
----
-title: How to Import an Application
-description: How to Import an Application
-author: dansimp
-ms.assetid: 85aaf5d8-489c-4929-996f-f15d2dab1ad8
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Import an Application
-
-
-You can use the following procedure to import an application into the cache directly from the **Results** pane of the **Application** node in the Application Virtualization Client Management Console.
-
-**To import an application**
-
-1. Move the cursor to the **Results** pane, right-click the desired application, and select **Import** from the pop-up menu.
-
-2. From the **Browse** window, navigate to the location of the package file for the desired application, and then click **OK**.
-
- **Note**
- If you have already configured an import search path or if the SFT file is in the same path as the last successful import, step 2 is not required.
-
-
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-import-an-applicationserver.md b/mdop/appv-v4/how-to-import-an-applicationserver.md
deleted file mode 100644
index 66852c68c1..0000000000
--- a/mdop/appv-v4/how-to-import-an-applicationserver.md
+++ /dev/null
@@ -1,102 +0,0 @@
----
-title: How to Import an Application
-description: How to Import an Application
-author: dansimp
-ms.assetid: ab40acad-1025-478d-8e13-0e1ff1bd37e4
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Import an Application
-
-
-Typically, you import applications to make them available to stream from an Application Virtualization Management Server. You can also add an application manually, but you must provide precise, detailed information about the application to do so. For more information, see [How to Manually Add an Application](how-to-manually-add-an-application.md).
-
-**Note**
-To import an application, you must have its sequenced Open Software Descriptor (OSD) file or its Sequencer Project (SPRJ) file available on the server.
-
-
-
-When importing an application, you should make sure the server is configured with a value in the **Default Content Path** field on the **General** tab of the **System Options** dialog (accessible by right-clicking the **Application Virtualization System** node in the App-V Server Console). The default content path value defines where the applications will be imported, and during the import process, this value is used to modify the paths defined in the OSD file for the SFT file and for the icon shortcuts. In the OSD file, the path for the SFT file is specified in the CODEBASE HREF entry and the path for the icons is specified in the SHORTCUTS entry.
-
-During the import process, the protocol, server, and, if present, port specified in these two paths in the OSD file will be replaced with the value from the default content path. The following table provides an example of how the import path will be affected.
-
-
-
-
-
-**To import an application**
-
-1. Right-click the **Applications** node in the left pane, and choose **Import Applications**.
-
-2. In the **Open** dialog box, navigate to the application's SPRJ or OSD file. Highlight the file and click **Open**.
-
-3. In the **New Application Wizard**, be sure the **Enabled** box is selected for applications you want to stream. There you can also enter a description and verify the server and file paths. Also, if you have set up license and server groups, you can select those.
-
-4. Click **Next**.
-
-5. On the **Published Shortcuts** screen, select the boxes for the locations where you would like the application shortcuts to appear on the client computers.
-
-6. Click **Next**.
-
-7. In the **File Associations** screen, you can add new file associations to this application. To do so, click **Add**, enter the extension (without a preceding dot), enter a description, and click **OK**.
-
- **Note**
- Applications sequenced with Sequencer 4.0 populate the **File Associations** dialog box when you import or create them through the management console. Applications with previous Sequencer version packages do not.
-
-
-
-8. Click **Next**.
-
-9. In the **Access Permissions** screen, click **Add**.
-
-10. Complete the **Select Groups** dialog box. When you finish, click **OK**.
-
-11. Click **Next**.
-
-12. On the **Summary** screen, you can review the import settings. Click **Finish**, or click **Back** to change the import or click **Cancel** to cancel the import.
-
-## Related topics
-
-
-[How to Manage Application Groups in the Server Management Console](how-to-manage-application-groups-in-the-server-management-console.md)
-
-[How to Manage Applications in the Server Management Console](how-to-manage-applications-in-the-server-management-console.md)
-
-[How to Manually Add an Application](how-to-manually-add-an-application.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-install-a-database.md b/mdop/appv-v4/how-to-install-a-database.md
deleted file mode 100644
index da440a18ff..0000000000
--- a/mdop/appv-v4/how-to-install-a-database.md
+++ /dev/null
@@ -1,95 +0,0 @@
----
-title: How to Install a Database
-description: How to Install a Database
-author: dansimp
-ms.assetid: 52e3a19d-b7cf-4f2c-8268-0f8361cc9766
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 08/30/2016
----
-
-
-# How to Install a Database
-
-
-You can use the following procedure to install a database for your server-based deployment of Application Virtualization if a database is not already available. Typically, in a production environment, you will connect to an existing database.
-
-**Important**
-To install the database, you must use a network account with the appropriate permissions. If your organization requires that only database administrators are allowed to create and conduct database upgrades, scripts are available that allow this task to be performed.
-
-
-
-**To install a database**
-
-1. Navigate to the location of the Application Virtualization System setup program on the network, either run this program from the network or copy its directory to the target computer, and then double-click **Setup.exe**.
-
-2. On the **Welcome Page**, click **Next**.
-
-3. On the **License Agreement** page, to accept the license agreement, select **I accept the license terms and conditions**, and click **Next**.
-
-4. On the **Registering Information** page, specify the **User Name** and **Organization** information, and then click **Next**.
-
-5. On the **Setup Type** page, select **Custom** and then click **Next**.
-
-6. On the **Custom Setup** page, deselect all Application Virtualization System components except **Application Virtualization Server**, and then click **Next**.
-
- **Note**
- If a component is already installed on the computer, by deselecting it on the **Custom Setup** screen it will automatically be uninstalled.
-
-
-
-7. On the **Database Server** page, type the passwords, assign an installation path, save the information, and click **Next**.
-
-8. Select a name for the database, and then click **Next**.
-
- **Note**
- If error 25109 is displayed when you try to complete this step, you have incorrectly set up the permissions necessary to install the database. For details on setting up the necessary SQL permissions, please see .
-
-
-
-9. On the **Directory Server** screen, enter a domain name and credentials that Application Virtualization Servers and the Management Web Service will use to access your domain controller, save this information, and then click **Next**.
-
- **Note**
- The installation will default to the domain of the current computer.
-
-
-
-10. On the **Administrator Group** page, enter the name of a group that will have Administrator privileges, save this information, and then click **Next**.
-
- **Note**
- You can also enter the first few characters of the name of a group that will have Administration privileges, click **Next**, and on the **Select Administrator Group** screen, select the group from the resulting list. Then save this information and click **Next**.
-
-
-
-11. On the **Default Provider Group** page, enter the complete name of a group that will control access to applications, save this information, and then click **Next**.
-
- **Note**
- You can also enter the first few characters of the name of a group that will control access to applications, click **Next**, and on the **Select Default Provider Group** screen, select the group in the list. Then save this information and click **Next**.
-
-
-
-12. On the **Installation Wizard Completed** page, to close the wizard, click **Finish**.
-
- **Important**
- The installation can take a few minutes to finish. A status message will flash above the Windows desktop notification area, indicating whether the installation succeeded.
-
-
-
-## Related topics
-
-
-[How to Install the Servers and System Components](how-to-install-the-servers-and-system-components.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-install-and-configure-the-app-v-management-console-for-a-more-secure-environment.md b/mdop/appv-v4/how-to-install-and-configure-the-app-v-management-console-for-a-more-secure-environment.md
deleted file mode 100644
index ba2ed5bf33..0000000000
--- a/mdop/appv-v4/how-to-install-and-configure-the-app-v-management-console-for-a-more-secure-environment.md
+++ /dev/null
@@ -1,49 +0,0 @@
----
-title: How to Install and Configure the App-V Management Console for a More Secure Environment
-description: How to Install and Configure the App-V Management Console for a More Secure Environment
-author: dansimp
-ms.assetid: 9d89ef09-cdbf-48fc-99da-b24fc987ef8f
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Install and Configure the App-V Management Console for a More Secure Environment
-
-
-The default installation of the App-V Management Console includes support for secure communications. Each Management Console is configured on a per-connection basis when the console is started for the first time or when connecting to an additional App-V Web Management Service. The default configuration uses SSL over TCP port 443. You can change the port number if the port number was modified on the server. You can use the following procedure to connect to an App-V Web Management Service by using a secure connection.
-
-**How to Connect to an App-V Management Service by Using an SSL Connection**
-
-1. Start the Application Virtualization Management Console.
-
-2. Click **Configure Connection** in the actions pane of the console.
-
-3. Type the **Web Service Host Name**, and ensure that **Use Secure Connection** is selected.
-
- **Important**
- The name provided in the Web Service Host Name must match the common name on the certificate, or the connection will fail.
-
-
-
-4. Select the appropriate login credentials, and click **OK**.
-
-## Related topics
-
-
-[Configuring Certificates to Support the App-V Web Management Service](configuring-certificates-to-support-the-app-v-web-management-service.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-install-and-configure-the-default-application.md b/mdop/appv-v4/how-to-install-and-configure-the-default-application.md
deleted file mode 100644
index 529a24aadc..0000000000
--- a/mdop/appv-v4/how-to-install-and-configure-the-default-application.md
+++ /dev/null
@@ -1,105 +0,0 @@
----
-title: How to Install and Configure the Default Application
-description: How to Install and Configure the Default Application
-author: dansimp
-ms.assetid: 5c5d5ad1-af40-4f83-8234-39e972f2c29a
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Install and Configure the Default Application
-
-
-The default application is provided as part of the installation and is automatically copied to the Microsoft Application Virtualization (App-V) Management Server during installation. It is used to verify that the Management Server was installed and configured correctly, but it has to be published to the Microsoft Application Virtualization (App-V) Client so that the user can access it.
-
-Use the following procedures to publish the default application and to stream it.
-
-**To publish the default application**
-
-1. Log on to the App-V Management Server by using an account that is a member of the App-V Administrators group specified during installation.
-
-2. On the App-V Management Server, click **Start**, click **Administrative Tools**, and then click **Application Virtualization Management Console**.
-
-3. In the App-V Management Console, click **Actions**, and then click **Connect to Application Virtualization System**.
-
-4. On the **Configure Connection** page, clear the **Use Secure Connection** check box.
-
-5. In the **Web Service Host Name** box, type the fully qualified domain name (FQDN) of the App-V Management Server, and then click **OK**.
-
- **Note**
- You can also use **localhost** for the Web Service Host name if it is installed on the Management Server.
-
-
-
-6. In the App-V Management Console, right-click the **Server** node, and click **System Options**.
-
-7. On the **General** tab, in the **Default Content Path** box, enter the Universal Naming Convention (UNC) path to the Content folder you created on the server during installation; for example, \\\\<Server Name>\\Content, and then click **OK**.
-
- **Important**
- Use the FQDN for the server name so that the client can resolve the name correctly.
-
-
-
-8. In the App-V Management Console, in the navigation pane, expand the **Server** node, and then click **Applications**.
-
-9. In the topic pane, click **Default Application**, and then, in the **Actions** pane, click **Properties**.
-
-10. In the **Properties** dialog box, next to the **OSD Path** box, click **Browse**.
-
-11. In the **Open** dialog box, enter the UNC path to the Content folder you created on the server during installation; for example, \\\\<Server Name>\\Content, and press ENTER. You must use the actual server name and cannot use the **localhost** here.
-
- **Important**
- Ensure that the values in both the **OSD Path** and **Icon Path** boxes are in UNC format (for example, \\\\<Server Name>\\Content\\DefaultApp.ico), and point to the Content folder you created when installing the server. Do not use **localhost** or a file path containing a drive letter such as C:\\Program Files\\..\\..\\Content.
-
-
-
-12. Select the DefaultApp.osd file, and click **Open**.
-
-13. Repeat the previous steps to configure the icon path.
-
-14. Click the **Access Permissions** tab, and confirm that the App-V Users group has access permissions to the application.
-
-15. Click the **Shortcuts** tab, and then click **Publish to User’s Desktop**. Click **OK**.
-
-16. Open Windows Explorer, and locate the Content directory.
-
-17. Double-click the DefaultApp.osd file, and open it with Notepad.
-
-18. Locate the line that contains the **HREF** tag, and change it to the following code:
-
- `CODEBASEHREF=”RTSP://:554/DefaultApp.sft”`
-
- Or, if you are using RTSPS:
-
- `CODEBASEHREF=”RTSPS://:322/DefaultApp.sft”`
-
-19. Close the DefaultApp.osd file, and save the changes.
-
-**To stream the default application**
-
-1. On the computer that has the App-V Client installed, log on as a user who is a member of the Application Virtualization Users group specified during server installation.
-
-2. On the desktop, the **Default Application Virtualization Application** shortcut appears. Double-click the shortcut to start the application.
-
-3. A status bar, displayed above the Windows notification area, reports that the application is starting. If the application startup is successful, the title screen for the default application is displayed. Click **OK** to close the dialog box. You have now confirmed that the App-V system is running correctly.
-
-## Related topics
-
-
-[How to Configure Servers for Server-Based Deployment](how-to-configure-servers-for-server-based-deployment.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-install-application-virtualization-management-server.md b/mdop/appv-v4/how-to-install-application-virtualization-management-server.md
deleted file mode 100644
index 9fff92bc25..0000000000
--- a/mdop/appv-v4/how-to-install-application-virtualization-management-server.md
+++ /dev/null
@@ -1,123 +0,0 @@
----
-title: How to Install Application Virtualization Management Server
-description: How to Install Application Virtualization Management Server
-author: dansimp
-ms.assetid: 8184be79-8c27-4328-a3c1-183791b5556c
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Install Application Virtualization Management Server
-
-
-The Application Virtualization Management Server publishes its applications to clients. In a load-balanced environment, which is typical of large deployments, all servers in a server group should stream the same applications. If Application Virtualization Management Servers are to publish different applications, assign the servers to different server groups. In this case, you also might need to increase a server group's capacity.
-
-If you have designated a target computer on the network, with a login account having local Administrator privileges, you can use the following procedure to install the Application Virtualization Management Server and assign it to the appropriate server group.
-
-**Note**
-The Installation Wizard can create a server group record, if one does not exist, as well as a record of the Application Virtualization Management Server's membership in this group.
-
-
-
-After you complete the installation process, reboot the server.
-
-**To install an Application Virtualization Management Server**
-
-1. Verify and, if necessary, uninstall previous versions of the Application Virtualization Management Server that are installed on the target computer.
-
-2. To open the **Microsoft Application Virtualization Management Server installation** wizard, navigate to the location of the Application Virtualization System **setup.exe** program on the network, either run this program from the network or copy its directory to the target computer, and then double-click the **Setup.exe** file.
-
-3. On the **Welcome** page, click **Next**.
-
-4. On the **License Agreement** page, read the license agreement and, to accept the license agreement, select **I accept the license terms and conditions**. Click **Next**.
-
-5. On the **Registering Information** page, you must enter the user name and the **Organization**. Click **Next**.
-
-6. On the **Setup Type** page, select **Custom**. Click **Next**. On the **Custom Setup** page, deselect all Application Virtualization System components except **Application Virtualization Server**, and then click **Next**.
-
- **Caution**
- If a component is already installed on the computer, when you deselect it in the **Custom Setup** window, the component is automatically uninstalled.
-
-
-
-7. On the **Configuration Database** page, select a database server from the list of available servers or add a server by selecting **Use the following host name** and specifying the **Server Name** and **Port Number** data. Click **Next**.
-
- **Note**
- The Application Virtualization Management Server does not support case sensitive SQL.
-
-
-
-~~~
-If a database is available, click the radio button, select the database from the list, and then click **Next**. Setup will upgrade it to this newer version. If the name does not appear in the list, enter the name in the space provided.
-
-**Note**
-When naming a server, do not use the backslash character (/) in the server name.
-
-If you need to install a database, see [How to Install a Database](how-to-install-a-database.md). If you would like to create a new database for this version, select **Create a new database** and specify the name that will be assigned to the new database. You can also specify a new location for the database by selecting the check box and entering the path.
-~~~
-
-
-
-8. On the **Connection Security Mode** page, select the desired certificate from the drop-down list. Click **Next**.
-
- **Note**
- The **Secure Connection Mode** setting requires the server to have a server certificate provisioned to it from a public key infrastructure. If a server certificate is not installed on the server, this option is unavailable and cannot be selected. You must grant the Network Service account read access to the certificate being used.
-
-
-
-9. On the **TCP Port Configuration** page, to use the default port (554), select **Use default port (554)**. To specify a custom port, select **Use custom port** and specify the port number that will be used. Click **Next**.
-
- **Note**
- When you install the server in a nonsecure environment, you can use the default port (554) or you can define a custom port.
-
-
-
-10. On the **Administrator Group** page, specify the name of the security group authorized to manage this server in **Group Name**. Click **Next**. Confirm the group specified and click **Next**.
-
-11. On the **Default Provider Group** page, specify the name of the default provider group, and then click **Next**.
-
-12. On the **Content Path** page, specify the location on the target computer where SFT files will be saved, and then click **Next**.
-
- **Note**
- If the HTTP or RTSP port for the Management Server is already allocated, you will be prompted to choose a new port. Select the desired port, and then click **Next**.
-
-
-
-13. On the **Ready to Install the Program** page, to install the Application Virtualization Management Server, click **Install**.
-
- **Note**
- If error 25120 is displayed when you try to complete this step, you need to enable IIS **Management Scripts and Tools**. To enable this Windows feature, open the **Programs and Features** control panel, select **Turn Windows features on or off**, and navigate to **Internet Information Services.**
-
- Under **Web Management Tools**, enable **IIS Management Scripts and Tools**.
-
-
-
-14. On the **Installation Wizard Completed** screen, to close the wizard, click **Finish**.
-
- **Important**
- The installation can take a few minutes to finish. A status message will flash above the Windows desktop notification area, indicating that the installation succeeded.
-
- It is not necessary to reboot the computer when prompted. However, to optimize system performance, a reboot is recommended.
-
-
-
-## Related topics
-
-
-[How to Install the Servers and System Components](how-to-install-the-servers-and-system-components.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-install-the-app-v-client-by-using-setupexe-new.md b/mdop/appv-v4/how-to-install-the-app-v-client-by-using-setupexe-new.md
deleted file mode 100644
index 37596836cd..0000000000
--- a/mdop/appv-v4/how-to-install-the-app-v-client-by-using-setupexe-new.md
+++ /dev/null
@@ -1,59 +0,0 @@
----
-title: How to Install the App-V Client by Using Setup.exe
-description: How to Install the App-V Client by Using Setup.exe
-author: dansimp
-ms.assetid: 106a5d97-b5f6-4a16-bf52-a84f4d558c74
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Install the App-V Client by Using Setup.exe
-
-
-This topic describes how to install the App-V client by using the setup.exe program. When you install the App-V client using the setup.exe program, the installer determines which prerequisite software is needed and installs it automatically before it installs the client.
-
-**To install the Application Virtualization Client by Using Setup.exe**
-
-1. Make sure you are logged on with an account that has administrator rights on the computer.
-
-2. Open a Command Prompt window, and then change the directory to the folder that contains the setup files. When installing version 4.6 or a later version of the App-V client, you must use the correct installer for the computer’s operating system, 32-bit or 64-bit. The installation will fail and an error message will be displayed if you use the wrong installer.
-
-3. Enter the install command string at the command prompt. Alternatively, you can create a command file and run it from the command prompt. You can also use a scripting language such as VBScript or Windows PowerShell to run the command.
-
-4. The following command-line example shows how setup.exe can be used with a number of optional parameters. For more information about these parameters, see [Application Virtualization Client Installer Command-Line Parameters](application-virtualization-client-installer-command-line-parameters.md).
-
- **"setup.exe" /s /v"/qn SWICACHESIZE=\\"10240\\" SWIPUBSVRDISPLAY=\\"Production System\\" SWIPUBSVRTYPE=\\"HTTP /secure\\" SWIPUBSVRHOST=\\"PRODSYS\\" SWIPUBSVRPORT=\\"443\\" SWIPUBSVRPATH=\\"/AppVirt/appsntype.xml\\" SWIPUBSVRREFRESH=\\"on\\" SWIGLOBALDATA=\\"D:\\AppVirt\\Global\\" SWIUSERDATA=\\"^% LOCALAPPDATA ^%\\Windows\\Application Virtualization Client\\" SWIFSDRIVE=\\"Q\\""**
-
- **Important**
- - The quotation marks that appear in the "**/v**" section must be treated as special characters and entered with a preceding "**\\**". The quotation marks are required only when the value contains a space; however, for consistency, all the instances in the preceding example are shown as having quotation marks.
-
- - The "**%**" characters in "**%HomeDrive%**" must be preceded by the "**^**" escape character. Otherwise, the Windows command shell sets the value to that of the user who is performing the installation.
-
- - The **InstallShield** switches **/s** and **/qn** are needed to make this a silent install. The **/qn** switch must follow the **/v** switch, separated by only a quote character with no intervening spaces.
-
- - The folder specified in the **SWIGLOBALDATA** value must already exist.
-
-
-
-5. When the installation is complete, we recommend that you run a Microsoft Update scan to ensure the latest updates are installed.
-
-## Related topics
-
-
-[How to Install the Client by Using the Command Line](how-to-install-the-client-by-using-the-command-line-new.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-install-the-app-v-client-by-using-setupmsi-new.md b/mdop/appv-v4/how-to-install-the-app-v-client-by-using-setupmsi-new.md
deleted file mode 100644
index 5485cfe6f6..0000000000
--- a/mdop/appv-v4/how-to-install-the-app-v-client-by-using-setupmsi-new.md
+++ /dev/null
@@ -1,187 +0,0 @@
----
-title: How to Install the App-V Client by Using Setup.msi
-description: How to Install the App-V Client by Using Setup.msi
-author: dansimp
-ms.assetid: 7221f384-36d6-409a-94a2-86f54fd75322
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 08/30/2016
----
-
-
-# How to Install the App-V Client by Using Setup.msi
-
-
-This topic describes how to install the App-V client by using the setup.msi program. Before you install the App-V client using the setup.msi program, you must first determine if any prerequisite software must be installed, and then you must install it. To install the prerequisite software, see the [Installing Prerequisite Software](#prereq-sw) section of this topic. To install the client software, see the [Installing the App-V Client Using the Setup.msi Program](#msi-setup) section of this topic.
-
-## Installing Prerequisite Software
-
-
-You can use the following procedures to install the prerequisite software. You can create a command file and run the commands from the command prompt, or you can use a scripting language such as VBScript or Windows PowerShell to run the commands.
-
-**Note**
-The x86 versions of the following software are required for both x86 and x64 versions of the App-V client.
-
-
-
-**To install Microsoft Visual C++ 2005 SP1 Redistributable Package (x86)**
-
-1. Download the [Microsoft Visual C++ 2005 SP1 Redistributable Package (x86)](https://go.microsoft.com/fwlink/?LinkId=119961) software package from the Microsoft Download Center (). \[Template Token Value\] For version 4.5 SP2 and later of the App-V client, download vcredist\_x86.exe from [Microsoft Visual C++ 2005 Service Pack 1 Redistributable Package ATL Security Update](https://go.microsoft.com/fwlink/?LinkId=169360) (https://go.microsoft.com/fwlink/?LinkId=169360).\[Template Token Value\]
-
-2. To install silently, use the command-line option “/Q” with vcredist\_x86.exe—for example, **vcredist\_x86.exe /Q**.
-
-3. To install the software by using the vcredist\_x86.msi file, use the command-line option “/C /T:<fullpathtofolder>” to extract the files vcredist.msi and vcredis1.cab from vcredist\_x86.exe to a temporary folder. To install silently, use the command-line option /quiet—for example, **msiexec /i vcredist.msi** /quiet.
-
-### To install Microsoft Visual C++ 2008 SP1 Redistributable Package (x86)
-
-**Important**
-For version 4.6 and later of the App-V client, you must also install the Microsoft Visual C++ 2008 Service Pack 1 Redistributable Package ATL Security Update.
-
-
-
-****
-
-1. Download the [Microsoft Visual C++ 2008 Service Pack 1 Redistributable Package ATL Security Update](https://go.microsoft.com/fwlink/?LinkId=150700) software package from the Microsoft Download Center (https://go.microsoft.com/fwlink/?LinkId=150700).
-
-2. To install silently, use the command-line option “/Q” with vcredist\_x86.exe—for example, **vcredist\_x86.exe /Q**.
-
-### To install Microsoft Core XML Services (MSXML) 6.0 SP1 (x86)
-
-****
-
-1. Download the [Microsoft Core XML Services (MSXML) 6.0 SP1 (x86)](https://go.microsoft.com/fwlink/?LinkId=63266) software package from the Microsoft Download Center (https://go.microsoft.com/fwlink/?LinkId=63266).
-
-2. To install silently, use the command-line option /quiet—for example, **msiexec /i msxml6\_x86.msi /quiet**.
-
-### To install Microsoft Application Error Reporting
-
-When installing Microsoft Application Error Reporting, you must use the *APPGUID* parameter to specify the App-V product code. The product code is unique for each App-V client type and version. Select the correct product code from the following table.
-
-**Important**
-For App-V 4.6 SP2 and later, you no longer need to install Microsoft Application Error Reporting (dw20shared.msi). App-V now uses Microsoft Error Reporting.
-
-
-
-
-
-
-
-
-
-
-
-
Version
-
Product Code for Desktop Client
-
Product Code for Client for Remote Desktop Services
-
-
-
-
-
App-V 4.5 CU1
-
FE495DBC-6D42-4698-B61F-86E655E0796D
-
8A97C241-D92A-47DC-B360-E716C1AAA929
-
-
-
App-V 4.5 SP1
-
93468B43-C19D-44F9-8BCC-114076DB0443
-
0042AD3C-99A4-4E58-B5F0-744D5AD96E1C
-
-
-
App-V 4.5 SP2
-
C6FC75B9-7D86-4C44-8BDB-EAFE1F0E200D
-
ECF80BBA-CA07-4A74-9ED6-E064F38AF1F5
-
-
-
App-V 4.6 x86
-
9E9D30B2-2065-4FDE-B756-8F1A6EABAFC3
-
439FAC21-B423-41D4-8126-54F9FCB70039
-
-
-
App-V 4.6 x64
-
E569E45F-7BA6-4C7F-B6BA-3FFCBE92FC22
-
D2977C18-D88A-47CB-AFD8-652DD36F4D0D
-
-
-
App-V 4.6 x86 ¹
-
40C3258B-F9D1-46DF-AE97-72C1F86F2427
-
9915D911-CC73-4122-AF4F-564F89454655
-
-
-
App-V 4.6 x64 ¹
-
1650E31F-23B8-40B5-A60A-C5934F557E3B
-
7580D918-C621-49E7-9877-3CC59F9BD1DA
-
-
-
App-V 4.6 x86 SP1
-
DB9F70CD-29BC-480B-8BA2-C9C2232C4553
-
1354855A-2298-4C73-9022-EF0686C65991
-
-
-
App-V 4.6 x64 SP1
-
342C9BB8-65A0-46DE-AB7A-8031E151AF69
-
B2C6C8D5-FE76-4056-A326-EE5D633EA175
-
-
-
-
-
-
-¹ App-V “Languages” release.
-
-**Note**
-If you need to find the product code, you can use the Orca.exe database editor or a similar tool to examine Windows Installer files to find the value of the *ProductCode* property. For more information about using Orca.exe, see [Windows Installer Development Tools](https://go.microsoft.com/fwlink/?LinkId=150008) (https://go.microsoft.com/fwlink/?LinkId=150008).
-
-
-
-****
-
-1. Locate the Microsoft Application Error Reporting install program, dw20shared.msi, which can be found in the **Support\\Watson** folder on the release media.
-
-2. To install the software, run the following command:
-
- **msiexec /i dw20shared.msi APPGUID={valuefromtable} REBOOT=Suppress REINSTALL=ALL REINSTALLMODE=vomus**
-
-## Installing the App-V Client by Using the Setup.msi Program
-
-
-Use the following procedure to install the App-V client. Ensure that any necessary prerequisite software has been installed. \[Template Token Value\] For version 4.6 and later of the App-V client, the setup.msi program checks the system and if prerequisite software is not installed, it generates an error message indicating that installation cannot continue. \[Template Token Value\]
-
-**To install the Application Virtualization Client by Using Setup.msi**
-
-1. Make sure you are logged on with an account that has administrator rights on the computer.
-
-2. Open a Command Prompt window by using elevated rights, and then change the directory to the folder that contains the setup files. When installing version 4.6 or a later version of the App-V client, you must use the correct installer for the computer’s operating system, 32-bit or 64-bit. The installation will fail and an error message will be displayed if you use the wrong installer.
-
-3. Enter the install command string at the command prompt. Alternatively, you can create a command file and run it from the command prompt. You can also use a scripting language such as VBScript or Windows PowerShell to run the command.
-
-4. The following command-line example shows how setup.msi can be used with a number of optional parameters. For more information about these parameters, see [Application Virtualization Client Installer Command-Line Parameters](application-virtualization-client-installer-command-line-parameters.md).
-
- **msiexec.exe /i "setup.msi" SWICACHESIZE="10240" SWIPUBSVRDISPLAY="Production System" SWIPUBSVRTYPE="HTTP /secure" SWIPUBSVRHOST="PRODSYS" SWIPUBSVRPORT="443" SWIPUBSVRPATH="/AppVirt/appsntype.xml" SWIPUBSVRREFRESH="on" SWIGLOBALDATA="D:\\AppVirt\\Global" SWIUSERDATA="^% LOCALAPPDATA^%\\Windows\\Application Virtualization Client" SWIFSDRIVE="S" /q**
-
- **Important**
- - The Windows Installer switch "**/q**" is used to make this a silent installation.
-
- - The "**%**" characters in "**%HomeDrive%**" must be preceded by the "**^**" escape character. Otherwise, the Windows command shell sets the value to that of the user who is performing the installation.
-
- - To turn on installation logging, use the msiexec switch **/l\*v filename.log**.
-
-
-
-## Related topics
-
-
-[How to Install the Client by Using the Command Line](how-to-install-the-client-by-using-the-command-line-new.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-install-the-application-virtualization-sequencer.md b/mdop/appv-v4/how-to-install-the-application-virtualization-sequencer.md
deleted file mode 100644
index 5cf9e908d7..0000000000
--- a/mdop/appv-v4/how-to-install-the-application-virtualization-sequencer.md
+++ /dev/null
@@ -1,59 +0,0 @@
----
-title: How to Install the Application Virtualization Sequencer
-description: How to Install the Application Virtualization Sequencer
-author: dansimp
-ms.assetid: 89cdf60d-18b0-4204-aa9f-b402610f8f0e
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Install the Application Virtualization Sequencer
-
-
-The Microsoft Application Virtualization Sequencer monitors and records the installation and setup process for applications so that the application can be run as a virtual application. You should install the Sequencer on a computer that has only the operating system installed. Alternatively, you can install the Sequencer on a computer running a virtual environment—for example, Microsoft Virtual PC. This method is useful because it is easier to maintain a clean sequencing environment that can be reused with minimal additional configuration.
-
-You must have administrative rights on the computer you are using to sequence the application and the computer must not be running any version of the Application Virtualization (App-V) client. Creating a virtual application by using the Sequencer is very resource intensive, so it is important that you install the Sequencer on a computer that meets or exceeds the recommended requirements. Running the App-V sequencer in Safe Mode is not supported. For more information about the system requirements, see [Application Virtualization System Requirements](application-virtualization-system-requirements.md).
-
-**Important**
-After you have sequenced an application, before you can properly sequence a new application you must reinstall the operating system and the Sequencer on the computer you are using to sequence applications.
-
-
-
-**To install the Microsoft Application Virtualization Sequencer**
-
-1. Copy the Microsoft Application Virtualization Sequencer installation files to the computer that you want to install it on.
-
-2. To start the Microsoft Application Virtualization Sequencer installation wizard, select **setup.exe**. If the **Microsoft Visual C++ SP1 Redistributable Package (x86)** is not detected prior to installation, **setup.exe** will install it.
-
-3. On the **Welcome** page, click **Next**.
-
-4. On the **License Agreement** page, to accept the terms of the license agreement, select **I accept the terms in the license agreement**. Click **Next**.
-
-5. On the **Destination Folder** page, to accept the default installation folder, click **Next**. To specify a different destination folder, click **Change** and specify the installation folder that will be used for the installation. Click **Next**.
-
-6. On the **Ready to Install the Program** page, to start the installation, click **Install**.
-
-7. On the **InstallShield Wizard Completed** page, to close the installation wizard and open the Sequencer, click **Finish**. To close the installation wizard without opening the Sequencer, deselect **Launch the program** and click **Finish**.
-
-## Related topics
-
-
-[How to Upgrade the Application Virtualization Sequencer](how-to-upgrade-the-application-virtualization-sequencer.md)
-
-[Application Virtualization Deployment Requirements](application-virtualization-deployment-requirements.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-install-the-application-virtualization-streaming-server.md b/mdop/appv-v4/how-to-install-the-application-virtualization-streaming-server.md
deleted file mode 100644
index b6facad249..0000000000
--- a/mdop/appv-v4/how-to-install-the-application-virtualization-streaming-server.md
+++ /dev/null
@@ -1,123 +0,0 @@
----
-title: How to Install the Application Virtualization Streaming Server
-description: How to Install the Application Virtualization Streaming Server
-author: dansimp
-ms.assetid: a3065257-fb5a-4d92-98f8-7ef996c61db9
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Install the Application Virtualization Streaming Server
-
-
-The Application Virtualization Streaming Server publishes its applications to clients. In a load-balanced environment, which is typical of large deployments, all servers in a server group should stream the same applications. If Application Virtualization Streaming Servers are to stream different applications, assign the servers to different server groups. In this case, you might also have to increase a server group's capacity.
-
-If you have designated a target computer on the network, with a logon account having local administrative privileges, you can use the following procedure to install the Application Virtualization Streaming Server and assign it to the appropriate server group.
-
-**Note**
-The Installation Wizard can create a server group record, if one does not exist, and a record of the Application Virtualization Streaming Server membership in this group.
-
-
-
-After you complete the installation process, restart the server.
-
-**To install an Application Virtualization Streaming Server**
-
-1. Verify that no earlier versions of the Application Virtualization Streaming Server are installed on your target computer.
-
- **Important**
- Make sure that the App-V Management Server is not installed on this computer. The two products cannot be installed on the same computer.
-
-
-
-2. Navigate to the location of the Application Virtualization System Setup program on the network, either run this program from the network or copy its directory to the target computer, and then double-click the **Setup.exe** file.
-
-3. On the **Welcome** page, click **Next**.
-
-4. On the **License Agreement** page, to accept the license terms, select **I accept the licensing terms and conditions**, and then click **Next**.
-
-5. On the **Customer Information** page, specify the **User name** and the organization, and then click **Next**.
-
-6. On the **Installation Path** page, click **Browse**, specify the location where you want to install the Streaming Server, and then click **Next**.
-
-7. On the **Connection Security Mode** page, select the desired certificate from the drop-down list, and then click **Next**.
-
- **Note**
- The **Secure Connection Mode** setting requires the server to have a server certificate provisioned to it from a public key infrastructure. If a server certificate is not installed on the server, this option is unavailable and cannot be selected. You must grant the Network Service account read access to the certificate being used.
-
-
-
-8. On the **TCP Port Configuration** page, to use the standard port (554), select **Use default port (554)**. To specify a custom port, select **Use custom port**, specify the port number in the field provided, and then click **Next**.
-
- **Note**
- When you install the server in a nonsecure scenario, you can use the default port (554), or you can define a custom port.
-
-
-
-9. On the **Content Root** page, specify the location on the target computer where SFT files will be saved, and then click **Next**.
-
- **Note**
- If the HTTP or RTSP port for the Virtual Application Streaming Server is already allocated, you will be prompted to select a new port. Specify the desired port, and then click **Next**.
-
-
-
-10. On the **Advanced Setting** screen, enter the following information:
-
- 1. **Max client connections**
-
- 2. **Connection timeout (sec)**
-
- 3. **RTSP thread pool size**
-
- 4. **RTSP timeout (sec)**
-
- 5. **Number of core processes**
-
- 6. **Core timeout (sec)**
-
- 7. **Enable User authentication**
-
- 8. **Enable User authorization**
-
- 9. **Cache block size (KB)**
-
- 10. **Maximum cache size (MB)**
-
- **Note**
- The App-V Streaming Server uses NTFS file system permissions to control access to the applications under the Content share. Use **Enable User authentication** and **Enable User authorization** to control whether the server checks and enforces those access control lists (ACLs) or not.
-
-
-
-11. On the **Ready to Install the Program** page, to start the installation, click **Install**.
-
-12. On the **Installation Wizard Completed** screen, to close the wizard, click **Finish**.
-
- **Important**
- The installation can take several minutes to finish. A status message will flash above the Windows desktop notification area, indicating that the installation succeeded.
-
- It is not required to restart the computer when you are prompted. However, to optimize system performance, we recommend a restart.
-
-
-
-13. Repeat Steps 1–12 for each Virtual Application Server that you have to install.
-
-## Related topics
-
-
-[How to Install the Servers and System Components](how-to-install-the-servers-and-system-components.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-install-the-client-by-using-the-command-line-new.md b/mdop/appv-v4/how-to-install-the-client-by-using-the-command-line-new.md
deleted file mode 100644
index 69e3331059..0000000000
--- a/mdop/appv-v4/how-to-install-the-client-by-using-the-command-line-new.md
+++ /dev/null
@@ -1,74 +0,0 @@
----
-title: How to Install the Client by Using the Command Line
-description: How to Install the Client by Using the Command Line
-author: dansimp
-ms.assetid: ed372403-64ff-48ff-a3cd-a46cad04a4d5
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 08/30/2016
----
-
-
-# How to Install the Client by Using the Command Line
-
-
-The topics in this section include procedures to install either the Application Virtualization (App-V) Desktop Client or the App-V Client for Remote Desktop Services (formerly Terminal Services) by using either setup.exe or setup.msi. Administrative rights are required to run either setup program.
-
-You can use optional command-line parameters to apply specific configuration settings to the App-V client during the installation. For more information about using parameters, see [Application Virtualization Client Installer Command-Line Parameters](application-virtualization-client-installer-command-line-parameters.md). If you have applied registry settings to a computer before deploying a client—for example, by using Group Policy—these settings are retained and any additional command line parameters are applied. Command line parameter values will replace any existing value for the same setting.
-
-**Note**
-When you install the App-V client to use with a read-only cache, for example with a VDI server implementation, you must set the *AUTOLOADTARGET* parameter to NONE to prevent the client from trying to update applications when the cache is read-only.
-
-
-
-For more information about setting these parameter values after installation, see [How to Configure the App-V Client Registry Settings by Using the Command Line](https://go.microsoft.com/fwlink/?LinkId=169355) (https://go.microsoft.com/fwlink/?LinkId=169355) in the Application Virtualization (App-V) Operations Guide.
-
-**Note**
-If a configuration setting on the user’s computer depends on the client installation path, note that the Application Virtualization (App-V) 4.5 client copies its installation files to a different folder than previous versions did. By default, a new installation of the App-V 4.5 client will copy its installation files to the \\Program Files\\Microsoft Application Virtualization Client folder. If an earlier version of the client is already installed, running the App-V 4.5 client installer will perform an upgrade of the existing client using the existing installation folder.
-
-
-
-\[Template Token Value\]
-
-**Note**
-For App-V version 4.6 and later, when the App-V client is installed, SFTLDR.DLL is copied to the Windows\\system32 directory. If the App-V client is installed on a 64-bit system, SFTLDR\_WOW64.DLL is copied to the Windows\\SysWOW64 directory.
-
-
-
-\[Template Token Value\]
-
-## In This Section
-
-
-The following topics describe how to install either the Application Virtualization (App-V) Desktop Client or the App-V Client for Remote Desktop Services (formerly Terminal Services) by using either setup.exe or setup.msi.
-
-[How to Install the App-V Client by Using Setup.exe](how-to-install-the-app-v-client-by-using-setupexe-new.md)
-Provides a step-by-step procedure for installing the App-V client by using the setup.exe program.
-
-[How to Install the App-V Client by Using Setup.msi](how-to-install-the-app-v-client-by-using-setupmsi-new.md)
-Provides step-by-step procedures for installing any prerequisite software and also the App-V client by using the setup.msi program.
-
-## Related topics
-
-
-[Application Virtualization Client Installer Command-Line Parameters](application-virtualization-client-installer-command-line-parameters.md)
-
-[How to Manually Install the Application Virtualization Client](how-to-manually-install-the-application-virtualization-client.md)
-
-[How to Publish a Virtual Application on the Client](how-to-publish-a-virtual-application-on-the-client.md)
-
-[How to Uninstall the App-V Client](how-to-uninstall-the-app-v-client.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-install-the-management-console.md b/mdop/appv-v4/how-to-install-the-management-console.md
deleted file mode 100644
index df74e0f969..0000000000
--- a/mdop/appv-v4/how-to-install-the-management-console.md
+++ /dev/null
@@ -1,74 +0,0 @@
----
-title: How to Install the Management Console
-description: How to Install the Management Console
-author: dansimp
-ms.assetid: 586d99c8-bca6-42e2-a39c-a696053142f1
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Install the Management Console
-
-
-You can use the following procedure to install the Application Virtualization Management Console on a target computer on the network. You must use a network account that has administrator privileges on the target computer. You can use the console to configure and manage the Application Virtualization System Platform.
-
-Before you can complete this procedure, you must install the Application Virtualization Management Web Service on this or a different computer. The Management Web Service allows you to access the data store and the domain controller. For more information about installing the Web service, see [How to Install the Management Web Service](how-to-install-the-management-web-service.md).
-
-**To install the Management Console**
-
-1. Verify that no previous versions of the Management Console are installed on the target computer.
-
-2. Navigate to the location of the Application Virtualization System setup program on the network, either run this program from the network or copy its directory to the target computer, and then double-click **Setup.exe**.
-
-3. On the **Welcome Page**, click **Next**.
-
-4. On the **License Agreement** page, to accept the license agreement, select **I accept the license terms and conditions**, and then click **Next**.
-
-5. On the **Registration Information** page, specify the **User Name** and **Organization** information, and then click **Next**.
-
-6. On the **Setup Type** page, click **Custom** and then click **Next**.
-
-7. On the **Custom Setup** page, deselect all Application Virtualization System components except **Management Console**, and then click **Next**.
-
- **Note**
- If a component is already installed on the computer, by deselecting it on the Custom Setup screen, it will automatically be uninstalled.
-
-
-
-8. On the **Ready to Modify the Program** screen, click **Install**.
-
- **Note**
- If this is the first component you install, the **Ready to Install the Program** page is displayed. To start the installation, click **Install**.
-
-
-
-9. On the **Installation Wizard Completed** screen, click **Finish**. Click **Okay** to restart the computer and complete the installation.
-
-10. In the Windows Control Panel, double-click **Administrative Tools** and then click **Application Virtualization Management Console** to display the Management Console.
-
-11. Click the **Connect** icon, or right-click the **Application Virtualization Systems** container, and then click **Connect to Application Virtualization System**.
-
-12. On the **Connect to Application Virtualization System** screen, enter the host name and port of the Management Web Service computer, change the security information and login credentials if necessary, and then click **OK**.
-
-13. After connecting to the Management Web Service computer, click **File** on the **Console** menu, and then click **Exit**. Click **Yes** to save console settings.
-
-## Related topics
-
-
-[How to Install the Servers and System Components](how-to-install-the-servers-and-system-components.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-install-the-management-web-service.md b/mdop/appv-v4/how-to-install-the-management-web-service.md
deleted file mode 100644
index 72f0d59456..0000000000
--- a/mdop/appv-v4/how-to-install-the-management-web-service.md
+++ /dev/null
@@ -1,84 +0,0 @@
----
-title: How to Install the Management Web Service
-description: How to Install the Management Web Service
-author: dansimp
-ms.assetid: cac296f5-8ca0-4ce7-afdb-859ae207d2f1
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Install the Management Web Service
-
-
-Use the following procedure to install the Application Virtualization Management Web Service on a target computer on the network, with a logon account having local administrative privileges. Although it is not required, we recommended that you install this component on your Web server.
-
-**To install the Management Web Service**
-
-1. Verify that no previous versions of the Application Virtualization Web Service are installed on your target computer.
-
-2. Navigate to the location of the Application Virtualization System setup program on the network, either run this program from the network or copy its directory to the target computer, and then double-click **Setup.exe**.
-
-3. After the Installation Wizard opens, on the **Welcome** page, click **Next**.
-
-4. On the **License Agreement** page, to accept the license agreement, select **I accept the license terms and conditions**, and then click **Next**.
-
-5. On the **Registration Information** page, specify the **User Name** and organization information, and then click **Next**.
-
-6. On the **Setup Type** page, click **Custom**, and then click **Next**.
-
- **Note**
- If this is not the first component you installed on this computer, the **Program Maintenance** page is displayed. On the **Program Maintenance** page, click **Modify**.
-
-
-
-7. On the **Custom Setup** page, clear all Application Virtualization System components except **App Virt Management Service**, and then click **Next**.
-
- **Note**
- If a component is already installed on the computer, by clearing it on the **Custom Setup** page, you will automatically uninstall it.
-
-
-
-8. On the **Database Server** page, click **Connect to available database**, and then click **Next**.
-
- **Note**
- In a production environment, Microsoft assumes that you will connect to an existing database. If you want to install a database, see [How to Install a Database](how-to-install-a-database.md). After installing the database, continue with step 13.
-
-
-
-9. On the **Database Server Type** page, select a database type from the list, and then click **Next**.
-
-10. On the **Database Server Location** page, select a database server from the list of available servers or add a server by selecting the **Use the following host name** check box and entering information in the **Server Name** and **Port Number** boxes, and then click **Next**.
-
-11. On the **Select Database** page, select the database you want, and then click **Next**.
-
-12. On the **Database User Configuration** page, enter the credentials that the Management Web Service will use to access the data store, and then click **Next**.
-
-13. On the **Ready to Modify the Program** page, click **Install**.
-
- **Note**
- If this is the first component you install, the **Ready to Install the Program** page is displayed. On the page, click **Install**.
-
-
-
-14. On the **Installation Wizard Completed** page, click **Finish**.
-
-## Related topics
-
-
-[How to Install the Servers and System Components](how-to-install-the-servers-and-system-components.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-install-the-sequencer---app-v-46-sp1-.md b/mdop/appv-v4/how-to-install-the-sequencer---app-v-46-sp1-.md
deleted file mode 100644
index ea900036a2..0000000000
--- a/mdop/appv-v4/how-to-install-the-sequencer---app-v-46-sp1-.md
+++ /dev/null
@@ -1,81 +0,0 @@
----
-title: How to Install the Sequencer (App-V 4.6 SP1)
-description: How to Install the Sequencer (App-V 4.6 SP1)
-author: dansimp
-ms.assetid: fe8eb876-28fb-46ae-b592-da055107e639
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Install the Sequencer (App-V 4.6 SP1)
-
-
-The Microsoft Application Virtualization (App-V) Sequencer monitors and records the installation and setup process for applications so that the application can be run as a virtual application. You should install the App-V Sequencer on a computer that has only the operating system installed. Alternatively, you can install the Sequencer on a computer running in a virtual environment, for example, a virtual computer. This method is useful because it is easier to maintain a clean sequencing environment that you can reuse with minimal additional configuration.
-
-You must have administrative credentials on the computer you are using to sequence the application, and the computer must not be running any version of App-V client. Creating a virtual application by using the App-V Sequencer requires multiple operations, so it is important that you install the Sequencer on a computer that meets or exceeds the [Application Virtualization Sequencer Hardware and Software Requirements](application-virtualization-sequencer-hardware-and-software-requirements.md).
-
-**Note**
-Running the App-V sequencer in Safe Mode is not supported.
-
-
-
-**To install the Microsoft Application Virtualization Sequencer**
-
-1. Copy the Microsoft Application Virtualization Sequencer installation files to the computer on which you want to install it.
-
-2. To start the Microsoft Application Virtualization Sequencer installation wizard, double-click **Setup.exe**. If the **Microsoft Visual C++ SP1 Redistributable Package (x86)** is not detected prior to installation, click **Install** to install the required prerequisite.
-
-3. To continue the installation, on the **Welcome** page, click **Next**.
-
-4. On the **License Agreement** page, to accept the terms of the license agreement, click **I accept the terms in the license agreement**, and then click **Next**.
-
-5. On the **Destination Folder** page, to accept the default installation folder, click **Next**. To specify a different destination folder, click **Change** and specify the installation folder that will be used for the installation. Click **Next**.
-
-6. On the **Virtual Drive** page, to configure the Application Virtualization default drive **Q:\\** (default) as the drive that all sequenced applications will run from, click **Next**. If you want to specify a different drive letter, use the list and select the drive letter that you want to use by selecting the appropriate drive letter, and then click **Next**.
-
- **Important**
- The Application Virtualization drive letter specified with this step is the drive letter that virtual applications will be run from on target computers. The drive letter specified must be available, and not currently in use on the computers running the App-V client. If the specified drive is already in use, the virtual application fails on the target computer.
-
-
-
-7. On the **Ready to Install the Program** page, to start the installation, click **Install**.
-
-8. On the **InstallShield Wizard Completed** page, to close the installation wizard and open the App-V Sequencer, click **Finish**. To close the installation wizard without opening the Sequencer, clear **Launch the program**, and then click **Finish**.
-
- **Note**
- If you installed the App-V Sequencer on a computer running a virtual environment, for example a virtual machine, you must now take a snapshot. After you sequence an application, you can revert to this image, so you can sequence the next application.
-
-
-
-~~~
-When you uninstall the Sequencer, the following registry keys are not removed from the computer that the Sequencer was installed on. Additionally, you must restart the computer after you have uninstalled the Sequencer so that all associated drivers can be stopped and the operation can be completed.
-
-- **HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Wow6432Node\\Microsoft\\SoftGrid**
-
-- **HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Wow6432Node\\Microsoft\\SoftGrid\\4.5**
-
-- **HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Wow6432Node\\Microsoft\\SoftGrid\\4.5\\SystemGuard**
-
-- **HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Wow6432Node\\Microsoft\\SoftGrid\\4.5\\SystemGuard\\SecKey**
-~~~
-
-## Related topics
-
-
-[Configuring the Application Virtualization Sequencer (App-V 4.6 SP1)](configuring-the-application-virtualization-sequencer--app-v-46-sp1-.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-install-the-sequencer.md b/mdop/appv-v4/how-to-install-the-sequencer.md
deleted file mode 100644
index decce9699a..0000000000
--- a/mdop/appv-v4/how-to-install-the-sequencer.md
+++ /dev/null
@@ -1,52 +0,0 @@
----
-title: How to Install the Sequencer
-description: How to Install the Sequencer
-author: dansimp
-ms.assetid: 2cd16427-a0ba-4870-82d1-3e3c79e1959b
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Install the Sequencer
-
-
-The Microsoft Application Virtualization (App-V) Sequencer monitors and records the installation and setup process for applications so that the application can be run as a virtual application. You should install the Sequencer on a computer that has only the operating system installed. Alternatively, you can install the Sequencer on a computer running a virtual environment—for example, Microsoft Virtual PC. This method is useful because it is easier to maintain a clean sequencing environment that can be reused with minimal additional configuration.
-
-You must have administrative rights on the computer you are using to sequence the application and the computer must be connected to the network. The computer must not be running any version of the Application Virtualization (App-V) client. Creating a virtual application using the Sequencer is very resource intensive, so it is important that you install the Sequencer on a computer that meets or exceeds the recommended requirements. For more information about the system requirements, see [Sequencer Hardware and Software Requirements](sequencer-hardware-and-software-requirements.md)..
-
-**To install the Microsoft Application Virtualization Sequencer**
-
-1. Copy the Microsoft Application Virtualization Sequencer installation files to the computer that you want to install it on.
-
-2. To start the Microsoft Application Virtualization Sequencer installation wizard, select **setup.exe**. If the **Microsoft Visual C++ SP1 Redistributable Package (x86)** is not detected prior to installation, **setup.exe** will install it.
-
-3. On the **Welcome** page, click **Next**.
-
-4. On the **License Agreement** page, to accept the terms of the license agreement, select **I accept the terms in the license agreement**. Click **Next**.
-
-5. On the **Destination Folder** page, to accept the default installation folder, click **Next**. To specify a different destination folder, click **Change** and specify the installation folder that will be used for the installation. Click **Next**.
-
-6. On the **Ready to Install the Program** page, to start the installation, click **Install**.
-
-7. On the **InstallShield Wizard Completed** page, to close the installation wizard and open the Sequencer, click **Finish**. To close the installation wizard without opening the Sequencer, deselect **Launch the program** and click **Finish**.
-
-## Related topics
-
-
-[Configuring the Application Virtualization Sequencer](configuring-the-application-virtualization-sequencer.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-install-the-servers-and-system-components.md b/mdop/appv-v4/how-to-install-the-servers-and-system-components.md
deleted file mode 100644
index d8d537d0e8..0000000000
--- a/mdop/appv-v4/how-to-install-the-servers-and-system-components.md
+++ /dev/null
@@ -1,64 +0,0 @@
----
-title: How to Install the Servers and System Components
-description: How to Install the Servers and System Components
-author: dansimp
-ms.assetid: c6f5fef0-522a-4ef1-8585-05b292d0289b
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Install the Servers and System Components
-
-
-Before you can deliver applications to users, you must install the Microsoft Application Virtualization Platform components. The topics in this section provide the information required to install the Application Virtualization Servers and the other Application Virtualization System components.
-
-**Note**
-The procedures in this section take you through a customized installation, where you pick and choose components to install on separate computers, as recommended in a production environment. However, your operating procedures might dictate a different approach, and during the installation process you might want to group components together. Regardless of where you install the components, you can install them in any order.
-
-
-
-## In This Section
-
-
-[How to Install Application Virtualization Management Server](how-to-install-application-virtualization-management-server.md)
-Provides a step-by-step procedure for installing the Application Virtualization Management Server and assigning it to the appropriate server group.
-
-[How to Install the Application Virtualization Streaming Server](how-to-install-the-application-virtualization-streaming-server.md)
-Provides a step-by-step procedure for installing the Application Virtualization Streaming Server and assigning it to the appropriate server group.
-
-[How to Install the Management Web Service](how-to-install-the-management-web-service.md)
-Provides a step-by-step procedure for installing the Application Virtualization Management Web Service on a target computer on your network.
-
-[How to Install the Management Console](how-to-install-the-management-console.md)
-Provides a step-by-step procedure for installing the Application Virtualization Management Console on a target computer on your network.
-
-[How to Install a Database](how-to-install-a-database.md)
-Provides a step-by-step procedure for installing a database for your server-based deployment of Application Virtualization, if a database is not already available.
-
-[How to Remove the Application Virtualization System Components](how-to-remove-the-application-virtualization-system-components.md)
-Provides step-by-step procedures to remove all or selected Application Virtualization software components from a target computer.
-
-## Related topics
-
-
-[Application Virtualization Server-Based Scenario Overview](application-virtualization-server-based-scenario-overview.md)
-
-[How to Configure Servers for Server-Based Deployment](how-to-configure-servers-for-server-based-deployment.md)
-
-[How to Upgrade the Servers and System Components](how-to-upgrade-the-servers-and-system-components.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-load-files-and-packages.md b/mdop/appv-v4/how-to-load-files-and-packages.md
deleted file mode 100644
index f70cbf6dc3..0000000000
--- a/mdop/appv-v4/how-to-load-files-and-packages.md
+++ /dev/null
@@ -1,58 +0,0 @@
----
-title: How to Load Files and Packages
-description: How to Load Files and Packages
-author: dansimp
-ms.assetid: f86f5bf1-99a4-44d7-ae2f-e6049c482f68
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Load Files and Packages
-
-
-You can use the following procedure to load files and packages on Application Virtualization Servers.
-
-**Note**
-During the installation process, you specified the location of the \\Content directory on the **Content Path** page. This directory should be created and configured as a standard file share before you point to its location.
-
-
-
-**To load files and packages**
-
-1. On the computer from which you will stream applications, navigate to the location that you specified for the \\Content directory. If necessary, create the directory and configure it as a standard file share.
-
-2. Move the SFT files for the virtual applications and packages to the \\Content directory. To keep the SFT files organized and to avoid confusion, put applications and packages in dedicated subfolders.
-
-3. Load the applications and packages according to the requirements of your scenario and configuration, considering the following conditions:
-
- - If your applications and packages are stored on an Application Virtualization (App-V) Management Server, load them through the Management Console. For more information, see [How to Load or Unload an Application](how-to-load-or-unload-an-application.md) or [How to Load Virtual Applications from the Desktop Notification Area](how-to-load-virtual-applications-from-the-desktop-notification-area.md).
-
- - If your applications are stored on an App-V Streaming Server, a Web server, or a computer configured as a file server, the applications can be automatically loaded.
-
- **Note**
- The App-V Streaming Server automatically polls the \\Content directory for applications and packages and puts this information in RAM to service application requests.
-
- The App-V Clients must be properly configured to retrieve applications and packages from Web servers and file servers. For more information, see [How to Configure the Client for Application Package Retrieval](how-to-configure-the-client-for-application-package-retrieval.md).
-
-
-
-## Related topics
-
-
-[Application Virtualization Server](application-virtualization-server.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-load-or-unload-an-application.md b/mdop/appv-v4/how-to-load-or-unload-an-application.md
deleted file mode 100644
index 5dd97091a1..0000000000
--- a/mdop/appv-v4/how-to-load-or-unload-an-application.md
+++ /dev/null
@@ -1,51 +0,0 @@
----
-title: How to Load or Unload an Application
-description: How to Load or Unload an Application
-author: dansimp
-ms.assetid: 8c149761-c591-433f-972b-91793a69c654
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Load or Unload an Application
-
-
-You can use the following procedures to load or unload an application from the cache, directly from the **Results** pane of the **Application** node in the Application Virtualization Client Management Console. When you select this node, the **Results** pane displays a list of applications.
-
-**Note**
-When you load or unload a package, all the applications in the package are loaded into or removed from cache. When loading a package, if you do not have adequate space in cache to load the applications, increase your cache size. For more information about cache size, see [How to Change the Cache Size and the Drive Letter Designation](how-to-change-the-cache-size-and-the-drive-letter-designation.md).
-
-
-
-**To load an application**
-
-1. Move the cursor to the **Results** pane, right-click the desired application, and select **Load** from the pop-up menu.
-
-2. The application is automatically loaded. The progress is tracked in the column labeled **Package Status**. You must refresh the view to see that the load is complete or to see the progress.
-
-**To unload an application**
-
-1. Move the cursor to the **Results** pane, right-click the desired application, and select **Unload** from the pop-up menu.
-
-2. The application is automatically unloaded, and the **Package Status** column is updated to reflect the change.
-
-## Related topics
-
-
-[How to Change the Cache Size and the Drive Letter Designation](how-to-change-the-cache-size-and-the-drive-letter-designation.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-load-virtual-applications-from-the-desktop-notification-area.md b/mdop/appv-v4/how-to-load-virtual-applications-from-the-desktop-notification-area.md
deleted file mode 100644
index c089ce97ab..0000000000
--- a/mdop/appv-v4/how-to-load-virtual-applications-from-the-desktop-notification-area.md
+++ /dev/null
@@ -1,59 +0,0 @@
----
-title: How to Load Virtual Applications from the Desktop Notification Area
-description: How to Load Virtual Applications from the Desktop Notification Area
-author: dansimp
-ms.assetid: f52758eb-8b81-4b3c-9bc3-adcf7c00c238
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Load Virtual Applications from the Desktop Notification Area
-
-
-If you are a mobile user, you might want to fully load your applications in the cache to use them during disconnected operation or offline mode. To stream applications from the Application Virtualization (App-V) Server or the Application Virtualization (App-V) Streaming Server, you must be connected to a server to load applications. If you are not connected to the server when you attempt to load applications, your system will generate an appropriate error message. You can also stream applications to the client from a file or disk.
-
-The applications are loaded one application at a time. The progress bar shows you the application name, the percentage of application loaded, and the number of applications already processed compared to the total number of the applications queued. You can skip any application in progress before it is 100% loaded. You can skip the loading of all remaining applications as well.
-
-**Note**
-If your system encounters an error while loading an application, it reports the error to you. You must dismiss the error dialog before it will load the next application.
-
-
-
-**To load all applications**
-
-1. Right-click the Application Virtualization System icon in the notification area.
-
-2. Select **Load Applications** from the pop-up menu.
-
-**To skip applications**
-
-1. Click the progress bar to display the dialog box.
-
-2. Select one of the following buttons to achieve the desired results:
-
- 1. **Skip**—To skip the currently loading application.
-
- 2. **Skip All**—To skip all remaining applications.
-
- 3. **Continue**—To cancel the dialog box and continue loading applications.
-
-## Related topics
-
-
-[How to Use the Desktop Notification Area for Application Virtualization Client Management](how-to-use-the-desktop-notification-area-for-application-virtualization-client-management.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-lock-or-unlock-an-application.md b/mdop/appv-v4/how-to-lock-or-unlock-an-application.md
deleted file mode 100644
index 1b2b033d69..0000000000
--- a/mdop/appv-v4/how-to-lock-or-unlock-an-application.md
+++ /dev/null
@@ -1,41 +0,0 @@
----
-title: How to Lock or Unlock an Application
-description: How to Lock or Unlock an Application
-author: dansimp
-ms.assetid: 8c65d4fd-f336-447f-8c0a-6d65aec9fd00
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Lock or Unlock an Application
-
-
-You can use the following procedures to lock or unlock any application in the Application Virtualization Desktop Client cache or the Client for Remote Desktop Services (formerly Terminal Services) cache. A locked application cannot be removed from the cache to make room for new applications. To remove a locked application from the Application Virtualization Desktop Client cache or the Client for Remote Desktop Services cache, you must first unlock it.
-
-**To lock an application**
-
-1. Move the cursor to the **Results** pane.
-
-2. Right-click the desired application, and select **Lock** from the pop-up menu. The selected application is locked in the cache.
-
-**To unlock an application**
-
-1. Move the cursor to the **Results** pane.
-
-2. Right-click the desired application, and select **Unlock** from the pop-up menu. The selected application is unlocked in the cache and can be removed.
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-manage-application-groups-in-the-server-management-console.md b/mdop/appv-v4/how-to-manage-application-groups-in-the-server-management-console.md
deleted file mode 100644
index a48df6078f..0000000000
--- a/mdop/appv-v4/how-to-manage-application-groups-in-the-server-management-console.md
+++ /dev/null
@@ -1,68 +0,0 @@
----
-title: How to Manage Application Groups in the Server Management Console
-description: How to Manage Application Groups in the Server Management Console
-author: dansimp
-ms.assetid: 46997971-bdc8-4565-aefd-f47e90d6d7a6
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Manage Application Groups in the Server Management Console
-
-
-You can display and manage one or more applications in application groups in the Application Virtualization Server Management Console. This can be useful when you want to do the following:
-
-- Organize many applications into more manageable subgroups.
-
-- Create groups of applications specific to a department or other company division.
-
-- Group similar types of applications, such as financial software.
-
-- Simplify access permissions or license management by group.
-
-- Change the properties of applications and application groups within a group simultaneously.
-
-You can create a group, place it where you would like in the console's **Applications** tree, and import applications to the group. Then you can configure and manage the group's properties to affect all of its applications. You can also move applications among groups.
-
-**Note**
-Moving applications into groups does not affect the locations of their files (SFT, OSD, or SPRJ) on the server's file system.
-
-
-
-## In This Section
-
-
-[How to Create an Application Group](how-to-create-an-application-group.md)
-Provides step-by-step instructions for creating an application group.
-
-[How to Move an Application Group](how-to-move-an-application-group.md)
-Provides step-by-step instructions for moving an application group.
-
-[How to Rename an Application Group](how-to-rename-an-application-group.md)
-Provides step-by-step instructions for renaming an application group.
-
-[How to Remove an Application Group](how-to-remove-an-application-group.md)
-Provides step-by-step instructions for removing or deleting an application group.
-
-## Related topics
-
-
-[How to Manage Applications in the Server Management Console](how-to-manage-applications-in-the-server-management-console.md)
-
-[How to Perform Administrative Tasks in the Application Virtualization Server Management Console](how-to-perform-administrative-tasks-in-the-application-virtualization-server-management-console.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-manage-application-licenses-in-the-server-management-console.md b/mdop/appv-v4/how-to-manage-application-licenses-in-the-server-management-console.md
deleted file mode 100644
index 89c0f06825..0000000000
--- a/mdop/appv-v4/how-to-manage-application-licenses-in-the-server-management-console.md
+++ /dev/null
@@ -1,63 +0,0 @@
----
-title: How to Manage Application Licenses in the Server Management Console
-description: How to Manage Application Licenses in the Server Management Console
-author: dansimp
-ms.assetid: 48503b04-0de7-48de-98ee-4623a712a341
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Manage Application Licenses in the Server Management Console
-
-
-The Application Virtualization Server Management Console is the interface you use to manage the Application Virtualization platform. From it, you can add, remove, configure, and control application license groups.
-
-**Important**
-If the App-V client Application Source Root (ASR) setting is configured to use any type of streaming source other than the Management Server, for example a Streaming Server, an IIS server, or a File server, then the Management Server is unable to enforce its licensing policy.
-
-
-
-## In This Section
-
-
-[How to Create an Application License Group](how-to-create-an-application-license-group.md)
-Provides a procedure for creating a new application in a license group.
-
-[How to Associate an Application with a License Group](how-to-associate-an-application-with-a-license-group.md)
-Provides a procedure for adding an application to a license group.
-
-[How to Remove an Application from a License Group](how-to-remove-an-application-from-a-license-group.md)
-Provides a procedure for removing an application from a license group.
-
-[How to Remove an Application License Group](how-to-remove-an-application-license-group.md)
-This section includes the steps necessary to delete an application license group.
-
-[How to Set Up an Unlimited License Group](how-to-set-up-an-unlimited-license-group.md)
-Provides a procedure for creating a new unlimited license group, allowing an unlimited number of users to access the applications in the group.
-
-[How to Set Up a Concurrent License Group](how-to-set-up-a-concurrent-license-group.md)
-Provides a procedure for creating a new concurrent license group, allowing a specific number of concurrent users to access the applications in the group.
-
-[How to Set Up a Named License Group](how-to-set-up-a-named-license-group.md)
-Provides a procedure for creating a new unlimited license group, allowing specific users to access the applications in the group.
-
-## Related topics
-
-
-[How to Perform Administrative Tasks in the Application Virtualization Server Management Console](how-to-perform-administrative-tasks-in-the-application-virtualization-server-management-console.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-manage-applications-in-the-client-management-console.md b/mdop/appv-v4/how-to-manage-applications-in-the-client-management-console.md
deleted file mode 100644
index caa426f56a..0000000000
--- a/mdop/appv-v4/how-to-manage-applications-in-the-client-management-console.md
+++ /dev/null
@@ -1,58 +0,0 @@
----
-title: How to Manage Applications in the Client Management Console
-description: How to Manage Applications in the Client Management Console
-author: dansimp
-ms.assetid: 15cb5133-539b-499d-adca-ed02da20194a
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Manage Applications in the Client Management Console
-
-
-You can use the Application Virtualization Client Management Console to manage virtual applications in the Application Virtualization Desktop Client or Client for Remote Desktop Services (formerly Terminal Services) cache. In the context of application virtualization, the cache is the area on the client computer reserved to store virtual applications.
-
-## In This Section
-
-
-[How to Load or Unload an Application](how-to-load-or-unload-an-application.md)
-Provides procedures for loading or unloading an application into or from the client cache.
-
-[How to Clear an Application](how-to-clear-an-application.md)
-Provides a procedure you can use to clear the settings, file type associations, and shortcuts from the Application Virtualization Desktop Client or Client for Remote Desktop Services.
-
-[How to Repair an Application](how-to-repair-an-application.md)
-Provides a procedure for repairing an application from the Application Virtualization Desktop Client or Client for Remote Desktop Services.
-
-[How to Import an Application](how-to-import-an-application.md)
-Provides a procedure you can use to add a new application to the Application Virtualization Desktop Client or Client for Remote Desktop Services.
-
-[How to Lock or Unlock an Application](how-to-lock-or-unlock-an-application.md)
-Provides procedures for locking or unlocking an application in the cache.
-
-[How to Delete an Application](how-to-delete-an-application.md)
-Provides a procedure you can use to remove an application from the file system cache.
-
-[How to Change an Application Icon](how-to-change-an-application-icon.md)
-Provides a procedure you can use to change the icon associated with the selected application.
-
-## Related topics
-
-
-[Application Virtualization Client Management Console](application-virtualization-client-management-console.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-manage-applications-in-the-server-management-console.md b/mdop/appv-v4/how-to-manage-applications-in-the-server-management-console.md
deleted file mode 100644
index bfae14c37b..0000000000
--- a/mdop/appv-v4/how-to-manage-applications-in-the-server-management-console.md
+++ /dev/null
@@ -1,61 +0,0 @@
----
-title: How to Manage Applications in the Server Management Console
-description: How to Manage Applications in the Server Management Console
-author: dansimp
-ms.assetid: 21139a77-9f0f-4787-8173-a7766966ff7f
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Manage Applications in the Server Management Console
-
-
-From the Application Virtualization Server Management Console, you can add, remove, configure, and control all applications, for one or multiple Application Virtualization Servers.
-
-## In This Section
-
-
-[How to Import an Application](how-to-import-an-applicationserver.md)
-Provides step-by-step instructions for importing an application by importing the Open Software Descriptor (OSD) or Sequencer Project (SPRJ) file.
-
-[How to Rename an Application](how-to-rename-an-application.md)
-Provides step-by-step instructions for renaming an existing application.
-
-[How to Delete an Application](how-to-delete-an-application-server.md)
-Provides step-by-step instructions for removing or deleting an application.
-
-[How to Manually Add an Application](how-to-manually-add-an-application.md)
-Provides step-by-step instructions for manually adding an application to the servers.
-
-[How to Move an Application](how-to-move-an-application.md)
-Provides step-by-step instructions for moving an application from one application group to another application group.
-
-[How to Grant Access to an Application](how-to-grant-access-to-an-application.md)
-Provides step-by-step instructions for giving users access permission to applications.
-
-[How to Deny Access to an Application](how-to-deny-access-to-an-application.md)
-Provides step-by-step instructions for denying users access permission to applications.
-
-[How to Change an Application Icon](how-to-change-an-application-iconserver.md)
-Provides step-by-step instructions for changing the application icon.
-
-## Related topics
-
-
-[How to Perform Administrative Tasks in the Application Virtualization Server Management Console](how-to-perform-administrative-tasks-in-the-application-virtualization-server-management-console.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-manage-packages-in-the-server-management-console.md b/mdop/appv-v4/how-to-manage-packages-in-the-server-management-console.md
deleted file mode 100644
index 920445161f..0000000000
--- a/mdop/appv-v4/how-to-manage-packages-in-the-server-management-console.md
+++ /dev/null
@@ -1,52 +0,0 @@
----
-title: How to Manage Packages in the Server Management Console
-description: How to Manage Packages in the Server Management Console
-author: dansimp
-ms.assetid: d13d3896-8575-4d2a-8bb4-1fe15d79c390
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Manage Packages in the Server Management Console
-
-
-Application Virtualization packages, accessible via the **Packages** node in the Application Virtualization Server Management Console, enable you to control virtual application versions on your Application Virtualization Management Servers.
-
-## In This Section
-
-
-[How to Add a Package](how-to-add-a-package.md)
-Provides a step-by-step procedure for adding a package to the Application Virtualization Server Management Console.
-
-[How to Add a Package Version](how-to-add-a-package-version.md)
-Provides a step-by-step procedure for adding a new version of the package to the Application Virtualization Server Management Console.
-
-[How to Delete a Package](how-to-delete-a-packageserver.md)
-Provides a step-by-step procedure for deleting a package from the Application Virtualization Server Management Console.
-
-[How to Delete a Package Version](how-to-delete-a-package-version.md)
-Provides a step-by-step procedure for deleting a specific version of a package from the Application Virtualization Server Management Console.
-
-[How to Upgrade a Package](how-to-upgrade-a-package.md)
-Provides a step-by-step procedure for upgrading a package version on the Application Virtualization Server Management Console.
-
-## Related topics
-
-
-[How to Perform Administrative Tasks in the Application Virtualization Server Management Console](how-to-perform-administrative-tasks-in-the-application-virtualization-server-management-console.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-manage-reports-in-the-server-management-console.md b/mdop/appv-v4/how-to-manage-reports-in-the-server-management-console.md
deleted file mode 100644
index cfd2debb42..0000000000
--- a/mdop/appv-v4/how-to-manage-reports-in-the-server-management-console.md
+++ /dev/null
@@ -1,70 +0,0 @@
----
-title: How to Manage Reports in the Server Management Console
-description: How to Manage Reports in the Server Management Console
-author: dansimp
-ms.assetid: 28d99620-6339-43f6-9288-4aa958607c59
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 08/30/2016
----
-
-
-# How to Manage Reports in the Server Management Console
-
-
-To effectively manage the Application Virtualization System, you can use the Application Virtualization Server Management Console to generate a variety of reports that provide information about the system. This information includes daily usage information for a specific application or all applications, and system error tracking.
-
-**Note**
-- During installation, the installation script installs only the English language version of report viewer. For the report viewer to display the correct information in other languages, it is necessary to install a language pack from the following location: .
-
-- When you add or edit an application in the Server Management Console, you must make sure that the application names and versions exactly match those in the OSD files. The reporting feature uses the application names and versions data fields when it identifies application usage data on which to report. If the data fields do not match, the usage records will be skipped.
-
-
-
-## In This Section
-
-
-[Application Virtualization Report Types](application-virtualization-report-types.md)
-Contains information about the available report types.
-
-[How to Create a Report](how-to-create-a-reportserver.md)
-Provides a step-by-step process for creating a report.
-
-[How to Run a Report](how-to-run-a-reportserver.md)
-Provides a step-by-step process for running a report.
-
-[How to Print a Report](how-to-print-a-reportserver.md)
-Provides a step-by-step process for printing a report.
-
-[How to Export a Report](how-to-export-a-reportserver.md)
-Provides a step-by-step process for exporting a report.
-
-[How to Delete a Report](how-to-delete-a-reportserver.md)
-Provides a step-by-step process for deleting a report.
-
-## Related topics
-
-
-[Application Utilization Report](application-utilization-reportserver.md)
-
-[How to Perform Administrative Tasks in the Application Virtualization Server Management Console](how-to-perform-administrative-tasks-in-the-application-virtualization-server-management-console.md)
-
-[Software Audit Report](software-audit-reportserver.md)
-
-[System Error Report](system-error-reportserver.md)
-
-[System Utilization Report](system-utilization-reportserver.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-manage-servers-in-the-server-management-console.md b/mdop/appv-v4/how-to-manage-servers-in-the-server-management-console.md
deleted file mode 100644
index 9287af4caa..0000000000
--- a/mdop/appv-v4/how-to-manage-servers-in-the-server-management-console.md
+++ /dev/null
@@ -1,55 +0,0 @@
----
-title: How to Manage Servers in the Server Management Console
-description: How to Manage Servers in the Server Management Console
-author: dansimp
-ms.assetid: 6e851c74-ea86-4fef-bb0c-e690e8e7e7eb
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Manage Servers in the Server Management Console
-
-
-The Application Virtualization Server Management Console is your interface to manage the servers in the Application Virtualization Platform. From it, you can add, configure, and control all the Application Virtualization Management Servers.
-
-## In This Section
-
-
-[How to Create a Server Group](how-to-create-a-server-group.md)
-Provides a procedure for creating server groups, to help you more effectively manage your servers.
-
-[How to Remove a Server Group](how-to-remove-a-server-group.md)
-Provides a procedure for removing server groups from the Application Virtualization System.
-
-[How to Add a Server](how-to-add-a-server.md)
-Provides a procedure for adding servers to a server group.
-
-[How to Remove a Server](how-to-remove-a-server.md)
-Provides a procedure for removing servers from a server group.
-
-[How to Change the Server Cache Size](how-to-change-the-server-cache-size.md)
-Provides a procedure for changing the cache size of a server.
-
-[How to Change the Server Port](how-to-change-the-server-port.md)
-Provides a procedure for changing the server ports.
-
-## Related topics
-
-
-[How to Perform Administrative Tasks in the Application Virtualization Server Management Console](how-to-perform-administrative-tasks-in-the-application-virtualization-server-management-console.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-manage-the-app-v-client-cache-using-performance-counters.md b/mdop/appv-v4/how-to-manage-the-app-v-client-cache-using-performance-counters.md
deleted file mode 100644
index b3050789b3..0000000000
--- a/mdop/appv-v4/how-to-manage-the-app-v-client-cache-using-performance-counters.md
+++ /dev/null
@@ -1,49 +0,0 @@
----
-title: How to Manage the App-V Client Cache Using Performance Counters
-description: How to Manage the App-V Client Cache Using Performance Counters
-author: dansimp
-ms.assetid: 49d6c3f2-68b8-4c69-befa-7598a8737d05
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Manage the App-V Client Cache Using Performance Counters
-
-
-You can use the following procedure to determine how much free space is available in the Application Virtualization (App-V) client cache by using Performance Monitor to display the information graphically. This information is captured on the client computer by a performance counter called “App Virt Client Cache,” and it includes the following counters: “Cache size (MB),” “Cache free space (MB),” and “% free space.”
-
-**To determine client cache space usage**
-
-1. Open a command prompt as administrator, or click **Start**, **Run**, type **perfmon.exe**, and click **OK**.
-
-2. Depending on the Windows operating system being used, click the Performance Monitor or System Monitor tool after the MMC window opens.
-
-3. To add counters, right-click the graph area and select **Add Counters**.
-
-4. Click the drop-down to display the list of available counters, scroll to find **App Virt Client Cache**, and then add the three counters.
-
- **Important**
- The App-V performance counters are implemented in a 32-bit DLL, so to see them, you must use the following command to start the 32-bit version of Performance Monitor: **mmc /32 perfmon.msc**. This command must be run directly on the computer being monitored and cannot be used to monitor a remote computer running a 64-bit operating system.
-
-
-
-## Related topics
-
-
-[How to Manage Virtual Applications by Using the Command Line](how-to-manage-virtual-applications-by-using-the-command-line.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-manage-virtual-applications-by-using-the-command-line.md b/mdop/appv-v4/how-to-manage-virtual-applications-by-using-the-command-line.md
deleted file mode 100644
index c88c2c0a2e..0000000000
--- a/mdop/appv-v4/how-to-manage-virtual-applications-by-using-the-command-line.md
+++ /dev/null
@@ -1,44 +0,0 @@
----
-title: How to Manage Virtual Applications by Using the Command Line
-description: How to Manage Virtual Applications by Using the Command Line
-author: dansimp
-ms.assetid: 88c61c20-5243-4862-83eb-5b30825f8bbf
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Manage Virtual Applications by Using the Command Line
-
-
-This section provides information about using the SFTMIME command-line language to manage applications and packages on computers.
-
-## In This Section
-
-
-[How to Add a Package by Using the Command Line](how-to-add-a-package-by-using-the-command-line.md)
-Describes how to add a package to a specific computer by using SFTMIME.
-
-[How to Remove a Package by Using the Command Line](how-to-remove-a-package-by-using-the-command-line.md)
-Describes how to remove a package from a specific computer by using SFTMIME.
-
-[How to Delete All Virtual Applications by Using the Command Line](how-to-delete-all-virtual-applications-by-using-the-command-line.md)
-Describes how to remove all applications from a specific computer by using SFTMIME.
-
-[How to Manage the App-V Client Cache Using Performance Counters](how-to-manage-the-app-v-client-cache-using-performance-counters.md)
-Describes how to determine free space in the client cache using the performance counters.
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-manage-virtual-applications-manually.md b/mdop/appv-v4/how-to-manage-virtual-applications-manually.md
deleted file mode 100644
index 1e5aa136e6..0000000000
--- a/mdop/appv-v4/how-to-manage-virtual-applications-manually.md
+++ /dev/null
@@ -1,241 +0,0 @@
----
-title: How to Manage Virtual Applications Manually
-description: How to Manage Virtual Applications Manually
-author: dansimp
-ms.assetid: 583c5255-d3f4-4197-85cd-2a59868d85de
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Manage Virtual Applications Manually
-
-
-You can use the Application Virtualization (App-V) Client Management Console to manage virtual applications in the App-V Desktop Client or the App-V Client for Remote Desktop Services (formerly Terminal Services). App-V administrators can use perform the following tasks:
-
-## How to Load or Unload an App-V Application
-
-
-You can use the following procedures to load or unload an application from the cache, directly from the **Results** pane of the **Application** node in the Application Virtualization Client Management Console. When you select this node, the **Results** pane displays a list of applications.
-
-**Note**
-When you load or unload a package, all the applications in the package are loaded into or removed from cache. When loading a package, if you do not have adequate space in cache to load the applications, increase your cache size. For more information about cache size, see [How to Change the Cache Size and the Drive Letter Designation](how-to-change-the-cache-size-and-the-drive-letter-designation.md).
-
-
-
-**To load an App-V application**
-
-1. Move the cursor to the **Results** pane, right-click the desired application, and select **Load** from the pop-up menu.
-
-2. The application is automatically loaded. The progress is tracked in the column labeled **Package Status**. You must refresh the view to see that the load is complete or to see the progress.
-
-**To unload an App-V application**
-
-1. Move the cursor to the **Results** pane, right-click the desired application, and select **Unload** from the pop-up menu.
-
-2. The application is automatically unloaded, and the **Package Status** column is updated to reflect the change.
-
-## How to clear an App-V application
-
-
-You can clear an application from the console directly from the **Results** pane of the **Application** node in the Application Virtualization Client Management Console. When you clear an application, the system removes the settings, shortcuts, and file type associations that correspond to the application and also removes the application from the user’s list of applications.
-
-**Note**
-When you clear an application from the console, you can no longer use that application. However, the application remains in cache and is still available to other users on the same system. After a publishing refresh, the cleared applications will again become available to you. If there are multiple applications in a package, the user's settings are not removed until all of the applications are cleared.
-
-
-
-**To clear an application from the console**
-
-1. Move the cursor to the **Results** pane, right-click the desired application, and select **Clear** from the pop-up menu.
-
-2. At the confirmation prompt, click **Yes** to remove the application or click **No** to cancel the operation.
-
-## How to Repair an App-V application
-
-
-To repair a selected application, you can perform the following procedure directly from the **Results** pane of the **Application** node in the Application Virtualization Client Management Console. When you repair an application, you remove any custom user settings and restore the default settings. This action does not change or delete shortcuts or file type associations, and it does not remove the application from cache.
-
-**To repair an App-V application**
-
-1. Move the cursor to the **Results** pane.
-
-2. Right-click the desired application, and select **Repair** from the pop-up menu.
-
-3. At the confirmation prompt, click **Yes** to repair the application or **No** to cancel.
-
-## How to import an App-V application
-
-
-You can use the following procedure to import an application into the cache directly from the **Results** pane of the **Application** node in the Application Virtualization Client Management Console.
-
-**To import an App-V application**
-
-1. Move the cursor to the **Results** pane, right-click the desired application, and select **Import** from the pop-up menu.
-
-2. From the **Browse** window, navigate to the location of the package file for the desired application, and then click **OK**.
-
- **Note**
- If you have already configured an import search path or if the SFT file is in the same path as the last successful import, step 2 is not required.
-
-
-
-## How to lock or unlock an App-V application
-
-
-You can use the following procedures to lock or unlock any application in the Application Virtualization Desktop Client cache or the Client for Remote Desktop Services (formerly Terminal Services) cache. A locked application cannot be removed from the cache to make room for new applications. To remove a locked application from the Application Virtualization Desktop Client cache or the Client for Remote Desktop Services cache, you must first unlock it.
-
-**To lock an application**
-
-1. Move the cursor to the **Results** pane.
-
-2. Right-click the desired application, and select **Lock** from the pop-up menu. The selected application is locked in the cache.
-
-**To unlock an application**
-
-1. Move the cursor to the **Results** pane.
-
-2. Right-click the desired application, and select **Unlock** from the pop-up menu. The selected application is unlocked in the cache and can be removed.
-
-## How to delete an App-V application
-
-
-When you select the **Application** node in the Application Virtualization Client Management Console, the **Results** pane displays a list of applications. You can use the following procedure to delete an application from the **Results** pane, which also removes the application from the cache.
-
-**Note**
-When you delete an application, the selected application will no longer be available to any users on that client. Shortcuts and file type associations are hidden, and the application is deleted from cache. However, if another application refers to data in the file system cache data for the selected application, these items will not be deleted.
-
-After a publishing refresh, the deleted applications will again become available to you.
-
-
-
-**To delete an application**
-
-1. Move the cursor to the **Results** pane, right-click the desired application, and select **Delete** from the pop-up menu.
-
-2. At the confirmation prompt, click **Yes** to remove the application or click **No** to cancel the operation.
-
-## How to change an App-V application icon
-
-
-You can use the following procedure to change an icon associated with the selected application directly from the **Results** pane of the **Application** node in the Application Virtualization Client Management Console.
-
-**To change an application icon**
-
-1. Move the cursor to the **Results** pane, and right-click the desired application.
-
-2. Select **Properties**.
-
-3. On the **General** tab, click **Change Icon**.
-
-4. Select the desired icon, or browse to another location to select the icon. After you've selected the icon, click **OK**. The new icon appears in the **Results** pane.
-
-## How to add an App-V application
-
-
-You can use the following procedure to add an application directly from the **Results** pane of the **Application** node in the Application Virtualization Client Management Console.
-
-**To add an application**
-
-1. In the **Results** pane, right-click and select **New Application** from the pop-up menu.
-
-2. On the wizard page, you can perform the following tasks:
-
- 1. **Change Icon**—Displays a standard Windows icon browser. Browse to and select the desired icon.
-
- 2. **OSD File Path or URL**—Enter a local absolute path, a full UNC path (shared file or directory on a network), or an HTTP URL.
-
- 3. **(OSD browse button)**—Displays the standard Windows **Open File** dialog box. Browse to find the desired file.
-
-3. Click **Finish** to add the application to the **Results** pane.
-
-## How to publish an App-V application shortcut
-
-
-You can use the following procedure to publish shortcuts to an application directly from the **Results** pane of the **Application** node in the Application Virtualization Client Management Console.
-
-**To publish application shortcuts**
-
-1. Move the cursor to the **Results** pane, right-click the desired application, and select **New Shortcut** from the pop-up menu to display the New Shortcut Wizard.
-
-2. On the first page of the New Shortcut Wizard, select an icon and specify a name for the shortcut.
-
- 1. **Change Icon**—Displays a standard Windows icon browser. Browse to and select the desired icon.
-
- 2. **Shortcut Title**—Enter the name you want to give the shortcut. This field defaults to the existing name and version of the application.
-
-3. On the second page of the wizard, determine the location of the published shortcut.
-
- 1. **The Desktop**—Select this check box to publish the shortcut to the desktop.
-
- 2. **The Quick Launch Toolbar**—Select this check box to publish the shortcut to the Quick Launch toolbar.
-
- 3. **The Send To Menu**—Select this check box to publish the shortcut to the **Send To** menu.
-
- 4. **Programs in the Start Menu**—When you select the **Start Menu** check box, this field becomes active. Leave this field blank to publish the shortcut directly to the root of the Programs folder, or enter a folder name or hierarchy—for example, "My\_Computer\\Office Applications." Shortcuts created this way are available only for the current user.
-
- 5. **Another location** and **Browse** button—When you select the **Another location** check box, this field becomes active. Enter any valid location on the computer or any available UNC path (shared file or directory on a network). The **Browse** button displays a standard Windows **File Open** dialog box.
-
-4. On the third page of the wizard, enter desired command-line parameters.
-
-5. Click **Finish** to publish the shortcuts and exit to the **Results** pane.
-
-## How to add a file type association for an App-V application
-
-
-You can use the following procedure to add a file type association, using the **File Type Associations** node in the Application Virtualization Client Management Console.
-
-**To add a file type association**
-
-1. Right-click the **File Type Associations** node, and select **New Association** from the pop-up menu.
-
-2. Complete the first step of the dialog box by completing the following information, and then click **Next**:
-
- 1. **Extension**—Enter a new file name extension. This field is blank by default.
-
- 2. **Create a new file type with this description**—Select this radio button to enter a new file type description in the active field. This button is selected by default, and the active field is blank.
-
- 3. **Apply this file type to all users**—Select this check box when you want this association to be global for all users. By default, this box is cleared.
-
- 4. **Link this extension with an existing file type**—Select this radio button to associate the extension with an existing file type. Pick a file type from the drop-down list. When you choose this option, **Next** is changed to **Finish**.
-
-3. Complete the second step of the dialog box by completing the following information, and then click **Finish** to return to the Client Management Console:
-
- 1. **Change Icon**—Click this button to change the application icon. Select one of the available icons, or browse to a new location and select an icon.
-
- 2. **Open files with the selected application**—Select this radio button to open the file with an existing application. Choose an application from the drop-down list of available applications.
-
- 3. **Open file with the association described in this OSD file**—Select this radio button to specify an Open Software Descriptor (OSD) file that determines the application used to open the file. Use the browse button to select an existing location, or enter a path or HTTP-formatted URL in this field.
-
-## How to delete a file type association for an App-V application
-
-
-You can use the following procedure to delete a file type association. The **File Type Associations** node is one level below the **Application Virtualization** node in the **Scope** pane. When you select this node, the **Results** pane displays a list of file type associations.
-
-**To remove a file type association**
-
-1. In the **Results** pane, right-click the extension of the file type association you want to delete.
-
-2. Select **Delete** from the pop-up menu.
-
-3. Click **Yes** to delete the association, or click **No** to return to the **Results** pane.
-
-## Related topics
-
-
-[Application Virtualization Client](application-virtualization-client.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-manage-virtual-applications-using-the-command-line.md b/mdop/appv-v4/how-to-manage-virtual-applications-using-the-command-line.md
deleted file mode 100644
index 49b1512034..0000000000
--- a/mdop/appv-v4/how-to-manage-virtual-applications-using-the-command-line.md
+++ /dev/null
@@ -1,41 +0,0 @@
----
-title: How to Manage Virtual Applications Using the Command Line
-description: How to Manage Virtual Applications Using the Command Line
-author: dansimp
-ms.assetid: 9394f34d-2b1e-4ea7-bf6f-1f56101ab4de
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Manage Virtual Applications Using the Command Line
-
-
-Click any of the following links for more information about managing virtual applications using the command line.
-
-## In This Section
-
-
-[How to Open a Sequenced Application Using the Command Line](how-to-open-a-sequenced-application-using-the-command-line.md)
-Specifies how to open a virtual application using the command line.
-
-[How to Upgrade a Sequenced Application Package Using the Command Line](how-to-upgrade-a-sequenced-application-package-using-the-command-line.md)
-Specifies how to sequence a virtual application using the command line.
-
-[How to Upgrade a Package Using the Open Package Command](how-to-upgrade-a-package-using-the-open-package-command.md)
-Specifies how to upgrade a virtual application package using the command line.
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-manually-add-an-application.md b/mdop/appv-v4/how-to-manually-add-an-application.md
deleted file mode 100644
index b503780e0d..0000000000
--- a/mdop/appv-v4/how-to-manually-add-an-application.md
+++ /dev/null
@@ -1,74 +0,0 @@
----
-title: How to Manually Add an Application
-description: How to Manually Add an Application
-author: dansimp
-ms.assetid: c635b07a-5c7f-4ab2-ba18-366457146cb9
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Manually Add an Application
-
-
-When adding an application to the Application Virtualization Management Server, it is recommended that you import it. You can add an application manually, but you must provide the precise, detailed information about the application called for in this section.
-
-**To manually add a new application**
-
-1. In the left pane, right-click the **Applications** node and choose **New Application**.
-
-2. In the **New Application Wizard**, complete the **General Information** dialog box:
-
- 1. **Application Name**—Type the name you want the users to see.
-
- 2. **Version**—Type the application version.
-
- 3. **Enabled**—This box must be selected to stream the application after you create it.
-
- 4. **Description**—Type an optional description for administrative use.
-
- 5. **OSD Path**—Browse the network to the application's Open Software Descriptor (OSD) file. This file must be in a shared network folder.
-
- 6. **Icon Path**—Browse to the application's ICO file.
-
- 7. **Application License Group**—If you have set up license groups, you can assign the application to one by selecting it in the pull-down list.
-
- 8. **Server Group**—If you have multiple Application Virtualization Servers, you can assign the application to one by selecting it in the pull-down list.
-
-3. Click **Next**.
-
-4. In the **Select Package** dialog box, select the related package and click **Next**.
-
-5. On the **Published Shortcuts** screen, select the boxes for the locations where you would like the application shortcuts to appear on the client computers and click **Next**.
-
-6. In the **File Associations** screen, you can add new type file associations to this application. To do so, click **Add**, enter the extension (without a preceding dot), enter a description, and click **OK**.
-
-7. Click **Next**.
-
-8. In the **Access Permissions** dialog box, click **Add**.
-
-9. In the **Add/Edit User Group** dialog box, navigate to the user group. You can also enter the domain and group by typing the information in the respective fields. When you finish, click **OK**. You can add other groups with the same pages.
-
-10. Click **Next**.
-
-11. On the **Summary** screen, you can review the import settings. Click **Finish** to add the application, click **Back** to change the information, or click **Cancel**.
-
-## Related topics
-
-
-[How to Manage Applications in the Server Management Console](how-to-manage-applications-in-the-server-management-console.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-manually-install-the-application-virtualization-client.md b/mdop/appv-v4/how-to-manually-install-the-application-virtualization-client.md
deleted file mode 100644
index 3df7f2a0ee..0000000000
--- a/mdop/appv-v4/how-to-manually-install-the-application-virtualization-client.md
+++ /dev/null
@@ -1,131 +0,0 @@
----
-title: How to Manually Install the Application Virtualization Client
-description: How to Manually Install the Application Virtualization Client
-author: dansimp
-ms.assetid: bb67f70b-d525-4317-b254-e4f084c717ab
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 08/30/2016
----
-
-# How to Manually Install the Application Virtualization Client
-
-There are two types of Application Virtualization Client components: the Application Virtualization Desktop Client, which is designed for installation on desktop computers, and the Application Virtualization Client for Remote Desktop Services (formerly Terminal Services), which you can install on Remote Desktop Session Host (RD Session Host) servers . Although the two client installer programs are different, you can use the following procedure to manually install either the Application Virtualization Desktop Client on a single desktop computer or the Application Virtualization Client for Remote Desktop Services on a single RD Session Host server. In a production environment, you most likely will install the Application Virtualization Desktop Client on multiple desktop computers with an automated scripted installation process. For information about how to install multiple clients by using a scripted installation process, see [How to Install the Client by Using the Command Line](how-to-install-the-client-by-using-the-command-line-new.md).
-
-**Note**
-1. If you are installing the Application Virtualization Client for Remote Desktop Services software on a RD Session Host server, advise users who have an open RDP or ICA client session with the RD Session Host server that they must save their work and close their sessions. In a Remote Desktop session, you can install the client the client manually. For more information about upgrading the client, see [How to Upgrade the Application Virtualization Client](how-to-upgrade-the-application-virtualization-client.md).
-
-2. If you have any configuration on the user’s computer that depends on the client install path, note that the Application Virtualization (App-V) 4.5 client uses a different install folder than previous versions. By default, a new install of the Application Virtualization (App-V) 4.5 client will install to the \\Program Files\\Microsoft Application Virtualization Client folder. If an earlier version of the client is already installed, installing the App-V client will perform an upgrade into the existing installation folder.
-
-**Note**
-For App-V version 4.6 and later, when the App-V client is installed, SFTLDR.DLL is installed in the Windows\\system32 directory. If the App-V client is installed on a 64-bit system, SFTLDR\_WOW64.DLL is installed in the Windows\\SysWOW64 directory.
-
-**To manually install Application Virtualization Desktop Client**
-
-1. After you have obtained the correct installer archive file and saved it to your computer, make sure you are logged on with an account having administrator rights on the computer and double-click the file to expand the archive.
-
-2. Choose the folder in which to save the files, and then open the folder after the files have been copied to it.
-
-3. Review the Release Notes if appropriate.
-
-4. Browse to find the setup.exe file, and double-click setup.exe to start the installation.
-
-5. The wizard checks the system to ensure that all prerequisite software is installed, and if any of the following are missing, the wizard will automatically prompt you to install them:
-
- - Microsoft Visual C++ 2005 SP1 Redistributable Package (x86)
-
- - Microsoft Core XML Services (MSXML) 6.0 SP1 (x86)
-
- - Microsoft Application Error Reporting
-
- **Note**
- For App-V version 4.6 and later, the wizard will also install Microsoft Visual C++ 2008 SP1 Redistributable Package (x86).
-
- For more information about installing Microsoft Visual C++ 2008 SP1 Redistributable Package (x86), see [https://go.microsoft.com/fwlink/?LinkId=150700](https://go.microsoft.com/fwlink/?LinkId=150700).
-
- If prompted, click **Install**. Installation progress is displayed, and the status changes from **Pending** to **Installing**. Installation status changes to **Succeeded** as each step is completed successfully.
-
-6. When the **Microsoft Application Virtualization Desktop Client – InstallShield Wizard** is displayed, click **Next**.
-
-7. The **License Agreement** screen is displayed. Read the license agreement, and if you agree, click **I accept the terms in the license agreement** and then click **Next**.
-
- Optionally, you can click the button to read the Privacy Statement. You must be connected to the Internet to access the Privacy Statement.
-
-8. On the **Setup Type** screen, select the setup type. Click **Typical** to use the default program values, or click **Custom** if you want to configure the program settings during installation.
-
-9. If you choose **Typical**, the next screen displays **Ready to Install the Program**. Click **Install** to begin the installation.
-
-10. If you choose **Custom**, the **Destination Folder** screen appears.
-
-11. On the **Destination Folder** screen, click **Next** to accept the default folder or click **Change** to display the **Change Current Destination Folder** screen. Browse to or, in the **Folder Name** field, enter the destination folder, click **OK**, and then click **Next**.
-
-12. On the **Application Virtualization Data Location** screen, click **Next** to accept the default data locations or complete the following actions to change where the data is stored:
-
- 1. Click **Change**, and then browse to or, in the **Global Data Location** field, enter the destination folder for the global data location, and click **OK**. The Global Data Directory is where the Application Virtualization Desktop Client caches data shared by all users on the computer, like OSD files and SFT file data.
-
- 2. If you want to change the drive letter to be used, select the preferred drive letter from the drop-down list.
-
- 3. Enter a new path to store the user-specific data in the **User-specific Data Location** field if you want to change the data location. The User Data Directory is where the Application Virtualization Desktop Client stores user-specific information, like personal settings for virtualized applications.
-
- **Note**
- This path must be different for every user, so it should include a user-specific environment variable or a mapped drive or something else that will resolve to a unique path for each user.
-
- 4. When you have finished making the changes, click **Next**.
-
-13. On the **Cache Size Settings** screen, you can accept or change the default cache size. Click one of the following radio buttons to choose how to manage the cache space:
-
- 1. **Use maximum cache size**. Enter a numeric value from 100–1,048,576 (1 TB) in the **Maximum size (MB)** field to specify the maximum size of the cache.
-
- 2. **Use free disk space threshold**. Enter a numeric value to specify the amount of free disk space, in MB, that the Application Virtualization Client must leave available on the disk. This allows the cache to grow until the amount of free disk space reaches this limit. The value shown in **Free disk space remaining** indicates how much disk space is currently unused.
-
- **Important**
- To ensure that the cache has sufficient space allocated for all packages that might be deployed, use the **Use free disk space threshold** setting when you configure the client so that the cache can grow as needed. Alternatively, determine in advance how much disk space will be needed for the App-V cache, and at installation time, set the cache size accordingly. For more information about the cache space management feature, in the Microsoft Application Virtualization (App-V) Operations Guide, see **How to Use the Cache Space Management Feature**.
-
- Click **Next** to continue.
-
-14. In the following sections of the **Runtime Package Policy Configuration** screen, you can change the parameters that affect how the Application Virtualization client behaves during runtime:
-
- 1. **Application Source Root**. Specifies the location of SFT files. If used, overrides the protocol, server, and port portions of the CODEBASE HREF URL in the OSD file.
-
- 2. **Application Authorization**. When **Require User authorization even when cached** is checked, users are required to connect to a server and validate their credentials at least once before they are allowed to start each virtual application.
-
- 3. **Allow streaming from file**. Indicates whether streaming from file will be enabled, regardless of how the **Application Source Root** field is used. If not checked, streaming from files is disabled. This must be checked if **Application Source Root** contains a UNC path in the form \\\\server\\share.
-
- 4. **Automatically Load Application**. Controls when and how automatic background loading of applications occurs.
-
- **Note**
- When you install the App-V client to use with a read-only cache, for example, with a VDI server implementation, set **What applications to Auto Load** to **Do not automatically load applications** to prevent the client from trying to update applications in the read-only cache.
-
- Click **Next** to continue.
-
-15. On the **Publishing Server** screen, select the **Set up a Publishing Server now** check box if you want to define a publishing server, or click **Next** if you want to complete this later. To define a publishing server, specify the following information:
-
- 1. **Display Name**—Enter the name you want to display for the server.
-
- 2. **Type**—Select the server type from the drop-down list of server types.
-
- 3. **Host Name** and **Port**—Enter the host name and the port in the corresponding fields. When you select a server type in the drop-down list, the port field will automatically fill with the standard port numbers. To change a port number, click the server type in the list and change the port number according to your needs.
-
- 4. **Path**—If you have selected either **Standard HTTP Server** or **Enhanced Security HTTP Server**, you must enter the complete path to the XML file containing publishing data in this field. If you select either **Application Virtualization Server** or **Enhanced Security Application Virtualization Server**, this field is not active.
-
- 5. **Automatically contact this server to update settings when a user logs in**—Select this check box if you want this server to be queried automatically when users log in to their account on the Application Virtualization Client.
-
- 6. When finished with the configuration steps, click **Next**.
-
-16. On the **Ready to Install the Program** screen, click **Install**. A screen is displayed that shows the progress of the installation.
-
-17. On the **Install Wizard Completed** screen, click **Finish**.
-
- **Note**
- If the installation fails for any reason, you might need to restart the computer before trying the install again.
-
-## Related topics
-
-[How to Install the Client by Using the Command Line](how-to-install-the-client-by-using-the-command-line-new.md)
-
-[Stand-Alone Delivery Scenario Overview](stand-alone-delivery-scenario-overview.md)
diff --git a/mdop/appv-v4/how-to-manually-manage-applications-in-the-client-management-console.md b/mdop/appv-v4/how-to-manually-manage-applications-in-the-client-management-console.md
deleted file mode 100644
index 4302487ce2..0000000000
--- a/mdop/appv-v4/how-to-manually-manage-applications-in-the-client-management-console.md
+++ /dev/null
@@ -1,49 +0,0 @@
----
-title: How to Manually Manage Applications in the Client Management Console
-description: How to Manually Manage Applications in the Client Management Console
-author: dansimp
-ms.assetid: e29caa22-325d-457b-a177-a11f8a8ad57c
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Manually Manage Applications in the Client Management Console
-
-
-This section provides procedures for using the Application Virtualization Client Management Console to manually manage your virtual applications.
-
-## In This Section
-
-
-[How to Add an Application](how-to-add-an-application.md)
-Provides a procedure you can use to add an application to the cache directly from the Application Virtualization Client Management Console.
-
-[How to Publish Application Shortcuts](how-to-publish-application-shortcuts.md)
-Provides a procedure you can use to publish application shortcuts to the desktop, menus, and tool bar directly from the Application Virtualization Client Management Console.
-
-[How to Add a File Type Association](how-to-add-a-file-type-association.md)
-Provides a procedure you can use to add a file type association to an application.
-
-[How to Delete a File Type Association](how-to-delete-a-file-type-association.md)
-Provides a procedure you can use to delete a file type association.
-
-## Related topics
-
-
-[Application Virtualization Client Management Console](application-virtualization-client-management-console.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-migrate-the-app-v-sql-database-to-a-different-sql-server.md b/mdop/appv-v4/how-to-migrate-the-app-v-sql-database-to-a-different-sql-server.md
deleted file mode 100644
index f4e1e2a14e..0000000000
--- a/mdop/appv-v4/how-to-migrate-the-app-v-sql-database-to-a-different-sql-server.md
+++ /dev/null
@@ -1,120 +0,0 @@
----
-title: How to Migrate the App-V SQL Database to a Different SQL Server
-description: How to Migrate the App-V SQL Database to a Different SQL Server
-author: dansimp
-ms.assetid: 353892a1-9327-4489-a19c-4ec7bd1b736f
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Migrate the App-V SQL Database to a Different SQL Server
-
-
-The following procedures describe in detail how to migrate the SQL database of the Microsoft Application Virtualization (App-V) Management Server to a different SQL Server.
-
-**Important**
-This procedure requires that the App-V server service is stopped and this will prevent end-users from using their applications.
-
-
-
-**To back up the App-V SQL database**
-
-1. Open the Services.msc program and stop the App-V Management Server service on all Management Servers that use the database to be migrated.
-
-2. On the computer where the App-V database is located, open SQL Server Management Studio.
-
-3. Expand the **Databases** node and locate the App-V database (default name is APPVIRT).
-
-4. Right-click the database and select **Tasks** and then select **Back Up**.
-
-5. Verify that **Recovery model** is set to **SIMPLE** and the **Backup type** is set to **Full**. Change the **Backup set** and **Destination** settings if it is necessary.
-
-6. Click **OK** to back up the database. After the backup has completed successfully, click **OK**.
-
-7. Open Windows Explorer and browse to the folder that contains the database backup file, for example APPVIRT.BAK. Copy the database backup file to the destination computer that is running SQL Server.
-
-**To restore the App-V SQL database to the destination computer**
-
-1. On the destination computer, open SQL Server Management Studio, right-click the **Databases** node and select **Restore Database**.
-
-2. Under **Source for Restore**, choose **From device** and then click the “**…**” button.
-
-3. In the **Specify Backup** dialog box, make sure that the **Backup Media** is set to **File** and then click **Add**.
-
-4. Select the backup file that you copied from the original computer that is running SQL Server, and then click **OK**.
-
-5. Click **OK** and then click to select the backup set to restore.
-
-6. Under **Destination for restore**, click the drop-down for **To database** and select the App-V database name, for example APPVIRT.
-
-7. Click **OK** to start the restore. After the restore has completed successfully, click **OK**.
-
-8. Expand the **Security** node, right-click **Logins** and select **New Login**.
-
-9. In the **Login Name** field, enter the Network Service account details for the App-V Management Server in the format of DOMAIN\\SERVERNAME$.
-
-10. On the **General** page under **Default database** select the App-V database name, for example, APPVIRT, and then click **OK**.
-
-11. Under **Select a page**, click to select the **User Mapping** page. Under **Users mapped to this login**, click the check box in the **Map** column to select the App-V database.
-
-12. Under **Database role membership for: <appvdatabasename>**, click to select **SFTEveryone** and then click **OK**.
-
-13. Make sure that the Windows Firewall on the new computer that is running SQL Server is configured to allow the App-V Management Server to access the system. Under **Administrative Tools**, use the **Windows Firewall with Advanced Security** program to create an **Inbound Rule** for the port that is used by SQL Server (default is port 1433).
-
-**To migrate the App-V SQL Server Agent jobs**
-
-1. On the original computer that is running SQL Server, in SQL Server Management Studio, expand the **SQL Server Agent** node, and then expand the **Jobs** node.
-
-2. Right-click the following four App-V jobs and select **Script Job as | CREATE to | File**, and save each script to a folder and give each script a descriptive name.
-
- - **Softgrid Database (appvdbname) Check Usage History**
-
- - **Softgrid Database (appvdbname) Close Orphaned Sessions**
-
- - **Softgrid Database (appvdbname) Enforce Size Limit**
-
- - **Softgrid Database (appvdbname) Monitor Alert/Job Status**
-
-3. Copy the four script files (.sql) to the destination computer that is running SQL Server and open SQL Server Management Studio.
-
-4. In Windows Explorer, right-click each .sql file and then click **Run**. Each script will open in a query window in SQL Server Management Studio. Click **Execute** for each script and verify that each is completed successfully.
-
-5. Refresh the **Jobs** node under the **SQL Server Agent** node and confirm that the four jobs are created successfully.
-
-**To update the configuration of the App-V Management Server**
-
-1. On the App-V Management Server, modify the following registry keys:
-
- - **SQLServerName** = <newservername>
-
- - **SQLServerPort** = <newserverport>
-
- Then restart the App-V server service.
-
-2. Browse to find the file SftMgmt.udl under the App-V Management Server installation directory (default is C:\\Program Files\\Microsoft System Center App Virt Management Server\\App Virt Management Service). Right-click the file and select **Open**.
-
-3. On the **Connection** tab, enter the name of the destination computer that is running SQL Server, and then click **Test Connection**. When the test is successful, click **OK** and then click **OK** again.
-
-4. For App-V Management Server versions before 4.5 SP2, you must update the SQL Logging settings. Under **Server Groups**, right-click the server group the server is a member of and select **Properties**.
-
-5. On the **Logging** tab click to select the **SQL Database** entry and then click **Edit**.
-
-6. Change the **DNS Host Name** to the host name of the new computer that is running SQL Server and then click **OK**. Click **OK** two times more, and then restart the App-V server service.
-
-7. Open the App-V Management Console, right-click the **Applications** node and select **Refresh**. The list of applications should be displayed as before.
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-modify-a-virtual-application-package--app-v-46-.md b/mdop/appv-v4/how-to-modify-a-virtual-application-package--app-v-46-.md
deleted file mode 100644
index 98641cae37..0000000000
--- a/mdop/appv-v4/how-to-modify-a-virtual-application-package--app-v-46-.md
+++ /dev/null
@@ -1,44 +0,0 @@
----
-title: How to Modify a Virtual Application Package (App-V 4.6)
-description: How to Modify a Virtual Application Package (App-V 4.6)
-author: dansimp
-ms.assetid: 346ec470-3822-48a7-95e7-61f46eb38dc2
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Modify a Virtual Application Package (App-V 4.6)
-
-
-The following procedure uses the Application Virtualization (App-V) Sequencer to edit the properties associated with an existing virtual application package.
-
-**To modify a virtual application package**
-
-1. To start the App-V Sequencer Console, on the computer running the Sequencer, select **Start** / **Programs** / **Microsoft Application Virtualization** / **Microsoft Application Virtualization Sequencer**.
-
-2. In the Sequencer console select **Edit a Package**. In the **Open** dialog box, locate and select the package you want to modify.
-
-3. Modify the application package. For more information about what properties can be modified, see [How to Determine Whether to Edit or Upgrade a Virtual Application Package](how-to-determine-whether-to-edit-or-upgrade-a-virtual-application-package.md).
-
-4. To save the modifications to the package, select **File** / **Save**.
-
-## Related topics
-
-
-[How to Upgrade a Virtual Application Package (App-V 4.6)](how-to-upgrade-a-virtual-application-package--app-v-46-.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-modify-an-existing-virtual-application-package--app-v-46-sp1-.md b/mdop/appv-v4/how-to-modify-an-existing-virtual-application-package--app-v-46-sp1-.md
deleted file mode 100644
index 9ef7b06355..0000000000
--- a/mdop/appv-v4/how-to-modify-an-existing-virtual-application-package--app-v-46-sp1-.md
+++ /dev/null
@@ -1,174 +0,0 @@
----
-title: How to Modify an Existing Virtual Application Package (App-V 4.6 SP1)
-description: How to Modify an Existing Virtual Application Package (App-V 4.6 SP1)
-author: dansimp
-ms.assetid: f43a9927-4325-4b2d-829f-3068e4e84349
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Modify an Existing Virtual Application Package (App-V 4.6 SP1)
-
-
-Use the following procedures to modify an existing virtual application package. You can use these procedures to:
-
-- Update an application that is part of an existing virtual application package. To perform this task, use the procedure **"To update an application in an existing application package"** in this document.
-
-- Modify the properties associated with an existing virtual application package. To perform this task, use the procedure **"To modify the properties associated with an existing virtual application package"** in this document.
-
-- Add a new application to an existing virtual application package. To perform this task, use the procedure **"To add a new application to an existing virtual application package"** in this document.
-
-You must have the App-V Sequencer installed to modify a virtual application package. For more information about installing the App-V Sequencer, see [How to Install the Sequencer (App-V 4.6 SP1)](how-to-install-the-sequencer---app-v-46-sp1-.md).
-
-**To update an application in an existing virtual application package**
-
-1. To start the App-V Sequencer, on the computer that is running the App-V Sequencer, click **Start** / **All Programs** / **Microsoft Application Virtualization** / **Microsoft Application Virtualization Sequencer**.
-
-2. In the App-V Sequencer, click **Modify an Existing Virtual Application Package**, and then click **Next**.
-
-3. On the **Select Task** page, click **Update Application in Existing Package**, and then click **Next**.
-
-4. On the **Select Package** page, click **Browse** to locate the virtual application package that contains the application that you want to update, and then click **Next**.
-
-5. On the **Prepare Computer** page, review the issues that could cause the application update to fail, or for the application update to contain unnecessary data. We strongly recommend that you resolve all potential issues before you continue. After you have fixed the conflicts, to update the information that is displayed, click **Refresh**. After you have resolved all potential issues, click **Next**.
-
- **Important**
- If you are required to disable virus scanning software, scan the computer running the sequencer to ensure that no unwanted or malicious files are added to the package.
-
-
-
-6. On the **Select Installer** page, click **Browse** and specify the update installation file for the application. If the update does not have an associated installer file and you plan to run all installation steps manually, select the **Select this option to perform a custom installation** check box, and then click **Next**.
-
-7. On the **Installation** page, when the sequencer and application installer are ready, install the application update so the sequencer can monitor the installation process. If additional installation files must be run as part of the installation, click **Run** and locate and run the additional installation files. When you are finished with the installation, select **I am finished installing**. Click **Next**.
-
- **Note**
- The sequencer monitors all changes and installations to the computer running the sequencer, including the changes and installations that are performed outside of the sequencing wizard.
-
-
-
-8. On the **Installation Report** page, you can review information about the virtual application you just updated. For a more detailed explanation about the information displayed in **Additional Information**, double-click the event. After you have reviewed the information, click **Next**.
-
-9. On the **Streaming** page, run each program so that it can be optimized and run more efficiently on target computers. It can take several minutes for all the applications to run. After all applications have run, close each of the applications, and then click **Next**.
-
- **Note**
- If you want to stop an application from loading during this step, in the **Application Launch** dialog box, click **Stop**, and then click one of the following options, **Stop all applications** or **Stop this application only**, depending on what you want.
-
-
-
-10. On the **Create Package** page, to modify the package without saving it, select the **Continue to modify package without saving using the package editor** check box. When you select this option, the package in the Sequencer console opens so that you can modify the package before it is saved. Click **Next**.
-
- To save the package immediately, select the default **Save the package now**. Add optional **Comments** that will be associated with the package. Comments are useful for identifying version and other information about the package. The default **Save Location** is also displayed. To change the default location, click **Browse** and specify the new location. The uncompressed package size is displayed. If the package size exceeds 4 GB (uncompressed) and you plan to stream the package to target computers, you must select **Compress Package**, and then click **Create**.
-
-11. On the **Completion** page, click **Close** to close the wizard. The package is now available in the sequencer.
-
-**To modify the properties associated with an existing virtual application package**
-
-1. To start the App-V Sequencer, on the computer that is running the App-V Sequencer, click **Start** / **All Programs** / **Microsoft Application Virtualization** / **Microsoft Application Virtualization Sequencer**.
-
-2. In the App-V Sequencer, click **Modify an Existing Virtual Application Package**, and then click **Next**.
-
-3. On the **Select Task** page, click **Edit Package**, and then click **Next**.
-
-4. On the **Select Package** page, click **Browse** to locate the virtual application package that contains the application properties that you want to modify, and then click **Edit**.
-
-5. In the Sequencer console, you can perform any of the following tasks:
-
- - View package properties.
-
- - View package change history.
-
- - View associated package files.
-
- - Edit registry settings.
-
- - Review additional package settings (except operating system file properties).
-
- - Create an associated Windows Installer (MSI).
-
- - Modify OSD file.
-
- - Compress and uncompress package.
-
- - Add file type associations.
-
- - Set virtualized registry key state (override or merge).
-
- - Set virtualized folder state.
-
- - Edit virtual file system mappings.
-
-6. When you have finished modifying the package properties, click **File** / **Save** to save the package,.
-
-**To add a new application to an existing virtual application package**
-
-1. To start the App-V Sequencer, on the computer that is running the App-V Sequencer, click **Start** / **All Programs** / **Microsoft Application Virtualization** / **Microsoft Application Virtualization Sequencer**.
-
-2. In the App-V Sequencer, click **Modify an Existing Virtual Application Package**, and then click **Next**.
-
-3. On the **Select Task** page, click **Add New Application**, and then click **Next**.
-
-4. On the **Select Package** page, click **Browse** to locate the virtual application package that you want to add the application to, and then click **Next**.
-
-5. On the **Prepare Computer** page, review the issues that could cause the package creation to fail, or for the update to contain unnecessary data. We strongly recommend that you resolve all potential issues before you continue. After you have fixed the conflicts, to update the information that is displayed, click **Refresh**. After you have resolved all potential issues, click **Next**.
-
- **Important**
- If you are required to disable virus scanning software, scan the computer running the sequencer to ensure that no unwanted or malicious files can be added to the package.
-
-
-
-6. On the **Select Installer** page, click **Browse** and specify the installation file for the application. If the application does not have an associated installer file and you plan to run all installation steps manually, select the **Select this option to perform a custom installation** check box, and then click **Next**.
-
-7. On the **Installation** page, when the sequencer and application installer are ready, install the application so the sequencer can monitor the installation process. If additional installation files must be run as part of the installation, click **Run**, and locate and run the additional installation files. When you are finished with the installation, select **I am finished installing**. Click **Next**. In the **Browse for Folder** dialog box, specify the primary directory where the application will be installed. This should be a new location so that you do not overwrite the existing version of the virtual application package.
-
- **Note**
- All changes and installations to the computer running the sequencer are monitored by the sequencer, including the changes and installations that are performed outside of the sequencing wizard.
-
-
-
-8. On the **Configure Software** page, optionally run the programs contained in the package. This step helps complete any associated license or configuration tasks that are required to run the application before you deploy and run the package on target computers. To run all the programs at the same time, select at least one program, and then click **Run All**. To run specific programs, select the program or programs you want to run, and then click **Run Selected**. Complete the required configuration tasks and then close the applications. It can take several minutes for all programs to run. Click **Next**.
-
-9. On the **Installation Report** page, you can review information about the virtual application you just updated. For a more detailed explanation about the information displayed in **Additional Information**, double-click the event. After you have reviewed the information, click **Next**.
-
-10. On the **Customize** page, if you are finished installing and configuring the virtual application, select **Stop now** and skip to step 14 of this procedure. If you want to customize any of the items in the following list, click **Customize**.
-
- - Edit the file type associations associated with an application.
-
- - Prepare the virtual package for streaming. Streaming improves the experience when the virtual application package is run on target computers.
-
- Click **Next**.
-
-11. On the **Edit Shortcuts** page, you can optionally configure the file type associations (FTA) that will be associated with the various applications in the package. To create a new FTA, select and expand the application that you want to customize in the left pane, and then click **Add**. In the **Add File Type Association** dialog box, provide the necessary information for the new FTA. To review the shortcut information associated with an application, under the application, select the **Shortcuts** check box, and in the **Location** pane, you can review the icon file information. To edit an existing FTA, click **Edit**. To remove an FTA, select the FTA, and then click **Remove**. Click **Next**.
-
-12. On the **Streaming** page, run each program so that it can be optimized and run more efficiently on target computers. It can take several minutes for all the applications to run. After all applications have run, close each of the applications, and then click **Next**.
-
- **Note**
- If you want to stop an application from loading during this step, in the **Application Launch** dialog box, click **Stop** and select either the **Stop all applications** or the **Stop this application only** check box, depending on what you want.
-
-
-
-13. On the **Create Package** page, select the **Continue to modify package without saving using the package editor** check box, to modify the package without saving it. When you select this option, the package in the sequencer console opens so that you can modify the package before it is saved. Click **Next**.
-
- Select the default **Save the package now**, to save the package immediately. Add optional **Comments** that will be associated with the package. Comments are useful for identifying version and other information about the package. The default **Save Location** is also displayed. To change the default location, click **Browse** and specify the new location. The uncompressed package size is displayed. If the package size exceeds 4 GB (uncompressed) and you plan to stream the package to target computers, you must select **Compress Package**. Click **Create**.
-
-14. On the **Completion** page, click **Close**. The package is now available in the sequencer.
-
-## Related topics
-
-
-[Tasks for the Application Virtualization Sequencer (App-V 4.6 SP1)](tasks-for-the-application-virtualization-sequencer--app-v-46-sp1-.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-modify-attributes-of-embedded-services.md b/mdop/appv-v4/how-to-modify-attributes-of-embedded-services.md
deleted file mode 100644
index 98cb2e695d..0000000000
--- a/mdop/appv-v4/how-to-modify-attributes-of-embedded-services.md
+++ /dev/null
@@ -1,62 +0,0 @@
----
-title: How to Modify Attributes of Embedded Services
-description: How to Modify Attributes of Embedded Services
-author: dansimp
-ms.assetid: b4057d3f-2e8f-4b1f-9ed5-b65f3da8631a
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Modify Attributes of Embedded Services
-
-
-After you sequence an application but before you save it, you can use the following procedure to manually modify the sequenced application package.
-
-**To remove an embedded service**
-
-1. Click the **Virtual Services** tab.
-
-2. Right-click the service you want to remove, and select **Remove**.
-
-3. In the **Sequencer** dialog box, click **Yes**.
-
-**To modify the properties of an embedded service**
-
-1. Click the **Virtual Services** tab.
-
-2. Right-click the service whose properties you want to modify, and select **Properties**.
-
-3. In the **Office Source Engine Properties** dialog box, complete the following tasks:
-
- 1. In the **Display Name** text box, type the name of the service.
-
- 2. In the **Description** text box, type a description of the service.
-
- 3. In the **Path to Executable** text box, enter the path to the executable file.
-
- 4. From the **Startup Type** drop down list, select how the service is to start up—manually, automatically, or not.
-
- 5. Click **OK**.
-
-## Related topics
-
-
-[About the Virtual Services Tab](about-the-virtual-services-tab.md)
-
-[Sequencer Console](sequencer-console.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-modify-file-mapping-information.md b/mdop/appv-v4/how-to-modify-file-mapping-information.md
deleted file mode 100644
index 8fdeaaf6cd..0000000000
--- a/mdop/appv-v4/how-to-modify-file-mapping-information.md
+++ /dev/null
@@ -1,78 +0,0 @@
----
-title: How to Modify File-Mapping Information
-description: How to Modify File-Mapping Information
-author: dansimp
-ms.assetid: d3a9d10a-6cc8-4399-9479-b20f729c4dd9
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Modify File-Mapping Information
-
-
-After you sequence an application but before you save it, you can manually modify the virtual file system. Use the following procedures to add, delete, or edit a file in the virtual file system.
-
-**To add a file in the file system**
-
-1. Click the **Virtual File System** tab.
-
-2. Right-click a file under the virtual file system root in the left pane. On the menu, select **Add**.
-
-3. Complete the following tasks in the **New Virtual File System Mapping** dialog box:
-
- 1. To specify the new file association type the full network path to the new file.
-
- 2. Click **OK**.
-
-4. To override the local directory, right-click the file you just added and, on the menu, select **Override Local Directory**; or to merge with the local directory, select **Merge with Local Directory**.
-
-5. On the **File** menu, select **Save** to save this change.
-
-**To delete a file in the file system**
-
-1. Click the **Virtual File System** tab.
-
-2. Right-click a file in the virtual file system, and select **Delete**.
-
-3. Accept the confirmation message by clicking **OK**.
-
-4. On the **File** menu, select **Save** to save this change.
-
-**To edit a file in the file system**
-
-1. Click the **Virtual File System** tab.
-
-2. Right-click a file in the virtual file system. On the menu, select **Edit**.
-
-3. Complete the following tasks in the **Edit Virtual File System Mapping** dialog box:
-
- 1. To edit the file association, specify the full network path to the new file.
-
- 2. Click **OK**.
-
-4. To override the local directory, right-click the file you just edited and, on the menu, select **Override Local Directory**.
-
-5. On the **File** menu, select **Save** to save this change.
-
-## Related topics
-
-
-[About the Virtual File System Tab](about-the-virtual-file-system-tab.md)
-
-[Sequencer Console](sequencer-console.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-modify-private-key-permissions-to-support-management-server-or-streaming-server.md b/mdop/appv-v4/how-to-modify-private-key-permissions-to-support-management-server-or-streaming-server.md
deleted file mode 100644
index f4c26c1e0a..0000000000
--- a/mdop/appv-v4/how-to-modify-private-key-permissions-to-support-management-server-or-streaming-server.md
+++ /dev/null
@@ -1,67 +0,0 @@
----
-title: How to Modify Private Key Permissions to Support Management Server or Streaming Server
-description: How to Modify Private Key Permissions to Support Management Server or Streaming Server
-author: dansimp
-ms.assetid: 1ebe86fa-0fbc-4512-aebc-0a5da991cd43
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 08/30/2016
----
-
-
-# How to Modify Private Key Permissions to Support Management Server or Streaming Server
-
-
-To support a more secure App-V installation, you can use the following procedures to modify private keys in either Windows Server 2003 or Windows Server 2008. To modify the permissions of the private key, you can use the Windows Server 2003 Resource Kit tool `WinHttpCertCfg.exe`.
-
-For Windows Server 2003, the procedure requires that a certificate that meets the prerequisites listed in this document is installed on the computer or computers on which you will install the App-V Management or Streaming Server. Additional information about using the `WinHttpCertCfg.exe` tool is available at .
-
-In Windows Server 2008, the process of changing the ACLs on the private key is much simpler. The certificate’s user interface can be used to manage private key permissions.
-
-**Note**
-The default security context is Network Service; however, a domain account can be used instead.
-
-
-
-**To manage private keys in Windows Server 2003**
-
-1. On the computer that will become the App-V Management or Streaming Server, type the following command in a command prompt to list the current permissions assigned to a specific certificate:
-
- `winhttpcertcfg -l -c LOCAL_MACHINE\My -s Name_of_cert`
-
-2. If necessary, modify the permissions of the certificate to provide read access to the security context that will be used for Management or Streaming Service:
-
- `winhttpcertcfg -g -c LOCAL_MACHINE\My -s Name_of_cert -a NetworkService`
-
-3. Verify that the security context was properly added by listing the permissions on the certificate:
-
- `winhttpcertcfg –l –c LOCAL_MACHINE\My –s Name_of_cert`
-
-**To manage private keys in Windows Server 2008**
-
-1. Create a Microsoft Management Console (MMC) with the *Certificates* snap-in that targets the *Local Machine* certificate store.
-
-2. Expand the MMC and select **Manage Private Keys**.
-
-3. On the **Security** tab, add the **Network Service** account with **Read** access.
-
-## Related topics
-
-
-[Configuring Certificates to Support App-V Management Server or Streaming Server](configuring-certificates-to-support-app-v-management-server-or-streaming-server.md)
-
-[Configuring Certificates to Support Secure Streaming](configuring-certificates-to-support-secure-streaming.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-modify-the-files-included-in-a-package.md b/mdop/appv-v4/how-to-modify-the-files-included-in-a-package.md
deleted file mode 100644
index 2b1f6f9355..0000000000
--- a/mdop/appv-v4/how-to-modify-the-files-included-in-a-package.md
+++ /dev/null
@@ -1,44 +0,0 @@
----
-title: How to Modify the Files Included in a Package
-description: How to Modify the Files Included in a Package
-author: dansimp
-ms.assetid: e331ac85-1c9c-49be-9d96-5444de38fd56
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Modify the Files Included in a Package
-
-
-After you sequence an application but before you save it, you can manually modify a sequenced application package to specify how it will retain its settings. Use the Sequencer attributes section to specify whether a file in a sequenced application package will be available to a specific user or to all users in the community.
-
-**To modify Sequencer attributes**
-
-1. Click the **Files** tab.
-
-2. Select **User Data** or **Application Data**, depending on how you want an application to retain its settings, and select **Override** to enable the client to overwrite the cached application.
-
-3. Click **Apply**.
-
-## Related topics
-
-
-[About the Files Tab](about-the-files-tab.md)
-
-[Sequencer Console](sequencer-console.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-modify-the-location-of-the-log-directory.md b/mdop/appv-v4/how-to-modify-the-location-of-the-log-directory.md
deleted file mode 100644
index 884b299f77..0000000000
--- a/mdop/appv-v4/how-to-modify-the-location-of-the-log-directory.md
+++ /dev/null
@@ -1,44 +0,0 @@
----
-title: How to Modify the Location of the Log Directory
-description: How to Modify the Location of the Log Directory
-author: dansimp
-ms.assetid: 8e222d29-6f58-43bb-9ea7-da9a2ebfa48c
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Modify the Location of the Log Directory
-
-
-The log directory location is where the Application Virtualization (App-V) Sequencer writes information about the sequencing of an application.
-
-Use the following procedure to change the location of the directory where the App-V Sequencer will save associated logs.
-
-**To modify the log directory location**
-
-1. To open the App-V Sequencer Console, on the computer running the App-V Sequencer, select **Start** / **Programs** / **Microsoft Application Virtualization** / **Microsoft Application Virtualization Sequencer**.
-
-2. To access the App-V Sequencer **Options** dialog box, select **Tools** / **Options**. On the **General** tab, specify the new directory location where you want the App-V Sequencer log file information to be saved. Alternatively, you can click **Browse** and use the **Browse For Folder** dialog box to specify a new location.
-
-3. To save the new location and close the **Options** dialog box, click **OK**.
-
-## Related topics
-
-
-[Configuring the Application Virtualization Sequencer](configuring-the-application-virtualization-sequencer.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-modify-the-location-of-the-scratch-directory.md b/mdop/appv-v4/how-to-modify-the-location-of-the-scratch-directory.md
deleted file mode 100644
index db5ae76ad1..0000000000
--- a/mdop/appv-v4/how-to-modify-the-location-of-the-scratch-directory.md
+++ /dev/null
@@ -1,42 +0,0 @@
----
-title: How to Modify the Location of the Scratch Directory
-description: How to Modify the Location of the Scratch Directory
-author: dansimp
-ms.assetid: 25ebc2fa-d532-4800-9825-9d08306fc2e0
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Modify the Location of the Scratch Directory
-
-
-The scratch directory is used by the App-V Sequencer to save temporary files during the sequencing of an application.
-
-**To modify the scratch directory location**
-
-1. To open the App-V Sequencer Console, on the computer running the App-V Sequencer, select **Start** / **Programs** / **Microsoft Application Virtualization** / **Microsoft Application Virtualization Sequencer**.
-
-2. To access the App-V Sequencer **Options** dialog box, select **Tools** / **Options**. On the **General** tab, specify the new scratch directory location where you want the App-V Sequencer temporary files to be saved. Alternatively, you can click **Browse** and use the **Browse For Folder** dialog box to specify a new location.
-
-3. To save the new location and close the **Options** dialog box, click **OK**.
-
-## Related topics
-
-
-[Configuring the Application Virtualization Sequencer](configuring-the-application-virtualization-sequencer.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-modify-the-log-directory-location.md b/mdop/appv-v4/how-to-modify-the-log-directory-location.md
deleted file mode 100644
index 59765268ac..0000000000
--- a/mdop/appv-v4/how-to-modify-the-log-directory-location.md
+++ /dev/null
@@ -1,51 +0,0 @@
----
-title: How to Modify the Log Directory Location
-description: How to Modify the Log Directory Location
-author: dansimp
-ms.assetid: 203c674f-8d46-4d42-9af0-245a2681fc0f
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Modify the Log Directory Location
-
-
-The log directory location is where the Application Virtualization (App-V) Sequencer writes information about the sequencing of an application.
-
-**Important**
-The log location directory must be located on the computer running the App-V Sequencer.
-
-
-
-Use the following procedure to change the location of the directory where the App-V Sequencer will save associated logs.
-
-**To modify the log directory location**
-
-1. To open the App-V Sequencer Console, on the computer running the App-V Sequencer, select **Start** / **Programs** / **Microsoft Application Virtualization** / **Microsoft Application Virtualization Sequencer**.
-
-2. To access the App-V Sequencer **Options** dialog box, select **Tools** / **Options**. On the **General** tab, specify the new directory location where you want the App-V Sequencer log file information to be saved. Alternatively, you can click **Browse** and use the **Browse For Folder** dialog box to specify a new location.
-
-3. To save the new location and close the **Options** dialog box, click **OK**.
-
-## Related topics
-
-
-[Application Virtualization Sequencer](application-virtualization-sequencer.md)
-
-[How to Configure the App-V Sequencer](how-to-configure-the-app-v-sequencer.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-modify-the-operating-systems-associated-with-an-existing-windows-installer-file.md b/mdop/appv-v4/how-to-modify-the-operating-systems-associated-with-an-existing-windows-installer-file.md
deleted file mode 100644
index 910e66507f..0000000000
--- a/mdop/appv-v4/how-to-modify-the-operating-systems-associated-with-an-existing-windows-installer-file.md
+++ /dev/null
@@ -1,55 +0,0 @@
----
-title: How to Modify the Operating Systems Associated With an Existing Windows Installer File
-description: How to Modify the Operating Systems Associated With an Existing Windows Installer File
-author: dansimp
-ms.assetid: 0633f7e2-aebf-4e00-be02-35bc59dec420
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Modify the Operating Systems Associated With an Existing Windows Installer File
-
-
-Use the following procedure to modify the operating system versions associated with an existing Windows Installer (**MSI**) file that was created by using the App-V Sequencer.
-
-**To modify the operating systems of an existing Windows Installer file**
-
-1. Install the App-V Sequencer on a computer in your environment that has only the operating system installed. Alternatively, you can install the Sequencer on a computer running a virtual environment—for example, Microsoft Virtual PC. This method is useful because it is easier to maintain a clean sequencing environment that you can reuse with minimal additional configuration. For more information about installing the App-V Sequencer, see [How to Install the Sequencer](how-to-install-the-sequencer.md).
-
-2. Copy the entire virtual application package that contains the Windows Installer file you want to modify to the computer running the Sequencer.
-
-3. To modify the Windows Installer file, open the Sequencer console, select **Package** / **Open**, and then browse to the location where the virtual application package associated with the Windows Installer file is saved.
-
-4. To add or remove operating systems, select the **Deployment** tab in the Sequencer console. To specify additional operating systems that will be associated with the Windows Installer file, select the desired operating system, and then click the arrow that points to the **Selected** operating system list control.
-
- To remove an operating system association, select the operating system you want to remove, and then click the arrow that points to the **Available** operating system list control.
-
-5. To create a new Windows Installer that will be associated with the virtual application package, select **Generate Microsoft Windows Installer (MSI) Package**. Alternatively, you can select **Tools** / **Create MSI**.
-
- **Note**
- If you select **Tools** / **Create MSI** to create a new Windows Installer file, you can skip **Step 6** of this procedure.
-
-
-
-6. To save the virtual application package, select **Package** / **Save**.
-
-## Related topics
-
-
-[Tasks for the Application Virtualization Sequencer](tasks-for-the-application-virtualization-sequencer.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-modify-the-scratch-directory-location.md b/mdop/appv-v4/how-to-modify-the-scratch-directory-location.md
deleted file mode 100644
index 55a1689ba0..0000000000
--- a/mdop/appv-v4/how-to-modify-the-scratch-directory-location.md
+++ /dev/null
@@ -1,53 +0,0 @@
----
-title: How to Modify the Scratch Directory Location
-description: How to Modify the Scratch Directory Location
-author: dansimp
-ms.assetid: 61ecb379-85be-4316-8023-a2c1811504e5
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Modify the Scratch Directory Location
-
-
-The scratch directory is used by the App-V Sequencer to save temporary files during the sequencing of an application.
-
-**Important**
-The specified scratch directory location should be located on the computer running the App-V Sequencer.
-
-
-
-Use the following procedure to modify the scratch directory location.
-
-**To modify the scratch directory location**
-
-1. To open the App-V Sequencer Console, on the computer running the App-V Sequencer, select **Start** / **Programs** / **Microsoft Application Virtualization** / **Microsoft Application Virtualization Sequencer**.
-
-2. To access the App-V Sequencer **Options** dialog box, select **Tools** / **Options**. On the **General** tab, specify the new scratch directory location where you want the App-V Sequencer temporary files to be saved. Alternatively, you can click **Browse** and use the **Browse For Folder** dialog box to specify a new location.
-
-3. To save the new location and close the **Options** dialog box, click **OK**.
-
-## Related topics
-
-
-[Application Virtualization Sequencer](application-virtualization-sequencer.md)
-
-[How to Create the Sequencer Package Root Directory](how-to-create-the-sequencer-package-root-directory.md)
-
-[How to Modify the Log Directory Location](how-to-modify-the-log-directory-location.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-modify-virtual-registry-key-information.md b/mdop/appv-v4/how-to-modify-virtual-registry-key-information.md
deleted file mode 100644
index 717a3d0b0b..0000000000
--- a/mdop/appv-v4/how-to-modify-virtual-registry-key-information.md
+++ /dev/null
@@ -1,70 +0,0 @@
----
-title: How to Modify Virtual Registry Key Information
-description: How to Modify Virtual Registry Key Information
-author: dansimp
-ms.assetid: cf2559f2-a8cc-4fc7-916e-8368843c7ebc
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Modify Virtual Registry Key Information
-
-
-After you sequence an application but before you save it, you can modify its registry settings. Use the following procedures to modify a sequenced application package's registry values and registry keys.
-
-**To modify a registry key**
-
-1. Click the **Virtual Registry Key** tab.
-
-2. Double-click the **Registry** folder to expand its contents.
-
-3. In the left pane, right-click the folder you want to modify and select **Key**.
-
-4. To create a new registry key, on the menu, select **New**. A new registry key will appear in the folder you selected.
-
-5. To rename a registry key, on the menu, select **Rename**. Type a new value name in the text box.
-
-6. To delete a registry key, on the menu, select **Delete**.
-
-7. To override the local key, on the menu, select **Override Local Key**, or to merge with the local key, select **Merge with Local Key**.
-
-**To modify a registry value**
-
-1. Click the **Virtual Registry Value** tab.
-
-2. Double-click the **Registry** folder to expand its contents.
-
-3. In the left pane, right-click the folder you want to modify and select **Value**.
-
-4. To add a string, on the menu, select **Add String**.
-
-5. To add a binary, on the menu, select **Add Binary**.
-
-6. To add a DWORD, on the menu, select **Add DWORD**.
-
-7. To delete a registry value, right-click a value and select **Delete**.
-
-8. To rename a registry value, right-click a registry value and select **Rename**.
-
-## Related topics
-
-
-[About the Virtual Registry Tab](about-the-virtual-registry-tab.md)
-
-[Sequencer Console](sequencer-console.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-move-an-application-group.md b/mdop/appv-v4/how-to-move-an-application-group.md
deleted file mode 100644
index 8ea5ba9d04..0000000000
--- a/mdop/appv-v4/how-to-move-an-application-group.md
+++ /dev/null
@@ -1,55 +0,0 @@
----
-title: How to Move an Application Group
-description: How to Move an Application Group
-author: dansimp
-ms.assetid: 7f9f9f2e-f394-4ad3-8615-4237a7dcfb95
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Move an Application Group
-
-
-In the Application Virtualization Server Management Console, you can use the following procedure to move an application group, which enables you to arrange your applications to suit your operations. You also can group them so that you can change the properties of nested groups simultaneously.
-
-**To move an application group**
-
-1. In the left pane of the Application Virtualization Server Management Console, expand **Applications** so that you can see the **Application** group you want to move.
-
-2. Right-click the group and choose **Move**.
-
-3. In the **Select Target** window, navigate to the application group under which you want to place this group.
-
-4. Click **OK**.
-
- The group, all its subgroups, and its existing applications now appear under the target group. This move does not change the properties of the group or its applications.
-
- **Note**
- You can select and move multiple application groups simultaneously. In the right pane, use the **CTRL**-click or **Shift**-click key combinations to select more than one group.
-
-
-
-## Related topics
-
-
-[How to Create an Application Group](how-to-create-an-application-group.md)
-
-[How to Manage Application Groups in the Server Management Console](how-to-manage-application-groups-in-the-server-management-console.md)
-
-[How to Manage Applications in the Server Management Console](how-to-manage-applications-in-the-server-management-console.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-move-an-application.md b/mdop/appv-v4/how-to-move-an-application.md
deleted file mode 100644
index 09e30ae09f..0000000000
--- a/mdop/appv-v4/how-to-move-an-application.md
+++ /dev/null
@@ -1,60 +0,0 @@
----
-title: How to Move an Application
-description: How to Move an Application
-author: dansimp
-ms.assetid: 3ebbf30c-b435-4a69-a0ba-2313aaf0017c
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Move an Application
-
-
-If you have application groups under the **Applications** node in the Application Virtualization Server Management Console, you can move an application between groups or from the main node to a group. You can move the applications to suit your operations. You also can group them so that you can change the properties of nested groups simultaneously.
-
-**Important**
-You must have one or more application groups under the **Applications** node to move applications.
-
-
-
-**To move an application**
-
-1. In the left pane of the Application Virtualization Server Management Console, expand **Applications**.
-
-2. Highlight the application you want to move.
-
-3. Right-click the application and choose **Move**.
-
-4. In the **Select Target** window, navigate to the group in which you want to place this group.
-
-5. Click **OK**.
-
- The applications now appear under the target group. This move does not change the properties of the group or its applications, and it does not move any of the application's files on the server.
-
- **Note**
- You can select and move multiple application groups simultaneously. In the right pane, use the **CTRL**-click or **Shift**-click key combinations to select more than one group.
-
-
-
-## Related topics
-
-
-[How to Create an Application Group](how-to-create-an-application-group.md)
-
-[How to Manage Applications in the Server Management Console](how-to-manage-applications-in-the-server-management-console.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-open-a-sequenced-application-using-the-command-line.md b/mdop/appv-v4/how-to-open-a-sequenced-application-using-the-command-line.md
deleted file mode 100644
index 21dbdb2640..0000000000
--- a/mdop/appv-v4/how-to-open-a-sequenced-application-using-the-command-line.md
+++ /dev/null
@@ -1,63 +0,0 @@
----
-title: How to Open a Sequenced Application Using the Command Line
-description: How to Open a Sequenced Application Using the Command Line
-author: dansimp
-ms.assetid: dc23ee65-8aea-470e-bb3f-a2f2b06cb241
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Open a Sequenced Application Using the Command Line
-
-
-You can open virtual application packages using the command line. You must run the **cmd** prompt as an administrator.
-
-Use the following procedure to open sequenced application packages using the command line
-
-**To open a sequenced application using the command line**
-
-1. To open the command prompt, click **Start**, and select **Run**, type **cmd**, and click **OK**.
-
-2. At a command prompt, type **cd\\** and specify the path to the directory where the Sequencer is installed and then press **Enter.**
-
-3. At the command prompt, type the following command, replacing the italicized text with your values:
-
- SFTSequencer /OPEN:*”specifies the .sprj file to open"*
-
- Press **Enter**.
-
-4. You can also specify the following optional parameters. At the command prompt, type the following commands, replacing the italicized text with your values:
-
- /PACKAGENAME:"*specifies the package name"*
-
- /MSI - specifies generating an associated Microsoft Windows Installer.
-
- /COMPRESS – specifies if the package will be compressed. By default, packages are not compressed.
-
- Press **Enter**.
-
- **Note**
- If the installer or Windows Installer package has a graphical user interface, it will be displayed after you specify the command-line parameters.
-
-
-
-## Related topics
-
-
-[How to Manage Virtual Applications Using the Command Line](how-to-manage-virtual-applications-using-the-command-line.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-perform-administrative-tasks-in-the-application-virtualization-server-management-console.md b/mdop/appv-v4/how-to-perform-administrative-tasks-in-the-application-virtualization-server-management-console.md
deleted file mode 100644
index 9c58f5b780..0000000000
--- a/mdop/appv-v4/how-to-perform-administrative-tasks-in-the-application-virtualization-server-management-console.md
+++ /dev/null
@@ -1,62 +0,0 @@
----
-title: How to Perform Administrative Tasks in the Application Virtualization Server Management Console
-description: How to Perform Administrative Tasks in the Application Virtualization Server Management Console
-author: dansimp
-ms.assetid: b80e39eb-4b2a-4f66-8c85-dd5712efed33
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Perform Administrative Tasks in the Application Virtualization Server Management Console
-
-
-You have a wide range of configuration and control operations for one or more Application Virtualization Management Servers. The Application Virtualization Server Management Console provides local or remote access to your servers.
-
-## In This Section
-
-
-[How to Connect to an Application Virtualization System](how-to-connect-to-an-application-virtualization-system.md)
-Provides steps for connecting to an Application Virtualization System in the Application Virtualization Management Server Management Console.
-
-[How to Manage Applications in the Server Management Console](how-to-manage-applications-in-the-server-management-console.md)
-Provides procedures for managing applications in the Application Virtualization Server Management Console.
-
-[How to Manage Application Groups in the Server Management Console](how-to-manage-application-groups-in-the-server-management-console.md)
-Provides procedures for managing application groups in the Application Virtualization Server Management Console.
-
-[How to Manage Packages in the Server Management Console](how-to-manage-packages-in-the-server-management-console.md)
-Provides procedures for managing packages in the Application Virtualization Server Management Console.
-
-[How to Manage Reports in the Server Management Console](how-to-manage-reports-in-the-server-management-console.md)
-Provides procedures for managing reports in the Application Virtualization Server Management Console.
-
-[How to Manage Servers in the Server Management Console](how-to-manage-servers-in-the-server-management-console.md)
-Provides procedures for managing Application Virtualization Management Servers in the Application Virtualization Server Management Console.
-
-[How to Manage Application Licenses in the Server Management Console](how-to-manage-application-licenses-in-the-server-management-console.md)
-Provides procedures for managing licenses in the Application Virtualization Server Management Console.
-
-[How to Customize an Application Virtualization System in the Server Management Console](how-to-customize-an-application-virtualization-system-in-the-server-management-console.md)
-Provides procedures for customizing an Application Virtualization System in the Application Virtualization Server Management Console.
-
-[How to Change the Server Logging Level and the Database Parameters](how-to-change-the-server-logging-level-and-the-database-parameters.md)
-Provides procedures for changing the logging level and the database log parameters in the Application Virtualization Server Management Console.
-
-[How to Configure Microsoft SQL Server Mirroring Support for App-V](how-to-configure-microsoft-sql-server-mirroring-support-for-app-v.md)
-Describes how to configure database mirroring by using Microsoft SQL Server for your App-V system.
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-perform-general-administrative-tasks-in-the-app-v-client-management-console.md b/mdop/appv-v4/how-to-perform-general-administrative-tasks-in-the-app-v-client-management-console.md
deleted file mode 100644
index 343308dd05..0000000000
--- a/mdop/appv-v4/how-to-perform-general-administrative-tasks-in-the-app-v-client-management-console.md
+++ /dev/null
@@ -1,54 +0,0 @@
----
-title: How to Perform General Administrative Tasks in the App-V Client Management Console
-description: How to Perform General Administrative Tasks in the App-V Client Management Console
-author: dansimp
-ms.assetid: 22abdb1e-ab35-440d-bf74-d358dd1a6558
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Perform General Administrative Tasks in the App-V Client Management Console
-
-
-The App-V Client Management Console enables users who are local administrators to manage their applications.
-
-## In This Section
-
-
-[How to Set Up Publishing Servers](how-to-set-up-publishing-servers.md)
-Provides procedures for setting up App-V Servers and for adding more App-V Servers to both the App-V Desktop Client and the App-V Client for Remote Desktop Services (formerly Terminal Services).
-
-[How to Refresh the Publishing Servers](how-to-refresh-the-publishing-servers.md)
-Provides a procedure for refreshing the App-V Servers from the App-V Client Management Console.
-
-[How to Disable or Modify Disconnected Operation Mode Settings](how-to-disable-or-modify-disconnected-operation-mode-settings.md)
-Provides procedures for disabling or modifying disconnected operation mode settings.
-
-[User Access Permissions in Application Virtualization Client](user-access-permissions-in-application-virtualization-client.md)
-Provides the list of user access permissions.
-
-[Disconnected Operation Mode](disconnected-operation-mode.md)
-Describes the disconnected operation mode and circumstances that affect it.
-
-## Related topics
-
-
-[Application Virtualization Client](application-virtualization-client.md)
-
-[How to Configure the Client in the Application Virtualization Client Management Console](how-to-configure-the-client-in-the-application-virtualization-client-management-console.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-perform-general-administrative-tasks-in-the-client-management-console.md b/mdop/appv-v4/how-to-perform-general-administrative-tasks-in-the-client-management-console.md
deleted file mode 100644
index 6680c9eb75..0000000000
--- a/mdop/appv-v4/how-to-perform-general-administrative-tasks-in-the-client-management-console.md
+++ /dev/null
@@ -1,52 +0,0 @@
----
-title: How to Perform General Administrative Tasks in the Client Management Console
-description: How to Perform General Administrative Tasks in the Client Management Console
-author: dansimp
-ms.assetid: 90bb7101-1075-4654-8a5e-ad08374e381f
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Perform General Administrative Tasks in the Client Management Console
-
-
-The Application Virtualization Client Management Console enables users who are local administrators to manage their applications.
-
-## In This Section
-
-
-[How to Set Up Publishing Servers](how-to-set-up-publishing-servers.md)
-Provides procedures for adding more Application Virtualization Servers to the Application Virtualization Desktop Client or Client for Remote Desktop Services (formerly Terminal Services) and for setting up those servers.
-
-[How to Refresh the Publishing Servers](how-to-refresh-the-publishing-servers.md)
-Provides a procedure for refreshing the Application Virtualization Servers from the Client Management Console.
-
-[How to Disable or Modify Disconnected Operation Mode Settings](how-to-disable-or-modify-disconnected-operation-mode-settings.md)
-Provides procedures you can use to disable or modify disconnected operation mode settings.
-
-## Related topics
-
-
-[Application Virtualization Client Management Console Overview](application-virtualization-client-management-console-overview.md)
-
-[How to Configure the Client in the Application Virtualization Client Management Console](how-to-configure-the-client-in-the-application-virtualization-client-management-console.md)
-
-[How to Manage Applications in the Client Management Console](how-to-manage-applications-in-the-client-management-console.md)
-
-[How to Manually Manage Applications in the Client Management Console](how-to-manually-manage-applications-in-the-client-management-console.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-print-a-reportserver.md b/mdop/appv-v4/how-to-print-a-reportserver.md
deleted file mode 100644
index b5032610a5..0000000000
--- a/mdop/appv-v4/how-to-print-a-reportserver.md
+++ /dev/null
@@ -1,48 +0,0 @@
----
-title: How to Print a Report
-description: How to Print a Report
-author: dansimp
-ms.assetid: 9cb3a2f1-69bf-47b2-b2cf-8afdcd77138f
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Print a Report
-
-
-The process for printing a report for the Application Virtualization Server Management Console is the same regardless of the report type.
-
-**To print a report**
-
-1. After the report output is displayed in the **Results** pane, click the **Printer** button (at the top of the **Results** pane) or right-click the desired report under the **Reports** node and select **Print** from the pop-up menu.
-
-2. Follow the printing prompts, and click **OK**.
-
-## Related topics
-
-
-[Application Virtualization Report Types](application-virtualization-report-types.md)
-
-[How to Create a Report](how-to-create-a-reportserver.md)
-
-[How to Delete a Report](how-to-delete-a-reportserver.md)
-
-[How to Export a Report](how-to-export-a-reportserver.md)
-
-[How to Run a Report](how-to-run-a-reportserver.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-publish-a-virtual-application-on-the-client.md b/mdop/appv-v4/how-to-publish-a-virtual-application-on-the-client.md
deleted file mode 100644
index 50cea0dd3a..0000000000
--- a/mdop/appv-v4/how-to-publish-a-virtual-application-on-the-client.md
+++ /dev/null
@@ -1,71 +0,0 @@
----
-title: How to Publish a Virtual Application on the Client
-description: How to Publish a Virtual Application on the Client
-author: dansimp
-ms.assetid: 90af843e-b5b3-4a71-a3a1-fa5f4c087f28
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Publish a Virtual Application on the Client
-
-
-When you deploy Application Virtualization by using an electronic software distribution system, you can use one of the following procedures to publish an application package to your users.
-
-**To publish a package using a stand-alone Windows Installer file**
-
-1. The client should be installed with the *REQUIREAUTHORIZATIONIFCACHED* parameter set to 0 (zero). For more information about setting this parameter, see [Application Virtualization Client Installer Command-Line Parameters](application-virtualization-client-installer-command-line-parameters.md)
-
-2. Copy the Windows Installer file and the SFT file to same folder on the target computer.
-
-3. Run the following command on the computer:
-
- `Msiexec.exe /I "packagename.msi" /q`
-
-**To publish a package using Windows Installer and the package manifest**
-
-1. Copy the Windows Installer file to the target computer and the SFT file to the CONTENT share on the streaming server.
-
-2. Run the following command on each user’s computer:
-
- `Msiexec.exe /I "\\pathtomsi\packagename.msi" MODE=STREAMING OVERRIDEURL="\\\\server\\share\\package.sft" LOAD=TRUE /q`
-
- **Important**
- For OVERRIDEURL all backslash characters must be escaped using a preceding backslash, or the OVERRIDEURL path will not be parsed correctly. Also, properties and values must be entered as uppercase except where the value is a path to a file.
-
-
-
-**To publish a package using SFTMIME**
-
-- For an example of how to publish an application for all users on a computer, run the following command on the user’s computer:
-
- `SFTMIME ADD PACKAGE:package-name /MANIFEST manifest-path [/GLOBAL] [/LOG log-pathname | /CONSOLE | /GUI]`
-
- For additional details about these and other SFTMIME commands, see [SFTMIME Command Reference](sftmime--command-reference.md).
-
-## Related topics
-
-
-[Determine Your Publishing Method](determine-your-publishing-method.md)
-
-[Electronic Software Distribution-Based Scenario](electronic-software-distribution-based-scenario.md)
-
-[SFTMIME Command Reference](sftmime--command-reference.md)
-
-[Stand-Alone Delivery Scenario for Application Virtualization Clients](stand-alone-delivery-scenario-for-application-virtualization-clients.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-publish-application-shortcuts.md b/mdop/appv-v4/how-to-publish-application-shortcuts.md
deleted file mode 100644
index 6d4a244cfe..0000000000
--- a/mdop/appv-v4/how-to-publish-application-shortcuts.md
+++ /dev/null
@@ -1,64 +0,0 @@
----
-title: How to Publish Application Shortcuts
-description: How to Publish Application Shortcuts
-author: dansimp
-ms.assetid: fc5efe86-1bbe-438b-b7d8-4f9b815cc58e
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Publish Application Shortcuts
-
-
-You can use the following procedure to publish shortcuts to an application directly from the **Results** pane of the **Application** node in the Application Virtualization Client Management Console.
-
-**To publish application shortcuts**
-
-1. Move the cursor to the **Results** pane, right-click the desired application, and select **New Shortcut** from the pop-up menu to display the New Shortcut Wizard.
-
-2. On the first page of the New Shortcut Wizard, select an icon and specify a name for the shortcut.
-
- 1. **Change Icon**—Displays a standard Windows icon browser. Browse to and select the desired icon.
-
- 2. **Shortcut Title**—Enter the name you want to give the shortcut. This field defaults to the existing name and version of the application.
-
-3. On the second page of the wizard, determine the location of the published shortcut.
-
- 1. **The Desktop**—Select this check box to publish the shortcut to the desktop.
-
- 2. **The Quick Launch Toolbar**—Select this check box to publish the shortcut to the Quick Launch toolbar.
-
- 3. **The Send To Menu**—Select this check box to publish the shortcut to the **Send To** menu.
-
- 4. **Programs in the Start Menu**—When you select the **Start Menu** check box, this field becomes active. Leave this field blank to publish the shortcut directly to the root of the Programs folder, or enter a folder name or hierarchy—for example, "My\_Computer\\Office Applications." Shortcuts created this way are available only for the current user.
-
- 5. **Another location** and **Browse** button—When you select the **Another location** check box, this field becomes active. Enter any valid location on the computer or any available UNC path (shared file or directory on a network). The **Browse** button displays a standard Windows **File Open** dialog box.
-
-4. On the third page of the wizard, enter desired command-line parameters.
-
-5. Click **Finish** to publish the shortcuts and exit to the **Results** pane.
-
-## Related topics
-
-
-[How to Add a File Type Association](how-to-add-a-file-type-association.md)
-
-[How to Add an Application](how-to-add-an-application.md)
-
-[How to Delete a File Type Association](how-to-delete-a-file-type-association.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-refresh-the-publishing-servers.md b/mdop/appv-v4/how-to-refresh-the-publishing-servers.md
deleted file mode 100644
index a0e9a2926b..0000000000
--- a/mdop/appv-v4/how-to-refresh-the-publishing-servers.md
+++ /dev/null
@@ -1,56 +0,0 @@
----
-title: How to Refresh the Publishing Servers
-description: How to Refresh the Publishing Servers
-author: dansimp
-ms.assetid: 92e1d7b0-10ee-4531-9049-1056b44934e2
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Refresh the Publishing Servers
-
-
-After you request access to additional applications and permission is granted by the system administrator, you must refresh the publishing information from the Application Virtualization Servers before the applications appear on your desktop. You can accomplish this directly from the Windows desktop notification area.
-
-**Note**
-By default, publishing information is refreshed on user log in.
-
-
-
-**To refresh the publishing information**
-
-1. Right-click the Application Virtualization System icon in the notification area.
-
-2. Select **Refresh Applications** from the pop-up-menu. The new shortcuts appear where designated by the system administrator—for example, on your desktop, **Start** menu, or **Quick Launch** menu, depending on the configuration of the Application Virtualization Server and your desktop.
-
- **Note**
- Following are additional ways you can refresh the publishing information from the servers:
-
- - Right-click the server in the **Results** pane, and select **Refresh Server** from the pop-up menu.
-
- - Right-click the server in the **Results** pane, and then select **Properties** from the pop-up menu. Select the **Refresh** tab, and then click the **Refresh** button.
-
-
-
-## Related topics
-
-
-[How to Set Up Periodic Publishing Refresh](how-to-set-up-periodic-publishing-refresh.md)
-
-[How to Set Up Publishing Refresh on Login](how-to-set-up-publishing-refresh-on-login.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-refresh-virtual-applications-from-the-desktop-notification-area.md b/mdop/appv-v4/how-to-refresh-virtual-applications-from-the-desktop-notification-area.md
deleted file mode 100644
index 7933691955..0000000000
--- a/mdop/appv-v4/how-to-refresh-virtual-applications-from-the-desktop-notification-area.md
+++ /dev/null
@@ -1,42 +0,0 @@
----
-title: How to Refresh Virtual Applications from the Desktop Notification Area
-description: How to Refresh Virtual Applications from the Desktop Notification Area
-author: dansimp
-ms.assetid: 801610d9-e89c-48bb-972c-20e37b945a02
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Refresh Virtual Applications from the Desktop Notification Area
-
-
-To refresh the list of available applications and the associated shortcuts and file type associations, you must refresh the publishing information from the Application Virtualization (App-V) Management Server or the Application Virtualization (App-V) Streaming Server before the applications appear on your desktop. You can accomplish this directly from the notification area on your desktop.
-
-**To refresh the virtual applications from the client desktop**
-
-1. Right-click the Application Virtualization System icon in the notification area.
-
-2. Select **Refresh Applications** from the pop-up-menu.
-
- Your desktop is updated, and the client reflects any changes in applications, shortcuts, and file type associations. This applies only when a publishing server has been defined.
-
-## Related topics
-
-
-[How to Use the Desktop Notification Area for Application Virtualization Client Management](how-to-use-the-desktop-notification-area-for-application-virtualization-client-management.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-remove-a-package-by-using-the-command-line.md b/mdop/appv-v4/how-to-remove-a-package-by-using-the-command-line.md
deleted file mode 100644
index d0f45a1774..0000000000
--- a/mdop/appv-v4/how-to-remove-a-package-by-using-the-command-line.md
+++ /dev/null
@@ -1,62 +0,0 @@
----
-title: How to Remove a Package by Using the Command Line
-description: How to Remove a Package by Using the Command Line
-author: dansimp
-ms.assetid: 47697ec7-20e5-4258-8865-a0a710d41d5a
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Remove a Package by Using the Command Line
-
-
-You can use the following command-line procedures to delete a virtual application package from the Application Virtualization (App-V) Client on a specific computer.
-
-**To delete a virtual application package for all users**
-
-- If the package was previously added for all users by using the /GLOBAL switch, use the following command to delete the package and the global file types and shortcuts. Administrator rights are required. The /GLOBAL switch is not needed in this case because the command always performs a global deletion of the package.
-
- `SFTMIME DELETE PACKAGE:”name”`
-
-**To delete a package previously added for individual users**
-
-1. If the package was previously added for individual users, you have several options.
-
- Run the following command once under the user account of each person the package was published to. This denies the user access to the applications if they roam to another computer. It deletes the specific user’s settings, shortcuts, and file types from the profile, and it stops background loads under the user’s context.
-
- `SFTMIME UNPUBLISH PACKAGE:”name”`
-
-2. Alternatively, run the following command under the user account of each person the package was published to.
-
- `SFTMIME UNPUBLISH PACKAGE:”name”`
-
- Then run this command for the package.
-
- `SFTMIME DELETE PACKAGE:”name”`
-
- This completely removes the package, and it deletes all user settings, shortcuts, and file types from their profiles. If the package is subsequently re-added, the users will have to specify their settings again. Only “Delete applications” (**DeleteApp**) permission is needed to run this command.
-
-3. As a third alternative, you can simply run the **DELETE PACKAGE** command without using the **UNPUBLISH PACKAGE** command. In this case, file types and shortcuts for each user are hidden rather than deleted, and the user settings are retained. This means that if the package is subsequently re-added for the user, the file types and shortcuts are restored, and the user settings are reapplied.
-
-## Related topics
-
-
-[How to Add a Package by Using the Command Line](how-to-add-a-package-by-using-the-command-line.md)
-
-[How to Delete All Virtual Applications by Using the Command Line](how-to-delete-all-virtual-applications-by-using-the-command-line.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-remove-a-server-group.md b/mdop/appv-v4/how-to-remove-a-server-group.md
deleted file mode 100644
index e7575feff4..0000000000
--- a/mdop/appv-v4/how-to-remove-a-server-group.md
+++ /dev/null
@@ -1,46 +0,0 @@
----
-title: How to Remove a Server Group
-description: How to Remove a Server Group
-author: dansimp
-ms.assetid: 3017f4f4-614b-4db4-834c-b6fd9b45f10c
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Remove a Server Group
-
-
-You can use the following procedure in the Application Virtualization Server Management Console to remove server groups, including all the servers in the group, from your Application Virtualization System.
-
-**To remove a server group**
-
-1. Click the **Server Groups** node in the left pane to expand the list of server groups.
-
-2. Right-click the desired server group, and select **Delete**.
-
-3. At the prompt, click **Yes**.
-
-## Related topics
-
-
-[How to Add a Server](how-to-add-a-server.md)
-
-[How to Create a Server Group](how-to-create-a-server-group.md)
-
-[How to Remove a Server](how-to-remove-a-server.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-remove-a-server.md b/mdop/appv-v4/how-to-remove-a-server.md
deleted file mode 100644
index bccd5fb64d..0000000000
--- a/mdop/appv-v4/how-to-remove-a-server.md
+++ /dev/null
@@ -1,46 +0,0 @@
----
-title: How to Remove a Server
-description: How to Remove a Server
-author: dansimp
-ms.assetid: afb2a889-733c-4058-9a50-caa2ca10bd58
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Remove a Server
-
-
-To help you manage your servers more efficiently, organize them into server groups. After you create a server group in the Application Virtualization Server Management Console, you can remove servers from the group.
-
-**To remove a server from a group**
-
-1. Click the **Server Groups** node in the left pane to expand the list of server groups.
-
-2. In the right pane, right-click the desired server and select **Delete**.
-
-3. At the prompt, click **Yes**.
-
-## Related topics
-
-
-[How to Add a Server](how-to-add-a-server.md)
-
-[How to Create a Server Group](how-to-create-a-server-group.md)
-
-[How to Remove a Server Group](how-to-remove-a-server-group.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-remove-an-application-from-a-license-group.md b/mdop/appv-v4/how-to-remove-an-application-from-a-license-group.md
deleted file mode 100644
index 8d0d072de5..0000000000
--- a/mdop/appv-v4/how-to-remove-an-application-from-a-license-group.md
+++ /dev/null
@@ -1,49 +0,0 @@
----
-title: How to Remove an Application from a License Group
-description: How to Remove an Application from a License Group
-author: dansimp
-ms.assetid: 973dfb11-b4d1-4b79-8f6a-aaea3e52b04f
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Remove an Application from a License Group
-
-
-You can use the following procedure to remove an application from its assigned license group in the Application Virtualization Server Management Console. After you do this, you cannot apply license controls or use reports to track the license usage for this application.
-
-**To remove an application from a license group**
-
-1. In the left pane of the management console, click and expand the **Applications** node.
-
-2. Right-click the desired application, and choose **Properties**.
-
-3. On the **General** tab, use the **Application License Group** pull-down menu to choose **<none>**.
-
-4. Click **OK**.
-
- **Note**
- You can alter the **Properties** tab of one application at a time.
-
-
-
-## Related topics
-
-
-[How to Associate an Application with a License Group](how-to-associate-an-application-with-a-license-group.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-remove-an-application-group.md b/mdop/appv-v4/how-to-remove-an-application-group.md
deleted file mode 100644
index 04c1069006..0000000000
--- a/mdop/appv-v4/how-to-remove-an-application-group.md
+++ /dev/null
@@ -1,68 +0,0 @@
----
-title: How to Remove an Application Group
-description: How to Remove an Application Group
-author: dansimp
-ms.assetid: 3016b373-f5a0-4c82-96e8-e5e7960f0cc4
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Remove an Application Group
-
-
-You can use the following procedures to remove an application group in the Application Virtualization Server Management Console in one of two ways:
-
-**Caution**
-Deleting a group with its applications deletes those applications from the Application Virtualization Management Server. When you try to do this, you must confirm the deletion in a pop-up window.
-
-
-
-**To empty and then delete an application group**
-
-1. In the Application Virtualization Server Management Console, expand **Applications** in the left pane and select the **Application** group you want to remove.
-
-2. In the right pane, select the applications and application groups you want to keep. You can use the **CTRL** and **Shift** keys to select multiple applications and application groups.
-
-3. Right-click the selected applications, and choose **Move**.
-
-4. In the **Select Target** window, navigate to the new location and click **OK**. Repeat this step if you want to move different applications to more than one group.
-
-5. When you finish moving the applications you want to keep, right-click the application group and choose **Delete**.
-
-6. Click **Yes** to confirm.
-
-**To delete the group, with all its child groups and its applications**
-
-1. In the Application Virtualization Server Management Console, expand **Applications** in the left pane.
-
-2. Right-click the application group you want to remove, and choose **Delete**.
-
-3. Click **Yes** to confirm.
-
- **Note**
- You can select and remove multiple application groups simultaneously. In the right pane, use the **CTRL**-click or **Shift**-click key combinations to select more than one group.
-
-
-
-## Related topics
-
-
-[How to Manage Application Groups in the Server Management Console](how-to-manage-application-groups-in-the-server-management-console.md)
-
-[How to Manage Applications in the Server Management Console](how-to-manage-applications-in-the-server-management-console.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-remove-an-application-license-group.md b/mdop/appv-v4/how-to-remove-an-application-license-group.md
deleted file mode 100644
index 6e686e7f7b..0000000000
--- a/mdop/appv-v4/how-to-remove-an-application-license-group.md
+++ /dev/null
@@ -1,61 +0,0 @@
----
-title: How to Remove an Application License Group
-description: How to Remove an Application License Group
-author: dansimp
-ms.assetid: 35830916-7015-44cd-829b-23599a5029a7
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Remove an Application License Group
-
-
-In the Application Virtualization Server Management Console, you can use the following procedure to remove an application license group. After you do this, you will be unable to apply license controls or use reports to track the licenses.
-
-**Important**
-Before you can remove a license group, you must remove any licenses associated with the group.
-
-
-
-**To remove a license group**
-
-1. In the left pane of the Application Virtualization Server Management Console, click and expand the **Applications Licenses** node.
-
-2. Click the desired **License Group**.
-
-3. In the right pane, right-click the license and select **Delete**.
-
-4. Click **Yes** at the prompt.
-
-5. In the left pane, right-click the desired license group and select **Delete**.
-
-## Related topics
-
-
-[How to Associate an Application with a License Group](how-to-associate-an-application-with-a-license-group.md)
-
-[How to Create an Application License Group](how-to-create-an-application-license-group.md)
-
-[How to Remove an Application from a License Group](how-to-remove-an-application-from-a-license-group.md)
-
-[How to Set Up a Concurrent License Group](how-to-set-up-a-concurrent-license-group.md)
-
-[How to Set Up a Named License Group](how-to-set-up-a-named-license-group.md)
-
-[How to Set Up an Unlimited License Group](how-to-set-up-an-unlimited-license-group.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-remove-the-application-virtualization-system-components.md b/mdop/appv-v4/how-to-remove-the-application-virtualization-system-components.md
deleted file mode 100644
index 40b1a72de1..0000000000
--- a/mdop/appv-v4/how-to-remove-the-application-virtualization-system-components.md
+++ /dev/null
@@ -1,56 +0,0 @@
----
-title: How to Remove the Application Virtualization System Components
-description: How to Remove the Application Virtualization System Components
-author: dansimp
-ms.assetid: 45bb1e43-8708-48b7-9169-e3659f32686f
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Remove the Application Virtualization System Components
-
-
-You can use the following procedures to remove all or selected Application Virtualization software components from a target computer.
-
-**To remove all components from a single computer**
-
-1. From the Windows desktop, click **Start > Settings > Control Panel**.
-
-2. In the Control Panel window, double-click **Add or Remove Programs**.
-
-3. On the **Add or Remove Programs** page, select **Microsoft System Center Application Virtual Management Server** or **Microsoft System Center Application Streaming Server**, click **Remove**, and then click **Yes** at the prompt to remove all Application Virtualization software components from the computer.
-
-**To remove one or more components from a computer**
-
-1. Navigate to the location of the Application Virtualization System setup program on the network, either run this program from the network or copy its directory to the target computer, and then double-click **Setup.exe**.
-
-2. On the **Welcome** page, click **Next**.
-
-3. On the **Program Maintenance** page, select **Modify** and then click **Next**.
-
-4. On the **Custom Setup** page, deselect the Application Virtualization component or components you want to remove, and then click **Next**.
-
-5. On the **Ready to Modify the Program** page, to remove the selected components, click **Install**.
-
-6. On the **Installation Wizard Completed** page, to close the wizard click **Finish**. Click **Yes** to restart the computer.
-
-## Related topics
-
-
-[How to Install the Servers and System Components](how-to-install-the-servers-and-system-components.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-rename-an-application-group.md b/mdop/appv-v4/how-to-rename-an-application-group.md
deleted file mode 100644
index a1ee2619d3..0000000000
--- a/mdop/appv-v4/how-to-rename-an-application-group.md
+++ /dev/null
@@ -1,46 +0,0 @@
----
-title: How to Rename an Application Group
-description: How to Rename an Application Group
-author: dansimp
-ms.assetid: 4dfd3336-ea9a-4a56-91e1-7e9d742c7b9a
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Rename an Application Group
-
-
-From the Application Virtualization Server Management Console, you can use the following procedure to rename an application group without affecting any of its properties or those of the applications in it.
-
-**To rename an application group**
-
-1. In the management console, expand **Applications** in the left pane.
-
-2. Right-click the **Applications** group, and choose **Rename**.
-
-3. Type the new name for the group, and press **Enter**.
-
- Alternately, you can highlight the group and press **F2**. Then type the new name, and press **Enter**
-
-## Related topics
-
-
-[How to Manage Application Groups in the Server Management Console](how-to-manage-application-groups-in-the-server-management-console.md)
-
-[How to Manage Applications in the Server Management Console](how-to-manage-applications-in-the-server-management-console.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-rename-an-application.md b/mdop/appv-v4/how-to-rename-an-application.md
deleted file mode 100644
index d039ae22e5..0000000000
--- a/mdop/appv-v4/how-to-rename-an-application.md
+++ /dev/null
@@ -1,47 +0,0 @@
----
-title: How to Rename an Application
-description: How to Rename an Application
-author: dansimp
-ms.assetid: 983136b7-66bf-49f6-8dea-8933b622072d
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Rename an Application
-
-
-You can rename an application through the Application Virtualization Server Management Console.
-
-**To rename an application**
-
-1. In the left pane of the management console, click **Applications**.
-
-2. Right-click the application and choose **Rename**.
-
-3. Enter the new name and press **Enter**, or click outside of the box to cancel.
-
- **Note**
- You can also highlight the application in the right pane and press **F2**.
-
-
-
-## Related topics
-
-
-[How to Manage Applications in the Server Management Console](how-to-manage-applications-in-the-server-management-console.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-repair-an-application.md b/mdop/appv-v4/how-to-repair-an-application.md
deleted file mode 100644
index a6a164f1df..0000000000
--- a/mdop/appv-v4/how-to-repair-an-application.md
+++ /dev/null
@@ -1,37 +0,0 @@
----
-title: How to Repair an Application
-description: How to Repair an Application
-author: dansimp
-ms.assetid: 80b08416-ad86-4ed6-966a-b943e3efb951
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Repair an Application
-
-
-To repair a selected application, you can perform the following procedure directly from the **Results** pane of the **Application** node in the Application Virtualization Client Management Console. When you repair an application, you remove any custom user settings and restore the default settings. This action does not change or delete shortcuts or file type associations, and it does not remove the application from cache.
-
-**To repair an application**
-
-1. Move the cursor to the **Results** pane.
-
-2. Right-click the desired application, and select **Repair** from the pop-up menu.
-
-3. At the confirmation prompt, click **Yes** to repair the application or **No** to cancel.
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-reset-the-filesystem-cache.md b/mdop/appv-v4/how-to-reset-the-filesystem-cache.md
deleted file mode 100644
index f419abda81..0000000000
--- a/mdop/appv-v4/how-to-reset-the-filesystem-cache.md
+++ /dev/null
@@ -1,42 +0,0 @@
----
-title: How to Reset the FileSystem Cache
-description: How to Reset the FileSystem Cache
-author: dansimp
-ms.assetid: 7777259d-8c21-4c06-9384-9599b69f9828
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Reset the FileSystem Cache
-
-
-Resetting the FileSystem cache is not something that should usually be necessary. However if you need to completely reset the FileSystem cache, perhaps for troubleshooting purposes, you can use the following procedure. Administrative rights are required to perform this action.
-
-**To reset the FileSystem cache**
-
-1. Set the following registry value to 0 (zero):
-
- HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Microsoft\\SoftGrid\\4.5\\Client\\AppFS\\State
-
-2. Restart the computer.
-
-## Related topics
-
-
-[How to Configure the App-V Client Registry Settings by Using the Command Line](how-to-configure-the-app-v-client-registry-settings-by-using-the-command-line.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-run-a-reportserver.md b/mdop/appv-v4/how-to-run-a-reportserver.md
deleted file mode 100644
index 989628b502..0000000000
--- a/mdop/appv-v4/how-to-run-a-reportserver.md
+++ /dev/null
@@ -1,65 +0,0 @@
----
-title: How to Run a Report
-description: How to Run a Report
-author: dansimp
-ms.assetid: 72a5419b-aa65-4e60-b23e-3751186b7aed
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Run a Report
-
-
-The process for running a report is the same regardless of the report type. When you select a report type in the Application Virtualization Server Management Console, the window displays a brief description of the selected report.
-
-**Note**
-Reports are not run automatically; you must run them explicitly to generate output data. The length of time it takes to run a report is determined by the amount of data collected in the data store.
-
-
-
-**To run a report**
-
-1. Click the **Reports** node in the navigation pane.
-
-2. Right-click the desired report, and select **Run Report** from the pop-up menu.
-
-3. The pages you must complete to run a report vary depending on the type of report. To run a report, complete the appropriate pages from the following list:
-
- 1. Select a **Report Period** radio button to specify the frequency for running the report.
-
- 2. Specify the start date and end date in the respective fields to determine the range of dates included in the report. You can enter these dates manually or use the calendar function and select the dates.
-
- 3. Select the **Server**, **Server Group**, or **Enterprise** radio button, and then select the server group and server from the corresponding drop-down list and field as enabled.
-
- 4. Select the desired application from the drop-down list of applications.
-
-4. Click **Finish**.
-
-## Related topics
-
-
-[Application Virtualization Report Types](application-virtualization-report-types.md)
-
-[How to Create a Report](how-to-create-a-reportserver.md)
-
-[How to Delete a Report](how-to-delete-a-reportserver.md)
-
-[How to Export a Report](how-to-export-a-reportserver.md)
-
-[How to Print a Report](how-to-print-a-reportserver.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-sequence-a-new-add-on-or-plug-in-application--app-v-46-sp1-.md b/mdop/appv-v4/how-to-sequence-a-new-add-on-or-plug-in-application--app-v-46-sp1-.md
deleted file mode 100644
index 71f9b1e3fe..0000000000
--- a/mdop/appv-v4/how-to-sequence-a-new-add-on-or-plug-in-application--app-v-46-sp1-.md
+++ /dev/null
@@ -1,128 +0,0 @@
----
-title: How to Sequence a New Add-on or Plug-in Application (App-V 4.6 SP1)
-description: How to Sequence a New Add-on or Plug-in Application (App-V 4.6 SP1)
-author: dansimp
-ms.assetid: 2c018215-66e5-4301-8481-159891a6b35b
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Sequence a New Add-on or Plug-in Application (App-V 4.6 SP1)
-
-
-Use the following procedure to create a new add-on or plug-in virtual application package by using the Application Virtualization (App-V) Sequencer. An add-on or plug-in application is an application that extends the functionality of an application, for example, a plug-in for Microsoft Excel. For more information about the types of applications you can sequence, see [How to Determine Which Type of Application to Sequence (App-V 4.6 SP1)](how-to-determine-which-type-of-application-to-sequence---app-v-46-sp1-.md).
-
-**Important**
-Before performing the following procedure, install the parent application locally on the computer that is running the sequencer. For example, if you are sequencing a plug-in for Microsoft Excel, install Microsoft Excel locally on the computer that is running the sequencer. Also install the parent application in the same directory where the application is installed on target computers. If the plug-in or add-on is going to be used with an existing virtual application package, install the application on the same virtual application drive that was used when you created the parent virtual application package.
-
-
-
-You can also use an existing virtual application package as the parent application. To use an existing virtual application package, use the following procedure before sequencing the new add-on or plug-in.
-
-1. To start the App-V Sequencer, on the computer that is running the App-V Sequencer, click **Start** / **All Programs** / **Microsoft Application Virtualization** / **Microsoft Application Virtualization Sequencer**.
-
-2. To expand an existing package to the computer running the sequencer, click **Tools** / **Expand Package to Local System**.
-
-3. Browse to and select the package (**.sprj** file) that you want to expand, and then click **Open**. Continue with the following procedure.
-
-**To sequence a new add-on or plug-in application**
-
-1. To start the App-V Sequencer, on the computer that is running the App-V Sequencer, click **Start** / **All Programs** / **Microsoft Application Virtualization** / **Microsoft Application Virtualization Sequencer**.
-
-2. To start the **Create New Package Wizard**, click **Create a New Virtual Application Package**. To create the package, select **Create Package (default)**, and click then **Next**.
-
-3. On the **Prepare Computer** page, review the issues that might cause the package creation to fail, or for the package to contain unnecessary data. We strongly recommend that you resolve all potential issues before you continue. After you have fixed the conflicts, to update the information displayed, click **Refresh**. After you have resolved all potential issues, click **Next**.
-
- **Important**
- If you are required to disable virus scanning software, scan the computer running the sequencer to ensure that no unwanted or malicious files could be added to the package.
-
-
-
-4. On the **Type of Application** page, select **Add-on or Plug-in**, and then click **Next**.
-
- For more information about the types of applications that you can sequence, see [How to Determine Which Type of Application to Sequence (App-V 4.6 SP1)](how-to-determine-which-type-of-application-to-sequence---app-v-46-sp1-.md).
-
-5. On the **Select Installer** page, click **Browse** and specify the installation file for the add-on or plug-in. If the application does not have an associated installer file and you plan to run all installation steps manually, select the **Select this option to perform a custom installation** check box, and then click **Next**.
-
-6. On the **Select Primary** page, click **Browse** and specify the parent application.
-
- **Important**
- If the parent application that the add-on or plug-in you are installing is going to support has not been installed locally, stop here and install the application on the computer running the sequencer. For example, the **Excel.exe** program file must be installed locally for a Microsoft Excel plug-in.
-
-
-
-~~~
-Click **Next**.
-~~~
-
-7. On the **Package Name** page, specify a name that will be associated with the package. Use a name that helps identify the purpose and version of the application that will be added to the package. The package name will also be displayed in the App-V management console. The **Installation Location** displays the Application Virtualization path where the application will be installed. To edit this location, select **Edit (Advanced)**.
-
- **Important**
- Editing the Application Virtualization path is an advanced configuration task. You should fully understand the implications of changing the path. For most applications, we recommend the default path.
-
-
-
-~~~
-Click **Next**.
-~~~
-
-8. On the **Installation** page, when the sequencer and application installer are ready, install the plug-in or add-in application so the sequencer can monitor the installation process. Perform the installation by using the application’s installation process. If additional installation files must be run as part of the installation, click **Run** and locate and run the additional installation files. When you are finished with the installation, select **I am finished installing**, and then click **Next**.
-
-9. On the **Installation Report** page, you can review information about the virtual application package that you just sequenced. For a more detailed explanation about the information displayed in **Additional Information**, double-click the event. After you have reviewed the information, click **Next**.
-
-10. On the **Customize** page, if you are finished installing and configuring the virtual application, select **Stop now** and skip to step 14 of this procedure. If you want to customize any of the items in the following list, select **Customize**.
-
- - Edit the file type associations associated with an application.
-
- - Prepare the virtual package for streaming. Streaming improves the experience when the virtual application package is run on target computers.
-
- - Specify the operating systems that can run this package.
-
- Click **Next**.
-
-11. On the **Edit Shortcuts** page, you can optionally configure the file type associations (FTA) that will be associated with the various applications in the package. To create a new FTA, in the left pane, select and expand the application that you want to customize, and then click **Add**. In the **Add File Type Association** dialog box, provide the necessary information for the new FTA. Under the application, select **Shortcuts** to review the shortcut information associated with an application. In the **Location** pane, you can review the icon file information. To edit an existing FTA, click **Edit**. To remove an FTA, select the FTA, and then click **Remove**. Click **Next**.
-
-12. On the **Streaming** page, run each program so that it can be optimized and run more efficiently on target computers. It can take several minutes for all the applications to run. After all applications have run, close each of the applications, and then click **Next**.
-
- **Note**
- If you want to stop an application from loading during this step, in the **Application Launch** dialog box, click **Stop** and select one of the check boxes, **Stop all applications** or **Stop this application only**.
-
-
-
-13. On the **Target OS** page, specify the operating systems that can run this package. To enable all supported operating systems in your environment to run this package, select the **Allow this package to run on any operating system** check box. To configure this package to run only on specific operating systems, select the **Allow this package to run only on the following operating systems** check box, and then select the operating systems that can run this package. Click **Next**.
-
-14. On the **Create Package** page, to modify the package without saving it, select **Continue to modify package without saving using the package editor** check box. Selecting this option opens the package in the Sequencer console so that you can modify the package before it is saved. Click **Next**.
-
- To save the package immediately, select the default **Save the package now**. Optionally, select **Comments** to add comments that will be associated with the package. Comments are useful for identifying version and other information about the package. The default **Save Location** is also displayed. To change the default location, click **Browse** and specify the new location. The uncompressed package size is displayed. If the package size exceeds 4 GB (uncompressed) and you plan to stream the package to target computers, you must select **Compress Package**. Click **Create**.
-
-15. On the **Completion** page, after you have reviewed the information that is displayed in the **Successful Virtual Application Package Report** pane, click **Close**. The information displayed in the **Successful Virtual Application Package Report** pane is also available in the directory specified in step 14 of this procedure, in a file named **Reports.xml**.
-
- The package is now available in the sequencer. Click **Edit \[Package Name\]** to edit the package properties. For more information about modifying a package, see [How to Modify an Existing Virtual Application Package (App-V 4.6 SP1)](how-to-modify-an-existing-virtual-application-package--app-v-46-sp1-.md).
-
- **Important**
- After you have successfully created a virtual application package, you cannot run the virtual application package on the computer that is running the sequencer.
-
-
-
-## Related topics
-
-
-[Tasks for the Application Virtualization Sequencer (App-V 4.6 SP1)](tasks-for-the-application-virtualization-sequencer--app-v-46-sp1-.md)
-
-[How to Determine Which Type of Application to Sequence (App-V 4.6 SP1)](how-to-determine-which-type-of-application-to-sequence---app-v-46-sp1-.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-sequence-a-new-application--app-v-46-.md b/mdop/appv-v4/how-to-sequence-a-new-application--app-v-46-.md
deleted file mode 100644
index d519abb772..0000000000
--- a/mdop/appv-v4/how-to-sequence-a-new-application--app-v-46-.md
+++ /dev/null
@@ -1,78 +0,0 @@
----
-title: How to Sequence a New Application (App-V 4.6)
-description: How to Sequence a New Application (App-V 4.6)
-author: dansimp
-ms.assetid: f2c398c6-9200-4be3-b502-e00386fcd150
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Sequence a New Application (App-V 4.6)
-
-
-Use the following procedure to create a new virtual application by using the Application Virtualization (App-V) Sequencer. You can also use the App-V Sequencer to configure which files and configurations are applicable to all users and which files and configurations users can customize. After you successfully sequence the application, it is available in the App-V Sequencer.
-
-**Important**
-During sequencing, if the computer running the sequencer is running Windows Vista or Windows 7, and a restart is initiated outside of the virtual environment, for example, by clicking **Start** / **Shut Down**, you must click **Cancel** when prompted to close the program that is preventing Windows from shutting down. If you click **Force shut down**, the package creation will fail, and the computer will restart. When you click **Cancel**, the sequencer successfully records the restart while the application is being sequenced.
-
-
-
-**To sequence a new application**
-
-1. To create the App-V drive, configure drive Q as the location that can be used to save files while you are sequencing an application. You must then create individual directories for each application that you plan to sequence on drive Q. You can create the virtual application targeted folders before you sequence an application, or you can create them in step 5 of this procedure.
-
- **Note**
- The App-V drive you specify must be accessible on targeted computers. If drive Q is not accessible, you can choose a different drive letter.
-
-
-
-2. To start the App-V Sequencer Console, on the computer that is running the App-V Sequencer, select **Start** / **Programs** / **Microsoft Application Virtualization** / **Microsoft Application Virtualization Sequencer**. To start the Sequencing Wizard, click **Create a Package**.
-
-3. On the **Package Information** page, specify the **Package Name** that will be assigned to the virtual application. The package name is required for generating the associated Windows Installer file. You should also add an optional comment that will be assigned to the package and that provides detailed information about the virtual application. To display the **Advanced Options** page, select **Show Advanced Monitoring Options**, and then click **Next**; otherwise, proceed to step 5.
-
-4. On the **Advanced Options** page, to allow Microsoft Update to update the application as it is being sequenced, select **Allow Microsoft Update to run during monitoring**. If you select this option, Microsoft Updates can be installed during the monitoring phase, and you have to accept the associated updates for them to be installed. To remap the supported dynamic link library (.dll) files so that they use a contiguous space of RAM, select **Rebase DLLs**. Selecting this option can conserve memory and help improve performance. Many applications do not support this option, but it is useful in environments with limited RAM such as in Terminal Server scenarios. Click **Next**.
-
-5. On the **Monitor Installation** page, when you are ready to install the application, click **Begin Monitoring**, and in the **Browse for Folder** dialog box, specify the directory on drive Q where the application will be installed. If you did not configure drive Q and used a different drive letter for the application virtualization drive, select the drive letter you specified in step 1 of this procedure. To install the application to a folder that has not been created on the application virtualization drive, click **Make New Folder**. After you specify the folder, wait while the Sequencer configures the computer for sequencing.
-
- **Important**
- You must install each application that you sequence into a separate directory on the virtual application drive, and the associated folder name must not be longer than eight characters.
-
-
-
-~~~
-After the computer has been configured for sequencing, install the application so that the App-V Sequencer can monitor the installation; when you are finished, click **Stop Monitoring**, and then click **Next**.
-~~~
-
-6. On the **Configure Applications** page, if necessary, configure the shortcuts and file type associations that will be associated with the virtual application. To add a new file type association or shortcut, click **Add**, and in the **Add Application** dialog box, specify the new element. To remove an existing shortcut or file type association, click **Remove**. To edit an existing element, select the element you want to modify, and then click **Edit**. Specify the configurations in the **Edit Application** dialog box. Click **Save**, and then click **Next**.
-
-7. On the **Launch Applications** page, to start the application to ensure that the package has been installed correctly and is optimized for streaming, select the package, and then click **Launch**. This step is useful for configuring how the application initially runs on targeted computers and for accepting any associated license agreements before the package becomes available to App-V clients. If multiple applications are associated with this package, you can select **Launch All** to open all of the applications. To sequence the package, click **Next**.
-
-8. After you have successfully created the package, in the App-V Sequencer Console, select **File** / **Save** and specify the name and the virtual drive location where the package will be saved.
-
- You can optionally create an associated Windows Installer file (**.msi**) to install the virtual application package on targeted computers. To create a Windows Installer file, open the package in the Sequencer and select **Tools** / **Create MSI**. The Windows Installer file will be created and saved in the directory where the virtual application package is saved.
-
- **Important**
- After you have successfully created a virtual application package, you cannot run the virtual application package on the computer running the sequencer.
-
-
-
-## Related topics
-
-
-[How to Upgrade a Virtual Application Package (App-V 4.6)](how-to-upgrade-a-virtual-application-package--app-v-46-.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-sequence-a-new-application-by-using-the-command-line.md b/mdop/appv-v4/how-to-sequence-a-new-application-by-using-the-command-line.md
deleted file mode 100644
index 493a114518..0000000000
--- a/mdop/appv-v4/how-to-sequence-a-new-application-by-using-the-command-line.md
+++ /dev/null
@@ -1,95 +0,0 @@
----
-title: How to Sequence a New Application by Using the Command Line
-description: How to Sequence a New Application by Using the Command Line
-author: dansimp
-ms.assetid: c3b5c842-6a91-4d0a-9a22-c7b8d1aeb09a
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Sequence a New Application by Using the Command Line
-
-
-You can use a command line to sequence a new application. Using a command line is useful when you have to create a large number of virtual applications or when you need to create sequenced applications on a recurring basis.
-
-**Important**
-Command-line sequencing allows for default sequencing only. If you need to change default installation settings for the application you are sequencing, you must either manually modify the virtual application or update the virtual application by using the Application Virtualization (App-V) Sequencer. For more information about updating a virtual application by using the App-V Sequencer, see [How to Upgrade an Existing Virtual Application](how-to-upgrade-an-existing-virtual-application.md).
-
-
-
-Use the following procedure to create a virtual application by using the command line.
-
-**To sequence an application by using the command line**
-
-1. On the computer that is running the App-V Sequencer, open the command prompt by selecting **Start**, **Run**, and then type **cmd**. Click **OK**.
-
-2. Use the command prompt to specify the location of where the App-V Sequencer is installed. For example, at the command prompt, you could type the following: **cd C:\\Program Files\\Microsoft Application Virtualization Sequencer**.
-
-3. At the command prompt, type the following command, replacing the text in quotation marks with your values:
-
- `SFTSequencer /INSTALLPACKAGE:"pathtoMSI" /INSTALLPATH:"pathtopackageroot" /OUTPUTFILE:"pathtodestinationSPRJ"`
-
- **Note**
- You can specify additional parameters by using the command line, depending on the complexity of the application you are sequencing. For a complete list of parameters that are available for use with the App-V Sequencer, see [Sequencer Command-Line Parameters](sequencer-command-line-parameters.md).
-
-
-
-~~~
-Use the value descriptions in the following table to help you determine the actual text you will use in the preceding command.
-
-
-
-
-
-
-
-
-
Value
-
Description
-
-
-
-
-
pathtoMSI
-
Specifies the Windows Installer or a batch file that will be used to install an application so that it can be sequenced.
-
-
-
pathtopackageroot
-
Specify the package root directory.
-
-
-
pathtodestinationSPRJ
-
Specifies the path and file name of the SPRJ file that will be created.
-
-
-
-~~~
-
-
-
-4. Press **Enter**.
-
-## Related topics
-
-
-[How to Create or Upgrade Virtual Applications Using the App-V Sequencer](how-to-create-or-upgrade-virtual-applications-using--the-app-v-sequencer.md)
-
-[Sequencer Command-Line Error Codes](sequencer-command-line-error-codes.md)
-
-[Sequencer Command-Line Parameters](sequencer-command-line-parameters.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-sequence-a-new-application-package-using-the-command-line.md b/mdop/appv-v4/how-to-sequence-a-new-application-package-using-the-command-line.md
deleted file mode 100644
index 3271202faa..0000000000
--- a/mdop/appv-v4/how-to-sequence-a-new-application-package-using-the-command-line.md
+++ /dev/null
@@ -1,91 +0,0 @@
----
-title: How to Sequence a New Application Package Using the Command Line
-description: How to Sequence a New Application Package Using the Command Line
-author: dansimp
-ms.assetid: de72912b-d9e7-45b5-a601-12528f1a4cac
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Sequence a New Application Package Using the Command Line
-
-
-You can use a command line to sequence a new application. Using a command line is useful when you have to create a large number of virtual applications or when you need to create sequenced applications on a recurring basis.
-
-**Important**
-Command-line sequencing allows for default sequencing only. If you need to change default installation settings for the application you are sequencing, you must either manually modify the virtual application or update the virtual application by using the Application Virtualization (App-V) Sequencer. For more information about updating a virtual application by using the App-V Sequencer, see [How to Upgrade an Existing Virtual Application](how-to-upgrade-an-existing-virtual-application.md).
-
-
-
-Use the following procedure to create a virtual application by using the command line.
-
-**To sequence an application by using the command line**
-
-1. On the computer that is running the App-V Sequencer, open the command prompt by selecting **Start**, **Run**, and then type **cmd**. Click **OK**.
-
-2. Use the command prompt to specify the location of where the App-V Sequencer is installed. For example, at the command prompt, you could type the following: **cd C:\\Program Files\\Microsoft Application Virtualization Sequencer**.
-
-3. At the command prompt, type the following command, replacing the text in quotation marks with your values:
-
- `SFTSequencer /INSTALLPACKAGE:"pathtoMSI" /INSTALLPATH:"pathtopackageroot" /OUTPUTFILE:"pathtodestinationSPRJ"`
-
- **Note**
- You can specify additional parameters by using the command line, depending on the complexity of the application you are sequencing. For a complete list of parameters that are available for use with the App-V Sequencer, see [Application Virtualization Sequencer Command Line](application-virtualization-sequencer-command-line.md).
-
-
-
-~~~
-Use the value descriptions in the following table to help you determine the actual text you will use in the preceding command.
-
-
-
-
-
-
-
-
-
Value
-
Description
-
-
-
-
-
pathtoMSI
-
Specifies the Windows Installer or a batch file that will be used to install an application so that it can be sequenced.
-
-
-
pathtopackageroot
-
Specifies the package root directory.
-
-
-
pathtodestinationSPRJ
-
Specifies the path and file name of the SPRJ file that will be created.
-
-
-
-~~~
-
-
-
-4. Press **Enter**.
-
-## Related topics
-
-
-[How to Manage Virtual Applications Using the Command Line](how-to-manage-virtual-applications-using-the-command-line.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-sequence-a-new-application.md b/mdop/appv-v4/how-to-sequence-a-new-application.md
deleted file mode 100644
index 8897653dba..0000000000
--- a/mdop/appv-v4/how-to-sequence-a-new-application.md
+++ /dev/null
@@ -1,74 +0,0 @@
----
-title: How to Sequence a New Application
-description: How to Sequence a New Application
-author: dansimp
-ms.assetid: e01e98cd-2378-478f-9739-f72c465bf79a
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Sequence a New Application
-
-
-The Application Virtualization (App-V) Sequencer creates applications that can be run in a virtual environment. The App-V Sequencer monitors the installation and setup process for an application, and it records the information necessary for the application to run in a virtual environment. You can also use the App-V Sequencer to configure which files and configurations are applicable to all users and which files and configurations users can customize. When you sequence an application, you should save the package to a drive that is local to the computer you are sequencing on.
-
-A sequenced application does not interact with the operating system because each application runs in a virtual environment and is isolated from other applications that might be installed or running on the target computer. This isolation dramatically reduces application conflicts and decreases the required amount of application pre-deployment testing.
-
-After you successfully sequence the application, it is available in the App-V Sequencer Console. Running the App-V sequencer in Safe Mode is not supported.
-
-**To sequence a new application**
-
-1. You must create the Application Virtualization drive to sequence a new virtual application. To create the Application Virtualization drive, map the Q:\\ drive to a location that can be used to save files while you are sequencing an application. You must then create individual directories for each application you plan to sequence on the Q:\\ drive. You can create the virtual application target folders before you sequence an application, or you can create it in step 5 of this procedure.
-
-2. To start the App-V Sequencer Console, on the computer that is running the App-V Sequencer, select **Start** / **Programs** / **Microsoft Application Virtualization** / **Microsoft Application Virtualization Sequencer**. To start the **Sequencing Wizard**, select **File** / **New Package**.
-
-3. On the **Package Information** page, specify the **Package Name** that will be assigned to the virtual application. The package name is required for generating the associated Windows Installer file. You should also add an optional comment that will be assigned to the package and that provides detailed information about the virtual application. To display the **Advanced Options** page, select **Show Advanced Monitoring Options**. Click **Next**.
-
- **Note**
- To display the **Advanced Options** page, you must select **Show Advanced Monitoring Options**. If you do not require the **Advanced Options** page, skip to step 4.
-
-
-
-4. On the **Advanced Options** page, to specify the **Block Size** for the virtual application, select the size you want. The block size determines how the **.sft** file will be divided for streaming the package across the network to target computers. To allow Microsoft Update to update the application as it is being sequenced; select **Allow Microsoft Update to run during monitoring**. If you select this option, Microsoft Updates are allowed to be installed during the monitoring phase and you will need to accept the associated updates for them to be installed. To remap the supported dynamic link library (.dll) files so that they use a contiguous space of RAM, select **Rebase DLLs**. Selecting this option can conserve memory and help improve performance. Many applications do not support this option, but it is useful in environments with limited RAM such as in Terminal Server scenarios. Click **Next**.
-
-5. On the **Monitor Installation** page, to monitor the installation of an application, click **Begin Monitoring**. After you click **Begin Monitoring**, specify the directory on the Q:\\ drive where the application will be installed. To install the application to a folder that has not been created, click **Make New Folder**. You must install each application that you sequence into a separate directory.
-
- **Important**
- The folder name you specify must not be longer than 8 characters.
-
-
-
-~~~
-Wait for the virtual environment to load, and then install the application so that the App-V Sequencer can monitor the process. When you have completed the installation, click **Stop Monitoring** and then click **Next**.
-~~~
-
-6. On the **Additional Files to Map to Virtual File System (VFS)** page, to specify additional files to be added to the Virtual File System (VFS), click **Add**. Browse to the file you want to add, and click **Open**. To clear existing files that have been added, click **Reset** and then click **Next**.
-
-7. On the **Configure Applications** page, configure the shortcuts and file type associations that will be associated with the virtual application. Select the element you want to update, and then click **Edit Locations**. Specify the configurations in the **Shortcut Locations** dialog box. Click **OK** and then click **Next**.
-
-8. On the **Launch Applications** page, to start the application to ensure that the package is optimized for streaming, select the package and click **Launch**. This step is useful for configuring how the application initially runs on target computers and for accepting any associated license agreements before the package is made available to clients. If there are multiple applications associated with this package, you can select **Launch All** to open all of the applications. To sequence the package, click **Next**.
-
-9. On the **Sequence Package** page, to close the wizard, click **Finish**.
-
-10. After you have successfully created the package, to save the package, in the App-V Sequencer Console, select **File** / **Save** and specify the name and the location where the package will be saved.
-
-## Related topics
-
-
-[Tasks for the Application Virtualization Sequencer](tasks-for-the-application-virtualization-sequencer.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-sequence-a-new-middleware-application--app-v-46-sp1-.md b/mdop/appv-v4/how-to-sequence-a-new-middleware-application--app-v-46-sp1-.md
deleted file mode 100644
index 70ccc6f38a..0000000000
--- a/mdop/appv-v4/how-to-sequence-a-new-middleware-application--app-v-46-sp1-.md
+++ /dev/null
@@ -1,94 +0,0 @@
----
-title: How to Sequence a New Middleware Application (App-V 4.6 SP1)
-description: How to Sequence a New Middleware Application (App-V 4.6 SP1)
-author: dansimp
-ms.assetid: 304045c2-5e5e-4c91-b59e-a91fdf2500fb
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 08/30/2016
----
-
-
-# How to Sequence a New Middleware Application (App-V 4.6 SP1)
-
-
-Use the following procedure to create a new middleware virtual application package using the Application Virtualization (App-V) Sequencer. A middleware application is software that connects software modules or applications. For more information about the types of applications that you can sequence, see [How to Determine Which Type of Application to Sequence (App-V 4.6 SP1)](how-to-determine-which-type-of-application-to-sequence---app-v-46-sp1-.md).
-
-Use this type of package by using Dynamic Suite Composition in App-V. Dynamic Suite Composition enables you to define a virtual application package as being dependent on another virtual application package. The dependency enables the application to interact with the middleware or plug-in in the virtual environment, where typically this interaction is prevented. This is useful because a secondary application package can be used with several other primary applications, which enables each primary application to reference the same secondary package. For more information about how to use Dynamic Suite Composition, see [How To Use Dynamic Suite Composition](https://go.microsoft.com/fwlink/?LinkID=203804&clcid=0x409) in the Microsoft Technical Library (https://go.microsoft.com/fwlink/?LinkID=203804&clcid=0x409).
-
-**Important**
-During sequencing, if the computer running the App-V Sequencer is running Windows Vista or Windows 7 and a restart is initiated outside of the virtual environment, for example, **Start** / **Shut Down**, you must click **Cancel** when prompted to close the program that is preventing Windows from shutting down. If you click **Force shut down**, the package creation fails. When you click **Cancel**, App-V Sequencer successfully records the restart while the application is being sequenced.
-
-
-
-**To sequence a new middleware application**
-
-1. To start App-V Sequencer, on the computer that is running App-V Sequencer, click **Start** / **All Programs** / **Microsoft Application Virtualization** / **Microsoft Application Virtualization Sequencer**.
-
-2. To start the **Create New Package Wizard**, click **Create a New Virtual Application Package**. To create the package, select **Create Package (default)**, and then click **Next**.
-
-3. On the **Prepare Computer** page, review the issues that might cause the package creation to fail, or for the package to contain unnecessary data. We strongly recommend that you resolve all potential issues before you continue. After you have fixed the conflicts, to update the information displayed, click **Refresh**. After you have resolved all potential issues, click **Next**.
-
- **Important**
- If you are required to disable virus scanning software, you must scan the computer running the App-VSequencer to ensure that no unwanted or malicious files can be added to the package.
-
-
-
-4. On the **Type of Application** page, select **Middleware**, and then click **Next**.
-
- For more information about the types of applications that you can sequence, see [How to Determine Which Type of Application to Sequence (App-V 4.6 SP1)](how-to-determine-which-type-of-application-to-sequence---app-v-46-sp1-.md).
-
-5. On the **Select Installer** page, click **Browse** and specify the installation file for the application. If the application does not have an associated installer file and you plan to run all installation steps manually, select the **Select this option to perform a custom installation** check box, and then click **Next**.
-
-6. On the **Package Name** page, specify a name that will be associated with the package. The name helps identify the purpose and version of the application that will be added to the package. The package name is also displayed in the App-V Management Console. The **Installation Location** displays the application virtualization path where the application will be installed. To edit this location, select **Edit (Advanced)**.
-
- **Important**
- Editing the Application Virtualization path is an advanced configuration task. You should fully understand the implications of changing the path. For most applications, we recommend the default path.
-
-
-
-~~~
-Click **Next**.
-~~~
-
-7. On the **Installation** page, when the Sequencer and middleware application installer are ready, install the application so that the Sequencer can monitor the installation process. Perform the installation by using the application’s installation process. If additional installation files must be run as part of the installation, click **Run**, to locate and run the additional installation files. When you are finished with the installation, select the **I am finished installing** check box, and then click **Next**.
-
-8. On the **Installation** page, wait while the Sequencer configures the virtual application package.
-
-9. On the **Installation Report** page, you can review information about the virtual application package that you just sequenced. For a more detailed explanation about the information displayed in **Additional Information**, double-click the event. After you have reviewed the information, click **Next**.
-
-10. On the **Target OS** page, specify the operating systems that can run this package. To enable all supported operating systems in your environment to run this package, select the **Allow this package to run on any operating system** check box. To configure this package to run only on specific operating systems, select the **Allow this package to run only on the following operating systems** check box and select the operating systems that can run this package. Click **Next**.
-
-11. On the **Create Package** page, to modify the package without saving it, select the **Continue to modify package without saving using the package editor** check box. Selecting this option opens the package in the Sequencer console so that you can modify the package before it is saved. Click **Next**.
-
- To save the package immediately, select the default, the **Save the package now** check box. Add optional comments in the **Comments** box that will be associated with the package. Comments are useful for identifying version and other information about the package. The default **Save Location** is also displayed. To change the default location, click **Browse**, and then specify the new location. The uncompressed package size is displayed. If the package size exceeds 4 GB (uncompressed) and you plan to stream the package to target computers, you must select **Compress Package**. Click **Create**.
-
-12. On the **Completion** page, after you have reviewed the information displayed in the **Virtual Application Package Report** pane, click **Close**. The information displayed in the **Virtual Application Package Report** pane is also available in the directory specified in step 11 of this procedure, in a file named **Report.xml**.
-
- The package is now available in the Sequencer. To edit the package properties, click **Edit \[Package Name\]**. For more information about modifying a package, see [How to Modify an Existing Virtual Application Package (App-V 4.6 SP1)](how-to-modify-an-existing-virtual-application-package--app-v-46-sp1-.md)
-
- **Important**
- After you have successfully created a virtual application package, you cannot run the virtual application package on the computer that is running the Sequencer.
-
-
-
-## Related topics
-
-
-[Tasks for the Application Virtualization Sequencer (App-V 4.6 SP1)](tasks-for-the-application-virtualization-sequencer--app-v-46-sp1-.md)
-
-[How to Determine Which Type of Application to Sequence (App-V 4.6 SP1)](how-to-determine-which-type-of-application-to-sequence---app-v-46-sp1-.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-sequence-a-new-standard-application--app-v-46-sp1-.md b/mdop/appv-v4/how-to-sequence-a-new-standard-application--app-v-46-sp1-.md
deleted file mode 100644
index 91c5c8dae1..0000000000
--- a/mdop/appv-v4/how-to-sequence-a-new-standard-application--app-v-46-sp1-.md
+++ /dev/null
@@ -1,123 +0,0 @@
----
-title: How to Sequence a New Standard Application (App-V 4.6 SP1)
-description: How to Sequence a New Standard Application (App-V 4.6 SP1)
-author: dansimp
-ms.assetid: c4a2eb33-def8-4535-b93a-3d2de21ce29f
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Sequence a New Standard Application (App-V 4.6 SP1)
-
-
-Use the following procedure to create a new standard virtual application package by using the Application Virtualization (App-V) Sequencer. This procedure applies to most applications that you sequence. For more information about the types of applications you can sequence, see [How to Determine Which Type of Application to Sequence (App-V 4.6 SP1)](how-to-determine-which-type-of-application-to-sequence---app-v-46-sp1-.md). You must run the sequencer (**SFTSequencer.exe**) using an account that has administrator privileges because of the changes the sequencer makes to the local system. These changes can include writing files to the **C:\\Program Files** directory, making registry changes, starting and stopping services, updating security descriptors for files, and changing permissions.
-
-**Important**
-During sequencing, if the computer running the Sequencer is running Windows Vista or Windows 7 and a restart is initiated outside of the virtual environment, for example, **Start** / **Shut Down**, you must click **Cancel** when prompted to close the program that is preventing Windows Vista or Windows from shutting down. If you click **Force shut down**, the package creation fails. When you click **Cancel**, the Sequencer successfully records the restart while the application is being sequenced.
-
-
-
-**Note**
-Running the App-V sequencer in Safe Mode is not supported.
-
-
-
-**To sequence a new standard application**
-
-1. To start the App-V Sequencer, on the computer that is running the App-V Sequencer, click **Start** / **All Programs** / **Microsoft Application Virtualization** / **Microsoft Application Virtualization Sequencer**.
-
-2. To start the **Create New Package Wizard**, click **Create a New Virtual Application Package**. To create the package, select **Create Package (default)**, and then click **Next**.
-
-3. On the **Prepare Computer** page, review the issues that could cause the package creation to fail, or for the package to contain unnecessary data. We strongly recommend that you resolve all potential issues before you continue. After you have fixed the conflicts, to update the information that is displayed, click **Refresh**. After you have resolved all potential issues, click **Next**.
-
- **Important**
- If you are required to disable virus scanning software, scan the computer running the Sequencer to ensure that no unwanted or malicious files could be added to the package.
-
-
-
-4. On the **Type of Application** page, click **Standard Application (default)** check box, and then click **Next**.
-
- For more information about the types of applications that you can sequence, see [How to Determine Which Type of Application to Sequence (App-V 4.6 SP1)](how-to-determine-which-type-of-application-to-sequence---app-v-46-sp1-.md).
-
-5. On the **Select Installer** page, click **Browse** and specify the installation file for the application. If the application does not have an associated installer file and you plan to run all installation steps manually, select the **Perform a Custom Installation** check box, and then Click **Next**.
-
-6. On the **Package Name** page, specify a name that will be associated with the package. The name helps identify the purpose and version of the application that are added to the package. The package name is also displayed in the App-V management console. The **Primary Virtual Application Directory** displays the Application Virtualization path where the application will be installed on target computers. To edit this location, select **Edit (Advanced)**.
-
- **Important**
- Editing the Application Virtualization path is an advanced configuration task. You should fully understand the implications of changing the path. For most applications, the default path is recommended.
-
-
-
-~~~
-Click **Next**.
-~~~
-
-7. On the **Installation** page, when the Sequencer and application installer are ready, install the application so that the Sequencer can monitor the installation process. Perform the installation by using the application’s installation process. If additional installation files must be run as part of the installation, click **Run** to locate and run the additional installation files. When you are finished with the installation, select **I am finished installing**. Click **Next**.
-
-8. On the **Installation** page, wait while the Sequencer configures the virtual application package.
-
-9. On the **Configure Software** page, optionally run the programs contained in the package. This step helps complete any associated license or configuration tasks that are required to run the application before you deploy and run the package on target computers. To run all the programs at one time, select at least one program, and then click **Run All**. To run specific programs, select the program or programs you want to run, and then click **Run Selected**. Complete the required configuration tasks and then close the applications. It can take several minutes for all programs to run. Click **Next**.
-
-10. On the **Installation Report** page, you can review information about the virtual application package you just sequenced. For a more detailed explanation about the information displayed in **Additional Information**, double-click the event. After you have reviewed the information, click **Next**.
-
-11. On the **Customize** page, if you are finished installing and configuring the virtual application, select **Stop now** and skip to step 15 of this procedure. If you want to customize any of the items in the following list, select **Customize**.
-
- - Edit the file type associations and the icons associated with an application.
-
- - Prepare the virtual package for streaming. Streaming improves the experience when the virtual application package is run on target computers.
-
- - Specify the operating systems that can run this package.
-
- Click **Next**.
-
-12. On the **Edit Shortcuts** page, you can optionally configure the file type associations (FTA) and shortcut locations that will be associated with the various applications in the package. To create a new FTA, in the left pane, select and expand the application you want to customize, and then click **Add**. In the **Add File Type Association** dialog box, provide the necessary information for the new FTA. To review the shortcut information associated with an application, under the application, select **Shortcuts**, and in the **Location** pane, you can edit the icon file information. To edit an existing FTA, click **Edit**. To remove an FTA, select the FTA, and then click **Remove**. Click **Next**.
-
-13. On the **Streaming** page, run each program so that it can be optimized and run more efficiently on target computers. It can take several minutes for all the applications to run. After all applications have run, close each of the applications, and then click **Next**.
-
- **Note**
- If you want to stop an application from loading during this step, in the **Application Launch** dialog box, click **Stop**, and select one of the check boxes, **Stop all applications** or **Stop this application only**, depending on what you want.
-
-
-
-14. On the **Target OS** page, specify the operating systems that can run this package. To enable all supported operating systems in your environment to run this package, select **Allow this package to run on any operating system**. To configure this package to run only on specific operating systems, select **Allow this package to run only on the following operating systems** and specify the operating systems that can run this package. Click **Next**.
-
- **Important**
- The operating systems specified during this step reflect the operating systems on target computers that are enabled to run the package. You must ensure that the operating systems specified are supported by the application you are sequencing.
-
-
-
-15. On the **Create Package** page, to modify the package without saving it, select **Continue to modify package without saving using the package editor**. Selecting this option opens the package in the Sequencer console so that you can modify the package before it is saved. Click **Next**.
-
- To save the package immediately, select the default **Save the package now**. Add optional **Comments** that will be associated with the package. Comments are useful for identifying version and other information about the package. The default **Save Location** is also displayed. To change the default location, click **Browse** and specify the new location. The uncompressed package size is displayed. If the package size exceeds 4 GB (uncompressed) and you plan to stream the package to target computers, you must select **Compress Package**. Click **Create**.
-
-16. On the **Completion** page, after you have reviewed the information displayed in the **Virtual Application Package Report** pane, click **Close**. The information displayed in the **Virtual Application Package Report** pane is also available in the directory specified in step 15 of this procedure, in a file named **Report.xml**.
-
- The package is now available in the Sequencer. To edit the package properties, click **Edit \[Package Name\]**. For more information about modifying a package, see [How to Modify an Existing Virtual Application Package (App-V 4.6 SP1)](how-to-modify-an-existing-virtual-application-package--app-v-46-sp1-.md)
-
- **Important**
- After you have successfully created a virtual application package, you cannot run the virtual application package on the computer that is running the Sequencer.
-
-
-
-## Related topics
-
-
-[Tasks for the Application Virtualization Sequencer (App-V 4.6 SP1)](tasks-for-the-application-virtualization-sequencer--app-v-46-sp1-.md)
-
-[How to Determine Which Type of Application to Sequence (App-V 4.6 SP1)](how-to-determine-which-type-of-application-to-sequence---app-v-46-sp1-.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-sequence-an-application.md b/mdop/appv-v4/how-to-sequence-an-application.md
deleted file mode 100644
index c920cb5280..0000000000
--- a/mdop/appv-v4/how-to-sequence-an-application.md
+++ /dev/null
@@ -1,76 +0,0 @@
----
-title: How to Sequence an Application
-description: How to Sequence an Application
-author: dansimp
-ms.assetid: bd643dd6-dbf6-4469-bc70-c43ad9c69da9
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Sequence an Application
-
-
-The Application Virtualization (App-V) Sequencer creates applications that can be run in a virtual environment. The App-V Sequencer monitors the installation and setup process for an application, and it records the information necessary for the application to run in a virtual environment. You can also use the App-V Sequencer to configure which files and configurations are applicable to all users and which files and configurations users can customize. When you sequence an application, you should save the package to a drive that is local to the computer you are sequencing on.
-
-A sequenced application does not interact with the operating system because each application runs in a virtual environment and is isolated from other applications that might be installed or running on the target computer. This isolation dramatically reduces application conflicts and decreases the required amount of application pre-deployment testing.
-
-After you successfully sequence the application, it is available in the App-V Sequencer Console.
-
-**To sequence a new application**
-
-1. You must create the Application Virtualization drive to sequence a new virtual application. To create the Application Virtualization drive, map the Q:\\ drive to a location that can be used to save files while you are sequencing an application. You must then create individual directories for each application you plan to sequence on the Q:\\ drive. You can create the virtual application target folders before you sequence an application, or you can create it in step 5 of this procedure.
-
-2. To start the App-V Sequencer Console, on the computer that is running the App-V Sequencer, select **Start** / **Programs** / **Microsoft Application Virtualization** / **Microsoft Application Virtualization Sequencer**. To start the **Sequencing Wizard**, select **File** / **New Package**.
-
-3. On the **Package Information** page, specify the **Package Name** that will be assigned to the virtual application. The package name is required for generating the associated Windows Installer file. You should also add an optional comment that will be assigned to the package and that provides detailed information about the virtual application. To display the **Advanced Options** page, select **Show Advanced Monitoring Options**. Click **Next**.
-
- **Note**
- To display the **Advanced Options** page, you must select **Show Advanced Monitoring Options**. If you do not require the **Advanced Options** page, skip to step 4.
-
-
-
-4. On the **Advanced Options** page, to specify the **Block Size** for the virtual application, select the size you want. The block size determines how the **.sft** file will be divided for streaming the package across the network to target computers. To allow Microsoft Update to update the application as it is being sequenced; select **Allow Microsoft Update to run during monitoring**. If you select this option, Microsoft Updates are allowed to be installed during the monitoring phase and you will need to accept the associated updates for them to be installed. To remap the supported dynamic link library (.dll) files so that they use a contiguous space of RAM, select **Rebase DLLs**. Selecting this option can conserve memory and help improve performance. Many applications do not support this option, but it is useful in environments with limited RAM such as in Remote Desktop Session Host (RD Session Host) Server scenarios. Click **Next**.
-
-5. On the **Monitor Installation** page, to monitor the installation of an application, click **Begin Monitoring**. After you click **Begin Monitoring**, specify the directory on the Q:\\ drive where the application will be installed. To install the application to a folder that has not been created, click **Make New Folder**. You must install each application that you sequence into a separate directory.
-
- **Important**
- The folder name you specify must not be longer than 8 characters.
-
-
-
-~~~
-Wait for the virtual environment to load, and then install the application so that the App-V Sequencer can monitor the process. When you have completed the installation, click **Stop Monitoring**, and then click **Next**.
-~~~
-
-6. On the **Additional Files to Map to Virtual File System (VFS)** page, to specify additional files to be added to the Virtual File System (VFS), click **Add**. Browse to the file you want to add and click **Open**. To clear existing files that have been added, click **Reset**, and then click **Next**.
-
-7. On the **Configure Applications** page, configure the shortcuts and file type associations that will be associated with the virtual application. Select the element that you want to update, and then click **Edit Locations**. Specify the configurations in the Shortcut Locations dialog box. Click **OK**, and then click **Next**.
-
-8. On the **Launch Applications** page, to start the application to ensure that the package is optimized for streaming, select the package and click **Launch**. This step is useful for configuring how the application initially runs on target computers and for accepting any associated license agreements before the package is made available to clients. If there are multiple applications associated with this package, you can select **Launch All** to open all of the applications. To sequence the package, click **Next**.
-
-9. On the **Sequence Package** page, to close the wizard, click **Finish**.
-
-10. After you have successfully created the package, to save the package, in the App-V Sequencer Console, select **File** / **Save** and specify the name and the location where the package will be saved.
-
-## Related topics
-
-
-[Application Virtualization Sequencer](application-virtualization-sequencer.md)
-
-[How to Sequence a New Application by Using the Command Line](how-to-sequence-a-new-application-by-using-the-command-line.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-set-up-a-concurrent-license-group.md b/mdop/appv-v4/how-to-set-up-a-concurrent-license-group.md
deleted file mode 100644
index 6a4304627f..0000000000
--- a/mdop/appv-v4/how-to-set-up-a-concurrent-license-group.md
+++ /dev/null
@@ -1,66 +0,0 @@
----
-title: How to Set Up a Concurrent License Group
-description: How to Set Up a Concurrent License Group
-author: dansimp
-ms.assetid: 031abcf6-d8ed-49be-bddb-91b2c695d411
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Set Up a Concurrent License Group
-
-
-You can use the following procedure in the Application Virtualization Server Management Console to set up a concurrent license group. When you set up a concurrent license group, you can limit access to applications to a specific number of concurrent users.
-
-**To set up a concurrent license group**
-
-1. In the left pane of the Application Virtualization Server Management Console, right-click the **Application Licenses** node.
-
-2. Select **New Concurrent License**.
-
-3. Enter a name in the **Application License Group Name** field.
-
-4. Enter a value (in minutes) in the **License Expiration Warning** field.
-
-5. Click **Next**.
-
-6. Enter descriptive text in the **License Description** field.
-
-7. Enter a value in the **Concurrent License Quantity** field.
-
-8. Select the **Enabled** check box to enable the license.
-
-9. Select the **Expiration Date** check box (if you want to set an expiration date), and enter the expiration date or use the calendar utility to select a date.
-
-10. If you need to associate a key with the license, enter the license key information in the **License Key** field.
-
-11. Click **Finish**.
-
-## Related topics
-
-
-[How to Associate an Application with a License Group](how-to-associate-an-application-with-a-license-group.md)
-
-[How to Create an Application License Group](how-to-create-an-application-license-group.md)
-
-[How to Remove an Application from a License Group](how-to-remove-an-application-from-a-license-group.md)
-
-[How to Set Up a Named License Group](how-to-set-up-a-named-license-group.md)
-
-[How to Set Up an Unlimited License Group](how-to-set-up-an-unlimited-license-group.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-set-up-a-named-license-group.md b/mdop/appv-v4/how-to-set-up-a-named-license-group.md
deleted file mode 100644
index 4077c745cd..0000000000
--- a/mdop/appv-v4/how-to-set-up-a-named-license-group.md
+++ /dev/null
@@ -1,68 +0,0 @@
----
-title: How to Set Up a Named License Group
-description: How to Set Up a Named License Group
-author: dansimp
-ms.assetid: 8ef6716c-0cb7-4706-ad3b-ac6f27b2e7ad
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Set Up a Named License Group
-
-
-You can use the following procedure in the Application Virtualization Server Management Console to set up a named license group. When you set up a named license group, you are giving specific users access to the selected application.
-
-**To set up a Named License Group**
-
-1. In the left pane of the Application Virtualization Server Management Console, right-click the **Application Licenses** node.
-
-2. Select **New Named License**.
-
-3. Enter a name in the **Application License Group Name** field.
-
-4. Enter a value (in minutes) in the **License Expiration Warning** field.
-
-5. Click **Next**.
-
-6. Enter descriptive text in the **License Description** field.
-
-7. Select the **Enabled** check box to enable the license.
-
-8. Select the **Expiration Date** check box (if you want to set an expiration date), and enter the expiration date or use the calendar utility to select a date.
-
-9. Click **Next**.
-
-10. Use the **Named License User Wizard** to add, edit, or remove specific users from the license group.
-
-11. Click **Finish**.
-
-## Related topics
-
-
-[How to Associate an Application with a License Group](how-to-associate-an-application-with-a-license-group.md)
-
-[How to Create an Application License Group](how-to-create-an-application-license-group.md)
-
-[How to Remove an Application from a License Group](how-to-remove-an-application-from-a-license-group.md)
-
-[How to Remove an Application License Group](how-to-remove-an-application-license-group.md)
-
-[How to Set Up a Concurrent License Group](how-to-set-up-a-concurrent-license-group.md)
-
-[How to Set Up an Unlimited License Group](how-to-set-up-an-unlimited-license-group.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-set-up-an-unlimited-license-group.md b/mdop/appv-v4/how-to-set-up-an-unlimited-license-group.md
deleted file mode 100644
index 4da9b85aa9..0000000000
--- a/mdop/appv-v4/how-to-set-up-an-unlimited-license-group.md
+++ /dev/null
@@ -1,64 +0,0 @@
----
-title: How to Set Up an Unlimited License Group
-description: How to Set Up an Unlimited License Group
-author: dansimp
-ms.assetid: 0c37c7b7-aba9-4c03-9e0e-94c966f874cf
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Set Up an Unlimited License Group
-
-
-You can use the following procedure in the Application Virtualization Server Management Console to set up an unlimited license group. When you set up an unlimited license group, you let an unlimited number of users access an application simultaneously.
-
-**To set up an unlimited license group**
-
-1. In the left pane of the Application Virtualization Server Management Console, right-click the **Application Licenses** node.
-
-2. Select **New Unlimited License**.
-
-3. Enter the name of the new group in the **Application License Group Name** field.
-
-4. Enter a value (in minutes) in the **License Expiration Warning** field.
-
-5. Click **Next**.
-
-6. Enter descriptive text in the **License Description** field.
-
-7. Select the **Enabled** check box to enable the license.
-
-8. Select the **Expiration Date** check box (if you want to set an expiration date), and enter the expiration date or use the calendar utility to select a date.
-
-9. If you need to associate a key with the license, enter the license key information in the **License Key** field.
-
-10. Click **Finish**.
-
-## Related topics
-
-
-[How to Associate an Application with a License Group](how-to-associate-an-application-with-a-license-group.md)
-
-[How to Create an Application License Group](how-to-create-an-application-license-group.md)
-
-[How to Remove an Application from a License Group](how-to-remove-an-application-from-a-license-group.md)
-
-[How to Set Up a Concurrent License Group](how-to-set-up-a-concurrent-license-group.md)
-
-[How to Set Up a Named License Group](how-to-set-up-a-named-license-group.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-set-up-and-enable-or-disable-authentication.md b/mdop/appv-v4/how-to-set-up-and-enable-or-disable-authentication.md
deleted file mode 100644
index 66c1796f86..0000000000
--- a/mdop/appv-v4/how-to-set-up-and-enable-or-disable-authentication.md
+++ /dev/null
@@ -1,63 +0,0 @@
----
-title: How to Set Up and Enable or Disable Authentication
-description: How to Set Up and Enable or Disable Authentication
-author: dansimp
-ms.assetid: 1e43d0c5-a467-4a8b-b656-93f75d7deb82
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Set Up and Enable or Disable Authentication
-
-
-The Application Virtualization Server Management Console lets you enable or disable Windows authentication, which lets you to define who has access to the system. You can use the following procedures to set up and disable authentication from the **Provider Policies Results** pane of the console.
-
-**Note**
- Normally, you set up authentication when you add a provider policy through the New Provider Policy Wizard.
-
-
-
-**To set up authentication**
-
-1. Click the **Provider Policies** node to display the list of provider policies in the **Results** pane.
-
-2. Right-click the provider policy, and select **Properties**.
-
-3. Select the **Provider Pipeline** tab.
-
-4. Make sure the **Authentication** check box is selected.
-
-5. Select the authentication level from the drop-down list.
-
-6. Click **Apply** or **OK**.
-
-**To enable or disable authentication**
-
-1. Click the **Provider Policies** node to display the list of provider policies in the **Results** pane.
-
-2. Right-click the provider policy, and select **Properties**.
-
-3. Select the **Provider Pipeline** tab.
-
-4. Select the **Authentication** check box to enable authentication. Clear the box to disable it.
-
-## Related topics
-
-
-[How to Customize an Application Virtualization System in the Server Management Console](how-to-customize-an-application-virtualization-system-in-the-server-management-console.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-set-up-or-disable-application-licensing.md b/mdop/appv-v4/how-to-set-up-or-disable-application-licensing.md
deleted file mode 100644
index 9e7b1e615b..0000000000
--- a/mdop/appv-v4/how-to-set-up-or-disable-application-licensing.md
+++ /dev/null
@@ -1,58 +0,0 @@
----
-title: How to Set Up or Disable Application Licensing
-description: How to Set Up or Disable Application Licensing
-author: dansimp
-ms.assetid: 7c00b531-ec41-4970-b0fc-d84225ce3bb2
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Set Up or Disable Application Licensing
-
-
-You can use the following procedures to set up or disable application licensing in the Application Virtualization Server Management Console.
-
-**To set up application licensing**
-
-1. Click the **Provider Policies** node to display the provider policies in the **Results** pane.
-
-2. Right-click the provider policy, and select **Properties**.
-
-3. Select the **Provider Pipeline** tab.
-
-4. Select the **Licensing** check box, and select a licensing option from the drop-down menu.
-
-5. Click **Apply** or **OK**.
-
-**To disable application licensing**
-
-1. Click the **Provider Policies** node to display the provider policies in the **Results** pane.
-
-2. Right-click the provider policy, and select **Properties**.
-
-3. Select the **Provider Pipeline** tab.
-
-4. Clear the **Licensing** check box.
-
-5. Click **Apply** or **OK**.
-
-## Related topics
-
-
-[How to Customize an Application Virtualization System in the Server Management Console](how-to-customize-an-application-virtualization-system-in-the-server-management-console.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-set-up-or-disable-database-size.md b/mdop/appv-v4/how-to-set-up-or-disable-database-size.md
deleted file mode 100644
index f6db631033..0000000000
--- a/mdop/appv-v4/how-to-set-up-or-disable-database-size.md
+++ /dev/null
@@ -1,65 +0,0 @@
----
-title: How to Set Up or Disable Database Size
-description: How to Set Up or Disable Database Size
-author: dansimp
-ms.assetid: 4abaf349-132d-4186-8873-a0e515593b93
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Set Up or Disable Database Size
-
-
-You can use the following procedures in the Application Virtualization Server Management Console to specify the size (in MB) of Application Virtualization System usage that you want to store in the database.
-
-When the size of the stored data reaches 95% (the high watermark) of the specified limit, the system will delete 10% of the usage data, leaving 85% of the data. Package and application usage data will be deleted. When the database grows large enough and approaches the high watermark, a warning message is sent to the SQL Server log to inform you that this limit has been reached. This warning is necessary because the cleanup action can affect the output of the reports. It will also help you decide whether you need to increase the maximum database size, reduce the number of months of usage data to be kept, or turn down the logging level.
-
-**Note**
-The **No Size Limit** and **Keep All Usage** options are provided so that you can disable usage reporting and database cleanup. Selecting these items will clean up the database transaction log as well. (All committed Microsoft SQL Server transactions will be removed from the database log.)
-
-
-
-**To set up database size**
-
-1. Right-click the Application Virtualization System node in the left pane, and select **System Options**.
-
-2. Select the **Database** tab.
-
-3. Select the **Maximum Database Size (MB)** or **No Size Limit** radio button.
-
-4. If you choose to specify a database size, best practices recommend that you enter a number between 512 and 4096 MB. The default size is 1024 MB and if you need to increase the database size, the maximum value you can enter is 2,147,483,647. If you select **No Size Limit**, the database will grow until it reaches the disk size limit.
-
-5. Click **Apply** or **OK**.
-
-**To disable database size limits**
-
-1. Right-click the Application Virtualization System node in the **Scope** pane, and select **System Options**.
-
-2. Select the **Database** tab.
-
-3. Select the **No Size Limit** and **Keep All Usage** radio buttons.
-
-4. Click **Apply** or **OK**.
-
-## Related topics
-
-
-[How to Customize an Application Virtualization System in the Server Management Console](how-to-customize-an-application-virtualization-system-in-the-server-management-console.md)
-
-[How to Set Up or Disable Usage Reporting](how-to-set-up-or-disable-usage-reporting.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-set-up-or-disable-usage-reporting.md b/mdop/appv-v4/how-to-set-up-or-disable-usage-reporting.md
deleted file mode 100644
index 1dc1ac12a1..0000000000
--- a/mdop/appv-v4/how-to-set-up-or-disable-usage-reporting.md
+++ /dev/null
@@ -1,65 +0,0 @@
----
-title: How to Set Up or Disable Usage Reporting
-description: How to Set Up or Disable Usage Reporting
-author: dansimp
-ms.assetid: 8587003a-128d-4b5d-ac70-5b9eddddd3dc
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Set Up or Disable Usage Reporting
-
-
-You can use the following procedures in the Application Virtualization Server Management Console to specify the duration (in months) of Application Virtualization System usage information you want to store in the database.
-
-**Note**
- To store usage information, you must select the **Log Usage Information** check box on the **Provider Pipeline** tab. To display this tab, right-click the provider policy in the **Provider Policies Results** pane and select **Properties**.
-
-
-
-**To set up usage reporting**
-
-1. Right-click the Application Virtualization System node in the left pane, and select **System Options**.
-
-2. Select the **Database** tab.
-
-3. Select the **Keep Usage For (Months)** or **Keep All Usage** radio button.
-
-4. If you choose to specify usage duration in months, enter a number from 1 to 120 (default value is 6 months). If you select **Keep All Usage**, the database will grow until it reaches the specified size limit.
-
-5. Click **Apply** or **OK**.
-
-**To disable usage reporting**
-
-1. Click the **Provider Policies** node.
-
-2. Right-click **Provider Policy** and select **Properties**.
-
-3. Select the **Provider Pipeline** tab.
-
-4. Clear the **Log Usage Information** check box.
-
-5. Click **Apply** or **OK**.
-
-## Related topics
-
-
-[How to Customize an Application Virtualization System in the Server Management Console](how-to-customize-an-application-virtualization-system-in-the-server-management-console.md)
-
-[How to Set Up or Disable Database Size](how-to-set-up-or-disable-database-size.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-set-up-periodic-publishing-refresh.md b/mdop/appv-v4/how-to-set-up-periodic-publishing-refresh.md
deleted file mode 100644
index 4aaf75708f..0000000000
--- a/mdop/appv-v4/how-to-set-up-periodic-publishing-refresh.md
+++ /dev/null
@@ -1,56 +0,0 @@
----
-title: How to Set Up Periodic Publishing Refresh
-description: How to Set Up Periodic Publishing Refresh
-author: dansimp
-ms.assetid: c358c765-cb88-4881-b4e7-0a2e87304870
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Set Up Periodic Publishing Refresh
-
-
-You can use the following procedure to configure the client to periodically refresh the publishing information from the App-V servers. After the client is configured, the refresh operation is automatic. These settings configure the default settings for the client so that all users on this computer will see the same settings.
-
-**Note**
-After you have performed this procedure, the publishing information will be refreshed according to the new settings after the first refresh at login. When this first refresh occurs, the server might override the computer settings with different settings, depending on how it is configured. The **Refresh** tab in the **Properties** dialog box shows the locally configured client computer settings and any settings that might have been configured for the user by the publishing server.
-
-
-
-**To periodically refresh the publishing information from the Application Virtualization Servers**
-
-1. Click **Publishing Servers** in the **Scope** pane.
-
-2. In the **Results** pane, right-click the desired server and select **Properties** from the pop-up-menu.
-
-3. In the **Properties** dialog box, on the **Refresh** tab, select the **Refresh configuration every** check box and enter a number that represents the frequency in the field. Then select **Minutes**, **Hours**, **Days** from the drop-down menu.
-
- **Note**
- This setting will cause the client to refresh publishing information every time the configured period elapses. If the user is not logged in when it's time to do a refresh, the refresh will take place when the user next logs in. The timer is then started again for the next period.
-
-
-
-4. Click **Apply** to change the configuration.
-
-5. When you finish configuring the server, click **OK** to exit the dialog box and return to the Application Virtualization Client Management Console.
-
-## Related topics
-
-
-[How to Configure the Client in the Application Virtualization Client Management Console](how-to-configure-the-client-in-the-application-virtualization-client-management-console.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-set-up-publishing-refresh-on-login.md b/mdop/appv-v4/how-to-set-up-publishing-refresh-on-login.md
deleted file mode 100644
index 0c4fc3c8e1..0000000000
--- a/mdop/appv-v4/how-to-set-up-publishing-refresh-on-login.md
+++ /dev/null
@@ -1,48 +0,0 @@
----
-title: How to Set Up Publishing Refresh on Login
-description: How to Set Up Publishing Refresh on Login
-author: dansimp
-ms.assetid: 196448db-7645-4fd5-a854-ef6405b15db4
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Set Up Publishing Refresh on Login
-
-
-You can use the following procedure to configure the Application Virtualization (App-V) Client to refresh the publishing information from the server each time you log in to the computer. After the client is configured, the refresh operation is automatic.
-
-**To refresh the publishing information on login**
-
-1. Click **Publishing Servers** in the **Scope** pane.
-
-2. In the **Results** pane, right-click the desired server and select **Properties** from the pop-up-menu.
-
-3. In the **Properties** dialog box, on the **Refresh** tab, select the **Refresh configuration server on user login** check box.
-
-4. Click **Apply** to change the configuration.
-
-5. When you finish configuring the settings, click **OK** to exit the dialog box and return to the Application Virtualization Management Console.
-
- The publishing information will now be refreshed each time you log in to the system.
-
-## Related topics
-
-
-[How to Configure the Client in the Application Virtualization Client Management Console](how-to-configure-the-client-in-the-application-virtualization-client-management-console.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-set-up-publishing-servers.md b/mdop/appv-v4/how-to-set-up-publishing-servers.md
deleted file mode 100644
index 08ed01a0ed..0000000000
--- a/mdop/appv-v4/how-to-set-up-publishing-servers.md
+++ /dev/null
@@ -1,58 +0,0 @@
----
-title: How to Set Up Publishing Servers
-description: How to Set Up Publishing Servers
-author: dansimp
-ms.assetid: 2111f079-c202-4c49-b2a6-f4237068b2dc
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Set Up Publishing Servers
-
-
-You can use the following procedures to add and configure Application Virtualization Servers directly from the Client Management Console.
-
-**To add an application publishing server**
-
-1. In the **Results** pane, right-click and select **New Server** from the pop-up-menu to start the New Application Virtualization Server Wizard, or alternatively, right-click the **Publishing Server** node and select **New Server** from the pop-up-menu.
-
-2. On page one of the wizard, enter the name of the server in the **Display Name** field and select the server type from the **Type** drop-down list. You can choose **Application Virtualization Server**, **Enhanced Security Application Virtualization Server**, **Standard HTTP Server**, or **Enhanced Security HTTP Server** from the drop-down list of server types.
-
-3. Click **Next**.
-
-4. On page two of the wizard, type the appropriate information into the **Host Name** and **Port** fields. The **Path** field is not editable for Application Virtualization Servers. You must enter a path for Standard HTTP Server or Enhanced Security HTTP Server.
-
-5. Click **Finish** to add the server.
-
-**To set up an application publishing server**
-
-1. In the **Results** pane, right-click the desired server and select **Properties** from the pop-up menu.
-
-2. Click the **General** tab, where you can change the server name, select a type from the drop-down list of server types, and specify the host name and port. When the server type is Standard HTTP Server or Enhanced Security HTTP Server, the **Path** field is also editable.
-
-3. Click the **Refresh** tab, where the **Refresh publishing on user login** check box is selected by default. To change the refresh rate, select the **Refresh publishing every** check box and enter a number that represents the frequency in the field. Then select **Minutes**, **Hours**, **Days** from the drop-down menu. (The minimum amount of time you can enter is 30 minutes.)
-
-4. Click **Apply** to change the configuration.
-
-5. When you are finished publishing, click **OK** to exit the dialog box and return to the Client Management Console.
-
-## Related topics
-
-
-[How to Disable or Modify Disconnected Operation Mode Settings](how-to-disable-or-modify-disconnected-operation-mode-settings.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-uninstall-the-app-v-client.md b/mdop/appv-v4/how-to-uninstall-the-app-v-client.md
deleted file mode 100644
index 6a88f59a7d..0000000000
--- a/mdop/appv-v4/how-to-uninstall-the-app-v-client.md
+++ /dev/null
@@ -1,71 +0,0 @@
----
-title: How to Uninstall the App-V Client
-description: How to Uninstall the App-V Client
-author: dansimp
-ms.assetid: 07591270-9651-4bb5-a5b3-e0fc009bd9e2
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Uninstall the App-V Client
-
-
-Use the following procedure to uninstall the Application Virtualization Client from the computer.
-
-**To uninstall the Application Virtualization Desktop Client**
-
-1. In Control Panel, double-click **Add or Remove Programs** (or in Windows Vista, **Programs and Features**), and then double-click **Microsoft Application Virtualization Desktop Client**.
-
-2. In the dialog box that appears, click **Yes** to continue with the uninstall process.
-
- **Important**
- The uninstall process cannot be canceled or interrupted.
-
-
-
-3. When a message stating that the Microsoft Application Virtualization Client Tray application must be closed before continuing appears, right-click the App-V icon in the notification area and select **Exit** to close the application. Then click **Retry** to continue with the uninstall process.
-
- **Important**
- You might see a message stating that one or more virtual applications are in use. Close any open applications and save your data before you continue. Then click **OK** to continue with the uninstall process.
-
-
-
-4. A progress bar shows the time remaining. When this step finishes, you must restart the computer so that all associated drivers can be stopped to complete the uninstall process.
-
- **Note**
- The following registry keys remain after the uninstall process is complete:
-
- - HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Wow6432Node\\Microsoft\\SoftGrid
-
- - HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Wow6432Node\\Microsoft\\SoftGrid\\4.5
-
- - HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Wow6432Node\\Microsoft\\SoftGrid\\4.5\\SystemGuard "Client"=dword:00000000
-
- - HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Wow6432Node\\Microsoft\\SoftGrid\\4.5\\SystemGuard\\SecKey
-
-
-
-## Related topics
-
-
-[How to Install the Client by Using the Command Line](how-to-install-the-client-by-using-the-command-line-new.md)
-
-[How to Manually Install the Application Virtualization Client](how-to-manually-install-the-application-virtualization-client.md)
-
-[How to Publish a Virtual Application on the Client](how-to-publish-a-virtual-application-on-the-client.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-upgrade-a-package-using-the-open-package-command.md b/mdop/appv-v4/how-to-upgrade-a-package-using-the-open-package-command.md
deleted file mode 100644
index a5bf655e68..0000000000
--- a/mdop/appv-v4/how-to-upgrade-a-package-using-the-open-package-command.md
+++ /dev/null
@@ -1,47 +0,0 @@
----
-title: How to Upgrade a Package Using the Open Package Command
-description: How to Upgrade a Package Using the Open Package Command
-author: dansimp
-ms.assetid: 67c10440-de8a-4547-a34b-f83206d0cc3b
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Upgrade a Package Using the Open Package Command
-
-
-Use the Open Package command to upgrade or apply an update to a sequenced application package. When you upgrade an existing virtual application package using the command line, the original version of the .sft file is deleted. You should backup the associated .sft file before upgrading the package using the command line.
-
-**To upgrade a package using the Open Package command**
-
-1. To open the package that will be upgraded, in the Application Virtualization (App-V) console select **File**, **Open Package for Upgrade**. In the **Open** dialog box, select the package that will be upgraded.
-
-2. To start the **Sequencing** wizard, select **Tools**, **Sequencing Wizard**. Complete the wizard applying the configuration changes, to save the new sequenced application, select **File**, **Save**.
-
-3. To append the version number to the package name, in the Sequencer console, select **Tools**, **Options**. Select **Append Package Version to Filename**. Click **OK**.
-
- **Important**
- Updating the file name with the package version is essential to successfully completing the upgrade.
-
-
-
-## Related topics
-
-
-[How to Manage Virtual Applications Using the Command Line](how-to-manage-virtual-applications-using-the-command-line.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-upgrade-a-package.md b/mdop/appv-v4/how-to-upgrade-a-package.md
deleted file mode 100644
index 5c88a1bf32..0000000000
--- a/mdop/appv-v4/how-to-upgrade-a-package.md
+++ /dev/null
@@ -1,57 +0,0 @@
----
-title: How to Upgrade a Package
-description: How to Upgrade a Package
-author: dansimp
-ms.assetid: 831c7556-6f6c-4b3a-aefb-26889094dc1a
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Upgrade a Package
-
-
-The process for an automatic upgrade is the same as for adding a package version in the Application Virtualization Server Management Console. An automatic upgrade is performed when you resequence the application in an existing package. Then you can add this new version to your servers for streaming.
-
-When you upgrade a package with a new version, you can leave the existing version in place or delete it and leave only the newest one. You might want to leave the old version in place for compatibility with legacy documents or so that you can test the new version before making it available to all users.
-
-**To upgrade a package automatically**
-
-1. Copy the new SFT file to the Application Virtualization Server's content folder.
-
- **Note**
- If resequencing did not add features that changed the Open Software Descriptor (OSD), icon (ICO), or Sequencer Project (SPRJ) files, you do not need to copy those. You can include these files if you want all these files to display the same date.
-
-
-
-2. In left pane of the Application Virtualization Server Management Console, expand **Packages**.
-
-3. Right-click the package you want to upgrade, and select **Add Version**.
-
-4. In the **Add Package Version** dialog box, browse for or type the full path name for the new application version in the **Full Path for the file** field. This must be an SFT file.
-
-5. Click **Next**.
-
-6. The **Summary** dialog box shows the file location and prompts you to copy the file there if you have not already done so. Click **Finish** after you have verified the information.
-
- The new version is now complete and ready to stream.
-
-## Related topics
-
-
-[How to Manage Packages in the Server Management Console](how-to-manage-packages-in-the-server-management-console.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-upgrade-a-sequenced-application-package-using-the-command-line.md b/mdop/appv-v4/how-to-upgrade-a-sequenced-application-package-using-the-command-line.md
deleted file mode 100644
index 0ac6b50d84..0000000000
--- a/mdop/appv-v4/how-to-upgrade-a-sequenced-application-package-using-the-command-line.md
+++ /dev/null
@@ -1,88 +0,0 @@
----
-title: How to Upgrade a Sequenced Application Package Using the Command Line
-description: How to Upgrade a Sequenced Application Package Using the Command Line
-author: dansimp
-ms.assetid: 682fac46-c71d-4731-831b-81bfd5032764
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Upgrade a Sequenced Application Package Using the Command Line
-
-
-Use the following procedure to upgrade a virtual application by using a command line. When you upgrade an existing virtual application package by using the command line, the original version of the .sft file is deleted. You should back up the associated .sft file before upgrading the package by using the command line.
-
-**To upgrade a virtual application**
-
-1. On the computer that is running the Application Virtualization (App-V) Sequencer, to open the command prompt, select **Start**, **Run**, and type **cmd**. Click **OK**.
-
-2. At the command prompt, specify the location where the App-V Sequencer is installed. For example, at the command prompt, you could type the following: **cd C:\\Program Files\\Microsoft Application Virtualization Sequencer**.
-
-3. At the command prompt, type the following command, replacing the text in quotation marks with your values:
-
- `SFTSequencer /UPGRADE:"pathtosourceSPRJ" /INSTALLPACKAGE:"pathtoUpgradeInstaller" /DECODEPATH:"pathtodecodefolder" /OUTPUTFILE:"pathtodestinationSPRJ"`
-
- **Note**
- You can specify additional parameters by using the command line, depending on the complexity of the application you are upgrading. For a complete list of parameters that are available for use with the App-V Sequencer, see [Command-Line Parameters](command-line-parameters.md).
-
-
-
-~~~
-Use the value descriptions in the following table to help you determine the actual text you will use in the preceding command.
-
-
-
-
-
-
-
-
-
Value
-
Description
-
-
-
-
-
pathtosourceSPRJ
-
Specifies the directory location of the virtual application to be upgraded.
-
-
-
pathtoUpgradeInstaller
-
Specifies the Windows Installer or a batch file that will be used to install an upgrade to the application.
-
-
-
pathtodecodefolder
-
Specify the directory in which to unpack the SFT file.
-
-
-
pathtodestinationSPRJ
-
Specifies the path and file name of the SPRJ file that will be created.
-
-
-
-~~~
-
-
-
-4. Press **Enter**.
-
-## Related topics
-
-
-[How to Manage Virtual Applications Using the Command Line](how-to-manage-virtual-applications-using-the-command-line.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-upgrade-a-sequenced-virtual-application-package.md b/mdop/appv-v4/how-to-upgrade-a-sequenced-virtual-application-package.md
deleted file mode 100644
index 131400d266..0000000000
--- a/mdop/appv-v4/how-to-upgrade-a-sequenced-virtual-application-package.md
+++ /dev/null
@@ -1,68 +0,0 @@
----
-title: How to Upgrade a Sequenced Virtual Application Package
-description: How to Upgrade a Sequenced Virtual Application Package
-author: dansimp
-ms.assetid: ffa989f3-6621-4c59-9599-e3c3b3332f67
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Upgrade a Sequenced Virtual Application Package
-
-
-You can upgrade an existing virtual application to a new version by using the Application Virtualization (App-V) Sequencer. The upgrade process is similar to creating a new virtual application. You must open the existing virtual application for an upgrade, make the necessary updates, and then save the updated virtual application to a new location in the package root directory. You can also use the App-V Sequencer Console to make changes to an existing virtual application without performing an upgrade. However, you cannot make modifications to the virtual application’s file system by using this method because the App-V Sequencer does not actually decode the associated .sft file. For example; you can open an existing virtual application in the App-V Sequencer Console by selecting **Open** on the **File** menu. You can update the **Package Name** and the associated **Comments**, and you can make changes to the virtual file system and virtual registry. You can also create a Windows Installer file.
-
-**Caution**
-You should not reference a previous version of the Windows Installer (.msi) file when you upgrade an existing virtual application package because the previous version of the .sft file will be modified during the upgrade.
-
-
-
-Use the following procedure to upgrade an existing virtual application.
-
-**To upgrade an existing virtual application**
-
-1. To start the App-V Sequencer Console, on the computer running the App-V Sequencer, select **Start**/**Programs**/**Microsoft Application Virtualization**/**Microsoft Application Virtualization Sequencer**.
-
-2. To open the existing virtual application, in the App-V Console, select **File**/**Open for Package Upgrade**. Use the **Open For Package Upgrade** dialog box to locate the associated SPRJ file you want to open for upgrade.
-
-3. To specify the location of where the updated package will be decoded, browse to the location by using the **Browse For Folder** dialog box. This is the location where the package root directory will be created as specified in the associated SFT file. The directory that you specify must be a different location from where the original version of the virtual application is saved. You can click **Make New Folder** if the new target folder has not been created yet. You should select the root of the Application Virtualization drive to create the folder. When you create the updated version of the package, it will be denoted with a sequential addition to the directory name—for example, “**.1**” will be added to the directory name located on the Q:\\ drive.
-
- **Important**
- The directory that you specify must be located in the package root directory on the Q:\\ drive. You can create a new folder, or you can create a subfolder under the directory where the original virtual application is saved. The name assigned to the new folder must not be longer than 8 eight characters.
-
-
-
-4. To open the Sequencing Wizard, select **Tools**/**Sequencing Wizard**. On the **Package Information** page, optionally specify the new **Package Name** and add optional comments that will be associated with the updated virtual application. Click **Next**.
-
-5. On the **Monitor Installation** page, to begin monitoring the new installation, click **Begin Monitoring**. After the virtual environment has finished loading, install the updated version of the application, or apply updates to the existing application. After you have finished updating the virtual application, click **Stop Monitoring**, and then click **Next**.
-
-6. On the **Additional Files to Map to Virtual File System (VFS)** page, to specify additional files to be added to the Virtual File System (VFS), click **Add**. Browse to the file you want to add, and click **Open**. To clear existing files that have been added, click **Reset**, and then click **Next**.
-
-7. On the **Configure Applications** page, configure the shortcuts and file type associations that will be associated with the updated virtual application. Select the element you want to update, and then click **Edit Locations**. Specify the configurations in the **Shortcut Locations** dialog box, and then click **Next**.
-
-8. On the **Launch Applications** page, to start the application to ensure that the package is optimized for streaming, select the package and click **Launch**. This step is useful for configuring how the application initially runs on target computers and for accepting any associated license agreements before the package is made available to clients. If there are multiple applications associated with this package, you can select **Launch All** to open all of the applications. To sequence the new version of the virtual application, click **Next**.
-
-9. To finish and to close the Sequencing Wizard, on the **Sequence Package** page, click **Finish**.
-
-10. After you have successfully updated the virtual application, to save the package, in the App-V Sequencer Console, on the **File** menu, select **Save**. The virtual application can be accessed in the directory specified in step 3.
-
-## Related topics
-
-
-[Tasks for the Application Virtualization Sequencer](tasks-for-the-application-virtualization-sequencer.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-upgrade-a-virtual-application-by-using-the-command-line.md b/mdop/appv-v4/how-to-upgrade-a-virtual-application-by-using-the-command-line.md
deleted file mode 100644
index 8557a608b7..0000000000
--- a/mdop/appv-v4/how-to-upgrade-a-virtual-application-by-using-the-command-line.md
+++ /dev/null
@@ -1,92 +0,0 @@
----
-title: How to Upgrade a Virtual Application by Using the Command Line
-description: How to Upgrade a Virtual Application by Using the Command Line
-author: dansimp
-ms.assetid: 83c97767-6ea1-42aa-b411-ccc9fa61cf81
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Upgrade a Virtual Application by Using the Command Line
-
-
-Use the following procedure to upgrade a virtual application by using a command line.
-
-**To upgrade a virtual application**
-
-1. On the computer that is running the Application Virtualization (App-V) Sequencer, to open the command prompt, select **Start**, **Run**, and type **cmd**. Click **OK**.
-
-2. At the command prompt, specify the location where the App-V Sequencer is installed. For example, at the command prompt, you could type the following: **cd C:\\Program Files\\Microsoft Application Virtualization Sequencer**.
-
-3. At the command prompt, type the following command, replacing the text in quotation marks with your values:
-
- `SFTSequencer /UPGRADE:"pathtosourceSPRJ" /INSTALLPACKAGE:"pathtoUpgradeInstaller" /DECODEPATH:"pathtodecodefolder" /OUTPUTFILE:"pathtodestinationSPRJ"`
-
- **Note**
- You can specify additional parameters by using the command line, depending on the complexity of the application you are upgrading. For a complete list of parameters that are available for use with the App-V Sequencer, see [Sequencer Command-Line Parameters](sequencer-command-line-parameters.md).
-
-
-
-~~~
-Use the value descriptions in the following table to help you determine the actual text you will use in the preceding command.
-
-
-
-
-
-
-
-
-
Value
-
Description
-
-
-
-
-
pathtosourceSPRJ
-
Specifies the directory location of the virtual application to be upgraded.
-
-
-
pathtoUpgradeInstaller
-
Specifies the Windows Installer or a batch file that will be used to install an upgrade to the application.
-
-
-
pathtodecodefolder
-
Specify the directory in which to unpack the SFT file.
-
-
-
pathtodestinationSPRJ
-
Specifies the path and file name of the SPRJ file that will be created.
-
-
-
-~~~
-
-
-
-4. Press **Enter**.
-
-## Related topics
-
-
-[How to Create or Upgrade Virtual Applications Using the App-V Sequencer](how-to-create-or-upgrade-virtual-applications-using--the-app-v-sequencer.md)
-
-[Sequencer Command-Line Error Codes](sequencer-command-line-error-codes.md)
-
-[Sequencer Command-Line Parameters](sequencer-command-line-parameters.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-upgrade-a-virtual-application-package--app-v-46-.md b/mdop/appv-v4/how-to-upgrade-a-virtual-application-package--app-v-46-.md
deleted file mode 100644
index 043776bf7d..0000000000
--- a/mdop/appv-v4/how-to-upgrade-a-virtual-application-package--app-v-46-.md
+++ /dev/null
@@ -1,61 +0,0 @@
----
-title: How to Upgrade a Virtual Application Package (App-V 4.6)
-description: How to Upgrade a Virtual Application Package (App-V 4.6)
-author: dansimp
-ms.assetid: 3566227e-f3dc-4c32-af1f-e0211588118c
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Upgrade a Virtual Application Package (App-V 4.6)
-
-
-Use the following procedure to upgrade an existing virtual application by using the Application Virtualization (App-V) Sequencer. You can also use the App-V Sequencer Console to make changes to an existing virtual application without performing an upgrade, but you cannot make modifications to the virtual application’s file system by using this method because the App-V Sequencer does not actually decode the associated .sft file. For more information about editing an existing package, see [How to Modify a Virtual Application Package (App-V 4.6)](how-to-modify-a-virtual-application-package--app-v-46-.md).
-
-**To upgrade an existing virtual application**
-
-1. To start the App-V Sequencer Console, on the computer running the App-V Sequencer, select **Start** / **Programs** / **Microsoft Application Virtualization** / **Microsoft Application Virtualization Sequencer**.
-
-2. To open the existing virtual application package and start the **Sequencing Wizard**, select **Upgrade a Package**. Locate the package you want to upgrade, and click **Open**. In the **Browse For Folder** dialog box, specify the location where the upgraded version of the package will be placed. This location specified must be located on the drive specified as the application virtualization drive, which is typically the Q:\\ drive. To create a new folder, select **Make New Folder**.
-
- **Warning**
- You must specify the root folder of the existing virtual application. Do not manually create a subfolder or the upgrade will fail.
-
-
-
-3. On the **Package Information** page, specify the **Package Name** that will be assigned to the updated package. The package name is required for generating the associated Windows Installer file. You should also add an optional comment that will be assigned to the package and that provides detailed information about the virtual application—for example, a version number. To display the **Advanced Options** page, select **Show Advanced Monitoring Options** and click **Next**; otherwise, proceed to step 5.
-
-4. On the **Advanced Options** page, to allow Microsoft Update to update the application as it is being sequenced, select **Allow Microsoft Update to run during monitoring**. If you select this option, Microsoft Updates are allowed to be installed during the monitoring phase and you will need to accept the associated updates for them to be installed. To remap the supported dynamic-link library (.dll) files so that they use a contiguous space of RAM, select **Rebase DLLs**. Selecting this option can conserve memory and help improve performance. Click **Next**.
-
-5. On the **Monitor Installation** page, when you are ready to update the application, click **Begin Monitoring**.
-
- When the updates to the application have been applied, click **Stop Monitoring**. Click **Next**.
-
-6. On the **Configure Applications** page, if necessary, configure the shortcuts and file type associations that will be associated with the virtual application. To add a new file type association or shortcut, click **Add**, and in the **Add Application** dialog box, specify the new element. To remove an existing shortcut or file type association, click **Remove**. To edit an existing element, select the element you want to modify, and then click **Edit**. Specify the configurations in the **Edit Application** dialog box. Click **Save**. Click **Next**.
-
-7. On the **Launch Applications** page, to start the application to ensure that the package has been installed correctly and is optimized for streaming, select the package and click **Launch**. This step is useful for configuring how the application initially runs on target computers and for accepting any associated license agreements before the package is made available to App-V clients. If multiple applications are associated with this package, you can select **Launch All** to open all of the applications. To sequence the package, click **Next**.
-
-8. To close the Sequencing Wizard, click **Finish**. To save the updated package, in the Sequencer Console, select **File** / **Save**.
-
- If you plan to deploy the updated package by using a Windows Installer file (.msi), you must create new one as follows: in the Sequencer Console, select **Tools** / **Create MSI**. The new Windows Installer file will be created and saved in the directory where the updated virtual application package is saved.
-
-## Related topics
-
-
-[How to Sequence a New Application (App-V 4.6)](how-to-sequence-a-new-application--app-v-46-.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-upgrade-an-existing-virtual-application.md b/mdop/appv-v4/how-to-upgrade-an-existing-virtual-application.md
deleted file mode 100644
index f56ab1c22a..0000000000
--- a/mdop/appv-v4/how-to-upgrade-an-existing-virtual-application.md
+++ /dev/null
@@ -1,62 +0,0 @@
----
-title: How to Upgrade an Existing Virtual Application
-description: How to Upgrade an Existing Virtual Application
-author: dansimp
-ms.assetid: ec531576-2423-4c2c-9b9f-da74174a6858
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Upgrade an Existing Virtual Application
-
-
-You can upgrade an existing virtual application to a new version by using the Application Virtualization (App-V) Sequencer. The upgrade process is similar to creating a new virtual application. You must open the existing virtual application for an upgrade, make the necessary updates, and then save the updated virtual application to a new location in the package root directory.
-
-You can also use the App-V Sequencer Console to make changes to an existing virtual application without performing an upgrade. However, you cannot make modifications to the virtual application’s file system by using this method because the App-V Sequencer does not actually decode the associated .sft file. For example; you can open an existing virtual application in the App-V Sequencer Console by selecting **Open** on the **File** menu. You can update the **Package Name** and the associated **Comments**, and you can make changes to the virtual file system and virtual registry. You can also create a Windows Installer file.
-
-Use the following procedure to upgrade an existing virtual application.
-
-**To upgrade an existing virtual application**
-
-1. To start the App-V Sequencer Console, on the computer running the App-V Sequencer, select **Start**/**Programs**/**Microsoft Application Virtualization**/**Microsoft Application Virtualization Sequencer**.
-
-2. To open the existing virtual application, in the App-V Console, select **File**/**Open for Package Upgrade**. Use the **Open For Package Upgrade** dialog box to locate the associated SPRJ file you want to open for upgrade.
-
-3. To specify the location of where the package will be decoded, click **Browse For Folder** and specify the Q:\\. This is the location where the package root directory will be created as specified in the associated SFT file. When you create the updated version of the package, it will be denoted with a sequential addition to the directory name—for example, “**.1**” will be added to the directory name located on the Q:\\ drive.
-
-4. To open the Sequencing Wizard, select **Tools**/**Sequencing Wizard**. On the **Package Information** page, optionally specify the new **Package Name** and add optional comments that will be associated with the updated virtual application. Click **Next**.
-
-5. On the **Monitor Installation** page, to begin monitoring the new installation, click **Begin Monitoring**. After the virtual environment has finished loading, install the updated version of the application, or apply updates to the existing application. After you have finished updating the virtual application, click **Stop Monitoring**, and then click **Next**.
-
-6. On the **Additional Files to Map to Virtual File System (VFS)** page, to specify additional files to be added to the Virtual File System (VFS), click **Add**. Browse to the file you want to add, and click **Open**. To clear existing files that have been added, click **Reset**, and then click **Next**.
-
-7. On the **Configure Applications** page, configure the shortcuts and file type associations that will be associated with the updated virtual application. Select the element you want to update, and then click **Edit Locations**. Specify the configurations in the **Shortcut Locations** dialog box, and then click **Next**.
-
-8. On the **Launch Applications** page, to start the application to ensure that the package is optimized for streaming, select the package and click **Launch**. This step is useful for configuring how the application initially runs on target computers and for accepting any associated license agreements before the package is made available to clients. If there are multiple applications associated with this package, you can select **Launch All** to open all of the applications. To sequence the new version of the virtual application, click **Next**.
-
-9. To finish and to close the Sequencing Wizard, on the **Sequence Package** page, click **Finish**.
-
-10. After you have successfully updated the virtual application, to save the package, in the App-V Sequencer Console, on the **File** menu, select **Save**. The virtual application can be accessed in the directory specified in step 3.
-
-## Related topics
-
-
-[Application Virtualization Sequencer](application-virtualization-sequencer.md)
-
-[How to Upgrade a Virtual Application by Using the Command Line](how-to-upgrade-a-virtual-application-by-using-the-command-line.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-upgrade-the-application-virtualization-client.md b/mdop/appv-v4/how-to-upgrade-the-application-virtualization-client.md
deleted file mode 100644
index 2441e92fe0..0000000000
--- a/mdop/appv-v4/how-to-upgrade-the-application-virtualization-client.md
+++ /dev/null
@@ -1,127 +0,0 @@
----
-title: How to Upgrade the Application Virtualization Client
-description: How to Upgrade the Application Virtualization Client
-author: dansimp
-ms.assetid: 2a75d8b5-da88-456c-85bb-f5bd3d470f7f
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Upgrade the Application Virtualization Client
-
-
-You can use the following procedures to upgrade the Application Virtualization (App-V) Desktop Client or the App-V Client for Remote Desktop Services (formerly Terminal Services). You upgrade the client by installing a new version over the previously installed older version. When you upgrade the clients, the installer software automatically preserves and migrates the user’s settings for virtual applications. Administrative rights are required to run the setup program.
-
-**Note**
-During the upgrade to Application Virtualization (App-V) 4.5 or later versions, the permissions to the HKCU registry key are changed. Because of this, users will lose user configurations that were set previously, such as user-configured Disconnected Mode settings. If the user is not actively restricted from configuring client user interface behavior through a permission lockdown, the user can reset these preferences after a publishing refresh.
-
-
-
-**Important**
-When upgrading to version 4.6 or a later version of the App-V Client, you must use the correct installer for the computer’s operating system, 32-bit or 64-bit. The installation will fail and an error message will be displayed if you use the wrong installer.
-
-
-
-**To upgrade the Application Virtualization Desktop Client**
-
-1. Shut down all virtual applications, right-click the App-V Desktop Client icon displayed in the Windows desktop notification area, and select **Exit** to shut down the existing client.
-
-2. After you have obtained the correct installer archive file and saved it to your computer, double-click it to expand the archive.
-
-3. Browse to find the setup.exe file, and double-click setup.exe to start the installation.
-
-4. The wizard checks the system to ensure that all prerequisite software is installed and will prompt you to install any of the following, if missing:
-
- - Microsoft Visual C++ 2005 SP1 Redistributable Package (x86)
-
- - Microsoft Core XML Services (MSXML) 6.0 SP1 (x86)
-
- - Microsoft Application Error Reporting
-
- **Note**
- For version 4.6 and higher, the wizard will also install the following software prerequisite:
-
- - Microsoft Visual C++ 2008 SP1 Redistributable Package (x86)
-
-
-
-5. Click **Install**. Installation progress is displayed, and the status changes from **Pending** to **Installing**. Installation status changes to **Succeeded** as each step is completed successfully.
-
-6. When the **Application Virtualization Desktop Client** dialog appears and displays a message stating that an older version of the client has been found on the computer, click **Next** to upgrade to the new version.
-
-7. When the **License Agreement** screen is displayed, read the license agreement, and if you agree, click **I accept the terms in the license agreement**, and then click **Next**.
-
-8. When the InstallShield Wizard displays the **Ready to Upgrade the Program** dialog screen, click **Upgrade** to begin the upgrade. The next screen indicates that the client is being installed.
-
- **Warning**
- If you did not shut down the client program in step 1, you might see a **Files In Use** warning displayed. If this happens, right-click the App-V Client icon displayed in the desktop notification area and select **Exit** to shut down the existing client. Then click **Retry** to continue.
-
-
-
-9. When the installation completes successfully, you will be prompted to restart the computer. You need to restart the computer to complete the installation.
-
- **Caution**
- If the upgrade fails for any reason, you will need to restart the computer before attempting the upgrade again.
-
-
-
-**To upgrade the Application Virtualization Client by Using the Command Line**
-
-1. If upgrading the App-V client using the setup.msi program, ensure that any necessary prerequisite software has been installed.
-
- **Important**
- - For version 4.6 and later of the App-V client, the setup.msi program checks the system and will fail with an error message indicating that installation cannot continue if prerequisite software is not installed.
-
- - For App-V version 4.6, command-line parameters cannot be used during an upgrade and will be ignored.
-
-
-
-2. The following command-line example uses the setup.msi file to upgrade the App-V Client. You will need to use the correct client installer program depending on whether you are upgrading the App-V Desktop Client or the App-V Client for Remote Desktop Services (formerly Terminal Services).
-
- **msiexec.exe /i "setup.msi"**
-
- **Important**
- The quotation marks are required only when the value contains a space. For consistency, all instances in the preceding example are shown as having quotation marks.
-
-
-
-**To upgrade the Application Virtualization Client for Remote Desktop Services**
-
-1. Follow your organization’s standard policies for installing or upgrading applications on the Remote Desktop Session Host (RD Session Host) server. If the system is part of a farm, remove the RD Session Host from the server farm.
-
-2. To upgrade the App-V Client for Remote Desktop Services (formerly Terminal Services), you must use the command line because you cannot upgrade the client manually on the RD Session Host.
-
- **Note**
- In App-V version 4.6 and later, in addition to using the command line to upgrade the client, you can also use a Remote Desktop session. No special parameters are required to start the Remote Desktop session.
-
-
-
-3. After the Client for Remote Desktop Services upgrade is complete, restart and log in to the RD Session Host.
-
-4. After the system is restarted, add the server to the server farm.
-
- **Caution**
- If the upgrade fails for any reason, you will need to restart the computer before attempting the upgrade again.
-
-
-
-## Related topics
-
-
-[Application Virtualization Deployment and Upgrade Considerations](application-virtualization-deployment-and-upgrade-considerations.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-upgrade-the-application-virtualization-sequencer.md b/mdop/appv-v4/how-to-upgrade-the-application-virtualization-sequencer.md
deleted file mode 100644
index 2842d352f7..0000000000
--- a/mdop/appv-v4/how-to-upgrade-the-application-virtualization-sequencer.md
+++ /dev/null
@@ -1,46 +0,0 @@
----
-title: How to Upgrade the Application Virtualization Sequencer
-description: How to Upgrade the Application Virtualization Sequencer
-author: dansimp
-ms.assetid: 7f85f140-5034-4227-85ef-81f205e722ef
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Upgrade the Application Virtualization Sequencer
-
-
-Upgrading from previous versions of the Sequencer is not supported. You must uninstall any previous versions of the Sequencer and then install Microsoft Application Virtualization Sequencer 4.5. However, Virtual applications created using an earlier version of the Sequencer can be opened and edited using Sequencer 4.5.
-
-**To upgrade the Sequencer on computers running Windows Vista**
-
-1. To uninstall previous installations of the Sequencer, open Control Panel and select **Programs and Features**. Select the older version from the list, and then click **Uninstall**. To confirm the uninstall, click **Yes** in the **Programs and Features** dialog box.
-
-2. After you have completed uninstalling the previous Sequencer version, install Application Virtualization Sequencer 4.5. For more information about installing Sequencer 4.5, see [How to Install the Application Virtualization Sequencer](how-to-install-the-application-virtualization-sequencer.md).
-
-**To upgrade the Sequencer on computers running Windows XP**
-
-1. To uninstall previous installations of the Sequencer, open Control Panel and select **Add or Remove Programs**. Select the older version from the list, and then click **Remove**. To confirm the uninstall, click **Yes** in the **Add or Remove Programs** dialog box.
-
-2. After you have completed uninstalling the previous Sequencer version, install Application Virtualization Sequencer 4.5. For more information about installing Sequencer 4.5, see [How to Install the Application Virtualization Sequencer](how-to-install-the-application-virtualization-sequencer.md).
-
-## Related topics
-
-
-[Application Virtualization Deployment and Upgrade Considerations](application-virtualization-deployment-and-upgrade-considerations.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-upgrade-the-servers-and-system-components.md b/mdop/appv-v4/how-to-upgrade-the-servers-and-system-components.md
deleted file mode 100644
index 924c233ee0..0000000000
--- a/mdop/appv-v4/how-to-upgrade-the-servers-and-system-components.md
+++ /dev/null
@@ -1,80 +0,0 @@
----
-title: How to Upgrade the Servers and System Components
-description: How to Upgrade the Servers and System Components
-author: dansimp
-ms.assetid: 7d8374fe-5897-452e-923e-556a854b2024
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Upgrade the Servers and System Components
-
-
-Use the following procedure to upgrade software components installed on all Application Virtualization System computers. Application Virtualization System services will be restarted automatically on each computer after it has been upgraded.
-
-**Note**
-- The upgrade process stops all Application Virtualization System services, thereby taking the system out of service. User sessions should be shut down before you begin the upgrade process, and you should stop all Application Virtualization Server services in your environment.
-
-- If you have more than one server that is sharing access to the Application Virtualization database, all those servers must be taken offline while the database is being upgraded. You should follow your normal business practices for the database upgrade, but it is highly advisable that you test the database upgrade by using a backup copy of the database first on a test server. Then, you should select one of the servers for the first upgrade, which will upgrade the database schema. After the production database has been successfully upgraded, you can upgrade the other servers.
-
-- You can upgrade to Microsoft Application Virtualization (App-V) 4.5 only from Microsoft Application Virtualization (App-V) 4.1 or 4.1 SP1. App-V 4.0 and earlier must be uninstalled or upgraded to 4.1 or 4.1 SP1 before upgrading to App-V 4.5.
-
-
-
-**To upgrade software components on Application Virtualization System computers**
-
-1. Navigate to the location of the Setup program on the network, either run this program from the network or copy its directory to the target computer, and then double-click the Setup.exe file.
-
-2. On the **Welcome** page of the Installation Wizard, click **Next**.
-
-3. On the **License Agreement** page, read the license agreement, check **I accept the terms in the license agreement**, and click **Next**.
-
-4. When the **Installed Software** page opens and displays a list of the installed Application Virtualization System components and the version of each component, click **Next**.
-
-5. On the **Session Loss Warning** page, read the displayed message and click **Next**.
-
-6. On the **Connect to Configuration Database** page, review the content on the page and click **Next**.
-
-7. If the **Database Upgrade Required** page is displayed, a database upgrade is required. Enter the database administrative credentials, and then click **Next**. If this page is not displayed, skip to Step 9.
-
-8. On the **Backup Configuration Database** page, check the appropriate boxes to perform the backup and export it to an existing location, and then click **Next**.
-
- **Important**
- If you want to be able to roll back to the previous version in the event of an upgrade failure, make sure you check the **Perform a backup of the configuration database** box, or you will lose the configuration data.
-
- When you want to restore a database with VSS, you must first stop the App-V Server Service on the Management Server. This should be done on every Management server if there is more than one server connected to the same database.
-
-
-
-9. On the first **Package Validation** page, read the content and then click **Next**.
-
-10. On the second **Package Validation** page, you have the option of displaying the details of the package validation in a Notepad window. To see the details, click **Details**; otherwise, click **Next**.
-
-11. On the **Ready to Upgrade the Program** page, click **Next**.
-
-12. On the **Installation Wizard Completed** page, click **Finish**.
-
-13. Repeat steps 1–12 on all other computers where you installed the Application Virtualization Management Console or the Application Virtualization Server software component.
-
- After upgrading the data store, you can resume normal operation. (The data store is upgraded when you upgrade any server or the App-V Management Web Service.)
-
-## Related topics
-
-
-[Application Virtualization Deployment and Upgrade Considerations](application-virtualization-deployment-and-upgrade-considerations.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-use-dynamic-suite-composition.md b/mdop/appv-v4/how-to-use-dynamic-suite-composition.md
deleted file mode 100644
index e6841ce254..0000000000
--- a/mdop/appv-v4/how-to-use-dynamic-suite-composition.md
+++ /dev/null
@@ -1,144 +0,0 @@
----
-title: How To Use Dynamic Suite Composition
-description: How To Use Dynamic Suite Composition
-author: dansimp
-ms.assetid: 24147feb-a0a8-4791-a8e5-cbe5fe13c762
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How To Use Dynamic Suite Composition
-
-
-Dynamic Suite Composition in Application Virtualization enables you to define an application as being dependent on another application, such as middleware or a plug-in. This enables the application to interact with the middleware or plug-in in the virtual environment, where typically this is prevented. This is useful because a secondary application package can be used with several other applications, referred to as the *primary applications*, which enables each primary application to reference the same secondary package.
-
-You can use Dynamic Suite Composition when you sequence applications that depend on plug-ins such as ActiveX controls or for applications that depend on middleware such as OLE DB or the Java Runtime Environment (JRE). If each application that used these dependent components required sequencing, including the components, updates to those components would require re-sequencing all the primary applications. If you sequence the primary applications without the components and then sequence the middleware or plug-in as a secondary package, then only the secondary package must be updated.
-
-One advantage of this approach is that it reduces the size of the primary packages. Another advantage is that it provides you with better control of access permissions on the secondary applications. Note that the secondary application can be streamed in the regular way and does not have to be fully cached to run.
-
-A primary package can have more than one secondary package. However, only one level of dependency is supported, so you cannot define a secondary package as dependent on another secondary package. Also the secondary application can only be middleware or a plug-in and cannot be another full software product.
-
-If you plan to make several primary applications dependent on a single middleware product, make sure that you test this configuration to determine the potential effect on system performance before you deploy it.
-
-**Important**
-Package dependencies can be specified as mandatory for a primary application. If a secondary package is flagged as mandatory and it cannot be accessed for some reason during loading, the load of the secondary package will fail. Also, the primary application will fail when the user tries to start it.
-
-
-
-You can use the following procedures to create a secondary package, for either a plug-in or a middleware component, and then you can use the final procedure to define the dependency in the OSD file of the secondary package.
-
-**To create a secondary package for a plug-in by using Dynamic Suite Composition**
-
-1. On a sequencing computer that is set up with a clean image, install Application Virtualization Sequencer and save the computer state.
-
-2. Sequence the primary application, and save the package to the Content folder on the server.
-
-3. Restore the sequencing computer to its saved state from step 1.
-
-4. Install and configure the primary application locally on the sequencing computer.
-
- **Important**
- You must specify a new package root for the secondary package.
-
-
-
-5. Start the sequencer monitoring phase.
-
-6. Install the plug-in on the sequencing computer and configure it as needed.
-
-7. Open the primary application, and confirm that the plug-in is working correctly.
-
-8. In the sequencer console, create a dummy application to represent the secondary package that will contain the plug-in and select an icon.
-
-9. Save the package to the Content folder on the server.
-
- **Note**
- To assist with management of secondary packages, it is recommended that the package name include the term “Secondary package” to emphasize that this is a package that will not function as a stand-alone application—for example, **\[Plug In Name\] Secondary package**.
-
-
-
-**To create a secondary package for middleware by using Dynamic Suite Composition**
-
-1. On a sequencing computer that is set up with a clean image, install Application Virtualization Sequencer and save the computer state.
-
-2. Install the middleware locally on the sequencing computer, and configure it.
-
-3. Sequence the primary application, and save the package to the Content folder on the server.
-
-4. Restore the sequencing computer to its saved state from step 1.
-
-5. Start the sequencer to create a new package.
-
-6. Start the sequencer monitoring phase.
-
-7. Install the middleware application on the sequencing computer, and configure it as in a typical installation.
-
-8. Complete the sequencing process.
-
-9. Save the package to the Content folder on the server.
-
- **Note**
- To assist with management of secondary packages, it is recommended that the package name include the term “Secondary package” to emphasize that this is a package that will not function as a stand-alone application—for example, **\[Middleware Name\] Secondary package**.
-
-
-
-**To define the dependency in the primary package**
-
-1. On the server, open the OSD file of the secondary package for editing. (It is a good idea to use an XML editor to make changes to the OSD file; however, you can use Notepad as an alternative.)
-
-2. Copy the **CODEBASE HREF** line from that file.
-
-3. Open the OSD file of the primary package for editing.
-
-4. Insert the <DEPENDENCIES>tag after the close of **</ENVLIST>** tag at the end of the **<VIRTUALENV>** section just before the **</VIRTUALENV>** tag.
-
-5. Paste the **CODEBASE HREF** line from the secondary package after the **<DEPENDENCIES>** tag you just created.
-
-6. If the secondary package is a mandatory package, which means that it must be started before the primary package is started, add the **MANDATORY=”TRUE”** property inside the **CODEBASE** tag. If it is not mandatory, the property can be omitted.
-
-7. Close the **<DEPENDENCIES>** tag by inserting the following:
-
- **</DEPENDENCIES>**
-
-8. Review the changes that you made to the OSD file, and then save and close the file. The following example shows how the added section should appear. The tag values shown here are for example only.
-
- **<VIRTUALENV>**
-
- **<ENVLIST>**
-
- **…**
-
- **</ENVLIST>**
-
- **<DEPENDENCIES>**
-
- **<CODEBASE HREF="rtsp://virt\_apps/package.1/package.1.sft" GUID="D54C80FA-9DFF-459D-AA33-DD852C9FBFBA" SYSGUARDFILE="package.1\\osguard.cp"/>**
-
- **<CODEBASE HREF="rtsp://sample\_apps/package.2/sample.sft" GUID="D54C80FA-9DFF-459D-AA33-DD852C9FBFBA" SYSGUARDFILE="package.2\\osguard.cp" MANDATORY="TRUE" />**
-
- **</DEPENDENCIES>**
-
- **</VIRTUALENV>**
-
-9. If the secondary package has any entries in the **<ENVLIST>** section of the OSD file, you must copy those entries to the same section in the primary package.
-
-## Related topics
-
-
-[How to Create or Upgrade Virtual Applications Using the App-V Sequencer](how-to-create-or-upgrade-virtual-applications-using--the-app-v-sequencer.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-use-the-cache-space-management-feature.md b/mdop/appv-v4/how-to-use-the-cache-space-management-feature.md
deleted file mode 100644
index a457af6266..0000000000
--- a/mdop/appv-v4/how-to-use-the-cache-space-management-feature.md
+++ /dev/null
@@ -1,60 +0,0 @@
----
-title: How to Use the Cache Space Management Feature
-description: How to Use the Cache Space Management Feature
-author: dansimp
-ms.assetid: 60965660-c015-46a8-88ac-54cbc050fe33
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Use the Cache Space Management Feature
-
-
-The FileSystem cache space management feature uses a Least Recently Used (LRU) algorithm and is enabled by default. If the space that is required for a new package would exceed the available free space in the cache, the Application Virtualization (App-V) Client uses this feature to determine which, if any, existing packages it can delete from the cache to make room for the new package. The client deletes the package with the oldest last-accessed date if it is older than the value specified in the MinPkgAge registry value. Use of the FileSystem cache space management feature can also help to avoid low cache space problems.
-
-More than one package is deleted if necessary. Packages that are locked are not deleted.
-
-**Note**
-To ensure that the cache has sufficient space allocated for all packages that might be deployed, use the **Use free disk space threshold** setting when you configure the client so that the cache can grow as needed. Alternatively, determine in advance how much disk space will be needed for the App-V cache, and at installation time, set the cache size accordingly.
-
-
-
-The cache space management feature is controlled by the UnloadLeastRecentlyUsed registry value. A value of 1 enables the feature, and a value of 0 (zero) disables it.
-
-**To enable or disable the cache space management feature**
-
-- Set the following registry value to 1 to enable the LRU algorithm. Set it to 0 (zero) to disable the feature.
-
- HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Microsoft\\SoftGrid\\4.5\\Client\\AppFS\\UnloadLeastRecentlyUsed
-
-**To control which packages can be discarded**
-
-- To determine when the package can be selected for discard, set the following registry value to equal the minimum number of days you want to elapse since the package was last accessed. Packages that have been used more recently are not discarded.
-
- HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Microsoft\\SoftGrid\\4.5\\Client\\AppFS\\MinPkgAge
-
- **Caution**
- The maximum value for this registry key is 0x00011111. Larger values will prevent the correct operation of the cache space management feature.
-
-
-
-## Related topics
-
-
-[How to Configure the App-V Client Registry Settings by Using the Command Line](how-to-configure-the-app-v-client-registry-settings-by-using-the-command-line.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-use-the-desktop-notification-area-for-application-virtualization-client-management.md b/mdop/appv-v4/how-to-use-the-desktop-notification-area-for-application-virtualization-client-management.md
deleted file mode 100644
index a8943af3a2..0000000000
--- a/mdop/appv-v4/how-to-use-the-desktop-notification-area-for-application-virtualization-client-management.md
+++ /dev/null
@@ -1,47 +0,0 @@
----
-title: How to Use the Desktop Notification Area for Application Virtualization Client Management
-description: How to Use the Desktop Notification Area for Application Virtualization Client Management
-author: dansimp
-ms.assetid: 75b2e636-7669-4e1e-8368-8b9fca567a84
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Use the Desktop Notification Area for Application Virtualization Client Management
-
-
-The notification area is a standard Windows feature that, by default, appears in the lower-right corner of the desktop. You can exercise some Application Virtualization Client functionality from the notification area without starting the Application Virtualization Client Management Console.
-
-## In This Section
-
-
-[How to Refresh Virtual Applications from the Desktop Notification Area](how-to-refresh-virtual-applications-from-the-desktop-notification-area.md)
-Provides a simple procedure you can use to refresh the list of virtualized applications authorized for the client.
-
-[How to Load Virtual Applications from the Desktop Notification Area](how-to-load-virtual-applications-from-the-desktop-notification-area.md)
-Provides procedures for loading virtualized applications into the cache.
-
-[How to Cancel Loading of Virtual Applications from the Desktop Notification Area](how-to-cancel-loading-of-virtual-applications-from-the-desktop-notification-area.md)
-Provides procedures for cancelling the loading of virtual applications.
-
-[How to Work Offline or Online with Application Virtualization](how-to-work-offline-or-online-with-application-virtualization.md)
-Provides procedures you can use to toggle between offline and online operation.
-
-[How to Exit the App-V Client from the Notification Area](how-to-exit-the-app-v-client-from-the-notification-area.md)
-Provides a simple procedure you can use to exit the application from the desktop notification area.
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-use-the-differential-sft-file.md b/mdop/appv-v4/how-to-use-the-differential-sft-file.md
deleted file mode 100644
index 963df8c7b7..0000000000
--- a/mdop/appv-v4/how-to-use-the-differential-sft-file.md
+++ /dev/null
@@ -1,72 +0,0 @@
----
-title: How to Use the Differential SFT File
-description: How to Use the Differential SFT File
-author: dansimp
-ms.assetid: 607e30fd-2f0e-4e2f-b669-0b3f010aebb0
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 08/30/2016
----
-
-
-# How to Use the Differential SFT File
-
-
-When sequencing an application, the Microsoft Application Virtualization (App-V) Sequencer creates SFT files (.sft) to store all of the virtual application’s files content and configuration information. In version 4.5 of App-V, the Differential SFT (.dsft) file has been introduced. After using the Sequencer to create an upgrade for an existing package, you can choose to generate this file to store only the differences between the original sequenced application package and the new version. It is therefore much smaller than the full SFT file would be for the new version of the application and reduces the impact of sending package updates over low-bandwidth network connections. However, its use is supported only in certain restricted situations. This feature was intended to be used specifically where you are using an electronic software distribution (ESD) system to manage a group of users with a local file server over a low-bandwidth connection and you are not using App-V streaming servers.
-
-You do not need to use the Differential SFT file if you are using Configuration Manager 2007 to manage the users, because Configuration Manager has support for low-bandwidth deployments already built in. It is also not required if you are using Application Virtualization (App-V) Management or Streaming Servers with Active Upgrade because the client will retrieve only the differences between the old and new package versions.
-
-The following procedure shows how to use the mkdiffpkg.exe that is included in the Sequencer installation to create the Differential SFT file, after completing the upgrade of the virtual application package, and to deploy the Differential SFT file. Completing this procedure helps ensure that if the package is somehow unloaded from the client computer, the next time the user tries to run the application, the client will fall back to the override URL, which is set to stream the full package V2.sft from the local file share. This will avoid any failure for the user when starting the application. If the entire client becomes corrupted or is uninstalled, it is recommended that the ESD system be configured to deploy the full version of the upgraded package, V2.sft, to the client.
-
-For more information about upgrading a package, see “How to Upgrade an Existing Virtual Application” in the App-V 4.5 Operations Guide at
-
-**Note**
-As a prerequisite, all user computers being targeted by the ESD must have the V1.sft file fully loaded into their local cache, and file streaming must be enabled on all computers.
-
-
-
-**To use the Differential SFT file**
-
-1. Log on to the Sequencer computer by using an account with administrator rights. Open the original package (V1) for upgrade in the Sequencer, and then upgrade the package to the new version (V2) and save it as a new V2.sft.
-
-2. Open a command window in the App-V 4.5 Sequencer installation folder, and run the following command:
-
- `“mkdiffpkg.exe V2.sft V2.dsft”`
-
-3. Using the ESD system or other file copy process, copy the full V2 package content file, V2.sft, to a local file share that is accessible to the user computers on a well-connected network connection.
-
-4. Using the ESD system, place a copy of the Differential SFT file, V2.dsft, on each user computer.
-
-5. To import the V2.dsft file, run the following SFTMIME command on each user computer:
-
- `“SFTMIME load package: /SFTPATH ”`
-
-6. Run the following SFTMIME command on each user computer to set the override URL to point to the V2.sft file:
-
- `“SFTMIME configure package: /OverrideURL FILE://”`
-
-**Note**
-- Differential SFT files must be applied to clients in the correct order. For example, V2.dsft must be applied to a V1 application before V3.dsft is applied.
-
-- The **Generate Microsoft Windows Installer (MSI) Package** capability in the Sequencer cannot be used with the Differential SFT file.
-
-
-
-## Related topics
-
-
-[How to Create or Upgrade Virtual Applications Using the App-V Sequencer](how-to-create-or-upgrade-virtual-applications-using--the-app-v-sequencer.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/how-to-work-offline-or-online-with-application-virtualization.md b/mdop/appv-v4/how-to-work-offline-or-online-with-application-virtualization.md
deleted file mode 100644
index 06576c4ec4..0000000000
--- a/mdop/appv-v4/how-to-work-offline-or-online-with-application-virtualization.md
+++ /dev/null
@@ -1,47 +0,0 @@
----
-title: How to Work Offline or Online with Application Virtualization
-description: How to Work Offline or Online with Application Virtualization
-author: dansimp
-ms.assetid: aa532b37-8a00-4db4-9b51-e1e8354b2495
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# How to Work Offline or Online with Application Virtualization
-
-
-If you plan to be disconnected from the network for an extended period of time, you can work in offline mode to eliminate possible delays when the Application Virtualization client attempts to communicate with the server. In offline mode, the Application Virtualization client will not attempt to communicate with the publishing server, so applications must be fully cached before enabling offline mode. Applications will not be retrieved from the content share even if they are on the local disk on the computer. You can use the following Application Virtualization Client procedure to toggle between working offline and online.
-
-**Note**
-By default, **Work Offline** is disabled for the Client for Remote Desktop Services (formerly Terminal Services). Your system administrator must change your user permissions to allow you to use this setting on a Client for Remote Desktop Services.
-
-
-
-**To work offline**
-
-- Right-click the Application Virtualization System icon in the notification area, and select **Work Offline** from the pop-up menu.
-
-**To work online**
-
-- Right-click the Application Virtualization System icon in the notification area, and select **Work Online** from the pop-up menu.
-
-## Related topics
-
-
-[How to Use the Desktop Notification Area for Application Virtualization Client Management](how-to-use-the-desktop-notification-area-for-application-virtualization-client-management.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/i b/mdop/appv-v4/i
deleted file mode 100644
index e69de29bb2..0000000000
diff --git a/mdop/appv-v4/images/appvbranchoffices.gif b/mdop/appv-v4/images/appvbranchoffices.gif
deleted file mode 100644
index 57ece467d2..0000000000
Binary files a/mdop/appv-v4/images/appvbranchoffices.gif and /dev/null differ
diff --git a/mdop/appv-v4/images/appvfirewalls.gif b/mdop/appv-v4/images/appvfirewalls.gif
deleted file mode 100644
index e72ffc5c0f..0000000000
Binary files a/mdop/appv-v4/images/appvfirewalls.gif and /dev/null differ
diff --git a/mdop/appv-v4/images/appvmgmtwebservice.gif b/mdop/appv-v4/images/appvmgmtwebservice.gif
deleted file mode 100644
index 303643d098..0000000000
Binary files a/mdop/appv-v4/images/appvmgmtwebservice.gif and /dev/null differ
diff --git a/mdop/appv-v4/images/appvperimeternetworkfirewall.gif b/mdop/appv-v4/images/appvperimeternetworkfirewall.gif
deleted file mode 100644
index b4f5a8d453..0000000000
Binary files a/mdop/appv-v4/images/appvperimeternetworkfirewall.gif and /dev/null differ
diff --git a/mdop/appv-v4/improving-security-during-app-v-sequencing.md b/mdop/appv-v4/improving-security-during-app-v-sequencing.md
deleted file mode 100644
index 2336ea5569..0000000000
--- a/mdop/appv-v4/improving-security-during-app-v-sequencing.md
+++ /dev/null
@@ -1,48 +0,0 @@
----
-title: Improving Security During App-V Sequencing
-description: Improving Security During App-V Sequencing
-author: dansimp
-ms.assetid: f30206dd-5749-4a27-bbaf-61fc21b9c663
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Improving Security During App-V Sequencing
-
-
-Packaging applications for sequencing is the largest ongoing task in an App-V infrastructure. Because this task is ongoing, you should carefully consider creating policies and procedures to follow when sequencing applications. In App-V 4.5, during sequencing, you can capture Access Control Lists (ACLs) on the file assets of the virtualized application.
-
-## Virus Scanning on the Sequencer
-
-
-It is a best practice to install the scanning software on the sequencing computer and then scan the computer for viruses and malware. After the sequencing computer is scanned and free of any viruses or malware, disable the scanning software, including all antivirus and malware detection software, on the sequencing computer before sequencing any applications. This speeds the sequencing process and prevents the scanning software components from being detected during sequencing and included in the virtual application package.
-
-## Capturing ACLs on Files (NTFS)
-
-
-The Sequencer captures NTFS permissions (the ACLs) for the files that are monitored during the sequencing installation phase. (Before the release of App-V 4.5, ACLs were not captured as part of the sequencing process.) This new feature enables certain applications to run for users with a low level of permission that would normally require Administrative privileges.
-
-This feature also enables the sequencing engineer to capture the security settings identified by the vendor. Failing to apply the settings recommended by the vendor could leave the application open to attack or misuse by users. For information about whether or not you should deploy an application with open ACLs, refer to your application support group or the software vendor.
-
-**Important**
-Although the sequencer captures the NTFS ACLs while monitoring the installation phase of sequencing, it does not capture the ACLs for the registry. Users have full access to all registry keys for virtual applications except for services. However, if a user modifies the registry of a virtual application, that change is stored in a specific location (`uservol_sftfs_v1.pkg`) and won’t affect other users.
-
-
-
-During the installation phase, a sequencing engineer can modify the default permissions of the files if necessary. After the sequencing process is complete, but before saving the package, the sequencing engineer can then choose to enforce security descriptors that were captured during the installation phase. It is a best practice to enforce security descriptors if no other solution allows the application to run properly once virtualized.
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/incompatible-installer-dialog-box--app-v-46-sp1-.md b/mdop/appv-v4/incompatible-installer-dialog-box--app-v-46-sp1-.md
deleted file mode 100644
index fd19796eb2..0000000000
--- a/mdop/appv-v4/incompatible-installer-dialog-box--app-v-46-sp1-.md
+++ /dev/null
@@ -1,42 +0,0 @@
----
-title: Incompatible Installer Dialog Box (App-V 4.6 SP1)
-description: Incompatible Installer Dialog Box (App-V 4.6 SP1)
-author: dansimp
-ms.assetid: 45d465b1-ee49-4274-8234-71dd031a07b6
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Incompatible Installer Dialog Box (App-V 4.6 SP1)
-
-
-The application did not install correctly.
-
-Use the following procedure to verify that the application you are trying to sequence is compatible with the computer running the sequencer.
-
-1. Close the App-V Sequencer.
-
-2. Install the application on the computer running the Sequencer without monitoring the installation.
-
-3. Verify that the application is compatible and can be installed successfully.
-
-## Related topics
-
-
-[Dialog Boxes (AppV 4.6 SP1)](dialog-boxes--appv-46-sp1-.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/index.md b/mdop/appv-v4/index.md
deleted file mode 100644
index 02747f94e3..0000000000
--- a/mdop/appv-v4/index.md
+++ /dev/null
@@ -1,41 +0,0 @@
----
-title: Application Virtualization 4
-description: Application Virtualization 4
-author: dansimp
-ms.assetid: 9da557bc-f433-47d3-8af7-68ec4ff9bd3f
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Application Virtualization 4
-
-
-Microsoft Application Virtualization provides the administrative capability to make applications available to end user computers without having to install the applications directly on those computers.
-
-## Technical Documentation
-
-
-The technical documentation for Application Virtualization in the TechNet Library contains the following sections:
-
-- [Microsoft Application Virtualization Getting Started Guide](microsoft-application-virtualization-getting-started-guide.md)
-
-- [Planning and Deployment Guide for the Application Virtualization System](planning-and-deployment-guide-for-the-application-virtualization-system.md)
-
-- [Operations Guide for the Application Virtualization System](operations-guide-for-the-application-virtualization-system.md)
-
-- [Online Help for Application Virtualization](online-help-for-application-virtualization.md)
-
-- [Application Virtualization Glossary](application-virtualization-glossary.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/installation-files-page.md b/mdop/appv-v4/installation-files-page.md
deleted file mode 100644
index 0825e6eddc..0000000000
--- a/mdop/appv-v4/installation-files-page.md
+++ /dev/null
@@ -1,59 +0,0 @@
----
-title: Installation Files Page
-description: Installation Files Page
-author: dansimp
-ms.assetid: b0aad26f-b143-4f09-87a1-9f016a23cb62
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Installation Files Page
-
-
-Use the **Installation Files** page to specify the installation files that were used to create the virtual application package specified on the **Select Package** page of this wizard. If you created a virtual application package that contains multiple applications, you should copy all required installation files to a single folder on the computer running the Microsoft Application Virtualization Sequencer.
-
-This page contains the following elements:
-
-**Original Installation Files**
-Click **Browse** to specify the installation files that were originally used to create the virtual application package. The parent directory you specify should be saved locally to the computer running the Sequencer and must contain all required installation files or subfolders that contain the installation files. The installation files can be contained in the parent folder or in any of the subfolders of the specified parent folder.
-
-**Files installed on local system**
-Click **Browse** to specify the installation files that have been installed locally on the computer running the Sequencer. You can only select this option if the application installation files have been installed to the application’s default location.
-
-**Note**
-The default installation location you provide depends on the following conditions:
-
-
-
-- The package root specified when the package was originally created.
-
-- The installation location specified in the Windows Installer when the package was originally created.
-
-- The default application installation path.
-
-For example, if the package root specified is **Q:\\Office12** and during installation, the default installation location is changed from **C:\\Program Files\\Office12** to **Q:\\Office12**, then the path specified during dehydration must be **C:\\Program Files\\Office 12**.
-
-If the package root specified is **Q:\\Microsoft** and during installation, the default installation location is changed from **C:\\Program Files\\Office12** to **Q:\\Microsoft\\Office12**, then the path specified during dehydration must be **C:\\Program Files**.
-
-When you create a package using a package accelerator, each file in the package, for example **Q:\\Office12\\file.txt** is found on the local computer by replacing the package root **Q:\\Office12** with the default location specified when the Package Accelerator was created, for example, **C:\\Program Files\\Office12**. In the previous example, the file should be located in **C:\\Program Files\\Office12\\file.txt**.
-
-## Related topics
-
-
-[Create Package Accelerator Wizard (AppV 4.6 SP1)](create-package-accelerator-wizard--appv-46-sp1-.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/installation-page--learn-more-.md b/mdop/appv-v4/installation-page--learn-more-.md
deleted file mode 100644
index 2979a1cb34..0000000000
--- a/mdop/appv-v4/installation-page--learn-more-.md
+++ /dev/null
@@ -1,42 +0,0 @@
----
-title: Installation Page (Learn More)
-description: Installation Page (Learn More)
-author: dansimp
-ms.assetid: a53b8330-dfc3-4540-b147-7c10529f403a
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Installation Page (Learn More)
-
-
-Use the **Installation** page to run additional installation files that are required to complete the application installation.
-
-This page contains the following elements:
-
-**Run**
-Opens the **Select installation file** dialog box. Specify the location of the additional installation files, Windows Installer and executable program files, and then click **Open**.
-
-**I am finished installing**
-Enables the **Next** button. Select this option if no additional installation files are associated with this application.
-
-## Related topics
-
-
-[Create New Package Wizard (AppV 4.6 SP1)](create-new-package-wizard---appv-46-sp1-.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/installation-report-page--learn-more-.md b/mdop/appv-v4/installation-report-page--learn-more-.md
deleted file mode 100644
index b35a3f1345..0000000000
--- a/mdop/appv-v4/installation-report-page--learn-more-.md
+++ /dev/null
@@ -1,39 +0,0 @@
----
-title: Installation Report Page (Learn More)
-description: Installation Report Page (Learn More)
-author: dansimp
-ms.assetid: 499cf4db-a39c-4dcf-b1cf-85fd7da11701
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Installation Report Page (Learn More)
-
-
-Use the **Installation Report** page to review the results of the sequencing process. These reports can help diagnose common problems that can occur during sequencing.
-
-This page contains the following elements:
-
-**Information Pane**
-Displays problems and additional information about the overall sequencing process.
-
-## Related topics
-
-
-[Create New Package Wizard (AppV 4.6 SP1)](create-new-package-wizard---appv-46-sp1-.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/installing-app-v-management-server-or-streaming-server-securely.md b/mdop/appv-v4/installing-app-v-management-server-or-streaming-server-securely.md
deleted file mode 100644
index c7ef697fc2..0000000000
--- a/mdop/appv-v4/installing-app-v-management-server-or-streaming-server-securely.md
+++ /dev/null
@@ -1,63 +0,0 @@
----
-title: Installing App-V Management Server or Streaming Server Securely
-description: Installing App-V Management Server or Streaming Server Securely
-author: dansimp
-ms.assetid: d2a51a81-a80f-427c-a727-611e1eb74f02
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 08/30/2016
----
-
-
-# Installing App-V Management Server or Streaming Server Securely
-
-
-The topics in this section provide information for installing an enhanced security version of the App-V Management Server or the App-V Streaming Server.
-
-**Note**
-Installing or configuring an App-V Management or Streaming Server to use enhanced security (for example, Transport Layer Security, or TLS) requires that an X.509 V3 certificate has been provisioned to the App-V server.
-
-
-
-When you prepare to install or configure a secure Management or Streaming Server, consider the following technical requirements:
-
-- The certificate must be valid. If the certificate is not valid, the client ends the connection.
-
-- The certificate must contain the correct *Enhanced Key Usage* (EKU)—Server Authentication (OID 1.3.6.1.5.5.7.3.1). If the certificate does not contain this EKU, the client ends the connection.
-
-- The certificate fully qualified domain name (FQDN) must match the server on which it is installed. For example, if the client is calling `RTSPS://Myserver.mycompany.com/content/MyApp.sft` and the certificate **Issued To** field is set to `Server1.mycompany.com`, the client will not connect to the server and the session ends. The failure is reported to the user.
-
- **Note**
- If you are using App-V in a Network Load Balancing cluster, you must configure the certificate with Subject Alternate Names (SANs) to support RTSPS. For information about configuring the certification authority (CA) and creating certificates with SANs, see .
-
-
-
-- The client and the server need to trust the root CA—The CA issuing the certificate to the App-V server must by trusted by the client connecting to the server. If not, the client ends the connection.
-
-- The certificate’s private key must have permissions changed to allow the App-V Service account to access the certificate. By default, App-V uses the Network Service account, and by default, the Network Service account does not have permission to access the private key, which will prevent secure connections.
-
-## In This Section
-
-
-[Configuring Certificates to Support Secure Streaming](configuring-certificates-to-support-secure-streaming.md)
-Provides information about obtaining, configuring, and installing certificates to support secure streaming.
-
-[How to Modify Private Key Permissions to Support Management Server or Streaming Server](how-to-modify-private-key-permissions-to-support-management-server-or-streaming-server.md)
-Provides procedures you can use to modify keys in Windows Server 2003 and Windows Server 2008.
-
-[Configuring Certificates to Support App-V Management Server or Streaming Server](configuring-certificates-to-support-app-v-management-server-or-streaming-server.md)
-Provides information about configuring certificates for the App-V Management or Streaming Servers, including information about configuring certificates for Network Load Balancing environments.
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/internet-facing-considerations-for-app-v-clients.md b/mdop/appv-v4/internet-facing-considerations-for-app-v-clients.md
deleted file mode 100644
index 9821a7ba66..0000000000
--- a/mdop/appv-v4/internet-facing-considerations-for-app-v-clients.md
+++ /dev/null
@@ -1,41 +0,0 @@
----
-title: Internet-Facing Considerations for App-V Clients
-description: Internet-Facing Considerations for App-V Clients
-author: dansimp
-ms.assetid: 261acde3-7112-492e-8b11-934ae45adc5f
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Internet-Facing Considerations for App-V Clients
-
-
-The topics in this section includes information about Internet-facing configurations for domain-joined and non-domain joined clients, as well as procedures you can use to assign the proper credentials to your App-V Desktop Clients.
-
-## In This Section
-
-
-[Domain-Joined and Non-Domain-Joined Clients](domain-joined-and-non-domain-joined-clients.md)
-Provides general information about configuring domain-joined or non-domain-joined clients for successful network access.
-
-[How to Assign the Proper Credentials for Windows XP](how-to-assign--the-proper-credentials-for-windows-xp.md)
-Provides a step-by-step procedure for assigning credentials on an App-V Desktop Client running Windows XP.
-
-[How to Assign the Proper Credentials for Windows Vista](how-to-assign--the-proper-credentials-for-windows-vista.md)
-Provides a step-by-step procedure for assigning credentials on an App-V Desktop Client running Windows Vista.
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/internet-facing-server-scenarios-for-perimeter-networks.md b/mdop/appv-v4/internet-facing-server-scenarios-for-perimeter-networks.md
deleted file mode 100644
index 5d2b394c68..0000000000
--- a/mdop/appv-v4/internet-facing-server-scenarios-for-perimeter-networks.md
+++ /dev/null
@@ -1,129 +0,0 @@
----
-title: Internet-Facing Server Scenarios for Perimeter Networks
-description: Internet-Facing Server Scenarios for Perimeter Networks
-author: dansimp
-ms.assetid: 8a4da6e6-82c7-49e5-b9b1-1666cba02f65
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 08/30/2016
----
-
-
-# Internet-Facing Server Scenarios for Perimeter Networks
-
-
-App-V 4.5 supports Internet-facing server scenarios, in which users who are not connected to the corporate network or who disconnect from the network can still use App-V. As shown in the following illustration, only the use of secure protocols on the Internet (RTSPS and HTTPS) is supported.
-
-
-
-You can set up an Internet-facing solution, using an ISA Server, where the App-V infrastructure is on the internal network in the following ways:
-
-- Create a Web Publishing rule for the IIS server that is hosting the ICO and OSD files—and optionally, the packages for streaming—located on the internal network. Detailed steps are provided at .
-
-- Create a Server Publishing rule for the App-V Web Management Server (RTSPS). Detailed steps are provided at [https://go.microsoft.com/fwlink/?LinkId=151983&](https://go.microsoft.com/fwlink/?LinkId=151983).
-
-As shown in the following illustration, if the infrastructure has implemented other firewalls between the client and the ISA Server or between the ISA Server and the internal network, both RTSPS (TCP 322) and HTTPS (TCP 443) firewall rules must be created to support the flow of traffic. Also, if firewalls have been implemented between the ISA Server and the internal network, the default traffic required for domain members must be permitted to tunnel through the firewall (DNS, LDAP, Kerberos, SMB/CIFS).
-
-
-
-Because the firewall solutions vary from environment to environment, the guidance provided in this topic describes the traffic that would be required to configure an Internet-facing App-V environment in the perimeter network. This information also includes the recommended internal network servers.
-
-Place the following servers in the perimeter network:
-
-- App-V Management Server
-
-- IIS server for publishing and streaming
-
-**Note**
-It is a best practice to place the Management Server and IIS server on separate computers.
-
-
-
-Place the following servers in the internal network:
-
-- Content server
-
-- Data store (SQL Server)
-
-- Active Directory Domain Controller
-
-## Traffic Requirements
-
-
-The following tables list the traffic requirements for communication from the Internet and the perimeter network and from the perimeter network to the internal network.
-
-
-
-
-
-
-
-
-
Traffic Requirements from Internet to Perimeter Network
-
Details
-
-
-
-
-
RTSPS (publishing refresh and streaming packages)
-
TCP 322 by default; this can be changed in App-V Management Server.
-
-
-
HTTPS (publishing ICO and OSD files and streaming packages)
-
TCP 443 by default; this can be changed in the IIS configuration.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Traffic Requirements from Perimeter Network to Internal Network
-
Details
-
-
-
-
-
SQL Server
-
TCP 1433 is the default but can be configured in SQL Server.
-
-
-
SMB/CIFS
-
If the content directory is located remotely from the Management Server(s) or IIS server (recommended).
-
-
-
Kerberos
-
TCP and UDP 88
-
-
-
LDAP
-
TCP and UDP 389
-
-
-
DNS
-
For name resolution of internal resources (can be eliminated with the use of host’s file on perimeter network servers)
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/introduction-to-the-application-virtualization-security-guide.md b/mdop/appv-v4/introduction-to-the-application-virtualization-security-guide.md
deleted file mode 100644
index b621871cef..0000000000
--- a/mdop/appv-v4/introduction-to-the-application-virtualization-security-guide.md
+++ /dev/null
@@ -1,85 +0,0 @@
----
-title: Introduction to the Application Virtualization Security Guide
-description: Introduction to the Application Virtualization Security Guide
-author: dansimp
-ms.assetid: 50e1d220-7a95-45b8-933b-3dadddebe26f
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 08/30/2016
----
-
-
-# Introduction to the Application Virtualization Security Guide
-
-
-This Microsoft Application Virtualization (App-V) security guide provides instructions for administrators who are responsible for configuring the security features that were selected for the App-V deployment.
-
-**Note**
-This documentation does not provide guidance for choosing the specific security options. That information is provided in the App-V Security Best Practices white paper available at .
-
-
-
-As an App-V administrator using this guide, you should be familiar with the following security-related technologies:
-
-- Active Directory Domain Services
-
-- Public key infrastructure (PKI)
-
-- Internet Protocol Security (IPsec)
-
-- Group Policies
-
-- Internet Information Services (IIS)
-
-## APP-V Infrastructure Components
-
-
-When planning an enhanced security App-V environment, you can consider several different infrastructure models.
-
-**Note**
-For more information about App-V infrastructure models, see the following documentation:
-
-- [App-V Planning and Deployment Guide](https://go.microsoft.com/fwlink/?LinkId=122063)
-
-- [Infrastructure Planning and Design Guide Series](https://go.microsoft.com/fwlink/?LinkId=151986)
-
-
-
-These models utilize some but possibly not all of the App-V components depicted in the following illustration.
-
-
-
-Application Virtualization (App-V) Management Server
-The App-V Management Server streams the package content and publishes the shortcuts and file-type associations to the App-V Client. The App-V Management Server also supports active upgrade, license management, and a database that can be used for reporting.
-
-Application Virtualization (App-V) Streaming Server
-The App-V Streaming Server hosts the packages for streaming to App-V Clients in environments such as branch offices, where the bandwidth of the connection to the App-V Management Server is insufficient for streaming package content to clients. The Streaming Server contains only streaming functionality and does not provide you with the App-V Management Console or the App-V Management Web Service.
-
-Application Virtualization (App-V) Data Store
-The App-V data store, in the SQL database, retains information related to the App-V infrastructure. The information in the App-V data store includes all application records, application assignments, and which groups manage the Application Virtualization environment.
-
-Application Virtualization (App-V) Management Service
-The App-V Management Service communicates read/write requests to the Application Virtualization data store. This component can be installed on the same computer as the App-V Management Server or on a separate computer with IIS installed.
-
-Application Virtualization (App-V) Management Console
-The App-V Management Console is a snap-in management utility for App-V Server administration. This component can be installed on the same computer as the App-V Server or on a separate workstation that has MMC 3.0 and .NET 2.0 installed.
-
-Application Virtualization (App-V) Sequencer
-The App-V Sequencer monitors and captures the installation of applications and creates virtual application packages. The output of the Sequencer consists of the application icon, the OSD file containing application definition information, a package manifest file, and an SFT file containing the application’s content files. Optionally, a Windows Installer file can be created for installing the package without using the App-V infrastructure.
-
-Application Virtualization (App-V) Client
-The App-V Client is installed on the App-V Desktop Client computer or on the App-V Terminal Services Client computer. It provides the virtual environment for the virtual application packages. The App-V Client manages the package streaming to the cache, virtual application publishing refresh, and interaction with the Application Virtualization Servers.
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/load-app.md b/mdop/appv-v4/load-app.md
deleted file mode 100644
index 8b07665623..0000000000
--- a/mdop/appv-v4/load-app.md
+++ /dev/null
@@ -1,87 +0,0 @@
----
-title: LOAD APP
-description: LOAD APP
-author: dansimp
-ms.assetid: 7b727d0c-5423-419d-92ef-7ebbc6343e79
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# LOAD APP
-
-
-Loads the specified application and all other applications in the package into the file system cache.
-
-**Note**
-The **LOAD APP** command starts the load process and a progress bar is displayed in the Desktop Notification Area. The command exits immediately after starting this process, so any load errors are displayed in the same location. Use the **LOAD PACKAGE** command if you want to start the load process from the command line without using the Desktop Notification Area.
-
-
-
-`SFTMIME LOAD APP:application [/LOG log-pathname | /GUI]`
-
-
-
-
-
-
-
-
-
Parameter
-
Description
-
-
-
-
-
APP:<application>
-
The name and version (optional) of the application to load.
-
-
-
/LOG
-
If specified, output is logged to the specified path name.
-
-
-
/GUI
-
If specified, output is presented in a Windows dialog box.
-
-
-
-
-
-
-For version 4.6, the following option has been added.
-
-
-
-
-
-
-
-
-
/LOGU
-
If specified, output is logged to the specified path name in UNICODE format.
If specified, the path to an SFT file to load from.
-
-
-
/LOG
-
If specified, output is logged to the specified path name.
-
-
-
/CONSOLE
-
If specified, output is presented in the active console window (default).
-
-
-
/GUI
-
If specified, output is presented in a Windows dialog box.
-
-
-
-
-
-
-For version 4.6, the following option has been added.
-
-
-
-
-
-
-
-
-
/LOGU
-
If specified, output is logged to the specified path name in UNICODE format.
-
-
-
-
-
-
-**Note**
-If no SFTPATH is specified, the client will load the package by using the path it has been configured to use, based on the OSD file, the ApplicationSourceRoot registry key value, or the OverrideURL setting.
-
-The **LOAD PACKAGE** command performs a synchronous load and will not be complete until the package is fully loaded or until it encounters an error condition.
-
-
-
-## Related topics
-
-
-[SFTMIME Command Reference](sftmime--command-reference.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/lock-app.md b/mdop/appv-v4/lock-app.md
deleted file mode 100644
index 1032c581d6..0000000000
--- a/mdop/appv-v4/lock-app.md
+++ /dev/null
@@ -1,86 +0,0 @@
----
-title: LOCK APP
-description: LOCK APP
-author: dansimp
-ms.assetid: 30673433-4364-499f-8116-cb135fe2716f
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# LOCK APP
-
-
-Locks the application specified in the file system cache.
-
-`SFTMIME LOCK APP:application [/LOG log-pathname | /CONSOLE | /GUI]`
-
-
-
-
-
-
-
-
-
Parameter
-
Description
-
-
-
-
-
APP:<application>
-
The name and version (optional) of the application to lock.
-
-
-
/LOG
-
If specified, output is logged to the specified path name.
-
-
-
/CONSOLE
-
If specified, output is presented in the active console window (default).
-
-
-
/GUI
-
If specified, output is presented in a Windows dialog box.
-
-
-
-
-
-
-For version 4.6, the following option has been added.
-
-
-
-
-
-
-
-
-
/LOGU
-
If specified, output is logged to the specified path name in UNICODE format.
-
-
-
-
-
-
-## Related topics
-
-
-[SFTMIME Command Reference](sftmime--command-reference.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/log-file-for-the-application-virtualization-client.md b/mdop/appv-v4/log-file-for-the-application-virtualization-client.md
deleted file mode 100644
index 1dec527a68..0000000000
--- a/mdop/appv-v4/log-file-for-the-application-virtualization-client.md
+++ /dev/null
@@ -1,62 +0,0 @@
----
-title: Log File for the Application Virtualization Client
-description: Log File for the Application Virtualization Client
-author: dansimp
-ms.assetid: ac4b3e4a-a220-4c06-bd60-af7dc318b3a9
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Log File for the Application Virtualization Client
-
-
-The log file for the Application Virtualization (App-V) Client captures detailed information about operations and error conditions. You can use it when you are verifying functionality and when you are troubleshooting issues.
-
-When the App-V Client is first installed, the log file is created by default in the location shown in the following table. The location of the log file is new for Application Virtualization (App-V) 4.5, although the location will not be changed if the client is upgraded from an earlier version.
-
-
-
-
-
-
-
-
-
Log File Name
-
Description
-
-
-
-
-
sftlog.txt
-
Provides general information about App-V Client operations and errors. Use this log as a starting point for troubleshooting App-V Client errors.
-
Log file location for either the Desktop Client or the Client for Remote Desktop Services (formerly Terminal Services):
-
-
C:\Documents and Settings\All Users\Application Data\Microsoft\Application Virtualization Client: Windows XP, Windows Server 2003
-
C:\ProgramData\Microsoft\Application Virtualization Client: Windows Vista, Windows Server 2008
-
-
-
-
-
-
-
-## Related topics
-
-
-[Application Virtualization Client Reference](application-virtualization-client-reference.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/log-files-for-the-application-virtualization-sequencer.md b/mdop/appv-v4/log-files-for-the-application-virtualization-sequencer.md
deleted file mode 100644
index fd8062d829..0000000000
--- a/mdop/appv-v4/log-files-for-the-application-virtualization-sequencer.md
+++ /dev/null
@@ -1,71 +0,0 @@
----
-title: Log Files for the Application Virtualization Sequencer
-description: Log Files for the Application Virtualization Sequencer
-author: dansimp
-ms.assetid: 1a296544-eab4-46f9-82ce-3136f8b578af
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Log Files for the Application Virtualization Sequencer
-
-
-The log files for the Application Virtualization (App-V) Sequencer provide detailed information about sequencing applications, and they can be helpful when you are verifying functionality or when you are troubleshooting issues.
-
-The following table provides information about the log files and their default locations, which are created when using the Sequencer.
-
-
-
-
-
-
-
-
-
Log File Name
-
Description
-
-
-
-
-
sft-seq-log.txt
-
Provides general information about sequencing an application. Use this log as a starting point for troubleshooting Sequencer errors.
-
-
-
-## Related topics
-
-
-[Application Virtualization Sequencer Reference](application-virtualization-sequencer-reference.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/microsoft-application-virtualization-46-service-pack-1-privacy-statement.md b/mdop/appv-v4/microsoft-application-virtualization-46-service-pack-1-privacy-statement.md
deleted file mode 100644
index fe711b15c3..0000000000
--- a/mdop/appv-v4/microsoft-application-virtualization-46-service-pack-1-privacy-statement.md
+++ /dev/null
@@ -1,146 +0,0 @@
----
-title: Microsoft Application Virtualization 4.6 Service Pack 1 Privacy Statement
-description: Microsoft Application Virtualization 4.6 Service Pack 1 Privacy Statement
-author: dansimp
-ms.assetid: e82c57ea-885d-4761-96db-4d80b1c3e1ae
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 08/30/2016
----
-
-
-# Microsoft Application Virtualization 4.6 Service Pack 1 Privacy Statement
-
-
-Microsoft is committed to protecting your privacy, while delivering software that brings you the performance, power, and convenience you desire in your personal computing. This privacy statement explains many of the data collection and use practices of Microsoft Application Virtualization, 4.6 Service Pack 1 (“App-V”). Specifically, the privacy statement describes the features in Service Pack 1 that send information to others, including Microsoft. It does not apply to other online or offline Microsoft sites, products, or services.
-
-App-V transforms applications into virtualized, network-available services resulting in dynamic delivery of software that is never installed, does not conflict, and minimizes costly application compatibility testing. Users and their application environments are no longer machine-specific, and the machines themselves are no longer user-specific, enabling IT to be flexible and responsive to business needs, and significantly reducing the cost of PC management, including application and operating system (OS) migrations.
-
-## Collection and Use of Your Information
-
-
-The information we collect from you will be used by Microsoft and its controlled subsidiaries and affiliates to enable the features you are using and provide the service(s) or carry out the transaction(s) you have requested or authorized. It may also be used to analyze and improve Microsoft products and services.
-
-We may send certain mandatory service communications such as welcome letters, billing reminders, information on technical service issues, and security announcements. Some Microsoft services may send periodic member letters that are considered part of the service. We may occasionally request your feedback, invite you to participate in surveys, or send you promotional mailings to inform you of other products or services available from Microsoft and its affiliates.
-
-In order to offer you a more consistent and personalized experience in your interactions with Microsoft, information collected through one Microsoft service may be combined with information obtained through other Microsoft services. We may also supplement the information we collect with information obtained from other companies. For example, we may use services from other companies that enable us to derive a general geographic area based on your IP address in order to customize certain services to your geographic area.
-
-Except as described in this statement, personal information you provide will not be transferred to third parties without your consent. We occasionally hire other companies to provide limited services on our behalf, such as packaging, sending and delivering purchases and other mailings, answering customer questions about products or services, processing event registration, or performing statistical analysis of our services. We will only provide those companies the personal information they need to deliver the service, and they are prohibited from using that information for any other purpose.
-
-Microsoft may access or disclose information about you, including the content of your communications, in order to: (a) comply with the law or respond to lawful requests or legal process; (b) protect the rights or property of Microsoft or our customers, including the enforcement of our agreements or policies governing your use of the services; or (c) act on a good faith belief that such access or disclosure is necessary to protect the personal safety of Microsoft employees, customers, or the public. We may also disclose personal information as part of a corporate transaction such as a merger or sale of assets.
-
-Information that is collected by or sent to Microsoft App-V may be stored and processed in the United States or any other country in which Microsoft or its affiliates, subsidiaries, or service providers maintain facilities. Microsoft abides by the safe harbor framework as set forth by the U.S. Department of Commerce regarding the collection, use, and retention of data from the European Union, the European Economic Area, and Switzerland.
-
-## Collection and Use of Information about Your Computer
-
-
-When you use software with Internet-enabled features, information about your computer ("standard computer information") is sent to the Web sites you visit and online services you use. Microsoft uses standard computer information to provide you Internet-enabled services, to help improve our products and services, and for statistical analysis. Standard computer information typically includes information such as your IP address, operating system version, browser version, and regional and language settings. In some cases, standard computer information may also include hardware ID, which indicates the device manufacturer, device name, and version. If a particular feature or service sends information to Microsoft, standard computer information will be sent as well.
-
-The privacy details for each App-V feature, software or service listed in this privacy statement describe what additional information is collected and how it is used.
-
-## Security of your information
-
-
-Microsoft is committed to helping protect the security of your information. We use a variety of security technologies and procedures to help protect your information from unauthorized access, use, or disclosure. For example, we store the information you provide on computer systems with limited access, which are located in controlled facilities.
-
-## Changes to this privacy statement
-
-
-We will occasionally update this privacy statement to reflect changes in our products, services, and customer feedback. When we post changes, we will revise the "last updated" date at the top of this statement. If there are material changes to this statement or in how Microsoft will use your personal information, we will notify you either by posting a notice of such changes prior to implementing the change or by directly sending you a notification. We encourage you to periodically review this statement to be informed of how Microsoft is protecting your information.
-
-## For More Information
-
-
-Microsoft welcomes your comments regarding this privacy statement. If you have questions about this statement or believe that we have not adhered to it, please contact us at:
-
-Microsoft Privacy
-
-Microsoft Corporation
-
-One Microsoft Way
-
-Redmond, Washington 98052 USA
-
-## Specific features
-
-
-The remainder of this document will address the following specific features:
-
-## Customer Experience Improvement Program
-
-
-### What This Feature Does:
-
-The Customer Experience Improvement Program (“CEIP”) collects basic information about your hardware configuration and how you use our software and services in order to identify trends and usage patterns. CEIP also collects the type and number of errors you encounter, software and hardware performance, and the speed of services. We will not collect your name, address, or other contact information.
-
-### Information Collected, Processed, or Transmitted:
-
-For more information about the information collected, processed, or transmitted by CEIP, see the CEIP privacy statement at .
-
-### Use of Information:
-
-We use this information to improve the quality, reliability, and performance of Microsoft software and services.
-
-### Choice/Control:
-
-You are offered the opportunity to participate in CEIP during setup. If you choose to participate and later change your mind, you can turn off CEIP at any time by:
-
-1. Select “Help” on the main toolbar.
-
-2. Select “Customer Feedback Options”.
-
-## Microsoft Error Reporting
-
-
-### What This Feature Does:
-
-Microsoft Error Reporting provides a service that allows you to report problems you may be having with App-V to Microsoft and to receive information that may help you avoid or solve such problems.
-
-### Information Collected, Processed, or Transmitted:
-
-For information about the information collected, processed, or transmitted by Microsoft Error Reporting, see the Microsoft Error Reporting privacy statement at .
-
-### Use of Information:
-
-We use the error reporting data to solve customer problems and improve our software and services.
-
-### Important Information:
-
-App-V does not change your Microsoft Error Reporting settings. If you previously turned on error reporting, it will send the information described above. Enterprise customers can use Group Policy to configure how Microsoft Error Reporting behaves on their computers. Configuration options include the ability to turn off Microsoft Error Reporting. If you are an administrator and wish to configure Group Policy for Microsoft Error Reporting, technical details are available at [https://go.microsoft.com/fwlink/?LinkId=35776](https://go.microsoft.com/fwlink/?LinkID=35776).
-
-## Application Package Accelerators
-
-
-### What This Feature Does:
-
-Customers can use Application Package Accelerators to automatically package complex applications without installing the application. The App-V sequencer allows you to create package accelerators for each virtual package. You can then use these package accelerators to automatically re-create the same virtual package in the future. You may also use package accelerators released by Microsoft or other third parties to simplify and automate packaging of complex applications.
-
-### Information Collected, Processed, or Transmitted:
-
-Application Package Accelerators may contain information such as computer names, user account information, and information about applications included in the Package Accelerator file.
-
-If you plan to share Application Package Accelerators with anyone outside your organization you should review all the settings and ensure the Package Accelerators do not contain any personal or company information. You can view the contents by opening the Package Accelerator files using any XML viewer. The following are ways you can view and remove any computer or user information from the Package Accelerator files before sharing with anyone outside your company:
-
-- **Username** - When you log on to the computer running the App-V sequencer you should use a generic user account, such as **administrator**. You should not use an account that is based on an existing username.
-
-- **Computer Name**– Specify a general, non-identifying name for the computer that is running the App-V Sequencer.
-
-- **Server URL**– Use the default settings for the server URL configuration information on the **Deployment** tab in the App-V Sequencer console.
-
-- **Applications** – If you do not want to share the list of applications that were installed on the computer running the sequencer when you created the Package Accelerator you must delete the **appv\_manifest.xml** file. This file is located in the package root directory of the virtual application package.
-
-No information is sent to Microsoft through customers’ use of the Application Package Accelerator feature.
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/microsoft-application-virtualization-46-service-pack-2-privacy-statement.md b/mdop/appv-v4/microsoft-application-virtualization-46-service-pack-2-privacy-statement.md
deleted file mode 100644
index 55db6ca874..0000000000
--- a/mdop/appv-v4/microsoft-application-virtualization-46-service-pack-2-privacy-statement.md
+++ /dev/null
@@ -1,227 +0,0 @@
----
-title: Microsoft Application Virtualization 4.6 Service Pack 2 Privacy Statement
-description: Microsoft Application Virtualization 4.6 Service Pack 2 Privacy Statement
-author: dansimp
-ms.assetid: 4ee569b2-7711-475a-9f17-70247f00b1b7
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 08/30/2016
----
-
-
-# Microsoft Application Virtualization 4.6 Service Pack 2 Privacy Statement
-
-
-Microsoft is committed to protecting your privacy, while delivering software that brings you the performance, power, and convenience you desire in your personal computing. This privacy statement explains many of the data collection and use practices of Microsoft Application Virtualization (App-V). Specifically, the privacy statement describes the features that send information to others, including Microsoft. It does not apply to other online or offline Microsoft sites, products, or services.
-
-App-V transforms applications into virtualized, network-available services resulting in dynamic delivery of software that is never installed, does not conflict, and minimizes costly application compatibility testing. Users and their application environments are no longer machine-specific, and the machines themselves are no longer user-specific, enabling IT to be flexible and responsive to business needs, and significantly reducing the cost of PC management, including application and operating system (OS) migrations.
-
-## Collection and Use of Your Information
-
-
-The information we collect from you will be used by Microsoft and its controlled subsidiaries and affiliates to enable the features you are using and provide the service(s) or carry out the transaction(s) you have requested or authorized. It may also be used to analyze and improve Microsoft products and services.
-
-We may send certain mandatory service communications such as welcome letters, billing reminders, information on technical service issues, and security announcements. Some Microsoft services may send periodic member letters that are considered part of the service. We may occasionally request your feedback, invite you to participate in surveys, or send you promotional mailings to inform you of other products or services available from Microsoft and its affiliates.
-
-In order to offer you a more consistent and personalized experience in your interactions with Microsoft, information collected through one Microsoft service may be combined with information obtained through other Microsoft services. We may also supplement the information we collect with information obtained from other companies. For example, we may use services from other companies that enable us to derive a general geographic area based on your IP address in order to customize certain services to your geographic area.
-
-Except as described in this statement, personal information you provide will not be transferred to third parties without your consent. We occasionally hire other companies to provide limited services on our behalf, such as packaging, sending and delivering purchases and other mailings, answering customer questions about products or services, processing event registration, or performing statistical analysis of our services. We will only provide those companies the personal information they need to deliver the service, and they are prohibited from using that information for any other purpose.
-
-Microsoft may access or disclose information about you, including the content of your communications, in order to: (a) comply with the law or respond to lawful requests or legal process; (b) protect the rights or property of Microsoft or our customers, including the enforcement of our agreements or policies governing your use of the services; or (c) act on a good faith belief that such access or disclosure is necessary to protect the personal safety of Microsoft employees, customers, or the public. We may also disclose personal information as part of a corporate transaction such as a merger or sale of assets.
-
-Information that is collected by or sent to Microsoft by App-V may be stored and processed in the United States or any other country in which Microsoft or its affiliates, subsidiaries, or service providers maintain facilities. Microsoft abides by the safe harbor framework as set forth by the U.S. Department of Commerce regarding the collection, use, and retention of data from the European Union, the European Economic Area, and Switzerland.
-
-## Collection and Use of Information about Your Computer
-
-
-When you use software with Internet-enabled features, information about your computer ("standard computer information") is sent to the Web sites you visit and online services you use. Microsoft uses standard computer information to provide you Internet-enabled services, to help improve our products and services, and for statistical analysis. Standard computer information typically includes information such as your IP address, operating system version, browser version, and regional and language settings. In some cases, standard computer information may also include hardware ID, which indicates the device manufacturer, device name, and version. If a particular feature or service sends information to Microsoft, standard computer information will be sent as well.
-
-Because this is a pre-release version of the software, some of these Internet-enabled features are turned on by default so that we can collect enough information about how the software is working in order to improve the commercially released software. The default settings in this pre-release software do not necessarily reflect how these features will be configured in the commercially released software.
-
-The privacy details for each App-V feature, software or service listed in this privacy statement describe what additional information is collected and how it is used.
-
-## Security of your information
-
-
-Microsoft is committed to helping protect the security of your information. We use a variety of security technologies and procedures to help protect your information from unauthorized access, use, or disclosure. For example, we store the information you provide on computer systems with limited access, which are located in controlled facilities.
-
-## Changes to this privacy statement
-
-
-We will occasionally update this privacy statement to reflect changes in our products, services, and customer feedback. When we post changes, we will revise the "last updated" date at the top of this statement. If there are material changes to this statement or in how Microsoft will use your personal information, we will notify you either by posting a notice of such changes prior to implementing the change or by directly sending you a notification. We encourage you to periodically review this statement to be informed of how Microsoft is protecting your information.
-
-## For More Information
-
-
-Microsoft welcomes your comments regarding this privacy statement. If you have questions about this statement or believe that we have not adhered to it, please contact us at .
-
-## Specific features
-
-
-The remainder of this document will address the following specific features:
-
-**Note**
-This section is divided into two parts: (1) features in all versions of App-V and (2) features in App-V 4.6 SP1 and later.
-
-
-
-### Microsoft Error Reporting
-
-**What This Feature Does:**
-
-Microsoft Error Reporting provides a service that allows you to report problems you may be having with App-V to Microsoft and to receive information that may help you avoid or solve such problems.
-
-**Information Collected, Processed, or Transmitted:**
-
-For information about the information collected, processed, or transmitted by Microsoft Error Reporting, see the Microsoft Error Reporting privacy statement at .
-
-**Use of Information:**
-
-We use the error reporting data to solve customer problems and improve our software and services.
-
-**Choice/Control:**
-
-App-V does not change your Microsoft Error Reporting settings. If you previously turned on error reporting, it will send Microsoft the information about the errors you encountered. When Microsoft needs additional data to analyze the problem, you will be prompted to review the data and choose whether or not to send it. App-V will always respect your Microsoft Error Reporting settings.
-
-**Important Information:**
-
-Enterprise customers can use Group Policy to configure how Microsoft Error Reporting behaves on their computers. Configuration options include the ability to turn off Microsoft Error Reporting. If you are an administrator and wish to configure Group Policy for Microsoft Error Reporting, technical details are available at .
-
-### Microsoft Update
-
-**What This Feature Does:**
-
-Microsoft Update is a service that provides Windows updates as well as updates for other Microsoft software, including App-V. For details about what information is collected, how it is used and how to change your settings, see the Update Services Privacy Statement at .
-
-**Choice/Control:**
-
-If Microsoft Update is not enabled, you can opt-in during setup and subsequent checks for updates will follow the machine-wide schedule. You can update this option from the Microsoft Update Control Panel item.
-
-### Collection/Transmission of Configuration Data
-
-**What This Feature Does:**
-
-The product will collect various configuration items, including UserID, MachineID and SecurityGroup details, to be able to enforce settings on managed nodes. The data is stored in the App-V SQL database and transmitted across the App-V server and client components to enforce the configuration on the managed node.
-
-**Information Collected, Processed, or Transmitted:**
-
-User and machine information and configuration content
-
-**Use of Information:**
-
-The information is used to enforce the application access configuration on the managed nodes within the enterprise. The information does not leave the enterprise.
-
-**Choice/Control:**
-
-By default, the product does not have any data. All data is entered and enabled by the admin and can be viewed in the Management console. The feature cannot be disabled as this is the product functionality. To disable this, App-V will need to be uninstalled.
-
-**Important Information:**
-
-None of this information is sent out of the enterprise.
-
-### Package History Information
-
-**What This Feature Does:**
-
-It captures package history and asset information as part of the package.
-
-**Information Collected, Processed, or Transmitted:**
-
-Information about the package and the sequencing environment is collected and stored in the package manifest during sequencing.
-
-**Use of Information:**
-
-The information will be used by the admin to track the updates done to a package during its lifecycle. It will also be used by software deployment systems to track the package deployments within the organization.
-
-**Choice/Control:**
-
-This feature is always enabled and cannot be turned off.
-
-**Important Information:**
-
-This administrator information will be stored in the package and can be viewed by the end users if they access the XML associated with the application.
-
-### Collection and Transmission of Reporting Data
-
-**What This Feature Does:**
-
-The product will collect a variety of reporting data points, including the username, to allow reporting on the usage of the product.
-
-**Information Collected, Processed, or Transmitted:**
-
-Information about the machine, package and application usage are collected from every machine that reporting is enabled on.
-
-**Use of Information:**
-
-The information is used to report on application usage within the enterprise. The information does not leave the enterprise.
-
-**Choice/Control:**
-
-By default, the product does not have any data. Data is only collected once the reporting feature is enabled on the App-V Client. To disable the collection of reporting data, the reporting feature must be disabled on all clients.
-
-**Important Information:**
-
-None of this information is sent out of the enterprise.
-
-### Features in App-V 4.6 SP1 and later
-
-This section addresses specific features available in App-V 4.6 SP1 and later.
-
-### Customer Experience Improvement Program
-
-**What This Feature Does:**
-
-The Customer Experience Improvement Program (“CEIP”) collects basic information about your hardware configuration and how you use our software and services in order to identify trends and usage patterns. CEIP also collects the type and number of errors you encounter, software and hardware performance, and the speed of services. We will not collect your name, address, or other contact information.
-
-**Information Collected, Processed, or Transmitted:**
-
-For more information about the information collected, processed, or transmitted by CEIP, see the CEIP privacy statement at .
-
-**Use of Information:**
-
-We use this information to improve the quality, reliability, and performance of Microsoft software and services.
-
-**Choice/Control:**
-
-CEIP is optional and the opt-in status can be updated during install or post install from the GUI.
-
-### Application Package Accelerators
-
-**What This Feature Does:**
-
-Customers can use Application Package Accelerators to automatically package complex applications without installing the application. The App-V sequencer allows you to create package accelerators for each virtual package. You can then use these package accelerators to automatically re-create the same virtual package in the future. You may also use package accelerators released by Microsoft or other third parties to simplify and automate packaging of complex applications.
-
-**Information Collected, Processed, or Transmitted:**
-
-Application Package Accelerators may contain information such as computer names, user account information, and information about applications included in the Package Accelerator file.
-
-If you plan to share Application Package Accelerators with anyone outside your organization you should review all the settings and ensure the Package Accelerators do not contain any personal or company information. You can view the contents by opening the Package Accelerator files using any XML viewer. The following are ways you can view and remove any computer or user information from the Package Accelerator files before sharing with anyone outside your company:
-
-- **Username** - When you log on to the computer running the App-V sequencer you should use a generic user account, such as **administrator**. You should not use an account that is based on an existing username.
-
-- **Computer Name**– Specify a general, non-identifying name for the computer that is running the App-V Sequencer.
-
-- **Server URL**– Use the default settings for the server URL configuration information on the **Deployment** tab in the App-V Sequencer console.
-
-- **Applications** – If you do not want to share the list of applications that were installed on the computer running the sequencer when you created the Package Accelerator you must delete the **appv\_manifest.xml** file. This file is located in the package root directory of the virtual application package.
-
-No information is sent to Microsoft through customers’ use of the Application Package Accelerator feature.
-
-## Related topics
-
-
-[About Microsoft Application Virtualization 4.6 SP2](about-microsoft-application-virtualization-46-sp2.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/microsoft-application-virtualization-client-management-help.md b/mdop/appv-v4/microsoft-application-virtualization-client-management-help.md
deleted file mode 100644
index c0c55aa648..0000000000
--- a/mdop/appv-v4/microsoft-application-virtualization-client-management-help.md
+++ /dev/null
@@ -1,51 +0,0 @@
----
-title: Microsoft Application Virtualization Client Management Help
-description: Microsoft Application Virtualization Client Management Help
-author: dansimp
-ms.assetid: 449eebda-70eb-48b7-855a-db965a680923
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 08/30/2016
----
-
-
-# Microsoft Application Virtualization Client Management Help
-
-
-The Microsoft Application Virtualization Desktop Client and the Client for Remote Desktop Services (formerly Terminal Services) provide the interface you can use to manage virtual applications on your computer. Through the user interface, you can manage applications and file type associations, and you can refresh applications from the Application Virtualization Management Servers (also referred to as application publishing servers).
-
-This help documentation supports the Application Virtualization Desktop Client and Client for Remote Desktop Services. It includes conceptual information, step-by-step procedures, and a user interface reference.
-
-For the latest updates to this help documentation, please visit the Microsoft TechNet Library at .
-
-## In This Section
-
-
-[Application Virtualization Client Management Console Roadmap](application-virtualization-client-management-console-roadmap.md)
-Includes overview information about the Client Management Console.
-
-[About Virtual Environments](about-virtual-environments.md)
-Describes virtual environments and the way virtual applications affect the environment.
-
-[How to Use the Desktop Notification Area for Application Virtualization Client Management](how-to-use-the-desktop-notification-area-for-application-virtualization-client-management.md)
-Includes information about using the features and commands that are available from the Windows desktop notification area.
-
-[Application Virtualization Client Management Console](application-virtualization-client-management-console.md)
-Includes an overview as well as step-by-step procedures for using the features and commands that are available in the Application Virtualization Client.
-
-[Application Virtualization Client Management Console Reference](application-virtualization-client-management-console-reference.md)
-Includes reference information about the screen elements and dialog boxes that are available in the Application Virtualization Desktop Client and the Client for Remote Desktop Services.
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/microsoft-application-virtualization-getting-started-guide.md b/mdop/appv-v4/microsoft-application-virtualization-getting-started-guide.md
deleted file mode 100644
index 6f19e8f359..0000000000
--- a/mdop/appv-v4/microsoft-application-virtualization-getting-started-guide.md
+++ /dev/null
@@ -1,59 +0,0 @@
----
-title: Microsoft Application Virtualization Getting Started Guide
-description: Microsoft Application Virtualization Getting Started Guide
-author: dansimp
-ms.assetid: 6cd9a212-e270-4d7c-bd0a-bd6af9a5c3ba
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Microsoft Application Virtualization Getting Started Guide
-
-
-This Getting Started Guide provides essential information that will help you design your Microsoft Application Virtualization (App-V) system and assist in your deployment and upgrade planning.
-
-## In This Section
-
-
-[Overview of Application Virtualization](overview-of-application-virtualization.md)
-Provides a summary of the App-V system features.
-
-[Planning for Application Virtualization System Deployment](planning-for-application-virtualization-system-deployment.md)
-Provides the guidance necessary to plan the implementation and deployment of your Application Virtualization system, and to migrate from previous versions.
-
-[Application Virtualization Deployment and Upgrade Considerations](application-virtualization-deployment-and-upgrade-considerations-copy.md)
-Provides information about hardware and software requirements for installing the various Application Virtualization components and upgrade information.
-
-[About Microsoft Application Virtualization 4.5](about-microsoft-application-virtualization-45.md)
-Describes the features introduced in App-V 4.5 and also includes the App-V 4.5 release notes documentation.
-
-[About Microsoft Application Virtualization 4.5 SP1](about-microsoft-application-virtualization-45-sp1.md)
-Describes the changes introduced in App-V 4.5 with SP1 and also includes the App-V 4.5 SP1 release notes documentation.
-
-[About Microsoft Application Virtualization 4.5 SP2](about-microsoft-application-virtualization-45-sp2.md)
-Describes what’s new in App-V 4.5 with SP2 and also includes the App-V 4.5 SP2 release notes documentation.
-
-[About Microsoft Application Virtualization 4.6](about-microsoft-application-virtualization-46.md)
-Describes what’s new in App-V 4.6 and also includes the App-V 4.6 release notes documentation.
-
-[About Microsoft Application Virtualization 4.6 SP1](about-microsoft-application-virtualization-46-sp1.md)
-Describes what’s new in App-V 4.6 SP1 and also includes the App-V 4.6 release notes documentation.
-
-[About Microsoft Application Virtualization 4.6 SP3](about-microsoft-application-virtualization-46-sp3.md)
-Describes what’s new in App-V 4.6 SP3 and also includes the App-V 4.6 release notes documentation.
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/microsoft-application-virtualization-management-system-release-notes-45-sp1.md b/mdop/appv-v4/microsoft-application-virtualization-management-system-release-notes-45-sp1.md
deleted file mode 100644
index 2add0e46ac..0000000000
--- a/mdop/appv-v4/microsoft-application-virtualization-management-system-release-notes-45-sp1.md
+++ /dev/null
@@ -1,221 +0,0 @@
----
-title: Microsoft Application Virtualization Management System Release Notes 4.5 SP1
-description: Microsoft Application Virtualization Management System Release Notes 4.5 SP1
-author: dansimp
-ms.assetid: 5d6b11ea-7b87-4084-9a7c-0d831f247aa3
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 08/30/2016
----
-
-
-# Microsoft Application Virtualization Management System Release Notes 4.5 SP1
-
-
-To search these Release Notes, press CTRL+F.
-
-**Important**
-Read these Release Notes thoroughly before you install the Application Virtualization Management System. These Release Notes contain information that you need to successfully install the Application Virtualization Management System. These Release Notes contain information that is not available in the product documentation. If there is a discrepancy between these Release Notes and other Application Virtualization Management System documentation, the latest change should be considered authoritative.
-
-
-
-For updated information about known issues, please visit the Microsoft TechNet Library at .
-
-## About Microsoft Application Virtualization 4.5 Service Pack 1
-
-
-These Release Notes have been updated to reflect the changes introduced with Microsoft Application Virtualization (App-V) 4.5 Service Pack 1 (SP1). This service pack contains the following changes:
-
-- Support for Windows 7 and Windows Server 2008 R2: App-V 4.5 SP1 provides support for Windows 7 and Windows Server 2008 R2, including support for Windows 7 features such as the taskbar, AppLocker, BranchCache, and BitLocker To Go. Windows Server 2008 R2 support is for the Application Virtualization Server only. For more information on AppLocker support in Windows 7, see .
-
-- Support for 3rd Party Kerberos Realms: App-V 4.5 SP1 provides support for environments that have a trust relationship and mapped user accounts between a Windows domain and an MIT Kerberos realm, which is a scenario that is common at many universities. For information on how to enable this support, please visit the Microsoft TechNet Library at .
-
-- Improved support for application publishing and streaming via HTTP/HTTPS: App-V 4.5 SP1 provides support for application publishing and streaming via the HTTP/HTTPS protocols for Windows XP Home Edition, Windows Vista Home Basic, and Windows 7 Home Basic.
-
-- Customer Feedback and Hotfix Rollup: App-V 4.5 SP1 also includes a rollup up of fixes to address issues found since the Microsoft Application Virtualization (App-V) 4.5 CU1 release. The updates are a result of a combination of known issues and customer feedback from our internal teams, partners, and customers who are using App-V 4.5. For a full list of the updates, see the KB article at .
-
-## About the Product Documentation
-
-
-Comprehensive documentation for Application Virtualization (App-V) is available on Microsoft TechNet in the Application Virtualization (App-V) TechCenter at . The TechNet documentation includes the online Help for the Application Virtualization Sequencer, the Application Virtualization Client, and the Application Virtualization Server. It also includes the Application Virtualization Planning and Deployment Guide and the Application Virtualization Operations Guide.
-
-## Protect Against Security Vulnerabilities and Viruses
-
-
-To help protect against security vulnerabilities and viruses, we recommend that you install the latest available security updates for any new software being installed. For more information, see the Microsoft Security Web site at .
-
-## Providing Feedback
-
-
-You can provide feedback, make a suggestion, or report an issue with the Microsoft Application Virtualization (App-V) Management System via a community forum on the Microsoft Application Virtualization TechCenter ().
-
-You can also provide your feedback on the documentation directly to the App-V documentation team. Send your documentation feedback to appvdocs@microsoft.com.
-
-## Known Issues with Application Virtualization 4.5 SP1
-
-
-This section provides the most up-to-date information about issues with Microsoft Application Virtualization (App-V) 4.5 SP1. These issues do not appear in the product documentation and in some cases might contradict existing product documentation. Whenever possible, these issues will be addressed in later releases of the software.
-
-### Guidance for installing Server Management Console
-
-If you need to install management software onto systems other than the primary Application Virtualization publishing and streaming server, the server install supports installing the Management Console and Management Web service on separate servers from the primary App-V Management Server. To distribute the management components across multiple servers, Kerberos delegation must be enabled on the server where the Web service is installed. For information on how to enable this support, please visit the Microsoft TechNet Library at
-
-### Guidance for installing or upgrading clients to App-V 4.5 SP1 using setup.msi
-
-When installing or upgrading your App-V clients to App-V 4.5 SP1 by using setup.msi, the prerequisites are not installed automatically.
-
-WORKAROUND You must manually install the prerequisites before installing or upgrading the App-V client to App-V 4.5 SP1. For detailed procedures for installing the prerequisites and the App-V client, see .
-
-When this has been completed, install the App-V 4.5 SP1 client by using setup.msi with elevated privileges. This file is available on the App-V 4.5 SP1 release media in the Installers\\Client folder.
-
-When installing Microsoft Application Error Reporting, use the following command if you are installing or upgrading to the App-V 4.5 SP1 Desktop client:
-
- msiexec /i dw20shared.msi APPGUID={93468B43-C19D-44F9-8BCC-114076DB0443} allusers=1 reboot=suppress REINSTALL=all REINSTALLMODE=vomus
-
-Alternatively, if you are installing or upgrading to the App-V 4.5 SP1 Client for Remote Desktop Services (formerly Terminal Services), use the following command:
-
- msiexec /i dw20shared.msi APPGUID={0042AD3C-99A4-4E58-B5F0-744D5AD96E1C} allusers=1 reboot=suppress REINSTALL=all REINSTALLMODE=vomus
-
-**Note**
-The APPGUID parameter references the product code of the App-V client that you install or upgrade. The product code is unique for each setup.msi. You can use the Orca database editor or a similar tool to examine Windows Installer files and determine the product code. This step is required for all installations or upgrades to App-V 4.5 SP1.
-
-
-
-### Improving performance when sequencing the .NET Framework
-
-When sequencing the .NET Framework, you might experience reduced system performance because the Microsoft .NET Framework NGEN service attempts to precompile assemblies as a background task.
-
-WORKAROUND When sequencing the .NET Framework, disable the Microsoft .NET Framework NGEN service (mscorsvw.exe) after completing the monitoring phase. You must use the **Virtual Services** tab in the Sequencer and change the startup type to disabled.
-
-### When you uninstall the Microsoft Application Virtualization Client, user settings associated with the user performing the uninstall will be deleted
-
-When you uninstall the App-V Client, the Windows Installer will remove Application Virtualization settings from the current user's profile. If your computer uses roaming profiles, do not use your personal network account to uninstall the client because it will remove settings for your virtual applications on all of your computers.
-
-WORKAROUND You should perform the App-V Client uninstall with an administrative account that is not used for running virtual applications.
-
-### Edits made on the virtual file system and virtual registry tabs must be saved while running the Sequencing wizard
-
-If you open a package to perform an upgrade, or if you have already run the Sequencing wizard with a new package and make changes to the package in the virtual file system or virtual registry tabs, those changes are not automatically saved.
-
-WORKAROUND Save the changes before re-running the wizard, to ensure that they are reflected inside the wizard’s virtual environment.
-
-### Command-line Sequencer must be run from an elevated command prompt
-
-When you use the command-line Sequencer, it does not prompt for elevation.
-
-WORKAROUND Run the command-line Sequencer using an elevated command prompt.
-
-### Short path variable names in OSD files can cause errors
-
-If you receive error 450478-1F702339-0000010B “The directory name is invalid” when starting a virtual application on the client, it is possible that the variable in the OSD is set incorrectly. This can happen if the application’s installer sets a short path name during sequencing.
-
-WORKAROUND Remove the trailing tilde from any CSIDL variable that exists in the OSD file.
-
-### Correct syntax for DECODEPATH parameter for command-line Sequencer
-
-In the command-line Sequencer, when opening a package for upgrade and decoding it to the root of the Q drive, the syntax for the *DECODEPATH* parameter should not include a trailing slash.
-
-WORKAROUND You can use **Q:** rather than **Q:\\** (omitting the trailing “\\” character).
-
-### When upgrading 4.2 packages, you encounter problems caused by Windows Installer files in the Virtual File System
-
-When upgrading a package from 4.2, you might experience issues relating to a mismatch of Windows Installer system files that were included by default in 4.2 and the Windows Installer libraries locally installed on your Sequencing workstation. The following files are located in CSIDL\_SYSTEM\\:
-
-cabinet.dll
-
-msi.dll
-
-msiexec.exe
-
-msihnd.dll
-
-msimsg.dlll
-
-WORKAROUND Delete all of the preceding files from the package. Delete the mappings on the **VFS** tab as well as the actual files in the CSIDL\_SYSTEM folder in your decode path.
-
-### On Windows XP, client install logging is not enabled by default
-
-When installing the client, to ensure that any install errors are captured for troubleshooting purposes, you should enable logging by using the command line.
-
-WORKAROUND Add the parameter */l\*vx! log.txt* to the command line, as shown in the following example:
-
-setup.exe /s /v”/qn /l\*vx! log.txt”
-
-msiexec.exe /i setup.msi /qn /l\*vx! log.txt
-
-Alternatively, you can set the registry key to the following value:
-
-\[HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Policies\\Microsoft\\Windows\\Installer\] "Logging"="voicewarmupx!"
-
-### For Kerberos authentication to work, Service Principal Names (SPNs) must be registered for IIS
-
-When using IIS 6.0 or 7.0 for icon or OSD file retrieval and streaming of packages, for Kerberos authentication to be enabled, the SPNs must be registered as follows:
-
-- On the IIS server, run the following commands by using the SETSPN.EXE Resource Kit tool. The server fully qualified domain name (FQDN) must be used.
-
- Setspn -r SOFTGRID/<Server FQDN>
-
- Setspn -r HTTP/<Server FQDN>
-
-For more information, see .
-
-### .NET compatibility changes
-
-Microsoft Application Virtualization (App-V) Cumulative Update 1 or later supports sequencing the .NET Framework on Windows XP (SP2 or later). Sequencing routines for .NET applications that were written for SoftGrid 4.2 might need to be updated when used with the App-V 4.5 Sequencer. For details and workarounds, please refer to the Knowledge Base article at .
-
-### After client upgrade from App-V 4.2, some applications are not shown
-
-Check for the following error in the log: ”The Application Virtualization Client could not parse the OSD file”. The App-V 4.5 client filters out applications that have an OSD file containing an empty OS tag (<OS></OS>).
-
-WORKAROUND Delete the empty OS tag from the OSD file.
-
-### The App-V server requires exemptions in its firewall for certain processes
-
-For the server to stream applications correctly, the server's core processes, including the dispatcher, need access through the firewall.
-
-WORKAROUND Set exemptions in the server's firewall for the following processes: sghwsvr.exe and sghwdsptr.exe. This applies to the App-V Management Server and App-V Streaming Server.
-
-### When the server installer is run in silent mode, it does not correctly check for MSXML6
-
-The App-V Management Server depends on MSXML6. However, if you run the installer in silent mode—for example, by using the command “msiexec -i setup.msi /qn” on a system where MSXML6 is not already installed—the installer does not detect the missing dependency and installs anyway. Therefore, when clients attempt to refresh publishing information from the App-V Management Server, they will see failures.
-
-WORKAROUND Verify that MSXML6 is installed on the system before attempting a silent install of the App-V Management Server.
-
-### Error code 000C800 when attempting to connect to the Application Virtualization Management Console
-
-An Application Virtualization administrator who is not a local administrator on the App-V Management Web Service server will receive an error (Error code: 000C800) when attempting to connect to the App-V Management Console, and the sftmmc.log entry will indicate that access to SftMgmt.udl is denied. To successfully connect to the App-V Management Console, an administrator who does not have local administrator rights on the App-V Management Web Service server must have at least read and execute permissions to the SftMgmt.udl file.
-
-The Application Virtualization administrators must be given read and execute permissions to the SftMgmt.UDL file under %systemdrive%\\Program Files\\Microsoft System Center App Virt Management Server\\App Virt Management Service.
-
-### Client installer command-line parameters are ignored when used in conjunction with KEEPCURRENTSETTINGS=1
-
-When used in conjunction with KEEPCURRENTSETTINGS=1, the following client installer command-line parameters are ignored: SWICACHESIZE, MINFREESPACEMB, ALLOWINDEPENDENTFILESTREAMING, APPLICATIONSOURCEROOT, ICONSOURCEROOT, OSDSOURCEROOT, SYSTEMEVENTLOGLEVEL, SWIGLOBALDATA, DOTIMEOUTMINUTES, SWIFSDRIVE, AUTOLOADTARGET, AUTOLOADTRIGGERS, SWIUSERDATA, and REQUIRESECURECONNECTION.
-
-WORKAROUND If you have settings you want to retain, use KEEPCURRENTSETTINGS=1 and then set the other parameters after deployment. The App-V ADM Template can be used to set the following client settings: APPLICATIONSOURCEROOT, ICONSOURCEROOT, OSDSOURCEROOT, AUTOLOADTARGET, AUTOLOADTRIGGERS, DOTIMEOUTMINUTES, and ALLOWINDEPENDENTFILESTREAMING. The ADM Template can be found at .
-
-## Release Notes Copyright Information
-
-
-Information in this document, including URL and other Internet Web site references, is subject to change without notice and is provided for informational purposes only. The entire risk of the use or results from the use of this document remains with the user, and Microsoft Corporation makes no warranties, either express or implied. Unless otherwise noted, the companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted in examples herein are fictitious. No association with any real company, organization, product, domain name, e-mail address, logo, person, place, or event is intended or should be inferred. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.
-
-Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.
-
-
-
-Microsoft, Active Directory, ActiveSync, MS-DOS, Windows, Windows Server, and Windows Vista are trademarks of the Microsoft group of companies.
-
-All other trademarks are property of their respective owners.
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/microsoft-application-virtualization-management-system-release-notes.md b/mdop/appv-v4/microsoft-application-virtualization-management-system-release-notes.md
deleted file mode 100644
index c97f47acca..0000000000
--- a/mdop/appv-v4/microsoft-application-virtualization-management-system-release-notes.md
+++ /dev/null
@@ -1,287 +0,0 @@
----
-title: Microsoft Application Virtualization Management System Release Notes
-description: Microsoft Application Virtualization Management System Release Notes
-author: dansimp
-ms.assetid: e1a4d5ee-53c7-4b48-814c-a34ce0e698dc
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 08/30/2016
----
-
-
-# Microsoft Application Virtualization Management System Release Notes
-
-
-To search these Release Notes, press CTRL+F.
-
-**Important**
-Read these Release Notes thoroughly before you install the Application Virtualization Management System. These Release Notes contain information that you need to successfully install the Application Virtualization Management System. This document contains information that is not available in the product documentation. If there is a discrepancy between these Release Notes and other Application Virtualization Management System documentation, the latest change should be considered authoritative. These Release Notes supersede the content included with this product.
-
-
-
-For updated information about known issues, please visit the Microsoft TechNet Library at .
-
-## About Microsoft Application Virtualization 4.5 Cumulative Update 1
-
-
-These Release Notes have been updated to reflect the changes introduced with Microsoft Application Virtualization 4.5 Cumulative Update 1 (App-V 4.5 CU1), which provides the latest updates to Application Virtualization (App-V) 4.5. This cumulative update contains the following changes:
-
-- Support for Windows 7 Beta and Windows Server 2008 R2 Beta: App-V 4.5 CU1 addresses compatibility issues with Windows 7 Beta and Windows Server 2008 R2 Beta. Support will be provided for blocking issues that prevent App-V 4.5 CU1 running in a test environment on pre-RTM versions of Windows 7. This will help ensure that your virtual applications can run successfully in a test environment where compatibility between App-V 4.5 Client and Windows 7 Beta is required.
-
- **Important**
- Running App-V 4.5 CU1 on any version of Windows 7 or Windows Server 2008 R2 in a live operating environment is not supported.
-
-
-
-- Improved support for sequencing the .NET Framework: App-V 4.5 CU1 addresses previous issues with sequencing the .NET Framework 3.5 and earlier on Windows XP (SP2 or later). For more information about the new capabilities, see the TechNet article at .
-
-- Customer Feedback and Hotfix Rollup: App-V 4.5 CU1 also includes a rollup up of fixes to address issues found since the App-V 4.5 RTM release. This includes a combination of known issues and customer feedback from our internal teams, partners, and customers who are using App-V 4.5. For a full list of the included updates, see the KB article at .
-
-## About the Product Documentation
-
-
-Comprehensive documentation for Application Virtualization (App-V) is available on Microsoft TechNet in the Application Virtualization (App-V) TechCenter at . The TechNet documentation includes the online Help for the Application Virtualization Sequencer, the Application Virtualization Client, and the Application Virtualization Server. It also includes the Application Virtualization Planning and Deployment Guide and the Application Virtualization Operations Guide.
-
-## Protect Against Security Vulnerabilities and Viruses
-
-
-To help protect against security vulnerabilities and viruses, it is important to install the latest available security updates for any new software being installed. For more information, see the Microsoft Security Web site at .
-
-## Providing Feedback
-
-
-You can provide feedback, make a suggestion, or report an issue with the Microsoft Application Virtualization (App-V) Management System via a community forum on the Microsoft Application Virtualization TechCenter ().
-
-You can also provide your feedback on the documentation directly to the App-V documentation team. Send your documentation feedback to appvdocs@microsoft.com.
-
-## Known Issues with Application Virtualization 4.5 CU1
-
-
-This section provides the most up-to-date information about issues with Microsoft Application Virtualization (App-V) 4.5 CU1. These issues do not appear in the product documentation and in some cases might contradict existing product documentation. Whenever possible, these issues will be addressed in later releases.
-
-### Guidance for installing or upgrading clients to App-V 4.5 CU1 using setup.msi
-
-When installing or upgrading your App-V clients to App-V 4.5 CU1 by using setup.msi, the prerequisites are not installed automatically.
-
-WORKAROUND You must manually install the prerequisites before installing or upgrading the App-V client to 4.5 CU1. For detailed procedures for installing the prerequisites and the App-V client, see .
-
-When this has been completed, install the App-V 4.5 CU1 client by using setup.msi with elevated privileges. This file is available on the App-V 4.5 CU1 release media in the Installers\\Client folder.
-
-When installing Microsoft Application Error Reporting, use the following command if you are installing or upgrading to the App-V 4.5 CU1 Desktop client:
-
- msiexec /i dw20shared.msi APPGUID={FE495DBC-6D42-4698-B61F-86E655E0796D} allusers=1 reboot=suppress REINSTALL=all REINSTALLMODE=vomus
-
-Alternatively, if you are installing or upgrading to the App-V 4.5 CU1 Terminal Services client, use the following command:
-
- msiexec /i dw20shared.msi APPGUID={8A97C241-D92A-47DC-B360-E716C1AAA929} allusers=1 reboot=suppress REINSTALL=all REINSTALLMODE=vomus
-
-**Note**
-The APPGUID parameter references the product code of the App-V client that you install or upgrade to. The product code is unique for each setup.msi. You can use the Orca database editor or similar tool to examine Windows Installer files and determine the product code. This step is required for all installs or upgrades to App-V 4.5 CU1.
-
-
-
-### Some applications might fail to install during the monitoring phase when sequencing on Windows 7 Beta
-
-When sequencing on Windows 7 Beta or on a computer with Windows Installer 5.0, some applications might fail to install during the monitoring phase.
-
-WORKAROUND You must manually grant the Everyone group Full Control permissions to the following registry key:
-
- HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Microsoft\\SoftGrid\\4.5\\SystemGuard
-
-**Important**
-You must use the **Advanced** button to set the “Include inheritable permissions from this object’s parent” option.
-
-
-
-### Unable to save packages when sequencing on Windows 7 Beta
-
-When sequencing on Windows 7 Beta, you might be unable to save your sequenced package because of a sharing violation.
-
-WORKAROUND As specified in the best practices section of the Microsoft Application Virtualization 4.5 Sequencing Guide (see ), you must shutdown and disable the following software programs before you begin sequencing:
-
-- Windows Defender
-
-- Antivirus software
-
-- Disk defragmentation software
-
-- Windows Search
-
-- Any open Windows Explorer session
-
-In addition, if you have Microsoft Update running on the sequencing station to capture updates during the package update process, you will need to add “C:\\Windows\\SoftwareDistribution” as a VFS exclusion before you start sequencing.
-
-### Improving performance when sequencing the .NET Framework
-
-When sequencing the .NET Framework, you might experience reduced system performance because the Microsoft .NET Framework NGEN service attempts to precompile assemblies as a background task.
-
-WORKAROUND When sequencing the .NET Framework, disable the Microsoft .NET Framework NGEN service (mscorsvw.exe) after completing the monitoring phase. You must use the **Virtual Services** tab in the Sequencer and change the startup type to disabled.
-
-### Interoperability issues with the Windows 7 Taskbar
-
-When you run the Application Virtualization Client on Windows 7, the Windows 7 taskbar does not collapse multiple instances of a virtual application into a single taskbar button. In addition, jump Lists do not appear when you right-click a taskbar button of a virtual application, unless the application has been pinned to the Windows 7 taskbar.
-
-### When you uninstall the Microsoft Application Virtualization Client, user settings associated with the user performing the uninstall will be deleted
-
-When you uninstall the Microsoft Application Virtualization Client, the Windows Installer will remove Application Virtualization settings from the current user's profile. If your computer uses roaming profiles, do not use your personal network account to uninstall the client because it will remove settings for your virtual applications on all of your computers.
-
-WORKAROUND You should perform the App-V Client uninstall with an administrative account that is not used for running virtual applications.
-
-### Edits made on the virtual file system and virtual registry tabs must be saved while running the Sequencing wizard
-
-If you open a package to perform an upgrade or have already run the Sequencing wizard with a new package and you make changes to the package in the virtual file system or virtual registry tabs, those changes are not automatically saved.
-
-WORKAROUND Save the changes before re-running the wizard, to ensure that they are reflected inside the wizard’s virtual environment.
-
-### Command-line Sequencer must be run from an elevated command prompt
-
-When you use the command-line Sequencer, it does not prompt for elevation.
-
-WORKAROUND Run the command-line Sequencer using an elevated command prompt.
-
-### Server Management Console configuration in distributed environments
-
-If you need to install management components onto systems other than the primary Application Virtualization publishing and streaming server, the server install supports installing our management console and Web service on separate servers from the primary Application Virtualization Server when properly configured.
-
-To distribute the management components across multiple servers, Kerberos delegation must be enabled on the server where the Web service is installed.
-
-### Short path variable names in OSD files can cause errors
-
-If you receive error 450478-1F702339-0000010B “The directory name is invalid” when starting a virtual application on the client, it is possible that the variable in the OSD is set incorrectly. This can happen if the application’s installer sets a short path name during sequencing.
-
-WORKAROUND Remove the trailing tilde from any CSIDL variable that exists in the OSD file.
-
-### Correct syntax for DECODEPATH parameter for command-line Sequencer
-
-In the command-line Sequencer, when opening a package for upgrade and decoding it to the root of the Q drive, the syntax for the *DECODEPATH* parameter should not include a trailing slash.
-
-WORKAROUND You can use **Q:** rather than **Q:\\** (omitting the trailing “\\” character).
-
-### When upgrading 4.2 packages, you encounter problems caused by Windows Installer files in the Virtual File System
-
-When upgrading a package from 4.2, you might experience issues relating to a mismatch of Windows Installer system files that were included by default in 4.2 and the Windows Installer libraries locally installed on your Sequencing workstation. The following files are located in CSIDL\_SYSTEM\\:
-
-cabinet.dll
-
-msi.dll
-
-msiexec.exe
-
-msihnd.dll
-
-msimsg.dlll
-
-WORKAROUND Delete all of the preceding files from the package. Delete the mappings on the **VFS** tab as well as the actual files in the CSIDL\_SYSTEM folder in your decode path.
-
-### On Windows XP, client install logging is not enabled by default
-
-When installing the client, to ensure that any install errors are captured for troubleshooting purposes, you should enable logging by using the command line.
-
-WORKAROUND Add the parameter */l\*vx! log.txt* to the command line, as shown in the following example:
-
-setup.exe /s /v”/qn /l\*vx! log.txt”
-
-msiexec.exe /i setup.msi /qn /l\*vx! log.txt
-
-Alternatively, you can set the registry key to the following value:
-
-\[HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Policies\\Microsoft\\Windows\\Installer\] "Logging"="voicewarmupx!"
-
-### For Kerberos authentication to work, Service Principal Names (SPNs) must be registered for IIS
-
-When using IIS 6.0 or 7.0 for icon or OSD file retrieval and streaming of packages, for Kerberos authentication to be enabled, the SPNs must be registered as follows:
-
-- On the IIS server, run the following commands by using the SETSPN.EXE Resource Kit tool. The server fully qualified domain name (FQDN) must be used.
-
- Setspn -r SOFTGRID/<Server FQDN>
-
- Setspn -r HTTP/<Server FQDN>
-
-For more information, see .
-
-### On upgrade from RC, the default permissions on client logs do not allow for non-admin users to access the logs for troubleshooting and support
-
-The default permissions on client logs for the Application Virtualization RC client did not allow for non-admin access to log files, and manual changes to these log permissions were reverted when clients were restarted. This has been corrected in the RTM release for new client installs, but on upgrade from RC, the custom permissions on existing log files are not reset. However, when any new logs are created or after a log reset, the files will have the new default permissions.
-
-WORKAROUND After the upgrade, reset existing client logs or manually change their permissions.
-
-### .NET compatibility changes
-
-Microsoft Application Virtualization Cumulative Update 1 supports sequencing the .NET Framework on Windows XP (SP2 or later). Sequencing routines for .NET applications that were written for SoftGrid 4.2 might need to be updated when used with the App-V 4.5 Sequencer. For details and workarounds, please refer to the Knowledge Base article at .
-
-### After client upgrade from App-V 4.2, some applications are not shown
-
-Check for the following error in the log: ”The Application Virtualization Client could not parse the OSD file”. The Microsoft Application Virtualization 4.5 client filters out applications that have an OSD file containing an empty OS tag (<OS></OS>).
-
-WORKAROUND Delete the empty OS tag from the OSD file.
-
-### The App-V server requires exemptions in its firewall for certain processes
-
-For the server to stream applications correctly, the server's core processes, including the dispatcher, need access through the firewall.
-
-WORKAROUND Set exemptions in the server's firewall for the following processes: sghwsvr.exe and sghwdsptr.exe. This applies to the App-V Management Server and App-V Streaming Server.
-
-### Sequencing packages that require new Visual Basic runtimes might fail
-
-If you sequence a package that uses a newer version of a Visual Basic (VB) runtime on a system where an older version of the VB runtime is installed, you might see a crash or other unexpected behavior when you try to use your package. For example, if you try to sequence Microsoft Money 2007, which uses version 6.00.9782 of the VB runtime, on a Windows XP system with version 6.00.9690 of the VB runtime, you might see a crash in the Invoice Designer when you try to run it on another Windows XP system with that older VB runtime.
-
-WORKAROUND After installing the application on the sequencing computer, while still monitoring, copy the correct (newer) VB runtime to the directory in the package from where the executable is started. This allows the sequenced application to find the expected version of the VB runtime when it is started.
-
-**Important**
-This issue has been fixed in Microsoft Application Virtualization 4.5 Cumulative Update 1.
-
-
-
-### When the server installer is run in silent mode, it does not correctly check for MSXML6
-
-The App-V Management Server depends on MSXML6. However, if you run the installer in silent mode—for example, by using the command “msiexec -i setup.msi /qn” on a system where MSXML6 is not already installed—the installer does not notice the missing dependency and installs anyway. The most common result is that when clients attempt to refresh publishing information from the App-V Management Server, they will see failures.
-
-WORKAROUND Verify that MSXML6 is installed on the system before attempting a silent install of the App-V Management Server.
-
-### Error code 000C800 when attempting to connect to the Application Virtualization Management Console
-
-An Application Virtualization administrator who is not a local admin on the Application Virtualization Management Service server will receive an error (Error code: 000C800) when attempting to connect to the Application Virtualization Management Console, and the sftmmc.log entry will indicate that access to SftMgmt.udl is denied. To successfully connect to the Application Virtualization Management Console, an Application Virtualization administrator who is not a local admin on the Application Virtualization Management Service server must have at least read and execute access to the SftMgmt.udl file.
-
-The Application Virtualization administrators must be given read and execute permissions to the SftMgmt.UDL file under %systemdrive%\\Program Files\\Microsoft System Center App Virt Management Server\\App Virt Management Service.
-
-### Client installer command-line parameters are ignored when used in conjunction with KEEPCURRENTSETTINGS=1
-
-When used in conjunction with KEEPCURRENTSETTINGS=1, the following client installer command-line parameters are ignored: SWICACHESIZE, MINFREESPACEMB, ALLOWINDEPENDENTFILESTREAMING, APPLICATIONSOURCEROOT, ICONSOURCEROOT, OSDSOURCEROOT, SYSTEMEVENTLOGLEVEL, SWIGLOBALDATA, DOTIMEOUTMINUTES, SWIFSDRIVE, AUTOLOADTARGET, AUTOLOADTRIGGERS, SWIUSERDATA, and REQUIRESECURECONNECTION.
-
-WORKAROUND If you have settings you want to retain, use KEEPCURRENTSETTINGS=1 and then set the other parameters after deployment. The App-V ADM Template can be used to set the following client settings: APPLICATIONSOURCEROOT, ICONSOURCEROOT, OSDSOURCEROOT, AUTOLOADTARGET, AUTOLOADTRIGGERS, DOTIMEOUTMINUTES, and ALLOWINDEPENDENTFILESTREAMING. The ADM Template can be found at .
-
-### Error initializing virtual applications with Symantec Endpoint Protection
-
-When using Symantec Endpoint Protection with the Application and Device Control feature enabled, virtual applications might fail to start, with the error “The application failed to initialize properly (0xc000007b)”. For details and workarounds, please refer to the Knowledge Base article at .
-
-**Important**
-This issue has been fixed in Microsoft Application Virtualization 4.5 Cumulative Update 1.
-
-
-
-## Release Notes Copyright Information
-
-
-Information in this document, including URL and other Internet Web site references, is subject to change without notice, and is provided for informational purposes only. The entire risk of the use or results of the use of this document remains with the user, and Microsoft Corporation makes no warranties, either express or implied. The example companies, organizations, products, people and events depicted herein are fictitious. No association with any real company, organization, product, person or event is intended or should be inferred. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.
-
-Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.
-
-
-
-Microsoft, MS-DOS, Windows, Windows Server, Windows Vista, Active Directory, and ActiveSync are either registered trademarks or trademarks of Microsoft Corporation in the U.S.A. and/or other countries.
-
-The names of actual companies and products mentioned herein may be the trademarks of their respective owners.
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/microsoft-application-virtualization-security-guide.md b/mdop/appv-v4/microsoft-application-virtualization-security-guide.md
deleted file mode 100644
index 8b8cf618b5..0000000000
--- a/mdop/appv-v4/microsoft-application-virtualization-security-guide.md
+++ /dev/null
@@ -1,29 +0,0 @@
----
-title: Microsoft Application Virtualization Security Guide
-description: Microsoft Application Virtualization Security Guide
-author: dansimp
-ms.assetid: 5e794316-cc4f-459e-90ef-79fc9841ba4e
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Microsoft Application Virtualization Security Guide
-
-
-This documentation introduces you to important information about deployment decisions that can affect the security of your system. It also provides you with the necessary steps to configure the Microsoft Application Virtualization (App-V) security settings to enhance the security of your environment based on the recommendations presented in the Security Best Practices Whitepaper. If the security settings are specific to Windows but not to App-V, the documentation includes the appropriate links to that information.
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/monitoring-application-virtualization-servers.md b/mdop/appv-v4/monitoring-application-virtualization-servers.md
deleted file mode 100644
index c778742dcd..0000000000
--- a/mdop/appv-v4/monitoring-application-virtualization-servers.md
+++ /dev/null
@@ -1,73 +0,0 @@
----
-title: Monitoring Application Virtualization Servers
-description: Monitoring Application Virtualization Servers
-author: dansimp
-ms.assetid: d84355ae-4fe4-41d9-ac3a-3eaa32d9a61f
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Monitoring Application Virtualization Servers
-
-
-To simplify Application Virtualization (App-V) Server management, you can use the System Center Operations Manager 2007 Management Pack. This Management Pack supports only Application Virtualization (App-V) 4.5 servers; it does not support previous server versions. The Management Pack maximizes App-V Server availability for handling App-V Client requests.
-
-## Status Indicators
-
-
-The App-V Server health status indicators are color-coded. The colors represent the following status values:
-
-- No color indicates that the server is running without non-recoverable errors.
-
-- Yellow indicates that one of the components is not functioning correctly. The overall functionality of the server is degraded, but the server is still available.
-
-- Red indicates that the server is not available and that it cannot provide key services or communicate with external service dependencies.
-
-## Monitoring Criteria
-
-
-The Management Pack monitors the following aspects of server health:
-
-- Server Status—monitors server events to validate that the server is providing its expected services.
-
-- Data Store Access—tracks the ability of one or more of the App-V Management Servers to access and communicate with the App-V data store.
-
-- Content Data Access—monitors access to the \\Content directory, which might be a local directory or a network share, and the ability to read the requested files.
-
-- Security—reports errors with the App-V Server’s certificate and secure communications.
-
-- Client Request Handling—monitors the ability of one or more of the App-V Servers to handle and correctly respond to client requests. These requests include publishing such items as configuration requests, package load requests, and out of sequence requests.
-
-- Server Configuration—checks the configuration settings of the App-V Server. These configuration settings include the settings in the registry and in the App-V data store.
-
-## Server Differences
-
-
-The main differences between the App-V Management Server and the App-V Streaming Server are as follows:
-
-- App-V Management Servers can provide publishing, streaming, management, and reporting services. Therefore, the Management Pack can manage more aspects of the App-V Management Server than it can manage on the App-V Streaming Server, which provides only package streaming.
-
-- The App-V Streaming Server does not have an App-V data store, so data store access is not monitored. The configuration information for the App-V Streaming Server is managed in the registry.
-
-- The App-V Streaming Server does not use the App-V Server Management Console interface; use other tools to manage the configuration.
-
-## Related topics
-
-
-[Application Virtualization Server](application-virtualization-server.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/online-help-for-application-virtualization.md b/mdop/appv-v4/online-help-for-application-virtualization.md
deleted file mode 100644
index 91d7d2784f..0000000000
--- a/mdop/appv-v4/online-help-for-application-virtualization.md
+++ /dev/null
@@ -1,41 +0,0 @@
----
-title: Online Help for Application Virtualization
-description: Online Help for Application Virtualization
-author: dansimp
-ms.assetid: 261ede48-976f-473c-84bc-452577efdcdf
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Online Help for Application Virtualization
-
-
-The Microsoft Application Virtualization (App-V) system provides the capability to make applications available to end user computers without having to install the applications directly on those computers. The following online help documentation provides step-by-step procedures for interacting with and using the key system components.
-
-## In This Section
-
-
-[Microsoft Application Virtualization Client Management Help](microsoft-application-virtualization-client-management-help.md)
-Includes conceptual information, step-by-step procedures, and a user interface reference for the Application Virtualization (App-V) Desktop Client and Terminal Services Client.
-
-[Application Virtualization Server Management Help](application-virtualization-server-management-help.md)
-Provides overview information about the Application Virtualization (App-V) Servers, as well as step-by-step procedures for using the available features and commands. A reference section includes information about the windows and dialogs that are available in the Server Management Console.
-
-[Application Virtualization Sequencer Online Help](application-virtualization-sequencer-online-help.md)
-Includes information about the user interface and the Sequencing Wizard and provides detailed step-by-step procedures for sequencing applications.
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/open-package-wizard---appv-46-sp1-.md b/mdop/appv-v4/open-package-wizard---appv-46-sp1-.md
deleted file mode 100644
index 0bf23f9812..0000000000
--- a/mdop/appv-v4/open-package-wizard---appv-46-sp1-.md
+++ /dev/null
@@ -1,42 +0,0 @@
----
-title: Open Package Wizard (AppV 4.6 SP1)
-description: Open Package Wizard (AppV 4.6 SP1)
-author: dansimp
-ms.assetid: 26bdef59-2ea3-4e30-9095-0ee0d0085b2d
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Open Package Wizard (AppV 4.6 SP1)
-
-
-Use any of the following links for more information about the App-V Open Package wizard.
-
-## In This Section
-
-
-[Select Task Page (Learn More)](select-task-page--learn-more-.md)
-Describes the options on the **Select Task** page to modify an existing virtual application package.
-
-[Packaging Method (Learn More)](packaging-method--learn-more-.md)
-
-## Related topics
-
-
-[Wizard Pages (AppV 4.6 SP1)](wizard-pages--appv-46-sp1-.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/operations-guide-for-the-application-virtualization-system.md b/mdop/appv-v4/operations-guide-for-the-application-virtualization-system.md
deleted file mode 100644
index fa836b09a6..0000000000
--- a/mdop/appv-v4/operations-guide-for-the-application-virtualization-system.md
+++ /dev/null
@@ -1,50 +0,0 @@
----
-title: Operations Guide for the Application Virtualization System
-description: Operations Guide for the Application Virtualization System
-author: dansimp
-ms.assetid: 686f2b75-7fba-4410-89b2-a539984b6ef2
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 08/30/2016
----
-
-
-# Operations Guide for the Application Virtualization System
-
-
-The Microsoft Application Virtualization Operations Guide provides information and step-by-step procedures to help you administer the Microsoft Application Virtualization (App-V) system and its components. This information will be valuable for system administrators who manage large installations with many servers and clients and for support personnel who interact directly with the computers or the end users.
-
-## In This Section
-
-
-[Application Virtualization Client](application-virtualization-client.md)
-Provides information about operational tasks for administering the Application Virtualization (App-V) Client.
-
-[Application Virtualization Server](application-virtualization-server.md)
-Provides information about operational tasks for administering the Application Virtualization (App-V) Servers.
-
-[Application Virtualization Sequencer](application-virtualization-sequencer.md)
-Provides information about operational tasks for using the Application Virtualization (App-V) Sequencer.
-
-## Reference
-
-
-For more information about general App-V sequencing best practices, see the following Microsoft Web sites:
-
-MCS Sequencing Guidelines at
-
-Best Practices for Sequencing at
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/osd-file-elements.md b/mdop/appv-v4/osd-file-elements.md
deleted file mode 100644
index 96422a7568..0000000000
--- a/mdop/appv-v4/osd-file-elements.md
+++ /dev/null
@@ -1,81 +0,0 @@
----
-title: OSD File Elements
-description: OSD File Elements
-author: dansimp
-ms.assetid: 8211b562-7549-4331-8321-144f52574e99
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# OSD File Elements
-
-
-The Sequencer installation directory contains an XML schema file, **Softricity.xsd**, which defines the valid structure of an Open Software Descriptor (OSD) file. Following are some of the more frequently used OSD elements.
-
-SOFTPKG
-The root element of the OSD file containing all elements defining the software package.
-
-CODEBASE
-Information about the .sft file for this package, including the HREF, FILENAME, and GUID attributes. You can edit the HREF attribute if you change the distribution point of this particular package.
-
-OS
-Defines on what operating systems this application can run based on values that are initially set in the Sequencing Wizard. This value can contain only the values defined in **Softricity.xsd**.
-
-LOCAL\_INTERACTION\_ALLOWED
-Set to TRUE, this enables creation of named objects (events, mutexes, semaphores, file mappings, and mailslots) and COM objects in the global namespace rather than isolated inside a particular virtual environment, which allows virtual applications to interact with the host operating system's applications.
-
-Example:<SOFTPKG><IMPLEMENTATION>
-
-<VIRTUALENV><POLICIES>
-
-<LOCAL\_INTERACTION\_ALLOWED>TRUE
-
-</LOCAL\_INTERACTION\_ALLOWED>
-
-</POLICIES></VIRTUALENV>
-
-</IMPLEMENTATION></SOFTPKG>
-
-DEPENDENCIES
-Defines Dynamic Suite Composition (dependencies on other packages) by using a CODEBASE tag from another package.
-
-Example:<DEPENDENCIES><CODEBASE HREF="rtsps://server/package.sft" GUID="7579F4DF-2461-4219-BD43-494E1FDC69E3" SYSGUARDFILE="pkg.1\\osguard.cp" SIZE="6572748" MANDATORY="FALSE"/></DEPENDENCIES>
-
-PACKAGE NAME
-A common name for the package entered into the Sequencing Wizard **Package Information** page, which enables you to specify a single name used for a sequenced application containing multiple applications.
-
-TITLE
-Optional descriptive name of the application you are sequencing.
-
-ABSTRACT
-Short description of the software package entered in the **Comments** field in the Sequencing Wizard **Package Information** page. A best practice is to specify information such as the operating system and service-pack level of the Sequencer workstation, Sequencer version, and the sequencing engineer’s name.
-
-SCRIPT
-Defines specific scripted events to occur during startup, shutdown, or streaming.
-
-MGMT\_SHORTCUTLIST
-List of all shortcuts defined in the wizard.
-
-MGMT\_FILEASSOCIATIONS
-List of the file types specified in the wizard.
-
-## Related topics
-
-
-[About the OSD Tab](about-the-osd-tab.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/osd-tab-keep.md b/mdop/appv-v4/osd-tab-keep.md
deleted file mode 100644
index dd06e42a12..0000000000
--- a/mdop/appv-v4/osd-tab-keep.md
+++ /dev/null
@@ -1,46 +0,0 @@
----
-title: OSD Tab
-description: OSD Tab
-author: dansimp
-ms.assetid: e66f1384-1753-4216-b9ee-77e99af93c74
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# OSD Tab
-
-
-Use the **OSD** tab to edit and customize the Open Software Descriptor (OSD) file.
-
-## In This Section
-
-
-[About the OSD Tab](about-the-osd-tab.md)
-Provides general information about the **OSD** tab.
-
-[How to Edit an OSD File](how-to-edit-an-osd-file.md)
-Provides the procedure to edit the OSD file by using the **Virtual Services** tab.
-
-[How to Edit an OSD File Using a Text Editor](how-to-edit-an-osd-file-using-a-text-editor.md)
-Provides the procedure to customize an OSD file by using a text editor.
-
-## Related topics
-
-
-[Sequencer Console](sequencer-console.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/oversized-package-dialog-box--app-v-46-sp1-.md b/mdop/appv-v4/oversized-package-dialog-box--app-v-46-sp1-.md
deleted file mode 100644
index 6a802d1959..0000000000
--- a/mdop/appv-v4/oversized-package-dialog-box--app-v-46-sp1-.md
+++ /dev/null
@@ -1,42 +0,0 @@
----
-title: Oversized Package Dialog Box (App-V 4.6 SP1)
-description: Oversized Package Dialog Box (App-V 4.6 SP1)
-author: dansimp
-ms.assetid: 8973a493-6509-4d52-afb6-a9f47d1c5c26
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Oversized Package Dialog Box (App-V 4.6 SP1)
-
-
-The uncompressed package size exceeds the recommended 4 GB package size limit. To reduce the size of the package, package compression has been enabled.
-
-In the **Oversized Package** dialog box, use the following procedure to configure package compression.
-
-1. In the App-V Sequencer console, click the **Deployment** tab.
-
-2. To enable package compression, select the **Compress Package** check box. To disable package compression, clear the **Compress Package** check box.
-
-3. To save the package, click **File** / **Save**.
-
-## Related topics
-
-
-[Dialog Boxes (AppV 4.6 SP1)](dialog-boxes--appv-46-sp1-.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/overview-of-application-virtualization.md b/mdop/appv-v4/overview-of-application-virtualization.md
deleted file mode 100644
index 356e53e996..0000000000
--- a/mdop/appv-v4/overview-of-application-virtualization.md
+++ /dev/null
@@ -1,97 +0,0 @@
----
-title: Overview of Application Virtualization
-description: Overview of Application Virtualization
-author: dansimp
-ms.assetid: 80545ef4-cf4c-420c-88d6-48e9f226051f
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Overview of Application Virtualization
-
-
-Microsoft Application Virtualization (App-V) can make applications available to end user computers without having to install the applications directly on those computers. This is made possible through a process known as *sequencing the application*, which enables each application to run in its own self-contained virtual environment on the client computer. The sequenced applications are isolated from each other. This eliminates application conflicts, but the applications can still interact with the client computer.
-
-The App-V client is the feature that lets the end user interact with the applications after they have been published to the computer. The client manages the virtual environment in which the virtualized applications run on each computer. After the client has been installed on a computer, the applications must be made available to the computer through a process known as *publishing*, which enables the end user to run the virtual applications. The publishing process copies the virtual application icons and shortcuts to the computer—typically on the Windows desktop or on the **Start** menu—and also copies the package definition and file type association information to the computer. Publishing also makes the application package content available to the end user’s computer.
-
-The virtual application package content can be copied onto one or more Application Virtualization servers so that it can be streamed down to the clients on demand and cached locally. File servers and Web servers can also be used as streaming servers, or the content can be copied directly to the end user’s computer—for example, if you are using an electronic software distribution system, such as Microsoft Endpoint Configuration Manager. In a multi-server implementation, maintaining the package content and keeping it up to date on all the streaming servers requires a comprehensive package management solution. Depending on the size of your organization, you might need to have many virtual applications available to end users located all over the world. Managing the packages to ensure that the appropriate applications are available to all users where and when they need access to them is therefore an important requirement.
-
-## Microsoft Application Virtualization System Features
-
-
-The following table describes the primary features of the Microsoft Application Virtualization Management System.
-
-
-
-
-
-
-
-
-
-
Feature
-
Function
-
Additional Information
-
-
-
-
-
Microsoft Application Virtualization Management Server
-
Responsible for streaming the package content and publishing the shortcuts and file type associations to the Application Virtualization client.
-
The Application Virtualization Management Server supports active upgrade, License Management, and a database that can be used for reporting.
-
-
-
Content folder
-
Indicates the location of the Application Virtualization packages for streaming.
-
This folder can be located on a share on or off the Application Virtualization Management Server.
-
-
-
Microsoft Application Virtualization Management Console
-
This console is an MMC 3.0 snap-in management tool used for Microsoft Application Virtualization Server administration.
-
This tool can be installed on the Microsoft Application Virtualization server or located on a separate workstation that has Microsoft Management Console (MMC) 3.0 and Microsoft .NET Framework 2.0 installed.
-
-
-
Microsoft Application Virtualization Management Web Service
-
Responsible for communicating any read and write requests to the Application Virtualization data store.
-
The Management Web Service can be installed on the Microsoft Application Virtualization Management server or on a separate computer that has Microsoft Internet Information Services (IIS) installed.
-
-
-
Microsoft Application Virtualization Data Store
-
The App-V SQL Server database responsible for storing all information related to the Application Virtualization infrastructure.
-
This information includes all application records, application assignments, and which groups have responsibility for managing the Application Virtualization environment.
-
-
-
Microsoft Application Virtualization Streaming Server
-
Responsible for hosting the Application Virtualization packages for streaming to clients in a branch office, where the link back to the Application Virtualization Management Server is considered a wide area networks (WAN) connection.
-
This server contains streaming functionality only and provides neither the Application Virtualization Management Console nor the Application Virtualization Management Web Service.
-
-
-
Microsoft Application Virtualization Sequencer
-
The sequencer is used to monitor and capture the installation of applications to create virtual application packages.
-
The output consists of the application’s icons, an .osd file that contains package definition information, a package manifest file, and the .sft file that contains the application program’s content files.
-
-
-
Microsoft Application Virtualization Client
-
The Application Virtualization Desktop Client and the Application Virtualization Client for Remote Desktop Services provide and manage the virtual environment for the virtualized applications.
-
The Microsoft Application Virtualization client manages the package streaming into cache, publishing refresh, transport, and all interaction with the Application Virtualization servers.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/overview-of-the-application-virtualization-system-components.md b/mdop/appv-v4/overview-of-the-application-virtualization-system-components.md
deleted file mode 100644
index d0436a2494..0000000000
--- a/mdop/appv-v4/overview-of-the-application-virtualization-system-components.md
+++ /dev/null
@@ -1,97 +0,0 @@
----
-title: Overview of the Application Virtualization System Components
-description: Overview of the Application Virtualization System Components
-author: dansimp
-ms.assetid: 75d88ef7-44d8-4fa7-b7f5-9153f37e570d
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Overview of the Application Virtualization System Components
-
-
-The following table describes the primary components of the Microsoft Application Virtualization Management System. For more information about deploying these system components, see [Application Virtualization Server-Based Scenario](application-virtualization-server-based-scenario.md).
-
-
-
-
-
-
-
-
-
-
Component
-
Function
-
Additional Information
-
-
-
-
-
Microsoft Application Virtualization Management Server
-
The component responsible for streaming the package content and publishing the shortcuts and file type associations to the Application Virtualization Client.
-
The Application Virtualization Management Server supports active upgrade, License Management, and a database that can be used for reporting.
-
-
-
Content folder
-
The location of the Application Virtualization packages for streaming.
-
This folder can be located on a share on or off the Application Virtualization Management Server. The folder can also be located on a Storage Area Network (SAN).
-
-
-
Microsoft Application Virtualization Management Console
-
An MMC 3.0 snap-in management utility for Microsoft Application Virtualization Server administration.
-
This component can be installed on the Microsoft Application Virtualization server or located on a separate workstation that has MMC 3.0 and .NET 2.0 installed.
-
-
-
Microsoft Application Virtualization Management Web Service
-
The component responsible for communicating any read/write requests to the Application Virtualization data store.
-
This component can installed on the Microsoft Application Virtualization Server or on a separate computer with IIS installed.
-
-
-
Microsoft Application Virtualization Data Store
-
The component stored in the SQL database and responsible for storing all information related to the Application Virtualization infrastructure.
-
This information includes all application records, application assignments, and which groups have responsibility for managing the Application Virtualization environment.
-
-
-
Microsoft Application Virtualization Streaming Server
-
The component responsible for hosting the Application Virtualization packages for streaming to clients in a branch office, where the link back to the Application Virtualization Management Server is considered a WAN.
-
This server contains streaming functionality only and provides neither the Application Virtualization Management Console nor the Application Virtualization Management Web Service.
-
-
-
Microsoft Application Virtualization Sequencer
-
The component used to monitor and capture the installation of applications to create virtual application packages.
-
Output consists of the application’s icons, an OSD file containing package definition information, a package manifest file, and the SFT file containing the application program’s content files.
-
-
-
Microsoft Application Virtualization Client
-
The component installed on the Application Virtualization Desktop Client or on the Application Virtualization Client for Remote Desktop Services (formerly Terminal Services) and that provides the virtual environment for the virtualized applications.
-
The Microsoft Application Virtualization Client manages the package streaming into cache, publishing refresh, transport, and all interaction with the Application Virtualization Servers.
-
-
-
-
-
-
-## Related topics
-
-
-[Application Virtualization Server-Based Scenario](application-virtualization-server-based-scenario.md)
-
-[Planning Your Streaming Solution in an Application Virtualization Server-Based Implementation](planning-your-streaming-solution-in-an-application-virtualization-server-based-implementation.md)
-
-[Publishing Virtual Applications Using Application Virtualization Management Servers](publishing-virtual-applications-using-application-virtualization-management-servers.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/package-name-page---learn-more-.md b/mdop/appv-v4/package-name-page---learn-more-.md
deleted file mode 100644
index 5a371c35ca..0000000000
--- a/mdop/appv-v4/package-name-page---learn-more-.md
+++ /dev/null
@@ -1,47 +0,0 @@
----
-title: Package Name Page (Learn More)
-description: Package Name Page (Learn More)
-author: dansimp
-ms.assetid: ee75b8f0-bd9d-4460-a256-016ff97c2386
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Package Name Page (Learn More)
-
-
-Use the **Package Name** page to specify a name for the virtual application package. You can also configure where the package will reside on the target computers.
-
-**Note**
-Editing the primary virtual application directory is an advanced task.
-
-
-
-This page contains the following elements:
-
-**Virtual Application Package Name**
-Specifies the name that will be associated with virtual application package. The name specified should help identify the purpose and version of the application. The package name is also displayed in the App-V management console.
-
-**Edit (Advanced)**
-Select this option to change the location of where the virtual application will be installed on target computers. Editing the Application Virtualization path is an advanced configuration task. You should fully understand the implications of changing the path. For most applications, we recommend the default path. Only select this option, if you prefer to generate your own file name.
-
-## Related topics
-
-
-[Create New Package Wizard (AppV 4.6 SP1)](create-new-package-wizard---appv-46-sp1-.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/package-name-page--app-v-46-sp1.md b/mdop/appv-v4/package-name-page--app-v-46-sp1.md
deleted file mode 100644
index 18593c1fbe..0000000000
--- a/mdop/appv-v4/package-name-page--app-v-46-sp1.md
+++ /dev/null
@@ -1,39 +0,0 @@
----
-title: Package Name Page
-description: Package Name Page
-author: dansimp
-ms.assetid: 1cea36b7-737d-4c5e-9294-5feba02a3e7d
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Package Name Page
-
-
-Use the **Package Name** page to specify a name to associate with the new virtual application package.
-
-This page contains the following elements:
-
-**Virtual Application Package Name**
-Specify a name that describes the new virtual application package. The name also identifies the virtual application package in the App-V Management Console.
-
-## Related topics
-
-
-[Sequencer Wizard - Package Accelerator (AppV 4.6 SP1)](sequencer-wizard---package-accelerator--appv-46-sp1-.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/package-results-pane-columns.md b/mdop/appv-v4/package-results-pane-columns.md
deleted file mode 100644
index 65f4510c3f..0000000000
--- a/mdop/appv-v4/package-results-pane-columns.md
+++ /dev/null
@@ -1,77 +0,0 @@
----
-title: Package Results Pane Columns
-description: Package Results Pane Columns
-author: dansimp
-ms.assetid: 4ed3a06a-656d-497a-b62d-21684396e2b0
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Package Results Pane Columns
-
-
-The **Packages Results** pane in the Application Virtualization Server Management Console displays a variety of columns.
-
-You can use the standard Windows **Add/Remove Columns** dialog box to select which columns are displayed in the **Results** pane.
-
-To see the **Add/Remove Columns** dialog box, right-click a package in the **Results** pane and select **View > Add/Remove Columns** from the pop-up menu.
-
-The following table displays the column name and its contents.
-
-
-
-
-
-
-
-
-
Column
-
Contents
-
-
-
-
-
Number
-
Displays the package icon and the version number.
-
-
-
Package File
-
Displays the name of the application file (SFT).
-
-
-
Date Added
-
Displays the date and time the package was added to the server.
-
-
-
Version GUID
-
Displays the version GUID.
-
-
-
-
-
-
-## Related topics
-
-
-[About Application Virtualization Packages](about-application-virtualization-packages.md)
-
-[How to Manage Packages in the Server Management Console](how-to-manage-packages-in-the-server-management-console.md)
-
-[Server Management Console: Packages Node](server-management-console-packages-node.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/package-results-pane.md b/mdop/appv-v4/package-results-pane.md
deleted file mode 100644
index ed92ee0b14..0000000000
--- a/mdop/appv-v4/package-results-pane.md
+++ /dev/null
@@ -1,81 +0,0 @@
----
-title: Package Results Pane
-description: Package Results Pane
-author: dansimp
-ms.assetid: 07b7f737-f26f-4feb-88aa-3d8009c5622d
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Package Results Pane
-
-
-The **Packages Results** pane in the Application Virtualization Server Management Console displays a list of the available packages.
-
-Right-click any package in the **Results** pane to display a pop-up menu that contains the following elements.
-
-**Add Version**
-Starts the Add Package Version wizard. On the **Add Package Version** page, in **Full path for package file**, you can enter or browse to the correct path. On the **Enter Relative path for package file** page, you can enter the relative path in the **Relative path for package file** field.
-
-**New Window from Here**
-Opens a new management console with the selected node as the root node.
-
-**Delete**
-Deletes a package from the **Results** pane.
-
-**Rename**
-Changes the name of a package in the **Results** pane.
-
-**Refresh**
-Refreshes the view of the server.
-
-**Properties**
-Displays the **Properties** dialog box for the selected package. The **Properties** dialog box displays the GUID information, the package name, and a list of applications (including version number and enabled status) associated with the package.
-
-**Help**
-Displays the help system for the Application Virtualization Server Management Console.
-
-Right-click anywhere in the **Results** pane to display a pop-up menu that contains the following elements.
-
-**Refresh**
-Refreshes the **Results** pane.
-
-**Export List**
-Creates a tab-delimited text file that contains the contents of the **Results** pane. This item displays a standard **File Save** dialog box where you specify the location for the text file you are creating.
-
-**View**
-Changes the appearance and content of the **Results** pane.
-
-**Arrange Icons**
-Changes how the icons are displayed in the **Results** pane.
-
-**Line Up Icons**
-Changes how the icons are displayed in the **Results** pane.
-
-**Help**
-Displays the help system for the Application Virtualization Server Management Console.
-
-## Related topics
-
-
-[About Application Virtualization Packages](about-application-virtualization-packages.md)
-
-[How to Manage Packages in the Server Management Console](how-to-manage-packages-in-the-server-management-console.md)
-
-[Server Management Console: Packages Node](server-management-console-packages-node.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/packages-node.md b/mdop/appv-v4/packages-node.md
deleted file mode 100644
index b293c3d8b7..0000000000
--- a/mdop/appv-v4/packages-node.md
+++ /dev/null
@@ -1,91 +0,0 @@
----
-title: Packages Node
-description: Packages Node
-author: dansimp
-ms.assetid: 3465168c-012f-4e9f-905d-611418d2975a
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Packages Node
-
-
-The **Packages** node is one level below the Application Virtualization System node in the **Scope** pane of the Application Virtualization Server Management Console. When you select this node, the **Results** pane displays a list of packages. Right-click the **Packages** node to display a pop-up menu that contains the following elements.
-
-**New Package**
-Displays the New Package Wizard. This wizard consists of the following three pages:
-
-1. Enter the package name and path to the corresponding package file (SFT).
-
-2. Enter the relative path to the SFT file. This path must be relative to the Server Content root.
-
-3. View the summary screen, and click **Finish** to add the new package.
-
-**View**
-Changes the appearance and content of the **Results** pane.
-
-**New Window from Here**
-Opens a new management console with the selected node as the root node.
-
-**Refresh**
-Refreshes the view of the server.
-
-**Export List**
-Creates a tab-delimited text file that contains the contents of the **Results** pane. This item displays a standard **File Save** dialog box where you specify the location for the text file you are creating.
-
-**Help**
-Displays the help system for the Application Virtualization Server Management Console.
-
-If you right-click any package that appears under the **Packages** node in the **Scope** pane, the following elements are available.
-
-**Add Version**
-Displays the Add Package Version Wizard. Use this wizard to enter the full path to a new SFT file, or browse to the location of a new SFT file. This wizard also has a summary screen.
-
-**View**
-Changes the appearance and content of the **Results** pane.
-
-**New Window from Here**
-Opens a new management console with the selected node as the root node.
-
-**Delete**
-Deletes a package from the **Results** pane.
-
-**Rename**
-Changes the name of a package in the **Results** pane.
-
-**Refresh**
-Refreshes the view of the server.
-
-**Export List**
-Creates a tab-delimited text file that contains the contents of the **Results** pane. This item displays a standard **File Save** dialog box where you specify the location for the text file you are creating.
-
-**Properties**
-Displays the **Properties** dialog box for the selected package. The **Properties** dialog box displays the GUID information, the package name, and a list of applications (including version number and enabled status) associated with the package.
-
-**Help**
-Displays the help system for the Application Virtualization Server Management Console.
-
-## Related topics
-
-
-[About Application Virtualization Packages](about-application-virtualization-packages.md)
-
-[How to Manage Packages in the Server Management Console](how-to-manage-packages-in-the-server-management-console.md)
-
-[Server Management Console: Packages Node](server-management-console-packages-node.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/packaging-method--learn-more-.md b/mdop/appv-v4/packaging-method--learn-more-.md
deleted file mode 100644
index 8fd5449b82..0000000000
--- a/mdop/appv-v4/packaging-method--learn-more-.md
+++ /dev/null
@@ -1,42 +0,0 @@
----
-title: Packaging Method (Learn More)
-description: Packaging Method (Learn More)
-author: dansimp
-ms.assetid: 3975a640-1ffd-4b4c-95fd-608469f4c205
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Packaging Method (Learn More)
-
-
-Use the **Packaging Method** page to specify the method you want to use to create a new virtual application package.
-
-This page contains the following elements:
-
-**Create Package (default)**
-Select this option to create a virtual application package by installing an application to the computer running the App-V Sequencer while the App-V Sequencer monitors the installation. You should also copy all the required installation files to a local directory on the computer running the Sequencer.
-
-**Create Package using a Package Accelerator**
-Select this option to create a package by using a Package Accelerator. The App-V Sequencer uses a Package Accelerator to create a virtual application package without having to manually install the application. For more information about Package Accelerators, see [About App-V Package Accelerators (App-V 4.6 SP1)](about-app-v-package-accelerators--app-v-46-sp1-.md).
-
-## Related topics
-
-
-[Open Package Wizard (AppV 4.6 SP1)](open-package-wizard---appv-46-sp1-.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/packaging-method-page--learn-more-.md b/mdop/appv-v4/packaging-method-page--learn-more-.md
deleted file mode 100644
index 41103433f7..0000000000
--- a/mdop/appv-v4/packaging-method-page--learn-more-.md
+++ /dev/null
@@ -1,42 +0,0 @@
----
-title: Packaging Method Page (Learn More)
-description: Packaging Method Page (Learn More)
-author: dansimp
-ms.assetid: f405a293-bcd4-48a1-b4d9-b5e4cf73c5f4
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Packaging Method Page (Learn More)
-
-
-Use the **Packaging Method** page to specify the method you want to use to create a new virtual application package.
-
-This page contains the following elements.
-
-**Create Package (default)**
-Select this option to create a virtual application package by installing an application on the computer running the App-V Sequencer while the App-V Sequencer monitors the installation. You should also copy all the required installation files to a local directory on the computer running the Sequencer.
-
-**Create Package using a Package Accelerator**
-Select this option to create a package by using a Package Accelerator. The App-V Sequencer uses a Package Accelerator to create a virtual application package. A Package Accelerator enables you to create a virtual application package without performing all of the required manual steps during installation. For more information about Package Accelerators, see [About App-V Package Accelerators (App-V 4.6 SP1)](about-app-v-package-accelerators--app-v-46-sp1-.md).
-
-## Related topics
-
-
-[Open Package Wizard (AppV 4.6 SP1)](open-package-wizard---appv-46-sp1-.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/parse-items-tab-keep.md b/mdop/appv-v4/parse-items-tab-keep.md
deleted file mode 100644
index e4f0a9b72f..0000000000
--- a/mdop/appv-v4/parse-items-tab-keep.md
+++ /dev/null
@@ -1,55 +0,0 @@
----
-title: Parse Items Tab
-description: Parse Items Tab
-author: dansimp
-ms.assetid: bdf3fe0d-404a-4745-af52-f415fa321564
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Parse Items Tab
-
-
-The **Parse Items** tab displays the mapping rules that the Sequencer uses to accommodate differences that exist between configurations on the sequencing computer and the App-V Desktop Client. This tab contains the following elements.
-
-## UI Elements List
-
-
-**Parse From**
-Displays read-only variable names evaluated by the Application Virtualization Sequencer to determine important operating system locations on the sequencing computer.
-
-**Parse To**
-Displays read-only variable names that the Application Virtualization Sequencer substitutes when encountering variable names in the associated **Parse From** column, while parsing items in the virtual file system or virtual registry.
-
-**Map Type**
-Displays read-only mapping rules that the Application Virtualization Sequencer applies to parse items in the virtual file system or virtual registry. One of the following values can occur:
-
-**OK**
-Saves the changes and exits the dialog box.
-
-**Cancel**
-Exits the dialog box without saving any changes.
-
-**Apply**
-Saves the changes and remains in the dialog box.
-
-## Related topics
-
-
-[Application Virtualization Sequencer Options Dialog Box](application-virtualization-sequencer-options-dialog-box.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/planning-and-deployment-guide-for-the-application-virtualization-system.md b/mdop/appv-v4/planning-and-deployment-guide-for-the-application-virtualization-system.md
deleted file mode 100644
index a3718091a0..0000000000
--- a/mdop/appv-v4/planning-and-deployment-guide-for-the-application-virtualization-system.md
+++ /dev/null
@@ -1,56 +0,0 @@
----
-title: Planning and Deployment Guide for the Application Virtualization System
-description: Planning and Deployment Guide for the Application Virtualization System
-author: dansimp
-ms.assetid: 6c012e33-9ac6-4cd8-84ff-54f40973833f
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Planning and Deployment Guide for the Application Virtualization System
-
-
-Microsoft Application Virtualization Management provides the capability to make applications available to end user computers without having to install the applications directly on those computers. This is made possible through a process known as *sequencing the application*, which enables each application to run in its own self-contained virtual environment on the client computer. The sequenced applications are isolated from one another, eliminating application conflicts, yet can still interact with the client computer.
-
-The Application Virtualization Client is the Application Virtualization system component that enables the end user to interact with the applications after they have been published to the computer. The client manages the virtual environment in which the virtualized applications run on each computer. After the client has been installed on a computer, the applications must be made available to the computer through a process known as *publishing*, which enables the end user to run the virtual applications. The publishing process places the virtual application icons and shortcuts on the computer—typically on the Windows desktop or on the **Start** menu—and also places the package definition and file type association information on the computer. Publishing also makes the application package content available to the end user’s computer.
-
-The virtual application package content can be placed on one or more Application Virtualization servers so that it can be streamed down to the clients on demand and cached locally. File servers and Web servers can also be used as streaming servers, or the content can be placed directly on the end user’s computer—for example, if you are using an electronic software distribution system, such as Microsoft Endpoint Configuration Manager. In a multi-server implementation, maintaining the package content and keeping it up to date on all the streaming servers requires a comprehensive package management solution. Depending on the size of your organization, you might need to have many virtual applications accessible to end users located all over the world. Managing the packages to ensure that the right applications are available to all users where and when they need access to them is therefore an essential requirement.
-
-The Application Virtualization Planning and Deployment Guide provides information to help you better understand and deploy the Microsoft Application Virtualization application and its components. It also provides step-by-step procedures for implementing the key deployment scenarios.
-
-## In This Section
-
-
-[Planning for Application Virtualization System Deployment](planning-for-application-virtualization-system-deployment.md)
-Provides the guidance necessary to plan the implementation and deployment of your Application Virtualization system.
-
-[Application Virtualization Deployment and Upgrade Considerations](application-virtualization-deployment-and-upgrade-considerations.md)
-Provides information about hardware and software requirements for installing the various Application Virtualization components, as well as upgrade information.
-
-[Electronic Software Distribution-Based Scenario](electronic-software-distribution-based-scenario.md)
-Provides information about deploying Application Virtualization using an electronic software distribution (ESD) system.
-
-[Application Virtualization Server-Based Scenario](application-virtualization-server-based-scenario.md)
-Provides information about deploying Application Virtualization using the Application Virtualization Management Server.
-
-[Stand-Alone Delivery Scenario for Application Virtualization Clients](stand-alone-delivery-scenario-for-application-virtualization-clients.md)
-Describes how to deploy Application Virtualization in a stand-alone mode, without the use of ESD or server-based resources.
-
-[Application Virtualization Reference](application-virtualization-reference.md)
-Contains detailed technical reference material related to installing and managing system components.
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/planning-for-application-virtualization-client-deployment.md b/mdop/appv-v4/planning-for-application-virtualization-client-deployment.md
deleted file mode 100644
index 4b56a86f3a..0000000000
--- a/mdop/appv-v4/planning-for-application-virtualization-client-deployment.md
+++ /dev/null
@@ -1,71 +0,0 @@
----
-title: Planning for Application Virtualization Client Deployment
-description: Planning for Application Virtualization Client Deployment
-author: dansimp
-ms.assetid: a352f80f-f0f9-4fbf-ac10-24c510b2d6be
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Planning for Application Virtualization Client Deployment
-
-
-After you have decided how you will publish and deploy virtual application packages to your end user computers, you should plan the deployment of the Application Virtualization Client software.
-
-The Application Virtualization Client is the component that actually runs the virtual applications. The Application Virtualization Client enables users to interact with icons and to double-click file types to start a virtual application. It also handles streaming of the application content from a streaming server and caches it before starting the application. The application content is structured such that all the content needed to start the application and handle initial user interaction is streamed to the end user computer first. There are two different types of Application Virtualization Client software: the Application Virtualization Client for Remote Desktop Services (formerly Terminal Services), which is used on Remote Desktop Session Host (RD Session Host) server systems, and the Application Virtualization Desktop Client, which is used for all other computers.
-
-The Application Virtualization Client should be configured at installation time, either in the Application Virtualization Management Console or via the installer command line, with a number of important settings, including the following:
-
-- Locations of the icons for all the applications.
-
-- The location of the OSD file that contains the package definition information.
-
-- The application content source.
-
-- The communications protocol to be used when retrieving the preceding items.
-
-- The cache size and cache size management method to be used.
-
-To expedite the deployment of the Application Virtualization Client software when using an electronic software distribution (ESD) solution, the preceding settings must be defined carefully in advance. This is especially important when you have computers in different offices, where their clients would need to be configured to use different source locations.
-
-**Note**
-- The icon location and OSD file values are an important factor to consider when choosing your publishing method, whether using Windows Installer or SFTMIME. The setting for the application content source is defined by your choice of streaming method.
-
-- To ensure that the cache has sufficient space allocated for all packages that might be deployed, use the **Use free disk space threshold** setting when you configure the client so that the cache can grow as needed. Alternatively, determine in advance how much disk space will be needed for the App-V cache, and at installation time, set the cache size accordingly. For more information about the cache space management feature, see **How to Use the Cache Space Management Feature** in the Microsoft Application Virtualization (App-V) Operations Guide.
-
-- During both the publishing and HTTP(S) streaming operations,App-V 4.5 SP1 clients use the proxy server settings that are configured in Internet Explorer on the user’s computer.
-
-For more information about configuring the client installation parameters, see [Application Virtualization Client Installer Command-Line Parameters](application-virtualization-client-installer-command-line-parameters.md).
-
-
-
-Finally, you need to determine how to deploy the Application Virtualization Desktop Client software for the desktop clients. Although it is possible to deploy the Application Virtualization Desktop Client manually on each computer, most organizations would need to do this through some automated process. A medium or large organization might have an ESD system in operation, and that would be an ideal way to deploy the client. If no ESD system exists, you can use your standard method of installing software in your organization. Choices include Group Policy or various scripting techniques. Depending on the number and size of the offices you have, this deployment process can be complex, and it is essential that you take a structured approach to ensure all computers get a client installed with the correct configuration.
-
-## Related topics
-
-
-[Planning for Application Virtualization System Deployment](planning-for-application-virtualization-system-deployment.md)
-
-[How to Install the Client by Using the Command Line](how-to-install-the-client-by-using-the-command-line-new.md)
-
-[How to Publish a Virtual Application on the Client](how-to-publish-a-virtual-application-on-the-client.md)
-
-[How to Upgrade the Application Virtualization Client](how-to-upgrade-the-application-virtualization-client.md)
-
-[How to Uninstall the App-V Client](how-to-uninstall-the-app-v-client.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/planning-for-application-virtualization-system-deployment.md b/mdop/appv-v4/planning-for-application-virtualization-system-deployment.md
deleted file mode 100644
index 7ac4ec4db2..0000000000
--- a/mdop/appv-v4/planning-for-application-virtualization-system-deployment.md
+++ /dev/null
@@ -1,72 +0,0 @@
----
-title: Planning for Application Virtualization System Deployment
-description: Planning for Application Virtualization System Deployment
-author: dansimp
-ms.assetid: 8215269f-c083-468a-bf0b-886b0d2dd69e
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Planning for Application Virtualization System Deployment
-
-
-This section provides important information to help you plan your deployment of Microsoft Application Virtualization.
-
-## In This Section
-
-
-[Best Practices for the Application Virtualization Sequencer](best-practices-for-the-application-virtualization-sequencer-sp1.md)
-Provides important security-related planning information about setting up the Application Virtualization Sequencer to sequence application packages.
-
-[Planning the Application Virtualization Sequencer Implementation](planning-the-application-virtualization-sequencer-implementation.md)
-Provides planning guidance for implementing the App-V sequencer.
-
-[Using Electronic Software Distribution as a Package Management Solution](using-electronic-software-distribution-as-a-package-management-solution.md)
-Provides planning guidance for using an electronic software distribution system to manage application package content, including setting up publishing and streaming.
-
-[Using Application Virtualization Servers as a Package Management Solution](using-application-virtualization-servers-as-a-package-management-solution.md)
-Provides the planning information necessary for managing application package content in an Application Virtualization Server-based deployment.
-
-[Planning for Application Virtualization Client Deployment](planning-for-application-virtualization-client-deployment.md)
-Provides important planning considerations for deploying the Application Virtualization Client.
-
-[Planning for Migration from Previous Versions](planning-for-migration-from-previous-versions.md)
-Identifies the steps for upgrading from a previous version and lists several important factors to consider.
-
-[Planning for Security and Protection](planning-for-security-and-protection.md)
-Provides information about enhanced security features in Application Virtualization 4.5.
-
-## Reference
-
-
-[Application Virtualization Reference](application-virtualization-reference.md)
-
-## Related Sections
-
-
-[Application Virtualization Deployment and Upgrade Considerations](application-virtualization-deployment-and-upgrade-considerations.md)
-
-## Related topics
-
-
-[Application Virtualization Server-Based Scenario](application-virtualization-server-based-scenario.md)
-
-[Electronic Software Distribution-Based Scenario](electronic-software-distribution-based-scenario.md)
-
-[Stand-Alone Delivery Scenario for Application Virtualization Clients](stand-alone-delivery-scenario-for-application-virtualization-clients.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/planning-for-client-security.md b/mdop/appv-v4/planning-for-client-security.md
deleted file mode 100644
index e47a871c34..0000000000
--- a/mdop/appv-v4/planning-for-client-security.md
+++ /dev/null
@@ -1,109 +0,0 @@
----
-title: Planning for Client Security
-description: Planning for Client Security
-author: dansimp
-ms.assetid: 4840a60f-4c91-489c-ad0b-6671882abf9b
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 08/30/2016
----
-
-
-# Planning for Client Security
-
-
-The App-V Client provides several security enhancements that were not present in previous versions of the product. These changes provide improved security after installation and through later configuration of the client settings. This topic describes some of those enhancements and identifies several important security-related configuration settings that you should consider during your planning process. It is important to remember that virtual applications are still executables, so you must ensure that these assets cannot be tampered with by unauthorized people. For this reason, the Open Software Descriptor (OSD) file cache is protected as described later in this topic, and we strongly recommend that you use RTSPS, HTTPS, and IPsec to protect publishing and streaming.
-
-## App-V Client Security
-
-
-By default, at installation the App-V client is configured with the minimum permissions required to allow a user to perform a publishing refresh and to start applications. Other security enhancements provided in the App-V client include the following:
-
-- By default, the OSD file cache can be updated only by administrators and by using the publishing refresh process.
-
-- The log file (sftlog.txt) is accessible only by accounts with local administrative access to the client.
-
-- The log file now has a maximum size.
-
-### File Type Associations
-
-By default, the installation of the client registers file type associations (FTAs) for OSD files, which enables users to start applications directly from OSD files instead of the published shortcuts. If a user with local administrator rights receives an OSD file containing malicious code, either in e-mail or downloaded from a Web site, the user can open the OSD file and start the application even if the client has been set to restrict the **Add Application** permission. You can unregister the FTAs for the OSD to reduce this risk. Also, consider blocking this extension in the e-mail system and at the firewall. For more information about configuring Outlook to block extensions, see .
-
-**Security Note:**
-
-Starting with App-V version 4.6, the file type association is no longer created for OSD files during a new installation of the client, although the existing settings will be maintained during an upgrade from version 4.2 or 4.5 of the App-V client. If for any reason it is essential to create the file type association, you can create the following registry keys and set their values as shown:
-
- Create HKEY\_CLASSES\_ROOT\\.osd with a default value of SoftGrid.osd.File
-
- Under HKEY\_LOCAL\_MACHINE\\software\\classes\\Softgrid.osd.file, create a string value named AppUserModelID with a data value of Microsoft.AppV.Client.Tray
-
-### Authorization
-
-During installation, you can use the **RequireAuthorizationIfCached** parameter to configure the client to require authorization from the server when the user tries to start an application. You should consider carefully how to set this parameter. If the App-V server is unavailable for any reason, the application will use the most recent stored state of this parameter to control user access to the application. If the user has not launched the application successfully before the App-V server becomes unavailable, they will not be able to launch the application until they can communicate with the server and receive authorization. However, if you set the parameter so that the client does not require authorization and if the server is unavailable, all previously cached applications can be started whether authorized or not. Also, if the user has permission to change the client to Work Offline mode through permissions or if the user is a local administrator, the user would be able to open all cached packages as if the App-V infrastructure was unavailable.
-
-### Antivirus Scanning
-
-Antivirus software running on an App-V Client computer can detect and report an infected file in the virtual environment. However, it cannot disinfect the file. If a virus is detected in the virtual environment, the antivirus software would perform the configured quarantine or repair operation in the cache, not in the actual package. Configure the antivirus software with an exception for the sftfs.fsd file. This file is the cache file that stores packages on the App-V Client.
-
-**Security Note:**
-
-If a virus is detected in an application or package deployed in the production environment, replace the application or package with a virus-free version.
-
-## Communication Between Client and Server
-
-
-Publishing refreshes and package streaming are also areas where security considerations relating to client-server communication are important.
-
-### Publishing Refresh
-
-When the client communicates with the server to perform a publishing refresh, it uses the credentials of the logged on user to request information about the application packages. You should secure the communication that occurs between the App-V client and App-V Management Server to ensure that none of the publishing information can be tampered with in transit. This is done by using the Enhanced Security option, which will use RTSPS/HTTPS. Communication between the Client and the location where the ICO and OSD files are stored should use IPsec for SMB/CIFS shares and HTTPS for an IIS server.
-
-**Note**
-If you are using IIS to publish the ICO and OSD files, configure a MIME type for OSD=TXT; otherwise, IIS will refuse to serve the ICO and OSD files to clients.
-
-
-
-### Package Streaming
-
-When a user launches an application for the first time, or if auto-loading parameters have been set on the client, the application package is streamed from a server to the client cache. This process supports the RTSP/RTSPS, HTTP/HTTPS, and SMB/CIFS protocols. The OSD files control which protocols are used, unless the **ApplicationSourceRoot** or **OverrideURL** setting has been configured on the clients. You should configure communication to occur over RTSPS, HTTPS, or IPsec for SMB/CIFS to achieve higher levels of security. For more information about choosing which communication method to use, see the App-V Planning and Deployment Guide at .
-
-**Note**
-If you are using IIS to publish packages (SFT files), configure a MIME type for SFT=Binary; otherwise, IIS will refuse to serve the SFT files to clients.
-
-
-
-### Roaming Profiles and Folder Redirection
-
-The App-V system stores user-specific changes to packages in the usrvol\_sftfs\_v1.pkg file. This file is located in the Application Data folder of a user’s profile. Because the profile or a redirected Application Data folder is transferred between the client and the server, use IPsec to secure the communication.
-
-## Considerations for Internet-Facing Clients
-
-
-For Internet-facing clients, it is important to consider whether the client is domain joined or non-domain joined.
-
-### Domain Joined Client
-
-By default, App-V Clients use Kerberos tickets that were issued by Active Directory Domain Services for authentication and authorization on the intranet. These Kerberos tickets are valid for 10 hours by default. The client will use this ticket to access the App-V server for as long as the ticket is valid, even if the computer is unable to connect to the domain controller to refresh the ticket. If the Kerberos ticket expires, the App-V client will revert to NTLM authentication and use the user’s cached credentials.
-
-### Non-Domain Joined Client
-
-If a user is home-based and the computer is not joined to the company domain, App-V can still support delivering applications. To authenticate and authorize a user to perform a publishing refresh and to start applications, configure the user account on the client computer to store the user name and password that has access to the App-V environment and to provide appropriate permissions to the applications.
-
-## Related topics
-
-
-[Planning for Security and Protection](planning-for-security-and-protection.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/planning-for-migration-from-previous-versions.md b/mdop/appv-v4/planning-for-migration-from-previous-versions.md
deleted file mode 100644
index 2e96c0f008..0000000000
--- a/mdop/appv-v4/planning-for-migration-from-previous-versions.md
+++ /dev/null
@@ -1,218 +0,0 @@
----
-title: Planning for Migration from Previous Versions
-description: Planning for Migration from Previous Versions
-author: dansimp
-ms.assetid: 62967bf1-542f-41b0-838f-c62f3430ac73
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 08/30/2016
----
-
-
-# Planning for Migration from Previous Versions
-
-
-Before attempting to upgrade to Microsoft Application Virtualization 4.5 or later versions, any version prior to 4.1 must be upgraded to version 4.1. You should plan to upgrade your clients first, and then upgrade the server components. Clients that have been upgraded to 4.5 will continue to work with Application Virtualization servers that have not yet been upgraded. Earlier versions of the client are not supported on servers that have been upgraded to 4.5. For more information about upgrading the system components, see [Application Virtualization Deployment and Upgrade Considerations](application-virtualization-deployment-and-upgrade-considerations.md).
-
-To help ensure a successful migration, the Application Virtualization system components should be upgraded in the following order:
-
-1. **Microsoft Application Virtualization Clients.** For step-by-step upgrade instructions, see [How to Upgrade the Application Virtualization Client](how-to-upgrade-the-application-virtualization-client.md).
-
-2. **Microsoft Application Virtualization Servers and Database.** For step-by-step upgrade instructions, see [How to Upgrade the Servers and System Components](how-to-upgrade-the-servers-and-system-components.md).
-
- **Note**
- If you have more than one server sharing access to the Application Virtualization database, all those servers must be taken offline while the database is being upgraded. You should follow your normal business practices for the database upgrade, but it is highly advisable that you test the database upgrade by using a backup copy of the database first on a test server. Then, you should select one of the servers for the first upgrade, which will upgrade the database schema. After the production database has been successfully upgraded, you can upgrade the other servers.
-
-
-
-3. **Microsoft Application Virtualization Management Web Service.** This step applies only if the Management Web Service is on a separate server, which would require that you run the server installer program on that separate server to upgrade the Web service. Otherwise, the previous server upgrade step will automatically upgrade the Management Web Service.
-
-4. **Microsoft Application Virtualization Management Console.** This step applies only if the Management Console is on a separate computer, which would require that you run the server installer program on that separate computer to upgrade the console. Otherwise, the previous server upgrade step will upgrade the Management Console.
-
-5. **Microsoft Application Virtualization Sequencer.** For step-by-step instructions, see [How to Install the Application Virtualization Sequencer](how-to-install-the-application-virtualization-sequencer.md). Any virtual application packages sequenced in version 4.2 will not have to be re-sequenced for use with version 4.5. However, you should consider upgrading the virtual packages to the Microsoft Application Virtualization 4.5 format if you would like to apply default access control lists (ACLs) or generate a Windows Installer file. This is a simple process and requires only that the existing virtual application package be opened and saved with the 4.5 Sequencer. This can be automated by using the Application Virtualization Sequencer command-line interface.
-
-## App-V 4.6 Client Package Support
-
-
-You can deploy packages created in previous versions of App-V to App-V 4.6 Clients. However, you must modify the associated **.osd** file so that it includes the appropriate operating system and chip architecture information. Use the following values.
-
-
-
-
-
-
-
-
OS Value
-
-
-
-
-
<OS VALUE=”Win2003TS”/>
-
-
-
<OS VALUE=”Win2003TS64”/>
-
-
-
<OS VALUE=”Win2008TS”/>
-
-
-
<OS VALUE=”Win2008TS64”/>
-
-
-
<OS VALUE=”Win2008R2TS64”/>
-
-
-
<OS VALUE=”Win7”/>
-
-
-
<OS VALUE=”Win764”/>
-
-
-
<OS VALUE=”WinVista”/>
-
-
-
<OS VALUE=”WinVista64”/>
-
-
-
<OS VALUE=”WinXP”/>
-
-
-
<OS VALUE=”WinXP64”/>
-
-
-
-
-
-
-To run a newly created 32-bit package, you must sequence the application on a computer running a 32-bit operating system with the App-V 4.6 Sequencer installed. After you have sequenced the application, in the Sequencer console, select the **Deployment** tab and then specify the appropriate operating system and chip architecture as required.
-
-**Important**
-Applications sequenced on a computer running a 64-bit operating system must be deployed to computers running a 64-bit operating system. New 32-bit packages created by using the App-V 4.6 Sequencer will not run on computers running the App-V 4.5 Client.
-
-
-
-To run new 64-bit packages on the App-V 4.6 Client, you must sequence the application on a computer running the App-V 4.6 Sequencer and that is running a 64-bit operating system. After you have sequenced the application, in the Sequencer console, select the **Deployment** tab and then specify the appropriate operating system and chip architecture as required.
-
-The following table lists which client versions will run packages created by using the various versions of the Sequencer.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Sequenced by using the App-V 4.2 Sequencer
-
Sequenced by using the App-V 4.5 Sequencer
-
Sequenced by using the 32-bit App-V 4.6 Sequencer
-
Sequenced by using the 64-bit App-V 4.6 Sequencer
-
Sequenced by using the 32-bit App-V 4.6 SP1 Sequencer
-
Sequenced by using the 64-bit App-V 4.6 SP1 Sequencer
-
-
-
-
-
4.2 Client
-
Yes
-
No
-
No
-
No
-
No
-
No
-
-
-
4.5 Client ¹
-
Yes
-
Yes
-
No
-
No
-
No
-
No
-
-
-
4.6 Client (32-bit)
-
Yes
-
Yes
-
Yes
-
No
-
Yes
-
No
-
-
-
4.6 Client (64-bit)
-
Yes
-
Yes
-
Yes
-
Yes
-
Yes
-
Yes
-
-
-
4.6 SP1 Client
-
Yes
-
Yes
-
Yes
-
No
-
Yes
-
No
-
-
-
4.6 SP1 Client (64-bit)
-
Yes
-
Yes
-
Yes
-
Yes
-
Yes
-
Yes
-
-
-
-
-
-
-¹Applies to all versions of the App-V 4.5 Client, including App-V 4.5, App-V 4.5 CU1 and App-V 4.5 SP1.
-
-## Additional Migration Considerations
-
-
-One of the features of the App-V 4.5 Sequencer is the ability to create Windows Installer files (.msi) as control points for virtual application package interoperability with electronic software distribution (ESD) systems such as Microsoft Endpoint Configuration Manager. Previous Windows Installer files created with the .msi tool for Application Virtualization that were installed on a App-V 4.1 or 4.2 Client that is subsequently upgraded to 4.5 continue to work, although they cannot be installed on the 4.5 Client. However, they cannot be removed or upgraded unless they are upgraded in the 4.5 Sequencer. The original pre-4.5 virtual application package would need to be opened in the 4.5 Sequencer and then saved as a Windows Installer File.
-
-**Note**
-If the App-V 4.2 Client has already been upgraded to 4.5, it is possible to use script as a workaround to preserve the 4.2 packages on 4.5 clients and allow them to be managed. This script must copy two files, msvcp71.dll and msvcr71.dll, to the App-V installation folder and set the following registry key values under the registry key \[HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Microsoft\\SoftGrid\\4.5\\Client\\Configuration\]:
-
-"ClientVersion"="4.2.1.20"
-
-"GlobalDataDirectory"="C:\\\\Documents and Settings\\\\All Users\\\\Documents\\\\" (a globally writeable location)
-
-
-
-Windows Installer files generated by the App-V 4.5 Sequencer display the error message "This package requires Microsoft Application Virtualization Client 4.5 or later" when you try to run them on an App-V 4.6 Client. Open the old package with either the App-V 4.5 SP1 Sequencer or the App-V 4.6 Sequencer and generate a new .msi for the package.
-
-Any 4.2 reports that were created and saved will be overwritten when the server is upgraded to 4.5. If you need to keep these reports, you must save a backup copy of the SftMMC.msc file located in the SoftGrid Management Console folder on the server and use that copy to replace the new SftMMC.msc that is installed during the upgrade.
-
-For additional information about upgrading from previous versions, see [Upgrading to Microsoft Application Virtualization 4.5 FAQ](https://go.microsoft.com/fwlink/?LinkId=120358) (https://go.microsoft.com/fwlink/?LinkId=120358).
-
-## Related topics
-
-
-[Planning for Application Virtualization System Deployment](planning-for-application-virtualization-system-deployment.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/planning-for-security-and-protection.md b/mdop/appv-v4/planning-for-security-and-protection.md
deleted file mode 100644
index dd42746a18..0000000000
--- a/mdop/appv-v4/planning-for-security-and-protection.md
+++ /dev/null
@@ -1,49 +0,0 @@
----
-title: Planning for Security and Protection
-description: Planning for Security and Protection
-author: dansimp
-ms.assetid: d0e2ef81-c197-4020-ad85-8d66fe5c178f
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Planning for Security and Protection
-
-
-As an infrastructure administrator, you must provide a secure, productive, and supportable, environment. Security for the Microsoft Application Virtualization (App-V) system relies on proper setup of the software and the environment in which it operates. This section of the Planning and Deployment Guide provides guidance for configuring the various App-V components to enhance the security of your environment. You should carefully consider the exposure and attack surface of your App-V environment before deciding to deploy a system without applying the security recommendations outlined in this section.
-
-## In This Section
-
-
-[Security and Protection Overview](security-and-protection-overview.md)
-Provides overview information about the security and protection of your App-V system.
-
-[Planning for Server Security](planning-for-server-security.md)
-Provides information you can use to configure the Application Virtualization Management Server and Application Virtualization Streaming Server.
-
-[Planning for Client Security](planning-for-client-security.md)
-Provides information you can use to configure the Application Virtualization Management Desktop Client.
-
-[Planning for Sequencer Security](planning-for-sequencer-security.md)
-Provides information you can use to configure the Application Virtualization Sequencer.
-
-## Related topics
-
-
-[Planning for Application Virtualization System Deployment](planning-for-application-virtualization-system-deployment.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/planning-for-sequencer-security.md b/mdop/appv-v4/planning-for-sequencer-security.md
deleted file mode 100644
index 63b4815f06..0000000000
--- a/mdop/appv-v4/planning-for-sequencer-security.md
+++ /dev/null
@@ -1,70 +0,0 @@
----
-title: Planning for Sequencer Security
-description: Planning for Sequencer Security
-author: dansimp
-ms.assetid: 8043cb02-476d-4c28-a850-903a8ac5b2d3
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Planning for Sequencer Security
-
-
-Incorporate recommended implementation practices as early as possible when configuring Application Virtualization (App-V) so that your Sequencer implementation is functional and more secure. If you have already configured the Sequencer, use the following best-practice guidelines to revisit your design decisions and analyze them from a security perspective.
-
-**Important**
-The App-V Sequencer collects and deploys all application information recorded on the computer running the sequencer. You should ensure that all users accessing the computer running the Sequencer have administrative credentials. Users with user account credentials should not have access to control package contents and package files. If you are sequencing on a computer running Remote Desktop Services (formerly Terminal Services), make sure it is a computer that is dedicated to sequencing and that users with user account credentials are not connected to it during sequencing.
-
-
-
-## Sequencer Security Best Practices
-
-
-Consider the following scenarios and the associated best practices when implementing and using the Application Virtualization (App-V) Sequencer:
-
-- **Virus scanning on the computer running the Sequencer**—It is recommended that you scan the computer running the Sequencer for viruses and then disable all antivirus and malware detection software on the computer running the Sequencer during the sequencing process. This will speed the sequencing process and prevent the antivirus and anti-malware software components from interfering with the sequencing process. Next install the sequenced package on a computer not running the Sequencer, and after successful installation, scan that computer for viruses. If viruses are found, the manufacturer of the software should be contacted to inform them of the infected source files and request an updated installation source without viruses. Optionally, the Sequencer could be scanned after the installation phase and if a virus is found, the software manufacturer should be contacted as mentioned above.
-
- **Note**
- If a virus is detected in an application, the application should not be deployed to target computers.
-
-
-
-- **Capturing access control lists (ACLs) on NTFS files**—The App-V Sequencer captures NTFS file system permissions for the files that are monitored during the installation of the product. This capability allows you to more accurately replicate the intended behavior of the application, as if it were installed locally and not virtualized. In some scenarios, an application might store information that users were not intended to access within the application files. For example, an application could store credentials information in a file inside of the application. If ACLs are not enforced on the package, a user could potentially view and then use this information outside of the application.
-
- **Note**
- You should not sequence applications that store unencrypted security-specific information, such as passwords, and so on.
-
-
-
-~~~
-During the installation phase, you can modify the default permissions of the files if necessary. After completion of the sequencing process, but before saving the package, you can choose whether to enforce security descriptors that were captured during the installation of the application. By default, App-V will enforce the security descriptors specified during the installation of the application. If you turn off security descriptor enforcement, you should test the application to ensure the removal of associated Access Control Lists (ACL) will not cause the application to perform unexpectedly.
-~~~
-
-- **Sequencer doesn’t capture registry ACLs**—Although the Sequencer captures the NTFS file system ACLs during the installation phase of sequencing, it does not capture the ACLs for the registry. Users will have full access to all registry keys for virtual applications except for services. However, if a user modifies the registry of a virtual application, the change will be stored in a specific store (**uservol\_sftfs\_v1.pkg**) and will not affect other users.
-
-- **Application services**—App-V provides support for application services that are part of a virtualized application. However, in the virtual environment, the security context that they will run as is limited. The only security contexts supported in a virtual environment are Local System, Local Service, and Network Service. During sequencing, if a security context is specified for an application service other than the three supported, the Local System security context will be applied in the virtual environment. If the application service is configured to use either Local Service or Network Service, it will be honored in the virtual environment. Configuring the service account can be done during the sequencing process using these three security contexts.
-
-- **Persisted security information**—When sequencing applications, you can install the application as a user would or you can develop an automated method for installing the application while being monitored. Everything that is not being excluded from the package will be captured as part of that package so that the application will have the necessary assets to run in a virtualized environment. Some applications store sensitive security information (such as passwords) during the installation; if persisted unprotected, this security information could be accessed by other users with access to the package. During installation, if an application installation asks for a password or other security-sensitive information, check with the documentation to ensure that it is either not persisted (removed after installation) or, if persisted, that it is protected (encrypted).
-
-- **Securing virtual application packages**—Always save virtual application packages in a secure location on the network to protect the package from being tampered with or corrupted.
-
-## Related topics
-
-
-[Planning for Security and Protection](planning-for-security-and-protection.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/planning-for-server-security.md b/mdop/appv-v4/planning-for-server-security.md
deleted file mode 100644
index 289d44d508..0000000000
--- a/mdop/appv-v4/planning-for-server-security.md
+++ /dev/null
@@ -1,125 +0,0 @@
----
-title: Planning for Server Security
-description: Planning for Server Security
-author: dansimp
-ms.assetid: c7cd8227-b359-41e7-a8ae-d0d5718a76a2
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 08/30/2016
----
-
-
-# Planning for Server Security
-
-
-To enhance the security of an environment, you must look at the exposure to any potential threats in the environment. Providing security for an App-V infrastructure requires you to use the specific App-V security features as well as the security practices and features for the underlying infrastructure. Securing the underlying infrastructure for services such as Internet Information Services (IIS), Active Directory Domain Services, and SQL Server will improve the overall security for your App-V system.
-
-The default settings for the server installation provide the highest levels of security. However, some of the components rely on underlying infrastructure that is not configured as part of the installation. Following up with post-installation steps will enhance the security of the App-V infrastructure.
-
-The content directory contains all of the packages that are to be streamed to clients. These resources need to be as secure as possible to eliminate many possible security threats. The following list offers some additional guidance:
-
-- UNC-based publishing and/or streaming—The permissions for this item should be the most restrictive in the environment. Use NTFS permissions to implement the most restrictive access control lists (ACLs) for the content directory (Users=Read, Administrators=Read and Write).
-
-- IIS used for publishing and/or streaming—Configure IIS to support only Windows Integrated authentication. Remove anonymous access to the IIS server, and restrict access to the directory with NTFS permissions.
-
-- RTSP/RTSPS to stream application packages—Configure the App-V Provider Policy to require authentication, enforce access permissions, and enable only required groups to have access to the provider policy. Configure applications with the appropriate permissions in the database.
-
-Keep the number of users with administrative privileges to a minimum to reduce possible threats to the data in the data store and to avoid publishing malicious applications into the infrastructure.
-
-## Application Virtualization Security
-
-
-App-V uses several methods of communication between the various components of the infrastructure. When you plan your App-V infrastructure, securing the communications between servers can reduce the security risks that might already be present on the existing network.
-
-### Data Store
-
-The Application Virtualization Management Server and Application Virtualization Management Service communicate with the data store by using an SQL connection over TCP port 1433. The Management Server uses the data store to retrieve application and configuration data, and it writes usage information to the database. The Management Service communicates with the data store on behalf of an administrator who is configuring the App-V infrastructure. Because the data store contains critical information, it is important to minimize threats to this data.
-
-It is recommended that communications between App-V Management Server, Management Service and the data store be secured with Internet Protocol Security (IPsec). Specifically, create policies that secure the communication channel between the data store (SQL) and the Management Server and the data store and the Management Service. You can also deploy server and domain isolation with IPsec, ensuring all App-V infrastructure components communicate only with secure channels. For information about implementing IPsec, refer to the following documentation:
-
-- For Windows Server 2003, see (https://go.microsoft.com/fwlink/?LinkId=133226).
-
-- For Windows Server 2008, see (https://go.microsoft.com/fwlink/?LinkId=133227).
-
-### Content Directory
-
-The App-V Management Server installation configures a location for the content directory. This directory is the storage location for virtualized application packages. This location can be local to the server, or it can be placed on a remote network share. Therefore, implement IPsec to help secure the communication with a remote location for the content directory.
-
-You can also use a virtual directory on an IIS server to stream packages to the clients. If the virtual directory that is created for content is located on a remote source, use IPsec to help secure the communication between the IIS server and the remote storage location.
-
-The content directory contains all of the packages that are streamed to clients. These resources need to be as secure as possible to eliminate many possible security threats.
-
-### Security Protocols
-
-You can use RTSPS or HTTPS for enhanced secure communications. RTSPS is the protocol used by App-V servers, and HTTPS is the protocol used by IIS servers. These protocols are used when publishing applications from the server to the Application Virtualization Desktop Client. After you determine the desired protocol, add a publishing server that uses that protocol.
-
-### Configuring App-V Servers for RTSPS
-
-Installing or configuring an App-V Management Server or Streaming Server to use Enhanced Security (for example, TLS) requires that an X.509 V3 certificate be provisioned to the App-V server. When you prepare to install or configure security for a server, you must fulfill some specific requirements. Technical requirements for deploying and configuring certificates for a more secure App-V Management Server or Streaming Server include the following:
-
-- Certificate must be valid. Otherwise, the client terminates the connection.
-
-- Certificate must contain the correct Enhanced Key Usage (EKU) - Server Authentication (OID 1.3.6.1.5.5.7.3.1). Otherwise, the client terminates the connection.
-
-- Certificate fully qualified domain name (FQDN) must match the server on which it is installed. For example, if the client is calling `RTSPS://Myserver.mycompany.com/content/MyApp.sft`, but the certificate **Issued To** field contains `Myserver1.mycompany.com`, the client will not connect to the server and the session is terminated, even if `Myserver.mycompany.com` and `Myserver1.mycompany.com` resolve to the same IP address.
-
- **Note**
- If you use App-V in a network load balanced cluster, the certificate must be configured with *Subject Alternate Names* (SANs) to support RTSPS. For information about configuring the certification authority (CA) and creating certificates with SANs, see (https://go.microsoft.com/fwlink/?LinkId=133228).
-
-
-
-- The CA issuing the certificate to the App-V server must be trusted by the client connecting to the server. Otherwise, the client terminates the connection.
-
-- You must change the permissions for the *Certificate Private Key* to enable access by the Server App-V Service. By default, the App-V Management Server and Streaming Server services run under the Network Service account. When a PKCS\#10 is generated on the server, a private key is created. Only the Local System and Administrators groups have access to this key. These default ACLs prevent the App-V server from accepting secure connections.
-
- **Note**
- For information about configuring a public key infrastructure (PKI), see (https://go.microsoft.com/fwlink/?LinkId=133229).
-
-
-
-### Configuring IIS Servers with HTTPS
-
-App-V might use IIS servers in certain infrastructure configurations. For more information about configuring IIS servers, see (https://go.microsoft.com/fwlink/?LinkId=133230).
-
-**Note**
-If you are using IIS to publish the ICO and OSD files, configure a MIME type for OSD=TXT; otherwise, IIS will refuse to serve the ICO and OSD files to clients.
-
-
-
-### Application-Level Security
-
-You can configure the servers to stream specific applications to a user’s desktop. However, access permission actually is granted at the package level, not at the application level. Although a specific application might not be published to the user’s desktop, if the user has permission to add applications or is an administrator on the client computer, the user can create and use a shortcut on the client to run all the applications in a package.
-
-## Configuring App-V Administration for a Distributed Environment
-
-
-When designing the infrastructure for your specific organization, you can install the App-V Management Web Service on a computer other than the computer where you install the App-V Management Server. Common reasons for separating these App-V components include the following:
-
-- Performance
-
-- Reliability
-
-- Availability
-
-- Scalability
-
-For the infrastructure to operate correctly, separating the App-V Management Console, Management Server and Management Web Service requires additional configuration. For detailed information about how to configure the server, see [How to Configure the Server to be Trusted for Delegation](how-to-configure-the-server-to-be-trusted-for-delegation.md).
-
-## Related topics
-
-
-[Planning for Security and Protection](planning-for-security-and-protection.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/planning-the-application-virtualization-sequencer-implementation.md b/mdop/appv-v4/planning-the-application-virtualization-sequencer-implementation.md
deleted file mode 100644
index f330eaca98..0000000000
--- a/mdop/appv-v4/planning-the-application-virtualization-sequencer-implementation.md
+++ /dev/null
@@ -1,74 +0,0 @@
----
-title: Planning the Application Virtualization Sequencer Implementation
-description: Planning the Application Virtualization Sequencer Implementation
-author: dansimp
-ms.assetid: 052f32fe-ad13-4921-a8ce-4a657eb2b2bf
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Planning the Application Virtualization Sequencer Implementation
-
-
-Sequencing, the process used by Application Virtualization to create virtual applications and application packages, requires the use of a computer with the Application Virtualization Sequencer software installed.
-
-During the sequencing process, the Sequencer is placed in monitor mode, and the application to be sequenced is installed on the sequencing computer. Next, the sequenced application is started, and its most important and commonly used functions are exercised so that the monitoring process can configure the primary feature block, which contains the minimum content in an application package that is necessary for an application to run. When these steps are complete, monitoring mode is stopped and the sequenced application is saved and tested to verify correct operation.
-
-When deciding which applications to choose for sequencing, remember that certain applications cannot be sequenced. These include certain parts of the Windows operating system, such as Internet Explorer, device drivers, and applications that start services at boot time.
-
-For step-by-step information about installing the Sequencer, see [How to Install the Application Virtualization Sequencer](how-to-install-the-application-virtualization-sequencer.md).
-
-**Important**
-The entire sequencing process plan should be reviewed and approved by your corporate security team. Sequencer operations would usually be kept separate from the production environment in a lab. This can be as simple or as comprehensive as necessary, based on your business requirements. The sequencing computers will need connectivity to the corporate network to copy finished packages over to the production servers. However, because they are typically operated without antivirus protection, they must not be on the corporate network unprotected—for example, you might be able to operate behind a firewall or on an isolated network segment. Using Virtual Machines configured to share an isolated virtual network might also be an acceptable approach. Follow your corporate security policies to safely address this situation.
-
-
-
-Key steps for planning the sequencing process include the following:
-
-- Consider the number of applications you expect to process each month, the size of those applications, and add an allowance for sequencing future updates. Packages can be up to 4 GB in size, compressed or uncompressed.
-
-- Prepare and document a methodical, repeatable process for your organization to follow when sequencing each application. This should include the use of a checklist for each run, as well as a version control process. The use of a tracking log for each sequenced application is also very helpful when investigating possible technical issues with a package.
-
-- For sequencing applications, use high-performing computers that are optimized for processing throughput, with at least 4 GB of RAM and a fast CPU (3 GHz or faster). Fast hard disks and the use of separate disk volumes can also improve performance. Virtual Machines are ideal for sequencing because they can easily be reset, or you can use a physical computer with a clean image on a local partition to enable rapid re-imaging after each package sequencing operation has been completed.
-
- **Important**
- Running the App-V sequencer in Safe Mode is not supported.
-
-
-
-- Verify that you understand the sequenced application’s operating environment, including integration elements such as Microsoft Office or the Java Runtime Environment, because this will often determine whether anything has to be installed on the sequencing computer prior to sequencing the application.
-
-- Ensure that each new sequencing operation always starts with a clean base image. Make sure that the sequencing computer has been reset, either by restoring the saved image to a physical computer or by restarting a virtual machine after discarding all changes. The base image should have the latest updates applied from Windows Update before saving.
-
-- Turn off anything on the sequencing computer that can interfere with the install monitoring process, such antivirus scanners and Windows Update, because having a stable platform during the sequencing process is essential. Because this step incurs significant security risks, ensure that the correct precautions are taken to protect the computer and network as well as the sequenced application package. We recommend that you do an antivirus scan of application packages before sequencing them.
-
-- Include a detailed process for testing each application after sequencing. Testing the sequenced application will determine whether it functions correctly and is an essential part of the process prior to deploying the virtualized application to end users. As the final step in testing prior to wide-scale deployment to end users, you should also plan for a pilot deployment to a test group.
-
-- When testing sequenced applications, choose computer equipment of the same type and running the same operating systems that are in use in the company production environment. As long as they are configured properly, either virtual machines or physical machines can be used.
-
-## Related topics
-
-
-[Application Virtualization Sequencer Hardware and Software Requirements](application-virtualization-sequencer-hardware-and-software-requirements.md)
-
-[How to Install the Application Virtualization Sequencer](how-to-install-the-application-virtualization-sequencer.md)
-
-[How to Upgrade the Application Virtualization Sequencer](how-to-upgrade-the-application-virtualization-sequencer.md)
-
-[Security and Protection Overview](security-and-protection-overview.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/planning-your-streaming-solution-in-an-application-virtualization-server-based-implementation.md b/mdop/appv-v4/planning-your-streaming-solution-in-an-application-virtualization-server-based-implementation.md
deleted file mode 100644
index 6a03d508c0..0000000000
--- a/mdop/appv-v4/planning-your-streaming-solution-in-an-application-virtualization-server-based-implementation.md
+++ /dev/null
@@ -1,123 +0,0 @@
----
-title: Planning Your Streaming Solution in an Application Virtualization Server-Based Implementation
-description: Planning Your Streaming Solution in an Application Virtualization Server-Based Implementation
-author: dansimp
-ms.assetid: 3a57306e-5c54-4fde-8593-fe3b788f18d3
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Planning Your Streaming Solution in an Application Virtualization Server-Based Implementation
-
-
-If you want to use Application Virtualization Streaming Servers in conjunction with your Application Virtualization Management Server-based implementation, you can choose from several alternatives, taking advantage of whatever infrastructure is already in place. For example, if you already have servers in your field branch offices, you can place the Application Virtualization \\CONTENT share on those servers and then configure the clients to use that content share as their application content source. If you choose to use only Application Virtualization Management Servers—for example, because you have only a single office—the clients can stream content from that server.
-
-The supported options include using a file server, an IIS server, or an Application Virtualization Streaming Server. You could also install the Application Virtualization Streaming Server on an existing file server or IIS server. The characteristics of these different options are summarized in the following table.
-
-**Note**
-The active upgrade feature enables a new version of an application to be added to an App-V Management Server or Streaming Server without affecting users currently running the application. The App-V clients will automatically receive the latest version of the application from the App-V Management Server or Streaming Server the next time the user starts the application. Use of the RTSP(S) protocol is required for this feature.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Server Type
-
Protocol
-
Advantages
-
Disadvantages
-
Links
-
-
-
-
-
File server
-
SMB
-
-
Simple low-cost solution to configure existing file server with \CONTENT share
-
-
-
-## Related topics
-
-
-[Application Virtualization Server-Based Scenario](application-virtualization-server-based-scenario.md)
-
-[Overview of the Application Virtualization System Components](overview-of-the-application-virtualization-system-components.md)
-
-[Publishing Virtual Applications Using Application Virtualization Management Servers](publishing-virtual-applications-using-application-virtualization-management-servers.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/planning-your-streaming-solution-in-an-electronic-software-distribution-implementation.md b/mdop/appv-v4/planning-your-streaming-solution-in-an-electronic-software-distribution-implementation.md
deleted file mode 100644
index f0e61dd69e..0000000000
--- a/mdop/appv-v4/planning-your-streaming-solution-in-an-electronic-software-distribution-implementation.md
+++ /dev/null
@@ -1,111 +0,0 @@
----
-title: Planning Your Streaming Solution in an Electronic Software Distribution Implementation
-description: Planning Your Streaming Solution in an Electronic Software Distribution Implementation
-author: dansimp
-ms.assetid: bc18772a-f169-486f-adb1-7af1a31845aa
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Planning Your Streaming Solution in an Electronic Software Distribution Implementation
-
-
-If you decide to use streaming servers in conjunction with your ESD system to make application content available to your end user computers, you can choose from several alternatives, taking advantage of whatever infrastructure is already in place. For example, if your ESD system has software distribution shares on servers in your field branch offices, you can place the Application Virtualization \\CONTENT share on those servers and then configure the clients to use that content share as their application content source. The supported options include using a file server or an IIS server. You could also install the Application Virtualization Streaming Server on an existing file server or IIS server.
-
-The Application Virtualization Streaming Server provides support for the active upgrade feature in Application Virtualization. The active upgrade feature enables a new version of an application to be added to an App-V Management Server or Streaming Server without affecting users currently running the application. The App-V clients will automatically receive the latest version of the application from the App-V Management Server or Streaming Server the next time the user starts the application. Use of the RTSP(S) protocol is required for this feature. If you choose not to use the Application Virtualization Streaming Server, you will need to explicitly manage application package upgrades by using the ESD system.
-
-**Note**
-Access to the applications is controlled by means of Security Groups in Active Directory Domain Services, so you will need to plan a process for setting up a security group for each virtual application and for managing which users are added to each group. The Application Virtualization system administrator configures each streaming server to use these Active Directory groups by applying ACLs to the application directories under the CONTENT share, which controls access to the packages based on Active Directory group membership.
-
-
-
-The characteristics of the available streaming options are summarized in the following table.
-
-
-
-
-
-
-
-
-
-
-
-
Server Type
-
Protocol
-
Advantages
-
Disadvantages
-
Links
-
-
-
-
-
File server
-
SMB
-
-
Simple low-cost solution to configure existing file server with \CONTENT share
-
-
-
-## Related topics
-
-
-[How to Configure Servers for ESD-Based Deployment](how-to-configure-servers-for-esd-based-deployment.md)
-
-[Security and Protection Overview](security-and-protection-overview.md)
-
-[Publishing Virtual Applications Using Electronic Software Distribution](publishing-virtual-applications-using-electronic-software-distribution.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/prepare-computer-page--learn-more-.md b/mdop/appv-v4/prepare-computer-page--learn-more-.md
deleted file mode 100644
index ae4493a4e7..0000000000
--- a/mdop/appv-v4/prepare-computer-page--learn-more-.md
+++ /dev/null
@@ -1,45 +0,0 @@
----
-title: Prepare Computer Page (Learn More)
-description: Prepare Computer Page (Learn More)
-author: dansimp
-ms.assetid: a401ce3d-b8f7-4b3f-9be9-ecf6d8b544fd
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Prepare Computer Page (Learn More)
-
-
-Use the **Prepare Computer** to review the issues that might cause the virtual application package creation to fail, or for the package to contain unnecessary data. We strongly recommend that you resolve all potential issues before you continue. After you have fixed the conflicts, to update the information displayed, click **Refresh**. After you have resolved all potential issues, you can proceed to the next step.
-
-This page contains the following elements.
-
-**Description**
-Displays the potential conflicting applications or programs that are currently running on the computer running the App-V Sequencer.
-
-**Resolution**
-Displays the recommended action to ensure that the computer running the Sequencer has been optimized to create the virtual application package.
-
-**Refresh**
-Refreshes the information displayed in the **Description** pane. After you performed the suggested steps, click **Refresh**.
-
-## Related topics
-
-
-[Create New Package Wizard (AppV 4.6 SP1)](create-new-package-wizard---appv-46-sp1-.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/properties-tab-keep.md b/mdop/appv-v4/properties-tab-keep.md
deleted file mode 100644
index 3631579f1f..0000000000
--- a/mdop/appv-v4/properties-tab-keep.md
+++ /dev/null
@@ -1,43 +0,0 @@
----
-title: Properties Tab
-description: Properties Tab
-author: dansimp
-ms.assetid: 6ff20678-6766-4f0d-8bbb-f19b224682a1
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Properties Tab
-
-
-The **Properties** tab provides basic statistical information about a sequenced application package.
-
-## In This Section
-
-
-[About the Properties Tab](about-the-properties-tab.md)
-Provides general information about the **Properties** tab.
-
-[How to Change Package Properties](how-to-change-package-properties.md)
-Provides the procedure to change package properties using the **Properties** tab.
-
-## Related topics
-
-
-[Sequencer Console](sequencer-console.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/provider-policies-node.md b/mdop/appv-v4/provider-policies-node.md
deleted file mode 100644
index bbe803ac9f..0000000000
--- a/mdop/appv-v4/provider-policies-node.md
+++ /dev/null
@@ -1,72 +0,0 @@
----
-title: Provider Policies Node
-description: Provider Policies Node
-author: dansimp
-ms.assetid: 89b47076-7732-4128-93cc-8e6d5b671c8e
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Provider Policies Node
-
-
-The **Provider Policies** node is one level below the Application Virtualization System node in the **Scope** pane in the Application Virtualization Server Management Console. When you select this node, the **Results** pane displays a list of provider policies. Right-click the **Provider Policies** node to display a pop-up menu that contains the following elements.
-
-**New Provider Policy**
-Displays the New Provider Policy Wizard. This wizard consists of the following pages:
-
-1. Enter a name in the **Provider Policy Name** field. Select the **Manage client desktop using the Management Console** check box if you want that capability. Select one or both of the following check boxes if you want the associated functionality:
-
- - **Refresh publishing configuration when a user logs in**
-
- - **Refresh configuration every**. After selecting this option, enter a number and select the unit from the drop-down menu. Valid entries range from a minimum of **30 minutes** to a maximum of **999 days**.
-
-2. Click **Add** or **Remove** to add or remove a group assignment. Use the standard **Windows Browse** dialog box to find a user group.
-
-3. Select one of the following check boxes on the **Provider Pipeline Configuration** dialog box to enable the associated feature:
-
- - **Authentication**—Select the type of authentication from the drop-down list.
-
- - **Enforce Access Permission Settings**
-
- - **Log Usage Information**
-
- - **Licensing**—Select an enforcement scheme from the drop-down list.
-
-4. Click **Finish** to add the new provider policy.
-
-**View**
-Changes the appearance and content of the **Results** pane.
-
-**New Window from Here**
-Opens a new management console with the selected node as the root node.
-
-**Refresh**
-Refreshes the view of the server.
-
-**Export List**
-Creates a tab-delimited text file that contains the contents of the **Results** pane. This item displays a standard **File Save** dialog box where you specify the location for the text file you are creating.
-
-**Help**
-Displays the help system for the Application Virtualization Server Management Console.
-
-## Related topics
-
-
-[Server Management Console: Provider Policies Node](server-management-console-provider-policies-node.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/provider-policies-results-pane-columns.md b/mdop/appv-v4/provider-policies-results-pane-columns.md
deleted file mode 100644
index 984d407ee3..0000000000
--- a/mdop/appv-v4/provider-policies-results-pane-columns.md
+++ /dev/null
@@ -1,61 +0,0 @@
----
-title: Provider Policies Results Pane Columns
-description: Provider Policies Results Pane Columns
-author: dansimp
-ms.assetid: f9456f17-3106-4e5a-9a8c-df3af66986e1
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Provider Policies Results Pane Columns
-
-
-The **Results** pane in the Application Virtualization Server Management Console displays one column for the provider policies. If there are additional columns available, you can add and remove them.
-
-You can use the standard Microsoft Windows **Add/Remove Columns** dialog box to select which columns are displayed in the **Results** pane.
-
-To see the **Add/Remove Columns** dialog box, right-click in the **Results** pane and select **View > Add/Remove Columns** from the pop-up menu.
-
-The following table displays the column name and its contents.
-
-
-
-
-
-
-
-
-
Column
-
Contents
-
-
-
-
-
Name
-
This column displays the name of the provider policy.
-
-
-
-
-
-
-## Related topics
-
-
-[Server Management Console: Provider Policies Node](server-management-console-provider-policies-node.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/provider-policies-results-pane.md b/mdop/appv-v4/provider-policies-results-pane.md
deleted file mode 100644
index efb2984428..0000000000
--- a/mdop/appv-v4/provider-policies-results-pane.md
+++ /dev/null
@@ -1,73 +0,0 @@
----
-title: Provider Policies Results Pane
-description: Provider Policies Results Pane
-author: dansimp
-ms.assetid: 17ea0836-bfb5-4966-8778-155444d81e64
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Provider Policies Results Pane
-
-
-The **Provider Policies Results** pane in the Application Virtualization Server Management Console displays a list of the available provider policies.
-
-Right-click any provider policy to display the following elements.
-
-**Delete**
-This menu item enables you to delete a provider policy from the **Results** pane.
-
-**Rename**
-This menu item enables you to change the name of a provider policy in the **Results** pane.
-
-**Properties**
-This menu item displays the **Properties** dialog box for the selected provider policy. The **Properties** dialog box has the following tabs:
-
-- **General**—Enables you to select the **Manage client desktop using the** **Management Console** check box if you want to centrally manage shortcuts on the client desktops from the Application Virtualization Server Management Console. If you choose to manage shortcuts from the console, you can select check boxes to refresh the desktop every time a user logs in and at intervals you specify.
-
-- **Group Assignment**—Enables you to add and remove user groups assigned to the provider policy.
-
-- **Provider Pipeline**—Enables you to specify the authentication required.
-
- - Select the desired check boxes for **Enforce Access Permission Settings**, **Log Usage Information**, and **Licensing**. If you select the **Licensing** check box, select **Audit License Usage Only** or **Enforce License Policies** from the drop-down list. The first option monitors license usage, while the second option strictly enforces your licensing policy. Click **Finish**, and then read the prompt and click **OK** to continue.
-
-**Help**
-Displays the help system for the Application Virtualization Server Management Console.
-
-Right-click anywhere in the **Results** pane, except on a provider policy, to display a pop-up menu that contains the following elements.
-
-**Refresh**
-Select this menu item to refresh the view of the provider policies.
-
-**Export List**
-With this menu item, you can create a tab-delimited text file that contains the contents of the **Results** pane. This item displays a standard **File Save** dialog box where you specify the location for the text file you are creating.
-
-**View**
-This menu item lets you change the appearance and content of the **Results** pane.
-
-**Arrange/Line Up Icons**
-These menu items can be used to change how the icons are displayed in the **Results** pane.
-
-**Help**
-Displays the help system of the Application Virtualization Server Management Console.
-
-## Related topics
-
-
-[Server Management Console: Provider Policies Node](server-management-console-provider-policies-node.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/publish-app.md b/mdop/appv-v4/publish-app.md
deleted file mode 100644
index 3248daad68..0000000000
--- a/mdop/appv-v4/publish-app.md
+++ /dev/null
@@ -1,110 +0,0 @@
----
-title: PUBLISH APP
-description: PUBLISH APP
-author: dansimp
-ms.assetid: f25f06a8-ca23-435b-a0c2-16a5f39b6b97
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# PUBLISH APP
-
-
-Publishes an application shortcut to the user's Start menu, desktop, or other specified location.
-
-`SFTMIME PUBLISH APP:application {/DESKTOP | /START | /TARGET target-path} [/ICON icon-pathname] [/DISPLAY display-name] [/ARGS command-args...] [/LOG log-pathname | /CONSOLE | /GUI]`
-
-
-
-
-
-
-
-
-
Parameter
-
Description
-
-
-
-
-
APPLICATION:<application>
-
The name and version (optional) of the application.
-
-
-
/DESKTOP
-
Publishes a shortcut to the user's desktop.
-
-
-
/START
-
Publishes a shortcut to the Application Virtualization Applications folder in the Programs folder of the Start menu.
-
-
-
/TARGET <target-path>
-
The absolute path where the shortcut should be published.
-
-
-
/ICON <icon-pathname>
-
The path or URL for the icon file.
-
-
-
/DISPLAY <display-name>
-
The display name for the shortcut.
-
-
-
/ARGS <command-args>
-
Parameters to be passed to the application.
-
-
-
/LOG
-
If specified, output is logged to the specified path name.
-
-
-
/CONSOLE
-
If specified, output is presented in the active console window (default).
-
-
-
/GUI
-
If specified, output is presented in a Windows dialog box.
-
-
-
-
-
-
-For version 4.6, the following option has been added.
-
-
-
-
-
-
-
-
-
/LOGU
-
If specified, output is logged to the specified path name in UNICODE format.
User-visible and user-friendly name for the package.
-
-
-
/MANIFEST <manifest-path>
-
The path or URL of the manifest file that lists the applications included in the package and all of their publishing information.
-
-
-
/GLOBAL
-
If present, the package will be available for all users on this computer.
-
-
-
/LOG
-
If specified, output is logged to the specified path name.
-
-
-
/CONSOLE
-
If specified, output is presented in the active console window (default).
-
-
-
/GUI
-
If specified, output is presented in a Windows dialog box.
-
-
-
-
-
-
-For version 4.6, the following option has been added.
-
-
-
-
-
-
-
-
-
/LOGU
-
If specified, output is logged to the specified path name in UNICODE format.
-
-
-
-
-
-
-**Important**
-The package must already have been added to the Application Virtualization Client, and the manifest file is required.
-
-To use the **GLOBAL** parameter, the PUBLISH PACKAGE command must be run as local Administrator; otherwise, only **ManageTypes** and **PublishShortcut** permissions are needed.
-
-Publishing without the **GLOBAL** parameter grants the user access to the applications in the package and publishes the file types and shortcuts listed in the manifest to the user’s profile.
-
-Publishing with the **GLOBAL** parameter adds the file types and shortcuts listed in the manifest to the “All Users” profile.
-
-If the package is not global before the call and the **GLOBAL** parameter is used, the package is made global and available to all users.
-
-
-
-## Related topics
-
-
-[SFTMIME Command Reference](sftmime--command-reference.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/publishing-servers-node.md b/mdop/appv-v4/publishing-servers-node.md
deleted file mode 100644
index 980c07416d..0000000000
--- a/mdop/appv-v4/publishing-servers-node.md
+++ /dev/null
@@ -1,70 +0,0 @@
----
-title: Publishing Servers Node
-description: Publishing Servers Node
-author: dansimp
-ms.assetid: b5823c6c-15bc-4e8d-aeeb-acc366ffedd1
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Publishing Servers Node
-
-
-The **Publishing Servers** node is one level below the **Application Virtualization** node in the **Scope** pane of the Application Virtualization Client Management Console. When you select this node, the **Results** pane displays a list of publishing servers.
-
-Right-click the **Publishing Servers** node to display a pop-up menu that contains the following elements.
-
-**New Server**
-This menu item displays the New Server Wizard. This wizard consists of two pages:
-
-1. Enter a server display name and server type:
-
- - **Display Name**—Enter a name that you want displayed for the server. This field is blank by default.
-
- - **Type**—Choose the server type from the drop-down list of server types.
-
-2. Specify the connection settings for the server:
-
- - **Host Name**—Enter the name or IP address for the server.
-
- - **Port**—Enter a numeric value that corresponds to the port number. The default value is 554 if the server type is "Application Virtualization Server" and 80 if the server type is "Standard HTTP Server."
-
- - **Path**—This field defaults to "/" and is read-only when the server type is "Application Virtualization Server" or “Enhanced Security Application Virtualization Server”. When the server type is “Standard HTTP Server” or “Enhanced Security HTTP Server”, the **Path** field is also editable.
-
-**New Window from Here**
-Select this menu item to open a new management console with the selected node as the root node.
-
-**Export List**
-You can use this menu item to create a tab-delimited text file that contains the contents of the **Results** pane. This item displays a standard **File Save** dialog box where you specify the location for the text file you are creating.
-
-**View**
-This pop-up list of menu items enables you to change the appearance and content of the **Results** pane.
-
-**Refresh**
-Select this item to refresh the management console.
-
-**Help**
-This item displays the help system for the management console.
-
-## Related topics
-
-
-[Publishing Servers Results Pane](publishing-servers-results-pane.md)
-
-[Publishing Servers Results Pane Columns](publishing-servers-results-pane-columns.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/publishing-servers-results-pane-columns.md b/mdop/appv-v4/publishing-servers-results-pane-columns.md
deleted file mode 100644
index 42862c4a61..0000000000
--- a/mdop/appv-v4/publishing-servers-results-pane-columns.md
+++ /dev/null
@@ -1,75 +0,0 @@
----
-title: Publishing Servers Results Pane Columns
-description: Publishing Servers Results Pane Columns
-author: dansimp
-ms.assetid: ad875715-50b3-4881-a6b3-586238d12527
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Publishing Servers Results Pane Columns
-
-
-The **Publishing Servers Results** pane can display a variety of columns. **Name**, **URL**, and **Next Refresh** are shown by default.
-
-**Note**
-You can add or remove a column simply by right-clicking in the **Results** pane, selecting **View**, then selecting **Add/Remove Columns**.
-
-
-
-The list can be sorted by any of the columns. Columns that contain dates and times are sorted in chronological order, not alphabetical. For columns that contain a mix of dates and times and text (for example, **Next Refresh**), dates and times are considered to come before any other text.
-
-The available column names contain the following elements.
-
-**Name**
-The display name for the server.
-
-**URL**
-The protocol, server name, server port, and path combined into a URL.
-
-**Next User Refresh**
-The next time a refresh is scheduled for the current user. Displays the time if periodic refreshes are set up. Displays **On Login** if the server is set to refresh only on login. Displays **Manual** if automatic refresh is not enabled.
-
-**Default Refresh Policy**
-Displays **Manual**, **On Login**, or **Periodic** to describe how the server is configured.
-
-**Host**
-The name or IP address for the server.
-
-**Type**
-Displays **HTTP** or **Virtual Application** to indicate the server type.
-
-**Port**
-The port on the server to be used.
-
-**Path**
-The path on the server (generally just "/" for Application Virtualization Servers).
-
-**Last User Refresh**
-The time the last refresh occurred for the current user.
-
-**Last System Refresh**
-The last time a refresh happened from this server for any user.
-
-## Related topics
-
-
-[Publishing Servers Node](publishing-servers-node.md)
-
-[Publishing Servers Results Pane](publishing-servers-results-pane.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/publishing-servers-results-pane.md b/mdop/appv-v4/publishing-servers-results-pane.md
deleted file mode 100644
index 27745a94ba..0000000000
--- a/mdop/appv-v4/publishing-servers-results-pane.md
+++ /dev/null
@@ -1,77 +0,0 @@
----
-title: Publishing Servers Results Pane
-description: Publishing Servers Results Pane
-author: dansimp
-ms.assetid: ee0662e8-9623-4a7c-b6dc-657fa3f56161
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Publishing Servers Results Pane
-
-
-The **Publishing Servers** **Results** pane is one level below the **System** pane in the Application Virtualization Client Management Console, and it displays a list of the available application publishing servers.
-
-To display specific options for the application publishing servers, right-click any server to display a pop-up menu that contains the following elements.
-
-**Refresh Server**
-Refreshes the application and file type associations from the selected application publishing server.
-
-**Delete**
-Deletes the server from the list.
-
-**Refresh**
-Refreshes the contents of the **Results** pane.
-
-**Properties**
-- Click the **General** tab, where you can change the server name, select a type from the drop-down list of server types, and specify the host name and port. When the server type is Standard HTTP Server or Enhanced Security HTTP Server, the **Path** field is also editable.
-
-- Click the **Refresh** tab, where the **Refresh publishing on user login** check box is selected by default. To change the refresh rate, select the **Refresh publishing every** check box and enter a number that represents the frequency in the field. Then select **Minutes**, **Hours**, **Days** from the drop-down menu. (The minimum amount of time you can enter is 30 minutes.)
-
-**Help**
-Displays the help system for the management console.
-
-To display general options for the **Result** pane, right-click anywhere in the **Result** pane to display a pop-up menu that contains the following elements.
-
-**New Server**
-- On page one of the wizard, enter the name of the server in the **Display Name** field and select the server type from the **Type** drop-down list. You can choose **Application Virtualization Server**, **Enhanced Security Application Virtualization Server**, **Standard HTTP Server**, or **Enhanced Security HTTP Server** from the drop-down list of server types.
-
-- On page two of the wizard, type the appropriate information into the **Host Name** and **Port** fields. The **Path** field is not editable for Application Virtualization Servers. You must enter a path for Standard HTTP Server or Enhanced Security HTTP Server.
-
-**Refresh**
-Refreshes the contents of the **Results** pane.
-
-**Export List**
-Can be used to create a tab-delimited text file that contains the contents of the **Results** pane. This item displays a standard **File Save** dialog box where you specify the location for the text file you are creating.
-
-**View**
-Enables you to change the appearance and content of the **Results** pane.
-
-**Arrange/Line Up Icons**
-Can be used to change how the icons are displayed in the **Results** pane.
-
-**Help**
-Displays the help system for the management console.
-
-## Related topics
-
-
-[Publishing Servers Node](publishing-servers-node.md)
-
-[Publishing Servers Results Pane Columns](publishing-servers-results-pane-columns.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/publishing-virtual-applications-using-application-virtualization-management-servers.md b/mdop/appv-v4/publishing-virtual-applications-using-application-virtualization-management-servers.md
deleted file mode 100644
index 53570b3732..0000000000
--- a/mdop/appv-v4/publishing-virtual-applications-using-application-virtualization-management-servers.md
+++ /dev/null
@@ -1,52 +0,0 @@
----
-title: Publishing Virtual Applications Using Application Virtualization Management Servers
-description: Publishing Virtual Applications Using Application Virtualization Management Servers
-author: dansimp
-ms.assetid: f3d79284-3f82-4ca3-b741-1a80b61490da
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Publishing Virtual Applications Using Application Virtualization Management Servers
-
-
-In an Application Virtualization Server-based deployment, virtual application packages that have been sequenced, tested, and found deployable are copied to the main CONTENT share to be used by the Application Virtualization Management Server. After the packages are imported on the Application Virtualization Management Server, they can be published to the end users.
-
-**Note**
-The CONTENT share should be located on the server’s attached disk storage. Using a network storage device such as a SAN or a DFS share should be considered carefully because of the network impact.
-
-
-
-Applications are provisioned to Active Directory groups. Typically, the Application Virtualization administrator will create Active Directory groups for each virtual application to be published and then add the appropriate users to those groups. When the users log on to their workstations, the Application Virtualization Client, by default, performs a publishing refresh using the credentials of the logged on user. The user can then start applications from wherever the shortcuts have been placed. The Application Virtualization administrator determines where and how many shortcuts are located on the client system during the sequencing of the application.
-
-**Note**
-A *publishing refresh* is a call to the Application Virtualization Server that is defined on the Application Virtualization Client, to determine which virtual application shortcuts are sent to the client for use by the end user.
-
-
-
-## Related topics
-
-
-[Application Virtualization Server-Based Scenario](application-virtualization-server-based-scenario.md)
-
-[How to Publish a Virtual Application on the Client](how-to-publish-a-virtual-application-on-the-client.md)
-
-[Overview of the Application Virtualization System Components](overview-of-the-application-virtualization-system-components.md)
-
-[Planning Your Streaming Solution in an Application Virtualization Server-Based Implementation](planning-your-streaming-solution-in-an-application-virtualization-server-based-implementation.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/publishing-virtual-applications-using-electronic-software-distribution.md b/mdop/appv-v4/publishing-virtual-applications-using-electronic-software-distribution.md
deleted file mode 100644
index 5a56209bc5..0000000000
--- a/mdop/appv-v4/publishing-virtual-applications-using-electronic-software-distribution.md
+++ /dev/null
@@ -1,46 +0,0 @@
----
-title: Publishing Virtual Applications Using Electronic Software Distribution
-description: Publishing Virtual Applications Using Electronic Software Distribution
-author: dansimp
-ms.assetid: 295fbc1d-ed1c-43b4-aeee-0df384d4e630
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Publishing Virtual Applications Using Electronic Software Distribution
-
-
-An electronic software distribution (ESD) system is designed to efficiently move software to many different computers over slow or fast network connections. With Application Virtualization, using an ESD system, you can use one of the following methods to distribute your virtual application packages:
-
-- Configure your ESD system to distribute the packages directly to each client computer by using the Windows Installer version of the package generated by the Application Virtualization Sequencer. The Windows Installer file contains the icons, package definition information, and the content, and when you use Windows Installer, it publishes the icons to the Windows desktop and Start menu and loads the package content into the Application Virtualization Client cache. The user can immediately start using the applications without any further setup requirements. Upgrading a package to a newer version is accomplished by using Windows Installer to uninstall the package.msi file and then to install the new version.
-
-- Place the package content on a software distribution point or Application Virtualization Streaming Server that is readily accessible to the client computers over a network connection with good bandwidth, such as a LAN. For example, you might use the existing ESD system distribution point computers in each branch office. Using command-line parameters to define the streaming source from which clients will stream the virtual application package, the ESD system would deploy the Windows Installer version of the package to each client. The ESD system could also be used to copy the SFT file that contains the package content to the file share on all streaming servers. Upgrading a package to a newer version is accomplished by using Windows Installer to uninstall the package.msi file and then install the new version.
-
-- As an alternative to using the self-contained Windows Installer file in either of the preceding modes to deploy the packages, you can control the deployment in a much more detailed way by using the Application Virtualization command-line language SFTMIME. This provides many commands to control all aspects of managing the packages. While SFTMIME is powerful, it is also complex, so administrators should plan to create all commands as scripts and thoroughly test them in a test environment prior to production use. For more information about available SFTMIME commands, see [SFTMIME Command Reference](sftmime--command-reference.md).
-
-## Related topics
-
-
-[Electronic Software Distribution-Based Scenario](electronic-software-distribution-based-scenario.md)
-
-[Planning for Application Virtualization System Deployment](planning-for-application-virtualization-system-deployment.md)
-
-[Planning Your Streaming Solution in an Electronic Software Distribution Implementation](planning-your-streaming-solution-in-an-electronic-software-distribution-implementation.md)
-
-[SFTMIME Command Reference](sftmime--command-reference.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/query-obj.md b/mdop/appv-v4/query-obj.md
deleted file mode 100644
index a137e1cbda..0000000000
--- a/mdop/appv-v4/query-obj.md
+++ /dev/null
@@ -1,142 +0,0 @@
----
-title: QUERY OBJ
-description: QUERY OBJ
-author: dansimp
-ms.assetid: 55abf0d1-c779-4172-8357-552ab010933b
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# QUERY OBJ
-
-
-Returns a tab-delimited list of current applications, packages, file type associations, or publishing servers.
-
-`SFTMIME QUERY OBJ:{APP|PACKAGE|TYPE|SERVER} [/SHORT] [/GLOBAL] [/LOG log-pathname | /CONSOLE ]`
-
-
-
-
-
-
-
-
-
Parameter
-
Description
-
-
-
-
-
APP
-
Returns a list of applications.
-
-
-
PACKAGE
-
Returns a list of packages.
-
-
-
TYPE
-
Returns a list of file type associations.
-
-
-
SERVER
-
Returns a list of publishing servers.
-
-
-
/SHORT
-
Without displaying the full properties of each, returns a list of application names, packages, associations, or server names.
-
-
-
/GLOBAL
-
For applications, returns all known applications instead of only the ones the current user has access to. For packages, returns all known packages instead of only the ones the current user has access to. For associations, returns only associations that apply to all users, not user-specific ones. Not valid for servers.
-
-
-
/LOG
-
If specified, output is logged to the specified path name.
-
-
-
/CONSOLE
-
If specified, output is presented in the active console window (default).
-
-
-
-
-
-
-For version 4.6, the following option has been added.
-
-
-
-
-
-
-
-
-
/LOGU
-
If specified, output is logged to the specified path name in UNICODE format.
-
-
-
-
-
-
-**Note**
-In version 4.6, a new column has been added to the output of SFTMIME QUERY OBJ:APP \[/GLOBAL\]. The last column of the output is a numeric value that indicates whether an application is published or not.
-
-PUBLISHED=1 means the application was published by a Publishing Server refresh, by installing the application by using a Windows Installer file (.MSI), or by running an SFTMIME ADD PACKAGE, CONFIGURE PACKAGE or PUBLISH PACKAGE command by using a package manifest.
-
-PUBLISHED=0 means the application has not been published or it is no longer published as a result of performing a Clear operation or running an SFTMIME UNPUBLISH command.
-
-If you use the /GLOBAL parameter, the PUBLISHED state will be 1 for applications that were published globally and 0 for those applications that were published under user contexts. Without the /GLOBAL parameter, a PUBLISHED state of 1 is returned for applications published in the context of the user running the command, and a state of 0 is returned for those applications that are published globally.
-
-
-
-The SFTMIME QUERY OBJ command can be used to query for information on all of the objects shown above—applications, packages, file type associations, and servers. To show how you might use the SFTMIME QUERY OBJ command in your normal operations tasks, the following example demonstrates the process you would follow if you wanted to set the OVERRIDEURL parameter value for a specific package to specify a new path to the package content.
-
-1. To find the package that you want to configure, run the following command:
-
- `SFTMIME QUERY OBJ:PACKAGE`
-
- This command returns each discovered package name as a GUID in the first column of output—for example, {AF78ABE1-57D4-4297-89DE-C308684AEDD6}.
-
-2. To set the OVERRIDEURL parameter value, you use the SFTMIME [CONFIGURE PACKAGE](configure-package.md) command. For example, to set the OVERRIDEURL value for this package to a value of *\\\\server\\share\\mypackage.sft*, use the SFTMIME CONFIGURE PACKAGE command and give it the selected package GUID from the output of the SFTMIME QUERY OBJ command in step 1, followed by the OVERRIDEURL parameter and its new value, as follows:
-
- `SFTMIME CONFIGURE PACKAGE:"{AF78ABE1-57D4-4297-89DE-C308684AEDD6}" /OVERRIDEURL "\\\\server\\share\\mypackage.sft "`
-
-For version 4.6 SP2, the following option has been added.
-
-
-
-
-
-
-
-
-
/NO-UPDATE-FTA-SHORTCUT
-
Indicates the current state of the /NO-UPDATE-FTA-SHORTCUT flag.
The name and version (optional) of the application.
-
-
-
/LOG
-
If specified, output is logged to the specified path name.
-
-
-
/CONSOLE
-
If specified, output is presented in the active console window (default).
-
-
-
/GUI
-
If specified, output is presented in a Windows dialog box.
-
-
-
-
-
-
-For version 4.6, the following option has been added.
-
-
-
-
-
-
-
-
-
/LOGU
-
If specified, output is logged to the specified path name in UNICODE format.
-
-
-
-
-
-
-## Related topics
-
-
-[SFTMIME Command Reference](sftmime--command-reference.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/reports-node.md b/mdop/appv-v4/reports-node.md
deleted file mode 100644
index d691eb3d1c..0000000000
--- a/mdop/appv-v4/reports-node.md
+++ /dev/null
@@ -1,77 +0,0 @@
----
-title: Reports Node
-description: Reports Node
-author: dansimp
-ms.assetid: b7fdc52d-f112-4a65-af25-134398810e9b
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Reports Node
-
-
-The **Reports** node is one level below the Application Virtualization System node in the **Scope** pane in the Application Virtualization Server Management Console. When you select this node, the **Results** pane displays a list of reports. Right-click the node to display a pop-up menu that contains the following elements.
-
-**New Report**
-Displays the New Report Wizard. The wizard has several pages. Depending on which report you select, the remaining pages in the wizard change for the requirements of that report type. Scan the following list of pages to find the pages that refer to your report:
-
-- **Report Name**—Enables you to select a report type from the **Report Type** drop-down list. For more information, see [Application Virtualization Report Types](application-virtualization-report-types.md).
-
-- **Report Period**—Enables you to select a radio button to specify the frequency for running the report.
-
-- **Server**—Enables you to select the **Server**, **Server Group**, or **Enterprise** radio button, and to select the server from the **Server** field and the server group from the **Server Group** drop-down list.
-
-- **Application**—Enables you to select an application from the drop-down list of available applications.
-
-- When prompted, click **Finish** to add the report.
-
-**View**
-Changes the appearance and content of the **Results** pane.
-
-**New Window from Here**
-Opens a new management console with the selected node as the root node.
-
-**Export List**
-Creates a tab-delimited text file that contains the contents of the **Results** pane. This item displays a standard **File Save** dialog box where you specify the location for the text file you are creating.
-
-**Help**
-Displays the help system for the Application Virtualization Server Management Console.
-
-Right-click any report displayed under the **Reports** node to display a pop-up menu that contains the following elements.
-
-**New Window from Here**
-Opens a new management console with the selected node as the root node.
-
-**Delete**
-Deletes the report from the **Reports** node.
-
-**Rename**
-Highlights the report name so that it becomes editable text.
-
-**Help**
-Displays the help system for the Application Virtualization Server Management Console.
-
-## Related topics
-
-
-[Application Virtualization Report Types](application-virtualization-report-types.md)
-
-[How to Manage Reports in the Server Management Console](how-to-manage-reports-in-the-server-management-console.md)
-
-[Server Management Console: Reports Node](server-management-console-reports-node.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/reports-results-pane-columns.md b/mdop/appv-v4/reports-results-pane-columns.md
deleted file mode 100644
index a7abb0ae55..0000000000
--- a/mdop/appv-v4/reports-results-pane-columns.md
+++ /dev/null
@@ -1,73 +0,0 @@
----
-title: Reports Results Pane Columns
-description: Reports Results Pane Columns
-author: dansimp
-ms.assetid: 907360ca-6a55-4e42-88d2-db1a24cd2a28
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Reports Results Pane Columns
-
-
-The **Results** pane in the Application Virtualization Server Management Console displays three columns for reports. If there are additional columns available, you can add and remove them.
-
-You can use the standard Windows **Add/Remove Columns** dialog box to select which columns are displayed in the **Results** pane.
-
-To see the **Add/Remove Columns** dialog box, right-click in the **Results** pane and select **View > Add/Remove Columns** from the pop-up menu.
-
-The following table displays the column name and its contents.
-
-
-
-
-
-
-
-
-
Column
-
Contents
-
-
-
-
-
Report Name
-
This column displays the report name.
-
-
-
Report Type
-
This column displays the report type.
-
-
-
Period Type
-
This column displays the frequency with which Application Virtualization generates the report.
-
-
-
-
-
-
-## Related topics
-
-
-[Application Virtualization Report Types](application-virtualization-report-types.md)
-
-[How to Manage Reports in the Server Management Console](how-to-manage-reports-in-the-server-management-console.md)
-
-[Server Management Console: Reports Node](server-management-console-reports-node.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/reports-results-pane.md b/mdop/appv-v4/reports-results-pane.md
deleted file mode 100644
index 77e23a88cc..0000000000
--- a/mdop/appv-v4/reports-results-pane.md
+++ /dev/null
@@ -1,69 +0,0 @@
----
-title: Reports Results Pane
-description: Reports Results Pane
-author: dansimp
-ms.assetid: 66beac62-fa55-4ab9-ac19-b9e1772e2d20
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Reports Results Pane
-
-
-The **Reports Results** pane in the Application Virtualization Server Management Console displays a list of the available reports.
-
-To display specific options for reports, right-click any report to view the following elements.
-
-**Run Report**
-Runs the selected report regardless of the specified value in the **Report Period** field.
-
-**New Window From Here**
-Opens a new management console with the selected node as the root node.
-
-**Delete**
-Deletes the selected report from the **Results** pane.
-
-**Rename**
-Changes the name of the selected report.
-
-**Help**
-Displays the help system for the Application Virtualization Server Management Console.
-
-Right-click anywhere in the **Results** pane to display a pop-up menu that contains the following elements.
-
-**Export List**
-Creates a tab-delimited text file that contains the contents of the **Results** pane. This item displays a standard **File Save** dialog box where you specify the location for the text file you are creating.
-
-**View**
-Changes the appearance and content of the **Results** pane.
-
-**Arrange/Line Up Icons**
-These menu items can be used to change how the icons are displayed in the **Results** pane.
-
-**Help**
-Displays the help system for the Application Virtualization Server Management Console.
-
-## Related topics
-
-
-[Application Virtualization Report Types](application-virtualization-report-types.md)
-
-[How to Manage Reports in the Server Management Console](how-to-manage-reports-in-the-server-management-console.md)
-
-[Server Management Console: Reports Node](server-management-console-reports-node.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/restart-task-failure-dialog-box--app-v-46-sp1-.md b/mdop/appv-v4/restart-task-failure-dialog-box--app-v-46-sp1-.md
deleted file mode 100644
index 2a2fbe0e8d..0000000000
--- a/mdop/appv-v4/restart-task-failure-dialog-box--app-v-46-sp1-.md
+++ /dev/null
@@ -1,36 +0,0 @@
----
-title: Restart Task Failure Dialog Box (App-V 4.6 SP1)
-description: Restart Task Failure Dialog Box (App-V 4.6 SP1)
-author: dansimp
-ms.assetid: 1933fe71-8aa0-4e43-b6f7-060050001edd
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Restart Task Failure Dialog Box (App-V 4.6 SP1)
-
-
-A restart task associated with the application that you are trying sequence failed.
-
-Complete the installation and then manually restart the computer running Microsoft Application Virtualization (App-V) Sequencer.
-
-## Related topics
-
-
-[Dialog Boxes (AppV 4.6 SP1)](dialog-boxes--appv-46-sp1-.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/run-each-program-page-app-v-46-sp1.md b/mdop/appv-v4/run-each-program-page-app-v-46-sp1.md
deleted file mode 100644
index 2a93fe0947..0000000000
--- a/mdop/appv-v4/run-each-program-page-app-v-46-sp1.md
+++ /dev/null
@@ -1,42 +0,0 @@
----
-title: Run Each Program Page
-description: Run Each Program Page
-author: dansimp
-ms.assetid: 4f09a64e-9545-47aa-bc43-fda0089f7adb
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Run Each Program Page
-
-
-Use the **Run Each Program** page to run each program to complete any configuration tasks after installation. For example, this step helps configure any associated application license agreements. Select the application in the **Application Pane** and select one of the following options.
-
-This page contains the following elements:
-
-**Run Selected**
-Runs only the selected applications.
-
-**Run All**
-Runs all applications contained in the package.
-
-## Related topics
-
-
-[Sequencer Wizard - Package Accelerator (AppV 4.6 SP1)](sequencer-wizard---package-accelerator--appv-46-sp1-.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/security-and-protection-overview.md b/mdop/appv-v4/security-and-protection-overview.md
deleted file mode 100644
index 99c0632836..0000000000
--- a/mdop/appv-v4/security-and-protection-overview.md
+++ /dev/null
@@ -1,76 +0,0 @@
----
-title: Security and Protection Overview
-description: Security and Protection Overview
-author: dansimp
-ms.assetid: a43e1c53-7936-4d48-a110-0be26c8e9d97
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Security and Protection Overview
-
-
-Microsoft Application Virtualization 4.5 provides the following enhanced security features to help you plan and implement a more secure deployment strategy:
-
-- Application Virtualization now supports Transport Layer Security (TLS) using X.509 V3 certificates. Provided that a server certificate has been provisioned to the planned Application Virtualization Management or Streaming Server, the installation will default to secure, using the RTSPS protocol over port 322. Using RTSPS ensures that communication between the Application Virtualization Servers and the Application Virtualization Clients is signed and encrypted. If no certificate is assigned to the server during the Application Virtualization Server installation, the communication will be set to RTSP over port 554.
-
- **Security Note:**
-
- To help provide a secure setup of the server, you must make sure that RTSP ports are disabled even if you have all packages configured to use RTSPS.
-
- If you add security certificates to the server after installing the server, the server might not detect the certificates. To help ensure security certificate detection, restart the server after adding the certificates.
-
-- The client must be configured to use the same protocol and port as the server, or it will not be able to communicate with the server. The client must also trust the issuer of the certificate and ships with several of the primary providers in its Trusted Root Store. You can use self-signed certificates, but you will need to update the clients.
-
-- When configuring IIS servers to use the HTTPS protocol for streaming, you will need to set up Secure Sockets Layer (SSL) on the IIS server and provision the certificate for the server. The clients will also need to be configured to trust the root certification authority that issued the server certificate.
-
-- Kerberos authentication has been added to Microsoft Application Virtualization as the default authentication mechanism. Earlier versions relied upon NTLM V2 for authentication. Using Kerberos Authentication strengthens the security of the communication between the client and the Application Virtualization server. When a connection has been initiated from the client, the Application Virtualization Server verifies the session ticket with the Key Distribution Center (KDC).
-
-- Because of the support for using server certificates and using the RTSPS or HTTPS protocols, you can now support clients outside of the corporate network. This can help eliminate the need for mobile users to set up a secure connection to the corporate network (VPN, RAS, and so on) prior to launching Application Virtualization provisioned applications.
-
-Other important security considerations to consider include the following:
-
-- Always keep servers fully updated and protected.
-
-- To add a certificate to enable more secure communications to the Application Virtualization Management Server, the following criteria must be met:
-
- - The user who will be adding the certificate must be an administrator on the server where the certificate store is located.
-
- - The server service must be started.
-
- - Port 139 on the Management Server must be open to the Web Service server’s IP.
-
-- Use access control lists (ACLs) to ensure that the application packages and all package files are protected and cannot be tampered. ACLs restrict access to the location or folder where you store the packages, allowing access only to certain accounts.
-
-- Make sure that the channel between the Application Virtualization Management Server and the database is secured—for example, by using IPsec.
-
-- If packages are stored on a SAN or NAS, ensure the connection between the central storage device and the Application Virtualization Servers is protected.
-
-- All communication channels to the client should be protected—including connections to the publishing server, the Application Virtualization Server, and the path to the OSD and ICO files—by using a protocol such as HTTPS or IPsec.
-
-- Client permissions should be configured to help ensure that packages cannot be tampered with by users. It is especially important that you do not grant users permission to add or update packages on systems, such as Remote Desktop Session Host (RD Session Host) servers, that are shared with multiple users.
-
-- Kerberos authentication must be permitted across domain or forest environments for the Server Management Console to work correctly.
-
-- This release of the software does not support hosting a Kerberos-based RTSP server and a Microsoft NTLM-only-based IIS server on the same computer. To host an RTSP server and an IIS server on the same computer, remove the SPN from the IIS server and use NTLM authentication.
-
-## Related topics
-
-
-[Planning for Application Virtualization System Deployment](planning-for-application-virtualization-system-deployment.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/select-files-page.md b/mdop/appv-v4/select-files-page.md
deleted file mode 100644
index f68466b525..0000000000
--- a/mdop/appv-v4/select-files-page.md
+++ /dev/null
@@ -1,39 +0,0 @@
----
-title: Select Files Page
-description: Select Files Page
-author: dansimp
-ms.assetid: 6d1524ca-6306-4a28-b65f-3ded9d487e75
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Select Files Page
-
-
-Use the **Select Files** page to review the files that will be saved with the Package Accelerator. Some of these files are displayed because they were not located on the specified media or on the local computer. In some scenarios the displayed files should be saved with the Package Accelerator so that the virtual application package can be fully recreated when the Package Accelerator is applied.
-
-This page contains the following elements:
-
-**Select Files Pane**
-Displays a list of the files that were discovered in the Package Accelerator. Carefully review the files, and clear any file that should be removed from the Package Accelerator. Select only files that are required by the application to run successfully.
-
-## Related topics
-
-
-[Create Package Accelerator Wizard (AppV 4.6 SP1)](create-package-accelerator-wizard--appv-46-sp1-.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/select-guidance-page--package-accelerators-.md b/mdop/appv-v4/select-guidance-page--package-accelerators-.md
deleted file mode 100644
index 387de4bfaf..0000000000
--- a/mdop/appv-v4/select-guidance-page--package-accelerators-.md
+++ /dev/null
@@ -1,39 +0,0 @@
----
-title: Select Guidance Page (Package Accelerators)
-description: Select Guidance Page (Package Accelerators)
-author: dansimp
-ms.assetid: 608b8823-6eac-40c0-a6dc-2f0bfc0d42a1
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Select Guidance Page (Package Accelerators)
-
-
-Use the **Select Guidance** page to specify a file that contains prescriptive guidance about how to use the Package Accelerator to create a new virtual application package. The file you select must be in rich text (.rtf) (recommended) or text (.txt) format. You should provide detailed information about all the necessary instructions for the Package Accelerator to create a virtual application package. For example, if you are performing a media installation, you can include information about how to extract files from any self-extracting executable programs. You should also provide information about all the dependent packages or any applications that must be installed for the package to run on target computers.
-
-This page contains the following elements:
-
-**Browse**
-Click **Browse** to specify the file that contains information about how to apply the Package Accelerator.
-
-## Related topics
-
-
-[Create Package Accelerator Wizard (AppV 4.6 SP1)](create-package-accelerator-wizard--appv-46-sp1-.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/select-installation-files-page-app-v-46-sp1.md b/mdop/appv-v4/select-installation-files-page-app-v-46-sp1.md
deleted file mode 100644
index 08bd4bf267..0000000000
--- a/mdop/appv-v4/select-installation-files-page-app-v-46-sp1.md
+++ /dev/null
@@ -1,47 +0,0 @@
----
-title: Select Installation Files Page
-description: Select Installation Files Page
-author: dansimp
-ms.assetid: 4c8cd49e-ba39-4918-9863-5b3c315d14a5
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Select Installation Files Page
-
-
-Use the **Select Installation Files** page to select installation files that the selected Package Accelerator requires. The installation files you specify should be located on the computer running the App-V Sequencer. The required installation files are also displayed on this page.
-
-This page contains the following elements:
-
-**Browse**
-Click **Browse** to specify the directory that contains required installation files for the selected Package Accelerator to create the virtual application package. The directory should be located on the computer running the Sequencer. You can specify installation files of the following types of media and format:
-
-- Compressed files
-
-- Windows Installer files
-
-- .cab files
-
-- Local files and directories
-
-## Related topics
-
-
-[Sequencer Wizard - Package Accelerator (AppV 4.6 SP1)](sequencer-wizard---package-accelerator--appv-46-sp1-.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/select-installer-page--learn-more-.md b/mdop/appv-v4/select-installer-page--learn-more-.md
deleted file mode 100644
index 6a57a0227a..0000000000
--- a/mdop/appv-v4/select-installer-page--learn-more-.md
+++ /dev/null
@@ -1,42 +0,0 @@
----
-title: Select Installer Page (Learn More)
-description: Select Installer Page (Learn More)
-author: dansimp
-ms.assetid: da05e756-d23e-4557-8ff6-313d695a78a1
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Select Installer Page (Learn More)
-
-
-Use the **Select Installer** page to specify the installation (**.msi**, **.exe**) files or programs for the application that you are sequencing. The files specified on this page must be the actual files that will be used to install the application you are sequencing.
-
-This page contains the following elements:
-
-**Select the installer for the application.**
-Specifies the installation file or files that the sequencer runs and records while creating the virtual application package. You must specify a valid Windows Installer or an executable (**.exe**) program.
-
-**Select this option to perform a custom installation.**
-If the application you are installing does not have an associated Windows Installer or executable program, select this option to manually install the application by using a custom set of installation files.
-
-## Related topics
-
-
-[Create New Package Wizard (AppV 4.6 SP1)](create-new-package-wizard---appv-46-sp1-.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/select-package--learn-more--page.md b/mdop/appv-v4/select-package--learn-more--page.md
deleted file mode 100644
index 24f631fd1d..0000000000
--- a/mdop/appv-v4/select-package--learn-more--page.md
+++ /dev/null
@@ -1,39 +0,0 @@
----
-title: Select Package (Learn More) Page
-description: Select Package (Learn More) Page
-author: dansimp
-ms.assetid: 0b3d4ca4-ff65-4aa5-87a9-61cbe2ffc8be
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Select Package (Learn More) Page
-
-
-Use the **Select Package** page to select the source virtual application package you want to use to create the Package Accelerator. Copy the package you specify on this page to the computer running the sequencer.
-
-This page contains the following elements:
-
-**Browse**
-Click **Browse** to specify the existing virtual application package that you will use to create the Package Accelerator. Save the package you specify locally on the computer running the sequencer.
-
-## Related topics
-
-
-[Create Package Accelerator Wizard (AppV 4.6 SP1)](create-package-accelerator-wizard--appv-46-sp1-.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/select-package-accelerator--learn-more--page.md b/mdop/appv-v4/select-package-accelerator--learn-more--page.md
deleted file mode 100644
index 18ce0df5a2..0000000000
--- a/mdop/appv-v4/select-package-accelerator--learn-more--page.md
+++ /dev/null
@@ -1,44 +0,0 @@
----
-title: Select Package Accelerator (Learn More) Page
-description: Select Package Accelerator (Learn More) Page
-author: dansimp
-ms.assetid: 2db51514-8695-4b5e-b3e5-1e96e3ee4cc7
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Select Package Accelerator (Learn More) Page
-
-
-Only run Package Accelerators from publishers that you trust. Package Accelerators usually include a digital signature. A digital signature is an electronic security mark that can help indicate the publisher of the software, and that the package has not been tampered with after the transform was originally signed. If you use a transform that has been digitally signed by a publisher and the publisher has verified its identity with a certification authority, you can be more confident that the transform comes from that specific publisher and has not been altered.
-
-The sequencer notifies you if any of the following conditions are true:
-
-- The selected transform has not been digitally signed.
-
-- The selected transform is signed by a publisher that has not verified its identity with a certification authority.
-
-- The selected transform has been altered after it was digitally signed and released.
-
-If any of these messages are displayed when using a Package Accelerator, visit the Package Accelerators publisher’s website to get a digitally signed version of the transform.
-
-## Related topics
-
-
-[Sequencer Wizard - Package Accelerator (AppV 4.6 SP1)](sequencer-wizard---package-accelerator--appv-46-sp1-.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/select-package-accelerator-page.md b/mdop/appv-v4/select-package-accelerator-page.md
deleted file mode 100644
index b1b04254d7..0000000000
--- a/mdop/appv-v4/select-package-accelerator-page.md
+++ /dev/null
@@ -1,51 +0,0 @@
----
-title: Select Package Accelerator Page
-description: Select Package Accelerator Page
-author: dansimp
-ms.assetid: 865c2702-4dfd-41ae-8cfc-3514d5f41f76
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Select Package Accelerator Page
-
-
-Use the **Select Package Accelerator** page to select the Package Accelerator that will be used to create the new virtual application package. You must copy the Package Accelerator to a folder on the computer running the App-V Sequencer. For more information, see [About App-V Package Accelerators (App-V 4.6 SP1)](about-app-v-package-accelerators--app-v-46-sp1-.md).
-
-Only run Package Accelerators from publishers that you trust. Package Accelerators usually include a digital signature. A digital signature is an electronic security mark that can help indicate the publisher of the software, and whether the package has been tampered with after the transform was originally signed. If you use a transform that has been digitally signed by a publisher and the publisher has verified its identity with a certification authority, you can be more confident that the transform comes from that specific publisher and has not been altered.
-
-The App-V Sequencer notifies you if any of the following conditions are true:
-
-- The selected transform has not been digitally signed.
-
-- The selected transform is signed by a publisher that has not verified its identity with a certification authority.
-
-- The selected transform has been altered after it was digitally signed and released.
-
-If any of these messages are displayed when using a Package Accelerators, visit the Package Accelerators publisher’s website to get a digitally signed version of the transform.
-
-This page contains the following elements:
-
-**Browse**
-Click **Browse** to specify the Package Accelerator that you will use to create the virtual application package. Save the Package Accelerator you specified locally on the computer that is running the Sequencer.
-
-## Related topics
-
-
-[Sequencer Wizard - Package Accelerator (AppV 4.6 SP1)](sequencer-wizard---package-accelerator--appv-46-sp1-.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/select-primary-page--learn-more-.md b/mdop/appv-v4/select-primary-page--learn-more-.md
deleted file mode 100644
index cf6a9e41a9..0000000000
--- a/mdop/appv-v4/select-primary-page--learn-more-.md
+++ /dev/null
@@ -1,49 +0,0 @@
----
-title: Select Primary Page (Learn More)
-description: Select Primary Page (Learn More)
-author: dansimp
-ms.assetid: 17c779da-f683-4967-b136-94fe65373c1b
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Select Primary Page (Learn More)
-
-
-Use the **Select Primary** page to specify the installation file of the program that the add-on or plug-in will be associated with. If the parent application is not already installed on the computer running the App-V Sequencer, you must stop this procedure and install it now.
-
-For example, if you are installing a plug-in that is designed to operate with Microsoft Excel, you must specify **Excel.exe**.
-
-You can also use an existing virtual application package as the parent application. To use an existing virtual application package, use the following procedure before sequencing the new add-on or plug-in.
-
-1. To start the App-V Sequencer, on the computer that is running the App-V Sequencer, click **Start** / **All Programs** / **Microsoft Application Virtualization** / **Microsoft Application Virtualization Sequencer**.
-
-2. To expand an existing package to the computer running the Sequencer, click **Tools** / **Expand Package to Local System**.
-
-3. Browse to, and select the package (**.sprj** file) that you want to expand, and then click **Open**.
-
-This page contains the following elements:
-
-**Browse**
-Click **Browse** to specify the program that the add-in or plug-in you are sequencing will be associated with.
-
-## Related topics
-
-
-[Create New Package Wizard (AppV 4.6 SP1)](create-new-package-wizard---appv-46-sp1-.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/select-task-page--learn-more-.md b/mdop/appv-v4/select-task-page--learn-more-.md
deleted file mode 100644
index 60b28a83fa..0000000000
--- a/mdop/appv-v4/select-task-page--learn-more-.md
+++ /dev/null
@@ -1,71 +0,0 @@
----
-title: Select Task Page (Learn More)
-description: Select Task Page (Learn More)
-author: dansimp
-ms.assetid: 09534c40-bf6c-4b3f-be9a-8624965c9c18
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Select Task Page (Learn More)
-
-
-Use the **Select Task** page to modify an existing virtual application package. For more information about modifying an existing virtual application package, see [How to Modify an Existing Virtual Application Package (App-V 4.6 SP1)](how-to-modify-an-existing-virtual-application-package--app-v-46-sp1-.md).
-
-This page contains the following elements:
-
-**Update Application in Existing Package**
-Select this option to apply an update to an application or program that is part of an existing virtual application package. If you select this option, you should have the associated installation files saved locally to the computer running the App-V Sequencer. You must also have access to the location where the package that contains the application or program that you want to modify is saved.
-
-**Edit Package**
-Select this option to modify the properties associated with an existing virtual application package. To edit a package, you must have access to the location where the virtual application package is saved. The following list displays the package properties that can be updated if you select **Edit Package**:
-
-- View package properties.
-
-- View package change history.
-
-- View associated package files.
-
-- Edit registry settings.
-
-- Review additional package settings (except operating system file properties).
-
-- Create associated Windows Installer.
-
-- Modify OSD file.
-
-- Compress and uncompress package.
-
-- Add file type associations.
-
-- Rename shortcuts.
-
-- Set virtualized registry key state (override / merge).
-
-- Set virtualized folder state.
-
-- Edit virtual file system mappings.
-
-**Add New Application**
-Select this option to add a new application or program to an existing virtual application package. For example, you can add Microsoft Excel to an existing Microsoft Office virtual application package. To add a new application, you must have access to the location where the virtual application package is saved. You can also edit file type associations associated with an existing package.
-
-## Related topics
-
-
-[Open Package Wizard (AppV 4.6 SP1)](open-package-wizard---appv-46-sp1-.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/sequencer-command-line-error-codes.md b/mdop/appv-v4/sequencer-command-line-error-codes.md
deleted file mode 100644
index 73d55eebce..0000000000
--- a/mdop/appv-v4/sequencer-command-line-error-codes.md
+++ /dev/null
@@ -1,101 +0,0 @@
----
-title: Sequencer Command-Line Error Codes
-description: Sequencer Command-Line Error Codes
-author: dansimp
-ms.assetid: 3d491314-4923-45fd-9839-c541c5e620bd
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Sequencer Command-Line Error Codes
-
-
-Use the following list to help identify errors that are related to sequencing applications by using the command line. You can also see this information by viewing the associated App-V Sequencer log file.
-
-**Note**
-Multiple errors can occur during sequencing, and if this happens, the error code that is displayed might be the sum of two error codes. For example, if the */InstallPath* and */OutputFile* parameters are missing, the App-V Sequencer will return **96**—the sum of the two error codes.
-
-
-
-01
-There is an unspecified error.
-
-02
-The specified installation directory (/INSTALLPACKAGE) is not valid.
-
-04
-The specified package root directory (/INSTALLPATH) is not valid.
-
-08
-The specified */OutputFile* parameter is not valid.
-
-16
-The installation directory (/INSTALLPACKAGE) is not specified.
-
-32
-The package root directory (/INSTALLPATH) is not specified.
-
-64
-The */OutputFile* parameter is not specified.
-
-128
-The specified application virtualization drive is not valid.
-
-256
-The installer failed.
-
-512
-Sequencing the application failed.
-
-1024
-Evaluating installed shortcuts failed.
-
-2048
-The sequenced application package cannot be saved.
-
-4096
-The specified package name (/PACKAGENAME) is not valid.
-
-8192
-The specified block size (/BLOCKSIZE) is not valid.
-
-16384
-The specified compression type (/COMPRESSION) is not valid.
-
-32768
-The specified project path is not valid.
-
-65536
-The specified upgrade parameter is not valid.
-
-131072
-The specified upgrade project parameter is not valid.
-
-262144
-The specified decode path parameter is not valid.
-
-525288
-The package name is not specified.
-
-## Related topics
-
-
-[Application Virtualization Sequencer Reference](application-virtualization-sequencer-reference.md)
-
-[Sequencer Command-Line Parameters](sequencer-command-line-parameters.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/sequencer-command-line-parameters.md b/mdop/appv-v4/sequencer-command-line-parameters.md
deleted file mode 100644
index 11ecdb06c4..0000000000
--- a/mdop/appv-v4/sequencer-command-line-parameters.md
+++ /dev/null
@@ -1,93 +0,0 @@
----
-title: Sequencer Command-Line Parameters
-description: Sequencer Command-Line Parameters
-author: dansimp
-ms.assetid: 28fb875a-c302-4d95-b2e0-8dc0c5dbb0f8
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Sequencer Command-Line Parameters
-
-
-You can use the following Application Virtualization (App-V) Sequencer parameters to sequence an application and to upgrade an existing virtual application by using a command line. For more information about sequencing an application by using a command line, see [How to Sequence a New Application by Using the Command Line](how-to-sequence-a-new-application-by-using-the-command-line.md).
-
-## Sequencer Command-Line Parameters
-
-
-**/HELP or /?**
-Displays information about parameters that are available for using a command line to sequence applications.
-
-**/INSTALLPACKAGE or /I**
-Specifies the Windows Installer or a batch file that will be used to install an application so that it can be sequenced.
-
-**/INSTALLPATH or /P**
-Specifies the package root directory for an application.
-
-**/OUTPUTFILE or /O**
-Specifies the path and file name of the SPRJ file that will be generated.
-
-**/FULLLOAD or /F**
-Specifies whether all files will be contained in the primary feature block. If the **/FULLLOAD** parameter is specified on the command line, all of the associated application data is added to primary feature block. If the **/FULLLOAD** parameter is not specified on the command line, then none of the associated application data is added to the primary feature block.
-
-**/PACKAGENAME or /K**
-Specifies the package name that will be assigned to the sequenced application.
-
-**/BLOCKSIZE**
-Specifies the SFT file block size that will be used to stream the package to client computers. You can select one of the following values:
-
-- 4 KB
-
-- 16 KB
-
-- 32 KB
-
-- 64 KB
-
-You should consider the size of the SFT file when you specify the block size. A file with a smaller block size takes longer to stream over the network but is less bandwidth-intensive. Files with larger block sizes use more network bandwidth.
-
-**/COMPRESSION**
-Specifies the method for compressing the SFT file that will be streamed to the client.
-
-**/MSI or /M**
-Specifies whether a Windows Installer for the sequenced application should be created.
-
-**/DEFAULT**
-Specifies the default SPRJ file that will be used when creating a virtual application package. This file is used as the .sprj template when the application is sequenced for the first time.
-
-**/UPGRADE**
-Specifies the path and file name of the SPRJ file that will be upgraded.
-
-**/DECODEPATH**
-Specifies the directory on the sequencing computer where the files associated with the sequenced application package are installed. Use one of the following formats when specifying the directory:
-
-- /decodepath:Q:
-
-- /decodepath:Q:.
-
-- /decodepath:”Q:.”
-
-- /decodepath:”Q:”
-
-## Related topics
-
-
-[Application Virtualization Sequencer](application-virtualization-sequencer.md)
-
-[Sequencer Command-Line Error Codes](sequencer-command-line-error-codes.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/sequencer-console.md b/mdop/appv-v4/sequencer-console.md
deleted file mode 100644
index 661a880497..0000000000
--- a/mdop/appv-v4/sequencer-console.md
+++ /dev/null
@@ -1,56 +0,0 @@
----
-title: Sequencer Console
-description: Sequencer Console
-author: dansimp
-ms.assetid: 69e0202d-be2c-41cc-99cb-2a08a034e804
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Sequencer Console
-
-
-The Application Virtualization Sequencer Console enables you to perform a variety of tasks, including sequencing an application, modifying a sequenced application package, configuring the Application Virtualization Sequencer, and more.
-
-## In This Section
-
-
-[Properties Tab](properties-tab-keep.md)
-Provides general information about the **Properties** tab, along with related procedures you can perform.
-
-[Deployment Tab](deployment-tab.md)
-Provides general information about the **Deployment** tab, along with related procedures you can perform.
-
-[Change History Tab](change-history-tab-keep.md)
-Provides general information about the **Change History** tab.
-
-[Files Tab](files-tab-keep.md)
-Provides general information about the **Files** tab, along with related procedures you can perform.
-
-[Virtual Registry Tab](virtual-registry-tab-keep.md)
-Provides general information about the **Virtual Registry** tab, along with related procedures you can perform.
-
-[Virtual File System Tab](virtual-file-system-tab-keep.md)
-Provides general information about the **Virtual File System** tab, along with related procedures you can perform.
-
-[Virtual Services Tab](virtual-services-tab-keep.md)
-Provides general information about the **Virtual Services** tab, along with related procedures you can perform.
-
-[OSD Tab](osd-tab-keep.md)
-Provides general information about the **OSD** tab, along with related procedures you can perform.
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/sequencer-dialog-boxes.md b/mdop/appv-v4/sequencer-dialog-boxes.md
deleted file mode 100644
index deba694e0e..0000000000
--- a/mdop/appv-v4/sequencer-dialog-boxes.md
+++ /dev/null
@@ -1,43 +0,0 @@
----
-title: Sequencer Dialog Boxes
-description: Sequencer Dialog Boxes
-author: dansimp
-ms.assetid: f660d56b-0244-4167-b077-96ad482e6b36
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Sequencer Dialog Boxes
-
-
-## In This Section
-
-
-- [Application Virtualization Sequencer Options Dialog Box](application-virtualization-sequencer-options-dialog-box.md)
-
-- [Application Virtualization Sequencing Wizard-Add Application Dialog Box](application-virtualization-sequencing-wizard-add-application-dialog-box.md)
-
-- [Application Virtualization Sequencing Wizard-Add File Type Association Dialog Box](application-virtualization-sequencing-wizard-add-file-type-association-dialog-box.md)
-
-- [Application Virtualization Sequencing Wizard-Shortcut Locations Dialog Box](application-virtualization-sequencing-wizard-shortcut-locations-dialog-box.md)
-
-## Related topics
-
-
-[Sequencing Wizard](sequencing-wizard.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/sequencer-hardware-and-software-requirements.md b/mdop/appv-v4/sequencer-hardware-and-software-requirements.md
deleted file mode 100644
index 40fe62a7a2..0000000000
--- a/mdop/appv-v4/sequencer-hardware-and-software-requirements.md
+++ /dev/null
@@ -1,153 +0,0 @@
----
-title: Sequencer Hardware and Software Requirements
-description: Sequencer Hardware and Software Requirements
-author: dansimp
-ms.assetid: 36084e12-831d-452f-a4a4-45f07f9ce471
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Sequencer Hardware and Software Requirements
-
-
-This topic describes the minimum recommended hardware and software requirements for the computer running the Microsoft Application Virtualization (App-V) Sequencer.
-
-Before you install the Sequencer and after you sequence each application, you must restore a clean operating system image to the sequencing computer. You can use one of the following methods to restore the computer running the Sequencer:
-
-- Reformat the hard drive and reinstall the operating system.
-
-- Restore the hard drive on the computer running the Sequencer image by using another disk-imaging software.
-
-The following list outlines the recommended hardware requirements for running the App-V Sequencer.
-
-### Hardware Requirements
-
-- Processor—Intel Pentium III, 1 GHz (32-bit or 64-bit). The sequencing process is a single-threaded process and does not take advantage of dual processors.
-
-- Memory—1 GB or above, 2 GB recommended.
-
-- Hard Disk—40 gigabyte (GB) hard disk space with a minimum of 15 GB available hard disk space. We recommend that you have at least three times the hard disk space that the application you are sequencing requires.
-
- **Note**
- Sequencing requires heavy disk usage. A fast disk speed can decrease the sequencing time.
-
-
-
-### Software Requirements
-
-The following list outlines the supported operating systems for running the Sequencer.
-
-
-
-
-
-
-
-
-
-
-
Operating System
-
Edition
-
Service Pack
-
System Architecture
-
-
-
-
-
Windows XP
-
Professional
-
SP2 or SP3
-
x86
-
-
-
Windows Vista
-
Business, Enterprise, or Ultimate
-
No service pack, SP1, or SP2
-
x86
-
-
-
Windows 7¹
-
Professional, Enterprise, or Ultimate
-
-
x86
-
-
-
-
-
-
-¹Supported for App-V 4.5 with SP1 or SP2, and App-V 4.6 only
-
-**Note**
-The Application Virtualization (App-V) 4.6 Sequencer supports 32-bit and 64-bit versions of these operating systems.
-
-
-
-You should configure computers running the Sequencer with the same applications that are installed on target computers.
-
-### Software Requirements for Remote Desktop Services
-
-
-
-
-
-
-
-
-
-
-
Operating System
-
Edition
-
Service Pack
-
System Architecture
-
-
-
-
-
Windows Server 2003
-
Standard Edition, Enterprise Edition, or Datacenter Edition
-
SP1 or SP2
-
x86
-
-
-
Windows Server 2003 R2
-
Standard Edition, Enterprise Edition, or Datacenter Edition
-
-
x86
-
-
-
Windows Server 2008
-
Standard, Enterprise, or Datacenter
-
SP1 or SP2
-
x86
-
-
-
-
-
-
-**Note**
-Application Virtualization (App-V) 4.6 for Remote Desktop Services supports 32-bit and 64-bit versions of these operating systems.
-
-
-
-## Related topics
-
-
-[Application Virtualization Sequencer Overview](application-virtualization-sequencer-overview.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/sequencer-wizard---package-accelerator--appv-46-sp1-.md b/mdop/appv-v4/sequencer-wizard---package-accelerator--appv-46-sp1-.md
deleted file mode 100644
index 6da8f78d45..0000000000
--- a/mdop/appv-v4/sequencer-wizard---package-accelerator--appv-46-sp1-.md
+++ /dev/null
@@ -1,55 +0,0 @@
----
-title: Sequencer Wizard - Package Accelerator (AppV 4.6 SP1)
-description: Sequencer Wizard - Package Accelerator (AppV 4.6 SP1)
-author: dansimp
-ms.assetid: 1f75f5ba-0707-48fb-b0b8-ba94a5159e36
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Sequencer Wizard - Package Accelerator (AppV 4.6 SP1)
-
-
-Use any of the following links for more information about the App-V Package Accelerator wizard.
-
-## In This Section
-
-
-[Select Package Accelerator Page](select-package-accelerator-page.md)
-
-[Select Package Accelerator (Learn More) Page](select-package-accelerator--learn-more--page.md)
-
-[Guidance Page](guidance-page-app-v-46-sp1.md)
-
-[Select Installation Files Page](select-installation-files-page-app-v-46-sp1.md)
-
-[Package Name Page](package-name-page--app-v-46-sp1.md)
-
-[Create Package Page](create-package-page--app-v-46-sp1.md)
-
-[Configure Software Page](configure-software-page-app-v-46-sp1.md)
-
-[Run Each Program Page](run-each-program-page-app-v-46-sp1.md)
-
-[Completion Page](completion-page-package-accelerator.md)
-
-## Related topics
-
-
-[Wizard Pages (AppV 4.6 SP1)](wizard-pages--appv-46-sp1-.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/sequencing-wizard.md b/mdop/appv-v4/sequencing-wizard.md
deleted file mode 100644
index 4db54af6bc..0000000000
--- a/mdop/appv-v4/sequencing-wizard.md
+++ /dev/null
@@ -1,51 +0,0 @@
----
-title: Sequencing Wizard
-description: Sequencing Wizard
-author: dansimp
-ms.assetid: 81e2f4fa-b06e-4cbe-aeb8-6ceb8f0543a5
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Sequencing Wizard
-
-
-Use the Sequencing Wizard to create applications that can run in a virtual environment. The topics in this section provide detailed information about each wizard page in the Sequencing Wizard.
-
-## In This Section
-
-
-- [Application Virtualization Sequencing Wizard Package Information Page](application-virtualization-sequencing-wizard-package-information-page-keep.md)
-
-- [Application Virtualization Sequencing Wizard Advanced Options Page](application-virtualization-sequencing-wizard-advanced-options-page.md)
-
-- [Application Virtualization Sequencing Wizard Monitor Installation Page](application-virtualization-sequencing-wizard-monitor-installation-page.md)
-
-- [Application Virtualization Sequencing Wizard Add Files to Virtual File System Page](application-virtualization-sequencing-wizard-add-files-to-virtual-file-system-page.md)
-
-- [Application Virtualization Sequencing Wizard Configure Application Page](application-virtualization-sequencing-wizard-configure-application-page-keep.md)
-
-- [Application Virtualization Sequencing Wizard Launch Applications Page](application-virtualization-sequencing-wizard-launch-applications-page.md)
-
-- [Application Virtualization Sequencing Wizard Sequence Package Page](application-virtualization-sequencing-wizard-sequence-package-page.md)
-
-## Related topics
-
-
-[Sequencer Dialog Boxes](sequencer-dialog-boxes.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/server-groups-node.md b/mdop/appv-v4/server-groups-node.md
deleted file mode 100644
index 95137d7733..0000000000
--- a/mdop/appv-v4/server-groups-node.md
+++ /dev/null
@@ -1,83 +0,0 @@
----
-title: Server Groups Node
-description: Server Groups Node
-author: dansimp
-ms.assetid: 6b2ed086-9100-47d0-be7f-0c5fb4fa55c6
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Server Groups Node
-
-
-The **Server Groups** node is one level below the Application Virtualization System node in the **Scope** pane in the Application Virtualization Server Management Console. When you select this node, the **Results** pane displays a list of server groups. Right-click the node to display a pop-up menu that contains the following elements.
-
-**New Server Group**
-Displays the New Server Group Wizard. This wizard consists of a single page, where you can specify a name for the server group in the **Server Group Name** field and then select the default provider policy from the drop-down menu of available provider policies. Select the **Enable** check box to enable the server group. Click **Finish** to add the new server group.
-
-**View**
-Changes the appearance and content of the **Results** pane.
-
-**New Window from Here**
-Opens a new management console with the selected node as the root node.
-
-**Refresh**
-Refreshes the view of the server.
-
-**Export List**
-Creates a tab-delimited text file that contains the contents of the **Results** pane. This item displays a standard **File Save** dialog box where you specify the location for the text file you are creating.
-
-**Help**
-Displays the help system for the Application Virtualization Server Management Console.
-
-If you click any server group that appears under the **Server Groups** node in the **Scope** pane, the following elements are available.
-
-**New Virtual Application Server**
-Displays the New Virtual Application Server Wizard. Use this wizard to add a new Application Virtualization Management Server. This wizard has one page, in which you specify the server name in the **Display Name** field and enter a name in the **DNS Host Name** field. From this wizard, you can also specify a value for the server cache in the **Maximum Memory Allocation (MB)** field and a value for the threshold warning level in the **Warn Memory Allocation (MB)** field.
-
-**New Window from Here**
-Opens a new management console with the selected node as the root node.
-
-**Delete**
-Deletes a package from the **Results** pane.
-
-**Rename**
-Changes the name of a package in the **Results** pane.
-
-**Refresh**
-Refreshes the view of the server.
-
-**Properties**
-Displays the **Properties** dialog box for the selected server group. The **Properties** dialog box has the following tabs:
-
-- **General**—Enables you to select the provider policy from the drop-down list of Provider Policies. You can also enable or disable the server by selecting or clearing the **Enable** check box.
-
-- **Logging**—Enables you to add, edit, and remove logging modules. When you add or edit a logging module, you can also set or change the logging level.
-
-- **Applications**—Lists the applications that are associated with the selected server group. The displayed information includes the application name, version number, and enable status.
-
-**Help**
-Displays the help system for the Application Virtualization Server Management Console.
-
-## Related topics
-
-
-[How to Manage Servers in the Server Management Console](how-to-manage-servers-in-the-server-management-console.md)
-
-[Server Management Console: Server Groups Node](server-management-console-server-groups-node.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/server-groups-results-pane-columns.md b/mdop/appv-v4/server-groups-results-pane-columns.md
deleted file mode 100644
index 9a40ac8e31..0000000000
--- a/mdop/appv-v4/server-groups-results-pane-columns.md
+++ /dev/null
@@ -1,90 +0,0 @@
----
-title: Server Groups Results Pane Columns
-description: Server Groups Results Pane Columns
-author: dansimp
-ms.assetid: e91b1b9b-e58c-4274-ad18-8b157936b9be
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Server Groups Results Pane Columns
-
-
-The **Results** pane in the Application Virtualization Server Management Console displays a variety of columns. If there are additional columns available, you can add and remove them.
-
-You can use the standard Microsoft Windows **Add/Remove Columns** dialog box to select which columns are displayed in the **Results** pane.
-
-To see the **Add/Remove Columns** dialog box, right-click in the **Results** pane and select **View > Add/Remove Columns** from the pop-up menu.
-
-When the **Results** pane displays server groups, the column name and contents that appear are described in the following table.
-
-
-
-
-
-
-
-
-
Column
-
Contents
-
-
-
-
-
Name
-
Displays the name of the server group.
-
-
-
-
-
-
-When the **Results** pane displays virtual application servers, the column name and contents that appear are described in the following table.
-
-
-
-
-
-
-
-
-
Column
-
Contents
-
-
-
-
-
Name
-
Displays the name of the virtual application server.
-
-
-
Host Name
-
Displays the DNS host name for the virtual application server.
-
-
-
-
-
-
-## Related topics
-
-
-[How to Manage Servers in the Server Management Console](how-to-manage-servers-in-the-server-management-console.md)
-
-[Server Management Console: Server Groups Node](server-management-console-server-groups-node.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/server-groups-results-pane.md b/mdop/appv-v4/server-groups-results-pane.md
deleted file mode 100644
index e8558e68c8..0000000000
--- a/mdop/appv-v4/server-groups-results-pane.md
+++ /dev/null
@@ -1,131 +0,0 @@
----
-title: Server Groups Results Pane
-description: Server Groups Results Pane
-author: dansimp
-ms.assetid: ac7b0525-5946-4728-9cf1-c65007852ebe
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Server Groups Results Pane
-
-
-The **Server Groups Results** pane in the Application Virtualization Server Management Console displays a list of the available server groups and Application Virtualization Management Servers.
-
-When you right-click any server group, the following elements are displayed.
-
-**New Application Virtualization Management Server**
-Displays the New Server Wizard. Use this wizard to add a new Application Virtualization Management Server. This wizard has one page, in which you specify a name for the server in the **Display Name** field, and enter a name in the **DNS Host Name** field. From this wizard, you can also specify a maximum memory allocation for the server cache and a memory threshold warning level.
-
-**New Window from Here**
-Opens a new management console with the selected node as the root node.
-
-**Delete**
-Deletes a server group.
-
-**Rename**
-Changes the name of a server group.
-
-**Refresh**
-Refreshes the **Results** pane.
-
-**Properties**
-Displays the **Properties** dialog box for the selected server group. The **Properties** dialog box has the following tabs:
-
-- **General Tab**—Enables you to select the provider policy from the drop-down list of provider policies and to enable or disable the server by selecting or clearing the **Enable** check box.
-
-- **Logging Tab**—Displays the list of logging modules. You can add, edit, and remove logging modules from this tab. When you add or edit a logging module, you can also set or change the logging level.
-
-- **Applications Tab**—Lists the applications that are associated with the selected server group. The displayed information includes the application name, version number, and enable status.
-
-**Help**
-Displays the help system for the Application Virtualization Server Management Console.
-
-When the **Results** pane displays **Server Groups**, right-click anywhere in the **Results** pane, except on a server group, to display a pop-up menu that contains the following elements.
-
-**Refresh**
-Refreshes the view of the server.
-
-**Export List**
-Creates a tab-delimited text file that contains the contents of the **Results** pane. This item displays a standard **File Save** dialog box where you specify the location for the text file you are creating.
-
-**View**
-Changes the appearance and content of the **Results** pane.
-
-**Arrange/Line Up Icons**
-Changes how the icons are displayed in the **Results** pane.
-
-**Help**
-Displays the help system for the Application Virtualization Server Management Console.
-
-When the **Results** pane displays **Application Virtualization Management** **Servers**, right-click a server to display a pop-up menu that contains the following elements.
-
-**Duplicate**
-Duplicates an Application Virtualization Management Server.
-
-**Delete**
-Deletes an Application Virtualization Management Server.
-
-**Rename**
-Changes the name of an Application Virtualization Management Server.
-
-**Properties**
-Displays the **Properties** dialog box for the selected server. The **Properties** dialog box has the following tabs:
-
-- **General**—Enables you to select the provider policy from the **Provider Policies** drop-down list and to enable or disable the server by selecting or clearing the **Enable** check box.
-
-- **Logging**—Displays the **Logging Modules** list. You can add, edit, and remove logging modules from this tab. When you add or edit a logging module, you can also set or change the logging level.
-
-- **Applications**—Lists the applications that are associated with the selected server group. The displayed information includes the application name, version number, and enable status.
-
-**Help**
-Displays the help system for the Application Virtualization Server Management Console.
-
-When the **Results** pane displays **Application Virtualization Management** **Servers**, right-click anywhere, except on a server, to display a pop-up menu that contains the following elements.
-
-**Refresh**
-Refreshes the **Results** pane.
-
-**Export List**
-Creates a tab-delimited text file that contains the contents of the **Results** pane. This item displays a standard **File Save** dialog box where you specify the location for the text file you are creating.
-
-**View**
-Changes the appearance and content of the **Results** pane.
-
-**Arrange/Line Up Icons**
-Changes how the icons are displayed in the **Results** pane.
-
-**Properties**
-Displays the **Properties** dialog box for the most recently selected server. The **Properties** dialog box has the following tabs:
-
-- **General**—Enables you to select the provider policy from the **Provider Policies** drop-down list and to enable or disable the server by selecting or clearing the **Enable** check box.
-
-- **Logging**—Displays the **Logging Modules** list. You can add, edit, and remove logging modules from this tab. When you add or edit a logging module, you can also set or change the logging level.
-
-- **Applications**—Lists the applications that are associated with the selected server group. The displayed information includes the application name, version number, and enable status.
-
-**Help**
-Displays the help system for the Application Virtualization Server Management Console.
-
-## Related topics
-
-
-[How to Manage Servers in the Server Management Console](how-to-manage-servers-in-the-server-management-console.md)
-
-[Server Management Console: Server Groups Node](server-management-console-server-groups-node.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/server-management-console-about-dialog-boxes.md b/mdop/appv-v4/server-management-console-about-dialog-boxes.md
deleted file mode 100644
index c40139a8da..0000000000
--- a/mdop/appv-v4/server-management-console-about-dialog-boxes.md
+++ /dev/null
@@ -1,36 +0,0 @@
----
-title: Server Management Console About Dialog Boxes
-description: Server Management Console About Dialog Boxes
-author: dansimp
-ms.assetid: b5fdee0b-4269-4a48-98a0-ed3f06cff041
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Server Management Console: About Dialog Boxes
-
-
-The **About** dialog boxes display information about the specific version of the Microsoft Management Console or the specific version of the Application Virtualization Server Management Console.
-
-To display these dialog boxes, click **Help** and select **About Microsoft Management Console** or **About Application Virtualization Server Management Console**.
-
-## Related topics
-
-
-[Application Virtualization Server Management Console Reference](application-virtualization-server-management-console-reference.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/server-management-console-administrators-node.md b/mdop/appv-v4/server-management-console-administrators-node.md
deleted file mode 100644
index 0ed24e294f..0000000000
--- a/mdop/appv-v4/server-management-console-administrators-node.md
+++ /dev/null
@@ -1,48 +0,0 @@
----
-title: Server Management Console Administrators Node
-description: Server Management Console Administrators Node
-author: dansimp
-ms.assetid: ab421454-69d1-4c10-8f58-2a35ae89c8b1
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Server Management Console: Administrators Node
-
-
-The topics in this section provide information about the screen reference for the **Administrators** node in the Application Virtualization Server Management Console.
-
-## In This Section
-
-
-[Administrators Node](administrators-node.md)
-Describes the features and commands available from the **Administrators** node.
-
-[Administrators Results Pane](administrators-results-pane.md)
-Describes the features and commands available in the **Administrators** node **Results** pane.
-
-[Administrators Results Pane Columns](administrators-results-pane-columns.md)
-Describes the columns available in the **Administrators** node **Results** pane.
-
-## Related topics
-
-
-[Application Virtualization Server Management Console Reference](application-virtualization-server-management-console-reference.md)
-
-[How to Perform Administrative Tasks in the Application Virtualization Server Management Console](how-to-perform-administrative-tasks-in-the-application-virtualization-server-management-console.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/server-management-console-application-licenses-node.md b/mdop/appv-v4/server-management-console-application-licenses-node.md
deleted file mode 100644
index 9d37dd63fa..0000000000
--- a/mdop/appv-v4/server-management-console-application-licenses-node.md
+++ /dev/null
@@ -1,50 +0,0 @@
----
-title: Server Management Console Application Licenses Node
-description: Server Management Console Application Licenses Node
-author: dansimp
-ms.assetid: ad3fa486-2b3c-4efd-91f5-507e9c5057d5
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Server Management Console: Application Licenses Node
-
-
-The topics in this section provide information about the screen reference for the **Application Licenses** node in the Application Virtualization Server Management Console.
-
-## In This Section
-
-
-[Applications Licenses Node](applications-licenses-node.md)
-Describes the features and commands available from the **Application Licenses** node.
-
-[Applications Licenses Results Pane](applications-licenses-results-pane.md)
-Describes the features and commands available in the **Application Licenses** node **Results** pane.
-
-[Applications Licenses Results Pane Columns](applications-licenses-results-pane-columns.md)
-Describes the columns available in the **Application Licenses** node **Results** pane.
-
-## Related topics
-
-
-[About Application Licensing](about-application-licensing.md)
-
-[Application Virtualization Server Management Console Reference](application-virtualization-server-management-console-reference.md)
-
-[How to Manage Application Licenses in the Server Management Console](how-to-manage-application-licenses-in-the-server-management-console.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/server-management-console-application-virtualization-system-node.md b/mdop/appv-v4/server-management-console-application-virtualization-system-node.md
deleted file mode 100644
index b52204a63d..0000000000
--- a/mdop/appv-v4/server-management-console-application-virtualization-system-node.md
+++ /dev/null
@@ -1,72 +0,0 @@
----
-title: Server Management Console Application Virtualization System Node
-description: Server Management Console Application Virtualization System Node
-author: dansimp
-ms.assetid: 9450832e-335c-41e7-af24-fddb8ffc327c
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Server Management Console: Application Virtualization System Node
-
-
-The Application Virtualization System node is the top-level node in the **Scope** pane. This node displays the name of the server the console is currently controlling, or it displays the name of the local computer (if you are connected by the name) or "local" when the console is connected to the local computer. From the Application Virtualization System node, you can connect to another computer or you can connect to the current computer with a different set of credentials.
-
-You can right-click the Application Virtualization System node to display the following elements.
-
-**Configure Connection**
-In this dialog box, you can modify the following settings:
-
-- **Web Service Host Name**—Enables you to enter the name of the Application Virtualization System to which you want to connect, or you can enter **localhost** to connect to the local computer.
-
-- **Use Secure Connection**—Select if you want to connect to the server with a secure connection.
-
-- **Port**—Enables you to enter the port number you want to use for the connection. 80 is the default regular port number, and 443 is default secure port number.
-
-- **Use Current Windows Account**—Select to use the current Windows account credentials.
-
-- **Specify Windows Account**—Select when you want to connect to the server as a different user.
-
-- **Name**—Enables you to enter the name of the new user by using either the *DOMAIN\\username* or the username@domain format.
-
-- **Password**—Enables you to enter the password that corresponds to the new user.
-
-**System Options**
-On the following tabs on this dialog box, you can modify the associated settings:
-
-- **General Tab**—Enables you to specify the **Default Content Path** where the OSD and icon files are stored.
-
-- **Database Tab**—Enables you to specify the maximum **Database Size** and the **Usage History**.
-
-**View**
-Changes the appearance of the Application Virtualization Server Management Console. For more information about changing the appearance of the console, refer to the help files for the Microsoft Management Console.
-
-**New Window from Here**
-Opens a new management console window.
-
-**Export List**
-Creates a tab-delimited text file that contains the contents of the **Results** pane. This item displays a standard **File Save** dialog box where you specify the location for the text file you are creating.
-
-**Help**
-Starts the management console help file.
-
-## Related topics
-
-
-[Application Virtualization Server Management Console Reference](application-virtualization-server-management-console-reference.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/server-management-console-applications-node.md b/mdop/appv-v4/server-management-console-applications-node.md
deleted file mode 100644
index 4b72b9cea2..0000000000
--- a/mdop/appv-v4/server-management-console-applications-node.md
+++ /dev/null
@@ -1,46 +0,0 @@
----
-title: Server Management Console Applications Node
-description: Server Management Console Applications Node
-author: dansimp
-ms.assetid: e465f816-032d-4824-9924-f2dcf30f2a2c
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Server Management Console: Applications Node
-
-
-The topics in this section provide information about the screen reference for the **Applications** node in the Application Virtualization Server Management Console.
-
-## In This Section
-
-
-[Applications Node in Server Management Console](applications-node-in-server-management-console.md)
-Describes the features and commands available from the **Applications** node.
-
-[Applications Results Pane in Server Management Console](applications-results-pane-in-server-management-console.md)
-Describes the features and commands available in the **Applications** node **Results** pane.
-
-[Applications Results Pane Columns in Server Management Console](applications-results-pane-columns-in-server-management-console.md)
-Describes the columns available in the **Applications** node **Results** pane.
-
-## Related topics
-
-
-[Application Virtualization Server Management Console Reference](application-virtualization-server-management-console-reference.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/server-management-console-file-type-associations-node.md b/mdop/appv-v4/server-management-console-file-type-associations-node.md
deleted file mode 100644
index 30911041dd..0000000000
--- a/mdop/appv-v4/server-management-console-file-type-associations-node.md
+++ /dev/null
@@ -1,46 +0,0 @@
----
-title: Server Management Console File Type Associations Node
-description: Server Management Console File Type Associations Node
-author: dansimp
-ms.assetid: c22168be-6601-4154-b36b-9ca0fa87e5e0
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Server Management Console: File Type Associations Node
-
-
-The topics in this section provide information about the screen reference for the **File Type Associations** node in the Application Virtualization Server Management Console.
-
-## In This Section
-
-
-[File Type Associations Node](file-type-associations-node.md)
-Describes the features and commands available from the **File Type Associations** node.
-
-[File Type Associations Results Pane](file-type-associations-results-pane.md)
-Describes the features and commands available in the **File Type Associations** node **Results** pane.
-
-[File Type Associations Results Pane Columns](file-type-associations-results-pane-columns.md)
-Describes the columns available in the **File Type Associations** node **Results** pane.
-
-## Related topics
-
-
-[Application Virtualization Server Management Console Reference](application-virtualization-server-management-console-reference.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/server-management-console-packages-node.md b/mdop/appv-v4/server-management-console-packages-node.md
deleted file mode 100644
index dc6de0a83f..0000000000
--- a/mdop/appv-v4/server-management-console-packages-node.md
+++ /dev/null
@@ -1,50 +0,0 @@
----
-title: Server Management Console Packages Node
-description: Server Management Console Packages Node
-author: dansimp
-ms.assetid: 458424f6-d586-4fa8-bf61-44c5028a4490
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Server Management Console: Packages Node
-
-
-The topics in this section provide information about the screen reference for the **Packages** node in the Application Virtualization Server Management Console.
-
-## In This Section
-
-
-[Packages Node](packages-node.md)
-Describes the features and commands available from the **Packages** node.
-
-[Package Results Pane](package-results-pane.md)
-Describes the features and commands available in the **Packages** node **Results** pane.
-
-[Package Results Pane Columns](package-results-pane-columns.md)
-Describes the columns available in the **Packages** node **Results** pane.
-
-## Related topics
-
-
-[About Application Virtualization Packages](about-application-virtualization-packages.md)
-
-[Application Virtualization Server Management Console Reference](application-virtualization-server-management-console-reference.md)
-
-[How to Manage Packages in the Server Management Console](how-to-manage-packages-in-the-server-management-console.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/server-management-console-provider-policies-node.md b/mdop/appv-v4/server-management-console-provider-policies-node.md
deleted file mode 100644
index e48e539846..0000000000
--- a/mdop/appv-v4/server-management-console-provider-policies-node.md
+++ /dev/null
@@ -1,46 +0,0 @@
----
-title: Server Management Console Provider Policies Node
-description: Server Management Console Provider Policies Node
-author: dansimp
-ms.assetid: a5b99158-9af8-45bb-b3b8-61e220529e14
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Server Management Console: Provider Policies Node
-
-
-The topics in this section provide information about the screen reference for the **Provider Policies** node in the Application Virtualization Server Management Console.
-
-## In This Section
-
-
-[Provider Policies Node](provider-policies-node.md)
-Describes the features and commands available from the **Provider Policies** node.
-
-[Provider Policies Results Pane](provider-policies-results-pane.md)
-Describes the features and commands available in the **Provider Policies** node **Results** pane.
-
-[Provider Policies Results Pane Columns](provider-policies-results-pane-columns.md)
-Describes the columns available in the **Provider Policies** node **Results** pane.
-
-## Related topics
-
-
-[Application Virtualization Server Management Console Reference](application-virtualization-server-management-console-reference.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/server-management-console-reports-node.md b/mdop/appv-v4/server-management-console-reports-node.md
deleted file mode 100644
index 5cda771115..0000000000
--- a/mdop/appv-v4/server-management-console-reports-node.md
+++ /dev/null
@@ -1,56 +0,0 @@
----
-title: Server Management Console Reports Node
-description: Server Management Console Reports Node
-author: dansimp
-ms.assetid: 9dde6332-5882-40dd-8a8f-857216df80ed
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Server Management Console: Reports Node
-
-
-The topics in this section provide information about the screen reference for the **Reports** node in the Application Virtualization Server Management Console.
-
-## In This Section
-
-
-Reports Node
-Describes the features and commands available from the **Reports** node.
-
-[Reports Results Pane](reports-results-pane.md)
-Describes the features and commands available in the **Reports** node **Results** pane.
-
-[Reports Results Pane Columns](reports-results-pane-columns.md)
-Describes the columns available in the **Reports** node **Results** pane.
-
-## Related topics
-
-
-[Application Utilization Report](application-utilization-reportserver.md)
-
-[Application Virtualization Server Management Console Reference](application-virtualization-server-management-console-reference.md)
-
-[Software Audit Report](software-audit-reportserver.md)
-
-[System Error Report](system-error-reportserver.md)
-
-[System Utilization Report](system-utilization-reportserver.md)
-
-[How to Manage Reports in the Server Management Console](how-to-manage-reports-in-the-server-management-console.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/server-management-console-server-groups-node.md b/mdop/appv-v4/server-management-console-server-groups-node.md
deleted file mode 100644
index 4b657466b4..0000000000
--- a/mdop/appv-v4/server-management-console-server-groups-node.md
+++ /dev/null
@@ -1,48 +0,0 @@
----
-title: Server Management Console Server Groups Node
-description: Server Management Console Server Groups Node
-author: dansimp
-ms.assetid: 83b86fc5-3f77-4470-985a-cf0bb8686067
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Server Management Console: Server Groups Node
-
-
-The topics in this section provide information about the screen reference for the **Server Groups** node in the Application Virtualization Server Management Console.
-
-## In This Section
-
-
-[Server Groups Node](server-groups-node.md)
-Describes the features and commands available from the **Server Groups** node.
-
-[Server Groups Results Pane](server-groups-results-pane.md)
-Describes the features and commands available in the **Server Groups** node **Results** pane.
-
-[Server Groups Results Pane Columns](server-groups-results-pane-columns.md)
-Describes the columns available in the **Server Groups** node **Results** pane.
-
-## Related topics
-
-
-[Application Virtualization Server Management Console Reference](application-virtualization-server-management-console-reference.md)
-
-[How to Manage Servers in the Server Management Console](how-to-manage-servers-in-the-server-management-console.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/sftmime--command-reference.md b/mdop/appv-v4/sftmime--command-reference.md
deleted file mode 100644
index 732b47bafc..0000000000
--- a/mdop/appv-v4/sftmime--command-reference.md
+++ /dev/null
@@ -1,101 +0,0 @@
----
-title: SFTMIME Command Reference
-description: SFTMIME Command Reference
-author: dansimp
-ms.assetid: a4a69228-9dd3-4623-b773-899d03c0cf10
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# SFTMIME Command Reference
-
-
-SFTMIME is a command-line interface used by Application Virtualization (App-V) that enables you to manage many client configuration details. This section contains all the commands and their parameters, with a brief description of each.
-
-**Important**
-- All backslash characters must be escaped using a preceding backslash, or the path will not be parsed correctly.
-
-- If you are using a calling program to invoke SFTMIME with **CreateProcess**, you must ensure that the first parameter is the path to sftmime.exe.
-
-- The output of the SFTMIME **QUERY OBJ** command cannot be piped to the **findstr** command to search for a string.
-
-- Use of the **GLOBAL** switch requires local administrator rights.
-
-- Use of short paths and relative paths can lead to unexpected results and should be avoided. Always use full paths.
-
-
-
-## In This Section
-
-
-[ADD APP](add-app.md)
-
-[ADD PACKAGE](add-package.md)
-
-[ADD SERVER](add-server.md)
-
-[ADD TYPE](add-type.md)
-
-[CLEAR APP](clear-app.md)
-
-[CLEAR OBJ](clear-obj.md)
-
-[CONFIGURE APP](configure-app.md)
-
-[CONFIGURE PACKAGE](configure-package.md)
-
-[CONFIGURE SERVER](configure-server.md)
-
-[CONFIGURE TYPE](configure-type.md)
-
-[DELETE APP](delete-app.md)
-
-[DELETE OBJ](delete-obj.md)
-
-[DELETE PACKAGE](delete-package.md)
-
-[DELETE SERVER](delete-server.md)
-
-[DELETE TYPE](delete-type.md)
-
-[HELP](help.md)
-
-[LOAD APP](load-app.md)
-
-[LOAD PACKAGE](load-package.md)
-
-[LOCK APP](lock-app.md)
-
-[PUBLISH APP](publish-app.md)
-
-[PUBLISH PACKAGE](publish-package.md)
-
-[QUERY OBJ](query-obj.md)
-
-[REFRESH SERVER](refresh-server.md)
-
-[REPAIR APP](repair-app.md)
-
-[UNLOAD APP](unload-app.md)
-
-[UNLOAD PACKAGE](unload-package.md)
-
-[UNLOCK APP](unlock-app.md)
-
-[UNPUBLISH PACKAGE](unpublish-package.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/sfttray-command-reference.md b/mdop/appv-v4/sfttray-command-reference.md
deleted file mode 100644
index 9e7dc93e91..0000000000
--- a/mdop/appv-v4/sfttray-command-reference.md
+++ /dev/null
@@ -1,145 +0,0 @@
----
-title: SFTTRAY Command Reference
-description: SFTTRAY Command Reference
-author: dansimp
-ms.assetid: 6fa3a939-b047-4d6c-bd1d-dfb93e065eb2
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# SFTTRAY Command Reference
-
-
-The Microsoft Application Virtualization (App-V) Client Tray application, sfttray.exe, is the main user interface element of the App-V Client that users will interact with during normal use. This program controls the streaming and starting of all virtual applications and is accessed by right-clicking the icon displayed in the notification area to display the menu of client functions. The menu enables the user to load applications, start a publishing refresh, cancel a request, or change the client to offline mode. The user can also close the Application Virtualization Client Tray application and all active applications by clicking **Exit**.
-
-By default, the icon is displayed whenever a virtual application is started, although you can control this behavior by using SFTTRAY commands. The Application Virtualization Client Tray application also displays a progress bar for each application that is started, as well as status messages about active applications. Clicking the progress bar displays a message that allows you to cancel the loading or starting of an application.
-
-## SFTTRAY Commands
-
-
-The list of commands and command-line switches can be displayed by running the following command from a command window.
-
-**Note**
-There is only one Application Virtualization Client Tray instance for each user context, so if you start a new SFTTRAY command, it will be passed to the program that is already running.
-
-
-
-`Sfttray.exe /?`
-
-### Command Usage
-
-`Sfttray.exe [/HIDE | /SHOW]`
-
-`Sfttray.exe [/HIDE | /SHOW] [/QUIET] [/EXE alternate-exe] /LAUNCH app [args]`
-
-`Sfttray.exe [/HIDE | /SHOW] [/QUIET] /LOAD app [/SFTFILE sft]`
-
-`Sfttray.exe [/HIDE | /SHOW] [/QUIET] /LOADALL`
-
-`Sfttray.exe [/HIDE | /SHOW] [/QUIET] /REFRESHALL`
-
-`Sfttray.exe [/HIDE | /SHOW] [/QUIET] /LAUNCHRESULT /LAUNCH app [args]`
-
-`Sfttray.exe /EXIT`
-
-### Command-Line Switches
-
-The SFTTRAY command-line switches are described in the following table.
-
-
-
-
-
-
-
-
-
Switch
-
Description
-
-
-
-
-
/HIDE
-
Hides the SFTTRAY icon in the Windows notification area.
-
-
-
/SHOW
-
Displays the SFTTRAY icon in the Windows notification area.
-
-
-
/QUIET
-
Supports unattended usage by preventing errors from displaying message boxes that require user acknowledgement.
-
-
-
/EXE <alternate-exe>
-
Used with /LAUNCH to specify that an executable program is to be started in the virtual environment when a virtual application is started in place of the target file specified in the OSD.
-
-Note
For example, use “SFTTRAY.EXE /EXE REGEDIT.EXE /LAUNCH <app>” to enable you to examine the registry of the virtual environment in which the application is running.
-
-
-
-
-
-
-
/LAUNCH <app> [<args>]
-
Starts a virtual application. Specify the name and version of an application or the path to an OSD file. Optionally, command-line arguments can be passed to the virtual application.
-
-Note
Use the command “SFTMIME.EXE /QUERY OBJ:APP /SHORT” to obtain a list of the names and versions of available virtual applications.
-
-
-
-
-
-
-
/LOAD
-
Loads or imports a virtual application.
-
-
-
/LOADALL
-
Loads all applications into cache.
-
-
-
/REFRESHALL
-
Starts a publishing refresh for all applications.
-
-
-
/LAUNCHRESULT <UNIQUE ID>
-
Returns the launch result code to the process that launches sfttray.exe by using a global event and a memory mapped file that are based on the specified root name for the UNIQUE ID.¹
-
-
-
/SFTFILE <sft>
-
Optional switch used with /LOAD to specify the path to the application’s SFT file. If specified, the application is imported rather than loaded.
-
-
-
/EXIT
-
Closes the SFTTRAY program and all active virtual applications and removes the icon from the Windows notification area.
-
-
-
-
-
-
-**Note**
-¹ The */LAUNCHRESULT* command line parameter provides a means for the process that launches sfttray.exe to specify the root name for a global event and a memory mapped file that are used to return the launch result code to the process. The unique identifier name should start with “SFT-” to prevent the event name from getting virtualized when the launching process is invoked within a virtual environment. The memory mapped region will be 64 bits in size.
-
-To use this parameter, the launching process creates an event with the name “<UNIQUE ID>-result\_event”, a memory mapped file with the name “<UNIQUE ID>-result\_value”, and optionally an event with the name “<UNIQUE ID>-shutdown\_event”, and then the launching process launches sfttray.exe and waits on the event to be signaled. After the event “<UNIQUE ID>-result\_event” is signaled, the launching process retrieves the 64-bit return code from the memory mapped region.
-
-If the optional event “<UNIQUE ID>-shutdown\_event” exists when the virtual application exits, sfttray.exe opens and signals the event. The launching process waits on this shutdown event if it needs to determine when the virtual application exits.
-
-
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/side-by-side-privatization-failed-dialog-box--app-v-46-sp1-.md b/mdop/appv-v4/side-by-side-privatization-failed-dialog-box--app-v-46-sp1-.md
deleted file mode 100644
index ced6882390..0000000000
--- a/mdop/appv-v4/side-by-side-privatization-failed-dialog-box--app-v-46-sp1-.md
+++ /dev/null
@@ -1,38 +0,0 @@
----
-title: Side-by-side Privatization Failed Dialog Box (App-V 4.6 SP1)
-description: Side-by-side Privatization Failed Dialog Box (App-V 4.6 SP1)
-author: dansimp
-ms.assetid: bcdb9b82-b53d-4a36-9f5d-71c021d4be28
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Side-by-side Privatization Failed Dialog Box (App-V 4.6 SP1)
-
-
-The Side-by-side assembly privatization failed. You can find more information about the side-by-side assemblies in the Sequencer log file which is located in the following directory:
-
-<App-V Sequencer installation drive> \\**Program Files** \\ **Microsoft Application Virtualization Sequencer** \\ **Logs**
-
-Install public versions of the required assemblies on the computer running the App-V Sequencer before you sequence the application. The same assemblies must also be installed on all computers running the App-V client before you deploy the package.
-
-## Related topics
-
-
-[Dialog Boxes (AppV 4.6 SP1)](dialog-boxes--appv-46-sp1-.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/software-audit-reportserver.md b/mdop/appv-v4/software-audit-reportserver.md
deleted file mode 100644
index 9efbb49955..0000000000
--- a/mdop/appv-v4/software-audit-reportserver.md
+++ /dev/null
@@ -1,58 +0,0 @@
----
-title: Software Audit Report
-description: Software Audit Report
-author: dansimp
-ms.assetid: 55a49ed2-f331-40d3-add6-8e5fcd6816fd
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Software Audit Report
-
-
-Use the Software Audit Report to list the usage information during the reporting period for all applications defined in the database. You can use this report to determine which applications are the most heavily used.
-
-For each application, the Software Audit Report lists the following information:
-
-- Number of sessions—Number of times an application was used
-
-The Software Audit Report also includes a summary of the total usage per application.
-
-When you create a report, you specify the parameters that are used for collecting the data when the report is run.
-
-Reports are not run automatically; you must run them explicitly to generate output data. The length of time it takes to run this report is determined by the amount of data collected in the data store.
-
-After you run a report and the output is displayed in the Application Virtualization Server Management Console, you can export the report into the following formats:
-
-- Adobe Acrobat (PDF)
-
-- Microsoft Office Excel
-
-## Related topics
-
-
-[How to Create a Report](how-to-create-a-reportserver.md)
-
-[How to Delete a Report](how-to-delete-a-reportserver.md)
-
-[How to Export a Report](how-to-export-a-reportserver.md)
-
-[How to Print a Report](how-to-print-a-reportserver.md)
-
-[How to Run a Report](how-to-run-a-reportserver.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/stand-alone-delivery-scenario-for-application-virtualization-clients.md b/mdop/appv-v4/stand-alone-delivery-scenario-for-application-virtualization-clients.md
deleted file mode 100644
index 224b3b7a04..0000000000
--- a/mdop/appv-v4/stand-alone-delivery-scenario-for-application-virtualization-clients.md
+++ /dev/null
@@ -1,58 +0,0 @@
----
-title: Stand-Alone Delivery Scenario for Application Virtualization Clients
-description: Stand-Alone Delivery Scenario for Application Virtualization Clients
-author: dansimp
-ms.assetid: 7545b468-f58a-4504-a6d5-3c2d303731c4
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Stand-Alone Delivery Scenario for Application Virtualization Clients
-
-
-The Stand-Alone Delivery Scenario enables you to realize the benefits of Microsoft Application Virtualization in situations where no servers are available to support other methods of deploying your virtual applications.
-
-**Note**
-It is assumed that you have already installed the Application Virtualization Sequencer in preparation for the stand-alone scenario. For more information, see [How to Install the Application Virtualization Sequencer](how-to-install-the-application-virtualization-sequencer.md).
-
-
-
-## In This Section
-
-
-[Stand-Alone Delivery Scenario Overview](stand-alone-delivery-scenario-overview.md)
-Provides a general overview of the benefits of a stand-alone Application Virtualization deployment scenario.
-
-[How to Manually Install the Application Virtualization Client](how-to-manually-install-the-application-virtualization-client.md)
-Provides a step-by-step procedure for installing the Application Virtualization Client software.
-
-[How to Publish a Virtual Application on the Client](how-to-publish-a-virtual-application-on-the-client.md)
-Provides command-line procedures for publishing an application package, using either Windows Installer or SFTMIME.
-
-## Reference
-
-
-[Application Virtualization Client Installer Command-Line Parameters](application-virtualization-client-installer-command-line-parameters.md)[SFTMIME Command Reference](sftmime--command-reference.md)
-
-## Related topics
-
-
-[Application Virtualization Client Hardware and Software Requirements](application-virtualization-client-hardware-and-software-requirements.md)
-
-[How to Install the Application Virtualization Sequencer](how-to-install-the-application-virtualization-sequencer.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/stand-alone-delivery-scenario-overview.md b/mdop/appv-v4/stand-alone-delivery-scenario-overview.md
deleted file mode 100644
index d01a132c43..0000000000
--- a/mdop/appv-v4/stand-alone-delivery-scenario-overview.md
+++ /dev/null
@@ -1,52 +0,0 @@
----
-title: Stand-Alone Delivery Scenario Overview
-description: Stand-Alone Delivery Scenario Overview
-author: dansimp
-ms.assetid: b109f309-f3c1-43af-996f-2a9b138dd171
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Stand-Alone Delivery Scenario Overview
-
-
-The stand-alone delivery scenario is an ideal application virtualization solution for environments where either low bandwidth connectivity or no connectivity limits the ability of the Application Virtualization Desktop Client to stream applications from centralized servers. In these environments, users often work remotely and device owners install applications by using Windows Installer files.
-
-You can use the Application Virtualization Sequencer to create sequenced applications that include Windows Installer files. These packages include the virtualized applications, publication information, and the necessary installer routines for installing the packages on the client systems. The installer adds the virtual application package to the Microsoft Application Virtualization Desktop Client. The publication information is configured to load applications from a local location rather than stream them across a WAN. Users can temporarily connect to a network to retrieve the Windows Installer files or can run them from a DVD.
-
-The stand-alone delivery scenario provides users the following benefits:
-
-- Simple deployment operation.
-
-- Network and servers not needed at runtime.
-
-- Applications pre-cached and available to all users.
-
-The stand-alone delivery scenario has the following limitations:
-
-- Built-in, automated reporting is unavailable; reports must be generated with external reporting tools.
-
-- Applications must be delivered to the client manually like the original Windows Installer files.
-
-## Related topics
-
-
-[How to Manually Install the Application Virtualization Client](how-to-manually-install-the-application-virtualization-client.md)
-
-[How to Publish a Virtual Application on the Client](how-to-publish-a-virtual-application-on-the-client.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/streaming-page-learn-more.md b/mdop/appv-v4/streaming-page-learn-more.md
deleted file mode 100644
index f46ecd595d..0000000000
--- a/mdop/appv-v4/streaming-page-learn-more.md
+++ /dev/null
@@ -1,47 +0,0 @@
----
-title: Streaming Page
-description: Streaming Page
-author: dansimp
-ms.assetid: a69a57a0-1bbe-4604-840d-bfa87ec463e1
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Streaming Page
-
-
-Use the **Streaming** page to optimize the virtual application package. During this step, the App-V Sequencer evaluates and configures the virtual application package so that it runs more efficiently when the package is deployed to target computers.
-
-**Note**
-You only have to perform the following tasks if you plan to stream the package across the network.
-
-
-
-This page contains the following elements:
-
-**Run Selected**
-Runs and optimizes only the specified programs saved in the virtual application package.
-
-**Run All**
-Runs all the programs saved in the virtual application package.
-
-## Related topics
-
-
-[Create New Package Wizard (AppV 4.6 SP1)](create-new-package-wizard---appv-46-sp1-.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/support-for-client-reporting-over-http.md b/mdop/appv-v4/support-for-client-reporting-over-http.md
deleted file mode 100644
index 23aa56eca5..0000000000
--- a/mdop/appv-v4/support-for-client-reporting-over-http.md
+++ /dev/null
@@ -1,108 +0,0 @@
----
-title: Support for Client Reporting over HTTP
-description: Support for Client Reporting over HTTP
-author: dansimp
-ms.assetid: 4a26ac80-1fb5-4c05-83de-4d06793f7bf2
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 08/30/2016
----
-
-
-# Support for Client Reporting over HTTP
-
-
-Version 4.6 of the App-V client now supports the use of HTTP communication when sending client reporting data to the publishing server. This feature supports scenarios where a customer has implemented a custom HTTP(S) publishing server that is configured to collect and process client data.
-
-For more information on HTTP publishing servers, see
-
-## Client Reporting over HTTP
-
-
-The client starts collecting data when it receives a “REPORTING=”TRUE””attribute in the publishing refresh response XML from the publishing server. When this attribute is received, the client sends any accumulated data to the publishing server that sent the publishing refresh. The details of this process are as follows:
-
-- The client sends an HTTP GET request to the publishing server for a publishing refresh. The header of this message contains an “AppV-Op:Refresh” custom header that the custom HTTP(S) publishing server uses to identify the message type.
-
-- The publishing server then sends the publishing refresh response XML that contains a “REPORTING=”TRUE”” value.
-
-- The client then sends an HTTP POST request to the publishing server along with the reporting data that has been gathered since the previous refresh. The header of this message contains an “AppV-Op:Report” custom header that the custom HTTP(S) publishing server uses to identify the message type.
-
-The following schema gives specific details of the package and the application data that is sent to the server.
-
-```xml
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-```
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/sxs-conflict-detected-dialog-box--app-v-46-sp1-.md b/mdop/appv-v4/sxs-conflict-detected-dialog-box--app-v-46-sp1-.md
deleted file mode 100644
index 8e3965c0c2..0000000000
--- a/mdop/appv-v4/sxs-conflict-detected-dialog-box--app-v-46-sp1-.md
+++ /dev/null
@@ -1,38 +0,0 @@
----
-title: SXS Conflict Detected Dialog Box (App-V 4.6 SP1)
-description: SXS Conflict Detected Dialog Box (App-V 4.6 SP1)
-author: dansimp
-ms.assetid: 7cbb67ba-cc11-4f10-b903-4a6af233eacb
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# SXS Conflict Detected Dialog Box (App-V 4.6 SP1)
-
-
-The application you are installing requires 64-bit assemblies. You can find more information about the side-by-side assemblies in the Sequencer log file which is located in the following directory:
-
-<App-V Sequencer installation drive> \\**Program Files** \\ **Microsoft Application Virtualization Sequencer** \\ **Logs**
-
-Install public versions of the required 64-bit assemblies on the computer running the App-V Sequencer before sequencing this application. You must also install the assemblies on the computer running the App-V client before you deploy this package.
-
-## Related topics
-
-
-[Dialog Boxes (AppV 4.6 SP1)](dialog-boxes--appv-46-sp1-.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/system-error-reportserver.md b/mdop/appv-v4/system-error-reportserver.md
deleted file mode 100644
index b94b419d2f..0000000000
--- a/mdop/appv-v4/system-error-reportserver.md
+++ /dev/null
@@ -1,54 +0,0 @@
----
-title: System Error Report
-description: System Error Report
-author: dansimp
-ms.assetid: 4081db2f-92a6-4928-a26b-757048159094
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# System Error Report
-
-
-Generate the System Error Report to track the number of errors and warnings logged over time during the specified reporting period for the specified server, for the specified server group.
-
-This report generates a bar graph that displays the fatal errors, errors, and log warnings in ascending order based on the time the messages were logged.
-
-When you create a report, you specify the parameters that are used for collecting the data when the report is run.
-
-Reports are not run automatically; you must run them explicitly to generate output data. The length of time it takes to run this report is determined by the amount of data collected in the data store.
-
-After you run a report and the output is displayed in the Application Virtualization Server Management Console, you can export the report into the following formats:
-
-- Adobe Acrobat (PDF)
-
-- Microsoft Office Excel
-
-## Related topics
-
-
-[How to Create a Report](how-to-create-a-reportserver.md)
-
-[How to Delete a Report](how-to-delete-a-reportserver.md)
-
-[How to Export a Report](how-to-export-a-reportserver.md)
-
-[How to Print a Report](how-to-print-a-reportserver.md)
-
-[How to Run a Report](how-to-run-a-reportserver.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/system-utilization-reportserver.md b/mdop/appv-v4/system-utilization-reportserver.md
deleted file mode 100644
index 5bccc4c9ab..0000000000
--- a/mdop/appv-v4/system-utilization-reportserver.md
+++ /dev/null
@@ -1,67 +0,0 @@
----
-title: System Utilization Report
-description: System Utilization Report
-author: dansimp
-ms.assetid: 4d490d15-2d1f-4f2c-99bb-0685447c0672
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# System Utilization Report
-
-
-Use the System Utilization Report to graph the total daily system usage. You can use this report to determine the load on your Application Virtualization System.
-
-This report tracks the usage over time during the reporting period for the specified server or for the server group.
-
-The System Utilization Report also graphs the following system usage:
-
-- Usage by day of the week
-
-- Usage by hour of the day
-
-The System Utilization Report also includes a summary of the total system usage for specific users and total session counts.
-
-When you create a report, you specify the parameters that are used for collecting the data when the report is run.
-
-Reports are not run automatically; you must run them explicitly to generate output data. The length of time it takes to run this report is determined by the amount of data collected in the data store.
-
-After you run a report and the output is displayed in the Application Virtualization Server Management Console, you can export the report into the following formats:
-
-- Adobe Acrobat (PDF)
-
-- Microsoft Office Excel
-
-**Note**
-The App-V server name reported from the clients must be part of the Default Server Group in order for the System Utilization report to show data. For example, if you are using multiple servers with a Network Load Balancer (NLB), you must add the NLB cluster name to the Default Server Group.
-
-
-
-## Related topics
-
-
-[How to Create a Report](how-to-create-a-reportserver.md)
-
-[How to Delete a Report](how-to-delete-a-reportserver.md)
-
-[How to Export a Report](how-to-export-a-reportserver.md)
-
-[How to Print a Report](how-to-print-a-reportserver.md)
-
-[How to Run a Report](how-to-run-a-reportserver.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/target-os-page-learn-more.md b/mdop/appv-v4/target-os-page-learn-more.md
deleted file mode 100644
index 34db517496..0000000000
--- a/mdop/appv-v4/target-os-page-learn-more.md
+++ /dev/null
@@ -1,47 +0,0 @@
----
-title: Target OS Page
-description: Target OS Page
-author: dansimp
-ms.assetid: 003fd992-0a7e-494e-9e75-4dd5e0927e15
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Target OS Page
-
-
-Use the **Target OS** page to specify which operating systems in your environment can run this virtual application package.
-
-**Note**
-The operating systems specified on this page can only run this virtual application package if the application you are sequencing supports the operating systems specified. Review the supported operating systems for the application you are sequencing to ensure compatibility.
-
-
-
-This page contains the following elements:
-
-**Allow this package to run on any operating system**
-Enables the virtual application package to be installed and run on all supported operating systems.
-
-**Allow this package to only run on the following operating systems**
-Enables the virtual application package to be installed and run only on the selected supported operating systems.
-
-## Related topics
-
-
-[Create New Package Wizard (AppV 4.6 SP1)](create-new-package-wizard---appv-46-sp1-.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/tasks-for-the-application-virtualization-sequencer--app-v-46-sp1-.md b/mdop/appv-v4/tasks-for-the-application-virtualization-sequencer--app-v-46-sp1-.md
deleted file mode 100644
index f3df4eb7f8..0000000000
--- a/mdop/appv-v4/tasks-for-the-application-virtualization-sequencer--app-v-46-sp1-.md
+++ /dev/null
@@ -1,61 +0,0 @@
----
-title: Tasks for the Application Virtualization Sequencer (App-V 4.6 SP1)
-description: Tasks for the Application Virtualization Sequencer (App-V 4.6 SP1)
-author: dansimp
-ms.assetid: 58597af9-6a62-4588-ab41-dbf6b7026267
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Tasks for the Application Virtualization Sequencer (App-V 4.6 SP1)
-
-
-Use any of the following links for more information about using the App-V Sequencer.
-
-## In This Section
-
-
-[How to Determine Which Type of Application to Sequence (App-V 4.6 SP1)](how-to-determine-which-type-of-application-to-sequence---app-v-46-sp1-.md)
-Describes how to determine the type of application you want to sequence.
-
-[How to Sequence a New Standard Application (App-V 4.6 SP1)](how-to-sequence-a-new-standard-application--app-v-46-sp1-.md)
-Describes how to sequence a new standard application.
-
-[How to Sequence a New Add-on or Plug-in Application (App-V 4.6 SP1)](how-to-sequence-a-new-add-on-or-plug-in-application--app-v-46-sp1-.md)
-Describes how to sequence a new add-on or plug-in application.
-
-[How to Sequence a New Middleware Application (App-V 4.6 SP1)](how-to-sequence-a-new-middleware-application--app-v-46-sp1-.md)
-Describes how to sequence a new middleware application.
-
-[How to Modify an Existing Virtual Application Package (App-V 4.6 SP1)](how-to-modify-an-existing-virtual-application-package--app-v-46-sp1-.md)
-Describes how to modify an existing virtual application package.
-
-[How to Apply a Package Accelerator to Create a Virtual Application Package (App-V 4.6 SP1)](how-to-apply-a-package-accelerator-to-create-a-virtual-application-package---app-v-46-sp1-.md)
-Describes how to use a Package Accelerator to create a new virtual application package.
-
-[How to Apply an App-V Project Template (App-V 4.6 SP1)](how-to-apply-an-app-v-project-template--app-v-46-sp1-.md)
-Describes how to use a project template to apply standard package settings to a new virtual application package.
-
-[How to Create App-V Package Accelerators (App-V 4.6 SP1)](how-to-create-app-v-package-accelerators--app-v-46-sp1-.md)
-Describes how create a new Package Accelerator.
-
-## Related topics
-
-
-[Application Virtualization Sequencer](application-virtualization-sequencer.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/tasks-for-the-application-virtualization-sequencer.md b/mdop/appv-v4/tasks-for-the-application-virtualization-sequencer.md
deleted file mode 100644
index 88d5d425f0..0000000000
--- a/mdop/appv-v4/tasks-for-the-application-virtualization-sequencer.md
+++ /dev/null
@@ -1,55 +0,0 @@
----
-title: Tasks for the Application Virtualization Sequencer
-description: Tasks for the Application Virtualization Sequencer
-author: dansimp
-ms.assetid: 398018f4-297a-440d-b614-23f0ab03e7bd
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Tasks for the Application Virtualization Sequencer
-
-
-The links in this section provide the necessary information to complete each associated Microsoft Application Virtualization (App-V) task.
-
-## In This Section
-
-
-[How to Sequence a New Application](how-to-sequence-a-new-application.md)
-Specifies the tasks associated with sequencing a new application.
-
-[How to Create a Virtual Environment for a Web-Based Application](how-to-create-a-virtual-environment-for-a-web-based-application.md)
-Specifies how to create separate web environments for virtual applications.
-
-[How to Upgrade a Sequenced Virtual Application Package](how-to-upgrade-a-sequenced-virtual-application-package.md)
-Specifies how to upgrade an existing virtual application package.
-
-[How to Branch a Package](how-to-branch-a-package.md)
-Specifies how to branch an existing virtual application package so you can run multiple versions of the same package.
-
-[How to Upgrade a Package Using the Open Package Command](how-to-upgrade-a-package-using-the-open-package-command.md)
-Specifies how to upgrade an existing virtual application package using the command line.
-
-[How to Manage Virtual Applications Using the Command Line](how-to-manage-virtual-applications-using-the-command-line.md)
-Specifies how to manage virtual applications using the command line.
-
-## Related topics
-
-
-[Application Virtualization Sequencer Online Help](application-virtualization-sequencer-online-help.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/troubleshooting-application-virtualization-sequencer-issues.md b/mdop/appv-v4/troubleshooting-application-virtualization-sequencer-issues.md
deleted file mode 100644
index c7285083d5..0000000000
--- a/mdop/appv-v4/troubleshooting-application-virtualization-sequencer-issues.md
+++ /dev/null
@@ -1,86 +0,0 @@
----
-title: Troubleshooting Application Virtualization Sequencer Issues
-description: Troubleshooting Application Virtualization Sequencer Issues
-author: dansimp
-ms.assetid: 2712094b-a0bc-4643-aced-5415535f3fec
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Troubleshooting Application Virtualization Sequencer Issues
-
-
-This topic includes information that you can use to help troubleshoot general issues on the Application Virtualization (App-V) Sequencer.
-
-## Creating an SFTD File by Using the App-V Sequencer Increases the Version Number Unexpectedly
-
-
-Use the command line to generate a new .sft file. To create the .sft file by using the command line, enter the following at a command prompt:
-
-**mkdiffpkg.exe <base SFT file name> <diff SFT file name>**
-
-## File Name in OSD File Is Not Correct After Package Upgrade
-
-
-When you open a package for upgrade, you should specify the root Q:\\ drive as the output location for the package. Do not specify an associated file name with the output location.
-
-## Microsoft Word 2003 Default Install Results in an Error When Streamed to a Client
-
-
-When you stream Microsoft Word 2003 to a client, an error is returned, but Microsoft Word continues to run.
-
-**Solution**
-
-Resequence the virtual application package and select **Full Install**.
-
-## Active Upgrade Does Not Work When You Create a Dependent Package
-
-
-When you create a dependent package by using active upgrade and add new registry entries, it appears to function correctly, but the updated registry entries are not available.
-
-**Solution**
-
-Registry settings are always stored with the original version of the package, so updates to the package will not appear to be available unless you repair the original package.
-
-## Detailed information is not visible for Microsoft Office 2007 documents by using the properties page
-
-
-When you try to view detailed information associated with a Microsoft Office 2007 document by using the properties page, the detailed information is not visible.
-
-**Solution**
-
-App-V does not support the required shell extensions for these property pages.
-
-## Some registry keys are not captured when you sequence 16-bit applications
-
-
-In App-V 4.5, registry hooking has been moved from kernel mode to user mode. If you want to sequence a 16-bit application or an application that uses a 16-bit installer, you must first configure the sequencer computer so that the process runs in its own copy of the Windows NT Virtual DOS Machine (NTVDM).
-
-**Solution**
-
-Before you sequence the application, set the following global REGSZ registry key value to "yes" on the sequencing computer:
-
-HKLM\\SYSTEM\\CurrentControlSet\\Control\\WOW\\DefaultSeparateVDM
-
-You must restart the computer before this takes effect.
-
-## Related topics
-
-
-[Application Virtualization Sequencer](application-virtualization-sequencer.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/troubleshooting-certificate-permission-issues.md b/mdop/appv-v4/troubleshooting-certificate-permission-issues.md
deleted file mode 100644
index 9b05d6624b..0000000000
--- a/mdop/appv-v4/troubleshooting-certificate-permission-issues.md
+++ /dev/null
@@ -1,47 +0,0 @@
----
-title: Troubleshooting Certificate Permission Issues
-description: Troubleshooting Certificate Permission Issues
-author: dansimp
-ms.assetid: 06b8cbbc-93fd-44aa-af39-2d780792d3c3
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Troubleshooting Certificate Permission Issues
-
-
-After the installation of App-V 4.5, if the private key has not been configured with the proper ACL for the Network Service, an event is logged in the NT Event Log and an entry is placed in the `Sft-server.log` file.
-
-## Error Messages
-
-
-### Windows Server 2003
-
-Event ID 36870—A fatal error occurred when attempting to access the SSL server credential private key. The error code returned from the cryptographic module is 0x80090016.
-
-### Windows Server 2008
-
-Event ID 36870—A fatal error occurred when attempting to access the SSL server credential private key. The error code returned from the cryptographic module is 0x8009030d.
-
-## Sft-server.log
-
-
-The following error is placed in the `sft-server.log` file located in the `%ProgramFiles%\Microsoft System Center App Virt Management Server\App Virt Management Server\logs` directory:
-
-Certificate could not be loaded. Error code \[-2146893043\]. Make sure that the Network Service account has proper access to the certificate and its corresponding private key file.
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/troubleshooting-information-for-the-application-virtualization-client.md b/mdop/appv-v4/troubleshooting-information-for-the-application-virtualization-client.md
deleted file mode 100644
index a8b8781132..0000000000
--- a/mdop/appv-v4/troubleshooting-information-for-the-application-virtualization-client.md
+++ /dev/null
@@ -1,98 +0,0 @@
----
-title: Troubleshooting Information for the Application Virtualization Client
-description: Troubleshooting Information for the Application Virtualization Client
-author: dansimp
-ms.assetid: 260a8dad-847f-4ec0-b7dd-6e6bc52017ed
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Troubleshooting Information for the Application Virtualization Client
-
-
-This topic includes information that you can use to troubleshoot various issues on the Application Virtualization (App-V) Client.
-
-## Publishing Refresh Is Very Slow
-
-
-If publishing refresh on a specific computer takes much longer than expected and if the client is configured to use the **IconSourceRoot** setting, determine whether **IconSourceRoot** contains a nonvalid URL. A nonvalid URL will cause very long delays during publishing refresh.
-
-## Users Cannot Connect to the Server and Go into Disconnected Operations Mode
-
-
-When you are using an App-V Management Server configured with the RTSPS protocol, if the users are unable to connect and they go into disconnected operations mode, determine whether the certificate that is being used on the server is valid. A nonvalid certificate will prevent users from connecting and will cause them to go into disconnected operations mode.
-
-## Users Experience Slow Performance When Applications Are Not Fully Cached
-
-
-When applications are not fully cached, users might occasionally experience temporary slow or intermittent performance when they start or use the application. There are several possible reasons this can occur—for example, when the App-V Client is in the process of auto-loading an application or when an Out Of Sequence request is being processed. When the applications are fully cached, these problems will no longer occur.
-
-## Error Displayed After an Update Is Removed
-
-
-You must use the correct Windows Installer 3.1 command format to remove an update from the App-V Client, as follows:
-
-`Msiexec /I {F82584A0-D706-4D2D-9BC1-7E6D8BE3BB0F} MSIPATCHREMOVE={BE3DD018-9A1F-40FD-9538-C0A995CBD254} /qb /l*v "Uninstall.log"`
-
-Using the older command format `msiexec /package /uninstall ` will cause error 6003 "Application Virtualization client could not be started".
-
-## Error Code 0A-0000E01E Occurs When You Try to Start an Application
-
-
-Error code 0A-0000E01E indicates that the sequenced application package might be corrupt. The solution is to resequence the package.
-
-## Users Cannot Access Files They Have Created on the Q: Drive
-
-
-If users save files to the **Q:** drive, they cannot retrieve them because they do not have read rights to the drive. Users should not save files to the **Q:** drive.
-
-## User Is Prompted with a 1D1 Error
-
-
-When the file streaming URL is incorrectly set in the Open Software Descriptor (OSD) file, the App-V Client returns a 1d1 error instead of a “file not found” error. This error indicates that the application start failed and the user has been forced into disconnected operations mode. Correct the file streaming URL.
-
-## Incorrect Icons Associated with Some Applications
-
-
-When an icon is to be used in a publishing operation, the App-V Client first determines whether it already has a cached copy of the icon, by looking in the icon cache for an item whose original source path matches the path of the icon given to the publishing operation. If the App-V Client finds a match, it will use the already-cached icon; otherwise, it will download the new icon into the cache. If the path to the icon is a scratch directory or if it gets reused for new icons or packages, the lookup in the cache might pick the wrong icon from a previous operation.
-
-## Users Are Prompted for Credentials When Starting an Application
-
-
-If a user attempts to start a virtual application to which the system administrator has restricted access, the user might be prompted to enter credentials. The user should type the user name and password for an account that has permission to launch the application and then press ENTER.
-
-## Publishing Refresh Fails After Upgrading the App-V Client to Version 4.5
-
-
-If the user data directory was previously placed in a non-standard location (%*AllUsersProfile*%\\Documents\\SoftGrid Client\\Users\\%*username*%), users who do not have administrator privileges on the computer will find that publishing refresh fails after the App-V Client is upgraded. During the upgrade, the App-V Client global data directory and all its subdirectories are configured with restricted access rights for administrators only. You can avoid this problem by changing the user data directory before upgrading so that it is not a subdirectory of the global data directory.
-
-## Reboot Required After Install Failure
-
-
-If the client install fails for any reason and if subsequent attempts to install the client also fail, check the Windows Installer log to see whether it shows an error “sftplay failed, error=1072”. If so, restart the computer before trying to install the client again.
-
-## Repairing a Corrupted Virtual Application
-
-
-If for any reason a virtual application package installed using a Windows Installer Package (MSI) file becomes corrupted, reinstall the package. The Repair function available in the Windows Installer will not update the user volumes.
-
-## Related topics
-
-
-[Application Virtualization Client Reference](application-virtualization-client-reference.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/troubleshooting-information-for-the-application-virtualization-server.md b/mdop/appv-v4/troubleshooting-information-for-the-application-virtualization-server.md
deleted file mode 100644
index df335aaec7..0000000000
--- a/mdop/appv-v4/troubleshooting-information-for-the-application-virtualization-server.md
+++ /dev/null
@@ -1,43 +0,0 @@
----
-title: Troubleshooting Information for the Application Virtualization Server
-description: Troubleshooting Information for the Application Virtualization Server
-author: dansimp
-ms.assetid: e9d43d9b-84f2-4d1b-bb90-a13740151e0c
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Troubleshooting Information for the Application Virtualization Server
-
-
-This topic includes information that you can use to troubleshoot various issues on the Application Virtualization (App-V) Servers.
-
-## Warning Message 25017 in Setup Log After Installing the Server
-
-
-You might find the following message in the server setup log after installation.
-
-*Warning 25017. The installation Program could not create the Active Directory marker object for the server. The account used to install did not have the sufficient rights to write to Active Directory or Active Directory was unavailable.*
-
-The App-V Management or Streaming Server installer creates a Service Connection Point entry under the Computer object in Active Directory Domain Services (AD DS) that corresponds to the computer on which the server is installed if the account used to run the installer has the appropriate rights. Failure to create this entry will not cause the install to fail and this should not otherwise affect the functioning of the product. The likely cause of any failure is that the user account used to run the install did not have sufficient rights to write to AD DS. Although registering the App-V server in AD DS is optional, one benefit of doing so enables centralized management tools to locate the App-V server for inventory and management purposes.
-
-## Related topics
-
-
-[Application Virtualization Server](application-virtualization-server.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/troubleshooting-the-application-virtualization-sequencer.md b/mdop/appv-v4/troubleshooting-the-application-virtualization-sequencer.md
deleted file mode 100644
index c832ebe830..0000000000
--- a/mdop/appv-v4/troubleshooting-the-application-virtualization-sequencer.md
+++ /dev/null
@@ -1,81 +0,0 @@
----
-title: Troubleshooting the Application Virtualization Sequencer
-description: Troubleshooting the Application Virtualization Sequencer
-author: dansimp
-ms.assetid: 12ea8367-0b84-44e1-a885-e0539486556b
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Troubleshooting the Application Virtualization Sequencer
-
-
-This topic includes information that you can use to help troubleshoot general issues on the Application Virtualization (App-V) Sequencer.
-
-## Creating an SFTD File by Using the App-V Sequencer Increases the Version Number Unexpectedly
-
-
-The version number associated with an SFTD file increases unexpectedly.
-
-**Solution**
-
-Use the command line to generate a new .sft file. To create the .sft file by using the command line, enter the following at a command prompt:
-
-**mkdiffpkg.exe <base SFT file name> <diff SFT file name>**
-
-## File Name in OSD File Is Not Correct After Package Upgrade
-
-
-After you upgrade an existing package, the file name is not correct.
-
-**Solution**
-
-When you open a package for upgrade, you should specify the root Q:\\ drive as the output location for the package. Do not specify an associated file name with the output location.
-
-## Microsoft Word 2003 Default Install Results in an Error When Streamed to a Client
-
-
-When you stream Microsoft Word 2003 to a client, an error is returned but Microsoft Word continues to run.
-
-**Solution**
-
-Resequence the virtual application package, and select **Full Install**.
-
-## Package Upgrade Does Not Work When You Create a Dependent Package
-
-
-When you create a dependent package by using package upgrade and add new registry entries, it appears to function correctly but the updated registry entries are not available.
-
-**Solution**
-
-Registry settings are always stored with the original version of the package, so updates to the package will not appear to be available unless you repair the original package.
-
-## Error When Trying to Sequence .NET 2.0
-
-
-When you sequence a package that requires .NET 2.0, you get an error.
-
-**Solution**
-
-Sequencing packages that require .NET 2.0 is not supported.
-
-## Related topics
-
-
-[Application Virtualization Sequencer](application-virtualization-sequencer.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/type-of-application-page--learn-more-.md b/mdop/appv-v4/type-of-application-page--learn-more-.md
deleted file mode 100644
index 529c2aac7d..0000000000
--- a/mdop/appv-v4/type-of-application-page--learn-more-.md
+++ /dev/null
@@ -1,45 +0,0 @@
----
-title: Type of Application Page (Learn More)
-description: Type of Application Page (Learn More)
-author: dansimp
-ms.assetid: d1262d16-7b14-441e-8500-7974bf68d196
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Type of Application Page (Learn More)
-
-
-Use the **Type of Application** page to specify the type of application you are sequencing. It is important to understand and select the correct type of application you are sequencing so you can ensure you take the correct steps toward successful package creation.
-
-This page contains the following elements:
-
-**Standard Application (default)**
-Select this option to create a package that contains an application or a suite of applications. You should select this option for most applications you plan to sequence.
-
-**Add-on or Plug-in**
-Select this option to create a package that extends the functionality of a standard application; for example, a plug-in for Microsoft Excel.
-
-**Middleware**
-Select this option to create a package that is required by a standard application, for example, the Microsoft .NET Framework.
-
-## Related topics
-
-
-[Create New Package Wizard (AppV 4.6 SP1)](create-new-package-wizard---appv-46-sp1-.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/unload-app.md b/mdop/appv-v4/unload-app.md
deleted file mode 100644
index e9b1a2c013..0000000000
--- a/mdop/appv-v4/unload-app.md
+++ /dev/null
@@ -1,86 +0,0 @@
----
-title: UNLOAD APP
-description: UNLOAD APP
-author: dansimp
-ms.assetid: f0d729ae-8772-498b-be11-1a4b35499c53
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# UNLOAD APP
-
-
-Unloads the application and all other applications in the package from the file system cache.
-
-`SFTMIME UNLOAD APP:application [/LOG log-pathname | /CONSOLE | /GUI]`
-
-
-
-
-
-
-
-
-
Parameter
-
Description
-
-
-
-
-
APP:<application>
-
The name and version (optional) of the application to unload.
-
-
-
/LOG
-
If specified, output is logged to the specified path name.
-
-
-
/CONSOLE
-
If specified, output is presented in the active console window (default).
-
-
-
/GUI
-
If specified, output is presented in a Windows dialog box.
-
-
-
-
-
-
-For version 4.6, the following option has been added.
-
-
-
-
-
-
-
-
-
/LOGU
-
If specified, output is logged to the specified path name in UNICODE format.
If present, user settings will also be removed. (For more information, see the Important note later in this topic.)
-
-
-
/GLOBAL
-
If present, the package will be unpublished for all users on this computer.
-
-
-
/LOG
-
If specified, output is logged to the specified path name.
-
-
-
/CONSOLE
-
If specified, output is presented in the active console window (default).
-
-
-
/GUI
-
If specified, output is presented in a Windows dialog box.
-
-
-
-
-
-
-For version 4.6, the following option has been added.
-
-
-
-
-
-
-
-
-
/LOGU
-
If specified, output is logged to the specified path name in UNICODE format.
-
-
-
-
-
-
-**Important**
-Before you can run the **UNPUBLISH PACKAGE** command, the package must already have been added to the Application Virtualization Client.
-
-To use **GLOBAL**, **UNPUBLISH PACKAGE** must be run as local Administrator; otherwise, only **ClearApp** permission is needed.
-
-Using **UNPUBLISH PACKAGE** with **GLOBAL** removes any global file types and shortcuts for the package. **CLEAR** is not applicable.
-
-Using **UNPUBLISH PACKAGE** without **GLOBAL** removes the user shortcuts and file types for the package and, if **CLEAR** is set, also removes user settings and stops background loads under the user’s context.
-
-**UNPUBLISH PACKAGE** works on applications from the same package name or GUID that was used as the source ID for **ADD**, **EDIT**, and **PUBLISH PACKAGE**.
-
-**UNPUBLISH PACKAGE** always clears all the user settings, shortcuts, and file types regardless of the use of the /CLEAR switch.
-
-
-
-## Related topics
-
-
-[SFTMIME Command Reference](sftmime--command-reference.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/user-access-permissions-in-application-virtualization-client.md b/mdop/appv-v4/user-access-permissions-in-application-virtualization-client.md
deleted file mode 100644
index b5823c5aa0..0000000000
--- a/mdop/appv-v4/user-access-permissions-in-application-virtualization-client.md
+++ /dev/null
@@ -1,134 +0,0 @@
----
-title: User Access Permissions in Application Virtualization Client
-description: User Access Permissions in Application Virtualization Client
-author: dansimp
-ms.assetid: 7459374c-810c-45e3-b205-fdd1f8514f80
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# User Access Permissions in Application Virtualization Client
-
-
-On the **Permissions** tab on the **Properties** dialog box, accessible by right-clicking the **Application Virtualization** node in the Application Virtualization Client Management Console, administrators can grant users permissions to use the various client functions.
-
-**Note**
-Before changing users permissions, ensure that any permissions changes are consistent with the organization's guidelines for granting user permissions.
-
-
-
-The following table lists and describes the permissions that can be granted to users.
-
-
-
-
-
-
-
-
-
Permission Name
-
Description
-
-
-
-
-
Add applications
-
Register new applications by passing a new OSD file to the client by using sfttray.exe, sftmime.exe or the MMC.
-
-
-
Change file system cache size
-
Increase the size of the file system cache.
-
-
-
Change file system drive
-
Select a different preferred drive letter for the file system.
-
-
-
Change log settings
-
Change the log level or the log path for the client log file.
-
-
-
Change OSD files
-
Modify OSD files for registered applications and pass them into the client. This does not affect publishing refresh.
-
-
-
Clear application settings
-
Delete file types, shortcuts and any configurations for the current user.
-
-
-
Delete applications
-
Remove all references to an application from the file system and OSD cache for all users on the computer.
-
-
-
Import applications into the cache
-
Load application data directly from a specified SFT file into the file system cache. This affects all users.
-
-
-
Load applications into the cache
-
Start a load of the SFT file for an application from the configured source, such as an App-V Streaming Server. This loads the application for all users on the computer.
-
-
-
Lock and unlock applications in the cache
-
Prevent or allow applications from being unloaded from the file system cache. This affects all users on the computer.
-
-
-
Manage file type associations
-
Add, modify, or delete file type associations for the current user only.
-
-
-
Manage publishing refresh settings
-
Change settings that control the timing of publishing refreshes for all users on the computer.
-
-
-
Manage publishing servers
-
Add, modify, or delete publishing servers for all users on the computer. This permission implicitly includes permission to manage publishing refresh settings.
-
-
-
Publish shortcuts
-
Create new shortcuts to registered applications. The user must also have permission to create files in the local file system.
-
-
-
Repair applications
-
Remove application specific configurations for the current user without removing shortcuts or file type associations.
-
-
-
Start a publishing refresh
-
Start an unscheduled publishing refresh for the current user.
-
-
-
Toggle offline mode
-
Change the entire client from online to offline mode for all users.
-
-
-
Unload applications from the cache
-
Clear application data from the file system cache for all users without removing user-specific settings, shortcuts, or file type associations.
-
-
-
View all applications
-
Allow the user to see the virtual applications for all users registered on the computer.
-
-
-
-
-
-
-## Related topics
-
-
-[How to Change User Access Permissions](how-to-change-user-access-permissions.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/using-application-virtualization-servers-as-a-package-management-solution.md b/mdop/appv-v4/using-application-virtualization-servers-as-a-package-management-solution.md
deleted file mode 100644
index e41d0cb21b..0000000000
--- a/mdop/appv-v4/using-application-virtualization-servers-as-a-package-management-solution.md
+++ /dev/null
@@ -1,53 +0,0 @@
----
-title: Using Application Virtualization Servers as a Package Management Solution
-description: Using Application Virtualization Servers as a Package Management Solution
-author: dansimp
-ms.assetid: 41597355-e7bb-45e2-b300-7b1724419975
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Using Application Virtualization Servers as a Package Management Solution
-
-
-If you do not have an existing ESD system to deploy your Application Virtualization solution or do not wish to use one, you will need to install one or more Application Virtualization Management Servers as the core of your system architecture. The Application Virtualization Management Server requires a dedicated server computer and needs a Microsoft SQL Server database. The database can be on the same server, or it can be configured on a corporate database server that is accessible to the Application Virtualization Management Server over a high-speed LAN connection. In addition, you will need to install the Microsoft Application Virtualization Management Console, on either the Application Virtualization Management Server or on a designated management workstation, and you will need to install the Microsoft Application Virtualization Management Web Service, which can also be installed on the Application Virtualization Management Server or on a separate IIS server. The Application Virtualization Management Console is used to connect to the Application Virtualization Management Web Service, enabling the system administrator to interact with the Application Virtualization Management Server.
-
-**Note**
-Access to the applications is controlled by means of Security Groups in Active Directory Domain Services, so you will need to plan a process to set up a security group for each virtualized application and for managing which users are added to each group. The Application Virtualization Management Server administrator configures the server to use these Active Directory groups, and the server then automatically controls access to the packages based on Active Directory group membership.
-
-
-
-## In This Section
-
-
-[Overview of the Application Virtualization System Components](overview-of-the-application-virtualization-system-components.md)
-Lists and describes the primary components of the Microsoft Application Virtualization Management System.
-
-[Publishing Virtual Applications Using Application Virtualization Management Servers](publishing-virtual-applications-using-application-virtualization-management-servers.md)
-Provides a brief overview of how virtual applications are published in an Application Virtualization Server-based deployment scenario.
-
-[Planning Your Streaming Solution in an Application Virtualization Server-Based Implementation](planning-your-streaming-solution-in-an-application-virtualization-server-based-implementation.md)
-Describes available options for using Application Virtualization Streaming Servers in conjunction with your Application Virtualization Management Server-based implementation.
-
-## Related topics
-
-
-[Application Virtualization Server-Based Scenario](application-virtualization-server-based-scenario.md)
-
-[Planning for Application Virtualization System Deployment](planning-for-application-virtualization-system-deployment.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/using-electronic-software-distribution-as-a-package-management-solution.md b/mdop/appv-v4/using-electronic-software-distribution-as-a-package-management-solution.md
deleted file mode 100644
index 7106bf01e0..0000000000
--- a/mdop/appv-v4/using-electronic-software-distribution-as-a-package-management-solution.md
+++ /dev/null
@@ -1,49 +0,0 @@
----
-title: Using Electronic Software Distribution as a Package Management Solution
-description: Using Electronic Software Distribution as a Package Management Solution
-author: dansimp
-ms.assetid: 7d96ea70-3e7e-49fa-89cc-586804a10657
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Using Electronic Software Distribution as a Package Management Solution
-
-
-In Application Virtualization, after you have sequenced and tested a package, you need to deploy the virtual application package to the target computers. To accomplish this, you will need to determine where to put the package content and how to deliver it to the end user computers. An efficient, effective electronic software distribution–based deployment plan will help you avoid the situation where large numbers of end users computers need to retrieve the package content over slow network connections.
-
-If you currently have an electronic software distribution (ESD) system in daily operation, you can use it to handle all necessary management tasks in Application Virtualization. This means that you can effectively use your existing infrastructure to the best advantage, without the need to add new servers and application software or incur the additional administrative overhead that these would require. Ideally, if you have Microsoft Endpoint Configuration Manager deployed and operational, you will find that Configuration Manager has built-in capability for performing the Application Virtualization management tasks.
-
-For in-depth information about performing an ESD-based deployment, [Electronic Software Distribution-Based Scenario](electronic-software-distribution-based-scenario.md).
-
-## In This Section
-
-
-[Publishing Virtual Applications Using Electronic Software Distribution](publishing-virtual-applications-using-electronic-software-distribution.md)
-Describes the available ESD-based methods for distributing your sequenced applications to clients.
-
-[Planning Your Streaming Solution in an Electronic Software Distribution Implementation](planning-your-streaming-solution-in-an-electronic-software-distribution-implementation.md)
-Describes available options for using a streaming server to deploy your sequenced applications to clients.
-
-## Related topics
-
-
-[Electronic Software Distribution-Based Scenario](electronic-software-distribution-based-scenario.md)
-
-[Planning for Application Virtualization System Deployment](planning-for-application-virtualization-system-deployment.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/verify-applications-page--package-accelerators-.md b/mdop/appv-v4/verify-applications-page--package-accelerators-.md
deleted file mode 100644
index fa38068d5e..0000000000
--- a/mdop/appv-v4/verify-applications-page--package-accelerators-.md
+++ /dev/null
@@ -1,55 +0,0 @@
----
-title: Verify Applications Page (Package Accelerators)
-description: Verify Applications Page (Package Accelerators)
-author: dansimp
-ms.assetid: e58a37db-d042-453f-aa0d-2f324600a35b
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Verify Applications Page (Package Accelerators)
-
-
-Use the **Verify Applications** page to review the installer file dependencies that are saved with the package. These files are required when the Package Accelerator is used to create a new virtual application package.
-
-You can add or edit the following types of information. Only the application **Name** is required; however, you should provide as much information as possible to help ensure that a new virtual application package is created successfully when you use a package accelerator:
-
-- **Name**. You must specify a name.
-
-- **Publisher**. Optionally specify information about the application publisher.
-
-- **Version**. Optionally specify application version information.
-
-- **Language**. Optionally specify language information.
-
-This page contains the following elements:
-
-**Add**
-Adds a new installation file dependency that will be required when the Package Accelerator is applied.
-
-**Delete**
-Deletes a selected dependency file that is currently part of the Package Accelerator.
-
-**Edit**
-Enables you to edit the properties associated with the selected installer file’s dependency.
-
-## Related topics
-
-
-[Create Package Accelerator Wizard (AppV 4.6 SP1)](create-package-accelerator-wizard--appv-46-sp1-.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/virtual-application-package-additional-components.md b/mdop/appv-v4/virtual-application-package-additional-components.md
deleted file mode 100644
index 8fe48620bc..0000000000
--- a/mdop/appv-v4/virtual-application-package-additional-components.md
+++ /dev/null
@@ -1,49 +0,0 @@
----
-title: Virtual Application Package Additional Components
-description: Virtual Application Package Additional Components
-author: dansimp
-ms.assetid: 476b0f40-ebd6-4296-92fa-61fa9495c03c
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 08/30/2016
----
-
-
-# Virtual Application Package Additional Components
-
-
-The App-V Sequencer has detected a directory that contains 64-bit and 32-bit executables and/or dynamic-link library (.dll) files that depend on the same side-by-side assembly. Typically, the Sequencer creates private side-by-side assemblies for all public assemblies that are used by the package; however, it is not possible to create 32-bit and 64-bit versions of the private assemblies in the same directory.
-
-If the Sequencer detects a single conflict, it will perform the following actions:
-
-- Remove all of the existing 64-bit private assemblies in the entire package, whether or not the directory has a conflict.
-
-- Create only 32-bit versions of the private side-by-side assemblies.
-
-You should natively install public versions of all the required 64-bit assemblies on the computer running the Sequencer and on all App-V client computers.
-
-To locate the required existing public assemblies, open the directory where the package is saved and look in the **VFS** folder. For example, if the package root is **Q:\\MyApp**, when you sequence the application, look in **Q:\\MyApp\\VFS\\CSIDL\_Windows\\WinSxS\\Manifests** and locate all of the existing public assemblies. The 64-bit versions of these files will always start with the following text at the beginning of the manifest name: **amd64…**. The exact name and version of the assembly can be found in the associated manifest file.
-
-Use any of the following links to download and install the correct version of the required prerequisites:
-
-- [Microsoft Visual C++ 2005 Redistributable Package (x64)](https://go.microsoft.com/fwlink/?LinkId=152697)
-
-- [Microsoft Visual C++ 2005 SP1 Redistributable Package (x64)](https://go.microsoft.com/fwlink/?LinkId=152698)
-
-- [Microsoft Visual C++ 2008 Redistributable Package (x64)](https://go.microsoft.com/fwlink/?LinkId=152699)
-
-- [Microsoft Visual C++ 2008 SP1 Redistributable Package (x64)](https://go.microsoft.com/fwlink/?LinkId=152700)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/virtual-file-system-tab-keep.md b/mdop/appv-v4/virtual-file-system-tab-keep.md
deleted file mode 100644
index 290e0a1d2a..0000000000
--- a/mdop/appv-v4/virtual-file-system-tab-keep.md
+++ /dev/null
@@ -1,43 +0,0 @@
----
-title: Virtual File System Tab
-description: Virtual File System Tab
-author: dansimp
-ms.assetid: 9d084e2a-720d-4a25-9cd5-d0d70868b413
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Virtual File System Tab
-
-
-The **Virtual File System** tab allows you to view and modify the file-mapping information.
-
-## In This Section
-
-
-[About the Virtual File System Tab](about-the-virtual-file-system-tab.md)
-Provides general information about the **Virtual File System** tab.
-
-[How to Modify File-Mapping Information](how-to-modify-file-mapping-information.md)
-Provides the procedure to modify the file-mapping information by using the **Virtual File System** tab.
-
-## Related topics
-
-
-[Sequencer Console](sequencer-console.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/virtual-registry-tab-keep.md b/mdop/appv-v4/virtual-registry-tab-keep.md
deleted file mode 100644
index cd9e9a01da..0000000000
--- a/mdop/appv-v4/virtual-registry-tab-keep.md
+++ /dev/null
@@ -1,43 +0,0 @@
----
-title: Virtual Registry Tab
-description: Virtual Registry Tab
-author: dansimp
-ms.assetid: 25833383-24c4-40a1-b34c-73b2bd3f11e1
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Virtual Registry Tab
-
-
-Use the **Virtual Registry** tab to view and modify the virtual registry key information.
-
-## In This Section
-
-
-[About the Virtual Registry Tab](about-the-virtual-registry-tab.md)
-Provides general information about the **Virtual Registry** tab.
-
-[How to Modify Virtual Registry Key Information](how-to-modify-virtual-registry-key-information.md)
-Provides the procedure to modify the virtual registry key information by using the **Virtual Registry** tab.
-
-## Related topics
-
-
-[Sequencer Console](sequencer-console.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/virtual-services-tab-keep.md b/mdop/appv-v4/virtual-services-tab-keep.md
deleted file mode 100644
index 360df6d0a5..0000000000
--- a/mdop/appv-v4/virtual-services-tab-keep.md
+++ /dev/null
@@ -1,43 +0,0 @@
----
-title: Virtual Services Tab
-description: Virtual Services Tab
-author: dansimp
-ms.assetid: 9fc4679d-ccb5-4df7-99de-dd7d3a367ecc
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Virtual Services Tab
-
-
-Use the **Virtual Services** tab to view and edit the attributes of embedded services.
-
-## In This Section
-
-
-[About the Virtual Services Tab](about-the-virtual-services-tab.md)
-Provides general information about the **Virtual Services** tab.
-
-[How to Modify Attributes of Embedded Services](how-to-modify-attributes-of-embedded-services.md)
-Provides the procedure to modify the attributes of embedded services by using the **Virtual Services** tab.
-
-## Related topics
-
-
-[Sequencer Console](sequencer-console.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v4/wizard-pages--appv-46-sp1-.md b/mdop/appv-v4/wizard-pages--appv-46-sp1-.md
deleted file mode 100644
index a0a4219295..0000000000
--- a/mdop/appv-v4/wizard-pages--appv-46-sp1-.md
+++ /dev/null
@@ -1,40 +0,0 @@
----
-title: Wizard Pages (AppV 4.6 SP1)
-description: Wizard Pages (AppV 4.6 SP1)
-author: dansimp
-ms.assetid: dadab8cf-fe6d-4cff-8f6c-e9676f244872
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Wizard Pages (AppV 4.6 SP1)
-
-
-Use any of the following links for more information about the App-V wizards.
-
-## In This Section
-
-
-[Create Package Accelerator Wizard (AppV 4.6 SP1)](create-package-accelerator-wizard--appv-46-sp1-.md)
-
-[Create New Package Wizard (AppV 4.6 SP1)](create-new-package-wizard---appv-46-sp1-.md)
-
-[Open Package Wizard (AppV 4.6 SP1)](open-package-wizard---appv-46-sp1-.md)
-
-[Sequencer Wizard - Package Accelerator (AppV 4.6 SP1)](sequencer-wizard---package-accelerator--appv-46-sp1-.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v5/TOC.md b/mdop/appv-v5/TOC.md
deleted file mode 100644
index 6f2058280a..0000000000
--- a/mdop/appv-v5/TOC.md
+++ /dev/null
@@ -1,223 +0,0 @@
-# [Application Virtualization 5](index.md)
-## [Application Virtualization 5.1](microsoft-application-virtualization-51-administrators-guide.md)
-### [Getting Started with App-V 5.1](getting-started-with-app-v-51.md)
-#### [About App-V 5.1](about-app-v-51.md)
-##### [Release Notes for App-V 5.1](release-notes-for-app-v-51.md)
-#### [Evaluating App-V 5.1](evaluating-app-v-51.md)
-#### [High Level Architecture for App-V 5.1](high-level-architecture-for-app-v-51.md)
-#### [Accessibility for App-V 5.1](accessibility-for-app-v-51.md)
-### [Planning for App-V 5.1](planning-for-app-v-51.md)
-#### [Preparing Your Environment for App-V 5.1](preparing-your-environment-for-app-v-51.md)
-##### [App-V 5.1 Prerequisites](app-v-51-prerequisites.md)
-##### [App-V 5.1 Security Considerations](app-v-51-security-considerations.md)
-#### [Planning to Deploy App-V 5.1](planning-to-deploy-app-v51.md)
-##### [App-V 5.1 Supported Configurations](app-v-51-supported-configurations.md)
-##### [App-V 5.1 Capacity Planning](app-v-51-capacity-planning.md)
-##### [Planning for High Availability with App-V 5.1](planning-for-high-availability-with-app-v-51.md)
-##### [Planning to Deploy App-V 5.1 with an Electronic Software Distribution System](planning-to-deploy-app-v-51-with-an-electronic-software-distribution-system.md)
-##### [Planning for the App-V 5.1 Server Deployment](planning-for-the-app-v-51-server-deployment.md)
-##### [Planning for the App-V 5.1 Sequencer and Client Deployment](planning-for-the-app-v-51-sequencer-and-client-deployment.md)
-##### [Planning for Migrating from a Previous Version of App-V](planning-for-migrating-from-a-previous-version-of-app-v51.md)
-##### [Planning for Using App-V with Office 5.1](planning-for-using-app-v-with-office51.md)
-##### [Planning to Use Folder Redirection with App-V 5.1](planning-to-use-folder-redirection-with-app-v51.md)
-#### [App-V 5.1 Planning Checklist](app-v-51-planning-checklist.md)
-### [Deploying App-V 5.1](deploying-app-v-51.md)
-#### [Deploying the App-V 5.1 Sequencer and Client](deploying-the-app-v-51-sequencer-and-client.md)
-##### [How to Deploy the App-V Client](how-to-deploy-the-app-v-client-51gb18030.md)
-##### [About Client Configuration Settings 5.1](about-client-configuration-settings51.md)
-##### [How to Deploy the App-V 4.6 and the App-V 5.1 Client on the Same Computer](how-to-deploy-the-app-v-46-and-the-app-v--51-client-on-the-same-computer.md)
-##### [How to Install the App-V 5.1 Client for Shared Content Store Mode](how-to-install-the-app-v-51-client-for-shared-content-store-mode.md)
-##### [How to Install the Sequencer](how-to-install-the-sequencer-51beta-gb18030.md)
-##### [How to Modify App-V 5.1 Client Configuration Using the ADMX Template and Group Policy](how-to-modify-app-v-51-client-configuration-using-the-admx-template-and-group-policy.md)
-##### [How to Uninstall the App-V 5.1 Client](how-to-uninstall-the-app-v-51-client.md)
-#### [Deploying the App-V 5.1 Server](deploying-the-app-v-51-server.md)
-##### [How to Deploy the App-V 5.1 Server](how-to-deploy-the-app-v-51-server.md)
-##### [How to Deploy the App-V 5.1 Server Using a Script](how-to-deploy-the-app-v-51-server-using-a-script.md)
-##### [How to Deploy the App-V Databases by Using SQL Scripts 5.1](how-to-deploy-the-app-v-databases-by-using-sql-scripts51.md)
-##### [How to Install the Publishing Server on a Remote Computer](how-to-install-the-publishing-server-on-a-remote-computer51.md)
-##### [How to Install the Management and Reporting Databases on Separate Computers from the Management and Reporting Services 5.1](how-to-install-the-management-and-reporting-databases-on-separate-computers-from-the-management-and-reporting-services51.md)
-##### [How to install the Management Server on a Standalone Computer and Connect it to the Database 5.1](how-to-install-the-management-server-on-a-standalone-computer-and-connect-it-to-the-database51.md)
-##### [About App-V 5.1 Reporting](about-app-v-51-reporting.md)
-##### [How to install the Reporting Server on a Standalone Computer and Connect it to the Database 5.1](how-to-install-the-reporting-server-on-a-standalone-computer-and-connect-it-to-the-database51.md)
-#### [App-V 5.1 Deployment Checklist](app-v-51-deployment-checklist.md)
-#### [Deploying Microsoft Office 2016 by Using App-V 5.1](deploying-microsoft-office-2016-by-using-app-v51.md)
-#### [Deploying Microsoft Office 2013 by Using App-V 5.1](deploying-microsoft-office-2013-by-using-app-v51.md)
-#### [Deploying Microsoft Office 2010 by Using App-V 5.1](deploying-microsoft-office-2010-by-using-app-v51.md)
-### [Operations for App-V 5.1](operations-for-app-v-51.md)
-#### [Creating and Managing App-V 5.1 Virtualized Applications](creating-and-managing-app-v-51-virtualized-applications.md)
-##### [How to Sequence a New Application with App-V 5.1](how-to-sequence-a-new-application-with-app-v-51-beta-gb18030.md)
-##### [How to Modify an Existing Virtual Application Package 5.1](how-to-modify-an-existing-virtual-application-package-51.md)
-##### [How to Create and Use a Project Template 5.1](how-to-create-and-use-a-project-template51.md)
-##### [How to Create a Package Accelerator 5.1](how-to-create-a-package-accelerator51.md)
-##### [How to Create a Virtual Application Package Using an App-V Package Accelerator 5.1](how-to-create-a-virtual-application-package-using-an-app-v-package-accelerator51.md)
-#### [Administering App-V 5.1 Virtual Applications by Using the Management Console](administering-app-v-51-virtual-applications-by-using-the-management-console.md)
-##### [About App-V 5.1 Dynamic Configuration](about-app-v-51-dynamic-configuration.md)
-##### [How to Connect to the Management Console 5.1](how-to-connect-to-the-management-console-51.md)
-##### [How to Add or Upgrade Packages by Using the Management Console](how-to-add-or-upgrade-packages-by-using-the-management-console-51-gb18030.md)
-##### [How to Configure Access to Packages by Using the Management Console 5.1](how-to-configure-access-to-packages-by-using-the-management-console-51.md)
-##### [How to Publish a Package by Using the Management Console 5.1](how-to-publish-a-package-by-using-the-management-console-51.md)
-##### [How to Delete a Package in the Management Console 5.1](how-to-delete-a-package-in-the-management-console-51.md)
-##### [How to Add or Remove an Administrator by Using the Management Console 5.1](how-to-add-or-remove-an-administrator-by-using-the-management-console51.md)
-##### [How to Register and Unregister a Publishing Server by Using the Management Console 5.1](how-to-register-and-unregister-a-publishing-server-by-using-the-management-console51.md)
-##### [How to Create a Custom Configuration File by Using the App-V 5.1 Management Console](how-to-create-a-custom-configuration-file-by-using-the-app-v-51-management-console.md)
-##### [How to Transfer Access and Configurations to Another Version of a Package by Using the Management Console 5.1](how-to-transfer-access-and-configurations-to-another-version-of-a-package-by-using-the-management-console51.md)
-##### [How to Customize Virtual Applications Extensions for a Specific AD Group by Using the Management Console 5.1](how-to-customize-virtual-applications-extensions-for-a-specific-ad-group-by-using-the-management-console51.md)
-##### [Configure Applications and Default Virtual Application Extensions in Management Console](configure-applications-and-default-virtual-application-extensions-in-management-console.md)
-#### [Managing Connection Groups 5.1](managing-connection-groups51.md)
-##### [About the Connection Group Virtual Environment 5.1](about-the-connection-group-virtual-environment51.md)
-##### [About the Connection Group File 5.1](about-the-connection-group-file51.md)
-##### [How to Create a Connection Group 5.1](how-to-create-a-connection-group51.md)
-##### [How to Create a Connection Group with User-Published and Globally Published Packages 5.1](how-to-create-a-connection-group-with-user-published-and-globally-published-packages51.md)
-##### [How to Delete a Connection Group 5.1](how-to-delete-a-connection-group51.md)
-##### [How to Publish a Connection Group 5.1](how-to-publish-a-connection-group51.md)
-##### [How to Use Optional Packages in Connection Groups 5.1](how-to-use-optional-packages-in-connection-groups51.md)
-##### [How to Make a Connection Group Ignore the Package Version 5.1](how-to-make-a-connection-group-ignore-the-package-version51.md)
-##### [How to Allow Only Administrators to Enable Connection Groups 5.1](how-to-allow-only-administrators-to-enable-connection-groups51.md)
-#### [Deploying App-V 5.1 Packages by Using Electronic Software Distribution (ESD)](deploying-app-v-51-packages-by-using-electronic-software-distribution--esd-.md)
-##### [How to deploy App-V 5.1 Packages Using Electronic Software Distribution](how-to-deploy-app-v-51-packages-using-electronic-software-distribution.md)
-##### [How to Enable Only Administrators to Publish Packages by Using an ESD 5.1](how-to-enable-only-administrators-to-publish-packages-by-using-an-esd51.md)
-#### [Using the App-V 5.1 Client Management Console](using-the-app-v-51-client-management-console.md)
-##### [How to Access the Client Management Console 5.1](how-to-access-the-client-management-console51.md)
-##### [How to Configure the Client to Receive Package and Connection Groups Updates From the Publishing Server 5.1](how-to-configure-the-client-to-receive-package-and-connection-groups-updates-from-the-publishing-server-51.md)
-#### [Migrating to App-V 5.1 from a Previous Version](migrating-to-app-v-51-from-a-previous-version.md)
-##### [Check Registry Keys before installing App-V 5.x Server](check-reg-key-svr.md)
-##### [How to Convert a Package Created in a Previous Version of App-V 5.1](how-to-convert-a-package-created-in-a-previous-version-of-app-v51.md)
-##### [How to Migrate Extension Points From an App-V 4.6 Package to a Converted App-V 5.1 Package for All Users on a Specific Computer](how-to-migrate-extension-points-from-an-app-v-46-package-to-a-converted-app-v-51-package-for-all-users-on-a-specific-computer.md)
-##### [How to Migrate Extension Points From an App-V 4.6 Package to App-V 5.1 for a Specific User](how-to-migrate-extension-points-from-an-app-v-46-package-to-app-v-51-for-a-specific-user.md)
-##### [How to Revert Extension Points from an App-V 5.1 Package to an App-V 4.6 Package For All Users on a Specific Computer](how-to-revert-extension-points-from-an-app-v-51-package-to-an-app-v-46-package-for-all-users-on-a-specific-computer.md)
-##### [How to Revert Extension Points From an App-V 5.1 Package to an App-V 4.6 Package for a Specific User](how-to-revert-extension-points-from-an-app-v-51-package-to-an-app-v-46-package-for-a-specific-user.md)
-#### [Maintaining App-V 5.1](maintaining-app-v-51.md)
-##### [How to Move the App-V Server to Another Computer 5.1](how-to-move-the-app-v-server-to-another-computer51.md)
-#### [Administering App-V 5.1 by Using PowerShell](administering-app-v-51-by-using-powershell.md)
-##### [How to Load the PowerShell Cmdlets and Get Cmdlet Help 5.1](how-to-load-the-powershell-cmdlets-and-get-cmdlet-help-51.md)
-##### [How to Manage App-V 5.1 Packages Running on a Stand-Alone Computer by Using PowerShell](how-to-manage-app-v-51-packages-running-on-a-stand-alone-computer-by-using-powershell.md)
-##### [How to Manage Connection Groups on a Stand-alone Computer by Using PowerShell 5.1](how-to-manage-connection-groups-on-a-stand-alone-computer-by-using-powershell51.md)
-##### [How to Modify Client Configuration by Using PowerShell 5.1](how-to-modify-client-configuration-by-using-powershell51.md)
-##### [How to Apply the User Configuration File by Using PowerShell 5.1](how-to-apply-the-user-configuration-file-by-using-powershell51.md)
-##### [How to Apply the Deployment Configuration File by Using PowerShell 5.1](how-to-apply-the-deployment-configuration-file-by-using-powershell51.md)
-##### [How to Sequence a Package by Using PowerShell 5.1](how-to-sequence-a-package--by-using-powershell-51.md)
-##### [How to Create a Package Accelerator by Using PowerShell 5.1](how-to-create-a-package-accelerator-by-using-powershell51.md)
-##### [How to Enable Reporting on the App-V 5.1 Client by Using PowerShell](how-to-enable-reporting-on-the-app-v-51-client-by-using-powershell.md)
-##### [How to Install the App-V Databases and Convert the Associated Security Identifiers by Using PowerShell 5.1](how-to-install-the-app-v-databases-and-convert-the-associated-security-identifiers--by-using-powershell51.md)
-### [Troubleshooting App-V 5.1](troubleshooting-app-v-51.md)
-### [Technical Reference for App-V 5.1](technical-reference-for-app-v-51.md)
-#### [Performance Guidance for Application Virtualization 5.1](performance-guidance-for-application-virtualization-51.md)
-#### [Application Publishing and Client Interaction 5.1](application-publishing-and-client-interaction51.md)
-#### [Viewing App-V Server Publishing Metadata 5.1](viewing-app-v-server-publishing-metadata51.md)
-#### [Running a Locally Installed Application Inside a Virtual Environment with Virtualized Applications 5.1](running-a-locally-installed-application-inside-a-virtual-environment-with-virtualized-applications51.md)
-## [Application Virtualization 5.0](microsoft-application-virtualization-50-administrators-guide.md)
-### [Getting Started with App-V 5.0](getting-started-with-app-v-50--rtm.md)
-#### [About App-V 5.0](about-app-v-50.md)
-##### [What's New in App-V 5.0](whats-new-in-app-v-50.md)
-##### [Release Notes for App-V 5.0](release-notes-for-app-v-50.md)
-#### [About App-V 5.0 SP1](about-app-v-50-sp1.md)
-##### [What's new in App-V 5.0 SP1](whats-new-in-app-v-50-sp1.md)
-##### [Release Notes for App-V 5.0 SP1](release-notes-for-app-v-50-sp1.md)
-#### [About App-V 5.0 SP2](about-app-v-50-sp2.md)
-##### [Release Notes for App-V 5.0 SP2](release-notes-for-app-v-50-sp2.md)
-#### [About App-V 5.0 SP3](about-app-v-50-sp3.md)
-##### [Release Notes for App-V 5.0 SP3](release-notes-for-app-v-50-sp3.md)
-#### [Evaluating App-V 5.0](evaluating-app-v-50.md)
-#### [High Level Architecture for App-V 5.0](high-level-architecture-for-app-v-50.md)
-#### [Accessibility for App-V 5.0](accessibility-for-app-v-50.md)
-### [Planning for App-V 5.0](planning-for-app-v-50-rc.md)
-#### [Preparing Your Environment for App-V 5.0](preparing-your-environment-for-app-v-50.md)
-##### [App-V 5.0 Prerequisites](app-v-50-prerequisites.md)
-##### [App-V 5.0 SP3 Prerequisites](app-v-50-sp3-prerequisites.md)
-##### [App-V 5.0 Security Considerations](app-v-50-security-considerations.md)
-#### [Planning to Deploy App-V](planning-to-deploy-app-v.md)
-##### [App-V 5.0 Supported Configurations](app-v-50-supported-configurations.md)
-##### [App-V 5.0 SP3 Supported Configurations](app-v-50-sp3-supported-configurations.md)
-##### [App-V 5.0 Capacity Planning](app-v-50-capacity-planning.md)
-##### [Planning for High Availability with App-V 5.0](planning-for-high-availability-with-app-v-50.md)
-##### [Planning to Deploy App-V 5.0 with an Electronic Software Distribution System](planning-to-deploy-app-v-50-with-an-electronic-software-distribution-system.md)
-##### [Planning for the App-V 5.0 Server Deployment](planning-for-the-app-v-50-server-deployment.md)
-##### [Planning for the App-V 5.0 Sequencer and Client Deployment](planning-for-the-app-v-50-sequencer-and-client-deployment.md)
-##### [Planning for Migrating from a Previous Version of App-V](planning-for-migrating-from-a-previous-version-of-app-v.md)
-##### [Planning for Using App-V with Office](planning-for-using-app-v-with-office.md)
-##### [Planning to Use Folder Redirection with App-V](planning-to-use-folder-redirection-with-app-v.md)
-#### [App-V 5.0 Planning Checklist](app-v-50-planning-checklist.md)
-### [Deploying App-V 5.0](deploying-app-v-50.md)
-#### [Deploying the App-V 5.0 Sequencer and Client](deploying-the-app-v-50-sequencer-and-client.md)
-##### [How to Deploy the App-V Client](how-to-deploy-the-app-v-client-gb18030.md)
-##### [About Client Configuration Settings](about-client-configuration-settings.md)
-##### [How to Deploy the App-V 4.6 and the App-V 5.0 Client on the Same Computer](how-to-deploy-the-app-v-46-and-the-app-v--50-client-on-the-same-computer.md)
-##### [How to Install the App-V 5.0 Client for Shared Content Store Mode](how-to-install-the-app-v-50-client-for-shared-content-store-mode.md)
-##### [How to Install the Sequencer](how-to-install-the-sequencer-beta-gb18030.md)
-##### [How to Modify App-V 5.0 Client Configuration Using the ADMX Template and Group Policy](how-to-modify-app-v-50-client-configuration-using-the-admx-template-and-group-policy.md)
-##### [How to Uninstall the App-V 5.0 Client](how-to-uninstall-the-app-v-50-client.md)
-#### [Deploying the App-V 5.0 Server](deploying-the-app-v-50-server.md)
-##### [How to Deploy the App-V 5.0 Server](how-to-deploy-the-app-v-50-server-50sp3.md)
-##### [How to Deploy the App-V 5.0 Server Using a Script](how-to-deploy-the-app-v-50-server-using-a-script.md)
-##### [How to Deploy the App-V Databases by Using SQL Scripts](how-to-deploy-the-app-v-databases-by-using-sql-scripts.md)
-##### [How to Install the Publishing Server on a Remote Computer](how-to-install-the-publishing-server-on-a-remote-computer.md)
-##### [How to Install the Management and Reporting Databases on Separate Computers from the Management and Reporting Services](how-to-install-the-management-and-reporting-databases-on-separate-computers-from-the-management-and-reporting-services.md)
-##### [How to install the Management Server on a Standalone Computer and Connect it to the Database](how-to-install-the-management-server-on-a-standalone-computer-and-connect-it-to-the-database.md)
-##### [About App-V 5.0 Reporting](about-app-v-50-reporting.md)
-##### [How to install the Reporting Server on a Standalone Computer and Connect it to the Database](how-to-install-the-reporting-server-on-a-standalone-computer-and-connect-it-to-the-database.md)
-#### [App-V 5.0 Deployment Checklist](app-v-50-deployment-checklist.md)
-#### [Deploying Microsoft Office 2016 by Using App-V](deploying-microsoft-office-2016-by-using-app-v.md)
-#### [Deploying Microsoft Office 2013 by Using App-V](deploying-microsoft-office-2013-by-using-app-v.md)
-#### [Deploying Microsoft Office 2010 by Using App-V](deploying-microsoft-office-2010-by-using-app-v.md)
-### [Operations for App-V 5.0](operations-for-app-v-50.md)
-#### [Creating and Managing App-V 5.0 Virtualized Applications](creating-and-managing-app-v-50-virtualized-applications.md)
-##### [How to Sequence a New Application with App-V 5.0](how-to-sequence-a-new-application-with-app-v-50-beta-gb18030.md)
-##### [How to Modify an Existing Virtual Application Package](how-to-modify-an-existing-virtual-application-package-beta.md)
-##### [How to Create and Use a Project Template](how-to-create-and-use-a-project-template.md)
-##### [How to Create a Package Accelerator](how-to-create-a-package-accelerator.md)
-##### [How to Create a Virtual Application Package Using an App-V Package Accelerator](how-to-create-a-virtual-application-package-using-an-app-v-package-accelerator.md)
-#### [Administering App-V 5.0 Virtual Applications by Using the Management Console](administering-app-v-50-virtual-applications-by-using-the-management-console.md)
-##### [About App-V 5.0 Dynamic Configuration](about-app-v-50-dynamic-configuration.md)
-##### [How to Connect to the Management Console](how-to-connect-to-the-management-console-beta.md)
-##### [How to Add or Upgrade Packages by Using the Management Console](how-to-add-or-upgrade-packages-by-using-the-management-console-beta-gb18030.md)
-##### [How to Configure Access to Packages by Using the Management Console](how-to-configure-access-to-packages-by-using-the-management-console-50.md)
-##### [How to Publish a Package by Using the Management Console](how-to-publish-a-package-by-using-the-management-console-50.md)
-##### [How to Delete a Package in the Management Console](how-to-delete-a-package-in-the-management-console-beta.md)
-##### [How to Add or Remove an Administrator by Using the Management Console](how-to-add-or-remove-an-administrator-by-using-the-management-console.md)
-##### [How to Register and Unregister a Publishing Server by Using the Management Console](how-to-register-and-unregister-a-publishing-server-by-using-the-management-console.md)
-##### [How to Create a Custom Configuration File by Using the App-V 5.0 Management Console](how-to-create-a-custom-configuration-file-by-using-the-app-v-50-management-console.md)
-##### [How to Transfer Access and Configurations to Another Version of a Package by Using the Management Console](how-to-transfer-access-and-configurations-to-another-version-of-a-package-by-using-the-management-console.md)
-##### [How to Customize Virtual Applications Extensions for a Specific AD Group by Using the Management Console](how-to-customize-virtual-applications-extensions-for-a-specific-ad-group-by-using-the-management-console.md)
-##### [How to View and Configure Applications and Default Virtual Application Extensions by Using the Management Console](how-to-view-and-configure-applications-and-default-virtual-application-extensions-by-using-the-management-console-beta.md)
-#### [Managing Connection Groups](managing-connection-groups.md)
-##### [About the Connection Group Virtual Environment](about-the-connection-group-virtual-environment.md)
-##### [About the Connection Group File](about-the-connection-group-file.md)
-##### [How to Create a Connection Group](how-to-create-a-connection-group.md)
-##### [How to Create a Connection Group with User-Published and Globally Published Packages](how-to-create-a-connection-group-with-user-published-and-globally-published-packages.md)
-##### [How to Delete a Connection Group](how-to-delete-a-connection-group.md)
-##### [How to Publish a Connection Group](how-to-publish-a-connection-group.md)
-##### [How to Use Optional Packages in Connection Groups](how-to-use-optional-packages-in-connection-groups.md)
-##### [How to Make a Connection Group Ignore the Package Version](how-to-make-a-connection-group-ignore-the-package-version.md)
-##### [How to Allow Only Administrators to Enable Connection Groups](how-to-allow-only-administrators-to-enable-connection-groups.md)
-#### [Deploying App-V 5.0 Packages by Using Electronic Software Distribution (ESD)](deploying-app-v-50-packages-by-using-electronic-software-distribution--esd-.md)
-##### [How to deploy App-V 5.0 Packages Using Electronic Software Distribution](how-to-deploy-app-v-50-packages-using-electronic-software-distribution.md)
-##### [How to Enable Only Administrators to Publish Packages by Using an ESD](how-to-enable-only-administrators-to-publish-packages-by-using-an-esd.md)
-#### [Using the App-V 5.0 Client Management Console](using-the-app-v-50-client-management-console.md)
-##### [How to Access the Client Management Console](how-to-access-the-client-management-console.md)
-##### [How to Configure the Client to Receive Package and Connection Groups Updates From the Publishing Server](how-to-configure-the-client-to-receive-package-and-connection-groups-updates-from-the-publishing-server-beta.md)
-#### [Migrating from a Previous Version](migrating-from-a-previous-version-app-v-50.md)
-##### [How to Convert a Package Created in a Previous Version of App-V](how-to-convert-a-package-created-in-a-previous-version-of-app-v.md)
-##### [How to Migrate Extension Points From an App-V 4.6 Package to a Converted App-V 5.0 Package for All Users on a Specific Computer](how-to-migrate-extension-points-from-an-app-v-46-package-to-a-converted-app-v-50-package-for-all-users-on-a-specific-computer.md)
-##### [How to Migrate Extension Points From an App-V 4.6 Package to App-V 5.0 for a Specific User](how-to-migrate-extension-points-from-an-app-v-46-package-to-app-v-50-for-a-specific-user.md)
-##### [How to Revert Extension Points from an App-V 5.0 Package to an App-V 4.6 Package For All Users on a Specific Computer](how-to-revert-extension-points-from-an-app-v-50-package-to-an-app-v-46-package-for-all-users-on-a-specific-computer.md)
-##### [How to Revert Extension Points From an App-V 5.0 Package to an App-V 4.6 Package for a Specific User](how-to-revert-extension-points-from-an-app-v-50-package-to-an-app-v-46-package-for-a-specific-user.md)
-#### [Maintaining App-V 5.0](maintaining-app-v-50.md)
-##### [How to Move the App-V Server to Another Computer](how-to-move-the-app-v-server-to-another-computer.md)
-#### [Administering App-V by Using PowerShell](administering-app-v-by-using-powershell.md)
-##### [How to Load the PowerShell Cmdlets and Get Cmdlet Help](how-to-load-the-powershell-cmdlets-and-get-cmdlet-help-50-sp3.md)
-##### [How to Manage App-V 5.0 Packages Running on a Stand-Alone Computer by Using PowerShell](how-to-manage-app-v-50-packages-running-on-a-stand-alone-computer-by-using-powershell.md)
-##### [How to Manage Connection Groups on a Stand-alone Computer by Using PowerShell](how-to-manage-connection-groups-on-a-stand-alone-computer-by-using-powershell.md)
-##### [How to Modify Client Configuration by Using PowerShell](how-to-modify-client-configuration-by-using-powershell.md)
-##### [How to Apply the User Configuration File by Using PowerShell](how-to-apply-the-user-configuration-file-by-using-powershell.md)
-##### [How to Apply the Deployment Configuration File by Using PowerShell](how-to-apply-the-deployment-configuration-file-by-using-powershell.md)
-##### [How to Sequence a Package by Using PowerShell](how-to-sequence-a-package--by-using-powershell-50.md)
-##### [How to Create a Package Accelerator by Using PowerShell](how-to-create-a-package-accelerator-by-using-powershell.md)
-##### [How to Enable Reporting on the App-V 5.0 Client by Using PowerShell](how-to-enable-reporting-on-the-app-v-50-client-by-using-powershell.md)
-##### [How to Install the App-V Databases and Convert the Associated Security Identifiers by Using PowerShell](how-to-install-the-app-v-databases-and-convert-the-associated-security-identifiers--by-using-powershell.md)
-### [Troubleshooting App-V 5.0](troubleshooting-app-v-50.md)
-### [Technical Reference for App-V 5.0](technical-reference-for-app-v-50.md)
-#### [Performance Guidance for Application Virtualization 5.0](performance-guidance-for-application-virtualization-50.md)
-#### [Application Publishing and Client Interaction](application-publishing-and-client-interaction.md)
-#### [Viewing App-V Server Publishing Metadata](viewing-app-v-server-publishing-metadata.md)
-#### [Running a Locally Installed Application Inside a Virtual Environment with Virtualized Applications](running-a-locally-installed-application-inside-a-virtual-environment-with-virtualized-applications.md)
-
diff --git a/mdop/appv-v5/about-app-v-50-dynamic-configuration.md b/mdop/appv-v5/about-app-v-50-dynamic-configuration.md
deleted file mode 100644
index 03301519d2..0000000000
--- a/mdop/appv-v5/about-app-v-50-dynamic-configuration.md
+++ /dev/null
@@ -1,889 +0,0 @@
----
-title: About App-V 5.0 Dynamic Configuration
-description: About App-V 5.0 Dynamic Configuration
-author: dansimp
-ms.assetid: 88afaca1-68c5-45c4-a074-9371c56b5804
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# About App-V 5.0 Dynamic Configuration
-
-
-You can use the dynamic configuration to customize an App-V 5.0 package for a user. Use the following information to create or edit an existing dynamic configuration file.
-
-When you edit the dynamic configuration file it customizes how an App-V 5.0 package will run for a user or group. This helps to provide a more convenient method for package customization by removing the need to re-sequence packages using the desired settings, and provides a way to keep package content and custom settings independent.
-
-## Advanced: Dynamic Configuration
-
-
-Virtual application packages contain a manifest that provides all the core information for the package. This information includes the defaults for the package settings and determines settings in the most basic form (with no additional customization). If you want to adjust these defaults for a particular user or group, you can create and edit the following files:
-
-- User Configuration file
-
-- Deployment configuration file
-
-The previous .xml files specify package settings and allow for packages to be customized without directly affecting the packages. When a package is created, the sequencer automatically generates default deployment and user configuration .xml files using the package manifest data. Therefore, these automatically generated configuration files simply reflect the default settings that the package innately as from how things were configured during sequencing. If you apply these configuration files to a package in the form generated by the sequencer, the packages will have the same default settings that came from their manifest. This provides you with a package-specific template to get started if any of the defaults must be changed.
-
-**Note**
-The following information can only be used to modify sequencer generated configuration files to customize packages to meet specific user or group requirements.
-
-
-
-### Dynamic Configuration file contents
-
-All of the additions, deletions, and updates in the configuration files need to be made in relation to the default values specified by the package's manifest information. Review the following table:
-
-
-
-
-
-
-
-
User Configuration .xml file
-
-
-
Deployment Configuration .xml file
-
-
-
Package Manifest
-
-
-
-
-
-
-The previous table represents how the files will be read. The first entry represents what will be read last, therefore, its content takes precedence. Therefore, all packages inherently contain and provide default settings from the package manifest. If a deployment configuration .xml file with customized settings is applied, it will override the package manifest defaults. If a user configuration .xml file with customized settings is applied prior to that, it will override both the deployment configuration and the package manifest defaults.
-
-The following list displays more information about the two file types:
-
-- **User Configuration File (UserConfig)** – Allows you to specify or modify custom settings for a package. These settings will be applied for a specific user when the package is deployed to a computer running the App-V 5.0 client.
-
-- **Deployment Configuration File (DeploymentConfig)** – Allows you to specify or modify the default settings for a package. These settings will be applied for all users when a package is deployed to a computer running the App-V 5.0 client.
-
-To customize the settings for a package for a specific set of users on a computer or to make changes that will be applied to local user locations such as HKCU, the UserConfig file should be used. To modify the default settings of a package for all users on a machine or to make changes that will be applied to global locations such as HKEY\_LOCAL\_MACHINE and the all users folder, the DeploymentConfig file should be used.
-
-The UserConfig file provides configuration settings that can be applied to a single user without affecting any other users on a client:
-
-- Extensions that will be integrated into the native system per user:- shortcuts, File-Type associations, URL Protocols, AppPaths, Software Clients and COM
-
-- Virtual Subsystems:- Application Objects, Environment variables, Registry modifications, Services and Fonts
-
-- Scripts (User context only)
-
-- Managing Authority (for controlling co-existence of package with App-V 4.6)
-
-The DeploymentConfig file provides configuration settings in two sections, one relative to the machine context and one relative to the user context providing the same capabilities listed in the UserConfig list above:
-
-- All UserConfig settings above
-
-- Extensions that can only be applied globally for all users
-
-- Virtual Subsystems that can be configured for global machine locations e.g. registry
-
-- Product Source URL
-
-- Scripts (Machine context only)
-
-- Controls to Terminate Child Processes
-
-### File structure
-
-The structure of the App-V 5.0 Dynamic Configuration file is explained in the following section.
-
-### Dynamic User Configuration file
-
-**Header** - the header of a dynamic user configuration file is as follows:
-
-<?xml version="1.0" encoding="utf-8"?><UserConfiguration **PackageId**="1f8488bf-2257-46b4-b27f-09c9dbaae707" DisplayName="Reserved" xmlns=";
-
-The **PackageId** is the same value as exists in the Manifest file.
-
-**Body** - the body of the Dynamic User Configuration file can include all the app extension points that are defined in the Manifest file, as well as information to configure virtual applications. There are four subsections allowed in the body:
-
-1. **Applications** - All app-extensions that are contained in the Manifest file within a package are assigned with an Application ID, which is also defined in the manifest file. This allows you to enable or disable all the extensions for a given application within a package. The **Application ID** must exist in the Manifest file or it will be ignored.
-
- <UserConfiguration **PackageId**="1f8488bf-2257-46b4-b27f-09c9dbaae707" DisplayName="Reserved" xmlns=";
-
- <Applications>
-
- <!-- No new application can be defined in policy. AppV Client will ignore any application ID that is not also in the Manifest file -->
-
- <Application Id="{a56fa627-c35f-4a01-9e79-7d36aed8225a}" Enabled="false">
-
- </Application>
-
- </Applications>
-
- …
-
- </UserConfiguration>
-
-2. **Subsystems** - AppExtensions and other subsystems are arranged as subnodes under the <Subsystems>:
-
- <UserConfiguration **PackageId**="1f8488bf-2257-46b4-b27f-09c9dbaae707" DisplayName="Reserved" xmlns=";
-
- <Subsystems>
-
- ..
-
- </Subsystems>
-
- ..
-
- </UserConfiguration>
-
- Each subsystem can be enabled/disabled using the “**Enabled**” attribute. Below are the various subsystems and usage samples.
-
- **Extensions:**
-
- Some subsystems (Extension Subsystems) control Extensions. Those subsystems are:- shortcuts, File-Type associations, URL Protocols, AppPaths, Software Clients and COM
-
- Extension Subsystems can be enabled and disabled independently of the content. Thus if Shortcuts are enabled, The client will use the shortcuts contained within the manifest by default. Each Extension Subsystem can contain an <Extensions> node. If this child element is present, the client will ignore the content in the Manifest file for that subsystem and only use the content in the configuration file.
-
- Example using the shortcuts subsystem:
-
- 1. If the user defined this in either the dynamic or deployment config file:
-
- **<Shortcuts Enabled="true">**
-
- **<Extensions>**
-
- ...
-
- **</Extensions>**
-
- **</Shortcuts>**
-
- Content in the manifest will be ignored.
-
- 2. If the user defined only the following:
-
- **<Shortcuts Enabled="true"/>**
-
- Then the content in the Manifest will be integrated during publishing.
-
- 3. If the user defines the following
-
- **<Shortcuts Enabled="true">**
-
- **<Extensions/>**
-
- **</Shortcuts>**
-
- Then all the shortcuts within the manifest will still be ignored. There will be no shortcuts integrated.
-
- The supported Extension Subsystems are:
-
- **Shortcuts:** This controls shortcuts that will be integrated into the local system. Below is a sample with 2 shortcuts:
-
- <Subsystems>
-
- <Shortcuts Enabled="true">
-
- <Extensions>
-
- <Extension Category="AppV.Shortcut">
-
- <Shortcut>
-
- <File>\[{Common Programs}\]\\Microsoft Contoso\\Microsoft ContosoApp Filler 2010.lnk</File>
-
- <Target>\[{PackageRoot}\]\\Contoso\\ContosoApp.EXE</Target>
-
- <Icon>\[{Windows}\]\\Installer\\{90140000-0011-0000-0000-0000000FF1CE}\\inficon.exe</Icon>
-
- <Arguments />
-
- <WorkingDirectory />
-
- <AppUserModelId>ContosoApp.Filler.3</AppUserModelId>
-
- <Description>Fill out dynamic forms to gather and reuse information throughout the organization using Microsoft ContosoApp.</Description>
-
- <Hotkey>0</Hotkey>
-
- <ShowCommand>1</ShowCommand>
-
- <ApplicationId>\[{PackageRoot}\]\\Contoso\\ContosoApp.EXE</ApplicationId>
-
- </Shortcut>
-
- </Extension>
-
- <Extension Category="AppV.Shortcut">
-
- <Shortcut>
-
- <File>\[{AppData}\]\\Microsoft\\Contoso\\Recent\\Templates.LNK</File>
-
- <Target>\[{AppData}\]\\Microsoft\\Templates</Target>
-
- <Icon />
-
- <Arguments />
-
- <WorkingDirectory />
-
- <AppUserModelId />
-
- <Description />
-
- <Hotkey>0</Hotkey>
-
- <ShowCommand>1</ShowCommand>
-
- <!-- Note the ApplicationId is optional -->
-
- </Shortcut>
-
- </Extension>
-
- </Extensions>
-
- </Shortcuts>
-
- **File-Type Associations:** Associates File-types with programs to open by default as well as setup the context menu. (MIME types can also be setup using this susbsystem). Sample File-type Association is below:
-
- <FileTypeAssociations Enabled="true">
-
- <Extensions>
-
- <Extension Category="AppV.FileTypeAssociation">
-
- <FileTypeAssociation>
-
- <FileExtension MimeAssociation="true">
-
- <Name>.docm</Name>
-
- <ProgId>contosowordpad.DocumentMacroEnabled.12</ProgId>
-
- <PerceivedType>document</PerceivedType>
-
- <ContentType>application/vnd.ms-contosowordpad.document.macroEnabled.12</ContentType>
-
- <OpenWithList>
-
- <ApplicationName>wincontosowordpad.exe</ApplicationName>
-
- </OpenWithList>
-
- <OpenWithProgIds>
-
- <ProgId>contosowordpad.8</ProgId>
-
- </OpenWithProgIds>
-
- <ShellNew>
-
- <Command />
-
- <DataBinary />
-
- <DataText />
-
- <FileName />
-
- <NullFile>true</NullFile>
-
- <ItemName />
-
- <IconPath />
-
- <MenuText />
-
- <Handler />
-
- </ShellNew>
-
- </FileExtension>
-
- <ProgId>
-
- <Name>contosowordpad.DocumentMacroEnabled.12</Name>
-
- <DefaultIcon>\[{Windows}\]\\Installer\\{90140000-0011-0000-0000-0000000FF1CE}\\contosowordpadicon.exe,15</DefaultIcon>
-
- <Description>Blah Blah Blah</Description>
-
- <FriendlyTypeName>\[{FOLDERID\_ProgramFilesX86}\]\\Microsoft Contoso 14\\res.dll,9182</FriendlyTypeName>
-
- <InfoTip>\[{FOLDERID\_ProgramFilesX86}\]\\Microsoft Contoso 14\\res.dll,1424</InfoTip>
-
- <EditFlags>0</EditFlags>
-
- <ShellCommands>
-
- <DefaultCommand>Open</DefaultCommand>
-
- <ShellCommand>
-
- <ApplicationId>{e56fa627-c35f-4a01-9e79-7d36aed8225a}</ApplicationId>
-
- <Name>Edit</Name>
-
- <FriendlyName>&Edit</FriendlyName>
-
- <CommandLine>"\[{PackageRoot}\]\\Contoso\\WINcontosowordpad.EXE" /vu "%1"</CommandLine>
-
- </ShellCommand>
-
- </ShellCommand>
-
- <ApplicationId>{e56fa627-c35f-4a01-9e79-7d36aed8225a}</ApplicationId>
-
- <Name>Open</Name>
-
- <FriendlyName>&Open</FriendlyName>
-
- <CommandLine>"\[{PackageRoot}\]\\Contoso\\WINcontosowordpad.EXE" /n "%1"</CommandLine>
-
- <DropTargetClassId />
-
- <DdeExec>
-
- <Application>mscontosowordpad</Application>
-
- <Topic>ShellSystem</Topic>
-
- <IfExec>\[SHELLNOOP\]</IfExec>
-
- <DdeCommand>\[SetForeground\]\[ShellNewDatabase "%1"\]</DdeCommand>
-
- </DdeExec>
-
- </ShellCommand>
-
- </ShellCommands>
-
- </ProgId>
-
- </FileTypeAssociation>
-
- </Extension>
-
- </Extensions>
-
- </FileTypeAssociations>
-
- **URL Protocols**: This controls the URL Protocols that are integrated into the local registry of the client machine e.g. “mailto:”.
-
- <URLProtocols Enabled="true">
-
- <Extensions>
-
- <Extension Category="AppV.URLProtocol">
-
- <URLProtocol>
-
- <Name>mailto</Name>
-
- <ApplicationURLProtocol>
-
- <DefaultIcon>\[{ProgramFilesX86}\]\\Microsoft Contoso\\Contoso\\contosomail.EXE,-9403</DefaultIcon>
-
- <EditFlags>2</EditFlags>
-
- <Description />
-
- <AppUserModelId />
-
- <FriendlyTypeName />
-
- <InfoTip />
-
- <SourceFilter />
-
- <ShellFolder />
-
- <WebNavigableCLSID />
-
- <ExplorerFlags>2</ExplorerFlags>
-
- <CLSID />
-
- <ShellCommands>
-
- <DefaultCommand>open</DefaultCommand>
-
- <ShellCommand>
-
- <ApplicationId>\[{ProgramFilesX86}\]\\Microsoft Contoso\\Contoso\\contosomail.EXE</ApplicationId>
-
- <Name>open</Name>
-
- <CommandLine>\[{ProgramFilesX86}\\Microsoft Contoso\\Contoso\\contosomail.EXE" -c OEP.Note /m "%1"</CommandLine>
-
- <DropTargetClassId />
-
- <FriendlyName />
-
- <Extended>0</Extended>
-
- <LegacyDisable>0</LegacyDisable>
-
- <SuppressionPolicy>2</SuppressionPolicy>
-
- <DdeExec>
-
- <NoActivateHandler />
-
- <Application>contosomail</Application>
-
- <Topic>ShellSystem</Topic>
-
- <IfExec>\[SHELLNOOP\]</IfExec>
-
- <DdeCommand>\[SetForeground\]\[ShellNewDatabase "%1"\]</DdeCommand>
-
- </DdeExec>
-
- </ShellCommand>
-
- </ShellCommands>
-
- </ApplicationURLProtocol>
-
- </URLProtocol>
-
- </Extension>
-
- </Extension>
-
- </URLProtocols>
-
- **Software Clients**: Allows the app to register as an Email client, news reader, media player and makes the app visible in the Set Program Access and Computer Defaults UI. In most cases you should only need to enable and disable it. There is also a control to enable and disable the email client specifically if you want the other clients still enabled except for that client.
-
- <SoftwareClients Enabled="true">
-
- <ClientConfiguration EmailEnabled="false" />
-
- </SoftwareClients>
-
- AppPaths:- If an application for example contoso.exe is registered with an apppath name of “myapp”, it allows you type “myapp” under the run menu and it will open contoso.exe.
-
- <AppPaths Enabled="true">
-
- <Extensions>
-
- <Extension Category="AppV.AppPath">
-
- <AppPath>
-
- <ApplicationId>\[{ProgramFilesX86}\]\\Microsoft Contoso\\Contoso\\contosomail.EXE</ApplicationId>
-
- <Name>contosomail.exe</Name>
-
- <ApplicationPath>\[{ProgramFilesX86}\]\\Microsoft Contoso\\Contoso\\contosomail.EXE</ApplicationPath>
-
- <PATHEnvironmentVariablePrefix />
-
- <CanAcceptUrl>false</CanAcceptUrl>
-
- <SaveUrl />
-
- </AppPath>
-
- </Extension>
-
- </Extensions>
-
- </AppPaths>
-
- **COM**: Allows an Application register Local COM servers. Mode can be Integration, Isolated or Off. When Isol.
-
- <COM Mode="Isolated"/>
-
- **Other Settings**:
-
- In addition to Extensions, other subsystems can be enabled/disabled and edited:
-
- **Virtual Kernel Objects**:
-
- <Objects Enabled="false" />
-
- **Virtual Registry**: Used if you want to set a registry in the Virtual Registry within HKCU
-
- <Registry Enabled="true">
-
- <Include>
-
- <Key Path="\\REGISTRY\\USER\\\[{AppVCurrentUserSID}\]\\Software\\ABC">
-
- <Value Type="REG\_SZ" Name="Bar" Data="NewValue" />
-
- </Key>
-
- <Key Path="\\REGISTRY\\USER\\\[{AppVCurrentUserSID}\]\\Software\\EmptyKey" />
-
- </Include>
-
- <Delete>
-
- </Registry>
-
- **Virtual File System**
-
- <FileSystem Enabled="true" />
-
- **Virtual Fonts**
-
- <Fonts Enabled="false" />
-
- **Virtual Environment Variables**
-
- <EnvironmentVariables Enabled="true">
-
- <Include>
-
- <Variable Name="UserPath" Value="%path%;%UserProfile%" />
-
- <Variable Name="UserLib" Value="%UserProfile%\\ABC" />
-
- </Include>
-
- <Delete>
-
- <Variable Name="lib" />
-
- </Delete>
-
- </EnvironmentVariables>
-
- **Virtual services**
-
- <Services Enabled="false" />
-
-3. **UserScripts** – Scripts can be used to setup or alter the virtual environment as well as execute scripts at time of deployment or removal, before an application executes, or they can be used to “clean up” the environment after the application terminates. Please reference a sample User configuration file that is output by the sequencer to see a sample script. The Scripts section below provides more information on the various triggers that can be used.
-
-4. **ManagingAuthority** – Can be used when 2 versions of your package are co-existing on the same machine, one deployed to App-V 4.6 and the other deployed on App-V 5.0. To Allow App-V vNext to take over App-V 4.6 extension points for the named package enter the following in the UserConfig file (where PackageName is the Package GUID in App-V 4.6:
-
- <ManagingAuthority TakeoverExtensionPointsFrom46="true" PackageName="032630c0-b8e2-417c-acef-76fc5297fe81" />
-
-### Dynamic Deployment Configuration file
-
-**Header** - The header of a Deployment Configuration file is as follows:
-
-<?xml version="1.0" encoding="utf-8"?><DeploymentConfiguration **PackageId**="1f8488bf-2257-46b4-b27f-09c9dbaae707" DisplayName="Reserved" xmlns=";
-
-The **PackageId** is the same value as exists in the manifest file.
-
-**Body** - The body of the deployment configuration file includes two sections:
-
-- User Configuration section –allows the same content as the User Configuration file described in the previous section. When the package is published to a user, any appextensions configuration settings in this section will override corresponding settings in the Manifest within the package unless a user configuration file is also provided. If a UserConfig file is also provided, it will be used instead of the User settings in the deployment configuration file. If the package is published globally, then only the contents of the deployment configuration file will be used in combination with the manifest.
-
-- Machine Configuration section–contains information that can be configured only for an entire machine, not for a specific user on the machine. For example, HKEY\_LOCAL\_MACHINE registry keys in the VFS.
-
-<DeploymentConfiguration **PackageId**="1f8488bf-2257-46b4-b27f-09c9dbaae707" DisplayName="Reserved" xmlns=";
-
-<UserConfiguration>
-
- ..
-
-</UserConfiguration>
-
-<MachineConfiguration>
-
-..
-
-</MachineConfiguration>
-
-..
-
-</MachineConfiguration>
-
-</DeploymentConfiguration>
-
-**User Configuration** - use the previous **Dynamic User Configuration file** section for information on settings that are provided in the user configuration section of the Deployment Configuration file.
-
-Machine Configuration - the Machine configuration section of the Deployment Configuration File is used to configure information that can be set only for an entire machine, not for a specific user on the computer. For example, HKEY\_LOCAL\_MACHINE registry keys in the Virtual Registry. There are four subsections allowed in under this element
-
-1. **Subsystems** - AppExtensions and other subsystems are arranged as subnodes under <Subsystems>:
-
- <MachineConfiguration>
-
- <Subsystems>
-
- ..
-
- </Subsystems>
-
- ..
-
- </MachineConfiguration>
-
- The following section displays the various subsystems and usage samples.
-
- **Extensions**:
-
- Some subsystems (Extension Subsystems) control Extensions which can only apply to all users. The subsystem is application capabilities. Because this can only apply to all users, the package must be published globally in order for this type of extension to be integrated into the local system. The same rules for controls and settings that apply to the Extensions in the User Configuration also apply to those in the MachineConfiguration section.
-
- **Application Capabilities**: Used by default programs in windows operating system Interface. Allows an application to register itself as capable of opening certain file extensions, as a contender for the start menu internet browser slot, as capable of opening certain windows MIME types. This extension also makes the virtual application visible in the Set Default Programs UI.:
-
- <ApplicationCapabilities Enabled="true">
-
- <Extensions>
-
- <Extension Category="AppV.ApplicationCapabilities">
-
- <ApplicationCapabilities>
-
- <ApplicationId>\[{PackageRoot}\]\\LitView\\LitViewBrowser.exe</ApplicationId>
-
- <Reference>
-
- <Name>LitView Browser</Name>
-
- <Path>SOFTWARE\\LitView\\Browser\\Capabilities</Path>
-
- </Reference>
-
- <CapabilityGroup>
-
- <Capabilities>
-
- <Name>@\[{ProgramFilesX86}\]\\LitView\\LitViewBrowser.exe,-12345</Name>
-
- <Description>@\[{ProgramFilesX86}\]\\LitView\\LitViewBrowser.exe,-12346</Description>
-
- <Hidden>0</Hidden>
-
- <EMailSoftwareClient>Lit View E-Mail Client</EMailSoftwareClient>
-
- <FileAssociationList>
-
- <FileAssociation Extension=".htm" ProgID="LitViewHTML" />
-
- <FileAssociation Extension=".html" ProgID="LitViewHTML" />
-
- <FileAssociation Extension=".shtml" ProgID="LitViewHTML" />
-
- </FileAssociationList>
-
- <MIMEAssociationList>
-
- <MIMEAssociation Type="audio/mp3" ProgID="LitViewHTML" />
-
- <MIMEAssociation Type="audio/mpeg" ProgID="LitViewHTML" />
-
- </MIMEAssociationList>
-
- <URLAssociationList>
-
- <URLAssociation Scheme="http" ProgID="LitViewHTML.URL.http" />
-
- </URLAssociationList>
-
- </Capabilities>
-
- </CapabilityGroup>
-
- </ApplicationCapabilities>
-
- </Extension>
-
- </Extensions>
-
- </ApplicationCapabilities>
-
- **Other Settings**:
-
- In addition to Extensions, other subsystems can be edited:
-
- **Machine Wide Virtual Registry**: Used when you want to set a registry key in the virtual registry within HKEY\_Local\_Machine
-
- <Registry>
-
- <Include>
-
- <Key Path="\\REGISTRY\\Machine\\Software\\ABC">
-
- <Value Type="REG\_SZ" Name="Bar" Data="Baz" />
-
- </Key>
-
- <Key Path="\\REGISTRY\\Machine\\Software\\EmptyKey" />
-
- </Include>
-
- <Delete>
-
- </Registry>
-
- **Machine Wide Virtual Kernel Objects**
-
- <Objects>
-
- <NotIsolate>
-
- <Object Name="testObject" />
-
- </NotIsolate>
-
- </Objects>
-
-2. **ProductSourceURLOptOut**: Indicates whether the URL for the package can be modified globally through PackageSourceRoot (to support branch office scenarios). Default is false and the setting change takes effect on the next launch.
-
- <MachineConfiguration>
-
- ..
-
- <ProductSourceURLOptOut Enabled="true" />
-
- ..
-
- </MachineConfiguration>
-
-3. **MachineScripts** – Package can be configured to execute scripts at time of deployment, publishing or removal. Please reference a sample deployment configuration file that is generated by the sequencer to see a sample script. The Scripts section below provides more information on the various triggers that can be used
-
-4. **TerminateChildProcess**:- An application executable can be specified, whose child processes will be terminated when the application exe process is terminated.
-
- <MachineConfiguration>
-
- ..
-
- <TerminateChildProcesses>
-
- <Application Path="\[{PackageRoot}\]\\Contoso\\ContosoApp.EXE" />
-
- <Application Path="\[{PackageRoot}\]\\LitView\\LitViewBrowser.exe" />
-
- <Application Path="\[{ProgramFilesX86}\]\\Microsoft Contoso\\Contoso\\contosomail.EXE" />
-
- </TerminateChildProcesses>
-
- ..
-
- </MachineConfiguration>
-
-### Scripts
-
-The following table describes the various script events and the context under which they can be run.
-
-
-
-
-
-
-
-
-
-
-
-
-
Script Execution Time
-
Can be specified in Deployment Configuration
-
Can be specified in User Configuration
-
Can run in the Virtual Environment of the package
-
Can be run in the context of a specific application
-
Runs in system/user context: (Deployment Configuration, User Configuration)
-
-
-
-
-
AddPackage
-
X
-
-
-
-
(SYSTEM, N/A)
-
-
-
PublishPackage
-
X
-
X
-
-
-
(SYSTEM, User)
-
-
-
UnpublishPackage
-
X
-
X
-
-
-
(SYSTEM, User)
-
-
-
RemovePackage
-
X
-
-
-
-
(SYSTEM, N/A)
-
-
-
StartProcess
-
X
-
X
-
X
-
X
-
(User, User)
-
-
-
ExitProcess
-
X
-
X
-
-
X
-
(User, User)
-
-
-
StartVirtualEnvironment
-
X
-
X
-
X
-
-
(User, User)
-
-
-
TerminateVirtualEnvironment
-
X
-
X
-
-
-
(User, User)
-
-
-
-
-
-
-### Create a Dynamic Configuration file using an App-V 5.0 Manifest file
-
-You can create the Dynamic Configuration file using one of three methods: either manually, using the App-V 5.0 Management Console or sequencing a package, which will be generated with 2 sample files.
-
-For more information about how to create the file using the App-V 5.0 Management Console see, [How to Create a Custom Configuration File by Using the App-V 5.0 Management Console](how-to-create-a-custom-configuration-file-by-using-the-app-v-50-management-console.md).
-
-To create the file manually, the information above in previous sections can be combined into a single file. We recommend you use files generated by the sequencer.
-
-
-
-
-
-
-## Related topics
-
-
-[How to Apply the Deployment Configuration File by Using PowerShell](how-to-apply-the-deployment-configuration-file-by-using-powershell.md)
-
-[How to Apply the User Configuration File by Using PowerShell](how-to-apply-the-user-configuration-file-by-using-powershell.md)
-
-[Operations for App-V 5.0](operations-for-app-v-50.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v5/about-app-v-50-reporting.md b/mdop/appv-v5/about-app-v-50-reporting.md
deleted file mode 100644
index f5bce3e29a..0000000000
--- a/mdop/appv-v5/about-app-v-50-reporting.md
+++ /dev/null
@@ -1,327 +0,0 @@
----
-title: About App-V 5.0 Reporting
-description: About App-V 5.0 Reporting
-author: dansimp
-ms.assetid: 27c33dda-f017-41e3-8a78-1b681543ec4f
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 08/30/2016
----
-
-
-# About App-V 5.0 Reporting
-
-
-Microsoft Application Virtualization (App-V) 5.0 includes a built-in reporting feature that helps you collect information about computers running the App-V 5.0 client as well as information about virtual application package usage. You can use this information to generate reports from a centralized database.
-
-## App-V 5.0 Reporting Overview
-
-
-The following list displays the end–to-end high-level workflow for reporting in App-V 5.0.
-
-1. The Microsoft Application Virtualization (App-V) 5.0 Reporting server has the following prerequisites:
-
- - Internet Information Service (IIS) web server role
-
- - Windows Authentication role (under **IIS / Security**)
-
- - SQL Server installed and running with SQL Server Reporting Services (SSRS)
-
- To confirm SQL Server Reporting Services is running, view `http://localhost/Reports` in a web browser as administrator on the server that will host App-V 5.0 Reporting. The SQL Server Reporting Services Home page should display.
-
-2. Install the App-V 5.0 reporting server and associated database. For more information about installing the reporting server see [How to install the Reporting Server on a Standalone Computer and Connect it to the Database](how-to-install-the-reporting-server-on-a-standalone-computer-and-connect-it-to-the-database.md). Configure the time when the computer running the App-V 5.0 client should send data to the reporting server.
-
-3. If you are not using an electronic software distribution system such as Configuration Manager to view reports then you can define reports in SQL Server Reporting Service. Download predefined appvshort Reports from the Download Center at .
-
- **Note**
- If you are using the Configuration Manager integration with App-V 5.0, most reports are generated from Configuration Manager rather than from App-V 5.0.
-
-
-
-4. After importing the App-V 5.0 PowerShell module using `Import-Module AppvClient` as administrator, enable the App-V 5.0 client. This sample PowerShell cmdlet enables App-V 5.0 reporting:
-
- ``` syntax
- Set-AppvClientConfiguration –reportingserverurl : -reportingenabled 1 – ReportingStartTime <0-23> - ReportingRandomDelay <#min>
- ```
-
- To immediately send App-V 5.0 report data, run `Send-AppvClientReport` on the App-V 5.0 client.
-
- For more information about installing the App-V 5.0 client with reporting enabled see [About Client Configuration Settings](about-client-configuration-settings.md). To administer App-V 5.0 Reporting with Windows PowerShell, see [How to Enable Reporting on the App-V 5.0 Client by Using PowerShell](how-to-enable-reporting-on-the-app-v-50-client-by-using-powershell.md).
-
-5. After the reporting server receives the data from the App-V 5.0 client it sends the data to the reporting database. When the database receives and processes the client data, a successful reply is sent to the reporting server and then a notification is sent to the App-V 5.0 client.
-
-6. When the App-V 5.0 client receives the success notification, it empties the data cache to conserve space.
-
- **Note**
- By default the cache is cleared after the server confirms receipt of data. You can manually configure the client to save the data cache.
-
-
-
-~~~
-If the App-V 5.0 client device does not receive a success notification from the server, it retains data in the cache and tries to resend data at the next configured interval. Clients continue to collect data and add it to the cache.
-~~~
-
-### App-V 5.0 reporting server frequently asked questions
-
-The following table displays answers to common questions about App-V 5.0 reporting
-
-
-
-
-
-
-
-
-
Question
-
More Information
-
-
-
-
-
What is the frequency that reporting information is sent to the reporting database?
-
The frequency depends on how the reporting task is configured on the computer running the App-V 5.0 client. You must configure the frequency / interval for sending the reporting data. App-V 5.0 Reporting is not enabled by default.
-
-
-
What information is stored in the reporting server database?
-
The following list displays what is stored in the reporting database:
-
-
The operating system running on the computer running the App-V 5.0 client: host name, version, service pack, type - client/server, processor architecture.
-
App-V 5.0 Client information: version.
-
Published package list: GUID, version GUID, name.
-
Application usage information: name, version, streaming server, user (domain\alias), package version GUID, launch status and time, shutdown time.
-
-
-
-
What is the average volume of information that is sent to the reporting server?
-
It depends. The following list displays the three sets of the data sent to the reporting server:
-
-
Operating system, and App-V 5.0 client information. ~150 Bytes, every time this data is sent.
-
Published package list. ~7 KB for 30 packages. This is sent only when the package list is updated with a publishing refresh, which is done infrequently; if there is no change, this information is not sent.
-
Virtual application usage information – about 0.25KB per event. Opening and closing count as one event if both occur before sending the information. When sending using a scheduled task, only the data since the last successful upload is sent to the server. If sending manually through the PowerShell cmdlet, there is an optional argument that controls if the data needs to be re-sent next time around – that argument is DeleteOnSuccess.
-
-
So for example, if twenty applications are opened and closed and reporting information is scheduled to be sent daily, the typical daily traffic should be about 0.15KB + 20 x 0.25KB, or about 5KB/user
-
-
-
-
Can reporting be scheduled?
-
Yes. Besides manually sending reporting using PowerShell Cmdlets (Send-AppvClientReport), the task can be scheduled so it will happen automatically. There are two ways to schedule the reporting:
-
-
Using PowerShell cmdlets - Set-AppvClientConfiguration. For example:
For a complete list of client configuration settings see About Client Configuration Settings and look for the following entries: ReportingEnabled, ReportingServerURL, ReportingDataCacheLimit, ReportingDataBlockSize, ReportingStartTime, ReportingRandomDelay, ReportingInterval.
-
-
By using Group Policy. If distributed using the domain controller, the settings are the same as previously listed.
-
-Note
Group Policy settings override local settings configured using PowerShell.
-
-
-
-
-
-
-
-
-
-
-
-## App-V 5.0 Client Reporting
-
-
-To use App-V 5.0 reporting you must install and configure the App-V 5.0 client. After the client has been installed, use the **Set-AppVClientConfiguration** PowerShell cmdlet or the **ADMX Template** to configure reporting. The reporting feature cmdlets are available by using the following link and are prefaced by **Reporting**. For a complete list of client configuration settings see [About Client Configuration Settings](about-client-configuration-settings.md). The following section provides examples of App-V 5.0 client reporting configuration using PowerShell.
-
-### Configuring App-V Client reporting using PowerShell
-
-The following examples show how PowerShell parameters can configure the reporting features of the App-V 5.0 client.
-
-**Note**
-The following configuration task can also be configured using Group Policy settings in the App-V 5.0 ADMX template. For more information about using the ADMX template, see [How to Modify App-V 5.0 Client Configuration Using the ADMX Template and Group Policy](how-to-modify-app-v-50-client-configuration-using-the-admx-template-and-group-policy.md).
-
-
-
-**To enable reporting and to initiate data collection on the computer running the App-V 5.0 client**:
-
-`Set-AppVClientConfiguration –ReportingEnabled 1`
-
-**To configure the client to automatically send data to a specific reporting server**:
-
-``` syntax
-Set-AppVClientConfiguration –ReportingServerURL http://MyReportingServer:MyPort/ -ReportingStartTime 20 -ReportingInterval 1 -ReportingRandomDelay 30
-```
-
-`-ReportingInterval 1 -ReportingRandomDelay 30`
-
-This example configures the client to automatically send the reporting data to the reporting server URL http://MyReportingServer:MyPort/. Additionally, the reporting data will be sent daily between 8:00 and 8:30 PM, depending on the random delay generated for the session.
-
-**To limit the size of the data cache on the client**:
-
-`Set-AppvClientConfiguration –ReportingDataCacheLimit 100`
-
-Configures the maximum size of the reporting cache on the computer running the App-V 5.0 client to 100 MB. If the cache limit is reached before the data is sent to the server, then the log rolls over and data will be overwritten as necessary.
-
-**To configure the data block size transmitted across the network between the client and the server**:
-
-`Set-AppvClientConfiguration –ReportingDataBlockSize 10240`
-
-Specifies the maximum data block that the client sends to 10240 MB.
-
-### Types of data collected
-
-The following table displays the types of information you can collect by using App-V 5.0 reporting.
-
-
-
-
-
-
-
-
-
-
Client Information
-
Package Information
-
Application Usage
-
-
-
-
-
Host Name
-
Package Name
-
Start and End Times
-
-
-
App-V 5.0 Client Version
-
Package Version
-
Run Status
-
-
-
Processor Architecture
-
Package Source
-
Shutdown State
-
-
-
Operating System Version
-
Percent Cached
-
Application Name
-
-
-
Service Pack Level
-
-
Application Version
-
-
-
Operating System Type
-
-
Username
-
-
-
-
-
Connection Group
-
-
-
-
-
-
-The client collects and saves this data in an **.xml** format. The data cache is hidden by default and requires administrator rights to open the XML file.
-
-### Sending data to the server
-
-You can configure the computer that is running the App-V 5.0 client to automatically send data to the specified reporting server. To specify the server use the **Set-AppvClientConfiguration** cmdlet with the following settings:
-
-- ReportingEnabled
-
-- ReportingServerURL
-
-- ReportingStartTime
-
-- ReportingInterval
-
-- ReportingRandomDelay
-
-After you configure the previous settings, you must create a scheduled task. The scheduled task will contact the server specified by the **ReportingServerURL** setting and will initiate the transfer. If you want to manually send data outside of the scheduled times, use the following PowerShell cmdlet:
-
-`Send-AppVClientReport –URL http://MyReportingServer:MyPort/ -DeleteOnSuccess`
-
-If the reporting server has been previously configured, then the **–URL** parameter can be omitted. Alternatively, if the data should be sent to an alternate location, specify a different URL to override the configured **ReportingServerURL** for this data collection.
-
-The **-DeleteOnSuccess** parameter indicates that if the transfer is successful, then the data cache is cleared. If this is not specified, then the cache will not be cleared.
-
-### Manual Data Collection
-
-You can also use the **Send-AppVClientReport** cmdlet to manually collect data. This solution is helpful with or without an existing reporting server. The following list displays information about collecting data with or without a reporting server.
-
-
-
-
-
-
-
-
-
With a Reporting Server
-
Without a Reporting Server
-
-
-
-
-
If you have an existing App-V 5.0 reporting Server, create a customized scheduled task or script. Specify that the client send the data to the specified location with the desired frequency.
-
If you do not have an existing App-V 5.0 reporting Server, use the –URL parameter to send the data to a specified share. For example:
The previous example will send the reporting data to \MyShare\MyData</strong> location indicated by the -URL parameter. After the data has been sent, the cache is cleared.
-
-Note
If a location other than the Reporting Server is specified, the data is sent using .xml format with no additional processing.
-
-
-
-
-
-
-
-
-
-
-### Creating Reports
-
-To retrieve report information and create reports using App-V 5.0 you must use one of the following methods:
-
-- **Microsoft SQL Server Reporting Services (SSRS)** - Microsoft SQL Server Reporting Services is available with Microsoft SQL Server. SSRS is not installed when you install the App-V 5.0 reporting server. It must be deployed separately to generate the associated reports.
-
- Use the following link for more information about using [Microsoft SQL Server Reporting Services](https://go.microsoft.com/fwlink/?LinkId=285596).
-
-- **Scripting** – You can generate reports by scripting directly against the App-V 5.0 reporting database. For example:
-
- **Stored Procedure:**
-
- **spProcessClientReport** is scheduled to run at midnight or 12:00 AM.
-
- To run the Microsoft SQL Server Scheduled Stored procedure, the Microsoft SQL Server Agent must be running. You should ensure that the Microsoft SQL Server Agent is set to **AutoStart**. For more information see [Autostart SQL Server Agent (SQL Server Management Studio)](https://go.microsoft.com/fwlink/?LinkId=287045).
-
- The stored procedure is also created when using the App-V 5.0 database scripts.
-
-You should also ensure that the reporting server web service’s **Maximum Concurrent Connections** is set to a value that the server will be able to manage without impacting availability. The recommended number of **Maximum Concurrent Connections** for the **Reporting Web Service** is **10,000**.
-
-
-
-
-
-
-## Related topics
-
-
-[Deploying the App-V 5.0 Server](deploying-the-app-v-50-server.md)
-
-[How to install the Reporting Server on a Standalone Computer and Connect it to the Database](how-to-install-the-reporting-server-on-a-standalone-computer-and-connect-it-to-the-database.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v5/about-app-v-50-sp1.md b/mdop/appv-v5/about-app-v-50-sp1.md
deleted file mode 100644
index 2222333447..0000000000
--- a/mdop/appv-v5/about-app-v-50-sp1.md
+++ /dev/null
@@ -1,61 +0,0 @@
----
-title: About App-V 5.0 SP1
-description: About App-V 5.0 SP1
-author: dansimp
-ms.assetid: 2848a51b-452e-4c70-b465-f6717cfa667f
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 08/30/2016
----
-
-
-# About App-V 5.0 SP1
-
-
-This service pack contains the following changes:
-
-- The App-V 5.0 sequencer and App-V 5.0 client now support twenty-four languages. You can download the additional language packs using the **Volume Licensing Service Center**.
-
-- The App-V 5.0 server now supports eleven languages. You can download the additional language packs using the **Volume Licensing Service Center**.
-
-- Support has been added for the App-V 5.0 Volume Shadow Copy Service (VSS) Writer feature.
-
- **Important**
- To use VSS and App-V 5.0 you must modify the values for the following server registry keys with the updated database names:
-
- - Management - **HKEY\_LOCAL\_MACHINE** \\ **SOFTWARE** \\ **Microsoft** \\ **AppV** \\ **Server** \\ **ManagementService** \\ **MANAGEMENT\_DB\_NAME**
-
- - Reporting - **HKEY\_LOCAL\_MACHINE** \\ **SOFTWARE** \\ **Microsoft** \\ **AppV** \\ **Server** \\ **ReportingService** \\ **REPORTING\_DB\_NAME**
-
-
-
-## How to Get MDOP Technologies
-
-
-App-V 5.0 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](https://go.microsoft.com/fwlink/?LinkId=322049) (https://go.microsoft.com/fwlink/?LinkId=322049).
-
-
-
-
-
-
-## Related topics
-
-
-[What's new in App-V 5.0 SP1](whats-new-in-app-v-50-sp1.md)
-
-[Release Notes for App-V 5.0 SP1](release-notes-for-app-v-50-sp1.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v5/about-app-v-50-sp2.md b/mdop/appv-v5/about-app-v-50-sp2.md
deleted file mode 100644
index f3f167d10a..0000000000
--- a/mdop/appv-v5/about-app-v-50-sp2.md
+++ /dev/null
@@ -1,183 +0,0 @@
----
-title: About App-V 5.0 SP2
-description: About App-V 5.0 SP2
-author: dansimp
-ms.assetid: 16ca8452-cef2-464e-b4b5-c10d4630fa6a
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 08/30/2016
----
-
-
-# About App-V 5.0 SP2
-
-
-App-V 5.0 SP2 provides an improved integrated platform, more flexible virtualization, and powerful management for virtualized applications. For more information see, [App-V 5.0 Overview](https://go.microsoft.com/fwlink/p/?LinkId=325265) (https://go.microsoft.com/fwlink/?LinkId=325265).
-
-## Changes in Standard App-V 5.0 SP2 Functionality
-
-
-The following sections contain information about the changes in standard functionality for App-V 5.0 SP2.
-
-### Support for Windows Server 2012 R2 and Windows 8.1
-
-App-V 5.0 includes support for Windows Server 2012 R2 and Windows 8.1
-
-### App-V 5.0 SP2 now supports folder redirection for the user’s roaming AppData directory
-
-App-V 5.0 SP2 supports roaming AppData (%AppData%) folder redirection. For more information, see the [Planning to Use Folder Redirection with App-V](planning-to-use-folder-redirection-with-app-v.md).
-
-### Package upgrade improvements and pending tasks
-
-In App-V 5.0 SP2, you are no longer prompted to close a running virtual application when a newer version of the package or connection group is published. If a package or connection group is in use when you try to perform a related task, a message displays to indicate that the object is in use, and that the operation will be attempted at a later time.
-
-Tasks that have been placed in a pending state will be performed according to the following rules:
-
-
-
-
-
-
-
-
-
Task type
-
Applicable rule
-
-
-
-
-
User-based task, e.g., publishing a package to a user
-
The pending task will be performed after the user logs off and then logs back on.
-
-
-
Globally based task, e.g., enabling a connection group globally
-
The pending task will be performed when the computer is shut down and then restarted.
-
-
-
-
-
-
-When a task is placed in a pending state, the App-V client also generates a registry key for the pending task, as follows:
-
-
-
-
-
-### Virtualizing Microsoft Office 2013 and Microsoft Office 2010 using App-V 5.0
-
-Use the following link for more information about App-V 5.0 supported Microsoft Office scenarios.
-
-[Virtualizing Microsoft Office 2013 for Application Virtualization (App-V) 5.0](../solutions/virtualizing-microsoft-office-2013-for-application-virtualization--app-v--50-solutions.md)
-
-**Note**
-This document focuses on creating a Microsoft Office 2013 App-V 5.0 Package. However, it also provides information about scenarios for Microsoft Office 2010 with App-V 5.0.
-
-
-
-### App-V 5.0 Client Management User Interface Application
-
-In previous versions of App-V 5.0 the Client Management User Interface (UI) was provided with the App-V 5.0 Client installation. With App-V 5.0 SP2 this is no longer the case. Administrators now have the option to deploy the App-V 5.0 Client UI as a Virtual Application (using all supported App-V deployment configurations) or as an installed application.
-
-For more information see [Microsoft Application Virtualization 5.0 Client UI Application](https://go.microsoft.com/fwlink/p/?LinkId=386345) (https://go.microsoft.com/fwlink/?LinkId=386345).
-
-### Side-by-Side (SxS) Assembly Automatic Packaging and Deployment
-
-App-V 5.0 SP2 now automatically detects side-by-side (SxS) assemblies, and deployment on the computer running the App-V 5.0 SP2 client. A SxS assembly primarily consists of VC++ run-time dependencies or MSXML. In previous versions of App-V, virtual applications that had dependencies on VC run-times required these dependencies to be locally on the computer running the App-V 5.0 SP2 client.
-
-The following functionality is now supported:
-
-- The App-V 5.0 sequencer automatically captures the SxS assembly in the package regardless of whether the VC run-time has already been installed on the computer running the sequencer.
-
-- The App-V 5.0 client automatically installs the required SxS assembly to the computer running the client as required at publishing time.
-
-- The App-V 5.0 sequencer reports the VC run-time dependency using the sequencer reporting mechanism.
-
-- The App-V 5.0 sequencer now allows you to exclude the VC run-time dependency in the event that the dependency is already available on the computer running the sequencer.
-
-### Publishing Refresh Improvements
-
-App-V 5.0 supports several features were added to improve the overall experience of refreshing a set of applications for a specific user.
-
-The following list displays the publishing refresh enhancements:
-
-The following list contains more information about how to enable the new publishing refresh improvements.
-
-- **EnablePublishingRefreshUI** - Enables the publishing refresh progress bar for the computer running the App-V 5.0 Client.
-
-- **HideUI** - Hides the publishing refresh progress bar during a manual sync.
-
-### New Client Configuration Setting
-
-The following new client configuration setting is available with App-V 5.0 SP2:
-
-**EnableDynamicVirtualization** - Enables supported Shell Extensions, Browser Helper Objects, and Active X controls to be virtualized and run with virtual applications.
-
-For more information, see [About Client Configuration Settings](about-client-configuration-settings.md).
-
-### App-V 5.0 Shell extensions
-
-App-V 5.0 SP2 now supports shell extensions.
-
-For more information see the **App-V 5.0 SP2 shell extension support** section of [Creating and Managing App-V 5.0 Virtualized Applications](creating-and-managing-app-v-50-virtualized-applications.md).
-
-## App-V 5.0 documentation updates
-
-
-App-V 5.0 SP2 provides updated documentation for the following scenarios:
-
-- [Migrating from a Previous Version](migrating-from-a-previous-version-app-v-50.md)
-
-- [About App-V 5.0](about-app-v-50.md)
-
-- [About App-V 5.0 Reporting](about-app-v-50-reporting.md) (frequently asked questions section)
-
-## How to Get MDOP Technologies
-
-
-App-V 5.0 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](https://go.microsoft.com/fwlink/?LinkId=322049) (https://go.microsoft.com/fwlink/?LinkId=322049).
-
-
-
-
-
-
-## Related topics
-
-
-[Release Notes for App-V 5.0 SP2](release-notes-for-app-v-50-sp2.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v5/about-app-v-50-sp3.md b/mdop/appv-v5/about-app-v-50-sp3.md
deleted file mode 100644
index a784b0b574..0000000000
--- a/mdop/appv-v5/about-app-v-50-sp3.md
+++ /dev/null
@@ -1,839 +0,0 @@
----
-title: About App-V 5.0 SP3
-description: About App-V 5.0 SP3
-author: dansimp
-ms.assetid: 67b5268b-edc1-4027-98b0-b3937dd70a6b
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 11/02/2016
----
-
-
-# About App-V 5.0 SP3
-
-
-Use the following sections to review information about significant changes that apply to Microsoft Application Virtualization (App-V) 5.0 SP3:
-
-- [App-V 5.0 SP3 software prerequisites and supported configurations](#bkmk-sp3-prereq-configs)
-
-- [Migrating to App-V 5.0 SP3](#bkmk-migrate-to-50sp3)
-
-- [Manually created connection group xml file requires update to schema](#bkmk-update-schema-cg)
-
-- [Improvements to connection groups](#bkmk-cg-improvements)
-
-- [Administrators can publish and unpublish packages for a specific user](#bkmk-usersid-pub-pkgs-specf-user)
-
-- [Enable only administrators to publish and unpublish packages](#bkmk-admins-only-pub-unpub-pkgs)
-
-- [RunVirtual registry key supports packages that are published to the user](#bkmk-runvirtual-reg-key)
-
-- [New PowerShell cmdlets and updateable cmdlet help](#bkmk-posh-cmdlets-help)
-
-- [Primary virtual application directory (PVAD) is hidden but can be turned on](#bkmk-pvad-hidden)
-
-- [ClientVersion is required to view App-V publishing metadata](#bkmk-pub-metadata-clientversion)
-
-- [App-V event logs have been consolidated](#bkmk-event-logs-moved)
-
-## App-V 5.0 SP3 software prerequisites and supported configurations
-
-
-See the following links for the App-V 5.0 SP3 software prerequisites and supported configurations.
-
-
-
-
-
-
-
-
-
Links to prerequisites and supported configurations
Supported operating systems and hardware requirements for the App-V Server, Sequencer, and Client components
-
-
-
-
-
-
-## Migrating to App-V 5.0 SP3
-
-
-Use the following information to upgrade to App-V 5.0 SP3 from earlier versions.
-
-### Before you start the upgrade
-
-Review the following information before you start the upgrade:
-
-
-
-
-
-
-
-
-
Items to review before upgrading
-
Description
-
-
-
-
-
Components to upgrade
-
-
App-V Server
-
Sequencer
-
App-V client or App-V Remote Desktop Services (RDS) client
You can upgrade to App-V 5.0 SP3 directly from any of the following versions:
-
-
App-V 5.0
-
App-V 5.0 SP1
-
App-V 5.0 SP2
-
-
To upgrade to App-V 5.0 SP3, follow the steps in the remaining sections of this article.
-
-
-
Required changes to packages and connection groups after upgrade
-
None. Packages and connection groups will continue to work as they currently do.
-
-
-
-
-
-
-### Steps to upgrade the App-V infrastructure
-
-Complete the following steps to upgrade each component of the App-V infrastructure to App-V 5.0 SP3.
-
-
-
-
-
-
-
-
-
Step
-
For more information
-
-
-
-
-
Step 1: Upgrade the App-V Server.
-
If you are not using the App-V Server, skip this step and go to the next step.
-
-Note
The App-V 5.0 SP3 client is compatible with the App-V 5.0 SP1 Server.
-
-
-
-### Check registry keys before installing the App-V 5.0 SP3 Server
-
-This is step 3 from the previous table.
-
-
-
-
-
-
-
-
-
When this step is required
-
You are upgrading from App-V SP1 with any subsequent Hotfix Packages that you installed by using an .msp file.
-
-
-
Which components require that you do this step
-
Only the App-V Server components that you are upgrading.
-
-
-
When you need to do this step
-
Before you upgrade the App-V Server to App-V 5.0 SP3
-
-
-
What you need to do
-
Using the information in the following tables, update each registry key value under HKLM\Software\Microsoft\AppV\Server with the value that you provided in your original server installation. Completing this step restores registry values that may have been removed when App-V SP1 Hotfix Packages were installed.
-
-
-
-
-
-
-**ManagementDatabase key**
-
-If you are installing the Management database, set these registry keys under `HKLM\Software\Microsoft\AppV\Server\ManagementDatabase`.
-
-
-
-
-
-
-
-
-
Key name
-
Description
-
-
-
-
-
IS_MANAGEMENT_DB_PUBLIC_ACCESS_ACCOUNT_REQUIRED
-
Describes whether a public access account is required to access non-local management databases. Value is set to “1” if it is required.
-
-
-
MANAGEMENT_DB_NAME
-
Name of the Management database.
-
-
-
MANAGEMENT_DB_PUBLIC_ACCESS_ACCOUNT
-
Account used for read (public) access to the Management database.
-
Used when IS_MANAGEMENT_DB_PUBLIC_ACCESS_ACCOUNT_REQUIRED is set to 1.
-
-
-
MANAGEMENT_DB_PUBLIC_ACCESS_ACCOUNT_SID
-
Secure identifier (SID) of the account used for read (public) access to the Management database.
-
Used when IS_MANAGEMENT_DB_PUBLIC_ACCESS_ACCOUNT_REQUIRED is set to 1.
-
-
-
MANAGEMENT_DB_SQL_INSTANCE
-
SQL Server instance for the Management database.
-
If the value is blank, the default database instance is used.
-
-
-
MANAGEMENT_DB_WRITE_ACCESS_ACCOUNT
-
Account used for write (administrator) access to the Management database.
-
-
-
MANAGEMENT_DB_WRITE_ACCESS_ACCOUNT_SID
-
Secure identifier (SID) of the account used for write (administrator) access to the Management database.
-
-
-
MANAGEMENT_REMOTE_SERVER_MACHINE_ACCOUNT
-
Management server remote computer account (domain\account).
-
-
-
MANAGEMENT_SERVER_INSTALL_ADMIN_ACCOUNT
-
Installation administrator login for the Management server (domain\account).
-
-
-
MANAGEMENT_SERVER_MACHINE_USE_LOCAL
-
Valid values are:
-
-
1 – the Management service is on the local computer, that is, MANAGEMENT_REMOTE_SERVER_MACHINE_ACCOUNT is blank.
-
0 - the Management service is on a different computer from the local computer.
-
-
-
-
-
-
-
-**ManagementService key**
-
-If you are installing the Management server, set these registry keys under `HKLM\Software\Microsoft\AppV\Server\ManagementService`.
-
-
-
-
-
-
-
-
-
Key name
-
Description
-
-
-
-
-
MANAGEMENT_ADMINACCOUNT
-
Active Directory Domain Services (AD DS) group or account that is authorized to manage App-V (domain\account).
-
-
-
MANAGEMENT_DB_SQL_INSTANCE
-
SQL server instance that contains the Management database.
-
If the value is blank, the default database instance is used.
-
-
-
MANAGEMENT_DB_SQL_SERVER_NAME
-
Name of the remote SQL server with the Management database.
-
If the value is blank, the local computer is used.
-
-
-
-
-
-
-**ReportingDatabase key**
-
-If you are installing the Reporting database, set these registry keys under `HKLM\Software\Microsoft\AppV\Server\ReportingDatabase`.
-
-
-
-
-
-
-
-
-
Key name
-
Description
-
-
-
-
-
IS_REPORTING_DB_PUBLIC_ACCESS_ACCOUNT_REQUIRED
-
Describes whether a public access account is required to access non-local reporting databases. Value is set to “1” if it is required.
-
-
-
REPORTING_DB_NAME
-
Name of the Reporting database.
-
-
-
REPORTING_DB_PUBLIC_ACCESS_ACCOUNT
-
Account used for read (public) access to the Reporting database.
-
Used when IS_REPORTING_DB_PUBLIC_ACCESS_ACCOUNT_REQUIRED is set to 1.
-
-
-
REPORTING_DB_PUBLIC_ACCESS_ACCOUNT_SID
-
Secure identifier (SID) of the account used for read (public) access to the Reporting database.
-
Used when IS_REPORTING_DB_PUBLIC_ACCESS_ACCOUNT_REQUIRED is set to 1.
-
-
-
REPORTING_DB_SQL_INSTANCE
-
SQL Server instance for the Reporting database.
-
If the value is blank, the default database instance is used.
-
-
-
REPORTING_DB_WRITE_ACCESS_ACCOUNT
-
-
-
-
REPORTING_DB_WRITE_ACCESS_ACCOUNT_SID
-
-
-
-
REPORTING_REMOTE_SERVER_MACHINE_ACCOUNT
-
Reporting server remote computer account (domain\account).
-
-
-
REPORTING_SERVER_INSTALL_ADMIN_ACCOUNT
-
Installation administrator login for the Reporting server (domain\account).
-
-
-
REPORTING_SERVER_MACHINE_USE_LOCAL
-
Valid values are:
-
-
1 – the Reporting service is on the local computer, that is, REPORTING_REMOTE_SERVER_MACHINE_ACCOUNT is blank.
-
0 - the Reporting service is on a different computer from the local computer.
-
-
-
-
-
-
-
-**ReportingService key**
-
-If you are installing the Reporting server, set these registry keys under `HKLM\Software\Microsoft\AppV\Server\ReportingService`.
-
-
-
-
-
-
-
-
-
Key name
-
Description
-
-
-
-
-
REPORTING_DB_SQL_INSTANCE
-
SQL Server instance for the Reporting database.
-
If the value is blank, the default database instance is used.
-
-
-
REPORTING_DB_SQL_SERVER_NAME
-
Name of the remote SQL server with the Reporting database.
-
If the value is blank, the local computer is used.
-
-
-
-
-
-
-## Manually created connection group xml file requires update to schema
-
-
-If you are manually creating the connection group XML file, and want to use the new “optional packages” and “use any version” features that are described in [Improvements to connection groups](#bkmk-cg-improvements), you must specify the following schema in the XML file:
-
-`xmlns="http://schemas.microsoft.com/appv/2014/virtualapplicationconnectiongroup"`
-
-For examples and more information, see [About the Connection Group File](about-the-connection-group-file.md).
-
-## Improvements to connection groups
-
-
-You can manage connection groups more easily by using optional packages and other improvements that have been added in App-V 5.0 SP3. The following table summarizes the tasks that you can perform by using the new connection group features, and links to more detailed information about each task.
-
-
-
-
-
-
-
-
-
-
Task/feature
-
Description
-
Links to more information
-
-
-
-
-
Enable a connection group to include optional packages
-
Including optional packages in a connection group enables you to dynamically determine which applications will be included in the connection group’s virtual environment, based on the applications that users are entitled to.
-
You don’t need to manage as many connection groups because you can mix optional and non-optional packages in the same connection group. Mixing packages allows different groups of users to use the same connection group, even though users might have only one package in common.
-
Example: You can enable a package with Microsoft Office for all users, but enable different optional packages, which contain different Office plug-ins, to different subsets of users.
Unpublish or delete an optional package without changing the connection group
-
Unpublish or delete, or unpublish and republish an optional package, which is in a connection group, without having to disable or re-enable the connection group on the App-V client.
Make a connection group ignore the package version
-
Configure a connection group to accept any version of a package, which enables you to upgrade a package without having to disable the connection group. In addition, if there is an optional package with an incorrect version in the connection group, the package is ignored and won’t block the connection group’s virtual environment from being created.
Merging identical package paths into one virtual directory in connection groups
-
If two or more packages in a connection group contain identical directory paths, the paths are merged into a single virtual directory inside the connection group virtual environment.
-
This merging of paths allows an application in one package to access files that are in a different package.
-
-
-
-## Administrators can publish and unpublish packages for a specific user
-
-
-Administrators can use the following cmdlets to publish or unpublish packages for a specific user. To use the cmdlets, enter the **–UserSID** parameter, followed by the user’s security identifier (SID). For more information, see:
-
-- [How to Manage App-V 5.0 Packages Running on a Stand-Alone Computer by Using PowerShell](how-to-manage-app-v-50-packages-running-on-a-stand-alone-computer-by-using-powershell.md#bkmk-pub-pkg-a-user-standalone-posh)
-
-- [How to Manage App-V 5.0 Packages Running on a Stand-Alone Computer by Using PowerShell](how-to-manage-app-v-50-packages-running-on-a-stand-alone-computer-by-using-powershell.md#bkmk-unpub-pkg-specfc-use)
-
-
-
-
-
-## Enable only administrators to publish and unpublish packages
-
-
-You can enable only administrators (not end users) to publish and unpublish packages by using one of the following methods:
-
-
-
-
-
-
-
-
-
Method
-
More information
-
-
-
-
-
Group Policy setting
-
Navigate to the following Group Policy Object node:
-
-
-
-## RunVirtual registry key supports packages that are published to the user
-
-
-App-V 5.0 SP3 adds support for using the **RunVirtual** registry key with virtualized applications that are in user-published packages. The **RunVirtual** registry key lets you run a locally installed application in a virtual environment, along with applications that have been virtualized by using App-V.
-
-Previously, the virtualized applications in App-V packages had to be published globally. For more about **RunVirtual** and about other methods of running locally installed applications in a virtual environment with virtualized applications, see [Running a Locally Installed Application Inside a Virtual Environment with Virtualized Applications](running-a-locally-installed-application-inside-a-virtual-environment-with-virtualized-applications.md).
-
-## New PowerShell cmdlets and updateable cmdlet help
-
-
-New PowerShell cmdlets and updateable cmdlet help are included in App-V 5.0 SP3. To download the cmdlet modules, see [How to Load the PowerShell Cmdlets and Get Cmdlet Help](how-to-load-the-powershell-cmdlets-and-get-cmdlet-help-50-sp3.md#bkmk-load-cmdlets).
-
-### New App-V 5.0 SP3 Server PowerShell cmdlets
-
-New Windows PowerShell cmdlets for the App-V Server have been added to help you manage connection groups.
-
-
-
-
-
-
-
-
-
Cmdlet
-
Description
-
-
-
-
-
Add-AppvServerConnectionGroupPackage
-
Appends a package to the end of a connection group's package list and enables you to configure the package as optional and/or with no version within the connection group.
-
-
-
Set-AppvServerConnectionGroupPackage
-
Enables you to edit details about the connection group package, such as whether it is optional.
-
-
-
Remove-AppvServerConnectionGroupPackage
-
Removes a package from a connection group.
-
-
-
-
-
-
-### Getting help for the PowerShell cmdlets
-
-Cmdlet help is available in the following formats:
-
-
-
-
-
-
-
-
-
Format
-
Description
-
-
-
-
-
As a downloadable module
-
To get the latest help after downloading the cmdlet module:
-
-
Open Windows PowerShell or Windows PowerShell Integrated Scripting Environment (ISE).
-
Type one of the following commands to load the cmdlets for the module you want:
-
-
-
-For more information, see [How to Load the PowerShell Cmdlets and Get Cmdlet Help](how-to-load-the-powershell-cmdlets-and-get-cmdlet-help-50-sp3.md).
-
-## Primary virtual application directory (PVAD) is hidden but can be turned on
-
-
-The primary virtual application directory (PVAD) is hidden in App-V 5.0 SP3, but you can turn it back on and make it visible by using one of the following methods:
-
-
-
-
-
-
-
-
-
Method
-
Steps
-
-
-
-
-
Use a command line parameter
-
Pass the –EnablePVADControl parameter to the Sequencer.exe.
-
-
-
Create a registry subkey
-
-
In the Registry Editor, navigate to: HKLM\SOFTWARE\Microsoft\AppV\Sequencer\Compatibility
-
-Note
If the Compatibility subkey doesn’t exist, you must create it.
-
-
-
-
-
Create a DWORD Value named EnablePVADControl, and set the value to 1.
-
A value of 0 means that PVAD is hidden.
-
-
-
-
-
-
-
-**More about PVAD:** When you use the Sequencer to create a package, you can enter any installation path for the package. In past versions of App-V, you were required to specify the primary virtual application directory (PVAD) of the application as the path. PVAD is the directory to which you would typically install an application on your local computer if you weren’t using App-V. For example, if you were installing Office on a computer, the PVAD typically would be C:\\Program Files\\Microsoft Office\\.
-
-## ClientVersion is required to view App-V publishing metadata
-
-
-In App-V 5.0 SP3, you must provide the following values in the address when you query the App-V Publishing server for metadata:
-
-
-
-
-
-
-
-
-
Value
-
Additional details
-
-
-
-
-
ClientVersion
-
If you omit the ClientVersion parameter from the query, the metadata excludes the new App-V 5.0 SP3 features.
-
-
-
ClientOS
-
You have to provide this value only if you select specific client operating systems when you sequence the package. If you select the default (all operating systems), do not specify this value in the query.
-
If you omit the ClientOS parameter from the query, only the packages that were sequenced to support any operating system appear in the metadata.
-
-
-
-
-
-
-For syntax and examples of this query, see [Viewing App-V Server Publishing Metadata](viewing-app-v-server-publishing-metadata.md).
-
-## App-V event logs have been consolidated
-
-
-The following event logs, previously located at **Applications and Services Logs/Microsoft/AppV/<App-V component>**, have been moved to **Applications and Services Logs/Microsoft/AppV/ServiceLog**.
-
-To view the logs, select **View** > **Show Analytic and Debug Logs** in the Event Viewer application.
-
-Client-Catalog Client-Integration Client-Orchestration Client-PackageConfig Client-Scripting Client-Service Client-Vemgr Client-VFSC FilesystemMetadataLibrary ManifestLibrary PolicyLibrary Subsystems-ActiveX Subsystems-AppPath Subsystems-Com Subsystems-fta
-
-## 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](https://go.microsoft.com/fwlink/?LinkId=322049).
-
-
-
-
-
-
-## Related topics
-
-
-[Release Notes for App-V 5.0 SP3](release-notes-for-app-v-50-sp3.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v5/about-app-v-50.md b/mdop/appv-v5/about-app-v-50.md
deleted file mode 100644
index a81421348c..0000000000
--- a/mdop/appv-v5/about-app-v-50.md
+++ /dev/null
@@ -1,113 +0,0 @@
----
-title: About App-V 5.0
-description: About App-V 5.0
-author: dansimp
-ms.assetid: 5799141b-44bc-4033-afcc-212235e15f00
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 08/30/2016
----
-
-
-# About App-V 5.0
-
-
-App-V 5.0 provides an improved integrated platform, more flexible virtualization, and powerful management for virtualized applications. For more information see the [App-V 5.0 Overview](https://go.microsoft.com/fwlink/?LinkId=325265) (https://go.microsoft.com/fwlink/?LinkId=325265).
-
-## What’s new?
-
-
-The following list displays what is new with App-V 5.0:
-
-- **IT Diagnostics and Monitoring** - App-V 5.0 enhances the ability to generate reporting information about computers running the App-V 5.0 client and virtualized packages.
-
-- **End-to-End Programmability** - Leveraging PowerShell 3.0, App-V 5.0 offers a complete programmability solution for packaging, client and server operations.
-
-- **Simple and Effective Client Console** - App-V 5.0 offers a modern client console designed to simplify the top end user and Tier 1 support engineer scenarios.
-
-- **Virtual Application Extensions** - App-V 5.0 virtual application extensions enable virtual packages to run as if they are installed locally.
-
-- **Local Drive Creation** - App-V 5.0 no longer requires a dedicated local drive letter for virtual application deployment.
-
-- **Shared Content Store** – The App-V 5.0 shared content store offers similar functionality to the streaming server available in previous versions of App-V. It also requires less disk space and updates to virtual applications are available as soon as the new version is ready.
-
-- **Connection Groups** - App-V 5.0 connection groups allow you to connect and run virtual applications interactively.
-
-## Differences between App-V 4.6 and App-V 5.0
-
-
-The following table displays some of the differences between App-V 4.6 and App-V 5.0:
-
-
-
-
-
-
-
-
-
App-V 4.6
-
App-V 5.0
-
-
-
-
-
Must Use a dedicated drive letter (Q:</strong>).
-
No dedicated drive letter required.
-
-
-
4 GB package size limit requirement.
-
No 4 GB package size limit requirement.
-
-
-
Virtual applications are isolated from locally installed applications.
-
Virtual applications can be extended to support local application interaction.
-
-
-
Dynamic Suite Composition enabled interaction with middleware applications.
-
Peer applications are shared using connection groups. For more information about connection groups see, Managing Connection Groups.
-
-
-
VDI/RDS environments required a read-only shared cache.
-
You can update the shared content store using the standard workflow.
-
-
-
Limited command-line scripting.
-
Supports robust PowerShell scripting for the sequencer, client, and server components.
-
-
-
-
Provides web-based management capabilities.
-
-
-
-
-
-
-## How to Get MDOP Technologies
-
-
-App-V 5.0 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](https://go.microsoft.com/fwlink/?LinkId=322049) (https://go.microsoft.com/fwlink/?LinkId=322049).
-
-
-
-
-
-
-## Related topics
-
-
-[Getting Started with App-V 5.0](getting-started-with-app-v-50--rtm.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v5/about-app-v-51-dynamic-configuration.md b/mdop/appv-v5/about-app-v-51-dynamic-configuration.md
deleted file mode 100644
index 663c596d68..0000000000
--- a/mdop/appv-v5/about-app-v-51-dynamic-configuration.md
+++ /dev/null
@@ -1,953 +0,0 @@
----
-title: About App-V 5.1 dynamic configuration
-description: You can use the dynamic configuration to customize an App-V 5.1 package for a user. Use the following information to create or edit an existing dynamic configuration file.
-author: dansimp
-ms.assetid: 35bc9908-d502-4a9c-873f-8ee17b6d9d74
-ms.reviewer:
-manager: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 08/28/2018
-ms.author: dansimp
----
-
-# About App-V 5.1 dynamic configuration
-With dynamic configuration, you can edit the dynamic configuration file to customize how an App-V 5.1 package runs for a user or group. Package customization removes the need to resequence packages using the desired settings. It also provides a way to keep package content and custom settings independent.
-
-Virtual application packages contain a manifest that provides all the core information for the package. This information includes the defaults for the package settings and determines settings in the most basic form (with no additional customization).
-
-When a package gets created, the sequencer generates default deployment and user configuration .xml files automatically using the package manifest data. Therefore, these generated files reflect the default settings configured during sequencing. If you apply these files to a package in the form generated by the sequencer, the packages have the same default settings that came from their manifest.
-
-Use these generated files to make changes, if necessary, which doesn’t directly affect the package. If you want to add, delete or update the configuration files, make your changes about the default values in the manifest information.
-
->[!TIP]
->The order in which the files read are:
UserConfig.xml
DeploymentConfig.xml
Manifest
The first entry represents what gets read last. Therefore, its content takes precedence, and all packages inherently contain and provide default settings from the package manifest.
If customizing the DeploymentConfig.xml file and apply the customized settings, the default settings in the package manifest get overridden.
If customizing the UserConfig.xml and apply the customized settings, the default settings for both the deployment configuration and the package manifest get overridden.
-
-## User configuration file contents (UserConfig.xml)
-The UserConfig file provides configuration settings that get applied for a specific user when deploying the package to a computer running the App-V 5.1 client. These settings don’t affect any other users on the client.
-
-Use the UserConfig file to specify or modify custom settings for a package:
-
-- Extensions integrated into the native system per user: shortcuts, file-type associations, URL protocols, AppPaths, software clients and COM
-- Virtual subsystems: application objects, environment variables, registry modifications, services and fonts
-- Scripts (user context only)
-- Managing authority (for controlling co-existence of package with App-V 4.6)
-
-### Header
-
-The header of a dynamic user configuration file looks like:
-
-```xml
-
-```
-
-The **PackageId** is the same value as exists in the manifest file.
-
-
-### Body
-
-The body of the dynamic user configuration file can include all the app extension points defined in the manifest file, as well as information to configure virtual applications. There are four subsections allowed in the body:
-
-1. **[Applications](#applications)**
-2. **[Subsystems](#subsystems)**
-3. **[UserScripts](#userscripts)**
-4. **[ManagingAuthority](#managingauthority)**
-
-#### Applications
-
-All app-extensions contained in the manifest file within a package have an Application ID assigned, which you find in the manifest file. The Application ID lets you enable or disable all extensions for a given application within a package. The Application ID must exist in the manifest file, or it gets ignored.
-
-```XML
-
-
-
-
-
-
-
-
-
-
-
-
-..
-
-
-```
-
-#### Subsystems
-
-AppExtensions and other subsystems arranged as subnodes.
-
-```XML
-
-
-
-
-..
-
-
-
-..
-
-
-```
-
-You can enable or disable each subsystem using the **Enabled** attribute.
-
-**Extensions**
-
-Some subsystems (extension subsystems) control extensions. Those subsystems are Shortcuts, File-Type associations, URL Protocols, AppPaths, Software Clients, and COM.
-
-Extension subsystems can be enabled and disabled independently of the content. For example, if you enable Shortcuts, the client uses the Shortcuts contained within the manifest by default. Each extension subsystem can contain an \ node. If this child element is present, the client ignores the content in the manifest file for that subsystem and only use the content in the configuration file.
-
-_**Examples:**_
-
-- If you define this in either the user or deployment config file, the content in the manifest gets ignored.
-
- ```XML
-
-
-
-
-
- ...
-
-
-
-
- ```
-- If you define only the following, the content in the manifest gets integrated during publishing.
-
- ```XML
-
-
- ```
-
-- If you define the following, all Shortcuts within the manifest still get ignored. In other words, no Shortcuts get integrated.
-
- ```XML
-
-
-
-
-
-
- ```
-
-_**Supported extension subsystems:**_
-
-**Shortcuts** extension subsystem controls what shortcuts get integrated into the local system.
-
-```XML
-
-
-
-
-
-
-
-
-
-
-
- [{Common Programs}]\Microsoft Contoso\Microsoft ContosoApp Filler 2010.lnk
-
- [{PackageRoot}]\Contoso\ContosoApp.EXE
-
-
- [{Windows}]\Installer\{90140000-0011-0000-0000-0000000FF1CE}\inficon.exe
-
-
-
-
-
- ContosoApp.Filler.3
-
- Fill out dynamic forms to gather and reuse information throughout the organization using Microsoft ContosoApp.
-
- 0
-
- 1
-
- [{PackageRoot}]\Contoso\ContosoApp.EXE
-
-
-
-
-
-
-
-
-
- [{AppData}]\Microsoft\Contoso\Recent\Templates.LNK
-
- [{AppData}]\Microsoft\Templates
-
-
-
-
-
-
-
-
-
-
-
- 0
-
- 1
-
-
-
-
-
-
-
-
-
-
-```
-
-**File-Type Associates** extension subsystem associates file types with programs to open by default as well as set up the context menu.
-
->[!TIP]
->You can set up the subsystem with MIME types.
-
-```XML
-
-
-
-
-
-
-
-
-
-
-
- .docm
-
- contosowordpad.DocumentMacroEnabled.12
-
- document
-
- application/vnd.ms-contosowordpad.document.macroEnabled.12
-
-
-
- wincontosowordpad.exe
-
-
-
-
-
- contosowordpad.8
-
-
-
-
-
-
-
-
-
-
-
-
-
- true
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- contosowordpad.DocumentMacroEnabled.12
-
- [{Windows}]\Installer\{90140000-0011-0000-0000-000000FF1CE}\contosowordpadicon.exe,15
-
- Blah Blah Blah
-
- [{FOLDERID_ProgramFilesX86}]\Microsoft Contoso 14\res.dll,9182
-
- [{FOLDERID_ProgramFilesX86}]\Microsoft Contoso 14\res.dll,1424
-
- 0
-
-
-
- Open
-
-
-
- {e56fa627-c35f-4a01-9e79-7d36aed8225a}
-
- Edit
-
- &Edit
-
- "[{PackageRoot}]\Contoso\WINcontosowordpad.EXE" /vu "%1"
-
-
-
-
-
- {e56fa627-c35f-4a01-9e79-7d36aed8225a}
-
- Open
-
- &Open
-
- "[{PackageRoot}]\Contoso\WINcontosowordpad.EXE" /n "%1"
-
-
-
-
-
- mscontosowordpad
-
- ShellSystem
-
- [SHELLNOOP]
-
- [SetForeground][ShellNewDatabase"%1"]
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-```
-
-**URL Protocols** extension subsystem controls the URL protocols integrated into the local registry of the client machine, for example, _mailto:_.
-
-```XML
-
-
-
-
-
-
-
-
-
- mailto
-
-
-
- [{ProgramFilesX86}]\MicrosoftContoso\Contoso\contosomail.EXE,-9403
-
- 2
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- 2
-
-
-
-
-
- open
-
-
-
- [{ProgramFilesX86}]\Microsoft Contoso\Contoso\contosomail.EXE
-
- open
-
- [{ProgramFilesX86}\Microsoft Contoso\Contoso\contosomail.EXE" -c OEP.Note /m "%1"
-
-
-
-
-
- 0
-
- 0
-
- 2
-
-
-
-
-
- contosomail
-
- ShellSystem
-
- [SHELLNOOP]
-
- [SetForeground][ShellNewDatabase "%1"]
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-```
-
-**Software Clients** extension subsystem allows the app to register as an email client, news reader, media player and makes the app visible in the Set program access and Computer defaults UI. In most cases, you should only need to enable and disable it. There is also a control to enable and disable the email client specifically if you want the other clients still enabled except for that client.
-
-```XML
-
-
-
-
-
-
-```
-
-**AppPaths** extension subsystem opens apps registered with an application path. For example, if contoso.exe has an apppath name of _myapp_, users can type _myapp_ from the run menu, opening contoso.exe.
-
-```XML
-
-
-
-
-
-
-
-
-
- [{ProgramFilesX86}]\Microsoft Contoso\Contoso\contosomail.EXE
-
- contosomail.exe
-
- [{ProgramFilesX86}]\Microsoft Contoso\Contoso\contosomail.EXE
-
-
-
- false
-
-
-
-
-
-
-
-
-
-
-```
-
-**COM** extensions subsystem allows an application registered to local COM servers. The mode can be:
-
-- Integration
-- Isolated
-- Off
-
-```XML
-
-
-```
-
-**Virtual Kernel Objects**
-
-```XML
-
-
-```
-
-**Virtual Registry** sets a registry in the virtual registry within HKCU.
-
-```XML
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-```
-
-**Virtual File System**
-
-```XML
-
-
-```
-
-**Virtual Fonts**
-
-```XML
-
-
-```
-
-**Virtual Environment Variables**
-
-```XML
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-```
-
-**Virtual services**
-
-```XML
-
-
-```
-
-#### UserScripts
-
-Use UserScripts to set up or alter the virtual environment. You can also execute scripts at the time of deployment or to clean up the environment after the application terminates. To see a sample script, refer to the user configuration file generated by the sequencer.
-The Scripts section below provides more information on the various triggers that can be used.
-
-#### ManagingAuthority
-
-Use ManagingAuthority when two versions of your package co-exist on the same machine, one deployed to App-V 4.6 and another deployed on App-V 5.0. To allow App-V vNext to take over App-V 4.6 extension points for the named package enter the following in the UserConfig file (where PackageName is the Package GUID in App-V 4.6:
-
-```XML
-
-
-```
-
-## Deployment configuration file (DeploymentConfig.xml)
-
-The DeploymentConfig file provides configuration settings for machine context and user context, providing the same capabilities listed in the UserConfig file. The setting get applied when deploying the package to a computer running the App-V 5.1 client.
-
-Use the DeploymentConfig file to specify or modify custom settings for a package:
-
-- All UserConfig settings
-- Extensions that can only be applied globally for all users
-- Virtual subsystems for global machine locations, for example, registry
-- Product source URL
-- Scripts (machine context only)
-- Controls to terminate child processes
-
-### Header
-
-The header of a dynamic deployment configuration file looks like:
-
-```XML
-
-```
-
-The **PackageId** is the same value as exists in the manifest file.
-
-### Body
-
-The body of the dynamic deployment configuration file includes two sections:
-
-- **UserConfiguration:** allows the same content as the user configuration file described in the previous section. When publishing the package to a user, any appextensions configuration settings in this section override corresponding settings in the manifest within the package, unless you provide a user configuration file. If also providing a UserConfig file, it gets used instead of the User settings in the deployment configuration file. If publishing the package globally, then only the contents of the deployment configuration file get used in combination with the manifest. For more details, see [User configuration file contents (UserConfig.xml)](#user-configuration-file-contents-userconfigxml).
-
-- **MachineConfiguration:** contains information that can be configured only for an entire machine, not for a specific user on the machine. For example, HKEY_LOCAL_MACHINE registry keys in the VFS.
-
-```XML
-
-
-
-
-
-...
-
-
-
-
-
-...
-
-
-
-...
-
-
-
-
-```
-
-### UserConfiguration
-
-Refer to [User configuration file contents (UserConfig.xml)](#user-configuration-file-contents-userconfigxml) for information on the settings provided for this section.
-
-### MachineConfiguration
-
-Use the MachineConfiguration section to configure information for an entire machine; not for a specific user on the computer. For example, HKEY_LOCAL_MACHINE registry keys in the virtual registry. There are four subsections allowed in under this element:
-
-1. **[Subsystems](#subsystems-1)**
-2. **[ProductSourceURLOptOut](#productsourceurloptout)**
-3. **[MachineScripts](#machinescripts)**
-4. **[TerminateChildProcess](#terminatechildprocess)**
-
-#### Subsystems
-
-AppExtensions and other subsystems arranged as subnodes.
-
-```XML
-
-
-
-
-
- …
-
-
-
-…
-
-
-```
-
-You can enable or disable each subsystem using the **Enabled** attribute.
-
-**Extensions**
-
-Some subsystems (extension subsystems) control extensions. The subsystem is Application Capabilities that default programs use. For this type of extension, the package must be published globally for integration into the local system. The same rules for controls and settings that apply to the Extensions in the User Configuration also, apply to those in the MachineConfiguration section.
-
-**Application Capabilities**: Used by default programs that allow an application to register itself as:
-
-- Capable of opening specific file extensions
-- A contender for the start menu internet browser slot
-- Capable of opening specific windows MIME types
-
-This extension also makes the virtual application visible in the Set default programs UI.
-
-```XML
-
-
-
-
-
-
-
-
-
-
- [{PackageRoot}]\LitView\LitViewBrowser.exe
-
-
-
- LitView Browser
-
- SOFTWARE\LitView\Browser\Capabilities
-
-
-
-
-
-
-
-
- @[{ProgramFilesX86}]\LitView\LitViewBrowser.exe,-12345
-
-
- @[{ProgramFilesX86}]\LitView\LitViewBrowser.exe,-12346
-
- 0
-
- Lit View E-Mail Client
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-```
-
-_**Supported extension subsystems:**_
-
-**Machine Wide Virtual Registry** extension subsystem sets a registry key in the virtual registry within HKEY_Local_Machine.
-
-```XML
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-```
-
-**Machine Wide Virtual Kernel Objects**
-
-```XML
-
-
-
-
-
-
-
-
-
-
-```
-
-#### ProductSourceURLOptOut
-
-Use ProductSourceURLOptOut to indicate that the URL for the package can be modified globally through _PackageSourceRoot_ (to support branch office scenarios). Changes take effect on the next launch.
-
-```XML
-
-
-
- ...
-
-
-
- ...
-
-
-```
-
-#### MachineScripts
-
-The package can be configured to execute scripts at time of deployment, publishing or removal. To see a sample script, refer to the deployment configuration file generated by the sequencer.
-
-The Scripts section below provides more information on the various triggers that can be used.
-
-#### TerminateChildProcess
-
-An application executable can be specified, whose child processes get terminated when the application exe process terminates.
-
-```XML
-
-
-
- ...
-
-
-
-
-
-
-
-
-
-
-
- ...
-
-
-```
-
-
-
-## Scripts
-
-The following table describes the various script events and the context under which they can be run.
-
-| Script Execution Time | Can be specified in Deployment Configuration | Can be specified in User Configuration | Can run in the Virtual Environment of the package | Can be run in the context of a specific application | Runs in system/user context: (Deployment Configuration, User Configuration) |
-|-----------------------------|----------------------------------------------|----------------------------------------|---------------------------------------------------|-----------------------------------------------------|-----------------------------------------------------------------------------|
-| AddPackage | X | | | | (SYSTEM, N/A) |
-| PublishPackage | X | X | | | (SYSTEM, User) |
-| UnpublishPackage | X | X | | | (SYSTEM, User) |
-| RemovePackage | X | | | | (SYSTEM, N/A) |
-| StartProcess | X | X | X | X | (User, User) |
-| ExitProcess | X | X | | X | (User, User) |
-| StartVirtualEnvironment | X | X | X | | (User, User) |
-| TerminateVirtualEnvironment | X | X | | | (User, User) |
-
-### Using multiple scripts on a single event trigger
-
-App-V 5.1 supports the use of multiple scripts on a single event trigger for
-App-V packages, including packages that you convert from App-V 4.6 to App-V 5.0
-or later. To enable the use of multiple scripts, App-V 5.1 uses a script
-launcher application, named ScriptRunner.exe, which is installed as part of the
-App-V client installation.
-
-### How to use multiple scripts on a single event trigger
-
-For each script that you want to run, pass that script as an argument to the
-ScriptRunner.exe application. The application then runs each script separately,
-along with the arguments that you specify for each script. Use only one script
-(ScriptRunner.exe) per trigger.
-
-> [!NOTE]
->
-> We recommended that you run the multi-script line from a command prompt
-> first to make sure that all arguments are built correctly before adding them to
-> the deployment configuration file.
-
-### Example script and parameter descriptions
-
-Using the following example file and table, modify the deployment or user
-configuration file to add the scripts that you want to run.
-
-```XML
-
-
- ScriptRunner.exe
-
- -appvscript script1.exe arg1 arg2 –appvscriptrunnerparameters –wait –timeout=10
- -appvscript script2.vbs arg1 arg2
- -appvscript script3.bat arg1 arg2 –appvscriptrunnerparameters –wait –timeout=30 –rollbackonerror
-
-
-
-
-```
-
-
-**Parameters in the example file include:**
-
-#### \
-
-Name of the event trigger for which you are running a script, such as adding a package or publishing a package.
-
-#### \ScriptRunner.exe\
-
-The script launcher application that is installed as part of the App-V client installation.
-
-> [!NOTE]
->
-> Although ScriptRunner.exe is installed as part of the App-V client, the location of the App-V client must be in %path% or ScriptRunner will not run. ScriptRunner.exe is typically located in the C:FilesApplication Virtualizationfolder.
-
-#### \
-
-`-appvscript` - Token that represents the actual script that you want to run.
-
-`script1.exe` – Name of the script that you want to run.
-
-`arg1 arg2` – Arguments for the script that you want to run.
-
-`-appvscriptrunnerparameters` – Token that represents the execution options for script1.exe.
-
-`-wait` – Token that informs ScriptRunner to wait for execution of script1.exe to complete before proceeding to the next script.
-
-`-timeout=x` – Token that informs ScriptRunner to stop running the current script after x number of seconds. All other specified scripts still runs.
-
-`-rollbackonerror` – Token that informs ScriptRunner to stop running all scripts that haven't yet run and to roll back an error to the App-V client.
-
-#### \
-
-Waits for overall completion of ScriptRunner.exe.
-
-Set the timeout value for the overall runner to be greater than or equal to the sum of the timeout values on the individual scripts.
-
-If any individual script reported an error and rollbackonerror was set to true, then ScriptRunner would report the error to App-V client.
-
-ScriptRunner runs any script whose file type is associated with an application installed on the computer. If the associated application is missing, or the script’s file type is not associated with any application on the computer, the script does not run.
-
-### Create a dynamic configuration file using an App-V 5.1 manifest file
-
-You can create the dynamic configuration file using one of three methods: either manually, using the App-V 5.1 Management Console or sequencing a package, which generates two sample files. For more information about how to create the file using the App-V 5.1 Management Console see, [How to create a custom configuration File by using the App-V 5.1 Management Console](how-to-create-a-custom-configuration-file-by-using-the-app-v-51-management-console.md).
-
-To create the file manually, the information above in previous sections can be combined into a single file. We recommend you use files generated by the sequencer.
-
-
-
-- 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/home?forum=mdopappv).
-
-## Related topics
-
-- [How to Apply the Deployment Configuration File by Using PowerShell](how-to-apply-the-deployment-configuration-file-by-using-powershell51.md)
-
-- [How to Apply the User Configuration File by Using PowerShell](how-to-apply-the-user-configuration-file-by-using-powershell51.md)
-
-- [Operations for App-V 5.1](operations-for-app-v-51.md)
-
----
diff --git a/mdop/appv-v5/about-app-v-51-reporting.md b/mdop/appv-v5/about-app-v-51-reporting.md
deleted file mode 100644
index 381a1231a7..0000000000
--- a/mdop/appv-v5/about-app-v-51-reporting.md
+++ /dev/null
@@ -1,253 +0,0 @@
----
-title: About App-V 5.1 Reporting
-description: About App-V 5.1 Reporting
-author: dansimp
-ms.assetid: 385dca00-7178-4e35-8d86-c58867ebd65c
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 08/30/2016
----
-
-
-# About App-V 5.1 Reporting
-
-Microsoft Application Virtualization (App-V) 5.1 includes a built-in reporting feature that helps you collect information about computers running the App-V 5.1 client as well as information about virtual application package usage. You can use this information to generate reports from a centralized database.
-
-## App-V 5.1 Reporting Overview
-
-The following list displays the end–to-end high-level workflow for reporting in App-V 5.1.
-
-1. The App-V 5.1 Reporting server has the following prerequisites:
-
- - Internet Information Service (IIS) web server role
-
- - Windows Authentication role (under **IIS / Security**)
-
- - SQL Server installed and running with SQL Server Reporting Services (SSRS)
-
- To confirm SQL Server Reporting Services is running, view `http://localhost/Reports` in a web browser as administrator on the server that will host App-V 5.1 Reporting. The SQL Server Reporting Services Home page should display.
-
-2. Install the App-V 5.1 reporting server and associated database. For more information about installing the reporting server see [How to install the Reporting Server on a Standalone Computer and Connect it to the Database](how-to-install-the-reporting-server-on-a-standalone-computer-and-connect-it-to-the-database51.md). Configure the time when the computer running the App-V 5.1 client should send data to the reporting server.
-
-3. If you are not using an electronic software distribution system such as Configuration Manager to view reports then you can define reports in SQL Server Reporting Service. Download predefined SSRS Reports from the [Download Center](https://go.microsoft.com/fwlink/?LinkId=397255).
-
- > [!NOTE]
- > If you are using the Configuration Manager integration with App-V 5.1, most reports are generated from Configuration Manager rather than from App-V 5.1.
-
-4. After importing the App-V 5.1 PowerShell module using `Import-Module AppvClient` as administrator, enable the App-V 5.1 client. This sample PowerShell cmdlet enables App-V 5.1 reporting:
-
- ```powershell
- Set-AppvClientConfiguration –reportingserverurl : -reportingenabled 1 – ReportingStartTime <0-23> - ReportingRandomDelay <#min>
- ```
-
- To immediately send App-V 5.1 report data, run `Send-AppvClientReport` on the App-V 5.1 client.
-
- For more information about installing the App-V 5.1 client with reporting enabled see [About Client Configuration Settings](about-client-configuration-settings51.md). To administer App-V 5.1 Reporting with Windows PowerShell, see [How to Enable Reporting on the App-V 5.1 Client by Using PowerShell](how-to-enable-reporting-on-the-app-v-51-client-by-using-powershell.md).
-
-5. After the reporting server receives the data from the App-V 5.1 client it sends the data to the reporting database. When the database receives and processes the client data, a successful reply is sent to the reporting server and then a notification is sent to the App-V 5.1 client.
-
-6. When the App-V 5.1 client receives the success notification, it empties the data cache to conserve space.
-
- > [!NOTE]
- > By default the cache is cleared after the server confirms receipt of data. You can manually configure the client to save the data cache.
-
-If the App-V 5.1 client device does not receive a success notification from the server, it retains data in the cache and tries to resend data at the next configured interval. Clients continue to collect data and add it to the cache.
-
-### App-V 5.1 reporting server frequently asked questions
-
-The following table displays answers to common questions about App-V 5.1 reporting
-
-
-
-
-
-
-
-
-
Question
-
More Information
-
-
-
-
-
What is the frequency that reporting information is sent to the reporting database?
-
The frequency depends on how the reporting task is configured on the computer running the App-V 5.1 client. You must configure the frequency / interval for sending the reporting data. App-V 5.1 Reporting is not enabled by default.
-
-
-
What information is stored in the reporting server database?
-
The following list displays what is stored in the reporting database:
-
-
The operating system running on the computer running the App-V 5.1 client: host name, version, service pack, type - client/server, processor architecture.
-
App-V 5.1 Client information: version.
-
Published package list: GUID, version GUID, name.
-
Application usage information: name, version, streaming server, user (domain\alias), package version GUID, launch status and time, shutdown time.
-
-
-
-
What is the average volume of information that is sent to the reporting server?
-
It depends. The following list displays the three sets of the data sent to the reporting server:
-
-
Operating system, and App-V 5.1 client information. ~150 Bytes, every time this data is sent.
-
Published package list. ~7 KB for 30 packages. This is sent only when the package list is updated with a publishing refresh, which is done infrequently; if there is no change, this information is not sent.
-
Virtual application usage information – about 0.25KB per event. Opening and closing count as one event if both occur before sending the information. When sending using a scheduled task, only the data since the last successful upload is sent to the server. If sending manually through the PowerShell cmdlet, there is an optional argument that controls if the data needs to be re-sent next time around – that argument is DeleteOnSuccess.
-
-
So for example, if twenty applications are opened and closed and reporting information is scheduled to be sent daily, the typical daily traffic should be about 0.15KB + 20 x 0.25KB, or about 5KB/user
-
-
-
-
Can reporting be scheduled?
-
Yes. Besides manually sending reporting using PowerShell Cmdlets (Send-AppvClientReport), the task can be scheduled so it will happen automatically. There are two ways to schedule the reporting:
-
-
Using PowerShell cmdlets - Set-AppvClientConfiguration. For example:
For a complete list of client configuration settings see About Client Configuration Settings and look for the following entries: ReportingEnabled, ReportingServerURL, ReportingDataCacheLimit, ReportingDataBlockSize, ReportingStartTime, ReportingRandomDelay, ReportingInterval.
-
-
By using Group Policy. If distributed using the domain controller, the settings are the same as previously listed.
-
-Note
Group Policy settings override local settings configured using PowerShell.
-
-
-
-
-
-
-
-
-## App-V 5.1 Client Reporting
-
-To use App-V 5.1 reporting you must install and configure the App-V 5.1 client. After the client has been installed, use the **Set-AppVClientConfiguration** PowerShell cmdlet or the **ADMX Template** to configure reporting. The reporting feature cmdlets are available by using the following link and are prefaced by **Reporting**. For a complete list of client configuration settings see [About Client Configuration Settings](about-client-configuration-settings51.md). The following section provides examples of App-V 5.1 client reporting configuration using PowerShell.
-
-### Configuring App-V Client reporting using PowerShell
-
-The following examples show how PowerShell parameters can configure the reporting features of the App-V 5.1 client.
-
-> [!NOTE]
-> The following configuration task can also be configured using Group Policy settings in the App-V 5.1 ADMX template. For more information about using the ADMX template, see [How to Modify App-V 5.1 Client Configuration Using the ADMX Template and Group Policy](how-to-modify-app-v-51-client-configuration-using-the-admx-template-and-group-policy.md).
-
-**To enable reporting and to initiate data collection on the computer running the App-V 5.1 client**:
-
-```powershell
-Set-AppVClientConfiguration –ReportingEnabled 1
-```
-
-**To configure the client to automatically send data to a specific reporting server**:
-
-```powershell
-Set-AppVClientConfiguration –ReportingServerURL http://MyReportingServer:MyPort/ -ReportingStartTime 20 -ReportingInterval 1 -ReportingRandomDelay 30 -ReportingInterval 1 -ReportingRandomDelay 30
-```
-
-This example configures the client to automatically send the reporting data to the reporting server URL **http://MyReportingServer:MyPort/**. Additionally, the reporting data will be sent daily between 8:00 and 8:30 PM, depending on the random delay generated for the session.
-
-**To limit the size of the data cache on the client**:
-
-```powershell
-Set-AppvClientConfiguration –ReportingDataCacheLimit 100
-```
-
-Configures the maximum size of the reporting cache on the computer running the App-V 5.1 client to 100 MB. If the cache limit is reached before the data is sent to the server, then the log rolls over and data will be overwritten as necessary.
-
-**To configure the data block size transmitted across the network between the client and the server**:
-
-```powershell
-Set-AppvClientConfiguration –ReportingDataBlockSize 10240
-```
-
-Specifies the maximum data block that the client sends to 10240 MB.
-
-### Types of data collected
-
-The following table displays the types of information you can collect by using App-V 5.1 reporting.
-
-|Client Information |Package Information |Application Usage |
-|---------|---------|---------|
-|Host Name |Package Name|Start and End Times|
-|App-V 5.1 Client Version |Package Version|Run Status|
-|Processor Architecture |Package Source|Shutdown State|
-|Operating System Version|Percent Cached|Application Name|
-|Service Pack Level| |Application Version|
-|Operating System Type| |Username|
-| | |Connection Group|
-
-The client collects and saves this data in an **.xml** format. The data cache is hidden by default and requires administrator rights to open the XML file.
-
-### Sending data to the server
-
-You can configure the computer that is running the App-V 5.1 client to automatically send data to the specified reporting server. To specify the server use the **Set-AppvClientConfiguration** cmdlet with the following settings:
-
-- ReportingEnabled
-- ReportingServerURL
-- ReportingStartTime
-- ReportingInterval
-- ReportingRandomDelay
-
-After you configure the previous settings, you must create a scheduled task. The scheduled task will contact the server specified by the **ReportingServerURL** setting and will initiate the transfer. If you want to manually send data outside of the scheduled times, use the following PowerShell cmdlet:
-
-```powershell
-Send-AppVClientReport –URL http://MyReportingServer:MyPort/ -DeleteOnSuccess
-```
-
-If the reporting server has been previously configured, then the **–URL** parameter can be omitted. Alternatively, if the data should be sent to an alternate location, specify a different URL to override the configured **ReportingServerURL** for this data collection.
-
-The **-DeleteOnSuccess** parameter indicates that if the transfer is successful, then the data cache is cleared. If this is not specified, then the cache will not be cleared.
-
-### Manual Data Collection
-
-You can also use the **Send-AppVClientReport** cmdlet to manually collect data. This solution is helpful with or without an existing reporting server. The following list displays information about collecting data with or without a reporting server.
-
-
-
-
-
-
-
-
-
With a Reporting Server
-
Without a Reporting Server
-
-
-
-
-
If you have an existing App-V 5.1 reporting Server, create a customized scheduled task or script. Specify that the client send the data to the specified location with the desired frequency.
-
If you do not have an existing App-V 5.1 reporting Server, use the –URL parameter to send the data to a specified share. For example:
The previous example will send the reporting data to \MyShare\MyData</strong> location indicated by the -URL parameter. After the data has been sent, the cache is cleared.
-
-Note
If a location other than the Reporting Server is specified, the data is sent using .xml format with no additional processing.
-
-
-
-
-
-
-
-### Creating Reports
-
-To retrieve report information and create reports using App-V 5.1 you must use one of the following methods:
-
-- **Microsoft SQL Server Reporting Services (SSRS)** - Microsoft SQL Server Reporting Services is available with Microsoft SQL Server. SSRS is not installed when you install the App-V 5.1 reporting server. It must be deployed separately to generate the associated reports.
-
- Use the following link for more information about using [Microsoft SQL Server Reporting Services](https://go.microsoft.com/fwlink/?LinkId=285596).
-
-- **Scripting** – You can generate reports by scripting directly against the App-V 5.1 reporting database. For example:
-
- **Stored Procedure:**
-
- **spProcessClientReport** is scheduled to run at midnight or 12:00 AM.
-
- To run the Microsoft SQL Server Scheduled Stored procedure, the Microsoft SQL Server Agent must be running. You should ensure that the Microsoft SQL Server Agent is set to **AutoStart**. For more information see [Autostart SQL Server Agent (SQL Server Management Studio)](https://go.microsoft.com/fwlink/?LinkId=287045).
-
- The stored procedure is also created when using the App-V 5.1 database scripts.
-
-You should also ensure that the reporting server web service's **Maximum Concurrent Connections** is set to a value that the server will be able to manage without impacting availability. The recommended number of **Maximum Concurrent Connections** for the **Reporting Web Service** is **10,000**.
-
-## Related topics
-
-[Deploying the App-V 5.1 Server](deploying-the-app-v-51-server.md)
-
-[How to install the Reporting Server on a Standalone Computer and Connect it to the Database](how-to-install-the-reporting-server-on-a-standalone-computer-and-connect-it-to-the-database51.md)
diff --git a/mdop/appv-v5/about-app-v-51.md b/mdop/appv-v5/about-app-v-51.md
deleted file mode 100644
index f52bcf1b64..0000000000
--- a/mdop/appv-v5/about-app-v-51.md
+++ /dev/null
@@ -1,527 +0,0 @@
----
-title: About App-V 5.1
-description: About App-V 5.1
-author: dansimp
-ms.assetid: 35bc9908-d502-4a9c-873f-8ee17b6d9d74
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 08/30/2016
----
-
-
-# About App-V 5.1
-
-
-Use the following sections to review information about significant changes that apply to Application Virtualization (App-V) 5.1:
-
-[App-V 5.1 software prerequisites and supported configurations](#bkmk-51-prereq-configs)
-
-[Migrating to App-V 5.1](#bkmk-migrate-to-51)
-
-[What’s New in App-V 5.1](#bkmk-whatsnew)
-
-[App-V support for Windows 10](#bkmk-win10support)
-
-[App-V Management Console Changes](#bkmk-mgmtconsole)
-
-[Sequencer Improvements](#bkmk-seqimprove)
-
-[Improvements to Package Converter](#bkmk-pkgconvimprove)
-
-[Support for multiple scripts on a single event trigger](#bkmk-supmultscripts)
-
-[Hardcoded path to installation folder is redirected to virtual file system root](#bkmk-hardcodepath)
-
-## App-V 5.1 software prerequisites and supported configurations
-
-
-See the following links for the App-V 5.1 software prerequisites and supported configurations.
-
-
-
-
-
-
-
-
-
Links to prerequisites and supported configurations
Supported operating systems and hardware requirements for the App-V Server, Sequencer, and Client components
-
-
-
-
-
-
-**Support for using Configuration Manager with App-V:** App-V 5.1 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.
-
-## Migrating to App-V 5.1
-
-
-Use the following information to upgrade to App-V 5.1 from earlier versions. See [Migrating to App-V 5.1 from a Previous Version](migrating-to-app-v-51-from-a-previous-version.md) for more information.
-
-### Before you start the upgrade
-
-Review the following information before you start the upgrade:
-
-
-
-
-
-
-
-
-
Items to review before upgrading
-
Description
-
-
-
-
-
Components to upgrade, in any order
-
-
App-V Server
-
Sequencer
-
App-V Client or App-V Remote Desktop Services (RDS) Client
-
-
-Note
Prior to App-V 5.0 SP2, the Client Management User Interface (UI) was provided with the App-V Client installation. For App-V 5.0 SP2 installations (or later), you can use the Client Management UI by downloading from Application Virtualization 5.0 Client UI Application.
-
-
-
-
-
-
-
Upgrading from App-V 4.x
-
You must first upgrade to App-V 5.0. You cannot upgrade directly from App-V 4.x to App-V 5.1. For more information, see:
-
-
“Differences between App-V 4.6 and App-V 5.0” in About App-V 5.0
You can upgrade to App-V 5.1 directly from any of the following versions:
-
-
App-V 5.0
-
App-V 5.0 SP1
-
App-V 5.0 SP2
-
App-V 5.0 SP3
-
-
To upgrade to App-V 5.1, follow the steps in the remaining sections of this topic.
-
Packages and connection groups will continue to work with App-V 5.1 as they currently do.
-
-
-
-
-
-
-### Steps to upgrade the App-V infrastructure
-
-Complete the following steps to upgrade each component of the App-V infrastructure to App-V 5.1. The following order is only a suggestion; you may upgrade components in any order.
-
-
-
-
-
-
-
-
-
Step
-
For more information
-
-
-
-
-
Step 1: Upgrade the App-V Server.
-
-Note
If you are not using the App-V Server, skip this step and go to the next step.
-
-
-
-
-
Follow these steps:
-
-
Do one of the following, depending on the method you are using to upgrade the Management database and/or Reporting database:
-
-
-
-
-
-
-
-
Database upgrade method
-
Step
-
-
-
-
-
Windows Installer
-
Skip this step and go to step 2, “If you are upgrading the App-V Server...”
-
-
-
-### 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.
-
-**Note**
-App-V 5.1 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 5.1 packages.
-
-
-
-## What’s New in App-V 5.1
-
-
-These sections are for users who are already familiar with App-V and want to know what has changed in App-V 5.1. If you are not already familiar with App-V, you should start by reading [Planning for App-V 5.1](planning-for-app-v-51.md).
-
-### 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 5.1.
-
-
-
-
-
-
-
-
-
-
Component
-
App-V 5.1
-
App-V 5.0
-
-
-
-
-
App-V Client
-
Yes
-
No
-
-
-
App-V RDS Client
-
Yes
-
No
-
-
-
App-V Sequencer
-
Yes
-
No
-
-
-
-
-
-
-### App-V Management Console Changes
-
-This section compares the App-V 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.
-
-### Notifications and messages are displayed individually in a dialog box
-
-
-
-
-
-
-
-
-
New in App-V 5.1
-
Prior to App-V 5.1
-
-
-
-
-
Number of messages indicator:
-
On the title bar of the App-V Management Console, a number is now displayed next to a flag icon to indicate the number of messages that are waiting to be read.
-
You could see only one message or error at a time, and you were unable to determine how many messages there were.
-
-
-
Message appearance:
-
-
Messages that require user input appear in a separate dialog box that displays on top of the current page that you were viewing, and require a response before you can dismiss them.
-
Messages and errors appear in a list, with one beneath the other.
-
-
You could see only one message or error at a time.
-
-
-
Dismissing messages:
-
Use the Dismiss All link to dismiss all messages and errors at one time, or dismiss them one at a time.
-
You could dismiss messages and errors only one at a time.
-
-
-
-
-
-
-### Console pages are now separate URLs
-
-
-
-
-
-
-
-
-
New in App-V 5.1
-
Prior to App-V 5.1
-
-
-
-
-
Each page in the console has a different URL, which enables you to bookmark specific pages for quick access in the future.
-
The number that appears in some URLs indicates the specific package. These numbers are unique.
-
All console pages are accessed through the same URL.
-
-
-
-
-
-
-### New, separate CONNECTION GROUPS page and menu option
-
-
-
-
-
-
-
-
-
New in App-V 5.1
-
Prior to App-V 5.1
-
-
-
-
-
The CONNECTION GROUPS page is now part of the main menu, at the same level as the PACKAGES page.
-
To open the CONNECTION GROUPS page, you navigate through the PACKAGES page.
-
-
-
-
-
-
-### Menu options for packages have changed
-
-
-
-
-
-
-
-
-
New in App-V 5.1
-
Prior to App-V 5.1
-
-
-
-
-
The following options are now buttons that appear at the bottom of the PACKAGES page:
-
-
Add or Upgrade
-
Publish
-
Unpublish
-
Delete
-
-
The following options will still appear when you right-click a package to open the drop-down context menu:
-
-
Publish
-
Unpublish
-
Edit AD Access
-
Edit Deployment Config
-
Transfer deployment configuration from…
-
Transfer access and configuration from…
-
Delete
-
-
When you click Delete to remove a package, a dialog box opens and asks you to confirm that you want to delete the package.
-
The Add or Upgrade option was a button at the top right of the PACKAGES page.
-
The Publish, Unpublish, and Delete options were available only if you right-clicked a package name in the packages list.
-
-
-
The following package operations are now buttons on the package details page for each package:
-
-
Transfer (drop-down menu with the following options):
-
-
Transfer deployment configuration from…
-
Transfer access and configuration from…
-
-
Edit (connection groups and AD Access)
-
Unpublish
-
Delete
-
Edit Default Configuration
-
-
These package options were available only if you right-clicked a package name in the packages list.
-
-
-
-
-
-
-### Icons in left pane have new colors and text
-
-The colors of the icons in the left pane have been changed, and text added, to make the icons consistent with other Microsoft products.
-
-### Overview page has been removed
-
-In the left pane of the Management Console, the OVERVIEW menu option and its associated OVERVIEW page have been removed.
-
-### Sequencer Improvements
-
-The following improvements have been made to the package editor in the App-V 5.1 Sequencer.
-
-### 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**
-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
-
-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
-
-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.
-
-### 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:
-
-- Press **Ctrl+H**
-
-- Right-click a key and select **Replace**.
-
-- Select **View** > **Virtual Registry** > **Replace**.
-
-Previously, the “Replace” dialog box did not exist, and you had to make changes manually.
-
-### 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
-
-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
-
-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 5.1, you could not import directories.
-
-### 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.
-
-To export a file, select the **Package Files** tab, right-click the file in the VFS, click **Export**, and choose an export location from which you can make your edits.
-
-To import a file, select the **Package Files** tab and right-click the file that you had exported. Browse to the file that you edited, and then click **Import**. The imported file will overwrite the existing file.
-
-After you import a file, you must save the package by clicking **File** > **Save**.
-
-### 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
-
-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
-
-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:
-
-- Exist in the package and are enabled, the check box is selected by default.
-
-- Exist in the package and are disabled, the check box is clear by default.
-
-- Exist in the package, with one or more enabled and one or more disabled, the check box is set to indeterminate by default.
-
-- Do not exist in the package, the check box is disabled.
-
-### Improvements to Package Converter
-
-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 5.1 from a Previous Version](migrating-to-app-v-51-from-a-previous-version.md).
-
-### Support for multiple scripts on a single event trigger
-
-App-V 5.1 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 5.1 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 5.1 Dynamic Configuration](about-app-v-51-dynamic-configuration.md).
-
-### 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 5.1 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 5.1 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 5.1 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 5.1 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](https://go.microsoft.com/fwlink/?LinkId=322049).
-
-
-
-
-
-
-## Related topics
-
-
-[Release Notes for App-V 5.1](release-notes-for-app-v-51.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v5/about-client-configuration-settings.md b/mdop/appv-v5/about-client-configuration-settings.md
deleted file mode 100644
index 9ba08f850a..0000000000
--- a/mdop/appv-v5/about-client-configuration-settings.md
+++ /dev/null
@@ -1,473 +0,0 @@
----
-title: About Client Configuration Settings
-description: About Client Configuration Settings
-author: dansimp
-ms.assetid: cc7ae28c-b2ac-4f68-b992-5ccdbd5316a4
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# About Client Configuration Settings
-
-
-The Microsoft Application Virtualization (App-V) 5.0 client stores its configuration in the registry. You can gather some useful information about the client if you understand the format of data in the registry. You can also configure many client actions by changing registry entries. This topic lists the App-V 5.0 Client configuration settings and explains their uses. You can use PowerShell to modify the client configuration settings. For more information about using PowerShell and App-V 5.0 see [Administering App-V by Using PowerShell](administering-app-v-by-using-powershell.md).
-
-## App-V 5.0 Client Configuration Settings
-
-
-The following table displays information about the App-V 5.0 client configuration settings:
-
-
-
-
-
-
-
-
-
-
-
-
-
Setting Name
-
Setup Flag
-
Description
-
Setting Options
-
Registry Key Value
-
Disabled Policy State Keys and Values
-
-
-
-
-
PackageInstallationRoot
-
PACKAGEINSTALLATIONROOT
-
Specifies directory where all new applications and updates will be installed.
-
String
-
Streaming\PackageInstallationRoot
-
Policy value not written (same as Not Configured)
-
-
-
PackageSourceRoot
-
PACKAGESOURCEROOT
-
Overrides source location for downloading package content.
-
String
-
Streaming\PackageSourceRoot
-
Policy value not written (same as Not Configured)
-
-
-
AllowHighCostLaunch
-
Not available.
-
This setting controls whether virtualized applications are launched on Windows 8 machines connected via a metered network connection (For example, 4G).
-
True (enabled); False (Disabled state)
-
Streaming\AllowHighCostLaunch
-
0
-
-
-
ReestablishmentRetries
-
Not available.
-
Specifies the number of times to retry a dropped session.
-
Integer (0-99)
-
Streaming\ReestablishmentRetries
-
Policy value not written (same as Not Configured)
-
-
-
ReestablishmentInterval
-
Not available.
-
Specifies the number of seconds between attempts to reestablish a dropped session.
-
Integer (0-3600)
-
Streaming\ReestablishmentInterval
-
Policy value not written (same as Not Configured)
-
-
-
AutoLoad
-
AUTOLOAD
-
Specifies how new packages should be loaded automatically by App-V on a specific computer.
-
(0x0) None; (0x1) Previously used; (0x2) All
-
Streaming\AutoLoad
-
Policy value not written (same as Not Configured)
-
-
-
LocationProvider
-
Not available.
-
Specifies the CLSID for a compatible implementation of the IAppvPackageLocationProvider interface.
-
String
-
Streaming\LocationProvider
-
Policy value not written (same as Not Configured)
-
-
-
CertFilterForClientSsl
-
Not available.
-
Specifies the path to a valid certificate in the certificate store.
-
String
-
Streaming\CertFilterForClientSsl
-
Policy value not written (same as Not Configured)
-
-
-
VerifyCertificateRevocationList
-
Not available.
-
Verifies Server certificate revocation status before steaming using HTTPS.
-
True(enabled); False(Disabled state)
-
Streaming\VerifyCertificateRevocationList
-
0
-
-
-
SharedContentStoreMode
-
SHAREDCONTENTSTOREMODE
-
Specifies that streamed package contents will be not be saved to the local hard disk.
-
True(enabled); False(Disabled state)
-
Streaming\SharedContentStoreMode
-
0
-
-
-
Name
-
-Note
This setting cannot be modified using the set-AppvclientConfiguration cmdLet. You must use the Set-AppvPublishingServer cmdlet.
-
-
-
-
-
PUBLISHINGSERVERNAME
-
Displays the name of publishing server.
-
String
-
Publishing\Servers{serverId}\FriendlyName
-
Policy value not written (same as Not Configured)
-
-
-
URL
-
-Note
This setting cannot be modified using the set-AppvclientConfiguration cmdLet. You must use the Set-AppvPublishingServer cmdlet.
-
-
-
-
-
PUBLISHINGSERVERURL
-
Displays the URL of publishing server.
-
String
-
Publishing\Servers{serverId}\URL
-
Policy value not written (same as Not Configured)
-
-
-
GlobalRefreshEnabled
-
-Note
This setting cannot be modified using the set-AppvclientConfiguration cmdLet. You must use the Set-AppvPublishingServer cmdlet.
-
-
-
-
-
GLOBALREFRESHENABLED
-
Enables global publishing refresh (Boolean)
-
True(enabled); False(Disabled state)
-
Publishing\Servers{serverId}\GlobalEnabled
-
False
-
-
-
GlobalRefreshOnLogon
-
-Note
This setting cannot be modified using the set-AppvclientConfiguration cmdLet. You must use the Set-AppvPublishingServer cmdlet.
-
-
-
-
-
GLOBALREFRESHONLOGON
-
Triggers a global publishing refresh on logon. ( Boolean)
-
True(enabled); False(Disabled state)
-
Publishing\Servers{serverId}\GlobalLogonRefresh
-
False
-
-
-
GlobalRefreshInterval
-
-Note
This setting cannot be modified using the set-AppvclientConfiguration cmdLet. You must use the Set-AppvPublishingServer cmdlet.
-
-
-
-
-
GLOBALREFRESHINTERVAL
-
Specifies the publishing refresh interval using the GlobalRefreshIntervalUnit. To disable package refresh, select 0.
Migration mode allows the App-V client to modify shortcuts and FTA’s for packages created using a previous version of App-V.
-
True(enabled state); False (disabled state)
-
Coexistence\MigrationMode
-
-
-
-
CEIPOPTIN
-
CEIPOPTIN
-
Allows the computer running the App-V 5.0 Client to collect and return certain usage information to help allow us to further improve the application.
-
0 for disabled; 1 for enabled
-
SOFTWARE/Microsoft/AppV/CEIP/CEIPEnable
-
0
-
-
-
EnablePackageScripts
-
ENABLEPACKAGESCRIPTS
-
Enables scripts defined in the package manifest of configuration files that should run.
-
True(enabled); False(Disabled state)
-
\Scripting\EnablePackageScripts
-
-
-
-
RoamingFileExclusions
-
ROAMINGFILEEXCLUSIONS
-
Specifies the file paths relative to %userprofile% that do not roam with a user's profile. Example usage: /ROAMINGFILEEXCLUSIONS='desktop;my pictures'
-
-
-
-
-
-
RoamingRegistryExclusions
-
ROAMINGREGISTRYEXCLUSIONS
-
Specifies the registry paths that do not roam with a user profile. Example usage: /ROAMINGREGISTRYEXCLUSIONS=software\classes;software\clients
-
String
-
Integration\RoamingRegistryExclusions
-
Policy value not written (same as Not Configured)
-
-
-
IntegrationRootUser
-
Not available.
-
Specifies the location to create symbolic links associated with the current version of a per-user published package. all virtual application extensions, for example shortcuts and file type associations, will point to this path. If you do not specify a path, symbolic links will not be used when you publish the package. For example: %localappdata%\Microsoft\AppV\Client\Integration.
-
String
-
Integration\IntegrationRootUser
-
Policy value not written (same as Not Configured)
-
-
-
IntegrationRootGlobal
-
Not available.
-
Specifies the location to create symbolic links associated with the current version of a globally published package. all virtual application extensions, for example shortcuts and file type associations, will point to this path. If you do not specify a path, symbolic links will not be used when you publish the package. For example: %allusersprofile%\Microsoft\AppV\Client\Integration
-
String
-
Integration\IntegrationRootGlobal
-
Policy value not written (same as Not Configured)
-
-
-
VirtualizableExtensions
-
Not available.
-
A comma -delineated list of file name extensions that can be used to determine if a locally installed application can be run in the virtual environment.
-
When shortcuts, FTAs, and other extension points are created during publishing, App-V will compare the file name extension to the list if the application that is associated with the extension point is locally installed. If the extension is located, the RunVirtual command line parameter will be added, and the application will run virtually.
Enables the client to return information to a reporting server.
-
True (enabled); False (Disabled state)
-
Reporting\EnableReporting
-
False
-
-
-
ReportingServerURL
-
Not available.
-
Specifies the location on the reporting server where client information is saved.
-
String
-
Reporting\ReportingServer
-
Policy value not written (same as Not Configured)
-
-
-
ReportingDataCacheLimit
-
Not available.
-
Specifies the maximum size in megabytes (MB) of the XML cache for storing reporting information. The size applies to the cache in memory. When the limit is reached, the log file will roll over. Set between 0 and 1024.
-
Integer [0-1024]
-
Reporting\DataCacheLimit
-
Policy value not written (same as Not Configured)
-
-
-
ReportingDataBlockSize
-
Not available.
-
Specifies the maximum size in bytes to transmit to the server for reporting upload requests. This can help avoid permanent transmission failures when the log has reached a significant size. Set between 1024 and unlimited.
-
Integer [1024 - Unlimited]
-
Reporting\DataBlockSize
-
Policy value not written (same as Not Configured)
-
-
-
ReportingStartTime
-
Not available.
-
Specifies the time to initiate the client to send data to the reporting server. You must specify a valid integer between 0-23 corresponding to the hour of the day. By default the ReportingStartTime will start on the current day at 10 P.M.or 22.
-
-Note
You should configure this setting to a time when computers running the App-V 5.0 client are least likely to be offline.
-
-
-
-
-
Integer (0 – 23)
-
Reporting\ StartTime
-
Policy value not written (same as Not Configured)
-
-
-
ReportingInterval
-
Not available.
-
Specifies the retry interval that the client will use to resend data to the reporting server.
-
Integer
-
Reporting\RetryInterval
-
Policy value not written (same as Not Configured)
-
-
-
ReportingRandomDelay
-
Not available.
-
Specifies the maximum delay (in minutes) for data to be sent to the reporting server. When the scheduled task is started, the client generates a random delay between 0 and ReportingRandomDelay and will wait the specified duration before sending data. This can help to prevent collisions on the server.
-
Integer [0 - ReportingRandomDelay]
-
Reporting\RandomDelay
-
Policy value not written (same as Not Configured)
-
-
-
EnableDynamicVirtualization
-
-Important
This setting is available only with App-V 5.0 SP2 or later.
-
-
-
-
-
Not available.
-
Enables supported Shell Extensions, Browser Helper Objects, and Active X controls to be virtualized and run with virtual applications.
This setting is available only with App-V 5.0 SP2.
-
-
-
-
-
Not available.
-
Hides the publishing refresh progress bar.
-
1 (Enabled), 0 (Disabled)
-
-
-
-
-
ProcessesUsingVirtualComponents
-
Not available.
-
Specifies a list of process paths (that may contain wildcards), which are candidates for using dynamic virtualization (supported shell extensions, browser helper objects, and ActiveX controls). Only processes whose full path matches one of these items can use dynamic virtualization.
-
String
-
Virtualization\ProcessesUsingVirtualComponents
-
Empty string.
-
-
-
-
-
-
-
-
-
-
-
-## Related topics
-
-
-[Deploying the App-V 5.0 Sequencer and Client](deploying-the-app-v-50-sequencer-and-client.md)
-
-[How to Modify App-V 5.0 Client Configuration Using the ADMX Template and Group Policy](how-to-modify-app-v-50-client-configuration-using-the-admx-template-and-group-policy.md)
-
-[How to Deploy the App-V Client](how-to-deploy-the-app-v-client-gb18030.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v5/about-client-configuration-settings51.md b/mdop/appv-v5/about-client-configuration-settings51.md
deleted file mode 100644
index 0ea5586f2b..0000000000
--- a/mdop/appv-v5/about-client-configuration-settings51.md
+++ /dev/null
@@ -1,89 +0,0 @@
----
-title: About Client Configuration Settings
-description: About Client Configuration Settings
-author: dansimp
-ms.assetid: 18bb307a-7eda-4dd6-a83e-6afaefd99470
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# About Client Configuration Settings
-
-
-The Microsoft Application Virtualization (App-V) 5.1 client stores its configuration in the registry. You can gather some useful information about the client if you understand the format of data in the registry. You can also configure many client actions by changing registry entries. This topic lists the App-V 5.1 Client configuration settings and explains their uses. You can use PowerShell to modify the client configuration settings. For more information about using PowerShell and App-V 5.1 see [Administering App-V 5.1 by Using PowerShell](administering-app-v-51-by-using-powershell.md).
-
-## App-V 5.1 Client Configuration Settings
-
-
-The following table displays information about the App-V 5.1 client configuration settings:
-
-|Setting name | Setup Flag | Description | Setting Options | Registry Key Value | Disabled Policy State Keys and Values |
-|-------------|------------|-------------|-----------------|--------------------|--------------------------------------|
-| PackageInstallationRoot | PACKAGEINSTALLATIONROOT | Specifies directory where all new applications and updates will be installed. | String | Streaming\PackageInstallationRoot | Policy value not written (same as Not Configured) |
-| PackageSourceRoot | PACKAGESOURCEROOT | Overrides source location for downloading package content. | String | Streaming\PackageSourceRoot | Policy value not written (same as Not Configured) |
-| AllowHighCostLaunch | Not available. |This setting controls whether virtualized applications are launched on Windows 10 machines connected via a metered network connection (For example, 4G). | True (enabled); False (Disabled state) | Streaming\AllowHighCostLaunch | 0 |
-| ReestablishmentRetries | Not available. | Specifies the number of times to retry a dropped session. | Integer (0-99) | Streaming\ReestablishmentRetries | Policy value not written (same as Not Configured) |
-| ReestablishmentInterval | Not available. | Specifies the number of seconds between attempts to reestablish a dropped session. | Integer (0-3600) | Streaming\ReestablishmentInterval | Policy value not written (same as Not Configured) |
-| LocationProvider | Not available. | Specifies the CLSID for a compatible implementation of the IAppvPackageLocationProvider interface. | String | Streaming\LocationProvider | Policy value not written (same as Not Configured) |
-| CertFilterForClientSsl | Not available. | Specifies the path to a valid certificate in the certificate store. | String | Streaming\CertFilterForClientSsl | Policy value not written (same as Not Configured) |
-| VerifyCertificateRevocationList | Not available. | Verifies Server certificate revocation status before steaming using HTTPS. | True(enabled); False(Disabled state) | Streaming\VerifyCertificateRevocationList | 0 |
-| SharedContentStoreMode | SHAREDCONTENTSTOREMODE | Specifies that streamed package contents will be not be saved to the local hard disk. | True(enabled); False(Disabled state) | Streaming\SharedContentStoreMode | 0 |
-| Name **Note** This setting cannot be modified using the **set-AppvclientConfiguration** cmdLet. You must use the **Set-AppvPublishingServer** cmdlet. | PUBLISHINGSERVERNAME | Displays the name of publishing server. | String | Publishing\Servers\{serverId}\FriendlyName | Policy value not written (same as Not Configured) |
-| URL **Note** This setting cannot be modified using the **set-AppvclientConfiguration** cmdLet. You must use the **Set-AppvPublishingServer** cmdlet. | PUBLISHINGSERVERURL | Displays the URL of publishing server. | String | Publishing\Servers\{serverId}\URL | Policy value not written (same as Not Configured) |
-| GlobalRefreshEnabled **Note** This setting cannot be modified using the **set-AppvclientConfiguration** cmdLet. You must use the **Set-AppvPublishingServer** cmdlet. | GLOBALREFRESHENABLED | Enables global publishing refresh (Boolean) | True(enabled); False(Disabled state) | Publishing\Servers\{serverId}\GlobalEnabled | False |
-| GlobalRefreshOnLogon **Note** This setting cannot be modified using the **set-AppvclientConfiguration** cmdLet. You must use the **Set-AppvPublishingServer** cmdlet. | GLOBALREFRESHONLOGON | Triggers a global publishing refresh on logon. ( Boolean) | True(enabled); False(Disabled state) | Publishing\Servers\{serverId}\GlobalLogonRefresh | False |
-| GlobalRefreshInterval **Note** This setting cannot be modified using the **set-AppvclientConfiguration** cmdLet. You must use the **Set-AppvPublishingServer** cmdlet. | GLOBALREFRESHINTERVAL | Specifies the publishing refresh interval using the GlobalRefreshIntervalUnit. To disable package refresh, select 0. | Integer (0-744) | Publishing\Servers\{serverId}\GlobalPeriodicRefreshInterval | 0 |
-| GlobalRefreshIntervalUnit **Note** This setting cannot be modified using the **set-AppvclientConfiguration** cmdLet. You must use the **Set-AppvPublishingServer** cmdlet. | GLOBALREFRESHINTERVALUNI | Specifies the interval unit (Hour 0-23, Day 0-31). | 0 for hour, 1 for day | Publishing\Servers\{serverId}\GlobalPeriodicRefreshIntervalUnit | 1 |
-| UserRefreshEnabled **Note** This setting cannot be modified using the **set-AppvclientConfiguration** cmdLet. You must use the **Set-AppvPublishingServer** cmdlet. | USERREFRESHENABLED | Enables user publishing refresh (Boolean) | True(enabled); False(Disabled state) | Publishing\Servers\{serverId}\UserEnabled | False |
-| UserRefreshOnLogon **Note** This setting cannot be modified using the **set-AppvclientConfiguration** cmdLet. You must use the **Set-AppvPublishingServer** cmdlet. | USERREFRESHONLOGON | Triggers a user publishing refresh onlogon. ( Boolean) Word count (with spaces): 60 | True(enabled); False(Disabled state) | Publishing\Servers\{serverId}\UserLogonRefresh | False |
-| UserRefreshInterval **Note** This setting cannot be modified using the **set-AppvclientConfiguration** cmdLet. You must use the **Set-AppvPublishingServer** cmdlet. | USERREFRESHINTERVAL | Specifies the publishing refresh interval using the UserRefreshIntervalUnit. To disable package refresh, select 0. | Word count (with spaces): 85 Integer (0-744 Hours) | Publishing\Servers\{serverId}\UserPeriodicRefreshInterval | 0 |
-| UserRefreshIntervalUnit **Note** This setting cannot be modified using the **set-AppvclientConfiguration** cmdLet. You must use the **Set-AppvPublishingServer** cmdlet. | USERREFRESHINTERVALUNIT | Specifies the interval unit (Hour 0-23, Day 0-31). | 0 for hour, 1 for day | Publishing\Servers\{serverId}\UserPeriodicRefreshIntervalUnit | 1 |
-| MigrationMode | MIGRATIONMODE | Migration mode allows the App-V client to modify shortcuts and FTA’s for packages created using a previous version of App-V. | True(enabled state); False (disabled state) | Coexistence\MigrationMode | |
-| CEIPOPTIN | CEIPOPTIN | Allows the computer running the App-V 5.1 Client to collect and return certain usage information to help allow us to further improve the application. | 0 for disabled; 1 for enabled | SOFTWARE/Microsoft/AppV/CEIP/CEIPEnable | 0 |
-| EnablePackageScripts | ENABLEPACKAGESCRIPTS | Enables scripts defined in the package manifest of configuration files that should run. | True(enabled); False(Disabled state) | \Scripting\EnablePackageScripts | |
-| RoamingFileExclusions | ROAMINGFILEEXCLUSIONS | Specifies the file paths relative to %userprofile% that do not roam with a user's profile. Example usage: /ROAMINGFILEEXCLUSIONS='desktop;my pictures' | | | |
-| RoamingRegistryExclusions | ROAMINGREGISTRYEXCLUSIONS | Specifies the registry paths that do not roam with a user profile. Example usage: /ROAMINGREGISTRYEXCLUSIONS=software\\classes;software\\clients | String | Integration\RoamingRegistryExclusions | Policy value not written (same as Not Configured) |
-| IntegrationRootUser | Not available. | Specifies the location to create symbolic links associated with the current version of a per-user published package. all virtual application extensions, for example shortcuts and file type associations, will point to this path. If you do not specify a path, symbolic links will not be used when you publish the package. For example: %localappdata%\Microsoft\AppV\Client\Integration.| String | Integration\IntegrationRootUser | Policy value not written (same as Not Configured) |
-|IntegrationRootGlobal | Not available.| Specifies the location to create symbolic links associated with the current version of a globally published package. all virtual application extensions, for example shortcuts and file type associations, will point to this path. If you do not specify a path, symbolic links will not be used when you publish the package. For example: %allusersprofile%\Microsoft\AppV\Client\Integration | String | Integration\IntegrationRootGlobal | Policy value not written (same as Not Configured) |
-| VirtualizableExtensions | Not available. | A comma -delineated list of file name extensions that can be used to determine if a locally installed application can be run in the virtual environment. When shortcuts, FTAs, and other extension points are created during publishing, App-V will compare the file name extension to the list if the application that is associated with the extension point is locally installed. If the extension is located, the **RunVirtual** command line parameter will be added, and the application will run virtually. For more information about the **RunVirtual** parameter, see [Running a Locally Installed Application Inside a Virtual Environment with Virtualized Applications](running-a-locally-installed-application-inside-a-virtual-environment-with-virtualized-applications51.md). | String | Integration\VirtualizableExtensions | Policy value not written |
-| ReportingEnabled | Not available. | Enables the client to return information to a reporting server. | True (enabled); False (Disabled state) | Reporting\EnableReporting | False |
-| ReportingServerURL | Not available. | Specifies the location on the reporting server where client information is saved. | String | Reporting\ReportingServer | Policy value not written (same as Not Configured) |
-| ReportingDataCacheLimit | Not available. | Specifies the maximum size in megabytes (MB) of the XML cache for storing reporting information. The size applies to the cache in memory. When the limit is reached, the log file will roll over. Set between 0 and 1024. | Integer [0-1024] | Reporting\DataCacheLimit | Policy value not written (same as Not Configured) |
-| ReportingDataBlockSize| Not available. | Specifies the maximum size in bytes to transmit to the server for reporting upload requests. This can help avoid permanent transmission failures when the log has reached a significant size. Set between 1024 and unlimited. | Integer [1024 - Unlimited] | Reporting\DataBlockSize | Policy value not written (same as Not Configured) |
-| ReportingStartTime | Not available. | Specifies the time to initiate the client to send data to the reporting server. You must specify a valid integer between 0-23 corresponding to the hour of the day. By default the **ReportingStartTime** will start on the current day at 10 P.M.or 22. **Note** You should configure this setting to a time when computers running the App-V 5.1 client are least likely to be offline. | Integer (0 – 23) | Reporting\ StartTime | Policy value not written (same as Not Configured) |
-| ReportingInterval | Not available. | Specifies the retry interval that the client will use to resend data to the reporting server. | Integer | Reporting\RetryInterval | Policy value not written (same as Not Configured) |
-| ReportingRandomDelay | Not available. | Specifies the maximum delay (in minutes) for data to be sent to the reporting server. When the scheduled task is started, the client generates a random delay between 0 and **ReportingRandomDelay** and will wait the specified duration before sending data. This can help to prevent collisions on the server. | Integer [0 - ReportingRandomDelay] | Reporting\RandomDelay | Policy value not written (same as Not Configured) |
-| EnableDynamicVirtualization **Important** This setting is available only with App-V 5.0 SP2 or later. | Not available. | Enables supported Shell Extensions, Browser Helper Objects, and Active X controls to be virtualized and run with virtual applications. | 1 (Enabled), 0 (Disabled) | HKEY_LOCAL_MACHINE\Software\Microsoft\AppV\Client\Virtualization | |
-| EnablePublishingRefreshUI **Important** This setting is available only with App-V 5.0 SP2. | Not available. | Enables the publishing refresh progress bar for the computer running the App-V 5.1 Client. | 1 (Enabled), 0 (Disabled) | HKEY_LOCAL_MACHINE\Software\Microsoft\AppV\Client\Publishing | |
-| HideUI **Important** This setting is available only with App-V 5.0 SP2.| Not available. | Hides the publishing refresh progress bar. | 1 (Enabled), 0 (Disabled) | | |
-| ProcessesUsingVirtualComponents | Not available. | Specifies a list of process paths (that may contain wildcards), which are candidates for using dynamic virtualization (supported shell extensions, browser helper objects, and ActiveX controls). Only processes whose full path matches one of these items can use dynamic virtualization. | String | Virtualization\ProcessesUsingVirtualComponents | Empty string. |
-
-
-
-
-
-
-## Related topics
-
-
-[Deploying the App-V 5.1 Sequencer and Client](deploying-the-app-v-51-sequencer-and-client.md)
-
-[How to Modify App-V 5.1 Client Configuration Using the ADMX Template and Group Policy](how-to-modify-app-v-51-client-configuration-using-the-admx-template-and-group-policy.md)
-
-[How to Deploy the App-V Client](how-to-deploy-the-app-v-client-51gb18030.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v5/about-the-connection-group-file.md b/mdop/appv-v5/about-the-connection-group-file.md
deleted file mode 100644
index 49785fcb96..0000000000
--- a/mdop/appv-v5/about-the-connection-group-file.md
+++ /dev/null
@@ -1,338 +0,0 @@
----
-title: About the Connection Group File
-description: About the Connection Group File
-author: dansimp
-ms.assetid: bfeb6013-a7ca-4e36-9fe3-229702e83f0d
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# About the Connection Group File
-
-
-**In this topic:**
-
-- [Connection group file purpose and location](#bkmk-cg-purpose-loc)
-
-- [Structure of the connection group XML file](#bkmk-define-cg-5-0sp3)
-
-- [Configuring the priority of packages in a connection group](#bkmk-config-pkg-priority-incg)
-
-- [Supported virtual application connection configurations](#bkmk-va-conn-configs)
-
-## Connection group file purpose and location
-
-
-
-
-
-
-
-
-
-
Connection group purpose
-
A connection group is an App-V feature that enables you to group packages together to create a virtual environment in which the applications in those packages can interact with each other.
-
Example: You want to use plug-ins with Microsoft Office. You can create a package that contains the plug-ins, and create another package that contains Office, and then add both packages to a connection group to enable Office to use those plug-ins.
-
-
-
How the connection group file works
-
When you apply an Application Virtualization 5.0 connection group file, the packages that are enumerated in the file will be combined at runtime into a single virtual environment. Use the Microsoft Application Virtualization (App-V) 5.0 connection group file to configure existing Application Virtualization 5.0 connection groups.
-
-
-
-## Structure of the connection group XML file
-
-
-**In this section:**
-
-- [Parameters that define the connection group](#bkmk-params-define-cg)
-
-- [Parameters that define the packages in the connection group](#bkmk-params-define-pkgs-incg)
-
-- [App-V 5.0 SP3 example connection group XML file](#bkmk-50sp3-exp-cg-xml)
-
-- [App-V 5.0 through App-V 5.0 SP2 example connection group XML file](#bkmk-50thru50sp2-exp-cg-xm)
-
-### Parameters that define the connection group
-
-The following table describes the parameters in the XML file that define the connection group itself, not the packages.
-
-
-
-
-
-
-
-
-
Field
-
Description
-
-
-
-
-
Schema name
-
Name of the schema.
-
Applicable starting in App-V 5.0 SP3: If you want to use the new “optional packages” and “use any version” features that are described in this table, you must specify the following schema in the XML file:
Unique GUID identifier for this connection group. The connection group state is associated with this identifier. Specify this identifier only when you create the connection group.
-
You can create a new GUID by typing: [Guid]::NewGuid().
-
-
-
VersionId
-
Version GUID identifier for this version of the connection group.
-
When you update a connection group (for example, by adding or updating a new package), you must update the version GUID to reflect the new version.
-
-
-
DisplayName
-
Display name of the connection group.
-
-
-
Priority
-
Optional priority field for the connection group.
-
“0” - indicates the highest priority.
-
If a priority is required, but has not been configured, the package will fail because the correct connection group to use cannot be determined.
-
-
-
-
-
-
-### Parameters that define the packages in the connection group
-
-In the <Packages> section of the connection group XML file, you list the member packages in the connection group by specifying each package’s unique package identifier and version identifier, as described in the following table. The first package in the list has the highest precedence.
-
-
-
-
-
-
-
-
-
Field
-
Description
-
-
-
-
-
PackageId
-
Unique GUID identifier for this package. This GUID doesn’t change when newer versions of the package are published.
-
-
-
VersionId
-
Unique GUID identifier for the version of the package.
-
Applicable starting in App-V 5.0 SP3: If you specify “*” for the package version, the GUID of the latest available package version is dynamically inserted.
-
-
-
IsOptional
-
Applicable starting in App-V 5.0 SP3: Parameter that enables you to make a package optional within the connection group. Valid entries are:
-
-
“true” – package is optional in the connection group
-
“false” – package is required in the connection group
-
-
-
-### App-V 5.0 SP3 example connection group XML file
-
-The following example connection group XML file shows examples of the fields in the previous tables and highlights the items that are new for App-V 5.0 SP3.
-
-```XML
-
-
-
-
-
-
-
-```
-
-### App-V 5.0 through App-V 5.0 SP2 example connection group XML file
-
-The following example connection group XML file applies to App-V 5.0 through App-V 5.0 SP2. It shows examples of the fields in the previous table, but it excludes the changes described above for App-V 5.0 SP3.
-
-```XML
-
-
-
-
-
-
-Configuring the priority of packages in a connection group
-
-
-Package precedence is configured using the package list order. The first package in the document has the highest precedence. Subsequent packages in the list have descending priority.
-
-Package precedence is the resolution for otherwise inevitable resource collisions during virtual environment initialization. For example, if two packages that are opening in the same virtual environment define the same registry DWORD value, the package with the highest precedence determines the value that is set.
-
-You can use the connection group file to configure each connection group by using the following methods:
-
-- Specify runtime priorities for connection groups.
-
- **Note**
- Priority is required only if the package is associated with more than one connection group.
-
-
-
-- Specify package precedence within the connection group.
-
-The priority field is required when a running virtual application initiates from a native application request, for example, Microsoft Windows Explorer. The App-V client uses the priority to determine which connection group virtual environment the application should run in. This situation occurs if a virtual application is part of multiple connection groups.
-
-If a virtual application is opened using another virtual application the virtual environment of the original virtual application will be used. The priority field is not used in this case.
-
-**Example:**
-
-The virtual application Microsoft Outlook is running in virtual environment **XYZ**. When you open an attached Microsoft Word document, a virtualized version Microsoft Word opens in the virtual environment **XYZ**, regardless of the virtualized Microsoft Word’s associated connection groups or runtime priorities.
-
-## Supported virtual application connection configurations
-
-
-
-
-
-
-
-
-
-
Configuration
-
Example scenario
-
-
-
-
-
An. exe file and plug-in (.dll)
-
-
You want to distribute Microsoft Office to all users, but distribute a Microsoft Excel plug-in to only a subset of users.
-
Enable the connection group for the appropriate users.
-
Update each package individually as required.
-
-
-
-
An. exe file and a middleware application
-
-
You have an application requires a middleware application, or several applications that all depend on the same middleware runtime version.
-
All computers that require one or more of the applications receive the connection groups with the application and middleware application runtime.
-
You can optionally combine multiple middleware applications into a single connection group.
-
-
-
-
-
-
-
-
Example
-
Example description
-
-
-
-
-
Virtual application connection group for the financial division
-
-
Middleware application 1
-
Middleware application 2
-
Middleware application 3
-
Middleware application runtime
-
-
-
-
Virtual application connection group for HR division
-
-
Middleware application 5
-
Middleware application 6
-
Middleware application runtime
-
-
-
-
-
-
-
-
-
An. exe file and an .exe file
-
You have an application that relies on another application, and you want to keep the packages separate for operational efficiencies, licensing restrictions, or rollout timelines.
-
Example:
-
If you are deploying Microsoft Lync 2010, you can use three packages:
-
-
Microsoft Office 2010
-
Microsoft Communicator 2007
-
Microsoft Lync 2010
-
-
You can manage the deployment using the following connection groups:
-
-
Microsoft Office 2010 and Microsoft Communicator 2007
-
Microsoft Office 2010 and Microsoft Lync 2010
-
-
When the deployment has completed, you can either create a single new Microsoft Office 2010 + Microsoft Lync 2010 package, or keep and maintain them as separate packages and deploy them by using a connection group.
-
-
-
-
-
-
-
-
-
-
-
-## Related topics
-
-
-[Managing Connection Groups](managing-connection-groups.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v5/about-the-connection-group-file51.md b/mdop/appv-v5/about-the-connection-group-file51.md
deleted file mode 100644
index c135acab7f..0000000000
--- a/mdop/appv-v5/about-the-connection-group-file51.md
+++ /dev/null
@@ -1,338 +0,0 @@
----
-title: About the Connection Group File
-description: About the Connection Group File
-author: dansimp
-ms.assetid: 1f4df515-f5f6-4b58-91a8-c71598cb3ea4
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# About the Connection Group File
-
-
-**In this topic:**
-
-- [Connection group file purpose and location](#bkmk-cg-purpose-loc)
-
-- [Structure of the connection group XML file](#bkmk-define-cg-5-0sp3)
-
-- [Configuring the priority of packages in a connection group](#bkmk-config-pkg-priority-incg)
-
-- [Supported virtual application connection configurations](#bkmk-va-conn-configs)
-
-## Connection group file purpose and location
-
-
-
-
-
-
-
-
-
-
Connection group purpose
-
A connection group is an App-V feature that enables you to group packages together to create a virtual environment in which the applications in those packages can interact with each other.
-
Example: You want to use plug-ins with Microsoft Office. You can create a package that contains the plug-ins, and create another package that contains Office, and then add both packages to a connection group to enable Office to use those plug-ins.
-
-
-
How the connection group file works
-
When you apply an App-V 5.1 connection group file, the packages that are enumerated in the file will be combined at runtime into a single virtual environment. Use the Microsoft Application Virtualization (App-V) 5.1 connection group file to configure existing App-V 5.1 connection groups.
-
-
-
-## Structure of the connection group XML file
-
-
-**In this section:**
-
-- [Parameters that define the connection group](#bkmk-params-define-cg)
-
-- [Parameters that define the packages in the connection group](#bkmk-params-define-pkgs-incg)
-
-- [App-V example connection group XML file](#bkmk-50sp3-exp-cg-xml)
-
-- [App-V 5.0 through App-V 5.0 SP2 example connection group XML file](#bkmk-50thru50sp2-exp-cg-xm)
-
-### Parameters that define the connection group
-
-The following table describes the parameters in the XML file that define the connection group itself, not the packages.
-
-
-
-
-
-
-
-
-
Field
-
Description
-
-
-
-
-
Schema name
-
Name of the schema.
-
Applicable starting in App-V 5.0 SP3: If you want to use the new “optional packages” and “use any version” features that are described in this table, you must specify the following schema in the XML file:
Unique GUID identifier for this connection group. The connection group state is associated with this identifier. Specify this identifier only when you create the connection group.
-
You can create a new GUID by typing: [Guid]::NewGuid().
-
-
-
VersionId
-
Version GUID identifier for this version of the connection group.
-
When you update a connection group (for example, by adding or updating a new package), you must update the version GUID to reflect the new version.
-
-
-
DisplayName
-
Display name of the connection group.
-
-
-
Priority
-
Optional priority field for the connection group.
-
“0” - indicates the highest priority.
-
If a priority is required, but has not been configured, the package will fail because the correct connection group to use cannot be determined.
-
-
-
-
-
-
-### Parameters that define the packages in the connection group
-
-In the <Packages> section of the connection group XML file, you list the member packages in the connection group by specifying each package’s unique package identifier and version identifier, as described in the following table. The first package in the list has the highest precedence.
-
-
-
-
-
-
-
-
-
Field
-
Description
-
-
-
-
-
PackageId
-
Unique GUID identifier for this package. This GUID doesn’t change when newer versions of the package are published.
-
-
-
VersionId
-
Unique GUID identifier for the version of the package.
-
Applicable starting in App-V 5.0 SP3: If you specify “*” for the package version, the GUID of the latest available package version is dynamically inserted.
-
-
-
IsOptional
-
Applicable starting in App-V 5.0 SP3: Parameter that enables you to make a package optional within the connection group. Valid entries are:
-
-
“true” – package is optional in the connection group
-
“false” – package is required in the connection group
-
-
-
-### App-V example connection group XML file
-
-The following example connection group XML file shows examples of the fields in the previous tables and highlights the items that are new starting in App-V 5.0 SP3.
-
-```XML
-
-
-
-
-
-
-
-```
-
-### App-V 5.0 through App-V 5.0 SP2 example connection group XML file
-
-The following example connection group XML file applies to App-V 5.0 through App-V 5.0 SP2. It shows examples of the fields in the previous table, but it excludes the changes described above for App-V 5.0 SP3.
-
-```XML
-
-
-
-
-
-
-
-```
-
-## Configuring the priority of packages in a connection group
-
-
-Package precedence is configured using the package list order. The first package in the document has the highest precedence. Subsequent packages in the list have descending priority.
-
-Package precedence is the resolution for otherwise inevitable resource collisions during virtual environment initialization. For example, if two packages that are opening in the same virtual environment define the same registry DWORD value, the package with the highest precedence determines the value that is set.
-
-You can use the connection group file to configure each connection group by using the following methods:
-
-- Specify runtime priorities for connection groups. To edit priority by using the App-V Management Console, click the connection group and then click **Edit**.
-
- **Note**
- Priority is required only if the package is associated with more than one connection group.
-
-
-
-- Specify package precedence within the connection group.
-
-The priority field is required when a running virtual application initiates from a native application request, for example, Microsoft Windows Explorer. The App-V client uses the priority to determine which connection group virtual environment the application should run in. This situation occurs if a virtual application is part of multiple connection groups.
-
-If a virtual application is opened using another virtual application the virtual environment of the original virtual application will be used. The priority field is not used in this case.
-
-**Example:**
-
-The virtual application Microsoft Outlook is running in virtual environment **XYZ**. When you open an attached Microsoft Word document, a virtualized version Microsoft Word opens in the virtual environment **XYZ**, regardless of the virtualized Microsoft Word’s associated connection groups or runtime priorities.
-
-## Supported virtual application connection configurations
-
-
-
-
-
-
-
-
-
-
Configuration
-
Example scenario
-
-
-
-
-
An. exe file and plug-in (.dll)
-
-
You want to distribute Microsoft Office to all users, but distribute a Microsoft Excel plug-in to only a subset of users.
-
Enable the connection group for the appropriate users.
-
Update each package individually as required.
-
-
-
-
An. exe file and a middleware application
-
-
You have an application requires a middleware application, or several applications that all depend on the same middleware runtime version.
-
All computers that require one or more of the applications receive the connection groups with the application and middleware application runtime.
-
You can optionally combine multiple middleware applications into a single connection group.
-
-
-
-
-
-
-
-
Example
-
Example description
-
-
-
-
-
Virtual application connection group for the financial division
-
-
Middleware application 1
-
Middleware application 2
-
Middleware application 3
-
Middleware application runtime
-
-
-
-
Virtual application connection group for HR division
-
-
Middleware application 5
-
Middleware application 6
-
Middleware application runtime
-
-
-
-
-
-
-
-
-
An. exe file and an .exe file
-
You have an application that relies on another application, and you want to keep the packages separate for operational efficiencies, licensing restrictions, or rollout timelines.
-
Example:
-
If you are deploying Microsoft Lync 2010, you can use three packages:
-
-
Microsoft Office 2010
-
Microsoft Communicator 2007
-
Microsoft Lync 2010
-
-
You can manage the deployment using the following connection groups:
-
-
Microsoft Office 2010 and Microsoft Communicator 2007
-
Microsoft Office 2010 and Microsoft Lync 2010
-
-
When the deployment has completed, you can either create a single new Microsoft Office 2010 + Microsoft Lync 2010 package, or keep and maintain them as separate packages and deploy them by using a connection group.
-
-
-
-
-
-
-
-
-
-
-
-## Related topics
-
-
-[Managing Connection Groups](managing-connection-groups51.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v5/about-the-connection-group-virtual-environment.md b/mdop/appv-v5/about-the-connection-group-virtual-environment.md
deleted file mode 100644
index 5b7e566fae..0000000000
--- a/mdop/appv-v5/about-the-connection-group-virtual-environment.md
+++ /dev/null
@@ -1,114 +0,0 @@
----
-title: About the Connection Group Virtual Environment
-description: About the Connection Group Virtual Environment
-author: dansimp
-ms.assetid: 535fa640-cbd9-425e-8437-94650a70c264
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# About the Connection Group Virtual Environment
-
-
-**In this topic:**
-
-- [How package priority is determined](#bkmk-pkg-priority-deter)
-
-- [Merging identical package paths into one virtual directory in connection groups](#bkmk-merged-root-ve-exp)
-
-## How package priority is determined
-
-
-The virtual environment and its current state are associated with the connection group, not with the individual packages. If an App-V package is removed from the connection group, the state that existed as part of the connection group will not migrate with the package.
-
-If the same package is a part of two different connection groups, you have to indicate which connection group App-V should use. For example, you might have two packages in a connection group that each define the same registry DWORD value.
-
-The connection group that is used is based on the order in which a package appears inside the **AppConnectionGroup** XML document:
-
-- The first package has the highest precedence.
-
-- The second package has the second highest precedence.
-
-Consider the following example section:
-
-```xml
-
-```
-
-Assume that same DWORD value ABC (HKEY\_LOCAL\_MACHINE\\software\\contoso\\finapp\\region) is defined in the first and third package, such as:
-
-- Package 1 (A8731008-4523-4713-83A4-CD1363907160): HKEY\_LOCAL\_MACHINE\\software\\contoso\\finapp\\region=5
-
-- Package 3 (04220DCA-EE77-42BE-A9F5-96FD8E8593F2): HKEY\_LOCAL\_MACHINE\\software\\contoso\\finapp\\region=10
-
-Since Package 1 appears first, the AppConnectionGroup's virtual environment will have the single DWORD value of 5 (HKEY\_LOCAL\_MACHINE\\software\\contoso\\finapp\\region=5). This means that the virtual applications in Package 1, Package 2, and Package 3 will all see the value 5 when they query for HKEY\_LOCAL\_MACHINE\\software\\contoso\\finapp\\region.
-
-Other virtual environment resources are resolved similarly, but the usual case is that the collisions occur in the registry.
-
-## Merging identical package paths into one virtual directory in connection groups
-
-
-If two or more packages in a connection group contain identical directory paths, the paths are merged into a single virtual directory inside the connection group virtual environment. This merging of paths allows an application in one package to access files that are in a different package.
-
-When you remove a package from a connection group, the applications in that removed package are no longer able to access files in the remaining packages in the connection group.
-
-The order in which App-V looks up a file’s name in the connection group is specified by the order in which the App-V packages are listed in the connection group manifest file.
-
-The following example shows the order and relationship of a file name lookup in a connection group for **Package A** and **Package B**.
-
-
-
-
-
-
-
-
-
Package A
-
Package B
-
-
-
-
-
C:\Windows\System32
-
C:\Windows\System32
-
-
-
C:\AppTest
-
C:\AppTest
-
-
-
-
-
-
-In the example above, when a virtualized application tries to find a specific file, Package A is searched first for a matching file path. If a matching path is not found, Package B is searched, using the following mapping rules:
-
-- If a file named **test.txt** exists in the same virtual folder hierarchy in both application packages, the first matching file is used.
-
-- If a file named **bar.txt** exists in the virtual folder hierarchy of one application package, but not in the other, the first matching file is used.
-
-
-
-
-
-
-## Related topics
-
-
-[Managing Connection Groups](managing-connection-groups.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v5/about-the-connection-group-virtual-environment51.md b/mdop/appv-v5/about-the-connection-group-virtual-environment51.md
deleted file mode 100644
index 3acd54097c..0000000000
--- a/mdop/appv-v5/about-the-connection-group-virtual-environment51.md
+++ /dev/null
@@ -1,114 +0,0 @@
----
-title: About the Connection Group Virtual Environment
-description: About the Connection Group Virtual Environment
-author: dansimp
-ms.assetid: b7bb0e3d-8cd5-45a9-b84e-c9ab4196a18c
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# About the Connection Group Virtual Environment
-
-
-**In this topic:**
-
-- [How package priority is determined](#bkmk-pkg-priority-deter)
-
-- [Merging identical package paths into one virtual directory in connection groups](#bkmk-merged-root-ve-exp)
-
-## How package priority is determined
-
-
-The virtual environment and its current state are associated with the connection group, not with the individual packages. If an App-V package is removed from the connection group, the state that existed as part of the connection group will not migrate with the package.
-
-If the same package is a part of two different connection groups, you have to indicate which connection group App-V should use. For example, you might have two packages in a connection group that each define the same registry DWORD value.
-
-The connection group that is used is based on the order in which a package appears inside the **AppConnectionGroup** XML document:
-
-- The first package has the highest precedence.
-
-- The second package has the second highest precedence.
-
-Consider the following example section:
-
-```xml
-
-```
-
-Assume that same DWORD value ABC (HKEY\_LOCAL\_MACHINE\\software\\contoso\\finapp\\region) is defined in the first and third package, such as:
-
-- Package 1 (A8731008-4523-4713-83A4-CD1363907160): HKEY\_LOCAL\_MACHINE\\software\\contoso\\finapp\\region=5
-
-- Package 3 (04220DCA-EE77-42BE-A9F5-96FD8E8593F2): HKEY\_LOCAL\_MACHINE\\software\\contoso\\finapp\\region=10
-
-Since Package 1 appears first, the AppConnectionGroup's virtual environment will have the single DWORD value of 5 (HKEY\_LOCAL\_MACHINE\\software\\contoso\\finapp\\region=5). This means that the virtual applications in Package 1, Package 2, and Package 3 will all see the value 5 when they query for HKEY\_LOCAL\_MACHINE\\software\\contoso\\finapp\\region.
-
-Other virtual environment resources are resolved similarly, but the usual case is that the collisions occur in the registry.
-
-## Merging identical package paths into one virtual directory in connection groups
-
-
-If two or more packages in a connection group contain identical directory paths, the paths are merged into a single virtual directory inside the connection group virtual environment. This merging of paths allows an application in one package to access files that are in a different package.
-
-When you remove a package from a connection group, the applications in that removed package are no longer able to access files in the remaining packages in the connection group.
-
-The order in which App-V looks up a file’s name in the connection group is specified by the order in which the App-V packages are listed in the connection group manifest file.
-
-The following example shows the order and relationship of a file name lookup in a connection group for **Package A** and **Package B**.
-
-
-
-
-
-
-
-
-
Package A
-
Package B
-
-
-
-
-
C:\Windows\System32
-
C:\Windows\System32
-
-
-
C:\AppTest
-
C:\AppTest
-
-
-
-
-
-
-In the example above, when a virtualized application tries to find a specific file, Package A is searched first for a matching file path. If a matching path is not found, Package B is searched, using the following mapping rules:
-
-- If a file named **test.txt** exists in the same virtual folder hierarchy in both application packages, the first matching file is used.
-
-- If a file named **bar.txt** exists in the virtual folder hierarchy of one application package, but not in the other, the first matching file is used.
-
-
-
-
-
-
-## Related topics
-
-
-[Managing Connection Groups](managing-connection-groups51.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v5/accessibility-for-app-v-50.md b/mdop/appv-v5/accessibility-for-app-v-50.md
deleted file mode 100644
index 4cc6cd8431..0000000000
--- a/mdop/appv-v5/accessibility-for-app-v-50.md
+++ /dev/null
@@ -1,153 +0,0 @@
----
-title: Accessibility for App-V 5.0
-description: Accessibility for App-V 5.0
-author: dansimp
-ms.assetid: 56696523-6332-4bbe-8ddf-32b1dfe38131
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 08/30/2016
----
-
-
-# Accessibility for App-V 5.0
-
-
-Microsoft is committed to making its products and services easier for everyone to use. This section provides information about features and services that make this product and its corresponding documentation more accessible for people with disabilities.
-
-## Access Any Command with a Few Keystrokes
-
-
-**Important**
-The information in this section only applies to the App-V 5.0 sequencer. For specific information about the App-V 5.0 server, see the Keyboard Shortcuts for the App-V 5.0 Management Server section of this document.
-
-
-
-Access keys let you quickly use a command by pressing a few keys. You can get to most commands by using two keystrokes. To use an access key:
-
-1. Press ALT.
-
- The keyboard shortcuts are displayed over each feature that is available in the current view.
-
-2. Press the letter shown in the keyboard shortcut over the feature that you want to use.
-
-**Note**
-To cancel the action that you are taking and hide the keyboard shortcuts, press ALT.
-
-
-
-## Keyboard Shortcuts for the App-V 5.0 Management Server
-
-
-Keyboard Shortcuts for the App-V 5.0 Management Server:
-
-
-
-
-
-
-
-
-
To do this
-
Press
-
-
-
-
-
Rename App-V 5.0 connection groups or the App-V 5.0 publishing server description.
-
F2
-
-
-
Transfer access and configuration information from an existing App-V 5.0 package.
-
CTRL + Shift + A
-
-
-
Transfer default configurations from an existing App-V 5.0 package.
-
CTRL + Shift + C
-
-
-
Refresh the current page of the App-V 5.0 client console.
-
F5
-
-
-
On the Connections Groups page of the client management console, copies as a new version.
-
CTRL + Shift + C
-
-
-
-
-
-
-## Documentation in Alternative Formats
-
-
-If you have difficulty reading or handling printed materials, you can obtain the documentation for many Microsoft products in more accessible formats. You can view an index of accessible product documentation on the Microsoft Accessibility website. In addition, you can obtain additional Microsoft publications from Learning Ally (formerly Recording for the Blind & Dyslexic, Inc.). Learning Ally distributes these documents to registered, eligible members of their distribution service.
-
-For information about the availability of Microsoft product documentation and books from Microsoft Press, contact:
-
-
-
-
-
-
-
-
-
Learning Ally (formerly Recording for the Blind & Dyslexic, Inc.)
-
20 Roszel Road
-
Princeton, NJ 08540
-
-
-
-
Telephone number from within the United States:
-
(800) 221-4792
-
-
-
Telephone number from outside the United States and Canada:
Web addresses can change, so you might be unable to connect to the website or sites mentioned here.
-
-
-
-
-
-
-## Customer Service for People with Hearing Impairments
-
-
-If you are deaf or hard-of-hearing, complete access to Microsoft product and customer services is available through a text telephone (TTY/TDD) service:
-
-- For customer service, contact Microsoft Sales Information Center at (800) 892-5234 between 6:30 AM and 5:30 PM Pacific Time, Monday through Friday, excluding holidays.
-
-- For technical assistance in the United States, contact Microsoft Product Support Services at (800) 892-5234 between 6:00 AM and 6:00 PM Pacific Time, Monday through Friday, excluding holidays. In Canada, dial (905) 568-9641 between 8:00 AM and 8:00 PM Eastern Time, Monday through Friday, excluding holidays.
-
-Microsoft Support Services are subject to the prices, terms, and conditions in place at the time the service is used.
-
-## For More Information
-
-
-For more information about how accessible technology for computers helps to improve the lives of people with disabilities, see the [Microsoft Accessibility website](https://go.microsoft.com/fwlink/?linkid=8431).
-
-## Related topics
-
-
-[Getting Started with App-V 5.0](getting-started-with-app-v-50--rtm.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v5/accessibility-for-app-v-51.md b/mdop/appv-v5/accessibility-for-app-v-51.md
deleted file mode 100644
index 30d29b8cd1..0000000000
--- a/mdop/appv-v5/accessibility-for-app-v-51.md
+++ /dev/null
@@ -1,174 +0,0 @@
----
-title: Accessibility for App-V 5.1
-description: Accessibility for App-V 5.1
-author: dansimp
-ms.assetid: ef3f7742-f2e9-4748-ad60-74e0961b1bd9
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 08/30/2016
----
-
-
-# Accessibility for App-V 5.1
-
-
-Microsoft is committed to making its products and services easier for everyone to use. This section provides information about features and services that make this product and its corresponding documentation more accessible for people with disabilities.
-
-## Keyboard Shortcuts for the App-V 5.1 Management Server
-
-
-Following are the keyboard Shortcuts for the App-V 5.1 Management Server:
-
-
-
-
-
-
-
-
-
To do this
-
Press
-
-
-
-
-
Close a dialog box.
-
Esc
-
-
-
Perform the default action of a dialog box.
-
Enter
-
-
-
Refresh the current page of the App-V 5.1 client console.
-
F5
-
-
-
-
-
-
-## Keyboard Shortcuts for the App-V 5.1 Sequencer
-
-
-Following are the keyboard shortcuts for the Virtual Registry tab in the package editor in the App-V 5.1 Sequencer:
-
-
-
-
-
-
-
-
-
To do this
-
Press
-
-
-
-
-
Open the Find dialog box.
-
CTRL + F
-
-
-
Open the Replace dialog box.
-
CTRL + H
-
-
-
-
-
-
-### Access Any Command with a Few Keystrokes
-
-**Important**
-The information in this section only applies to the App-V 5.1 sequencer. For specific information about the App-V 5.1 server, see the Keyboard Shortcuts for the App-V 5.1 Management Server section of this document.
-
-
-
-Access keys let you quickly use a command by pressing a few keys. You can get to most commands by using two keystrokes. To use an access key:
-
-1. Press ALT.
-
- An underline appears beneath the keyboard shortcut for each feature that is available in the current view.
-
-2. Press the letter underlined in the keyboard shortcut for the feature that you want to use.
-
-**Note**
-To cancel the action that you are taking and hide the keyboard shortcuts, press ALT.
-
-
-
-## Documentation in Alternative Formats
-
-
-If you have difficulty reading or handling printed materials, you can obtain the documentation for many Microsoft products in more accessible formats. You can view an index of accessible product documentation on the Microsoft Accessibility website. In addition, you can obtain additional Microsoft publications from Learning Ally (formerly Recording for the Blind & Dyslexic, Inc.). Learning Ally distributes these documents to registered, eligible members of their distribution service.
-
-For information about the availability of Microsoft product documentation and books from Microsoft Press, contact:
-
-
-
-
-
-
-
-
-
Learning Ally (formerly Recording for the Blind & Dyslexic, Inc.)
-
20 Roszel Road
-
Princeton, NJ 08540
-
-
-
-
Telephone number from within the United States:
-
(800) 221-4792
-
-
-
Telephone number from outside the United States and Canada:
Web addresses can change, so you might be unable to connect to the website or sites mentioned here.
-
-
-
-
-
-
-## Customer Service for People with Hearing Impairments
-
-
-If you are deaf or hard-of-hearing, complete access to Microsoft product and customer services is available through a text telephone (TTY/TDD) service:
-
-- For customer service, contact Microsoft Sales Information Center at (800) 892-5234 between 6:30 AM and 5:30 PM Pacific Time, Monday through Friday, excluding holidays.
-
-- For technical assistance in the United States, contact Microsoft Product Support Services at (800) 892-5234 between 6:00 AM and 6:00 PM Pacific Time, Monday through Friday, excluding holidays. In Canada, dial (905) 568-9641 between 8:00 AM and 8:00 PM Eastern Time, Monday through Friday, excluding holidays.
-
-Microsoft Support Services are subject to the prices, terms, and conditions in place at the time the service is used.
-
-## For More Information
-
-
-For more information about how accessible technology for computers helps to improve the lives of people with disabilities, see the [Microsoft Accessibility website](https://go.microsoft.com/fwlink/?linkid=8431).
-
-## Related topics
-
-
-[Getting Started with App-V 5.1](getting-started-with-app-v-51.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v5/administering-app-v-50-virtual-applications-by-using-the-management-console.md b/mdop/appv-v5/administering-app-v-50-virtual-applications-by-using-the-management-console.md
deleted file mode 100644
index 50214f1054..0000000000
--- a/mdop/appv-v5/administering-app-v-50-virtual-applications-by-using-the-management-console.md
+++ /dev/null
@@ -1,119 +0,0 @@
----
-title: Administering App-V 5.0 Virtual Applications by Using the Management Console
-description: Administering App-V 5.0 Virtual Applications by Using the Management Console
-author: dansimp
-ms.assetid: e9280dbd-782b-493a-b495-daab25247795
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 10/03/2016
----
-
-
-# Administering App-V 5.0 Virtual Applications by Using the Management Console
-
-
-Use the Microsoft Application Virtualization (App-V) 5.0 management server to manage packages, connection groups, and package access in your environment. The server publishes application icons, shortcuts, and file type associations to authorized computers that run the App-V 5.0 client. One or more management servers typically share a common data store for configuration and package information.
-
-The management server uses Active Directory Domain Services (AD DS) groups to manage user authorization and has SQL Server installed to manage the database and data store.
-
-Because the management servers stream applications to end users on demand, these servers are ideally suited for system configurations that have reliable, high-bandwidth LANs. The management server consists of the following components:
-
-- Management Server – Use the management server to manage packages and connection groups.
-
-- Publishing Server – Use the publishing server to deploy packages to computers that run the App-V 5.0 client.
-
-- Management Database - Use the management database to manage the package access and to publish the server’s synchronization with the management server.
-
-## Management Console tasks
-
-
-The most common tasks that you can perform with the App-V 5.0 Management console are:
-
-- [How to Connect to the Management Console](how-to-connect-to-the-management-console-beta.md)
-
-- [How to Add or Upgrade Packages by Using the Management Console](how-to-add-or-upgrade-packages-by-using-the-management-console-beta-gb18030.md)
-
-- [How to Configure Access to Packages by Using the Management Console](how-to-configure-access-to-packages-by-using-the-management-console-50.md)
-
-- [How to Publish a Package by Using the Management Console](how-to-publish-a-package-by-using-the-management-console-50.md)
-
-- [How to Delete a Package in the Management Console](how-to-delete-a-package-in-the-management-console-beta.md)
-
-- [How to Add or Remove an Administrator by Using the Management Console](how-to-add-or-remove-an-administrator-by-using-the-management-console.md)
-
-- [How to Register and Unregister a Publishing Server by Using the Management Console](how-to-register-and-unregister-a-publishing-server-by-using-the-management-console.md)
-
-- [How to Create a Custom Configuration File by Using the App-V 5.0 Management Console](how-to-create-a-custom-configuration-file-by-using-the-app-v-50-management-console.md)
-
-- [How to Transfer Access and Configurations to Another Version of a Package by Using the Management Console](how-to-transfer-access-and-configurations-to-another-version-of-a-package-by-using-the-management-console.md)
-
-- [How to Customize Virtual Applications Extensions for a Specific AD Group by Using the Management Console](how-to-customize-virtual-applications-extensions-for-a-specific-ad-group-by-using-the-management-console.md)
-
-- [Configure Applications and Default Virtual Application Extensions in Management Console](configure-applications-and-default-virtual-application-extensions-in-management-console.md)
-
-The main elements of the App-V 5.0 Management Console are:
-
-
-
-
-
-
-
-
-
Management Console tab
-
Description
-
-
-
-
-
Overview
-
-
-
App-V Sequencer - Select this option to review general information about using the App-V 5.0 sequencer.
-
Application Packages Library – Select this option to open the PACKAGES page of the Management Console. Use this page to review packages that have been added to the server. You can also manage the connection groups, as well as add or upgrade packages.
-
SERVERS – Select this option to open the SERVERS page of the Management Console. Use this page to review the list of servers that have been registered with your App-V 5.0 infrastructure.
-
CLIENTS – Select this option to review general information about App-V 5.0 clients.
-
-
-
-
Packages tab
-
Use the PACKAGES tab to add or upgrade packages. You can also manage connection groups by clicking CONNECTION GROUPS.
-
-
-
Servers tab
-
Use the SERVERS tab to register a new server.
-
-
-
Administrators tab
-
Use the ADMINISTRATORS tab to register, add, or remove administrators in your App-V 5.0 environment.
-
-
-
-
-
-
-
-
-
-
-
-## Other resources for this App-V 5.0 deployment
-
-
-- [Microsoft Application Virtualization 5.0 Administrator's Guide](microsoft-application-virtualization-50-administrators-guide.md)
-
-- [Operations for App-V 5.0](operations-for-app-v-50.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v5/administering-app-v-51-by-using-powershell.md b/mdop/appv-v5/administering-app-v-51-by-using-powershell.md
deleted file mode 100644
index be798c4983..0000000000
--- a/mdop/appv-v5/administering-app-v-51-by-using-powershell.md
+++ /dev/null
@@ -1,143 +0,0 @@
----
-title: Administering App-V 5.1 by Using PowerShell
-description: Administering App-V 5.1 by Using PowerShell
-author: dansimp
-ms.assetid: 9e10ff07-2cd9-4dc1-9e99-582f90c36081
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Administering App-V 5.1 by Using PowerShell
-
-
-Microsoft Application Virtualization (App-V) 5.1 provides Windows PowerShell cmdlets, which can help administrators perform various App-V 5.1 tasks. The following sections provide more information about using PowerShell with App-V 5.1.
-
-## How to administer App-V 5.1 by using PowerShell
-
-
-Use the following PowerShell procedures to perform various App-V 5.1 tasks.
-
-
Describes how to take an array of account names and to convert each of them to the corresponding SID in standard and hexadecimal formats.
-
-
-
-
-
-
-**Important**
-Make sure that any script you execute with your App-V packages matches the execution policy that you have configured for PowerShell.
-
-
-
-## PowerShell Error Handling
-
-
-Use the following table for information about App-V 5.1 PowerShell error handling.
-
-
-
-
-
-
-
-
-
Event
-
Action
-
-
-
-
-
Using the RollbackOnError attribute with embedded scripts
-
When you use the RollbackOnError attribute with embedded scripts, the attribute is ignored for the following events:
-
-
Removing a package
-
Unpublishing a package
-
Terminating a virtual environment
-
Terminating a process
-
-
-
-
Package name contains $
-
If a package name contains the character ( $ ), you must use a single-quote ( ‘ ), for example,
-
Add-AppvClientPackage ‘Contoso$App.appv’
-
-
-
-
-
-
-
-
-
-
-
-## Related topics
-
-
-[Operations for App-V 5.1](operations-for-app-v-51.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v5/administering-app-v-51-virtual-applications-by-using-the-management-console.md b/mdop/appv-v5/administering-app-v-51-virtual-applications-by-using-the-management-console.md
deleted file mode 100644
index 26ff07008e..0000000000
--- a/mdop/appv-v5/administering-app-v-51-virtual-applications-by-using-the-management-console.md
+++ /dev/null
@@ -1,118 +0,0 @@
----
-title: Administering App-V 5.1 Virtual Applications by Using the Management Console
-description: Administering App-V 5.1 Virtual Applications by Using the Management Console
-author: dansimp
-ms.assetid: a4d078aa-ec54-4fa4-9463-bfb3b971d724
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Administering App-V 5.1 Virtual Applications by Using the Management Console
-
-
-Use the Microsoft Application Virtualization (App-V) 5.1 management server to manage packages, connection groups, and package access in your environment. The server publishes application icons, shortcuts, and file type associations to authorized computers that run the App-V 5.1 client. One or more management servers typically share a common data store for configuration and package information.
-
-The management server uses Active Directory Domain Services (AD DS) groups to manage user authorization and has SQL Server installed to manage the database and data store.
-
-Because the management servers stream applications to end users on demand, these servers are ideally suited for system configurations that have reliable, high-bandwidth LANs. The management server consists of the following components:
-
-- Management Server – Use the management server to manage packages and connection groups.
-
-- Publishing Server – Use the publishing server to deploy packages to computers that run the App-V 5.1 client.
-
-- Management Database - Use the management database to manage the package access and to publish the server’s synchronization with the management server.
-
-## Management Console tasks
-
-
-The most common tasks that you can perform with the App-V 5.1 Management console are:
-
-- [How to Connect to the Management Console](how-to-connect-to-the-management-console-51.md)
-
-- [How to Add or Upgrade Packages by Using the Management Console](how-to-add-or-upgrade-packages-by-using-the-management-console-51-gb18030.md)
-
-- [How to Configure Access to Packages by Using the Management Console](how-to-configure-access-to-packages-by-using-the-management-console-51.md)
-
-- [How to Publish a Package by Using the Management Console](how-to-publish-a-package-by-using-the-management-console-51.md)
-
-- [How to Delete a Package in the Management Console](how-to-delete-a-package-in-the-management-console-51.md)
-
-- [How to Add or Remove an Administrator by Using the Management Console](how-to-add-or-remove-an-administrator-by-using-the-management-console51.md)
-
-- [How to Register and Unregister a Publishing Server by Using the Management Console](how-to-register-and-unregister-a-publishing-server-by-using-the-management-console51.md)
-
-- [How to Create a Custom Configuration File by Using the App-V 5.1 Management Console](how-to-create-a-custom-configuration-file-by-using-the-app-v-51-management-console.md)
-
-- [How to Transfer Access and Configurations to Another Version of a Package by Using the Management Console](how-to-transfer-access-and-configurations-to-another-version-of-a-package-by-using-the-management-console51.md)
-
-- [How to Customize Virtual Applications Extensions for a Specific AD Group by Using the Management Console](how-to-customize-virtual-applications-extensions-for-a-specific-ad-group-by-using-the-management-console51.md)
-
-- [How to View and Configure Applications and Default Virtual Application Extensions by Using the Management Console](how-to-view-and-configure-applications-and-default-virtual-application-extensions-by-using-the-management-console-beta.md)
-
-The main elements of the App-V 5.1 Management Console are:
-
-
-
-
-
-
-
-
-
Management Console tab
-
Description
-
-
-
-
-
Packages tab
-
Use the PACKAGES tab to add or upgrade packages.
-
-
-
Connection Groups tab
-
Use the CONNECTION GROUPS tab to manage connection groups.
-
-
-
Servers tab
-
Use the SERVERS tab to register a new server.
-
-
-
Administrators tab
-
Use the ADMINISTRATORS tab to register, add, or remove administrators in your App-V 5.1 environment.
-
-
-
-
-
-
-**Important**
-JavaScript must be enabled on the browser that opens the Web Management Console.
-
-
-
-
-
-
-
-
-## Other resources for this App-V 5.1 deployment
-
-
-- [Microsoft Application Virtualization 5.1 Administrator's Guide](microsoft-application-virtualization-51-administrators-guide.md)
-
-- [Operations for App-V 5.1](operations-for-app-v-51.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v5/administering-app-v-by-using-powershell.md b/mdop/appv-v5/administering-app-v-by-using-powershell.md
deleted file mode 100644
index 8d6b8071a3..0000000000
--- a/mdop/appv-v5/administering-app-v-by-using-powershell.md
+++ /dev/null
@@ -1,138 +0,0 @@
----
-title: Administering App-V by Using PowerShell
-description: Administering App-V by Using PowerShell
-author: dansimp
-ms.assetid: 1ff4686a-1e19-4eff-b648-ada091281094
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Administering App-V by Using PowerShell
-
-
-Microsoft Application Virtualization (App-V) 5.0 provides Windows PowerShell cmdlets, which can help administrators perform various App-V 5.0 tasks. The following sections provide more information about using PowerShell with App-V 5.0.
-
-## How to administer App-V 5.0 by using PowerShell
-
-
-Use the following PowerShell procedures to perform various App-V 5.0 tasks.
-
-
Describes how to take an array of account names and to convert each of them to the corresponding SID in standard and hexadecimal formats.
-
-
-
-
-
-
-## PowerShell Error Handling
-
-
-Use the following table for information about App-V 5.0 PowerShell error handling.
-
-
-
-
-
-
-
-
-
Event
-
Action
-
-
-
-
-
Using the RollbackOnError attribute with embedded scripts
-
When you use the RollbackOnError attribute with embedded scripts, the attribute is ignored for the following events:
-
-
Removing a package
-
Unpublishing a package
-
Terminating a virtual environment
-
Terminating a process
-
-
-
-
Package name contains $
-
If a package name contains the character ( $ ), you must use a single-quote ( ‘ ), for example,
-
Add-AppvClientPackage ‘Contoso$App.appv’
-
-
-
-
-
-
-
-
-
-
-
-## Related topics
-
-
-[Operations for App-V 5.0](operations-for-app-v-50.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v5/app-v-50-capacity-planning.md b/mdop/appv-v5/app-v-50-capacity-planning.md
deleted file mode 100644
index 3fe507eacf..0000000000
--- a/mdop/appv-v5/app-v-50-capacity-planning.md
+++ /dev/null
@@ -1,963 +0,0 @@
----
-title: App-V 5.0 Capacity Planning
-description: App-V 5.0 Capacity Planning
-author: dansimp
-ms.assetid: 56f48b00-cd91-4280-9481-5372a0e2e792
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# App-V 5.0 Capacity Planning
-
-
-The following recommendations can be used as a baseline to help determine capacity planning information that is appropriate to your organization’s App-V 5.0 infrastructure.
-
-**Important**
-Use the information in this section only as a general guide for planning your App-V 5.0 deployment. Your system capacity requirements will depend on the specific details of your hardware and application environment. Additionally, the performance numbers displayed in this document are examples and your results may vary.
-
-
-
-## Determine the Project Scope
-
-
-Before you design the App-V 5.0 infrastructure, you must determine the project’s scope. The scope consists of determining which applications will be available virtually and to also identify the target users, and their locations. This information will help determine what type of App-V 5.0 infrastructure should be implemented. Decisions about the scope of the project must be based on the specific needs of your organization.
-
-
-
-
-
-
-
-
-
Task
-
More Information
-
-
-
-
-
Determine Application Scope
-
Depending on the applications to be virtualized, the App-V 5.0 infrastructure can be set up in different ways. The first task is to define what applications you want to virtualize.
-
-
-
Determine Location Scope
-
Location scope refers to the physical locations (for example, enterprise-wide or a specific geographic location) where you plan to run the virtualized applications. It can also refer to the user population (for example, a single department) who will run the virtual applications. You should obtain a network map that includes the connection paths as well as available bandwidth to each location and the number of users using virtualized applications and the WAN link speed.
-
-
-
-
-
-
-## Determine Which App-V 5.0 Infrastructure is Required
-
-
-**Important**
-Both of the following models require the App-V 5.0 client to be installed on the computer where you plan to run virtual applications.
-
-You can also manage your App-V 5.0 environment using an Electronic Software Distribution (ESD) solution such as Microsoft Systems Center Configuration Manager. For more information see [Deploying App-V 5.0 Packages by Using Electronic Software Distribution (ESD)](deploying-app-v-50-packages-by-using-electronic-software-distribution--esd-.md).
-
-
-
-- **Standalone Model** - The standalone model allows virtual applications to be Windows Installer-enabled for distribution without streaming. App-V 5.0 in Standalone Mode consists of the sequencer and the client; no additional components are required. Applications are prepared for virtualization using a process called sequencing. For more information see, [Planning for the App-V 5.0 Sequencer and Client Deployment](planning-for-the-app-v-50-sequencer-and-client-deployment.md). The stand-alone model is recommended for the following scenarios:
-
- - With disconnected remote users who cannot connect to the App-V 5.0 infrastructure.
-
- - When you are running a software management system, such as Configuration Manager 2012.
-
- - When network bandwidth limitations inhibit electronic software distribution.
-
-- **Full Infrastructure Model** - The full infrastructure model provides for software distribution, management, and reporting capabilities; it also includes the streaming of applications across the network. The App-V 5.0 Full Infrastructure Model consists of one or more App-V 5.0 management servers. The Management Server can be used to publish applications to all clients. The publishing process places the virtual application icons and shortcuts on the target computer. It can also stream applications to local users. For more information about installing the management server see, [Planning for the App-V 5.0 Server Deployment](planning-for-the-app-v-50-server-deployment.md). The full infrastructure model is recommended for the following scenarios:
-
- **Important**
- The App-V 5.0 full infrastructure model requires Microsoft SQL Server to store configuration data. For more information see [App-V 5.0 Supported Configurations](app-v-50-supported-configurations.md).
-
-
-
- - When you want to use the Management Server to publish the application to target computers.
-
- - For rapid provisioning of applications to target computers.
-
- - When you want to use App-V 5.0 reporting.
-
-## End-to-end Server Sizing Guidance
-
-
-The following section provides information about end-to-end App-V 5.0 sizing and planning. For more specific information, refer to the subsequent sections.
-
-**Note**
-Round trip response time on the client is the time taken by the computer running the App-V 5.0 client to receive a successful notification from the publishing server. Round trip response time on the publishing server is the time taken by the computer running the publishing server to receive a successful package metadata update from the management server.
-
-
-
-- 20,000 clients can target a single publishing server to obtain the package refreshes in an acceptable round trip time. (<3 seconds)
-
-- A single management server can support up to 50 publishing servers for package metadata refreshes in an acceptable round trip time. (<5 seconds)
-
-## App-V 5.0 Management Server Capacity Planning Recommendations
-
-
-The App-V 5.0 publishing servers require the management server for package refresh requests and package refresh responses. The management server then sends the information to the management database to retrieve information. For more information about App-V 5.0 management server supported configurations see [App-V 5.0 Supported Configurations](app-v-50-supported-configurations.md).
-
-**Note**
-The default refresh time on the App-V 5.0 publishing server is ten minutes.
-
-
-
-When multiple simultaneous publishing servers contact a single management server for package metadata refreshes, the following three factors influence the round trip response time on the publishing server:
-
-1. Number of publishing servers making simultaneous requests.
-
-2. Number of connection groups configured on the management server.
-
-3. Number of access groups configured on the management server.
-
-The following table displays more information about each factor that impacts round trip time.
-
-**Note**
-Round trip response time is the time taken by the computer running the App-V 5.0 publishing server to receive a successful package metadata update from the management server.
-
-
-
-
-
-
-
-
-
-
-
Factors impacting round trip response time
-
More Information
-
-
-
-
-
The number of publishing servers simultaneously requesting package metadata refreshes.
-
-
-
A single management server can respond to up to 320 publishing servers requesting publishing metadata simultaneously.
-
Round trip response time for 320 pub servers is ~40 seconds.
-
For <50 publishing servers requesting metadata simultaneously, the round trip response time is <5 seconds.
-
From 50 to 320 publishing servers, the response time increases linearly (approximately 2x).
-
-
-
-
The number of connection groups configured on the management server.
-
-
-
-
For up to 100 connection groups, there is no significant change in the round trip response time on the publishing server.
-
For 100 - 400 connection groups, there is a minor linear increase in the round trip response time.
-
-
-
-
The number of access groups configured on the management server.
-
-
-
-
For up to 40 access groups, there is a linear (approximately 3x) increase in the round trip response time on the publishing server.
-
-
-
-
-
-
-
-The following table displays sample values for each of the previous factors. In each variation, 120 packages are refreshed from the App-V 5.0management server.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Scenario
-
Variation
-
Number of connection groups
-
Number of access groups
-
Number of publishing servers
-
Network connection type publishing server / management server
-
Round trip response time on the publishing server (in seconds)
-
CPU utilization on management server
-
-
-
-
-
Publishing servers simultaneously contacting management server for publishing metadata.
-
Number of publishing servers
-
-
-
0
-
0
-
0
-
0
-
0
-
0
-
-
-
-
1
-
1
-
1
-
1
-
1
-
1
-
-
-
-
50
-
100
-
200
-
300
-
315
-
320
-
-
-
-
LAN
-
LAN
-
LAN
-
LAN
-
LAN
-
LAN
-
-
-
-
5
-
10
-
19
-
32
-
30
-
37
-
-
-
-
17
-
17
-
17
-
15
-
17
-
15
-
-
-
-
Publishing metadata contains connection groups
-
Number of connection groups
-
-
-
10
-
50
-
100
-
150
-
300
-
400
-
-
-
-
1
-
1
-
1
-
1
-
1
-
1
-
-
-
-
100
-
100
-
100
-
100
-
100
-
100
-
-
-
-
LAN
-
LAN
-
LAN
-
LAN
-
LAN
-
LAN
-
-
-
-
10
-
11
-
11
-
16
-
22
-
25
-
-
-
-
17
-
19
-
22
-
19
-
20
-
20
-
-
-
-
Publishing metadata contains access groups
-
Number of access groups
-
-
-
0
-
0
-
0
-
0
-
-
-
-
1
-
10
-
20
-
40
-
-
-
-
100
-
100
-
100
-
100
-
-
-
-
LAN
-
LAN
-
LAN
-
LAN
-
-
-
-
10
-
43
-
153
-
535
-
-
-
-
17
-
26
-
24
-
24
-
-
-
-
-
-
-
-The CPU utilization of the computer running the management server is around 25% irrespective of the number of publishing servers targeting it. The Microsoft SQL Server database transactions/sec, batch requests/sec and user connections are identical irrespective of the number of publishing servers. For example: Transactions/sec is ~30, batch requests ~200, and user connects ~6.
-
-Using a geographically distributed deployment, where the management server & publishing servers utilize a slow link network between them, the round trip response time on the publishing servers is within acceptable time limits (<5 seconds), even for 100 simultaneous requests on a single management server.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Scenario
-
Variation
-
Number of connection groups
-
Number of access groups
-
Number of publishing servers
-
Network connection type publishing server / management server
-
Round trip response time on the publishing server (in seconds)
-
CPU utilization on management server
-
-
-
-
-
Network connection between the publishing server and management server
-
1.5 Mbps Slow link Network
-
-
-
0
-
0
-
-
-
-
1
-
1
-
-
-
-
50
-
100
-
-
-
-
1.5Mbps Cable DSL
-
1.5Mbps Cable DSL
-
-
-
-
4
-
5
-
-
-
-
1
-
2
-
-
-
-
Network connection between the publishing server and management server
-
LAN / WIFI Network
-
-
-
0
-
0
-
-
-
-
1
-
1
-
-
-
-
100
-
200
-
-
-
-
Wifi
-
Wifi
-
-
-
-
11
-
20
-
-
-
-
15
-
17
-
-
-
-
-
-
-
-Whether the management server and publishing servers are connected over a slow link network, or a high speed network, the management server can handle approximately 15,000 package refresh requests in 30 minutes.
-
-## App-V 5.0 Reporting Server Capacity Planning Recommendations
-
-
-App-V 5.0 clients send reporting data to the reporting server. The reporting server then records the information in the Microsoft SQL Server database and returns a successful notification back to the computer running App-V 5.0 client. For more information about App-V 5.0 Reporting Server supported configurations see [App-V 5.0 Supported Configurations](app-v-50-supported-configurations.md).
-
-**Note**
-Round trip response time is the time taken by the computer running the App-V 5.0 client to send the reporting information to the reporting server and receive a successful notification from the reporting server.
-
-
-
-
-
-
-
-
-
-
-
Scenario
-
Summary
-
-
-
-
-
Multiple App-V 5.0 clients send reporting information to the reporting server simultaneously.
-
-
-
Round trip response time from the reporting server is 2.6 seconds for 500 clients.
-
Round trip response time from the reporting server is 5.65 seconds for 1000 clients.
-
Round trip response time increases linearly depending on number of clients.
-
-
-
-
Requests per second processed by the reporting server.
-
-
-
-
A single reporting server and a single database, can process a maximum of 139 requests per second. The average is 121 requests/second.
-
Using two reporting servers reporting to the same Microsoft SQL Server database, the average requests/second is similar to a single reporting server = ~127, with a max of 278 requests/second.
-
A single reporting server can process 500 concurrent/active connections.
-
A single reporting server can process a maximum 1500 concurrent connections.
-
-
-
-
Reporting Database.
-
-
-
-
Lock contention on the computer running Microsoft SQL Server is the limiting factor for requests/second.
-
Throughput and response time are independent of database size.
-
-
-
-
-
-
-
-**Calculating random delay**:
-
-The random delay specifies the maximum delay (in minutes) for data to be sent to the reporting server. When the scheduled task is started, the client generates a random delay between **0** and **ReportingRandomDelay** and will wait the specified duration before sending data.
-
-Random delay = 4 \* number of clients / average requests per second.
-
-Example: For 500 clients, with 120 requests per second, the Random delay is, 4 \* 500 / 120 = ~17 minutes.
-
-## App-V 5.0 Publishing Server Capacity Planning Recommendations
-
-
-Computers running the App-V 5.0 client connect to the App-V 5.0 publishing server to send a publishing refresh request and to receive a response. Round trip response time is measured on the computer running the App-V 5.0 client. Processor time is measured on the publishing server. For more information about App-V 5.0 Publishing Server supported configurations see [App-V 5.0 Supported Configurations](app-v-50-supported-configurations.md).
-
-**Important**
-The following list displays the main factors to consider when setting up the App-V 5.0 publishing server:
-
-- The number of clients connecting simultaneously to a single publishing server.
-
-- The number of packages in each refresh.
-
-- The available network bandwidth in your environment between the client and the App-V 5.0 publishing server.
-
-
-
-
-
-
-
-
-
-
-
Scenario
-
Summary
-
-
-
-
-
Multiple App-V 5.0 clients connect to a single publishing server simultaneously.
-
-
-
A publishing server running dual core processors can respond to at most 5000 clients requesting a refresh simultaneously.
-
For 5000-10000 clients, the publishing server requires a minimum quad core.
-
For 10000-20000 clients, the publishing server should have dual quad cores for more efficient response times.
-
A publishing server with a quad core can refresh up to 10000 packages within 3 seconds. (Supporting 10000 simultaneous clients)
-
-
-
-
Number of packages in each refresh.
-
-
-
-
Increasing number of packages will increase response time by ~40% (up to 1000 packages).
-
-
-
-
Network between the App-V 5.0 client and the publishing server.
-
-
-
-
Across a slow network (1.5 Mbps bandwidth), there is a 97% increase in response time compared to LAN (up to 1000 users).
-
-
-
-
-
-
-
-**Note**
-The publishing server CPU usage is always high during the time interval when it has to process simultaneous requests (>90% in most cases). The publishing server can handle ~1500 client requests in 1 second.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Scenario
-
Variation
-
Number of App-V 5.0 clients
-
Number of packages
-
Processor configuration on the publishing server
-
Network connection type publishing server / App-V 5.0 client
-
Round trip time on the App-V 5.0 client (in seconds)
-
-
-
-## App-V 5.0 Streaming Capacity Planning Recommendations
-
-
-Computers running the App-V 5.0 client stream the virtual application package from the streaming server. Round trip response time is measured on the computer running the App-V 5.0 client, and is the time taken to stream the entire package.
-
-**Important**
-The following list identifies the main factors to consider when setting up the App-V 5.0 streaming server:
-
-- The number of clients streaming application packages simultaneously from a single streaming server.
-
-- The size of the package being streamed.
-
-- The available network bandwidth in your environment between the client and the streaming server.
-
-
-
-
-
-
-
-
-
-
-
Scenario
-
Summary
-
-
-
-
-
Multiple App-V 5.0 clients stream applications from a single streaming server simultaneously.
-
-
-
If the number of clients simultaneously streaming from the same server increases, there is a linear relationship with the package download/streaming time.
-
-
-
-
Size of the package being streamed.
-
-
-
-
The package size has a significant impact on the streaming/download time only for larger packages with a size ~ 1GB. For package sizes ranging from 3 MB to 100 MB, the streaming time ranges from 20 seconds to 100 seconds, with 100 simultaneous clients.
-
-
-
-
Network between the App-V 5.0 client and the streaming server.
-
-
-
-
Across a slow network (1.5 Mbps bandwidth), there is a 70-80% increase in response time compared to LAN (up to 100 users).
-
-
-
-
-
-
-
-The following table displays sample values for each of the factors in the previous list:
-
-
-
-
-
-
-
-
-
-
-
-
-
Scenario
-
Variation
-
Number of App-V 5.0 clients
-
Size of each package
-
Network connection type streaming server / App-V 5.0 client
-
Round trip time on the App-V 5.0 client (in seconds)
-
-
-
-
-
Multiple App-V 5.0 clients streaming virtual application packages from a streaming server.
-
Number of clients.
-
-
-
100
-
200
-
1000
-
-
100
-
200
-
1000
-
-
-
-
3.5 MB
-
3.5 MB
-
3.5 MB
-
-
5 MB
-
5 MB
-
5 MB
-
-
-
-
LAN
-
LAN
-
LAN
-
-
LAN
-
LAN
-
LAN
-
-
-
-
29
-
39
-
391
-
-
35
-
68
-
461
-
-
-
-
Size of each package being streamed.
-
Size of each package.
-
-
-
100
-
200
-
-
100
-
200
-
-
-
-
21 MB
-
21 MB
-
-
109
-
109
-
-
-
-
LAN
-
LAN
-
-
LAN
-
LAN
-
-
-
33
-
83
-
-
100
-
160
-
-
-
Network connection between client and App-V 5.0 streaming server.
-
1.5 Mbps Slow link network.
-
-
-
100
-
-
100
-
-
-
-
3.5 MB
-
-
5 MB
-
-
-
-
1.5 Mbps Intra-Continental Network
-
-
-
102
-
-
121
-
-
-
-
-
-
-Each App-V 5.0 streaming server should be able to handle a minimum of 200 clients concurrently streaming virtualized applications.
-
-**Note**
-The actual time to it will take to stream is determined primarily by the number of clients streaming simultaneously, number of packages, package size, the server’s network activity, and network conditions.
-
-
-
-For example, an average user can stream a 100 MB package in less than 2 minutes, when 100 simultaneous clients are streaming from the server. However, a package of size 1 GB could take up to 30 minutes. In most real world environments streaming demand is not uniformly distributed, you will need to understand the approximate peak streaming requirements present in your environment in order to properly size the number of required streaming servers.
-
-The number of clients a streaming server can support can be significantly increased and the peak streaming requirements reduced if you pre-cache your applications. You can also increase the number of clients a streaming server can support by using on-demand streaming delivery and stream optimized packages.
-
-## Combining App-V 5.0 Server Roles
-
-
-Discounting scaling and fault-tolerance requirements, the minimum number of servers needed for a location with connectivity to Active Directory is one. This server will host the management server, management server service, and Microsoft SQL Server roles. Server roles, therefore, can be arranged in any desired combination since they do not conflict with one another.
-
-Ignoring scaling requirements, the minimum number of servers necessary to provide a fault-tolerant implementation is four. The management server, and Microsoft SQL Server roles support being placed in fault-tolerant configurations. The management server service can be combined with any of the roles, but remains a single point of failure.
-
-Although there are a number of fault-tolerance strategies and technologies available, not all are applicable to a given service. Additionally, if App-V 5.0 roles are combined, certain fault-tolerance options may no longer apply due to incompatibilities.
-
-
-
-
-
-
-## Related topics
-
-
-[App-V 5.0 Supported Configurations](app-v-50-supported-configurations.md)
-
-[Planning for High Availability with App-V 5.0](planning-for-high-availability-with-app-v-50.md)
-
-[Planning to Deploy App-V](planning-to-deploy-app-v.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v5/app-v-50-deployment-checklist.md b/mdop/appv-v5/app-v-50-deployment-checklist.md
deleted file mode 100644
index 2b84226c10..0000000000
--- a/mdop/appv-v5/app-v-50-deployment-checklist.md
+++ /dev/null
@@ -1,94 +0,0 @@
----
-title: App-V 5.0 Deployment Checklist
-description: App-V 5.0 Deployment Checklist
-author: dansimp
-ms.assetid: d6d93152-82b4-4b02-8b11-ed21d3331f00
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# App-V 5.0 Deployment Checklist
-
-
-This checklist can be used to help you during Microsoft Application Virtualization (App-V) 5.0 deployment.
-
-**Note**
-This checklist outlines the recommended steps and a high-level list of items to consider when deploying App-V 5.0 features. It is recommended that you copy this checklist into a spreadsheet program and customize it for your use.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Task
-
References
-
Notes
-
-
-
-
-
-
Complete the planning phase to prepare the computing environment for App-V 5.0 deployment.
Review the App-V 5.0 supported configurations information to make sure selected client and server computers are supported for App-V 5.0 feature installation.
Run App-V 5.0 Setup to deploy the required App-V 5.0 features for your environment.
-
-Note
Keep track of the names of the servers and associated URL’s created during installation. This information will be used throughout the installation process.
-
-
-
-
-
-
-
-
-## Related topics
-
-
-[Deploying App-V 5.0](deploying-app-v-50.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v5/app-v-50-planning-checklist.md b/mdop/appv-v5/app-v-50-planning-checklist.md
deleted file mode 100644
index 3eeb21f0b8..0000000000
--- a/mdop/appv-v5/app-v-50-planning-checklist.md
+++ /dev/null
@@ -1,101 +0,0 @@
----
-title: App-V 5.0 Planning Checklist
-description: App-V 5.0 Planning Checklist
-author: dansimp
-ms.assetid: 81d3fa62-3c9e-4de7-a9da-cd13112b0862
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# App-V 5.0 Planning Checklist
-
-
-This checklist can be used to help you plan for preparing your computing environment for Microsoft Application Virtualization (App-V) 5.0 deployment.
-
-**Note**
-This checklist outlines the recommended steps and a high-level list of items to consider when planning for an App-V 5.0 deployment. It is recommended that you copy this checklist into a spreadsheet program and customize it for your use.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Task
-
References
-
Notes
-
-
-
-
-
-
Review the getting started information about App-V 5.0 to gain a basic understanding of the product before beginning deployment planning.
-
-
-
-
-
-
-
-
-## Related topics
-
-
-[Planning for App-V 5.0](planning-for-app-v-50-rc.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v5/app-v-50-prerequisites.md b/mdop/appv-v5/app-v-50-prerequisites.md
deleted file mode 100644
index e90a62583c..0000000000
--- a/mdop/appv-v5/app-v-50-prerequisites.md
+++ /dev/null
@@ -1,436 +0,0 @@
----
-title: App-V 5.0 Prerequisites
-description: App-V 5.0 Prerequisites
-author: dansimp
-ms.assetid: 9756b571-c785-4ce6-a95c-d4e134e89429
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 08/30/2016
----
-
-
-# App-V 5.0 Prerequisites
-
-
-Before you begin the Microsoft Application Virtualization (App-V) 5.0 Setup, you should make sure that you have met the prerequisites to install the product. This topic contains information to help you successfully plan for preparing your computing environment before you deploy the App-V 5.0 features.
-
-**Important**
-**The prerequisites in this article apply only to App-V 5.0**. For additional prerequisites that apply to App-V 5.0 Service Packs, see the following web pages:
-
-- [What's new in App-V 5.0 SP1](whats-new-in-app-v-50-sp1.md)
-
-- [About App-V 5.0 SP2](about-app-v-50-sp2.md)
-
-- [App-V 5.0 SP3 Prerequisites](app-v-50-sp3-prerequisites.md)
-
-
-
-The following table lists prerequisite information that pertains to specific operating systems.
-
-
-
-
-
-
-
-
-
Operating systems
-
Prerequisite description
-
-
-
-
-
Computers that are running:
-
-
Windows 8
-
Windows Server 2012
-
-
The following prerequisites are already installed:
-
-
Microsoft .NET Framework 4.5 – you do not need Microsoft .NET Framework 4
Be sure to check for subsequent KBs that have superseded this one, and note that some KBs may require that you uninstall previous updates.
-
-
-
-
-
-
-## Installation prerequisites for App-V 5.0
-
-
-**Note**
-The following prerequisites are already installed for computers that run Windows 8.
-
-
-
-Each of the App-V 5.0 features have specific prerequisites that must be met before the App-V 5.0 features can be successfully installed.
-
-### Prerequisites for the App-V 5.0 client
-
-The following table lists the installation prerequisites for the App-V 5.0 client:
-
-
-
-
-
-### Prerequisites for the App-V 5.0 Remote Desktop Services client
-
-**Note**
-The following prerequisites are already installed for computers that run Windows Server 2012.
-
-
-
-The following table lists the installation prerequisites for the App-V 5.0 Remote Desktop Services client:
-
-
-
-
-
-### Prerequisites for the App-V 5.0 Sequencer
-
-**Note**
-The following prerequisites are already installed for computers that run Windows 8 and Windows Server 2012.
-
-
-
-The following table lists the installation prerequisites for the App-V 5.0 Sequencer. If possible, the computer that runs the Sequencer should have the same hardware and software configurations as the computers that will run the virtual applications.
-
-**Note**
-If the system requirements of a locally installed application exceed the requirements of the Sequencer, you must meet the requirements of that application. Additionally, because the sequencing process is system resource-intensive, we recommend that the computer that runs the Sequencer has plenty of memory, a fast processor, and a fast hard drive. For more information see [App-V 5.0 Supported Configurations](app-v-50-supported-configurations.md).
-
-
-
-
You can download and install either one of the previous KB articles. However, they may have been replaced with a more recent version.
-
-
-
-
-
-
-
-
-
-
-
-### Prerequisites for the App-V 5.0 server
-
-**Note**
-The following prerequisites are already installed for computers that run Windows Server 2012:
-
-- Microsoft .NET Framework 4.5. This eliminates the Microsoft .NET Framework 4 requirement.
-
-- Windows PowerShell 3.0
-
-- Download and install [KB2533623](https://support.microsoft.com/kb/2533623) (https://support.microsoft.com/kb/2533623)
-
- **Important**
- You can still download install the previous KB. However, it may have been replaced with a more recent version.
-
-
-
-
-
-The following table lists the installation prerequisites for the App-V 5.0 server. The account that you use to install the server components must have administrative rights on the computer that you are installing on. This account must also have the ability to query Active Directory Directory Services. Before you install and configure the App-V 5.0 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 the specified ports.
-
-**Note**
-Web Distributed Authoring and Versioning (WebDAV) is automatically disabled for the Management Service.
-
-
-
-The App-V 5.0 server is supported for a standalone deployment, where all the components are deployed on the same server, and a distributed deployment. Depending on the topology that you use to deploy the App-V 5.0 server, the data that you will need for each component will slightly change.
-
-**Important**
-The installation of the App-V 5.0 server on a computer that runs any previous version or component of App-V is not supported. Additionally, the installation of the server components on a computer that runs Server Core or a Domain Controller is also not supported.
-
-
-
-
Windows Web Server with the IIS role enabled and the following features: Common HTTP Features (static content and default document), Application Development (ASP.NET, .NET Extensibility, ISAPI Extensions and ISAPI Filters), Security (Windows Authentication, Request Filtering), Management Tools (IIS Management Console).
The App-V 5.0 server components are dependent but they have varying requirements and installation options that must be deployed. Use the following information to prepare your environment to run the App-V 5.0 management server.
-
-
Installation location - by default this component will be installed to: %PROGRAMFILES%\Microsoft Application Virtualization Server.
-
Location of the App-V 5.0 management database - SQL Server Name, SQL Instance Name, Database Name.
-
Access rights for the App-V 5.0 management console - This is the user or the group that should be granted access to the management console at the end of the deployment. After the deployment, only these users will have access to the management console until additional administrators are added through the management console.
-
-Note
Security groups and single users are not supported. You must specify an AD DS group.
-
-
-
-
-
App-V 5.0 management service website name – specify a name for the website or use the default name.
-
App-V 5.0 management service port binding - this should be a unique port number that is not used by another website on the computer.
-
Support for Microsoft Silverlight– Microsoft Silverlight must be installed before the management console is available. While this is not a requirement for the deployment, the server must be able to support Microsoft Silverlight.
-
-
-
-
Management Database
-
-
-Note
The database is required only when using the App-V 5.0 management server.
The App-V 5.0 server components are dependent but they have varying requirements and installation options that must be deployed. Use the following information to prepare your environment to run the App-V 5.0 management database.
-
-
Installation location - by default this component will be installed to %PROGRAMFILES%\Microsoft Application Virtualization Server.
-
Custom SQL Server instance name (if applicable) – the format should be INSTANCENAME, because the installation assumes that it is on the local machine. If you specify the name with the following format, SVR\INSTANCE will fail.
-
Custom App-V 5.0 database name (if applicable) – you must specify a unique database name. The default value for the management database is AppVManagement.
-
App-V 5.0 management server location – specifies the machine account on which the management server is deployed. This should be specified in the following format Domain\MachineAccount.
-
App-V 5.0 management server installation administrator - specifies the account that will be used to install the App-V 5.0 management server. You should use the following format: Domain\AdministratorLoginName.
To help reduce the risk of unwanted or malicious data being sent to the reporting server, you should restrict access to the Reporting Web Service per your corporate security policy.
-
-
-
-
-
Windows Web Server with the IIS role with the following features: Common HTTP Features (static content and default document), Application Development (ASP.NET, .NET Extensibility, ISAPI Extensions and ISAPI Filters), Security (Windows Authentication, Request Filtering), Security (Windows Authentication, Request Filtering), Management Tools (IIS Management Console)
-
64-bit ASP.NET registration
-
Installation location - by default this component is installed to %PROGRAMFILES%\Microsoft Application Virtualization Server.
-
App-V 5.0 reporting service website name – specifies the name of the website or the default name that will be used.
-
App-V 5.0 reporting service port binding - This should be a unique port number that is not already used by another website that runs on the computer.
-
-
-
-
Reporting Database
-
-
-Note
The database is required only when using the App-V 5.0 reporting server.
The App-V 5.0 server components are dependent but they have varying requirements and installation options that must be deployed. Use the following information to prepare your environment to run the App-V 5.0 reporting database.
-
-
Installation location - by default this component will be installed to %PROGRAMFILES%\Microsoft Application Virtualization Server.
-
Custom SQL Server instance name (if applicable) – the format should be INSTANCENAME, because the installation assumes that it is on the local machine. If you specify the name with the following format, SVR\INSTANCE will fail.
-
Custom App-V 5.0 database name (if applicable) – you must specify a unique database name. The default value for the reporting database is AppVReporting.
-
App-V 5.0 reporting server location – specifies the machine account on which the reporting server is deployed. This should be specified in the following format Domain\MachineAccount.
-
App-V 5.0 reporting server installation administrator - specifies the account that will be used to install the App-V 5.0 reporting server. You should use the following format: Domain\AdministratorLoginName.
-
Microsoft SQL Server Service and the Microsoft SQL Server Agent Service – these services must be associated with user accounts that have access to query AD.
Windows Web Server with the IIS role with the following features: Common HTTP Features (static content and default document), Application Development (ASP.NET, .NET Extensibility, ISAPI Extensions and ISAPI Filters), Security (Windows Authentication, Request Filtering), Security (Windows Authentication, Request Filtering), Management Tools (IIS Management Console)
-
64-bit ASP.NET registration
-
-
The App-V 5.0 server components are dependent but they have varying requirements and installation options that must be deployed. Use the following information to prepare your environment to run the App-V 5.0 publishing server.
-
-
Installation location - by default this component is installed to %PROGRAMFILES%\Microsoft Application Virtualization Server.
-
App-V 5.0 management service URL – specifies the URL of the App-V 5.0 management service. This is the port that the publishing server communicates with, and it should be specified using the following format: http://localhost:12345.
-
App-V 5.0 publishing service website name – specifies the name of the website or the default name that will be used.
-
App-V 5.0 publishing service port binding - This should be a unique port number that is not already used by another website that runs on the computer.
-
-
-
-
-
-
-
-
-
-
-
-
-## Related topics
-
-
-[Planning to Deploy App-V](planning-to-deploy-app-v.md)
-
-[App-V 5.0 Supported Configurations](app-v-50-supported-configurations.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v5/app-v-50-security-considerations.md b/mdop/appv-v5/app-v-50-security-considerations.md
deleted file mode 100644
index 3425e93637..0000000000
--- a/mdop/appv-v5/app-v-50-security-considerations.md
+++ /dev/null
@@ -1,128 +0,0 @@
----
-title: App-V 5.0 Security Considerations
-description: App-V 5.0 Security Considerations
-author: dansimp
-ms.assetid: 1e7292a0-7972-4b4f-85a9-eaf33f6c563a
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 08/30/2016
----
-
-
-# App-V 5.0 Security Considerations
-
-
-This topic contains a brief overview of the accounts and groups, log files, and other security-related considerations for App-V 5.0.
-
-**Important**
-App-V 5.0 is not a security product and does not provide any guarantees for a secure environment.
-
-
-
-## PackageStoreAccessControl (PSAC) feature has been deprecated
-
-
-Effective as of June, 2014, the PackageStoreAccessControl (PSAC) feature that was introduced in Microsoft Application Virtualization (App-V) 5.0 Service Pack 2 (SP2) has been deprecated in both single-user and multi-user environments.
-
-## General security considerations
-
-
-**Understand the security risks.** The most serious risk to App-V 5.0 is that its functionality could be hijacked by an unauthorized user who could then reconfigure key data on App-V 5.0 clients. The loss of App-V 5.0 functionality for a short period of time due to a denial-of-service attack would not generally have a catastrophic impact.
-
-**Physically secure your computers**. Security is incomplete without physical security. Anyone with physical access to an App-V 5.0 server could potentially attack the entire client base. Any potential physical attacks must be considered high risk and mitigated appropriately. App-V 5.0 servers should be stored in a physically secure server room with controlled access. Secure these computers when administrators are not physically present by having the operating system lock the computer, or by using a secured screen saver.
-
-**Apply the most recent security updates to all computers**. To stay informed about the latest updates for operating systems, Microsoft SQL Server, and App-V 5.0, subscribe to the Security Notification service ().
-
-**Use strong passwords or pass phrases**. Always use strong passwords with 15 or more characters for all App-V 5.0 and App-V 5.0 administrator accounts. Never use blank passwords. For more information about password concepts, see the “Account Passwords and Policies” white paper on TechNet ().
-
-## Accounts and groups in App-V 5.0
-
-
-A best practice for user account management is to create domain global groups and add user accounts to them. Then, add the domain global accounts to the necessary App-V 5.0 local groups on the App-V 5.0 servers.
-
-**Note**
-App-V client computer accounts that need to connect to the publishing server must be part of the publishing server’s **Users** local group. By default, all computers in the domain are part of the **Authorized Users** group, which is part of the **Users** local group.
-
-
-
-### App-V 5.0 server security
-
-No groups are created automatically during App-V 5.0 Setup. You should create the following Active Directory Domain Services global groups to manage App-V 5.0 server operations.
-
-
-
-
-
-
-
-
-
Group name
-
Details
-
-
-
-
-
App-V Management Admin group
-
Used to manage the App-V 5.0 management server. This group is created during the App-V 5.0 Management Server installation.
-
-Important
There is no method to create the group using the management console after you have completed the installation.
-
-
-
-
-
-
-
Database read/write for Management Service account
-
Provides read/write access to the management database. This account should be created during the App-V 5.0 management database installation.
-
-
-
App-V Management Service install admin account
-
-Note
This is only required if management database is being installed separately from the service.
-
-
-
-
-
Provides public access to schema-version table in management database. This account should be created during the App-V 5.0 management database installation.
-
-
-
App-V Reporting Service install admin account
-
-Note
This is only required if reporting database is being installed separately from the service.
-
-
-
-
-
Public access to schema-version table in reporting database. This account should be created during the App-V 5.0 reporting database installation.
-
-
-
-
-
-
-Consider the following additional information:
-
-- Access to the package shares - If a share exists on the same computer as the management Server, the **Network** service requires read access to the share. In addition, each App-V client computer must have read access to the package share.
-
- **Note**
- In previous versions of App-V, package share was referred to as content share.
-
-
-
-- Registering publishing servers with Management Server - A publishing server must be registered with the Management server. For example, it must be added to the database, so that the Publishing server machine accounts are able to call into the Management service API.
-
-### App-V 5.0 package security
-
-The following will help you plan how to ensure that virtualized packages are secure.
-
-- If an application installer applies an access control list (ACL) to a file or directory, then that ACL is not persisted in the package. When the package is deployed, if the file or directory is modified by a user it will either inherit the ACL in the **%userprofile%** or inherit the ACL of the target computer’s directory. The former case occurs if the file or directory does not exist in a virtual file system location; the latter case occurs if the file or directory exists in a virtual file system location, for example **%windir%**.
-
-## App-V 5.0 log files
-
-
-During App-V 5.0 Setup, setup log files are created in the **%temp%** folder of the installing user.
diff --git a/mdop/appv-v5/app-v-50-sp3-prerequisites.md b/mdop/appv-v5/app-v-50-sp3-prerequisites.md
deleted file mode 100644
index 4b92ce66e0..0000000000
--- a/mdop/appv-v5/app-v-50-sp3-prerequisites.md
+++ /dev/null
@@ -1,659 +0,0 @@
----
-title: App-V 5.0 SP3 Prerequisites
-description: App-V 5.0 SP3 Prerequisites
-author: dansimp
-ms.assetid: fa8d5578-3a53-4e8a-95c7-e7a5f6e4a31c
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# App-V 5.0 SP3 Prerequisites
-
-
-Before installing Microsoft Application Virtualization (App-V) 5.0 SP3, ensure that you have installed all of the following required prerequisite software.
-
-For a list of supported operating systems and hardware requirements for the App-V Server, Sequencer, and Client, see [App-V 5.0 SP3 Supported Configurations](app-v-50-sp3-supported-configurations.md).
-
-## Summary of software preinstalled on each operating system
-
-
-The following table indicates the software that is already installed for different operating systems.
-
-
-
-
-
-
-
-
-
Operating system
-
Prerequisite description
-
-
-
-
-
Windows 8.1
-
All of the prerequisite software is already installed.
-
-
-
Windows 8
-
Windows Server 2012
-
The following prerequisite software is already installed:
-
-
Microsoft .NET Framework 4.5
-
Windows PowerShell 3.0
-
-Note
Installing PowerShell 3.0 requires a restart.
-
-
-
-
-
-
-
-
Windows 7
-
The prerequisite software is not already installed. You must install it before you can install App-V.
-
-
-
-
-
-
-## App-V Server prerequisite software
-
-
-Install the required prerequisite software for the App-V 5.0 SP3 Server components.
-
-### What to know before you start
-
-
-
-
-
-
-
-
-
Account for installing the App-V Server
-
The account that you use to install the App-V Server components must have:
-
-
Administrative rights on the computer on which you are installing the components.
-
The ability to query Active Directory Domain Services.
-
-
-
-
Port and firewall
-
-
Specify a port where each component will be hosted.
-
Add the associated firewall rules to allow incoming requests to the specified ports.
-
-
-
-
-
Web Distributed Authoring and Versioning (WebDAV)
-
WebDAV is automatically disabled for the Management Service.
-
-
-
Supported deployment scenarios
-
-
A stand-alone deployment, where all components are deployed on the same server.
-
A distributed deployment.
-
-
-
-
Unsupported deployment scenarios
-
-
Installing the App-V Server on a computer that runs any previous version or component of App-V.
-
Installing the App-V server components on a computer that runs server core or domain controller.
-
-
-
-
-
-
-
-### Management server prerequisite software
-
-
This role must be added to a server operating system that is supported for the Management server.
-
-
-
Web Server (IIS) Management Tools
-
Click IIS Management Scripts and Tools.
-
-
-
Web Server Role Services
-
Common HTTP Features:
-
-
Static Content
-
Default Document
-
-
Application Development:
-
-
ASP.NET
-
.NET Extensibility
-
ISAPI Extensions
-
ISAPI Filters
-
-
Security:
-
-
Windows Authentication
-
Request Filtering
-
-
Management Tools:
-
-
IIS Management Console
-
-
-
-
Default installation location
-
%PROGRAMFILES%\Microsoft Application Virtualization Server
-
-
-
Location of the Management database
-
SQL Server database name, SQL Server database instance name, and database name.
-
-
-
Management console and Management database permissions
-
A user or group that can access the Management console and database after the deployment is complete. Only these users or groups will have access to the Management console and database unless additional administrators are added by using the Management console.
-
-
-
Management service website name
-
Name for the Management console website.
-
-
-
Management service port binding
-
Unique port number for the Management service. This port cannot be used by another process on the computer.
-
-
-
Microsoft Silverlight 5
-
The Management console is available only if Silverlight is installed.
-
-
-
-
-
-
-### Management server database prerequisite software
-
-The Management database is required only if you are using the App-V 5.0 SP3 Management server.
-
-
This role must be added to a server operating system that is supported for the Management server.
-
-
-
Web Server (IIS) Management Tools
-
Click IIS Management Scripts and Tools.
-
-
-
Web Server Role Services
-
To reduce the risk of unwanted or malicious data being sent to the Reporting server, you should restrict access to the Reporting Web Service per your corporate security policy.
-
Common HTTP Features:
-
-
Static Content
-
Default Document
-
-
Application Development:
-
-
ASP.NET
-
.NET Extensibility
-
ISAPI Extensions
-
ISAPI Filters
-
-
Security:
-
-
Windows Authentication
-
Request Filtering
-
-
Management Tools:
-
-
IIS Management Console
-
-
-
-
Default installation location
-
%PROGRAMFILES%\Microsoft Application Virtualization Server
-
-
-
Reporting service website name
-
Name for the Reporting website.
-
-
-
Reporting service port binding
-
Unique port number for the Reporting service. This port cannot be used by another process on the computer.
-
-
-
-
-
-
-### Reporting database prerequisite software
-
-The Reporting database is required only if you are using the App-V 5.0 SP3 Reporting server.
-
-
-
-
-
-## Sequencer prerequisite software
-
-
-**What to know before installing the prerequisites:**
-
-- Best practice: The computer that runs the Sequencer should have the same hardware and software configurations as the computers that will run the virtual applications.
-
-- The sequencing process is resource intensive, so make sure that the computer that runs the Sequencer has plenty of memory, a fast processor, and a fast hard drive. The system requirements of locally installed applications cannot exceed those of the Sequencer. For more information, see [App-V 5.0 Supported Configurations](app-v-50-supported-configurations.md).
-
-
-
-
-
-
-
-
-
-
-## Related topics
-
-
-[Planning for App-V 5.0](planning-for-app-v-50-rc.md)
-
-[App-V 5.0 SP3 Supported Configurations](app-v-50-sp3-supported-configurations.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v5/app-v-50-sp3-supported-configurations.md b/mdop/appv-v5/app-v-50-sp3-supported-configurations.md
deleted file mode 100644
index 8341bc668d..0000000000
--- a/mdop/appv-v5/app-v-50-sp3-supported-configurations.md
+++ /dev/null
@@ -1,467 +0,0 @@
----
-title: App-V 5.0 SP3 Supported Configurations
-description: App-V 5.0 SP3 Supported Configurations
-author: dansimp
-ms.assetid: 08ced79a-0ed3-43c3-82e7-de01c1f33e81
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 08/30/2016
----
-
-
-# App-V 5.0 SP3 Supported Configurations
-
-
-This topic specifies the requirements to install and run Microsoft Application Virtualization (App-V) 5.0 SP3 in your environment.
-
-## App-V Server system requirements
-
-
-This section lists the operating system and hardware requirements for all of the App-V Server components.
-
-### Unsupported App-V 5.0 SP3 Server scenarios
-
-The App-V 5.0 SP3 Server does not support the following scenarios:
-
-- Deployment to a computer that runs Microsoft Windows Server Core.
-
-- Deployment to a computer that runs a previous version of App-V 5.0 SP3 Server components. You can install App-V 5.0 SP3 side by side with the App-V 4.5 Lightweight Streaming Server (LWS) server only. Deployment of App-V side by side with the App-V 4.5 Application Virtualization Management Service (HWS) server is not supported.
-
-- Deployment to a computer that runs Microsoft SQL Server Express edition.
-
-- Remote deployment of the management server database or the reporting database. You must run the installer directly on the computer that is running Microsoft SQL Server.
-
-- Deployment to a domain controller.
-
-- Short paths. If you plan to use a short path, you must create a new volume.
-
-### Management server operating system requirements
-
-The following table lists the operating systems that are supported for the App-V 5.0 SP3 Management server installation.
-
-**Note**
-Microsoft provides support for the current service pack and, in some cases, the immediately preceding service pack. To find the support timelines for your product, see the [Lifecycle Supported Service Packs](https://go.microsoft.com/fwlink/p/?LinkId=31975). See [Microsoft Support Lifecycle Support Policy FAQ](https://go.microsoft.com/fwlink/p/?LinkId=31976) for more information.
-
-
-
-
-
-
-
-
-
-
-
-
Operating system
-
Service Pack
-
System architecture
-
-
-
-
-
Microsoft Windows Server 2012 R2
-
-
64-bit
-
-
-
Microsoft Windows Server 2012
-
-
64-bit
-
-
-
Microsoft Windows Server 2008 R2
-
SP1
-
64-bit
-
-
-
-
-
-
-**Important**
-Deployment of the Management server role to a computer with Remote Desktop Sharing (RDS) enabled is not supported.
-
-
-
-### Management server hardware requirements
-
-- Processor—1.4 GHz or faster, 64-bit (x64) processor
-
-- RAM—1 GB RAM (64-bit)
-
-- Disk space—200 MB available hard disk space, not including the content directory
-
-### Management server database requirements
-
-The following table lists the SQL Server versions that are supported for the App-V 5.0 SP3 Management database installation.
-
-
-
-
-
-
-
-
-
-
SQL Server version
-
Service pack
-
System architecture
-
-
-
-
-
Microsoft SQL Server 2014
-
-
32-bit or 64-bit
-
-
-
Microsoft SQL Server 2012
-
SP2
-
32-bit or 64-bit
-
-
-
Microsoft SQL Server 2008 R2
-
SP3
-
32-bit or 64-bit
-
-
-
-
-
-
-### Publishing server operating system requirements
-
-The following table lists the operating systems that are supported for the App-V 5.0 SP3 Publishing server installation.
-
-
-
-
-
-
-
-
-
-
Operating system
-
Service Pack
-
System architecture
-
-
-
-
-
Microsoft Windows Server 2012 R2
-
-
64-bit
-
-
-
Microsoft Windows Server 2012
-
-
64-bit
-
-
-
Microsoft Windows Server 2008 R2
-
SP1
-
64-bit
-
-
-
-
-
-
-### Publishing server hardware requirements
-
-App-V adds no additional requirements beyond those of Windows Server.
-
-- Processor—1.4 GHz or faster, 64-bit (x64) processor
-
-- RAM—2 GB RAM (64-bit)
-
-- Disk space—200 MB available hard disk space, not including the content directory
-
-### Reporting server operating system requirements
-
-The following table lists the operating systems that are supported for the App-V 5.0 SP3 Reporting server installation.
-
-
-
-
-
-
-
-
-
-
Operating system
-
Service Pack
-
System architecture
-
-
-
-
-
Microsoft Windows Server 2012 R2
-
-
64-bit
-
-
-
Microsoft Windows Server 2012
-
-
64-bit
-
-
-
Microsoft Windows Server 2008 R2
-
SP1
-
64-bit
-
-
-
-
-
-
-### Reporting server hardware requirements
-
-App-V adds no additional requirements beyond those of Windows Server.
-
-- Processor—1.4 GHz or faster, 64-bit (x64) processor
-
-- RAM—2 GB RAM (64-bit)
-
-- Disk space—200 MB available hard disk space
-
-### Reporting server database requirements
-
-The following table lists the SQL Server versions that are supported for the App-V 5.0 SP3 Reporting database installation.
-
-
-
-
-
-
-
-
-
-
SQL Server version
-
Service pack
-
System architecture
-
-
-
-
-
Microsoft SQL Server 2014
-
-
32-bit or 64-bit
-
-
-
Microsoft SQL Server 2012
-
SP2
-
32-bit or 64-bit
-
-
-
Microsoft SQL Server 2008 R2
-
SP3
-
32-bit or 64-bit
-
-
-
-
-
-
-## App-V client system requirements
-
-
-The following table lists the operating systems that are supported for the App-V 5.0 SP3 client installation.
-
-
-
-
-
-
-
-
-
-
Operating system
-
Service pack
-
System architecture
-
-
-
-
-
Microsoft Windows 8.1
-
-
32-bit or 64-bit
-
-
-
Microsoft Windows 8
-
-
32-bit or 64-bit
-
-
-
Windows 7
-
SP1
-
32-bit or 64-bit
-
-
-
-
-
-
-The following App-V client installation scenarios are not supported, except as noted:
-
-- Computers that run Windows Server
-
-- Computers that run App-V 4.6 SP1 or earlier versions
-
-- The App-V 5.0 SP3 Remote Desktop services client is supported only for RDS-enabled servers
-
-### App-V client hardware requirements
-
-The following list displays the supported hardware configuration for the App-V 5.0 SP3 client installation.
-
-- Processor— 1.4 GHz or faster 32-bit (x86) or 64-bit (x64) processor
-
-- RAM— 1 GB (32-bit) or 2 GB (64-bit)
-
-- Disk— 100 MB for installation, not including the disk space that is used by virtualized applications.
-
-## Remote Desktop Services client system requirements
-
-
-The following table lists the operating systems that are supported for App-V 5.0 SP3 Remote Desktop Services (RDS) client installation.
-
-
-
-
-
-
-
-
-
-
Operating system
-
Service Pack
-
System architecture
-
-
-
-
-
Microsoft Windows Server 2012 R2
-
-
64-bit
-
-
-
Microsoft Windows Server 2012
-
-
64-bit
-
-
-
Microsoft Windows Server 2008 R2
-
SP1
-
64-bit
-
-
-
-
-
-
-### Remote Desktop Services client hardware requirements
-
-App-V adds no additional requirements beyond those of Windows Server.
-
-- Processor—1.4 GHz or faster, 64-bit (x64) processor
-
-- RAM—2 GB RAM (64-bit)
-
-- Disk space—200 MB available hard disk space
-
-## Sequencer system requirements
-
-
-The following table lists the operating systems that are supported for the App-V 5.0 SP3 Sequencer installation.
-
-
-
-
-
-
-
-
-
-
Operating system
-
Service pack
-
System architecture
-
-
-
-
-
Microsoft Windows Server 2012 R2
-
-
64-bit
-
-
-
Microsoft Windows Server 2012
-
-
64-bit
-
-
-
Microsoft Windows Server 2008 R2
-
SP1
-
64-bit
-
-
-
Microsoft Windows 8.1
-
-
32-bit and 64-bit
-
-
-
Microsoft Windows 8
-
-
32-bit and 64-bit
-
-
-
Microsoft Windows 7
-
SP1
-
32-bit and 64-bit
-
-
-
-
-
-
-### Sequencer hardware requirements
-
-See the Windows or Windows Server documentation for the hardware requirements. App-V adds no additional hardware requirements.
-
-## Supported versions of System Center Configuration Manager
-
-
-The App-V client supports the following versions of System Center Configuration Manager:
-
-- Microsoft System Center 2012 Configuration Manager
-
-- System Center 2012 R2 Configuration Manager
-
-- System Center 2012 R2 Configuration Manager SP1
-
-For more information about how Configuration Manager integrates with App-V, see [Planning for App-V Integration with Configuration Manager](https://technet.microsoft.com/library/jj822982.aspx).
-
-
-
-
-
-
-## Related topics
-
-
-[Planning to Deploy App-V](planning-to-deploy-app-v.md)
-
-[App-V 5.0 SP3 Prerequisites](app-v-50-sp3-prerequisites.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v5/app-v-50-supported-configurations.md b/mdop/appv-v5/app-v-50-supported-configurations.md
deleted file mode 100644
index 4b23a3738a..0000000000
--- a/mdop/appv-v5/app-v-50-supported-configurations.md
+++ /dev/null
@@ -1,532 +0,0 @@
----
-title: App-V 5.0 Supported Configurations
-description: App-V 5.0 Supported Configurations
-author: dansimp
-ms.assetid: 3787ff63-7ce7-45a8-8f01-81b4b6dced34
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 08/30/2016
----
-
-
-# App-V 5.0 Supported Configurations
-
-
-This topic specifies the requirements that are necessary to install and run Microsoft Application Virtualization (App-V) 5.0 in your environment.
-
-**Important**
-**The supported configurations in this article apply only to App-V 5.0**. For supported configurations that apply to App-V 5.0 Service Packs, see the following web pages:
-
-- [What's new in App-V 5.0 SP1](whats-new-in-app-v-50-sp1.md)
-
-- [About App-V 5.0 SP2](about-app-v-50-sp2.md)
-
-- [App-V 5.0 SP3 Supported Configurations](app-v-50-sp3-supported-configurations.md)
-
-
-
-## App-V 5.0 server system requirements
-
-
-**Important**
-The App-V 5.0 server does not support the following scenarios:
-
-
-
-- Deployment to a computer that runs Microsoft Windows Server Core.
-
-- Deployment to a computer that runs a previous version of App-V 5.0 server components.
-
- **Note**
- You can install App-V 5.0 side-by-side with the App-V 4.5 Lightweight Streaming Server (LWS) server only. Deployment of App-V 5.0 side-by-side with the App-V 4.5 Application Virtualization Management Service (HWS) server is not supported.
-
-
-
-- Deployment to a computer that runs Microsoft SQL Server Express edition.
-
-- Remote deployment of the management server database or the reporting database. The installer must be run directly on the computer running Microsoft SQL for the database installation to succeed.
-
-- Deployment to a domain controller.
-
-- Short paths are not supported. If you plan to use a short path you must create a new volume.
-
-### Management Server operating system requirements
-
-The following table lists the operating systems that are supported for the App-V 5.0 management server installation.
-
-**Note**
-Microsoft provides support for the current service pack and, in some cases, the immediately preceding service pack. To find the support timelines for your product, see the [Lifecycle Supported Service Packs](https://go.microsoft.com/fwlink/p/?LinkId=31975). For additional information about Microsoft Support Lifecycle Policy, see [Microsoft Support Lifecycle Support Policy FAQ](https://go.microsoft.com/fwlink/p/?LinkId=31976).
-
-
-
-
-
-
-
-
-
-
-
-
-
Operating system
-
Edition
-
Service pack
-
System architecture
-
-
-
-
-
Microsoft Windows Server 2008 (Standard, Enterprise, Datacenter, or Web Server)
-
R2
-
SP1 and higher
-
64-bit
-
-
-
Microsoft Windows Server 2012 (Standard, Datacenter)
-
-
-
64-bit
-
-
-
Microsoft Windows Server 2012 (Standard, Datacenter)
-
R2
-
-
64-bit
-
-
-
-
-
-
-**Important**
-Deployment of the management server role to a computer with Remote Desktop Sharing (RDS) enabled is not supported.
-
-
-
-### Management Server hardware requirements
-
-- Processor—1.4 GHz or faster, 64-bit (x64) processor
-
-- RAM— 1 GB RAM (64-bit)
-
-- Disk space—200 MB available hard disk space, not including the content directory.
-
-### Publishing Server operating system requirements
-
-The following table lists the operating systems that are supported for the App-V 5.0 publishing server installation.
-
-**Note**
-Microsoft provides support for the current service pack and, in some cases, the immediately preceding service pack. To find the support timelines for your product, see the [Lifecycle Supported Service Packs](https://go.microsoft.com/fwlink/p/?LinkId=31975). For additional information about Microsoft Support Lifecycle Policy, see [Microsoft Support Lifecycle Support Policy FAQ](https://go.microsoft.com/fwlink/p/?LinkId=31976).
-
-
-
-
-
-
-
-
-
-
-
-
-
Operating system
-
Edition
-
Service pack
-
System architecture
-
-
-
-
-
Microsoft Windows Server 2008 (Standard, Enterprise, Datacenter, or Web Server)
-
R2
-
-
64-bit
-
-
-
Microsoft Windows Server 2012 (Standard, Datacenter)
-
-
-
64-bit
-
-
-
Microsoft Windows Server 2012 (Standard, Datacenter)
-
R2
-
-
64-bit
-
-
-
-
-
-
-### Publishing Server hardware requirements
-
-- Processor—1.4 GHz or faster. 64-bit (x64) processor
-
-- RAM— 2 GB RAM (64-bit)
-
-- Disk space—200 MB available hard disk space. not including content directory
-
-### Reporting Server operating system requirements
-
-The following table lists the operating systems that are supported for the App-V 5.0 reporting server installation.
-
-**Note**
-Microsoft provides support for the current service pack and, in some cases, the immediately preceding service pack. To find the support timelines for your product, see the [Lifecycle Supported Service Packs](https://go.microsoft.com/fwlink/p/?LinkId=31975). For additional information about Microsoft Support Lifecycle Policy, see [Microsoft Support Lifecycle Support Policy FAQ](https://go.microsoft.com/fwlink/p/?LinkId=31976).
-
-
-
-
-
-
-
-
-
-
-
-
-
Operating system
-
Edition
-
Service Pack
-
System architecture
-
-
-
-
-
Microsoft Windows Server 2008 (Standard, Enterprise, Datacenter, or Web Server)
-
R2
-
-
64-bit
-
-
-
Microsoft Windows Server 2012 (Standard, Datacenter)
-
-
-
64-bit
-
-
-
Microsoft Windows Server 2012 (Standard, Datacenter)
-
R2
-
-
64-bit
-
-
-
-
-
-
-### Reporting Server hardware requirements
-
-- Processor—1.4 GHz or faster. 64-bit (x64) processor
-
-- RAM—2 GB RAM (64-bit)
-
-- Disk space—200 MB available hard disk space
-
-### SQL Server database requirements
-
-The following table lists the SQL Server versions that are supported for the App-V 5.0 database and server installation.
-
-
-
-
-
-
-
-
-
-
-
-
App-V 5.0 server type
-
SQL Server version
-
Edition
-
Service pack
-
System architecture
-
-
-
-
-
Management / Reporting
-
Microsoft SQL Server 2008
-
(Standard, Enterprise, Datacenter, or the Developer Edition with the following feature: Database Engine Services.)
-
-
-
32-bit or 64-bit
-
-
-
Management / Reporting
-
Microsoft SQL Server 2008
-
(Standard, Enterprise, Datacenter, or the Developer Edition with the following feature: Database Engine Services.)
-
R2
-
SP2
-
32-bit or 64-bit
-
-
-
Management / Reporting
-
Microsoft SQL Server 2012
-
(Standard, Enterprise, Datacenter, or the Developer Edition with the following feature: Database Engine Services.)
-
-
-
32-bit or 64-bit
-
-
-
-
-
-
-## App-V 5.0 client system requirements
-
-
-The following table lists the operating systems that are supported for the App-V 5.0 client installation.
-
-**Note**
-Microsoft provides support for the current service pack and, in some cases, the immediately preceding service pack. To find the support timelines for your product, see the [Lifecycle Supported Service Packs](https://go.microsoft.com/fwlink/p/?LinkId=31975). For additional information about Microsoft Support Lifecycle Policy, see [Microsoft Support Lifecycle Support Policy FAQ](https://go.microsoft.com/fwlink/p/?LinkId=31976).
-
-
-
-
-
-
-
-
-
-
-
-
Operating system
-
Service pack
-
System architecture
-
-
-
-
-
Microsoft Windows 7
-
SP1
-
32-bit or 64-bit
-
-
-
Microsoft Windows 8
-
-
32-bit or 64-bit
-
-
-
-Important
Windows 8.1 is only supported by App-V 5.0 SP2
-
-
-
-
-
Windows 8.1
-
-
32-bit or 64-bit
-
-
-
-
-
-
-The following App-V client installation scenarios are not supported, except as noted:
-
-- Computers that run Windows Server
-
-- Computers that run App-V 4.6 SP1 or earlier versions
-
-- The App-V 5.0 Remote Desktop services client is supported only for RDS-enabled servers
-
-### Client hardware requirements
-
-The following list displays the supported hardware configuration for the App-V 5.0 client installation.
-
-- Processor— 1.4 GHz or faster 32-bit (x86) or 64-bit (x64) processor
-
-- RAM— 1 GB (32-bit) or 2 GB (64-bit)
-
-- Disk— 100 MB for installation, not including the disk space that is used by virtualized applications.
-
-## App-V 5.0 Remote Desktop client system requirements
-
-
-The following table lists the operating systems that are supported for App-V 5.0 Remote Desktop client installation.
-
-**Note**
-Microsoft provides support for the current service pack and, in some cases, the immediately preceding service pack. To find the support timelines for your product, see the [Lifecycle Supported Service Packs](https://go.microsoft.com/fwlink/p/?LinkId=31975). For additional information about Microsoft Support Lifecycle Policy, see [Microsoft Support Lifecycle Support Policy FAQ](https://go.microsoft.com/fwlink/p/?LinkId=31976).
-
-
-
-Operating system
-Edition
-Service pack
-Microsoft Windows Server 2008
-
-R2
-
-SP1
-
-Microsoft Windows Server 2012
-
-**Important**
-Windows Server 2012 R2 is only supported by App-V 5.0 SP2
-
-
-
-Microsoft Windows Server 2012 (Standard, Datacenter)
-
-R2
-
-64-bit
-
-
-
-### Remote Desktop client hardware requirements
-
-The following list displays the supported hardware configuration for the App-V 5.0 client installation.
-
-- Processor— 1.4 GHz or faster 32-bit (x86) or 64-bit (x64) processor
-
-- RAM— 1 GB (32-bit) or 2 GB (64-bit)
-
-- Disk— 100 MB for installation, not including the disk space that is used by virtualized applications.
-
-## App-V 5.0 Sequencer system requirements
-
-
-The following table lists the operating systems that are supported for App-V 5.0 Sequencer installation.
-
-**Note**
-Microsoft provides support for the current service pack and, in some cases, the immediately preceding service pack. To find the support timelines for your product, see the [Lifecycle Supported Service Packs](https://go.microsoft.com/fwlink/p/?LinkId=31975). For additional information about Microsoft Support Lifecycle Policy, see [Microsoft Support Lifecycle Support Policy FAQ](https://go.microsoft.com/fwlink/p/?LinkId=31976).
-
-
-
-
-
-
-
-
-
-
-
-
-
Operating system
-
Edition
-
Service pack
-
System architecture
-
-
-
-
-
Microsoft Windows 7
-
-
SP1
-
32-bit and 64-bit
-
-
-
Microsoft Windows 8
-
-
-
32-bit and 64-bit
-
-
-
-Important
Windows 8.1 is only supported by App-V 5.0 SP2
-
-
-
-
-
Windows 8.1
-
-
-
32-bit or 64-bit
-
-
-
Microsoft Windows Server 2008
-
R2
-
SP1
-
32-bit and 64-bit
-
-
-
Microsoft Windows Server 2012
-
-
-
32-bit and 64-bit
-
-
-
-Important
Windows Server 2012 R2 is only supported by App-V 5.0 SP2
-
-
-
-
-
Microsoft Windows Server 2012
-
R2
-
-
64-bit
-
-
-
-
-
-
-## Supported versions of System Center Configuration Manager
-
-
-You can use Microsoft System Center 2012 Configuration Manager or System Center 2012 R2 Configuration Manager to manage App-V virtual applications, reporting, and other functions. The following table lists the supported versions of Configuration Manager for each applicable version of App-V.
-
-
-
-
-
-
-
-
-
Supported Configuration Manager version
-
App-V version
-
-
-
-
-
Microsoft System Center 2012 Configuration Manager
-
-
App-V 5.0
-
App-V 5.0 SP1
-
App-V 5.0 SP2
-
-
-
-
System Center 2012 R2 Configuration Manager
-
-
App-V 5.0
-
App-V 5.0 SP1
-
App-V 5.0 SP2
-
-
-
-
-
-
-
-For more information about how Configuration Manager integrates with App-V, see [Planning for App-V Integration with Configuration Manager](https://technet.microsoft.com/library/jj822982.aspx).
-
-
-
-
-
-
-## Related topics
-
-
-[Planning to Deploy App-V](planning-to-deploy-app-v.md)
-
-[App-V 5.0 Prerequisites](app-v-50-prerequisites.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v5/app-v-51-capacity-planning.md b/mdop/appv-v5/app-v-51-capacity-planning.md
deleted file mode 100644
index 0473ec9858..0000000000
--- a/mdop/appv-v5/app-v-51-capacity-planning.md
+++ /dev/null
@@ -1,963 +0,0 @@
----
-title: App-V 5.1 Capacity Planning
-description: App-V 5.1 Capacity Planning
-author: dansimp
-ms.assetid: 7a98062f-5a60-49d6-ab40-dc6057e1dd5a
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# App-V 5.1 Capacity Planning
-
-
-The following recommendations can be used as a baseline to help determine capacity planning information that is appropriate to your organization’s App-V 5.1 infrastructure.
-
-**Important**
-Use the information in this section only as a general guide for planning your App-V 5.1 deployment. Your system capacity requirements will depend on the specific details of your hardware and application environment. Additionally, the performance numbers displayed in this document are examples and your results may vary.
-
-
-
-## Determine the Project Scope
-
-
-Before you design the App-V 5.1 infrastructure, you must determine the project’s scope. The scope consists of determining which applications will be available virtually and to also identify the target users, and their locations. This information will help determine what type of App-V 5.1 infrastructure should be implemented. Decisions about the scope of the project must be based on the specific needs of your organization.
-
-
-
-
-
-
-
-
-
Task
-
More Information
-
-
-
-
-
Determine Application Scope
-
Depending on the applications to be virtualized, the App-V 5.1 infrastructure can be set up in different ways. The first task is to define what applications you want to virtualize.
-
-
-
Determine Location Scope
-
Location scope refers to the physical locations (for example, enterprise-wide or a specific geographic location) where you plan to run the virtualized applications. It can also refer to the user population (for example, a single department) who will run the virtual applications. You should obtain a network map that includes the connection paths as well as available bandwidth to each location and the number of users using virtualized applications and the WAN link speed.
-
-
-
-
-
-
-## Determine Which App-V 5.1 Infrastructure is Required
-
-
-**Important**
-Both of the following models require the App-V 5.1 client to be installed on the computer where you plan to run virtual applications.
-
-You can also manage your App-V 5.1 environment using an Electronic Software Distribution (ESD) solution such as Microsoft Systems Center Configuration Manager. For more information see [How to deploy App-V 5.1 Packages Using Electronic Software Distribution](how-to-deploy-app-v-51-packages-using-electronic-software-distribution.md).
-
-
-
-- **Standalone Model** - The standalone model allows virtual applications to be Windows Installer-enabled for distribution without streaming. App-V 5.1 in Standalone Mode consists of the sequencer and the client; no additional components are required. Applications are prepared for virtualization using a process called sequencing. For more information see, [Planning for the App-V 5.1 Sequencer and Client Deployment](planning-for-the-app-v-51-sequencer-and-client-deployment.md). The stand-alone model is recommended for the following scenarios:
-
- - With disconnected remote users who cannot connect to the App-V 5.1 infrastructure.
-
- - When you are running a software management system, such as Configuration Manager 2012.
-
- - When network bandwidth limitations inhibit electronic software distribution.
-
-- **Full Infrastructure Model** - The full infrastructure model provides for software distribution, management, and reporting capabilities; it also includes the streaming of applications across the network. The App-V 5.1 Full Infrastructure Model consists of one or more App-V 5.1 management servers. The Management Server can be used to publish applications to all clients. The publishing process places the virtual application icons and shortcuts on the target computer. It can also stream applications to local users. For more information about installing the management server see, [Planning for the App-V 5.1 Server Deployment](planning-for-the-app-v-51-server-deployment.md). The full infrastructure model is recommended for the following scenarios:
-
- **Important**
- The App-V 5.1 full infrastructure model requires Microsoft SQL Server to store configuration data. For more information see [App-V 5.1 Supported Configurations](app-v-51-supported-configurations.md).
-
-
-
- - When you want to use the Management Server to publish the application to target computers.
-
- - For rapid provisioning of applications to target computers.
-
- - When you want to use App-V 5.1 reporting.
-
-## End-to-end Server Sizing Guidance
-
-
-The following section provides information about end-to-end App-V 5.1 sizing and planning. For more specific information, refer to the subsequent sections.
-
-**Note**
-Round trip response time on the client is the time taken by the computer running the App-V 5.1 client to receive a successful notification from the publishing server. Round trip response time on the publishing server is the time taken by the computer running the publishing server to receive a successful package metadata update from the management server.
-
-
-
-- 20,000 clients can target a single publishing server to obtain the package refreshes in an acceptable round trip time. (<3 seconds)
-
-- A single management server can support up to 50 publishing servers for package metadata refreshes in an acceptable round trip time. (<5 seconds)
-
-## App-V 5.1 Management Server Capacity Planning Recommendations
-
-
-The App-V 5.1 publishing servers require the management server for package refresh requests and package refresh responses. The management server then sends the information to the management database to retrieve information. For more information about App-V 5.1 management server supported configurations see [App-V 5.1 Supported Configurations](app-v-51-supported-configurations.md).
-
-**Note**
-The default refresh time on the App-V 5.1 publishing server is ten minutes.
-
-
-
-When multiple simultaneous publishing servers contact a single management server for package metadata refreshes, the following three factors influence the round trip response time on the publishing server:
-
-1. Number of publishing servers making simultaneous requests.
-
-2. Number of connection groups configured on the management server.
-
-3. Number of access groups configured on the management server.
-
-The following table displays more information about each factor that impacts round trip time.
-
-**Note**
-Round trip response time is the time taken by the computer running the App-V 5.1 publishing server to receive a successful package metadata update from the management server.
-
-
-
-
-
-
-
-
-
-
-
Factors impacting round trip response time
-
More Information
-
-
-
-
-
The number of publishing servers simultaneously requesting package metadata refreshes.
-
-
-
A single management server can respond to up to 320 publishing servers requesting publishing metadata simultaneously.
-
Round trip response time for 320 pub servers is ~40 seconds.
-
For <50 publishing servers requesting metadata simultaneously, the round trip response time is <5 seconds.
-
From 50 to 320 publishing servers, the response time increases linearly (approximately 2x).
-
-
-
-
The number of connection groups configured on the management server.
-
-
-
-
For up to 100 connection groups, there is no significant change in the round trip response time on the publishing server.
-
For 100 - 400 connection groups, there is a minor linear increase in the round trip response time.
-
-
-
-
The number of access groups configured on the management server.
-
-
-
-
For up to 40 access groups, there is a linear (approximately 3x) increase in the round trip response time on the publishing server.
-
-
-
-
-
-
-
-The following table displays sample values for each of the previous factors. In each variation, 120 packages are refreshed from the App-V 5.1management server.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Scenario
-
Variation
-
Number of connection groups
-
Number of access groups
-
Number of publishing servers
-
Network connection type publishing server / management server
-
Round trip response time on the publishing server (in seconds)
-
CPU utilization on management server
-
-
-
-
-
Publishing servers simultaneously contacting management server for publishing metadata.
-
Number of publishing servers
-
-
-
0
-
0
-
0
-
0
-
0
-
0
-
-
-
-
1
-
1
-
1
-
1
-
1
-
1
-
-
-
-
50
-
100
-
200
-
300
-
315
-
320
-
-
-
-
LAN
-
LAN
-
LAN
-
LAN
-
LAN
-
LAN
-
-
-
-
5
-
10
-
19
-
32
-
30
-
37
-
-
-
-
17
-
17
-
17
-
15
-
17
-
15
-
-
-
-
Publishing metadata contains connection groups
-
Number of connection groups
-
-
-
10
-
50
-
100
-
150
-
300
-
400
-
-
-
-
1
-
1
-
1
-
1
-
1
-
1
-
-
-
-
100
-
100
-
100
-
100
-
100
-
100
-
-
-
-
LAN
-
LAN
-
LAN
-
LAN
-
LAN
-
LAN
-
-
-
-
10
-
11
-
11
-
16
-
22
-
25
-
-
-
-
17
-
19
-
22
-
19
-
20
-
20
-
-
-
-
Publishing metadata contains access groups
-
Number of access groups
-
-
-
0
-
0
-
0
-
0
-
-
-
-
1
-
10
-
20
-
40
-
-
-
-
100
-
100
-
100
-
100
-
-
-
-
LAN
-
LAN
-
LAN
-
LAN
-
-
-
-
10
-
43
-
153
-
535
-
-
-
-
17
-
26
-
24
-
24
-
-
-
-
-
-
-
-The CPU utilization of the computer running the management server is around 25% irrespective of the number of publishing servers targeting it. The Microsoft SQL Server database transactions/sec, batch requests/sec and user connections are identical irrespective of the number of publishing servers. For example: Transactions/sec is ~30, batch requests ~200, and user connects ~6.
-
-Using a geographically distributed deployment, where the management server & publishing servers utilize a slow link network between them, the round trip response time on the publishing servers is within acceptable time limits (<5 seconds), even for 100 simultaneous requests on a single management server.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Scenario
-
Variation
-
Number of connection groups
-
Number of access groups
-
Number of publishing servers
-
Network connection type publishing server / management server
-
Round trip response time on the publishing server (in seconds)
-
CPU utilization on management server
-
-
-
-
-
Network connection between the publishing server and management server
-
1.5 Mbps Slow link Network
-
-
-
0
-
0
-
-
-
-
1
-
1
-
-
-
-
50
-
100
-
-
-
-
1.5Mbps Cable DSL
-
1.5Mbps Cable DSL
-
-
-
-
4
-
5
-
-
-
-
1
-
2
-
-
-
-
Network connection between the publishing server and management server
-
LAN / WIFI Network
-
-
-
0
-
0
-
-
-
-
1
-
1
-
-
-
-
100
-
200
-
-
-
-
Wifi
-
Wifi
-
-
-
-
11
-
20
-
-
-
-
15
-
17
-
-
-
-
-
-
-
-Whether the management server and publishing servers are connected over a slow link network, or a high speed network, the management server can handle approximately 15,000 package refresh requests in 30 minutes.
-
-## App-V 5.1 Reporting Server Capacity Planning Recommendations
-
-
-App-V 5.1 clients send reporting data to the reporting server. The reporting server then records the information in the Microsoft SQL Server database and returns a successful notification back to the computer running App-V 5.1 client. For more information about App-V 5.1 Reporting Server supported configurations see [App-V 5.1 Supported Configurations](app-v-51-supported-configurations.md).
-
-**Note**
-Round trip response time is the time taken by the computer running the App-V 5.1 client to send the reporting information to the reporting server and receive a successful notification from the reporting server.
-
-
-
-
-
-
-
-
-
-
-
Scenario
-
Summary
-
-
-
-
-
Multiple App-V 5.1 clients send reporting information to the reporting server simultaneously.
-
-
-
Round trip response time from the reporting server is 2.6 seconds for 500 clients.
-
Round trip response time from the reporting server is 5.65 seconds for 1000 clients.
-
Round trip response time increases linearly depending on number of clients.
-
-
-
-
Requests per second processed by the reporting server.
-
-
-
-
A single reporting server and a single database, can process a maximum of 139 requests per second. The average is 121 requests/second.
-
Using two reporting servers reporting to the same Microsoft SQL Server database, the average requests/second is similar to a single reporting server = ~127, with a max of 278 requests/second.
-
A single reporting server can process 500 concurrent/active connections.
-
A single reporting server can process a maximum 1500 concurrent connections.
-
-
-
-
Reporting Database.
-
-
-
-
Lock contention on the computer running Microsoft SQL Server is the limiting factor for requests/second.
-
Throughput and response time are independent of database size.
-
-
-
-
-
-
-
-**Calculating random delay**:
-
-The random delay specifies the maximum delay (in minutes) for data to be sent to the reporting server. When the scheduled task is started, the client generates a random delay between **0** and **ReportingRandomDelay** and will wait the specified duration before sending data.
-
-Random delay = 4 \* number of clients / average requests per second.
-
-Example: For 500 clients, with 120 requests per second, the Random delay is, 4 \* 500 / 120 = ~17 minutes.
-
-## App-V 5.1 Publishing Server Capacity Planning Recommendations
-
-
-Computers running the App-V 5.1 client connect to the App-V 5.1 publishing server to send a publishing refresh request and to receive a response. Round trip response time is measured on the computer running the App-V 5.1 client. Processor time is measured on the publishing server. For more information about App-V 5.1 Publishing Server supported configurations see [App-V 5.1 Supported Configurations](app-v-51-supported-configurations.md).
-
-**Important**
-The following list displays the main factors to consider when setting up the App-V 5.1 publishing server:
-
-- The number of clients connecting simultaneously to a single publishing server.
-
-- The number of packages in each refresh.
-
-- The available network bandwidth in your environment between the client and the App-V 5.1 publishing server.
-
-
-
-
-
-
-
-
-
-
-
Scenario
-
Summary
-
-
-
-
-
Multiple App-V 5.1 clients connect to a single publishing server simultaneously.
-
-
-
A publishing server running dual core processors can respond to at most 5000 clients requesting a refresh simultaneously.
-
For 5000-10000 clients, the publishing server requires a minimum quad core.
-
For 10000-20000 clients, the publishing server should have dual quad cores for more efficient response times.
-
A publishing server with a quad core can refresh up to 10000 packages within 3 seconds. (Supporting 10000 simultaneous clients)
-
-
-
-
Number of packages in each refresh.
-
-
-
-
Increasing number of packages will increase response time by ~40% (up to 1000 packages).
-
-
-
-
Network between the App-V 5.1 client and the publishing server.
-
-
-
-
Across a slow network (1.5 Mbps bandwidth), there is a 97% increase in response time compared to LAN (up to 1000 users).
-
-
-
-
-
-
-
-**Note**
-The publishing server CPU usage is always high during the time interval when it has to process simultaneous requests (>90% in most cases). The publishing server can handle ~1500 client requests in 1 second.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Scenario
-
Variation
-
Number of App-V 5.1 clients
-
Number of packages
-
Processor configuration on the publishing server
-
Network connection type publishing server / App-V 5.1 client
-
Round trip time on the App-V 5.1 client (in seconds)
-
-
-
-## App-V 5.1 Streaming Capacity Planning Recommendations
-
-
-Computers running the App-V 5.1 client stream the virtual application package from the streaming server. Round trip response time is measured on the computer running the App-V 5.1 client, and is the time taken to stream the entire package.
-
-**Important**
-The following list identifies the main factors to consider when setting up the App-V 5.1 streaming server:
-
-- The number of clients streaming application packages simultaneously from a single streaming server.
-
-- The size of the package being streamed.
-
-- The available network bandwidth in your environment between the client and the streaming server.
-
-
-
-
-
-
-
-
-
-
-
Scenario
-
Summary
-
-
-
-
-
Multiple App-V 5.1 clients stream applications from a single streaming server simultaneously.
-
-
-
If the number of clients simultaneously streaming from the same server increases, there is a linear relationship with the package download/streaming time.
-
-
-
-
Size of the package being streamed.
-
-
-
-
The package size has a significant impact on the streaming/download time only for larger packages with a size ~ 1GB. For package sizes ranging from 3 MB to 100 MB, the streaming time ranges from 20 seconds to 100 seconds, with 100 simultaneous clients.
-
-
-
-
Network between the App-V 5.1 client and the streaming server.
-
-
-
-
Across a slow network (1.5 Mbps bandwidth), there is a 70-80% increase in response time compared to LAN (up to 100 users).
-
-
-
-
-
-
-
-The following table displays sample values for each of the factors in the previous list:
-
-
-
-
-
-
-
-
-
-
-
-
-
Scenario
-
Variation
-
Number of App-V 5.1 clients
-
Size of each package
-
Network connection type streaming server / App-V 5.1 client
-
Round trip time on the App-V 5.1 client (in seconds)
-
-
-
-
-
Multiple App-V 5.1 clients streaming virtual application packages from a streaming server.
-
Number of clients.
-
-
-
100
-
200
-
1000
-
-
100
-
200
-
1000
-
-
-
-
3.5 MB
-
3.5 MB
-
3.5 MB
-
-
5 MB
-
5 MB
-
5 MB
-
-
-
-
LAN
-
LAN
-
LAN
-
-
LAN
-
LAN
-
LAN
-
-
-
-
29
-
39
-
391
-
-
35
-
68
-
461
-
-
-
-
Size of each package being streamed.
-
Size of each package.
-
-
-
100
-
200
-
-
100
-
200
-
-
-
-
21 MB
-
21 MB
-
-
109
-
109
-
-
-
-
LAN
-
LAN
-
-
LAN
-
LAN
-
-
-
33
-
83
-
-
100
-
160
-
-
-
Network connection between client and App-V 5.1 streaming server.
-
1.5 Mbps Slow link network.
-
-
-
100
-
-
100
-
-
-
-
3.5 MB
-
-
5 MB
-
-
-
-
1.5 Mbps Intra-Continental Network
-
-
-
102
-
-
121
-
-
-
-
-
-
-Each App-V 5.1 streaming server should be able to handle a minimum of 200 clients concurrently streaming virtualized applications.
-
-**Note**
-The actual time to it will take to stream is determined primarily by the number of clients streaming simultaneously, number of packages, package size, the server’s network activity, and network conditions.
-
-
-
-For example, an average user can stream a 100 MB package in less than 2 minutes, when 100 simultaneous clients are streaming from the server. However, a package of size 1 GB could take up to 30 minutes. In most real world environments streaming demand is not uniformly distributed, you will need to understand the approximate peak streaming requirements present in your environment in order to properly size the number of required streaming servers.
-
-The number of clients a streaming server can support can be significantly increased and the peak streaming requirements reduced if you pre-cache your applications. You can also increase the number of clients a streaming server can support by using on-demand streaming delivery and stream optimized packages.
-
-## Combining App-V 5.1 Server Roles
-
-
-Discounting scaling and fault-tolerance requirements, the minimum number of servers needed for a location with connectivity to Active Directory is one. This server will host the management server, management server service, and Microsoft SQL Server roles. Server roles, therefore, can be arranged in any desired combination since they do not conflict with one another.
-
-Ignoring scaling requirements, the minimum number of servers necessary to provide a fault-tolerant implementation is four. The management server, and Microsoft SQL Server roles support being placed in fault-tolerant configurations. The management server service can be combined with any of the roles, but remains a single point of failure.
-
-Although there are a number of fault-tolerance strategies and technologies available, not all are applicable to a given service. Additionally, if App-V 5.1 roles are combined, certain fault-tolerance options may no longer apply due to incompatibilities.
-
-
-
-
-
-
-## Related topics
-
-
-[App-V 5.1 Supported Configurations](app-v-51-supported-configurations.md)
-
-[Planning for High Availability with App-V 5.1](planning-for-high-availability-with-app-v-51.md)
-
-[Planning to Deploy App-V](planning-to-deploy-app-v51.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v5/app-v-51-deployment-checklist.md b/mdop/appv-v5/app-v-51-deployment-checklist.md
deleted file mode 100644
index 955988dde1..0000000000
--- a/mdop/appv-v5/app-v-51-deployment-checklist.md
+++ /dev/null
@@ -1,94 +0,0 @@
----
-title: App-V 5.1 Deployment Checklist
-description: App-V 5.1 Deployment Checklist
-author: dansimp
-ms.assetid: 44bed85a-e4f5-49d7-a308-a2b681f76372
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# App-V 5.1 Deployment Checklist
-
-
-This checklist can be used to help you during Microsoft Application Virtualization (App-V) 5.1 deployment.
-
-**Note**
-This checklist outlines the recommended steps and a high-level list of items to consider when deploying App-V 5.1 features. It is recommended that you copy this checklist into a spreadsheet program and customize it for your use.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Task
-
References
-
Notes
-
-
-
-
-
-
Complete the planning phase to prepare the computing environment for App-V 5.1 deployment.
Review the App-V 5.1 supported configurations information to make sure selected client and server computers are supported for App-V 5.1 feature installation.
Run App-V 5.1 Setup to deploy the required App-V 5.1 features for your environment.
-
-Note
Keep track of the names of the servers and associated URL’s created during installation. This information will be used throughout the installation process.
-
-
-
-
-
-
-
-
-## Related topics
-
-
-[Deploying App-V 5.1](deploying-app-v-51.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v5/app-v-51-planning-checklist.md b/mdop/appv-v5/app-v-51-planning-checklist.md
deleted file mode 100644
index e1f8ef66b6..0000000000
--- a/mdop/appv-v5/app-v-51-planning-checklist.md
+++ /dev/null
@@ -1,36 +0,0 @@
----
-title: App-V 5.1 Planning Checklist
-description: App-V 5.1 Planning Checklist
-author: dansimp
-ms.assetid: 1e26a861-0612-43a6-972f-375a40a8dcbc
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# App-V 5.1 Planning Checklist
-
-This checklist can be used to help you plan for preparing your computing environment for Microsoft Application Virtualization (App-V) 5.1 deployment.
-
-> [!NOTE]
-> This checklist outlines the recommended steps and a high-level list of items to consider when planning for an App-V 5.1 deployment. It is recommended that you copy this checklist into a spreadsheet program and customize it for your use.
-
-| |Task |References |
-|-|-|-|
-| |Review the getting started information about App-V 5.1 to gain a basic understanding of the product before beginning deployment planning.|[Getting Started with App-V 5.1](getting-started-with-app-v-51.md)|
-| |Plan for App-V 5.1 1.0 Deployment Prerequisites and prepare your computing environment.|[App-V 5.1 Prerequisites](app-v-51-prerequisites.md)|
-| |If you plan to use the App-V 5.1 management server, plan for the required roles.|[Planning for the App-V 5.1 Server Deployment](planning-for-the-app-v-51-server-deployment.md)|
-| |Plan for the App-V 5.1 sequencer and client so you to create and run virtualized applications.|[Planning for the App-V 5.1 Sequencer and Client Deployment](planning-for-the-app-v-51-sequencer-and-client-deployment.md)|
-| |If applicable, review the options and steps for migrating from a previous version of App-V.|[Planning for Migrating from a Previous Version of App-V](planning-for-migrating-from-a-previous-version-of-app-v51.md)|
-| |Plan for running App-V 5.1 clients using in shared content store mode.|[How to Install the App-V 5.1 Client for Shared Content Store Mode](how-to-install-the-app-v-51-client-for-shared-content-store-mode.md)|
-| | | |
-
-## Related topics
-
-[Planning for App-V 5.1](planning-for-app-v-51.md)
diff --git a/mdop/appv-v5/app-v-51-prerequisites.md b/mdop/appv-v5/app-v-51-prerequisites.md
deleted file mode 100644
index f9709263ec..0000000000
--- a/mdop/appv-v5/app-v-51-prerequisites.md
+++ /dev/null
@@ -1,665 +0,0 @@
----
-title: App-V 5.1 Prerequisites
-description: App-V 5.1 Prerequisites
-author: dansimp
-ms.assetid: 1bfa03c1-a4ae-45ec-8a2b-b10c2b94bfb0
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# App-V 5.1 Prerequisites
-
-
-Before installing Microsoft Application Virtualization (App-V) 5.1, ensure that you have installed all of the following required prerequisite software.
-
-For a list of supported operating systems and hardware requirements for the App-V Server, Sequencer, and Client, see [App-V 5.1 Supported Configurations](app-v-51-supported-configurations.md).
-
-## Summary of software preinstalled on each operating system
-
-
-The following table indicates the software that is already installed for different operating systems.
-
-
-
-
-
-
-
-
-
Operating system
-
Prerequisite description
-
-
-
-
-
Windows 10
-
All of the prerequisite software is already installed.
-
-
-
Windows 8.1
-
All of the prerequisite software is already installed.
-
-Note
If you are running Windows 8, upgrade to Windows 8.1 before using App-V 5.1.
-
-
-
-
-
-
-
Windows Server 2012
-
The following prerequisite software is already installed:
-
-
Microsoft .NET Framework 4.5
-
Windows PowerShell 3.0
-
-Note
Installing PowerShell 3.0 requires a restart.
-
-
-
-
-
-
-
-
Windows 7
-
The prerequisite software is not already installed. You must install it before you can install App-V.
-
-
-
-
-
-
-## App-V Server prerequisite software
-
-
-Install the required prerequisite software for the App-V 5.1 Server components.
-
-### What to know before you start
-
-
-
-
-
-
-
-
-
Account for installing the App-V Server
-
The account that you use to install the App-V Server components must have:
-
-
Administrative rights on the computer on which you are installing the components.
-
The ability to query Active Directory Domain Services.
-
-
-
-
Port and firewall
-
-
Specify a port where each component will be hosted.
-
Add the associated firewall rules to allow incoming requests to the specified ports.
-
-
-
-
-
Web Distributed Authoring and Versioning (WebDAV)
-
WebDAV is automatically disabled for the Management Service.
-
-
-
Supported deployment scenarios
-
-
A stand-alone deployment, where all components are deployed on the same server.
-
A distributed deployment.
-
-
-
-
Unsupported deployment scenarios
-
-
Installing side-by-side instances of multiple App-V Server versions on the same server.
-
Installing the App-V server components on a computer that runs server core or domain controller.
-
-
-
-
-
-
-
-### Management server prerequisite software
-
-
This role must be added to a server operating system that is supported for the Management server.
-
-
-
Web Server (IIS) Management Tools
-
Click IIS Management Scripts and Tools.
-
-
-
Web Server Role Services
-
Common HTTP Features:
-
-
Static Content
-
Default Document
-
-
Application Development:
-
-
ASP.NET
-
.NET Extensibility
-
ISAPI Extensions
-
ISAPI Filters
-
-
Security:
-
-
Windows Authentication
-
Request Filtering
-
-
Management Tools:
-
-
IIS Management Console
-
-
-
-
Default installation location
-
%PROGRAMFILES%\Microsoft Application Virtualization Server
-
-
-
Location of the Management database
-
SQL Server database name, SQL Server database instance name, and database name.
-
-
-
Management console and Management database permissions
-
A user or group that can access the Management console and database after the deployment is complete. Only these users or groups will have access to the Management console and database unless additional administrators are added by using the Management console.
-
-
-
Management service website name
-
Name for the Management console website.
-
-
-
Management service port binding
-
Unique port number for the Management service. This port cannot be used by another process on the computer.
-
-
-
-
-
-
-**Important**
-JavaScript must be enabled on the browser that opens the Web Management Console.
-
-
-
-### Management server database prerequisite software
-
-The Management database is required only if you are using the App-V 5.1 Management server.
-
-
This role must be added to a server operating system that is supported for the Management server.
-
-
-
Web Server (IIS) Management Tools
-
Click IIS Management Scripts and Tools.
-
-
-
Web Server Role Services
-
To reduce the risk of unwanted or malicious data being sent to the Reporting server, you should restrict access to the Reporting Web Service per your corporate security policy.
-
Common HTTP Features:
-
-
Static Content
-
Default Document
-
-
Application Development:
-
-
ASP.NET
-
.NET Extensibility
-
ISAPI Extensions
-
ISAPI Filters
-
-
Security:
-
-
Windows Authentication
-
Request Filtering
-
-
Management Tools:
-
-
IIS Management Console
-
-
-
-
Default installation location
-
%PROGRAMFILES%\Microsoft Application Virtualization Server
-
-
-
Reporting service website name
-
Name for the Reporting website.
-
-
-
Reporting service port binding
-
Unique port number for the Reporting service. This port cannot be used by another process on the computer.
-
-
-
-
-
-
-### Reporting database prerequisite software
-
-The Reporting database is required only if you are using the App-V 5.1 Reporting server.
-
-
-
-
-
-## Sequencer prerequisite software
-
-
-**What to know before installing the prerequisites:**
-
-- Best practice: The computer that runs the Sequencer should have the same hardware and software configurations as the computers that will run the virtual applications.
-
-- The sequencing process is resource intensive, so make sure that the computer that runs the Sequencer has plenty of memory, a fast processor, and a fast hard drive. The system requirements of locally installed applications cannot exceed those of the Sequencer. For more information, see [App-V 5.1 Supported Configurations](app-v-51-supported-configurations.md).
-
-
Applies to Windows 7 only: Download and install the KB.
-
-
-
-
-
-
-
-
-
-
-
-## Related topics
-
-
-[Planning for App-V 5.1](planning-for-app-v-51.md)
-
-[App-V 5.1 Supported Configurations](app-v-51-supported-configurations.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v5/app-v-51-security-considerations.md b/mdop/appv-v5/app-v-51-security-considerations.md
deleted file mode 100644
index cf442e5690..0000000000
--- a/mdop/appv-v5/app-v-51-security-considerations.md
+++ /dev/null
@@ -1,147 +0,0 @@
----
-title: App-V 5.1 Security Considerations
-description: App-V 5.1 Security Considerations
-author: dansimp
-ms.assetid: 6bc6c1fc-f813-47d4-b763-06fd4faf6a72
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 08/30/2016
----
-
-
-# App-V 5.1 Security Considerations
-
-
-This topic contains a brief overview of the accounts and groups, log files, and other security-related considerations for Microsoft Application Virtualization (App-V) 5.1.
-
-**Important**
-App-V 5.1 is not a security product and does not provide any guarantees for a secure environment.
-
-
-
-## PackageStoreAccessControl (PSAC) feature has been deprecated
-
-
-Effective as of June, 2014, the PackageStoreAccessControl (PSAC) feature that was introduced in Microsoft Application Virtualization (App-V) 5.0 Service Pack 2 (SP2) has been deprecated in both single-user and multi-user environments.
-
-## General security considerations
-
-
-**Understand the security risks.** The most serious risk to App-V 5.1 is that its functionality could be hijacked by an unauthorized user who could then reconfigure key data on App-V 5.1 clients. The loss of App-V 5.1 functionality for a short period of time due to a denial-of-service attack would not generally have a catastrophic impact.
-
-**Physically secure your computers**. Security is incomplete without physical security. Anyone with physical access to an App-V 5.1 server could potentially attack the entire client base. Any potential physical attacks must be considered high risk and mitigated appropriately. App-V 5.1 servers should be stored in a physically secure server room with controlled access. Secure these computers when administrators are not physically present by having the operating system lock the computer, or by using a secured screen saver.
-
-**Apply the most recent security updates to all computers**. To stay informed about the latest updates for operating systems, Microsoft SQL Server, and App-V 5.1, subscribe to the Security Notification service ().
-
-**Use strong passwords or pass phrases**. Always use strong passwords with 15 or more characters for all App-V 5.1 and App-V 5.1 administrator accounts. Never use blank passwords. For more information about password concepts, see the “Account Passwords and Policies” white paper on TechNet ().
-
-## Accounts and groups in App-V 5.1
-
-
-A best practice for user account management is to create domain global groups and add user accounts to them. Then, add the domain global accounts to the necessary App-V 5.1 local groups on the App-V 5.1 servers.
-
-**Note**
-App-V client computer accounts that need to connect to the publishing server must be part of the publishing server’s **Users** local group. By default, all computers in the domain are part of the **Authorized Users** group, which is part of the **Users** local group.
-
-
-
-### App-V 5.1 server security
-
-No groups are created automatically during App-V 5.1 Setup. You should create the following Active Directory Domain Services global groups to manage App-V 5.1 server operations.
-
-
-
-
-
-
-
-
-
Group name
-
Details
-
-
-
-
-
App-V Management Admin group
-
Used to manage the App-V 5.1 management server. This group is created during the App-V 5.1 Management Server installation.
-
-Important
There is no method to create the group using the management console after you have completed the installation.
-
-
-
-
-
-
-
Database read/write for Management Service account
-
Provides read/write access to the management database. This account should be created during the App-V 5.1 management database installation.
-
-
-
App-V Management Service install admin account
-
-Note
This is only required if management database is being installed separately from the service.
-
-
-
-
-
Provides public access to schema-version table in management database. This account should be created during the App-V 5.1 management database installation.
-
-
-
App-V Reporting Service install admin account
-
-Note
This is only required if reporting database is being installed separately from the service.
-
-
-
-
-
Public access to schema-version table in reporting database. This account should be created during the App-V 5.1 reporting database installation.
-
-
-
-
-
-
-Consider the following additional information:
-
-- Access to the package shares - If a share exists on the same computer as the management Server, the **Network** service requires read access to the share. In addition, each App-V client computer must have read access to the package share.
-
- **Note**
- In previous versions of App-V, package share was referred to as content share.
-
-
-
-- Registering publishing servers with Management Server - A publishing server must be registered with the Management server. For example, it must be added to the database, so that the Publishing server machine accounts are able to call into the Management service API.
-
-### App-V 5.1 package security
-
-The following will help you plan how to ensure that virtualized packages are secure.
-
-- If an application installer applies an access control list (ACL) to a file or directory, then that ACL is not persisted in the package. When the package is deployed, if the file or directory is modified by a user it will either inherit the ACL in the **%userprofile%** or inherit the ACL of the target computer’s directory. The former case occurs if the file or directory does not exist in a virtual file system location; the latter case occurs if the file or directory exists in a virtual file system location, for example **%windir%**.
-
-## App-V 5.1 log files
-
-
-During App-V 5.1 Setup, setup log files are created in the **%temp%** folder of the installing user.
-
-
-
-
-
-
-## Related topics
-
-
-[Preparing Your Environment for App-V 5.1](preparing-your-environment-for-app-v-51.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v5/app-v-51-supported-configurations.md b/mdop/appv-v5/app-v-51-supported-configurations.md
deleted file mode 100644
index 7785be89ee..0000000000
--- a/mdop/appv-v5/app-v-51-supported-configurations.md
+++ /dev/null
@@ -1,551 +0,0 @@
----
-title: App-V 5.1 Supported Configurations
-description: App-V 5.1 Supported Configurations
-author: dansimp
-ms.assetid: 8b8db63b-f71c-4ae9-80e7-a6752334e1f6
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 04/02/2020
----
-
-
-# App-V 5.1 Supported Configurations
-
-This topic specifies the requirements to install and run Microsoft Application Virtualization (App-V) 5.1 in your environment.
-
-## App-V Server system requirements
-
-This section lists the operating system and hardware requirements for all of the App-V Server components.
-
-### Unsupported App-V 5.1 Server scenarios
-
-The App-V 5.1 Server does not support the following scenarios:
-
-- Deployment to a computer that runs Microsoft Windows Server Core.
-
-- Deployment to a computer that runs a previous version of App-V 5.1 Server components. You can install App-V 5.1 side by side with the App-V 4.5 Lightweight Streaming Server (LWS) server only. Deployment of App-V side by side with the App-V 4.5 Application Virtualization Management Service (HWS) server is not supported.
-
-- Deployment to a computer that runs Microsoft SQL Server Express edition.
-
-- Deployment to a domain controller.
-
-- Short paths. If you plan to use a short path, you must create a new volume.
-
-### Management server operating system requirements
-
-The following table lists the operating systems that are supported for the App-V 5.1 Management server installation.
-
-**Note**
-Microsoft provides support for the current service pack and, in some cases, the immediately preceding service pack. To find the support timelines for your product, see the [Lifecycle Supported Service Packs](https://go.microsoft.com/fwlink/p/?LinkId=31975). See [Microsoft Support Lifecycle Support Policy FAQ](https://go.microsoft.com/fwlink/p/?LinkId=31976) for more information.
-
-
-
-
-
-
-
-
-
-
-
-
Operating system
-
Service Pack
-
System architecture
-
-
-
-
-
Microsoft Windows Server 2016
-
-
64-bit
-
-
-
Microsoft Windows Server 2012 R2
-
-
64-bit
-
-
-
Microsoft Windows Server 2012
-
-
64-bit
-
-
-
Microsoft Windows Server 2008 R2
-
SP1
-
64-bit
-
-
-
-
-
-
-**Important**
-Deployment of the Management server role to a computer with Remote Desktop Sharing (RDS) enabled is not supported.
-
-
-
-### Management server hardware requirements
-
-- Processor—1.4 GHz or faster, 64-bit (x64) processor
-
-- RAM—1 GB RAM (64-bit)
-
-- Disk space—200 MB available hard disk space, not including the content directory
-
-### Management server database requirements
-
-The following table lists the SQL Server versions that are supported for the App-V 5.1 Management database installation.
-
-
-
-
-
-
-
-
-
-
SQL Server version
-
Service pack
-
System architecture
-
-
-
-
-
Microsoft SQL Server 2019
-
-
32-bit or 64-bit
-
-
-
-
Microsoft SQL Server 2017
-
-
32-bit or 64-bit
-
-
-
Microsoft SQL Server 2016
-
SP2
-
32-bit or 64-bit
-
-
-
Microsoft SQL Server 2014
-
SP2
-
32-bit or 64-bit
-
-
-
Microsoft SQL Server 2012
-
SP2
-
32-bit or 64-bit
-
-
-
Microsoft SQL Server 2008 R2
-
SP3
-
32-bit or 64-bit
-
-
-
-
-For more information on user configuration files with SQL server 2016 or later, see the [support article](https://support.microsoft.com/help/4548751/app-v-server-publishing-might-fail-when-you-apply-user-configuration-f).
-
-### Publishing server operating system requirements
-
-The following table lists the operating systems that are supported for the App-V 5.1 Publishing server installation.
-
-
-
-
-
-
-
-
-
-
Operating system
-
Service Pack
-
System architecture
-
-
-
-
-
Microsoft Windows Server 2016
-
-
64-bit
-
-
-
Microsoft Windows Server 2012 R2
-
-
64-bit
-
-
-
Microsoft Windows Server 2012
-
-
64-bit
-
-
-
Microsoft Windows Server 2008 R2
-
SP1
-
64-bit
-
-
-
-
-
-
-### Publishing server hardware requirements
-
-App-V adds no additional requirements beyond those of Windows Server.
-
-- Processor—1.4 GHz or faster, 64-bit (x64) processor
-
-- RAM—2 GB RAM (64-bit)
-
-- Disk space—200 MB available hard disk space, not including the content directory
-
-### Reporting server operating system requirements
-
-The following table lists the operating systems that are supported for the App-V 5.1 Reporting server installation.
-
-
-
-
-
-
-
-
-
-
Operating system
-
Service Pack
-
System architecture
-
-
-
-
-
Microsoft Windows Server 2016
-
-
64-bit
-
-
-
Microsoft Windows Server 2012 R2
-
-
64-bit
-
-
-
Microsoft Windows Server 2012
-
-
64-bit
-
-
-
Microsoft Windows Server 2008 R2
-
SP1
-
64-bit
-
-
-
-
-
-
-### Reporting server hardware requirements
-
-App-V adds no additional requirements beyond those of Windows Server.
-
-- Processor—1.4 GHz or faster, 64-bit (x64) processor
-
-- RAM—2 GB RAM (64-bit)
-
-- Disk space—200 MB available hard disk space
-
-### Reporting server database requirements
-
-The following table lists the SQL Server versions that are supported for the App-V 5.1 Reporting database installation.
-
-
-
-
-
-
-
-
-
-
SQL Server version
-
Service pack
-
System architecture
-
-
-
-
-
Microsoft SQL Server 2017
-
-
32-bit or 64-bit
-
-
-
Microsoft SQL Server 2016
-
SP2
-
32-bit or 64-bit
-
-
-
Microsoft SQL Server 2014
-
SP2
-
32-bit or 64-bit
-
-
-
Microsoft SQL Server 2012
-
SP2
-
32-bit or 64-bit
-
-
-
Microsoft SQL Server 2008 R2
-
SP3
-
32-bit or 64-bit
-
-
-
-
-
-
-## App-V client system requirements
-
-The following table lists the operating systems that are supported for the App-V 5.1 client installation.
-
-**Note:** With the Windows 10 Anniversary release (aka 1607 version), the App-V client is in-box and will block installation of any previous version of the App-V client
-
-
-
-
-
-
-
-
-
-
Operating system
-
Service pack
-
System architecture
-
-
-
-
-
Microsoft Windows 10 (pre-1607 version)
-
-
32-bit or 64-bit
-
-
-
Microsoft Windows 8.1
-
-
32-bit or 64-bit
-
-
-
Windows 7
-
SP1
-
32-bit or 64-bit
-
-
-
-
-
-
-The following App-V client installation scenarios are not supported, except as noted:
-
-- Computers that run Windows Server
-
-- Computers that run App-V 4.6 SP1 or earlier versions
-
-- The App-V 5.1 Remote Desktop services client is supported only for RDS-enabled servers
-
-### App-V client hardware requirements
-
-The following list displays the supported hardware configuration for the App-V 5.1 client installation.
-
-- Processor— 1.4 GHz or faster 32-bit (x86) or 64-bit (x64) processor
-
-- RAM— 1 GB (32-bit) or 2 GB (64-bit)
-
-- Disk— 100 MB for installation, not including the disk space that is used by virtualized applications.
-
-## Remote Desktop Services client system requirements
-
-
-The following table lists the operating systems that are supported for App-V 5.1 Remote Desktop Services (RDS) client installation.
-
-
-
-
-
-
-
-
-
-
Operating system
-
Service Pack
-
System architecture
-
-
-
-
-
Microsoft Windows Server 2016
-
-
64-bit
-
-
-
Microsoft Windows Server 2012 R2
-
-
64-bit
-
-
-
Microsoft Windows Server 2012
-
-
64-bit
-
-
-
Microsoft Windows Server 2008 R2
-
SP1
-
64-bit
-
-
-
-
-
-
-### Remote Desktop Services client hardware requirements
-
-App-V adds no additional requirements beyond those of Windows Server.
-
-- Processor—1.4 GHz or faster, 64-bit (x64) processor
-
-- RAM—2 GB RAM (64-bit)
-
-- Disk space—200 MB available hard disk space
-
-## Sequencer system requirements
-
-The following table lists the operating systems that are supported for the App-V 5.1 Sequencer installation.
-
-
-
-
-
-
-
-
-
-
Operating system
-
Service pack
-
System architecture
-
-
-
-
-
Microsoft Windows Server 2016
-
-
64-bit
-
-
-
Microsoft Windows Server 2012 R2
-
-
64-bit
-
-
-
Microsoft Windows Server 2012
-
-
64-bit
-
-
-
Microsoft Windows Server 2008 R2
-
SP1
-
64-bit
-
-
-
Microsoft Windows 10
-
-
32-bit and 64-bit
-
-
-
Microsoft Windows 8.1
-
-
32-bit and 64-bit
-
-
-
Microsoft Windows 7
-
SP1
-
32-bit and 64-bit
-
-
-
-
-
-
-### Sequencer hardware requirements
-
-See the Windows or Windows Server documentation for the hardware requirements. App-V adds no additional hardware requirements.
-
-## Supported versions of System Center Configuration Manager
-
-The App-V client supports the following versions of System Center Configuration Manager:
-
-- Microsoft System Center 2012 Configuration Manager
-
-- System Center 2012 R2 Configuration Manager
-
-- System Center 2012 R2 Configuration Manager SP1
-
-The following App-V and System Center Configuration Manager version matrix shows all officially supported combinations of App-V and Configuration Manager.
-
-**Note:** Both App-V 4.5 and 4.6 have exited Mainstream support.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
App-V Version
-
System Center Configuration Manager 2007
-
System Center 2012 Configuration Manager
-
System Center 2012 Configuration Manager SP1
-
System Center 2012 R2 Configuration Manager
-
System Center 2012 R2 Configuration Manager SP1
-
System Center 2012 Configuration Manager SP2
-
System Center Configuration Manager Version 1511
-
-
-
-
-
App-V 5.0 SP3
-
MSI-Wrapper Only
-
No
-
2012 SP1 CU4
-
2012 R2 CU1
-
Yes
-
Yes
-
Yes
-
-
-
App-V 5.1
-
MSI-Wrapper Only
-
No
-
2012 SP1 CU4
-
2012 R2 CU1
-
Yes
-
Yes
-
Yes
-
-
-
-
-
-
-For more information about how Configuration Manager integrates with App-V, see [Planning for App-V Integration with Configuration Manager](https://technet.microsoft.com/library/jj822982.aspx).
-
-## Related topics
-
-[Planning to Deploy App-V](planning-to-deploy-app-v51.md)
-
-[App-V 5.1 Prerequisites](app-v-51-prerequisites.md)
diff --git a/mdop/appv-v5/application-publishing-and-client-interaction.md b/mdop/appv-v5/application-publishing-and-client-interaction.md
deleted file mode 100644
index 6c060982f7..0000000000
--- a/mdop/appv-v5/application-publishing-and-client-interaction.md
+++ /dev/null
@@ -1,1635 +0,0 @@
----
-title: Application Publishing and Client Interaction
-description: Application Publishing and Client Interaction
-author: dansimp
-ms.assetid: c69a724a-85d1-4e2d-94a2-7ffe0b47d971
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 08/30/2016
----
-
-
-# Application Publishing and Client Interaction
-
-
-This article provides technical information about common App-V client operations and their integration with the local operating system.
-
-- [App-V package files created by the Sequencer](#bkmk-appv-pkg-files-list)
-
-- [What’s in the appv file?](#bkmk-appv-file-contents)
-
-- [App-V client data storage locations](#bkmk-files-data-storage)
-
-- [Package registry](#bkmk-pkg-registry)
-
-- [App-V package store behavior](#bkmk-pkg-store-behavior)
-
-- [Roaming registry and data](#bkmk-roaming-reg-data)
-
-- [App-V client application lifecycle management](#bkmk-clt-app-lifecycle)
-
-- [Integration of App-V packages](#bkmk-integr-appv-pkgs)
-
-- [Dynamic configuration processing](#bkmk-dynamic-config)
-
-- [Side-by-side assemblies](#bkmk-sidebyside-assemblies)
-
-- [Client logging](#bkmk-client-logging)
-
-For additional reference information, see [Microsoft Application Virtualization (App-V) Documentation Resources Download Page](https://www.microsoft.com/download/details.aspx?id=27760).
-
-## App-V package files created by the Sequencer
-
-
-The Sequencer creates App-V packages and produces a virtualized application. The sequencing process creates the following files:
-
-
-
-
-
-
-
-
-
File
-
Description
-
-
-
-
-
.appv
-
-
The primary package file, which contains the captured assets and state information from the sequencing process.
-
Architecture of the package file, publishing information, and registry in a tokenized form that can be reapplied to a machine and to a specific user upon delivery.
-
-
-
-
.MSI
-
Executable deployment wrapper that you can use to deploy .appv files manually or by using a third-party deployment platform.
-
-
-
_DeploymentConfig.XML
-
File used to customize the default publishing parameters for all applications in a package that is deployed globally to all users on a computer that is running the App-V client.
-
-
-
_UserConfig.XML
-
File used to customize the publishing parameters for all applications in a package that is a deployed to a specific user on a computer that is running the App-V client.
-
-
-
Report.xml
-
Summary of messages resulting from the sequencing process, including omitted drivers, files, and registry locations.
-
-
-
.CAB
-
Optional: Package accelerator file used to automatically rebuild a previously sequenced virtual application package.
-
-
-
.appvt
-
Optional: Sequencer template file used to retain commonly reused Sequencer settings.
-
-
-
-
-
-
-For information about sequencing, see [Application Virtualization 5.0 Sequencing Guide](https://www.microsoft.com/download/details.aspx?id=27760).
-
-## What’s in the appv file?
-
-
-The appv file is a container that stores XML and non-XML files together in a single entity. This file is built from the AppX format, which is based on the Open Packaging Conventions (OPC) standard.
-
-To view the appv file contents, make a copy of the package, and then rename the copied file to a ZIP extension.
-
-The appv file contains the following folder and files, which are used when creating and publishing a virtual application:
-
-
-
-
-
-
-
-
-
-
Name
-
Type
-
Description
-
-
-
-
-
Root
-
File folder
-
Directory that contains the file system for the virtualized application that is captured during sequencing.
-
-
-
[Content_Types].xml
-
XML File
-
List of the core content types in the appv file (e.g. DLL, EXE, BIN).
-
-
-
AppxBlockMap.xml
-
XML File
-
Layout of the appv file, which uses File, Block, and BlockMap elements that enable location and validation of files in the App-V package.
-
-
-
AppxManifest.xml
-
XML File
-
Metadata for the package that contains the required information for adding, publishing, and launching the package. Includes extension points (file type associations and shortcuts) and the names and GUIDs associated with the package.
-
-
-
FilesystemMetadata.xml
-
XML File
-
List of the files captured during sequencing, including attributes (e.g., directories, files, opaque directories, empty directories,and long and short names).
-
-
-
PackageHistory.xml
-
XML File
-
Information about the sequencing computer (operating system version, Internet Explorer version, .Net Framework version) and process (upgrade, package version).
-
-
-
Registry.dat
-
DAT File
-
Registry keys and values captured during the sequencing process for the package.
-
-
-
StreamMap.xml
-
XML File
-
List of files for the primary and publishing feature block. The publishing feature block contains the ICO files and required portions of files (EXE and DLL) for publishing the package. When present, the primary feature block includes files that have been optimized for streaming during the sequencing process.
-
-
-
-
-
-
-## App-V client data storage locations
-
-
-The App-V client performs tasks to ensure that virtual applications run properly and work like locally installed applications. The process of opening and running virtual applications requires mapping from the virtual file system and registry to ensure the application has the required components of a traditional application expected by users. This section describes the assets that are required to run virtual applications and lists the location where App-V stores the assets.
-
-
Stores previous integration points that enable restore on package unpublish
-
-
-
Copy on Write (COW) Roaming
-
%AppData%\Microsoft\AppV\Client\VFS
-
Writeable roaming location for package modification
-
-
-
Copy on Write (COW) Local
-
%LocalAppData%\Microsoft\AppV\Client\VFS
-
Writeable non-roaming location for package modification
-
-
-
Machine Registry
-
HKLM\Software\Microsoft\AppV
-
Contains package state information, including VReg for machine or globally published packages (Machine hive)
-
-
-
User Registry
-
HKCU\Software\Microsoft\AppV
-
Contains user package state information including VReg
-
-
-
User Registry Classes
-
HKCU\Software\Classes\AppV
-
Contains additional user package state information
-
-
-
-
-
-
-Additional details for the table are provided in the section below and throughout the document.
-
-### Package store
-
-The App-V Client manages the applications assets mounted in the package store. This default storage location is `%ProgramData%\App-V`, but you can configure it during or after setup by using the `Set-AppVClientConfiguration` PowerShell command, which modifies the local registry (`PackageInstallationRoot` value under the `HKLM\Software\Microsoft\AppV\Client\Streaming` key). The package store must be located at a local path on the client operating system. The individual packages are stored in the package store in subdirectories named for the Package GUID and Version GUID.
-
-Example of a path to a specific application:
-
-``` syntax
-C:\ProgramData\App-V\PackGUID\VersionGUID
-```
-
-To change the default location of the package store during setup, see [How to Deploy the App-V Client](how-to-deploy-the-app-v-client-gb18030.md).
-
-### Shared Content Store
-
-If the App-V Client is configured in Shared Content Store mode, no data is written to disk when a stream fault occurs, which means that the packages require minimal local disk space (publishing data). The use of less disk space is highly desirable in VDI environments, where local storage can be limited, and streaming the applications from a high performance network location (such as a SAN) is preferable. For more information on shared content store mode, see .
-
-**Note**
-The machine and package store must be located on a local drive, even when you’re using Shared Content Store configurations for the App-V Client.
-
-
-
-### Package catalogs
-
-The App-V Client manages the following two file-based locations:
-
-- **Catalogs (user and machine).**
-
-- **Registry locations** - depends on how the package is targeted for publishing. There is a Catalog (data store) for the computer, and a catalog for each individual user. The Machine Catalog stores global information applicable to all users or any user, and the User Catalog stores information applicable to a specific user. The Catalog is a collection of Dynamic Configurations and manifest files; there is discrete data for both file and registry per package version.
-
-### Machine catalog
-
-
-
-
-
-
-
-
-
Description
-
Stores package documents that are available to users on the machine, when packages are added and published. However, if a package is “global” at publishing time, the integrations are available to all users.
-
If a package is non-global, the integrations are published only for specific users, but there are still global resources that are modified and visible to anyone on the client computer (e.g., the package directory is in a shared disk location).
-
If a package is available to a user on the computer (global or non-global), the manifest is stored in the Machine Catalog. When a package is published globally, there is a Dynamic Configuration file, stored in the Machine Catalog; therefore, the determination of whether a package is global is defined according to whether there is a policy file (UserDeploymentConfiguration file) in the Machine Catalog.
Additional files in the machine catalog when the package is part of a connection group
-
-
PackageGroupDescriptor.xml
-
UserPackageGroupDescriptor.xml (globally published Connection Group)
-
-
-
-
-
-
-
-### User catalog
-
-
-
-
-
-
-
-
-
Description
-
Created during the publishing process. Contains information used for publishing the package, and also used at launch to ensure that a package is provisioned to a specific user. Created in a roaming location and includes user-specific publishing information.
-
When a package is published for a user, the policy file is stored in the User Catalog. At the same time, a copy of the manifest is also stored in the User Catalog. When a package entitlement is removed for a user, the relevant package files are removed from the User Catalog. Looking at the user catalog, an administrator can view the presence of a Dynamic Configuration file, which indicates that the package is entitled for that user.
-
For roaming users, the User Catalog needs to be in a roaming or shared location to preserve the legacy App-V behavior of targeting users by default. Entitlement and policy are tied to a user, not a computer, so they should roam with the user once they are provisioned.
Additional file in the machine catalog when the package is part of a connection group
-
UserPackageGroupDescriptor.xml
-
-
-
-
-
-
-### Shortcut backups
-
-During the publishing process, the App-V Client backs up any shortcuts and integration points to `%AppData%\Microsoft\AppV\Client\Integration\ShortCutBackups.` This backup enables the restoration of these integration points to the previous versions when the package is unpublished.
-
-### Copy on Write files
-
-The Package Store contains a pristine copy of the package files that have been streamed from the publishing server. During normal operation of an App-V application, the user or service may require changes to the files. These changes are not made in the package store in order to preserve your ability to repair the application, which removes these changes. These locations, called Copy on Write (COW), support both roaming and non-roaming locations. The location where the modifications are stored depends where the application has been programmed to write changes to in a native experience.
-
-### COW roaming
-
-The COW Roaming location described above stores changes to files and directories that are targeted to the typical %AppData% location or \\Users\\{username}\\AppData\\Roaming location. These directories and files are then roamed based on the operating system settings.
-
-### COW local
-
-The COW Local location is similar to the roaming location, but the directories and files are not roamed to other computers, even if roaming support has been configured. The COW Local location described above stores changes applicable to typical windows and not the %AppData% location. The directories listed will vary but there will be two locations for any typical Windows locations (e.g. Common AppData and Common AppDataS). The **S** signifies the restricted location when the virtual service requests the change as a different elevated user from the logged on users. The non-**S** location stores user based changes.
-
-## Package registry
-
-
-Before an application can access the package registry data, the App-V Client must make the package registry data available to the applications. The App-V Client uses the real registry as a backing store for all registry data.
-
-When a new package is added to the App-V Client, a copy of the REGISTRY.DAT file from the package is created at `%ProgramData%\Microsoft\AppV\Client\VREG\{Version GUID}.dat`. The name of the file is the version GUID with the .DAT extension. The reason this copy is made is to ensure that the actual hive file in the package is never in use, which would prevent the removal of the package at a later time.
-
-
-
-
-
-When the first application from the package is launched on the client, the client stages or copies the contents out of the hive file, re-creating the package registry data in an alternate location `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\AppV\Client\Packages\PackageGuid\Versions\VersionGuid\REGISTRY`. The staged registry data has two distinct types of machine data and user data. Machine data is shared across all users on the machine. User data is staged for each user to a userspecific location `HKCU\Software\Microsoft\AppV\Client\Packages\PackageGuid\Registry\User`. The machine data is ultimately removed at package removal time, and the user data is removed on a user unpublish operation.
-
-### Package registry staging vs. connection group registry staging
-
-When connection groups are present, the previous process of staging the registry holds true, but instead of having one hive file to process, there are more than one. The files are processed in the order in which they appear in the connection group XML, with the first writer winning any conflicts.
-
-The staged registry persists the same way as in the single package case. Staged user registry data remains for the connection group until it is disabled; staged machine registry data is removed on connection group removal.
-
-### Virtual registry
-
-The purpose of the virtual registry (VREG) is to provide a single merged view of the package registry and the native registry to applications. It also provides copy-on-write (COW) functionality – that is any changes made to the registry from the context of a virtual process are made to a separate COW location. This means that the VREG must combine up to three separate registry locations into a single view based on the populated locations in the registry COW -> package -> native. When a request is made for a registry data it will locate in order until it finds the data it was requesting. Meaning if there is a value stored in a COW location it will not proceed to other locations, however, if there is no data in the COW location it will proceed to the Package and then Native location until it finds the appropriate data.
-
-### Registry locations
-
-There are two package registry locations and two connection group locations where the App-V Client stores registry information, depending on whether the Package is published individually or as part of a connection group. There are three COW locations for packages and three for connection groups, which are created and managed by the VREG. Settings for packages and connection groups are not shared:
-
-**Single Package VReg:**
-
-
-
-
-
-
-
-
-
Location
-
Description
-
-
-
COW
-
-
Machine Registry\Client\Packages\PkgGUID\REGISTRY (Only elevate process can write)
-
User Registry\Client\Packages\PkgGUID\REGISTRY (User Roaming anything written under HKCU except Software\Classes
-
User Registry Classes\Client\Packages\PkgGUID\REGISTRY (HKCU\Software\Classes writes and HKLM for non elevated process)
User Registry Classes\Client\PackageGroups\GrpGUID\Versions\VerGUID\REGISTRY
-
-
-
-
Native
-
-
Native application registry location
-
-
-
-
-
-
-
-
-
-There are two COW locations for HKLM; elevated and non-elevated processes. Elevated processes always write HKLM changes to the secure COW under HKLM. Non-elevated processes always write HKLM changes to the non-secure COW under HKCU\\Software\\Classes. When an application reads changes from HKLM, elevated processes will read changes from the secure COW under HKLM. Non-elevated reads from both, favoring the changes made in the unsecure COW first.
-
-### Pass-through keys
-
-Pass-through keys enable an administrator to configure certain keys so they can only be read from the native registry, bypassing the Package and COW locations. Pass-through locations are global to the machine (not package specific) and can be configured by adding the path to the key, which should be treated as pass-through to the **REG\_MULTI\_SZ** value called **PassThroughPaths** of the key `HKLM\Software\Microsoft\AppV\Subsystem\VirtualRegistry`. Any key that appears under this multi-string value (and their children) will be treated as pass-through.
-
-The following locations are configured as pass-through locations by default:
-
-- HKEY\_CURRENT\_USER\\SOFTWARE\\Classes\\Local Settings\\Software\\Microsoft\\Windows\\CurrentVersion\\AppModel
-
-- HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Classes\\Local Settings\\Software\\Microsoft\\Windows\\CurrentVersion\\AppModel
-
-- HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\WINEVT
-
-- HKEY\_LOCAL\_MACHINE\\SYSTEM\\CurrentControlSet\\services\\eventlog\\Application
-
-- HKEY\_LOCAL\_MACHINE\\SYSTEM\\CurrentControlSet\\Control\\WMI\\Autologger
-
-- HKEY\_CURRENT\_USER\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Internet Settings
-
-- HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\Perflib
-
-- HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Policies
-
-- HKEY\_CURRENT\_USER\\SOFTWARE\\Policies
-
-The purpose of Pass-through keys is to ensure that a virtual application does not write registry data in the VReg that is required for non-virtual applications for successful operation or integration. The Policies key ensures that Group Policy based settings set by the administrator are utilized and not per package settings. The AppModel key is required for integration with Windows Modern UI based applications. It is recommend that administers do not modify any of the default pass-through keys, but in some instances, based on application behavior may require adding additional pass-through keys.
-
-## App-V package store behavior
-
-
-App-V 5 manages the Package Store, which is the location where the expanded asset files from the appv file are stored. By default, this location is stored at %ProgramData%\\App-V, and is limited in terms of storage capabilities only by free disk space. The package store is organized by the GUIDs for the package and version as mentioned in the previous section.
-
-### Add packages
-
-App-V Packages are staged upon addition to the computer with the App-V Client. The App-V Client provides on-demand staging. During publishing or a manual Add-AppVClientPackage, the data structure is built in the package store (c:\\programdata\\App-V\\{PkgGUID}\\{VerGUID}). The package files identified in the publishing block defined in the StreamMap.xml are added to the system and the top level folders and child files staged to ensure proper application assets exist at launch.
-
-### Mounting packages
-
-Packages can be explicitly loaded using the PowerShell `Mount-AppVClientPackage` or by using the **App-V Client UI** to download a package. This operation completely loads the entire package into the package store.
-
-### Streaming packages
-
-The App-V Client can be configured to change the default behavior of streaming. All streaming policies are stored under the following registry key: `HKEY_LOCAL_MAcHINE\Software\Microsoft\AppV\Client\Streaming`. Policies are set using the PowerShell cmdlet `Set-AppvClientConfiguration`. The following policies apply to Streaming:
-
-
-
-
-
-
-
-
-
Policy
-
Description
-
-
-
-
-
AllowHighCostLaunch
-
On Windows 8 it allows streaming over 3G and cellular networks
-
-
-
AutoLoad
-
Specifies the Background Load setting:
-
0 - Disabled
-
1 – Previously Used Packages only
-
2 – All Packages
-
-
-
PackageInstallationRoot
-
The root folder for the package store in the local machine
-
-
-
PackageSourceRoot
-
The root override where packages should be streamed from
-
-
-
SharedContentStoreMode
-
Enables the use of Shared Content Store for VDI scenarios
-
-
-
-
-
-
-
-
-These settings affect the behavior of streaming App-V package assets to the client. By default, App-V only downloads the assets required after downloading the initial publishing and primary feature blocks. There are three specific behaviors around streaming packages that must be explained:
-
-- Background Streaming
-
-- Optimized Streaming
-
-- Stream Faults
-
-### Background streaming
-
-The PowerShell cmdlet `Get-AppvClientConfiguration` can be used to determine the current mode for background streaming with the AutoLoad setting and modified with the cmdlet Set-AppvClientConfiguration or from the registry (HKLM\\SOFTWARE\\Microsoft\\AppV\\ClientStreaming key). Background streaming is a default setting where the Autoload setting is set to download previously used packages. The behavior based on default setting (value=1) downloads App-V data blocks in the background after the application has been launched. This setting can be disabled all together (value=0) or enabled for all packages (value=2), whether they have been launched.
-
-### Optimized streaming
-
-App-V packages can be configured with a primary feature block during sequencing. This setting allows the sequencing engineer to monitor launch files for a specific application, or applications, and mark the blocks of data in the App-V package for streaming at first launch of any application in the package.
-
-### Stream faults
-
-After the initial stream of any publishing data and the primary feature block, requests for additional files perform stream faults. These blocks of data are downloaded to the package store on an as-needed basis. This allows a user to download only a small part of the package, typically enough to launch the package and run normal tasks. All other blocks are downloaded when a user initiates an operation that requires data not currently in the package store.
-
-For more information on App-V Package streaming visit: .
-
-Sequencing for streaming optimization is available at: .
-
-### Package upgrades
-
-App-V Packages require updating throughout the lifecycle of the application. App-V Package upgrades are similar to the package publish operation, as each version will be created in its own PackageRoot location: `%ProgramData%\App-V\{PkgGUID}\{newVerGUID}`. The upgrade operation is optimized by creating hard links to identical- and streamed-files from other versions of the same package.
-
-### Package removal
-
-The behavior of the App-V Client when packages are removed depends on the method used for removal. Using an App-V full infrastructure to unpublish the application, the user catalog files (machine catalog for globally published applications) are removed, but retains the package store location and COW locations. When the PowerShell cmdlet `Remove-AppVClientPackge` is used to remove an App-V Package, the package store location is cleaned. Remember that unpublishing an App-V Package from the Management Server does not perform a Remove operation. Neither operation will remove the Package Store package files.
-
-## Roaming registry and data
-
-
-App-V 5 is able to provide a near-native experience when roaming, depending on how the application being used is written. By default, App-V roams AppData that is stored in the roaming location, based on the roaming configuration of the operating system. Other locations for storage of file-based data do not roam from computer to computer, since they are in locations that are not roamed.
-
-### Roaming requirements and user catalog data storage
-
-App-V stores data, which represents the state of the user’s catalog, in the form of:
-
-- Files under %appdata%\\Microsoft\\AppV\\Client\\Catalog
-
-- Registry settings under `HKEY_CURRENT_USER\Software\Microsoft\AppV\Client\Packages`
-
-Together, these files and registry settings represent the user’s catalog, so either both must be roamed, or neither must be roamed for a given user. App-V does not support roaming %AppData%, but not roaming the user’s profile (registry), or vice versa.
-
-**Note**
-The **Repair-AppvClientPackage** cmdlet does not repair the publishing state of packages, where the user’s App-V state under `HKEY_CURRENT_USER` is missing or mismatched with the data in %appdata%.
-
-
-
-### Registry-based data
-
-App-V registry roaming falls into two scenarios, as shown in the following table.
-
-
-
-
-
-
-
-
-
Scenario
-
Description
-
-
-
-
-
Applications that are run as standard users
-
When a standard user launches an App-V application, both HKLM and HKCU for App-V applications are stored in the HKCU hive on the machine. This presents as two distinct paths:
The locations are enabled for roaming based on the operating system settings.
-
-
-
Applications that are run with elevation
-
When an application is launched with elevation:
-
-
HKLM data is stored in the HKLM hive on the local computer
-
HKCU data is stored in the User Registry location
-
-
In this scenario, these settings are not roamed with normal operating system roaming configurations, and the resulting registry keys and values are stored in the following location:
-
-
-
-### App-V and folder redirection
-
-App-V 5.0 SP2 supports folder redirection of the roaming AppData folder (%AppData%). When the virtual environment is started, the roaming AppData state from the user’s roaming AppData directory is copied to the local cache. Conversely, when the virtual environment is shut down, the local cache that is associated with a specific user’s roaming AppData is transferred to the actual location of that user’s roaming AppData directory.
-
-A typical package has several locations mapped in the user’s backing store for settings in both AppData\\Local and AppData\\Roaming. These locations are the Copy on Write locations that are stored per user in the user’s profile, and that are used to store changes made to the package VFS directories and to protect the default package VFS.
-
-The following table shows local and roaming locations, when folder redirection has not been implemented.
-
-
-
-
-
-
-
-The following table shows local and roaming locations, when folder redirection has been implemented for %AppData%, and the location has been redirected (typically to a network location).
-
-
-
-
-
-
-
-The current App-V Client VFS driver cannot write to network locations, so the App-V Client detects the presence of folder redirection and copies the data on the local drive during publishing and when the virtual environment starts. After the user closes the App-V application and the App-V Client closes the virtual environment, the local storage of the VFS AppData is copied back to the network, enabling roaming to additional machines, where the process will be repeated. The detailed steps of the processes are:
-
-1. During publishing or virtual environment startup, the App-V Client detects the location of the AppData directory.
-
-2. If the roaming AppData path is local or ino AppData\\Roaming location is mapped, nothing happens.
-
-3. If the roaming AppData path is not local, the VFS AppData directory is mapped to the local AppData directory.
-
-This process solves the problem of a non-local %AppData% that is not supported by the App-V Client VFS driver. However, the data stored in this new location is not roamed with folder redirection. All changes during the running of the application happen to the local AppData location and must be copied to the redirected location. The detailed steps of this process are:
-
-1. App-V application is shut down, which shuts down the virtual environment.
-
-2. The local cache of the roaming AppData location is compressed and stored in a ZIP file.
-
-3. A timestamp at the end of the ZIP packaging process is used to name the file.
-
-4. The timestamp is recorded in the registry: HKEY\_CURRENT\_USER\\Software\\Microsoft\\AppV\\Client\\Packages\\<GUID>\\AppDataTime as the last known AppData timestamp.
-
-5. The folder redirection process is called to evaluate and initiate the ZIP file uploaded to the roaming AppData directory.
-
-The timestamp is used to determine a “last writer wins” scenario if there is a conflict and is used to optimize the download of the data when the App-V application is published or the virtual environment is started. Folder redirection will make the data available from any other clients covered by the supporting policy and will initiate the process of storing the AppData\\Roaming data to the local AppData location on the client. The detailed processes are:
-
-1. The user starts the virtual environment by starting an application.
-
-2. The application’s virtual environment checks for the most recent time stamped ZIP file, if present.
-
-3. The registry is checked for the last known uploaded timestamp, if present.
-
-4. The most recent ZIP file is downloaded unless the local last known upload timestamp is greater than or equal to the timestamp from the ZIP file.
-
-5. If the local last known upload timestamp is earlier than that of the most recent ZIP file in the roaming AppData location, the ZIP file is extracted to the local temp directory in the user’s profile.
-
-6. After the ZIP file is successfully extracted, the local cache of the roaming AppData directory is renamed and the new data is moved into place.
-
-7. The renamed directory is deleted and the application opens with the most recently saved roaming AppData data.
-
-This completes the successful roaming of application settings that are present in AppData\\Roaming locations. The only other condition that must be addressed is a package repair operation. The details of the process are:
-
-1. During repair, detect if the path to the user’s roaming AppData directory is not local.
-
-2. Map the non-local roaming AppData path targets are recreated the expected roaming and local AppData locations.
-
-3. Delete the timestamp stored in the registry, if present.
-
-This process will re-create both the local and network locations for AppData and remove the registry record of the timestamp.
-
-## App-V client application lifecycle management
-
-
-In an App-V Full Infrastructure, after applications are sequenced they are managed and published to users or computers via the App-V Management and Publishing servers. This section details the operations that occur during the common App-V application lifecycle operations (Add, publishing, launch, upgrade, and removal) and the file and registry locations that are changed and modified from the App-V Client perspective. The App-V Client operations are performed as a series of PowerShell commands initiated on the computer running the App-V Client.
-
-This document focuses on App-V Full Infrastructure solutions. For specific information on App-V Integration with Configuration Manager 2012 visit: .
-
-The App-V application lifecycle tasks are triggered at user login (default), machine startup, or as background timed operations. The settings for the App-V Client operations, including Publishing Servers, refresh intervals, package script enablement, and others, are configured during setup of the client or post-setup with PowerShell commands. See the How to Deploy the Client section on TechNet at: [How to Deploy the App-V Client](how-to-deploy-the-app-v-client-gb18030.md) or utilize the PowerShell:
-
-```powershell
-get-command *appv*
-```
-
-### Publishing refresh
-
-The publishing refresh process is comprised of several smaller operations that are performed on the App-V Client. Since App-V is an application virtualization technology and not a task scheduling technology, the Windows Task Scheduler is utilized to enable the process at user logon, machine startup, and at scheduled intervals. The configuration of the client during setup listed above is the preferred method when distributing the client to a large group of computers with the correct settings. These client settings can be configured with the following PowerShell cmdlets:
-
-- **Add-AppVPublishingServer:** Configures the client with an App-V Publishing Server that provides App-V packages.
-
-- **Set-AppVPublishingServer:** Modifies the current settings for the App-V Publishing Server.
-
-- **Set-AppVClientConfiguration:** Modifies the currents settings for the App-V Client.
-
-- **Sync-AppVPublishingServer:** Initiates an App-V Publishing Refresh process manually. This is also utilized in the scheduled tasks created during configuration of the publishing server.
-
-The focus of the following sections is to detail the operations that occur during different phases of an App-V Publishing Refresh. The topics include:
-
-- Adding an App-V Package
-
-- Publishing an App-V Package
-
-### Adding an App-V package
-
-Adding an App-V package to the client is the first step of the publishing refresh process. The end result is the same as the `Add-AppVClientPackage` cmdlet in PowerShell, except during the publishing refresh add process, the configured publishing server is contacted and passes a high-level list of applications back to the client to pull more detailed information and not a single package add operation. The process continues by configuring the client for package or connection group additions or updates, then accesses the appv file. Next, the contents of the appv file are expanded and placed on the local operating system in the appropriate locations. The following is a detailed workflow of the process, assuming the package is configured for Fault Streaming.
-
-**How to add an App-V package**
-
-1. Manual initiation via PowerShell or Task Sequence initiation of the Publishing Refresh process.
-
- 1. The App-V Client makes an HTTP connection and requests a list of applications based on the target. The Publishing refresh process supports targeting machines or users.
-
- 2. The App-V Publishing Server uses the identity of the initiating target, user or machine, and queries the database for a list of entitled applications. The list of applications is provided as an XML response, which the client uses to send additional requests to the server for more information on a per package basis.
-
-2. The Publishing Agent on the App-V Client performs all actions below serialized.
-
- Evaluate any connection groups that are unpublished or disabled, since package version updates that are part of the connection group cannot be processed.
-
-3. Configure the packages by identifying an Add or Update operations.
-
- 1. The App-V Client utilizes the AppX API from Windows and accesses the appv file from the publishing server.
-
- 2. The package file is opened and the AppXManifest.xml and StreamMap.xml are downloaded to the Package Store.
-
- 3. Completely stream publishing block data defined in the StreamMap.xml. Stores the publishing block data in the Package Store\\PkgGUID\\VerGUID\\Root.
-
- - Icons: Targets of extension points.
-
- - Portable Executable Headers (PE Headers): Targets of extension points that contain the base information about the image need on disk, directly accessed or via file types.
-
- - Scripts: Download scripts directory for use throughout the publishing process.
-
- 4. Populate the Package store:
-
- 1. Create sparse files on disk that represent the extracted package for any directories listed.
-
- 2. Stage top level files and directories under root.
-
- 3. All other files are created when the directory is listed as sparse on disk and streamed on demand.
-
- 5. Create the machine catalog entries. Create the Manifest.xml and DeploymentConfiguration.xml from the package files (if no DeploymentConfiguration.xml file in the package a placeholder is created).
-
- 6. Create location of the package store in the registry HKLM\\Software\\Microsoft\\AppV\\Client\\Packages\\PkgGUID\\Versions\\VerGUID\\Catalog
-
- 7. Create the Registry.dat file from the package store to %ProgramData%\\Microsoft\\AppV\\Client\\VReg\\{VersionGUID}.dat
-
- 8. Register the package with the App-V Kernel Mode Driver HKLM\\Microsoft\\Software\\AppV\\MAV
-
- 9. Invoke scripting from the AppxManifest.xml or DeploymentConfig.xml file for Package Add timing.
-
-4. Configure Connection Groups by adding and enabling or disabling.
-
-5. Remove objects that are not published to the target (user or machine).
-
- **Note**
- This will not perform a package deletion but rather remove integration points for the specific target (user or machine) and remove user catalog files (machine catalog files for globally published).
-
-
-
-6. Invoke background load mounting based on client configuration.
-
-7. Packages that already have publishing information for the machine or user are immediately restored.
-
- **Note**
- This condition occurs as a product of removal without unpublishing with background addition of the package.
-
-
-
-This completes an App-V package add of the publishing refresh process. The next step is publishing the package to the specific target (machine or user).
-
-
-
-### Publishing an App-V package
-
-During the Publishing Refresh operation, the specific publishing operation (Publish-AppVClientPackage) adds entries to the user catalog, maps entitlement to the user, identifies the local store, and finishes by completing any integration steps. The following are the detailed steps.
-
-**How to publish and App-V package**
-
-1. Package entries are added to the user catalog
-
- 1. User targeted packages: the UserDeploymentConfiguration.xml and UserManifest.xml are placed on the machine in the User Catalog
-
- 2. Machine targeted (global) packages: the UserDeploymentConfiguration.xml is placed in the Machine Catalog
-
-2. Register the package with the kernel mode driver for the user at HKLM\\Software\\Microsoft\\AppV\\MAV
-
-3. Perform integration tasks.
-
- 1. Create extension points.
-
- 2. Store backup information in the user’s registry and roaming profile (Shortcut Backups).
-
- **Note**
- This enables restore extension points if the package is unpublished.
-
-
-
- 3. Run scripts targeted for publishing timing.
-
-Publishing an App-V Package that is part of a Connection Group is very similar to the above process. For connection groups, the path that stores the specific catalog information includes PackageGroups as a child of the Catalog Directory. Review the machine and users catalog information above for details.
-
-
-
-### Application launch
-
-After the Publishing Refresh process, the user launches and subsequently re-launches an App-V application. The process is very simple and optimized to launch quickly with a minimum of network traffic. The App-V Client checks the path to the user catalog for files created during publishing. After rights to launch the package are established, the App-V Client creates a virtual environment, begins streaming any necessary data, and applies the appropriate manifest and deployment configuration files during virtual environment creation. With the virtual environment created and configured for the specific package and application, the application starts.
-
-**How to launch App-V applications**
-
-1. User launches the application by clicking on a shortcut or file type invocation.
-
-2. The App-V Client verifies existence in the User Catalog for the following files
-
- - UserDeploymentConfiguration.xml
-
- - UserManifest.xml
-
-3. If the files are present, the application is entitled for that specific user and the application will start the process for launch. There is no network traffic at this point.
-
-4. Next, the App-V Client checks that the path for the package registered for the App-V Client service is found in the registry.
-
-5. Upon finding the path to the package store, the virtual environment is created. If this is the first launch, the Primary Feature Block downloads if present.
-
-6. After downloading, the App-V Client service consumes the manifest and deployment configuration files to configure the virtual environment and all App-V subsystems are loaded.
-
-7. The Application launches. For any missing files in the package store (sparse files), App-V will stream fault the files on an as needed basis.
-
- 
-
-### Upgrading an App-V package
-
-The App-V 5 package upgrade process differs from the older versions of App-V. App-V supports multiple versions of the same package on a machine entitled to different users. Package versions can be added at any time as the package store and catalogs are updated with the new resources. The only process specific to the addition of new version resources is storage optimization. During an upgrade, only the new files are added to the new version store location and hard links are created for unchanged files. This reduces the overall storage by only presenting the file on one disk location and then projecting it into all folders with a file location entry on the disk. The specific details of upgrading an App-V Package are as follows:
-
-**How to upgrade an App-V package**
-
-1. The App-V Client performs a Publishing Refresh and discovers a newer version of an App-V Package.
-
-2. Package entries are added to the appropriate catalog for the new version
-
- 1. User targeted packages: the UserDeploymentConfiguration.xml and UserManifest.xml are placed on the machine in the user catalog at appdata\\roaming\\Microsoft\\AppV\\Client\\Catalog\\Packages\\PkgGUID\\VerGUID
-
- 2. Machine targeted (global) packages: the UserDeploymentConfiguration.xml is placed in the machine catalog at %programdata%\\Microsoft\\AppV\\Client\\Catalog\\Packages\\PkgGUID\\VerGUID
-
-3. Register the package with the kernel mode driver for the user at HKLM\\Software\\Microsoft\\AppV\\MAV
-
-4. Perform integration tasks.
-
- - Integrate extensions points (EP) from the Manifest and Dynamic Configuration files.
-
- 1. File based EP data is stored in the AppData folder utilizing Junction Points from the package store.
-
- 2. Version 1 EPs already exist when a new version becomes available.
-
- 3. The extension points are switched to the Version 2 location in machine or user catalogs for any newer or updated extension points.
-
-5. Run scripts targeted for publishing timing.
-
-6. Install Side by Side assemblies as required.
-
-### Upgrading an in-use App-V package
-
-**Starting in App-V 5 SP2**: If you try to upgrade a package that is in use by an end user, the upgrade task is placed in a pending state. The upgrade will run later, according to the following rules:
-
-
-
-
-
-
-
-
-
Task type
-
Applicable rule
-
-
-
-
-
User-based task, e.g., publishing a package to a user
-
The pending task will be performed after the user logs off and then logs back on.
-
-
-
Globally based task, e.g., enabling a connection group globally
-
The pending task will be performed when the computer is shut down and then restarted.
-
-
-
-
-
-
-When a task is placed in a pending state, the App-V client also generates a registry key for the pending task, as follows:
-
-
-
-
-
-The following operations must be completed before users can use the newer version of the package:
-
-
-
-
-
-
-
-
-
Task
-
Details
-
-
-
-
-
Add the package to the computer
-
This task is computer specific and you can perform it at any time by completing the steps in the Package Add section above.
-
-
-
Publish the package
-
See the Package Publishing section above for steps. This process requires that you update extension points on the system. End users cannot be using the application when you complete this task.
-
-
-
-
-
-
-Use the following example scenarios as a guide for updating packages.
-
-
-
-
-
-
-
-
-
Scenario
-
Requirements
-
-
-
-
-
App-V package is not in use when you try to upgrade
-
None of the following components of the package can be in use: virtual application, COM server, or shell extensions.
-
The administrator publishes a newer version of the package and the upgrade works the next time a component or application inside the package is launched. The new version of the package is streamed and run. Nothing has changed in this scenario in App-V 5 SP2 from previous releases of App-V 5.
-
-
-
App-V package is in use when the administrator publishes a newer version of the package
-
The upgrade operation is set to pending by the App-V Client, which means that it is queued and carried out later when the package is not in use.
-
If the package application is in use, the user shuts down the virtual application, after which the upgrade can occur.
-
If the package has shell extensions (Office 2013), which are permanently loaded by Windows Explorer, the user cannot be logged in. Users must log off and the log back in to initiate the App-V package upgrade.
-
-
-
-
-
-
-### Global vs user publishing
-
-App-V Packages can be published in one of two ways; User which entitles an App-V package to a specific user or group of users and Global which entitles the App-V package to the entire machine for all users of the machine. Once a package upgrade has been pended and the App-V package is not in use, consider the two types of publishing:
-
-- **Globally published**: the application is published to a machine; all users on that machine can use it. The upgrade will happen when the App-V Client Service starts, which effectively means a machine restart.
-
-- **User published**: the application is published to a user. If there are multiple users on the machine, the application can be published to a subset of the users. The upgrade will happen when the user logs in or when it is published again (periodically, ConfigMgr Policy refresh and evaluation, or an App-V periodic publishing/refresh, or explicitly via PowerShell commands).
-
-### Removing an App-V package
-
-Removing App-V applications in a Full Infrastructure is an unpublish operation, and does not perform a package removal. The process is the same as the publish process above, but instead of adding the removal process reverses the changes that have been made for App-V Packages.
-
-### Repairing an App-V package
-
-The repair operation is very simple but may affect many locations on the machine. The previously mentioned Copy on Write (COW) locations are removed, and extension points are de-integrated and then re-integrated. Please review the COW data placement locations by reviewing where they are registered in the registry. This operation is done automatically and there is no administrative control other than initiating a Repair operation from the App-V Client Console or via PowerShell (Repair-AppVClientPackage).
-
-## Integration of App-V packages
-
-
-The App-V Client and package architecture provides specific integration with the local operating system during the addition and publishing of packages. Three files define the integration or extension points for an App-V Package:
-
-- AppXManifest.xml: Stored inside of the package with fallback copies stored in the package store and the user profile. Contains the options created during the sequencing process.
-
-- DeploymentConfig.xml: Provides configuration information of computer and user based integration extension points.
-
-- UserConfig.xml: A subset of the Deploymentconfig.xml that only provides user- based configurations and only targets user-based extension points.
-
-### Rules of integration
-
-When App-V applications are published to a computer with the App-V Client, some specific actions take place as described in the list below:
-
-- Global Publishing: Shortcuts are stored in the All Users profile location and other extension points are stored in the registry in the HKLM hive.
-
-- User Publishing: Shortcuts are stored in the current user account profile and other extension points are stored in the registry in the HKCU hive.
-
-- Backup and Restore: Existing native application data and registry (such as FTA registrations) are backed up during publishing.
-
- 1. App-V packages are given ownership based on the last integrated package where the ownership is passed to the newest published App-V application.
-
- 2. Ownership transfers from one App-V package to another when the owning App-V package is unpublished. This will not initiate a restore of the data or registry.
-
- 3. Restore the backed up data when the last package is unpublished or removed on a per extension point basis.
-
-### Extension points
-
-The App-V publishing files (manifest and dynamic configuration) provide several extension points that enable the application to integrate with the local operating system. These extension points perform typical application installation tasks, such as placing shortcuts, creating file type associations, and registering components. As these are virtualized applications that are not installed in the same manner a traditional application, there are some differences. The following is a list of extension points covered in this section:
-
-- Shortcuts
-
-- File Type Associations
-
-- Shell Extensions
-
-- COM
-
-- Software Clients
-
-- Application capabilities
-
-- URL Protocol Handler
-
-- AppPath
-
-- Virtual Application
-
-### Shortcuts
-
-The short cut is one of the basic elements of integration with the OS and is the interface for direct user launch of an App-V application. During the publishing and unpublishing of App-V applications.
-
-From the package manifest and dynamic configuration XML files, the path to a specific application executable can be found in a section similar to the following:
-
-```xml
-
-
- [{Common Desktop}]\Adobe Reader 9.lnk
- [{AppVPackageRoot}]\Reader\AcroRd32.exe
- [{Windows}]\Installer\{AC76BA86-7AD7-1033-7B44-A94000000001}\SC_Reader.ico
-
-
- 1
- [{AppVPackageRoot}]\Reader\AcroRd32.exe
-
-
-```
-
-As mentioned previously, the App-V shortcuts are placed by default in the user’s profile based on the refresh operation. Global refresh places shortcuts in the All Users profile and user refresh stores them in the specific user’s profile. The actual executable is stored in the Package Store. The location of the ICO file is a tokenized location in the App-V package.
-
-### File type associations
-
-The App-V Client manages the local operating system File Type Associations during publishing, which enables users to use file type invocations or to open a file with a specifically registered extension (.docx) to start an App-V application. File type associations are present in the manifest and dynamic configuration files as represented in the example below:
-
-```xml
-
-
-
- .xdp
- AcroExch.XDPDoc
- application/vnd.adobe.xdp+xml
-
-
- AcroExch.XDPDoc
- Adobe Acrobat XML Data Package File
- 65536
- [{Windows}]\Installer\{AC76BA86-7AD7-1033-7B44-A94000000001}\XDPFile_8.ico
-
- Read
-
- [{AppVPackageRoot}]\Reader\AcroRd32.exe
- Open
- "[{AppVPackageRoot}]\Reader\AcroRd32.exe" "%1"
-
-
- [{AppVPackageRoot}]\Reader\AcroRd32.exe
- Printto
- "[{AppVPackageRoot}]\Reader\AcroRd32.exe" /t "%1" "%2" "%3" "%4"
-
-
- [{AppVPackageRoot}]\Reader\AcroRd32.exe
- Read
- Open with Adobe Reader 9
- "[{AppVPackageRoot}]\Reader\AcroRd32.exe" "%1"
-
-
-
-
-
-```
-
-**Note**
-In this example:
-
-- `.xdp` is the extension
-
-- `AcroExch.XDPDoc` is the ProgId value (which points to the adjoining ProgId)
-
-- `"[{AppVPackageRoot}]\Reader\AcroRd32.exe" "%1"` is the command line, which points to the application executable
-
-
-
-### Shell extensions
-
-Shell extensions are embedded in the package automatically during the sequencing process. When the package is published globally, the shell extension gives users the same functionality as if the application were locally installed. The application requires no additional setup or configuration on the client to enable the shell extension functionality.
-
-**Requirements for using shell extensions:**
-
-- Packages that contain embedded shell extensions must be published globally.
-
-- The “bitness” of the application, Sequencer, and App-V client must match, or the shell extensions won’t work. For example:
-
- - The version of the application is 64-bit.
-
- - The Sequencer is running on a 64-bit computer.
-
- - The package is being delivered to a 64-bit App-V client computer.
-
-The following table displays the supported shell extensions.
-
-
-
-
-
-
-
-
-
Handler
-
Description
-
-
-
-
-
Context menu handler
-
Adds menu items to the context menu. It is called before the context menu is displayed.
-
-
-
Drag-and-drop handler
-
Controls the action upon right-click drag-and-drop and modifies the context menu that appears.
-
-
-
Drop target handler
-
Controls the action after a data object is dragged-and-dropped over a drop target such as a file.
-
-
-
Data object handler
-
Controls the action after a file is copied to the clipboard or dragged-and-dropped over a drop target. It can provide additional clipboard formats to the drop target.
-
-
-
Property sheet handler
-
Replaces or adds pages to the property sheet dialog box of an object.
-
-
-
Infotip handler
-
Allows retrieving flags and infotip information for an item and displaying it inside a popup tooltip upon mouse- hover.
-
-
-
Column handler
-
Allows creating and displaying custom columns in Windows Explorer Details view. It can be used to extend sorting and grouping.
-
-
-
Preview handler
-
Enables a preview of a file to be displayed in the Windows Explorer Preview Pane.
-
-
-
-
-
-
-### COM
-
-The App-V Client supports publishing applications with support for COM integration and virtualization. COM integration allows the App-V Client to register COM objects on the local operating system and virtualization of the objects. For the purposes of this document, the integration of COM objects requires additional detail.
-
-App-V supports registering COM objects from the package to the local operating system with two process types: Out-of-process and in-process. Registering COM objects is accomplished with one or a combination of multiple modes of operation for a specific App-V package that includes off, Isolated, and Integrated. The integrated mode is configured for either the out-of-process or in-process type. Configuration of COM modes and types is accomplished with dynamic configuration files (deploymentconfig.xml or userconfig.xml).
-
-Details on App-V integration are available at: .
-
-### Software clients and application capabilities
-
-App-V supports specific software clients and application capabilities extension points that enable virtualized applications to be registered with the software client of the operating system. This enables users to select default programs for operations like email, instant messaging, and media player. This operation is performed in the control panel with the Set Program Access and Computer Defaults, and configured during sequencing in the manifest or dynamic configuration files. Application capabilities are only supported when the App-V applications are published globally.
-
-Example of software client registration of an App-V based mail client.
-
-```xml
-
-
-
-
-
-
- Mozilla Thunderbird
- Mozilla Thunderbird
- [{ProgramFilesX86}]\Mozilla Thunderbird\thunderbird.exe,0
-
-
- "[{ProgramFilesX86}]\Mozilla Thunderbird\uninstall\helper.exe" /SetAsDefaultAppGlobal
- "[{ProgramFilesX86}]\Mozilla Thunderbird\uninstall\helper.exe" /HideShortcuts
- "[{ProgramFilesX86}]\Mozilla Thunderbird\uninstall\helper.exe" /ShowShortcuts
-
- 1
-
-
-
- [{ProgramFilesX86}]\Mozilla Thunderbird\thunderbird.exe
- "[{ProgramFilesX86}]\Mozilla Thunderbird\thunderbird.exe" -mail
-
- [{ProgramFilesX86}]\Mozilla Thunderbird\mozMapi32_InUse.dll
-
- Thunderbird URL
- 2
- [{ProgramFilesX86}]\Mozilla Thunderbird\thunderbird.exe,0
-
- [{ProgramFilesX86}]\Mozilla Thunderbird\thunderbird.exe
- "[{ProgramFilesX86}]\Mozilla Thunderbird\thunderbird.exe" -osint -compose "%1"
-
-
-
-
-
-
-
-```
-
-**Note**
-In this example:
-
-- `` is the overall Software Clients setting to integrate Email clients
-
-- `` is the flag to set a particular Email client as the default Email client
-
-- `[{ProgramFilesX86}]\Mozilla Thunderbird\mozMapi32_InUse.dll` is the MAPI dll registration
-
-
-
-### URL Protocol handler
-
-Applications do not always specifically called virtualized applications utilizing file type invocation. For, example, in an application that supports embedding a mailto: link inside a document or web page, the user clicks on a mailto: link and expects to get their registered mail client. App-V supports URL Protocol handlers that can be registered on a per-package basis with the local operating system. During sequencing, the URL protocol handlers are automatically added to the package.
-
-For situations where there is more than one application that could register the specific URL Protocol handler, the dynamic configuration files can be utilized to modify the behavior and suppress or disable this feature for an application that should not be the primary application launched.
-
-### AppPath
-
-The AppPath extension point supports calling App-V applications directly from the operating system. This is typically accomplished from the Run or Start Screen, depending on the operating system, which enables administrators to provide access to App-V applications from operating system commands or scripts without calling the specific path to the executable. It therefore avoids modifying the system path environment variable on all systems, as it is accomplished during publishing.
-
-The AppPath extension point is configured either in the manifest or in the dynamic configuration files and is stored in the registry on the local machine during publishing for the user. For additional information on AppPath review: .
-
-### Virtual application
-
-This subsystem provides a list of applications captured during sequencing which is usually consumed by other App-V components. Integration of extension points belonging to a particular application can be disabled using dynamic configuration files. For example, if a package contains two applications, it is possible to disable all extension points belonging to one application, in order to allow only integration of extension points of other application.
-
-### Extension point rules
-
-The extension points described above are integrated into the operating system based on how the packages has been published. Global publishing places extension points in public machine locations, where user publishing places extension points in user locations. For example a shortcut that is created on the desktop and published globally will result in the file data for the shortcut (%Public%\\Desktop) and the registry data (HKLM\\Software\\Classes). The same shortcut would have file data (%UserProfile%\\Desktop) and registry data (HKCU\\Software\\Classes).
-
-Extension points are not all published the same way, where some extension points will require global publishing and others require sequencing on the specific operating system and architecture where they are delivered. Below is a table that describes these two key rules.
-
-
-
-
-
-
-
-
-
-
Virtual Extension
-
Requires target OS Sequencing
-
Requires Global Publishing
-
-
-
-
-
Shortcut
-
-
-
-
-
File Type Association
-
-
-
-
-
URL Protocols
-
X
-
-
-
-
AppPaths
-
X
-
-
-
-
COM Mode
-
-
-
-
-
Software Client
-
X
-
-
-
-
Application Capabilities
-
X
-
X
-
-
-
Context Menu Handler
-
X
-
X
-
-
-
Drag-and-drop Handler
-
X
-
-
-
-
Data Object Handler
-
X
-
-
-
-
Property Sheet Handler
-
X
-
-
-
-
Infotip Handler
-
X
-
-
-
-
Column Handler
-
X
-
-
-
-
Shell Extensions
-
X
-
-
-
-
Browser Helper Object
-
X
-
X
-
-
-
Active X Object
-
X
-
X
-
-
-
-
-
-
-## Dynamic configuration processing
-
-
-Deploying App-V packages to one machine or user is very simple. However, as organizations deploy AppV applications across business lines and geographic and political boundaries, the ability to sequence an application one time with one set of settings becomes impossible. App-V was designed for this scenario, as it captures specific settings and configurations during sequencing in the Manifest file, but also supports modification with Dynamic Configuration files.
-
-App-V dynamic configuration allows for specifying a policy for a package either at the machine level or at the user level. The Dynamic Configuration files enable sequencing engineers to modify the configuration of a package, post-sequencing, to address the needs of individual groups of users or machines. In some instances it may be necessary to make modifications to the application to provide proper functionality within the App-V environment. For example, it may be necessary to make modifications to the \_\*config.xml files to allow certain actions to be performed at a specified time during the execution of the application, like disabling a mailto extension to prevent a virtualized application from overwriting that extension from another application.
-
-App-V Packages contain the Manifest file inside of the appv package file, which is representative of sequencing operations and is the policy of choice unless Dynamic Configuration files are assigned to a specific package. Post-sequencing, the Dynamic Configuration files can be modified to allow the publishing of an application to different desktops or users with different extension points. The two Dynamic Configuration Files are the Dynamic Deployment Configuration (DDC) and Dynamic User Configuration (DUC) files. This section focuses on the combination of the manifest and dynamic configuration files.
-
-### Example for dynamic configuration files
-
-The example below shows the combination of the Manifest, Deployment Configuration and User Configuration files after publishing and during normal operation. These examples are abbreviated examples of each of the files. The purpose is show the combination of the files only and not to be a complete description of the specific categories available in each of the files. For more information review the App-V 5 Sequencing Guide at:
-
-**Manifest**
-
-```xml
-
-
- [{Common Programs}]\7-Zip\7-Zip File Manager.lnk
- [{AppVPackageRoot}]\7zFM.exe
- [{AppVPackageRoot}]\7zFM exe.O.ico
-
-
-```
-
-**Deployment Configuration**
-
-```xml
-
-
-
-
-
-
-
-
-
-
-```
-
-**User Configuration**
-
-```xml
-
-
-
-
- [{Desktop}]\7-Zip\7-Zip File Manager.lnk
- [{AppVPackageRoot}]\7zFM.exe
- [{AppVPackageRoot}]\7zFM exe.O.ico
-
-
-
-
-
-
-
- [{Desktop}]\7-Zip\7-Zip File Manager.lnk
- [{AppVPackageRoot}]\7zFM.exe
- [{AppVPackageRoot}]\7zFM.exe.O.ico
-
-
- [{Common Programs}]\7-Zip\7-Zip File Manager.Ink
- [{AppVPackageRoot}]\7zFM.exe
- [{AppVPackageRoot)]\7zFM.exe.O.ico
-
-
-
-
-
-
-
-
-
-
-
-
-```
-
-## Side-by-side assemblies
-
-
-App-V supports the automatic packaging of side-by-side (SxS) assemblies during sequencing and deployment on the client during virtual application publishing. App-V 5 SP2 supports capturing SxS assemblies during sequencing for assemblies not present on the sequencing machine. And for assemblies consisting of Visual C++ (Version 8 and newer) and/or MSXML run-time, the Sequencer will automatically detect and capture these dependencies even if they were not installed during monitoring. The Side by Side assemblies feature removes the limitations of previous versions of App-V, where the App-V Sequencer did not capture assemblies already present on the sequencing workstation, and privatizing the assemblies which limited to one bit version per package. This behavior resulted in deployed App-V applications to clients missing the required SxS assemblies, causing application launch failures. This forced the packaging process to document and then ensure that all assemblies required for packages were locally installed on the user’s client operating system to ensure support for the virtual applications. Based on the number of assemblies and the lack of application documentation for the required dependencies, this task was both a management and implementation challenge.
-
-Side by Side Assembly support in App-V has the following features.
-
-- Automatic captures of SxS assembly during Sequencing, regardless of whether the assembly was already installed on the sequencing workstation.
-
-- The App-V Client automatically installs required SxS assemblies to the client computer at publishing time when they are not present.
-
-- The Sequencer reports the VC run-time dependency in Sequencer reporting mechanism.
-
-- The Sequencer allows opting to not package the assemblies that are already installed on the Sequencer, supporting scenarios where the assemblies have previously been installed on the target computers.
-
-### Automatic publishing of SxS assemblies
-
-During publishing of an App-V package with SxS assemblies the App-V Client will check for the presence of the assembly on the machine. If the assembly does not exist, the client will deploy the assembly to the machine. Packages that are part of connection groups will rely on the Side by Side assembly installations that are part of the base packages, as the connection group does not contain any information about assembly installation.
-
-**Note**
-UnPublishing or removing a package with an assembly does not remove the assemblies for that package.
-
-
-
-## Client logging
-
-
-The App-V client logs information to the Windows Event log in standard ETW format. The specific App-V events can be found in the event viewer, under Applications and Services Logs\\Microsoft\\AppV\\Client.
-
-**Note**
-In App-V 5.0 SP3, some logs have been consolidated and moved to the following location:
-
-`Event logs/Applications and Services Logs/Microsoft/AppV/ServiceLog`
-
-For a list of the moved logs, see [About App-V 5.0 SP3](about-app-v-50-sp3.md#bkmk-event-logs-moved).
-
-
-
-There are three specific categories of events recorded described below.
-
-**Admin**: Logs events for configurations being applied to the App-V Client, and contains the primary warnings and errors.
-
-**Operational**: Logs the general App-V execution and usage of individual components creating an audit log of the App-V operations that have been completed on the App-V Client.
-
-**Virtual Application**: Logs virtual application launches and use of virtualization subsystems.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v5/application-publishing-and-client-interaction51.md b/mdop/appv-v5/application-publishing-and-client-interaction51.md
deleted file mode 100644
index ba6d7e8fe7..0000000000
--- a/mdop/appv-v5/application-publishing-and-client-interaction51.md
+++ /dev/null
@@ -1,1635 +0,0 @@
----
-title: Application Publishing and Client Interaction
-description: Application Publishing and Client Interaction
-author: dansimp
-ms.assetid: 36a4bf6f-a917-41a6-9856-6248686df352
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 08/30/2016
----
-
-
-# Application Publishing and Client Interaction
-
-
-This article provides technical information about common App-V client operations and their integration with the local operating system.
-
-- [App-V package files created by the Sequencer](#bkmk-appv-pkg-files-list)
-
-- [What’s in the appv file?](#bkmk-appv-file-contents)
-
-- [App-V client data storage locations](#bkmk-files-data-storage)
-
-- [Package registry](#bkmk-pkg-registry)
-
-- [App-V package store behavior](#bkmk-pkg-store-behavior)
-
-- [Roaming registry and data](#bkmk-roaming-reg-data)
-
-- [App-V client application lifecycle management](#bkmk-clt-app-lifecycle)
-
-- [Integration of App-V packages](#bkmk-integr-appv-pkgs)
-
-- [Dynamic configuration processing](#bkmk-dynamic-config)
-
-- [Side-by-side assemblies](#bkmk-sidebyside-assemblies)
-
-- [Client logging](#bkmk-client-logging)
-
-For additional reference information, see [Microsoft Application Virtualization (App-V) Documentation Resources Download Page](https://www.microsoft.com/download/details.aspx?id=27760).
-
-## App-V package files created by the Sequencer
-
-
-The Sequencer creates App-V packages and produces a virtualized application. The sequencing process creates the following files:
-
-
-
-
-
-
-
-
-
File
-
Description
-
-
-
-
-
.appv
-
-
The primary package file, which contains the captured assets and state information from the sequencing process.
-
Architecture of the package file, publishing information, and registry in a tokenized form that can be reapplied to a machine and to a specific user upon delivery.
-
-
-
-
.MSI
-
Executable deployment wrapper that you can use to deploy .appv files manually or by using a third-party deployment platform.
-
-
-
_DeploymentConfig.XML
-
File used to customize the default publishing parameters for all applications in a package that is deployed globally to all users on a computer that is running the App-V client.
-
-
-
_UserConfig.XML
-
File used to customize the publishing parameters for all applications in a package that is a deployed to a specific user on a computer that is running the App-V client.
-
-
-
Report.xml
-
Summary of messages resulting from the sequencing process, including omitted drivers, files, and registry locations.
-
-
-
.CAB
-
Optional: Package accelerator file used to automatically rebuild a previously sequenced virtual application package.
-
-
-
.appvt
-
Optional: Sequencer template file used to retain commonly reused Sequencer settings.
-
-
-
-
-
-
-For information about sequencing, see [Application Virtualization Sequencing Guide](https://go.microsoft.com/fwlink/?LinkID=269810).
-
-## What’s in the appv file?
-
-
-The appv file is a container that stores XML and non-XML files together in a single entity. This file is built from the AppX format, which is based on the Open Packaging Conventions (OPC) standard.
-
-To view the appv file contents, make a copy of the package, and then rename the copied file to a ZIP extension.
-
-The appv file contains the following folder and files, which are used when creating and publishing a virtual application:
-
-
-
-
-
-
-
-
-
-
Name
-
Type
-
Description
-
-
-
-
-
Root
-
File folder
-
Directory that contains the file system for the virtualized application that is captured during sequencing.
-
-
-
[Content_Types].xml
-
XML File
-
List of the core content types in the appv file (e.g. DLL, EXE, BIN).
-
-
-
AppxBlockMap.xml
-
XML File
-
Layout of the appv file, which uses File, Block, and BlockMap elements that enable location and validation of files in the App-V package.
-
-
-
AppxManifest.xml
-
XML File
-
Metadata for the package that contains the required information for adding, publishing, and launching the package. Includes extension points (file type associations and shortcuts) and the names and GUIDs associated with the package.
-
-
-
FilesystemMetadata.xml
-
XML File
-
List of the files captured during sequencing, including attributes (e.g., directories, files, opaque directories, empty directories,and long and short names).
-
-
-
PackageHistory.xml
-
XML File
-
Information about the sequencing computer (operating system version, Internet Explorer version, .Net Framework version) and process (upgrade, package version).
-
-
-
Registry.dat
-
DAT File
-
Registry keys and values captured during the sequencing process for the package.
-
-
-
StreamMap.xml
-
XML File
-
List of files for the primary and publishing feature block. The publishing feature block contains the ICO files and required portions of files (EXE and DLL) for publishing the package. When present, the primary feature block includes files that have been optimized for streaming during the sequencing process.
-
-
-
-
-
-
-## App-V client data storage locations
-
-
-The App-V client performs tasks to ensure that virtual applications run properly and work like locally installed applications. The process of opening and running virtual applications requires mapping from the virtual file system and registry to ensure the application has the required components of a traditional application expected by users. This section describes the assets that are required to run virtual applications and lists the location where App-V stores the assets.
-
-
Stores previous integration points that enable restore on package unpublish
-
-
-
Copy on Write (COW) Roaming
-
%AppData%\Microsoft\AppV\Client\VFS
-
Writeable roaming location for package modification
-
-
-
Copy on Write (COW) Local
-
%LocalAppData%\Microsoft\AppV\Client\VFS
-
Writeable non-roaming location for package modification
-
-
-
Machine Registry
-
HKLM\Software\Microsoft\AppV
-
Contains package state information, including VReg for machine or globally published packages (Machine hive)
-
-
-
User Registry
-
HKCU\Software\Microsoft\AppV
-
Contains user package state information including VReg
-
-
-
User Registry Classes
-
HKCU\Software\Classes\AppV
-
Contains additional user package state information
-
-
-
-
-
-
-Additional details for the table are provided in the section below and throughout the document.
-
-### Package store
-
-The App-V Client manages the applications assets mounted in the package store. This default storage location is `%ProgramData%\App-V`, but you can configure it during or after setup by using the `Set-AppVClientConfiguration` PowerShell command, which modifies the local registry (`PackageInstallationRoot` value under the `HKLM\Software\Microsoft\AppV\Client\Streaming` key). The package store must be located at a local path on the client operating system. The individual packages are stored in the package store in subdirectories named for the Package GUID and Version GUID.
-
-Example of a path to a specific application:
-
-``` syntax
-C:\ProgramData\App-V\PackGUID\VersionGUID
-```
-
-To change the default location of the package store during setup, see [How to Deploy the App-V Client](how-to-deploy-the-app-v-client-51gb18030.md).
-
-### Shared Content Store
-
-If the App-V Client is configured in Shared Content Store mode, no data is written to disk when a stream fault occurs, which means that the packages require minimal local disk space (publishing data). The use of less disk space is highly desirable in VDI environments, where local storage can be limited, and streaming the applications from a high performance network location (such as a SAN) is preferable. For more information on shared content store mode, see .
-
-**Note**
-The machine and package store must be located on a local drive, even when you’re using Shared Content Store configurations for the App-V Client.
-
-
-
-### Package catalogs
-
-The App-V Client manages the following two file-based locations:
-
-- **Catalogs (user and machine).**
-
-- **Registry locations** - depends on how the package is targeted for publishing. There is a Catalog (data store) for the computer, and a catalog for each individual user. The Machine Catalog stores global information applicable to all users or any user, and the User Catalog stores information applicable to a specific user. The Catalog is a collection of Dynamic Configurations and manifest files; there is discrete data for both file and registry per package version.
-
-### Machine catalog
-
-
-
-
-
-
-
-
-
Description
-
Stores package documents that are available to users on the machine, when packages are added and published. However, if a package is “global” at publishing time, the integrations are available to all users.
-
If a package is non-global, the integrations are published only for specific users, but there are still global resources that are modified and visible to anyone on the client computer (e.g., the package directory is in a shared disk location).
-
If a package is available to a user on the computer (global or non-global), the manifest is stored in the Machine Catalog. When a package is published globally, there is a Dynamic Configuration file, stored in the Machine Catalog; therefore, the determination of whether a package is global is defined according to whether there is a policy file (UserDeploymentConfiguration file) in the Machine Catalog.
Additional files in the machine catalog when the package is part of a connection group
-
-
PackageGroupDescriptor.xml
-
UserPackageGroupDescriptor.xml (globally published Connection Group)
-
-
-
-
-
-
-
-### User catalog
-
-
-
-
-
-
-
-
-
Description
-
Created during the publishing process. Contains information used for publishing the package, and also used at launch to ensure that a package is provisioned to a specific user. Created in a roaming location and includes user-specific publishing information.
-
When a package is published for a user, the policy file is stored in the User Catalog. At the same time, a copy of the manifest is also stored in the User Catalog. When a package entitlement is removed for a user, the relevant package files are removed from the User Catalog. Looking at the user catalog, an administrator can view the presence of a Dynamic Configuration file, which indicates that the package is entitled for that user.
-
For roaming users, the User Catalog needs to be in a roaming or shared location to preserve the legacy App-V behavior of targeting users by default. Entitlement and policy are tied to a user, not a computer, so they should roam with the user once they are provisioned.
Additional file in the machine catalog when the package is part of a connection group
-
UserPackageGroupDescriptor.xml
-
-
-
-
-
-
-### Shortcut backups
-
-During the publishing process, the App-V Client backs up any shortcuts and integration points to `%AppData%\Microsoft\AppV\Client\Integration\ShortCutBackups.` This backup enables the restoration of these integration points to the previous versions when the package is unpublished.
-
-### Copy on Write files
-
-The Package Store contains a pristine copy of the package files that have been streamed from the publishing server. During normal operation of an App-V application, the user or service may require changes to the files. These changes are not made in the package store in order to preserve your ability to repair the application, which removes these changes. These locations, called Copy on Write (COW), support both roaming and non-roaming locations. The location where the modifications are stored depends where the application has been programmed to write changes to in a native experience.
-
-### COW roaming
-
-The COW Roaming location described above stores changes to files and directories that are targeted to the typical %AppData% location or \\Users\\{username}\\AppData\\Roaming location. These directories and files are then roamed based on the operating system settings.
-
-### COW local
-
-The COW Local location is similar to the roaming location, but the directories and files are not roamed to other computers, even if roaming support has been configured. The COW Local location described above stores changes applicable to typical windows and not the %AppData% location. The directories listed will vary but there will be two locations for any typical Windows locations (e.g. Common AppData and Common AppDataS). The **S** signifies the restricted location when the virtual service requests the change as a different elevated user from the logged on users. The non-**S** location stores user based changes.
-
-## Package registry
-
-
-Before an application can access the package registry data, the App-V Client must make the package registry data available to the applications. The App-V Client uses the real registry as a backing store for all registry data.
-
-When a new package is added to the App-V Client, a copy of the REGISTRY.DAT file from the package is created at `%ProgramData%\Microsoft\AppV\Client\VREG\{Version GUID}.dat`. The name of the file is the version GUID with the .DAT extension. The reason this copy is made is to ensure that the actual hive file in the package is never in use, which would prevent the removal of the package at a later time.
-
-
-
-
-
-When the first application from the package is launched on the client, the client stages or copies the contents out of the hive file, re-creating the package registry data in an alternate location `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\AppV\Client\Packages\PackageGuid\Versions\VersionGuid\REGISTRY`. The staged registry data has two distinct types of machine data and user data. Machine data is shared across all users on the machine. User data is staged for each user to a userspecific location `HKCU\Software\Microsoft\AppV\Client\Packages\PackageGuid\Registry\User`. The machine data is ultimately removed at package removal time, and the user data is removed on a user unpublish operation.
-
-### Package registry staging vs. connection group registry staging
-
-When connection groups are present, the previous process of staging the registry holds true, but instead of having one hive file to process, there are more than one. The files are processed in the order in which they appear in the connection group XML, with the first writer winning any conflicts.
-
-The staged registry persists the same way as in the single package case. Staged user registry data remains for the connection group until it is disabled; staged machine registry data is removed on connection group removal.
-
-### Virtual registry
-
-The purpose of the virtual registry (VREG) is to provide a single merged view of the package registry and the native registry to applications. It also provides copy-on-write (COW) functionality – that is any changes made to the registry from the context of a virtual process are made to a separate COW location. This means that the VREG must combine up to three separate registry locations into a single view based on the populated locations in the registry COW -> package -> native. When a request is made for a registry data it will locate in order until it finds the data it was requesting. Meaning if there is a value stored in a COW location it will not proceed to other locations, however, if there is no data in the COW location it will proceed to the Package and then Native location until it finds the appropriate data.
-
-### Registry locations
-
-There are two package registry locations and two connection group locations where the App-V Client stores registry information, depending on whether the Package is published individually or as part of a connection group. There are three COW locations for packages and three for connection groups, which are created and managed by the VREG. Settings for packages and connection groups are not shared:
-
-**Single Package VReg:**
-
-
-
-
-
-
-
-
-
Location
-
Description
-
-
-
COW
-
-
Machine Registry\Client\Packages\PkgGUID\REGISTRY (Only elevate process can write)
-
User Registry\Client\Packages\PkgGUID\REGISTRY (User Roaming anything written under HKCU except Software\Classes
-
User Registry Classes\Client\Packages\PkgGUID\REGISTRY (HKCU\Software\Classes writes and HKLM for non elevated process)
User Registry Classes\Client\PackageGroups\GrpGUID\Versions\VerGUID\REGISTRY
-
-
-
-
Native
-
-
Native application registry location
-
-
-
-
-
-
-
-
-
-There are two COW locations for HKLM; elevated and non-elevated processes. Elevated processes always write HKLM changes to the secure COW under HKLM. Non-elevated processes always write HKLM changes to the non-secure COW under HKCU\\Software\\Classes. When an application reads changes from HKLM, elevated processes will read changes from the secure COW under HKLM. Non-elevated reads from both, favoring the changes made in the unsecure COW first.
-
-### Pass-through keys
-
-Pass-through keys enable an administrator to configure certain keys so they can only be read from the native registry, bypassing the Package and COW locations. Pass-through locations are global to the machine (not package specific) and can be configured by adding the path to the key, which should be treated as pass-through to the **REG\_MULTI\_SZ** value called **PassThroughPaths** of the key `HKLM\Software\Microsoft\AppV\Subsystem\VirtualRegistry`. Any key that appears under this multi-string value (and their children) will be treated as pass-through.
-
-The following locations are configured as pass-through locations by default:
-
-- HKEY\_CURRENT\_USER\\SOFTWARE\\Classes\\Local Settings\\Software\\Microsoft\\Windows\\CurrentVersion\\AppModel
-
-- HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Classes\\Local Settings\\Software\\Microsoft\\Windows\\CurrentVersion\\AppModel
-
-- HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\WINEVT
-
-- HKEY\_LOCAL\_MACHINE\\SYSTEM\\CurrentControlSet\\services\\eventlog\\Application
-
-- HKEY\_LOCAL\_MACHINE\\SYSTEM\\CurrentControlSet\\Control\\WMI\\Autologger
-
-- HKEY\_CURRENT\_USER\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Internet Settings
-
-- HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\Perflib
-
-- HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Policies
-
-- HKEY\_CURRENT\_USER\\SOFTWARE\\Policies
-
-The purpose of Pass-through keys is to ensure that a virtual application does not write registry data in the VReg that is required for non-virtual applications for successful operation or integration. The Policies key ensures that Group Policy based settings set by the administrator are utilized and not per package settings. The AppModel key is required for integration with Windows Modern UI based applications. It is recommend that administers do not modify any of the default pass-through keys, but in some instances, based on application behavior may require adding additional pass-through keys.
-
-## App-V package store behavior
-
-
-App-V 5 manages the Package Store, which is the location where the expanded asset files from the appv file are stored. By default, this location is stored at %ProgramData%\\App-V, and is limited in terms of storage capabilities only by free disk space. The package store is organized by the GUIDs for the package and version as mentioned in the previous section.
-
-### Add packages
-
-App-V Packages are staged upon addition to the computer with the App-V Client. The App-V Client provides on-demand staging. During publishing or a manual Add-AppVClientPackage, the data structure is built in the package store (c:\\programdata\\App-V\\{PkgGUID}\\{VerGUID}). The package files identified in the publishing block defined in the StreamMap.xml are added to the system and the top level folders and child files staged to ensure proper application assets exist at launch.
-
-### Mounting packages
-
-Packages can be explicitly loaded using the PowerShell `Mount-AppVClientPackage` or by using the **App-V Client UI** to download a package. This operation completely loads the entire package into the package store.
-
-### Streaming packages
-
-The App-V Client can be configured to change the default behavior of streaming. All streaming policies are stored under the following registry key: `HKEY_LOCAL_MAcHINE\Software\Microsoft\AppV\Client\Streaming`. Policies are set using the PowerShell cmdlet `Set-AppvClientConfiguration`. The following policies apply to Streaming:
-
-
-
-
-
-
-
-
-
Policy
-
Description
-
-
-
-
-
AllowHighCostLaunch
-
On Windows 8 and later, it allows streaming over 3G and cellular networks
-
-
-
AutoLoad
-
Specifies the Background Load setting:
-
0 - Disabled
-
1 – Previously Used Packages only
-
2 – All Packages
-
-
-
PackageInstallationRoot
-
The root folder for the package store in the local machine
-
-
-
PackageSourceRoot
-
The root override where packages should be streamed from
-
-
-
SharedContentStoreMode
-
Enables the use of Shared Content Store for VDI scenarios
-
-
-
-
-
-
-
-
-These settings affect the behavior of streaming App-V package assets to the client. By default, App-V only downloads the assets required after downloading the initial publishing and primary feature blocks. There are three specific behaviors around streaming packages that must be explained:
-
-- Background Streaming
-
-- Optimized Streaming
-
-- Stream Faults
-
-### Background streaming
-
-The PowerShell cmdlet `Get-AppvClientConfiguration` can be used to determine the current mode for background streaming with the AutoLoad setting and modified with the cmdlet Set-AppvClientConfiguration or from the registry (HKLM\\SOFTWARE\\Microsoft\\AppV\\ClientStreaming key). Background streaming is a default setting where the Autoload setting is set to download previously used packages. The behavior based on default setting (value=1) downloads App-V data blocks in the background after the application has been launched. This setting can be disabled all together (value=0) or enabled for all packages (value=2), whether they have been launched.
-
-### Optimized streaming
-
-App-V packages can be configured with a primary feature block during sequencing. This setting allows the sequencing engineer to monitor launch files for a specific application, or applications, and mark the blocks of data in the App-V package for streaming at first launch of any application in the package.
-
-### Stream faults
-
-After the initial stream of any publishing data and the primary feature block, requests for additional files perform stream faults. These blocks of data are downloaded to the package store on an as-needed basis. This allows a user to download only a small part of the package, typically enough to launch the package and run normal tasks. All other blocks are downloaded when a user initiates an operation that requires data not currently in the package store.
-
-For more information on App-V Package streaming visit: .
-
-Sequencing for streaming optimization is available at: .
-
-### Package upgrades
-
-App-V Packages require updating throughout the lifecycle of the application. App-V Package upgrades are similar to the package publish operation, as each version will be created in its own PackageRoot location: `%ProgramData%\App-V\{PkgGUID}\{newVerGUID}`. The upgrade operation is optimized by creating hard links to identical- and streamed-files from other versions of the same package.
-
-### Package removal
-
-The behavior of the App-V Client when packages are removed depends on the method used for removal. Using an App-V full infrastructure to unpublish the application, the user catalog files (machine catalog for globally published applications) are removed, but retains the package store location and COW locations. When the PowerShell cmdlet `Remove-AppVClientPackge` is used to remove an App-V Package, the package store location is cleaned. Remember that unpublishing an App-V Package from the Management Server does not perform a Remove operation. Neither operation will remove the Package Store package files.
-
-## Roaming registry and data
-
-
-App-V 5 is able to provide a near-native experience when roaming, depending on how the application being used is written. By default, App-V roams AppData that is stored in the roaming location, based on the roaming configuration of the operating system. Other locations for storage of file-based data do not roam from computer to computer, since they are in locations that are not roamed.
-
-### Roaming requirements and user catalog data storage
-
-App-V stores data, which represents the state of the user’s catalog, in the form of:
-
-- Files under %appdata%\\Microsoft\\AppV\\Client\\Catalog
-
-- Registry settings under `HKEY_CURRENT_USER\Software\Microsoft\AppV\Client\Packages`
-
-Together, these files and registry settings represent the user’s catalog, so either both must be roamed, or neither must be roamed for a given user. App-V does not support roaming %AppData%, but not roaming the user’s profile (registry), or vice versa.
-
-**Note**
-The **Repair-AppvClientPackage** cmdlet does not repair the publishing state of packages, where the user’s App-V state under `HKEY_CURRENT_USER` is missing or mismatched with the data in %appdata%.
-
-
-
-### Registry-based data
-
-App-V registry roaming falls into two scenarios, as shown in the following table.
-
-
-
-
-
-
-
-
-
Scenario
-
Description
-
-
-
-
-
Applications that are run as standard users
-
When a standard user launches an App-V application, both HKLM and HKCU for App-V applications are stored in the HKCU hive on the machine. This presents as two distinct paths:
The locations are enabled for roaming based on the operating system settings.
-
-
-
Applications that are run with elevation
-
When an application is launched with elevation:
-
-
HKLM data is stored in the HKLM hive on the local computer
-
HKCU data is stored in the User Registry location
-
-
In this scenario, these settings are not roamed with normal operating system roaming configurations, and the resulting registry keys and values are stored in the following location:
-
-
-
-### App-V and folder redirection
-
-App-V 5.1 supports folder redirection of the roaming AppData folder (%AppData%). When the virtual environment is started, the roaming AppData state from the user’s roaming AppData directory is copied to the local cache. Conversely, when the virtual environment is shut down, the local cache that is associated with a specific user’s roaming AppData is transferred to the actual location of that user’s roaming AppData directory.
-
-A typical package has several locations mapped in the user’s backing store for settings in both AppData\\Local and AppData\\Roaming. These locations are the Copy on Write locations that are stored per user in the user’s profile, and that are used to store changes made to the package VFS directories and to protect the default package VFS.
-
-The following table shows local and roaming locations, when folder redirection has not been implemented.
-
-
-
-
-
-
-
-The following table shows local and roaming locations, when folder redirection has been implemented for %AppData%, and the location has been redirected (typically to a network location).
-
-
-
-
-
-
-
-The current App-V Client VFS driver cannot write to network locations, so the App-V Client detects the presence of folder redirection and copies the data on the local drive during publishing and when the virtual environment starts. After the user closes the App-V application and the App-V Client closes the virtual environment, the local storage of the VFS AppData is copied back to the network, enabling roaming to additional machines, where the process will be repeated. The detailed steps of the processes are:
-
-1. During publishing or virtual environment startup, the App-V Client detects the location of the AppData directory.
-
-2. If the roaming AppData path is local or ino AppData\\Roaming location is mapped, nothing happens.
-
-3. If the roaming AppData path is not local, the VFS AppData directory is mapped to the local AppData directory.
-
-This process solves the problem of a non-local %AppData% that is not supported by the App-V Client VFS driver. However, the data stored in this new location is not roamed with folder redirection. All changes during the running of the application happen to the local AppData location and must be copied to the redirected location. The detailed steps of this process are:
-
-1. App-V application is shut down, which shuts down the virtual environment.
-
-2. The local cache of the roaming AppData location is compressed and stored in a ZIP file.
-
-3. A timestamp at the end of the ZIP packaging process is used to name the file.
-
-4. The timestamp is recorded in the registry: HKEY\_CURRENT\_USER\\Software\\Microsoft\\AppV\\Client\\Packages\\<GUID>\\AppDataTime as the last known AppData timestamp.
-
-5. The folder redirection process is called to evaluate and initiate the ZIP file uploaded to the roaming AppData directory.
-
-The timestamp is used to determine a “last writer wins” scenario if there is a conflict and is used to optimize the download of the data when the App-V application is published or the virtual environment is started. Folder redirection will make the data available from any other clients covered by the supporting policy and will initiate the process of storing the AppData\\Roaming data to the local AppData location on the client. The detailed processes are:
-
-1. The user starts the virtual environment by starting an application.
-
-2. The application’s virtual environment checks for the most recent time stamped ZIP file, if present.
-
-3. The registry is checked for the last known uploaded timestamp, if present.
-
-4. The most recent ZIP file is downloaded unless the local last known upload timestamp is greater than or equal to the timestamp from the ZIP file.
-
-5. If the local last known upload timestamp is earlier than that of the most recent ZIP file in the roaming AppData location, the ZIP file is extracted to the local temp directory in the user’s profile.
-
-6. After the ZIP file is successfully extracted, the local cache of the roaming AppData directory is renamed and the new data is moved into place.
-
-7. The renamed directory is deleted and the application opens with the most recently saved roaming AppData data.
-
-This completes the successful roaming of application settings that are present in AppData\\Roaming locations. The only other condition that must be addressed is a package repair operation. The details of the process are:
-
-1. During repair, detect if the path to the user’s roaming AppData directory is not local.
-
-2. Map the non-local roaming AppData path targets are recreated the expected roaming and local AppData locations.
-
-3. Delete the timestamp stored in the registry, if present.
-
-This process will re-create both the local and network locations for AppData and remove the registry record of the timestamp.
-
-## App-V client application lifecycle management
-
-
-In an App-V Full Infrastructure, after applications are sequenced they are managed and published to users or computers via the App-V Management and Publishing servers. This section details the operations that occur during the common App-V application lifecycle operations (Add, publishing, launch, upgrade, and removal) and the file and registry locations that are changed and modified from the App-V Client perspective. The App-V Client operations are performed as a series of PowerShell commands initiated on the computer running the App-V Client.
-
-This document focuses on App-V Full Infrastructure solutions. For specific information on App-V Integration with Configuration Manager 2012 visit: .
-
-The App-V application lifecycle tasks are triggered at user login (default), machine startup, or as background timed operations. The settings for the App-V Client operations, including Publishing Servers, refresh intervals, package script enablement, and others, are configured during setup of the client or post-setup with PowerShell commands. See the How to Deploy the Client section on TechNet at: [How to Deploy the App-V Client](how-to-deploy-the-app-v-client-51gb18030.md) or utilize the PowerShell:
-
-```powershell
-get-command *appv*
-```
-
-### Publishing refresh
-
-The publishing refresh process is comprised of several smaller operations that are performed on the App-V Client. Since App-V is an application virtualization technology and not a task scheduling technology, the Windows Task Scheduler is utilized to enable the process at user logon, machine startup, and at scheduled intervals. The configuration of the client during setup listed above is the preferred method when distributing the client to a large group of computers with the correct settings. These client settings can be configured with the following PowerShell cmdlets:
-
-- **Add-AppVPublishingServer:** Configures the client with an App-V Publishing Server that provides App-V packages.
-
-- **Set-AppVPublishingServer:** Modifies the current settings for the App-V Publishing Server.
-
-- **Set-AppVClientConfiguration:** Modifies the currents settings for the App-V Client.
-
-- **Sync-AppVPublishingServer:** Initiates an App-V Publishing Refresh process manually. This is also utilized in the scheduled tasks created during configuration of the publishing server.
-
-The focus of the following sections is to detail the operations that occur during different phases of an App-V Publishing Refresh. The topics include:
-
-- Adding an App-V Package
-
-- Publishing an App-V Package
-
-### Adding an App-V package
-
-Adding an App-V package to the client is the first step of the publishing refresh process. The end result is the same as the `Add-AppVClientPackage` cmdlet in PowerShell, except during the publishing refresh add process, the configured publishing server is contacted and passes a high-level list of applications back to the client to pull more detailed information and not a single package add operation. The process continues by configuring the client for package or connection group additions or updates, then accesses the appv file. Next, the contents of the appv file are expanded and placed on the local operating system in the appropriate locations. The following is a detailed workflow of the process, assuming the package is configured for Fault Streaming.
-
-**How to add an App-V package**
-
-1. Manual initiation via PowerShell or Task Sequence initiation of the Publishing Refresh process.
-
- 1. The App-V Client makes an HTTP connection and requests a list of applications based on the target. The Publishing refresh process supports targeting machines or users.
-
- 2. The App-V Publishing Server uses the identity of the initiating target, user or machine, and queries the database for a list of entitled applications. The list of applications is provided as an XML response, which the client uses to send additional requests to the server for more information on a per package basis.
-
-2. The Publishing Agent on the App-V Client performs all actions below serialized.
-
- Evaluate any connection groups that are unpublished or disabled, since package version updates that are part of the connection group cannot be processed.
-
-3. Configure the packages by identifying an Add or Update operations.
-
- 1. The App-V Client utilizes the AppX API from Windows and accesses the appv file from the publishing server.
-
- 2. The package file is opened and the AppXManifest.xml and StreamMap.xml are downloaded to the Package Store.
-
- 3. Completely stream publishing block data defined in the StreamMap.xml. Stores the publishing block data in the Package Store\\PkgGUID\\VerGUID\\Root.
-
- - Icons: Targets of extension points.
-
- - Portable Executable Headers (PE Headers): Targets of extension points that contain the base information about the image need on disk, directly accessed or via file types.
-
- - Scripts: Download scripts directory for use throughout the publishing process.
-
- 4. Populate the Package store:
-
- 1. Create sparse files on disk that represent the extracted package for any directories listed.
-
- 2. Stage top level files and directories under root.
-
- 3. All other files are created when the directory is listed as sparse on disk and streamed on demand.
-
- 5. Create the machine catalog entries. Create the Manifest.xml and DeploymentConfiguration.xml from the package files (if no DeploymentConfiguration.xml file in the package a placeholder is created).
-
- 6. Create location of the package store in the registry HKLM\\Software\\Microsoft\\AppV\\Client\\Packages\\PkgGUID\\Versions\\VerGUID\\Catalog
-
- 7. Create the Registry.dat file from the package store to %ProgramData%\\Microsoft\\AppV\\Client\\VReg\\{VersionGUID}.dat
-
- 8. Register the package with the App-V Kernel Mode Driver HKLM\\Microsoft\\Software\\AppV\\MAV
-
- 9. Invoke scripting from the AppxManifest.xml or DeploymentConfig.xml file for Package Add timing.
-
-4. Configure Connection Groups by adding and enabling or disabling.
-
-5. Remove objects that are not published to the target (user or machine).
-
- **Note**
- This will not perform a package deletion but rather remove integration points for the specific target (user or machine) and remove user catalog files (machine catalog files for globally published).
-
-
-
-6. Invoke background load mounting based on client configuration.
-
-7. Packages that already have publishing information for the machine or user are immediately restored.
-
- **Note**
- This condition occurs as a product of removal without unpublishing with background addition of the package.
-
-
-
-This completes an App-V package add of the publishing refresh process. The next step is publishing the package to the specific target (machine or user).
-
-
-
-### Publishing an App-V package
-
-During the Publishing Refresh operation, the specific publishing operation (Publish-AppVClientPackage) adds entries to the user catalog, maps entitlement to the user, identifies the local store, and finishes by completing any integration steps. The following are the detailed steps.
-
-**How to publish and App-V package**
-
-1. Package entries are added to the user catalog
-
- 1. User targeted packages: the UserDeploymentConfiguration.xml and UserManifest.xml are placed on the machine in the User Catalog
-
- 2. Machine targeted (global) packages: the UserDeploymentConfiguration.xml is placed in the Machine Catalog
-
-2. Register the package with the kernel mode driver for the user at HKLM\\Software\\Microsoft\\AppV\\MAV
-
-3. Perform integration tasks.
-
- 1. Create extension points.
-
- 2. Store backup information in the user’s registry and roaming profile (Shortcut Backups).
-
- **Note**
- This enables restore extension points if the package is unpublished.
-
-
-
- 3. Run scripts targeted for publishing timing.
-
-Publishing an App-V Package that is part of a Connection Group is very similar to the above process. For connection groups, the path that stores the specific catalog information includes PackageGroups as a child of the Catalog Directory. Review the machine and users catalog information above for details.
-
-
-
-### Application launch
-
-After the Publishing Refresh process, the user launches and subsequently re-launches an App-V application. The process is very simple and optimized to launch quickly with a minimum of network traffic. The App-V Client checks the path to the user catalog for files created during publishing. After rights to launch the package are established, the App-V Client creates a virtual environment, begins streaming any necessary data, and applies the appropriate manifest and deployment configuration files during virtual environment creation. With the virtual environment created and configured for the specific package and application, the application starts.
-
-**How to launch App-V applications**
-
-1. User launches the application by clicking on a shortcut or file type invocation.
-
-2. The App-V Client verifies existence in the User Catalog for the following files
-
- - UserDeploymentConfiguration.xml
-
- - UserManifest.xml
-
-3. If the files are present, the application is entitled for that specific user and the application will start the process for launch. There is no network traffic at this point.
-
-4. Next, the App-V Client checks that the path for the package registered for the App-V Client service is found in the registry.
-
-5. Upon finding the path to the package store, the virtual environment is created. If this is the first launch, the Primary Feature Block downloads if present.
-
-6. After downloading, the App-V Client service consumes the manifest and deployment configuration files to configure the virtual environment and all App-V subsystems are loaded.
-
-7. The Application launches. For any missing files in the package store (sparse files), App-V will stream fault the files on an as needed basis.
-
- 
-
-### Upgrading an App-V package
-
-The App-V 5 package upgrade process differs from the older versions of App-V. App-V supports multiple versions of the same package on a machine entitled to different users. Package versions can be added at any time as the package store and catalogs are updated with the new resources. The only process specific to the addition of new version resources is storage optimization. During an upgrade, only the new files are added to the new version store location and hard links are created for unchanged files. This reduces the overall storage by only presenting the file on one disk location and then projecting it into all folders with a file location entry on the disk. The specific details of upgrading an App-V Package are as follows:
-
-**How to upgrade an App-V package**
-
-1. The App-V Client performs a Publishing Refresh and discovers a newer version of an App-V Package.
-
-2. Package entries are added to the appropriate catalog for the new version
-
- 1. User targeted packages: the UserDeploymentConfiguration.xml and UserManifest.xml are placed on the machine in the user catalog at appdata\\roaming\\Microsoft\\AppV\\Client\\Catalog\\Packages\\PkgGUID\\VerGUID
-
- 2. Machine targeted (global) packages: the UserDeploymentConfiguration.xml is placed in the machine catalog at %programdata%\\Microsoft\\AppV\\Client\\Catalog\\Packages\\PkgGUID\\VerGUID
-
-3. Register the package with the kernel mode driver for the user at HKLM\\Software\\Microsoft\\AppV\\MAV
-
-4. Perform integration tasks.
-
- - Integrate extensions points (EP) from the Manifest and Dynamic Configuration files.
-
- 1. File based EP data is stored in the AppData folder utilizing Junction Points from the package store.
-
- 2. Version 1 EPs already exist when a new version becomes available.
-
- 3. The extension points are switched to the Version 2 location in machine or user catalogs for any newer or updated extension points.
-
-5. Run scripts targeted for publishing timing.
-
-6. Install Side by Side assemblies as required.
-
-### Upgrading an in-use App-V package
-
-**Starting in App-V 5 SP2**: If you try to upgrade a package that is in use by an end user, the upgrade task is placed in a pending state. The upgrade will run later, according to the following rules:
-
-
-
-
-
-
-
-
-
Task type
-
Applicable rule
-
-
-
-
-
User-based task, e.g., publishing a package to a user
-
The pending task will be performed after the user logs off and then logs back on.
-
-
-
Globally based task, e.g., enabling a connection group globally
-
The pending task will be performed when the computer is shut down and then restarted.
-
-
-
-
-
-
-When a task is placed in a pending state, the App-V client also generates a registry key for the pending task, as follows:
-
-
-
-
-
-The following operations must be completed before users can use the newer version of the package:
-
-
-
-
-
-
-
-
-
Task
-
Details
-
-
-
-
-
Add the package to the computer
-
This task is computer specific and you can perform it at any time by completing the steps in the Package Add section above.
-
-
-
Publish the package
-
See the Package Publishing section above for steps. This process requires that you update extension points on the system. End users cannot be using the application when you complete this task.
-
-
-
-
-
-
-Use the following example scenarios as a guide for updating packages.
-
-
-
-
-
-
-
-
-
Scenario
-
Requirements
-
-
-
-
-
App-V package is not in use when you try to upgrade
-
None of the following components of the package can be in use: virtual application, COM server, or shell extensions.
-
The administrator publishes a newer version of the package and the upgrade works the next time a component or application inside the package is launched. The new version of the package is streamed and run. Nothing has changed in this scenario in App-V 5 SP2 from previous releases of App-V 5.
-
-
-
App-V package is in use when the administrator publishes a newer version of the package
-
The upgrade operation is set to pending by the App-V Client, which means that it is queued and carried out later when the package is not in use.
-
If the package application is in use, the user shuts down the virtual application, after which the upgrade can occur.
-
If the package has shell extensions (Office 2013), which are permanently loaded by Windows Explorer, the user cannot be logged in. Users must log off and the log back in to initiate the App-V package upgrade.
-
-
-
-
-
-
-### Global vs user publishing
-
-App-V Packages can be published in one of two ways; User which entitles an App-V package to a specific user or group of users and Global which entitles the App-V package to the entire machine for all users of the machine. Once a package upgrade has been pended and the App-V package is not in use, consider the two types of publishing:
-
-- **Globally published**: the application is published to a machine; all users on that machine can use it. The upgrade will happen when the App-V Client Service starts, which effectively means a machine restart.
-
-- **User published**: the application is published to a user. If there are multiple users on the machine, the application can be published to a subset of the users. The upgrade will happen when the user logs in or when it is published again (periodically, ConfigMgr Policy refresh and evaluation, or an App-V periodic publishing/refresh, or explicitly via PowerShell commands).
-
-### Removing an App-V package
-
-Removing App-V applications in a Full Infrastructure is an unpublish operation, and does not perform a package removal. The process is the same as the publish process above, but instead of adding the removal process reverses the changes that have been made for App-V Packages.
-
-### Repairing an App-V package
-
-The repair operation is very simple but may affect many locations on the machine. The previously mentioned Copy on Write (COW) locations are removed, and extension points are de-integrated and then re-integrated. Please review the COW data placement locations by reviewing where they are registered in the registry. This operation is done automatically and there is no administrative control other than initiating a Repair operation from the App-V Client Console or via PowerShell (Repair-AppVClientPackage).
-
-## Integration of App-V packages
-
-
-The App-V Client and package architecture provides specific integration with the local operating system during the addition and publishing of packages. Three files define the integration or extension points for an App-V Package:
-
-- AppXManifest.xml: Stored inside of the package with fallback copies stored in the package store and the user profile. Contains the options created during the sequencing process.
-
-- DeploymentConfig.xml: Provides configuration information of computer and user based integration extension points.
-
-- UserConfig.xml: A subset of the Deploymentconfig.xml that only provides user- based configurations and only targets user-based extension points.
-
-### Rules of integration
-
-When App-V applications are published to a computer with the App-V Client, some specific actions take place as described in the list below:
-
-- Global Publishing: Shortcuts are stored in the All Users profile location and other extension points are stored in the registry in the HKLM hive.
-
-- User Publishing: Shortcuts are stored in the current user account profile and other extension points are stored in the registry in the HKCU hive.
-
-- Backup and Restore: Existing native application data and registry (such as FTA registrations) are backed up during publishing.
-
- 1. App-V packages are given ownership based on the last integrated package where the ownership is passed to the newest published App-V application.
-
- 2. Ownership transfers from one App-V package to another when the owning App-V package is unpublished. This will not initiate a restore of the data or registry.
-
- 3. Restore the backed up data when the last package is unpublished or removed on a per extension point basis.
-
-### Extension points
-
-The App-V publishing files (manifest and dynamic configuration) provide several extension points that enable the application to integrate with the local operating system. These extension points perform typical application installation tasks, such as placing shortcuts, creating file type associations, and registering components. As these are virtualized applications that are not installed in the same manner a traditional application, there are some differences. The following is a list of extension points covered in this section:
-
-- Shortcuts
-
-- File Type Associations
-
-- Shell Extensions
-
-- COM
-
-- Software Clients
-
-- Application capabilities
-
-- URL Protocol Handler
-
-- AppPath
-
-- Virtual Application
-
-### Shortcuts
-
-The short cut is one of the basic elements of integration with the OS and is the interface for direct user launch of an App-V application. During the publishing and unpublishing of App-V applications.
-
-From the package manifest and dynamic configuration XML files, the path to a specific application executable can be found in a section similar to the following:
-
-```xml
-
-
- [{Common Desktop}]\Adobe Reader 9.lnk
- [{AppVPackageRoot}]\Reader\AcroRd32.exe
- [{Windows}]\Installer\{AC76BA86-7AD7-1033-7B44-A94000000001}\SC_Reader.ico
-
-
- 1
- [{AppVPackageRoot}]\Reader\AcroRd32.exe
-
-
-```
-
-As mentioned previously, the App-V shortcuts are placed by default in the user’s profile based on the refresh operation. Global refresh places shortcuts in the All Users profile and user refresh stores them in the specific user’s profile. The actual executable is stored in the Package Store. The location of the ICO file is a tokenized location in the App-V package.
-
-### File type associations
-
-The App-V Client manages the local operating system File Type Associations during publishing, which enables users to use file type invocations or to open a file with a specifically registered extension (.docx) to start an App-V application. File type associations are present in the manifest and dynamic configuration files as represented in the example below:
-
-```xml
-
-
-
- .xdp
- AcroExch.XDPDoc
- application/vnd.adobe.xdp+xml
-
-
- AcroExch.XDPDoc
- Adobe Acrobat XML Data Package File
- 65536
- [{Windows}]\Installer\{AC76BA86-7AD7-1033-7B44-A94000000001}\XDPFile_8.ico
-
- Read
-
- [{AppVPackageRoot}]\Reader\AcroRd32.exe
- Open
- "[{AppVPackageRoot}]\Reader\AcroRd32.exe" "%1"
-
-
- [{AppVPackageRoot}]\Reader\AcroRd32.exe
- Printto
- "[{AppVPackageRoot}]\Reader\AcroRd32.exe" /t "%1" "%2" "%3" "%4"
-
-
- [{AppVPackageRoot}]\Reader\AcroRd32.exe
- Read
- Open with Adobe Reader 9
- "[{AppVPackageRoot}]\Reader\AcroRd32.exe" "%1"
-
-
-
-
-
-```
-
-**Note**
-In this example:
-
-- `.xdp` is the extension
-
-- `AcroExch.XDPDoc` is the ProgId value (which points to the adjoining ProgId)
-
-- `"[{AppVPackageRoot}]\Reader\AcroRd32.exe" "%1"` is the command line, which points to the application executable
-
-
-
-### Shell extensions
-
-Shell extensions are embedded in the package automatically during the sequencing process. When the package is published globally, the shell extension gives users the same functionality as if the application were locally installed. The application requires no additional setup or configuration on the client to enable the shell extension functionality.
-
-**Requirements for using shell extensions:**
-
-- Packages that contain embedded shell extensions must be published globally.
-
-- The “bitness” of the application, Sequencer, and App-V client must match, or the shell extensions won’t work. For example:
-
- - The version of the application is 64-bit.
-
- - The Sequencer is running on a 64-bit computer.
-
- - The package is being delivered to a 64-bit App-V client computer.
-
-The following table displays the supported shell extensions.
-
-
-
-
-
-
-
-
-
Handler
-
Description
-
-
-
-
-
Context menu handler
-
Adds menu items to the context menu. It is called before the context menu is displayed.
-
-
-
Drag-and-drop handler
-
Controls the action upon right-click drag-and-drop and modifies the context menu that appears.
-
-
-
Drop target handler
-
Controls the action after a data object is dragged-and-dropped over a drop target such as a file.
-
-
-
Data object handler
-
Controls the action after a file is copied to the clipboard or dragged-and-dropped over a drop target. It can provide additional clipboard formats to the drop target.
-
-
-
Property sheet handler
-
Replaces or adds pages to the property sheet dialog box of an object.
-
-
-
Infotip handler
-
Allows retrieving flags and infotip information for an item and displaying it inside a popup tooltip upon mouse- hover.
-
-
-
Column handler
-
Allows creating and displaying custom columns in Windows Explorer Details view. It can be used to extend sorting and grouping.
-
-
-
Preview handler
-
Enables a preview of a file to be displayed in the Windows Explorer Preview Pane.
-
-
-
-
-
-
-### COM
-
-The App-V Client supports publishing applications with support for COM integration and virtualization. COM integration allows the App-V Client to register COM objects on the local operating system and virtualization of the objects. For the purposes of this document, the integration of COM objects requires additional detail.
-
-App-V supports registering COM objects from the package to the local operating system with two process types: Out-of-process and in-process. Registering COM objects is accomplished with one or a combination of multiple modes of operation for a specific App-V package that includes off, Isolated, and Integrated. The integrated mode is configured for either the out-of-process or in-process type. Configuration of COM modes and types is accomplished with dynamic configuration files (deploymentconfig.xml or userconfig.xml).
-
-Details on App-V integration are available at: .
-
-### Software clients and application capabilities
-
-App-V supports specific software clients and application capabilities extension points that enable virtualized applications to be registered with the software client of the operating system. This enables users to select default programs for operations like email, instant messaging, and media player. This operation is performed in the control panel with the Set Program Access and Computer Defaults, and configured during sequencing in the manifest or dynamic configuration files. Application capabilities are only supported when the App-V applications are published globally.
-
-Example of software client registration of an App-V based mail client.
-
-```xml
-
-
-
-
-
-
- Mozilla Thunderbird
- Mozilla Thunderbird
- [{ProgramFilesX86}]\Mozilla Thunderbird\thunderbird.exe,0
-
-
- "[{ProgramFilesX86}]\Mozilla Thunderbird\uninstall\helper.exe" /SetAsDefaultAppGlobal
- "[{ProgramFilesX86}]\Mozilla Thunderbird\uninstall\helper.exe" /HideShortcuts
- "[{ProgramFilesX86}]\Mozilla Thunderbird\uninstall\helper.exe" /ShowShortcuts
-
- 1
-
-
-
- [{ProgramFilesX86}]\Mozilla Thunderbird\thunderbird.exe
- "[{ProgramFilesX86}]\Mozilla Thunderbird\thunderbird.exe" -mail
-
- [{ProgramFilesX86}]\Mozilla Thunderbird\mozMapi32_InUse.dll
-
- Thunderbird URL
- 2
- [{ProgramFilesX86}]\Mozilla Thunderbird\thunderbird.exe,0
-
- [{ProgramFilesX86}]\Mozilla Thunderbird\thunderbird.exe
- "[{ProgramFilesX86}]\Mozilla Thunderbird\thunderbird.exe" -osint -compose "%1"
-
-
-
-
-
-
-
-```
-
-**Note**
-In this example:
-
-- `` is the overall Software Clients setting to integrate Email clients
-
-- `` is the flag to set a particular Email client as the default Email client
-
-- `[{ProgramFilesX86}]\Mozilla Thunderbird\mozMapi32_InUse.dll` is the MAPI dll registration
-
-
-
-### URL Protocol handler
-
-Applications do not always specifically called virtualized applications utilizing file type invocation. For, example, in an application that supports embedding a mailto: link inside a document or web page, the user clicks on a mailto: link and expects to get their registered mail client. App-V supports URL Protocol handlers that can be registered on a per-package basis with the local operating system. During sequencing, the URL protocol handlers are automatically added to the package.
-
-For situations where there is more than one application that could register the specific URL Protocol handler, the dynamic configuration files can be utilized to modify the behavior and suppress or disable this feature for an application that should not be the primary application launched.
-
-### AppPath
-
-The AppPath extension point supports calling App-V applications directly from the operating system. This is typically accomplished from the Run or Start Screen, depending on the operating system, which enables administrators to provide access to App-V applications from operating system commands or scripts without calling the specific path to the executable. It therefore avoids modifying the system path environment variable on all systems, as it is accomplished during publishing.
-
-The AppPath extension point is configured either in the manifest or in the dynamic configuration files and is stored in the registry on the local machine during publishing for the user. For additional information on AppPath review: .
-
-### Virtual application
-
-This subsystem provides a list of applications captured during sequencing which is usually consumed by other App-V components. Integration of extension points belonging to a particular application can be disabled using dynamic configuration files. For example, if a package contains two applications, it is possible to disable all extension points belonging to one application, in order to allow only integration of extension points of other application.
-
-### Extension point rules
-
-The extension points described above are integrated into the operating system based on how the packages has been published. Global publishing places extension points in public machine locations, where user publishing places extension points in user locations. For example a shortcut that is created on the desktop and published globally will result in the file data for the shortcut (%Public%\\Desktop) and the registry data (HKLM\\Software\\Classes). The same shortcut would have file data (%UserProfile%\\Desktop) and registry data (HKCU\\Software\\Classes).
-
-Extension points are not all published the same way, where some extension points will require global publishing and others require sequencing on the specific operating system and architecture where they are delivered. Below is a table that describes these two key rules.
-
-
-
-
-
-
-
-
-
-
Virtual Extension
-
Requires target OS Sequencing
-
Requires Global Publishing
-
-
-
-
-
Shortcut
-
-
-
-
-
File Type Association
-
-
-
-
-
URL Protocols
-
X
-
-
-
-
AppPaths
-
X
-
-
-
-
COM Mode
-
-
-
-
-
Software Client
-
X
-
-
-
-
Application Capabilities
-
X
-
X
-
-
-
Context Menu Handler
-
X
-
X
-
-
-
Drag-and-drop Handler
-
X
-
-
-
-
Data Object Handler
-
X
-
-
-
-
Property Sheet Handler
-
X
-
-
-
-
Infotip Handler
-
X
-
-
-
-
Column Handler
-
X
-
-
-
-
Shell Extensions
-
X
-
-
-
-
Browser Helper Object
-
X
-
X
-
-
-
Active X Object
-
X
-
X
-
-
-
-
-
-
-## Dynamic configuration processing
-
-
-Deploying App-V packages to one machine or user is very simple. However, as organizations deploy AppV applications across business lines and geographic and political boundaries, the ability to sequence an application one time with one set of settings becomes impossible. App-V was designed for this scenario, as it captures specific settings and configurations during sequencing in the Manifest file, but also supports modification with Dynamic Configuration files.
-
-App-V dynamic configuration allows for specifying a policy for a package either at the machine level or at the user level. The Dynamic Configuration files enable sequencing engineers to modify the configuration of a package, post-sequencing, to address the needs of individual groups of users or machines. In some instances it may be necessary to make modifications to the application to provide proper functionality within the App-V environment. For example, it may be necessary to make modifications to the \_\*config.xml files to allow certain actions to be performed at a specified time during the execution of the application, like disabling a mailto extension to prevent a virtualized application from overwriting that extension from another application.
-
-App-V Packages contain the Manifest file inside of the appv package file, which is representative of sequencing operations and is the policy of choice unless Dynamic Configuration files are assigned to a specific package. Post-sequencing, the Dynamic Configuration files can be modified to allow the publishing of an application to different desktops or users with different extension points. The two Dynamic Configuration Files are the Dynamic Deployment Configuration (DDC) and Dynamic User Configuration (DUC) files. This section focuses on the combination of the manifest and dynamic configuration files.
-
-### Example for dynamic configuration files
-
-The example below shows the combination of the Manifest, Deployment Configuration and User Configuration files after publishing and during normal operation. These examples are abbreviated examples of each of the files. The purpose is show the combination of the files only and not to be a complete description of the specific categories available in each of the files. For more information review the App-V 5 Sequencing Guide at:
-
-**Manifest**
-
-```xml
-
-
- [{Common Programs}]\7-Zip\7-Zip File Manager.lnk
- [{AppVPackageRoot}]\7zFM.exe
- [{AppVPackageRoot}]\7zFM exe.O.ico
-
-
-```
-
-**Deployment Configuration**
-
-```xml
-
-
-
-
-
-
-
-
-
-
-```
-
-**User Configuration**
-
-```xml
-
-
-
-
- [{Desktop}]\7-Zip\7-Zip File Manager.lnk
- [{AppVPackageRoot}]\7zFM.exe
- [{AppVPackageRoot}]\7zFM exe.O.ico
-
-
-
-
-
-
-
- [{Desktop}]\7-Zip\7-Zip File Manager.lnk
- [{AppVPackageRoot}]\7zFM.exe
- [{AppVPackageRoot}]\7zFM.exe.O.ico
-
-
- [{Common Programs}]\7-Zip\7-Zip File Manager.Ink
- [{AppVPackageRoot}]\7zFM.exe
- [{AppVPackageRoot)]\7zFM.exe.O.ico
-
-
-
-
-
-
-
-
-
-
-
-
-```
-
-## Side-by-side assemblies
-
-
-App-V supports the automatic packaging of side-by-side (SxS) assemblies during sequencing and deployment on the client during virtual application publishing. App-V 5 SP2 supports capturing SxS assemblies during sequencing for assemblies not present on the sequencing machine. And for assemblies consisting of Visual C++ (Version 8 and newer) and/or MSXML run-time, the Sequencer will automatically detect and capture these dependencies even if they were not installed during monitoring. The Side by Side assemblies feature removes the limitations of previous versions of App-V, where the App-V Sequencer did not capture assemblies already present on the sequencing workstation, and privatizing the assemblies which limited to one bit version per package. This behavior resulted in deployed App-V applications to clients missing the required SxS assemblies, causing application launch failures. This forced the packaging process to document and then ensure that all assemblies required for packages were locally installed on the user’s client operating system to ensure support for the virtual applications. Based on the number of assemblies and the lack of application documentation for the required dependencies, this task was both a management and implementation challenge.
-
-Side by Side Assembly support in App-V has the following features.
-
-- Automatic captures of SxS assembly during Sequencing, regardless of whether the assembly was already installed on the sequencing workstation.
-
-- The App-V Client automatically installs required SxS assemblies to the client computer at publishing time when they are not present.
-
-- The Sequencer reports the VC run-time dependency in Sequencer reporting mechanism.
-
-- The Sequencer allows opting to not package the assemblies that are already installed on the Sequencer, supporting scenarios where the assemblies have previously been installed on the target computers.
-
-### Automatic publishing of SxS assemblies
-
-During publishing of an App-V package with SxS assemblies the App-V Client will check for the presence of the assembly on the machine. If the assembly does not exist, the client will deploy the assembly to the machine. Packages that are part of connection groups will rely on the Side by Side assembly installations that are part of the base packages, as the connection group does not contain any information about assembly installation.
-
-**Note**
-UnPublishing or removing a package with an assembly does not remove the assemblies for that package.
-
-
-
-## Client logging
-
-
-The App-V client logs information to the Windows Event log in standard ETW format. The specific App-V events can be found in the event viewer, under Applications and Services Logs\\Microsoft\\AppV\\Client.
-
-**Note**
-In App-V 5.0 SP3, some logs were consolidated and moved to the following location:
-
-`Event logs/Applications and Services Logs/Microsoft/AppV/ServiceLog`
-
-For a list of the moved logs, see [About App-V 5.0 SP3](about-app-v-50-sp3.md#bkmk-event-logs-moved).
-
-
-
-There are three specific categories of events recorded described below.
-
-**Admin**: Logs events for configurations being applied to the App-V Client, and contains the primary warnings and errors.
-
-**Operational**: Logs the general App-V execution and usage of individual components creating an audit log of the App-V operations that have been completed on the App-V Client.
-
-**Virtual Application**: Logs virtual application launches and use of virtualization subsystems.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v5/check-reg-key-svr.md b/mdop/appv-v5/check-reg-key-svr.md
deleted file mode 100644
index 44498c1829..0000000000
--- a/mdop/appv-v5/check-reg-key-svr.md
+++ /dev/null
@@ -1,246 +0,0 @@
----
-title: Check Registry Keys before installing App-V 5.x Server
-description: Check Registry Keys before installing App-V 5.x Server
-author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
----
-
-
-# Check Registry Keys before installing App-V 5.x Server
-
-If you are upgrading the App-V Server from App-V 5.0 SP1 Hotfix Package 3 or later, complete the steps in this section before installing the App-V 5.x Server
-
-
-
-
-
-
-
-
-
When this step is required
-
You are upgrading from App-V 5.0 SP1 with any subsequent Hotfix Packages that you installed by using an .msp file.
-
-
-
Which components require that you do this step
-
Only the App-V Server components that you are upgrading.
-
-
-
When you need to do this step
-
Before you upgrade the App-V Server to App-V 5.x
-
-
-
What you need to do
-
Using the information in the following tables, update each registry key value under HKLM\Software\Microsoft\AppV\Server with the value that you provided in your original server installation. Completing this step restores registry values that may have been removed when App-V 5.0 SP1 Hotfix Packages were installed.
-
-
-
-
-
-
-**ManagementDatabase key**
-
-If you are installing the Management database, set these registry keys under `HKLM\Software\Microsoft\AppV\Server\ManagementDatabase`.
-
-
-
-
-
-
-
-
-
Key name
-
Description
-
-
-
-
-
IS_MANAGEMENT_DB_PUBLIC_ACCESS_ACCOUNT_REQUIRED
-
Describes whether a public access account is required to access non-local management databases. Value is set to “1” if it is required.
-
-
-
MANAGEMENT_DB_NAME
-
Name of the Management database.
-
-
-
MANAGEMENT_DB_PUBLIC_ACCESS_ACCOUNT
-
Account used for read (public) access to the Management database.
-
Used when IS_MANAGEMENT_DB_PUBLIC_ACCESS_ACCOUNT_REQUIRED is set to 1.
-
-
-
MANAGEMENT_DB_PUBLIC_ACCESS_ACCOUNT_SID
-
Secure identifier (SID) of the account used for read (public) access to the Management database.
-
Used when IS_MANAGEMENT_DB_PUBLIC_ACCESS_ACCOUNT_REQUIRED is set to 1.
-
-
-
MANAGEMENT_DB_SQL_INSTANCE
-
SQL Server instance for the Management database.
-
If the value is blank, the default database instance is used.
-
-
-
MANAGEMENT_DB_WRITE_ACCESS_ACCOUNT
-
Account used for write (administrator) access to the Management database.
-
-
-
MANAGEMENT_DB_WRITE_ACCESS_ACCOUNT_SID
-
Secure identifier (SID) of the account used for write (administrator) access to the Management database.
-
-
-
MANAGEMENT_REMOTE_SERVER_MACHINE_ACCOUNT
-
Management server remote computer account (domain\account).
-
-
-
MANAGEMENT_SERVER_INSTALL_ADMIN_ACCOUNT
-
Installation administrator login for the Management server (domain\account).
-
-
-
MANAGEMENT_SERVER_MACHINE_USE_LOCAL
-
Valid values are:
-
-
1 – the Management service is on the local computer, that is, MANAGEMENT_REMOTE_SERVER_MACHINE_ACCOUNT is blank.
-
0 - the Management service is on a different computer from the local computer.
-
-
-
-
-
-
-
-**ManagementService key**
-
-If you are installing the Management server, set these registry keys under `HKLM\Software\Microsoft\AppV\Server\ManagementService`.
-
-
-
-
-
-
-
-
-
Key name
-
Description
-
-
-
-
-
MANAGEMENT_ADMINACCOUNT
-
Active Directory Domain Services (AD DS) group or account that is authorized to manage App-V (domain\account).
-
-
-
MANAGEMENT_DB_SQL_INSTANCE
-
SQL server instance that contains the Management database.
-
If the value is blank, the default database instance is used.
-
-
-
MANAGEMENT_DB_SQL_SERVER_NAME
-
Name of the remote SQL server with the Management database.
-
If the value is blank, the local computer is used.
-
-
-
-
-
-
-**ReportingDatabase key**
-
-If you are installing the Reporting database, set these registry keys under `HKLM\Software\Microsoft\AppV\Server\ReportingDatabase`.
-
-
-
-
-
-
-
-
-
Key name
-
Description
-
-
-
-
-
IS_REPORTING_DB_PUBLIC_ACCESS_ACCOUNT_REQUIRED
-
Describes whether a public access account is required to access non-local reporting databases. Value is set to “1” if it is required.
-
-
-
REPORTING_DB_NAME
-
Name of the Reporting database.
-
-
-
REPORTING_DB_PUBLIC_ACCESS_ACCOUNT
-
Account used for read (public) access to the Reporting database.
-
Used when IS_REPORTING_DB_PUBLIC_ACCESS_ACCOUNT_REQUIRED is set to 1.
-
-
-
REPORTING_DB_PUBLIC_ACCESS_ACCOUNT_SID
-
Secure identifier (SID) of the account used for read (public) access to the Reporting database.
-
Used when IS_REPORTING_DB_PUBLIC_ACCESS_ACCOUNT_REQUIRED is set to 1.
-
-
-
REPORTING_DB_SQL_INSTANCE
-
SQL Server instance for the Reporting database.
-
If the value is blank, the default database instance is used.
-
-
-
REPORTING_DB_WRITE_ACCESS_ACCOUNT
-
-
-
-
REPORTING_DB_WRITE_ACCESS_ACCOUNT_SID
-
-
-
-
REPORTING_REMOTE_SERVER_MACHINE_ACCOUNT
-
Reporting server remote computer account (domain\account).
-
-
-
REPORTING_SERVER_INSTALL_ADMIN_ACCOUNT
-
Installation administrator login for the Reporting server (domain\account).
-
-
-
REPORTING_SERVER_MACHINE_USE_LOCAL
-
Valid values are:
-
-
1 – the Reporting service is on the local computer, that is, REPORTING_REMOTE_SERVER_MACHINE_ACCOUNT is blank.
-
0 - the Reporting service is on a different computer from the local computer.
-
-
-
-
-
-
-
-**ReportingService key**
-
-If you are installing the Reporting server, set these registry keys under `HKLM\Software\Microsoft\AppV\Server\ReportingService`.
-
-
-
-
-
-
-
-
-
Key name
-
Description
-
-
-
-
-
REPORTING_DB_SQL_INSTANCE
-
SQL Server instance for the Reporting database.
-
If the value is blank, the default database instance is used.
-
-
-
REPORTING_DB_SQL_SERVER_NAME
-
Name of the remote SQL server with the Reporting database.
-
If the value is blank, the local computer is used.
-
-
-
-
diff --git a/mdop/appv-v5/configure-applications-and-default-virtual-application-extensions-in-management-console.md b/mdop/appv-v5/configure-applications-and-default-virtual-application-extensions-in-management-console.md
deleted file mode 100644
index c96dff8cbe..0000000000
--- a/mdop/appv-v5/configure-applications-and-default-virtual-application-extensions-in-management-console.md
+++ /dev/null
@@ -1,52 +0,0 @@
----
-title: Configure Applications and Default Virtual Application Extensions in Management Console
-description: How to View and Configure Applications and Default Virtual Application Extensions by Using the Management Console
-author: dansimp
-ms.assetid: 1e1941d3-fb22-4077-8ec6-7a0cb80335d8
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 09/26/2019
----
-
-# Configure Applications and Default Virtual Application Extensions in Management Console
-
-Use the following procedure to *view* and *configure* default package extensions.
-
-**To view and configure default virtual application extensions**
-
-1. To view the package that you want to configure, open the App-V 5.1 Management Console. Select the package that you want to configure, right-click the package name and select **edit default configuration**.
-
-2. To view the applications contained in the specified package, in the **Default Configuration** pane, click **Applications**. To view the shortcuts for that package, click **Shortcuts**. To view the file type associations for that package, click **File Types**.
-
-3. To enable the application extensions, select **ENABLE**.
-
- To enable shortcuts, select **ENABLE SHORTCUTS**. To add a new shortcut for the selected application, right-click the application in the **SHORTCUTS** pane and select **Add new shortcut**. To remove a shortcut, right-click the application in the **SHORTCUTS** pane and select **Remove Shortcut**. To edit an existing shortcut, right-click the application and select **Edit Shortcut**.
-
-4. To view any other application extensions, click **Advanced** and click **Export Configuration**. Type in a filename and click **Save**. You can view all application extensions associated with the package using the configuration file.
-
-5. To edit other application extensions, modify the configuration file and click **Import and Overwrite this Configuration**. Select the modified file and click **Open**. In the dialog box, click **Overwrite** to complete the process.
-
->**Note** If the upload fails and the size of your configuration file is above 4MB, you will need to increase the maximum file size allowed by the server. This can be done by adding the maxRequestLength attribute with a value greater than the size of your configuration file (in KB) to the httpRuntime element on line 26 of `C:\Program Files\Microsoft Application Virtualization Server\ManagementService\Web.config`.
-For example, changing `` to `` will increase the maximum size to 8MB
-
-
-**Got a suggestion for App-V**? Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). **Got an App-V issue?** Use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/home?forum=mdopappv).
-
-## Related topics
-
-
-[Operations for App-V 5.1](operations-for-app-v-51.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v5/creating-and-managing-app-v-50-virtualized-applications.md b/mdop/appv-v5/creating-and-managing-app-v-50-virtualized-applications.md
deleted file mode 100644
index 56bd58a27e..0000000000
--- a/mdop/appv-v5/creating-and-managing-app-v-50-virtualized-applications.md
+++ /dev/null
@@ -1,344 +0,0 @@
----
-title: Creating and Managing App-V 5.0 Virtualized Applications
-description: Creating and Managing App-V 5.0 Virtualized Applications
-author: dansimp
-ms.assetid: 66bab403-d7e0-4e7b-bc8f-a29a98a7160a
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Creating and Managing App-V 5.0 Virtualized Applications
-
-
-After you have properly deployed the Microsoft Application Virtualization (App-V) 5.0 sequencer, you can use it to monitor and record the installation and setup process for an application to be run as a virtualized application.
-
-**Note**
-For more information about configuring the Microsoft Application Virtualization (App-V) 5.0 sequencer, sequencing best practices, and an example of creating and updating a virtual application, see the [Microsoft Application Virtualization 5.0 Sequencing Guide](https://download.microsoft.com/download/F/7/8/F784A197-73BE-48FF-83DA-4102C05A6D44/App-V 5.0 Sequencing Guide.docx) (https://download.microsoft.com/download/F/7/8/F784A197-73BE-48FF-83DA-4102C05A6D44/App-V 5.0 Sequencing Guide.docx).
-
-
-
-## Sequencing an application
-
-
-You can use the App-V 5.0 Sequencer to perform the following tasks:
-
-- Create virtual packages that can be deployed to computers running the App-V 5.0 client.
-
-- Upgrade existing packages. You can expand an existing package onto the computer running the sequencer and then upgrade the application to create a newer version.
-
-- Edit configuration information associated with an existing package. For example, you can add a shortcut or modify a file type association.
-
- **Note**
- You must create shortcuts and save them to an available network location to allow roaming. If a shortcut is created and saved in a private location, the package must be published locally to the computer running the App-V 5.0 client.
-
-
-
-- Convert existing virtual packages.
-
-The sequencer uses the **%TMP% \\ Scratch** or **%TEMP% \\ Scratch** directory and the **Temp** directory to store temporary files during sequencing. On the computer that runs the sequencer, you should configure these directories with free disk space equivalent to the estimated application installation requirements. Configuring the temp directories and the Temp directory on different hard drive partitions can help improve performance during sequencing.
-
-When you use the sequencer to create a new virtual application, the following listed files are created. These files comprise the App-V 5.0 package.
-
-- .msi file. This Windows Installer (.msi) file is created by the sequencer and is used to install the virtual package on target computers.
-
-- Report.xml file. In this file, the sequencer saves all issues, warnings, and errors that were discovered during sequencing. It displays the information after the package has been created. You can us this report for diagnosing and troubleshooting.
-
-- .appv file. This is the virtual application file.
-
-- Deployment configuration file. The deployment configuration file determines how the virtual application will be deployed to target computers.
-
-- User configuration file. The user configuration file determines how the virtual application will run on target computers.
-
-**Important**
-You must configure the %TMP% and %TEMP% folders that the package converter uses to be a secure location and directory. A secure location is only accessible by an administrator. Additionally, when you sequence the package you should save the package to a location that is secure, or make sure that no other user is allowed to be logged in during the conversion and monitoring process.
-
-
-
-The **Options** dialog box in the sequencer console contains the following tabs:
-
-- **General**. Use this tab to enable Microsoft Updates to run during sequencing. Select **Append Package Version to Filename** to configure the sequence to add a version number to the virtualized package that is being sequenced. Select **Always trust the source of Package Accelerators** to create virtualized packages using a package accelerator without being prompted for authorization.
-
- **Important**
- Package Accelerators created using App-V 4.6 are not supported by App-V 5.0.
-
-
-
-- **Parse Items**. This tab displays the associated file path locations that will be parsed or tokenized into in the virtual environment. Tokens are useful for adding files using the **Package Files** tab in **Advanced Editing**.
-
-- **Exclusion Items**. Use this tab to specify which folders and directories should not be monitored during sequencing. To add local application data that is saved in the Local App Data folder in the package, click **New** and specify the location and the associated **Mapping Type**. This option is required for some packages.
-
-App-V 5.0 supports applications that include Microsoft Windows Services. If an application includes a Windows service, the Service will be included in the sequenced virtual package as long as it is installed while being monitored by the sequencer. If a virtual application creates a Windows service when it initially runs, then later, after installation, the application must be run while the sequencer is monitoring so that the Windows Service will be added to the package. Only Services that run under the Local System account are supported. Services that are configured for AutoStart or Delayed AutoStart are started before the first virtual application in a package runs inside the package’s Virtual Environment. Windows Services that are configured to be started on demand by an application are started when the virtual application inside the package starts the Service via API call.
-
-[How to Sequence a New Application with App-V 5.0](how-to-sequence-a-new-application-with-app-v-50-beta-gb18030.md)
-
-## App-V 5.0 SP2 shell extension support
-
-
-App-V 5.0 SP2 supports shell extensions. Shell extensions will be detected and embedded in the package during sequencing.
-
-Shell extensions are embedded in the package automatically during the sequencing process. When the package is published, the shell extension gives users the same functionality as if the application were locally installed.
-
-**Requirements for using shell extensions:**
-
-- Packages that contain embedded shell extensions must be published globally. The application requires no additional setup or configuration on the client to enable the shell extension functionality.
-
-- The “bitness” of the application, Sequencer, and App-V client must match, or the shell extensions won’t work. For example:
-
- - The version of the application is 64-bit.
-
- - The Sequencer is running on a 64-bit computer.
-
- - The package is being delivered to a 64-bit App-V client computer.
-
-The following table lists the supported shell extensions:
-
-
-
-
-
-
-
-
-
Handler
-
Description
-
-
-
-
-
Context menu handler
-
Adds menu items to the context menu. It is called before the context menu is displayed.
-
-
-
Drag-and-drop handler
-
Controls the action where right-click, drag and drop and modifies the context menu that appears.
-
-
-
Drop target handler
-
Controls the action after a data object is dragged and dropped over a drop target such as a file.
-
-
-
Data object handler
-
Controls the action after a file is copied to the clipboard or dragged and dropped over a drop target. It can provide additional clipboard formats to the drop target.
-
-
-
Property sheet handler
-
Replaces or adds pages to the property sheet dialog box of an object.
-
-
-
Infotip handler
-
Allows retrieving flags and infotip information for an item and displaying it inside a pop-up tooltip upon mouse hover.
-
-
-
Column handler
-
Allows creating and displaying custom columns in Windows Explorer Details view. It can be used to extend sorting and grouping.
-
-
-
Preview handler
-
Enables a preview of a file to be displayed in the Windows Explorer Preview pane.
-
-
-
-
-
-
-## Copy on Write (CoW) file extension support
-
-
-Copy on write (CoW) file extensions allow App-V 5.0 to dynamically write to specific locations contained in the virtual package while it is being used.
-
-The following table displays the file types that can exist in a virtual package under the VFS directory, but cannot be updated on the computer running the App-V 5.0 client. All other files and directories can be modified.
-
-.acm
-
-.asa
-
-.asp
-
-.aspx
-
-.ax
-
-.bat
-
-.cer
-
-.chm
-
-.clb
-
-.cmd
-
-.cnt
-
-.cnv
-
-.com
-
-.cpl
-
-.cpx
-
-.crt
-
-.dll
-
-.drv
-
-.exe
-
-.fon
-
-.grp
-
-.hlp
-
-.hta
-
-.ime
-
-.inf
-
-.ins
-
-.isp
-
-.its
-
-.js
-
-.jse
-
-.lnk
-
-.msc
-
-.msi
-
-.msp
-
-.mst
-
-.mui
-
-.nls
-
-.ocx
-
-.pal
-
-.pcd
-
-.pif
-
-.reg
-
-.scf
-
-.scr
-
-.sct
-
-.shb
-
-.shs
-
-.sys
-
-.tlb
-
-.tsp
-
-.url
-
-.vb
-
-.vbe
-
-.vbs
-
-.vsmacros
-
-.ws
-
-.esc
-
-.wsf
-
-.wsh
-
-
-
-## Modifying an existing virtual application package
-
-
-You can use the sequencer to modify an existing package. The computer on which you do this should match the chip architecture of the computer you used to create the application. For example, if you initially sequenced a package using a computer running a 64-bit operating system, you should modify the package using a computer running a 64-bit operating system.
-
-[How to Modify an Existing Virtual Application Package](how-to-modify-an-existing-virtual-application-package-beta.md)
-
-## Creating a project template
-
-
-A .appvt file is a project template that can be used to save commonly applied, customized settings. You can then more easily use these settings for future sequencings.
-
-App-V 5.0 project templates differ from App-V 5.0 Application Accelerators because App-V 5.0 Application Accelerators are application-specific, and App-V 5.0 project templates can be applied to multiple applications. Additionally, you cannot use a project template when you use a Package Accelerator to create a virtual application package. The following general settings are saved with an App-V 5.0 project template:
-
-A template can specify and store multiple settings as follows:
-
-- **Advanced Monitoring Options**. Enables Microsoft Update to run during monitoring. Saves allow local interaction option settings
-
-- **General Options**. Enables the use of **Windows Installer**, **Append Package Version to Filename**.
-
-- **Exclusion Items.** Contains the Exclusion pattern list.
-
-[How to Create and Use a Project Template](how-to-create-and-use-a-project-template.md)
-
-## Creating a package accelerator
-
-
-**Note**
-Package accelerators created using a previous version of App-V must be recreated using App-V 5.0.
-
-
-
-You can use App-V 5.0 package accelerators to automatically generate a new virtual application packages. After you have successfully created a package accelerator, you can reuse and share the package accelerator.
-
-In some situations, to create the package accelerator, you might have to install the application locally on the computer that runs the sequencer. In such cases, you should first try to create the package accelerator with the installation media. If multiple missing files are required, you should install the application locally to the computer that runs the sequencer, and then create the package accelerator.
-
-After you have successfully created a Package Accelerator, you can reuse and share the Package Accelerator. Creating App-V 5.0 Package Accelerators is an advanced task. Package Accelerators can contain password and user-specific information. Therefore you must save Package Accelerators and the associated installation media in a secure location, and you should digitally sign the Package Accelerator after you create it so that the publisher can be verified when the App-V 5.0 Package Accelerator is applied.
-
-[How to Create a Package Accelerator](how-to-create-a-package-accelerator.md)
-
-[How to Create a Virtual Application Package Using an App-V Package Accelerator](how-to-create-a-virtual-application-package-using-an-app-v-package-accelerator.md)
-
-## Sequencer error reporting
-
-
-The App-V 5.0 Sequencer can detect common sequencing issues during sequencing. The **Installation Report** page at the end of the sequencing wizard displays diagnostic messages categorized into **Errors**, **Warnings**, and **Info** depending on the severity of the issue.
-
-You can also find additional information about sequencing errors using the Windows Event Viewer.
-
-
-
-
-
-
-## Other resources for the App-V 5.0 sequencer
-
-
-- [Operations for App-V 5.0](operations-for-app-v-50.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v5/creating-and-managing-app-v-51-virtualized-applications.md b/mdop/appv-v5/creating-and-managing-app-v-51-virtualized-applications.md
deleted file mode 100644
index c781eb4fea..0000000000
--- a/mdop/appv-v5/creating-and-managing-app-v-51-virtualized-applications.md
+++ /dev/null
@@ -1,216 +0,0 @@
----
-title: Creating and Managing App-V 5.1 Virtualized Applications
-description: Creating and Managing App-V 5.1 Virtualized Applications
-author: dansimp
-ms.assetid: 26be4331-88eb-4cfb-9d82-e63d7ee54576
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Creating and Managing App-V 5.1 Virtualized Applications
-
-
-After you have properly deployed the Microsoft Application Virtualization (App-V) 5.1 sequencer, you can use it to monitor and record the installation and setup process for an application to be run as a virtualized application.
-
-**Note**
-For more information about configuring the App-V 5.1 sequencer, sequencing best practices, and an example of creating and updating a virtual application, see the [Microsoft Application Virtualization 5.0 Sequencing Guide](https://download.microsoft.com/download/F/7/8/F784A197-73BE-48FF-83DA-4102C05A6D44/App-V 5.0 Sequencing Guide.docx).
-
-**Note**
-The App-V 5.x Sequencer cannot sequence applications with filenames matching "CO_<x>" where x is any numeral. Error 0x8007139F will be generated.
-
-## Sequencing an application
-
-
-You can use the App-V 5.1 Sequencer to perform the following tasks:
-
-- Create virtual packages that can be deployed to computers running the App-V 5.1 client.
-
-- Upgrade existing packages. You can expand an existing package onto the computer running the sequencer and then upgrade the application to create a newer version.
-
-- Edit configuration information associated with an existing package. For example, you can add a shortcut or modify a file type association.
-
- **Note**
- You must create shortcuts and save them to an available network location to allow roaming. If a shortcut is created and saved in a private location, the package must be published locally to the computer running the App-V 5.1 client.
-
-- Convert existing virtual packages.
-
-The sequencer uses the **%TMP% \\ Scratch** or **%TEMP% \\ Scratch** directory and the **Temp** directory to store temporary files during sequencing. On the computer that runs the sequencer, you should configure these directories with free disk space equivalent to the estimated application installation requirements. Configuring the temp directories and the Temp directory on different hard drive partitions can help improve performance during sequencing.
-
-When you use the sequencer to create a new virtual application, the following listed files are created. These files comprise the App-V 5.1 package.
-
-- .msi file. This Windows Installer (.msi) file is created by the sequencer and is used to install the virtual package on target computers.
-
-- Report.xml file. In this file, the sequencer saves all issues, warnings, and errors that were discovered during sequencing. It displays the information after the package has been created. You can us this report for diagnosing and troubleshooting.
-
-- .appv file. This is the virtual application file.
-
-- Deployment configuration file. The deployment configuration file determines how the virtual application will be deployed to target computers.
-
-- User configuration file. The user configuration file determines how the virtual application will run on target computers.
-
-**Important**
-You must configure the %TMP% and %TEMP% folders that the package converter uses to be a secure location and directory. A secure location is only accessible by an administrator. Additionally, when you sequence the package you should save the package to a location that is secure, or make sure that no other user is allowed to be logged in during the conversion and monitoring process.
-
-The **Options** dialog box in the sequencer console contains the following tabs:
-
-- **General**. Use this tab to enable Microsoft Updates to run during sequencing. Select **Append Package Version to Filename** to configure the sequence to add a version number to the virtualized package that is being sequenced. Select **Always trust the source of Package Accelerators** to create virtualized packages using a package accelerator without being prompted for authorization.
-
- **Important**
- Package Accelerators created using App-V 4.6 are not supported by App-V 5.1.
-
-- **Parse Items**. This tab displays the associated file path locations that will be parsed or tokenized into in the virtual environment. Tokens are useful for adding files using the **Package Files** tab in **Advanced Editing**.
-
-- **Exclusion Items**. Use this tab to specify which folders and directories should not be monitored during sequencing. To add local application data that is saved in the Local App Data folder in the package, click **New** and specify the location and the associated **Mapping Type**. This option is required for some packages.
-
-App-V 5.1 supports applications that include Microsoft Windows Services. If an application includes a Windows service, the Service will be included in the sequenced virtual package as long as it is installed while being monitored by the sequencer. If a virtual application creates a Windows service when it initially runs, then later, after installation, the application must be run while the sequencer is monitoring so that the Windows Service will be added to the package. Only Services that run under the Local System account are supported. Services that are configured for AutoStart or Delayed AutoStart are started before the first virtual application in a package runs inside the package’s Virtual Environment. Windows Services that are configured to be started on demand by an application are started when the virtual application inside the package starts the Service via API call.
-
-[How to Sequence a New Application with App-V 5.1](how-to-sequence-a-new-application-with-app-v-51-beta-gb18030.md)
-
-## App-V 5.1 shell extension support
-
-
-App-V 5.1 supports shell extensions. Shell extensions will be detected and embedded in the package during sequencing.
-
-Shell extensions are embedded in the package automatically during the sequencing process. When the package is published, the shell extension gives users the same functionality as if the application were locally installed.
-
-**Requirements for using shell extensions:**
-
-- Packages that contain embedded shell extensions must be published globally. The application requires no additional setup or configuration on the client to enable the shell extension functionality.
-
-- The “bitness” of the application, Sequencer, and App-V client must match, or the shell extensions won’t work. For example:
-
- - The version of the application is 64-bit.
-
- - The Sequencer is running on a 64-bit computer.
-
- - The package is being delivered to a 64-bit App-V client computer.
-
-The following table lists the supported shell extensions:
-
-
-
-
-
-
-
-
-
Handler
-
Description
-
-
-
-
-
Context menu handler
-
Adds menu items to the context menu. It is called before the context menu is displayed.
-
-
-
Drag-and-drop handler
-
Controls the action where right-click, drag and drop and modifies the context menu that appears.
-
-
-
Drop target handler
-
Controls the action after a data object is dragged and dropped over a drop target such as a file.
-
-
-
Data object handler
-
Controls the action after a file is copied to the clipboard or dragged and dropped over a drop target. It can provide additional clipboard formats to the drop target.
-
-
-
Property sheet handler
-
Replaces or adds pages to the property sheet dialog box of an object.
-
-
-
Infotip handler
-
Allows retrieving flags and infotip information for an item and displaying it inside a pop-up tooltip upon mouse hover.
-
-
-
Column handler
-
Allows creating and displaying custom columns in Windows Explorer Details view. It can be used to extend sorting and grouping.
-
-
-
Preview handler
-
Enables a preview of a file to be displayed in the Windows Explorer Preview pane.
-
-
-
-
-## Copy on Write (CoW) file extension support
-
-Copy on write (CoW) file extensions allow App-V 5.1 to dynamically write to specific locations contained in the virtual package while it is being used.
-
-The following table displays the file types that can exist in a virtual package under the VFS directory, but cannot be updated on the computer running the App-V 5.1 client. All other files and directories can be modified.
-
-| File Type | | | | | |
-|------------ |------------- |------------- |------------ |------------ |------------ |
-| .acm | .asa | .asp | .aspx | .ax | .bat |
-| .cer | .chm | .clb | .cmd | .cnt | .cnv |
-| .com | .cpl | .cpx | .crt | .dll | .drv |
-| .esc | .exe | .fon | .grp | .hlp | .hta |
-| .ime | .inf | .ins | .isp | .its | .js |
-| .jse | .lnk | .msc | .msi | .msp | .mst |
-| .mui | .nls | .ocx | .pal | .pcd | .pif |
-| .reg | .scf | .scr | .sct | .shb | .shs |
-| .sys | .tlb | .tsp | .url | .vb | .vbe |
-| .vbs | .vsmacros | .ws | .wsf | .wsh | |
-
-
-## Modifying an existing virtual application package
-
-
-You can use the sequencer to modify an existing package. The computer on which you do this should match the chip architecture of the computer you used to create the application. For example, if you initially sequenced a package using a computer running a 64-bit operating system, you should modify the package using a computer running a 64-bit operating system.
-
-[How to Modify an Existing Virtual Application Package](how-to-modify-an-existing-virtual-application-package-51.md)
-
-## Creating a project template
-
-
-A .appvt file is a project template that can be used to save commonly applied, customized settings. You can then more easily use these settings for future sequencings.
-
-App-V 5.1 project templates differ from App-V 5.1 Application Accelerators because App-V 5.1 Application Accelerators are application-specific, and App-V 5.1 project templates can be applied to multiple applications. Additionally, you cannot use a project template when you use a Package Accelerator to create a virtual application package. The following general settings are saved with an App-V 5.1 project template:
-
-A template can specify and store multiple settings as follows:
-
-- **Advanced Monitoring Options**. Enables Microsoft Update to run during monitoring. Saves allow local interaction option settings
-
-- **General Options**. Enables the use of **Windows Installer**, **Append Package Version to Filename**.
-
-- **Exclusion Items.** Contains the Exclusion pattern list.
-
-[How to Create and Use a Project Template](how-to-create-and-use-a-project-template51.md)
-
-## Creating a package accelerator
-
-
-**Note**
-Package accelerators created using a previous version of App-V must be recreated using App-V 5.1.
-
-You can use App-V 5.1 package accelerators to automatically generate a new virtual application packages. After you have successfully created a package accelerator, you can reuse and share the package accelerator.
-
-In some situations, to create the package accelerator, you might have to install the application locally on the computer that runs the sequencer. In such cases, you should first try to create the package accelerator with the installation media. If multiple missing files are required, you should install the application locally to the computer that runs the sequencer, and then create the package accelerator.
-
-After you have successfully created a Package Accelerator, you can reuse and share the Package Accelerator. Creating App-V 5.1 Package Accelerators is an advanced task. Package Accelerators can contain password and user-specific information. Therefore you must save Package Accelerators and the associated installation media in a secure location, and you should digitally sign the Package Accelerator after you create it so that the publisher can be verified when the App-V 5.1 Package Accelerator is applied.
-
-[How to Create a Package Accelerator](how-to-create-a-package-accelerator51.md)
-
-[How to Create a Virtual Application Package Using an App-V Package Accelerator](how-to-create-a-virtual-application-package-using-an-app-v-package-accelerator51.md)
-
-## Sequencer error reporting
-
-
-The App-V 5.1 Sequencer can detect common sequencing issues during sequencing. The **Installation Report** page at the end of the sequencing wizard displays diagnostic messages categorized into **Errors**, **Warnings**, and **Info** depending on the severity of the issue.
-
-You can also find additional information about sequencing errors using the Windows Event Viewer.
-
-
-## Other resources for the App-V 5.1 sequencer
-
-
-- [Operations for App-V 5.1](operations-for-app-v-51.md)
-
diff --git a/mdop/appv-v5/deploying-app-v-50-packages-by-using-electronic-software-distribution--esd-.md b/mdop/appv-v5/deploying-app-v-50-packages-by-using-electronic-software-distribution--esd-.md
deleted file mode 100644
index 4490ab666a..0000000000
--- a/mdop/appv-v5/deploying-app-v-50-packages-by-using-electronic-software-distribution--esd-.md
+++ /dev/null
@@ -1,57 +0,0 @@
----
-title: Deploying App-V 5.0 Packages by Using Electronic Software Distribution (ESD)
-description: Deploying App-V 5.0 Packages by Using Electronic Software Distribution (ESD)
-author: dansimp
-ms.assetid: d1d74af4-229f-4578-8c95-554a3d7cd2f3
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 08/30/2016
----
-
-
-# Deploying App-V 5.0 Packages by Using Electronic Software Distribution (ESD)
-
-
-You can deploy App-V 5.0 packages using an Electronic Software Distribution (ESD) solution. For information about planning to deploy App-V packages with an ESD, see [Planning to Deploy App-V 5.0 with an Electronic Software Distribution System](planning-to-deploy-app-v-50-with-an-electronic-software-distribution-system.md).
-
-To deploy App-V packages with Microsoft System Center 2012 Configuration Manager, see [Introduction to Application Management in Configuration Manager](https://go.microsoft.com/fwlink/?LinkId=281816)
-
-## How to deploy virtualized packages using an ESD
-
-
-Describes the methods you can use to deploy App-V packages by using an ESD
-
-[How to deploy App-V 5.0 Packages Using Electronic Software Distribution](how-to-deploy-app-v-50-packages-using-electronic-software-distribution.md)
-
-## How to Enable Only Administrators to Publish Packages by Using an ESD
-
-
-Explains how to configure the App-V client to enable only administrators to publish and unpublish packages when you’re using an ESD.
-
-[How to Enable Only Administrators to Publish Packages by Using an ESD](how-to-enable-only-administrators-to-publish-packages-by-using-an-esd.md)
-
-
-
-
-
-
-## Other resources for using an ESD and App-V 5.0
-
-
-Use the following link for more information about [App-V and Citrix Integration](https://go.microsoft.com/fwlink/?LinkId=330294 ) (https://go.microsoft.com/fwlink/?LinkId=330294).
-
-[Operations for App-V 5.0](operations-for-app-v-50.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v5/deploying-app-v-50.md b/mdop/appv-v5/deploying-app-v-50.md
deleted file mode 100644
index 5f13c3d291..0000000000
--- a/mdop/appv-v5/deploying-app-v-50.md
+++ /dev/null
@@ -1,62 +0,0 @@
----
-title: Deploying App-V 5.0
-description: Deploying App-V 5.0
-author: dansimp
-ms.assetid: 77cb19d7-00e6-4b39-b35a-e8a8ca0b807b
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Deploying App-V 5.0
-
-
-Microsoft Application Virtualization (App-V) 5.0 (App-V 5.0) supports a number of different deployment options. This section of the App-V 5.0 Administrator’s Guide includes information you should consider about the deployment of App-V 5.0 and step-by-step procedures to help you successfully perform the tasks that you must complete at different stages of your deployment.
-
-## App-V 5.0 Deployment Information
-
-
-- [Deploying the App-V 5.0 Sequencer and Client](deploying-the-app-v-50-sequencer-and-client.md)
-
- This section describes how to install the App-V 5.0 sequencer which is used to virtualize applications, and the App-V 5.0 client which runs on target computers to facilitate virtualized packages.
-
-- [Deploying the App-V 5.0 Server](deploying-the-app-v-50-server.md)
-
- This section provides information about installing the App-V 5.0 management, publishing, database and reporting severs.
-
-- [App-V 5.0 Deployment Checklist](app-v-50-deployment-checklist.md)
-
- This section provides a deployment checklist that can be used to assist with installing App-V 5.0.
-
-## Other Resources for Deploying App-V 5.0
-
-
-- [Microsoft Application Virtualization 5.0 Administrator's Guide](microsoft-application-virtualization-50-administrators-guide.md)
-
-- [Getting Started with App-V 5.0](getting-started-with-app-v-50--rtm.md)
-
-- [Planning for App-V 5.0](planning-for-app-v-50-rc.md)
-
-- [Operations for App-V 5.0](operations-for-app-v-50.md)
-
-- [Troubleshooting App-V 5.0](troubleshooting-app-v-50.md)
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v5/deploying-app-v-51-packages-by-using-electronic-software-distribution--esd-.md b/mdop/appv-v5/deploying-app-v-51-packages-by-using-electronic-software-distribution--esd-.md
deleted file mode 100644
index de4772c416..0000000000
--- a/mdop/appv-v5/deploying-app-v-51-packages-by-using-electronic-software-distribution--esd-.md
+++ /dev/null
@@ -1,57 +0,0 @@
----
-title: Deploying App-V 5.1 Packages by Using Electronic Software Distribution (ESD)
-description: Deploying App-V 5.1 Packages by Using Electronic Software Distribution (ESD)
-author: dansimp
-ms.assetid: c2e4d176-460d-44ca-9a1d-69d2a733aa42
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 08/30/2016
----
-
-
-# Deploying App-V 5.1 Packages by Using Electronic Software Distribution (ESD)
-
-
-You can deploy App-V 5.1 packages using an Electronic Software Distribution (ESD) solution. For information about planning to deploy App-V packages with an ESD, see [Planning to Deploy App-V 5.1 with an Electronic Software Distribution System](planning-to-deploy-app-v-51-with-an-electronic-software-distribution-system.md).
-
-To deploy App-V packages with Microsoft System Center 2012 Configuration Manager, see [Introduction to Application Management in Configuration Manager](https://go.microsoft.com/fwlink/?LinkId=281816)
-
-## How to deploy virtualized packages using an ESD
-
-
-Describes the methods you can use to deploy App-V packages by using an ESD
-
-[How to deploy App-V 5.1 Packages Using Electronic Software Distribution](how-to-deploy-app-v-51-packages-using-electronic-software-distribution.md)
-
-## How to Enable Only Administrators to Publish Packages by Using an ESD
-
-
-Explains how to configure the App-V client to enable only administrators to publish and unpublish packages when you’re using an ESD.
-
-[How to Enable Only Administrators to Publish Packages by Using an ESD](how-to-enable-only-administrators-to-publish-packages-by-using-an-esd51.md)
-
-
-
-
-
-
-## Other resources for using an ESD and App-V 5.1
-
-
-Use the following link for more information about [App-V and Citrix Integration](https://go.microsoft.com/fwlink/?LinkId=330294 ) (https://go.microsoft.com/fwlink/?LinkId=330294).
-
-[Operations for App-V 5.1](operations-for-app-v-51.md)
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v5/deploying-app-v-51.md b/mdop/appv-v5/deploying-app-v-51.md
deleted file mode 100644
index 719dc32571..0000000000
--- a/mdop/appv-v5/deploying-app-v-51.md
+++ /dev/null
@@ -1,64 +0,0 @@
----
-title: Deploying App-V 5.1
-description: Deploying App-V 5.1
-author: dansimp
-ms.assetid: af8742bf-e24b-402a-bcf4-0f2297f26bc4
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 06/16/2016
----
-
-
-# Deploying App-V 5.1
-
-
-Microsoft Application Virtualization (App-V) 5.1 supports a number of different deployment options. This section of the App-V 5.1 Administrator’s Guide includes information you should consider about the deployment of App-V 5.1 and step-by-step procedures to help you successfully perform the tasks that you must complete at different stages of your deployment.
-
-## App-V 5.1 Deployment Information
-
-
-- [Deploying the App-V 5.1 Sequencer and Client](deploying-the-app-v-51-sequencer-and-client.md)
-
- This section describes how to install the App-V 5.1 sequencer which is used to virtualize applications, and the App-V 5.1 client which runs on target computers to facilitate virtualized packages.
-
-- [Deploying the App-V 5.1 Server](deploying-the-app-v-51-server.md)
-
- This section provides information about installing the App-V 5.1 management, publishing, database and reporting severs.
-
-- [App-V 5.1 Deployment Checklist](app-v-51-deployment-checklist.md)
-
- This section provides a deployment checklist that can be used to assist with installing App-V 5.1.
-
-## Other Resources for Deploying App-V 5.1
-
-
-- [Microsoft Application Virtualization 5.1 Administrator's Guide](microsoft-application-virtualization-51-administrators-guide.md)
-
-- [Getting Started with App-V 5.1](getting-started-with-app-v-51.md)
-
-- [Planning for App-V 5.1](planning-for-app-v-51.md)
-
-- [Operations for App-V 5.1](operations-for-app-v-51.md)
-
-- [Troubleshooting App-V 5.1](troubleshooting-app-v-51.md)
-
-- [Technical Reference for App-V 5.1](technical-reference-for-app-v-51.md)
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v5/deploying-microsoft-office-2010-by-using-app-v.md b/mdop/appv-v5/deploying-microsoft-office-2010-by-using-app-v.md
deleted file mode 100644
index 88c3436957..0000000000
--- a/mdop/appv-v5/deploying-microsoft-office-2010-by-using-app-v.md
+++ /dev/null
@@ -1,315 +0,0 @@
----
-title: Deploying Microsoft Office 2010 by Using App-V
-description: Deploying Microsoft Office 2010 by Using App-V
-author: dansimp
-ms.assetid: 0a9e496e-82a1-4dc0-a496-7b21eaa00f53
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 08/30/2016
----
-
-
-# Deploying Microsoft Office 2010 by Using App-V
-
-
-You can create Office 2010 packages for Application Virtualization 5.0 using one of the following methods:
-
-- Application Virtualization (App-V) Sequencer
-
-- Application Virtualization (App-V) Package Accelerator
-
-## App-V support for Office 2010
-
-
-The following table shows the App-V versions, methods of Office package creation, supported licensing, and supported deployments for Office 2010.
-
-
-
-
-
-
-
-
-
Supported item
-
Level of support
-
-
-
-
-
Supported App-V versions
-
-
4.6
-
5.0
-
-
-
-
Package creation
-
-
Sequencing
-
Package Accelerator
-
Office Deployment Kit
-
-
-
-
Supported licensing
-
Volume Licensing
-
-
-
Supported deployments
-
-
Desktop
-
Personal VDI
-
RDS
-
-
-
-
-
-
-
-## Creating Office 2010 App-V 5.0 using the sequencer
-
-
-Sequencing Office 2010 is one of the main methods for creating an Office 2010 package on App-V 5.0. Microsoft has provided a detailed recipe through a Knowledge Base article. To create an Office 2010 package on App-V 5.0, refer to the following link for detailed instructions:
-
-[How To Sequence Microsoft Office 2010 in Microsoft Application Virtualization 5.0](https://go.microsoft.com/fwlink/p/?LinkId=330676)
-
-## Creating Office 2010 App-V 5.0 packages using package accelerators
-
-
-Office 2010 App-V 5.0 packages can be created through package accelerators. Microsoft has provided package accelerators for creating Office 2010 on Windows 8 and Windows 7. To create Office 2010 packages on App-V using Package accelerators, refer to the following pages to access the appropriate package accelerator:
-
-- [App-V 5.0 Package Accelerator for Office Professional Plus 2010 – Windows 8](https://go.microsoft.com/fwlink/p/?LinkId=330677)
-
-- [App-V 5.0 Package Accelerator for Office Professional Plus 2010 – Windows 7](https://go.microsoft.com/fwlink/p/?LinkId=330678)
-
-For detailed instructions on how to create virtual application packages using App-V package accelerators, see [How to Create a Virtual Application Package Using an App-V Package Accelerator](how-to-create-a-virtual-application-package-using-an-app-v-package-accelerator.md).
-
-## Deploying the Microsoft Office package for App-V 5.0
-
-
-You can deploy Office 2010 packages by using any of the following App-V deployment methods:
-
-- System Center Configuration Manager
-
-- App-V server
-
-- Stand-alone through PowerShell commands
-
-## Office App-V package management and customization
-
-
-Office 2010 packages can be managed like any other App-V 5.0 packages through known package management mechanisms. No special instructions are needed, for example, to add, publish, unpublish, or remove Office packages.
-
-## Microsoft Office integration with Windows
-
-
-The following table provides a full list of supported integration points for Office 2010.
-
-
-
-
-
-
-
-
-
-
Extension Point
-
Description
-
Office 2010
-
-
-
-
-
Lync meeting Join Plug-in for Firefox and Chrome
-
User can join Lync meetings from Firefox and Chrome
-
-
-
-
Sent to OneNote Print Driver
-
User can print to OneNote
-
Yes
-
-
-
OneNote Linked Notes
-
OneNote Linked Notes
-
-
-
-
Send to OneNote Internet Explorer Add-In
-
User can send to OneNote from IE
-
-
-
-
Firewall Exception for Lync and Outlook
-
Firewall Exception for Lync and Outlook
-
-
-
-
MAPI Client
-
Native apps and add-ins can interact with virtual Outlook through MAPI
-
-
-
-
SharePoint Plugin for Firefox
-
User can use SharePoint features in Firefox
-
-
-
-
Mail Control Panel Applet
-
User gets the mail control panel applet in Outlook
Windows explorer shell icon overlays when users look at folders OneDrive Pro folders
-
-
-
-
-
-
-
-## Additional resources
-
-
-**Office 2013 App-V 5.0 Packages 5.0 Additional Resources**
-
-[Supported scenarios for deploying Microsoft Office as a sequenced App-V Package](https://go.microsoft.com/fwlink/p/?LinkId=330680)
-
-**Office 2010 App-V 5.0 Packages**
-
-[Microsoft Office 2010 Sequencing Kit for Microsoft Application Virtualization 5.0](https://go.microsoft.com/fwlink/p/?LinkId=330681)
-
-[Known issues when you create or use an App-V 5.0 Office 2010 package](https://go.microsoft.com/fwlink/p/?LinkId=330682)
-
-[How to sequence Microsoft Office 2010 in Microsoft Application Virtualization 5.0](https://go.microsoft.com/fwlink/p/?LinkId=330676)
-
-**Connection Groups**
-
-[Deploying Connection Groups in Microsoft App-V v5](https://go.microsoft.com/fwlink/p/?LinkId=330683)
-
-[Managing Connection Groups](managing-connection-groups.md)
-
-**Dynamic Configuration**
-
-[About App-V 5.0 Dynamic Configuration](about-app-v-50-dynamic-configuration.md)
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v5/deploying-microsoft-office-2010-by-using-app-v51.md b/mdop/appv-v5/deploying-microsoft-office-2010-by-using-app-v51.md
deleted file mode 100644
index 8e68496eec..0000000000
--- a/mdop/appv-v5/deploying-microsoft-office-2010-by-using-app-v51.md
+++ /dev/null
@@ -1,316 +0,0 @@
----
-title: Deploying Microsoft Office 2010 by Using App-V
-description: Deploying Microsoft Office 2010 by Using App-V
-author: dansimp
-ms.assetid: ae0b0459-c0d6-4946-b62d-ff153f52d1fb
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 08/30/2016
----
-
-
-# Deploying Microsoft Office 2010 by Using App-V
-
-
-You can create Office 2010 packages for Microsoft Application Virtualization (App-V) 5.1 using one of the following methods:
-
-- Application Virtualization (App-V) Sequencer
-
-- Application Virtualization (App-V) Package Accelerator
-
-## App-V support for Office 2010
-
-
-The following table shows the App-V versions, methods of Office package creation, supported licensing, and supported deployments for Office 2010.
-
-
-
-
-
-
-
-
-
Supported item
-
Level of support
-
-
-
-
-
Supported App-V versions
-
-
4.6
-
5.0
-
5.1
-
-
-
-
Package creation
-
-
Sequencing
-
Package Accelerator
-
Office Deployment Kit
-
-
-
-
Supported licensing
-
Volume Licensing
-
-
-
Supported deployments
-
-
Desktop
-
Personal VDI
-
RDS
-
-
-
-
-
-
-
-## Creating Office 2010 App-V 5.1 using the sequencer
-
-
-Sequencing Office 2010 is one of the main methods for creating an Office 2010 package on App-V 5.1. Microsoft has provided a detailed recipe through a Knowledge Base article. To create an Office 2010 package on App-V 5.1, refer to the following link for detailed instructions:
-
-[How To Sequence Microsoft Office 2010 in Microsoft Application Virtualization 5.0](https://go.microsoft.com/fwlink/p/?LinkId=330676)
-
-## Creating Office 2010 App-V 5.1 packages using package accelerators
-
-
-Office 2010 App-V 5.1 packages can be created through package accelerators. Microsoft has provided package accelerators for creating Office 2010 on Windows 10, Windows 8 and Windows 7. To create Office 2010 packages on App-V using Package accelerators, refer to the following pages to access the appropriate package accelerator:
-
-- [App-V 5.0 Package Accelerator for Office Professional Plus 2010 – Windows 8](https://go.microsoft.com/fwlink/p/?LinkId=330677)
-
-- [App-V 5.0 Package Accelerator for Office Professional Plus 2010 – Windows 7](https://go.microsoft.com/fwlink/p/?LinkId=330678)
-
-For detailed instructions on how to create virtual application packages using App-V package accelerators, see [How to Create a Virtual Application Package Using an App-V Package Accelerator](how-to-create-a-virtual-application-package-using-an-app-v-package-accelerator51.md).
-
-## Deploying the Microsoft Office package for App-V 5.1
-
-
-You can deploy Office 2010 packages by using any of the following App-V deployment methods:
-
-- System Center Configuration Manager
-
-- App-V server
-
-- Stand-alone through PowerShell commands
-
-## Office App-V package management and customization
-
-
-Office 2010 packages can be managed like any other App-V 5.1 packages through known package management mechanisms. No special instructions are needed, for example, to add, publish, unpublish, or remove Office packages.
-
-## Microsoft Office integration with Windows
-
-
-The following table provides a full list of supported integration points for Office 2010.
-
-
-
-
-
-
-
-
-
-
Extension Point
-
Description
-
Office 2010
-
-
-
-
-
Lync meeting Join Plug-in for Firefox and Chrome
-
User can join Lync meetings from Firefox and Chrome
-
-
-
-
Sent to OneNote Print Driver
-
User can print to OneNote
-
Yes
-
-
-
OneNote Linked Notes
-
OneNote Linked Notes
-
-
-
-
Send to OneNote Internet Explorer Add-In
-
User can send to OneNote from IE
-
-
-
-
Firewall Exception for Lync and Outlook
-
Firewall Exception for Lync and Outlook
-
-
-
-
MAPI Client
-
Native apps and add-ins can interact with virtual Outlook through MAPI
-
-
-
-
SharePoint Plugin for Firefox
-
User can use SharePoint features in Firefox
-
-
-
-
Mail Control Panel Applet
-
User gets the mail control panel applet in Outlook
Windows explorer shell icon overlays when users look at folders OneDrive Pro folders
-
-
-
-
-
-
-
-## Additional resources
-
-
-**Office 2013 App-V Packages Additional Resources**
-
-[Supported scenarios for deploying Microsoft Office as a sequenced App-V Package](https://go.microsoft.com/fwlink/p/?LinkId=330680)
-
-**Office 2010 App-V Packages**
-
-[Microsoft Office 2010 Sequencing Kit for Microsoft Application Virtualization 5.0](https://go.microsoft.com/fwlink/p/?LinkId=330681)
-
-[Known issues when you create or use an App-V 5.0 Office 2010 package](https://go.microsoft.com/fwlink/p/?LinkId=330682)
-
-[How to sequence Microsoft Office 2010 in Microsoft Application Virtualization 5.0](https://go.microsoft.com/fwlink/p/?LinkId=330676)
-
-**Connection Groups**
-
-[Deploying Connection Groups in Microsoft App-V v5](https://go.microsoft.com/fwlink/p/?LinkId=330683)
-
-[Managing Connection Groups](managing-connection-groups51.md)
-
-**Dynamic Configuration**
-
-[About App-V 5.1 Dynamic Configuration](about-app-v-51-dynamic-configuration.md)
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v5/deploying-microsoft-office-2013-by-using-app-v.md b/mdop/appv-v5/deploying-microsoft-office-2013-by-using-app-v.md
deleted file mode 100644
index ec3642bc65..0000000000
--- a/mdop/appv-v5/deploying-microsoft-office-2013-by-using-app-v.md
+++ /dev/null
@@ -1,894 +0,0 @@
----
-title: Deploying Microsoft Office 2013 by Using App-V
-description: Deploying Microsoft Office 2013 by Using App-V
-author: dansimp
-ms.assetid: 02df5dc8-79e2-4c5c-8398-dbfb23344ab3
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 11/02/2016
----
-
-
-# Deploying Microsoft Office 2013 by Using App-V
-
-
-Use the information in this article to use Microsoft Application Virtualization 5.0, or later versions, to deliver Microsoft Office 2013 as a virtualized application to computers in your organization. For information about using App-V to deliver Office 2010, see [Deploying Microsoft Office 2010 by Using App-V](deploying-microsoft-office-2010-by-using-app-v.md). To successfully deploy Office 2013 with App-V, you need to be familiar with Office 2013 and pp-V.
-
-This topic contains the following sections:
-
-- [What to know before you start](#bkmk-before-you-start)
-
-- [Creating an Office 2013 package for App-V with the Office Deployment Tool](#bkmk-create-office-pkg)
-
-- [Publishing the Office package for App-V 5.0](#bkmk-pub-pkg-office)
-
-- [Customizing and managing Office App-V packages](#bkmk-custmz-manage-office-pkgs)
-
-## What to know before you start
-
-
-Before you deploy Office 2013 by using App-V, review the following planning information.
-
-### Supported Office versions and Office coexistence
-
-Use the following table to get information about supported versions of Office and about running coexisting versions of Office.
-
-
Considerations for installing different versions of Office on the same computer
-
-
-
-
-
-
-### Packaging, publishing, and deployment requirements
-
-Before you deploy Office by using App-V, review the following requirements.
-
-
-
-
-
-
-
-
-
Task
-
Requirement
-
-
-
-
-
Packaging
-
-
All of the Office applications that you want to deploy to users must be in a single package.
-
In App-V 5.0 and later, you must use the Office Deployment Tool to create packages. You cannot use the Sequencer.
-
If you are deploying Microsoft Visio 2013 and Microsoft Project 2013 along with Office, you must include them in the same package with Office. For more information, see Deploying Visio 2013 and Project 2013 with Office.
-
-
-
-
Publishing
-
-
You can publish only one Office package to each client computer.
-
You must publish the Office package globally. You cannot publish to the user.
-
-
-
-
Deploying any of the following products to a shared computer, for example, by using Remote Desktop Services:
You don’t use shared computer activation if you’re deploying a volume licensed product, such as:
-
-
Office Professional Plus 2013
-
Visio Professional 2013
-
Project Professional 2013
-
-
-
-
-
-
-
-### Excluding Office applications from a package
-
-The following table describes the recommended methods for excluding specific Office applications from a package.
-
-
-
-
-
-
-
-
-
Task
-
Details
-
-
-
-
-
Use the ExcludeApp setting when you create the package by using the Office Deployment Tool.
-
-
Enables you to exclude specific Office applications from the package when the Office Deployment Tool creates the package. For example, you can use this setting to create a package that contains only Microsoft Word.
Modify the DeploymentConfig.xml file after the package has been created. This file contains the default package settings for all users on a computer that is running the App-V Client.
-
-
-
-## Creating an Office 2013 package for App-V with the Office Deployment Tool
-
-
-Complete the following steps to create an Office 2013 package for App-V 5.0 or later.
-
-**Important**
-In App-V 5.0 and later, you must the Office Deployment Tool to create a package. You cannot use the Sequencer to create packages.
-
-
-### Review prerequisites for using the Office Deployment Tool
-
-The computer on which you are installing the Office Deployment Tool must have:
-
-
-
-
-
-
-
-
-
Prerequisite
-
Description
-
-
-
-
-
Prerequisite software
-
.Net Framework 4
-
-
-
Supported operating systems
-
-
64-bit version of Windows 8
-
64-bit version of Windows 7
-
-
-
-
-
-
-**Note**
-In this topic, the term “Office 2013 App-V package” refers to subscription licensing and volume licensing.
-
-
-### Create Office 2013 App-V Packages Using Office Deployment Tool
-
-You create Office 2013 App-V packages by using the Office Deployment Tool. The following instructions explain how to create an Office 2013 App-V package with Volume Licensing or Subscription Licensing.
-
-Create Office 2013 App-V packages on 64-bit Windows computers. Once created, the Office 2013 App-V package will run on 32-bit and 64-bit Windows 7 and Windows 8 computers.
-
-### Download the Office Deployment Tool
-
-Office 2013 App-V Packages are created using the Office Deployment Tool, which generates an Office 2013 App-V Package. The package cannot be created or modified through the App-V sequencer. To begin package creation:
-
-1. Download the [Office Deployment Tool for Click-to-Run](https://www.microsoft.com/download/details.aspx?id=36778).
-
-2. Run the .exe file and extract its features into the desired location. To make this process easier, you can create a shared network folder where the features will be saved.
-
- Example: \\\\Server\\Office2013
-
-3. Check that a setup.exe and a configuration.xml file exist and are in the location you specified.
-
-### Download Office 2013 applications
-
-After you download the Office Deployment Tool, you can use it to get the latest Office 2013 applications. After getting the Office applications, you create the Office 2013 App-V package.
-
-The XML file that is included in the Office Deployment Tool specifies the product details, such as the languages and Office applications included.
-
-1. **Customize the sample XML configuration file:** Use the sample XML configuration file that you downloaded with the Office Deployment Tool to customize the Office applications:
-
- 1. Open the sample XML file in Notepad or your favorite text editor.
-
- 2. With the sample configuration.xml file open and ready for editing, you can specify products, languages, and the path to which you save the Office 2013 applications. The following is a basic example of the configuration.xml file:
-
- ```xml
-
-
-
-
-
-
-
-
-
-
- ```
-
- **Note**
- The configuration XML is a sample XML file. The file includes lines that are commented out. You can “uncomment” these lines to customize additional settings with the file.
-
- The above XML configuration file specifies that Office 2013 ProPlus 32-bit edition, including Visio ProPlus, will be downloaded in English to the \\\\server\\Office 2013, which is the location where Office applications will be saved to. Note that the Product ID of the applications will not affect the final licensing of Office. Office 2013 App-V packages with various licensing can be created from the same applications through specifying licensing in a later stage. The table below summarizes the customizable attributes and elements of XML file:
-
-
-
-
-
-
-
-
-
-
Input
-
Description
-
Example
-
-
-
-
-
Add element
-
Specifies the products and languages to include in the package.
-
N/A
-
-
-
OfficeClientEdition (attribute of Add element)
-
Specifies the edition of Office 2013 product to use: 32-bit or 64-bit. The operation fails if OfficeClientEdition is not set to a valid value.
-
OfficeClientEdition="32"
-
OfficeClientEdition="64"
-
-
-
Product element
-
Specifies the application. Project 2013 and Visio 2013 must be specified here as an added product to be included in the applications.
-
Product ID ="O365ProPlusRetail "
-
Product ID ="VisioProRetail"
-
Product ID ="ProjectProRetail"
-
Product ID ="ProPlusVolume"
-
Product ID ="VisioProVolume"
-
Product ID = "ProjectProVolume"
-
-
-
Language element
-
Specifies the language supported in the applications
-
Language ID="en-us"
-
-
-
Version (attribute of Add element)
-
Optional. Specifies a build to use for the package
-
Defaults to latest advertised build (as defined in v32.CAB at the Office source).
-
15.1.2.3
-
-
-
SourcePath (attribute of Add element)
-
Specifies the location in which the applications will be saved to.
-
Sourcepath = "\Server\Office2013”
-
-
-
-
- After editing the configuration.xml file to specify the desired product, languages, and also the location which the Office 2013 applications will be saved onto, you can save the configuration file, for example, as Customconfig.xml.
-
-2. **Download the applications into the specified location:** Use an elevated command prompt and a 64 bit operating system to download the Office 2013 applications that will later be converted into an App-V package. Below is an example command with description of details:
-
- ``` syntax
- \\server\Office2013\setup.exe /download \\server\Office2013\Customconfig.xml
- ```
-
- In the example:
-
-
-
-
-
-
-
-
-
\server\Office2013
-
is the network share location that contains the Office Deployment Tool and the custom Configuration.xml file, Customconfig.xml.
-
-
-
Setup.exe
-
is the Office Deployment Tool.
-
-
-
/download
-
downloads the Office 2013 applications that you specify in the customConfig.xml file. These bits can be later converted in an Office 2013 App-V package with Volume Licensing.
-
-
-
\server\Office2013\Customconfig.xml
-
passes the XML configuration file required to complete the download process, in this example, customconfig.xml. After using the download command, Office applications should be found in the location specified in the configuration xml file, in this example \Server\Office2013.
-
-
-
-
-
-
-### Convert the Office applications into an App-V package
-
-After you download the Office 2013 applications through the Office Deployment Tool, use the Office Deployment Tool to convert them into an Office 2013 App-V package. Complete the steps that correspond to your licensing model.
-
-**Summary of what you’ll need to do:**
-
-- Create the Office 2013 App-V packages on 64-bit Windows computers. However, the package will run on 32-bit and 64-bit Windows 7 and Windows 8 computers.
-
-- Create an Office App-V package for either Subscription Licensing package or Volume Licensing by using the Office Deployment Tool, and then modify the CustomConfig.xml configuration file.
-
- The following table summarizes the values you need to enter in the CustomConfig.xml file for the licensing model you’re using. The steps in the sections that follow the table will specify the exact entries you need to make.
-
-
-
-
-
-
-
-
-
-
Product ID
-
Volume Licensing
-
Subscription Licensing
-
-
-
-
-
Office 2013
-
ProPlusVolume
-
O365ProPlusRetail
-
-
-
Office 2013 with Visio 2013
-
ProPlusVolume
-
VisioProVolume
-
O365ProPlusRetail
-
VisioProRetail
-
-
-
Office 2013 with Visio 2013 and Project 2013
-
ProPlusVolume
-
VisioProVolume
-
ProjectProVolume
-
O365ProPlusRetail
-
VisioProRetail
-
ProjectProRetail
-
-
-
-
-
-
-**How to convert the Office applications into an App-V package**
-
-1. In Notepad, reopen the CustomConfig.xml file, and make the following changes to the file:
-
-
-
-
-
-
-
-
-
Parameter
-
What to change the value to
-
-
-
-
-
SourcePath
-
Point to the Office applications downloaded earlier.
-
-
-
ProductID
-
Specify the type of licensing, as shown in the following examples:
In this example, the following changes were made to create a package with Volume licensing:
-
-
-
-
-
-
-
-
SourcePath
-
is the path, which was changed to point to the Office applications that were downloaded earlier.
-
-
-
Product ID
-
for Office was changed to ProPlusVolume.
-
-
-
Product ID
-
for Visio was changed to VisioProVolume.
-
-
-
-
-
-
-
-
-
ExcludeApp (optional)
-
Lets you specify Office programs that you don’t want included in the App-V package that the Office Deployment Tool creates. For example, you can exclude Access and InfoPath.
-
-
-
PACKAGEGUID (optional)
-
By default, all App-V packages created by the Office Deployment Tool share the same App-V Package ID. You can use PACKAGEGUID to specify a different package ID for each package, which allows you to publish multiple App-V packages, created by the Office Deployment Tool, and manage them by using the App-V Server.
-
An example of when to use this parameter is if you create different packages for different users. For example, you can create a package with just Office 2013 for some users, and create another package with Office 2013 and Visio 2013 for another set of users.
-
- Note
Even if you use unique package IDs, you can still deploy only one App-V package to a single device.
-
-
-
-
-
-
-
-
-
-
-2. Use the /packager command to convert the Office applications to an Office 2013 App-V package.
-
- For example:
-
- ``` syntax
- \\server\Office2013\setup.exe /packager \\server\Office2013\Customconfig.xml \\server\share\Office2013AppV
- ```
-
- In the example:
-
-
-
-
-
-
-
-
-
\server\Office2013
-
is the network share location that contains the Office Deployment Tool and the custom Configuration.xml file, Customconfig.xml.
-
-
-
Setup.exe
-
is the Office Deployment Tool.
-
-
-
/packager
-
creates the Office 2013 App-V package with Volume Licensing as specified in the customConfig.xml file.
-
-
-
\server\Office2013\Customconfig.xml
-
passes the configuration XML file (in this case customConfig) that has been prepared for the packaging stage.
-
-
-
\server\share\Office 2013AppV
-
specifies the location of the newly created Office App-V package.
-
-
-
-
-
-
-~~~
-After you run the **/packager** command, the following folders appear up in the directory where you specified the package should be saved:
-
-- **App-V Packages** – contains an Office 2013 App-V package and two deployment configuration files.
-
-- **WorkingDir**
-
-**Note**
-To troubleshoot any issues, see the log files in the %temp% directory (default).
-~~~
-
-
-
-3. Verify that the Office 2013 App-V package works correctly:
-
- 1. Publish the Office 2013 App-V package, which you created globally, to a test computer, and verify that the Office 2013 shortcuts appear.
-
- 2. Start a few Office 2013 applications, such as Excel or Word, to ensure that your package is working as expected.
-
-## Publishing the Office package for App-V 5.0
-
-
-Use the following information to publish an Office package.
-
-### Methods for publishing Office App-V packages
-
-Deploy the App-V package for Office 2013 by using the same methods you use for any other package:
-
-- System Center Configuration Manager
-
-- App-V Server
-
-- Stand-alone through PowerShell commands
-
-### Publishing prerequisites and requirements
-
-
-
-
-
-
-
-
-
Prerequisite or requirement
-
Details
-
-
-
-
-
Enable PowerShell scripting on the App-V clients
-
To publish Office 2013 packages, you must run a script.
-
Package scripts are disabled by default on App-V clients. To enable scripting, run the following PowerShell command:
Extension points in the Office App-V package require installation at the computer level.
-
When you publish at the computer level, no prerequisite actions or redistributables are needed, and the Office 2013 package globally enables its applications to work like natively installed Office, eliminating the need for administrators to customize packages.
-
-
-
-
-
-
-### How to publish an Office package
-
-Run the following command to publish an Office package globally:
-
-- `Add-AppvClientPackage | Publish-AppvClientPackage –global`
-
-- From the Web Management Console on the App-V Server, you can add permissions to a group of computers instead of to a user group to enable packages to be published globally to the computers in the corresponding group.
-
-## Customizing and managing Office App-V packages
-
-
-To manage your Office App-V packages, use the same operations as you would for any other package, but there are a few exceptions, as outlined in the following sections.
-
-- [Enabling Office plug-ins by using connection groups](#bkmk-enable-office-plugins)
-
-- [Disabling Office 2013 applications](#bkmk-disable-office-apps)
-
-- [Disabling Office 2013 shortcuts](#bkmk-disable-shortcuts)
-
-- [Managing Office 2013 package upgrades](#bkmk-manage-office-pkg-upgrd)
-
-- [Managing Office 2013 licensing upgrades](#bkmk-manage-office-lic-upgrd)
-
-- [Deploying Visio 2013 and Project 2013 with Office](#bkmk-deploy-visio-project)
-
-### Enabling Office plug-ins by using connection groups
-
-Use the steps in this section to enable Office plug-ins with your Office package. To use Office plug-ins, you must use the App-V Sequencer to create a separate package that contains just the plug-ins. You cannot use the Office Deployment Tool to create the plug-ins package. You then create a connection group that contains the Office package and the plug-ins package, as described in the following steps.
-
-**To enable plug-ins for Office App-V packages**
-
-1. Add a Connection Group through App-V Server, System Center Configuration Manager, or a PowerShell cmdlet.
-
-2. Sequence your plug-ins using the App-V 5.0 Sequencer. Ensure that Office 2013 is installed on the computer being used to sequence the plug-in. It is recommended you use Microsoft 365 Apps for enterprise(non-virtual) on the sequencing computer when you sequence Office 2013 plug-ins.
-
-3. Create an App-V 5.0 package that includes the desired plug-ins.
-
-4. Add a Connection Group through App-V server, System Center Configuration Manager, or a PowerShell cmdlet.
-
-5. Add the Office 2013 App-V package and the plug-ins package you sequenced to the Connection Group you created.
-
- **Important**
- The order of the packages in the Connection Group determines the order in which the package contents are merged. In your Connection group descriptor file, add the Office 2013 App-V package first, and then add the plug-in App-V package.
-
-
-
-6. Ensure that both packages are published to the target computer and that the plug-in package is published globally to match the global settings of the published Office 2013 App-V package.
-
-7. Verify that the Deployment Configuration File of the plug-in package has the same settings that the Office 2013 App-V package has.
-
- Since the Office 2013 App-V package is integrated with the operating system, the plug-in package settings should match. You can search the Deployment Configuration File for “COM Mode” and ensure that your plug-ins package has that value set as “Integrated” and that both "InProcessEnabled" and "OutOfProcessEnabled" match the settings of the Office 2013 App-V package you published.
-
-8. Open the Deployment Configuration File and set the value for **Objects Enabled** to **false**.
-
-9. If you made any changes to the Deployment Configuration file after sequencing, ensure that the plug-in package is published with the file.
-
-10. Ensure that the Connection Group you created is enabled onto your desired computer. The Connection Group created will likely “pend” if the Office 2013 App-V package is in use when the Connection Group is enabled. If that happens, you have to reboot to successfully enable the Connection Group.
-
-11. After you successfully publish both packages and enable the Connection Group, start the target Office 2013 application and verify that the plug-in you published and added to the connection group works as expected.
-
-### Disabling Office 2013 applications
-
-You may want to disable specific applications in your Office App-V package. For instance, you can disable Access, but leave all other Office application main available. When you disable an application, the end user will no longer see the shortcut for that application. You do not have to re-sequence the application. When you change the Deployment Configuration File after the Office 2013 App-V package has been published, you will save the changes, add the Office 2013 App-V package, and then republish it with the new Deployment Configuration File to apply the new settings to Office 2013 App-V Package applications.
-
-**Note**
-To exclude specific Office applications (for example, Access and InfoPath) when you create the App-V package with the Office Deployment Tool, use the **ExcludeApp** setting. For more information, see [Reference for Click-to-Run configuration.xml file](https://technet.microsoft.com/library/jj219426.aspx).
-
-
-
-**To disable an Office 2013 application**
-
-1. Open a Deployment Configuration File with a text editor such as **Notepad** and search for “Applications."
-
-2. Search for the Office application you want to disable, for example, Access 2013.
-
-3. Change the value of "Enabled" from "true" to "false."
-
-4. Save the Deployment Configuration File.
-
-5. Add the Office 2013 App-V Package with the new Deployment Configuration File.
-
- ```xml
-
-
- InfoPath Filler 2013
-
-
-
-
-
-
- Lync 2013
-
-
-
-
-
-
- Access 2013
-
-
-
-
- ```
-
-6. Re-add the Office 2013 App-V package, and then republish it with the new Deployment Configuration File to apply the new settings to Office 2013 App-V Package applications.
-
-### Disabling Office 2013 shortcuts
-
-You may want to disable shortcuts for certain Office applications instead of unpublishing or removing the package. The following example shows how to disable shortcuts for Microsoft Access.
-
-**To disable shortcuts for Office 2013 applications**
-
-1. Open a Deployment Configuration File in Notepad and search for “Shortcuts”.
-
-2. To disable certain shortcuts, delete or comment out the specific shortcuts you don’t want. You must keep the subsystem present and enabled. For example, in the example below, delete the Microsoft Access shortcuts, while keeping the subsystems <shortcut> </shortcut> intact to disable the Microsoft Access shortcut.
-
- ``` syntax
- Shortcuts
-
- -->
-
-
-
-
- [{Common Programs}]\Microsoft Office 2013\Access 2013.lnk
- [{AppvPackageRoot}])office15\MSACCESS.EXE
- [{Windows}]\Installer\{90150000-000F-0000-0000-000000FF1CE)\accicons.exe.Ø.ico
-
-
- Microsoft.Office.MSACCESS.EXE.15
- true
- Build a professional app quickly to manage data.
- l
- [{AppVPackageRoot}]\office15\MSACCESS.EXE
-
- ```
-
-3. Save the Deployment Configuration File.
-
-4. Republish Office 2013 App-V Package with new Deployment Configuration File.
-
-Many additional settings can be changed through modifying the Deployment Configuration for App-V packages, for example, file type associations, Virtual File System, and more. For additional information on how to use Deployment Configuration Files to change App-V package settings, refer to the additional resources section at the end of this document.
-
-### Managing Office 2013 package upgrades
-
-To upgrade an Office 2013 package, use the Office Deployment Tool. To upgrade a previously deployed Office 2013 package, perform the following steps.
-
-**How to upgrade a previously deployed Office 2013 package**
-
-1. Create a new Office 2013 package through the Office Deployment Tool that uses the most recent Office 2013 application software. The most recent Office 2013 bits can always be obtained through the download stage of creating an Office 2013 App-V Package. The newly created Office 2013 package will have the most recent updates and a new Version ID. All packages created using the Office Deployment Tool have the same lineage.
-
- **Note**
- Office App-V packages have two Version IDs:
-
- - An Office 2013 App-V Package Version ID that is unique across all packages created using the Office Deployment Tool.
-
- - A second App-V Package Version ID, x.x.x.x for example, in the AppX manifest that will only change if there is a new version of Office itself. For example, if a new Office 2013 release with upgrades is available, and a package is created through the Office Deployment Tool to incorporate these upgrades, the X.X.X.X version ID will change to reflect that the Office version itself has changed. The App-V server will use the X.X.X.X version ID to differentiate this package and recognize that it contains new upgrades to the previously published package, and as a result, publish it as an upgrade to the existing Office 2013 package.
-
-
-
-2. Globally publish the newly created Office 2013 App-V Packages onto computers where you would like to apply the new updates. Since the new package has the same lineage of the older Office 2013 App-V Package, publishing the new package with the updates will only apply the new changes to the old package, and thus will be fast.
-
-3. Upgrades will be applied in the same manner of any globally published App-V Packages. Because applications will probably be in use, upgrades might be delayed until the computer is rebooted.
-
-### Managing Office 2013 licensing upgrades
-
-If a new Office 2013 App-V Package has a different license than the Office 2013 App-V Package currently deployed. For instance, the Office 2013 package deployed is a subscription based Office 2013 and the new Office 2013 package is Volume Licensing based, the following instructions must be followed to ensure smooth licensing upgrade:
-
-**How to upgrade an Office 2013 License**
-
-1. Unpublish the already deployed Office 2013 Subscription Licensing App-V package.
-
-2. Remove the unpublished Office 2013 Subscription Licensing App-V package.
-
-3. Restart the computer.
-
-4. Add the new Office 2013 App-V Package Volume Licensing.
-
-5. Publish the added Office 2013 App-V Package with Volume Licensing.
-
-An Office 2013 App-V Package with your chosen licensing will be successfully deployed.
-
-### Deploying Visio 2013 and Project 2013 with Office
-
-The following table describes the requirements and options for deploying Visio 2013 and Project 2013 with Office.
-
-
-
-
-
-
-
-
-
Task
-
Details
-
-
-
-
-
How do I package and publish Visio 2013 and Project 2013 with Office?
-
You must include Visio 2013 and Project 2013 in the same package with Office.
How can I deploy Visio 2013 and Project 2013 to specific users?
-
Use one of the following methods:
-
-
-
-
-
-
-
-
If you want to...
-
...then use this method
-
-
-
-
-
Create two different packages and deploy each one to a different group of users
-
Create and deploy the following packages:
-
-
A package that contains only Office - deploy to computers whose users need only Office.
-
A package that contains Office, Visio, and Project - deploy to computers whose users need all three applications.
-
-
-
-
If you want only one package for the whole organization, or if you have users who share computers:
-
Follows these steps:
-
-
Create a package that contains Office, Visio, and Project.
-
Deploy the package to all users.
-
Use Microsoft AppLocker to prevent specific users from using Visio and Project.
-
-
-
-
-
-
-
-
-
-
-
-## Additional resources
-
-
-**Office 2013 App-V 5.0 Packages 5.0 Additional Resources**
-
-[Office Deployment Tool for Click-to-Run](https://go.microsoft.com/fwlink/p/?LinkID=330672)
-
-[Supported scenarios for deploying Microsoft Office as a sequenced App-V Package](https://go.microsoft.com/fwlink/p/?LinkId=330680)
-
-**Office 2010 App-V 5.0 Packages**
-
-[Microsoft Office 2010 Sequencing Kit for Microsoft Application Virtualization 5.0](https://go.microsoft.com/fwlink/p/?LinkId=330681)
-
-[Known issues when you create or use an App-V 5.0 Office 2010 package](https://go.microsoft.com/fwlink/p/?LinkId=330682)
-
-[How to sequence Microsoft Office 2010 in Microsoft Application Virtualization 5.0](https://go.microsoft.com/fwlink/p/?LinkId=330676)
-
-**Connection Groups**
-
-[Deploying Connection Groups in Microsoft App-V v5](https://go.microsoft.com/fwlink/p/?LinkId=330683)
-
-[Managing Connection Groups](managing-connection-groups.md)
-
-**Dynamic Configuration**
-
-[About App-V 5.0 Dynamic Configuration](about-app-v-50-dynamic-configuration.md)
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v5/deploying-microsoft-office-2013-by-using-app-v51.md b/mdop/appv-v5/deploying-microsoft-office-2013-by-using-app-v51.md
deleted file mode 100644
index 3c08f56eaf..0000000000
--- a/mdop/appv-v5/deploying-microsoft-office-2013-by-using-app-v51.md
+++ /dev/null
@@ -1,902 +0,0 @@
----
-title: Deploying Microsoft Office 2013 by Using App-V
-description: Deploying Microsoft Office 2013 by Using App-V
-author: dansimp
-ms.assetid: 9a7be05e-2a7a-4874-af25-09c0f5037876
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 11/02/2016
----
-
-
-# Deploying Microsoft Office 2013 by Using App-V
-
-
-Use the information in this article to use Microsoft Application Virtualization (App-V) 5.1, or later versions, to deliver Microsoft Office 2013 as a virtualized application to computers in your organization. For information about using App-V to deliver Office 2010, see [Deploying Microsoft Office 2010 by Using App-V](deploying-microsoft-office-2010-by-using-app-v51.md). To successfully deploy Office 2013 with App-V, you need to be familiar with Office 2013 and App-V.
-
-This topic contains the following sections:
-
-- [What to know before you start](#bkmk-before-you-start)
-
-- [Creating an Office 2013 package for App-V with the Office Deployment Tool](#bkmk-create-office-pkg)
-
-- [Publishing the Office package for App-V 5.1](#bkmk-pub-pkg-office)
-
-- [Customizing and managing Office App-V packages](#bkmk-custmz-manage-office-pkgs)
-
-## What to know before you start
-
-
-Before you deploy Office 2013 by using App-V, review the following planning information.
-
-### Supported Office versions and Office coexistence
-
-Use the following table to get information about supported versions of Office and about running coexisting versions of Office.
-
-
Considerations for installing different versions of Office on the same computer
-
-
-
-
-
-### Packaging, publishing, and deployment requirements
-
-Before you deploy Office by using App-V, review the following requirements.
-
-
-
-
-
-
-
-
-
Task
-
Requirement
-
-
-
-
-
Packaging
-
-
All of the Office applications that you want to deploy to users must be in a single package.
-
In App-V 5.1 and later, you must use the Office Deployment Tool to create packages. You cannot use the Sequencer.
-
If you are deploying Microsoft Visio 2013 and Microsoft Project 2013 along with Office, you must include them in the same package with Office. For more information, see Deploying Visio 2013 and Project 2013 with Office.
-
-
-
-
Publishing
-
-
You can publish only one Office package to each client computer.
-
You must publish the Office package globally. You cannot publish to the user.
-
-
-
-
Deploying any of the following products to a shared computer, for example, by using Remote Desktop Services:
You don’t use shared computer activation if you’re deploying a volume licensed product, such as:
-
-
Office Professional Plus 2013
-
Visio Professional 2013
-
Project Professional 2013
-
-
-
-
-
-
-
-### Excluding Office applications from a package
-
-The following table describes the recommended methods for excluding specific Office applications from a package.
-
-
-
-
-
-
-
-
-
Task
-
Details
-
-
-
-
-
Use the ExcludeApp setting when you create the package by using the Office Deployment Tool.
-
-
Enables you to exclude specific Office applications from the package when the Office Deployment Tool creates the package. For example, you can use this setting to create a package that contains only Microsoft Word.
Modify the DeploymentConfig.xml file after the package has been created. This file contains the default package settings for all users on a computer that is running the App-V Client.
-
-
-
-## Creating an Office 2013 package for App-V with the Office Deployment Tool
-
-
-Complete the following steps to create an Office 2013 package for App-V 5.1 or later.
-
-**Important**
-In App-V 5.1 and later, you must the Office Deployment Tool to create a package. You cannot use the Sequencer to create packages.
-
-
-
-### Review prerequisites for using the Office Deployment Tool
-
-The computer on which you are installing the Office Deployment Tool must have:
-
-
-
-
-
-
-
-
-
Prerequisite
-
Description
-
-
-
-
-
Prerequisite software
-
.Net Framework 4
-
-
-
Supported operating systems
-
-
64-bit version of Windows 8 or later
-
64-bit version of Windows 7
-
-
-
-
-
-
-
-**Note**
-In this topic, the term “Office 2013 App-V package” refers to subscription licensing and volume licensing.
-
-
-
-### Create Office 2013 App-V Packages Using Office Deployment Tool
-
-You create Office 2013 App-V packages by using the Office Deployment Tool. The following instructions explain how to create an Office 2013 App-V package with Volume Licensing or Subscription Licensing.
-
-Create Office 2013 App-V packages on 64-bit Windows computers. Once created, the Office 2013 App-V package will run on 32-bit and 64-bit Windows 7, Windows 8.1, and Windows 10 computers.
-
-### Download the Office Deployment Tool
-
-Office 2013 App-V Packages are created using the Office Deployment Tool, which generates an Office 2013 App-V Package. The package cannot be created or modified through the App-V sequencer. To begin package creation:
-
-1. Download the [Office Deployment Tool for Click-to-Run](https://www.microsoft.com/download/details.aspx?id=36778).
-
-2. Run the .exe file and extract its features into the desired location. To make this process easier, you can create a shared network folder where the features will be saved.
-
- Example: \\\\Server\\Office2013
-
-3. Check that a setup.exe and a configuration.xml file exist and are in the location you specified.
-
-### Download Office 2013 applications
-
-After you download the Office Deployment Tool, you can use it to get the latest Office 2013 applications. After getting the Office applications, you create the Office 2013 App-V package.
-
-The XML file that is included in the Office Deployment Tool specifies the product details, such as the languages and Office applications included.
-
-1. **Customize the sample XML configuration file:** Use the sample XML configuration file that you downloaded with the Office Deployment Tool to customize the Office applications:
-
- 1. Open the sample XML file in Notepad or your favorite text editor.
-
- 2. With the sample configuration.xml file open and ready for editing, you can specify products, languages, and the path to which you save the Office 2013 applications. The following is a basic example of the configuration.xml file:
-
- ```xml
-
-
-
-
-
-
-
-
-
-
- ```
-
- **Note**
- The configuration XML is a sample XML file. The file includes lines that are commented out. You can “uncomment” these lines to customize additional settings with the file.
-
-
-
-~~~
- The above XML configuration file specifies that Office 2013 ProPlus 32-bit edition, including Visio ProPlus, will be downloaded in English to the \\\\server\\Office 2013, which is the location where Office applications will be saved to. Note that the Product ID of the applications will not affect the final licensing of Office. Office 2013 App-V packages with various licensing can be created from the same applications through specifying licensing in a later stage. The table below summarizes the customizable attributes and elements of XML file:
-
-
-
-
-
-
-
-
-
-
Input
-
Description
-
Example
-
-
-
-
-
Add element
-
Specifies the products and languages to include in the package.
-
N/A
-
-
-
OfficeClientEdition (attribute of Add element)
-
Specifies the edition of Office 2013 product to use: 32-bit or 64-bit. The operation fails if OfficeClientEdition is not set to a valid value.
-
OfficeClientEdition="32"
-
OfficeClientEdition="64"
-
-
-
Product element
-
Specifies the application. Project 2013 and Visio 2013 must be specified here as an added product to be included in the applications.
-
Product ID ="O365ProPlusRetail "
-
Product ID ="VisioProRetail"
-
Product ID ="ProjectProRetail"
-
Product ID ="ProPlusVolume"
-
Product ID ="VisioProVolume"
-
Product ID = "ProjectProVolume"
-
-
-
Language element
-
Specifies the language supported in the applications
-
Language ID="en-us"
-
-
-
Version (attribute of Add element)
-
Optional. Specifies a build to use for the package
-
Defaults to latest advertised build (as defined in v32.CAB at the Office source).
-
15.1.2.3
-
-
-
SourcePath (attribute of Add element)
-
Specifies the location in which the applications will be saved to.
-
Sourcepath = "\\Server\Office2013”
-
-
-
-
-
-
- After editing the configuration.xml file to specify the desired product, languages, and also the location which the Office 2013 applications will be saved onto, you can save the configuration file, for example, as Customconfig.xml.
-~~~
-
-2. **Download the applications into the specified location:** Use an elevated command prompt and a 64 bit operating system to download the Office 2013 applications that will later be converted into an App-V package. Below is an example command with description of details:
-
- ``` syntax
- \\server\Office2013\setup.exe /download \\server\Office2013\Customconfig.xml
- ```
-
- In the example:
-
-
-
-
-
-
-
-
-
\server\Office2013
-
is the network share location that contains the Office Deployment Tool and the custom Configuration.xml file, Customconfig.xml.
-
-
-
Setup.exe
-
is the Office Deployment Tool.
-
-
-
/download
-
downloads the Office 2013 applications that you specify in the customConfig.xml file. These bits can be later converted in an Office 2013 App-V package with Volume Licensing.
-
-
-
\server\Office2013\Customconfig.xml
-
passes the XML configuration file required to complete the download process, in this example, customconfig.xml. After using the download command, Office applications should be found in the location specified in the configuration xml file, in this example \Server\Office2013.
-
-
-
-
-
-
-### Convert the Office applications into an App-V package
-
-After you download the Office 2013 applications through the Office Deployment Tool, use the Office Deployment Tool to convert them into an Office 2013 App-V package. Complete the steps that correspond to your licensing model.
-
-**Summary of what you’ll need to do:**
-
-- Create the Office 2013 App-V packages on 64-bit Windows computers. However, the package will run on 32-bit and 64-bit Windows 7, Windows 8, and Windows 10 computers.
-
-- Create an Office App-V package for either Subscription Licensing package or Volume Licensing by using the Office Deployment Tool, and then modify the CustomConfig.xml configuration file.
-
- The following table summarizes the values you need to enter in the CustomConfig.xml file for the licensing model you’re using. The steps in the sections that follow the table will specify the exact entries you need to make.
-
-
-
-
-
-
-
-
-
-
Product ID
-
Volume Licensing
-
Subscription Licensing
-
-
-
-
-
Office 2013
-
ProPlusVolume
-
O365ProPlusRetail
-
-
-
Office 2013 with Visio 2013
-
ProPlusVolume
-
VisioProVolume
-
O365ProPlusRetail
-
VisioProRetail
-
-
-
Office 2013 with Visio 2013 and Project 2013
-
ProPlusVolume
-
VisioProVolume
-
ProjectProVolume
-
O365ProPlusRetail
-
VisioProRetail
-
ProjectProRetail
-
-
-
-
-
-
-**How to convert the Office applications into an App-V package**
-
-1. In Notepad, reopen the CustomConfig.xml file, and make the following changes to the file:
-
-
-
-
-
-
-
-
-
Parameter
-
What to change the value to
-
-
-
-
-
SourcePath
-
Point to the Office applications downloaded earlier.
-
-
-
ProductID
-
Specify the type of licensing, as shown in the following examples:
In this example, the following changes were made to create a package with Volume licensing:
-
-
-
-
-
-
-
-
SourcePath
-
is the path, which was changed to point to the Office applications that were downloaded earlier.
-
-
-
Product ID
-
for Office was changed to ProPlusVolume.
-
-
-
Product ID
-
for Visio was changed to VisioProVolume.
-
-
-
-
-
-
-
-
-
ExcludeApp (optional)
-
Lets you specify Office programs that you don’t want included in the App-V package that the Office Deployment Tool creates. For example, you can exclude Access and InfoPath.
-
-
-
PACKAGEGUID (optional)
-
By default, all App-V packages created by the Office Deployment Tool share the same App-V Package ID. You can use PACKAGEGUID to specify a different package ID for each package, which allows you to publish multiple App-V packages, created by the Office Deployment Tool, and manage them by using the App-V Server.
-
An example of when to use this parameter is if you create different packages for different users. For example, you can create a package with just Office 2013 for some users, and create another package with Office 2013 and Visio 2013 for another set of users.
-
- Note
Even if you use unique package IDs, you can still deploy only one App-V package to a single device.
-
-
-
-
-
-
-
-
-
-
-2. Use the /packager command to convert the Office applications to an Office 2013 App-V package.
-
- For example:
-
- ``` syntax
- \\server\Office2013\setup.exe /packager \\server\Office2013\Customconfig.xml \\server\share\Office2013AppV
- ```
-
- In the example:
-
-
-
-
-
-
-
-
-
\server\Office2013
-
is the network share location that contains the Office Deployment Tool and the custom Configuration.xml file, Customconfig.xml.
-
-
-
Setup.exe
-
is the Office Deployment Tool.
-
-
-
/packager
-
creates the Office 2013 App-V package with Volume Licensing as specified in the customConfig.xml file.
-
-
-
\server\Office2013\Customconfig.xml
-
passes the configuration XML file (in this case customConfig) that has been prepared for the packaging stage.
-
-
-
\server\share\Office 2013AppV
-
specifies the location of the newly created Office App-V package.
-
-
-
-
-
-
-~~~
-After you run the **/packager** command, the following folders appear up in the directory where you specified the package should be saved:
-
-- **App-V Packages** – contains an Office 2013 App-V package and two deployment configuration files.
-
-- **WorkingDir**
-
-**Note**
-To troubleshoot any issues, see the log files in the %temp% directory (default).
-~~~
-
-
-
-3. Verify that the Office 2013 App-V package works correctly:
-
- 1. Publish the Office 2013 App-V package, which you created globally, to a test computer, and verify that the Office 2013 shortcuts appear.
-
- 2. Start a few Office 2013 applications, such as Excel or Word, to ensure that your package is working as expected.
-
-## Publishing the Office package for App-V 5.1
-
-
-Use the following information to publish an Office package.
-
-### Methods for publishing Office App-V packages
-
-Deploy the App-V package for Office 2013 by using the same methods you use for any other package:
-
-- System Center Configuration Manager
-
-- App-V Server
-
-- Stand-alone through PowerShell commands
-
-### Publishing prerequisites and requirements
-
-
-
-
-
-
-
-
-
Prerequisite or requirement
-
Details
-
-
-
-
-
Enable PowerShell scripting on the App-V clients
-
To publish Office 2013 packages, you must run a script.
-
Package scripts are disabled by default on App-V clients. To enable scripting, run the following PowerShell command:
Extension points in the Office App-V package require installation at the computer level.
-
When you publish at the computer level, no prerequisite actions or redistributables are needed, and the Office 2013 package globally enables its applications to work like natively installed Office, eliminating the need for administrators to customize packages.
-
-
-
-
-
-
-### How to publish an Office package
-
-Run the following command to publish an Office package globally:
-
-- `Add-AppvClientPackage | Publish-AppvClientPackage –global`
-
-- From the Web Management Console on the App-V Server, you can add permissions to a group of computers instead of to a user group to enable packages to be published globally to the computers in the corresponding group.
-
-## Customizing and managing Office App-V packages
-
-
-To manage your Office App-V packages, use the same operations as you would for any other package, but there are a few exceptions, as outlined in the following sections.
-
-- [Enabling Office plug-ins by using connection groups](#bkmk-enable-office-plugins)
-
-- [Disabling Office 2013 applications](#bkmk-disable-office-apps)
-
-- [Disabling Office 2013 shortcuts](#bkmk-disable-shortcuts)
-
-- [Managing Office 2013 package upgrades](#bkmk-manage-office-pkg-upgrd)
-
-- [Managing Office 2013 licensing upgrades](#bkmk-manage-office-lic-upgrd)
-
-- [Deploying Visio 2013 and Project 2013 with Office](#bkmk-deploy-visio-project)
-
-### Enabling Office plug-ins by using connection groups
-
-Use the steps in this section to enable Office plug-ins with your Office package. To use Office plug-ins, you must use the App-V Sequencer to create a separate package that contains just the plug-ins. You cannot use the Office Deployment Tool to create the plug-ins package. You then create a connection group that contains the Office package and the plug-ins package, as described in the following steps.
-
-**To enable plug-ins for Office App-V packages**
-
-1. Add a Connection Group through App-V Server, System Center Configuration Manager, or a PowerShell cmdlet.
-
-2. Sequence your plug-ins using the App-V 5.1 Sequencer. Ensure that Office 2013 is installed on the computer being used to sequence the plug-in. It is recommended you use Microsoft 365 Apps for enterprise(non-virtual) on the sequencing computer when you sequence Office 2013 plug-ins.
-
-3. Create an App-V 5.1 package that includes the desired plug-ins.
-
-4. Add a Connection Group through App-V server, System Center Configuration Manager, or a PowerShell cmdlet.
-
-5. Add the Office 2013 App-V package and the plug-ins package you sequenced to the Connection Group you created.
-
- **Important**
- The order of the packages in the Connection Group determines the order in which the package contents are merged. In your Connection group descriptor file, add the Office 2013 App-V package first, and then add the plug-in App-V package.
-
-
-
-6. Ensure that both packages are published to the target computer and that the plug-in package is published globally to match the global settings of the published Office 2013 App-V package.
-
-7. Verify that the Deployment Configuration File of the plug-in package has the same settings that the Office 2013 App-V package has.
-
- Since the Office 2013 App-V package is integrated with the operating system, the plug-in package settings should match. You can search the Deployment Configuration File for “COM Mode” and ensure that your plug-ins package has that value set as “Integrated” and that both "InProcessEnabled" and "OutOfProcessEnabled" match the settings of the Office 2013 App-V package you published.
-
-8. Open the Deployment Configuration File and set the value for **Objects Enabled** to **false**.
-
-9. If you made any changes to the Deployment Configuration file after sequencing, ensure that the plug-in package is published with the file.
-
-10. Ensure that the Connection Group you created is enabled onto your desired computer. The Connection Group created will likely “pend” if the Office 2013 App-V package is in use when the Connection Group is enabled. If that happens, you have to reboot to successfully enable the Connection Group.
-
-11. After you successfully publish both packages and enable the Connection Group, start the target Office 2013 application and verify that the plug-in you published and added to the connection group works as expected.
-
-### Disabling Office 2013 applications
-
-You may want to disable specific applications in your Office App-V package. For instance, you can disable Access, but leave all other Office application main available. When you disable an application, the end user will no longer see the shortcut for that application. You do not have to re-sequence the application. When you change the Deployment Configuration File after the Office 2013 App-V package has been published, you will save the changes, add the Office 2013 App-V package, and then republish it with the new Deployment Configuration File to apply the new settings to Office 2013 App-V Package applications.
-
-**Note**
-To exclude specific Office applications (for example, Access and InfoPath) when you create the App-V package with the Office Deployment Tool, use the **ExcludeApp** setting. For more information, see [Reference for Click-to-Run configuration.xml file](https://technet.microsoft.com/library/jj219426.aspx).
-
-
-
-**To disable an Office 2013 application**
-
-1. Open a Deployment Configuration File with a text editor such as **Notepad** and search for “Applications."
-
-2. Search for the Office application you want to disable, for example, Access 2013.
-
-3. Change the value of "Enabled" from "true" to "false."
-
-4. Save the Deployment Configuration File.
-
-5. Add the Office 2013 App-V Package with the new Deployment Configuration File.
-
- ```xml
-
-
- InfoPath Filler 2013
-
-
-
-
-
-
- Lync 2013
-
-
-
-
-
-
- Access 2013
-
-
-
-
- ```
-
-6. Re-add the Office 2013 App-V package, and then republish it with the new Deployment Configuration File to apply the new settings to Office 2013 App-V Package applications.
-
-### Disabling Office 2013 shortcuts
-
-You may want to disable shortcuts for certain Office applications instead of unpublishing or removing the package. The following example shows how to disable shortcuts for Microsoft Access.
-
-**To disable shortcuts for Office 2013 applications**
-
-1. Open a Deployment Configuration File in Notepad and search for “Shortcuts”.
-
-2. To disable certain shortcuts, delete or comment out the specific shortcuts you don’t want. You must keep the subsystem present and enabled. For example, in the example below, delete the Microsoft Access shortcuts, while keeping the subsystems <shortcut> </shortcut> intact to disable the Microsoft Access shortcut.
-
- ``` syntax
- Shortcuts
-
- -->
-
-
-
-
- [{Common Programs}]\Microsoft Office 2013\Access 2013.lnk
- [{AppvPackageRoot}])office15\MSACCESS.EXE
- [{Windows}]\Installer\{90150000-000F-0000-0000-000000FF1CE)\accicons.exe.Ø.ico
-
-
- Microsoft.Office.MSACCESS.EXE.15
- true
- Build a professional app quickly to manage data.
- l
- [{AppVPackageRoot}]\office15\MSACCESS.EXE
-
- ```
-
-3. Save the Deployment Configuration File.
-
-4. Republish Office 2013 App-V Package with new Deployment Configuration File.
-
-Many additional settings can be changed through modifying the Deployment Configuration for App-V packages, for example, file type associations, Virtual File System, and more. For additional information on how to use Deployment Configuration Files to change App-V package settings, refer to the additional resources section at the end of this document.
-
-### Managing Office 2013 package upgrades
-
-To upgrade an Office 2013 package, use the Office Deployment Tool. To upgrade a previously deployed Office 2013 package, perform the following steps.
-
-**How to upgrade a previously deployed Office 2013 package**
-
-1. Create a new Office 2013 package through the Office Deployment Tool that uses the most recent Office 2013 application software. The most recent Office 2013 bits can always be obtained through the download stage of creating an Office 2013 App-V Package. The newly created Office 2013 package will have the most recent updates and a new Version ID. All packages created using the Office Deployment Tool have the same lineage.
-
- **Note**
- Office App-V packages have two Version IDs:
-
- - An Office 2013 App-V Package Version ID that is unique across all packages created using the Office Deployment Tool.
-
- - A second App-V Package Version ID, x.x.x.x for example, in the AppX manifest that will only change if there is a new version of Office itself. For example, if a new Office 2013 release with upgrades is available, and a package is created through the Office Deployment Tool to incorporate these upgrades, the X.X.X.X version ID will change to reflect that the Office version itself has changed. The App-V server will use the X.X.X.X version ID to differentiate this package and recognize that it contains new upgrades to the previously published package, and as a result, publish it as an upgrade to the existing Office 2013 package.
-
-
-
-2. Globally publish the newly created Office 2013 App-V Packages onto computers where you would like to apply the new updates. Since the new package has the same lineage of the older Office 2013 App-V Package, publishing the new package with the updates will only apply the new changes to the old package, and thus will be fast.
-
-3. Upgrades will be applied in the same manner of any globally published App-V Packages. Because applications will probably be in use, upgrades might be delayed until the computer is rebooted.
-
-### Managing Office 2013 licensing upgrades
-
-If a new Office 2013 App-V Package has a different license than the Office 2013 App-V Package currently deployed. For instance, the Office 2013 package deployed is a subscription based Office 2013 and the new Office 2013 package is Volume Licensing based, the following instructions must be followed to ensure smooth licensing upgrade:
-
-**How to upgrade an Office 2013 License**
-
-1. Unpublish the already deployed Office 2013 Subscription Licensing App-V package.
-
-2. Remove the unpublished Office 2013 Subscription Licensing App-V package.
-
-3. Restart the computer.
-
-4. Add the new Office 2013 App-V Package Volume Licensing.
-
-5. Publish the added Office 2013 App-V Package with Volume Licensing.
-
-An Office 2013 App-V Package with your chosen licensing will be successfully deployed.
-
-### Deploying Visio 2013 and Project 2013 with Office
-
-The following table describes the requirements and options for deploying Visio 2013 and Project 2013 with Office.
-
-
-
-
-
-
-
-
-
Task
-
Details
-
-
-
-
-
How do I package and publish Visio 2013 and Project 2013 with Office?
-
You must include Visio 2013 and Project 2013 in the same package with Office.
How can I deploy Visio 2013 and Project 2013 to specific users?
-
Use one of the following methods:
-
-
-
-
-
-
-
-
If you want to...
-
...then use this method
-
-
-
-
-
Create two different packages and deploy each one to a different group of users
-
Create and deploy the following packages:
-
-
A package that contains only Office - deploy to computers whose users need only Office.
-
A package that contains Office, Visio, and Project - deploy to computers whose users need all three applications.
-
-
-
-
If you want only one package for the whole organization, or if you have users who share computers:
-
Follows these steps:
-
-
Create a package that contains Office, Visio, and Project.
-
Deploy the package to all users.
-
Use Microsoft AppLocker to prevent specific users from using Visio and Project.
-
-
-
-
-
-
-
-
-
-
-
-## Additional resources
-
-
-**Office 2013 App-V Packages Additional Resources**
-
-[Office Deployment Tool for Click-to-Run](https://go.microsoft.com/fwlink/p/?LinkID=330672)
-
-[Supported scenarios for deploying Microsoft Office as a sequenced App-V Package](https://go.microsoft.com/fwlink/p/?LinkId=330680)
-
-**Office 2010 App-V Packages**
-
-[Microsoft Office 2010 Sequencing Kit for Microsoft Application Virtualization 5.0](https://go.microsoft.com/fwlink/p/?LinkId=330681)
-
-[Known issues when you create or use an App-V 5.0 Office 2010 package](https://go.microsoft.com/fwlink/p/?LinkId=330682)
-
-[How to sequence Microsoft Office 2010 in Microsoft Application Virtualization 5.0](https://go.microsoft.com/fwlink/p/?LinkId=330676)
-
-**Connection Groups**
-
-[Deploying Connection Groups in Microsoft App-V v5](https://go.microsoft.com/fwlink/p/?LinkId=330683)
-
-[Managing Connection Groups](managing-connection-groups51.md)
-
-**Dynamic Configuration**
-
-[About App-V 5.1 Dynamic Configuration](about-app-v-51-dynamic-configuration.md)
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/mdop/appv-v5/deploying-microsoft-office-2016-by-using-app-v.md b/mdop/appv-v5/deploying-microsoft-office-2016-by-using-app-v.md
deleted file mode 100644
index 2856f34f5d..0000000000
--- a/mdop/appv-v5/deploying-microsoft-office-2016-by-using-app-v.md
+++ /dev/null
@@ -1,796 +0,0 @@
----
-title: Deploying Microsoft Office 2016 by Using App-V
-description: Deploying Microsoft Office 2016 by Using App-V
-author: dansimp
-ms.assetid: cc675cde-cb8d-4b7c-a700-6104b78f1d89
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 07/25/2017
----
-
-
-# Deploying Microsoft Office 2016 by Using App-V
-
-
-Use the information in this article to use Microsoft Application Virtualization 5.0, or later versions, to deliver Microsoft Office 2016 as a virtualized application to computers in your organization. For information about using App-V to deliver Office 2013, see [Deploying Microsoft Office 2013 by Using App-V](deploying-microsoft-office-2013-by-using-app-v.md). For information about using App-V to deliver Office 2010, see [Deploying Microsoft Office 2010 by Using App-V](deploying-microsoft-office-2010-by-using-app-v.md).
-
-This topic contains the following sections:
-
-- [What to know before you start](#bkmk-before-you-start)
-
-- [Creating an Office 2016 package for App-V with the Office Deployment Tool](#bkmk-create-office-pkg)
-
-- [Publishing the Office package for App-V 5.0](#bkmk-pub-pkg-office)
-
-- [Customizing and managing Office App-V packages](#bkmk-custmz-manage-office-pkgs)
-
-## What to know before you start
-
-
-Before you deploy Office 2016 by using App-V, review the following planning information.
-
-### Supported Office versions and Office coexistence
-
-Use the following table to get information about supported versions of Office and about running coexisting versions of Office.
-
-
Considerations for installing different versions of Office on the same computer
-
-
-
-
-
-
-### Packaging, publishing, and deployment requirements
-
-Before you deploy Office by using App-V, review the following requirements.
-
-
-
-
-
-
-
-
-
Task
-
Requirement
-
-
-
-
-
Packaging
-
-
-
All of the Office applications that you want to deploy to users must be in a single package.
-
In App-V 5.0 and later, you must use the Office Deployment Tool to create packages. You cannot use the Sequencer.
-
If you are deploying Microsoft Visio 2016 and Microsoft Project 2016 along with Office, you must include them in the same package with Office. For more information, see Deploying Visio 2016 and Project 2016 with Office.
-
-
-
-
Publishing
-
-
You can publish only one Office package to each client computer.
-
You must publish the Office package globally. You cannot publish to the user.
-
-
-
-
Deploying any of the following products to a shared computer, for example, by using Remote Desktop Services:
-
-
-
-### Excluding Office applications from a package
-
-The following table describes the recommended methods for excluding specific Office applications from a package.
-
-
-
-
-
-
-
-
-
Task
-
Details
-
-
-
-
-
Use the ExcludeApp setting when you create the package by using the Office Deployment Tool.
-
-
Enables you to exclude specific Office applications from the package when the Office Deployment Tool creates the package. For example, you can use this setting to create a package that contains only Microsoft Word.
Modify the DeploymentConfig.xml file after the package has been created. This file contains the default package settings for all users on a computer that is running the App-V Client.
-
-
-
-## Creating an Office 2016 package for App-V with the Office Deployment Tool
-
-
-Complete the following steps to create an Office 2016 package for App-V 5.0 or later.
-
->**Important** In App-V 5.0 and later, you must use the Office Deployment Tool to create a package. You cannot use the Sequencer to create packages.
-
-### Review prerequisites for using the Office Deployment Tool
-
-The computer on which you are installing the Office Deployment Tool must have:
-
-
-
-
-
-
-
-
-
Prerequisite
-
Description
-
-
-
-
-
Prerequisite software
-
.Net Framework 4
-
-
-
Supported operating systems
-
-
64-bit version of Windows 10
-
64-bit version of Windows 8 or 8.1
-
64-bit version of Windows 7
-
-
-
-
-
-
->**Note** In this topic, the term “Office 2016 App-V package” refers to subscription licensing.
-
-
-### Create Office 2016 App-V Packages Using Office Deployment Tool
-
-You create Office 2016 App-V packages by using the Office Deployment Tool. The following instructions explain how to create an Office 2016 App-V package with Subscription Licensing.
-
-Create Office 2016 App-V packages on 64-bit Windows computers. Once created, the Office 2016 App-V package will run on 32-bit and 64-bit Windows 7, Windows 8.1, and Windows 10 computers.
-
-### Download the Office Deployment Tool
-
-Office 2016 App-V Packages are created using the Office Deployment Tool, which generates an Office 2016 App-V Package. The package cannot be created or modified through the App-V sequencer. To begin package creation:
-
-1. Download the [Office 2016 Deployment Tool for Click-to-Run](https://www.microsoft.com/download/details.aspx?id=49117).
-
-> **Important** You must use the Office 2016 Deployment Tool to create Office 2016 App-V Packages.
-> 2. Run the .exe file and extract its features into the desired location. To make this process easier, you can create a shared network folder where the features will be saved.
-
- Example: \\\\Server\\Office2016
-
-3. Check that a setup.exe and a configuration.xml file exist and are in the location you specified.
-
-### Download Office 2016 applications
-
-After you download the Office Deployment Tool, you can use it to get the latest Office 2016 applications. After getting the Office applications, you create the Office 2016 App-V package.
-
-The XML file that is included in the Office Deployment Tool specifies the product details, such as the languages and Office applications included.
-
-1. **Customize the sample XML configuration file:** Use the sample XML configuration file that you downloaded with the Office Deployment Tool to customize the Office applications:
-
- 1. Open the sample XML file in Notepad or your favorite text editor.
-
- 2. With the sample configuration.xml file open and ready for editing, you can specify products, languages, and the path to which you save the Office 2016 applications. The following is a basic example of the configuration.xml file:
-
- ```xml
-
-
-
-
-
-
-
-
-
-
- ```
-
- >**Note** The configuration XML is a sample XML file. The file includes lines that are commented out. You can “uncomment” these lines to customize additional settings with the file. To “uncomment” these lines, remove the "" from the end of the line.
-
- The above XML configuration file specifies that Office 2016 ProPlus 32-bit edition, including Visio ProPlus, will be downloaded in English to the \\\\server\\Office 2016, which is the location where Office applications will be saved to. Note that the Product ID of the applications will not affect the final licensing of Office. Office 2016 App-V packages with various licensing can be created from the same applications through specifying licensing in a later stage. The table below summarizes the customizable attributes and elements of XML file:
-
-
-
-
-
-
-
-
-
-
Input
-
Description
-
Example
-
-
-
-
-
Add element
-
Specifies the products and languages to include in the package.
-
N/A
-
-
-
OfficeClientEdition (attribute of Add element)
-
Specifies the edition of Office 2016 product to use: 32-bit or 64-bit. The operation fails if OfficeClientEdition is not set to a valid value.
Specifies the language supported in the applications
-
Language ID="en-us"
-
-
-
Version (attribute of Add element)
-
Optional. Specifies a build to use for the package
-
Defaults to latest advertised build (as defined in v32.CAB at the Office source).
-
16.1.2.3
-
-
-
SourcePath (attribute of Add element)
-
Specifies the location in which the applications will be saved to.
-
Sourcepath = "\Server\Office2016”
-
-
-
Channel (attribute of Add element)
-
Optional. Specifies the update channel for the product that you want to download or install.
For more information about update channels, see Overview of update channels for Microsoft 365 Apps for enterprise.
-
Channel="Deferred"
-
-
-
-
- After editing the configuration.xml file to specify the desired product, languages, and also the location which the Office 2016 applications will be saved onto, you can save the configuration file, for example, as Customconfig.xml.
-
-2. **Download the applications into the specified location:** Use an elevated command prompt and a 64 bit operating system to download the Office 2016 applications that will later be converted into an App-V package. Below is an example command with a description of details:
-
- ``` syntax
- \\server\Office2016\setup.exe /download \\server\Office2016\Customconfig.xml
- ```
-
- In the example:
-
-
-
-
-
-
-
-
-
\server\Office2016
-
is the network share location that contains the Office Deployment Tool and the custom Configuration.xml file, Customconfig.xml.
-
-
-
Setup.exe
-
is the Office Deployment Tool.
-
-
-
/download
-
downloads the Office 2016 applications that you specify in the customConfig.xml file. These bits can be later converted in an Office 2016 App-V package with Volume Licensing.
-
-
-
\server\Office2016\Customconfig.xml
-
passes the XML configuration file required to complete the download process, in this example, customconfig.xml. After using the download command, Office applications should be found in the location specified in the configuration xml file, in this example \Server\Office2016.
-
-
-
-
-
-
-### Convert the Office applications into an App-V package
-
-After you download the Office 2016 applications through the Office Deployment Tool, use the Office Deployment Tool to convert them into an Office 2016 App-V package. Complete the steps that correspond to your licensing model.
-
-**Summary of what you’ll need to do:**
-
-- Create the Office 2016 App-V packages on 64-bit Windows computers. However, the package will run on 32-bit and 64-bit Windows 7, Windows 8 or 8.1, and Windows 10 computers.
-
-- Create an Office App-V package for Subscription Licensing package by using the Office Deployment Tool, and then modify the CustomConfig.xml configuration file.
-
- The following table summarizes the values you need to enter in the CustomConfig.xml file for the licensing model you’re using. The steps in the sections that follow the table will specify the exact entries you need to make.
-
->**Note** You can use the Office Deployment Tool to create App-V packages for Microsoft 365 Apps for enterprise. Creating packages for the volume-licensed versions of Office Professional Plus or Office Standard is not supported.
-
-
-
-
-
-
-
-
-
Product ID
-
Subscription Licensing
-
-
-
-
-
Office 2016
-
O365ProPlusRetail
-
-
-
Office 2016 with Visio 2016
-
O365ProPlusRetail
-
VisioProRetail
-
-
-
Office 2016 with Visio 2016 and Project 2016
-
O365ProPlusRetail
-
VisioProRetail
-
ProjectProRetail
-
-
-
-
-
-
-**How to convert the Office applications into an App-V package**
-
-1. In Notepad, reopen the CustomConfig.xml file, and make the following changes to the file:
-
-
-
-
-
-
-
-
-
Parameter
-
What to change the value to
-
-
-
-
-
SourcePath
-
Point to the Office applications downloaded earlier.
-
-
-
ProductID
-
Specify Subscription licensing, as shown in the following example:
In this example, the following changes were made to create a package with Subscription licensing:
-
-
-
-
-
-
-
-
SourcePath
-
is the path, which was changed to point to the Office applications that were downloaded earlier.
-
-
-
Product ID
-
for Office was changed to O365ProPlusRetail.
-
-
-
Product ID
-
for Visio was changed to VisioProRetail.
-
-
-
-
-
-
ExcludeApp (optional)
-
Lets you specify Office programs that you don’t want included in the App-V package that the Office Deployment Tool creates. For example, you can exclude Access and InfoPath.
-
-
-
PACKAGEGUID (optional)
-
By default, all App-V packages created by the Office Deployment Tool share the same App-V Package ID. You can use PACKAGEGUID to specify a different package ID for each package, which allows you to publish multiple App-V packages, created by the Office Deployment Tool, and manage them by using the App-V Server.
-
An example of when to use this parameter is if you create different packages for different users. For example, you can create a package with just Office 2016 for some users, and create another package with Office 2016 and Visio 2016 for another set of users.
- >Note Even if you use unique package IDs, you can still deploy only one App-V package to a single device.
-
-
-
-
-
-
-
-2. Use the /packager command to convert the Office applications to an Office 2016 App-V package.
-
- For example:
-
- ``` syntax
- \\server\Office2016\setup.exe /packager \\server\Office2016\Customconfig.xml \\server\share\Office2016AppV
- ```
-
- In the example:
-
-
-
-
-
-
-
-
-
\server\Office2016
-
is the network share location that contains the Office Deployment Tool and the custom Configuration.xml file, Customconfig.xml.
-
-
-
Setup.exe
-
is the Office Deployment Tool.
-
-
-
/packager
-
creates the Office 2016 App-V package with the type of licensing specified in the customConfig.xml file.
-
-
-
\server\Office2016\Customconfig.xml
-
passes the configuration XML file (in this case customConfig) that has been prepared for the packaging stage.
-
-
-
\server\share\Office 2016AppV
-
specifies the location of the newly created Office App-V package.
-
-
-
-
-
-
-~~~
-After you run the **/packager** command, the following folders appear up in the directory where you specified the package should be saved:
-
-- **App-V Packages** – contains an Office 2016 App-V package and two deployment configuration files.
-
-- **WorkingDir**
-
-**Note** To troubleshoot any issues, see the log files in the %temp% directory (default).
-~~~
-
-
-
-3. Verify that the Office 2016 App-V package works correctly:
-
- 1. Publish the Office 2016 App-V package, which you created globally, to a test computer, and verify that the Office 2016 shortcuts appear.
-
- 2. Start a few Office 2016 applications, such as Excel or Word, to ensure that your package is working as expected.
-
-## Publishing the Office package for App-V
-
-
-Use the following information to publish an Office package.
-
-### Methods for publishing Office App-V packages
-
-Deploy the App-V package for Office 2016 by using the same methods you use for any other package:
-
-- System Center Configuration Manager
-
-- App-V Server
-
-- Stand-alone through PowerShell commands
-
-### Publishing prerequisites and requirements
-
-
-
-
-
-
-
-
-
Prerequisite or requirement
-
Details
-
-
-
-
-
Enable PowerShell scripting on the App-V clients
-
To publish Office 2016 packages, you must run a script.
-
Package scripts are disabled by default on App-V clients. To enable scripting, run the following PowerShell command:
Extension points in the Office App-V package require installation at the computer level.
-
When you publish at the computer level, no prerequisite actions or redistributables are needed, and the Office 2016 package globally enables its applications to work like natively installed Office, eliminating the need for administrators to customize packages.
-
-
-
-
-
-
-### How to publish an Office package
-
-Run the following command to publish an Office package globally:
-
-- `Add-AppvClientPackage | Publish-AppvClientPackage –global`
-
-- From the Web Management Console on the App-V Server, you can add permissions to a group of computers instead of to a user group to enable packages to be published globally to the computers in the corresponding group.
-
-## Customizing and managing Office App-V packages
-
-
-To manage your Office App-V packages, use the same operations as you would for any other package, but there are a few exceptions, as outlined in the following sections.
-
-- [Enabling Office plug-ins by using connection groups](#bkmk-enable-office-plugins)
-
-- [Disabling Office 2016 applications](#bkmk-disable-office-apps)
-
-- [Disabling Office 2016 shortcuts](#bkmk-disable-shortcuts)
-
-- [Managing Office 2016 package upgrades](#bkmk-manage-office-pkg-upgrd)
-
-- [Deploying Visio 2016 and Project 2016 with Office](#bkmk-deploy-visio-project)
-
-### Enabling Office plug-ins by using connection groups
-
-Use the steps in this section to enable Office plug-ins with your Office package. To use Office plug-ins, you must use the App-V Sequencer to create a separate package that contains just the plug-ins. You cannot use the Office Deployment Tool to create the plug-ins package. You then create a connection group that contains the Office package and the plug-ins package, as described in the following steps.
-
-**To enable plug-ins for Office App-V packages**
-
-1. Add a Connection Group through App-V Server, System Center Configuration Manager, or a PowerShell cmdlet.
-
-2. Sequence your plug-ins using the App-V Sequencer. Ensure that Office 2016 is installed on the computer being used to sequence the plug-in. It is recommended you use Microsoft 365 Apps for enterprise(non-virtual) on the sequencing computer when you sequence Office 2016 plug-ins.
-
-3. Create an App-V package that includes the desired plug-ins.
-
-4. Add a Connection Group through App-V server, System Center Configuration Manager, or a PowerShell cmdlet.
-
-5. Add the Office 2016 App-V package and the plug-ins package you sequenced to the Connection Group you created.
-
- >**Important** The order of the packages in the Connection Group determines the order in which the package contents are merged. In your Connection group descriptor file, add the Office 2016 App-V package first, and then add the plug-in App-V package.
-
-
-
-6. Ensure that both packages are published to the target computer and that the plug-in package is published globally to match the global settings of the published Office 2016 App-V package.
-
-7. Verify that the Deployment Configuration File of the plug-in package has the same settings that the Office 2016 App-V package has.
-
- Since the Office 2016 App-V package is integrated with the operating system, the plug-in package settings should match. You can search the Deployment Configuration File for “COM Mode” and ensure that your plug-ins package has that value set as “Integrated” and that both "InProcessEnabled" and "OutOfProcessEnabled" match the settings of the Office 2016 App-V package you published.
-
-8. Open the Deployment Configuration File and set the value for **Objects Enabled** to **false**.
-
-9. If you made any changes to the Deployment Configuration file after sequencing, ensure that the plug-in package is published with the file.
-
-10. Ensure that the Connection Group you created is enabled onto your desired computer. The Connection Group created will likely “pend” if the Office 2016 App-V package is in use when the Connection Group is enabled. If that happens, you have to reboot to successfully enable the Connection Group.
-
-11. After you successfully publish both packages and enable the Connection Group, start the target Office 2016 application and verify that the plug-in you published and added to the connection group works as expected.
-
-### Disabling Office 2016 applications
-
-You may want to disable specific applications in your Office App-V package. For instance, you can disable Access, but leave all other Office application main available. When you disable an application, the end user will no longer see the shortcut for that application. You do not have to re-sequence the application. When you change the Deployment Configuration File after the Office 2016 App-V package has been published, you will save the changes, add the Office 2016 App-V package, and then republish it with the new Deployment Configuration File to apply the new settings to Office 2016 App-V Package applications.
-
->**Note** To exclude specific Office applications (for example, Access and InfoPath) when you create the App-V package with the Office Deployment Tool, use the **ExcludeApp** setting.
-
-
-**To disable an Office 2016 application**
-
-1. Open a Deployment Configuration File with a text editor such as **Notepad** and search for “Applications."
-
-2. Search for the Office application you want to disable, for example, Access 2016.
-
-3. Change the value of "Enabled" from "true" to "false."
-
-4. Save the Deployment Configuration File.
-
-5. Add the Office 2016 App-V Package with the new Deployment Configuration File.
-
- ```xml
-
-
- Lync 2016
-
-
-
-
-
-
- Access 2016
-
-
-
-
- ```
-
-6. Re-add the Office 2016 App-V package, and then republish it with the new Deployment Configuration File to apply the new settings to Office 2016 App-V Package applications.
-
-### Disabling Office 2016 shortcuts
-
-You may want to disable shortcuts for certain Office applications instead of unpublishing or removing the package. The following example shows how to disable shortcuts for Microsoft Access.
-
-**To disable shortcuts for Office 2016 applications**
-
-1. Open a Deployment Configuration File in Notepad and search for “Shortcuts”.
-
-2. To disable certain shortcuts, delete or comment out the specific shortcuts you don’t want. You must keep the subsystem present and enabled. For example, in the example below, delete the Microsoft Access shortcuts, while keeping the subsystems <shortcut> </shortcut> intact to disable the Microsoft Access shortcut.
-
- ``` syntax
- Shortcuts
-
- -->
-
-
-
-
- [{Common Programs}]\Microsoft Office 2016\Access 2016.lnk
- [{AppvPackageRoot}])office16\MSACCESS.EXE
- [{Windows}]\Installer\{90150000-000F-0000-0000-000000FF1CE)\accicons.exe.Ø.ico
-
-
- Microsoft.Office.MSACCESS.EXE.15
- true
- Build a professional app quickly to manage data.
- l
- [{AppVPackageRoot}]\office16\MSACCESS.EXE
-
- ```
-
-3. Save the Deployment Configuration File.
-
-4. Republish Office 2016 App-V Package with new Deployment Configuration File.
-
-Many additional settings can be changed through modifying the Deployment Configuration for App-V packages, for example, file type associations, Virtual File System, and more. For additional information on how to use Deployment Configuration Files to change App-V package settings, refer to the additional resources section at the end of this document.
-
-### Managing Office 2016 package upgrades
-
-To upgrade an Office 2016 package, use the Office Deployment Tool. To upgrade a previously deployed Office 2016 package, perform the following steps.
-
-**How to upgrade a previously deployed Office 2016 package**
-
-1. Create a new Office 2016 package through the Office Deployment Tool that uses the most recent Office 2016 application software. The most recent Office 2016 bits can always be obtained through the download stage of creating an Office 2016 App-V Package. The newly created Office 2016 package will have the most recent updates and a new Version ID. All packages created using the Office Deployment Tool have the same lineage.
-
- > **Note** Office App-V packages have two Version IDs:
- >
- >
An Office 2016 App-V Package Version ID that is unique across all packages created using the Office Deployment Tool.
- >
A second App-V Package Version ID, x.x.x.x for example, in the AppX manifest that will only change if there is a new version of Office itself. For example, if a new Office 2016 release with upgrades is available, and a package is created through the Office Deployment Tool to incorporate these upgrades, the X.X.X.X version ID will change to reflect that the Office version itself has changed. The App-V server will use the X.X.X.X version ID to differentiate this package and recognize that it contains new upgrades to the previously published package, and as a result, publish it as an upgrade to the existing Office 2016 package.
- >
-
-
-2. Globally publish the newly created Office 2016 App-V Packages onto computers where you would like to apply the new updates. Since the new package has the same lineage of the older Office 2016 App-V Package, publishing the new package with the updates will only apply the new changes to the old package, and thus will be fast.
-
-3. Upgrades will be applied in the same manner of any globally published App-V Packages. Because applications will probably be in use, upgrades might be delayed until the computer is rebooted.
-
-
-### Deploying Visio 2016 and Project 2016 with Office
-
-The following table describes the requirements and options for deploying Visio 2016 and Project 2016 with Office.
-
-
-
-
-
-
-
-
-
Task
-
Details
-
-
-
-
-
How do I package and publish Visio 2016 and Project 2016 with Office?
-
You must include Visio 2016 and Project 2016 in the same package with Office.
-
If you aren’t deploying Office, you can create a package that contains Visio and/or Project, as long as you follow the packaging, publishing, and deployment requirements described in this topic.
-
-
-
How can I deploy Visio 2016 and Project 2016 to specific users?
-
Use one of the following methods:
-
-
-
-
-
-
-
-
If you want to...
-
...then use this method
-
-
-
-
-
Create two different packages and deploy each one to a different group of users
-
Create and deploy the following packages:
-
-
A package that contains only Office - deploy to computers whose users need only Office.
-
A package that contains Office, Visio, and Project - deploy to computers whose users need all three applications.
-
-
-
-
If you want only one package for the whole organization, or if you have users who share computers:
-
Follows these steps:
-
-
Create a package that contains Office, Visio, and Project.
-
Deploy the package to all users.
-
Use Microsoft AppLocker to prevent specific users from using Visio and Project.
-
-
-
-
-
-
-
-
-
-
-
-## Additional resources
-
-
-[Deploying Microsoft Office 2013 by Using App-V](deploying-microsoft-office-2013-by-using-app-v.md)
-
-[Deploying Microsoft Office 2010 by Using App-V](deploying-microsoft-office-2010-by-using-app-v.md)
-
-[Office 2016 Deployment Tool for Click-to-Run](https://www.microsoft.com/download/details.aspx?id=49117)
-
-**Connection Groups**
-
-[Deploying Connection Groups in Microsoft App-V v5](https://go.microsoft.com/fwlink/p/?LinkId=330683)
-
-[Managing Connection Groups](managing-connection-groups.md)
-
-**Dynamic Configuration**
-
-[About App-V 5.1 Dynamic Configuration](about-app-v-51-dynamic-configuration.md)
-
-
-
-
-
diff --git a/mdop/appv-v5/deploying-microsoft-office-2016-by-using-app-v51.md b/mdop/appv-v5/deploying-microsoft-office-2016-by-using-app-v51.md
deleted file mode 100644
index 6d6021c95e..0000000000
--- a/mdop/appv-v5/deploying-microsoft-office-2016-by-using-app-v51.md
+++ /dev/null
@@ -1,795 +0,0 @@
----
-title: Deploying Microsoft Office 2016 by Using App-V
-description: Deploying Microsoft Office 2016 by Using App-V
-author: dansimp
-ms.assetid: e0f4876-da99-4b89-977e-2fb6e89ea3d3
-ms.reviewer:
-manager: dansimp
-ms.author: dansimp
-ms.pagetype: mdop, appcompat, virtualization
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.prod: w10
-ms.date: 04/19/2017
----
-
-
-# Deploying Microsoft Office 2016 by Using App-V
-
-
-Use the information in this article to use Microsoft Application Virtualization (App-V) 5.1, or later versions, to deliver Microsoft Office 2016 as a virtualized application to computers in your organization. For information about using App-V to deliver Office 2013, see [Deploying Microsoft Office 2013 by Using App-V](deploying-microsoft-office-2013-by-using-app-v51.md). For information about using App-V to deliver Office 2010, see [Deploying Microsoft Office 2010 by Using App-V](deploying-microsoft-office-2010-by-using-app-v51.md).
-
-This topic contains the following sections:
-
-- [What to know before you start](#bkmk-before-you-start)
-
-- [Creating an Office 2016 package for App-V with the Office Deployment Tool](#bkmk-create-office-pkg)
-
-- [Publishing the Office package for App-V 5.1](#bkmk-pub-pkg-office)
-
-- [Customizing and managing Office App-V packages](#bkmk-custmz-manage-office-pkgs)
-
-## What to know before you start
-
-
-Before you deploy Office 2016 by using App-V, review the following planning information.
-
-### Supported Office versions and Office coexistence
-
-Use the following table to get information about supported versions of Office and about running coexisting versions of Office.
-
-
Considerations for installing different versions of Office on the same computer
-
-
-
-
-
-
-### Packaging, publishing, and deployment requirements
-
-Before you deploy Office by using App-V, review the following requirements.
-
-
-
-
-
-
-
-
-
Task
-
Requirement
-
-
-
-
-
Packaging
-
-
-
All of the Office applications that you want to deploy to users must be in a single package.
-
In App-V 5.1 and later, you must use the Office Deployment Tool to create packages. You cannot use the Sequencer.
-
If you are deploying Microsoft Visio 2016 and Microsoft Project 2016 along with Office, you must include them in the same package with Office. For more information, see Deploying Visio 2016 and Project 2016 with Office.
-
-
-
-
Publishing
-
-
You can publish only one Office package to each client computer.
-
You must publish the Office package globally. You cannot publish to the user.
-
-
-
-
Deploying any of the following products to a shared computer, for example, by using Remote Desktop Services:
-
-
-
-### Excluding Office applications from a package
-
-The following table describes the recommended methods for excluding specific Office applications from a package.
-
-
-
-
-
-
-
-
-
Task
-
Details
-
-
-
-
-
Use the ExcludeApp setting when you create the package by using the Office Deployment Tool.
-
-
Enables you to exclude specific Office applications from the package when the Office Deployment Tool creates the package. For example, you can use this setting to create a package that contains only Microsoft Word.
Modify the DeploymentConfig.xml file after the package has been created. This file contains the default package settings for all users on a computer that is running the App-V Client.
-
-
-
-## Creating an Office 2016 package for App-V with the Office Deployment Tool
-
-
-Complete the following steps to create an Office 2016 package for App-V 5.1 or later.
-
->**Important** In App-V 5.1 and later, you must use the Office Deployment Tool to create a package. You cannot use the Sequencer to create packages.
-
-### Review prerequisites for using the Office Deployment Tool
-
-The computer on which you are installing the Office Deployment Tool must have:
-
-
-
-
-
-
-
-
-
Prerequisite
-
Description
-
-
-
-
-
Prerequisite software
-
.Net Framework 4
-
-
-
Supported operating systems
-
-
64-bit version of Windows 10
-
64-bit version of Windows 8 or 8.1
-
64-bit version of Windows 7
-
-
-
-
-
-
->**Note** In this topic, the term “Office 2016 App-V package” refers to subscription licensing.
-
-
-### Create Office 2016 App-V Packages Using Office Deployment Tool
-
-You create Office 2016 App-V packages by using the Office Deployment Tool. The following instructions explain how to create an Office 2016 App-V package with Subscription Licensing.
-
-Create Office 2016 App-V packages on 64-bit Windows computers. Once created, the Office 2016 App-V package will run on 32-bit and 64-bit Windows 7, Windows 8.1, and Windows 10 computers.
-
-### Download the Office Deployment Tool
-
-Office 2016 App-V Packages are created using the Office Deployment Tool, which generates an Office 2016 App-V Package. The package cannot be created or modified through the App-V sequencer. To begin package creation:
-
-1. Download the [Office 2016 Deployment Tool for Click-to-Run](https://www.microsoft.com/download/details.aspx?id=49117).
-
-> **Important** You must use the Office 2016 Deployment Tool to create Office 2016 App-V Packages.
-> 2. Run the .exe file and extract its features into the desired location. To make this process easier, you can create a shared network folder where the features will be saved.
-
- Example: \\\\Server\\Office2016
-
-3. Check that a setup.exe and a configuration.xml file exist and are in the location you specified.
-
-### Download Office 2016 applications
-
-After you download the Office Deployment Tool, you can use it to get the latest Office 2016 applications. After getting the Office applications, you create the Office 2016 App-V package.
-
-The XML file that is included in the Office Deployment Tool specifies the product details, such as the languages and Office applications included.
-
-1. **Customize the sample XML configuration file:** Use the sample XML configuration file that you downloaded with the Office Deployment Tool to customize the Office applications:
-
- 1. Open the sample XML file in Notepad or your favorite text editor.
-
- 2. With the sample configuration.xml file open and ready for editing, you can specify products, languages, and the path to which you save the Office 2016 applications. The following is a basic example of the configuration.xml file:
-
- ```xml
-
-
-
-
-
-
-
-
-
-
- ```
-
- >**Note** The configuration XML is a sample XML file. The file includes lines that are commented out. You can “uncomment” these lines to customize additional settings with the file. To “uncomment” these lines, remove the "" from the end of the line.
-
- The above XML configuration file specifies that Office 2016 ProPlus 32-bit edition, including Visio ProPlus, will be downloaded in English to the \\\\server\\Office 2016, which is the location where Office applications will be saved to. Note that the Product ID of the applications will not affect the final licensing of Office. Office 2016 App-V packages with various licensing can be created from the same applications through specifying licensing in a later stage. The table below summarizes the customizable attributes and elements of XML file:
-
-
-
-
-
-
-
-
-
-
Input
-
Description
-
Example
-
-
-
-
-
Add element
-
Specifies the products and languages to include in the package.
-
N/A
-
-
-
OfficeClientEdition (attribute of Add element)
-
Specifies the edition of Office 2016 product to use: 32-bit or 64-bit. The operation fails if OfficeClientEdition is not set to a valid value.
Specifies the language supported in the applications
-
Language ID="en-us"
-
-
-
Version (attribute of Add element)
-
Optional. Specifies a build to use for the package
-
Defaults to latest advertised build (as defined in v32.CAB at the Office source).
-
16.1.2.3
-
-
-
SourcePath (attribute of Add element)
-
Specifies the location in which the applications will be saved to.
-
Sourcepath = "\Server\Office2016”
-
-
-
Branch (attribute of Add element)
-
Optional. Specifies the update branch for the product that you want to download or install.
For more information about update branches, see Overview of update branches for Microsoft 365 Apps for enterprise.
-
Branch = "Business"
-
-
-
-
- After editing the configuration.xml file to specify the desired product, languages, and also the location which the Office 2016 applications will be saved onto, you can save the configuration file, for example, as Customconfig.xml.
-
-2. **Download the applications into the specified location:** Use an elevated command prompt and a 64 bit operating system to download the Office 2016 applications that will later be converted into an App-V package. Below is an example command with a description of details:
-
- ``` syntax
- \\server\Office2016\setup.exe /download \\server\Office2016\Customconfig.xml
- ```
-
- In the example:
-
-
-
-
-
-
-
-
-
\server\Office2016
-
is the network share location that contains the Office Deployment Tool and the custom Configuration.xml file, Customconfig.xml.
-
-
-
Setup.exe
-
is the Office Deployment Tool.
-
-
-
/download
-
downloads the Office 2016 applications that you specify in the customConfig.xml file. These bits can be later converted in an Office 2016 App-V package with Volume Licensing.
-
-
-
\server\Office2016\Customconfig.xml
-
passes the XML configuration file required to complete the download process, in this example, customconfig.xml. After using the download command, Office applications should be found in the location specified in the configuration xml file, in this example \Server\Office2016.
-
-
-
-
-
-
-### Convert the Office applications into an App-V package
-
-After you download the Office 2016 applications through the Office Deployment Tool, use the Office Deployment Tool to convert them into an Office 2016 App-V package. Complete the steps that correspond to your licensing model.
-
-**Summary of what you’ll need to do:**
-
-- Create the Office 2016 App-V packages on 64-bit Windows computers. However, the package will run on 32-bit and 64-bit Windows 7, Windows 8 or 8.1, and Windows 10 computers.
-
-- Create an Office App-V package for Subscription Licensing package by using the Office Deployment Tool, and then modify the CustomConfig.xml configuration file.
-
- The following table summarizes the values you need to enter in the CustomConfig.xml file for the licensing model you’re using. The steps in the sections that follow the table will specify the exact entries you need to make.
-
->**Note** You can use the Office Deployment Tool to create App-V packages for Microsoft 365 Apps for enterprise. Creating packages for the volume-licensed versions of Office Professional Plus or Office Standard is not supported.
-
-
-
-
-
-
-
-
-
Product ID
-
Subscription Licensing
-
-
-
-
-
Office 2016
-
O365ProPlusRetail
-
-
-
Office 2016 with Visio 2016
-
O365ProPlusRetail
-
VisioProRetail
-
-
-
Office 2016 with Visio 2016 and Project 2016
-
O365ProPlusRetail
-
VisioProRetail
-
ProjectProRetail
-
-
-
-
-
-
-**How to convert the Office applications into an App-V package**
-
-1. In Notepad, reopen the CustomConfig.xml file, and make the following changes to the file:
-
-
-
-
-
-
-
-
-
Parameter
-
What to change the value to
-
-
-
-
-
SourcePath
-
Point to the Office applications downloaded earlier.
-
-
-
ProductID
-
Specify Subscription licensing, as shown in the following example:
In this example, the following changes were made to create a package with Subscription licensing:
-
-
-
-
-
-
-
-
SourcePath
-
is the path, which was changed to point to the Office applications that were downloaded earlier.
-
-
-
Product ID
-
for Office was changed to O365ProPlusRetail.
-
-
-
Product ID
-
for Visio was changed to VisioProRetail.
-
-
-
-
-
-
ExcludeApp (optional)
-
Lets you specify Office programs that you don’t want included in the App-V package that the Office Deployment Tool creates. For example, you can exclude Access and InfoPath.
-
-
-
PACKAGEGUID (optional)
-
By default, all App-V packages created by the Office Deployment Tool share the same App-V Package ID. You can use PACKAGEGUID to specify a different package ID for each package, which allows you to publish multiple App-V packages, created by the Office Deployment Tool, and manage them by using the App-V Server.
-
An example of when to use this parameter is if you create different packages for different users. For example, you can create a package with just Office 2016 for some users, and create another package with Office 2016 and Visio 2016 for another set of users.
-
- >Note Even if you use unique package IDs, you can still deploy only one App-V package to a single device.
-
-
-
-
-
-
-2. Use the /packager command to convert the Office applications to an Office 2016 App-V package.
-
- For example:
-
- ``` syntax
- \\server\Office2016\setup.exe /packager \\server\Office2016\Customconfig.xml \\server\share\Office2016AppV
- ```
-
- In the example:
-
-
-
-
-
-
-
-
-
\server\Office2016
-
is the network share location that contains the Office Deployment Tool and the custom Configuration.xml file, Customconfig.xml.
-
-
-
Setup.exe
-
is the Office Deployment Tool.
-
-
-
/packager
-
creates the Office 2016 App-V package with the type of licensing specified in the customConfig.xml file.
-
-
-
\server\Office2016\Customconfig.xml
-
passes the configuration XML file (in this case customConfig) that has been prepared for the packaging stage.
-
-
-
\server\share\Office 2016AppV
-
specifies the location of the newly created Office App-V package.
-
-
-
-
-
-
-~~~
-After you run the **/packager** command, the following folders appear up in the directory where you specified the package should be saved:
-
-- **App-V Packages** – contains an Office 2016 App-V package and two deployment configuration files.
-
-- **WorkingDir**
-
-**Note** To troubleshoot any issues, see the log files in the %temp% directory (default).
-~~~
-
-
-
-3. Verify that the Office 2016 App-V package works correctly:
-
- 1. Publish the Office 2016 App-V package, which you created globally, to a test computer, and verify that the Office 2016 shortcuts appear.
-
- 2. Start a few Office 2016 applications, such as Excel or Word, to ensure that your package is working as expected.
-
-## Publishing the Office package for App-V
-
-
-Use the following information to publish an Office package.
-
-### Methods for publishing Office App-V packages
-
-Deploy the App-V package for Office 2016 by using the same methods you use for any other package:
-
-- System Center Configuration Manager
-
-- App-V Server
-
-- Stand-alone through PowerShell commands
-
-### Publishing prerequisites and requirements
-
-
-
-
-
-
-
-
-
Prerequisite or requirement
-
Details
-
-
-
-
-
Enable PowerShell scripting on the App-V clients
-
To publish Office 2016 packages, you must run a script.
-
Package scripts are disabled by default on App-V clients. To enable scripting, run the following PowerShell command:
Extension points in the Office App-V package require installation at the computer level.
-
When you publish at the computer level, no prerequisite actions or redistributables are needed, and the Office 2016 package globally enables its applications to work like natively installed Office, eliminating the need for administrators to customize packages.
-
-
-
-
-
-
-### How to publish an Office package
-
-Run the following command to publish an Office package globally:
-
-- `Add-AppvClientPackage | Publish-AppvClientPackage –global`
-
-- From the Web Management Console on the App-V Server, you can add permissions to a group of computers instead of to a user group to enable packages to be published globally to the computers in the corresponding group.
-
-## Customizing and managing Office App-V packages
-
-
-To manage your Office App-V packages, use the same operations as you would for any other package, but there are a few exceptions, as outlined in the following sections.
-
-- [Enabling Office plug-ins by using connection groups](#bkmk-enable-office-plugins)
-
-- [Disabling Office 2016 applications](#bkmk-disable-office-apps)
-
-- [Disabling Office 2016 shortcuts](#bkmk-disable-shortcuts)
-
-- [Managing Office 2016 package upgrades](#bkmk-manage-office-pkg-upgrd)
-
-- [Deploying Visio 2016 and Project 2016 with Office](#bkmk-deploy-visio-project)
-
-### Enabling Office plug-ins by using connection groups
-
-Use the steps in this section to enable Office plug-ins with your Office package. To use Office plug-ins, you must use the App-V Sequencer to create a separate package that contains just the plug-ins. You cannot use the Office Deployment Tool to create the plug-ins package. You then create a connection group that contains the Office package and the plug-ins package, as described in the following steps.
-
-**To enable plug-ins for Office App-V packages**
-
-1. Add a Connection Group through App-V Server, System Center Configuration Manager, or a PowerShell cmdlet.
-
-2. Sequence your plug-ins using the App-V Sequencer. Ensure that Office 2016 is installed on the computer being used to sequence the plug-in. It is recommended you use Microsoft 365 Apps for enterprise(non-virtual) on the sequencing computer when you sequence Office 2016 plug-ins.
-
-3. Create an App-V package that includes the desired plug-ins.
-
-4. Add a Connection Group through App-V server, System Center Configuration Manager, or a PowerShell cmdlet.
-
-5. Add the Office 2016 App-V package and the plug-ins package you sequenced to the Connection Group you created.
-
- >**Important** The order of the packages in the Connection Group determines the order in which the package contents are merged. In your Connection group descriptor file, add the Office 2016 App-V package first, and then add the plug-in App-V package.
-
-
-
-6. Ensure that both packages are published to the target computer and that the plug-in package is published globally to match the global settings of the published Office 2016 App-V package.
-
-7. Verify that the Deployment Configuration File of the plug-in package has the same settings that the Office 2016 App-V package has.
-
- Since the Office 2016 App-V package is integrated with the operating system, the plug-in package settings should match. You can search the Deployment Configuration File for “COM Mode” and ensure that your plug-ins package has that value set as “Integrated” and that both "InProcessEnabled" and "OutOfProcessEnabled" match the settings of the Office 2016 App-V package you published.
-
-8. Open the Deployment Configuration File and set the value for **Objects Enabled** to **false**.
-
-9. If you made any changes to the Deployment Configuration file after sequencing, ensure that the plug-in package is published with the file.
-
-10. Ensure that the Connection Group you created is enabled onto your desired computer. The Connection Group created will likely “pend” if the Office 2016 App-V package is in use when the Connection Group is enabled. If that happens, you have to reboot to successfully enable the Connection Group.
-
-11. After you successfully publish both packages and enable the Connection Group, start the target Office 2016 application and verify that the plug-in you published and added to the connection group works as expected.
-
-### Disabling Office 2016 applications
-
-You may want to disable specific applications in your Office App-V package. For instance, you can disable Access, but leave all other Office application main available. When you disable an application, the end user will no longer see the shortcut for that application. You do not have to re-sequence the application. When you change the Deployment Configuration File after the Office 2016 App-V package has been published, you will save the changes, add the Office 2016 App-V package, and then republish it with the new Deployment Configuration File to apply the new settings to Office 2016 App-V Package applications.
-
->**Note** To exclude specific Office applications (for example, Access and InfoPath) when you create the App-V package with the Office Deployment Tool, use the **ExcludeApp** setting.
-
-
-**To disable an Office 2016 application**
-
-1. Open a Deployment Configuration File with a text editor such as **Notepad** and search for “Applications."
-
-2. Search for the Office application you want to disable, for example, Access 2016.
-
-3. Change the value of "Enabled" from "true" to "false."
-
-4. Save the Deployment Configuration File.
-
-5. Add the Office 2016 App-V Package with the new Deployment Configuration File.
-
- ```xml
-
-
- Lync 2016
-
-
-
-
-
-
- Access 2016
-
-
-
-
- ```
-
-6. Re-add the Office 2016 App-V package, and then republish it with the new Deployment Configuration File to apply the new settings to Office 2016 App-V Package applications.
-
-### Disabling Office 2016 shortcuts
-
-You may want to disable shortcuts for certain Office applications instead of unpublishing or removing the package. The following example shows how to disable shortcuts for Microsoft Access.
-
-**To disable shortcuts for Office 2016 applications**
-
-1. Open a Deployment Configuration File in Notepad and search for “Shortcuts”.
-
-2. To disable certain shortcuts, delete or comment out the specific shortcuts you don’t want. You must keep the subsystem present and enabled. For example, in the example below, delete the Microsoft Access shortcuts, while keeping the subsystems <shortcut> </shortcut> intact to disable the Microsoft Access shortcut.
-
- ``` syntax
- Shortcuts
-
- -->
-
-
-
-
- [{Common Programs}]\Microsoft Office 2016\Access 2016.lnk
- [{AppvPackageRoot}])office16\MSACCESS.EXE
- [{Windows}]\Installer\{90150000-000F-0000-0000-000000FF1CE)\accicons.exe.Ø.ico
-
-
- Microsoft.Office.MSACCESS.EXE.15
- true
- Build a professional app quickly to manage data.
- l
- [{AppVPackageRoot}]\office16\MSACCESS.EXE
-
- ```
-
-3. Save the Deployment Configuration File.
-
-4. Republish Office 2016 App-V Package with new Deployment Configuration File.
-
-Many additional settings can be changed through modifying the Deployment Configuration for App-V packages, for example, file type associations, Virtual File System, and more. For additional information on how to use Deployment Configuration Files to change App-V package settings, refer to the additional resources section at the end of this document.
-
-### Managing Office 2016 package upgrades
-
-To upgrade an Office 2016 package, use the Office Deployment Tool. To upgrade a previously deployed Office 2016 package, perform the following steps.
-
-**How to upgrade a previously deployed Office 2016 package**
-
-1. Create a new Office 2016 package through the Office Deployment Tool that uses the most recent Office 2016 application software. The most recent Office 2016 bits can always be obtained through the download stage of creating an Office 2016 App-V Package. The newly created Office 2016 package will have the most recent updates and a new Version ID. All packages created using the Office Deployment Tool have the same lineage.
-
- > **Note** Office App-V packages have two Version IDs:
- >
- >
An Office 2016 App-V Package Version ID that is unique across all packages created using the Office Deployment Tool.
- >
A second App-V Package Version ID, x.x.x.x for example, in the AppX manifest that will only change if there is a new version of Office itself. For example, if a new Office 2016 release with upgrades is available, and a package is created through the Office Deployment Tool to incorporate these upgrades, the X.X.X.X version ID will change to reflect that the Office version itself has changed. The App-V server will use the X.X.X.X version ID to differentiate this package and recognize that it contains new upgrades to the previously published package, and as a result, publish it as an upgrade to the existing Office 2016 package.
- >
-
-
-2. Globally publish the newly created Office 2016 App-V Packages onto computers where you would like to apply the new updates. Since the new package has the same lineage of the older Office 2016 App-V Package, publishing the new package with the updates will only apply the new changes to the old package, and thus will be fast.
-
-3. Upgrades will be applied in the same manner of any globally published App-V Packages. Because applications will probably be in use, upgrades might be delayed until the computer is rebooted.
-
-
-### Deploying Visio 2016 and Project 2016 with Office
-
-The following table describes the requirements and options for deploying Visio 2016 and Project 2016 with Office.
-
-
-
-
-
-
-
-
-
Task
-
Details
-
-
-
-
-
How do I package and publish Visio 2016 and Project 2016 with Office?
-
You must include Visio 2016 and Project 2016 in the same package with Office.
-
If you aren’t deploying Office, you can create a package that contains Visio and/or Project, as long as you follow the packaging, publishing, and deployment requirements described in this topic.
-
-
-
How can I deploy Visio 2016 and Project 2016 to specific users?
-
Use one of the following methods:
-
-
-
-
-
-
-
-
If you want to...
-
...then use this method
-
-
-
-
-
Create two different packages and deploy each one to a different group of users
Browse to and select the enterprise license file to upgrade the HoloLens edition.You can also toggle Yes or No to hide parts of the first experience.To set up the device without the need to connect to a Wi-Fi network, toggle Skip Wi-Fi setup to On.Select a region and timezone in which the device will be used. 
In this section, you can enter the details of the Wi-Fi wireless network that the device should automatically connect to. To do this, select On, enter the SSID, the network type (Open or WPA2-Personal), and (if WPA2-Personal) the password for the wireless network.
You can enroll the device in Azure Active Directory, or create a local account on the deviceBefore you use a Windows Configuration Designer wizard to configure bulk Azure AD enrollment, 
To provision the device with a certificate, click Add a certificate. Enter a name for the certificate, and then browse to and select the certificate to be used.
Toggle Yes or No to enable Developer Mode on the HoloLens. 
Do not set a password to protect your provisioning package. If the provisioning package is protected by a password, provisioning the HoloLens device will fail.
Toggle Yes or No for proxy settings. The default configuration for Surface Hub is to automatically detect proxy settings, so you can select No if that is the setting that you want. However, if your infrastructure previously required using a proxy server and has changed to not require a proxy server, you can use a provisioning package to revert your Surface Hub devices to the default settings by selecting Yes and Automatically detect settings. If you toggle Yes, you can select to automatically detect proxy settings, or you can manually configure the settings by entering a URL to a setup script, or a static proxy server address. You can also identify whether to use the proxy server for local addresses, and enter exceptions (addresses that Surface Hub should connect to directly without using the proxy server). 
You can enroll the device in Active Directory and specify a security group to use the Settings app, enroll in Azure Active Directory to allow global admins to use the Settings app, or create a local administrator account on the device.To enroll the device in Active Directory, enter the credentials for a least-privileged user account to join the device to the domain, and specify the security group to have admin credentials on Surface Hub. If a provisioning package that enrolls a device in Active Directory is going to be applied to a Surface Hub that was reset, the same domain account can only be used if the account listed is a domain administrator or is the same account that set up the Surface Hub initially. Otherwise, a different domain account must be used in the provisioning package.Before you use a Windows Configuration Designer wizard to configure bulk Azure AD enrollment, 
Toggle Yes or No for enrollment in MDM. If you toggle Yes, you must provide a service account and password or certificate thumbprint that is authorized to enroll the device, and also specify the authentication type. If required by your MDM provider, also enter the URLs for the discovery service, enrollment service, and policy service. 
You can install multiple Universal Windows Platform (UWP) apps in a provisioning package. For help with the settings, see 
You don't configure any settings in this step. It provides instructions for including a configuration file that contains a list of device accounts. The configuration file must not contain column headers. When you apply the provisioning package to Surface Hub, if a Surface Hub configuration file is included on the USB drive, you can select the account and friendly name for the device from the file. See 
Uncontrolled: Not managed by AGPM.
Checked In: Available for authorized Editors to check out for editing or for a Group Policy administrator to deploy.
Checked Out: Currently being edited. Unavailable for other Editors to check out until the Editor who checked it out or an AGPM Administrator checks it in.
Pending: Awaiting approval from a Group Policy administrator before being created, controlled, deployed, or deleted.
Template: A static version of a GPO for use as a starting point when creating new GPOs.
Template (default): By default, this template is the starting point used when creating a new GPO.
Created: Identifies the date and time of the initial creation of the GPO.
Labeled: Identifies a labeled version of the GPO.