Hey everyone! We're in the middle of upgrading our systems to Windows 11, but we're running into a frustrating issue where the wired network profile gets lost post-upgrade. This profile is critical because it has the authentication settings for 802.1x using EAP-TLS, which we push through Group Policy. When the profile is gone, devices can't connect to the network, which means they can't pull the necessary Group Policies and just end up stuck. Has anyone else experienced this? Are there any solutions or workarounds that might help?
2 Answers
I actually faced a similar problem with earlier upgrades, but surprisingly not from Windows 10 to 11. In the past, we managed to fix it by running an extra script that uses the postOOBE parameter to enforce an authentication profile during the upgrade. It worked out pretty well!
Yes, we encountered the same issue too! We resolved it by implementing a script that runs during the upgrade to import the 802.1x configuration from the previous installation. I originally found it on Reddit but misplaced the link. Here’s a snippet:
```powershell
for ($i = 1; $i -le 3; $i++) {
Write-Output "Iteration ${i}: Resetting Migration Status..."
New-ItemProperty -Path 'HKLM:SOFTWAREMicrosoftdot3svcMigrationData' -Name 'dot3svcMigrationDone' -Value "0" -PropertyType DWORD -Force -ErrorAction SilentlyContinue
Write-Output "Iteration ${i}: Restarting service dot3svc..."
Restart-Service -Name dot3svc -ErrorAction SilentlyContinue
Write-Output "Waiting for 30 seconds..."
Start-Sleep -Seconds 30
}
```
This helped us ensure the profile was imported correctly as soon as the OS was installed. Does anyone know how to time the script to run perfectly during the upgrade? We want to streamline using Windows Update for the installation to avoid reimaging all our devices.
I’ve been trying to get the timing right too. Do you have a method in mind for when to trigger that script during the OS upgrade?