The computer object's password in the domain is changed every 30 days. If the account password expires and is changed while the machine is boxed up, its local password (a.k.a. local secret) no longer matchs up with the domain's. So the answer is, depends on how close you are to the password...
I've had the following happen to me a couple times: there is a member server (NT or 2k) sitting in a box for a couple weeks, waiting to be shipped off site; when it reaches its destination and is powered on, its access to the domain (mixed-mode) is denied and it has to be removed and added back...
I'm watching a co-working rip his hair out testing the ArcServe Full Disaster Recovery Option and it seems like he's having a lot of strange issues (corrupt databases, missing folders, etc.). Is anyone else using this method?
Thanks
Odd name resolution problem
I have an NT4 Server on the end of a 56k WAN line whose name will not resovle. This is a mixed mode domain using DNS and WINS (we also have Active Directory but are only using it for Exchange, we don’t do anything else with it as far as I know).
Now for the weird...
Hello,
My company is working on a new disaster recovery plan and is looking into options involving data mirroring (NSI Software's Double-Take). I have been reading through some of NSI's whitepapers and I am curious if anyone has any experience using Double-Take with Exchange2000.
Thanks
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.