Forum Discussion
Raphael_Veauvy
Nov 25, 2022Copper Contributor
Script execution problem for migration of exchange 2016 public folders to office365
Hello, We have started a migration from exchange 2016 to office365. for user mailboxes, everything went well For the migration of public folders, I ran the script "Export-ModernPublicFolderStatist...
- Nov 26, 2022
Raphael_Veauvy I was hoping to go through this article yesterday and move our Exchange 2013 on-premises Public Folders to Exchange Online. Unfortunately I came across the same issue which is item 1 under Step 3: Generate the .csv files. I did successfully run the script back in June this year but never did finish this migration.
The article mentions:
To run the migration scripts in this article, you must use an account that has basic authentication enabled. Accounts that use multi-factor authentication (MFA) are currently not supported.
Here is a link but it pertains to Exchange Online and we're running the script against our on-premises server but I'm wondering if it will impact any of the other scripts?
Thanks
* Update - I ran Powershell as an admin on my Exchange 2013 server, ran this command Add-PSSnapin Microsoft.Exchange.Management.PowerShell.SnapIn and was able to run the script without error. I was using Exchange Powershell and it wasn't working.
Cabarrus300
Nov 26, 2022Copper Contributor
Raphael_Veauvy I was hoping to go through this article yesterday and move our Exchange 2013 on-premises Public Folders to Exchange Online. Unfortunately I came across the same issue which is item 1 under Step 3: Generate the .csv files. I did successfully run the script back in June this year but never did finish this migration.
The article mentions:
To run the migration scripts in this article, you must use an account that has basic authentication enabled. Accounts that use multi-factor authentication (MFA) are currently not supported.
Here is a link but it pertains to Exchange Online and we're running the script against our on-premises server but I'm wondering if it will impact any of the other scripts?
Thanks
* Update - I ran Powershell as an admin on my Exchange 2013 server, ran this command Add-PSSnapin Microsoft.Exchange.Management.PowerShell.SnapIn and was able to run the script without error. I was using Exchange Powershell and it wasn't working.
Raphael_Veauvy
Nov 27, 2022Copper Contributor
Hi, you are great.
I opened a new windows powershell console as administrator, run the line "Add-PSSnapin Microsoft.Exchange.Management.PowerShell.SnapIn"
then, I executed the script without error (I got the CSV file correctly)
the script ran correctly...
I tried to run the script again in a new powershell exchange window : same error
I compared the 2 versions of powershell (Windows and Exchange) on the same server (Exchange 2016):
WINDOWS:
Name Value
---- -----
PSVersion 5.1.14393.5127
PSEdition Desktop
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
BuildVersion 10.0.14393.5127
CLRVersion 4.0.30319.42000
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
EXCHANGE:
Name Value
---- -----
PSVersion 5.1.14393.5127
PSEdition Desktop
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0, 5.0, 5.1.14393.5127}
BuildVersion 10.0.14393.5127
CLRVersion 4.0.30319.42000
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
It's OK for me, I can continue my migration
Thank you very much for this tip.