OpManager stops after the user logs off
Issue :
If the OpManager Service runs on a service account (This Account). It will NOT allow you to keep the Wrapper running after the user mentioned (This Account) logs off. It happens only in Windows 2003 R2.
Solution :
Change the Service account to (Local System Account).
OR
Add the below line in the wrapper.conf file and restart OpManager.
wrapper.java.additional.12=-Xrs
New to ADSelfService Plus?
Related Articles
Changing OpManager User Password
OpManager's user management feature helps network admins create specific user roles and associate them with the respective user profiles. You can also change their passwords. Kindly note that only an admin user or a user with full control privilege ...
Custom User Roles in OpManager
The level of access for users across different modules and add-ons in OpManager can be customized individually through Custom User Roles. The different levels of access that can be provided in OpManager for users through custom roles include: ...
Vulnerabilities in OpManager 12.0
VULNERABILITY DETAILS(found in build 12000) Vulnerability 1: Unrestricted File Upload: OpManager fails to validate or improperly validates files before uploading to the system. As a result an attacker might be able to upload arbitrary JSP file and ...
OpManager Scalability recommendations
If your organization is expanding and looking to introduce additional elements and monitors, follow this guide on scalability recommendations. We've outlined the maximum counts and limits for resources and metrics in OpManager to maintain optimal ...
MSSQL Transaction Logs Full
Steps to clear the Transaction logs. 1. Shutdown opmanager service. 2. Change the Recovery Model to Simple by following the steps below: Go to SQL server-->OpManagerDB properties-->Options-->Recovery Model-->Simple. (You can replace it with full mode ...