Great video and good explanations over the FSMO roles. I normally prefer doing the transfer through ntdsutil console since its far more easy transferring all the roles from single place utility rather scavenger around the GUI. Also as a tip after each role transfer do force sync over the DC's (especially between the donor DC and the FSMO role recipient DC) and in the end you can pass the basic diagnostic on each DC in the Domain/Forest via dcdiag command in ps/cmd with admin privilege to make sure all DC's function is restored back to normal after the role transfer.
Unfortunately, Evey office has one of those arrogant turds John...I have been fortunate at my current location and I have multiple coworkers who love the fact that once I learn something new I can take that off their plate and add value to the team. It frees themup for other tasks. It's called reciprocated appreciation.
Excellent tutorial. The difference between each roles was very well explained and the process was explained perfectly. Just to add that before starting this task, ensure the user your logged in as is domain admin and a schema administrator, other wise the option to change will be greyed out. This was my first time carrying out this task and you made it very simple to follow. Top man. Thanks very much.
Hi yazan, you need to verify few things: 1. What is the current FSMO holder? netdom query fsmo 2. Is the current FSMO holder up and running? You can use dcdiag command to verify that the Domain Controller is functional. 3. Are they seeing each other? Is there a normal replication in place? repadmin command will help you determine this. 4. Was the current FSMO holder restored? 5. Try to restart the current FSMO holder and the destination Domain Controller and try to transfer the roles again.
Very Great and professional. if i transfer my FSMO Roles to my secondary domain, will it continue performing the role of primary domain incase it fails?
Thank you David! When you transfer the FSMO roles to another Domain Controller it picks up the roles and is responsible for all functions related to them. If you have at least two Domain Controllers in the environment should be enough to withstand a failure in one DC.
Hello, I do have a small queries as you told domain wide operations will be per domain .. but here we are transferred to one to another(primary to secondary) then what about the primary domain now ?
If the primary dc with all the roles just needs to be shut down for 45min maintenance , does a secondary dc or tertiary dc automatically assume the fsmo roles?
THanks for the video, but I'm not able to transfer the Schema master role... I'm migrating from 08 to server16.. The option is greyed out to change the schema master... Any suggestions?
Thank you, this was great, exactly what I needed. Once I have successfully transferred the FSMO roles and set up DHCP, is there anything else I need to do before I can decommission my old PDC?
Thank you FazerWiz! There could be multiple things to check before removing a Domain Controller for example: 1. Any applications using this Domain Controller for authentication. 2. DNS services, if your DHCP is giving the address of the Domain Controller. Possibly any static DNS settings on servers or computers. 3. Print or Share services, if you have those setup on the DC. 4. It would be wise to check everything and migrate them prior. Also shutdown the DC (only short period of time) and see if anything will be affected. Note that it is not a good idea to leave a DC not communicating with other DCs for long period of time.
Thanks. All seemed to go well, but I do now have a problem showing up in dcdiag, I wonder if you could help. 1. Joined the domain ok. 2. Promoted the server to a pdc ok, AD seemed fine. 3. Transferred the FSMO roles ok, tested ok 4. Tried to demote the SBS server and 1st time it failed, it said there was no other PDC. I googled the problem and found a MS document saying I needed to change a registry entry here: support.microsoft.com/en-nz/help/947022/the-netlogon-share-is-not-present-after-you-install-active-directory-d 5. I did that and was able to demote the old SBS pdc ok.I ran DC dcdiag on the new 2016 server which was throwing up errors because the new server had no SYSVOL share - in fact, there wasn’t even a directory. I tried to restore the SYSVOL with these instructions: jorgequestforknowledge.wordpress.com/2010/08/12/restoring-the-sysvol-non-authoritatively-when-either-using-ntfrs-or-dfs-r-part-3/ Now I have a SYSVOL folder but no files in it. Dcdiag is still showing sysvol errors. My users can log on to the domain and don’t know anything is wrong, but I’m really worried that the authentication is going to break sometime and they won’t be able to. If you can offer any advice I’m be eternally grateful.
Hi siddharth, I would double check if my Domain services are working as expected before demoting. Using dcdiag and checking logs. Try to turn off the Domain Controller for an hour, see if any of the services are affected, run dcdiag and repadmin.
Hi Nick how to transfer fsmo rule in child domain, what are the roles need to transfer. Please let me know, i transfer my dc forest and it successfully transfers and child domain given error after transfer fsmo rule.
dear all i had a Power problem with the main 2012 R2 AD DC and i had to do the recovery after i fix the power supply on it >>> now i had this problem .... (This server is the owner of the following FSMO role, but does not consider it valid. For the partition which contains the FSMO, this server has not replicated successfully with any of its partners since this server has been restarted. Replication errors are preventing validation of this role) and the other one ... (The DFS Replication service stopped replication on the folder with the following local path: C:\Windows\SYSVOL\domain. This server has been disconnected from other partners for 71 days, which is longer than the time allowed by the MaxOfflineTimeInDays parameter (60). DFS Replication considers the data in this folder to be stale, and this server will not replicate the folder until this error is corrected) ... nothing work on it any idea to get it back to work as a main domain controller
This is great. I am 5 years late to the party, but still relevant! I’ll be transferring one role tonight. Thanks for sharing!
Thank you very much for this. I'm doing my first FSMO migration this weekend and now I am less nervous about doing it!
+Gary Calvert I am glad that I was able to help! And good luck !
I had never done this before and you made it quite easy! Thanks a million times for posting this video.
Thank you Thom! That is my one of my main goals, to make things simple and for my viewers.
ONE OF THE BEST VIDEO ABOUT F S M O ROLES. THANK YOU NLB solutions
Great video and good explanations over the FSMO roles. I normally prefer doing the transfer through ntdsutil console since its far more easy transferring all the roles from single place utility rather scavenger around the GUI. Also as a tip after each role transfer do force sync over the DC's (especially between the donor DC and the FSMO role recipient DC) and in the end you can pass the basic diagnostic on each DC in the Domain/Forest via dcdiag command in ps/cmd with admin privilege to make sure all DC's function is restored back to normal after the role transfer.
Excellent video. Great preparation for my interview
Thank you very much! Every time I have a question about something you have a video with the solution :)
Very nicely explained FSMO roles in a simple language and clear. Thanks for sharing Brother. Keep up the good work.
Awesome video. I, unfortunately work with a jerk who did not share any knowledge of this with me!!!
Thank you, John. I think everyone worked with a person that does not want to share. This is not the case here !
Unfortunately, Evey office has one of those arrogant turds John...I have been fortunate at my current location and I have multiple coworkers who love the fact that once I learn something new I can take that off their plate and add value to the team. It frees themup for other tasks. It's called reciprocated appreciation.
Thank you, this video is not only helpful but very well explained also.
+Efstathia Efi thank you for your kind words and support.
very professional, GREAT!!!
Thank you, Esteban! I am happy that I was able to help!
Appreciate you, demonstration is really good.
Thanks
Hello Nick,
Thank you for making this vedio, it was simple to understand.
Excellent tutorial. The difference between each roles was very well explained and the process was explained perfectly. Just to add that before starting this task, ensure the user your logged in as is domain admin and a schema administrator, other wise the option to change will be greyed out. This was my first time carrying out this task and you made it very simple to follow. Top man. Thanks very much.
100% perfect guide.... Thanks
Thank you Sourav!
Excellent explanation..Great .. Thanks
Clear and crystal explanation. Thank you.
Thank you Jay!
Dad?
Nice Video !!! thumbs up !
Very well explained thank you so much !
Thank you so much! This video showed me exactly what and how to do it.
Happy I was able to help Keith!
Very nice explanation, keep it up!
Thank you Rajesh!
thank you very much we are waiting for more lessons
Thank you, yazan! More coming your way!
NLB Solutions when i try it i cant connect with the another dc ...why
i am sorry i am trying to write in english as possible as i can
Hi yazan, if I understand correctly you cannot connect when trying to move the FSMO roles?
NLB Solutions yes that's it please
Hi yazan, you need to verify few things:
1. What is the current FSMO holder? netdom query fsmo
2. Is the current FSMO holder up and running? You can use dcdiag command to verify that the Domain Controller is functional.
3. Are they seeing each other? Is there a normal replication in place? repadmin command will help you determine this.
4. Was the current FSMO holder restored?
5. Try to restart the current FSMO holder and the destination Domain Controller and try to transfer the roles again.
Thank you !
Thank you for the support, Hakob!
Very clear and precise content. Thank a lot
Thank you, Dhrubajyoti!
Was very helpful video.
Very nice video .please keep up the good job
Good Explained. Thanks
Great, very well explained! Tks
Thank you for the support!
such a great job!
Thank you Ibra!
Love u man!
Thanks!
perfect!
Good thanks
Very Great and professional. if i transfer my FSMO Roles to my secondary domain, will it continue performing the role of primary domain incase it fails?
Thank you David! When you transfer the FSMO roles to another Domain Controller it picks up the roles and is responsible for all functions related to them. If you have at least two Domain Controllers in the environment should be enough to withstand a failure in one DC.
Thank YOu very much
Thanks
Great Video and but One Small dought ,I have two Windows 2012 r2 servers can i transfer the roles from one to another.
Great video, well explained.. Where can I get the program that loads in the up right corner. Thanks..
Thank you, Hose. The program is called BGInfo, you can get it from here - technet.microsoft.com/en-us/sysinternals/bginfo.aspx
Hello,
I do have a small queries as you told domain wide operations will be per domain .. but here we are transferred to one to another(primary to secondary) then what about the primary domain now ?
If the primary dc with all the roles just needs to be shut down for 45min maintenance , does a secondary dc or tertiary dc automatically assume the fsmo roles?
thank you
Thank you very much...
Thank you for the support Jubaer!
THanks for the video, but I'm not able to transfer the Schema master role... I'm migrating from 08 to server16.. The option is greyed out to change the schema master... Any suggestions?
Great video.
Is the RID Master now officially known as the RID Pool Manager ?
Hi, there are many names but they all hold the same idea - The RID master (also known as the RID pool manager, RID manager, or RID operations master).
Thank you, this was great, exactly what I needed. Once I have successfully transferred the FSMO roles and set up DHCP, is there anything else I need to do before I can decommission my old PDC?
Thank you FazerWiz! There could be multiple things to check before removing a Domain Controller for example:
1. Any applications using this Domain Controller for authentication.
2. DNS services, if your DHCP is giving the address of the Domain Controller. Possibly any static DNS settings on servers or computers.
3. Print or Share services, if you have those setup on the DC.
4. It would be wise to check everything and migrate them prior. Also shutdown the DC (only short period of time) and see if anything will be affected. Note that it is not a good idea to leave a DC not communicating with other DCs for long period of time.
Thanks, I'd thought of all those things and all went well, however I have hit a sysvol issue which I've messages you about. Thanks again.
Thanks. All seemed to go well, but I do now have a problem showing up in dcdiag, I wonder if you could help.
1. Joined the domain ok.
2. Promoted the server to a pdc ok, AD seemed fine.
3. Transferred the FSMO roles ok, tested ok
4. Tried to demote the SBS server and 1st time it failed, it said there was no other PDC. I googled the problem and found a MS document saying I needed to change a registry entry here: support.microsoft.com/en-nz/help/947022/the-netlogon-share-is-not-present-after-you-install-active-directory-d
5. I did that and was able to demote the old SBS pdc ok.I ran DC dcdiag on the new 2016 server which was throwing up errors because the new server had no SYSVOL share - in fact, there wasn’t even a directory. I tried to restore the SYSVOL with these instructions: jorgequestforknowledge.wordpress.com/2010/08/12/restoring-the-sysvol-non-authoritatively-when-either-using-ntfrs-or-dfs-r-part-3/
Now I have a SYSVOL folder but no files in it. Dcdiag is still showing sysvol errors. My users can log on to the domain and don’t know anything is wrong, but I’m really worried that the authentication is going to break sometime and they won’t be able to. If you can offer any advice I’m be eternally grateful.
Great !! One question how do you force a replication?
very easily explain.. Great,
So that now can i demote the dc.?
After transfer fsmo roles.
Hi siddharth, I would double check if my Domain services are working as expected before demoting. Using dcdiag and checking logs. Try to turn off the Domain Controller for an hour, see if any of the services are affected, run dcdiag and repadmin.
well done bro.. clearly explained can u please upload for seize the roles if pdc fails
Sure, I will create an explanation video ! Stay tuned !
Hi Nick
how to transfer fsmo rule in child domain, what are the roles need to transfer.
Please let me know, i transfer my dc forest and it successfully transfers and child domain given error after transfer fsmo rule.
Best watched on 2x speed.
What program installed to have info of the system on desktop? dbginfo? Thanks
BGInfo - docs.microsoft.com/en-us/sysinternals/downloads/bginfo
dear all i had a Power problem with the main 2012 R2 AD DC and i had to do the recovery after i fix the power supply on it >>> now i had this problem .... (This server is the owner of the following FSMO role, but does not consider it valid. For the partition which contains the FSMO, this server has not replicated successfully with any of its partners since this server has been restarted. Replication errors are preventing validation of this role) and the other one ... (The DFS Replication service stopped replication on the folder with the following local path: C:\Windows\SYSVOL\domain. This server has been disconnected from other partners for 71 days, which is longer than the time allowed by the MaxOfflineTimeInDays parameter (60). DFS Replication considers the data in this folder to be stale, and this server will not replicate the folder until this error is corrected) ... nothing work on it any idea to get it back to work as a main domain controller
Are you Dutch?
my fsmo roles dont move automatically i need help
it's v.good
but can help me to give me way to learn english language
TALK TALK TALK - Get to it!!!!!!!!!!!!!!!!!!!!!! Thumbs down!!!!!!!!!!!!!!!
Thank you so much