My network is one domain, with 2 sites. Each site has it's own DC running 2003 server.
I've purchased two new servers to replace the existing DC's and want to carry out this upgrade without giving myself any unnecessary headaches!
My understanding is that after adding my new server to the domain as a member server I then need to run ADPREP on the exising DC before I can then run DCPROMO on the new server.
The new server is Windows 2003 server R2 and I've read that I need to run the ADPREP on the existing DC from the R2 CD. I also read that the existing DC should be running SP2, which it is not.
I inherited this domain and I've never had much confidence in how my predecessor setup the domain in the first place. For example, on the existing DC at my main site, I cannot access Windows Updates from the MS site as it constantly asks me to install the Active X each time I load the page, and continues to do so after I choose to install it. Obviously I could download SP2 directly from Microsoft but I'm concerned that as I can't upgrade to SP2 from the MS Update site I wonder if my predecessor has disabled anything on the server preventing updates from taking place, if so then would SP2 give me problems?
Also, need Clarification on the following:
After this I need to run ADPREP /Forestprep and then ADPREP /Domainprep.
Run DCPromo on the new DC.
Set it as a GC server
Transfer the FSMO roles to the new DC from the old
Power down the old DC and ensure the domain functions correctly
If so, demote the old DC using DCPROMO
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.
Make sure you get time synchronisation working. It is often overlooked and can prevent domain replication and cause other issues too. You'll need to move this to the new server with the PDC-emulator FSMO role.
See http://blogs.bdnet.co.uk/s
Make sure you check that AD Sites & Services is configured correctly as well.
I'd recommend that both new servers are global catalogs and both are DNS and DHCP servers. I'd also recommend that they are both WINS servers.
I've been away for a while, so sorry for the late reply!
All three steps can be accomplished while the network is active and in use. The changes are replicated in the same way as when you install Exchange or make administrative changes, and it is assumed that the network is active while this is going on!
You should either force AD replication or wait for it to complete (normally 15 minutes maximum in a LAN) before doing the DCPromo step, however.
Business Accounts
Answer for Membership
by: mihapiPosted on 2008-01-17 at 05:33:31ID: 20681029
Hi,
Yes, if you want to have R2 domain controller then you will need to run ADPREP first.
Here are some other steps for you
- Clean installation of Windows
- Install all updates
- run dcpromo on new server and make it a domain controller
- make new server DNS server
- make new server global catalog (http://support.microsoft.
- move all FSMO roles (if necessary) to new server (http://support.microsoft.
If necessary update your clients to point to new DNS server (e.g. if you are using DHCP, update DHCP configuration).
About your Windows Update problem, you can try this. Stop Automatic Update service on the server. Locate SoftwareDistribution folder in %systemroot%. Rename SoftwareDistribution to SoftwareDistribution_OLD. Now start Automatic Update service. It will create new SoftwareUpdate folder. Try using Windows Update.
Le me know if you have any questions about this...
Mike