Windows Server 2025 Domain and Functional Levels domainFunctionality and forestFunctionality attributes

The Active Directory domain and functional levels have changed for Windows Server 2025 with a new functional level being added.

However the documentation for the 3.1.1.3.2.26 domainFunctionality and 3.1.1.3.2.27 forestFunctionality attributes have not been updated.

https://learn.microsoft.com/en-us/openspecs/windows_protocols/ms-adts/6dd88965-8feb-4369-ae7e-075985da8071


0 DS_BEHAVIOR_WIN2000

1 DS_BEHAVIOR_WIN2003_WITH_MIXED_DOMAINS

2 DS_BEHAVIOR_WIN2003

3 DS_BEHAVIOR_WIN2008

4 DS_BEHAVIOR_WIN2008R2

5 DS_BEHAVIOR_WIN2012

6 DS_BEHAVIOR_WIN2012R2

7 DS_BEHAVIOR_WIN2016


The new value 

10 DS_BEHAVIOR_WIN2025


Notice there is a gap of two numbers for Server 2016 and Server 2019 that didn't have an update to the domain and forest functional levels.


In addition to this the .NET Framework classes have not been updated - both of these commands (shown in Windows PowerShell) return "Unknown" for the domain and forest modes.

[System.DirectoryServices.ActiveDirectory.Forest]::GetCurrentForest();
[System.DirectoryServices.ActiveDirectory.Domain]::GetCurrentDomain()


The PowerShell cmdlets however have been updated.

Get-ADDomain|SELECT DomainMode
Get-ADForest|SELECT ForestMode


If you need to determine the domain functional level without using the PowerShell cmdlets you can still use a directory entry and read the domain functionality property that corresponds to a value listed above. 

(New-Object DirectoryServices.DirectoryEntry "LDAP://domainname/RootDSE").Properties["domainFunctionality"];


If you need to determine the forest functional level without using the PowerShell cmdlets you can still use a directory entry and read the forestFunctionality property that corresponds to a value listed above. 

(New-Object DirectoryServices.DirectoryEntry "LDAP://forestname/RootDSE").Properties["forestFunctionality"];



 While you're here -
Why not check out our Active Directory Documentation Tool?




Comments

Post a Comment

Popular posts from this blog

Windows Server 2016, 2019, 2022, Windows 10 and Windows 11: Date and time "Some settings are managed by your organization".

Image
When you're using the new "Modern" date and time settings in Windows Server 2016, 2019, 2022, Windows 10 and Windows 11 you may find that you can't set the correct date and time and the value "Some settings are managed by your organization". - While you're here - Why not check out our Windows Server Documentation and Audit Tool? The simplest way around this is to go back to the proper control panel using Start, Run, "Control.exe" and searching for "Set the date".  Within here you can set the date and time manually as required If you try and click the Change time zone button you may again get access denied... To resolve this open an elevated command prompt by right clicking the command prompt and selecting Run as Administrator  From there run the command rundll32.exe shell32.dll,Control_RunDLL timedate.cpl This will open the Data and Time control panel app elevated as an Administrator.
Read more

TFTPD32 or TFTPD64 reports Bind error 10013 An attempt was made to access a socket in a way forbidden by its access permissions.

Image
When you start the trivial FTP (TFTP) server application TFTPD32 or TDTPD64 you may see the following error Bind error 10013 An attempt was made to access a socket in a way forbidden by its access permissions. This can be because another application is using this port. The easiest way to check if (and which) application is using the port is as administrator run an elevated command prompt and enter netstat -anb > ports.txt Then open ports.txt in Notepad and search for :69, you'll quickly be able to see the process using the required port - While you're here - Why not check out our Windows Server Documentation and Audit Tool?
Read more

When using the "Send to compressed (zipped) folder" context menu item nothing happens

Image
I've recently had a problem when using the "Send to compressed (zipped) folder" context menu item nothing happens on Windows 8.1. Looking further into this I found that it worked most folders just not the one I wanted to ZIP. After a while I realised that I had a Visual Studio project source code in this folder that had that annoy deep obj folder problem and it seems that when you click "Send to compressed (zipped) folder" if there is an exceptionally deep directory structure in the folder you are zipping the compression may fail but show now error. I use the following tried and tested RoboCopy method for removing these broken directories with exceptionally deep paths that you can't delete with Windows Explorer. @echo off cls mkdir emptyfolder robocopy emptyfolder "path\to\obj" /MIR rmdir emptyfolder rmdir "path\to\obj" pause  While you're here - Why not check out our Windows Server Documentation and Audit Tool?
Read more