Deploy on OfficeConnectPro

Deploy Tenants via Registry

Mon, 01 Jan 0001 00:00:00 +0000

For admins & power users This is an IT admin / power-user task. It requires access to Windows group policy, deployment scripts, or software distribution tools (e.g., SCCM, Intune).

Instead of having each user manually enter tenant details, you can deploy tenant configuration directly to the Windows registry. This is the recommended approach for organizations with many users.

Registry locations

Choose one:

Location	Scope
`HKEY_LOCAL_MACHINE\Software\Adaptive Insights`	All users on the machine (preferred)
`HKEY_CURRENT_USER\Software\Adaptive Insights`	The current user only

Configuration file format

Create an XML configuration file with your tenant details:

Silent Install Workday OfficeConnect with Microsoft Intune (Win32 App)

Mon, 01 Jan 0001 00:00:00 +0000

For admins & power users This is an IT admin / power-user task. Requires Microsoft Intune admin access and the Microsoft Win32 Content Prep Tool.

Microsoft Intune deploys Workday OfficeConnect cleanly through its Win32 app model — silent install, mandatory assignment, automatic upgrade on new releases. This guide walks through packaging, uploading, and assigning the app.

For the SCCM/MECM equivalent, see Silent Install with SCCM/MECM. For tenant configuration after install, see Deploy Tenants via Registry.

Silent Install Workday OfficeConnect with SCCM / MECM

Mon, 01 Jan 0001 00:00:00 +0000

For admins & power users This is an IT admin / power-user task. Requires Microsoft Configuration Manager (the product formerly known as SCCM, now MECM) admin access and a working software distribution channel.

Microsoft Configuration Manager (MECM, formerly SCCM) is still the dominant on-prem software-deployment tool in many organizations. This guide packages Workday OfficeConnect as an Application in MECM, with silent install, supersedence-aware upgrade behavior, and reliable detection.