Software Deployment

for what it's worth this is how we got it to run. The config.xml file was placed in the root of the zip file along with the setup.exe to to get it to run.

Sounds like you are running it as Use default. Under managed installed make sure you click the radial button that says "Configure Manually" and then put in your "setup.exe" /admin "custom.msp". You may or may not need the quotes.

I am using the Configure Manually, the current iteration of the command line is:

"setup.exe" /adminfile "Updates\custom.msp"

I have a deployment for Office 2007 the same way you have your 2010.

My command line reads:
"setup.exe" /adminfile "silent.msp"

Two things to look at. Try putting the .msp file in the same directory as setup.exe and make sure the "Don't Prepend msiexec.exe:" is checked. This will cause an invalid command to be issued

No joy.

Make sure the setup.exe is at the root of the zip file, as well as all the other files. The MSP should be placed in the Updates directory. Try a manual command line "setup.exe" It will detect and apply the MSP found in the Updates directory - no need to add to the command line.

I believe that the install process is the same as Office 2007

http://www.kace.com/support/kb/index.php?action=artikel&cat=4&id=992&artlang=en

Two notes:

1. .MSP files, whether created by the Office Customization Wizard or something else (like a service pack), do not have to be on the command line, as long as you put them in the Updates subdirectory of the main Office directory. Any .msp in that Updates folder is run automatically, in alphabetical order. So, if you have two .MSP files in the Updates subdirectory, you might rename them 1Custom.msp and 2ServicePack.msp, then just run setup.exe from the parent directory. By leaving these off the command line, you may solve the referencing problem.

2. When Windows installers use auxiliary files, I often find I have to use a full path name, especially with KBOX-based installs. Sometimes it can be a relative path name like ..\1file.txt, and sometimes it needs to be an absolute path name like "$(KACE_DEPENDENCY_DIR)\1file.txt". With Office 2010, I use the /config parameter from a batch file, and if I'm remembering correctly, I used a relative path name, something like this:
setup.exe /config ProPlus.WW\config.xml
If you need to use the KACE variables inside a batch file, you can pass them in like this:
MI command configured manually: batch.bat "$(KACE_DEPENDENCY_DIR)"
In the batch.bat file: %1\setup.exe /config %1\ProPlus.WW\config.xml
(Though the quotation marks in the fully resolved path name are in the wrong place, this still seems to work.) Sande