timbo343 Posted March 1, 2017 Posted March 1, 2017 Since moving over to windows 10, we are seeing a strange one where students are trying to change their password however when they do, it says "Password cannot be changed at this time". We never got this when we were running Windows 7 and only has started to happen when running windows 10. A quick reboot of the machine and the user can login with their newly created password. This doesn't happen on all machines, again just the random few and again a reboot sorts the issue. Is this another "unknown" issue that Windows 10 has?
Cazale Posted March 1, 2017 Posted March 1, 2017 I believe this happens when it detects a network connection but can't reach the Microsoft servers (maybe because of the content filter and/or proxy?), it's their crappy attempt to force you to sign up for a Microsoft Account, and it is very annoying! Not sure how this affects domain PCs, but on non-domain W10 boxes you can cure it by disconnecting the network, then adding the user/changing password/whatever, and reconnecting the network. I'd imagine it would throw an error on a domain PC? (we're still W7 here, thankfully).
newpersn Posted March 1, 2017 Posted March 1, 2017 Since moving over to windows 10, we are seeing a strange one where students are trying to change their password however when they do, it says "Password cannot be changed at this time". We never got this when we were running Windows 7 and only has started to happen when running windows 10. A quick reboot of the machine and the user can login with their newly created password. This doesn't happen on all machines, again just the random few and again a reboot sorts the issue. Is this another "unknown" issue that Windows 10 has? We get that aswell. What OS is your servers? We are on 2008R2 but looking to upgrade to 2012 or 2016 during the summer.
timbo343 Posted March 1, 2017 Author Posted March 1, 2017 We get that aswell. What OS is your servers? We are on 2008R2 but looking to upgrade to 2012 or 2016 during the summer. I wonder if thats where the problem lies, i wondsr if the machines that are having the issue are connecting to the 2008r2 DCs instead of the 2012r2 ones. We are split at the moment on a 2008R2 domain running 2008r2 and 2012r2 servers.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now