all docs building successfully

Author: jtviolet

.cursor/rules/mdx-stuff.mdc

@@ -0,0 +1,12 @@
+---
+description: 
+globs: 
+alwaysApply: true
+---
+When asked to remediate mdx compliation issues, reference all of these docs before responding:
+[extending-mdx.mdx](mdc:reference-docs/mdx/extending-mdx.mdx)
+[getting-started.mdx](mdc:reference-docs/mdx/getting-started.mdx)
+[index.mdx](mdc:reference-docs/mdx/index.mdx)
+[troubleshooting-mdx.mdx](mdc:reference-docs/mdx/troubleshooting-mdx.mdx)
+[using-mdx.mdx](mdc:reference-docs/mdx/using-mdx.mdx)
+[what-is-mdx.mdx](mdc:reference-docs/mdx/what-is-mdx.mdx)

docs/policypak/policypak/applicationsettings/overview/videolearningcenter.md

@@ -117,7 +117,7 @@ See the following Video topics for Application Manager.
 
 - [Manage Google Chrome using Group Policy, SCCM or your own management utility](/docs/policypak/policypak/video/applicationsettings/chrome/gettingstarted.md)
 - [Google Chrome: Clear Browsing History, Cookies, Password, Images and more](/docs/policypak/policypak/video/applicationsettings/chrome/clearbrowsing.md)
-- [Manage Google Chrome Bookmarks](/docs/policypak/policypak/video/applicationsettings/chrome/bookmarks_.md)
+- [Manage Google Chrome Bookmarks](/docs/policypak/policypak/video/applicationsettings/chrome/bookmarks.md)
 
 ## Firefox (all videos)
 

docs/policypak/policypak/applicationsettings/preconfigured/firefox/transition.md

@@ -45,15 +45,15 @@ The upshot is:
 - If you use an older CSE you must use the Older AppSet (FF23)
 - Then when you use the new CSE and the New AppSet (FF115), Endpoint Policy Manager will operate as expected for FF ESR version 102.9 and also FF 115 and later
 
-Additionally, you will want to ensure that your existing FF23 AppSet policies do not get pushed  down to the machines with the new 23.10 and later CSE. During this guide you will use Item Level Targeting to ensure that the older FF23 AppSet cannot work with, and shouldn't be applied to newer CSEs; therefore we need to ensure that the newer FF115 AppSet only applies to the newer CSEs.
+Additionally, you will want to ensure that your existing FF23 AppSet policies do not get pushed  down to the machines with the new 23.10 and later CSE. During this guide you will use Item Level Targeting to ensure that the older FF23 AppSet cannot work with, and shouldn't be applied to newer CSEs; therefore we need to ensure that the newer FF115 AppSet only applies to the newer CSEs.
 
 __NOTE:__ This document mostly focuses on Group Policy Object delivery of the Firefox Endpoint Policy Manager AppSet. Note you may have other ways to deliver the FireFox Endpoint Policy Manager AppSet like Endpoint Policy Manager Cloud, local GPOs, and/or XML data files (via MSI files.) Be sure to perform this same operation using any and all methods.
 
 ## Finding all GPOs with Endpoint Policy Manager Application Settings Manager Data
 
 You'll want to first discover all GPOs with Endpoint Policy Manager Application Settings Manager Data, and those with specific Firefox 23 AppSets. That being said, automation can only help you discover which GPOs contain Endpoint Policy Manager Application Settings Manager data. After that, you must open each Group Policy Object one by one and manually look for FF23 AppSet data.
 
-Overview of using the Endpoint Policy Manager PowerShell cmdlets to discover Endpoint Policy Manager data within GPOs see the [Endpoint Policy Manager User PowerShell to find all Endpoint Policy Manager GPOs](/docs/policypak/policypak/video/troubleshooting/powershell.md) topic for additional information.
+Overview of using the Endpoint Policy Manager PowerShell cmdlets to discover Endpoint Policy Manager data within GPOs see the [Endpoint Policy Manager User PowerShell to find all Endpoint Policy Manager GPOs](/docs/policypak/policypak/video/troubleshooting/powershell.md) topic for additional information.
 
 ![939_1_image-20231101213809-1_950x372](/img/product_docs/policypak/policypak/applicationsettings/preconfigured/firefox/939_1_image-20231101213809-1_950x372.png)
 
@@ -138,13 +138,13 @@ When done save the values. You will know you have ILT set when you see the Targe
 
 ![939_7_image-20231101213809-7_950x273](/img/product_docs/policypak/policypak/applicationsettings/preconfigured/firefox/939_7_image-20231101213809-7_950x273.png)
 
