GFI Archiver makes heavy use of EWS.
Yes, this indeed generates a high amount of IIS logs. Depending on the size of the environment this can become quite large. This is normal behavior, but it can become problematic if this triggers disk space issues on the Microsoft Exchange side due to the logs.
The journal is also polled via EWS, but in comparison to UMPolling, this would probably not trigger that amount of logs.
Microsoft Exchange offers the EWS API (and this is the API to use in the future) and GFI Archiver just makes use of it.
Below are some options that can be used to limit the logging:
- On the GFI Archiver side:
- Disable UMPolling
- Edit EWSPollingSettings.xml and make UMpolling query less often (see tech manual)
- On the Microsoft Exchange / IIS side
- Place the logs on a drive that holds sufficient space
- Setup a scheduled script that zips and or moves away older IIS logs
- Create a new web site in IIS and place the EWS service in it. Disable logging only for this site. (This would allow logging of OWA access, but then NOT log EWS based access.)
- Disable logging on the IIS side completely