Migration of Unity users from MS Exchange server 2007 to 2010

Hi,
I am having Unity 7.0 with MS Exchange server 2007,now want to transfer the users and Unity mailboxes to MS Exchange server 2010. Want to know the procedure. Can anyone help me out?

The way you're doing it has two very high hurdles.
First, you have to get the data out of an offline server and into Office 365.  That's hardly a trivial task.  If the server were online and reachable by the Internet you could use a move request or a third-party tool like MigrationWiz.
Second, if you do get the mail moved, you will want to synchronize the legacyExchangeDN attribute from the old organization into an X500 proxy address in Office 365 for all mailboxes to preserve mail replyability.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Similar Messages

  • Migrating Exchagne Server 2007 to 2010 DAG....

    Hi,
    One of my customer request to migrate their existing Exchange server 2007 to a latest version. They are currently using Office 2003 package so I think we can only migrate to Exchange server 2010 due to compatibility issue of Office Outlook with Exchange 2013.
    We need to implement DAG solution with 2 server and I  know that I can install Exchange Server 2010 SP3 over Windows Server 2012 stranded edition. We hope to implement one server in the Head office and the other server is gong to be fixed in DR site that
    connects the Head Office via a IPSec VPN tunnel.
    We have several ADs. 3 in Head Office, One in remote site and one in DR site.
    HO-Primary AD    :    Windows server 2003 R2 32bit    Standard    :    Schema,Domain,RID,PDC,Infra and a GC
    HO-DC01        :    Windows server 2008 R2 64bit Standard    :    GC    
    HO-ADC        :    Windows server 2008 R2 64bit Standard    :    GC
    ROADC        :    Windows server 2008 R2 64bit Standard    :    DC
    DR-ADC        :    Windows server 2008 R2 64bit Standard    :    DC. Will change to GC when installing DAG
    Domain Functional Level    :    Windows server 2003
    Forest Functional Level    :    Windows server 2003
    Current Exchange 2007 setup has only one server with Hub,Mail and CAS role installed. Also there is a Edge transport role installed in the perimeter network.
    We are planning to purchase 2 brand new servers for Exchange DAG and hope to retire the old server after migrating completed My concern is that I've never done a Exchange Migration in this type of a setup where mix server OS and lower Functional level exists.
    It would be great if you could let me know what should i look before planning this migration.
    Are there any known issues of the current setup I need to be aware of while migrating?
    Is there a complete guide available that I can refer?
    Please be kind enough to support me to find accurate information to plan and execute this migration.
    Thanks in advance.
    Tharaka

    Hi Tharaka,
    In addition to Steve's suggestion, I would like to clarify the following thing:
    When you migrate Exchange 2007 to Exchange 2010, you need to stand up the new environment, create a 'legacy' name space (or rename 'owa' is an option), and then move mailboxes to the new environment.
    Here is a thread about migration from Exchange 2007 to Exchange 2010 for your reference.
    migration of exchange server 2007 to 2010
    http://social.technet.microsoft.com/Forums/en-US/0d0d031d-46ed-4806-ada5-6590346caa74/migration-of-exchange-server-2007-to-2010?forum=exchangesvrdeploylegacy
    What's more, about Exchange 2010 DAG, here are some helpful threads for your reference.
    Database Availability Group Design Examples
    http://technet.microsoft.com/en-us/library/dd979781(v=exchg.141).aspx
    Understanding Database Availability Groups
    http://technet.microsoft.com/en-us/library/dd979799(v=exchg.141).aspx
    Hope it helps.
    If there are any problems, please feel free to let me know.
    Best regards,
    Amy
    Amy Wang
    TechNet Community Support

  • Exchange server 2007 still on version 8.1 even after applying sp3

    hello,
    I have exchange 2007 version 8.1 and I want to migrate to exchange 2013, so in order to to that I need to upgrade the exchange 2007 to sp3.
    I install the sp3 without any issue but the version of the exchange 2007 still 8.1, I try to re install but it show that the sp3 already installed.
    any idea about this issue?
    thank you

    Hi
    As is well known, you
    must patch Exchange 2007 to the very latest Service Pack and Update Rollup before you attempt to do anything with Exchange 2013.
    According to your description, I suggest you should check the rangeUpper value by using ADSI Edit .  If the value was 14625. This indicates
    your schema is at Exchange 2007 SP3.
    Here is the article  for your reference:  https://supertekboy.com/2014/05/01/check-exchange-schema-objects-adsi-edit/
    Also you could re-install the patches in the following links .
    Please download and install these patches from here:
    Exchange Server 2007 Service Pack 3: https://www.microsoft.com/en-gb/download/details.aspx?id=24111
    Exchange Server 2007 SP3 Update Rollup 10 : https://www.microsoft.com/en-us/download/details.aspx?id=36708
    Hope it’s helpful to you .
    Best Regards,
    David

  • Hidden Contact Subfolders are visible on iPhone after sync with Exchange Server 2007

    Hello,
    We have encountered an issue where synchronizing the iPhone with Contacts from an Exchange Server 2007 mailbox, causes hidden contact subfolders (from Outlook) to be visible and appear in the Groups list in the Contacts App on the iPhone.  This does not occur with Exchange Server 2010 mailboxes.
    We have a 3rd party application that creates hidden subfolders in the default Contacts folder on Exchange Server 2007 mailboxes.  The hidden folders do not display in the Outlook client, Blackberry or on an Android phone.  We did see that they were showing up in Outlook Web Access until we applied this Microsoft Exchange Server 2007 Service Pack 3 Rollup 2 patch unto the Exchange server:
    http://support.microsoft.com/kb/2210042 - A sub contact folder is still visible after you set the "PR_ATTR_HIDDEN" attribute to "True" in an Exchange Server 2007 environment.
    After the patch was applied, the hidden contacts do not show up anywhere else.  However, when we synced the mailbox to an iPhone and synced existing contacts, all of the hidden folders appear in the Contact Groups list.  Is there a way to hide the hidden sub contact folders on the iPhone and prevent them from appearing in the Contact Group lists?
    Any help provided would be most appreciated.
    Thanks and Best Regards

    Hi SBuchan,
    I have an open case with Microsoft about it.  It is an issue with ActiveSync in Exchange 2007 that sends the hidden objects.  Microsoft tried to resolve this in Exchange 2010 by sending a delete message after sending the hidden objects to remove them from the device.  Am awaiting to see if they will approve a design change to Exchange 2007 ActiveSync to prevent the synching of hidden objects.

  • Microsoft Exchange Server 2007 and iCal

    So at my new job they use Exchange Server 2007 for mail and calendars, and supposedly I should be able to view other people's calendars, but I can't find any way to do this in iCal.
    Do I have to install Entourage, or is there some other way to do this?

    Hello,
    I finally found the response : Grid control 11g cannot monitor Exchange Server 2007 or 2010 because they don't support WMI. The plugin uses WMI to connect to Exchange Server.
    Oracle have to create a new plugin based on PowerShell.
    Thanks Dominik.
    Edited by: Dominik on 19 nov. 2010 07:14

  • Provisiong of users from OIM to Exchange Server 2007

    Hi,
    I am trying to Provisioning the users from OIM 9.1.0.1 to Exchange server 2007. For this i used Exchange Server Connector 9.1.1.1.0. By using AD_Base_connector 9.1.1.0.0 i can
    provisioned the user details. But while provisioning to the Exchange server 2007 i am getting the following error
    ERROR [XELLERATE.WEBAPP],Class/Method: tcLookupFieldAct ion/lookupByColumn encounter some problems: lookup Error in OIM
    And i am unable to get the LookUp detais for the MailBox in Design Console as well as in the ScheduleTasks in OIM Admin Console..
    Can anybody help me in solving this issue.
    Thanks & Regards
    SRI

    Hi suren,
    i am using the Remote Manager. I enabled logs in log.properties in both OIM server and Remote Manager.
    I am observing the following message in Remote Manager command prompt.
    DEBUG,30 Mar 2010 01:12:44,437,[XELLERATE.REMOTEMANAGER],Class/Method: RMISSLCli
    entSocketFactory/createSocket left.
    and i am getting the error in Weblogic server command prompt.
    Running ISADAM
    Target Class = java.lang.String
    Running GETATTRIBUTEHASH
    Target Class = com.thortech.xl.util.adapters.tcUtilHashTableOperations
    Running Set User Attributes
    ERROR,30 Mar 2010 01:13:39,484,[XELLERATE.WEBAPP],Class/Method: tcLookupFieldAct
    ion/lookupByColumn encounter some problems: lookup Error
    can u help me in resolving this issue.
    Thanks in Advance,
    SRI

  • Migrate Notes from Exchange server 2007 to office 365

    Hi,
    Anyone help me to how to migrate notes from exchange server 2007 to office 365 . My customer having notes on his existing exchange account  . We would like to move notes to office 365 . 
    Please help me or guide me .
    Thanks & Regards,
    Vinoth

    The way you're doing it has two very high hurdles.
    First, you have to get the data out of an offline server and into Office 365.  That's hardly a trivial task.  If the server were online and reachable by the Internet you could use a move request or a third-party tool like MigrationWiz.
    Second, if you do get the mail moved, you will want to synchronize the legacyExchangeDN attribute from the old organization into an X500 proxy address in Office 365 for all mailboxes to preserve mail replyability.
    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

  • Migrate a Single User from GW7 to Exchange 2003

    Does anyone have experience migrating a single user from GroupWise 7 to Exchange 2003? We have a business unit that we acquired several years ago and no decision has been made to this point about merging the two e-mail systems (we are GroupWise 7 and they are Exchange 2003). I have just been asked about moving one of our employees to their business unit and want to know my options.
    My gut says that we should keep him on GroupWise because that is what he knows and loves, then we can use this as a first crack in getting GroupWise over there.
    I have found a few Microsoft articles that reference setting up the API gateway and migrating data through there, but everything mentioned is either GroupWise 5.5 or 6.x. Also, based on our past experiences with the API gateway we would like to avoid that if possible.
    We have an implementation of the Novell GroupWise Gateway for Microsoft Exchange, but that presumably does not help us in this situation.
    Are there any utilities out there? Anything that could take a GroupWise Native Archive and convert it to the Outlook equivalent? Even if it was like an archive that he had to manually open from time to time, I'm betting that would be good enough.

    Yes, I have lots of experience. The Microsoft articles that you refer to basically involve setting up co-Existence between GW and Exchange. They all refer to GW 6.5, but it works with GW7. It is just not "officially" supported by Microsoft. The other thing to be aware is that the Microsoft Connector for GroupWise comes with Exchange 2003 and links in with the Novell API Gateway 4.1. The Newer Novell Gateway for Exchange sort of replaces this Microsoft tool, but you are not going to find it much better as a gateway. Too many issues and not nearly enough documentation on the web.
    Also, you can use the migration wizard from the Exchange 2003 installation to migrate a user from GW to Exchange (with or without co-existence set up) . It works fine to migrate all of the users mail, appointments, etc. Does not destroy the GW mailbox, so you can do a dry run to see how it works. Does not migrate their personal address books though.
    The Wizard can create the user for you in Exchagne 2003, but it can only create an Exchange 2003 Legacy account. If you are running Exch2007, set up the user first, then migrate.
    Hope that helps.

  • How do I export public folder data from inactive exchange server?

    I have migrated from SBS2003 (old) to SBS2008 (new)
    Used migration wizard / answer etc...  All went well, expect for the public folders; which failed.
    Question: How do I retrieve the public folder information from the OLD (inactive) server and import it to the NEW server?
    The OLD server has been removed from the domain. I have backups of the OLD server and its original hard drive; where the public store info is located.
    I tried PDDAVAdmin.exe; did not work for me.
    All help is greatly appreciated.
    Bill

    Hi Amit,
    I did as Zoltán said; searched the Internet for edb recovery tools and found a number of companies and Software Products which might help. I also considered your option as well but I have limited experience with building a recovery server and it sounds time consuming.
    Our office is small we have 10 users; we keep contact lists in the public folders. I want to restore the contact lists from the inactive source server to the active destination.
    I believe the process is called "rehoming" (from the web -- "In a Windows environment, rehoming is the process of moving public folders from one Exchange server to another. It involves the creation of a replica of the public folders on the target destination server, waiting for replication to complete, and then removing the public folders from the original source server.")
    Background:
    We have two servers FHHSERVER (the source, SBS2003) and FHHSERVER2 (the destination, SBS2008).
    I used the SBS2008 migration wizard. The important stuff in the exchange database transferred ok; all emails, schedules, tasks, notes, etc. Everything appeared to work; including public folders.
    Microsoft allows a 21 day grace period to complete the migration. I believed the migration was successful so on the 21st day, I followed Microsoft’s instructions and demoted the source server, removing it from the domain. 
    That’s when the trouble started….
    Unknown to me; the public folders remained on the old source server. I did not detect this problem since, during the 21 day migration grace period, the destination server was using the old source server to replicate public folders. As long as the old source server was active, eveyone could open public folder contact lists. After the source server was demoted, the destination server lost its replicate and now our users cannot access that information.
    Another problem is that the inactive server is n o longer licensed and the Exchange console cannot connect to its stores.
    It would seem to me that this problem should be relatively simple to fix. I need some way to open the public folder stores and export the contact lists. I’m not even sure where the public folder database is located on the hard drive.
    I hope this explains the situation in greater detail and that you may be able to offer some insight on how I might resolve this issue.
    Oh, I also tried using EXMerge but cannot seem to make it work either. <http://www.microsoft.com/downloads/details.aspx?familyid=429163EC-DCDF-47DC-96DA-1C12D67327D5&displaylang=en>
    Thanks!
    Bill

  • Upgrading from SBS 2008 and Exchange Server 2007 and Adding Modest Failover Protection

    I haven't seen anyone describe this scenario, so maybe it can't be done, but it seems it should work. Can someone either confirm this is viable or set me straight and tell me it's not wise (and if not, why not).
    I currently have SBS 2008 (2008 Server + Exchange Server 2007 + some other components). I use redirected folders so all my user data is stored primarily on the server, and then sync'd with their local harddrives for roaming use and as an additional
    backup precaution. I want to upgrade to a modern version of Exchange (don't care too much about the underlying server OS, but seems like a good time to upgrade everything). I also want to improve the reliability for rapid recovery in the event of a system
    failure. I have always felt nervous with SBS because it only runs on a single server.
    My plan is:
    Install Windows Server 2012 Standard on a new server machine
    Join that new server to the existing SBS domain and sync the users, etc.
    Install Exchange Server 2013 on the new 2012 Server
    Migrate the existing Exchange data and account info to the new server
    Demote the SBS Server and promote the new server to primary DC
    Reformat the old SBS server and install Windows Server 2012 on it too, and join it to the domain as a second DC
    Set up DFS Replication and keep all my user data folders between the two servers (so if one server fails, the other can take over, just not automatically like with a cluster)
    Install Exchange Server 2013 on the reformatted 2012 Server box (so second instance on the domain) and set it up to sync with the first Exchange Server 2013 via DAG (so if either computer crashes, the other can take over for both Exchange Server and file
    services)
    Wouldn't that give me a complete slow-response failover system without the need for setting up a cluster (I know a cluster would provide instant failover protection, but I don't need that kind of speed - a manual switchover in the rare event of a server
    failure is acceptable for us)? I could do this using cheap hardware for each server, because unless both servers fail at the same time, clients can point to the other server. And because it's not a formal cluster, I don't need to buy anything for a shared
    SAN. This seems like such an obvious more cost-effective solution for a small network, I don't understand why this isn't a common approach, which makes me wonder if there is some reason it won't work.
    Any suggestions or feedback? Are Redirected Folders still recommended for users on a Server 2012-based domain?
    Thanks,
    Colin
    Colin

    Ed, thanks again for your help. OK, so here's my updated plan (I realize I should probably check on some of these pieces on the Server group, instead of this Exchange group).
    Constraints/objectives:
    None of the machines are truly server grade hardware, but only 5 people on the network, so performance is generally not an issue, unless a given server is just pegged on CPU or HD due to its own internal maintenance tasks and can't respond to user requests.
    Haven't seen any problems, since upgrading server from 4GB RAM to 8GB a few years ago.
    Not going to buy any new hardware at this time, but do have several unused consumer-grade computers I can deploy as wimpy or moderate servers.
    Main issue is to limit repair time in the event of a system failure (instant failover is not required, but want to be able to restore network functions within less than 24 hours in the event of a hardware failure) and minimize time spent on IT
    maintenance.
    Because of light IT maintenance (not anyone's primary job and we're too small to justify a dedicated IT person or to pay for outside help), almost every touch takes me research and time to re-learn what I haven't done in weeks, months, or years -- so also
    want to keep all IT tasks as simple as possible.
    We philosophically want to invest now for the next 5 years and avoid ongoing cloud fees (so zero interest in Windows Server Essentials with Exchange Online)
    A little nervous about using VM's, just because I never have before, but I do respect that's probably the right way to do many of these things...
    Currently I have SBS 2008 (Windows Server 2008 R2, Exchange Server 2007, WSUS 3, all with latest SP's, also includes SharePoint and other stuff, but I don't really care about most of it) on a single 8GB consumer grade system, which functions as a file
    server and Exchange server. We use Redirected Folders and Offline files for all users, which works great for us and provides additional file redundancy (if server goes down, all of each user's files are also on their own machine and they can even continue
    to work just fine w/o the server, losing only ability to send and receive e-mail). It has been sufficient, but I want to upgrade our version of Exchange and I am nervous that if that current one server fails, it would take me a long time to restore everything
    from backup, easily many days, especially if I need to buy any replacement hardware. It is RAID1, so a single drive failure is easy to handle, but that's the only hardware redundancy for the current server.
    New Plan:
    Install Windows Server 2012 R2 Standard on a new modest machine (16GBR RAM, Core i7, 1TB RAID1 (may upgrade to 3 or 4 TB), 256 GB SSD boot drive, this had been my old personal computer)
    Join that new server to the existing SBS domain (2008 R2/Exchange 2007), make it a DC, sync the users, etc.
    Install Windows Server 2012 R2 Standard on a wimpy computer (4GB RAM Core i3 processor), leave it as a member server
    Install Exchange Server 2013 on the wimpy new 2012 R2 Server (and nothing else, this will be dedicated to Exchange to make the most of such a wimpy machine)
    Migrate the existing Exchange data from the old SBS Exchange 2007 server and account info to the new server
    (or should I just create new accounts and copy the data from the user end through Outlook -- is that safer and cleaner than attempting any kind of server-level Exchange data migration?)
    Demote the old SBS Server and promote the new 16GB server to primary DC. Now it's OK to take the old SBS server off the network.
    Reformat the old SBS server and install Windows Server 2012 R2 on it too, and join it to the domain as a second DC (and possibly DCPROMO it to be the main server)
    Install Exchange Server 2013 in a VM on the reformatted 2012 R2 Server box (so second instance on the domain for Exchange redundancy) and set it up to sync with the first Exchange Server 2013 via DAG OR set up another physical wimpy member server and install
    it there. In any case, do NOT install Exchange directly on either DC.
    Set up DFS Replication or a Failover Cluster (still need to research this, but I had planned on DFS, thinking Cluster required shared drive, but Ed corrected me on this) between the two DC's for redirected files and keep all my user data folders between
    the two servers. We don't need automatic failover, like with a cluster, a manual switch would be acceptable, but if no additional cost or risk to clustering the two DC's, then the auto-failover protection that provides would be better than DFS.
    I think this incorporates all of your points, Ed. Does this sound right now? What's your advice on #5 (how to best migrate user data)?
    Thanks so much for all your help,
    Colin

  • Exchange Server 2007 OWA users can receive email but can't send

    Hi,
    I have an Exchange server 2007 in an SBS 2008 environment with POP3 connector configured and working fine , smtp send mail connector configured. 
    Now users can connect to OWA, receive email but cant not send.
    smtp connector works fine from Outlook client. Tried to track the emails from exchange server management console and I get the
    SEND DELIVER SUBMIT TRANSFER.
    The emails go to the sent items folder, but it never reach the recipients.
    Have been troubleshooting for a while without succes. Any help will be most appreciated.
    Regards
    Faisal

    POP3 is a single mailbox client mail retrieval protocol, not a mail transport protocol. 
    Any attempt to use it as a mail transport protocol is a great big kludge. 
    Exchange is designed to connect to the Internet using SMTP.
    No version of Exchange has a POP3 connector.
    I recommend that you post this in the SBS Forum:  http://social.technet.microsoft.com/Forums/en/smallbusinessserver/threads
    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

  • Some Users on randomly basis unable to send mails from 2003 exchange to 2007 Exchange users Internally.

    Hi All,
    Some Users on randomly basis are unable to send e-mails from 2003 exchange to 2007 Exchange users Internally.
    They are sending mails from outlook and users from 2007 dont have any issues.
    But sometime mails from 2003 to 2007 goes without any issue.
    The NDR reported is as below.
    From: System Administrator
    Sent: 22 February 2014 15:59
    To: XYZ
    Subject: Undeliverable: Regarding Test Message
    Your message did not reach some or all of the intended recipients.
         Subject:  Regarding Test Message
         Sent:     22/02/2014 15:59
    The following recipient(s) could not be reached:
         XXX,XYZ on 22/02/2014 15:59
               The message contains a content type that is not supported
               <HubServer.Domain.UK #5.6.0 smtp;554 5.6.0 STOREDRV.Deliver.Exception:PropertyValidationException; Failed to process message due to a permanent exception>

    Hi,
    According to the NDR, I found this point "The message contains a content type that is not supported".
    Please verify whether the un-delivered messages contain some Sensitive
    Information,  signatures or attachments that cannot pass the Exchange 2007 Edge server. Please also check the content type of the un-delivered messages.
    Found a useful KB for your reference:
    Frequently asked questions about MIME and content conversion in Exchange 2000 Server and in Exchange Server 2003
    http://support.microsoft.com/kb/836555/en-us
    Hope it is helpful
    Thanks
    Mavis
    Mavis Huang
    TechNet Community Support

  • How to move all emails from mailbox to an external email account in Exchange Server 2007?

    I have a user who is leaving the university in a few days. The user would like to forward all of their old emails from their mailbox to their G-mail account. Will setting up email forwarding forward all of the old emails to the G-mail account or just the
    new emails that are received after setting up email forwarding? If forwarding isn't the correct solution; then what is? We are running Exchange Server 2007.

    No, as you've suspected the forwarding will only affect new messages coming into the mailbox, not existing ones. Additionally, if you did get all existing messages to forward to another account (you could probably do it by creating a rule in Outlook) then
    the gmail account would show every single one of them as arriving now, and lose their existing send date.
    Probably a better option would be to export the mailbox to .pst, and then assuming the user has their gmail account configured in Outlook somewhere as something other than POP3 they can then open the .pst file on their machine and copy the messages over
    to their gmail account, which I think would also preserve the original information.
    You could do that via the server using Export-Mailbox as described here
    http://technet.microsoft.com/en-gb/library/bb266964(v=exchg.80).aspx (note it has to be run from a 32-bit OS with the Exchange Management tools installed), or the user could just as easily do it themselves from within Outlook using the Export option.

  • Downloading data from MS exchange server

    Hello Gurus,
    i have a requirement to download user email information (first name, last name, nt id and email etc..) from Microsoft Exchange server (Outlook). Is there a way to do this in PL/SQL?

    I'm assuming you mean "and into an Oracle database".
    Exchange uses a proprietry format, you are very unlikely to connect to it directly. You could use some .Net tools out there, but the better option is to query the Active Directory server that runs it using LDAP.
    It depends of course on your language - but I've used Perl and the standard LDAP query module to query this sort of info from Active Directory in just a few lines of code. It wouldn't take much to then insert to a database.

  • Config OES/sendmail to forward email from/to Exchange Server

    Hi
    I have installed an OES on a Red Hat ES 3.
    But on my network i have a Exchange Server that send/receive all emails. And i cannot change here nothing(company rules). Now what i need to do? I need to config the Linux sendmail to relay on the Exchange Server(the exchange is now configured relay on Linux) to forward the emails that i need.
    I only need this to one email account e.g [email protected] The Oracle Email Server is running, but i need to config the Linux to forward the email to the Exchange Server, and go to outside. Also i need that receiving an email to [email protected] that my Linux receive this email from the Exchange Server.
    I have configured the sendmail.cf like Oracle says on the Administrator’s Guide manual. I have add the ip and name of the Exchange on /etc/mail/access to relay. But still i cant send emails outside. If i test the sendmail -v testuser, and all says ok. I have tested telnet domain 25, and all went ok.
    I think the only problem is forward the oes to exchange to forward outside
    Any help
    Many thanks
    Thank you
    Jail

    Hi andreas
    Yes i also think that it maybe resolved by an alias and forwarding
    Th COM is the domain in the OES is the com default. Is this domain that you referring?
    The company domain that is in the OES(e.g xpto.com) is the same that is in the Exchange. Do you think this will be a problem? Must i create one like oes.xpto.com? To work with the OES?
    I have created a relay on the access file, but is this ok? Or must i need change anything else? Mean while i will check that url
    And yes i can connect to the Exchange on port 25 from the RH
    Since i have several user/account created on the OES, the only think that i did not understand yet is how can they receive any email?
    The fax@domain was a example. But i can collect all outside emails from that account and with some rules forward to any other OES account? I think this is possible? Or this is the hard way to configure the OES?
    Thank You
    Jail

Maybe you are looking for