This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(25.6, 66%, 12%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDB%3C/text%3E%3C/svg%3E)
During migration from exchange 2013 last CU. (I know, I know I'm trying to hurry) to EO, I need to run Sync-ModernMailPublicFolders.ps1 to support PFs temporarily as I migrate the remaining mailboxes. The script requires I run it in exchange management shell on the server itself. It also appears this should just work out of the box, but it doesn't.
Checking for mail-enabled System folders...
Getting all public folders. This might take a while...
Found 18 public folders.
17 of those are mail-enabled.
0 folders are mail-enabled with no AD object.
17 folders are mail-enabled and are properly linked to an existing AD object.
No folders need to be mail-disabled.
No orphaned MailPublicFolders were found.
No duplicate MailPublicFolders were found.
No mail-disabled public folders with proxy GUIDs were found.
No disconnected MailPublicFolders were found.
Done!
I get this error with a typo (authenticaion).
WARNING: [5/10/2023 7:21:12 AM] This script uses modern authenticaion to connect to Exchange Online and requires EXO V2 module to be installed. Please follow the instructions at
https://docs.microsoft.com/powershell/exchange/exchange-online-powershell-v2?view=exchange-ps#install-the-exo-v2-module to install EXO V2 module.
This url conflicts with other information microsoft provides about which module can be installed with which PSVersion:
"All versions of the module are supported in Windows PowerShell 5.1."
ExchangeOnlineManagement 3.1.0 Minimum PowerShell version 3.0
$psversiontable
Name Value
PSVersion 4.0
WSManStackVersion 3.0
SerializationVersion 1.1.0.1
CLRVersion 4.0.30319.42000
BuildVersion 6.3.9600.20713
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0}
PSRemotingProtocolVersion 2.2
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(284.8, 17%, 37%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EYS%3C/text%3E%3C/svg%3E)
Hi @Dee Bukkus ，
Just circling back to follow up with this thread. If the information provided was helpful, do you mind accepting it as answer for others' referencing? If you still have any further questions or concerns, feel free to post back.
Just wanted to check if the answer shared below helped. If it helped, then would request you to please "Accept the answer" as it would be helpful to others in the community as well.
Hi @Dee Bukkus ，
Is safe to install or upgrade exchange online powershell v2 or higher on exchange 2013 server itself to run Sync-ModernMailPublicFolders.ps1?
Yes, you can go ahead.
I haven't seen that it will do any harm to install or upgrade Exchange Online PowerShell module on Exchange server 2013. And you can always choose to uninstall the module if necessary. See About the Exchange Online PowerShell module.
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.