How to use the OpenFileDialog Control with SAPIEN PowerShell Studio

Developing advanced GUIs is a neat way to expand your PowerShell coding capability. Traditionally, we would have to learn a different programming language to do this. That means you would have to learn PowerShell for your day-to-day tasks and something like C+ or .NET to crate the GUI. After teaching PowerShell for the last 7 years, I know that IT Pros do not want to have to learn multiple languages. With SAPIEN PowerShell Studio, you can leverage your PowerShell skill set in a visual environment.

Today we are going to take a very simplistic view on how to graphically select files on your hard drive. First, create a simple form with these three controls. Button, Label, OpenFileDialog. The first two will appear on your form but the OpenFileDialog will appear below the form because it will open in a new window when called.

Next, add the Click event to the button and then add this code: (Remember to add the event by right clicking button1 and selecting edit default event. Just typing lines 7 and 12 will not register the event.)

We left all of the control names at their defaults for simplicity. Line 9 will open the file browser. Line 10 will display what you selected in the label.

Here we go!

Click on button1

Select a file and click OK.

The name of the selected file is stored in the FileName property of the $openfiledialog object.

Nice and easy!!!

Comments

How to list all the AD LDS instances on a server

AD LDS allows you to provide directory services to applications that are free of the confines of Active Directory. To list all the AD LDS instances on a server, follow this procedure: Log into the server in question Open a command prompt. Type dsdbutil and press Enter Type List Instances and press Enter . You will receive a list of the instance name, both the LDAP and SSL port numbers, the location of the database, and its status.

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.

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...

Jason Yoder, MCT

Search This Blog