Hi
In A domain environment when i rest a user password from active directory users and computers he is unable to login to Windows with new password. He is configured to login through wifi And we are using single sign on in the wifi settings. This issue is only affecting few users. connection to company wifi network is authenticated through 802.1x. so we manualy create a wifi profile for 802.1x .
At the dual login screen the new credentials (we are using active directory credentials for wifi since it's 802.1x) are entered. First it spits an error that unable to connect to wifi. Then windows spits an error of invalid user name or password.
If we enter the old credentials at login in both wifi access and windows access we are able to login to Windows (it logs in with Cached credentials) but I it obviously is unable to connect to wifi network.
The user is a member of wifi group so he has access to wifi and he can access wifi through his iPhone.
Also another observation is that if I login with his Cached credentials and configure a wifi profile /connection using his new (reseted password) password windows spits an error that cannot connect to the network.
So the core issue is that after reseting his password from active directory users and computers he cannot connect to wifi through windows.
The workaround that currently I do is i login with his Cached credentials to Windows and then i use my own credentials to configure wifi connection and ask him to login to Windows using his Cached credentials while he will be using my credentials for wifi access. And for other systems that will be using credentials like email he uses new credentials.
Pretty crude solution.
Any way how to figure out what could go wrong.
Besides i have tried configuring a wifi connection /profile on another users laptop using the affected user credentials I got same error that windows cannot connect you to wifi.
So the real issue is that after resetting the password of the user from aduc he cannot connect to wifi.
Any clue idea?
Windows is latest and updated. We are using Microsoft forefront endpoint protection.
In A domain environment when i rest a user password from active directory users and computers he is unable to login to Windows with new password. He is configured to login through wifi And we are using single sign on in the wifi settings. This issue is only affecting few users. connection to company wifi network is authenticated through 802.1x. so we manualy create a wifi profile for 802.1x .
At the dual login screen the new credentials (we are using active directory credentials for wifi since it's 802.1x) are entered. First it spits an error that unable to connect to wifi. Then windows spits an error of invalid user name or password.
If we enter the old credentials at login in both wifi access and windows access we are able to login to Windows (it logs in with Cached credentials) but I it obviously is unable to connect to wifi network.
The user is a member of wifi group so he has access to wifi and he can access wifi through his iPhone.
Also another observation is that if I login with his Cached credentials and configure a wifi profile /connection using his new (reseted password) password windows spits an error that cannot connect to the network.
So the core issue is that after reseting his password from active directory users and computers he cannot connect to wifi through windows.
The workaround that currently I do is i login with his Cached credentials to Windows and then i use my own credentials to configure wifi connection and ask him to login to Windows using his Cached credentials while he will be using my credentials for wifi access. And for other systems that will be using credentials like email he uses new credentials.
Pretty crude solution.
Any way how to figure out what could go wrong.
Besides i have tried configuring a wifi connection /profile on another users laptop using the affected user credentials I got same error that windows cannot connect you to wifi.
So the real issue is that after resetting the password of the user from aduc he cannot connect to wifi.
Any clue idea?
Windows is latest and updated. We are using Microsoft forefront endpoint protection.