upstream/icinga-powershell-framework
1
0
Fork 0
mirror of https://github.com/Icinga/icinga-powershell-framework.git synced 2025-12-20 23:00:35 -05:00
Code Issues Projects Releases Packages Wiki Activity Actions

Fix docs for Icinga homepage

Browse source
This commit is contained in:
Lord Hepipud 2021-06-02 13:06:49 +02:00
parent d59ef8a297
commit 4c07ecd399
2 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
doc/frameworkusage/06-Update-Framework-And-Components.md
View file

@ -4,7 +4,7 @@ Icinga for Windows ships with a bunch of Cmdlets, allowing users to manage the e
## Updating Icinga PowerShell Framework
To update the Framework it is not required to run the [installation process](..\02-Installation.md) again. The Framework ships with a native command for this and is recommended to use, as this allows you to keep your current configuration and cache files. The command is `Install-IcingaFrameworkUpdate`.
To update the Framework it is not required to run the [installation process](../02-Installation.md) again. The Framework ships with a native command for this and is recommended to use, as this allows you to keep your current configuration and cache files. The command is `Install-IcingaFrameworkUpdate`.
### Interactive Update

2
doc/knowledgebase/IWKB000008.md
View file

@ -20,7 +20,7 @@ The issue on this method is, that even while we only load the `Processor` Perfor
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.
Right now a workaround would be the experimental feature [Forward Checks to Internal API](..\experimental\01-Forward-checks-to-internal-API.md), which is not yet ready for production.
Right now a workaround would be the experimental feature [Forward Checks to Internal API](../experimental/01-Forward-checks-to-internal-API.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.