1. PDQ Deploy & Inventory Help Center
  2. Community
  3. PDQ Deploy
 

Important Notice: On February 29th, this community was put into read-only mode. All existing posts will remain but customers are unable to add new posts or comment on existing. Please feel to join our Community Discord for any questions and discussions.

MSI config options and user notifications

Avatar
Scott Parkis

When creating an install package - I want to 1) notify the users we are doing an install 2) make sure outlook is closed 3) show the status of the installation.

PDQ Deploy Details -> Parameters vs Command Line (and custom)

I have a bunch of options I want to apply:

(ZoomautoUpdate="true" ZoomAutoStart="false" ZConfig=nogoogle=1;nofacebook=1;advdscp=1;AddFWException=1;FullScreenWhenJoin=0;DisableScreenShare=1;ConfirmWhenLeave=1;UserDualMonitor=0;MuteVoipWhenJoin=1;HideNonVideoUsers=1)

  1. For an msi does this go on the Parameters field? command line field is getting populated. And when would I select Custom here?
  2. MSI Options -> those look fine.
  3. I am installing two different msi's in this package. I really want a passive installation so users can see an install is going on. Or can I keep it as a quiet install, and just have a message w/ some status for the two msi's in this package. So users know when its done and can start opening stuff? how?
  4. check for outlook to be closed before I start.

Thanks!

0

Comments

3 comments
Date Votes
  • Avatar
    sean johnson

    This might work for you. It doesn't ask for permission but it will let the user know what's up per step.

    Step 1 (powershell - make sure to select run as logged on user under options)

    $wshell = New-Object -ComObject Wscript.Shell
$wshell.Popup("A message to your user that the program will update",0,"Box Name",0x0)

    Step 2 (powershell) get-service -name "whatever" | stop-service

    Step 3 (do your thing)

    Step 45678 (inject any other messages between steps for update or task completed) (again make sure to select Run as Logged on User under Options for the task)

    ref https://mcpmag.com/articles/2016/06/09/display-gui-message-boxes-in-powershell.aspx https://powershell.org/2013/04/29/powershell-popup/

    0
  • Avatar
    Scott Parkis

    Thanks.

    so how do you do Step 1 to keep going until Step 8 is complete?

    User Logs on Notification "installations happening, please wait..." (this stays on screen during installs) Do the installations (/quiet w. Notification still on the scree) Notification updates to "complete" and closes.

    0
  • Avatar
    sean johnson

    the notification from above would only be relevant to users already logged on. For anyone after that it would not happen until the next notification window.

    I'm having trouble understanding your specific requirement, it might help if I understood a bit more of what your attempting to achieve.

    A few questions to help better understand

    1. Do you have a prohibiting factor for off hour updates?
    2. Could you instead opt for something like a desktop background? I have a BGINFO script that throws up system information over a default background that could be used to update the background to a "Under construction" background or whatever for all system users.

    for part 2 you just download BGINFO and add a startup script to group policy to run the BGINFO template file against bginfo after copying it local with the background of your choice. Something like C:\generalstuff\bginfo

    Then just change step one to copy a replacement jpg or whatever to bginfo new step 2 execute the same script as logged on user and tada the background changes to "stuff is happening" untill whatever step where you put it back to normal or to a finished background until log off and on gpolicy reapply normal.

    0