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.
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.
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.
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.
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.
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.
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.
select the default profile that we just created.
Then browse to the package that you want to import and select the MSI file and click next.
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.
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.
Select any distribution point or group, if you want the package to be replicated to them. Click Next.
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
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.
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!