A study homelab turned into a real automation server
The setup began as a lab for Network+ study and hands-on practice. It used two MacBooks and a used Micro. The MacBooks ran Windows 11, 24.04, Windows Server 2022, AD DS, DNS, and IIS for practice. The Micro was the machine that changed roles.
It started as an always-on computer for , breaking things, and rebuilding them. Over time, it became the small server that handled real tasks. It now runs a few Python automation programs through Task Scheduler. One handles repeated SEO work for a study site, and another sends weekly analytics emails for iOS apps.
One automation stopped working for four weeks with no obvious crash or error. The missing weekly emails were not noticed for a month because nothing actively warned that the job had gone quiet.
Key points
- A learning homelab became a real automation setup.
- The always-on small computer became useful , not just a practice machine.
- Python automation programs ran through Task Scheduler.
- A weekly silently stopped for four weeks.
- need alerts for missing results, not only visible crashes.