Exchange 2013 - ECP shows wrong public folder permissions

Hi everybody,
I just migrated from Exchange 2007 to 2013 SP1 CU7 and we have an issue with the public folder permissions in ECP. ECP doest not show the correct permissions, here an example:
Get-PublicFolder "\Folder" | Get-PublicFolderClientPermission | ft
FolderName User AccessRights
Folder Default {Author}
Folder Anonymous {None}
Folder Administrator {Owner}
Thank you very much and best regards,
Sebastian

Hi,
Based on your description, the public folder permissions you get using command aren't the same with that you view from EAC.
Please check if you can change the wrong permissions to right in EAC.
If you have multiple public folder mailbox, please move affected public folders to another public folder mailbox and move back to check result.
And if you have multiple DCs, please make sure there is no replication issue between DCs or you can force DC replication and then to check result.
Best regards,
Belinda Ma
TechNet Community Support

Similar Messages

Exchange 2013 Users cannot access Public folder in Exchange 2007 SP3

Dears,
i am working in Upgrading Exchange 2007 to Exchange 2013 CU7,, I came to know with CU7 we have new way for coexistence with legacy Public Folder
https://technet.microsoft.com/en-us/library/dn690134(v=exchg.150).aspx
i did the steps exactly as it is in the article, but now users in Exchange 2013 always prompt for username /password when opening outlook and i found they still trying to connect to Exchange 2007 PF Server using HTTPS and failed..
BTW, Outlook anywhere is disabled in EX2007 and as per this article Q/A , it is no more needed
http://blogs.technet.com/b/exchange/archive/2014/11/07/on-premises-legacy-public-folder-coexistence-for-exchange-2013-cumulative-update-7-and-beyond.aspx
the issue now, still users getting prompted and cannot connect to PF in EX2007,,
your help is appreciated
thanks
Mufleh

I ran into the same situation recently, and found out that you need to make sure InternalClientsRequireSSL is set to false.
To verify: Run Get-OutlookAnywhere | fl Identity, *ssl
If it is true, try setting it to false.
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. This can be beneficial to other community members reading the thread

Exchange 2013 ECP shows no databases. User moves fail referencing an old database of a crashed 2010 server

Our old 2010 server was migrated to 2013 but before removal, the 2010 server failed. Now when I go to my ECP > Servers > Databases, the list is empty. I can't move any users either as the list population fails because it can't find the
old database from the 2010 server. I thought I removed it all from ASDIEdit but something is lingering. Mail is flowing fine at the moment.

Server has been rebooted several times with no success. These are production mailboxes.
Log Name: Application
Source: MSExchangeTransportDelivery
Date: 4/14/2014 5:53:45 AM
Event ID: 5006
Task Category: Routing
Level: Warning
Keywords: Classic
User: N/A
Computer: MAIL1.onshoreit.local
Description:
Cannot find information about owning Mailbox Server CN=MAIL\0ADEL:437877b5-6216-44ea-a145-997cba794f45,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=OnshoreIT,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=onshoreit,DC=local
for database CN=DFMCO_PUB_DB,CN=Databases,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=OnshoreIT,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=onshoreit,DC=local in routing tables with timestamp 4/14/2014 10:53:45
AM. Recipients will not be routed to this database.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="MSExchangeTransportDelivery" />
<EventID Qualifiers="32772">5006</EventID>
<Level>3</Level>
<Task>4</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2014-04-14T10:53:45.000000000Z" />
<EventRecordID>663745</EventRecordID>
<Channel>Application</Channel>
<Computer>MAIL1.onshoreit.local</Computer>
<Security />
</System>
<EventData>
<Data>CN=MAIL\0ADEL:437877b5-6216-44ea-a145-997cba794f45,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=OnshoreIT,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=onshoreit,DC=local</Data>
<Data>CN=DFMCO_PUB_DB,CN=Databases,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=OnshoreIT,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=onshoreit,DC=local</Data>
<Data>4/14/2014 10:53:45 AM</Data>
</EventData>
</Event>
Log Name: Application
Source: MSExchangeTransportDelivery
Date: 4/14/2014 5:53:45 AM
Event ID: 5006
Task Category: Routing
Level: Warning
Keywords: Classic
User: N/A
Computer: MAIL1.onshoreit.local
Description:
Cannot find information about owning Mailbox Server CN=MAIL\0ADEL:437877b5-6216-44ea-a145-997cba794f45,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=OnshoreIT,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=onshoreit,DC=local
for database CN=DFMCO_MAIL_DB,CN=Databases,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=OnshoreIT,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=onshoreit,DC=local in routing tables with timestamp 4/14/2014 10:53:45
AM. Recipients will not be routed to this database.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="MSExchangeTransportDelivery" />
<EventID Qualifiers="32772">5006</EventID>
<Level>3</Level>
<Task>4</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2014-04-14T10:53:45.000000000Z" />
<EventRecordID>663744</EventRecordID>
<Channel>Application</Channel>
<Computer>MAIL1.onshoreit.local</Computer>
<Security />
</System>
<EventData>
<Data>CN=MAIL\0ADEL:437877b5-6216-44ea-a145-997cba794f45,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=OnshoreIT,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=onshoreit,DC=local</Data>
<Data>CN=DFMCO_MAIL_DB,CN=Databases,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=OnshoreIT,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=onshoreit,DC=local</Data>
<Data>4/14/2014 10:53:45 AM</Data>
</EventData>
</Event>
The 2010 box is dead and unable to be restored.

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 2013 Mailbox Using 2010 Public Folders

Firstly, we will not be migrating completely to Exchange 2013 public folders for quite a while. Our first Ex2013 server is in a small branch office and won't be appropriate to hose the PF's for the entire company. Our environment consists of
8 Ex2010 servers and now the one Ex2013. I setup a test mailbox on the 2013 server and it access a 2010 PF database on another server just fine. How is that server discovered, and can we specify which one it uses? I understand the way 2013
public folders are moving but is there a downside to leaving our configuration this way for a long period of time?

Yes, the procedure should be followed to move mailbox first. Once you have successfully moved all the mailbox to new exchange server, you can migrate public folder after that.
You can also checekout this thread related to public folder migration from exchange 2010 to 2013 :
http://social.technet.microsoft.com/Forums/exchange/en-US/b7a35a45-9b74-4910-9dc3-c997bc71f03f/migration-form-exchange2010-to-exchange2013?forum=exchangesvrdeploy
Further, for a better convenience, you can also take a look at this application (http://www.exchangemailboxmigration.com/) which would be a good approach while migrating mailboxes and public folders
between two exchange server. It ensures about the data security and email contents during the completion of entire migration process.

Unable to set Public Folder Permissions

I have created a Public Folder Mailbox and Public Folder. When I go to set permissions via the EAC, the "User" field is grayed out...when I Browse for a user I can search and select a user, but that user is not carried over to the User field where
you would set permissions. I am unable to see ANYYONE with permissions via the EAC. However, when I access my Public Folders in Outlook 2013, I and a co-worker both have "Author" level permissions.
I am an Administrator on the system and have added myself to the Public Folders role and anything else that looked even remotely related :-o
Thanks for the help!
-Nick

Hi,
We can try settings the permission on the specific folders by using the exFolders tool:
https://gallery.technet.microsoft.com/office/Exchange-2010-SP1-ExFolders-e6bfd405
Thanks,
Simon Wu
TechNet Community Support

Exchange 2013 ECP 500 Error

We are in the beginning phase of migrating from Exchange 2010 to Exchange 2013. When I login to the exchange 2013 admin console and navigate to servers it does not show me any of my servers. When I navigate to mailflow-receive connectors I receive a 500
error. When I run the powershell command to get-receiveconnectors it shows me the correct exchange 2013 connectors. I checked IIS and the permissions appear to be correct. Not sure where to look to resolve the issue.

Hi,
From your description, I would like to verify if you can see all the Exchange servers when running the Get-ExchangeServer cmdlet. If yes, the issue should be ECP virtual directory, you can remove this problematic ECP virtual directory and create a new
ECP virtual directory to check the result.
For your reference:
New-EcpVirtualDirectory
https://technet.microsoft.com/en-us/library/dd351218(v=exchg.150).aspx
Hope this can be helpful to you.
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]
Amy Wang
TechNet Community Support

Exchange 2013 ECP 503 error

