10 Lab - Add Windows 7 Client To A Server 2012 Domain

Lab -Add Windows 7 Client to a Server 2012 Domain
Overview
In this lab, we add our windows 7 Professional VM to our freshly built Server 2012 domain. We
have a Domain controller, a DNS and DHCP server and as long as the client can see the 2012
Server as being on the same network, there should be no issues with joining any Windows client
with the right capabilities to the network.
First some caveats about adding any device to a domain network. When we take any machine out
of the box or drop any existing machine onto a new network, the machine must be able to see the
network to be able to find the DNS server, the DC, the DHCP server and the Default Gateway
(DFGW). We can’t just come into a Windows domain and start browsing the network. as if we
owned it.
Before we can add the new machine to the network is needs to be configured with the correct IP
information needed to join the domain.
Now click on the Advanced system settings link on the left hand side.
1
© 2016 syberoffense.com All Rights Reserved
When the advanced system settings open, switch to the computer name tab.
2
Click on the change button. From here you can change your Computers Name to a friendlier
name.
3
Select the radio button for Domain. The text box now becomes available.
Type in the name of your domain, in this example we’re using CMIT369.local but the name of
your domain may differ. You can call your domain anything you want!
Some caveats need to be added. Active directory should be designed to allow for expansion and
growth. To this end we should use a domain name which makes sense. The name could be based
on the organizations identity, location or function or all three.
It’s much easier to do this right the first time than to come back in six months and redesign
Active directory. In this example I have used the name the of the course. But I could also expand
the name and added UMUC to create the domain name of CMIT369.UMUC.local and we could
expand the name even further by adding in Server2012 to create CMIT.UMUC.Server2012.local.
Carefully think your AD design through and be sure to get management’s approval. Remember,
if you touch it, you own it.
Why (dot).local?
We use the domain extension of (dot).local to prevent the internal network from being routed out
to the Internet. There is no top level domain for. local. This keeps all traffic queries for the. local
domain internal. Any other queries such as .com or .net can be forwarded to the outside DNS
server provided by our ISP or organization.
4
What’s a naming convention?
The naming convention used to identify machines on the network is just important as your
domain name. This should all be established beforehand. When you see a DNS record or an AD
object for a computer, a printer or a server you should be able to tell immediately if it is the
machine you’re looking for.
We should know where every machine on the network is located and what port it is connected to
starting at the switch. Again, this is all part of the design process for Active directory. In this
example, we see the machine is named Win7Pro_HR01. We can look at the machine name and
we know this is a Windows 7 Professional client assigned to HR.
I might have a switch in my wiring closet just for HR. The 01 could represent the port number
assigned to the machine on the switch. Hopefully whomever wired the network took the time to
tone out the cabling and correctly mark the locations of the end points.
When we have finished adding our machine to AD, it will appear inside the Computers OU
container. Inside the Computer OU Container I could have a sub container for each
organizational department such a HR, Sales, Engineering, Warehouse or IT. Again, this all part
of your Active Directory design. If I have remote locations, I could add the name of the location
to the computers name and have a container inside of the OU container for Computers using the
name of the Remote location such Tucson or Phoenix. We abbreviate the name as much as
possible.
I don’t have to write out the word Windows or Professional in the computer’s name. Same with
the location. Human Resources is abbreviated HR. If the machine in located in Tucson, I can
abbreviate Tucson as TUC or Phoenix for PHX.
Once the machine has been added to the domain, I can move the client to its correct container
under Computers.
The rule of thumb for designing any naming convention is to keep it simple.
5
When you hit enter, or click ok, you will be asked for the domain administrators user name and
password. This is the username and password you use to log onto your Server 2012 R2 DC.
If you specify the correct credentials you will be welcomed to the Domain.
6
Your domain name may differ and that’s fine as long as your machine has joined successfully,
you are a go with this portion of the lab.
Caveat
Your Windows 7 machine must be able to find a DNS server for your domain. If you receive an
error message no DNS server could be located for the network, you will need to go into your
adapter settings and add the IP address for your server.
When your machine comes back up after the restart, CTRL+ALT+DELETE to logon. Your can
also send a CTRL+ALT+DELETE message by clicking on Player in the taskbar menu of
VMWare.
7
When you get to logon Window, click the Switch User button.
Click the icon for the Other User
8
In the next window, use domain\administer name and password to logon on to your Server 2012
R2.
VMWare message pops up…. Click OK. Log off and back on.
9
Now we see this…. type in your domain password.
Let’s find our new machine inside of Active Directory.
Logon on to your Server 2012 DC.
Click on the start button and click on the tile marked Administrative Tools.
From the context menu, click on the Active Directory Users and Computers snapin.
10
Click on your domain name and the open the Computers OU. In the right windows pain, you see
the computers that are member of your domain.
Right click on the name of your Windows 7 PC. Here you see all the options you have for
dealing with a computer in AD.
11
Click on View and from the context menu, select Advanced Features. Now you can see all the
containers that AD provides.
The Computers folder is not an OU but a container or an object in LDAP database. We cannot
add OU’s to the object. To better manage our computers we can create a new OU giving it
12
friendly user name such as ‘Domain Computers.’ Notice some folder icons appear different.
These folders are actually OU’s and can have additional OU’s
In the left window pane, right click on your domain name and select New>Organizational
Container. Name the container based on the location of your Windows 7 machine. In this
example, I named the OU, ‘Domain Computers’
13
Find your new OU at the bottom of your container list.
14
Right click on your new OU, select New and Organizational Unit.
Create a new OU inside your existing OU and name based on the department or location of your
Windows 7 PC.
15
Now we have a sub OU inside our new OU.
Click on your default Computers container and in the right pane, right click on the name of your
PC and select move.
16
From the list, open your new OU and select your new sub OU and click OK.
When you open the sub OU, here you will see the new location of your PC.
17
The way we design our Active Directory has a huge impact on how well we manage it. Keep it
simple and keep it clean. Of course you can just use the default Computers container but there is
no way to organize the content. Do it right the first time and months and years from now, the
design will still be effective.
End of the lab!
18

10 Lab - Add Windows 7 Client To A Server 2012 Domain

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

10 Lab - Add Windows 7 Client To A Server 2012 Domain

Uploaded by

Copyright:

Available Formats

Lab -Add Windows 7 Client to a Server 2012 Domain

Click the icon for the Other User

Let’s find our new machine inside of Active Directory.

Logon on to your Server 2012 DC.

End of the lab!

You might also like