[kpoland]

So... Everything in the environment is patched now, all the servers, Exchange servers, BES, devices, etc.

Yet, when an entry is created on the device, it will still display 1 hr ahead on Outlook.

I may have missed something - one question I have is this:

Am I actually supposed to run the Exchange update patch on the BES (because Exchange System Manager is a requirement of BES)? Because I'm fairly certain only the OS patch was done on the BES.

[kpoland]

Been digging:

From the BlackBerry PDF on the DST Patch...

Step 5: Apply the most recent Collaboration Data Objects (CDO) to the BlackBerry Enterprise Server and the Microsoft Exchange Server.

How do I apply the CDO? Extract it from the install file and regsvr32 it?

Or should I just do the Exchange patch on the BES?

[DarienA]

Just run the Exchange DST patch on the BES.

[kpoland]

Just did the Exchange patch (926666) on the BES - it didn't ask for a reboot, so I didn't.

Still having the same problem - entries I create on the device are ahead 1hr on Outlook.

All servers are patched (OS patch).
All Exchange servers are patched.
All BB devices are patched.

Strange things afoot:

User in Office A (Exchange Server A) creates appointments - they display properly when Online (not cached). When cached they appear 1 hour EARLY! Never seen this before!

User in Office B (Exchange Server B) creates appointments - they display 1 hr late whether cached or online.

[kpoland]

I just tried to manually register cdo.dll as suggested in this article, and that did not help.

[agep]

Might be a silly question, but did you patch the desktops as well?

[kpoland]

Originally Posted by agep

Might be a silly question, but did you patch the desktops as well?

The one that is displaying the entry EARLY is probably not patched. I can't think of anything else.

But my PC is Vista, which doesn't need or have a patch. And I'm still showing dates 1 hr late.

On hold with RIM right now...

[kpoland]

Out of sheer frustration, I relogged onto the BES servers and reregistered the cdo.dll this morning. And everything seems to work now!!

I can't possibly explain why it didn't work last night, so I don't feel too confident, but I dont care because it works!!!