Beruflich Dokumente
Kultur Dokumente
Setup.exe /forestprep
2. What Exchange process is responsible for communication with AD?
DSACCESS
3. What 3 types of domain controller does Exchange access?
Normal Domain Controller, Global Catalog, Configuration Domain Controller
4. What connector type would you use to connect to the Internet, and what are the
two methods of sending mail over
that connector?
SMTP Connector: Forward to smart host or use DNS to route to each address
5. How would you optimise Exchange 2003 memory usage on a Windows Server
2003 server with more than 1Gb of memory?
Add /3Gb switch to boot.ini
6. Name the process names for the following:
System Attendant? MAD.EXE, Information Store – STORE.EXE,
SMTP/POP/IMAP/OWA – INETINFO.EXE
7. What is the maximum amount of databases that can be hosted on Exchange 2003
Enterprise?
20 databases. 4 SGs x 5 DBs.
8. What are the standard port numbers for SMTP, POP3, IMAP4, RPC, LDAP and
Global Catalog?
- 25 SMTP
- 110 POP3
- 143 IMAP4
- 135 RPC
- 389 LDAP
- 636 LDAP (SSL)
- 3268 Global Catalog
- 465 SMTP/SSL,
- 993 IMAP4/SSL
- 563 IMAP4/SSL
- 53 DNS ,
- 80 HTTP
- 88 Kerberos
- 110 POP3
- 119 NNTP
ASP.NET
ANS: NNTP
Ans: Deals with the restoration of computer system with all attendent software and
connections to full functionality under a variety of damaging or interfering external
condtions.
(Ent.&Datacenter)
This means mail is not being sent to other servers. This can be explained by outages or
performance issues with the network or remote servers.
15. What would a rise in the Local Delivery queue generally mean?
This indicates a performance issue or outage on the local server. Reasons could be
slowness in consulting AD, slowness in handing messages off to local delivery or SMTP
delivery. It could also be databases being dismounted or a lack of disk space.
In the event of a corrupt database, data can only be restored to the last backup.
17. What is the maximum storage capacity for Exchange standard version? What
would you do if it reaches maximum capacity?”
Ans: 16GB.Once the store dismounts at the 16GB limit the only way to mount it again is
to use the 17GB registry setting. And even this is a temporary solution. if you apply
Exchange 2003 SP2 to your Standard Edition server, the database size limit is initially
increased to 18GB. Whilst you can go on to change this figure to a value up to 75GB, it’s
important to note that 18GB is the default setting
HKLM\System\CurrentControlSet\Services\MSExchangeIS\{server name}\Private-
{GUID It therefore follows that for registry settings that relate to making changes on a
public store, you’ll need to work in t he following registry key:
HKLM\System\CurrentControlSet\Services\MSExchangeIS\{server name}\Public-
{GUID}
Under the relevant database, create the following registry information: Value type:
REG_DWORD
Set the value data to be the maximum size in gigabytes that the database is allowed to
grow to. For the Standard Edition of Exchange, you can enter numbers between 1 and 75.
For the Enterprise Edition, you can enter numbers between 1 and 8000. Yes, that’s right,
between 1GB and 8000GB or 8TB. Therefore, even if you are running the Enterprise
Edition of Exchange, you can still enforce overall database size limits of, say, 150GB if
you so desire..
With MIME it is possible to exchange information about the type of messages (the
content type) between the sender and the recipient of the message. MIME also defines the
art of coding (Content-Transfer-Encoding). These are different coding methods defined
for the transportation of non ASCII characters in plain text documents and non text
documents like Images, Voice and Video for transportation through text based delivery
systems like e-mail or the Usenet.
The non text elements will be encoded from the sender of the message and will be
decoded by the message recipient. Coding of non ASCII characters is often based on
“quoted printable” coding, binary data typically using Base64-coding.
There is an extension of this Standard called S/MIME (Secure Multipurpose Internet Mail
Extensions) that allows the signing and encryption of messages. There are other e-mail
encryption solutions like PGP/MIME (RFC 2015 and 3156).
There are several services involved with Exchange Server, and stopping different services
will accomplish different things. The services are interdependent, so when you stop or
start various services you may see a message about having to stop dependent services. If
you do stop dependent services, don’t forget to restart them again when you restart the
service that you began with.
To shut down Exchange completely on a given machine, you need to stop all of the
following services:
Microsoft Exchange Event (MSExchangeES) :-This service was used for launching
event-based scripts in Exchange 5.5 when folder changes were detected. Exchange 2000
offered the ability to create Event Sinks directly, so this use of this service has decreased.
This service is not started by default.
Microsoft Exchange Routing Engine (RESvc):-This service is used for routing and
topology information for routing SMTP based messages. This service is started by
default.
one of the first places you will look for an issue. If you need to enable diagnostics for the
RUS, the parameters are maintained in a separate service registry entry called
MSExchangeAL. This isn’t a real service; it is simply the supplied location to modify
RUS functionality. This service is started by default.
Network News Transfer Protocol (NntpSvc) :-This service is responsible for supplying
NNTP Protocol Server functionality. This service is started by default.
This also means that if you mistakenly delete a mail-enabled user account, you can
recreate that user object, and then reconnect that mailbox during the mailbox retention
period.
Configure the deleted mailbox retention period at the mailbox store object level.
The mailbox is now flagged for deletion and will be permanently deleted at the end of the
mailbox retention period unless you recover it.
1. In Exchange System Manager, locate the mailbox store that contains the disconnected
mailbox.
3. If the mailbox is not already marked as disconnected (the mailbox icon appears with a
red X), right-click the Mailboxes object, and then click Cleanup Agent.
4. Right-click the disconnected mailbox, click Reconnect, and then select the appropriate
user from the dialog box that appears.
5. Click OK.
Note Only one user may be connected to a mailbox because all globally unique identifiers
(GUIDs) are required to be unique across an entire forest
2. Follow steps 1 through 4 in the preceding “To Reconnect (or Recover) a Deleted
Mailbox” section.
2. On the Limits tab, change the Keep deleted mailboxes for (days) default setting of 30
to the number of days you want.
3. Click OK.
Repair the database. ESEUTIL is a tool to defragment your exchange databases offline,
to check their integrity and to repair a damaged/lost database.
You can use the Eseutil utility to defragment the information store and directory in
Microsoft Exchange Server 5.5 and to defragment the information store in Microsoft
Exchange 2000 Server and in Microsoft Exchange Server 2003. Eseutil examines the
structure of the database tables and records (which can include reading, scanning,
repairing, and defragmenting) the low level of the database (Ese.dll). Eseutil is located in
the Winnt\System32 folder in Exchange Server 5.5 and in the Exchsrvr/Bin folder in
Exchange 2000 and in Exchange 2003. The utility can run on one database at a time from
the command line.
22. If you have deleted the user, after you recreated the same user. How you will
give the access of previous mail box ?
Reconnect the Deleted user’ s mailbox to the recreated user. Provided the recreated user
doesn’t have mailbox .
NNTP Network News Transfer Protocol, both nntp and imap helps clients to access the
public folder. but actually, Smtp send the mails across the public folder.
24. What is latest service pack Exchange 2003?
SP2
SP4
priv1.edb
20
29: What is the definition of site, administrative group, and routing group in a
mixed organization?
Ans: An Exchange site is a server grouping for both administrative and topological
purposes. In a mixed organization, the servers running Exchange 5.5 recognize sites,
while the servers running Exchange 2000 recognize both administrative and routing
groups. The Active Directory Connector automatically replicates each Exchange 5.5 site
to Exchange 2000 as both an administrative group with a routing group of the same
name.
30: How does an Exchange 5.5 site relate to an Exchange 2000 administrative
group?
Ans: In a mixed or native Exchange 2000/Exchange 5.5 topology, these are mapped 1:1.
The administrative group is mainly for permissions mapping, although the administrative
group is used to create the legacy-distinguished name (DN).
31: How do messages get from an Exchange 2000 server to an Exchange 5.5 server
in the same site/routing group?
Ans: An Exchange 2000 server evaluates whether the server is in the same routing group
or not. If it is, then the server sends the message through the Message Transfer Agent
(MTA), which creates a direct local area network (LAN), MTA, RPC connection. If it is
not, the server routes the message to the routing group of the destination server through
connectors.
32: How do messages get from an Exchange 2000 server to another Exchange 2000
server in a mixed routing group?
Ans: Exchange 2000 servers, whether in a mixed or pure routing group, always use
SMTP to send messages from one server to another. The SMTP Service will open a direct
connection to the destination server. However, Exchange 2000 servers will route based
on routing groups, not administrative groups.
33: How does a Windows 2000 domain relate to an Exchange 2000 organization?
Ans: There is no relationship. All configuration information for Exchange 2000 is stored
in the Active Directory configuration naming context. This is replicated to every domain
controller to each domain in the forest. Therefore, Exchange Organization information is
available for read/write in every domain.
34: How does a Windows 2000 site relate to an Exchange 2000 routing group?
Ans: An Exchange routing group is a collection of Exchange 2000 servers with high-
availability to one another, but not necessarily high bandwidth. Although the concept of
the Windows 2000 site and the Exchange routing group are quite similar, there are no
alignment prerequisites for deployment. Routing groups are defined in the configuration
naming context of the Active Directory.
35: How does a Windows 2000 domain relate to an Exchange 2000 routing group?
Ans; There is no relationship. An Active Directory domain contains users and computer
information for those that reside in that domain. An Exchange routing group contains
information about Exchange 2000 servers that have high-availability to one another.
Ans: In Exchange 2000, there is a limitation of exactly one Exchange organization per
Windows 2000 Active Directory forest. Conversely, every server within a given
Exchange organization must be in the same Active Directory forest.
Ans; The routing group is the smallest unit of servers likely to be connected to one
another at all times. The routing group is one node on the graph of connector paths with
multiple possible connectors between routing groups.
Within a routing group, or before routing has been configured by the creation of a routing
group, mail from one server to another goes point-to-point using SMTP.
If you wish to have direct point-to-point routing between a collection of Exchange 2000
servers, you can place them into the same routing group. In general, you design your
routing group boundaries based upon connectivity and availability of the network.
Between routing groups, you can define connectors that route messages between these
routing group collections. It is common practice to use a routing group connector (RGC)
to accomplish this.
Ans: If the source bridgehead cannot contact the destination bridgehead, then the system,
by default, retries for 10 minutes. After 10 minutes, the bridgehead is marked
unavailable. If there are other target bridgeheads on the connector, those are tried instead.
Once all target bridgeheads on the connector are tagged as unavailable, then the whole
connector is marked down and other routes are evaluated. If there are other available
routes, message(s) are rerouted. If there are no other routes available, the message will sit
in the local queue until the connector comes back up.
39: What does the routing service do when a local connector is down?
Ans: When the SMTP Service or X.400 Service notices that a connector is down, it
notifies the routing service of this. The routing service marks the connection as down in
its routing state graph.
Ans: The routing master coordinates changes to link state that are learned by servers
within its routing group. When one single server coordinates changes, it is possible to
treat a routing group as a single entity and to compute a least-cost path between routing
groups. All servers in the routing group advertise and act upon the same information.
Ans: All servers in the routing group continue to operate on the same information that
they had at the time they lost contact with the master. This cannot cause mail to loop,
because all servers continue to operate on loop-free information.
When the master comes back up, it starts with all servers and connectors marked up. As it
learns about down servers, it reconstructs the link state information and passes it around.
42: How do SMTP and X.400 servers communicate link state information within a
routing group?
Ans: Each server communicates with the master through a TCP-based Link State
Algorithm (LSA) protocol developed in the transport core development team. Each
server, including the master, is on TCP listening port 691 and registered with Internet
Assigned Numbers Authority (IANA) for this purpose. The master broadcasts changes
only to all servers in its routing group.
43: What are the file names for the essential exchange database?
44: What are the core exchange serives? Are they the same on exchange 5.5 and
2000?
Ans: 53
51: How do you administer the new remote wipe feature in SP2?
A. The new remote wipe capability requires the Microsoft Exchange ActiveSync Mobile
Web Administration tool, one of a collection of Web tools that will be available in late
2005. The Exchange ActiveSync Mobile Administration Web tool was created as a
separate Web tool so that Help desk staff or non–Exchange Server administrators can be
delegated the right to manage devices.
47: How do you administer the new remote wipe feature in SP2?
A. The new remote wipe capability requires the Microsoft Exchange ActiveSync Mobile
Web Administration tool, one of a collection of Web tools that will be available in late
2005. The Exchange ActiveSync Mobile Administration Web tool was created as a
separate Web tool so that Help desk staff or non–Exchange Server administrators can be
delegated the right to manage devices.
A connection agreement type has two check boxes selected by default, even if a
connection agreement already exists. These are “This is a primary connection agreement
for the connected Exchange organization” and “This is a primary connection agreement
for the connected Windows domain.”
If you are using more than one connection agreement to replicate Microsoft Windows
2000 user accounts for a single Exchange Server 5.5 organization, there should be only
one primary connection agreement. Using multiple primary connection agreements to
replicate the same Exchange 5.5 organization will result in creating duplicate objects.
Our transport events technology also makes it very easy for Microsoft or a third-party
software vendor to release an extension to Exchange 2000 that would automatically
compress and decompress messages as they come into or go out of Exchange. In most
cases, compression overhead taxes the CPU of the Exchange server. This reduces
performance, often offsetting any network bandwidth you gained through compression.
Thus, it’s probably better to build more functionality into the client, where you may have
idle CPU cycles to spare, than to tax the server with compression.
Note: Current TLS implementations do not use any compression algorithms.
54: Can Exchange 2000 run on top of a different Microsoft Windows SMTP Server
from Microsoft Internet Information Server (IIS) 5.0?
A. No, Exchange 2000 requires and works in concert with the server events extensibility
that are built into the SMTP server. This ships as part of IIS 5.0 in Windows 2000.
Note: By default, Windows 2000 DNS ships with the IP addresses of the InterNIC root
name servers pre-populated in its configuration. This means that a request for a domain
that is not defined in a zone on the DNS server will be forwarded to one of those servers.
If your server is behind a firewall and cannot reach these servers, you will not get
“Authoritative Host Not Found,” but rather “Server Failed.”
56: How does a Windows 2000 site relate to an Exchange 2000 organization?
A. There is no relationship. A Windows 2000 site is defined as a group of resources
(computers, servers, etc.) that have high-connectivity to one another. An Exchange
organization encompasses the entire forest and bears no relationship to the topological
site structure that the Active Directory administrator defines.
58: Q. Does having a single routing master introduce a single point of failure?
A. No. Exchange 2000 may send mail to a server whose link is down, but mail will
continue to flow, since Exchange will automatically switch to sub-optimal routing if a
routing master fails. Exchange 2000 enables the administrator to manually change the
routing master role from one server to another.
59: How do servers (both SMTP and X.400) communicate link state information
between routing groups?
A. When two servers communicate through SMTP, Exchange 2000 uses a version of
LSA protocol that works as an extension to SMTP through the SMTP Service Extensions
(ESMTP) framework. Exchange 2000 servers advertise X-LINK2STATE support during
the EHLO. When one Exchange 2000 server sees another advertising that, it attempts to
trade routing information. Routing information will only be traded if the two servers are
in the same organization (a DIGEST string is compared). This only occurs in the event of
per-routing-group differences in transferred information.
Between routing groups, when servers communicate through X.400, Exchange 2000 uses
a version of LSA. The MTA constructs a “dummy” X.400 message to transfer this
information.
60: How often do servers that connect between routing groups communicate link
state updates? Are messages used?
A. In the case of link state updates tunneled through SMTP, messages are not used.
Instead, when there is an update, a connection is created to the neighboring routing
group. During the course of that connection, the link state information is transferred. In
fact, even if there is no new information on the source side, during each SMTP
transmission between two Exchange 2000 servers in the same organization, they will
exchange link state information.
In the case of link state updates through X.400 between two Exchange 2000 servers, a
“dummy message” is created that includes the link state update information.
63: How can I control which users have access to Exchange ActiveSync?
A. By default, all users are enabled for Exchange ActiveSync. An Exchange Server
administrator can globally disable Exchange ActiveSync for all users in Exchange
System Manager by using the Mobile Settings option under Global Settings. You can also
enable or disable individual users by using Active Directory Users and Computers.
65: What are the core services in Exchange 5.5? Exlplain the order of starting the
services?
Ans: 1. Directory service(DS): “net start msexchangeds”
2. Information Store(IS): “net start msexchangeis”
3. Message Transfer Agent(MTA): “net start msexchangemta”
4. Internet Mail Connector(IMC): “net start msexchangeimc”
5. “net start msexchangees”
67.We are running an Exchange 2003 server using Panda Antivirus. Panda needs to
have access to the public folders for monitoring and scanning purposes. Both
Exchange and Panda were installed by using the Administrator account and
password. However, Panda is now telling us that Panda and Administrator have no
rights to the public folders. This keeps Exchange from allowing e-mail into the mail
server.
Ans:-Here is what has likely happened to you: Recently the password for Administrator
was changed. The Panda software uses a service account to run the Panda services.
During the install, you probably specified the Administrator account as the service
account. Now the service will not work until you update the password on the Panda
service
To update the password, open the services.msc snap-in, locate the Panda service(s) and
view the properties of the service by clicking on the Log On tab. Change the password
and click OK
68.We are using an Exchange 2000 server and Outlook 2003. We have some public
folders (Contacts, etc). When we were using Outlook XP, it worked fine. But now,
we can’t see public folders with Outlook 2003. What can we do to use and
synchronize it again? In Outlook 2003, public folders are not at the bottom of the
tree where they used to be. Click on the folder button at the bottom of the
navigation pane. The folder list will appear, and then click Public Folders. You may
want to add public folder to your favorite folder list.
Ans:-Unpredictable things can happen if a Microsoft Exchange public folder’s objects are
moved out of the Exchange System Objects organizational unit (OU). For one, you may
get the following error when you try to view the properties of a mail-enabled folder
affected by such a change:
The format of the specified domain name is invalid
Facility: Win32
ID no: c00704bc
Exchange System Manager
You’d think that the solution would be to just move the affected objects back into the
right OU using Exchange System Manager — but it isn’t that easy. One of the odder bits
of asymmetry in Exchange System Manager is that an object can be moved out of the
Exchange System Objects OU, but cannot be moved into it. That’s right — not even if it
originally belonged there in the first place. (From what I have been able to tell, this is to
prevent the OU from getting “contaminated” by things that aren’t supposed to be there,
which makes sense, but doesn’t help us fix the problem!)
The only way to move objects into the Microsoft Exchange System Objects OU is
through the ADSI Edit tool, which is included with Windows 2000/2003 on the
\Support\Tools folder on the installation CD.