Navy Chief Aiding the Marines with PowerShell

I love this job. I’m not only talking about what I do in the civilian world as an IT Trainer, but also as a Navy Chief Petty Officer. I received a Facebook message from a Marine at Camp Pendleton a few nights ago in need of some assistance with PowerShell. Below is his line of code and his error

Get-User -organizationalunit test.local.net/users -RecipentTypeDetails

Get-ADUser : A parameter cannot be found that matches parameter name 'organizationalunit'.

At line:1 char:12

+ Get-ADUser -organizationalunit PowerIT.com/users

+ ~~~~~~~~~~~~~~~~~~~

+ CategoryInfo : InvalidArgument: (:) [Get-ADUser], ParameterBindingException

+ FullyQualifiedErrorId : NamedParameterNotFound,Microsoft.ActiveDirectory.Management.Commands.GetADUser

Being both a PowerShell enthusiast and a Navy Chief, I helped him see what was wrong with his code, but I also had to correct his bad habits.

The error on Get-ADUser is because there is not an –OrganizationalUnit parameter. (there is also not a –RecipentTypeDetails parameter.) I directed him to look up the help file for Get-ADUser and I gave him the address (https://technet.microsoft.com/en-us/library/ee617241.aspx). I even told him the correct parameter name, –SearchBase.

The root cause of the error is this Marine is have is “assuming” parameter names and not actually looking them up. I find this in every PowerShell class that I teach. Despite the first lesson of each class explains how to prevent you from making this mistake, someone always does. Never assume a parameter is present. Check the help file for the Cmdlet being used and verify.

The correction came when he did the same thing again for his next cmdlet. PowerShell is an incredible technology, but if you are not willing to read the help files, do not work in this Chief’s work center. Reading the help files is not an option, but a requirement to effectively utilize PowerShell.

Comments

With the AD Recycle Bin Turned on, What Happens when you Create a User Account with a Password that does not meet the Password Policy?

This was an interesting observation from one of my Windows Server 2012 classes. While working with the AD Recycle bin in a lab, one of my students discovered some interesting accounts that were created. When he created user accounts that did not meet password complexity requirements, an account is temporarily made and then deleted. When a new password is provided that meets the password requirements, then a new account is made. We discovered this in two places. First off in the Active Directory Administrative Center. This is what caused the initial confusion. Take a look. This is in the Deleted Objects OU. You can see multiple deleted accounts for Test2 and one for Test3. Test3 is a valid, functioning user account. Using the PowerShell command Get-ADObject –IncludeDeletedObjects –Filter * –Properties ObjectSID we can see that indeed, two accounts were created, with one of them deleted. Notice the RID portion of the SID is different. ...

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 .

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