I made a install script for Adobe Reader DC to do a Silent install.

UPDATED VERSION 2 With auto detect if Invoke-WebRequest exists

Improvements are welcome!

Change the version if needed in the Source URL: http://ardownload.adobe.com/pub/adobe/reader/win/AcrobatDC/1502320053/AcroRdrDC1502320053_en_US.exe

# Silent install Adobe Reader DC
# https://get.adobe.com/nl/reader/enterprise/

# Path for the workdir
$workdir = "c:\installer\"

# Check if work directory exists if not create it

If (Test-Path -Path $workdir -PathType Container)
{ Write-Host "$workdir already exists" -ForegroundColor Red}
ELSE
{ New-Item -Path $workdir  -ItemType directory }

# Download the installer

$source = "http://ardownload.adobe.com/pub/adobe/reader/win/AcrobatDC/1502320053/AcroRdrDC1502320053_en_US.exe"
$destination = "$workdir\adobeDC.exe"
Invoke-WebRequest $source -OutFile $destination

# Start the installation

Start-Process -FilePath "$workdir\adobeDC.exe" -ArgumentList "/sPB /rs"

# Wait XX Seconds for the installation to finish

Start-Sleep -s 35

# Remove the installer

rm -Force $workdir\adobe*

For Windows 7 please change 

$source = "http://ardownload.adobe.com/pub/adobe/reader/win/AcrobatDC/1502320053/AcroRdrDC1502320053_en_US.exe"
$destination = "$workdir\adobeDC.exe"
Invoke-WebRequest $source -OutFile $destination

To

$WebClient = New-Object System.Net.WebClient
$WebClient.DownloadFile("http://ardownload.adobe.com/pub/adobe/reader/win/AcrobatDC/1502320053/AcroRdrDC1502320053_en_US.exe","$workdir\adobeDC.exe")

Since Powershell in Windows 7 does not support the Invoke-WebRequest

I had the same thing happen with the winrar script.  Nothing.

Well almost nothing.  I deleted the c:\installer directory.

I watched the directory get created again but never saw a file in it.

Did you get any output from the script?

@kavaaI'd also return an exit code of 1 or higher when there's a problem so Pulseway will mark the script execution as failed.

-Paul

23 minutes ago, Paul said:

Did you get any output from the script?

@kavaaI'd also return an exit code of 1 or higher when there's a problem so Pulseway will mark the script execution as failed.

-Paul

Any suggestions on how to integrate that?

Because its a silent installer and checking for errors with that... kind of tricky?

2 hours ago, ComputerConsulting said:

I had the same thing happen with the winrar script.  Nothing.

Well almost nothing.  I deleted the c:\installer directory.

I watched the directory get created again but never saw a file in it.

Added instruction for Windows 7 since it does not have the Invoke-WebRequest command in PowerShell

Version 2

This version will check if the Invoke-WebRequest Command exists or not. For legacy Systems like Windows 7 you than only have one Script and don't need to change things in Pulseway

# Silent install Adobe Reader DC
# https://get.adobe.com/nl/reader/enterprise/

# Path for the workdir
$workdir = "c:\installer\"

# Check if work directory exists if not create it

If (Test-Path -Path $workdir -PathType Container)
{ Write-Host "$workdir already exists" -ForegroundColor Red}
ELSE
{ New-Item -Path $workdir  -ItemType directory }

# Download the installer

$source = "http://ardownload.adobe.com/pub/adobe/reader/win/AcrobatDC/1502320053/AcroRdrDC1502320053_en_US.exe"
$destination = "$workdir\adobeDC.exe"

# Check if Invoke-Webrequest exists otherwise execute WebClient

if (Get-Command 'Invoke-Webrequest')
{
     Invoke-WebRequest $source -OutFile $destination
}
else
{
    $WebClient = New-Object System.Net.WebClient
    $webclient.DownloadFile($source, $destination)
}

# Start the installation

Start-Process -FilePath "$workdir\adobeDC.exe" -ArgumentList "/sPB /rs"

# Wait XX Seconds for the installation to finish

Start-Sleep -s 35

# Remove the installer

rm -Force $workdir\adobe*

 

22 hours ago, kavaa said:

Any suggestions on how to integrate that?

Because its a silent installer and checking for errors with that... kind of tricky?

Added instruction for Windows 7 since it does not have the Invoke-WebRequest command in PowerShell

You could test the exit code of the installer. If it's msi based then these are some known exit codes: http://www.msierrors.com/tag/msiexec-return-codes/

-Paul