topic I'm having this same problem in Network Access Control

Windows 10 Wireless issues ISE 2.0

michaellperrin — Mon, 11 Mar 2019 06:50:20 GMT

Has anyone else seen issues with windows 10 PC's connecting to wireless network using ISE?

In the radius logs the machine is getting authenticated but the PC doesn't prompt for username/password.

The config works for Windows 7. User clicks on the SSID it prompts for username and pass and they are granted access.

This doesn't seem to be working with users on Windows10

Hi there, I have a couple of

nspasov — Sun, 05 Jun 2016 07:03:25 GMT

Hi there, I have a couple of questions:

- Is the supplicant configured via GP or some other dynamic method

- What type of authentication are you using? (PEAP, EAP-TLS, etc)

Thank you for rating helpful posts!

Supplicant is just standard

michaellperrin — Mon, 06 Jun 2016 02:48:42 GMT

Supplicant is just standard windows wireless.

Using PEAP

Do you any patches installed

jrabinow — Mon, 06 Jun 2016 04:00:54 GMT

Do you any patches installed with 2.0? The following fix was made in patch 1 of 2.0

CSCuw88770: ISE 2.0 PEAP TLS 1.2 wireless auth failing with Android 6 and Win 10

No patches have been applied.

michaellperrin — Mon, 06 Jun 2016 12:17:59 GMT

No patches have been applied. I will try that this morning

Can I go right to patch2? ise-patchbundle-2.0.0.306-Patch2-164765.SPA.x86_64.tar.gz

Or should I go patch 1 then patch 2?

Sure. You can go straight to

jrabinow — Tue, 07 Jun 2016 14:28:06 GMT

Sure. You can go straight to patch 2 (or even patch 3 which is available) and no need to install one at a time. All patches are cumulative and include contents of the previous patch

So the patch seemed to work.

michaellperrin — Thu, 09 Jun 2016 17:17:15 GMT

So the patch seemed to work. At least I'm getting further.

However seem to now having cert issues. When I connect to the SSID It says The the SSID in this location, it may be a different network with the same name.

If I setup the wireless manually and choose to trust the CA that signed the ISE cert I no longer get that message. Do I really need to manually setup the connection?

Also we have a Machine and user authorization policy. As long as the machine auth happens the computer will connect even if the user does not authenticate.

I'm having this same problem

jeffkelso — Tue, 01 Nov 2016 14:26:57 GMT

I'm having this same problem with Windows 10. We are using self signed ISE certs and they are installed and trusted on the local machine. Did you find a solution to this?

You have to manually created

michaellperrin — Tue, 01 Nov 2016 14:29:30 GMT

You have to manually created the wireless network and choose the cert, then push it through config through GPO.

How about the BYOD users who

Eric V. Zarghami — Fri, 13 Jan 2017 20:19:17 GMT

How about the BYOD users who are not on the domain?