Skip to main content

Bring an existing installation under DCP

Use this procedure to manage an existing DerScanner installation without replacing its data. Record its version, edition, modules, main server address and every scanner node. Prepare a recoverable independent copy or snapshot first.

  1. Start DCP on the server that already holds the product and sign in. Open Overview, then Products. Compare the detected version, modules and the message about bringing the installation under the panel: Overview says once that DerScanner of that version was found on the server and the panel can update it.
  2. If the panel shows an empty server, refuses recognition or reports an unfinished operation, stop. Check the selected server and product location. Do not start a fresh installation to repair recognition.
  3. Open Updates. If asked for the edition, choose the edition specified in your contract or delivery. The interface language does not identify the product edition. Press Confirm the edition and wait for the operation result.
  4. For explicit adoption, the administrator first runs sudo dcp adopt --dry-run on that server. Read the detected version, directories, warnings and relationship to Core; a module whose service is not running is named. If correct, run sudo dcp adopt --yes. A state that already records the product is refused, in the dry run as in a real run.
  5. When the edition is unknown, supply its confirmed technical identifier: sudo dcp adopt --edition EDITION --yes. Replace EDITION with the identifier specified for your delivery; do not type the placeholder literally. For the International edition EDITION is international; for another edition use the identifier given with your delivery. The document or interface language does not determine the edition. This command does not convert an installation between editions.
  6. For a separate SAST/DAST/SCA node of a classic 12.6 or 13.0 installation, run sudo dcp adopt --node MAIN_ADDRESS --dry-run on the node, then the same command with --yes instead of --dry-run. Replace MAIN_ADDRESS with the real Core address reachable from that node. If sudo dcp nodes on the main server prints this command with --edition, run it exactly as printed. A DerScanner 13.2 node installed using DCP does not need adoption. This command does not move a component to another Core.
  7. Add your nodes to Servers on the main panel and check connectivity and ownership. Return to Overview and review each server separately.

The result is the existing installation represented in DCP with its actual health. Adoption does not itself upgrade the product or repair unhealthy services. If refused, retain the error and use Support to collect an archive; do not edit the state file by hand.