Add a bit of Control to Your PowerShell Code

Currently I am in the middle of writing a script that is exceeding 2500 lines of code. Although I can keep the horizontal scrolling under control, the vertical scrolling is getting out of hand. The collapsible code functionality in the PowerShell V3 ISE really helps in keeping the scrolling down.

In the screenshot above, you can see those little “+” symbols on lines 164 and 201. Notice the line numbers jump from 164 to 194. This collapsible region was defined by the curly braces for this function. Once I get a function completely debugged, I collapse it to make my scrolling easier. In my current situation with 2500+ lines of code, collapsing every region each time I load the script in the ISE is a bit time consuming. Here is a little secrete, press Ctrl M. Take a look at my code now.

Now I can selectively expand my code so I am only looking at what I need to look at. This little trick will help reduce the frustration of vertically scrolling through large amounts of code and will also save your mouse wheel from unnecessary wear and tear, not to mention your index finger. This little shortcut is not listed on the Microsoft Keyboard Shortcuts webpage for the ISE. To expand all of your collapsible regions, press Ctrl M once again.

My friend Jakub Jareš has an article on PowerShellMagazine.com about how to use Regions to manually define expansion regions in your code. It is worth a few minutes of your time.

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