[DarthBBerry]

Originally Posted by stuwhite

Anytime man. Yeah most of my "errors" are actually fine and like you, I think most of the awaitings are done. Remember that the Up to Date on the h/h config just means the helper is on though, not the patch.

Even though it ways Up to Date on the server side and Awaiting Patch on the report side, I checked the Module view and it's there. That tells me that the reporting tool is pooched.

Originally Posted by stuwhite

aaah, you are getting so excited aren't you

Ya think? I'm truly looking forward to getting some direct answers to questions instead of a 2 hour hold time on the phone. Yeah, it's great that it's in Orlando, but honestly I want to do some server experimentation without breaking my production environment.

[DarthBBerry]

ACK! Double post! Sorry!

[stuwhite]

Originally Posted by DarthBBerry

Even though it ways Up to Date on the server side and Awaiting Patch on the report side, I checked the Module view and it's there. That tells me that the reporting tool is pooched.

I'm confused now. Everything in the h/h config is just reporting the status of the helper app, not the patch. So you know helper 2.2 is on there but DSTquery is separately telling you awaiting patch for the actual patch file. Ok so we know DSTquery might say awaiting when the BB has the patch but the module and s/ware config stuff on the BES doesn't relate in any way to the patch itself (unless I am missing something najor here!).

Originally Posted by DarthBBerry

Ya think? I'm truly looking forward to getting some direct answers to questions instead of a 2 hour hold time on the phone. Yeah, it's great that it's in Orlando, but honestly I want to do some server experimentation without breaking my production environment.

Yeah it will be good. If I do get to go, I need to get from 4.0 to 4.1 first, or my questions will be pretty pointless

[DarthBBerry]

Originally Posted by stuwhite

I'm confused now. Everything in the h/h config is just reporting the status of the helper app, not the patch. So you know helper 2.2 is on there but DSTquery is separately telling you awaiting patch for the actual patch file. Ok so we know DSTquery might say awaiting when the BB has the patch but the module and s/ware config stuff on the BES doesn't relate in any way to the patch itself (unless I am missing something najor here!).

Yeah, I'm confused too. But in my mass e-mail to folks, I said if they DON'T see "2007 DST patch applied" they should call our Help Desk right away. The Help Desk hasn't assigned me any requests for DST fixes.

Originally Posted by stuwhite

Yeah it will be good. If I do get to go, I need to get from 4.0 to 4.1 first, or my questions will be pretty pointless

That's one of my issues I'm gonna bring up. I want to change my database from MSDE to SQL, but I have to roll up to 4.1 first. I also want to change server hardware from the old machine to a nice, new sparkly powerhouse server. All at the same time. Now you know why I want to pin down somebody at WES instead of on the phone? LOL

[jrbes]

I had similar issues with the patch push, two entire servers did not get the push pushed properly and not a single device on that database got it. Three other servers are partially patched.

RIM's response so far is Option1. Remove all users from BES, Wipe, EA, and then it will be there. Option 2. Have the users download the link from the website and install.

The first is not an option! The second is an option but still not preferred, but we have to do something as all workstations have been patched and the devices have not...

[janusbegins]

So I pushed out my patches Friday night, and this Monday morning, only roughly half show that the patch was pushed out. This is the info that the query analyzer showed. So am I being impatient? there are no reported errors so far.

[stuwhite]

Originally Posted by janusbegins

So I pushed out my patches Friday night, and this Monday morning, only roughly half show that the patch was pushed out. This is the info that the query analyzer showed. So am I being impatient? there are no reported errors so far.

If the h/h config tool shows that the BB is up-to-date, you are cool as the patch helper is on there, so now you wait for the patch. If it isn't on there you might need to remove the s/w config and redo it for those users but that is just for the helper app, not the patch. Once the config says that the app is on fine, you get to sit back and wait for the BB to get the patch, reboot and report in (the last bit is the fun bit!).

[stuwhite]

Originally Posted by jrbes

I had similar issues with the patch push, two entire servers did not get the push pushed properly and not a single device on that database got it. Three other servers are partially patched.

RIM's response so far is Option1. Remove all users from BES, Wipe, EA, and then it will be there. Option 2. Have the users download the link from the website and install.

The first is not an option! The second is an option but still not preferred, but we have to do something as all workstations have been patched and the devices have not...

When you say "didn't get the patch pushed properly", is the issue with pushing the patch helper app to the BBs or that app then grabbing the patch from RIM? I would totally stay away from anything drastic with users, as every problem I have seen on this forum re DST so far has been fixed by simple tweaking or waiting. Quite frankly there is tons more BB DST knowledge here than with Tsupport, so I would browse through this thread rather than waste your time talking to them (sorry but I have lost any respect I had for RIM in the last 3 weeks). All my users got the helper without any probs, it was getting the patch which seemed to be the problem.

[stuwhite]

Originally Posted by DarthBBerry

Yeah, I'm confused too. But in my mass e-mail to folks, I said if they DON'T see "2007 DST patch applied" they should call our Help Desk right away. The Help Desk hasn't assigned me any requests for DST fixes.

Yeah exactly. I wrote a doc for our helpdesk and told them how to t/shoot. The very last step was "wipe the bloody thing and start again", as I don't see the point wasting hours over a single erroring device. I don't believe there has been a single case of that yet, although a lot of users have had to use the cable method to avoid the wipe scenario

