The Skedda Companion App can be deployed in a few different ways depending on your IT environment. Some teams prefer to have users install it themselves, while others want to distribute it centrally using endpoint management tools.
Important Note: regardless of how it is installed, every user still needs to sign in to the Companion App individually after installation. Ensure this is communicated across your organization.
Option 1: Microsoft Intune deployment for Windows
Because the Companion App is delivered as an .exe installer rather than an .msi, it should be packaged in Intune as a Win32 app. In general, MSI files give Intune more built-in install and detection information automatically, while EXE files are more flexible but usually require IT to define the install command and detection rule manually.
Windows Installer Link:
Important setup note
The current Windows installer is a per-user install, which means it installs into the signed-in user’s local profile rather than as a system-wide application.
Install location:
%LOCALAPPDATA%\Skedda Companion\
Because of that, Intune install behavior should be set to User, not System.
If deployed in System context, the app may install into the SYSTEM profile rather than the actual employee’s profile.
Silent install command
Replace the filename version as needed:
skedda-companion-1.1.1-windows-x86_64.exe /S /R
Flags
/S = silent install
/R = launch the app immediately after install
Optional:
/NS = skip Start Menu / Desktop shortcut creation
Recommended detection rule
Use a file-based detection rule:
Path:
%LOCALAPPDATA%\Skedda CompanionFile:
skedda-companion.exeDetection method: String (version)
Operator: Greater than or equal to
Value:
1.1.1.0
If detection is inconsistent
Because the app installs per user, some environments may find that a PowerShell detection script is more reliable than a plain file rule. In that case, the script should:
resolve the signed-in user’s LocalAppData
check for Skedda Companion\skedda-companion.exe
compare the file version against the expected version
Best for
Intune-managed Windows environments
Organizations that want centralized distribution
Teams comfortable managing per-user Win32 app installs
Option 2: Intune or MDM deployment for Mac
For Mac environments, the Companion App can be distributed using the .pkg installer through your existing Mac management workflow.
Best for
Centrally managed Mac fleets
Organizations using Intune, Jamf, Kandji, Mosyle, Addigy, or similar tools
Teams already used to package-based Mac deployments
Mac package link
Mac (ARM64 + Intel): https://app.skedda.com/companion-app/installer-latest/darwin-aarch64-pkg
How it works
Your IT team distributes the package through its normal Mac software deployment process, then users sign in to the app individually after installation.
Notes
Confirm package compatibility with your Mac fleet before wide rollout
If your environment includes Intel Macs, check with Skedda before deployment
Users still need to sign in once after install
Option 3: Other managed Windows deployment tools
If you do not use Intune, the Companion App can still be distributed using other endpoint management tools.
Best for
RMM or UEM platforms
Login-script based software rollout
Other managed Windows environments
Important setup note
Because the app is a per-user Windows install, it should be deployed in the signed-in user’s context, not system context.
How it works
Your IT team uses its existing deployment tool to:
run the installer silently
install the app into the user profile
optionally validate install using the executable path and version
Option 4: Manual user installation
This is the simplest rollout method, although it typically takes the most time since it requires each member of your team taking action. Users across both Mac and Windows may use this method depending on their device.
Best for
Small teams
Initial testing
Organizations without centralized device management
How it works
Each user:
Downloads the Companion App
Installs it on their work computer
Signs in once with their Skedda account email
Download links
Distribute the following install links to your users according to their device:
Mac (ARM64 + Intel):
Windows:
What happens after installation
Once the app is installed:
The user signs in once with their Skedda account email
The app runs quietly in the background
When the device is detected on the office network, Skedda can use that signal for occupancy tracking
If configured, Skedda can also support automatic check-ins for eligible bookings
Recommended rollout path
Use Intune for Windows if:
You manage a Windows fleet, want centralized deployment, and are comfortable deploying the Companion App as a per-user install in User context.
Use Mac MDM if:
You manage a Mac fleet and want a lower-touch rollout by centrally distributing the Companion App as a .pkg through your preferred MDM solution.
Use manual install if:
You want the simplest way to get started, are rolling out to a smaller group, or are testing with an initial set of users before a broader deployment.