Public Folders Permissions

Hi,
is there a way to set Public Folder permissions in ECP not for user but for group(distribution or security)? COnsole only shows me users, doesnt matter if its mail enabled or not. Thank you.
Pete
sfs

Hi,
If we create an universal security group in AD, and at the same time, another universal sercurity group is created via EAC. We will find that the group created in AD doesn't show in EAC, this group doesn't have an email address when we check it from AD.
After we use the Enable-DistributionGroup cmdlet to enable this group, this security group will display in EAC and we can also grant public folder permissions to this group.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Similar Messages

Public Folders Permissions Tab Missing on one pc but not another

this has to be pc related but i just can't find any info anywhere. when i log into a pc and startup outlook and go to public folders, i cannot see the permissions tab on the folders at all. but if i go to another pc, same OS and office version, i CAN see
and edit the permissions on public folders! has anyone else run across this problem?
Exchange Server 2007
Desktops Win7
Outlook 2013

Hi,
Since the issue only happens to specific client, the issue should be related to client side. I suggest we can do the following method to narrow down the issue:
1. Start Outlook in safe mode(Start > Run >type “Outlook /safe”> Enter) to check whether the issue persists.
2. Perform a clean boot for Windows to have a try.
If the issue doesn’t happen in safe mode, the issue may be caused by any third-party add-ins. We can disable third-party add-ins one by one to find out the root cause.
If the issue persists in Outlook safe mode but not occurs after performing a clean boot, please disable the related third-party program in Windows to resolve the issue. For more information about clean boot, please refer to:
http://support.microsoft.com/kb/929135/en-us
Regards,
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Winnie Liang
TechNet Community Support

Exchange 2010 Public Folders Cannot Change Permissions Errors from Management Console and Powershell

This problem does not affect new public folders, only old ones that have probably been on Exchange 2000/2003 servers in the past. Migrations I believe did go smoothly but now have errors.
Error Reported is:
Microsoft Exchange Error
The following error(s) occurred while saving changes:
Add-PublicFolderClientPermission
Failed
Error:
Failed to modify the MAPI.NET table property of the object "000000001A447390AA6611CD9BC800AA002FC45A030064004E9CC2F8DD46B5E1E4578DE6D8030000000278E90000" on server "FQDN.Server.Name". See inner exception for more information.
MapiExceptionNonCanonicalACL: Unable to modify table. (hr=0x80004005, ec=2409)
Diagnostic context:
    Lid: 40487   EMSMDBMT.EcDoRpcExt2 called [length=218]
    Lid: 56871   EMSMDBMT.EcDoRpcExt2 returned [ec=0x0][length=356][latency=0]
    Lid: 23226   --- ROP Parse Start ---
    Lid: 27962   ROP: ropModifyACL [64]
    Lid: 17082   ROP Error: 0x969
    Lid: 27745
    Lid: 21921   StoreEc: 0x969
    Lid: 27962   ROP: ropExtendedError [250]
    Lid: 1494    ---- Remote Context Beg ----
    Lid: 26426   ROP: ropModifyACL [64]
    Lid: 22086
    Lid: 27128
    Lid: 27232   StoreEc: 0x8004010F
    Lid: 27128
    Lid: 27232   StoreEc: 0x8004010F
    Lid: 22086
    Lid: 21970   StoreEc: 0x8004010F PropTag: 0x3D210102
    Lid: 19149   Error: 0x0
    Lid: 24509   Error: 0x0
    Lid: 31229   Error: 0x0
    Lid: 21970   StoreEc: 0x8004010F PropTag: 0x668F0040
    Lid: 6671    StoreEc: 0x8004010F
    Lid: 24976
    Lid: 24952
    Lid: 25472
    Lid: 7972    StoreEc: 0x969
    Lid: 26532
    Lid: 4920    StoreEc: 0x969
    Lid: 5119    StoreEc: 0x969
    Lid: 5247    StoreEc: 0x969
    Lid: 17916   StoreEc: 0x969
    Lid: 4814    StoreEc: 0x969
    Lid: 1750    ---- Remote Context End ----
    Lid: 26849
    Lid: 21817   ROP Failure: 0x969
    Lid: 29150
    Lid: 20446   StoreEc: 0x969
OK
From ExFolders we get error "Exception: Object Reference not set to an instance of an object"
Any thought on how to fix permissions, people who already had permission in the past can see and access them OK and all objects, but we cannot change/update or remove permissons
We alos receive similar error from the powershell.

