DI
asked on
Windows 10 loses contact with Server 2012 R2 Essentials domain after updates
Hi,
I have a server running Server 2012 R2 Essentials with some Windows 10 Pro clients.
Whenever there are major updates to Windows 10 (the ones that tells you "we have upgraded your PC" at first logon), the PC loses contact with the domain. I can log on due to the cached account, but if I try to access server resources (redirected folders or mapped drives), I am asked to enter the user credentials. This works fine until next reboot of the PC.
Checking "remember the credentals" doesn't help.
I know that the PC has indeed lost the domain connection, because if I try logging on with a new user that hasn't a user profile yet, I am being told that there are no domain controllers available.
The workaround so far has been to uninstall the Essentials Server connector, leave the domain and re-join the domain using the Server connector, but I cannot go on like this everytime a Windows 10 update is released!
Another issue that comes with this, is that it now takes about a minute to create a new folder on a server share, even after a sucessful re-join. The only way I have found to get rid of this problem, is to reinstall the computer! Then everything works perfectly... until the next Windows 10 update!
Any ideas?
I have a server running Server 2012 R2 Essentials with some Windows 10 Pro clients.
Whenever there are major updates to Windows 10 (the ones that tells you "we have upgraded your PC" at first logon), the PC loses contact with the domain. I can log on due to the cached account, but if I try to access server resources (redirected folders or mapped drives), I am asked to enter the user credentials. This works fine until next reboot of the PC.
Checking "remember the credentals" doesn't help.
I know that the PC has indeed lost the domain connection, because if I try logging on with a new user that hasn't a user profile yet, I am being told that there are no domain controllers available.
The workaround so far has been to uninstall the Essentials Server connector, leave the domain and re-join the domain using the Server connector, but I cannot go on like this everytime a Windows 10 update is released!
Another issue that comes with this, is that it now takes about a minute to create a new folder on a server share, even after a sucessful re-join. The only way I have found to get rid of this problem, is to reinstall the computer! Then everything works perfectly... until the next Windows 10 update!
Any ideas?
ASKER
I've found a temporary fix: Open an elevated command prompt and run
DISM /Online /Cleanup-Image /RestoreHealthASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
So far, it seems you found the culprit, but you want to reproduce it again by reinstalling the update.
The cab file can be installed using pkgmgr.exe like this:
The cab file can be installed using pkgmgr.exe like this:
Pkgmgr /ip /m:c:\somefolder\yourcab.сabASKER
Running the command (elevated) gave no results; no visible reaction, and immediate return to the command prompt.
But you modified the path, did you?
ASKER
Yes, I moved the file (all-windows10.0-kb3176935
pkgmgr /ip /m:c:\Install\all-windows10.0-kb3176935-x64_baf9da8bed676d32ffaf22667bfc6f5afc423af0.cabSOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
McKnife,
I set up a VM just as you suggested, and for some reason, I do not get the KB3176935 update from Windows Update anymore. Has it been recalled or superseeded, perhaps?
And installing it manually with the PKGMGR command doesn't work in my VM either. As described earlier, nothing happens.
So I'll conclude that KB3176935 is the reason, and I hope that it will not pop up on my computers again!
Thank you for your assistance!
I set up a VM just as you suggested, and for some reason, I do not get the KB3176935 update from Windows Update anymore. Has it been recalled or superseeded, perhaps?
And installing it manually with the PKGMGR command doesn't work in my VM either. As described earlier, nothing happens.
So I'll conclude that KB3176935 is the reason, and I hope that it will not pop up on my computers again!
Thank you for your assistance!
ASKER
Uninstalling the KB3176935 update has solved the problem on all my PCs, and I have not been able to reproduce the problem, as the update appears to be unavailable now.
Install 1511, join it to your domain, install no additional software, then upgrade to 1607 and test.