Thanks!!!! Easy tutorial. I was getting hung up on the Schema error/warning, didn't realize that it was just a warning message and not an actual error.
Thanks, you helped me a lot. At one point I run into the issue that I couldn't transfer the Scheme what was caused by 2 fatcs: 1st was, that I had disabled IPv6 and second, that my admin wasn't a member of the Schema-Admins group. After I sorted that out, your guide worked like a charm.
At 2.48 you mentioned to check these 2 repl commands at least. What would be the full set of checks that should be run on the main DC? all? Also shouldn t you change the future decommissioned dc from GC to DC catalogue?
OR you can simply do this through powershell: Move-ADDirectoryServerOperationMasterRole -Identity ADIR02 -OperationMasterRole SchemaMaster, DomainNamingMaster, PDCEmulator, RIDMaster, InfrastructureMaster
Im about to move my PDC from a desktop PC to a virtual server on a new to me poweredge i got - Will these steps move the DNS role as well? DNS is on my PDC
Everything is fine for me until I'm trying to change schema operations master. The change button is greyed out. I've tried running MMC snap-in from both source and target DC (picking target DC first of course), greyed out on both tries. It's Windows Server 2019 Standard on both DCs. ADD: My domain user was not member of schema admins group. After adding and logout/login, I was able to transfer this role as well.
I had an issue transferring the Schema role. I had to run a PowerShell command for that last one. The Role numbers are here so I excluded 0,1,2,4. The command to transfer roles from Powershell is below. 0 PDCEmulator 1 RIDMaster 2 InfrastructureMaster 3 SchemaMaster 4 DomainNamingMaster Move-ADDirectoryServerOperationMasterRole -Identity "ServerName" -OperationMasterRole 0,1,2,3,4
Hi. Thanks for the video. If I wanted to also setup DHCP on the new server, would I create the scope before or after following your guide? I'd like to keep the old DC around as a backup. Thanks
DHCP works independently to the FSMO and DC roles so it doesn't really matter. My best practice advice would be to do it after you have your DC and FSMO roles set on the new server, just so that stuff is "out of the way and done" before moving on to setting up DHCP
Old video I m going to give it a try though.... 1. What about if the source domain controller is on a win serv 2012r2 environment and the server on which the roles are going to be transferred is a win serv 2019. 2.What about the domain functional level which due to 2012r2 will be at a lower level than the new server. 3.When there is the need for the old server to be demoted , is the process requires specific steps like a.Transfer the fsmo roles b.demote the old server c.promote the new server e.what about the functional level which step might that be here? f.dhcp/dns/ntp roles?
Amazing, I got everything else done except for the schema master. It wasn't same but I got the idea. I run windows server 2022 core, thats where the primary roles where being transferred to. I wound up using a powershell command to transfer the last one. I would love to see an all powershell tutorial on doing this though!
Can this all not be done from Windows PowerShell from the source machine? Move-ADDirectoryServerOperationMasterRole -Identity "NEW-FSMO-SERVER-NAME" -OperationMasterRole 0,1,2,3,4
quick question, does the DHCP role also move over? Our PDC provides DHCP for 4 subnets and before we transfer everything over we want to make sure the addressing responsibilities also move over.
The BEST GUIDANCE!! Thank you!!
Thanks!!!! Easy tutorial. I was getting hung up on the Schema error/warning, didn't realize that it was just a warning message and not an actual error.
Glad it helped!
Nice job, Alexander! Easy to follow, and worked great! Much appreciated!!
You're welcome!
Thanks, you helped me a lot. At one point I run into the issue that I couldn't transfer the Scheme what was caused by 2 fatcs: 1st was, that I had disabled IPv6 and second, that my admin wasn't a member of the Schema-Admins group. After I sorted that out, your guide worked like a charm.
Thanks, this got me out of a hole, I wasted a day messing around with commands and running into issues.
Thank you, very clear instructions and guidance!!!
Great video. Exactly what I was looking for! Thanks!
You're welcome!
Thank you very much for sharing you knowlage. Very clearly explained !
Thanks a lot. Wonderfully explained!!
Glad it was helpful!
Excellent tutorial. Thank you
Glad it was helpful!
Thanks Alexander sharing your knowledge.
Great Explanation. Thank You So Much.
Thank you for this video, precise and step by step. thank you !!!!
Thank you so much~!! Very useful info
You're very welcome!
Great walkthrough, thank you!
Great Explaination.
Nice Video!! ty man.
No problem!
Great video! Thanks!
thanks much for the help exactly what i needed and easy as pie
Great video!
Well done and thank you.
Excellent. Thank you.
I have a project coming up like this next few weeks. thx
At 2.48 you mentioned to check these 2 repl commands at least. What would be the full set of checks that should be run on the main DC? all?
Also shouldn t you change the future decommissioned dc from GC to DC catalogue?
OR you can simply do this through powershell:
Move-ADDirectoryServerOperationMasterRole -Identity ADIR02 -OperationMasterRole SchemaMaster, DomainNamingMaster, PDCEmulator, RIDMaster, InfrastructureMaster
Thanks
Thanks man :D
No problem!
Thanks
Welcome
Im about to move my PDC from a desktop PC to a virtual server on a new to me poweredge i got - Will these steps move the DNS role as well? DNS is on my PDC
Everything is fine for me until I'm trying to change schema operations master. The change button is greyed out. I've tried running MMC snap-in from both source and target DC (picking target DC first of course), greyed out on both tries. It's Windows Server 2019 Standard on both DCs.
ADD: My domain user was not member of schema admins group. After adding and logout/login, I was able to transfer this role as well.
I had an issue transferring the Schema role. I had to run a PowerShell command for that last one. The Role numbers are here so I excluded 0,1,2,4. The command to transfer roles from Powershell is below.
0 PDCEmulator
1 RIDMaster
2 InfrastructureMaster
3 SchemaMaster
4 DomainNamingMaster
Move-ADDirectoryServerOperationMasterRole -Identity "ServerName" -OperationMasterRole 0,1,2,3,4
Hi. Thanks for the video. If I wanted to also setup DHCP on the new server, would I create the scope before or after following your guide? I'd like to keep the old DC around as a backup. Thanks
DHCP works independently to the FSMO and DC roles so it doesn't really matter. My best practice advice would be to do it after you have your DC and FSMO roles set on the new server, just so that stuff is "out of the way and done" before moving on to setting up DHCP
Old video I m going to give it a try though....
1. What about if the source domain controller is on a win serv 2012r2 environment and the server on which the roles are going to be transferred is a win serv 2019.
2.What about the domain functional level which due to 2012r2 will be at a lower level than the new server.
3.When there is the need for the old server to be demoted , is the process requires specific steps like
a.Transfer the fsmo roles
b.demote the old server
c.promote the new server
e.what about the functional level which step might that be here?
f.dhcp/dns/ntp roles?
Amazing, I got everything else done except for the schema master. It wasn't same but I got the idea. I run windows server 2022 core, thats where the primary roles where being transferred to. I wound up using a powershell command to transfer the last one. I would love to see an all powershell tutorial on doing this though!
Awesome - That is a good idea and I will make note of it.
Can this all not be done from Windows PowerShell from the source machine? Move-ADDirectoryServerOperationMasterRole -Identity "NEW-FSMO-SERVER-NAME" -OperationMasterRole 0,1,2,3,4
quick question, does the DHCP role also move over? Our PDC provides DHCP for 4 subnets and before we transfer everything over we want to make sure the addressing responsibilities also move over.
This is a separate role and doesn't really have anything to do with active directory.
ty
np
Or you could force a replication between DC's by typing the following in powershell; repadmin /syncall /adep