Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

In joining a new company, I have inherited it's history.

I find that the User and Computer Object property lastLogonTimeStamp is not available. I have checked that the AD Schema version is 2003 R2, and that the domain attribute ms-DS-Logon-Time-Sync-Interval was "" (which should default to 14, to which I've now explicitly set.)

If relevant, the first DC is a SBS server. (This is my first time dealing with SBS, and so far I'm tempted to set it aflame.)

Checking random users and computers, I see no LLTS. How can I force this property into existence?

This is the Schema entry for CN=ms-DS-Logon-Time-Sync-Interval:

ms-DS-Logon-Time-Sync-Interval Schema

share|improve this question
What is the domain functional level? – uSlackr May 3 '12 at 21:01
up vote 2 down vote accepted

There are several possible causes. The likely cause is that your domain functional level is not yet set to windows 2003. Once that's been established check out this KB article:

share|improve this answer
Ugh, I'm a dumbass. Thank you. – gWaldo May 4 '12 at 12:22
It's been so long since its really mattered, its easy to forget about functional levels – uSlackr May 4 '12 at 17:01

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.