In spite of the popularity of “DevOps” many IT pros are still divided into two camps: development and operations. Although both groups do much more than their titles imply, they tend to look at enterprise solutions from different perspectives. In our area of batch job scheduling, we see a lot of humility among operations personnel
Technology infrastructure decisions increasingly include some cloud component. Cloud services can decrease maintenance costs, increase reliability or improve efficiency. Amazon Elastic Cloud Computing (EC2) is one such service that enables a company to migrate servers off site and into the Amazon cloud, mitigating the risks of power outages, energy fees and other costly issues. Basic
Managing IT infrastructure is full of exceptions that are beyond your control – network latency, bad disks, power failures and human error. Fortunately, holiday batch scheduling is well within your control when you leverage centralized workload automation. Even in cases where different business units celebrate different sets of holidays, batch jobs can be configured to
Note: This post was originally published in the February 2013 PowerShell.org TechLetter. The whole purpose of PowerShell is to automate tasks. So, why are some users still manually deploying scripts? And why are some organizations relying on one or two users to execute critical PowerShell scripts? The automation of PowerShell scripts is an important step