How to Request a New Bespoke Application

Bespoke Applications are applications that can't be added to our Back Catalogue.

It means the applications cannot be automatically updated and deployed to your tenants for one or more reasons. Usually, due to parameters that the application developer provides, such as license keys or custom install arguments.

Why can't an application be added to the Back Catalogue?

We are only able to add an application to the Back Catalogue if ALL these conditions are met:

• Installer files are publicly available for download from the publisher's website
• Version IDs are publicly available on the publisher's website
• The application supports silent installs
• The installed application and version appear under Control Panel > Programs and Features
• The application version under Control Panel > Programs and Features matches the application version on the publisher's website
• The application is installed as is from the publisher. i.e. no modifications such as logo, license numbers, activation code, etc.

What happens when I request or submit an application to be added to the Back Catalogue?

When you request a new application to be added to our Back Catalogue, there is no guarantee that the application meets all the requirements.  For our packaging team to confirm whether the requested application is a good fit for back catalogue, they need to complete manual testing and investigation to discern this. Part of this testing includes packaging the application as bespoke.

Requirements to submit a Bespoke Application request

For us to efficiently package and deploy Bespoke Applications we need you to provide:

• The expectation of how the application will appear on a device, for example:
  • The application will show in Programs and Features
  • The application only requires files to be copied from the origin to the destination
  • Registry 
• The download URL or the setup files if the download is not publicly available.
• Silent arguments are required for the application to install silently. Intune deployments don't support user interaction with the installation process.
• List of dependencies required for the application to install.
• Documentation from the application publisher (if available).
• Any requirements such as start menu shortcuts, registry edits and additions, copying of files and folders, and license file or product activation key.

How many revisions are permitted with Bespoke Applications after initial deployment?

We are committed to delivering satisfactory application packaging results. Though, we are also limited by the information provided on the packaging request.

Our packaging team will package the bespoke applications to the best of their knowledge and add any requirements listed by you in your initial request. Once the application is deployed per your requirements, we allow wiggle room for 2 minor changes and 1 major change to the application package.

Examples of Minor changes:

• Add/remove shortcuts
• Add/edit/remove registry keys
• Add license key or activation key to the installation

Examples of Major changes:

• Different software version
• Copy additional files to the installation directory
• Modify installation files

Uninstalling Bespoke Application packages

The process to uninstall Bespoke Applications requires manual investigation, testing, and deployment of a custom-created uninstall package. Our packaging team investigates the silent arguments and deploys the application with the appropriate detection so that Intune can report the uninstallation outcome correctly.

Note: Uninstall applications cannot be deployed alongside install packages due to the complexity of each package and to allow you and our packaging team to narrow down any potential issues.

You can deploy the uninstall package as a requirement to another install package. This will guarantee that an older version of an application is uninstalled before the latest version can be installed.

Can Devicie package ANY application as bespoke?

Unfortunate no, we are limited by the availability of silent install commands provided by you or documentation by the application publisher. We are also limited to the available functions within the installer. e.g. We may not be able to prevent one software from removing another if the package was developed to remove other conflicting software. We are also unable guarantee that what end users' experience in a manual install can be achieved the same way when the software is deployed silently.

How does Devicie package applications that need admin access to install, but also require changes on the logged-on users' profiles?

To reduce confusion and limits errors, we commit to packaging one application or functionality in a single bespoke application. 

If an application requires to be installed as an administrator, our packaging team will package the application as a "System Context" app.

If the application needs to install or make changes to the users' profiles, the application is packaged as a "User Context" app.

Note: If the application needs to both install as admin and then add/remove/modify settings on the users' profiles, we need to treat them as two bespoke applications that are to be packaged separately.

The "User Context" application will be assigned as desired, while the "System Context" one will be set as a dependency to the "User Context" application. Dependencies install first, followed by the application(s) that are dependent on them, in this case the "User Context" application which will make the relevant changes to the users' profiles.

Changes to users' profiles include, but not limited to:

• Registry changes
• Shortcuts creation outside of the main application's functionality
• License deployment
• Copying of files/folders to the users' profiles
• Modifying files/folders on the users' profile