Scripting Question

How to deploy application remotely

05/14/2018 1579 views
I'm trying to deploy an application/MSI file remotely on a thin client using the HPDM 4.7
So far i was able to deploy the patches by using the below

Sample used for Patch

wusa.exe Z:\Temp\Windows6.1-KB2803821-v2-x86.msu /quiet /norestart

if %ERRORLEVEL% equ 3010 ( exit 0 ) else ( exit %ERRORLEVEL% )

The patch was successful and worked seamlessly. However when i tried the same for an .exe or .msi im getting error . The file is getting saved/deployed on the thin client but the Installer i created is not able to execute.
I have tried different permutation and combination but not working.

Thin Client used - T620
OS - WES7P 64 Bit

Thanks in advance.
2 Comments   [ + ] Show comments


  • well, WUSA ist only for installing a Patch, not for exe or msi.
    If you have the files already on the remote system you could use wmi (built in) or psexec (you need to download it from Microsoft)
    But this is one example where you would never ever miss a KACE SMA anymore if you used it once.
    • Hi Nico ,
      i tried with the msiexec . So what is did is , i had the executable file deployed on the remote desktop and a script which will run that executable . The script tried
      msiexec \i "Path/Application/msi" /quiet /norestart
      When i tried locally without any remote activity , im getting an error.
  • "an error"

    Have you got any *less* information? There's too much here to go through.

Be the first to answer this question

Don't be a Stranger!

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

Sign up! or login

View more:


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