Hi,
Could
you please add a new public folder hierarchies with ADSIEdit as following setups.
For how to use ADSIEdit ,you can access:
http://technet.microsoft.com/en-us/library/cc773354(WS.10).aspx
1.Run ADSIEdit, right click Exchange Administrative Group under “Configuration \ services \ Microsoft
Exchange \ Organization name \ Administrative groups”.
2.Select New Object.
3.Select msExchPublicFolderTreeContainer for the class and click Next.
4.Enter the following for the value:
Folder Hierarchies, click Next.
5.Click Finish.
6.Create
Public Folder Tree Object.
7.Right click CN=Folder Hierarchies -> New Object.
8.Selected msExchPFTree for the class.
9.For the value we entered, "Public Folders" and clicked next.
10.Clicked on the "More Attributes" button, selected msExchPFTreeType .
11.Set the value
to 1.
Note: This is very important that this value is set
to a value of 1 as This tells Exchange that this is a MAPI Tree.
12.Click Ok and then finish.
13.We then went
to the properties of the newly created "Public Folders" Tree object in
ADSIEdit.
14.Copy the distinguished name value
to the clipboard and then click cancel.
15.Navigate
to the Storage group that contains the Public
Folder Store for this server and get properties of the server.
16.Locate the msExchOwningPFTree attribute and paste in the value that was copied
from the Public folders Distinguish name attribute.
17.Restart the Information Store Service.
18.Mounted and dismount the PF store.
19.Open Outlook with administrator,give full permission to default owner.
Hope it can help you!

Permissions problem: Public folders/Shared Calendars across domains with Linked accounts

I have a linked mailbox that is accessed by an account in a trusted domain. The account can access e-mail, send e-mail, free-busy search, etc, just fine. However, there seems to be a permissions issue with the public folders and shared calendars.
When trying to access the public folders for which permissions have been assigned to the linked account from the trusted domain account, I get an error, or just can't see the folders. The only way I can view public folders is by setting default permissions
on the folder to 'Read'.
I've found some other threads that reference this problem, and a blog that no longer exists as the solution:
http://social.technet.microsoft.com/Forums/en-US/exchangesvrclientslegacy/thread/5fdf4cd7-3543-4b5d-94cc-317446ddaa46
If anyone has any ideas or the solution that was shown in the above referenced blog, I'd be very grateful!
-shane

Hi,Shane,
I believe you can try James' suggestion in the link
http://social.technet.microsoft.com/Forums/en-US/exchangesvrclientslegacy/thread/6c88569d-e693-46f4-a8fa-e1f9e5b6234e/ to get it solved.
Per the
Detecting and Correcting msExchMasterAccountSid Issues it says,
Active Directory does not enforce simultaneous performance of all these tasks, nor does it enforce removal of the Associated External Account or
msExchMasterAccountSid if an Active Directory account is re-enabled.
Regards,
Sharon
Sharon Shen
TechNet Community Support
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question.

Exchange 2013 Public Folders implicit permissions

Hi,
I have fresh Exchange 2013 without SP1. I am testing PF but I discovered strange thing. I create PF with permissions only for two users but the third user can access them and edit without problems, I also trid to modify root folder permissions but
no change. Are there any implicit permissions that allow all users to access anything so they have to denied access explicitly or can I change these implicit permissions? Or am I doing something wrong? Thank you.
Pete
sfs

Hi,
For this issue, I recommend you use the following command to check the public folder permission for Default user on this PF.
Get-PublicFolderClientPermission -Identity "\Marketing" | fl
Just replace the "\Marketing" with your PF.
Make sure the public folder permissions for the Default user is set to lowest permissions or None. Default means the default permission. It is what permissions the users have if they don't have any other permissions listed. If it's set to Author or others,
please change it back to None to check the result.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Cannot expand public folders in Outlook but can in OWA

