Skip to main content

Getting information back from a Message Box with PowerShell

Sometimes I want a script to run automatically, but still prompt me before it takes an action.  A neat way of doing this is with a pop up message box.  Utilizing the MessageBox class from the .NET Framework, we can do just that.  For example, maybe I have a script that notifies me with the Dow Jones Industrial Average drops by 300 points in the current trading session.  Hey, that is a money making opportunity! 
1
2



3
4
5
6
[System.Reflection.Assembly]::LoadWithPartialName("System.Windows.Forms")
$Answer = [Windows.Forms.MessageBox]::Show("DJIA has dropped by 300 points today `n Do you want to `n go to your IRA?", "Trade Alert",
          [Windows.Forms.MessageBoxButtons]::YESNO,
          [Windows.Forms.MessageBoxIcon]::Information)

If ($Answer -eq "Yes")
{
    Write-Host "Do Something."
}
Essentially, line 1 gives us access to the Windows Forms objects.
Line 2 Saves the answer of our message box in a the variable $Answer.  To control the type of message box that we display, we have several options. 

The Windows.Forms.MessageBox class is overloaded.  That means that you can implement it in several different ways.  In this instance, we are using the Show method.  Take a look at the screen shot below of the many different versions of the Show method for this class:
image
What differentiates each call to the MessageBox class is the number of arguments and their data types that you pass to the class.  In this case, we passing the 7th item which is String, String, MessageBoxButtons, MessageBoxIcon.
Clicking on this item, we are taken to the MessageBox.Show Method (String, String, MessageBoxButtons, MessageBoxIcon) method on MSDN.  Here we can see that the first string is the message and the second is the caption on the message box window.
image
From here, if we click on System.Windows.Forms.MessageBoxButtons, we can see the types of buttons that we have access to.
image
In this example, we are using YesNo. Yes or No will be returned and stored in $Answer
We are also choosing an icon for this message box from MessageBoxIcon. Here are valid options are:
image
In the end, this is what you will see:
image
Either the string Yes or No will be returned when the appropriate button is clicked.

Comments

Popular posts from this blog

How to run GPResult on a remote client with PowerShell

In the past, to run the GPResult command, you would need to either physically visit this client, have the user do it, or use and RDP connection.  In all cases, this will disrupt the user.  First, you need PowerShell remoting enabled on the target machine.  You can do this via Group Policy . Open PowerShell and type this command. Invoke-Command –ScriptBlock {GPResult /r} –ComputerName <ComputerName> Replace <ComputerName> with the name of the target.  Remember, the target needs to be online and accessible to you.

Set up your Environment to utilize Invoke-GPUpdate

I’m sitting in O’Hare enjoying my 3 hour layover as I get ready to teach a Windows 10 class in Fort Wayne.  I’m actually prepping for my class in Fort Wayne in a few weeks, 10982 Supporting and Troubleshooting Windows 10.  This class is very much like the Windows 7 version that I used to teach so I decided to up the detail quite a bit.  In the GPO troubleshootin chapter, I’m including a demonstration on how to use PowerShell’s Invoke-GPUpdate.  I needed to make sure the environment is set up for me to be able to utilize this cmdlet.  If you read the Notes section on Invoke-GPUpdate’s help file, you will see there are three firwall rules that need to be in place:          Remote Scheduled Tasks Management (RPC)          Remote Scheduled Tasks Management (RPC-ERMAP)          Windows Management Instrumentation (WMI-IN) I decided to create a little PowerShell script to crea...

Where did a User’s Account Get Locked Out?

Updated: May 15, 2015 When this article was originally published, two extra carriage returns were add causing the code to malfunction.  The code below is correct.   My client for this week’s PowerShell class had a really interesting question. They needed to know where an account is being locked out at. OK, interesting. Apparently users hop around clients and forget to log off, leading to eventual lock out of their accounts. The accounts can be unlocked, but are then relocked after Active Directory replication. This problem is solved in two parts. The first one is to modify the event auditing on the network. The second part is resolved with PowerShell. The first part involves creating a group policy that will encompass your Domain Controllers. In this GPO, make these changes. Expand Computer Configuration \ Policies \ Windows Settings \ Security Settings \ Advanced Audit Policy Configuration \ Audit Policies \ Account Management Double click User Account Management C...