In Cisco MeetingPlace Web server versions 5.2.x and earlier, the logs that Windows Internet Information Services (IIS) generate continue to accumulate if unchecked. These logs can consume the available space on the partition to which they are published. This accumulation eventually leads to an Operating System (OS) crash. This crash results from a lack of space for the paging file or other critical OS components.
At this time, there is no native Windows application to overwrite or purge these logs. In Cisco MeetingPlace Web server versions 5.3 and later, this functionality is automated in the product. One month of IIS logs are kept.
These are additional recommendations for how to manage the log files:
If you have a network directory or non-root partition to which you can post the log files, Cisco recommends you do so in order to avoid OS issues.
Regardless of their location, Cisco recommends that you purge the log files every quarter or sooner, based upon usage and disk size. Cisco advises that you keep log files for at least one month to help debug.
Use the Windows scheduled task utility to run the batch file, to automatically purge IIS logs on a regular basis.
We recently upgraded from Unity Connection 11.5 to 12.5. I'm used to having to manually add the user's email address to their notification device after I create their mailbox, but since the upgrade their notification schedules have all been blank and they...
Dear Experts, I have configured the helpdesk user using RANK but I am facing one issue:After configuring user rank, the helpdesk user is not able to assign end-user in Users Associated with Line phone line setting. for example, a...
Agents sometimes cannot open the web browsers to access the finesse desktop. The agent's logout reason was agent initiated and connection failure. Their agents often connect failing the server. The reason code is a connection failure. Which logs do I...