Skip to main content
Question

Scheduled Reboots - Intelligent Operations - Categories

  • Nov 6, 2026 4:45 PM UTC
  • 3 replies
  • 27 views

We do scheduled restarts on VM’s monthly. We have several hundred VM’s.

I want to be able to reboot a group of servers at say 9am, then another group of servers at 9:15am. I feel the easiest way would be to tie group 1 to a category (MaintGroup1), and group 2 to a separate category (MaintGroup2), then utilize Intelligent Operations to run the VM Reboot actions on the categories at the specified times.

My primary issue is that I don’t see a way to assign the operation to a category. It gives me the list of all my VM’s, but again, with hundreds of VM’s it would be very time consuming to add them all to the reboot operation individually.

Is there a way to do this besides manually adding each one?

3 replies

jarrodl
Forum|alt.badge.img+3
  • jarrodl
  • Vanguard
  • Nov 6, 2026 5:43 PM UTC

What are you using for your endpoint management?

The reason I ask is most endpoint management solutions include patching and reboot capabilities, so you ideally should be able to hand it via your endpoint management solution. 

Platform Engineer | Nutanix Technology Champion 2026
  • RWH
  • Author
  • Voyager
  • Nov 6, 2026 7:05 PM UTC

We use Tanium, which is already used for the patching process itself, however we would rather utilize Nutanix for the reboots. NGT allows for graceful (guest) reboots on the VM’s - that’s why we were hoping to use the VM Reboot operation that’s built into Intelligent Operations.

jarrodl
Forum|alt.badge.img+3
  • jarrodl
  • Vanguard
  • Nov 6, 2026 7:42 PM UTC

Hmm, I’m not able to test this but this could be something worth exploring.

Item 1: Reboot Times:

This can be handled by the time trigger

Documentation: https://portal.nutanix.com/page/documents/details?targetId=Intelligent-Operations-Guide-vpc_7_6:mul-playbook-time-create-pc-t.html

 

Item 2: VM Identification - Category X

Then you might have a couple of pathways here.

Option A: Self Service Runbook

If you have NCM Self Service, you may be able to work with a Self Service Playbook to handle the VM look up (Untested).

 

Option B: Ansible Playbook:

You could have it call an ansible playbook that handles returning a list of VMs from an inventory based on the category assignment, parse that into the intelligent ops runbook and have that trigger the reboot VM action.

For the loops on Intelligent opts, you can only go two ifs deep. So keep that inmind. 

 

Let me know if that is something that is viable.

 

Platform Engineer | Nutanix Technology Champion 2026
Terms & ConditionsAccessibility statement