Hi All,
I have a problem which I hope some one might be able to shed some light on. Firstly, the environment is Exchange 2010 (v 14.01.0438.000) and all clients use Outlook 2007. We have one user in the organisation who recently noticed that he cannot expand public
folders. He had been able to do so a couple of months back but could not pin point the time it stopped working. The error received reads :-
"Cannot expand the folder. The set of folders cannot be opened. The attempt to log on to Microsoft Exchange has failed."
I thought that this might be a permissions issue but this particular user can access the public folders via OWA. Also, my AD account was a copy of this user's and I can access public folders without issue.
I have tried the following so far :-
Tried running Outlook in safe mode
Tried recreating the Outlook profile.
Tried creating a new Outlook profile on a different client PC.
Tried running Outlook in cached an online modes.
Ran Exchange BPA and found no issues.
Checked ADSIedit for old administrative groups left over from past migrations.
used the test-outlook connectivity cmdlet from powershell which ran it's tests successfully.
This user originally set up all the public folders and was still listed as the owner of all of them.
Tried creating a new public folder.
Checked for an Outlook update that had caused a similar issue.
All the above failed to progress the situation. I have come across posts online that sound very similar, one stated that a Microsoft tech had found a permission that wasn't correct but didn't list which permission and the other related to an update to Outlook
that had triggered it. I can confirm it's not the update and I have checked permissions in the public folder management utility in Exchange. Also, my AD account is a copy of his and I can access the folders without issue.
I have also considered what may have changed on the network recently. The only major change has been a new admin password but I cannot see how that would be relevant.
Any help would be hugely appreciated!
Thanks in advance!

Hello John: We are having the exact same issue. Thank you for the great description, it hits the nail on the head for an issue that is tough to explain. Did rebuilding the mailbox fix the problem? We thought a next step would be to create a new
AD profile for the user all together, although replacing the user herself would be easier for us. She obviously caused this problem and will most likely cause us more problems that might be worse if she keeps clicking and sliding on every thing that
is shiny to see what it does..
I can only surmise that CaRa ChEn has decided to "better understand customer views on social support experience" elsewhere. I think the only logic for the mailbox suggestion would be "grasping for straws" and it is the only thing you have not tried
so far. (Other than replacing the user). Pactera employees get points for being the first to reply to a question and the first to have a suggestion marked as helpful as well as the sheer quantity of replies to the forums that are made. High
value is placed on moving posts to different forums as well so I thought I would ask quick before the thread gets shoveled somewhere else.. If she needs help with the interview project she can find plenty of my thoughts here in the community.
Thanks again, and we will reply back if replacing the user (account) does NOT solve the problem, otherwise one can assume we are happy campers again our new employee and remember just because it is blinking does not mean you should click on it. :)
Best regards,
RickkEE

Exchange 2013 SP1 RU4 Public Folder Permissions

Hi All,
Exchange 2013 SP1 RU4 Public Folder Permissions
We have a weird problem after migrating our PF from Exchange 2010 to 2013.
Users do not have permission to create or delete in PF even thou they have owner permissions.
Example:-
I have created a '\test1' folder in the root which has the following permissions (this works OK):-
Myself - Owner
Default - Author
Anonymous - None
I have created another folder '\admin\test2' folder which has the same permissions as above but i get the "cannot create the folder. you don't have appropriate permissions to perform this operation"
I get this problem across all of the folders that were migrated. clean folders created at the root with the correct permission function as per expected.
Regards
Paul Sheldon

Hi,
I recommend you use the Get-PublicFolderClientPermission -Identity publicfolder command to check the client access permissions to a public folder.
If possible, please remove permission and re-add permission to check the result.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Exchange 2007 to 2013 Migration issues. Prompt for credentials, Public Folders inaccessible, Apps not working

