Exchange 2013 / 2010 / 2007 - Public Folders

I have read that legacy public folders and 2013 public folders canot co-exist.
If I have legacy public folders A, B and C, does this mean...
 that if I migrate folder A to 2013, i cannot maintain a replica on legacy systems, but folders B and C are still accessible
..or..
 If I migrate folder A to 2013, I must migrate folders B and C also.
If I am need to import folder D, from an external Exchange 2013 installation, into my legacy public folder system, is it possible to migrate folder D out of the external 2130 environment into my legacy public folder environment? If so, is there any extra functionality
2013 PF has that the users will lose if the folders are down graded to legacy?
Thanks!
Tom

Hi,
User mailboxes on Exchange 2013 servers can connect to legacy public folders, but legacy Exchange mailboxes are unable to access the public folder hierarchy on Exchange 2013 server.
Exchange 2013 public folders and legacy public folders can’t exist in your Exchange organization simultaneously.
Before you migrate public folders, you need to migrate mailboxes to Exchange 2013 first.
Please refer to the following article.
http://technet.microsoft.com/en-us/library/jj150538(v=exchg.150).aspx
Besides, here is a related thread for your reference.
http://social.technet.microsoft.com/Forums/office/en-US/7603f02e-beb4-4c3d-8cb9-613ad806766b/public-folder-migration-from-multiple-exchange-2007-to-exchange-2013?forum=exchangesvrsharingcollab
Best regards,
Belinda Ma
TechNet Community Support

