Are there any plans to release the "Microsoft Office Compatibility Pack for
Word, Excel, and PowerPoint 2007 File Formats" through Windows Update? We
use WSUS to distribute updates and with the number of computers that we have
installing the Compatibility Pack one at a time will be very difficult. If
not, does Microsoft have any instructions on how we could go about rolling
this out to our systems?

The compat. pack is just another MSI like other apps, you could set up a GPO
to push it out.
"Brian Fraley" <BrianFraley@discussions.microsoft.com> wrote in message
news:7EE70B0F-7B26-4117-BE1C-5C02537B675D@microsoft.com...
> Are there any plans to release the "Microsoft Office Compatibility Pack
> for
> Word, Excel, and PowerPoint 2007 File Formats" through Windows Update? We
> use WSUS to distribute updates and with the number of computers that we
> have
> installing the Compatibility Pack one at a time will be very difficult.
> If
> not, does Microsoft have any instructions on how we could go about rolling
> this out to our systems?

Gyorgy,

Thank you for your reply. We have looked at doing that but since we use
WSUS would prefer that MS did it as an update. Less testing and
implementation problems when it is done through WSUS as an update.

Brian

"Gyorgy Moldova [MVP]" wrote:

> The compat. pack is just another MSI like other apps, you could set up a GPO
> to push it out.
> "Brian Fraley" <BrianFraley@discussions.microsoft.com> wrote in message
> news:7EE70B0F-7B26-4117-BE1C-5C02537B675D@microsoft.com...
> > Are there any plans to release the "Microsoft Office Compatibility Pack
> > for
> > Word, Excel, and PowerPoint 2007 File Formats" through Windows Update? We
> > use WSUS to distribute updates and with the number of computers that we
> > have
> > installing the Compatibility Pack one at a time will be very difficult.
> > If
> > not, does Microsoft have any instructions on how we could go about rolling
> > this out to our systems?
>

Hi Brian,

My guess is that at some point after the retail release of Office 2007 (30Jan) that the compatability pack will be available as a
WSUS update (more than one MS product group involved <g>).


There are 2 parts to the compatibility twin pack. The recognizer is already provided in Windows updates as I understand it and folks
who try to open an Office 2007 file should be seeing a prompt to obtain and install the converter pack, but not all companies want
that approach to happen). There is information on deploying the converter pack in the Office 2007 Resource kit at
http://microsoft.com/office/ork

Depends somewhat on your time frame for needing this capability on a widespread basis and your internal practices/policies. There
will likely be similar issues in multi-lingual installations as the creation of all of those tools is usually a phased over time
one.

=============
<<"Brian Fraley" <BrianFraley@discussions.microsoft.com> wrote in message
news:5D4EC4ED-66E4-4032-A69E-37EECB451FAE@microsoft.com...
Gyorgy,

Thank you for your reply. We have looked at doing that but since we use
WSUS would prefer that MS did it as an update. Less testing and
implementation problems when it is done through WSUS as an update.

Brian >>
--

Bob Buckland ?:-)
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

Good Morning,
I am only seeing the Compatibility Pack available as an .exe, not an .msi --
where can I find the .msi?
Thank you, D

"Bob Buckland ?:-)" wrote:

> Hi Brian,
>
> My guess is that at some point after the retail release of Office 2007 (30Jan) that the compatability pack will be available as a
> WSUS update (more than one MS product group involved <g>).
>
>
> There are 2 parts to the compatibility twin pack. The recognizer is already provided in Windows updates as I understand it and folks
> who try to open an Office 2007 file should be seeing a prompt to obtain and install the converter pack, but not all companies want
> that approach to happen). There is information on deploying the converter pack in the Office 2007 Resource kit at
> http://microsoft.com/office/ork
>
> Depends somewhat on your time frame for needing this capability on a widespread basis and your internal practices/policies. There
> will likely be similar issues in multi-lingual installations as the creation of all of those tools is usually a phased over time
> one.
>
> =============
> <<"Brian Fraley" <BrianFraley@discussions.microsoft.com> wrote in message
> news:5D4EC4ED-66E4-4032-A69E-37EECB451FAE@microsoft.com...
> Gyorgy,
>
> Thank you for your reply. We have looked at doing that but since we use
> WSUS would prefer that MS did it as an update. Less testing and
> implementation problems when it is done through WSUS as an update.
>
> Brian >>
> --
>
> Bob Buckland ?:-)
> MS Office System Products MVP
>
> *Courtesy is not expensive and can pay big dividends*
>
>
>

If you go to a command prompt and execute the file with a /? after it you
will see the options to extract the files. /extract creates the files and
folder structure. We are testing using group policy to push out the patch.
You only need the O12Conv.msi and the O12Conv.cab file for this.

Brian

"DFM" wrote:

> Good Morning,
> I am only seeing the Compatibility Pack available as an .exe, not an .msi --
> where can I find the .msi?
> Thank you, D
>
> "Bob Buckland ?:-)" wrote:
>
> > Hi Brian,
> >
> > My guess is that at some point after the retail release of Office 2007 (30Jan) that the compatability pack will be available as a
> > WSUS update (more than one MS product group involved <g>).
> >
> >
> > There are 2 parts to the compatibility twin pack. The recognizer is already provided in Windows updates as I understand it and folks
> > who try to open an Office 2007 file should be seeing a prompt to obtain and install the converter pack, but not all companies want
> > that approach to happen). There is information on deploying the converter pack in the Office 2007 Resource kit at
> > http://microsoft.com/office/ork
> >
> > Depends somewhat on your time frame for needing this capability on a widespread basis and your internal practices/policies. There
> > will likely be similar issues in multi-lingual installations as the creation of all of those tools is usually a phased over time
> > one.
> >
> > =============
> > <<"Brian Fraley" <BrianFraley@discussions.microsoft.com> wrote in message
> > news:5D4EC4ED-66E4-4032-A69E-37EECB451FAE@microsoft.com...
> > Gyorgy,
> >
> > Thank you for your reply. We have looked at doing that but since we use
> > WSUS would prefer that MS did it as an update. Less testing and
> > implementation problems when it is done through WSUS as an update.
> >
> > Brian >>
> > --
> >
> > Bob Buckland ?:-)
> > MS Office System Products MVP
> >
> > *Courtesy is not expensive and can pay big dividends*
> >
> >
> >

Bob,

Thank you for the reply. Since a user account doesn't have enough rights to
install the patch we are testing with the msi and group policy. So far it is
working but having it available through WSUS eliminates so much work on our
end.

Just my littel rant but in MS's infinite wisdom IE7 is considered a high
priority must have update so why isn't the ability to open files not rate?

Brian

"Bob Buckland ?:-)" wrote:

> Hi Brian,
>
> My guess is that at some point after the retail release of Office 2007 (30Jan) that the compatability pack will be available as a
> WSUS update (more than one MS product group involved <g>).
>
>
> There are 2 parts to the compatibility twin pack. The recognizer is already provided in Windows updates as I understand it and folks
> who try to open an Office 2007 file should be seeing a prompt to obtain and install the converter pack, but not all companies want
> that approach to happen). There is information on deploying the converter pack in the Office 2007 Resource kit at
> http://microsoft.com/office/ork
>
> Depends somewhat on your time frame for needing this capability on a widespread basis and your internal practices/policies. There
> will likely be similar issues in multi-lingual installations as the creation of all of those tools is usually a phased over time
> one.
>
> =============
> <<"Brian Fraley" <BrianFraley@discussions.microsoft.com> wrote in message
> news:5D4EC4ED-66E4-4032-A69E-37EECB451FAE@microsoft.com...
> Gyorgy,
>
> Thank you for your reply. We have looked at doing that but since we use
> WSUS would prefer that MS did it as an update. Less testing and
> implementation problems when it is done through WSUS as an update.
>
> Brian >>
> --
>
> Bob Buckland ?:-)
> MS Office System Products MVP
>
> *Courtesy is not expensive and can pay big dividends*
>
>
>

Thank you for the quick response.

"Brian Fraley" wrote:

