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 - 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

Package Source

The Package Source File Path screen allows you to specify the UNC path to a source, which can, for example, be a network share containing applications or Web data to be assessed.

Note: If you subsequently add applications or Web data to the source, these will automatically be pre-loaded in the Import screen.

To specify the source location

  1. Enter the required UNC path using the following syntax: \\server\share\file_path.

    The server portion of the UNC name references the strings maintained by a network naming service such as DNS or WINS. Server names are set by a system administrator. \\localhost can be used to reference the local machine. For example, \\localhost\d$\Training locates a folder called 'Training' on the d:\ drive of the local machine.

    The share portion of the UNC name references a label created by an administrator or, in some cases, within the operating system. In most versions of Microsoft Windows, for example, the built-in share name admin$ refers to the root directory of the operating system installation (usually C:\WINNT or C:\WINDOWS). You will need to set up shares if accessing folders across a client/server setup.

    The file_path portion of the UNC name references the local sub-directories beneath the share.

2. Click Next to provide the Package Source Name.

CSV Import

The CSV Setup screen allows you to specify the path to a CSV file, and indicate whether or not it has a header row.

To load a CSV

  1. Ensure that your CSV file matches the format described in Creating a CSV File from the CSV Template.
  2. Enter the CSV Path to the CSV file.
  3. Click Load to bring up the file in a table.
  1. Click Next to proceed to Package Source Name.

Note: If you subsequently update the loaded CSV file outside ChangeBASE, by for example adding extra packages, then, provided that the associated Package Source is open in the Import Options, you can click the Refresh button to load into that window the additional packages from the CSV file.

Creating a CSV File from the CSV Template

Creating a CSV File from the CSV Template

The CSV template is called BulkCSVImport.csv and is automatically installed with ChangeBASE, under .\Resources\Bulk CSV Import\, for example in C:\Program Files (x86)\Dell\ChangeBASE\Resources\Bulk CSV Import\.

It has a CSV file header row with the following fields. Complete the remaining rows with details of your applications and save the file in the location to be given as the CSV Path in CSV Import.

Table 7: CSV Fields

Name

Purpose

Executable File Name

Path to the file to be repackaged.

Example:

\\localhost\d$\Training\FileZilla_3.7.3_win32-setup.exe

Command Line Arguments

Installation options or MST for application.

Examples:

/silent

TRANSFORMS="C:\ChangeBASE\Packages\Msi-Store-2\AdbeRdr930_en_US\FIXES35.mst"

Support Files (Y/N)

N: Only the Executable Filename will be copied to the Virtual Machine.

Y: All files and subfolders in the same folder as the Executable Filename will be copied to the Virtual Machine.

Note: This option only applies to Repackaging.

AutoComplete (Y/N)

With this option checked, ChangeBASE will attempt to click on the buttons on the installation dialogs (Next, Finish, and so on) to allow the installation to progress unattended.

Note: This option only applies to the importing of legacy applications.

ProductName

Specifies the product name that will be displayed in ChangeBASE.

Note: This option only applies to the importing of legacy applications.

ProductVersion

Specifies the product version that will be displayed in ChangeBASE.

Note: This option only applies to the importing of legacy applications.

MSI Output Folder

This option is not relevant to the current version of ChangeBASE.

Launch Application

Where VBScripts are imported, this field will automatically be populated with WScript. This is the script host for running VBScript on Windows. Alternative script hosts (such as CScript) can be specified if required.

Manufacturer

Name of the manufacturer.

Note: This option only applies to the importing of legacy applications.

View

 

This option is not relevant to the current version of ChangeBASE.

Package Source Name

The Package Source Name screen allows you to provide the Package Source with a meaningful name.

  1. Enter a name in the Package Source Name field.

    Note: If you are setting up a source that is being used to pre-load non-MSI files, typically a CSV or SCCM source, then there is an additional prompt for you to select a File System Package Source from a drop-down. This is the Source to which the repackaged MSIs are copied once they have been repackaged, so that the applications can then be imported and assessed.

  2. Once you have specified the package name, and additional source if required, then click Create to pre-load all the files in the source into the Import window.

Important: Once non-MSI files are initially imported into the Applications window, they are shown as gray in both this window and Dashboard to indicate that they are as yet unassessed.

They can now be selectively repackaged in the Applications window via Convert > Repackage, in order to be given regular RAG statuses.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating