Home
%3CLINGO-SUB%20id%3D%22lingo-sub-595682%22%20slang%3D%22en-US%22%3EReleased%3A%20Update%20Rollup%202%20for%20Exchange%20Server%202007%20Service%20Pack%202%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-595682%22%20slang%3D%22en-US%22%3E%3CP%3E%3C%2FP%3E%3CDIV%20style%3D%22font-family%3A%20'Calibri'%2C'Helvetica'%2C'Arial'%2Csans-serif%3B%20font-size%3A%201.1em%22%3EExchange%20CXP%20team%20has%20released%20Update%20Rollup%202%20for%20Exchange%20Server%202007%20Service%20Pack%202%20(KB%20972076)%20to%20the%20%3CA%20title%3D%22Download%20Update%20Rollup%202%20for%20Exchange%202007%20Service%20Pack%202%22%20href%3D%22http%3A%2F%2Fwww.microsoft.com%2Fdownloads%2Fdetails.aspx%3FFamilyID%3Dfa83be11-9d5e-47bc-9a51-a10986f22928%26amp%3Bdisplaylang%3Den%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Edownload%20center%3C%2FA%3E.%3CP%3E%3C%2FP%3E%0A%3CP%3EIn%20addition%20to%20bug%20fixes%20reported%20by%20customers%20we%20have%20added%20new%20rules%20to%20the%20Exchange%20Best%20Practices%20Analyzer%20to%20check%20the%20health%20of%20your%20system.%20Starting%20this%20rollup%2C%20customers%20who%20wish%20to%20deploy%20the%20new%20BPA%20health%20rules%20to%20a%20server%20with%20no%20internet%20connection%20can%20do%20so%20by%20downloading%20the%20installing%20the%20update%20rollup%20on%20the%20server.%20Until%20Exchange%20Server%202007%20Service%20Pack%202%2C%20updates%20to%20the%20BPA%20rules%20were%20available%20only%20via%20the%20web%20which%20meant%20customers%20wanting%20to%20deploy%20the%20new%20health%20check%20rules%20to%20servers%20not%20connected%20to%20the%20internet%20would%20have%20had%20to%20copy%20over%20the%20XML%20files%20manually.%20In%20Exchange%202007%20SP2%2C%20we%20implemented%20a%20work%20item%20which%20allows%20us%20to%20ship%20updates%20to%20the%20BPA%20health%20check%20rules%20via%20the%20rollup%20and%20as%20well%20as%20via%20the%20traditional%20web%20based%20channel.%20More%20on%20this%20via%20a%20blog%20post%20in%20the%20near%20future.%3C%2FP%3E%0A%3CP%3EKBA%20972076%20lists%20all%20the%20fixes%20included%20in%20this%20rollup.%20Here%20are%20some%20of%20the%20product%20improvements%20and%20critical%20bug%20fixes%20we'd%20like%20to%20call%20out%3A%3C%2FP%3E%3COL%3E%20%3CLI%3E%3CA%20href%3D%22http%3A%2F%2Fsupport.microsoft.com%2F%3Fkbid%3D972705%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3EKB%20972705%3C%2FA%3E%3A%20This%20one%20is%20for%20all%20the%20IT%20pros%20and%20anyone%20who%20has%20ever%20had%20to%20explain%20abnormal%20database%20size%2Flog%20file%20growth%20in%20a%20short%20period%20of%20time.%20We%20have%20added%20three%20new%20registry%20entries%20to%20help%20speed%20up%20troubleshooting%20the%20issue%3A%3CUL%20style%3D%22list-style-type%3A%20square%22%3E%20%3CLI%3EBytesLogWarningThreshold%3C%2FLI%3E%3CLI%3EBytesLogErrorThreshold%3C%2FLI%3E%3CLI%3EBytesLogCheckPeriodInMinutes%3C%2FLI%3E%3C%2FUL%3EMore%20information%20on%20the%20values%20to%20set%20in%20the%20above%20registry%20keys%20is%20documented%20in%20KB%20972705.%3C%2FLI%3E%3CLI%3E%3CA%20href%3D%22http%3A%2F%2Fsupport.microsoft.com%2F%3Fkbid%3D975404%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3EKB%20975404%3C%2FA%3E%3A%20Accepting%20meeting%20requests%20sent%20via%20an%20application%20using%20CDO%20like%20Blackberry%20devices%20sometimes%20results%20in%20rendering%20an%20embedded%20message%20attached%20to%20the%20meeting%20request%20inaccessible.%3C%2FLI%3E%3CLI%3E%3CA%20href%3D%22http%3A%2F%2Fsupport.microsoft.com%2F%3Fkbid%3D976137%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3EKB%20976137%3C%2FA%3E%3A%20We%20have%20made%20a%20change%20to%20the%20behavior%20of%20the%20Unified%20Messaging%20Auto%20attendant%20when%20it%20plays%20the%20greeting%20for%20callers%20on%20a%20holiday.%20Currently%20when%20callers%20call%20on%20a%20holiday%2C%20they%20hear%20the%20non-business%20hours%20greeting%20followed%20by%20the%20holiday%20greeting.%20In%20this%20rollup%20we%20have%20made%20a%20change%20so%20that%20the%20callers%20calling%20on%20a%20holiday%20will%20only%20hear%20the%20holiday%20greeting.%20If%20your%20greetings%20are%20configured%20such%20that%20they%20would%20make%20sense%20to%20callers%20calling%20on%20a%20holiday%20only%20if%20they%20hear%20both%20the%20non-business%20hours%20greeting%20and%20the%20holiday%20greeting%2C%20then%20you%20need%20to%20re-configure%20them%20when%20you%20install%20this%20update%20rollup.%3C%2FLI%3E%3CLI%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EKB%20971177%3C%2FA%3E%3A%20Another%20change%20in%20the%20UM%20Auto%20Attendants%20configuration%20in%20the%20Exchange%20Management%20Console.%20It%20is%20now%20aware%20if%20your%20time%20zone%20follows%20Daylight%20Saving%20Time.%3C%2FLI%3E%3CLI%3E%3CA%20href%3D%22http%3A%2F%2Fsupport.microsoft.com%2F%3Fkbid%3D975165%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3EKB%20975165%3C%2FA%3E%3A%20In%20an%20environment%20using%20self-signed%20certificates%20and%20CAS-CAS%20proxying%2C%20Exchange%20Web%20Services%20requests%20proxied%20may%20start%20failing%20after%20the%20Availability%20Service%20has%20made%20a%20proxy%20request.%3C%2FLI%3E%3CLI%3EA%20bug%20where%20the%20OWA%20Virtual%20Directory%20cannot%20be%20accessed%20via%20the%20Exchange%20Management%20Console%20in%20an%20environment%20coexisting%20with%20Exchange%202010%20if%20the%20Exchange%202007%20server%20was%20upgraded%20from%20Exchange%202007%20SP1%20to%20SP2.%3C%2FLI%3E%3C%2FOL%3E%3CA%20href%3D%22http%3A%2F%2Fsupport.microsoft.com%2Fkb%2F972076%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3EKB%20972076%3C%2FA%3Ehas%20more%20details%20about%20this%20release%20and%20a%20complete%20list%20of%20all%20fixes%20included%20in%20this%20rollup.%3CP%3E%3C%2FP%3E-Exchange%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-595682%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAnnouncements%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EExchange%202007%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E

