Set objshell = CreateObject("Wscript.Shell") Prepare a file called 8021x.vbs that contains: Prepare a file called TSConfig.ini that contains:ĬommandLine="x:\Windows\system32\cscript.exe x:\windows\System32\8021x.vbs" I shall call them profile.xml for the LAN Profile and uprofile.xml for the EAP Host User Credentials. You will need to prepare two xml files (see This Technet Post for the XML content) for authentication purposes. I explained in my last post why certain files are needed, so please read this as I will shorten this post by not rewriting this information. So this post is not all my own knowledge and work, there are other people in the background proving each point. But with a bit more poking at the TechNet forums I managed to over come these. While 802.1x worked, there were obvious flaws.
Inject hotfix into wim sccm ntlite dism windows#
Changing the WIM file after updating the package resulted a package hash mismatch (as the hash is calculated when SCCM updates the package, not when the DPs are refreshed.) This meant that the image could only be used for initial boot and failed when the image was downloaded (either from within Windows or when switching architecture.).This was because the TSBootshell.ini file was only run when initially running the task sequence and not when continuing a task sequence. The 802.1x only occurred only at initial boot and subsequent reboots failed to authenticate.So the problems that occurred following my last post were:
It seems my previous post on this was a little premature but provided a testing a ground for the technology.
After many months of asking questions I seem to have come up with a definitive 'working in all scenarios' guide to enabling 802.1x in WinPE and working with System Center Configuration Manager.