Inside the infrastructure.

04 My Role

Worked with management to identify service editions and licences, then organised accounts, access and learning resources around college policies.

05 Implementation

• Created internal staff, external staff and student accounts with appropriate roles and licences.
• Organised OneDrive folders and departmental permissions, Azure VMs and Outlook signatures.
• Configured LMS users, roles, resources and surveys to suit college requirements.

06 Security

Role-based permissions and departmental folder access were part of the work. The diagram groups users and services conceptually; it does not disclose a real tenant, domain, IP address or security boundary.

07 Outcome

Completed within a month, with services available from the first student enrolment. Continued refining the environment after launch.

08 Lessons Learned

Design account roles and folder ownership before provisioning. Treat onboarding, learning resources and communication tools as one connected user journey.

04 My Role

Built and administered virtual machines, directory roles, organisational units and user policies in the project environment.

05 Implementation

• Installed AD DS, a child domain and a read-only domain controller in virtual machines.
• Checked domain controllers and member computers from the root-domain environment.
• Created OUs and users; managed passwords, account states and departmental permissions.
• Applied application-access restrictions and a policy to hide the password-reveal button.

06 Security

Directory permissions and Group Policy restricted access to applications. A read-only domain controller formed part of the design; the diagram does not imply unrestricted trust or access between all systems.

07 Outcome

Configured Active Directory, organisational units and user accounts, then applied application-access constraints to the virtualised environment.

08 Lessons Learned

Separate directory structure from policy scope. Verify the experience from a member endpoint, rather than relying only on the administrator’s view.

04 My Role

Designed the topology and addressing, configured departmental segmentation and first-hop redundancy, and implemented routing and translation scenarios.

05 Implementation

• Planned device subnets and routed links between Layer 3 switches and routers.
• Assigned departmental access switches and VLANs across five departments.
• Implemented first-hop redundancy on Layer 3 switches and OSPF routing in the routing scenario.
• Explored NAT-PT for IPv6-only to IPv4-only communication in the historical project lab.

06 Security

VLANs separate broadcast domains; controlled communication also requires routing policy and access controls. The reference diagram illustrates a firewall and controlled access between segments.

07 Outcome

Completed the VLAN, first-hop redundancy and NAT topology, plus a separate OSPF and IPv4/IPv6 translation scenario. The two scenarios demonstrated segmentation, resilient gateways and routed connectivity.

08 Lessons Learned

Verify segmentation and failover independently of basic reachability. Record routing and translation assumptions; NAT-PT here describes historical lab work, not a current deployment recommendation.