Uploading your own app to Scappman

Support for custom apps is limited, please review this page

Scappman enables you to bring your custom applications to the party and enjoy all of our predefined automation logic.

To upload your app in Scappman, browse the Scappman portal and sign in.

Open the App Store and click "New App".

The upload your app UI has five steps that have to be completed.

Step 1: General information

Required fields:

Parameter	Explanation	Example
App Name	The name of the application that will be used to display it in the Scappman portal and in the Scappman detection rules.	7-zip
Vendor	The vendor name of the application that will be used to display it in the Scappman portal and in the Scappman detection rules	Igor Pavlov
Language	The language for the configuration you're creating. This language will be used in the filter on the Scappman portal and in the Scappman detection rule	English
Icon	The icon that will be used for the application in the Scappman portal and in Microsoft Endpoint Manager. PNG's and JPEG's are supported with a max file size of 200KB and 256x256 pixels.	icon.png
Description	The description of the application in Scappman and Microsoft Endpoint Manager	7-zip is a free and open-source file archiver

Optional fields:

Parameter	Explanation	Example
Notes	Anything you would like to keep track of about the application. This parameter is only available in the Scappman portal	This application only works on Dell devices.
Hardcoded license	Some private applications have a hardcoded license key.	Checked
Programmable license	The license key for some applications can be provided in the install or post-install command.	Unchecked

Step 2: Configuration

Required fields:

Parameter	Explanation	Example
Install Context	The context from which the application will be executed. Some applications require to be install in user context, most work in System context. This parameter will also be set in Microsoft Endpoint Manager	System
Bitness	The Bitness for the application. If 64-bit is selected, the application will be configured to require 64-bit OS in Microsoft Endpoint Manager. If 32-bit is selected both 32-bit and 64-bit will be enabled in Microsoft Endpoint Manager	32-bit

Optional fields:

Parameter	Explanation	Example
Processes	Scappman will check these processes to see if the application is running, if so, we show a notification to the user. Process names should be comma separated and .exe should always be added.	Chrome.exe,firefox.exe,...
Apps & Features name	When an application is made available, Scappman will push a secondary update app that checks to see if it can find a previous version of that application. That check is based on the name of the application in Apps & Features. The parameter accepts wildcards (*). If this parameter is left empty you will not be able to selected Available or Uninstall as assignment type for this application.	7-Zip*
Enable Dependency	When this is checked, the UI will suggest to create a dependency for the specific app. The text in the textbox is what will be displayed when creating the installation.	This application has a dependency on xxxx. Please create an installation for xxxx first and link it here.

Step 3: Select the file you want to upload

In step 3, you can upload the file that you want Scappman to package for you.

Suggested file types: EXE, MSI, PS1, ZIP,

Step 4: Installation Commands

The installation commands will be injected into the Scappman PSADT template. Some examples have been added for your convenience, but any PowerShell command will work.

Examples

Here are some examples for step 3 & 4

Chrome

Firefox

Zip file

File copy

For more information on PSADT install commands, click below

Install Command Cheat Sheet

Step 5: Detection rules

On this step the detection rules that will be used by Microsoft Endpoint Manager can be configured. The script detection rule cannot be used in conjunction with other detection rule types and only 1 MSI detection rule can be created.

An easy way to get the MSI product code is by running either of these PowerShell commands:

Get-Package -Name '<AppName>' | Select-Object TagId

Get-WmiObject Win32_Product | Where Name -eq '<AppName>' |Format-Table IdentifyingNumber, Name

Substitute <AppName> for the Name of the application as it exists in Programs and Features

Scappman also uses placeholders that are replaced by the API upon package creation to simplify updates and changes.

Placeholder	Replaced by
<PACKAGENAME>	Value in App Name field in step 1
<PACKAGEVENDOR>	Value in Vendor field in step 1
<VERSION>	Value in Version field in step 2
<ARCHITECTURE>	x86 or x64, based on the toggle selected in step 2
<PRODUCTCODE>	Value in MSI Product code detection in step 5
<INSTALLERFILE>	Name of the primary installer file in step 3
<LANGUAGE>	2 letter language code for the language selected in step 1