Skip to main content

How to get the FSMO roles in PowerShell

Even though our domains are multimaster domains, not all functionality can be handled by each machine independently. For example, let’s take a look at the RID Master role.

And RID is what uniquely identifies all security objects in a domain. A security object is either a user, computer, group, or INetOrgPerson. Each of these objects have a Security Identifier (SID). A SID looks like this:

S-1-5-21-576790344-2948317706-4057815606-1702

To break this down:

S

The string is a SID

1

The revision level

5

The identifier value. Possible identifier authority values are:

0 – Null Authority

1 – World Authority

2 – Local Authority

3 – Creator Authority

4 – Non-unique Authority

5 – NT Authority

9 – Resource Manager Authroity

576790344-2948317706-4057815606

Domain or local computer identifier

Relative Identifier (RID). This is unque in the domain.

1702

   

Active Directory uses the SID to identify an object that can have security access assigned to it. You and I use the user name. the username name maps to a SID with the RID portion being unique in the domain. If two domain controller are handing our RIDs to new objects, there is a chance that two objects could get the same SID. This would allow the two different users to have the same access as the other one. With the RID Master being a single domain controller, this cannot happen.

The easiest way to discover the FSMO (Flexible Single Master Operation) roles was to use NETDOM Query FSMO.

clip_image001

If you need to discover these roles in a PowerShell script, this would be difficult as the information is returned as a string of text. To execute the below PowerShell commands, you must do this on a client or server with the ActiveDirectory module installed.

Import-Module ActiveDirectory

$FSMOObj = New-Object PSObject
# Retrieve the Schema Master
$FSMOObj | Add-Member -MemberType NoteProperty -Name "Schema" -Value (Get-ADForest).SchemaMaster
# Retrieve the Domain Naming
$FSMOObj | Add-Member -MemberType NoteProperty -Name "DomainNaming" -Value(Get-ADForest).DomainNamingMaster
# Retrieve the PDC
$FSMOObj | Add-Member -MemberType NoteProperty -Name "PDC" -Value(Get-ADDomain).PDCEmulator
# Retrieve the Infrastructure Master
$FSMOObj | Add-Member -MemberType NoteProperty -Name "Infrasturcture" -Value(Get-ADDomain).InfrastructureMaster
# Retrieve the RID pool manager
$FSMOObj | Add-Member -MemberType NoteProperty -Name "RID" -Value(Get-ADDomain).RIDMaster

#Send the object to the Pipeline.
Write-Output $FSMOObj

This will send objects into the PowerShell pipeline that you can use in your code.

Comments

Popular posts from this blog

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

How to run GPResult on a remote client with PowerShell

In the past, to run the GPResult command, you would need to either physically visit this client, have the user do it, or use and RDP connection.  In all cases, this will disrupt the user.  First, you need PowerShell remoting enabled on the target machine.  You can do this via Group Policy . Open PowerShell and type this command. Invoke-Command –ScriptBlock {GPResult /r} –ComputerName <ComputerName> Replace <ComputerName> with the name of the target.  Remember, the target needs to be online and accessible to you.

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 .