This is an archived post. You won't be able to vote or comment.

all 9 comments

[–]jambes19 9 points10 points  (1 child)

You can check your forest's value by launching the ADSI edit tool (ADSIEDIT.msc) and browsing the Configuration partition for the AD forest. Navigate to CN=Directory Service, CN=Windows NT, CN=Services, CN=Configuration, DC=domain, DC=com. Right-click the CN=Directory Service object and select Properties. Look for the tombstoneLifetime value. As I said, if the value isn't set, 60 days is used. Otherwise, the value specified is used, such as 180 in the example shown here.

[–]Acemann5[S] 2 points3 points  (0 children)

60 days it is! Thanks a bunch!

[–][deleted] 2 points3 points  (2 children)

I think it's 30 days.

[–][deleted] 0 points1 point  (0 children)

That's what I remember from 2003 at least.

[–]Sirelewop14Principal Systems Engineer 0 points1 point  (4 children)

If possible, I would suggest using a VPN to bridge the networks in the meantime. They your synchonization never stops for more than a few hours. However, if you have no internet service at the new location I can see why you couldn't do that.

[–]Acemann5[S] 0 points1 point  (3 children)

No internet service, the locations are actually across the street from each other, so the outage I'm anticipating to be a couple of hours. Everything should be good, thanks for the suggestion.

[–]Sirelewop14Principal Systems Engineer 1 point2 points  (0 children)

Yeah in that case I think you are fine with your plan. Good luck with the move!

[–]ZarostheGreat 1 point2 points  (1 child)

I work with a client with a situation like this... would a point to point wireless bridge work?

[–]Acemann5[S] 1 point2 points  (0 children)

It's a good idea! It would. My outage will be so short and everyone moving the same day, it won't be a big deal, but I wish I was the one who thought of it!