hehe, yep I've seen that (the difference of the Schema.ini
files; i.e. missing entry for the tombstonelifetime property) but didn't think
too much of it because for now I've only had to handle upgrading from Win2000 or
2003 to R2 where the Schema.ini doesn't play a role. It is "only" used to
populate a blank schema at the time that you create a new AD forest - and yes,
this means that your tombstone lifetime wouln't match that of other Win2003
forests that were created from a DC that had SP1 applied to
it...
I agree, not very nice, but easily fixed as you describe.
Personally, I don't think too much of the fact that the tombstonelifetime was
increased to 180 days in SP1 anyways. This was done to avoid issues for
companies with a badly managed AD - I would generally much prefer to adjust
the value to what is appropriate for a company's backup & recovery strategy.
And this usually doesn't mean that you need to keep the "garbage" in your AD for
1/2 a year...
Granted, it's the inconsistency here with which MSFT has
done the update of the schema.ini files which is not so nice - but the rules are
pretty clear on how tombstone lifetime can be evaluated by an admin: if the
attribute on the Directory Services object (tombstoneLifetime
ð
CN=Directory Service,CN=Windows NT,CN=Services,CN=Configuration,DC=<MyRootDomain>
/Guido
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of joe
Sent: Monday, July 24, 2006 1:50 AM
To: ActiveDir@mail.activedir.org
Subject: [ActiveDir] Have you built an R2 Forest?
If so... you may want to peek at
entitled "R2 tombstoneLifetime boo
boo"
