KLMover not working

[Nabi]

I want to change the IP address of our KSC, It is 192.168.1.6

I added a new network adapter with new IP address 172.17.30.22 to the KSC VM. Both IP addresses are reachable.

I searched the web and found the KLMover tool, but running this command did not change the administration server address.

old IP address of KSC was: 192.168.1.6

new IP address of KSC is: 172.17.30.22, but I used DNS address: kaspersky.ourdomain.local , The client can resolve the name and ping the KSC server.

Result of klnagchk (before running klmover):

Quote

c:\Program Files (x86)\Kaspersky Lab\NetworkAgent>klnagchk.exe
Starting utility 'klnagchk'...
Checking the command-line options...OK
Initializing basic libraries...OK
Current device is '*****'
Network Agent version is '14.0.0.10902'

Reading the settings...OK
Verifying the settings...OK
Network Agent settings:
  Administration Server address: '192.168.1.6'
  Use SSL: 1
  Compress traffic: 1
  Numbers of the Administration Server SSL ports: '13000'
  Numbers of the Administration Server ports: '14000'
  Use proxy server: 0
  Administration Server certificate: available
  Open UDP port: 1
  Numbers of UDP ports: '15000'

  Synchronization interval (min): 15
  Connection timeout (in seconds): 30
  Send / receive timeout (in seconds): 180
  Device ID: ********************************

Attempting to connect to Administration Server...OK

Attempting to connect to Network Agent...OK
Network Agent is running.
Receiving the Network Agent statistical data...OK
  Network Agent statistical data:
  Total number of synchronization requests: 3
  The number of successful synchronization requests: 3
  Total number of synchronizations: 2
  The number of successful synchronizations: 2
  Date/time of the last request for synchronization: 1/23/2023 4:08:47 PM GMT 

Deinitializing basic libraries...OK
 

 

 

Result of klmover:

Quote

c:\Program Files (x86)\Kaspersky Lab\NetworkAgent>klmover.exe -address kaspersky.ourdomain.local -dupfix
Checking the command-line options...OK
Initializing basic libraries...OK
Verifying the settings...OK
Reading the settings...OK
Preparing settings...OK
Writing settings...OK

Restarting the Network Agent service...OK

Operation has completed successfully.

 

Result of klnagchk (after running klmover):

Quote

c:\Program Files (x86)\Kaspersky Lab\NetworkAgent>klnagchk.exe
Starting utility 'klnagchk'...
Checking the command-line options...OK
Initializing basic libraries...OK
Current device is '******'
Network Agent version is '14.0.0.10902'

Reading the settings...OK
Verifying the settings...OK
Network Agent settings:
  Administration Server address: '192.168.1.6'
  Use SSL: 1
  Compress traffic: 1
  Numbers of the Administration Server SSL ports: '13000'
  Numbers of the Administration Server ports: '14000'
  Use proxy server: 0
  Administration Server certificate: available
  Open UDP port: 1
  Numbers of UDP ports: '15000'

  Synchronization interval (min): 15
  Connection timeout (in seconds): 30
  Send / receive timeout (in seconds): 180
  Device ID: *************************************

Attempting to connect to Administration Server...OK

Attempting to connect to Network Agent...OK
Network Agent is running.
Receiving the Network Agent statistical data...OK
  Network Agent statistical data:
  Total number of synchronization requests: 1
  The number of successful synchronization requests: 1
  Total number of synchronizations: 1
  The number of successful synchronizations: 1
  Date/time of the last request for synchronization: 1/23/2023 4:15:06 PM GMT

Deinitializing basic libraries...OK
 

 

where is the problem? 

 

 

[DonKid]

Please, open a ticket here.

[Renan Corassa]

Do you want to use two ips on KSC or just one?

[ElvinE5]

1. The address 172.17.*.* is not a standard network for the default client settings, in the process of work you may have some difficulties associated with restrictions for public networks ... therefore, before switching clients to a new server address, specify this network as local to your clients, in KES policy

Спойлер

Спойлер

2. I would still recommend to switch clients to a new address (you execute the klmover command on the client device) to use an IP address in a non-DNS, it is still reliable, besides, you have one name with two IPs in DNS ... this can confuse ...

3. Check that the client device can REALLY ping the new address, and that a TCP 13000 connection is open between the server (new IP) and the client, you can check with the PS command from the client device

tns 172.17.30.22 -port 13000

Спойлер

4. When switching the client, run cmd as admin, and run the command to change the administration server (klmover)

klmover -addrress 172.17.30.22

the same can be done using the "change administration server" task in KSC, for devices connected to this server, remotely

Спойлер

 

try it, hope it works...

 

Edited July 27, 2023 by ElvinE5

[THask]

Hi Nabi,

if the DNS Server knows the new IP Address and you used the DNS Name of your KSC Server as connection Information on the Devices for the Network Agent you normally have nothing to move.

If the Network Agent Connection Information is not the IP only the DNS Name the Service is using the Information what is the result contacting DNS Server. If the Device could resolve the Name to the new IP and it is reachable in your Network from the Devices you don't have to change anything.

And the Mistake in your commands was the -dubfix suffix that is an old Command for resetting the Connection Information and GUID from the Network Agent.