Office 2007 Enterprise - Deployment

Hey everyone,

When I try to deploy Office 2007 Enterprise onto XP SP2, the deployment is
failing because Windows File Protection is kicking in. Group Policy
eventually times out and the process fails.

Does anyone know of a work-around for this?

Thanks
Ben

I have never seen this happen.

You may want to open a ticket with MS at 800-936-4900
--
Eric Palm
MSFT Office Setup


"LBIT" wrote:

> Hey everyone,
>
> When I try to deploy Office 2007 Enterprise onto XP SP2, the deployment is
> failing because Windows File Protection is kicking in. Group Policy
> eventually times out and the process fails.
>
> Does anyone know of a work-around for this?
>
> Thanks
> Ben

Hi Eric,

Thanks for your reply.

Unfortunately I'm in Australia, do you know of either an email address or
local number I should call?

I've worked out exactly what's going on.

Software Update for Web Folders (RosebudMUI.msi) - here is the log file
entry created.

Error 1933. The Windows Installer service cannot update one or more
protected Windows files. SFP Error: 1223.

List of protected files:\r\nc:\program files\common files\microsoft
shared\web server extensions\40\bin\fp4autl.dll

MSI (s) (08:1C) [19:04:06:864]: Product: Microsoft Software Update for Web
Folders (English) 12 -- Error 1933.
The Windows Installer service cannot update one or more protected Windows
files. SFP Error: 1223.

List of protected files:\r\nc:\program files\common files\microsoft
shared\web server extensions\40\bin\fp4autl.dll


I can't find anything to get around this. It's going to be a problem that's
ultimately going to prevent the rollout of Office 2K7...

Frustrating.

I dread the idea of using some dodgy hacking of SFC dll's to disable Windows
File Protection, but if I can't get past this problem - then what choices
will I have...



"Eric A." wrote:

> I have never seen this happen.
>
> You may want to open a ticket with MS at 800-936-4900
> --
> Eric Palm
> MSFT Office Setup
>
>
> "LBIT" wrote:
>
> > Hey everyone,
> >
> > When I try to deploy Office 2007 Enterprise onto XP SP2, the deployment is
> > failing because Windows File Protection is kicking in. Group Policy
> > eventually times out and the process fails.
> >
> > Does anyone know of a work-around for this?
> >
> > Thanks
> > Ben

OK... now thats an error I am familier with!


KB324500 describes this problem for office 2000 and Project 2000. The
solution
is... copy Fp4autl.dll from the cd to the "C :\Program
Files\Common Files\Microsoft Shared\Web Server Extensions\40\Bin\" dir.

The Fp4autl.dll file is located inside the CDROOT\Rosebud.en-us\RbudLR.CAB.
To resolve this issue extract the file out of RbudLR.CAB and replace the file
located at C :\Program Files\Common Files\Microsoft Shared\Web Server
Extensions\40\Bin\ and then reinstall office.


--
Eric Palm
MSFT Office Setup


"LBIT" wrote:

> Hi Eric,
>
> Thanks for your reply.
>
> Unfortunately I'm in Australia, do you know of either an email address or
> local number I should call?
>
> I've worked out exactly what's going on.
>
> Software Update for Web Folders (RosebudMUI.msi) - here is the log file
> entry created.
>
> Error 1933. The Windows Installer service cannot update one or more
> protected Windows files. SFP Error: 1223.
>
> List of protected files:\r\nc:\program files\common files\microsoft
> shared\web server extensions\40\bin\fp4autl.dll
>
> MSI (s) (08:1C) [19:04:06:864]: Product: Microsoft Software Update for Web
> Folders (English) 12 -- Error 1933.
> The Windows Installer service cannot update one or more protected Windows
> files. SFP Error: 1223.
>
> List of protected files:\r\nc:\program files\common files\microsoft
> shared\web server extensions\40\bin\fp4autl.dll
>
>
> I can't find anything to get around this. It's going to be a problem that's
> ultimately going to prevent the rollout of Office 2K7...
>
> Frustrating.
>
> I dread the idea of using some dodgy hacking of SFC dll's to disable Windows
> File Protection, but if I can't get past this problem - then what choices
> will I have...
>
>
>
> "Eric A." wrote:
>
> > I have never seen this happen.
> >
> > You may want to open a ticket with MS at 800-936-4900
> > --
> > Eric Palm
> > MSFT Office Setup
> >
> >
> > "LBIT" wrote:
> >
> > > Hey everyone,
> > >
> > > When I try to deploy Office 2007 Enterprise onto XP SP2, the deployment is
> > > failing because Windows File Protection is kicking in. Group Policy
> > > eventually times out and the process fails.
> > >
> > > Does anyone know of a work-around for this?
> > >
> > > Thanks
> > > Ben