Exchange 2013 Migration issues
I have three issues and decided to list them here. Please pick and choose to assist. Thanks in advance.
Environment:
Mixed 2007 SP3 R12 and 2013 CU3. 2007 Environment was webmail.domain.com. I installed new Exchange 2013 (1 CAS, 1 Mailbox) according to:
http://technet.microsoft.com/en-us/library/ff805032(v=exchg.150).aspx. Exchange 2007 is now legacy.domain.com and Exchange 2013 CAS is webmail.domain.com.
Machine 1: Windows 8.1, not domain joined, using Outlook Anywhere external. Outlook 2013
Machine 2: Windows 7, domain joined, using Outlook Anywhere internal. Outlook 2010 SP2
I have migrated 1 user so far to Exchange 2013. This user was a Domain Admin. I have removed that membership. I checked the box to inherit permissions of the security of the object and reset the AdminCount attribute in ADSIedit to 0 and verified this replicated
to all domain controllers. ( I originally thought this to be the issue with it prompting for the password. )
Here is a Get-OutlookAnywhere cmdlet...
ServerName                         : EXCHANGE2007SVR
SSLOffloading                      : False
ExternalHostname                   : legacy.domain.com
InternalHostname                   :
ExternalClientAuthenticationMethod : Basic
InternalClientAuthenticationMethod : Basic
IISAuthenticationMethods           : {Basic}
XropUrl                            :
ExternalClientsRequireSsl          : True
InternalClientsRequireSsl          : False
MetabasePath                       : IIS://EXCHANGE2007SVR.domain.local/W3SVC/1/ROOT/Rpc
Path                               : C:\WINDOWS\System32\RpcProxy
ExtendedProtectionTokenChecking    : None
ExtendedProtectionFlags            : {}
ExtendedProtectionSPNList          : {}
AdminDisplayVersion                : Version 8.3 (Build 83.6)
Server                             :
EXCHANGE2007SVR
AdminDisplayName                   :
ExchangeVersion                    : 0.1 (8.0.535.0)
Name                               : Rpc (Default Web Site)
DistinguishedName                  : CN=Rpc (Default Web Site),CN=HTTP,CN=Protocols,CN=EXCHANGE2007SVR,CN=Servers,CN=Exchange
                                     Administrative Group (FYDIBOHF23SPDLT),CN=Administrative
                                     Groups,CN=DOMAIN,CN=Microsoft
                                     Exchange,CN=Services,CN=Configuration,DC=DOMAIN,DC=local
Identity                           : EXCHANGE2007SVR\Rpc (Default Web Site)
Guid                               : 4901bb14-ab81-4ded-8bab-d5ee57785416
ObjectCategory                     : domain.local/Configuration/Schema/ms-Exch-Rpc-Http-Virtual-Directory
ObjectClass                        : {top, msExchVirtualDirectory, msExchRpcHttpVirtualDirectory}
WhenChanged                        : 12/31/2013 4:08:04 PM
WhenCreated                        : 7/18/2008 10:56:46 AM
WhenChangedUTC                     : 12/31/2013 9:08:04 PM
WhenCreatedUTC                     : 7/18/2008 2:56:46 PM
OrganizationId                     :
OriginatingServer                  : DC1.domain.local
IsValid                            : True
ObjectState                        : Changed
ServerName                         :
EXCHANGE2013SVR
SSLOffloading                      : True
ExternalHostname                   : webmail.domain.com
InternalHostname                   : webmail.domain.com
ExternalClientAuthenticationMethod : Basic
InternalClientAuthenticationMethod : Ntlm
IISAuthenticationMethods           : {Basic, Ntlm}
XropUrl                            :
ExternalClientsRequireSsl          : True
InternalClientsRequireSsl          : True
MetabasePath                       : IIS://EXCHANGE2013SVR.domain.local/W3SVC/1/ROOT/Rpc
Path                               : C:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy\rpc
ExtendedProtectionTokenChecking    : None
ExtendedProtectionFlags            : {}
ExtendedProtectionSPNList          : {}
AdminDisplayVersion                : Version 15.0 (Build 775.38)
Server                             : EXCHANGE2013SVR
AdminDisplayName                   :
ExchangeVersion                    : 0.20 (15.0.0.0)
Name                               : Rpc (Default Web Site)
DistinguishedName                  : CN=Rpc (Default Web Site),CN=HTTP,CN=Protocols,CN=EXCHANGE2013SVR,CN=Servers,CN=Exchange
                                     Administrative Group (FYDIBOHF23SPDLT),CN=Administrative
                                     Groups,CN=DOMAIN,CN=Microsoft
                                     Exchange,CN=Services,CN=Configuration,DC=DOMAIN,DC=local
