Skip to main content

Office 2013 Silent Install

Office 2013 Silent Install Setup

To setup a silent install of Office 2013 follow the below steps.
  • If you have an ISO mount the file and then copy all the files out to a folder. 
  • Run the command \\locationoffolder\setup.exe /admin. This will bring up the Office 2013 customisation tool. 
  • You can apply which settings you require. The main ones you probably need to apply are 
    • Licensing and user interface - choose here if you want to use a KMS key or a MAK key. In the options for the licencing agreements it is best to
      • Tick "I accept the terms of the license agreement"
      • Display level - none
      • Suppress modal - ticked
    • Set feature installation states. Tick the appropriate install options and features which you want.
    • Configure shortcuts. I came across an issue in here which appears to be a known bug. If you try to create desktop shortcuts for any of the applications it would try to force you to enter something in the "start in" field saying this is required. Apparently the fix for this is to put a single square bracket in this field [ 
      • If you entered the location of the exe it would also fill in the arguments and then you get an error when launching the application.
  • Once this is done save you MSP file and then put it into the 'updates' folder in your install directory. 
  • I was then getting an issue when running the setup.exe where it would ask for the product key under the page header "Read the Microsoft licence terms". To get around this you need to modify the config.xml file which is located in the standard.ww or ProPlus.ww folder. Add the fields the first line is as below.
    • <Display Level="none" CompletionNotice="no" SuppressModal="yes" AcceptEula="yes" /> 
  • I also then had an issue where setup.exe did not appear to be reading all the install arguments and I was on a page asking for me to choose the installation I want with an option of Continue or choose options. I had to end up copying the config.xml file into the same directory as the setup.exe file and this seemed to get around this issue.

Comments

Post a Comment

Popular posts from this blog

SCCM - Required Application Not Installing to a collection based on an Active Directory Security Group I recently had an issue where I was trying to install Office 2013 as a required application to a collection based on an AD Security group. This would work fine if I was advertising the install as  'available', however when I set as 'required' it would not install and not even show up in Software Centre. After looking through the Monitoring section in SCCM and had a look at the deployment status I noticed it said success however the Message ID was 10040 and the description was "program will not rerun" I managed to fix this by going to the deployment settings for this collection and then going to scheduling and altering the "Rerun behaviour" to always rerun program.
Post a Comment
Read more

SCCM Task Sequence Fails on SSD Drives Error Error: 87D00267

If you get the error code  87D00267 in a task sequence when deploying an Operating System it  basically means the machine is unable to talk to the DHCP server. From a bit of investigation it  seems that some machines with SSD's actually boot up into the task sequence quicker than it  gets an IP Address! The get around this problem you need to put some pauses in the task  sequence.  The best way is to put the pause in the task sequence just before the point where it  fails. There is  some further reading into this issue below, the sites credited with links.  Part 1 Source: http://ericsccm2012.blogspot.com.au/2013/04/applications-fail-to-install-on-ssd.html Applications Fail to Install on SSD Drives. We received several of the new Dell Latitude 6430U models with SSD drives.  Very nice laptops in a small case.  Easily found drivers for them and loaded into SCCM.  Started the task sequence on one and all look...
Post a Comment
Read more