I am trying to convert a DC from a 2003 DC to a 2008 RODC. Before I can do that, I must have a writable 2008 DC in my domain. I have a Windows 2003R2 x86 DC that I would like to upgrade to Windows Server 2008R2 x64. What is the best way to back this up before doing so, just to be safe. Also what is the best way to back up my other 2003 DC before upgrading it to a 2008 RODC?
If the DC is a virtual machine, would taking a copy of the .VHD file be helpful?
Thanks in advance
I'm stumped.
I was trying to replicate a file (corporate wallpaper) to branch offices via SYSVOL (so that workstations in branch offices don't have to pull the file from HO). However, the replication only worked for some RODCs, but failed on other RODCs.
On one failed RODC, I tried forcing replication by using the command ntfrsutl.exe forcerepl DEST_RODC_NAME /r "Domain System Volume (SYSVOL share)" /p dc01.example.com ... and within minutes, the wallpaper appeared!
What could possibly the problem here? Why won't some RODC perform automatic sync?
Quick and easy one for the return after Easter;)
I upgraded a clients domain a few months ago from a 2003DC to a 2008R2 Domain. All went OK, few issues we solved along the way but all good now. During the upgrade procedure I completed the necessary adprep /domainprep and /forestprep commands and never bothered withthe /RODC commands because the client had no need for this...so guess what? Yep, a few months alter and they open up a new small office and want to bung in a server down there.
So, my question is, is it OK to run the adprep /rodc commands now on the new 2008R2 DC to ensure the RODC server deploys successfully? The one and only 2003DC was successfully decommisioned some time ago and is gone forever.
Any asistance is greatly appreciated as usual ;)
I have a two-site domain (call them Local and Remote). Site Local has our main IT infrastructure, including two Active Directory Domain Controllers (2008R2). We're trying to set up an RODC at site Remote, which for the most part works just fine. Everything is replicated, password replication follows the policy, the remote DC answers queries - so all good. Except that machines in site Local, when querying the AD, are referred to site Remote. If I do a tcpdump, I see the LDAP query hit both of the Local DCs, and then go on to the Remote RODC.
I've ensured that all of the subnets on both ends are configured in the Site and Services snap-in, and that the DCs are both in their respective sites. According to my research, that should be all that's required for the clients to query the closest DC. Have I missed a step?
I have client which has multiple sites all over the world. They have 2 domain controllers in main location and every other location connects thru to main site with vpn tunnel. Currently the network is more or less disaster so I'm trying to fix it. One thing in common for the secondary sites is that their routers in network settings have ISP local DNS servers so their DHCP based computers get "wrong" DNS servers. It's been like that for ages and they use IP address to connect to servers.
So I would like to fix it with proper DNS servers etc. So I was planning to use RODC and DNS server on the only server (with Terminal Services and couple of programs like Visual Studio that people use to work) that is located in the location. The other option was to enter DNS servers from main location but if the tunnel goes down employees will be confused and won't be able to access internet (as they would need to change router settings) so this doesn't seem as reliable solution.
My questions are as follows: