Moving from a Linux Mail Server and peer-to-peer network to Exchange Server 2007

[LEFT][CODE]http://www.msexchange.org/articles_tutorials/exchange-server-2007/migration-deployment/moving-linux-mail-server-p2p-network-exchange-server-2007-part1.html[/CODE]
[SIZE=3][B]
PART-1[/B][/SIZE]

In Exchange Server 2003, we were able to use the Exchange Migration Wizard to migrate from an environment running IMAP4 to Active Directory and Exchange Server 2003. A list of all steps required can be read at: [URL="http://technet.microsoft.com/en-us/library/bb123854.aspx"]How to Migrate Users and Mailboxes from an Internet Messaging System to Exchange 2003[/URL].
In this article series I intend to demonstrate how to move directly from a Linux Mail server running Postfix and POP3 to Exchange Server 2007. This scenario can be useful to small and medium sized companies that do not want to first migrate to 2003 through the Exchange Server Migration Wizard and then transition to Exchange Server 2007.
All steps shown in this article series can be changed to better fit your current scenario. Changing some steps in your deployment is not a straightforward process. A best practice for this kind of migration is to understand how your current environment runs (server side and client side) and creating a deployment lab to validate.
Our objective is: creating all users using the Linux information that we already have and gradually moving resources to the new Active Directory / Exchange Server. In the last phase we will be moving the users’ current message data to Exchange Server 2007 through Outlook 2007 deployment.
[B]Current scenario[/B]

In this article we have a peer-to-peer network where all workstations are in workgroup mode and there is a local user on each machine and all users retrieve their messages using Outlook Express from the Linux Box, as shown in Figure 01.
[IMG]http://www.msexchange.org/img/upl/untitled1204189011201.JPG[/IMG]
[B]Figure 01:[/B] Current Scenario
In our current environment all workstations are configured to use [I]srv-linux.apatricio.ca[/I] as POP and SMTP Server (Figure 02), all users have at least 2 passwords, one locally and another password to access their message in the Linux Box.
[IMG]http://www.msexchange.org/img/upl/img0031204189011201.png[/IMG]
[B]Figure 02:[/B] Configuration defined in all workstations (using pop3 and SMTP)
We can also see a normal user accessing their message through Outlook Express (Figure 03).
[IMG]http://www.msexchange.org/img/upl/img0051204189011201.jpg[/IMG]
[B]Figure 03:[/B] Using Outlook Express to send and receive messages from the Linux Box
We will be using the current information in the Linux box to create the new users in the Active Directory. This information is located in the [I]passwd[/I] file in the Linux box and it can be found at [B]/etc/passwd[/B]. In this file we will find valuable information, such as user name, name, office and phone numbers. To validate which information a user has, we can use [I]finger <user-name>[/I], as shown in Figure 04. Since we have user names and other information we can add this extra information in the new Active Directory accounts.
[IMG]http://www.msexchange.org/img/upl/img0071204189051842.jpg[/IMG]
[B]Figure 04:[/B] Gathering user information using [I]finger[/I]
[B]Note[/B]:
To change the current user’s information in the Linux box we use [I]chfn <username>[/I].
We need to create an Active Directory structure, create the same user name accounts that we already have in the Linux box, install Exchange 2007 and move all workstations into the new domain and set them up to use Exchange 2007 and Outlook 2007. In this scenario our company wants to move directly to Exchange Server 2007 and not transition between message systems. Then, our goals in this article are:

[LIST][*]Build the Active Directory from scratch.[*]Build the Exchange Server 2007 environment to be interoperable with the current client way to access the messages for a short while.[*]Configure Exchange Server to work with the current environment.[*]Move users and profiles from workgroup to domain environment.[*]radually improve the end-user experience by installing Outlook 2007 and using the MAPI protocol.[/LIST]
[B]Creating the new infrastructure [/B]

In order to prepare the prerequisites required to move between message systems we will be deploying the Active Directory and Exchange Server however the current environment will not be affected.

[LIST=1][*]Install a brand new Windows Server 2003 + Service Pack and hotfixes.[*]Create an Active Directory forest and domain called [I]apatricio.local[/I]. The old DNS namespace used by the Linux box is [I]apatricio.ca[/I] and it will be supported in the new environment.
The process to create the new Active Directory will not be covered in this article, but there is a step-by-step at [URL="http://technet.microsoft.com/en-us/library/6ef6e029-6f29-49b1-be13-cef2bbdffda1.aspx"]How to Install Active Directory on Windows Server 2003[/URL].

