PowerWF News, Tutorials, and more...

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.


Special - 20% Discount


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!

PowerVI

vSphere Automation fueled by PowerShell


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.
January 30, 2012

Best Practices for Developing and Presenting SLA Information

I saw that PowerWF champion Chris Ross is giving a presentation on SLA’s (Service Level Agreements) in System Center on Thursday.

In this co-hosted webinar, Chris Ross from Catapult Systems will join Rob Reyes from Bay Dynamics.Topics will include:

  • What is an SLA .. really
  • Best Practices for developing SLAs for your System Center infrastructure
  • Leveraging the power of Service Manager
  • Presenting SLAs and metrics with IT Analytics’ Key Performance Indicators and dashboards

Space is limited.

Reserve your Webinar seat now at:

https://www1.gotomeeting.com/register/574414905

Power of IT Analytics Series: Best Practices for Developing and Presenting SLA information

Date:     Thursday, February 2, 2012

Time:     10:00 AM – 11:00 AM PST

(read more)



December 2, 2011

SCSM User Group Recap - Video of PowerWF In Action

PowerWF for Service Manager (SCSM) was highlighted at the December 2011 SCSM User Group.  Topics discussed include:

  • SCSM 2012 Implementation Briefing from Acceleres
  • Extending Service Manager with PowerWF
  • SCSM 2012 News
  • General Q&A for SCSM 2010/2012
  • 2012 Release Request Activities and SSP Example Demo from Travis Wright

Click over to watch the video.



October 11, 2011

PowerWF/SCSM Tip

Chris Ross has an important PowerWF/SCSM tip.  I was going to bug @XCUD to blog about this discovery, but it looks like Chris beat him to it.

Just a quick note for those of you who have PowerWF running on your primary Management Server.

Please, for the time being, remember to stop the Service Manager Services running on the primary Management Server (the one running workflow).


June 27, 2011

PowerWF & PowerSE 2.5 have been released!

PowerWF - Visual PowerShell is the ultimate PowerShell development tool. PowerWF allows you to create automated IT solutions by leveraging the full strength of PowerShell and Windows Workflow.

WHAT’S NEW in v2.5

  • Added support for IE9
  • Added support for PS Remoting
  • Added support for STA
  • Improved workflow runtime engine
  • Improved ‘Generate PowerShell’ in script editor grid
  • Improved support for Windows XP
  • Improved app start performance


This is the version demonstrated at MS Tech Ed 2011 and the System Center Rally 2011 this summer. Download it today at http://powerwf.com

Every PowerShell cmdlet is at your fingertips for simple drag and drop script creation. Easily switch back and forth between visual and traditional scripts. 

PowerSE - Professional Script Editor

PowerSE’s advanced script editor, interactive console, integrated help and powerful debugger make developing PowerShell scripts easier than ever.

System Center - Service Manager

PowerWF for Service Manager is a MUST-HAVE for anyone using Microsoft System Center - Service Manager. Extend Service Manager’s authoring experience using PowerWF to create custom activities and Management Packs.

System Center - Operations Manager

Effortlessly create custom management packs for cross-vendor, 3rd Party and legacy system monitoring using PowerWF and Microsoft’s Operations Manager.



April 21, 2011

SMLets Beta 3 released

Beta 3 of the latest SCSM PowerShell cmdlets (SMLETS) has been released.

32 NEW cmdlets!

The latest release adds 32 cmdlets to the mix, which of course means the PowerWF just picked up 32 more SCSM toolbox items.  Here is the list of new cmdlets :

    Get-SCSMObjectTemplate
    Set-SCSMObjectTemplate
    (apply template to a projection object)
    New-SCSMGroup
    Get-SCsMGroup
    New-SCSMView
    Remove-SCGroup
    Get-SCSMQueue
    New-SCSMQueue
    Remove-SCSMQueue
    New-SCSMEnumeration
    Get-SCSMView
    Get-SCSMFolder
    Get-SCSMForm
    Get-SCSPage
    Get-SCSMPageSet
    Get-SCSMViewSetting
    Get-SCSMViewType
    Get-SCSMImage
    Get-SCSMFolderHierarchy
    Get-SCSMStringResource
    Get-SCSMLanguagePackCulture
    Get-SCSMWhoAmI
    Get-SCSMConnectedUser
    Get-SCSMConsoleTask
    New-SCSMUserRole
    Get-SCSMUserRole
    Get-SCSMView
    New-SCSMNotificationSubscription
    Remove-SCSMView
    New-SCSMManagementPackReference
    Get-SCSMManagementPackReference
    Remove-SCSMUserRole

MSI Installer

The release notes say that the SMLets installer is now a standard MSI file. I don’t remember having problems installing the last version (was it just a ZIP file?), but an MSI is always nice.



April 15, 2011

Viewing and Modifying PowerShell from a Workflow

Many of our users have asked questions like:

