Project Scope
Delivery Context
2023 internship final infrastructure implementation completed for a company environment.
Operational Environment
Automation engineers working with PLC software from engineering workstations.
Core Platform
Dell PowerEdge T330, VMware ESXi 7, VMware vCenter, Cisco switching, OpenVPN, and Veeam.
Primary Workflow
Centralized upload, storage, access, backup, and return of virtual machines during development and commissioning.
Project Overview
Completed in 2023 as an internship final infrastructure implementation, this project introduced a centralized virtual machine management system for automation engineers working with PLC software.
The main objective was to replace workstation-based and removable-media workflows with a controlled server-based platform that improved storage, access, update handling, and operational consistency.
The resulting design combined Dell PowerEdge T330 hardware, VMware ESXi 7, VMware vCenter, VMware Workstation workflows, VLAN-based access separation, remote connectivity, and backup planning.
Context and Problem
Before the project, virtual machines were typically stored on local workstations or removable media, even though they were required for PLC-related development and commissioning work.
That created several practical problems: no central backup location, no reliable way to keep the latest version visible to multiple users, and no consistent approach for local and remote access.
The system also needed to support a real workflow where a virtual machine could be downloaded to a physical drive for on-site work, then uploaded back to the server so the latest verified version remained centrally available.
Infrastructure Components
The implementation combined physical infrastructure, virtualization, networking, user workflow, remote access, and recovery planning into one controlled environment.
Hardware
- Dell PowerEdge T330 prepared as the physical host platform for the centralized VM environment.
- Engineering workstations used as user endpoints for VMware-based VM handling.
Virtualization
- VMware ESXi 7 used as the hypervisor.
- VMware vCenter included to support centralized administration and host visibility.
- VMware Workstation used for user-side connection, upload, and download workflows.
Networking
- Cisco 2960 switch used as the local switching layer for workstation-to-server access.
- VLAN 111, 222, 333, and 444 planned to separate users and prevent IP conflicts between similar VM environments.
- Router and firewall provided the upstream security and internet path.
Remote Access
- OpenVPN used in the project documentation as the remote access approach for secure connectivity.
- Remote users needed to work as if they were on the local company network.
Backup
- Veeam Backup & Replication selected for backup and restore demonstration because of strong VMware integration.
- Backup handling was planned outside the main server platform to reduce recovery risk.
What I Implemented
- Prepared the Dell PowerEdge T330 and used iDRAC for remote server access, remote media mounting, and installation control.
- Installed VMware ESXi 7 from ISO, configured the base host, and validated browser-based access through the vSphere client.
- Configured core post-installation tasks such as network settings, static addressing, time synchronization, system updates, and SSH enablement for administration and troubleshooting.
- Documented the installation and initial setup of VMware vCenter to support centralized administration of the ESXi host and virtual machine inventory.
- Defined VLAN 111, 222, 333, and 444 on the Cisco switch so separate users could work without overlapping VM IP conflicts.
- Documented the VMware Workstation workflow for connecting to the server, uploading a VM, downloading it for field work, and returning the updated version to centralized storage.
- Defined archive and naming logic so virtual machines could be tracked by project number, name, and upload timing rather than stored chaotically.
- Documented the OpenVPN-based remote access concept for off-site connectivity into the environment.
- Reviewed account and permission handling within the VMware environment.
Reliability and Backup Considerations
Centralized hosting reduced dependence on individual user devices and made storage ownership, access, and VM state easier to control.
The workflow was designed so the latest working VM could remain on the server as a backup reference, while older copies could be removed after verification to reduce version confusion.
Veeam Backup & Replication was selected for the project documentation because it integrates directly with VMware environments and supports restore, replication, and off-host recovery planning.
Documented configuration, storage conventions, and user workflow were treated as maintainability controls that supported long-term reliability.
Testing and Validation
Verification focused on practical infrastructure checks in both physical and virtual environments rather than abstract evaluation.
- Validated ESXi host accessibility, browser-based vSphere login, and general management connectivity.
- Checked network reachability from Windows workstations and confirmed the host worked with the configured static addressing.
- Tested virtual machine upload, download, and centralized availability through the VMware Workstation workflow.
- Reviewed user authentication, access control, and controlled separation through the planned VLAN structure.
- Reviewed VPN connectivity, backup and restore considerations, and error-handling points as part of the validation approach.
- Used both the physical environment and the virtual environment as part of the validation mindset described in the report.
Key Learnings
- Centralized VM infrastructure supports availability, version control, and collaboration more effectively than unmanaged local storage.
- Virtualization design depends on user workflow, network segmentation, and backup planning as much as on the hypervisor itself.
- Remote server access and installation tooling such as iDRAC can materially simplify infrastructure deployment work.
- Documentation is part of delivery quality in infrastructure projects, especially where multiple users depend on a shared system.
- Validation should cover the full operating workflow, including upload, download, remote access, and recovery assumptions.