New class added: 50025 PowerShell for Administrators

After a few requests, I'm finally adding PowerShell into my class lineup. Some of you have already noticed that I'm posting PowerShell tips on Tuesdays. I figured that it is time to start teaching it as well. I've been writing administrative scripts for 5 years now. PowerShell is a clear improvement on VBScript. In one of my future Tuesday postings you will see how a 75 line VBScript was written in just 6 lines in PowerShell. Now that is something!

In this class we will look at some key aspects to get you off and scripting in PowerShell. We will cover the environment, Syntax and logic, and how to make your life a little bit easier.

I'll be instructing this class on September 9th 2009 at ENS Group in Fort Wayne, IN. Give Dave Shriner a call and let him you are interested in this three day class.

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