An understanding of the different combinations of Windows and Exchange Server
The different combinations of support for Exchange and Windows Server are listed here:
* Exchange Server 5.5 supports the following versions of Windows:
or Windows NT 4 Server
or Windows 2000 Server
or you can play only the data from Active Directory and Active Directory using the Active Directory Connector (ADC).
* Exchange Server 2000 supports the following versions of Windows
or Windows Server 2000 with Service Pack 1 or higher.
or depends on Active Directory.
or can be installed on a member server or domain controller.
* Exchange Server 2003 supports the following versions of Windows
or Windows Server 2003
or Windows Server 2000 with Service Pack 3 or higher.
or depends on Active Directory.
or can be installed on a member server or domain controller.
There are also a number of features in Exchange Server 2003 that are not supported when Exchange Server 2003 is installed on Windows 2000 Server:
* IPSec to secure the support of front-end and back-end clusters.
* Cross-forest Kerberos authentication
* IIS 6 features enhanced security.
* HTTP access from Outlook 2003
* SharePoint Portal Server Web
* Volume Shadow Copy feature
* Real time collaboration
The following features of Exchange Server 2003 are only available when Windows Server 2003 Enterprise Edition is being used:
* 8-node groups
* 8 way PIII Xeon processors
* Supports 8-way P4 processors XeonMP
* Mount Point Support
Planning for implementation of Exchange Server 2003
When planning a deployment of Exchange Server 2003, it is recommended that you create an Exchange Server 2003, a document that includes the following aspects of the implementation of Exchange Server 2003:
* The goals of the company.
* Documenting the design of existing Exchange.
* Determine the placement of mailboxes in Exchange Server.
* To determine the front-end servers.
* Determine Brideghead servers.
* Determine the placement of global catalog.
* Determine the number of Exchange organizations.
* Determine the number of administrative groups.
* Determine the number of storage groups.
* Determine the number of routing groups.
* Determine whether the use of mixed mode or native mode.
* Determine the following for each server
or function of each server
or recovery requirements
Redundancy or requirements
* Recipient determining policy.
* Determine the strategy to protect against viruses.
* Determine the administrative model.
* Recipient determining policy.
* Determine the policies of the system.
* To determine the control strategy for change.
* Determine the backup strategy for Exchange.
* Determine the strategy for recovery Exchange.
You should consider the possibility of building a test environment of Exchange, which should include the following:
* Creation of Exchange Server 2003 in lab tests.
* Test Design Exchange.
* Exchange of testing failover and recovery.
* Evidence of the operations of e-mail.
* Test of email features.
When it comes to complex environments, multiple domains, the factors listed below should be considered:
* Security Groups must be created for each administrative function. The appropriate members to be added to these security groups.
* The creation of a deployment team, which includes messages from managers and administrators of Active Directory. It is recommended that an administrator has permissions for Windows Server and Exchange Server 2003.
* The current design of Active Directory must be examined for weaknesses before installing Exchange.
* Before you install Exchange Server 2003, attempts to combine the Windows domains into fewer domains
As part of its planning stage, you have to determine whether any third-party applications will be added to improve its implementation of Exchange:
* Virus Scan
* Spam filtering
* Fax Software
* Backup
Exchange Server 2003 Hardware Requirements
The minimum hardware requirements for installing Exchange Server 2003 are listed here:
* Processor – Pentium 133
* Operating System – Windows Server 2000 with Service Pack 3
* Memory – 256 MB RAM
* Disk space – 200 MB on system drive
* Disk space – 500 MB on the partition that is used to install Exchange.
* File System requirements: Exchange Server 2003 must be installed on an NTFS partition. This includes the following partitions and files:
system or partition
or partition that is used for the following:
+ Exchange database files
+ Exchange transaction logs
+ Exchange binaries
+ All other Exchange files
* Drive – CD-ROM
* Screen – VGA at least
Recommended hardware requirements for a server configuration below:
* A hard disk system which is common to the cluster nodes.
* A local disk on each node for the operating system and any program files.
* LAN dedicated link between the cluster nodes.
* TCP / IP between the group and customers.
The hardware requirements for installing Exchange Server 2003 are listed here:
* Processor for Exchange Server 2003 Standard Edition – Pentium III 500
* Processor for Exchange Server 2003 Enterprise Edition – Pentium III 733
* Operating System – Windows Server 2003
* Memory – 512 MB RAM
* Disk space – 200 MB on system drive
* Disk space – 500 MB on the partition that is used to install Exchange.
* File System requirements: Exchange Server 2003 must be installed on an NTFS partition. This includes the following partitions and files:
system or partition
or partition that is used for the following:
+ Exchange database files
+ Exchange transaction logs
+ Exchange binaries
+ All other Exchange files
Use separate physical disks for the exchange of binary files, database files of Exchange and Exchange transaction logs.
* Drive – CD-ROM
* Display – SVGA at least
Windows services and components required for Exchange Server 2003
Due to the integration of Windows and Exchange, there are a number of Windows Server 2003 components and services that must be installed and enabled before you can install Exchange Server 2003.
These Windows services are:
* Simple Mail Transfer Protocol (SMTP)
* Network News Transfer Protocol (NNTP) service
* World Wide Web service
* Microsoft ASP.NET
* In Microsoft. NET Framework
To install the first Exchange 2003 server, the infrastructure of Active Directory and DNS must be working, and working properly and efficiently, ie without errors. Exdeploy can be used to scroll through all the necessary pre-installation health checks before running Exchange Server 2003 Setup.
Impact of Windows to install Exchange Server 2003
Because Windows is the basic infrastructure for an installation of Exchange Server 2003, a number of factors to be taken into account before proceeding with your installation of Exchange Server 2003. These factors are:
* Placement of Global Catalog The Global Catalog server must be available to the recipient’s address to be resolved when the messages are directed by users. The global catalog maintains the mailing list of a user who used to address a message.
When planning the placement of global catalog, consider the following recommendations:
o For each Active Directory site that has an Exchange 2003 server, you must have at least one global catalog server.
For large sites or Active Directory, you must have at least two global catalog servers to provide redundancy.
Only for models or Active Directory domain, you should consider making all domain controllers global catalog servers.
o To optimize performance, place the global catalog server close to customers so that the mailing list of quick access is guaranteed.
o To reduce the overhead of having done with the global catalog servers in each Active Directory site, make sure the design of your Active Directory site is solid and optimized.
or you can use the Replication Monitor in Active Directory (ReplMon) utility to help determine the number of global catalogs are required in the Active Directory forest.
* Mixed or Native mode Windows: In mixed mode, mailboxes can not be moved between administrative groups. Servers in the same administrative group to reside in a routing group. Native mode should be used when not using any previous versions of Exchange Server. In native mode, routing groups can include many of the administrative groups of servers. None of the above limitations of earlier versions of Exchange are applicable in native mode. It is impossible to switch from native mode to mixed mode.
* Use the type of group: Group could become a major planning and design if you are running multiple domains in Active Directory in Windows 2000 or Windows 2003 Active Directory environments environments.
A few major changes with respect to groups that are listed here:
or distribution lists used by the version of Exchange 5.5 has been replaced by groups in Windows 2000 Exchange Server 2003.
or distribution lists used by the Exchange 5.5 version has been replaced by distribution groups in Active Directory.
or a Windows 2000 or Windows 2003 distribution group is identical to the version of Exchange 5.5 distribution list, except that no permits be allocated an access control list.
Some important factors affecting how the visibility of the group types are listed here. Visibility refers to the ability of users to see the domain of belonging to a group:
Local or Group Domain: Domain of the members does not appear in the global catalog. This means that users can only see one domain belonging to the domain local groups for their own specific domain. While they may see the group entry in the Global Address List (GAL) for the domain local groups from different areas, can not see details of the membership.
or global group: members of domain does not appear in the global catalog. This means that users can only see one domain membership of global groups from its own specific domain. While they may see the group entry in the Global Address List (GAL) for the global groups from different domains, you can not see details of the membership.
Universal or group members domain appears in the global catalog. This essentially means that users can view the group members, irrespective of the location of the group.
You need to define security groups so that you can assign permissions for the sharing of resources, calendars and public folders. A security group is a collection of users who have the same permissions to resources and rights to perform certain system tasks. These are the groups that are assigned permissions to its members may have access to resources. Security groups, thus eliminating the need for an administrator to assign permissions to individual users. Users who need to perform certain tasks can be grouped into a security group and then assign permissions to perform these tasks. Each user is a member of that group would have the same permissions. In addition, any email sent to a security group is received by each member of that group.
Different areas of the group make it possible for groups to be used in different ways to assign permissions to access resources. The scope of a defined place in the network where the group will be used or is valid. This is the degree to which the group will be able to reach through a domain, the domain tree or forest. The group will also determine what users can be included as members of the group.
With the local domain, the domain functional level set to determine which members can be included in the domain local group.
Mixed or Windows 2000: user accounts, computer accounts and global groups from any domain can be added as members of the group.
Native or Windows 2000 / Windows Server 2003: user accounts, computer accounts, global groups and universal groups from any domain can be added as members of the group. You can also add other domain local groups in the same domain as the group members.
Global groups, the domain functional level for the domain determines which members can be included in the global group.
Mixed or Windows 2000: Only user accounts and computer accounts in the domain that the group was created, it can be added as members of the group.
Native or Windows 2000 / Windows Server 2003: user accounts, computer accounts, global groups and domain where the group was created, it can be added as members of the group.
Universal groups of user accounts, computer accounts, global groups, universal groups from any domain in the Active Directory domain tree or forest can be defined as members. This basically means you can add members from any domain in the forest to a group of Universal. Universal groups are not available when operating in Windows 2000 mixed domain functional level domain.
* Extending the Active Directory schema: One of the first steps you need to carry out an implementation of Exchange Server 2003 is to expand or update the Active Directory schema. The Active Directory schema defines what types of objects can be stored in Active Directory. It also defines what the attributes of these objects. The schema is defined by two types of objects or metadata schema. Class of objects to define the outline of objects that can be created and stored in Active Directory. Schema information on the attributes of the class schema object when creating a new class. Attribute schema objects provide information about classes of objects. The attributes of an object is also called object properties.
Some other elements associated with the Active Directory schema are:
or derived class to define the way for the formation of new classes of objects using the object classes.
Scheme or rules: The Active Directory directory service running a set of rules in the Active Directory schema to control the way in which classes and attributes are used, and what kinds of values and attributes can include. Outline of the standards are organized into the structure regulation, syntax rules, and content rules.
Rules and Structure: The structure of Active Directory in the rule is that an object class can only take classes directly above him. These classes are called Possible Superiors. Structure of the rules prevent you from placing an object class in an inappropriate container.
The syntax rules or to define the types and ranges of allowed values for attributes.
o The rules dictate the content of what attributes can be associated with a particular class.
Prior to extending the Active Directory schema, consider the following:
or you have to extend the Active Directory schema on the server, assuming that the schema master Flexible Single Master Operations (FSMOs paper.
To find the server configured as the schema master,
1. Open the Active Directory schema of MMC.
2. Right-click the Active Directory Schema.
3. Select Operations Master to view the server schema master.
o To extend the schema, the service account being used must meet the following requirements:
+ Member of the Schema Admins group.
+ Member of the Enterprise Admins group.
Note that or to extend the Active Directory schema, there is a replication of Active Directory include the following components:
+ Databases Active Directory domain
+ Global Catalog Information
To extend the Active Directory schema, you’ll have to run ForestPrep. ForestPrep extends or updates the Active Directory schema so that the necessary classes of 2003 and the Exchange attributes are added.
* Preparation of the Active Directory domain: Before you install Exchange Server 2003, you have to prepare the Windows 2000 domain or Windows Server 2003 that will be used to host Exchange 2003 servers. The account that is used to prepare you running DomainPrep domains, you must be a member of the Domain Admins group in the specific domain. DomainPrep creates the necessary Active Directory groups and permissions in Exchange Server 2003 that will change.
DomainPrep must be run on each of these areas:
* Forest root domain.
* In every domain that will host Exchange Server 2003.
* In every domain that will host Exchange mailbox-enabled objects. If the domain hosts an Exchange Server 2003 is irrelevant.
Changes to the domain when running DomainPrep listed here:
* The global security group, Exchange Domain Servers, is created.
* The local security domain, Exchange Server Enterprise, is created.
* The Domain Servers group is added to the Exchange Enterprise Servers group in Exchange.
* For the domain controller is used for the Recipient Update Service, the necessary permissions are assigned.
Before starting to install Exchange Server 2003, verify that the installation of the following preparations have been produced:
* Use the Services applet to verify that IIS, NNTP, SMTP, and WWW services are installed and running.
* Check that the wood was prepared, that the Active Directory schema has been extended.
* Check that the domain was prepared.
* Check all the log files for errors.
Exchange Server 2003 Service account requirements
It is recommended that the service account you use to install Exchange Server 2003 is a dedicated service.
For the purposes of audit, this will enable you to more quickly identify the activities being carried out by the Exchange services.
To install Exchange Server 2003, the following permissions are required:
* Initially to run in a forest ForestPrep upgrade / extend the Active Directory schema – a member of the Schema Administrators group and Administrators group.
* To run ForestPrep in a forest after the first instance – Exchange Administrator permissions at the Exchange organization level.
* To run DomainPrep to prepare for installation of Exchange Server 2003 – Member of the Domain Admins group in the specific domain.
* To install the first server in the domain – Exchange Administrator permissions at the Exchange organization level.
* To install additional servers in the domain – Exchange Administrator permissions at the administrative group level. The machine account must be included in the group Exchange Domain Servers.
* To install a server with the Site Replication Service (SRS) – Exchange Administrator permissions at the Exchange organization level.
To determine which version of Exchange 2003 to use
The different versions of Exchange 2003 are:
* Exchange 2003 Standard Edition: This version of Exchange 2003 is suitable for a small organization. It also works well as a server for use in a great atmosphere and as a bridgehead server for an Exchange organization. The Exchange 2003 Standard Edition provides the core message of the server version of the software, and supports a database of up to 16GB mailboxes. Exchange 2003 Standard Edition includes support for web access, support for mobile access, and support the recovery of the server functionality.
* Exchange 2003 Enterprise Edition: This version of Exchange 2003 is ideal for organizations that need more than a single database of 16 GB to exchange messages, and for organizations that need to use the advanced capabilities and features of Exchange. Exchange 2003 Enterprise Edition can support up to 20 databases in Exchange messaging server.
The features not supported in the standard version of Exchange Server 2003 was noted here:
* Only one database is supported.
* The database can not be over 16 GB in size.
* The existence of multiple databases and storage groups are not compatible.
* The grouping is not supported.
* X.400 connectors for remote site connectivity is not supported.
To determine whether the use of multiple Exchange databases and storage groups
A storage group in Exchange refers to the logical grouping of Exchange databases that have records in common.
Exchange Server 2003 provides the following features as regards the exchange of databases:
* You can create multiple databases in a single Exchange server.
* You can share databases larger than 16 GB.
A single Exchange Server 2003 Enterprise version can support the following:
* Up to 4 storage groups per server.
* A group of storage can hold up to 5 databases.
Some advantages of applying multiple Exchange databases are listed here:
* Having multiple Exchangedatabases less translates into a reduction of time required to restore the database.
* The user can distribute the processing load across multiple databases. This results in a reduction in the loss of connectivity of mail users.
* You can define and configure different storage limits for each database.
* You can define and create a recovery storage group to which every exchange databases can be restored.
Best Practices for Exchange Server 2003 Design
Some of the best design practices for Exchange Server 2003 are listed here:
* Exchange Server 2003 must be installed on Windows Server 2003.
* A dedicated service account must be used to install Exchange Server 2003.
* You must maintain a simple design of Active Directory.
* Consider reducing the number of sites in Active Directory to reduce the number of Exchange servers that need to be installed.
* Use DNS in Active Directory domain controllers.
* When simplicity is important, the external DNS name of Active Directory.
* Where security is an important factor, the use of a DNS namespace for Active Directory.
* Use separate physical disks for the following:
Exchange files or binaries.
Exchange or database files.
or exchange transaction logs.
* You must have a local copy of the nearly global catalog servers Exchange.
* Include a backup and recovery strategy for Exchange Server in its design.
* Includes an antivirus strategy for its design of Exchange Server.
* Make sure you keep your operating system updated with Windows and Exchange regarding the installation of the latest released patches and service packs.
* Supports the client access methods should match the appropriate technology Exchange.
How to create an Exchange Server 2003 Service Account
1. Click Start, Administrative Tools, and then click Active Directory Users and Computers to open the Active Directory Users and Computers console.
2. In the console tree, expand the domain.
3. Right-click the Users container and select New and then User from the context menu.
4. When the New Object – User dialog box, enter the required information.
5. Enter the login name for the user account login in the Name field and select the domain to which the account must be associated with.
6. Click Next.
7. Proceed to set the password of the service account in the Password and Confirm Password fields, and any applicable options in the dialog for the new service account.
8. Make sure you select the Password never expires. This option is generally allowed for accounts used by Windows services or programs.
9. Click Next
10. Click Finish.
11. Right-click the service account you created and select Properties from the context menu.
12. The service account Properties dialog box opens.
13. Click the Member Of tab.
14. Click Add.
15. Proceed to add the service account to the groups listed here:
* Group Administrators schema
* Administrators group
* Domain Admins group
16. Click OK.
17. Click OK in the Properties dialog box of the service account.
How to install Windows Services for Exchange Server 2003 implementation
To install the SMTP service,
1. Click Start, Control Panel, click Add or Remove Programs.
2. Click Add / Remove Windows Components in Add or Remove Programs dialog box.
3. The Windows Components Wizard starts.
4. Click Application Server in the dialog box Windows Components, and then click the Details button.
5. The Application Server dialog box appears next.
6. Click Internet Information Services (IIS) and select the Details button.
7. Click the SMTP Service check box.
8. Click OK.
To install the NNTP service,
1. Click Start, Control Panel, click Add or Remove Programs.
2. Click Add / Remove Windows Components in Add or Remove Programs dialog box.
3. The Windows Components Wizard starts.
4. Click Application Server in the dialog box Windows Components, and then click the Details button.
5. The Application Server dialog box appears next.
6. Click Internet Information Services (IIS) and select the Details button.
7. Click the NNTP Service check box.
8. Click OK.
To install the service and ASP World Wide Web,
1. Click Start, Control Panel, click Add or Remove Programs.
2. Click Add / Remove Windows Components in Add or Remove Programs dialog box.
3. The Windows Components Wizard starts.
4. Click Application Server in the dialog box Windows Components, and then click the Details button.
5. Click the check box ASP.NET.
6. Click OK.
7. Click Internet Information Services (IIS) and select the Details button.
8. Click on the World Wide Web Service box.
9. Click OK.
To enable ASP,
1. Click Start, Administrative Tools, and then click Internet Information Services (IIS) to open the console of Internet Information Services.
2. In the console tree, select Web Service Extensions.
3. Choose ASP.
4. Click Allow for ASP.
How to run ForestPrep
1. Using an account that belongs to the Schema Administrators group and Administrators group, access to Windows Server 2003 server.
2. The place of Exchange Server 2003 installation CD into the CD-ROM.
3. Click Start, Run and then Run to access the command line.
4. Run D: \ setup \ i386 \ setup.exe / forestprep, where D is the letter of your CD-ROM.
5. The Exchange Installation Wizard starts.
6. Click Next on the Exchange Installation Wizard Welcome screen.
7. Read and accept the License Agreement End User. Click Next.
8. The Component Selection page is displayed
9. Make sure it is selected ForestPrep.
10. Provide the installation path, if necessary. Click Next.
11. Provide account information for the account that is used to install Exchange Server 2003, and then click Next.
12. After the process of executing ForestPrep, a message dialog box is displayed, indicating that the process is complete.
13. Click Finish to complete the Installation Wizard Exchange.
How to run DomainPrep
1. Using an account that belongs to Domain Admins group, access to Windows Server 2003 server.
2. The place of Exchange Server 2003 installation CD into the CD-ROM.
3. Click Start, Run and then Run to access the command line.
4. Run D: \ setup \ i386 \ setup.exe / domainprep, where D is the letter of your CD-ROM.
5. The Exchange Installation Wizard starts.
6. Click Next on the Exchange Installation Wizard Welcome screen.
7. Read and accept the License Agreement End User. Haga clic en Siguiente.
8. Cuando la página Selección de componentes aparece, asegúrese de que está seleccionada DomainPrep.
9. Proporcionar la ruta de instalación, si es necesario. Haga clic en Siguiente.
10. Proporcionar la información de la cuenta para la cuenta que se utiliza para instalar Exchange Server 2003 y, a continuación, haga clic en Siguiente.
11. Después de que el proceso ha DomainPrep plazo, un mensaje de cuadro de diálogo, indicando que el proceso se ha completado.
12. Haga clic en Finalizar para terminar el Asistente para instalación de Exchange.
Useful Links
Custom Application Services : SynapseIndia offers custom web application development services and professional website development at affordable rates to worldwide clients.
affordable search engine optimization : SynapseInteractive offering affordable SEO services with proven organic search engine optimization (SEO) techniques to increase ranking and visibility.
Web Design India : SynapseIndia is a professional web design company in India providing website designing, website development & SEO solutions for your business at affordable prices.
Professional Web Development : UK based professional web development company that specializes in development of website offering web design and development, web based development for database driven websites at affordable prices.
Manual Directory Submission : Evowebservices offering 100% manual directory submission service.