This section explains how to configure the operating environment of the Relay Server.
For each smart device (Android device or iOS device) or PC (Windows device) to be managed, configure the settings below.
Android device:
Use SDSVSetMS.EXE (change configuration of Relay Server command) to set the following:
- Enable management of Android devices: Specify the -Android.enabled option.
- Set the Management Server or Master Management Server: Specify the -h option.
If the default port number (48080) must be changed, refer to "How to Modify the Port Number Being Used" in the Reference Manual and change the port number.
To perform HTTPS communication with a smart device (agent) (Android), build a certificate environment for HTTPS communication.
Refer to "2.9.3.2 Configuring HTTPS Communication" for details. The procedure is the same as that for managing iOS devices, so you do not need to configure the settings if you have done so on an iOS device.
Use SDSVService.bat (start/stop service of Relay Server command) to start the Relay Server.
iOS device:
Point
You can configure the settings in steps 1 to 4 below at one time.
Enable management of iOS devices.
Execute SDSVSetMS.EXE (change configuration of Relay Server command) with the -iOS.enabled option.
Set the Management Server and Master Management Server.
Execute SDSVSetMS.EXE with the -h option.
This procedure is the same as that for managing Android devices, so you do not need to configure the settings if you have done so on an Android device.
Set the server or reverse proxy that is to be connected to from the iOS device.
Execute SDSVSetMS.EXE with the -iOS.connect.h, -iOS.connect.p, and -iOS.connect.profile.p options.
Set the iOS management database.
Execute SDSVSetMS.EXE with the -iOSmgr.h option.
To manage iOS devices with Systemwalker Desktop Keeper only, specify the Management Server.
To manage iOS devices even with Systemwalker Desktop Patrol, specify the Management Servers or Systemwalker Desktop Patrol CSs that are running the iOS management database.
Do not change this setting after configuring it.
If necessary, change the default port number (55432) to be used for communication with the iOS management database.
Refer to "How to Modify the Port Number Being Used" in the Reference Manual for details.
Build the certificate environment to perform HTTPS communication with a smart device (agent) (iOS).
Refer to "2.9.3.2 Configuring HTTPS Communication" for details.
The procedure is the same as that for managing Android devices, so you do not need to configure the settings if you have done so on an Android device.
Install the MDM certificate prepared in "2.2 Advance Preparation".
Execute swss_ImportAppleCert.bat (register Apple Inc. certificate command).
Start the Relay Server.
Execute SDSVService.bat (start/stop service of Relay Server command).
Windows devices
Point
You can configure the settings in steps 1 to 3 below at one time.
Execute SDSVSetMS.EXE (change configuration of Relay Server command) with the -Windows.enabled to enable management of Windows devices.
Execute SDSVSetMS.EXE (change configuration of Relay Server command) with the -h option to specify the FQDN or IP address of the Management Server/Master Management Server.
This procedure is the same as that for managing Android/iOS devices, so you do not need to configure the settings if you have done so on an Android/iOS device.
If the default port number (48643, 48281,48443,48081) used when connecting from a Windows device must be changed, refer to "How to Modify the Port Number Being Used" in the Reference Manual for details.
To perform HTTPS communication with a client (CT), build a certificate environment for HTTPS communication.
Refer to "2.9.3.2 Configuring HTTPS Communication" for details.Execute SDSVService.bat (start/stop service of Relay Server command) to start the Relay Server.
Refer to "Command Reference" in the Reference Manual for details on each command.
Note
Notes regarding coexistence with Systemwalker Desktop Patrol SS
The following options of SDSVSetMS.EXE (change configuration of Relay Server command) are used only in Systemwalker Desktop Keeper:
-h
-p
-Android.http.p
-Android.https.p
-Android.enabled
-iOS.enabled
-Windows.https.p
-Windows.scep.p
-Windows.manage.https.p
-Windows.manage.scep.p
-Windows.enabled
The following items options of SDSVSetMS.EXE (change configuration of Relay Server command) are also used in Systemwalker Desktop Patrol:
-iOSmgr.h
-iOSmgr.p
-iOS.profile.p
-iOS.https.p
-iOS.connect.h
-iOS.connect.p
-iOS.connect.profile.p
The items set in steps 6 and 7 for iOS device are also used in Systemwalker Desktop Patrol.
For items also used in Systemwalker Desktop Patrol, specify the same values in both products.
After the items are set in Systemwalker Desktop Keeper, specifying different values in the same items in Systemwalker Desktop Patrol will result in the settings initially configured in this product changed to the new values specified in Systemwalker Desktop Patrol. After the items are set in Systemwalker Desktop Patrol, specifying different values in the same items in this product will result in the settings initially configured in Systemwalker Desktop Patrol changed to the new values specified in this product.
This section describes how to configure HTTPS communication between the Relay Server and a smart device (agent)/client(CT). The configuration procedure depends on whether the server certificate used is prepared by the user or is the Systemwalker certificate.
Perform the procedure below to configure the settings:
Use SDSVMakeCSR.exe with the -file option to generate the certificate issuance application.
Send the certificate issuance application that was generated in step 1 to the CA, to obtain the CA certificate (intermediate CA certificate) and server certificate issued by the CA.
Use SDSVService.bat to stop the Relay Server.
Use SDSVImportCert.exe with the -file option (-alias option) to register the CA certificate (intermediate CA certificate) obtained in step 2.
Use SDSVImportCert.exe with the -file option to register the server certificate obtained in step 2.
If using the Windows client (CT) to connect to the Relay Server, perform the procedure below.
Use SDSVMakeCSR.exe with the -file option to generate the ccertificate issuance application. This step should be performed apart from step 1.
Save the certificate issuance application that was generated in step a to the Management Server, and use DTKSVMakeCSR.exe with the -file2 and -certfile2 options on the Management Server to generate a server certificate based on the certificate issuance application file.
Use SDSVImportCert.exe with the -file2 option to register the server certificate obtained in step b.
Use SDSVConfig.exe to enable the use of the server certificate prepared by the user.
Use SDSVService.bat to start the Relay Server.
Note
If step 5 is mistakenly performed before step 4, repeat the procedure from step 1.
Use SDSVMakeCSR.exe, and specify the -file and -certfile options to generate a certificate issuance application and server certificate.
Use SDSVService.bat to stop the Relay Server.
Execute SDSVImportCert.exe with the -CACERT option specified.
Use SDSVImportCert.exe with the -file option to register the server certificate generated in step 1.
If using the Windows client (CT) to connect to the Relay Server, perform the procedure below.
Use SDSVMakeCSR.exe with the -file option to generate the ccertificate issuance application. This step should be performed apart from step 1.
Save the certificate issuance application that was generated in step a to the Management Server, and use DTKSVMakeCSR.exe with the -file2 and -certfile2 options on the Management Server to generate a server certificate based on the saved certificate issuance application file.
Use SDSVImportCert.exe with the -file2 option to register the server certificate obtained in step b.
Use SDSVConfig.exe to enable the use of the server certificate that you registered in step 5.
Use SDSVService.bat to start the Relay Server.
Note
If step 4 is mistakenly performed before step 3, repeat the procedure from step 1.
Perform the procedures below to configure the settings:
Use SDSVMakeCSR.exe to generate the certificate issuance application for the server certificate.
Send the certificate issuance application that was generated in step 1 to the CA, to obtain the server certificate issued by the CA.
Use SDSVService.bat to stop the Relay Server.
Use SDSVImportCert.exe with the -file option to register the server certificate obtained in step 2.
If using the Windows client (CT) to connect to the Relay Server, perform the procedure below.
Use SDSVMakeCSR.exe with the -file option to generate the certificate issuance application. This step should be performed apart from step 1.
Save the certificate issuance application that was generated in step a to the Management Server, and use DTKSVMakeCSR.exe with the -file2 and -certfile2 options on the Management Server to generate a server certificate based on the certificate issuance application file.
Use SDSVImportCert.exe with the -file2 option to register the server certificate obtained in step b.
Use SDSVService.bat to start the Relay Server.
Use SDSVMakeCSR.exe, and specify the -file and -certfile options to generate a certificate issuance application and server certificate.
Use SDSVService.bat to stop the Relay Server.
Use SDSVImportCert.exe with the -file option to register the server certificate generated in step 1.
If using the Windows client (CT) to connect to the Relay Server, perform the procedure below.
Use SDSVMakeCSR.exe with the -file option to generate the certificate issuance application. This step should be performed apart from step 1.
Save the certificate issuance application that was generated in step a to the Management Server, and use DTKSVMakeCSR.exe with the -file2 and -certfile2 options on the Management Server to generate a server certificate based on the saved certificate issuance application file.
Use SDSVImportCert.exe with the -file2 option to register the server certificate obtained in step b.
Use SDSVService.bat to start the Relay Server.
Refer to "Command Reference" in the Reference Manual for details on each command.
Note
In coexistence with the SS of Systemwalker Desktop Patrol V15.0.0 or later, if a certificate is registered in Systemwalker Desktop Patrol after another certificate is registered in Systemwalker Desktop Keeper, then the certificate registered in Systemwalker Desktop Patrol will be used for HTTPS communication between iOS devices and the Relay Server.