- [Instructor] Once the deployment
of a new server has been planned,
the installation itself if a pretty elementary task.
Unlike servers from long ago,
the installation of Windows servers today
only ask a small handful of questions.
And if the answers are known in advance,
installation is pretty smooth.
If you're prepared with the language preference,
the product key and whether or not you need
the desktop experience, the only configuration question
that you'll be asked is the size and the placement
of the install partition.
And that size can even be modified
after the fact, if you need to.
The bare bones requirement here
is that you should have at least 32 gigabytes
for the install partition.
As we mentioned before, that minimum doesn't even account
for the desktop experience.
That's only for Core, which is now considered
the default install for Windows Servers.
Best practice is to consider starting
at double or more the stated minimum requirement.
Keep in mind that you're going
to be installing various roles and that you want this server
to run for several years so there's going to need
to be room for whatever security and feature updates
may be released over that time.
Here's a fresh install that I completed
on a server in my test lab
on a virtual machine with eight gig of RAM,
dynamically expanding.
You can see that right now it's using 3/4 of that
and this server is literally doing nothing.
That two gig of RAM really is a bare bones minimum.
I installed this, like I said, in a virtual machine.
I granted it eight virtual processors
and this eight gig of RAM,
and it took all of 15 minutes to complete,
including the reboot at the end.
In fact, it felt like the reboot
was the longest part of the process.
Completing that install is only the first step
to getting a new server ready.
Before you add any roles, share any folders,
or install any applications,
you need to assign the server an identity.
And this includes two things:
the network address, and the computer or host name.
Just like in previous versions of Windows Server,
the server manager loads by default.
And, just as in previous versions of Windows Server,
you can select this line next to ethernet
and get the legacy interface for changing the IP address
and network configuration of any interface in the machine.
I'm going to go ahead and assign this an address,
using tools that have been around for several versions
of Windows and Windows Server.
I'm going to assign it a static IP address,
including the default gateway and DNS information
provided to me by my network administration team.
Assigning new IP configuration,
even adding or removing IP version four or six,
or switching from dynamic to static,
none of these changes require a reboot.
I like to get as many things done as possible
before a reboot, so that all of those settings
can be applied as the system comes up again.
So let me go ahead and save those changes,
and this is on my company network,
and yes I do want my server to be visible to other machines
so I'm going to go ahead and say yes.
And I can close out of this panel.
And now the next step of giving the computer a name.
This can also be done from the server manager,
but I want to show you a different path.
I'm going to open PowerShell.
And if you haven't started using PowerShell yet, it's time.
Especially if you're considering semiannual releases
of Windows Server, or if you go
with the default installation of Windows Server,
formerly known as Core, where you don't have
this desktop experience with a server manager.
From the start menu, here is PowerShell.
I'm going to right-click it
so that I can run it as administrator.
If I've logged into the machine as the administrator account
this extra step may not be necessary,
but it's a pattern that I've gotten used to
and it allows me to always have the access I need
regardless of how I logged in to start.
So here in PowerShell, let me go ahead
and maximize this window.
The process of renaming the server,
I like to do it in two steps.
The first is to type the cmdlet HostName.
This gives me the automatically assigned computer name.
That's not something that I want to have to remember
or be responsible for typing accurately.
So I'm going to select it, and use ctrl+c
on the keyboard to copy that information.
Now to rename the computer.
The PowerShell cmdlet for that is Rename-Computer.
And that's the basic syntax in PowerShell.
We first start with a verb, in this case rename,
and then we have a noun, computer.
Most PowerShell cmdlets have a verb-noun construct.
So we're going to rename a computer.
First we need to tell it which computer
we're going to rename.
The parameter computer name and now I'm going to hit ctrl+v
to paste the current computer name.
That's the computer we want to rename
and we want to assign it a new name on our network.
Let's go ahead and name this Srv01.
Naming conventions are very important
and as you bring up new machines
and configure them in your environment,
consider using server names that will be meaningful
to your users.
In very large organizations those names might include
something about the function and the location of the server.
In smaller to medium-size organizations,
they may be named after the task that they perform
or some people even use characters from TV series or movies
that represent a task being done by that server.
Buy make sure those decisions are deliberate.
When I go ahead and hit enter,
you'll notice that despite getting a warning
that I'm going to have to restart,
that change was done really quickly.
All we need to do now is reboot,
and that can be done using the Shutdown command,
using the r parameter for restart.
And that should take care of it.
If this server is also going to be part
of an existing active directory domain,
you should take care of joining it to the domain
as soon as it reboots.
Then and only then will you have a fresh install
of Windows Server 2019 that is ready to be put to work.