Skip to main content

Hash Tables - DC operating systems

I have been meaning to get my head around a lot of different aspects of powershell, one of which is hash tables.  As we are currently going through a DC upgrade, I wanted to know how many DC's we had of each different operating system.  I wondered if hash tables would help me.

First, I got all DC's in my domain : 

$DClist = get-ADDomainController -server domain.com -filter {enabled -eq $true}
You may notice the get-ad portion of the command....this means that this command runs only on powershell 2 when connected to an Windows 2008 R2 DC or a 2003 / 2008 DC with ADMGS installed. 


So, $DCList is now all the DC's from domain.com (-server domain.com) that are set to enabled (-filter {enabled -eq $true}). 


NOTE: The only DC's that are not enabled are pre-staged RODC accounts ... by that i mean accounts that have been created but the server has not come online yet.  These servers do not have any OS information in them anyway. It is more helpful to filter these when you want to query the online servers later as is only wastes processing power trying to query a server that doesn't really exist yet!.  You can also do -filter {isreadonly -eq $false} to just get read write DC's.

So how do we use hash tables to count all the different os types? First we need to declare a variable as an empty array.

$OSlist = @{}

Next, we pass the operatingsystem attribute via foreach to $oslist AS A NEW ATTRIBUTE. At the same time we want to increment that attribute by 1. The way powershell works is that if the attribute doesn't exist, it will create it prior to adding 1 to it. If it is there, it will increment the existing value.

$DClist | foreach {$OSlist.$($_.operatingsystem) ++}
$DClist | - pass $dclist through the pipeline

foreach { - the foreach statement

$oslist. - accessing an attribute in the variable $oslist

$($_.operatingsystem) - the evaluation of the value of $_.operatingsystem

++} - increment the value $oslist.$($_.operatingsystem) and close the foreach.

for example, if the $($_.operatingsystem) value is the first instance of "Windows 2008 R2", this process will create an attribute in $oslist called "Windows 2008 R2" and then increment it by 1. As it doesn't have a value or a type, powershell assumes it is a number and and the value becomes 1.

At the end of the process, you have attributes corresponding to all the OS's in your environment (no more, no less) and a count of each in 3 lines of code.  Sweet.

$DClist = get-ADDomainController -server domain.com -filter {enabled -eq $true}
$OSlist = @{}
$DClist | foreach {$OSlist.$($_.operatingsystem) ++}

Comments

Popular posts from this blog

PowerShell 3 behavioural change

It's taken me way too long to get into PowerShell 3, I guess opportunity hasn't shown it's self until now and so, here, my V3 journey begins.

I was asked to debug a script that would run fine in PS v2 and not in v3.  The issue was a that a variable length was being checked and was failing in v3.  This is why...

In v2 if a variable is undefined, this test returns false

PS C:\windows\system32> $var.length -eq 0
False

In v3 the same test returns true....

PS C:\windows\system32> $var.length -eq 0
True

Not a biggie, but as in this case, a script has broken so something to consider!

cheers

Adam

Enable Powershell Remoting (WinRM) via Group Policy

I have been doing some testing on enabling WinRM via group policy, being that WinRM is the service that Powershell v2 sets up it remoting capabilities. Here are the GPO settings that you need to configure WinRM ....


set the winrm service to auto start


Computer Configuration \ Policies \ Windows Settings \ Security Settings \ System Services


Windows Remote Management (WS-Management)  set Startup Mode to Automatic

start the service


incorporated in to the above - you may need a restart.


create a winrm listener


Computer Configuration / Policies / Administrative Templates / Windows Components / Windows Remote Management (WinRM) / WinRM Service / Allow automatic configuration of listeners


IPv4 filter: *


* is listen on all addresses, or if you only want a particular IP address to respond use an iprange eg 10.1.1.1-10.1.1.254 - don't forget that this IP range has to be valid for all hosts that fall in the scope of the GPO you are creating.  You can use 10.1.1.1 - 10.1.1.254,10.1.1.3 - 10.1.4.254 …

compare-object in Powershell - comparing mulitple values

I'm starting to use compare-object more and more, and one thing I noticed, is that you can compare 2 objects based on multiple attributes. here is how it is constructed...
Compare-Object -ReferenceObject $object1 -DifferenceObject $object2 -Property a,b,c,d,eIf a,b,c and d are the same, but e is different, compare object will return a difference. In the following example, I use "-eq $null" as a check because by default compare-object returns $null if the objects are the same.
#create an array of objects to check against

$collection = @()
foreach ($entry in ("aaaaa","bbbbb","ccccc","ddddd")){
   $store = "" | select "a","b","c","d","e"
   $store.a = $entry*1
   $store.b = $entry*2
   $store.c = $entry*3
   $store.d = $entry*4
   $store.e = $entry*5
   $collection += $store
}

#create an object similar to those in the array
$object = "" | select "a","b…