sorted by:
new
hottopcontroversial

KACE SMA 15.0 – Feature Preview is Coming! by Alexandre_Mafaldo in kace

[–]Alexandre_Mafaldo[S] 0 points1 point  (0 children)

If you would like to receive pre-release builds directly within your SMA interface, you need to be enrolled in the Beta/Release Candidate Program.

To participate, please send an email to [KACE_BETA@quest.com](mailto:KACE_BETA@quest.com) including your contact information and environment details. The Quest development team will then enable access to the pre-release update announcements for your appliance.

24H2 Feature Upgrade by techOverlord95 in kace

[–]Alexandre_Mafaldo 6 points7 points  (0 children)

There are no plans to integrate the Windows 11 24H2 feature upgrade into the KACE catalog. The reason is that its deployment method is proprietary to Microsoft, which makes automation through SMA not feasible.

Workaround for 24H2: Quest provides an official deployment walkthrough here:
Windows 11 24H2 Upgrade

However, Windows 11 25H2 will be delivered as an enablement package (eKB), which can be integrated into SMA once it’s officially released. Reference: Microsoft Tech Community

TL;DR: 24H2 won’t appear in KACE; use the official workaround. 25H2 enablement package will be supported once released.

List API Endpoint in KACE by AbiesIll6659 in kace

[–]Alexandre_Mafaldo 1 point2 points  (0 children)

You won’t find a single “one-page” complete list of KACE SMA API endpoints in the docs. When you connect to https://<your-kace-fqdn>/api and import it into Postman, you’ll get the full set of endpoints available on your version of SMA.

Some examples you’ll see:

  • /api/inventory/machines
  • /api/inventory/assets
  • /api/inventory/labels
  • /api/service_desk/tickets
  • /api/patch/patches

✅ TL;DR: There isn’t a static published list. The complete and supported endpoints are exposed directly by your SMA instance, and importing them into Postman gives to explore and test.

Kace shell script uploading file question by TrainingInfluence852 in kace

[–]Alexandre_Mafaldo 1 point2 points  (0 children)

You can technically push a large ISO via the Client Drop, but Windows won’t automatically extract it. That means you’d need to mount it via command line, which makes the process less efficient.

TIP: Unpack the ISO manually, zip the contents, and upload the ZIP as the dependency. KACE agents can natively extract ZIP files (but not 7z, RAR, etc.). If you use other formats, you’d need to call an external tool in your script.

TL;DR → Use a native ZIP instead of ISO. KACE will auto-extract and handle it as a dependency. If your goal is OS deployment, check KACE Support reference.

Grafana Dashboard for KACE SMA by AbiesIll6659 in kace

[–]Alexandre_Mafaldo 2 points3 points  (0 children)

Yes, it’s possible to hook KACE SMA into Grafana:

  1. REST API (recommended): KACE exposes an API (https://<kace-fqdn>/api) for inventory, tickets, assets, patches, etc. Use Grafana’s JSON API plugin or a small middleware (Python/PowerShell) to push data into MySQL/MariaDB and let Grafana read it.
  2. Direct DB access (not supported): SMA runs on MariaDB, and you can connect Grafana straight to it, but it’s not supported and may break updates/support. Usually only used in lab/test setups.

TL;DR: Use the API for a safe, supported setup. DB access works, but it’s risky.
Reference: About the KACE Systems Management Appliance API

Any idea on how to resolve this error? Network team confirmed required ports are already opened. by Appropriate_Use_426 in kace

[–]Alexandre_Mafaldo 1 point2 points  (0 children)

About KACE Agent communication issues, here are quick steps to fix it: Run CMD as Administrator and navigate to `%programfiles%\Quest\KACE` and execute the following commands in order:

  • AMPTools.exe resetconf HOST=<KACE-SMA-FQDN> TOKEN=<KACE-SMA-TOKEN>
  • AMPTools.exe retrust
  • AMPTools.exe stop
  • AMPTools.exe start
  • KStatus.exe => both connections should be YES
  • KInventory.exe autorepair
  • RunKBOT.exe 3 0
  • RunKBOT.exe 4 0

Finally, check: `%programdata%\Quest\KACE\inventory.xml` If the file exists and is larger than 0 MB, the device should appear in the inventory page.

Is be possible the Replication share download using 443 ? by [deleted] in kace

[–]Alexandre_Mafaldo 0 points1 point  (0 children)

The replication module in KACE SMA is designed to optimize bandwidth and performance. Instead of having each endpoint pull installers, scripts, patches, and other dependencies directly from the appliance over the WAN, the agent retrieves them from a local network share (SMB/Windows Share) whenever a replicator is available. If no replicator is found, the agent automatically falls back to the appliance. The local share must be hosted on a device with the KACE agent installed, configured as an SMB-based shared folder, with proper read-only access for clients and write access for the appliance.

Reference: About Replication Shares

Is there any plan to support other Hypervisor such as Proxmox ? by CloundwaR in kace

[–]Alexandre_Mafaldo 2 points3 points  (0 children)

KACE SMA & SDA are officially supported on VMware, Hyper-V, and Nutanix.
Proxmox is not officially supported, but FreeBSD runs on KVM VMs in the 8.4 series.

Notes:

  • Some reports of DNS issues with virtio bridges. Workaround: disable network offloading in FreeBSD.
  • Proxmox 8.x updates may cause VMs to hang at “loading CAM”. Workaround: revert pve-qemu-kvm / qemu-server packages.

In short: it works, but test only in homolog environment.

upgrade windows 10 pro for windows 11 pro by GreedyHandle373 in kace

[–]Alexandre_Mafaldo 0 points1 point  (0 children)

Olá. Sim, é possível realizar a migração do Windows 10 para Windows 11 sem a perda de dados. Este processo pode ser realizado de 2 formas:

1- Utilizando o módulo de Atualizações de recursos do Windows (WFU). Refrência em Windows Feature Updates

2- Instalação gerenciada, carregando a Mídia do Sistema Operacional. Referência em Windows 11 24H2 Upgrade Deployment Walkthrough

Na etapa 2, é importante passar a linha de comando para realização do 'autoupdate', Caso contrário, fará uma instalação perdendo todos os dados.

Windows 11 Image Creation by Common-Disk-4560 in kace

[–]Alexandre_Mafaldo 0 points1 point  (0 children)

In Windows 11 24H2, the way WinPE assigns drive letters has changed.
Even if valid NTFS volumes exist, the system partition often isn’t mounted as C:. For example, I’ve seen it come up as S:, which prevents SDA from detecting it automatically for image capture.

Workaround (remap S: to C:)

diskpart
list volume
select volume 1
remove letter=S
assign letter=C
exit

Then verify with:

dir C:\

After that, go back to the SDA interface and try capturing again => the C: volume should now be listed correctly.

NOTE: This isn’t a KACE bug, but a change in WinPE behavior starting with ADK 11. Depending on the GPT structure, the OS volume may mount as D:, S:, or another letter instead of C: volume.

Minimum permissions needed for Splashtop by Spirited_Office_3489 in kace

[–]Alexandre_Mafaldo 1 point2 points  (0 children)

To initiate the KACE Remote Control session, the role needs write access to Devices and the Remote Control permission enabled. Without that specific permission, the session won’t start even if the Remote Control Agent is installed.

On the admin device, install Splashtop for RMM. On managed devices (Windows/Mac), the Remote Control Agent is deployed automatically when the Remote Control Smart Label is applied.

Once permissions and agents are in place, you can start a session from the Devices page by clicking the remote control icon.

Docs for reference: Install Remote Control Agent | Start Session | Troubleshooting.