By default, the ODM Active Directory Device Agent checks in with the ODMAD back-end infrastructure every two minutes looking for new jobs via the connectionless UDP protocol. UDP is a light and fast protocol, but there is no way to validate a successful connection was made via UDP. For this reason, the ODM Active Directory Device Agent will also check in every 4 hours using the TCP protocol, which is able to be validated. This verified TCP connection that occurs every 4 hours is then what is used to update the "Last Agent Contact" column in the GUI.
The ODM Active Directory device agent is able to pick up new Actions, Tasks or jobs using either connection method. As long as device is online and the "Agent Last Contact" is reasonably close to 4 hours, then the agent should really be checking in every 2 minutes.
If you find that your devices are only checking in every 4 hours, then ensure that UDP connections are allowed from the devices to the endpoint for your ODM Organization region:
US - https://us.odmad.quest-on-demand.com/
EU - https://eu.odmad.quest-on-demand.com/
CA - https://ca.odmad.quest-on-demand.com/
AU - https://au.odmad.quest-on-demand.com/
UK - https://uk.odmad.quest-on-demand.com/
You can check the ODMAD Device Agent logs in the following location for clues to as to why the agent is not able to communicate with the ODMAD portal:
C:\Program Files (x86)\Quest\On Demand Migration Active Directory Agent\Files
