restoring system state after with backup over 60 days old

[Tony Burke]

I am tearing my hair out still, I have a 90 day old backup of a domain
controller. it is the only domain controller on my network. If i try to
restore it skips some files because they are over 60 days old I then get a
lsass error and i am locked out

can anyone tell me how i actually increase the tombstone so that the server
will accept the old backup

If I use asiedit I cannot find the enterprise-wide ds config object. I can
only see the domain

I am really in a pickle here

Tony

 

[\Richard McCall [MSFT]\]

What service pack was the back taken on

 

[Herb Martin]

I am tearing my hair out still, I have a 90 day old backup of a domain
controller. it is the only domain controller on my network. If i try to
restore it skips some files because they are over 60 days old I then get a
lsass error and i am locked out

I didn't know that actually had an interlock for 60 days -- this restriction
is really
based on the "tombstone expiration" which DEFAULTS to 60 days.

I cannot imagine what "files" would be skipped. What about installing onto
a fresh
SERVER (not a DC).

can anyone tell me how i actually increase the tombstone so that the server
will accept the old backup

I would just try a NEW Server (not a DC) and if it works you just replace
the
current DC.

 

[Tony Burke]

Service pack 1 im afraid

Tony

 

[\Richard McCall [MSFT]\]

The machine you restored the system state to what service pack was it. If it
was not the same sp as the system state I would try using the same sp level.