Configuration Manager/Create and deploy an application
Overview
In most cases, administrator privileges are required to install software. However, in an organization, IT will not grant administrator privileges to domain accounts for security reasons. Users can call the helpdesk for support, but with the help of the Software Center, users can install, repair, or uninstall software by themselves. This can significantly reduce the number of calls and improve IT productivity.
Prerequisites
- The account used to operate must have an appropriate security role to perform the site server.
- A share to store the installation package and allow users to access it.
Create an application
Note:
This article takes the deployment of Adobe Acrobat Reader as an example.
Start the wizard

Go to the Software Library → Application Management → Applications.
Right-click the blank and select Create Application.
Specify application information

- Enter the application name in the Name box.
- Enter comments, publisher, and version to more easily identify the software.
- Create and select an administrative category to sort the software.
- Select a date for publishing.
- Specify users or groups responsible for this application as Owners and Support contacts.
Specify the software center entry

- Select the language for the application.
- Enter the application name, recommended to keep the same as the previous step.
- Browse and select the installation package to add the software icon.
- Provide additional information if needed.
Configure information for deployment type

Enter the name and comments for the deployment type. Select a language and click Next.
Configure content for deployment type

- Select the share where the installation package is located.
- Enter the package name and installation properties.
- Specify an uninstaller for the application, it can be a script.
Configure detection method for deployment type

Software Center determines if the application is installed on the device by configuring the detection method.
Click Add Clause to add a method.

- Setting Type
- For most cases, select File System.
- It determines whether the application is installed by whether this file exists.
- Type
- Select File.
- Some applications leave empty directories after uninstallation, which leads to incorrect detection.
- Path
- Specify the detection path, you can use environment variables.
- File or folder name
- Specify the name of the EXE program.
- This file or folder is associated with a 32-bit application on 64-bit systems
- Always check this to avoid the coexistence of 32-bit and 64-bit programs.
- The file system setting must exist on the target system to indicate presence of this application
- If the file exists, the application is considered to be present.
- The file system setting must satisfy the following rule to indicate the presence of this application
- If the file satisfies the rule, the application is considered to be present.
Configure user experience for deployment type

- Installation behavior
- Select to install for system or user.
- Logon requirement
- Select whether to require login for installation.
- If you select Install for user in the Installation behavior drop-down box, you can't change this option.
- Installation program visibility: Specifies how many activities or notifications to display in the deployment.
- Maximized: Deploy the application with all activities or notifications displayed.
- Normal: Deploy the application with activity notifications displayed based on the system and program. This option is the default.
- Minimized: Deploy the application with fewer activities or notifications displayed. Users might see them in the notification area or taskbar.
- Hidden: Silent installation, no activity or notifications.
- Allow users to view and interact with the program installation
- Always check it for compatibility.
Configure requirements for deployment type

Software Center determines whether an application can be installed on the device through requirement rules.
Typically, this is not required and should not be configured. For installation of large programs or industry software, it should be configured to call the Helpdesk for manual installation.
Click Next to proceed.
Configure dependencies for deployment type

Software Center determines the dependencies that must be installed before an application can be installed using this deployment type.
Typically, there is no need to install dependencies in advance. Most software installation packages have integrated dependencies (such as runtime), which are installed silently during installation.
Click Next to proceed.
Deploy an application
Start the wizard

Go to the Software Library → Application Management → Applications. Select and right-click an application, and then select Deploy.

- Use default distribution point groups associated with this collection
- Store the application content on the collection's default distribution point group.
- Automatically distribute content for dependencies
- Check if the dependencies of deployment types of the application have been configured.
Specify distribution points

Click Add to add one or more distribution points or distribution point groups for this application.
If you selected Use default distribution point groups associated with this collection in the previous step, this option is automatically populated.
Configure deployment settings

- Action
- Select whether this deployment is to Install or Uninstall the application from the drop-down box.
- If you have created deployments for installation and uninstallation, the Install deployment takes priority.
- Purpose: Select Available or Required from the drop-down box.
- Available: Install the application on demand.
- Required: Install the application according to your schedule.
- Allow end users to attempt to repair this application
- Check if you configured a repair for the application.
- Require administrator approval if users request this application
- Before enabling, additional configuration is required.
Note:
The following options are only available when the deployment is Required.

- When a resource is no longer a member of the collection, uninstall this application
- Uninstall the application when removing the device from the target collection.
- Pre-deploy software to the user's primary device
- If the deployment is to a user, deploy the application to the user's primary device.
- Don't select this if the user must interact with the installation.
- Send wake-up packets
- Send a wake-up packet to computers before the client runs the deployment.
- Allow clients on a metered Internet connection to download content after the installation deadline, which might incur additional costs
- Do not select this option unless necessary.
Configure scheduling settings

- Schedule the application to be available at
- Make the application available to clients after a certain time.
- Installation deadline: This option is only available when the deployment is Required.
- Delay enforcement of this deployment according to user preferences, up to the grace period defined in client settings: Give users more time to install required applications beyond any deadlines you set. You can configure the grace period in client settings.
Configure user experience settings

- User notifications: Select one of the following options.
- Display in Software Center and show all notifications: Display all notifications to users on the client computers.
- Display in Software Center, and only show notifications for computer restarts: Notify the user only when a reboot is required.
- Hide in Software Center and all notifications: Hide shows all notifications, you can't select the option for available deployment purposes.
Select other options if needed.