The WinOps Blog

Installation Files to be deployed

Depending on your environment the number of files could vary, for instance, if you have Windows Virtual PC already enabled as a part of your standard image, you won’t need to deploy it, so let’s assume you have a clean environment with nothing but Windows 7 deployed, you need the following:

Windows Virtual PC: KB958559

Non-HAV clients patch: KB977206 (already in Windows 7 SP1)

MED-V Client: MED-V_HostAgent_setup.exeSetup.exe: the workspace itself

That’s about it, if you’re deploying Windows 7 you should consider a task sequencer to get them installed, remember Windows Virtual PC requires the clients to reboot, but that’s ok Task Sequencers in Configuration Manager run perfectly fine after a reboot.

MED-V Installation

Method 1: Using a Package and multiple Programs

The good thing about this method is that each component is installed individually, with its own advertisement, that gives you great flexibility and makes it easy for you to troubleshoot each component; the bad thing about it, well, it’s long!

Let’s examine the files produced by the MED-V Packager:

a .REG Configuration File

a Workspace VHD (compress that, it can save up to 50% of space)

a .EXE Workspace Package Installer

a .MSI File

a PowerShell Script (should you need to repeat your steps!)

that being said, here’s the plan, we’re going to create an SCCM Package that contains the installation source files, then we’ll create a program for each file we need, so let’s begin!

Step 1: Create a new Package

I prefer you create a new folder under Software Distribution, and then create a new Package, the package location should be the path to your custom made folder with all the executable files we need, it doesn’t have to be a UNC since SCCM will copy the contents to an accessible Distribution Point.

Step 2: Create a Program for WPC

As you can see above, the command “Windows6.1-KB958559-X64.msu /quiet” note the (X64) at the end of file name? you guessed it, if you have Windows 7 is 32-bit then you should get the x86 bits, the /quiet switch will take care of the WPC installation quietly, you can specify /noreboot switch if you wish not to reboot your client machine, moreover, you really need to make sure SCCM Deploys WPC whether or not the user is logged on in the next page, here is what you should do in the environment page:

You can do this for every Program we’re going to deploy.

Step 3: Create a Program for the WPC Patch

We’re going to use the same command to get it installed, and again using the /noreboot switch will disable rebooting the client.

Step 4: Create a Program for the MED-V Host Agent

Alright, the command here is similar to what we used above but this time the parameters differ a little bit, “ MED-V_HostAgent_setup.exe /qn IGNOREPREREQUISITES=1” will cause the host agent installation to ignore any prerequisites, for example not having WPC installed.

Step 5: Create a Program for the Workspace

As you can see below the command “setup.exe /qn OVERWRITEVHD=1” will make SCCM install the Workspace even if there any previous Workspaces present at the client.

Step 6: Create an Advertisement for each Program

Now that the Package and all of its Programs have been created, you should create an advertisement for each program, I know, it’s a lengthy process, but with multiple advertisements you can control the deployment level at each client and track every single component being deployed through reporting and Advertisement Status.

Here’s how the advertisement should look like

Now, in the Schedule page, you either run it “As Soon As Possible” causing the clients to pull it right next to its upcoming policy refresh cycle, or schedule to run during off-business hours.

Method 2: Using a Task Sequence

Deploying the components in a Task Sequence allows for fine-grained control, and it also allows you to use one advertisement to send Windows Virtual PC components to clients of differing bitness. Here’s one example of an SCCM Task Sequence to deploy MED-V. Note that it’s okay to install the non-HAV patch to systems that are HAV capable. If a system is capable of HAV and HAV is properly configured, Windows Virtual PC will use HAV features even though the non-HAV patch is installed. Deploying the non-HAV patch universally will allow administrators to ensure that Windows Virtual PC will function properly on all systems. Again, the non-HAV patch is not needed on systems that are running Windows 7 Service Pack 1.

The query at the top of the branch to select x64 systems is from WMI Namespace root/cimv2 and the WQL is “select * from Win32_Computer_System where SystemType = “x64-based PC”

For X86, the WQL is “select * from Win32_Computer_System where SystemType = “x86-based PC”

Method 3: Using a batch file

Here is a sample batch file that installs the MED-V components in reverse order with prerequisite checks turned off. Turning the prerequisite checks off lets you deploy the components with one reboot:

#REM Batch Starts

#REM Installing Host Agent components

start /WAIT MED-V_HostAgent_Setup.exe /qn IGNORE_PREREQUISITES=1

#REM Installing Workspace

start /WAIT .\setup.exe /qn OVERWRITEVHD=1

#REM Installing Windows Virtual PC

start /WAIT Windows6.1-KB958559-x64.msu /norestart /quiet

#REM Installing the non-HAV Patch

start /WAIT Windows6.1-KB977206-x64.msu /norestart /quiet

#REM Optional: Restart the computer after 5 minutes.

Shutdown.exe -c “Please save your work, Windows will restart in 5 minutes” -r -t 300

#REM Batch File Ends

Source: http://ajweh.com/blog/?p=96