What IS the Powershell App Deployment Toolkit? Here's a quick look.

[@lynetteberg4807]

Good Stuff, i'm still learning allot of this Intune stuff and yet i've learned something new with using this App Deployment Toolkit . With instructions and seeing it live, taught me a few things. I'm super grateful. This is really good stuff.

[@marinotarulli6568]

Excellent Topic, I love this PS toolkit

[@theCMC]

Thanks Marino!

[@ashisharya65]

Hi Dean, I was looking for a simple tutorial to understand how the app packaging works via PSADT tool and luckily reached to this video. Thank you so much for explaining this tool in the most simplest manner. Regads, Ashish Arya

[@theCMC]

You’re welcome! Glad it helped.

[@christianh9920]

51% do not know PSADT? This is a super toolkit!

[@theCMC]

I know right! Spread the word 😂

[@axiomvicarious]

Was hoping this would help me with deploying applications, but for some reason our Intune environment is unable to run any install commands. It can't run powershell.exe. Requirement and post-detection scripts run just fine, but from install command it just does not work. Tried running cmd.exe as well and that doesn't work either. Great video though, very informative!

[@ResurrectionMotorsports]

I typically under the Install command use Deploy-Application.exe -DeploymentType "Install" any reason for using the ps1 vs the exe?

[@theCMC]

Now that you mention it I think the docs suggest to use the .exe - good catch!

[@DavidAlexander-kc6tx]

How do i get the PSAppDeployToolkit notifications to the enduser? The win32 App will be executed as system account

[@theCMC]

That’s where ServiceUI comes in. Take a look at this blog from Rudy. call4cloud.nl/2021/01/the-amazing-psadt/

[@Distrax]

Wy would you call the powershell script instead of the .exe? just currious

[@theCMC]

Not sure, actually.

[@Distrax]

@@theCMC Thanks for the video love PSADT, i used it in SCCM times and now Intune.

[@alphaeusmote184]

One major reason is that usually applications require that things be done before and after the application install/removal. Most apps do not handle the removal and upgrade of versions. As a result the environment becomes in disarray. With scripting, now you could remove older versions dynamically and install the version you intend.

[@theCMC]

Oh, I thought the question was “why use deploy-application.ps1 rather than deploy-application.exe?”

[@alphaeusmote184]

I was deceived by my eyes and misread the question. You are right my good sir! As far as the original question is silence. Powershell makes a window flash when executed interactively and also has a more complex command line. The exe is a bootstrapper that hides the window and launches the Deploy-Application.ps1 powershell script for you along with any parameters you pass through the exe. The only warning is that exe requires that .Net 3.0 be enabled on your device otherwise you will get a pop up by Windows asking if you want to enable it.

[@nicholasguerrero577]

im confused. why would you use this if you have the msi? SCCM lets you deploy these with the msi to workstations already? Just confused. I know some applications dont use msi's and thats why i use PSADT

[@daveus111]

For msi you want to use PSADT only if you need more customizing of the installation-process. For example you need to copy additional files, Stop-Processes or Delete a Registry key...Much more is possible with the script Runner then with the MSI option of patchmyPC

[@creativegarb]

When I attempt to deploy this through Intune, it fails during the ESP phase when installing (0x81036502). I'm attempting to setup, configure and refine our AutoPilot process. Any ideas on what this is and why it would be doing it? Would any policy block or stop a power script from running potentially?

[@e_steban89]

How are you all running the tool for .exe installations. I'm lost when packaging it up with the IntuneWinAppUtil.exe once the .ps1 script is edited with all the installation steps. Am I converting the .ps1 or the .exe application? Any guidance would be most appreciated.

[@bulliontoy]

Very skeptical about it working for more complex msi. I'll have to test this but I've had issues deploying with PS and gpos. Especially o365 install, printer drivers software that need prompts and entering info, packaging that can't be /qn or needing license typed. We had to end up reverting to manual install. Or using app-v so no installation was needed besides pushing app-v to the client.

[@theCMC]

Interesting! Would you be interested in joining a live session to talk through these? I have a PSADT expert who is happy to talk through it live. Hit me up on Twitter @dean_ellerby if you are!

[@Eschguy]

This doesn't seem any easier than just pushing an .msi through Intune, though.

[@theCMC]

It’s definitely not easier. MSI via Intune is a couple of steps - this is way more. This tool brings additional features that the native Intune installer can’t do, such as notifying the user and allowing them to defer the install / upgrade.

[@NA-lp2re]

If that's all you need to do you are right. However deployments often take multiple stages. Sometimes you need to present the user with prompts to install and chances to defer. It also allows you to run several installations within the same toolkit. Also is useful when you need to uninstall applications before hand or import or set a registry key before or after the main installation. I use it all the time

[@ResurrectionMotorsports]

@@NA-lp2re Do this as well, use it to inject registry strings that I will in turn use for Detection Methods, then you can version the string value along with the script to have versioning and method detection.

[@petersabou]

PSADT is awesome when you need to package many apps quickly that may be straightforward MSIs. You only need to drop the app msi in the Files folder and that’s it, don’t do any edits to the ps1. Literally creates a deployable package for SCCM in less than a minute, with log file. Also it’s great for apps that install under the user context and writes to the registry - use Invoke-HKCURegistrySettingsForAllUsers in the ps1. Brilliant!

[@DannyNilsson]

I have now seen many videos about this toolkit, but when it requires a MSI file to begin with. why not just deploy with file.msi /qn to do a silent installation. where are the benefits if you only aim at silent installs. I could see the toolkit has its power when it comes to interactive installations. Where does this position it self? i guess when you have a install shield program do create MSI, this tool will not benefit you. or is it aimed at a freeware product to begin in smaller scale?

[@DannyNilsson]

from my testing, i can see the comunity have a huge list of finished scripts, that can save a lot of time even though it might be as powerful as a full blown installer. its free and add the ability to easy update already made scripts with just an exchange of the exe file. and further into deploy it can save time on updating multiply scripts instead of a gui based installer

[@theCMC]

Great insight, thanks Danny. I agree, there are many possible use-cases for PSADT and many of them would be difficult or cumbersome to solve without this toolkit.

[@htconex19062012]

Thanks so much 🙏

[@davidhood1972]

Shame he didn't show the actual experience the end-user sees

[@theCMC]

True. I was planning to but a W11 feature update has broken my Camtasia, so I was lucky to get it released at all. I will follow up with the end user side 😀

[@WetterThnWtr]

wait this isn't valorant...

[@yendang6143]

Love your videos. I follow your guide when i started editing the deploy-application.ps1 but could you tell me how i could point to appdata oaming location? ## CMD /c C:\Windows\system32 obocopy.exe "custom templates" "C:\Users\%Username%\AppData\Roaming\Microsoft\Templates\Charts" /MIR