100 Updated MS Exchange Server 2003 Interview Questions Part – 2
Q – 61 What is the difference between “receive as” and “send as”?
Ans- “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.
Q – 62 In Exchange 5.5, I could have multiple mailboxes associated with a single user account. How do I do that in Exchange 2003?
Ans- 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.
Q – 63 I created a secondary Public Folder Hierarchy, but only the original public folder hierarchy appears in Outlook.
Ans- Current versions of Outlook only support a single public folder hierarchy. Secondary Public Folder hierarchies can be accessed with the web.
Q – 64 I created a user in AD Users and Computers, but in the Exchange system manager it does not appear under Mailbox Store | Mailboxes. What did I do wrong?
Ans- 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.
Q – 65 Can I use Exchange 2003 tools to manage Exchange 5.5 and Exchange 2000 Servers?
Ans- Yes, with the exception of the following Exchange 2000 components; Key Management Server, Exchange Instant Messaging, Chat, MS-Mail / Schedule+ / DirSync / cc:Mail Connectors
Q – 66 Can I use Exchange 2000 tools to manage Exchange 2003 Servers?
Ans- 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.
Q – 67 What tools are used to administer Exchange 2003?
Ans- 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
Q – 68 How can I prevent a user from sending and receiving Internet mail?
Ans- Follow the steps outlined below:
1. Create a group called InternalOnly.
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.
4. Follow the steps in KB277872, regarding Connector Restrictions.
[Now they ca not use the SMTP connector(s) to send external mail]
Q – 69 Can I back up the EXIFS drive using NT Backup or another backup application?
Ans- 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.
Q – 70 Under Exchange 5.5 I could not 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?
Ans- 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.
Q – 71 How do I configure the Recovery Storage Group?
Ans- 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).
One of the goals for the Recovery Storage Group
Q – 72 When will Exchange 2003 SP1 be available?
Ans- When it is ready
Q – 73 Do I need Windows XP to use Outlook RPC over HTTP?
Ans- Yes.
Windows XP with Service Pack 1 + KB331320
Q – 74 Exchange Group Policy Notes, what should I do?
Ans- 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.
Q – 75 What ports does the Exchange server use?
Ans- 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
* 137 – NetBIOS Session Service
* 139 – NetBIOS Name Service
* 143 IMAP4
* 379 LDAP (SRS)
* 389 LDAP
* 443 HTTP (SSL)
* 445 – NetBIOS over TCP
* 465 SMTP (SSL)
* 563 NNTP (SSL)
* 636 LDAP (SSL)
* 691 LSA
* 993 IMAP4 (SSL)
* 994 IRC (SSL)
* 995 POP3 (SSL)
* 1503 T.120
* 1720 H.323
* 1731 Audio conferencing
* 1863 – MSN IM
* 3268 GC
* 3269 GC (SSL)
* 6001 Rpc/HTTP Exchange Store
* 6002 HTTP Exchange Directory Referral service
* 6004 Rpc/HTTP NSPI Exchange Directory Proxy service/Global Catalog
* 6667 IRC/IRCX
* 6891 – 6900 – MSN IM File transfer
* 6901 – MSN IM Voice
* 7801 – 7825 – MSN IM Voice
Q – 76 Can an Exchange 2003 organization span multiple forests?
Ans- 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
Q – 77 Can I have multiple Exchange 2003 organizations in a single forest?
Ans- 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.
Q – 78 Am I better off with one really fast processor or two somewhat slower processors?
Ans- 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.
Q – 79 What are the minimum hardware requirements for Exchange 2003?
Ans- 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.
Q – 80 Can I rename or move the default groups created by Exchange during domainprep and forestprep?
Ans- Only if you want to horribly break your Exchange installation.
Q – 81 Can I install Exchange 2003 on Windows 2000 server?
Ans- Yes, but Windows 2000 must have SP3 loaded first.
Q – 82 I am running Exchange 5.5 and would like to upgrade to Exchange 2003. Can I upgrade directly?
Ans- 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.
Q – 83 What do I need in order to install Exchange 2003?
Ans- A partial list includes:
* DNS (preferably DDNS)
* Active Directory 2000 or 2003
* Permissions to update the Schema
* Hardware sufficient to run Exchange 2003
* Windows 2000 SP3 applied to all DCs, GC, and all (future) E2K2 servers, or Windows 2003.
Q – 84 What do I need to get RPC over HTTP working?
Ans- Client-side:
* Outlook 2003, Windows XP with Service Pack 1 + Q331320
Server-side:
* Exchange 2003 on Windows 2003 for FE (if FE is deployed)
* Exchange 2003 on Windows 2003 for BE
* Exchange 2003 on Windows 2003 for Public Folders
* Exchange 2003 on Windows 2003 for System Folders
* Windows 2003 for Global Catalog server
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.
Q – 85 What are the Supported FE/BE scenarios? (i.e. E2003 FE with E2k BE etc.)
Ans- It is not sufficient to simply upgrade front-end servers to Exchange 2003 for users to get the new interface.
You must upgrade back-end servers to Exchange 2003 as well
Interface matrix:
Ex2000 FE + Ex2000 BE = Ex2000 OWA
Ex2003 FE + Ex2000 BE = Ex2000 OWA
Ex2000 FE + Ex2003 BE = Not supported (AG protected)
Ex2003 FE + Ex2003 BE = Ex2003 OWA
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
Q – 86 Where is the Instant Messaging Server in exchange server 2003?
Ans- 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.
Q – 87 How should I upgrade from Exchange 5.5 to Exchange 2003?
Ans- 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.
Q – 88 Can I upgrade Exchange 5.5 in place to Exchange 2003?
Ans- 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.
Q – 89 Can I upgrade Exchange 2003 Beta 2 to RTM?
Ans- 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.
Q – 90 Can I run Exchange 2000 with an AD infrastructure with Windows 2003 DC’s?
Ans- 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.*
Q – 91 Can Exchange 5.5 or Exchange 2000 run on Windows 2003?
Ans- 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.
Q – 92 What happened to the M: drive?
Ans- 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.
Q – 93 My evaluation version has expired! Are my databases toast?
Ans- No. Install a full version of Exchange 2000 Enterprise and you can continue to use your existing databases.
Q – 94 How can you tell how many days remain until the evaluation copy of Exchange 2000 Server expires?
Ans- 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.
Q – 95 Can I upgrade from the evaluation edition of Exchange 2003 Enterprise Server to the RTM standard version of Exchange 2003 Server?
Ans- 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.
Q – 96 How can I merge multiple directories to create a unified Exchange organization?
Ans-
* Microsoft’s Meta-Directory Services (MMS)
* HP’s LDAP Directory Synchronization Utility
* CPS Systems’ SimpleSync
* ADSI (code, code code)
Q – 97 What is the difference between Exchange 2003 and Windows 2003?
Ans- Windows Server 2003 provides significant enhanced functionality that Exchange 2003 takes advantage of:
Outlook HTTP access:
IIS 6.0 and Windows RPC Proxy service in Windows Server 2003 enable communication between Outlook 2003 and Exchange Server 2003 by means of HTTP. Outlook 2003 users can synchronize directly with the server running Exchange Server 2003 over a HTTP or HTTPS connection.
Internet protocol support:
IIS 6.0 provides Exchange with its support for many common Internet access protocols that increase the flexibility of the operating system, such as HTTP, Post Office Protocol version 3 (POP3), Internet Message Access Protocol version 4 (IMAP4), and Simple Mail Transfer Protocol (SMTP).
Active Directory:
Windows provides Active Directory, upon which Exchange depends for user information, mail routing information, user authentication, and LDAP read and write functions.
Q – 98 What is the difference between Exchange 2003 Standard and Exchange 2003 Enterprise editions?
Ans- Standard Edition:
* 16 GB database limit
* One mailbox store
* One public folder store
* NEW: Server can act as a front-end (post-Beta 2)
Enterprise Edition:
* Clustering
* Up to 20 databases per server
* X.400 Connectors
Both Editions support features such as:
* Database snapshot
* OMA and ActiveSync
* AirMAPI
* Recovery Storage Group
* Exchange Management Pack for MOM
* Note:
It is not possible to in-place upgrade Exchange 2000 Enterprise Edition to Exchange 2003 Standard Edition.
Q – 99 What are the differences between Exchange 2000 and Exchange 2003?
Ans- Some features that are new in Exchange 2003 are:
* Volume Shadow Copy Service for Database Backups/Recovery
* Mailbox Recovery Center
* Recovery Storage Group
* Front-end and back-end Kerberos authentication
* Distribution lists are restricted to authenticated users
* Real-time Safe and Block lists
* Inbound recipient filtering
* Attachment blocking in Microsoft Office Outlook Web Access
* HTTP access from Outlook 2003
* cHTML browser support (i-Mode phones)
* xHTML (Wireless Application Protocol [WAP] 2.0) browser support
* Queues are centralized on a per-server basis
* Move log files and queue data using Exchange System Manager
* Multiple Mailbox Move tool
* Dynamic distribution lists
* 1,700 Exchange-specific events using Microsoft Operations Manager (requires Microsoft Operations Manager)
* Deployment and migration tools
Q – 100 Why should I go to Exchange 2003 now?
Ans- There are several reasons. A few are:
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.
Q – 101 What is OMA?
Ans- 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.
Q – 102 Where is the Instant Messaging Server?
Ans- 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/.
Q – 103 How does an Exchange 5.5 site compare to an Exchange 2003 Routing Group or Administrative Group?
Ans- 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.
Q – 104 What is a mixed mode Exchange environment?
Ans- An Exchange environment which contains Exchange 2003 or Exchange 2000 and Exchange 5.5 servers.
Q – 105 What is a border server?
Ans- 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.
Q – 106 What is DDNS and why do I need it?
Ans- 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.
Q – 107 What is a GC?
Ans- 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.
Q – 108 What is a DC?
Ans- A DC is a Windows 2000 or 2003 Domain Controller that holds active directory partitions for a domain (used for things like user authentication).
Q – 109 What is Exchange 2003 Domainprep?
Ans- Exchange 2003 Domainprep creates the groups and permissions necessary for Exchange servers to read and modify user attributes.
Q – 110 What is Exchange 2003 Forestprep?
Ans- Exchange 2003 Forestprep extends the AD schema to include Exchange specific information.