V4.1.5 Show-ADTInstallationPrompt Pre-test Runas Admin problems

Am I doing something wrong? Before I begin, I need to adjust.

Invoke-AppDeployToolkit.ps1 still says 4.1.5.
Invoke-AppDeployToolkit.exe is still 4.1.5.

The contents of PSAppDeployToolkit_ModuleOnly\PSAppDeployToolkit are the same as those in the template PSAppDeployToolkit_Template\PSAppDeployToolkit.

or can I try until it is released properly

We don't re-version the toolkit until it's released. This is a pre-4.1.6 release that contains fixes not in 4.1.5, which is why I was wanting you to test it.

Hi @mjr4077au, I tested pre-4.1.6 and this worked perfectly using my Admin account. I tested an install from an elevated-admin PS prompt using Invoke-AppDeployToolkit.ps1, and I also tested using run-as-admin on Invoke-AppDeployToolkit.exe.

Thank you,
Paul

No wonder I couldn't replicate it as it was something we've already addressed! We'll likely get 4.1.6 released next week at some stage.

Thank you for testing and working this one through with me :sign_of_the_horns:

praise to you, send you the log by email
================== 4.1.6 Beta Version ==================
via cmd/Invoke-AppDeployToolkit.exe = viaexe 101160-harmonie10.7.10006x64-MUI_PSAppDeployToolkit_Install.log

via Powershell powershell.exe -executionpolicy bypass -file Invoke-AppDeployToolkit.ps1 = 101160-harmonie10.7.10006x64-MUI_PSAppDeployToolkit_Install.log

Dialogs appear, open application is closed, completion dialog appears
open application is closed Show-ADTInstallationWelcome @saiwParams
uninstall works Uninstall-ADTApplication -Name $MyRemove -ApplicationType 'MSI'
installation works Start-ADTMsiProcess -Action 'Install' -FilePath $MyMSIFile

not tested via SCCM or Intune Agent.
thanks

Thank you mate, I'm glad it's all working well!

RIP Robert Redford!
RIP Robert Redford (1936-2025) :man_bowing:

For what it's worth, if the big warning when using your admin account is annoying you, you can grant your admin account the necessary privileges to impersonate other users if you wish. The privilege SeAssignPrimaryTokenPrivilege translates into "Replace a process level token" within User Rights Assigment:

Thanks, good to know, but that doesn't bother me. What's important is all the features I at least use and need.

per machine per user
as runas admin
SCCM with login user
SCCM without user/provisioned mode
Intune with login user
Intune via Autopilot required

You just have to be patient; we can't always test everything right away.

You're doing a great job.

I don't believe you'll have an issue with any of those other scenarios. It's just the runas admin setup is tricky to say the least.