Aug 2 2017

Automating Day-to-Day PowerShell Admin Tasks – Jobs and Workflow – Simple Talk #simple #workflow #software


Automating Day-to-Day PowerShell Admin Tasks Jobs and Workflow

Figure 12 Workflow in format XAML


We have arrived at the end of this article dedicated to administrations tasks with PowerShell. We have looked at how the use of Jobs and Workflows can help you in your routine tasks.

A good starting point in working out the best strategy for the implementation of PowerShell tasks in a series of steps :

  • First step. Job
  • Second step. Workflow
  • And finally new complex combinations. For example: a workflow within another workflow.

From my experience, two mains benefits of creating a PowerShell Job are:

  • Running simple commands in background. Think about the visibility of your command line.
  • Reviewing the results of your jobs whenever you want.

It makes it easier to manage a remote background Job if you collect the results in a central location unless the data is sensitive. In that case, I maintain results on the remote computer for security purposes.

In my opinion, Workflow is very flexible and can be easily customized to match with your corporate IT environment. Workflow comes into its own if you identify those activities which can be executed in parallel and add them into a Workflow.

I hope that you now understand better the usage of jobs and workflow while processing your daily actions. Just remember that the more your tasks are automated, the more time will save. Simplify your life to the maximum.

Subscribe for more articles

Fortnightly newsletters help sharpen your skills and keep you ahead, with articles, ebooks and opinion to keep you informed.

Want more? Subscribe to our fortnightly newsletter

[Total: 7 Average: 4.4/5]

  • PS Version
    What version of PS needs to be running for this. Using 4 and the Show-NetfirewallRule is not there

    enabled-eq true does not work
    Can you please provide the script as I am getting

    enabled. The term ?enabled is not recognized as the name of a cmdlet, function, script file, or operable program.

    Are you sure it is ?enabled-eq”true” ?

    You need at least Windows PowerShell 4.0.
    You get powerShell version 4.0 automatically with Windows 8.1 and Windows Server 2012 R2.

    Below is the full command.

    Related articles

    Also in Powershell

    Because it is important with maintaining Virtual Machine environments to be able to repeat routine tasks completely accurately, Windows PowerShell has grown in importance for the job. Now you can manage the Hyper-V environment via PowerShell without needing to use the Hyper-V Manager console. It opens up many opportunities for automation. Read more

    Also in Sysadmin

    PowerShell’s Desired State Configuration (DSC) framework depends on the Local Configuration Manager (LCM) which has a central role in a DSC architecture. It runs on all nodes that have PowerShell 4.0 or above installed in order to control the execution of DSC configurations on target nodes. Nicolas Prigent illustrates the role of the LCM in the ‘Push’ mode of configuring nodes. Read more

    Also in PowerShell

    PowerShell is a scripting language, and like all scripting languages it struggles to perform well with rapid iterative processes such as aggregation. It isn’t well-known that PowerShell can use LINQ for many of those tasks which would otherwise use iteration, though somewhat awkwardly. However, some of the speed improvements you can get are startling. To get you well started, Michael explains every LINQ function. gives you example code in C#, The PowerShell way of getting the result, and finally Powershell’s use of LINQ. This article could change the way you use PowerShell. Read more

    2005 – 2017 Red Gate Software Ltd

    What do you think of the new Simple Talk? Give us your feedback

    Written by admin

    Leave a Reply

    Your email address will not be published. Required fields are marked *