Replacing SCCM with FOG Project

Replacing SCCM with FOG Project When I moved our infrastructure from Hyper-V to Proxmox, I also took the chance to rip out one of the heaviest pieces of the old stack: SCCM. For an enterprise with thousands of endpoints and a full Microsoft licensing budget, SCCM can make sense. For four instructional labs with 72 workstations, it was too much. It wanted Windows Server, SQL Server, licensing baggage, and constant babysitting just to do the thing I actually needed: boot a machine over the network, lay down a clean image, put it back in the domain, and get out of the way. FOG Project was the answer. This post is the technical deep-dive for the imaging side of the migration. For the full Hyper-V to Proxmox migration story, see the migration deep-dive. The environment I was replacing The target was straightforward on paper: 4 classrooms 72 total workstations 3 hardware-specific Windows 11 images 47 machines with known MAC addresses at import time 25 machines that would need to self-registe