vmWare: Enabling RemoteSigned execution policy in PowerShell for PowerCLI
Success! The completed install of vmWare's Power-CLI
Installing Power-CLI for vSphere Admin is straight forward
It's not a difficult thing to install Power-CLI, but while I did a vanilla "spousal" installation, I DID get one warning. It was a warning centered on, actually decreasing the security of my workstation a bit. Merely opening it up to the execution of certain types of scripts. But this is a requirement if you do wish to work with such scripts.
"Security, it goes both ways. In other words, for YOU to "hack", or "program" and "Administer" other systems, you've got to open those channels of communications up on your system, and networks.
64 or 32 Bit
You will see, immediately below in the video. At the end of the video I show you the shortcuts for the "32-Bit Power-CLI" icon, and the other one is "64-Bit".
Changing the Script-execution policy under Powershell
The warning (it's not really an error) looked like THIS
A quickie, on HOW to enable a requirement for Power-CLI
The information is all in the video I made. It's up on YouTube, with the right keywords on it. But, the command to use (under PowerShell) is just as follows: Exactly, as follows- spacing and everything. The lack of spaces on certains words is NOT a "typo" in this case...
Just THAT. Nothing more, nothing less. Simple.
This is "it" right here, This picture is THE whole Article...
Power-CLI needs a couple of pieces installed
Power CLI wizard will inform you of the need to install: vmWare Remote Console Plug-in 5.1 and another piece called, vmWare VIX.
It's a fast install, 4 or 5 min tops.
The slowest parts of the install are just where there are some significant file extractions, and then at one point it announces it is performing a "Precompile" with some .Net assemblies.
And that's it!
Get ready to "Script" your life Away, with Power-CLI and PowerShell! Fun for everyone!