http://www.howto-outlook.com/howto/deployprf.htm

Deploy Outlook mail profile settings via GPO or script

• Deploy Office with a customization file (msp-file)
• Deploy a msp-file if Office is already installed
• Deploy a prf-file via a (Group Policy) logon script

---

Deploy Office with a customization file (msp-file)

Directly deploying Outlook mail profile settings when deploying Office is the best way to go. By using the Office Customization Tool (OCT) you can prepare your deployment and specify default settings for your users including Outlook mail profile settings.

Download: Office 2007 Office Customization Tool (OCT)
Download: Office 2010 Office Customization Tool (OCT)

Installing and running the OCT

To be able to use the OCT you must do the following;

1. Execute the downloaded OCT for your version to extract it to a convenient location.
2. Copy the contents of your Office 2007/2010 installation media to the deployment location.
3. Copy the Admin folder from the extracted OCT location to the installation directory of your Office deployment folder.
   • If your installation DVD contains both the 32-bit and the 64-bit version of Office 2010, you’ll have to copy it to the x86 or x64 folder, respectively.
4. Start setup.exe from the deployment location with the /admin switch;
   setup.exe /admin

Note:
The OCT works for any Office Suite. Be aware of the fact though that the Home and Student version doesn’t contain Outlook.

The mail profile can be configured in the Outlook section of the OCT.
(click on image to enlarge)

Deploying Office with the msp-file

Once you’ve configured all the settings that you want, use File-> Save As… to save the msp-file to the Updates folder of your Office deployment folder. When Office is being installed, it will automatically apply the msp-file and configure the settings for the user.

For further customizations required to deploy Office 2010 via a GPO see;
Deploy Office 2010 by using Group Policy computer startup scripts

Deploy a msp-file if Office is already installed

If Outlook 2007 or Outlook 2010 is already installed on the client computers, you can create a new msp-file via the OCT which only holds mail profile settings and nothing else. You can then deploy this msp-file.

This deployment can be done via Microsoft System Center Configuration Manager or via a different deployment application within your organization.

If you want to do this via a Group Policy, you’ll have to do it via a startup script as the installation requires Administrator level rights. Since users usually don’t have installation rights, a logon script will fail. The command to use in your startup script would be similar to;

msiexec.exe /p "\\server\share\custom.msp"

Outlook 2003
If you are still using Outlook 2003, then you can use the Office Resource Kit (ORK) to create a Custom Maintenance Wizard File (cmw-file). To apply this to your users, deploy the Maintwiz.exe file to the Office directory of the user’s machine and execute it with a the location of the cmw-file as the parameter in a GPO startup script.

"C:\Program Files\Microsoft Office\Office\Maintwiz.exe" "\\server\share\custom.cmw"

Deploy a prf-file via a (Group Policy) logon script

The OCT or ORK also allows you to export the Outlook mail profile as a prf-file. This prf-file can then be distributed to your users via a logon script. As logon scripts work on user instead of computer level, it will allow you to more easily deploy different mail profiles to different sets (Organizational Units) of users. Outlook offers 2 built-in mechanisms for this.

/importprf startup switch

One method is to import prf-files via the /importprf command line switch. The downside of this command line is that it will also directly launch Outlook and will execute at each logon and could therefore possibly also modify end-user alterations to the mail profile.

ImportPRF Registry value

The ImportPRF Registry value has the benefit that it can be set without needing to open Outlook. The first time that Outlook is launched, Outlook will look at this value and if it is set, it will use the specified prf-file to configure Outlook.

Key: HKEY_CURRENT_USER\Software\Microsoft\Office\<version>\Outlook\Setup
Value name: ImportPRF
Value type: REG_SZ
Value: path to prf-file

For this Registry value to work, the FirstRun and First-Run value may not exist in the Setup key.

Deployment script

While setting the key for the fist time isn’t hard to do, once the FirstRun or First-Run values have been set, updating the mail profile without ending up applying it each time the user logs on is a bit more complicated. To prevent this, you can use the vbs-script below which has the following characteristics.

• Checks if the profile already exists. If it does, it won’t import the prf-file again.
• Allows for setting a version for your prf-file. By increasing the version in the script, you can force the (updated) prf-file to be reapplied again.
• It doesn’t start Outlook.
• Can be used as a (Group Policy) logon script.
• Works at user-level rights.
• Works for all versions of Outlook.

Download: deployprf.zip

