How to Install and Update Microsoft 365 Offline on an RDS Server
Question details
The user needs to securely deploy and maintain Microsoft 365 on a disconnected Windows Server 2019 Remote Desktop Services (RDS) server.

- Product
- Microsoft 365 Apps
- Device & OS
- Windows Server 2019
- Scenario
- Deploying and updating Microsoft 365 in an air-gapped or offline RDS environment where standard internet-based installers cannot function.
- Observed behavior
- The server has no internet connection, meaning all installation files, configuration XMLs, and ongoing updates must be downloaded on an external computer and manually transferred for local deployment.
Ensure you have an internet-connected computer with sufficient storage to download the installation files, a secure transfer method (like a USB drive) for the offline server, and administrative privileges on the RDS server.
Install Microsoft 365 Offline via the Office Deployment Tool
Use the official Office Deployment Tool (ODT) on a connected PC to fetch the necessary installation files and configure them for an offline RDS deployment.
The standard Microsoft 365 installer requires an active connection to the Microsoft Content Delivery Network (CDN). To bypass this, IT administrators must use the ODT to download the raw files externally, then deploy them locally.
On an internet-connected computer, download the Office Deployment Tool from the Microsoft Download Center and extract the files to a local folder (e.g., C:\ODT).
Create a configuration.xml file in the ODT folder. Ensure it contains the necessary RDS attributes, specifically setting '<Property Name="SharedComputerLicensing" Value="1" />' and defining the SourcePath to the local folder where files will be placed.
Open Command Prompt as an administrator, navigate to your ODT folder, and run 'setup.exe /download configuration.xml'. Wait for the Office files to download into the folder.
Copy the entire ODT folder—including setup.exe, configuration.xml, and the downloaded Office data folder—and transfer it to a local drive on the offline Windows Server 2019 RDS server.
On the offline RDS server, open Command Prompt as an administrator, navigate to the transferred ODT folder, and execute 'setup.exe /configure configuration.xml' to begin the offline installation.

Establish an Offline Update Process
Since the RDS server cannot connect to the Microsoft CDN automatically, updates must be managed manually using an administrative deployment method.
Looking for a Simpler Offline Office Solution? Try WPS Office
Deploying Microsoft 365 in an offline RDS environment can be highly complex, requiring XML configurations, manual file downloads, and constant maintenance. WPS Office offers a straightforward, single-file offline installer that is fully compatible with Microsoft Word, Excel, and PowerPoint formats. It is lightweight, resource-friendly, and perfect for isolated remote desktop environments.
- 1. Download the Installer: Download the WPS Office offline installer on a connected PC.
- 2. Transfer to Server: Copy the single installer file to your offline RDS server.
- 3. Install Globally: Run the installer to instantly provide complete Office capabilities to all RDS users.

Frequently Asked Questions
Can I use the standard Microsoft 365 installer on an offline RDS server?
No. The standard Microsoft 365 setup requires an active internet connection to download application files from the Microsoft CDN during installation. For offline servers, you must use the Office Deployment Tool (ODT) to download the files externally first.
How does Microsoft 365 activate on an offline RDS server?
Microsoft 365 Apps require internet access at least once every 30 days for license verification. For fully disconnected (air-gapped) environments, standard Microsoft 365 subscriptions will eventually deactivate. You may need to use an alternative licensing method, an on-premises KMS server for Office LTSC, or temporarily allow proxy access to Microsoft's activation servers.
What happens if I don't enable Shared Computer Activation on the RDS server?
If Shared Computer Activation (SCA) is not explicitly enabled in your configuration.xml file, users will be prompted to activate Office individually, which will fail and consume their limited personal installation counts in a multi-user RDS environment.




