Instant Messaging Service provides a new means of
communication between individuals that is immediate, interactive, and private.
This article describes how to install and configure Instant Messaging on
Exchange 2000 Server. This article assumes that you have a working knowledge of
64 megabytes (MB) random access memory (RAM) (128 MB or
2 gigabytes (GB) of available NTFS file system (NTFS) hard
CD-ROM drive, network cards, mouse, and so on
Microsoft Windows 2000 Server
Microsoft Internet Information Services (IIS)
Network News Transfer Protocol (NNTP) Stack
Simple Mail Transfer Protocol (SMTP) Stack
Dynamic Domain Name System (DDNS)
Exchange 2000 Server
Exchange 2000 Server
Exchange System Management
Exchange Instant Messaging
Windows 2000 Server with Internet Information Services 5.0
must be installed. Make sure that you select both Network News Transfer Protocol (NNTP) and Simple Mail Transfer Protocol (SMTP) during the installation process.
A DDNS server must be installed and available in your
IMPORTANT: The target installation computer must register all network
interfaces with this DDNS server and corresponding dynamic enabled
A user account that is designated as the Exchange Service
Account should be created in the domain before Exchange 2000 Server is
NOTE: The Exchange 2000 Instant Messaging Server can be installed on
either a member server or a domain controller and requires membership in a
domain. The Exchange 2000 Server computer cannot belong to a workgroup.
Installing Instant Messaging
Install Exchange 2000 from your Exchange 2000 CD. Make sure that
you install the following components:
Microsoft Management Console (MMC) Exchange System Manager
Instant Messaging Service
Configuring Instant Messaging
Create a virtual server. If you create an Exchange 2000
Instant Messaging virtual server, Windows 2000 users can communicate with other
users in real time by using the MSN Messenger Service client program. To create
a virtual server:
Click Start, point to Programs, point to Microsoft Exchange, and then click Exchange System Manager.
Click to expand the Administrative Groups container, and then click to expand the first administrative
Click your server, and then click Protocols.
Right-click Instant Messaging (RVP), and then click New.
Click Instant Messaging Virtual Server.
The Instant Messaging Installation Wizard, which helps
you create the Instant Messaging Service virtual server, is
In the Welcome dialog box, click Next.
In the Display Name dialog box, type the display name of your virtual
In the IIS Server dialog box, click the Web site that you want to use in the
In the Domain Name dialog box, the host or computer name of your Instant Messaging
virtual server is automatically displayed. This information is gathered from
the host header data that is associated with the Web site that you
selected. Change the server name to the fully qualified domain name (FQDN) of the server. The FQDN must have the following format, where servername is the name of the server, and example is your domain name:
In the Host Server dialog box, click to select the Allow this server to host user accounts check box. This means that the server is responsible for hosting
users; otherwise, the server becomes an Instant Messaging router that directs
incoming Instant Messaging traffic to the appropriate destination.
Create and configure a Domain Name System (DNS) service
location (SRV) record:
Start the DNS.
Click the zone that you want.
Right-click that zone, point to Other New Records, point to Service Location, and then click Create record.
In the Service box, type _rvp.
In the Protocol box, type _tcp.
In the Priority box, type 0.
In the Weight box, type 0.
In the Port Number box, type 80.
In the Host offering this service box, type the FQDN of the server.
NOTE: The FQDN is the same as the FQDN that was displayed when you
created the Instant Messaging virtual server.
Enable a user for Instant Messaging:
Click Start, point to Programs, point to Microsoft Exchange, and then click Active Directory Users and Computers.
In the console tree, double-click the domain, and then
Right-click the name of a user, click Exchange Tasks, and then click Next in the Welcome dialog box.
Click Enable Instant Messaging, and then click Next.
Next to Instant Messaging Home Server, click Browse. In Select Instant Messaging Server, in the Server name column, click the Instant
Messaging virtual server that you created in step 1, and then click OK.
When the server is displayed in the dialog box, click Next.
NOTE: Repeat the preceding steps as needed for any additional users
that want to use the service.
Install the MSN Messenger Service client. You may use a
computer that is running either Windows 2000 Server, Microsoft Windows 2000
Professional, Microsoft Windows NT Server 4.0, Microsoft Windows NT Workstation
4.0, Microsoft Windows 95, or Microsoft Windows 98 to connect and communicate
with an Instant Messaging server. Winsock 2.0 must be installed on Windows 95
based-computers to use Instant Messaging. To install the MSN Messenger Service
Insert the Exchange Server CD.
Click Start, and then click Run.
Click Browse, locate
(where drive_letter is the letter of your CD-ROM
drive), and then click OK.
Read the end user license, and then click Yes. The MSN Messenger Service client is installed.
In the Welcome to MSN Messenger Service dialog box, click Next.
In the Provide Microsoft Exchange Instant
Messaging information dialog box, type the e-mail address of the
Instant Messaging user that you want to configure in the following format
where alias is the Exchange 2000 alias
and domain_name is the name of the
In the Get a free passport dialog box,
either import an MSN passport or use Exchange Instant Messaging only, as
After you install the MSN Messenger Service client, the client
can log on to the Instant Messaging server and communicate with other Instant
NOTE: The Instant Messaging client relies on Microsoft Internet
Explorer for the connectivity settings. If there is a period (.) in the user's
Instant Messaging logon domain (for example, someone@.microsoft.com), Instant
Messaging determines that the destination is "external." If Internet Explorer
has a proxy server defined for connectivity, this request is passed to the
proxy server for a connection.