We've gotten reports of an installation glitch that makes it so that node management cmdlets won't work when run from a remote client (they'll work just fine run on the headnode) due to a registry key that doesn't always get set up correctly.  Fortunately, there is a simple work around!  If you are trying to run PowerShell from a remote client and get an error like this:

PS> get-hpcnode
Get-HpcNode : Unable to find assembly 'Microsoft.Ccp.Sdm.Store, Version=2.0.0.0, Culture=neutral, PublicKeyToken=null'.
At line:1 char:12
+ get-hpcnode <<<<
    + CategoryInfo          : NotSpecified: (Microsoft.ComputeCluster.CCPPSH.GetNode:GetNode) [Get-HpcNode], Serializa
   tionException
    + FullyQualifiedErrorId : Microsoft.ComputeCluster.CCPPSH.GetNode

You should be able to remedy the problem by adding the following registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\HPC\BinDir" with a value of "C:\Program Files\Microsoft HPC Pack\Bin\".  You can either do so manually, or just run the .REG file attached to this post.

 Then, just open a new PowerShell window and you should be good to go!  We hope to have a fix for this at some point soon.