Disconnecting an SCN from PCN
8 November 2023
ID 247901
The SCN can be disconnected from the PCN unilaterally.
If you disconnect an SCN using the SCN web interface, changed settings are only applied to the SCN. The PCN continues to display information about that server.
If you disconnect the SCN using the PCN web interface, information about that server is deleted at the PCN. However, the server with the SCN role will keep trying to connect to the PCN to synchronize settings.
To complete a bilateral disconnect, you must follow both instructions presented below. In this case, the SCN keeps working as a standalone Central Node server, and information about the disconnected SCN is displayed on the PCN.
The administrator of Kaspersky Anti Targeted Attack Platform is responsible for the confidentiality of data on PCN, SCN, and Central Node servers. If you plan to move an SCN server from one tenant to another, you must delete all data remaining on the server after using Kaspersky Anti Targeted Attack Platform and reinstall Kaspersky Anti Targeted Attack Platform before handing over the server to the different tenant.
To disconnect the SCN from the PCN through the PCN web interface:
- Log in to the application web interface with the administrator account.
Log in to the web interface of the PCN server that you want to disconnect the SCN from.
- Select the Operation mode section in the window of the application web interface.
- In the server list, select the SCN that you want to disconnect.
- Click Disconnect.
This opens the action confirmation window.
- Click Yes.
The SCN will attempt to connect to the PCN to synchronize settings.
To disconnecting the SCN from the PCN through the SCN web interface:
- Log in to the application web interface with the administrator account.
Log in to the web interface of the SCN server that you want to disconnect from the PCN.
- Select the Operation mode section in the window of the application web interface.
- Click Disconnect.
This opens the action confirmation window.
- Click Yes.
The SCN is disconnected from the PCN and continues working as a standalone Central Node server.
