Blog Post

Exchange Team Blog
2 MIN READ

Please DO NOT install Beta versions of Exchange 2007 SP1 into your production environment!!

The_Exchange_Team's avatar
The_Exchange_Team
Platinum Contributor
Aug 29, 2007

Seeing that I work closely with Exchange Support Services group, I have yesterday heard of a 2nd instance where a customer has installed Exchange 2007 SP1 Beta 2 in their production environment.

It seems it is time for a reminder:

If you have access to an Exchange 2007 SP1 build, DO NOT install it into your production environment. Also realize that Exchange 2007 SP1 will extend your Active Directory schema.

Just to give you a little bit more information: with our TAP customers, we go through a very specific process to make sure that there are no issues when Beta builds of Exchange are joined into production. Exchange 2007 SP1 is Beta code. As such, it has not been extensively tested in all possible configurations and results of installing it into the existing Organization can lead to unexpected results.

We want to strike a balance between releasing early builds so that our customers can see the product and give us feedback and ensuring that our customers have a good experience with the product. When our instructions about an early build being for testing only are ignored, customers can have a bad experience and it makes it harder for us to decide to release early builds because we don't want those situations to happen.

What you of course can do, is install Exchange 2007 SP1 in the lab and test it there... you can test coexistence too (meaning, having Exchange 2003 servers in the same Org) but this should be in your labs only. We also provided ability to test-drive Exchange 2007 in other ways.

Please be patient. We know that many are waiting for their favorite SP1 features, but it is not the time yet to roll this into production!

- Nino Bilic

Updated Jul 01, 2019
Version 2.0

24 Comments

  • Thanks for the pointer to the release notes... I hadn't read them for the beta yet (and justifiably, because I hadn't installed it anywhere!)  Given that the install/upgrade updates the schema, thus requiring Schema Admin for the AD, it's even more shocking that it has been 'accidentally' installed in production!  Perhaps to protect more against this, there should be an extra screen in the setup that appears, when the product version = a beta, requiring one last extra acknowledgement that you're installing it in a lab or are a TAP customer.

    Having read the release notes now, I noticed there's at least one new thing, the default disabling of streaming backup, that's also using a registry key.  I don't know if this suggestion could be taken into consideration at this point in the beta, but it would be nice (even though it could be considered trivial to add a given registry key) if this was also available in powershell (Enable-RemoteStreamingBackup?)  Perhaps that could just be a .ps1 script that adds the registry key... in any case this would keep with the theme of relatively self-documenting, scriptable, powershell commands that encompass everything that can be done or configured in Exchange server.
  • Robert,


    I would advise against it. Even though I have never heard of a problem created by E2007 Sp1 Schema extensions, it is still not a good idea as it is still beta.



    KB,


    We do not have a lot at this time (we will have this in the SP1 documentation though when time comes) - but Release Notes do mention this too:



    http://www.microsoft.com/downloads/details.aspx?FamilyID=5770bd59-376e-42ec-b940-be6225cd97ff&DisplayLang=en

  • 2007 SP1 updates the schema of a 2007 org?  Are there any details published about this?
  • What is your view on using the Beta 2 code to ONLY update the production AD schema? Has the schema been locked down in the beta code?