Microsoft 365 Installation Problems

Fix Slow Office 365 Version 1902 Installation with SCCM

Nimra MalikNimra Malik Nov 14, 2026 868 views

Question details

The user needs to troubleshoot a slow Office 365 ProPlus version 1902 installation that requires Internet access during an SCCM deployment.

Product
Office 365 ProPlus version 1902, Office Deployment Tool, and Microsoft Configuration Manager (SCCM)
Device & OS
not provided
Scenario
Deploying Office 365 ProPlus through SCCM and the Office Deployment Tool, including to devices without Internet access.
Observed behavior
Installation takes much longer than expected, displays a message that Office must stay online, and fails without Internet access. The same issue occurs when setup.exe is run manually.
Before you start

Locate the Office Deployment Tool setup.exe, the deployment configuration XML, and the Office installation files used by SCCM. Identify the configured product, version, channel, languages, and source path so you can compare them with the downloaded content.

Solution 1Recommended

Verify the Office Deployment Tool source and configuration

Use this approach first because the installation also fails when setup.exe runs outside SCCM.

1
Review the configuration XML

Open the deployment XML in a text editor and check the Add element's SourcePath, OfficeClientEdition, Channel, and Version settings, along with the Product and Language entries. Make sure they describe the content you intend to install.

2
Download matching installation files

On a connected device, open Command Prompt in the folder containing setup.exe and run setup.exe /download configuration.xml, replacing configuration.xml with your actual XML file name. Confirm that the configured source location contains the downloaded Office files.

3
Test the local source

Copy the complete installation source and XML to a test device, update SourcePath in the XML to the accessible local source if necessary, and run setup.exe /configure configuration.xml from Command Prompt. Test without Internet access to see whether the source and configuration work independently of SCCM.

4
Check setup logs

If installation still fails, open the test user's %temp% folder and review the Office setup logs for source, download, or configuration errors. Use the reported error to identify missing content or an inaccessible path.

Version 1902 is an older release: Before rebuilding the deployment, check Microsoft's current support and availability information and consider testing a supported Office version and channel.
Free Microsoft Office alternative

Use WPS Office as an alternative to Office 365

WPS Office is a free, lightweight alternative with a familiar interface and support for common Microsoft Office formats, making it easier to move existing documents into a different office suite. It does not repair SCCM or Office 365 deployments.

Free, lightweight office suite for everyday document workCompatible with Microsoft Word, Excel, and PowerPoint formats, including DOCX, XLSX, and PPTXFamiliar editing tools help users transition from Microsoft OfficeProvides an alternative way to work with Office files while an Office 365 deployment issue is investigated
microsoft office alternative - wps office

Frequently Asked Questions

Why does the Office installer ask to stay online?

The installer may need content that is not available from the configured source. Open the Office Deployment Tool XML and compare its SourcePath, product, version, channel, and language settings with the files downloaded for the deployment.

How can I test whether SCCM is causing the problem?

On a test device, run setup.exe /configure configuration.xml from Command Prompt using an accessible installation source. If the same failure occurs manually, investigate the Office source and XML rather than SCCM alone.

How do I prepare Office installation files for an offline test?

On a connected device, run setup.exe /download configuration.xml using the intended Office Deployment Tool configuration. Copy the complete downloaded source to the test device and make sure the XML's SourcePath points to that accessible location.

Where can I check whether SCCM has distributed the Office content?

In the Configuration Manager console, open Monitoring > Distribution Status > Content Status. Check that the deployment content is available on the distribution points used by the affected clients.