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.Windows
Which file do I need?
Every tool on this page uses the same deployment kit (.zip).
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
AllowAllTrustedAppspolicy, 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.
- Intune
- Configuration Manager (SCCM)
- Group Policy
- Other tools
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 PCsDownload kit (ARM64)
.zip for Windows on ARM PCsAdd the app
Application.intunewin. For details, see Microsoft’s guide to Win32 apps in Intune.Fill in the app information
Set the program
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.Set the requirements
Deploy.ps1 as its detection script:Set the detection rule
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.Assign the app
Alternative: deploy the plain MSIX
Alternative: deploy the plain MSIX
C:\Program Files\WindowsApps, and you can’t change that location.
Replace personal installs
People who installed Langdock themselves withLangdock 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 -RemovePersonalInstallas the install command instead ofDeploy.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.
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: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 theLetAppsAccessMicrophone 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, andDeploy.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.
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’sDeploy.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.Deploy the app (required)
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
macOS DMG
- 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.
/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.Want to install the DMG yourself? Use this script
Want to install the DMG yourself? Use this script
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.Copies of Langdock outside /Applications? Remove them with this script
Copies of Langdock outside /Applications? Remove them with this script
/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.Add the configuration profile (required)
- It sets how the Langdock updater works. The sample keeps the default,
updateModeset toautomatic. 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.
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.Sample configuration profile (Langdock.mobileconfig)
Sample configuration profile (Langdock.mobileconfig)
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:Upload the privacy profile (optional)
Sample profile
Sample profile
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.
Deploy the system extension profile (required)
Sample profile
Sample profile
Deploy it before you turn on the watermark
- 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.
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.
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
0x87D1041C: Intune reports the app as not detected after installation
0x87D1041C: Intune reports the app as not detected after installation
.ps1 file and set Run script as 32-bit process on 64-bit clients to No.0x80073CFF or 0x80073D01: Windows blocks the install by policy
0x80073CFF or 0x80073D01: Windows blocks the install by policy
0x80073D06 or 0x80073CF3: a newer version is already installed
0x80073D06 or 0x80073CF3: a newer version is already installed
0x80073D02: the package is in use
0x80073D02: the package is in use
Deploy.cmd Uninstall closes Langdock first. For updates you deploy yourself, ask people to quit Langdock and retry.0x800B0109 or 0x800B010A: the signature isn't trusted
0x800B0109 or 0x800B010A: the signature isn't trusted
Exit code 1 from Deploy.cmd
Exit code 1 from Deploy.cmd
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.Intune shows Installed, but people don't see Langdock
Intune shows Installed, but people don't see Langdock
AppLocker blocks Langdock or the scripts
AppLocker blocks Langdock or the scripts
Packaged app-Deployment, Packaged app-Execution, and MSI and Script for blocks.The kit doesn't run: PowerShell scripts are blocked
The kit doesn't run: PowerShell scripts are blocked
Unblock-File on the extracted kit files before you deploy them.Intune doesn't pick up the app
Intune doesn't pick up the app
Langdock doesn't update with the kit
Langdock doesn't update with the kit
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.Langdock doesn't update on a Mac
Langdock doesn't update on a Mac
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.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.Where are the logs?
Where are the logs?
- Intune:
C:\ProgramData\Microsoft\IntuneManagementExtension\Logs, mainlyAppWorkload.logandIntuneManagementExtension.log. - Package installs: Event Viewer under Applications and Services Logs > Microsoft > Windows > AppXDeployment-Server > Microsoft-Windows-AppXDeploymentServer/Operational.
- Kit updates:
update.login%ProgramFiles%\LangdockUpdater\com.langdock.desktop.msix_b9czaxkzpqt8m. Lines from the task’s own update logic start withUpdater:. - Langdock app:
main.login%LOCALAPPDATA%\Packages\com.langdock.desktop.msix_b9czaxkzpqt8m\LocalCache\Roaming\com.langdock.desktop.msix\logsfor each user.
FAQ
Is there an MSI installer?
Is there an MSI installer?
Deploy.ps1 or Get-AppxProvisionedPackage instead of MSI-based detection.Is Langdock in the Microsoft Store?
Is Langdock in the Microsoft Store?
How do I deploy with ACMP, baramundi, or Matrix42 Empirum?
How do I deploy with ACMP, baramundi, or Matrix42 Empirum?
Do people need admin rights?
Do people need admin rights?
Can I pre-approve the microphone prompt?
Can I pre-approve the microphone prompt?
Do I have to package every update?
Do I have to package every update?
What happens to the personal Langdock Setup.exe install?
What happens to the personal Langdock Setup.exe install?
Deploy.cmd Install -RemovePersonalInstall or let people remove it when the MSIX asks. See Replace personal installs.Some people already installed the MSIX themselves. What happens when I deploy it?
Some people already installed the MSIX themselves. What happens when I deploy it?
Does this work for dedicated deployments?
Does this work for dedicated deployments?
app.langdock.com. Desktop apps for dedicated deployments aren’t available yet.