Home → LOGbinder for SP KB → How To → LOGbinder for SharePoint 6 Features
3.22. LOGbinder for SharePoint 6 Features
In May 2016 Microsoft released SharePoint 2016 but due to a bug in Exchange 2016, we wanted to make sure that we performed very extensive testing of SharePoint auditing to make sure we didn’t discover any bugs. We also performed very stringent testing of LOGbinder for SharePoint to make sure that our software continues to meet and exceed our internal standards.
What is new in LOGbinder for SharePoint 2016?
- Support for SharePoint 2016 On-Premises
- New installer – Our new installer automates some of the prerequisites required during the installation process. Installation time is now just a couple of minutes.
- Improved service resilience – A few customers have reported to us that from time to time the LOGbinder service is stopped. The detailed service logs showed that delays between SharePoint and the farms’ SQL Server were causing timeouts. These timeouts were being reported by SharePoint and were long enough to negatively impact the LOGbinder service. Now the LOGbinder service will handle these interruptions with less impact.
- Weird username prefixes removal – Some customers were wondering why they are seeing weird characters prefixing usernames in the logs. You can find more info about it here. We have included an option to remove the claim type characters from the data.
- Site collection selection – Managing a handful of site collections is easy. Some customers though have thousands and thousands of site collections being monitor. Now you can use CTRL-A to select all site collections in the LOGbinder input.
These are just a few of the improvements in this release of LOGbinder for SharePoint.
Customers with current support and maintenance contracts can access the latest version at the link below. To upgrade to the latest version just run the installer on top of the previous version. No data or settings will be lost.