Document Management Server Configuration
AccelOps supports these document management servers for discovery and monitoring.
Microsoft SharePoint Configuration
Microsoft SharePoint Configuration
What is Discovered and Monitored
Event Types
Rules
Reports
Configuration
Installing and Configuring LOGbinder SP Agent
WMI
Creating a Generic User Who Does Not Belong to the Local Administrator Group
Creating a User Who Belongs to the Domain Administrator Group
What is Discovered and Monitored
Protocol | Information discovered | Metrics/Logs collected | Used for |
WMI | SharePoint logs – Audit trail integrity, Access control changes, Document updates, List updates, Container object updates, Object changes, Object Import/Exports, Document views, Information Management Policy changes | Log analysis and compliance |
Event Types
In CMDB > Event Types, search for “sharepoint” in the Description column to see the event types associated with this device.
Rules
There are no predefined rules for this device.
Reports
In Analytics > Reports, search for “sharepoint” in the Name column to see the reports associated with this application or device.
Configuration
Microsoft SharePoint logs are supported via LOGbinder SP agent from Monterey Technology group. The agent needs to be installed on the SharePoint server. Configure the agent to write logs to Windows Security log. AccelOps simply reads the logs from windows security logs via WMI and categorizes the SharePoint specific events and parses SharePoint specific attributes.
Installing and Configuring LOGbinder SP Agent
LOGbinder Configuration web link – remember to configure LOGbinder SP agent to write to Windows security log
LOGbinder SP getting started document – remember to configure LOGbinder SP agent to write to Windows security log
WMI
Configuring WMI on your device so AccelOps can discover and monitor it requires you to create a user who has access to WMI objects on the device. There are two ways to do this:
Creating a Generic User Who Does Not Belong to the Local Administrator Group
Creating a User Who Belongs to the Domain Administrator Group
Creating a Generic User Who Does Not Belong to the Local Administrator Group
Log in to the machine you want to monitor with an administrator account.
Enable Remote WMI Requests by Adding a Monitoring Account to the Distributed COM Users Group and the Performance Monitor Users Group
- Go to Start > Control Panel > Administrative Tools > Computer Management > Local Users and Groups.
- Right-click Users and select Add User.
- Create a user.
- Go to Groups, right-click Distributed COM Users, and then click Add to group.
- In the Distributed COM Users Properties dialog, click Add.
- Find the user you created, and then click OK.
This is the account you will need to use in setting up the Performance Monitor Users group permissions.
- Click OK in the Distributed COM Users Properties dialog, and then close the Computer Management dialog.
- Repeat steps 4 through 7 for the Performance Monitor Users group. Enable DCOM Permissions for the Monitoring Account
- Go to Start > Control Panel > Administrative Tools > Component Services.
- Right-click My Computer, and then Properties.
- Select the COM Security tab, and then under Access Permissions, click Edit Limits.
- Make sure that the Distributed COM Users group and the Performance Monitor Users group have Local Access and Remote Access set to
- Click OK.
- Under Access Permissions, click EditDefault.
- Make sure that the Distributed COM Users group and the Performance Monitor Users group have Local Access and Remote Access set to
- Click
- Under Launch and Activation Permissions, click Edit Limits.
- Make sure that the Distributed COM Users group and the Performance Monitor Users group have the permissions Allow for Local Launch, Remote Launch, Local Activation, and Remote Activation.
- Click OK.
- Under Launch and Activation Permissions, click Edit Defaults.
- Make sure that the Distributed COM Users group and the Performance Monitor Users group have the permissions Allow for Local Launch, Remote Launch, Local Activation, and Remote Activation.
See the sections on Enabling WMI Privileges and Allowing WMI Access through the Windows Firewall in the Domain Admin User set up instructions for the remaining steps to configure WMI.
Creating a User Who Belongs to the Domain Administrator Group
Log in to the Domain Controller with an administrator account.
Enable remote WMI requests by Adding a Monitoring Account to the Domain Administrators Group
- Go to Start > Control Pane > Administrative Tools > Active Directory Users and Computers > Users.
- Right-click Users and select Add User.
- Create a user for the @accelops.com domain.
For example, YJTEST@accelops.com.
- Go to Groups, right-click Administrators, and then click Add to Group.
- In the Domain Admins Properties dialog, select the Members tab, and then click Add.
- For Enter the object names to select, enter the user you created in step 3.
- Click OK to close the Domain Admins Properties dialog.
- Click OK.
Enable the Monitoring Account to Access the Monitored Device
Log in to the machine you want to monitor with an administrator account. Enable DCOM Permissions for the Monitoring Account
- Go to Start > Control Panel > Administrative Tools > Component Services.
- Right-click My Computer, and then select Properties.
- Select the Com Security tab, and then under Access Permissions, click Edit Limits.
- Find the user you created for the monitoring account, and make sure that user has the permission Allow for both Local Access and Re mote Access.
- Click OK.
- In the Com Security tab, under Access Permissions, click Edit Defaults.
- Find the user you created for the monitoring account, and make sure that user has the permission Allow for both Local Access and Re mote Access.
- Click OK.
- In the Com Security tab, under Launch and Activation Permissions, click Edit Limits.
- Find the user you created for the monitoring account, and make sure that user has the permission Allow for Local Launch, Remote Launch, Local Activation, and Remote Activation.
- In the Com Security tab, under Launch and Activation Permissions, click Edit Defaults.
- Find the user you created for the monitoring account, and make sure that user has the permission Allow for Local Launch, Remote Launch, Local Activation, and Remote Activation.
Enable Account Privileges in WMI
The monitoring account you created must have access to the namespace and sub-namespaces of the monitored device.
- Go to Start > Control Panel > Administrative Tools > Computer Management > Services and Applications.
- Select WMI Control, and then right-click and select Properties.
- Select the Security
- Expand the Root directory and select CIMV2.
- Click Security.
- Find the user you created for the monitoring account, and make sure that user has the permission Allow for Enable Account and Remot e Enable.
- Click Advanced.
- Select the user you created for the monitoring account, and then click Edit.
- In the Apply onto menu, select This namespace and subnamespaces.
- Click OK to close the Permission Entry for CIMV2 dialog.
- Click OK to close the Advanced Security Settings for CIMV2 dialog.
- In the left-hand navigation, under Services and Applications, select Services.
- Select Windows Management Instrumentation, and then click Restart. Allow WMI to Connect Through the Windows Firewall (Windows 2003)
- In the Start menu, select Run.
- Run msc.
- Go to Local Computer Policy > Computer Configuration > Administrative Templates > Network > Network Connections > Windows Firewall.
- Select Domain Profile or Standard Profile depending on whether the device you want to monitor is in the domain or not.
- Select Windows Firewall: Allow remote administration exception.
- Run exe and enter these commands:
- Restart the server.
Allow WMI through Windows Firewall (Windows Server 2008, 2012)
- Go to Control Panel > Windows Firewall.
- In the left-hand navigation, click Allow a program or feature through Windows Firewall.
- Select Windows Management Instrumentation, and the click OK.