Hi,
The new PSADTv4 is Powershell 7 capable. This is one of the new features. However, Powershell 5 is executed when the ‘Invoke-AppDeployToolkit.exe’ is executed.
I have already searched, but unfortunately found no further information.
Is it possible to force PSADTv4 to run Powershell 7.
By the way, I noticed this when using Invoke-WebRequest.
There isn’t a way currently, but it’d be good to have. I’ll add it in after the Christmas holidays but it won’t be in a release until 4.1.0, currently slated for Q2 2025.
EDIT: Tracking it here: [Feature] Add switch to exe to allow it to invoke with PowerShell 7 · Issue #1218 · PSAppDeployToolkit/PSAppDeployToolkit · GitHub
For deployments with Intune, SCCM etc. there is no problem as we can start the PS1 directly with pwsh.exe (Powershell 7).
However, we also provide any packages to the 1st level for a “quick deployment”. It is easier if only the EXE has to be started. It is more streamlined.
As these are exactly the same packages that are also deployed in Intune, there are no differences and the detection methods are also 100% effective
I am looking forward to version 4.1.0
Thanks Mitch for the quick reply.
I wish you a Merry Christmas.
These changes have been implemented in Resolved via - Add `/Core` switch to `Invoke-AppDeployToolkit.exe` to allow using … · PSAppDeployToolkit/PSAppDeployToolkit@431f5de · GitHub and - Let `Invoke-AppDeployToolkit.exe` invoke the PowerShell path in its… · PSAppDeployToolkit/PSAppDeployToolkit@1eb4fb5 · GitHub, and will be part of 4.1.0 as discussed.
You can now either specify /Core to force it to use PowerShell 7 (it’ll throw if it’s not installed), but the latter commit will automatically run Invoke-AppDeployToolkit.ps1 using whatever PowerShell parent Invoke-AppDeployToolkit.exe is called from. So if you’re calling Invoke-AppDeployToolkit.exe inside a 32-bit version of PowerShell 7, it’ll automatically use it.
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.