[bbgirl]

Originally Posted by stuwhite

Yup, go and make some tea (it's what we do in the UK when we are bored) :->

Oh my god...I have three days..to do 300+ and not even two received yet.


I think I'm going to turn out my light and close my door and act like i'm not at work...

[bbgirl]

Originally Posted by DarienA

at the very end -invokesync. My handhelds were all over the place, many patched fine, one required a manual restart, one was stuck on patch mgr running... Again I'm glad we are a small company.

All the trouble handhelds I just plugged in to my own PC and did the USB install from the website.

I feel the pain of you larger blackberry orgs. Good luck.

I should probably do the ones, by cable I have in the bldg, huh? because at the rate of the wireless, I could probably fly out and take care of them the handhelds, I have in the field

[stuwhite]

Originally Posted by bbgirl

Oh my god...I have three days..to do 300+ and not even two received yet.


I think I'm going to turn out my light and close my door and act like i'm not at work...

LOL. I have 300 users and we asked users to manually patch last Tuesday, knowing that the push would be a nightmare. About 25% did it and then we started the push on Thursday. We now have about 80% done but it has taken that long....

[bbgirl]

Originally Posted by bbgirl

Oh my god...I have three days..to do 300+ and not even two received yet.


I think I'm going to turn out my light and close my door and act like i'm not at work...

another question, I keep going in and check my config status' and I see that the MDS service keeps getting disabled. Shouldn't this stay "enabled?"

I think someone else is logging on...mmm..

[bbgirl]

Originally Posted by stuwhite

LOL. I have 300 users and we asked users to manually patch last Tuesday, knowing that the push would be a nightmare. About 25% did it and then we started the push on Thursday. We now have about 80% done but it has taken that long....

Oh MY God. I like your signature...

so how many did you push it to, at a time?

[DarienA]

Originally Posted by bbgirl

I should probably do the ones, by cable I have in the bldg, huh? because at the rate of the wireless, I could probably fly out and take care of them the handhelds, I have in the field

Yeah I'd say any ones you have local access to, do them via USB cable. It's quick the download happens fast. The reboot still takes the same amt of time though.

[ces_john]

Like many of you, I have been working on this nonsense for days. This post has been very helpful but now I cannot see the forest through the trees.

Several units report "up to date" on the BES yet the query tool shows 0x43, indicating an HTTP 503 error. It sounds as though the RIM server responsible for serving the patchs is a little busy. If my understanding is correct then patience will get me through these.

Other h/h continue to report "helper not installed". This is particularly disconcerting as I have no idea where to go from here. These devices are identical, the BES is 4.1, there is only a "default" IT Policy. So I don't get the impression that is my problem.

Any help is appreciated.

[bbgirl]

Originally Posted by ces_john

Like many of you, I have been working on this nonsense for days. This post has been very helpful but now I cannot see the forest through the trees.

Several units report "up to date" on the BES yet the query tool shows 0x43, indicating an HTTP 503 error. It sounds as though the RIM server responsible for serving the patchs is a little busy. If my understanding is correct then patience will get me through these.

Other h/h continue to report "helper not installed". This is particularly disconcerting as I have no idea where to go from here. These devices are identical, the BES is 4.1, there is only a "default" IT Policy. So I don't get the impression that is my problem.

Any help is appreciated.

did you create an application policy. there is a setting that allows the handhelds to download externally from http... go over your configuration again, and make sure to go over the control policy too.

[Gotrek]

Originally Posted by bbgirl

did you create an application policy. there is a setting that allows the handhelds to download externally from http... go over your configuration again, and make sure to go over the control policy too.

I'm seeing the same thing 2000 users maybe 1500 have the patch manager 1000 have the patch applied.

The error 503 users clear up on there own over time. I suspected like you that the rim servers were just very busy. Our's cleared up.

I'm still seeing lot's of error 0x88 though.

[juwaack68]

I have downloaded the latest DSTQuery and will be running it tonight with the new -invokesync command. However, I noticed something odd when I compared the current DSTQuery results (run 30 minutes ago) with what I see in the HH Config Tool window.

I have a bunch of users who's Patch Status shows "Applied" w/ DSTQuery, but show the Application Status of "Upgrade Required", or "Downgrade Required" in the Config Tool. Huh??

I have other users who's Patch Status shows "Awaiting Patch", but show the App Status of "Up to date" in the Config Tool. Wait a minute....

I also have a few who show Patch Status of "Error", but show App Status of "Up to date" in the Config Tool. Really? How is that possible?

And I even have a couple who show a Patch Status "Helper Not Installed", but show "Up to date" in the Config Tool. Nice, this one is helps a lot.

At this point, I don't know what to believe. Telling everyone to just download it OTA is starting to look like a good idea, in retrospect.....

I had pushed v2.2 of the patch manager to everyone, so may take just those that are showing conflicting results and push 2.3 to them (after the DSTQuery runs again tonight).

[ces_john]

Originally Posted by bbgirl

did you create an application policy. there is a setting that allows the handhelds to download externally from http... go over your configuration again, and make sure to go over the control policy too.

I neglected to mention the 1/2 dozen or so that applied correctly. I do have an "application policy" in place. This would not be so frustrating if there was any consistency from one device to the next.

The idea of having users implement this (or any update) goes against everything you learn in Network Admin 101.