[B]Note[/B]:
We should use at least 2 Domain Controllers to provide fault tolerance to authentication and some network services.[*]After finishing the Active Directory deployment, we can log on using the new administrator credentials, and open the DNS management interface. We have to create a new zone using the same name that the current clients are using to resolve the services. In our scenario this is [I]apatricio.ca[/I][*]Update this zone with all hosts included in the DNS Linux box because when we change the resolution of all current workstations they must access the same services.[*]Install DHCP Server in the Active Directory. This step depends of how your current environment is defined. We can have two options:

- Workstation and servers using manual IP Address: This is the best scenario, because we just have to deploy the New DHCP server and take care that our IP range available to the new clients will not clash with the current IP Address. All Servers should be configured manually but the new IP settings must be updated.
- The Linux box has a DHCP Server: in this scenario we have to validate the current range that the Linux DHCP server is distributing, disable the service and create a range that does not clash with the current IP Address.

In both scenarios the new DHCP server must pass the correct settings to the workstations. These settings should be at least: DNS Server of the Domain Controllers, DNS suffix of our new Active Directory domain (apatricio.local).[/LIST]
At this point, our workstations should be receiving IP configuration data from the new DHCP Server and resolving hosts through the new DNS Server. The next step is the Exchange Server 2007 installation:
[B]Use Exchange Server 2007 Setup wizard to Install Exchange Server 2007 [/B]

[LIST=1][*]Install the prerequisites (.Net Framework, PowerShell and MMC 3.0 if we are not using a R2 Operating System) these items will be available in the first wizard screen.[*]After all prerequisites are done, click on [I]Step 4: Install Microsoft Exchange.[/I][*]In the Introduction page, just click on [B]Next.[/B][*]In the License Agreement, click on [I]I accept...[/I] option and click on [B]Next.[/B][*]Error Reporting. Choose your option about send the errors to Microsoft and click on [B]Next.[/B][*]Installation Type. In this article we will be using a single server, then click on [I]Custom Exchange Server Installation[/I] button, and if necessary change the location where Exchange Server will be installed. Click on [B]Next[/B].[*]In the Server role selection, select Mailbox, Hub Transport and Client Access roles and click on [B]Next[/B].[*]In the Exchange organization, define the Exchange organization name and click on [B]Next[/B].[*]Client Settings. If we are going to use Public Folder, if we will install any Outlook 2003 click on Yes. After your choice click on [B]Next[/B].[*]Readiness Checks, validate if everything is okay and click on [B]Install[/B].[*]Completion. Validate if all roles have been installed and click Finish. (Figure 05)[/LIST]
[IMG]http://www.msexchange.org/img/upl/img0091204189051842.jpg[/IMG]
[B]Figure 05:[/B] Finalizing the Exchange Server 2007 installation

