Update: behavior described in this blog post has changed in later Cumulative Update; please see Remote PowerShell Proxying Behavior in Exchange 2013 CU12 and Exchange 2016.
Coming to the next CUs ...
Updated Jul 01, 2019
Version 2.0
Blog Post
@Satyajit321 and others- I have a quick and dirty method for solve your administration problem.
To resolve this issue
Open IIS on the CAS server
Navigate to the PowerShell virtual directory
Select "Advanced Settings" from the Actions pane on the right.
Change the Physical Path settings from"C:ExchangeServerV15FrontEndHttpProxyPowerShell" to "C:ExchangeServerV15ClientAccessPowerShell"
Run IISRESET
And of course, I don't advise you to repeat it at home, boys and girls!
I recommend to wait for correction of the problem in future releases.
Regards, Dima.