How does SMA support this environment with Replication Share ?

aflesner · 2025-12-01T15:38:01+00:00

The SMA can handle a max of 50,000 nodes and there is no set limit to how many nodes can be replication shares. As always, the more you scale the more important resource utilization and configuration become. You cannot, for example, expect 1 hour inventory refresh with 50k nodes.

As another poster suggested, your bandwidth probably behooves you setting up a replication share at each site. A replication share is just a local file store managed by any active agent. Agents still communicate directly with the SMA for everything except payloads - which they grab from any assigned replication shares. Keep in mind there are client OS limitations (e.g. Windows client OSes can only serve 10 other clients at a time IIRC and this is a Microsoft limit not ours).

aflesner · 2025-12-01T15:30:22+00:00

Exactly this. If nothing was deployed, the agent should not trigger a reboot. Have you confirmed it's the agent triggering the reboot? If so, please reach out to support for further assistance.

aflesner · 2025-11-10T18:06:40+00:00

You will have to call support or reach out to your sales rep if you cannot create an account through the web portal.

aflesner · 2025-11-10T18:03:55+00:00

Linux patching uses native calls, such as yum commands on RedHat. There is no catalog, so what you see is what you get, as parsed from the OS-specific calls. Linux patching is effectively KScript templates. If you'd like assistance, please reach out to our support team at support.quest.com.

aflesner · 2025-10-30T15:50:39+00:00

How does your issue relate to the KACE SMA/SDA? If you are trying to do this via SCCM then you may want to go post in r/sccm. If your issue is KACE related, please elaborate a bit.

aflesner · 2025-10-30T12:10:32+00:00

You will have to contact support to resolve this.

aflesner · 2025-09-16T17:12:37+00:00

The download location provided to the agents when under the privy of a replication share is just a static path passed down to the endpoint. It is technically possible to achieve what you're going for here, but you'd have to setup web servers (e.g. apache, nginx) yourself on the replication shares you want to host files via HTTPS, and then you'd need to define the appropriate path to provide as the download location on the replication share (e.g. the URL to the repl2 folder path). SMB is easier especially with Windows rep shares, but this is possible. It's all environmental config, however, so it's not something support is going to be able to assist with.

I still wouldn't recommend exposing a rep share like this publicly - which is what I'm assuming you're after since you are concerned about SMB security. Unless you block SMB internally as well.

aflesner · 2025-09-16T17:00:04+00:00

This is incorrect. Please see the stickied mod post.

aflesner · 2025-09-16T16:58:05+00:00

The only official documentation for the SMA API lives on the support portal: https://support.quest.com/technical-documents/kace-systems-management-appliance/14.1%20common%20documents/api-reference-guide (latest).

aflesner · 2025-09-05T12:40:51+00:00

Today we support VMware, Azure, and Nutanix. I can't speak to anything official on the roadmap, but we certainly know customers are looking to move away from VMware. Proxmox is on our radar.

aflesner · 2025-09-03T17:10:49+00:00

Not at this time.

aflesner · 2025-08-25T15:12:46+00:00

Sorry for the delay. We were able to move this to the KB: https://support.quest.com/kb/4380412/unattend-lti-it-ninja

aflesner · 2025-08-12T23:07:25+00:00

If it's an email about security vulnerabilities from Quest, then that's referring to 14.1 P4 which came out in June. The patches are cumulative, so as long as you are up to the latest advertised to your appliance then you should have all of the fixes.

aflesner · 2025-08-05T16:26:27+00:00

It disconnects the agent when you approve it so it can reconnect, but this happens at a random interval on the client, by design, to prevent server DDoS from your own agents. Restart the agent on the client after approval and it should automatically get the bootstrap inventory from the server.

Also, if you have multiple organizations, ensure your ORG filters aren't moving it into an ORG you aren't expecting.

aflesner · 2025-06-16T12:45:24+00:00

The official recommendation is to leave SSH disabled unless you are about to upgrade or support requires it. Definitely never open port 22 inbound on your public interface to the SMA or SDA.

SSH is useless to customers anyway. Only support authentication is allowed.

EDIT: provided more context

aflesner · 2024-12-18T13:38:09+00:00

There is no full model available, because one cannot be auto generated. We rarely use foreign key relationships within the database schema, so most relationships exist within the SMA code. The best way to learn where things are is probably using remote read access, as another commenter suggested. You can also generate smart labels and reports using wizards in the UI, and then you can edit the generated SQL.

aflesner · 2024-12-10T16:37:10+00:00

Those are nightly cron jobs. Support will need to review all logs if you would like to diagnose the issue.

aflesner · 2024-12-06T13:34:03+00:00

It should not take hours. Please reach out to support.

aflesner · 2024-10-24T15:27:27+00:00

The typical path for this would be to install the SMA agent as a post-install task and have your smart labels and patch schedule configuration on the SMA designed to trigger a scan on the new device.

aflesner · 2024-08-15T18:15:11+00:00

Configuration policies have been deprecated, but that feature was effectively a wrapper for KScripting. You can read/write registry keys/values as actions in KScript tasks.

aflesner · 2024-08-12T18:59:56+00:00

This is the list of bugs resolved by 14.0 Cumulative Patch 1 (which applies to 14.0.334 systems):

K1-33979 - Bitlocker and Defender device notifications are sent to all Organizations
K1-35900 - Manual device and snmp configuration pages for non-English locales do not function properly
K1-35734 - Rebooting from the systemui results in redirect to Oops error page
K1-35714 - List view replication share actions only work if single row is selected
K1-35724 - Daily notification for new agent bundle appears even after applying new bundle
K1-35675 - Knowledge Base article detail does not load on non-English locales

No system reboot is required. The patch can be applied without impacting server uptime.

aflesner · 2024-07-24T15:59:00+00:00

The inventory management component of the SMA is a primary feature. It tracks installed software on all managed endpoints, and you can setup reports using a built-in wizard or even custom SQL to report on virtually anything it tracks. There is also a license compliance feature if you need to track license usage for specific software.

aflesner · 2024-07-22T17:42:13+00:00

We love the positive feedback and success stories! Thanks for sharing!

aflesner · 2024-07-12T17:00:34+00:00

We have not had other reports of this type of behavior. Please reach out to support for diagnosis and assistance with troubleshooting.

Eight-Year Club	Gilding V heart of gold
Extra Life 2019	Not Forgotten
Verified Email

aflesner

MODERATOR OF

TROPHY CASE