DPLens installs from a single Windows Installer package, dplens.msi. How you run it depends on how many machines you are deploying to and whether the configuration is decided centrally.
Choose your method
| You are… | Use |
|---|---|
| Trying DPLens on one machine | Installing on one machine |
| Rolling out to a handful of machines with a script | Silent installation |
| Deploying to a fleet — configuration, secrets and licences from one machine you configured | The deployment MSI, by Group Policy, Intune, Configuration Manager, an RMM or a cloud image, or a push from your workstation |
| Deploying through Group Policy with a transform, no secrets involved | The transform bundle |
| Baking DPLens into a golden image or VDI template | Golden images and VDI clones |
| Not sure | The deployment wizard |
All of them install the same package. The difference is where the configuration, the licence and any secrets come from.
Before you start
- Check Requirements.
- Verify your download — confirm the checksum and the signature before you run anything.
- Have your licence key to hand. You can install without one and apply it afterwards, but the agent will not deliver any events until it is licensed. See Licensing.
What an installation gives you
However you install it, you end up with:
dplens.exeinC:\Program Files\DPLens.- A Windows service named dplens, set to start automatically, running as its own virtual service account.
- A configuration file at
C:\ProgramData\DPLens\config\agent.yaml. - A working folder at
C:\ProgramData\DPLens\state, with permissions set so that only administrators and the service itself can read it. - The console, on
https://localhost:8443, unless you turned it off.
A plain installation with no options is deliberately inert: it configures a set of common Windows Event Log channels, a placeholder destination pointing at the local machine, and a pipeline that is switched off. Nothing is collected and nothing is sent anywhere until you choose a real destination and enable it. That is what Your first hour walks you through.
After installing
- Your first hour — sign in, licence, first source and destination.
- Upgrading and uninstalling.