2,187
edits
Difference between revisions of "Getting Started (PowerCLI)"
Jump to navigation
Jump to search
→Scheduling: Added "Force 32-bit"
(Move of content from original PowerCLI/VIToolkit page) |
(→Scheduling: Added "Force 32-bit") |
||
| Line 102: | Line 102: | ||
* <code> C:\WINDOWS\system32\windowspowershell\v1.0\powershell.exe -PSConsoleFile "C:\Program Files\VMware\Infrastructure\vSphere PowerCLI\vim.psc1" "& C:\Scripts\ESX-probe.ps1" </code> | * <code> C:\WINDOWS\system32\windowspowershell\v1.0\powershell.exe -PSConsoleFile "C:\Program Files\VMware\Infrastructure\vSphere PowerCLI\vim.psc1" "& C:\Scripts\ESX-probe.ps1" </code> | ||
Or on a Win7 or Win2k8 (64bit) machine you might have something like... | Or on a Win7 or Win2k8 (64bit) machine you might have something like... | ||
* <code> Powershell -PSConsoleFile "C:\Program Files (x86)\VMware\Infrastructure\vSphere PowerCLI\vim.psc1" "& C:\Scripts\ESX-probe.ps1" </code> | * Program/script: <code> Powershell </code> | ||
* Add arguments (optional): <code>-PSConsoleFile "C:\Program Files (x86)\VMware\Infrastructure\vSphere PowerCLI\vim.psc1" "& C:\Scripts\ESX-probe.ps1" </code> | |||
=== Force 32-bit === | |||
To ensure that a script runs in a 32-bit environment rather than 64-bit, you need to run with 32-bit version of PowerShell, so you'd use the following in the Program/script box... | |||
* <code> C:\Windows\SysWOW64\WindowsPowerShell\v1.0\powershell.exe </code> | |||
== Certificates == | == Certificates == | ||