Active Directory, Microsoft 365, and Exchange management and reporting
Hybrid AD, cloud, and file auditing; security; and compliance
Identity security with adaptive MFA, SSPR, and SSO
Reporting, auditing, and monitoring for hybrid Exchange and Skype
Active Directory, Microsoft 365, and Exchange backup and recovery
Hybrid AD, cloud, and file auditing; security; and compliance
SharePoint reporting and auditing
Microsoft 365 security
Cloud security monitoring and analytics
File auditing, data leak prevention, and data risk assessment
File security and storage analysis
Automated patching across multiple OSs and over 850+ third-party apps
Simplified third-party patch deployment via ConfigMgr and Intune
Seamless mobile device management from onboarding to retirement
Remote troubleshooting with integrated chat, voice, and video
Automated OS image creation and seamless role-based deployment
Prioritization-focused enterprise vulnerability management
App control and endpoint privilege management software
Data theft prevention with strict peripheral device control
Browser security with isolation, lockdown, and activity tracking
Sensitive data protection and compliance for endpoint devices
Real-time ransomware mitigation and file recovery for business continuity
Next-gen antivirus software for threat detection and breach prevention
Full-stack observability with AIOps and digital experience monitoring
AI-powered, all-in-one SaaS platform for observability and digital experience monitoring
Digital experience, application performance, and infrastructure monitoring
All-in-one vendor risk assessment tool to ensure domain security
Network, server, and storage performance monitoring
Bandwidth monitoring and traffic analysis
Network change and configuration management
Firewall rule, configuration, and log management
IP address and switch port management
Centralized IT alert management
Status pages for real-time status and incident communication
A cloud-native identity platform for workforce IAM
Full-stack service management for enterprises
IT asset management with an integrated CMDB
Unified endpoint management and security
Comprehensive mobile device management
Enterprise remote access
Automated multi-OS patch management
Full-stack monitoring for IT admins, DevOps, and SREs
Status pages for real-time status and incident communication
Cloud cost management for modern software teams
SaaS management platform to maximize ROI
Centralized IT alert management
Secure your IT infrastructure and prove compliance from the cloud
AI-powered unified analytics platform to correlate all IT data
An all-in-one DNS management service to keep your business online
Low-code application development platform
Remote support software
Collaborative project management
Agile project management
All-in-one collaboration tool for unified communication
Secure email hosting solution for businesses
All-in-one video conferencing solution for remote business meetings
All-in-one AR remote assistance software solution for remote collaboration.
Unified network monitoring and endpoint management for MSPs
Unified Active Directory management and reporting solution for MSPs
Unified SIEM solution for MSSPs
Log management and advanced threat intelligence for MSSPs
Complete privileged access security for enterprises
Privileged password management
Full-stack service management for MSPs
Upon starting Secondary/Failover server after completing failover configuration, the Secondary/Failover server will be connected to the database and will listen to the Primary server. However, the installation will not be started completely as the Primary is already up and running.
Following is the output obtained upon executing the nohup command from command line or viewing the wrapper.log file under <Applications Manager Home>/logs directory in Primary server:
INFO | jvm 1 | 2013/08/05 01:00:06 | Checking for the availablity of the Primary Server in the Database. Found an entry.
INFO | jvm 1 | 2013/08/05 01:00:06 |
INFO | jvm 1 | 2013/08/05 01:00:06 | Trying to connect to the Primary Server at 192.168.1.3
INFO | jvm 1 | 2013/08/05 01:00:06 |
INFO | jvm 1 | 2013/08/05 01:00:07 | Please wait ...
INFO | jvm 1 | 2013/08/05 01:00:08 | ....Connected
INFO | jvm 1 | 2013/08/05 01:00:08 |
INFO | jvm 1 | 2013/08/05 01:00:08 |
INFO | jvm 1 | 2013/08/05 01:00:08 | Starting ManageEngine Applications Manager Standby Server. The Modules will be started once it takes over as the Primary Server.
INFO | jvm 1 | 2013/08/05 01:00:08 |
INFO | jvm 1 | 2013/08/05 01:00:08 | Monitoring the Primary Server at 192.168.1.3
When Primary server goes down, secondary/failover server will start up completely and will act as the primary server. Email notifications will be triggered on occurrence of a failover where you have to correct the issues with the primary setup that is down. Once the issues are resolved and server is started, this acts as the secondary which will now listen for another failure.
Following is the output obtained in the upon executing the nohup command from command line or viewing the wrapper.log file under <Applications Manager Home>/logs directory in the currently-active Secondary server:
INFO | jvm 1 | 2013/08/05 01:09:47 | Monitoring the Primary Server at 192.168.1.3
INFO | jvm 1 | 2013/08/05 01:10:48 | Starting to do FailOver Tasks.
INFO | jvm 1 | 2013/08/05 01:11:08 | Process : AlertFE [ Started ]
INFO | jvm 1 | 2013/08/05 01:11:08 | Process : NmsMainFE [ Started ]
INFO | jvm 1 | 2013/08/05 01:11:08 |
INFO | jvm 1 | 2013/08/05 01:11:08 | Verifying connection with web server... verified
INFO | jvm 1 | 2013/08/05 01:11:08 |
INFO | jvm 1 | 2013/08/05 01:11:08 | Applications Manager started successfully.
INFO | jvm 1 | 2013/08/05 01:11:08 |
INFO | jvm 1 | 2013/08/05 01:11:08 | Please connect your client to the web server on port: 9095
INFO | jvm 1 | 2013/08/05 01:11:08 |
INFO | jvm 1 | 2013/08/05 01:11:09 | The new primary server is 192.168.1.4