Merge pull request #501 from Icinga:doc/iwkb_perf_lib_doc

Doc: Updates IWKB for perf lib errors

Author: LordHepipud

doc/knowledgebase/IWKB000008.md

@@ -18,10 +18,8 @@ The issue on this method is, that even while we only load the `Processor` Perfor
 
 ## Solution
 
-At the moment there is no solution available to resolve this issue. Permissions to these counters cannot be granted. Disabling these Performance Counter endpoints is not suitable as well, because it might break different applications and it is also **not** adviced to run the Icinga Agent or checks in `LocalSystem` context for security reasons.
+Permissions to these counters cannot be granted individually and disabling these is also not a suitable option. One way to resolve this problem, is to use [JEA Profiles](../130-JEA/01-JEA-Profiles.md) for monitoring or switch to the feature [Forward Checks to Internal API](../110-Installation/30-API-Check-Forwarder.md).
 
-Right now a workaround would be the experimental feature [Forward Checks to Internal API](../110-Installation/30-API-Check-Forwarder.md), which is not yet ready for production.
-
-As Performance Counter libraries are loaded during startup, they will only occur once you start the Icinga for Windows service with this daemon. Every single check executed afterwards will use Performance Counter libraries, but the current shell session has already loaded required components and therefor only access objects we want.
+As Performance Counter libraries are loaded during startup within the REST-Api, they will only occur once you start the Icinga for Windows service daemon. Every single check executed afterwards will use Performance Counter libraries, but the current shell session has already loaded required components and therefor only access objects we want.
 
 As a result, no additional errors or warnings are added to the EventLog.