FYI - VMs, VHDs, and SIDs

This is just an informational post, if it has been covered before, please disregard.

I use Hyper-V and virtual machines (Windows Server 2008 R2 Enterprise and Windows 7 Enterprise) for doing labs. I created a base install VHD of w2k8r2 and a base install VHD of Win 7 Enterprise. When I need new VMs for a lab, I simply copy the base VHD to each of a couple of folders and create the VMs from those copies of the base VHD.

For example, suppose I need a Dvsrv1 VM and a Boston VM. I create a Dcsrv1 folder and a Boston folder, copy base_w2k8r2ent.vhd to each of those folders, rename w2k8r2ent.vhd to dcsrv1.vhd in the dcsrv1 folders and rename w2k8r2ent.vhd to boston.vhd in the Boston folder, and create a Dcsrv1 VM using dcsrv1.vhd and a Boston VM using boston.vhd.

Here's where it gets interesting. In one of the labs in 70-642, I was supposed to add a domain security group (domain admins maybe?) to a local security group on a member server. It wouldn't let me do it! It gave me a hex error. So I looked it up on TITProsPFN (The IT Professionals Psychic Friends Network (Google)) and found out it was caused by duplicate SIDs. So I went back and sysprepped my base VHD files and had it shut them down instead of reboot. Now when i copy the base VHD files and create VMs, mini setup is run on first boot and new SIDs are generated! Then I change the computer name and reboot. No more duplicate SID issues.

As a side note, I keep a VM for each of my base VHD files that points to the sysprepped VHD. Once every week or two, I fire up the VM, let mini setup run, download and install Windows Updates, reboot TWICE, then run sysprep again. That way my VHD files stay patched. I believe you can do all the above with System Center Virtual Machine Manager including base VHDs, patching, rapaid provisioning of VMs, etc. but I haven't gotten around to playing around with it yet.

If none of this makes sense to you, as Roseanne Roseannadanna would say..."Never Mind"

Find more posts tagged with

Comments

pzero

Just keep in mind that you wont be able to sysprep again after 3 times.

Jander1023

I have a similar setup, running R2 in a dual boot config with my Win7 machine. I installed the R2 machine in a VHD. I run Hyper-V on that machine and run virtual R2 servers from there. This way, I get experience with Hyper-V and can do my labs. I was using other virtual software previously but I feel it is important to get more hands-on experience with Hyper-V.

However, I install each virtual client from scratch. It doesn't take that long and it's good practice. I don't connect them to the internet, so I don't even bother with updates; except for my primary R2 server running the Hyper-V.

Ultimately, I probably spend a little bit of extra time doing it this way but I have gained a lot of valuable experience. I'm starting to get more comfortable in R2 than I am with Win7! I can promote a server to a DC, add DNS or DHCP and many other server tasks easily and without needing to check the book for instructions.

MentholMoose

I use sysprep'ed base images for my labs. It is good practice to create them since in the real world you don't usually install every machine from scratch. Even when I create a new base image I automate it as much as possible (again, like in the real world).

It is also very convenient, on my faster lab machines I can have a fresh desktop or server up and running in two minutes, so I can test things really quickly and easily. If you are using linked clones it will save some disk space (I care about this a lot since I use SSDs, and even a few GB here and there helps).

Jander1023

MentholMoose wrote: »

I use sysprep'ed base images for my labs. It is good practice to create them since in the real world you don't usually install every machine from scratch. Even when I create a new base image I automate it as much as possible (again, like in the real world).

It is also very convenient, on my faster lab machines I can have a fresh desktop or server up and running in two minutes, so I can test things really quickly and easily. If you are using linked clones it will save some disk space (I care about this a lot since I use SSDs, and even a few GB here and there helps).

I'm not making any suggestions about how things are done "in the real world". Not all of us have years of work experience in the real world as Server Admins. I find it important to walk before I run, so I spend plenty of time doing things "from scratch" or manually.

LAN_Guru

Jander1023 wrote: »

I'm not making any suggestions about how things are done "in the real world". Not all of us have years of work experience in the real world as Server Admins. I find it important to walk before I run, so I spend plenty of time doing things "from scratch" or manually.

It doesn't matter how I do it or how you do it. What matters is whether or not how you are doing it works for you. You keep doing what works for you until it stops working then find another way of doing it. After installing from bare-metal a few times you'll get tired of doing it that way and will find a better way. Deploying WDS is really easy and then you can install unattended. Or you can download Virtual Server 2005 R2 for free and use VMs. I happen to have a real server and a legit 2008 R2 Enterprise license for my lab.

I admire anyone that takes the time to prepare enough for these exams to pass or better. A couple of years after I got into IT I was discussing certifications with a guy who had been in the business 5 years and did a lot of Netware consulting. He said certfications don't mean squat. We're both still in the industry, he still has 3 years more experience than me, but I have certs and he still doesn't. He has a degree and I don't. My billing rate is almost double what his is.

Certifications are important. I don't care what anyone says. Even if your test scores aren't the highest and even if you use brain ****...there is no way you can pass these exams without learning at least something while preparing for them. Anything you learn makes you a better support rep, admin, or engineer.

LAN_Guru

pzero wrote: »

Just keep in mind that you wont be able to sysprep again after 3 times.

Technically, you can sysprep unlimited times. You can only reset the activation clock 3 times though and sysprep resets the activation clock.

You could sysprep a VHD once every 30 days and get 90 days out of it before you have to activate.

I use sysprep to limit the number of bare-metal installs I have to do, not to skirt licensing requirements. I am a MS partner and have an Action Pack and Technet subscription so I have multiple legit licenses of almost every MS product for internal, lab, and demonstration use.

MentholMoose

Jander1023 wrote: »

I'm not making any suggestions about how things are done "in the real world". Not all of us have years of work experience in the real world as Server Admins. I find it important to walk before I run, so I spend plenty of time doing things "from scratch" or manually.

I'm definitely not suggesting you never install Windows from scratch. It is good fundamental knowledge, and you need to be familiar with the installation process since it is covered on some exams. However, once you are comfortable with it, move on to the "advanced" deployment tools (e.g. sysprep). There are exams (e.g. 70-680 and 686) that cover these tools as well.

I try to make my labs similar to an enterprise network that I would want to work on. I have actually seen companies "in the real world" that don't use sysprep or imaging, and do fully manual installations for every new PC. However, that is typically inefficient and I would not want to work in such an environment unless I had the power to change things.

LAN_Guru

MentholMoose wrote: »

I'm definitely not suggesting you never install Windows from scratch. It is good fundamental knowledge, and you need to be familiar with the installation process since it is covered on some exams. However, once you are comfortable with it, move on to the "advanced" deployment tools (e.g. sysprep). There are exams (e.g. 70-680 and 686) that cover these tools as well.

I try to make my labs similar to an enterprise network that I would want to work on. I have actually seen companies "in the real world" that don't use sysprep or imaging, and do fully manual installations for every new PC. However, that is typically inefficient and I would not want to work in such an environment unless I had the power to change things.

Well stated.