Get the latest tips and tricks directly from the PowerWF development team. Find out about new releases and upcoming features.
Seamless Automation
From the Desktop to the Data Center
The PowerWF family of products are easy enough for desktop and departmental automation, yet powerful and scalable enough for the Data Center. PowerWF compliments Opalis and other RBA solutions, lets you leverage your workforce and preserves your investment as your automation needs grow.
In conjunction with our recently
announced Silver
Award from Windows IT Magazine we
would like to offer our customers an opportunity to save 20%
off any Devfarm product
purchase through the end of the year. This includes all PowerWF products as
well as Devfarm's new PowerVI product!
Designed for the VMware Administrator, PowerVI eases the automation of vSphere infrastructures. PowerVI includes over 100 PowerShell automation scripts that simplify everyday VMware administration tasks and PowerVI makes it easy to author new scripts.
Today’s Friday Fun is a continuation of my exploration of ways to use Start-Job. A few weeks ago I wrote about using Start-Job to create “scheduled” tasks. I realized I could take this further and turn this into a sort of alarm clock. The goal is to execute at command at a given time, but I wanted to make it easy to specify the time. What I have so far is a function called New-Alarm. I have some other ideas and hope to expand this into a module, but for now I thought I’d toss this out to you and get some feedback.
By the way, if you are using PowerWF, it includes an agent that makes it easy to schedule your PowerShell scripts or workflows to run an a specific schedule (Every so many minutes, every Wednesday, etc.)
Richard Siddaway at IT Knowledge Exchange answers a very basic question that many new PowerShell scripters run into - Once I create a function, how do I use it.
Most of my scripts end up being functions because I will eventually combine them into modules
If you are running PowerWF, it is very easy to leverage a function you find on the internet. Simply paste the function into a script block in the workflow and then either call it from that script block or from elsewhere in your workflow.
Devfarm Software, a Windows 8 Launch Partner, today announced the release of version 2.7 of the award winning PowerWF. With this release, PowerWF begins the transition from a popular PowerShell workflow orchestration tool to a complete windows automation platform.
For the past 3 years PowerWF has seamlessly combined Windows PowerShell with Workflow technologies to provide users with PowerShell Orchestration. PowerWF provides a rich automation platform that lets IT Administrators harness the strengths and versatility of Windows PowerShell with a workflow Orchestration layer required to cross technical disciplines.
The latest version of PowerWF provides instant return on investment with one-click automation solutions for many common IT and VMware administrative tasks. The solutions can be run as-is, or easily modified using PowerWF’s visual authoring environment.
“The focus of this release has been jump starting the automation process,” said Ben Vierck, CTO of Devfarm Software. “We want our users to see the value of automation as soon as they launch the product.”
“PowerWF has always provided a powerful authoring environment,” added PowerWF Product Manager Kirk Munro. “This version ensures that users gain the benefits of automation even before exploring PowerWF’s authoring experience.”
PowerWF’s new features include:
New Start Page - Immediately run dozens of automation workflows included with the product and leverage the power of Workflow and PowerShell without requiring the technical knowledge behind the automation scripts.
Improved Microsoft System Center Service Manager (SCSM) support - Deploy management packs right from the Start Page. Management Packs for SCSM include: automatically close resolved incidents; expire inactive problem announcements; cancel pending activities for closed change requests; identify problems from incident trends; notify incident authors about unresolved incidents; and retrieving SCSM statistics.
Improved Toolbox Search - search using command names or keywords.
PowerSE’s new features include:
Easier Breakpoint Management - Breakpoints pane shows all breakpoints set in the scripting environment. Manage breakpoints using the breakpoint cmdlets.
Breakpoints Preserved Across Sessions - Allows continued debugging of PowerShell scripts from one session to the next, even if the file is closed inside PowerSE.
Improved Help Search - search using keywords topic headings. PowerSE includes a keyword search in command descriptions to allow users to discover commands using related terms, such as “vMotion”.
I recently needed to provide a high level capacity overview per VMware cluster looking at some metrics of interest that were being used as a guide to the capacity state of a cluster. Note: these are by no means definitive or the ones you should be using in your environment, but for these purposes they met the requirements. The metrics I looked at per cluster were the ratio of vCPUs to pCPUs, the amount of Effective, Allocated and average Active Memory and the amount of Free Diskspace.
As is usually the case, it would be very straight forward to convert this script to a PowerWF workflow or a PowerVI script so that you can run it from your vSphere client.
I needed to […] check that all of the Windows Services set to Automatic successfully started after the reboot.
This should be pretty straightforward since we have a Get-Servicecmdlet. Unfortunately however, this cmdlet does not return a StartMode parameter, i.e. it’s not possible to tell whether the Startup Type has been set to Automatic, Manual or Disabled. This is quite a large gap in my opinon – if you agree with me you can vote to get it included in a future release here. Of course with PowerShell there’s usually another way to achieve the same objective and using Get-WMIObject it is possible to find out the Startup Type of the service.
Product Note: If you are not comfortable writing scripts, don’t forget that you can use PowerWF to take full advantage of Exchange PowerShell integration without getting lost in scripts.
Found another good candidate for a PowerVI script at vNiklas.djungel.se.
If you are running too many VM´s on your datastores in your vSphere environment you can have some problems, this if your SAN is not VAAI compliant and can handle SCSI locking etc.
Alan Renouf has made a blog post about how to get a report about how many VM´s you have on every datastore, I have extended to only report on running VM´s as these are the interesting number..
The Microsoft PowerShell development team is starting to talk about the addition of Workflow to PowerShell v3. As Hal points out -
A workflow is a sequence of automated steps or activities that execute tasks on or retrieve data from one or more managed nodes (computers or devices). These activities can include individual commands or scripts. Windows PowerShell Workflow enables, IT pros and developers alike, to author sequences of multi-computer management activities — that are either long-running, repeatable, frequent, parallelizable, interruptible, stoppable, or restartable — as workflows. By design, workflows can be resumed from an intentional or accidental suspension or interruption, such as a network outage, a reboot or power loss.
Alan Renouf has posted his top PowerCLI scripts of the week (a couple are from PowerWF friend Luc Dekens). There are scripts on High Availability, Storage DRS, getting VMware Views, and virtual machine start up scripts.