Running Monitoring Agent for Microsoft SharePoint Server by a non-admin user
You can use local security policies to run the Monitoring Agent for Microsoft SharePoint Server as a non-administrator user.
About this task
A combination of following two local security policies works to run the Microsoft
SharePoint Server agent by a non-administrator-user:
- Debug programs
- Log on as a service
Procedure
- Go to TEMA and change the Microsoft SharePoint Server agent startup with non-administrator user.
- Add a non-administrator user under the Registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server directory and give read access to it.
- Add non-administrator user under Registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions and give read access to it.
- Add non-administrator user manually under Registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\16.0\Secure\ and give read access to it.
- Add non-administrator user under Registry key HKEY_LOCAL_MACHINE\SOFTWARE\IBMMonitoring directory and give full permissions to it.
- Add non-administrator user under Registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib directory and give read access to it.
- Add non-administrator user in SharePoint Agent installation folder. For example, C:\IBM\APM and give full permissions to it.
- Run the secpol.msc command in startmenu to open the Local Security Policy.
- Add non-administrator user in Local Security Policy. For more information, see Local Security Policy permissions.
- Add non-administrator user in the SQL Server Login user group. The user must have sysadmin SQL Server role permissions on the SQL Server.
- Restart the Microsoft SharePoint Server agent.
- Check Microsoft SharePoint Server agent status and verify the data on IBM Cloud Application Management portal.
-
The following attribute groups show data for users who are members of the Administrators
group:
- Availability