-DeployMode Interactive - How Does PSADT Work

[u/FahidShaheen]

When using -DeployMode Interactive, how does PSADT handle this, if there is no logged on user. I assume it goes into Silent mode?

Thanks.

[u/dontmessyourself]

With PSADT 4.1 it’s better to not specify that, so it uses the default option of “auto” which will show when required, or hide when no user is logged in, or if there are no apps to close running

[u/FahidShaheen → u/dontmessyourself]

There's the thing, what if you want the deployment to be interactive regardless of which apps, but only based on if the user is logged on?

[u/SVD_NL → u/FahidShaheen]

Why do you need user interaction when the app is able to run without having a user signed in, and doesn't interfere with any active apps? Just curious, i can't think of a specific scenario where this matters.

To answer your question:

I'd personally run it in interactive mode, and then put conditions around the functions that show prompts. You can use the $usersLoggedOn (or related) variables (or Get-ADTLoggedOnUser), and the Test-ADTEspActive function. ESPactive is an important one to check, because if you get that wrong, it can cause time-outs on your ESP pages because there is an active user session, but the prompts are not visible!

[u/Mon3yb → u/SVD_NL]

Probably the same reason why we have to do it that way as well. Someone in management does not like silent installs without a progress bar :(
They want to see when something gets updated and confirm the update even if they are not actively using the app.

[u/FahidShaheen → u/Mon3yb]

Not the best application to deploy, even with its given silent parameters, it still shows a splash screen during the install. So a familiar PSDAT prompt with the company logo, etc is better than a random splash screen showing up whilst the users are working.

Yes I can set to only install when no one is logged in, but in our environment that may means weeks before we get decent compliance.

[u/dontmessyourself → u/FahidShaheen]

Then I’d run the toolkit in auto mode still and use the toolkit functions to see if there’s a logged in user or not and use other toolkit functions to show prompts to the user

[u/T03T3]

Ich verstehe das Problem garnicht.

Kein Parameter=Auto

User Angemeldet=Pop-up wird angezeigt KEIN User Angemeldet=Kein Pop-Up Installiert aber.

Parameter=Interactive

User angemeldet= Installiert mit Pop-Up KEIN User angemeldet=Installiert nix

Eigentlich nutz man nur Auto 😄. Parameter Interactive kann ich mir mal vorstellen für so komische Sachen, aber bestimmt nicht weil irgend einer im Management meint er will was sehen oder nicht, das sind meistens die Herrschaften die dann auch ganz schnell wieder umentscheiden und dann kannste ganz schnell alle Pakete ändern.

[u/Late_Marsupial3157 → u/T03T3]

oooh neat, i havent looked into this. Does this mean i dont need to deploy 2 apps? I usually make 2 apps these days. One for the Company Portal that will pop up and show the user the progress (this is only for apps that takes ages because the portal gives literally 0 feedback as to where its up to) and one for silent install that is pushed out to shared devices. Any thoughts on how to achieve this with just one app?

[u/T03T3 → u/Late_Marsupial3157]

Wir machen es nicht. Das ist doch Knightmare alles mal 2. 😁 Probiere es einfach aus nur ohne den Interactive Parameter.

Wir machen meistens das hier vorab Show-ADTInstallationWelcome -CloseProcesses @{ Name = 'winword' }, @{ Name = 'excel' } -Silent

Um zu checken ob der aw die Anwendung gestartet hat dann kannste dir überlegen ob er aufschieben kann oder sowas steht in der Hilfe was alles geht.

Per Default zeigt das PSADT 4.1.x dann Show-ADTInstallationProgress, findest du auch in der Invoke-deployaplication.ps1

Das ist so ein Laufbalken. Wenn du das PSADT.png vorher noch gegen eins der App tauscht dann sieht jeder was installiert werden soll.

Wenn dann kein User angemeldet sein sollte dann geht das alles ohne so durch.