|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Home > Products > IM Setup Guide | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Step-By-Step Guide to Setup Instant Messaging (IM)
This document contains a step-by-step manual on how to install Bopup Communication Server version 3.x and get IM clients connected. The installation of the server does not require any specific knowledge or skills. It is easy to install the server and get it ready and working just after the installation process.
Installation. System RequirementsBopup Communication Server requires the following minimum system configuration:
** — The built-in MSDE 2000 package that comes with the installation is not supported by Windows Vista and on that system the communication server should be installed using an existing external MS SQL Server. Installation. SQL Server setup
Run the Setup Wizard to install Bopup Communication Server 3.x on a computer that will be used as an IM server.
During the installation process, the Setup Wizard asks you about the SQL database setup mode. The SQL Server is used to store the Bopup Communication Server data that includes user account information, user groups, message history, etc.
If the SQL server is already installed on a local or remote computer, it is recommended to use that SQL server. In that case you need to specify the name of the server, enter Login ID and Password to create a Bopup Communication Server database on the SQL server. Otherwise choose the option to install the SQL Server locally. In that case the Setup Wizard installs MSDE 2000 (Microsoft SQL Server Desktop Engine) on the local computer.
After the Setup Wizard finishes its work, Bopup Communication Server is ready to be used and it can accept messenger connections. Setting up user accounts. Authentication mode
After you install Bopup Communication Server, you need to set up the options related to creating user accounts and authentication mode. Since each user should have his or her own IM account on the server to be able to connect to it, you should first specify the account creation options and/or create user accounts on the server. An IM account has the same name as the Windows login ID the user log on to a computer with.
There are 3 modes available to authenticate users on the IM server: Simple, Windows Authentication and Private login/password pair. Simple mode only matches user's Windows logon ID and account name on the communication server. No any other authorization is used. For example, all users who logs to Windows with the Administrator name will establish the connection with the communication server with the same IM account name. In the Windows Authentication mode the communication server authenticates users using standard Windows Authentication (SSPI). This is the most preferred mode for domain networks and it offers more security than the Simple mode. Private login and password mode offers to use a pair of private login name (IM account name) and password to authenticate users on the communication server. Those login names and passwords are not based on Windows authentication credentials and can be chosen by users, for example, user's e-mail address and his desired secure password. Setting up user accounts. Account options
There are 3 ways to create user accounts on Bopup Communication Server: import accounts from the Active Directory, create each account manually via the Add User Account Wizard or allow users to create their own accounts on the server from IM clients.
The following topics describe each of these ways. Setting up user accounts. Import from the Active Directory
It is easy to create user accounts if your network is based on the Windows Domain structure. You can import accounts from the Active Directory (LDAP) catalog with the help of the Active Directory Import Wizard. Just run the wizard from the Tools menu in the Management Console.
Setting up user accounts. Create via the account wizardThe Management Console includes tools for managing user accounts on the IM server. To create a new user account, run the Add User Account Wizard. Setting up user accounts. Create from IM clients
You can permit users to create their own IM accounts from messengers in the server options (described above). When the options allow users to create accounts, the IM client automatically displays the Create My Account Wizard when establishing a connection and allows the user to enter his own account information, such as the first and last names, title, department, contact details that are visible to other users. After the wizard finishes its work, the IM account is created on the server. When the option "Created accounts are enabled by default" is enabled, a new user automatically logs into the IM network.
Managing the IM workspace. Organizational Units
Organizational Units constitute the primary way to manage the user's permissions to send messages and view other users available on the IM server. You can create the Organizational Units tree by any criteria according to your corporate infrastructure, such as office locations, departments, user roles or any other particular criteria.
Manage each unit permissions and place users for the best type. It is an easy and flexible way to control the list of users that is available to users from the same Organizational Unit. You can easily move users and units from one Organizational Unit to another. When you move a user, you change his permissions to view other users in the contact list and send messages and files to them because the new unit's permissions are applied to the user. This action also resets the user's Contact List stored on the server and the user receives the corresponding notification in the messaging client. If you move an Organizational Unit, you change only your IM network structure visible in the Management Console and no changes are applied to users. Managing the IM workspace. Messaging GroupsThe centralized client/server architecture allows you to manage messaging groups from the IM server. Each user can be assigned to multiple messaging groups at the same time. A group is assigned to the user with the sending permission flag, which means that the user has the right to send messages and files to the group. The list of assigned messaging groups is visible in the messaging client, so the user can simply select a group and send a message or file to it. Managing the IM workspace. News messagesThe news messaging system is designed to create messages that should be automatically sent by the IM server at a certain time. It is easy to notify users and groups about any events that may occur, such as a file server restart, a discussion meeting, etc. Getting IM clients connected. Set up a connection to the server
To log into the IM network and to be able to communicate with others, the user should specify the name of the computer where Bopup Communication Server is running. The messenger automatically displays the Connection Setup Wizard each time it is started and the IM server is not specified or no connection can be established.
The name of the server can be a simple NetBIOS name (like a computer name) if the client connects from the same local area network, e.g. "imserver". If the connection is established via the Internet, the user should enter the IP address or DNS name of the server. To verify the specified name and establish a test connection to the IM server, click the "Check connection" button.
Getting IM clients connected. Sign up to the IM network
When the Windows Authentication mode is enabled on the communication server the IM clients use current user's Windows Login ID by default as an IM account name to authenticate user. If Windows Authentication fails or the Private login/password authentication mode is enabled, then "Login to the IM network" pane is shown in the instant messaging client to allow users to enter their own IM account name and password to sign in.
Users can login to the IM network outside a domain network even the Windows Authentication mode is enabled on the server. For successful authentication they must enter their Windows Login ID including domain name, i.e. in the DOMAIN\account format. The messengers automatically resolve and deliver specified domain name on the server that gives users ability to authenticate to the communication server using Windows Authentication outside a domain LAN, for example, from home computers or other locations. Additional information on server and client software comes with the product and can be found in product's help documentation.
Available Event Codes
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||