Summer Wrap-Up – #VirtualDesignMaster, #HyperV, and more

With summer coming to a close, there’s an unavoidable temptation to look book on what was. This year has been pretty busy, so I thought I’d take some time to look back on my accomplishments.

In February, I started this blog. I set out with a goal of one article per week on the blog. In the last seven months, I’ve met that average for the week even if I don’t write another article (52 articles in 29 weeks), but I also learned that it’s not feasible for me to actually write one article every week. I wrote three series, on PowerCLI, Auto Deploy, and Puppet for the vSphere Admin (ongoing) and managed over 14,000 page views in ~7 months. I have been lucky enough to convince Jason Crichton (@hawkbox) to contribute articles on Hyper-V while I took a summer break, and there’s really no point in trying to advertise new content during VMworld next week. I count the blog as a success and I learned some lessons along the way.

Speaking of which, I am unable to attend VMworld this year. Last year was my first VMworld and I sorely miss the opportunity to go back and to meet all my tweeps. I’ll be watching online, however!

In the area of personal growth, I acquired my VCP5-DCV certification in April and became a vExpert in July. Both were exciting, the certification because it validated my technical knowledge and the vExpert because it validated my community activities. The fact that both came with some free licenses didn’t hurt, either. I plan to put those to good use in the coming months to continue my education! I’m looking forward to being part of these two communities and learning from the other members.

In July, Season 2 of Virtual Design Master (VDM) began. I was one of 11 contestants. I survived round 1 and round 2, but I had to fold on round 3 of 4 due to time commitments. Congratulations to Timothy Patterson (@PcProfessionals) for winning Season 2! I learned a LOT during this competition – taking all the skills I use on a day to day basis as a vSphere admin, what I studied for my VCP, and a number of vSphere design books and applying it to design and engineering, which is not part of my day job in operations. I haven’t done any actual design work in years, and then it was always on a much smaller scale. VDM was challenging, exciting, and scarey. It was also very rewarding. In addition to the technical growth, there was a great sense of community and co-opetition between the contestants and the viewers of the competition. Check out #VirtualDesignMaster on Twitter for some great discussions. There’s some good content about IPv6 and Openstack in particular.

As I mentioned above, I was able to convince Jason to become a contributing editor on my blog. He is in the middle of his own Hyper-V series, which now has its own page. As a vSphere admin myself, I find the content very helpful – the world isn’t all VMware – and I hope that others find it useful as well. We would both love to hear any comments you have on the series and what direction it should go in.

In addition to all of the above, my wife changed jobs in August and we moved from Richmond, VA to Indianapolis, IN. We’re really excited about the new job and home, but we’re both very exhausted, too. If you’re in the Indianapolis area and I didn’t meet you at the IndyVMUG, drop me a line.

Have a great summer, and enjoy VMworld if you are attending!

Installing SCVMM for Hyper-V

Welcome Back! For this article I am going to try and cover SCVMM (System Center Virtual Machine Manager) well enough to allow you to install it for testing purposes. This isn’t intended to cover all of the details as I think there is too much material here for one post and I haven’t had time with my new job to properly explore deeply yet. If I have missed something important or you would like me to go into more detail on a part of this, please send me a message and I will be happy to look into it.

SCVMM is the functional Hyper-V equivalent to vCenter in a vSphere environment. I have rather extensive experience dealing with vCenter, so I wanted to try and familiarize myself with SCVMM in the same way. With System Center 2012 and 2012 R2 it comes as part of the entire package, which is rather handy. I am going to go through step by step and show my experience with it. I will make note of any caveats or landmines I come across during the setup.

Probably the number one thing to consider before getting started is your SQL environment, where are you going to host your SQL DB? I am in the process of familiarizing myself with SQL 2012 right now so I have chosen to deploy this on another server. You are also able to use a local SQL Express install should you only want to run this in testing. I  would recommend a dedicated server if you plan to run this in production.

For the purposes of this article I deployed a new 2012R2 server from my Hyper-V environment using the MDT (Microsoft Deployment Toolkit) which I will further explain and cover in another article. I want to cover this separately as it’s an extremely useful tool whether you are using Hyper-V or vSphere. Using this fresh install I started in much the same way a windows vCenter install would begin.

I downloaded the evaluation ISO and mounted it in the VM I created, from there I ran setup.exe to begin the process.
Choose the Install option, installing the server automatically adds the console.

