WinPE Wired Autoconfig 802.1x

Question

WinPE Wired Autoconfig 802.1x

Ze Wong 1

Hey,

I am using WinPE Version 10.0.19041 with IEEE 802.1x network authentication protocol.

During the start up I am using

Net Start dot3svc

But receiving the error below

The Wired AutoConfig service is starting
The Wired AutoConfig service could not be started
A System error has occurred.
System error 2753 has occurred.
There are no more endpoints available from the endpoint mapper.

Is anyone experiencing the issue? I am trying to incorporate 802.1x into the Imaging process and it's failing before i can even import the network profile.

Thank you,

Simon Ren-MSFT 40,346 Reputation points Microsoft External Staff

2021-05-31T02:46:03.843+00:00

Hi,

Thanks for posting in Microsoft MECM Q&A forum.

Please refer to:
Configuring 802.1x Authentication for Windows Deployment
Native 802.1x Support for Enterprise Operating System Deployments
802.1X WITH WINDOWS DEPLOYMENT SERVICE

Best regards,
Simon

If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
https://learn.microsoft.com/en-us/answers/articles/67444/email-notifications.html
Chrissy Willow Rothgeb 6 Reputation points

2021-08-30T00:13:27.117+00:00

I'm experiencing the same problem. I'd posted in the community forum, but was directed here.

As far as I can tell, this is a similar issue to the one noted previously in WinPE versions 1607 and 1703 (https://support.microsoft.com/en-us/topic/windows-pe-network-winpe-dot3svc-optional-component-doesn-t-work-in-windows-10-version-1607-or-version-1703-8f392d99-c248-6148-39ab-6dc05fd49622)

I have verified that WinPE-Dot3Svc-Package~... was indeed installed, that dot3cfg.dll exists in the system, and that the interface is recognized, has an active IP, and is otherwise working.

This is the case for WinPE builds 10.0.20348 and 10.0.22000 for AMD64. I have not tried other architectures.

I'm glad to hear that this is not just me and hope that this can be resolved in a patch or future version of WinPE.
Chrissy Willow Rothgeb 6 Reputation points

2021-08-30T00:16:12.12+00:00

This appears to be a problem with the dot3svc service itself, not with how 802.1x support is being utilized. The service simply does not start. This problem existed in WinPE 1607 and 1703 and appears to have returned in the latest two builds of WinPE.

6 answers

Your answer

Simon Ren-MSFT 40,346 Reputation points Microsoft External Staff

2021-05-31T02:46:03.843+00:00

Hi,

Thanks for posting in Microsoft MECM Q&A forum.

Please refer to:
Configuring 802.1x Authentication for Windows Deployment
Native 802.1x Support for Enterprise Operating System Deployments
802.1X WITH WINDOWS DEPLOYMENT SERVICE

Best regards,
Simon

If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
https://learn.microsoft.com/en-us/answers/articles/67444/email-notifications.html
Chrissy Willow Rothgeb 6 Reputation points

2021-08-30T00:13:27.117+00:00

I'm experiencing the same problem. I'd posted in the community forum, but was directed here.

As far as I can tell, this is a similar issue to the one noted previously in WinPE versions 1607 and 1703 (https://support.microsoft.com/en-us/topic/windows-pe-network-winpe-dot3svc-optional-component-doesn-t-work-in-windows-10-version-1607-or-version-1703-8f392d99-c248-6148-39ab-6dc05fd49622)

I have verified that WinPE-Dot3Svc-Package~... was indeed installed, that dot3cfg.dll exists in the system, and that the interface is recognized, has an active IP, and is otherwise working.

This is the case for WinPE builds 10.0.20348 and 10.0.22000 for AMD64. I have not tried other architectures.

I'm glad to hear that this is not just me and hope that this can be resolved in a patch or future version of WinPE.
Chrissy Willow Rothgeb 6 Reputation points

2021-08-30T00:16:12.12+00:00

This appears to be a problem with the dot3svc service itself, not with how 802.1x support is being utilized. The service simply does not start. This problem existed in WinPE 1607 and 1703 and appears to have returned in the latest two builds of WinPE.

Answer 1

Hello,
We are experiencing the same issue also.
Upgraded our infrastructure to 2107, upgraded ADK to 10.0.22000, creating a new bootimage and a bootmedia with our 8021.x customizations :
Dot3svc service does not work, Wired Autoconfig tries to start but never does.
On a different forum, someone proposed to copy the "mobilenetworking.dll" from a Windows 11 image into the winpe wim, which we did.
This solved the issue with the "Wired Autoconfig" not starting, but still the authentication failed.
I think there might be some more things not working and preventing the authentication to happen.
On the Radius side, there was no request showing the computer had tried to send the proper authentication.

I will open a ticket to MS regarding this issue, hopefully if I get answers I will share them here

Balazot, William 11 Reputation points

2021-12-02T18:03:38.137+00:00

Forgot to say that we rolled back the ADK 10.0.22000 to the version 2004, refreshed the bootimages, recreated a new bootimage and bootmedia, and it works like a charm again.

Answer 2

Merins, Daniel 6

Cool News!

from https://www.reddit.com/r/SCCM/comments/px4uvl/dot3svc_cannot_start_in_winpe_100220001_sccm/ I get the info about missing mobilenetworking.dll in ADK.

I extract the mobilenetworking.dll from Windows 11 ISO, mount the boot.wim, copy the file in C:\windows\system32\ & unmount the image.

Now can the dot3svc service be started!

Simon Ren-MSFT 40,346 Reputation points Microsoft External Staff

2022-01-21T01:30:17.543+00:00

Hi,

Thank you very much for sharing! I think maybe other peoples with the same needs will benefit from it.

Have a nice day!

Best regards,
Simon

Answer 3

Shawn lockner 6

in additions to copying the mobilenetworking.dll

I also had to mount the WIM and then load the system reg hive

and create the following key

ControlSet001\Services\EAPHost /t REG_DWORD /v UseLegacyTlsStack /d 1

this resolved the failed authorization issues

Answer 4

Colin Ford 1,026

Have you tried following this https://www.asquaredozen.com/2018/07/29/configuring-802-1x-authentication-for-windows-deployment/

Answer 5

Merins, Daniel 6

I get the same error:

netsh
The following helper DLL cannot be loaded: DOT3CFG.DLL

In the Task Manager I see that the dot3svc service ist starting...

Do you have any news about it?

Share via

WinPE Wired Autoconfig 802.1x

6 answers

Your answer