Skip to main content

Deploying the desktop app

IT admins can install the desktop app on managed devices so people find Langdock in the Start menu or Applications folder without installing it themselves. Use it when you want to roll Langdock out to a whole department, keep versions under IT control, and handle every step that needs admin rights centrally, so people never need them.
Already deployed Langdock? To move your devices to the current release, follow Upgrade an existing deployment.

Windows

Which file do I need?

Every tool on this page uses the same deployment kit (.zip).
Don’t deploy the regular Langdock Setup.exe through an MDM. It installs for one user only, so when an MDM runs it as SYSTEM, your users won’t get the app. Use the deployment kit (.zip) on this page for managed Windows installs.
The deployment kit has everything each tool needs. Unzip it before you use it: Application.intunewin already contains Application.msix, Bootstrap.ps1, Deploy.cmd, and Deploy.ps1. Other tools use those four files from the extracted folder. Before you deploy, check these requirements:
  • Windows version: Requires 64-bit Windows 10 version 1809 or later. Automatic updates require Windows 10 version 2004 or later. On older versions, the app doesn’t update itself, so push each new release through your MDM. The meeting watermark camera needs Windows 11.
  • Sideloading: Langdock isn’t installed from the Microsoft Store, so Windows must allow apps from other sources. This is on by default since Windows 10 version 2004. On older versions, or if your organization turned it off, enable the AllowAllTrustedApps policy, called Allow all trusted apps to install in Group Policy.
  • AppLocker: only if you enforce Packaged app Rules. Add a publisher rule and select Langdock on a reference device. AppLocker fills in the publisher and package name.
Each tab installs Langdock machine-wide: it provisions the MSIX for the whole device, so every user gets it, including standard users. People who are signed in get it right away, and everyone else at their next sign-in. Pick the tab for your tool:
Download the deployment kit and unzip it. You upload three of its files to Intune: Application.intunewin as the Win32 app, Deploy.ps1 as the detection script, and Logo.png as the logo. While automatic updates stay on, the install adds a task that keeps Langdock up to date for most updates, so you upload a new kit to Intune only in rare cases. If you turn automatic updates off, you upload every new version to Intune.

Download kit (x64)

.zip for most Windows PCs

Download kit (ARM64)

.zip for Windows on ARM PCs
1

Add the app

In the Intune admin center, go to Apps > Windows > Add, select Windows app (Win32), and upload the kit’s Application.intunewin. For details, see Microsoft’s guide to Win32 apps in Intune.
2

Fill in the app information

Name is prefilled from the package. You can use these values for the rest:
3

Set the program

Set Install command to Deploy.cmd Install -RemovePersonalInstall, Uninstall command to Deploy.cmd Uninstall, and Install behavior to System. Return codes are 0 success, 3010 soft reboot, and 1 failed. -RemovePersonalInstall also removes copies people installed with Langdock Setup.exe. See Replace personal installs. To keep those copies, use Deploy.cmd Install.
4

Set the requirements

Set Check operating system architecture to Yes. Create a separate Win32 app from each kit, each with that kit’s Deploy.ps1 as its detection script:Never select x86, because there’s no 32-bit build. If you rely on automatic updates, choose Windows 10 2004 instead. Skip the ARM64 app if you have no ARM devices. Never deploy both apps to the same device.
5

Set the detection rule

After the install, Intune checks whether Langdock is on the device. If it doesn’t find it, it reports the install as failed and tries again. Built-in file and registry rules don’t fit here. The MSIX install folder and its registry entries contain the version, which changes with every update.Use Deploy.ps1 from the same kit as the detection script, so it matches the kit’s Application.intunewin. Under Detection rules, select Use a custom detection script and upload Deploy.ps1. Set Run script as 32-bit process on 64-bit clients and Enforce script signature check to No.The script reports Langdock as installed when the kit’s version or newer is provisioned, so Langdock’s own updates don’t make Intune reinstall it. Each time you upload Application.intunewin from a newer kit, upload that kit’s Deploy.ps1 with it. That’s what makes Intune run the new install on every device. See Upgrade an existing deployment.
Don’t use a detection script that only checks the package name, such as Get-AppxProvisionedPackage -Online | Where-Object DisplayName -eq 'com.langdock.desktop.msix'. It reports any older version as installed, so Intune never runs a newer package on devices that already have Langdock. Replace it with the kit’s Deploy.ps1.
6

Assign the app

