Flatten the Policy Manager doc structure

docs/endpointpolicymanager/browser-router/_category_.json

@@ -0,0 +1,6 @@
+{
+  "label": "Browser Router",
+  "position": 30,
+  "collapsed": true,
+  "collapsible": true
+}

docs/endpointpolicymanager/browser-router/manual/_category_.json

@@ -0,0 +1,10 @@
+{
+  "label": "Manual",
+  "position": 10,
+  "collapsed": true,
+  "collapsible": true,
+  "link": {
+    "type": "doc",
+    "id": "overview"
+  }
+}

docs/endpointpolicymanager/browser-router/manual/block.md

@@ -0,0 +1,31 @@
+---
+title: "Using Block Policies"
+description: "Using Block Policies"
+sidebar_position: 40
+---
+
+# Using Block Policies
+
+You can block specific websites by making a rule and selecting the **Block** website type. You can
+choose to provide **Block Text**, which will appear in a pop-up for the user, explaining why they
+cannot visit the website.
+
+:::note
+For an overview of using Block policies, see the following video:
+[Block web sites from opening in all browsers.](/docs/endpointpolicymanager/knowledgebase/browserrouter/videolearningcenter/gettingstarted/blockwebsites.md)
+:::
+
+
+![about_policypak_browser_router_16](assets/policy/about_endpointpolicymanager_browser_router_16.webp)
+
+When you include text in the **Block Text** field, the endpoint will react in all browsers with a
+pop-up like this one.
+
+![about_policypak_browser_router_17](assets/policy/about_endpointpolicymanager_browser_router_17.webp)
+
+:::note
+If you leave the **Block Text** field empty, default text is automatically provided.
+:::
+
+
+![about_policypak_browser_router_18](assets/policy/about_endpointpolicymanager_browser_router_18.webp)

docs/endpointpolicymanager/browser-router/manual/commandlinearguments.md

@@ -0,0 +1,37 @@
+---
+title: "Using Command Line Arguments"
+description: "Using Command Line Arguments"
+sidebar_position: 60
+---
+
+# Using Command Line Arguments
+
+This feature enables you to create a route in situations where you start off in the wrong browser
+and want to open up the right browser, with specific options such as  `-incognito` for Chrome and
+`-private-window` for Firefox, or launch a custom App-V virtualized Internet Explorer plugin like
+this one:
+
+```
+-noframemerging /appwe:76d7f387-c5c4-44a9-8982-cca6124a6aec. 
+```
+
+Below is an example of launching www.abc.com in Chrome's incognito mode.
+
+![about_policypak_browser_router_21](assets/about_endpointpolicymanager_browser_router_21.webp)
+
+Note how you must specifically include **%url%** to specify where the URL will reside on the command
+line. Just selecting **incognito** by itself is not enough. The **%url%** will populate the correct
+URL, and it is up to you to place it correctly within the command line arguments structure, based on
+your needs.
+
+Another use for the **Custom** policy that utilizes command line arguments might be if you want to
+launch a specific non-browser application instead of launching an actual browser. For example, one
+use might be to launch a Remote Desktop Protocol (RDP) session that calls a remote program, which
+would usually be a browser on the RDP machine.
+
+To do this, select **Custom** for the browser type. Then set the **Command Line Arguments** field to
+**Yes**. Finally, in the **Custom Browser Path** and **Command Line Arguments** field, specify the
+application you want to launch (as in, MSTSC) and the command line arguments to pass (as in,
+`c:\temp\file1.rdp /v:server1 8080`).
+
+![about_policypak_browser_router_22](assets/about_endpointpolicymanager_browser_router_22.webp)

docs/endpointpolicymanager/browser-router/manual/custom.md

@@ -0,0 +1,34 @@
+---
+title: "Using Custom Policies"
+description: "Using Custom Policies"
+sidebar_position: 50
+---
+
+# Using Custom Policies
+
+Custom policies are useful in a variety of situations. The most common situation concerns a user who
+wants to route a website to a browser that isn't Internet Explorer, Edge, Chrome, or Firefox. For
+instance, Opera and Vivaldi are two browsers you may have installed on endpoints that you want to
+route to.
+
+:::note
+For an overview of using custom policies, see the following video:
+[Browser Router with Custom Browsers](/docs/endpointpolicymanager/knowledgebase/browserrouter/videolearningcenter/citrixvirtualapps/custombrowsers.md).
+:::
+
+
+You might also want to route websites to virtualized browsers. In this example you can see a
+virtualized Firefox. To route to virtualized browsers, simply take the icon's launch target and copy
+it.
+
+![about_policypak_browser_router_19](assets/policy/about_endpointpolicymanager_browser_router_19.webp)
+
+Then, using Endpoint Policy Manager Browser Router, make a custom route and paste the target path
+into the **Custom Browser Path** field.
+
+![about_policypak_browser_router_20](assets/policy/about_endpointpolicymanager_browser_router_20.webp)
+
+This technique works for most virtualized browsers such as Microsoft App-V, VMware ThinApp, etc.
+Note that once a virtualized browser is opened, Endpoint Policy Manager Browser Router cannot route
+away from those browsers and then back to real browsers. This is because Endpoint Policy Manager
+Browser Router's helper extensions are not installed in the virtualized browser.

docs/endpointpolicymanager/browser-router/manual/exportcollections.md

@@ -0,0 +1,31 @@
+---
+title: "Exporting Collections"
+description: "Exporting Collections"
+sidebar_position: 120
+---
+
+# Exporting Collections
+
+Advanced Concepts explains how to use the Endpoint Policy Manager Exporter to wrap up any Endpoint
+Policy Manager directives and deliver them using Microsoft Endpoint Manager (SCCM and Intune), KACE,
+your own MDM service, or Endpoint Policy Manager Cloud.
+
+To export a policy for later use using Endpoint Policy Manager Exporter or Endpoint Policy Manager
+Cloud, follow thee steps:
+
+![about_policypak_browser_router_47](assets/about_endpointpolicymanager_browser_router_47.webp)
+
+**Step 1 –** Right-click the collection or the policy and select **Export to XML**. This enables you
+to save an XML file for later use.
+
+![about_policypak_browser_router_48](assets/about_endpointpolicymanager_browser_router_48.webp)
+
+Choose a policy and select Export to XML.
+
+:::note
+Exported collections or policies maintain any Item-Level Targeting that is set. Endpoint
+Policy Manager Browser Router policies are always contained within collections, even if you export
+one single policy. In other words, a collection is automatically created at the time of export if
+you export a single policy.
+
+:::

docs/endpointpolicymanager/browser-router/manual/internetexplorer/_category_.json

@@ -0,0 +1,10 @@
+{
+  "label": "Understanding Browser Router and Internet Explorer",
+  "position": 80,
+  "collapsed": true,
+  "collapsible": true,
+  "link": {
+    "type": "doc",
+    "id": "overview"
+  }
+}

docs/endpointpolicymanager/browser-router/manual/internetexplorer/convertxmls.md

