Feature request - heartbeat step in deployment


1 comment

  • Patrick Pierce

    Would be a good idea. Could setup a workaround with schedules, heartbeats and scan.

    Set a schedule to do the first part, scan the device at the end of deployment to place in a collection. Set a second schedule linked to the collection on heartbeat. That should detect computers in collection (if you have it set to an AD OU for computer_configuration or something) that did stage 1 of deployment, reboot, and still need stage 2.

    I usually log back into the machine and it will reconnect. Only do a few devices at a time, so this works for me. If I had more, I would do the schedules.

    Comment actions Permalink

Please sign in to leave a comment.