Most Microsoft Exchange Client files are stored in several compressed cabinet (.cab) files until they are installed. When Setup is run, the cabinet files are uncompressed and the files are copied to the client's disk or a network server. Knowing where the Microsoft Exchange Client files are stored when they are installed can be useful information if you need to troubleshoot a problem. For example, if the Microsoft Exchange Client won't start and it's running from a network server, the server containing the Microsoft Exchange Client files may be down. The location of the files depends on whether:
The Microsoft Exchange Client installs configuration files, application files, and Messaging Application Programming Interface (MAPI) files. Configuration files (including .ini files, spelling DLLs that Microsoft Exchange Client and other applications share, and information about forms) are copied to and run from the Windows directory or the user's home directory on the local disk or another location on a network server where user files are stored. The following table describes where application files and MAPI files are copied to or run from depending on the Microsoft Exchange Client computer's configuration.
Application Files | MAPI System Files | |||||
Copies to Exchange directory | Runs from network share | Copied to local Windows System directory | Runs from Windows System directory on operating system network share | |||
Local operating system and client | X | X | ||||
Local operating system and shared client | X | X | ||||
Shared operating system and local client | X | X | ||||
Shared operating system and client | X | X | ||||
Setup uses the following process when installing the Microsoft Exchange Client to the local disk from a client installation point or floppy disks. If you encounter problems during Setup, you can use this information to help you troubleshoot. The operating system is running locally.
1. Reads the Setup.lst file in the client installation point to determine which files must be copied to the local disk. The Setup.lst file also instructs Setup to create a temporary, hidden directory for these files on the local disk that is called ~Mssetup.t\~Tmpjnk.t. The cabinet (.cab) files are uncompressed as they are copied to the temporary directory.
2. Reads the Exchng.stf file that was copied to the temporary directory and gathers the user's installation information. This file contains information such as the name of the user's organization and whether the installation is local or shared. By default, Setup obtains the user's name and organization from the registry or, depending on the operating system, the Win.ini file.
3. Copies files to the local disk as described in "New Client Installation" on the preceding page.
4. Writes the Exchng.stf file to the Exchange directory. Edits the registry or Win.ini file to indicate the location of the Exchng.stf file. Deletes the temporary directory.
5. If a Default.prf file exists in the client installation point, Setup copies the file to the Windows directory and runs the automatic profile generator (Newprof.exe) to create a default profile. If a default profile does not exist, the Microsoft Exchange Client runs the Profile Wizard the first time the client is run.
To set up a network share and install Microsoft Exchange Client, you must first create the share by running Setup with the /a option. Then, you or the user can run Setup to install the Microsoft Exchange Client from the network share. If you encounter problems during Setup, you can use the following information to help you isolate the cause of the problem.
Setup /a creates a network share depending on whether the operating system on the computer setting up the share is running from a network share or from a local disk.
After you've created the network share, you can install Microsoft Exchange Client to run from the network share. The Setup process to install from a network share is similar to installing to a local disk, with the following differences: