Windows-specific prerequisites

The following are tasks to perform or issues to address before installing Transfer CFT.

Windows requirements

The Windows installation directory must not contain any sub-folders or files that are owned by another user.

Hardware and software requirements

Before installing Transfer CFT Windows check the following:

  • OS version
  • Communication system type

These selections affect the minimum hardware and software requirements for the product and may be inter-dependent.

Transfer CFT is based on an external network layer, which must be installed before operating the product. And note that if other applications are running at the same time as Transfer CFT, the RAM requirement needs to be increased.

Apply a service pack or patch, or upgrade using Central Governance

To upgrade or install a Transfer CFT Service Pack or patch from Central Governance, you must:

  • Run the Transfer CFT UI (Copilot) as administrator.
  • Disable the Windows User Account Control (UAC).

Configure Windows UAC

User Account Control (UAC) is an option to add security infrastructure on Windows operating systems.

For Windows versions that support UAC, Windows Vista, Windows Server 2008, Windows 7, Windows Server 2008 R2, and Windows 2012, you must disable the UAC when using Central Governance to apply patches, service packs or upgrades for Transfer CFT.

  1. From the Start menu, type UAC and click to search.
  2. In the User Control Account settings pop-up window, set the slider to Never Notify.
  3. Click OK.
  4. Reboot to make the change effective.

For Windows versions prior to the versions listed above, perform the following steps to add yourself in Log on as a service group:

  1. Navigate to Start > Control Panel > Administrative Tools > Local Security Policy.
  2. From the tree, select Local Policies > User Rights Assignment > Log on as a service.
Note On some systems the path may be Start > Control Panel > System and Security > Administrative Tools > Local Security Policy.

Set administration rights if UAC is enabled

If you do not disable the UAC, the installer requires administration rights at installation. You must be part of a group of administrators, or have an administrator user account. The installer detects the type of user, and sends the appropriate message:

  • Setup with administrator user account: Accept or decline if you want to make changes to your computer.
  • Setup with standard user account: Enter your administrator password first to continue.

Tasks that required elevated rights

The following tasks require that you have elevated rights and fail if one of the above setup options was not performed:

  • Create or remove shortcuts in Start menu or desktop
  • Create or remove Windows services
  • Installing in %SystemRoot% or %ProgramFiles%
  • Running product scripts that require elevated rights

Windows x86 operating system prerequisites

When using a Windows x86 (32-bit) or (64-bit) system, you must install the Visual C++ Redistributable Package for Visual Studio 2013 (not a later version) to provide necessary library files (DLL) for the compiler:

  • For a win-x86-32 target use: vcredist_x86.exe
  • For a win-x86-64 target use: vcredist_x64.exe

User rights prerequisites

There are certain Windows-specific tasks you must perform to enable system user authentication and file system rights before using Transfer CFT or Copilot.

The following sections in the Defining user rights Windows page describe how to:

  • Define rights before starting the UI server (Copilot/REST API/Transfer CFT UI)
  • Define rights before logging on the Transfer CFT UI server (Copilot)
  • Define rights before starting Transfer CFT
  • Define a domain user
  • Define folder rights
  • Define system user access

Run as administrator

The user who installs or upgrades Transfer CFT must be an administrator on the system where you are performing the installation.

Service mode prerequisites

Note the following prerequisites and limitations when installing Transfer CFT in service mode.

  • If you install Transfer CFT in service mode, to launch the service on a specific account you must grant that user service rights to log in.
  • To grant this right, navigate to Administrative Tools > Local Security Policy > Local Management > Local Policies, and select User Rights Assignment. Then grant the user Logon as a Service.
  • If you install Transfer CFTin service mode but want to launch the service on a Local System Account, be aware that you cannot start Transfer CFT from the Copilot UI.

Cluster installation requirements

Because you cannot use a UNC path (\\address\folder) as a shared directory, when installing a Transfer CFT cluster the shared directory must be located in a mounted shared drive (u:\folder).

This is due to UNC path support limitations, such as the changedir function, which are needed by Transfer CFT server. Transfer CFT cannot start up properly if the CFTDIRRUNTIME environment variable is set to a UNC path.

A best practice therefore, when using Transfer CFT clusters in Windows, is to install Transfer CFT in cluster mode and permanently map the network shared directory to a drive. Using this method, the mapped drive is then accessible to the Transfer CFT Windows Services. There is no need to modify the Transfer CFT profile after the installation.

See also, Shared file system prerequisites.

Create a mapped drive

This section describes how to create a mapped drive using the psexec tool. You require this step when installing an active/active cluster, but it can be used for a standalone installation.

To map network shares to a drive accessible to Windows Services, you must log in as the NT AUTHORITY\SYSTEM account.

  1. Download the Sysinternals Suite from Microsoft, and unzip it to a directory.
  2. Open a command window and start a session as Administrator (Run as administrator).
  3. Go to the unzipped directory containing the Sysinternals Suite executable:
  4. CD <the_previously_unzipped_directory>
  5. Log in as the NT AUTHORITY\SYSTEM account:
  6. psexec -i -s cmd.exe
    Note This launches a new command window. Perform the next step in this new window.
  7. In the new window, create the persistent mapped drive.
  8. net use Z: \\servername\sharedfolder /persistent:yes
  9. Provide the credentials for a user having access to the shared folder.
  10. Create a Startup script that contains only the command from step 5 (Create the persistent mapped drive), and implement using the instructions in the Microsoft article: Assign Computer Startup scripts.

Remove a mapped drive

To remove a mapped drive:

  1. Launch a command prompt as Administrator (run as administrator).
  2. Go to the unzipped directory containing the Sysinternals Suite executable with command:
  3. CD <the_previously_unzipped_directory>
  4. Login as the NT AUTHORITY\SYSTEM account:
  5. psexec -i -s cmd.exe
    Note This launches a new command window. Perform the next step in this new window.
  6. In the new window, delete the mapped drive:
  7. net use Z: /delete

Related Links