Document Actions

binaryOptimizer

A standardized software installation technology forms the base for a professional Windows Clients Management.

The binaryOptimizer is an unique software with an innovative technology for an automated assessement and realization of corporate guidelines in MSI Packaging.

This standardized installation technology offers the possibility to achieve and assess a consistent quality in decentralized or outsourced packaging environments.

An established Change- and Release Management lookink towards ITIL completes the whole.

Visit Optimizer WEB-Page

MSI Management

As always it starts harmlessly... only a few MSI packages to create for the software deployment. But like the wind starting with these few packages there are needed more and more, being available with different languages, there should be an already realized Release- and Change Management and finally it should be preceded with standardized best - practice techniques.

The MSI Technology makes also high demands on the package quality and the structured proceeding in the different creation practices.

How supports the binaryOptimizer (bO) companies in the MSI Management?

Cost savings through standardization:

Packages are customized automatically according the preset naming convention and compliancy settings.
The Change- and Release process are realized automatically (differentiating between manufacturer and own developed packages)!
The creation- and quality process are based on a customizable workflow engine.
Error recovery at the push of a button and based on a built in knowledge data base

Cost control through the same language:

Through a role model there are assigned Engineering and Management roles.
Automatic package analyzing resulting in plain quality reports, which meet the demands of Engineers and Managers
Assess packages through an easy, group based traffic signal system
Presenting statuses of any packages

Long-term cost optimizing through Conflict- and Dependency Management:

Collision Management of MSI packages between the operating system and already deployed packages
Dependency Management of packages and libraries (Merge Modules)
Design of pre - requirements (which packages have to be installed first) and Cross Updates (which packages replace an already installed application)

What does this stand for a company?

A decrease of service desk interventions trough an increase of the package quality

A decrease of complexity for the update scenarios through the inclusion of the MSI technology and through that the relocation of the logic into the packages.

Enhancement of infrastructure stability through the consistent use of the MSI technology (Change- and Release Management)

ITIL (SLA) conform assessment of delivered packages (manufacturer or outsourcing partners)

Document Actions

Workflow

The Workflow Engine represents the central engine for all Optimizer processes. One can choose from 6 different templates, which cover any possibility from easy to advanced.
Sources are imported automatically through the implemented Crawler.

The following features characterize the Workflow:

Free choice out of 6 Workflow Templates from easy to advanced
Open definition of role functions for the transitions (who is allowed to execute a transition, who has to sign, etc.)
Logging of all status changes in the reports and thereby tracking of iterations in a package.
Triggering of e-mails and actions if a transition is executed (Notify a user for the next step, start of an external process)
Easy connection to superordinated systems over .xml, .net and scripts
"Performance Optimized" for it can be only done one status change without copying of the package
Avoiding changes of released packages that are in a productive environment
Avoiding of accidentally package changes not having the status Checkout
Automatically importing, analyzing and inserting of delivered outsourcing packages into the Workflow

Document Actions

Quality Assurance

Through the binaryOptimizers basic functions, quality saving measures can be realized very easy.
Over the custom report section significant reports can be created, which display a view over the whole environment at a push of a button.

Considering an individual quality examination the aimed quality can be determined using three parameters.

The Optimizer contains the following quality features:

Quality Assessment report which displays errors grouped in 7 main categories as well as packages grouped in their complexity providing detailed information.
Critical Packages report which shows critical,- or problem packages providing detailed information.
Critical Custom Actions report which shows dangerous Custom Actions which need further analysis respectively have to be accepted as not dangerous.
Analyzing of all packages based on the "Internal Consistency Evaluation" of Microsoft, which displays ICE and ICEM errors.
Analyzing of all packages based on collected best practice approaches from 10 years MSI of binary and its customers.
Repair of the above mentioned errors without having profound MSI knowledge at a push of a button.
Exclusion-List, which can be set on the ICE and best practice layer.
Black-White-List, which can be set on the Custom-Action layer.

Document Actions

Package Optimization

At the beginning of every successful life cycle and a stable client management stand the standardization and the clearing up of errors.

The Optimizer offers the following features to optimize packages:

Standardized installation dialog with a company logo and additional information
Standardized Naming Convention for the Program Folder, the Start Menu and the Summary Information Stream
Determination of the quality level by means of 3 parameters (Origin, Client Rights and Operating System)
Determination of interfaces to superordinate systems like i.e. a CLM-System
Determination of different Compliancy Settings (ALLUSERS, REBOOT ARPNOMODIFY etc.)
Displaying and repairing of differences to the Compliancy Settings
Simple package editing through the integration of external editors (ORCA, WISE etc.) in the Optimizer

Document Actions

Conflict- / Dependency- Management

	Conflicts and errors left in packages affect the stability of an infrastructure negatively and create to some extend massive costs. In the worst case, conflicts result in reinstalling a system respectively result in applications not working anymore. Comparable with mines, they have a certain destroying potential that should not be underestimated. A conflict management only works if as possible all needs are considered related to the infrastructure. In common these are: Conflicts on the OS layer related to the registry and files Conflicts between packages considering the Release Management (different versions of the same application are excluded from each other) Conflicts between Merge Modules The Dependency Management as well plays a central role related to the conflicts. Thereby related topics, like i.e. the Release Management have to be considered.
	Which features contains the Optimizer to detect and display conflicts? Automatic package analyzing and output of a plain conflict report. Inclusion of all relevant resources like the OS, other packages and Merge Modules for a holistic conflict assessement Automatic update of all conflict-affecting parameters (OS, packages, Merge Modules) in the background Displaying all conflicts within seconds!!!

	And what features contains the Dependency Management? Design of Dependencies in terms of the installation order (package A has to be installed before package B and C) Design of Dependencies in terms of pre-requirements (package B can only be installed if package A is already installed) Design of a Release Management considering the basic MSI Technology (version 0003 uninstalls automatically all previous versions 0002 / 0001 if one has been found) Design of a Release Management in terms of update behavior and cross update behavior and origin of a package Design of conflict behavior (package A will never be installed together with package B --> conflicts are ignored) Design of OS conflict behavior (package A will never be installed on an OS-X--> conflicts are ignored) Design of Merge Module affiliation (Merge Modul y has to be included in package A)

Sections

Personal tools

Document Actions

binaryOptimizer

MSI Management

MSI Management

How supports the binaryOptimizer (bO) companies in the MSI Management?

What does this stand for a company?

Document Actions

Workflow

Workflow

Document Actions

Quality Assurance

Quality Assurance

Document Actions

Package Optimization

Package Optimization

Document Actions

Conflict- / Dependency- Management

Conflict- / Dependency- Management

Document Actions