Not Working and not sure why

[russjar]

Just installed the CLI and fired it up, went to run the connect-viserver cmdlet and it aint working and I don't know why? System is Win7 x32.

C:\Program Files\VMware\VMware vSphere CLI>connect-viserver

'connect-viserver' is not recognized as an internal or external command,

operable program or batch file.

VCP,MCSE NT4/W2k/W2k3, MCSA W2k3

[lamw]

You're posting in the vCLI forum and not PowerCLI.

For PowerCLI questions, please post here - http://communities.vmware.com/community/vmtn/vsphere/automationtools/powercli

=========================================================================

William Lam

VMware vExpert 2009,2010

VMware scripts and resources at:

Twitter: @lamw

Getting Started with the vMA (tips/tricks)

Getting Started with the vSphere SDK for Perl

VMware Code Central - Scripts/Sample code for Developers and Administrators

VMware Developer Community

If you find this information useful, please award points for "correct" or "helpful".

[Dave_Mishchenko · Accepted solution]

The connect-viserver cmdlet is part of PowerCLI and not part of the vCLI. With the vCLI you can specific the host to connect to when running a command.




Dave

VMware Communities User Moderator

Now available - vSphere Quick Start Guide

Do you have a system or PCI card working with VMDirectPath? Submit your specs to the Unofficial VMDirectPath HCL.

[russjar]

Thanks Dave, forgot about the PowerCLI

VCP,MCSE NT4/W2k/W2k3, MCSA W2k3