Update Roll-up 7 for Exchange Server 2007 Service Pack 1 has been released.


*Note! Comments have been disabled for this post. To comment on this post, please visit the Exchange Software Updates forum which deals with issues encountered in updates we release for Exchange. We will be monitoring the forums every day to assist you in applying this roll-up. Thanks for keeping your servers updated to the latest and greatest to take full advantage of our cumulative servicing model!

We have released Update Roll-up 7 for Exchange Server 2007 Service Pack 1 (KB 960384) to the download center. The release of the roll-up via Microsoft Update will happen on March 24.

Yes, it has been only 5 weeks since we shipped the last update roll-up on February 10 and usually our gap between roll-ups is about eight weeks. Since the release of update roll-up 6, we have fixed about 50 issues and wanted to go ahead and provide them to customers. How did this happen in a short span of 5 weeks? I am not inflating the figures. Actually, the last roll-up was special since it included the fix for a security issue as described in Microsoft Security Bulletin MS09-003. The test pass for that roll-up lasted much longer since all security related updates released by Microsoft go through a Security Update Validation Program (SUVP). As part of this program, the security updates are made available to a limited group of customers to test before its release on a second Tuesday. More on this program can be found at the MSRC blog here. As a result we had a shorter time available for including fixes in that roll-up. This also ensured a lower risk for the roll-up since the amount of code churn was lower. Of course, all this meant that we had more time on our hands to work on the development and testing for this roll-up and we are now ready a little earlier.

Now for the part which I like! Announcing some of the important fixes included in this roll-up to improve the customer experience: 

  1. First off, we fixed the SCR issue which have caused everyone some pain and which did not get completed in time to be included in the last update roll-up.

    KB 961281 Update Roll-up 5 for Exchange Server 2007 Service Pack 1 introduced an issue where you receive an error when attempting to enable SCR on a storage group if the environment has a parent domain -> child domain active directory structure. Tim has blogged about this over here. This is now fixed.  Additionally, there are also 2 other SCR related issues which we have been addressed in this roll-up and have been asked for by many customers.

    KB 957834 Network shares are deleted and created intermittently by the replication service on an Exchange SCC cluster when SCR is enabled on the Exchange server

  2. KB 958331 Restore-StorageGroupCopy command may fail in an Exchange Server 2007 SCR environment.

  3. We have also fixed two issues which caused intermittent crashes in the IMAP4 service and resulted in event 4999 being logged in the event logs. The following KBs have more information on the scenarios which are fixed:  KB 957504 and KB 960292.

Additionally we have also done a design change to address encapsulation and the way it is handled by Exchange Server 2007. If you would like to read the official version of this design change, you can read KB 956069. Of course for a lighter and funnier perspective on this, I will recommend Jason’s blog post released as a run up to this roll-up release.

Oh! And I almost forgot. Thanks to the folks who helped provide service startup logs via the forums when they encountered an issue where some services would be left disabled after patch installation. The logs helped us identify a missed case when starting the MSExchangeTransportLogSearch  service which would happen in scenarios where the server has more than one Exchange role installed on it.

KB 960384 has more details about this release and a complete list of all fixes included in this roll-up.

And finally, from the installation perspective, a friendly reminder that the roll-up installer will overwrite any OWA script files if required to ensure proper operation of OWA. So if you have customized the logon.aspx page or other similar OWA pages, you will need to redo any customization after installation of the roll-up. I promise, this is the last time I will remind everyone via the blog.

By the way, we will be disabling comments on this blog post. We have the Exchange Software Updates forum which deals with issues encountered in updates we release for Exchange. We will be monitoring the forums every day to assist you in applying this roll-up. Thanks for keeping your servers updated to the latest and greatest to take full advantage of our cumulative servicing model!

Ananth Ramanathan


Share this post :

