Scripted Sequences

Scripted Sequences

The Scripted Sequences feature in Nerdio Manager provides an intuitive, GUI-based way to build sequences of tasks to run on managed devices, without the need for scripting knowledge. You can use Scripted Sequences to schedule and run tasks including:

  • Install and uninstall applications

  • Create, edit, and delete registry keys

  • Run custom scripts

  • Restart the device.

Note: Scripted Sequences are distinct from Scripted Actions, a more developer-oriented Nerdio Manager feature designed to run custom PowerShell scripts on a broader range of managed devices.

Availability

This feature is in Public Preview.

The feature is available in the following Nerdio Manager plans:

AVD Core

True

AVD Premium

True

Windows 365

True*

Unified Endpoint Management

True

* Windows 365 deployment is supported via Intune device management only; direct deployment via Windows 365 provisioning policies is planned for a future release.

Limitations and known issues

Issue/limitation

Impact

Mitigation/planned fix

The Scripted Sequences feature is currently available for AVD and Intune-enrolled devices only.

Direct application of scripted sequences to Windows 365 devices via provisioning policies is not supported.

Support for Windows 365 provisioning policy-based assignments is planned for a future release.

The Scripted Sequences feature does not currently support automatic remediation

If a sequence is run on a particular device group, it will run only on devices that are part of the group at the time it is initiated, and won't automatically run on devices subsequently added to the device group.

Run sequences manually on any devices subsequently added to the group.

While the Scripted Sequences feature is in Public Preview, volume restrictions apply.

  • Each sequence can contain a maximum of 50 tasks (irrespective of whether they are in task groups).

  • Each sequence can contain a maximum of 20 application install/uninstall tasks, to prevent timeout before the sequence run is complete.

  • Each run is restricted to 100 devices. If the total number of target devices selected for a given run (across individual devices and device groups) exceeds 100, the scripted sequence will run only on the first 100 selected devices.

  • Break large and complex chains of tasks into multiple scripted sequences.

  • Create sub-groups of devices specifically for running scripted sequences if the target group would otherwise exceed the device limit.

Enabling Scripted Sequences requires Nerdio Manager to create a new Azure storage account.

It is not currently possible to use an existing account, or to change the attached storage account after enabling the feature.

The ability to modify the associated storage account is planned as a future development.

If any task within a scripted sequence fails on a particular device with an unhandled exception, the entire sequence will stop running.

No further tasks in the sequence will run on the device, which may leave it in a partially configured or otherwise undesirable state.

See Scripted Sequences: task types and parameters for guidance on scenarios that might trigger unhandled exceptions in predefined tasks.

The Executions page currently does not automatically update as new sequence executions are completed.

Information on the Executions page may not reflect the status of recently run tasks.

Use the Refresh button to display the most up-to-date list.

Scripted sequences are deployed to to Intune-enrolled devices using a Task Worker script that is subject to a small number of limitations regarding customization. These limitations don't apply to direct deployment of scripted sequences to AVD.

  • The Nerdio Task Worker can't currently be automatically deleted from devices to which it has been deployed.

  • The Nerdio Task Worker doesn't currently support multi-NME instance scenarios.

  • It is not currently possible to rename either the Nerdio Task Worker script or the associated Entra groups created by enabling the feature.

The ability to remove the task worker will be added in a future release.

The Nerdio Task Worker script is currently unsigned.

The device script execution policy must be set to allow unsigned scripts.

The Task worker script will be publicly signed in a future release.

Role-based access control (RBAC) and permissions

      Nerdio Manager roles

Creating and running scripted sequences in Nerdio Manager requires the Admin role.

      Additional permissions

For deployment to Intune-enrolled devices, Nerdio Manager must be assigned the permissions Group.ReadWrite.All and DeviceManagementScripts.ReadWrite.All. These permissions are managed on the Intune integration configuration page.

Procedures

The following procedures guide you through configuring and managing Scripted Sequences:

Deployment considerations

      Required resources

Scripted Sequences require a storage account from which tasks are collected by devices. Line-of-sight visibility between the target device and the storage account is required.

      Scaling considerations

There are no special resource usage or performance impacts to consider when running scripted sequences at scale. However, larger environments are more likely to be impacted by the device volume limitations in place for scripted sequence runs and to require the suggested mitigation measures.

      Task Worker deployment on Intune-enrolled devices

Nerdio Manager runs scripted sequences on Intune-enrolled via Intune platform scripts, as follows:

  • A task scheduler runs on Nerdio Manager every 15 minutes to check for newly scheduled scripted sequence executions, and deploys any scripted sequences initiated since its last check to the target device(s) (subject to initial device limitations while the feature is in preview).

  • A Nerdio Task Worker deployed on the target device runs a check every 15 minutes for newly scheduled scripted sequences, and runs any sequences scheduled since its last check.

    Note: This scheduling arrangement means a maximum time interval of 30 minutes between a scripted sequence being initiated in Nerdio Manager and starting to run on a given target device, provided that

    • the device is online; and

    • a Nerdio Task Worker has previously been deployed to the device.

    If a Nerdio Task Worker has not previously been deployed to the device, this will be instantiated before any scripted sequences are run. This process may take over an hour to complete.

Help and support

      Contact us

Contact our Sales team for more information about this feature.

Raise a support ticket about this feature.

Was this article helpful?

0 out of 0 found this helpful
Have more questions? Submit a request

Comments (0 comments)

Please sign in to leave a comment.