|
|
|
03-13-2007, 05:10 AM
|
#581
|
Knows Where the Search Button Is
Join Date: Sep 2006
Location: UK
Model: 8800
PIN: uh uh
Carrier: many
Posts: 44
|
Please Login to Remove!
Yeah I have seen this... Basically the patch download times out when going via the BES mostly on slower handset models. Are you US based or somewhere further afield?
Deleting the Desktop IPPP forces the handset to go via the carrier browser. I was also instructed to delete desktop IPPP on my handsets but no one bothered to mention why or check whether I was forcing clients to use the Blackberry browser via IT Policy.
So much for a silent push without user intervention anyway. I wish RIM had allowed us to host these files on our own network so as to make the download faster and more reliable.
|
Offline
|
|
03-13-2007, 09:40 AM
|
#582
|
New Member
Join Date: Nov 2005
Model: 8830
Carrier: sprint
Posts: 11
|
Permission settings have become more restrictive
My users that have gotten patched with DST 2007 already are still popping up with "Permission settings have become more restrictive" on their Handhelds every hour. Even after they choose reset it comes up again an hour later.
Any ideas how to stop this? Is it as simple as removing the assigned software configuration or is something corrupt on the handhelds?
Thanks
|
Offline
|
|
03-13-2007, 02:57 PM
|
#583
|
New Member
Join Date: Apr 2006
Model: 7105T
Carrier: T-Mobile
Posts: 8
|
I'm trying up update the CDO, and I'm stuck. Here's the versions that we have currently, and they are both newer than the versions mentioned in the update article.
MAPI32 - 6.0.6617.47
CDO.DLL - 6.0.6617.47
Do I still need to update?
|
Offline
|
|
03-14-2007, 09:09 AM
|
#584
|
Feeling Blue, Bigly ;->
Join Date: Jan 2007
Location: U to the K
Model: 9000
PIN: 3, it's the magic number
Carrier: Most of them, it's a Global Village man!
Posts: 1,273
|
Quote:
Originally Posted by Ramma2
I'm trying up update the CDO, and I'm stuck. Here's the versions that we have currently, and they are both newer than the versions mentioned in the update article.
MAPI32 - 6.0.6617.47
CDO.DLL - 6.0.6617.47
Do I still need to update?
|
What are you reading that says that? CDO should be 6.5.7651.61, just use the MS package to update it and it will stop if it doesn't need it.
__________________
I was a BES and Exchange admin once.
Then my world turned Blue.
|
Offline
|
|
03-14-2007, 09:11 AM
|
#585
|
New Member
Join Date: Mar 2007
Location: Colorado
Model: 8100
Carrier: T-Mobile (unfortunately)
Posts: 3
|
I've managed to get more users patched, by removing them from the BES, having them try the patch download again, and then re-Enterprise Activate them once successful! kind of a pain, but it works...
|
Offline
|
|
03-14-2007, 04:57 PM
|
#586
|
Talking BlackBerry Encyclopedia
Join Date: Aug 2006
Model: 9000
Carrier: AT&T
Posts: 228
|
Quote:
Originally Posted by chrbes
I believe the documentation says it can take up to 4 hours for the polling service to pick up the new software change. I forced my test to update by resetting the handheld, and thus forcing an update. Not sure if there is a better way to force the update.
I am also seeing a prompt to manually reset the handheld after the patch is applied, anyone know of a way to have it automatically reset without user intervention?
|
This is definitely a day late, etc, but to change the polling interval, on the BES, edit the following registry key (DWORD), or create it if it doesn't exist:
HKLM/Software/Research In Motion/Blackberry Enterprise Server/Blackberry IT Admin Server/AppProvisioningPollInterval
Setting a decimal value of 5 sets it to poll every 5 minutes for example. Restart the Blackberry Policy Service and you're good.
Curious, I pushed this update out on Sunday after my company realized that this needed to be done (they didn't heed my warning about getting it done sooner). Though the update has been pushed down to all devices, when a calendar event is created on the BB, it shows up an hour late in Outlook. The reverse is not true, when the event is created in Outlook, it's fine on the BB. BES update? We're running BES for Exchange 4.1, and we haven't upgraded to SP3 yet. Downloading now.
Last edited by Xaneth; 03-14-2007 at 07:04 PM..
|
Offline
|
|
03-15-2007, 01:04 PM
|
#587
|
New Member
Join Date: Mar 2007
Model: 8700g
Carrier: T-mobile
Posts: 1
|
we were having the same issue with calendar events created on the BB device, they showed up in Outlook an hour later. Blackberry forgot to inform us that we needed to re-register the cdo.dll after applying the Exchange DST patch to our BES server.
I have a question about removing a software configuration from a user. So take for instance the DST patch manager v2.2, I created a software config package and sent it out OTAto roughly 200 devices. About 20 of them are not reporting correctly when run against the 2007DSTQuery.exe script saying taht they are awaiting patch when it says installed from the device. The updated patch manager v2.3 is supposed to fix that and report correctly. The dilema is that if we go ahead and update the files of the software config package it will be pushed to all devices and force them to reboot. This is not good in our environment.
If I remove the 180 user devices that have the patch applied from the DST software config package will the patch uninstall?? My thinking is that I should remove the 180 devices that have the patch installed, then update the software config files with the v2.3 patch manager files and that will sent the update to the remaining 20 that are giving us issues. SO only those 20 are forced to reboot. I haven't played around with the wireless software config feature too much but it makes sense to me that if you apply something OTA to a device you can remove something OTA from a device if you remove the device from that specific config.
Maybe someone can shed some light on this for me?
Thanks and yes this is my first post sorry for the long winded version..
|
Offline
|
|
03-16-2007, 05:04 AM
|
#588
|
Feeling Blue, Bigly ;->
Join Date: Jan 2007
Location: U to the K
Model: 9000
PIN: 3, it's the magic number
Carrier: Most of them, it's a Global Village man!
Posts: 1,273
|
Quote:
Originally Posted by tinman
we were having the same issue with calendar events created on the BB device, they showed up in Outlook an hour later. Blackberry forgot to inform us that we needed to re-register the cdo.dll after applying the Exchange DST patch to our BES server.
I have a question about removing a software configuration from a user. So take for instance the DST patch manager v2.2, I created a software config package and sent it out OTAto roughly 200 devices. About 20 of them are not reporting correctly when run against the 2007DSTQuery.exe script saying taht they are awaiting patch when it says installed from the device. The updated patch manager v2.3 is supposed to fix that and report correctly. The dilema is that if we go ahead and update the files of the software config package it will be pushed to all devices and force them to reboot. This is not good in our environment.
If I remove the 180 user devices that have the patch applied from the DST software config package will the patch uninstall?? My thinking is that I should remove the 180 devices that have the patch installed, then update the software config files with the v2.3 patch manager files and that will sent the update to the remaining 20 that are giving us issues. SO only those 20 are forced to reboot. I haven't played around with the wireless software config feature too much but it makes sense to me that if you apply something OTA to a device you can remove something OTA from a device if you remove the device from that specific config.
Maybe someone can shed some light on this for me?
Thanks and yes this is my first post sorry for the long winded version..
|
I am a bit confused but the following should apply - for every user you set a config against in the h/h config tool, just remove that DST config from them. the patch is applied already and you were never pushing the patch, just the patching app (helper). There is no reason to leave them on that config but note that you can use the latest verison of the DSTQuery tool to move all these guys to a new config, e.g. back to your standard.
__________________
I was a BES and Exchange admin once.
Then my world turned Blue.
|
Offline
|
|
03-16-2007, 02:00 PM
|
#589
|
Talking BlackBerry Encyclopedia
Join Date: Aug 2006
Model: 9000
Carrier: AT&T
Posts: 228
|
Sorry, meant to update my previous post and forgot. Got my issues fixed by updating Exchange 2003 System Manager to SP2 and 926666. Our main Exchange server was all up to date, but the System Manager tools on the BES were out of date. Still needed SP3 for proper Pearl drivers anyway, so I'm glad everything is finally up to date.
|
Offline
|
|
03-22-2007, 02:29 PM
|
#590
|
Talking BlackBerry Encyclopedia
Join Date: Jul 2006
Model: 8800
Carrier: Rogers
Posts: 216
|
Anyone ever run into this issue?
1) Installed DST 2007 patch to 8700r v4.1.0.284
2) Upgraded handheld code on 8700r to v4.1.0.351
After handheld code upgrade, it says "DST 2007 patch manager running..." when I check Options, About, DST 2007! It never says "DST 2007 patch applied".
Only way around this was to wipe the handheld, upgrade the handheld code to v4.1.0.351 AND THEN apply the DST 2007 patch. Can anyone relate?
__________________
Novell GroupWise 6.5 SP6
Blackberry Enterprise Server v4.1.2 Hotfix 3
Windows Server 2003 R2 SP1, SQL Server 2005
|
Offline
|
|
03-26-2007, 06:00 PM
|
#591
|
New Member
Join Date: Mar 2007
Location: San Diego, CA
Model: 8100
Carrier: T-Mobile
Posts: 11
|
Quote:
Originally Posted by dropscience
Anyone ever run into this issue?
1) Installed DST 2007 patch to 8700r v4.1.0.284
2) Upgraded handheld code on 8700r to v4.1.0.351
After handheld code upgrade, it says "DST 2007 patch manager running..." when I check Options, About, DST 2007! It never says "DST 2007 patch applied".
Only way around this was to wipe the handheld, upgrade the handheld code to v4.1.0.351 AND THEN apply the DST 2007 patch. Can anyone relate?
|
Have you run the dstquery.exe? I encountered quite a few of my handhelds that received the helper, but got stuck on running... it then showed "error" in the dstquery logs. Your best bet will be to plug it to a workstation via usb and run the patch loader website.
|
Offline
|
|
03-27-2007, 10:17 AM
|
#592
|
New Member
Join Date: Aug 2005
Model: 7250
Posts: 10
|
Well, still having issues...
Hey, all! Read through the list, and haven't had any real success yet on several of our company 7250s. Basically we've got a bunch of 7250's out there, and Exchange 2k3 and BES on the back end. Both Exchange and BES have been updated.
Some of the handhelds took the push fine, but others didn't. I manually installed the DST 2k7 patch on one handheld that didn't take, and it's times are still off (appointment times in Outlook/Exchange are fine).
Any tricks? What does it take to get this thing working correctly?
Thanks much for any ideas...
Steve
|
Offline
|
|
03-27-2007, 10:47 AM
|
#593
|
iPhone Convert
Join Date: Oct 2005
Location: Tulip City - MI
Model: iP5
OS: 6.0.2
PIN: to beans
Carrier: I'm not
Posts: 13,878
|
Hi Solo,
On the BES, did you register the CDO.DLL in the exchsrvr\bin folder AND the system32 folder (and make sure they are the same version)? I had the same issue until I did this.....
__________________
No longer a BES Admin, but it was fun while it lasted!
|
Offline
|
|
03-27-2007, 11:02 AM
|
#594
|
New Member
Join Date: Aug 2005
Model: 7250
Posts: 10
|
Quote:
Originally Posted by juwaack68
Hi Solo,
On the BES, did you register the CDO.DLL in the exchsrvr\bin folder AND the system32 folder (and make sure they are the same version)? I had the same issue until I did this.....
|
No I haven't, but I'll look into having our Exchange and BES admins do this! Thanks for the suggestion!
Steve
|
Offline
|
|
03-28-2007, 10:42 AM
|
#595
|
BlackBerry Extraordinaire
Join Date: Jul 2005
Location: MA
Model: 9930
PIN: PM Me!
Carrier: VZW
Posts: 1,073
|
Anyone doing any plans this weekend as this would have been the real DST time change?
|
Offline
|
|
03-28-2007, 10:57 AM
|
#596
|
Feeling Blue, Bigly ;->
Join Date: Jan 2007
Location: U to the K
Model: 9000
PIN: 3, it's the magic number
Carrier: Most of them, it's a Global Village man!
Posts: 1,273
|
Quote:
Originally Posted by jletendre
Anyone doing any plans this weekend as this would have been the real DST time change?
|
Planning to get drunk and plan which theme parks to visit while at the WES :->
__________________
I was a BES and Exchange admin once.
Then my world turned Blue.
|
Offline
|
|
03-29-2007, 08:07 AM
|
#597
|
Wireless Sith Lord
Join Date: Jan 2007
Location: Online
Model: iOS 6
Carrier: Verizon x2
Posts: 1,458
|
Quote:
Originally Posted by stuwhite
Planning to get drunk and plan which theme parks to visit while at the WES :->
|
w00t.
Disney (4 theme parks)
Universal (2 theme parks)
__________________
DarthBBerry
6-Time BlackBerry World Champion (2007-2012)
BlackBerry® Certified Support Specialist v5.0
BlackBerry® Certified System Administrator v5.0
|
Offline
|
|
03-30-2007, 08:58 AM
|
#598
|
Thumbs Must Hurt
Join Date: Aug 2004
Model: 9700
Carrier: T-Mobile
Posts: 50
|
Quote:
Originally Posted by jletendre
Anyone doing any plans this weekend as this would have been the real DST time change?
|
Just curious if anyone has confirmed the clocks will not be pushed ahead 1 hour this weekend.
The Prophet
|
Offline
|
|
03-30-2007, 09:48 AM
|
#599
|
Feeling Blue, Bigly ;->
Join Date: Jan 2007
Location: U to the K
Model: 9000
PIN: 3, it's the magic number
Carrier: Most of them, it's a Global Village man!
Posts: 1,273
|
Quote:
Originally Posted by The Prophet
Just curious if anyone has confirmed the clocks will not be pushed ahead 1 hour this weekend.
The Prophet
|
Why would they be pushed ahead if you have patched all your systems? The "old" DST date is irrelevant this year.
__________________
I was a BES and Exchange admin once.
Then my world turned Blue.
|
Offline
|
|
03-30-2007, 10:08 AM
|
#600
|
Thumbs Must Hurt
Join Date: Aug 2004
Model: 9700
Carrier: T-Mobile
Posts: 50
|
Quote:
Originally Posted by stuwhite
Why would they be pushed ahead if you have patched all your systems? The "old" DST date is irrelevant this year.
|
That depends on how much you trust RIM/MSFT to update their software correctly.
Remember, this change took most of IT by surprise and many vendors (not pointing fingers specifically at RIM) released fixes that were not exactly ready.
Odds are nothing will happen....but what if.....?
|
Offline
|
|
|
|