@@ -0,0 +1,43 @@
+---
+title: "Converting Existing IE Site List XMLs"
+description: "Converting Existing IE Site List XMLs"
+sidebar_position: 20
+---
+
+# Converting Existing IE Site List XMLs
+
+:::note
+To get an overview on how to convert existing IE site lists, please see:
+[Internet Explorer to Endpoint Policy Manager Browser Router Site lists](/docs/endpointpolicymanager/knowledgebase/browserrouter/videolearningcenter/tipsandtricks/iesitelists.md).
+:::
+
+
+Now let's see how you can take a Microsoft Enterprise Mode Internet Explorer site list and quickly
+convert it to be used in Endpoint Policy Manager Browser Router. This saves you the time and trouble
+of converting all of the list information by hand.
+
+First, you need an Enterprise Mode site list. If you don't have an existing site list already,
+Microsoft has a tool you can use to create these lists that you can download at:
+[https://www.microsoft.com/en-us/download/details.aspx?id=49974](https://www.microsoft.com/en-us/download/details.aspx?id=49974).
+Simply run the tool and add the sites along with their necessary parameters as is shown below.
+
+![about_policypak_browser_router_31](assets/internetexplorer/about_endpointpolicymanager_browser_router_31.webp)
+
+When this is complete, save the list as an XML file. Once you have a list, create a **From
+Enterprise Mode Site List** rule using Endpoint Policy Manager Browser Router.
+
+![about_policypak_browser_router_32](assets/internetexplorer/about_endpointpolicymanager_browser_router_32.webp)
+
+You will then be prompted to point to the created list. Once selected, a pop-up will confirm the
+number of rules being imported. You can choose to import the rules into the existing collection or a
+new collection.
+
+![about_policypak_browser_router_33](assets/internetexplorer/about_endpointpolicymanager_browser_router_33.webp)
+
+The imported rules now appear.
+
+![about_policypak_browser_router_34](assets/internetexplorer/about_endpointpolicymanager_browser_router_34.webp)
+
+You can review any of the rules to confirm or change their settings.
+
+![about_policypak_browser_router_35](assets/internetexplorer/about_endpointpolicymanager_browser_router_35.webp)

docs/endpointpolicymanager/browser-router/manual/internetexplorer/edgemod.md

@@ -0,0 +1,107 @@
+---
+title: "Internet Explorer in Edge Mode"
+description: "Internet Explorer in Edge Mode"
+sidebar_position: 10
+---
+
+## Internet Explorer in Edge Mode
+
+:::note
+To get an overview of Endpoint Policy Manager Browser Router and Internet Explorer in Edge
+Mode, please see:
+[Endpoint Policy Manager Browser Router: Internet Explorer in Edge mode](/docs/endpointpolicymanager/knowledgebase/browserrouter/videolearningcenter/tipsandtricks/ieedgemode.md).
+:::
+
+
+If you want to stay with a Microsoft browser, you want your user to use Edge rather than IE. But
+some intranet sites don't support Edge, so you are forced to use IE. However, instead of forcing
+users to open a dedicated IE session for these sites, you can use Endpoint Policy Manager Browser
+Router to enforce IE in Edge for any site of your choosing. In other words, it tucks IE tabs into
+the Edge browser.
+
+:::warning
+Be aware that this is only guaranteed to work in the 2004 version of Windows 10,
+however, it might work in versions 1909, 1903, and 1809.
+:::
+
+
+Create a rule for
+[www.endpointpolicymanager.com](http://www.endpointpolicymanager.com/video/endpointpolicymanager-browser-router-and-ports.html) and
+assign it to IE. This time select **Open as IE in Edge tab** .
+
+![about_policypak_browser_router_29](assets/internetexplorer/about_endpointpolicymanager_browser_router_29.webp)
+
+When the user logs on and tries to access [www.endpointpolicymanager.com](http://www.endpointpolicymanager.com/) they should
+see it open as an IE tab in Edge. We say should because the rule will not work right away. There is
+a detail called the 65 second rule, which you can read more about here
+[https://docs.microsoft.com/en-us/microsoft-edge/deploy/emie-to-improve-compatibility](http://www.endpointpolicymanager.com/video/endpointpolicymanager-troubleshooting-with-admx-files.html).
+From the first time a user accesses
+[www.endpointpolicymanager.com](http://www.endpointpolicymanager.com/knowledge-base/browser-router-troubleshooting/how-to-quickly-troubleshoot-endpointpolicymanager-browser-router.html),
+a period of 65 seconds or so has to transpire until the rule comes fully into effect. Here you can
+see that the Endpoint Policy Manager website now appears in IE mode within the Edge browser itself:
+
+![about_policypak_browser_router_30](assets/internetexplorer/about_endpointpolicymanager_browser_router_30.webp)
+
+### Converting Existing IE Site List XMLs
+
+:::note
+To get an overview on how to convert existing IE site lists, please see
+[Internet Explorer to Endpoint Policy Manager Browser Router Site lists](/docs/endpointpolicymanager/knowledgebase/browserrouter/videolearningcenter/tipsandtricks/iesitelists.md).
+:::
+
+
+See how you can take a Microsoft Enterprise Mode Internet Explorer site list and quickly convert it
+to be used in Endpoint Policy Manager Browser Router. This saves you the time and trouble of
+converting all of the list information by hand.
+
+First, you need an Enterprise Mode site list. If you don't have an existing site list already,
+Microsoft has a tool you can use to create these lists that you can download at
+[https://www.microsoft.com/en-us/download/details.aspx?id=49974](https://www.microsoft.com/en-us/download/details.aspx?id=49974).
+Simply run the tool and add the sites along with their necessary parameters.
+
+![about_policypak_browser_router_31](assets/internetexplorer/about_endpointpolicymanager_browser_router_31.webp)
+
+When this is complete, save the list as an XML file. Once you have a list, create a **From
+Enterprise Mode Site List** rule using Endpoint Policy Manager Browser Router.
+
+![about_policypak_browser_router_32](assets/internetexplorer/about_endpointpolicymanager_browser_router_32.webp)
+
+You are then prompted to point to the created list. Once selected, a pop-up confirms the number of
+rules being imported. You can choose to import the rules into the existing collection or a new
+collection.
+
+![about_policypak_browser_router_33](assets/internetexplorer/about_endpointpolicymanager_browser_router_33.webp)
+
+The imported rules now appear.
+
+![about_policypak_browser_router_34](assets/internetexplorer/about_endpointpolicymanager_browser_router_34.webp)
+
+You can review any of the rules to confirm or change their settings.
+
+![about_policypak_browser_router_35](assets/internetexplorer/about_endpointpolicymanager_browser_router_35.webp)
+
+### Using Special Policy Types for Internet Explorer
+
+There are two special policies that may be used only once per collection . These policies manage how
+the Windows 10 Edge browser functions alongside Internet Explorer 11.
+
+:::note
+To get an overview of Endpoint Policy Manager Browser Router's special policies for
+Microsoft Edge, please see
+[Endpoint Policy Manager and Edge ‘Special' policies](/docs/endpointpolicymanager/knowledgebase/browserrouter/videolearningcenter/gettingstarted/edgespecial.md).
+:::
+
+
+The policies are **All intranet to IE** policy and **All Enterprise from Edge to I**E policy.
+
+![about_policypak_browser_router_36](assets/internetexplorer/about_endpointpolicymanager_browser_router_36.webp)
+
+The **All intranet to IE** policy will take all websites that are already defined in the Intranet
+zone and ensure that those sites open in Internet Explorer 11 whenever the user tries to use
+Microsoft Edge. In other words, once this policy is applied, if a user opens an Intranet site using
+Edge, it is automatically routed to Internet Explorer 11.
+
+All Enterprise from Edge to IE policy will take all websites that are already defined in the IE
+Enterprise site list and route them to Internet Explorer. In other words, once this policy is
+applied, if a user opens any website within Edge that you've set to Enterprise Mode, it is
+automatically routed to Internet Explorer 11.