How do I make an installer interactive that is deployed from self service?

I guess you can download the package to the machine, then run the script "open filename" and add the whole top one as a self-service package

@dlprentice Can you explain what the need is here? Why do you want to make the installer interactive when run from Self Service? I'm not saying it's impossible to do this, but I'm curious why you'd need that to happen?

@mm2270 I want users to select what they'd like fixed when running this app https://office-reset.com/

You could use a script to curl the package (https://office-reset.com/download/Microsoft_Office_Reset_1.4.pkg) and then open it.

Edit: This would get you started...

#!/bin/bash

# Variables
downloadUrl="https://office-reset.com/download"
pkgName="Microsoft_Office_Reset_1.4.pkg"

# Get current user
loggedInUser=$( scutil <<< "show State:/Users/ConsoleUser" | awk '/Name :/ && ! /loginwindow/ { print $3 }' )

if [[ -n ${loggedInUser} ]]; then
  echo "Downloading and opening pkg as ${loggedInUser}"

  tmpDir=$(su -l ${loggedInUser} -c "mktemp -d")
  echo "Temp dir set to ${tmpDir}"

  # Download package to tmpDir
  su -l ${loggedInUser} -c "curl -Ss ${downloadUrl}/${pkgName} -o ${tmpDir}/${pkgName}"

  # Check for successful download
  if [[ ! -f "${tmpDir}/${pkgName}" ]]; then
    echo "Download unsuccessful"
    exit 1
  fi

  su -l ${loggedInUser} -c "open ${tmpDir}/${pkgName}"
fi

You can also use a tool like Suspicious Package or Pacifist to extract the scripts from the Office Reset pkg and just rehost them on your distribution point so users can just run them straight from Self Service.

@wmehilos Thats an great way to approach it! i see the developer points out that you are free to use Suspicious Package or Pacifist to look at the scripts. You can then, if needed, just copy paste the scripts you do need, and enable each of them in self service as an policy.

Thanks everyone for your responses I'm in good shape now!