• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 264
  • Last Modified:

Trouble preparing AD for 2000 server to 2003 server upgrade

We are having difficulty prepping A.D. for an upgrade to 2003 Server R2.  We appear to be having a replication issue.  Here are the errors we are getting from adprep /forestprep:

"There is a schema conflict with Exchange 2000. The schema is not upgraded."

When we ran dcdiag /test:fsmocheck on one of the DC's... we got this error:

"Warning: DcGetDcName(GC_SERVER_REQUIRED) call failed, error 1355
A Global Catalog Server could not be located - All GC's are down."

We host our own internet DNS and our domain name was switched from AD-integrated to standard primary.  We aren't sure if this is what is causing the replication issue/errors we are getting or if it's just part of the problem.  Or... not the problem at all?

Anyone have any ideas?  We need to get this fixed asap!

  • 2
2 Solutions
I would start with dcdiag and try fixing some of the error from there.

"We host our own Internet DNS and our domain name was switched from AD-integrated to standard primary. "

Why did you do that?
A windows domain needs to be set to AD Integrated.

MemberMindedAuthor Commented:
Thanks ComputerTechie... we were able to clear the problem!
MemberMindedAuthor Commented:
Problem resolved

Featured Post

Veeam Disaster Recovery in Microsoft Azure

Veeam PN for Microsoft Azure is a FREE solution designed to simplify and automate the setup of a DR site in Microsoft Azure using lightweight software-defined networking. It reduces the complexity of VPN deployments and is designed for businesses of ALL sizes.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now