u/nanaki989

So there you have it, an easy and elegant solution from WotC. The Company who brought you the award winning TV Comedy "Can you defeat 100 Million Scalpers/Bots in 20 minutes for a Goblin Storm Deck?"

This is extremely sarcastic and meant to poke fun at the bizarre and horrid Asendia tracking. I do think it may actually help people find some tracking information though. I asked for permission to post this to the mod team but if its too much we can remove it.

Even after all these various couriers you may still not get up to date information but almost always the last mile USPS does a good job of saying its out for delivery at least.

Short story long, our previous IT staff decided to have our power users test M365 before rolling it out, then rolled it out and couldn't migrate on prem mailboxes of the test users to the cloud since they already existed. The issue is that I couldn't just delete the online mailboxes when I arrived since they had been in use dual function for a while. I followed this guide https://learn.microsoft.com/en-us/troubleshoot/exchange/user-and-shared-mailboxes/mailbox-exists-exo-onpremises and got to the point where I try and remote restore the mailbox on prem to the cloud and get the following error.

Some infrastructure information. We are running Version 15.2 (Build 1748.10) Exchange 2019 CU15 on Server 2019. .net framework 4. We have a hybrid connection to m365 and I came in on the tail end of the migration piece which worked well enough.

Things I have tried.

TLS 1.2 settings to confirm use of strong Cryptography and registry edits.

Triple checked IIS Settings and Certs and removed IIS IP restriction features

confirmed admin credentials and move rights

Our Network guy says the port is open, but I suspect our Firewall is the culprit regardless of what he says. I'm out of ideas to try and was hoping for a little help. We are a relatively small org and I have very little on prem exchange experience so this process is a little daunting.

I run this command

$cred = Get-Credential

New-MailboxRestoreRequest -RemoteHostName "mail.domain.com" -RemoteCredential $cred -SourceStoreMailbox "GUID" -TargetMailbox "GUID" -RemoteDatabaseGuid "GUID" -RemoteRestoreType DisconnectedMailbox

and get this error

Write-ErrorMessage : ||The call to 'https://mail.ourdomain.com/EWS/mrsproxy.svc' failed. Error details: The SSL connection

could not be established, see inner exception. --> The SSL connection could not be established, see inner exception.

--> Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host..

--> An existing connection was forcibly closed by the remote host..

At C:\Users\myadmin\AppData\Local\Temp\2\tmpEXO_r4thaxj0.kay\tmpEXO_r4thaxj0.kay.psm1:1220 char:13

+ Write-ErrorMessage $ErrorObject

+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

+ CategoryInfo : NotSpecified: (:) [New-MailboxRestoreRequest], MRSRemoteTransientException

+ FullyQualifiedErrorId : [Server=SN7PR01MB8066,RequestId=361a1f0d-510f-31f9-2d5e-023eaf1874f3,TimeStamp=Tue, 18 A

ug 2026 14:41:56 GMT],Write-ErrorMessage

It's either this or The Master of Lake Town is throwing gang signs.