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

Similar Messages

  • 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.

  • Outlook - One user cannot expand public folders

    I have one user who is having an issue with expanding Public Folders.  They are the only one in their area who cannot expand it and I'm running out of troubleshooting steps.  Here is a list of what I've tried/found for this issue.  The Public
    Folders are on Exchange 2007 and we have our mailboxes on Exchange 2013.  Outlook version is 2010.  This also does not work in our Citrix environment either.
    Repaired email account
    Removed/re-added Outlook profile
    Log off/log on
    Reboot PC
    Confirmed that she can’t get to them in Citrix either
    Checked the Outlook connection status, no Public Folders connection is listed there.
    Rebooted the Public Folder server.
    Removed/re-added PF permissions AD groups, log off/log 
    Move the mailbox do a different mailbox database
    RPC Client Access service is running on the mailbox server
    I am pretty much at a loss here and I am not sure what else to do.  Thanks!

    Hi,
    From your description, only one user can't expand public folders in Exchange 2007 after you migrate users to Exchange 2013.
    Could this user send or receive message normally?
    Please use the Test E-mail Autoconfiguration to check result, compare with other normal users to see if there is any difference.
    Please click on the link below to make sure your Microsoft Outlook is up to date.
    http://support.microsoft.com/kb/2625547
    Best regards,
    Belinda Ma
    TechNet Community Support

  • 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

  • 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

  • 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

  • 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

  • Unable to Open Public folders from Windows XP after the upgrade of CU4 to Cu7

    We still have few machines running windows Xp, who cannot access Public folders after the upgrade to the latest CU7. Is there any fix for it other than moving them to Windows 7?

    Hi DNair,
    Hope you are already upto date. But still just putting it through to cross check.
    Outlook Versions Supported by Exchange 2013
    The following Outlook client versions are fully supported by Exchange server 2013. Please bear in mind there’s a difference between what is supported and what might be compatible with Exchange 2013.All
    of the Outlook versions listed below have been thoroughly tested by the Exchange Product group:
    Outlook 2013
    Outlook 2010 SP1 with November 2012 Cumulative Update ( available from
    http://support.microsoft.com/kb/2687623 )
    Outlook 2007 SP3 with November 2012 Cumulative Update ( available from
    http://support.microsoft.com/kb/2687404 )
    Entourage 2008 for Mac, Web Services Edition
    Outlook for Mac 2011
    Outlook clients earlier than Outlook 2007 are not supported.
    Find and Manage
    Outlook Updates here.
    Regards,
    Satyajit
    Please “Vote As Helpful”
    if you find my contribution useful or “Mark As Answer” if it does answer your question. That will encourage me - and others - to take time out to help you.

  • Migrated user cannot open outlook or log into owa

    We are in the middle of an Exchange 2013 migration from 2007 and this is the 2nd time I've encountered this issue.  The migrated user cannot open outlook or log into owa.  The error that is thrown in owa is below.  I cant really find any info
    on this error.  Also, notice the date.  No idea where its getting that.  We've moved about 7000 users and I've seen this on two of them.  I'd appreciate any insight on this.  Thanks.
    X-OWA-Error: SDServerErr;Microsoft.Exchange.UM.UMCommon.InvalidPrincipalException
    X-OWA-Version: 15.0.847.32
    X-FEServer: server01
    X-BEServer: server01.domain.com
    Date: 1/2/1601 2:47:50 PM
    Rich

    Hi,
    Based on my research, the issue can be caused by Duplicate legacyExchangeDN properties. Thus, let’s check it and remove or change it:
    Check if the properties of the two problematic users is same. If it’s same, we can change the value.
    If not, let’s check if there are other users who have the same value with the two users:
    Use LDP.exe to search "legacyexchangedn=/o=…”.
    http://support.microsoft.com/kb/252335
    If you have any question, please feel free to let me know.
    Thanks,
    Angela Shi
    TechNet Community Support

  • PC users cannot open my Pages-exported PDF documents

    Has anyone encountered this? When I want to give someone a PDF, I need to export it from Pages, choose "Open with Adobe Reader," and then re-save from Reader as a different name. (If I just export from Pages, some PC users cannot open it.) When I look at the file information for these two supposed PDFs, the one that's only exported from Pages says "Portable Document Format (PDF)" and the one opened and resaved with Reader says "Adobe PDF Document." What's going on here? Is there a reason my PC friends can't open a Pages-generated PDF?

    Thanks for the suggestions. Funny, when I changed the "Open With" selection inside the "File Info" box to tell it to use Reader, it it still tells me in the "General" information section that it's a "Portable Document Format (PDF)", but it does replace the "Preview" icon in the upper left with the Adobe logo. Only the version that I physically opened with Reader and re-saved lists the "Kind" of document as an "Adobe PDF Document". Wacky.
    Regarding the extension, when I exported from Pages, the "Hide Extension" box was unchecked in the "Save" window, yet the file's PDF extension is in fact hidden (and the "File Info" box also says it's hidden). What's up with that? Grr.
    Seems like a small bug--now I just have to get some PC-using friends to let me know which ones they can open! Thanks for your (tres rapide) help guys!

  • Some Users cannot Open Workflow Approval Task

    We have a SPD workflow published to our production site and it includes a 'Start Approval Process' task which involves a number of users (determined by a lookup to another list) this worked brilliantly until we republished the workflow with some minor changes,
    none of which were to this particular approval task. Now we are seeing some strange behaviours. When some users click the task to approve they are seeing 'This from cannot be opened in a browser, To open this form use Microsoft Infopath'. Now strangely it's
    only certain users, if you're a site collection admin you never have this error. So if a user previously had the error and i then add them to the site collection administrators list the error goes away and they can complete the task.
    Obviously not a solution! giving users full control permissions on the task list or task item doesnt fix the error either. The same workflow on our UAT works without any issues. The task forms in SPD have not been customised either. Its a SP2010 Standard
    farm with no infopath services obviously. Bizarrely there are some users with only Contribute rights to the task list who can open approve tasks, so it's looking like a permissions issue to me but I'm at a loss to find a fix. I've tried totally removing
    the worklows and republishing, regenerating the .xsn task forms in SPD by deleting them and republishing, removing and re-adding the task related content types to site, Changing the Approval Task settings 'only allow users to edit their tasks...' to false
    and then back to true, the works, but to no avail.
    Anybody any ideas?
    TIA
    Chris

    Hi,
    According to your post, my understanding is that Some Users cannot Open Workflow Approval Task.
    I recommend that you can create a new list and workflow to check whether it works.
    Then use the user who get the error to open task.
    If he can open the task in the brower, the issue is related to the older list.
    Then you can use the new created list and assgin the task.
    Here is a similar thread for your reference:
    https://social.msdn.microsoft.com/Forums/en-US/67dc8577-f248-4d6c-bb82-3aca0f084d24/this-form-cannot-be-opened-in-a-web-browser-error-not-an-infopath-form?forum=sharepointcustomizationprevious
    Thanks,
    Linda Li                
    Forum Support
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Linda Li
    TechNet Community Support

  • How to retrict user cannot open the same form more than once (Forms 6i)

    Our users always open the same forms more than once. For example the customer form, the user may access a customer record in the first form, however, he will open a new customer form to edit the same record, the result is he cannot save the record because the record is locked in the first customer form.
    How can I control the user cannot open the same form more than 1 time.
    Best Regards,
    Kane

    The customer form is only an example, I found there will cause a lot of problems is I cannot control the user from calling 1 program more than 1 than within application. Sometimes a user (not good in using computer) will overlap the form for many times.....
    Is there any simple way to do that?...can I have some PL/SQL statement or build-in functions that let me easily found our what forms the user has already opened, then I can control whether I let him open this form or not.
    Urgent...please
    Thanks

  • Office 365 Outlook is now frozen. I cannot open outlook folders or mail. Can't access Options either. Works fine in IE.

    Office 365 Outlook is now frozen in Firefox.
    I cannot open Outlook folders or mail.
    Can't access Outlook Options either.
    Works fine in IE.
    Running latest Firefox, Win 7 and Office 365/Office 2010
    Cheers
    John

    LOL It worked! Thanks for your help. I will keep this handy in case I need to do it again!

  • Why the remote user cannot open any folds?

    Why the remote user cannot open any folds?
    I create a user user8 and already grant the user the role connect, OLTP-user, and resource. I also assign this user unlimited space in the user8 tablespace. But after connection, the user8 cannot open any folds and the connection is terninated automaticlly.

    Why the remote user cannot open any folds?I don't know what you have.
    I don't know what you do.
    I don't know what you see.
    It is really, Really, REALLY difficult to fix a problem that can not be seen.
    use COPY & PASTE so we can see what you do & how Oracle responds.
    do as below so we can know complete Oracle version & OS name.
    Post via COPY & PASTE complete results of
    SELECT * from v$version;

  • Windows users cannot open my Pages documents

    Even though I check Windows Friendly Attachment, Windows users cannot open my Pages documents. Is there anyway to fix this problem?

    KOENIG Yvan wrote:
    I decided that I will not replicate what is printed in the available documents.
    If the only questions we're going to answer are the ones that aren't already answered in the manual, then these discussions will consist of little more than directing people to page numbers. Yes, it would be nice if people read the manual before posting here. But everyone's brain works a little differently, and I don't mind if nice people ask questions that can be solved by reading the manual or doing a search in this discussion group. Even figuring out how to find things in the manual isn't intuitive to a lot of people.
    In terms of helping people, it's actually a lot less work to provide a solution for them than to look it up in the manual, then come back and report the page number.
    We have a saying in America that goes like this: Different strokes for different folks. You can thank Sly and the Family Stone for that one.
    -Dennis

Maybe you are looking for