✨ SYS-265-01 Final Group Project ✨

For this final project our team was tasked with building a medium-sized enterprise from scratch for a client over a period of some weeks. As part of this project we demonstrate integration efforts to a client manager as a part of user acceptance testing in a series of milestones, as seen below.

✨ System Infrastructure and Project Assignments✨

Item	OS	IP address	Documentation	Person
`DC01-sparkle` `DC02-sparkle`	Server Core 2019	`172.16.1.12` `172.16.1.13`	config documentation	Mike
`DFS1` `DFS2`	Server Core 2019	`172.16.1.17` `172.16.1.18`	config documentation	Mike
`dhcp1-razzle` `dhcp2-dazzle`	CentOS 7	`172.16.1.10` `172.16.1.11`	config documentation	Matt
`docker-sparkle`	Ubuntu	`172.16.1.5`	config documentation	Matt
`fw01-sparkle`	PfSense	WAN: `10.0.17.75` LAN: `172.16.1.2`	config documentation	Matt
`mgmt01-sparkle`	Server 2019 GUI	`172.16.1.14`	config documentation	Mike
`mgmt02-sparkle`	Ubuntu	`172.16.1.16`	config documentation	Mike and Hanne
`util`	CentOS 7	`172.16.1.15`	config documentation	Mike + Matt
`w1` and `w2`	Windows 10	`172.16.0.100` `172.16.0.101`	config documentation	Hanne
Network Diagram	N/A	N/A	Network Diagrams	Mike
RVTM	N/A	N/A	RVTM Link	Hanne
Videos	N/A	N/A	Milestone 1 Milestone 2	Hanne

Build documentation can also be found by clicking on each Milestone header!

✨ Milestone 1 ✨

Provide a link to your group GitHub repo that shows:

Routing works (systems can talk to one another and route to the internet)
Domain Users are created
Domain Joined W1, W2
Redundant ADDS (this means that either can be down and that domain services are still
provided)

Incorporates the following GitHub features:

Additionally:

Build documentation for each system involved
Build RVTM that is in progress for each system
Build Network Diagram with relevant details and design via https://www.planttext.com/ Example Network Diagram Here
- IPs, Hostnames, OS's, Services (some servers might have 2+ services, so include them as well)

Quick Video proving:

Routing works (system to system, system to internet)
W1 and W2 are AD Domain joined
ADDS is redundant
Reference Network Diagram
All Team Members present on their GitHub repo portions referencing their features listed above

✨ Milestone 2 ✨

Provide a link to your team's GitHub repo that shows the build documentation for each system involved as well as the RVTM that is in progress for each system.

Redundant Linux DHCP works
Ansible Controller and nodes are configured
Util is domain joined
MGMT02 configured
Documentation Updated

Provide a link to your group tech wiki that shows:

Incorporates the following GitHub features: Wiki, Issues, Labels, Milestones and Boards
Build documentation for each system involved
Update RVTM that is in progress for each system
Update Network Diagram with relevant details and design via https://www.planttext.com/ Example Network Diagram Here
- IPs, Hostnames, OS's, Services (some servers might have 2+ services, so include them as well)

Quick Video proving:

Redundant Linux DHCP works
Ansible Controller and nodes are configured
Util is domain joined
MGMT02 configured
Reference Updated Network Diagram, different from Milestone 01
All Team Members present on their GitHub repo portions referencing their features listed above

✨ Final ✨

Incorporating the following GitHub features: Wiki, Issues, Labels, Milestones and Boards
Docker service is deployed
DFS based profiles
Ansible Services
Ansible Users
Group Policy completed
Final Documentation Complete