[PacketRat]

Is anyone seen any problems with the patch MS06-029 on exchange. There seems to be a high number of issues due to this patch.


Thanks

[NJBlackBerry]

A quick search yielded this information: http://www.blackberryforums.com/sear...archid=1079637

Yes, Ms06-029 breaks BES...

[d_fisher]

Information about this update is also on the main page of the BlackBerry Technical Knowledge Center.
http://www.blackberry.com/knowledgec...nc=llworkspace

[RIM - BBTECH]

Actually it breaks the send on behalf of permissions within the Microsoft Exchange enviroment.

[NJBlackBerry]

Absolutely right; I was taking a swipe at my friends in Redmond....

[mayor111]

Man we are having one hell of a time fixing this problem at my office.

We fixed it, then we cant SEND again, then it was only the ADMIN accounts that cant SEND, now its everyone again...

We are going crazy. Anyone have any suggestions of what they did to fix it once and for all?

Thanks,

[JuneK]

Originally Posted by d_fisher

Information about this update is also on the main page of the BlackBerry Technical Knowledge Center.
http://www.blackberry.com/knowledgec...nc=llworkspace

Any idea why RIM set that document up so you can't print it from Adobe 7.0? Makes it tough to tick off the steps as you do them.

[geoWorm]

Originally Posted by JuneK

Any idea why RIM set that document up so you can't print it from Adobe 7.0? Makes it tough to tick off the steps as you do them.

Select all, copy, paste...

[HDClown]

I just dealt with this issue. The fix linked is fine if you are not a Blackberry user with elevated domain access (such as being a Domain Admin). RIM would love for you to just remove your elevated access and use some other account, psha right.

AdminSDHolder permissions will remove Send As from any user with elevated access. DSACLS can be used to correct this. This used to be in the MS KB, but it was removed in revised version.

Run this, wait about 2 hours, restart your BES Router Service, and you should be good

dsacls "cn=AdminSDHolder,cn=system,dc=domain,dc=com" /G "netbiosdomain\besadminuser:CA;Send As"

This, combined with granted Send As to your besadminuser (and making sure that user itself has no elevated access, it doesn't need it anyway for BES purposes) will fix you up good.