PowerCLI - 3

PowerShell Server has been rebranded as PowerShell SSH Server and has moved to a new home as a member of the 'PowerShell Inside' product line (www.powershellinside.com). In addition, the new PowerShell SSH Server is now completely FREE to use when run as a desktop application.

PowerShell Inside is a new and separate division of /n software focused exclusively in PowerShell technologies. PowerShell Inside products make technologies more customizable by enhancing them with PowerShell scripting. /n software has built these tools to provide an easy way to enhance and integrate applications without the complexity or expense of custom development. With PowerShell you get comprehensive access to the power of the .NET Framework in an easy to use interface that is tailor-made to help you get more work done, faster.

The following PowerShell Inside products are currently available:

• PowerShell ASP - Build dynamic Web content with PowerShell.
• PowerShell Panel - A PowerShell powered ASP.NET Panel control.
• PowerShell SSH Server - Access PowerShell remotely from SSH terminals.
• PowerShell Web Part - Extend SharePoint portals with dynamic content.
• PowerShell Data Provider - Databind to PowerShell, like you Databind to SQL.
• PowerShell Office Add-In - Automate Outlook with PowerShell scripting.
• PowerShell SSH Components - Components for PowerShell SSH Server Access.
• PowerShell BizTalk Adapter - Automate BizTalk and simplify orchestrations.
• PowerShell SSIS Task - Automate SQL Server and simplify SSIS Workflows.
• PowerShell Workflow Activity - Simplify WF Workflows with PowerShell.

Arnim van Lieshout over at van-lieshout.com has created a great blog post with all the steps involved in completing the setup of the PowerCLI/The VESI environment:

1.Installation of Windows PowerShell
2.Installation of VMware PowerCLI
3.Installation of The Virtualization EcoShell

On April 8th we had a very good DutchVMUG meeting, which was totally dedicated to using PowerCLI and The VESI (Virtualization EcoShell Initiative). Although setting up the environment is straightforward, I wanted to do a small write-up which leads you through the install process and includes all download links needed.

http://www.van-lieshout.com/2010/04/the-vesi-getting-it-up-and-running/

Pablo Roesch has just announced the winners of the Scriptomania contest, congratulations to everyone that participated!

1. @alanrenouf
2. @lamw
3. @avlieshout

We are happy to announce our Script-O-Mania contest Winners. Our judges were extremely excited about all the creative and useful scripts submitted into the community. The decisions were tough to make, some we even considered splitting the prize money but in the end we went with the following line up. Congratulations to all that won and participated. Also wanted to thank Scott L, Robert B, Jeff H. again for their efforts in participating as Judges.

Steve Jin -> Winners of the VMware Script-O-Mania Contest: Who, What, How and Why?

My former colleague and virtualization friend Harold Schoofs has send me a real cool PowerShell script for automating the reporting part of the vSphere VUM baseline compliancy. The Baseline-Compliancy.Ps1 PowerShell script can be used to check the compliancy of all ESX Hosts registered on a VMware vCenter server and match up to any baseline. It will generate 3 kinds of output Files:

1) One file with all hosts and their compliancy state
2) One file with all attached baselines found
3) One file for every attached baseline found with its content

You can get you copy of Harold’s script here: Baseline-Compliancy.ps1 If you have any questions or suggestions for improvements just send your Tweets to @Hharold.

There are a lot of automation tools available which are able to deploy and configure an ESX host but if you want to use PowerCLI for the finishing configuration part there was always a manual step involved. I’ve found a way to start a PowerShell script from the service console trough SSH. The only thing you have to do is install WinSSHD on one of your Windows servers, just execute the distributable that you downloaded from the Bitvise website and follow the process. As soon as the installer completes, you will have a working WinSSHD installation on your machine. No changes to the default configuration are necessary; you only need to start it. However, you might want restrict your users' access to those features that they actually need, which will improve security. If you are new to WinSSHD, it’s highly recommended that you first make sure that you can establish a working SSH connection before you change any settings on the server. If you cannot connect to WinSSHD using its default configuration, this is most likely due to a network or firewall problem that you will need to resolve before you are able to connect. In its default configuration, WinSSHD accepts connections on the well-known port number for SSH servers, 22.

I’ve recorded a Jing video (with audio) which demos the CPU-Ready PowerCLI script running on my vCenter server launched from one of my ESX host’s service console.

Continue reading "How to access PowerCLI trough SSH" »