slolrnr

prathapml: I downloaded the latest Orca (3.1.4000.1830) and did a search for 'Slash_A' as indicated and was not found. Does Office XP RET use different commands? I also searched for 'Slash_Q' , '- SkuredQuiet', and 'SkuredCIW' and found nothing. So the modifications suggested in the posts for Office 2003 do not appear appropriate for Office XP RET or this version of Orca. Now I am realy confused!

Prathapml: Yes it does help, thank you for that reference! Does using this approach to install Office violate your EULA as is suggested or does anyone know for sure. Don't want to create new problems with Microsoft using this approach!

Anybody else have any suggestions?

prathapml: If that code was your answer, it did not work when I tested it. The error message was that silent install was not supported in non-enterprise versions of Office (thanks Microsoft!). I have found nothing else in your posts that suggests another solution, do you have one?

prathapml, you sure have a lot of posts. Is the information on the Office 2003 without product key post of April 15, 2005? This looks like it might be it: CODE setup.exe /QB PIDKEY=YOURSERIALHERE office2k3-sp1.exe /Q regedit /S clear-key.reg the first line installs office silently with the specified key, and second line installs SP1, and third line clears key. The clear-key.reg has to be made from notepad, copy/paste the below into it: CODE Windows Registry Editor Version 5.00 [-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\11.0\Registration]

Need a lot of advice as to how to make my Office XP pro (retail) version upgrade to SP3 and install unattended. There must be other Office retail users who read the MSFN unattended CD instructions and wondered how they got so lucky. I know that you can not create a slipstreamed SP3 version with PRORET.MSI, that's only possible with enterprise versions of office (thanks MSN!). Retail can't use the /a switch or the ork tools. According to a white paper from MSN, it's not a good idea to mix admin full file and binary client updates so they blocked retail users from doing admin installs. The only exception is when it's a service pack like SP3 and the product version is changed to a new baseline, then you can do an admin full file update of the service pack (which replaces files), and the updates after the service pack can be binary client updates (which use a diff file on the hard drive). Unless someone has a workaround for slipstreaming in PRORET, the only option seems to be a chained install or binary client updates added manually. Perhaps someone else has suggestions on how to approach this. Thanks!