How to read Help Files (Part 1 of 7)

Every job has a mission critical skills that you need to master to perform your duties. An airline pilot needs to master the safe landing. A surgeon must master the usage of a scalpel. You, as a PowerShell coder must master the reading of the help files.

Reading help files is a regular them on my blog. I receive a lot of request for help. Not only from moderating the forums on PowerShell.com, but I also get contacted out of the blue for consulting. I look at the code that was generated and I sometimes just want to say “What were you thinking?” I think that because of mistakes that reading the help files would have prevented from happening.

Normally not reading the help files is due to either a lack of knowledge about the help files or just a plain lack of motivation. I cannot do anything about an individual’s motivation level, but I can help with the knowledge part. The PowerShell help system is very robust. In this series, I plan on walking you through a detailed, step-by-step guide on how to use the help system.

Since PowerShell V3, we have had updatable help. That means that you must update the help system before it provides you with any real information. To do this, open PowerShell as an Administrator and execute the command Update-Help. I suggest doing this in the shell. You can do this in the ISE, but it takes longer. Update-Help uses your internet connection to download the help files for all modules stored in the locations specified by $env:PsModulePath. To see these locations:

$env:PSModulePath.Split(“;”)

PS C:\> $Env:PSModulePath.Split(";")

C:\Users\JASON\Documents\WindowsPowerShell\Modules

C:\Program Files\WindowsPowerShell\Modules

C:\WINDOWS\system32\WindowsPowerShell\v1.0\Modules\

C:\Program Files (x86)\Microsoft SDKs\Azure\PowerShell\ServiceManagement

If you install a new feature or software that has a PowerShell module, you will need to run Update-Help once again. Update-Help will only update once every 24 hours so you may have to run

Update-Help –Force

Tomorrow we will look at the basic help file.

Comments

Sticky Key problem between Windows Server 2012 and LogMeIn

This week I instructed my first class using Windows Server 2012 accessed via LogMeIn and discovered a Sticky Key problem every time you press the Shift key. Here is my solution to resolve this. First off, in the Preferences of LogMeIn for the connection to the Windows Server, click General . Change the Keyboard and mouse priority to Host side user and click Apply at the bottom. On the Windows 2012 server, open the Control Panel – Ease of Access – Change how your keyboard works . Uncheck Turn on Sticky Keys . Click Set up Sticky Keys . Uncheck Turn on Sticky Keys when SHIFT is pressed five times . Click OK twice. If you are using Windows Server 2012 as a Hyper-V host, you will need to redo the Easy of Use settings on each guest operating system in order to avoid the Sticky Key Problem. Updated Information: March 20, 2013 If you continue to have problems, Uncheck Turn on Filter Keys .

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...

Backup and Restore AD LDS with DSDBUTIL.exe

Active Directory Lightweight Directory Services allow you to create a directory service that allows applications to have access to user accounts, groups, and authentication similar to Active Directory Domain Services. The big advantage here is that the schema of the directory service will not be bound by the rules of an Active Directory database. Exchange 2007/2010, for example, use an instance of AD LDS on the Edge Transport Server to provide for user authentication from the internet. Because your Active Directory database is not exposed to the internet, this is more secure. Applications will handle most of the dirty work should they require AD LDS. You may want to make sure the database is being backed up and also have a restore plan in place. Should the database become corrupt, the application that uses that database will fail. This document will walk you through backing up and restoring an instance of AD LDS using the dsdbutil.exe command. Fi...

Jason Yoder, MCT

Search This Blog