How do clients get updated agents and do I need to configure other settings?
Our remote site has over 200 machines, but only 83 show up in the old smart label we use and I get the same result testing a new smart label. All machine names at the remote site begin with the same 4 letters and that's the criteria used for the label. ==> "Begins" with "abcd". Also tried "contains". Out of the 83 that do show up, only 6 received patches during a patch run 3 weeks ago. Most of the rest return "error (Handshake Failed)". I'm hoping a complete uninstall of the agent and data files and then a reinstall will correct this.
I need to force the install of the agent or maybe remove it first and then install it on over 200 remote clients with limited physical accessibility. I have one guy on site there, but he's swamped with other stuff so I'm trying to address this programmatically.
Our sec policies prevent us from running NTLM in a compatible manner with Kace. We must deploy first time install agents via GPO. I'm not clear on whether existing installed agents get their agent updates from the GPO or from Kace or from whichever happens to communicate with the client next. I'm also not sure if Kace can deploy agent updates at all due to our NTLM restrictions. Our Agent Updates from Kace page is set to Enabled as shown below.
*** Our Provisioned Configurations page has 75 configurations created by a previous tech, but they are all disabled. Do these configurations need to be working in order for Kace to deploy an updated agent to a machine with an older agent?
We have 2 sites and one replication machine that is located at the remote replication site. The replication action is confirmed to be working and has new files in the repl2\patches\windows directory with today's date.
Any tips or suggestions on getting the machines to report back to our K1K are greatly appreciated.