Removing a note since it's not accurate. The note below which states that Device credential is supported for Co-management and Azure Virtual Desktop is accurate.
Device Credential
Is only supported for:
- Co-management
- WVD (Azure Virtual Desktop)
- Autopilot deploying mode - witch is not using GPO for enrollment
As outlined in issue ticket #8682 (3rd bullet point in Requirements section is confusing, and linked page is unrelated to the link's text), "The linked page contains basically no information about registering your "enterprise AD" with Azure AD. Instead, that page is a somewhat convoluted set of sections that are sort of unrelated to anything specific."
Thanks to Jeremy T. Bradshaw (JeremyTBradshaw) for identifying and reporting this issue.
Changes proposed:
- change the MDM page link URL to a more precise Azure AD page link
- change the 3rd bullet point text to refer to the new page link
Whitespace changes:
- remove end-of-line redundant whitespace (blanks)
Closes#8682
This change corrects a broken "Important" note that might've included two procedures. I've fixed the note and revised it to not encapsulate the two procedures.
Even though Device Credential is an option on the GPO, the device credential gives error while auto-enrollment tasks running through the Task Scheduler. To avoid this error we need to choose the User Credential option from the dropdown to auto-enroll the device. The below line has been updated on the document.
5. Click **Enable**, and select **User Credential** from the dropdown **Select Credential Type to Use**, then click **OK**.
* 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>
