Shared mailbox - users cannot create or view subfolders Announcing the arrival of Valued Associate #679: Cesar Manara Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern) Come Celebrate our 10 Year Anniversary!Can't access public folders in Outlook after upgrade to Exchange 2010 SP1Outlook 2003 won't connect to Exchange 2010Powershell: undelete messages removed by recipient policyWhere do Outlook folders go when moved?Allowing manager access to user's email stealthilyBlock Specific Versions of Outlook from ExchangeExchange Full Access issueOutlook Exchange 2010- OWA/Outlook Client issueIssues importing PST into Archive Mailbox Exchange 2013What could prevent autocompletion from working on Exchange 2010/Outlook 2010?
String `!23` is replaced with `docker` in command line
English words in a non-english sci-fi novel
List of Python versions
How does debian/ubuntu knows a package has a updated version
How to call a function with default parameter through a pointer to function that is the return of another function?
Withdrew £2800, but only £2000 shows as withdrawn on online banking; what are my obligations?
Overriding an object in memory with placement new
Short Story with Cinderella as a Voo-doo Witch
Generate an RGB colour grid
How to react to hostile behavior from a senior developer?
How discoverable are IPv6 addresses and AAAA names by potential attackers?
prime numbers and expressing non-prime numbers
Book where humans were engineered with genes from animal species to survive hostile planets
Why is my conclusion inconsistent with the van't Hoff equation?
ListPlot join points by nearest neighbor rather than order
Do I really need recursive chmod to restrict access to a folder?
Why did the IBM 650 use bi-quinary?
Using et al. for a last / senior author rather than for a first author
The logistics of corpse disposal
Output the ŋarâþ crîþ alphabet song without using (m)any letters
How to find out what spells would be useless to a blind NPC spellcaster?
List *all* the tuples!
What to do with chalk when deepwater soloing?
How come Sam didn't become Lord of Horn Hill?
Shared mailbox - users cannot create or view subfolders
Announcing the arrival of Valued Associate #679: Cesar Manara
Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern)
Come Celebrate our 10 Year Anniversary!Can't access public folders in Outlook after upgrade to Exchange 2010 SP1Outlook 2003 won't connect to Exchange 2010Powershell: undelete messages removed by recipient policyWhere do Outlook folders go when moved?Allowing manager access to user's email stealthilyBlock Specific Versions of Outlook from ExchangeExchange Full Access issueOutlook Exchange 2010- OWA/Outlook Client issueIssues importing PST into Archive Mailbox Exchange 2013What could prevent autocompletion from working on Exchange 2010/Outlook 2010?
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;
I've setup a shared mailbox on our Exchange 2010/SBS2011 server. I've added some users as Full permission-users on this mailbox, and when they open Outlook/login to OWA the mailbox is automatically opened. Great stuff.
However, only the Inbox folder is visible, and the alternative to create a folder is grayed out. If they open the mailbox explicitly (for instance in OWA by clicking open other user's mailbox) they can see other folders, as well as create new ones. What configuration is needed to be able to view and create subfolders directly?
exchange-2010 mailbox
add a comment |
I've setup a shared mailbox on our Exchange 2010/SBS2011 server. I've added some users as Full permission-users on this mailbox, and when they open Outlook/login to OWA the mailbox is automatically opened. Great stuff.
However, only the Inbox folder is visible, and the alternative to create a folder is grayed out. If they open the mailbox explicitly (for instance in OWA by clicking open other user's mailbox) they can see other folders, as well as create new ones. What configuration is needed to be able to view and create subfolders directly?
exchange-2010 mailbox
add a comment |
I've setup a shared mailbox on our Exchange 2010/SBS2011 server. I've added some users as Full permission-users on this mailbox, and when they open Outlook/login to OWA the mailbox is automatically opened. Great stuff.
However, only the Inbox folder is visible, and the alternative to create a folder is grayed out. If they open the mailbox explicitly (for instance in OWA by clicking open other user's mailbox) they can see other folders, as well as create new ones. What configuration is needed to be able to view and create subfolders directly?
exchange-2010 mailbox
I've setup a shared mailbox on our Exchange 2010/SBS2011 server. I've added some users as Full permission-users on this mailbox, and when they open Outlook/login to OWA the mailbox is automatically opened. Great stuff.
However, only the Inbox folder is visible, and the alternative to create a folder is grayed out. If they open the mailbox explicitly (for instance in OWA by clicking open other user's mailbox) they can see other folders, as well as create new ones. What configuration is needed to be able to view and create subfolders directly?
exchange-2010 mailbox
exchange-2010 mailbox
asked Nov 22 '12 at 21:58
carlpettcarlpett
52661227
52661227
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
You can give permissions on Inbox folder directly. It doesn't matter - shared mailbox it is or user mailbox.
Add Full permission for this folder to yourself.
Open the Inbox Folder properties - Permissions Tab.Choose the user and Check the checkbox Create Subfolder.
If you want to make the Subfolder visible - Open the Permission Tab of subfolder and check the Folder visible parameter.
Or you can use Set-MailboxFolderPermission cmdlet in powershell.
add a comment |
You can set the inheritance type of the permissions as described in this document:
The InheritanceType parameter specifies whether permissions are inherited by folders within the mailbox.
The options for this parameter can be seen here. This appears to be the default, at least in our environment. To check if this is relevant to your scenario, you can do
Get-MailboxPermission <MailboxIdentity> | ft User,InheritanceType
to see what the InheritanceType
flag is set to for your permissions entries on that shared mailbox. If they're not set to All
then you may need to remove and re-add the permissions using
Add-MailboxPermission -Identity "Ellen Adams" -User KevinKelly -AccessRights FullAccess -InheritanceType All
as an example.
The other thing we have had problems with is adding users to shared mailboxes directly. If you create a mail-enabled security group for that mailbox, grant it FullAccess to the mailbox and then add users to the security group, you may get better results.
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "2"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
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%2fserverfault.com%2fquestions%2f451368%2fshared-mailbox-users-cannot-create-or-view-subfolders%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
You can give permissions on Inbox folder directly. It doesn't matter - shared mailbox it is or user mailbox.
Add Full permission for this folder to yourself.
Open the Inbox Folder properties - Permissions Tab.Choose the user and Check the checkbox Create Subfolder.
If you want to make the Subfolder visible - Open the Permission Tab of subfolder and check the Folder visible parameter.
Or you can use Set-MailboxFolderPermission cmdlet in powershell.
add a comment |
You can give permissions on Inbox folder directly. It doesn't matter - shared mailbox it is or user mailbox.
Add Full permission for this folder to yourself.
Open the Inbox Folder properties - Permissions Tab.Choose the user and Check the checkbox Create Subfolder.
If you want to make the Subfolder visible - Open the Permission Tab of subfolder and check the Folder visible parameter.
Or you can use Set-MailboxFolderPermission cmdlet in powershell.
add a comment |
You can give permissions on Inbox folder directly. It doesn't matter - shared mailbox it is or user mailbox.
Add Full permission for this folder to yourself.
Open the Inbox Folder properties - Permissions Tab.Choose the user and Check the checkbox Create Subfolder.
If you want to make the Subfolder visible - Open the Permission Tab of subfolder and check the Folder visible parameter.
Or you can use Set-MailboxFolderPermission cmdlet in powershell.
You can give permissions on Inbox folder directly. It doesn't matter - shared mailbox it is or user mailbox.
Add Full permission for this folder to yourself.
Open the Inbox Folder properties - Permissions Tab.Choose the user and Check the checkbox Create Subfolder.
If you want to make the Subfolder visible - Open the Permission Tab of subfolder and check the Folder visible parameter.
Or you can use Set-MailboxFolderPermission cmdlet in powershell.
answered Dec 16 '12 at 11:56
sl-iwisl-iwi
112
112
add a comment |
add a comment |
You can set the inheritance type of the permissions as described in this document:
The InheritanceType parameter specifies whether permissions are inherited by folders within the mailbox.
The options for this parameter can be seen here. This appears to be the default, at least in our environment. To check if this is relevant to your scenario, you can do
Get-MailboxPermission <MailboxIdentity> | ft User,InheritanceType
to see what the InheritanceType
flag is set to for your permissions entries on that shared mailbox. If they're not set to All
then you may need to remove and re-add the permissions using
Add-MailboxPermission -Identity "Ellen Adams" -User KevinKelly -AccessRights FullAccess -InheritanceType All
as an example.
The other thing we have had problems with is adding users to shared mailboxes directly. If you create a mail-enabled security group for that mailbox, grant it FullAccess to the mailbox and then add users to the security group, you may get better results.
add a comment |
You can set the inheritance type of the permissions as described in this document:
The InheritanceType parameter specifies whether permissions are inherited by folders within the mailbox.
The options for this parameter can be seen here. This appears to be the default, at least in our environment. To check if this is relevant to your scenario, you can do
Get-MailboxPermission <MailboxIdentity> | ft User,InheritanceType
to see what the InheritanceType
flag is set to for your permissions entries on that shared mailbox. If they're not set to All
then you may need to remove and re-add the permissions using
Add-MailboxPermission -Identity "Ellen Adams" -User KevinKelly -AccessRights FullAccess -InheritanceType All
as an example.
The other thing we have had problems with is adding users to shared mailboxes directly. If you create a mail-enabled security group for that mailbox, grant it FullAccess to the mailbox and then add users to the security group, you may get better results.
add a comment |
You can set the inheritance type of the permissions as described in this document:
The InheritanceType parameter specifies whether permissions are inherited by folders within the mailbox.
The options for this parameter can be seen here. This appears to be the default, at least in our environment. To check if this is relevant to your scenario, you can do
Get-MailboxPermission <MailboxIdentity> | ft User,InheritanceType
to see what the InheritanceType
flag is set to for your permissions entries on that shared mailbox. If they're not set to All
then you may need to remove and re-add the permissions using
Add-MailboxPermission -Identity "Ellen Adams" -User KevinKelly -AccessRights FullAccess -InheritanceType All
as an example.
The other thing we have had problems with is adding users to shared mailboxes directly. If you create a mail-enabled security group for that mailbox, grant it FullAccess to the mailbox and then add users to the security group, you may get better results.
You can set the inheritance type of the permissions as described in this document:
The InheritanceType parameter specifies whether permissions are inherited by folders within the mailbox.
The options for this parameter can be seen here. This appears to be the default, at least in our environment. To check if this is relevant to your scenario, you can do
Get-MailboxPermission <MailboxIdentity> | ft User,InheritanceType
to see what the InheritanceType
flag is set to for your permissions entries on that shared mailbox. If they're not set to All
then you may need to remove and re-add the permissions using
Add-MailboxPermission -Identity "Ellen Adams" -User KevinKelly -AccessRights FullAccess -InheritanceType All
as an example.
The other thing we have had problems with is adding users to shared mailboxes directly. If you create a mail-enabled security group for that mailbox, grant it FullAccess to the mailbox and then add users to the security group, you may get better results.
answered Jul 29 '13 at 15:22
johnjohn
1,6851429
1,6851429
add a comment |
add a comment |
Thanks for contributing an answer to Server Fault!
- 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%2fserverfault.com%2fquestions%2f451368%2fshared-mailbox-users-cannot-create-or-view-subfolders%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