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

Similar Messages

  • 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 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 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 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 2010 to 2013 Public Folder Migration -- Token Serialization

    Here is the log entry,Failed to save admin audit log for this cmdlet invocation. Organization: First Organization Log content:Cmdlet Name: New-PublicFolderMigrationRequestObject Modified: f0daff33-6a93-4367-b609-662cfa0b92de\71fc0595-b5d7-4f15-8b7c-bffcefbd810fParameter: SourceDatabase = Public Folder Database Parameter: CSVData = VGFyZ2V0TWFpbGJveCxGb2xkZXJQYXRoDQpDb2JvY28gUEYsXA0KQ29ib2NvIFBGLFxJUE1fU1VCVFJFRVxBcg==...Caller: ExternalAccess: FalseSucceeded: TrueRun Date: 2015-07-07T12:41:45OriginatingServer: (15.00.0995.012)Error:Microsoft.Exchange.Data.ApplicationLogic.AuditLogAccessDeniedException: The requesting account doesn't have permission to access the audit log. --- System.Web.Services.Protocols.SoapException: The requesting account does not have permission to serialize tokens. at...

    Hey Guys!
    I'm in the process of testing a Public Folder migration from Exchange 2010 to 2013, I've been following the recommened migration scenario from Microsoft but have ran into this issue when running New-PublicFolderMigrationRequest. I let the request sit at a queued status for over 6 hours and then decided to look at the event logs. I'm receiving an access denied, requesting account does not have permission to serialize tokens.
    Luckily this is just a test and not in a production environment :-)
    Any suggestion or help to point me in the right direction would be appreciated
    Thanks Guys
    This topic first appeared in the Spiceworks Community

  • Exchange 2010 - 2013 Public Folder Migration target database gets much bigger than source database

    Hi,
    i have a question about the pf migration from Exchange 2010 to Exchange 2013. The source database ist about 370 GB. The migration process is still running. At the moment the target database is already 491GB big. Is that a normal behaviour during the migration
    process.
    Thanks

    Hi,
    After you have finished the public folder migration process, you can compare the item count of public folders to make sure all public folders have been moved to Exchange 2013.
    You can check this by comparing the snapshots before and after the migration. You can refer to the "How do I know this worked?" section in the following article.
    Migrate Public Folders to Exchange 2013 From Previous Versions
    http://technet.microsoft.com/en-us/library/jj150486(v=exchg.150).aspx
    Best regards,
    Belinda
    Belinda Ma
    TechNet Community Support

  • 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 Contact Public Folder Migration Question

    I am migrating our Exchange 2010 environment to Exchange 2013.  We are migrating all of our public folders into SharePoint before we continue with the migration.  Most of our public folders are calendars, so it has been a pretty cut and dry migration.
     We do have one public folder that is designated for emergency contacts.  It contains the personal contact information for the CEO as well as other high up execs and managers from around the company.
    Here is my dilemma.  I need to migrate this out of public folders, but it still needs to remain in Exchange somewhere.  I need to accomplish the following
    1. Be able to view all user contact info, not just email address
    2. Be able to apply permissions to the folder so that only certain individuals can gain access to these contacts
    3. Be available to sync with said user's mobile devices, so that they have 24X7 access to that information
    I am not real sure how to accomplish this and am open to any ideas.  I am very new to SharePoint, so not sure how you might be able to leverage SharePoint to do the same thing.  Any information that anybody could provide would be greatly appreciated.
    Thank you in advance,
    --Scott

    Hi Scott,
    Since this is Exchange Server Forum, if you have any problem on SharePoint, I suggest ask SharePoint Forum for help so that you can get more professional suggestions. For your convenience:
    https://social.technet.microsoft.com/Forums/office/en-US/home?category=sharepoint
    Here is some information related to Exchange for your reference.
    Based on my knowledge, Exchange 2013 is different from previous version of Exchange server. For example, public folder. Public folder in Exchange 2013 doesn’t based on public folder database, it is a mailbox level, called public folder mailbox.
    We can follow following article to perform the public folder migration.
    Use serial migration to migrate public folders to Exchange 2013 from previous versions
    https://technet.microsoft.com/en-us/library/jj150486%28v=exchg.150%29.aspx?f=255&MSPPError=-2147217396
    Thanks
    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]
    Mavis Huang
    TechNet Community Support

  • 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

  • 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

  • 2010 to 2013 Public Folder Migration - PF work in OWA but not outlook Client, password prompt?

    Hello All,
    I have migrated all public folders from Exchange 2010 Sp3 to Exchange 2013 Cu7. You can access the public folders without any problems in OWA.
    When trying to access in outlook i will get a password/username prompt. If i enter my details in this it will keep popping up even with the remember me button ticked.
    When i check the connection status i see the below the status which is "connecting" is the PF; it will never connect.
    I have done:
    Reboots
    Restart the Microsoft Exchange RPC Client Access service on the Exchange 2013 server
    Tried changing the Logon network security in the outlook client which made no difference:
    Tried logging into the outlook client as different user which made no difference
    What else can i do please?
    Help Appreciated!

    Hi,
    Please check if you have NTLM configured for Outlook Anywhere on your Exchange 2010.
    Get-OutlookAnywhere | fl Identity,*auth*
    And please check the server the public folder is trying to connect.
    Best regards,
    Belinda Ma
    TechNet Community Support

  • 2010 - 2013 Public Folder migration failed - Property Expression isn't valid

    We just migrated from 2003 to 2010, and now on to 2013.  I have Exchange 2013 CU3 installed, and all mailboxes moved.  When trying to move the public folders, I'm getting an error about DataValidationException.  Property expression <PF
    Name with spaces> isn't valid......
    Many articles refer to a mail-enabled public folder with spaces can't have spaces in the alias.  This is NOT a mail-enabled public folder, so there isn't an alias that I can find.
    Any ideas?
    Thanks!
    --Kent

    I believe aliases are only available in mail-enabled public folders.  
    Here is the exact message:
    RunspaceId                       : 7fdb2174-e04a-4950-be57-6c0e77c4c02b
    Name                             : PublicFolderMigration
    Status                           : Failed
    StatusDetail                     : FailedOther
    SyncStage                        : CreatingFolderHierarchy
    Flags                            : IntraOrg, Pull, Suspend, SuspendWhenReadyToComplete
    RequestStyle                     : IntraOrg
    Direction                        : Pull
    Protect                          : False
    Priority                         : Normal
    Suspend                          : True
    SourceVersion                    : Version 14.3 (Build 123.0)
    SourceDatabase                   : Public Folder Database 0592897580
    SourceServer                     : MYEXCHTEMP.mydomain.local
    BatchName                        : 
    OutlookAnywhereHostName          : 
    RemoteCredentialUsername         : 
    AuthenticationMethod             : Basic
    RemoteMailboxLegacyDN            : 
    RemoteMailboxServerLegacyDN      : 
    BadItemLimit                     : 0
    BadItemsEncountered              : 0
    LargeItemLimit                   : 0
    LargeItemsEncountered            : 0
    FolderToMailboxMap               : {\}
    QueuedTimestamp                  : 1/20/2014 8:36:49 PM
    StartTimestamp                   : 1/20/2014 8:36:56 PM
    LastUpdateTimestamp              : 1/20/2014 8:36:59 PM
    InitialSeedingCompletedTimestamp : 
    FinalSyncTimestamp               : 
    CompletionTimestamp              : 
    SuspendedTimestamp               : 
    OverallDuration                  : 1.11:22:26
    TotalFinalizationDuration        : 
    TotalDataReplicationWaitDuration : 
    TotalSuspendedDuration           : 
    TotalFailedDuration              : 1.11:22:16
    TotalQueuedDuration              : 00:00:04
    TotalInProgressDuration          : 00:00:05
    TotalStalledDueToCIDuration      : 
    TotalStalledDueToHADuration      : 
    TotalStalledDueToReadThrottle    : 
    TotalStalledDueToWriteThrottle   : 
    TotalStalledDueToReadCpu         : 
    TotalStalledDueToWriteCpu        : 
    TotalStalledDueToReadUnknown     : 
    TotalStalledDueToWriteUnknown    : 
    TotalTransientFailureDuration    : 
    TotalIdleDuration                : 00:00:01
    MRSServerName                    : 
    EstimatedTransferSize            : 0 B (0 bytes)
    EstimatedTransferItemCount       : 0
    BytesTransferred                 : 0 B (0 bytes)
    BytesTransferredPerMinute        : 
    ItemsTransferred                 : 0
    PercentComplete                  : 10
    PositionInQueue                  : 
    PreventCompletion                : True
    FailureCode                      : -2146233088
    FailureType                      : DataValidationException
    FailureSide                      : Target
    Message                          : Error: Property expression "my Office Schedule" isn't valid. Valid values are: 
                                       Strings formed with characters from A to Z (uppercase or lowercase), digits from 0 
                                       to 9, !, #, $, %, &, ', *, +, -, /, =, ?, ^, _, `, {, |, } or ~. One or more 
                                       periods may be embedded in an alias, but each period should be preceded and 
                                       followed by at least one of the other characters. Unicode characters from U+00A1 to 
                                       U+00FF are also valid in an alias, but they will be mapped to a best-fit US-ASCII 
                                       string in the e-mail address, which is generated from such an alias.
    FailureTimestamp                 : 1/20/2014 8:36:59 PM
    IsValid                          : True
    ValidationMessage                : 
    OrganizationId                   : 
    RequestGuid                      : 447ed7f5-3e13-4e3c-8654-c202ba040030
    RequestQueue                     : Mailbox Database 1159688983
    ExchangeGuid                     : b62af075-26c1-4636-8273-8aa94ec4725f
    Identity                         : 2616f69b-d3b3-48d5-85fc-25cf0cea9860\447ed7f5-3e13-4e3c-8654-c202ba040030
    DiagnosticInfo                   : 
    Report                           : 1/20/2014 8:36:49 PM [myexch01] 'mydomain.local/my/Administrators/Kent Iler' 
                                       created request.
                                       1/20/2014 8:36:54 PM [myexch01] The Microsoft Exchange Mailbox Replication service 
                                       'myexch01.mydomain.local' (15.0.775.35 caps:3F) is examining the request.
                                       1/20/2014 8:36:55 PM [myexch01] Connected to target mailbox 
                                       'b62af075-26c1-4636-8273-8aa94ec4725f', database 'Mailbox Database 1159688983', 
                                       Mailbox server 'myEXCH01.mydomain.local' Version 15.0 (Build 775.0), proxy 
                                       server 'myexch01.mydomain.local' 15.0.775.35 caps:07FFCB07FFFF.
                                       1/20/2014 8:36:55 PM [myexch01] Connected to source mailbox '', database 'Public 
                                       Folder Database 0592897580', Mailbox server 'myEXCHTEMP.mydomain.local' Version 
                                       14.3 (Build 123.0).
                                       1/20/2014 8:36:55 PM [myexch01] Request processing started.
                                       1/20/2014 8:36:57 PM [myexch01] Stage: CreatingFolderHierarchy. Percent complete: 
                                       10.
                                       1/20/2014 8:36:57 PM [myexch01] Initializing folder hierarchy from mailbox '': 33 
                                       folders total.
                                       1/20/2014 8:36:57 PM [myexch01] Folder creation progress: 0 folders created in 
                                       mailbox 'b62af075-26c1-4636-8273-8aa94ec4725f'.
                                       1/20/2014 8:36:59 PM [myexch01] Fatal error DataValidationException has occurred.
    ObjectState                      : New

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

Maybe you are looking for