Like Exchange 2007 Service Pack 1, Exchange 2007 Service Pack 2 is a slip-streamed version. Exchange 2007 Service Pack 2 introduces several new features, but in order to utilize Exchange 2007 SP...
Published Aug 28, 2009
Version 1.0
Blog Post
@Franc
It is best practice to split up Schema Admin and Exchange Admin roles, so you would typically have your schema person do the extension, and then you do the install. The GUI is suitable for shops that do not follow this best practice.
@Richard
It is best practice to have all of your exchange servers running the same service pack level. However if you do not do this you shouldn’t experience any problems.
@Liam
I am not sure why Microsoft supports some things and not others. I wonder if maybe exchange 2010 makes schema extension decisions based on the presence (or lack thereof) of older exchange servers. Meaning the environment isn’t suitable for older versions of exchange if they weren’t first there. This support model is the same for Exchange 2007 and 2000/3 as well, so I am not surprised to see this.
It is best practice to split up Schema Admin and Exchange Admin roles, so you would typically have your schema person do the extension, and then you do the install. The GUI is suitable for shops that do not follow this best practice.
@Richard
It is best practice to have all of your exchange servers running the same service pack level. However if you do not do this you shouldn’t experience any problems.
@Liam
I am not sure why Microsoft supports some things and not others. I wonder if maybe exchange 2010 makes schema extension decisions based on the presence (or lack thereof) of older exchange servers. Meaning the environment isn’t suitable for older versions of exchange if they weren’t first there. This support model is the same for Exchange 2007 and 2000/3 as well, so I am not surprised to see this.