Windows Messaging Subsystem, HKCU Outlook keys, Outlook.prf

[jiambor]

We created an admin node to install Office 2k3 from now on with an
Outlook.prf file. This is good. What I want to know is how can I fix
everyone else. We have to keep setting up Outlook for those computers that
don't have the Outlook.prf file defined everytime there is a new user. I was
hoping to use a login script to remove the First-Run key and put in the
ImportPRF key into the users HKCU../../outlook/setup, but it's not there and
niether is the Windows Messaging Subsystem key either. This all comes in
after outlook is started. I see that I could use a command line at start up
outlook.exe /importprf blah blah, but then it would start outlook everytime.
I could make it only when the key is not there, but then everytime an admin
logs onto a different computer......

Anyways, my search thus far has only found how to deploy it the way we have,
but not how to get those prior to the smart deployment. We currently have
users using 2002 and 2003. I have a function that helps me determine the
version on the computer, but I am stuck without the reg keys in
HKCU\SOFTWARE\Microsoft\Office\<Version>\Outlook\Setup.

Windows XP Pro

I appreciate and thank you for any answers, help, links, pointers, and
documentation that will help me on my quest.

 

[Sue Mosher [MVP-Outlook]]

If you're installing with an .mst file creating with the CIW, then the necessary keys should be created when each user starts Outlook.

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003

and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers

 

[jiambor]

What about for those computers that were not installed with a .mst file?

 

[Sue Mosher [MVP-Outlook]]

Maybe a dumb question, but if you created an admin install, why didn't you use an .mst file for the deployment?

In any case, you can use the CMW at any time, as long as you can point it to a valid source of the install files.

You can also deploy the necessary registry keys with a tool like the Office Profile Wizard (with some tweaking) or virtually any other tool that scripts registry values.

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003

and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers