Chat now with support
Chat with Support

Welcome, erwin customers to Quest Support Portal click here for for frequently asked questions regarding servicing your supported assets.

ChangeBASE 6.2.2 - Release Notes

System Requirements

Before installing ChangeBASE 6.2.2, ensure your system meets the following minimum requirements:

  Training/POC (For example, less than 50 packages) Small Operation (For example, less than 1,000 packages) Medium Operation (For example, between 1,000 and 5,000 packages) Large Operation (For example, more than 5,000 packages)
ChangeBASE Client Dual core CPU, 4GB RAM Quad core CPU, 8GB RAM Quad CPU, 16GB RAM Quad CPU, 16GB RAM
ChangeBASE Server Dual core CPU, 4GB RAM Quad core CPU, 8GB RAM 8-core CPU, 16GB RAM 16-core CPU, 32GB RAM
MSI Studio MSI Studio requires Microsoft .NET 4.0 Framework to be installed.
SQL Server As per Microsoft recommendations for a 1GB database As per Microsoft recommendations for a 20GB database As per Microsoft recommendations for a 100GB database As per Microsoft recommendations for a database larger than 100GB

For more details about system requirements, please refer ChangeBASE User Guide.

Important: We have added functionality in the Dependency and Conflict Checker (DaCC) that allows users to detect .NET dependencies. We need to collect extra application data to facilitate this and as a result it will increase the ChangeBASE database size. For customers with very large application estates this increase could be significant.

Product Licensing

To activate an evaluation license

  1. During the setup of ChangeBASE 6.2.2, ensure that, on the SQL Server Database screen, you select Use Eval License before clicking Create.
  2. Your database is then set up and associated with a trial license that allows you to use ChangeBASE for a 30-day evaluation period and import and assess up to 35 packages. You will also be able to fix, repackage, virtualize, and report on, 50% of these packages.

To activate a purchased commercial license

  1. During the setup of ChangeBASE 6.2.2, ensure that, on the SQL Server Database screen, you select Enter License Details. Then enter the License Key and Site Message exactly as supplied by Dell, before clicking Create.
  2. Your new database is then set up and associated with the license that was supplied to you. To check what exactly you are licensed for, go to your Dashboard and open up the Details on the License Usage widget.
  3. If at any time you want to renew your license, go to Settings > License Upgrade and enter your new License Key and Site Message.

Getting Started with ChangeBASE

Installing ChangeBASE

To install:

  1. Download and run the Dell ChangeBASE MSI (version 6.2.2) from Software Downloads available from https://support.quest.com/changebase.

Upgrading ChangeBASE

Large database upgrades (in excess of 1000 applications), may take considerable time to upgrade, please be aware of this and do not cancel the process.

Note: You do not need to uninstall previous versions before installing version 6.2.2.

To upgrade:

  1. Before upgrading ChangeBASE take a backup of your database.

  2. Download the Dell ChangeBASE MSI (version 6.2.2) from Software Downloads available from https://support.quest.com/changebase.
  1. Shut down the client(s).
  1. If the service is logged in as a user that is not LocalSystem and also not the same as the user performing the installation, a password prompt dialog appears during the installation.
  1. If the client and service are installed on the same machine, simply double-click the file and follow the prompts. In a multi-user environment, the patch must be installed on the service first, and then installed on each client in turn.
  1. During installation of the patch on the service, you will be notified when the ChangeBASE service is automatically stopped or started. When installation of the patch is complete, the ChangeBASE service will be left running.
  1. Following installation on the client(s), restart the client(s) and verify that the version number displayed on the user interface is now 6.2.2 and also that you can see all your previously imported applications in the Applications window. The Microsoft Patch Tuesday checks from July 2013 to February 2014 (inclusive) will have been loaded for running from the Reporting module. In addition, the new and amended checks will be displayed (refer to Checks_suffixes).

  2. Following installation on the client(s), restart the client(s) and verify that the version number displayed on the user interface is now 6.2.2 and also that you can see all your previously imported applications in the Applications window. The Microsoft Patch Tuesday checks from July 2013 to September 2014 (inclusive) will have been loaded for running from the Reporting module. In addition, the new and amended checks will be displayed (refer to Checks_suffixes).

