Windows 10: How to stop Windows 10 Enterprise from using logged in user's credentials for wireless

We're running Windows 10 Enterprise, domain joined, in a large enterprise with a managed network using WPA2-Enterprise.When joining a wireless network, how do I stop Windows from attempting to authenticate to the wireless network using the logged in user's credentials, and force it to prompt for username/password to the wireless network?I try all of this without success:netsh wlan profiles delete <profilename>Choose "forget this network"I check using netsh wlan profiles and there is no local or GPO profile listed. However, upon connecting to the network again Windows again does not promp

:)

 

Windows users can't log in

The DNS server has collapsed. However, users cannot log into the domain?

I thought as long as they log in once, their credentials were saved locally into the computer?

 

Detailed logs for wireless network in Win 10 Enterprise

We have various Windows 10 Enterprise clients (domain managed) that have issues with our wireless network (large commercial enterprise network using WPA2-Enterprise - not a home router).

The network is managed by another team. I need to prove malfunctions to that team.

The user-facing error in Win 10 is not near detailed enough for us to prove the issue, e.g. "Can't connect to this network."

Where can I find very detailed logs for wireless - including auth, AP association/roaming by the client, signal strength, DHCP failures (e.g. timeouts when the DHCP server does not provide offer or ack, or sends a nak), and everything else?

 

Windows Network Credentials

Hi Keith,

We suggest that you disable Credential Manager before mapping your Drives. Please follow these steps to disable Credential Manager:

• In the search box type “Services”
• Right click on “Services” and select “Run as Administrator”
• In the Services Window, look for Credential Manager Service and click “Stop”.
• Restart the computer and go back the Credential Manager Service and set it to “Automatic”.
• Restart the computer again.

Please keep us updated if you were able to map your drives.