Skip to main content

Installing on Windows

The Windows installer, the MSI and the portable zip, the firewall rule, a silent installation's parameters, BeeBEEP 5.x on the same computer, and uninstalling.

For: administrators, users · From BeeBEEP 6.0.0 · Updated on

BeeBEEP for Windows comes as an installer, as an MSI package and as a portable zip. This page says what each one puts on the computer, how they deal with Windows Firewall and with an older BeeBEEP 5.x, and which parameters an administrator gives them to install BeeBEEP on many computers without a question.

The downloads

FileForNeeds an administrator
beebeep-<version>-windows-x64-setup.exeinstalling BeeBEEP for every account of the computer, with its firewall ruleyes
beebeep-<version>-windows-x64.msithe same installation through Windows Installer, for Group Policy, Intune or any tool that deploys MSI packages (see the MSI package)yes
beebeep-<version>-windows-x64-portable.ziprunning BeeBEEP from any folder, a USB stick included, without installing itno, but see the portable zip and the firewall

All three are for 64-bit Windows 10 (version 1809) or newer, and signed with BeeBEEP's code-signing certificate. Use either the installer or the MSI on one computer, not both: each one stops while the other's installation is there. The headless node beebeep-relay is a download of its own, with its own instructions.

What the installer does

  • Installs BeeBEEP in C:\Program Files\BeeBEEP, for every account of the computer, and adds BeeBEEP to the Start menu; a desktop icon is an option, unticked.
  • Installs the Microsoft Visual C++ Redistributable (x64) when the computer has none or an older one than BeeBEEP needs, so that Windows Update keeps it up to date afterwards. If that installation fails, the installer stops before copying anything.
  • Writes one Windows Firewall rule, so that Windows never has to ask about BeeBEEP (see the firewall rule).
  • Finds an installed BeeBEEP 5.x and asks what to do with it (see BeeBEEP 5.x on the same computer).
  • At the end, Launch BeeBEEP starts it as the account that ran the installer, not as an administrator.

Running the installer again over an installed BeeBEEP upgrades it in place. A BeeBEEP still running is closed by Windows first and its files are replaced without a restart; start it again from the last page or the Start menu.

The firewall rule

The installer first removes every Windows Firewall rule that names C:\Program Files\BeeBEEP\beebeep.exe -- among them the block rules Windows writes when its question about a program is cancelled -- and then writes one rule:

PropertyValue
NameBeeBEEP
GroupBeeBEEP
ProgramC:\Program Files\BeeBEEP\beebeep.exe
Directioninbound, allow
Protocolany
Profilesall three (Domain, Private, Public), unless /FIREWALL= says otherwise

Every profile is the default because Windows classes a network it has not seen before as Public, which is where the first computer of a new office usually is. Who BeeBEEP talks to on a public network is decided by BeeBEEP itself (the network's classification, the network password), not by the firewall.

To keep BeeBEEP off public networks, or to manage the rules yourself, see /FIREWALL= in a silent installation.

The portable zip and the firewall

The zip writes no rule. The first time BeeBEEP starts from a folder, Windows asks "Do you want to allow public and private networks to access this app?". While the question is open, Windows dims the screen and nothing else can be clicked, BeeBEEP included: answer it first.

Despite its title, Allow on its own opens BeeBEEP only on the type of network the computer is on now. To open it on both, choose Show more, tick Private networks and Public networks, then Allow. If the question is cancelled or closed, Windows keeps BeeBEEP blocked on that type of network and does not ask again for that folder; a copy moved to another folder is asked about again.

When the firewall blocks BeeBEEP, its Users screen says so while it finds nobody, with a button Open Allowed apps: there, Change settings (which asks for an administrator), then tick Private and Public on the row named beebeep.exe (a portable copy's row carries the program's file name).

A silent installation

For a deployment tool (a startup script, Intune, SCCM), run the installer with Inno Setup's switches for no window and no restart, and BeeBEEP's own two parameters:

.\beebeep-6.0.0-windows-x64-setup.exe /VERYSILENT /SUPPRESSMSGBOXES /NORESTART /FIREWALL=private /LEGACY5=uninstall
ParameterValuesDefaultMeaning
/FIREWALL=all, private, noneallall: the rule on every profile; private: on Domain and Private only; none: the installer writes no rule and removes none, for an administrator who manages the rules (uninstalling still removes the rules that name BeeBEEP's program)
/LEGACY5=keep, uninstallkeepwhat happens to an installed BeeBEEP 5.x

An upgrade without /FIREWALL= keeps the choice of the installation before it, so a plain upgrade never widens a private rule to every profile. An uninstall forgets the choice. A parameter with any other value stops the installer before it installs anything.

The MSI package

The MSI installs exactly what the installer does, in the same folder, with the same firewall rule, the same Start menu entry and the same uninstall. It shows no page of its own: double-clicked, it shows Windows Installer's progress; deployed, it runs silently:

msiexec /i beebeep-6.0.0-windows-x64.msi /qn FIREWALL=private
PropertyValuesDefaultMeaning
FIREWALLall, private, noneallas the installer's /FIREWALL= (see a silent installation); an upgrade without it keeps the choice of the installation before
DESKTOPICON1nonea desktop shortcut too

It differs from the installer in three things:

  • The Microsoft Visual C++ Redistributable (x64) is not in it. An MSI cannot install another program, so the computer must have the redistributable already, at least the version BeeBEEP was built with; without it the MSI stops before installing anything and says so. Deploy Microsoft's vc_redist.x64.exe first, with /install /quiet /norestart; Windows Update keeps it up to date afterwards.
  • BeeBEEP 5.x is left as it is. No question is asked and nothing is uninstalled; while a 5.x is installed, the Start menu entry is named BeeBEEP 6. To remove 5.x, uninstall it separately.
  • A new version replaces the old one whatever its number, a rebuild of the same version included; a running BeeBEEP is closed first and is not started again.

A property with any other value stops the MSI before it installs anything (exit code 1603, the reason in the log of msiexec /l*v).

BeeBEEP 5.x on the same computer

BeeBEEP 6 installs beside an older BeeBEEP 5.x in its own folder; when the installer finds one, a page asks whether to uninstall it or keep both. Chats, settings and contacts stay where they are either way, and BeeBEEP imports them at its first start.

  • Uninstall BeeBEEP 5.x: the installer first keeps a copy of 5.x's beebeep.rc (BeeBEEP reads it once, to find a data folder 5.x was set to use), then runs 5.x's own uninstaller silently and waits for it. If that uninstaller fails, the installation goes on, and BeeBEEP 5.x can be uninstalled later from Settings > Apps.
  • Keep both: both versions work, but they share the network ports, and only one of them answers some of the other computers' searches. While a 5.x is installed, BeeBEEP 6's Start menu entry is named BeeBEEP 6, so the two can be told apart; once 5.x is gone, the next upgrade names it BeeBEEP again.

In a silent installation /LEGACY5=keep is the default; give /LEGACY5=uninstall to remove BeeBEEP 5.x.

Uninstalling

Settings > Apps > BeeBEEP > Uninstall (for the MSI also msiexec /x beebeep-6.0.0-windows-x64.msi /qn) removes the program, its Start menu entry and every firewall rule that names its program. Each account's data folder (%LOCALAPPDATA%\MarcoMastroddiSW\BeeBEEP: settings, database, logs) and the database password kept in Windows' Credential Manager stay, so a later installation finds them again. To remove a user's data as well, delete that folder by hand; see settings for administrators.

All the help pages