نمایش نتایج: از شماره 1 تا 7 از مجموع 7
سپاس ها 1سپاس

موضوع: Moving from MDaemon to Exchange Server 2003/2007

  
  1. #1
    نام حقيقي: 1234

    مدیر بازنشسته
    تاریخ عضویت
    Jul 2009
    محل سکونت
    5678
    نوشته
    5,634
    سپاسگزاری شده
    2513
    سپاسگزاری کرده
    272

    Moving from MDaemon to Exchange Server 2003/2007

    کد:
    http://www.msexchange.org/articles_tutorials/exchange-server-2007/migration-deployment/moving-mdaemon-exchange-server-2003-2007-part1.html

    PART-1


    Introduction

    Any mail migration requires a lot of preparatory work from the mail administrator to ensure that the end-users and mail flow will not be affected during the migration and/or transition process.
    We still have a lot of message topics in the Microsoft forums inquiring about how to migrate from third-party mail servers to Exchange Server 2003 and 2007. In this series, we are going over this process to establish the minimum requirements for this kind of migration. We are going to use MDaemon mail server as the source mail server to our future Exchange 2007 and 2003. However, we can use the same principles applied here to any other third-party mail server.
    There are many ways to perform a migration from MDaemon Mail Server to Exchange Server, basically the options are: Single Step (also called Big Bang Migration) or using Coexistence. The Big Bang Migration is when all users are moved at the same time, usually during the weekend, and on the first day of the new Exchange Server the Help Desk team is swamped by incidents from the new users. There is also the coexistence scenario where both systems are kept up and running, sharing information and a group of users is migrated at a time. In this scenario, the process is more complex and requires some efforts to make sure that both users (migrated and non-migrated) are able to exchange messages and use both mail systems during the transition. In a coexistence scenario, all steps should be done seamlessly from the user point of view.
    A big bang migration can be visualized in the following MSExchange.org article here. After reading this series you can make up your own mind on which migration path you want to follow. You can always use a mix of both article series to create your own migration plan. There are similarities in some steps in both migration scenarios, however, the main goal of this current series is to provide end-to-end migration steps in coexistence mode.
    In order to achieve a successful migration we are going to use 4 (four) important points that we are be validating during the coexistence which are: Directory Synchronization, Global Address List, Mail Routing and Data Migration Process. This general rule may be applied in any Exchange migration to provide basic functionality during the coexistence but it is not a rule, you can add/remove important points in your migration plan.
    Microsoft provides a suite of tools to accomplish these tasks when the source systems are Lotus Notes or GroupWise (Microsoft Lotus and GroupWise Connectors built-in Exchange Server 2003 and Microsoft Transporter for Lotus notes in Exchange Server 2007). However, there is no single built-in tool to do all the process when the source is a third-party mail server.

    Figure 1
    The migration process itself requires a lot of labs and testing from the IT team but there are some other points that must be seen before starting the lab phase, some of them are listed below:

    • Backup
    • Message flow before, during and after migration
    • Anti-virus
    • Disk subsystem
    • Documentation
    • Applications that do relay on the mail server
    • User Training
    • IT Team training
    • Documentation of the basic procedures to be performed by Help Desk team
    • Outlook deployment
    • Outlook Web Access usage for the new users
    • Message Archiving

    Our migration scenario

    In this article series we are going to start migrating from MDaemon mail server to Exchange Server 2007 and in the final part we are going to do the same process using Exchange Server 2003 as well. In this first portion we are going to use 3 (three) servers: a Domain Controller, an Exchange Server 2007 with the three basic roles installed (Mailbox, Client Access Server and Hub Transport) and the MDaemon mail server, as show in Figure 2.

    Figure 2
    The Active Directory is a single forest/domain called apatricio.local and the SMTP address that is being in use by MDaemon is andersonpatricio.org.
    Directory Authentication

    Our first goal is to make sure that our authentication directories are synchronized. MDaemon Mail server allows different methods to create mailboxes in its mail system and the mailbox information can be kept in a simple disk file, ODBC data source or LDAP store. We can also use Active Directory to either import users or monitor Active for user changes, and then any new user created in AD is also created in MDaemon.
    Based on the variety of ways to have the accounts/mailboxes stored, we must ensure that both directories are synchronized, or at least both directories have the same users. We are going over each scenario to validate how to make sure that the future environment will have all users added to the Active Directory.
    Scenario 1: Active Directory and Mdaemon are being synchronized through Mdaemon
    The best option that you may have from a migration perspective is if MDaemon uses Active Directory to synchronize its mailboxes, we can check this out by opening MDaemon, click on Accounts menu, Account Database/Active Directory/Minger… item, and click on Active Directory tab as shown in Figure 3.
    If the first checkbox is enabled then any new AD in Active Directory will automatically start a mailbox creation and the password used will be the same for both environments (mail and AD). The same process will take an action for deleted accounts. In our environment, the mailbox is disabled when the AD account is deleted.

    Figure 3
    If you are using this option, you are ready to move forward to the next step since you do not need to create users because the MDaemon mailboxes came from Active Directory.
    Scenario 2: There is no Active Directory integration
    In this scenario we must ensure that all MDaemon users have accounts in Active Directory before changing their mail clients to the new environment. In some cases, users may have two different directories: Active Directory, where all users log on with different user names and passwords at mail level. In this case, the administrator has to manage and instruct users that in the new environment they will use the same username and password to log on in the network (Active Directory) and mail system (Exchange).
    In order to export the information from MDaemon to Active Directory the following can be used.
    Note:
    The MDaemon export process may contain passwords, which is a really good thing because all new users in Active Directory will use their current passwords.

    1. First, validate the current usernames that are being used on the MDaemon server. Open MDaemon Console, click on Accounts, then Account Manager (Figure 4). We can use this step to remove unnecessary accounts from the source environment.


    Figure 4


    1. We can now import the current accounts. Click on the Accounts menu, Exporting, and again on Export accounts to a comma delimited file item.
    2. A windows dialog box will show up saying that the export will create a file and it will be save on the following path: C:\Mdaemon\APP\Accounts.csv. Click OK.
    3. Another dialog box will show up saying that the export process was completed , click OK
    4. We can open the file that was created by MDaemon and a list of all users and their correspondent attributes will be in that file, as shown in Figure 5.

    Note:
    We can clean up the accounts.csv file to avoid unnecessary accounts to be migrated. In this step we are going to remove the built-in MDaemon and administrator accounts/lines from the csv file because they are not going to be moved to Exchange Server.

    Figure 5
    Now, we can copy the file C:\MDaemon\App\Accounts.csv to the root drive of Exchange Server. Logged with privileges to create an account and mailboxes, we can run the following commands:
    $Users = Import-CSV C:\Accounts.csv
    $Users | ForEach { $SecurePWD = ConvertTo-SecureString $_.Password –AsPlainText –Force; New-MailUser –Name $_.Mailbox –UserPrincipalName ($_.Mailbox+”@<your-AD-FQDN-Domain-Name>”) –SamAccountName $_.Mailbox –FirstName $_.FullName –Password $SecurePWD –ResetPasswordOnNextLogon $false –ExternalEmailAddress (“SMTP:”+$_.Email)}

    Figure 6
    Note #1:
    You may have some issues with users who have passwords that do not match with Active Directory security requirements, you may have to change the current Domain Security policy to accommodate the new users.
    Note #2:
    If you are migrating from a different product and you cannot retrieve the users’ password, you can use a general password to the new users.
    Conclusion

    In this first article we visualized the main steps that should be covered during a migration process with coexistence between Exchange and any other third-party mail server. Our main goal in this first article was to make sure that we have both directories synchronized. This synchronization may be running automatically or an export/import process may be required like we saw in the last section.
    In the next article we are going to start the mail routing section of this article series where Exchange Server will be configured to receive, route and send message traffic to the Internet and also MDaemon server.





    موضوعات مشابه:

  2. #2
    نام حقيقي: 1234

    مدیر بازنشسته
    تاریخ عضویت
    Jul 2009
    محل سکونت
    5678
    نوشته
    5,634
    سپاسگزاری شده
    2513
    سپاسگزاری کرده
    272
    کد:
    http://www.msexchange.org/articles_tutorials/exchange-server-2007/migration-deployment/moving-mdaemon-exchange-server-2003-2007-part2.html
    PART-2

    Introduction

    In the last part of this article series we saw how to export and import accounts and passwords from MDaemon to an Active Directory/Exchange Server environment when required. Let us hold on the directory authentication and Global Address list migration for a bit and let us focus on the mail routing portion of the migration in this article.
    The first step is to make sure that Exchange Server 2007 will be able to receive, send and route messages back and forth to the internet, MDaemon Server and local mailboxes. In order to accomplish this task we need to configure Receive Connectors, Send Connectors and other exchange components in the current organization. The current scenario has all mail traffic using the current MDaemon server (Figure 1). In this article we are going to configure Exchange to handle the current SMTP traffic and also communicate with MDaemon Server.
    Figure 1
    Configuring Accepted Domains and E-mail Policies …

    By default, any new Exchange Server 2007 installation has a single default domain and it is the FQDN (Full Qualified Domain Name) of the current Active Directory. In our scenario, the Active Directory FQDN name is apatricio.local, which means that our Exchange accepts only messages addressed to users containing domain@apatricio.local.
    The first step is to configure Exchange Server organization to accept the domain that is being used by MDaemon and also configure it as a shared SMTP Address. The following steps may be followed in order to configure a shared accepted Domain.

    • Open the Exchange Management Console
    • Expand Organization Configuration
    • Click on Hub Transport
    • Click on Accepted Domains tab.
    • In the toolbox actions, click on New Accepted Domain and type in a label for the new domain name in the Name text box.
    • Fill out the domain that will appear in our Exchange organization accepting messages.
    • Select the option Internal Relay Domain radio button (Figure 2).
    • Click on New and Finish in the following screen.


    Figure 2
    When we have the Internal Relay Domain option selected for an Accepted Domain, that domain is not authoritative, which means that exchange will accept relay for the domain. However, the user may not exist in the Exchange Organization. Exchange will check if there are any messages addressed to that domain against the current users’ proxy address. If it does not find the SMTP address, the message can be routed to another host through a Send Connector. If we leave the default setting (Authoritative domain), then, any message sent to Exchange that does not contain an SMTP associated to an AD user will be refused and a NDR will be generated saying that the mail address does not exist.
    Now that we already have the Accepted Domain, it is time to configure the shared SMTP address to be stamped in all new and existent users, as follows:

    • Open Exchange Management Console
    • Expand Organization Configuration
    • Click on Hub Transport item
    • Click on E-mail Address Policies tab
    • Double click on Default Policy
    • In the first wizard page click on Next twice.
    • In the E-mail address page, click on Add button and then SMTP Address

    In this last window, we are to configure the SMTP Address policy that will be applied to all new users. This section is really important from a coexistence perspective because all migrated users will be created on Exchange server and they will receive the current SMTP policy. If the current SMTP policy matches the current SMTP addresses that have been used in MDaemon we will not have any extra work to configure SMTP address after migration. After configuring the SMTP policy, click OK. (Figure 3).

    Figure 3
    All SMTP addresses that will be assigned to the users that belong to this policy will be displayed, as shown in Figure 4. In our current deployment, all users in our exchange organization will receive two SMTP Addresses: @andersonpatricio.org and @apatricio.local. It is very import to keep at least two different addresses at this point because we are going to use the second one that is not being used by MDaemon to route internal messages from MDaemon. Click on Next twice, and click on Edit using default settings to apply the new policy to the existent users.

    Figure 4
    After applying the E-Mail Address Policy, we can double click on an existent user or create a new one and all SMTP Address configured in the default policy should be stamped in the E-mail Addresses tab of the user object properties using Exchange Management Console.
    Configuring Send Connectors

    Our next step is to configure Exchange server to route messages to MDaemon and Internet as well. These following steps can be used to create the SMTP routing to MDaemon:

    • Open Exchange Management Console
    • Expand Organization Configuration
    • Click on Hub Transport item and click on Send Connectors tab
    • Click on New Send Connector located in the Toolbox Actions
    • Fill out a descriptive name for the connector and make sure that Internal option is selected
    • Click Next. (Figure 5)


    Figure 5
    In the address space section, click on the Add button. In the Address field, add the domain that is being shared between two mail systems and click OK. The result is shown in Figure 6. Click Next.

    Figure 6
    So far we confirmed that all messages addressed to @andersonpatricio.org are going to be routed through this connector. The next section of the wizard configures what the destination for these messages is going to be, in our case, the MDaemon server.
    Note:
    The message is going to be routed only if there is no local Mailbox using the mail address.
    Click on the option Route mail through the following smart hosts and click on Add. Next, add the IP address of the third-party mail server and click on Next, as shown in Figure 7.

    Figure 7
    Because we have both servers located in the internal network, the authentication will not be used to route messages, but can be configured using several option from the authentication settings page. Let us leave the default settings which has no authentication and click Next. In the Source Server make sure that the local exchange server is listed and click Next, click New in the following page, and then Finish to conclude the process.
    The second step using Send Connectors, is to configure Exchange Server to send messages to Internet since down the road we are going to configure all incoming and outbound traffic through Exchange Server. Before switching over it is extremely important to make sure that Exchange is ready to receive and send messages back and forth without any interruption in the current mail flow.
    The process of creating a send connector to send messages to the internet is almost the same that we have just done, here are the summary of the required steps during the Send Connector wizard:

    1. Introduction. Label this connector accordingly and select Internet.
    2. Address Space. Add a SMTP address and use *in the address field
    3. Network settings. Leave the default settings.
    4. Source Servers. Leave the default settings.

    Besides of the Send Connector component configuration on Exchange Server, there are several components that are used to send messages out, such as: reverse DNS, SPF record, FQDN configuration in the Send Connector using the proper FQDN name.
    After configuring Accepted Domains, Recipient Policies and Send Connectors we can visualize the changes made in our environment so far in Figure 8.

    Figure 8
    Conclusion

    In this second article we went over the Exchange configuration to route messages to MDaemon server and also send messages to the Internet. In the next article we will continue configuring SMTP routing and we will be executing some tests to validate the SMTP routing architecture.





  3. #3
    نام حقيقي: 1234

    مدیر بازنشسته
    تاریخ عضویت
    Jul 2009
    محل سکونت
    5678
    نوشته
    5,634
    سپاسگزاری شده
    2513
    سپاسگزاری کرده
    272
    کد:
    http://www.msexchange.org/articles_tutorials/exchange-server-2007/migration-deployment/moving-mdaemon-exchange-server-2003-2007-part3.html
    PART-3

    Introduction

    In the last article, we created an Accepted Domain and Send Connectors to support our coexistence scenario. The current message flow configured can be seen in Figure 1.

    Figure 1
    Now, we need to configure Exchange Server 2007 to receive mails from Internet and also be a relay server for our Mdaemon server and then we are going to run some tests to validate our coexistence scenario.
    Configuring Receive Connectors

    By default, Exchange Server 2007 has two receive connectors (Default and Client) we are going to add an additional Receive Connector and it will be configured only to allow relay from any message coming from the Mdaemom Server IP address. After that, we will be able to configure MDaemon to send messages to Exchange Server and the new server will be responsible to send messages to the internet. Also, we are going to configure the Default connector to receive internet mail without requiring authentication (default setting).
    First things first, let us create a receive connector to allow MDaemon to send messages:

    1. Open Exchange Management Console.
    2. Expand Server Configuration.
    3. Click on Hub Transport.
    4. Select the server object on the right.
    5. Click on New Receive Connector in the Toolbox Actions.
    6. On the Introduction page, type in a name for the new receive connector and select Custom, click on Next. (Figure 02).


    Figure 2

    1. On the Network Settings page, let us use the default settings (all available IP Addresses and listening on 25 port) and to facilitate a troubleshooting later on we can use a different FQDN for this new receive connector, click on Next.
    2. On the Remote Network settings page, remove any entry from Remote IP Address (es) frame and click on Add buttonand specify the IP address of the MDaemon Server and click on Next. (Figure 3).


    Figure 3

    1. On the New Connector page, we will see a summary of all configuration that we have done so far, click on New.
    2. On the Completion page, click on Finish.

    The Receive Connector was created however we still have some stuff to do. Double click on the new receive connector, and click on Permissions Groups tab and tick the option Anonymous users and click on OK.
    So far our new Receive Connector will allow Mdaemon Server to deliver local messages in Exchange Server 2007, however it will not allow Mdaemon Server to use our Exchange Server as relay server for Internet recipients. We can configure Exchange Server to act as relay server to any recipient coming from Mdaemon Server, we can use the following Exchange Management Shell to accomplish our goal:
    Get-ReceiveConnector “MDaemon Receive Connector” | Add-ADPermission –User “NT Authority\Anonymous Logon”-ExtendedRights:ms-exch-SMTP-Accept-Any-Recipient
    Note:
    Be extremely careful with the cmdlet above, if you configure that on your Receive Connector facing the Internet you will be allowing any external host to use your server as an Open Relay Server and your server is going to join a Black List.
    At this point of our article, the new Exchange Server accepts message from MDaemon Server and deliveries the message either internal or external recipients. The second step is to configure Exchange Server 2007 to receive mails from the Internet, this configuration is straight forward process. We just need to configure the Default Receive Connector to accept anonymous users, like we have just done in the previous step. More information how to configure an Exchange Server to receive mail from Internet can be seen on this MSExchange.org article.
    Changing MDaemon Server mail flow

    If you are moving from another third-party mail server to Exchange Server, you should adapt the settings that we are going to perform on MDaemon Server to your current scenario/solution. Basically, we are going make sure that MDaemon is going to send all mail traffic to Exchange Server. Keep in mind that if both recipients are in the same server (either MDaemon or Exchange Server) the smtp routing will not work because both system check their local address first before sending messages out.
    In order to configure MDaemon to forward all message traffic to Exchange Server, these following steps can be done:

    1. Open MDaemon Console (Click on Start, Programs, Mdaemon and then Start MDaemon).
    2. Click on Setup menu item, and click on Primary Domain…
    3. Click on Delivery tab (Figure 04), and select the option Try direct delivery but send problem emails to the server specified below and in the Mail server field add the Exchange Server IP Address.


    Figure 4


    1. Click on Unknown Mail tab (Figure 05). Make sure that Send message to the “Postmaster”user and Place message in bad message directory options are uncheck, and check the option Enable advanced options and add the Exchange Server IP address on Send the message to this host field.


    Figure 5

    Testing the mail routing…

    We have just done the required configurations in order to allow Exchange to receive and route messages in a coexistence scenario however we need to test the new settings and make sure that everything works properly. In order to test the new scenario these initial tests can be performed, as follows:

    1. Create a new mailbox user on Exchange Server.
    2. Open Exchange Management Console and check the new user SMTP Address. You can use that e-mail address to perform the next tests.
    3. From any client machine or Exchange Server use telnet utility to connect on Exchange Server port 25 and send a message to the new user and also to an existent user located in MDaemon.
      Note: In this test we are going to use the Default <Server-Name> Receive Connector.
    4. Logged on MDaemon Server try to send a message to an Exchange User.
    5. Logged on MDaemon Server try to send a message to an external recipient.
    6. Logged on OWA try to send a message to a MDaemon user.
    7. Logged on OWA try to reply a test message that came from MDaemon (Step 04).

    Note:
    The process to test SMTP message through a command line can be seen in this MSExchange.org article or in this Microsoft KB article.
    Change the incoming traffic to Exchange server

    After testing all the configuration and document all the process, we will be able to switch the incoming traffic to the new Exchange Server without interrupting the mail traffic. You need to change the current firewall settings to forward external traffic arriving on 25 ports from external sources to the IP address of the new Exchange Server.
    Conclusion

    In this article we worked on the Receive Connectors to accommodate the coexistence between Exchange Server and third-party mail server and also created some tests to validate that coexistence between them. In the next article we are going to cover the directory synchronization to provide some Global Address List during the migration.






  4. #4
    نام حقيقي: 1234

    مدیر بازنشسته
    تاریخ عضویت
    Jul 2009
    محل سکونت
    5678
    نوشته
    5,634
    سپاسگزاری شده
    2513
    سپاسگزاری کرده
    272
    کد:
    http://www.msexchange.org/articles_tutorials/exchange-server-2007/migration-deployment/moving-mdaemon-exchange-server-2003-2007-part4.html
    PART-4

    Introduction

    In our last article, we had a look at mail flow options (Send Connectors, Receive Connectors, MDaemon configuration). In this article of our migration series, we are going to discuss some steps that may be helpful towards directory synchronization between both environments during the coexistence scenario.
    MDaemon E-Mail server is the core component of the mail solution and the MDaemon Suite has several add-on products to support the message system. MDaemon users can take advantage of ComAgent, which allows Address List synchronization between Outlook Express/Outlook with a MDaemon server. There is also an Outlook Connector component that allows Outlook to connect directly with the MDaemon server. By default, a client is able to connect using POP3/IMAP4 or WebClient (webmail client interface).
    ComAgent also has a built-in Instant Messaging client that allows end-users to have a buddy list where they can send and receive short messages using an IM interface. Microsoft has a solution called OCS, where IM is one of the features. Some of the key features of MS solution are: Telephony Integration, Audio/Video conferencing, Application Sharing, Live Meeting, federation with external clients and also public networks such as: MSN, AOL and Yahoo.
    Okay, let us get back to the main point of this article, namely, the Address List synchronization between MDaemon and Exchange Server. We are going to go over some manual process to keep both directories synchronized during the coexistence period. You can always create scripts to automate the process and avoid manual labour to keep both environments synchronized.
    Basically, we want to provide to the migrated and non-migrated users the same Global Address List in both environments.
    Configuring Global Address List on MDaemon side

    MDaemon users using WorldClient webmail client are able to search the Address List and use Auto-Complete when they are sending messages in the “To/Cc” fields (Figure 1) or if they click on Address List Lookup icon and select organization-name/Contacts (Figure 2).

    Figure 1

    Figure 2
    For each new mailbox created using MDaemon Console, an entry for this new mailbox will be created in the Contacts folder, located in the MDaemon Public folder structure.
    There are several methods to provide the Address List entries in an MDaemon server, and we are going over two easy steps to create entries in its Address List. The first one can be used for new accounts created only in Exchange Server 2007 and the second one can be done for accounts migrated between systems. Both methods can be used and it is completely up to you for which method to use.
    Note:
    In both the scenarios demonstrated below, we already have a mailbox created on Exchange Server 2007.
    Method 1: Creating a contact in MDaemon’s Address List

    The first method requires a user configuration which is able to change the public address book (you can create a new user for that purpose or use the Administrator Account Server). After deciding which account will be used, let us open the MDaemon Console, click on the Accounts menu and then Account Manager… double click on the designated user and click the Options tab. Tick the option Account can modify the public Address Book and click OK (as shown in Figure 3).

    Figure 3
    Now, we can log onto the WordClient using the account that we have just changed in the previous step. Expand Public Folders, expand your-organization-name item, click on Contacts, and then click on New. Type in the information necessary and do not forget the E-mail address, as shown in Figure 4.

    Figure 4
    Now, you can start a new message using the WorldClient and type in the first letters from the new contact and it will show up automatically.
    Method 2: Changing an existent mailbox properties to forward messages

    Let us say that we have a user and that user is going to be migrated to the new Exchange Server 2007 environment, we can follow the previous method, delete the mailbox and create a contact. However, we may want to keep the original mailbox content on the MDeamon server for a while and make sure that the migrated user is happy and has all content in the new mailbox for a couple of days before removing the original mailbox from MDaemon Server.
    Note:
    We are not talking about data migration at this point, just the required steps to keep the coexistence of the environment.
    Open the MDaemon Console, click Accounts and Account Manager… double click on the designated user, and clear the options POP, IMAP and/or Outlook connector to force the user to use the new environment. Click on Forwarding tab and check the option This account is currently forwarding mail and type in the e-mail address of the target user, we are going to use a secondary SMTP address that he has in the new environment (@apatricio.local), as shown in Figure 5.


    Note:
    You can configure to be forwarded and also keep a copy in the local MDaemon, even though, the user will not be using MDaemon any more we can have a copy of the content during the initial stage of the migration.
    Note 2:
    If Exchange Server is receiving messages from the internet at this point the forward will work only for messages sent from non-migrated accounts, all messages coming from either Internet or another Exchange mailbox will not reach the MDaemon account.

    Figure 5
    Configuring Global Address List on Exchange side

    The next step, in order to provide some sort of Global Address List synchronization is to make sure that Exchange Server Global Address List has all existent mailboxes that exist in the MDaemon server.
    On the Exchange side we can create a Mail-Enabled Contact or a Mail-Enabled User, if you already have the users in your Active Directory the Mail-Enable User should be easier to do because we are going to play with just one object.
    In order to create a Mail-Enabled User, we can use these following steps:

    1. Open Exchange Management Console
    2. Expand Recipient Configuration
    3. Click on New Mail user... in the Toolbox Actions
    4. On the Introduction page. Click on Existent User… and click Browse and select an existent user. Click on Next.
    5. On the Mail Settings page. Click on Edit... and fill out the SMTP Address using the same SMTP Address that is being used by MDaemon mailbox and click on Next (Figure 6)


    Figure 6

    1. On the New Mail User page. Click on New
    2. On the Completion page. Click on Finish

    In order to create a Mail-Enabled contact, we can use these following steps:

    1. Open Exchange Management Console
    2. Expand Recipient Configuration
    3. Click on New Mail Contact… in the Toolbox Actions
    4. On the Introduction page. Select New Contact option and click Next
    5. On the Contact Information page. Fill out if the information from the mailbox located in the MDaemon Server and make sure that the external e-mail address field matches the mailbox in MDaemon. Click on Next. (Figure 7)


    Figure 7

    1. On the New Mail Contact page (It is just a summary of what we have done so far) click on New
    2. On the Completion page. Click on Finish.

    Now, we just need to open Outlook Web Access and our new entry will appear in the Global Address List, and the end-users will be able to use Global Address List to address messages to the non-migrated users located in our MDaemon server, as show in Figure 8.

    Figure 8
    By the way, we can use Exchange Management Shell to create the Mail-Enable Contacts or Mail-Enable Users easily through a script.
    Conclusion

    In this article we have seen how to create entries in both message systems to maintain the same Address List visualization for users located in both environments. The same process can be applied to others mail systems to provide Address List features for migrated and non-migrated users.





  5. #5
    نام حقيقي: 1234

    مدیر بازنشسته
    تاریخ عضویت
    Jul 2009
    محل سکونت
    5678
    نوشته
    5,634
    سپاسگزاری شده
    2513
    سپاسگزاری کرده
    272
    کد:
    http://www.msexchange.org/articles_tutorials/exchange-server-2007/migration-deployment/moving-mdaemon-exchange-server-2003-2007-part5.html
    PART-5

    Public Folder Migration

    Inter-Org replication tool does not work between MDaemon and Exchange server, and a manual process can be performed to migrate data from MDaemon environment to Exchange Server.
    A possible way to move data between systems is using a PST file, the process is to connect an Outlook client to the MDaemon server and copy the Public Folder content to a PST and move the content of that PST to the Exchange Server Public Folders structure. Unfortunately, we can move data but not permissions and the permissions must be documented prior the migration and applied manually afterwards.
    In order to connect an Outlook client to an MDaemon server, the Outlook Connector should be installed on the server side and also on the client site. A trial version of the Outlook Connector add-on is available at the MDaemon webpage. After installing that add-on on the server, these following steps can be performed:

    1. Choose an existing MDaemon account to perform the migration
    2. Open the MDaemon Console
    3. Click on Accounts menu item
    4. Click on Account Manager…
    5. Double click on the account chosen in the previous step 1
    6. On the General tab, click on Outlook Connector
    7. Now, log on to a workstation with Outlook 2003/2007 installed and log on tp the WorldClient using the credentials of the account used in Step 1
    8. Click on Options
    9. Click on Outlook Connector
    10. Click on Download Outlook Connector and follow the installation wizard using default values

    We can now create a new Outlook profile and select the option Other on the Choose E-mail Service page and then select Outlook Connector for MDaemon 2.2, as shown in Figure 1.

    Figure 1
    Now lets move on to the easier part of the migration. Let us open the Outlook Profile that we have just configured which is connected with MDaemon Server. Then, in an Outlook session click on File, New and click on Outlook Data File… A new window requiring which type of PST we are going to create will show up, click on Office Outlook Personal Folders File (PST) and click on OK, and select the path where the file will be created and click on OK.
    After adding a PST file a new item will be noticed on the left side of the MDaemon Connector mailbox. In order to see Public Folders in the same view, click on Folders List item on the left. The result will be similar to the Figure 2.

    Figure 2
    In order to create a backup of the current Public Folder information to a PST, we just need to drag and drop the Public Folders that we want to move to the PST item, as shown in Figure 3.

    Figure 3
    On the Exchange Server side, Open Exchange Management Console, click on Toolbox item and double-click on Public Folder Management Console. Click on Default Public Folder item and in the Toolbox Actions we can create new Public Folders to create a structure similar that we have been using in MDaemon to accommodate the new users.
    Note:
    To create calendar, contacts, notes, tasks, etc folders we need to use an Outlook client. Using Public Folder Management Console we can create only Mail and Post Items type folders.
    As soon as we have the initial folders created on Exchange Server 2007, we can create a new Outlook profile configured to access Outlook and then we need to attach the PST file that we used with the old MDaemon profile and copy the content from PST to Exchange Server. Afterwards, we need to assign permissions to the migrated folders in the new Exchange Server 2007 Public folders.
    MDaemon Public Folder Management

    MDaemon uses different level of permissions for Public Folders. In order to document the current permissions we can use two different methods: client side or server side.
    At the client’s side, we can get the Properties of any folder located underneath Public Folders and select Folder Permissions tab, as shown in figure 4.

    Figure 4
    At the server side, we can open the MDaemon Console, click on Setup menu item and then click on Shared Folders (Figure 5), using this method the administrator can also manage the current Public Folders and play with the permissions as well.

    Figure 5
    If your organization uses more than the default Public Folder structure, try to move Public Folders and users who have access to the migrated public folder in the same step, because we can not keep both Public Folders synchronized.
    Configuring Outlook client to use Exchange Server 2007

    Some companies that use MDaemon as mail server also use Outlook Connector in their environment to connect Outlook 2003/2007 clients to the mail Server. There are several ways to configure a migration script to move user’s profiles to the new environment, and there is no right or wrong way to accomplish that task. In your migration you just need to test your strategy and make sure that it makes the majority of your users happy through the migration process.
    We are going to shed some light on a possible script that can help you out during the migration process. When we have an Outlook Connector profile configured, Autodiscover for Outlook 2007 will not run and the profile will not be configured automatically unless the end-user creates a new profile. The Outlook profile configuration is kept in the following registry key path HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Profiles.
    We can create a simple script (migration.bat) to delete the current profile settings and export a brand new profile using the content of the NewProfile.reg file.
    The content of migration.bat file:
    Echo Removing current profile...



    reg delete "HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Profiles" /f
    Echo.
    Echo Importing initial settings..
    reg import \\<Server-Name>\<Share>\NewProfile.reg
    Echo. The content of NewProfile.reg file:
    Windows Registry Editor Version 5.00
    [HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Profiles]
    "DefaultProfile"="Outlook"
    [HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Profiles\Outlook] Note:
    In order to properly run the sample script above the end-user should be able to run reg utility on the client and permissions to manage that specific registry portion.
    After running the sample script above, the end-user can double click on Outlook icon and a new profile will run and the Autodiscover will take care of the rest of the configuration.
    We can also use Group Policies to automatically configure Outlook 2007 without any end-user interaction. You can see the procedures involved in this process here.
    If you still have Outlook 2002/2003 clients, the same sample script can be used in conjunction with PRF to create the user’s Outlook profile.
    Conclusion

    In this article we went over the process to migrate Public Folders and an initial script to configure current Outlook Connectors users to the new environment.
    More information








  6. #6
    نام حقيقي: 1234

    مدیر بازنشسته
    تاریخ عضویت
    Jul 2009
    محل سکونت
    5678
    نوشته
    5,634
    سپاسگزاری شده
    2513
    سپاسگزاری کرده
    272
    کد:
    http://www.msexchange.org/articles_tutorials/exchange-server-2007/migration-deployment/moving-mdaemon-exchange-server-2003-2007-part6.html
    PART-6

    Changing POP/IMAP/Webmail clients…

    MDaemon allows several types of clients to connect to it, we saw in the last article a way to migrate Outlook Connector to the new environment using a script. However, we still have to play with POP/IMAP and Webmail clients during the migration process.
    Your client may have been configured to use either a DNS host name or IP configuration in POP/SMTP/IMAP client configuration. We are covering all aspects of a coexistence scenario and the POP/IMAP clients should be tested before moving the users’ data. We have a couple of scenarios where we need to prepare to the user’s configuration, as follows:

    • End-users using POP/IMAP clients (non-Outlook) configured to an IP Address/Hostname
      Possible Solution: Change the IP Address to the new server for the migrated user(s)
      Recommended solution: Install Outlook 2007 on the user workstation and migrate the local data to Exchange Server
    • End-Users using Outlook client configured to an IP Address/Hostname
      Possible solution: In this scenario, the client should use a PST, in theory, we just need to create a new profile and attach the PST to the new profile and move data to Exchange Server. We can go a little bit further and create a script to read the current PSTs files in use and configure a new Outlook profile and re-attach the old PSTs into the new profile.

    The steps described to import data from an Outlook Express client to Outlook 2007 are described in the following MSExchange.org Article.
    After migrating the last user we should change any IP Address, host name or firewall rule pointing from MDaemon to the new Exchange Server. This configuration will allow any user that hasn’t been configured yet to be able to have some connectivity to the new server. Unfortunately, we cannot do this at the beginning because the majority of the users are using the MDaemon Server and they have not had their data migrated over.
    Changing Webmail and mobility users

    During the coexistence we need to instruct the migrated users to use a different URL to access the webmail page from internal network and also from the Internet. A new firewall rule in your current firewall to publish OWA is required to provide webmail for the remote users.
    Another firewall change that should be made is related to Outlook Anywhere and web services, after moving users to the new environment they will be able to use all Exchange Server mobility features and they require some configuration at your firewall level. If you are using ISA you can use the built-in wizards to help you out to create the publishing rules. The same method can be used to create rules to publish Exchange to mobile users using Activesync devices.
    Data Migration

    One of the last steps for a coexistence scenario migration is the real data migration. We have several ways to move data from MDaemon to Exchange Server. All methods that will be described here must be synchronized with the end-user migration.
    The first method is using Microsoft Transport Suite and all steps involved in this process are described in the following article series.
    Based on the articles series above, we just need to validate two points on the MDaemon side, as follows:

    1. All accounts that will be migrated using the Transporter tool, must be enabled as POP or IMAP (during the Migration wizard we can decide which protocol will be used). In order to enable POP/IMAP on an MDaemon Mailbox, open the MDaemon Console, click on Accounts, and Account Manager. Double click on selected users and make sure that the protocols are enabled in the Account tab, as shown in Figure 1.


    Figure 1


    1. As we saw in the first article, we can export MDaemon account list and use some of those columns to create a migration file. Open MDaemon Console, click on Accounts, Exporting and then click on Export accounts to comma delimited file.

    We can use the exported file from Mdaemon to create the file required by Microsoft Transporter Tool, we can use Excel or a simple notepad to change the format. In the table below we can see all required columns by Transporter Tool and what we already have using the exported file that came from MDaemon.

    Transporter Column
    MDaemon Column
    SourceIdentity
    Email
    SourceServer
    -
    SourceLoginID
    Mailbox
    SourcePassword
    Password
    TargetIdentity
    -
    A second option is using Import-Mailbox cmdlet, where we can import data from a PST file to an existent Exchange mailbox. This method can be useful if the user does not have any data on the MDaemon Server and all information is kept in his/her local PST. In this scenario the Microsoft Transporter Tool would not be useful because it only copies data from the Mdaemon Server to Exchange Server.
    My fellow MVP Henrik Walther wrote about the process to import using Import-Mailbox cmdlet, and you can check his article series here.
    A third option is to do the migration on the client side, if user has an Outlook express we should install Outlook client and migrate the content; if the user has an existent Outlook using PST we just need to migrate the data over to the server.
    Wrapping it up…

    During this article series we went over some procedures for each step that can be used during a coexistence migration scenario to move from MDaemon mail server to Exchange Server 2007. A lot of these procedures covered in this article series can be used on any other third-party mail server. Each third-party mail server has its own features and set of configuration but the main steps will be similar. Just make sure that you have a lab to test and validate your migration plan.
    Conclusion

    In the next article we are going to go over some administrative tasks that an MDaemon administrator should know how to do in their new Exchange Server 2007 environment.





  7. #7
    نام حقيقي: 1234

    مدیر بازنشسته
    تاریخ عضویت
    Jul 2009
    محل سکونت
    5678
    نوشته
    5,634
    سپاسگزاری شده
    2513
    سپاسگزاری کرده
    272
    کد:
    http://www.msexchange.org/articles_tutorials/exchange-server-2007/migration-deployment/moving-mdaemon-exchange-server-2003-2007-part7.html
    PART-7

    Introduction

    In this final part of the series we are going to cover some basic administrative tasks that an MDaemon administrator should know how to do in their new Exchange Server 2007 environment. I selected some tasks that can help the new administrator to perform their daily tasks routine.
    Managing protocols at User level

    Using MDaemon, an administrator can double-click on the user and then General tab. An MDaemon administrator is able to manage which protocols that specific user is able to connect on the MDaemon server. The available options on the General tab are; POP, IMAP and Outlook Connector (Figure 1). The tab “Web” allows you to configure access to the webmail interface, as shown in Figure 2.

    Figure 1

    Figure 2
    In Exchange Server 2007, we can use Exchange Management Console and perform these following steps:

    1. Open Exchange Management Console
    2. Expand Recipient Configuration
    3. Click on Mailbox item
    4. Double-click on the designated user
    5. Click on Mailbox Features, as shown in Figure 3, and you will be able to disable several protocols from the user, such as: OWA, ActiveSync, UM, MAPI, POP3 and/or IMAP4.


    Figure 3
    Creating an alternate SMTP address

    Using MDaemon, an administrator can create an alias and associate it to a mailbox, from there, the mailbox will start receiving messages that are addressed to the alias as well, as shown in Figure 4.

    Figure 4
    Using Exchange Server 2007 is a little bit different. One mailbox can have multiple e-mail address associated to it and any message addressed to those addresses will be delivered in the same mailbox. In order to add an extra SMTP Address to a user the following steps can be done:

    1. Open Exchange Management Console
    2. Expand Recipient Configuration
    3. Click on Mailbox item
    4. Double-click on the designated user
    5. Click on E-mail Addresses tab, and click on Add button. In the Figure 5, I am adding the SMTP address andy@andersonpatricio.org to the existent mailbox.


    Figure 5
    Note #1:
    Only one entry from that list can be configured as Set a Reply and the accounts’ SMTP Address will be stamped in any message sent from that mailbox. Natively, the end-user cannot switch over their own e-mail address to send a message, they are able to receive messages addressed to any address of that list but when they send a message the replay address will be always the SMTP configured as Set as Reply.
    Note #2:
    If you need more than one user receiving messages addressed to an SMTP address, you should consider creating a Mail-Enabled group and adding all accounts that should receive a message into that group.
    Full Access permissions

    Using MDaemon an administrator can define permissions on the Inbox folder on the user’s properties, as shown in Figure 6.

    Figure 6
    Using Exchange Server 2007, we can define Full Access permissions at mailbox level and the user that is defined in the Full Access Permissions wizard will be able to access the entire content of the mailbox through Outlook or Outlook Web Access, as shown in Figure 7. In order to configure using Exchange Management Console, open it, expand Recipient Configuration, click on Mailbox and select the user. In the Toolbox Actions there is an option called Manage Full Access Permissions.

    Figure 7
    There is also a client side option where a user using Outlook can right-click on any folder and click on Permissions tab. Then, the user can assign users from the Global Address List and define level of access for that specific user.
    The user that has received the permission can open Outlook, click on File, Open, and then on Open Other User’s folder item, pick it up the username from the Global Address List and select which default folder he wants to connect and click on OK.
    Forwarding e-mail

    Exchange 2007 allows an administrator to forward mail traffic to a mailbox, Mail-Enabled group or contact. The administrator can also configure if it is going to be just a forward or if the incoming messages will be delivered on both places (mailbox and forward object). In order to configure the forward settings, these steps can be followed:

    1. Open Exchange Management Console
    2. Expand Recipient Configuration
    3. Click on Mailbox item
    4. Double-click on the designated user
    5. Click on Mailbox Flow tab and double-click on Delivery Options (Figure 08)
    6. Check the option Forward to and select a mail enabled object from the list, to bring it up the available entries, click on Browse button.


    Figure 8

    Note:
    Exchange Server allows a single entry on the forward field, if more than one entry is required, you should consider using a Mail-Enabled group instead.
    Creating a group containing All Users from your organization

    A common question that may come up in your first days of Exchange Server 2007 administration is how to create a group that contains all users from your organization. You can create a group like that in two different ways: create a normal group and add all users which require manual labour afterwards to keep that group update or using Dynamic Distribution Groups. In order to create a dynamic distribution group that does not require manual updates later on, we can follow these steps:

    1. Open Exchange Management Console
    2. Expand Recipient Configuration
    3. Click on Distribution Group
    4. Click on New Dynamic Distribution Group
    5. On the Introduction page, choose the Organization Unit where this group will be created, and define name and alias for this new group, then click Next
    6. On the Filter Settings: Select the recipient container, in our case let us select the domain root item, enable the option Users with Exchange Mailboxes options and click on Next. (Figure 9)


    Figure 9

    1. Leave the default settings and finish the wizard

    Now, we can go to Global Address list and we will be able to see the group that we have just created.
    Hiding a user from the Address List

    Using MDaemon a user can be easily removed from the Address List through the option Hide account from calendar, ‘Everyone’ list, and VRFY results, as shown in Figure 10.

    Figure 10

    To do the same process in Exchange Server 2007, we need to double-click on the designated user and check the option Hide from Exchange address list, as shown in Figure 11.

    Figure 11
    Exchange Management Shell cmdlets

    We have been working on Exchange Management Console so far, but Exchange Server can be managed through Exchange Management Shell. The following table can help you out to remember which cmdlet can be used to configure the same previous configurations that we have just done.

    Task
    Exchange Management Shell cmdlet
    Most likely attributes that will be used
    Create a new user
    New-Mailbox

    Disable mailbox features
    Set-CASMailbox
    POPEnabled, IMAPEnabled, MAPIEnabled, OWAEnabled and ActiveSyncEnabled
    Full Access Permission
    Add-MailboxPermission
    AccessRights
    Hide from Address List
    Set-Mailbox
    HiddenFromAddressListsEnabled
    Forward mail
    Set-Mailbox
    ForwardingAddress
    Dynamic Distribution Groups
    New-DynamicDistributionGroup

    Conclusion

    In this final article we demonstrated some manage tasks that an MDaemon Administrator should know in order to manage his new Exchange Server 2007 after a migration.




    th95 سپاسگزاری کرده است.

