DIY Guide: Create Your First Automated Script in Atera in 5 Steps

Automating routine maintenance and remedial tasks is one of the fastest ways to free up your team’s time for strategic projects. Atera’s scripting engine empowers IT pros to push custom code—Batch, PowerShell, or Shell—to endpoints at scale, all from within a single pane of glass. In this guide, you’ll learn how to author, configure, and deploy your first script in under 10 minutes, so you can stop clicking through individual devices and start letting automation do the heavy lifting.

Key Takeaways

• Access the Scripts page in Atera’s Admin console to view or create scripts.
• Choose a method: create from scratch, upload an existing file, or generate with AI Copilot.
• Fill mandatory fields (name, description, file type) and author your code in the editor.
• Configure optional properties like category, max run time, and execution context.
• Test on a dummy device, then deploy to your fleet via profiles or manual runs.

Step 1: Access the Scripts Page

Every script lifecycle in Atera begins under Admin > Monitoring and automation > Scripts.
 

1. Log in to Atera and click Admin in the sidebar.

2. Select Monitoring and automation, then Scripts.

   
   

Here you’ll see two tabs: My Scripts (your personal library) and Shared Script Library (community and Atera-provided scripts) 

Step 2: Choose Your Creation Method

Atera supports three script ingestion methods:
 

1. Create script
   • Click Create script.
   • Ideal for new scripts under 100 lines. 
      
2. Upload script
   • Click Upload script, choose your file, then fill metadata.
   • Perfect for heavyweight installers or signed binaries. 
      
3. Generate via AI Copilot
   • Click Create script, switch to the Copilot script generator tab.
   • Enter a prompt like “Remove temp files older than 7 days,” then click Generate.  
   • Review and tweak the AI output before saving

Step 3: Fill Mandatory Fields & Author Your Code

Once you’ve chosen a method, the Create script form requires these mandatory inputs:
 

• Script name: Clear, concise, e.g. “DiskCleanup-TempFiles.”
• Script description: One-line summary for future reference.
• File type: Batch (.bat), PowerShell (.ps1), or Shell (.sh) 
   

Then, author or paste your code in the editor. For example, a PowerShell snippet to clear the Recycle Bin:
 

Step 4: Configure Optional Properties & Save

Click More script properties to fine-tune execution:
 

• Category: Tag scripts for filtering (e.g., “Maintenance,” “Security”).
• Max script run time: Define a timeout between 1–60 minutes.
• Arguments: Supply command-line parameters.
• Run as: Choose System (elevated) or Current user. 
   

After configuring, click Create. Your script now appears under My Scripts, ready to use.

Step 5: Test and Deploy Your Script

Job-to-Be-Done Scenario

Let’s say you manage 50 Windows servers. Before you roll out a cleanup script to all servers, test on a non-critical VM:
 

1. Navigate to Devices, select your test machine, then Manage > Run script.
2. Choose your newly created script from My Scripts and hit Run.
3. Verify the action completed successfully in the execution summary. 
    

Once validated, deploy at scale by:
 

• Adding to an Automation Profile under Patch Management and IT Automation, or
• Scheduling via the script’s context menu in My Scripts. 

Ready to Automate?

Click Here

FAQ Summary

What script types does Atera support?

Atera supports:

• Batch scripts (.bat)
• PowerShell scripts (.ps1)
• Shell scripts (.sh)
• Executable files (.exe)
• MSI installers (.msi)
  You can upload these or write inline directly in the Atera scripting console.

Can I use variables in Atera scripts?

Yes. You can use dynamic variables in the format {[variable_name]}.
These values are defined at runtime when deploying the script, allowing for flexible, reusable automation across devices or clients.

How do I roll back a script action in Atera?

Currently, Atera does not support automatic script rollback. To reverse script effects:

• Run a compensating script that undoes the original changes, or
• Manually revert the change on the target endpoint
  For specific cases or rollback feature requests, contact Atera Support 24/7.

Where do AI Copilot–generated scripts appear in Atera?

All AI-generated scripts are saved to My Scripts, marked with a Copilot icon.
You can review, edit, or deploy them just like manually created scripts.

Do I need admin rights to run scripts on devices via Atera?

Yes. Scripts that run as System require the Atera Agent to be installed with elevated (admin) permissions.
If running as Current User, permissions depend on that user’s local rights on the device.

Can I test a script in Atera before full deployment?

Absolutely. It’s best practice to:

• Select a non-critical device (like a test VM)
• Navigate to Devices > Manage > Run Script
• Execute and verify the script before deploying it across your environment

How do I deploy a script across multiple endpoints in Atera?

You can:

• Attach the script to an Automation Profile via Patch Management and IT Automation, or
• Schedule the script using the context menu in My Scripts for broader rollout

Can I edit or update a script after creating it in Atera?

Yes. Go to My Scripts, click on the script name, and make your changes in the editor.
You can update code, description, runtime settings, or even switch the execution method.

How long can scripts run in Atera before timeout?

You can set a maximum run time of 1 to 60 minutes when configuring script properties.
If a script exceeds this limit, Atera will terminate the execution automatically.