Daniel Thiele IT - daniel@dproject.de

This homelab demonstrates how to build and expand a VMware-based Windows domain environment with Active Directory, virtual and physical clients, Group Policy, backup and recovery, printer deployment, and remote power management.   Because the project is too large for a single article, I divided it into smaller PDF documents. Each document covers one milestone of the setup and contains the practical steps needed to reproduce it. I will later add to this project and expand on it with Azure, MS365 and more. That will be updated here. 0 – ARES ESXi and Veeam Preparation Preparing the physical ARES computer for VMware ESXi, creating a Veeam backup, and making sure the existing Windows installation can be restored safely as aVM. 0 ARES_ESXi_Veeam_Preparation_Tutorial.pdf   1 – Restore the Windows VM on ESXi Creating a virtual machine on ESXi and restoring the previous Windows system from the Veeam backup. 1 ARES_ESXi_Windows_VM_Restore   2 – Set Up the vSwitch, Port Groups, and...

  CUPS is the Linux printer daemon. The original goal sounded simple: the Brother printer already worked through CUPS and I set that up as part of my LPIC 1 studies , so scanning should also be available from the network. In practice, the printer and scanner parts of a multifunction device are handled by different Linux subsystems. Printing was already solved through CUPS as part of LPIC 1. Scanning required a separate path through SANE, the Brother scanner backend, and finally a way to expose the scanner to Windows clients without installing scanner software on every machine. The device in question was a Brother DCP-7055 connected by USB to the Ubuntu VM  Test which was also my printer server . The working CUPS printer queue was named brother7055 , and printing was already functional. The Ubuntu host had the management LAN address 192.168.10.123 , and later we also confirmed that it had a second address, 192.168.178.123 . The network design matters here. VLAN 10 is the manag...