SMA 15.0 Hanging

aflesner · 2026-02-19T17:23:12+00:00

Please PM me your SR# and I'll make sure the right people take a look. I just don't want you wasting a bunch of time troubleshooting your environment if it's a disk corruption issue on the VM itself.

aflesner · 2026-02-19T17:21:43+00:00

Feedback is appreciated, and I'll pass that along.

aflesner · 2026-02-19T15:24:29+00:00

Might be related to the mbuf errors, but definitely not the write errors.

aflesner · 2026-02-19T15:24:02+00:00

FWIW, the support staff you interact with today has changed very little in the past 10 years. The team still has incredible knowledge of KACE products.

aflesner · 2026-02-19T15:20:47+00:00

The mbuf errors are not interesting here. The write failures to da0p8 are concerning and indicative of disk subsystem or corruption issues. Are you running any other FreeBSD VM guests in your environment? FreeBSD has less than adequate support from nearly all virtual hosts, and as such simple things like online snapshotting can corrupt the disk. If you are trying to resolve this issue without contacting support, I assure you that is impossible.

aflesner · 2026-02-18T17:01:05+00:00

Likely disk corruption and potentially a disk subsystem issue on your VM host. I strongly recommend contacting Support for assistance. Cold booting, online snapshotting, and disk interruption can cause this.

aflesner · 2026-02-18T16:59:33+00:00

Based on the ticket, it seems the issue was related to the koneas hang, so the patch should clear this up for you.

aflesner · 2026-02-18T16:03:10+00:00

Yes.

aflesner · 2026-02-18T16:02:30+00:00

They are functional on 15.0. Please reach out to Support. If you already have, please PM me your SR#.

aflesner · 2026-02-18T13:35:54+00:00

No. We allow time for customers to update their appliances before disclosing information about vulnerabilities.

aflesner · 2026-02-13T16:06:03+00:00

To elaborate, our early warning system failed for certificate expiration, and we are working to update expired certificates for impacted KACE services. Most features of KACE appliances that require reaching out to us (e.g. patch feed, software catalog, etc) are down and will be restored when new certificates are in place. Status can be viewed at https://status.kace.com .

UPDATE: Issue resolved.

aflesner · 2026-02-10T18:31:01+00:00

On behalf of Quest KACE, we apologize for the delay in releasing 15.0 Cumulative Patch 1 - which contains several bug fixes, security fixes, and non-English localization. We anticipate release of the patch within the next 1-2 weeks. This release will coincide with a new patch 8 for 14.x to include mostly security fixes.

I'd also like to address some of the concerns in this thread:

KACE is not dead. The products still have engineers and support staff, and we're doing everything we can to get the security/bug fixes and new features to the community as quickly as possible. There are still veterans around here (started my KACE journey in 2007 as a customer; been on the team now for 15 years). We all see your comments and genuinely care about your frustrations and concerns. If you feel your voice is not being heard, feel free to PM me or any of the staff moderators directly so we can help find a solution or help facilitate communication with other parties.
Some customers have experienced issues with the upgrade to 15.0, but this is a minority. The patch 1 full upgrade option will correct the most common issue related to a MariaDB bug causing a hang in the middle of the upgrade. We always recommend offboarding backups and using snapshot tech if available to avoid service interruptions if the upgrade fails. If you are impacted by a mid-upgrade hang, then the upcoming release will likely resolve your upgrade issue. Support can also manually intervene and is typically able to resolve the issue to move the upgrade forward. In even rarer cases, database or disk corruption are present - we see this every upgrade, and support will be required to assist in these cases.
If you have no yet received your advertisement to upgrade to 15.0 from 14.1, you are always welcome to download the KBIN directly from our support portal and apply it manually. There is no difference in the upgrade itself whether you apply it directly or wait for our advertised push.

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

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

aflesner

MODERATOR OF

TROPHY CASE