Re: Exchange 5.5 on Windows NT in Active Directory

From: CJ (chrisj_at_illicom.net)
Date: 07/05/04 

Date: Mon, 05 Jul 2004 05:37:19 GMT

"Rich Matheisen [MVP]" <richnews@rmcons.com.NOSPAM.COM> wrote in message
news:gmjhe0l2r2pfkhk8lfg2t6jligp3auvap9@4ax.com...
> "CJ" <chrisj@illicom.net> wrote:
>
> >"Rich Matheisen [MVP]" <richnews@rmcons.com.NOSPAM.COM> wrote in message
> >news:pmvee0175h787ddt570o1k5b6prns0g1bc@4ax.com...
> >> "CJ" <chrisj@illicom.net> wrote:
> >>
> >> >Someone please help!!!!!! ARRRGH.
> >> >
> >> >I tested my Windows NT domain to Windows 2003 Active Directory
upgrade.
> >> >Everything went as planned...the DNS, the logons..everything.
> >> >Except for the mail server. I still, at this time, have to run
Exchange
> >5.5
> >> >on a Windows NT box until the next budget comes up.
> >> >
> >> >How do I get Exchange 5.5 on an NT box to work on an Active Directory
> >> >system? I am running in mixed mode.
> >>
> >> If the Exchange server's a member server in the AD domain there's
> >> nothing to do. The AD provides a PDC emulator that the Exchange server
> >> will use in pace of the NT domain controllers.
> >
> >
> >That sounded about right to me. To give you a little more information,
if I
> >try to log on locally it won't let me until I put the NT PDC back on
line.
>
> Uh-oh. And how can you have a NT4 PDC when that's the first domain
> controller that gets upgraded to become a AD Domain Controller? You
> PDC should have been made into a Windows 2003 server.

I did make a PDC into a win2003 DC, just not my production PDC. I take it
offline and use a BDC that I upgraded to a PDC...just in case I need to put
the NT domain back until I figure out the problem.

>
> >Its like there is no domain controller to authenticate me.
>
> With the NT4 domain controller off-line, who owns the PDC Emulator
> FSMO role for the domain?

Should be the test PDC that I upgraded to Win2003

> >But I can log
> >all other machines on to the new 2003 DC. XP, 2000 and 98.
> >Any ideas?
> >
> >If somehow the NT server is not a memeber of the new AD domain, what do I
> >need to do to get it to be? It is listed in Computers in the 2003
server.
>
> Just because there's a computer account doesn't necessaily mean that
> the server's a member of the domain. Check the server's properties and
> verify it's a domain member of the correct domain . . . and please
> explain how you have a NT4 PDC for the domain! I don;t think your
> problem's got much to do with Exchange.

Me neither, but like I said, I made a Win NT BDC from scratch and promoted
it to a PDC after my production PDC was taken offline just for the sole
purpose of using it to test the Windows 2003 upgrade.

Does this clear it up?...Any ideas.
Thanks for the replies. Its greatly appreciated.

>
> --
> Rich Matheisen
> MCSE+I, Exchange MVP
> MS Exchange FAQ at http://www.swinc.com/resource/exch_faq.htm

Relevant Pages

  • RE: NT4.0 to 2003
    ... I'd give up on the idea of installing NT on the new server unless ... Promote it to the PDC ... Upgrade the temp PDC to Server 2003 and have it be the first AD Domain ... Assuming you go the round about way I'm suggesting you won't be installing ...
    (microsoft.public.windows.server.migration)
  • Re: Migrating a NT4 Domain into an Active Directory Domain
    ... That being said you can build a new NT 4 BDC and switch it to being the PDC. ... Then upgrade it ... of hardware and in need of a 'transitional' and temporary server. ... > upgrade it to the NT Domains PDC and then upgrade it to Windows 2003 DC? ...
    (microsoft.public.windows.server.active_directory)
  • Re: Windows NT 4.0 BDC Upgrade
    ... >>Microsoft MVP - Windows NT Server ... >>> I am guessing that during the w2k upgrade it logs ... >>> or pdc. ... >>> make the computer account on the DC. ...
    (microsoft.public.win2000.active_directory)
  • dcpromo fails on 2nd server after in-place upgrade of NT to W2K3
    ... After completing an in-place upgrade of our NT 4 PDC to Windows 2003 Server, ... I cannot run dcpromo to create a second domain controller on a server running ... The Active Directory name (and DNS zone) is MyDomain.com and the NetBIOS ...
    (microsoft.public.windows.server.active_directory)
  • Re: NT 4.0 to windows 2003 AD in place upgrade.
    ... I believe you will need Server ... Manager to make it the PDC. ... upgrade the OS and go with the rest of the steps ... Floppy I was able to install them during the OS install. ...
    (microsoft.public.windows.server.migration)