[Jonathan Lefebvre]

Hey Guys!

I've been reading the topic for couple days to follow problem and solutions.
Unfortunatly, I haven't found the solution to my problem yet.

We are running :
BES 4.1.2
Domino 601 cf1
Patch manager 2.3

I've been able to create the Apps Configuration on the BES. Handhelds are receiving the update.. BUT now if I look in Option/2007 DST Patch, it is saying "2007 DST Patch Manager is running".

How much time should it take to download/install the patch on a blackberry?
It's now close to 24hours with that state.
I've looked in the document by RIM for different state on the installation. Unfortunatly, the state I have is not one of them.

I tried it on 3 different blackberry with 2 different provider (BELL and ROgers)

I called Rogers for support. They told me that patch manager 2.2 needed MDS activated but not 2.3. We don't want to activate MDS now, as we don't have time to check for that.

So it meens that the BB browser is not working, but the Bell/Rogers browser are working.

Any idea on what could be wrong?

Thanks

[stuwhite]

Originally Posted by Jonathan Lefebvre

Hey Guys!

I've been reading the topic for couple days to follow problem and solutions.
Unfortunatly, I haven't found the solution to my problem yet.

We are running :
BES 4.1.2
Domino 601 cf1
Patch manager 2.3

I've been able to create the Apps Configuration on the BES. Handhelds are receiving the update.. BUT now if I look in Option/2007 DST Patch, it is saying "2007 DST Patch Manager is running".

How much time should it take to download/install the patch on a blackberry?
It's now close to 24hours with that state.
I've looked in the document by RIM for different state on the installation. Unfortunatly, the state I have is not one of them.

I tried it on 3 different blackberry with 2 different provider (BELL and ROgers)

I called Rogers for support. They told me that patch manager 2.2 needed MDS activated but not 2.3. We don't want to activate MDS now, as we don't have time to check for that.

So it meens that the BB browser is not working, but the Bell/Rogers browser are working.

Any idea on what could be wrong?

Thanks

I think you have anwswered your own question. I will have to play hunt the doc but I do remember early on RIM saying that you had to use the BB browser. They said that others may work but there were issues and they wouldn't support anything other than the BB (MDS) one. I don't honestly think you can do this OTA without, but maybe someone else has had more success than us. If you really can't enable MDS, you will need to use the cable method. How many users are we talking about here?

[Jonathan Lefebvre]

Originally Posted by stuwhite

I think you have anwswered your own question. I will have to play hunt the doc but I do remember early on RIM saying that you had to use the BB browser. They said that others may work but there were issues and they wouldn't support anything other than the BB (MDS) one. I don't honestly think you can do this OTA without, but maybe someone else has had more success than us. If you really can't enable MDS, you will need to use the cable method. How many users are we talking about here?

We have close to 100 users...

I tried to figure out to configure MDS without success.
I've search on the net to find out how, but nothing helped me for MDS.
Any quick link for MDS?

thanks for the quick answer

[stuwhite]

Originally Posted by Jonathan Lefebvre

We have close to 100 users...

I tried to figure out to configure MDS without success.
I've search on the net to find out how, but nothing helped me for MDS.
Any quick link for MDS?

thanks for the quick answer

You know what, I just saw in the tutorial that they state "BB Browser, Internet Browser or WAP Browser" so it looks like they changed their minds (surprise surprise). The thing is that you won't get much help from RIM on the phone so not sure where to go next. I will have to dig deep to find MDS info but if you check the KB it shouldn't be too hard to find. I guess it comes down to whether you have enough time to play. Try a hard reset on the BB which still shows "running".

[Jonathan Lefebvre]

Originally Posted by Jonathan Lefebvre

We have close to 100 users...

I tried to figure out to configure MDS without success.
I've search on the net to find out how, but nothing helped me for MDS.
Any quick link for MDS?

thanks for the quick answer

I just found a way with the tech support from ROGERS.

