No apology necessary. I'm glad to hear your problem is solved for now. I
wonder what could have caused the setting to be disabled if not a GPO. I
know there are ways these types of settings can be controlled during the
install process, but you'd know if you had done that. Anyway, if you figure
it out, please post back with an update.
I always do separate GPOs for specific topics. I've got my Office XP and
Office 2003 settings all in one policy, but at least it's all Office. I
learned this the hard way when the Default Domain Policy got set back to its
default during a troubleshooting thing a couple of years ago. If I had not
had things like Office controlled by the default domain policy, at least I
wouldn't have had to try and figure those policies out again from scratch.
But the real reason is that if a policy change has an unintended result, you
can just disable the whole thing to minimize the effect while sorting it
out.
"Sharon" wrote in message
> Dave,
> My apologies. I am new to usenet, and didn't see your response until
> Friday. After running RSOP I don't see any policies that look like
> they would be affecting this. I finally wrapped my head around how to
> install the Outlook template in whatever policy I wanted it. For now
> I've put it in Default Domain Policy, but your suggestion of creating a
> separate Office policy seems like a sound one. I still can't get the
> particular setting I want to be anything but disabled or not
> configured. However, since the policy not only disables the checkbox,
> but unchecks it, I have at least achieved the effect I wanted. Thank
> you so much for your help, and patience with my being so slow on the
> uptake - group policies are not yet my forte.
> --Sharon
> >> Stay informed about: enable ""make Outlook the default program"" checkbox