Software Deployment Question

After putting the .MSI file into the Updates Folder it is not getting installed.

07/26/2012 7752 views


Have created the customised .MSP file and kept into the Updates folder. I have created Program to deploy the Office 2007 using the SCCM 2007 onto the client machine having the OS Windows XP SP2. 

What should be the command line to run the program?

I tried the full command line as setup.exe /adminfile <the path of .MSP> but it fails.

Also I ran the .MSP file onto the client machine but it give the error "The Upgrade patch cannot be installed. Verify that program to be upgraded exist on the system and that you have correct upgrade patch."

Please help!!!!



Answer Summary:
0 Comments   [ + ] Show comments


Community Chosen Answer


If your msp is in the updates folder you should be able to just run setup.exe.

Answered 07/26/2012 by: dugullett
Red Belt

All Answers


By using the OCT, you customize Office and save your customizations in a Setup customization .msp file. You place the file in the Updates folder on the network installation point. When you install Office, Setup looks for a Setup customization file in the Updates folder and applies the customizations. The Updates folder can only be used to deploy software updates during an initial installation of Office 2010.

As an alternative to placing the customization .msp file in the Updates folder, you can use the Setup command-line option /adminfile to specify the fully-qualified path of the location of the .msp file. For example, type: setup.exe /adminfile \\server\share\mychanges\custom.msp.

If you use a folder other than the Updates folder for your customization files, you can specify the folder's location in the Config.xml file by using the SUpdateLocation attribute of the SetupUpdates element. The Config.xml file is located in the core product folder (core_product_folder_name.WW folder, for example, ProPlus.WW for Microsoft Office Professional Plus 2010) for the Office 2010 product that you install. For more information, see Config.xml file in Office 2010.

Answered 07/26/2012 by: jagadeish
Red Belt


How about using double quotes?  Example:  "setup.exe" /adminfile "<the path of .MSP>"

Answered 07/26/2012 by: freewill0078
Senior Yellow Belt


Just point to your Setup.exe in SCCM and give /s as parameter.

Answered 07/31/2012 by: piyushnasa
Red Belt

This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