Controlling the Auto-Insert Features of SAPIEN PowerShell Studio

For those of you who take my PowerShell classes, you know that I close my curly braces {} when I open them. I have a slight tendency to forget to do this and then we all get to see the errors. Hey, I’m human. When it comes to single and double quotes, I’m usually pretty good at remembering to do this. In SAPIEN PowerShell Studio, you can control the auto-insert of these various characters.

When you type on of the following in SAPIEN PowerShell Studio, it is automatically closed for you.

‘

“

(

{

[

For many, this is a nice feature. For me, the part that I do not like this when I am working with strings. To fix this, open the Options window from the Home tab

Now just un-check Auto-insert closing string quotes

You can also see that you have the ability to turn off the auto insert for parentheses, square brackets, and curly braces.

Properly customizing the environment to your personal style will greatly increase the efficiency of your coding. Take the time to familiarize yourself with the Editors options so you can make the most of your coding experience.

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