New in Commands: Enrollment Commands allow more customization of your new device experience.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
โ12-15-2022 03:31 PM
One of the features that admins have wanted from us for some time is the ability to run commands without any admin action, especially at the time a new device enrolls.
Customer Request: Make sure that any new device has provisioning commands run at enrollment time, so I donโt have to remember to go do it, or so that my user can enroll their freshly shipped device without IT having to be hands on keyboard when it happens.
Starting today (December 15th), JumpCloud can now deliver enrollment commands on macOS, Linux or Windows devices to ensure:
- Commands run on any device thatโs added to JumpCloud through any of our enrollment methods.
- More than one command can be run at enrollment, and Commands will run in alphabetical order
- All commands will report back results in the Admin Portal.
We think that you're going to love this major enhancement to your onboarding flows, allowing new systems that get the JumpCloud Agent to proceed through configuration tasks without admins needing to be hands on.
- Labels:
-
Commands
-
Device Management
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
โ01-13-2023 04:33 PM
I have requested this trigger for many months now. Thanks for making this happen JumpCloud๐๐ฟ
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
โ01-13-2023 04:44 PM
And you can see Tom's demo on the IT Hour if you missed it: The IT Hour | 2022 Wrap Up and Our Favorite Things 12.16.22
Like someone's post? Give them a kudo!
Did someone's answer help you? Please mark it as a solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
โ03-22-2023 03:03 PM
This is an outstanding addition to JC functionality but it would be _even better_ if you could specify device groups/user groups instead of an all-or-nothing by OS type
![](/skins/images/1519CD93B86343CA58368DF3BFFB373D/responsive_peak/images/icon_anonymous_message.png)
![](/skins/images/1519CD93B86343CA58368DF3BFFB373D/responsive_peak/images/icon_anonymous_message.png)