2 Answers
2

This happens when you're missing the .Net types Exchange uses. PowerShell remoting perfomrs some serialization that makes some objects end up as "PsObject" instead of the full strongy typed object. The solution is to install the Exchange Management Console on your client computer, this will include the .Net types you need.

Thanks, that makes sense. Unfortunately our Exchange Server is in a resource forest and my management workstation is not. I've yet to find a way to install the exchange management tools on a machine that is not in the Exchange resource forest.
– SturdyErdeMay 21 '15 at 11:41

Note, the EWS Managed API appears to require a 64-bit machine. I ran it first from my workstation and got a Windows Installer error stating that "This installation package is not suported by this processory type. Contact your product vendor."
– SturdyErdeJun 8 '15 at 12:20

That is a factor, but I don't think the actual problem. As noted in the answer/comments from Trondh, I am unable to install the required management tools because the management machine in question is not in the Exchange forest. In this case, the Set-ADServerSettings -ViewEntireForest command does not help. Thanks, though!
– SturdyErdeJun 8 '15 at 12:14