Getting started with upload Software Packages
Introduction
In order to deploy software or operating systems the required packages needs to be prepared, uploaded and registered at the server. This getting started describes the options to prepare and upload the packages for the various package types. Depending on your licensing model, you have two options for the subsequent upload of packages. On the one hand, packages can be uploaded via the Unified User Experience or directly to the system's repository as described below.
Package Preparation
The first step before uploading and distributing packages is to prepare the corresponding package for processing in the target system.
Package Types
The following packages types are supported:
- Empirum
- Software Package
- Operating System sources
- Language Packs
- PXE images
- Driver packages
Package Preparation
In order to upload software to Empirum they need to be provided as a *.zip file in the Empirum import format. To do this, do one of the following, depending on your package type:
- Software Packages
- Use the Empirum Package Wizard to create a new software package. Install the Matrix42 Packaging Center on a Windows computer and use the option Package Wizard to create a new Empirum software package. Choose to create a *.zip file at the end of the process to allow the upload.
- Export an existing package from the Empirum package library of an other Empirum server. In the Matrix42 Empirum Management Console -> Configuration -> Software Management -> Depot -> right click on a software package and choose Export Package... The package needs to be zipped before uploading it.
- Empirum Software packages can also be integrated via the Matrix42 PackageCloud integration. This allows the instant use of hundreds of prepackaged software packages. Please refer to Software Distribution IV: Distribute via PackageCloud for additional information.
- Operating System source
- Install the Matrix42 Packaging Center on a Windows 10/11 computer and use the option Prepackaged OS Wizard to create an import ready operating system source.
- Before the Windows operating system (ISO) files can be imported, the latest Windows Assessment and Deployment Kit (WADK) must be installed on the machine that is running the Packaging Center.
- PXE images
- Install the Matrix42 Packaging Center on a Windows 10/11 computer and use the option Offline PXE Image Creator to create an import ready PXE image source.
- Additional information can be found here.
- Driver packages
- Install the Matrix42 Packaging Center on a Windows 10/11 computer and use the option Offline Driver Package Creator to create an import ready driver package source.
Upload and Import of Packages
The second step is to upload your packages. Depending on your licensing model, you have two options for the subsequent upload of packages. On the one hand, packages can be uploaded via the Unified User Experience or directly to the system's repository as described below.
Unified User Experience
To upload Empirum packages via the Unified User Experience, please use the following guide: Software Distribution II: Distribute Software Packages One benefit using the Unified User Experience based package upload is that there is no 8 GB file size limit and that the packages will be automatically registered in Empirum.
Repository
If you licensed only Empirum, you can transfer all software package via the Packaging Center Tool Package Upload and Import. Your prepared packages can easily be uploaded and imported to your Master server and Empirum Management Console.
The prerequisites are:
- The latest UEM Agent needs to be installed on the Client or Depot server. You can download the latest version here.
- Only Clients or Depot server with an Agent Temnplate and direct Connection the Master server are allowed.
The old and slowly way is to use WinSCP. More information of the right configuration and transfer can be found here. After the transfer you need to import the packages via the Empirum Management Console in the Software depot section or using the Empirum API service for an unattendend import. Here you can find detailed information about that.