Virtualization
MACVM01 runs as VM 500 on Proxmox with OVMF, Q35, four virtual CPU cores, 4 GB memory, and an 80 GB system disk.
Home Lab · Cross-platform administration
I deployed a macOS 12.7.6 virtual machine in my personal home lab, placed it on the pfSense-managed LAN, joined it to the Windows Server Active Directory domain, and validated identity, DNS, network, SSH, and VNC administration.
Implementation
MACVM01 runs as VM 500 on Proxmox with OVMF, Q35, four virtual CPU cores, 4 GB memory, and an 80 GB system disk.
The virtual NIC is attached to vmbr1, placing the guest behind pfSense on the lab LAN instead of the upstream network.
The computer account MACVM01$ is joined to ad.jeremyfontenot.online, and mobile domain-account creation is enabled.
MACVM01 uses DC01 for DNS. Forward lookup resolves the domain-qualified host name, and reverse lookup identifies MACVM01.
Remote Login is enabled and authenticated SSH sessions were completed from DC01 using both the local administrator and the domain mobile account.
macOS Screen Sharing is reachable from DC01 on TCP 5900 and was used through a VNC viewer for graphical administration.
Observed results
The statements below are limited to the captured personal-lab results.
MACVM01 reported macOS 12.7.6, computer name MACVM01, and the domain-qualified host name MACVM01.ad.jeremyfontenot.online.
The guest reported the expected Active Directory forest and domain, an enabled computer account, Kerberos authority generation, and mobile-account creation.
A domain mobile user signed in successfully and directory identity resolution returned the expected domain account context.
The guest received LAN address 10.10.20.101, used pfSense gateway 10.10.20.1, and used DC01 at 10.10.20.10 for DNS.
DC01 successfully reached TCP 22 and TCP 5900, and interactive SSH and VNC sessions were completed.
The guest uses the America/Chicago timezone with network time enabled.
Skills demonstrated
MACVM01 expands the Home Lab beyond Windows and Linux by demonstrating practical macOS integration with the same identity, DNS, routing, virtualization, and remote-management services.
Configured a macOS guest on Proxmox, reviewed virtual hardware, selected the correct Linux bridge, and corrected network placement behind pfSense.
Bound macOS to Active Directory, validated the computer object, enabled mobile domain accounts, confirmed domain identity resolution, and preserved Kerberos-aware configuration.
Validated forward and reverse DNS, gateway and DNS assignment, LAN placement, port reachability, hostname state, and the difference between upstream and pfSense-managed network paths.
Enabled and tested SSH and VNC access from DC01, administered local and domain accounts, corrected timezone configuration, and documented verified results and limitations.
Boundaries
This is a personal nonproduction implementation. It does not prove enterprise-scale Apple administration, MDM, Apple Business Manager integration, production readiness, high availability, disaster recovery, compliance certification, continuous availability, or complete security assurance. Port tests establish reachability at collection time; they do not independently validate every security control.