[LIST=1][*]Install the latest available Service Pack.[*]Install the latest available Update Rollup (if available).[/LIST]
I am assuming that we have a single Exchange Server and we have extra steps to do in order to configure properly the new Exchange Server 2007.
First of all we have to enable this new server to send and receive messages from the Internet, we can see all steps required in the following article: [URL="http://www.msexchange.org/articles_tutorials/exchange-server-2007/migration-deployment/configuring-mail-flow-single-exchange-server-2007.html"]Configuring Mail Flow in a Single Exchange Server 2007[/URL]
[B]Note[/B]:
Do not change the settings on the firewall yet - just allow Exchange Server to send and receive internet messages.
The second step is enabling the Web Services and correct certificates in Exchange Server 2007, information about this can be found in this article: [URL="http://www.msexchange.org/articles_tutorials/exchange-server-2007/management-administration/configuring-exchange-server-2007-web-services-urls.html"]Configuring Exchange Server 2007 Web Services URLs[/URL]
[B]Migration Process – Current Status (Update #01)[/B]

We have just deployed a new environment in parallel with the current environment. There has been no effect on any of our clients. We can see an overview of what we have done so far in Figure 06.
[B][IMG]http://www.msexchange.org/img/upl/img0111204189051857.JPG[/IMG]
Figure 06:[/B] The environment is gradually changing. Now we have Active Directory and Exchange 2007 deployed
All clients should receive IP configuration data from the Active Directory DHCP Server and resolve names from the DNS server that can be found in the Active Directory. Our current zones in this new domain are [I]apatricio.local[/I] that hosts the Active Directory information and [I]apatricio.ca[/I] that was created to maintain compatibility with the legacy environment.
[B]Conclusion[/B]

In this first article we validated our current scenario and we started to create the parallel environment. Our first goal was migrating some network services to the new environment without interrupting the current clients. In the next article we will be creating the new users using the current information that we have in the Linux box.

[/LEFT]

[LEFT][CODE]http://www.msexchange.org/articles_tutorials/exchange-server-2007/migration-deployment/moving-linux-mail-server-p2p-network-exchange-server-2007-part2.html[/CODE]

[SIZE=3][B]PART-2[/B][/SIZE]

In this article we will create the e-mail Address Policy to be applied to the new users and we will create the users based on the Linux [I]passwd[/I] file.
[B]Creating the E-Mail Address Policy[/B]

We have a bunch of Linux distribution and MTA (Message Transfer Agents) out there, in this article we will move from Postfix to Exchange Server 2007. Each MTA has different configuration files but most of them use the passwd file and an alias file to gather information about the current environment. One of the pieces of information that we must know is how the current naming schema is being used. If they have the format [email]FirstName.LastName@domain.com[/email] or [email]FirstLetterFirstName+LastName@domain.com[/email], then our work will be easier because we are going to use this naming strategy in Exchange Server 2007 before creating the new mailboxes. If we don’t have a standard after creating the users we will have to validate each user to make sure that the e-mail addresses match between the environments.
Before creating the e-mail address policy we have to configure Exchange Server 2007 to accept the same external domains that we have configured in the Linux box. To configure the Accepted Domains in Exchange 2007 follow these steps:

[LIST=1][*]Open the [I]Exchange Management Console.[/I][*]Expand [I]Organization Configuration.[/I][*]Click on Hub Transport, and then click on the [I]Accepted Domains[/I] tab.[*]In Toolbox Actions, click on New Accepted Domain.[*]Add a name for the new domain and fill in the [I]Accept Domain[/I] field with the external name (Example: apatricio.ca) and click on [I]New[/I], as shown in Figure 01.[/LIST]
[IMG]http://www.msexchange.org/img/upl/img0021209047146921.jpg[/IMG]
[B]Figure 01:[/B] Adding accepted domains, all domains configured on the Linux box must be added in Exchange Server

[LIST=1][*]Click on Finish[/LIST]
Now, it’s time to create the E-mail Address policy to stamp the correct SMTP address on future users:

[LIST=1][*]Open the Exchange Management Console.[*]Expand Organization Configuration, click on Hub Transport.[*]Click on Default Policy and click on Edit at Toolbox Actions.[*][B]Introduction[/B]. Just click Next.[*][B]Conditions[/B]. Click on [I]Next[/I].[*][B]E-Mail Address[/B]. Click on Add and we will be able to set up the format of the new SMTP address that will be used by new users. Choose a format that is currently being utilized by the Linux box and select the accepted domain list choosing the domain that we have just created. Click [I]OK[/I]. See Figure 02.[/LIST]
[IMG]http://www.msexchange.org/img/upl/img0041209047146953.jpg[/IMG]
[B]Figure 02:[/B] Adding the new SMTP address format to be used in the mailboxes

[LIST=1][*][B]E-mail Address[/B]. We can add more than one SMTP format but we have to use only one as the [I]Reply Address[/I] (Figure 03). Click on [I]Next[/I].

[B]Note[/B]:
We can create more than one name schema to better fit in our current environment, it can be useful if we have more than two standards in the current environment.[/LIST]
[IMG]http://www.msexchange.org/img/upl/img0061209047146953.jpg[/IMG]
[B]Figure 03: [/B]Defining the E-mail Address policies that will be applied to the mailboxes

[LIST=1][*][B]Schedule[/B]. Accept the default values and click on Next.[*][B]Edit E-mail Address Policy[/B]. Click on [I]Edit[/I].[*][B]Completion[/B]. Click on [I]Finish[/I].[/LIST]
Now all new users will receive an SMTP address in accordance with our new E-mail Address Policy. We must make sure that the SMTP address of the current Linux users will be the same in the new mailboxes.
[B]Creating the Linux mailbox users as Active Directory mail-enabled users[/B]

We will be using PowerShell to create all Active Directory users and mailboxes, using a file that contains all user names in use by Linux:

[LIST=1][*]Copy the [I]passwd[/I] file that is located on /etc/passwd from Linux to any computer with Excel installed.[*]Rename [I]passwd[/I] to [I]passwd.csv[/I] and open it using Wordpad.[*]Click on [I]Edit[/I], [I]Replace[/I] and in the field [I]Find what[/I] write “:” and in the field [I]Replace with[/I] write “;”, and then click on [I]Replace All.[/I][*]Save the file and close it.[*]Now open the [I]passwd.csv[/I] that we have just edited in Microsoft Excel.[*]Let’s clean up the file to be used by PowerShell. Linux has a bunch of system accounts and we do not want these users in our Active Directory, right? So… all normal users have a uid (User ID) of 500 or higher. So we can now remove users with a [I]uid[/I] (3rd column) of less than 500. We also need to replicate these changes in the [I]passwd.csv[/I] file using Excel:

- After using the uid information to remove unnecessary users we can remove all columns that we will not be used in Active Directory, such as password (2nd column), uid (3rd column), guid (4th column), [I]dir[/I] and [I]shell[/I] columns.
- Right-click on row number 1, and click on [I]Insert[/I] to create a new first blank row.
- Head each column with a descriptive title. We will use it to create the user, mailboxes, and add extra information to the new users accounts. In this article we will create the following column titles: UserName, DisplayName, FirstName, LastName, Office, OfficePhone and HomePhone to match with information that we have in the Linux passwd file.[/LIST]
The CSV file after the cleanup process will look like Figure 04 below.
[IMG]http://www.msexchange.org/img/upl/img0081209047164093.jpg[/IMG]
[B]Figure 04:[/B] CSV file after the clean up process
Now, we can fill in the CSV file with user information and we can create additional columns to be imported into Active Directory as well (Figure 05).
[IMG]http://www.msexchange.org/img/upl/img0101209047164093.jpg[/IMG]
[B]Figure 05:[/B] Final CSV file with all current user information retrieved from the Linux box
Okay, we have just built the CSV file. It’s time to create the users through PowerShell.

[LIST=1][*]Copy the [I]passwd.csv[/I] file to C:\ in the Exchange Server.[*]Open the Exchange Management Shell.[*]Import the CSV to a variable, using the following cmdlet:
[I]$FilePasswd = Import-Csv C:\passwd.csv[/I][*]To validate the content of the $FilePasswd variable (Figure 06), just type in:
[I]$FilePasswd[/I][/LIST]
[IMG]http://www.msexchange.org/img/upl/img0121209047183687.jpg[/IMG]
[B]Figure 06:[/B] The content of the variable $Passwdfile

[LIST=1][*]Let’s create an OU to create the new users. In this article we will use an OU called [I]Postfix Users.[/I][*]We have to define an initial password to the new accounts that will be created through PowerShell, then type in the following cmdlet:
[I]$Password = Read-Host “Password “ –AsSecureString
[/I]We will be requested for the password. We should use an easy password that will be used for all new accounts. The user will use this password the first time they log on to the Active Directory. We have to inform all users about the migration process and this initial password.[*]Now that we have finished all the prerequisites required to create users (Figure 07), we can create the mailboxes using our imported CSV file through the $FilePasswd variable and the columns that we defined in Excel to match with the parameters used. The following table can be used to create the cmdlet to start the user creation process:[/LIST]
[B]Cmdlet Parameter[/B]
[B]Variable that will be used[/B]
$FilePasswd
CSV file imported (step 03)
$UPN
Each line read of variable $FilePasswd will add the Username more @apatricio.local to the $UPN variable. We have to change using your current FQDN domain name used during AD deployment.
-Alias and -Name
$_.UserName that is the Username column of our CSV file.
-UserPrincipalName
It will be the value of $UPN variable that is changing for each user.
-DisplayName
$_.DisplayName that is the DisplayName column in our CSV file.
-FirstName and -LastName
$_.FirstName and $_.Lastname that are the FirstName and LastName column in our CSV file respectively.
-Database
Database that the new users will create, to validate the mailbox database we can use run Get-MailboxDatabase.
-OrganizationUnit
OU where the new users will be created.
-Password
$Password that was created in step 6.
-ResetPasswordOnNextLogon
$True. All users after the first logon in the Active Directory will be requested to change their password.
[B]Table 1[/B]
In our article the following cmdlet will be used:
[I]$FilePasswd | ForEach { $UPN = $_.UserName + “apatricio.local”; New-Mailbox –Alias $_.UserName –Name $_userName –UserPrincipalName $UPN –DisplayName $_.DisplayName –FirstName $_.FirstName –LastName $_.LastName –Database “srv-2k7-ex01\mailbox database” –OrganizationUnit “PostFix Users” –Password $Password –ResetPasswordOnNextLogon $true }[/I]
[IMG]http://www.msexchange.org/img/upl/img0141209047183703.jpg[/IMG]
[B]Figure 07:[/B] Creating the new users through PowerShell cmdlet
Now we are able to open the Exchange Management Console and see the new mailbox that we have just created (Figure 08).
[IMG]http://www.msexchange.org/img/upl/img0161209047183703.jpg[/IMG]
[B]Figure 08:[/B] The new users created
In the process above we created all users from the Linux passwd file. If you are using the [I]alias[/I] file you have to update those e-mail addresses in the current environment. If there is only a small number of e-mail addresses on the [I]alias[/I] file the work can be done manually but in some cases a script to add the secondary SMTP address can be useful.
[B]Conclusion[/B]

In this article we defined our E-mail address policy to match with the current policy that is being used in the Linux Box. We also created all users in the Active Directory and Exchange Server using the Linux [I]passwd[/I] file as our source.
[/LEFT]

[LEFT][CODE]http://www.msexchange.org/articles_tutorials/exchange-server-2007/migration-deployment/moving-linux-mail-server-p2p-network-exchange-server-2007-part3.html[/CODE]

[SIZE=3][B]PART-3[/B][/SIZE]

[B]Updating User information in the Active Directory[/B]

Now that we have created the users we should move on to user information. Using the New-Mailbox cmdlet we are not able to add all the information that we have in our CSV file. We can use the same Exchange Management Shell session and run another cmdlet to add the left over information in the $Passwdfile variable in the new users that we have just created. The following cmdlet can be used (Figure 01):
[I]$FilePasswd | ForEach { Set-User $_.Username –Office $_.Office –Phone $_.OfficePhone –HomePhone $_.HomePhone}[/I]
[IMG]http://www.msexchange.org/img/upl/img0021210248496833.jpg[/IMG]
[B]Figure 01:[/B] Adding information from $Passwdfile into the current AD accounts
The result can be seen in the user’s Properties as shown in Figure 02 and Figure 03.
[IMG]http://www.msexchange.org/img/upl/img0041210248496833.jpg[/IMG]
[B]Figure 02:[/B] User has received information from $PasswdFile variable
[IMG]http://www.msexchange.org/img/upl/img0061210248496849.jpg[/IMG]
[B]Figure 03:[/B] User with telephone information that was created in the Linux box
Using the same concept, we can create extra columns in the [I]passwd.csv[/I] file to add more information in the new users’ accounts. For example, we can create a column called MobilePhone in the CSV file and add that information for all users and add [I]–MobilePhone $_.MobilePhone[/I] in the [I]set-user[/I] cmdlet. Using this logic we can add as much information as we want in the new environment through the initial CSV file.
[B]Joining the workgroup workstations in the Active Directory domain[/B]

In order to migrate to the new environment, we have to work on the workstations first. Then, we have to keep in mind the following points before starting this process:

[LIST][*]We must make sure that all workstations use the Active Directory DNS Server in the DNS settings.[*]Make sure that all workstations are using the correct DNS suffix (Active Directory suffix).[*]Inform the users after joining their workstations in the Active Directory that they have to log on to the domain with the current user name credentials used to access the message system and password that we defined previously.[*]Download the [URL="https://www.microsoft.com/downloads/details.aspx?FamilyID=9d467a69-57ff-4ae7-96ee-b18c4790cffd"]Windows 2003 Resource Kit[/URL] and make it available to be copied to all workstations when necessary.[*]We can perform this process gradually, we don’t need to work on all clients at the same time.[/LIST]
We have just covered some of the initial setup. All workstations should be resolving through the Active Directory DNS Server and they should also be accessing DNS resolution from the old zone (apatricio.ca) without problems. Now, we can start the workstation migration from workgroup to Active Directory:

[LIST=1][*]Join the workstations into the Active Directory
More information can be found at this [URL="http://support.microsoft.com/kb/295017"]Microsoft KB article[/URL].[*]Log on locally as [I]Administrator.[/I][*]Copy the moveuser.exe to c:\[*]Configure the local profile to be used with the new Active Directory account (Figure 04). We can run the following command:

[I]Move <local-user-name> <domain-NetBIOS-Name\user-name>[/I]
Where Local user is the local user name that the user has been using.[/LIST]
[IMG]http://www.msexchange.org/img/upl/img0081210248576693.jpg[/IMG]
[B]Figure 04:[/B] Moving local user profile to be used in the new Active Directory account

[LIST=1][*]Log off from the machine as administrator.[*]Users can log on using their user name and the initial password that we already defined during the user mailbox creation through PowerShell.[*]After logging on users will receive a message asking to change their password. Instruct them to use the same password that they have been using to access the Linux box to retrieve their messages.[*]The users should be accessing the same information that they had had before we moved the profile with the moveuser.exe tool. The user experience should be the same; it includes desktop icons, Outlook Express, etc, as shown in Figure 05.[/LIST]
[IMG]http://www.msexchange.org/img/upl/img0101210248576693.jpg[/IMG]
[B]Figure 05:[/B] Users logged on to the domain will access the same information that they used to have locally
[B]Migration Process – Current Status (Update #02) [/B]

Now, our workstations have begun to be moved to the new domain, and all users are using their Active Directory accounts to log into the domain. Our users have enabled mailboxes already; however they are still accessing the Linux Box. A picture of our environment can be seen in Figure 06.
[IMG]http://www.msexchange.org/img/upl/img0111210248576693.jpg[/IMG]
[B]Figure 06:[/B] Current status of our scenario
Our next steps are enabling Exchange Server 2007 to accept the current client’s settings before switching to Exchange Server 2007, to do that we have to set up some Exchange Server 2007 components, such as:

[LIST][*]POP3[*]Receive Connector[*]OWA[/LIST]
[B]Configuring POP3 Setting in Exchange Server 2007[/B]

We will install Outlook 2007 on all workstations but until then our current clients running Outlook Express should work without any problems. We will accommodate them on to Exchange Server 2007 using their current settings. To do that we have to enable POP3 in Exchange Server 2007:

[LIST=1][*]Open the Exchange Management Console.[*]Expand Client Access.[*]In the work panel click on Exchange Server 2007, and in the result panel click on [I]POP3 and IMAP4[/I] tab.[*]Click on POP3 and in Toolbox Actions click on Properties under POP3.[*]Click on Authentication tab.[*]Select [I]Plain text login (Basic Authentication)[/I] as shown in Figure 07.[/LIST]
[IMG]http://www.msexchange.org/img/upl/img0121210248605974.png[/IMG]
[B]Figure 07:[/B] Configuring the POP3 Authentication

[LIST=1][*]Click [I]OK.[/I][*]Open [I]services.msc[/I] and make sure that the [I]POP3 Service[/I] is configured to start automatically and click on Start.[/LIST]
Let’s get a workstation to validate the new POP3 Settings. Configure this workstation using a test user in the current environment (Linux box) and then change the Outlook Express settings to use the IP address of the Exchange Server. Make sure that the test user can download messages through the POP3 protocol. We can send some test messages to the user’s mailbox using Exchange 2007 OWA because the new user’s Exchange 2007 mailbox is empty.
[B]Configuring a Receive Connector for internal users[/B]

In order to allow the current internal users to send messages through SMTP we can create a Receive Connector that will allow all internal clients to send messages through it. It will be a temporary configuration. After we install Outlook 2007 on all clients they will use MAPI and this connector can be removed. 1. Open the Exchange Management Console.

[LIST=1][*]Expand Server Configuration.[*]Click on Hub Transport.[*]In Toolbox Actions, click on New SMTP Receive Connector.[*]In the Introduction section, label the new receive connector and select Custom. Click on Next.[*]In the Local Network Setting section, just type in the FQDN name to be used for this Receive Connector. Click on Next.[*]In the Remote Network settings, we have to add our internal network and click Next.[*]In the New Connector, a summary will be displayed, click on New. (Figure 08)[/LIST]
[IMG]http://www.msexchange.org/img/upl/img0141210248605990.jpg[/IMG]
[B]Figure 08:[/B] Finishing the new receive connector that all internal clients will use
If your current environment allows any internal user to send messages through the Linux box we have to enable Anonymous users in the new Receive Connector. To do that, just check Anonymous users on the Permissions Groups tab. (Figure 09)
[IMG]http://www.msexchange.org/img/upl/img0161210248631349.jpg[/IMG]
[B]Figure 09:[/B] Allowing Anonymous users to send messages through internal receive connector
The last setting to be done in our new Receive Connector is to allow the internal clients to send Internet messages through this new connector (Figure 10). By default the Exchange Server 2007 will allow relay only for the local domain. The internal users will not be able to send internet messages, to change this behavior we can run the following cmdlet:
[I]Get-ReceiveConnector *Internal* | Add-ADPermission –user “NT AUTHORITY\ANONYMOUS LOGON” –ExtendendRights ms-Exch-SMTP-Accept-Any-Recipient[/I]
[B]Note:[/B]
Our Receive connector name is “[I]Internal Receive Connector[/I]”.
[IMG]http://www.msexchange.org/img/upl/img0181210248631349.jpg[/IMG]
[B]Figure 10:[/B] Adding the ms-Exch-SMTP-Accept-Any-Recipient to Anonymous users in the Internal Receive Connector
Time to validate the Receive Connector! Here are some tests to validate if our internal clients will work on the new environment:

[LIST][*]Telnet <IP-Exchange-Server> 25
The FQDN besides 220 must be the name that we have set up during the Receive Connector, if it is not please make sure that the IP addresses range in the network remote settings include the IP address of the host where we are doing the test.[*]Configure a single machine with the IP Address of the Exchange Server 2007 in the SMTP configuration and send a message to internal and internet recipients. This process should work properly.[/LIST]
If everything went well we know that after switching the environment from Linux to Exchange 2007 all users will be able to send messages internally and externally without problems. If you have different settings to send messages, such as SMTP Authenticated or TLS make sure that you change your Exchange Server 2007 to work properly with your needs before changing the environment.
[B]Conclusion[/B]

In this tutorial we have seen how to update the users’ attributes and configure some Exchange Server 2007 components to work with the current environment. In the next and final article we will be looking at the final steps to switch between message systems and install Microsoft Outlook on the workstations to migrate the user data from local to the Exchange database.


[/LEFT]

[LEFT][CODE]http://www.msexchange.org/articles_tutorials/exchange-server-2007/migration-deployment/moving-linux-mail-server-p2p-network-exchange-server-2007-part4.html[/CODE]

[SIZE=3][B]PART-4[/B][/SIZE]

[B]Configuring OWA[/B]

Linux users might be using Web Access to access their messages and they don’t have the domain information to add during the webmail access process. To avoid questions in the new OWA, let’s change the default behavior and configure it to accept only user name and password just like they have been using in the Linux box. To configure OWA to accept only user name and password follow these steps:

[LIST=1][*]Open the Exchange Management Console.[*]Expand Server Configuration.[*]In the Work Panel, click on the Exchange Server.[*]In the Result Panel, click on Outlook Web Access tab.[*]Right-click on OWA (Default Web Site) and then click on Properties.[*]Click on the Authentication tab.[*]Check [I]Use forms-based authentication[/I] and click [I]on user name only[/I] and choose the current Active Directory domain, as shown in Figure 01.[/LIST]
[IMG]http://www.msexchange.org/img/upl/img0021211984228430.jpg[/IMG]
[B]Figure 01:[/B] Configuring OWA authentication to user name only

[LIST=1][*]Click on OK in the new window.[*]Restart IIS to apply the new settings. Click on the Start button, Run and type in iisreset /noforce.[/LIST]
Now, the new users will be able to use only user name and password to access their mailbox through OWA, as shown in Figure 02.
[IMG]http://www.msexchange.org/img/upl/img0041211984228446.jpg[/IMG]
[B]Figure 02:[/B] New users using only the user name and password to log on to OWA
Most of the webmail deployments using Linux don’t have any SSL, in this case we will configure a script that redirects the connection [url]http://srv-linux.patricio.ca[/url] to the https URL used by Exchange Server 2007. It’s important because we will change the current Linux host DNS record to the Exchange 2007’s IP address. In this scenario all users will access the new Exchange 2007 OWA instead of the old environment after the switch process.
To create a direct script and apply it in the new environment follow these steps:

[LIST=1][*]Create a [I]default.htm[/I] file and copy and paste the following content:
[I]<html>
[/I][I]<head>
[/I][I]<script language=”javascript”>
[/I][I]<! --
[/I][I]Self.location.replace([url]https://fqdn-of-exchange-server);[/url]
[/I][I] // -->
[/I][I]</Script>
[/I][I]</head>
[/I][I]</html>[/I][*]Save the file in the home folder of the Default web site, c:\inetpub\wwwroot.[*]Open Internet Information Services Manager.[*]Expand Web, right click Default Web Site and click on Properties.[*]Click on the Directory Security tab.[*]In Secure Communications, click Edit.[*]Uncheck Require secure channel (SSL).[/LIST]
[B]Starting to use Exchange Server 2007[/B]

It’s time to switch from Linux to Exchange Server 2007. Here are some points that must be validated:

[LIST][*]Validate if the Exchange Server 2007 users’ SMTP Address matches with the SMTP address for the Linux users.[*]If you use the Linux [I]alias[/I] file feature, make sure that all entries are in the new environment, in some cases we have to create Groups, add extra e-mail addresses for some users, etc.[*]Validate if a user in Exchange Server 2007 can send external messages. You might have to check the firewall settings.[*]Create a list of all users that work only through Webmail. This list will have priority in the migration to Outlook 2007.[*]Warn users that OWA content will be empty. We need to migrate the data locally to the Exchange database first.[/LIST]
Okay, we have done all prerequisites and all tests are fine, so we can start the switch process:

[LIST=1][*]Schedule a weekend and send a message informing that the message system will be offline for some hours and the new system will be up.[*]Log on to the Domain Controller.[*]Open DNS Management.[*]Find the zone where the current entry of the Linux Server is and all users are using to resolve to the Linux Server, in our case this is [I]apatricio.ca.[/I][*]Change the IP Address of the Linux server to the Exchange Server box.[*]Change the firewall rule that redirects external SMTP traffic to the Exchange Internal IP Address.[*]Change the firewall rule to allow the Exchange Server 2007 to send external messages (allow 25 SMTP out).[*]Log on to a workstation and run [I]ipconfig /flushdns[/I] to clean up the local cache and try to ping the server name used by Linux in the POP/SMTP setting. The resolution must point to the Exchange Server.[/LIST]
So... how can we test the new environment? Let’s use the new features. Let’s log on to OWA and send a message from Administrator to user Anderson.Patricio.
The user Anderson.Patricio should receive the new messages and all old messages will stay in the same place (locally in the Inbox Folder), as shown in Figure 03.
[IMG]http://www.msexchange.org/img/upl/img0061211984228446.jpg[/IMG]
[B]Figure 03:[/B] The new message received in the new environment
By default Outlook Express will configure the Account and all messages will stay on locally; there is no copy of received messages in the mailbox server. This behavior is controlled through the option “leave a copy of messages on server”, as shown in Figure 04.
[IMG]http://www.msexchange.org/img/upl/img0071211984251117.png[/IMG]
[B]Figure 04:[/B] Maintaining a copy of all received message in the Server
Using this option the same new content will be received in Outlook Express and OWA as well.
[B]Migration Process – Current Status (Update #03)[/B]

So, we should now have all workstations accessing Exchange Server 2007 by legacy protocols (POP, SMTP and OWA). We have also changed the Internet message flow to the new server. Our current environment can be seen in Figure 05.
[IMG]http://www.msexchange.org/img/upl/img0081211984251117.jpg[/IMG]
[B]Figure 05:[/B] The new environment
The Linux Box server is no longer in use, but if we need some information we can access it through Webmail and POP3 using the Linux server IP address.
[B]Installing Outlook 2007 on workstations[/B]

Now we will really move the data from the clients to an Exchange database. In order to configure all clients to use all Exchange Server 2007 features we will install Outlook 2007.
This process is straightforward. After successful installation, we will upgrade the current Outlook Express settings to Outlook and after that we will be able to transfer local messages to the Exchange Server by just moving the messages.

[LIST=1][*]Click on Outlook.[*]In the Outlook 2007 Startup screen click Next.[*][B]E-mail Upgrade Options[/B]. Select upgrade option and then click Next.[/LIST]
[IMG]http://www.msexchange.org/img/upl/img0101211984251164.jpg[/IMG]
[B]Figure 06:[/B] Upgrading from Outlook Express to Outlook 2007

[LIST=1][*]Most of the information will be filled in already, just click Next to finish this process.[*]The first time that Outlook runs it will display a dialog box about the import process, click Yes.[*]Close Outlook.[/LIST]
Now it’s time to remove the POP3/SMTP account settings and define the MAPI profile using Autodiscover.

[LIST=1][*]Click on Start, Settings and Control Panel.[*]Double click the Mail icon.[*]Click the E-mail Accounts button.[*]Click the E-mail tab and click New.[*]Add an Exchange Mailbox; the profile will be created automatically based on the current user information in the Active Directory, as shown in Figure 07.[/LIST]
[IMG]http://www.msexchange.org/img/upl/img0121211984270399.jpg[/IMG]
[B]Figure 07:[/B] Adding the Exchange Server account

[LIST=1][*]Let’s remove the old imported Account. Select the legacy account (the new one is called Microsoft Exchange) and then click Remove. Click Yes to confirm.[*]Click Data Files and see all the Personal Folder and Mailbox information that you worked on, as shown in Figure 08.[/LIST]
[IMG]http://www.msexchange.org/img/upl/img0141211984270399.jpg[/IMG]
[B]Figure 08:[/B] The available Data Files

[LIST=1][*]Open Outlook again see two main items: Mailbox, where all information is in the Exchange Server and Personal Folder, where we have all messages that we were working with in the legacy system. Move the important messages to Exchange and they will be available in OWA as well.[/LIST]
[IMG]http://www.msexchange.org/img/upl/img0161211984270399.jpg[/IMG]
[B]Figure 09:[/B] The old content in the PST file and the server content
[B]Final Steps …[/B]

Okay, in this article series was demonstrated how to move from a Linux mail server to Exchange Server 2007 using the resources found in Exchange Server 2007 and Active Directory. We moved all network services, workstations and we were able to move them gradually to the new environment.
Have we finished the migration process? Actually no, we still have to check some points:

[LIST][*]After we upgrade all workstations to Outlook 2007 and configure them to use MAPI instead of POP3 and SMTP, we will be able to remove the Receive Connector for Internal users.[*]We will also be able to disable the POP3 Service.[*]Configure the Firewall to publish the other Exchange 2007 features (RPC over HTTP, ActiveSync, etc.[/LIST]
Finally, we can say that we have finished the Exchange Server 2007 deployment, but your work is not done. You have a lot of cool features to explore like high availability, unified messaging, anti-spam protection, etc.
[B]Conclusion[/B]

In this article we switched between messaging environments and we also saw how to upgrade from Outlook Express to Outlook 2007 on the client side. With this process done we were able to move local content to the Exchange Server database through Outlook.


[/LEFT]