The Windows agent installation is a little confusing. You download the zip and extract it to Program Files\elastic-agent. When you run the command to install the agent service and get it talking with Fleet, a new but nearly identical directory structure is created under Program Files\Elastic\Agent. The service runs from this directory. What about Program Files\elastic-agent--can the original download be deleted?
In the new directory structure, the current elastic-agent.yml can't be read, but a backup copy (.bak) can. Is this by design--to keep people out b/c it is something downloaded by Fleet?
With Azure Log Analytics (formerly OMS), Microsoft Monitoring Agents can home to multiple workspaces. Will Elastic Agent be able to do something similar, i.e. report to multiple Fleets? Would be great for testing.
If there's advanced documentation for Fleet/Elastic Agent, please point me to it. I will need to know this as well as SCOM and Azure Monitor/Log Analytics