-This is different than "Predefined Targeting". To understand the difference between ILT and Predefined Targeting see the [Predefined ILTs (Internal Filters)](/docs/policypak/policypak/video/applicationsettings/designstudio/itemleveltargeting.md) topic for additional information.
+This is different than "Predefined Targeting". To understand the difference between ILT and Predefined Targeting see the [Predefined ILTs (Internal Filters)](/docs/policypak/policypak/video/applicationsettings/designstudio/itemleveltargeting.md) topic for additional information.
 
 ### Optional: Testing the ILT Filters on FF23 using the Endpoint Policy Manager Item Level Targeting Validation Tool
 
 Tip: You can also export the FF 23 settings to XMLdata File format and use part of the output to verify the Item Level Targeting will evaluate to TRUE or FALSE. To do this, right-click the entry and select Export settings to XMLData file and save the file. Then use the Endpoint Policy Manager Item Level Targeting Validation tool to test how ILT will operate. See the [Troubleshooting ILT with the ILT Validator Tool](/docs/policypak/policypak/video/troubleshooting/itemleveltargeting.md) topic for additional information.
 
-__NOTE:__ You will have to trim the ILT part of the output to eliminate the``` <ILTFilters> ```at the beginning and ```</ILTFilters>``` at the end.
+__NOTE:__ You will have to trim the ILT part of the output to eliminate the `<ILTFilters>` at the beginning and `</ILTFilters>` at the end.
 
 ![939_8_image-20231101213809-8_950x453](/img/product_docs/policypak/policypak/applicationsettings/preconfigured/firefox/939_8_image-20231101213809-8_950x453.png)
 
@@ -208,7 +208,7 @@ Click OK and then close the AppSet entry to save it.
 
 You can also export the FF 115 settings to XMLdata File format and use part of the output to verify the Item Level Targeting will evaluate to TRUE or FALSE. To do this, right-click the entry and select Export settings to XMLData file and save the file. Then use the Endpoint Policy Manager Item Level Targeting Validation tool to test how ILT will operate. See the [Troubleshooting ILT with the ILT Validator Tool](/docs/policypak/policypak/video/troubleshooting/itemleveltargeting.md) topic for additional information.
 
-Note that you will have to trim the ILT part of the output to eliminate the <ILTFilters> at the beginning and </ILTFilters> at the end.
+Note that you will have to trim the ILT part of the output to eliminate the `<ILTFilters>` at the beginning and `</ILTFilters>` at the end.
 
 You can test the ILT evaluation by using the Export settings to XMLData file for the Mozilla Firefox 115 entry.
 
@@ -220,7 +220,7 @@ Then you can use the ILT Evaluator tool to ensure your ILT evaluation is properl
 
 # HTML Settings Report Manual Comparison
 
-In one of the backup steps we recommended you export the FF23 GPMC HTML report.  At this point you may also want to double-check the FF115 GPMC report for any discrepancies or omissions in the export/import process.
+In one of the backup steps we recommended you export the FF23 GPMC HTML report. At this point you may also want to double-check the FF115 GPMC report for any discrepancies or omissions in the export/import process.
 
 If you don't see an expected value this could be because (1) the FF115 Pak was updated to remove some values which appear to be unsupported in modern Firefox versions or (2) Some part of the Export from FF23 and import to FF115 didn't work as expected.
 

docs/policypak/policypak/applicationsettings/preconfigured/internetexplorer/tab/programs.md

@@ -16,9 +16,9 @@ Figure 21. Managing IE add-ons in Endpoint Policy Manager.
 
 To manage toolbars and extensions, you need the Class ID (GUID) of the extension, as shown in Figure 20. Click "Copy" to copy the whole text. Then cut and paste the corresponding Class ID, insert a comma, and specify "enable" or "disable," as shown in the lines of text below.
 
-{04c37f46-d9df-473c-943c-efa8d69854b9}, disable
+`{04c37f46-d9df-473c-943c-efa8d69854b9}`, disable
 
-{620ef192-a795-4f9d-9a6d-9da2adf95213}, enable
+`{620ef192-a795-4f9d-9a6d-9da2adf95213}`, enable
 
 Additionally, on this page you can:
 

docs/policypak/policypak/archive/autoupdater.md

@@ -14,15 +14,15 @@ __Step 1 –__ Download the Endpoint Policy Manager bits (721 or later) and loca
 
 __Step 2 –__ Copy / rename these files to the names that these build will recognize: Endpoint Policy Manager __CSE Setup x64.MSI__ and Endpoint Policy Manager __CSE Setup x86.msi__.
 
-__Step 3 –__ Place the now-renamed 721-or-later CSE and put in default SYSVOL location ( \sysvolsysvol<domain name>policiesPolicyPakCSE). This should force the build 605-703 CSEs to upgrade to version 712 (or later) CSE.
+__Step 3 –__ Place the now-renamed 721-or-later CSE and put in default SYSVOL location ( `\sysvolsysvol<domain name>policiesPolicyPakCSE`). This should force the build 605-703 CSEs to upgrade to version 712 (or later) CSE.
 
 If you have 704-711:
 
 __Step 1 –__ Download the Endpoint Policy Manager bits (721 or later) and locate the file named Endpoint Policy Manager __Client-Side Extension x86.MSI__ and Endpoint Policy Manager __Client-Side Extension x64.msi__.
 
 __Step 2 –__ Copy / rename these files to the names that these build will recognize: Endpoint Policy Manager __Application Manager CSE x86.msi__ and Endpoint Policy Manager __Application Manager CSE x64.msi__.
 
-__Step 3 –__ You must still use the default SYSVOL location ( \sysvolsysvol<domain name>policiesPolicyPakCSE). This should force the build 704-708 CSEs to upgrade to the 712 version (or later) CSE.
+__Step 3 –__ You must still use the default SYSVOL location ( `\sysvolsysvol<domain name>policiesPolicyPakCSE`). This should force the build 704-708 CSEs to upgrade to the 712 version (or later) CSE.
 
 If you have build 712:
 
@@ -32,7 +32,7 @@ __Step 1 –__ Download the Endpoint Policy Manager bits (721 or later) and loca
 
 __Step 2 –__ Copy / rename these files to the names that these build will recognize:Endpoint Policy Manager Application Manager CSE x86.msi and Endpoint Policy Manager Application Manager CSE x64.msi.
 
-__Step 3 –__ File placement: After renaming the file, you must put these renamed files in default SYSVOL location ( \sysvolsysvol<domain name>policiesPolicyPakCSE)
+__Step 3 –__ File placement: After renaming the file, you must put these renamed files in default SYSVOL location ( `\sysvolsysvol<domain name>policiesPolicyPakCSE`)
 
 Option 2: Use the update.config file and specify the precise filename to use)
 

docs/policypak/policypak/archive/designstudiofirefox.md

@@ -20,7 +20,7 @@ What we're going to do is go over to the "Design Studio" first. We'll then go ah
 
 Next thing we want to do is this is a true/false, so what I would suggest that you do here is you put a little "Check Box" in. I'm going to put a little "Check Box" here, and we can call this checkbox "Checked is TRUE," which of course means that unchecked would be false. OK.
 
-Then on this value here, I'm going to go to "Advanced" parameters and under "First Action" I'm going to pick the "Mozilla-specific config file." We're in Mozilla, and all this is already situated so we're OK here. You just leave "<project root>." You put in the "Property" name. We'll go ahead and we'll call this – again this is the official thing we're doing here – which is "browser.shell.checkDefaultBrowser." The "Default state" is "Unchecked," and the "Revert state" is "Unchecked."
+Then on this value here, I'm going to go to "Advanced" parameters and under "First Action" I'm going to pick the "Mozilla-specific config file." We're in Mozilla, and all this is already situated so we're OK here. You just leave `<project root>`. You put in the "Property" name. We'll go ahead and we'll call this – again this is the official thing we're doing here – which is "browser.shell.checkDefaultBrowser." The "Default state" is "Unchecked," and the "Revert state" is "Unchecked."
 
 Next we need to go to "Data type," and it's not an "Integer," right? It is a "Boolean," and therefore "On" when it's checked is "True" and "Off" will be "False." OK, so that's how this all lines up. You need to know the "Date type," which is the first thing we did. We figured out is it a "String," is it an "Integer" or a "Boolean." Then you put the information here as you need to – so "Boolean," "True" or "False."
 

docs/policypak/policypak/gpoexport/securitysettings.md

@@ -4,7 +4,7 @@ Over thirteen types of security settings can be managed with Netwrix Endpoint Po
 
 - Account Policies
   - Password Policy
-  - Account Lockout Policy<
+  - Account Lockout Policy
   - Kerberos Policy
 - Local Policies
   - Audit Policy

docs/policypak/policypak/install/clientsideextension/guids.md

@@ -2,22 +2,22 @@
 
 | COMPONENT | CSE EXTENSION GUID | RELEASED IN BUILD |  |
 | --- | --- | --- | --- |
