# 7.14 - Windows agent deployed with Fleet, but not sending data

**URL:** <https://discuss.elastic.co/t/7-14-windows-agent-deployed-with-fleet-but-not-sending-data/281347>\
**Category:** Elastic Security\
**Tags:** fleet\
**Created:** [August 13, 2021, 12:03pm UTC](https://discuss.elastic.co/t/7-14-windows-agent-deployed-with-fleet-but-not-sending-data/281347 "2021-08-13T12:03:13Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![blaker](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/blaker/32/65621_2.png) [@blaker](https://discuss.elastic.co/u/blaker)\
**Post date:** [August 13, 2021, 12:48pm UTC](https://discuss.elastic.co/t/7-14-windows-agent-deployed-with-fleet-but-not-sending-data/281347/2 "2021-08-13T12:48:35Z")

</div>

The issue is that using `--insecure` only allow Elastic Agent to communicate with Fleet Server insecurely. It still takes the settings from the policy to communicate with Elasticsearch. You need to modify the output settings inside the Fleet UI in Kibana.

> **[Fleet UI settings | Fleet User Guide \[7.14\] | Elastic](https://www.elastic.co/guide/en/fleet/current/fleet-settings.html)**

You will want to add the following in the `Elasticsearch output configuration (YAML)` block:

```auto
ssl.verification_mode: none

```

---

_[View the full topic](https://discuss.elastic.co/t/7-14-windows-agent-deployed-with-fleet-but-not-sending-data/281347)._