Share via

How to Install Office 365(2016) on clients without internet connection

Question

Wednesday, November 4, 2015 11:32 AM

I try to setup office 365 in SCCM 2012 R2 SP1. I'd like the installation to complete, even if the client has no internet connection. That seems to be a problem.

- I used ODT 2016 and downloaded the office source files.

  • I created an install xml file, without source path, as mentioned here: https://technet.microsoft.com/en-us/library/dn708063.aspx
    this article states:
    It's important that you don't include the SourcePath attribute in the Add section of your configuration.xml file. That's because Configuration Manager copies the installation files for an application into a folder under the Configuration Manager client cache folder, and the name of that subfolder is different for each computer. Because the folder name is different for each computer, you can't specify a SourcePath that will work for every computer that you're deploying Office 365 ProPlus to. Instead, leave out the SourcePath attribute. When a SourcePath isn't specified, the Office Deployment Tool automatically looks for the Office 365 ProPlus installation files in the same folder that the Office Deployment Tool is located. That's why we're including the Office Deployment Tool, the configuration.xml, and the Office 365 ProPlus installation files together in the same shared folder.

I also use the same filetree, as shown in this article.

  • my xml file looks like this:
    <Configuration>
        <Add OfficeClientEdition="32" Branch="Current">
            <Product ID="O365ProPlusRetail">
                <Language ID="nl-nl" />
            </Product>
        </Add>
        <Logging Level="Standard" Path="c:\temp\O365\logs" />
        <Display Level="Full" AcceptEULA="TRUE" />
    </Configuration>

- Before I configure everything in SCCM, I try to do the install cmd on a clean VM. The VM has no internet connection.
I run the following command: Setup.exe /configure configuration.xml
Immediately, I get the following error:
We're sorry we can't continue because we weren't able to download a required file. Please make sure you're connected to the internet or connect to a different network, then try again.
Error code: 30183-1011 (1)
extraction from the log file:
11/04/2015 12:21:05.771 SETUP (0xee0) 0xae4  Identity Http Client a9idt Monitorable [HttpWin] sendInternal {"Message": "The request failed to send, but GetLastError returned Result::OK!", "RequestId": "1", "Url": "http://officecdn.microsoft.com/pr/492350f6-3a01-4f97-b9c0-c7c6ddf67d60/Office/Data/v32.cab"} 84327FF3-A687-426B-B695-1EBEC1E742DA

Why would the setup want to download anything? the setup.exe is in the same folder as the office - folder. (the folder conaining my source files)
When I do configure a source path, the install works fine offline.

Is this the way it is supposed to work? Do I have to use a script in SCCM, copying the source files to my machine, and next, starting setup with an xml that has a sourcepath defined?
Or do I just work like mentioned in this article, (https://technet.microsoft.com/en-us/library/dn708063.aspx ) and hope all my clients have (a fast) internet connection?
What is best practice?

All replies (6)

Saturday, November 7, 2015 5:21 PM âś…Answered | 1 vote

Had the same issue.

As soon as I removed the branch attribute from the xml file completly, it installed ok without internet access. Not sure why it is but it worked for me. Will be setting update branch options using GPO instead.

Branch="Current"

Hope that works for you.

Thursday, November 5, 2015 7:28 AM

Hi,

Based on your description >>Before I configure everything in SCCM, I try to do the install cmd on a clean VM. The VM has no internet connection.
I run the following command: Setup.exe /configure configuration.xml<<

Have you copied the Office Deployment Tool and Office 365 ProPlus source files in the same folder to the VM? If no, we will get the error message.

Note that there is no SourcePath attribute in the xml file.  This means that the Office Deployment Tool will first look in the current folder to find the Office 365 ProPlus source files.  Since the source files aren't there, then the Office Deployment Tool will get the files directly from Office 365 across the Internet. The advantage of that is users don't have to be on the local network to get to the source files.  They just need to be connected to the Internet.

You can name the xml file anything you want. For example, InstallFromCloud.xml.

Please see this article:

http://blogs.technet.com/b/office_resource_kit/archive/2013/08/08/how-to-deploy-office-365-proplus-from-an-on-premises-web-portal.aspx

More reference:

https://social.technet.microsoft.com/Forums/en-US/a0ce55a3-61de-4402-9469-aedca4f35c08/office365click-to-run-deployment-with-mdt-offline-media?forum=mdt

Regards,

George Zhao
TechNet Community Support

Please mark the reply as an answer if you find it is helpful.

If you have feedback for TechNet Support, contact [email protected].

Thursday, November 5, 2015 9:41 AM

Hello George,

Thank you for your reply. I have copied my xml, setup.exe and source files into the same folder on my VM:

It still doesn't work. Unless I define "SourcePath" in the xml. The reference links you give, are Office 2013 related. I also tried the same scenario using ODT 2013. Using ODT 2013, offline installations work fine.

Friday, November 6, 2015 1:02 AM

Hi,

OK, I see. I need some times to test. Since this issue is related Office 365 deployment, you can ask in Office 365  deployment forum, they'll provide some help.

https://community.office365.com/en-us/f/156

Regards,

George Zhao
TechNet Community Support

Please mark the reply as an answer if you find it is helpful.

If you have feedback for TechNet Support, contact [email protected].

Monday, November 9, 2015 9:22 AM

Hello Patrick,

Omitting the branch attribute did the trick indeed.
Many thanks. :-)

Wednesday, March 14, 2018 8:03 PM

Did not work for me. Branch is not defined in the XML, yet the ODT still attempts to download from the CDN instead of using what is in the Office folder, which is co-located with the setup.exe and install.xml files. This was working at one point such that ODT would reference the contents in the Office folder. But now it won't, despite explicit guidance from Microsoft that this is how it is supposed to work. MS, please clarify or fix.

Doug

Douglas Cote