Endpoint Services, MECM, Creating an MECM application


Follow this guide to create an MECM application with the considerations of our MECM environment in mind.


Microsoft Endpoint Configuration Manager (MECM)

Intended Audience

University of Illinois IT Pros leveraging MECM, hosted by Technology Services' Endpoint Services team

General Information

Microsoft's documentation covers the steps for creating an application for deployment via MECM. LinkedIn Learning also provides a training video:

Please note the local considerations below before creating the application.

Local considerations

You'll need to have the following in place:

  • The content source location will need to grant the relevant MECM primary site server read/execute permissions so that the content can be accessed. Using a Distributed File System (DFS) namespace (of the form \\<DOMAIN.NAME>\<dfsroot>\<path>) to identify the content source location is preferred over using an UNC path to an SMB/CIFS-accessible fileshare (\\<SERVER>\<path>\<subpath>). A DFS namespace is preferred over a UNC path because if the source content ever needs to move servers it's easier to reconfigure the DFS namespace to a new share than to edit the UNC source location for each and every piece of leveraged content.

    • Grant the primary site computer account read/write access to the share. Here's a list of the primary site computer accounts to use, add the account(s) for your campus:
      Campus Account
    • You'll need to supply the DFS namespace or UNC path to this fileshare; referring to drive letters will not work properly. Drive letters are per-user references that MECM is not able to resolve.

  • Add the UIUC-YourUnit prefix when creating the application (or any custom content)

Tips for avoiding unnecessary work

  • Reference the following sites for guidance on the silent installation options for various application installers
  • Test the application deployment on a test endpoint that matches your environment

  • Avoid creating multiple entries that refer to the same publisher or author (such as "Mozilla, Inc.", "Mozilla Inc.", and "Mozilla"). Similarly, avoid making duplicate 'administrative categories'; please check existing categories before creating your own.

  • In the wizard, typically you'll select that you wish to "Always obtain files from a source directory" so the installer file will be copied to the endpoint. If you're making a package that only runs a command, select "This package does not contain any source files".

  • If your content has dependencies, select the deployment types in the 'Dependencies' tab of an application's deployment type. Paint.net is an example of an application that depends on the latest version of .NET.

You can set all of the fields in the wizard when you import an MSI, and Microsoft's documentation covers this.

Related links

Contact the EPS team

Keywordsapplication, EPS, SCCM, TechS-EPS-SCCM MECM   Doc ID79451
OwnerEPS Distribution ListGroupUniversity of Illinois Technology Services
Created2018-01-18 14:00:04Updated2023-09-11 10:46:45
SitesUniversity of Illinois Technology Services
Feedback  0   0