# How do large organizations manage beats deployment?

**URL:** <https://discuss.elastic.co/t/how-do-large-organizations-manage-beats-deployment/51044>\
**Category:** Beats\
**Created:** [May 26, 2016, 10:33am UTC](https://discuss.elastic.co/t/how-do-large-organizations-manage-beats-deployment/51044 "2016-05-26T10:33:42Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![fetchmelogs](https://avatars.discourse-cdn.com/v4/letter/f/c2a13f/32.png) [@fetchmelogs](https://discuss.elastic.co/u/fetchmelogs)\
**Post date:** [May 26, 2016, 10:33am UTC](https://discuss.elastic.co/t/how-do-large-organizations-manage-beats-deployment/51044/1 "2016-05-26T10:33:42Z")

</div>

Suppose I had to deploy Winlogbeat to 100 Windows servers and 1000 Windows workstations ; what is the best way to proceed with deploying winlogbeat to all these end-points?

Suppose I had to make a change to the config file on a section of the servers; what are some options available to push these changes?

Has someone achieved this using Active Directory? SCCM?

Just looking for options on the best way to proceed.

Thank you.

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [May 26, 2016, 9:43pm UTC](https://discuss.elastic.co/t/how-do-large-organizations-manage-beats-deployment/51044/2 "2016-05-26T21:43:04Z")

</div>

Any sort of automation. - puppet, chef, ansible, whatever the Windows specific one it.  
AD might do it.

---

<div class="post-metadata">

**Author:** ![ruflin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ruflin/32/3116_2.png) [@ruflin](https://discuss.elastic.co/u/ruflin)\
**Post date:** [May 30, 2016, 8:26am UTC](https://discuss.elastic.co/t/how-do-large-organizations-manage-beats-deployment/51044/3 "2016-05-30T08:26:52Z")

</div>

In addition, have a look at the issue here: [https://github.com/elastic/beats/issues/464](https://github.com/elastic/beats/issues/464) We plan in the future to offer some centralised config management (not implemented yet). For deployment you will still need one of the automation tools recommended by @warkolm

---

<div class="post-metadata">

**Author:** ![fetchmelogs](https://avatars.discourse-cdn.com/v4/letter/f/c2a13f/32.png) [@fetchmelogs](https://discuss.elastic.co/u/fetchmelogs)\
**Post date:** [June 3, 2016, 12:35pm UTC](https://discuss.elastic.co/t/how-do-large-organizations-manage-beats-deployment/51044/4 "2016-06-03T12:35:11Z")

</div>

This would be awesome ! Thanks for the link. Cheers.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 5, 2017, 9:51pm UTC](https://discuss.elastic.co/t/how-do-large-organizations-manage-beats-deployment/51044/5 "2017-07-05T21:51:18Z")

</div>