Next option is product key, for now evaluation is fine. If you have one, feel free to enter it. I am doing this as a lab so there is no need for one right now.

Agree to terms, if you don’t you go no further.

Yes or no to CEIP, I really don’t have much of an opinion on this. Unless you’re doing something confidential it’s probably fine to agree to it.

Decide where you want to install to, I’m using defaults for this. If you have a different system feel free to make use of it.

Hmm looks like I’m missing something. Need to install the Windows 8.1 ADK for this.

Grab the ADK. This utility is used to enable automated deployments and it is quite critical. Download and install it.


Decide where you want to install it. I chose to install this computer.

CEIP again, do as you wish.

You will have a EULA come up, you know the deal.

Decide what you need from the ADK. Most likely, WinPE and Deployment Tools is all you really need. If you do not have a separate SQL server, check Microsoft SQL Server 2012 Express.

Let the install run, this can take a while.

Once you’re done you can go through the getting started guide or not. It isn’t relevant for my purposes so I am not bothering. Go back to your SCVMM install and check the prereqs again. For me I got a new warning.

I’m downloading the SQL 2012 command line in annoyance. I wish MS installers were like Veeam or Dells OME and allow you to just install the necessary files from the checker. It would make everyone’s life a lot simpler.

If you download through the download link you get the following information in a text file for whatever reason. So click on install instructions and find the command line feature pack in the list. This is the one you want.

Grab the x64 package assuming you are using the x64 version. Save and run it as necessary

If you have the luck I have you will get the following popup, because why tell me this first?

So now we need to install the native client. It’s also in that list of files to download. Conveniently it is directly above the command line utilities (As of May 2014 at least). Download and install it as well.




You really don’t need the SDK for this.

Simply click install and it will proceed to install the native client.

Once you’ve finished this install now install the command line utilities using the same steps as the native client install. Now we check our Prereqs again. Mine shows a pending restart but yours may not.
So I’m restarting. No big deal, simply wait for it to come back up and run the installer one more time.

Post restart we return to the prereq check and see how we’re doing. Basically for this stage just clear up anything outstanding before you proceed. In my case, the second time through no prereqs failed and it moves on to the DB configuration. If you installed the SQL Express version just point to localhost, otherwise point to your SQL DB’s hostname. In production use some properly configured credentials, for this I am using my regular lab Domain Admin account.


Next you need to configure the service account. NOTE!!!!! This cannot be changed afterward, if you change the account in services you will break this and need to reinstall. I have learned this the hard way. For this lab I am just using the local account. Additionally if you are running HA you need to store your encryption keys in AD, it’s fairly easy to do if you have an existing AD, click the blue link and follow the instructions.


Port information is auto populated and probably best to leave alone unless you have a specific reason to modify it.scvmm25

Next you create your library share. Put this in a location that will not cause you problems down the road. In production, that would not be the C drive.

Finally assuming everything has gone nicely you will get a page with a summary and an install button. At this point you’re committed so you better press that install button. Otherwise why are you reading this?
NOTE: Make sure the account you set to create the database has to appropriate permissions or it will fail and you’ll need to start all over.

Installing takes a while, this is normal and not a problem.

At this point I ran into some SQL problems with my first attempt, but I believe they were related to my poorly set up lab DNS structure. I plan to do a full install from scratch again to verify this when I have the time.

When you launch the client, if you get a popup about a folder access being denied go into explorer and follow the path till you get to the last folder, it should ask you to provide permission and afterwards that error shouldn’t come up any more.

SCVMM is now installed. Configuration of SCVMM is for another day, and another article. Hope you all have a great week!

Hyper-V memory oversubscription

Welcome back to my third article, I hope these provide some useful information. This posting is based around my observations of the differences in how vSphere and Hyper-V manage memory on the host. Without further rambling, let’s get started.

Hyper-V handles memory in a noticeably different way than vSphere does. This has taken me some getting used to but the largest take away is that it does not overcommit memory. Microsoft uses the term Dynamic Memory for their version, and based on my observations that is a good term for it.

Memory over allocation in vSphere is handled through the VMTools and the balloon driver in instances of the memory allocation actually being utilized. This historically, to my understanding, results in paging to disk when recovered memory isn’t adequate for the needs to be met. This is where Dynamic Memory kind of breaks my brain. Unlike vSphere, which more or less just assumes you will overcommit at some point, you need to explicitly enable this functionality. It’s not complicated, just not something you might think to do when coming from a VMware environment. Continue reading

