Frequently Asked Questions

You can use command line arguments for MSI setup packages and install software in the silent mode.

Use the following command line keys to run the setup packages:
"msiexec /i setup.msi /qn" — Installs the software in the silent mode and does not display any setup dialog boxes.

It is possible to use Setup.ini configuration file to upgrade existing versions the messenger software silently or deploy it with no setup dialogs via Active Directory Group Policies. For more information see the next question and IM Client Configuration Tool topic in Bopup Communication Server product documentation.

Unlike in case with the previous question, Microsoft does not allow you to specify any command line parameters for an MSI package when it is deployed via Active Directory Group Policies. So you cannot normally use the command line parameters listed above to set the name of the IM server.

We extended the MSI packages and added the possibility to specify the name of the IM server via Setup.ini configuration file. You may also set other options via the configuration file that will be applied as "common" options in the software and cannot be changed by users.

Download the Setup.ini file and modify its entry, or use IM Client Configuration Tool to build new settings file via graphic interface, then place the file into the same shared folder that contains the MSI package and deploy the software via the Computer Assign options.

You can use the Setup.ini file on a regular installation of the client software. Put the file into the same directory where you place the MSI package to and start the Setup Wizard.

For extended information on the Setup.ini Configuration Tool please refer IM Client Configuration Tool topic in Bopup Communication Server product documentation.

You can prevent users from changing the settings and exiting the program. See the next topic regarding common options and Setup.ini configuration file.

Yes, you can apply the common settings for all users who run the client software on the same computer.

Manual deploying

For the Bopup Messenger software:
Create the "bopup.ini" file in the following path under users common directory which is different for Windows systems:

Windows XP, Windows Server 2003, Windows Server 2003 R2
\Documents and Settings\All Users\Application Data\B Labs\Bopup Messenger\

Windows Vista, Windows 7, Windows Server 2008, Windows Server 2008 R2, Windows 8, Windows Server 2012
\ProgramData\B Labs\Bopup Messenger\

Just copy the existing settings file from the user's profile directory at \Documents and Settings\USER_LOGON_NAME\Application Data\B Labs\Bopup Messenger\, edit the file and keep all options you want to set as common ones for all users on the computer.

For the Bopup Observer software:
Create the "observer.ini" file in the following path under users common directory which is different for Windows systems:

Windows XP, Windows Server 2003, Windows Server 2003 R2
\Documents and Settings\All Users\Application Data\B Labs\Bopup Observer\

Windows Vista, Windows 7, Windows Server 2008, Windows Server 2008 R2, Windows 8, Windows Server 2012
\ProgramData\B Labs\Bopup Observer\

Just copy the existing settings file from the user's profile directory at \Documents and Settings\USER_LOGON_NAME\Application Data\B Labs\Bopup Observer\, edit the file and keep all options you want to set as common ones for all users on the computer.

Automated deploying

You can also distribute common settings with the client software on deploying the messengers using the "IM Client Updates & Branding" built-in feature. Just upload new *.MSI packages and the Setup.ini file on the server to distribute settings within the new version.

Common options are displayed in the messenger as "read-only" options and cannot be changed by users.

This warning message appears on computers running the earlier version of Windows Installer (MSI). Our installation packages for client messengers require Windows Installer version 2.0.

You can download Windows Installer engine version 2.0 for Windows 95/98/ME and Windows NT 4.0/2000/XP/2003 from official Microsoft website using the links below:

Windows Installer version 2.0 for Windows 95, 98 and Me
Windows Installer version 2.0 for Windows NT 4.0, 2000 and XP

Installation of Bopup Communication Server is a very easy and simple. You do not need any other software or additional experience to install Bopup Communication Server. Just click to install and get it working.

For more information see the Step-by-Step Guide to Setup Instant Messaging (IM) article that includes detailed instructions on how to install the server and get IM clients connected to it.

Yes, you can install the server and its internal Microsoft SQL Server 2005/2008 on a server that already has other MS SQL instances running. Since we use the "BCS" instance name to install and run the built-in database software that comes with the server installation package so there will be no conflicts and issues if the computer is already running MS SQL Server.

Yes, you can control and manage your existing installation of the IM server from a remote computer. In order to do this you need to install a part of the communication server (administrative part) on a remote computer. Run the installation package of the server and choose "Install the Management Console only" option on the Database Setup Mode dialog box. Then you need to enter a name or address of the server comptuter which running the Bopup Communication Server and provide valid credentials to connect to the SQL server.

You can login to the IM network outside a domain local network even the Windows Authentication mode is enabled on the server. For successful authentication you must enter your own Windows Login ID including domain name, i.e in the DOMAIN\account format. The messenger automatically resolves and delivers specified domain name on the server that gives you ability to authenticate to the communication server using Windows Authentication outside a domain LAN, for example from a home computer and other locations.

Please note that Windows Authentication cannot be supported if mobile IM client for Android platform is used. In this case such connections from mobile devices must be permitted on Authentication tab of the Options dialog in the server console to use Private login/password authentication mode instead.

Bopup Communication Server contains built-in functionality to backup, restore and clean up SQL database. For more information please refer to the online documentation topic at SQL database maintenance options.

You can also refer to the Step-by-Step Guide to Migrate and Move Bopup Communication Server Database to a New Microsoft SQL Server article that provides detailed information on creating and restoring a backup of Bopup Communication Server database.

You can get a SQL error #5 during creation of a backup of the program database. This error can occur when a target directory that has been chosen to save a backup file is located in current user's profile folder such as "My Documents", "Desktop", etc. Please note that backups are created by SQL Server service running on the computer and it may not have a write access to those locations. In case of the error try to choose another location to save a backup file.

Bopup Communication Server uses 19810 (Primary) and 19809 (for remote Management Console) TCP/IP ports. These ports must be added to allowed list in firewall applications both on the server and client computers to enable instant messaging.

Yes, instant messages to users and groups can be sent from the IM server using the bcscmd.exe command line tool. This utility comes with Bopup Communication Server and allows to use it and send instant messages from external third-party applications, scripts and batch files.

For more information on supported command line switches and parameters refer to the server documentation topic at BCSCmd.EXE command line tool.

It is possible. In order to distribute or install Bopup Messenger and Bopup Observer client software with a built-in (pre-existing) branding image you should use a MSI setup package. Then place your company logo named brand-logo.bmp filename into the same folder where the MSI file is located. The setup will automatically recognize the BMP image file, copy and use it as a common branding image in the messenger (visible to all users on a computer).

Please note that pre-existing branding logo will be shown only if the communication server has no uploaded branding image or the messenger starts with no connection to the IM server. If you upload a new branding logo on Bopup Communication Server then it will be shown instead of pre-existing branding image installed with the messenger.

Sometimes due to unknown reasons Bopup Communication Server may disappear from Services List in Windows so the communication server stops working. In order to resolve this problem you have to register the service manually to get it visible and start from the Management Console again. Follow the step below to register the service file.

1. Open installation directory of the communication server in Windows Explorer. By default that directory is located at \Program Files\Bopup Communication Server.
2. Click Start menu and choose Run... option from there. This will open a command field.
3. Select bcssrvc.exe file (communication service) and drag-n-drop it from opened folder to the Run... text field.
4. Type /service command line argument after full path of the inserted service file so the run string looks like as "PATH\bcssrvc.exe" /service.
5. Press Enter to run the command and register the communicaton server in Windows system. Then open the Management Console and start the service.