Assign it as Required to a device group. Start with a pilot group.
Use this if you don’t want the Win32 app or a detection script, and you control versions yourself.Upload the x64 or ARM64 MSIX as a Line-of-business app. Assign it as Required to a device group and change Install Context to Device. Intune then provisions Langdock for every user.Turn off automatic updates first. Intune’s built-in detection expects the version you uploaded. Upload each new version to the app yourself. This package doesn’t register the meeting watermark camera. To switch to the Win32 app, see Upgrade an existing deployment.
Windows installs every MSIX to C:\Program Files\WindowsApps, and you can’t change that location.

Replace personal installs

People who installed Langdock themselves with Langdock Setup.exe keep that copy next to the MSIX, so they see two Langdock apps. You can remove the personal copy in two ways:
  • With the deployment kit: use Deploy.cmd Install -RemovePersonalInstall as the install command instead of Deploy.cmd Install. Once Langdock is provisioned, the kit removes the personal copy from every user profile on the device, including its shortcuts. It closes a running copy without warning, so tell people before you roll out. A copy that’s using the microphone, for example to record a meeting, stays, and the kit tries again the next time the install command runs.
  • In the app: when someone opens the MSIX while their personal copy is still installed, Langdock asks whether to remove it. When they click Remove, Langdock closes, uninstalls the other copy, and opens again by itself after about 30 seconds. They don’t need admin rights for that. Not Now asks again at the next launch. To stop the question, they check Don’t ask again and click Not Now.
Nothing moves over from the personal copy. The MSIX has its own sign-in and app data, so everyone signs in again. If the kit can’t clean up a profile, the install still succeeds, and that user gets the question in the app instead.

Network requirements

The desktop app loads the same Langdock web app as your browser, so allow the same domains you allow for Langdock in the browser. It also needs: The app uses the Windows system proxy settings. The kit’s update task runs as SYSTEM.

Shared devices and VDI

Each user gets their own copy of Langdock with their own sign-in and app data. Each user moves to a new version when they restart Langdock, so different users on one device can be on different versions for a while. On non-persistent VDI, provision Langdock in the base image (golden image) your virtual desktops start from. Turn off automatic updates in the base image too. For each new Langdock version, update the base image and roll it out. Per-user app data lives in %LOCALAPPDATA%\Packages\com.langdock.desktop.msix_b9czaxkzpqt8m. Keep that folder in your profile container, or people have to sign in again in every session. Langdock hasn’t been validated on Windows multi-session hosts or Remote Desktop Session Host yet.

Microphone access

The first time Langdock uses the microphone, Windows asks “Let Langdock access your microphone?” once per user. To approve microphone access up front, configure the LetAppsAccessMicrophone policy through the Intune Settings Catalog or the Group Policy Let Windows apps access the microphone. Add the Langdock package family name to the force allow list:

Meeting watermark camera

The camera needs Windows 11. A kit newer than desktop 1.0.15 skips it on Windows 10, and Deploy.cmd Install still succeeds. The 1.0.15 kit returns exit code 1. When the watermark is required and the camera can’t run, Langdock doesn’t transcribe meetings. In-person notes still record. There’s no setting that allows meeting transcription without the camera. The camera is a virtual camera that Windows Camera Frame Server loads. Frame Server runs as LocalService, so it can only load a machine-wide registration. That registration is COM classes under HKEY_LOCAL_MACHINE and the camera files in %ProgramFiles%\LangdockVirtualCamera. Only an administrator can write those locations. There is no separate driver or Windows service to deploy. Deploy.cmd Install registers the camera in the same SYSTEM step as the app. People on that device don’t see a UAC prompt. A plain MSIX or an Intune line-of-business app doesn’t register the camera. Langdock then asks people to contact their IT admin. With the personal Langdock Setup.exe, Windows asks for an admin once per device. A later release asks again only when that release changes the camera. Camera access is separate from the admin prompt. Windows doesn’t show desktop apps a camera prompt. If camera access is off, the watermark camera shows a black picture. If LetAppsAccessCamera is Force Deny, add Langdock’s package family name to the Force Allow list, the same name as under Microphone access. A microphone Force Deny policy does not black out the camera. The camera reads the physical camera on the device so the person’s video can carry the watermark. On Langdock cloud, a camera failure or a setup outcome sends Langdock a diagnostic code, how many times it happened, and whether a transcription is running. A camera failure also includes the Windows status code when Windows reported one. When another app is using that physical camera, that failure can also name up to five programs by their .exe file name. Reports leave out camera device names, meeting content, and video. Dedicated deployments don’t send these reports. The same events are written to main.log on the device, and camera failures also go to the Windows Application event log under the source LangdockWatermark.
Cameras registered on an older MSIX stop working after this update. Upgrade your deployment to the current kit once. Until then, Langdock tells people to contact their IT admin.

