&RQWHQWV##
2YHUYLHZ#4#
&RPSDULQJ#&ROODERUDWLRQ#&RPSRQHQWV#5#
,QWURGXFWLRQ#WR#,QVWDQW#0HVVDJLQJ#6#
,QVWDQW#0HVVDJLQJ#&RPSRQHQWV#8#
,QVWDQW#0HVVDJLQJ#'HSHQGHQFLHV#RQ#
:LQGRZV#5333# 43#
,QVWDQW#0HVVDJLQJ#&OLHQW#2SHUDWLRQV# 44#
,QVWDQW#0HVVDJLQJ#6HUYHU#2SHUDWLRQV# 46#
,QVWDOOLQJ#DQG#&RQILJXULQJ#,QVWDQW##
0HVVDJLQJ# 47#
0RQLWRULQJ#,QVWDQW#0HVVDJLQJ# 53#
,QVWDQW#0HVVDJLQJ#%HVW#3UDFWLFHV# 54#
&KDW#6HUYLFHV# 55#
([FKDQJH#'DWD#&RQIHUHQFLQJ#6HUYLFHV# 57#
:KDW#LV#,3#0XOWLFDVW#&RQIHUHQFLQJ"# 64#
([FKDQJH#5333#'DWD#&RQIHUHQFLQJ#
$UFKLWHFWXUH# 66#
&RQILJXULQJ#([FKDQJH#'DWD#&RQIHUHQFLQJ## 73#
/DE#$=#&RQILJXULQJ#DQG#8VLQJ##
([FKDQJH#5333#,QVWDQW#0HVVDJLQJ# 7:#
/DE#%=#&UHDWLQJ#DQG#8VLQJ#([FKDQJH#5333#
'DWD#&RQIHUHQFLQJ# 86#
5HYLHZ## 94#
#
Module 13: Real-Time

owners.

Project Lead:
David Phillips
Instructional Designers:
Lance Morrison (Wasser), Janet Sheperdigian, Steve Thues
Lead Program Manager:
Mark Adcock
Program Manager:
Lyle Curry, Scott Hay, Janice Howd, Steve Schwartz (Implement.Com),
Bill Wade (Wadeware LLC)

Graphic Artist:
Kimberly Jackson, Andrea Heuston (Artitudes Layout and Design)
Editing Manager:
Lynette Skinner
Editor:
Elizabeth Reese (Write Stuff)
Copy Editor:
Ed Casper (S&T Consulting), Carolyn Emory (S&T Consulting), Patricia Neff
(S&T Consulting), Noelle Robertson (S&T Consulting)
Online Program Manager:
Debbi Conger
Online Publications Manager:
Arlo Emerson (Aquent Partners)
Online Support:
Eric Brandt
Multimedia Developer
: Kelly Renner (Entex)
Compact Disc Testing:

„#
Describe the functions of the Chat Services.
„#
Describe the features and components of Microsoft
®
Exchange 2000 Data
Conferencing Services.
„#
Explain the differences between conferencing under Microsoft Exchange
Server version 5.5 and under Exchange 2000.
„#
Describe the Data Conferencing architecture.
„#
Describe the ways Data Conferencing is dependent upon Exchange 2000.
„#
Configure Data Conferencing.
„#
Use System Monitor to monitor Data Conferencing.

3UHVHQWDWLRQ=##
93#0LQXWHV#
#
/DEV=#
78#0LQXWHV#
LY##0RGXOH#46=#5HDO07LPH#&ROODERUDWLRQ#LQ#([FKDQJH#5333#0DWHULDOV#DQG#3UHSDUDWLRQ#
This section provides you with the required materials and preparation tasks that
are needed to teach this module.

components. The comparison slide is a good place to describe the different
purposes of each component.
„#
Instant Messaging Components
This section describes the overall architecture of Instant Messaging and then
goes into greater detail about the server and client, and their relationship to
Windows 2000. The important points are the improvements in the
architecture over the design of Exchange Server 5.5.
„#
Configuring Instant Messaging
This topic describes the features that need to be configured and how to do it.
„#
Monitoring Instant Messaging
This topic describes important considerations for administrators to monitor
to ensure optimum performance. It discusses only tools that have already
been introduced.
„#
Instant Messaging Best Practices
This is a list of the best practices for configuring Instant Messaging at the
time the course was written. Bear in mind that the product was still in beta
so these practices may change with the released version.
„#
Chat Services
There is only one slide about this topic. It is not considered a major feature,
and you can cover it quickly.
„#
Introduction to Exchange Data Conferencing
This topic describes the various features of data conferencing. The
comparison between conferencing under Exchange Server 5.5 and
Exchange 2000 are the most important points of the section.

„
0LFURVRIW#([FKDQJH#,QVWDQW#0HVVDJLQJ#6HUYLFHV
„
0LFURVRIW#([FKDQJH#&KDW#6HUYLFHV
„
0LFURVRIW#([FKDQJH#'DWD#&RQIHUHQFLQJ#6HUYLFHVTraditional e-mail systems cannot transfer dynamic data and information on
demand. For these functions, users still rely on the telephone. Real-time
collaboration services in Microsoft Exchange 2000 provide the immediacy of
the telephone with the functionality of e-mail.
&RPSDULQJ#&ROODERUDWLRQ#&RPSRQHQWV#
The different collaboration services are designed for specific types of
collaboration.
,QVWDQW#0HVVDJLQJ#6HUYLFHV#
Instant Messaging is designed for individual users to have one-to-one
conversations.
&KDW#6HUYLFHV#
Deploy Chat Services in scenarios where individuals need to communicate in
groups, such as in a discussion forum.
'DWD#&RQIHUHQFLQJ#6HUYLFHV#
Data Conferencing Services enable you to pre-arrange an electronic conference.
Participants can share multimedia information, and chat with each other.
At the end of this module, you will be able to:
„#
Choose the appropriate collaboration component to use for a given situation.
„#
Describe the function and configuration of Instant Messaging Services.
„#

Conferencing
Data
Data
Conferencing
Conferencing
Primary Use
Primary Use
Instant
Messaging
Instant
Messaging
Chat Server
Chat Server
Data
Conferencing
Data
Conferencing
Meeting Style
Meeting Style
Closed
Closed
Open Forum
Open Forum
Invitation Only
Invitation Only
Meeting
Structure
Meeting
Structure
Immediate/Ad-

Deployment
Corporate
Corporate
Service Provider
Service Provider
Corporate
CorporateInstant Messaging, Chat, and Data Conference all have unique features suited to
different, specific situations.
6OLGH#2EMHFWLYH#
7R#EULHIO\#FRPSDUH#WKH#
LQWHQGHG#XVHV#RI#WKH#WKUHH#
FROODERUDWLRQ#IHDWXUHV#LQ#
([FKDQJH#53331#
/HDG0LQ#
(DFK#RI#WKH#WKUHH#
FROODERUDWLRQ#FRPSRQHQWV#LQ#
([FKDQJH#5333#LV#GHVLJQHG#
IRU#D#VSHFLILF#W\SH#RI#
FRPPXQLFDWLRQ1#
# 0RGXOH#46=#5HDO07LPH#&ROODERUDWLRQ#LQ#([FKDQJH#5333# # 6#,QWURGXFWLRQ#WR#,QVWDQW#0HVVDJLQJ#
Exchange Instant Messenger
File Tools Help
Add Send
Contacts Currently Online

Messaging server that passes the information to other members of the team or
interested parties. Likewise, a user logging on to the network can quickly find
out who else is online and able to communicate.
Instant Messaging is designed as a way to track the presence of each member of
an individual team. For example, as an Instant Messaging user, you may have
listed in your client ten other team members, their manager, three contacts in
other companies, and a few friends on the Internet.
6OLGH#2EMHFWLYH#
7R#LQWURGXFH#WKH#FRQFHSW#RI#
LQVWDQW#PHVVDJLQJ1#
/HDG0LQ#
$V#WKH#QDPH#LPSOLHV/#,QVWDQW#
0HVVDJLQJ#LV#XVHG#WR#
FRPPXQLFDWH#LQWHUDFWLYHO\#
ZLWK#DQRWKHU#SHUVRQ#
LQVWDQWO\1#
7# # 0RGXOH#46=#5HDO07LPH#&ROODERUDWLRQ#LQ#([FKDQJH#5333#There are seven modifiable presence settings that you can change as appropriate
on your Instant Messaging client:
„#
Online
„#
Invisible (this prevents your presence information from being displayed
even though you are at your computer)
„#
Busy
„#
Be Right Back

because the router obtains the server names from Active Directory, and routes
users accordingly.
,QVWDQW#0HVVDJLQJ#7UDQVSRUW#DQG#0HVVDJH#)RUPDW#
All Instant Messaging communication takes place over HTTP (Hypertext
Transfer Protocol). The message format is XML (Extensible Markup
Language).
# 0RGXOH#46=#5HDO07LPH#&ROODERUDWLRQ#LQ#([FKDQJH#5333# # 8#‹‹
#,QVWDQW#0HVVDJLQJ#&RPSRQHQWV#
Server
Admin.
(MMC)
Server
Admin.
(MMC)
Server
Application
Layer
Server
Application
Layer
FTM
FTM
Locator
Locator
Node
Database
Messenger

0HVVDJLQJ1#
/HDG0LQ#
,QVWDQW#0HVVDJLQJ#XVHV#
FRPSRQHQWV#RQ#ERWK#WKH#
VHUYHU#DQG#WKH#FOLHQW#VLGH#RI#
WKH#WUDQVDFWLRQ1#
9# # 0RGXOH#46=#5HDO07LPH#&ROODERUDWLRQ#LQ#([FKDQJH#5333#,QVWDQW#0HVVDJLQJ#6HUYHU#&RPSRQHQWV#
Server
Admin.
(MMC)
Server
Admin.
(MMC)
Server
Application
Layer
Server
Application
Layer
FTM
FTM
Locator
Locator
Node
Database
Messenger
Client UI

directory service.
5HQGH]YRXV#3URWRFRO#
All Instant Messaging communication between clients and servers takes place
by using the RVP protocol (also known as the rendezvous protocol). RVP is an
extended subset of Hypertext Transfer Protocol - Distributed Authoring and
Versioning (HTTP-DAV), which is an extension to HTTP 1.1.
Developers can use RVP within their applications to access the Instant
Messaging presence data for other uses.
1RGH#'DWDEDVH#
The Node Database is an instance of the Extensible Storage Engine (ESE) that
retains status information for Instant Messaging users.
6OLGH#2EMHFWLYH#
7R#H[SODLQ#WKH#SDUWV#RI#
,QVWDQW#PHVVDJLQJ#WKDW#
UHVLGH#RQ#D#VHUYHU1#
/HDG0LQ#
7KH#,QVWDQW#0HVVDJLQJ#
VHUYHU#LV#FRPSRVHG#RI#ILYH#
PDMRU#FRPSRQHQWV1#
# 0RGXOH#46=#5HDO07LPH#&ROODERUDWLRQ#LQ#([FKDQJH#5333# # :#)LUHZDOO#7RSRORJ\#0RGXOH#
You can choose whether to enable Instant Messaging with entities outside of
the corporate network, such as other Exchange 2000 installations maintained by
business partners, suppliers, or customers. Some organizations may need
intranet-only messaging. In these cases, all of the Instant Messaging
infrastructure is located behind the firewall, and is never exposed to the
Internet. If your company needs connectivity with the Internet, you should
protect your internal Instant Messaging network with firewalls in both the

Database
Messenger
Client UI
Messenger
Client UI
RVP
RVP
MSN
MSN
AOL
AOL
Active
Directory
Active
Directory
Internet
Information
Services
Internet
Information
Services
DNS
DNSYou use the Instant Messaging Client to log on to the Instant Messaging server,
and communicate with other Instant Messaging users. It includes the following
components:
„#
Instant Messaging Client User Interface (UI)

ZULWWHQ/#0LFURVRIW#DQG#$2/#
KDG#QRW#DJUHHG#RQ#KRZ/#RU#
ZKHWKHU/#WKHLU#XVHUV#VKRXOG#
FRPPXQLFDWH#WKURXJK#
LQVWDQW#PHVVDJLQJ1#
# 0RGXOH#46=#5HDO07LPH#&ROODERUDWLRQ#LQ#([FKDQJH#5333# # <#+RPH#6HUYHU#85/#
This HTTP address points to the Instant Messaging home server where the user
is stored. For example, the user Kim at Northwind Traders who is an Instant
Messaging user on the Vancouver server in an Exchange organization with an
IM_Domain equal to im.nwtraders.msft would have the following home server
URL:
•
http://im.vancouver.nwtraders.msft/instmsg/local/im.nwtraders.msft/instmsg
/aliases/kim

'RPDLQ#85/#
This HTTP address points to the Instant Messaging router for the Instant
Messaging domain. The user Kim would have the following domain URL:
•
http://im.nwtraders.msft/instmsg/aliases/kim

,QVWDQW#0HVVDJLQJ#8VHU#$GGUHVVHV#
To provide users with a more convenient format than URLs to identify
themselves and other users, they can use Instant Messaging User Addresses to
identify Instant Messaging users. An Instant Messaging User Address is
formatted in the same way as a standard SMTP e-mail address. To be easily
accessible to other users, Instant Messaging addresses for your users should


,QVWDQW#0HVVDJLQJ#'HSHQGHQFLHV#RQ#:LQGRZV#5333#
Server
Admin.
(MMC)
Server
Admin.
(MMC)
Server
Application
Layer
Server
Application
Layer
FTM
FTM
Locator
Locator
Node
Database
Messenger
Client UI
Messenger
Client UI
RVP
RVP
MSN
MSN
AOL
AOL

Instant Messaging clients connect to the IIS service and the instmsg alias when
logging on to Instant Messaging.
6OLGH#2EMHFWLYH#
7R#GHVFULEH#WKH#
:LQGRZV#5333#IHDWXUHV#RQ#
ZKLFK#,QVWDQW#0HVVDJLQJ#
GHSHQGV1#
/HDG0LQ#
([FKDQJH#,QVWDQW#
0HVVDJLQJ#LV#GHSHQGHQW#RQ#
$FWLYH#'LUHFWRU\/#,,6/#DQG#
'16##
# 0RGXOH#46=#5HDO07LPH#&ROODERUDWLRQ#LQ#([FKDQJH#5333# # 44#,QVWDQW#0HVVDJLQJ#&OLHQW#2SHUDWLRQV#
Status Information
Client Logon
Status Information
Client Logon
IM Client
IM Client
IM Router
IM Router
IM Home Server
IM Home Server
Contact Home Server
Contact Home Server
Active Directory
Active Directory

the client.
4. The Instant Messaging client uses the home server URL address to
connect to their Instant Messaging home server.
5. The Instant Messaging home server validates the users’ Active
Directory user name and password. If there is only one Instant Messaging home server, the im_domain
is the FQDN of the home server. If there are two or more home servers, the
im_domain must be the FQDN of the Instant Messaging router.

6OLGH#2EMHFWLYH#
7R#GHVFULEH#WKH#RSHUDWLRQV#
WKDW#WDNH#SODFH#ZKHQ#D#XVHU#
ORJV#RQ1#
/HDG0LQ#
$#QXPEHU#RI#RSHUDWLRQV#
RFFXU#WR#DXWKHQWLFDWH#XVHUV#
ZKHQ#WKH\#ORJ#RQ1#
,PSRUWDQW#
45# # 0RGXOH#46=#5HDO07LPH#&ROODERUDWLRQ#LQ#([FKDQJH#5333#6WDWXV#1RWLILFDWLRQ#
IM user status information is updated in the Node Database of their home
server. Other Instant Messaging users that have this user as a contact are
notified of status changes by the user’s home server.
&RQWDFW#6XEVFULSWLRQV#
Instant Messaging users can add contacts to their client. After a contact is
added, the Instant Messaging client will obtain status information from the

Server
IM Client
Inside Firewall
IM Client
Inside Firewall
Inside Firewall
Outside Firewall
Inside Firewall
Outside FirewallIn addition to the client logon, authentication, and status operations described
earlier, IM server operations also include redirecting clients to home servers
and proxy operations for clients outside a network firewall.
,QVWDQW#0HVVDJLQJ#5RXWHUV#
You can deploy Exchange 2000 in a front-end/back-end configuration where
the protocols and store can be split onto different servers. Instant Messaging
servers operate with a similar concept.
A bank of Instant Messaging routing servers can be used as the primary point of
contact, and these redirect clients to the home server for the Instant Messaging
user. The bridgehead server configuration allows for one or more front-end
servers to provide a unified view of the Instant Messaging topology.
)LUHZDOO#7RSRORJ\#0RGXOH#
An Instant Messaging routing server will return the appropriate URL to the
requesting client to make the requesting client’s connection based on the
requestor’s IP address and the configuration of the FTM. If the IP address is
inside your firewall, the home server URL is returned; if it is from outside the
firewall, the Instant Messaging domain URL is returned and all client
communications will be sent through an Instant Messaging routing server. In
this configuration, Instant Messaging clients outside the firewall only connect
Instant Messaging Service is installed as part of the Exchange 2000 Setup
program. During installation, the Active Directory schema is updated with some
new classes and attributes to support the Instant Messaging infrastructure.
Instant Messaging management is accomplished through a snap-in in Microsoft
Management Console (MMC). You can load this separately or as part of the
Exchange System Manager.
6OLGH#2EMHFWLYH#
7R#LQWURGXFH#WKLV#WRSLF1#
/HDG0LQ#
,QVWDQW#0HVVDJLQJ#6HUYLFH#
LV#LQVWDOOHG#DV#SDUW#RI#WKH#
([FKDQJH#5333#6HWXS#
SURJUDP1#
# 0RGXOH#46=#5HDO07LPH#&ROODERUDWLRQ#LQ#([FKDQJH#5333# # 48#&RQILJXUH#6HUYHU#&RPSRQHQWV#
„
,QVWDQW#0HVVDJLQJ#9LUWXDO#6HUYHUV
z
5RXWHU
z
+RPH#6HUYHU
„
)LUHZDOO#7RSRORJ\
z
,3#$GGUHVV#UDQJH#SURWHFWHG#E\#ILUHZDOO
z
)LUHZDOO#7RSRORJ\#
The Firewall Topology is configured in the Exchange System Manger MMC
snap-in under Global Settings for the Exchange organization.
You can configure which IP address ranges are protected by a firewall. IP
addresses within this range would be considered inside the firewall. You can
also configure the address of the HTTP Proxy Server used for outbound
connections.
,QVWDQW#0HVVDJLQJ#6HUYHU#1DPLQJ#&RQYHQWLRQV##
When naming your home servers, it is recommended to use im.server_name,
where server_name is the full DNS hostname of the computer (for example,
im.vancouver.nwtraders.msft). You can also use the Exchange server name for
the home server.
When naming your Instant Messaging routers, you should base the names on
your company’s e-mail domain name (for example, im.nwtraders.msft).
# 0RGXOH#46=#5HDO07LPH#&ROODERUDWLRQ#LQ#([FKDQJH#5333# # 4:#(QDEOH#8VHUV#
User
User
Instant Messaging
Address URL
Instant Messaging
Home Server URL
Instant Messaging
Domain
Instant Messaging
Domain

Im.nwtradersmsft A 192.168.1.200
Logon: [email protected]
IM Client IM Router
IM Home Server
DNS – NWTRADERS.MSFT
Im.nwtradersmsft A 192.168.1.200
DNS – NWTRADERS.MSFT
Im.nwtradersmsft A 192.168.1.200
Logon: [email protected]
IM Client IM Router
IM Home Server
Separate Namespace
Separate NamespaceWhen users enter their Instant Messaging address into the client logon screen,
the string will be transformed into a URL. So, [email protected]
becomes http://im.nwtraders.msft/aliases/sparkyc. The client will use DNS to
locate the physical server for the operation
The Instant Messaging domain of a user’s Instant Messaging address should be
based on the SMTP hostname of the user's e-mail address. For example, a user
whose e-mail address is [email protected] should have an Instant Messaging
domain of im.nwtraders.msft.
Using the prefix “im” to denote an Instant Messaging domain allows external
users to easily determine an Instant Messaging address from an e-mail address.
For example, users, whose e-mail addresses end with @nwtraders.msft, should
have the Instant Messaging domain im.nwtraders.msft. Similarly, users, whose
e-mail addresses end with @jp.nwtraders.msft, should have the Instant
Messaging domain im.jp.nwtraders.msft.
The Instant Messaging domain should be identical to the hostname of the