COMMAND SCREEN POPPING UP WINDOWS

Several years back, Windows included a command named Net Send, which could be used to display popup messages on a user’s screen. Unfortunately, there is no native PowerShell cmdlet for generating popup messages. A simpler option, however, is to generate PowerShell on-screen alerts by using popup messages. One option, for example, is to design the script to send email alerts whenever necessary. There are several different ways of accomplishing this. What the script really needs is a way of getting someone’s attention in real-time. Because the IT staff is likely to be busy with other things, they are likely to assume that the script is working just like it always has, and therefore ignore the log file. This approach works fine in nominal situations, but imagine what would happen if the script encountered a problem. Getting attention with PowerShell on-screen alerts That being the case, the script is most likely to write its output and any other relevant information to a log file. After all, there probably isn’t going to be someone looking at the screen when the script runs. Because the script is running automatically on a scheduled basis, writing the script’s output to the PowerShell console isn’t going to be effective. The script’s purpose is irrelevant to this discussion, but let’s assume that the script does something important. Imagine for a moment that you have configured the Windows Task Scheduler to automatically run a specific PowerShell script once a week. Even so, they are not ideally suited to every situation. Both of these approaches are widely used and are perfectly valid. Either the script displays a message on screen or it writes information to some sort of log file. Most of the time, PowerShell scripts that are designed to automate some sort of task convey the task status in one of two ways.

Command screen popping up