Cluster updates the lastLogonTimeStamp when it brings a clustered network name resource online. Once online, it caches the authentication token. Therefore, a clustered network named resource working in production for months will never update the lastLogonTimeStamp. This appears as a stale computer account to the AD administrator. Being a good citizen, the AD administrator deletes the stale computer account that has not logged on in months. Oops.
There are few things that you can do to avoid this situation.
Mike "Four out of Five AD admins recommend ASKDS" Stephens
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.