Migrate to Windows 2012 R2 and Exchange 2013 SP1 using database portability

Hi, I'm planning to migrate from Exchange 2013 SP1 running on Windows 2012 to Exchange 2013 SP1 on Windows 2012 R2.
Is it possible to use database portability to move the databases from the exchange installation on win 2012 to the new installation on Win 2012 R2? This would save a great deal of time not doing the mailbox moves.
I've searched similar cases but couldn't find any, all speak about disaster recovery and database portability but I've found no articles that uses the migration scenario.
Would it be possible to do and if so, what would the steps be? Do I need to delete the database from the source server, move the database files to the new server and mount them and relocate the mailboxes? Or should I dismount the database on the source server,
move them to the new server and mount them and relocate the mailboxes?
Frank.

Hi,
According to your description, I recommend you consider using DAG to achieve your requirement.
The following steps for your reference:
1.Prepare a new server which installed windows 2012 R2 for Exchange 2013 mailbox server.
2.After you deploy Exchange 2013 Mailbox servers, you can create a DAG, add Mailbox servers to the DAG, and then replicate mailbox databases between the DAG members.
3.After replication, you can mount all the databases on the new server.
Hope this helps!
Thanks.
Niko Cheng
TechNet Community Support
This no way a resolution. This won't work at all as Both OS will be different and you can't form the Cluster.
Please Unmark it!
Cheers,
Gulab Prasad
Technology Consultant
Blog:
http://www.exchangeranger.com    Twitter:
  LinkedIn:
   Check out CodeTwo’s tools for Exchange admins
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Similar Messages

  • Upgrade of Integation Services (Windows 2012 R2) on Windows 2008 R2 with Exchange 2013 SP1 DAG fails

    Here is the scenario:
    Legacy Host: Windows 2008 R2
    Guest VM: Windows 2008 R2 with Exchange 2013 SP1 DAG cluster.
    After importing the VM (2008 R2 and Exchange 2013 DAG) into a 2012 R2 host (Cluster).  (copy VM files to new 2012 R2host) Everything works fine.
    Then upgrading "Installation Services" (for Windows 2012 R2 host) on the imported VM runs fine with no errors to the "Restart" prompt. VM than shows: "Configuring Windows updates 32% complete. Do not turn
    of your computer." Hangs there for about 20 minutes until is says "shutting down". Hangs there for 20 minutes until power off. Restart to normal start; "Preparing to configure Windows. Do not turnoff your computer." proceeds slowly
    to "Configuring Windows updates 32% complete. Do not turn of your computer." hangs there again indefinite. Sometime hangs at shutdown cycle and "Configuring Windows updates 32% complete. Do not turn of your computer." indefinitely.
    I moved 20 other machines from a 2008 R2 host to new Windows 2012 R2 hosts all of these machines install the 2012 R2 Integration services just fine on the 2008 R2 VM. Just the 2008 R2 VMs clustered (DAG) and Exchange 2013 SP1 do not take the Integration
    Services upgrade.
    Any advise from Microsoft? I know I could decommission the DAG and Exchange machines and install Integration services on the native box before Exchange and DAG and that would sure work, but I'd rather avoid that amount of work for a simple integration layer
    upgrade.
    Thanks
    Gerhard Waterkamp ACSLA Inc.

    Hi,
    Could you try use the following method to fix this issue first?
    1. Run the System Update Readiness Tool, then check if there is any error in the Checksur.log and checksur.persist.log.
     1. Please run the System Update Readiness Tool on this affected server. Please download this tool from the following Microsoft article:
     Description of the System Update Readiness Tool for Windows Vista, for Windows Server 2008, and for Windows 7
     http://support.microsoft.com/kb/947821/en-us
    2. The System Update Readiness Tool creates the log files that captures any issues that the tool found or fixed. The log files are located at the following location:
    %SYSTEMROOT%\Logs\CBS\
    3. Please paste the checksur.log here for analysis.
    If there is no error found, please try the following step.
    ==================================
    2. Use Fix it tool to reset the Windows Update components.
     1. Open the following link.
     http://support.microsoft.com/kb/971058/en-nz
     2. Select Windows 8.1, Windows 8 and Windows 7 in the product selection box.
     3. Click “Run Now” to reset the Windows Update components.
    Note: We can reset the Windows Updates manually by following the steps in the KB above.
    3. Use the System File Checker tool to repair missing or corrupted system files
     1. Open the command promote with Administrators.
     2. At the command prompt, type the following command, and then press ENTER:
         sfc /scannow
    Any errors are found in the steps above, please let me know.
    Hope this helpful.
    Best Regards,
    Jason Zeng
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

  • SBS2011 - Cross domain Migration to Server 2012 R2 w/ Exchange 2013

    I am attempting to find the best way to do this, and any input/guidance would be greatly appreciated.
    Source Server: SBS 2011 Standard - Internal domain costco.local
    Target Server: Server 2012 R2, 2 virtuals, one for the domain controller, one for Exchange 2013 - Internal domain ad.costco.com
    I know that in order to establish a trust relation, I must add a secondary domain controller to the SBS2011 domain and transfer FSMO roles.  My question is, can I use a trial Server 2008 R2 as an interim DC, create the trust, use ADMT to migrate user
    accounts to the new domain and move mailboxes from the SBS server with the trust established on the Server 2008 DC?  Or do I have to install an interim exchange server and move the mailboxes and remove the SBS server from the domain?
    If that is the case, can I use a 180 Trial of Server 2008 R2 and Exchange 2010 on two separate virtuals on the old domain, move all user accounts and mailboxes to a standard domain temporarily.  Then from the standard domain move user accounts and mailboxes
    to the Server 2012 R2 DC and Exchange 2013 virtual?
    It would be great if I could just establish a trust with with a second DC with SBS and move user accounts and mailboxes to the new internal domain, but I'm not sure if that is possible.  Any insight would be greatly appreciated!

    SBS can't do trusts but the migration prep tool temporarily allows them I believe.  Have a look at this link dealing with migration to 2012 essentials from SBS, it doesn't deal with exchange though:
    https://technet.microsoft.com/en-us/library/jj721754.aspx
    There is also a recent thread "Migrating from SBS 2011 to Server 2012R2 Standard & Exchange 2013" that may have some info.
    -- Al

  • Migrating a mailbox cross forest from exchange 2013 Sp1 to exchange 2010 SP2 Update rollup 8

    I can migrate a mailbox fine from exchange 2010 sp2 update rollup 8 to exchange 2013 sp1 or Cu2.
    I was testing today migrating cross forest from 2010 sp2 udpate rollup 8 back to exchange 2010 sp2 but I get the below error.  Is this even possible?  I cannot find any documentation on this scenario yet.
    VERBOSE: [21:52:47.622 GMT] New-MoveRequest : The remote server doesn't support client 'casservername.domain.com'
    version (14.2.341.0 caps:05FEFF). Missing functionality: 'TenantHint'.
    VERBOSE: [21:52:47.637 GMT] New-MoveRequest : Admin Audit Log: Entered Handler:OnComplete.
    The remote server doesn't support client 'casservername.domain.com' version (14.2.341.0 caps:05FEFF). Missing functionality: 'TenantHint'.
        + CategoryInfo          : NotSpecified: (0:Int32) [New-MoveRequest], RemotePermanentException
        + FullyQualifiedErrorId : 782D22F0,Microsoft.Exchange.Management.RecipientTasks.NewMoveRequest

    Hi Steve,
    I'm a little confused what you are saying. Here is my understanding:
    When you migrate mailboxes from Exchange 2013 back to Exchange 2007, the above error occurs.
    If I have misunderstood your concern, please let me know.
    For migrating mailboxes back to Exchange 2007, there is a simple and straightforward method. Please use the New-MailboxExportRequest cmdlet to convert all mailboxes into pst files. And then use the Import-Mailbox cmdlet to import all pst files into Exchange
    2007.
    Hope it helps.
    Best regards,
    If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Amy Wang
    TechNet Community Support

  • Exchange 2013 sp1 move databases

    Hello all
    I am running Exchange 2013 sp1 in a two node DAG. Originally the DAG  had two under powered servers, i built two new more powerful servers added the servers to the DAG, then i moved database copies to the new servers, removed the copies from the original
    servers and then removed the original servers from the DAG. The two original servers are multi role (CAS Mailbox) and currently they are still in the org. My confusion is around this. When i run get-mailbox -identity <name>. The output from the command
    shows the mailbox is on oldserver.  Again oldserver was removed from the DAG and no databases exist on the server. I want to remove the two old servers from the org, but i am hesitant on doing this because all mailboxes seem to think they exist on oldserver 
    Thanks for any help
    Bulls on Parade

    You can ignore that:
    http://blogs.technet.com/b/timmcmic/archive/2011/09/26/exchange-2010-homemta-and-msexchhomeservername-are-not-updated-on-mailboxes.aspx
    Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

  • How to configure AD on windows 2012 server for Exchange 2013 internal and external email flow

    Dear Experts,
    I have to configure exchange 2013 on Windows server 2012 STD. Company has registered Static IP addresses and can get the MX record pointing to any of this Static IP.  
    The registered domain name is e.g.  contoso.com. 
    a. What should I use as domain name on AD? contoso.com or contoso.local
    b. Is it recommended to have two different servers  for AD and Exchange?
    c. What should be my connector settings for mail flow?
    d. how can I set 2 email servers in company for load balancing?

    Hi,
    a, I suggest use contoso.com as domain name. It is convenient to add urls into our certificate for internal and external mail flow.
    b, Recommended that installing AD
    and Exchange Server on two separate
    Servers. If Exchange Server downed unfortunately, it can prevent AD server from crushing at the same time.
    c, Found some articles for your reference:
    Configure Mail Flow and Client Access
    http://technet.microsoft.com/en-us/library/jj218640(v=exchg.150).aspx
    Configuring Outbound Mail Flow in Exchange Server 2013
    http://exchangeserverpro.com/configuring-outbound-mail-flow-in-exchange-server-2013/
    d, Load Balancing
    http://technet.microsoft.com/en-us/library/jj898588(v=exchg.150).aspx
    Hope it is helpful
    Thanks
    Mavis
    Mavis Huang
    TechNet Community Support

  • Send Issues with Outlook for Mac (2011 / V15) and Exchange 2013 SP1

    Hi all,
    we have a strange issue with only with Outlook for Mac Users (version 2011 and the newest Outlook Version (V15) from Office 365) connected to our Exchange Server 2013 SP1. Some emails which we send out to the exactly same recipient are not sent through our
    Exchange Server. 
    We have sent 8 emails with subject "test1, test2, test3...". Only test 3-6 was arriving to the recipient. The other emails are in the "sent" folder but it was not sent out through the Exchange.
    What we can see with "Get-MessageTrackingLog" is, that the Recipients and MessageSubject are empty for these emails:
    Timestamp Sender Recipients MessageSubject
    25.02.2015 16:48:52 [email protected].. {}
    25.02.2015 17:04:43 [email protected].. {}
    25.02.2015 17:08:25 [email protected].. {[email protected]} test 3
    25.02.2015 17:08:56 [email protected].. {[email protected]} test 4
    25.02.2015 17:09:38 [email protected].. {[email protected]} test 5
    25.02.2015 17:09:38 [email protected].. {[email protected]} test 6
    25.02.2015 17:13:45 [email protected].. {}
    25.02.2015 17:13:55 [email protected].. {}
    We can still reproduce the issue on different Mac computers.
    Thanks for any help in advance!
    Thanks and best regards
    Reto

    Here is the mailheader form the successfully sent email:
    Date: Wed, 25 Feb 2015 17:08:25 +0100
    Subject: test 3
    From: sender <[email protected]>
    To: "'[email protected]'" <[email protected]>
    This mailheader is from an email which was not sent out:
    User-Agent: Microsoft-MacOutlook/15.6.0.150113
    Date: Wed, 25 Feb 2015 16:48:52 +0100
    Subject: test 1
    From: sender <[email protected]>
    To: [email protected] <[email protected]>
    Interesting: Only the not received messages contains User-Agent string and have some quotation marks missing in the To field.

  • Cross-forest migration to Exchange 2013 SP1 and Outlook 2013 SP1

    Hello! I have two forest: Exchange 2010 SP2 RU5 - resource forest and Exchange 2013 SP1 - account forest. I make cross-forest migration from resource forest (linked mailboxes with account forest) to forest with Exchange 2013 SP1.
    I have moved mailbox from resource forest exchange 2010 to exchange 2013 sp1 forest.
    Outlook 2010 connect to migrated mailbox without any problem, but outlook 2013 sp1 cannot connect to migrated mailbox.
    Error look like - cannot find exchange server.
    I created new mailbox in Exchange 2013 organization and can connect to it with outlook 2010 and outlook 2013 sp1.
    Someone have the same problem with migrated mailbox? How to solve it?
    Truly, Valery Tyurin

    You can use New-MoveRequest to perform a cross-forest move. Here is a well post and step-wise explanation you can check for cross forest migration from exchange 2010 to exchange 2013(http://msexchangeguru.com/2013/11/03/e2013crossforestmigration/).
    Moreover, you can try this utility (
    http://www.exchangemigrationtool.com/ ) to accomplish this task.

  • Exchange 2013 SP1 CU6 / WinSer 12R2 - Recreate Daily Performance Logs

    Hi there,
    I disabled the jobs in Task Sheduler to get rid of the logfiles. Now I wanted to reactivate the jobs but they are missing and I don´t know how to "install" them again.
    Some said after rebooting the server, the jobs are automatically recreated, but that´s not the case on my server. Additionally I get Performance Counter errors, don´t know if these have anything to do with that.
    It´s a test environment with an Exchange 2007 SP3 and Exchange 2013 SP1 CU6 (+ ActiveSync hotfix).
    Has anybody an idea how to get the sheduled tasks available/working again? 

    Hi,
    Do you mean:
    Task ConvertLogEntries missing from C:\Windows\System32\Tasks\Microsoft\Windows\PLA\System
    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Schedule\TaskCache\Tree\Microsoft\Windows\PLA\System\ConvertLogEntries]
    "Id"="{76663950-2087-40B2-A63E-9A940F2C5508}"
    "Index"=dword:00000000
    Thanks,
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Simon Wu
    TechNet Community Support

  • Exchange 2013 SP1 and SCOM 2012 R2

    Hi there, 
    Hopefully someone can assist me with this issue, if it is one... 
    I am halfway through an Exchange migration, from Exchange 2010 SP3 on Server 2008 R2 to Exchange 2013 SP1 on Server 2012 R2.
    76 users in total, roughly 80GB of Public Folders.
    I have configured the 2013 environment with a cross datacenter DAG, also increased all of the timeouts of the cluster to take this into consideration, and everything appears to function as expected. 
    Added both 2013 machines to SCOM 2012 R2 for at least a week with no active users on it, and all monitoring reported ok, no issues. 
    Exchange 2010 is configured to use webmail.company.com for RPC over HTTP, which is what I have configured 2013 to use as well. 
    Implemented Microsoft ARR for client access to Exchange 2013, as opposed to ISA we've used for Exchange 2010. 
    A week ago, changed the DNS records for webmail.company.com from ISA to ARR, and all clients connected perfect. 
    Thought, ok, now we can start the migration. So far everything "seems" to be going perfect with the mailbox moves, however, SCOM is really noisy. 
    Attempted to reran the probe for EWS and got the error below:
    Is there perhaps anyone that can assist me with these errors?
    Cheers

    FYI... IIS ARR is not supported for Exchange Server.
    Check in event log if you are getting anything related to the issue.
    About Outlook POP UP to end users. Check the event log on 2010/2013 for MRS events.
    Are those mailboxes still moving or in move request?
    Cheers,
    Gulab Prasad
    Technology Consultant
    Blog:
    http://www.exchangeranger.com    Twitter:
      LinkedIn:
       Check out CodeTwo’s tools for Exchange admins
    Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

  • Problems with Outlook 2013 and Windows 8.1 with Exchange 2013

    Hello Guys,
    I just got started with testing Exchange 2013. My lab consists of 2 Exchange 2013 Servers, the Installation Media is the Exchange 2013 SP1 from MSDN, Server 2012 R2 and 2 Windows 8.1 Clients with Office 2013 SP 1 with all updates installed. I have configured
    some mailboxes in Exchange and I want now to configure Outlook. So at the initial startup Outlook displays the correct Name and Mail Address. When I click next I make it to Logging on the mail server and then I am getting the Error : The connection to Microsoft
    Exchange is unavailable. Your Network adapter does not have a default Gateway. All servers are in the network 192.168.5.0 /24. Any suggestions how can I fix this problem ?
    Thank you

    Hi there and thanks for Posting!
    You can correct the issue by disabling outlook connection optimism.
    Full details can be found from link below.
    http://blogs.technet.com/b/rmilne/archive/2014/03/27/outlook-unable-to-connect-to-exchange-_1320_default-gateway-not-found.aspx
    Happy Testing :)
    Farhad

  • Exchange 2013 SP1 mailbox role on 2012 R2 and 2012

    Hi,
    We have a client who were running the following setup:
    2 x Exchange 2013 CU2 CAS servers / Win Srv 2012
    2 x Exchange 2013 CU2 MBX servers / Win Srv 2012
    Active Directory etc, basically everything else, runs on Win Server 2012.
    Due to upgrading etc, one of the mailbox servers has been removed. It is to be installed with Ex2013 SP1 with 2012 R2 from scratch, and eventually also upgrade the remaining CAS and MBX srvers with SP1 and 2012 R2.
    So my question is..will this present a problem? Is it possible to have one MBX running 2013 CU2 on Server 2012 and one MBX running 2013 SP1 on Server 2012 R2?
    I've read that failover clustering service is not possible between 2012 and 2012 R2, but i'm not sure how this effects Exchange.
    Thanks for your time.

    Hi,
    Each member of the DAG should be running the same operating system. It is not supported to run a DAG member on Windows Server 2012 R2 and run another member on  Windows Server 2012.
    What's more, upgrading the OS is not supported on Exchange server.
    Here are some helpful threads for your reference.
    Planning for High Availability and Site Resilience
    http://technet.microsoft.com/en-us/library/dd638104(v=exchg.150).aspx
    Exchange 2013 CU2 and Upgrading from Server 2012 to Server 2012 R2 issues
    http://social.technet.microsoft.com/Forums/exchange/en-US/afba40de-efb6-4916-ae42-b09cff35e5d7/exchange-2013-cu2-and-upgrading-from-server-2012-to-server-2012-r2-issues
    Hope it helps.
    Best regards,
    If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Amy Wang
    TechNet Community Support

  • Cannot connect to Exchange server (Small Business Server 2008) using Windows 8.1 and Outlook 2013

    I am at my wits end. I have got a new PC running Windows 8.1 and Outlook 2013 simply WILL NOT connect to my work Exchange server. The REALLY annoying thing is that the Windows Mail client inbuilt to Windows 8.1 works perfectly! But I have to have Outlook
    for the functionality. The issue appears to be that in Outlook 2013 on Windows 8.1, it tries to be clever and auto-detect the settings whereas Windows Mail allows you to input the server and domain names.  
    I have tried all the suggestions already on some of the boards - manual setup, etc - nothing works! Is it a compatibilityissue with SBS 2008 and Outlook 2013? Any help appreciated!

    I am at my wits end. I have got a new PC running Windows 8.1 and Outlook 2013 simply WILL NOT connect to my work Exchange server.................... it tries to be clever and auto-detect the settings.  
    I have tried all the suggestions already on some of the boards - manual setup, etc - nothing works! Is it a compatibilityissue with SBS 2008 and Outlook 2013? Any help appreciated!
    There's no issue with O'2013 connecting with Ex '2007. Also not clear about comments of "auto-detect" versus "....have tried all the suggestions ............ manual setup....". On the one hand your stating that only "auto-detect" is available and on the
    other that you've tried "manual settings" (which definitely is an option in O'2013 for EX accounts).
    This may have more to do with the fact that you're using a new computer trying to connect to the server which it may not be configured for - something your admin will need to address.
    Given that your question is in reference to Exchange - you are likely to get a better/faster answer in the following forum which deals with Exchange server related questions:
    Exchange Previous Versions - Outlook, OWA, POP, and IMAP Clients
    http://social.technet.microsoft.com/Forums/en-US/exchangesvrclientslegacy/threads
    Karl Timmermans [Outlook MVP] "Outlook Contact Import/Export/Data Mgmt" http://www.contactgenie.com

  • SCCM 2012 and Exchange 2013 Connector

    Hello all,
    I hope that you are well!
    I have an issue that I can't explain for the moment, maybe someone can help me.
    Actually we have SCCM 2012 SP1 and Exchange 2013 Enterprise in our LAN.
    Now I did the configuration within SCCM of creating a new Exchange Server Connectors, everything seem's to be okay, no warning, no active alert, the Exchange server connection account and so on..
    But I can't see the mobile devices from my user into the All Mobile Devices within SCCM 2012.
    Do I miss something into this specific configuration, certificate or something related !
    Best regards to all of you
    Stephane

    Hello Gerry,
    This is what I got on EassDisc.log
    ERROR: [MANAGED] Invoking cmdlet Get-Recipient failed. Exception: System.Management.Automation.RemoteException: Cannot bind parameter 'Filter' to the target. Exception setting "Filter": "The value "$true" could not be converted to type System.Boolean."~~  
    at System.Management.Automation.PowerShell.CoreInvoke[TOutput](IEnumerable input, PSDataCollection`1 output, PSInvocationSettings settings)~~   at System.Management.Automation.PowerShell.Invoke(IEnumerable input, PSInvocationSettings settings)~~  
    at System.Management.Automation.PowerShell.Invoke()~~   at Microsoft.ConfigurationManager.ExchangeConnector.Connector.Invoke(PSCommand cmd)
    ERROR: [MANAGED] Exception: Cannot bind parameter 'Filter' to the target. Exception setting "Filter": "The value "$true" could not be converted to type System.Boolean."
    ERROR: Failed to check status of discovery thread of managed COM. error = Unknown error 0x80131501
    But that is old error, since I configure the Account properly
    Regards to you,
    Stephane

  • SBS 2011 and Exchange 2013

    Hey Experts,
    So an associate of mine decided to do a little freelance work for a business who's requirements were;
    -File Shares
    -AD DS/DNS/DHCP
    -Exchange Server
    -SQL Server
    The current server is a SBS 2003 box, with 2003 Exchange also installed. The plan was to migrate AD/Exchange to SBS 2011, however, he soon ran into a road block. Exchange 2003+ is not supported by SBS 2011, only Server 2008/2012 standard and upwards.
    What should he do in this scenario?
    Currently we're looking at purchasing Server 2012 R2 Standard and installing Exchange 2013. Advice?

    How would we go about licensing, as far as I understand, exchange and 2012 have different CAL restrictions.
    I'm not a licensing advisor.
    Exchange and Server 2012 indeed have separate licensing requirements, each have a Server License requirement (for the server), and you each product also requires their own Client Access Licenses for users/devices who will be accessing the products.
    You're looking at Windows Server 2012 license, and Exchange Server 2013 license, and probably 15 client access licenses for each (15 for Server, 15 for Exchange).
    Windows Server 2012 specifically has a 1+2 server license. With this, you can install the Server license on a system (that's the "1").  If you enable only the Hyper-V role on the physical server, and run Virtual Machines as children in
    this parent server, you are entitled to run two Virtualized instances of this same license on that hardware (that's the "2).  This also applies if you are virtualized on another virtualization platform; one license for Server 2012 allows 2 virtualized
    instances on the same host hardware.  If you don't virtualize your workloads and you have two hardware installs of Server 2012, well you'll need two server licenses in that model. For a small business such as described, I'd virtualize every time.
    Larry mentions a good point; you can enable the 'Essentials' role on the Server 2012 R2 platform that provides wizard driven interfaces for enabling Remote Web App, and PC backups from a Dashboard console.  Weigh the value in this, as you will have
    more work in front of you if you want to enable this and still provide remote access to email on your Exchange 2013 system (multiple external IP's and a modern firewall or the Microsoft ARR utility can address this). Generally OWA and Outlook Anywhere require
    HTTPS redirection at your gateway to the Exchange server. RWA in Essentials uses the same protocol, so plan accordingly.
    Hope that helps,
    Jason
    Jason Miller B.Comm (Hons), MCSA, MCITP, Microsoft MVP

Maybe you are looking for