FAQs > Difference between MSP Center Plus and OpManger MSP

Difference between MSP Center Plus and OpManger MSP

Tags:  

Difference between MSP Center Plus and OpManager MSP
The new OpManager MSP version 7 is renamed as MSP Center Plus [current build: 7002] and has more features included. 

MSP Center Plus
OpManager MSP
Agent based Desktop Management module providing asset, patch management, windows configuration and software deployment.Not available.
Enhanced option to switch between desktop management/helpdesk modules.
Not that much efficient when compared to the one in MSP Center Plus.
Provides Professional Service Automation.
Not possible.
Provides Service Level Agreements.
Not possible.
Reports on Active Directory.
Not possible.
WMI based MSSQL monitoring.
Not possible.
Schedule Custom reports.
Not possible.
Single MySQL instance - all the MSP modules will share the single MySQL resource. Easy to backup and restrore.
Multiple MySQL instances. 
Supports MySQL 5.0
Supports only 4.0
Option to use external mail services to send notifications [using Secure Mode].
Not possible.
Gigabit interface support.
Not available.
Disable status poll on specific switch ports.
Not possible.
Integration with NetFlow Analyzer.
Not possible.
Improved Alarm Management.Not that much efficient when compared to the one in MSP Center Plus.
Enhanced Rebranding settings.Not that much efficient when compared to the one in MSP Center Plus.


Apart from the above features, also some major and minor bugs are fixed. They are:

Bug fixes for 7001:
  • Unnecessary event log generation in agent installed machines.
  • Change password option provided for technicians directly logging into helpdesk.
  • Support for running mysql database in a seperate machine.
  • Option to alert MSP administrators about the health of the MSP Central/Probe - Alerts are generated whenever there is a problem in probe polling or data processing in the central side.
  • Maps UI error in case of shared probe.
  • Probe/Central synchronize issue in Rediscovery interface operation.
  • Interfaces remaining in unmanaged state after a device unmanage/manage operation is fixed.

Bug fixes for 6005:
  • Remote Control black screen issue when the machine is in logged off/locked state.
  • Routers not showing the unnumbered interfaces.
  • Thread lock issue in CLI datacollection.
  • Accenuated characters in helpdesk while showing other language characters.
  • Could not open attachments in helpdesk.
  • Interface Utilization graphs showing wrong unit.
  • Threshold clear alarms getting notified even if the notification profile is not configured to do so.
  • Customer list not populated in schedule report UI for a newly created admin user.
  • Vendor specific cisco monitors could not be disassociated through QCW.
  • Add windows service monitor from probe not reflected in central.
  • Interface Utilization value showing wrongly as 100%.
  • Router Memory Utilization report not showing any value in schedule reports.
  • Event log monitoring not working when central installed in a linux machine.
  • Maps UI showing other customer devices when logged in as a customer user.
  • Data not shown in the central UI for monitors added in bulk through QCW in central.
  • Varbind converted as meaningful information in Alert message.
  • Performance enhancements in Trap processor creation through load from mib option. 
  • Traps not listed in load from mib option.
  • Add windows service monitor from probe not reflected in central.
  • Single series custom report not working in cases of multiple instances for the monitor.
  • Custom report not showing free/used disk space snmp monitor data.
 




 RSS of this page

rtttrrb