Public Folder Exchange 2010 to Exchange 2013 Migration

hi guys
i have Exchagne 2010 SP3 and Exchange 2013 CU2 , i have moved all my mailboxes to Exchange2013 , before that i created Exchnage2013 Address Book ( web base ) for OAB . i have Public folder Database( used for Default Address book ) -Free/Busy on exchnage
2010 . now i don't need PF at all on Exchange 2013, So can i just Delete Public Folders from Exchange 2010 without Moving Public Folder ( free/Busyy , etcc... ) to Exchange 2013. from exchange 2007 to exchange , we did create Public folder
on Exchnage 2010 , Add replica , waited for sync, moved OAB generated Server as Exchnage 2010.
as i see from deploymetn guild, there are few steps need to be done to move PF to excahnge 2013, but since i don't need PF, can i just delete it.
Indunil

Hi
I m migrating public folder 2010 to 2013
When i do :
Get-PublicFolderMigrationRequest | Get-PublicFolderMigrationRequestStatistics -IncludeReport | Format-List
I have a lot of line like this
00-00-00-00-1A-44-73-90-AA-66-11-CD-9B-C8-00-AA-00-2F-C4-5A-03-00-36-B9-C6-5D-38-99-D6-11-9B-D6-00-08-02-55-A6-70-00-00-00-18-33-94-00-00 ». Ce dossier peut être
lié manuellement en exécutant la cmdlet Enable-MailPublicFolder une fois la migration terminée.
23/05/2014 19:18:02 [serveur] Avertissement : échec de recherche ou de liaison de l'objet destinataire « 96-7D-85-6C-DC-A6-83-42-AC-77-A4-5E-BD-CD-52-9B » dans
Active Directory pour le dossier public à extension messagerie « Public Root/IPM_SUBTREE/Secrétariat RC/PAYS/VENEZUELA/2006/SINCOR » avec l'ID d'entrée «
00-00-00-00-1A-44-73-90-AA-66-11-CD-9B-C8-00-AA-00-2F-C4-5A-03-00-36-B9-C6-5D-38-99-D6-11-9B-D6-00-08-02-55-A6-70-00-00-00-13-4D-8A-00-00 ». Ce dossier peut être
lié manuellement en exécutant la cmdlet Enable-MailPublicFolder une fois la migration terminée.
it scared me, what does it means ? Do i do something wrong?
I have let it work
And when i check status i have this :
Statut: Failed
Détails status : Failed other
Syncstages : Copying message
Estimed transfert size : 0
Pourcentcomplete : 95
What do i do? Can You help me? I m a little scared right now
Thanks

Similar Messages

Exchange 2013 migration, disable SSLOffloading on 2010 CAS servers

We just going through the Exchange 2013 migration from Exchange 2010. I have one or two questions when following the Exchange deployment Assistant. We have HLB where the certificates and we enable SSLoffload on the CAS server. So we don't have public CA's
on our CAS 2010 servers.
So on the documentation it says to run this command, were it will disable SSLOffloading and change to Basic authentication. Will my running outlook 2010 clients start getting certificate errors and will they work as normal ?
Get-ExchangeServer | Where {($_.AdminDisplayVersion -Like "Version 14*") -And ($_.ServerRole -Like "*ClientAccess*")} | Get-ClientAccessServer | Where {$_.OutlookAnywhereEnabled -Eq $False} | Enable-OutlookAnywhere -ClientAuthenticationMethod
Basic -SSLOffloading $False -ExternalHostName $Exchange2013HostName -IISAuthenticationMethods NTLM, Basic

We have OA enabled on all CAS 2010 servers with NTLM authentication and SSLoffloading box checked. We have also setup our CAS2013 and is running. My question above was that if I ran that command, Will I break anything since all my users
are still on Exchange 2010 mailboxes.
Then as I mentioned, that command will do nothing as OA is already enabled on CAS 10. It would only make a change if CAS10 had OA disabled.
Where {$_.OutlookAnywhereEnabled -Eq $False}
Where {$_.OutlookAnywhereEnabled -Eq $False}
Cheers,
Rhoderick
Microsoft Senior Exchange PFE
Blog:
http://blogs.technet.com/rmilne
Twitter:   LinkedIn:
  Facebook:
  XING:
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 2010 to Exchange 2013 Migration and Architect a resilient and high availability exchange setup