Hi Eric,

The really strange thing about this - there is no files in the C :\Program
Files\Common Files\Microsoft Shared\Web Server
Extensions\40\Bin\ directory prior to installing Office.

The directory structure is there, but are empty folders.

If I try to copy the file from the cab into the directory manually, I get
the Windows File protection prompt.

I've noticed the version shipped with Office 2007 is older than the version
in the dllcache...

Even if I copy the file from the dllcache - I still get the Windows File
Protection prompt.


The problem is, how do I automate this as part of a Group Policy deployment?

I can create a start-up script to do the file-copy before the Software
Installation is initiated, but am I going to endup with computers prompting
users with Windows File Protection errors?

Thanks
Ben

"Eric A." wrote:

> OK... now thats an error I am familier with!
>
>
> KB324500 describes this problem for office 2000 and Project 2000. The
> solution
> is... copy Fp4autl.dll from the cd to the "C :\Program
> Files\Common Files\Microsoft Shared\Web Server Extensions\40\Bin\" dir.
>
> The Fp4autl.dll file is located inside the CDROOT\Rosebud.en-us\RbudLR.CAB.
> To resolve this issue extract the file out of RbudLR.CAB and replace the file
> located at C :\Program Files\Common Files\Microsoft Shared\Web Server
> Extensions\40\Bin\ and then reinstall office.
>
>
> --
> Eric Palm
> MSFT Office Setup
>
>
> "LBIT" wrote:
>
> > Hi Eric,
> >
> > Thanks for your reply.
> >
> > Unfortunately I'm in Australia, do you know of either an email address or
> > local number I should call?
> >
> > I've worked out exactly what's going on.
> >
> > Software Update for Web Folders (RosebudMUI.msi) - here is the log file
> > entry created.
> >
> > Error 1933. The Windows Installer service cannot update one or more
> > protected Windows files. SFP Error: 1223.
> >
> > List of protected files:\r\nc:\program files\common files\microsoft
> > shared\web server extensions\40\bin\fp4autl.dll
> >
> > MSI (s) (08:1C) [19:04:06:864]: Product: Microsoft Software Update for Web
> > Folders (English) 12 -- Error 1933.
> > The Windows Installer service cannot update one or more protected Windows
> > files. SFP Error: 1223.
> >
> > List of protected files:\r\nc:\program files\common files\microsoft
> > shared\web server extensions\40\bin\fp4autl.dll
> >
> >
> > I can't find anything to get around this. It's going to be a problem that's
> > ultimately going to prevent the rollout of Office 2K7...
> >
> > Frustrating.
> >
> > I dread the idea of using some dodgy hacking of SFC dll's to disable Windows
> > File Protection, but if I can't get past this problem - then what choices
> > will I have...
> >
> >
> >
> > "Eric A." wrote:
> >
> > > I have never seen this happen.
> > >
> > > You may want to open a ticket with MS at 800-936-4900
> > > --
> > > Eric Palm
> > > MSFT Office Setup
> > >
> > >
> > > "LBIT" wrote:
> > >
> > > > Hey everyone,
> > > >
> > > > When I try to deploy Office 2007 Enterprise onto XP SP2, the deployment is
> > > > failing because Windows File Protection is kicking in. Group Policy
> > > > eventually times out and the process fails.
> > > >
> > > > Does anyone know of a work-around for this?
> > > >
> > > > Thanks
> > > > Ben

"The problem is, how do I automate this as part of a Group Policy deployment?"

You shouldn't have to automate this, as the issue you are facing should be
unique to the computer you are working on (Unless all the machines in your
envirnment are from an image.) This is not a common issue. Windows doesn't
typically complain about replacing the Fp4autl.dll file.

