| 1 |
Redundant AD Infrastructure |
DC1, DC2, W1, W2, MGMT1 |
Shut down DC1 β log in to W1 with a domain account and open ADUC. Repeat with DC2 shut down instead. Both should work independently |
| 2 |
Redundant DHCP |
DHCP1, DHCP2 |
Shut down DHCP1 β on W1 run ipconfig /release then ipconfig /renew β should receive a new IP lease from DHCP2. Repeat with DHCP2 shut down |
| 3 |
Ansible Interactive |
MGMT2, DC1, DC2, DFS1, DFS2, UTIL, Linux systems |
From MGMT2 run ansible all -m ping β all non-Windows, non-firewall systems return pong. Run an ad-hoc command e.g. ansible all -m command -a "uptime" against all targets |
| 4 |
Ansible Deploy App to Util |
MGMT2, UTIL |
From MGMT2 run the Ansible playbook targeting UTIL β application installs without errors. SSH to UTIL and confirm the application is installed and running. Can check on W01 on http//172/16/1/15:9090 |
| 5 |
AD Infrastructure & Domain Join |
DC1, DC2, DFS1, DFS2, MGMT1, W1, W2, Linux system |
On each Windows machine check System Properties β domain shows as groupname.local. On the Linux system run realm list or id <domainuser> β confirms domain join |
| 6 |
Group Sudo β linux-admins |
DC1, Linux system |
In ADUC confirm the linux-admins security group exists and has members. SSH to the Linux system as a member of linux-admins and run sudo -i β should get a root shell without errors |
| 7 |
Docker Wiki |
UTIL or designated Docker host |
Run docker ps β wiki container shows as running. Open the wiki URL in a browser β page loads. Confirm it is not WordPress |
| 8 |
GPO Wallpaper |
DC1, W1, W2, MGMT1 |
Log in to W1, W2, and MGMT1 β corporate wallpaper should be set as the desktop background. Run gpresult /r on each machine β confirm Corporate Wallpaper appears under Applied Group Policy Objects in USER SETTINGS |
| 9 |
GPO Remote Desktop between W1 and W2 |
DC1, W1, W2 |
From W1 open Remote Desktop Connection β connect to W2's IP β session opens successfully. Repeat from W2 to W1 |
| 10 |
Profiles and Shares on DFS |
DC1, DFS1, DFS2, W1, W2 |
Log in to W1 as a domain user β open File Explorer and confirm the home directory maps to the DFS share e.g. \\groupname.local\users\<username>. Log in as the same user on W2 β profile and files follow |
| 11 |
Ansible β apt package install |
MGMT2, Ubuntu/Debian node |
Run the Ansible playbook ansible-playbook /etc/ansible/playbooks/apt_install.yml -K and enter passwordβ no errors. SSH to the target and run dpkg -l <packagename> β package shows as installed |
| 12 |
Ansible β yum package install |
MGMT2, CentOS/Rocky node |
Run the Ansible playbook ansible-playbook /etc/ansible/playbooks/yum_install.yml -K β no errors. SSH to the target and run rpm -q <packagename> β package shows as installed |
| 13 |
Ansible β Linux local user |
MGMT2, target Linux node |
Run the Ansible playbook ansible-playbook /etc/ansible/playbooks/add_linux_user.yml-K β no errors. SSH to the target and run id <newusername> β user exists. Confirm SSH or password login works |
| 14 |
Ansible β Windows domain user |
MGMT2, DC1 |
Run the Ansible playbook ansible-playbook /etc/ansible/playbooks/add_windows_user.yml β no errors. Open ADUC on DC1 and confirm the new user account exists. Log in to W1 or W2 with the new domain account β login succeeds |