Office 365 – Automatic deployment of Office 365 with MDT

This blog has been updated by a new blog:
Office 365 – Updated Deployment Guide

Not every blog needs to be technical, sometimes clustering information, that is shattered over the internet can be useful too!

This time I want to explain how Office 365 can be deployed unattended, automatically, first time right!

On my journey into all the new stuff  (for me at least), I’ve encountered allot of things in the past couple of months. Automatic deployment of bitlocker on Windows 8.1, Intune, Server 2012 (R2) etc.

The challenges that arise by trying to work and automate with these new things really make me enjoy my work, because it is fun to do, it provides insight and experience after you have managed to get things working. So was this, when I was looking into Office 365. For a project that involves Windows 8.1, Office 365 and Windows Intune, I was looking on how to gather the right files to do a unattended deployment of Office 365 and it all came down to this:

1. Know which Office 365 plan you have!

First of all, there is this website: Compare Office 365 for Business Plans this Microsoft website explains the number of Office 365 plans that are available and lets you as a customer, reseller or company choose which plan suits best for your purpose.

figure 1.1: Office 365 Business Plans

o365plans

Based on the chosen plan, Microsoft has a list of official product id’s, just like the regular office suites, which are used to identify which version of Office we are dealing with here: Product IDs that are supported by the Office Deployment Tool for Click-to-Run

2. Know which Product ID you need!

As you can see, the product IDs differ much from the Business Plans names:

The following Microsoft Office 365 product IDs are supported by the Office Deployment Tool for Click-to-Run in Office 365 deployments:

  • O365ProPlusRetail
  • VisioProRetail
  • ProjectProRetail
  • SPDRetail (SharePoint Designer)

In addition to these product IDs, the following non-Office 365 product IDs are supported by this tool:

  • AccessRetail
  • ExcelRetail
  • HomeBusinessRetail
  • HomeStudentRetail
  • InfoPathRetail
  • LyncRetail
  • ProfessionalRetail
  • O365HomePremRetail
  • O365SmallBusPremRetail
  • OneNoteRetail
  • OutlookRetail
  • PowerPointRetail
  • ProjectStdRetail
  • PublisherRetail
  • VisioStdRetail
  • WordRetail

These product Id’s come in quite handy, when trying to retrieve the Office 365 click-to-run files, which are no ordinary setup.exe and some source files, but rather exist out of several cab files (depending on what you are downloading) and a number of *.dat files containing the source files.

3. Acquire the Office Deployment Tool for Click-to-Run!

It all starts with the setup.exe for Office click-to-run which can be downloaded here: Office Deployment Tool for Click-to-Run

This is no ordinary setup as mentioned earlier, instead it contains the logic to download Office 365 click-to-run based on certain command line switches and a “configure.xml”

figure 1.2: Office 365 click-to-run setup files

O365setup

4. Know how to use the setup.exe

When downloaded, these files are located in a folder. Open up an elevated command prompt, browse to the folder and type:

setup.exe /?

This will provide the following available information and command line switches:

figure 1.3: command prompt

o365cmd

  • setup.exe /download
  • setup.exe /configure
  • setup.exe /packager

The purpose of each switch is explained in the command prompt.

Based on the configuration of the configure.xml, a Office 365 click-to-run installation will be downloaded to a designated directory. Based on the very brief documentation about the configure.xml, I choose to do the following:

Create one “configure.xml” for downloading and call it “download.xml”, and one “configure.xml” for installation and call it “install.xml”. This way it’s not necessary to change the xml file ever again. Since within the configure xml a download directory is specified, but this directory also functions as a source folder. That’s the reason why I used two xml files, since the download and source directory can be different.

Next I’ve created a command line file (cmd) which does the following when running the Office 365 click-to-run during an automatic deployment:

codeblock 1.1: install.cmd

It copies the source to the local %temp% directory into a seperate folder. It executes the installation of Office 365 click-to-run locally, and unattended, and when done, cleans up the temp folder.

To demonstrate the differences between the xml files, I have provided a screenshot of them opened in Notepad++

figure 1.4: download.xml and install.xml in Notepad++

o365np++

as you can see I’ve used one of the desired Product ID’s specified by Microsoft’s website, I’ve specified on the download.xml a source path where the files can be stored, and on the install.xml the source path for installation.

5. Incorporate in MDT (or any other tool)

