I came here and made an account to say you are a lifesaver. This video is really saved my life and our 9k employees.
@CalebeOwsiany Жыл бұрын
You're a life saver, my dude!! Thanks for sharing your experience.
@MarkSmith-ln5ki4 жыл бұрын
This video was a lifesaver thank you very much.
@LabsHandsOn4 жыл бұрын
You're welcome!
@lucianM-o9k5 жыл бұрын
Thank you! Very good tutorial! Worked perfectly
@LabsHandsOn5 жыл бұрын
Thanks, Glad to know you like it.
@keratiwichitchote80152 жыл бұрын
This video can help my life . Thank you very much.
@a-teamIL4 жыл бұрын
Great videos! I think for the client to recognize the new FSMO server, you could have just did an 'ipconfig/flushdns' versus removing the DNS entry for each client (and restarting).
@subhendumordunya82175 жыл бұрын
Sir Thanks such a great explanation.
@LabsHandsOn5 жыл бұрын
Thanks.. Glad to know you like it.
@alfianpanudi8533 жыл бұрын
great video, thank you Vikas Singh
@LabsHandsOn3 жыл бұрын
you are welcome
@lordhackerrr4 жыл бұрын
My customer WinSRV2003 Faile master DC Down you video apply method. Problem resolved .. Thanks Vikas ...
@LabsHandsOn4 жыл бұрын
Glad to know keep rocking
@vikino833 жыл бұрын
Thank you for that :-) One more thing... After all, copy from failed DC (if HDD is working) policies to C:\Windows\SYSVOL\"domain"\policies
@owobogbenga818511 ай бұрын
you are a life saver boss.
@vaibhavattarde5 жыл бұрын
Thanks a lot. It really helped me to recovery.
@LabsHandsOn5 жыл бұрын
Thanks glad to know you like it
@marvinpuri65834 жыл бұрын
Thanks very much. such a helpful video
@LabsHandsOn4 жыл бұрын
Glad it was helpful!
@reuelsoriano25546 жыл бұрын
This just made my day. Thanks for such good explanation
@LabsHandsOn6 жыл бұрын
Your most welcome dear
@mario7mag6 жыл бұрын
Thanks for the information, helped me a lot!!
@LabsHandsOn6 жыл бұрын
Thank you very much for your feedback, Glad to know you like it..
@athatoghumakkar17565 жыл бұрын
Thanks sir I was so confused but aftr watching this videos, it's clear. Pls share ur machine hardware configuration to practice with vmway. Because my system is getting hanged too much.
@LabsHandsOn5 жыл бұрын
Thanks glad to know you like it.... May machine having i7 with 128GB Memory
@RifaiRahmanM4 жыл бұрын
Nice Video, Was really helpful, Also it would be great if you make another video to bring back the FSMO roles the back to the new/replaced DC server
@LabsHandsOn4 жыл бұрын
Thanks for the idea!
@sammar196211 ай бұрын
thanks a lot for clear illustration
@snehdeepbains63165 жыл бұрын
If we have to change primary DC from DC1 to DC2, do we first change domain controller and then transfer FSMO roles or do we first transfer FSMO roles and then change DC?
@LabsHandsOn5 жыл бұрын
What you mean by Change DC?? After promoting new DC in your forest/domain you can move FSMO Roles to new server.
@snehdeepbains63165 жыл бұрын
Vikas Singh so basically our Primary DC is Windows 2008 and DC2 is Windows 2012, we want to 1) make DC2 as primary DC so that we can upgrade DC1 from 2k8 to 2012, for this do we first change DC from DC1 to DC2 and then transfer FSMO roles or directly transfer FSMO roles? 2) while upgrading 2008 to 2012 will the entire data in 2008 get erased or is there a way we can upgrade while keeping data in place? DC1 is a physical server, DC2 is virtual machine hosted on esx 5.5 3) after upgrading DC1 to 2012, we want to move roles back from DC2 to DC1 and raise functional domain level of the forest to 2012
@NeoZod193 жыл бұрын
very good and so helpfull!,
@LabsHandsOn3 жыл бұрын
Glad it was helpful!
@pranjaldeka5173 жыл бұрын
very good explanation... thanks
@osobm372 жыл бұрын
Hello, i have a similar issue, I have 2 physical servers, we clone the AD server which is a Windows Server 2012 virtual machine to a new physical server, this clone never worked, the error message is "Windows cannot create the object because the directory service was unable to allocate a relative" when we tried to create new users, so we continue with the original VM . We accidentally deleted the original VM and only have the cloned VM left. Will this procedure work for us?
@Doowhip4 жыл бұрын
great video, thank you very much
@LabsHandsOn4 жыл бұрын
Glad it helped
@kuweekee4 жыл бұрын
Thank you very much for your video
@LabsHandsOn4 жыл бұрын
Glad it was helpful!
@naminda.perera3 жыл бұрын
Nice one mate
@LabsHandsOn3 жыл бұрын
Thanks
@roeljamessacdalan3 жыл бұрын
Hi i have the situation that whem Im put a "connect to server" then Binding a server then after that there's a message that my RPC is unavailable. How can I manage that? Btw my Primary server is offline and I do this on my 2nd server..
@duramax01034 жыл бұрын
How do I transfer the RID & PDC back to the primary DC? Currently the secondary DC has both roles assigned to itself. Well this cause any errors?
@LabsHandsOn4 жыл бұрын
i don't think no
@matfraeke84823 жыл бұрын
Thank you for the help!
@lanepulcini3 жыл бұрын
Thank you very much.
@LabsHandsOn3 жыл бұрын
You are welcome!
@davemagno33616 жыл бұрын
Hi Sir question, If we seize the FSMO rule from dead dc to 2nd DC, what is be the effect on the workstation? We're using live production right now!
@LabsHandsOn6 жыл бұрын
If you are able to seize and transfer all roles to 2nd DC, then their will be no issue in production infra.
6 жыл бұрын
Very good friend! Thanks for sharing.
@LabsHandsOn6 жыл бұрын
Thanks
@mykelrose6 жыл бұрын
After seizing role got this error at the end: can you tell me what wrong ? i have 2 domain server 2012r2 , one primary and one secondary and i need to remove the primary as being too old. i have try the seizing procedure and got the error at the end when i want to check if the server is ok PS C:\Windows\system32> get-addomain | select-object infrastructuremaster, ridmaster, pdcemulator get-addomain : Unable to find a default server with Active Directory Web Services running. At line:1 char:1 + get-addomain | select-object infrastructuremaster, ridmaster, pdcemulator + ~~~~~~~~~~~~ + CategoryInfo : ResourceUnavailable: (TCO:ADDomain) [Get-ADDomain], ADServerDownException + FullyQualifiedErrorId : ActiveDirectoryServer:1355,Microsoft.ActiveDirectory.Management.Commands.GetADDomain
@davemagno33616 жыл бұрын
siezing is force transfer FSMO rule from dead DC1 to DC2, if the dc1 is still active just use transfer role.
@fliprodbr5 жыл бұрын
great job !
@LabsHandsOn5 жыл бұрын
Thanks Glad to know you like it
@blogas26 жыл бұрын
Thank you. Very helpful.
@LabsHandsOn6 жыл бұрын
You are most welcome
@esmaildibazar81635 жыл бұрын
tanks very good
@LabsHandsOn5 жыл бұрын
Thanks, Glad to know you like it.
@jonaldrose81165 жыл бұрын
Thank you...
@LabsHandsOn5 жыл бұрын
Thanks, Glad to know you like it.
@madhavireddy65933 жыл бұрын
When you give the netdom query fsmo in dc2 it should show the roles of dc2 as it is also a domai controller. Why it is showing roles of dc1
@tarreislam6 жыл бұрын
ty bredda
@akosipye7 жыл бұрын
hi.. i have the situation that my DC is damage and im trying to follow your instruction and i got this error message while in command: connect to server
@marlonocillos6 жыл бұрын
use connect to server
@Tony_Heisenberg6 жыл бұрын
connect your server. I assume that it's gonna be your secondary DC in your situation
@YairZafrani4 жыл бұрын
thank you so much for this tutorial. you absolutely rescued my ass :))
@LabsHandsOn4 жыл бұрын
Keep rocking
@maheshmuthupandiyan75944 жыл бұрын
Hi bro, Thanks for your video, I have two questions 1. Suppose the Primary server will be back to normal operation. The client machine will automatically connect to the Primary server? 2.When we can change the FSMO role from Primary to the secondary domain server. A client machine cannot connect automatically? we need to do restart the client machine?
@imalihaider5 жыл бұрын
thanks
@LabsHandsOn5 жыл бұрын
Thanks for your feedback... Glad to know you like it.
@geforceadmin5 жыл бұрын
Thanks for this video. In your this demo you just turned off your Primary Domain Controller (PDC 192.168.1.254). What if after seizing all the roles to 192.168.1.253, anyone just turn on Old PDC (192.168.1.254)?
@LabsHandsOn5 жыл бұрын
Once you moved all FSMO roles to other server, and done with Meta Data cleanup nothing going to happen when old DC is going to come online.