The information contained in this document is believed to be accurate in
all respects but is not warranted by Mitel Corporation (MITEL). The information is subject to change without notice and should not be construed
in any way as a commitment by MITE L or any of it s af fili ates or su bsidi aries. MITEL and its affiliates and subsidiaries assume no responsibility for
any error or omissions in this document. Revisions of this document or
new editions of it may be issued to incorporate any such changes.
Nothing in this doc um en t ma y be reproduced in any manne r, either wholly or in part fo r any u se whatsoever, wi thou t w rit ten perm is s ion from M ite l
Corporation.
OnePoint Messenger, MITEL, MiTAI, Host Command Interface, HCI,
NuPoint Messenger, SUPERSET, SX-200 and SX-2000 are trademarks
of Mitel Corporation.
Windows 95 and Windows NT are trademarks of Microsoft Corporation.
INTEL and Pentium are trademarks of Intel Corporation.
All other product names specified in this document are trademarks of
their corresponding owners.
OnePoint Mess enger Getting Started Guide
9164-120-114-NA , Revision C
for OnePoint Messenger 2.0
August 10, 2000
â,ä , Trademark of MITEL Corporation.
Ó Copyright 2000, MITEL Corporation.
All rights reserved.
Printed in Canada.
Table of Contents
List of Figures and Tables ............................................................... vi
Figure A-1Slot Layout on Riser Card in TS800 .........................................................80
viOnePoint Messenger Getting Started Guide, Rev. C, 8/10/00
1. Introduction
This guide is intended for someone setting up the turnkey OnePoint
Messenger™ Telephony Server at the customer site. The turnkey
Telephony Server is loaded at the factory with all necessary software
and hardware. The installer must configure it on-site for its on-site
network and telephone switch (PBX). To provide integration with a
PBX, see the OnePoint Messenger integration guide for the associated PBX, as listed in “Supporting Documen tation” on page 10 in this
chapter. This guide provides an installation sequence using t he Mitel
SX-2000™ as the example.
This guide also covers the installation of required software on the
Microsoft
messaging environmen t. This chapter includes th e f ollowing sections:
About OnePoint Messenger7
â
Exchange Server and on client PCs to provide a unified
SectionPage
Required Skills9
Organization of this Manual9
Supporting Documentation10
About OnePoint Messenger
OnePoint Messenger is a set of software applications that support
unified messaging. Unified messaging is the combination of
telephone messages, fax, and e-mail on one mail server and the
presentation of those messages to end users through a combined
messaging interface. OnePoint Messenger includes software to
provide unified messaging through Outlook
supported Web browsers, and any touchtone-compliant telephone.
OnePoint Messenger server software is installed on two computers
â
running Microsoft Windows NT
•The “Exchange Server”: The computer running Microsoft
Exchange
OnePoint Messenger Getting Started Guide, Rev. C, 8/10/007
â; OnePoint Messenger adds softwar e t o the Excha nge
Server 4.0:
â
98 and Outlook 2000,
Server for performing unified mes saging , including an Exchange
Extension that adds the Unified Messaging tab to each Exchange
account profile.
•The T e lephony Server : A lar g e suit e of so ft ware co mponents pro -
viding messaging and maintenance services is install ed on a computer that handles communi cation between the t elephony network
and Microsoft Exchange. It also handles the VPIM transcoding
and gateway.
See “OnePoint Messenger Server Components” on page 20 in
Chapter 2 for more on Telephony Server components, and see
Appendix A (page 77) for more details, including line card types and
settings. Se e Chapter 1 in the OnePoint Messenger Administrator Guide for a detailed system overview, a summary of each of the
hardware and software components, and an overview list of tasks.
Chapter 1 in the OnePoint Messenger User Guide also has a basic
system overview and a summary of what you can do with OnePoint
Messenger.
The Turnkey Telephony Server
The OnePoint Messenger “turnkey” system is a fairly standard computer on which is install ed all of the hard ware and softwa re neede d to
perform the role of the OnePoint Messenger Telephony Server—
hence the name “turnkey” system, implying that you only need to
“turn the key” for it to start. However, there is much more involved,
which is the purpose of this manual.
The installed software is listed in Chapter 2 (“What You Need for a
OnePoint Messenger System” on page 13) and includes Microsoft
Windows NT Server 4.0
â
4.01
with Service Pack 1, Microsoft Outlook, and OnePoint Mes-
â
with Service Pack 5, Internet Explorer
senger. The OnePoint Messenger software suite includes both proprietary software and software bundled from other vendors. The
OnePoint Messenger components are detailed in Chapter 1 of the
OnePoint Messenger Administrator Guide.
The turnkey box is the Telephony Server 800 (TS800). It has a standard PC mid-tower design with the typical number and type of
peripherals (keyboard, mouse, CD-ROM, floppy, 6GB EIDE hard
disk). The processor is a 550 MHz Intel Pentium III. 256 MB RAM is
required to support 24 voice ports. The ATI Rage™ video interface
and the NIC are on the motherboard, so they do not require slots. For
8Chapter 1, Introduction
Required Skills
motherboard details, see the Intel JN440BX Mothe rboard Technical
Product Specification included in the box.
The backplane contains three PCI slots and five ISA slots. What line
cards are installed on the system depend on the PBX to which the
Telephony Server will be connected and on the preference of the customer. Information about supported cards appears in Appendix A of
the OnePoint Messenger Installation Guide. Details on cards sup-
ported for a specifi c PBX inte gra ti on appears in the integration guide
for that PBX. Details on the turnkey hardware, including regulatory
approvals, appears in Appendix A here.
OnePoint Messenger installers are expected to have Microsoft Certified Systems Engineer (MCSE) certification in Windows NT Server
4.0 and Microsoft Exchange. While the OnePoint Messenger documentation covers the basic Windows NT and Exchange tasks needed
to configure and manage a OnePoint Messenger environment, installers and administrators must have a good understanding of Windows
NT domain options and ass oci at ed administrator rights, NT tools, t he
Event log, etc.
To provide user access to mailboxes using a Web browser, you must
install and manage Internet Information Server (IIS ), which will
require IIS training.
For those of you instal ling and managi ng W ind ows NT and Exchang e
on the Exchange Server, you will be required to perform NT Administrator functions, including setting up domains, creating administrator accounts, and performing software maintenance and backups.
OnePoint Messenger applications all use common Microsoft Windows interfa ces and interop erate with NT system utilities, so the
learning curve on OnePoint Messenger software is very easy after
you become conversant with Windows NT facilities. For example,
each OnePoint Messeng er application sends error and trace messages
to the NT Event Log. All OnePoint Messenger software with user
interfaces have online help.
Organization of this Manual
This manua l contains six chapters:
•This Chapter 1 introduces OnePoint Messenger and its documentation, and lists required installation and administrator training.
Required Skills9
•Chapter 2 (page 13) lists the hardware and software necessary to
create a OnePoint Messenger unified messaging environment,
including what you ne ed t o get from the PBX programmer, and it
summarizes the installation process. It also lists the administrative rights, accounts, passwords, and computer and network
names that you will need to gather and use.
NOTE: For configuring a Mitel SX-200 for OnePoint Messenger, see the OnePoint Messenger/SX-200 Integration Guide. For
configuring a Mitel SX-2000 for OnePoint Messenger, see the
OnePoint Messenger/SX-2000 Integration Guide.
•Chapter 3 (page 23) covers the installation of Exchange Server
software.
•Chapter 4 (page 29) covers the installation of the Telephony
Server platform, along with configuration adjustments that you
need to make to allow the Telephony Server to communicate
through the on-site network.
•Chapter 5 (page 49) lists validation tests and provides a roadmap
for other tasks.
•Chapter 6 (page 55) details the steps required to install OnePoint
Messenger software on clie nt PCs and covers cli ent PC validati on
tests.
•Appendix A (page 77) contains details on TS800 hardware components and recommended usage, including slot assignments.
Supporting Documentation
The shipping box for the turnkey Telephony Server contains documentation from each of the hardware manufacturers whose components comprise the turnkey system, including computer (separate
documents for motherboard , CD-ROM drive, and SCSI ada pter card),
line cards, and modem. The box should also contain this guide and
any other OnePoint Messenger hardcopy guides ordered by the customer . The OnePoint Mes senger CD-R OM also con tains copi es of a ll
OnePoint Messenger guides, in Acrobat 3.0 PDF format, in addition
to Show N Tel guides from Brooktrout Technology.
The OnePoint Messenger Installation Guide contains information on:
10Chapter 1, Introduction
•Removing, reinstalling, and u pgradi ng OnePoin t Messenge r components and licenses, including the use of the License Install utility for adding Telephony Server feature licenses.
•Hardware and software requirements, upgrade options and considerations, and card configuration instructions.
There is a OnePoint Messenger integration guide for each of the following PBXs:
•Mitel SX-200
•Mitel SX-2000
•Lucen t Definity
•Nortel Meridian
•NEC NEAX 2400
•Fujitsu 9600
•Centrex switches
Each PBX integration guide contains the tasks required to prepare
your PBX to support OnePoint Messenger services:
•Configuring the Telephony Server to communicate with a PBX,
including using Show N Tel Manager and the PBX-related nodes
of Microsoft Management Console
•Setup requirements for peripheral cards and other hardware associated with that PBX i nt egr at ion. See also the manufacturer documentation included in the turnkey system shipping box, and see
Appendix A here (page 77).
The OnePoint Messenger Administrator Guide contains a sy stem
overview and administration details that can help you, the installer,
understand the purpos es and use of the component s. It con tains pr ocedures for creating user mailboxes (Chapter 2), configuring the Telephony User Interface (Cha pter 3 ), managi ng fax se rvice s (Chapt er 4),
and operating and maintaining the Telephony Server (Chapter 5), as
well as details on each OnePoint Messenger utility.
The OnePoint Messenger User Guide describes the use of OnePoint
Messenger voice, fax, and unified messaging features—on Outlook,
Web browsers, and telephones. The guide also contains information
on client software setup.
Supporting Documentation11
All of the OnePoint Messen ger book s are s tored as Acrob at PDF fi les
on the OnePoint Messenger CD-ROM. The Show N Tel Manager User’s Guide from Brooktrout Technology is also included on the
OnePoint Messenger CD-ROM, stored as sntmgrguide.pdf.
Other useful sources of information include Windows NT and
Exchange manuals, as well as the vendor manuals of products that
complete your OnePoint Messenger unified messaging environment.
For a list of URLs of those webs ites, s ee Append ix B in t he OnePoint Messenger Administra tor Guide.
Contacting Mitel Technical Publications
The Mitel Technical Publications and Media Development Group
maintains this document. We welcome your questions and suggestions—notes on spelling and grammatical errors, comments on readability, and suggestions for improvements. Please reference the
document number that appears on the back of the cover page. Send
your comments to:
techpubs@mitel.com
12Chapter 1, Introduction
2. Preparing for Installation
This chapter lists the hardware and software necessary to create a
OnePoint Messenger unifi ed messaging environmen t and summarizes
the installation process:
SectionPage
What You Need for a OnePoint Messenger System13
Remote Management Hardware and Software16
Preparing the Installation Site
•Gathering Information: Names, Passwords, and
Addresses
Installation Summary19
What You Need for a OnePoint Messenger System
T o c reat e a One Point Mess enger unifi ed mes saging envir onmen t, you
need two Windows NT Server 4.0 computers. One computer hosts
Microsoft Exchange with additional OnePoint Messenger software,
and the other is the turnkey Telephony Server. The servers should be
on the same 100 megabit LAN segment. For messaging users to
access and make unified messages from Outlook, OnePoint Messenger client software must be installed on client PCs.
Turnkey TS800
The turnkey TS800 Telephony Server should have all necessary cards
and software instal led at the f actor y. For details on the components of
the TS800, see Appendix A (page 77).
Verify that backup copies of all soft ware for the Telephony Server are
included in the shipment, as listed here and in Chapter 4 (see
“Unpacking the Server and Verifying Contents” on page 30):
16
17
•The OnePoint Messenger CD-ROM containing all OnePoint
Messenger software for the Telephony Server, and OnePoint
OnePoint Messenger Getting Started Guide, Rev. C, 8/10/0013
Messenger add-on software for the Exchange Server and client
PCs
•OnePoint Messenger license key on floppy diskette, which contains data from the existing Telephony Server hardware, so it can
only be used to reinstall OnePoint Messenger on the shipped
configuration. See Chapter 5 in the OnePoint Messeng er I nstalla-
tion Guide or Chapter 9 in the OnePoint Messenger Administrator Guide for details.
•Windows NT Server 4.0 with Service Pack 6a
•Outlook 98
•Internet Explorer 5.01
•MiTAI 7.5.3 for Mitel PBX integrations, (includes the AFC
driver to correspond with Mitel SX-2000 PBX software)
•Network card software on floppy diskette
•Video card software on floppy diskette
NOTE: You do not need the network and video card software
when installing the turnkey Telephony Server, unless it becomes
necessary to reinst all Windows. The drivers avail able on th e Windows NT CD-ROM do not support the network and video cards
in the Telephony Server. For details on upgrading or reinstalling
OnePoint Messenger software, see Chapter 5 in the OnePoint Messenger Installation Guide.
Windows NT Option Pack 4 is included for the Exchange Server,
containing Internet Information Server 4.0, used for provided Web
access to messages.
NOTE: Please refer to the latest OnePoint Messenger Release Notes
for changes in requirements.
Exchange Server
The following software for th e Exchange Server is requi red, but is not
included with the turnkey Telephony Server:
•Microsoft Windows NT Server 4.0 with Service Pack 5 or 6a
•Microsoft Exchange 5.5 with Service Pack 1, 2, or 3
•Internet Explorer 5.01
14Chapter 2. Preparing for Installation
Software Required for Web Browser Access to
Mailboxes
With the OnePoint Messenger Web Access site license (option purchase, noted in the OnePoint Messenger licens e key) you can provide
users access to their mailboxes via supported Web browsers. Currently, the supported bro wsers are Net scape 4.0 or higher and I nter net
Explorer 4.0 or higher.
To provide Web Client access, install on the Exchange Server:
•Exchange 5.5 with Service Pack 1, 2, or 3
•Outlook Web Access (available on the Exchange CD-ROM)
•Internet Information Server (IIS) 4.0 with Active Server Pages,
(available on the NT Option Pack 4 CD-ROM)
Software Required on Client PCs
OnePoint Messenger subscribers (“users”) can be set up to access
various levels of messaging through Outlook, Web browsers, and
telephones. If a user will access messages Outlook, you must install
on the user’s computer (“client PC”):
•Microsoft Windows 95
â
, 98â, or NT
â
•Microsoft Outlook 98 or Outlook 2000
•OnePoint Messenger Desktop Cli ent, inst alled fr om the OnePoint
Messenger CD-ROM or from the \Staging\WEB Client subdirectory on the Telephony Server.
SMDI Integration Hardware
For integrating the Telephony Server to Nortel and Lucent PBXs, the
T el ephony Se rve r req uires a “ca ll pi cku p box” ( proto col co nverte r) t o
collect integration data coming from PBX, translate it to the Simplified Message Desk Interface (SMDI) protocol, and forward it to the
T elepho ny Server. For those PBX integrations, the turnke y Telephony
Server ships with the Calista PBXLink™, which performs that function. For details on options and setup, see the appropriate integration
guide, included on the OnePoint Messenger CD-ROM.
What You Need for a OnePoint Messenger System15
Fiber Optic Cables for a Mitel SX-2000 PBX
For the link between a Mi tel SX-2000 PBX and t he T el ephony Server ,
two cables are requ ired f or a fi ber l ink to the SX-2000—o ne for trans mitting and the other for receiving. The specifications are:
•Fiber cable type: Glass Multi-mode
•Fiber diameter: 62.5/125 mm
•Connector type: ST
•Maximum distance (cable length): 1 km
•Maximum optical loss: 6 dB (including splices and connections)
•The grade or type of cable used must be suitable for the installation (i.e., light or heavy duty, plenum, outdoor). Consult local
building codes and your fiber cable supplier.
Those fiber cables are not provided with the Telephony Server.
NOTE: Optical repeaters cannot be used to increase the maximum
distance.
Remote Management Hardware and Software
The turnkey Telephony Server ships with a copy of Symantec ’s pcAnywhere
T el ephony Server for provi ding remote man agement. You can control
all Telephony Server software, either through your LAN, or, with the
supplied modem, through a telephone connection. This remote management facility also enables offsite vendor technical support personnel to help you with installation and operation problems. The
shipping box contains Symantec’s user manual for pcAnywhere; it
discusses how to set up permissions for specified users to log in from
the network or from a telephone connection.
â
remote control software installed, which you can use on the
Preparing the Installation Site
The T el ephony Ser ver is hou sed in a PC-t ype tower cabinet that has a
footprint of 23 cm wide by 49 cm deep (9" X 19.5"). The cabinet
height is 48 cm (19"). The Telephony Server must be situated where it
can connect to the:
•PBX (for more details, see the relevant PBX integration guide):
•For a Mitel SX-200, use twisted pair wire, 25 feet maximum
16Chapter 2. Preparing for Installation
•For a Mitel SX-2000, use fiber optic link, as listed above
(“Fiber Optic Cables for a Mitel SX-2000 PBX”)
•For PBXs using SMDI integrations, use RS-232 cable, 50
feet maximum
•LAN wiring using standard Ethernet cabling
•Grounded three-prong power outlet (NEMA 5-15R for 115 Vac,
NEMA 6-15R outlet for 230 Vac, or other approved outlet)
Access to the front, rear , and si des of the Telephony Server is required
for maintenance. The Telephony Server should only be situated in a
clean and dry environment in accordance with the following environmental requirements:
•10° to 35° C (50° to 95° F) ambient temperature
•30% to 80% relative humidity non-condensing
•maximum altitude 3048 m (10,000’)
•Isolation from strong electromagnetic fields
•UPS recommended
NOTE: The Telephony Server must be acclimatized to the local
environment for at least 12 hours before installation.
Gathering Information: Names, Passwords, and
Addresses
Before starting the installation, fill out a reference list of computer
names, administrator IDs and passwords, and Exchange names, as
shown in Table 2-1. This will provide you and other instal lers a quick
reference for entering the information in logon and installation setup
screens. You can also enter some or all of this information for future
online reference in the Site Log and the Site Info dialog, both available through the System Service Tool. For details, see Chapter 5 in
the OnePoint Messenger Installation Guide.
What information you record below depends on how you divide
responsibilities and what domain roles the servers play. For example,
if you set up the Exchange Serv er as a domain control ler, any domain
administrator can log onto the machine as the local administrator, so
you do not need a separate local administrator name and password.
For details, see the section “Administrator Rights Overview” on
page 18 below, and see your Microsoft documentation.
Preparing the Installation Site17
Table 2-1 Names and Passwords
1Exchange Server computer name
2Exchange Server local administrator name
2Exchange Server local administrator password
3Microsoft Exchange Site name
4Organization name (entered for Exchange, Outlook, and OnePoint Mes-
senger)
5Exchange administrator logon name (“Exchange_Admin” is used here)
6Exchange administrator password
7Internet domain (e.g., mycompany.com)
8Intranet domain (e.g., http://mycompany_intranet/...)
9IP Address of Telephony Server
10IP Address of Exchange Server
11*Telephony Server computer name (“onepoint” is entered at the factory)
11Telephony Server local administrator name (“administrator” at factory)
12T e le pho ny Ser ver local admini s trat or password (factory uses “rmx250”)
13Telephony Server administrator name (“TSAdmin” is used here)
14Telephony Server administrator password
15Exchange/TServer network domain name
16Exchange/TServer network subnet mask
17Exchange/TServer network default gateway
18DNS IP address
19Exchange/TServer network primary WIN Server
20Exchange/TServer network secondary WIN Server
21Telephony Server Message Center pilot number, as set on PBX
22Telephony Server Automated Receptionist pilot number, as set on PBX
23T e le pho ny Ser ver Fax on Dem and pi lot number, as set on PBX
24Windows NT domain in which Exchange Server resides
Administrator Rights Overview
A major part of OnePoint Messenger installation is the creation and
use of various administr at or acco unt s. It is not necessary that you create your network hierarchy and permissions in exactly the way
18Chapter 2. Preparing for Installation
assumed in this guide. The critical condition is that installers and
administrators have enough rights to install and manage the Telephony Server and Exchange.
This guide uses “TSAdmin” for the logon name of the Telephony
Server administrator and “Exchange_Admin” for the Exchange
administrator. Both are assumed to have domain administrator rights.
You can have multiple Exchange and Telephony Server administrators to whom you can grant different access levels. You may also set
up access privil ege s f or remote administrators in pcAny where. If you
set up other administrator accounts, you should maintain a record of
those names, passwords, rights, and the people that can use those
accounts.
Installati on Summary
The instructions in this guide are written for the installer who is starting with a turnkey Telephony Server (one completely installed at the
factory with at least the minimum hardware and software described
on page 14) and one bare PC (network card should be installed, without installed operating system) for the Exchange Server. However, if
you already have Exchange or Windows NT Server 4.0 installed on
the Exchange Server, you do not need to reinstall. Compare the software requirements listed a bove with what you have to make sure you
have installed what you need.
If you need to make changes to the Exchange Server to support
OnePoint Messenger, do so before you begin to set up the Telephony
Server . Th e direc tions in this guide do n ot deta il the pro cess of install ing Windows NT or Exchange beyond noting the sequence of installation of the critical components. For details on these products, see
your Microsoft documentation. There is a list of references to both
Microsoft documentatio n and Micros oft se rvice packs in Append ix B
of the OnePoint Messenger Administrator Guide.
What you need to do on the turnkey Telephony Server is detailed in
Chapter 4 (page 29), including physically installing it, testing it, setting up addresses and permissions, configuring the Message Transfer
Agent software to send VPIM messages, and integrating it with the
primary Exchange Server. T o in teg rate th e Telephony Server with the
primary Exchange Server, you will run Configuration Wizard, which
manages installation of OnePoint Messenger software from the Telephony Server to the Exchan ge Se rver an d creat es a co uple of adminis trative user accounts in Exchange. Finally, to provide Web access to
Installation Summary19
mailboxes, you install the Web Client server component on the
Exchange Server.
To integrate the Telephony Server with a specific brand of PBX, follow the directions in the OnePoint Messenger integration guide created for that PBX. The specific guide discusses what you need to do
on the PBX, what you need to set up between the PBX and the Telephony Server , how to c onfigu re the ap pro priat e line c ards on t he Telephony Server, and how to configure the integration software on the
T elepho ny Server, including t he assign ment of t elephony a pplications
to ports.
If you need to reinstall OnePoint Messeng er on the Telephony Server,
use the OnePoint Messenger CD-ROM and follow the procedure
listed in Chapter 5 of the OnePoint Messenger Installation Guide.
Follow Chapter 6 he re ( page 55) to install clie nt softwar e on each end
user PC. You can install from the OnePoint Messenger CD-ROM or
over the LAN from the Telephony Server.
OnePoint Messenger Server Components
The installation instructions in this guide are explicit enough for you
to be able to successfully install OnePoint Messenger without
detailed knowledge of how it works. However, you will be better prepared to make choices during the installation if you understand the
roles and uses of the following OnePoint Messenger components:
•Directory Initialization is a utility for manually performing an initial directory synchronization on the Telephony Server with the
Exchange Server directory. Thereafter, Directory Access Service
(DAS) automatically synchronizes Exchange and Telephony
Server directories. For details, see Appendix A in the OnePoint
Messenger Administrator Guide.
•License Install is a utility for installing feature licenses. For
details, see Chapter 5 in the OnePoint Messenger Installation Guide.
•ODBC provides for compaction of OnePoint Messenger configuration and maintenance databases. For details, see Chapter 9 in
the OnePoint Messenger Administrator Guide.
•Telephony Server Monitor (TSMon) and WinFT Watchdog are
utilities that manage the starting and stopping of OnePoint Messenger services. For details, see Chapter 5 in the OnePoint Mes-
senger Administrator Guide.
20Chapter 2. Preparing for Installation
•Show N Tel Runtime is a software suite from Brooktrout Technology that supports call processing, PBX integration, and other
functions. For details, see the Chapter 4 in the OnePoint Messen-ger Installation Guide, your specific PBX integration guide, or
the Brooktrout Show N Tel Manager User’s Guide included as
sntmgrguide.pdf on the OnePoint Messenger CD-ROM.
•The Telephone User Interface (TUI) provides the telephone
menus and prompts and manages the interface parameters to the
Post Office Network Gateway (PONG) and DAS to send and
receive messages, addresses, and user data. You can rerun the
OnePoint Messenger Installation Program to choose additional
prompt languages to install—U.S. English, U.K. English, Spanish, or any combination. For details on configuring the interface,
see Chapter 3 in the OnePoint Messenger Administ rator Guide .
For details on using the TUI, see Chapter 7 in the OnePoint
Messenger User Guide.
For a summary of OnePoint Messenger components installed on the
Telephony Server, Exchange Server, and client PCs, and for a task
summary, see Chapter 1 in the OnePoint Messenger Administrator
Guide.
Installation Summary21
22Chapter 2. Preparing for Installation
3. Installing Exchange Server
Software
This chapter covers the installation of Windows NT and Exchange
Server software on the Exchange Server. If this software is already
installed, you do not need to reinstall. V erify in Chapter 2 (“What Y ou
Need for a OnePoint Messenger System” on page 13) that you have
the components you need. Although it is not essential, consider
removing any software from the Exchange Server that is not related
to the operation of th e c ore messa ging functions. The performance of
the messaging services is dependent on the availability of syst em
resources. The sections in this chapter are:
SectionPage
What You Need to Complete This Chapter23
Installing Windows NT Server 4.027
Installing Microsoft Exchange27
Where To Go from Here28
What You Need to Complete This Chapter
To complete the procedures detailed in this chapter, you need the following software for the Exchange Server:
•Windows NT 4.0 with Service Pack 5 or 6a
•Microsoft Exchange Server 5.5 with Service Pack 1, 2, or 3
•To provide users with Web browser access to unified messages:
•Microsoft
Option Pack 4
•Microsoft
•Microsoft Outlook Web Access
•OnePoint Messenger Web Client server component
OnePoint Messenger Getting Started Guide, Rev. C, 8/10/0023
â
Internet Information Server (IIS) 4.0, from NT
â
Internet Explorer (IE) 5.0 or higher
CAUTION! To use McAfee VirusScanâ on the Exchange
Server, you must install VirusScan 4.03 or higher.
Installing Windows NT Server 4.0
NOTE: If Windows NT Server 4.0 with Service Pack 5 (SP5) is
already installed, you do not need to reinstall. If you are not sure that
SP5 is installed, check the Version tab in Windows NT Diagnostics
(in the Administrative Tools group).
Install NT Server 4.0, with NTFS as the file system. Do not select
Internet Information Server (IIS). You will install IIS 4 from NT
Option Pack 4.
During the NT Server installation, you must choose the NT domain
role for the Exchange Server, from these choices:
•Primary Domain Controller (PDC)
•Secondary Domain Controller (“backup server” or BDC)
•Stand-alone Server (“member server”)
•W or kgr oup onl y
For OnePoint Messenger, you can select any one of th e roles initially,
but the directions in this guide assume that you set up Exchange as a
stand-alone server. See your Windows NT Serve r documentati on for a
full discussion of the options.
Installing NT Server 4.0 Service Pack
1. After installing NT Server 4.0, shut down and restart the Tele-
phony Server with NT Server 4.0 Service Pack 5 or Service Pack 6a in the CD-ROM drive. The setup should autostart.
2. During the installation of the service pack, do not select the
options to install IIS or Active Server Pages (ASP). You will
install upgraded components from Option Pack 4.
If you have an NT service pack higher than SP 6a already installed,
you may be able to use it instead. Please check with Customer Support. If you need to resolve issues through offsite technical support,
be sure to note the later service pack.
24Chapter 3, Installing Exchange Server Soft-
Installing Opt ion Pack 4 and In ternet Expl orer
If you want to provide Web access to mailboxes, install IIS 4.0 from
Windows NT 4 Option Pack 4 and Internet Explorer (available on
the Outlook CD-ROM or from the Microsoft Web site) on the
Exchange Server.
1. From the Option Pack 4 main installation screen, select the Cus-tom installation option.
7. In order for the Unified Messaging Player and recorder to appear
in the Web Client, set up IIS using the default “Basic Authenti-cation on the Exchang e V irtual Di rec tory.” This guide does not
otherwise discuss IIS setup and management.
8. From the Outlook 98 CD-ROM, its own CD-ROM, or from the
Web, install Internet Explorer 4.01 with Service Pack 1, or any
higher version, through Internet Explorer 5.01. You can download Internet Explorer from the Microsoft Web site at:
NOTE: To support Web access, you also need to inst all Out look Web
Access from the Exchange Server CD-ROM (see page 27), and purchase and install the One Poin t Messenge r Web Client site license and
software (see page 47).
Making the Exchange Server Part of the Domain
NOTE: If you set up the Exchange Server on the domain while
installing Windows NT, you do not need to perform this procedure.
To perform this procedure, the domain administrator must log on to
the Exchange Server.
1. Log on to the Exchange Server as the local administrator.
2. Right-click the Network Neighborhood icon on the desktop.
3. On the Identification tab of the Network dialog, click Change.
Installing Windows NT Server 4. 025
4. On the Identification Changes dialog:
•Click the Domain radio button.
•Enter the domain name.
•Click Create a Computer Account in the Domain.
•In the User Name field, enter the domain administrator
name.
•In the Password field, enter the domain administrator pass-
word.
•Click OK.
5. The Network Configuration screen displays
Welcome to the <domain name> Domain.
Click OK.
6. The Network screen is displayed, click Close.
7. On the Network Settings Change screen, click Yes to restart the
computer.
Testing the Network Connection
1. When the Exchange Server reboots, log on to the domain:
a. Click the drop-down arrow by the Domain fiel d on th e log-o n
screen
b. Select your domain name from the list.
c. Enter your domain administrator network user name.
d. Enter your domain administrator password.
e.Click OK.
The fact that you r computer is able to log on to the domain cons titu tes
a test of network connectivity.
To further test connectivity:
1. From the Windows Start menu, choose Programs, then Command Prompt.
2. In the Command Prompt window type:
ping <IP address>
26Chapter 3, Installing Exchange Server Soft-
where <IP address> is the IP addre ss of anothe r computer run ning
on the LAN.
or type the computer name of a computer on the network.
3. On the screen you should see the following display:
C:\>ping <server name>
Pinging <servername>.<domain Name> [IP Address] with
32 bytes of data:
Reply from <IP Address>: bytes=32 time=20ms TTL=128
Reply from <IP Address>: bytes=32 time=1ms TTL=128
Reply from <IP Address>: bytes=32 time=44ms TTL=128
Reply from <IP Address>: bytes=32 time=2ms TTL=128
4. Enter Exit to quit the Command Prompt window.
Installing Microsoft Exchange
Set up an Exchange Administrator NT account:
NOTE: For details, refer to the directions in the Microsoft manual
Exchange Server Getting Started.
1. Log on to any NT Server in the domain in which the Exchange
Server resides as a domain administrator: Click the Windows
Start button, then choose Programs, then Administrative Tools,
and User Manager for Domains.
2. From the User menu in the User Manager for Domains application, choose New User.
3. In the User Name field, enter the ID for the Exchange Administrator that you entered in Table 2-1. (“Exchange_Admin” is used
in these instructions as an example.)
4. In the Password field, enter the password for Exchange_Admin
that you entered in Table 2-1.
5. Confirm the passwor d.
6. Clear User Must Change Password at Next Log On.
7. Select Password Never Expires.
8. Click Groups.
Installing Microsoft Exch ang e27
Loading...
+ 61 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.