Everybody and welcome to the next video in the module.
Now in this video we're going to be going over common configurations for the Windows Server.
Now keep in mind this is not a complete list.
This is a quick a quick guide to kind of get you up and running to avoid some of the issues that you're
going to find out later if you don't change these ahead of time.
Now some of these configurations are going to be insecure but that's done so we avoid restrictions blocks
any any sort of issue later going through the course we want to make sure that the learning process
is set in place first but I will notate what shouldn't be changed in a production environment that you
would have to go into and actually configure all the stuff manually.
But in our case we're going to ignore all the big configuration changes.
Now go ahead and open up the server manager and then move over to local server on the top left.
Now there are a few things here that we want to change.
Now the first thing we're gonna look at is the i.e. enhanced security configuration.
Currently we've set this to off for the administrator.
Just make sure that that's up to often on for the user.
Now the next thing we're gonna do is we're gonna click on the firewall at the top left and we're gonna
click on the top left as well turn off and on Windows Firewall and we're just going to head and turn
these off.
Now we're turning these off to avoid ports being blocked or anything like that when we're messing around
with installing directory in the real world you would use you would open up specific ports for specific
services and only allow those in in our case we're gonna turn it off for sake of sanity when we're playing
around with this.
So the next thing we're gonna do is go over to our Ethernet tab right here and click on this.
Now we only have one network interface or one Nick so we'll just use this one right click properties
and then we're gonna go over to Internet Protocol Version 4 and then properties.
Now currently we're getting everything from DCP which is fine virtual box has its own DCP that gives
us an IP address and a DNS server everything like that.
But what we want is we want to use our own IP that we decide.
So overall the command line to IP config and we can see that our IP addresses tend zeroed out to def
15 or subnet masses 255 255 255 0.
And our default gateway is 10 dot zeroed out to that too.
Now we're gonna go over what a subnet mask is a default gateway and an IP address in the networking
module.
But for now we're just going to copy the data directly over.
So we'll go and use the following IP and we'll just use the same one.
So 10 does zero to 15 then 255 255 255 0.
The gateway is 10 dot 0 2 2 and then the preferred DNS servers 1 2 1 2 7 0 0 1.
So we're going to point to the local machine itself.
That's the shortcut notation for that and then for the ultimate we're going to do googles which is a
daddy daddy daddy.
Normally when a enterprise will have their own DNS server that will talk to the the and replicate from
the internets as well and be able to resolve it.
So that's why you point to the local host first we're only having a daddy daddy daddy there for sanity
when we on this machine need to go and download something because if you didn't do that and we didn't
have the DNS server available we could not resolve Google dot com to an IP address which means it would
it would not load.
So go out and click ok and cancel and then if we redo IP config we should see nothing because it's resetting
the adapter and then poof there you go.
So we're good to go.
We've got our single IP.
And the reason having a static IP where it's not going to change on us.
So currently when we had set this up it's use the DCP server which has something called a lease which
can be three days 60 days or a permanent lease.
But the IP addresses tends to be temporary.
What we've done is we made it permanent so it will never change.
You're going to want to do that in the DCP server as well and make sure that it knows that it's being
used by something.
Well we'll get into that in a different video.
It's not going to be in this particular module.
So we've set our IP we've turned off the Internet security controls.
We've also turned up the firewall.
Perfect.
Now the next thing you should do is completely patch the Windows Server.
But for sake of it taking the next 30 years to patch the thing for every possible thing from the time
that this bill was made to current and it doesn't really help us in the scope of the course.
So we're gonna go ahead and leave the patches alone.
The next important thing is the computer name.
So go in and click on that might change.
Now the only thing we're not going to change workgroup because we haven't set up a domain yet.
So we're not going to mess with this we're going to change the work so we're gonna change this to Red
Team nation we'll do dot DC we'll do underscore.
DC 0 1 so in most naming conventions you're going to have a DC oh something at the end.
Now every organization is a little different.
In my particular case I'm just gonna do DC one we don't plan on having 2 but the naming convention does
work so you know which one you're pointing to.
Go ahead and hit OK am.
Do you want to use this.
Yes we do.
Oh that's right.
15 characters.
That's fine.
We'll leave that alone.
It'll be misnamed for a little bit.
We'll change it later.
Change it to something that's less than 15 characters.
Completely forgot about that.
And it'll force a restart
see what it does now.
Party Nation.
Let us get away with that.
Perfect.
All right let us go with it.
Cool.
All right.
So go ahead and restart the computer will restart now and once it boots back up it will have its static
IP.
It'll have the firewall off it will then have a single hostname so this has been the quick configuration.
Next video we're going to be going over actually installing active directory.