I have returned to the most basic setup possible for unattended installation. No .MSP-file generated from the OCT. No MUI language packs, just the basic Office DVD copied to a network share and I have the following defined in ProPlus.WW\config.xml:

<Display Level="none" CompletionNotice="no" SuppressModal="yes" AcceptEula="yes" />
<AddLanguage Id="en-us" ShellTransform="yes"/>
<Logging Type="standard" Path="%temp%" Template="Microsoft Office Professional Plus Setup(*).txt" />

For debugging reasons I deploy via a script (.pts) which contains:

/run /wait \\myserver.xx.nn\prism\Unattend\office2010\setup.exe /config \\myserver.xx.nn\prism\Unattend\office2010\ProPlus.WW\config.xml

The account I deploy under is member of administrators group on client, it is my normal account for deployment.
Installation will fail with error 1603. It fails on different msi files most of the time, sometimes at the beginning, sometimes at the end or inbetween. Typically a msi fails and rollback is made.

I have turned on extensive logging without finding any relevant clues, other than that I should make sure I have enough permissions.

If I cut&paste the above cmd line on client (with "start /wait ..." instead of /run), then setup will work each time so I think I have excluded errors in my media.
I have also tried copying the complete network installation to local disk and have Prism launch it from c:\tmp, thereby excluding network problems.

It seems like my problems only occur when setup is launched via Prism (which seem to run under WoW64, I do not know if that matters?).

Anyone else who has successfully managed to deploy Office 2010 Pro Plus in unattended mode on Windows 7 x64 using Prism? I have lots and lots of error logs collected, but maybye someone could verify that it actually is possible to deploy Office 2010 with Prism in unattended mode? How is it done?

Regards,
Niklas

I'm going to assume you also made sure that you used the PIDKEY option in the config.xml file to specify the product key of Office 2010.  I have also tested this while running as just a command task with this configuration:

Command Line:  \\Server\Office2010\Setup.exe

Command Options: /config \\Server\Office2010\config.xml

I set the task to run unattended and to run as the local system account.  After about 10-15 minutes for the install, I logged onto the computer and verified that the product was installed and didn't require a reboot.

Office will default to KMS if no PID is assigned, we use KMS (it also acivates fine once setup completes).
UAC is turned off, I have tried deploying under a domain account which is memeber of local admins on test machine, have tried account which is member of domain adminis. No GPO:s applied except for a password policy. Have tried a command task instead of script. Have tried several physical machines as well as virtual.

I need to use a domain account in order for Prism to read the installation files from a file server. How do you manage to install Office 2010 as local system using Prism in unattended mode? Local system is not allowed to access network resources??

The exact same installation seem to work just fine when deployed to XP clients, and as I mentioned before setup works fine on Win7 x64 as well if it is invoked interactively.