I’m in the midst of deploying a new lab for learning, demo-ing, and delivering training on Windows Server 2012 R2 and System Center 2012 R2 (WSSC 2012 R2). I’ve flattened the WS2012 lab and am starting from scratch … by using the MSFT vision. The first thing up was a management host running Hyper-V. Second: a DC. Third: VMM 2012 R2.
My plan is to use VMM to build everything else. My "management" host is actually a storage box. It runs my System Center VMs, but it’s also where I run my virtual storage machines, including iSCSI target, and SMB 3.0 Scale-Out File Server VMs. I want my storage to be up before my demo hosts/cluster, and I also want to be able to re-deploy my storage quickly.
Hmm, that sounds like I need a Service Template. So I created a generalized VHDX for WS2012 R2, created a bunch of VM templates with the roles/features I need, and created a 2-tier service template:
- A VM running the iSCSI Target: My shared storage for the SOFS – no I can’t use Shared VHDX because that must live on shared storage … and the iSCSI Target/SOFS will be my lab’s shared storage … in this iteration anyway.
- 2 VMs with clustering and file services: My SOFS nodes.
The demo SOFS is deploying right now as I type:
Once the storage is running, I will turn my attention to Hyper-V. The plan is to build up server profiles, logical switch, etc, and do bare metal host deployment. It should be fun #Nerd