Active Directory(Domain Controller) server migration


this is my first time doing this and I think I missed something.

I am trying to migrate an active directory server from an old windows 2003 server to a newer 2008 r2 server.

I did my adprep, I added the new server to the active directory with dcpromo.
everything worked fine.

then I trnsfered the operational master, global catalog, and
did a

Transfer domain naming master
Transfer infrastructure master
Transfer PDC
Transfer RID master
Transfer schema master

so, now, this server should be the primary domain controller and I think I should be able to shut down the old one. at least I thought.

I think I missed something somewhere. if I shut down the old domain controller, the new one
can't find the active directory. but if I turn it back on. both see it.

I don't know what I'm missing, but apparently, the old one is still the primary domain controller.

any help on this would be appreciated
Who is Participating?
Krzysztof PytkoConnect With a Mentor Senior Active Directory EngineerCommented:

if you wish, you may follow with articles on my blog for that.

How to add the first 2008R2 DC to 2003 network

after that you may wish to transfer FSMO roles to the new box

when you moved PDC Emulator role, you need to advertise new time server in your forest/domain
[...]- after transfer of the PDCEmulator role, configure the NEW PDCEmulator to an external timesource and reconfigure the old PDCEmulator to use the domainhierarchie now. Therefore run on the NEW "w32tm /config /manualpeerlist:PEERS /syncfromflags:manual /reliable:yes /update" where PEERS will be filled with the ip address or server( and on the OLD one run "w32tm /config /syncfromflags:domhier /reliable:no /update" and stop/start the time service on the old one. All commands run in an elevated command prompt without the quotes. [...]

it's an extract from MVP blog at

Now, also important part. On each staticaly configured computer/server modify DNS settings in NIC properties. Point them to the new DC (which is also DNS, if you didn't change anything during server promotion).

For DHCP clients, go to DHCP management console and modify server/scope(s) options (depends on your configuration). Update option 006 for your internal DNS servers. Put there only INTERNAL IPs of DNS servers which are used in your network (remove that one, which you want to demote). Reboot clients or wait until their lease will expire, then they will get new settings.

On your new DNS server (2008R2 DC) check if you have configured forwarders to allow users browsing the Internet. Put in forwarders section IP addresses of DNS from your ISP or any other publicly available (like Google or/and

The last step before you can demote 2003 DC is to migrate DHCP database from the old box to the new one. Check this MVP blog article, how to do that at

Now, shut down your old DC (to see if everything is working fine). If so, turn it on before 60days will pass (tombstone lifetime for DC) and decommission it to prevent any problems in the future.

How to do that is also on my blog at

So, everything should be fine, now.

And out of the topic. If you have at least 2 2008 R2 servers, you may consider using DHCP redundant server for security purposes. Check how to use Split-Scope on 2008 R2 at

Check also DNS settings.
Here you can find detailed guide:
TheWebGuy38Author Commented:
My dns wasn't right during the migrtion I think

this is the error I got

This server is the owner of the following FSMO role, but does not consider it valid. For the partition which contains the FSMO, this server has not replicated successfully with any of its partners since this server has been restarted. Replication errors are preventing validation of this role.
Operations which require contacting a FSMO operation master will fail until this condition is corrected.
FSMO Role: DC=gssmedical,DC=com

I fixed the dns, but
I don't know if I need to redo the dcpromo and rejoin, or the data will migrate and I can then take the servers offline
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Radhakrishnan RSenior Technical LeadCommented:
Make sure that you have configured your 2008 server as primary and the server should be global catalog role holder. once done run dcpromo /force removal on the old server and disconnect it from network.
TheWebGuy38Author Commented:

think I found my problem.

The schema got corrupted or deleted. also, I don't think the fsmo transferred correctly

this it, it shall work! I have faith!
Krzysztof PytkoSenior Active Directory EngineerCommented:
So, if FSMO roles weren't transffered successful, you need to now seize them to another Domain Controller and do metadata cleanup of that broken one.

You may wish to check articles on my blog for that at
Seizing FSMO roles

Metadata cleanup process

TheWebGuy38Author Commented:
this is interesting, I migrated everything to a new server, everything was successful

but when I did a dcpromo /forceremoval on the old severs due to inconsistencies.

somehow the new servers active directory information disappeared.

I'm trying it again without the  dcpromo /forceremoval
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.