LogoLogo
  • Introducing dope.swg
    • Changing the Rules...
    • Quick Start Guide
      • Create a dope.swg Account
      • Get Started with the dope.endpoint
      • Import User and Group Data
      • Create a dope.swg Web Policy
    • Mitre ATT&CK and Nist CSF
  • dope.console
    • Analytics
      • Overview dashboard
      • Policy View
      • Productivity
      • Shadow IT
      • Detail View
    • dope.swg Policy
      • Editing the Base Policy
      • Adding Policy Exceptions
      • Assigning a Block Page
      • Creating Custom Categories
      • URL Bypass List
      • Application Bypass List
      • Default Bypass List
      • Cloud Application Control (CAC)
        • Microsoft O365
        • Google
        • Box
        • Salesforce
        • Dropbox
        • Slack
        • WebEx
      • Custom Policy
      • Policy Assignment
      • Policy Inheritance and Customization
    • CASB Neural
      • Microsoft 365 - Authentication
      • Google - Authentication
      • CASB DLP
        • DLP Files Table
    • Endpoint Manager View
      • Searching the View
      • Filtering and Sorting the Endpoint View
      • Endpoint Count
      • Running Diagnostics
      • Disable Endpoint
    • Settings
      • General
      • Block Pages
      • Endpoints
      • Users
        • Importing from Google
        • Why not SAML & SCIM?
      • Audit Log
      • SIEM Integration
        • Category & Verdict Mappings
      • API Client Credentials
      • Billing Details
    • Notifications
      • SSL Errors
  • dope.endpoint
    • Trusted Process Names
    • Generate Diagnostics
    • Disable Endpoint
    • Installing using MDM on Mac
      • Using JAMF
      • Using Kandji
      • Using Intune
    • Installing using Intune on Win
    • Mac Installer
      • Installation Process - Silent
      • Uninstall
      • Endpoint Authentication
    • Windows Installer
      • Installation Process - Silent
      • Uninstall
      • Endpoint Authentication
    • dope.endpoint UI
      • Windows UI
      • macOS UI
    • Automatic Updates
  • Release Notes
  • DOPE.APIs
    • Public API Specification
Powered by GitBook
On this page
  1. dope.endpoint

Windows Installer

Supports Windows 10 & 11

PreviousEndpoint AuthenticationNextInstallation Process - Silent

Last updated 4 months ago

Downloading the Windows Installation Package

To download the Windows installation package, log in to the Dope Console. Then, click the download button in the top right corner.

The ZIP file will be called dope_security_windows_<build number>.zip.

Extract the ZIP file, it will contain the following three files:

  • <build number>.exe — The dope.endpoint installer.

  • dope.security.crt — The dope.security Root CA, required for SSL inspection.

  • agent_parameters.json — Tenant specific data required for the installation process.

All three files must be in the same directory or the installation will FAIL

To install the dope.endpoint, double click on the EXE file. This will launch the following Installer UI.

Before installation can start the dope.security End User License Agreement (EULA) needs to be accepted. Once this has been accepted, select the install option to start the installation process.

MS Windows will also prompt to accept installing the dope.endpoint on the Windows machine.

On selection of Yes the installation process will continue. Once it is complete the following dialog will be displayed.

Once the installation is complete a dope.security icon can be seen in the Windows systems tray icon.

Where endpoint authentication has been enabled (See Users), then the user will be prompted to authenticate with their M365 or Google credentials.

If missing, the installer automatically installs the (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 install of VC++ first

Visual C++ redistributable