PRF Files and current configs
.prf files, by design, replace the current configuration in the MAPI profile of the client machine. Use of the .prf file in a login script will remove specialty configurations for all users who exectue the code so specialty configurations will needto be handled within the script based on login name. Users who need a specialty configuration will require a seperate .prf file for them and your script will have to contain the logic to decide which .prf file to place onto the machine. The easiest way to handle personal folders is to place them all in a common yet variable location, such as \\ \users\%username\profile and either name the file something common (outlook.pst for example) or something controlled by a viarable such as .pst This will allow the .prf to correct map the personal folder. Essesntial IEAK allow you to create or modify a .prf file. This utility help do the same thing. It may, however, give easier access to the list of variables that can be used in a .prf file. As for netscape and outlook express, these email clients are not controlled by the .prf (at least the last time I looked at these packages for such things). This tool is more used for the properties of Windows Messaging/Outlook clients.
