They even broke it twice. There are two major ways of doing 802.1X during deployment. * using user certs and use 802.1X in PE - Broken In PE
* Using Mab and switch to 802.1X after you got a valid certificate. - broken in SCCM. In 2012 you can do certutil -pulse to trigger a cert autoenrollment. In 2016 MS has broken this (I got a case on it currently) -----Original Message----- From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Miller, Todd Sent: den 12 april 2017 05:50 To: mdtosd@lists.myITforum.com Subject: [MDT-OSD] 802.1x is still broken Almost unbelievably, WinPE 10 still cannot function on an 802.1x secured network. How is this bug still present in 1703? ________________________________ Notice: This UI Health Care e-mail (including attachments) is covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521 and is intended only for the use of the individual or entity to which it is addressed, and may contain information that is privileged, confidential, and exempt from disclosure under applicable law. If you are not the intended recipient, any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender immediately and delete or destroy all copies of the original message and attachments thereto. Email sent to or from UI Health Care may be retained as required by law or regulation. Thank you. ________________________________
