This automatic installation does not take place if you are installing on Windows 2003 though. NET framework and ASP.NET components of Windows are automatically installed. And when installing Exchange 2003 on Windows 2000, both the. Specifically, on global catalog servers, there is no need to reboot (as there was with Windows 2000) when you enable the Name Service Provider Interface for use by MAPI clients.Įxchange 2003 itself will only install on servers that are running Windows 2000 SP3 or higher. And Windows 2003 itself is smarter here, too, because it only advertises its service to act as a global catalog server when it has fully synchronized within the Active Directory environment thus, issues of latency within the environment are minimized. Bear in mind, of course, that using secure LDAP access implies that a server certificate be installed on the DCs or global catalog servers that Exchange 2003 will use. Windows 2000 SP3 domain controllers are important to Exchange 2003 for a number of reasons, not least being that they offer secure LDAP connectivity to many components of Exchange 2003, including the Active Directory Connector (ADC), the Site Replication Service (SRS), the Recipient Update Service (RUS), and DSAccess. Also note that only Windows 2003 Domain Controllers (DCs) or Windows 2000 domain controllers running Service Pack 3 (SP3) or higher can be used by Exchange 2003, and at least one of these must be available within the domain in which the Exchange 2003 server is installed. However, do note that Exchange 2000 is supported running on a Windows 2000 member server in a Windows 2003 domain controller environment. Exchange 2003 is supported by both Windows 2000 and Windows 2003, but it is very important to know that Exchange 2000 is not supported on a Windows 2003 server. The most important item to note about installing Exchange 2003 is really not about Exchange 2003 at all. Also, bear in mind the importance of using the Windows 2000 Advanced Server or Windows 2003 Enterprise editions so that you can use the /3GB boot switch for large memory Exchange servers (>1 GB). This facilitates support for clustering, multiple storage groups, and database sizes in excess of 16 GB. It is still recommended that large enterprise-style configurations use the Exchange 2003 Enterprise edition. In a nutshell, the major improvement in terms of changes between the Exchange 20 editions is the addition of front-end/back-end server functionality with the Exchange 2003 Standard edition. There is certainly no dramatic difference in the thinking that is required to design, plan, and implement an Exchange 2003 environment. Microsoft has used the expression “evolution, not revolution” in the past, and if ever there was a time to use it, that time is now for the relationship between Exchange 2000 and Exchange 2003. Kieran McCorry, in Microsoft Exchange Server 2003, Deployment and Migration SP1 and SP2, 2006 1.8 Exchange 2003 Installation Requirements
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |