Hi,

Today was a great day :) I tested my package Template on SCCM 2012 R2. In this Template, I implement PS AppDeployToolkit. But the balloon tips and dialog box never appeared. When I am running the package manually, everything is fine. So I review the PSAD documentations.

I am launching my package with the following commandline:

powershell.exe -executionpolicy bypass -file .\mypackage.ps1 "install" "Interactive"

Am I missing something?

Thanks.

This question has nothing to do with ConfigMgr, so you should post the question to the Powershell App Deployment Toolkit forums: https://psappdeploytoolkit.codeplex.com/discussions. 

I don't think you want Run set to Hidden.  Set it to maximized.  Also, that package is running in the System context.  The user will not see anything as they are not logged in with the System account. 

I've used workarounds to allow users to interact with PS in the past, but never used psappdeploytoolkit.

Hi,

1. Why would I not want the package running hidden? With maximized a user would be able to close the powershell window and it would disturb the customer?!

2. If I change "Program can run" from "Whether or not a user is logged on" to "Only when a user is logged on" that would mean as soon as the session is logged off the packages would not run?!

2a. In fact keeping it "Whether or not a user is logged on" with check "Allow users to interact with this program" should make the program able to run always with interaction?!

3. In my past life with SMS 2.0, I ran package with "requires drive letter". Is it still better or UNC is better?

Hi,

>>When I am running the package manually, everything is fine. So I review the PSAD documentations.

Have you tried to run the commandl line under the system account?

Best Regards,

Joyce

Remove hidden and it will work also change it to "Only when a user is logged in"

Hi

Not sure to understand as SCCM is using system account by default. Would you give more dtails?

Thanks,

Hi,

I already tried it with no success. And running "Only when a user is logged in" would mean no distribution at night on logoff computers. This is bad.

Thanks,

The way we got around this was to use the application model and create two deployment types for the one application. One that runs only when a user is logged in (PADT runs in interactive mode). A second deployment type runs in non-interactive mode that runs only when no user is logged in. 

We target the non-interactive/logged off deployment at our student machines because we don't want students to be in the middle of working on a project and have to close down apps etc. We aren't as worried about this for staff. We do this using a global condition called "Staff Machines" and this must be true on the interactive deployment type.

I hope this helps?

Which version of PSADT are you using?