Solution 1: Native EXE
This uses VMware's original DL'd EXE but there is a catch:
It installs the VIX requisite AFTER this EXE is log exited.
That could cause issues depending what you are doing after this line is executed (e.g. install another MSI, forced reboot...).
Notice the escaped double quotes (\") for the /V parameter
It's a InstallShield Setup.exe parameter.
To figure out the %~DP0 part, see
http://ss64.com/ntsyntax/parameters.html
The TRANSFORMS property is just there for demonstration purposes. This will work, too.:
"%~DP0VMware-PowerCLI-5.0.0-435426.exe" /q /s /w /V"/qn /l*v \"%TEMP%\Install\VMware_Power_CLI_V500.LOG\" "
#############################
Solution 2: Base MSI
The MSIs are obtained via the %TEMP% folder trick. (see my notes in the VMware vSphere client 5.0)
Install VIX first and the VMware vSphere PowerCLI.msi will *NOT* spawn a stealth MSI install for VIX afterwards.
Questions & Answers related to VMware, Inc. VMware Power CLI
Blogs (0)
Blog posts related to VMware, Inc. VMware Power CLI
Links (0)
Links related to VMware, Inc. VMware Power CLI
Reviews (0)
Reviews related to VMware, Inc. VMware Power CLI
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