Timeline for Connecting to SQL Server using cached credentials
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 5, 2012 at 13:28 | comment | added | mrdenny | No problem, glad we got the problem resolved. | |
| Jun 5, 2012 at 13:26 | comment | added | Jirka Hanika | Thank you for the extra info. We will go the local account way and maybe even buy your book :-) | |
| Jun 5, 2012 at 13:07 | comment | added | mrdenny | Correct, when services log on the credentials aren't cached, and when services start they don't use cached credentials. | |
| Jun 4, 2012 at 20:30 | comment | added | Jirka Hanika | I get that. But you are saying that when AD is online, the service can log on, but no credentials will be cached for later use, because this particular log on is not interactive. Correct? | |
| Jun 4, 2012 at 20:26 | comment | added | mrdenny | @JirkaHanika No, when the service tries to start it'll throw an error message and the service won't start. When verifying if the account can login it won't be able to as there's no domain controller to verify against. | |
| Jun 4, 2012 at 19:57 | vote | accept | Jirka Hanika | ||
| Jun 4, 2012 at 19:36 | comment | added | Jirka Hanika | This was the key bit of info I was missing. Can you please confirm my understanding? Suppose that I create a domain account that is allowed to log on interactively. Then credential caching will happen as configured when this user logs on as a normal user; but if I try to use the same account as a service logon account, such a service startup or database authentication will never result in caching the credentials in registry. Is that correct? | |
| Jun 4, 2012 at 18:44 | history | answered | mrdenny | CC BY-SA 3.0 |