locked
Office 2013 Deployment with different .msp's RRS feed

  • Question

  • I found Ronni's guide for deploying Office 2013 via SCCM 2012 and it's perfect and works great but I have a question. We have differnet license codes for different areas of our organization. In his guide he shows you how to create the Office Customization file (.msp) and to place it in the Updates folder when done. But what if I will have 3 different .msp's in this updates folder? How do I call each one when I do a deployment? Because right now I am just using setup.exe in the installation program of the package and it's only using the one .msp file I have in the updates folder.

    Thanks.

    http://www.ronnipedersen.com/2012/11/how-to-deploying-microsoft-office-2013-using-configmgr-2012/


    • Edited by RBanse Monday, December 22, 2014 7:59 PM
    Monday, December 22, 2014 7:58 PM

Answers

  • Don't place them in the Updates folder. I don't like this method because it means anyone who accidentally initiates setup.exe will get Office installed.

    Instead, place them one level up, in the root, and use the /adminfile option to specify the appropriate msp on the setup.exe command-line. I do this even if there is only one MSP to avoid the accidental installation.

    Alternatively, you could specify the different keys in config.xml files and use the /config setup.exe option to specify the correct one: http://technet.microsoft.com/en-US/library/cc179195%28v=office.15%29.aspx


    Jason | http://blog.configmgrftw.com | @jasonsandys

    • Proposed as answer by Damon. Johns Monday, December 22, 2014 8:28 PM
    • Marked as answer by RBanse Monday, December 22, 2014 8:29 PM
    Monday, December 22, 2014 8:12 PM

All replies

  • Don't place them in the Updates folder. I don't like this method because it means anyone who accidentally initiates setup.exe will get Office installed.

    Instead, place them one level up, in the root, and use the /adminfile option to specify the appropriate msp on the setup.exe command-line. I do this even if there is only one MSP to avoid the accidental installation.

    Alternatively, you could specify the different keys in config.xml files and use the /config setup.exe option to specify the correct one: http://technet.microsoft.com/en-US/library/cc179195%28v=office.15%29.aspx


    Jason | http://blog.configmgrftw.com | @jasonsandys

    • Proposed as answer by Damon. Johns Monday, December 22, 2014 8:28 PM
    • Marked as answer by RBanse Monday, December 22, 2014 8:29 PM
    Monday, December 22, 2014 8:12 PM
  • Thank you. So the path for the first option you mentioned would just simply be:

    setup.exe \adminfile downtown.msp 

    Correct?

    Monday, December 22, 2014 8:26 PM
  • Correct on the path (although you need a forward-slash for the adminfile option and not a back-slash).

    Jason | http://blog.configmgrftw.com | @jasonsandys

    Monday, December 22, 2014 8:28 PM