I need to update the AD schema for Exchange or SharePoint and don't want to do it alone.
Schema updates touch the whole forest and cannot be rolled back. Routine if you prepare: backup, tested media, single Schema Master, done at a quiet time.
Try this first
- 1Back up the Schema Master (DC holding that FSMO role): system state or a full VM snapshot. Not for hope of rollback, but as insurance.
- 2Run setup /PrepareSchema (or /ForestPrep) from the Exchange/SharePoint media on the Schema Master, with an account in Schema Admins and Enterprise Admins.
- 3Verify with repadmin /showrepl and Event Viewer that replication to other DCs works after the schema change. Force with repadmin /syncall if needed.
- 4Only then install Exchange or SharePoint on its server. Schema and install are two separate steps.
- 5Document the schema version (Get-ADObject 'cn=schema,cn=configuration,...' rangeUpper) so you can tell later what changed.
When to bring us in
An Exchange schema update in a multi-domain forest needs /PrepareDomain in each domain afterwards. Don't skip, or you get strange lookup issues months later.
See also
- One DC or two DCs for an SMB office?Two is almost always the right answer; one DC is a single point of failure for logon, DNS and GPOs.
- Should I split FSMO roles across two DCs?For a small domain all on one DC is fine; with two DCs splitting is tidier but not required.
- How do I know my AD replication is healthy?Replication errors creep in silently; they only surface when logins or GPOs misbehave.
None of the above fits?
Describe your situation below. We pass your input plus the steps you already saw to our AI and return tailored next-step advice. If it's too risky to DIY, we'll say so.
Or skip the DIY entirely
Our Managed IT clients do not look these things up. One point of contact, a fixed monthly price, resolved within working hours.