# Packetbeat on Win2016 Core
**URL:** https://discuss.elastic.co/t/packetbeat-on-win2016-core/117370
**Category:** Beats
**Tags:** packetbeat
**Created:** [January 28, 2018, 1:22pm UTC](https://discuss.elastic.co/t/packetbeat-on-win2016-core/117370 "2018-01-28T13:22:11Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@antwan](https://discuss.elastic.co/u/antwan)
#### Post date: [January 28, 2018, 1:22pm UTC](https://discuss.elastic.co/t/packetbeat-on-win2016-core/117370/1 "2018-01-28T13:22:11Z")
Hey,
I am trying to deploy Packetbeat 6.1.2 on a Windows 2016 Standard Core using Ansible. I install WinPcap using the `win_chocolatey` module in Ansible, and then Packetbeat calling the supplied powershell-script. I use the default packetbeat.yml, with the exception of changing the `packet.interfaces.device` to either of my interfaces listed when I run `netsh interface ipv4 show interfaces`. I presume its the `Idx` value I should use? I get a non-descriptive error in powershell when I try `Start-Service packetbeat`.
No logs gets generated in `C:\ProgramData\packetbeat\logs`, the `packetbeat` folder does not even get created. In the Eventlog System I get 2 entries per attempt:
One timeout waiting for the packetbeat to connect, and one with a generic event about timely fashion.
Nothing exists outside this Windows host, but surely the service should start without valid output hosts?
---
### Author:  [@antwan](https://discuss.elastic.co/u/antwan)
#### Post date: [January 28, 2018, 2:29pm UTC](https://discuss.elastic.co/t/packetbeat-on-win2016-core/117370/2 "2018-01-28T14:29:53Z")
Tried the Windows 2016 with the whole GUI, and not the semi-GUI that exists in Core, and that gave me a "nice" dialog box stating I didn´t have a `wpcap.dll` when I tried `packetbeat.exe -e -d "*"`. After a manual`choco install winpcap --force` packetbeat spun up nicely.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [February 25, 2018, 2:30pm UTC](https://discuss.elastic.co/t/packetbeat-on-win2016-core/117370/3 "2018-02-25T14:30:00Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.