Technical Bulletin – DIB Check Status Diagnostic Module for Add2Exchange
| Audience |
Add2Exchange administrators, IT/security teams, Microsoft 365 / Exchange administrators, and support engineers |
| Scenario |
Understanding what the DIB Check Status diagnostic does, what local infrastructure it reads, what prerequisites it may install, and how to prepare an Internet-restricted Add2Exchange appliance |
| Use Case |
Customer review, change-control approval, offline prerequisite staging, and technical support diagnostics |
| Current Reference Build |
DIB_Check_Status V6.59 |
| Last Updated |
8/20/2026 |
Executive Summary. DIB Check Status is a local Add2Exchange diagnostic and health-analysis tool. It runs in Windows PowerShell on the Add2Exchange appliance, reads local Add2Exchange and Windows information, correlates SQL history with Add2Exchange Event Log activity, and generates a self-contained HTML dashboard for technical review. The report is designed to show what is running, what has succeeded, what is late or failing, what changed, and what the administrator should check next.
The diagnostic itself does not create, edit, delete, or reconfigure Add2Exchange relationships, mailboxes, distribution lists, licenses, or synchronization settings. Its normal changes are limited to creating local report/helper files and, when preflight installation is enabled, installing or updating PowerShell prerequisite components. The report also exposes links to separate Add2Exchange maintenance and support scripts; those scripts run only when an operator deliberately clicks and launches them.
What the Diagnostic Does
| Area |
What DIB Check Status Does |
| System health |
Checks Add2Exchange service/agent state, pending reboot, uptime, last boot, recent restart initiator, Outlook state, Auto Logon, UAC, disk/CPU/network basics, Windows update history, and user-session activity. |
| Add2Exchange Event Logs |
Reads dedicated Add2Exchange logs and analyzes success audits, failures, errors, function timing, relationship timing, Automatic Permissions activity, RelMan / Template Validation activity, clone creation/failure activity, and error recurrence. |
| Local SQL history |
Reads the local Add2Exchange SQL database when available to obtain relationship inventory, relationship timing history, module/process history, templates, clones, distribution-list attachments, alerted relationships, and richer module-cycle history. |
| Registry/configuration |
Reads Add2Exchange registry settings, version/license information, service-account information, configuration paths, Outlook-related status, and other settings needed to explain the appliance configuration. |
| Trend analysis |
Calculates slow relationships, overdue relationships, expected next-run timing, function cadence, module success periods, last full cycle, queue/backlog estimates, error trends, and health status. |
| Support guidance |
Builds a Recommended Action Plan and links Add2Exchange Event IDs directly to the centralized Add2Exchange AI KnowledgeBase entry for that Event ID. |
| Local tools |
Creates helper launchers for common support scripts such as Level 2 Update, Permissions, Outlook Setup/Tools, Light Report, and Full Report with SQL. |
How the Analysis Is Built
DIB Check Status intentionally uses more than one source because Add2Exchange SQL history and Windows Event Log data answer different questions.
| Information Needed |
Primary Source |
How It Is Used |
| Relationship and module history |
Local Add2Exchange SQL database |
Provides the durable timing/history backbone used for relationship inventory, historical durations, module success periods, templates, clones, and relationship status. |
| Failures, errors and warnings |
Add2Exchange Event Logs |
Provides the failure/error truth, error recurrence, most recent log body, recovery context, and direct Event ID KnowledgeBase links. |
| Generic synchronization identification |
SQL + Event Log correlation |
SQL process Type 2 is a generic synchronization record. The diagnostic uses nearby success audits and item/relationship counts to identify whether the cycle was Calendar, Contacts, Tasks, Posts, or Notes. |
| RelMan / Template Validation |
SQL and Event Log success audits |
Template Validation / RelMan is tracked as its own functional area and is also used for clone/template diagnostics. |
| GAL synchronization |
SQL with Event Log support |
GAL has its own process type and is tracked separately from generic Type 2 synchronization. |
RelationshipsProcess Process-Type Map Used by the Diagnostic
| TYPE |
Meaning |
| 0 |
Report |
| 1 |
Reset |
| 2 |
Synchronization – module is identified by Event Log correlation and relationship/item counts |
| 3 |
Synchronization GAL |
| 4 |
Template Validation / RelMan |
| 5 |
Analysis |
| 6 |
Confirmation |
Local Infrastructure and Data Sources
| Component / Source |
Purpose |
Important Note |
| Windows PowerShell |
Runs the diagnostic and generates the report. |
Current code is designed for Windows PowerShell 5.1 compatibility. |
| Add2Exchange dedicated Event Logs |
Success, error, failure, relationship and function activity. |
The diagnostic prefers dedicated Add2Exchange logs rather than unrelated Application log noise. |
| SQL Server / A2ESQLSERVER |
Add2Exchange relationship and process history. |
The SQL Server service must be running and the logged-in Windows context must be able to read the local Add2Exchange database for SQL-backed history to populate. |
| Add2Exchange registry |
Version, service account, licensing, paths and configuration snapshot. |
Reads the OpenDoor Software® / Add2Exchange registry areas and uses compatibility fallbacks when needed. |
| Windows System/Security data |
Boot/restart history, user session pulse, service/process state and machine context. |
Used for troubleshooting correlation; the diagnostic does not alter the Windows security log. |
| Local file system |
Creates report and helper files and checks Add2Exchange installation paths. |
Preferred output folder is C:\Program Files (x86)\DidItBetterSoftware\Support. If that folder cannot be used, the script falls back to a Windows temporary folder or the current working folder. |
SQL Server Availability
SQL is important because the richest Add2Exchange relationship and module history comes from the local database. Beginning with the current diagnostic line, the report explicitly detects when the local SQL Server instance is unavailable or stopped.
| Condition |
Diagnostic Behavior |
| SQL Server running and database readable |
SQL-backed relationship history, inventory, module history, template/DL information, alerted relationships and timing data are included. |
| SQL Server stopped |
The report identifies the SQL service problem, places it in Recommended Actions, and warns on the Graphs and Functions pages that SQL-backed history may be incomplete. |
| SQL database cannot be opened under the current Windows user |
The report continues using local Event Log information where possible and reports that SQL history is unavailable. |
| Automatic service changes |
DIB Check Status does not automatically start or restart SQL Server. It recommends starting the service and rerunning the diagnostic. |
PowerShell Preflight and Prerequisites
The diagnostic includes a preflight routine with three modes: CheckOnly, InstallMissing, and InstallAndUpdate. The default is InstallMissing. Administrators can also use -SkipPreflight to suppress installation actions or -DoNotOpenReport to prevent the finished HTML report from opening automatically.
When installation actions are allowed, the diagnostic may set the standard PSGallery repository to Trusted and may install missing components using Install-PackageProvider and Install-Module. When running elevated, it prefers an AllUsers installation scope; otherwise it falls back to CurrentUser.
| Component |
Minimum Version in V6.59 |
Role |
Current Importance |
| NuGet Package Provider |
2.8.5.201 |
Allows gallery-backed PowerShell package/module installation. |
Core preflight component when online installation is being used. |
| PackageManagement |
1.4.8.1 |
PowerShell package-management framework used by preflight/install logic. |
Core preflight component. |
| PowerShellGet |
2.2.5 |
Provides Install-Module / Save-Module and PowerShell Gallery integration. |
Core preflight component. |
| PSWriteHTML |
0.0.170 |
HTML reporting module retained by the preflight manifest. |
Optional/reserved in the current build. V6.59 generates its primary HTML dashboard with its own self-contained renderer. |
| ImportExcel |
7.8.6 |
Excel export capability retained by the preflight manifest. |
Optional/reserved in the current build. V6.59 is configured for HTML-only output by default. |
Internet Access and Manual / Offline Prerequisite Staging
The local diagnostic analysis does not require Internet access when the required PowerShell environment is already present and preflight installation is disabled or satisfied. Internet access is used primarily for PowerShell prerequisite installation and for links in the finished report that open DidItBetter.com support content.
The script specifies the standard PSGallery repository. The standard PowerShell Gallery feed is:
https://www.powershellgallery.com/api/v2
For disconnected appliances, the preferred practice is to download or stage the components on an Internet-connected administrative workstation, transfer them through the customer's approved offline process, then run DIB Check Status in CheckOnly or with -SkipPreflight.
Suggested Offline Preparation
- On an Internet-connected administrative workstation, obtain the required module versions from the official PowerShell Gallery package pages above or stage them with PowerShell
Save-Module.
- Bootstrap/install the NuGet provider on the connected workstation if required, then copy the provider through the customer's approved offline transfer process. Microsoft identifies the provider locations as the PackageManagement ProviderAssemblies folders under Program Files or the current user's LocalAppData.
- Copy the PowerShell module folders to an appropriate Windows PowerShell module path on the isolated Add2Exchange appliance.
- Confirm the SQL Server / A2ESQLSERVER service is running before the diagnostic is executed.
- Run DIB Check Status with
-PreflightMode CheckOnly or -SkipPreflight when the customer does not want the diagnostic to attempt Internet-based prerequisite installation.
Important: PowerShell Gallery's browser-based Manual Download retrieves a raw .nupkg package and does not automatically unpack dependencies. For controlled offline deployment, staging with Save-Module on a connected machine is often the simplest way to collect a ready-to-copy module folder.
What the Diagnostic Changes – and What It Does Not Change
| Behavior |
Current V6.59 Behavior |
| Read Add2Exchange configuration |
Yes. Reads local registry, logs, SQL data, processes, services and supporting Windows state. |
| Create local report files |
Yes. Creates the HTML report and local helper launchers in the Support folder or fallback output location. |
| Install PowerShell prerequisites |
Possible. Default preflight mode is InstallMissing. Use CheckOnly or -SkipPreflight when installation actions are not desired. |
| Trust PSGallery |
Possible. When installation actions are enabled, the preflight may set PSGallery InstallationPolicy to Trusted. |
| Modify Add2Exchange relationships/configuration |
No. Report generation does not create, change, disable or delete Add2Exchange relationships. |
| Modify Exchange / Microsoft 365 objects |
No. Report generation does not change users, mailboxes, groups or tenant settings. |
| Start/restart SQL Server |
No. It detects and reports SQL service problems and recommends starting SQL and rerunning the report. |
| Automatically send data off the appliance |
No. The report is written locally. External support/KnowledgeBase pages are opened only when an operator follows a link. |
| Run repair/update scripts automatically |
No. The report exposes helper links, but the operator must deliberately launch a separate tool. |
Dashboard Pages, Reports and Exposed Features
1. Summary
| Feature |
Information Shown |
| Health Status |
Overall Healthy / Warning / Critical assessment based on service state, reboot status, errors, overdue functions/relationships, duration spikes and preflight readiness. |
| Pending Reboot |
Whether Windows is waiting for a reboot. |
| A2E Error Trend |
Error counts in the last 24 hours and 7 days. |
| Top Overdue Relationship |
Most overdue relationship, due time and relationship identity. |
| Queue / Backlog |
Current queue position, remaining items, estimated backlog and next due timing when available. |
| Last Full Cycle |
Latest successful module-cycle timing, with SQL/Event Log source labels where applicable. |
| Automatic Permissions |
Recent Event ID 10000 success / 10001 failure activity and next expected timing. |
| License Status |
License state and the nearest known Add2Exchange license expiration date. |
| Raw Analysis Summary |
Client/company, Add2Exchange version, service/agent state, boot/session information, SQL status, preflight status, license, registry source, log source and report path. |
| Top Slow Relationships |
Highest observed relationship durations with compact visual bars. |
| Top Overdue Relationships |
Relationships whose expected next sync has been exceeded. |
2. Recommended Action Plan
Builds an ordered set of troubleshooting recommendations based on the current machine. Examples include Add2Exchange service state, SQL Server state, pending reboot, error recurrence, overdue relationships, update/maintenance guidance, offboarding guidance, and the most recent Add2Exchange Event ID KnowledgeBase reference.
The Action Plan also exposes the following local support tools when those Add2Exchange files are present:
| Tool |
Target File |
Purpose |
| Level 2 System Update |
...\Add2Exchange\Setup\Level_2.ps1 |
Launches the standard Level 2 update workflow. |
| Run Permissions |
...\Add2Exchange\Setup\PermissionsOnPremOrO365Combined.ps1 |
Launches the Add2Exchange permissions workflow. |
| Outlook Setup |
...\Add2Exchange\Setup\Outlook_Profile_Set.ps1 |
Launches Outlook profile setup. |
| Other Outlook Tools |
...\Add2Exchange\Setup\Outlook_Tools_Menu.ps1 |
Launches the Outlook tools menu. |
| Light Reporting Package |
...\Add2Exchange\Setup\LightReport.ps1 |
Creates the lighter support reporting package. |
| Full Report Package including SQL |
...\Add2Exchange\Setup\FullReport.ps1 |
Creates the full support package including SQL data. |
| Permissions Command Reference |
...\Add2Exchange\Setup\A2E_Permissions_Commands.rtf |
Opens the local permissions command reference. |
For each PowerShell tool, DIB Check Status generates an HTA launcher and a CMD fallback. The launcher attempts to start powershell.exe, copies the exact PowerShell command to the clipboard, and tells the operator to paste the command manually if PowerShell does not open. If the target file is missing, it reports the missing path and opens the folder as a fallback.
3. Graphs
- RelMan / Template Validation success period for the last 7 days.
- GAL success period for the last 7 days.
- Calendars success period for the last 7 days.
- Contacts success period for the last 7 days.
- Tasks success period for the last 7 days.
- Posts success period for the last 7 days.
- Notes success period for the last 7 days.
- Merged module-success table showing whether each row came from SQL or Event Log fallback.
- Relationship success/failure activity for supported synchronization modules.
- Error markers/overlays where report data allows the error to be associated with a module timeline.
- Horizontal scrolling and per-graph Zoom In, Zoom Out, Reset and Fit Width controls for dense graphs.
4. Relationships
- SQL relationship landscape by module, including active, template, single, clone, alerted and distribution-list counts.
- Failed RelMan / Template Validation member clone creates in the last 7 days.
- New member clones created in the last 7 days.
- Templates and Distribution List attachments from SQL.
- Grouped active relationship inventory from SQL, with templates first, then active singles and clones.
- Per-relationship last duration, average duration, last-seen age and relationship identity.
- Top slow and overdue relationship calculations used by the Summary and Action Plan.
5. Functions
- Function success audits using actual Add2Exchange Event IDs.
- Tracked functional areas include RelMan / Template Validation, GAL, Calendar, Contacts, Tasks, Posts and Notes when present.
- Last duration, average duration, duration ratio, average interval, time since last success, expected due time and late status.
- Function Watchlist for overdue functions or runs whose duration is materially above normal.
- Automatic Permissions success/failure history.
- SQL availability warning when SQL-backed function/module history cannot be read.
6. Errors
- Groups recurring Add2Exchange errors into an Error Trend.
- Shows occurrence count, Event ID, last-seen time, relationship identity when available, and the latest log body.
- Builds a direct KnowledgeBase link in the format
https://support.diditbetter.com/ai-add2exchange-knowledgebase.aspx#id-<EventID>.
- Shows active SQL relationships where ALERT is true and KILL is false.
- Uses Event Log data as the primary source for errors, failures and warnings.
7. Registry
Displays a read-only snapshot of Add2Exchange registry settings used by the diagnostic, including the value name, current value and registry key string.
8. Preflight
Displays the installation manifest with component name, minimum version, installed version, status, action taken and notes. If a prerequisite cannot be installed or needs attention, the diagnostic can create a local _NextSteps.txt file with the suggested PowerShell command.
Current Output Files
| Output |
Current V6.59 Behavior |
| HTML Dashboard |
Primary report. File name format: Dib_Check_Status_yyyy-MM-dd_HH-mm-ss.html. |
| Report Location |
Preferred location: C:\Program Files (x86)\DidItBetterSoftware\Support. |
| Automatic Open |
The HTML report opens in the default browser unless -DoNotOpenReport is specified. |
| Preflight Next Steps |
Created as a UTF-8 text file when preflight finds unresolved prerequisites. |
| Helper Launchers |
Local HTA and CMD files are created for the exposed Add2Exchange support scripts. |
| TXT / CSV |
The current V6.59 release is configured for HTML-only output by default. The code retains CSV/TXT export paths for alternate/future use, but they are not emitted in the normal V6.59 run. |
Security and Data-Handling Considerations
- The report is created locally on the Add2Exchange appliance.
- The diagnostic does not automatically upload the report or send it to DidItBetter.com.
- The report can contain customer-specific technical information such as computer name, service account, email addresses, relationship names, registry settings, error messages, SQL relationship metadata, distribution-list names and configuration paths. Treat the report as support-sensitive customer data.
- Internet access may be used by PowerShell preflight installation and by support hyperlinks, not by the core local SQL/Event Log analysis itself.
- If the customer does not permit automatic prerequisite installation, run with
-PreflightMode CheckOnly or -SkipPreflight.
Related DidItBetter.com Resources
Bottom Line
DIB Check Status is a local, read-oriented Add2Exchange troubleshooting and trend-analysis utility. It combines local SQL history, Add2Exchange Event Logs, registry/configuration information and Windows machine state into one HTML dashboard. The SQL database provides the best historical relationship/module picture; Event Logs provide the primary error/failure picture and help identify generic synchronization cycles. The diagnostic can prepare its own PowerShell prerequisite environment when Internet access is permitted, or the required components can be staged in advance for an Internet-restricted appliance.
For customers with restricted Internet access, pre-stage the PowerShell components from the official Microsoft / PowerShell Gallery links above, confirm the Add2Exchange SQL Server service is running, and execute the diagnostic in CheckOnly or SkipPreflight mode to avoid automatic prerequisite installation attempts.