PSADT Example - Relaunch Processes and inform user

[LeeViewB]

Pull Request Type

• [X ] New Script
• Edit Script
• Repository Improvement

Brief summary of changes

This is an example PSADT script that can be used in the Cloud Portal.
With this example, and with the provided pre and post-scripts, customers can now relaunch processes closed during the installation and inform the user that the installation is complete.

Describe your Testing

I have tested this with various applications in my lab, like Google Chrome (one conflicting processes) and OBS Studio (multiple conflicting processes running)

Checklist

• Did you Clean your script - No environment details, comments are PG-13
• Did you test your script
• If required, did you create, and include a Read Me as outlined in Community Scripts Read Me

[DanGough]

Please can you investigate whether the MCP process list can now be overidden by the new minified command line? If so then we cannot rely upon package.xml for the process list.

Similarly WSUS/ConfigMgr updates will have their processes defined via command line as there is no package.xml in such updates.

Both situations could be resolved by either allowing for the process list to be supplied as a script parameter (you could use the same format as Show-ADTInstallationWelcome [PSADT.ProcessManagement.ProcessDefinition[]]$CloseProcesses), or by querying the command line of the running ScriptRunner process (and decoding the base64 in the case of the minified command line).