How many endpoints can a KACE virtual appliance support?
Hello,
I have some questions about a large KACE deployment.
How many endpoints can one KACE Endpoint Systems Deployment Appliance virtual appliance support?
Working with 30,000 endpoints.
If multiple appliances are required, is there some sort of HA configuration?
Thanks!
1 Comment
[ + ] Show comment
Answers (2)
Please log in to answer
Posted by:
AbhayR
6 years ago
KACE Endpoint Systems Management Appliance can support up to 20K nodes.
KACE Endpoint Systems Deployment Appliance doesn't manage any nodes. It does the OS deployment.
There are ways by which more than 1 KACE Endpoint Systems Management Appliance can integrate. But there is no HA support between 2 KACE Endpoint Systems Management Appliance
Posted by:
jamie_kace
6 years ago
The SMA Appliance scales to about 16,000 nodes per appliance, some of that will vary based on usage (i.e. if you are not patching or pushing software it might handle more since there is less load).
You can see specs on this page:
https://www.quest.com/products/kace-systems-management-appliance/
There is no HA configuration but the SMA can be linked to other SMAs for a master reporting server (called Federated Reporting in the admin guides). We have many large customers that have multiple appliances sharing the load and a reporting appliance that is pulling from all of the SMAs.
We do support using distribution points which can ease the traffic on the main appliance and those distribution points (replication shares) are no additional cost, it is simply an agent at the remote site and storage at the local site for distribution of patches and software.
The SDA will support more typically since you are not doing as much connection wise. Specs are here:
https://www.quest.com/products/kace-systems-deployment-appliance/
We also support a distribution site with the SDA but these are simply VMs at the remote sites (VMWare or HyperV) that sync back with the master appliance. Again given that there is no agent check in or constant traffic like with the SMA, you can probably support all of your devices with a single appliance and RSAs at remote locations.
Your KACE Sales team will be able to architect the proper solution based on your requirements and topology.
You can see specs on this page:
https://www.quest.com/products/kace-systems-management-appliance/
There is no HA configuration but the SMA can be linked to other SMAs for a master reporting server (called Federated Reporting in the admin guides). We have many large customers that have multiple appliances sharing the load and a reporting appliance that is pulling from all of the SMAs.
We do support using distribution points which can ease the traffic on the main appliance and those distribution points (replication shares) are no additional cost, it is simply an agent at the remote site and storage at the local site for distribution of patches and software.
The SDA will support more typically since you are not doing as much connection wise. Specs are here:
https://www.quest.com/products/kace-systems-deployment-appliance/
We also support a distribution site with the SDA but these are simply VMs at the remote sites (VMWare or HyperV) that sync back with the master appliance. Again given that there is no agent check in or constant traffic like with the SMA, you can probably support all of your devices with a single appliance and RSAs at remote locations.
Your KACE Sales team will be able to architect the proper solution based on your requirements and topology.
You can see specs on this page:
https://www.quest.com/products/kace-systems-management-appliance/
There is no HA configuration but the SMA can be linked to other SMAs for a master reporting server (called Federated Reporting in the admin guides). We have many large customers that have multiple appliances sharing the load and a reporting appliance that is pulling from all of the SMAs.
We do support using distribution points which can ease the traffic on the main appliance and those distribution points (replication shares) are no additional cost, it is simply an agent at the remote site and storage at the local site for distribution of patches and software.
The SDA will support more typically since you are not doing as much connection wise. Specs are here:
https://www.quest.com/products/kace-systems-deployment-appliance/
We also support a distribution site with the SDA but these are simply VMs at the remote sites (VMWare or HyperV) that sync back with the master appliance. Again given that there is no agent check in or constant traffic like with the SMA, you can probably support all of your devices with a single appliance and RSAs at remote locations.
Your KACE Sales team will be able to architect the proper solution based on your requirements and topology. - jamie_kace 6 years ago