Note
This feature is in Public Preview.
A Scripted Sequence assignment runs a Scripted Sequence automatically on devices that join a scope you choose. Instead of selecting devices and selecting Run now each time, you point the assignment at a set of devices, such as an AVD host pool or an Entra device group, and Nerdio Manager runs the sequence on every new device it finds there.
You create an assignment from a Scripted Sequence, and you manage assignments on the Assignments tab of the Scripted Sequences page (Endpoints > Automation > Scripted Sequences). A sequence can have several assignments, so one sequence can serve, for example, a host pool and an Intune device group at the same time.
Note
Scripted Sequences is currently in Public Preview. Assignments are available in Nerdio Manager 8.3 and later, for Azure Virtual Desktop and Intune-enrolled Windows devices.
Important
An assignment runs the sequence once on each newly discovered device in scope. It does not re-run, monitor, or repair devices that it has already processed.
An assignment checks its scope, creates an execution for each new device that it finds, and then leaves that device alone. The following sections describe this behavior.
Device discovery
A background process checks the assignment scope about every 15 minutes. When it finds a device that it has not seen before, it creates a sequence execution for that device, as if you had selected Run now for the newly added devices. A new device is therefore not processed instantly. Devices that appear in scope between scans are picked up on the next scan.
One run per device
Once an execution has been created for a device, the assignment does not touch that device again. If the execution passes, fails, or is canceled, the assignment takes no further action. A device is never re-run automatically.
Changes to the sequence
If you edit the sequence later, devices that were already processed are not re-run. Devices that are discovered after the edit use the updated sequence.
Execution status
The assignment records only whether a device has been discovered. Success, failure, and progress are tracked on the Executions page. The assignment details page lists the devices in scope, when they were detected, the total number of executions, and a link to each device's execution details.
Re-imaged AVD hosts
A host that is re-imaged is treated as a new device, and receives a new execution.
Run the sequence again on a device
To run the sequence again on a device that the assignment has already processed, use Forget. This has the same effect as selecting Run now on those devices.
To run the sequence again on a device:
-
Open the assignment details.
-
Select one or more devices.
-
Select Forget.
The devices are removed from the list, and the sequence runs on them again on the next scan.
Assignment settings
An assignment has a Name, a Description, a Status (Enabled or Disabled), a Platform, a Tenant, a Timeout (days), and one or more targets. For AVD, it also has a Concurrency balancer (AVD) and a Maximum jobs setting. A disabled assignment does not discover devices or create executions.
Scenarios that assignments support
Assignments suit work that must happen once, when a device first appears in scope.
-
Configure new AVD session hosts: When a host pool scales out or hosts are added, each new host receives the sequence (baseline apps, registry settings, and scripts) without an administrator starting it. Use a host pool or a workspace as the scope.
-
Re-image and rebuild: A re-imaged host is treated as new, so the sequence is applied again after the rebuild. Use a host pool or a workspace as the scope.
-
Post-enrollment setup for Intune devices: Devices that become members of a group, for example Autopilot devices or newly onboarded laptops, receive an ordered sequence of installs, scripts, and settings. Use an Entra device group as the scope.
-
Phased or staged rollouts: Add devices to the group in waves. Each wave is picked up on the next scan, and the sequence runs only on the new members. Use an Entra device group as the scope.
-
Ordered, multi-step setup: Use a sequence when the order matters (install, then configure, then restart) rather than separate unordered deployments. This works with either scope.
-
Apps that need secure variables: Shell Apps that use secure variables can be delivered through a sequence on both AVD and Intune devices. See Requirements.
-
Re-apply after a sequence change: Use Forget on the affected devices to run the updated sequence on them again.
Scenarios that assignments are not for
-
Keeping devices compliant or correcting configuration drift: Assignments do not evaluate or re-check devices. Use Unified Application Management policies or Intune configuration for ongoing compliance.
-
Re-running automatically when the sequence or an app version changes: Not supported. Use Forget or Run now on the devices that need the update.
-
Targeting one or two specific devices: Use Run now. Assignment scopes are sets of devices that are expected to grow, and selecting individual devices is not offered.
-
Running on a new desktop image, or when an image changes: Not supported. Assignments target host pools, workspaces, and device groups, not images.
-
Running on an event or a schedule, for example a license alert or a date and time: Not available in assignments.
-
Delaying or batching runs to group several new devices: Not available. Each scan creates executions for the devices that it finds.
Assignments work on the following platforms.
Table 6.
|
Platform |
What you can select |
Notes |
|---|---|---|
|
Azure Virtual Desktop |
Hosts, host pools, and workspaces |
Delivered through the Azure Custom Script Extension. Create one assignment per platform: an assignment cannot cover AVD and Intune together. |
|
Intune (Windows) |
Entra device groups |
Delivered through the Task Worker. Individual devices cannot be selected in an assignment. |
To cover both AVD and Intune devices with one sequence, create at least two assignments on that sequence, one for each platform. Assignments support Windows devices only. macOS is not supported.
-
For AVD devices, assignments use native Azure VM extensions. The Task Worker is not required, because Azure has a native way to assign scripts to devices.
-
For Intune devices, including AVD devices that you target through Intune, the Task Worker must be deployed and healthy on the device. If it is not, the execution stays in Pending. Check the Task Worker analytics page for the device.
-
For Shell Apps that use secure variables, the Task Worker must be trusted. Task Workers that were deployed before version 9 are marked untrusted, and they receive a one-time upgrade through an Intune script (not the usual self-upgrade) before they can receive secure variables.
-
Scripted Sequences and their executions have dedicated permissions under the Automation section of a role, each with Read or Manage access. To create, edit, and run assignments, users need either the Admin role or a custom role with Manage access to Scripted Sequences. Read access lets a user view assignments and executions. Only the Admin role can create custom roles.
Create an assignment to run a Scripted Sequence automatically on the new devices in a scope.
To create an assignment:
-
Navigate to Endpoints > Automation > Scripted Sequences.
-
On the Scripted Sequences tab, select the three-dot menu for the sequence, and then select Create assignment....
-
In the Create Assignment for Scripted Sequence dialog box, enter a Name and, optionally, a Description. To start the assignment as soon as you create it, turn on Status. It is Disabled by default.
-
From the Platform list, select AVD or Intune, and then select the Tenant. Under Deploy to..., select the type of target and search for the targets. For AVD, the targets are hosts, host pools (for example, multi-session host pools), or workspaces. For Intune, the targets are device groups. Select Add new target... to add more than one target.
Important
Devices that are already in scope when you create the assignment are treated as new, and each receives an execution, even if the sequence ran on it before. Check the scope before you enable the assignment.
-
Set Timeout (days). The default is 3. For AVD, you can also set the Concurrency balancer (AVD) (the default is Global) and Maximum jobs (the default is 10). The Intune dialog box does not show the concurrency options. Select Create.
-
To see the runs that are created as devices are discovered, open the Executions tab.
The Assignments tab lists your assignments. For each one, it shows the Status, Name, Sequence, number of Tasks, Targets, the date of the Last Run, and the number of Executions. A green status means the assignment is active.
To manage an assignment:
-
Navigate to Endpoints > Automation > Scripted Sequences, and then select the Assignments tab.
-
For the assignment, select the eye icon to view it, or the pencil icon to edit it.
-
To change its state or run it, select the three-dot menu, and then select Deactivate (or Activate for an inactive assignment), Force run, or Delete.
-
Device cap: Up to 1,000 devices are processed per execution (100 in versions before 8.2). When a scope contains more devices, they are sorted by display name, and the devices beyond 1,000 are not processed.
-
Platforms: Windows only. Assignments support AVD session hosts and Intune-enrolled Windows devices. macOS is not supported.
-
Targets: Each assignment targets either AVD (hosts, host pools, or workspaces) or Intune (Entra device groups), not both.
-
Existing devices on the first scan: Devices that are already in scope when you create an assignment are treated as new, and receive an execution, even if the sequence ran on them before. An option to adopt earlier executions is not available.
-
Status: Assignments do not show per-device success or failure. Use the Executions page.
-
Job timeout: Sequences on physical endpoints time out after 90 minutes, which matches the AVD Custom Script Extension limit. Sequences with several large installers can exceed this limit.
-
Sequence size: A sequence supports up to 50 tasks, with up to 20 applications.
-
Drain mode: A sequence does not hold an AVD host in drain mode, so a host can accept user connections while a sequence is still running.
-
Hybrid AVD hosts: Hybrid hosts can be selected, but running sequences on them has not been validated for the preview.
Scripted Sequence assignments and Unified Application Management (UAM) policies share a similar interface, but they work differently.
Table 7.
|
Feature |
Scripted Sequence assignment |
UAM policy |
|---|---|---|
|
Purpose |
Run a sequence once on newly discovered devices |
Keep applications installed and up to date |
|
Re-evaluation |
Never re-runs a device it has processed |
Re-evaluates devices continuously and re-runs when applications change |
|
Removal tracking |
Does not track removals |
Tracks and removes as devices leave scope |
|
Status location |
Executions page |
Policy page |
|
Best for |
Ordered setup tasks at build or enrollment |
Ongoing application management |
Use the following table to resolve common issues with assignments.
Table 8.
|
Symptom |
What to check |
|---|---|
|
Execution stays Pending on an Intune device |
Confirm the Task Worker is deployed and enrolled on the device and review the Task Worker analytics page. |
|
Assignment shows no status for a device |
This is expected. Open the Executions page for the device's status. |
|
Device did not run again after editing the sequence |
Expected. Select the device in the assignment details and choose Forget, or use Run now. |
|
Some devices were not processed in a very large group |
The device cap applies. Split the group into smaller groups, or use several assignments. |
|
Shell App with secure variables is rejected on an Intune device |
Check whether the Task Worker is flagged untrusted and complete the one-time Intune script upgrade. |
|
Cannot select a single device |
Expected. Use Run now for individual devices. |
Comments (0 comments)