Bulk Enable & Disable CAPI2/Operational Logging
One of the biggest headaches to troubleshoot when working with customer deployments is certificates.
What is the CAPI2/Operational Log? CAPI2 stands for Cryptographic API. The CAPI2 log is located in event viewer under Application and Services Logs/Microsoft/CAPI2/Operational.
By default, Microsoft has this log disabled. This log will grow/overwrite itself extremely fast on a production server that relies on certificates.
During a recent Skype to Exchange troubleshooting effort Microsoft requested that we enable CAPI2 logging to identify why Exchange was throwing an error accepting Unified Messaging (UM) calls from a Skype Pool.
Due to the nature of this issue we had to enable CAPI2 logging on All production Exchange servers as we had no way to force Skype to connect to a specific server.
Note: I only turned this logging on my laptop for 15 seconds and already have over 300 events captured)
During a recent Skype to Exchange troubleshooting effort Microsoft requested that we enable CAPI2 logging to identify why Exchange was throwing an error accepting Unified Messaging (UM) calls from a Skype Pool.
Due to the nature of this issue we had to enable CAPI2 logging on All production Exchange servers as we had no way to force Skype to connect to a specific server.
Note: I only turned this logging on my laptop for 15 seconds and already have over 300 events captured)
I had to enable CAPI2 logging on almost 50 servers, reproduce our failed connection attempt, then disable the logs before they overwrote themselves.
Below is the script I used to set the log size to 20MB as well as enable or disable the logs in bulk
Below is the script I used to set the log size to 20MB as well as enable or disable the logs in bulk