How To AutoMate PowerShell Scripts

Applies To: AutoMate 9, AutoMate BPA Server 9

Video Summary

A short How-To covering AutoMate's PowerShell functionalities, and its ability to embed and run PowerShell scripts.


More Tutorials

Automate Complete Introduction 6/21/173443 views
The Automate Enterprise Ops Console Overview 5/17/172644 views
Getting Started With AutoMate 10 2/19/1511290 views
Getting Started With BPA Server 10 1/30/155557 views
How to Extract Information from Exchange 11/29/125992 views
How To AutoMate VMware 10/29/128942 views
How To AutoMate Amazon Web Services (AWS) 9/25/128018 views
How To AutoMate Email and SMS Notification 8/28/1212404 views
How To AutoMate PowerShell Scripts 7/31/1221925 views
How To AutoMate Web Services 7/5/128487 views
How To AutoMate Web Extraction 7/5/128317 views
Getting Started: BPA Server 9 2/24/129223 views
Getting Started With AutoMate 9 1/6/1222327 views
Overview of the BPA Server Management Console (SMC) 2/24/116872 views
Getting Started With BPA Server 8 2/16/117304 views
Getting Started With AutoMate 8 12/21/1017978 views
Interacting with a Drop-Down Menu 1/24/0820635 views
AutoMate BPA Server Agent Deployment 12/18/0716607 views
User Resource Center 10/16/0711441 views
Account Page 10/16/079786 views
AutoMate BPA Server 7 10/16/0726534 views
Looping and Sending Emails From a List 5/22/0714329 views
Looping With Excel 3/23/0723017 views
Terminal Emulation 2/20/0717538 views
Download File from Web 1/16/0719921 views
Web Account Login 11/20/0623071 views
SQL Query a CSV File 9/1/0630946 views
FTP Uploads by Files Last Modified Date 7/18/0617991 views
FTP Download by Date 6/1/0619665 views
The File Watcher and FTP Actions 3/14/0628959 views
AutoMate 6 Intro (Outdated, See "Getting Started With AutoMate 8") 3/13/0662294 views

Comments (9)

  1. 9/8/13 by Anonymous
    1 Writing by hand is easier than opening all those windows, assuming one even knew what and where to type-in. You need to provide one unified interface; an IDE or something... otherwise you don't have a product to offer. 2. Your product is not clearly priced. Another huge mistake. This means we won't be charged a fair amount; or even worse different pricing depending on how dumb the customer is... 3. You assume there are no other successful products out there. There are better Free and Paid options. 4. You don't show the finished product. what the heck is the script you can create? EXE? VBS? .Net? How do you execute it? From Where? without this it is not clear who and when we should be using this..
  2. 9/9/13 by Leonard Amabile
    @Anonymous: 1.) The PowerShell action, as described in the video, allows the user to either write the PowerShell command or script within the action, which is then executed in the PowerShell environment or the user can reference an external .ps1 file (PowerShell script), which AutoMate can then execute. AutoMate's Task Builder is a fully functional IDE for all of its actions. 2.) All pricing is clearly outlined within the ordering process. A user can select maintenance plans, services, and licenses and view pricing prior to purchase. 3.) A user can download and install a fully functional version of our applications that expire at the end of their evaluation periods. We let our applications speak for themselves and make no such assumptions. 4.) Our applications are not compilers so our software is required to be installed in order to execute tasks and/or workflows. I welcome you to install an evaluation copy of our software where we can then address any questions or concerns you may have.
  3. 10/29/13 by Adam Ingle
    Is there a way to exit the powershell window once the script has finished?
  4. 11/4/13 by Anonymous
    @Adam: The way the tutorial is written and provided will leave the PowerShell window open. However, adding cmd.exe /c at the beginning of the Run action command line will cause the window to close after the script has completed.
  5. 8/13/14 by Charles Zhou
    I have tried to use the "Run" action for running PowerShell. I have set the PowerShell execution policy to RemoteSigned on the server (Windows Server 2008 R2). I have found the PowerShell cmdlet runs successfully when putting it in the "Run" action box directly such as "powershell -noexit -command Get-Help". However, it indicates it cannot be run when putting it inside a PS1 file and called by the "Run" action. The PowerShell window is opened with the red text indication of "the execution of scripts is disabled on this system". I then enter "Get-ExecutionPolicy" inside this PowerShell prompt. It shows it is set to "Restricectd". Do you know why there is different PowerShell execution policy settings when running PowerShell in this two ways? What further configuration can be made to overcome this? I have tried to use "Set-ExecutionPolicy RemoteSigned" inside this PowerShell prompt, but it indicates "Access to the registry key 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PowerShell\1\ShellIds\Microsoft.PowerShell' is denied". Thanks.
  6. 8/13/14 by Leonard Amabile
    @Charles Zhou: Please make sure that the task or Task Builder is configured to run elevated. The error message is because the command or PowerShell prompt is not in an elevated state that can adjust the execution policy.
  7. 8/13/14 by Charles Zhou
    I have further found that Windows on our Windows Server 2008 R2 is a 64bit while the PowerShell window launched by the PS1 file in "Run" action is on 32bit as two PowerShell processes in the Windows Task Manager. One is "powershell.exe" with "RemotedSigned" and another one is "powershell.exe *32". Both are run by the same "User Name".
  8. 8/13/14 by Charles Zhou
    The "powershell.exe *32" is with "Restricted" and cannot be set to "RemoteSigned".
  9. 8/13/14 by Leonard Amabile
    @Charles Zhou: AutoMate and AutoMate BPA Server are 32bit applications and therefore can only initiate 32bit processes. If you are still encountering issues, please post it in the forums rather than on the URC. The URC comment section is not intended for troubleshooting sessions.
Please sign in to your account or your comment will be forever stored under "anonymous".
Include Code Snippet

Search the URC

Subscribe to Version History via RSS
Subscribe to Version History via RSS
Version Watcher

11.0.6 changelog
11.0.6 changelog
other versions downloads


Subscribe to Latest Resources via RSS
Subscribe to Latest Resources via RSS
Latest Resources

show filter options

Subscribe to Forum Posts via RSS
Subscribe to Forum Posts via RSS
Forum Posts