Installation and first security baseline

Before installation

1. Take a full backup of the DNN files and database.
2. Record the DNN version and confirm that critical modules support the planned environment.
3. Verify the package source and checksum supplied with the release.
4. Confirm there is enough free disk space for installation, quarantine evidence, logs, and FIM recovery copies.
5. Schedule a maintenance window for production systems.

Install the package

Install the production package through Settings > Extensions while signed in as Host. Do not manually copy package assemblies into bin. After DNN completes the extension installation, recycle the application only if requested and verify that the site, Host login, and module page load without an exception.

The Trial edition must display a visible TRIAL badge and its remaining period. When the trial expires, the UI must clearly identify which AI or semantic capabilities are disabled and which rule-based, baseline, and monitoring functions remain active.

First-run checklist

1. Open Dashboard and confirm the version, edition, license state, and protection-mode cards.
2. Open Settings and review WAF mode, Advisory Shield mode, notification recipients, scan scope, schedules, and retention settings.
3. Run Security Risk Analysis and review every Failure and Warning before relying on a green dashboard.
4. Run a full scan. Investigate Critical, Review, and Scan Error results; intentionally skipped metadata is not an error.
5. Confirm Realtime Monitor is running and that DNN Defender handlers reject anonymous probes.
6. Create the FIM baseline only after the site and scan results have been verified.

Baseline approval rule

Never refresh a baseline only to remove alerts. A baseline is an explicit administrator statement that the current protected files are trusted. If a suspicious file becomes part of the baseline, future integrity scans will correctly report it as unchanged.

Use Maintenance Mode before installing or upgrading DNN, a module, a skin, or making an approved web.config change. Test the site, review the changes, then use Refresh Baseline & Resume. If the deployment is not accepted, end maintenance without changing the baseline and investigate the resulting differences.