[hdawg]

Just got off a call with our PAM & TAM ...

Apply the SQL "patch" to your database (making sure you are at the minimum version of BES as listed on the KB Article). This will automatically update the timezone tables on 4.2 HH OSs

Still waiting to hear exactly what will happen with 4.1 HH OSs

[hdawg]

There will be no patch for New Zealand DST change for 4.1 HH OSs

The HHs will either need to be upgraded to HH OS 4.2.2 or > (contains the updated info) or at least upgraded to 4.2 and then the database update will need to be performed on your SQL server.

For Domino BES you'll need at least:

4.0 Service Pack 7 MR1 xxx8211; Released as of 9/24/2007 -- http://www.blackberry.com/go/serverdownloads
4.1 Service Pack 2 HF4

For Exchange BES you'll need at least:
4.0 Service Pack 6
4.1 Service Pack 2 Hot Fix 2

[dphsv]

Have tried a number of times to apply NZ DST fix to BES (4.0 SP7) but HH's not being updated. Here is a run-down of last attempt yesterday:

Applied SQL NZ DST fix - came back with (1 row affected) which I presume meant it actioned the request.

Produces the following in the CMNG log (have included a non-patched HH for completeness).

[40082] (09/24 16:48:15):{0xD38} {David Palmer.65} UpdateDeviceUserState - Record does not exist. No request sent. DbID=15403, GUID=14, Operation=U
[40084] (09/24 16:48:15):{0xD38} Timezones not enabled, no request sent to server. UserConfigId=76

My "test calendar entries" are still 1 hour out on the HH whilst showing correct in patched Exchange/Outlook environment.

Can't find any reference to this message anywhere. Any ideas welcome. Might upgrade to BES 4.1 to see if any difference.

[hdawg]

What is the model and version of the HH OS?

[dphsv]

Originally Posted by hdawg

What is the model and version of the HH OS?

Hi there... it's a 8700 running 4.2.1.101 released by Vodafone a week ago

[hdawg]

Is the HH Configuration Manager picking up the HH as a 4.2.x device?

[Frank Castle]

this blurb on KB14176 makes me nervous:

"A known issue exsists (SDR138787), as a result of applying the new CDO.dll. a duplicate appointment may occue (read will) if meetings are updated after they have been accepted."

I am going to have some anger admins after me.

Is anyone leaning towards NOT applying this? Does this have any impact on standard states time? Eastern, Central, Western etc?

[dphsv]

Originally Posted by hdawg

Is the HH Configuration Manager picking up the HH as a 4.2.x device?

Yes it is - showing 4.2.1.101, and all other HH's showing correct version too.

[hdawg]

Originally Posted by jletendre

this blurb on KB14176 makes me nervous:

"A known issue exsists (SDR138787), as a result of applying the new CDO.dll. a duplicate appointment may occue (read will) if meetings are updated after they have been accepted."

I am going to have some anger admins after me.

Is anyone leaning towards NOT applying this? Does this have any impact on standard states time? Eastern, Central, Western etc?

This is apparently fixed in 4.1.4 MR2 ... if you don't have anyone in the affected timezone(s) then there is no rush to apply this; I would just wait until 4.1.4 MR2 is out and then schedule the update. Perhaps wait until 4.1.5 in November, unless you find lots of Kiwi's with appointment times being off in your org.

[hdawg]

Originally Posted by dphsv

Yes it is - showing 4.2.1.101, and all other HH's showing correct version too.

If you have a spare HH try wiping / activating it on the BES and see if it gets the updated TZ data.

Perhaps perform a soft reset on the HH and then force an update config on the BES to poll the HH. Not sure if this plays a role in it, but is the Date/Time Source: set to None? None of the options will pull from the BES, but I'm wondering if this is playing a role in it. ... I'm assuming you have the TZ set to Auckland?

Either way I would contact Vodaphone / RIM due to the short time left. This log event doesn't seem to be documented.

[contra]

I work for vodafone and we have at least one company with the KNown issue. Duplicate entries after applying patch. Have logged it with RIM....

Vodafone NZ !

[contra]

Note: Applying the above CDO.dll may result in duplicate appointments if meetings are updated after they have been accepted. This issue is resolved by upgrading BlackBerry Enterprise Server software version 4.1 Service Pack 4 (4.1.4) to BlackBerry Enterprise Server software version
4.1 Service Pack 4 Maintenance Release 2.

Getting Client to try this now