From an Old Desktop to a 15U ZimaOS Homelab with Windows Server

Eva Wong is the Technical Writer and resident tinkerer at ZimaSpace. A lifelong geek with a passion for homelabs and open-source software, she specializes in translating complex technical concepts into accessible, hands-on guides. Eva believes that self-hosting should be fun, not intimidating. Through her tutorials, she empowers the community to demystify hardware setups, from building their first NAS to mastering Docker containers.

Thank you to u/Wolfishllama601 for sharing the third version of a homelab that grew from an old desktop into a 15U rack. ZimaOS runs on an HP computer and brings together file storage, media, Minecraft management and a Windows Server virtual machine used for network services.

The original Reddit post explains the earlier versions as well as the current hardware. It is a story about gradually learning what a home setup needs, from mounting equipment correctly to deciding whether another router should actually be part of the live network.

Three Versions Changed More Than the Rack Size

Version one used an old second-generation Intel Dell PC running Ubuntu Server for file storage and music streaming. The next version moved into an 18U audio rack, with an HP switch and a fourth-generation Lenovo ThinkCentre. The creator remembers not knowing that the rack required cage nuts rather than simply accepting M6 screws.

The current version uses a Vevor 15U server rack that extends to 1,000 mm depth. Its lower U count does not tell the whole story: the owner describes moving to a server rack with the physical arrangement needed for this collection of equipment.

That progression is useful because each stage answers a different question. The first machine established useful services; the second introduced equipment mounting; the third brings the server and networking components into a more deliberate layout. It does not require every older part to remain active simply because there is room to mount it.

Wolfishllama601โ€™s 15U homelab rack with the HP desktop server, Cisco networking equipment and open shelf space
The third-version rack holds the HP server and networking equipment, with shelf space still available. Original photograph: u/Wolfishllama601 on Reddit.

ZimaOS Runs the Service Collection on an HP Desktop

The creator identifies the host as an HP 290 G2 with an i5-7500, 24 GB of DDR4 memory and 1 TB plus 2 TB hard drives. Those model and component details are reported by the owner. The thread does not provide a board-level hardware audit or a detailed disk layout.

Part of the setup Reported responsibility
HP desktop running ZimaOS Main host for storage and applications
1 TB and 2 TB hard drives Installed storage; redundancy layout not specified
Jellyfin Media service
Navidrome Music streaming
Crafty Controller Minecraft server management
Windows Server 2025 VM Domain controller and RADIUS roles
Cisco 3560 PoE switch and Aruba 205 AP Network switching and wireless access
Cisco 2811 router Mounted equipment the creator says is not in use

The application list keeps the server connected to everyday use. Files, music, video and game servers offer reasons to maintain it after the excitement of arranging the rack has passed. The Windows VM adds a different learning area on the same physical host.

Media and Minecraft Have Different Maintenance Needs

Jellyfin and Navidrome serve existing libraries. Crafty manages a Minecraft environment whose world can change while people play. All three are useful services, but the information that matters during recovery is not identical.

Craftyโ€™s official Backup Manager guide describes selectable locations, retained backups and the option to stop a server while copying its data. Those controls provide relevant context for the Minecraft role listed here. The Reddit post itself does not state which backup options the owner has enabled.

For a similar combined server, a useful service record would identify what must be retained for each application: a game world, music files, application settings or a database. That would make a future reinstall easier to plan than treating every item as an interchangeable app icon.

Our Pi-hole-to-family-server story follows another machine as its household duties expand. In both examples, the evolving service list explains why the hardware continues to matter.

The Windows VM Makes Identity Part of the Lab

The Windows Server 2025 guest is listed as a domain controller and a RADIUS server for the Aruba access point. This introduces identity and network access into a setup that also serves entertainment and files.

Microsoftโ€™s Network Policy Server overview explains RADIUS authentication, authorization and accounting, including its use with wireless equipment. That is useful background for the role described by the creator; the thread does not name the Windows role implementation or publish its policies.

The dependency is worth understanding before making changes on a similar host. An update that stops the Windows guest could affect a different user interaction from an update that only stops a media application. Exactly which connections would be affected depends on the access-point and authentication configuration, which the source does not provide.

A simple maintenance note separating โ€œmedia unavailableโ€ from โ€œauthentication unavailableโ€ would make that distinction visible. This is an operating lesson drawn from the listed responsibilities, rather than a claim that the contributor has already documented such a procedure.

A Mounted Router Does Not Have to Be an Active Router

The creator explicitly says the Cisco 2811 is not being used, citing a desire to avoid double NAT and the inability to run a cable to the bedroom. Keeping that detail prevents the photograph from becoming a misleading network diagram.

The Cisco switch and Aruba AP have their own stated roles, while the spare router remains part of the collection. The images show equipment placement and patching; they do not establish a complete VLAN policy, routing design or security boundary for the household.

Front view of Wolfishllama601โ€™s rack with the Cisco router, PoE switch, patch panel and HP ZimaOS host
The front view separates the mounted router, PoE switch, patch panel and HP host. The creator says the router is not currently in use. Original photograph: u/Wolfishllama601 on Reddit.

This is a useful habit for reading any homelab photo: ask which devices are carrying traffic and which are present for learning or future experiments. A more populated rack is not automatically a more complicated live topology.

Physical Organization Supports the Next Round of Learning

The cage-nut anecdote grounds the upgrade in a practical mistake. Equipment needs a mounting method that suits both the rack and the item being installed. The shelves and open space in the new photographs make the arrangement easier to follow than an app list alone.

The creator still describes being relatively new to homelabbing. That keeps the project open-ended without pretending the rack is a finished reference architecture. The source does not include noise measurements, wall-power readings, a redundancy plan or an independent backup test.

For comparison, the small homelab story from u/jc-21 shows another approach to assigning jobs within limited space. Readers considering an integrated storage host can consult the ZimaCube 2 product page separately. The machine in this contributorโ€™s rack remains the HP desktop running ZimaOS.

FAQ

What runs ZimaOS in this build?

The owner identifies an HP 290 G2 desktop with an i5-7500, 24 GB DDR4 and two hard drives. These are the creatorโ€™s reported hardware details.

Why is Windows Server part of the setup?

The creator lists a Windows Server 2025 VM with domain-controller and RADIUS roles, including authentication for the Aruba access point.

Is the Cisco 2811 handling the home internet connection?

The source says it is not being used. The creator wants to avoid double NAT and cannot run the desired cable to the bedroom.

Does the rack prove that the storage is redundant?

No. Two drive capacities are listed, but the post does not specify a redundancy layout or an independent backup and restore arrangement.

Conclusion

Wolfishllama601โ€™s third homelab combines an increasingly deliberate physical layout with a wider set of ZimaOS services. The clearest lessons come from its specific decisions: learn how the rack mounts work, distinguish active networking from spare equipment, and recognize that a media application and an identity VM have different dependencies. The two original photographs keep those choices connected to the actual build.

Welcome to the ZimaSpace community! Share your setup, ask questions, and explore practical build guides, real user stories, and product updates with fellow self-hosters.

Zima Campaign Hub

More to Read

Get More Builds Like This

Stay in the Loop

Get updates from Zima - new products, exclusive deals, and real builds from the community.

Stay in the Loop preferences

We respect your inbox. Unsubscribe anytime.