Exchange 2010 Schema was back ported to Exchange 2007 SP2, but why are files different?


It was mentioned before that Exchange 2007 SP2 contained Exchange 2010 schema completely back ported to it, but if you check the LDF files that generate the schema you may notice that they are in fact different.

Back porting the schema was not a straight forward action code wise. In order to do it, we had to add some of the properties that were in a separated file in Exchange 2010 to all the *99.ldf files in Exchange 2007 SP2. This is why you may notice that there are differences in the files that generate the schemas in between the 2 versions.

However, this change has no impact on what happens when you install E2007 SP2. Schema versions are synchronized and after installing it, the schema in your environment will be that of Exchange 2010.

Mario Trigueros Solorio


Comments (3)
  1. Pedro Acosta says:

    Nice to know that, I am running the beta of exchange 2010 for about 45 days in my test enviroment, some changes are very visible.

    I’ll comment more within the next few weeks as time permit.

    thanks

  2. Petri says:

    I never understood why there were such rush to E2010 schema. This was one result from the rush..

  3. John says:

    I understand the Exchange 2010 schema changes are included in Exchange 2007 SP2. If SP2 has been installed, is the Exchange 2010 Setup /PrepareSchema still required to be run to prepare AD for Exchange 2010, or can this be skipped?

    If so, can you provide some details on why this is required, or more specifically what is done? Assuming the schema updates already exist (via SP2), is PrepareSchema required to validate the schema version or are there additional (non-schema extension changes) implemented by the Exchange 2010 PrepareSchema in an existing Exchange 2007 SP2 org?

Comments are closed.