Skip to main content

The Importance of TAB Completion

By

I start both my PowerShell and Windows Server classes off with a basic lesson on PowerShell’s syntax. This lesson includes the importance of using TAB completion.  It never fails.  I always find someone who insist on typing everything.  Here are a few benefits of press the TAB key.

  1. Faster typing
  2. Less work
  3. Greater productivity
  4. Fewer typing errors
  5. No more using parameters that do not exists.
  6. No more using cmdlets that do not exists
  7. Less troubleshooting

All these sound like good reasons to press the TAB key, yet there are those that will not.  For those who want to type everything, this is what you are doing that the rest of the PowerShell community is not.

  1. Working hard
  2. More debugging
  3. Wasting time
  4. Making typos
  5. More frustration
  6. More stress
  7. Less productivity

Remember, every time you press the dash “-“ key, type one or two more characters and then press TAB. It will make your life easier. It is strange at first, but once that lught bulb turns on, you will not believe how much harder you were working before TA completion.

Labels

Labels:

Comments

Post a Comment

Popular posts from this blog

How to list all the AD LDS instances on a server

By
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.
Post a Comment
Read more

How to run GPResult on a remote client with PowerShell

By
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.
Post a Comment
Read more

Where did a User’s Account Get Locked Out?

By
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...
18 comments
Read more