KACE Product Support

We use a logon script applied via group policy at the top of our domain and enforced down (so none of our machines can escape). Here's the script:

if exist "c:\program files\dell\kace\runkbot.exe" goto FOUND

if exist "c:\program files (x86)\dell\kace\runkbot.exe" goto FOUND

echo "%date%,%time%,%computername%" >> \\<path to your log file>\<log file name>.txt

:found

We check that file once a month and manually deploy if necessary.

You can use advanced provisioning to deploy agent on an IP range. If the agent is detected on a machine then it will not be reinstalled.

You can run the IP Scan in the kbox and have it try to connect to port 52230 (kbox amp port). Since this is an agentless scan, you can see what machines it can and can't connect to via port 52230. Those that we can't need the agent. 

You can also provision agents by host name, comma separated, under advanced provisioning. Export the last of names out of AD and you may need to clean it up and then as long as it is comma separated you can copy and paste into the field area for advanced provisioning by hostname.

I've found group policy to be particularly useful for catching machines that don't take the agent via advanced provisioning. If you want more granular control of which machines get the agent you can organize them by OU and apply the GPO to the OUs you want to ensure compliance on.