Attempts to apply actions, like ReACL to the machine are ended up with FailedToQueue status.
On Demand Agent service is stopped or blocked from connecting to the backend. Also might be caused by DNS resolution issues.
To resolve the issue, please verify the following on the affected machine:
Open services.msc and verify that "On Demand..." service is up and running. If it's stopped, try to start it and monitor log files in the C:\Program Files (x86)\Quest\On Demand Migration Active Directory Agent\Files\ folder for agent_xxxxx.txt files
Agent should not log any errors, especially those, where it's unable to resolve the URL. Error like that usually means that there are connectivity or DNS issues, blocking agent service to communicate to the backend.
