Skip to main content

A Good Reason to Take an Instructor Led Class

By
I am doing my final checkout of my code for my evening session with Jaap Brasser for next week’s PowerShell Conference Asia.  Microsoft released Windows Server 2016 last week and all of us are rebuilding our test environments and validating our code with the final product.  While doing my thing, I received an email notification from the  IDERA community from someone new to PowerShell.  They were having some difficulty getting the distinguished names of their clients from Active Directory.  First off, for someone who is new to PowerShell, the code they posted is intense:

Function Get-ComputerFromAD
 {
  param(
   $ComputerName
  )
 
 
  ForEach ($Domain in $Global:ADDomains)
  {
   $LdapPath = "LDAP://OU=Computers,OU=GPWS,DC=$Domain,DC=xxx,DC=com"
   [System.DirectoryServices.DirectorySearcher]$Searcher = $LdapPath
   $Searcher.Filter = "(&(objectCategory=computer)(cn=$ComputerName))"
   $Searcher.SearchRoot = $LdapPath
   $Searcher.SearchScope = "Subtree"
   $Searcher.PageSize = 1000
  
   $PropertiesToLoad = "objectClass","cn","description","distinguishedName","operatingSystem","operatingSystemVersion","operatingSystemServicePack","dnsHostName","lastLogonTimeStamp","whenCreated"
   foreach ($property in $PropertiesToLoad) { $Searcher.PropertiesToLoad.Add($property) | Out-Null }
   
   $ADResult = $Searcher.FindOne()
  
   if ($ADResult -ne $null)
   {
    return $ADResult
   }
  }
 
  return $null
 }

That is really awesome for someone who is new.  The problem is that this wheel has already been invented.  To get the distinguished name of a client in Active Directory, you simply need to use the Active Directory Module for Windows PowerShell.  Here is the command:

 Get-ADComputer -filter * | Select-Object -ExpandProperty DistinguishedName

After 5 days of my PowerShell classes, I routinely get comments like:
  • ·         I would have never figured that out on my own.
  • ·         I read the entire book and could not understand it until I listened to you.
  • ·         I’ve tried to understand this for a month, you taught it to me in an hour.

The internet is great, but you just cannot beat an interactive class with an instructor who knows there stuff.  Give your local Microsoft Training Partner a call and ask them to place you in a  PowerShell class in your area. If you want me to be your instructor, just ask them to contact me.  Let me help you invest your time wisely and get you well on your way to being a PowerShell rock star.  

That command took me 10 seconds.  Image the time that I can save you.


Labels:

Comments

Post a Comment

Popular posts from this blog

Sticky Key problem between Windows Server 2012 and LogMeIn

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

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?

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