Wednesday, 20 March 2013

ConfigMgr 2012 / SCCM 2012 SP1 Step by Step Guide Part 20: Software Distribution - Office 2013

Back to main menu

Part 18 described how to create and deploy a Config Mgr application using an MSI file. Part 19 described how to create an application using an EXE file (manually creating the deployment type and detection method).

Creating the Office 2013 Config Mgr Application is a hybrid of the two with a twist.

Office 2013 is installed using setup.exe. However the Windows Installer information can be determined from an MSI found in the installation files (proplusww.msi).

The twist is that you use the Office Customisation Tool (OCT) to customise the settings and prepare for unattended installation (note OCT is only available with Volume Licensing copies of Office)

Copy the installation files to a folder and open command prompt.
Browse to the root of the Office 2013 folder


Enter setup.exe /admin to launch the OCT



Choose to Create a new setup file


OCT launches


Choose default


Browse to "Licensing and User Information". Choose to Accept the License terms. Choose "None" as the Display Level and select "Supress Modal".



Note that this is not an in-place upgrade. Earlier versions of Office products are uninstalled.


Click Add for additional configuration


Note that the name must be in capitals. We don't want the installation to force a reboot.


 Save the file in the Updates folder (call it whateveryoulike.msp)



Close OCT

Now we create the Config Mgr application

 Launch Create Application Wizard





Select Automatically detect information about this application from installation files and browse to the file PROPLUSWW.msi

Note if you are using Office 2013 Standard then you choose Standardww.Msi 


Config Mgr interrogates the MSI and discovers the Windows Installer details


Note that the installation details are now incorrect. We will edit them later. Click Next.



Now we must change the installation parameters. Open the properties of the newly created Application


Choose the Deployment Types tab.


Select Edit.



Select the Programs tab


Replace the installation program field with setup.exe . Leave the uninstall field alone.


On the Content tab, modify the content location to the Office 2010 root media

Click Apply

OK to close Deployment Type

OK to close Application

The application is now ready to be distributed and deployed




Posted by at
Labels: , ,

10 comments:

  1. Unknown28 October 2013 at 07:14

    How to make the program needs Approval from the SCCM Administrator???

    ReplyDelete
  2. Gerry Hampson28 October 2013 at 15:14

    You have that option when you deploy to "Users", not devices.

    ReplyDelete
  3. PaulV6 January 2014 at 03:09

    Hi Gerry,

    You can use the OCT utility without having a volume license copy of office 2013. Download the Office 2013 Admin template, run the exe and extract the files to the original Office 2013 installation folder. Once this is done you can run the setup.exe /admin and it should work fine. Just thought it would be helpful for someone.

    Regards,
    Paul

    ReplyDelete
    Replies
    1. Gerry Hampson6 January 2014 at 09:24

      Thanks for that Paul

      Delete
    2. PaulV6 January 2014 at 17:40

      You're Welcome. Also I modified the uninstall strings to setup.exe /uninstall instead of the default uninstallation string.

      By the way your guides are very useful and are very well laid out. I am planning on taking 70-243 exam hopefully I can pass soon.

      Paul

      Delete
  4. superjudge5 March 2014 at 22:01

    I've followed these instructions to create the very same package (64-bit on an entirely 64-bit domain).

    I've attempted to deploy the package to two test machines, and they have been installing for hours.

    I have also set them to use an MSP file by setting the executable to 'setup.exe /adminfile "\\FQDN\path.MSP"'

    Should I be doing this differently?

    ReplyDelete
  5. Gerry Hampson10 March 2014 at 10:19

    You don't need to use the executable above. Save the MSP to the Updates folder and it is automatically used.

    ReplyDelete
  6. Anonymous28 July 2014 at 15:21

    Hi Gerry, your posts are really informative and helpful. How can I join to see updates and issues on SCCM 2012

    ReplyDelete
  7. Anonymous28 July 2014 at 15:23

    Forgot to mention my email on earlier request, rajiv.k.jindal@gmail.com. I am doing sccm 2012 support, would like to get access to your posts, please advise, thanks

    ReplyDelete
  8. Unknown12 February 2018 at 07:38

    Hello Gerry,

    I have used this guide to create office app
    and used both Setup.exe with admin file and Setup.exe alone as if the .msp file will be used automatically.
    But failed on both tries with error failed to verify the executable file or to construct the associated command line.

    Any thing I should try please.
    Thank you

    ReplyDelete

Subscribe to: Post Comments (Atom)