CAT Auto Pulish for Windows Release Messages - 20200219134607 (#2081)

* Update vpnv2-profile-xsd.md

<MachineMethod>Eap</MachineMethod> should’t be in the example, because

1.  MachineMethod can only be Certificate 
------ see https://docs.microsoft.com/en-gb/windows/client-management/mdm/vpnv2-csp 
........................VPNv2/ProfileName/NativeProfile/Authentication/MachineMethod
                         This is only supported in IKEv2.
                                This value can be one of the following:
                                •	Certificate

2. A profile conatins either UserMethod or MachineMethod but not both

* Update advanced-troubleshooting-802-authentication.md

* missing "r" in $OSArch

https://github.com/MicrosoftDocs/windows-itpro-docs/issues/5972

* Update windows/client-management/advanced-troubleshooting-802-authentication.md

Co-Authored-By: JohanFreelancer9 <48568725+JohanFreelancer9@users.noreply.github.com>

* Update windows/client-management/advanced-troubleshooting-802-authentication.md

Co-Authored-By: JohanFreelancer9 <48568725+JohanFreelancer9@users.noreply.github.com>

* Update windows/client-management/advanced-troubleshooting-802-authentication.md

Co-Authored-By: Trond B. Krokli <38162891+illfated@users.noreply.github.com>

* Test, updated Caps

* Update windows/client-management/advanced-troubleshooting-802-authentication.md

Co-Authored-By: JohanFreelancer9 <48568725+JohanFreelancer9@users.noreply.github.com>

* Multiple corrections required (see notes)

@Dansimp 

1) This note is contradictory - need to clarify this:
"> [!NOTE]
> Device credential group policy setting is not supported for enrolling into Microsoft Intune. "
2) We should remove all references to "Primary Domain Controller" (PDC) - it's not the 90's with Windows NT 4.0 anymore !
3) "Restart the Domain Controller for the policy to be available."
   A reboot is not required
4) "Enforce a GPO link"
   This is in contradiction with our recommended practices. We should not be suggesting this.

* Update web-content-filtering.md

fixed extra space

* CAT Auto Pulish for Windows Release Messages - CAT_AutoPublish_20200219114538 (#2080)

Co-authored-by: Direesh Kumar Kandakatla <direek@microsoft.com>

Co-authored-by: rogersoMS <44718379+rogersoMS@users.noreply.github.com>
Co-authored-by: Daniel Simpson <dansimp@microsoft.com>
Co-authored-by: Office Content Publishing <34616516+officedocspr@users.noreply.github.com>
Co-authored-by: Tina Burden <v-tibur@microsoft.com>
Co-authored-by: Direesh Kumar Kandakatla <direek@microsoft.com>
This commit is contained in:
John Liu
2020-02-19 13:58:02 -08:00
committed by GitHub
parent af2cce9f8d
commit 0d2ee0d912
23 changed files with 37 additions and 171 deletions

View File

@ -59,7 +59,7 @@ First, validate the type of EAP method being used:
![eap authentication type comparison](images/comparisontable.png)
If a certificate is used for its authentication method, check if the certificate is valid. For server (NPS) side, you can confirm what certificate is being used from the EAP property menu:
If a certificate is used for its authentication method, check if the certificate is valid. For server (NPS) side, you can confirm what certificate is being used from the EAP property menu. In **NPS snap-in**, go to **Policies** > **Network Policies**. Right click on the policy and select **Properties**. In the pop-up window, go to the **Constraints** tab and select the **Authentication Methods** section.
![Constraints tab of the secure wireless connections properties](images/eappropertymenu.png)
@ -118,4 +118,3 @@ Even if audit policy appears to be fully enabled, it sometimes helps to disable
[Troubleshooting Windows Vista 802.11 Wireless Connections](https://technet.microsoft.com/library/cc766215%28v=ws.10%29.aspx)<br>
[Troubleshooting Windows Vista Secure 802.3 Wired Connections](https://technet.microsoft.com/library/cc749352%28v=ws.10%29.aspx)