When people start looking at our enterprise job scheduler, they often ask “Aren’t many of the features of JAMS already available through PowerShell?”. The answer is “yes”.
We embrace PowerShell and we are constantly seeking out ways to make JAMS fully accessible to it. Why? Microsoft has established and actively supports PowerShell as a standard for server management and administration, two tasks high on the list of responsibilities for JAMS users. Naturally, when our users are ready to automate their PowerShell scripts, we want them to be able to migrate them seamlessly into the automation architecture for their entire IT environment. To make the transition even easier, we’ve written more than 50 cmdlets to set dependencies, transfer files, read job queues and check user credentials.
Travis Jones’s post Scheduling Background Jobs in Windows PowerShell 3.0 provides a good introduction to the basic Job Scheduling cmdlets native to Windows PowerShell 3.0 Beta and Windows Management Framework 3.0 Beta. If you experimented with PowerShell 2.0’s background jobs, you’ll like where 3.0 Beta is going with triggers and advanced configurations.