As you probably have gathered I've been busy working out how to install all the bits that make up vSphere, and install them automagically without human interaction. It's all about getting away from doing any of my day to day stuff manually - and instead document them fastest, quickest, most automated ways of getting stuff done. They are working me so hard here at Corp.com, and want everything by next week - there's no time to shilly-shally about I can tell you.
So to install vCLI automatically I used:
192.168.3.254\software\VMware\vs5\VMware-vSphere-CLI-5.0.0-373086.exe /s /v/qn
And to install PowerCLI automatically I used the same command-line switches.
192.168.3.254\software\VMware\vs5\VMware-PowerCLI-5.0.0-374833.exe /s /v/qn
After the install of PowerCLI I opened both the 32-bit and 64-bit icons that were left on my desktop – and set the execution policy for both with
set-executionpolicy remotesigned
I've come across situations where if it hadn’t been set for both – cmdlet that was called in a PowerShell script, the script would fail because of an unset execution policy.
No comments:
Post a Comment