Upgrade and add a module on the current server

This route adds a module on the server performing the update. It does not create a remote agent. Check the module's hardware requirements and extra space for its images and data first.

1. Open Updates, select a target and complete the preparation in Upgrade an older single-server installation.
2. Find Add modules in the plan. Its contents depend on the installed modules and target release. Select only entries actually offered; editing the page address does not make an unavailable module supported. The plan reads "To add …, tick it below" next to the list.
3. Select the module. The panel rebuilds the plan. Recheck space, module composition, warnings and any requirements displayed below the selection. Do not rely on estimates read before this change.
4. If the added module causes refusal, read the reason. Use The plan without the added modules to return to a normal update, or resolve the additional requirements.
5. When using a delivery folder, ensure it also contains the added module for the correct version and edition. A folder for the previous module set may be insufficient.
6. After recalculation, complete the source and the required acknowledgements (no server name is typed for an update). Press Start the update.
7. Check both the updated product and the added module in the final result. Open Products and check the component's version, health and licensed availability.

For a module on another server, first finish the compatible product update, then install the node through Servers. Builder belongs on a separate server through Settings → Optional components; do not treat it as an ordinary local checkbox when the plan does not offer it. If the new function fails, retain the journal and saved update data while investigating.