I've uploaded Utils.zip to Packages, containing procexp.exe and some other utilities, and specified C:\Windows as the desired destination folder in the Command field. When deploying to Windows Server the log says:

Package installer successfully completed, command = unzip 'C:\NetXMS\var\Utils.zip' -d 'C:\Windows'

I can see Utils.zip in var, but the extracted files are nowhere to be found. I also tried C:\Temp as destination, same result.

Another thing I noticed is that the Package deployment process isn't shown in a new tab on the node anymore. This worked in 5.1.3 at least.

NetXMS Server: 5.2.6
NetXMS Agent: Tested 5.2.6 and 5.2.7

Pls try to put
DebugLevel = 6
into agent configuration file and collect logs for the moment when the package is being deployed.

There's now Package Deployment Job under Configuration.

Ah, there is a clue:

2025.11.10 11:33:54.355 *D* [installer          ] Starting package installation using command line unzip 'C:\NetXMS\var\Utils.zip' -d 'C:\Windows'
2025.11.10 11:33:54.355 *D* [procexec.7         ] ProcessExecutor::executeWithOutput(): process "CMD.EXE /C unzip 'C:\NetXMS\var\Utils.zip' -d 'C:\Windows'" started (PID=5104)
2025.11.10 11:33:54.386 *D* [installer          ] Installer output: 'unzip' is not recognized as an internal or external command,

operable program or batch file.


2025.11.10 11:33:54.386 *D* [procexec.7         ] ProcessExecutor::readOutput(): stopped on GetOverlappedResult (The pipe has been ended.)
2025.11.10 11:33:54.386 *I* [installer          ] Package installer successfully completed, command = unzip 'C:\NetXMS\var\Utils.zip' -d 'C:\Windows'
2025.11.10 11:33:54.386 *D* [comm.cs.2          ] Sending message CMD_REQUEST_COMPLETED (ID 6; size 32; uncompressed)


Agent has a copy of unzip that gets installed into C:\NetXMS\bin and we can add this to agent's config

[ENV]
PATH=%PATH%;C:\NetXMS\bin

so that agent would be able to run this unzip binary, but then there's another issue as agent puts parameters for unzip in single quotes and unzip does not like that.

I've created a ticket for all this - https://track.radensolutions.com/issue/NX-2862.

Currently you can make a self-extracting binary and ship is as executable package. Or may be you can just put the .zip file and set it as executable and then in Command field you can put the actual unzip command, file location will be in ${file} macro.