OpManager stops after the user logs off

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

                      • 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 ...
                      • 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 ...
                      • Alarm severity levels in OpManager

                        OpManager has four different severity levels for the alarms. Severity levels of device down alarms (availability monitoring) are already predefined. Here is the list with the severity and the events which will trigger the alarms with these severity : ...
                      • Upgrading OpManager

                      • Integrating Whatsapp with OpManager