Greetings, I'm Professor Kay and in this short video presentation, we're going to see how we go about transferring the operation masters for either server 2012 or server 2016 using PowerShell. For this video demonstration, I'll be using DC one as my forest route and I have DC two configured as a replica. The benefits of using PowerShell as opposed to the GUI is you do not need to use any snap ins to transfer the role to the future or the receiving server. You can also run the needed PowerShell commandlets from a Windows 10 client or a Windows Server with the Remote Server Administration tools are set package installed. To get this lab started. We will need to open up PowerShell and running as the administrator.
So let's go click on the start button. And from the available tiles, let's click on Windows PowerShell. let's right click, and from the context menu, let's select Run as administrator. For this demonstration, I've gone fullscreen with my PowerShell and I have increased the font size to 16. The Active Directory module for PowerShell is already installed by default for server 2012 and server 2016. So I've used the get dash ad forest command lit here, and I followed that up with the name of my domain.
We give it a space, a pipe space, and then we type in Ft. And then we're looking for the domain naming master and the scheming master. So the first time we want to do here is identify where these two operation masters are currently located on your domain. And this is an easy and quick way to do it. So I'm going to go ahead and just hit Enter, and it comes back and it tells me Meaning that the domain naming master and my schema master are both located on VC one, our first command identified the forest wide operation masters. Now we need to identify where the domain wide operation masters are located. Pretty much the same command, I've got to get dash ad domain as opposed to AD forest.
And the rest of it just followed up with the name of the operation matters that I want to look for. So I'm gonna go ahead and I'm going to hit Enter, and it comes back and it tells me that the infrastructure Master, the PDC, emulator, and the RID master are also located on DC one. So one of the great benefits of using PowerShell. To do all this is a lot less clicking. We don't have to open up a whole lot of different interfaces, and click on a lot of different tabs to find information. Our next step is to go ahead and gracefully move or transfer these operation master roles over to DC to So this command is pretty well complete right out of the box, the only thing that you have to add is the name of the server.
And that's it. Alright, so in this scenario right here, I need, I need to move. So in this scenario here, I'm going to move the PDC emulator over to DC to using PowerShell. So let's go ahead and hit Enter, and it comes up and it wants you to confirm that you're actually going to move this roll over to DC two, I'm going to go ahead and type in a capital N for No, I'm back to my prop. Another great feature of doing this with PowerShell is that I can move all the roles at once with just a single command. And so we're looking at the move option here up inside of the ad directory service operations master role.
And I've got all of the operation masters listed here. And I'm saying I want to move on. So let's go out let's go ahead So let's go ahead and see how we're going to do this. First of all, when I hit Enter, it's going to come up one at a time with each of these operation masters and asked me to either confirm or not that I'm going to complete the move. For each one of these, I'm gonna type in a capital N. And I'm going to say no, and I come up with the next one. So we begin with the domain naming master.
And then we go on to the PDC emulator. And then we have the RID master. And finally we have the schema master. We've got one more to go here. And we end up with the infrastructure master. I've typed in no again.
So that's all five of my operation master roles being transferred using a single command. So I didn't have to connect to any domain controller. I didn't have to get up inside of a snap in for domains and trust or Active Directory Users and Computers. I was able to do everything from a single window using PowerShell Using our last command, we were able to move all five operation masters at one time with a single command, but that command was a little long. So we can use a number that is associated with the operation master, and replace the name of the operation master in the command with just a number. So you can see in this table, each number that is associated with an operation master.
In this next example, you see where I have replaced the name of the operation masters with their corresponding number. This makes the command much shorter and easier to deal with. And again, if I hit Enter, it's going to ask me one at a time to confirm or deny that I want to move that particular operation master over to DC two, I'm gonna go ahead and type in in capital wise for no and I'll do the same thing here. And I'll do it again. One more time. And now all of the operation masters have been recently moved using my PowerShell.
If that's what I wanted to do, in this short video presentation, you got to see how we could use PowerShell to gracefully move the operation masters from one machine to another without having to interact with any GUI, or tabs or Windows. Again, PowerShell proves to be a much more efficient way of getting something done up inside of our server, in the event that the machine that is actually hosting the operation masters for your network is down and it's down hard and it's not going to be able to come back up. You can use the Move command and follow that up with a dash force to forcibly seize the rolls and move them over to DC to or whatever you're receiving domain controller is going to be. So that's going to conclude this short video presence. information on how we go about using PowerShell to gracefully transfer the operation master roles for our domain.
If you have any questions or concerns about anything that was covered in this video or in the lab file, please do not hesitate to reach out and contact your instructor and I'll see you in my next video.