Comments on: Office 2007 Silent Deployment

By: Jarvis

Jarvis — Tue, 28 Sep 2010 03:38:46 +0000

yep…the updates folder does work well. However…if you are needing to use multiple MSP files for different automated setups of Office, then you can’t just dump them all into the updates folder…you would need to specify them at the command line. That’s the reason I went that route…I had different divisions who were needing slightly different office installations.

Great comment though!

By: joel Franco

joel Franco — Sat, 25 Sep 2010 20:14:31 +0000

Thank You by your information.

I’ve seen in wpkg.org that to install with a msp custom file is enough to put the .msp file (generated with setup /admin) in the UPDATES folder. Then when you run the setup.exe, it will check the updates folder and automatically run it.

The installer will apply automatically any update in this folder, including the extracted service packs!

Regards,

By: DEZ

DEZ — Wed, 22 Oct 2008 18:42:20 +0000

I am currently running it from the SMS Package source with the adminfile switch pointed to the location of my msp, and it seems to be running fine. But when running via the advertisement it bonks in the first 2 seconds of running.

By: DEZ

DEZ — Wed, 22 Oct 2008 18:18:26 +0000

Okay, I have performed all of the back end sms setup, created my msp file that contains everything, set have tried the install many times, The advertisement pops up, I receive the install, I select run, and I see the processor begin to go, and then I here the Microsoft error bonk, no message, no nothing. I have 2003 installed and have setup the msp to remove the prior office. I don’t see an error pointing to anything, I have it running in normal mode so I can see things start, but I don’t see a thing and only here the error bonk…

Any Ideas???
Thanks for your help.

By: Jarvis

Jarvis — Wed, 20 Aug 2008 17:15:18 +0000

Tony,
If I understand your comment, then it sounds like you are misunderstanding the SMS process…but perhaps I’m just misunderstanding your comment.

You can point the SMS Package to have its source files on a network share…but the install doesn’t actually run from the share…the files are pulled from the DP.

A couple of things for you to look at…does the SMS Server’s computer account have permission on the share? that sounds like the most likely culprit…it would keep the files from being copied to the DP. You could also check the log files associated with the distribution process to see what shows up. I am assuming also that you have attempted to update the DP after changing the source file location.

By: TonyP

TonyP — Wed, 20 Aug 2008 15:59:02 +0000

Hello, I have been testing my SMS 2003 deployment of Office2007. Everything seems to work ok as long as I setup to install from the local drive on the SMS server. My problem is I want to install from a corporate share. When I re-direct the package to the share the files do not download to the distribution points & the test fails – waiting for files to down load. Any Ideas what could cause this break in the install? Thanks much.

By: Gerard

Gerard — Wed, 07 May 2008 19:16:25 +0000

No, I was running it from a UNC path. Apparently, it must have been to long. I copied the install folder to my C drive, and I adjusted the batch file. Now it is installing fine. Thanks for the quick response. I am going to reboot my computer now to complete the install.

By: Jarvis

Jarvis — Wed, 07 May 2008 17:18:19 +0000

Where are you running the batch file? From an SMS program? Is there a reason for throwing that extra level in? If doing it in SMS, just create a program with your command line in it.

Also…and this is a bigger one…have you tried it on more than one workstation? The process as listed in my post is correct. It’s possible that you have an issue with the one workstation. Or…if it fails on multiple, you may have an issue with how your computers have been installed/uninstalled previously.

By: Gerard

Gerard — Wed, 07 May 2008 17:06:07 +0000

I did the first part and it worked great to create the .msp file. I placed the custom .msp file in the same directory as the setup.exe file. I then created a batch file with the appropriate switch; when I run the batch file I receive the following message – “Please go to Control Panel to install and configure system components”. I am using a Volume License CD as opposed to a Retail CD. Any information regarding this with be greatly appreciated. If you like you can email me directly at glagana@lagnor.com.

By: Jarvis

Jarvis — Thu, 21 Feb 2008 14:17:13 +0000

Sanka –
When you go through the process of creating the custom.msp…when you run “setup.exe /admin”, there is a setting for what to do with previous versions. I’m pretty sure the default is to remove the old version and install new. You’ll just need to explore the various settings that you can stipulate and find what works for your requirements. I’ve never had a problem with the previous version not being removed.

When you say it won’t do anything…what do you mean? Is the advertisement running on the box?

Another thing for you to try…to ensure that you have a valid installer and custom.msp…try to remove SMS/SCCM from the process. Just run the installer with the custom.msp from a server share or burn a CD with the install source on it and run from there. It could be that something in your source is hosed. Once you have that working, you can go back into SCCM and make it work there.