what exactly do the fireye logs say it is doing? that is the only way to determine what it is doing and therefore add the right exclusions.
Slowness on the console after starting FireEye
Following the documentation
I have the following exclusions set on the Primary server
But its is still slow... anything missing?
Sign in to comment
Sort by: Most helpful
Hi @Duchemin, Dominique ，
Thanks for your update. And I am looking forward to hearing the news of the problem resolution. If the problem has been solved, please share your solution in this post. It will make someone who has the similar issue easily find the answer.
We will check again as we have a case opened with FireEye Support and Microsoft to try to coordinate,
Still looking into it as the list of exceptions has been reviewed and completed...
The list of exceptions has been agreed between Microsoft Support & FireEye support.
An improvement has been seen but still the response time from the console has been degraded by the addition of FireEye. At this time I am looking for estimate response time got by Configuration Manager Clients...
- To open the console it is between 12 & 17 seconds.
- To add an item to a collection and get it available it is 15 seconds.
- To open SQL Management Studio on the SQL server it is between 15 & 20 seconds.
Also in the meantime we have been running perfmon on the drives... only the C: drive is showing peaks
for Avg. Disk Queue Length
and it is about the same values for Avg. Disk Write Queue Length 0 C:.
What to look for?