-| Netwrix Endpoint Policy Manager (formerly PolicyPak) Application Manager | {F8357AE4-F4E0-49EC-AE9D-61078938E7CD} | 747 |  |
-| Endpoint Policy Manager Administrative Templates Manager | {E0088A46-AB54-4FBD-A733-303C58244C5E} | 747 |  |
-| Endpoint Policy Manager Preferences Manager | {608BA33D-AF06-46F9-9E6C-62495560024E} | 747 |  |
-| Endpoint Policy Manager Security Manager | {342A05C5-2052-4C55-8996-A539707D21F4} | 747 |  |
-| Endpoint Policy Manager MDM Settings Manager    (DEPRECATED as a MMC plugin in v2) | {DC73979D-AB98-46BE-B126-FB32182DDB8A} | 785 v1, 1371 v2 1500 deprecated |  |
-| Endpoint Policy Manager Browser Router | {1659C456-08FC-4359-B125-BB70EE34DD55} | 785 |  |
-| Endpoint Policy Manager Least Privilege Manager | {58DE0268-6384-49E0-A333-20EC46654B82} | 1149 |  |
-| Endpoint Policy Manager Java Rules Manager (aka Java Enterprise Deployment Rule Set Manager) | {3557AF76-7192-460B-A80C-393F7CA6220F} | 1227 |  |
-| Endpoint Policy Manager File Associations Manager | {32F17E56-85B0-460F-B029-8EAA332F440B} | 1371 |  |
-| Endpoint Policy Manager Start Screen & Taskbar Manager | {D60C1153-50A6-469D-A1C1-9F58A35504FE} | 1560 |  |
-| Endpoint Policy Manager Scripts Manager | {3219BD7B-1A0A-4A49-976C-CE18E0086860} | 1638 |  |
-| Endpoint Policy Manager Feature Manager for Windows | {A3421EA7-1C42-4C95-9908-4A73062DA938} | 1988 |  |
-| Endpoint Policy Manager Remote Desktop Protocol Manager | {DACB03DF-C80F-4031-99DB-B11889AC74DF} | 2513 |  |
-| Endpoint Policy Manager Remote Work Delivery Manager | {AC57FC3E-861F-4425-B9AD-368722549A22} | 2536 |  |
-| Endpoint Policy Manager VPN Manager | {4482335D-8FDD-47EE-B285-556DF04F7F2F} | 2687 |  |
-| Endpoint Policy Manager Software Package Manager | {993C3D17-E2BF-4562-8D86-14419E52977C} | 2700 |  |
+| Netwrix Endpoint Policy Manager (formerly PolicyPak) Application Manager | `{F8357AE4-F4E0-49EC-AE9D-61078938E7CD}` | 747 |  |
+| Endpoint Policy Manager Administrative Templates Manager |`{E0088A46-AB54-4FBD-A733-303C58244C5E}` | 747 |  |
+| Endpoint Policy Manager Preferences Manager |`{608BA33D-AF06-46F9-9E6C-62495560024E}` | 747 |  |
+| Endpoint Policy Manager Security Manager |`{342A05C5-2052-4C55-8996-A539707D21F4}` | 747 |  |
+| Endpoint Policy Manager MDM Settings Manager    (DEPRECATED as a MMC plugin in v2) |`{DC73979D-AB98-46BE-B126-FB32182DDB8A}` | 785 v1, 1371 v2 1500 deprecated |  |
+| Endpoint Policy Manager Browser Router |`{1659C456-08FC-4359-B125-BB70EE34DD55}` | 785 |  |
+| Endpoint Policy Manager Least Privilege Manager |`{58DE0268-6384-49E0-A333-20EC46654B82}` | 1149 |  |
+| Endpoint Policy Manager Java Rules Manager (aka Java Enterprise Deployment Rule Set Manager) |`{3557AF76-7192-460B-A80C-393F7CA6220F}` | 1227 |  |
+| Endpoint Policy Manager File Associations Manager |`{32F17E56-85B0-460F-B029-8EAA332F440B}` | 1371 |  |
+| Endpoint Policy Manager Start Screen & Taskbar Manager |`{D60C1153-50A6-469D-A1C1-9F58A35504FE}` | 1560 |  |
+| Endpoint Policy Manager Scripts Manager |`{3219BD7B-1A0A-4A49-976C-CE18E0086860}` | 1638 |  |
+| Endpoint Policy Manager Feature Manager for Windows |`{A3421EA7-1C42-4C95-9908-4A73062DA938}` | 1988 |  |
+| Endpoint Policy Manager Remote Desktop Protocol Manager |`{DACB03DF-C80F-4031-99DB-B11889AC74DF}` | 2513 |  |
+| Endpoint Policy Manager Remote Work Delivery Manager |`{AC57FC3E-861F-4425-B9AD-368722549A22}` | 2536 |  |
+| Endpoint Policy Manager VPN Manager |`{4482335D-8FDD-47EE-B285-556DF04F7F2F}` | 2687 |  |
+| Endpoint Policy Manager Software Package Manager |`{993C3D17-E2BF-4562-8D86-14419E52977C}` | 2700 |  |
 | Endpoint Policy Manager Network Security Manager | BFEE5AC6-79E1-41D6-B946-23BFBDD90C96 | 3557 |  |
 | Endpoint Policy Manager RDP Manager | DACB03DF-C80F-4031-99DB-B11889AC74DF | 2513 |  |
 | Endpoint Policy Manager Device Manager | 7FA1BDCB-818A-4EF6-A1B7-EF5F85C2D702 | 2905 |  |

