Highlight Unknown Commands in Sapien PowerShell Studio

OK, so I should not be working right now. It is Friday. I just finished teaching a 5 day Windows Server 2012 R2 class. It is sunny and 86 degrees. I should be outside or something. Like the nerd I am, this Navy Chief is hard at work. Albeit, in shorts and no shoes or socks since I am at home. Anyway, I took a quick look at the forms at PowerShell.com and noticed the stream about having bold face type in the ISE. I like the PowerShell ISE. It is fast and simple. That also means that it is light on the bells and whistles.

I also use Sapien’s PowerShell Studio 2015 so I decided to publish out one of my personal settings. Take a look at the Font and Color settings below.

The item is Unknown Command it is also the only item with a background color other that the editors background, which for me is black. I normally use TAB completion heavily, but I also do some weird stuff where TAB completion is not the best idea. So, every once and a while, I make a typo. Having the Unknown Command highlighted so dramatically really helps to alert me when I make that rare typo (insert rolling of the eyes). Anyway, as for that question on PowerShell.com, take another look at the image. You can select to have different items in the editor as bold face. See below for my highlight.

It stands out.

Comments

June Blender said…

Great idea, Jason! I just changed my settings to match.

April 10, 2015 at 5:53 PM

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