Re: Default tombstone lifetime

Is this SP1 or R2 Media? Please triple check and verify what it is, where it came from, and whether or not schema.ini has the tombstonelifetime value set.

If it doesn't, please document the media (VLK, MSDN, what ever) where it came from, the date/time stamp on schema.ini.


joe

--
Joe Richards Microsoft MVP Windows Server Directory Services
Author of O'Reilly Active Directory Third Edition
www.joeware.net


---O'Reilly Active Directory Third Edition now available---

http://www.joeware.net/win/ad3e.htm


Jorge Silva wrote:
InLine

180 days is configured when the first DC in the forest is W2K3 SP1. everything lower than that or upgraded to SP1 is 60 days.
ARE you sure the install media is sliptstreamed WITH SP1 and it is not just W2K3 RTM?


Joe is correct!! I'm wrong???

Funny, because I did some testing, and as David mentioned, even if you install W2k3 SP1 the tombstoneLifetime attribute is set to "<not set>".

I also have the Idea that when tombstoneLifetime attribute is set to "<not set>" this means 60 days. But I never notice that if we installed W2K3 SP1 that the tombstoneLifetime attribute is set to "<not set>", I'm still looking for some explanation/article for this.




.

Relevant Pages

  • Re: Default tombstone lifetime
    ... It obviously points out a process flaw that we need to help Microsoft acknowledge so they can address it so it doesn't happen again with say Longhorn R2. ... Just to clarify, you mentioned in your blog post that "some people aren't seeing this", referring to the TLS being set to 180 if using Windows 2003 SP1. ... If you windiff the two involved version of the file you will see that it appears that someone took a file from 11/23 and updated the object version of the schema object in the file and then 7 days later on 11/30 someone updated the file from 11/23 with the new tombstonelifetime. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Default tombstone lifetime
    ... If you windiff the two involved version of the file you will see that it appears that someone took a file from 11/23 and updated the object version of the schema object in the file and then 7 days later on 11/30 someone updated the file from 11/23 with the new tombstonelifetime. ... Please verify that any Gold SP1 media you actually received from Microsoft or built directly from a Gold ISO has the proper schema.ini file. ... Joe says that the documentation is wrong and that it actually does set that particular attribute to 180 days if you create a forest on a SP1 machine, but that is not what I am seeing. ... In an Forest were you installed the 1st DC a Windows Server 2003 SP1he new default tombstone-lifetime is tripled to 180 days. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Migration/Install SBS 2003 & Win Server 2003 Service Pack Ques
    ... If the media is SP1, you are in much better shape. ... I don't have any RTM installs left, and only a couple SP1, but if you can't ... before installing SP2, although it is possible to substitute Exchange SP2 ...
    (microsoft.public.windows.server.sbs)
  • RE: Service Pack 1 License Key Encryption Problem
    ... I know that log file gets generated with SP2 when you create a slip-stream ... The media changed from RTM media to slip-stream media after SP1 shipped. ...
    (microsoft.public.windowsxp.setup_deployment)
  • Re: Default tombstone lifetime
    ... Cool thanks David. ... Just to clarify, you mentioned in your blog post that "some people aren't seeing this", referring to the TLS being set to 180 if using Windows 2003 SP1. ... If you windiff the two involved version of the file you will see that it appears that someone took a file from 11/23 and updated the object version of the schema object in the file and then 7 days later on 11/30 someone updated the file from 11/23 with the new tombstonelifetime. ...
    (microsoft.public.windows.server.active_directory)