-
Type:
Incident report
-
Resolution: Unresolved
-
Priority:
Minor
-
None
-
Affects Version/s: None
-
Component/s: Documentation (D)
-
None
Try to use the example (with pre-shared key) when using PowerShell, not CMD. You will fail!
You will immediately see a help pop-up window instead of the command proper execution. Specified log will not be written.
Reason - PowerShell will cut double quotes and MSI engine will get improperly provided parameters, because of 2 spaces in path for INSTALLFOLDER or TLSPSKFILE etc.
Solution - escaping double quotes by back tick. Example explanation -
https://www.reddit.com/r/PowerShell/comments/15p6nmc/how_to_escape_spaces_in_powershell_while_using/
or this is even better https://stackoverflow.com/questions/44498335/command-line-arguments-for-msiexec-break-on-powershell-if-they-contain-space
So, as many admins nowadays by default are using PowerShell instead of CMD and we did not specify in our doc that the example is for CMD, to be more user friendly we should indicate this behavior in doc.