cabele/master
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Merge branch 'master' of https://github.com/byteben/Toast

Browse source
This commit is contained in:
Ben Whitmore 2021-01-10 22:48:47 +00:00
commit 82327cb3f7
1 changed files with 32 additions and 28 deletions
Download patch file Download diff file Expand all files Collapse all files

60
README.md
View file

@ -1,27 +1,31 @@
# Version History # Version History
**Version 1.2.10 - 10/01/21**
-Removed XMLOtherSource Parameter
-Cleaned up XML formatting which removed unnecessary duplication when the Snooze parameter was passed. Action ChildNodes are now appended to ToastTemplate XML.
**Version 1.2 - 09/01/21** **Version 1.2 - 09/01/21**
Added logic so if the script is deployed as SYSTEM it will create a scheduled task to run the script for the current logged on user. -Added logic so if the script is deployed as SYSTEM it will create a scheduled task to run the script for the current logged on user.
If the Toast script is deployed in the SYSTEM context, the script source is copied to a new folder in the users %TEMP% Directory. -If the Toast script is deployed in the SYSTEM context, the script source is copied to a new folder in the users %TEMP% Directory. The folder is given a unique GUID name.
The folder is given a unique GUID name. -A scheduled task is created for the current logged on user and is unique for the each time the Toast Script is deployed. Each scheduled task is named using the User SID and the unique Task GUID.
-If the script is deployed to the current logged on user, a scheduled task is not created and the script is run as normal.
A scheduled task is created for the current logged on user and is unique for the each time the Toast Script is deployed. Each scheduled task is named using the User SID and the unique Task GUID.
If the script is deployed to the current logged on user, a scheduled task is not created and the script is run as normal
**Version 1.1 - 30/12/20** **Version 1.1 - 30/12/20**
Added a Snooze option (Use the -Snooze switch) -Added a Snooze option (Use the -Snooze switch).
**Version 1.0 - 22/07/20** **Version 1.0 - 22/07/20**
Release -Release
# Project Outline # Toast Notify
**Screenshots** **Screenshots**
http://byteben.com/bb/wp-content/uploads/2020/07/Toast-Example.jpg http://byteben.com/bb/wp-content/uploads/2020/07/Toast-Example.jpg
http://byteben.com/bb/wp-content/uploads/2021/01/Toast-Example-Snooze.jpg
http://byteben.com/bb/wp-content/uploads/2020/07/Content-Example.jpg http://byteben.com/bb/wp-content/uploads/2020/07/Content-Example.jpg
**Description** **Description**
@ -48,23 +52,15 @@ More information and Toast Content guidelines can be found at:-
https://docs.microsoft.com/en-us/windows/uwp/design/shell/tiles-and-notifications/toast-ux-guidance https://docs.microsoft.com/en-us/windows/uwp/design/shell/tiles-and-notifications/toast-ux-guidance
**Parameters** **Parameters**
You should specify either XMLScriptSourceDir **or** XMLOtherSource parameters but not both. If you specify no parameter the script will read the CustomMessage.xml in the script root. If you specify no parameter for XMLSource the script will read the CustomMessage.xml in the script root.
**.PARAMETER XMLScriptDirSource** **.PARAMETER XMLSource**
Specify the name of the XML file to read. The XML file must exist in the same directory as Toast_Notify.ps1. If no parameter is passed, it is assumed the XML file is called CustomMessage.xml. Specify the name of the XML file to read. The XML file must exist in the same directory as Toast_Notify.ps1. If no parameter is passed, it is assumed the XML file is called CustomMessage.xml.
**.PARAMETER XMLOtherSource**
Specify the location of the Custom XML file used for the Toast when it is not the same directory as Toast_Notify.ps1 e.g the full UNC path to the XML file.
**.EXAMPLE** **.EXAMPLE**
Toast_Notify.ps1 -XMLOtherSource "\\\\fileserverhome\xml\CustomMessage.xml" Toast_Notify.ps1 -XMLSource "PhoneSystemProblems.xml"
**.EXAMPLE**
Toast_Notify.ps1 -XMLSciptDirSource "PhoneSystemProblems.xml"
**.EXAMPLE** **.EXAMPLE**
@ -72,18 +68,26 @@ Toast_Notify.ps1 -Snooze
**Known Issues** **Known Issues**
Currently, the images in the XML can only be read from the local file system. This is not an issue if we are deploying the package from MEMCM. -Images in the XML can only be read from the local file system. This is not an issue if we are deploying the package from MEMCM
PowerShell Window flashes before Toast when deployed in SYSTEM context -PowerShell Window flashes before Toast when deployed in SYSTEM context
**Thanks for the help from** **Inspiration, Credit and Help**
@guyrleech @guyrleech
@young_robbo @young_robbo
@mwbengtsson
@ccmexec
@syst_and_deploy
@PaulWetter
**Community** **Community**
Seriously check our Martin Bentsson's work on Toasts. It is very comprehensive. https://www.imab.dk/windows-10-toast-notification-script/ https://www.imab.dk/windows-10-toast-notification-script/
I don't believe in reinventing the wheel, part of me was saying "Use Martin's Script", but I challenged myself to learn how Windows Toasts work from the ground up - so this project was a labour of love for me. I have enjoyed the ride so far. http://www.systanddeploy.com/2020/09/display-simple-toast-notification-with.html
https://github.com/Windos/BurntToast
https://wetterssource.com/ondemandtoast
https://msendpointmgr.com/2020/06/29/adding-notifications-to-win32appremedy-with-proactive-remediations/
https://msendpointmgr.com/2020/08/07/proactive-battery-replacement-with-endpoint-analytics/
If you have any comments, feedback or would like to contribute - please don't be shy! I welcome comments and feedback. Please fork repo to contribute