Electronic messaging services within a provider remains a mission important application and its implementation can be a crucial component to the conduct of everyday enterprise strategies, requirements and goals. Within the organization the organization needs now involve the safeguard of electronic content retention finest practices. Therefore, it can be essential to see to it that a migration project is undertaken with a good deal of care. Read this document carefully to achieve an excellent understanding of not simply the pre-requisites but also the migration path from mixed to native mode.
This requires that firms learn the best way to standardize their projects to meet not just corporate needs but also judicial demands.
The granularity of server management depends upon a enterprise model that will 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 many changes upon the organization model. It is to be undertaken by keeping the infrastructure model and design flexible without the impairment of performance.
SETUP PROCEDURES FOR THE MIGRATION:
MANAGING THE MIGRATION:
o Domain controller location.
o Global Catalog server location. Need not less than a single International Catalog server in every office that has an Exchange 2003 server. This also can act as the local Domain Controller. The simplest way to accomplish this would be to make all branch workplace DCs into GCs. Microsoft recommends a minimum of a single GC server for just about every 4 Exchange processors, not servers.
o DNS configuration. Make specific that DNSLint shows no errors, other suggested tool KILLADCGN.EXE to verify chkds Checkdisk and chkdsro (CheckReplicationOrphan objects in AD);
o Active Directory Native Mode.
o Replication or authentication problems. You can use the EventCombMT utility (download from Microsoft). EventCombMT is portion of the Account Lockout and Management and Lockout
Verify Current Exchange Organization Roles and Distributions:
O Exchange server version
O Site configuration
O Compatible backup
O Antivirus and Antispam software
O E-mail dependent applications
Pre-Requisites and Precautions just before 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 internet sites the Administrator will need to install an Exchange 5.5 DS/IS hotfix (http://support.microsoft.com/?kbid=836489) on just about every Exchange 5.5 Public Folder server prior to moving mailboxes or DLs in between sites.
o Windows service packs (SP4.0 for Exchange 5.5 whilst Exchange 2003 is on SP2.0 this information need to be revised on the web site of Microsoft for the most recent updates)
o Considerations – Mobile Information Server (MIS) –To preserve functionality for existing mobile users in the course of the Exchange 2003 deployment, preserve no less than 1 MIS 5.5 servers running as you migrate to Exchange 2003.
o Backup, Antivirus, and Antispam software program compatibility problems and third party software issues
The ADC upgrade modifies the schema, so ensure that that the Schema Master is available.
– For those who have an existing deployment which include for example, Exchange 2000 that uses a distributed architecture, upgrade the front-end servers very first and then upgrade the backend servers.
O Normalize mailboxes (size sum check)
O Verify public folders permissions (permissions will have an effect on the RUS)
OMigration Account Rights Make certain the account(s) utilised for the migration process are given ‘Service Account Admin’ rights at the Organization, Site and Server level.
(Deployment tools)
Considering ultimate performance:
o Domain Upgrade
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 Traffic patterns
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 common Microsoft messaging system that contains a mail server, an e-mail program (e-mail client), and groupware applications. Exchange email is usually applied in business settings, most folks use Microsoft Outlook to take benefit of Outlook’s collaborative features, including the ability to share calendars and get in touch with lists.
• No software costs (Outlook is usually included for free)
• No IT hardware costs (Exchange Server and licenses price thousands)
• Servers are maintained and backed up by hosting company
• Quick and rapidly setup with continued Technical Support
o Directory service connection failures
o Inability to access public folders
Exchange serves two Purposes
• Mail Server
• Collaboration server
• Exchange permits 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 – generate and effortlessly maintain a International Address Book
o Software compatibility failures
Considering Final Networking Objectives:
o Single mailbox-enabled account for each and every user
o Retain existing mailbox and public folder permissions.
o Fastest probable introduction of new features
o Maximize existing hardware
ADC, DcDiag, NetDiag, AD Snapshot, Log Files, Event Viewer Security, Application and System Logs
NB*: Remove Net Explorer Enhanced Security. Remove this characteristic from the server for the duration of the ADC and Exchange setup.
1.
2. Open the Add/Remove Programs applet.
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:
o DSConfigSum. This test reports the total quantity of web-sites as well as the number of servers in each and every site.
o DSObjectSum. This utility reports the total quantity of public folders, distribution lists, distribution lists with hidden membership, and custom recipients.
o UserCount. This test reports the total number of recipients (users) in the organization, broken down by site.
o VerCheck. This check verifies that you simply have the proper Exchange version and service pack level in your Exchange servers.
o NB*: The primary log file for the deployment is Exdeploy.log. It shows the outcome of each check performed by DSScopeScan.
INSTALLATION CONTROLS:
The Extending of the Active Directory Schema:
/Forestprep switch is utilized to extend the Active Directory schema.
§ Will modify the Active Directory Schema to contain new attributes and classes utilized 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:
It will configure the Recipient Update Service parameters responsible for keeping Exchange address lists up-to-date and for creating proxy addresses for users based on recipient policy addressing configuration.
NB*: Recipients are Active Directory objects that have messaging capabilities. The messages aren’t stored in Active Directory. Instead, they can reside in a mailbox on an Exchange server, in a public folder, or in yet another messaging system.
How these objects work:
Domainprep will generate two new groups:
a) Exchange Domain Servers
b) Exchange Enterprise Servers
1) OrgPrepCheck
Remote Procedure Call (RPC)
• RPC is often a protocol that a single plan can use to request a service from a plan situated on yet another computer.
• HTTPS (Port 443) – OWA (outlook web access), OMA ( outlook mobile access),async
• Port 443 is also used for all exchange objects (mail, contacts)
3) PolCheck
All connections are safe
• imaps – port 993
• smtps – port 465
OrgPrepCheck: Verifying the Organization Settings with OrgPrepCheck. To validate the Forestprep and Domainprep utilities were functionally successful. The OrgPrepCheck utility is found via the Exchange Deployment Tools and can be a suggested way of determining whether it can be secure to proceed using the migration process.
OrgCheck: This check is produced to verify that the Setup produced the correct Exchange objects in the Configuration naming context and Domain naming context. It also will verify that the schema changes are propagated and that it can come across a Global Catalog server in the identical web page as the ADC server.
PolCheck: This check queries each and every domain controller inside the domain to ascertain if the Exchange Enterprise Servers group has been given the Manage Auditing and Security Logs privileges. If the changes haven’t been made it truly is possible to create 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. These distinct versions of ADC don’t map special attributes needed by Exchange recipients and public folders. If you have already installed the operating system version of the ADC, remove it before installing the Exchange version. The ADC makes use of LDAP to query and update servers. The ADC shops configuration parameters in Active Directory objects called Connection Agreements (CAs). A CA defines object types for the ADC to copy, the supply and target containers for the objects, a replication schedule, and credentials to make use of for creating inter-server replication connections between sites.
This failed over principle is crucial for if things go wrong during the migration an authoritative restore will need to be performed with the NTDSUTIL utility of the Active Directory Database.
Fail Over practices for recovery purposes during the migration:
This specific tool is going to offer a fail over practice which is the normal method to perform database upkeep of Active Directory
- managing of single master operations
- managing of the metadata in regards to the Domain Controllers
Found in systemrootSystem32
May also perform the restore from Backups
Step 1: Before installing the ADC the Administrator will will need to produce or select a user account which will be put to use 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 inside the domain if the ADC is installed on a domain controller.
Step 3: Permissions rights for a Member Server: This account needs 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 each administrative accounts to achieve the correct credentials (service account Admin group)
Step 4: To install the ADC there are actually two (2) possibilities ADC Setup from the Auto Run menu, or simply invoke the setup from the Exchange Deployment Tools.
In Outlook >Go to Tools Select the type of mail server you is going to be connecting to. (Exchange
3. Add the server name – supplied by hosting firm and User Name
4. add the name by which the account will likely 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
(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 commence synchronizing the Active Directory and Exchange 5.5 directories.
VERIFY THE CONNECTIVITY WITH ACTIVE DIRECTORY:
Exchange Features
• Mailboxes: Allows you to create, edit and manage mailboxes. This includes setting up get in touch with facts that will make employee get in touch with info readily available inside the Global Address Book in Outlook.
• Public Folders: Permits you to set a user to Admin status, in order that they can create and manage public folders for shared documents in either Outlook Web Access or Outlook.
• Disk Space: View/manage how much disk space is being used by mailboxes, and order further space as needed.
Run the Exchange 2003 SP1 version of exdeploy.exe using the following switches to check the ADC configuration.
%pathname%exdeploy.exe /t:ADCCheck /p:%logpath% /s:
o NT Account Migrations -Invalid User Accounts , Do not Enable the Disabled User Objects
o Numerous Mailbox Owners (NTDSNoMatch) set an exclusion regular 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 it is possible to opt for to implement 1 or more (CA) connection agreements within the organization. It ought to be done mainly because of the migration procedure for it’s going to not sustain issues of fault tolerance or load balancing. For managerial purposes of the migration installation procedures the best practice is to install a single ADC with a single connection agreement for each Exchange 5.5 site.
Site Replication: The 5.5 Exchange Server and also the installed ADC will need to have to be on the identical 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.