Hyper-V Replication

Hello again, welcome back to the second of my indeterminate number of articles covering my various observations regarding differences around vSphere and Hyper-V. This post is covering host replication without a central controller. So hopefully you benefit from and enjoy this one.

As near as I can tell there is no direct analog in vSphere to compare this to.  As such I’m going to give as much of an explanation as I realistically can and show where I think this would be extremely beneficial.

Hyper-V replication does not require SCVMM or any kind of centrally managed vCenter equivalent, all it requires is two or more Hyper-V hosts that meet the necessary requirements for performing the replication. (CPU, Memory, Storage, etc….) Once that is met it is quite straight forward to do as a test. Continue reading

Basic Sudo Access

A few months back I noted that I’d be more concerned with security going forward. Among other things, this means using sudo for accounting and authorization. A mature system would configure this via Puppet or another CM tool. If you haven’t gotten there with your CM tool, or you are working on a standalone system, you can still enable basic sudo access with a few steps:

[root@puppet git]# useradd rnelson0 -c "Rob Nelson"
[root@puppet git]# passwd rnelson0
Changing password for user rnelson0.
New password:
Retype new password:
passwd: all authentication tokens updated successfully.

[root@puppet ~]# cat > /etc/sudoers.d/sudoadmins
rnelson0        ALL=(ALL)       ALL
  1. Add a local user.
  2. Set a password for the local user.
  3. Allow the user to use sudo for all commands.

This is a good start for a lab. In production, more granular sudo permissions should be used, in addition to a central user management system, like LDAP or ADS. And if you have to do this in more than one place, automation is a good idea.

Hyper-V for the vSphere Admin

Welcome to my inaugural post on, I’m happy to be here and hope that I can provide some useful insight. Recently, I received a voucher for the Microsoft Hyper-V certification exam and decided to take that opportunity to really give it a proper test. With that in mind, Rob convinced me to write some articles on interesting or difficult concepts I come across in the hope that I can help people down the road avoid the same technical landmines. I’m a vSphere admin by experience, so I’ll be comparing Hyper-V components to their vSphere equivalents to help root this in familiar terms. Today, I’ll describe what Hyper-V is, the lab I’m running it in, and some pre-reqs to installing it. Follow up articles with provide greater detail (and pictures!) and cover installation and use.

Hyper-V is Microsoft’s virtualization product in their server line. In my opinion, starting with Hyper-V in Server 2012, it’s becoming competitive with vSphere for the small to medium scale environments in which I’ve worked. Veeam has a great article explaining the concept of Hyper-V. Veeam is a terrific backup product for virtual environments and it supports both Hyper-V and vSphere. If you are an MCSA/MCSE or VCP, you should look into their NFR (Not for resale) licenses to run in your home lab. Continue reading

Introducing Jason Crichton, aka @hawkbox

With summer upon us, I’ve taken a break from the blog. You’ll still see a few of my small posts pop out every so often, but no lengthy technical posts from me for a while. That doesn’t mean the blog is taking the summer off, though!

I’m proud to introduce a colleague and fellow Arsian, Jason Crichton, as a contributing author on my blog! Jason is going to write some articles over the summer about Hyper-V. For those of us (myself included!) who are only familiar with vSphere, Jason will help us compare the analogous features from each product with articles most Wednesdays this summer. Here’s a little background those of you who have not met Jason before:

My name is Jason Crichton, I’m an IT professional like Rob, just crossing over the 10 year mark of System Administration this summer. I started in the trenches of help desk and through a bit of luck and a lot of hard work now work as a Senior Systems Analyst for a relatively small multinational corporation. I tend to end up heavily involved in the virtualization, security, and operations aspects of the business. Recently I have moved into Powershell tool development for improving the lives of our help desk staff. I find the willingness of people like Rob to put the time and energy into sites like this incredibly valuable, so when he asked me to contribute I was thrilled at the opportunity to give back myself.
When I’m not working with tech, I tend to be motorbiking with my wife Christina on whatever random trip we’ve been able to organize.
My professional experience can be viewed on LinkedIn. Additionally you can follow me on twitter through @hawkbox.
Please give Jason a warm welcome to the blogosphere! If you have any requests for Hyper-V topics, please let myself or Jason know what you’d like to see covered. Thanks!