Some links to get you started:
Really good website about computer security, very well explained:
Some links to get you started:
Really good website about computer security, very well explained:
A while ago we received the following questions from one of our users:
My name is .. from the .. GmbH in Germany. I have two questions about your program (LimagitoX):
1. Is it possible to Change the Event-ID at the Event Viewer? We want to monitor this Event with our Monitoring System. Our Idea is when an Event comes in with “On Success” it should be have another Event-ID as “On Error”.
2. Our Second question / problem we get following Event Description:
The description for Event ID 0 from source LimagitoX.exe cannot be found. Either the component that raises this event is not installed on your
local computer or the installation is corrupted. You can install or repair the component on the local computer. If the event originated on another
computer, the display information had to be saved with the event.Is it possible to change this description or is this an mistake from your program? (the red labeled text)
Thanks for your help!
So we did what he asked and the result is available starting from version v11.12.12.0.
We’ve added the following Id’s and Categories to make it much more suited when using external monitoring tools.
We also had to add an extra dll and a registry entry to get rid of the red labeled text. The installer will handle this for you.
Best Regards,
Limagito Team
We got the following question recently:
hello, i am currently running 10.206.20.0. i have a rule that move file to an external ftp destination and also a unc path. if the ftp destination is not available the rule fails to move the file to it but keeps trying to send to the unc path. these means that the same file is sent many times to the unc destination. this keeps happening until the ftp site come back. is there a way to configure the rule to stop this behaviour? thanks robert
Our reply: Please enable ‘Destination Memory’ in your Function Setup.
This option will solve the issue because our file mover will remember which destination failed and will not move the file to the destination(s) that was(were) successful.
The feedback afterwards from robert was even better.