My experience here has been that commands like clist work fine via powershell remoting with the following exceptions:
- You just installed chocolatey. And the path may not be permanent until the first chocolatey run completes.
- You authenticte into the remoting session as a different user than the one you installed chocolatey with. This
might have been fixed in a recent release.
Of course I'm sure there are more exceptions that you may have found. However, if you find yourself in a PS remoting session and clist does not work, try manually adding the chocolatey bin to your path:
I believe that will fix up your session and make the commands accessible.