Summary

This lab had us use a vm that ran the Windows server operating system and getting the hang of the new tools it brings us, specifically active directory. We started with a basic setup by assigning the IP, subnet, gateway, and DNS. The hostname was changed and time zone to the required material and rebooted. After the server manager was booted up to the add roles and features menu to add active directory domain services. After installation the download required post deployment configuration. The configuration required to promote the server to a domain controller. A wizard window prompts to choose a deployment option in which a new forest was created ending with .local. When rebooting I logged into the domain admin instead of the local admin. DNS settings had to be altered as currently the DNS was a local loopback. Under the server manager and the DNS tab. The proper host and lookup zones were added to the proper credentials. Under the active directory, two new users were made with one being an admin user added to the domain admin group, and a non admin user. Finally the DNS of the workstation I wanted to connect had to be altered properly which is very IMPORTANT. After verification in powershell the two machines are fully connected.

Terms

1. What are reverse lookup zones?
2. What's so special about .local that machines are giving warnings about
3. What's a PTR record?

Notes

• Remember to alter the DNS of the machine you want to connect as its easy to miss and mess up
• If the connection states its missing, then reboot