Wi-Fi issues on endpoints after creating Wi-Fi policy
Hello everyone, We started using Autopilot a while ago. I wanted to optimize this "procedure" by adding a configuration profile with the use of the Wi-Fi template in Intune. A few weeks later, I started to notice that some autopilot devices were having Wi-Fi issues. The Wi-Fi was suddenly not findable anymore, and they lost the internet connection. Eventually I found out that multiple services where disabled, and I could not enable them by hand. So I found a couple regkey entries online named "WinHTTP_Web_Proxy_Auto-Discovery_Service" that fixed this issue temporarely. Sadky the issue came back after a few days. I later noticed that this issue might have something to do with the Wi-Fi configuration profile I made a while ago. Since these devices could not connect with the Wi-Fi network that I specified in that profile, so I quickly deleted that profile in the hopes of it fixing this issue. Sadly it did not, and we are stuck with laptops losing their entire Wi-Fi connection/appereance. Is there any way to fix this, does the Wi-Fi profile make changes to the regkey, or does it create a certificate on the computer that has to be deleted? I checked event viewer and saw that a lot of services weren't able to run, which is probably caused by the Wi-Fi configuration profile (see attachments for event viewer errors).
Intune enterprise wi-fi profile for windows - clients stuck on pending
Hi everyone, I opened a ticket with Microsoft but maybe someone already encountered this and can help. We deployed a .1x wireless network and until last Thursday it worked perfectly. here is the setup we use: On Thursday I renamed all the profiles associated with the wireless network to reflect for which clients this profile is for and what it does. Apparently this resulted in deleting the wireless profile from the clients... I decided to recreate the policies of the trusted root certificate profile, PKCS certificate profile and the wireless profile but it still didn't work. The picture above is another wireless network I deployed to test whether the problem is with the wireless name but the new profile also didn't deploy. I also deployed a basic network which deployed successfully. Worth noting but maybe unrelated, We blocked the public store and I checked the policy to make sure it was deployed successfully. any ideas? Rahamim.Laptops using both LAN and WIFI
Hi everyone, We deployed WCM policies to favor ethernet over Wi-Fi and to use soft disconnect to make the transfer more fluent. Our laptops are connecting to ethernet via a USB replicator (some using USB-C and others with HP 3005 models.). Has anyone encountered a situation where even after this deployment, the laptops still use both network adapters (Answering to ping on both LAN and Wi-Fi)? Thanks in advance, Rahamim.
Intune EAP/TLS Wi-Fi Profile Only Applied to First Wi-Fi NIC?
I'm working on a problem unrelated to the subject of this post related to RADIUS authentication with Cisco ISE and needed to use an external network adapter capable of monitor/promiscuous mode to catch some traffic in Wireshark. I have Intune set up to push down certificate and Wi-Fi profiles which normally work fine. The device goes out to NDES to get its cert then connects to our Wi-Fi using the EAP/TLS Wi-Fi profile pushed down from Intune. I noticed that when I hook up my external Wi-Fi adapter, the Intune Wi-Fi profile doesn't seem to work on it. Instead of connecting with EAP/TLS, it asks for username/password. This makes me think that Intune isn't applying or associating the Wi-Fi profile with this external NIC. Has anyone else encountered this? Is it possible Intune is only assigning the Wi-Fi profile to the first NIC it finds or the NIC that was in use when the device was enrolled? Even if I disable the built-in NIC in device manager, it still won't use the Wi-Fi profile on the external NIC. So weird. I'm doing this testing on a Surface and have disabled the internal Wi-Fi NIC in UEFI/BIOS and am currently re-imaging the device with just the external adapter connected to see if that makes any difference. thanks, Dan
