Useful
Useful
Useful
01
Exchange 2003 Forestprep extends the AD schema to include Exchange specific information.
02
Exchange 2003 Domainprep creates the groups and permissions necessary for Exchange servers to read and
modify user attributes.
03
What is a DC?
A DC is a Windows 2000 or 2003 Domain Controller that holds active directory partitions for a domain (used
for things like user authentication).
04
What is a GC?
A GC is a Global Catalog Server. A GC holds a full set of attributes for the domain in which it resides and a
subset of attributes for all objects in the Active Directory Forest.
05
Dynamic DNS (described in RFC 2136) allows servers to dynamically update and create records in DNS.
Dynamic DNS is used by the Exchange server to create server records and other entries used by the Exchange
Servers for things like message routing. In a simple Exchange organization, DDNS is not strictly necessary, but
makes administration much easier.
06
A border server is an Exchange server that communicates with external servers. In a single server
organization, your server is by default a border server. In a multi-server configuration, you may have one or
more dedicated servers that communicate directly or indirectly with foreign servers and then pass the mail
to other internal Exchange servers.
07
How does an Exchange 5.5 site compare to an Exchange 2003 Routing Group or Administrative Group?
In a mixed mode Exchange environment the Exchange 2003 Administrative Group and Routing Group
correspond to the Exchange 5.5 site. In a native Exchange 2000 environment, the Administrative Group is a
group of Exchange objects sharing a common set of permissions and routing groups define how those servers
communicate with one another. A single Administrative Group can contain several Routing Groups. Example:
Your North American Exchange servers might be grouped in a single Administrative Group, but subdivided
into several Routing Groups to optimize interserver communication. An Administrative Group contains zero
or more Routing Groups.
09
The Exchange Instant Messaging Service is being replaced by the Microsoft Office Real-Time Communications
(RTC) server. It is no longer a component of the Exchange Server. For more information, see
http://www.microsoft.com/office/preview/rtcserver/.
10
What is OMA?
Outlook Mobile Access and Exchange Server ActiveSync features, formerly found in Microsoft Mobile
Information Server 2002, are now built-in with all Exchange Server 2003 Standard installations.
Complementing the Outlook 2003 and Outlook Web Access mobile improvements, Outlook Mobile Access and
Exchange Server ActiveSync help enable secure corporate e-mail on a range of mobile devices including
browser-based mobile phones, Microsoft Windows Powered Pocket PC, and Microsoft Windows Powered
Smartphone devices.
Adding this functionality to the core Exchange Server 2003 product reduces the need to deploy additional
mobile server products in the corporate environment, thus lowering the total cost of ownership.
11
1. Opportunity for Server Consolidation From Exchange 5.5 and Exchange 2000 because you can get more
mailboxes on an Exchange 2003 Server.
2. Better security features. The server is secure by default and has added things like automatic logoff for
an inactive OWA session, Connection filtering, and has more junk mail features like real-time blacklists.
3. Availability enhancements such as End-to-End Outlook Monitoring, Improvements in ESM, Mailbox
Recovery Center, and a Recovery Storage Group.
4. Increase in Mobile device support for Pocket PC’s, Pocket PC Phones and Microsoft Windows®-powered
Smartphones.
12
What are the differences between Exchange 2000 and Exchange 2003?
Move log files and queue data using Exchange System Manager
13
What is the difference between Exchange 2003 Standard and Exchange 2003 Enterprise editions?
Standard Edition
16 GB database limit
Enterprise Edition
Clustering
X.400 Connectors
Database snapshot
AirMAPI
Windows Server 2003 provides significant enhanced functionality that Exchange 2003 takes advantage of:
Active Directory
Windows provides Active Directory, upon which Exchange depends for user information, mail routing
information, user authentication, and LDAP read and write functions.
SETUP/UPGRADE
01
Can I upgrade from the evaluation edition of Exchange 2003 Enterprise Server to the RTM standard
version of Exchange 2003 Server?
No this is technically a downgrade from enterprise to standard. You can only upgrade the evaluation version
of Exchange 2003 Enterprise to Exchange 2003 Enterprise RTM.
03
How can you tell how many days remain until the evaluation copy of Exchange 2000 Server expires?
The Exchange Server Setup Progress Log includes the date on which the Exchange server was installed. Take
the difference between that date and today’s date and subtract it from 120 to determine how many days
remain in your evaluation.
04
No. Install a full version of Exchange 2000 Enterprise and you can continue to use your existing databases.
05
I plan to run Exchange in a hosted environment, where can I find information on how to configure my
Exchange server to host multiple companies
06
The EXIFS (M: drive) feature has been disabled by default. If the feature is still needed, it can be assigned to
an available drive letter with a registry setting.
07
NO. Windows 2003 uses IIS 6.0, which has been re-engineered to keep up with best practices and industry
standards. Windows 2003 has an IIS 5.0 compatibility mode, however, it is not compatible with Exchange 5.5
or Exchange 2000. Therefore, neither Exchange Systems are compatible with Windows 2003.
08
Can I run Exchange 2000 with an AD infrastructure with Windows 2003 DC’s?
YES, all exchange versions will run in an AD 2003 environment. Exchange 2000 will benefit from some of the
new features in AD 2003 and Exchange 5.5 has an ADC specifically for an Exchange 5.5/ AD 2003
environment. If AD 2000 is upgraded to AD 2003, the ADC will need to be upgraded also.*
09
NO. Microsoft will not support any deployment of Beta 2 into a production environment. Their official
position is, “Exchange 2003 Beta 2 should not be deployed in a production environment. You can deploy
Exchange 2003 Beta 2 in a test environment only.
10
Can I upgrade Exchange 5.5 in place to Exchange 2003?
NO. In place upgrades to Exchange 2003 must already be Exchange 2000 SP3 and Windows 2000 SP3 or later.
The only upgrade paths from 5.5 to 2003 are; an in place upgrade to Exchange 2000 then an in place upgrade
to Exchange 2003 or the leap frog migration which requires another server.
11
Since Exchange 5.5 can not be upgraded in place, The Active Directory should be upgraded to AD 2003, setup
the new ADC and then install a new Exchange 2003 server. Then move users from 5.5 to 2003.
12
The Exchange Instant Messaging Service is being replaced by the Microsoft Office Real-Time Communications
(RTC) server. It is no longer a component of the Exchange Server.
13
What are the Supported FE/BE scenarios? (i.e. E2003 FE with E2k BE etc.)
It is not sufficient to simply upgrade front-end servers to Exchange 2003 for users to get the new interface.
Interface matrix
Ability to Reply and Forward to Messages and Posts in Public Folders is only enabled when the client is using
a front-end server. Forms-based authentication (FBA) is functional for deployments where the FE is Exchange
2003, but the mailbox is still on Exchange 2000. However, session timeouts are handled much better if the
BE are also Exchange 2003
14
Client
Server-side
When used with the Microsoft Windows Server 2003 RPC Proxy Service and Exchange 2003, Outlook 2003
clients can connect simply using HTTP or HTTPS, thereby reducing the need for virtual private networks
(VPNs) or dial-up remote access. If remote users only need to gain access to corporate messaging
information, your IT department may not need to deploy VPN infrastructure. VPN-less access reduces costs
and provides for increased security by ensuring that remote Outlook users don’t need access to the entire
network.
15
Windows 2000 SP3 applied to all DCs, GC, and all (future) E2K2 servers, or Windows 2003.
16
I’m running Exchange 5.5 and would like to upgrade to Exchange 2003. Can I upgrade directly?
No. The only supported upgrade in place is from Exchange 2000 SP3 or later. You would need to first upgrade
your Exchange 5.5 server to at least Exchange 2000 SP3 and then upgrade in place to Exchange 2003.
Another option is to exmerge out your current users and exmerge them into an Exchange 2003 server. And
the only other option is called the leap frog migration. You configure the Active Directory Connector (ADC)
for Exchange 2003 between the Active Directory and Exchange 5.5 Directory Service. Install a new Exchange
2003 server into the enterprise and move the Exchange 5.5 users to Exchange 2003.
17
Can I rename or move the default groups created by Exchange during domainprep and forestprep?
19
The minimum practical hardware requirements in our experience are 1.25 times the disk space one would
allocate under Exchange 2000, 1GB RAM (4GB minimum if the Exchange server also serves any other
function) and the fastest processor(s) you can afford.
20
Am I better off with one really fast processor or two somewhat slower processors?
You’re better off with two really fast processors. But, with all other things being equal, two processors are
better than one with Exchange 2003. In most instances, a 2-processor machine would be preferable.
21
No. Only a single E2K3 organization can exist within a single forest. Delegation of administration within the
organization can be accomplished using OUs in AD and Administrative/ Routing Groups in the Exchange
system manager.
22
No. All domains in a forest share a common schema and the Exchange organization exists within this
configuration naming context. The GC, which provides the Global Address List is populated only with items
within the forest
23
A partial list of the ports your Exchange server might use is included below
25 SMTP
53 DNS
80 HTTP
88 Kerberos
102 X.400
110 POP3
119 NNTP
135 RPC
143 IMAP4
389 LDAP
691 LSA
1503 T.120
1720 H.323
1863 – MSN IM
3268 GC
3269 GC (SSL)
6667 IRC/IRCX
A: Do Not delete the Default Domain Policy or Default Domain Controller Policy in your Active Directory.
The Exchange domain prep operation targets a policy with GUID 6AC1786C-016F-11D2-945F-00C04fB984F9 for
its operations. If it doesn’t find it, domain prep will fail.
ADMINISTRATION
01
The EXIFS (M: drive) feature has been disabled by default. If the feature is still needed, it can be assigned to
an available drive letter with a registry setting.
02
03
When it is ready
04
In Exchange 2003, there is a new feature called the “Recovery Storage Group” (RSG). This is a special
instance of ESE (a 5th instance) which can be spun up to provide:
a. Item/Folder/Mailbox level restore without the need for a spare server
b. “Dial tone” (blank mailbox) support if you lose a database and need to get the users quickly up and
running for send/receive
To create the RSG, go into Exchange 2003 ESM, right-click on your server object and choose to create a new
Recovery Storage Group.
Once the RSG exists, you can add a database to it (any MDB from any Storage Group from any server inside
the same Admin Group). Then, use NTBackup or similar to restore a backup into the RSG. Now, you can use
ExMerge to extract the data from the RSG and merge it into the production database (for scenario a.), or you
can swap the RSG-restored database for the temporary production database (for scenario b).
05
Under Exchange 5.5 I couldn’t restore a single mailbox without 3rd party products. With Exchange 2003,
is it any easier to restore a single mailbox or back up a single mailbox?
Yes and no. Under Exchange 2003, a mailbox is not deleted immediately when a Windows account is deleted.
Although restores have been greatly improved with the new Recovery Storage Group (RSG) and the Volume
Shadow Copy Service, there is no built in mechanism for backing up a single Exchange mailbox. This would
still require a 3rd party brick level backup utility.
06
Can I back up the EXIFS drive using NT Backup or another backup application?
You can, but you will be sad. Do NOT back up the EXIFS drive of an Exchange 2003 server. It can result in
messages and attachments being inaccessible via the Outlook client.
07
How can I prevent a user from sending and receiving Internet mail?
2. Create a recipient policy that gives them a fake SMTP address. i.e. @fake.domain. Leave the X400
address alone so they can receive internal mail.
3. Drill down through Routing Groups > Group Name > Connectors > SMTP internet connector(s), choose its
properties. Choose the Delivery Restrictions tab, and under “reject”, add this group. Do this for each
connector.
Active Directory Users & Computers – Used to create users, distribution groups and contacts.
Exchange System Manager – Used to manage the Exchange Server, create address lists, recipient policies,
and now does some user level actions…
09
No, the property sheets of the 2003 servers will appear as read-only. You should avoid using Exchange 2000
ESM in environments where Exchange 2003 is installed. Not only will you not be able to access new Exchange
2003 features, but there is also the risk of damage to new objects that Exchange 2000 does not understand.
If you must continue to use Exchange 2000 ESM, apply the latest Exchange 2000 SP3 roll-up to your Admin
workstation(s) – http://microsoft.com/downloads/details.aspx?FamilyId=E247C80E-8AFA-4C2A-96B3-
F46D1808C790&displaylang=en
The roll-up includes support for the msExchMinAdminVersion attribute (also known as ESM versioning).
Essentially, each Exchange object in the AD is stamped with a minimum admin version. If ESM detects that
the data value is greater than the version of ESM running, it will not allow edits to that object.
10
Can I use Exchange 2003 tools to manage Exchange 5.5 and Exchange 2000 Servers?
Yes, with the exception of the following Exchange 2000 components; Key Management Server, Exchange
Instant Messaging, Chat, MS-Mail / Schedule+ / DirSync / cc:Mail Connectors
11
I created a user in AD Users and Computers, but in the Exchange system manager it doesn’t appear
under Mailbox Store | Mailboxes. What did I do wrong?
Probably nothing. A mailbox will not appear under Mailbox Store | Mailboxes until either someone has logged
into the mailbox or the mailbox has received a mail message. Some administrators send a welcome message
to a mailbox shortly after it has been created, which would cause it to appear.
12
I created a secondary Public Folder Hierarchy, but only the original public folder hierarchy appears in
Outlook.
Current versions of Outlook only support a single public folder hierarchy. Secondary Public Folder hierarchies
can be accessed with the web.
13
In Exchange 5.5, I could have multiple mailboxes associated with a single user account. How do I do that
in Exchange 2003?
Exchange 2003 requires a user object for each mailbox. You can create a disabled user object, associate a
mailbox with it, and then grant another user object ‘receive as’ and ‘send as’ permissions to that mailbox.
14
‘Receive as’ allows a user object to open a mailbox. ‘Send as’ allows a user to send out a mail message as
the mailbox that has been opened.
15
First, add the address or domain you wish to filter to the Filtering Tab of the Message Delivery Global
Settings. Next, you need to apply the filter to the SMTP virtual server you wish to filter. (Administrative
Group | Server | Protocols | SMTP | <SMTP Virtual Server> | Properties | Advanced | <select the IP address
for which you wish to enable filtering> | Edit | Apply Filter). Normally, you would only want to apply
message filtering to the border SMTP servers (servers that communicate directly with External servers).
16
I’ve created more than one address list. Which list will users see for their GAL?
The following criteria are used when determining what a client will see for the Global Address List.
17
18
Is Single Instance Storage maintained when moving users between servers | storage groups | databases?
Yes…
19
In my native E2K3 organization is there any requirement for RPC connectivity between servers?
20
1. Messages can be archived on a per store basis by enabling the option on the general properties tab of
the Mailbox Store in the Exchange System Manager.
2. Use an event sink (either write your own or use the simple one provided by Microsoft and described in
“Archive Sink Readme.txt”
Why when I try to add an additional mailbox store do I receive the following error? This storage group
already contains the maximum number of stores allowed. ID no: c1034a7a
You are running the standard version of Exchange 2003 which is limited to a single 16GB private information
store.
22
How do I get the Exchange Advanced Tab in Active Directory Users and Computers?
Open Active Directory Users and Computers. Click on the View menu item at the top of the application.
Select “Advanced Features” on the menu list. When you open a property page for an Active Directory object
that has a mailbox associated with it, you will now see the “Exchange Advanced” tab at the top.
23
How do I control the format of the addresses before the @ sign in a recipient policy?
You can use the following variables: %g Given Name, %s Surname, %i initials in the recipient policy.
Examples:
%g.%[email protected] = [email protected]
%1g%[email protected] = [email protected]
%g%[email protected] = [email protected]
24
How do I make Exchange automatically send a welcome message to all newly created users?
There is nothing in the product that will do this. You can create a WELCOME.MSG that you deploy with
Outlook, but that only applies the first time Outlook is opened after creating a new profile. Otherwise, you
could script mailbox creation and send a message at the end of the script.
25
Is there any way to append a text message to all out bound email for Exchange 2003?
On a single Exchange server deployment, there is no 100% reliable way to accomplish this with an SMTP
Transport Event Sink; even though KB273233 suggests that creating a second SMTP Virtual Server works.
However, at startup the Exchange Information Store binds to the SMTP Virtual Server that starts first and you
can not rely on the routing of the mail from SMTP VS 1 to SMTP VS 2 as the KB273233 proposes. Also note
that under special circumstances the database can become corrupted if you use an SMTP Transport Event
Sink to manipulate outgoing (MAPI) message contents. This is currently under investigation by Microsoft and
a QFE to prevent the store corruption is under development. ****
How do I add a disclaimer to outgoing SMTP messages in Visual Basic/Visual Basic Script?
You can do it, however, see there are limitations. It reliably works only on a border server, which can be
either a Windows 2000 or 2003 SMTP Server with or without Exchange 2000/2003 installed. For more
information, see KB317327 and KB317680
27
How can you tell the exact version of Exchange you are running?
Exchange 2000
Exchange 2003
28
How To: Add a Disclaimer to Outgoing SMTP Messages in Visual Basic – KB317327
29
Outlook 2003 offers basic resource booking functionality through Direct Booking. For more information refer
to “Direct Booking of Resource Without a Delegate Account”
There are 3rd party products such as Exchange Resource Manager and AutoAccept Sink for Exchange that
will automatically accept/decline meeting requests for conference rooms and other resources.
31
How do I find an SMTP mail address in Active Directory if Active Directory Users and Computers tells me
it is in use when I try to create a new user?
Either open Outlook to create a new message with that SMTP address and hit “CTRL+K” to resolve it, or use
a Windows Scripting Host script to find it. For the latter, see
http://www.cdolive.net/download/adusermanagement.zip (look for FindUserWithADSI.wsf and
FindUserWithCDO.wsf)
32
This tab is not enabled by default. For instructions on how to enable it see KB264733
33
For Exchange 2000 public folders, you can follow the instructions in this article KB256131. But with
Exchange 2000, however, any time a new server is added to the organization, these permissions will be
reset.
In Exchange 2003 these permission are restricted by default so to install Exchange 2003, you will
automatically restrict them.
“Allow create top-level public folder access control entry for everyone” permissions and “allow anonymous
logon from the organization container” permissions are removed during the installation of Exchange
2003.*****
34
This problem has been fixed in AN Microsoft Exchange 2000 Server Post-Service Pack 3 MDB patch. For more
information see KB327378
35
You need to create the Disable MAPI Clients registry value to disable MAPI client access. For more
information, see KB288894
37
How do I disable the “Automatically update e-mail addresses based on recipient policy” on all users or
contacts?
Migration
01
Can I use Exchange 2003′s OWA to access a mailbox on an Exchange 5.5 or Exchange 2000 server?
Yes and No. Exchange 2003 can access a 2000 back-end server however, it will remain the same as Exchange
2000 OWA. As for Exchange 5.5, the enhanced OWA is built directly into the store technology and only a
mailbox residing on an Exchange 2003 server can be accessed using the enhanced OWA interface. Nice try,
though.
02
Can I use Exchange 5.5′s OWA to access a mailbox on an Exchange 2003 server?
Yes. But you will not get the look and feel or the added features from the 2003 servers.
03
How do I remove the ADC after moving all of my users to an Exchange 2003 server?
First, you need to use the Exchange 5.5 Admin program to delete the directory replication connectors (Org |
Site | Configuration | Connections). Once you have deleted the connections, you need to be logged on with
an account with Schema Admin privileges to delete the ADC connector.
04
There is no hard and fast rule in this regard. Some potential guidelines include:
Transport
01
All the system queues like the failed message retry queue, DNS messages pending submission, and messages
queued for deferred delivery are now exposed to enhance trouble shooting.
02
Is there any way to append a text message to all out bound email for Exchange 2003?
On a single Exchange server deployment, there is no 100% reliable way to accomplish this with an SMTP
Transport Event Sink; even though KB273233 suggests that creating a second SMTP Virtual Server works.
However, at startup the Exchange Information Store binds to the SMTP Virtual Server that starts first and you
can not rely on the routing of the mail from SMTP VS 1 to SMTP VS 2 as the KB273233 proposes. Also note
that under special circumstances the database can become corrupted if you use an SMTP Transport Event
Sink to manipulate outgoing (MAPI) message contents. This is currently under investigation by Microsoft and
a QFE to prevent the store corruption is under development. ****
There are 3rd party products that will do this too.
03
How do I add a disclaimer to outgoing SMTP messages in Visual Basic/Visual Basic Script?
You can do it, however, see there are limitations. It reliably works only on a border server, which can be
either a Windows 2000 or 2003 SMTP Server with or without Exchange 2000/2003 installed. For more
information, see KB317327 and KB317680
04
Yes, in the new Queue Viewer in the Exchange 2003 System Manager.
05
Exchange 2003 allows you to change the location of queue directories for SMTP virtual servers and X.400.
The Directions are in the document entitled “Exchange Titanium Getting Started Guide”
06
DNS messages pending submission – Contains delivery status notifications (DSN), also known as non-delivery
reports that are ready to be delivered by Exchange. The Delete All Messages (no NDR) and Delete All
Messages (NDR) functions are unavailable for this queue.
Messages queued for deferred delivery – Contains the messages marked by the client for deferred delivery or
messages simply awaiting delivery at a different time.
Failed message retry – Contains messages that have been marked as retry due to a delivery failure. This
queue also does not have the NDR functions mention in the DNS messages pending submission queue.
07
1. Create the recipient filter using the Connection Filtering tab on the Message Delivery Properties under
Global Settings.
08
09
How do I limit the maximum amount of messages the SMTP queue can hold?
10
You can do this through a registry entry. But there are two drawbacks. Once this is done, the details that are
necessary to display the notification in the preview pane are stripped, and the originator of the message
cannot use the Send Again option.
11
Submissions can be restricted to a limited number of security principles though the standard Windows
Discretionary Access Control List (DACL). This feature prevents non-trusted senders, such as unauthorized
Internet users, from sending mail to an internal only distribution list. An example of this would be an “All
Employees” distribution list which should not be available to anyone outside the company (by spoofing or
otherwise). Note Restricted distribution lists will only work on the bridgehead servers or SMTP gateway
servers running Exchange 2003.
1. Click Start, point to All Programs, point to Microsoft Exchange, and then click Active Directory Users
and Computers.
3. Right-click the distribution list for which you want to restrict submissions, and then click Properties.
5. Under Message Restrictions, under Accept messages, select one of the following options:
Click From everyone to allow anyone to send to this distribution list. This includes anonymous users
from the Internet.
Click From authenticated users only to allow only authenticated users to send mail to this distribution
list.
Click Only from to specify a select set of users or groups that can send to this group and then click Add
to specify the users or groups that you want to permit to send mail to this distribution list.
Click From everyone except to allow everyone but a select set of users or groups to send to this
distribution group and then click Add to specify the list of users or groups that you want to restrict from
sending to this distribution list.
STORE
The EXIFS (M: drive) feature has been disabled by default. If the feature is still needed, it can be assigned to
an available drive letter with a registry setting.
02
the .stm file is part of the information store database that contains the native internet formatted items. It is
used to improve the performance of the database.
03
Why does the size of the EDB file not change when I move users out of that store?
The .edb file will only decrease in size once a database defrag is performed.
04
The new ESM allows the administrator to move the log files through the GUI.
05
Yes, you can now move mailboxes through ESM grouped by mailbox store.
06
Yes, In both the clean install and upgrade from Exchange 2000 scenarios, Exchange 2003 does not present
EXIFS as drive letter M:
07
If there is still an M: drive mapped, why does the free space number look funny?
The free space number shown on the M: drive is based on the main install drive for Exchange. It is not
related to the drive space on the drives where the stores actually exist.
CLUSTERING
01
Which cluster configuration is preferred?
Scales better
02
Active/Active clustering is only supported with a 2-node cluster limited to 1900 concurrent connections.
03
Do I still have to cycle the services on fail back like in 2000 Active/Passive mode?
The Exchange services are automatically shutdown on failover so when fail back happens the services are
automatically brought back online for a clean address space.
04
Exchange 2003 and Windows 2003, Standard Edition will run up to a 4-node cluster. Exchange 2003 and
Windows 2003 Enterprise will run an 8-node cluster with at least one passive node.
05
Are there any other differences between Win2k and Win2k3 clustering?
Win2k3 Enterprise and Datacenter both support 8-node clusters. MSCS (Microsoft Clustering Services) is now
available for high availability. NLB Manager allows the administrator to configure the NLB service in a central
location thus avoiding mistakes from repetitive actions. For more information see the “Technical Overview
of Clustering in Windows Server 2003″ and “Windows Server 2003 Server Cluster Architecture”
documents.
06
VM fragmentation is when the virtual memory becomes fragmented and can prevent stores form mounting.
The 9582 event is the event that warns about this condition. For more information refer to “The Extensible
Storage Engine Database Engine Contributes to Virtual Memory Fragmentation (324118)”
ADC
01
The Active Directory Connector management console now contains an ADC Tools option. ADC Tools is a
collection of wizards and tools that help you set up connection agreements by scanning your current Active
Directory and Exchange 5.5 Directory and organization, and automatically creating the recommended
connection agreements. The following wizards are included in the ADC Tools:
Resource Mailbox Wizard This wizard identifies Active Directory accounts that match more than one
Exchange 5.5 mailbox. Using this wizard, you can match the appropriate primary mailbox to the Active
Directory account and stamp other mailboxes with the NTDSNoMatch attribute, which designates the
mailboxes as resource mailboxes. You can either make these changes online or export a commaseparated
value (.csv) file that you can update and import into the Exchange 5.5 directory.
Connection Agreement Wizard This wizard recommends connection agreements based on your Exchange 5.5
directory and Active Directory configuration. You can review the list of recommended connection
agreements and select those you want the wizard to create.
The Exchange Server Deployment Tools lead you through the process of installing Active Directory Connector
and running ADC Tools.
02
Can I use the Windows 2003 Active Directory connector with Exchange 2003?
OWA
In Active Directory Users and Computers (Advanced Features view) open the properties for the user object
and choose Exchange Advanced | Protocol Settings | HTTP | Settings | and uncheck the ‘Enable for mailbox’
check box.
03
Beginning in Exchange 2000, messages with extended characters are encoded with UTF-8, by default. For
more information see KB273615 and KB281745
04
How do I stop users from going to a bookmarked /LOGON.ASP page after conversion to 2003 OWA?
After converting from Exchange 5.5 OWA to 2000 OWA, all the users had book marked the URL of
mail.company.com/exchange/logon.asp, since in 5.5 OWA it automatically would pull the user from the root
URL into a logon page (since it used ASP) but now the user only sees the same base URL of
mail.company.com/exchange. So once the users used the book mark or in some cases the “autocomplete”
feature in IE they would be pulled to a dead address.
Right click on the /Exchange directory and using the “wizard” create a new virtual directory called
logon.asp. When it prompts where the content is located just put something like c:\inetpub\wwwroot
Once the virtual root has been created, right click it, select properties then select the tab labeled
“Virtual Directory”
Select the “A redirection to a URL” and then in the “Redirect to” URL enter /exchange/
What happens is when the user hits the virtual root of /exchange/logon.asp it pulls the user back to only
/exchange*
05
Outlook Web Access user credentials are now stored in a cookie. When the user logs out of Outlook Web
Access, the cookie is cleared and is no longer valid for authentication. Additionally, by default the cookie is
set to expire automatically after 20 minutes of user inactivity. See Logon Modifications for OWA Users for
the instructions.
06
Exchange 2000 SP2 introduced the concept of OWA segmentation. This is where you can selectively
enable/disable certain features in the web client. Exchange 2003 extends the segmentation options found in
Exchange 2000. You can either set global (per server) segmentation via a registry parameter, or set the
msExchMailboxFolderSet attribute on user objects. A bit mask determines the functionality available to the
user.
07
OMA
01
In a mixed Exchange environment, you must use Exchange 2003 for both the front-end and back-end servers
to gain access to mailboxes through Outlook Mobile Access (OMA) and Exchange ActiveSync. For mailboxes on
Exchange 5.5 and 2000, you need to deploy Microsoft Mobile Information Server.
02
What is OMA?
Outlook Mobile Access and Exchange Server ActiveSync features, formerly found in Microsoft Mobile
Information Server 2002, are now built-in with all Exchange Server 2003 Standard installations.
Complementing the Outlook 2003 and Outlook Web Access mobile improvements, Outlook Mobile Access and
Exchange Server ActiveSync help enable secure corporate e-mail on a range of mobile devices including
browser-based mobile phones, Microsoft Windows Powered Pocket PC, and Microsoft Windows Powered
Smartphone devices.
Adding this functionality to the core Exchange Server 2003 product reduces the need to deploy additional
mobile server products in the corporate environment, thus lowering the total cost of ownership.
03
Device support for Outlook Mobile Access (OMA) Browse is dictated by the Device Update package installed
on the Exchange 2003 server. When you run Exchange 2003 Setup today, the DU2 package is silently installed
as part of the installation.
Approximately, every 6 months, new Device Update packages are released. This will add support for more
devices to your Exchange server.
The current Device Update package is DU4. The full list of devices and which DU package they are included
in is available here.
04
05
I have an Exchange 2003 server on a member server that I promoted to a DC, what happened to my
OMA, it no longer works?
Amongst other problems, the ASP.NET account changes which causes OMA to cease functioning.
06
You can verify Outlook Mobile Access (OMA) is functioning from a desktop machine running IE 6.0 Assuming
that SERVER1 is running Exchange 2003:
2. Enter the logon credentials for an existing mailbox which resides on server1
3. Click the OK hyperlink when you receive the warning about your device being unsupported
OUTLOOK 2003
01
Client
Server-side
When used with the Microsoft Windows Server 2003 RPC Proxy Service and Exchange 2003, Outlook 2003
clients can connect simply using HTTP or HTTPS, thereby reducing the need for virtual private networks
(VPNs) or dial-up remote access. If remote users only need to gain access to corporate messaging
information, your IT department may not need to deploy VPN infrastructure. VPN-less access reduces costs
and provides for increased security by ensuring that remote Outlook users don’t need access to the entire
network.
02
03
How can I enable/disable an attribute used by the Outlook client for ambiguous name resolution
04
What are the differences in compression between Outlook 2002/2003 and Exchange 2002/2003?
The following tables illustrate how RPC compression and buffer packing works on the wire between the
Outlook client and Exchange Server.
The compression technology used between Outlook 2003 and Exchange 2003 is called XPRESS(tm) and is
based on the Lempel-Ziv (LZ-77) algorithm. This is the same technology that Active Directory uses to
perform compression of its’ RPC data when replicating between servers. All data over the size of 1 KB is
compressed, and the technology is built into both client and server; therefore the compression is full duplex.
The compression gain is dictated by the message format and attachment(s) type. Because the compression is
performed at the RPC level, all message data is compressed.
Plain text and HTML messages usually compress between 60% and 80% (on the wire saving)
Rich-text (RTF) messages usually compress up to 20% (on the wire saving)
You can enable a new logon page for Outlook Web Access that will store the user’s user name and password
in a cookie instead of in the browser. When a user closes their browser, the cookie will be cleared.
Additionally, after a period of inactivity, the cookie will be cleared automatically. The new logon page
requires users to enter either their domain name\alias and password or their full UPN e-mail address and
password to access their e-mail.
2. Expand the Protocols node under the Exchange server for which you wish to enable forms-based
authentication.
3. Expand HTTP, and then right-click the Exchange Virtual Server.
4. On the Exchange Virtual Server properties page, select the check box next to Enable Forms Based
Authentication for Outlook Web Access.
The automatic timeout is valuable for keeping a user’s account secure from unauthorized access. Although
this timeout does not completely eliminate the possibility that an unauthorized user might access an account
if an Outlook Web Access session is accidentally left running on a public computer, it greatly reduces this
risk.
Note: Cookie Authentication Timeout is available for the rich experience version of Outlook Web Access
only.
The inactivity timeout value can be configured by an administrator to match the security needs of your
organization.
Note: The default value for the cookie timeout is 10 minutes. If you want to set this value to something
other than 10 minutes, you must modify the registry settings on the server. Warning This section
contains information about editing the registry. Before you edit the registry, make sure you understand
how to restore it if a problem occurs. For information about restoring the registry, see the “Restore the
Registry” Help topic in Regedit.exe or Regedt32.exe
6. In the Value Data field, enter a value (in minutes) between 1 and 1440.