-
Notifications
You must be signed in to change notification settings - Fork 0
1.1 First Lab Prep
- AAA and Cross Platform Authentication
- Containerization
- High Availability/Failover
- Distributed Computing
- Server Automation and Provisioning
- Configuration Management
- Network Management
- DNS, Mail, Web Services
- DevOps and Agile Operations
- And as always... Troubleshooting
As with any new environment, I started by setting up the firewall first, and I configured the LAN and WAN IPs as seen in the IP information entry (Upstream Gateway 10.0.17.2, WAN 10.0.17.101, LAN 10.0.1.1)
I then finished the setup on the workstation, setting the hostname to fw01-elizabeth and changing a few other settings. Next was to finish the setup of the workstation, making a new local admin user, as well as setting the hostname (wks01-elizabeth) and the IP information (10.0.1.10, default gateway and dns 10.0.1.1)
I then checked connectivity with whoami, ipconfig, tracert 8.8.8.8, ping 10.0.1.1 and ping champlain.edu
Of note: Might be a good idea to make a script containing the check commands... make it so that it asked for input for specific things like IP addresses or hostnames
Next was ad01. After making sure it was cabled correctly, used sconfig to configure the IP information and hostname of the server core.
Now it was time to install the AD stuff on the server core. To do this I used powershell to run the following commands:
-
Install-WindowsFeature AD-Domain-Services- Install AD services -
Install-ADDSForest -DomainName elizabeth.local- Install and create the forest for your domain
Next was the management server setup. Again, it needed to be cabled, then I used sconfig to configure the hostname. I used the network and internet tools to set the IP information.
Then I used Server Manager to install the Remote Server Administration Tools for AD DS, DHCP, DNS, and File Services, and I was able to add ad01 to the mgmt01 server by right clicking "all servers" and adding it through the native tool.
I then added two domain users, a normal named one "Elizabeth Chadbourne" and a domain admin, "Elizabeth Chadbourne ADMIN" as well as all of the DNS records and associated PTR records for all of the devices I have set up thus far. This includes the firewall, the workstation, the active directory itself (making sure the records are there properly) and management (same deal as active directory, making sure all the records are there as intended.
Finally, I added wks01 to the domain, and everything was all working and happy!
Of note, I did run into an issue where I left the management server (logged out) and came back to work on it later and found that it had forgotten that it was managing ad01 as well as itself. I had to re-add ad01, but the records persisted. Will keep an eye on that and if it persists will troubleshoot to fix.
RFC1918 Private Networks - I didn't know what this was referring to, so I looked it up. It is referring to the use of private IP addresses in a network rather than public ones, so in our case 10.x.x.x IP addresses (Also refers to 192.168.x.x addresses). Regarding how this applies to the lab, it is in the firewall configuration, so by unblocking these addresses we are allowed to use private IPs within our own little network.
There was nothing else that I was confused about or wanted to learn more about regarding the lab, so instead I decided to research two of the topics that were mentioned in the lecture as stuff we were going to go over later
Containerization - When software comes packaged with just the operating system and whatever libraries it depends on. It is made to be a lightweight, easy way to run any software on any infrastructure, and is easier than VMs. Doing it this way ensures that whatever the code is will always have whatever libraries or OS it depends on, but doesn't require much of anything else. This also reduces any bugs that come from moving code to a different OS or a VM.
Cross Platform Authentication -
- Source: