Lot of files are created in C: drive(making the drive full) while monitoring Exchange Server via Powershell in APM
When powershell is used for monitoring Exchange server, the processing of commands is logged in some .psd1 files. This logging property is specified in "Local Group Policy Editor".
By default, logging is disabled. In case if the customer environment has those logging property enabled, then lot of files will be created in C: quickly making it full.
Resolution :
- Disable powershell logging by referring to the solution mentioned in this link, https://superuser.com/questions/979888/disable-windows-powershell-event-logging
- Delete all the log files once. No more log files should be created.
New to ADSelfService Plus?
Related Articles
Uninstrumented Block of Code - APM Insight
In the traces tab --> Slowest Method Calls and Count we show if you find Un-instrumented block of code the reason is as follows: Basically, What is un-instrumented block of code in APM Insight? By default, APM Insight agent monitors known frameworks ...Self monitor Applications Manager using APM Insight Java Agent
Applications Manager is built with Java, hence we can monitor it using APM Insight Java Agent to measure it's performance continuously, which can be very much useful. Setting up APM Insight Java Agent Follow the below steps to download and set up the ...How to rename an existing APM - Java agent application's monitor?
In Applications Manager's APM(Application Performance Monitoring) doesn't support renaming applications/monitors from the web client. However, the application name of an existing application instance can be renamed in the `apminsight.conf` file and ...Troubleshooting errors in Exchange Online (PowerShell Mode)
Prerequisites: Ensure that you have met all the prerequisites for the Microsoft 365 monitor. From Applications Manager version 16300 onwards, Microsoft 365 monitor will use Microsoft Graph API as the primary mode of data collection. We have migrated ...Troubleshooting Applications Manager Plugin database migration failure after service pack upgrade of OPM and APM plugin
When upgrading OpManager from version 12.6.xxx to 12.7.xxx and updating the APM Plugin to 1651x, particularly when using Postgresql as the backend database, an essential one-time migration occurs. This migration involves moving our backend Postgresql ...