Hi All,
I have a domain which has only one domain controller with Windows 2003 server, standard edition. I am planning to add another domain controller for redundancy purpose. The second server has windows 2003 ENTERPRISE edition. I have already join this server to the domain as a stand alone server. Now I want to run the Manage Server roles wizard to make it a domain controller, will it work? Is it doable?
Also, do I need to install DNS services on the second domain controller to be before I make it a domain controller? This is my first time doing it. I will appreciate it if some one can give me step sequence so I don't mess it up.
I did do some research on the web and somewhere I found that it is mandatory to install DNS first on the domain controller to be, before I upgrade it to DC.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
You do not have to install DNS on the second domain controller at all. It can use the first DC as its DNS server. Installing DNS on the second DC will give you redundancy, allowing DNS to continue to function in case the first DC goes down, but it is not absolutely necessary. If you do choose to install DNS on the second DC, you do not have to do so before you promote it. You can do it at any time afterward.
Since you already have the 2003 machine as a member server, you're ready to run dcpromo. It is not necessary to have DNS on the 2003 machine to promote it, but it has to have access to a DNS server (in this case your 2000 machine). It is advisable to add DNS to the 2003 machine though, since it will provide redundancy for this important service.
I entirely agree with Paka's comments. Not having DNS redundancy is effectively the same as operating with a single domain controller --- users won't be able to login without it --- however you still have a working copy of AD so it is still much, much better from a recovery perspective.
There is no good reason not to implement a second DNS service since you are adding a second domain controller.
I'd also make the same recommendations for WINS and DHCP, although these do require a little more configuration, particularly DHCP.
If the first DC is the pre-R2 version of Server 2003 and the new DC is the R2 version, then yes, you will need to run those commands (actually, you will likely only need to run adprep /forestprep in a single-domain forest, but you may as well run the /domainprep too). They will need to be run on the original DC, and will need to be run from the R2 CD (the second CD in the set).
If both servers are R2 or pre-R2, you do not need to run the commands.
If you are looking in Active Directory Users and Computers, the domain is whatever is shown, so almost certainly xyz.com.
You need to run forestprep at least once. You'll only need to run it now if you are installing an R2 server as you already have a Windows 2003 server configured. The same is true for domainprep.
You should run both commands on your existing domain controller. You'll need to be a member of Schema Admins and Enterprise Admins for the forestprep command.
Alright, let me give it a shot.
DrDave242 said "but you may as well run the /domainprep too). They will need to be run on the original DC, and will need to be run from the R2 CD (the second CD in the set)."
How can I run that? I see ADPREP.exe on CD 2. So I just copy it to HD and run it?
Also, will any of the steps require a reboot on main domain controller? Do I need to have a backup of system state before I do that? Is it okay to do it during business hours? Sorry, for throwing all the questions. I am doing it for the first time and I am little nervous because we only have on old PC that is running as domain controller. So I want to take every precaution that I can think off.
To run it, just put CD2 in the drive of the old DC, exit the Autorun screen when it comes up, and open a command prompt. Change to your CD drive, then change to the cmpnents\r2\adprep directory (I think that's correct), and run adprep /forestprep. Once that's done, run adprep /domainprep, although like I said, I think it will tell you that it doesn't need to be run. I don't recall off the top of my head whether a reboot is required after running these commands, but for some reason I don't think so. If so, you can put off the reboot until a more convenient time.
A system-state backup is always a good idea when you're making significant change to AD (like a schema extension, which is what you're doing).
Yep, I agree. I hope this is doable.
I found this link http://support.microsoft.c
That link refers to an older version of Adprep, the one used to prepare a Windows 2000 forest/domain for 2003 DCs. Here's some information on the newer (2003 R2) version of Adprep:
http://technet2.microsoft.
Hi DrDav242,
I read the link. It says "When you update the schema, you do not have to upgrade your existing domain controllers to Windows Server 2003 R2; they can continue to run Windows NT® Server 4.0, Windows® 2000 Server, or Windows Server 2003. Note, however, that Identity Management for UNIX must be installed on a Windows Server 2003 R2 domain controller. DFS Replication Service and Print Management Console can run on any computer that runs Windows Server 2003 R2."
So I am guessing it should be okay if my origanl domain controller is windows 2003 server, STANDARD EDITION and new one is ENTERPRISE edition R2.
As per the link, I need to install Identity Management for UNIX. Do I really have to? We have lots of Linux machines in the domain? How will I do it, if answer is yes?
You are correct in that your existing DC does not have to be upgraded to R2. The other statement simply means that Identity Management for UNIX can't be installed on a pre-R2 machine, so if you needed to use Identity Management for UNIX (which you don't if you have no UNIX servers in your network), you would have to install it on your R2 server.
Hi DrDave242,
I was able to add second domain controller without any problem.
ADPREP /forestprep was only command that I had to run. As you mentioned, the when I ran ADPREP /domainperp, it told that it is not needed.
After that I ran DCPROMO and everything went well.
FYI: ADPREP does not require a reboot.
THANK YOU SO MUCH FOR ALL YOUR HELP !!!
Business Accounts
Answer for Membership
by: SteveH_UKPosted on 2008-02-29 at 13:20:23ID: 21017687
Have a look at this link:
http://www.experts-exchang
----
Regarding Enterprise edition, there are no issues. It is a fully supported scenario.