Identity                           : EXCHANGE2013SVR\Rpc (Default Web Site)
Guid                               : d983a4b1-6921-4a7f-af37-51de4a61b003
ObjectCategory                     : domain.local/Configuration/Schema/ms-Exch-Rpc-Http-Virtual-Directory
ObjectClass                        : {top, msExchVirtualDirectory, msExchRpcHttpVirtualDirectory}
WhenChanged                        : 1/7/2014 11:29:05 AM
WhenCreated                        : 12/31/2013 1:17:42 PM
WhenChangedUTC                     : 1/7/2014 4:29:05 PM
WhenCreatedUTC                     : 12/31/2013 6:17:42 PM
OrganizationId                     :
OriginatingServer                  : DC1.domain.local
IsValid                            : True
ObjectState                        : Changed
ISSUE 1
Issue: On Machine 1 (reference above) Windows Security prompt that says "Connecting to
[email protected]". Almost always prompts when Outlook is first opened. Afterwards (if it goes away) seemingly random on when it asks for it. I put in the credentials (absolutely correct) and it fails and prompts again.
I always check the box for it to save the password. To get rid of it, I click the Cancel button at which Outlook reports "NEED PASSWORD", but still acts fine sending and receiving emails. Eventually the "NEED PASSWORD" sometimes changes
to say "CONNECTED", but it works regardless.
No issues on Machine 2 so I don't know where the problem might be as there are a lot of variables in play here.
ISSUE 2
Migrated user is unable to open Public folders from Exchange 2007.
Cannot expan the folder. Microsoft Exchange is not available. Either there are network problems or the Exchange server is down for maintenance. (/o=...).
This error occurs on Machine 1, Machine 2 and from OWA, same error each time.
ISSUE 3
Apps. Installed by default are 4 apps (Bing Maps, Suggested Meetings, Unsubscribe, Action Items). I have made sure the apps are enabled in OWA and they show up in mail items on both Machine 1 (Outlook 2013) and OWA. They do not show up in Machine 2 (Outlook
2010). I'm assuming that isn't supported.
In OWA, when I go to the installed apps listing it shows all of the apps but has a broken link on the image describing the app.
When I click the app in either Outlook 2013 or in OWA, I get "APP ERROR, Sorry we can't load the app. Please make sure you have network and/or internet connectivity. Click "Retry" once you're back online.
Current workaround is just disabling them through OWA.

Hello,
In order to avoid confusion, we troubleshoot a issue per thread usually.
For your first isue, I agree with Ed's suggestion to check if your certificate name is correct.
Besides, I recommend you change ExternalClientAuthenticationMethod from Basic authentication to Negotiate authentication to check the result.
For the second issue and third issue, please create a new post.
If you have any feedback on our support, please click here
Cara Chen
TechNet Community Support

Users could not open Public Folders in Outlook 2007 SP3.

Is anybody had this issue or probably know how to fix it?
We have Exchange 2013 server and users workstations with XP SP3 and Office 2007 SP3 installed. Exchange has users’ mailboxes and public folders. Public folders work OK until last week. Issue probably happened after latest CU update for Exchange 2013 installation.
Now users could not open Public Folders in their Outlook. The error is:
"Cannot expand the folder. Your profile is not configured. (/o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=[email protected])"
And this "[email protected]" is public folder ContentMailboxGuid.
And this error message appears when user click on Public Folders \All Public Folders in Outlook. So company public folders do not even appear in All Public Folders folder. Users have Owner permissions for all Public Folders and Root Public folders.
Also one more error in Outlook about it:
“Cannot display the folder. Microsoft Office Outlook cannot access the specified folder location.”
One more issue is that previous Exchange 2007 server died (RAID died) so we had to delete it from AD and clean its records in ADSIEdit (CN=configuration,DC=.domainname,DC=.COM > CN=Services > CN=Microsoft Exchange > CN=Organization > CN= Administrative
Groups > CN=(Groupname) > CN=Servers >) and install new server with Exchange 2013, and import all users mailboxes from backup. Public folders were not migrated from the old server because of its death. We create new public folders in Exchange and
then manually import all folders from latest .pst backup using user Outlook.
And it work OK more than a month till last week.
Thanks,
Andrey

Hi Mavis,
Thank you for your answer.
I check permissions couple of times for both public folder and its root and both are granted for users as “Owner” and applied to public folder and its subfolders.
This server has 2 mailbox stores and both are currently mounted.
[PS] C:\Windows\system32>Get-MailboxDatabase -Status |fl name,mounted
Name    : Mailbox Database 2104233799
Mounted : True
Name    : MBDB1
Mounted : True
But when I check homeMDB property for Microsoft System Attendant in ADSIEdit I found that it is empty.
And it looks like System Attendant mailbox & service have been removed from Exchange 2013.
http://howexchangeworks.com/2013/05/cannot-open-microsoft-system-attendant-mailbox-error-during-exchange-2013-mailbox-move.html
and even from Exchange 2010.
http://blogs.msdn.com/b/dvespa/archive/2009/10/06/say-so-long-to-the-system-attendant-mailbox.aspx
Also I check arbitration mailboxes and all are looks to be in default database “Mailbox Database 2104233799” which is currently mounted.
[PS] C:\Windows\system32>Get-Mailbox -Arbitration |fl name,data*
Name     : FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042
Database : Mailbox Database 2104233799
Name     : SystemMailbox{1f05a927-77cc-4f5d-b5ca-667ea4256ff9}
Database : Mailbox Database 2104233799
Name     : SystemMailbox{bb558c35-97f1-4cb9-8ff7-d53741dc928c}
Database : Mailbox Database 2104233799
Name     : SystemMailbox{e0dc1c29-89c3-4034-b678-e6c29d823ed9}
Database : Mailbox Database 2104233799
Name     : Migration.8f3e7716-2011-43e4-96b1-aba62d229136
Database : Mailbox Database 2104233799
Thanks,
Andrey

