Deployment Package / Easy way to run a .exe file from an UNC path with parameters?

[alphanimal]

Hi!

Is there an easy way to run an executable to be executed from a Deployment Package Step?

Say we want to run '\\server\path\to\bananainstaller.exe /uninstall /showui /removedata' - we enter the path to the exe and the parameters using the "Command" mode

When we try with the "Command" mode, it executes something like 'C:\Windows\system32\cmd.exe /c "\\server\path\to\bananainstaller.exe /uninstall /showui /removedata"'

the problem is, cmd.exe doesn't know about UNC paths.

Is there a way to execute the exe directly without using cmd?

Thanks!

Daniel

[alphanimal]

The permissions to the share are OK.

We tried with the Installer mode as well but that also didn't work.
We'll investigate some more...

Thanks!

[Daniel_B · Accepted solution]

The UNC path should not be the issue if the target server name can be resolved from the computer on which the package gets deployed, but rather the access to this path. You need to ensure that this package gets deployed under scanning credentials which need to have access to this path. Alternatively the currently logged on user might be working, if you are sure that all users which receive this package have access to the installer path.

Generally we recommend providing a package share and configure this under Deployment\Security options. You can always refer to the package share location with the place holder {PackageShare} in your deployment packages, and you can define separate credentials to access the package share.

BTW, you can use the installer step for this as well. The UNC path to the installer EXE will be the Install File and the parameters will be entered in the Parameters field.