Update 10/1/2023: As per the below Timeline of RPS deprecation, we have now entered the stage where all tenants in our WW cloud have RPS disabled by default and cannot re-enable it. All tenants from ...
Updated Nov 09, 2023
Version 13.0
Blog Post
4 MIN READ
Deprecation of Remote PowerShell in Exchange Online – Re-enabling or Extending RPS support
Hello Bhalchandra_Atre-MSFT ,
The prob now is that we've to use EXO V3, which requires PowerShell 5. But it's not supported to upgrade PowerShell on an Exchange Server 2013. Exchange server 2013 has been designed to work with PowerShell 4. I've already tried in the past to upgrade PowerShell to the v5 version and it broke my Exchange, so I needed to rollback. at that time, I've opened a ticket to the support team and they told me to not do that.
Regarding that website, PowerShell 5 is still not compatible with Exchange server 2013 : https://learn.microsoft.com/en-us/powershell/scripting/windows-powershell/wmf/whats-new/compatibility?view=powershell-7.3
but I've found a workaround. Here is what I've done :
- Created a new Windows server 2012 R2 with the installation of powershell 5, dotnet framework 4.8 and all updates
- installation of EXO V3 3.3.0
- Installation of Exchange 2013 management console
- modification of the script Sync-ModernMailPublicFolders.ps1 to put in comment the Exchange server check (from line 659 to 665)
and now I can sync it again
Regards