2007 client install

[Siggy]

I'm preparing for a rollout of about 200 2007 pro clients.
I've used the administrative setup to build my own msp file, then put the
SP2 + kb 969409 in the updates folder.
most of my client workstations are still on xp sp2, upgrade to xp sp3 is busy
during my pilot test, I've noticed that the SP2 is missing on some machines
in the setup log file I found the following entries:

Failed to apply patch \\server\share$\Project Professional 2007 with SP2
(Microsoft)\source\updates\ProjectWWsp2.msp
Error applying patch: <Properties><Property name="Description">Compound
error encountered.</Property><Property
name="Hresult">-2147467259</Property></Properties>
Error: Type: . PatchApplicationFailure ErrorCode: -2147467259(0x80004005).
Unspecified error

Not showing completion dialog because it was not requested.
Reboot requested if needed.
No reboot is needed.
Catalyst execution finished: 05/07/2009 03:42:32. Return code: 0.
PERF: TickCount=41270984 Name=RunSetup Description=End function

the thing Is that due to returncode 0 the distribution thinks everything is
ok
before I do a check on the project.exe file version, what options do I have
to make sure that return code 0 really means that everything is ok.

and what causes setup to fail to install this patch sometimes ??

 

[Christophe Fiessinger [MSFT]]

Project 2007 requires XP SP2 at a minimum

 

[Siggy]

now you're confusing me ...

all machines are on XP sp2, but some are on XP sp3

should I have Xp sp3 in order to have project 07 SP2?

 

[Christophe Fiessinger [MSFT]]

XP sp2 is the minimum OS requirement so if you have XP SP2 you are fine
since it contains SP2.