[T1berious]

Hi,

I'm a BlackBerry newbie admin (The most I've done is restart services etc and add new users \ devices), Unfortunately since applying the DST patch some users can't send mail (myself included). I've seen lots of threads regarding this issue but I can't see a definitive fix for it.

Really could do with some help fixing this as I'm having a hard time resolving it.

Many thanks

T1b

[JPenrose]

Originally Posted by T1berious

Hi,

I'm a BlackBerry newbie admin (The most I've done is restart services etc and add new users \ devices), Unfortunately since applying the DST patch some users can't send mail (myself included). I've seen lots of threads regarding this issue but I can't see a definitive fix for it.

Really could do with some help fixing this as I'm having a hard time resolving it.

Many thanks

T1b

Do you see a red X beside mail you try to send from the handheld? Are you in a Microsoft Exchange/Active Directory environment? This is a common issue with BB users that are also members of AD 'protected groups'.

If this describes your sitch then I'll give you the fix that has worked for most.

-J

[ojai00]

Have you tried generating a new encryption key? This usually will do the trick. I recently had a problem where a user could send and receive but could not reply to an e-mail. He received a red "x" whenever he tried to do so. It turned out he had two service book entries and I guess the Blackberry was getting confused. I deleted both service book entries and resent the service books and that fixed the issue.

[T1berious]

Originally Posted by JPenrose

Do you see a red X beside mail you try to send from the handheld? Are you in a Microsoft Exchange/Active Directory environment? This is a common issue with BB users that are also members of AD 'protected groups'.

If this describes your sitch then I'll give you the fix that has worked for most.

-J

Yes! a big reg X greets me! A fix would be cool! Yes its an Exchange/AD environment (I'm the windows guy) (2003) running BES

[T1berious]

Originally Posted by ojai00

Have you tried generating a new encryption key? This usually will do the trick. I recently had a problem where a user could send and receive but could not reply to an e-mail. He received a red "x" whenever he tried to do so. It turned out he had two service book entries and I guess the Blackberry was getting confused. I deleted both service book entries and resent the service books and that fixed the issue.

Hi, my issue is different as you can't send any mail, you receive but not send. this all happened after the DST patch was installed.

[dogmaticvox]

Originally Posted by T1berious

Yes! a big reg X greets me! A fix would be cool! Yes its an Exchange/AD environment (I'm the windows guy) (2003) running BES

Are all of your devices experiencing this or only domain admins, etc. with blackberries?

If all of your devices are experiencing this problem, then you need to apply the "send as" permission to all your users for your bes admin account. Open up AD Users and Comps and select View from your file menu and make sure "Advanced Features" is checked. Now select the OU you have your users in and go to properties. Then select Security tab and click Advanced. In the Permissions tab, click Add and enter your BES admin account. Now "Apply onto" should be set to User Objects. Now grant the BES admin account "send as" permission. All your users in this OU should now inherit this permission. You can now check by going to one of your users and selecting properties and looking at the security tab (which you can only see if advanced features is turned on). Now go to advanced, see if your BES admin account has the "send as" permission... you can also check this in the effective permission tab.

If any of your Domain Admins, etc. have Blackberries, the Send As permission will not hold for more than one hour. In order to fix this, you will need to make some changes to the AdminSDHolder... check this KB with Microsoft: KB907434

Hope this helps!

[T1berious]

Hi,

I did that and ran the batch file after installing support tools etc. Unfortunately I get an error generated

The application, C:\Program Files\Support Tools\dsacls.exe, generated an application error The error occurred on 03/28/2007 @ 09:46:02.320 The exception generated was c0000005 at address 77BD8DF3 (msvcrt!wcschr)

Am I better of just putting in the objects in AD? as dsacls doesn't seem to be working. Arghhhh!!

[theitdude]

Not sure why you got that crash with the dsacls tool. Mine did the trick for the domain admins red-x issue.

can you manually type the dsacls command (don't have it with me now) with out the /G grant. It should at least give you a list of the ACLs without crashing.

Try it from another system. I applied mine from a workstation.

[T1berious]

Cheers, I'll give that a whirl!

Many thanks

T1b

[T1berious]

Hey DogmaticVox

Thats working! how long till the the permissions are removed? If they are removed which hopefully they won't

Many thanks for all your help!

[dogmaticvox]

Originally Posted by T1berious

Hey DogmaticVox

Thats working! how long till the the permissions are removed? If they are removed which hopefully they won't

Many thanks for all your help!

If a full hour passes and the permissions are still there, then you're in the clear.

Glad it worked, no problem!

[str86diesel]

Originally Posted by JPenrose

Do you see a red X beside mail you try to send from the handheld? Are you in a Microsoft Exchange/Active Directory environment? This is a common issue with BB users that are also members of AD 'protected groups'.

If this describes your sitch then I'll give you the fix that has worked for most.

-J

I actually have this same problem as well with the new cdo.dll. Can I ask what is the work around that you are referring to for protected groups? I actually went around the system and created a second account for our protected group users and then tied the email account back. Is there an easier way to just give the send as permission to a protected group. I really haven't had time to sit down and mess with the dsacl. Is that the fix?

Does anyone have the statement handy, where I can just throw it in and call it good?

Thanks
Kev

EDIT: nevermind on the DSACL's...got it taken care of

dsacls "cn=adminsdholder,cn=system,dc=mydomain,dc=com " /G "\SELF:CA;Send As"
dsacls "cn=adminsdholder,cn=system,dc=<mydomain>,dc=c om" /G "\SELF:CA;Receive As"
dsacls "cn=adminsdholder,cn=system,dc=<mydomain>,dc=c om" /G "\SELF:CA;Change Password"
dsacls "cn=adminsdholder,cn=system,dc=<mydomain>,dc=c om" /G "\SELF:RPWP;Personal Information"
dsacls "cn=adminsdholder,cn=system,dc=<mydomain>,dc=c om" /G "\SELF:RPWP;Phone and Mail Options" dsacls "cn=adminsdholder,cn=system,dc=<mydomain>,dc=c om" /G "\SELF:RPWP;Web Information"
dsacls "cn=adminsdholder,cn=system,dc=mydomain,dc=com " /G "\BlackBerrySA:CA;Send As"