docs/policypak/policypak/install/ringsupgrade.md

@@ -23,9 +23,9 @@ Therefore, if the first Ring element uses DateTime, then RingCatchAll MUST use D
 
 Some notes:
 
-- <DateTime>2021-12-05 15:00:00</DateTime>: This is YEAR-MONTH-DAY  and 24:00:00 format.
-- <RandomOffset>60</RandomOffset>: Is optional parameter but doesn't work by itself.
-- <RingCatchAll> is optional. If a computer is not specified within a specific ring, then it will automatically know it should be in the <RingCatchAll> ring.
+- `<DateTime>2021-12-05 15:00:00</DateTime>`: This is YEAR-MONTH-DAY  and 24:00:00 format.
+- `<RandomOffset>60</RandomOffset>`: Is optional parameter but doesn't work by itself.
+- `<RingCatchAll>` is optional. If a computer is not specified within a specific ring, then it will automatically know it should be in the `<RingCatchAll>` ring.
 
 ## Example 1: Using specific dates and times to make rings and perform a rollout
 
@@ -63,7 +63,7 @@ Some notes:
 
 With this method you set your rings apart with number of hours between updates.
 
-__NOTE:__  Use the <HoursBeforeUpdate> value to specify how many hours to delay. Note that if <HoursBeforeUpdate> is 0, then the update should perform immediately after the CSE checks in and sees what ring it is in.
+__NOTE:__  Use the `<HoursBeforeUpdate>` value to specify how many hours to delay. Note that if `<HoursBeforeUpdate>` is 0, then the update should perform immediately after the CSE checks in and sees what ring it is in.
 
 ```
 <?xml version="1.0" encoding="UTF-8"?>  
@@ -106,7 +106,7 @@ Breakdown of the parameters for the ```update.config``` file and how to use them
 | --- | --- | --- | --- |
 | Enabled | Enables/disables     auto-update | True or False | Enabled (True) by default |
 | CheckForUpdatesInterval | Sets a schedule for    when the CSE will    perform an auto    check for a new    version | Interval (in minutes) when    checking for an update | The default value is 360 (6    hours). |
-| MSIROOT | Enables you to point    to any share of your    choice to house the    CSE update (instead    of using the Endpoint Policy Manager     Central Storage and    CSE directory) | Any share name, such as   \\server123\PPCSES | Defaults to \\sysvol\sysvol\    <domain name>\policies\policypak    \CSE directory |
+| MSIROOT | Enables you to point    to any share of your    choice to house the    CSE update (instead    of using the Endpoint Policy Manager     Central Storage and    CSE directory) | Any share name, such as   \\server123\PPCSES | Defaults to \\sysvol\sysvol\    `<domain` name>\policies\policypak    \CSE directory |
 | GenerateReports | Facilitates reports to    show success or    failure of machines'    updates | True or False | Disabled (False) by default |
 | ReportsRoot | Sets a share up to    receive CSE update    reports | Any share name, such as   \\server123\Reports | This is not defined and will not    generate reports if   GenerateReports is not set. |
 | CheckForConfigInterval | Tells the CSE how    often to check for    updates within this    configuration file | Any interval (in minutes) | Defaults to 90 minutes |

docs/policypak/policypak/itemleveltargeting/windowsserver2019.md

@@ -44,6 +44,6 @@ __Step 1 –__ Locate the CurrentBuildNumber using the registry.
 
 __Step 2 –__ Then set your ILT to something similar to this:
 
-Windows 10 and BuildNumber <= 17704
+Windows 10 and BuildNumber \<= 17704
 
 ![88_7_image](/img/product_docs/policypak/policypak/itemleveltargeting/88_7_image.png)