As I mentioned, we have our own 32-bit EXE “IT Splash Window”. The EXE is just another file that is downloaded to the system and executed at the beginning of the actionscript, specifically for interactive pushes (those that require user input/acknowledgement, such as drivers, bios, and VPN updates). Silent pushes DO NOT use this EXE and are therefore remain silent.
PROS: Notifies users, doesn’t break their VPN, etc. when installing.
CONS: This puts the BigFix action in a RUNNING state indefinitely, or at least until the IT Splash times out. All other actions are now in the BES Client action queue, and cannot run until this one is acted upon by the user. Because of this, we use this sparingly and only when absolutely necessary.
Our EXE is launched via Actionscript with lots of parameters, including these below:
- Beginning or Ending splash (this is the “you need this” vs. “all done” option)
- Security vs. Non-Security splash
- Estimated time to execute action
- Multiple URL links and display text
- Reboot/No Reboot indicator
- Remind me later options
- Master countdown timer (at which point the action will exit with a specific error code that you can work with in the next BigFix actionscript line, or just run the next line of code)
Again, this is a great stand-alone project for someone who needs to build their resume, and post something meaningful on Github. This, of course, does not have to be specific to BigFix, and could be used by any deployment tool. ( <-- am I allowed to say this on this forum??? LOL)