Exchange CXP team has released Update Rollup 2 for Exchange Server 2007 Service Pack 2 (KB 972076) to the download center.

In addition to bug fixes reported by customers we have added new rules to the Exchange Best Practices Analyzer to check the health of your system. Starting this rollup, customers who wish to deploy the new BPA health rules to a server with no internet connection can do so by downloading the installing the update rollup on the server. Until Exchange Server 2007 Service Pack 2, updates to the BPA rules were available only via the web which meant customers wanting to deploy the new health check rules to servers not connected to the internet would have had to copy over the XML files manually. In Exchange 2007 SP2, we implemented a work item which allows us to ship updates to the BPA health check rules via the rollup and as well as via the traditional web based channel. More on this via a blog post in the near future.

KBA 972076 lists all the fixes included in this rollup. Here are some of the product improvements and critical bug fixes we'd like to call out:

  1. KB 972705: This one is for all the IT pros and anyone who has ever had to explain abnormal database size/log file growth in a short period of time. We have added three new registry entries to help speed up troubleshooting the issue:
    • BytesLogWarningThreshold
    • BytesLogErrorThreshold
    • BytesLogCheckPeriodInMinutes
    More information on the values to set in the above registry keys is documented in KB 972705.
  2. KB 975404: Accepting meeting requests sent via an application using CDO like Blackberry devices sometimes results in rendering an embedded message attached to the meeting request inaccessible.
  3. KB 976137: We have made a change to the behavior of the Unified Messaging Auto attendant when it plays the greeting for callers on a holiday. Currently when callers call on a holiday, they hear the non-business hours greeting followed by the holiday greeting. In this rollup we have made a change so that the callers calling on a holiday will only hear the holiday greeting. If your greetings are configured such that they would make sense to callers calling on a holiday only if they hear both the non-business hours greeting and the holiday greeting, then you need to re-configure them when you install this update rollup.
  4. KB 971177: Another change in the UM Auto Attendants configuration in the Exchange Management Console. It is now aware if your time zone follows Daylight Saving Time.
  5. KB 975165: In an environment using self-signed certificates and CAS-CAS proxying, Exchange Web Services requests proxied may start failing after the Availability Service has made a proxy request.
  6. A bug where the OWA Virtual Directory cannot be accessed via the Exchange Management Console in an environment coexisting with Exchange 2010 if the Exchange 2007 server was upgraded from Exchange 2007 SP1 to SP2.
KB 972076 has more details about this release and a complete list of all fixes included in this rollup.

-Exchange
27 Comments
Not applicable
Is anyone else seeing an issue with Entourage EWS, and sending out meeting requests with attachments included?
Not applicable
This will be on Microsoft update when?
Not applicable
When are you going to release an update to the 32 bit Management Tools for 2007 so we can continue to export PST files after upgrading to SP2?



http://www.microsoft.com/downloads/details.aspx?FamilyId=6BE38633-7248-4532-929B-76E9C677E802&displa...



No download for the SP2 version as of now.

Not applicable
It should be... it came down to our WSUS server on 1/26/10.  Though typically there was usually a 2 week delay between rollup updates being available in the download center and being pushed to WSUS/Microsoft Update.  I may install this sometime this week.  I've never had any serious issues when installing any of the rollup updates / service packs to Exchange 2007.
Not applicable
Do not install this update. It has a flaw when it comes to OWA and signitures. Very annoying when you have thousands of OWA users.
Not applicable
JB - Could you please post the details of what problems you are facing at the technet forums: http://social.technet.microsoft.com/Forums/en-US/exchangesoftwareupdate/threads
Not applicable
I find that when i add a transport rule - e-mail discaimer on exchange after applying rollup 2 for service pack 2, many of our company e-mails get marked as poisoned and will not deliver. removing the transport rule, allows all mails to go through without queueing in the poisoned queue.
Not applicable
Ya, unfortunately we are getting the annoying owa signature bug after the update.  5,000 users the next day flooded the helpdesk.  
Not applicable
Still... after automatic update the Transport service doesn't get restarted. Why oh why can't MSFT fix this? If you are going to offer an update via Windows Update, then at least make sure it leaves the server as it found it after the update. Otherwise if you require admin intervention, then simply make us manually download it and install it...
Not applicable
Anyone else having failures when trying to install on Windows 7 64-bit? I'm trying to up my admin tools install and get this every time:

Service 'Remote Registry (RemoteRegistry)' cannot be configured due to the following error: Access is denied
Unable to enable service(s): 'RemoteRegistry'.
Unable to enable all services for 'AdminTools'.
Removing service state from 'C:UsersaltoidsAppDataLocalTempStoppedServices.xml'...
Removing service registry data from 'C:UsersaltoidsAppDataLocalTempServiceRegistryData.xml'...
Script completed with one or more errors.
Not applicable
This roll-up also causes an issue when you use Enterprise Vault archiving, with the OWA-extentions installed. When rightclicking an item in OWA you get an error. Symantec is working on a fix/hotfix/patch.
Not applicable
Though Ex_Ronil suggested we post our problems there, it seems no one from Microsoft is checking http://social.technet.microsoft.com/Forums/en-US/exchangesoftwareupdate/threads, at least since last Friday.
Not applicable
I installed the Rollup 2 to E2K7 on Windows 2008 and found that some people started to receive mails that they could not open. Did post this on the Technet Forum.
http://social.technet.microsoft.com/Forums/en-US/exchangesoftwareupdate/thread/a53b2c83-adaa-4846-8e...

