# Deployment improvement - MSI package

**URL:** <https://discuss.elastic.co/t/deployment-improvement-msi-package/203541>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [October 15, 2019, 12:45am UTC](https://discuss.elastic.co/t/deployment-improvement-msi-package/203541 "2019-10-15T00:45:38Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![danielsnelling](https://avatars.discourse-cdn.com/v4/letter/d/76d3ee/32.png) [@danielsnelling](https://discuss.elastic.co/u/danielsnelling)\
**Post date:** [October 15, 2019, 12:45am UTC](https://discuss.elastic.co/t/deployment-improvement-msi-package/203541/1 "2019-10-15T00:45:38Z")

</div>

Hi, I'm in the process of adding Filebeat (and Metricbeat) to hundreds of servers that we want to retrieve logs from.  
These servers are not all config managed using tools like ansible or puppet, so manual deployment is the only option.

I'd like to suggest the below:

- For Windows Servers, a MSI package is built (I'm currently having to make my own)
- Consolidate the multiple Beats into WinBeat and LinuxBeat
- Enable Central Management for all Beats
- Enable configuration of all settings through Central Management (like adding tags)
- Create a long-lived token (like 30 days long) for deployment of central management. This could be passed in through MSI package parameter during install. Having to deploy each Beat with the once-only token is very slow and manual

Otherwise I'm very happy with the product so far and would love to see improvements to help us poor sys admins 🙂

---

<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:** [November 12, 2019, 12:45am UTC](https://discuss.elastic.co/t/deployment-improvement-msi-package/203541/2 "2019-11-12T00:45:49Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.