Re: Error DCPromoing 2003 R2 Server adding to existing domain




tke402 wrote:
Hi,

I am dcproming a 2003 R2 Server and I receive an error saying the version of
AD in the existing domain isn't compatible to the version on this server. Run
adprep again ...etc. etc.

you have to run forest prep from the 2nd CD of R2.



Just some background info. Domain Level = 2003, Forest Level =2000. Orignal
DC's and AD domain were created on 2003 server. The new servers I would like
to make DCs are R2.

Do I just have to raise the forest level to 2003 for me to be able to
dcpromo the R2 servers? Or do I have to rebuild the R2 Servers with regular
2003?

I'm hesitant to raise the forest level, because I have a trust with a NT4.0
domain that is still activiely used. Will raising the forest level to 2003
break this trust in any way?

Thanks,

TKE402

.



Relevant Pages

  • Re: DCPROMO Question
    ... Windows2000 Native or Windows Server 2003 Native if the particular domain ... > raise my forest level but can't until I either upgrade my win2k DC to ... > was my PDC running NT4. ... I loaded up a new server with NT4 made it a BDC ...
    (microsoft.public.windows.server.active_directory)
  • Re: Domain Rename Error Message
    ... LDAP tools such as Ldp.exe and Adsiedit.msc can be used to view and modify ... Forest Level Setting ... The attribute is msDS-Behavior-Version on the CN=Partitions, ... Value of 1=Windows Server 2003 interim forest level ...
    (microsoft.public.windows.server.active_directory)
  • multihomed DC??
    ... I am running a forest level DC, ... media server in the same domain and subnet. ... manager role. ...
    (microsoft.public.windows.server.networking)
  • Re: multihomed DC??
    ... > I am running a forest level DC, ... > have a media server in the same domain and subnet (at forest ... I want to combine the media server and DC ... You can multihome a DC, but you have to be careful ...
    (microsoft.public.windows.server.networking)
  • Re: Trust requirements for TS License Server in a different domain
    ... Licensing Server needs to trust the domain containing the Terminal ... only thinking about the Terminal Server and the TS Licensing ... have to be in trust relationship with License Server Domain ...
    (microsoft.public.windows.terminal_services)