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

Demoting a Windows 2000 DC in a 2003 Domain 500 pts b/c I need correct answers quick.

I have a Windows 2003 and 2000 Server mixed environment operating in Windows 2000 native mode.  2 of the Windows 2003 servers are DCs, and one Windows 2000 server is a DC.  I want to migrate any of the operation masters/roles from the 2000 server to the 2003 dcs in preparation for demoting the 2000 DC.   Currently, the 2k machine is a global catalog and one w2k3 machine is a global catalog.  The 3rd dc (w2K3) is not a global catalog.  Here are my questions:

1.  I want to remove the global catalog off of the 2k machine.  Will this cause any issues?  

2.  Should I make the other 2k3 DC a global catalog once I take the role away from the 2k machine?  The 2k3 dc that is not a global catalog has exchange 2003 running on it.  That way I will have 2 global catalogs.

3.  Should I make the 2k3 dc a global catalog before I remove the role from the 2k machine?

4.  Once I demote the 2k server, I will have 2 W2K3 servers with Active directory on them.  What roles should be on which servers?  One of the 2k3 DC servers is running exchange 2003 on it as well.  I don't know if that changes anything.

Thanks for the quick replies.

0
adsnetcurve
Asked:
adsnetcurve
  • 4
  • 3
  • 2
2 Solutions
 
mikeleebrlaCommented:
1.  no it won't cause any issues,, but you dont need to do this.  why do you want to remove it? its always best to have mulitple copies of the GC

2.  yes you should,, reason stated in question 1's answer

3.  it really doesn't matter the order

4.  it really doesn't matter since you are in a single domain. the rule of "the infrastructure master should be located on a nonglobal catalog server" doesn't apply to you since you are in a single domain AND b/c all DCs are GCs.

see MS reference below:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;223346
this article is for 2000, but the same is true for 2003
0
 
Chris DentPowerShell DeveloperCommented:

1. As long as you have another available no.

2. You need at least one Global Catalog and Exchange makes heavy use of it so it would probably be worthwhile.

3. Since another is available it's not too important which order you do this.

4. There are 5 roles to take into consideration:

Schema Master
Domain Naming Master
Infrastructure Master
RID Master
PDC Emulator

I would ensure that the PDC Emulator is not on the Exchange server, it's perhaps the most heavily used of all the FSMO roles. RID Master should also go on this server.

Schema Master and Domain Naming Master should ideally be on the same server.

Infrastructure Master shouldn't be running on a Global Catalog unless all servers are Global Catalog. So if you make the third DC a Global Catalog it doesn't matter, if not, put it on whichever server isn't Global Catalog.

I hope that all makes sense.

Chris
0
 
Chris DentPowerShell DeveloperCommented:

oops sorry Mike... I have to learn to press refresh before posting...
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
joedoe58Commented:
I agree with mikeleebrla and would just add a comment about the DC with Exchange. Why not upgrade your w2k server to w2k3 and have it as a second DC and demote the Exchange to a member server. That way you will remove a lot of load from the Exchange.
0
 
Chris DentPowerShell DeveloperCommented:

Sorry to disagree with you Joe...

But... I strongly advise you do not demote the Exchange server... doing that (changing the state of an installed Exchange) is not supported by Microsoft and quite likely to terminally break your Exchange server.

Chris
0
 
mikeleebrlaCommented:
good point joedoe58
0
 
joedoe58Commented:
And I am sorry to disagree with you Chris-Dent.
The reason is that MS does not recomend an installation of Exchange on a DC See this link:
http://www.msexchange.org/articles/Speed-up-Exchange-2000-2003-DC-reboot.html
There should not be any problem to Exchange if you demote a DC since it is true that Exchange 2003 is dependant on AD but AD is still present in the domain just not on the same machine anymore.
0
 
Chris DentPowerShell DeveloperCommented:

Supporting documentation on Exchange 2003 on DCs:

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

> You can run Exchange Server 2003 on either a member server or on a domain controller. After you install
> Exchange Server 2003 on a server, do not change the role of the server. For example, if you install Exchange
> Server 2003 on a member server, do not use the Dcpromo tool to promote the server to a domain
> controller. Or, if you install Exchange Server 2003 on a domain controller, do not use the Dcpromo tool to
> demote the server to a member server. Changing the role of a server after you install Exchange Server
> 2003 may result in loss of some Exchange functionality and is not supported.
0
 
joedoe58Commented:
Stands corrected. Thanks :-)
0

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.

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