Advice for long term disconnected domain controller
Posted on 2008-06-18
We have a research vessel which can go out to sea for upto 3 or 4 months at a time (sometimes upto 6 months before returning to our broadband connection). We have just implimented group policy and locked down our desktop machines, one of the advantages with this is that we have taken local admin rights from our users. When they used to go on "the ship" they would take their machines out the domain and put in the ships workgroup, this is no longer an option for them! We are thinking about putting a domain controller on the ship to solve this problem and in turn make our lives easier (ie no repromoting!). How would a Windows 2003 R2 domain controller feel about this, I have read a couple of MS articles that say it should be ok, providing we don't go over 180days (tombstone life). Any advice or tips welcome.