I cannot get my head around this, does the toolkit need to be installed on each machine you want to run the software on via intune or only one the machine you are packaging the software on. How does the PSADT work with Intune. Do you need some kind of SCCM/MDT to deploy MDT onto all machines first?
Do you mean why not skip the whole PSADT bit and let Intune just deploy the MSI? I’ll assume so. One reason is that PSADT allows for a user interface / notifications to be sent to the user before/during/after deployment. Probably not a great example in this video, but for apps that need the user to do something, this is a great way to do that. Another reason might be that you want additional logging, or pre/post deployment actions that you want to happen. Finally, you can use PSADT to permit the user to delay or postpone the installation. There are a few more reasons, but it’s probably best if I just make another video to explain them 😀
@@DeanEllerbyMVP agree 💯 PSADT provides so much flexibility and customization. We use it for all our Company Portal apps and always leave the logs in a common location in case we need to troubleshoot installation errors. The added benefit of providing a GUI is a massive benefit for our end-users so they are aware that an automated installation is taking place.
@DeanEllerbyMVP, If you are deploying as System from Intune, how will the user see the the UI generated from the PSADT as it would be running in Session 0 (non-interactive). In the video, we didn't get to see the software deployed from Intune onto an end-user's computer.
You're right! My bad. To allow the user to see and interact with the UI running in Session 0, we need to borrow an app from the Microsoft Deployment Toolkit, called ServiceUI.exe Rudy does a great write up here: call4cloud.nl/2021/01/the-amazing-psadt/
@14:22 you start talking about the setup file should have been the msi - but then the psadt install part is skipped entirely... and the install would just run the msi?
Yeah - I need to go back on that and be more clear. If you use the MSI file to generate the Intunewin, rather than the PSADT file, it will pre-fill the name and details of the app for you. The choice you make during Intunewin creation doesn’t determine which file Intune users during the install, that’s determined when you create the App in Intune.
As I read some blog posts the ServiceUI.exe should be used and probably a 32bit version. ServiceUI.exe -process:explorer.exe Deploy-Application.exe I need to test it.
Thanks for the PSADT run through Dean, - looking forward to more for sure, - really curious to see where you take it from here
great video! can't wait for next one with more details on configuration!
Thank you heaps Dean ... I am combining PSADT with WinGet Packages, works beautifully.
I cannot get my head around this, does the toolkit need to be installed on each machine you want to run the software on via intune or only one the machine you are packaging the software on. How does the PSADT work with Intune. Do you need some kind of SCCM/MDT to deploy MDT onto all machines first?
When doing this, does this install on the user's computers silently without any UI or user interactions?
Excellent video, Dean!
I know this video is a year old, but would this run as a required app during the autopilot process?
Thanks for your videos. Why not upload the msi directly to intune?
Do you mean why not skip the whole PSADT bit and let Intune just deploy the MSI? I’ll assume so.
One reason is that PSADT allows for a user interface / notifications to be sent to the user before/during/after deployment. Probably not a great example in this video, but for apps that need the user to do something, this is a great way to do that.
Another reason might be that you want additional logging, or pre/post deployment actions that you want to happen.
Finally, you can use PSADT to permit the user to delay or postpone the installation.
There are a few more reasons, but it’s probably best if I just make another video to explain them 😀
@@DeanEllerbyMVP agree 💯 PSADT provides so much flexibility and customization. We use it for all our Company Portal apps and always leave the logs in a common location in case we need to troubleshoot installation errors. The added benefit of providing a GUI is a massive benefit for our end-users so they are aware that an automated installation is taking place.
@DeanEllerbyMVP, If you are deploying as System from Intune, how will the user see the the UI generated from the PSADT as it would be running in Session 0 (non-interactive). In the video, we didn't get to see the software deployed from Intune onto an end-user's computer.
You're right! My bad.
To allow the user to see and interact with the UI running in Session 0, we need to borrow an app from the Microsoft Deployment Toolkit, called ServiceUI.exe
Rudy does a great write up here:
call4cloud.nl/2021/01/the-amazing-psadt/
@14:22 you start talking about the setup file should have been the msi - but then the psadt install part is skipped entirely... and the install would just run the msi?
Yeah - I need to go back on that and be more clear.
If you use the MSI file to generate the Intunewin, rather than the PSADT file, it will pre-fill the name and details of the app for you.
The choice you make during Intunewin creation doesn’t determine which file Intune users during the install, that’s determined when you create the App in Intune.
@@DeanEllerbyMVP thanks for clarification
How do i can get MSI product code for any MSI file?
Greta video, in terms of daily administration, would you recommend this or something like patch my pc
This is a great way to deploy apps and manage script deployment. Its completely free so worth keeping in mind for all deployments
I think you chose the wrong setup file location, it should have been the ZOOM application
You are very right on that point! I have no idea why I didn't spot that. Thank you!
Can you go over when it is an .exe file?
All of your videos show using a .msi
Execute-Process -Path "$dirFiles\Setup.exe" -Parameters "/modify ProPlus /config `"$dirSupportFiles\AddOutlook.xml`"" -WindowStyle Hidden
Example.
Hi! As system? Sure?
Not sure which bit you’re referring to but PSADT can run as system, can’t it?
@@DeanEllerbyMVP yep. I'm not able to show the PSADT dialogs. As system, can't show dialogs to user. Perhaps using serviceUi?
As I read some blog posts the ServiceUI.exe should be used and probably a 32bit version.
ServiceUI.exe -process:explorer.exe Deploy-Application.exe
I need to test it.
Did you guys end up testing this without serviceui? asSystem
I really don't understand how this is easier than just deploying an individual pkg in intune?