You get an access denied error (error 5)
I think the issue is related to the fact the powershell script is making a network call, "-Node ..... " for which there is no authentication with the local account mapped with BSA.
An automation principal would probably be the way forward
Hi Mike Jones, Thanks for your response.
Yes your understanding is correct about the script, Script will be making a network call.
Do we have a way to map local account to BSA or we can use the local admin account to run the script.
I also tried a workaround, added BSA user to administrators group. Still got the same error.
Adding it to the administrators group is good (I was surprised it was not already a member so that is can install software/patches etc.) however that will not give you remote access to another server even if the account names and passwords are identical.
I haven't done anything with cluster powershell commands, can you use "." as the node the same as you can with cluster.exe ? That might work and perhaps you you run the command on both managed hosts
The only real solution is to use automation principles which were introduced to provide this functionality
Please try using the .\ before script name. Another important pointer is use Set-ExecutionPolicy to set execution policy.