Prerequisites for installing SCC
Last updated June 4th, 2026
This document is new for the Knox cloud services 26.06 UAT.
On this tab
- Prepare your services, server, and network
- License
- OS requirements
- JDK requirements
- Recommended JDK versions for SCC client 26.06 or later
- Recommended JDK versions for SCC client 2.8.1 or earlier
- Firewall exceptions
- TCP communication resources
- Set up the TCP communication resource
- Check open source license information
- Copy the secret token
Before installing Samsung Cloud Connector (SCC), you must satisfy the prerequisites on this page in your network, server, and Knox Manage tenant.
If there is a web proxy between the SCC client and the SCC server connection, the connector won’t function.
From Knox Manage 26.06, the SCC client version format is changed to align with the Knox Manage version that it was launched. For example, 26.06.
The SCC Client Installer filename resembles SCC_Setup_Version_Builddate. For example, SCC_Setup_26.06_20260130.
Prepare your services, server, and network
License
Set up your Knox Manage tenant and register your Knox Manage license.
OS requirements
SCC is compatible with the following operating systems:
- Microsoft Windows Server 2008 R2 (64-bit)
- Microsoft Windows Server 2012 (64-bit)
- Microsoft Windows Server 2016 (64-bit)
- Microsoft Windows Server 2019 (64-bit)
- Microsoft Windows Server 2022 (64-bit)
- Microsoft Windows Server 2025 (64-bit)
JDK requirements
Your SCC client server requires the Java Development Kit (JDK) in one of the following configurations, depending on your use case:
-
To use the latest version of the SCC client (26.06 or later), you must install JDK 21 (64-bit).
When installing JDK 21 (64-bit) version, you must also set JAVA_HOME to JDK 21. For more details, refer to Setting PATH from JAVA_HOME.
-
To use SCC client 2.8.1 or earlier, you must install JDK 1.8.0 (64-bit).
Recommended JDK versions for SCC client 26.06 or later
We recommend using a JDK version from the following list, as these versions have been formally tested for SCC client 26.06 or later.
- Azul Zulu Prime 21.0.10
Recommended JDK versions for SCC client 2.8.1 or earlier
For security and system stability, we strongly recommend using the latest version of the SCC client.
We recommend using a JDK version from the following list, as these versions have been formally tested for SCC client 2.8.1 or earlier.
You must upgrade your SCC client if your client version is 2.5.2.1 or earlier. SCC client versions are reflected in the installer file name.
| OpenJDK distribution | Tested versions |
|---|---|
| Oracle OpenJDK |
1.8.0_251 1.8.0_291 1.8.0_311 1.8.0_341 1.8.0_352 1.8.0_451 (recommended for SCC client 2.5.2.1 or higher) |
| Azul Zulu Prime |
1.8.0_252 1.8.0_292 1.8.0_312 1.8.0_345 1.8.0_352 1.8.0_452 |
Firewall exceptions
- The firewall between the SCC client and the LDAP server must be open.
- The firewall between the SCC client and the CA server must be open.
- The firewall between the Layer 4 (L4) switch for accessing the SCC server and the SCC client must be open. Refer to the list below for the firewall information of L4 domains according to the service regions.
Aside from region code 01, if the region code is between 02 and 07, then you must include the region code after the area name (ap, us, eu) of the firewall domain. Your region code can be found in the URL of your Knox Manage console session.
| Region | Domain and port |
|---|---|
| Asia (Singapore) |
[01]
[02]
[03]
[04]
[05]
|
| US (Oregon) |
[01]
[02]
[03]
|
| EU (Ireland) |
[01]
[02]
[03]
[04]
[05]
[06]
[07]
[08]
|
TCP communication resources
The SCC server and SCC client are connected through TCP communication. To enhance the TCP performance of the SCC client, you can change the registry value.
Set up the TCP communication resource
We recommend changing the registry value for the TCP resource in the SCC client for enhanced TCP performance.
To do so, complete the following steps:
- On your computer, open the Registry Editor.
- Navigate to HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters.
- Change the value of each of the following items. If the value does not exist, right-click anywhere on the screen, and then select New > DWORD (32- bit) Value to create a new one.
- TcpTimedWaitDelay — Change the default value from 240 (4 minutes) to 30 (30 seconds) to convert the disconnected TCP resource rapidly. For more information, see https://technet.microsoft.com/enus/library/cc938217.aspx.
- MaxUserPort — Change the default value from 5000 to the maximum value of 65534 to increase the number of concurrent requests delivered to SCC from the application. For more information, see MaxUserPort in the Microsoft documentation.
Check open source license information
To check open source license information for SCC, refer to the following file in the folder where the SCC client is installed:
{SCC installation location}\scc-client\resources\SCCClient-OpenSourceLicense.html
Copy the secret token
You can enter a secret token while installing the SCC client. The added security the secret token provides helps authorize SCC, and prevents data leaks through the KM-SCC-LDAP channel.

To copy the secret token:
-
Click your account icon in the top-right of the console, then click Settings.
-
Go to Knox Manage > General settings, then click the Cloud connector tab.
-
Under Secret token, click COPY TOKEN.
If this is your first time generating a secret token, or you’ve revoked your previous secret token, you must first generate a token by clicking GENERATE TOKEN.
Is this page helpful?
Thank you for your feedback!