Infopulse PACE Suite Enterprise

PACE Suite is an advanced software packaging tool with intuitive user interface and set of features providing (re)packaging in Windows Installer and various virtualization formats.

Key advantages
out-of-the-box application packaging solution
intelligible wizards for running complex user scenarios
high performance when generating large packages
per-user license valid for any number of physical and virtual machines

PACE Suite is an advanced application packaging tool with intuitive user interface and set of features providing successful (re)packaging in Windows Installer (convert EXE to MSI) and various virtualization formats. PACE Suite is a customer-driven product. We encourage all our customers to request adding new features to the product backlog. Anyone who reports us a missing valuable feature gets the 100% discount for a PACE Suite license in reward.

Repackaging any installation to MSI/MST/App-V/ThinApp
Convert EXE to MSI, MST (a pure Windows Installer), Microsoft Application Virtualization (App-V 5.0-5.1) and VMware Application Virtualization (ThinApp 5.0-5.2) packages. PACE Suite has the most accurate and precise capturing engine that detects system changes in two modes: Monitoring and Snapshotting.

32-bit and 64-bit platforms support
Capture 32-bit and 64-bit applications on any platform you have for any platform you need.

Smart detection of embedded vendor MSI packages
PACE capturing engine instantly detects all hidden or wrapped vendor MSI installations and copies them to a project location, and you have the option to continue customizing detected packages via transform.
Note, that according to the Microsoft packaging best practices it is not recommended to repackage vendor MSI.

Capturing permission changes
None of the filesystem or registry permission changes will be lost. Captured permission changes could be included in the package using SecEdit tool.

Excluding/including captured resources at any time
PACE Suite keeps all of the resources that have been excluded and allows you to include them back at any moment after the capturing has been completed.

Modifying existing projects
With PACE application packaging tool, you do not need to recapture the application again if you need to make small changes. Just open your existing project, update or add more resources (e.g. import files or registry) according to your needs and generate a new version of MSI/MST/App-V/ThinApp packages.

Using global editable exclusion lists
Exclusion lists automatically filter all captured resources, which ensures the creation of pure packages. Exclusion lists are completely editable, so you can adapt them according to your needs.

Environment variables and advertised information handling
Be sure that high-level constructs like Environment Variables and Services are captured, and you can modify them before building a package.

Continue capturing after system restart
PACE knows when a system was rebooted during the capturing and allows you to continue repackaging the installation.

Creating blank MSI packages
Create a new blank MSI package and add necessary resources manually.

Creating transforms for customizing MSI packages
Use transform files (MST) to customize vendor MSI packages. With PACE, you can either create a transform at the very beginning of editing a package or save all your changes as a transform later.

Creating Patch packages (MSP)
Create Patch packages with help of PACE Suite to deliver application updates. PACE provides you with two approaches to creating patches: (1) Save MSI database changes as Patch; (2) Generate Patch as a difference between new and old packages.

Merge Modules (MSM) support
PACE monitors specified pools of Merge Modules and replaces captured resources with appropriate modules. Another available option in PACE is importing Merge Modules to MSI package manually.

Manipulating contents of an MSI in a convenient tree-like interface
Review and modify package resources such as files, registry, features-components in a convenient tree-like interface with complementary functionality presented in wizards.

Importing files and registry to package
With PACE, you can import files, registry, and shortcuts at any stage of packaging. Our application packaging tool includes advanced wizard for importing resources allows you to control many options like INI files handling, feature-component assignment, Media (CAB) options, etc.

We are proud to present PACE Suite 4.7 – our latest release, which takes one of the particularly complex areas of application packaging – working with the registry – and makes it easier to succeed with your packaging tasks, even for newcomers to this field. This release brings a new approach to reviewing and managing registry keys and values with the help of an entirely new Registry tab in MSI Editor. We made a lot of improvements to the UI to ensure it stays user-friendly, no matter how hard your current task is. Read on to discover every improvement PACE Suite 4.7 brings!

New Registry tab in MSI Editor Enjoy a user-friendly tree list view on the Registry tab and find all registry keys and values from both “Registry” and “RemoveRegistry” tables. This view makes it easier to see all contents of all keys – either check everything that is in your package or use a high-level overview.

In the tree list, you can immediately see registry value’s details such as type, value itself, and Component to which this value is assigned. All added, modified, or removed resources are highlighted with colours, and you can quickly undo any of those changes. Using the Registry tab, you can create a new key, value and value/key removal items (RemoveRegistry).

Error detection right when it’s most needed The tree list has a vast amount of validation rules so you can fix errors before testing or building your package. For instance, it checks if a value matches all the limitations and rules of the specified value type; if there are keys, which begin or end, or contain extra backslashes (\). Another example – the tree list even checks if the component, associated with the registry value, does not contain both per-user and per-machine resources, as it is against the packaging best practices and rules.

Rich data for every resource In MSI Editor, Registry tab has four types of resources – Hives (roots), registry keys, registry values, and value/key removal items –each of which has its own Details pane. For instance, for registry key the Details pane shows its name, parent key, root, and other relevant details and key options. For registry values, you can review their values in parsed (transformed) view and in their original, raw MSI format.

For instance, for a registry value, you can change identifier, name, value type, value itself, key, where this value is located, root and re-assign this value to another component from the list. For creating a Default key value, or securing a key creation and/or removal, simply select a respective option from the Value processing method field.

Redesigned permissions management MSI Editor now has a new permission management property, and you can change permissions for registry keys on the Registry tab.

Other Improvements

MSI Editor A new approach to creating patch packages, which changes the way files are extracted from MSI before creating a patch. We developed our solution that offers better stability than the standard tool, built into the operating systems, so now you can always get a working patch package with PACE Suite. Many enhancements to the internal mechanisms of MSI Editor that boosted the overall speed of editing your packages.

MSI Generator We replaced the old mechanism of creating CAB files to guarantee the better stability of managing these resources. CAB files are always split into equal parts and do not depend on the file size. For instance, even files over 3Gb in size will be divided into 500MB cabinet files and will be saved correctly. Another improvement to MSI Generator is a signigicantly better identification of package’s architecure (32-bit or 64-bit) that depends on the resources you capture. Now, the final value of the Platform field will be set automatically and correctly if you left the Autodetect option turned on. You can find detailed description of the new features in PACE Suite 4.7 Release Notes. Don’t forget to check our PACE Suite User Manual – your go-to guide to software packaging with PACE Suite.

Suite, registry, packaging, value, packages, resources, files, package, changes, application, which, Editor, Registry, features, values, creating, capturing, interface, Patch, option, Suite, registry, packaging, value, packages, resources, files, package, changes, application, which, Registry, Editor, features, values, capturing, interface, creating, vendor, advanced