Inventory and uninstall

Langdock appears under Settings > Apps, not in Programs and Features or the classic Uninstall registry key. To check which devices have it, use the kit’s Deploy.ps1 or run these commands from an elevated PowerShell:
Deploy.cmd Uninstall as SYSTEM removes Langdock for all users, along with its update task. Remove-AppxPackage removes only the current user’s install. Windows deletes each user’s app data with the package. Policy keys you set stay in place.

macOS

Use this section for Jamf Pro, Kandji, Intune, or another macOS MDM. On managed Macs, people work as standard users without admin rights, so your MDM handles every step that needs them: it installs Langdock, keeps it updated, and approves its permissions. Langdock doesn’t ask people for an admin password on these Macs. When something needs IT, it tells them to contact their IT admin.
1

Deploy the app (required)

Both files work on Apple silicon and Intel Macs. Use the PKG on managed Macs. It installs Langdock.app to /Applications together with the Langdock updater, which installs new versions without admin rights. The PKG is signed with Langdock’s Developer ID Installer certificate and notarized by Apple, so you can upload it to your MDM as it is. See Updates on managed Macs.

macOS PKG

Installer package for your MDM

macOS DMG

Disk image
  • Jamf Pro: upload the PKG as a package and add it to a policy that runs once per computer.
  • Intune: add a macOS app (PKG) with the PKG and set Ignore app version to Yes.
  • Kandji: upload the PKG as a custom app that installs once.
