Packaging

Overview

The glueckkanja-gab Software Packaging Service delivers standardized application deployment packages based on setup binaries in various formats compatible with Windows 10 to deliver these packages in organic, chocolatey, or App-V packages. With the Packaging Service, all software packages are created in our packaging lab by a dedicated team of experienced engineers, tested for quality and delivery, then transferred to the customers deployment endpoints for assignment to modern desktops.

Cost base

Software packages are charged per retrieved or delivered package. The exact prices can be found in the glueckkanja-gab product catalog. App-V packages are generally charged on a time and material basis via On-Demand services.

Standard services and tasks

The following section lists the standard tasks and services included in the service.

App Store

glueckkanja-gab maintains an ever-expanding library of ready-to-go applications that might instantly be added to the list of available packages and assigned to groups or users.

Building of software packages

If an application is not listed in the App Store or is in need of customization, a packaging request can be sent to glueckkanja-gab. The request must be submitted via the RealmJoin Upload Portal.

The following information is required for the package request:

• package name
• version number
• intended users
• comment

The customer has to provide the necessary binaries as well as all installation requirements and additional information for an unattended installation. It is essential for in-time processing, that the request only contains the necessary binaries and a detailed installation guide document.

The installation document shall contain command-line switches for the unattended setup of the application. Many vendors provide this documentation for their applications. Please provide any available installation documentation for the application in the request form. If the installer requires any response files (.ini, .inf, .iss, ...) they must be provided with the request form. Step-by-step installation instructions, such as screenshot documentation are not eligible for the regular packaging SLA and may cause additional costs based on time and material for the investigation of the required settings and configuration. If a package requires additional time and material budget, we will contact the Service Owner beforehand and request approval, and provide a rough estimation of the needed effort.

After submitting the request information (please do not forget a contact email address if the requesting admin account does not have a monitored inbox. The requester is the first point of contact for any questions.), you will be able to upload your zip file containing the binaries. After the upload, a ticket will automatically be created and the packaging request will be handled by glueckkanja-gab. When you have entered everything you need, click on Send Request. You can attach files to the request as soon as the request has been sent. In case any support is required from the software vendor, it is the responsibility of the customer to maintain communication with the vendor. glueckkanja-gab will not communicate with any third-party software vendor. To prevent spam and unsolicited requests, if no file is attached, the request is not processed. In case of a file-less request, a dummy.txt file has to be attached.

Package types

There are four different kinds of packages that can be requested. It is recommended to use the most generic package types (craft and Chocolatey) if possible.

Craft package

A craft package is just a container to transfer a batch or PowerShell script and related files to a device. Typical examples would be to set system or user-based settings in the registry, prepare files with user-specific details like Outlook signatures or Office templates, or install drivers.

It is important to know that craft packages can run in user or system context, which can be specified during the package crafting process. Packages that are run in user mode are installed using the current user without administrative rights, even if the user is a local administrator on the device. Packages that are run in the system mode use the SYSTEM account on the device.

Chocolatey package

Chocolatey packages contain all necessary files, e.g. installs, zip files, scripts, etc., in one compiled package. During package installation, Chocolatey checks for dependencies (specified during package assignment in RealmJoin) and takes care of those, silently installing the needed packages.

Organic Packages

Organic packages contain raw and unprocessed application setups. When handling those, RealmJoin is used as a transport vehicle to move the zipped container to a specified location on a device. Depending on its payload, the installer then has to be manually started by the user (if user mode) or by a remote administrator or field service person.

The idea of organic packages is based on the experience that large infrastructures sometimes need specialized software only used by up to five users. Because lots of these applications are not identified as relevant to the overall company strategy but users often insist to have it, there was a need to offer a fast and cost-effective way to transport the setup in a controlled and auditable way to the client but to have its installation be a manual process.

With organic packages, the organization knows exactly which software based on the detailed binaries and versions is in use on the client machines. If there is a security issue with one of these versions, all information is at hand. And if the user needs a new device, the special software packages are again available.

The used binaries are scanned for malware when transferred to the RealmJoin infrastructure. Because of their highly individualized nature and manual on-device management, those packages are not maintained in a standard process, possible effects have to be addressed locally.

On-Demand services and tasks

The tasks and services described in the following section are not included as part of the Service but may be requested and delivered via On-Demand Services.

Ramp-Up

The initial commissioning and setup of our service is defined as ramp-up and is not part of our service. The ramp-up can be carried out via on-demand services or consulting services.

Package type

App-V

Microsoft Application Virtualization (App-V) is an application virtualization solution from Microsoft. The application is isolated from the operating system that is running it, and an intermediate layer between the application and the operating system is provided as a runtime environment. However, the application behaves as if it is installed locally.

App-V packages are the most exotic packages supported by RealmJoin. They are created as the difference between an out-of-the-box Windows 10 and an out-of-the-box Windows 10 with the software installed; therefore, contain all the differences in data, keys, and file structure that result from the installation.

App-V sandboxes the execution environment, hosting a virtual file system, registry keys, services, and so on, based on the App-V package. All the data specific to the software version is enclosed in the sandbox, resulting in no changes in the client's operating system. This also allows the use of a different version of the same software parallel, even if they contain contradicting settings and key values. App-V might be considered as an intermediate step towards a virtual machine.

Generally spoken, App-V is the most sophisticated package type in RealmJoin, while highly customized, allowing most applications to be run. App-V is only available on Windows 10 Enterprise version.

Customer requests and incidents

Requests that do not fall into the items listed under Standard services and tasks and are from direct customer requests will be treated as a normal change and serviced through On-Demand services.

Prerequisites

Services

An IT-Service agreement with glueckkanja-gab is required. The glueckkanja-gab Service Level Agreement and Request definitions also apply to this Service Description.

The Client Module is required as the basis for the Software Module.

Requirements

The packaging lab can only perform quality tests, but not functional and integration tests. Technical contact for the respective software and processes for testing and releasing packaged software must be provided by the customer.

License

The Customer is responsible for the correct licensing of all Microsoft services and other Software used and affected.

Optional

• Optionally, the customer can add one of the on-call duty packages (defined in more detail in the Service Level Agreement).

Exclusion

The packaging lab cannot produce software packages without comprehensive documentation. The preparation of such documentation is not part of the service.