Kace agent provisioning for remote computers
I have used PStools psexec to remotely enable WinRM on a few Windows test computers but am still seeing failed installations of the Kace agent. I am not seeing anything significant in the log file on the K1100 appliance. Has anyone pushed out the agent successfully over a VPN?
Thanks in advance,
Can you post your script and your errors? That would be helpful.
I have been able to push agents out over the VPN provided your VPN is setup so the machine doing the pushing is allowed to connect to the remote computer.
You can test if you have access from the deployment computer to the remote computer by trying the following:
- Open \\Remotecomputer\admin$ to reach the remote computer's C:\Windows folder. If you cannot then PSEXEC will not push the files over
- If your install file is located on a server share you have to be sure Authenticated Users can access the share, because you are most likely trying to run PSEXEC with the -S switch (Use System Account) to install the agent. The system account (computer) must be able to access the remote share so Domain User group access is not sufficient.
Hi James, it depends on how many computers you are attempting to install the client.
If you are connecting to a single computer that is VPN'd in: I would copy the install file to the local (VPN'd) machine and use psexec (or powershell) to run the installer. Making sure you have "admin" rights on the machine.
If you are attempting to do a push from Kace to install the client on multiple machines that could be tricky, I would attempt to wrap the whole package in a zip and run the bat file locally?
VPN'd machines would be an issue due to network connectivity users disconnecting etc.., I have heard that people are starting to move/allow access directly from the internet (DMZ) to the Kace server for updates and installs, but I have not done much research on the possibilities.