Installing on Windows using the command line utility

Use these instructions to install on a single or multiple Windows server using the command line utility. This utility automates the installation process by running an unattended, or silent, installation. It allows you to pass parameters through to the installation program instead of entering information manually through the wizard.

Since the automated process does not prompt for settings, the settings are manually defined in a configuration file called DTSetup.ini. By default, DTSetup.ini contains two sections. The second section can be duplicated as many times as necessary. The first section, [Config], applies to any server not defined in the second (or duplicate of second) sections. The second (or duplicate of second) section, [MachineName], allows you to specify unique settings for individual servers. You have to modify the heading name (case-sensitive) to identify the server.

Review the following table to understand the different parameters available in DTSetup.ini.

 

DTSetupType

If you are installing on Server Core or Windows Hyper-V Server (standalone), the setup type will be server components only regardless of your setting.

DTActivationCode

A 24 character, alpha-numeric license key which applies the appropriate license to the server. Multiple license keys can be separated by a semi-colon.

DoubleTakeFolder

Any valid path specifying the location of the OpenText Availability and OpenText Migrate files

QMemoryBufferMax

Any integer representing the amount of system memory, in MB, that OpenText Availability and OpenText Migrate can use

DiskQueueFolder

Any valid path to the location of the disk-based queue

DiskQueueMaxSize

Any integer representing the amount of disk space, in MB, to use for disk-based queuing or the keyword UNLIMITED which will allow the queue usage to automatically expand whenever the available disk space expands

DiskFreeSpaceMin

Any integer representing the amount of disk space, in MB, that must remain free at all times

Port

Any integer between 1024 and 65535 that identifies the primary port used for OpenText Availability and OpenText Migrate communications

WINFW_CONFIG_OPTION

LICENSE_ACTIVATION_OPTION

 

You must have Microsoft .NET installed or enabled (depending on your operating system) on the server before starting the automatic installation.

If you are not using the built-in administrator account, User Access Control will prompt you to confirm you want to install OpenText Availability and OpenText Migrate. To work around this issue, use the built-in administrator account when you are installing to each server. You may also disable User Access Control, if that is acceptable for your environment.

 

For Windows servers, if you want to use your own secure certificate, you should obtain and install a certificate from an enterprise or commercial Certificate Authority. Once a certificate is installed in the Windows certificate store, you can select it from the Certificate Subject Name list in the Server Properties General section in the OpenText Replication Console. You will be responsible for updating an expired certificate as needed. If you want to revoke a certificate, you must remove it from the server. If a selected certificate is expired or revoked, OpenText Availability and OpenText Migrate will not replicate data.