@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.
@greg-lindsay , @Dansimp
The edit on this article is complete per work item 3851148. Let me know if my edits changed the technical meaning anywhere. Once you've approved, please sign off.
Thanks!
Kelly
@greg-lindsay , @Dansimp
The edit on this article is complete per work item 3851148. Let me know if my edits changed the technical meaning anywhere. Once you've approved, please sign off.
Two comments:
- Changing "internet" to "Internet" contra MS Writing style per team guidance that MARVEL follows this usage.
- Lines 135, 267, and 288 seems to be referencing the "EAP configuration article." Is this a different article? If so, should we provide a link? If not, should we make that clearer?
Thanks!
Kelly
@greg-lindsay , @Dansimp
The edit on this article is complete per work item 3851148. Let me know if my edits changed the technical meaning anywhere. Once you've approved, please sign off.
Thanks!
Kelly
<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