19. Migrate Active Directory from Windows Server 2012 R2 to Server 2022
HTML-код
- Опубликовано: 8 сен 2024
- Windows Server 2022 Video Tutorials for Beginners:
This is a step by step guide on How to Migrate Active Directory from Windows Server 2012 R2 to Windows Server 2022.
Follow my blogs:
msftwebcast.com
This channel is so very awesome, very useful for IT administrative work to Microsoft server and other Products related. Recently i have successfully Migrated Active Directory from Windows Server 2012 R2 to Server 2022.
Thanks You Bro.
Thank You.
Hi - I'm supposed to migrate my AD Server 2012 R2 to 2022. I can one physical server and one ADC in VM. on AD my exchange witness server is placed. Would you please share me insights/ best practice to upgrade from 2012 R2 to 2022. Please
@@bilalamjad4622 The ad migration process remains same but in the first step you have to change Witness Server and Directory. You can use Exchange admin center or Exchange Management Shell for that. Temporary you can assign the witness server to any of your member server. You also have one more option. Add new Windows Server 2022 DC as an ADC, then change the witness server and directory and assign it to new server 2022 domain controller.
Me too thanks a million
This channel is so amazing, I can't still believe you made all these videos, you are god !!
Wow, thank you! And I m no god brother. Really appreciate the kind words.
melhor materia que eu ja vi sobre este assunto voce esta de parabens.
Obrigado.
Very useful, thank you
Glad it was helpful!
perfect!
Bro, you rae doing all steps in powershall, to better understanding, if you are doing GUI steps. Its easyly to understand
Hi I left a question on your IPAM configuration video. Please take a look! Thanks!
Could you do a video on how to migrate file shares from 2012 to 2019?
Here is the video: ruclips.net/video/GKslGHFM3JM/видео.html
hello sir if one server have AD DS , File server and DHCP role what the first one must be migrate to server 2022?thank u
Very good videos!! Couldn't you do one to migrate an FTP from 2008 to 2022? Thank you very much
Noted. Will try with the current migration series.
I have to migrate a server with users and permissions, it is not easy 😢
One Question Sir/Madam,
Before demote the old Windows Server 2012 domain controller. (5th Step)
Can I execute following commands in new Win2k22 Server after move the FSMO?
Set-ADDomainMode -Identity (domainname) -DomainMode Windows2016Domain
And
Set-ADForestMode -Identity (domainname) -ForestMode Windows2016Forest
You can only raise domain and functional level after the demotion of old domain controller (WS 2012). So first demote the old dc and then raise the functional levels.
At 12:23 seems weird that my old WS2K19DC has the NTDS->Parameters path but the new one (WS2K19DC0) hasnr. It only has the RID Values folder underneath which is empty from values. Maybe a role needs to be installed first to the new server in order for the parameters folder to be created?
PS1: Since they are both 2019 they are certain to have the same schema version, but I just wan to check.
PS2:At 20:33, the way you let the configuration options for DNS Servers with 172.18.72.49 and 127.0.01 it is like pointing twice to itself.
New edit: As I initially thought (didnt mention it here though), you need first to install the ADDS role.
1. The parameters folder appears after you promote the server as dc. So if you server is not a DC then that key/folder wont be available in regedit.
2. Schema version is for AD not for an OS.
3. You are correct, I made a mistake, it is pointing twice but it is not bad. Suppose if you change the IP address and forget to update the preferred DNS servers address then 127.0.0.1 will be helpful in that case.
@@MSFTWebCast Thanks for your quick response!
Last observation is at the end of the video, wouldnt it more compete if you delete the references from the new server WS2K22 which point to the old one WS2K12? Im sure they exist I can t remember where and if there is a global command from cli or gui to remove them all at once.
Hey awesome video, have a ? if I swap the IP's from the old to the New DC, do I still have to demote the old one?
Yes you do but not necessary. You can keep your old Server 2012 R2 DC's but its end of life, thats why we are upgrading AD. So no point of keeping it.
Hello,
I am planning to migrate my Active Directory (AD) from Windows Server 2012 R2 to Windows Server 2022. I have a question regarding the current setup: both my Primary Domain Controller (PDC) and Additional Domain Controller (ADC) are configured in the existing infrastructure and both are running on Windows Server 2012 R2 Standard.
As per my current requirement, I don't want to keep the ADC.
Can I first migrate the PDC to Windows Server 2022 and, after verifying, demote both the PDC and ADC?
Yes, you can do that. Before demoting old PDC, just turn it off for few days to monitor everything is working normally. If you want to keep single DC, then make sure you take full backup regularly.
How to migrate the policy and other datas from server 2012 to 2022 . Can you help with an explanation.
You mean group policy? You dont have to do anything for group policy, it will be migrated automatically with Active Directory. For data, you can use robocopy tool to migrate shared folders and data to new server.
Yes the policies , OUs , computers ,domain user profiles etc.all these will be automatically migrated is it ??@MSFTWebCast
@@anilnair108 Yes, as it is stored in Active Directory database.
Thank you @@MSFTWebCast
Hi I have problem of replication of SYSVOL on 2022 server. Can you advise please ?
Could you provide details about the error or warning related to sysvol?
The error : 9075 ( the content set is read-only and can’t be a primary )
@@fsfernandes20 1. First run dcdiag on all domain controllers. You have to make sure that all domain controller are in healthy state.
2. Check the replication status.
3. On DFS Management, expand Replication, Click on Domain System Volume. Now check the membership status. Check if any membership is (read only).
4. If membership is read-only. You have to troubleshoot missing SYSVOL and Netlogon shares: Follow this guide: learn.microsoft.com/en-us/troubleshoot/windows-server/networking/troubleshoot-missing-sysvol-and-netlogon-shares
5. If you are still not able to fix the issue. the last stop is sysvol authoritative and non-authoritative sync. Follow this guide: learn.microsoft.com/en-us/troubleshoot/windows-server/group-policy/force-authoritative-non-authoritative-synchronization
In one video you told migration easy easy now you entered so many commands something telling why provision you did in one installed role and new server tranfar fsmo roles login new server safe mode like that you told ? Why you are telling different now
Hello and thank you for your great videos. I like to know something. We still use Windows Server 2012, but we will go to 2020 soon. I watched this video about ad migration and i like to ask this. Are with migration all users (with passwords) and settings transffered from win2012 to win2020? So if i set on new server the same domain name like we used on old one, users can normaly logon to new domain, without any interruption? Will i have any problems with user profiles, will old profiles and settings stay and be used the same? I like to shutdown win2012 after this. Thank you. Regards, Samo
1. If you are using WS 2012 then first check the sysvol replication. It should be on DFSR not FRS.
2. Add WS 2022 as an additional domain controller.
3. Check Replication and if successful the transfer the FSMO roles to ADC (WS 2022)
4. If you have a roaming user profile, then you have to migrate it to a new file server. (You have to schedule this as there will be downtime while you copy the existing data to new server).
5. Use this setup for few days, check events and logs, if everything works normally then you can remove the WS 2012 DC.
@@MSFTWebCast Thank you, i will check this. Profiles are not roaming, but i am not sure, if this profile can somehow be used, even if i log into another domain. So all what i need is, to keep this user profiles (desktop, certificates,...) when log to another domain, if this is possible.
Please post video of print server migration from 2012 R2 to windows 2022. Its request
Noted!
Hi, what can cause this in a 2012 (DC1) 2016 (DC2)?
Starting test: DFSR Event There are warning or error events within the last 24 hours after the SYSVOL has been shared. Failing SYSVOL replication problems may cause Group Policy problems.
...................... Domainpc Passed DFSR Event
Starting test: SysVolcheck...................... Domainpc Passed DFSR Event
Domain and Forest functional levels are 2008
NB: Planning to implement a 2022 DC that will take over 2012 but I need to cleanup any issues first.
It doesn't mean you have issue with sysvol. It is possible that in last 24 hours there will be a sysvol warning. I used to do simple test: Open run menu, type \\2012-DC1. Open sysvol share folder --> access domain folder (msftwebcast.local) and create a folder name T1.
Go to 2016 DC, repeat the same process and create another folder T2. On 2016 DC, can you see the T1 folder? It should be there if sysvol is working properly. If you have T1 folder then now delete it from 2016 DC.
Go back to 2012 DC. Check if T1 is deleted. (it should be) and check if you have T2 folder. (again It should be there if sysvol is working properly). delete T2 folder.
Go back to 2016 DC and check if T2 folder is also deleted successfully. If you can do this, that means syscol is working perfectly fine. If you still have any doubt send me an email.
@@MSFTWebCast Hi, thanks for sharing this feedback, I have sent an email with what I encountered.
Hey does the group policies also get migrated to the new server 2022?
Yes, it will.
I migrated 2012 essentials server to 2022
I exported and imported DHCP ok
DNS server keeps pointing to the old server
It seems to be replicating but I don't know which DNS server is the first
How do I change it?
If you have two domain controllers with DNS services, configure DC1 by setting the IP address of the other DC as the preferred DNS server and use 127.0.0.1 (or the local IP) as the secondary DNS server. Do the same on DC2.
@@MSFTWebCast where can I see which is DC1 and DC2?
the stations continue to have the old DNS server
dhcp server 192.168.10.2
dns server 192.168.10.1 (this server will be discontinued)
@@alicioneto79 I believe I misunderstood your question. You have to update the DHCP scope option to have new DNS servers address in DHCP.
@@MSFTWebCast yes that was it, I forgot about the scope options 🤦🏻♂
Now with 2 servers in the domain, if I turn off the DNS server on server 1, accessing the shares by hostname doesn't work. Shouldn't the DNS server on server 2 manage this?
Hi, my OS server 2012 std R2 but domain/forest functional level is 2008 Std R2.. should it be changed or not?
If you don't have any domain controllers running on an older version than Windows Server 2012 R2, then you can upgrade it to Windows Server 2012 R2.
the migration steps is not clear, expecting more detail
At what point you think: the steps are not clear?
It will also migrate dns records ?
Yes, it will if DNS has AD integrated DNS zones.
Today I m doing Migration the existing Active Directory from Windows Server 2012 R2 Standard to Windows Server 2022 Standard on Physical server. When i am run the following command in Windows Power Shell with rus as administrator in Windows Server 2012 R2
PS H:\support\adprep> .\adprep.exe /forestprep
then getting me following error.
Adprep failed to verify whether schema master has completed a replication cycle after last reboot.
[Status/Consequence]
The schema is not upgraded.
[User Action]
Check the log file ADPrep.log in the C:\Windows\debug\adprep\logs\20240305154854 directory for possible cause of failure.
[2024/03/05:15:48:57.653]
Adprep encountered an LDAP error.
Error code: 0xc. Server extended error code: 0x20ae, Server error message: 000020AE: SvcErr: DSID-0321040C, problem 5010 (UNAVAIL_EXTENSION), data 8610
Please help how to resolved above error....
A waiting your replay...
Thank You.
1. Check the replication status between exiting domain controllers.
2. Check if any domain controllers records exists in AD.
3. If you have any then remove orphaned domain controllers and domains.
4. Check the domain and forest functional levels
5. Check DFS Sysvol replication status.
This problem has resolved after Backup Domain Controller (BDC) Server is power on; this BDC server working under main domain controller server. (BDC) server was switched off some electrical issues. Thank for Replay.@@MSFTWebCast
how about migrate from 2008 r2 to 2019 or 2022?
Here is the link: ruclips.net/video/pESJX7oHf4Y/видео.html