[vhato]

The install went well.

The current CDO is also 6.5.7974. I run 6.5.7888. The current CDO requires Outlook 2007 to be installed. Anyone know of a way around it?

[hdawg]

I've updated the thread name. Link to Release Notes

Known issues
Wireless calendar synchronization
SDR 144896
In BlackBerry Enterprise Server Version 4.1 SP4, in some circumstances, if an organizer sends an invitation for a recurring meeting from Microsoft® Outlook® to both BlackBerry devices users and users without BlackBerry devices, and then updates an instance of the meeting using the BlackBerry device, users without BlackBerry devices cannot accept the update

Fixed issues
BlackBerry Manager
*SDR 129760
In BlackBerry Enterprise Server Version 4.1 SP4, if you specified only a server name and not a complete path while setting up a software configuration, the BlackBerry Manager stopped responding.
In BlackBerry Enterprise Server Version 4.1 SP4 MR4 and later, this issue is resolved.

BlackBerry MDS Services
*SDR 152321
In BlackBerry Enterprise Server Version 4.1 SP4, if you used RSA® authentication to log in, the default inactivity timeout did not work as expected.
In BlackBerry Enterprise Server Version 4.1 SP4 MR4 and later, this issue is resolved.
*SDR 149371
In BlackBerry Enterprise Server Version 4.1 SP4, you could not use RSA authentication to log in and access web resources.
In BlackBerry Enterprise Server Version 4.1 SP4 MR4 and later, this issue is resolved.
*SDR 140052
In BlackBerry Enterprise Server Version 4.1 SP4, if the proxy server returned a 502 message, the BlackBerry MDS Services treated the response as an unexpected error.
In BlackBerry Enterprise Server Version 4.1 SP4 MR4 and later, this issue is resolved

BlackBerry Messaging Agent
*SDR 140655
In BlackBerry Enterprise Server Version 4.1 SP4, when performing LDAP searches using the address lookup protocol, the search would timeout.
In BlackBerry Enterprise Server Version 4.1 SP4 MR4 and later, this issue is resolved.
*SDR 128830
In BlackBerry Enterprise Server Version 4.1 SP4, if you installed the BlackBerry Enterprise Server in a Microsoft Exchange 2007 environment, the installation process did not complete successfully if the Microsoft Exchange server did not include public folders.
In BlackBerry Enterprise Server Version 4.1 SP4 MR4 and later, this issue is resolved when you create the public folder database. For more information, read article 555851 from www.microsoft.com/support and read articles 123694 and 124270 from technet.microsoft.com.

BlackBerry Policy Service
*SDR 145833
In BlackBerry Enterprise Server Version 4.1 SP4, in certain circumstances, after upgrading from BlackBerry Enterprise Server Version 4.1 SP3, the GroupingNumber became negative, and wireless push did not work.
In BlackBerry Enterprise Server Version 4.1 SP4 MR4 and later, this issue is resolved.

BlackBerry Synchronization Service
*SDR 136748
In BlackBerry Enterprise Server Version 4.1 SP4, after upgrading the BlackBerry Device Software using the BlackBerry Desktop Software, the BlackBerry Synchronization Service did not send updated service books to the BlackBerry device.
In BlackBerry Enterprise Server Version 4.1 SP4 MR4 and later, this issue is resolved.

Hosted BlackBerry Enterprise Server
*SDR 137482
In BlackBerry Enterprise Server Version 4.1 SP4, when looking up addresses using short queries, the address lookup returned more results than expected.
In BlackBerry Enterprise Server Version 4.1 SP4 MR4 and later, this issue is resolved.

Secure messaging
*SDR 140054
In BlackBerry Enterprise Server Version 4.1, when processing S/MIME encrypted and signed messages that included large attachments, the memory usage of the BlackBerry Enterprise Server increased significantly.
In BlackBerry Enterprise Server Version 4.1 SP4 MR4 and later, this issue is resolved.

Wireless calendar synchronization
*SDR 126932
In BlackBerry Enterprise Server Version 4.1 SP4, an appointment in Microsoft Outlook was not updated if a user updated the notes in the appointment on the BlackBerry device without modifying the first 1024 bytes in the calendar note field.
In BlackBerry Enterprise Server Version 4.1 SP4 MR4 and later, this issue is resolved.
*SDR 125750
In BlackBerry Enterprise Server Version 4.1 SP4, if an administrator attempted to reload a user during calendar synchronization after wireless enterprise activation, the calendar synchronization process stopped responding.
In BlackBerry Enterprise Server Version 4.1 SP4 MR4 and later, this issue is resolved.

Wireless enterprise activation
*SDR 137957
In BlackBerry Enterprise Server Version 4.1 SP4, after activating a user, the BlackBerry Enterprise Server did not record the activation time correctly.
In BlackBerry Enterprise Server Version 4.1 SP4 MR4 and later, this issue is resolved.
Hosted BlackBerry Enterprise Server

[Elgin]

Thanks for the info, this might be the IT Policy fix i'm looking for.

Cheers! I'll let you know.

[audit]

Installed it on my BES servers with no issues. All Exchange servers are 2003+SP2

[Frank Castle]

Regarding the 1st post - did this install a new CDO or was that due to Outlook 2007?

At least this gives me something to do when the holiday change freeze is over

[vhato]

The new CDO had nothing to do with the upgrade. While I was downloading MR4 I browsed Microsoft and saw release 1.2.1 was update to version 6.5.7974. I couldn't use it so I am still using release 1.2.1 version 6.5.7888.

[celeb]

Anyone experiencing any issues with MR4 and calendaring? ie. meetings canceling on their own etc... ? How about anything else?

Thanks in advance

[Elgin]

MR4 installed and working properly.

As an FYI, login with the proper service account (eg: BESadmin) to update your BES. I used a domain admin account and the update changed all the service login credentials, taking down my BES for a few hours

[adamli9]

The upgrade to MR4 went great last weekend.

I also learned the hard way about the service account with MR3 (my first upgrade). ;)

I haven't heard of random meeting cancellations, but we've been closed for business this past week.

[thejollyboys]

Guy's,

Since the upgrade everything from the browser is being sent to our proxy. We have an exception which says anything with *.ourcompany.com go direct.

This worked great before the upgrade but now everytime the user browses to an internal site they are prompted for username and password, where as before it just used to connect.

Since the upgrade it is ignoring this exception rule.

Just wondering if any else has this issue.

Thanks.

[frazer_clark]

We are getting the same problem after applying MR4 - browsing (which used to use a servcie account and password and go via our proxy) now prompts for users account credentials. Is there a fix for this?