Hello Sue,

We are using Policy Maker and are in dire need to have the OAB auto
installed during rollout. Can you briefly explain the steps required?
Or does Microsoft have a fix?



The first .prf sets up the mail account(s) and will -- in some but not
all circumstances -- also set up the OAB. Why it doesn't do it in all
cases, we don't know. Something in Outlook is broken, but we don't know
exactly what.

Using the second .prf file manually is the workaround that Microsoft
recommends to add an OAB to users who don't get it when Outlook
processes the first .prf . The only other available workaround is to
give the users an instruction sheet on how to add the OAB manually.
Group policy does not provide a solution unless perhaps you're using a
GPO tool like Policy Maker from http://www.desktopstandard.com
--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003
http://www.turtleflock.com/olconfig/index.htm
and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers
http://www.outlookcode.com/jumpstart.aspx

- Hide quoted text -
- Show quoted text -
"Julie Williams" wrote in
message ...
From my understanding of what you said in your reply is that the second prf
file cannot be used to automatically add the oab setting into Outlook. It
has to be manually run by the user. Is there anyway of getting this to run
through group policy so that the alteration can be without the user knowing.
Also what does the 1st prf file do then?

I do not understand why that when you create the CIW with the OAB setting it
seems to ignore it. Is there another way of getting this setting to appear
during the installation through group policy?

"Sue Mosher [MVP-Outlook]" wrote:

You're mixing up two different parts of the process. (I know it's confusing.) The profile settings that you set up with the CIW the first time, the ones in the .MST file -- those are the ones that set up the default mail profile. That's phase I.

Phase II is the part that corrects the problem with the OAB. For that you want a .prf file that just modifies the default profile to add the OAB. Export that from the CIW, then DO NOT SAVE CHANGES TO THE MST FILE!!!! In other words, the first PRF is part of your MST file. The second PRF is not. It's a standalone PRF file that the user will need to run if Outlook doesn't add the OAB based on the settings in the second file.

Having the second PRF file available is just a workaround. I don't know why Microsoft isn't making more of an effort to fix the root problem that results in the OAB not getting added in the first place.

If you're using Policy Maker, talk to them about this issue. They may have a solution other than running a second .prf file, as you described below.

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003
http://www.turtleflock.com/olconfig/index.htm
and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers
http://www.outlookcode.com/jumpstart.aspx

"Schuff" wrote in message oups.com...
Hello Sue,

We are using Policy Maker and are in dire need to have the OAB auto
installed during rollout. Can you briefly explain the steps required?
Or does Microsoft have a fix?



The first .prf sets up the mail account(s) and will -- in some but not
all circumstances -- also set up the OAB. Why it doesn't do it in all
cases, we don't know. Something in Outlook is broken, but we don't know
exactly what.

Using the second .prf file manually is the workaround that Microsoft
recommends to add an OAB to users who don't get it when Outlook
processes the first .prf . The only other available workaround is to
give the users an instruction sheet on how to add the OAB manually.
Group policy does not provide a solution unless perhaps you're using a
GPO tool like Policy Maker from http://www.desktopstandard.com

Ok I thought since you mentioned it you may already have had a
solution. Thx

Sue Mosher [MVP-Outlook] wrote:
If you're using Policy Maker, talk to them about this issue. They may have a solution other than running a second .prf file, as you described below.

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003
http://www.turtleflock.com/olconfig/index.htm
and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers
http://www.outlookcode.com/jumpstart.aspx

"Schuff" wrote in message oups.com...
Hello Sue,

We are using Policy Maker and are in dire need to have the OAB auto
installed during rollout. Can you briefly explain the steps required?
Or does Microsoft have a fix?



The first .prf sets up the mail account(s) and will -- in some but not
all circumstances -- also set up the OAB. Why it doesn't do it in all
cases, we don't know. Something in Outlook is broken, but we don't know
exactly what.

Using the second .prf file manually is the workaround that Microsoft
recommends to add an OAB to users who don't get it when Outlook
processes the first .prf . The only other available workaround is to
give the users an instruction sheet on how to add the OAB manually.
Group policy does not provide a solution unless perhaps you're using a
GPO tool like Policy Maker from http://www.desktopstandard.com

You already know about the one solution that I am aware of, since you quoted one of my posts below.

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003
http://www.turtleflock.com/olconfig/index.htm
and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers
http://www.outlookcode.com/jumpstart.aspx

"Schuff" wrote in message ups.com...
Ok I thought since you mentioned it you may already have had a
solution. Thx

Sue Mosher [MVP-Outlook] wrote:
If you're using Policy Maker, talk to them about this issue. They may have a solution other than running a second .prf file, as you described below.


"Schuff" wrote in message oups.com...
Hello Sue,

We are using Policy Maker and are in dire need to have the OAB auto
installed during rollout. Can you briefly explain the steps required?
Or does Microsoft have a fix?



The first .prf sets up the mail account(s) and will -- in some but not
all circumstances -- also set up the OAB. Why it doesn't do it in all
cases, we don't know. Something in Outlook is broken, but we don't know
exactly what.

Using the second .prf file manually is the workaround that Microsoft
recommends to add an OAB to users who don't get it when Outlook
processes the first .prf . The only other available workaround is to
give the users an instruction sheet on how to add the OAB manually.
Group policy does not provide a solution unless perhaps you're using a
GPO tool like Policy Maker from http://www.desktopstandard.com