MID-TERM
REVIEW CHAPTERS 1-11
EXCHANGE SERVER 2000
Chapter 1:
Introduction to Microsoft Exchange 2000 Server
Chat Service (p83,835)
The Exchange Chat Service allows you to configure chat rooms on your server to support real-time
collaboration using any standard Internet Relay Chat (IRC) or Extended IRC (IRCX) client. Users
can communicate synchronously.
The port that Chat Service uses is 6667. The Chat service is integrated with Active Directory, and
uses TCP/IP.
Mixed Mode (p26)
Exchange 2000 supports a specific operation mode called mixed mode to facilitate coexistence with
previous Exchange Server versions and it provides all required components for directory replication
with previous versions. Active Directory Connector (ADC) and Site Replication Service (SRS).
Mixed mode is the default.
Remember that there are no Universal Groups in mixed mode, and you can’t just switch from native
to mixed, it is a one-way trip.
NetMeeting (p24)
NetMeeting is online data conferencing and uses T.120 standard. Video conferencing, on the other
and offers integrated scheduling and management services for multicast video conferencing based on the
H.323 protocol suite. remember the Gatekeeper?
OWA (p24)
Outlook Web Access is an application that works in conjunction with Internet Information Services (IIS).
Using Outlook Access, you can your mailbox, public folders, calendar and appointment items, and the
contacts using any standard browser that support script languages and frames. Using http://and the Web
Browser, allows anonymous or validated access. Clients need to use IMAP and IMAP4 to access Outlook on files.
Client/Server VS Shared File messaging system (p9)
The client only has to inform the server “Here is the message for you. Please deliver it to Paul,” and the
server services will take care of that request. The client does not need to perform the actual server-side
processing, it is handled by the server.
Advantages:
Disadvantages:
If it is the Client/Server, you have better security, reduced network traffic and it is scalable.
Instant Messaging (24, 83)
Allows you to see who is online and send instant messages to users. It integrates IIS 5.0 Web
Publishing service. It is similar to a telephone call since it is one-on-one communication. Share work
and show video, this is live.
SNADS (p27)
System Network Architecture Distributed Systems. Exchange does not provide connectors to messaging
systems that currently uses SNADS or PROFS. IBM-based, IBM mainframe. Direct connection is not
supported by Windows 2000 for SNADs.
Chapter 2:
Integration with Microsoft Windows 2000
DSProxy (p53, 54)
Created by Microsoft Exchange 2000 Server to support MAPI-based clients.
DSProxy also keeps a reference of connections between clients and servers, ensuring that the response
from the Global Catalog is passed to the correct client. DSProxy is part of the Exchange SA and uses
these files: EPROXY.DLL & DSPROXY.DLL.
How and why is RPC important to Exchange 2000? (48, 58, 86)
Replication can be performed via IP, synchronous remote procedure call (RPC) communication, or via
SMTP. IP-based and synchronous RPC communications works best over fast and reliable network
connections (such as a local area network LAN).
RPCs are application layer communication mechanism, which means that RPCs use other
interprocess communication mechanisms, such as NetBIOS, named piped, or Windows Sockets, to
establish communication path.
RPCs are synchronous, and require high-speed network connection.
They involve further interfaces for network communication, such as Windows Sockets.
What is a “smart” MAPI client? (p55)
A smart MAPI client (such as Outlook 2000) can be diverted by the DXProxy to the Global
Catalog directly. To cause DSProxy to divert Outlook 2000 and other smart clients, set the
registry parameter RFR Target Server on the server to the name of the desired Global Catalog
Server HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSExchangeSA\Parameters.
An example of a MAPI client is Outlook 2000.
How do you check that the SMTP service is running?
Check the Services MMC snap-in and view if it is started, if not start it by right-clicking on the service.
You can also ensure that everything is okay by scanning the Event Viewer records. Run Telnet at the
command prompt, port #25 for SMTP. Use Telnet to check for SMTP service, especially if you are
going through a firewall.
\Mailroot (p77)
The Mail root directory for Exchange Server \Programs\Exchsrvr\Mailroot.
\Mailroot is used to store the SMTP virtual directory. D:\exchsrvr\Mailroot\vsi 1 or vsi 2. And the
other directories, BadMail, Pickup and Queue.
Chapter 3:
Microsoft Exchange 2000 Server Architecture
Categorizer (p1024)
A component that performs directory lookups to check message transfer limits and restrictions in
Active Directory. It also handles the expansion of distribution groups for message routing.
Event Sink (p498)
Event Sinks are a script file for the Web Storage System in scripting languages, such as VBScript or
Microsoft Jscript, or using any Component Object Model (COM)-compliant development environment.
Does not relate to Event Viewer, it has to do with Programming languages.
MSExchangeIS
MS Exchange Information Store, must also be running and has several dependencies, such as IIS and
the SA. The repository of user Mail Boxes. IMPORTANT, this is where the E-MAILS are stored.
MSExchangeSA (p71)
Under Application Log in Event Viewer, choose View in the toolbar and select Find command. In the
Find, under Event Source, select MSExchangeSA, and then open the Category list box. This is the most
important of the service, and must be running, it has several dependencies. Monitoring Logs. Also it deals
with the routing Toplogy.
What is ExIPC? (p77)
Is Part of the Information Store service and is also implemented in a DLL names EPOXY.DLL,
located in the \Program Files\Exchsrvr\Bin directory.
What is the Advanced Queuing Engine and what is it used for?
(p63)
Exchange 2000 Server also extends SMTP message queuing by implementing its advanced Queuing
Engine. This engine asynchronously performs actions based on the individual properties of the messages.
Chapter 4:
Planning the Microsoft Exchange 2000 Server Installation
Installation requirements (p122)
Remember BLURSKY.COM!!!
MAPI Clients (626, 134)
A MAPI-Client is an Outlook clients use front end and back end servers.
Examples of MAPI-Clients:
Advantages:
What is the relationship between routing groups and
administrative groups? (p115)
Administrative groups are used to organize administration, it is similar to a containers.
This is a new group to Exchange.
Routing Groups are similar to sites in Windows 2000, define regions of high-speed connections
within your network. You can use a Routing Group Connector, X.400 connector, or an SMTP
Connector to provide a message path between Exchange 2000 routing groups. More the
physical layout.
Chapter 5:
Installing Microsoft Exchange 2000 Server
KMS Data (p173)
KMS is an optional service of Microsoft Exchange 2000 Server that integrates with Microsoft Windows
2000 Certificate services to issue security certificates for Exchange users. The KMS also maintains a key
history for those users for whom it issued certificates. KMSDATA is the directory where the certificate
information is stored. Install on one machine in an organization, (only 1 Administrative Group).
MTA Data (p173)
The \MTA Data directories contain files of former message queues and databases. This is important
because you will not be able to install Exchange 2000 Server again if an \MDBData directory with an
old database file is found on the computer. Microsoft says not to toy around with this and to back it
up regularly. But, if you really know what you are doing you can use the ADSI Edit utility and manually
alter the containers.
Schema Admins (p1060)
A special Windows 2000 group that exists only in the root
domain of an
Members of this group are known as schema administrators. They are authorized to make schema
changes in Active directory.
/ForestPrep (p126)
To run /ForestPrep successfully you must be a member of Enterprise Admins and Schema Admins groups
and you need to be a member of the local Administrators group on the computer where you are running
ForestPrep. ForestPrep/ extends the Schema.
IMAP (p348, 351)
Internet Messaging Access Protocol, taken over by IMAP version 4. For E-Mail messaging, you
do not have to download to the client. Port 143 is used for IMAP, and Secure IMAP 993. It’s
opposite is POP3.
Mdbdata (p173)
Directory Mdbdata is important, Exchange will not work without it. It is off of \Program
Files\Exchsrv\Mdbdata. Stores mailbox and public folders and transactual log files.
Upgrading procedures and requirements (p179)
You may need to upgrade, so upgrade the PDCs first in your domain environment, then bridgehead
servers, then BDCs lastly. Simplify the structure, by leaving only one domain if possible, keep it simple.
Change LDAP port number.
ADC must be set-up, Connectors.
Chapter 6:
Coexistence with Previous Microsoft Exchange Server Versions (p179, 181)
Upgrading to Exchange 2000 (p179, 181)
This may include updating the operating system to Microsoft Windows 2000 Server Service Pack
1 and the server Exchange Server 5.5 Service Pack 3 first.
You will need ADC Active Directory Connectors to populate and synchronize user accounts with
mailbox information.
What are the components involved in maintaining backward
connectivity
with an Exchange 5.5 site?
(p188)
Active Directory supports mixed networks containing computers running Windows NT Server
4.0 and Windows 2000 Server, so you don’t need to upgrade all operating systems at once before
installing Exchange Server. Upgrade the PDC first, and then the computers running Exchange
Server 5.5 one at a time.
If the Exchange servers are operating as BDCs, change the LDAP port number for the Exchange
directory as previously outlined prior to the upgrade. If your domain also contains member servers
running Exchange Server 5.5, upgrade them after the BDCs have been upgraded. You also require
a “Site and Services” account.
Active Directory Connectors
Connection Agreement.
Exchange Full Administrator
(p201)
Although Exchange 2000 Server resources are displayed in the directory information tree within the
Exchange Administrator, any changes you make to these configuration objects are not replicated to
Exchange 2000 Server and don’t take effect.
You must administer Exchange Server 5.5 using the Exchange Administrator program and Exchange
2000 Server using the Exchange System snap-in and other MMCs. When viewing your organization in
Exchange Administrator, note that Exchange 2000 servers are displayed in much the same ways as
servers running previous versions of Exchange. The Full Administrator account has Full Control,
ut you cannot modify the permissions on the containers.
How to maintain a connection to a PROFS site when upgrading
to Exchange
2000? (p149,
198)
Exchange 2000 does not support connectors configured on your existing server, such as PROFS,
hose connectors will not be available after the upgrade. IBM again, mainframe based.
You can upgrade to Exchange 2000 Server in any order, which means that you don’t need to
consider bridgehead or connector servers first. As a matter of fact, you might want to upgrade
these systems last, especially when they are running connector instances not supported by Exchange
2000 Server, such as PROF connector. It is advisable to upgrade public and mailbox server first
so that your users can benefit from the advanced messaging and collaboration features of Exchange
2000 Server immediately.
NOTE: You can never go to NATIVE mode with PROfs. Always in mixed mode.
389 (p203)
The LDAP port of 389. Before updating to change the Port 3289. Open up if going through
a firewall, the LDAP port.
Connection Agreement (p192, 203)
The SRS only replicates data with previous Exchange directories. Connection Agreements of the
ADC, on the other hand, replicate changes between SRS and Active Directory. ADC in Exchange
5.5 must be done with each service (SMTP for example) setup. You can synchronize one way or
both ways.
An In Place upgrade VS a Mailbox upgrade (p195)
An in-place upgrade has the disadvantage of server downtime because the Exchange Server
services must be stopped during the upgrade process. It forces you to perform an Active Directory
cleanup or merge. Those are the 2 options.
During a move-mailbox upgrade, you join an existing site with a machine running Exchange 2000
Server and move all resources from the legacy Exchange server to this computer. As soon as all
resources have been moved, the old system may be removed from the site.
Active Directory Migration Tool (p182)
You can use the Active Directory Migration Tool to clone the existing security information.
Cloned accounts are specific Windows 2000 accounts for which properties and group memberships
have been copied from corresponding Windows NT 4.0 source accounts.
The Migration Tool is useful for NT environments with multiple Windows NT 4.0 domains
because it allows consolidation of the domain environment.
SRS (p201-203, 81)
Site Replication Service is disabled by default or the first one in the site or the bridgehead server.
SRS is a type of Exchange directory service for Exchange 2000 Server. SRS consists of the
following components:
The Windows 2000 SRS implemented in SRSMAIN.EXE
A Site Consistency Checker , which runs as part of SRA and performs tasks similar to the KCC.
An SRS database named SRS.EDB and corresponding transaction logs, which hold Exchange
Server 5.5 directory information and reside in the \Exchsrvr\Dsadata directory or the \Exchsrv\Srsdata
directory (joining and existing site).
Chapter 7:
Microsoft Exchange 2000 Server in Clustered Environments
Clustering (p217)
A group of servers that appear as a single virtual server. It is used mainly for fault-tolerance. You
can minimize downtime cause by software, network, and hardware failure. “Offline Failover and
Online = Failback.
Four-node clustering, you must install Windows 2000 Datacenter Server.
You can have as many clusters at a time, but one can only be active at a time.
Active Directory Domain name change
Should not do, once you have chosen names for your domain, you are stuck with them. You will have
to re-install to change, so make sure you have it right the first time. ADSI Edit can change the name if
you have to. Very hard to do you may have to enter the Registry to get rid of the trail ends of it.
Quorum Disk (p224)
Holds the configuration data log files, is a cluster-specific resource used to communicate changes to
all nodes in the cluster. There is no fault tolerance with this. If the quorum disk is down, you are dead,
this is a problem. Maybe you can mirror it, still considered a single point of failure.
Virtual Servers in clusters (p235, 236)
As soon as you have installed Exchange 2000 on all cluster nodes, you are ready to configure resource
groups. Each virtual server (equivalent to a resource group) requires an IP address and a network name.
Managed in the Exchange Service Manager. Started in IIS.
Chapter 8: Microsoft
Outlook 2000 Deployment
.prf
Or OUTLOOK.PRF is a file you can create and place it in the administrative installation point. This
file will then be copied to the Windows directory (\Winnt) during the installation. You must edit using
a text editor.
Delegation (p429, 432)
Assigning administrative responsibility to another user or group. In Microsoft Exchange 2000
Server, administration is delegated to other users and groups at the organization and administrative
group level using the Delegation of Control Wizard.
You can remove Delegation tab in Outlook/Tools/Options/Other/Advanced/Add-in Manager.
Editor
Use in Outlook, editing your E-mails.
Metabase (78, 364)
It is the task of the metabase update service to transfer the changes into the metabase.
Because the metabase update may take a few minutes, changes may not take effect immediately.
Entirely there for IIS.
Outlook Profile (263)
When you first install Outlook no profile exists. You are prompted by Outlook for create a valid
messaging profile when you start the client for the very first time.
You can create in Control Panel, you can choose from this 1 profile but uses the first one created
as the default.
.mst (p262)
Use as a file in the Custom Installation Wizard. Shared from Administrative Points.
Delegate Access (p276)
Delegate Access refers to a configuration where one user is able to read and send messages and
modify calendar and task items on behalf of another user. On the delegate tab, you can designate
an assistant or configure Delegate permissions for the Outlook folders of your mailbox.
Tools/Options/Delegate users and computers/Right Click the private folders you can delegate
access through the folders.
Private Items
Stored items within Outlook for a users profile. Can’t delegate, if marked as private.
Profile Management
The System Administrator is responsible for the profile management.
Quick Deployment of Outlook 2000
A GPO, then assign or publish it to someone. Then you have an .mst file to modify.
Send on Behalf of
(p278)
The user can use the From button in a message to add your name to the From field. By
default, the From button is not displayed, but your delegate can make this button available
via the message’s View menu and the From Field command. Recipients of the message will
see your name under Sent On Behalf Of beside your delegate’s name in the From field.
Chapter 9:
MAPI-Based Clients
Send As (278)
It you want to designate an assistant to send as permission. The assistant’s name is found on the
Exchange Advanced tab. They also need to grant the Send As permission on the security
property sheet.
Exchange Client Software (291)
If using MS-DOS-based Outlook client and any MAPI based-client does not exist. You will
be forced to use legacy Exchange Client or choose another solution, such as Microsoft Terminal Services.
Laptops and Roaming Profiles (p312)
Windows 95/98, NT and 2000 provide built-in support for roving users because MAPI-based
clients store their messaging profiles within the user’s context in the workstation’s Registry.
Synchronize (314)
Synchronizing should be done with offline files when the laptops for example are docked in the
office. Outlook 2000 can synchronize automatically.
Chapter 10
MAPI-Based Clients in a Novell NetWare Environment
Authentication (365)
There are Anonymous Access, Basic Authentication and Integrated Windows Authentication.
Anonymous uses HTTP and NNTP. Basic is the default.
NWLinks’s greatest connectivity Problem? (325)
“Probably the Frame Type”. If it is not identical on the sending and receiving end you will not
be able to connect. Routable, very chatty.
When manually configuring frame types, you will also need to specify the corresponding external
network number with each frame type added.
What Methods do you have available to get your clients over
to a Groupwise
mail server? (p331)
If you are using Exchange and Novells NetWare GroupWise, it is important to adjust the MSDSS
configuration to avoid the synchronization of GroupWise addresses (that are stored in NDS) with
Active Directory. You can also set-up a connector for GroupWise. Easiest way is to choose
Novell clients, use GSNW to get them connected.
SAP (p328)
You must install the SAP Agent on the server in addition to the GSNW. To install the SAP Agent on
Windows 2000 Server, open the Network and Dial-up Connections program from the Control Panel
and display the properties of the Local Area Connection. You need SAP on all routers for compatibility.
MSDSS (p331)
When integrating Exchange 2000 Server in an environment with NetWare and Novell GroupWise, it
is important to adjust the MSDSS configuration to avoid the synchronization of GroupWise. Novell
client must be installed on Windows 2000 Server.
When wouldn’t a NetWare client while trying to access their
mailbox on the Exchange 2000
Server not be challenged to log on?
Because if you are already logged on and authenticated, you do not need to do so again.
Chapter 11:
Internal-Based Client Access
NDR (p1052) Non-delivery Report
For Outlook, if you cannot find the user, or the account is invalid. Mainly meant for SMTP
messaging.
Access e-mail and calendar remotely – which protocols?
HTTP to connect and access calendars in the outlook.
How to you alleviate the problem of multiple locations and
unreliable connections?
Use SMTP) Protocol for unreliable.
How to stop remote SMTP access but still allow
internal access? (p341) (or filter
for IP address, only allow)
SMTP is an industry standard for the Internet, which rules the transfer of e-mail messages between two
messaging hosts. Do not allow external address, set-up filters. Set-up SMTP on internal network.
Or set-up another “virtual server” and only allow specified groups access to it.
Newsgroup creation (p370)
Creating manually a forum for discussing in Exchange. These resources are not
created in Outlook, they are put in the public folders in Exchange 2000. But, you can view
NewsGroups in Outlook.
Exchange will automatically create a new public folder according to your public hierarchy.
Administrative Group/First Administrative Group/Server/Manchester/Protocols/NNTP/Default
NNTP Virtual Server/Newsgroups.
POP3 (p362)
When you right-click on a protocol container (HTTP, IMAP4, NNTP, and POP3).
POP3 is clear text. POP3 port 110. You can check in Telnet. (p354 & 491). Used for
receiving not sending E-Mails.
Push feed VS Pull Feed (p353)
Usage of NNTP differs slightly between pull and push feeds. Pull feeds need a command set for
querying remote servers. Push feeds can allow larger amounts of data need a command set for
newsgroup creation and article posting.
SKCC (201)
Super Knowledge Consistency Checker. Is used for Exchange Server 5.5 Replication. Can
“Map out”, can tell routes and correct them if they are wrong, so it is dynamic. They are not
actually fixed, they are sent a signal that the route is wrong.
Storage Limits –How to manage them? (428)
Warns users if the mailbox exceeds a certain limit. You can set values in the properties itself.
Similar to quotas. At Exchange Server or at the client end.
Virtual Protocol Servers – What are they and how do your
manage
them? (362)
You can manage them in Exchange Server under the associated protocol: HTTP, IMAP4,
NNTP, POP3 or SMTP.
Blue Sky Airlines/Administrative Groups/First Administrative Group/Servers/Manchester/
Protocols/HTTP;IMAP4;NNTP;POP3;SMTP;X.400.