Best Practices: Building a home System Center Test environment Part II

Part II (Create your first virtual machine)

So to recap in Part I we covered:

-Some basics around choosing hardware
-Where to get install media from
-How to Install Hyper-V depending on if you are installing from a workstation or server based OS.

Now that you have your base Hyper-V install we can begin setting up the first VM.

Launch Hyper-V Manager

 New-Virtual Machine

Click Next

Name your VM and choose a location

Choose Generation 2

Assign Memory

Add A connection for a NIC

Click Next

Select Install an Operating System and point to your Windows Server 2012 R2 ISO and click Next

Click Finish

Right click your newly created VM–Select Connect–Click Power button–Press Enter to Boot to the ISO

Click Next

Click Install Now

If using MSDN or other non-trial based install enter a product key.

Select (Server with GUI)

I accept the license terms

Select Custom: Install Windows only (advanced)

Click Next

Wait Patiently…

Create a password


Turn on automatic updates and install any updates that are required

Power down the server and add additional cores.

Power the server back on and log back in. You are now ready for Part III (Setting up your domain controller)

Best Practices: Building a home System Center Test Environment (Part I)

Part I (Choosing Hardware, Install Base Windows OS, Install Hyper-V)

I have always found that the vast majority of my learning comes from actually getting to do something.  In the world of IT and System Center this means I have to have my own personal test environment where I can experiment, iterate, and try out new ideas. Having a test/dev environments that your company provides for you is critical as well, but there is a need to be able to safely test within the comfort of your home network rather than testing out some crazy idea and then breaking the test environment which people other than yourself at your company depend on. Thus the need for a completely autonomous home or portable test environment.

The problem is that while there are tons of fantastic guides for how to install System Center Products, there are really no good guides (at least not that I am aware of) that take you through the entire process which at its most simplistic high level tends to look like:

Procure Hardware–Install Base Windows OS–Install Hyper-V–Create New Virtual Machine–Install Base Server OS–Configure VM as Domain Controller–Install SQL–Install System Center product of choice. (Basic)

Procure Hardware–Install Base Windows OS–Install Hyper-V–Create New Virtual Machine–Install Base Server OS–Configure VM as Domain Controller–Create New VM–Install SQL–Create New VM–Install System Center product of choice (Advanced)

There are of course ways around this like Hydration Kits which require some pointers to media, and a few inputs and will automate the process for you, but if you have never gone through the process from start to finish something is lost, and if a new version comes out it means you can’t build a test environment until someone else builds a hydration kit for you.

Once you make a basic standalone system center test environment you can then experiment with building a distributed one: Dedicated VM’s for DC, SQL, and various system center roles etc.

First thing you need is a computer/server with enough horsepower to handle running a few VM’s without breaking a sweat. You can skimp on test environment hardware, but you will pay in the form of slow performance. My theory with test environments is they should be fast–not necessarily blazingly fast, but preferably faster than whatever prod environment you work with. This may seem counter intuitive, but if I am going to productively use my test environment on a regular basis I need something that can rapidly spin up and spin down systems to simulate different scenarios. Also your production environment will be a lot larger than test, so to achieve fast speeds in a test environment you can use less robust hardware since your scale is much smaller. Keep in mind though,  if prod is signficantly faster, you will inevitably gravitate towards takings risks that you shouldn’t in prod (even with the best change management process in place). If test is faster, it will become your new home.

So you have to start with hardware. If you decide you want to use a laptop I recommend something that meets the following specs:

Processor: Quad-Core with Hyper-threading (You want at least 8 logical processors)

Memory: 16-32 GB Minimum (Yes this can be kind of expensive to do with a laptop since it often means 8 GB Chips. I recommend buying a base model laptop and then upgrading the RAM yourself via Newegg or it is much cheaper)

Disk: Minimum of two disks at least 1 disk should be an SSD. Depending on how ambitious you are feeling I recommend going with a laptop that has space for 2 SSD’s (again buy a base model and buy the drives yourself) then add a CD-ROM hard drive replacement to the mix and purchase a third SSD. I personally use multiple Mushkin Chronos Deluxe 240 GB SATA 6.0 Gb-s 2.5-Inch Solid State Drive (MKNSSDCR240GB-DX) though I have also heard good things about the Samsung Electronics 840 Pro Series 2.5-Inch 256 GB SATA 6GB/s Solid State Drive MZ-7PD256BW

This may sound like a pretty expensive combo, but it can be done quite affordably. One of my first test systems was an HP Pavilion dv7 notebook. It was quad core with 8 logical processors, I added 16 GB of RAM, and 3 SSD’s + cdrom harddrive adapter and was safely hovering under $1,500.

(The dv7 is a bit dated now, and HP has newer offerings, and you can certainly find other quality systems from manufactures like Lenovo which you can get the same functionality out of, though finding a Lenovo that can natively support two hard drives tends to only happen with their W series laptops which while fantastic machines tend to be a bit too pricy for once I start adding in SSDs from Newegg or Amazon.)

If you happen to have a server lying around, or if you are of the savvy EBay persuasion you may decide that you want more power than what your laptop is going to offer. Home servers are awesome, but they are also generally pretty noisy, less kind to your electrical bill, and more likely to cause those close to you in your life to look at you with mild trepidation as you slink down to the basement to tinker with the strange creature that sits next to the washing machine. (I am currently the proud owner of two home servers and am in the market for a third)

Base recommended server specs:

If you are going to have a server it is best to have one that at least has some basic specs to support heavier workloads, otherwise you might as well just get a laptop and pimp it out. If you are going with a home server, I cannot stress enough to buy used from reputable sellers. Buying new servers is prohibitively expensive, and while completely advisable for your business, it makes no sense for a home test lab.  Here are the base specs of one of home servers:

Processor:  2 Quad-core processors with hyper-threading support (This means 8 cores = 16 logical processors)