Restore W2K after partial upgrade to W2003 - schema mismatch

Archived from groups: microsoft.public.win2000.setup_upgrade (More info?)

I am currently working in our test lab verifying the upgrade to W2003 and
checking that we can recovery back to W2K if any problems occur.

My problem is that I do not seem to be able to restore the W2K system state
data and replicate this to the rest of the domain after carrying out adprep
/forestprep and domainprep.

Tasks carried out were.
1. Move all FSMO roles onto one server.
2. Carry out full back up of this server.
3. Carry out the inetOrgPersonfix changes for our Exchange 2000 installation
4. Run adprep /forestprep and check that it has replicated.
5. Run adprep /domainprep and check that it has replicated.
At this point AD has a couple of Windows2003update containers and the
registry has the schema version as 30

I now want to restore this back to the point where the backup was carried
out. So I
6. Boot the server up into directory restore mode
7. Restore the system state data
8. Go into ntdsutil and carry out an authoritative restore and increment
the version by 100000.
9. Checked AD and the registry - Windows2003update containers gone and the
schema version in the registry is back to 13 -> I'm happy that this DC is
restored.
10. Boot it up normally and within a few minutes the server is back at
schema version 30. It has been updated from the other domain controllers.

I have repeated the process several times using much larger USN version
increments during the authoritative restore but with no success. I have also
disabled inbound replication and tried to push the version 13 schema out on
to the other DCs but get a schema version mismatch error.

I would seem that schema version overrides the USN version in determining
the direction of replication. ie AD will always replicated from the higher
schema version irrespective of the USN version numbers. I do not want to
muck about with the schema version number as this could completely screw up
AD.

Any one any ideas how to restore back to W2K?

Cheers,

Doug