We are using a Batch File and a MSP with a config.xml.
Works very good....
setup.exe /adminfile youranswerfile.MSP /config ProPlus.WW\config.xml
Check the Office Customization Tool....for MSP file:
I have found when Office 2010 is deployed via the Landesk software deployment portal the portal crashes half we though the install with a HTTP error. The install completes fine but it s not a good look having the portal stop refreshing and showing a HTTP error half way though the install. Anyone else experienced this? Any fix?
Which delivery method did you use and did you install on a Windows 7 machine. I only get the setup.exe to run but never takes off even though I have my config.xml setup for a silent install.
LANDesk IT has successfully tested Office 2010 package in our company environment. I checked his setting. Not complex, just set the setup.exe as the main executable, add all the other additional files (including the .msp answer file), push delivery method (run from source). Basically he followed the BKM for office 2003. :-)
We have successfully used the same deployment in our environment, deployed on 147 systems so far. I put it as an always listed in desktop manager with run from source.
Maybe you can help me sort out one issue i am seeing with software deployment through Desktop Manager. I am seeing a large number of systems coming back with Delyaed as the status.
In the config.xml file. what is it that you need to input?
Doesn't the .MSP file takes care of all the office configuration?
I think you can use both. I have succesfully deployed Office 07, and 2010 simply using the msp method. Once you generate the MSP file using the office customization tool, you dump it in the updates folder(along with any patches/service packs) and off you go.
We are getting ready to deploy office to 3000 users and I would like to use this method you described. Can you shed more lights on the processs?
Any help will be appreciated b/c I am not very familiar with all the batch files and scritps
With office 2010 you just run the setup.exe /admin (might be /a with the new software...sorry been a year since i did teh setup) in a CMD line or the run line in windows. This will open the admin install tool from windows and walk you through creating the MSP file. Stick that in the updates folder contained in the windows instal files along with any office 2010 pacthes you want rolled into teh install. After that we setup i setup a distribution package and used Desktop manager (software portal if you are on version 8) to advertise it to our users
Great! thanks alot. We have 34 sites and it looks like this method will not work for all of them. I'll utilize this patch method for my current site and try to find a way to zip up the office installation files after creating MSP files to be distributed to prefered servers accrss the WAN to other sites.
Still searching how to accomplish this Zip and push method using probably batch file.
We were able to use a combination of 7-zip (http://www.7-zip.org/) and batch files to deliver the Office 2010 package to remote sites after configuring the .msp file using OCT (http://technet.microsoft.com/en-us/library/cc179097.aspx). The zipped file is copied to the local machine and extracted into a folder, then the batch file calls the .msp file to start the installation.
We use the same way for deploying Office 2003, 2007 and 2010.
We have the main files zipped into a self extracting EXE (using WinRAR), a batch file and the MSP.
The main file in the deployment package is the batch file. The others are additional files. After everything is downloaded to the client, the batch file invokes the EXEs so that they extract and then it invokes the extracted setup.exe with the /admin and /config options pointing to our customized MSP and config.xml files.
We have over 60+ offices but only 35 LANDesk distribution points so "running from source" is not an option for us, otherwise, we would kill the WAN links for every install.
We don't zip the MSP so that we can reuse the same self extracting EXEs with different MSPs (with Outlook, w/o Outlook, keep previous version of office, upgrade all removing old versions, etc.)