This one hadn't reared its head in a long time, but here's a classic PowerShell error which isn't yet lost to history. When a common cmdlet suddenly isn't recognized, here's a solution.

There are still plenty of legacy Exchange Server installations out there, and customers who need to migrate. I doubt you will see this problem beyond 2013 RTM, but if this looks familiar then you're on the right track here.

And here's the fix:

First, exit your Exchange Management Shell session. Then, look for a folder in your Windows profile folder, called RemotePowerShell, and delete it. When you start a new EMS session, the cmdlets should be available. Be sure not to delete the RemotePowerShell folder in anyone else’s profile.

#PowerShell