Hi,
I currently have a single Exchange 2010 Server that has all the roles supporting about 500 users. I plan to upgrade to 2013 and move to a four server HA Exchange setup (a CAS array with 2 Server as CAS servers and one DAG with 2 mailbox Servers). My
goal is to plan out the transition in steps with no downtime. Email is most critical with my company.
Exchange 2010 is running SP3 on a Windows Server 2010 and a Separate Server as archive. In the new setup, rather than having a separate server for archiving, I am just going to put that on a separate partition.
Here is what I have planned so far.
1. Build out four Servers. 2 CAS and 2 Mailbox Servers. Mailbox Servers have 4 partitions each. One for OS. Second for DB. Third for Logs and Fourth for Archives.
2. Prepare AD for exchange 2013.
3. Install Exchange roles. CAS on two servers and mailbox on 2 servers. Add a DAG. Someone had suggested to me to use an odd number so 3 or 5. Is that a requirement?
4. I am using a third party load balancer for CAS array instead of NLB so I will be setting up that.
5. Do post install to ready up the new CAS. While doing this, can i use the same parameters as assigned on exchange 2010 like can i use the webmail URL for outlook anywhere, OAB etc.
6. Once this is done. I plan to move a few mailboxes as test to the new mailbox servers or DAG.
7. Testing outlook setups on new servers. inbound and outbound email tests.
once this is done, I can migrate over and point all my MX records to the new servers.
Please let me know your thoughts and what am I missing. I like to solidify a flowchart of all steps that I need to do before I start the migration.
thank you for your help in advance

Hi,
okay, you can use 4 virtual servers. But there is no need to deploy dedicated server roles (CAS + MBX). It is better to deploy multi-role Exchange servers, also virtual! You could install 2 multi-role servers and if the company growths, install another multi-role,
and so on. It's much more simpler, better and less expensive.
CAS-Array is only an Active Directory object, nothing more. The load balancer controls the sessions on which CAS the user will terminate. You can read more at
http://blogs.technet.com/b/exchange/archive/2014/03/05/load-balancing-in-exchange-2013.aspx Also there is no session affinity required.
First, build the complete Exchange 2013 architecture. High availability for your data is a DAG and for your CAS you use a load balancer.
On channel 9 there is many stuff from MEC:
http://channel9.msdn.com/search?term=exchange+2013
Migration:
http://geekswithblogs.net/marcde/archive/2013/08/02/migrating-from-microsoft-exchange-2010-to-exchange-2013.aspx
Additional informations:
http://exchangeserverpro.com/upgrading-to-exchange-server-2013/
Hope this helps :-)

Public Folder Exchange 2010

Good Day ,
I did migration from exchange 2003 to exchange 2010 for mailbox but not yet for public folder , in my situation i have just 3 folders in public folder , my idea is I creat new public folder in exchange 2010 and I copy in the path this three folders
and iI gave autorisation it's possible ?
Regards
e

You can take a look into below mentioned few good resources that clarifies your concern in depth. It will assist you to move public folders between two exchange server : http://blogs.technet.com/b/agobbi/archive/2010/08/04/how-to-move-public-folder-from-exchange-2003-to-exchagne-2010.aspx
http://exchangeservermigration.blogspot.in/2013/06/how-to-perform-migration-in-exchange.html
http://www.petenetlive.com/KB/Article/0000426.htm

Exchange 2013 Migration from 2010 Test (Shared split DNS)

Hi
Im testing a migration from Exchange 2010 to 2013. I have tried to run a single DNS name to both servers, so externally mail.test.com resolves to the external IP and that NAT's to the new Exchange 2013. Then internally mail.test.com resolves both to EXC13
and EXC10 ip adresses (Round Robin).
I have moved some mailboxes to 2013. If the IP resolves to the new Exchange and i try to login to a mailbox on the old server i get redirected as im supposed to. If the IP resolves to the old Exchange and i try to login with a mailbox on the new server i
get:
A server configuration change is temporarily preventing access to your account. Please close all Web browser windows and try again in a few minutes. If the problem continues, contact your helpdesk.
Should this be possible, or do i need to change the intarnal URL on all virtual directories on the old server to the local netbios name or what to do?

