hi - i have been trying to get the hardware monitoring using powershell up and running as per this link ..... http://blogs.vmware.com/vipowershell/2009/03/monitoring-esx-hardware-with-powershell.html. i am running pshell/winrm from a 2k8 server and am authenticating against a vsphere Host. If i use the commands specified such as this ...Get-VMHostWSManInstance -VMHost (Get-VMHost) -class CIM_Fan -ignoreCertFailures ... i get the follwoing error messages ..
PS C:\Users\Administrator> Get-VMHostWSManInstance -VMHost (Get-VMHost) -class CIM_Fan -ignoreCertFailures
Get-WSManInstance : Access is denied.
At line:44 char:34
+ Get-WSManInstance <<<< -Authentication basic -ConnectionURI $uri -Credential $credential -Enumerate -Port 443 -UseS
SL -SessionOption $option -ResourceURI "$baseUrl/$class"
+ CategoryInfo : InvalidOperation: ( , UnauthorizedAccessException
+ FullyQualifiedErrorId : Exception,Microsoft.WSMan.Management.GetWSManInstanceCommand
Get-WSManInstance :
At line:44 char:34
+ Get-WSManInstance <<<< -Authentication basic -ConnectionURI $uri -Credential $credential -Enumerate -Port 443 -UseS
SL -SessionOption $option -ResourceURI "$baseUrl/$class"
+ CategoryInfo : InvalidOperation: (http://schemas....hema/2//CIM_Fan:Uri) , InvalidOperationExceptio
n
+ FullyQualifiedErrorId : WsManError,Microsoft.WSMan.Management.GetWSManInstanceCommand
can anyone shed any light on why this error is being generated ?
Was also playing with that, same problem.
Did you already see this What's Up Duck ?
____________
Blog: LucD notes
Twitter: lucd22
Blog: lucd.info Twitter: @LucD22 Co-author PowerCLI Reference
thanks for the info Luc. i can see the same error in my messages file when trying to run the script as mentioned in the post ...
openwsmand: pam_unix(openwsman:auth): bad username
So if i have followed the thread correctly its the \ in front of the username that is the issue. Is there a version of pshell that anyone has got this working on ?