Reimage schedule

There are a couple of ways, that I know of, to accomplish this.
The first is most "standard" and the second is a bit more "non-standard" 🙂.
With either one, I recommend using the Image Validation or Staged Image features of Nerdio's Desktop Image Management to minimize the number of failed reimage tasks.

The Reimage the Entire Host Pool option is preferred because it will grab the number of hosts you specify reimage them and then do the rest.
Whereas the Reimage a Group of Hosts option has the potential for more administrative overhead if one of the hosts is reimaged (with a new name) or replaced entirely. Both will get the job done, but it's just depending on how you want to set it up and handle your maintenance schedule.

Reimage the Entire Host Pool

When you reimage the entire host pool, there's the Process hosts in groups of setting that allows you to specify the number of hosts that will be reimaged at a time.
In the example below, I have it set to 4.
Assuming there's 8 hosts in the host pool, it will keep 4 hosts online while it reimages the other 4.
Once those are done, the remaining hosts will be reimaged.

NOTE: With the MESSAGING flag turned-on, any users who are currently logged-in will be prompted to log-off/on so they don't lose their work.
If they do log-off/on, they will be put (automatically) on one of the hosts that was reimaged.

Reimage a Groups of Hosts

The other way to do it is to schedule a reimage of certain group hosts at a time and scheduling another group of hosts for another time.

1. Manage the host pool
2. Select one or more hosts and choose Reimage/Resize Selected from the Select Bulk Action drop-down
   
3. Enter a Name for the Reimage Schedule, set your Image options and click Save & Close
   
   
4. Select one or more of the remaining hosts and choose Reimage/Resize Selected from the Select Bulk Action drop-down
5. Click the Add New Schedule button, set your reimage preferences similar to what you did in Step 3
   

Hi Dave Stephenson,

Thank you for the quick answer.

We dont want any downtime for the users or send them a message that they should sign out and sign in again. Maybe we go for multiple pools one for day time and one for night time and instruct the users to pick the wright pool.

You're very welcome 🙂.

If that's the case, two (or three) host pools would make more sense.
Instead of giving them instructions of which pool to join, I would put them in security groups according to their shift (Morning, Night, Swing, etc.) and then assign each group to their respective host pool.
That way, they're presented with only the host pool they are assigned.

You could also put them in the same FSLogix File Share so that if they change shifts, they wouldn't need to recreate their profile or have your team move their profile to a different file share manually.