> If you go to a command prompt and execute the file with a /? after it you
> will see the options to extract the files. /extract creates the files and
> folder structure. We are testing using group policy to push out the patch.
> You only need the O12Conv.msi and the O12Conv.cab file for this.
>
> Brian
>
> "DFM" wrote:
>
> > Good Morning,
> > I am only seeing the Compatibility Pack available as an .exe, not an .msi --
> > where can I find the .msi?
> > Thank you, D
> >
> > "Bob Buckland ?:-)" wrote:
> >
> > > Hi Brian,
> > >
> > > My guess is that at some point after the retail release of Office 2007 (30Jan) that the compatability pack will be available as a
> > > WSUS update (more than one MS product group involved <g>).
> > >
> > >
> > > There are 2 parts to the compatibility twin pack. The recognizer is already provided in Windows updates as I understand it and folks
> > > who try to open an Office 2007 file should be seeing a prompt to obtain and install the converter pack, but not all companies want
> > > that approach to happen). There is information on deploying the converter pack in the Office 2007 Resource kit at
> > > http://microsoft.com/office/ork
> > >
> > > Depends somewhat on your time frame for needing this capability on a widespread basis and your internal practices/policies. There
> > > will likely be similar issues in multi-lingual installations as the creation of all of those tools is usually a phased over time
> > > one.
> > >
> > > =============
> > > <<"Brian Fraley" <BrianFraley@discussions.microsoft.com> wrote in message
> > > news:5D4EC4ED-66E4-4032-A69E-37EECB451FAE@microsoft.com...
> > > Gyorgy,
> > >
> > > Thank you for your reply. We have looked at doing that but since we use
> > > WSUS would prefer that MS did it as an update. Less testing and
> > > implementation problems when it is done through WSUS as an update.
> > >
> > > Brian >>
> > > --
> > >
> > > Bob Buckland ?:-)
> > > MS Office System Products MVP
> > >
> > > *Courtesy is not expensive and can pay big dividends*
> > >
> > >
> > >

Hi D.,

The .MSI is contained within the .exe and can be extracted for deployment by opening the .exe file with a program such as Winzip.

==============
<<"DFM" <DFM@discussions.microsoft.com> wrote in message news:E89D34AE-6DEA-48B3-A20F-642D2B21B8D9@microsoft.com...
Good Morning,
I am only seeing the Compatibility Pack available as an .exe, not an .msi --
where can I find the .msi?
Thank you, D <<
--

Bob Buckland ?:-)
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

Hi Brian,

The Windows team is bigger than the Office team <g>?

Seriously, probably a testing issue, but IE7 was beta tested probably more extensively in various user scenarios than the Office
compatibility pack had been at time of release.

Also, there will be many admins who do not want to install the compatibility pack as well (i.e. it will be the creator/sender's
problem to provide documents in 'usable' [legacy] formats). For those users the prompt to install the compatibility pack can be
disabled via the registry. That may also be a useful temporary approach if you would rather wait until the Windows Server Update
Service (WSUS) has a package for deployment through that method:
http://support.microsoft.com/kb/929302?kb=1

===============
<<"Brian Fraley" <BrianFraley@discussions.microsoft.com> wrote in message
news:1686B452-D442-411F-B7C5-DE55E4A79B09@microsoft.com...
Bob,
[snip]

Just my littel rant but in MS's infinite wisdom IE7 is considered a high priority must have update so why isn't the ability to open
files not rate?

Brian >>
--

Bob Buckland ?:-)
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

Bob,

Thanks for the response, we are going to have to try and go ahead with the
group policy pushout of the MSI. If we don't our support time will increase
with either "why can't I open this file" or "how do I get this add-in thingy
installed". It would be nice to be able to just disable the pop up and
depend upon senders to send the older file type but being customer support we
don't really have the option. I'm sure you've been there with a salesperson
swearing that the whole deal will fall through if I have to make the customer
resend this file in a differnt format. ;-)

Brian

"Bob Buckland ?:-)" wrote:

> Hi Brian,
>
> The Windows team is bigger than the Office team <g>?
>
> Seriously, probably a testing issue, but IE7 was beta tested probably more extensively in various user scenarios than the Office
> compatibility pack had been at time of release.
>
> Also, there will be many admins who do not want to install the compatibility pack as well (i.e. it will be the creator/sender's
> problem to provide documents in 'usable' [legacy] formats). For those users the prompt to install the compatibility pack can be
> disabled via the registry. That may also be a useful temporary approach if you would rather wait until the Windows Server Update
> Service (WSUS) has a package for deployment through that method:
> http://support.microsoft.com/kb/929302?kb=1
>
> ===============
> <<"Brian Fraley" <BrianFraley@discussions.microsoft.com> wrote in message
> news:1686B452-D442-411F-B7C5-DE55E4A79B09@microsoft.com...
> Bob,
> [snip]
>
> Just my littel rant but in MS's infinite wisdom IE7 is considered a high priority must have update so why isn't the ability to open
> files not rate?
>
> Brian >>
> --
>
> Bob Buckland ?:-)
> MS Office System Products MVP
>
> *Courtesy is not expensive and can pay big dividends*
>
>
>