Interactive features not working for logged on user?

Have an MSI application that requires admin privileges to install.
However I need to prompt the user who is logged on to close their browser:
Show-InstallationWelcome -CloseApps 'chrome,' -AllowDefer -DeferTimes 3 -CheckDiskSpace -PersistPrompt

I’m using PDQ deploy to deploy which uses an admin service account.
Whether I run the exe or ps1 accordingly, the Show-InstallationWelcome never shows for the user who is logged on.
The Chrome browser simply just closes automatically and there are no prompts.

Is there a different way to approach this that is the recommended work around?
For example do I run the Show-InstallationWelcome part as the logged on user in one step, then proceed to another step that runs in an admin user context to carry out the installation?

You run it as interactive.

do you have your have your install script to hand so we can view it in its entirety ?

Yes this is it:

	This script performs the installation or uninstallation of an application(s).
	PowerShell App Deployment Toolkit - Provides a set of functions to perform common application deployment tasks on Windows. 
	Copyright (C) 2017 - Sean Lillis, Dan Cunningham, Muhammad Mashwani, Aman Motazedian.
	This program is free software: you can redistribute it and/or modify it under the terms of the GNU Lesser General Public License as published by the Free Software Foundation, either version 3 of the License, or any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. 
	You should have received a copy of the GNU Lesser General Public License along with this program. If not, see <>.
	The script is provided as a template to perform an install or uninstall of an application(s).
	The script either performs an "Install" deployment type or an "Uninstall" deployment type.
	The install deployment type is broken down into 3 main sections/phases: Pre-Install, Install, and Post-Install.
	The script dot-sources the AppDeployToolkitMain.ps1 script which contains the logic and functions required to install or uninstall an application.
.PARAMETER DeploymentType
	The type of deployment to perform. Default is: Install.
	Specifies whether the installation should be run in Interactive, Silent, or NonInteractive mode. Default is: Interactive. Options: Interactive = Shows dialogs, Silent = No dialogs, NonInteractive = Very silent, i.e. no blocking apps. NonInteractive mode is automatically set if it is detected that the process is not user interactive.
.PARAMETER AllowRebootPassThru
	Allows the 3010 return code (requires restart) to be passed back to the parent process (e.g. SCCM) if detected from an installation. If 3010 is passed back to SCCM, a reboot prompt will be triggered.
.PARAMETER TerminalServerMode
	Changes to "user install mode" and back to "user execute mode" for installing/uninstalling applications for Remote Destkop Session Hosts/Citrix servers.
.PARAMETER DisableLogging
	Disables logging to file for the script. Default is: $false.
    powershell.exe -Command "& { & '.\Deploy-Application.ps1' -DeployMode 'Silent'; Exit $LastExitCode }"
    powershell.exe -Command "& { & '.\Deploy-Application.ps1' -AllowRebootPassThru; Exit $LastExitCode }"
    powershell.exe -Command "& { & '.\Deploy-Application.ps1' -DeploymentType 'Uninstall'; Exit $LastExitCode }"
    Deploy-Application.exe -DeploymentType "Install" -DeployMode "Silent"
	Toolkit Exit Code Ranges:
	60000 - 68999: Reserved for built-in exit codes in Deploy-Application.ps1, Deploy-Application.exe, and AppDeployToolkitMain.ps1
	69000 - 69999: Recommended for user customized exit codes in Deploy-Application.ps1
	70000 - 79999: Recommended for user customized exit codes in AppDeployToolkitExtensions.ps1
Param (
	[string]$DeploymentType = 'Install',
	[string]$DeployMode = 'Interactive',
	[switch]$AllowRebootPassThru = $false,
	[switch]$TerminalServerMode = $false,
	[switch]$DisableLogging = $false

Try {
	## Set the script execution policy for this process
	Try { Set-ExecutionPolicy -ExecutionPolicy 'ByPass' -Scope 'Process' -Force -ErrorAction 'Stop' } Catch {}
	## Variables: Application
	[string]$appVendor = ''
	[string]$appName = ''
	[string]$appVersion = ''
	[string]$appArch = ''
	[string]$appLang = 'EN'
	[string]$appRevision = '01'
	[string]$appScriptVersion = '1.0.0'
	[string]$appScriptDate = '02/12/2017'
	[string]$appScriptAuthor = '<author name>'
	## Variables: Install Titles (Only set here to override defaults set by the toolkit)
	[string]$installName = ''
	[string]$installTitle = ''
	##* Do not modify section below
	#region DoNotModify
	## Variables: Exit Code
	[int32]$mainExitCode = 0
	## Variables: Script
	[string]$deployAppScriptFriendlyName = 'Deploy Application'
	[version]$deployAppScriptVersion = [version]'3.7.0'
	[string]$deployAppScriptDate = '02/13/2018'
	[hashtable]$deployAppScriptParameters = $psBoundParameters
	## Variables: Environment
	If (Test-Path -LiteralPath 'variable:HostInvocation') { $InvocationInfo = $HostInvocation } Else { $InvocationInfo = $MyInvocation }
	[string]$scriptDirectory = Split-Path -Path $InvocationInfo.MyCommand.Definition -Parent
	## Dot source the required App Deploy Toolkit Functions
	Try {
		[string]$moduleAppDeployToolkitMain = "$scriptDirectory\AppDeployToolkit\AppDeployToolkitMain.ps1"
		If (-not (Test-Path -LiteralPath $moduleAppDeployToolkitMain -PathType 'Leaf')) { Throw "Module does not exist at the specified location [$moduleAppDeployToolkitMain]." }
		If ($DisableLogging) { . $moduleAppDeployToolkitMain -DisableLogging } Else { . $moduleAppDeployToolkitMain }
	Catch {
		If ($mainExitCode -eq 0){ [int32]$mainExitCode = 60008 }
		Write-Error -Message "Module [$moduleAppDeployToolkitMain] failed to load: `n$($_.Exception.Message)`n `n$($_.InvocationInfo.PositionMessage)" -ErrorAction 'Continue'
		## Exit the script, returning the exit code to SCCM
		If (Test-Path -LiteralPath 'variable:HostInvocation') { $script:ExitCode = $mainExitCode; Exit } Else { Exit $mainExitCode }
	##* Do not modify section above
	If ($deploymentType -ine 'Uninstall') {
		[string]$installPhase = 'Pre-Installation'

		## Show Welcome Message, close Internet Explorer if required, allow up to 3 deferrals, verify there is enough disk space to complete the install, and persist the prompt
		Show-InstallationWelcome -CloseApps 'chrome,Five9SoftphoneService,Five9SoftphoneSupervisor,Five9SoftphoneTray' -AllowDefer -DeferTimes 3 -CheckDiskSpace -PersistPrompt
		## Show Progress Message (with the default message)
		## <Perform Pre-Installation tasks here>
				Remove-MSIApplications -name 'Five9 SoftPhone Service'

		[string]$installPhase = 'Installation'
		## Handle Zero-Config MSI Installations
		If ($useDefaultMsi) {
			[hashtable]$ExecuteDefaultMSISplat =  @{ Action = 'Install'; Path = $defaultMsiFile }; If ($defaultMstFile) { $ExecuteDefaultMSISplat.Add('Transform', $defaultMstFile) }
			Execute-MSI @ExecuteDefaultMSISplat; If ($defaultMspFiles) { $defaultMspFiles | ForEach-Object { Execute-MSI -Action 'Patch' -Path $_ } }
		## <Perform Installation tasks here>
		Execute-MSI -Action 'Install' -Path 'Five9SoftphoneService_10.2.16.msi' -Parameters ' /qn /i SYSTEM_SPACE_MODE=1 /log c:\temp\Five9SoftphoneService_10.2.16.log'
		[string]$installPhase = 'Post-Installation'
		## <Perform Post-Installation tasks here>
		Show-DialogBox -Title 'Install Complete' -Text 'Installation has completed. It is recommended to reboot your computer manually at your earliest convenience.' -Icon 'Information'
		## Display a message at the end of the install
		If (-not $useDefaultMsi) { Show-InstallationPrompt -Message 'You can customize text to appear at the end of an install or remove it completely for unattended installations.' -ButtonRightText 'OK' -Icon Information -NoWait }
	ElseIf ($deploymentType -ieq 'Uninstall')
		[string]$installPhase = 'Pre-Uninstallation'
		## Show Welcome Message, close Internet Explorer with a 60 second countdown before automatically closing
		Show-InstallationWelcome -CloseApps 'iexplore' -CloseAppsCountdown 60
		## Show Progress Message (with the default message)
		## <Perform Pre-Uninstallation tasks here>
		[string]$installPhase = 'Uninstallation'
		## Handle Zero-Config MSI Uninstallations
		If ($useDefaultMsi) {
			[hashtable]$ExecuteDefaultMSISplat =  @{ Action = 'Uninstall'; Path = $defaultMsiFile }; If ($defaultMstFile) { $ExecuteDefaultMSISplat.Add('Transform', $defaultMstFile) }
			Execute-MSI @ExecuteDefaultMSISplat
		# <Perform Uninstallation tasks here>
		[string]$installPhase = 'Post-Uninstallation'
		## <Perform Post-Uninstallation tasks here>
	## Call the Exit-Script function to perform final cleanup operations
	Exit-Script -ExitCode $mainExitCode
Catch {
	[int32]$mainExitCode = 60001
	[string]$mainErrorMessage = "$(Resolve-Error)"
	Write-Log -Message $mainErrorMessage -Severity 3 -Source $deployAppScriptFriendlyName
	Show-DialogBox -Text $mainErrorMessage -Icon 'Stop'
	Exit-Script -ExitCode $mainExitCode

In SCCM , you have to enable deployment with ‘Allow User to Interact’ - is there something similar in PDQ?

I am having this same issue using Datto. My script executes O.K., but it simply closes the apps instead of presenting a dialog which would allow users to gracefully save/exit.

Interesting. I’ve found with SCCM CB you get the dialogues if the install is Available but you do not get them when the deployment is Required!

Note this is when it’s created as an Application. I’ve left whether or not a user is logged on as needs to be included in the build task sequence in the future.

SCCM has done it this way as long as I can remember. Required deployment at deadline will not run interactive. Required deployment executed from software center before deadline will run interactive.
You either need to use the newish option of deploy for system, weather or not a user is logged in, with allow user to interact (this is the new part and you need to be ok with the security warning) or have 2 deployments, the first with a custom condition Boolean that says a user is logged in, run as system, only when user is logged in, allow interact (checked default) and the second, run as system, weather or not a user is logged in, don’t allow user to interact.

I don’t have CM in front of me right now so, can’t give exact details. Ping back if you need more details.