Exchange inherited permissions
up vote
0
down vote
favorite
We have situations where I would like to keep an AD account active for legal reasons for access to personal payroll data only. We would like to block access to everything else including the users own email yet keep the mailbox active.
Though there's a few things I could do manually to achieve this I would like to partially automate it. I've create an AD group with the intent of adding users to this with certain deny permissions within Exchange and AD. AD is OK as I have GPO's which 'Deny logon' to members of the group.
For Exchange I have run the following:
Get-MailboxDatabase -Identity "DB01" | Add-ADPermission -User "DOMAINDenyGroup" -AccessRights ExtendedRight -ExtendedRights Receive-As -Deny
The outcome of this for the particular user is:
Get-MailboxPermission BadUser
User AccessRights IsInherited Deny
---- ------------ ----------- ----
NT AUTHORITYSELF {FullAccess, ReadPermission} False False
DOMAINAdministrator {FullAccess} True True
DOMAINDomain Admins {FullAccess} True True
DOMAINEnterprise A... {FullAccess} True True
DOMAINOrganization... {FullAccess} True True
DOMAINDenyGroup {FullAccess} True True
NT AUTHORITYSYSTEM {FullAccess} True False
NT AUTHORITYNETW... {ReadPermission} True False
As can be seen, the DenyGroup (which the user is a member of) is denied FullAccess to the mailbox yet the user can still access email via OWA. I know that the NT AUTHORITYSELF {FullAccess, ReadPermission} still exists but I was hoping to have it working where I don't have to fiddle with this and the deny would take precedence.
Is there some form of precedence in regards to inherited permissions and permissions applied at the local object level? I would have thought an explicit Deny would override anything.
permissions exchange
asked Nov 30 at 6:14
Lexdon
61
add a comment |
up vote
0
down vote
favorite
We have situations where I would like to keep an AD account active for legal reasons for access to personal payroll data only. We would like to block access to everything else including the users own email yet keep the mailbox active.
Though there's a few things I could do manually to achieve this I would like to partially automate it. I've create an AD group with the intent of adding users to this with certain deny permissions within Exchange and AD. AD is OK as I have GPO's which 'Deny logon' to members of the group.
For Exchange I have run the following:
Get-MailboxDatabase -Identity "DB01" | Add-ADPermission -User "DOMAINDenyGroup" -AccessRights ExtendedRight -ExtendedRights Receive-As -Deny
The outcome of this for the particular user is:
Get-MailboxPermission BadUser
User AccessRights IsInherited Deny
---- ------------ ----------- ----
NT AUTHORITYSELF {FullAccess, ReadPermission} False False
DOMAINAdministrator {FullAccess} True True
DOMAINDomain Admins {FullAccess} True True
DOMAINEnterprise A... {FullAccess} True True
DOMAINOrganization... {FullAccess} True True
DOMAINDenyGroup {FullAccess} True True
NT AUTHORITYSYSTEM {FullAccess} True False
NT AUTHORITYNETW... {ReadPermission} True False
As can be seen, the DenyGroup (which the user is a member of) is denied FullAccess to the mailbox yet the user can still access email via OWA. I know that the NT AUTHORITYSELF {FullAccess, ReadPermission} still exists but I was hoping to have it working where I don't have to fiddle with this and the deny would take precedence.
Is there some form of precedence in regards to inherited permissions and permissions applied at the local object level? I would have thought an explicit Deny would override anything.
permissions exchange
asked Nov 30 at 6:14
Lexdon
61
Have you considered changing the user's "logon hours" to nothing, or expiring the password (or the whole account)?
– grawity
Nov 30 at 6:31
Your Exchange command denies Receive-As, not FullAccess. You could disconnect the Mailbox (it will be kept for a time depending on your configuration).
– Seth
Nov 30 at 8:39
Thanks but neither suit. Logon hours needs to be 'always' so they can get to payroll. Disconnect won't work as the mailbox needs to be active for others to read incoming and respond. I don't believe that Add-ADPermission has an AccessRight of FullAccess but Receive-As shows as FullAccess when a Get-MailboxPermission is run.
– Lexdon
Dec 3 at 3:51
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
We have situations where I would like to keep an AD account active for legal reasons for access to personal payroll data only. We would like to block access to everything else including the users own email yet keep the mailbox active.
Though there's a few things I could do manually to achieve this I would like to partially automate it. I've create an AD group with the intent of adding users to this with certain deny permissions within Exchange and AD. AD is OK as I have GPO's which 'Deny logon' to members of the group.
For Exchange I have run the following:
Get-MailboxDatabase -Identity "DB01" | Add-ADPermission -User "DOMAINDenyGroup" -AccessRights ExtendedRight -ExtendedRights Receive-As -Deny
The outcome of this for the particular user is:
Get-MailboxPermission BadUser
User AccessRights IsInherited Deny
---- ------------ ----------- ----
NT AUTHORITYSELF {FullAccess, ReadPermission} False False
DOMAINAdministrator {FullAccess} True True
DOMAINDomain Admins {FullAccess} True True
DOMAINEnterprise A... {FullAccess} True True
DOMAINOrganization... {FullAccess} True True
DOMAINDenyGroup {FullAccess} True True
NT AUTHORITYSYSTEM {FullAccess} True False
NT AUTHORITYNETW... {ReadPermission} True False
As can be seen, the DenyGroup (which the user is a member of) is denied FullAccess to the mailbox yet the user can still access email via OWA. I know that the NT AUTHORITYSELF {FullAccess, ReadPermission} still exists but I was hoping to have it working where I don't have to fiddle with this and the deny would take precedence.
Is there some form of precedence in regards to inherited permissions and permissions applied at the local object level? I would have thought an explicit Deny would override anything.
permissions exchange
asked Nov 30 at 6:14
Lexdon
61
We have situations where I would like to keep an AD account active for legal reasons for access to personal payroll data only. We would like to block access to everything else including the users own email yet keep the mailbox active.
Though there's a few things I could do manually to achieve this I would like to partially automate it. I've create an AD group with the intent of adding users to this with certain deny permissions within Exchange and AD. AD is OK as I have GPO's which 'Deny logon' to members of the group.
For Exchange I have run the following:
Get-MailboxDatabase -Identity "DB01" | Add-ADPermission -User "DOMAINDenyGroup" -AccessRights ExtendedRight -ExtendedRights Receive-As -Deny
The outcome of this for the particular user is:
Get-MailboxPermission BadUser
User AccessRights IsInherited Deny
---- ------------ ----------- ----
NT AUTHORITYSELF {FullAccess, ReadPermission} False False
DOMAINAdministrator {FullAccess} True True
DOMAINDomain Admins {FullAccess} True True
DOMAINEnterprise A... {FullAccess} True True
DOMAINOrganization... {FullAccess} True True
DOMAINDenyGroup {FullAccess} True True
NT AUTHORITYSYSTEM {FullAccess} True False
NT AUTHORITYNETW... {ReadPermission} True False
As can be seen, the DenyGroup (which the user is a member of) is denied FullAccess to the mailbox yet the user can still access email via OWA. I know that the NT AUTHORITYSELF {FullAccess, ReadPermission} still exists but I was hoping to have it working where I don't have to fiddle with this and the deny would take precedence.
Is there some form of precedence in regards to inherited permissions and permissions applied at the local object level? I would have thought an explicit Deny would override anything.
permissions exchange
permissions exchange
asked Nov 30 at 6:14
Lexdon
61
asked Nov 30 at 6:14
Lexdon
61
asked Nov 30 at 6:14
Lexdon
61
asked Nov 30 at 6:14
Lexdon
61
asked Nov 30 at 6:14
Lexdon
61
61
Have you considered changing the user's "logon hours" to nothing, or expiring the password (or the whole account)?
– grawity
Nov 30 at 6:31
Your Exchange command denies Receive-As, not FullAccess. You could disconnect the Mailbox (it will be kept for a time depending on your configuration).
– Seth
Nov 30 at 8:39
Thanks but neither suit. Logon hours needs to be 'always' so they can get to payroll. Disconnect won't work as the mailbox needs to be active for others to read incoming and respond. I don't believe that Add-ADPermission has an AccessRight of FullAccess but Receive-As shows as FullAccess when a Get-MailboxPermission is run.
– Lexdon
Dec 3 at 3:51
add a comment |
Have you considered changing the user's "logon hours" to nothing, or expiring the password (or the whole account)?
– grawity
Nov 30 at 6:31
Your Exchange command denies Receive-As, not FullAccess. You could disconnect the Mailbox (it will be kept for a time depending on your configuration).
– Seth
Nov 30 at 8:39
Thanks but neither suit. Logon hours needs to be 'always' so they can get to payroll. Disconnect won't work as the mailbox needs to be active for others to read incoming and respond. I don't believe that Add-ADPermission has an AccessRight of FullAccess but Receive-As shows as FullAccess when a Get-MailboxPermission is run.
– Lexdon
Dec 3 at 3:51
Have you considered changing the user's "logon hours" to nothing, or expiring the password (or the whole account)?
– grawity
Nov 30 at 6:31
Have you considered changing the user's "logon hours" to nothing, or expiring the password (or the whole account)?
– grawity
Nov 30 at 6:31
Your Exchange command denies Receive-As, not FullAccess. You could disconnect the Mailbox (it will be kept for a time depending on your configuration).
– Seth
Nov 30 at 8:39
Your Exchange command denies Receive-As, not FullAccess. You could disconnect the Mailbox (it will be kept for a time depending on your configuration).
– Seth
Nov 30 at 8:39
Thanks but neither suit. Logon hours needs to be 'always' so they can get to payroll. Disconnect won't work as the mailbox needs to be active for others to read incoming and respond. I don't believe that Add-ADPermission has an AccessRight of FullAccess but Receive-As shows as FullAccess when a Get-MailboxPermission is run.
– Lexdon
Dec 3 at 3:51
Thanks but neither suit. Logon hours needs to be 'always' so they can get to payroll. Disconnect won't work as the mailbox needs to be active for others to read incoming and respond. I don't believe that Add-ADPermission has an AccessRight of FullAccess but Receive-As shows as FullAccess when a Get-MailboxPermission is run.
– Lexdon
Dec 3 at 3:51
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1379657%2fexchange-inherited-permissions%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Have you considered changing the user's "logon hours" to nothing, or expiring the password (or the whole account)?
– grawity
Nov 30 at 6:31
Your Exchange command denies Receive-As, not FullAccess. You could disconnect the Mailbox (it will be kept for a time depending on your configuration).
– Seth
Nov 30 at 8:39
Thanks but neither suit. Logon hours needs to be 'always' so they can get to payroll. Disconnect won't work as the mailbox needs to be active for others to read incoming and respond. I don't believe that Add-ADPermission has an AccessRight of FullAccess but Receive-As shows as FullAccess when a Get-MailboxPermission is run.
– Lexdon
Dec 3 at 3:51