We’re introducing significant improvements to Automation Manager, making it easier to build, maintain, and modernize automation policies.

This release adds support for PowerShell 7 through a new automation object, while also delivering a much improved script editing experience for Automation Manager users.

Availability

These Automation Manager improvements are available across N-able platforms:

• N-sight — Already available. No action required.
• N-central — Available by applying the N-central 2026.3 Hotfix 1 (build 2026.3.1.3), which includes an updated version of Automation Manager. The expected release date is July 22 – July 30.
• N-central 26.4 — These features will also be included when N-central 26.4 is released.

PowerShell 7 Support for Automation Policies

Automation Manager now includes a new Run PowerShell 7 Script object, allowing automation policies to execute scripts using PowerShell 7.

This gives partners access to a more modern PowerShell runtime for new automation scenarios, while preserving compatibility with existing automation policies.

The existing Run PowerShell Script object will be renamed to Run PowerShell 5.1 Script. It will remain available without any additional changes and continues to use Windows PowerShell 5.1.

This allows partners to adopt PowerShell 7 at their own pace without disrupting existing automation workflows.

No additional endpoint requirements

The new PowerShell 7 object includes everything required to run PowerShell 7 scripts.

On the managed endpoints there is no need to manually install:

• PowerShell 7
• Additional .NET runtime components

PowerShell Module Support

The new PowerShell 7 object supports standard PowerShell 7 cmdlets and can also use compatible PowerShell modules.

This includes:

• Built-in PowerShell 7 functionality
• Compatible custom modules
• Modules already installed on the managed endpoint, where supported

Because PowerShell 7 differs from Windows PowerShell 5.1, some legacy modules may not be compatible.

Partners using custom or existing modules should validate compatibility before migrating automation policies to the new PowerShell 7 object.

Execution Context Compatibility

The new PowerShell 7 object supports common Automation Manager execution contexts, including:

• Local System
• Custom credentials
• Device credentials
• Currently logged-on user

This helps maintain compatibility with existing automation workflows.

Improved Script Editing Experience

We’ve significantly improved the script editing experience in Automation Manager Designer. These enhancements apply to both:

• Run PowerShell 5.1 Script (previously named Run PowerShell Script)
• Run PowerShell 7 Script

This means all Automation Manager users benefit immediately, even if they continue using existing PowerShell 5.1 automation policies.

Editor enhancements

• PowerShell syntax highlighting: Scripts are now easier to read and review with PowerShell-aware syntax highlighting.
• Line numbers: Line numbering makes troubleshooting and script maintenance easier.
• Current line highlighting: The active editing line is now highlighted for improved readability and navigation.
• Parameter auto-complete: Typing $ now presents available Automation Manager input and output parameters for easier insertion into scripts. This helps reduce manual copying and scripting mistakes.
• Font scaling and zoom: Users can now increase or decrease editor font size using built-in zoom controls or mouse scroll shortcuts.
• Word wrap support: Long scripts are easier to read with the new word wrap option.
• Improved editor window behaviour: The script editor now provides a better day-to-day experience by opening maximized by default, and remembering the last window size/position.

Important Notes

In this initial release, the new Run PowerShell 7 Script object supports 64-bit Windows operating systems only.

• Existing automation policies using Run PowerShell 5.1 Script (previously named Run PowerShell Script) continue to function as before.
• Compatibility for some legacy Windows PowerShell 5.1 modules may vary depending on module design.

These enhancements modernize Automation Manager in two important ways:

• Partners can now begin building automation policies with a modern PowerShell runtime.
• Benefit from a much better script authoring experience for both new and existing automation content.