/build/static/layout/Breadcrumb_cap_w.png

Software Deployment Question


VMware Horizon View Client x86 & x64 3.2.0 Deployment / Distribution via Kace

03/11/2015 4084 views

I would like to know how to deploy VMware Horizon View via Kace software via Kace.  There is a 32 bit and 64 bit client available on VMware's website here:  https://my.vmware.com/web/vmware/info/slug/desktop_end_user_computing/vmware_horizon_clients/3_0   However, Kace identifies the 64 bit install and the x86 32 bit install as the same software line item in Kace.  The problem is that you need separate exe install files for both types of OSs but can only associate one file with that particular software item.  Then, how can you set up separate distributions for the x86 and x64 install when you can only point it to one software package with one install file? 

 

Custom software inventory rule doesn't work.  Why not?? 

RegistryValueEquals(HKLM64\SOFTWARE\Wow6432Node\VMware, Inc.\VMware VDM\Client,BuildNumber,2331566)

4 Comments   [ + ] Show comments

Comments

  • I have added a custom inventory rule for VMware Horizon view but it still fails to detect it. I can detect a file but that isn't suitable - it needs to detect the exact version or registry key. Here is an example of the reg key which is not successful. What am I doing wrong?

    RegistryValueEquals(HKLM64\SOFTWARE\Wow6432Node\VMware, Inc.\VMware VDM\Client,BuildNumber,2331566)
  • I bet I know what it is - VMware, Inc. has a comma and it's messing up the path!!! How do I get it to ignore the comma in the reg key path?
  • Did you ever find a solution?
  • This content is currently hidden from public view.
    Reason: Removed by member request For more information, visit our FAQ's.
  • This is quite old; we are now deploying the x64 version as all endpoints are 64 bit. The switches for VMware Horizon View version 4.10 that we're using are: /S /V"/qn VDM_S/S /V"/qn DESKTOP_SHORTCUT=1 VDM_SERVER=view.myserver.com REBOOT=Reallysuppress"ERVER=view.myserver.com REBOOT=Reallysuppress" /norestart

    We target this by label groups of machines.

All Answers

0
You will have to use a custom software inventory item as well as a custom inventory rule.  Look up the MI install for Office 2013 here or on kace.com and it will give an example of this.
Answered 03/12/2015 by: jknox
Red Belt

  • This content is currently hidden from public view.
    Reason: Removed by member request For more information, visit our FAQ's.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