Tunnel EAP-Teap

[oumar]

Hello Guys,

I am somehow at a lost here. We have successfully implement Tunnel Teap into a test machine and we want to deploy it into our environment. I have downloaded the .xml wifi profile for the device and since EAP-TEAP is not yet integrated in the configuration policy in Intune, I have uploaded the xml file. I am running into a migration error.

 I am no sure where to go from there. 

Did anyone implemented TEAP configuration. 

[#2]

Hi, @oumar 

Since there is a confirmed bug in wired TEAP configuration and it should be solved in Q4 Intune release, I think that Wifi could be a very same story...

[#3]

@jdvorskycz do you have a public link for this bug at all? We've had massive issues and had to switch to XML for wireless (which we got working) but haven't been able to get it functioning on wired. Had a support ticket open with Microsoft for 3 months, but never got notified that this was a known issue.

[#4]

Hello @ jdvorskycz, I was able to solve my issue. It was because I had the wrong SSID in my configuration. What issues are you having?
For the wired Teap, I have used a Custom OMA-URI Settings to deployed it.

[#5]

Unfortunately no, support closed the ticket with the fact that it was acknowledged by the product group as a bug and will be fixed during Q4. It was manifested by the fact that the root certificate hash (the root certificate with which the ISE server is signed) was not registered in the TEAP configuration.

[#6]

@tgardiner_ @jdvorskycz This sounds like the same issue I am facing. I have also had a ticket open with Microsoft for over three months and they have not said this is a known issue. When trying to deploy a Wired Network profile with TTLS and root certs, there is an error syncing the profile. When I remove the root certs, then it is successful (most of the time). Please provide a link for this bug so I can confirm this is the issue we are facing.  Thanks!

[#7]

@jdvorskycz 

Yep that was exactly the behaviour we experienced. Now got it going with XML.

Thanks all!

[#8]

You can try to mention our TrackingID#2403181420002543