\| \| \| \| News & Media \| Our Blog \| Site Map

Home	Solutions	Products	Downloads	Pricing	Online Help	Support	Contact Us

Home > Support > FAQ

IM Software Frequently Asked Questions

Questions:

1. Can I install the client software in the silent mode?

2. How can I deploy the client software via the Active Directory Group Policy and specify the default name of the IM server and other options?

3. Can I prevent users from changing the settings and exiting the messengers?

4. Can I apply the default (common) settings for all users on the computer that use the messenger?

5. Installation of the client software fails with the following error message: "1155:File INSTMSIW.EXE file not found."

6. How do I install Bopup Communication Server? Are there any specific requirements or third-party software settings?

7. Can I install Bopup Communication Server and the MSDE on a server that already has other MS SQL instances running?

8. Can I manage existing installation of the communication server remotely?

9. Installation of Bopup Communication Server fails during the MSDE 2000 installation. What's wrong?

10. How do I sign up to the IM network outside a domain network/LAN, e.g. from a home computer when Windows Authentication mode is enabled on the communication server?

11. How to backup and restore the communication server database?

12. IM clients are not updated from the communication server as designed. Why?

13. Which ports are used by the communication server? I have to configure firewall on client computers.

Answers:

1. Can I install the client software in the silent mode?

Yes, 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.

Note that command line parameters are valid only for the MSI packages. You can download them from our Download Center.

2. How can I deploy the client software via the Active Directory Group Policy and specify the default name of the IM server and other options?

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 the 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, modify its entry, 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 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.

3. Can I prevent users from changing the settings and exiting the messengers?

Yes, you can prevent users from changing the settings and exiting the program. See the next topic regarding common options and setup.ini pre-configuration file.

4. Can I apply the default (common) settings for all users on the computer that use the messenger?

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 \Documents and Settings\All Users\Application Data\B Labs\Bopup Messenger\ folder. 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 leave 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 \Documents and Settings\All Users\Application Data\B Labs\Bopup Observer\ folder. 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 leave all the options you want to set up as common options to all users on a 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 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.

5. Installation of the client software fails with the following error message: "1155:File INSTMSIW.EXE file not found."

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 the Recommended Updates section at the Download Center.

6. How do I install Bopup Communication Server? Are there any specific requirements or third-party software settings?

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.

7. Can I install Bopup Communication Server and the MSDE on a server that already has other MS SQL instances running?

Yes, you can install the server and its internal MSDE (Microsoft SQL Desktop Engine) on a server that already has other MS SQL instances running. We use the Instance Name "BCS" to install and run the MSDE that comes with the server installation package.

8. Can I manage existing installation of the communication server remotely?

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.

9. Installation of Bopup Communication Server fails during the MSDE 2000 installation. What's wrong?

Make sure that the Server service is enabled and running in your Services list. For more information, please refer to the following article on the Microsoft website: You cannot install MSDE 2000 if the Server service is not running.

10. How do I sign up to the IM network outside a domain network/LAN, e.g. from a home computer when Windows Authentication mode is enabled on the communication 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.

11. How to backup and restore the communication server database?

You can use oSQL.exe utility to access the SQL database, run script files and etc from a command line interface on your SQL server. This built-in utility is also installed when you choose to setup MSDE 2000 within your Bopup Communication Server.

To backup and restore the 'BCS30' database (this database hosts all your communication server data) download the following batch files: backup_sql.bat and restore_sql.bat. Save the files into any folder on your server computer, modify its entries such as a file name of the backup file (it is set to "C:\bcs_backup.bak" by default) and run the files.

12. IM clients are not updated from the communication server as designed. Why?

Both Bopup Messenger and Bopup Observer automatically download new versions from communication server and update itself on startup by default. But this functionality depends on a result of previous updates from the server. And if a previous AutoUpdate was cancelled or failed (due to user account permissions/rights on a computer, etc) then the messenger will not download new installation packages from the server any more.

To enable again the ability of IM clients to download new versions from the communication server you can modify registry on a target computer where the messenger is installed. Download set-autoupdate-messenger.reg registry file for Bopup Messenger and set-autoupdate-observer.reg for Bopup Observer, copy the file onto a client computer, double-click on the file and confirm to apply changes to the system registry.

Note that if the messenger fails to update itself again then it will disable the AutoUpdate feature.

13. Which ports are used by the communication server? I have to configure firewall on client computers.

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.