Can't find what you're looking for? Access our previous PDF-based library.
6 min read
️ Updated Jun 25, 20261. Prerequisites to Audit SharePoint
The following are the prerequisites to add a SharePoint Server (any version) for auditing
Connectivity and accessibility to the instance of SQL Server, which is interlinked with SharePoint Server
Microsoft System CLR Types for SQL Server 2012
Microsoft SQL Server 2012 Management Objects
.NET Framework 4.6 should be installed on both the server to be monitored and the computer where software is installed.
NOTE: You can add a SharePoint Server in Lepide Data Security Platform for auditing only when you have installed Microsoft System CLR Types for SQL Server 2012 and Microsoft SQL Server 2012 Management Objects on the server computer running SharePoint. The setup files to install these two add-ons comes with the compressed setup file of the solution.
The required user rights to add SharePoint for auditing is listed in the Section entitled Add a SharePoint Component.
1.1 Install Microsoft CLR Types on SP Server
Follow the steps below to install Microsoft System CLR Types for SQL Server 2012:
Go to the server and browse the folder of the computer where the Lepide Data Security Platform is installed.
Open the Redist folder, which has different folders. x64 folder has the setup files for 64-bit Windows Server, and x86 contains the files for 32-bit Windows Server OS.
Open the required folder.
Copy these files to the SP Server and Run the setup file SQLSysClrTypes.msi to install Microsoft System CLR Types for SQL Server 2012.
If you are running the setup file after copying it to the Local File System, then the warning message does not appear.
Click Run. It shows Windows Installer.
Once Windows Installer is initialized, it shows the installation wizard.
Click Next. The next step displays the license agreement of Microsoft Corporation.
Read the license agreement carefully. The license and terms to install Microsoft CLR Types will be between you and Microsoft. If you agree, then click I accept the terms in the license agreement.
Click Next to proceed. The module is now ready to be installed.
Click Install to start the installation.
Once Microsoft System CLR Types is installed, the successful message appears in the wizard.
Click Finish to complete the process and to close the wizard.
1.2 Install SQL Management Objects on SP Server
Follow the steps below to install Microsoft SQL Server 2012 Management Objects Setup.
Go to the server and browse the folder of the computer where the Lepide Data Security Platform is installed.
Open Redist folder, which contains two sub-folders. x64 folder has the setup files for 64-bit Windows Server, and x86 contains the files for 32-bit Windows Server OS.
Open the required folder
Copy the files to the SP Server and Run the setup file SharedManagementObjects.msi to install SQL Management Objects.
Click Run. It shows Windows Installer.
Once Windows Installer is initialized, it shows the installation wizard.
Click Next. The next step displays the license agreement of Microsoft Corporation.
Read the license agreement carefully. The license to install Microsoft SQL Server 2012 Management Objects will be between you and Microsoft. If you agree, then click I accept the terms in the license agreement.
Click Next to proceed. The module is now ready to be installed.
Click Install to start the installation.
Once SQL Management Objects is installed, the successful message appears in the Wizard.
Click Finish to complete the process and to close the wizard.
Close Redist folder.
2. Required User Rights
To install and work with the Lepide Data Security Platform, you need to have appropriate rights to the system where it will be installed. Also, you need to have appropriate rights to access Active Directory, Exchange Server, SQL Server and SharePoint Server.
2.1 Service Rights
To run the service of Lepide Data Security Platform after installation, you can select any of the following objects or users.
A local system administrator
A member of Domain Admins Group
2.2 Local System Rights
The user should have the following permissions on the local computer where the solution is installed:
Full access permission on the drive where the Operating System is installed
Read/Write permissions in the Registry
Follow the steps below to assign these permissions.
Go to Control Panel and select User Accounts.
Select the User and select Change Account Type.
Make user an Administrator.
Click Save.
NOTE:
Steps mentioned above may vary depending on the Windows version installed on the system.
If the User Account does not exist on the system, create a new User Account with Administrative rights.
2.3 Required SQL Server Rights for Audit Database
The provided user to create or access a database for auditing logs should have a login with the assigned role of sysadmin in SQL Server.
If you are using Windows Authentication, then a login for the currently logged on Windows user should exist in SQL Server. Perform the following steps.
If such a user login does not exist already, then follow the steps below to create it.
Open SQL Server Management Studio.
Select SQL or Windows Authentication.
Enter the username and password of an SQL Server Administrator in the case of SQL authentication.
Click Connect.
In the left tree panel, go to Security → Logins.
Right click on Logins and select New Login.
Login - New wizard appears onscreen.
Enter the same login name as that of currently logged-on user, with which you are running Lepide Data Security Platform.
Switch to Server Roles and select sysAdmin.
Click OK.
If the user exists, but no such rights are assigned, then follow these steps to assign the required rights.
Open SQL Server Management Studio.
Select SQL or Windows Authentication.
Enter the username and password of an SQL Server Administrator in the case of SQL authentication.
Click Connect.
In the left tree panel, go to Security → Logins.
Expand Logins and select the required user.
Right-click on the user and select Properties.
Switch to Server Roles and select sysAdmin.
Click OK.
Go to the Status page, select Grant and Enabled.
Click OK.
3. Required Ports
The software uses the following ports for different purposes:
Lepide Data Security Platform uses the following ports for communication:
Port 389 and Port 636 for LDAP queries.
Port 445 for RPCSS (Remote Procedure Call Services)
Port 135 for communication to Event Logs
TCP/5985 (HTTP) and TCP/5986(HTTPS) for Remote PowerShell Communication
Default Port for SQL Server Communication. In most cases, the default port for SQL is 1433.
The Solution uses the following Microsoft functions, which uses different ports:
OpenEventLog, which uses Port 445 and Port 135
ReadEventLogt, which uses Port 445 and Port 135
AdsOpenObject, which uses Port 389 and Port 636
Lepide Data Security Platform Web Console uses Port 7778 (HTTP). You can change the Port Number.
Lepide Data Security Platform App uses Port 1051.