You should never use the server name in any of the URLs. You should use either a CNAME or a load-balanced VIP with a generic name like mail.company.com or webmail.company.com. Then you just point this name to the new server. If
you're currently using a server name, it's about time to change that first before trying to switch to Exchange 2013.
Curently im using a generic name, mail.test.com. But that's just a normal A record on the internal DNS. So i cannot use that on both?

Journaling mailbox - Exchange 2013 Migrations from 2010

hi guys
i am about to start mailbox movement from Exchange 2010 to 2013. my setup is working fine. i have enabled journaling from Exchange 2010 and as ii found, automatically journaling rules will be reflected to exchange 2013. i had very big journaling mailbox
and then newly created New Exchange 2010 journaling mailbox. now new journaling mailbox is configured for journaling and that also still on 2010(both Old and new journaling mailbox ), new mailx is couple of weeks old (6-8 GB) and old one is 2.6 TB. So i will
move old one at the end .
my questions is if i move new journaling mailbox to 2013 before start normal Mailboxes, it will cause some issues for journaling. i use premium journaling . is it okay to move journaling mailbox at the begin ??
thank you
Indunil

Hi,
Based on my test, journal rules will be synchronized in Exchange 2013 after you create in Exchange 2010. If you create in Exchange 2013, then the rule will be synchronized in Exchange 2010.
And I did create a rule to send message to a Exchange 2013 jounal mailbox for Exchange 2010 users. It worked.
So you can migrate journal mailbox to Exchange 2013 firstly based on this test.
Best regards,
Belinda Ma
TechNet Community Support

Unable to delete the meeting invitation from Calendar stored in Public Folder - exchange 2010

I assume the specific entry (meeting invitation) is corrupted, due to which we are unable to delete the meeting either from outlook or OWA. Is there any possibility to delete that calender invitation from reoccuring?

Hi,
For further troubleshooting, I would like to collect some information
Is there any error when trying to delete the meeting invitation from calendar?
If the calendar is not stored in the public folder, is it possible to delete the meeting in this calendar?
Does this issue occur on one user or multi-users?
Cancel all meetings in a recurring series
https://support.office.com/en-za/article/Cancel-all-meetings-in-a-recurring-series-f19821e2-a05b-4f20-b0b8-d69b5a135564
Please also refer to
KB 2771436
Thanks.

Cross-forest access to public folders Exchange 2013-2007

Dear.
We have an Exchange 2007 org in one forest and an Exchange 2013 org in another forest.
User accounts remain in the 2007 AD, mailbox moved to Exchange 2013 in the other forest, so a linked mailbox.
What do I need to do in the Exchange 2007 public folders to give the migrated mailboxes (not migrated users) access to these public folders?
Thanks for the support.
Regards.
Peter Van Keymeulen, IT Infrastructure Solution Architect, www.edeconsulting.be

Hi Stephen,<o:p></o:p>
<o:p> </o:p>
Do you have trust between Exchange 2007 forest and Exchange 2013 forest? Please set up a trust between the two forests. Then set the public folder client permission
to see if we can access the
public folders.<o:p></o:p>
<o:p> </o:p>
If not, since Public folder cross forest migration is not supported in from an Exchange 2007/2010 forest to an exchange 2013 forest, refer to forum:
http://social.technet.microsoft.com/Forums/office/en-US/51da1b97-fbb1-4f81-87da-c3370960c4ab/crossforest-public-folder-migration?forum=exchangesvrdeploy
http://social.technet.microsoft.com/Forums/office/en-US/663f0dc3-a977-408a-93c7-94584fbefc62/public-folder-issue-cross-forest-migration-exchange-2010-to-2013?forum=exchangesvrdeploy
<o:p></o:p>
Title: Migrate Public Folders to Exchange 2013 From Previous Versions<o:p></o:p>
Link:
http://technet.microsoft.com/en-us/library/jj150486(v=exchg.150).aspx<o:p></o:p>
<o:p> </o:p>
So for public folder migration,
the only supported path is cross forest 2007/2010 to 2007/2010 and then inter forest 2007/010 to 2013. Or
we can first export all the public folder to PST from the Exchange 2007 forest, then import the PST to the Exchange 2013 forest.
<o:p></o:p>
Regards, Eric Zou

Double prompts for Exchange 2013 migrated users: "The microsoft exchange administrator has made a change that requires you to restart outlook"

I have Exchange 2010 SP3 in my environment and am migrating to Exchange 2013. Whenever a mailbox is migrated, the Outlook 2013 client will prompt the user with a "the exchange administrator has made a change that requires you to restart
Outlook". When the user does so, he or she is prompted again. After he or she closes and reopens Outlook for the second time, the issue is gone permanently.
I've seen a number of other posts about repeated prompts like this but I haven't yet found one or someone gets exactly 2 prompts for each client and no more.
A couple of pieces of information that may be relevant:
1. On exchange 2013, the authentication method for the internal host name is NTLM
2. I have not yet migrated public folders from Exchange 2010. I plan to do that after the mailbox migration is complete.
Thanks in advance for your help.

Hi,
From your description, after mailboxes are moved from Exchange 2010 to Exchange 2013, users receive the following prompt when opening Outlook.
The Microsoft Exchange Administrator has made a change that requires you quit and restart Outlook.
In order to solve this issue, you need to apply the Outlook update that is described in KB 2863911.
For your reference:
Outlook 2013 cannot connect after an Exchange Server 2010 mailbox is moved to Exchange Server 2013
https://support.microsoft.com/kb/2934750?wa=wsignin1.0
Hope this can be helpful to you.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Amy Wang
TechNet Community Support

Server 2012 and Exchange 2013 Migration from SBS 2011

Server UpgradeI'm migrating an SBS 2011 server to a new machine with Server 2012 R2 and a Hyper-V server running Exchange 2013. I've set up the new machine, all is running well in a test environment. I now want to migrate the old server to new. These are the steps I'm going to take and I wanted advice for any modifications or errors. 1. Demote DC on Server 2012 that I set up to test. 2. Join new Server 2012 to existing SBS 2011 domain. 3. Promote Server 2012 to DC. 4. Join the Hyper-V Server 2012 to the Server 2012 domain.5. Migrate Exchange 2010 on the SBS 2011 Server to Exchange 2013. 6. Transfer FSMO role from SBS 2011 Server to Server 2012 DC. I'll copy shared data files using robocopy.The only things I'm not sure about is the FSMO order, when to do that and the fact that I already have Exchange 2013 installed in the test...
This topic first appeared in the Spiceworks Community

I recently acquired a SuperMicro chassis that has a SAS2 expander backplane. It has SFF-8087 ports on it.http://www.supermicro.com/manuals/other/BPN-SAS2-846EL.pdfI made a post on another forum and someone mentioned that the card couldn't be used with that backplane since it's a SATA controller, however, the backplane is both SAS and SATA device compliant, it's only the RAID controller, as far as I know, that is a "SATA II" controller, and not a SAS controller.So, I couldn't find anything in the official documentation of this controller on whether or not it was able to control SAS devices. The card itself has a 3 SFF-8087 ports though, couldn't this theoretically still be used with a SFF-8087 to SFF-8087 cable(seen below)since the backplane is a SAS/SATA backplane?...

Creating public folders Exchange 2013 powershell

