Barren

Yeah, we're using SCCM. The UDI is basically just a boot CD with a nice interface to build a system, load OS, drivers, and choose what software you want to load. Just running setup.exe works fine, it just slows down the build process. I could reduce the timeout period from 40 minutes to 20... I assume that all my Win7 builds are fast enough to load office 2010 in under 20 minutes, but I hate that it gives me a red X in the applications installed tab at the end of the build process. I find it odd that setup.exe is not sending a completion code to SCCM.... when I run just setup.exe, that is the problem. I think I'll try a batch file next. Something like this: \\uncpath to a specific server\packages\officeinstaller\setup.exe /adminfile \\uncpath to specific server\packages\officeinstaller\updats\1_customization.msp Not happy about using a UNC path to a specific server, but I'm to the point where I'll try anything.

A different failure this time.. and again, it didn't load. It's crazy... using just setup.exe, it loads just fine, the problem is that it never sends an exit code, so it keeps running till the timeout, then sccm kills the process. I'm wondering if a batch file isn't the way to go here. The problem is that you have to specify a direct path to a server, which is going to direct everyone of my clients to a single source instead of to their local distribution point. Here is the current failure: command line: setup.exe /adminfile updates\1_customization.msp http://www.barrenplanet.com/pics/officefail3.jpg The program is called UDI Installer.

The 1_customizations, is indeed in the updates folder. I'll try your last note and see if that works. I'd rather not specify a UNC path since this is setup on many deployment servers.

Made the change above... ran a build.. Office failed to load completely. http://www.barrenplanet.com/pics/officefail2.jpg In the past, it would load, it would just wait till the 40 minute timer completed before finishing. So... should I try a batch file instead or should I attempt to put "" around my path for the customization.msp file?

It's being deployed during OSD using a UDI. My Office package for the UDI is just using setup.exe, but a friend thought I should try changing the command line to this: setup.exe /adminfile 1_customizations.msp -to see if that works. I have a customizations file of that name in the /updates directory of the source. Thoughts? I may just make the change and try it now.

and here is the log. http://www.barrenplanet.com/pics/officefailure.jpg

Can't post a pic yet.. so here is post 2..

Bringing this thread back from the dead a bit.. I setup my office install as listed 2 posts above, and I'm using it via UDI install. The office package will load, however, it doesn't send the "done" flag ever, so basically, it loads in 10-15 minutes, then sits waiting for the 40 minute timeout before proceeding completing the build. Then upon completion, I have an exclamation point on the Office installer. It does work properly, just takes longer. I've love to get this figured out... Not sure why it wouldn't be sending the "done" flag with success back to SCCM. I'm building a machine right now with the package on it, I'll post up the details from the log, but the last time I saw it, it just said "package timed out" or something similar.