If you don't want to use MDS, here what I did :
- Use patch manager 2.3
- Follow instruction from RIM for the BES configuration
- Once you see 2007 DST Patch in Option, delete the Service Book called
Desktop [IPPP]
- Remove the battery
- Go back and check the status is 2007 DST Patch, you should see Contacting web site, and after a couple second you will see Downloading...


What a wonderfull word to see... hmmm Downloading...

After the reboot, if you check back in Option/2007 DST patch you will see APPLIED!!!!!!!!!!!

Only problem I will face is the user must do this manually on their blackberry.
but, it'S working

Hope this will help

[stuwhite]

Originally Posted by Jonathan Lefebvre

I just found a way with the tech support from ROGERS.

If you don't want to use MDS, here what I did :
- Use patch manager 2.3
- Follow instruction from RIM for the BES configuration
- Once you see 2007 DST Patch in Option, delete the Service Book called
Desktop [IPPP]
- Remove the battery
- Go back and check the status is 2007 DST Patch, you should see Contacting web site, and after a couple second you will see Downloading...


What a wonderfull word to see... hmmm Downloading...

After the reboot, if you check back in Option/2007 DST patch you will see APPLIED!!!!!!!!!!!

Only problem I will face is the user must do this manually on their blackberry.
but, it'S working

Hope this will help

Fantastic, yet again we have to ask users to do all the work! Oh well, glad you found a solution man, sorry for the lack of useful info

[Jonathan Lefebvre]

Originally Posted by stuwhite

Fantastic, yet again we have to ask users to do all the work! Oh well, glad you found a solution man, sorry for the lack of useful info

Well RIM just release that Info to ROgers this morning...
They found it yesterday.

Now I understand why I wasn't able to find any information for my problem

[stuwhite]

Originally Posted by Jonathan Lefebvre

Well RIM just release that Info to ROgers this morning...
They found it yesterday.

Now I understand why I wasn't able to find any information for my problem

Welcome to DST my friend

[hippolove]

Running BES 4.06 hf4 for Domino

I followed all the instructions on the DST 2007 page.
created the software configuration and getting 'check required' in the status.
I am trying to push this out to my test group. 3 BBs. Have 150 total and only 3 days ..heheh

Does anyone knows what this error message means?

Thanks

[totalstu]

All my devices have received the helper and appear to have installed the patch. I few needed to actually click the update under options and click reboot, restart, or whatever. I can't get either the BES manager, dst query from patchmanager 2.2, or boxtone to report back the correct results.

At this point I'm letting the chips fall where they may.

[SoUnCool]

we decided to go for USB method of DST install, we have manpower to do this with devices and over 500 BB users to support, they are all over canada not in one location, and so far 100% sucess rate

[rpfeffer]

Originally Posted by SoUnCool

we decided to go for USB method of DST install, we have manpower to do this with devices and over 500 BB users to support, they are all over canada not in one location, and so far 100% sucess rate

Why would you do 500 people over USB and not wireless push?

[Sp!ke]

Well I've managed to kick my push into action.

Deleted the PacageCache folder, reindexed and restarted the policy service and after a 6 hour wait it sprang into action thank god. Only another 1500 handsets to do in 3 days.

I'm seeing about 5% of handhelds doing odd things but then I am not surprised as we have some odd handhelds out there such as the Siemans SK65 and a few running Nokia Connect software. I'll handle these rogue ones manually - some may need upgrading handsets.

Next question is whether there is a DSTQuery tool for a BES 3.6 server as we have a further 600 users stuck on a 3.6 BES due to having to use some bespoke software coded for 3.6. I've instructed them on the joys of updating them manually but I suspect most will ignore it.

Anyone?

[jkbusinessedge]

I have sent the patch to only a few users to start.
I am gettting an error;

in the csv file under dst 2007 it show v2.3, under patch stats it shows as error.
any ideas ?

[Pistol_Pete]

Originally Posted by juwaack68

What does 'Downgrade Required' mean? I've got a Cingular device (8700c with v4.1.0194) that is showing this.

It means the patch manager applied on the device is newer the patch manager installed on the server (Software Configuration).

[Pistol_Pete]