Hello, we have exchange server 2013 with a lot of public folders
We use script to create this folders and to manage them.
With upgrade to 2013 command New-PublicFolder was changed.
parameter -server was deleted, and now we gaining error:
Creating Public Folder
New-PublicFolder : Cannot find information about the local server XXX.XXXXXX.com in Active Directory. This may be related to a change in the server name.
+ New-PublicFolder -DomainController $dcserver -Name $grpn -Path '\Projects'
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [New-PublicFolder], LocalServerNotFoundException
+ FullyQualifiedErrorId : [Server=XXXXX,RequestId=XXXXXXXXXXXXXXX,TimeStamp=19.04.2014 3:55:21] 465E6BC6,Microsoft.Exchange.Managemen
t.MapiTasks.NewPublicFolder
Now i found a solution but is it normal to use something like this :
$exsession = New-PSSession -ConfigurationName Microsoft.Exchange –ConnectionUri "http://$mailserver/PowerShell/" -Authentication Kerberos
Invoke-Command -Session $exsession {param($grpn,$pffn,$pfpn,$grpnpg,$dcserver) New-PublicFolder -DomainController $dcserver -Name $grpn -Path '\Projects'} -ArgumentList $grpn,$pffn,$pfpn,$grpnpg,$dcserver
sleep 20
Invoke-Command -Session $exsession {param($grpn,$pffn,$pfpn,$grpnpg,$dcserver) Enable-MailPublicFolder -DomainController $dcserver -Identity $pffn} -ArgumentList $grpn,$pffn,$pfpn,$grpnpg,$dcserver
sleep 20
Invoke-Command -Session $exsession {param($grpn,$pffn,$pfpn,$grpnpg,$dcserver) Add-PublicFolderClientPermission -DomainController $dcserver -User $grpnpg -AccessRights 'Author' -Identity $pffn} -ArgumentList $grpn,$pffn,$pfpn,$grpnpg,$dcserver
sleep 20
Invoke-Command -Session $exsession {param($grpn,$pffn,$pfpn,$grpnpg,$dcserver) remove-PublicFolderClientPermission -DomainController $dcserver -User "Default" -Identity $pffn -confirm:$false} -ArgumentList $grpn,$pffn,$pfpn,$grpnpg,$dcserver
sleep 20
Invoke-Command -Session $exsession {param($grpn,$pffn,$pfpn,$grpnpg,$dcserver) Add-PublicFolderClientPermission -DomainController $dcserver -User "Default" -AccessRights 'CreateItems' -Identity $pffn} -ArgumentList $grpn,$pffn,$pfpn,$grpnpg,$dcserver
Invoke-Command -Session $exsession {param($grpn,$pffn,$pfpn,$grpnpg,$dcserver) Add-PublicFolderClientPermission -DomainController $dcserver -User "Anonymous" -AccessRights 'CreateItems' -Identity $pffn} -ArgumentList $grpn,$pffn,$pfpn,$grpnpg,$dcserver
sleep 20
Invoke-Command -Session $exsession {param($grpn,$pffn,$pfpn,$grpnpg,$dcserver) Set-MailPublicFolder -DomainController $dcserver -Identity $pffn -HiddenFromAddressListsEnabled $true} -ArgumentList $grpn,$pffn,$pfpn,$grpnpg,$dcserver
sleep 20
Invoke-Command -Session $exsession {param($grpn,$pffn,$pfpn,$grpnpg,$dcserver) Add-DistributionGroupMember -DomainController $dcserver -Identity $grpnpg -Member $pfpn} -ArgumentList $grpn,$pffn,$pfpn,$grpnpg,$dcserver
sleep 20
#Closing remote session
Remove-PSSession $exsession
is there any other solutions to do this operations?

Hello, we have exchange server 2013 with a lot of public folders
We use script to create this folders and to manage them.
With upgrade to 2013 command New-PublicFolder was changed.
parameter -server was deleted, and now we gaining error:
Creating Public Folder
New-PublicFolder : Cannot find information about the local server XXX.XXXXXX.com in Active Directory. This may be related to a change in the server name.
+ New-PublicFolder -DomainController $dcserver -Name $grpn -Path '\Projects'
You can specify the parameter mailbox but that is optional.
Example:
New-PublicFolder -Name SomeName -Path \Projects -mailbox "PF Mailbox"
...and you have more examples in the Technet Article New-PublicFolder
Martina Miskovic

Exchange 2013 Migration Questions

Exchange 2013 SP1 to a new server. I just realized that I have been asking migration questions on the "general" forum. Here's the deal:
We just want to move to a newer server and reuse the "old" server as a DAG member. We have a production exchange 2013 SP1 server and I found that the DB is not on a RAID'ed drive. So, we purchased a server. I installed 2012 R2 and all windows updates.
Then installed exchange 2013 SP1. Then got our AS/AV software installed. When I boot the new server up and login to ECP, it sees all the exchange users, DB and info. So, I followed:
http://technet.microsoft.com/en-us/library/dd876926(v=exchg.150).aspx
to migrate users and current email to the new DB. However, when users logged in their current email was not there. I also tried to use the ECP migration option and this resulted in the same, users old email was not in their inbox. So I had to perform that
same process on the old DB to get users old email back. I then tried to use the migration option in the ECP->same issue. So as of now, we are on the old DB and things are working fine.
According to:
http://technet.microsoft.com/en-us/library/aa997006(v=exchg.65).aspx
When moving from server to server, the DB filename must be the same. The non-production server does not have the same DB filename. Could this be the problem? Could someone point me to documentation on migrating from server to server