In MDT I’ve created the following:

figure 1.5: MDT Application

o365mdt_app

First an application, which calls the install.cmd

figure 1.6: MDT Task Sequence

o365mdt_ts

and embedded this step as an “install application” step in my task sequence. Since I use this task sequence to build reference images, I’ve disabled other versions of Office and added the Office 365 click-to-run as an application to be installed.

Concluding:

Deploying Office 365 click-to-run isn’t that hard to do, you just need to know where to look and how to approach the installation. Keep in mind that whatever Office version you download, this software is not branded to one Office 365 account. The software is universally applicable. Since after the deployment you always need to sign into Office with your Office 365 account, thus activating 1 out of 5 available installations for this account.

Anything to report, contribute or have done deploying Office 365 click-to-run in any other (efficient) way. Please feel free to contribute in the comments, or write me an e-mail or contact me at twitter!

Find attached the screenshots and files used for my Office 365 click-to-run deployment

zip
O365_BlogContent.zip

Thanks for reading 🙂

 

77 thoughts on “Office 365 – Automatic deployment of Office 365 with MDT

    1. Rens Hollanders

      Hi Cindy,

      D: is pointing to my MDT Deployment Share’s hard drive, which is located on a second partition. I just keep my sources on a D: disk, so I can’t pollute or write the C: drive full

      Cheers!

       
      Reply
  1. Cindy

    So D: is not the default location within MDT where applications are stored after they are imported? And are these the files from the Office Deployment Tool?

    Thank you so much for all your help!

    Cindy

     
    Reply
    1. Rens Hollanders

      Hi Cindy,

      Indeed, D: is not the default location after apps are imported in MDT. Check your deployment shares physical path to find imported applications under: X:\DeploymentShare\Applications, where “X:” represents the drive you have used for your share, and “DeploymentShare” for the path and name specified for your DeploymentShare (out of the box the name is also DeploymentShare).
      Furthermore these are all the files related to Office 365.

      Cheers!

       
      Reply
  2. Cindy

    Hi Rens,

    I am not having much luck =( I get an error saying “Couldn’t Install … to check your Internet connection and make sure their is enough disk space on your hard drive…” I have confirm the computer has Internet connection and plenty of disk space. hhhmmm? Am I missing something?

    And once again thank you so much for all your help!

    Cindy

     
    Reply
    1. Rens Hollanders

      Hi, send me your install and configure xml to see if something is wrong. Post it on your skydrive or send me an e-mail at rens dot hollanders at sign gmail dot com

      Cheers!

       
      Reply
  3. Cindy

    Hello Rens,

    The mistake was on my end. I didn’t run the most crucial which was to run setup.exe /download to download the files from Microsoft.

    I have another question, how can I uninstall or perform an in place upgrade with Office 365 click to run?

    Thank you,

    Cindy

     
    Reply
    1. Rens Hollanders

      Hi Cindy, an uninstall can be performed (I think) by using an msiexec /x {guid}. For more information, please see this link: http://support.microsoft.com/kb/296067/en
      An in place upgrade is also something different. I’m guessing Microsoft just releases updates for Office 365 the same as for Office 2013. However at one point in time the two Office Suites are going to differ from each other. Then perhaps you’ll need to execute the installation of a newer Office 365 on an existing machine all over again. Or uninstall the current and install the new one.

      I haven’t had any experiences with this thusfar.

      Cheers!

       
      Reply
  4. Karthik

    Hello Rens,
    Thanks for your useful article. We are in the process of migrating Office 2010 clients to Office 365. I am aware of using OCT (Office Customization Tool) for customizing office 2013. Is there any way to use this along with office 365? OCT tool generates a MSP file, which is installed along with the updates for Office 2013. Will it work with Office 365? Is there any guidance around this?

    Thanks,
    Karthik

     
    Reply
    1. Rens Hollanders

      Hi Karthik,

      You are welcome. Great to hear people like you find my blog usefull 🙂 You cannot use the OCT with Office 365. Everything needs to be configured through the XML file. There are some blogs that give guidance on how to configure the Office 365 components through the XML file.

      Cheers!

       
      Reply
  5. Karthik

    Hi Rens,

    Thanks for your quick response. Is XML file you refer here is install.xml (setup.exe /CONFIGURE install.xml) ? If yes, is there any references on how to make additional configurations to office install like what we used to do in OST to retain the old preferences and settings?

    -Karthik

     
    Reply
  6. Graham

    I have followed these instructions and scoured the relevant TechNet articles, but it won’t work. I have downloaded O365SmallBusPremRetail, but when I run the ODT to with the configure switch I get the start ‘can’t install’ error, as shown in http://support.microsoft.com/kb/2696484. I’ve managed to get O365ProPlusRetail installed without any dramas. Can you help? I am wondering whether there is a problem with the source I have downloaded as there are less files than I would have expected. In the Office\Data folder I have v32.cab and v32_15.0.4623.1003.cab, and in the Office\Data\15.0.4623.1003 I have s320.cab and stream.x86.x-none.dat. Is that what I should have?

     
    Reply
    1. Rens Hollanders

      Hi Graham,

      it appears your download is corrupt. I have checked my version of O365SmallBusPremRetail which I’d already downloaded some time ago. And it exists out of the following files:
      v32.cab
      v32_15.0.4551.1512.cab
      15.0.4551.1512 (folder)
      i321043.cab
      i641043.cab
      s320.cab
      s321043.cab
      stream.x86.nl-nl.dat
      stream.x86.x-none.dat

      So if you can, I would try it again. Feel free to send me your download and install.xml, you have my e-mail address already!
      Cheers!

       
      Reply
  7. Graham

    Thanks for solving my previous problem. Now for the next question. I have a customer on Office 365 Midsize Business, what do I need to download for that? There doesn’t seem to be a code for that version of Office 365. Is the a specific version of Office 365 or do I just install O365ProPlusRetail?

     
    Reply
    1. Rens Hollanders

      Hi Graham,
      If you can’t find a suitable O365 Click-to-Run installation, my suggestion would be to go for the O365SmallBusPremRetail and try to login in with your O365 plan account. Office will inform you either the installed software of Office 365 is or isn’t the correct version. I know it’s a bit tidious, but if you can’t get clear which version you need, you’ll need to log in on your current O365 click to run installation.

      Cheers!

       
      Reply
  8. Graham

    I have downloaded both O365ProPlusRetail (x86/x64) and O365SmallBusPremRetail (x86/x64), and the files are all the same size. I’m puzzled as to what I am downloading now and why do we have to download the different versions where they appear to be the same installation files.

     
    Reply
    1. Rens Hollanders

      Hi,

      I understand it can be a bit confusing. The files indeed are -or at least look like they are- the same. That’s just the way how O365 is wrapped. So basically this will be the trial and error part, where you install the different versions of O365 and check if when logging in with your O365 account, you receive an error message stating that no right version of Office 365 is installed on the current system.

      Cheers!

       
      Reply
  9. Adam

    Hi,
    Anyone know where I can download the officedeploymenttool version 15.0.4623.1003? There are MS articles saying this is the latest release but when you download it, it is .1001 version and log file shows version mismatch when trying to run setup.exe /configure xxx.xml …
    Thanks

     
    Reply
  10. david

    Hi Mate

    Really sorry for the dumb question I’m about to ask but I’m bit confused at moment I’m testing this on a VM, so I only have one drive which is my C:\ by default , I’ve download my Office source files by using the command setup.exe /download.xml, I’ve created the install.xml, and download.xml, but for the Install.bat , when i look in my C:\Windows\Temp\ There’s a folder called clientC005200a4, should this be included in Install.bat
    how should the command look ?

    xcopy “%~DP0*.*” C:\Windows\Temp\O365SmallBusPremRetail /E /I /Y

    C:\Windows\Temp\O365SmallBusPremRetail\setup.exe /CONFIGURE install.xml

    rmdir C:\Windows\Temp\O365SmallBusPremRetail /S /Q

    exit

    Thanks for the help

     
    Reply
    1. Rens Hollanders

      Hi David,

      There are no dumb question’s to my knowledge 😉 The folder you mention “clientC005200a4” doesn’t ring a bell. When you look in your temp folder is the O365SmallBusPremRetail folder present? Or any other O365 folder which might have been created using the cmd. Because the only thing I did was copy the O365 source files from the application folder with MDT to my local machine to let the installation process complete correctly. So normally if you’d copy the folder “O365SmallBusPremRetail” to “C:\Windows\Temp” I’d expect the exact same folder on that particular location.

      I can imagine that O365 is submitted to changes from the Microsoft O365 team all the time. Since O365 is released in waves, not in periodic updates like Office 2010, 2013 etc.

      Cheers!

       
      Reply
  11. Andy

    THANK YOU! I just got started w MDT and because of that have been forced into light scripting w little background. Just seeing how you did this helped me understand how it this new “streaming” method of install works.

     
    Reply
  12. Graham

    Have the supported ProductIDs changes since the release of the new plans on the 1st of October? We no longer have Small Business Premium so has the ProductIDs changed accordingly?

     
    Reply
    1. Rens Hollanders

      Hi Graham,

      Not that I’m aware of, but I haven’t keep track of the O365 products since I wrote this blog.
      If I find some spare time, I’d be happy to look into it.

      Cheers! Rens

       
      Reply
        1. Rens Hollanders

          Hi Graham,

          That’s some usefull information, I will update the post. Thank you for contributing.

          Cheers! Rens

           
          Reply
          1. Graham

            You should also update the plans too. It’s easier now as there are three Business plans (<300) and 3 Enterprise plans; one for just the online services, one for just the desktop installation of Office and one for both. The features change between the Business and Enterprise plans as before as does the products included in the version of Office. There is no mention of Active Directory support for either sets of plans – I'll need to hunt further.

             
  13. Greg

    I have MDT setup and other than the file path to my MDT share it is the same as yours. For some reason i get errors during the MDT deploy that are very generic.

    On the pc i am testing deployment on, if i cd to make command prompts working directory c:\windows\temp\Office365 and then run \\mdtshare\office365\install.cmd it will copy the files and do the install fine.

    In talking with other Engineer i work with this has been a roadblock for him as well, he believes that it is permissions related caused by the account that the MDT deploy is installing the software and has stopped him in the past.

    Currently when you run the task sequence it will copy the files to the temp directory and fail there, then remove the directory per the install.cmd

    Any guidance would be greatly appreciated. I have tried to get the install.cmd to run as admin and it prompts for a password and fails still. disabling UAC does not seem to change anything.

     
    Reply
    1. Rens Hollanders

      Hi Greg,

      Are you familiar with “%~DP0” and do you use it in your CMD file? Because this is the way to go. It sets the relative or full path as the path from where you are executing your setup from. Basically the scripts / commandlines I have provided with this blog should do the trick. They are tested and work 100%. If they do not in your environment you should check for any restrictions concerning the execution of the setup.

      Cheers! Rens

       
      Reply
      1. Greg

        Thanks for the quick response!!

        Funny you ask, I actually didn’t know what it was and changed it to be an absolute path in the script, trying that causes xcopy to fail as it cannot run from a UNC path! so alas i dived into the %~DP0 and it bypasses that restriction. So yes, it does.

        My install.cmd : http://i.imgur.com/FmpyFe9.png

        I’m curious about your MDT setup, mine is a completely fresh install so it’s using all default stuff and i was curious about the account doing your OS install for the task sequence you call this install in. I’m not a pro with MDT so i’m not sure if you can change that, my OS install creates no users and uses local admin to do software installs, launches everything locally on the imaged pc, my deployment share is wide open network permission wise. Do you alter the OS in anyway that i may be overlooking?

         
        Reply
        1. Rens Hollanders

          Greg,

          I clean up the O365 directory after the installation. To my experience, the directory is already cleaned-up before the installation can begin.
          So my advice is to remove the removal of the directory from this script, and execute it somewhere at the end of your deployment with a total clean-up script, which also cleares logfiles, temp directories etc. Another suggestion is that you incorporate a wait time of say 5 to 10 minutes, before the RMDIR action. To my experience, it often happens that the command lines within a CMD do not wait before the command line before is fully processed.

          My MDT environment wether it is test or production is pretty straight forward. Just installed MDT 2013 with ADK 8.1 update 1, and no specific alterations to the OS. Instead be on the look out that you have not placed your machine in an OU with limiting group policy’s configured on it.

          Besides if it works from the command line, and if it works from .bat or .cmd it will also work from MDT.

          Cheers!

           
          Reply
          1. Greg

            I’m not deploying with a domain integrated deployment. Deploying Win7 Pro x64. I was having troubles with the 8.1 ADK install and rolled back to 2012 MDT but it seems very close in functionality.

            Very puzzling that i can get it to work from command line but launching the same script from the same location does not work. I will try removing the rmdir command from the install.cmd and do some testing.

            Thanks for the help so far Rens!

             
  14. Aaron Perrault

    Hi There,
    I just stumbled upon this post, and your great instructions. I hope you can help me with a small issue I am having. It seems no matter what I do I cannot get my downloads to go directly to a Network share. They can go just fine to a local folder, but I am in a large enterprise and we want to have the same thing available to all users.

    I have tried a UNC path, I have tried UNC with IP address, I have tried a mapped drive. Nothing seems to work. It downloads the v32.cab file, the v32_15.0.4675.1003.cab, as well as the first 4 files in the next sub folder, but it appears that it is trying to download the stream.x86.x-none.dat file and it sits there for about 10 minutes, and then it fails.

    Here is my download.xml file

    and the command I am running is

    E:\Office2013\setup.exe /download E:\Office2013\configuration.xml

    What am i missing?

    thanks

     
    Reply
    1. Rens Hollanders

      Hi Aaron,

      If I understand you correctly, you want to download the files to a share, instead of a local folder? What tool are you using, MDT? SCCM?
      Basically I made two XML’s, the first one only downloads and the second one is for installation. I encountered problems too, when wanting to achieve the download and installation based on one xml file.

      Also over time, things might have changed regarding Office 365, since the post I wrote dates back almost a year.

      I’m willing to help, I have your e-mail address. Please feel free to contact me any time.

      Cheers!

       
      Reply
  15. Tim

    Hi there
    Im new to MDT and just stumbled upon your article. There’s one part that still not clicking for me here… how does the “download” come into play at all? Are you manually running the download on regularly? Even when it is downloaded, how is it used by the install process defined in your MDT install step since you dont use that download location at all?

    Thanks in advance!

     
    Reply
    1. Rens Hollanders

      Hi Tim,

      The download happens manually, and is not incorporated in MDT anywhere. It just an action you perform to retrieve the O365 files. Next the installation is something I did do with MDT, created an application, placed the O365 files in the folder, supplied an Installation command line file (cmd) and tested it on a running deployment.

      Does this clarify for you?

      Cheers! Rens

       
      Reply
      1. Tim

        So is this essentially what you’re doing?
        1. Run setup.exe /download manually to your “sources” directory.
        2. Manually copy files to the “.\Applications\Microsoft_Office_365….” MDT application folder which also contains install.cmd, setup.exe and install.xml?

        If this is correct, can you clarify why you choose to store the “download” in the different location from your MDT application folder?

        Thanks again!

         
        Reply
        1. Rens Hollanders

          Hi Tim,

          Exactly, only the setup.exe and install.xml is relevant for deploying Office 365 through MDT. And now you want to know why I copy the files locally before installing? This is due to the fact that I have experienced that running the installation from a network share doesn’t work.. it fails, and that’s something what happens occasionally with certain software. However I do not store the download.xml somewhere else, I just don’t use it anywhere during my MDT deployment.

          Ok?

          Cheers! Rens

           
          Reply
  16. Tim

    Ha, I’m sorry, still a little hazy on a couple things. Not sure why this is so difficult for me to wrap my head around. Let me try asking this a different way.

    Your MDT Applications\Microsoft_Office365 folder – whats in that exactly? Only setup.exe and install.xml? Or do you also include copy the O365 files from your D:\Sources\… folder?

    If you are including a copy of the O365 cab files in the MDT Applications\O365 folder, why use the Applications\O365 folder instead of your Sources folder in download.xml?

    If you are NOT including a copy of the O365 files in the MDT Applicaitons\O365, then doesnt that mean when the installation is performed the install files (cabs) are pulled down from the internet/MS website?

    Thanks!

     
    Reply
    1. Rens Hollanders

      In my .\DeploymentShare\Applications\O365 folder I have:
      – Setup.exe
      – cab files
      – install.xml
      – install.cmd
      – download.xml (but this isn’t used for anything other then downloading the files manually)

      The reason why I splitted it up into two xml files, is that was the only way I’ve managed to get things to work. And the reason why I use the applications\O365 instead of my sources location, is that I would like to keep everything MDT related, inside the MDT deploymentshare.

      Ok?

      Cheers! Rens

      p.s. have some weekend, relax and think about it. My best inspirations occur when I’m not working 🙂

       
      Reply
  17. Pingback: Re-blog – How to deploy Office Pro Plus (C2R) with MDT | Blogging about Microsoft Technologies

  18. Fallon

    Aw, this was an exceptionally good post. Taking a few minutes and actual effort to produce a great article… but
    what can I say… I put things off a lot and never seem to get nearly anything done.

     
    Reply
  19. Jay

    This was an awesome article and got me very far, very easily. My only question is on the working directory. I’m using O365ProPlusRetail x64 and am not sure what to set the working directory to in MDT. I get ‘unable to set working directory. error -2147024894. I had tried:

    .\Applications\Microsoft_Office_365_x64_Professional_Plus_Retail_EN

     
    Reply
    1. Jay

      Ok, I think I figured out the Working Directory issue from other google’d threads. I’m definitely a rookie with this. However, I still get that the ‘application returned an unexpected return code: 1’, during the setup. It is the only application I’m trying to install. I didn’t really follow some of the reasons for multiple directories above, but here is my setup:

      Cmd, xmls and setup.exe are in the Share’s Application\Office365 folder. Along with v32.cab and v32_15.0.4711.1003.cab – but these are 16 KB files. I’m guessing I don’t have the full installer.

      TS -> Applications -> Microsoft Office 365 x64
      -Standard Application
      -Quiet Install Command: install.cmd
      -Working Directory: .\Applications\Office365

      Install.cmd (removed xcopy and cleanup for simplification after none of it was working)
      C:\MDT\Deployment Shares\Testing Share\Applications\Office365\setup.exe /CONFIGURE install.xml

      Install.xml (changed to source path = “” after several tries not working and seeing in other guides that it wasn’t used if files were in the proper directory already or would download anyways if not in the location)

      Obviously, I’m probably doing a lot of things wrong. Your guide has gotten me the closest, but apparently I’m still far away.

       
      Reply
    2. Jay

      DISREGARD!!! Feel free to delete this before it even passes moderation! I figured it out after reading up more on the TechNet articles to understand all the parts combined with your helpful thread here. I also gave myself a break and just tried to install the 32-bit version first. I’ll try to tackle the 64-bit version in the future.

       
      Reply
  20. Louis

    Hi Rens. Thank you for this excellent blog post. I’m in a position where I’m currently setting up an MDT environment at my new job.
    It’s probable that they will want their Office365 available in the Application selection screen. (They want to be able to choose what apps to install for each deployment)
    My question is, since the application package is just running a .cmd, does MDT know to pause the task sequence until office365 is fully installed? I don’t want to cause any issues with applications that are set to install right after it in the sequence.

     
    Reply
    1. Rens Hollanders

      Hi Louis,

      Thanks for your comment. Sorry for my late response, but I think what you are looking for is this: http://ss64.com/nt/start.html START /W or /WAIT will result in a wait for termination of the application, in this case the installation of Office 365.

      Cheers! Rens

       
      Reply
  21. Pingback: Re-blog – How to deploy Office Pro Plus (C2R) with MDT | Akilon – In The Cloud

  22. Freddy

    Hi! I have a problem with MDT. Im trying to deploy Windows 8 and MS Office with it. It installs Windows perfectly but when it gets to the office installation it gives me an error, that it has not enough space at the location where im trying to install it or something like that. Something that it needs 3636mb free space but doesnt have.
    I tried to give the virtual machine 20gb of memory but it didnt solve the problem. I couldnt find anymore places to change the memory size, so could anybody say what sould i do next?

    Thanks for that…

     
    Reply
    1. Rens Hollanders

      Hi Freddy,

      What happens when you perform the installation manually on the designated machine? Either manual installation or command line installation.
      You could check the BDD.log and or SMSTS.log on the machine to receive a better understanding of the problem. Both file can be found in the %localappdata%\temp\ folder.

      Cheers! Rens

       
      Reply
  23. Martin

    Hi Rens,

    thank you for this great post.

    Maybe you can help me with deploying Office 365 through MDT.
    Installation itself is working without a problem, but not the way I want it to.
    MDT thinks that Office is completely installed right after the installation started and goes on with the next step in the task sequence.
    So Office is still installing while MDT installs other programs, updates the client or just restarts the client.
    I already tried “start /w setup.exe /configure ….” but it does not work.
    When I do the installation manually I see that it just shows “… configured successfully” in the command line and the command line is ready to be used again, even though the installation has only started a few seconds ago.

    Any help or suggestion?

    Thank you in advance.
    Best regards.

     
    Reply
    1. Rens Hollanders

      Hi Martin,

      This is unfortunately very common to happen with the installation of Office 365 in this manner. The only solution I can and have come up with is to do a “guestimate” on how long the actual installation would take, and add a couple extra seconds just to be sure. So you could build in a wait time for MDT (like timeout 300, or sleep 300 with PowerShell). Another option would be to let the Office 365 be the last step in your task sequence.

      Anything other then that just isn’t going to work.

      Cheers! Rens

       
      Reply
      1. Martin

        Hi Rens,

        thank you for the quick response.

        Already thought that I would have to do it like this…
        Deploying Office 365 (Office Click-to-Run software) really seems to be a pain in the …
        Anyways, as I do not want to put Office installation as a “hardcoded” task in a task sequence, I put it to all the other applications to make it a selectable application after choosing a task sequence.

        Regards from germany,
        Martin

         
        Reply
  24. Pingback: Office 365 – Updated deployment guide – renshollanders.nl

  25. Jacob

    Thanks for a great article! Unfortunately I am stuck 🙁

    Im trying to do this on a windows 10 machine. I have all the files copied.

    C:\Windows>xcopy “\\gh-mdt2013\mdtbuildlab$\Applications\Microsoft Office365\*.*” C:\Windows\Temp\O365ProPlusRetail /E /I /Y
    \\gh-mdt2013\mdtbuildlab$\Applications\Microsoft Office365\download.xml
    \\gh-mdt2013\mdtbuildlab$\Applications\Microsoft Office365\install.cmd
    \\gh-mdt2013\mdtbuildlab$\Applications\Microsoft Office365\install.xml
    \\gh-mdt2013\mdtbuildlab$\Applications\Microsoft Office365\o365cmd.png
    \\gh-mdt2013\mdtbuildlab$\Applications\Microsoft Office365\o365mdt_app.png
    \\gh-mdt2013\mdtbuildlab$\Applications\Microsoft Office365\o365mdt_ts.png
    \\gh-mdt2013\mdtbuildlab$\Applications\Microsoft Office365\o365np++.png
    \\gh-mdt2013\mdtbuildlab$\Applications\Microsoft Office365\o365plans.PNG
    \\gh-mdt2013\mdtbuildlab$\Applications\Microsoft Office365\O365setup.png
    \\gh-mdt2013\mdtbuildlab$\Applications\Microsoft Office365\setup.exe
    \\gh-mdt2013\mdtbuildlab$\Applications\Microsoft Office365\Office\Data\v32.cab
    \\gh-mdt2013\mdtbuildlab$\Applications\Microsoft Office365\Office\Data\v32_15.0.4753.1003.cab
    \\gh-mdt2013\mdtbuildlab$\Applications\Microsoft Office365\Office\Data\15.0.4753.1003\s320.cab
    \\gh-mdt2013\mdtbuildlab$\Applications\Microsoft Office365\Office\Data\15.0.4753.1003\stream.x86.x-none.dat
    14 File(s) copied

    C:\Windows>C:\Windows\Temp\O365ProPlusRetail\setup.exe /CONFIGURE install.xml

    My install.xml looks like this:

    But i get this error:

    30088-1021

    Something about not having enough spave or no internet which i definately have 🙁

    Any idea what could be wrong?

    Regards
    Jacob

     
    Reply
  26. Mark

    Hello! thank you for this post! I want to ask you about MS professional Plus 2016 (this one http://hardware.nl/microsoft/79p-05552.html) is it reasonable to buy it? As I see it is very expensive. I cannot find good overview of this software via internet also I need advice of an expert as you. In my every day work I use microsoft publisher but I can’t understand what was new added there. I am waiting for your reply a lot!

     
    Reply
    1. Rens Hollanders

      Hi Mark,

      I’m not sure this is a good starting point, do you need Office 2016 for private or business use? If you already make use of Office 365 some plans provide software to go. Have a look at this link to learn what’s new: https://support.office.com/en-us/article/What-s-New-and-Improved-in-Office-2016-for-Office-365-95c8d81d-08ba-42c1-914f-bca4603e1426?ui=en-US&rs=en-US&ad=US I’m not fully aware of improvements made to Publisher. So if an older version of Office would do, perhaps that’s a possible cheaper solution.

      Cheers! Rens

       
      Reply
  27. Marc Westerink

    Hi Rens,

    This approach works like a charm for Office 2016 C2R as well.
    The only modification I did was not including the SourcePath parameter in the install.xml.

    I must admit this is a clever way of preventing MDT to continue after running setup.exe. Closing setup.exe to run another process is imho a little bit nasty since MDT considers the task to be finished and proceed deployment…

    Cheers,

    Marc Westerink

     
    Reply
    1. Rens Hollanders

      Hi Marc,

      Indeed, I did this also for the 2016 version. I’ve created an updated guide on that one. Thanks for letting me know. Much appreciated.

      Cheers! Rens

       
      Reply
  28. Thomas Essick

    Hi Rens,
    I’ve got a strange thing happening with my MDT deployment of Office 365. When I run my OS deployment task while installing Office 365, the Office 365 fails every time with the error code 0-1011 (0). I’ve tried copying all the files locally, still no go. My second task is run from within a currently installed OS and only installs applications. If I select the Office 365 install during this task sequence, it works fine. Any thoughts?

     
    Reply
    1. Rens Hollanders

      Hi Thomas,

      That’s pretty strange, perhaps you should embed a reboot before installation? There is a Microsoft article with possible solutions if you encounter the specific error code: https://support.office.com/en-us/article/Error-code-0-1011-30088-1015-30183-1011-or-0-1005-when-installing-Office-65aa955c-a35f-41d4-b098-8060f2d04264?ui=en-US&rs=en-US&ad=US

      Have you tried that? Also it depends I think on which version of Office 365 you are deploying, since things tend to change every once and a while.

      Cheers! Rens

       
      Reply
      1. Thomas Essick

        Thanks Ren,

        Was able to get my O365 to install finally during the OS task sequence. My configuration file was still pointed to the network share. I’m not sure why MDT acts differently between the OS task sequence and Application task sequence. My configuration file now reads:

         
        Reply
  29. Laurence Leiter

    Hello I am trying to use your method of deployment. It works great until the install.xml is run. It just seems to hang and never actually installs office. I know this post is old but any help would be awesome I so stuck on this lol.

     
    Reply
    1. Rens Hollanders

      Hello Laurence,

      Keep in mind the installation may take up to 20 minutes before Office 365 is actually installed. If your install.xml is identical as the example in my blog it should work fine. Perhaps you can look after some logging during the installation to see the progress or feedback why Office 365 isn’t installing. Also have a look at your eventviewer application log.

      Cheers! Rens

       
      Reply
  30. Brant

    Rens,

    GREAT article. Thank you so much for doing this. One question I find myself asking is why you choose to copy all the files locally first instead of just having it install across the network. Any particular reason? Thank you again for writing this. Great stuff.

     
    Reply
  31. Stian

    I have an Retail iso file With Visio, the folder does not have an admin folder, a config file or an updates folder. How can i customize the isntallation? Ive tried to create a config file manually but it jsut ignores it.

     
    Reply
    1. Rens Hollanders

      Hi you need to run setup.exe from command prompt and type: setup.exe /admin, then you will be able to create an MSP with the Office Customization Tool, this MSP can then be called either by the following command line: setup.exe /adminfile .msp or by placing the MSP in the updates folder of your Office installation.

      Just to make clear you do not have an Office 365 installation, but as you describe a retail iso, and this is installed differently opposed to Office 365.

      Cheers! Rens

       
      Reply
  32. Brent

    I came here to say thanks a lot! This was a great help. Worked swimmingly with Surface Deployment accelerator where you cant run anything off a network share due to no Ethernet cable.

     
    Reply
  33. Chip Hughes

    Thanks, I was able to add this as a task sequence in MDT. I noticed that when I boot the resulting litetouch, it gives you an option to install the application, I thought, great, sometimes I might not want to install. so today I did not check the box under choose applications to install and it installed anyway? Any ideas where I might have gone wrong?

     
    Reply
    1. Rens Hollanders

      Hi Chip,

      If it is installed any way, whether or not you ticked the checkbox, then make sure you don’t have an “Install Application” step in your task sequence, that installs Office 365.
      Or have a setting in your customsettings.ini that forcefully installs applications by GUID.

      Cheers! Rens

       
      Reply

Leave a Reply

Your email address will not be published. Required fields are marked *