Of course DeployR can install your apps

Installing apps is generally a straightforward task: Take this set of content, run this command, wait for it to finish, make sure it succeeded.  That’s what DeployR implements.  You can create an application with the command to execute, and then upload a folder of content (which, as with drivers, DeployR will compress into a .wim file for compression and download efficiency, extracting it on the fly before running the install command on the device).  No need for anything overly complicated (e.g. the ConfigMgr app model).

You can then reference that app in the task sequence, either in a step that installs a single app:

Or one that installs a list of apps in the order specified:

That list could also be determined dynamically (e.g. by calling a web service or calculating it via a PowerShell script).

Based on feedback from early DeployR customers, we also added the ability to use .intunewin files (the same packages that you upload to Intune, created by IntuneWinAppUtil.exe) directly in the DeployR – no need for you to use different installation files in DeployR and no need for us to compress that one file into a .wim file since it is already compressed.  So, you can just upload that original .intunewin file to DeployR, configure the same command line that you would use in Intune, and you’re all set.  We will automatically extract the app installation files, then run the installation command line with those extracted files.  The nice part of this is that it guarantees the same installation as from Intune (since it’s the same content and command line), so detection rules in Intune will work great, allowing for ongoing management of the app (e.g. updating it).

If you prefer using something like PSADT to wrap your applications, you can certainly use those in DeployR as well – from our perspective, it’s just another app (content plus command line).

It’s also worth mentioning that all the content stored in DeployR (apps, driver packs, OSes, boot images, etc.) is fully BranchCache-enabled, so instead of every client needing to download from the server they can instead pull some or all the content from nearby peers.  Peer-to-peer monitoring, management and efficiency (for both BranchCache and Delivery Optimization) are 2Pint specialties.