After the install, the updater keeps Langdock current, so the version on the Mac moves past the PKG you uploaded. Don’t let your MDM reinstall the PKG because the version differs: the PKG always replaces /Applications/Langdock.app, even when that copy is newer. To check whether a Mac has the PKG install, run pkgutil --pkg-info com.langdock.desktop. The updater has its own receipt, com.langdock.desktop.updater.
Run this script as root from your MDM. It downloads the latest DMG, checks Apple’s signature and notarization, and copies Langdock.app to /Applications. This install doesn’t include the Langdock updater, so run the script on a schedule, for example daily, to keep Langdock current. When the installed version is already the latest, it does nothing. When Langdock is running, it exits with 1 so your MDM tries again later.
The PKG and the DMG script only install to /Applications. When people dragged Langdock from the DMG into the Applications folder in their home folder, that copy stays, so they see two Langdock apps. Run this script as root from your MDM before you install Langdock, for example as a pre-install script. It removes every Langdock.app in /Users/*/Applications with the bundle ID com.langdock.desktop and lists each copy it removed. People keep their sign-in, because their app data stays in place. When Langdock is running, it exits with 1 without removing anything, so your MDM tries again later.
2

Add the configuration profile (required)

The profile does two things:
  • It sets how the Langdock updater works. The sample keeps the default, updateMode set to automatic. To pin a version, see Updates on managed Macs.
  • It allows the updater as a managed login item. Without it, macOS shows people a “Background Items Added” notice, and anyone can turn the updater off under System Settings > General > Login Items & Extensions.
Deliver it as a device profile: upload the file as a custom profile in Jamf Pro, Intune, or Kandji. To build it in your MDM instead, set the com.langdock.desktop keys in Application & Custom Settings in Jamf Pro, a preference file in Intune, or a custom profile in Kandji, then add a Managed Login Items rule of type Label with the value com.langdock.desktop.updater. A user’s own defaults write is ignored.The watermark camera and the privacy permissions have their own profiles, under Privacy permissions and Watermark camera.

Privacy permissions

Standard users can’t turn on Accessibility. If your workspace uses dictation or Meetings, deploy this privacy (PPPC) profile so nobody has to ask IT: The entry is pinned to Langdock’s team ID, the same one as in the watermark camera profile.
1

Upload the privacy profile (optional)

Use this for dictation and Meetings. Upload the sample below as a configuration profile in Intune, Jamf, or Kandji, or build the same Privacy Preferences Policy Control payload there.
Langdock-Privacy.mobileconfig
With the profile in place, people still answer the macOS prompts for the microphone, the camera, and system audio the first time Langdock uses them. Those prompts don’t need admin rights.

Watermark camera

With Langdock Watermark on, people use the Langdock camera in their meetings. The camera needs macOS 14. It is a system extension, com.langdock.desktop.camera.extension. Approving that extension needs an administrator. On a managed Mac, deploy the profile below. On a machine-wide install without that profile, a standard user can’t approve the extension. Langdock asks them to contact their IT admin. A local admin can turn it on under System Settings > General > Login Items & Extensions > By Category > Camera Extensions. The camera reads the physical camera on the Mac so the person’s video can carry the watermark. On Langdock cloud, a camera failure or a setup outcome sends Langdock a diagnostic code, how many times it happened, and whether a transcription is running. A camera failure also includes the system status code when macOS reported one. Reports leave out camera names, meeting content, and video. Dedicated deployments don’t send these reports. The desktop app also writes them to main.log on the Mac.
1

Deploy the system extension profile (required)

Upload the sample as a configuration profile.
Langdock-Camera.mobileconfig
2

Deploy it before you turn on the watermark

Deploy the profile together with Langdock, or before it. If it arrives later, macOS turns on a camera that’s waiting for approval as soon as the profile installs, so nobody has to set it up again.The profile doesn’t install the camera itself. Langdock adds it when someone first sets up the watermark, and replaces it after updates that change it. With the profile in place, macOS approves both without asking for an admin. Keep the profile deployed: if you remove it, macOS can turn the camera off again.
With the profile in place, people see this:
  • No admin prompt when Langdock adds or replaces the camera extension.
  • One macOS prompt asking whether Langdock may use the camera. People answer it themselves, without admin rights. No MDM can approve camera access in advance, so this prompt stays.
  • In their meeting app, they choose the camera whose name ends in “Langdock Watermark”. Meeting apps that were open before Langdock may need a restart before they list it.
To check a Mac, run systemextensionsctl list. The line for com.langdock.desktop.camera.extension shows [activated enabled]. After an update that replaces the camera extension, macOS can keep it enabled without running it. Langdock then shows that the watermark camera stopped running. Restarting the Mac brings it back, and people can do that without admin rights. Turning the camera off and on again in System Settings also works, but asks for an admin.

Uninstall

Run the uninstall script as root from your MDM. It quits Langdock, removes /Applications/Langdock.app and the Langdock updater, and forgets both package receipts. People’s app data in their home folders stays.
Remove the configuration profiles after the uninstall. Removing the profiles alone doesn’t uninstall Langdock.

Automatic updates

The desktop app updates itself by default. On Windows, the deployment kit installs updates for the whole device. On Macs, the PKG’s updater does the same, see Updates on managed Macs. On both, you can pin a version by policy. To ship each version through your MDM instead, turn automatic updates off by policy. Pick one owner before you deploy, so the updater and your MDM don’t work against each other. See Manage desktop app updates.

Troubleshooting

The detection script doesn’t find Langdock. Upload the detection script from the Intune steps as a .ps1 file and set Run script as 32-bit process on 64-bit clients to No.
Sideloading or an app install policy blocks the package. Allow sideloading of trusted apps on the device and check AppLocker or WDAC.
Windows doesn’t install an older version over a newer one. Deploy the current version, or remove Langdock first if you need to roll back.
Windows can’t replace a package that’s running. Deploy.cmd Uninstall closes Langdock first. For updates you deploy yourself, ask people to quit Langdock and retry.
The device can’t build the certificate chain. Make sure the GlobalSign Code Signing Root R45 is in the machine’s trusted root store. Windows usually adds it through its automatic root updates.
The kit failed and wrote the reason to its error output. Common causes: the kit files come from different releases (“The MSIX does not match this deployment script”), or it didn’t run as SYSTEM or admin in 64-bit PowerShell. Run Deploy.cmd instead of calling Deploy.ps1 directly.The install also fails when the watermark camera can’t be registered (“Camera registration failed.”). Langdock is provisioned then, and the kit has still added its update task and, with -RemovePersonalInstall, removed personal installs. The update task tries to register the camera again each time it runs, at startup and once a day. To repair it sooner, fix the cause and run Deploy.cmd Install again.Kits through desktop 1.0.15 can’t register the camera on Windows 10, because it needs Windows 11. Deploy.cmd Install returns 1 there every time, so Intune shows the install as failed. Langdock is still installed and updates through the kit’s task, and each run of that task ends with “Update failed: Camera: Camera registration failed.” in update.log. A kit newer than desktop 1.0.15 skips the camera instead, and the install succeeds.
People who are signed in during the install get Langdock right away. To check who has it, run this from an elevated PowerShell:
If someone isn’t listed, ask them to sign out and back in.
Add the Packaged app Rules rule for Langdock. The kit scripts also fall under Script Rules. Check the AppLocker event logs Packaged app-Deployment, Packaged app-Execution, and MSI and Script for blocks.
If a Group Policy sets the PowerShell execution policy to AllSigned, Windows blocks the kit’s scripts, both during the install and in the update task. Use RemoteSigned for these devices instead. If needed, run Unblock-File on the extracted kit files before you deploy them.
Win32 apps can take up to about an hour to arrive. To speed it up, click Sync in Company Portal under Settings or restart the Microsoft Intune Management Extension service.
Check state.json in %ProgramFiles%\LangdockUpdater\com.langdock.desktop.msix_b9czaxkzpqt8m. update is idle when the last run worked, off when the policy turns updates off, and error when it failed. update.log in the same folder has the reason. updater-health.json next to it shows whether the task’s update logic works. If lastRunResult is unavailable or needsKitReinstall is true, deploy the current kit again.
Check the updater’s status file. state is idle when Langdock is current, staged when an update waits for Langdock to quit, off when the profile turns updates off, and error with the reason in detail, for example an invalid policy value, a blocked download, or updater_unavailable. updater-health.json next to it shows whether the update logic works. If needsPkgReinstall is true or detail is updater_unavailable, install the current PKG again.
To check right away instead of waiting for the hourly run, run sudo launchctl kickstart -k system/com.langdock.desktop.updater. The updater writes both files on its first run, right after the PKG install. If they’re still missing, the Mac doesn’t have the PKG install. Deploy the PKG.
  • Intune: C:\ProgramData\Microsoft\IntuneManagementExtension\Logs, mainly AppWorkload.log and IntuneManagementExtension.log.
  • Package installs: Event Viewer under Applications and Services Logs > Microsoft > Windows > AppXDeployment-Server > Microsoft-Windows-AppXDeploymentServer/Operational.
  • Kit updates: update.log in %ProgramFiles%\LangdockUpdater\com.langdock.desktop.msix_b9czaxkzpqt8m. Lines from the task’s own update logic start with Updater:.
  • Langdock app: main.log in %LOCALAPPDATA%\Packages\com.langdock.desktop.msix_b9czaxkzpqt8m\LocalCache\Roaming\com.langdock.desktop.msix\logs for each user.

FAQ

No. Langdock ships an MSIX, which Intune, Configuration Manager, Matrix42 Empirum, ACMP, baramundi, and Group Policy startup scripts can all deploy silently and machine-wide. MSIX apps have no MSI product code or Uninstall registry key, so use the kit’s Deploy.ps1 or Get-AppxProvisionedPackage instead of MSI-based detection.
No. Download the MSIX from this page. Devices don’t need Microsoft Store access.
Use the deployment kit and follow the steps in the Other tools tab under Windows. It has notes for each of these tools.
No. With a machine-wide deployment, standard users get Langdock at sign-in without admin rights. Only the provisioning step needs SYSTEM or admin rights. The kit registers the meeting watermark camera in the same step. Updates from the kit need no admin rights either. Without the kit, each user’s copy updates itself, so if your policies restrict app installs by standard users, turn off automatic updates and ship each version through your MDM.On Macs, the PKG, the Langdock updater, and the configuration profiles cover every step that needs admin rights. People never need them.
Yes. See Microphone access. Without the policy, each user answers the Windows prompt once.
Only if your MDM manages versions. If Langdock manages versions, you deploy once and Langdock stays up to date. Windows doesn’t install an older version over a newer one. To roll back, remove Langdock and deploy the older version.
Both can be installed on one device. They’re separate apps with their own sign-in. To remove the EXE install, deploy with Deploy.cmd Install -RemovePersonalInstall or let people remove it when the MSIX asks. See Replace personal installs.
Nothing to clean up. It’s the same app, so people keep their sign-in and app data. If their copy is older than the version you deploy, Windows updates it at their next sign-in. If it’s newer, they keep their version. From then on, Langdock is provisioned for every user of the device, and your detection counts it as installed.
Not yet. The MSIX on this page connects to Langdock cloud at app.langdock.com. Desktop apps for dedicated deployments aren’t available yet.