Re: New 2003 DC

On Feb 15, 5:56 pm, "Paul Bergson [MVP-DS]"
<pbergson@xxxxxxxxxxxxxxxxx> wrote:
<boogy...@xxxxxxxxx> wrote in message

news:1171553632.546050.267930@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

On Feb 15, 1:42 pm, "Paul Bergson [MVP-DS]"
<pbergson@xxxxxxxxxxxxxxxxx> wrote:
<boogy...@xxxxxxxxx> wrote in message

news:1171538697.126913.20710@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Hi,

I have a Win2k Domain with three DC's all on service pack 4. There is
one server running Exchange 2000. There are also a mix of 2000/2003
member servers in this Domain.
I plan to install a new server, which needs to be a domain controller,
running Windows 2003R2.

Running a similar setup using Virtual servers, I am trying to
"pratice" the install before doing it in the live setup.

I have read as much as I can on installing a new 2003 DC in a 2000
domain, and have tried to run adprep /forestprep on the DC, I get an
error:

"Adprep was unable to extend the schema.
[Status/Consequence]
There is a schema conflict with Exchange 2000. The schema is not
upgraded.
[User Action]
The schema conflict must be resolved before running adprep. Resolve
the schema c
onflict, allow the change to replicate between all replication
partners, and the
n run Adprep. For information on resolving the conflict, see Microsoft
Knowledge
Base article Q325379.
"

The article given isn't the most helpful, as it is more for upgrading
rather than a new install into an existing domain.

Thanks in advanced

My guess is you are using disk1 of R2, use disk 2 of the two disk set for
the R2 o/s:

"To update the schema, on the schema master domain controller, insert
Disc 2
and open the command prompt. Then, change to the Cmpnents\R2\Adprep
folder
of Disc 2, and type: adprep.exe /forestprep"

See my article on upgrading your forest to 2003 at:

http://www.pbbergs.com
Select articles and click on Upgrade Your Forest

--
Paul Bergson
MVP - Directory Services
MCT, MCSE, MCSA, Security+, BS CSci
2003, 2000 (Early Achiever), NT

http://www.pbbergs.com

Please no e-mails, any questions should be posted in the NewsGroup
This posting is provided "AS IS" with no warranties, and confers no
rights.

Nope, using the 2nd Disk. Have run DCDIAG and it came back with no
errors at all, everything passed.

What do you mean by nope?

I thought you were trying to extend your schema?

I meant, nope, I am not using disk 1 of Win2k3 R2, i was using the
second disk, actually I have used both to no avail.


I just want to add a Windows 2003 DC to an existing Windows 2000
Domain, but I keep getting the errors when running adprep....




.

Relevant Pages

  • Re: 2008 or 2003
    ... To install a 2008 DC in a 2003 domain the schema has to be upgraded to version 44. ... The schema is the same in your complete domain, the schema upgrade will add additional AD objects which are needed for 2008. ... 2008 ad schema instead of setting it up as a 2003 AD server I need all ...
    (microsoft.public.windows.server.setup)
  • Re: MMC Snap-ins
    ... After that the Active Directory Schema is available for selection via mmc snapin. ... From the features install the "Remote server administration tools". ...
    (microsoft.public.windows.server.general)
  • Re: New 2003 DC
    ... one server running Exchange 2000. ... I plan to install a new server, which needs to be a domain controller, ... There is a schema conflict with Exchange 2000. ...
    (microsoft.public.win2000.active_directory)
  • Re: DCPROMO a Windows 2003 R2 server into a Windows 2000 environment
    ... he has a R2 server that he wants to be a DC...so, for an R2 server to be a DC you need to update the AD schema to R2 version... ... the same occurs when installing R2 on an existing non-R2 DC, you need to update the AD schema to R2 version ... Of course all depends how you install the SO. ... If it's the first DC in the Forest, the Schema upgrade is automagically done. ...
    (microsoft.public.windows.server.active_directory)
  • Re: MMC Snap-ins
    ... Well I can use ADSIEDIT.msc or LDP.exe but what happened to the AD Schema MMC? ... From the features install the "Remote server administration tools". ...
    (microsoft.public.windows.server.general)