As an IT Manager with a background in programming, I freely admit to knowing enough about networking and Domain Controllers to be dangerous. I was dreading upgrading our 2012r2 server to 2022. Today, it went off almost without a hitch. Thanks for the clear, accurate, and comprehensive video! Oh, and the hitch? Just make sure you don't accidentally change your timezone and throw off the time by 3 hours. Oops.😬
It was a little strange to see this comment, because it describes my own situation perfectly. I also have a background in programming and are now working as an IT-manager. I been thinking about upgrading my domain controller from 2012R2 for a long time. After seeing this video I dared to do the job, and it went smoothly. The most timeconsuming part was actually the part that was almost forgotten in the video - updating the DNS settings for all our DHCP-server, server, printers, etc. to point to the new server.
This tutorial has come at the right time. Updating a small office of 12 users from 2012 essentials to 2022 essentials. Thank you so much for taking the time and showing the steps. Thumbs up and subscribed.
By accident I was assigned an urgent task to move DC from a VM to a Windows host OS. With my limited AD knowledge, thanks to this video, I was able to get this done within half an hour. My honest gratitude to the author for concise, efficient instructions in this video.
Ha! So very glad I could help. I actually did this video to prove to a company that I knew what I was doing. They chose someone else, but it was a good experience all the same.
@@URTechDotCa Well its their loss in the end. Or maybe the "would be your boss" got scared that you could replace him so he hired someone who didn't know that much.
Thanks Bro!! This isn't something I do more than once every 2 years, I always fumble through through the errors.. this video is so handy, thanks again! 🤘🐱🌱🍄
Here we are in 2023, once again migrating the same domain, that was created on 2003 Small Business Server (+SQL, + Exchange), virtualized and migrated to 2012 R2, and now migrating to Windows Server 2022 - completed introduction of 2022 DC and transferred roles. Everything still works after all these years, although I still find remnants of SBS2003 here and there :)
Will be trying this tomorrow for a client. It would be nice if MS put out videos like this, or made a wizard for this rather than having people play Where's Waldo to find and move different roles...but that would make too much sense. Thanks for the helpful video.
@@URTechDotCa Of course when I tried this it wouldn't take because the current domain forest/domain level was either 2000 or 2003 and when I tried to raise it to 2008 R2 it failed.
Part of the problem is that all this amazing tech is no longer sexy and doesn't get the attention it should. Ideally Microsoft would rewrite all their domain tools and unify most of it, but that's never going to happen now, so we are left with this breadcrumb situation sadly.
I got a little problem about group policy, upon checking it copies to the new windows server 2022 but no setting has been moved. What extra step do I need to do? Thank you!
HI, great watch and so good thanks. When wanting to move over the Domain to Operations Masters , I only see my old server in both the Operations masters and transfer to, any ideas? Thanks
when going to MMC AD Schema - the new server shows unavailable? I get AD Schema Snap-in is not connected to the schema operations master. You will not be able to perform any changes.
After demoting the 2012 server removing it from the network, and shutting it down can i change the ip address of the new 2022 server to the ip address of the old server so i don't need to change all the dns settings for all the workstations and other servers?
Thanks for this video. We are actually on the process of planning our migration for exactly the same versions of windows server and this one is an absulote rescue. One question though: does running a robocopy command to move all files from the old DC (2012) to the new DC (2022) should be done before promoting the new server to a DC or after? or it doesn't really matter? Thanks for the answer.
Through this process the users in AD are moved over? That's the only thing I didn't see covered in the video. I'll be following this video to help me with an AD migration from 2012 to 2022!
Yes. The new server got all the user accounts when it was made a domain controller. That's how AD works. The title of this video is ever so slightly technically misleading lol
@@craigmurray4746No worries! I followed this video when I did the migration and everything worked as expected! Thank you for this video and the clear explanation of how to do this!
This is almost exactly my own situation that I'm working on. This video is wonderful! It's going to be my walkthrough through process, however I do have one questions. Rather than having to repoint every device/machine to a new DNS address, is it possible, once I demote the old one DC to swap the IP of the new box to the old one or am I asking for trouble trying to do that? Seems like it should be easy enough to do.
Changing the IP address of the servers would work, but this is also why best practice is to assign all client IP's with DHCP so that you make the change in one place and within a period all clients automatically pick up the new DNS server without needing to manually reconfigure anything.
@URTechDotCa I have to carry out this same task as you have done, however not because my old DC is from an earlier version of Windows but because I setup the dc on an evaluation version of server 2022 and apparently you can't convert an evaluation server DC to a full one. When I do this task, I won't need the old server so will just turn it off. But can I then change the IP address of the new DC to that of the old one so I don't have to update all the client machines with the IP of the new DC?
I have Windows Server 2012 R2 Domain Controller and intend to upgrade to Windows Server 2022. Additionally, my Group Policy Management is currently hosted on the same Windows Server 2012 R2 machine. The question is, will Group Policy Management also transfer to Windows Server 2022 after the process?
Hi. Very helpful. Just a quick question. I have in old server AD Certificates Services. How do migrate this too? I believed we cannot have multiple AD with certificates services.
great tutorial but unable to raise domain function lever from win2012 r2 to server 2022. error 'To update the domain functional level, the Active Directory Domain Controllers in the domain must be running the appropriate version of windows'. kindly help
If you follow this very well done video, be certain that SYSVOL is replicating before you demote your old DC. Fail to do and you may find no clients are able to authenticate or GPO's present on new DC. Check your "\Windows\SYSVOL\sysvol\DOMAIN NAME.WHATEVER" is the same as your old DC and test replication before demoting/decommissioning. Excellent guide non the less and very funny. DHCP "MORON"😄
@Drakken_ Yeah it's a work around. Best practice is to have DHCP and get your changes made that way. Clients are meant to be far more flexible than servers after all
@Drakken_ Yeah it's a work around. Best practice is to have DHCP and get your changes made that way. Clients are meant to be far more flexible than servers after all
Thanks!!! do you know if its possible to move shared folders with access permissions from one server to another inside a domain without losing their respective permissons
Hey mate, QQ. Do i remove DNS delegation first or do i update dns delegation first? Migrating primary DC that has DNS from Win2012 to Win2019, so wondering as you skipped it in the first step and did NOT update but later on you removed it off the old server. Need to move the zones , DNS namespaces etc.
Can you power down the old DC and rename the new DC with the same name as the old DC and assign it the same static IP. This way you don't have to worry about changing DNS information on the workstation.
Not directly. You need to first use 2012R2 as a temporary measure cause some tech changed over the years so you can't have 2022 as a domain controller in a 2003 domain.
Hi, thank you for the tutorial.. but i have a few question. If i am in a server 2008R2, i need to upgrade to 2012R2 then upgrade to Server 2022 right? Do we need to upgrade the schema first? No need for schema upgrade? Thanks again for the video.
If you were talking about upgrading on the same hardware, then yes you'd have to jump to 2012R2 1st, then to 2022. You definitely do not need to update the schema before upgrading, one of the nice things about AD is how conservative you can be.
Unless you configured Group Policy to use the concept of the central store, then no, it won't have copied the policies from one server to the other. Scripts may have copied depending on where they were stored. If it was in the SYSVOL share it would be copied to the new server yes.
As an IT Manager with a background in programming, I freely admit to knowing enough about networking and Domain Controllers to be dangerous. I was dreading upgrading our 2012r2 server to 2022. Today, it went off almost without a hitch. Thanks for the clear, accurate, and comprehensive video! Oh, and the hitch? Just make sure you don't accidentally change your timezone and throw off the time by 3 hours. Oops.😬
It was a little strange to see this comment, because it describes my own situation perfectly. I also have a background in programming and are now working as an IT-manager. I been thinking about upgrading my domain controller from 2012R2 for a long time. After seeing this video I dared to do the job, and it went smoothly. The most timeconsuming part was actually the part that was almost forgotten in the video - updating the DNS settings for all our DHCP-server, server, printers, etc. to point to the new server.
This tutorial has come at the right time. Updating a small office of 12 users from 2012 essentials to 2022 essentials. Thank you so much for taking the time and showing the steps. Thumbs up and subscribed.
Wow! This is the most comprehensive and entertaining manual I found on my research. thank you very much for this video!! Kudos to the team.
I have a migration scheduled for tomorrow and am very happy to have found your video. Thank you for sharing your knowledge 🙂
How did it go?
Thank you very much! this tutorial helped me to migrate my 2012 AD to 2019 AD in minutes. The video is precise and easy to follow. Congrats!
Great tutorial. This really helped me with migrating from 2012R2 to 2016 domain and forest. Thanks again.
By accident I was assigned an urgent task to move DC from a VM to a Windows host OS. With my limited AD knowledge, thanks to this video, I was able to get this done within half an hour. My honest gratitude to the author for concise, efficient instructions in this video.
Dang. That's something an L3 could do. Congratulations for the huge upskill you've done!
Did my first DC migration and it went well, thanks to this video!
Again - many thanks. It was such a clear, comprehensive explanation that I just used it on a job. I feel like I should split my fee with you!
Ha! So very glad I could help. I actually did this video to prove to a company that I knew what I was doing. They chose someone else, but it was a good experience all the same.
@@URTechDotCa Well its their loss in the end. Or maybe the "would be your boss" got scared that you could replace him so he hired someone who didn't know that much.
@@URTechDotCa jesus that's a shame. Great video and extremely helpful and clear appreciate it!
Extremely valuable and well done.
Thanks Bro!! This isn't something I do more than once every 2 years, I always fumble through through the errors.. this video is so handy, thanks again! 🤘🐱🌱🍄
Very well done. Covered a couple of pieces I had overlooked in the past
simple, clear, no bs, perfect
Very informative to anyone looking to upgrade!
Here we are in 2023, once again migrating the same domain, that was created on 2003 Small Business Server (+SQL, + Exchange), virtualized and migrated to 2012 R2, and now migrating to Windows Server 2022 - completed introduction of 2022 DC and transferred roles. Everything still works after all these years, although I still find remnants of SBS2003 here and there :)
Will be trying this tomorrow for a client. It would be nice if MS put out videos like this, or made a wizard for this rather than having people play Where's Waldo to find and move different roles...but that would make too much sense. Thanks for the helpful video.
Agreed
@@URTechDotCa Of course when I tried this it wouldn't take because the current domain forest/domain level was either 2000 or 2003 and when I tried to raise it to 2008 R2 it failed.
Part of the problem is that all this amazing tech is no longer sexy and doesn't get the attention it should. Ideally Microsoft would rewrite all their domain tools and unify most of it, but that's never going to happen now, so we are left with this breadcrumb situation sadly.
Fast, efficient, straight to the goal. Félicitations
Thanks for this short piece really helpful.
Maaaannn, thank you sooooo much, i just did this in small dental clinic, everything was just as you described
Great Video. Looking to do this some time this year. Just getting the 2022 licensing together for now
Thaks for the video. May is a stupid cuestion, but how can I transfer the whole user data from the old Server to the new?
I got a little problem about group policy, upon checking it copies to the new windows server 2022 but no setting has been moved. What extra step do I need to do? Thank you!
Thank you for this! i have to do this over the holiday.
Have fun! It's not that hard.
10:13 having issue with that part, ‘change’ button is greyed out.
Fixed now!
HI, great watch and so good thanks. When wanting to move over the Domain to Operations Masters , I only see my old server in both the Operations masters and transfer to, any ideas? Thanks
Straight to the point, cheers
will this bring over all of the dns records and gpo settings? What if i have a replicated dc in another site?
this was so helpful!!! THANKS!!!
Thanks so much. Doing this today!
do all the users/groups and gpos are migrated this way?
Very nice! Great Job. Very Helpful.
when going to MMC AD Schema - the new server shows unavailable? I get AD Schema Snap-in is not connected to the schema operations master. You will not be able to perform any changes.
Hi Carlos,
Could you recommend any tools for migrating user calendars and contacts?
After demoting the 2012 server removing it from the network, and shutting it down can i change the ip address of the new 2022 server to the ip address of the old server so i don't need to change all the dns settings for all the workstations and other servers?
Can anyone answer this?
Yes, but you really should be using DHCP for your clients. Makes this kind of a change seamless and stress free
Yes
After demoting the DC I was not able to login. Logon services unavailable. Reboot did not help;.
Thanks for this video. We are actually on the process of planning our migration for exactly the same versions of windows server and this one is an absulote rescue. One question though: does running a robocopy command to move all files from the old DC (2012) to the new DC (2022) should be done before promoting the new server to a DC or after? or it doesn't really matter? Thanks for the answer.
Thanks for this well made video. Does doing this also transfer all users/groups/computers etc. from the old AD server to the new one?
Through this process the users in AD are moved over? That's the only thing I didn't see covered in the video. I'll be following this video to help me with an AD migration from 2012 to 2022!
Yes. The new server got all the user accounts when it was made a domain controller. That's how AD works. The title of this video is ever so slightly technically misleading lol
@@craigmurray4746No worries! I followed this video when I did the migration and everything worked as expected! Thank you for this video and the clear explanation of how to do this!
What happens if my dc is also my dhcp server ? How can I demote it . I cannot have 2 dhcp servers and I still want them be together 😊
This is almost exactly my own situation that I'm working on. This video is wonderful! It's going to be my walkthrough through process, however I do have one questions. Rather than having to repoint every device/machine to a new DNS address, is it possible, once I demote the old one DC to swap the IP of the new box to the old one or am I asking for trouble trying to do that? Seems like it should be easy enough to do.
Changing the IP address of the servers would work, but this is also why best practice is to assign all client IP's with DHCP so that you make the change in one place and within a period all clients automatically pick up the new DNS server without needing to manually reconfigure anything.
Hi.
Is that Windows server 2012 or 2012 R2?
I've Windows server 2012, is it possible migrate from 2012 (not R2) to 2022?
@URTechDotCa I have to carry out this same task as you have done, however not because my old DC is from an earlier version of Windows but because I setup the dc on an evaluation version of server 2022 and apparently you can't convert an evaluation server DC to a full one. When I do this task, I won't need the old server so will just turn it off. But can I then change the IP address of the new DC to that of the old one so I don't have to update all the client machines with the IP of the new DC?
I have Windows Server 2012 R2 Domain Controller and intend to upgrade to Windows Server 2022. Additionally, my Group Policy Management is currently hosted on the same Windows Server 2012 R2 machine. The question is, will Group Policy Management also transfer to Windows Server 2022 after the process?
Hi. Very helpful. Just a quick question. I have in old server AD Certificates Services. How do migrate this too? I believed we cannot have multiple AD with certificates services.
great tutorial but unable to raise domain function lever from win2012 r2 to server 2022. error 'To update the domain functional level, the Active Directory Domain Controllers in the domain must be running the appropriate version of windows'. kindly help
If you follow this very well done video, be certain that SYSVOL is replicating before you demote your old DC. Fail to do and you may find no clients are able to authenticate or GPO's present on new DC. Check your "\Windows\SYSVOL\sysvol\DOMAIN NAME.WHATEVER" is the same as your old DC and test replication before demoting/decommissioning. Excellent guide non the less and very funny. DHCP "MORON"😄
hello @streborz, this is my error currently, can you kindly help me ?
I was just thinking this. This comment should be pinned.
Can you then completely remove/turn off the old DC, and shift the IP address back so the new DC has the old IP?
Ah, I was thinking the same. not sure if it will work. If you tried let me know please.
Theoretically it would work, but you will need to update your hosts in DNS for everything to jive correctly.
I think you CAN by adding the old ip address to the network adapter so you will then work on both ip's. Its more like a workaround right?
@Drakken_ Yeah it's a work around. Best practice is to have DHCP and get your changes made that way. Clients are meant to be far more flexible than servers after all
@Drakken_ Yeah it's a work around. Best practice is to have DHCP and get your changes made that way. Clients are meant to be far more flexible than servers after all
Thanks for the video. No FRS to DFR migration?
Thanks!!! do you know if its possible to move shared folders with access permissions from one server to another inside a domain without losing their respective permissons
Use the Server Storage Migration Service that comes in the free Windows Admin Center tool. Absolutely amazing how awesome that thing works
@@craigmurray4746 thanks ill give it a try next time, i had to rebuild all the user access after moving all the forlders haha
Wait, do you no longer have to upgrade the schema anymore after 2012r2?
Brilliant stuff thanks mil
Hey mate, QQ. Do i remove DNS delegation first or do i update dns delegation first? Migrating primary DC that has DNS from Win2012 to Win2019, so wondering as you skipped it in the first step and did NOT update but later on you removed it off the old server. Need to move the zones , DNS namespaces etc.
Amazing! Thank you!1
Can you power down the old DC and rename the new DC with the same name as the old DC and assign it the same static IP. This way you don't have to worry about changing DNS information on the workstation.
Can anyone answer this?
Yes
@@Secuwity Yes
Anyone can help me with my problem? my problem is when i tried to open group policy management in 2019 it says the network name cannot be found.
excellent guide. thanks for sharing
very straight forward
I noticed you stopped at 2016 when bringing up the domain and forest levels... How come it has not changed for 2022? - Did you miss the step or?
2016 is the latest the forest has been updated to.
You have to wait for Windows Server 2025
Nice video... although I am running into the "FRS is depreciated" error.
Will this method also migrate AD users and groups?
Yes, since it's not technically a migration in the true sense of the word.
43 / 5 000
I love your expression! As you say Boom!
EXCELENTE EL MEJOR
Hello,
in my company we have Domain in windows server 2003
is it possible to do this tutorial??
Thank you very much in advance
Not directly. You need to first use 2012R2 as a temporary measure cause some tech changed over the years so you can't have 2022 as a domain controller in a 2003 domain.
Hi, thank you for the tutorial.. but i have a few question. If i am in a server 2008R2, i need to upgrade to 2012R2 then upgrade to Server 2022 right? Do we need to upgrade the schema first? No need for schema upgrade? Thanks again for the video.
If you were talking about upgrading on the same hardware, then yes you'd have to jump to 2012R2 1st, then to 2022. You definitely do not need to update the schema before upgrading, one of the nice things about AD is how conservative you can be.
thx man
do you have tutorial on AD migration from Server 2008 to Server 2022 ?
Sorry, no but I expect is is the same process.
Will it also move or copy the group policies and the scripts as configured on the old Windows 2012 server AD?
i would also like to know this
How did it goes? Did it copy all the group policy and is policy working?
Unless you configured Group Policy to use the concept of the central store, then no, it won't have copied the policies from one server to the other. Scripts may have copied depending on where they were stored. If it was in the SYSVOL share it would be copied to the new server yes.
THANKS!
Thanks again, very instructional. Very useful.
Is this different VM?
Nice.
Can we export GPO winser 2012 to 2022?
ditto
Nice but way to fast for a person not as familiar with this.
Thanks!
Thank you!!!