Just for the record, it was that sec group.
I ended up blowing it away, recreating as a DL and it works fine now.

-----Original Message-----
From: Martin Blackstone [mailto:[EMAIL PROTECTED] 
Sent: Thursday, May 08, 2008 10:46 AM
To: NT System Admin Issues
Subject: RE: Acct Losing Rights

He is a member of a DL that was setup by someone as a security group.
That group had no BES Admin perms in it.

I turned the security group into a distribution group (cause that's all it
is), gave BES Admin the rights to that DL for the heck of it, then saved
that.
Went back to his acct, threw the switch to 0 and reinherited the perms.

Lets see what happens now.

-----Original Message-----
From: Michael B. Smith [mailto:[EMAIL PROTECTED] 
Sent: Thursday, May 08, 2008 10:40 AM
To: NT System Admin Issues
Subject: RE: Acct Losing Rights

adminCount is one again?

I think that, even thought you've already checked, you need to go back and
look at his group memberships again - and the nested group situation.

Is inheritance on the user object enabled?

After those two - it's deep voodoo. But I have links and references.

Regards,

Michael B. Smith
MCSE/Exchange MVP
http://TheEssentialExchange.com


-----Original Message-----
From: Martin Blackstone [mailto:[EMAIL PROTECTED] 
Sent: Thursday, May 08, 2008 1:35 PM
To: NT System Admin Issues
Subject: RE: Acct Losing Rights

It flipped back. What now?

-----Original Message-----
From: Michael B. Smith [mailto:[EMAIL PROTECTED] 
Sent: Thursday, May 08, 2008 7:19 AM
To: NT System Admin Issues
Subject: RE: Acct Losing Rights

He's got the adminCount attribute set on his account. He may not be a member
of a restricted group NOW, but at some point he was.

Reset it to zero with ADSI Edit.

If it flips back after you do THAT - then he somehow IS a member of a
restricted group.

Regards,

Michael B. Smith
MCSE/Exchange MVP
http://TheEssentialExchange.com


-----Original Message-----
From: Andy Shook [mailto:[EMAIL PROTECTED] 
Sent: Thursday, May 08, 2008 10:11 AM
To: NT System Admin Issues
Subject: RE: Acct Losing Rights

What flavor of Exchange and Windows?  Is this guy a member of another
group/OU that the others are not?

Shook
-----Original Message-----
From: Martin Blackstone [mailto:[EMAIL PROTECTED] 
Sent: Thursday, May 08, 2008 10:07 AM
To: NT System Admin Issues
Subject: Acct Losing Rights

We are deploying BES here right now and I have run into a snag with one
user.

BES Admin acct has send as perms on all AD accts. I followed the 912918
KB
and used the How to grant the Send As permission for multiple accounts.
This has worked for everyone but on guy. It doesn't show up in his.
I've also noticed that the "Allow inheritable permissions" was unchecked
and
rechecked it. The BES Admin acct comes back and it works. Then it
disappears. The allow box is unchecked. He is not an admin. Just a
domain
user.
 
So I open his acct, click the security tab and add the BES Admin acct
and
give it send as perms.
That occurs and then he can send.
But a few hours later, that perm disappears. Put it back, works, then
disappears.


I'm kind of at a loss here as to what is going on. Why does this one
acct
keep tossing the new perms?


~ Upgrade to Next Generation Antispam/Antivirus with Ninja!    ~
~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm>  ~

~ Upgrade to Next Generation Antispam/Antivirus with Ninja!    ~
~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm>  ~


~ Upgrade to Next Generation Antispam/Antivirus with Ninja!    ~
~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm>  ~


~ Upgrade to Next Generation Antispam/Antivirus with Ninja!    ~
~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm>  ~


~ Upgrade to Next Generation Antispam/Antivirus with Ninja!    ~
~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm>  ~


~ Upgrade to Next Generation Antispam/Antivirus with Ninja!    ~
~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm>  ~


~ Upgrade to Next Generation Antispam/Antivirus with Ninja!    ~
~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm>  ~

Reply via email to