Re: Problem getting Exchange 2000 to see AD 2003 GC

The DC/GC may not be properly synchronized. You can check by connecting to
RootDSE (using LDP.EXE) and looking for the IsSynchronized flag. Another
good option would to use wind up the diagnostics logging on DSAccess, as
explained in the following article.

http://support.microsoft.com/kb/316300

Tony
www.activedir.org

"BeFree" <BeFree@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:59D550F8-414E-426E-96A5-93485BAF4F29@xxxxxxxxxxxxxxxx
> We are trying to decide the best way to upgrade our AD 2000 & Exchange
> 2000
> domain to 2003. I can't upgrade the AD servers because they're off the
> HCL,
> so I want to replace them with newly built Windows 2003 servers, dcpromo'd
> into the tree (after the prerequisite adprep and mangle prevention tasks
> ...). We're working all of this out in the testlab first. For the full
> story and proposed migration plan, see
> http://x220.win2ktest.com/forum/topic.asp?TOPIC_ID=13776
>
> The problem is we can't seem to get Exchange 2000 to work after doing
> that.
> It can not see the newly created Windows 2003 AD as a Global Catalog. It
> does appear to actually be a GC, repadmin /showreps says IS_GC, and it's
> listed in DNS as a GC as well. But in Exchange System Manager on the
> Directory Access tab it does not recognize the 2003 server automatically.
> If
> we set it to manual and force it to that new server, the message stores
> don't
> mount and it complains that there is no GC. All the Microsoft literature
> I've read says that Exchange 2000 will work just fine with AD 2003, but
> they
> usually are talking about an upgrade path.
>
> When we ran through the scenario of doing it as an upgrade after DCPROMO,
> the 2003 server does work just fine with Exchange. Only when it's a clean
> build of Windows 2003 fresh (which is what I'd prefer for many reasons)
> does
> it cause Exchange grief.
>
> Can anyone confirm that this should work, promoting a Windows 2003 server
> and using it as a GC for Exchange 2000? Or will I need to keep a Windows
> 2000 GC available until Exchange 2003 has replaced Exchange 2000
> completely
> in our environment ?
>


.

Relevant Pages

  • Re: NT to W2K3 Migration
    ... You cannot just promote a member server to AD. ... upgrade your PDC to windows 2000 or 2003, whichever flavor of AD you want to ... Upgrading from Windows NT Server 4.0 ... ensure that you have designed a DNS ...
    (microsoft.public.windows.server.active_directory)
  • Re: NT to W2K3 Migration
    ... How to Upgrade from Windows NT Server 4.0 ... Best Practice Active Directory Design for Managing Windows Networks ...
    (microsoft.public.windows.server.active_directory)
  • Re: Native 2003 mode and NT4 workstations?
    ... Migrating from Windows NT Server 4.0 to Windows Server 2003 ... How to Upgrade from Windows NT Server 4.0 ... ensure that you have designed a DNS ...
    (microsoft.public.windows.server.active_directory)
  • RE: Single Server Upgrade Exchange Question
    ... The Exchange Migration Wizard can migrate all user mailboxes. ... server and then import them to the destination server. ... Single Server Upgrade Exchange Question ...
    (microsoft.public.windows.server.sbs)
  • Re: Migrating NT4 to Windows 2003
    ... Migrating from Windows NT Server 4.0 to Windows Server 2003 ... How to Upgrade from Windows NT Server 4.0 ... Best Practice Active Directory Design for Managing Windows Networks ...
    (microsoft.public.windows.server.active_directory)
Loading