Exchange 2010 - visibility of items in Public Folders

Hello all,
I already posted this question to the German Exchange 2010 forum, but have not gotten an answer yet. So I hope to be more lucky in the English forum.
Environment: Exchange 2010 SP3 RU4, 2 replicas for Public Folders, Outlook 2007 cache Mode
Problem:
Some of our users have a phenomenon when working with mail enabled Public Folders:
User has the focus set to Public Folder A, an email is sent there (and correctly delivered) but remains invisible to the user. When he changes the focus to point to his inbox or to Public Folder B and directly changes back to folder A he can see the email.
Other users can see the email directly on delivery without leaving the folder first.
When an affected user adds Public Folder A to his Public Folder Favorites he can see that an email is delivered from the change in numbers of unread mails (number in brackets behind folder name).
I already checked the Exchange server to see if there is a replication related problem (though the default Public Folder DB is the same for all mailbox databases). Even after a successful replication an effected user does not see the email unless he leaves
the folder and re-opens it.
As the problem does not affect all users having permissions to this folder I picked one affected user and tried to remedy the issue as follows:
- deleted the existing Outlook profile and re-created it => without success
- deleted the user profile and re-created it => without success
We use Outlook Cache Mode (set by policy, so the user cannot deactivate it) but there is no Public Folder data downloaded.
When I create a new mail enabled Public Folder to test the scenario with an affected user everything works without problems, he can see an email on delivery.
As far as I know this problem occurs with only two folders (and for both folders only a few users are affected - different users for each folder) I do not know what else to do. Can someone please give me a hint where to look at? Thanks in advance.
Kind regards,
Klaus

