Hey everybody and welcome back.
So in this video we're gonna be installing a d d s or Active Directory Domain Services.
Now the first thing you're gonna want to do is pop up onto the server manager and you'll see something
called add rules and features because 80 s or Active Directory is a service or it's a role and it's
a roll on the Windows Server.
Now in this particular video we're going to just click Skip for this one we don't need.
We don't care about this.
It is a rule based or feature based install.
We're not doing a remote install of any kind so we're going to select from the pool.
So this should be the only one there.
And what we're going to do is you should see something called Active Directory Domain Services.
Go ahead and check that box.
Now this is telling you that it wants to install the tools and everything that goes with it.
You want this.
So go ahead and click add features and next and we'll leave this part alone.
We don't need anything else.
So at least for this for these purposes we'll just leave it as is next.
And so if you notice here this is telling us two things note that users can still log on to the network
in case there's a server outage which is fine.
Why require a want you to do two domain controllers.
And it's also saying that ADT requires DNS server to be installed in the network.
If you don't have one which we don't it will be installed on the system.
So 80 days will automatically install a DNS server local to this which is why we set the DNS and the
previous video to the local host of 1 2 7 0 0 1.
So go ahead and hit next and the restart destinations are automatically.
We were going to leave that unchecked because we need to do something at the end.
So this is telling us it's going to install HDD as the group policy stuff.
And then the administrative tools which is what we need.
So go ahead and click install so this will take a few minutes.
We will.
I will come back to you guys once this is done.
So welcome back.
So at this point we've finished the install and then we can see here we should see the the option to
promote the server to a domain controller.
So what's important to understand is that this is what makes it a domain controller that domain controller
is what controls domain handles all of the management and handles the users and everything like that.
Now it won't do anything until it's promoted to do so.
The reason this is a separate action is because it's permanent so which is why everybody should be making
a snapshot before we got to this point.
There's no reverting this you have to reinstall windows.
If an actual system it wasn't virtual there wasn't a snapshot and you needed to revert this you would
have to reinstall windows.
So we're going to go ahead and click to promote the server to domain controller area.
Now we're going to want to do is so the default is to added to make judgment existing domain.
We don't want to do that and we don't want to add a new domain to an existing forest.
What we want is a new forest.
So a new forest.
Think of a forest as as the domain of just a forest of machines which is also forcing domains.
So this is the domain name.
So in our case we want red team nation dot local.
You can name this wherever you like.
A lot of places this is like the name of the company.
Whatever the case might be maybe it references a particular network that it's managing whatever the
case might be.
I'm just doing the company name and then dot local for simplicity's sake.
So go ahead.
Next.
Perfect.
Now we're going to do is we're going to leave the forest functional level as Windows Server 2016.
Now if you had servers on the network that were not the latest and greatest you would want to dumbness
down a bit.
Otherwise they won't be able to join the domain.
So for this we're gonna do we're going to install the DNS server and global catalog is fine.
That's where we go.
Well we're not going to do is do a read only now a read only means that it is.
For example you already need to have a domain controller on the network.
So in this case it's a brand new one which is why it's great out.
So if I wanted to add this to an existing domain I could have the option added as a read only which
means nobody can log into this and make changes to the users or anything like that.
This is good for remote offices.
So if somebody needs to log in on a remote office they don't have to connect all the way back to the
HQ.
They can just log in it'll just logging them in locally.
Some of the credentials are cached on that domain controller.
Now the recovery mode password in this particular case we're just going to give it a random password
in the real environment you're gonna want to keep track of this because this is your fallback if something
happens and you need to recover or you need to gain access this pass or you're going to be the only
thing that saves your ass.
So keep it keep it written down somewhere.
In my case it's not that big of a deal we don't plan on locking ourselves out but if it does happen
take note of this password somewhere.
Got it.
Next perfect.
We can ignore this.
We're not doing any DNS delegation.
So here next again our net bios domain name should just auto populate.
So we're gonna go over these in a different video just will these as defaults.
Now this is just going to review the stuff that we've selected.
Everything looks fine.
Now if you want to automate this you could just do the script and then copy that out.
I believe it's Empower show.
Yep exploited a power show.
So this means you could rapidly deploy domain controllers automatically with a similar configuration.
So we'll go ahead next and I'll do a pre Rex check.
You're gonna see quite a bit of things here.
We're not going to worry about fixing these.
The only time you should be worried is if you get something that's red because it will not let you actually
install anything without passing it.
But in this particular case I believe there's only one or two yellow based ones.
Also note at the end of this this this particular installer it will force a restart of the system so
don't worry about that.
That's completely normal.
It requires a restart for everything to take into effect perfect.
So as I said we're going to ignore these all proc parameters of checks of past successfully so if this
failed then you'd have to go back and fix something.
In this particular case we're perfectly fine.
So we're gonna go ahead hit install now.
I will be back when this is finished.
So the install is finished.
You should get this you're about to be signed out and as soon as you hit close it should start restarting
it just a second.
Perfect.
OK.
We'll be back when it restarts.
OK so now we've gone ahead and reboot it.
So let's go ahead and attempt to log in now what I want you to notice is we're not longer just using
administrator.
We're doing Red Team nation slash administrator.
So this first part is the domain then the slash and then the user name.
So now we're not logging into a physical machine anymore.
Now we're logging in to the Domain Controller with the account administrator
and we'll use the same password that you had set for the original administrator calc because the admin
on the domain controller is the domain admin.
So it is still a an account a local domain admin account.
So now we can see we've been logged in.
Nothing really looks any different.
We'll go over some of the differences and some of the tools in the next video.
But now we've successfully installed Active Directory Domain Services and DNS onto the machine so we
can start playing around with different things.
So go ahead and make a snapshot now.
So you have a stable state for the the Active Directory Server and the DNS service.
So if we take just a half second here and let this load.
We should see our new services.
Looking good right after.
Right out here
perfect.
So we see 80 80 DNS and DNS look green.
So we are good to go.