And as for the integration of SP1 into Office 2007, you can simply dump the MSPs into the Updates folder and it will automatically run it after the install. However - note that this will increase the installation time.
Main Topics
Browse All TopicsI have read the technet article but I still need help
http://technet.microsoft.c
could someone give me clear instruction on deploying Office 2007 using the MSI file in the Group Policy software installation and how to use the config.xml deploying this method.
second question.
depoying this way can the software be cashe to the user computer first and then come back and do the install later?
third question.
can this be deployed by machine name and not by user name?
please do not send me to an articles. give clear and simple instruction for the 500 points
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Are you talking about the MSP for SP1 or the MSP for the customization of Office 2007?
I haven't tried this, but for SP1 (by itself) you should be able to deploy it thru WSUS or automatically with the Office 2007 install (using the Updates folder) or do a deploy with a command similar to:
"\\server\officesp1\office
To do a remote deploy you can use PsExec to assist with this:
psexec @computerlist.txt -u domain/Admin -p Passwd -c "\\server\officesp1\office
*Note I haven't tested these commands so it may need some tweaking to get it to work.
From what I understand, you _cannot_ use Group Policy to deploy SP1 by itself.
As for the MSP customization for Office 2007 you will need to specify which custom.MSP it is using:
setup.exe /adminfile mycustom.msp
This will not work with a GP deploy though since it GP deployment DOES not use MSP, it will refer to the CONFIG.XML for customization options.
@ ThinkPaper - I have spent all day looking at various articles on Office 2007 and GP. I have seen you post the link http://www.msfn.org/board/
Business Accounts
Answer for Membership
by: ThinkPaperPosted on 2009-01-22 at 14:13:01ID: 23444271
I'm afraid I'm going to have to give you a link.. This is a really good resource you should take a look at: Office-200 7-Unattend ed-Setup-a nd- Fine-tu ning-t7239 2.html
http://www.msfn.org/board/
Basically you have 2 ways to create an unattended installation: by config.xml or by msp.
If you choose config.xml, you would need to modify the text as needed and save it. When you run the MSI, it should reference config.xml by default. If you want to specify different configurations (with different names) you can run the install and specify the config file by typing:
setup.exe /config mycustomconfig.xml
(below is an example for Office 2007 Professional)
If you choose to do a MSP for the install, you will need to run the administration tool to create the MSP:
setup.exe /admin
This will initiate the creation of your MSP.
Once created, it will not automatically use the MSP for installation. You will need to run this command to do so:
setup.exe /adminfile mycustom.msp
As for group policy installation, one question:
do the machines have existing Office installed (2003) and was that deployed by GPO?
I advise you be VERY wary of deploying Office 2007 via GP. If you've read other posts, you'll find that MS has seemlingly stopped "pushing" GP as a way to deploy software. While they give you some insight in deploying Office 2007 via GP, they don't offer much. Support is minimal. The issues you may run into with the GP install are: (which i've ran into)
- Office installing partially on some systems.
- Office 2003 not being removed from the client machines and Office 2007 installed side by side or partially on the machine
- When user logs on, it may take 10-15 for "Office 2007 setup".
>>depoying this way can the software be cashe to the user computer first and then come back and do the install later?
Yes, but not by GP. A script will handle this much better and I believe this is one of the options MS has provided (via logon script or on reboot)
>>can this be deployed by machine name and not by user name?
Yes you can set it up to do a machine installation vs user install. It does NOT have to be a user based install
Ultimately, I ended up doing a gradual deployments based room by room .. We did a step by step process to minimize problems...
1) remotely remove office 2003 and initiate reboot
2) A script to locally cache the needed files
3) run the script to install the software and reboot
3) log on 1 machine in the room remotely to ensure that the installation caused no issues and office 2007 deployed properly.
Select allOpen in new window