Originally Posted by tibbymstie

Has anyone gotten the 0x8D error yet?? The patch went through great on the Pearl, but this is a 7150T
I tried calling RIM, but there were 87 calls ahead of me!!
We're installing this wirelessly (which means there's VERY little documentation for errors) via the BES..
On the device itself, it does have a listing for "2007DST Patch", but in there all it says "Error installing 2007 DST patch."
I have tried re-downloading it from the device, but no luck.

EDIT: Forgot to mention, I'm on Lotus Notes 6.5.5 if that matters..

Just a hunch.. check device memory availability.. Remove a few features like Memo Pad, Tasks, Language etc. and try again.

[SoUnCool]

Originally Posted by rpfeffer

Why would you do 500 people over USB and not wireless push?

we have lot of old devices already running low on memmory and wireless push didnt seem to work on them, plsu most devices have just 4.0 device OS, upgrading them all just before patch is pain

[Pistol_Pete]

-invokesync is a switch only available on the new DST2007Query Tool v4.1.2.8. This will not work on older versions.

According to the release notes, you will need to:

1. Run the DST2007Query.exe
2. Check for BB devices that report the 'Awaiting Patch' state
3. After business hours, run the DST2007Query Tool with -invokesync
4. Restart the BlackBerry Synchronization Service.
5. Once the data has sync'd, run the DST2007Query Tool again (several hours later).

My numbers went from 81 devices applied to 121 overnight.

[stuwhite]

Originally Posted by jkbusinessedge

I have sent the patch to only a few users to start.
I am gettting an error;

in the csv file under dst 2007 it show v2.3, under patch stats it shows as error.
any ideas ?

I've got about 5% "error" rate but they are virtually all fine, when you check the h/h. The link seems to be that these devices wouldn't take the patch OTA and had to be done USB.

[halflife78]

Originally Posted by stuwhite

I am so gonna get lynched here but I really need to clear something up for the guys who have joined this thread recently. I have seen a few posts about the "up-to-date status" in the h/h config tool against what you see in DST query. I have explained a few times but I fear a few people are getting overly confused and stressed!

In short, the application you are pushing to the BB is NOT the patch. It is the Patch Helper, which contacts RIM and downloads the required patch for your device. Everything you see in the h/h config tool relates to getting the app on the BB, so the patch download can be automated. You are not pushing the patch, you are pushing the facility to download the patch. Seeing up-to-date in the h/h config just means the helper app is up to date in relation to the one you are pushing using the s/ware config, nothing else. If the BB has 2.2 and then you change the policy to push 2.3, it will no longer be up to date.

DSTQuery queries your BES db and pulls the status of the patch, as sent by the BB. "Applied" and "Awaiting" relate to the patch, and "Helper not installed" relates to the helper app. We know there are reporting issues but the problem is mainly with the BB sending the wrong status, not the actual DSTQuery (remember it is only reading what is in the db). Yes DSTQuery has some issues but essentially, the units aren't telling us the trust OTA. RIM have stated many times that the h/h wins so if it says applied on the actually BB, that's it, job done. I myself have many BBs showing in the db with an incorrect status but this is mainly because it isn't telling the db. It doesn't matter what you see anywhere on a server, if the actuall h/h says it is applied, it is.

Don't get me wrong, I am no expert and may well have missed something major which am happy to be corrected on, but I see a lot of folks checking the h/h config status against dstquery and jumping to the wrong conclusion. Sorry for the lecture but as we have had all the pain for 3 weeks, I guess we have to try and help the late comers (although you do owe us stress-beer :->)

OK, off to hide now.

I used the above to judge whether the patches got downloaded, the reason being I ran a test bed of 20 devices and used the above to judge whether they completed and everyone that was up to date the next day on the above was patched on the device after me checking.

I just send the configuration out to the last 20 people of 400 so I am done basically, if we have issues we have issues, I worked this to the best of my ability seeing as I got the server thrown on me when I started here. My boss didn't want me to patch people at all, he just told me to have them manually change their time so I went further to try and help this issue than I was required to go.