Encountered error "Verification of replica failed. The specified domain [DomainName] is still using the File Replication Service (FRS) to replicate the SYSVOL share. FRS is deprecated." What can be done
hi, did you have to upgrade the schema? i run the upgrade process in a test environment and promoting the 2019 server, it done the schema upgrade as part of the process
This video instruction was fabulous. I've been procrastinating our migration to Server 2019 for some time. Now I'm ready to put this project behind me. Thank you for a very high-quality presentation.
When I was doing this activity I faced this issue "adprep failed to verify whether schema master has completed a replication cycle after last reboot" I also resolved this issue during migration from 2008 to 2019. Excellent Job and your way of explanation is highly appreciated with great learning experience, thanks bro.. Well done keep it up..
This is great! It shows step by step of what I need to do on both servers. I actually promoted Windows 2019 to DC without doing those 3 adprep's, but Win2019 seems to be smart enough to have completed them, since the registry entry shows scheme number of 88 right after the DC promo. Not sure if Win2019 is that smart, so I demoted it again and redid the adprep's, this time it confirmed that the schema has already been updated. This video is a big help!! Awesome.
So I've been checking online and everywhere they say we have to migrate from 2008>2012>2016>2019, i'm relieved that this video alleviates those tedious steps. Thanks.
Appreciated your perfect solution for Windows Servers Migration. I have used the same procedure and successfully Migrated on my Production Environment. Thanks you so much.
Really appreciate your effort to make this Video, it was very helpful to implement same steps in Production environment, wish you all the best, may god bless you
Great tutorial! One thing I did see though (unless I missed it somehow) was moving an authorized DHCP server from the old DC to new one. If you had only one DC, most likely it ran the DCHP as well. Otherwise, really great video.
Excellent Video. You have explained step by step very clearly, particularly the FSMO move. Great work buddy. It would be more useful If you show the DNS manager IP details after decom the 2008 R2.
Awesome tutorial! Thank you very much! By any chance that you also have a tutorial with regards to File Server Migration from 2008R2 over to 2019? Looking forward to your other videos!
Great tutorial, thank you. If needing to add a third DC (DC3 for example) to eventually remove the older DC1, should the "Replica From" on step at 15:30 in this tutorial, be be to replicate from "DC2" (which holds the 5 FSMOs), or would it be better to replicate from "Any Domain Controller"? Also, in that scenario (of 3 DCs), what is the best way to configure the NICs on all servers in regards to the IPv4 Preferred DNS Server settings (as shown in one section around 17:05 (or 18:16) and 18:30 in this tutorial?) - Ultimately, I will end up with DC2 and DC3 only, but I need DC1 to still be DC for a little longer - any tips on the above mentioned configuration are greatly appreciated! Thanks again.
@ 29:00 you are checking the SOA numbers matching. I just did this and my msdcs .domain SOA on my new machine is 2 numbers higher on my win2k19 than my 2k8 server. How do I fix this or does it matter? Everything else went Great. Excellent video.
When you open GPMC, it will first try to connect to the PDC role owner DC. At that point already we have transferred PDC Emulator role to Windows Server 2019 Domain controller, so GPMC connect with the windows server 2019 domain controller.
@@MSFTWebCast I'm following you and watched this video at least 3 times. I'm thinking to migrate my 2008 DC to 2019 DC this week. I tested at my test lab everything works fine. I had disscussed about User files at the own PCs. I thought that they will not be effected ( there's no user files and datas at 2008 DC ) but my friend advised me to take a full backup of all users. Did you test this issue at user computers? Thanks for your post :)
@@cuneytkurt3675 If you are just migrating Domain controllers than there is nothing going to change on client side. If users data's are on client computer than that is not going to impact. But if you have group policy with UNC paths, home directory or roaming profile in your setup and if it is stored on domain controller itself then you need to address it first or need to migrate to some other location. Hope I am making some sense here.
@@MSFTWebCast Thanks for your response. I will try this migration on live company structure. I hope this will work and wish not to have any issue on client site.
@@cuneytkurt3675 If you need any help let me know on my email address. One more thing which is not covered in video is you need to perform Sysvol ntfrs to dfsr migration (for group policy). Do that first and then start the migration. Do not remove your old dc's for atleast week or so.
Why did you join Domain prior to upgrading Schema on 2019? Was this just to make things easier ? When i did mine, i mounted CD(Image) on older VM, since that is the same VM you check in regedit after anyway to verify upgrade completed.
Could you update video with "How to demote Win2012R2 DC" ? In 2012, dcpromo is deprecated and I have to use the "Remove role" in Server Manager. But, when I run it, server was dejoined from domain and moved in Workgroup but DC and DNS Server roles ttill remain installed.
When I trying to promote this server to domain controller, I encountered this error "Verification of replica failed. The specified domain [DomainName] is still using the File Replication Service (FRS) to replicate the SYSVOL share. FRS is deprecated." how to solve this error?
Hi, I did the same steps in a lab environment and after promoting 2019 to DC , i cant see any entries in 2019 DNS server .No forward/reverse lookup zone and server showing cross mark
Hello, I am planning to upgrade my current DC which is on Windows 2008 R2 to Windows 2019. All the Domain controller in my environment is on Windows 2008 R2. I have 3 DC, out of which 2 DC are Global Catalog and one is DC. when i run "netdom query fsmo" I see the result except for "infrastructure master" everything is on my Primary DC . what steps should i take to move infrastructure master which is on other DC to my Primary DC ? Or Am i able to upgrade my Primary DC with out moving infrastructure master to primary DC ? What safety measures should i take? Thank you,
You can manually transfer Infrastructure master role to Root DC. 1. Take a backup before you start migration. 2. First manually upgrade schema on Schema master (in your case root dc) 3. Introduce Windows Server 2019 as a member server. 4. Promote Windows Server 2019 as a additional domain controller. 5. Wait for replication to complete successfully. 6. Transfer the FSMO roles to Server 2019 DC. 7. Migrate DHCP, File Server Shares or print service to server 2019. 8. Test with one user account that everything is working file with them like group policy and other settings. 9. If everything is working fine, then start decommissioning the server 2008 R2 DC. Note: Make sure that your Root DC will be the last to decommission.
@@MSFTWebCast Thank you very much for your quick response. 1. Do you have any steps or video which i can follow to manually transfer infrastructure master role to Root DC. 2. In your second step you mentioned "First manually upgrade schema on Schema master (in your case root dc)" , are you referring to schema ver. 47 to new Schema ver 88. ?
I get this message when I select my domain and click 'Next': Replica verification failed. The forest functional level is not supported. To allow the installation of a domain or domain controller on Windows Server 2019, the forest functional level must be at least Windows Server 2008 or a later version.
DCHP is far simpler..... run the following from Commmd Prompt netsh dhcp server export all so for example: netsh dhcp server export c:\dhcp.txt all copy that text file to new server, then install dhcp role.. but do not add scope (when it comes to define scope, leave blank and click "Next") after install of dhcp role, open command prompt and run : netsh dhcp server import all ie: replace with physical path.
hi, many thanks for tutorial, extremally helpful. i tested the schema upgrade in a test environment and i did not need to do it as adding and promoting the 2019 server, it must of done it during DC promote. can you confirm if this was the case? thanks in advance. the version was 47 before promoting. when running adprep commands it stated, already upgraded Ajay
We can manually update the schema or we allow it to update automatically during the AD DS configuration (I mean when we add windows server 2019 as an additional domain controller). But I prefer to use manual method to for more surety. Note: You need to insert the Windows server 2019 ISO image while running the adprep commands.
Hi ! Thank you for this great tutorial. I used for migrate some servers in the past. One question: it's right that windows server 2022 use the same schema number (88) of 2019 ?.
Before i start, Can this same step work for Active Directory Migration From Windows 2003 to Windows Server 2016? If not do you have a detailed video as this?
I deeply appreciate your effort to provide the cristal clear tutorial it would be very much helpful to the people. I have my domain controller of windows server 2008 STANDARD in a production environment, Can I migrate it to server 2012 R2 or server 2019, using the same steps, or do I need to upgrade my 2008 standard to R2 first?
Microsoft Documents says that it needs Server 2008 R2 but with Server 2008 it also work. You can migrate Server 2008 to 2012 R2 or Server 2019. Keep in mind that you need to upgrade FRS to DFSR.
Excellent demo and explanation¡ Which is your suggestion to test applications running in windows server 2008 r2 domain before migrating to windows server 2019 functional and domain level?
One question: is it mandatory run adprep BEFORE migrating domain ? Is not possible migrate domain leaving the original schema and raise forest/domain level AFTER migration ?
NO, you need to prepare the existing forest to support new version of Windows domain controller. You can manually update the schema before adding new domain controller or if it is already not updated then the AD DS wizard will update the schema (if you have sufficient privilege).
can you migrate (or copy) all objects and GPO to a new domain with another domain name ? what about all PC members of the domain ? how to manage Exchange messaging (2010 version which should be migrated in 2019 and integrated into the new domain), Skype, existing shares, all services and hundred of servers etc. ... all dependent on the existing domain?
Hello, thanks for the video, i am planning do the migration to 2008 R2 to 2022, while the migration is running, the AD of the 2008R2 will be suspended or the users can work normally, because the server have DNS, DHCP and AD DS + FortiAD sync.
I've been an admin for a long time. A lot of changes of AD get made, but very few seem to deal with demoting and changing the cert services - which is kind critical in background when moving your AD forwards :/
FSMO roles has nothing to with DNS SOA number. If SOA numbers are not same on both DNS server that means DNS replication is not completed yet. Once replication completes, both SOA numbers will be same.
If you want new domain then why migration? If your are asking for migration with new domain name. 1) Migrate Active Directory and 2) Rename Active Directory Domain Name.
I've following you for quite sometime now and all your videos I would say, they are all amazing. Straight to the point and helpful. Next Year 2024 around Jan or Feb, we are planning to migrate our on-prem active directory. We have 4 active directory, 2x in AWS they are both WinServ 2012, 2 onprem, 1x 2008 R2 and 1x 2012. Our Domain and forest function level are both WinSer 2008 R2. The idea is, we want to reuse the same IP and hostname of this 2008 R2 AD. Would you please just help me to layout the steps like what you did here in this video? I saw that only 1 AD you have here. I am hoping to receive an answer from you brother.. Again, thank you very much for all your hard work to put all of these up. Kudos to you.
good morning and thanks for video i have a problem when i try to add windows controller domain to an exist domain error is forest not supported but i have execute adprep and i have forest whit 2018 level how can i do ? thanks Alberto
Check replication between all the domain controllers and then raise the forest and domain functional level. Manually update the Active directory schema.
After I finish this process can I leave my old 2008r2 server in the domain so users can access old projects? Is that going to be problem since end of life on 2008 is coming soon? Do I need to rebuild it and buy 2016 with appropriate cals?
Shall I use windows 2008 IP to new windows 2019 domain after transfer all roles? My all clients and systems pointing to dns1 and dns2 are windows 2008 IP’s.
Can I follow your video and then at the end change the ip address of the new server 2019 to the old ip of the server 208 r2 and then just give the old server a new ip address? My DHCP dns and some other items are pointed at the old server and I dont want to change those items if I dont have to. Thoughts on changing the ip address after completion. Also I am wondering about changing the Server name to the same as old one as well.
Yes, you can do it without any issue. Just make sure those changes reflects in DNS (I want to say dont remove server 2008 R2 DC) and make sure both DCs can replicates with each other. (please do this after office ours). About name changes: Yes, agree with you with name changes. Note: Even I want to include those things in this video but I thought that will be confusing to do that. Ask for help if needed...Good Luck.
So I want to make sure I have the order correct on doing this. I have promoted the new server 2019 to a domain controller. Checked replication to the old and back to the new controller. Transferred the FSMO roles. I have not demoted the old R2 2008 domain controller yet. Now which order should I change the ip address and server names in? My thought is to change the ip address of the old R2 controller first, Then change the name on the old R2 controller. Reboot the old R2 server and then go to the new 2019 and change its IP to what the old one was and then change its name as well, reboot the new server. Next remove the DNS entry from the dns manager on the new server for both the old R2 server and New 2019 server and clear the DNS cache as well on the new 2019 server. Reboot both servers again. Will this method /order work? Unfortunately I don't have a test environment larger enough to test this. I will have snapshots to quickly revert back if needed.
@@scottboucher5329 After 2008 R2 reboot one more time check replication with 2019. DNS entries will update automatically but just check it again after 2008 r2 reboot for DNS resource records.
21:59 To prevent the need to constantly go back and forth with replication, explained Inter-Site Transports and click "ip"... Right click site link in the right pane, and go to "properties". change value from 'Replicate every" to 15 minutes (default is 180) 3 hours Regardless in some cases, when you click ok,, it should replicate "immediately" and should not requite much effort to get it done correctly. :) Windows versions after 2008 should be 15 minutes by default.... as any changes to replication time-frame must be done both ways... so if needed, it will be under same location.
Encountered error "Verification of replica failed. The specified domain [DomainName] is still using the File Replication Service (FRS) to replicate the SYSVOL share. FRS is deprecated." What can be done
Eliminated the error with this link techcommunity.microsoft.com/t5/Storage-at-Microsoft/Streamlined-Migration-of-FRS-to-DFSR-SYSVOL/ba-p/425405
Try this link
th-cam.com/video/jl4vo5rD18A/w-d-xo.html
Thisone works for me.
www.tech-faq.net/dfs-migration-active-directory/
Check this : th-cam.com/video/jl4vo5rD18A/w-d-xo.html
same error, what the solution?
This video is *still* the gold standard. I did this migration today and this video was a fantastic walk through of the process.
Thank you David.
hi, did you have to upgrade the schema? i run the upgrade process in a test environment and promoting the 2019 server, it done the schema upgrade as part of the process
@@1ajaypaul sorry, I don't recall if I had to do the schema upgrade separately
@@davidjoelhall ok. Thanks for replying. After a little research. There’s no need of your introducing a newer DC.
Thank you for this concise explanation of migrating from 2008R2 to 2019 AD
This video instruction was fabulous. I've been procrastinating our migration to Server 2019 for some time. Now I'm ready to put this project behind me. Thank you for a very high-quality presentation.
When I was doing this activity I faced this issue "adprep failed to verify whether schema master has completed a replication cycle after last reboot" I also resolved this issue during migration from 2008 to 2019. Excellent Job and your way of explanation is highly appreciated with great learning experience, thanks bro.. Well done keep it up..
Thank you..
This is great! It shows step by step of what I need to do on both servers. I actually promoted Windows 2019 to DC without doing those 3 adprep's, but Win2019 seems to be smart enough to have completed them, since the registry entry shows scheme number of 88 right after the DC promo. Not sure if Win2019 is that smart, so I demoted it again and redid the adprep's, this time it confirmed that the schema has already been updated. This video is a big help!! Awesome.
Such a big thank you for this tutorial. Been years since I did this last and my eyes were starting to roll till I found this. You're worth more money.
Very useful video dear. Very nice presentation 👍👍
So I've been checking online and everywhere they say we have to migrate from 2008>2012>2016>2019, i'm relieved that this video alleviates those tedious steps.
Thanks.
If you're doing upgrades, then it's recommended to do that. This video is migrating to another VM/server running a later version of the OS.
Best video i have watched ever. Its working perfectly for me. Thank You
Appreciated your perfect solution for Windows Servers Migration. I have used the same procedure and successfully Migrated on my Production Environment. Thanks you so much.
Great to hear!
Great job and your step by step process made my job look so simple. You're my hero and keep up the good work !!! THANK YOU !!!
Really appreciate your effort to make this Video, it was very helpful to implement same steps in Production environment, wish you all the best, may god bless you
Thank You!
Excellent tutorial. I have two sites which are moving to Server 2019 and this was very helpful and easy to follow. Thank you!
This worked very well for me, thank you for your complete and detailed instruction
Great to hear!
Excellent instruction. Followed to the letter and everything worked great.
Glad it helped
It worked for met to migrate an SBS 2011 server to a Windows 2022 standard server. I owe you a good beer!
Thank You for the beer.
Excellent Video. The steps you have provided are very systematic and easy to follow. Keep it up !!! Looking forward for more video's from you
Great tutorial! One thing I did see though (unless I missed it somehow) was moving an authorized DHCP server from the old DC to new one. If you had only one DC, most likely it ran the DCHP as well. Otherwise, really great video.
Yes, we have dedicated video on it.
Thaks for this video, It help me to migration in a client, thaks for your work from Colombia
Excellent Video. You have explained step by step very clearly, particularly the FSMO move. Great work buddy. It would be more useful If you show the DNS manager IP details after decom the 2008 R2.
Noted
Awesome tutorial! Thank you very much! By any chance that you also have a tutorial with regards to File Server Migration from 2008R2 over to 2019? Looking forward to your other videos!
Thanks for the wonderful video and clear instructions
Great tutorial, thank you. If needing to add a third DC (DC3 for example) to eventually remove the older DC1, should the "Replica From" on step at 15:30 in this tutorial, be be to replicate from "DC2" (which holds the 5 FSMOs), or would it be better to replicate from "Any Domain Controller"? Also, in that scenario (of 3 DCs), what is the best way to configure the NICs on all servers in regards to the IPv4 Preferred DNS Server settings (as shown in one section around 17:05 (or 18:16) and 18:30 in this tutorial?) - Ultimately, I will end up with DC2 and DC3 only, but I need DC1 to still be DC for a little longer - any tips on the above mentioned configuration are greatly appreciated! Thanks again.
you should always replicated from Primary Domain Controller. and it would better to give Ip address of SRV which you are migrating the PDC role to.
This was nicely done and very accurate. Thank you for putting it together!
Thanks for tutorial bro, i will implement your tutorial into my customer environment and before doing that i will take a snapshot on it.
Yeah backups or snapshots are necessary. You can also create a clone from snapshot to test the migration first.
@ 29:00 you are checking the SOA numbers matching. I just did this and my msdcs .domain SOA on my new machine is 2 numbers higher on my win2k19 than my 2k8 server. How do I fix this or does it matter? Everything else went Great. Excellent video.
It will sync automatically, not to worry about it.
I just checked again this morning and you are correct. THANK YOU for this video. Instructions are Excellent!
Thanks for this tutorial, very detailed and worked fine.
Warm Greetings for this awesome Tutorial
Thank you!
Your videos really awesome
Thank you so much.
30:19
which option made domain controller have decided that the new server (windows server 2019) is the current domain controller ?
When you open GPMC, it will first try to connect to the PDC role owner DC. At that point already we have transferred PDC Emulator role to Windows Server 2019 Domain controller, so GPMC connect with the windows server 2019 domain controller.
@@MSFTWebCast Thanks
Great Video , from all the videos on TH-cam, this is the best XD
How do I give you all the kudos?! Thank you for this video. It saved me today! Huge, huge help! There is no way I can thank you enough for this.
Great to hear!
@@MSFTWebCast I'm following you and watched this video at least 3 times. I'm thinking to migrate my 2008 DC to 2019 DC this week. I tested at my test lab everything works fine. I had disscussed about User files at the own PCs. I thought that they will not be effected ( there's no user files and datas at 2008 DC ) but my friend advised me to take a full backup of all users. Did you test this issue at user computers?
Thanks for your post :)
@@cuneytkurt3675 If you are just migrating Domain controllers than there is nothing going to change on client side. If users data's are on client computer than that is not going to impact. But if you have group policy with UNC paths, home directory or roaming profile in your setup and if it is stored on domain controller itself then you need to address it first or need to migrate to some other location. Hope I am making some sense here.
@@MSFTWebCast Thanks for your response. I will try this migration on live company structure. I hope this will work and wish not to have any issue on client site.
@@cuneytkurt3675 If you need any help let me know on my email address. One more thing which is not covered in video is you need to perform Sysvol ntfrs to dfsr migration (for group policy). Do that first and then start the migration. Do not remove your old dc's for atleast week or so.
running ad connect on old 2012 server, any extra steps i should take befroe i modify the schema at all?
Why did you join Domain prior to upgrading Schema on 2019? Was this just to make things easier ?
When i did mine, i mounted CD(Image) on older VM, since that is the same VM you check in regedit after anyway to verify upgrade completed.
Thanks for this wonderful tutorial
Thanks for your helpful guide. By the way, can we change the IP address of Windows 2019 to be as IP address of Windows 2018 ex-PDC?
Yes, you can. Once everything settle down you can switch back to the old IP address.
@@MSFTWebCastThank you. What's the best way to change PDC computer name?
excellent explanation. Thank you
24:50 transfer fsmo roles
28:27 check DNS replication
30:34 remove AD services from 2008 (no need to uncheck GC first)
Could you update video with "How to demote Win2012R2 DC" ? In 2012, dcpromo is deprecated and I have to use the "Remove role" in Server Manager. But, when I run it, server was dejoined from domain and moved in Workgroup but DC and DNS Server roles ttill remain installed.
When I trying to promote this server to domain controller, I encountered this error "Verification of replica failed. The specified domain [DomainName] is still using the File Replication Service (FRS) to replicate the SYSVOL share. FRS is deprecated." how to solve this error?
Cheers for the video, only sticking point was 37.57, when looking into the regedit, was unable to get the schema a cross.
Excellent really enjoyed the steps you showed . Made it look very easy thank you
Great Tutorial
Great video!!! Saved a lot of time.
Great to hear!
Hi,
I did the same steps in a lab environment and after promoting 2019 to DC , i cant see any entries in 2019 DNS server .No forward/reverse lookup zone and server showing cross mark
Hello, I am planning to upgrade my current DC which is on Windows 2008 R2 to Windows 2019.
All the Domain controller in my environment is on Windows 2008 R2.
I have 3 DC, out of which 2 DC are Global Catalog and one is DC.
when i run "netdom query fsmo" I see the result except for "infrastructure master" everything is on my Primary DC .
what steps should i take to move infrastructure master which is on other DC to my Primary DC ?
Or Am i able to upgrade my Primary DC with out moving infrastructure master to primary DC ?
What safety measures should i take?
Thank you,
You can manually transfer Infrastructure master role to Root DC.
1. Take a backup before you start migration.
2. First manually upgrade schema on Schema master (in your case root dc)
3. Introduce Windows Server 2019 as a member server.
4. Promote Windows Server 2019 as a additional domain controller.
5. Wait for replication to complete successfully.
6. Transfer the FSMO roles to Server 2019 DC.
7. Migrate DHCP, File Server Shares or print service to server 2019.
8. Test with one user account that everything is working file with them like group policy and other settings.
9. If everything is working fine, then start decommissioning the server 2008 R2 DC.
Note: Make sure that your Root DC will be the last to decommission.
@@MSFTWebCast
Thank you very much for your quick response.
1. Do you have any steps or video which i can follow to manually transfer infrastructure master role to Root DC.
2. In your second step you mentioned "First manually upgrade schema on Schema master (in your case root dc)" , are you referring to schema ver. 47 to new Schema ver 88. ?
How to Transfer FSMO Roles:
th-cam.com/video/u2AOryyOmv4/w-d-xo.html
Went like a glove. Thanks mate!
I get this message when I select my domain and click 'Next':
Replica verification failed. The forest functional level is not supported. To allow the installation of a domain or domain controller on Windows Server 2019, the forest functional level must be at least Windows Server 2008 or a later version.
Verify the functional levels of the forest and, if your forest has more than one domain, the functional levels of each domain as well.
What about doing an upgrade in place on a Windows 2008 domain controller? Upgrading to server 2012 then 2016/19? How would the steps vary?
This excellent. I wish you also would have also included DHCP as one of the services needed to migrate over. Thank you!
DCHP is far simpler..... run the following from Commmd Prompt
netsh dhcp server export all
so for example: netsh dhcp server export c:\dhcp.txt all
copy that text file to new server, then install dhcp role.. but do not add scope (when it comes to define scope, leave blank and click "Next")
after install of dhcp role, open command prompt and run : netsh dhcp server import all
ie: replace with physical path.
hi, many thanks for tutorial, extremally helpful.
i tested the schema upgrade in a test environment and i did not need to do it as adding and promoting the 2019 server, it must of done it during DC promote. can you confirm if this was the case? thanks in advance.
the version was 47 before promoting. when running adprep commands it stated, already upgraded
Ajay
We can manually update the schema or we allow it to update automatically during the AD DS configuration (I mean when we add windows server 2019 as an additional domain controller). But I prefer to use manual method to for more surety.
Note: You need to insert the Windows server 2019 ISO image while running the adprep commands.
@@MSFTWebCast many thanks for the reply.
Hi ! Thank you for this great tutorial. I used for migrate some servers in the past.
One question: it's right that windows server 2022 use the same schema number (88) of 2019 ?.
Yes, correct, There is no schema update in server 2022.
@@MSFTWebCast Thank you
Very understandable, love it. Thank you.
Glad it was helpful!
Before i start, Can this same step work for Active Directory Migration From Windows 2003 to Windows Server 2016? If not do you have a detailed video as this?
Will this steps work on Windows Server SBS 2011???
I deeply appreciate your effort to provide the cristal clear tutorial it would be very much helpful to the people.
I have my domain controller of windows server 2008 STANDARD in a production environment, Can I migrate it to server 2012 R2 or server 2019, using the same steps, or do I need to upgrade my 2008 standard to R2 first?
Microsoft Documents says that it needs Server 2008 R2 but with Server 2008 it also work. You can migrate Server 2008 to 2012 R2 or Server 2019. Keep in mind that you need to upgrade FRS to DFSR.
Excellent demo and explanation¡ Which is your suggestion to test applications running in windows server 2008 r2 domain before migrating to windows server 2019 functional and domain level?
One question: is it mandatory run adprep BEFORE migrating domain ? Is not possible migrate domain leaving the original schema and raise forest/domain level AFTER migration ?
NO, you need to prepare the existing forest to support new version of Windows domain controller. You can manually update the schema before adding new domain controller or if it is already not updated then the AD DS wizard will update the schema (if you have sufficient privilege).
awesome video, thank you!
Perfect 🌺🌺🌺🌺
Great Tutorial!!! Congratulations!!! Can the same be used to migrate a 2008 R2 Foundation server to 2019 STD server'
Perfect! Great video, thank you very much!
Thanks for your tutorials. Great job :-)
can you migrate (or copy) all objects and GPO to a new domain with another domain name ?
what about all PC members of the domain ?
how to manage Exchange messaging (2010 version which should be migrated in 2019 and integrated into the new domain), Skype, existing shares, all services and hundred of servers etc. ... all dependent on the existing domain?
Very helpful. Thank you.
Thanks!!, Great
Thank you for this! Question, can the windows 2019 DC use a 2008r2 certificate master or will the certificate master have to up migrated as well?
Not necessary but you wont get some new features of certificate templates.
Hello, thanks for the video, i am planning do the migration to 2008 R2 to 2022, while the migration is running, the AD of the 2008R2 will be suspended or the users can work normally, because the server have DNS, DHCP and AD DS + FortiAD sync.
It is side by side migration, so your old server will be in running condition and users can work normally without any issue.
@@MSFTWebCast thank you for answering, is possible do a video of renaming Domain?
@@AkumetsuOne Yes already we have video on domain renaming: th-cam.com/video/fS3cpFd2jxE/w-d-xo.html
I've been an admin for a long time. A lot of changes of AD get made, but very few seem to deal with demoting and changing the cert services - which is kind critical in background when moving your AD forwards :/
Hello - after i transferred the FSMO roles, i checked the DNS and the 2019 server shows(648) and the 2008 server shown (647). is this correct?
FSMO roles has nothing to with DNS SOA number. If SOA numbers are not same on both DNS server that means DNS replication is not completed yet. Once replication completes, both SOA numbers will be same.
Thank you!
Great job man . Amazing video.Really helpfull.
Thank You.
Great video. Where in those steps we need to migrate the DHCP?
Can this be done with Server 2019 Essentials?
Fabulous
from where i can get the adprep utility to upgrade 2008 forest ?
It will be in Windows Server ISO image.
thanks for the video. lengthy but good one.
Is this possible with 2008R2 --> 2019 in a different, brand new domain?
If you want new domain then why migration? If your are asking for migration with new domain name. 1) Migrate Active Directory and 2) Rename Active Directory Domain Name.
Does this process work if you want server 2019 to have a new domain name?
You need to rename you active directory domain for that. This will retain old domain name just upgrade the domain controllers.
@@MSFTWebCast so best practice would be to follow this lesson and migrate first, then change the domain name?
I've following you for quite sometime now and all your videos I would say, they are all amazing. Straight to the point and helpful. Next Year 2024 around Jan or Feb, we are planning to migrate our on-prem active directory. We have 4 active directory, 2x in AWS they are both WinServ 2012, 2 onprem, 1x 2008 R2 and 1x 2012. Our Domain and forest function level are both WinSer 2008 R2. The idea is, we want to reuse the same IP and hostname of this 2008 R2 AD. Would you please just help me to layout the steps like what you did here in this video? I saw that only 1 AD you have here. I am hoping to receive an answer from you brother.. Again, thank you very much for all your hard work to put all of these up. Kudos to you.
Send me an email, will give you the guideline. Note: find my email address on channels about page.
@@MSFTWebCast Hi brother, we will send you an email tonight. Thank you for your response.
Great video, thank you! Saved me a lot of time :)
Thanks a lot. It's precisely explained it.
hi all your videos are really helpful and professional .do you have video how to Migrating Shared Folder from Server 2008R2 to Server 2019/2022
Migrating Shared Folder from Server 2003 to Server 2019: th-cam.com/video/GKslGHFM3JM/w-d-xo.html
Many thanks to you, you are a professional and courteous person
good morning and thanks for video
i have a problem when i try to add windows controller domain to an exist domain error is forest not supported
but i have execute adprep and i have forest whit 2018 level
how can i do ?
thanks Alberto
First check both Domain and Forest functional level. You also need to make sure sysvol is using DFS not FRS.
@@MSFTWebCast many thank
do you know guide to change in dfs for this ?
thanks Alberto
@@Omeromuscio I have not created video on it yet, but surely video will be there. You can get very good guide on rebel admins website.
Thank you :)
verification of the replica failed the forest functional level not supported to install I was the update schema version
Check replication between all the domain controllers and then raise the forest and domain functional level. Manually update the Active directory schema.
Perfect
thank you so much for your help. Very good tutorial
After I finish this process can I leave my old 2008r2 server in the domain so users can access old projects? Is that going to be problem since end of life on 2008 is coming soon? Do I need to rebuild it and buy 2016 with appropriate cals?
Just robocopy the files over to your new server :)
Shall I use windows 2008 IP to new windows 2019 domain after transfer all roles? My all clients and systems pointing to dns1 and dns2 are windows 2008 IP’s.
This is what I will be doing. Best way to avoid any over looked static entries out on your network.
really useful
Glad to hear that
Awsome man!!!
What about certificate of authority stuff?
Check the AD CS series playlist.
Can I follow your video and then at the end change the ip address of the new server 2019 to the old ip of the server 208 r2 and then just give the old server a new ip address? My DHCP dns and some other items are pointed at the old server and I dont want to change those items if I dont have to. Thoughts on changing the ip address after completion. Also I am wondering about changing the Server name to the same as old one as well.
Yes, you can do it without any issue. Just make sure those changes reflects in DNS (I want to say dont remove server 2008 R2 DC) and make sure both DCs can replicates with each other. (please do this after office ours).
About name changes: Yes, agree with you with name changes.
Note: Even I want to include those things in this video but I thought that will be confusing to do that.
Ask for help if needed...Good Luck.
So I want to make sure I have the order correct on doing this. I have promoted the new server 2019 to a domain controller. Checked replication to the old and back to the new controller. Transferred the FSMO roles. I have not demoted the old R2 2008 domain controller yet. Now which order should I change the ip address and server names in? My thought is to change the ip address of the old R2 controller first, Then change the name on the old R2 controller. Reboot the old R2 server and then go to the new 2019 and change its IP to what the old one was and then change its name as well, reboot the new server. Next remove the DNS entry from the dns manager on the new server for both the old R2 server and New 2019 server and clear the DNS cache as well on the new 2019 server. Reboot both servers again. Will this method /order work? Unfortunately I don't have a test environment larger enough to test this. I will have snapshots to quickly revert back if needed.
@@scottboucher5329 After 2008 R2 reboot one more time check replication with 2019.
DNS entries will update automatically but just check it again after 2008 r2 reboot for DNS resource records.
Great tutorial. Thanks.
21:59 To prevent the need to constantly go back and forth with replication, explained Inter-Site Transports and click "ip"... Right click site link in the right pane, and go to "properties". change value from 'Replicate every" to 15 minutes (default is 180) 3 hours
Regardless in some cases, when you click ok,, it should replicate "immediately" and should not requite much effort to get it done correctly. :)
Windows versions after 2008 should be 15 minutes by default.... as any changes to replication time-frame must be done both ways... so if needed, it will be under same location.
God bless, really grateful for the video..... do you have video on Windows server 2008r2 file server migration to Windows server 2019?
great video, this helped a lot
Good tutorial Thanks
Glad it helped