Systems

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.
  • For MSI applications, follow this section of the documentation
  • For non-MSI applications, follow these sections:
    1. Manually specify application information
    2. Manually specify the deployment type information
       
       
• LinkedIn Learning also provides a training video - 'Manage Apps with Configuration Manager'
  • Sign in with your @illinois.edu email at https://www.linkedin.com/learning/
  • Open the training: https://www.linkedin.com/learning/manage-apps-with-configuration-manager/the-application-wizard?autoplay=true&resume=false&u=43607124
  • On the left panel, start with 'The Application Wizard' under '1. Create Applications' and continue through the end of '2. Deploy Applications'.
    
    
• Please note the 'Local considerations' and 'Tips for avoiding unnecessary work' sections 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>), 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
    Chicago	SCCMUICPS1$
    Urbana-Champaign	SCCMUIUCPS1$ SCCMCASMS$

  • 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 sources for guidance on the silent installation and uninstall options for various application installers
  • http://unattended.sourceforge.net/installers.php
  • InstallShield command-line parameters
  • https://chocolatey.org/packages
    • The scripts under each application's 'Files' section contain the silent installation and uninstallation commands
  • https://www.itninja.com/software
  • https://silentinstallhq.com/
  • Some application vendors provide documentation on silent installations of their products
  • After an application installs, sometimes an uninstall application or uninstall shortcut (that contains the appropriate command line) will be available.
    • The uninstall app or shortcut may be in the application's installation folder or Start Menu folder
      
      
• Test the application deployment on a test endpoint that matches your environment (e.g. an AD OU with similar GPOs and a collection with similar MECM deployments)
  
  
• 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 .NET.

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

Related links

• https://learn.microsoft.com/en-us/mem/configmgr/apps/deploy-use/create-applications—official Microsoft documentation on this procedure.
• https://4sysops.com/archives/how-to-deploy-an-msi-package-with-sccm-2012/—third-party documentation

Contact the EPS team