“MS Exchange Server 2003 Guide and Interview Questions and Answers. Learn about Forestprep, Domainprep, DC, GC, DDNS, Exchange 2003 Routing, OMA, SETUP/UPGRADE of Exchange server, ADMINISTRATION, STORE, CLUSTERING, ADC and BASIC of MS Exchange Server 2003. This MS Exchange Server 2003 Interview Questions and Answers Guide all of you from very beginning to the advance level of Exchange Server 2003”
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.*
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.
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.
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.
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.
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
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.
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.
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.
Yes, but Windows 2000 must have SP3 loaded first.
Only if you want to horribly break your Exchange installation.
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.
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.
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.
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
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
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.
Yes.
Windows XP with Service Pack 1 + KB331320
When it is ready
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
rendc.org
Whether it is technological solutions or user-oriented innovations, We have put together for you the best sources of HR Interview Questions and Answers, Tech Ideas, and Programming Tutorials."
Get all the latest information on rendc.org
© 2022 | All rights reserved.
RENDC
welcome to www.rendc.org
