Support Forum

The oneDrive script is very small and should not place any load on the agent.

When script runs, it test to see if a user is logged in which is a Automate function and it does not reach out to agent for this test.

So if user is not logged in then zero activity is sent to agent, including the is user logged in test. This makes a zero footprint on agent for OneDrive services.

If user is logged in then we test for and or write a small powershell script to agent then execute that script. The script reads onedrive data from registry and returns data to automate.

It should only execute on Windows agents. We have not added in ability to exclude agents or clients at this time. It has not been requested by anyone yet.

Thanks its not the load on agents.
We have a specific client that is going through some security "challenges", and they want to reduce powershell noise.
There are also quite a few clients that are break fix only, so dont particularly want to be spending time and energy on monitoring something that we not paid for.

On a separate note, what risk is there in the Onedrivelib.dll being replaced by a bad actor in github and gaining access to all agents?