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

Unlicensed Number of Packages

If you see a message to the effect that you have used up the number of packages that you can import and assess, fix, repackage, virtualize, or report on, within a particular database, then you will no longer be able to carry out the associated operation (for example, if your license allows you to fix 500 packages, then, once you have auto-fixed this number of packages, you cannot auto-fix any more under that particular license).

This is most likely to happen after a ‘proof of concept’ or ‘evaluation’ where you are using an Evaluation License only allows you to import and assess up to 10 packages, and fix, repackage, virtualize, and report on, 5 of these.

If, prior to the license expiry date, you want to upgrade your license, contact changebase_sales_queries@dell.com. You may want to do this in order to move from an Evaluation License to a Commercial License. Alternatively, if you are already using a Commercial License, you may want to reset the numbers of packages that you can import and assess, fix, repackage, virtualize, and report on, within the existing database. Once you have the new license details, proceed as in License Settings.

Note: If you have more than one database on the existing license, then all the databases will be transferred to the new license.

Platform Setup

The Platform Setup screen allows you to specify your target platform(s).

Each platform is made up of one or more assessment groups of compatibility checks (refer to Overview of Checks), relating to its Operating System, Virtualization Technology, particular version of Office, and/or Browser.

To setup a platform

  1. For each of your target platforms (up to a maximum of eight), click New and then make the required selections from the Operating System, Virtualization Technology and Office drop-downs, and, if you are going to be importing Web data for assessment, from the Browser drop-down.

  2. As you make a selection from each drop-down, the name of the associated assessment group is added to both the Name field and the relevant platform row at the top of the screen. You can amend the Name field as required.

    Important: You are advised to edit the Name field as required, to keep it to a manageable length. This is because, if you use it in the Fixing template (refer to Fixing Settings), it will form part of the names of the generated Transform files (MSTs).

    If you do not specify a Fixing template, then, by default, the Platform Number is appended to the package name when the MSTs are generated. This is the number that indicates the order of creation of the platforms, as opposed to their priorities.

  3. You can amend the priorities of the platforms by using the Move Up and Move Down buttons on the right. The platform at the top assumes the highest priority in the Dashboard, the Applications Details screen (refer to Drilling Down into an Application), and the Checks Options.

  4. To add a further platform, click New to create a row at the top of the screen, and then select each required assessment group as before.

    You can add up to eight Platforms. If you want to remove an unwanted one, use the Delete key on the right.

  5. Once you have defined the required platform(s), click Create to add the checks linked to the assessment groups, into ChangeBASE.

Note: You will be able to create further platforms subsequently, using the Platform Settings under Settings.

Determining Assessment Groups

As an example, answer the questions below about the target platform to which you are going to migrate - this will determine which assessment groups to select.

Table 6: Platform Setup Example

Question

Answer

ChangeBASE Assessment Group Required

Operating System?

Windows 8 64-bit

Operating System > Windows 8 64-bit

Windows Server 2008 64-bit (inc. R2) Operating System > Windows Server 2008 64-bit (inc. R2)

Browser?

Internet Explorer 10

Browser > Internet Explorer 10

Office Package?

Microsoft Office 2013

Office > Microsoft Office 2013

Hosted Packages?

Yes, via Citrix XenApp

Virtualization Technology > Citrix XenApp - hosted and MS RDS

No No Virtualization Technology assessment group is required.

Package Format?

Virtual, via App-V 5.0

Virtualization Technology > Microsoft App-V 5.0

Suitable for direct import No Virtualization Technology Assessment Group is required

Overview of Checks

Overview of Checks

Assessment groups contain checks (formerly known as 'plugins'), which provide automated assessment for a specific technology. For example, the assessment group for Windows 8 64-bit contains checks that assess packages for specific compatibility with Windows 8 64-bit.

A check is a group of codified rules that validate a package against a particular issue. ChangeBASE contains thousands of rule sets which are grouped into checks of various categories. A check may contain several rule sets, with the number varying according to the logic that goes into making up the particular check.

All the checks associated with the platforms that you selected in Platform Setup are available for selection in the Checks Options, broken down by platform and then assessment group.

Note: The capability has been provided for you to write your own Custom Checks. Some existing checks have been provided that you can clone, to save you having to write each new one from scratch.

Example of Individual Check - Hard-Coded File References Scan

Whether virtualizing, moving to a 64-bit Operating System, or upgrading from Windows XP to Windows 7, there are paths that will have changed. For example:

  • App-V packages are installed to Q:\ instead of C:\Program Files\.
  • 32-bit software is installed to C:\Program Files(x86)\ instead of C:\Program Files\ on 64-bit Windows.
  • Windows 7’s user settings are stored in C:\Users\ instead of C:\Documents and Settings\on Windows XP.

A hard-coded reference to C:\Program Files\ on a 32-bit Operating System is unlikely to cause the associated application to fail as the path remains valid, and so this is flagged as an Amber issue - refer to RAG Statuses. However, ChangeBASE makes auto-fixing available just to make sure.

On the other hand, a hard-coded reference to C:\Program Files\ on a 64-bit Operating System is likely to cause the associated application to fail as that path has changed for 32-bit applications, to C:\Program Files (x86)\. Therefore, this is flagged as a Red issue. However, ChangeBASE can still auto-fix this automatically in many cases, and, where it cannot, advise in the Next Steps tab that the hard-coded path be replaced with a Windows Installer property.

Package Source Type

ChangeBASE has the ability to directly import native versions of the following packages.

  • Microsoft Windows Installer: .MSI (including .MST if required)
  • Microsoft App-V: .APPV, .SFT
  • AppZero: .CAP and uncompressed VAA packages (see the note below)
  • Radia: .XPI

Note: AppZero packages can be imported in their uncompressed and compressed forms. To import a compressed package, the AppZero runtime must be installed on the server machine, so that ChangeBASE can utilize the appzuncompress executable. ChangeBASE expects to find this file in [ProgramFiles]AppZero. If the AppZero runtime is installed elsewhere, the location can be modified in the Import section under the Product tab of the Settings screen.

When using the File System import method, the file extensions above will be automatically detected.

For applications that can be directly imported, you can choose either the File System, SCCM or CSV import methods. File System imports are commonly used for these package types. For all other applications types (e.g. EXE) you need to use the CSV import method.

The Package Source Type screen allows you to specify how you are going to import your packages.

  • To import packages from a folder, select File System and then Next, and go to Package Source.

    Important: If you are going to be importing legacy packages via SCCM or CSV, you will need to set up a File System source first, into which the repackaged legacy applications will be copied for loading back into ChangeBASE so that they can be assessed. Therefore, the SCCM and CSV options will be grayed out until you have selected a File System source.

  • To import packages via SCCM, you need to ensure that, following the creation of the above File System source, you have set up the details of SCCM server access in Configuring New SCCM Server Access, and that you have also set up the other SCCM Options. If so, click SCCM and then Next. You are then prompted to select the SCCM server from a drop-down, following which you can proceed from Package Source Name.
  • To import packages via CSV, then, following the creation of the above File System source, click CSV followed by Next, and go to CSV Import.
  • To capture Web data for assessment against a particular browser platform, in accordance with the Web Capture section, select Web Capture, followed by Next, and go to Package Source.

Note: You will be able to add further Package Sources subsequently via either the Import window (refer to Import Options), or the Package Source Settings under Settings.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating