The first way we used to apply profile configurations was exchange newprof.exe utility. But the keyword there was contained within the utility name – “new”. It could only create new profiles and cannot modify existing configurations.
Then at last we got modprof.exe and the ability to preserve existing settings and configure new.
The command line we use was
modprof -p \\circinus\dat\cfg$\xyzoutlook.prf
p PRF, specifies the path to the profile settings file. As usual, if no path is specified utility looks for the default.prf file located within %systemroot% folder

s, this switch specifies an option to run the tool in a separate window, ask user to specify the PRF file and display messages within it

x, when the –s option is specified, sets automatic start without waiting for user to select concrete PRF file.

z, specifies MAPI error code output if any

Additional source of trouble in case when you deploy it for several users and on a limited set of persons you get an error is the fact that the tool cannot generate log files.

List of switches for the newprof automatic profile generator program
Creating Default User Profiles


To those of you wondering, what we decided to do further, I will continue the storytelling. We started implementing outlook profiles with Office Profile Wizard. We got Office 2003 Resource Kit and started with creation of standard profile description PRF-file.
The Configuring Outlook Profiles by Using a PRF File whitepaper helped us to tackle the tool up.
The main problem was the fact that after configuring you realize that the settings you’ve made were made from scratch and thus would give the return for new Outlook-less systems only. The good thing was that we just established new room with brand new PCs. The bad thing was that we had to move several users that already work on old PCs but the way to get the settings for them was to apply this newly created PRF on new machines via MST transform file. The second what was actual for us is the we have different versions of operating systems and different versions of applictions which in turn require different steps to apply PRF file.
So we started with manual edit of registry. We deleted the key
to drop the state flag
created a string ImportPRF in
key and set is with value \\circinus\dat\cfg$\xyzoutlook.prf

to point to the PRF file we created and placed on our server share. Thus key value represents the UNC path where circinus is the name of our server, dat\cfg$\ is the share path and the xyzoutlook.prf is how we named our profile configuration file.