Try this..
1. Goto Add/Remove Programs>Add/Remove Windows Components>Application
Server>Details>IIS>Details and install (or uninstall if it is already
installed) the FrontPage 2002 Server Extensions
2. Attempt to replace the file
3. whether or to you can replace the file in the step 2 try to install
office.

If this doesn't work I would need to troubleshoot the machine. I am hoping
that you don't have this issue on all the machines in your enviroment.

If my last suggestion doesn't work I would recommend you open a case with MS
at 800-936-4900 so they can get a look at the machine.




--
Eric Palm
MSFT Office Setup


"LBIT" wrote:

> Hi Eric,
>
> The really strange thing about this - there is no files in the C :\Program
> Files\Common Files\Microsoft Shared\Web Server
> Extensions\40\Bin\ directory prior to installing Office.
>
> The directory structure is there, but are empty folders.
>
> If I try to copy the file from the cab into the directory manually, I get
> the Windows File protection prompt.
>
> I've noticed the version shipped with Office 2007 is older than the version
> in the dllcache...
>
> Even if I copy the file from the dllcache - I still get the Windows File
> Protection prompt.
>
>
> The problem is, how do I automate this as part of a Group Policy deployment?
>
> I can create a start-up script to do the file-copy before the Software
> Installation is initiated, but am I going to endup with computers prompting
> users with Windows File Protection errors?
>
> Thanks
> Ben
>
> "Eric A." wrote:
>
> > OK... now thats an error I am familier with!
> >
> >
> > KB324500 describes this problem for office 2000 and Project 2000. The
> > solution
> > is... copy Fp4autl.dll from the cd to the "C :\Program
> > Files\Common Files\Microsoft Shared\Web Server Extensions\40\Bin\" dir.
> >
> > The Fp4autl.dll file is located inside the CDROOT\Rosebud.en-us\RbudLR.CAB.
> > To resolve this issue extract the file out of RbudLR.CAB and replace the file
> > located at C :\Program Files\Common Files\Microsoft Shared\Web Server
> > Extensions\40\Bin\ and then reinstall office.
> >
> >
> > --
> > Eric Palm
> > MSFT Office Setup
> >
> >
> > "LBIT" wrote:
> >
> > > Hi Eric,
> > >
> > > Thanks for your reply.
> > >
> > > Unfortunately I'm in Australia, do you know of either an email address or
> > > local number I should call?
> > >
> > > I've worked out exactly what's going on.
> > >
> > > Software Update for Web Folders (RosebudMUI.msi) - here is the log file
> > > entry created.
> > >
> > > Error 1933. The Windows Installer service cannot update one or more
> > > protected Windows files. SFP Error: 1223.
> > >
> > > List of protected files:\r\nc:\program files\common files\microsoft
> > > shared\web server extensions\40\bin\fp4autl.dll
> > >
> > > MSI (s) (08:1C) [19:04:06:864]: Product: Microsoft Software Update for Web
> > > Folders (English) 12 -- Error 1933.
> > > The Windows Installer service cannot update one or more protected Windows
> > > files. SFP Error: 1223.
> > >
> > > List of protected files:\r\nc:\program files\common files\microsoft
> > > shared\web server extensions\40\bin\fp4autl.dll
> > >
> > >
> > > I can't find anything to get around this. It's going to be a problem that's
> > > ultimately going to prevent the rollout of Office 2K7...
> > >
> > > Frustrating.
> > >
> > > I dread the idea of using some dodgy hacking of SFC dll's to disable Windows
> > > File Protection, but if I can't get past this problem - then what choices
> > > will I have...
> > >
> > >
> > >
> > > "Eric A." wrote:
> > >
> > > > I have never seen this happen.
> > > >
> > > > You may want to open a ticket with MS at 800-936-4900
> > > > --
> > > > Eric Palm
> > > > MSFT Office Setup
> > > >
> > > >
> > > > "LBIT" wrote:
> > > >
> > > > > Hey everyone,
> > > > >
> > > > > When I try to deploy Office 2007 Enterprise onto XP SP2, the deployment is
> > > > > failing because Windows File Protection is kicking in. Group Policy
> > > > > eventually times out and the process fails.
> > > > >
> > > > > Does anyone know of a work-around for this?
> > > > >
> > > > > Thanks
> > > > > Ben