Thanks for this detailed info! I don't have the SysAdmin background to fully understand the details, so I apologize if this is a dumb question. I often rely on LastLogon dates to help me determine if computer objects are stale. In my experience, servers tend to report very recent LastLogon dates. I'd say 95% of the production servers belonging to clients I work with report a LastLogon date within 72 hours, with the great majority reporting a date within 24 hours or so. I work with customers of all kinds, from small to giant. I'm confident they aren't really actually logging their servers in so often. Do you think this s4u2Self process explains why many LastLogon dates for normal production Windows Servers remain quite fresh, even for servers that haven't power cycled in months? Or is the process you describe here more of an outlier situation?