Deprecated cmdlets (Get-MessageTrace and Get-MessageTraceDetails)

[TheFruggg]

Hi there, great tool!

Are the any plans to update/add functionality or can you suggest any workarounds or alternatives now that those cmdlets are deprecated?

Thanks!

[takacsi77]

Hi! I have the same question! How can I solve this? "[11/19/2025 10:48:08 AM] - [ACTION] - Gathering messages sent by:user-user@domain.com in the last 10 days
Write-ErrorMessage : ||Get-MessageTrace will start deprecating on September 1st, 2025. Please refer to: https://learn.microsoft.com/en-us/powershell/module/exchange/get-messagetracev2?view=exchange-ps to switch to
Get-MessageTraceV2.
At C:\Users\usersname\AppData\Local\Temp\tmpEXO_0s5plljk.l2n\tmpEXO_0s5plljk.l2n.psm1:1191 char:13

•         Write-ErrorMessage $ErrorObject
  

•         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  

  • CategoryInfo : InvalidOperation: (:) [Get-MessageTrace], ValidationException
  • FullyQualifiedErrorId : [Server=PAXPR04xxxxx07,RequestId=xxxxx-xx67-e0f7-a469-7a4822ed17ee,TimeStamp=Wed, 19 Nov 2025 09:47:06 GMT],Write-ErrorMessage

[11/19/2025 10:48:08 AM] - No Data Found" Any hint how can I try to update the script? (sorry I dont have experience with this) Thank!

[takacsi77]

ok, in this case looks like I just need to update the Get-OspreyUserMessageTrace.ps1 file in the "c:\Program Files\WindowsPowerShell\Modules\Osprey\1.0.3\functions\User" folder, line53 Get-MessageTrace --> Get-MessageTracev2