Skip to main content

Set forest and domain modes with PowerShell

Both the domain and forest functional modes in a Windows domain will determine what functionality that you get.  When you purchase a new Windows Server OS, it comes with more advanced functionality than the previous version.  Some of that functionality may not be compatible with previous versions of the server OS.  In order to raise the functional level to say, Windows Server 2008, you need to upgrade all your domain controllers to a minimum of Windows Server 2008.  You can still have Windows 2000 and 2003 member servers, just not as domain controllers.

You can use PowerShell to raise both your functional levels.  Here is an example of how to raise both levels to Windows Server 2008 R2.

Open PowerShell
Import-Module ActiveDirectory
Set-ADDomainMode –Identity (Get-ADDomain) –DomainMode Windows2008R2Domain
Set-ADForestMode –Identity (Get-ADDomain) –DomainMode Windows2008R2Forest

The valid values are:

ID Domain Forest
0 Windows2000Domain Windows2000Forest
1 Windows2003InterimDomain Windows2003InterimForest
2 Windows2003Domain WIndows2003Forest
3 Windows2008Domain Windows2008Forest
4 WIndows2008R2Domain Windows2008R2Forest

Comments

Popular posts from this blog

How to list all the AD LDS instances on a server

AD LDS allows you to provide directory services to applications that are free of the confines of Active Directory.  To list all the AD LDS instances on a server, follow this procedure: Log into the server in question Open a command prompt. Type dsdbutil and press Enter Type List Instances and press Enter . You will receive a list of the instance name, both the LDAP and SSL port numbers, the location of the database, and its status.

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.

Where did a User’s Account Get Locked Out?

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