* 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>
Description:
As pointed out in issue ticket #6017 (Double 0 typo), Windows Server
2016 contains a double 0 typo which needs correction.
Thanks to vainkop for making us aware of this typo issue.
Proposed change:
- Remove the extra 0 to spell Windows Server 2016 correctly.
issue ticket closure or reference:
Closes#6017
As the link is not pointing to a proper source and there is no other information is available on Microsoft docs so I have removed this link. The link provided was pointing to the LinkedIn course intro video and doesn't fit with the context of the article.
Problem: https://github.com/MicrosoftDocs/windows-itpro-docs/issues/5854
