PowerCLI

NetCmdlets V2 is packed full of exciting new features including PowerShell Server (formerly PowerShell Remoting), Parameter Sets, Object Pipelining, and new Cmdlets for SSH Enabled Remoting and Amazon Web Services (S3) Integration. The /n software NetCmdlets extend the features of Microsoft Windows PowerShell with a broad range of network management and messaging capabilities. The current release contains more than 30 Cmdlets providing access to network and host protocols such as SNMP, LDAP, DNS, Syslog, HTTP, WebDav, FTP, SMTP, POP, IMAP, Rexec/RShell, Telnet, and more.

VMware is the king when it comes to virtualization. Windows PowerShell has gotten huge accolades as an extremely powerful tool for automation of IT tasks. These two technologies make a lot of sense together, and VMware is now making that happen with the release of their VI Toolkit for Windows. In "Managing VMware Infrastructure with PowerShell", you will learn how to perform everything from simple ad-hoc reporting at the command-line ("are any of my virtual machines powered off?") to complex scripts to automate a a massive deployment of hundreds of virtual machines. Simple, yet powerful; concise, yet robust; you will enjoy using this new language to solve your old problems using less code than you thought possible. If you are a system administrator responsible for managing a VMware Virtual Infrastructure (version 2.0 or above), or a standalone ESX Server (version 3.0 or above), then you need this book. Aimed at scripters of every level, the book starts off with a PowerShell primer and continues well into the internals of virtualization on the VMware platform.

More PowerShell Goodness: The SAPIEN Blog includes a complete section on Windows PowerShell news and tips, and the SAPIEN Knowledge Base has a growing list of PowerShell-related articles. You may also enjoy www.ScriptingAnswers.com, which offers discussions, training, and free resources for administrative scripting - including Windows PowerShell.

John Troyer has written a great post on the VMTN Blog about the Windows VI Toolkit based on PowerShell. Besides a link to my articles he summed up everyone who is experimenting with this toolkit.

Well, once Carter spilled the beans, everybody is now waiting with bated breath for VMware to release the beta of our new curiously-named VI Toolkit (for Windows). The toolkit is powered by Windows PowerShell, a shell/scripting technology that Microsoft appears to have gotten very right indeed. The VI SDK, while extremely powerful, is not for the faint of heart. This toolkit takes that power and wraps it up in a very simple syntax which creates a compelling tool for VI admins.

In total there are 102 PowerShell cmdlets in the Beta that cover all aspects of Virtual Infrastructure management. The most important thing is that you can now easily write scripts, tailor made to your problems, that save you time and frustration, whether that means saving you 10 clicks or 100. Once you've had a chance to kick the proverbial tires, don't forget to visit the Community Page to give your feedback or to talk with other Beta testers. Last but not least, congratulations to the VI Toolkit (for Windows) team for all your hard work on this release!

Carter Shanklin added a blog entry to the VI PowerShell Blog and officially announced the beta to be released this month. Besides that the PowerShell team is very surprised by all the enthusiasm for the PowerShell lab at the Vmworld in Cannes.  You can also download the lab manual.

Hope you enjoyed the PowerShell lab at VMworld Europe.

We here on the VI Toolkit (for Windows) team know just how exciting PowerShell is, but sometimes we're surprised to learn just how many people agree. Our PowerShell lab at VMworld Europe was attended by over 250 students. What surprised me most though, was that we noticed at least 3 different people working on the PowerShell lab for over 3 hours each. Considering all the great sessions and other labs offered at VMworld Europe, this is really a testament to how important PowerShell is going to be for system management in the coming years.