The user is caching the public folder. When he changes the focus and goes back, it tells Outlook to update. In my experience, I've seen that Outlook only gets the update notices for the primary mailbox, so cached shared mailboxes are generally
rarely updated. We have stopped caching shared mailboxes for this reason and others. Think of the following scenario:
Ten different users perform actions on items in a shared mailbox
When they first get the message, they move it to a subfolder in the mailbox (so it won't be there for other users)
Since users are working in Cached mode, they will see an out-of-date image of the mailbox - they will move the item in their copy of the mailbox, but that won't be reflected in the other mailboxes until their copy updates to the server, then the server updates
the other copies. Talk about being lagged ...

Cannot Open Some Public Folders on MacBook

I have several users using my macbook. Each user has their own user account. For user accounts created before "Personal File Sharing" was switched on, other users (except for root) cannot open the "Public" or "Drop" folders. Public and Drop folders for user accounts created after "Personal File Sharing" was switched on may be opened by all users. Both the pre- and post- "Personal File Sharing"-switched-on folders have the correct permissions settings.
The only work-around I can think of to ensure every user has Public and Drop folders that every other user can open is to delete the pre-"Personal File Sharing"-switched-on user-accounts and create new ones.
Any other suggestions? Is there some other setting I need to change?
Help much appreciated.
MacBook Mac OS X (10.4.9)

When you say "cannot open the "Public" or "Drop" folders, do you mean that the folders are available in the list of shares but cannot be opened, or that the folders aren't available at all? I'm not sure if this is related to your problem, or what accounts for the different behaviours, but it seems in "Tiger", new accounts are often created with an empty 'sharedDir' property. This property in the user record specifies which of the user's folders is to be shared for non-user access in AFP, and usually has a value of "Public". The "Public" folders of users without this property set will not appear in the list of available "shares" that appears after connecting to an AFP server.
To see what the current value of 'sharedDir' is on a given account, try opening "/Applications" > "Utilities" > "Terminal.app" and entering the command below, substituting 'username' with the user's "short name":<pre>nicl . -read /users/username sharedDir</pre>
The expected output is 'sharedDir: Public', but if it is just 'sharedDir:' or 'No such key: sharedDir', then that would explain why those users' "Public" folders aren't available for personal file sharing. To set the value to "Public", make sure you are logged in to an "admin" account and try this command:<pre>sudo /usr/bin/nicl . -create /users/username sharedDir Public</pre>
Substitute a user's name as above, and enter your "admin" password when prompted (your password will not be visible as you enter it - just press the <Return> key after you are done).

Unable to access public folders on Exchange 2007 when user mailbox is on Exchange 2013

Hi
I have coexistence with Exchange 2007 and Exchange 2013. I've moved a mailbox to Exchange 2013 and now cannot view the public folders on Exchange 2007. The error message I get is "could not connect to the public folder server. microsoft exchange is
not available. either there are network problems or the exchange server is down for maintenance."
Mailboxes on Exchange 2007 do not have any problems viewing public folders. I can't migrate users to Exchange 2013 until this issue is resolved.
The IIS permissions to the Public virtual directory on Exchange 2007 is set to Intergrated Windows and Basic authentication.

Hi northerly,
I recommend you follow the steps below for troubleshooting:
1. Please run the Get-OutlookAnywhere cmdlet to verify the Outlook Anywhere settings on Exchange Server 2013 Client Access servers.
2. If "ExternalHostName" is set, and "ExternalClientAuthenticationMethod" is Negotiate, change "ExternalClientAuthenticationMethod" to something other than Negotiate.
3. If "InternaClientlAuthenticationMethod" is set to Negotiate, and "InternalRequireSSL" is True, change "InternalClientAuthenticationMethod" to something other than Negotiate, or change "InternalRequireSSL" to False.
What's more, here is a helpful KB for your reference.
Users of Exchange Server 2013 or Exchange Online can't open public folders or shared mailboxes on an Exchange 2010 or Exchange 2007 server
http://support.microsoft.com/kb/2834139/en-us
Hope my clarification is helpful.
If there are any problems, please feel free to let me know.
Best regards,
Amy
Amy Wang
TechNet Community Support

User Access to Public Folders Disappearing (Outlook 2013)

I have one particular user who is losing access to public folders in Outlook 2013. I have found that going to
File > Account Settings > Account Settings > Email [TAB] > Repair... and then following through that dialog temporarily restores public folder access after restarting Outlook. However, once Outlook is restarted
for 30-60 seconds, the public folders disappear again. This is only happening for this one user. They receive their public folder permissions via group membership. Other group members report no such issue. I had another user with identical permissions
log into the same workstation and they again had no issue.
What could be causing this? This is a particularly bothersome problem since this user happens to be the office scheduler and the calendar they schedule on is public (which, thanks to reduced functionality in Exchange 2013, is no longer accessible in OWA).
Tech specs: Exchange 2013 CU5 accessed from Outlook 2013 running on Windows 8.1 Update. Outlook did not log any events during the time when public folders were dropped, nor are there any network connectivity issues being logged.
Any ideas for resolving this?

Hi,
Please check the connection status for Outlook.
Press the CTRL key and right-click the Outlook icon in the notification area, then select Connection Status.
Please run the command get-mailbox administrator | fl defaul* to check the default public folder mailbox for this affected user.
Do you have mail-enabled public folders? If you have mail-enabled public folders, you can check if this user can view public folders in OWA.
If possible, please re-add the public folder permissions for this user to check result.
Best regards,
Belinda Ma
TechNet Community Support

Public folders are not wisible in exchange 2007 EMS

Hello!
I'm experiencing some troubles with public folders. Few months ago I migrated to exchange 2013 CU3, server OS is 2012R2. All public folders are working OK, users can see them in outlook, can send mail to and from them. But in EMS I cannot see public folders
structure. When I'm trying to create new folder, there is error
Summary: 1 item(s). 0 succeeded, 1 failed.
Elapsed time: 00:00:00
Test
Failed
Error:
There is no existing PublicFolder that matches the following Identity: '\'. Please make sure that you specified the correct PublicFolder Identity and that you have the necessary permissions to view PublicFolder.
MapiExceptionUnknownUser: Unable to make connection to the server. (hr=0x80004005, ec=1003)
Diagnostic context:
Lid: 16280 dwParam: 0x6BA Msg: EEInfo: ComputerName: n/a
Lid: 8600 dwParam: 0x6BA Msg: EEInfo: ProcessID: 5368
Lid: 12696 dwParam: 0x6BA Msg: EEInfo: Generation Time: 2014-02-21 09:41:29:149
Lid: 10648 dwParam: 0x6BA Msg: EEInfo: Generating component: 2
Lid: 14744 dwParam: 0x6BA Msg: EEInfo: Status: 1722
Lid: 9624 dwParam: 0x6BA Msg: EEInfo: Detection location: 390
Lid: 13720 dwParam: 0x6BA Msg: EEInfo: Flags: 0
Lid: 11672 dwParam: 0x6BA Msg: EEInfo: NumberOfParameters: 2
Lid: 8856 dwParam: 0x6BA Msg: EEInfo: prm[0]: Unicode string: vls-mail4.vl.veb
Lid: 8856 dwParam: 0x6BA Msg: EEInfo: prm[1]: Unicode string: SERVER_NAME
Lid: 23065 EcDoConnectEx called [length=203]
Lid: 17913 EcDoConnectEx returned [ec=0x3EB][length=56][latency=0]
Lid: 19778
Lid: 27970 StoreEc: 0x3EB
Lid: 17730
Lid: 25922 StoreEc: 0x3EB
Exchange Management Shell command attempted:
New-PublicFolder -Name 'Test' -Path '\' -Server 'server_name'
Elapsed Time: 00:00:00
With powershell I have following
Get-PublicFolder -Server server_name
Get-PublicFolder : There is no existing PublicFolder that matches the following Identity: '\'. Please make sure that you specified the correct PublicFolder Identity and that you have the necessary p
ermissions to view PublicFolder.
At line:1 char:17
+ Get-PublicFolder <<<< -Server server_name
+ CategoryInfo : NotSpecified: (0:Int32) [Get-PublicFolder], MapiOperationException
+ FullyQualifiedErrorId : 9416A968,Microsoft.Exchange.Management.MapiTasks.GetPublicFolder
Checked ADSI, all settings are correct. Application and system logs on server shows nothing.
With PFDAVadmin I can see all PF's structure. Permissions are set correctly.

Hi,
I recommend you refer to the following article to migrate the PF from exchange 2007 to exchange 2013:
Migrate Public Folders to Exchange 2013 From Previous Versions
Exchange supports moving your public folders from the following legacy versions of Exchange Server:
Exchange Server 2010 SP3
Exchange Server 2007 SP3 RU10
Thanks.
Niko Cheng
TechNet Community Support

Public Folders not visible in outlook 2010 for some

Migrated exchange 2007 to 2013. I know Public Folders are a mailbox now.
My question is why do some users with outlook 2010 see the Public Folders under "Tasks" on the left vertical bottom of outlook with "Folder List" highlighted and other DON'T -They just don't see anything under "Tasks" on the
left vertical bottom of outlook with "Folder List" highlighted
Also (in a newly created email) if they go to the address book drop down click on Public Folders entry its empty.
any help would be appreciated
RJM

Hi RJM,
Except above links, I also recommend you refer to the following article to migrate the PF from exchange 2007 to 2013:
http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-4-step-by-step-exchange-2007-to-2013-migration.aspx
Check the status
Once the migration reached the AutoSuspended state as shown below, proceed to the next steps, otherwise you must wait as this may take some time based on your PF size.
Get-PublicFolderMigrationRequest | Get-PublicFolderMigrationRequestStatistics
Lock Down PF for Migration (Down time is required, as during this phase PF will bot be accessible for all users)
Set-OrganizationConfig -PublicFoldersLockedForMigration:$true
Set-PublicFolderMigrationRequest -Identity \PublicFolderMigration -PreventCompletion:$false
Resume-PublicFolderMigrationRequest -Identity \PublicFolderMigration
Test and Unlock the PF Migration
I will configure a test user to use the new PF using the following command:
Set-Mailbox -Identity mohsaeed -DefaultPublicFolderMailbox mailbox1
Open the test user mailbox and run some tests: Create new post, view old posts, check permissions
If all tests passed successful proceed to next step.
Get-Mailbox -PublicFolder | Set-Mailbox -PublicFolder -IsExcludedFromServingHierarchy $false
Set-OrganizationConfig -PublicFolderMigrationComplete:$true
Best regards,
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Niko Cheng
TechNet Community Support

Public Folders Permissions

Similar Messages

Maybe you are looking for