Anyone please? Maybe @Gatt
This is how I get office 2010 to deploy in SCCM:
run the office setup.exe with the "/admin" switch to create your MSP (I called it default.msp and placed in the "updates" folder within the Office Setup Dir..)
In the Setup section:
Install Location and Organisation name: [Org Name=YOUR_ORG_NAME_HERE]
Licencing and user interface: [Key as per required (KMS/MAK)] , Accept EULA, Display Level = NONE, suppress Modal, no Cancel]
Everything else as you need it - I'd leave "Remove previous installations" set to default so that it removes all previous Office installs
Save it and update your DP in SCCM
Now for the Program / Advert
for Programs the command line just needs to be "setup.exe" (as long as you have the "default.msp" file in your Updates folder it will automatically use this)
Environment tab should be - Whether or not a user is logged in and run with admin rights and run with a UNC Name - no other settings needed here
Windows Installer - import and find "ProPlus.WW\ProPlusWW.msi" (Not really needed but good practice if using MSI's)
Other tabs as you need
Add a DP and update/refresh
When refreshed - create your advert in the same way you normally would...
FN-GM (22nd May 2012)
Problem is users rebooting the PC halfway through setup, had that a few times even with the notification bar showing!
Also Office 2007 sometimes acts silly when uninstalling and needs the Fixit \ Offscrub tool to clean it completely...
I have a free MS support call i might get them to do it for me
FN-GM (6th June 2012)
What happens if office 2010 isnt installed?
That I'm not too sure on - but suspect that since its using an MSP file and the /P switch (patch?), then it will probably fail if Office isn't installed.
It may be worth testing this though as it might work.
You could create a collection query via DCM and run the above only if Office 2010 is installed on the PC (Compliant) and run the full install if its not (Non-Compliant)
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.
Can't post a pic yet.. so here is post 2..
and here is the log.
Seen this error before and its a bit tricky to resolve
Is this being deployed as part of an OS Deployment or just Office itself?
If the latter - it could be a corrupted CCMClient setup - or more accurately the WMI sections of the client (the logs show a WMI error just before all the red lines..)
Try removing all traces of the client (ccmsetup /uninstall) and then reinstall it and try the deployment again
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.
Made the change above... ran a build.. Office failed to load completely.
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?
There are currently 1 users browsing this thread. (0 members and 1 guests)