Upgrade a distributed installation and expand it

Separate two changes: adding a module on the main server and adding a remote node. The update plan is not an agent-creation form. Define the intended topology, licensed modules and resources for every server first.

Add a module on the main server

1. On the main server, open Updates and select the target.
2. Under Add modules, select an offered module for the main server. Wait for recalculation and review its requirements as described in Upgrade and add a module on the current server.
3. Ensure the signed folder includes that module as well as the modules of the existing distributed installation.
4. Complete the all-server plan in Upgrade a distributed installation: node list, scan handling, delivery-folder source and maintenance acknowledgements.
5. Press Update all servers. Afterwards, check the added local module and every existing node separately. Selecting a module does not install it on all nodes.

Add a remote agent

1. First update existing Core and nodes to the intended compatible version using Upgrade a distributed installation. Resolve unfinished or excluded states.
2. Prepare the new server: resources, SSH/sudo, address, Core connectivity and delivery source. Add it through Servers and verify its fingerprint.
3. Run its checks. Choose module installation, the scanner and the main address reachable from the new node. Use a version compatible with the updated Core.
4. Review the separate node plan and install. Check Core ownership and component state in the server list.
5. Run a permitted job on the new agent. For multiple SAST agents, distinguish separate hosts from the threads setting of one SAST and check the licence limit.

If the new agent fails to install, the existing topology's update and the expansion have different outcomes. Do not report expansion as complete based on the earlier operation's success. Add SAST Builder separately on a server without SAST.