When a Get from Server action has been performed to acquire a remote application from a server, your PC becomes a client to that server, and the application's directory containing a core set of application files are immediately transferred from the server to the client's hard drive. These core files consist of:
• GDI.wif: Helps VTS identify the acquired application directory as an application directory by providing a Globally Unique Identifier or GUID. Detailed information on the GDI.wif file for a standard application can be found in "GDI.wif". (The GDI.wif file for a script application differs slightly from that of a standard application. Please refer to Interpreting the GDI.wif File for a Script Application for details.)
• SecMgr.dat: Contains the existing user accounts that have been configured for the application. Detailed information on the SecMgr.dat file can be found in "9: Security Manager Service: Introduction to the Security Manager: Security Manager Data Files and Initialization Files: SecMgr.dat".
• SecurityManager.ini: Contains administrative-type security data, such as any application-specific privileges or administrative settings (e.g. mandatory password lengths) that have been configured for this application. Information on the SecurityManager.ini file can be found in Introduction to SecurityManager.ini.
• Sync.wif: Provides the list of configuration servers for this application. The first PC referenced within Sync.wif is the primary configuration server for your application, while the subsequent PCs are the backup configuration servers. Detailed information on Sync.wif can be found in Sync.wif
It is not until the application is actually run on the client that the databases and their data are transferred to the server. This process occurs during "startup synchronization", which is described in the section that follows.