[stuwhite]

I'm pretty sure the patch can't/won't do that. Especially as it's an Exchange patch, not a BES-specific one. You might want to see if someone is playing on your system.....

[Abaddon]

Originally Posted by stuwhite

I'm pretty sure the patch can't/won't do that. Especially as it's an Exchange patch, not a BES-specific one. You might want to see if someone is playing on your system.....

I would have thought so, too, but no one touches this system but me. And I haven't touched it since I installed the BES system. Strange.

[stuwhite]

Originally Posted by Abaddon

I would have thought so, too, but no one touches this system but me. And I haven't touched it since I installed the BES system. Strange.

Bizarre. Keep an eye an the besadmin account's group membership for a while just in case.

[Abaddon]

Originally Posted by stuwhite

Bizarre. Keep an eye an the besadmin account's group membership for a while just in case.

Will do. I'd say now that this is fixed, the TNEF patch worked just fine for me. I haven't had any other issues out of it.

[funkyp56]

Originally Posted by funkyp56

BTW ill be installing it this weekend.

It installed over the weekend. Everything A-OK

[stuwhite]

Has anyone put the patch on their BES yet? MS have updated the bulletin Microsoft Security Bulletin MS09-003 to state that MAPI is affected and they say CDO doesn't actually need updating but it's their for our convenience . They say that anyone using ESM-only should apply the patch but obviously I won't until the man from RIM he say yes. Plus things are still syncing fine for us with the mismatch in place.

[doctortt]

You guys only installed the security patch on the Exchange boxes and not the BES, right?

[knottyrope]

Originally Posted by doctortt

You guys only installed the security patch on the Exchange boxes and not the BES, right?

Right.

[doctortt]

Originally Posted by knottyrope

Right.

So far so good, right? Nothing breaks?

[RipThorn]

How about this?
Known Issues. Microsoft Knowledge Base Article 959239 documents the currently known issues that customers may experience when installing this security update, and recommended solutions. When currently known issues and recommended solutions pertain only to specific releases of this software, this article provides links to further articles.

I have yet to find anything that explains what the issue really is. The link provided takes you to another link and that another link explains nothing. WTF???

[rshire]

for those wondering about the interactions between the .dlls on the BES server and the Exchange server, read this article:

"How Outlook, CDO, MAPI, and Providers Work Together" I can't post a URL, but you can google the title of the article.



Question My application doesn't run on the server. Do the server binaries need to be the same version as the client?
Answer No. EMSMDB32 on the client does not communicate with EMSMDB32 on the server. It communicates with Store.exe.

Question Does MAPI32 on the client communicate with MAPI32 on the server?
Answer No, it does not. MAPI32 interfaces with the providers and the application.

Question Does CDO on the client communicate with CDO on the server?
Answer No, it does not. CDO interfaces with MAPI and the applications using it.

Question What if I have a CDO application that runs on the server?
Answer Update the binaries "Where the application runs." If your application runs on the server, update it there.

Question But I also have it running on another computer.
Answer Update where the binaries run. If it runs on the client, update it on the client. If it runs on the server, update it on the server. If the application runs on both, update both.

Question I have a third computer that runs this binary.
Answer Same answer: Update where the binaries run. If it runs on the client, update it on the client. If it runs on the server, update it on the server. If the application runs on both, update both.

[MarkF]

Originally Posted by doctortt

I just called RIM and they said that they haven't fully tested it. They will support us and resolve any issuses if problems do arise after the patch installation.

This is their reply:

"Resolution:
Microsoft Security Patch MS09-003 does not necessarily have to be applied to the Exchange System Manager installed on the BlackBerry Enterprise Server if the patch is applied to the Exchange 2003 server. Any BlackBerry ramifications of installing the Microsoft Security Patch MS09-003 are unknown and currently under investigation by BlackBerry."

That reply is pretty curious as it clearly states in the FAQ's for MS09-003:

I am a third-party application developer and I recommend that customers install Exchange System Management tools for Exchange Server 2003 as a prerequisite in order to use my application. How do they update it?
Customers who are running only the Exchange System Management tools for Exchange Server 2003 should install the security update for Exchange Server 2003 Service Pack 2 (KB959897) to be protected from the vulnerabilities described in this bulletin.

[stuwhite]

Originally Posted by MarkF

That reply is pretty curious as it clearly states in the FAQ's for MS09-003:

I am a third-party application developer and I recommend that customers install Exchange System Management tools for Exchange Server 2003 as a prerequisite in order to use my application. How do they update it?
Customers who are running only the Exchange System Management tools for Exchange Server 2003 should install the security update for Exchange Server 2003 Service Pack 2 (KB959897) to be protected from the vulnerabilities described in this bulletin.

Yeah, like we trust MS to have checked all the third-party apps . While your BES is functioning fine with the mismatch (as all seem to be), why take the chance? OK so RIM are being a bit rubbish over stating it's ok, but if it's working fine...

[MarkF]

stuwhite - I hear ya on trusting MS. I think I'll pass on this patch until RIM makes an official stance. I don't want our 11,000 BB users hatin on me

[Wiseman13]

This patch appears to have screwed up my BES (Blackberry Profession Server actually).

After installing the patch everything was fine, but after the reboot we are unable to send emails from the BBs, we can receive just fine.

The difference in CDO.dll was the cause of the problem, as soon as I uninstalled the patch on my Exchange server I was again able to send and receive email properly.

Not sure why I'm the black sheep of this family but that patch didn't get along with my BES!

[knottyrope]

Is BPS installed on the exchange server or seperate?

[Wiseman13]

They are separate.

[stuwhite]

Oh well, patched now. I am shocked that RIM still haven't said yes but maybe they did and us TS-less plebs never heard

[knottyrope]

I have knot done it so far, maybe next week if I am bored I will try it.

[MJDW]

I am running BES 4.1.4.16 MS server 2003 SP1 with Exchange servers 2003 SP2

I installed Exchange2003-KB959897-x86-ENU.exe
Version: 6.5.7654.12
Security Bulletins: MS09-003
Knowledge Base (KB) Articles: KB959897
Which updated the CDO and MAPI dll's to these versions
Cdo.dll 6.5.7654.12 724,992 26-Nov-2008
Mapi32.dll 6.5.7654.12 637,440 26-Nov-2008


I did this because our exchange servers were updated and according to RIM these two files need to be the same or newer than Exchange or it will cause issues with calendar syncing.
I also installed
Update for Exchange Server 2003 SP2 (KB 924334)
Security Update for Exchange Server 2003 SP2 (KB950159)

Basically I am trying to install any exchange updates on to the BES that have been installed on our exchange servers.
So far with these 3 updates I am not having any issues on the BES..

I was just told about 3 more updates
Microsoft Security Patch MS09-003 which according to Marks post RIm states does not have to be applied to the BES
KB931832 and KB912442 which I have not checked out yet.