/build/static/layout/Breadcrumb_cap_w.png
01/17/2019 156 views

Hello all, new Ninja here... We are in the process of deploying the agent to all of our domain PCs, however we have a number of Windows devices that are off our domain that we would like to install the agent. I am trying to use Kaspersky Security Center to deploy the agent to some of our POS devices, but am not having any luck. I have uploaded the entire folder (ampagent-9.0.167-x86.msi, agent_msi_remove.bat, agent_msi_provision.bat) using differnet silent paramaters (/qn, /s) to push out the installation and no luck! Any siggestions are much appreciated!



1 Comment   [ + ] Show comment

Comments

  • Are there any hints launching the msi manually? Is it installing, just not syncing? Check that they can reach the K1000 since they are off the domain. For instance, you cannot get to our kbox outside our firewall, but, we can still manage them inside and they can get resources off the replication servers using credentials the K1000 provides on their behalf.

    This is my cmd: msiexec /i ampagent-8.1.52-x86.msi host="mydomain.com" cloneprep="1" /qn


Community Chosen Answer

2

There are a few options.
The first (and obvious) would be a Provisioning (if the right ports are open and the clients are configured correctly, this should be no problem)

The second, if you use a 3rd party deployment tool, use the right parameters.

msiexec /i AGENT.msi /qn host=XXX (where XXX is your KACE Appliance webserver name) NOHOOKS=1 DEBUG=ALL
(I use the NOHOOKS, since not all of my managed devices boot in a network environment, so the userinit is not modified, it has other flaws, but in my case it is more important, and I love logs ;) )
All options can be found here:
https://support.quest.com/kb/153581

You also need to verify your POS systems are x86 technology, since the agent is only avaiable for x86 (or Raspberry), so some ARM POS will not take the agent.

Answered 01/17/2019 by: Nico_K
Red Belt

All Answers

0

if you have a common user and password on these machines you can use a provisioning schedule and use those credentials to attach as and install the client,  Even if you have a few accounts you can create multiple schedules and use different credentials where needed


Answered 01/17/2019 by: SMal.tmcc
Red Belt