ManageEngine ServiceDesk Plus -
configuration from scratch

You have just decided to deploy ManageEngine ServiceDesk Plus in your company. You receive the license, you have access to the admin panel - and now the question is: where do I start? In this article I walk you through every step of the configuration: from system requirements, through installation, all the way to setting up categories, SLAs, workflow automations, and Active Directory integration. The guide applies both to on-premise and Cloud deployments.

System requirements and installing ServiceDesk Plus

Before installation, check that your infrastructure meets the minimum requirements. ManageEngine SDP requirements differ by scale - for 5 technicians an entry-level server is enough; for 100+ technicians you need a robust setup.

Minimum hardware (on-premise)

• Up to 50 technicians: Windows Server 2016+ or Linux, 8 GB RAM, 4 vCPU, 100 GB SSD
• 51-100 technicians: 16 GB RAM, 8 vCPU, 200+ GB SSD
• 100+ technicians: 32+ GB RAM, 16 vCPU, dedicated database (SQL Server / PostgreSQL / Oracle), 500+ GB SSD
• Java: Java 11+ (installed with ManageEngine, but worth keeping recent)

Step by step: installation

1. Download ManageEngine SDP from the official ManageEngine site or contact a partner (Rotech Group) for a direct link to your version/edition.
2. Prepare the database - on-premise requires PostgreSQL or MSSQL. By default the installer uses the embedded H2 database (dev/test only, not for production). In production configure an external PostgreSQL or MSSQL database - this is mandatory.
3. Run the installer - EXE on Windows, .sh script on Linux. The wizard walks you through port configuration (8080 by default), install path, database choice, and admin password.
4. Right after installation: log in at localhost:8080 (or your IP) with admin/admin (change the password immediately), go to Admin → License Activation, and activate your license with the key you received.
5. Set up backups - Admin → Backup & Restore, configure automatic daily backups at 2 AM local time.

Configuring categories, subcategories, and request types

Categories are the foundation of help desk organization. If you define them poorly, users will file tickets under the wrong categories and you will spend time moving them. Before you start configuring, audit your existing tickets.

How to plan the category structure

• Main categories = IT areas: Hardware, Software, Network, Printer, Access, VPN, etc. Maximum 10-12 main categories.
• Subcategories = problem types: Under Hardware: "Monitor will not turn on", "Laptop will not boot", "No sound". Under Software: "Outlook will not open", "Excel freezes", "VLC will not play video".
• Too many categories = chaos. Rule: one main category plus a maximum of 3-5 subcategories per category.

Step by step in ServiceDesk Plus

1. Admin → Request Categories → New Category
2. Enter the name (e.g. "Hardware"), a description, and the technicians who will handle this category
3. Add subcategories: sub-categories → New Sub Category, e.g. "Laptop", "Monitor", "Printer"
4. For each category set "Item Type" - is this an Incident, Request, or Problem? Usually: Incident for current issues, Request for changes/services, Problem for deep analyses.
5. Set "Subcategory Mandatory" - does the user have to pick a subcategory? Yes - it forces precision.
6. Add Custom Fields if needed - for Hardware: "Type of Device", "Serial Number", "Warranty Status".

Setting SLAs and escalation rules

An SLA (Service Level Agreement) is a promise - e.g. "we will resolve critical problems in 4 hours, normal ones in 24 hours". Without an SLA there is no pressure on technicians; without pressure there is chaos.

Building the SLA matrix

In ServiceDesk Plus, SLA is defined as a matrix: Category × Priority = resolution time. Example:

Configuration in SDP

1. Admin → SLA Policies → New SLA
2. Set the name (e.g. "Standard SLA"), a description, and whether it applies to Incident or Request
3. Define the matrix: for each Category + Priority combination, enter time in hours and minutes
4. Set escalation: when the time expires, the system automatically moves the ticket status to "On Escalation" and sends an alert to the manager
5. Enable notifications: Admin → Notification Templates, configure an auto-email to the technician and customer when SLA is nearing its deadline (e.g. 30 minutes before timeout)

Pro tip: SLAs that make sense for your organization are not the same as for the company next door. If business requirements do not justify a 2-hour SLA for every incident, do not set one - that leads to team burnout with no visible benefit.

Automations - business rules step by step

Automation rules (Business Rules) are the heart of an effective help desk. Any manual operation you repeat more than 10 times a day should be automated.

Example rules to set up immediately

• Automatic ticket assignment to a team

  Rule: If category = Hardware AND priority = Critical → assign to the "Hardware Emergency" group. Rule: If category = Network → assign to the Network Team. Without this rule, all tickets land in a default queue and wait for manual assignment.

• Auto-set priority based on impact/urgency

  Rule: If impact = High (many people) AND urgency = High (immediate) → priority = Critical. If impact = Low (1 person) AND urgency = Low (can wait) → priority = Low. Users routinely flag everything red - this rule normalizes that.

• Auto-close tickets after 3 days of inactivity

  Rule: If status = On Hold AND no changes for 72 hours → change status to Closed → email the customer asking for confirmation. Prevents tickets sitting in limbo.

• Auto-escalate to a manager

  Rule: If status = On Escalation AND time remaining to resolve < 30 minutes → send an email to the Service Manager. The manager knows they have to act.

Business Rules configuration

1. Admin → Business Rules → New Business Rule
2. Set conditions: if X conditions are met (AND/OR logic)
3. Set actions: what happens when conditions are met (status change, assignment, email, custom field updates)
4. Test on a few tickets before rolling out globally

Active Directory and email integration

Without AD integration your help desk works offline - new users have to be added manually, password reset is ineffective, and group sync is wishful thinking. AD integration is mandatory.

Active Directory integration (LDAP/AD)

1. Admin → LDAP Settings
2. Enter AD server data:
   • Server Address: IP or FQDN of the domain controller (e.g. dc.company.local)
   • Base DN: cn=Users,dc=company,dc=local (for your domain)
   • Username: DOMAIN\user (a service account with AD access)
   • Password: that account's password
3. Click Test Connection - if it succeeds, OK. If not, check the firewall and ports 389 (LDAP) or 636 (LDAPS).
4. Set up automatic sync: Admin → LDAP Sync, every hour (or daily at night).
5. Choose which AD attributes to sync: mail, telephoneNumber, department, manager. Do not sync everything - it depends on your AD.

Email integration (IMAP/POP3 → ManageEngine)

If you want emails sent to helpdesk@company.com to automatically create tickets in SDP, you need mailbox integration.

1. Admin → Email Notification / Email to Ticket (depends on version)
2. Add a mailbox:
   • Type: IMAP (Exchange / Office 365) or POP3 (basic mail)
   • Server: imap.office365.com (for M365) or your server
   • Port: 993 (IMAP+SSL) or 110 (POP3)
   • Username: helpdesk@company.com
   • Password: application password (for M365)
3. Set polling frequency: check the mailbox every 5 minutes, each new email = a new ticket
4. Test: send a test email to helpdesk@company.com, wait 5 minutes, check that a ticket appeared.