> For the complete documentation index, see [llms.txt](https://docs.hex-rays.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hex-rays.com/ida-9.5/add-ons/floating-license/admin/hex-rays-license-server-migration-guide.md). # Migrate to the current Hex-Rays License Server ## Choose your migration path There are two migration paths. Choose the one that matches the server you are replacing: | Existing deployment | How to recognize it | Migration path | | -------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Flexera-based license server** used with IDA 8.4 and earlier | Runs `lmadmin` or `lmgrd` together with the `hexrays` vendor daemon | Follow [From the Flexera-based license server](#from-the-flexera-based-license-server-ida-84-and-earlier) below | | **Previous Hex-Rays License Server** shipped with IDA 9.0–9.4 | Runs `license_server` or `hexlicsrv`, usually as the `hexlicsrv` service, and uses `lsadm` for administration | Follow [Migrating to the latest version](/ida-9.5/add-ons/floating-license/admin/license-server.md#migrating-to-the-latest-version) in the administration manual | ## From the previous Hex-Rays License Server (IDA 9.0–9.4) The current server can migrate this deployment directly. Its `setup` command reads the previous configuration, TLS material, access rules and license, and copies the existing database into the new data directory. Follow [Migrating to the latest version](/ida-9.5/add-ons/floating-license/admin/license-server.md#migrating-to-the-latest-version) for the complete procedure, including backup, shutdown, migration and rollback instructions. Do not use the Flexera procedure below, and do not unpack the new server over the existing installation. ## From the Flexera-based license server (IDA 8.4 and earlier) IDA 8.4 and earlier used these components: * the `lmadmin` or `lmgrd` license server manager, provided by Flexera * the `hexrays` vendor daemon, provided by Hex-Rays IDA 9.0 introduced the Hex-Rays License Server and its command-line administration client. Both are provided by Hex-Rays. The current package contains `license-server` and `license-client` in a single archive and needs no installer. ### Differences between the servers | | Flexera | Hex-Rays | | ------------------ | ----------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------- | | **Server setup** | Two binaries and processes: `lmadmin` or `lmgrd` server + `hexrays` vendor daemon | Single program (`license-server`), unzipped and set up with one command | | **Ports required** | Two ports required, plaintext communication | Single TCP port, communication protected by TLS | | **OS supported** | Server available for Windows, Linux, or macOS x64. Manual service configuration on Linux. | Server available for Linux x64 and arm64. The systemd service is registered by `setup`. | ### Migration steps To move from the Flexera-based infrastructure to the current Hex-Rays License Server: * First make sure that you have the [License Server Administration](/ida-9.5/add-ons/floating-license/admin/license-server.md) manual at hand. * Follow [Installing the Hex-Rays License Server](/ida-9.5/add-ons/floating-license/admin/license-server.md#installing-the-hex-rays-license-server). * Install a current IDA instance and test your installation by trying to connect to the license server, to select a license, borrow and finally return it. You are now ready to switch. ### Attention points for the switch Since an 8.4 client will not be able to connect to the new license server (and a 9.0 or later client won't be able to connect to the 8.4 license server), you should make sure that all users are using the new clients which are configured with the correct server and port. If your workflow requires using 8.4, you can keep the old server running until all users have switched to the new IDA version. Then you can stop and decommission the old server. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.hex-rays.com/ida-9.5/add-ons/floating-license/admin/hex-rays-license-server-migration-guide.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.