So I ran Get-Mailbox -Database “Source Database Name” " -ResultSize Unlimited | New-MoveRequest -TargetDatabase “Target Database Name” and moved all the user mailboxes. Then moved the system mailboxes, public folders and
OAB. Adjusted send connector to reflect new server. Log in as a user, all email is there. Great! Dismount the old DB. Wait a few minutes and user email is still there. Woohoo! Shut down the old exchange server and a few minutes later, all email is gone. Boo!
Boot the old server back up and mount the old DB, all email is back in user inbox. How do I use only the new DB in exchange 2013?
So I just dismounted the old DB and all email stays in users inbox?! So it must be something with the old server that did not get moved over but for the life of me I cant figure out what

Exchange 2013 migration warning, cmdlet canceled

I have an Exchange 2013 SP1 on 2012 R2 and I get this warning migrating a users mailbox from 2010
Cmdlet cancelled. Cmdlet New-MoveRequest, parameters {TargetDatabase=XXXX, WhatIf=True, Identity=xxxxx BadItemLimit=3, BatchName=MigrationService:XXXX, CompletedRequestAgeLimit=7.00:00:00}.
I removed user info.
Looking here I see some similar postings but nothing in the way of an answer. It completes fine, no issues, but these warnings indicate something is off.
Any answer for this?

Hi,
Based on my research, the warning may be caused by the disk storage performance on one of your Exchange servers. And here are some similar threads you can refer to:
http://social.technet.microsoft.com/Forums/en-US/00a48c77-3ddf-4d3b-b870-425a8a6e288e/exchange-2013-cu-2-cmdlet-cancelled-cmdlet-newmoverequest?forum=exchangesvradmin
http://social.technet.microsoft.com/Forums/en-US/d93249da-22d9-496a-a5c0-529077ea33be/exchange-2013-cu-2-cmdlet-cancelled-cmdlet-newmoverequest?forum=exchangesvradmin
Thanks,
Angela Shi
TechNet Community Support

Exchange 2013 migration and Lync server

hi guys,
i wanna upgrade my exchange 2010 to 2013 in our company.
but i faced with a question
will exchange migration has effect on Lync server an should i reinstall it again in our caompany or not?
plz help me
thanks guys

Hi,
you will need to config IM in OWA for Exchange 2013 server.As i can remember voice and everything else should be fine.
Here is a guide for enabling IM in OWA:
http://www.expta.com/2010/09/how-to-integrate-lync-server-2010-with.html
Just remember to point DNS to the New Exchange 2013 server and it should be fine.
Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you. Thank you! Off2work

Exchange 2013 migrations logs deleted!

Hi,
I migrated mailboxes from 2010 to 2013 one domain straight forward process that went successfully. The migration reports were deleted from the 2013 ECP. Any idea how to get logs or information on "when" mailboxes were moved to the 2013 servers?
Thank you
Ibby667

Hi,
I migrated mailboxes from 2010 to 2013 one domain straight forward process that went successfully. The migration reports were deleted from the 2013 ECP. Any idea how to get logs or information on "when" mailboxes were moved to the 2013 servers?
Thank you
Ibby667
You can get that information using Get-Mailboxstatistics.
Example:
Get-Mailbox | Get-MailboxStatistics -IncludeMoveReport | FL Displayname,MoveHistory
UPDATE: Exchange 2013 stores by default information about the latest
5 moves in the mailbox, so that is why you can get the information even if the migrationbatch or moverequest has been deleted (MaxMoveHistoryLength="5" in *\bin\MsExchangeMailboxReplication.exe.config)
Martina Miskovic
all suggestions in here will work, however i like & believe it is best to pull the moverequeststatistics vs the mailbox statistics.
as listed in my reply, this will help to user determine numerous things about the move that the mailboxstatistics will not show
I agree, but if the moverequests has been deleted (default setting: 30 days) and you want to know when a mailbox was moved, then you can with Get-Mailboxstatistics.
Martina Miskovic

Public Folder Exchange 2010 to Exchange 2013 Migration

Similar Messages

Maybe you are looking for