Duplin domain controller into an existing domain doesn't require you to think about many options as
one of the domain controllers are reliably connected with high speed network links.
Runnier have a domain controller that are only intermittently connected or host connections are slow
such as remote sites.
There are specific considerations you need to take into account.
We'll cover it later when we'll talk about management sites and replication.
We've already deployed an additional domain controller to use in graphical user interface in this course.
But now we'll consider deploying domain controllers additional domain controllers union power shell.
In case you want to automate this process converting a server to a domain controller is a four step
process the first step is to configure network an appropriate domain controller.
This means assign sign in a fixed IP address to the server and configure in domain name sir system or
DNS to point to an existing domain controller.
If you are use an active directory Integrated DNS or to an authoritative DNS or if you are using standalone
DNS.
The second point is to install an Active Directory role on the server.
After that you have to turn the server to the domain if it isn't already a domain joint.
If this is a news server now is also the time to change the name of the server to manage your organizational
standard and the last step is to promote the server to a domain controller.
So the first step domain controller in Windows Server or domain is typically configure it is a fixed
IP version 4 address and a fixed IP version 6 addressed.
If you are using an active directory Integrated DNS configure the networking adapter use to join this
server to the domain and to promote it to domain controller.
This network adapter should boot into an existing domain controller as its primary DNS server.
If you are using standalone DNS you should configure the DNS server to point to an authoritative DNS
server for the domain to configure your adapter use.
Said this.
NET IP interface and new dash type interface command lets along with the third does DNS clients server
address command left to set the DNS server address the server I'm working with is allowed.
This is 3 so I'll be joining this server to the existing domain.
Contorts or dot com.
So if you ask them what real use is get their network adapter then will add a wearable called Nick and
it will be looking like this will get the net adapter with a foreign name.
The name of your net adapter could be different.
Now we need to reconfigure variable Nic to disable the Duge soupy.
We could do this with a full on command Nic and pipe it to set the net IP interface for this to be disabled.
Then we can figure the IP version for address the following command.
Again the result of Niek variable.
The pipe to new does not IP address command the Folarin parameters address family IP address which will
be used by the server Grafix graphics Lans type and default gateway IP address.
Next lets configure the DNS set and for Niek variable we can just pass Nic through the pipeline.
So we use Livonian.
So does DNS client server address interface.
LS The variable Nic with name property server addresses and parse through parameter Andrys command to
returns the following output.
We can also configured Nicolaides IP version 4 address or the following command left.
Again we will use new address not IP address command left and the command to look as follows.
We can always check network configuration this IP config command line we have the network and configured.
The next step is to add the Active Directory all to the server we'll use install Dasch Windows feature
come and let the Adey domain services roll to the server and the command looks like that.
Installed dush Windows feature name Adey domain services and include management tools.
You can always perform the command was What-If parameter to see what results you will get to double
check everything before doing something important to the server.
In my case it just just server.
So I didn't run the command was what if parameter.
And as you can tell from the output no restart is required.
In addition to install of the active directory domain services all installed Windows feature has installed
the full set of room on server administration tools or are set related to Active Directory domain services
or 80 years.
And the group policy management console.
And of course don't forget about help files so there is one more task you'll want to do before you join
the computer to domain and promoted to a domain controller.
Update the windows power shell get help files even if you had already done this.
Now that you've added additional modules you'll need to get the help files for those modules.
The command to update help from a local network share is as follows.
Of course you have to have these files on a local share or you can live off the source based parameter
entirely.
To go directly to Microsoft from the files.
So we are ready to adjourn the server to the domain.
You can promote a server or two domain controller in a domain that isn't a member of.
But first you could need to rename the server so you could do this in the fall or in step first Gediman
credentials for Jones who is a domain admin.
The second step is to add computer to contorts or dot com with a credential you've got before and renamed
the server to whatever name unit and the last step is to restart the server again get cadential command
prompts you for domain credentials to join the server to the domain and the ADD computer command combines
the domain join with the computer rename aberration rather Sorber reboots.
You can log on as your domain credentials and it will have its new name applied.
If you only need to remind the computer user rename Desch computer command led.
This allows you to rename a server even after it has been promoted to domain controller.
In most cases but it doesn't require a restart after running the command.
Now we are ready to promote a server to a domain controller promoting a Serota domain controller uses
only one command installed us 80 D.S. domain controller.
There are a lot of options and parameters to the process most of which you won't need except in specialized
circumstances.
As you can see here we have parameters like domain name site name skip or check safe mode administrator
password Adey prep credential allow domain controller install EHLO password replication account name
and application partition replicated and of course there are many more parameters like DNS related database
related.
So this will pass and so on.
Before you deploy a new domain controller it's good practice to test the deployment to ensure that it
will work.
This allows you to pretest environment during working hours and then perform the actual deployment Duren
of hours and the extra replication traffic is less likely to affect overall network speeds to test the
deployment.
You'll use the same command parameters you expect to use during the actual deployment.
Then if the deployment is reasonably close in time to your test you can skip the pre-check stage.
The parameter for it is does keep rechecks during the actual deployment because that just repeats the
prerequisite checks.
Let the test come on.
Let's use this so for protest and we use a full on command test.
There's a d d domain controller installation with a full and parameterless no global catalog.
Create DNS delegation.
Typical Erik placation only database path domain name or press and some more like no reboot on completion
side may so this will pass.
Install DNS perimeter and force parameter.