Enable Database 32k pages optional feature in Active Directory Domain Services

Anonymous
2024-11-18T17:14:24+00:00

In my lab I upgraded all DC to Win2025 and update forest and domain level to 2025 but when I try to enable database 32K received below error.

PS C:\Users\da_tmichalek> $params = @{

Identity = 'Database 32k pages feature' 

Scope = 'ForestOrConfigurationSet' 

Target = $forestname 

}

Enable-ADOptionalFeature @params

WARNING: Enabling 'Database 32k Pages Feature' on 'CN=Partitions,CN=Configuration,DC=TMICHALEK,DC=PL' is an irreversible action! You will not be able

to disable 'Database 32k Pages Feature' on 'CN=Partitions,CN=Configuration,DC=TMICHALEK,DC=PL' if you proceed.

Enable-ADOptionalFeature : The Active Directory JET database page size does not match on all Domain Controllers in this forest

At line:6 char:1

  • Enable-ADOptionalFeature @params
  • 
        + CategoryInfo          : NotSpecified: (Database 32k pages feature:ADOptionalFeature) [Enable-ADOptionalFeature], ADException 
    
        + FullyQualifiedErrorId : ActiveDirectoryServer:8660,Microsoft.ActiveDirectory.Management.Commands.EnableADOptionalFeature  
    
    

PS C:\Users\da_tmichalek> Get-ADObject -LDAPFilter "(ObjectClass=nTDSDSA)" -SearchBase "CN=Configuration,DC=TMICHALEK,DC=PL" -properties msDS-JetDBPageSize |

Format-List distinguishedName,msDs-JetDBPageSize

distinguishedName : CN=NTDS Settings,CN=TMDC12,CN=Servers,CN=TM-KRK,CN=Sites,CN=Configuration,DC=TMICHALEK,DC=PL

msDs-JetDBPageSize : 8192

distinguishedName : CN=NTDS Settings,CN=TMDC11,CN=Servers,CN=TM-KRK,CN=Sites,CN=Configuration,DC=TMICHALEK,DC=PL

msDs-JetDBPageSize : 8192

distinguishedName : CN=NTDS Settings,CN=SLEDC12,CN=Servers,CN=TM-SLE,CN=Sites,CN=Configuration,DC=TMICHALEK,DC=PL

msDs-JetDBPageSize : 8192

distinguishedName : CN=NTDS Settings,CN=SLEDC11,CN=Servers,CN=TM-SLE,CN=Sites,CN=Configuration,DC=TMICHALEK,DC=PL

msDs-JetDBPageSize : 8192

Can you help me?

Windows Server Identity and access Active Directory

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question. To protect privacy, user profiles for migrated questions are anonymized.

0 comments No comments
{count} votes
Accepted answer
  1. Anonymous
    2024-11-19T07:06:40+00:00

    Hi TomaszMichałek,

    Thank you for posting in the Microsoft Community Forums.

    Based on the error message you provided, you are experiencing problems when trying to enable the Database 32k Page Feature in an Active Directory forest. The error indicates that the Active Directory JET database page sizes on all domain controllers (DCs) in this forest do not match and are currently 8192 bytes (i.e., 8K) instead of the required 32K.

    Enabling the 32K database page size is an irreversible operation that requires all DCs in the forest to use the same page size. If an attempt is made to enable this feature with inconsistent page sizes, the operation will fail because Active Directory needs to ensure that the database structure is consistent across all DCs to maintain data integrity and synchronization.

    Solution Step:

    Confirm the requirement:

    Ensure that you do need to upgrade to a 32K page size. This is often done to support larger objects or to improve performance, but may also create additional resource requirements (such as more disk space).

    Back up your data:

    Before making any changes, make sure you have backed up the Active Directory database and system state on all DCs.

    Unify page sizes:

    You need to change the database page size to 32K on all DCs. this usually involves reinstalling or reconfiguring Active Directory on each DC because once a database is created, its page size cannot be changed.

    One method is to use DCPROMO (Domain Controller Upgrade Wizard) to downgrade the DC (if possible), change the page size setting, and then re-upgrade it to a DC. However, this method may result in data loss or service interruption, so it should be used with caution and make sure you have a full backup.

    Another safer method is to add new DCs, configure them to use 32K page sizes, then transfer the roles on the existing DCs to the new DCs, and finally deprecate the old DCs.

    Test environment:

    Verify the entire migration and upgrade process in a test environment before implementing in a production environment.

    Best regards

    Neuvi

    0 comments No comments

0 additional answers

Sort by: Most helpful