Skip to main content

Get-ADDomainController - AD Cmdlets Reference

Get-ADDomainController

Get-ADDomainController is useful to easily return all, or a subset of your domain controllers.  This can be easily filtered by type, OS, AD Site, or a number of other values.

Example usage


#get all read only DC's
Get-ADDomainController -filter {isreadonly -eq $true}
# get the domain controller DC1
Get-ADDomainController -identity "DC1"
# get the PDCE for the domain
Get-ADDomainController -Discover -Service "PrimaryDC"}
# get a GC but force it to rediscover (clear any cached DC)
Get-ADDomainController -Discover -Service "GlobalCatalog" -ForceDiscover



Define the parameters

Identity takes a range of identifiers for the object. These include "Distinguished Name", "GUID", "SID", and "samaccountname".

Service takes the following :
PrimaryDC or 1
GlobalCatalog or 2
KDC or 3
TimeService or 4
ReliableTimeService or 5
ADWS or 6

Filter uses the format {isreadonly -eq $true} against most of the object properties.

There are more options, use get-help cmdlet for all options

In a script

For each Read / Write DC, tell me how much memory the lsass process is using in Mb.
foreach ($RWDC in $(Get-ADDomainController -filter { isreadonly -eq $false })) {
   $lsass = get-process -ComputerName $rwdc.name -Name lsass
   "Current memory usage for lsass on $($rwdc.name) is $($lsass.WorkingSet / 1mb)Mb"
}

Powershell without the Management pack
I have covered How to find a GC, here are some others :

#get all DC's in the domain
$domain = [System.DirectoryServices.ActiveDirectory.domain]::getcurrentdomain()
$Domain.FindAllDomainControllers()

#read only DC's
#search AD for DC's with a primary group ID of 521
#or get memebers of the group "Enterprise Read-only Domain Controllers"

#get pre-staged RODC objects
#search AD and filter DC's for useraccountcontrol value of 83890178


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…