This article answers frequently asked questions about using scripts in Atera. Scripts allow technicians to automate maintenance, monitoring, remediation, and configuration tasks across Windows, Mac, and Linux devices.
Below you’ll find guidance on uploading, scheduling, troubleshooting, and managing scripts effectively.
Overview
Q: What scripting languages does Atera support?
A: Atera supports PowerShell, Batch (.bat), and Shell (.sh) scripts for Windows, Mac, and Linux devices.
Q: Is there a size limit for uploaded scripts?
A: In the Pro subscription plan for Atera, there is a 20MB limit for uploading .msi and .exe files. For users on higher subscription tiers, the upload limit is increased to 1GB.
Q: Is there a limit to the number of scripts I can upload?
A: No, there is no set limit for uploaded scripts.
Q: Do scripts require admin rights?
A: Scripts run as SYSTEM (Windows) or root (Mac/Linux) by default. Administrative privileges are required.
Q: What is the maximum execution time for scripts?
A: Scripts have a 1-60 minutes of execution time.
Q: Is there version control for scripts?
A: No. Updating a script overwrites the previous version. Keep backups if you wish to retain versions.
Q: Can scripts be run as the current user instead of SYSTEM/root?
A: Yes, select “Run as current user” when executing or scheduling the script.
Q: What is the difference between System and Current User permissions?
A: The difference lies in who the action runs as on the device:
System permissions run under the local SYSTEM account, which has elevated privileges on the device.
Current User permissions run under the currently logged-in user’s account, with only the permissions that user has.
Q: If I run a command in PowerShell/CMD or execute a script, will it continue running if I close the window, or do I need to keep it open?
A: Once the command or script is sent, it will continue running on the device even if you close the PowerShell/CMD window.
Script Management
Q: How do I upload a script to Atera?
A: Go to Admin > Monitoring and Automation > Scripts, then click ‘Create script’ or ‘Upload script’.
Q: How do I edit or update an existing script?
A: Open the script in Admin > Scripts, select it, and click ‘Edit’ to make changes.
Q: How do I remove a script I no longer need?
A: Delete it directly from the Scripts page in Admin > Monitoring and Automation.
Q: Can I access or share scripts with others?
A: Yes, you can use or contribute to Atera’s Shared Script Library, which includes community and Atera-verified scripts.
Q: Can I test a script before wide deployment?
A: Yes, execute it on a test device and review output in the Recent Processes Report.
Running and Scheduling Scripts
Q: Can I run scripts on multiple devices at once?
A: Yes, scripts can be executed in bulk from Devices, Sites, or Customers pages.
Q: Can scripts be scheduled automatically?
A: Yes, add them to an IT Automation Profile and set a recurring schedule (daily, weekly, etc.).
Q: Can I schedule scripts to run outside business hours or per time zone?
A: Yes, automation profiles run at each device’s local time. You can schedule tasks for off-peak hours.
Q: How do I add a script to an automation profile?
A: In an IT Automation Profile, add a step, choose Script, select your file, and save.
Q: Can scripts run on offline devices?
A: Scripts queue and execute once the device comes back online.
Q: Can I chain multiple scripts or prompt users before execution?
A: You can chain scripts by calling others from within one file. User prompts are not supported.
Q: Why is my script output being cut off in the report?
A: For performance and stability reasons, script output in reports is limited to 32,000 characters. Any output beyond this limit is automatically trimmed and cannot be expanded in the report view.
Q: How can I access the full script output?
A: To access the complete output, consider writing it to a file or logging it to another destination outside the report.
Monitoring and Reporting
Q: How can I view script results or logs?
A: Check the Recent Processes Report, Automation Feedback, and Alerts pages for output and errors.
Q: Are scripts logged or audited?
A: Yes, execution details (technician, time, result) are logged in each device’s activity history.
Q: Can I get email notifications when a script completes?
A: No direct notifications are sent, but you can monitor status and results in reports. You can attach the script to an IT Automation Profile and check the feedback email:
Q: How do I check if a script completed successfully?
A: Review exit codes and outputs in the Recent Processes or Automation Feedback dashboards.
Q: What happens if a script fails?
A: Verify the correct OS, execution method (SYSTEM vs. user), and syntax. Check logs and retry locally.
Automation and Remediation
Q: Can scripts trigger alerts or tickets?
A: Yes, scripts can be attached to threshold profiles or auto-healing rules to generate alerts or tickets.
Q: Can I use scripts for automatic remediation (auto-healing)?
A: Yes, attach scripts to thresholds for automatic resolution of issues (e.g., restarting a failed service).
Q: How do I use script-based monitoring thresholds?
A: Add a script in a Threshold Profile; its output can trigger alerts when custom conditions are met.
Q: Can I use scripts for regular maintenance?
A: Yes, schedule cleanup, patching, or optimization scripts through automation profiles.
Script Capabilities
Q: Can scripts call external APIs or download files?
A: Yes, if permitted by the device’s security and firewall settings.
Q: Can scripts install or remove software?
A: Yes, using PowerShell or Batch scripts. Integrate Chocolatey (Windows) or Homebrew (Mac) for automation.
Q: Can scripts manage users, passwords, or accounts?
A: Yes, scripts can handle user creation, modification, password resets, and cleanup of old profiles.
Q: Can scripts configure network adapters, printers, or shares?
A: Yes, scripts can set IPs, DNS, printers, and network drives.
Q: Can scripts modify system settings (firewall, registry, policies)?
A: Yes, as long as the script runs with admin privileges.
Q: Can I use scripts to monitor performance metrics (CPU, RAM, disk)?
A: Yes, scripts can collect and report system metrics or trigger alerts based on thresholds.
Q: Can scripts automate OS upgrades, reboots, or patching?
A: Yes, though OS updates are best managed through Atera’s patch management tools.
Q: Can scripts manage BitLocker, Defender, or antivirus settings?
A: Yes, PowerShell scripts can check encryption, set exclusions, or trigger scans.
Q: Can I automate file transfers, backups, or cleanup?
A: Yes, scripts can upload/download files, back up user data, and delete temporary files.
Q: Can scripts deploy custom configurations (wallpapers, hosts, shortcuts)?
A: Yes, scripts can copy or replace these elements for all users on a device.
Q: Can I use scripts to collect inventory or event logs?
A: Yes, scripts can retrieve hardware/software data, serial numbers, or export Windows Event logs.
Security and Best Practices
Q: Are there security risks to running scripts?
A: Yes. Always review scripts for malicious code and restrict upload/run permissions to trusted users.
Q: Can I restrict script use by technician, site, or customer?
A: Only admin users can upload or run scripts. Assign scripts to specific profiles or device groups for scope control.
Q: How do I ensure scripts don’t disrupt users?
A: Schedule scripts during off-hours or include logic to detect active sessions.
Q: How do I ensure script reliability and safety before deployment?
A: Test scripts in a controlled environment, review the code, and maintain backups.
Q: How can I ensure scripts aren’t blocked by antivirus?
A: Whitelist Atera agent and script paths in your AV or endpoint protection tools.
Advanced and AI Features
Q: Is AI available to assist with script generation?
A: Yes, Atera’s AI Copilot can generate scripts, suggest commands, and help optimize automation workflows.
Q: Can I execute scripts through the Atera API or external triggers?
A: No. Scripts can only be triggered through the Atera platform interface or automation profiles.
Q: Can scripts use environment or Atera variables?
A: Yes, Atera supports script variables for dynamic data, along with standard OS environment variables.
Q: Can scripts update custom device fields?
A: Yes, script outputs can populate custom fields for inventory or monitoring purposes.
Troubleshooting
Q: How do I troubleshoot scripts with no output?
A: Verify syntax, output redirection, and permissions. Run the script locally to confirm behavior.
Q: What should I do if a script behaves unexpectedly?
A: Contact Atera Support with script details, device info, and logs, or consult the Shared Script Library for verified samples.