Important: If the upgrade fails, for example if there are no previously imported applications showing in the Applications window after the upgrade, follow the instructions in Contacting Dell. In any communication with Support, be sure to attach all the log files in the directory %ProgramData%\ChangeBASE\Logs. You will then be supplied with an executable file and associated instructions to enable you to complete the upgrade successfully.

 

Important: Please note if you are upgrading from 6.1.1 you may have already made this change.

The fix for making repackaging work utilizing MSI Studio in a 64bit guest VM requires the updating of a batch file. This batch file resides in the ‘Program Files\Dell\ChangeBASE\MSI Studio’ folder (or ‘Program Files (x86)\Dell\ChangeBASE\MSI Studio’ folder in a 64 bit machine) wherever MSI Studio has been installed. However, updating the ChangeBASE installation in the host will not cause the batch file in the guest VM to be updated.

There are four methods of updating the batch file in the guest VM outlined below and the most appropriate method for your specific environment should be chosen:

  1. Edit the custom conversion settings in the ChangeBASE host so that it copies over the updated batch file at the start of the repackaging process:
    1. Copy the msistudio.bat from file to an empty folder that the ChangeBASE Service can access (copying just the batch file will ensure that only that file is copied over to the guest VM, not the whole of the ‘MSI Studio’ folder from the ChangeBASE host machine)
    2. In ChangeBASE
      1. Navigate to the Settings, Conversion, Custom Conversion Technologies screen ii. Select the required technology ‘MSI Studio (x64)’ iii. Uncheck the Use Pre-installed Tools.
      2. Specify the folder’s UNC path where the batch file has been copied to in the ‘Tools Path (on host)’ field.
      3. Save the changes
        Note that this option does not require the guest VM to be updated – the updated batch file will be copied over at the start of each repackaging process using this technology.
  2. Revert to an earlier snapshot in the guest VM (a snapshot that doesn’t have MSI Studio installed), and install MSI Studio using the latest ChangeBASE MSI. A new snapshot should then be taken and the Conversion settings updated in ChangeBASE to reflect this new snapshot name if necessary.
  3. Re-install MSI Studio using the latest ChangeBASE MSI in the existing guest VM. A new snapshot should then be taken and the Conversion settings updated in ChangeBASE to reflect this new snapshot name if necessary.
  4. Manually copy over the batch file to the ‘Program Files (x86)\Dell\ChangeBASE\MSI Studio’ folder in the guest VM, overwriting the existing file. A new snapshot should then be taken and the Conversion settings updated in ChangeBASE to reflect this new snapshot name if necessary.

CBVM Tools

CBVM Tools must be upgraded in any VM snapshots used by ChangeBASE. This new version provides features which ChangeBASE 6.1 onwards requires. Please note if you are upgrading from 6.1.1 you may have already made this change.

  1. Locate to tools on the ChangeBASE server. They are found in Program Files\Dell\ChangeBASE\Resources\CB VM Tools.
  2. For each VM Snapshot used by ChangeBASE you must revert the snapshot, and copy the CBVMTools Setup.msi to the guest to install them.

    You may need to restart the VM after installation.

  3. Once installation is complete, re-snapshot the VM and give it the same name as the parent snapshot. This will remove the need to update the ChangeBASE Settings.

    If you do name it the same as the parent snapshot, you must delete the parent snapshot so there is only one snapshot with that name.

Additional Resources

Additional information is available from the user guides in the following locations:

Globalization

This section contains information about installing and operating this product in non-English configurations, such as those needed by customers outside of North America. This section does not replace the materials about supported platforms and configurations found elsewhere in the product documentation.

This release supports any single-byte or multi-byte character set. It supports simultaneous operation with multilingual data. This release is targeted to support operations in the following regions: North America, Western Europe and Latin America, Central and Eastern Europe, Japan.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating