Is there a way to control the behavior of the Compatibility Pack at
installation? We'd like to push it out to our Office 2003 users, but want
the default Save action to stay Office 2003. Our first test deployment is
showing a mixed result. Some users are reporting that the default action is
to save as Office 2007.

Is there a CIW or other transform creating tool that will help us? Can we
control the behavior with a GPO? Probably GPO would be best so we can
change it once everyone (13,000+) gets it.

Thanks,

Tom

OK, so no one knows how to customize the install. Can someone tell me
exactly what the proper installation behavior is? Should the default Save
be Office 2003 or 2007? How about the default Save As - Office 2003 or
Office 2007?

How about GPO control of the Save/Save As functions?

Thanks,

Tom


"Tom Ker" <thomas.DOT.kerA@Thighmark.com> wrote in message
news:uK$oeM7%23HHA.4460@TK2MSFTNGP02.phx.gbl...
> Is there a way to control the behavior of the Compatibility Pack at
> installation? We'd like to push it out to our Office 2003 users, but want
> the default Save action to stay Office 2003. Our first test deployment is
> showing a mixed result. Some users are reporting that the default action
> is to save as Office 2007.
>
> Is there a CIW or other transform creating tool that will help us? Can we
> control the behavior with a GPO? Probably GPO would be best so we can
> change it once everyone (13,000+) gets it.
>
> Thanks,
>
> Tom
>