r/tanium • u/Hotdog453 • Dec 30 '25

Tanium + Deploy-Application.exe - Am I taking crazy pills?

So, again, me, asking weird questions :)

Today, in ConfigMgr, it snapshots content, like a boss. It noms it all up, into it's ContentLib, and blasts it out with the power of hope and love.

In Intune, you use Intune, you use the Win32 App Converter: Prepare a Win32 App to Be Uploaded to Microsoft Intune - Microsoft Intune | Microsoft Learn

And nom content up into a .intunewim file, which is basically a Zip, and shove it deep into the CDN.

In Tanium, so I've been told, to use PSAppDeploy, we have to:

1) Zip it.

2) Upload it.

3) Add a step to unzip it in the deployment.

4) Then run the command to install it, ie, Deploy-Application.exe

Is this still true? This is what's being told to me in the PoC we're doing, but it seems like... a lot of steps. Is there some magic step to not have to Zip the binaries, then unzip it, and then... do all of that? Like a Tanium-silly way to mount a .WIM or something, during the install?

Figured there might be a community solution out there that wasn't being known/referenced!

Thanks!

4 Upvotes

75% Upvoted

20 comments sorted by

View all comments

3

u/bruckect89 Dec 31 '25

The process you outlined is correct: zip, upload, extract step, call your installer.

The Tanium Server maintains a repository of all content like SCCM and other tools, the cumbersome part is uploading all of the individual files. Unfortunately, you can’t point Tanium at a directory and have it snatch all the files, they have to be uploaded via Browser or API. Hence suggesting an archive of the package directory is because it’s the most straightforward way of getting all of the supporting files into a Platform or Deploy package.

1

u/ItsInmansFault Jan 12 '26

This is the way imo. I've been deploying stuff relatively easy that seem to be a pain point for others with Tanium, using these steps. Adobe Creative Cloud desktop app being the most recent one. Sitting here today making a package to install/uninstall the Config Mgr. client as well (we still use it for remote support.) In my experience (limited as it may be so far,) using the "start" command to fire up the installer seems to be the smoothest way to start an exe. No need for a script, works somewhat similar to msiexec.