top of page
  • ExchangeMaster

Missing PowerShell Cmdlet

Updated: Apr 20, 2021

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.


33 views0 comments

Recent Posts

See All

To avoid unpredictable results due to your script reading from or writing to "random" domain controllers, it's good practice to use the -Server or -DomainController parameter pertinent to a given cmdl

Recently I needed a quick script to set the two-letter O365 country codes, while my only source for the setting was the three-letter codes in a given AD forest. This presented a problem, because O365

bottom of page