Help CenterIn order to run a PowerShell Script, you'll need to upload a PowerShell ( *.ps1 ) file into the scripts repository, which can be found in Admin (on the side panel) > Scripts.
Example of a common PowerShell Script: A user 'password age' report, saved as an HTML file:
PS C:\> Get-ADUser -Filter "Enabled -eq 'True' -AND
PasswordNeverExpires -eq 'False'" -Properties
PasswordLastSet,PasswordNeverExpires,PasswordExpired |
Select DistinguishedName,Name,pass*,@{Name="PasswordAge";
Expression={(Get-Date)-$_.PasswordLastSet}} |sort
PasswordAge -Descending | ConvertTo-Html -Title
"Password Age Report" | Out-File c:\Work\pwage.htm
There are two ways to deploy the script:
- Immediately from Agent page > Manage > Scripts
- Automated profile
To create a script, follow the steps below:
|
1. From the left-hand panel click Admin |
 |
|
2. Then click Scripts |
| Note: You can also access the menu from the Devices page. |
| The Scripts page displays. |
|
3. Click Upload Script |
|
The Upload Script dialog box displays. |
 |
|
4. Upload the script file from your PC ( *.bat, *.msi, *.exe, *.ps1 ) and click Upload.
|
|
To apply the script to an Agent:
|
|
1. From the left-hand panel click Devices |
 |
|
2. Under the required Agent's Manage menu click Run Script |
|
The Run Script dialog box displays |
 |
|
Click Submit.
PowerShell Execution Policy
PowerShell's execution policy is a safety feature that controls the conditions under which PowerShell loads configuration files and runs scripts. You can find more details on this execution policy here. To get the current execution policy on a machine, you can use the cmdlet Get-ExecutionPolicy Atera will bypass the Execution policy on Powershell scripts in all situations: when live-managing PowerShell, when executing a script via an IT Automation profile, when running scripts immediately on a machine and when using the auto-healing scripts within a Threshold profile item.
|
Liron Hanania