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>
Updated GPO name and links to files. Edited instructions to include new options in GPO and removed hyperlinks to older version of ADMX files (1803) and added links to newest version (1903)
"Enable automatic MDM enrollment using default Azure AD credentials" is the GPO name and it has two sub options. Not sure if Device Certificate is working at the moment, but the pictures are wrong, but User Certificate is working and so the docs should at least say to use that for now
Description:
Administrative Templates (.admx) for Windows 10 May 2019 Update (1903)
v3.0 has been available since 2019-08-28 and this page needs updating
to reflect this change, as mentioned in issue ticket #5078.
Proposed changes:
- Remove the note saying that Windows 10 version 1903 is still on the
Insider program and doesn't contain any downloadable templates yet.
- Add version number 1903 and its link to the list (under 1803 & 1809)
- Add folder information for the installed 1903 templates location
- Minor MarkDown space standardization adjustments
- Add missing blank line after one of the headings
issue ticket closure or reference:
Closes#5078
Adds note that the scheduled task that triggers GPO enrollment isn't visible to standard users so to confirm the task was created, admin creds should be used
Removed some language tags from links, and verified that they still work and apply the users own language when visited.
Added more clarification to certain subjects.
