Chat now with support
Chat with Support

ChangeBASE 6.2.2 - User Guide

Introduction Before You Start... Installing ChangeBASE Configuring ChangeBASE The Pre-Loading of Packages into ChangeBASE Import Options Applications Options Checks Options Dependency and Conflict Checker Dashboard Reporting Repackaging and Virtualization Web Capture

Drilling Down and Fixing

Drilling Down into an Application

To drill down into the issues of a selected application

  1. Either double-click it in the Applications window, or select it and click the Details option at the top of the window. The issues are then displayed in a Details tab, which breaks down the issues by platform, in order of Platform Settings priority.
  2. Select the required platform and then click on the issues that you wish to investigate and/or fix.

Viewing the Application in MSI Studio or the Package Source

To view the application in MSI Studio

  1. Select Open > Selected Package with MSI Studio.

To view the application in the Package Source

  1. Select Open > Selected Package Folder with Windows Explorer.

Important: Any client viewing the application in a multi-user setup will need access to the shared Package Source.

Auto-Fixing Issues

If you want to auto-fix any of the issues that have the Auto Fix icon , check the Fix column, and, if there is a choice of fixes available, select the required one from the drop-down in the Auto Fix column. Then select Apply at the top of the screen.

Alternatively, to override an issue, check the Ignore column and select Apply at the top of the screen.

The spinning icon is displayed while fixing takes place. Once fixing is complete, this is replaced by the icon in the Fix column. The relevant fix files, for example CAB and MST files, are created in your Package Source.

Note: To display the application RAG statuses by assessment group, and apply multiple fixes, go to the Checks Options.


The status of an application is indicated in the Phase column. These statuses will be used by the ChangeBASE API.

To manually change the status of any application

  1. In the Select column, check the applications for which the status is to change. For example, if you want to put a series of applications on hold, select all the applications that you want to put on hold.
  2. Select Set Phase at the top of the screen, and, from the drop-down menu, select the status to which all the selected applications are to be changed.

  1. Select Apply to Selected Applications.
  1. The existing phase of each selected application is changed to the selected phase.

Complexity Ratings

The Complexity rating for an application is based on the number of associated files and registry entries:



<Count op="GT" value="100" increment="1"/>

<Count op="GT" value="250" increment="2"/>

<Count op="GT" value="500" increment="3"/>

<Count op="GT" value="1000" increment="4"/>



<Count op="GT" value="1000" increment="1"/>

<Count op="GT" value="5000" increment="2"/>



<Count op="GT" value="0" increment="1"/>



If you wish to use your own complexity ratings and override the ratings that are currently displayed, then you can add a file called ComplexityRules.xml into c:\ProgramData\ChangeBASE. You can reference any MSI table and provide an operator and a value to provide an increment. The maximum is 5. The operators have to be GT, LT or EQ.

Creating Composite Applications

If required, you can drag one or more packages in the Application Name column onto another, parent, package to create composite applications, with composite RAG statuses.

The constituent packages within a composite application appear at the bottom of the screen, in the member package grid at the bottom of the window, when the application is highlighted. The parent package is indicated in the Package Primary column on the left.

If you want to remove a package from an application, highlight the required package and select Remove Package from Application in the bottom right hand corner of the screen.

If you want to link any of the SCCM packages to packages that share the same SCCM Package Name, select them in turn and then select SCCM > Link SCCM Programs. The linking is indicated via the SCCM Program Linked flag. The applications are linked under the parent SCCM Package Name, and are shown at the bottom of the screen as shown above.

TIP: If the SCCM Package Name or SCCM Program Linked column is not currently displayed, you can select one or both from the Column Chooser by right-clicking in any of the column headers, selecting Show Column Chooser from the context menu, and then dragging the columns onto the top row of the grid. You can also display the SCCM Application Install Count in the same way.

Figure 5: Applications Window Column Chooser

When you need to hide the Column Chooser again, either close it by clicking the cross in the top right-hand corner, or right-click in any of the column headers and select Hide Column Chooser from the context menu.


Note: In SCCM, 'package' is the equivalent of 'application' in ChangeBASE, and 'program' is the equivalent of 'package'. If you have, say, three programs - Word, Excel and Access - that belong to a single package called 'Office' in SCCM, then, when they are imported into ChangeBASE, three separate packages - Word, Excel and Access - will be created by default.

If you then check the three packages in the Applications window, and select SCCM > Link SCCM Programs, the three packages will be grouped into a single application called 'Office'. The individual packages will be shown at the bottom of the screen when 'Office' is highlighted.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating