Much like how blueprints control the device fleet at large, individual and group actions control can control one-off device actions. Use these actions to organize your devices, troubleshoot, and perform other tasks. Some actions can be used with other device types.
Note: Although Windows devices are visible in the Advanced Devices & Groups view, commands are not currently supported from the Advanced view. We currently recommend using the Basic Devices & Groups view for Windows devices. Advanced view support will be added in the future.
In this article:
Individual Device Actions
In Devices & Groups, click on the device’s ellipsis (...) menu to perform device actions.
- Move to group: Move the device to a different group. The blueprint linked to that group can be converged to that device.
- Modify Tags: Add or remove tags associated with the device. Tags are useful for organizing devices.
- Rename Device: Change the device's name, also known as its alias name.
- Ping Device: Have the device check in with the console.
- Screen Lock: Lock the device’s screen.
- Run Script: Run a script on the device.
- Change Blueprint: Change the device’s blueprint. You can choose to just change the blueprint, or change and converge to the new blueprint.
- Converge: Converge the device to its current blueprint.
- Remove Device: Remove the device from Esper.
Multiple Device Actions
Select multiple Windows devices and then click on the Actions button to perform actions on multiple devices.
When multiple Windows devices are selected, you can:
- Move to group
- Ping
- Screen Lock
- Run Script
- Change Blueprint
- Converge
- Remove
Managing Groups of Windows Devices
Manage Windows devices in a group.
You can apply the following actions to devices in a group:
Move to group
- Ping
- Screen Lock
- Run Script
- Change Blueprint
- Converge
- Remove
Enterprise applications can also be managed at the group level. Although both methods are possible, group app management could conflict with apps managed at the blueprint level. In general, users should choose whether they want to manage applications at the blueprint or group level.
Group level app management was originally designed to test application versions on devices before deploying those apps to production devices.
In a group, go to Actions and select App Management.
Then selection from the following options:
- App Platform: Windows
- App Type: Enterprise
- App Action: Install or Uninstall
- App: Choose the enterprise app
- Version Name: Choose the app version name
Then select Install (or Uninstall).
Check the installation status from the App Event Feed.
Event Feed
Check the status of commands (including the converge command) in the Event Feed.
If you run a script, click on its name to see the script.
The script will appear.
An option to download the script will appear.
Scripts show a success message in the Event Feed when they reach the device. However, this does not necessarily mean the script successfully ran on the device. Use exit codes in your script to verify that the script successfully runs on the device. Any non-zero code will show a Failure in the Event Feed.