Bug 14608 - Add possibility to upgrade from Schema Version 30 (Windows 2003) to 47
Summary: Add possibility to upgrade from Schema Version 30 (Windows 2003) to 47
Status: NEW
Alias: None
Product: Samba 4.1 and newer
Classification: Unclassified
Component: AD: LDB/DSDB/SAMDB (show other bugs)
Version: 4.13.3
Hardware: All All
: P5 normal (vote)
Target Milestone: ---
Assignee: Samba QA Contact
QA Contact: Samba QA Contact
Depends on:
Reported: 2021-01-06 09:35 UTC by Carsten Menke
Modified: 2021-01-06 11:54 UTC (History)
1 user (show)

See Also:

Upgrade Files schema 30 - 47 (27.48 KB, application/x-bzip2)
2021-01-06 09:35 UTC, Carsten Menke
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Carsten Menke 2021-01-06 09:35:22 UTC
Created attachment 16375 [details]
Upgrade Files schema 30 - 47

I guess there a more people beside me out there who have migrated a Windows 2003 Server once a long time ago to a Samba4 DC without doing a schema update on the Windows 2003 first.

The correct way would be to insert a Windows 2008R2 Disc in the Windows Server 2003 and running adprep to update the schema of the Windows 2003 server before you migrate the Windows Server 2003 to Samba. But if you've migrated the 2003 Server to Samba without doing this step, you are currently bound to Schema Version 30 without a chance to get the schema updated to the current supported schema of Samba.

I have manually updated my schema from Version 30 to 47 by extracting the LDF files from the Windows 2008R2 Disc and manually updated my schema to Version 47.

I'll attach the modified LDB files and the script need to apply them to this report. I think we should include this in share/docs/samba4/setup folder so that one has at least a starting point who is in the same situation without reinventing the wheel.

Christophe Borivant has done the work for the files from version 31 - 47 (so the credits go to him). I've added the modifications to go from Version 30 - 31