Re: Membership in Admin groups resets Send As permissions - Blackberry
- From: "Phil McNeill" <philmcneill@xxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 22 Jun 2006 12:04:54 -0400
That's two months in a row that an Exchange patch has killed BES. I'm sure
it's just an accident though. Hopefully, for Microsoft's sake, the judge
will see it the same way.
I have to wonder when Exchange patches will start killing competing
anti-virus products as well, now that MS has branded it's name on Antigen...
"John T." <John T.@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:2722FDD8-F7C1-4359-A388-1AE463065EF0@xxxxxxxxxxxxxxxx
I've been on the phone numerous times since installing the hotfix with
Microsoft. It seems they don't care about how this affects people. We
use
GoodLink and have similar problems. All my IT staff people use GoodLink
via
Treo's and there's no way for them to work normally without them. Had to
uninstall the patch.
According to them, they have had customer feedback stating they didn't
want
those protected groups having Send As rights. Well, what if a company
DOES
want those protected groups to have that?
Another thing - the KB article and Security notification says the update
fixes a OWA vulnerability. Why would Microsoft put a change this drastic
in
a hotfix for a code vulnerability. According to their own definitions,
hotfixes address code problems, they aren't designed to make fundamental
changes to how things work.
I'm extremely frustrated with Microsoft on this one. Why didn't they just
fix the OWA issue and put a download on the Microsoft Downloads site for
customer who WANTED to change how Send As works for protected groups?
Wouldn't that have made more sense?
I feel your pain, I really do. I'm right there with you.
John
"John D. Gwinner" wrote:
Ok, this is an odd one.
Blackberry Enterprise Server (BES 4.0, SP4, HF 3, i.e. version 4.0.4.5)
Exchange 2003, SP2, 2003 native mode domain.
Using the script in http://support.microsoft.com/kb/912918/en-us (KB
Article
912918) per the latest security patch, I attempted to set the 'send as'
permission.
Everyone works but 4 people. I removed 2 of the people from
administrative
groups, and the script works.
What happens is that about 5-10 minutes after I grant the Blackberry
service
accounts permission to 'send as' ... they revert to not having 'send as'
permission.
The other, non admistrator, users work fine.
I called Blackberry support, and they said that Microsoft had 'hard
coded'
it so that Administrators CANNOT use Blackberry's. Apparently
administrators will no longer be able to have another account have 'send
as'
authority.
Obviously, one possible 'best practice' is to remove my 'normal' account
from admin groups and have a second account used only for administration,
but NOTHING should remove a permission I have explicitly set without some
kind of warning.
Also, this basically forces any admin to have 2 accounts, otherwise they
won't get notifications about critical events, given that their
blackberry's
are non operational with administrator accounts.
Now I'll be typing my password 100's of times a day.
It's extremely frustrating to me that this 'feature' is being jammed down
our throats.
Thoughts?
== John ==
.
- Follow-Ups:
- Re: Membership in Admin groups resets Send As permissions - Blackberry
- From: Phil McNeill
- Re: Membership in Admin groups resets Send As permissions - Blackberry
- References:
- Prev by Date: Delay after connecting w/ RPC over HTTPS
- Next by Date: Re: Delay after connecting w/ RPC over HTTPS
- Previous by thread: RE: Membership in Admin groups resets Send As permissions - Blackberry
- Next by thread: Re: Membership in Admin groups resets Send As permissions - Blackberry
- Index(es):
Relevant Pages
|
Loading