This is a very useful video and helped me a lot - would you be able to answer some additional questions. - I have 4 DC across two sites. 2 on each. 2012 R2 and want to upgrade to 2019 now. (Hyper-V failover cluster ) - They also hold DNS and DHCP roles and replicate Question 1 = how my client and other services will get DNS resolution as IP address and DNS name is different for the new server. 2019 Question 2= Is there any impact of Hypervisor as my Hyper-V hosts are still on 2012 Question 3 = How to migrate file servers in DFS replication scenario
Hi, I have tried to migrate our ad windows server 2012R2 to Windows server 2019 Core, it's migrated successfully but schema version and system schema version showing 58. What should be do in this case.Please suggest...
Great video... One question... Would it be a problem if the 2k19 is first joined to the domain and then the ADDS role is installed?... Or does it have to be at workgroup as in the video?...
hi if my current AD having features like DHCP, WSUS, etc, when i replicate the current AD to new AD and make it secondary, is the DHCP, WSUS auto replicate as well? or i need to reinstall the features also in my secondary AD?
Adprep encountered an LDAP error. Error code: 0x32. Server extended error code: 0x5, Server error message: 00000005: SecErr: DSID-031527D3, problem 4003 (INSUFF_ACCESS_RIGHTS), data 0
At 13:51 are you setting up a new DSRM password or are you using the one from winserv2012R2 ? Also, since you removed WinServ2012 why you keep in your 2019 adapter's settings as second dns the ip address of the 2012 server?
I would giess it would be new,,,,, DSRM is needed for install and removal. of DC. Up to you weather you remove ip, or change, but its not neccessary in the video i don't think. because that's not the main point.
One migration completes successfully and you transferred all FSMO roles to new DC. Wait for few days and switch the IP addresses first. Again wait and monitor. If everything works normally, then demote the old DC's. If demotion is successful then you can rename the new DC and assign the old name. If you have two DC's then this can be done faster.
Thank you for posting this Video, the instructions are very clear. I have a 2012R2 Server that also has Hyper-V and some VMs. I need to move everything to the new 2019 Server. In what order would you suggest doing this? Make the new 2019 Server a DC first and then add the Hyper-V role or the other way around? I will be doing a "share nothing" migration of the VMs. Any advice would be most welcome.
38:09 I notice you raised level after de-mote DC from older version... However, for me on new server i get different: "The following Active Directory Domain Controllers are running earlier versions of windows:" This would have made more sense (i would have thought), because you connected to existing domain anyway when you set up on 2019 My old server still has DC installed, but it's no longer a Catalog Server now. Must i first remove roles before raising functional level on new?
Raise functional level after removing Domain Controller role from old server. It is not necessary to raise the functional level instantly, you can take some time and then do it later.
good video, everything went smooth, but I noticed that after I removed AD from 2012 server, I still see the 2012 server listed under Sites and Services. I also still see it listed as a name server in DNS manager of the 2019 server. Do we just need to manually delete these old records from DNS ?
What if you already have Win2k12r2 DC1 and DC2 replication to each other? 1. Do you choose Replication from "Any domain controller" during promoting Win2K19-DC1 to a domain controller? 2. What will the Alternate DNS Server IP on Win2K19-DC1 be? Can it be from either Win2k12r2-DC1 or DC2?? etc.
Ans:1 You can choose any domain controller but I would go with the PDC (who holds the all FSMO roles, specially Domain naming master and infrastructure master). Ans:2 You can set both DNS server address as alternate DNS server.
Hello, Good Morning! This excellent video just have few clarification as i need to migrate existing Primary domain controller from windows server 2012 R2 to Windows Server 2019 i have few questions only: 1. In my case i have both primary and secondary on windows server 2012 R2 and want to migrate it windows server 2019. Please correct if i ma wrong with the steps mentioned below: a. First need demote the additional domain controller b. Second need to format the server and install windows server 2019 R2 and follow the process explained in your video anything else i need to do before demoting the additional domain controller? Please guide the steps if need to follow some different procedure. 1. After following the steps mentioned above the New Windows Server 2019 will be acting as primary domain controller? 2. The existing clients will not require reregistration with new domain controller as it's migrated already? 3. In the second video you have explained how to add Additional domain controller apart from that any additional steps to be performed as after demoting additional domain controller from windows server 2012 and reinstall windows server 2019 and reconfigure as additional domain controller? Have a good day! Kind Regards, Khan.
Hello You are only one giving proper video and clarity. Quick question:- Before Promote Server 2022 as an ADC. Do we need to follow 1 Step:- Prepare Existing AD forest for Server 2022 DC using Adprep command? we can't directly do migration?
Windows 2012 R2 is End of life on October 2023 I would like to plan migrations of Servers with exchange. My Current Infra Servers are running VMWare 1-Primary Domain Controller**(Win2012)** TLS.LOCAL 1-Secondary Domain Controller + File Server (Win2012) 2-RODC :-UK-RODC**(Win2012)** 2 Child Domain**(Win2012)** CDC01.BLR.TLS.LOCAL CDC02.BLR.TLS.LOCAL 1 Exchange Server 2016 (CU23) (No DAG Configured) (Win2012) C Drive (OS) NTFS DB01**(ReFS Partition)** DB02**(ReFS Partition)** DB03**(ReFS Partition)** DB04**(ReFS Partition) ** Now exchange servers are live. how can we migrate Domain Controllers and Exchange Server to Windows Srv 2019 or 2022? Directly Because Exchange 2016 will support OS 2016 right? Suppose i am planning to migrate Exchange 2019 with OS 2022? What is to be done? -What is the best practices and order to Migrate Servers order? -When Exchange Server is running, whether need to be migrate All Domain controllers and Child Domains First then migrating Exchange Server? Please share me the links or videos steps migration with advice. i am not getting proper links or steps to for huge changes in infrastructure. Can you advise me
Can i keep same Computer Name or will i have issues with transferring FSMO roles via POwershell? Since domain name gets transferred, the only thing unique will be the IP addres, so i think this will be a show stopper,, Unless you CNAME or something to forward all requests to new as FQDN is everything in a business..
@@MSFTWebCast hello Thanks for making this wonderful video, but i have one question - since we have already installed DNS role during joining of the new Server 2019 DC to DC 2012, so what will happen if we change the new 2019 server IP and name back to old 2012 server IP and name? will DNS will work. As in our current scenario we have to migrate 2012 Server to Server 2019, but want to keep the same IP and Name of existing 2012 server. Also what will happen to existing workstation that joined to old 2012 Domain, do we have to change the DNS settings in all clients manually if we dont want to retain the old name and IP? Please advise
hello Thanks for making this wonderful video, but i have one question - since we have already installed DNS role during joining of the new Server 2019 DC to DC 2012, so what will happen if we change the new 2019 server IP and name back to old 2012 server IP and name? will DNS will work. As in our current scenario we have to migrate 2012 Server to Server 2019, but want to keep the same IP and Name of existing 2012 server. Also what will happen to existing workstation that joined to old 2012 Domain, do we have to change the DNS settings in all clients manually if we dont want to retain the old name and IP? Please advise
1. For a time being you have to use the new dns name and new IP address on Server 2019 DC. After checking (and monitoring) the replication and AD services for a while you can eliminate the old Domain Controller (Server 2012), if everything is going good. 2. After removing the old DC, you can rename the server 2019 DC to old name as well as you can change the IP address to the old one. 3. Also what will happen to existing workstation that joined to old 2012 Domain, do we have to change the DNS settings in all clients manually if we dont want to retain the old name and IP? Answer: You haven't mentioned that you are using DHCP in your network or not. But if you have DHCP server then you can add the new DC's IP as a secondary DNS servers address. Client will automatically get the second DNS servers address and they can use that DNS server for any name resolution. If you are not using the DHCP server then you can switch the old IP. I mean assign new IP address on old DC and assign old IP on new DC. So without any issue client can contact DNS. Feel free to ask again if you have any doubts.
can i change the hostname of my new dc server. for example like the hostname of my server is winsvr2019 to the dcsvr1 which is the hostname of the old server(given i demoted and disconnected this from the network)? Old server hostname dcsvr1(demoted and disconnected and renamed olddcsvr1) New Server hostname windcsvr promoted as new server as dcsvr1(i use this as a new server)
The one thing I would have liked to see is DHCP included. My old DC is a DC, DNS and DHCP server so having that last item included in this video would have been very helpful. But thanks for this one.
first Thank you so much for this video I have a question after we migrate to 2019 server if we need to change the name of 2019 server and IP address same as 2012 server can we do that? because some application and file share its point to 2012 server (I Don't need to make everything new :D ) thanks
You can migrate the DHCP server as well. You just need to export the configuration from old dhcp server. 1) install DHCP role on new server, 2) Disable the DHCP service on old dhcp server. 3) import the configuration to new server. And new dhcp server is ready to distributes the IP address.
@@MSFTWebCast awesome, thanks. one more question. After changing the old server to a DC instead of a GC, some of the workstations are still showing the old logon server after using the "set" command. Even after a reboot
@@IdealnetCa Might be service records (SRV) are not yet update to date in DNS server. You can check out SRV records in DNS manager (Under forest dns zone _msdcs_yourdomain_name.)
But in most cases, you will have minimum two Domain Controllers. When you install additional Domain controller for an existing domain, you assign the OLD IP to that DC. So if any client is using old DC (DNS) IP still it will reach to DC.
You need to export DHCP configuration on old server and then import the configuration file on new server. Use Netsh command or export-dhcpserver powershell cmdlet to do so. To Export: netsh dhcp server export C:\DHCPConfig.txt all To Import netsh dhcp server import C:\DHCPConfig.txt all
this migrating is the same method on WS-2012 R2 TO WS-2016? Step by Step Guide to Migrate Active Directory from server 2012 R2 to Server 2016 ruclips.net/video/yQD-oFp8Hzo/видео.html or not because your tuts i made on my WS-2012 R2 TO WS-2019! and success i don't know why if your remove the ADDS on WS2012 R2 and change the DNS to .7
![MISSING: SLIM SHADY [Expanded Mourner’s Edition Trailer]](http://i.ytimg.com/vi/xh8qgHrOO1g/mqdefault.jpg)
Thank you for the steps. Works well with Windows Server 2022 in-place upgrade from Windows 2012 R2.
Man, you're simply great and appreciated for your vidos❤
Thank you so much 😀
This is exactly what I need to migrate from Windows Server 2019. Thank you.
you are so thorough with your step by steps.. thank you so much.
Thank you so much for uploading the video.
We have successfully migrated the Active directory from 2012 R2 to 2019 with the help of this video.
Glad to hear that.
Same here, thank you very much!
Great video, very informative and took away my fear of doing this procedure - didn't look as scary as I thought it would be! :)
I use this video for Upgrade 2 diffrent Network. 👌🙏 Thanks a lot
This is so great. Has worked well, without any glitches so far. So great. Thank you
Great to hear!
You are the best. Thank you
Thank you too!
Also when you join W2019 into the W2012 domain, its schema will be extended automatically.
Very informative video and I thanks to your knowledge and experience to demonstrate this.
It is still working for WinSrv2022. Thank you :)
Yes, it is.
Thank you for the very informative and step-by-step video!
Man, just saved my me greatly... Many Thanks!!!
You need to make the preferred DNS as the other Domain Controller. Your replication issue should then be resolved.
Thanks for the Tip! But can you explain why this is?
Why Schema extends is required? Without schema upgrade, we can incorporate W2019 DC in W2012 Infra.
Thank you, you saved my life today.
This is a very useful video and helped me a lot - would you be able to answer some additional questions.
- I have 4 DC across two sites. 2 on each. 2012 R2 and want to upgrade to 2019 now. (Hyper-V failover cluster )
- They also hold DNS and DHCP roles and replicate
Question 1 = how my client and other services will get DNS resolution as IP address and DNS name is different for the new server. 2019
Question 2= Is there any impact of Hypervisor as my Hyper-V hosts are still on 2012
Question 3 = How to migrate file servers in DFS replication scenario
Well done. Very informative video. Will be doing this on a server tomorrow.
good luck with that, let me know how it goes.
Can we do the same senario to migrate from 2012 standard (not 2012 R2)?
great.....:) really helpful
Great video tutorial . Thank you for this :D
I made it successfully .
Excellent video and simple explanation.
Hi, I have tried to migrate our ad windows server 2012R2 to Windows server 2019 Core, it's migrated successfully but schema version and system schema version showing 58.
What should be do in this case.Please suggest...
Thankyou for making this valuable Video !
Glad it was helpful!
Great video... One question... Would it be a problem if the 2k19 is first joined to the domain and then the ADDS role is installed?... Or does it have to be at workgroup as in the video?...
I just want to show the different option otherwise I preferred to join server first and then install Active Directory Domain Services.
hi if my current AD having features like DHCP, WSUS, etc, when i replicate the current AD to new AD and make it secondary, is the DHCP, WSUS auto replicate as well? or i need to reinstall the features also in my secondary AD?
No, you have to manually install and configure those roles on additional domain controller.
@@MSFTWebCast thank you
is it posible to do this on WS 2012 STD (not R2) to WS 2019 STD? appreciate your response.
is upgrading the schema impact the operation/ require downtime?
No, it doesnt require downtime. Even the end user won't realize that it's done.
Adprep encountered an LDAP error.
Error code: 0x32. Server extended error code: 0x5, Server error message: 00000005: SecErr: DSID-031527D3, problem 4003 (INSUFF_ACCESS_RIGHTS), data 0
i am using command prep.exe /domainprep by administrator account but getting error on 2nd command. first command successfully execute
I think the issue is related to permission. Make sure user (which you are using to run adprep) is in the Schema Admins and Enterprise Admins groups.
At 13:51 are you setting up a new DSRM password or are you using the one from winserv2012R2 ?
Also, since you removed WinServ2012 why you keep in your 2019 adapter's settings as second dns the ip address of the 2012 server?
I would giess it would be new,,,,, DSRM is needed for install and removal. of DC. Up to you weather you remove ip, or change, but its not neccessary in the video i don't think. because that's not the main point.
if we want to use the old ip and hostname when we need to perform it?
One migration completes successfully and you transferred all FSMO roles to new DC. Wait for few days and switch the IP addresses first. Again wait and monitor. If everything works normally, then demote the old DC's. If demotion is successful then you can rename the new DC and assign the old name. If you have two DC's then this can be done faster.
Thank you for posting this Video, the instructions are very clear.
I have a 2012R2 Server that also has Hyper-V and some VMs. I need to move everything to the new 2019 Server. In what order would you suggest doing this?
Make the new 2019 Server a DC first and then add the Hyper-V role or the other way around? I will be doing a "share nothing" migration of the VMs. Any advice would be most welcome.
38:09 I notice you raised level after de-mote DC from older version... However, for me on new server i get different:
"The following Active Directory Domain Controllers are running earlier versions of windows:"
This would have made more sense (i would have thought), because you connected to existing domain anyway when you set up on 2019
My old server still has DC installed, but it's no longer a Catalog Server now. Must i first remove roles before raising functional level on new?
Raise functional level after removing Domain Controller role from old server. It is not necessary to raise the functional level instantly, you can take some time and then do it later.
good video, everything went smooth, but I noticed that after I removed AD from 2012 server, I still see the 2012 server listed under Sites and Services. I also still see it listed as a name server in DNS manager of the 2019 server. Do we just need to manually delete these old records from DNS ?
Hi, can we follow the same steps for Server 2022 Domain Controller?
Yes. steps will be the same.
What if you already have Win2k12r2 DC1 and DC2 replication to each other?
1. Do you choose Replication from "Any domain controller" during promoting Win2K19-DC1 to a domain controller?
2. What will the Alternate DNS Server IP on Win2K19-DC1 be? Can it be from either Win2k12r2-DC1 or DC2??
etc.
Ans:1 You can choose any domain controller but I would go with the PDC (who holds the all FSMO roles, specially Domain naming master and infrastructure master).
Ans:2 You can set both DNS server address as alternate DNS server.
Hello,
Good Morning!
This excellent video just have few clarification as i need to migrate existing Primary domain controller from windows server 2012 R2 to Windows Server 2019 i have few questions only:
1. In my case i have both primary and secondary on windows server 2012 R2 and want to migrate it windows server 2019. Please correct if i ma wrong with the steps mentioned below:
a. First need demote the additional domain controller
b. Second need to format the server and install windows server 2019 R2 and follow the process explained in your video anything else i need to do before demoting the additional
domain controller? Please guide the steps if need to follow some different procedure.
1. After following the steps mentioned above the New Windows Server 2019 will be acting as primary domain controller?
2. The existing clients will not require reregistration with new domain controller as it's migrated already?
3. In the second video you have explained how to add Additional domain controller apart from that any additional steps to be performed as after demoting additional domain controller from windows server 2012 and reinstall windows server 2019 and reconfigure as additional domain controller?
Have a good day!
Kind Regards,
Khan.
nice video it's very easy to understand. i have a quired does this migrate all GPO also?
Yes, all the GPOs will migrate too.
Hi, This video is very informative thanks, Do we have any video for removing the corrupted ADC from environment.
very informative. thank you! :-)
Hello
You are only one giving proper video and clarity.
Quick question:-
Before Promote Server 2022 as an ADC. Do we need to follow 1 Step:- Prepare Existing AD forest for Server 2022 DC using Adprep command? we can't directly do migration?
Windows 2012 R2 is End of life on October 2023
I would like to plan migrations of Servers with exchange.
My Current Infra
Servers are running VMWare
1-Primary Domain Controller**(Win2012)**
TLS.LOCAL
1-Secondary Domain Controller + File Server (Win2012)
2-RODC :-UK-RODC**(Win2012)**
2 Child Domain**(Win2012)**
CDC01.BLR.TLS.LOCAL
CDC02.BLR.TLS.LOCAL
1 Exchange Server 2016 (CU23) (No DAG Configured) (Win2012)
C Drive (OS) NTFS
DB01**(ReFS Partition)**
DB02**(ReFS Partition)**
DB03**(ReFS Partition)**
DB04**(ReFS Partition)
**
Now exchange servers are live. how can we migrate Domain Controllers and Exchange Server to Windows Srv 2019 or 2022? Directly
Because Exchange 2016 will support OS 2016 right?
Suppose i am planning to migrate Exchange 2019 with OS 2022? What is to be done?
-What is the best practices and order to Migrate Servers order?
-When Exchange Server is running, whether need to be migrate All Domain controllers and Child Domains First then migrating Exchange Server?
Please share me the links or videos steps migration with advice.
i am not getting proper links or steps to for huge changes in infrastructure.
Can you advise me
Can i keep same Computer Name or will i have issues with transferring FSMO roles via POwershell? Since domain name gets transferred, the only thing unique will be the IP addres, so i think this will be a show stopper,,
Unless you CNAME or something to forward all requests to new as FQDN is everything in a business..
After removing the old domain controller you can rename the new (server 2019) domain controller and assign the old hostname and IP address.
@@MSFTWebCast hello Thanks for making this wonderful video, but i have one question - since we have already installed DNS role during joining of the new Server 2019 DC to DC 2012, so what will happen if we change the new 2019 server IP and name back to old 2012 server IP and name? will DNS will work. As in our current scenario we have to migrate 2012 Server to Server 2019, but want to keep the same IP and Name of existing 2012 server.
Also what will happen to existing workstation that joined to old 2012 Domain, do we have to change the DNS settings in all clients manually if we dont want to retain the old name and IP? Please advise
Pretty cool presentation
Thank You!
If i have 2 DC Primary and Secondary? how to for migrate? still with step2 above?
Yes. It will be same.
hello Thanks for making this wonderful video, but i have one question - since we have already installed DNS role during joining of the new Server 2019 DC to DC 2012, so what will happen if we change the new 2019 server IP and name back to old 2012 server IP and name? will DNS will work. As in our current scenario we have to migrate 2012 Server to Server 2019, but want to keep the same IP and Name of existing 2012 server.
Also what will happen to existing workstation that joined to old 2012 Domain, do we have to change the DNS settings in all clients manually if we dont want to retain the old name and IP? Please advise
1. For a time being you have to use the new dns name and new IP address on Server 2019 DC. After checking (and monitoring) the replication and AD services for a while you can eliminate the old Domain Controller (Server 2012), if everything is going good.
2. After removing the old DC, you can rename the server 2019 DC to old name as well as you can change the IP address to the old one.
3. Also what will happen to existing workstation that joined to old 2012 Domain, do we have to change the DNS settings in all clients manually if we dont want to retain the old name and IP?
Answer: You haven't mentioned that you are using DHCP in your network or not. But if you have DHCP server then you can add the new DC's IP as a secondary DNS servers address. Client will automatically get the second DNS servers address and they can use that DNS server for any name resolution.
If you are not using the DHCP server then you can switch the old IP. I mean assign new IP address on old DC and assign old IP on new DC. So without any issue client can contact DNS.
Feel free to ask again if you have any doubts.
can i change the hostname of my new dc server. for example like the hostname of my server is winsvr2019 to the dcsvr1 which is the hostname of the old server(given i demoted and disconnected this from the network)?
Old server hostname dcsvr1(demoted and disconnected and renamed olddcsvr1)
New Server hostname windcsvr promoted as new server as dcsvr1(i use this as a new server)
Yes, you can change the name from server manager dashboard or you can also use netdom command.
@@MSFTWebCast thank you, then can i use the old server's ip address upon deployment given the old server is demoted and down?
@@FumieBasketTV Yes, you can use the old IP address as well. Recently I have done the same in one project.
Fantastic!!
Thanks!
What about raising the globalstate for switching from FRS to DFRS?
Sorry, I missed that part.
Can we change the computer name after migration? i want same computer and IP ?
Yes, we can change it. But make sure everything is working smoothly after migration.
Hi, any video for Migrating Active Directory From Windows 2012 R2 to Windows Server 2022
Not yet but all the steps are same. You wont find any difference.
@@MSFTWebCast Great Thank you.
The one thing I would have liked to see is DHCP included. My old DC is a DC, DNS and DHCP server so having that last item included in this video would have been very helpful. But thanks for this one.
No, DHCP needs to migrate separately
first Thank you so much for this video
I have a question
after we migrate to 2019 server if we need to change the name of 2019 server and IP address same as 2012 server can we do that?
because some application and file share its point to 2012 server (I Don't need to make everything new :D )
thanks
Yes, Why not? Even most of us want that..
Hello - Great video. If Server 2008 is running DHCP, does that have to be migrated or should it be installed fresh on server 2019. Thanks
sorry, meant 2012
You can migrate the DHCP server as well. You just need to export the configuration from old dhcp server.
1) install DHCP role on new server,
2) Disable the DHCP service on old dhcp server.
3) import the configuration to new server.
And new dhcp server is ready to distributes the IP address.
@@MSFTWebCast awesome, thanks. one more question. After changing the old server to a DC instead of a GC, some of the workstations are still showing the old logon server after using the "set" command. Even after a reboot
@@IdealnetCa Might be service records (SRV) are not yet update to date in DNS server. You can check out SRV records in DNS manager (Under forest dns zone _msdcs_yourdomain_name.)
Do we need to change DNS servers in the ip4 config after all?
If you want. You can change to the original IP after the migration process completes successful.
@@MSFTWebCast I mean you used both of the DCs ip's in the ip4 DNS configuration. Now that one is gone how do we configure DNS servers on the new DC?
@@alekseygrachev4025 You need to remove the OLD DNS servers IP address from the list.
But in most cases, you will have minimum two Domain Controllers. When you install additional Domain controller for an existing domain, you assign the OLD IP to that DC. So if any client is using old DC (DNS) IP still it will reach to DC.
Hello, Please make it for Windows Server 2012 R2 to Windows Server 2022
Will be live on next Tuesday.
What about DHCP?
You need to export DHCP configuration on old server and then import the configuration file on new server. Use Netsh command or export-dhcpserver powershell cmdlet to do so.
To Export: netsh dhcp server export C:\DHCPConfig.txt all
To Import netsh dhcp server import C:\DHCPConfig.txt all
this migrating is the same method on WS-2012 R2 TO WS-2016?
Step by Step Guide to Migrate Active Directory from server 2012 R2 to Server 2016
ruclips.net/video/yQD-oFp8Hzo/видео.html
or not
because your tuts i made on my WS-2012 R2 TO WS-2019! and success i don't know why if your remove the ADDS on WS2012 R2 and change the DNS to .7
tf that dialect .....