Voltar
-
Título
Device: Change Polling Interval for Workstation Agents -
Descrição
Is there any way to change the polling interval for all workstations from the default of 4 hours to something like 15 minutes? We are using ODMAD, the cloud based version. 4 hours is just too long to instruct users to wait for their workstation to be migrated. I know that I can update the registry manually on a workstation, but it always reverts back to 4 hours. How can I set this to be 15 minutes consistently? -
Resolução
This is working as designed, where the interval is reset, or this would cause issues with SQL traffic.
How do I adjust the agent polling interval?
In Active Directory, unlike in Active Directory Pro, the agent polling interval is not end user adjustable. The polling interval is every two minutes over UDP and every four hours over TCP. Should this amount of network traffic be an issue contact Support to investigate reducing the polling interval. Note that reducing the polling interval will cause queued migration actions to take longer to be picked up by the agents.
How to temporarily modify the polling interval
When you have the agent deployed in mass in production, the agent will start communicate with the back-end API and register itself. It does at the interval of 4 hours. Once it is registered, it will use the 120 seconds polling interval to retrieve Jobs
for lab deployments (NOT Suggested for Prod) you can stop the agent service, modify the registry value PollIntervalSeconds
ODM: HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Quest\ODM_AD
P3565: HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Binary Tree\P365ADAgent
You can set it to 120 seconds, and start the service, it will perform its registration attempt then the registry setting will be reset back to its default values.