We have 100 Users an also 100 PC, and then any of this user has 1 or 2 VMs on his PC. I would make the Provisioning by the Hostname with a Placeholder. On example
Physical PC beginns with: CLVDxxxxxxxx
Virtual PCs beginns with: VCLVDxxxxxx
I would now enroll the agent only to the Physical PCs. But in the Target Hostnames its not possible to write CLVD* or something like that.

WHen provisioning to a client, most of the time my clients get SUCCESS on 90 percent of the deployment but then fail with one error or another. Your support site says “Test connectivity to ports 139 and 445 on TARGETPC from the K1000 Appliance. On Windows devices, ports 139 and 445, File and Print Sharing, and Administrator credentials are required only during Agent installation. “
SYSTEM>SETTINGS>SUPPORT>Diagnostic Utilities> TEST:
But there is no TELNET option available to use to TEST!!! TELNET needs to be added for PHYSICAL APPLIANCES as the instructions are written for KACE VM’s I believe.

WHen provisioning to a client, most of the time my clients get SUCCESS on 90 percent of the deployment but then fail with one error or another. Your support site says “Test connectivity to ports 139 and 445 on TARGETPC from the K1000 Appliance. On Windows devices, ports 139 and 445, File and Print Sharing, and Administrator credentials are required only during Agent installation. “
SYSTEM>SETTINGS>SUPPORT>Diagnostic Utilities> TEST:
But there is no TELNET option available to use to TEST!!! TELNET needs to be added for PHYSICAL APPLIANCES as the instructions are written for KACE VM’s I believe.

For differents reasons, we install the K1000 agent with some switches, namely "NOHOOKS=1" or "/qb! /i". But when we use agent provisioning feature (either "Provisioning Schedule Detail" page or "Update Agent Settings" page), we're unable to add these switches, so the installer don't have the behavior we expect.
It could be interesting to have an "Additionnal Parameters" field like in "Managed Installation Detail" page.

It would be great if the error messages were more accurate so if I run a agent installation against a subnet the failed error message said "agent already installed" or "no agent found" and that sort of thing. This will allow me to focus on actual problem devices.

The ability to provision a machine, for example, by going "Kace_Server"/provision instead of having to create a simple provisioning schedule. You could have the page you landed on ask you for your kace credentials and then only allow specific users in Kace to initiate this process.

This would be much faster for getting new machines or recently rebuilt machines provisioned instead of waiting for Kace to scan your entire DHCP range for new machines or look-up each machines IP so that you could setup a simple provisioning schedule.