You are simply the best. Thank you very much. Excellent Tutorial.
@MSFTWebCast
2 ай бұрын
Thank You.
@user-wi4et4dg7x
10 ай бұрын
Excellent video. Worked perfectly going from 2012 R2 to Server 2022
@Chandrashekhar1972
4 жыл бұрын
The smoothest way to transfer DC/FSMO roles from 2012 to 2016
@iFly969
2 жыл бұрын
best video on the subject on youtube. Lifesaver.
@ramonpf_ch
7 жыл бұрын
Thank you, very well explained.
@mrbazzzinga4878
3 жыл бұрын
Sir you have good knowledge but please talk slow and clearly i was having very hard time understanding i had to slow the speed of video
@Didiana62
7 жыл бұрын
Thank you for this vid, was very helpful. I love your accent! :D
@sasa22254
10 ай бұрын
Perfect❤
@itechsolutionslk
Жыл бұрын
Thank you, very well explained. Keep it up 😀
@ecofriend93
2 жыл бұрын
Great tutorials! Thank you!
@kelum1981
Жыл бұрын
Excellent. Thanks a lot.
@QuantumByteHub
7 жыл бұрын
thank you for your movie, love them all, well explained
@gaurabpokharel6373
9 ай бұрын
Thanks for the video
@kiran4uster
2 жыл бұрын
Thanks lot ! Best tutorials!!
@MSFTWebCast
2 жыл бұрын
Glad you think so!
@aronnov
6 жыл бұрын
Very good video. Great walkthrough.
@royhindole
Жыл бұрын
Instead of using ntdsutil one can use the below Powershell command in Admin mode Move-ADDirectoryServerOperationMasterRole-Identity "DC Name where the roles are to be moved TO/ONLY the HOSTNAME" -OperationMasterRole 0,1,2,3,4
@MSFTWebCast
Жыл бұрын
Yes, we can.
@gomezganiphiri2446
4 жыл бұрын
Thanks for the vid, it was extremely helpful
@vikassinghsingraur
2 жыл бұрын
Very helpful
@malgeo
5 жыл бұрын
Very hard to understand because of the accent, but it worked perfectly. Thank you.
@marutiritz5534
3 жыл бұрын
Easy and clear
@DawidKellerman
6 жыл бұрын
Very Good to the point Tutorial!
@theglot1
7 жыл бұрын
Thank-you-- very useful and help solve many problems
@basscaq
3 жыл бұрын
Very Clear Video. Thx
@bigheadedkid
7 жыл бұрын
Your videos are fantastic. I am having an issue transfering FSMO from 2012 (not R2) to 2016. After following all of the same steps you have done to the point of transferring the roles, I opened AD UC, right click on the domain, select Operations Masters then in the RID tab hit Change, which is what I've always done when moving FSMO. In this case I am receiving an error that says "The current Domain Controller is the operations master. To transfer the operations master role to another computer, you must first connect to it." I am doing this FROM the 2016 server. I am perplexed why it is giving me this message, like it thinks I am on the 2012 server... I have refollowed through all of your steps and I still get this message. My next step would be to try do transfer FSMO using the command prompt as you do, but before I do this and run into the same problem, or potential create a new problem for myself, have you run into this issue before? Do you have any suggestions? Thank you!
@BagasDwiAnggitahudzaifah
Жыл бұрын
Thank you, you have clear video. please advice, once demote old DC (os2012), each computer client should re-join to new DC (os2016)right?
@nihaljaiswal2459
9 ай бұрын
After demote W2012 how to change W2019 Hostname and IP (want to keep old server hostname and IP)? Could you please help me into this.
@vishalsaxena5081
2 жыл бұрын
I want to migrate resources from source domain to tager domain pls share video for this i have migrate all resouces but when i try to login migrated device with migrated user so device not accessable
@Tech-geeky
2 жыл бұрын
Replication is the toughest part, because it changes constantly.. You can do it several times to "match" between servers, but when you change an IP address or restart again, its ":out of sync" Does it matter at that specific point ? It may be in sync the first time, but other times after chang to network settings are done, its "constantly" out of sync, doesn't matter how many times you do replication or restart on both services.. its usually 2 or 3 numbers out of sync.. The fact it was right the first time (before I changed network settings) I may just leave it but its a pain in the ****.. I think it matters ONLY the first time you do it, but if you go back to DNS later on both system, its will be out of sync again.... But I think that is OK isn't it ? because 100% of the time one will always be out if sync.... Its just unless you go to DNS you will never know, but I;m also not sure if that matters either basing on the first time it's done.
@user-zj2vk7rd2n
3 жыл бұрын
Thanks man, this is work)
@ToutMinteresse
7 жыл бұрын
Hi, is your method keep the domain features level at 2016 ?
@OmarEshtiwi
7 жыл бұрын
Thank you it worked well for me.
@Johnson14207
Жыл бұрын
Do you have a video to upgrade a DC server 2012 to 2019? Is it going to be in place upgrade it clean installation? Thanks for the hard work
@MSFTWebCast
Жыл бұрын
Here is the playlist: kzitem.info/door/PLUZTRmXEpBy3gEFrdPHSP4vPB3GJsS4CV
@Johnson14207
Жыл бұрын
@@MSFTWebCast thanks for replying but none of those is “upgrade DC server 2012 to 2019” Thanks again
@ayoubatif2644
4 жыл бұрын
Thank you
@pg4694
2 жыл бұрын
in case of this migration im confused abt updating schema why have you not used adprep for updating it and if it is done on the older server by using older serve cd and performing adprep through cmd
@MSFTWebCast
2 жыл бұрын
Definitely you can use adprep command line tool to update the schema first and you should have to. But In this video I want to show another method to do so. At 6:04 you can see information about Schema and Forest-domain preparation.
@pg4694
2 жыл бұрын
@@MSFTWebCast thankyou for the quick reply on the same but there is one more thing that i would like to know that for the ad prep we need to use older version of server i mean for example if you are migrating from 2008 to 2012 then we need to insert 2008 server cd for running ad prep and we need to perform adprep on server 2008 only
@MSFTWebCast
2 жыл бұрын
@@pg4694 It is not like that you can do that from any server. But it is best practice to run those commands on the domain controller who holds the schema master FSMO role. You also need to have schema master admin role to successfully run those commands.
@PRABHAKINGPIN
Жыл бұрын
Bro i hv migrated as you said but unable to join new pc or server to domain. AD DC could be contacted error is coming pls help me out 🙏
@MSFTWebCast
Жыл бұрын
Is the old DC still running? Run nslookup on client, check DNS settings. Let me know.
@gaurabpokharel6373
9 ай бұрын
Can IP Address to 2016 server be resued if 2012 server ? I am having Issue after doing that ? I just shut down the 2012 server and reused its Ip address then I am having Issue ? Can someone recommend the correct procedure ?
@MSFTWebCast
9 ай бұрын
Active Directory fully supports IP address changes on DC. You can use your old IP addresses on new DC. Check DNS Zone and Records are updated or not?
@movietime5333
2 жыл бұрын
good job mate !
@ArturoForlano.
6 жыл бұрын
Hello, this explanation is applicable with a windows server 2012 r2 server foundation to server 2016 essentials?
@undergod1987
5 жыл бұрын
THANK YOU SO MUCH..
@junedi5085
5 жыл бұрын
Hi , Great Explain Is this represent about migrating AD from one host server to another? . I have plan to p2v the AD from existing server to new server. But in some article not recommend to do p2v on AD. Do you have advice for my plan ? Thanks
@MSFTWebCast
5 жыл бұрын
Yeah, I had a bad experience with P2V migration. Some time it works and some time not. One more option is there. Create a brand new VM, promote as an ADC and transfer the FSMO roles. Wait for few days and if everything is working fine then eliminate the physical DC.
@jai3537
5 жыл бұрын
You are knowledgeable but you dont have to try the FAKE accent . It makes harder to understand. Believe me , Indian accent is acceptable everywhere.
@veeranmatmari1340
6 жыл бұрын
Can you make a video of Migration using ADMT tool ?
@sv_vigneshsekar
6 жыл бұрын
Great man
@1jeffhead
4 жыл бұрын
hi, please help me. When i try to press "replicate configurarion to selected DC " i get an error code saying "DSA Operation is unable to proceed due to dns lookup failure" , please help. i have no idea what to do.
@MSFTWebCast
4 жыл бұрын
Problem is related to DNS name resolution. Check DNS and make sure both DCs can ping with each other using FQDN (it is must). :- If required restart dns service (not server) once. :- Clear DNS cache by using ipconfig /flushdns command.
@steveanderson1779
3 жыл бұрын
thx
@nobody-P
3 жыл бұрын
I did but completely failed
@skypete09
5 жыл бұрын
Hi would this work the same if i was to migrate from a 2012 to a 2012 server? Also can i keep the same name IP DNS and DHCP thanks.
@skypete09
5 жыл бұрын
Thanks so I could for sure keep the host name DNS and Ip as well just want to make sure thanks again.
@jdh2021
7 жыл бұрын
can I have your contact or how to connect with you in very convenience way?
@MsAkshay19
6 жыл бұрын
your pronunciation i cant get it
@clusternate
4 жыл бұрын
Domain Controller or Domain ConDEDEDE :D
@stephanielemejouk8127
Жыл бұрын
votre video est trop rapide. mais merci
@MSFTWebCast
Жыл бұрын
Thank you for the suggestion. I will keep it in mind.
Пікірлер: 67