Installing using Intune on Win
Last updated
Last updated
Use Intune to mass-deploy to all corporate devices. There are two primary steps, and one optional:
IntuneWin File Prep: A Microsoft binary that prepares the zip for deployment
Intune Deployment: The series of steps to deploy the installer
Autopilot Provisioning (Optional): Automated installation of applications when a new laptop is Entra joined
If missing, the installer automatically installs the Visual C++ redistributable (dependency). This causes a VC++ download prior to the dope.endpoint installation. Very rarely, this can cause install failures during managed deployments (bad network etc). To avoid, stage an Intune install of VC++ first
Intune requires a Win32 "preparation" process before uploading to the Intune console. You'll perform this step first.
Microsoft docs are located here.
Download IntuneWinAppUtil
, and use it to prepare the .intunewin
package with this command modified for version:
The application deployment process is standard and similar to any other application
Microsoft docs are located here.
Here are a few hints for setting it up:
Install command should be dope_security_<build number>.exe -silent
Uninstall command: dope_security_<build number>.exe -silent -uninstall AT_PASSWORD=<password>
Detection rule: C:\Program Files\
Folder: dope.security
and use the File or Folder Exists
dropdown
Assignment: Required
When a new device is entra joined for the first time, it will run through the checklist of apps to install prior to allowing a user access to the system. Sometimes, the Intune configured application can automatically be a part of the Blocking Apps inside of Autopilot which will naturally cause a conflict.
Ensure that you have removed dope.security from "blocking apps" in Autopilot, and instead, keep it as a required app. Blocked apps will prevent the enrollment process from successfully completing.
If you have this setup correctly, there will not be any issue during initial Entra-device joining.