From eed4959625d234f744b08d41b380b82128f4b440 Mon Sep 17 00:00:00 2001 From: jsuther1974 Date: Tue, 1 Oct 2019 08:29:35 -0700 Subject: [PATCH 01/16] Correct documentation for Disable:Script Enforcement Disable:Script Enforcement option is incorrectly marked as not supported. Fixed the documentation for this feature option. --- .../select-types-of-rules-to-create.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/security/threat-protection/windows-defender-application-control/select-types-of-rules-to-create.md b/windows/security/threat-protection/windows-defender-application-control/select-types-of-rules-to-create.md index db654141a9..287c247293 100644 --- a/windows/security/threat-protection/windows-defender-application-control/select-types-of-rules-to-create.md +++ b/windows/security/threat-protection/windows-defender-application-control/select-types-of-rules-to-create.md @@ -64,7 +64,7 @@ You can set several rule options within a WDAC policy. Table 2 describes each ru | **8 Required:EV Signers** | In addition to being WHQL signed, this rule requires that drivers must have been submitted by a partner that has an Extended Verification (EV) certificate. All future Windows 10 and later drivers will meet this requirement. | | **9 Enabled:Advanced Boot Options Menu** | The F8 preboot menu is disabled by default for all WDAC policies. Setting this rule option allows the F8 menu to appear to physically present users. | | **10 Enabled:Boot Audit on Failure** | Used when the WDAC policy is in enforcement mode. When a driver fails during startup, the WDAC policy will be placed in audit mode so that Windows will load. Administrators can validate the reason for the failure in the CodeIntegrity event log. | -| **11 Disabled:Script Enforcement** | This option is not currently supported. | +| **11 Disabled:Script Enforcement** | This option disables script enforcement options. Unsigned PowerShell scripts and interactive PowerShell are no longer restricted to Restricted Language Mode. NOTE: This option is only supported with the Windows 10 May 2019 Update (1903) and higher. Using it on earlier versions of Windows 10 is not supported and may have unintended results. | | **12 Required:Enforce Store Applications** | If this rule option is enabled, WDAC policies will also apply to Universal Windows applications. | | **13 Enabled:Managed Installer** | Use this option to automatically allow applications installed by a software distribution solution, such as System Center Configuration Manager, that has been defined as a managed installer. | | **14 Enabled:Intelligent Security Graph Authorization** | Use this option to automatically allow applications with "known good" reputation as defined by Microsoft’s Intelligent Security Graph (ISG). | From 5fe4bc604ddcc1773b636143e32019bc8af6fc67 Mon Sep 17 00:00:00 2001 From: George Jacob Date: Sat, 5 Oct 2019 19:44:57 +0530 Subject: [PATCH 02/16] Grammattical error corrected. Removed a wrong usage of the verb 'is', in a sentence. --- .../bitlocker/bitlocker-overview-and-requirements-faq.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/security/information-protection/bitlocker/bitlocker-overview-and-requirements-faq.md b/windows/security/information-protection/bitlocker/bitlocker-overview-and-requirements-faq.md index 000e35587d..a4733f2848 100644 --- a/windows/security/information-protection/bitlocker/bitlocker-overview-and-requirements-faq.md +++ b/windows/security/information-protection/bitlocker/bitlocker-overview-and-requirements-faq.md @@ -41,7 +41,7 @@ Yes, BitLocker supports multifactor authentication for operating system drives. For requirements, see [System requirements](bitlocker-overview.md#system-requirements). > [!NOTE] -> Dynamic disks are not supported by BitLocker. Dynamic data volumes will not be displayed in the Control Panel. Although the operating system volume will always be displayed in the Control Panel, regardless of whether it is a Dynamic disk, if it is a dynamic disk it is cannot be protected by BitLocker. +> Dynamic disks are not supported by BitLocker. Dynamic data volumes will not be displayed in the Control Panel. Although the operating system volume will always be displayed in the Control Panel, regardless of whether it is a Dynamic disk, if it is a dynamic disk it cannot be protected by BitLocker. ## Why are two partitions required? Why does the system drive have to be so large? From 7aee40c961b6c58303a9cebc810a734bd68ee359 Mon Sep 17 00:00:00 2001 From: MaratMussabekov <48041687+MaratMussabekov@users.noreply.github.com> Date: Tue, 8 Oct 2019 09:38:34 +0500 Subject: [PATCH 03/16] Update event-5156.md --- windows/security/threat-protection/auditing/event-5156.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/windows/security/threat-protection/auditing/event-5156.md b/windows/security/threat-protection/auditing/event-5156.md index 613f28d976..a86cedf37d 100644 --- a/windows/security/threat-protection/auditing/event-5156.md +++ b/windows/security/threat-protection/auditing/event-5156.md @@ -102,7 +102,7 @@ This event generates when [Windows Filtering Platform](https://msdn.microsoft.co - Outbound – for unbound connections. -- **Source Address** \[Type = UnicodeString\]**:** local IP address on which application received the connection. +- **Source Address** \[Type = UnicodeString\]**:** IP address from which connection was initiated. - IPv4 Address @@ -114,9 +114,9 @@ This event generates when [Windows Filtering Platform](https://msdn.microsoft.co - 127.0.0.1 , ::1 - localhost -- **Source Port** \[Type = UnicodeString\]**:** port number on which application received the connection. +- **Source Port** \[Type = UnicodeString\]**:** port number on which connection was initiated. -- **Destination Address** \[Type = UnicodeString\]**:** IP address ***from*** which connection was received or initiated. +- **Destination Address** \[Type = UnicodeString\]**:** IP address to which connection was attempted. - IPv4 Address @@ -128,7 +128,7 @@ This event generates when [Windows Filtering Platform](https://msdn.microsoft.co - 127.0.0.1 , ::1 - localhost -- **Destination Port** \[Type = UnicodeString\]**:** port number which was used from remote machine to initiate connection. +- **Destination Port** \[Type = UnicodeString\]**:** port number on which connection was attempted. - **Protocol** \[Type = UInt32\]: number of protocol which was used. From 7babb242cf1419f432413d4fae77ba49b4de3183 Mon Sep 17 00:00:00 2001 From: MaratMussabekov <48041687+MaratMussabekov@users.noreply.github.com> Date: Tue, 8 Oct 2019 15:17:33 +0500 Subject: [PATCH 04/16] Update tpm-recommendations.md --- .../security/information-protection/tpm/tpm-recommendations.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/security/information-protection/tpm/tpm-recommendations.md b/windows/security/information-protection/tpm/tpm-recommendations.md index bd96309c30..4ab3d8f320 100644 --- a/windows/security/information-protection/tpm/tpm-recommendations.md +++ b/windows/security/information-protection/tpm/tpm-recommendations.md @@ -123,7 +123,7 @@ The following table defines which Windows features require TPM support. TPM Platform Crypto Provider Key Storage Provider| Yes | Yes | Yes Virtual Smart Card | Yes | Yes | Yes Certificate storage | No | Yes | Yes | TPM is only required when the certificate is stored in the TPM. - Autopilot | Yes | No | Yes | TPM 2.0 and UEFI firmware is required. + Autopilot | Yes | No | Yes | TPM 2.0 and UEFI firmware is required for white glove and self-deploying scenarios. SecureBIO | Yes | No | Yes | TPM 2.0 and UEFI firmware is required. DRTM | Yes | No | Yes | TPM 2.0 and UEFI firmware is required. From 4878c1f665856dd5705afc8c2b52a7d7809c202e Mon Sep 17 00:00:00 2001 From: Rona Song <38082753+qrscharmed@users.noreply.github.com> Date: Tue, 8 Oct 2019 15:19:02 -0700 Subject: [PATCH 05/16] Update faq-wd-app-guard.md --- .../faq-wd-app-guard.md | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/windows/security/threat-protection/windows-defender-application-guard/faq-wd-app-guard.md b/windows/security/threat-protection/windows-defender-application-guard/faq-wd-app-guard.md index ae7c4a20a4..5863d90777 100644 --- a/windows/security/threat-protection/windows-defender-application-guard/faq-wd-app-guard.md +++ b/windows/security/threat-protection/windows-defender-application-guard/faq-wd-app-guard.md @@ -111,3 +111,17 @@ Answering frequently asked questions about Windows Defender Application Guard (A
+| | | +|--------|-----------------------------------------------------------------------------------------------| +| **Q:** | Is there a size limit to the domain lists that I need to configure? | +| **A:** | Yes, both the Enterprise Resource domains hosted in the cloud and the Domains categorized as both work and personal have a 16383B limit.| + +
+ +| | | +|--------|-----------------------------------------------------------------------------------------------| +| **Q:** | Why does my encryption driver break WDAG? | +| **A:** | WDAG accesses files from a VHD mounted on the host that needs to be written during setup. If an encryption driver prevents a VHD from being mounted or from being written to, WDAG will not work. | + +
+ From 605187176a3ba3ba3d4c91e0f4fd75c68e78fb78 Mon Sep 17 00:00:00 2001 From: MaratMussabekov <48041687+MaratMussabekov@users.noreply.github.com> Date: Wed, 9 Oct 2019 15:31:06 +0500 Subject: [PATCH 06/16] Update event-5156.md --- windows/security/threat-protection/auditing/event-5156.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/windows/security/threat-protection/auditing/event-5156.md b/windows/security/threat-protection/auditing/event-5156.md index a86cedf37d..e3881d0ecb 100644 --- a/windows/security/threat-protection/auditing/event-5156.md +++ b/windows/security/threat-protection/auditing/event-5156.md @@ -102,7 +102,7 @@ This event generates when [Windows Filtering Platform](https://msdn.microsoft.co - Outbound – for unbound connections. -- **Source Address** \[Type = UnicodeString\]**:** IP address from which connection was initiated. +- **Source Address** \[Type = UnicodeString\]**:** IP address from which the connection was initiated. - IPv4 Address @@ -114,9 +114,9 @@ This event generates when [Windows Filtering Platform](https://msdn.microsoft.co - 127.0.0.1 , ::1 - localhost -- **Source Port** \[Type = UnicodeString\]**:** port number on which connection was initiated. +- **Source Port** \[Type = UnicodeString\]**:** port number on which the connection was initiated. -- **Destination Address** \[Type = UnicodeString\]**:** IP address to which connection was attempted. +- **Destination Address** \[Type = UnicodeString\]**:** IP address to which the connection was initiated. - IPv4 Address @@ -128,7 +128,7 @@ This event generates when [Windows Filtering Platform](https://msdn.microsoft.co - 127.0.0.1 , ::1 - localhost -- **Destination Port** \[Type = UnicodeString\]**:** port number on which connection was attempted. +- **Destination Port** \[Type = UnicodeString\]**:** port number on which the connection was initiated. - **Protocol** \[Type = UInt32\]: number of protocol which was used. From df758c084ee58d554e254592e60b538f5b57f6a9 Mon Sep 17 00:00:00 2001 From: Daniel Simpson Date: Wed, 9 Oct 2019 08:51:22 -0700 Subject: [PATCH 07/16] Update faq-wd-app-guard.md spelled out instances of WDAG to Windows Defender Application Guard --- .../faq-wd-app-guard.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/windows/security/threat-protection/windows-defender-application-guard/faq-wd-app-guard.md b/windows/security/threat-protection/windows-defender-application-guard/faq-wd-app-guard.md index 5863d90777..c2b8dc832a 100644 --- a/windows/security/threat-protection/windows-defender-application-guard/faq-wd-app-guard.md +++ b/windows/security/threat-protection/windows-defender-application-guard/faq-wd-app-guard.md @@ -67,8 +67,8 @@ Answering frequently asked questions about Windows Defender Application Guard (A | | | |--------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| **Q:** | How do I configure WDAG to work with my network proxy (IP-Literal Addresses)? | -| **A:** | WDAG requires proxies to have a symbolic name, not just an IP address. IP-Literal proxy settings such as “192.168.1.4:81” can be annotated as “itproxy:81” or using a record such as “P19216810010” for a proxy with an IP address of 192.168.100.10. This applies to Windows 10 Enterprise edition, 1709 or higher. These would be for the proxy policies under Network Isolation in Group Policy or Intune. | +| **Q:** | How do I configure Windows Defender Application Guard to work with my network proxy (IP-Literal Addresses)? | +| **A:** | Windows Defender Application Guard requires proxies to have a symbolic name, not just an IP address. IP-Literal proxy settings such as “192.168.1.4:81” can be annotated as “itproxy:81” or using a record such as “P19216810010” for a proxy with an IP address of 192.168.100.10. This applies to Windows 10 Enterprise edition, 1709 or higher. These would be for the proxy policies under Network Isolation in Group Policy or Intune. |
@@ -76,7 +76,7 @@ Answering frequently asked questions about Windows Defender Application Guard (A | | | |--------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | **Q:** | Which Input Method Editors (IME) in 19H1 are not supported? | -| **A:** | The following Input Method Editors (IME) introduced in Windows 10, version 1903 are currently not supported in WDAG.
Vietnam Telex keyboard
Vietnam number key-based keyboard
Hindi phonetic keyboard
Bangla phonetic keyboard
Marathi phonetic keyboard
Telugu phonetic keyboard
Tamil phonetic keyboard
Kannada phonetic keyboard
Malayalam phonetic keyboard
Gujarati phonetic keyboard
Odia phonetic keyboard
Punjabi phonetic keyboard | +| **A:** | The following Input Method Editors (IME) introduced in Windows 10, version 1903 are currently not supported in Windows Defender Application Guard.
Vietnam Telex keyboard
Vietnam number key-based keyboard
Hindi phonetic keyboard
Bangla phonetic keyboard
Marathi phonetic keyboard
Telugu phonetic keyboard
Tamil phonetic keyboard
Kannada phonetic keyboard
Malayalam phonetic keyboard
Gujarati phonetic keyboard
Odia phonetic keyboard
Punjabi phonetic keyboard |
@@ -120,8 +120,8 @@ Answering frequently asked questions about Windows Defender Application Guard (A | | | |--------|-----------------------------------------------------------------------------------------------| -| **Q:** | Why does my encryption driver break WDAG? | -| **A:** | WDAG accesses files from a VHD mounted on the host that needs to be written during setup. If an encryption driver prevents a VHD from being mounted or from being written to, WDAG will not work. | +| **Q:** | Why does my encryption driver break Windows Defender Application Guard? | +| **A:** | Windows Defender Application Guard accesses files from a VHD mounted on the host that needs to be written during setup. If an encryption driver prevents a VHD from being mounted or from being written to, WDAG will not work. |
From ddf58250ac8c01398c5153f8b14890712d6433e3 Mon Sep 17 00:00:00 2001 From: MaratMussabekov <48041687+MaratMussabekov@users.noreply.github.com> Date: Thu, 10 Oct 2019 16:45:51 +0500 Subject: [PATCH 08/16] Update windows/security/threat-protection/auditing/event-5156.md Co-Authored-By: Trond B. Krokli <38162891+illfated@users.noreply.github.com> --- windows/security/threat-protection/auditing/event-5156.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/security/threat-protection/auditing/event-5156.md b/windows/security/threat-protection/auditing/event-5156.md index e3881d0ecb..953804c16b 100644 --- a/windows/security/threat-protection/auditing/event-5156.md +++ b/windows/security/threat-protection/auditing/event-5156.md @@ -114,7 +114,7 @@ This event generates when [Windows Filtering Platform](https://msdn.microsoft.co - 127.0.0.1 , ::1 - localhost -- **Source Port** \[Type = UnicodeString\]**:** port number on which the connection was initiated. +- **Source Port** \[Type = UnicodeString\]**:** port number from which the connection was initiated. - **Destination Address** \[Type = UnicodeString\]**:** IP address to which the connection was initiated. From 3db50e79130c197fac7455f545d23b36666335c2 Mon Sep 17 00:00:00 2001 From: MaratMussabekov <48041687+MaratMussabekov@users.noreply.github.com> Date: Thu, 10 Oct 2019 16:45:58 +0500 Subject: [PATCH 09/16] Update windows/security/threat-protection/auditing/event-5156.md Co-Authored-By: Trond B. Krokli <38162891+illfated@users.noreply.github.com> --- windows/security/threat-protection/auditing/event-5156.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/security/threat-protection/auditing/event-5156.md b/windows/security/threat-protection/auditing/event-5156.md index 953804c16b..27ab53971a 100644 --- a/windows/security/threat-protection/auditing/event-5156.md +++ b/windows/security/threat-protection/auditing/event-5156.md @@ -116,7 +116,7 @@ This event generates when [Windows Filtering Platform](https://msdn.microsoft.co - **Source Port** \[Type = UnicodeString\]**:** port number from which the connection was initiated. -- **Destination Address** \[Type = UnicodeString\]**:** IP address to which the connection was initiated. +- **Destination Address** \[Type = UnicodeString\]**:** IP address where the connection was received. - IPv4 Address From f0e3c42402da1a046e76ff4f7b3b7d947d2e7d0b Mon Sep 17 00:00:00 2001 From: MaratMussabekov <48041687+MaratMussabekov@users.noreply.github.com> Date: Thu, 10 Oct 2019 16:46:09 +0500 Subject: [PATCH 10/16] Update windows/security/threat-protection/auditing/event-5156.md Co-Authored-By: Trond B. Krokli <38162891+illfated@users.noreply.github.com> --- windows/security/threat-protection/auditing/event-5156.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/security/threat-protection/auditing/event-5156.md b/windows/security/threat-protection/auditing/event-5156.md index 27ab53971a..a5aaae535b 100644 --- a/windows/security/threat-protection/auditing/event-5156.md +++ b/windows/security/threat-protection/auditing/event-5156.md @@ -128,7 +128,7 @@ This event generates when [Windows Filtering Platform](https://msdn.microsoft.co - 127.0.0.1 , ::1 - localhost -- **Destination Port** \[Type = UnicodeString\]**:** port number on which the connection was initiated. +- **Destination Port** \[Type = UnicodeString\]**:** port number where the connection was received. - **Protocol** \[Type = UInt32\]: number of protocol which was used. From 968743ea8bf6f7b96264f8f764c98a437101d3bd Mon Sep 17 00:00:00 2001 From: Andres Mariano Gorzelany <36666927+get-itips@users.noreply.github.com> Date: Thu, 10 Oct 2019 10:00:52 -0300 Subject: [PATCH 11/16] Propose adding 1809 or higher --- windows/configuration/customize-and-export-start-layout.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/configuration/customize-and-export-start-layout.md b/windows/configuration/customize-and-export-start-layout.md index 7ac4b1ff90..b9e7da8958 100644 --- a/windows/configuration/customize-and-export-start-layout.md +++ b/windows/configuration/customize-and-export-start-layout.md @@ -93,7 +93,7 @@ When you have the Start layout that you want your users to see, use the [Export- `Export-StartLayout –path .xml` - On a device running Windows 10, version 1809, run the **Export-StartLayout** with the switch **-UseDesktopApplicationID**. For example: + On a device running Windows 10, version 1809 or higher, run the **Export-StartLayout** with the switch **-UseDesktopApplicationID**. For example: ```PowerShell Export-StartLayout -UseDesktopApplicationID -Path layout.xml From 1beeec7b8ec0c8f483230f80917029ca4c3e1126 Mon Sep 17 00:00:00 2001 From: Baard Hermansen Date: Fri, 11 Oct 2019 10:09:18 +0200 Subject: [PATCH 12/16] Update active-directory-based-activation-overview.md Updated the links under Related topics. --- .../active-directory-based-activation-overview.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/windows/deployment/volume-activation/active-directory-based-activation-overview.md b/windows/deployment/volume-activation/active-directory-based-activation-overview.md index b0c4c10975..581a2a317e 100644 --- a/windows/deployment/volume-activation/active-directory-based-activation-overview.md +++ b/windows/deployment/volume-activation/active-directory-based-activation-overview.md @@ -9,7 +9,8 @@ ms.prod: w10 ms.mktglfcycl: deploy ms.sitesec: library ms.pagetype: activation -audience: itpro author: greg-lindsay +audience: itpro +author: greg-lindsay ms.date: 12/07/2018 ms.topic: article --- @@ -37,7 +38,7 @@ VAMT enables IT Professionals to manage and activate the ADBA object. Activation ## Related topics -- [How to Activate an Active Directory Forest Online](https://go.microsoft.com/fwlink/p/?LinkId=246565) -- [How to Proxy Activate an Active Directory Forest](https://go.microsoft.com/fwlink/p/?LinkId=246566) +- [How to Activate an Active Directory Forest Online](https://docs.microsoft.com/windows/deployment/volume-activation/activate-forest-vamt) +- [How to Proxy Activate an Active Directory Forest](https://docs.microsoft.com/windows/deployment/volume-activation/activate-forest-by-proxy-vamt)     From cf045b9464d5b2b8f05923aed09fdab375f2eccf Mon Sep 17 00:00:00 2001 From: Nikita Potapenko Date: Fri, 11 Oct 2019 11:26:41 +0300 Subject: [PATCH 13/16] Fix quotes --- mdop/appv-v5/deploying-microsoft-office-2016-by-using-app-v.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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 index 4dbf7f3b64..f66484192f 100644 --- 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 @@ -224,7 +224,7 @@ The XML file that is included in the Office Deployment Tool specifies the produc ```xml - + From ad1edc1ec2cfd932f9508ce6e21c735c6a848095 Mon Sep 17 00:00:00 2001 From: Raaj Baskaran Date: Mon, 14 Oct 2019 07:32:38 -0500 Subject: [PATCH 14/16] tasbkar -> taskbar :) --- windows/configuration/customize-and-export-start-layout.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/configuration/customize-and-export-start-layout.md b/windows/configuration/customize-and-export-start-layout.md index b9e7da8958..f13d6f81c8 100644 --- a/windows/configuration/customize-and-export-start-layout.md +++ b/windows/configuration/customize-and-export-start-layout.md @@ -191,7 +191,7 @@ If the Start layout is applied by Group Policy or MDM, and the policy is removed - [Start layout XML for desktop editions of Windows 10 (reference)](start-layout-xml-desktop.md) - [Customize Windows 10 Start and taskbar with Group Policy](customize-windows-10-start-screens-by-using-group-policy.md) - [Customize Windows 10 Start and taskbar with provisioning packages](customize-windows-10-start-screens-by-using-provisioning-packages-and-icd.md) -- [Customize Windows 10 Start and tasbkar with mobile device management (MDM)](customize-windows-10-start-screens-by-using-mobile-device-management.md) +- [Customize Windows 10 Start and taskbar with mobile device management (MDM)](customize-windows-10-start-screens-by-using-mobile-device-management.md) - [Changes to Start policies in Windows 10](changes-to-start-policies-in-windows-10.md) From 668b7c99baec2cd7d1b3d19f7abc9dfe23b6b20e Mon Sep 17 00:00:00 2001 From: Raaj Baskaran Date: Mon, 14 Oct 2019 07:34:48 -0500 Subject: [PATCH 15/16] removed ach --- .../bitlocker/bitlocker-overview-and-requirements-faq.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/security/information-protection/bitlocker/bitlocker-overview-and-requirements-faq.md b/windows/security/information-protection/bitlocker/bitlocker-overview-and-requirements-faq.md index a4733f2848..53ed00fa28 100644 --- a/windows/security/information-protection/bitlocker/bitlocker-overview-and-requirements-faq.md +++ b/windows/security/information-protection/bitlocker/bitlocker-overview-and-requirements-faq.md @@ -78,4 +78,4 @@ To turn on, turn off, or change configurations of BitLocker on operating system ## What is the recommended boot order for computers that are going to be BitLocker-protected? -You should configure the startup options of your computer to have the hard disk drive first in the boot order, before any other drives such ach as CD/DVD drives or USB drives. If the hard disk is not first and you typically boot from hard disk, then a boot order change may be detected or assumed when removable media is found during boot. The boot order typically affects the system measurement that is verified by BitLocker and a change in boot order will cause you to be prompted for your BitLocker recovery key. For the same reason, if you have a laptop with a docking station, ensure that the hard disk drive is first in the boot order both when docked and undocked.  +You should configure the startup options of your computer to have the hard disk drive first in the boot order, before any other drives such as CD/DVD drives or USB drives. If the hard disk is not first and you typically boot from hard disk, then a boot order change may be detected or assumed when removable media is found during boot. The boot order typically affects the system measurement that is verified by BitLocker and a change in boot order will cause you to be prompted for your BitLocker recovery key. For the same reason, if you have a laptop with a docking station, ensure that the hard disk drive is first in the boot order both when docked and undocked.  From 205334bab423f45a119f89c64a50c1ba922fd7da Mon Sep 17 00:00:00 2001 From: Raaj Baskaran Date: Mon, 14 Oct 2019 07:36:33 -0500 Subject: [PATCH 16/16] compter -> computer --- windows/security/threat-protection/auditing/event-5156.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/security/threat-protection/auditing/event-5156.md b/windows/security/threat-protection/auditing/event-5156.md index a5aaae535b..cdfc758875 100644 --- a/windows/security/threat-protection/auditing/event-5156.md +++ b/windows/security/threat-protection/auditing/event-5156.md @@ -184,7 +184,7 @@ For 5156(S): The Windows Filtering Platform has permitted a connection. - If you need to monitor all inbound connections to a specific local port, monitor for [5156](event-5156.md) events with that “**Source Port**.**”** -- Monitor for all connections with a “**Protocol Number”** that is not typical for this device or compter, for example, anything other than 1, 6, or 17. +- Monitor for all connections with a “**Protocol Number”** that is not typical for this device or computer, for example, anything other than 1, 6, or 17. - If the computer’s communication with “**Destination Address”** should always use a specific “**Destination Port**,**”** monitor for any other “**Destination Port**.”