Web Hosting Exchange Server
[affmage source="chitika" results="0"][/affmage]
Opinions On Set Up Exchange Server 2003
OBJECTIVE:
Electronic messaging services within a company remains a mission essential application and its implementation is really a important component to the conduct of everyday company strategies, requirements and goals. Within the organization the company needs now include issues like the safeguard of electronic content material retention finest practices. Therefore, it’s crucial to see to it that a migration project is undertaken with a lot of care. Read this document carefully to achieve a good understanding of not only the pre-requisites but also the migration path from mixed to native mode.
The delivery of mail is actually a challenging process which includes the help of thousand of users inside the corporation environment. Affirmatively, organization guidelines and principles for the preservation of electronic mail inside the corporate physique will need to now be taken into consideration. This calls for that businesses understand ways to standardize their projects to meet not only corporate wants but also judicial demands.
The granularity of server management depends upon a company model that may sustain the rationalization of all of the mechanics of the migration project from Exchange 5.5 to Exchange 2003. It is understood that the migration will introduce several changes upon the business model. It is to be undertaken by keeping the infrastructure model and design flexible devoid of the impairment of performance.
SETUP PROCEDURES FOR THE MIGRATION:
MANAGING THE MIGRATION:
o Global Catalog server location. Need not less than one Global Catalog server in every office that has an Exchange 2003 server. This may also act as the local Domain Controller. The simplest strategy to accomplish this is to make all branch workplace DCs into GCs. Microsoft recommends a minimum of a single GC server for every four Exchange processors, not servers.
o DNS configuration. Make specific that DNSLint shows no errors, other recommended tool KILLADCGN.EXE to verify chkds Checkdisk and chkdsro (CheckReplicationOrphan objects in AD);
o Active Directory Native Mode.
You can use the EventCombMT utility (download from Microsoft). EventCombMT is aspect of the Account Lockout and Management and Lockout
O Site configuration
O Site connectors and Directory Replication connectors
O Online connectors
O Key Management Services
O Compatible backup
O Antivirus and Antispam software
O E-mail dependent applications
O Exchange 2000 instant messaging
Pre-Requisites and Precautions prior to the installation:
o Security patches (ISDS for Exchange)
o In order to preserve Exchange 5.5 Public Folder Access Control Lists (ACLs) after mailboxes or distribution lists are moved between sites the Administrator will will need to install an Exchange 5.5 DS/IS hotfix (http://support.microsoft.com/?kbid=836489) on each and every Exchange 5.5 Public Folder server prior to moving mailboxes or DLs between sites.
o Windows service packs (SP4.0 for Exchange 5.5 though Exchange 2003 is on SP2.0 this facts will need to be revised on the web page of Microsoft for the newest updates)
o Considerations – Mobile Information Server (MIS) –To preserve functionality for existing mobile users during the Exchange 2003 deployment, keep at the very least a single MIS 5.5 servers running as you migrate to Exchange 2003.
o CcMail connector — Should you are running ccMail (mainly for Lotus Mail Agents) inside the organization together with Exchange, it is time for a final transition upon the migration path to Exchange 2003.
o Backup, Antivirus, and Antispam software program compatibility problems and third party software program issues
o ADC upgrades considerations – You have to upgrade the ADC servers to Exchange 2003 ADC prior to introducing any Exchange 2003 servers into the organization. The ADC upgrade modifies the schema, so make certain that the Schema Master is available.
– Should you have an existing deployment for instance for example, Exchange 2000 that uses a distributed architecture, upgrade the front-end servers first after which upgrade the backend servers.
PRE-MIGRATION NORMALIZATION ISSUES:
O Normalize mailboxes (size sum check)
O Verify public folders permissions (permissions will affect the RUS)
OMigration Account Rights Make sure the account(s) utilized for the migration approach are given ‘Service Account Admin’ rights at the Organization, Site and Server level.
(Deployment tools)
Considering ultimate performance:
o Upgrade the existing PDC to Windows Server 2003.
o Install further Windows Server 2003 domain controllers
What is Exchange?
o Shift the domain and forest to Windows Server 2003 functional level
Network Infrastructure Considerations:
o Outages
o Remote users
o Routing groups
Costs Topology:
o Server software
o Client Access Licenses (CALs)
o Additional personnel
o Training
o Client software
Additional Networking Considerations:
Exchange is really a popular Microsoft messaging program that consists of a mail server, an e-mail plan (e-mail client), and groupware applications. Exchange e-mail is normally utilized in small business settings, most people today use Microsoft Outlook to take advantage of Outlook’s collaborative features, which include the capability to share calendars and contact lists.
Why Hosted Exchange?
o Directory service connection failures
o Inability to access public folders
o Inability to replicate public folders with legacy Exchange
Exchange serves two Purposes
• Mail Server
• Collaboration server
• Exchange will allow users to share information:
o Public folders – users can contribute and view files.
o Calendars
o coordinate meeting schedule
o set appointments
o Address books – create and quickly sustain a Global Address Book
Considering Final Networking Objectives:
o Fastest probable introduction of new features
o Maximize current hardware
ADC, DcDiag, NetDiag, AD Snapshot, Log Files, Event Viewer Security, Application and System Logs
ADC Setup will make extensive use of Net files (.html, .hta, etc.). Windows Server 2003 has a function called Internet Explorer Enhanced Security that forces a security launched wizard. Remove this feature from the server for the duration of the ADC and Exchange setup.
1.
2.
3. Click Add/Remove Windows Components
How Does Exchange work?
• Hosted Exchange (Hosted Messaging & Collaboration- HMC)
• Exchange uses RPC over HTTPS = safe connection (outlook anywhere)
4.
5.
Primary Reports and Log Files verifications:
This test reports the total number of web-sites as well as the quantity of servers in every single site.
o DSObjectSum. This utility reports the total number of public folders, distribution lists, distribution lists with hidden membership, and custom recipients.
o UserCount. This test reports the total number of recipients (users) within the organization, broken down by site.
o VerCheck. This test verifies that you have the appropriate Exchange version and service pack level on your Exchange servers.
INSTALLATION CONTROLS:
The Extending of the Active Directory Schema:
§ Will modify the Active Directory Schema to consist of new attributes and classes utilised by Exchange 2003 and also installs the top-level objects for a placeholder organization tree within the Configuration Naming Context within the Active Directory forest.
Preparing the Windows Server 2003 Domains to Support Exchange Server 2003:
/Domainprep It will prepare the domains which will host Exchange servers or mailbox-enabled users
§ This creates objects inside the Active Directory domain that represent Exchange service accounts, public folders, and groups that represent Exchange servers inside the domain as well as the enterprise.
It will configure the Recipient Update Service parameters responsible for keeping Exchange address lists up-to-date and for making proxy addresses for users based on recipient policy addressing configuration.
The object itself doesn’t obtain messages. The messages will not be stored in Active Directory. Instead, they can reside in a mailbox on an Exchange server, in a public folder, or in one more messaging system.
How these objects work:
When the correct credentials are sent to the domain controller for the user object, the contents of the mailbox become offered to the e-mail client like Outlook (in the inbox of the user).
Domainprep will develop two new groups:
a) Exchange Domain Servers
b) Exchange Enterprise Servers
1) OrgPrepCheck
Remote Procedure Call (RPC)
• RPC is a protocol that one program can use to request a service from a plan located on a different computer.
• HTTPS (Port 443) – OWA (outlook net access), OMA ( outlook mobile access),async
• Port 443 is also applied for all exchange objects (mail, contacts)
2) OrgCheck
3) PolCheck
All connections are safe
• imaps – port 993
• smtps – port 465
To validate the Forestprep and Domainprep utilities had been functionally successful. The OrgPrepCheck utility is observed via the Exchange Deployment Tools and is really a suggested way of determining whether or not it’s safe to proceed using the migration process.
OrgCheck: This test is created to verify that the Setup created the correct Exchange objects within the Configuration naming context and Domain naming context. It also will verify that the schema changes are propagated and that it can uncover a Global Catalog server inside the exact same web page as the ADC server.
PolCheck: This test queries every domain controller inside the domain to identify if the Exchange Enterprise Servers group has been given the Manage Auditing and Security Logs privileges. If the adjustments haven’t been created it really is attainable to make use of Active Directory Sites and Services to force replication to the affected problematic Domains to run OrgPrepCheck again.
Manage the (ADC) Active Directory Controller:
Do not make use of the ADC that comes on the Win 2000 or Win 2003 Setup CD. In the event you have already installed the operating method version of the ADC, eliminate it before installing the Exchange version. The ADC uses LDAP to query and update servers. The ADC shops configuration parameters in Active Directory objects known as Connection Agreements (CAs). A CA defines object kinds for the ADC to copy, the supply and target containers for the objects, a replication schedule, and credentials to make use of for producing inter-server replication connections in between sites.
Failed Over Principle: The (ADC) Active Directory Connector has the capacity to delete objects in both directories, as a pre-migration rule and precaution the data really should be stored. This failed over principle is vital for if items go wrong in the course of the migration an authoritative restore will need to be performed using the NTDSUTIL utility of the Active Directory Database.
Fail Over practices for recovery purposes during the migration:
This particular tool is going to deliver a fail over practice which will be the regular strategy to carry out database upkeep of Active Directory
- managing of single master operations
- managing of the metadata in regards to the Domain Controllers
Found in systemrootSystem32
Step 1: Before installing the ADC the Administrator have to create or decide on a user account which will be utilised to run the ADC service and handle the (CA) connection agreements.
Step 2: Permissions rights for the (DC) Domain Controller: This account needs to be added to the Administrators group within the domain if the ADC is installed on a domain controller.
Step 3: Permissions rights for a Member Server: This account requirements to be added to the local Administrators group. Must standardize the rights on both sides 5.5 Admin and 2003 server by adding the service accounts from both administrative accounts to achieve the proper credentials (service account Admin group)
Step 4: To install the ADC there are two (2) alternatives ADC Setup from the Auto Run menu, or just invoke the setup from the Exchange Deployment Tools.
Setting up Exchange in Outlook
1. Add new e-mail accounts
2. (Exchange
3. Add the server name – supplied by hosting corporation and User Name
4. add the name by which the account is going to be named.
Select the Connection Tab – Select Connect to my Exchange mailbox utilizing HTTP
6. Click on the Exchange Proxy Settings
• URL to connect to my proxy server for Exchange: offered by hosting company
• Principal name for proxy server: provided by hosting company
Step 5: Before constructing the installation of the (CA) connection agreements the Administrator will need to configure the Attribute replication, account-matching rules, diagnostic logging properties and replicating directory entries. (Very important)
Step 6: As soon as the ADC is installed with its account credentials and services it is going to be time to configure the connection agreement (CA) and to start synchronizing the Active Directory and Exchange 5.5 directories.
VERIFY THE CONNECTIVITY WITH ACTIVE DIRECTORY:
• Public Folders: Allows you to set a user to Admin status, in order that they can generate and manage public folders for shared documents in either Outlook Web Access or Outlook.
• Distribution Lists: Create a distribution checklist utilizing use a single e mail alias.
• Contacts: Create and handle external Contacts so that they can be included in a International Address Book.
• Disk Space: View/manage how much disk space is being employed by mailboxes, and order extra space as needed.
Run the Exchange 2003 SP1 version of exdeploy.exe with the following switches to test the ADC configuration.
o NT Account Migrations -Invalid User Accounts , Do not Enable the Disabled User Objects
o Multiple Mailbox Owners (NTDSNoMatch) set an exclusion standard on the account
o Active Directory Account Cleanup Wizard
o ADC and Distribution Lists – Automatic Security Group Upgrades
o Distribution List Membership
o ADC Setup Permissions – ADC Server Selection – ADC Service Account Selection
Dispositions: Can be installed on a Member Server or on the 1st Exchange 2003 Server installed.
Implementation of CA: At this point you can opt for to implement a single or far more (CA) connection agreements inside the organization. It will need to be accomplished because of the migration method for it’s going to not sustain issues of fault tolerance or load balancing. For managerial purposes of the migration installation procedures the very best practice would be to install a single ADC with one connection agreement for every Exchange 5.5 site.
Site Replication: The 5.5 Exchange Server and the installed ADC need to be on the exact same physical network segment.
If you concluded that this essay is worthwhile you should also want to be researching about Xp Wireless Network Setup and also Set Up Exchange Server.
