VMware Infastrcture Client 2.5 commandline
Trying to run VMware Client from the commandline silently via the msi.
The source has come directly from their site and installs fine, except when run from the commandline the install fails.
Any suggestions on fixes.
Cheers
The source has come directly from their site and installs fine, except when run from the commandline the install fails.
Any suggestions on fixes.
Cheers
0 Comments
[ + ] Show comments
Answers (4)
Please log in to answer
Posted by:
anonymous_9363
15 years ago
In these situations, you would typically run both installs with a verbose log and compare the two logs. My guess would be that there is a Custom Action in the UI sequence which doesn't get run in silent install (obviously, since no UI is presented). I'd be surprised to find such a thing in a VMWare MSI, though: they're normally very thorough.
Posted by:
Conapps
15 years ago
I was installing the wrong exe from the source files provided:
VMware VI Client 2.5\vi - wrong exe
VMware VI Client 2.5\vpx - has the correct exe
Found this command line on the net that installs the Client:
start /wait %~dp0\VMware-viclient.exe /s /w /v"/qr WARNING_LEVEL=0 LICENSING=custom INSTALL_VICLIENT=\"\" REBOOT=SUPPRESS"
Cheers
VMware VI Client 2.5\vi - wrong exe
VMware VI Client 2.5\vpx - has the correct exe
Found this command line on the net that installs the Client:
start /wait %~dp0\VMware-viclient.exe /s /w /v"/qr WARNING_LEVEL=0 LICENSING=custom INSTALL_VICLIENT=\"\" REBOOT=SUPPRESS"
Cheers
Posted by:
anonymous_9363
15 years ago
The '/V' argument followed by those property/value pairs clearly indicates an MSI-based install so, if you wanted, you could still use the MSI which that EXE extracts.
Posted by:
jmcfadyen
15 years ago
its actually better practice to use the extracted msi unless you are also specifying a SOURCELIST property.
when using exe's that contain msi's they tend to extract to %temp% then install the MSI. The issue with this is the SOURCELIST gets set to %temp%. The last step during the installation is often to delete the MSI. This effectively breaks the installation for healing.
when using exe's that contain msi's they tend to extract to %temp% then install the MSI. The issue with this is the SOURCELIST gets set to %temp%. The last step during the installation is often to delete the MSI. This effectively breaks the installation for healing.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.