This installation requires Windows 2000?!?!?!? Do What? Error when deploying MED-V Deployment Package . . . aka – did I just Travel back in Time?

Note. We are speaking of MED-V V1 here. 😉

 

So, here is the scenario: You are creating a deployment package using the MED-V Deployment Packing Wizard. This is available in the MED-V v1 console. More information about this is found here:

 

http://blogs.technet.com/b/medv/archive/2009/07/27/creating-a-med-v-deployment-package.aspx

 

The MED-V Deployment Package Wizard allows you to bind all of the binaries required for deploying a MED-V client along with a prestaged image into a single package. During the wizard, you have the option to specify the installers to include in the package. The trouble is, it does not verify that the installer you are choosing is the right one. For example, when you are specifying the MED-V installation file under “MED-V installation settings” it does not verify that that is, in fact, the client installer.

 

I recently encountered an issue where a customer was attempting to deploy the MED-V client to a Windows 7 host using the MED-V 1.0 SP1 Deployment Package methodology. It failed with the following error:

 

This installation requires Windows 2000 SP4 or Windows XP SP2/SP3

Needless to say, getting this error on a Windows 7 computer was confusing. Luckily, the customer did not attmept to cretae a Versionlie AppCompat shim as this could have yielded even more trouble.

This was simply caused by the wrong MSI being selected during the packaging wizard. When you select the option to run the MED-V packaging wizard (From the Management Console – select Tools – Packaging Wizard.”In the MED-V Installation Settings, dialog box, the installation binary selected should be MED-V_1.0.105.MSI.

In this particular scenario where the above error occurred, the MED-V_Workspace_1.0.105.MSI was selected and used instead of the client installer (MED-V_1.0.105.MSI.) The MED-V_Workspace_1.0.105.MSI is only one used to install the workspace guest binaries inside the virtual machine.