Share via

public folder migration

dirkdigs 921 Reputation points
2022-01-25T17:55:49.743+00:00

Hello,

I am performing a Public Folder Migration from my Exchange 2019 server to O365.

I am going through this article to meet all my prerequisites.

But I am stuck at adding a new accepted domain (Step 2).
Why is this article asking to create a new accepted domain with this particular name?

If the accepted domain already exists in your on-premises environment, rename it to PublicFolderDestination_78c0b207_5ad2_4fee_8cb9_f373175b3f99 and leave the other attributes intact.

https://learn.microsoft.com/en-us/Exchange/collaboration/public-folders/migrate-to-exchange-online?view=exchserver-2019#prerequisite-steps-in-the-on-premises-exchange-2013-exchange-2016-or-exchange-2019-server-environment

I already have domain.mail.onmicrosoft.com added as my accepted domain, still asking to change the name??
168419-image.png

Any ideas if you have performed the migration and noticed this part????

Thanks in advance!!

Exchange Server Management
Exchange Server Management
Exchange Server: A family of Microsoft client/server messaging and collaboration software.Management: The act or process of organizing, handling, directing or controlling something.
7,504 questions
Microsoft Exchange Hybrid Management
Microsoft Exchange Hybrid Management
Microsoft Exchange: Microsoft messaging and collaboration software.Hybrid Management: Organizing, handling, directing or controlling hybrid deployments.
1,999 questions

3 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Andy David - MVP 145.6K Reputation points MVP
    2022-01-25T18:02:23.073+00:00

    Hey Jason, if it already exists then follow. All you are doing here is changing the name, not the domain name itself.

    If the accepted domain already exists in your on-premises environment, rename it to PublicFolderDestination_78c0b207_5ad2_4fee_8cb9_f373175b3f99 and leave the other attributes intact. 

    Get-AcceptedDomain | Where {$_.DomainName -eq "<target domain>"} | Set-AcceptedDomain -Name PublicFolderDestination_78c0b207_5ad2_4fee_8cb9_f373175b3f99
    0 comments
  2. dirkdigs 921 Reputation points
    2022-01-25T18:08:05.493+00:00

    ok this will not break any mail flow or existing PF access?

    "I am dealing with a very sensitive client here" :)

    Also I see the article makes reference to creating internal relay type connector. Mine appears to be authoritative. Does this matter?

  3. Warren Calvert 11 Reputation points
    2022-02-14T14:02:46.29+00:00

    I'm also confused by this step.

    The primary step is to create a new accepted domain of '*.mail.onmicrosoft.com' and only rename if the domain already exists.
    This domain is created by default in a hybrid environment so I cant see how it could ever not exist. So why do Microsoft say try to create it first?

    Also, if it didnt exist and we did create a new domain, this new domain would only be present in Exch on-prem and wouldnt exist in EXO. If this domain is for routing purposes to EXO I dont understand how creating a new domain would work? Nowhere does it say the domain must be added to O365 and to the hybrid config.

    Can anyone clarify this?

    I'm also concerned about renaming the primary domain in Exch on-prem and changing from Authoritive to Internal Relay
    Any thoughts?