How To Deploy MED-V with Existing Management Systems?

MED-V Workspace Packager lets you package your XP VM for use as a MED-V workspace. The documentation included with the Workspace Packager will guide you through the process of:Preparing your XP imageCreating a MED-V Workspace package for deploymentTesting and deploying your MED-V workspaceManaging app and software updates within MED-V andManaging MED-V settings after deploymentOften, you'll […]

MED-V Workspace Packager lets you package your XP VM for use as a MED-V workspace. The documentation included with the Workspace Packager will guide you through the process of:

  • Preparing your XP image
  • Creating a MED-V Workspace package for deployment
  • Testing and deploying your MED-V workspace
  • Managing app and software updates within MED-V and
  • Managing MED-V settings after deployment

Often, you'll deploy a management agent such as SCCM client inside of your MED-V workspace to allow for app distribution and update along with patch management. The SCCM team has provided a client hotfix, to be installed on your SCCM SP2 Site Server, which improves SCCM functionality when you've configured your MED-V workspace to use network address translation (NAT). The hotfix allows a MED-V workspace that's also an SCCM client to use the same SCCM site and distribution point assignment as its host.

Once you've created your MED-V workspace package you'll have a MED-V Workspace Package -- a standard app file set that's ready to deploy. You'll find:

  • A setup.exe
  • A .medv file that is a compressed copy of your workspace VHD file and
  • An .msi installer

You can create installation tasks within your software deployment tool to install MED-V and its prerequisites together, or you can create separate tasks that deploy the individual components. If you are using SCCM, you can create packages and a Task Sequence to install the MED-V and WVPC components.

In this sample batch script for MED-V component installation, the MED-V components are installed in inverted order, allowing the installation to complete with a single reboot. There are two things to keep in mind about this batch script. First, while the MED-V Client installer and MED-V workspace package installer will detect if they are running on an x86 or x64 system and will install the appropriate "bitness", the WVPC update and associated hotfix are specific to x86 or x64 systems. 2nd, the MED-V installation willn't be complete until the system is restarted.

REM install the MEDV Host Agent
start /WAIT msiexec /i MED-V_HostAgent_Setup.exe /qn IGNORE_PREREQUISITES=1
REM install the MED-V workspace package
start /WAIT .\setup.exe /qn OVERWRITEVHD=1
REM Install WVPC(this example is for WVPCx64)
start /WAIT Windows6.1-KB958559-x64.msu /norestart /quiet
REM Install WVPC update (this example is for the x64 version of the update)
Windows6.1-KB977206-x64.msu /norestart /quiet

Here're command line examples for creating packages within SCCM:

  • MED-V Host Agent
  • msiexec /i MED-V_HostAgent_Setup.exe /qn IGNORE_PREREQUISITES=1
  • MED-V workspace package
  • setup.exe /qn
  • WVPC installation (Note: This example shows the x64 version of WVPC. If installing within a Task Sequence, use "Run Command Line" instead of "Install Software" to avoid a reboot at this step.)
  • wusa.exe Windows6.1-KB958559-x64.msu /norestart /quiet
  • WVPC update (Note: This example shows the x64 version of the update. If installing within a Task Sequence, use "Run Command Line" instead of "Install Software" to avoid a reboot at this step.)
  • wusa.exe Windows6.1-KB977206-x64.msu /norestart /quiet

Once MED-V 2.0 and WVPC have been deployed, and any necessary reboot completed, MED-V First Time Setup runs and legacy applications published from MED-V are available in the Win7 Start menu. Legacy web based apps or sites defined by the MED-V admin are seamlessly redirected to IE6 or 7.

[tags]wvpc,win7,nat,ie6,ie7,internet explore 7,internet explorer 6[/tags]

[Source]