Control The Amount Of Cached Logons

Published on Thursday, April 26, 2012 in

One of my colleagues had a project where they though it would be a good idea to restrict the amount of cached logons to 1. This would ensure only the last logged on user (the owner) would be able to use the computer off the network. This way the credentials of privileged users such as helpdesk employees wouldn’t be cached.

However when they set the setting to 1 it seemed like even the user itself couldn’t log on any more. Well here is some explanation: http://blogs.technet.com/b/instan/archive/2011/12/06/cached-logons-and-cachedlogonscount.aspx

Basically there’s also other processes filling up slots of the cached logons, and it’s hard to take these into account. So I’d say it was never meant to be set THAT restrictive.

Related Posts

2 Response to Control The Amount Of Cached Logons

15 February, 2013 13:32


Very nice article.

Do you write product reviews for AD software?



18 February, 2013 13:38

Nope, I haven't got any experience writing such reviews...

Add Your Comment