Currently if a machine cannot be reached because the machine is offline the job cannot be run. We like to see the job being queued for when it comes back online. As soon as the machine is being turned on the job should be started. This is handy for quickly assign a job and you never have to look back to make groups/policies assigning everything just to make sure the job is being runned on a few devices.
Thanks
Wietse
Would like to see this too. Very handy for classrooms with workstations to quickly run a job or install specific software for example.
@theopenem_admin
Thanks, just found the login tracker policy. We will test this.
Wietse
Hello,
Large organizations have a lot of devices. It would be great if we could place devices in hierarchical groups graphically like this:
Rather than a long list with hundreds of thousands of machines.
The devices could be colored whether it's active or not. This could make it also easier to deploy jobs or actions (wake up etc.) to groups or machines.
Have a nice day.
Wietse
Hello,
We have noticed that user login history and process history is empty. Is there a way to fix this?
Regards,
Wietse