Need PSAppDeployToolkit (4.1.5) to work both in Task Sequence and Software Center with interactive UI

The Toolkit General Discussion
1

Hi everyone,

I’m running into a problem with PSAppDeployToolkit 4.1.5 and I’m hoping someone here has solved this before.

  • In the old 3.x versions I simply launchedwhich (as the docs say) defaults to -DeploymentType 'Install' and -DeployMode 'Interactive'. That worked fine in both Software Center and imaging.Deploy-Application.exe
  • Now, with 4.1.5, I’m usingtogether with Show-ADTInstallationWelcome (to prompt users to close specific apps) and Show-ADTInstallationProgress (to show an estimated install time and progress).Invoke-AppDeployToolkit.exe -DeploymentType Install -DeployMode Interactive
  • This works perfectly when the app is installed via Software Center: users get the welcome prompt to close apps and a progress message.
  • But when I use the same deployment in an OSD Task Sequence (during imaging), the step fails as soon as it hits the interactive mode. My understanding is that during imaging there’s no active user session, so interactive UI can’t be displayed.

I would like to keep one single deployment that:

  1. Shows the welcome/progress UI when installed from Software Center (so users can choose which apps to close and see the install estimate), and
  2. Runs silently/non-interactive when executed inside a Task Sequence.

Has anyone found a good pattern or script logic to detect when the app is running inside a TS and automatically switch to NonInteractive while keeping the interactive mode for Software Center?

Any code samples, best practices, or pointers to official PSADT docs/examples would be hugely appreciated.

Have tried deploymenttype auto now its not working for all programs?

Thanks in advance!

2

This is a duplicate of 4.1x User Interactivity Behavior. We're looking into it.

3

i got told to make a new thread? after i ask how to send a pm for one after my reddit post and he ref to the post to link to

4

I'm sorry for that, the person who asked might not have understood the situation.