# Elastic Defend integration on Windows Servers influences results from system.process dataset **URL:** \ **Category:** Elastic Agent\ **Created:** [February 21, 2023, 3:22pm UTC](https://discuss.elastic.co/t/elastic-defend-integration-on-windows-servers-influences-results-from-system-process-dataset/326087 "2023-02-21T15:22:31Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![norgro2601](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/norgro2601/32/33292_2.png) [@norgro2601](https://discuss.elastic.co/u/norgro2601)\ **Post date:** [February 21, 2023, 3:22pm UTC](https://discuss.elastic.co/t/elastic-defend-integration-on-windows-servers-influences-results-from-system-process-dataset/326087/1 "2023-02-21T15:22:31Z")
I have added the Elastic Defend integration to Policies for Windows and Linux Servers today. After activation, the system.process dataset on the Windows servers doesn't report elastic-agent.exe as a running process any longer, while this is still OK on the Linux servers. As soon as I remove the integration from the Windows servers, elastic-agent.exe is reported as a running process again. The Elastic Agent is version 8.6.2 and the Elastic Defend integration is version 8.6.1. Is there a configuration setting necessary, which I haven't seen so far, or could this be a bug in the integration? Kind regards, Norbert ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [March 21, 2023, 3:22pm UTC](https://discuss.elastic.co/t/elastic-defend-integration-on-windows-servers-influences-results-from-system-process-dataset/326087/2 "2023-03-21T15:22:33Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.