Re: Exchange Update and Blackberry

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

The Feb. 2007 Cumulative Time Zone Update for Windows OSes (KB 931836) is a
pre-req for the Exchange CDO patch (KB 926666 for Exchange Server 2003 SP2).

Before you upgrade Store.exe to a version that separates the Full Mailbox
Access and Send As permissions, assign Send As rights on all Stores with
BlackBerry-enabled users to the BES svc account.

--
Bharat Suneja
MVP - Exchange
www.zenprise.com
NEW blog location:
exchangepedia.com/blog
----------------------------------------------


<baito7@xxxxxxxxx> wrote in message
news:1172769109.538862.259900@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hi there

This weekend we are planning to roll out the Windows and Exchange DST
Patch to your single domain environment.

Blackberries suggested upgrade path is as follows:

1) Update Windows Server with the DST patch
2) Update Windows Clients with the DST patch
3) Update Blackberry devices
4) RUN THE RIM SET SEND AS PERMISSION TOOL
5) Apply the Exchange Server CDO DST Patch

The RIM set send as permission tool is supposed to prevent the
problems as listed in KB912918 where there are set send as receive
problems. This problem arrised after store.exe was upgraded to
version 7650 or higher.
We never had this problem because we havent run the windows update
patches on our exchange server in over a year.

My question is as following: This weekend we are forced to upgrade
store.exe to 7651 as per the CDO update.
Should we run Windows Update prior to step 1 listed above or do it
last as the RIM set send as permission tool will prevent us from
having the set send as receive problem. Or does the new CDO.dll DST
patch assume we are close to up to date with our patches.

I want to run Windows update as Step 6, but I am not sure if this is a
good idea. I would assume Blackberry did most of their testing on
Exchange Servers that are current with their patch schedule.

Can someone offer an educated opinion on this matter?

Thanks.



.

Relevant Pages

  • Re: Legality of software "handmedowns"
    ... You NEVER need to call for permission. ... If you do upgrade enough times in the 120 days, a 5 minute call may be ... Also since you chose OEM, you also chose the applicable EULA. ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: Legality of software "handmedowns"
    ... You NEVER need to call for permission. ... If you do upgrade enough times in the 120 days, a 5 minute call may be ... Also since you chose OEM, you also chose the applicable EULA. ...
    (microsoft.public.windowsxp.general)
  • Re: cannot start 3 services after FC3 upgrade ==> Update not that great.
    ... Probably because we upgrade from different configurations. ... James T wrote: ... > was with SELinux denying those services permission/access to those libs. ... so they don't get those permission errors when I reactivate ...
    (linux.redhat.install)
  • Re: Permissions on user keep changing
    ... We use a Blackberry Enterprise Server. ... The account that accesses his mailbox "blackberry" was given "send as" permission on his user account. ... For some reason, he is initially able to send, and then the permission disappears. ...
    (microsoft.public.windows.server.active_directory)
  • Re: permissions gone missing in sysprotects
    ... we now preserve permissions on system objects during the ... we will remember that during the upgrade. ... permission setting does not appear in objects permission ...
    (microsoft.public.sqlserver.security)