Home → LOGbinder for SP KB → How To

3. How To

• 3.1. How does LOGbinder for SharePoint detect log tampering?
• 3.2. How to reduce the number of audit events
• 3.3. Why are User ID's prefixed with "i:0#.w" in LOGbinder for SharePoint?
• 3.4. LOGbinder SP use of SQL Privileges
• 3.5. Workaround if LOGbinder for SharePoint is having SQL database issues
• 3.6. How To Set SPDataAccess on Large Number of Content Databases
• 3.7. Impact of Restricted Lookups
• 3.8. Can't connect to SQL database WSS_Content?
• 3.9. Default Audit Policy Options
• 3.10. LOGbinder for SharePoint Restricted Lookups Option
• 3.11. Audit log truncation and audit integrity
• 3.12. FIPS Mode and LOGbinder software
• 3.13. New technical updates posted and available for customers with current maintenance and support contracts - July 2015
• 3.14. “Run as Administrator” may be needed to initialize LOGbinder for SharePoint
• 3.15. Tech Tip: Manage the audit performance by tweaking the amount of excess information attached to the audit
• 3.16. Where to find information about LOGbinder events
• 3.17. You want to run audit reports in SharePoint but LOGbinder for SharePoint purges the audit log
• 3.18. Why There's No Event for List Item Views
• 3.19. How to change the LOGbinder service account password
• 3.20. Diagnostic logs – Use them and let them go
• 3.21. LOGbinder troubleshooting tip: Use the Diagnostic Logs
• 3.22. LOGbinder for SharePoint 6 Features
• 3.23. How to Audit an Individual Library or List in SharePoint
• 3.24. Recovery options for LOGbinder service
• 3.25. New Syslog Features in LOGbinder SP 4.0.5