Wow.. Why did it shift downward from 2003 to 2003R2? -ASB: http://XeeSM.com/AndrewBaker
On Mon, Aug 2, 2010 at 2:24 PM, Brian Desmond <[email protected]>wrote: > 60 is the default for 2000 and 2003 R2 forests, 180 for 2003, 2008, 2008 R2 > forests. Note this is the original OS version of the first DC not the > current FFL. > > There are scenarios you'd change this but they're fairly vertical. > > Thanks, > Brian Desmond > [email protected] > > c - 312.731.3132 > > > -----Original Message----- > From: David Lum [mailto:[email protected]] > Sent: Monday, August 02, 2010 9:30 AM > To: NT System Admin Issues > Subject: RE: 2008 DC being offline > > I stand corrected, maybe it was 66 days. As a general rule I don't change > defaults unless I have a compelling reason to do so, and I can't think of > one here. > > -----Original Message----- > From: Brian Desmond [mailto:[email protected]] > Sent: Friday, July 30, 2010 4:07 PM > To: NT System Admin Issues > Subject: RE: 2008 DC being offline > > 30 days not unless you tinkered with some tombstone lifetime settings which > I don't know why you would lower it... > > Thanks, > Brian Desmond > [email protected] > > c - 312.731.3132 > > > > -----Original Message----- > From: David Lum [mailto:[email protected]] > Sent: Wednesday, July 28, 2010 2:55 PM > To: NT System Admin Issues > Subject: RE: 2008 DC being offline > > Past 30 days offline it will complain - at least 2003 servers do, but I > think it's also related to some AD archive or backup time setting....I ran > into something about 30 days when I restored a DC from a backup that was 36 > days old. > > Minor in the scheme of things, just something to keep in mind. > > ...Then again, maybe that was of no help... > > David Lum // SYSTEMS ENGINEER > NORTHWEST EVALUATION ASSOCIATION > (Desk) 971.222.1025 // (Cell) 503.267.9764 > > > > -----Original Message----- > From: [email protected] [mailto:[email protected]] > Sent: Wednesday, July 28, 2010 11:56 AM > To: NT System Admin Issues > Subject: 2008 DC being offline > > Hello, > A 2008 DC (lets call it Server-F) we have at another site has been offline > for 6 weeks. We powered it down because the building was undergoing > construction, and the building was effectively CLOSED for those 6 weeks. > Construction is done and I'm ready to bring the server back online. > > Is there a problem with just turning Server-F on and letting it re-sync > with active directory even though its been offline for 6 weeks? or... > would I be better off bringing Server-F up WITHOUT a network cable > connected, run dcpromo /forceremoval on it... then remove any references to > the Server-F from my other DCs, and eventually re-promote server F back as > a DC? > > Thoughts? > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