Comments (23)
  1. Exchange says:

    Would you like to comment on this post? Please visit the Exchange software update forums located here: http://social.technet.microsoft.com/Forums/en-US/exchangesoftwareupdate/threads/

    Thanks!

    Joey

  2. Slawek says:

    Hi, Will Exchange 14 support CalDAV?

  3. ML49448 says:

    This rollup just broke my OWA.

    Windows 2008 Exchange 2007 SP1, OWA not working, and I have no idea where to start to fix the issue… arg!

  4. Nathan - ASG says:

    I (and one other colleague in a different environment) have also run into an issue when installing Rollup7 on a Srv2008/E2007 SCC CMS.  Install on the passive node goes well and says it is successful, however, the cluster svc and networking services begin to fail or "flap".  Even when the cluster svc and networking components are online and working, an attempt to failover the CMS fails.  Has anyone had any issues with installing Rollup7 on a SCC?

    Rollup 7 installed fine on the CAS/HUB servers…

    Thanks,

    Nate

  5. Exchange says:

    Hi Nathan, Michael

    Please visit our Exchange software update forum and place a request for help in there. We have many people actively monitoring this forum thread area, and we are already in process investigating issues for customers. here’s the link:

    http://social.technet.microsoft.com/Forums/en-US/exchangesoftwareupdate/threads/

    Thanks,

    Joey

  6. Chris says:

    Sorry, something is wrong… since the last updates, the exchange do some crazy things:

    Mails are marked as a virus:

    DATEI IN QUARANTÃ"NE

    Der ursprüngliche Inhalt dieser Datei wurde aufgrund seiner

    Beschaffenheit durch diese Nachricht ersetzt.

    Dateiname: ‘Nachrichtentext’

    Virusname: ‘Echtzeit-Zeitüberschreitung überschritten’

    The Server hangs up.

    And after a hard reboot, some exchange-services are destroyed (?), the Forefront Scanengine quits, no mails are collected…

    Fehlerhafte Anwendung ScanEngineTest.exe, Version 10.1.746.0, Zeitstempel 0x473ca2df, fehlerhaftes Modul NSE_W32.DLL, Version 5.93.1.0, Zeitstempel 0x48490cc5, Ausnahmecode 0xc0000005, Fehleroffset 0x0000cf19, Prozess-ID 0x1d9c, Anwendungsstartzeit 01c9aecde54507ed.

    Has anyone a solution?

    best regards!

  7. George Kentas says:

    When i installed rollup 7 on my exchange 2007 sp1 box my external receipient they were getting my e-mail addresses like the format below.

    IMCEAEX_OU=FIRST+20ORGANIZATION_OU=EXCHANGE+20ADMINISTRATIVE+20GROUP+20+28FYDIBOHF23SPDLT+29_CN=RECIPIENTS_CN=Name+2Esurname@domain.com

    Is there anyway to leave avoid these?

    Thanks

  8. Tony Eversole says:

    Exchange 2007 SP1 Rollup 7 has broken Exchange auto-generated emails such as NDR’s and deliver confirmation receipts. A long email string is now displayed as the FROM instead of Microsoft Exchange (as seen in the example below). Is there a fix for this or is this a known issue? Our users are starting to panic as they see this as hoax email.

    MicrosoftExchange329e71ec88ae4615bbc36ab6ce41109e@kctcs.edu

  9. hashem says:

    I have exactly the same "long email string" for auto-generated NDR and delivery confirmations! I havent been able to fix it. Is tehre any place where one could change the displayname parameter for this? to report the usual "Microsoft Exchange" instead of "MicrosoftExchange329e71ec88ae4615bbc36ab6ce41109e@**.net

  10. Suriya says:

    Yes, i received that kind of email also after roll out the update 7.

    How to fix the issue?

    From:MicrosoftExchange329e71ec88ae4615bbc36ab6ce41109e@domail.com

  11. Stefan Heyl says:

    Hi everyone. I have the same problem after roll out the update 7 to several exchange server MicrosoftExchange329e71ec88ae4615bbc36ab6ce41109e@**.de. I think it is something with one value in get-OrganizationConfig. Maybe MicrosoftExchangeRecipientEmailAddressPolicyEnabled when you set this value from true to false!? http://technet.microsoft.com/de-de/library/aa997443.aspx

    I tried this with set-OrganizationConfig MicrosoftExchangeRecipientEmailAddressPolicyEnabled $false with no result.

  12. RichardJAD says:

    As far as I can see in ADSIedit, the displayname for the mailbox is still "Microsoft Exchange", but it isn’t being added to the emails, so you only get the bare "MicrosoftExchange329e71ec88ae4615bbc36ab6ce41109e@" address showing up.

  13. Aseem Snehi says:

    If OWA does not open after Updating Roll-up 7 for Exchange Server 2007 Service Pack 1, then just re-install it again. Do not un-install, No reboot, nothing else is required. It will start working.

  14. peterp says:

    Hi, The install of rollup 7 failed on my edge and hub servers via Windows Update. However, if I check under Programs / Features / View Updates, the rollup 7 patch is installed. Does this mean that it has been successfully installed. Is there anyway to check using the get-exchangeServer command? Also, there has been some posts that Rollup 6 must be removed before Rollup 7 needs to be installed. Please confirm ?

  15. Dankwax says:

    When is MS coming out with a hotfix for this issue?

  16. Aseem Snehi says:

    Hi Peter,

    You can download the Rollup 7 from MS site and then try to install. Uninstall the rollup 6 or any pervious rollup before installing rollup 7, it will then ask for reboot and configuration changes. Further also to check if rollup 7 is installed or not go to Add/remove program and click on rollup 7 and click ‘remove’, if you it say the ‘Patch is not applied’ that means that it was not successfully installed. Now to remove that you first install the rollup 7 it possibly will not ask for a reboot. Reboot the sever, go to add/remove and now uninstall rollup 7. It will ask for reboot, go aheah with it. Now do the clean install of the rollup 7 from the dump and finally it will ask for reboot due to config changes. Go ahead with that.

    aseem.snehi@gmail.com

  17. Michael Knox says:

    OWA does not work anymore after this update.

    Here’s what is in the log:

    [03:20:44] * UpdateOwa.ps1: 18/04/2009 3:20:44 AM

    [03:20:59] CAS role is not installed on server [servername]

    I will reapply the update and reboot the server, great… Any other ideas?

  18. Rhiu says:

    Hey.. after I apply Update 7, I can no longer view the contents of my public folders.. any ideas?

  19. Terje (say tay-a) says:

    Since I added Rollup 7 for E2007 to our Window2008 server Exchange locks up in the early hours of most (but not all) mornings. To get it going again I have to completely reboot the server and then manually start the MS EXCHANGE SYSTEM ATTENDANT service. It then seems to work fine for another day or two before the problem repeats itself. I’m inclinded to remove Rollup 7. Has anybody else had similar problems?

  20. vipin says:

    At this moment in time, the update rollup breaks more things than it fixs, is their any way to roll back to update rollup 6?

  21. Vince K. says:

    Update Rollup 8 for Exchange Server 2007 Service Pack 1:

    http://support.microsoft.com/kb/968012

  22. terryb says:

    E2K7 installed fine.  But those of us that REQUIRE public folders are forced to take the leap to SP1, which crashed in the install process and forced a full rebuild and IIS still not functional, which means no OWA. Anyone else had issues with IIS lockup due to SP1 install? Any fix other than full reinstall of E2K7?

Comments are closed.