The following code is contained in the zip-file download. You can use the code below for review or manual creation of a vbs-script.

'This script determines if a specified mail profile already exists.
'If it doesn't, it will set the path to the prf-file containing
'the mail profile configuration settings.

'Script created by: Robert Sparnaaij
'For more information about this file see;
'http://www.howto-outlook.com/howto/deployprf.htm

'=====BEGIN EDITING=====

'Name of mail profile as in the prf-file
ProfileName = "Outlook"

'Path to the prf-file
ProfilePath = "\\server\share\profile.prf"

'Increase the ProfileVersion whenever you want to reapply the prf-file
ProfileVersion = 1

'======STOP EDITING UNLESS YOU KNOW WHAT YOU ARE DOING=====

const HKEY_CURRENT_USER = &H80000001
const HKEY_LOCAL_MACHINE = &H80000002

strComputer = "."
Set objRegistry = GetObject("winmgmts:\\" & _
strComputer & "\root\default:StdRegProv")

strKeyProfilePath = _
"Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Profiles\" _
& ProfileName & "\9375CFF0413111d3B88A00104B2A6676"
strLastChangeVer = "LastChangeVer"
objRegistry.GetBinaryValue _
HKEY_CURRENT_USER,strKeyProfilePath,strLastChangeVer,strValueLastChangeVer

If ProfileVersion > 1 Then
strKeyProfileVersionPath = "SOFTWARE\HowTo-Outlook\DeployPRF"
strProfileVersionName = ProfileName
objRegistry.GetDWORDValue _
HKEY_CURRENT_USER,strKeyProfileVersionPath,strProfileVersionName,strValueProfileVersion

If IsNull(strValueProfileVersion) OR ProfileVersion > strValueProfileVersion Then
ReapplyPrf = True
End If
End If

If IsNull(strValueLastChangeVer) OR ReapplyPrf Then
'The mail profile doesn't exist yet so we'll set the the ImportPRF key and remove the FirstRun keys

'Determine path to outlook.exe
strKeyOutlookAppPath = "SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\OUTLOOK.EXE"
strOutlookPath = "Path"
objRegistry.GetStringValue _
HKEY_LOCAL_MACHINE,strKeyOutlookAppPath,strOutlookPath,strOutlookPathValue

'Verify that the outlook.exe and the configured prf-file exist
Set objFSO = CreateObject("Scripting.FileSystemObject")
If objFSO.FileExists(strOutlookPathValue & "outlook.exe") AND objFSO.FileExists(ProfilePath) Then

'Determine version of Outlook
strOutlookVersionNumber = objFSO.GetFileVersion(strOutlookPathValue & "outlook.exe")
strOutlookVersion = Left(strOutlookVersionNumber, inStr(strOutlookVersionNumber, ".0") + 1)

'Create the Setup key, set the ImportPRF value and delete the First-Run values.
strKeyOutlookSetupPath = "SOFTWARE\Microsoft\Office\" & strOutlookVersion & "\Outlook\Setup"

strImportPRFValueName = "ImportPRF"
strImportPRFValue = ProfilePath
objRegistry.CreateKey HKEY_CURRENT_USER,strKeyOutlookSetupPath
objRegistry.SetStringValue HKEY_CURRENT_USER,_
strKeyOutlookSetupPath,strImportPRFValueName,strImportPRFValue

strFirstRunValueName = "FirstRun"
objRegistry.DeleteValue HKEY_CURRENT_USER,_
strKeyOutlookSetupPath,strFirstRunValueName

strFirstRun2ValueName = "First-Run"
objRegistry.DeleteValue HKEY_CURRENT_USER,_
strKeyOutlookSetupPath,strFirstRun2ValueName

'Save the applied ProfileVersion if larger than 1.
If ProfileVersion > 1 Then
objRegistry.CreateKey HKEY_CURRENT_USER,strKeyProfileVersionPath
objRegistry.SetDWORDValue HKEY_CURRENT_USER,_
strKeyProfileVersionPath,strProfileVersionName,ProfileVersion
End If

Else
Wscript.Echo "Crucial file in script could not be found." &vbNewLine & _
"Please contact your system administrator."
End If

Else
'The mail profile already exists so there is no need to launch Outlook with the profile switch.
'Of course you are free to do something else here with the knowledge that the mail profile exists.
End If

'Cleaup
Set objRegistry = Nothing
Set objFSO = Nothing