Import your first package into SCCM in three simple steps using SCCM Importer.

No Comments 4553 Views1


This tutorial will show you how to import your first packages using SCCM Importer. Invest 4 minutes and you will never add packages using the SCCM Admin Console again.

Intro

Hi and welcome to this getting started tutorial. First, I will talk a bit about the general settings of SCCM Importer and then I will help you create your first template followed by importing packages in different ways.

Step 1 – Verify General Settings

Let’s start with general settings. Click on the Settings button in the ribbon to launch the Manage Settings Wizard.

Launch the settings wizard from the ribbon

Launch the settings wizard from the ribbon

Here you could change the path for the import templates that we will soon create. If you have several coworkers you could change the local path to a network path to start sharing your templates. The same is possible for the repository settings, so that your coworkers can access the desired repositories without the need to specify credentials etc. The package cache is where SCCM importer stores the downloaded applications. And finally, you can change the path to the log files.

Manage Settings Wizard

Manage Settings Wizard

If you are running into problem importing applications with SCCM Importer you can enable verbose logging to get a lot more details during an import. I generally recommend to only enable verbose logging if you are troubleshooting else you can leave it as is. Click next to get to the proxy screen where you can add a proxy if needed.

Manage Settings Wizard - proxy settings

Manage Settings Wizard – proxy settings

Step 2 – Create a Template

Now once the general settings are taken care of, the next step is to create an import template. Open the Manage template wizard by clicking on the Templates button.

Launch the Manage Template Wizard from the ribbon

Launch the Manage Template Wizard from the ribbon

In this short tutorial, we will create a default template with a minimum amount of settings to get started. There are a lot more settings available if you create a custom template. To create your first template, fill in the name of the SCCM server and the network path you would like to set as the top-level source directory. We will create a subfolder for each package you will import and SCCM will use that folder as a source directory.

Manage Template Wizard - first startup

Manage Template Wizard – first startup

Click Create template and you are done (An autogenerated profile will be created with default settings).

Step 3a – Import a Package Into SCCM

I will now show you the two most common ways to import packages. First I will show you how to import a package manually by reading information from the MSI file. Then I will import a package from a repository using our Batch Import feature. Let’s start with the manual import. Select From folder in the ribbon menu.

Ribbon Menu - From Folder

Ribbon Menu – From Folder

select the default profile that we just created.

Application Iimport wizard - select template

Application Iimport wizard – select template

Then browse to the package that you want to import and select the MSI file and click next.

Application Import Wizard - Select Content to Import

Application Import Wizard – Select Content to Import

As you can see, we have read the application name, manufacturer, version and language from the selected MSI file, populating the variable fields to create names for all objects that the SCCM Importer will create during the import. You can see changes to the objects directly when changing any of the variables.

Application Import Wizard - Naming Conventions

Application Import Wizard – Naming Conventions

The default template will only create the minimum number of objects needed to import a package. Create your own custom template to enable tons of settings, including custom naming convention, security scopes, default distribution points and more. Click next to continue.

If the package has any dependencies or will supersede an existing package, you can specify it here. Click Next.

Application Import Wizard - Relationships-dependencies-supersedence

Application Import Wizard – Relationships-dependencies-supersedence

Select any distribution point or group, if you want the package to be replicated to them. Click Next.

Application Import Wizard - Distribution Points - Distribution Groups

Application Import Wizard – Distribution Points – Distribution Groups

In the advanced wizard step you could change many of the settings the we have filled in for you, including making the deployment required at a specific date. Click Import package to start the import.

Application Import Wizard - Advanced -Required Deployments

Application Import Wizard – Advanced -Required Deployments

Step 3b – Batch Import a Package Into SCCM

While the package is imported in the background, I will show you the second and most convenient way to import a package. Select any package from the free repository and download it. Right click and select Batch import into SCCM. Select the same profile as before. What happened in the background is that we detected a custom import XML file in the downloaded package. This file contains everything we need for a successful import, from install and uninstall command lines to the name of the application. This mean that you don’t have to verify and change the autogenerated info from the MSI file for each import. Click Import all to start importing the package.

Batch Import - select template

Batch Import – select template

While the package is importing in the background, open the output window to see the progress. In a few seconds the package will be successfully imported!

SCCMImporter - package completed successfully

SCCMImporter – package completed successfully

Leave a Reply

Your email address will not be published. Required fields are marked *