Intune Application Templates

1 Open the templates

The administration interface for Intune application templates is found under the Settings menu.

Click Settings in the top bar.
Click Intune Application Templates.

The Settings menu open, listing Security Roles, Package Security Groups, Intune Application Templates, Application Templates, Package Templates, Program Flags and Advertisement Flags. Intune Application Templates is the third group of items. — The **Settings** menu. Click **Intune Application Templates**.

The Intune Application Templates page with the Add new template button and a search box on the left. The list shows the template names, each with Edit and Delete links. — The template list. **Add new template** starts a new template. **Edit** and **Delete** are on each row.

From this interface you can manage the existing templates and add new templates.

2 Add, edit and delete

Add: click Add new template, fill in the tabs described below, then click Save.
Edit: click Edit on the template's row, change the tabs you need, then click Save.
Delete: click Delete on the row. In the window, click Delete to remove the template, or Cancel to keep it.

Templates are stored in SoftwareCentral only Saving or deleting a template changes only SoftwareCentral's database. Nothing is written to Intune until you create an application from a template on the Intune Applications page.

The settings are on six tabs: General, Program, Requirements, Tenants, Distribution and Security. Each is described in its own section below.

3 General

On the General tab, enter the name of the template and the information about the application.

Setting	What it does
Template name (required)	The name of the template, up to 128 characters. Names must be unique; the check ignores upper and lower case.
Application description	The description is visible to end users in the company portal. It starts as “Created by SoftwareCentral”.
Is featured	Tick Show as a featured app in the Intune Company Portal to set the application as featured, as the label says.
Create Groups	Tick Create Required Install Group, Create Available Install Group and/or Create Uninstall Group for the groups to create with each application. Check the groups in Intune after the first import.
Assign new groups to another group	Search for a group to place the new groups in. Leave it empty to create them without a parent group.
Scope Tags	The scope tags given to the applications created from this template.

Add new template window on the General tab: Template name, Application description with the text Created by SoftwareCentral, Is featured checkbox, three Create Groups checkboxes, Assign new groups to another group and Scope Tags. Save and Cancel at the bottom. — The **General** tab of a new template. **Template name** is required.

4 Program

From the Program tab, you specify the commands used to install and uninstall the program.

Variables {file_name} and {product_code} are variables that are replaced by the actual values when an application is imported. {file_name} becomes the name of the installer file, and {product_code} becomes the product code of the MSI.

Setting	What it does
MSI Install Command Line	The install command for MSI packages. Default: `msiexec /i "{file_name}" /q`
MSI Uninstall Command Line	The uninstall command for MSI packages. Default: `msiexec /x "{product_code}" /q`
Script/EXE Install Command Line	The install command for script and EXE packages. Default: `"{file_name}" -DeployMode Silent`
Script/EXE Uninstall Command Line	The uninstall command for script and EXE packages. Default: `"{file_name}" Uninstall -DeployMode Silent`
Allow available uninstall	Tick Allow available uninstall to let users uninstall the application from the company portal.
Installation time required (mins)	How long the installation may take. Default: 60 minutes.
Install behavior	System (the default) or User.
Device restart behavior	What Intune does on a restart. The options are Determine behavior based on return codes, No specific actions, App install may force a device restart (the default) and Intune will force a mandatory device restart.
Return codes	Return codes and their code type (for example Success, Soft reboot, Hard reboot or Retry). Use Add return code to add one, and the red cross to remove one.

Add new template window on the Program tab: the MSI install and uninstall command lines with the file_name and product_code variables, the Script/EXE install and uninstall command lines, Allow available uninstall, Installation time required, Install behavior, Device restart behavior and a table of return codes with code types. — The **Program** tab with the default command lines and five return codes.

5 Requirements

From the Requirements tab, you specify the requirements that devices must meet before the application is installed.

Setting	What it does
Operating system architectures	Tick 32-bit and/or 64-bit. Both are ticked by default.
Minimum Windows release	The lowest Windows release. The default is 1607. If the release you need is not in the list, type it in the drop-down box.
Disk space required (MB)	The free disk space the device needs.
Physical memory required (MB)	The memory the device needs.
Minimum number of logical processors required	The number of processors the device needs.
Minimum CPU speed required (MHz)	The CPU speed the device needs.

Add new template window on the Requirements tab: 32-bit and 64-bit checkboxes, Minimum Windows release set to Windows 10 1607, and empty boxes for disk space, physical memory, logical processors and CPU speed. — The **Requirements** tab. The release drop-down accepts a value that is not in its list.

6 Tenants

From the Tenants tab, you define which Intune tenants applications will be created on.

Applications will always be created on the tenant the user has selected. Tick a tenant here to create the application on that tenant as well.

Leave the list empty for one tenant Do not select any tenants on this screen if you only want to create the application on the tenant currently selected by the user.

Add new template window on the Tenants tab: an instruction that tenants selected here are copied to, a list with a TENANT column and one row with a checkbox. Tenant names are masked. — The **Tenants** tab. Only the tenants you are allowed to manage are listed. The tenant name is masked in this picture.

7 Distribution

From the Distribution tab, you define which Package Security Groups an application will be added to when it is imported.

The groups you tick are the Package Security Groups that can see the applications imported with this template.

Add new template window on the Distribution tab: a list of Package Security Groups with checkboxes. Two groups are ticked. Group names are masked. — The **Distribution** tab. The group names are masked in this picture.

8 Security

From the Security tab, you control which security roles are allowed to see this application template.

Tick the security roles that may see the template. The same can also be controlled from the security roles interface.

Add new template window on the Security tab: the instruction to select the security roles allowed to see the template, and a list with a SECURITY ROLE column and checkboxes for Application Manager, SoftwareCentral Administrators New, test and Test Role. — The **Security** tab. Tick the roles that may see the template.

9 Best practice

Leave Tenants empty unless the application must go to other tenants. A template that names tenants creates the application on those tenants as well as on the user's own tenant.
Keep the {file_name} and {product_code} variables in the commands. They are replaced with the real file name or MSI product code when the application is imported.
Tick only the Package Security Groups and roles that should see the applications. The Distribution and Security tabs decide who can see the applications imported with the template.
Know when a change takes effect. Saving a template does not change applications that already exist in Intune. The saved template is used for the applications you import after that.
Give each template one clear name. Names must be unique, so a second template for a similar installer should have its own name.

10 Troubleshooting

Symptom	Cause	What to do
“Template name cannot be empty.”	The Template name box is empty.	Type a name on the General tab, then click Save.
“A template with the same name already exists.”	Another template has the same name. The check ignores upper and lower case.	Choose a different name.
The window stays open after you click Save, and no message is shown	An unexpected error occurred while saving. SoftwareCentral writes the error to the Log but does not show it on the window.	Check the Log for the details, then try again.