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.
Main Topics
Browse All Topics





by: mihapiPosted on 2008-01-17 at 05:33:31ID: 20681029
Hi,
com/kb/313 994) com/kb/324 801)
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