1 What an application template is
All settings for an application creation can be configured using an Application Template.
For how to create one, see Manage Application Templates. The Application Wizard, the Create tile in Application Management, Create Multiple Applications, Convert Package to Application and Mend can all start from a template.
| Tab in a template | What it holds |
|---|---|
| General | The template name and a description for the applications. |
| Deployment Types | Install, uninstall and repair arguments, supported operating systems, content behaviour, installation behaviour, run times and return codes. |
| Distribution Settings | Distribution points and groups, the ConfigMgr application folder, Package Security Groups, download rules and security scopes. |
| Deployment Settings | Required or available, time base, user notifications, auto install, user collections, implicit uninstall and AD-Deployment. |
| Security Roles | Which security roles may use the template. |
If you pick no template, SoftwareCentral uses built-in default settings. An administrator can choose a default template under Settings › SoftwareCentral › Interface Settings.
2 Best practice
- Make one template per kind of software (for example MSI applications for everyone, and scripted applications for a pilot group), and name them clearly.
- Limit who can use a template with the Security Roles tab, so helpdesk roles cannot pick settings meant for administrators.
- Add the Package Security Groups a template should place new applications in, so new applications are delegated automatically.
- Set the template you use most as the default.