Home > MED-V, SCCM > MED-V 1.0: Windows Installer Service Retriggers MED-V Client installation When Trying to Start Workspace

MED-V 1.0: Windows Installer Service Retriggers MED-V Client installation When Trying to Start Workspace


A while back, I encountered an issue on the forums that evolved into an incident. I had an issue where the MED-V client host is retriggering installation (self-healing) when trying to start the client. The Windows Installer Service also retriggers the MED-V Client installation when trying to start a workspace or an application that is dependent on the workspace. Also, the MED-V shortcuts appear with the default icon instead of the correct icon.

Upon further investigation, I found that the installation was only installed for the user instead of the entire machine (the MED-V Client.) The MED-V Client was deployed silently using SCCM. The command line in the package to install the MSI did not have the ALLUSERS=1 flag properly set.

The resolution was to redeploy the client using the ALLUSERS=1 Flag. Due to the way the Windows Installer properties handle installations, this is the only remediation.

Refer to the following article:

http://blogs.technet.com/b/medv/archive/2010/02/16/prescriptive-guidance-for-deploying-the-med-v-client-via-an-electronic-software-distribution-method-such-as-sms-sccm.aspx

 

Categories: MED-V, SCCM Tags: , , , , ,
  1. No comments yet.
  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: