Problem in remote installation [MOVED]

[Guest]

Dear Admin

I faced with the problem of can not connecting to server to installing antivirus version on client.

I have a work group network, after installing Console, I had a problem to can not see the client which are in a defined IP Scope, so that I installed package locally on client, then It was possible to add device individually in managed devices, but the antivirus version is not installed on them.

I created a change administration Task and set the server IP as the antivirus Server to solve this problem, The task operated successfully, the I tried to install remotely package again, but It got stuck in the 32% of the process and the problem was in the connecting client to server and vice versa phase

how can i solve this problem?

 

 

[Deadlock4400]

Hello @Samira-IT Expert 

Your Remote Installation Target machine should have Windows Firewall Off and Windows Remote Registry Service ON. And check if any other AV is installed there or not.

And while you installed KSC, was it IP base or FQDN base installation?

 

Thanks in Advance

@Deadlock4400 

[Guest]

Dear Deadlock

hi

What do you mean by windows remote registry service? is that Windows Remote Management Service?

and It would be on , on all clients? or you mean It should be on, just on server?

There is no FQDN because It’s a workgroup network, and I set the Server IP in “Change administration “ Task to established a connection between clients and server based on IP Address

but I chechked it before and I’m sure about solving NetBios Name to IP Address correct

 

[Deadlock4400]

Dear Deadlock

hi

What do you mean by windows remote registry service? is that Windows Remote Management Service?

and It would be on , on all clients? or you mean It should be on, just on server?

There is no FQDN because It’s a workgroup network, and I set the Server IP in “Change administration “ Task to established a connection between clients and server based on IP Address

but I chechked it before and I’m sure about solving NetBios Name to IP Address correct

 

I clearly wrote there that for Client/Target machine, NOT KSC Server?

You can find the Remote Registry Service on Services.msc 

While you did KSC, what did you chose, IP or FQDN for this KSC Server, that i was saying!

 

 

[Guest]

Dear Deadlock4400

I implement Kaspersky security Console, and then saw which clients are discovered in the unassigned clients list, just one of all my clients was discovered

so I installed package (integration of Agent & antivirus) on client,Agent was installed successfully but the antivirus was not installed , then I tried to use remote installation tools but it was not successfull

The installation task got stuck in 32% and the problem was in connection between client and server.

please note that I disabled firewall service in server and turn off It in client control panel

[Deadlock4400]

Dear Deadlock4400

I implement Kaspersky security Console, and then saw which clients are discovered in the unassigned clients list, just one of all my clients was discovered

so I installed package (integration of Agent & antivirus) on client,Agent was installed successfully but the antivirus was not installed , then I tried to use remote installation tools but it was not successfull

The installation task got stuck in 32% and the problem was in connection between client and server.

please note that I disabled firewall service in server and turn off It in client control panel

try to do ping with IP and hostname from both side (Server to Client and Client to Server), if that’s alright then from Client PC \\…...(KSC server IP), see if you have the KLShare folder or not?

[Guest]

It’s possible to solve server’s Netbios name and Client’s Netbios name in the both side

and Server have access to client’s c$

and in the client side I able to open klshare

[Deadlock4400]

If the connection between KSC Server and Clients are good to go then the problem in your Network Agent and on Client Packages.

Try to make standalone package of Network Agent and Endpoint. Then first installed Network agent then Endpoint agent.