Minor changes are by default collapsed in the page history.
No changes
The page does not exist yet.
Failed to load changes
Version by on
Leave Collaboration
Are you sure you want to leave the realtime collaboration and continue editing alone? The changes you save while editing alone will lead to merge conflicts with the changes auto-saved by the realtime editing session.
Modifying the configuration files
The configuration directives are read during application startup. They are read again only if you upload a new configuration file to the system.
Normally, the configuration file is modified only in the BMC Defender Server File Integrity Monitor configuration tab. Consequently, listening port 55514 (CO-logmon) or listening port 55515 (CO-fmon) must be open to the agent. Uploading a configuration file automatically generates a new image file based on the changes to the file.
To force the agent to read its configuration file, you can remotely configure the agent by using the rfmconf.exe Windows program.
If the configuration file is directly modified on the managed system, the changes are not read until the next time CO-logman or CO-fmon restart, and no image file is generated. Therefore, next time the system starts, the programs are likely to report a large number of file additions, deletions, or modifications. In this case, you should regenerate the image file manually.