I had to remove the Rollup after three days only to find it left OWA Premium broken. The rollup did not restore all the .aspx files in owaformspremium.

See http://social.technet.microsoft.com/Forums/en-US/exchangesoftwareupdate/thread/65ca9584-e797-439a-bd...

on how I managed to fix it.
Not applicable
The Get-ClusteredMailboxServerStatus once again seems to only work correctly when run on a node in the CCR cluster. Remote uses do not work. This is similiar to an issue in one of the SP1 RUs that was later resolved.

Posted on the technet forums as requested:
http://social.technet.microsoft.com/Forums/en-US/exchangesoftwareupdate/thread/9f733c86-7c8e-4113-aa...
Not applicable
Has SP2 Rollup 2 been withdrawn from WindowsUpdates?

I ran WindowsUpdates on my mails server and 6 fixes for Server 2007 offered up but Rollup 2 not there. Installed the 6 OS updates and after reboot did WindowsUpdates again and still no sign of Rollup 2???

A few people have reported problems so I an wondering if it has be taken off?
Not applicable

We applied this update and now am seeing at times slow or delays in outlook(2003)/exchange peformance. Anyone dedected this issue?
Not applicable
For a number of reasons, we cannot yet upgrade our Exchange Servers to SP2 for the coming months.
On the other hand we need some of the functionalities available in Powershell  V2.
Can we have an Windows 2008 Server with Exchange 2007 Management Tools installed, upgrade to SP2 and Powershell V2?
Will the schema update be a required step before doing this?
Not applicable
Your best bet is to make a post on the Technet forums at this link:-

http://social.technet.microsoft.com/Forums/en-US/category/exchangeserver

and post your question there/
Not applicable
I'm getting this error message after updating Rollup update 1 for Exchange 2007 SP2.
Source: MSExchange Web Services.
Event ID 6
Unable to send a notification for subscription EwBwLWV4Y2h3bTAxLm9uMjQuY29tEAAAAGGo3ZhcQz5Gjqmuroysdgo=. (Send attempts: 7)

Anyone having this issue after updaing rollup update 1 for Exch2007 SP7:
Not applicable
I will say this, this update definely required that you launch it with administrative rights or else it doesn't work!  I had a friend of mine install it and it completely screwed OWA until I ran the update from an Administrator enabled command prompt and then it worked!
Not applicable
Wow! With all the complaints about this Rollup, is it safe to install??? Have the peoples complaints been addressed?
Not applicable
Put us in the "haven't had any problems" column.
Not applicable
Update Rollup broke my OWA...sheesh.
Not applicable
No bug detected, except the classic broken tool box ... already exist in rollup 1.

Just have to disable IPV6 on all servers. In my case, this prevent the error with 'Transport service' on my 3 CAS/HUB servers :
[ERROR] Service 'MSExchangeTransport' failed to reach  status 'Running' on this server. (error when upgrading to SP2 ... with IPv6 actived).
Not applicable
It doesn't appear as if this version fixed the issues with MSExchangeREPL 2104 / MSExchangeREPL 2147 / MSExchangeREPL 2127 if you are using a secondary network for CCR replication.

Quite annoying that the application logs are filled with events of Exchange flipping back and forth between the production network and the replication network for no good reason.
Not applicable

E:19-03-2010exch2k7 sp2>setup  /upgradecms

Welcome to Microsoft Exchange Server 2007 Unattended Setup

Preparing Exchange Setup

The following server roles will be upgraded
   Clustered Mailbox Server

Performing Microsoft Exchange Server Prerequisite Check


Configuring Microsoft Exchange Server

   Clustered Mailbox Server         ......................... FAILED
An unexpected error has occurred and debug information is being generated: Obje
ct reference not set to an instance of an object.
    Object reference not set to an instance of an object.

Exchange Server setup encountered an error.

We are getting tthe above error while upgrading SCC passive node,
Not applicable
Wow, not suprising - another rollup that includes too many hotfixes to properly test against all customer scenarios.

When will MSFT admit that this method is problematic and individual patches are easier for administrators to manage?