Core File Transference

When a Get From Server action has been performed (that is, when a client workstation requests a copy of a remote application from the primary configuration server), an application directory is created on the client within the VTS installation directory, and a core set of application files are immediately transferred to this directory. These core files are:

    GDI.WIF

    SecMgr.DAT

    SecurityManager.INI

    Sync.WIF

 

GDI.WIF

GDI.WIF helps VTS to identify the directory as one that contains a VTS application. The GDI.WIF file contains an alphanumeric Globally Unique Identifier or GUID that is provided by VTS to distinguish one application from another. Further information on GDI.WIF files and their contents can be found in .WIF Files.

SecMgr.DAT

The file, SecMgr.DAT, contains all the user account data that has been configured for the application including the password and privileges that have been configured for each account. This file is an encrypted binary file, and cannot be manually edited.

For further information on the SecMgr.DAT file, see: Security-Related Data Storage.

SecurityManager.INI

The SecurityManager.INI file in your application directory contains administrative settings related to the security for your application, including automatic logoff time, password length, and suppressed privileges. SecurityManager.INI files are described in detail in VTS Programmer's Guide:  Introduction to SecurityManager.INI.

Sync.WIF

The Sync.WIF file in your application directory provides the list of configuration servers for your application. Sync.WIF files only exist in the application directories of remote applications.

 

The tag database and other data are not transferred from the server to the client until the application is actually run on the client.  This process occurs during "startup synchronization", as described in the following section.