Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Thursday, January 12, 2017 9:15 PM
Hello everyone,
I have a problem with the credential manager in Windows 10 Enterprise Build 14393 (1607) on numerous clients. For some reason it stores passwords only with a persistence of the current session. Whenever a user logs off and on again, the stored credentials (infact the hole entry, not only the password) have vanished. In the credentail details it says "persistence: logon session" (never seen before). I am not using advanced technics like credential guard. Also we doesn't notice this with the previous builds (10240, 10585).
I have no idea on how to change it back to "enterprise". Any advise?
Thanks for any answer in advance!
Best regards!
All replies (6)
Friday, January 13, 2017 2:45 AM
Hi,
Let’s try the following method to see the result:
Go to Credential Manager, look for your network storage device under windows credential and open it. Then select Edit. Replace the domain name in front of your user name, Save.
Log off from you Windows account and then log in again. Windows will again say it cannot connect network drive. Open Credential Manager again and you will notice that your device is not there under windows credential.
Now connect your device again manually. Then in Credential Manager click "Add a Windows Credential": enter device name as internet/network address, user name (without domain name) and password. Save.
Have a try please.
Regards
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Friday, January 13, 2017 2:46 AM
In fact, smart as you, have found out the key point of problem.
The correct value for Persistence parameter is Enterprise. There is no way to change Persistence in Credential Manager. You will need to find local settings that prevent credentials from being saved correctly.
Check local/domain security policy settings applied to affected computer and user account. Verify if these settings affect credential persistence by excluding computer from domain or setting all policies to default.
There is similar case can be regarded as a reference, have a look please.
Try to hange the authentication level to “Send LM & NTLM - use NTLMv2 session security if negotiated”
Regards
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Monday, January 30, 2017 8:37 PM
Thanks for your reply! I was testing this for some days but came to the conclusion that this seems not to be my original problem.
Here is the original reason for my post: I have some sharepoint sites with document libraries on it. When I open such a document library in the Windows file explorer, I get asked for my username and password. Ok. But even if I choose to rememer my credentials, the site keeps asking for the them after every logon. (Which brought me to the credential manager thing) In fact, the credential manager stores all information very fine, except these for users of my domain (e.g. user "test" gets stored with persistence Enterprise, user "mydom\test" gets stored with persistence logon session).
Now, after some days of testing, I noticed that I have this way of authentication only when I use the file explorer to access the ressources (once after every reboot/login). If I use a web browser (tested IE 11 / Edge) no manual authentication is required, so I think web browsers use some kind of advanced authentication technics like NLTM or Kerberos.
Is there a way to force the file explorer to use the same level of authentication? Maybe only for selected ressources?
Best regards!
Tuesday, February 7, 2017 7:43 AM
Sorry for late reply.
To my knowledge, there is no way to force the file explorer to use the same level of authentication now.
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Thursday, February 9, 2017 7:49 AM
Users reported this to work with Windows 7. So is this some kind of a known bug with Windows 10?
Thursday, February 16, 2017 7:52 AM
Compared with Windows 7, Windows 10 makes more progress on security, it might not be a bug, just by design.
You could feedback to Microsoft via Feedback Hub app.
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].