More of an NT/AD than an Exchange issue, but we're only going to AD to get to Exchange 2000, so here goes:
As part of planning our migration from our current single NT domain to a single-forest, single-domain active directory, a plan to back out this upgrade in case of unforeseen problems is being developed and tested. The upgrade plan goes something like this: - Create a new NT BDC on new hardware. - Take the production NT PDC offline prior to the AD upgrade. - Promote a new BDC to the PDC. - Upgrade the PDC to AD This is all done using the same netbios domain name in AD as we had in NT, and an internal DNS namespace name that happens to be the same as our WinNT/AD domain name. And, it works great. But, just in case it does not go as well in the real world as it does in our lab, we have the following as a backout plan: - Take the new AD DC(s) offline - Put the old PDC online. - Re-sync the NT domain So far, so good. It all works great - everyone can log back on to the old NT domain and keep going while I figure out what went wrong. Well there is one exception: Windows 2000 workstations and member servers cannot log on - they get a 'Broken trust relationship with the domain controller' message at log on. Win9x and NT boxes have no problem. Any ideas?? Much thanks for any assist. Jon Martin Systems Programmer East Bay Municipal Utility District (EBMUD) Oakland, CA _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED]
