Not immediately.
The Get-View cmdlet is indeed faster in larger vSphere environments.
And with Get-View you can also get access to vSphere API methods and properties that are not yet exposed through PowerCLI cmdlets.
Some suggestions I always give:
- Set yourself some practical goals. That is more productive then reading and learning cmdlets one by one. For example, try to produce a report to document your vSphere environment. Later, add functionality, for example a function to compare two such reports and list the changes.
- Don't forget to improve your PowerShell knowledge. PowerCLI is built on top of PowerShell, knowing the basics will make scripting a lot easier and will allow you to write more efficient code
- Start with the PowerCLI cmdlets, and see how far they can bring you
- First the Get- cmdlets, they can do no harm, you are only reading from the vSphere environment
- Later the Set- and New- cmdlets, these allow you to modify and create objects and settings in the vSphere environment
- Start digging into the API. For example, add some values to your report that are not readily available through PowerCLI cmdlets
Christophe made a great document on a sample learning track for PowerCLI.
See his PowerCLI study guide – core concepts