Is there a way for me to modify the underlying powershell code after creating a worklflow?
Can I save a workflow out as a PS1 file?
Can I see the PowerShell equivalent of a workflow

There are a several ways to answer these questions, but it really boils down to explaining PowerWF workflows and what types of output PowerWF can generate for you.

All about Activities

Although PowerWF lets you easily create workflows using PowerShell cmdlets, its primary output is not a traditional PS1 file.  At first this may seem odd until you realize that although every PowerShell cmdlet is a PowerWF activity, not every PowerWF activity is a PowerShell cmdlet.  The Venn diagram illustrates this and shows some of the many sources of PowerWF activities.

Venn diagram showing PowerWF Activities

Even if a user limits themselves to using only PowerShell activities, there is still a very good chance that they will want to take advantage of workflow features that don’t easily translate back to a simple PS1 file.

But What If I REALLY want to use it in PowerShell

Even though we don’t generate PS1 files by default, that doesn’t mean you can’t use your workflows directly from PowerShell.  Any PowerWF workflow, even those that use non-PowerShell activities and features can be used directly from PowerShell scripts (PS1 files) or from the PowerShell host.

To make your workflows available as PowerShell CMDLETs, use the Deploy tab on the ribbon bar to create a PowerShell CMDLET, Snap-In, or Module.

Deploy to PowerShell

Once a workflow has been deployed to PowerShell you can use it from the host or a PS1 file like any other CMDLET on your system.

But I Want To See and Edit the Actual PowerShell

PowerWF is bundled with PowerSE, a full featured PowerShell script editor. PowerSE lets you view the PowerShell equivalent for a workflow or part of a workflow.  Every activity that is based on PowerShell will have a blue PowerShell icon in the lower left corner.

If you double-click on a PowerShell activity, a PowerShell pipeline, or a PowerShell script block, you can both view and edit the PowerShell using PowerSE.

If you multi-select a group of PowerShell activities, you can choose the Edit PowerShell option from the PowerShell icon drop-down menu.

View PowerShell behind a workflow

The PowerShell commands can even be executed directly in PowerSE.  PowerSE also gives you the option to save the PowerShell script out as a PS1 file.

SO…

In cases where your entire workflow is PowerShell, you can:

  1. Use the “Edit - Select All” option to choose all the workflow acivities.
  2. Choose “Edit PowerShell” from the  PowerSE drop-down menu discussed above.
  3. Verify the script works correctly in PowerSE by pressing Play
  4. Save the script as a PS1 file.


February 11, 2011

Customer Question - PowerWF Remote Deployment

From time to time, the question comes up,…

“If I want to deploy my workflow as an executable or PowerShell Module remotely, what do I need to install on the remote machine?”

When you deploy a workflow from PowerWF, the executable or PowerShell Module could have a number of dependencies. 

  1. If you used a third party PowerShell Module, like PowerCLI or Quest Active Directory, you will need to install the PowerShell Module on the remote machine.  IF you forget, PowerWF will let you know which dependencies are missing when you attempt to run the module or executable.
  2. If you use any non-powershell activities,  you will need them to be available on the remote machine.  In most cases, these will automatically be handled by installing the PowerWF runtime installer on the remote machine (see below)
  3. PowerWF has runtime libraries that are required to run workflows.  There are two possible ways to get these on your remote machine, discussed in detail below.

The PowerWF Runtime

PowerWF has an option that allows you to simply take the item you deployed and use it on a remote machine – the deployment is smart enough to wrap up what it needs and include it.  That said, there are some things it can not wrap up for you, which is why we have the runtime installer. 

Under “Program Files\Devfarm Software\Interop” there is a PowerWF-Module-2.4-Setup.exe installer that will install the runtime files for you.

The auto-deploy functionality, (no runtime installed) is somewhat hidden at the moment.  To get the feature, you need to enable the feature by setting the registry key HKEY_CURRENT_USER\Software\DevFarm Software\PowerWF Studio\Settings\EmbedBootstrapper to True.

The default behavior is that the binaries we create require our runtime footprint to be installed on the target machine first (every machine with PowerWF installed already has our runtime footprint). The runtime footprint comes with the module.



January 27, 2011

PowerWF 2.4 has been released!

PowerWF - Visual PowerShell is the ultimate PowerShell development tool. PowerWF allows you to create automated IT solutions by leveraging the full strength of PowerShell and Windows Workflow.

WHAT’S NEW
• PowerSE - Script Editor, console, intellisence, and powerful debugger.
• Improved 2-way script editing
• Enhanced PowerShell support throughout the product. Even non-PowerShell activities now support PowerShell variables as properties.
• Workflow activities can be interrogated using the embedded PowerShell console.

Every PowerShell cmdlet is at your fingertips for simple drag and drop script creation. Easily switch back and forth between visual and traditional scripts.

Introducing PowerSE - Professional Script Editor
PowerWF’s PowerShell script editor is now available as a stand-alone product. PowerSE’s advanced script editor, interactive console, integrated help and powerful debugger make developing PowerShell scripts easier than ever.

System Center - Service Manager
PowerWF for Service Manager is a MUST-HAVE for anyone using Microsoft System Center - Service Manager. Extend Service Manager’s authoring experience using PowerWF to create custom activities and Management Packs.

System Center - Operations Manager
Effortlessly create custom management packs for cross-vendor, 3rd Party and legacy system monitoring using PowerWF and Microsoft’s Operations Manager.

Visit our new website - Product Information, Videos, and more



October 7, 2010

Tutorial: Integration with Service Manager Authoring (SCSM)

Service Manager (SCSM) is a relatively new addition to the System Center suite of products. Service Manager helps automate best practices within an IT organization, especially in cases of incident reporting and problem resolution, change control, and asset lifecycle management. Service Manager is tightly integrated with Operation Manager, Configuration Manager, and Active Directory Domain Services.

Service Manager (SCSM) provides a workflow based authoring tool to handle the logic behind the specific automated actions. PowerWF extends this functionality significantly by allowing users to either create custom toolbox items within the Service Manager authoring tool or to directly create Service Manager management packs. This tutorial discusses how PowerWF can be used to extend the existing Service Manager authoring tool by creating custom toolbox activities.

Topics Discussed

  • Creating a PowerWF Workflow
  • Using the embedded PowerShell Editor
  • Using Auto-Script Creation
  • Creating Input Parameters
  • Creating Service Manager (SCSM) Toolbox Activities
  • Importing and Using Custom Toolbox Activities in Service Manager

See Requirements…

    Procedure

    1. Create a new workflow called “TopCPUProcesses”
      Create new workflow for Service Manager
    2. Type “Process” in the toolbox search window to find the Get-Process activity. As its name suggest, this activity collect information about the processes running on a computer.
      Add an activity to a workflow using search feature
    3. Double-Click the blue PowerShell icon on the getProcess activity to open the PowerShell editor.
    4. Click the Start button to view the output of this activity. The Grid tab shows the complete results in a table format.
      View PowerShell results in editor.
    5. One nice feature of PowerWF is the ability to automatically generate PowerShell script based on user interaction with the Grid pane. Find the CPU column and click the heading to sort the results. Next, while holding down the CTRL key, select a cell in the CPU and Name columns.

      Automatically create PowerShell scripts from user input

      Note: If desired, additional cells can be selected. Be sure to hold down the CTRL key the entire time while selecting columns.

    Read More



    October 6, 2010

    PowerWF Integration: Service Manager Requirements

    Requirements

    In order to take advantage of PowerWF’s integration with Service Manager (SCSM), PowerWF should be run on a 64-bit machine running Windows Vista or later and using the 64-bit version of PowerWF. Be sure to install the Service Manager authoring tool on the PowerWF workstation. The authoring tool can be downloaded from Microsoft.com.

    PowerWF Running Remotely

    If PowerWF is not installed on the same machine as Service Manager (SCSM), there are few required files that need to be copied to take full advantage of the integration between the two products. Administrator privileges will be required on both the PowerWF and Service Manager machines.

    On the Service Manager machine locate the SDK binaries. These are typically located at:

    C:\Program Files\Microsoft System Center\Service Manager 2010\SDK Binaries

    Copy the entire directory to the PowerWF machine using this directory structure. This usually means adding directories for “Microsoft System Center” under “Program Files”, followed by a sub-directory of “Service Manager 2010”. The “SDK Binaries” directory lets PowerWF create workflows that are compatible with Service Manger.

    At this time, it is required that the SDK Binaries be installed on the C drive at:

    C:\Program Files\Microsoft System Center\Service Manager 2010\SDK Binaries

    Leveraging the Service Manager CMDLETS

    Regardless of where PowerWF is installed, it is recommended that the Service Manager (SCSM) CMDLETS be installed. Download the Service Manager PowerShell CMDLETS from http://smlets.codeplex.com/

    Make sure the contents of the Zip file are unblocked. This is done by right clicking on the SMLets.zip file and selecting Properties.

    Service Manage PowerShell CMDLETs/Module

    When the SMLets.zip Properties window appears, click the Unblock button and click OK.

    Next unzip the cmdlets in:

    C:\Windows\System32\WindowsPowerShell\v1.0\Modules

    Extract PowerShell CMDLETs

    To verify that everything is installed correctly, launch PowerShell with administrator rights. Run this command:

    set-executionpolicy unrestricted

    When prompted, click ‘Y’.

    PowerShell Unrestricted configuratoin

    The final step is to import the module in PowerShell:

    Import-module smelts

    As long the Import happens without errors, PowerWF should be able to discover the CMDLETS and use them as toolbox items.

    PowerWF Service Manage Integration

    NOTE: Be sure to run the 64-bit version of PowerWF when working with Service Manager (SCSM)



     ::: Older Posts :::