Activity 4:
Domain Controller
Amaba, Marcus Albert M. December 31, 2017
CPE42FB1 Engr. Ariel Isidro
//Update Windows 2008 Server. Go to Start > Windows Update.
//Once the updates installation was finished, shut down the Windows Server.
//Clone your MS Windows Server on the Virtual Machine.
//After cloning the Windows 2008 Server, turn on the original Windows 2k8 Server and
configure the initial settings again. This screenshot shows the configuration of IP
address.
//Type dcpromo in the search box to run the Active Directory Server.
//You will be immediately prompted into the installation wizard. Click next.
//Select the Create a new domain in a new forest option then click next.
//You will be needing a Fully Qualified Domain Name which needs to be in the form of surname.local.
In this case it is named as amaba.local.
//Click Next after configuring the Domain NetBIOS name.
//Choose Windows Server 2003 as your forest functional level.
//Select the additional domain controller options for DNS server.
// Select the Yes option.
//Input your desired password.
//This means the active directory is now being installed.
//This shows the Active Directory Server that was made earlier.
//Create a new User by right clicking the Directory Server and hovering to New then click User.
//Fill up the User creation fields with the required and desired credentials.
//Put in the desired password to complete user creation.
//This is the summary of the User Credentials.
//Include the DHCP server as one of the new roles to be set up.
//Use the IP address of the Windows Server 2008.
//The required text fields will be automatically filled up.
//Input the appropriate value of IP addresses, Subnet mask and Default gateway into the DHCP Pool.
//Install the following roles, roles servers, and features.
//Make sure the Windows Client is a part of the amaba.local domain.
//Log-in with the username and password from the configuration steps before. In this case, the
username is marcus and the password is Mayalong1222.
//It is successfully connected in the domain.
//This shows who is currently logged in in the Domain Controller.
Observation
Few observations have been made in creating this Activity. I observed that
Windows require too much passwords for good security. Next, I also observed that
Windows Client and Windows Server look different from each other. These two also has
different interfaces from each other. Lastly, I observed that using Windows Server on
your own and without the help of references is quite confusing as we are only used on
using the Windows Client.
Recommendation
For this activity, I recommend to remember the passwords you create for each
field. Making different passwords will make users confused on which password they
have used. I recommend same password all throughout the configuration process. I alsi
recommend to use passwords that are secure, not just short and easy to predict ones.
Windows will automatically prompt you if your name or birthday is included in your
password as it is prohibited.
Conclusion
There is only one thing I have learned in this activity but that one learning is a big
one. That is how to set up an Domain Controller. I believe I will be using it in the near
future since I intend to work on a Network company. This is a good foundation in the
computer engineering world and can be used as an edge on other students.
Lessons Learned
First and foremost, I learned the importance of assigning IP addresses. This
activity taught me that IP addresses can not only be any random IP Addresses. It has also
taught me the relationships between IP Addresses and Default gateways. I can use this in
the future by configuring small networks in the office or even configuring individual
computers. Next is the changing of the domain group. I am not familiar on how to
include the client within the domain and I needed to ask few people about it. Now that I
know it, I can easily navigate through it. Lastly, I learned how to set up server roles. You
need to be extra careful here as one wrong move will make your Domain Controller
broken.
