[doctortt]

Maintenance release 2 has just released for SP6. MR1 released not long ago. What's the deal here? Can we skip MR1 and install MR2 directly?

[TreeDude]

You can skip MR1 if you have not installed it yet. MR2 will have all the same fixes as MR1. I just installed MR2 last night, no issues at all.

[doctortt]

Cool dude. Thanks a lot.

[knottyrope]

Here is the link for exchange and lotus notes, groupwise not released yet.

https://www.blackberry.com/Downloads/entry.do

or

https://www.blackberry.com/Downloads...7224027CE111BC

[TreeDude]

Bad link knotty.

[phonemonkey]

If a MR is labelled "rollup" then it will include any prior MRs. I think this happens 100% of the time.

Hotfixes do not include prior hotfixes, so you would have to install those in order.

[m4ilm4n]

I checked the list of patches exclusive to MR2, and since none are earth-shatteringly required I'll hold off a while.

[JavaJunkee]

I like this fix. I've got some high profile execs with Bolds', that I was unable to setup pending message thresholds in the BB Monitoring Service. Sounds like this will resolve the issue.

*SDR 210995
In BlackBerry Enterprise Server version 4.1 SP6, the BlackBerry Enterprise Server reported the BlackBerry 9000 series on a 3G network as “unknown”, which caused the BlackBerry Monitoring Service to show the BlackBerry 9000 device users as “Filtered” and did not allow monitoring or reporting.
In BlackBerry Enterprise Server version 4.1 SP6, this issue is resolved.

[doctortt]

Just spoke with RIM. You can just install MR2 over SP6 - no need MR1.

Originally Posted by doctortt

Just spoke with RIM. You can just install MR2 over SP6 - no need MR1.

That's what TreeDude (and phonemonkey) told you two days ago.

[doctortt]

Well, I know you guys are better than RIM support.

[doctortt]

Originally Posted by JavaJunkee

I like this fix. I've got some high profile execs with Bolds', that I was unable to setup pending message thresholds in the BB Monitoring Service. Sounds like this will resolve the issue.

*SDR 210995
In BlackBerry Enterprise Server version 4.1 SP6, the BlackBerry Enterprise Server reported the BlackBerry 9000 series on a 3G network as “unknown”, which caused the BlackBerry Monitoring Service to show the BlackBerry 9000 device users as “Filtered” and did not allow monitoring or reporting.
In BlackBerry Enterprise Server version 4.1 SP6, this issue is resolved.

Just curious, is this a problem if the user is not on a 3G network but just regular EDGE?

[jibi]

Originally Posted by doctortt

Well, I know you guys are better than RIM support.

I'm not sure on your level of support with RIM, but my guess is that it would not be high enough to validate your sarcasm. I'm not slamming RIM's first tier support (or possibly even second tier), but I would say that people like TreeDude are more knowledgeable than the 'RIM support' you deal with.

...not to mention that you could have found this out very easily online:

http://na.blackberry.com/eng/support...enance_FAQ.pdf

Q: Must I apply the latest rollup or apply every MR in order?
A: Both types of MRs are cumulative. For example, MR3 includes all the fixes released in MR1 and MR2, regardless of whether MR1 and MR2 were rollups or hotfixes; furthermore, the Release Notes detail the fixes in the MR.

@phonemonkey, although the former term 'hotfix' was changed to 'maintenance release', it still remains as a cumulative update (in addition to the 'rollup' releases). The 'quickfix' releases may be what you're thinking of, and they are not cumulative.

[curriertech]

Upgraded without incident.

[JavaJunkee]

Originally Posted by doctortt

Just curious, is this a problem if the user is not on a 3G network but just regular EDGE?

Excellent question. I'm not sure.

Currently, all my Bold users are affected.

I know some had forced an EDGE connection, while we were troubleshooting some 3G reception issues. I don't recall the Monitoring Service picking up the devices during those EDGE tests.

[knottyrope]

Wierd got a "can not remove a service and BES has to reboot" window.
Click ok and now have reboot the server and rerun setup again window.

Weird, I stoppeded off all BES services before upgrading.

Doing reboot.

[knottyrope]

on reboot only attachment and synchronizer were present and set to manual

started MR2 update again and it finished this time.

Needed to restart BES again.

Wonder if this is because I am on server 2000.

[laskint]

Originally Posted by knottyrope

on reboot only attachment and synchronizer were present and set to manual

started MR2 update again and it finished this time.

Needed to restart BES again.

Wonder if this is because I am on server 2000.

Same thing happened on my install. A service wouldn't stop. After the reboot, I continued with no problems.

[Inphektion]

Originally Posted by knottyrope

on reboot only attachment and synchronizer were present and set to manual

started MR2 update again and it finished this time.

Needed to restart BES again.

Wonder if this is because I am on server 2000.

This happens to me on every MR or SP update. I'm on server 2003. I don't consider it a problem though, figured it probably just wants to cleanly remove something registered with the system.

[JGonzalezGUS]

The same thing happens to me. I discovered my problem was SNMP service. I now stop it manually before trying to update BES.