Exchange 2013 Public Folder Missing in Outlook

Hello,
i have succesfully migrated from Exchange 2010 to Exchange 2013.
Everything was running after i migrated the public folders they disappeared on the Clients after starting Outlook 2013.
We are able to see the public Folders in OWA but not in Outlook.
Anybody know this Problem and can help?
regards
René

Hi,
Based on the description, everything was running after you migrated from Exchange 2010 to Exchange 2013. When you upgraded from Outlook 2010 to Outlook 2013, you couldn't see public folders in Outlook 2013. However, you could see public folders in Outlook
2010, but you couldn't expand it. OWA worked well.
If I misunderstood your concern, please feel free to let me know.
About "No we had migrated to Office 2013 before but tested it now with Outlook 2010.", was the Outlook 2010 client a remaining Outlook 2010 client?
Did the issue affect all users or some of them?
Could you please switch between online mode and cached mode to check the result?
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Similar Messages

  • Exchange 2013 - Public Folder Mailbox and Single Item Recovery

    Hello,
    I recently had a request to recover some messages that an ex-employee deleted from the "recover deleted items" folder in their public folder. Since this resides on a public folder mailbox and it does have the option for
    "Single Item Recovery" to be enabled on the box (which I enabled not knowing if this really works or not), is there a way I can still recovery these items or do I have to go to a backup to obtain those messages. Since ExFolders does not work that
    is not an option. I've seen commands to restore a public folder that was deleted but not items that were deleted directly from a public folder. I checked using MFCMAPI and I do see the dumper root and the public folder dumpster for each folder but it
    looks to be only the "deletions" folder and don't see anything similar to a "purges" type folder. Any ideas or am I stuck recovering from backup? Thanks in advance!

    So I think you are stuck and will need to restore the EDB to a Recovery Database to restore the items because when the end user purged the items from the "Recover Deleted Items" it removes them from the Recoverable Items/Deletions folder. 
    Check out this article
    http://blogs.technet.com/b/exchange/archive/2013/08/23/recovering-public-folder-information-in-exchange-2013.aspx
    I have not played with the recoverable items settings on the 2013 public folder enabled mailbox EDB  but you might try checking out Litigation or In Place Hold to use as a safety mechanism moving forward.  That said this will also increase the
    DB size so consider all the options before implementing
    Search, Recover, & Extract Mailboxes, Folders, & Email Items from Offline Exchange Mailbox and Public Folder EDB's and Live Exchange Servers or Import/Migrate direct from Offline EDB to Any Production Exchange Server, even cross version i.e. 2003 -->
    2007 --> 2010 --> 2013 with Lucid8's
    DigiScope

  • Outlook save/update error with Exchange 2013 public folder used as Contact Items

    Hello Everybody.
    This problem is driving me crazy.
    In Exchange 2013 i have created a public folder with several subfolders used as Contact Items.
    I've reviewed all settings several times and all is ok.
    Outlook 2010/2013 users several times receive the message:
    "The item cannot be saved to this folder. The folder was deleted or moved, or you do not have permission. Do you want to save a copy of it in the default folder for the item?"
    when try save an existing contact after modification.
    I can assure you that user permissions, server configurations are ok; please, help me.

    Did you make the subfolder the correct type, i.e., a contacts-type folder?
    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

  • Exchange 2013 - Public folder search not working

    Hi There,
    We have Exchange 2013 install on server 2012 and clients using Outlook 2010 on Windows 7.
    Since we have installed the system a search of the public folders always returns no results even if we know the email is there. Any suggestions?
    Thank you
    Dave

    Hi Triumphtech,
    Yes, if our Exchange 2003 environment is healthy, it will work.
    Please forgive me for the silly clarification. If we used Exchange 2003 and wanted to migrate to Exchange 2013. We must migrate to Exchange 2007/2010 first, then to Exchange 2013.
    So please make sure we have moved the public folder successfully first.
    And great information from Tarique Noorain.
    According to  the article, I found some points for your reference:
    1. Although a full text search of public folder content is available, public folder content isn't searchable across public folders and the content isn't indexed by Exchange Search.
    2. You must use Outlook 2007 or later to access public folders on Exchange 2013 servers.
    Feel free to contact me if there is any problem.
    Thanks
    Mavis
    Mavis Huang
    TechNet Community Support

  • Exchange 2013 user cann't access exchange 2013 public folder

    Hi, during the coexistence exchange 2007 and exchange 2013, outlook is unable to access public folder of exchange 2007 from exchange 2013, I've install CU2 for exchange 2013 and also set authentication to Ntlm, but also failed. please help to look into this
    problem, thanks.
    belows are information about outlook anywhere in our exchange.
    exchange 2007：(primary site)shmail04,shmail05,shmail06; (DR site)drpmail05,drpmail06
    exchange 2013：(primary site)shcas01,shcas02; (DR site)wxcas01
    Identity                           : SHCAS01\Rpc (Default Web Site)
    InternalHostname                   : infor.tdw.com
    InternalClientAuthenticationMethod : Ntlm
    InternalClientsRequireSsl          : True
    ExternalHostname                   : infor.tdw.com
    ExternalClientAuthenticationMethod : Ntlm
    ExternalClientsRequireSsl          : True
    IISAuthenticationMethods           : {Ntlm}
    Identity                           : SHCAS02\Rpc (Default Web Site)
    InternalHostname                   : infor.tdw.com
    InternalClientAuthenticationMethod : Ntlm
    InternalClientsRequireSsl          : True
    ExternalHostname                   : infor.tdw.com
    ExternalClientAuthenticationMethod : Ntlm
    ExternalClientsRequireSsl          : True
    IISAuthenticationMethods           : {Ntlm}
    Identity                           : WXCAS01\Rpc (Default Web Site)
    InternalHostname                   : infor.tdw.com
    InternalClientAuthenticationMethod : Ntlm
    InternalClientsRequireSsl          : True
    ExternalHostname                   : infor.tdw.com
    ExternalClientAuthenticationMethod : Ntlm
    ExternalClientsRequireSsl          : True
    IISAuthenticationMethods           : {Ntlm}
    Identity                           : SHMAIL04\Rpc (Default Web Site)
    InternalHostname                   :
    InternalClientAuthenticationMethod : Ntlm
    InternalClientsRequireSsl          : False
    ExternalHostname                   : legacy.tdw.com
    ExternalClientAuthenticationMethod : Ntlm
    ExternalClientsRequireSsl          : True
    IISAuthenticationMethods           : {Ntlm}
    Identity                           : SHMAIL05\Rpc (Default Web Site)
    InternalHostname                   :
    InternalClientAuthenticationMethod : Ntlm
    InternalClientsRequireSsl          : False
    ExternalHostname                   : legacy.tdw.com
    ExternalClientAuthenticationMethod : Ntlm
    ExternalClientsRequireSsl          : True
    IISAuthenticationMethods           : {Ntlm}
    Identity                           : SHMAIL06\Rpc (Default Web Site)
    InternalHostname                   :
    InternalClientAuthenticationMethod : Ntlm
    InternalClientsRequireSsl          : False
    ExternalHostname                   : legacy.tdw.com
    ExternalClientAuthenticationMethod : Ntlm
    ExternalClientsRequireSsl          : True
    IISAuthenticationMethods           : {Ntlm}
    Identity                           : DRPMAIL05\Rpc (Default Web Site)
    InternalHostname                   :
    InternalClientAuthenticationMethod : Ntlm
    InternalClientsRequireSsl          : False
    ExternalHostname                   : legacy.tdw.com
    ExternalClientAuthenticationMethod : Ntlm
    ExternalClientsRequireSsl          : True
    IISAuthenticationMethods           : {Ntlm}
    Identity                           : DRPMAIL06\Rpc (Default Web Site)
    InternalHostname                   :
    InternalClientAuthenticationMethod : Ntlm
    InternalClientsRequireSsl          : False
    ExternalHostname                   : legacy.tdw.com
    ExternalClientAuthenticationMethod : Ntlm
    ExternalClientsRequireSsl          : True
    IISAuthenticationMethods           : {Ntlm}

    Hi,
    I have found an article said that we need to set the external host name the same. See more details in the following link:
    http://blogs.technet.com/b/mspfe/archive/2013/10/21/upgrading-to-on-premises-exchange-server-2013.aspx
    To allow your Exchange 2013 Client Access server to redirect connections to your Exchange 2007 servers, you must enable and configure
    Outlook Anywhere on all of the Exchange 2007 servers in your organization. If some Exchange 2007 servers in your organization are already configured to use Outlook Anywhere, their configuration must also be updated to support Exchange 2013.
    The following configuration is set on each Exchange 2007 server:
    The Outlook Anywhere external URL is set to the external hostname of the Exchange 2013 server.
    Sent By
    Silver

  • Exchange 2013 Public Folder Migration Problem

    Hi All,
    Wonder if any of you can assist with a public folder issue I am having with Exchange 2013. We have migrated from Exchange 2010 to 2013.
    I have followed the guide for public folder migration here
    http://technet.microsoft.com/en-us/library/jj150486(v=exchg.150).aspx
    Everything went fine and as per the document - except I had to use the "largeitemlimit" parameter to get the public folder migration to complete.
    We tested the public folder migration by adding content to public folders and creating public folders and it all appeared to be OK, we completed the migration and removed our old public folder databases from Exchange 2010.
    However we noticed later that users cannot CREATE folders in SOME public folders. It appears from some testing that any folder that does not lie in the first public folder mailbox, end users cannot create public folders.  Administrators can create them
    fine from the ECP - just not from outlook.
    It also appears some users cannot see some folders that they have permissions to.
    Can anyone assist with some ideas to resolve ?
    Thanks.

    Question?
    Are you able to create the Folder in OWA?
    Cheers,
    Gulab Prasad,
    Technology Consultant
    Blog:
    www.exchangeranger.com 
    Twitter:
       LinkedIn:
    Check out CodeTwo’s tools for Exchange admins   
    Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.
    it is not functionally possible to create Public Folders in OWA user interface in Exchange 2013!.... From admin ECP it works fine!
    My Bad, that's what I was trying to say.
    Testing the same thing in the LAB, should have some update tomorrow morning.
    Cheers,
    Gulab Prasad,
    Technology Consultant
    Blog:
    www.exchangeranger.com 
    Twitter:   
    LinkedIn:   
    Check out CodeTwo’s tools for Exchange admins   
    Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

  • Exchange 2013 public folder can not create folder

    hello,
    we have migrate public folders to20102013.
    we can not createfolders / files inpublic folders.Access Rights seems to be
    ok on the control panel
    in Outlook, we can not apply change permissions
    what can i do to fix that ?
    all the public folder have migrate on the secondary mailbox public folder like the technet KB
    Please, help us !
    thank you

    Could you please have a look at below mentioned links ? May be, it will help you to sort-out the issue which you are getting right now while moving public folder :
    http://redmondmag.com/articles/2013/07/15/exchange-2013-cu2.aspx
    http://www.msexchange.org/articles-tutorials/exchange-server-2013/planning-architecture/exchange-2013-preview-public-folders-part1.html
    Carlo

  • Exchange 2013 Public Folder Calendars in OWA

    Hello,
    I have a Public Folder calendar that I need to publish via OWA in Exchange 2013.  I understand that you cannot view any public folder that is not mail enabled in OWA.  If I make this specific calendar mail enabled will I be able to view the calendar
    in OWA?  I think I still have to convert this to a shared mailbox.  If that is the case, what are the best steps to perform that?

    Hi,
    Yes I agree with Ed Crowley. In Exchange 2013 Cumulative Update 1, Microsoft have allowed to display public folders. However, two major restrictions exist. First, OWA can only display modern public folders. In other words, you have to complete your
    migration to Exchange 2013 and then execute a public folder migration before OWA can be used. No access is possible to legacy public folders. Second, OWA can only display “mail public folders”, or public folders that contain “mail and post items” (as they
    are referred to by Outlook). Other folders (calendars, contacts, tasks, notes, InfoPath, and journal items) are unsupported.
    Regards,
    Santhosh,
    www.jijitechnologies.com

  • Exchange 2013 Public Folder Accessability Issues

    After migrating from Exchange 2010 to Exchange 2013 we are experiencing random issues accessing Public Folders.  Issues range from a hung server requests to on-screen errors like this one:
    “Cannot expand the folder. Microsoft Exchange is not available. Either there are network problems or the Exchange server is down for maintenance”
    We are using groups to manage permissions, verified that they are mail enabled, and have used the following PS command to re-propagate permissions:
    ./AddUsersToPFRecursive.ps1 -TopPublicFolder "%folder%" -User "%groupname" -Permissions %permissionlevel"
    The odd thing is that if the user bounces between on of their Inbox folders then back to one of the Public folders or restarts Outlook it seems to resolve itself.
    Ideas?

    Hi Niko,
    Firstly, apologies for the delayed update...
    We are still experiencing random loss of access to Public Folders, I would think it would be so much easier if I could replicate the problem quickly and easily however that is not the case as I ran into this issue again this morning.
    I am really at a loss for explanation, what I can offer is when we had migrated from Exchange 2000 to Exchange 2010 I had to export the PF out to a pst file prior to importing them on the new server installation.  While migrating from Exchange 2010
    to Exchange 2013 we did follow the migration process.
    Here is what our current settings from Get-OutlookAnywhere -Server %Server%
    RunspaceId                         : e2e4f324…
    ServerName                        
    : %server%
    SSLOffloading                     
    : True
    ExternalHostname                  
    : <set>
    InternalHostname                   : <set>
    ExternalClientAuthenticationMethod : Ntlm
    InternalClientAuthenticationMethod : Ntlm
    IISAuthenticationMethods          
    : {Basic, Ntlm, Negotiate}
    XropUrl                           
    ExternalClientsRequireSsl         
    : True
    InternalClientsRequireSsl         
    : True
    MetabasePath              
            : IIS://%server%/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                             : %server%
    AdminDisplayName             
    ExchangeVersion                   
    : 0.20 (15.0.0.0)
    Name                              
    : Rpc (Default Web Site)
    DistinguishedName                 
    : CN=Rpc (Default Web Site),CN=HTTP,CN=Protocols,CN=%server%,CN=Servers,CN=Exchange
                        Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=%company%
    Software,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=%domain%,DC=net
    Identity                           : %server%\Rpc (Default Web Site)
    Guid                              
    : 0bf08d0e…
    ObjectCategory                    
    : %domain%/Configuration/Schema/ms-Exch-Rpc-Http-Virtual-Directory
    ObjectClass                       
    : {top, msExchVirtualDirectory, msExchRpcHttpVirtualDirectory}
    WhenChanged                       
    : 5/5/2014 3:08:31 PM
    WhenCreated                       
    : 2/20/2014 2:13:17 PM
    WhenChangedUTC                    
    : 5/5/2014 8:08:31 PM
    WhenCreatedUTC                    
    : 2/20/2014 8:13:17 PM
    OrganizationId                    
    OriginatingServer                 
    : %server%
    IsValid                           
    : True
    ObjectState                       
    : Changed

  • Exchange 2013 Public Folder Migration Not Listed

    I started a public folder migration from my 2010 SP3 Exchange server to my new 2013 SP1 Exchange server. Somewhere during the process I failed. Not sure where but I am now at the point where if I try to create a new public folder on teh 2013 box i get a
    warning like this.
    An existing Public Folder deployment has been detected. To migrate existing Public Folder data, create new Public Folder mailbox using -HoldForMigration switch.
    So I then run Get-PublicFoldermIgrationRequest to see what is still waiting... I get no migration listed in Exchange Management Shell.
    I would like to find the place in AD or in the Server that thinks there is still an active request out there and remove it so I can start again with a clean slate. How do I do that?
    Thanks!

    Hi Zulea,
    This is a known issue, I recommend you refer to the following article to resolve the issue:
    http://support.microsoft.com/kb/3004062/en-us
    Cause:
    This problem occurs when the Exchange organization coexists with an earlier version of Exchange Server, and one or more public folder databases from the earlier version of Exchange still exist.
    Resolution:
    To resolve this issue, use one of the following methods.
    Method 1: Create the mailbox by using the -HoldForMigration switch:
    This option lets an administrator create a public folder mailbox in order to begin a migration from the existing public folders:
    Open the Exchange Management Shell.
    Run the following cmdlet to create the public folder mailbox:
    New-Mailbox "Public Folder Mailbox" -PublicFolder -HoldForMigration
    Method 2: Remove all public folder databases from earlier versions of Exchange Server
    To remove existing public folder databases, see the following TechNet websites, as appropriate for the version of Exchange that an existing public folder resides on.
    Exchange 2010:
    http://technet.microsoft.com/en-us/library/dd876883(v=exchg.141).aspx
          (http://technet.microsoft.com/en-us/library/dd876883(v=exchg.141).aspx)    
    Exchange 2007:
    http://technet.microsoft.com/en-us/library/aa998329(v=EXCHG.80).aspx
          (http://technet.microsoft.com/en-us/library/aa998329(v=EXCHG.80).aspx)    
    Create the public folder mailbox by using either the Exchange Admin Center (EAC) or the Exchange Management Shell (EMS). To do this, see the following TechNet website:
    http://technet.microsoft.com/en-us/library/jj552410(v=exchg.150).aspx
    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

  • Exchange 2010 to Exchange 2013 Public Folder Problem

    Dear Experts,
    I am in a face of migrating Exchange 2010 to Exchange 2013. Below are my infrastructure details,
    1) Parent Domain in Site A (abc.com)
    2) One Child domain in Site A named child1.abc.com and Exchange 2007 is running in Site A child domain
    3) One Child domain in Site B named me.abc.com and currently Exchange 2010 is running in Site B.
    I have installed Exchange 2013 in Site B in coexistence scenario now Exchange 2013 users in Site B trying to attempt connection with a public folder store in the Site A Exchange 2007 servers instead of Site B Exchange 2010 servers.
    Anyone help will be highly appreciated.
    Thanks & Regards,
    ZB

    so you want users to access the PF in site B.
    Check the setting of Databases in Exchange 2013 and find out what is default Public Folder setup for those Database. You will basically need to change the default Public Folder in Exchange 2013 from Site A PF to Site B,, the way you have explained the scenario.
    run this for Exchanger 2013 DA
    Get-mailboxDatabase -Identity Exchange2013DBNAME | fl
    Get-MailboxDatabase -Identity e15-db1 | fl *PublicFolder*
    Where Technology Meets Talent

  • EXCHANGE 2013 Public Folder Migration across Domain Forest

    Hi
    I am planning to migration public folder across the forest but unable find any documentation. can you guys share the step by step guide to move/migrate public folder. we have exchange 2013 in source and target forest.   
    Please help!

    Hi,
    Currently, there is no official document about Exchange 2013 cross-forest public folder migration. Maybe some third party software can help you to do cross forest public folder migration.
    Best regards,
    Belinda Ma
    TechNet Community Support

  • Exchange 2013 public folder showing as mail enable no, after migration

    I have migrated from 2010 to 2013 and now have a problem with some MailPublicFolders. They can receive mail, but show up in EAC as Mail Enabled "no". If I try to mail enable them they get an odd ball address i.e.
    subject?[email protected]
    I need them to show as mail enabled in EAC so I can give people SendAs etc.
    If I edit the email address, I get an error saying the address already exists.
    I think it is from 2003/2010 when alias was set to
    [email protected] and now that is not permitted.
    Thinking back to when we went from 2003 to 2010, we had to mail disable, then mail enable to get them working.
    How can I fix the properties and end up with a mail enabled mailpublicfolder?

    Hi,
    For this issue, I recommend you delete the public folder object under the Microsoft Exchange System Objects container. Before you delete the public folder object, please note the existing SMTP addresses.
    After that, please Mail-enable the
    public folder again to check result.
    Here is a similar thread for your reference.
    https://social.technet.microsoft.com/Forums/en-US/1cce206c-694b-4dc2-8052-39e988fe0dcf/public-folder-not-showing-up-as-mail-enabled-but-its-receiving-email?forum=exchange2010
    Best regards,
    If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Belinda Ma
    TechNet Community Support

  • Exchange 2013 Public Folder Error

    When I try to create a Public Folder in Exchange Admin Center for Exchange Standard 2013 I get an error that says: "The process failed to get the correct properties".   If I create the Public Folder from shell "New-PublicFolder -Name
    "Bldg 1 & 2" -Path "\Projects\10000 to 10099"", when I browse to it from Admin Center I receive the same error.
    If I try to edit the properties using Admin Center I get a popup that says "error - The process failed to get the correct properties - Click here for help..."
    I have attempted this as "administrator" with membership in the following groups:
    Schema Admins, Organization Management, Group Policy Creator Owners, Exchange Services, Exchange Domain Servers, Enterprise Admins, Domain Admins, Administrators.

    Hi,
    Did we migrate to Exchange 2013 from legacy?
    We cannot starting recreating Public Folders on Exchange Server 2013 until all users have been migrated to Exchange Server 2013. For how to migrate from legacy Public Folders to Exchange Server 2013 Public Folders, see
    Migrate Public Folders to Exchange 2013 From Previous Versions.
    Would you like to collect event logs for the further troubleshooting?
    Please contact me if there is any problem. 
    Thanks
    Mavis
    Mavis Huang
    TechNet Community Support
    Hi Mavis,
    Yes, this was an upgrade, but all previous versions of Exchange have been uninstalled.
    I'd be more then happy to send any log files in, but I'd need assistance knowing which ones you'd require.
    Thanks,
    Peter

  • Exchange 2013 Public Folder BCC Problem

    Hi ,
    I have a mail enabled public folder, it accept mail but it sends a copy of the mail in bcc to a user.
    Can someone please tell me how to remove the bcc address?
    The public folder only has one e-mail address.
    I have run the command "DeliverToMailboxAndForward" $false
    RunspaceId              : 83238470-b8c1-42ec-9228-42403e14df2d
    Timestamp               : 13.06.2014 09:11:27
    ClientIp                :
    ClientHostname          : SERVER1
    ServerIp                :
    ServerHostname          :
    SourceContext           :
    ConnectorId             :
    Source                  : AGENT
    EventId                 : AGENTINFO
    InternalMessageId       : 14710262988876
    MessageId               : <[email protected]>
    Recipients              :
    {[email protected],
    [email protected]}
    RecipientStatus         : {}
    TotalBytes              : 10226
    RecipientCount          : 2
    RelatedRecipientAddress :
    Reference               :
    MessageSubject          : Forwarding BCC Problem
    Sender                  :
    [email protected]
    ReturnPath              :
    prvs=234d3e19e=[email protected]
    Directionality          : Incoming
    TenantId                :
    OriginalClientIp        : 214.9.49.62
    MessageInfo             :
    MessageLatency          :
    MessageLatencyType      : None
    EventData               : {[CompCost, |ETR=0]}
    Somewhere there is a rule and I cannot for the life of me find it.
    I would really appreciate some help on this one.
    Thanks in advance.

    Grant yourself Owner role on the folder, and you should then be able to use Outlook to see if there are any folder rules associated with it.  Also look at your transport rules to see if there's one that's based on that recipient address.
    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Maybe you are looking for