Installation
This installation guide describes how to install, set up, and upgrade manage.ID on your device.
manage.ID automatically detects the language configured in your operating system. The following languages are supported:
- English
- German
- French
- Polish
If your operating system uses a language not listed above, manage.ID defaults to English. You can change the language at any time in your profile settings.
1 - System Requirements
All hardware and software requirements necessary for installing manage.ID are listed here.
Hardware Requirements
The resources manage.ID needs depend mainly on two factors:
- the number of printers and other devices (scanners, I/O modules) connected to manage.ID
- the number of print jobs manage.ID processes
Choose the installation size that matches the number of devices you plan to connect.
Dedicated server
The values below apply to a server that runs only manage.ID. If other software runs on the same server, it takes resources away from manage.ID. In this case, add the resources that the other software needs on top of the values below.
- CPU: 4 cores
- RAM: 16 GB
- Disk space: 100 GB SSD
- CPU: 8 cores
- RAM: 32 GB
- Disk space: 250 GB SSD
- CPU: 16 cores
- RAM: 64 GB
- Disk space: 500 GB NVMe SSD
Print volume: If you expect a high print volume (more than approx. 1,000 print jobs per hour) or want to keep printer logs for a long time, choose the next larger installation size.
Operating system: Windows Server 2022 or Windows Server 2025 (x64)
Disk Space
manage.ID stores all print jobs, printer logs and logistic units in its database. The database grows continuously during production. Also plan disk space for:
- Backups: Keep enough free space for several backups. Each backup is roughly as large as the database.
- Log files: With many devices and a high print volume, log files can grow by more than 1 GB per day.
We recommend storing backups on a separate disk from the database.
Network
A network connection of 1 Gbit/s is sufficient. A low latency between the manage.ID server and the printers is more important than a high bandwidth.
Software Requirements
You must have Local Administrator rights on the device where you install manage.ID.
The manage.ID installer installs all required runtime components, including Java (Amazon Corretto) and the database (PostgreSQL). You do not need to install them yourself.
Supported Browsers
Users access manage.ID through a web browser. The following browsers are supported:
- Google Chrome 117 or newer
- Microsoft Edge 117 or newer
- Mozilla Firefox 121 or newer (Firefox ESR 128 or newer)
Internet Explorer is not supported.
Required Open Ports
manage.ID consists of several software components. Most of them only communicate with each other on the manage.ID server. Only the following ports must be reachable from other devices in your network. Ensure these ports are open in your firewall before installing:
| Port | Component | Required |
|---|
80 / 443 | Web application and Web API (HTTP / HTTPS) | Always. All users access manage.ID through this port. External systems (ERP, MES) also call the manage.ID Web API through this port. |
2000, 6100–6105 | Scanner (incoming connections from scanners to the manage.ID server) | Only if scanners connect to manage.ID over the network |
In addition, manage.ID establishes outgoing connections to your devices. Ensure that your firewall allows these connections from the manage.ID server to the devices. The port is configured per device in manage.ID. The following table lists the default ports:
| Port | Device |
|---|
9100 | Printers with RAW socket communication (e.g. NOVEXX) |
9100, 9101 | Logopak printers (PL6). Port 9101 is used for signals. |
22 | Logopak printers (PL6), file transfer via SFTP (e.g. layouts and log files) |
8000, 8100, 8200 | Logopak printers (PL3) |
9084, 9184, 9284 | Logopak printers (PL3), used to reset the connection |
49153 | I/O modules (W&T Web-IO) |
4840 | OPC UA devices |
389 / 636 | LDAP / LDAPS, only if users log in with Active Directory accounts |
The following ports are used only on the manage.ID server itself. You do not need to open them in your firewall: 5432 (database), 5672 (AMQP), 8080 (Keycloak), 8081 (Core), 8087, 8088, 8089, 8095, 8098 (internal services).
2 - Installing manage.ID
This page describes how to install manage.ID on your device.
Prerequisites: Your device meets all System Requirements, including Local Administrator rights.
- Click Manage.ID to run the installer.
- If prompted, enter your Local Administrator credentials.
The manage.ID Setup Assistant starts. - Click Next.
- To install an optional function, check its box.
You cannot uncheck the grayed-out boxes as they are mandatory. For more information, see [Optional Functions](../optional-functions/).
- Click Next.
- Click Install.
The installation process may take a few minutes. - Windows Firewall requests network access permission. Check the box to allow access for private networks, then click Allow access twice.
The public network option is checked by default. You may deactivate it.
- Click Next.
- After the installation is complete, click Finish to close the Setup Assistant.
Result: manage.ID is installed on your device. The manage.ID services start automatically — you do not need to restart your device. The manage.ID client does not start automatically. The following shortcuts are now available on your desktop:
- Manage.ID – the manage.ID client
- Manage.ID Documentation – the online web help
To complete setup, proceed to Activating Your License.
3 - Activating Your License
This page describes how to upload your license file and activate manage.ID.
Prerequisites:
- manage.ID is installed on your device. See Installing manage.ID.
- You have received an email with your license file and customer number.
- Open manage.ID.
- In the upper toolbar, click Renew license.
- In the field Upload a license file, click Upload file.
The window Upload license file appears. - Add your license file using one of the following methods:
- Drag and drop your license file into the field.
- Click in the field to open the file explorer and select your license file manually.
- Enter your customer number.
Your customer number was included in the same email as your license file. - Click Upload.
Result: The information box License is valid appears in the upper toolbar for a few seconds. manage.ID is fully installed and activated.
4 - Optional Functions
manage.ID offers a set of optional functions that you can select during installation alongside the mandatory components.
Note
Optional functions can only be selected during a new installation. To add an optional function to an existing installation, run the installer again.
| Function | Description | When to install |
|---|
| PostgreSQL | A relational database bundled with manage.ID. | Install this unless you want to integrate a proprietary database. |
| Print Engine | Additional software that extends printer compatibility. | Install this to enable access to printers not natively supported by manage.ID. |
5 - Upgrading manage.ID
This page describes how to upgrade an existing manage.ID installation to a newer version.
Prerequisites:
- manage.ID is already installed on your device.
- You have Local Administrator rights on the device.
- You have received the new installer from PID Solutions.
Note
Before upgrading, we recommend backing up your current configuration and data. Contact PID Solutions support if you need assistance.
- Stop all active production lines in manage.ID before proceeding.
- Click the new Manage.ID installer to run it.
- If prompted, enter your Local Administrator credentials.
The manage.ID Setup Assistant starts and detects the existing installation. - Follow the on-screen instructions to complete the upgrade.
The upgrade process may take a few minutes. - Click Finish to close the Setup Assistant.
Result: manage.ID is upgraded. Your existing configuration, master data, and user accounts are retained. You do not need to reactivate your license unless instructed to do so.
6 - Error Logs
Typical errors and their respective log files and default file paths are listed here. Start with the Windows Service log when you encounter an unknown error, then consult the other logs as needed.
| Log File | What It Covers | Default File Path |
|---|
| Windows Service log | First log to check when encountering an unknown error | C:/Users/Public/Public Documents/PIDWare/LOG |
| Keycloak log | Users and access permissions | C:/PID3SIXTY/ManageID/ControlCenter/KEYCLOAK/log |
| manage.ID log | Errors while using manage.ID | C:/PID3SIXTY/ManageID/ControlCenter/APPLICATIONS/logs |
| Web server log | Access logs and errors | C:/PID3SIXTY/ManageID/ControlCenter/FRONTEND/logs |
You can also check the Windows Task Manager for additional information. For example, if a service is not running properly, ManageIDControlCenter will be listed as starting instead of running.
7 - Troubleshooting
This page describes common problems that may occur when installing manage.ID and how to resolve them.
License Upload Failed
Condition: manage.ID displays the error message License upload failed.
Wrong customer number
Cause: You have entered an incorrect customer number.
Remedy:
- Check your customer number. It is listed in your license and in the email with which your license was sent to you.
- Enter the correct customer number.
For more information, see Activating Your License.
Expired license
Cause: Your license has expired.
Remedy:
- Check the expiry date and confirm it lies in the future.
- If your license has expired, contact support to obtain a renewed license.
You will receive a warning 14 days before your license is due to expire.
Wrong Java Version
Condition: An error message appears during installation related to the Java version.
Cause: Your device has a Java version installed that is higher than the version required by manage.ID.
Remedy: Change the Java version on your device to Java SE 19.0.1.
Web Help Not Available
Condition: You cannot access the manage.ID web help.
No internet connection
Cause: Your device does not have a stable internet connection.
Remedy: Ensure that your device has a stable internet connection.
Intranet only
Cause: Your device is only connected to an intranet without internet access.
Remedy: Ensure that your device has an open internet connection.