Offline & Enterprise Deployment

For environments without internet access or for automated enterprise deployments (GPO, SCCM, Intune).

Prerequisites to pre-download

Download these on a machine with internet access and transfer to target machines:

Installation order

1. Install the Amazon Redshift ODBC Driver first (silent: msiexec /i AmazonRedshiftODBC64.msi /quiet)
2. Install the BEEM ODBC Driver (msiexec /i BEEM-Setup.msi /quiet)

Silent install

msiexec /i BEEM-Setup.msi /quiet /norestart /l*v install.log

The /quiet flag skips the UI wizard entirely. All components are installed to C:\Program Files\BEEM\ODBC\.

The Power BI connector and silent installs

The installer is built for single-user workstations: it copies the Power BI
connector into the Custom Connectors folder of the account running the
installer, and only that account.

That matters for deployment tools. SCCM, Intune and scheduled tasks typically run
msiexec as SYSTEM or as a service account, so the connector lands in that
account's profile — not in the profile of whoever actually uses the machine. The
ODBC driver itself installs machine-wide and is unaffected; it is only the Power
BI connector that is per-user.

If you deploy silently and your users need the Power BI connector, run the script
the installer ships for exactly this, once per user:

powershell -ExecutionPolicy Bypass -File "C:\Program Files\BEEM\ODBC\install-connector.ps1"

Run it in the user's own context — a logon script or a per-user configuration
item works well. It picks the right folder name (Power BI Desktop or
Microsoft Power BI Desktop, depending on which build of Power BI is installed)
and follows Documents to wherever it actually lives, which matters when OneDrive
has redirected it. Prefer it over a plain copy for that reason.

It appends what it did to %ProgramData%\BEEM\connector-install.log, so a failed
run leaves something to read.

Excel and other ODBC clients need none of this — they use the DSN and the driver,
both of which are machine-wide.

Pre-staging configuration

Without internet, the post-install setup page (setup.beemdata.com/odbc-config)
won't load. Pre-stage the DSN instead.

The driver reads its settings from the ODBC registry, so create a System DSN with
a .reg file applied per machine:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\BEEM]
"Driver"="C:\\Program Files\\BEEM\\ODBC\\beem_odbc.dll"
"Server"="your-cluster.abc123.ca-central-1.redshift.amazonaws.com"
"Port"="5439"
"Database"="analytics"
"Backend_Driver"="Amazon Redshift ODBC Driver (x64)"
"SSH_Host"="bastion.yourcompany.com"
"SSH_Port"="22"
"SSH_User"="deploy"
"SSH_Auth"="key"
"SSH_Key_File"="C:\\ProgramData\\BEEM\\id_ed25519"
"SSH_Host_Key_FP"="SHA256:..."

[HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\ODBC Data Sources]
"BEEM"="BEEM ODBC Driver"

Both keys are required — the second is what makes the DSN appear to
applications.

Use the value names exactly as shown; they match the connection parameters in
Connection Reference. SSH_Host_Key_FP is the
bastion fingerprint from your BEEM warehouse configuration: set it here so
machines never have to accept an unverified host key.

Credentials (UID / PWD) can be included the same way, but they are stored in
the registry in plain text and readable by anyone on the machine — prefer
supplying them per user, or from your own secret distribution.

GPO deployment

1. Place BEEM-Setup.msi on a network share accessible to target machines
2. Create a GPO: Computer Configuration → Software Settings → Software Installation
3. Add the MSI as an "Assigned" package
4. The MSI installs per-machine and requires no user interaction

Bypassing the Redshift driver check

If using PostgreSQL as the backend driver instead of Redshift:

msiexec /i BEEM-Setup.msi /quiet REDSHIFT_DRIVER_INSTALLED=1

Future: Bundled installer

A future release will provide a single BEEM-Setup.exe (WiX Burn bootstrapper) that automatically installs the Redshift ODBC driver and the BEEM driver in sequence, with prerequisite detection.