Add to the installer the possibility to define a planified task

Agent 2.0.x seems suffer some memory problems.
He can take about 1 Go of ram memory instead of some Ko.

Could you add a feature to installer to use a planified task instead of a service, as the unix installer.
Or create a task that restart service every week to reduce is impact...

Update: I talk about agent execution (daemon or task scheduling)... in my case i was obliged to deployed on all my windows server a planified task to restart agent every week. This solved problems of lake of memory of my servers.