I have a problem with my two Exchange 2013 servers. There are no mailboxes on the servers, because we are just beginning our migration from Exchange 2007. We are running Exchange 2013 SP1 on Server 2012R2
When I try to access ecp/owa on ex01 (https://localhost or https://ex01.domain.local), I am presented with a login page, but after entering my credentials,
I get a 503 error:
Service Unavailable HTTP Error 503. The service is unavailable
On ex02, I can RDP to the server and log into ecp/owa just fine. However, if I log in (https://ex02.domain.local) from another computer (like my PC), I get the
same credential page and 503 error.
I verified the following:
All of the application pools and Exchange services are started
I do not have any instances of event 2280 in the Application log
I have also restarted the server
Local security policy shows that Administrators and Backup Operators have "Allow log on locally" permission
This feels like a permissions issue in IIS, but I'm not sure.
My ECP virtual directory settings (both servers) look like this:
InternalAuthenticationMethods : {Basic, Fba}
BasicAuthentication : True
WindowsAuthentication : False
DigestAuthentication : False
FormsAuthentication : True
LiveIdAuthentication : False
AdfsAuthentication : False
OAuthAuthentication : False
ExternalAuthenticationMethods : {Fba}
Why won't ex01 let me log in and why would the login on ex02 work from the server, but 503 from my machine? Thanks.

Hi,
From your description, I would like to clarify the following things for troubleshooting:
1. Make sure that the services are running under the Local System account.
2. Ensure that the mailbox database that you want to access are mounted. Besides, the account you use to access ECP should have a mailbox in the Exchange server you are accessing.
Hope my clarification can be helpful to you.
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]
Amy Wang
TechNet Community Support

Exchange 2013 users cannot open public folders on exchange 2010

Migrating from Exchange 2010 SP3 to Exchange 2013 CU3 in same forest and domain
client version is outlook 2013
outlook any where is disable (default) on exchange 2010 which must be disabled as organization policy
outlook any where external host name field is blank (we need to keep outlook any where disable for external)
outlook anywhere internal authentication is set to NTLM and Client require SSL to false
I have moved a mailbox from Exchange 2010 to Exchange 2013, user moved from exchange 2010 to 2013 cannot access public folder on exchange 2010. I have been stuck on this kindly suggest

Hello,
Please explain the sentence "The user moved from exchange 2010 to 2013 cannot access public folder on exchange 2010". Do you mean the moved user can't see the public folder or the user has no permission to see the public folder?
If the moved user can't see the public folder, please check if the moved user can see the public folder via owa. When you use outlook to view public folder, you can following the method: Open outlook, click folder list at the bottom of left panel.
If the user has no permission to see the public folder, please check the permission.
=============================================================
1. Open ADSIEDIT.
2. Navigation to CN=Configuration, DC=Your domain name -> CN=Services ->CN=Microsoft Exchange ->CN=Your organization name ->CN=Administrative Groups ->CN=Exchange
Administrative Group ->CN=Databases ->CN= PF Database.
3. Right-click the PF Database, and then select Properties. Under Security, check if everyone has read permission.
Besides, please check if public folder replication is ok. You can use Get-PublicFolderStatistics cmdlet to compare item count, size.
Additional article for your reference.
http://technet.microsoft.com/en-us/library/jj150486(v=exchg.150).aspx
If you have any feedback on our support, please click
here
Cara Chen
TechNet Community Support

Exchange 2013 ECP Login fails HTTP 404 Requested URL: /owa/auth/logon.aspx

Hi,
One of our Exchange servers stopped allowing access to OWA and ECP. I have now managed to get OWA working but ECP is still failing. When connecting to ECP using https://servername/ecp/ it asks me for my username and password. After hitting enter it shows
me an error page:
Server Error in '/owa' Application.
The resource cannot be found.
Description: HTTP 404. The resource you are looking for (or one of its dependencies) could have been removed, had its name changed, or is temporarily unavailable. Please review the following URL and make sure that it is spelled correctly.
Requested URL: /owa/auth/logon.aspx
URL in the address bar while on this screen: https://exchangeserver:444/owa/auth/logon.aspx?url=https://exchangeservera:444/ecp/&reason=0
Question: When the URL points to servername:444/owa/auth/logon.aspx - Is it trying to find the logon.aspx in C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\Owa\auth? There is no such file in that directory?
I have removed and recreated the ECP and OWA virtual directories several times.
I am trying to login using a domain administrator account.
Thanks,

Hi,
Is there any Exchange server 2010 coexistence with your Exchange 2013 server? If it is, please try the URL
https://CAS15-NA/ecp?ExchClientVer=15 to access ECP.
Also run the following to check your OWA and ECP virtual directories:
Get-EcpVirtualDirectory -ShowMailboxVirtualDirectories | FL Identity,*Authentication*
Get-OwaVirtualDirectory -ShowMailboxVirtualDirectories | FL Identity,*Authentication*
And make sure the Basic and Forms authentications are enabled in
Default Web Site and Ntlm, WindowsIntegrated
authentication methods are enabled in
Exchange Back End. Then restart IIS service by running
iisreset /noforce from a command prompt window.
If the issue persists, please collect any event logs or IIS logs for further analysis.
Thanks,
Winnie Liang
TechNet Community Support

Exchange groupware connector cannot read public folder

Hi,
we're installing the Groupware Connector for Exchange (2003) on a Win2003 SP1 server. The installation is simple, but when starting the service, the following error occurs:
[26/Apr/2006:11:33:52 +0200] WARNING - - - - - "[WRN:1010] Invalid default target folder for contacts: [email protected] does not specify public folder
. Please verify 'replica.contacts.default-target' option in config.xml." Source: Common\GroupWare.cpp:199
I tried installing and starting the connector on both the exchange server and a seperate server, but in both a cases the message appears.
The public folder exists (called "contacts"), has an email address: [email protected] and we can sent emails to it and they arrive in the contacts folder. As far as I know we executed all the steps in the installation guide (permissions etc) but for some reason the connector cannot see the public folder.
Any ideas?
I've read the two notes: 908577 and 908571
Much obliged
Marcel Rabe

Hi,
Once again very sorry for such a delayed reponse ... i don't know how did i missed your response ... anyway
You can find version of Connector 2.1.053 after you install it on a system and right click on the connectorsvc.exe and go to the version tab, find the version of the GWC.
What ever versions you have mentioned i.e., 2.1.036 and 2.1.037 are versions of Install package of GWC (which is a common for both exchange gwc and lotus gwc ).
If you still have some problems with it then revert back to me via e-mail so that i won't miss your response.
regards,
Gokul
[email protected]

Public Folder permissions to groups not working

Hello Together,
I have some problems with permission of Exchange 2010 (SP2) public folders. Although I can't find an TechNet article which describes the procedure to add a group to a public Folder client permission list, it should be possible because the
Add-PublicFolderClientPermission cmd-let will accept Users and groups as parameter for -user.
But if I give permissions to groups the members of the Groups can't access the public folders.
What I exactly do is this:
- Create a Distribution Group for example TEST (Universal Distribution Group)
- Add User "Testuser" to this Group
- Add public folder Clientpermissions to the Group "Test" which autmatically changes the group type to Universal Security Group (there is no difference if I do this with the GUI or management shell)
Result: No Access for User "Testuser"
If I add the User directly to the Public folder he can acces the folder.
I can reproduce this problem in my test- and my Productionenvironment.
Any ideas?
Best regards
Hans Moggert
Hans Moggert Technical Account Manager Geschäftsbereich Technologie & Service Allgeier IT Solutions GmbH

Hi Martina,
thank you for your very fast answer, but this was exactly what I had done ...
But Today, if I tried to access the Public Folder again everything works as expected, so I tried to find out why I have to wait so long until the expected permissions work and now I think I have found the reason:
- Exchange 2010 uses Universal Groups for Distribution and Security Groups
- Universal Groups are the only Grouptypes which saves the member list at the Global Catalog server
- the default Global Catalog Caching interval is 1440 Minutes (24 hours)
So if you change membership of universal Groups you have to wait 24 hours until Exchange recognizes this change!
If you want to force this you can do one of the following steps:
- reduce the "Cached Membership Refresh Interval (minutes)"
http://technet.microsoft.com/en-us/library/how-global-catalog-servers-work(v=ws.10).aspx
- Use the following VB-Script:
set objRoot = GetObject("LDAP://rootDSE")
objRoot.Put "UpdateCachedMemberships", 1
objRoot.SetInfo
msgbox "Universal Group Cache refreshed!"
This forces the Group members to refresh immediatly.
I think I am not the only person who had this problem so I hope I can help others with this solution ...
Best regards and thx
Hans Moggert Technical Account Manager Geschäftsbereich Technologie & Service Allgeier IT Solutions GmbH

Exchange 2007 error relating to Public Folder Database

Hi
We migrated from Exchange 2003 to Exchange 2007 recently as we already had the licence so decided to take advantage of it.
We unfortunately forgot to migrate the Public Folders as we mistakenly thought as we didn't use them they were no longer needed in Exchange 2007.
We are now receiving
"Event ID 8207, MSExchangeFBPublish
Error updating public folder with free/busy information on virtual machine BARR-EXCH-001. The error number is 0x80004005."
On the server, I have tried http://support.microsoft.com/kb/945602 and the command
doesnt show an error but
Get-PublicFolder -Identity "\NON_IPM_SUBTREE\SCHEDULE+ FREE BUSY" -Recurse | fl name,Replicas
Still shows no entry for the NON_IPM_SUBTREE\SCHEDULE+ FREE BUSY. I have been advised to create a new PF store on the server as the one currently is probably empty or corrupted.
To do this would I follow this article http://technet.microsoft.com/en-GB/library/bb123687(v=exchg.80).aspx
Or
Dismount the public folder database on the Exchange 2007 serverGo to the folder path of the EDB filedelete\move the EDB fileGo back to the management console and mount the
public folder database. You will get a warning that one or more database files is missing. Go ahead and clickOK to mount a blank database file.?
Any help/advice appreciated.
Cheers
Cheers Chris

Hi,
If the existing file is corrupt, I recommend you recreate a new public folder database in Exchange 2007.
To create a new public folder database, you can refer to the following article.
How to Create a New Public Folder Database
http://technet.microsoft.com/en-GB/library/bb123687(v=exchg.80).aspx
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Exchange 2013 User cannot view public folders

Good morning,
User was able to view public folders, then lost connection to public folders. User cannot view public folders in OWA.
Verified proper permissions. No changes have been made to the user account in AD, exchange.

Did you do a fresh install of Exchange, meaning there was no version of Exchange installed previously? If not, have you moved Public Folders over to Exchange 2013 yet? If the answer to this question is no, then you will not be able to view Public
Folders in OWA until they are migrated over Exchange 2013.

Exchange 2013 ECP/OWA Error 503 Service Unavailable

Hi,
Hoping that someone can clarify or assist with an issue relating to Exchange 2013 CU3..
Both roles installed on a single 2012 server, mailboxes created, able to login to ECP/OWA using ht tps://servername.int.domain.com/ecp using the out of the box internally generated SSL certificate.
Virtual directory internal and external settings for all directories were configured to be ht tps://mail.domain.com/owa /ecp /EWS etc and a UCC certificate (containing mail.domain.com, autodiscover.domain.com)from GoDaddy was imported and assigned to
IIS and SMTP, internal DNS records were setup internally and externally for mail.domain.com and full propagated, Outlook Anywhere enabled and configured to mail.domain.com, external access configured for all virtual directories
The issue is that ECP and OWA can only be accessed internally by the full internal server FQDN URL ht tps:// serverame.int.domain.com/ecp whereas it should be accessible at this point by ht tps:// mail.domain.com/ecp
Error received both internal and external when trying ht tps://mail.domain.com / owa / rpc etc is error 503 Service Unavailable
I know that the ECP and OWA sites are up and running as I can login and do anything by internal servername URL but no joy at all using the external (which is to be used for internal clients aswell for seamless access)
The only way it works is by adding a host name to the 2 x 443 bindings in IIS for the front end website and set it to mail.domain.com but this means autodiscover.domain.com internally and externally wont work
Is this normal and required for Exchange 2013 or is there a way to resolve this?
Thanks in advance!

Hi,
I found a article might help you, for you reference:
http://support.microsoft.com/kb/2619402
Generally, this error occurs if the application pool that is associated with the web application doesn't start.
To troubleshoot this issue, follow these steps:
In Event Viewer, view the System log to find errors from the Microsoft-Windows-WAS source. An event is frequently logged in the System log if the application pool fails to start.
If you don't find any relevant events in the System log, search for relevant entries in the HTTPERR log file. The httperr1.log file is located in the following system folder:
c:\windows\system32\logfiles
In the file, search on "503" to locate any relevant information about why the application pool failed. For example, you may see an entry that resembles the following:
2011-12-08 18:26:42 ::1%0 6721 ::1%0 443 HTTP/1.1 GET /owa 503 3 N/A SharePoint+Web+Services+Root
Thanks.
Niko Cheng
TechNet Community Support

Exchange 2013 - ECP shows wrong public folder permissions

Similar Messages

Maybe you are looking for