cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Powershell Deployment Toolkit Packages in AdminStudio 2019

We have a lot of packages that were created using the PS App Deployment Toolkit and are trying to import them.  Some of them seem to work, however others we keep getting the error that it is an invalid installer.  Is there any type of matrix that tells you what exactly AdminStudio is expecting to see?  Everything appears to be the same with the ones that work compared to the ones that don't, but not seeing much in the logs that would tell us why it is an invalid installer.

(1) Solution

The PowerShell wrapper script that AdminStudio uses as a template to wrap the packages looks for the setup files (installers) at the root of $dirFiles (Files) therefore AdminStudio always expects the installers to be available at the root of $dirFiles (Files) for successful import of wrapped packages.

Thanks

View solution in original post

(3) Replies

While importing a PowerShell wrapped package, AdminStudio expects it to be in certain format for import to be successful. The files and folder structure of the wrapped package should look like this: 

kmantagi_0-1573557470995.png

For successful import of PowerShell wrapped packages, the files, folder content and folder structure should match with what you see in the 'PowerShellTemplate' folder which can be found in AdminStudio's install directory here  - C:\Program Files (x86)\AdminStudio Shared\PowerShellTemplate

The content of PowerShellTemplate folder is explained here

Thanks

Thanks for the information.  Does the installer need to be in the root of the Files directory?  For example can it be in $dirFiles\Source\example.exe" or does it not like the additional folder?  I am seeing that if I move the install files from the additonal folder into the root of $dirfiles (Files) then it seems to work ok.  The script will work fine with the additional folder but not sure if Adminstudio needs to see it in a specific location.

The PowerShell wrapper script that AdminStudio uses as a template to wrap the packages looks for the setup files (installers) at the root of $dirFiles (Files) therefore AdminStudio always expects the installers to be available at the root of $dirFiles (Files) for successful import of wrapped packages.

Thanks