Similar Messages

  • How to view Exchange 2007 Public folders, calender on iphone

    How to view Exchange 2007 public folders mainly the calenders on the iphone?

    Not possible.
    Sent from my iPad.

  • 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 and 2007 coexistence and redirects

    Hi all,
    I'm settings up the coexistence but i've got a problem.
    I've got 3 sites:
    Site A: Exchange 2013 cas and mailbox
    Site B: Exchange 2007 hub/cas and mailbox
    Site C: Exchange 2007 hub/cas and mailbox
    The problem is the owa and active sync redirect. I can open a mailbox located in site B where the legacy.domain.com dns record points, but i cannot open a mailbox from the exchange 2013 nor 2007 owa from site B to C.
    I configured only the internal url leaving the external one blank.
    How do i redirect all the requests to a mailbox located in site C from site A and B?
    Thanks,
    D.

    You need to have External URL too, so that redirection can take place.
    http://blogs.technet.com/b/mbaher/archive/2009/12/17/exchange-2010-proxy-or-redirect.aspx
    http://technet.microsoft.com/en-us/library/bb310763(v=exchg.141).aspx
    http://blogs.technet.com/b/exchange/archive/2013/01/25/exchange-2013-client-access-server-role.aspx
    Cheers,
    Gulab Prasad
    Technology Consultant
    Blog:
    http://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/2010 - Co-Existence, URLs.

    Hey Team,
    I am sure this is well documented and i for some reason cant seem to get good solid answer. But here is my questions. what are the correct URL settings for (OWA, ActiveSync, EWS) etc for Exchange 2013/2010 in a coexistence scenario?
    1) All servers in the same ad site
    2) mail. autodiscover, pointed to the 2013 server
    3) 2013 server is internet connected.
    Am i supposed to clear all the 2010 URLs?, Just the external ones? Use a separate namespace?
    Thanks,
    Robert
    Robert

    This is well documented in the below post, I would recommend you check it:
    http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx
    In Exchange 2010/2013 coexistence scenario, CAS 2013 will proxy all connections to Exchange 2010.
    How CAS2013 Picks a Target Legacy Exchange Server
    It’s important to understand that when CAS2013 proxies to a legacy Exchange Client Access server, it constructs a URL based on the server FQDN, not a load balanced namespace or the InternalURL value.
    When a CAS2013 starts up, it connects to Active Directory and enumerates a topology map to understand all the Client Access servers that exist within the environment. Every 50 seconds, CAS2013 will send a lightweight request to each
    protocol end point to all the Client Access servers in the topology map; these requests have a user agent string of HttpProxy.ClientAccessServer2010Ping
    Mohammad Saeed Abdelaziz | MCSE 2003 | MCTS: Lync, OCS, Exchange2007 | CCNP | UC Voice Specialist http://lyncrocks.wordpress.com/

  • Exchange 2013 with Outlook 2010 anywhere - Public Folders disappear from Outlook favourites

    Hi,
    we have a 3 server Exchange 2013 SP1 DAG published with Forefront TMG. 
    Outlook 2010 anywhere connection works fine (only anywhere connection is possible, there are no clients in the exchange server AD).
    The users are adding public folders to their local Outlook favorites. In about 10% of the Outlook starts, those public folders are missing in the favorites. Local favorites folders are still there, public folders are connected.
    After restarting the Outlook a few times, the favorites are back. 
    Deleting the outlook.xml brought no success, the favorites seem to be saved somewhere on the exchange server.
    Outlook 2010 is up to date, all hotfixes are installed.
    There are no related entries in servers or clients eventlogs, the logs of the TMG server are normal.
    Does anyone have a simular behavior?
    Thanks in advance!

    Hi,
    According to your description,it is clear that something got corrupted, but it is hard to say directly what caused it. However, there are a few troubleshooting steps to determine what caused it and you can also make a backup of your Favorite Folders list
    so you can easily restore it when it still happens.
    Pleaser refer to the following article:
    Favorite Folders empty upon restart
    Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot
    make any representations regarding the quality, safety, or suitability of any software or information found there. Please make sure that you completely understand the risk before retrieving any suggestions from the above link.
    Hope this helps!
    Thanks.
    If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Niko Cheng
    TechNet Community Support

  • Exchange 2013 / 2010 coexistence with different public domains

    Currently in my organization
    1x Exchange 2010 Standard w/SP3 - Client Access / Hub Transport
    1x Exchange 2010 Standard w/SP3 - Unified Messaging Server (we also have Lync 2013 in the environment)
    1x Exchange 2010 Standard w/SP3 - Mailbox
    In my organization, we have approximately 600 mailboxes - 100 office staff, and 500 field employees using a mixture of Outlook 2007/2010/2013 and various mobile devices. Most of our field employees are in remote locations, several hundred
    miles away. We have no IT staff in any of our field locations.
    We also have two public domains that we use, though we are trying to phase out the old one to unify everything.
    domain-old.com - Used when the company had a different name. All Exchange services are published with this one.
    domain-new.com - Used after the company changed names. The goal is to publish all Exchange services with this one.
    domain.local - Our internal Active Directory domain.
    We use Microsoft Exchange Online Protection for all inbound/outbound email. We publish OWA, ActiveSync, etc. through our Sophos firewall. Also, we have two KEMP LoadMaster appliances that for high availability that we currently use for Lync 2013; they are
    severely underutilized.
    Goals for the Exchange migration
    My primary goal is to introduce high availability into our environment by introducing redundancy on multiple levels. I would like to accomplish this by utilizing Exchange 2013 since we will need to purchase additional licensing anyway. My idea of the
    final topology is:
    2x KEMP LoadMaster appliances providing reverse proxy and load balancing to the CAS servers
    2x Physical servers running Hyper-V, separated physically but in the same AD site. Each one would run:
    1x VM with Exchange 2013 Standard w/SP1 - Client Access
    1x VM with Exchange 2013 Enterprise w/SP1 - Mailbox - Utilizing DAGs for high-availability
    I'd like all the new Exchange services to be published under the domain-new.com domain - such as mail.domain-new.com, mail.domain-new.com/owa, smtp.domain-new.com, etc.
    We have purchased two new physical servers that will be Hyper-V hosts running Server 2012R2. My timeframe to start this project is within the next two weeks, so I'll be running the new Exchange 2013 VMs under Server 2012, not R2 as it won't be supported
    until Exchange 2013 SP3 is released.
    Deployment Plan
    Install Exchange 2013 on new VMs.
    Create CAS Array object.
    Configure Exchange 2013 to publish under the new namespace.
    Perform mailbox moves to 2013 for a small group (1-5 users) at a time. Recreate Outlook profiles and mobile device profiles for that group. Test and move to the next group.
    Once all users are moved to the new namespace, decommission the Exchange 2010 servers.
    Unknowns
    My primary unknown is about the namespaces. All of the guides I have read strictly deal with keeping the existing namespace and having the Exchange 2013 CAS proxy requests to Exchange 2010 for mailboxes still on 2010. This should never be an issue for us
    since we'll be using the new domain for each mailbox we move.
    My question boils down to, is this a supported way to migrate to Exchange 2013? And if so, are there some materials or information to help me perform it this way?

    Hi,
    From the description, you want to install Exchange 2013 in another domain and then migrate from Exchange 2010 to Exchange 2013. 
    About DAG, all servers in a DAG must be running the same operating system. If there is only one mailbox server, there is no need to deploy DAG.
    About CAS array, we should know that the CAS Array no longer exists in Exchange 2013.
    About the namespace, based on my knowledge, we can introduce a new namespace. Just as what you said "This should never be an issue for us since we'll be using the new domain for each mailbox we move".
    Here are some articles about how to upgrade from Exchange 2010 to Exchange 2013 in the same organization.
    Checklist: Upgrade from Exchange 2010
    Install Exchange 2013 in an Existing Exchange 2010 Organization
    Upgrade from Exchange 2010 to Exchange 2013
    Hope this helps.
    Best regards,
    Belinda
    Belinda Ma
    TechNet Community Support

  • Exchange 2010 SP2 Public Folders Stubborn Replicas (OAB)

    I migrated to a new server with 2010 SP3 all is working good, I am able to see all Public Folders and their contents fine. Now I need to delete this stubborn Public Folder on the older 2010 SP2 server to decommission it. But I get the dreadful 'you cannot
    delete this database because it contain replicas' blah blah. Very annoying.
    This is what the stats pulled up. They are not folders to me, and the new server is the default for OAB. Not sure what to do, I just want to delete this database the right way without resorting to ASIEDIT. I do not want to use that tool, read many horrible
    stories of people deleted the database only to have hours of after affects where other public stores went into an inconsistent state. HELP! 
    [PS] C:\Program Files\Microsoft\Exchange Server\V14\scripts>Get-PublicFolderStatistics -server server-04
    Name                                     ItemCount                                  
                        LastAccessTime
    EX:/o=LMV/ou=Exchange Administrative ... 28                                                       10/25/2014 9:20:35 PM
    EX:/o=LMV/ou=first administrative group  10                                                       10/25/2014 9:13:30
    PM
    OAB Version 2                            28                                          
                10/25/2014 9:44:33 PM
    OAB Version 4                            16                                          
                10/25/2014 9:44:33 PM

    Did you create replicas of these folders on the other server and remove the replicas from the server you want to uninstall? Have you configured the OAB so that it's generated on the new server?
    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

  • Exchange 2010 System Public Folders trying to replicate to decommissioned Exchange 2003

    I was checking the mail queue on Exchange 2010 and noticed several hundred messages in retry. Looking at the messages I found that they were all destined for an old 2003 exchange that has been decommissioned. I looked at the System Public Folders and found
    replication is set up on "events root, OWAScatchpad, SchemaRoot, and Store Events. They are set to replicate to the old mail server. When I try to remove the old server from replication it gives me an error;
    Microsoft Exchange Error
    The following error(s) occurred while saving changes:
    Set-PublicFolder
    Failed
    Error:
    You must specify a value with the Replicas parameter.
    OK
    Not sure where to go with this error.  Could someone point me in the right direction?
    Thank you,
    Wade Harris

    Hi,
    For this issue, I recommend you add an Exchange 2010 public folder database to the replica list and then remove Exchange 2003 server from this list to check result.
    I tested in my lab, and I got the same error with yours, we need to keep at least one public folder database in the replica list.
    Best regards,
    Belinda
    Belinda Ma
    TechNet Community Support

  • 2010 - 2013 Migration of Public Folders blank spaces in Public Folder names

    So I found the problem that I was running into with this thread:
    http://social.technet.microsoft.com/Forums/en-US/466106c8-33a4-4474-83eb-2f6451e0d4eb/2010-2013-public-folder-migration-failed-property-expression-isnt-valid?forum=exchangesvrdeploy , however the question I have is a bulk solution for this problem.
    The customer I am working with has just shy of 200GB of Public Folder items with many, well organized public folders that they have been using for many years. I am trying to finish up their migration to 2013 and the solution of ADSI Edit removing blank spaces
    is not going to be a good option, it would add days to the migration and many hours of labor.
    What I am looking for is to see if there is a way to remove these spaces in a bulk or automated fashion. It may be asking a lot but it will save MUCH time and effort. If there is anyone that has any ideas I would love to hear them.
    Thanks,
    Joe

    I ended up opening a support case with MS to resolve this issue. The issue took us through a few different things, on our Get-PublicFolders we had to add the -ResultSize Unlimited flag. He had a modified script that enumerated all of the special characters
    and performed a replace like the script in the prior link had performed.
    From there we also had another issue with trailing blank characters. For that we had a three step process.
    1. Get the list of Public Folders that were Mail Enabled
    2. Disable Mail for all Public Folders
    3. Enable Mail flow to the above Public Folders that had mail flow going to them.
    Finally I was able to get the public folders to migrate.

  • Outlook 2010 connecting to Exchange 2013 and 2007 ... delivery fails

    Hello,
    we are having a problem with a few Outlook 2010 Clients that have two Exchange accounts setup in one profile. One account is connecting to the company's Exchange 2013 Server, the second account is connecting to an external provider's Exchange 2007 infrastructure
    using Outlook Anywhere.
    The companies Exchange 2013 was recently migrated from Exchange 2010 and this is the point where the problem started.
    Some users are no longer able to send using the external Exchange 2007 account. When they try they are receiving an NDR with the following error message:
    #554 5.6.0 STOREDRV.Deliver; Corrupt message content##  from the external provider's servers.
    When I setup a profile containing only the external provider's mailbox everything works fine until I am adding the company's Exchange 2013 back in at which point the same error appears.
    We have no problems using the company's Exchange 2013 servers.
    Does anyone have an idea what causes this and how to resolve it? The external provider is uncooperative in troubleshooting so we are left with the problem.
    Thank you
    Sascha

    Hi,
    The problem should be related to the External Exchange 2007.
    Please refer to this kb below:
    http://support.microsoft.com/kb/2203381/en-us
    This problem occurs when the email message is a multipart/mixed MIME message which contains a text/plain body and an application/applefile body.  If the corresponding body is not a real application/applefile body, the Exchange Server 2007 server considers
    that the email message is invalid. Therefore, it generates the NDR. However, Exchange Server 2010 can deliver this kind of email message successfully.
    To resolve this problem, you should let the External Provider install the following update rollup:
    2279665 Description of Update Rollup 1 for Exchange Server 2007 Service Pack 3
    Hope this helps.
    Thanks,
    Melon Chen
    Forum Support
    Come back and mark the replies as answers if they help and unmark them if they provide no help.
    If you have any feedback on our support, please click
    here

  • My 2007 public folders are only used for Organizational Forms Library

    I have migrated all of our users from Exchange 2007 to Exchange 2013 and in order to complete the migration we need to put our Outlook Organizational Forms Library on the new server, which I understand is stored in public folders.  We do not
    need anything in our existing single public folder.  We have just one Outlook form and I can recreate it, but it won't let me create a new public folder on my new Exchange 2013 server because it says that there is an existing Public Folder deployment
    detected.  I don't really need to migrate anything, but I can't seem to go forward until the server thinks it doesn't need migration.  How do I do that?
    Sally

    Hi There,
    Please try :
    New-Mailbox "Public Folder Mailbox" -PublicFolder -HoldForMigration
    You can read more at the link below:
    https://support.microsoft.com/kb/3004062?wa=wsignin1.0
    Exchange Blog:
    www.ntweekly.com
    MCSA, MCSE, MCITP:SA, MCITP:EA, MCITP:Enterprise Messaging Administrator 2010,MCTS:Virtualization

  • Exchange Online (O365) and Exchange 2013 On-Premise, Public Folder issues?

    Hello,
    I have recently migrated from Exchange 2010 to Exchange 2013 on premise (decommissioned the old server) and migrated my public folders to the new mailbox architecture found in Exchange 2013.
    We are also hybrid setup with Office 365 and Exchange Online (AD FS and Password Sync). For our on-premise Exchange we use Split DNS.
    What I am trying to do now is give my Exchange Online users the ability to see our on-premise public folder infrastructure however I am not having any luck in getting this to work.
    On premise I have the "PublicFolderMaster" mailbox which is the Primary Public Folder Mailbox, and PublicFolderMailbox1 which is the secondary mailbox (where all the public folder data is).
    How do I configure my Exchange Online to allow the users to see on-premise public folders? I tried..
    Set-OrganizationConfig -PublicFoldersEnabled Remote -RemotePublicFolderMailboxes PublicFolderMaster,PublicFolderMailbox1
    In my O365 user's Outlook I see Public Folders, but when I try to expand it I get an error saying unavailable...
    What am I doing wrong?

    Or must I follow all these steps in addition to the last step above?
    http://technet.microsoft.com/en-us/library/dn249373(v=exchg.150).aspx

  • Exchange 2013 - where are public contacts supposed to go?

    This may seem like a stupid question but it has me stumped
    We have migrated from exchange 2007 to exchange 2013. We have users using outlook 2013 and some who just want to use OWA and some who want to use both.
    We have imported our public folder global contacts into a public folder in the public folder database and the outlook users have added this as an address book.
    HOWEVER - the owa users cannot see it, they can only see the GAL
    If we add users to GAL, the outlook users can send emails to people listed in GAL in the drop down in the email to:, but I can see no way in which outlook users can manage contacts (review /add) in GAL
    So the question is - What are we supposed to be doing? What is the recommended way to manage external global contacts (such as our customers) in Exchange 2013 system so that both owa and outlook people can access them?

    Hi Helen,
    According to your description, I know that you have some confusions on this behavior.
    First, please make sure the migration completed successfully.
    Then, please check whether there is any error message poping-up when cannot see the contacts in the public folder via OWA. Some like,
    This version of Outlook Web Access only supports your primary contact folder.
    or
    Public Contact folders are not supported by Outlook Web Access.  
    If it is the case, the reason should be the OWA only allows access to contacts that are contained in the primary contact folder in your mailbox. Public contacts are not available. Custom contact folders and subfolders are also not available.
    However, it has a workaround. You can use an Outlook client to access public contacts, or custom contact folders.
    Last, about "but I can see no way in which outlook users can manage contacts (review /add) in GAL", based on my experience, we cannot manage contacts in GAL on Outlook directly. I suggest manage it in AD as Administrator.
    Please correct me if there is any misunderstanding.
    Thanks
    Mavis
    If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Mavis Huang
    TechNet Community Support

  • Exchange 2013 - Outlook 2007 - Server name GUID

    Hi Guys.
    I am hoping someone can shine some light on something for me.
    Right now I have the following with roles.
    1 x Exchange 2010 - MBX & CAS
    1x Exchange 2013 - MBX
    1 x Exchange 2013 - CAS
    Mix of Outlook 2007 & 2010
    I migrated a user from Exchange 2010 over to Exchange 2013 and the process went fine. Email flow is working, OWA and Active Sync again working ok.
    However when we opened Outlook 2007 it displayed a message to say an Administrator had made changes and we needed to restart Outlook. No issues there.
    Outlook connected up fine and everything works. However when you look in the mail profile for the Exchange server name i see something like
    [email protected]
    Also Outlook Anywhere is ticked and when you untick it from the client and then open it again it comes back.
    Are the above items of migration?

    Hi,
    RPC is no longer a supported direct access protocol. This means that all Outlook connectivity must take place using RPC over HTTP (also known as Outlook Anywhere).
    Outlook clients no longer connect to a server FQDN as they have done in all previous versions of Exchange. Outlook uses Autodiscover to create a new connection point comprised of mailbox GUID, @ symbol, and the domain portion of the user’s primary SMTP
    address.
    To expand on this a little bit, I worked an issue with a new Exchange 2013 environment for 3 days before figuring out that you do NOT specify a server name where it asks for it in Outlook, you use the format mentioned above.  
    For reference, I received a very particular error from testconnectivity.microsoft.com that made no sense until I discovered the server name format.  If a test fails with a 404 HTTP Not Found error and an X-CasErrorCode of MailboxGuidWithDomainNotFound,
    this is most likely your problem.  Its very frustrating that Microsoft does not have it documented anywhere exactly what this error means, would have saved me a lot of time and energy.

Maybe you are looking for