کلمات کلیدی در جستجوها:

1

Active Directory Server icon

2

active directory server symbol

DISABLE PASS Mdaemon console

4

how can i create an user in mdaemon9.3Migration mdaemon to exchange 2010migrate mdaemon to exchange 2010symbol domain controllerwhen domain controller smtp replicationdirect migration of mdaemon 11 to exchange 2010WEB SERVER STORAGE SERVER DB SERVER DOCUMENT MANAGEMENT SERVER ACTIVE DIRECTORY ISA SERVER AND DOMAIN CONTROLLER ANTIVIRUS SERVER CONFIGURATION AND ARCHITECTUREMdaemonad server iconOutlook Connectormdaemon how to export distribution grouphow to configure relay server in ms exchange 2010 for mdaemonmicrosoft transporter suite mdaemonwhat is the difference between Exchange server 2010 and MDaemon mail servertransport suite calendar mdaemondomain sharing in mdaemon for exchangehow to open mdaemon 11 open in main consolehow to migrate messages from mdaemon to exchange 2010connect send connector exchange 2010 to mdaemon

برچسب برای این موضوع

مجوز های ارسال و ویرایش

  • شما نمی توانید موضوع جدید ارسال کنید
  • شما نمی توانید به پست ها پاسخ دهید
  • شما نمی توانید فایل پیوست ضمیمه کنید
  • شما نمی توانید پست های خود را ویرایش کنید
  •