I am installing the PowerActions v1.5 in my lab as it will be very handy to be able to execute PowerCLI scripts while working in a Mac Chrome browser. But not working yet.
I am using Win2K12 with all the patches as of 4/7/16. I got the following error during the install process.
I got past this by executing the .MSI at the command prompt when I opened the command prompt as an Administrator. I copied the .MSI into the documents folder, then accessed the command prompt as Admin, and changed to that directory and executed using the following command line:
msiexec /i PowerActions_1_5_0.msi
I am using Brian’s excellent article (and this one which mentions vSphere 6 support) to help with the install.
BTW, I used the latest .NET, and I had an embedded SSO but had nothing to do because of it. I am also using vSphere 6.0 U2. My PowerCLI is 6.3 Release 1.
I am not saying this all works. Look at the exciting error when I try to access the console:
I did confirm the PowerActions service is running, and yes, I did do the Set-ExecutionPolicy Remote Signed.
Thanks for Frank’s help on this! When I figure it out the big red and blue issue above I will do another article.
Update:
- 4/13/16 – The red error above is because I am using PowerCLI 6.3 R1 and it doesn’t happen with PowerCLI 6.0 R2.
- 4/13/16 – You can find out the whole story of making PowerActions work in this article.
Michael
=== END ===
Notes from MWhite 